diff --git a/marked/Rel-18/38_series/38108/16da2d7b436c26f2efc4b51b2aae0fed_img.jpg b/marked/Rel-18/38_series/38108/16da2d7b436c26f2efc4b51b2aae0fed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa189265add40b6c126b86a4d057a686b1a88241 --- /dev/null +++ b/marked/Rel-18/38_series/38108/16da2d7b436c26f2efc4b51b2aae0fed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a931a8b7630f07d66f2240b101dc88113fca233f3042ddaace9ee02389c5980b +size 48532 diff --git a/marked/Rel-18/38_series/38108/2876be3592c7b4878400b85f209b2b6a_img.jpg b/marked/Rel-18/38_series/38108/2876be3592c7b4878400b85f209b2b6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8c2cbbd4dd0aaf25875918bd4afed9a71314941 --- /dev/null +++ b/marked/Rel-18/38_series/38108/2876be3592c7b4878400b85f209b2b6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:425f64600fd30d0e651ba5ca4dbdec8a95440cf39630a272a02c6c26c6e6f330 +size 67424 diff --git a/marked/Rel-18/38_series/38108/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg b/marked/Rel-18/38_series/38108/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb07d6a13294b15261f29a4d7b26415a09d6303b --- /dev/null +++ b/marked/Rel-18/38_series/38108/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1a83663c48f95932f2d77ab2a367a742380a357c4a4525506d81cbc7c27d04a +size 44550 diff --git a/marked/Rel-18/38_series/38108/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38108/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1800df19cd8e948b2f0eb0857e7dd9512468eb1 --- /dev/null +++ b/marked/Rel-18/38_series/38108/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ffbd8e06d9211a3a5d695e3eba4609c55cf1f49ae5a03deabf523fb9f86d6cc5 +size 9521 diff --git a/marked/Rel-18/38_series/38108/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38108/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2253c328a6150440d42b63a1b7afb37d9cf096bc --- /dev/null +++ b/marked/Rel-18/38_series/38108/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:149750b8132a393f535ed3199b0a696de83cc823fa7706f9cb1dfa5bcf408a26 +size 5602 diff --git a/marked/Rel-18/38_series/38108/694df81535f89c7bfb9ef0df6f130dc0_img.jpg b/marked/Rel-18/38_series/38108/694df81535f89c7bfb9ef0df6f130dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d479b7d4983773a942f9525bc720a6d04fea78d6 --- /dev/null +++ b/marked/Rel-18/38_series/38108/694df81535f89c7bfb9ef0df6f130dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b431efa4fbaa97f21fb13c9f8d1b3671ca03a8cc50928a62898fc6884e7e5ece +size 38296 diff --git a/marked/Rel-18/38_series/38108/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg b/marked/Rel-18/38_series/38108/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4be75c9185de4960ba74140d4383b73f463b9651 --- /dev/null +++ b/marked/Rel-18/38_series/38108/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c5cd8dc49e996d86ffba9a509ccd3db4bd2f76a078c796cb1e18d172c863c54 +size 28586 diff --git a/marked/Rel-18/38_series/38108/92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg b/marked/Rel-18/38_series/38108/92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dda3a238a0ac74aa5618711bc5b59a15015dd37b --- /dev/null +++ b/marked/Rel-18/38_series/38108/92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1969e53f2fb24c837877a6cda09f7a88497a7014c5febaa2fb7ed12d94cb53f3 +size 144379 diff --git a/marked/Rel-18/38_series/38108/cf64ff479b0c6bc567effa28e2c1d2ea_img.jpg b/marked/Rel-18/38_series/38108/cf64ff479b0c6bc567effa28e2c1d2ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18aa2e133991b3820c3b6c0c58b0bfbce94e5281 --- /dev/null +++ b/marked/Rel-18/38_series/38108/cf64ff479b0c6bc567effa28e2c1d2ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32c2332b24b1950853044b1e28f9be74795cd5e6a1bbb3e8514a2f1a87ce1af8 +size 13632 diff --git a/marked/Rel-18/38_series/38108/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-18/38_series/38108/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b3541f4170f3b707ab1c42a4189c0d29fce773f --- /dev/null +++ b/marked/Rel-18/38_series/38108/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:235efb5e01a21370b3bb3b497cb396645f4a7a540ba478ed218347a94510f4a3 +size 39533 diff --git a/marked/Rel-18/38_series/38108/raw.md b/marked/Rel-18/38_series/38108/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a324b9abb22d1aa6ffd31d99e717b384fdb60d83 --- /dev/null +++ b/marked/Rel-18/38_series/38108/raw.md @@ -0,0 +1,3496 @@ + + +# 3GPP TS 38.108 V18.1.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Satellite Access Node 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 ..... | 8 | +| 1 Scope..... | 10 | +| 2 References..... | 10 | +| 3 Definitions, symbols and abbreviations ..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Symbols..... | 14 | +| 3.3 Abbreviations ..... | 15 | +| 4 General..... | 16 | +| 4.1 Relationship with other core specifications ..... | 16 | +| 4.2 Relationship between minimum requirements and test requirements..... | 16 | +| 4.3 Requirement reference points..... | 16 | +| 4.3.1 SAN type 1-H..... | 16 | +| 4.3.2 SAN type 1-O..... | 17 | +| 4.4 Satellite Access Node classes..... | 17 | +| 4.5 Regional requirements..... | 17 | +| 4.6 Applicability of minimum requirements ..... | 18 | +| 5 Operating bands and channel arrangement ..... | 19 | +| 5.1 General ..... | 19 | +| 5.2 Operating bands..... | 20 | +| 5.3 Satellite Access Node channel bandwidth ..... | 20 | +| 5.3.1 General ..... | 20 | +| 5.3.2 Transmission bandwidth configuration ..... | 21 | +| 5.3.3 Minimum guardband and transmission bandwidth configuration..... | 21 | +| 5.3.4 RB alignment..... | 22 | +| 5.3.5 SAN channel bandwidth per operating band..... | 22 | +| 5.4 Channel arrangement..... | 23 | +| 5.4.1 Channel spacing..... | 23 | +| 5.4.1.1 Channel spacing for adjacent carriers ..... | 23 | +| 5.4.2 Channel raster..... | 23 | +| 5.4.2.1 NR-ARFCN and channel raster ..... | 23 | +| 5.4.2.2 Channel raster to resource element mapping ..... | 23 | +| 5.4.2.3 Channel raster entries for each operating band ..... | 24 | +| 5.4.3 Synchronization raster ..... | 24 | +| 5.4.3.1 Synchronization raster and numbering ..... | 24 | +| 5.4.3.2 Synchronization raster to synchronization block resource element mapping..... | 25 | +| 5.4.3.3 Synchronization raster entries for each operating band..... | 25 | +| 6 Conducted transmitter characteristics ..... | 25 | +| 6.1 General ..... | 25 | +| 6.2 Satellite Access Node output power..... | 25 | +| 6.2.1 General ..... | 25 | +| 6.2.2 Minimum requirement for SAN type 1-H ..... | 26 | +| 6.3 Output power dynamics ..... | 26 | +| 6.3.1 General ..... | 26 | +| 6.3.2 RE power control dynamic range ..... | 26 | +| 6.3.2.1 General..... | 26 | +| 6.3.2.2 Minimum requirement for SAN type 1-H ..... | 26 | +| 6.3.3 Total power dynamic range ..... | 26 | +| 6.3.3.1 General..... | 26 | +| 6.3.3.2 Minimum requirement for SAN type 1-H ..... | 27 | +| 6.4 Transmit ON/OFF power ..... | 27 | +| 6.5 Transmitted signal quality..... | 27 | +| 6.5.1 Frequency error ..... | 27 | +| 6.5.1.1 General..... | 27 | + +| | | | +|-----------|----------------------------------------------------------------|----| +| 6.5.1.2 | Minimum requirement for SAN type 1-H ..... | 27 | +| 6.5.2 | Modulation quality ..... | 27 | +| 6.5.2.1 | General..... | 27 | +| 6.5.2.2 | Minimum Requirement for SAN type 1-H ..... | 27 | +| 6.5.2.3 | EVM frame structure for measurement ..... | 28 | +| 6.5.3 | Time alignment error..... | 28 | +| 6.6 | Unwanted emissions..... | 28 | +| 6.6.1 | General ..... | 28 | +| 6.6.2 | Occupied bandwidth..... | 28 | +| 6.6.2.1 | General..... | 28 | +| 6.6.2.2 | Minimum requirement for SAN type 1-H ..... | 29 | +| 6.6.3 | Adjacent Channel Leakage Power Ratio..... | 29 | +| 6.6.3.1 | General..... | 29 | +| 6.6.3.2 | Minimum requirement for SAN type 1-H ..... | 29 | +| 6.6.4 | Out-of-band emissions..... | 30 | +| 6.6.4.1 | General..... | 30 | +| 6.6.4.2 | Minimum requirements for SAN type 1-H ..... | 30 | +| 6.6.5 | Transmitter spurious emissions ..... | 30 | +| 6.6.5.1 | General..... | 30 | +| 6.6.5.2 | Minimum requirements for SAN type 1-H ..... | 31 | +| 6.6.5.2.1 | General transmitter spurious emissions requirements..... | 31 | +| 6.6.5.2.2 | Protection of the own Satellite Access Node receiver ..... | 31 | +| 6.6.5.2.3 | Additional spurious emissions requirements..... | 31 | +| 6.6.5.2.4 | Co-location with other Satellite Access Nodes..... | 31 | +| 6.7 | Transmitter intermodulation..... | 31 | +| 7 | Conducted receiver characteristics..... | 32 | +| 7.1 | General ..... | 32 | +| 7.2 | Reference sensitivity level ..... | 32 | +| 7.2.1 | General ..... | 32 | +| 7.2.2 | Minimum requirements for SAN type 1-H ..... | 32 | +| 7.3 | Dynamic range ..... | 33 | +| 7.3.1 | General ..... | 33 | +| 7.3.2 | Minimum requirements for SAN type 1-H ..... | 33 | +| 7.4 | In-band selectivity and blocking ..... | 34 | +| 7.4.1 | Adjacent Channel Selectivity (ACS)..... | 34 | +| 7.4.1.1 | General..... | 34 | +| 7.4.1.2 | Minimum requirements for SAN type 1-H ..... | 34 | +| 7.4.2 | In-band blocking..... | 34 | +| 7.5 | Out-of-band blocking ..... | 35 | +| 7.5.1 | General ..... | 35 | +| 7.5.2 | Minimum requirements for SAN type 1-H ..... | 35 | +| 7.6 | Receiver spurious emissions ..... | 35 | +| 7.6.1 | Void..... | 35 | +| 7.6.2 | Void..... | 35 | +| 7.7 | Receiver intermodulation..... | 35 | +| 7.8 | In-channel selectivity ..... | 36 | +| 7.8.1 | General ..... | 36 | +| 7.8.2 | Minimum requirements for SAN type 1-H ..... | 36 | +| 8 | Conducted performance requirements ..... | 37 | +| 8.1 | General ..... | 37 | +| 8.2 | Performance requirements for PUSCH..... | 38 | +| 8.2.1 | Requirements for PUSCH with transform precoding disabled ..... | 38 | +| 8.2.1.1 | General..... | 38 | +| 8.2.1.2 | Minimum requirements..... | 38 | +| 8.2.2 | Requirements for PUSCH with transform precoding enabled ..... | 39 | +| 8.2.2.1 | General..... | 39 | +| 8.2.2.2 | Minimum requirements..... | 40 | +| 8.2.3 | Requirements for UL timing adjustment..... | 41 | +| 8.2.3.2 | Minimum requirements..... | 42 | +| 8.2.4 | Requirements for PUSCH repetition Type A ..... | 43 | + +| | | | +|-------------|---------------------------------------------------------------------------|----| +| 8.2.4.1 | General..... | 43 | +| 8.2.4.2 | Minimum requirements..... | 44 | +| 8.3 | Performance requirements for PUCCH..... | 45 | +| 8.3.1 | DTX to ACK probability..... | 45 | +| 8.3.1.1 | General..... | 45 | +| 8.3.1.2 | Minimum requirement ..... | 45 | +| 8.3.2 | Performance requirements for PUCCH format 0 ..... | 45 | +| 8.3.2.1 | General..... | 45 | +| 8.3.2.2 | Minimum requirements..... | 45 | +| 8.3.3 | Performance requirements for PUCCH format 1 ..... | 46 | +| 8.3.3.1 | NACK to ACK requirements..... | 46 | +| 8.3.3.1.1 | General ..... | 46 | +| 8.3.3.1.2 | Minimum requirements ..... | 46 | +| 8.3.3.2 | ACK missed detection requirements ..... | 47 | +| 8.3.3.2.1 | General ..... | 47 | +| 8.3.3.2.2 | Minimum requirements ..... | 47 | +| 8.3.4 | Performance requirements for PUCCH format 2 ..... | 48 | +| 8.3.4.1 | ACK missed detection requirements ..... | 48 | +| 8.3.4.1.1 | General ..... | 48 | +| 8.3.4.1.2 | Minimum requirements ..... | 48 | +| 8.3.4.2 | UCI BLER performance requirements ..... | 48 | +| 8.3.4.2.1 | General ..... | 48 | +| 8.3.4.2.2 | Minimum requirements ..... | 49 | +| 8.3.5 | Performance requirements for PUCCH format 3 ..... | 49 | +| 8.3.5.1 | General..... | 49 | +| 8.3.5.2 | Minimum requirements..... | 50 | +| 8.3.6 | Performance requirements for PUCCH format 4 ..... | 50 | +| 8.3.6.1 | General..... | 50 | +| 8.3.6.2 | Minimum requirement ..... | 51 | +| 8.3.7 | Performance requirements for multi-slot PUCCH ..... | 51 | +| 8.3.7.1 | General..... | 51 | +| 8.3.7.2 | Performance requirements for multi-slot PUCCH format 1 ..... | 51 | +| 8.3.7.2.1 | NACK to ACK requirements..... | 51 | +| 8.3.7.2.1.1 | General ..... | 51 | +| 8.3.7.2.1.2 | Minimum requirements ..... | 52 | +| 8.3.7.2.2 | ACK missed detection requirements..... | 52 | +| 8.3.7.2.2.1 | General ..... | 52 | +| 8.3.7.2.2.2 | Minimum requirements ..... | 53 | +| 8.4 | Performance requirements for PRACH..... | 53 | +| 8.4.1 | PRACH False alarm probability..... | 53 | +| 8.4.1.1 | General..... | 53 | +| 8.4.1.2 | Minimum requirement ..... | 53 | +| 8.4.2 | PRACH detection requirements ..... | 53 | +| 8.4.2.1 | General..... | 53 | +| 8.4.2.2 | Minimum requirements..... | 54 | +| 9 | Radiated transmitter characteristics ..... | 54 | +| 9.1 | General ..... | 54 | +| 9.2 | Radiated transmit power..... | 54 | +| 9.2.1 | General ..... | 54 | +| 9.2.2 | Minimum requirement for SAN type 1-H and SAN type 1-O ..... | 55 | +| 9.3 | OTA Satellite Access Node output power ..... | 55 | +| 9.3.1 | General ..... | 55 | +| 9.3.2 | Minimum requirement for SAN type 1-O ..... | 55 | +| 9.4 | OTA output power dynamics..... | 55 | +| 9.4.1 | General ..... | 55 | +| 9.4.2 | OTA RE power control dynamic range..... | 56 | +| 9.4.2.1 | General..... | 56 | +| 9.4.2.2 | Minimum requirement for SAN type 1-O ..... | 56 | +| 9.4.3 | OTA total power dynamic range ..... | 56 | +| 9.4.3.1 | General..... | 56 | +| 9.4.3.2 | Minimum requirement for SAN type 1-O ..... | 56 | + +| | | | +|-----------|---------------------------------------------------------------|----| +| 9.5 | OTA transmit ON/OFF power ..... | 56 | +| 9.6 | OTA transmitted signal quality ..... | 56 | +| 9.6.1 | OTA frequency error ..... | 56 | +| 9.6.1.1 | General ..... | 56 | +| 9.6.1.2 | Minimum requirement for SAN type 1-O ..... | 57 | +| 9.6.2 | OTA modulation quality ..... | 57 | +| 9.6.2.1 | General ..... | 57 | +| 9.6.2.2 | Minimum requirement for SAN type 1-O ..... | 57 | +| 9.6.3 | OTA time alignment error ..... | 57 | +| 9.7 | OTA unwanted emissions ..... | 57 | +| 9.7.1 | General ..... | 57 | +| 9.7.2 | OTA occupied bandwidth ..... | 57 | +| 9.7.2.1 | General ..... | 57 | +| 9.7.2.2 | Minimum requirement for SAN type 1-O ..... | 58 | +| 9.7.3 | OTA Adjacent Channel Leakage Power Ratio (ACLR) ..... | 58 | +| 9.7.3.1 | General ..... | 58 | +| 9.7.3.2 | Minimum requirement for SAN type 1-O ..... | 58 | +| 9.7.4 | OTA out-of-band emissions ..... | 58 | +| 9.7.4.1 | General ..... | 58 | +| 9.7.4.2 | Minimum requirement for SAN type 1-O ..... | 58 | +| 9.7.5 | OTA transmitter spurious emissions ..... | 58 | +| 9.7.5.1 | General ..... | 58 | +| 9.7.5.2 | Minimum requirement for SAN type 1-O ..... | 59 | +| 9.7.5.2.1 | General ..... | 59 | +| 9.7.5.2.2 | General OTA transmitter spurious emissions requirements ..... | 59 | +| 9.7.5.2.3 | Protection of the SAN receiver ..... | 59 | +| 9.7.5.2.4 | Additional spurious emissions requirements ..... | 59 | +| 9.8 | OTA transmitter intermodulation ..... | 59 | +| 10 | Radiated receiver characteristics ..... | 60 | +| 10.1 | General ..... | 60 | +| 10.2 | OTA sensitivity ..... | 60 | +| 10.2.1 | General ..... | 60 | +| 10.2.2 | Minimum requirement for SAN type 1-O ..... | 61 | +| 10.3 | OTA reference sensitivity level ..... | 61 | +| 10.3.1 | General ..... | 61 | +| 10.3.2 | Minimum requirement for SAN type 1-O ..... | 61 | +| 10.4 | OTA dynamic range ..... | 62 | +| 10.4.1 | General ..... | 62 | +| 10.4.2 | Minimum requirement for SAN type 1-O ..... | 62 | +| 10.5 | OTA in-band selectivity and blocking ..... | 63 | +| 10.5.1 | OTA adjacent channel selectivity ..... | 63 | +| 10.5.1.1 | General ..... | 63 | +| 10.5.1.2 | Minimum requirement for SAN type 1-O ..... | 63 | +| 10.5.2 | OTA in-band blocking ..... | 64 | +| 10.6 | OTA out-of-band blocking ..... | 64 | +| 10.6.1 | General ..... | 64 | +| 10.6.2 | Minimum requirement for SAN type 1-O ..... | 64 | +| 10.6.2.1 | General minimum requirement ..... | 64 | +| 10.7 | OTA receiver spurious emissions ..... | 65 | +| 10.7.1 | Void ..... | 65 | +| 10.7.2 | Void ..... | 65 | +| 10.8 | OTA receiver intermodulation ..... | 65 | +| 10.9 | OTA in-channel selectivity ..... | 65 | +| 10.9.1 | General ..... | 65 | +| 10.9.2 | Minimum requirement for SAN type 1-O ..... | 65 | +| 11 | Radiated performance requirements ..... | 66 | +| 11.1 | General ..... | 66 | +| 11.1.1 | Scope and definitions ..... | 66 | +| 11.1.2 | OTA demodulation branches ..... | 67 | +| 11.2 | Performance requirements for PUSCH ..... | 67 | + +| | | | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------| +| 11.2.1 | Requirements for PUSCH with transform precoding disabled ..... | 67 | +| 11.2.2 | Requirements for PUSCH with transform precoding enabled ..... | 67 | +| 11.2.3 | Requirements for UL timing adjustment..... | 68 | +| 11.2.4 | Requirements for PUSCH repetition Type A ..... | 68 | +| 11.3 | Performance requirements for PUCCH..... | 68 | +| 11.3.1 | Requirements for SAN type 1-O ..... | 68 | +| 11.3.1.1 | DTX to ACK probability ..... | 68 | +| 11.3.1.2 | Performance requirements for PUCCH format 0 ..... | 68 | +| 11.3.1.3 | Performance requirements for PUCCH format 1 ..... | 68 | +| 11.3.1.4 | Performance requirements for PUCCH format 2 ..... | 68 | +| 11.3.1.5 | Performance requirements for PUCCH format 3 ..... | 68 | +| 11.3.1.6 | Performance requirements for PUCCH format 4 ..... | 68 | +| 11.3.1.7 | Performance requirements for multi-slot PUCCH..... | 68 | +| 11.4 | Performance requirements for PRACH..... | 68 | +| 11.4.1 | PRACH False alarm probability..... | 68 | +| 11.4.2 | PRACH detection requirements ..... | 68 | +| Annex A (normative): Reference measurement channels ..... | | 69 | +| A.1 | Fixed Reference Channels for RF Rx requirements in FR1 (QPSK, R=1/3) ..... | 69 | +| A.2 | Fixed Reference Channels for dynamic range (16QAM, R=2/3) ..... | 69 | +| A.3 | Fixed Reference Channels for performance requirements (QPSK, R=308/1024)..... | 70 | +| A.3A | Fixed Reference Channels for performance requirements (QPSK, R=99/1024)..... | 71 | +| A.4 | PRACH test preambles ..... | 72 | +| Annex B (normative): Error Vector Magnitude (FR1) ..... | | 72 | +| B.1 | Reference point for measurement ..... | 72 | +| B.2 | Basic unit of measurement..... | 73 | +| B.3 | Modified signal under test..... | 73 | +| B.4 | Estimation of frequency offset..... | 74 | +| B.5 | Estimation of time offset..... | 74 | +| B.5.1 | General ..... | 74 | +| B.5.2 | Window length ..... | 74 | +| B.6 | Estimation of TX chain amplitude and frequency response parameters..... | 75 | +| B.7 | Averaged EVM ..... | 77 | +| Annex C (normative): Characteristics of the interfering signals..... | | 78 | +| Annex D (Normative): Propagation conditions ..... | | 78 | +| D.1 | Static propagation condition ..... | 78 | +| D.2 | Multi-path fading propagation conditions..... | 78 | +| D.2.1 | Delay profiles ..... | 78 | +| D.2.1.1 | Delay profiles for FR1 ..... | 79 | +| D.2.2 | Combinations of channel model parameters ..... | 79 | +| D.2.3 | MIMO channel correlation matrices ..... | 80 | +| D.2.3.1 | MIMO correlation matrices using Uniform Linear Array ..... | 80 | +| D.2.3.1.1 | Definition of MIMO correlation matrices ..... | 80 | +| D.2.3.1.2 | MIMO correlation matrices at high, medium and low level..... | 80 | +| Annex E (informative): Change history ..... | | 83 | + +# 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 and minimum performance requirements of NR Satellite Access Node (SAN). + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] ITU-R Recommendation SM.329: "Unwanted emissions in the spurious domain". +- [3] 3GPP TS 38.181: "NR; Satellite Node conformance testing". +- [4] ITU-R Recommendation M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000". +- [5] 3GPP TS 38.211: "NR; Physical channels and modulation". +- [6] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification". +- [7] 3GPP TS 38.213: "NR; Physical layer procedures for control". +- [8] ITU-R Recommendation SM.328: "Spectra and bandwidth of emissions". +- [9] ITU-R Recommendation SM.1541-6: "Unwanted emissions in the out-of-band domain". +- [10] 3GPP TS 38.212: "NR; Multiplexing and channel coding". +- [11] 3GPP TS 38.101-5: "NR; User Equipment (UE) radio transmission and reception; Part 5: Satellite access Radio Frequency (RF) and performance requirements" +- [12] 3GPP TR 38.901: "Study on channel model for frequencies from 0.5 to 100 GHz" +- [13] 3GPP TR 38.811: "Study on New Radio (NR) to support non-terrestrial networks" + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +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]. + +**basic limit:** emissions limit relating to the power supplied by a single transmitter to a single antenna transmission line in ITU-R SM.329 [2] used for the formulation of unwanted emission requirements for FR1. + +**beam:** beam (of the antenna) is the main lobe of the radiation pattern of an *antenna array*. + +NOTE: For certain *antenna array*, there may be more than one beam. + +**beam centre direction:** direction equal to the geometric centre of the half-power 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 found. + +**beamwidth:** beam which has a half-power contour that is essentially elliptical, the half-power beamwidths in the two pattern cuts that respectively contain the major and minor axis of the ellipse. + +**Channel edge:** lowest or highest frequency of the NR carrier, separated by the *SAN channel bandwidth*. + +**directional requirement:** 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 REFSENS RoAoA* or the *minSENS RoAoA* as appropriate for the receiver. + +**Enhanced channel raster:** channel raster with a 10 kHz granularity in bands with a 100 kHz channel raster. + +**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 specific requirement is met. + +NOTE 2: Isotropic directivity is equal in all directions (i.e. 0 dBi). + +**feeder link:** Wireless link between satellite-Gateway and satellite. + +**Geostationary Earth Orbit:** Circular orbit at 35,786 km above the Earth's equator and following the direction of the Earth's rotation. An object in such an orbit has an orbital period equal to the Earth's rotational period and thus appears motionless, at a fixed position in the sky, to ground observers. + +**Low Earth Orbit:** Orbit around the Earth with an altitude between 300 km, and 1500 km. + +**Highest Carrier:** The carrier with the highest carrier frequency transmitted/received in a specified frequency band. + +**Lowest Carrier:** The carrier with the lowest carrier frequency transmitted/received in a specified frequency band. + +**maximum carrier output power:** mean power level measured per carrier at the indicated interface, during the *transmitter ON period* in a specified reference condition. + +**maximum carrier TRP output power:** 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 output power* ( $P_{\text{rated,c,TRP}}$ ). + +**maximum total output power:** mean power level measured within the *operating band* at the indicated interface, during the *transmitter ON period* in a specified reference condition. + +**maximum total TRP output power:** mean power level measured per RIB during the *transmitter ON period* in a specified reference condition and corresponding to the declared *rated total TRP output power* ( $P_{\text{rated,t,TRP}}$ ). + +**measurement bandwidth:** RF bandwidth in which an emission level is specified. + +**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. + +**minimum elevation angle:** Minimum angle under which the satellite can be seen by a UE. + +**necessary bandwidth:** The width of the frequency band which is just sufficient to ensure the transmission of information at the rate and with the quality required under specified conditions. + +**non-terrestrial networks:** Networks, or segments of networks, using an airborne or space-borne vehicle to embark a transmission equipment relay node or SAN. + +**operating band:** frequency range in which NR operates (paired or unpaired), that is defined with a specific set of technical requirements. + +NOTE: The *operating band(s)* for a SAN is declared by the manufacturer according to the designations in tables 5.2-1 and 5.2-2. + +**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: 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. + +**OTA REFSENS RoAoA:** 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 beamwidth. + +**OTA sensitivity directions declaration:** set of manufacturer declarations comprising at least one set of declared minimum EIS values (with *SAN channel bandwidth*), and related directions over which the EIS applies. + +NOTE: 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: 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. + +**rated beam EIRP:** For a declared beam and *beam direction pair*, the *rated beam EIRP* level is the maximum power that the SAN is declared to radiate at the associated *beam peak direction* during the *transmitter ON period*. + +**rated carrier output power:** mean power level associated with a particular carrier the manufacturer has declared to be available at the indicated interface, during the *transmitter ON period* in a specified reference condition. + +**rated carrier TRP output power:** mean power level declared by the manufacturer per carrier, for SAN 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 total output power:** mean power level associated with a particular *operating band* the manufacturer has declared to be available at the indicated interface, during the *transmitter ON period* in a specified reference condition. + +**rated total TRP output power:** mean power level declared by the manufacturer, that the manufacturer has declared to be available at the RIB during the *transmitter ON period*. + +**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*. + +**receiver target:** AoA in which reception is performed by *SAN types 1-H* or *SAN type 1-O*. + +**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 RoAoA:** the *sensitivity RoAoA* associated with the *receiver target reference direction* for each OSDD. + +**requirement set:** one of the NR SAN requirement's set as defined for *SAN type 1-H*, *SAN type 1-O*. + +**SAN channel bandwidth:** RF bandwidth supporting a single NR RF carrier with the *transmission bandwidth* configured in the uplink or downlink. + +NOTE 1: The *SAN channel bandwidth* is measured in MHz and is used as a reference for transmitter and receiver RF requirements. + +NOTE 2: It is possible for the SAN to transmit to and/or receive from one or more satellite UE bandwidth parts that are smaller than or equal to the *SAN transmission bandwidth configuration*, in any part of the *SAN transmission bandwidth configuration*. + +**SAN RF Bandwidth:** RF bandwidth in which a SAN transmits and/or receives single or multiple carrier(s) within a supported *operating band*. + +NOTE: In single carrier operation, the *SAN RF Bandwidth* is equal to the *SAN channel bandwidth*. + +**SAN RF Bandwidth edge:** frequency of one of the edges of the *SAN RF Bandwidth*. + +**SAN transmission bandwidth configuration:** set of resource blocks located within the *SAN channel bandwidth* which may be used for transmitting or receiving by the SAN. + +**SAN type 1-H:** Satellite Access Node operating at FR1 with a requirement set consisting of conducted requirements defined at individual *TAB connectors* and OTA requirements defined at RIB. + +**SAN type 1-O:** Satellite Access Node operating at FR1 with a requirement set consisting only of OTA requirements defined at the RIB. + +**SAN total assigned bandwidth:** Bandwidth of the total assigned band (frequencies range) as defined in SM.1541-6 + +**SAN transponder bandwidth:** Total bandwidth of the carrier(s) in operation by one SAN transponder. + +NOTE: When the SAN transponder operates one carrier only, the SAN transponder bandwidth is equal to the SAN channel bandwidth of this carrier. + +**SAN transponder:** part of the SAN permitting to receive, channelize and transmit signals within an allocated bandwidth. + +**satellite:** A space-borne vehicle embarking a bent pipe payload or a regenerative payload telecommunication transmitter, placed into Low-Earth Orbit (LEO) or Geostationary Earth Orbit (GEO). + +**Satellite Access Node:** node providing NR user plane and control plane protocol terminations towards NTN Satellite capable UE, and connected via the NG interface to the 5GC. It encompass a transparent NTN payload on board a NTN platform, a gateway and gNB functions. + +**satellite-gateway:** An earth station or gateway is located at the surface of Earth, and providing sufficient RF power and RF sensitivity for accessing to the satellite. + +**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 SAN direction setting. + +**TAB connector:** *transceiver array boundary* connector. + +**total radiated power:** is the total power radiated by the antenna. + +NOTE: The *total radiated power* is the power radiating in all direction for two orthogonal polarizations. *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 transmission from a satellite UE or SAN, measured in resource block units. + +## 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. | +| $\text{BeW}_{\theta, \text{REFSENS}}$ | Beamwidth equivalent to the OTA REFSENS RoAoA in the $\theta$ -axis in degrees. Applicable for FR1 only. | +| $\text{BeW}_{\phi, \text{REFSENS}}$ | Beamwidth equivalent to the OTA REFSENS RoAoA in the $\phi$ -axis in degrees. Applicable for FR1 only. | +| $\text{BW}_{\text{Channel}}$ | SAN channel bandwidth. | +| $\text{BW}_{\text{Config}}$ | Transmission bandwidth configuration , where $\text{BW}_{\text{Config}} = N_{\text{RB}} \times \text{SCS} \times 12$ . | +| $\text{BW}_{\text{GB,low}}$ | The minimum guard band defined in clause 5.3.3 for lowest assigned component carrier. | +| $\text{BW}_{\text{GB,high}}$ | The minimum guard band defined in clause 5.3.3 for highest assigned component carrier. | +| $\text{BW}_{\text{SAN}}$ | The SAN transponder bandwidth | +| $\Delta f$ | Separation between the channel edge frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency. | +| $\Delta f_{\text{Global}}$ | Global frequency raster granularity. | +| $\Delta f_{\text{max}}$ | $f_{\text{offset,max}}$ minus half of the bandwidth of the measuring filter. | +| $\Delta f_{\text{OOB}}$ | Maximum offset of the out-of-band boundary from the uplink operating band edge. | +| $\Delta f_{\text{minSENS}}$ | Difference between conducted reference sensitivity and minSENS. | +| $\Delta f_{\text{OTAREFSENS}}$ | Difference between conducted reference sensitivity and OTA REFSENS. | +| $\Delta f_{\text{Raster}}$ | Channel raster granularity. | +| $\text{EIS}_{\text{minSENS}}$ | The EIS declared for the minSENS RoAoA . | +| $\text{EIS}_{\text{REFSENS}}$ | OTA REFSENS EIS value. | +| $F_{\text{C}}$ | RF reference frequency on the channel raster, given in table 5.4.2.2-1. | +| $F_{\text{C,low}}$ | The $F_{\text{C}}$ of the lowest carrier , expressed in MHz. | +| $F_{\text{C,high}}$ | The $F_{\text{C}}$ of the highest carrier , expressed in MHz. | +| $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{filter}}$ | Filter centre frequency. | +| $F_{\text{offset,high}}$ | Frequency offset from $F_{\text{C,high}}$ to the upper SAN RF Bandwidth edge . | +| $F_{\text{offset,low}}$ | Frequency offset from $F_{\text{C,low}}$ to the lower SAN RF Bandwidth edge . | +| $f_{\text{offset}}$ | Separation between the channel edge frequency and the centre of the measuring. | +| $f_{\text{offset,max}}$ | The offset to the frequency $\Delta f_{\text{OBUE}}$ outside the downlink operating band . | +| $F_{\text{REF}}$ | RF reference frequency. | +| $F_{\text{REF-Offs}}$ | Offset used for calculating $F_{\text{REF}}$ . | +| $F_{\text{UL,low}}$ | The lowest frequency of the uplink operating band . | +| $F_{\text{UL,high}}$ | The highest frequency of the uplink operating band . | +| $n_{\text{PRB}}$ | Physical resource block number. | +| $N_{\text{RB}}$ | Transmission bandwidth configuration , expressed in resource blocks. | +| $N_{\text{REF}}$ | NR Absolute Radio Frequency Channel Number (NR-ARFCN). | +| $N_{\text{REF-Offs}}$ | Offset used for calculating $N_{\text{REF}}$ scaling per cell, as calculated in clause 6.1. | +| $P_{\text{EIRP,N}}$ | EIRP level for channel N. | +| $P_{\text{max,c,TABC}}$ | The maximum carrier output power per TAB connector . | +| $P_{\text{max,c,TRP}}$ | Maximum carrier TRP output power measured at the RIB(s), and corresponding to the declared rated carrier TRP output power ( $P_{\text{rated,c,TRP}}$ ). | +| $P_{\text{max,c,EIRP}}$ | The maximum carrier EIRP when the SAN is configured at the maximum rated carrier output TRP ( $P_{\text{rated,c,TRP}}$ ). | +| $P_{\text{rated,c,sys}}$ | $P_{\text{rated,c,sys,GEO}}$ for SAN GEO class or $P_{\text{rated,c,sys,LEO}}$ for SAN LEO class. | +| $P_{\text{rated,c,sys,GEO}}$ | The sum of $P_{\text{rated,c,TABC}}$ for all TAB connectors for a single carrier of the SAN GEO class. | +| $P_{\text{rated,c,sys,LEO}}$ | The sum of $P_{\text{rated,c,TABC}}$ for all TAB connectors for a single carrier of the SAN LEO class. | +| $P_{\text{rated,c,TABC}}$ | $P_{\text{rated,c,TABC,GEO}}$ for SAN GEO class or $P_{\text{rated,c,TABC,LEO}}$ for SAN LEO class. | +| $P_{\text{rated,c,TABC,GEO}}$ | The rated carrier output power per TAB connector of the SAN GEO class. | +| $P_{\text{rated,c,TABC,LEO}}$ | The rated carrier output power per TAB connector of the SAN LEO class. | +| $P_{\text{rated,c,TRP}}$ | Rated carrier TRP output power declared per RIB. | + +| | | +|---------------------------|------------------------------------------------------------------------| +| $P_{\text{rated,t,TABC}}$ | The rated total output power declared at TAB connector . | +| $P_{\text{rated,t,TRP}}$ | Rated total TRP output power declared per RIB. | +| $P_{\text{rated,t,sys}}$ | The sum of $P_{\text{rated,t,TABC}}$ for all TAB connectors . | +| $P_{\text{REFSENS}}$ | Conducted Reference Sensitivity power level. | +| $SS_{\text{REF}}$ | SS block reference frequency position. | + +## 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]. + +| | | +|------------|--------------------------------------------| +| AA | Antenna Array | +| ACLR | Adjacent Channel Leakage Ratio | +| ACS | Adjacent Channel Selectivity | +| AoA | Angle of Arrival | +| AWGN | Additive White Gaussian Noise | +| BW | Bandwidth | +| CA | Carrier Aggregation | +| CP-OFDM | Cyclic Prefix-OFDM | +| CW | Continuous Wave | +| DFT-s-OFDM | Discrete Fourier Transform-spread-OFDM | +| DM-RS | Demodulation Reference Signal | +| EIRP | Equivalent Isotropic Radiated Power | +| EIS | Equivalent Isotropic Sensitivity | +| EVM | Error Vector Magnitude | +| FR | Frequency Range | +| FRC | Fixed Reference Channel | +| GEO | Geostationary Earth Orbiting | +| GSCN | Global Synchronization Channel Number | +| ICS | In-Channel Selectivity | +| LEO | Low Earth Orbiting | +| MCS | Modulation and Coding Scheme | +| NR | New Radio | +| NR-ARFCN | NR Absolute Radio Frequency Channel Number | +| NTN | Non-Terrestrial Network | +| OOB | Out-of-band | +| OOBE | Out-of-band Emissions | +| OSDD | OTA Sensitivity Directions Declaration | +| OTA | Over-The-Air | +| PRB | Physical Resource Block | +| PT-RS | Phase Tracking Reference Signal | +| QAM | Quadrature Amplitude Modulation | +| RB | Resource Block | +| RDN | Radio Distribution Network | +| RE | Resource Element | +| REFSENS | Reference Sensitivity | +| RF | Radio Frequency | +| RIB | Radiated Interface Boundary | +| RMS | Root Mean Square (value) | +| RoAoA | Range of Angles of Arrival | +| RX | Receiver | +| SAN | Satellite Access Node | +| SCS | Sub-Carrier Spacing | +| SSB | Synchronization Signal Block | +| TAB | Transceiver Array Boundary | +| TRP | Total Radiated Power | +| TX | Transmitter | + +# 4 General + +## 4.1 Relationship with other core specifications + +The present document is a single-RAT specification for a SAN, covering RF characteristics and minimum performance requirements. Conducted and radiated core requirements are defined for the SAN architectures and SAN types defined in clause 4.3. + +The applicability of each requirement is described in clause 4.6. + +## 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 specification TS 38.181 [3]. + +The minimum requirements given in this specification make no allowance for measurement uncertainty. The test specifications TS 38.181 [3] 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 [4]. + +## 4.3 Requirement reference points + +### 4.3.1 SAN type 1-H + +For *SAN type 1-H*, the requirements are defined for two points of reference, signified by radiated requirements and conducted requirements. + +![Diagram of Satellite Access Node (SAN) architecture for type 1-H. It shows a flow from Non-NTN infrastructure gNB functions to a Gateway, then a Feeder link, and finally into the NTN Payload RF. The NTN Payload RF contains a Transceiver unit array (TRXUA) 1 to M, a Radio Distribution Network (RDN), and an Antenna Array (AA). The TRXUA is connected to the RDN via TAB connectors (labeled #1, #2, #K). The RDN is connected to the AA. Two dashed boxes indicate reference points: the 'Transceiver array boundary' is between the TRXUA and the RDN, and the 'Radiated interface boundary' is between the RDN and the AA. The entire NTN Payload RF is labeled as a 'Composite antenna'.](16da2d7b436c26f2efc4b51b2aae0fed_img.jpg) + +Diagram of Satellite Access Node (SAN) architecture for type 1-H. It shows a flow from Non-NTN infrastructure gNB functions to a Gateway, then a Feeder link, and finally into the NTN Payload RF. The NTN Payload RF contains a Transceiver unit array (TRXUA) 1 to M, a Radio Distribution Network (RDN), and an Antenna Array (AA). The TRXUA is connected to the RDN via TAB connectors (labeled #1, #2, #K). The RDN is connected to the AA. Two dashed boxes indicate reference points: the 'Transceiver array boundary' is between the TRXUA and the RDN, and the 'Radiated interface boundary' is between the RDN and the AA. The entire NTN Payload RF is labeled as a 'Composite antenna'. + +**Figure 4.3.1-1: Radiated and conducted reference points for SAN type 1-H** + +Radiated characteristics are defined over the air (OTA), where the radiated interface is referred to as the *Radiated Interface Boundary* (RIB). Radiated requirements are also referred to as OTA requirements. The (spatial) characteristics in which the OTA requirements apply are detailed for each requirement. + +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 receiving and transmitting modulated signal to ensure radio links with users. + +The satellite payload is composed by a transceiver unit array and a composite antenna array. The transceiver unit array contains an implementation specific number of transmitter units and an implementation specific number of receiver units. + +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 clause. + +### 4.3.2 SAN type 1-O + +For *SAN type 1-O*, the radiated characteristics are defined over the air (OTA), where the *operating band* specific radiated interface is referred to as the *Radiated Interface Boundary* (RIB). Radiated requirements are also referred to as OTA requirements. The (spatial) characteristics in which the OTA requirements apply are detailed for each requirement. + +![Figure 4.3.2-1: Radiated reference points for SAN type 1-O. The diagram shows a Satellite Access Node (SAN) containing three main components: Non-NTN infrastructure gNB functions, a Gateway, and NTN payload RF. The gNB functions and Gateway are connected by a Feeder link. The NTN payload RF is further divided into three sub-components: Transceiver unit array (TRXUA) 1 to M, Radio Distribution Network (RDN), and Antenna Array (AA). A dashed box labeled 'Radiated interface boundary' encloses the TRXUA, RDN, and AA components.](3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg) + +Figure 4.3.2-1: Radiated reference points for SAN type 1-O. The diagram shows a Satellite Access Node (SAN) containing three main components: Non-NTN infrastructure gNB functions, a Gateway, and NTN payload RF. The gNB functions and Gateway are connected by a Feeder link. The NTN payload RF is further divided into three sub-components: Transceiver unit array (TRXUA) 1 to M, Radio Distribution Network (RDN), and Antenna Array (AA). A dashed box labeled 'Radiated interface boundary' encloses the TRXUA, RDN, and AA components. + +Figure 4.3.2-1: Radiated reference points for *SAN type 1-O* + +## 4.4 Satellite Access Node classes + +The requirements in this specification apply to Satellite Access Node unless otherwise stated. The associated deployment scenarios are exactly the same for SAN with and without connectors. + +For *SAN type 1-O* and *SAN type 1-H*, two SAN classes (LEO and GEO) are defined in Table 4.4-1. + +Table 4.4-1 SAN classes + +| SAN Class | Satellite constellation | +|-----------|-----------------------------------------------| +| GEO | GEO satellite | +| LEO | LEO 600 km satellite
LEO 1200 km satellite | + +## 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. + +**Table 4.5-1: List of regional requirements** + +| Clause number | Requirement | Comments | +|---------------|-----------------------------------------------------|-------------------------------------------------------------| +| 5.2 | Operating bands | Satellite operating bands may be applied regionally. | +| 6.6.4,
9.7 | Out-of-band emission,
OTA unwanted emissions | For n255 operation in US, Limits in FCC Title 47 apply. | +| 6.6.5 | Tx spurious emissions,
OTA Tx spurious emissions | For n255 operation in US, Limits in FCC Title 47 apply. | + +## 4.6 Applicability of minimum requirements + +In table 4.6-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 4.6-1: Requirement set applicability** + +| Requirement | Requirement set | | +|-------------------------------------------|-----------------|--------------| +| | SAN type 1-H | SAN type 1-O | +| Satellite Access Network output power | 6.2 | | +| Output power dynamics | 6.3 | | +| Transmit ON/OFF power | NA | | +| Frequency error | 6.5.1 | | +| Modulation quality | 6.5.2 | | +| Time alignment error | NA | | +| Occupied bandwidth | 6.6.2 | | +| ACLR | 6.6.3 | | +| Out-of-band emissions | 6.6.4 | | +| Transmitter spurious emissions | 6.6.5 | | +| Transmitter intermodulation | NA | NA | +| Reference sensitivity level | 7.2 | | +| Dynamic range | 7.3 | | +| ACS | 7.4.1 | | +| In-band blocking | NA | | +| Out-of-band blocking | 7.5 | | +| Receiver spurious emissions | NA | | +| Receiver intermodulation | NA | | +| In-channel selectivity | 7.8 | | +| Performance requirements | 8 | | +| Radiated transmit power | 9.2 | 9.2 | +| OTA Satellite Access Network output power | | 9.3 | +| OTA output power dynamics | | 9.4 | +| OTA transmit ON/OFF power | | NA | +| OTA frequency error | | 9.6.1 | +| OTA modulation quality | | 9.6.2 | +| OTA time alignment error | | NA | +| OTA occupied bandwidth | | 9.7.2 | +| OTA ACLR | NA | 9.7.3 | +| OTA out-of-band emission | | 9.7.4 | +| OTA transmitter spurious emission | | 9.7.5 | +| OTA transmitter intermodulation | | NA | +| OTA sensitivity | 10.2 | 10.2 | +| OTA reference sensitivity level | | 10.3 | +| OTA dynamic range | | 10.4 | +| OTA ACS | | 10.5.1 | +| OTA in-band blocking | | NA | +| OTA out-of-band blocking | NA | 10.6 | +| OTA receiver spurious emission | | NA | +| OTA receiver intermodulation | | NA | +| OTA in-channel selectivity | | 10.9 | +| Radiated performance requirements | | 11 | + +NOTE: Co-location requirements are not applicable to SAN. + +# 5 Operating bands and channel arrangement + +## 5.1 General + +The channel arrangements presented in this clause are based on the *operating bands* and *SAN channel bandwidths* defined in the present release of specifications. + +NOTE: Other *operating bands* and *SAN channel bandwidths* may be considered in future releases. + +Requirements throughout the RF specifications are in many cases defined separately for different frequency ranges (FR). The frequency ranges in which satellite can operate according to the present version of the specification are identified as described in table 5.1-1. + +**Table 5.1-1: Definition of frequency ranges** + +| Frequency range designation | Corresponding frequency range | +|-----------------------------|-------------------------------| +| FR1 | 410 MHz – 7125 MHz | + +## 5.2 Operating bands + +Satellite is designed to operate in the *operating bands* defined in table 5.2-1. + +**Table 5.2-1: 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. | | | + +## 5.3 Satellite Access Node channel bandwidth + +### 5.3.1 General + +The *SAN channel bandwidth* supports a single RF carrier in the uplink or downlink at the SAN. Different UE channel bandwidths may be supported within the same spectrum for transmitting to and receiving from UEs connected to the SAN. The placement of the UE channel bandwidth is flexible but can only be completely within the *SAN channel bandwidth*. The SAN shall be able to transmit to and/or receive from one or more UE bandwidth parts that are smaller than or equal to the number of carrier resource blocks on the RF carrier, in any part of the carrier resource blocks. + +The relationship between the channel bandwidth, the guard band and the *transmission bandwidth configuration* is shown in figure 5.3.1-1. + +![Figure 5.3.1-1: Definition of channel bandwidth and transmission bandwidth configuration for one channel. The diagram shows a horizontal axis representing frequency. A dashed vertical line on the left is labeled 'Channel Edge' and another on the right is also labeled 'Channel Edge'. A double-headed arrow between these edges is labeled 'Channel Bandwidth [MHz]'. Inside this, a solid vertical line on the left and a dashed vertical line on the right define the 'Transmission Bandwidth Configuration N_RB [RB]'. A double-headed arrow between these lines is labeled 'Transmission Bandwidth [RB]'. Below the axis, a series of vertical bars represent 'Resource Block's. A group of these bars, starting from the left solid line, is labeled 'Active Resource Blocks'. The area between the solid line and the dashed line is labeled 'Guardband, can be asymmetric'.](2876be3592c7b4878400b85f209b2b6a_img.jpg) + +Figure 5.3.1-1: Definition of channel bandwidth and transmission bandwidth configuration for one channel. The diagram shows a horizontal axis representing frequency. A dashed vertical line on the left is labeled 'Channel Edge' and another on the right is also labeled 'Channel Edge'. A double-headed arrow between these edges is labeled 'Channel Bandwidth [MHz]'. Inside this, a solid vertical line on the left and a dashed vertical line on the right define the 'Transmission Bandwidth Configuration N\_RB [RB]'. A double-headed arrow between these lines is labeled 'Transmission Bandwidth [RB]'. Below the axis, a series of vertical bars represent 'Resource Block's. A group of these bars, starting from the left solid line, is labeled 'Active Resource Blocks'. The area between the solid line and the dashed line is labeled 'Guardband, can be asymmetric'. + +**Figure 5.3.1-1: Definition of channel bandwidth and *transmission bandwidth configuration* for one channel** + +### 5.3.2 Transmission bandwidth configuration + +The *transmission bandwidth configuration* $N_{RB}$ for each *SAN channel bandwidth* and subcarrier spacing is specified in table 5.3.2-1 for FR1. + +**Table 5.3.2-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 | + +NOTE: All Tx and Rx requirements are defined based on *transmission bandwidth configuration* specified in table 5.3.2-1 for FR1. + +### 5.3.3 Minimum guardband and transmission bandwidth configuration + +The minimum guard band for each *SAN channel bandwidth* and SCS is specified in table 5.3.3-1 for FR1. + +**Table 5.3.3-1: 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. + +![Diagram illustrating SAN PRB utilization. It shows a horizontal axis representing frequency. A rectangular block represents the SAN channel bandwidth. A vertical line in the center of the block represents the carrier. Two dashed arrows point from the text 'Minimum guard band' to the gaps between the block and the carrier. A double-headed arrow below the block is labeled 'SAN channel BW'. Another double-headed arrow below the right half of the block is labeled 'All PRBs falling within SAN channel BW not covering the minimum guard band can be used'.](8ed7f57cc317f6574bec781d01ae6ad2_img.jpg) + +Diagram illustrating SAN PRB utilization. It shows a horizontal axis representing frequency. A rectangular block represents the SAN channel bandwidth. A vertical line in the center of the block represents the carrier. Two dashed arrows point from the text 'Minimum guard band' to the gaps between the block and the carrier. A double-headed arrow below the block is labeled 'SAN channel BW'. Another double-headed arrow below the right half of the block is labeled 'All PRBs falling within SAN channel BW not covering the minimum guard band can be used'. + +**Figure 5.3.3-1: SAN PRB utilization** + +In the case that multiple numerologies are multiplexed in the same symbol, the minimum guard band on each side of the carrier is the guard band applied at the configured *SAN channel bandwidth* for the numerology that is transmitted/received immediately adjacent to the guard band. + +![Figure 5.3.3-2: Guard band definition when transmitting multiple numerologies. The diagram shows a horizontal line representing the SAN channel BW. Above the line, a double-headed arrow labeled 'SAN channel BW' spans a section containing two adjacent blocks labeled 'Numerology X' and 'Numerology Y'. Below the line, two dashed arrows point to the gaps between the numerology blocks and the channel boundaries. The left gap is labeled 'Guard band defined for numerology X when transmitted across full SAN channel BW'. The right gap is labeled 'Guard band defined for numerology Y when transmitted across full SAN channel BW'.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Figure 5.3.3-2: Guard band definition when transmitting multiple numerologies. The diagram shows a horizontal line representing the SAN channel BW. Above the line, a double-headed arrow labeled 'SAN channel BW' spans a section containing two adjacent blocks labeled 'Numerology X' and 'Numerology Y'. Below the line, two dashed arrows point to the gaps between the numerology blocks and the channel boundaries. The left gap is labeled 'Guard band defined for numerology X when transmitted across full SAN channel BW'. The right gap is labeled 'Guard band defined for numerology Y when transmitted across full SAN channel BW'. + +**Figure 5.3.3-2: Guard band definition when transmitting multiple numerologies** + +NOTE: Figure 5.3.3-2 is not intended to imply the size of any guard between the two numerologies. Inter-numerology guard band within the carrier is implementation dependent. + +### 5.3.4 RB alignment + +For each *SAN channel bandwidth* and each numerology, *SAN transmission bandwidth configuration* must fulfil the minimum guard band requirement specified in clause 5.3.3. + +For each numerology, its common resource blocks are specified in clause 4.4.4.3 in TS 38.211 [5], and the starting point of its *transmission bandwidth configuration* on the common resource block grid for a given channel bandwidth is indicated by an offset to “Reference point A” in the unit of the numerology. + +For each numerology, all *UE transmission bandwidth configurations* indicated to UEs served by the SAN by higher layer parameter *carrierBandwidth* defined in TS 38.331 [6] shall fall within the *SAN transmission bandwidth configuration*. + +### 5.3.5 SAN channel bandwidth per operating band + +The requirements in this specification apply to the combination of *SAN channel bandwidths*, SCS and *operating bands* shown in table 5.3.5-1 for FR1. The *transmission bandwidth configuration* in table 5.3.2-1 shall be supported for each of the *SAN channel bandwidths* within the SAN capability. The *SAN channel bandwidths* are specified for both the Tx and Rx path. + +**Table 5.3.5-1: SAN channel bandwidths and SCS per operating band in FR1** + +| SAN Operating Band | SCS (kHz) | SAN channel bandwidth (MHz) | | | | | +|--------------------|-----------|-----------------------------|----|----|----|--------------| +| | | 5 | 10 | 15 | 20 | 30
(NOTE) | +| n256 | 15 | 5 | 10 | 15 | 20 | | +| | 30 | | 10 | 15 | 20 | | +| | 60 | | 10 | 15 | 20 | | +| n255 | 15 | 5 | 10 | 15 | 20 | | +| | 30 | | 10 | 15 | 20 | | +| | 60 | | 10 | 15 | 20 | | +| n254 | 15 | 5 | 10 | 15 | | | +| | 30 | | 10 | 15 | | | +| | 60 | | 10 | 15 | | | + +NOTE: Deployment of 30 MHz channel bandwidth for NTN SAN needs to be preceded by introduction of all applicable Tx RF, Rx RF, and demodulation requirements. + +## 5.4 Channel arrangement + +### 5.4.1 Channel spacing + +#### 5.4.1.1 Channel spacing for adjacent carriers + +The spacing between carriers will depend on the deployment scenario, the size of the frequency block available and the *SAN channel bandwidths*. The nominal channel spacing between two adjacent SAN carriers is defined as following: + +- For SAN FR1 *operating bands* with 100 kHz channel raster, + +$$\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 *SAN channel bandwidths* of the two respective SAN carriers. The channel spacing can be adjusted depending on the channel raster to optimize performance in a particular deployment scenario. + +### 5.4.2 Channel raster + +#### 5.4.2.1 NR-ARFCN and channel raster + +The global frequency raster defines a set of *RF reference frequencies* $F_{\text{REF}}$ . The *RF reference frequency* is used in signalling to identify the position of RF channels, SS blocks and other elements. The global frequency raster is defined for all frequencies from 0 to 100 GHz. The granularity of the global frequency raster is $\Delta F_{\text{Global}}$ . + +*RF reference frequencies* are designated by an NR Absolute Radio Frequency Channel Number (NR-ARFCN) in the range [0...3279165] on the global frequency raster. The relation between the NR-ARFCN and the *RF reference frequency* $F_{\text{REF}}$ in MHz is given by the following equation, where $F_{\text{REF-Offs}}$ and $N_{\text{Ref-Offs}}$ are given in table 5.4.2.1-1 and $N_{\text{REF}}$ is the NR-ARFCN. + +$$F_{\text{REF}} = F_{\text{REF-Offs}} + \Delta F_{\text{Global}} (N_{\text{REF}} - N_{\text{REF-Offs}})$$ + +**Table 5.4.2.1-1: NR-ARFCN parameters for the global frequency raster** + +| Range of frequencies (MHz) | $\Delta F_{\text{Global}}$ (kHz) | $F_{\text{REF-Offs}}$ (MHz) | $N_{\text{REF-Offs}}$ | Range of $N_{\text{REF}}$ | +|----------------------------|----------------------------------|-----------------------------|-----------------------|---------------------------| +| 0 – 3000 | 5 | 0 | 0 | 0 – 599999 | + +The *channel raster* defines a subset of *RF reference frequencies* that can be used to identify the RF channel position in the uplink and downlink. The *RF reference frequency* for an RF channel maps to a resource element on the carrier. For each *operating band*, a subset of frequencies from the global frequency raster are applicable for that band and forms a channel raster with a granularity $\Delta F_{\text{Raster}}$ , which may be equal to or larger than $\Delta F_{\text{Global}}$ . + +The mapping between the *channel raster* and corresponding resource element is given in clause 5.4.2.2. The applicable entries for each *operating band* are defined in clause 5.4.2.3. + +#### 5.4.2.2 Channel raster to resource element mapping + +The mapping between the *RF reference frequency* on the channel raster and the corresponding resource element is given in table 5.4.2.2-1 and can be used to identify the RF channel position. The mapping depends on the total number of RBs that are allocated in the channel and applies to both UL and DL. The mapping must apply to at least one numerology supported by the SAN. + +**Table 5.4.2.2-1: Channel Raster to Resource Element Mapping** + +| | $N_{RB} \bmod 2 = 0$ | $N_{RB} \bmod 2 = 1$ | +|------------------------------------------|---------------------------------------------------------|---------------------------------------------------------| +| Resource element index $k$ | 0 | 6 | +| Physical resource block number $n_{PRB}$ | $n_{PRB} = \left\lfloor \frac{N_{RB}}{2} \right\rfloor$ | $n_{PRB} = \left\lfloor \frac{N_{RB}}{2} \right\rfloor$ | + +$k$ , $n_{PRB}$ and $N_{RB}$ are as defined in TS 38.211 [5]. + +#### 5.4.2.3 Channel raster entries for each *operating band* + +The RF channel positions on the channel raster in each SAN *operating band* are given through the applicable NR-ARFCN in table 5.4.2.3-1 for FR1, using the channel raster to resource element mapping in clause 5.4.2.2. + +For SAN *operating bands* with 100 kHz channel raster, $\Delta F_{Raster} = 20 \times \Delta F_{Global}$ . In this case, every 20th NR-ARFCN within the *operating band* are applicable for the channel raster within the *operating band* and the step size for the channel raster in table 5.4.2.3-1 is given as <20>. + +**Table 5.4.2.3-1: Applicable NR-ARFCN per *operating band* in FR1** + +| SAN operating band | $\Delta F_{Raster}$ (kHz) | Uplink range of $N_{REF}$
(First – – Last) | Downlink range of $N_{REF}$
(First – – Last) | +|---------------------------|---------------------------|-----------------------------------------------------------|-------------------------------------------------------------| +| n256 | 100 | 396000 – <20> – 402000 | 434000 – <20> – 440000 | +| n255 | 100 | 325300 – <20> – 332100 | 305000 – <20> – 311800 | +| n254 | 100 | 322000 – <20> – 325300 | 496700 – <20> – 500000 | + +For SAN *operating bands* with 100 kHz channel raster, *enhanced channel raster* is defined with $\Delta F_{Raster} = 2 \times \Delta F_{Global}$ . In this case every 2nd NR-ARFCN within the *operating band* are applicable for the channel raster within the *operating band* and the step size for the channel raster in table 5.4.2.3-1 is <2>. + +**Table 5.4.2.3-2: Applicable NR-ARFCN per *operating band* for enhanced channel raster** + +| SAN operating band | $\Delta F_{Raster}$ (kHz) | Uplink range of $N_{REF}$
(First – – Last) | Downlink range of $N_{REF}$
(First – – Last) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------------------------------------------------|-------------------------------------------------------------| +| n256 | 10 | 396000 – <2> – 402000 | 434000 – <2> – 440000 | +| n255 | 10 | 325300 – <2> – 332100 | 305000 – <2> – 311800 | +| NOTE 1: The channel numbers that designate carrier frequencies so close to the operating band edges that the carrier extends beyond the operating band edge shall not be used. These channel numbers shall also be such that the minimum guard band for each channel bandwidth and SCS specified in Table 5.3.3-1 are met for carriers located at the upper or lower edge of an operating band. | | | | + +### 5.4.3 Synchronization raster + +#### 5.4.3.1 Synchronization raster and numbering + +The synchronization raster indicates the frequency positions of the synchronization block that can be used by the UE for system acquisition when explicit signalling of the synchronization block position is not present. + +A global synchronization raster is defined for all frequencies. The frequency position of the SS block is defined as $SS_{REF}$ with corresponding number GSCN. The parameters defining the $SS_{REF}$ and GSCN for all the frequency ranges are in table 5.4.3.1-1. + +The resource element corresponding to the SS block reference frequency $SS_{REF}$ is given in clause 5.4.3.2. The synchronization raster and the subcarrier spacing of the synchronization block are defined separately for each band. + +The synchronization raster and the corresponding SS block do not cover all possible RF channel bandwidth and locations on *enhanced channel raster*. + +**Table 5.4.3.1-1: GSCN parameters for the global frequency raster** + +| Range of frequencies (MHz) | SS block frequency position $SS_{REF}$ | GSCN | Range of GSCN | +|---------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|----------------|---------------| +| 0 – 3000 | $N \cdot 1200 \text{ kHz} + M \cdot 50 \text{ kHz}$ ,
$N = 1:2499$ , $M \in \{1,3,5\}$ (Note) | $3N + (M-3)/2$ | 2 – 7498 | +| NOTE: The default value for operating bands which only support SCS spaced channel raster(s) is $M=3$ . | | | | + +#### 5.4.3.2 Synchronization raster to synchronization block resource element mapping + +The mapping between the synchronization raster and the corresponding resource element of the SS block is given in table 5.4.3.2-1. + +**Table 5.4.3.2-1: Synchronization Raster to SS block Resource Element Mapping** + +| | | +|----------------------------|-----| +| Resource element index $k$ | 120 | +|----------------------------|-----| + +$k$ is the subcarrier number of SS/PBCH block defined in TS 38.211 clause 7.4.3.1 [5]. + +#### 5.4.3.3 Synchronization raster entries for each operating band + +The synchronization raster for each band is given in table 5.4.3.3-1. The distance between applicable GSCN entries is given by the indicated in table 5.4.3.3-1 for FR1. + +**Table 5.4.3.3-1: Applicable SS raster entries per operating band (FR1)** + +| SAN operating band | SS Block SCS | SS Block pattern (NOTE) | Range of GSCN (First – – Last) | +|-------------------------------------------------------------------|--------------|-------------------------|--------------------------------------------| +| n256 | 15 kHz | Case A | 5429 – <1> – 5494 | +| n255 | 15 kHz | Case A | 3818 – <1> – 3892 | +| | 30 kHz | Case B | 3824 – <1> – 3886 | +| n254 | 15 kHz | Case A | 6215 – <1> – 6244 | +| | 30 kHz | Case C | 6218 – <1> – 6241 | +| NOTE: SS Block pattern is defined in clause 4.1 in TS 38.213 [7]. | | | | + +# 6 Conducted transmitter characteristics + +## 6.1 General + +Unless otherwise stated, the conducted transmitter characteristics are specified at the *TAB connector* for *SAN type 1-H*, with a full complement of transceiver units for the configuration in normal operating conditions. + +## 6.2 Satellite Access Node output power + +### 6.2.1 General + +The SAN conducted output power requirement applies at *TAB connector* for *SAN type 1-H*. + +The *rated carrier output power* of the *SAN type 1-H* shall be as specified in table 6.2.1-2. + +**Table 6.2.1-2: SAN type 1-H rated output power limits for SAN classes** + +| SAN class | Prated,c,sys (NOTE) | Prated,c,TABC (NOTE) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|----------------------------------------| +| SAN GEO class | Prated,c,sys,GEO | Prated,c,TABC,GEO | +| SAN LEO class | Prated,c,sys,LEO | Prated,c,TABC,LEO | +| NOTE: P rated,c,sys or P rated,c,TABC of SAN shall be based on manufacturer declaration and comply with regulation requirement. | | | + +### 6.2.2 Minimum requirement for SAN type 1-H + +In normal conditions, Pmax,c,TABC shall remain within +2 dB and -2 dB of the *rated carrier output power* Prated,c,TABC for each *TAB connector* as declared by the manufacturer. + +## 6.3 Output power dynamics + +### 6.3.1 General + +Transmitted signal quality (as specified in clause 6.5) shall be maintained for the output power dynamics requirements of this clause. + +Power control is used to limit the interference level. + +### 6.3.2 RE power control dynamic range + +#### 6.3.2.1 General + +The RE power control dynamic range is the difference between the power of an RE and the average RE power for a SAN at maximum output power (Pmax,c,TABC) for a specified reference condition. + +For SAN type 1-H this requirement shall apply at each *TAB connector* supporting transmission in the *operating band*. + +#### 6.3.2.2 Minimum requirement for SAN type 1-H + +RE power control dynamic range requirement is specified in table 6.3.2.2-1. + +**Table 6.3.2.2-1: 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 | +| 16QAM (PDSCH) | -3 | +3 | +| 64QAM (PDSCH) (NOTE 2) | 0 | 0 | +| NOTE 1: The output power per carrier shall always be less or equal to the maximum output power of the satellite access node.
NOTE 2: This requirement is optional, subject to manufacturer declaration. | | | + +### 6.3.3 Total power dynamic range + +#### 6.3.3.1 General + +The SAN total power dynamic range is the difference between the maximum and the minimum transmit power of an OFDM symbol for a specified reference condition. + +For *SAN type 1-H* this requirement shall apply at each *TAB connector* supporting transmission in the *operating band*. + +NOTE 1: The upper limit of the dynamic range is the OFDM symbol power for a SAN when transmitting on all RBs at maximum output power. The lower limit of the total power dynamic range is the average power for single RB transmission. The OFDM symbol shall carry PDSCH and not contain RS or SSB. + +#### 6.3.3.2 Minimum requirement for *SAN type 1-H* + +The downlink (DL) total power dynamic range for each SAN carrier shall be larger than or equal to the level in table 6.3.3.2-1. + +**Table 6.3.3.2-1: Total power dynamic range** + +| SAN channel bandwidth (MHz) | Total power dynamic range (dB) | | | +|-----------------------------|--------------------------------|------------|------------| +| | 15 kHz SCS | 30 kHz SCS | 60 kHz SCS | +| 5 | 13.9 | 10.4 | N/A | +| 10 | 17.1 | 13.8 | 10.4 | +| 15 | 18.9 | 15.7 | 12.5 | +| 20 | 20.2 | 17 | 13.8 | + +## 6.4 Transmit ON/OFF power + +The requirement is not applicable in this version of the specification. + +## 6.5 Transmitted signal quality + +### 6.5.1 Frequency error + +#### 6.5.1.1 General + +Frequency error is the measure of the difference between the actual SAN transmit frequency and the assigned frequency. The same source shall be used for RF frequency and data clock generation. + +For *SAN type 1-H* this requirement shall be applied at each *TAB connector* supporting transmission in the *operating band*. + +#### 6.5.1.2 Minimum requirement for *SAN type 1-H* + +The modulated carrier frequency of each carrier configured by the SAN shall be accurate to within 0.05 ppm observed over 1 ms. + +### 6.5.2 Modulation quality + +#### 6.5.2.1 General + +Modulation quality is defined by the difference between the measured carrier signal and an ideal signal. Modulation quality can e.g. be expressed as Error Vector Magnitude (EVM). The Error Vector Magnitude is a measure of the difference between the ideal symbols and the measured symbols after the equalization. This difference is called the error vector. Details about how the EVM is determined are specified in Annex B. + +For *SAN type 1-H* this requirement shall be applied at each *TAB connector* supporting transmission in the *operating band*. + +#### 6.5.2.2 Minimum Requirement for *SAN type 1-H* + +The EVM levels of each carrier for different modulation schemes on PDSCH outlined in table 6.5.2.2-1 shall be met using the frame structure described in clause 6.5.2.3. + +**Table 6.5.2.2-1: EVM requirements for SAN type 1-H carrier** + +| Modulation scheme for PDSCH | Required EVM | +|-----------------------------------------------------------------------------------|--------------| +| QPSK | 17.5 % | +| 16QAM | 12.5 % | +| 64QAM (NOTE) | 8 % | +| NOTE: EVM requirement for 64QAM is optional, subject to manufacturer declaration. | | + +#### 6.5.2.3 EVM frame structure for measurement + +EVM shall be evaluated for each carrier over all allocated resource blocks and downlink subframes. Different modulation schemes listed in table 6.5.2.2-1 shall be considered for rank 1. + +For all bandwidths, the EVM measurement shall be performed for each carrier over all allocated resource blocks and downlink subframes within 10 ms measurement periods. The boundaries of the EVM measurement periods need not be aligned with radio frame boundaries. + +### 6.5.3 Time alignment error + +The requirement is not applicable in this version of the specification. + +## 6.6 Unwanted emissions + +### 6.6.1 General + +Unwanted emissions consist of out-of-band emissions and spurious emissions according to ITU definitions [2]. In ITU terminology, out of band emissions are unwanted emissions immediately outside the *SAN 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 SAN transmitter is specified both in terms of Adjacent Channel Leakage power Ratio (ACLR) and out-of-band emissions (OOBE). There is in addition a requirement for occupied bandwidth. + +**Table 6.6.1-1: void** + +For *SAN type 1-H* the unwanted emission requirements are applied to sum of power over all *TAB connectors* for all the configurations supported by the SAN, except for occupied bandwidth in subclause 6.6.2. + +### 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 [8]. + +The value of $\beta/2$ shall be taken as 0.5%. + +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. + +For *SAN type 1-H* this requirement shall be applied at each *TAB connector* supporting transmission in the *operating band*. + +#### 6.6.2.2 Minimum requirement for SAN type 1-H + +The occupied bandwidth for each carrier shall be less than the *SAN channel bandwidth*. + +### 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. + +The requirements shall apply outside the *SAN 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. + +### 6.6.3.2 Minimum requirement for SAN type 1-H + +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. + +The ACLR shall be higher than the value specified in Table 6.6.3.2-1/2. + +**Table 6.6.3.2-1: SAN ACLR limit for GEO class** + +| SAN channel bandwidth of lowest/highest carrier transmitted $BW_{Channel}$ (MHz) | SAN 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 (dB) | +|----------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|-----------------| +| 5, 10, 15, 20 | $BW_{Channel}$ | NR of same BW (NOTE 2) | Square ( $BW_{Config}$ ) (NOTE 1) | 14 | +| | $2 \times BW_{Channel}$ | NR of same BW (NOTE 2) | Square ( $BW_{Config}$ ) (NOTE 1) | 14 | + +NOTE 1: $BW_{Channel}$ and $BW_{Config}$ are the *SAN channel bandwidth* and *transmission bandwidth configuration* of the lowest/highest carrier transmitted on the assigned channel frequency. + +NOTE 2: With SCS that provides largest transmission bandwidth configuration ( $BW_{Config}$ ). + +**Table 6.6.3.2-2: SAN ACLR limit for LEO class** + +| SAN channel bandwidth of lowest/highest carrier transmitted $BW_{Channel}$ (MHz) | SAN 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 (dB) | +|----------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|-----------------| +| 5, 10, 15, 20 | $BW_{Channel}$ | NR of same BW (NOTE 2) | Square ( $BW_{Config}$ ) (NOTE 1) | 24 | +| | $2 \times BW_{Channel}$ | NR of same BW (NOTE 2) | Square ( $BW_{Config}$ ) (NOTE 1) | 24 | + +NOTE 1: $BW_{Channel}$ and $BW_{Config}$ are the *SAN channel bandwidth* and *transmission bandwidth configuration* of the lowest/highest carrier transmitted on the assigned channel frequency. + +NOTE 2: With SCS that provides largest transmission bandwidth configuration ( $BW_{Config}$ ). + +## 6.6.4 Out-of-band emissions + +### 6.6.4.1 General + +Unless otherwise stated, the out-of-band emission (OOBE) limits for SAN in FR1 are defined from $BW_{SAN}$ channel edge up to frequencies separated from the $BW_{SAN}$ channel edge by 200% of the *necessary bandwidth*, where the *necessary bandwidth* is $BW_{SAN}$ . + +The requirements shall apply whatever the type of transmitter considered and for all transmission modes foreseen by the manufacturer's specification. + +*Basic limits* are specified in the tables below, where: + +- $\Delta f$ is the separation between the $BW_{SAN}$ *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. +- $\Delta_{Sat\_Class}[dB]$ is the *SAN class parameter* in dB identified to characterize different SAN classes. + +### 6.6.4.2 Minimum requirements for SAN type 1-H + +For SAN operating in Bands n256, n255, n254, the requirements are specified in table 6.6.4.2-1 for GEO and LEO class respectively, in line with Annex 5 of ITU recommendation SM.1541-6 [9]. + +The SAN out-of-band emissions(OOBE) requirements for GEO and LEO classes are therefore defined as described in Table 6.6.4.2-1 below. + +**Table 6.6.4.2-1: SAN LEO and GEO Classes OOBE basic limits** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits (dBm) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 2 \times BW_{SAN}$ | $0.002 \text{ MHz} \leq f\_offset < 2 \times BW_{SAN} + 0.002 \text{ MHz}$ | $\max \left( \begin{aligned} &SE \text{ limit}, P_{\text{rated,t,sys}} - 10\log_{10}(BW_{SAN}) - 24 - \Delta_{Sat\_Class}[dB] \\ &- 40 \times \log_{10} \left( \frac{f\_offset - 0.002}{BW_{SAN}} \times 2 + 1 \right) \end{aligned} \right) \text{ dBm}$ | 4 kHz | + +NOTE 1: $BW_{SAN}$ is in the unit of MHz. +NOTE 2: SE limit is spurious emission limit specified in spurious emission clause 6.6.5. +NOTE 3: PSD attenuation as in ITU-R SM.1541-6 [9], Annex 5 OoB domain emission limits for space services. +NOTE 4: $\Delta_{Sat\_Class}[dB]=0 \text{ dB}$ for GEO class and $\Delta_{Sat\_Class}[dB]=3 \text{ dB}$ for LEO class. + +## 6.6.5 Transmitter spurious emissions + +### 6.6.5.1 General + +The transmitter spurious emission limits shall apply from 30 MHz to the fifth harmonic of the upper frequency edge of the DL operating band, excluding the *SAN transponder bandwidth* $BW_{SAN}$ and the frequency range where the out-of-band emissions apply. For some *operating bands*, the upper 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 [2]. + +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 specification. + +Unless otherwise stated, all requirements are measured as mean power (RMS). + +## 6.6.5.2 Minimum requirements for SAN type 1-H + +### 6.6.5.2.1 General transmitter spurious emissions requirements + +The requirements in table 6.6.5.2.1-1 shall apply. The application of those limits shall be the same as for out-of-band emissions in clause 6.6.4. + +**Table 6.6.5.2.1-1: General SAN transmitter spurious emission limits in FR1** + +| Spurious frequency range | $P_{\text{rated,c,sys}}$ (dBm) | Basic limit (dBm) | Measurement bandwidth (kHz) | Notes | +|----------------------------------------------------------------------------------------|--------------------------------|----------------------------------------|-----------------------------|------------------------| +| 30 MHz – 5 th harmonic of the upper frequency edge of the DL operating band | $\leq 47$ | -13 | 4 | NOTE 1, NOTE 2, NOTE 3 | +| | $> 47$ | $P_{\text{rated,c,sys}} - 60\text{dB}$ | | | + +NOTE 1: Measurement bandwidths as in ITU-R SM.329 [2], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [2], s2.5 table 1. +NOTE 3: The lower frequency limit is replaced by 0.7 times the waveguide cut-off frequency, according to ITU-R SM.329 [2], for systems having an integral antenna incorporating a waveguide section, or with an antenna connection in such form, and of unperturbed length equal to at least twice the cut-off. + +### 6.6.5.2.2 Protection of the own Satellite Access Node receiver + +This requirement shall be applied for NR FDD operation in order to prevent the receivers of the SAN being de-sensitized by emissions from its own SAN transmitter. It is measured at the *TAB connector* for SAN type 1-H for any type of SAN which has common or separate Tx/Rx *TAB connectors*. + +The spurious emission *basic limits* are provided in table 6.6.5.2.2-1. + +**Table 6.6.5.2.2-1: SAN spurious emissions *basic limits* for protection of the SAN receiver** + +| Frequency range | Basic limits | Measurement bandwidth | +|------------------------------------------|--------------|-----------------------| +| $F_{\text{UL,low}} - F_{\text{UL,high}}$ | -96 dBm | 100 kHz | + +### 6.6.5.2.3 Additional spurious emissions requirements + +The additional spurious emissions requirement is not applicable for SAN. + +### 6.6.5.2.4 Co-location with other Satellite Access Nodes + +The co-location requirement is not applicable for SAN. + +## 6.7 Transmitter intermodulation + +The requirement is not applicable in this version of the specification. + +## 7 Conducted receiver characteristics + +### 7.1 General + +Conducted receiver characteristics are specified at the *TAB connector* for *SAN type 1-H*, with full complement of transceivers for the configuration in normal operating condition. + +Unless otherwise stated, the following arrangements apply for conducted receiver characteristics requirements in clause 7: + +- Requirements shall be met for any transmitter setting. +- The requirements shall be met with the transmitter unit(s) ON. +- Throughput requirements do not assume HARQ retransmissions. +- When SAN is configured to receive multiple carriers, all the throughput requirements are applicable for each received carrier. +- For ACS and blocking characteristics, the negative offsets of the interfering signal apply relative to the lower *SAN RF Bandwidth* edge or *sub-block* edge inside a *sub-block gap*, and the positive offsets of the interfering signal apply relative to the upper *SAN RF Bandwidth* edge or *sub-block* edge inside a *sub-block gap*. + +NOTE: In normal operating condition the SAN is configured to transmit and receive at the same time. + +### 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* for *SAN type 1-H* at which a throughput requirement shall be met for a specified reference measurement channel. + +#### 7.2.2 Minimum requirements for *SAN type 1-H* + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.1 with parameters specified in table 7.2.2-1 and 7.2.2-2 for *SAN type 1-H* in all operating band in FR1. + +**Table 7.2.2-1: SAN GEO class reference sensitivity levels** + +| SAN channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel (NOTE) | Reference sensitivity power level, $P_{\text{REFSENS}}$ (dBm) | +|-----------------------------|---------------------------|--------------------------------------|---------------------------------------------------------------| +| 5, 10, 15 | 15 | G-FR1-A1-1 | -99.3 | +| 10, 15 | 30 | G-FR1-A1-2 | -99.4 | +| 10, 15 | 60 | G-FR1-A1-3 | -96.5 | +| 20 | 15 | G-FR1-A1-4 | -92.9 | +| 20 | 30 | G-FR1-A1-5 | -93.2 | +| 20 | 60 | G-FR1-A1-6 | -93.3 | + +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 *SAN channel bandwidth*. + +Table 7.2.2-2: SAN LEO class reference sensitivity levels + +| SAN channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel (NOTE) | Reference sensitivity power level, $P_{\text{REFSENS}}$ (dBm) | +|-----------------------------|---------------------------|--------------------------------------|---------------------------------------------------------------| +| 5, 10, 15 | 15 | G-FR1-A1-1 | -102.4 | +| 10, 15 | 30 | G-FR1-A1-2 | -102.5 | +| 10, 15 | 60 | G-FR1-A1-3 | -99.6 | +| 20 | 15 | G-FR1-A1-4 | -96.0 | +| 20 | 30 | G-FR1-A1-5 | -96.3 | +| 20 | 60 | G-FR1-A1-6 | -96.4 | + +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 SAN channel bandwidth. + +## 7.3 Dynamic range + +### 7.3.1 General + +The dynamic range is specified as a measure of the capability of the receiver to receive a wanted signal in the presence of an interfering signal at the *TAB connector* for *SAN type 1-H* inside the received SAN channel bandwidth. In this condition, a throughput requirement shall be met for a specified reference measurement channel. The interfering signal for the dynamic range requirement is an AWGN signal. + +### 7.3.2 Minimum requirements for *SAN type 1-H* + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.2 with parameters specified in table 7.3.2-1 for LEO. + +Table 7.3.2-1: SAN LEO class dynamic range + +| SAN channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / $BW_{\text{Config}}$ | Type of interfering signal | +|-----------------------------|--------------------------|-------------------------------|--------------------------------|------------------------------------------------------------|----------------------------| +| 5 | 15 | G-FR1-A2-1 | -76.4 | -88.2 | AWGN | +| | 30 | G-FR1-A2-2 | -77.1 | | | +| 10 | 15 | G-FR1-A2-1 | -76.4 | -85.0 | AWGN | +| | 30 | G-FR1-A2-2 | -77.1 | | | +| | 60 | G-FR1-A2-3 | -74.1 | | | +| 15 | 15 | G-FR1-A2-1 | -76.4 | -83.2 | AWGN | +| | 30 | G-FR1-A2-2 | -77.1 | | | +| | 60 | G-FR1-A2-3 | -74.1 | | | +| 20 | 15 | G-FR1-A2-4 | -70.2 | -81.9 | AWGN | +| | 30 | G-FR1-A2-5 | -70.2 | | | +| | 60 | G-FR1-A2-6 | -70.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 SAN channel bandwidth. + +## 7.4 In-band selectivity and blocking + +### 7.4.1 Adjacent Channel Selectivity (ACS) + +#### 7.4.1.1 General + +Adjacent channel selectivity (ACS) is a measure of the receiver's ability to receive a wanted signal at its assigned channel frequency at *TAB connector* for *SAN type 1-H* in the presence of an adjacent channel signal with a specified center frequency offset of the interfering signal to the band edge of a victim system. + +#### 7.4.1.2 Minimum requirements for *SAN type 1-H* + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel. + +For SAN, the wanted and the interfering signal coupled to the *SAN type 1-H TAB connector* are specified in table 7.4.1.2-1 and the frequency offset between the wanted and interfering signal in table 7.4.1.2-2 for ACS. The reference measurement channel for the wanted signal is identified in table 7.2.2-1 and 7.2.2-2 for each *SAN channel bandwidth* in any operating band and further specified in annex A.1. The characteristics of the interfering signal is further specified in annex C. + +The ACS requirement is applicable outside the *SAN RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *SAN RF Bandwidth* edges or *Radio Bandwidth* edges. + +Minimum conducted requirement is defined at the *TAB connector* for *SAN type 1-H*. + +**Table 7.4.1.2-1: Satellite Access Node ACS requirement** + +| SAN channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|--------------------------------------------| +| 5, 10, 15, 20
(NOTE 1) | $P_{REFSENS} + 6$ dB
(NOTE 2) | SAN GEO class: -57
SAN LEO class: -60 | +| NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the SAN for that bandwidth.
NOTE 2: $P_{REFSENS}$ depends on the SAN channel bandwidth as specified in table 7.2.2-1 and 7.2.2-2. | | | + +**Table 7.4.1.2-2: Satellite Access Node ACS interferer frequency offset values** + +| SAN channel bandwidth of the lowest/highest carrier received (MHz) | Interfering signal center frequency offset from the lower/upper SAN RF Bandwidth edge (MHz) | Type of interfering signal | +|---------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------------------------------------------| +| 5 | $\pm 2.5025$ | 5 MHz CP-OFDM NR signal
15 kHz SCS, 25 RBs | +| 10 | $\pm 2.5075$ | | +| 15 | $\pm 2.5125$ | | +| 20 | $\pm 2.5025$ | | + +### 7.4.2 In-band blocking + +The requirement is not applicable in this version of the specification. + +## 7.5 Out-of-band blocking + +### 7.5.1 General + +The out-of-band blocking characteristics is a measure of the receiver ability to receive a wanted signal at its assigned channel at the *TAB connector* for *SAN type 1-H* in the presence of an unwanted interferer out of the *operating band*, which is a CW signal for out-of-band blocking. + +### 7.5.2 Minimum requirements for *SAN type 1-H* + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel, with a wanted and an interfering signal coupled to *SAN type 1-H TAB connector* using the parameters in table 7.5.2-1. + +The reference measurement channel for the wanted signal is identified in clause 7.2.2 for each *SAN channel bandwidth* and further specified in annex A.1. + +The out-of-band blocking requirement apply 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 SAN. The $\Delta f_{OOB}$ for *SAN type 1-H* is defined in table 7.5.2-2. + +Minimum conducted requirement is defined at the *TAB connector* for *SAN type 1-H*. + +**Table 7.5.2-1: Out-of-band blocking requirement for NR** + +| Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|--------------------------------------------------------------------------|-------------------------------------|----------------------------| +| P REFSENS +6 dB
(NOTE) | -44 | CW carrier | +| NOTE: P REFSENS depends on the SAN channel bandwidth . | | | + +**Table 7.5.2-2: $\Delta f_{OOB}$ offset for NR *operating bands*** + +| SAN type | Operating band characteristics | $\Delta f_{OOB}$ (MHz) | +|---------------------|---------------------------------------|------------------------| +| SAN type 1-H | $F_{UL,high} - F_{UL,low} < 100$ MHz | 20 | + +## 7.6 Receiver spurious emissions + +The requirement is not applicable in this version of the specification. + +### 7.6.1 Void + +### 7.6.2 Void + +## 7.7 Receiver intermodulation + +The requirement is not applicable in this version of the specification. + +## 7.8 In-channel selectivity + +### 7.8.1 General + +In-channel selectivity (ICS) is a measure of the receiver ability to receive a wanted signal at its assigned resource block locations at *TAB connector* for *SAN type 1-H* 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 interfering signal shall be an NR signal which is time aligned with the wanted signal. + +### 7.8.2 Minimum requirements for *SAN type 1-H* + +For *SAN type 1-H*, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.1 with parameters specified in table 7.8.2-1 for GEO SAN, in table 7.8.2-2 for LEO SAN. The characteristics of the interfering signal is further specified in annex C. + +**Table 7.8.2-1: SAN GEO class ICS requirement** + +| SAN channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|------------------------------------|---------------------------------|--------------------------------------|---------------------------------------|--------------------------------------------|------------------------------------------| +| 5 | 15 | G-FR1-A1-7 | -98.2 | -92.0 | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10,15,20 | 15 | G-FR1-A1-1 | -96.3 | -88.1 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 5 | 30 | G-FR1-A1-8 | -98.9 | -92.0 | DFT-s-OFDM NR signal, 30 kHz SCS, 5 RBs | +| 10,15,20 | 30 | G-FR1-A1-2 | -96.4 | -89.0 | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 10,15,20 | 60 | G-FR1-A1-9 | -95.8 | -89.0 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | + +NOTE: Wanted and interfering signal are placed adjacently around $F_c$ , where the $F_c$ is defined for *SAN channel bandwidth* of the wanted signal according to the table 5.4.2.2-1. The aggregated wanted and interferer signal shall be centred in the *SAN channel bandwidth* of the wanted signal. + +Table 7.8.2-2: SAN LEO class ICS requirement + +| SAN channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|-----------------------------|--------------------------|-------------------------------|--------------------------------|-------------------------------------|------------------------------------------| +| 5 | 15 | G-FR1-A1-7 | -101.3 | -83.1 | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10,15,20 | 15 | G-FR1-A1-1 | -99.4 | -79.2 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 5 | 30 | G-FR1-A1-8 | -102.0 | -83.1 | DFT-s-OFDM NR signal, 30 kHz SCS, 5 RBs | +| 10,15,20 | 30 | G-FR1-A1-2 | -99.5 | -80.1 | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 10,15,20 | 60 | G-FR1-A1-9 | -98.9 | -80.1 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | + +NOTE: Wanted and interfering signal are placed adjacently around $F_c$ , where the $F_c$ is defined for SAN channel bandwidth of the wanted signal according to the table 5.4.2.2-1. The aggregated wanted and interferer signal shall be centred in the SAN channel bandwidth of the wanted signal. + +## 8 Conducted performance requirements + +### 8.1 General + +Conducted performance requirements specify the ability of the SAN type 1-H to correctly transmit and receive signals in various conditions and configurations. Conducted performance requirements are specified at the TAB connector(s) (for SAN type 1-H). + +Conducted performance requirements for the SAN are specified for the fixed reference channels defined in annex A and for the propagation conditions defined in Recommendation ITU-R P.618 (Propagation data and prediction methods required for the design of Earth-space telecommunication systems). + +Unless stated otherwise, performance requirements apply for a single carrier only. Performance requirements for a SAN 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 (for SAN type 1-H) in the operating band turned ON. + +NOTE: In normal operating conditions, TAB connectors (for SAN type 1-H) 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.181 [3]. + +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 power in the slot on a single on a single TAB connector (for SAN type 1-H). + +$N$ is the noise density integrated in a bandwidth corresponding to the transmission bandwidth over the same duration where signal energy exists on a single TAB connector (for SAN type 1-H). + +## 8.2 Performance requirements for PUSCH + +### 8.2.1 Requirements for PUSCH with transform precoding disabled + +#### 8.2.1.1 General + +The performance requirement of PUSCH is determined by a minimum required throughput for a given SNR. The required throughput is expressed as a fraction of maximum throughput for the FRCs listed in annex A. The performance requirements assume HARQ retransmissions. + +**Table: 8.2.1.1-1 Test parameters for testing PUSCH** + +| Parameter | | Value | +|-------------------------------------------|-------------------------------------------|--------------------------------| +| Transform precoding | | Disabled | +| HARQ | Maximum number of HARQ transmissions | 4 | +| | RV sequence | 0, 2, 3, 1 | +| DM-RS | DM-RS configuration type | 1 | +| | DM-RS duration | single-symbol DM-RS | +| | Additional DM-RS position | pos1 | +| | Number of DM-RS CDM group(s) without data | 2 | +| | Ratio of PUSCH EPRE to DM-RS EPRE | -3 dB | +| | DM-RS port | {0} | +| | DM-RS sequence generation | $N_{ID}^0=0, n_{scID}=0$ | +| Time domain resource assignment | PUSCH mapping type | A, B | +| | Start symbol | 0 | +| | Allocation length | 14 | +| Frequency domain resource assignment | RB assignment | Full applicable test bandwidth | +| | Frequency hopping | Disabled | +| Code block group based PUSCH transmission | | Disabled | + +#### 8.2.1.2 Minimum requirements + +The throughput shall be equal to or larger than the fraction of maximum throughput for the FRCs stated in tables 8.2.1.2-1 to 8.2.1.2-4 at the given SNR. FRCs are defined in annex A. + +**Table 8.2.1.2-1: Minimum requirements for PUSCH with 70% of maximum throughput, Type A, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-1 | pos1 | 3.2 | +| | | Normal | NTN-TDLC5-200 Low | 70 % | G-FR1-A3-1 | pos1 | 1.6 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-1 | pos1 | -0.7 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-1 | pos1 | -1.2 | + +**Table 8.2.1.2-2: Minimum requirements for PUSCH with 70% of maximum throughput, Type A, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-3 | pos1 | 2.9 | +| | | Normal | NTN-TDLC5-200 Low | 70 % | G-FR1-A3-3 | pos1 | 1.4 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-3 | pos1 | -1.0 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-3 | pos1 | -1.4 | + +**Table 8.2.1.2-3: Minimum requirements for PUSCH with 70% of maximum throughput, Type B, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-1 | pos1 | 3.3 | +| | | Normal | NTN-TDLC5-200 Low | 70 % | G-FR1-A3-1 | pos1 | 1.6 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-1 | pos1 | -0.6 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-1 | pos1 | -1.2 | + +**Table 8.2.1.2-4: Minimum requirements for PUSCH with 70% of maximum throughput, Type B, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-3 | pos1 | 2.9 | +| | | Normal | NTN-TDLC5-200 Low | 70 % | G-FR1-A3-3 | pos1 | 1.3 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-3 | pos1 | -1.0 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-3 | pos1 | -1.4 | + +## 8.2.2 Requirements for PUSCH with transform precoding enabled + +### 8.2.2.1 General + +The performance requirement of PUSCH is determined by a minimum required throughput for a given SNR. The required throughput is expressed as a fraction of maximum throughput for the FRCs listed in annex A. The performance requirements assume HARQ retransmissions. + +Table 8.2.2.1-1: Test parameters for testing PUSCH + +| Parameter | | Value | +|-------------------------------------------|-------------------------------------------|----------------------------------------------------------------| +| Transform precoding | | Enabled | +| HARQ | Maximum number of HARQ transmissions | 4 | +| | RV sequence | 0, 2, 3, 1 | +| DM-RS | DM-RS configuration type | 1 | +| | DM-RS duration | single-symbol DM-RS | +| | Additional DM-RS position | pos1 | +| | Number of DM-RS CDM group(s) without data | 2 | +| | Ratio of PUSCH EPRE to DM-RS EPRE | -3 dB | +| | DM-RS port | {0} | +| | DM-RS sequence generation | $N_{ID}^0=0$ , group hopping and sequence hopping are disabled | +| Time domain resource assignment | PUSCH mapping type | A, B | +| | Start symbol | 0 | +| | Allocation length | 14 | +| Frequency domain resource assignment | RB assignment | Full applicable test bandwidth | +| | Frequency hopping | Disabled | +| Code block group based PUSCH transmission | | Disabled | + +## 8.2.2.2 Minimum requirements + +The throughput shall be equal to or larger than the fraction of maximum throughput for the FRCs stated in tables 8.2.2.2-1 to 8.2.2.2-4 at the given SNR. FRCs are defined in annex A. + +Table 8.2.2.2-1: Minimum requirements for PUSCH with 70% of maximum throughput, PUSCH mapping Type A, 5 MHz channel bandwidth, 15 kHz SCS + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-1 | pos1 | 3.7 | +| | | Normal | NTN-TDLC5-200 Low | 70 % | G-FR1-A3-1 | pos1 | 1.6 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-1 | pos1 | -0.5 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-1 | pos1 | -1.2 | + +Table 8.2.2.2-2: Minimum requirements for PUSCH with 70% of maximum throughput, PUSCH mapping Type A, 10 MHz channel bandwidth, 30 kHz SCS + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-3 | pos1 | 3.5 | +| | | Normal | NTN-TDLC5-200 Low | 70 % | G-FR1-A3-3 | pos1 | 1.3 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-3 | pos1 | -0.7 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-3 | pos1 | -1.4 | + +**Table 8.2.2.2-3: Minimum requirements for PUSCH with 70% of maximum throughput, PUSCH mapping Type B, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-1 | pos1 | 3.7 | +| | | Normal | NTN-TDLC5-200 Low | 70 % | G-FR1-A3-1 | pos1 | 1.6 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-1 | pos1 | -0.5 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-1 | pos1 | -1.2 | + +**Table 8.2.2.2-4: Minimum requirements for PUSCH with 70% of maximum throughput, PUSCH mapping Type B, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-3 | pos1 | 3.5 | +| | | Normal | NTN-TDLC5-200 Low | 70 % | G-FR1-A3-3 | pos1 | 1.3 | +| | 2 | Normal | NTN-TDLA100-200 Low | 70 % | G-FR1-A3-3 | pos1 | -0.7 | +| | | Normal | NTN-TDLC5-200 Low | 70% | G-FR1-A3-3 | pos1 | -1.4 | + +## 8.2.3 Requirements for UL timing adjustment + +The performance requirement of UL timing adjustment is determined by a minimum required throughput for the moving UE at given SNR. The performance requirements assume HARQ retransmissions. + +In the tests for UL timing adjustment, two signals are configured, one being transmitted by a moving UE and the other being transmitted by a stationary UE. The transmission of SRS from UE is optional. FRC parameters in Table A.3-1 are applied for both UEs. The received power for both UEs is the same. The resource blocks allocated for both UEs are consecutive. + +Table 8.2.3-1 Test parameters for testing UL timing adjustment + +| Parameter | | Value | +|-------------------------------------------|----------------------------------------------------|--------------------------------------------------------------------------------------------| +| Transform precoding | | Disabled | +| HARQ | Maximum number of HARQ transmissions | 4 | +| | RV sequence | 0, 2, 3, 1 | +| DM-RS | DM-RS configuration type | 1 | +| | DM-RS duration | single-symbol DM-RS | +| | Additional DM-RS position | pos1 | +| | Number of DM-RS CDM group(s) without data | 2 | +| | Ratio of PUSCH EPRE to DM-RS EPRE | -3 dB | +| | DM-RS port | {0} | +| | DM-RS sequence generation | $N_{ID}^0=0$ , $n_{SCID}=0$ for moving UE
$N_{ID}^0=1$ , $n_{SCID}=1$ for stationary UE | +| Time domain resource assignment | PUSCH mapping type | A, B | +| | Start symbol | 0 | +| | Allocation length | 14 | +| Frequency domain resource assignment | RB assignment | 12 RB for each UE | +| | Starting PRB index | Moving UE: 0
Stationary UE: 12 | +| | Frequency hopping | Disabled | +| SRS resource allocation | Slots in which sounding RS is transmitted (Note 1) | slot #1 in radio frames | +| | SRS resource allocation | $C_{SRS} = 5$ , $B_{SRS} = 0$ , for 20 RB | +| Code block group based PUSCH transmission | | Disabled | + +NOTE 1: The transmission of SRS is optional. The transmission comb is configured as $K_{TC} = 2$ . The SRS periodic is configured as $T_{SRS} = 10$ for 15kHz SCS and 20 for 30kHz SCS respectively. + +### 8.2.3.2 Minimum requirements + +The throughput shall be $\geq 70\%$ of the maximum throughput of the reference measurement channel as specified in Annex A for the moving UE at the SNR given in table 8.2.3.2-1 to table 8.2.3.2-4. + +Table 8.2.3.2-1: Minimum requirements for UL timing adjustment with 70% of maximum throughput, PUSCH mapping Type A, 5 MHz channel bandwidth, 15 kHz SCS + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | Scenario X | 70 % | G-FR1-A3-2 | pos1 | 4.1 | +| | 2 | Normal | Scenario X | 70 % | G-FR1-A3-2 | pos1 | -0.3 | + +Table 8.2.3.2-2: Minimum requirements for UL timing adjustment with 70% of maximum throughput, PUSCH mapping Type A, 10 MHz channel bandwidth, 30 kHz SCS + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | Scenario X | 70 % | G-FR1-A3-4 | pos1 | 3.6 | +| | 2 | Normal | Scenario X | 70 % | G-FR1-A3-4 | pos1 | -0.5 | + +**Table 8.2.3.2-3: Minimum requirements for UL timing adjustment with 70% of maximum throughput, PUSCH mapping Type B, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | Scenario X | 70 % | G-FR1-A3-2 | pos1 | 4.2 | +| | 2 | Normal | Scenario X | 70 % | G-FR1-A3-2 | pos1 | -0.3 | + +**Table 8.2.3.2-4: Minimum requirements for UL timing adjustment with 70% of maximum throughput, PUSCH mapping Type B, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | Scenario X | 70 % | G-FR1-A3-4 | pos1 | 3.6 | +| | 2 | Normal | Scenario X | 70 % | G-FR1-A3-4 | pos1 | -0.4 | + +## 8.2.4 Requirements for PUSCH repetition Type A + +### 8.2.4.1 General + +The performance requirement of PUSCH is determined by a maximum block error probability (BLER) for a given SNR. The BLER is defined as the probability of incorrectly decoding the PUSCH information when the PUSCH information is sent. The performance requirements assume HARQ re-transmissions. + +**Table: 8.2.4.1-1 Test parameters for testing PUSCH repetition Type A** + +| Parameter | Value | +|--------------------------------------------------------------------------|-------------------------------------------| +| Transform precoding | Disabled | +| Channel bandwidth | 15kHz SCS: 5MHz
30kHz SCS: 10MHz | +| HARQ | Maximum number of HARQ transmissions | +| | 4 | +| DM-RS | RV sequence | +| | 0, 3, 0, 3 [Note 1] | +| | DM-RS configuration type | +| | 1 | +| | DM-RS duration | +| | single-symbol DM-RS | +| | Additional DM-RS position | +| | pos1 | +| | Number of DM-RS CDM group(s) without data | +| | 2 | +| | Ratio of PUSCH EPRE to DM-RS EPRE | +| | -3 dB | +| | DM-RS port | +| | {0} | +| | DM-RS sequence generation | +| | $N_{ID}^0=0, n_{SCID}=0$ | +| Time domain resource assignment | PUSCH mapping type | +| | A, B | +| | Start symbol | +| | 0 | +| | Allocation length | +| | 14 | +| | PUSCH aggregation factor | +| | n2 | +| Frequency domain resource assignment | RB assignment | +| | Full applicable test bandwidth | +| | Frequency hopping | +| | Disabled | +| Code block group based PUSCH transmission | Disabled | +| Note 1: The effective RV sequence is {0, 2, 3, 1} with slot aggregation. | | + +#### 8.2.4.2 Minimum requirements + +The BLER shall be equal to or smaller than the required target BLER for the FRCs stated in tables 8.2.4.2-1 to 8.2.4.2-4 at the given SNR. FRCs are defined in annex A. + +**Table 8.2.4.2-1: Minimum requirements for PUSCH repetition TypeA, PUSCH mapping Type A, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Target BLER | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 1% (Note 1) | G-FR1-A3A-1 | pos1 | -5.1 | +| | 2 | Normal | NTN-TDLA100-200 Low | 1% (Note 1) | G-FR1-A3A-1 | pos1 | -8.5 | + +Note 1: BLER is defined as residual BLER; i.e. ratio of incorrectly received transport blocks / sent transport blocks, independently of the number HARQ transmission(s) for each transport block. + +**Table 8.2.4.2-2: Minimum requirements for PUSCH, PUSCH mapping Type A, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Target BLER | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 1% (Note 1) | G-FR1-A3A-2] | pos1 | -5.1 | +| | 2 | Normal | NTN-TDLA100-200 Low | 1% (Note 1) | G-FR1-A3A-2 | pos1 | -8.5 | + +Note 1: BLER is defined as residual BLER; i.e. ratio of incorrectly received transport blocks / sent transport blocks, independently of the number HARQ transmission(s) for each transport block. + +**Table 8.2.4.2-3: Minimum requirements for PUSCH, PUSCH mapping Type B, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Target BLER | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 1% (Note 1) | G-FR1-A3A-1 | pos1 | -5.1 | +| | 2 | Normal | NTN-TDLA100-200 Low | 1% (Note 1) | G-FR1-A3A-1 | pos1 | -8.5 | + +Note 1: BLER is defined as residual BLER; i.e. ratio of incorrectly received transport blocks / sent transport blocks, independently of the number HARQ transmission(s) for each transport block. + +**Table 8.2.4.2-4: Minimum requirements for PUSCH, PUSCH mapping Type B, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Target BLER | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 1% (Note 1) | G-FR1-A3A-2 | pos1 | -5.1 | +| | 2 | Normal | NTN-TDLA100-200 Low | 1% (Note 1) | G-FR1-A3A-2 | pos1 | -8.5 | + +Note 1: BLER is defined as residual BLER; i.e. ratio of incorrectly received transport blocks / sent transport blocks, independently of the number HARQ transmission(s) for each transport block. + +## 8.3 Performance requirements for PUCCH + +### 8.3.1 DTX to ACK probability + +#### 8.3.1.1 General + +The DTX to ACK probability, i.e. the probability that ACK is detected when nothing was sent: + +$$\text{Prob}(\text{PUCCH DTX} \rightarrow \text{Ack bits}) = \frac{\#(\text{false ACK bits})}{\#(\text{PUCCH DTX}) * \#(\text{ACK/NACK bits})}$$ + +where: + +- #(false ACK bits) denotes the number of detected ACK bits. +- #(ACK/NACK bits) denotes the number of encoded bits per slot +- #(PUCCH DTX) denotes the number of DTX occasions + +#### 8.3.1.2 Minimum requirement + +The DTX to ACK probability shall not exceed 1% for all PUCCH formats carrying ACK/NACK bits: + +$$\text{Prob}(\text{PUCCH DTX} \rightarrow \text{Ack bits}) \leq 10^{-2}$$ + +## 8.3.2 Performance requirements for PUCCH format 0 + +### 8.3.2.1 General + +The ACK missed detection probability is the probability of not detecting an ACK when an ACK was sent. + +**Table 8.3.2.1-1: Test Parameters** + +| Parameter | Test | +|--------------------------------------|------------------| +| Number of UCI information bits | 1 | +| Number of PRBs | 1 | +| First PRB prior to frequency hopping | 0 | +| Intra-slot frequency hopping | Enabled | +| First PRB after frequency hopping | N/A | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Initial cyclic shift | 0 | +| First symbol | 12 for 2 symbols | + +The transient period as specified in TS 38.101-5 [11] clause 6.3.3 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the CC centre, i.e. intra-slot frequency hopping is enabled. + +### 8.3.2.2 Minimum requirements + +The ACK missed detection probability shall not exceed 1% at the SNR given in table 8.3.2.2-1 and in table 8.3.2.2-2. + +**Table 8.3.2.2-1: Minimum requirements for PUCCH format 0, 15 kHz SCS and 5MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|-----------------------|-----------------------|---------------------------------------------------------|----------| +| 1 | 1 | NTN-TDLA100-200 Low | 8.9 | +| | 2 | NTN-TDLA100-200 Low | 3.3 | + +**Table 8.3.2.2-2: Minimum requirements for PUCCH format 0, 30 kHz SCS and 10MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|-----------------------|-----------------------|---------------------------------------------------------|----------| +| 1 | 1 | NTN-TDLA100-200 Low | 11.1 | +| | 2 | NTN-TDLA100-200 Low | 4.8 | + +### 8.3.3 Performance requirements for PUCCH format 1 + +#### 8.3.3.1 NACK to ACK requirements + +##### 8.3.3.1.1 General + +The NACK to ACK detection probability is the probability that an ACK bit is falsely detected when an NACK bit was sent on the particular bit position, where the NACK to ACK detection probability is defined as follows: + +$$\text{Prob}(\text{PUCCH NACK} \rightarrow \text{ACK bits}) = \frac{\#(\text{NACK bits decoded as ACK bits})}{\#(\text{Total NACK bits})},$$ + +where: + +- $\#(\text{Total NACK bits})$ denotes the total number of NACK bits transmitted +- $\#(\text{NACK bits decoded as ACK bits})$ denotes the number of NACK bits decoded as ACK bits at the receiver, i.e. the number of received ACK bits +- NACK bits in the definition do not contain the NACK bits which are mapped from DTX, i.e. NACK bits received when DTX is sent should not be considered. + +Random codeword selection is assumed. + +**Table 8.3.3.1.1-1: Test Parameters** + +| Parameter | Test | +|---------------------------------------------------------|----------------------------------------| +| Number of information bits | 2 | +| Number of PRBs | 1 | +| Number of symbols | 14 | +| First PRB prior to frequency hopping | 0 | +| Intra-slot frequency hopping | enabled | +| First PRB after frequency hopping | The largest PRB index – (nrofPRBs – 1) | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Initial cyclic shift | 0 | +| First symbol | 0 | +| Index of orthogonal cover code ( timeDomainOCC ) | 0 | + +The transient period as specified in TS 38.101-5 [11] clause 6.3.3 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the CC centre, i.e. intra-slot frequency hopping is enabled. + +##### 8.3.3.1.2 Minimum requirements + +The NACK to ACK probability shall not exceed 0.1% at the SNR given in table 8.3.3.1.2-1 and table 8.3.3.1.2-2. + +**Table 8.3.3.1.2-1: Minimum requirements for PUCCH format 1, 15 kHz SCS and 5MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclis Prefix | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 2.2 | +| | 2 | Normal | NTN-TDLA100-200 Low | -4.1 | + +**Table 8.3.3.1.2-2: Minimum requirements for PUCCH format 1, 30 kHz SCS and 10MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclis Prefix | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 3.0 | +| | 2 | Normal | NTN-TDLA100-200 Low | -3.5 | + +### 8.3.3.2 ACK missed detection requirements + +#### 8.3.3.2.1 General + +The ACK missed detection probability is the probability of not detecting an ACK when an ACK was sent. The test parameters in table 8.3.3.1.1-1 are configured. + +The transient period as specified in TS 38.101-5 [11] clause 6.3.3 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the centre, i.e. intra-slot frequency hopping is enabled. + +#### 8.3.3.2.2 Minimum requirements + +The ACK missed detection probability shall not exceed 1% at the SNR given in table 8.3.3.2.2-1 and in table 8.3.3.2.2-2. + +**Table 8.3.3.2.2-1: Minimum requirements for PUCCH format 1, 15 kHz SCS and 5MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclis Prefix | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 1.5 | +| | 2 | Normal | NTN-TDLA100-200 Low | -4.6 | + +**Table 8.3.3.2.2-2: Minimum requirements for PUCCH format 1, 30 kHz SCS and 10MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclis Prefix | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 3.1 | +| | 2 | Normal | NTN-TDLA100-200 Low | -3.4 | + +## 8.3.4 Performance requirements for PUCCH format 2 + +### 8.3.4.1 ACK missed detection requirements + +#### 8.3.4.1.1 General + +The ACK missed detection probability is the probability of not detecting an ACK when an ACK was sent. + +The ACK missed detection requirement only applies to the PUCCH format 2 with 4 UCI bits. + +**Table 8.3.4.1.1-1: Test Parameters** + +| Parameter | Value | +|--------------------------------------|--------------| +| Modulation order | QSPK | +| First PRB prior to frequency hopping | 0 | +| Intra-slot frequency hopping | N/A | +| First PRB after frequency hopping | N/A | +| Number of PRBs | 4 | +| Number of symbols | 1 | +| The number of UCI information bits | 4 | +| First symbol | 13 | +| DM-RS sequence generation | $N_{ID}^0=0$ | + +The transient period as specified in TS 38.101-5 [11] clause 6.3.3 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the CC center, i.e. intra-slot frequency hopping is enabled. + +#### 8.3.4.1.2 Minimum requirements + +The ACK missed detection probability shall not exceed 1% at the SNR given in table 8.3.4.1.2-1 and table 8.3.4.1.2-2 for 4 UCI bits. + +**Table 8.3.4.1.2-1: Minimum requirements for PUCCH format 2, 15 kHz SCS and 5MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 14.6 | +| | 2 | Normal | NTN-TDLA100-200 Low | 4.7 | + +**Table 8.3.4.1.2-2: Minimum requirements for PUCCH format 2, 30 kHz SCS and 10MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 12.0 | +| | 2 | Normal | NTN-TDLA100-200 Low | 4.4 | + +### 8.3.4.2 UCI BLER performance requirements + +#### 8.3.4.2.1 General + +The UCI block error probability (BLER) is defined as the probability of incorrectly decoding the UCI information when the UCI information is sent. The UCI information does not contain CSI part1 and part 2. + +The transient period as specified in TS 38.101-5 [11] clause 6.3.3 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the CC centre, i.e. intra-slot frequency hopping is enabled. + +The UCI block error probability performance requirement only applies to the PUCCH format 2 with 22 UCI bits. + +**Table 8.3.4.2.1-1: Test Parameters** + +| Parameter | Value | +|--------------------------------------|----------------------------------------------| +| Modulation order | QSPK | +| First PRB prior to frequency hopping | 0 | +| Intra-slot frequency hopping | enabled | +| First PRB after frequency hopping | The largest PRB index – (Number of PRBs – 1) | +| Number of PRBs | 9 | +| Number of symbols | 2 | +| The number of UCI information bits | 22 | +| First symbol | 12 | +| DM-RS sequence generation | $N_{ID}^0=0$ | + +### 8.3.4.2.2 Minimum requirements + +The UCI block error probability shall not exceed 1% at the SNR given in table 8.3.4.2.2-1 and table 8.3.4.2.2-2 for 22 UCI bits. + +**Table 8.3.4.2.2-1: Minimum requirements for PUCCH format 2, 15 kHz SCS and 5MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 6.3 | +| | 2 | Normal | NTN-TDLA100-200 Low | 0.8 | + +**Table 8.3.4.2.2-2: Minimum requirements for PUCCH format 2, 30 kHz SCS and 10MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex X) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 6.4 | +| | 2 | Normal | NTN-TDLA100-200 Low | 0.5 | + +## 8.3.5 Performance requirements for PUCCH format 3 + +### 8.3.5.1 General + +The performance is measured by the required SNR at UCI block error probability not exceeding 1%. + +The UCI block error probability is defined as the conditional probability of incorrectly decoding the UCI information when the UCI information is sent. The UCI information does not contain CSI part1 and part 2. + +The transient period as specified in TS 38.101-5 [11] clause 6.3.3 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the centre, i.e. intra-slot frequency hopping is enabled. + +**Table 8.3.5.1-1: Test Parameters** + +| Parameter | Test | +|--------------------------------------|----------------------------------------------| +| Modulation order | QPSK | +| First PRB prior to frequency hopping | 0 | +| Intra-slot frequency hopping | enabled | +| First PRB after frequency hopping | The largest PRB index – (Number of PRBs – 1) | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Number of PRBs | 1 | +| Number of symbols | 14 | +| The number of UCI information bits | 16 | +| First symbol | 0 | + +### 8.3.5.2 Minimum requirements + +The UCI block error probability shall not exceed 1% at the SNR given in Table 8.3.5.2-1 and Table 8.3.5.2-2. + +**Table 8.3.5.2-1: Minimum requirements for PUCCH format 3, 15 kHz SCS and 5MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclis Prefix | Propagation conditions and correlation matrix (Annex X) | Additioan DM-RS configuration | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | No additional DM-RS | 6.6 | +| | | | | Additional DM-RS | 6.4 | +| | 2 | Normal | NTN-TDLA100-200 Low | No additional DM-RS | 0.3 | +| | | | | Additional DM-RS | 0.0 | + +**Table 8.3.5.2-2: Minimum requirements for PUCCH format 3, 30 kHz SCS and 10MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclis Prefix | Propagation conditions and correlation matrix (Annex X) | Additioan DM-RS configuration | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | No additional DM-RS | 9.2 | +| | | | | Additional DM-RS | 8.6 | +| | 2 | Normal | NTN-TDLA100-200 Low | No additional DM-RS | 1.6 | +| | | | | Additional DM-RS | 1.5 | + +## 8.3.6 Performance requirements for PUCCH format 4 + +### 8.3.6.1 General + +The performance is measured by the required SNR at UCI block error probability not exceeding 1%. + +The UCI block error probability is defined as the conditional probability of incorrectly decoding the UCI information when the UCI information is sent. The UCI information does not contain CSI part1 and part 2. + +The transient period as specified in TS 38.101-5 [11] clause 6.3.3 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the centre, i.e. intra-slot frequency hopping is enabled. + +**Table 8.3.6.1-1: Test parameters** + +| Parameter | Value | +|--------------------------------------|----------------------------------------------| +| Modulation order | QPSK | +| First PRB prior to frequency hopping | 0 | +| Number of PRBs | 1 | +| Intra-slot frequency hopping | enabled | +| First PRB after frequency hopping | The largest PRB index – (Number of PRBs – 1) | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Number of symbols | 14 | +| The number of UCI information bits | 22 | +| First symbol | 0 | +| Length of the orthogonal cover code | n2 | +| Index of the orthogonal cover code | n0 | + +### 8.3.6.2 Minimum requirement + +The UCI block error probability shall not exceed 1% at the SNR given in Table 8.3.6.2-1 and Table 8.3.6.2-2. + +**Table 8.3.6.2-1: Minimum requirements for PUCCH format 4, 15 kHz SCS and 5MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex X) | Additional DM-RS configuration | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | No additional DM-RS | 8.9 | +| | | | | Additional DM-RS | 8.6 | +| | 2 | Normal | NTN-TDLA100-200 Low | No additional DM-RS | 2.5 | +| | | | | Additional DM-RS | 2.2 | + +**Table 8.3.6.2-2: Minimum requirements for PUCCH format 4, 30 kHz SCS and 10MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex X) | Additional DM-RS configuration | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | No additional DM-RS | 10.5 | +| | | | | Additional DM-RS | 10.5 | +| | 2 | Normal | NTN-TDLA100-200 Low | No additional DM-RS | 3.5 | +| | | | | Additional DM-RS | 3.3 | + +## 8.3.7 Performance requirements for multi-slot PUCCH + +### 8.3.7.1 General + +### 8.3.7.2 Performance requirements for multi-slot PUCCH format 1 + +#### 8.3.7.2.1 NACK to ACK requirements + +##### 8.3.7.2.1.1 General + +The NACK to ACK detection probability is the probability that an ACK bit is falsely detected when a NACK bit was sent on the particular bit position, where the NACK to ACK detection probability is defined as follows: + +$$\text{Prob}(\text{PUCCH NACK} \rightarrow \text{ACK bits}) = \frac{\#(\text{NACK bits decoded as ACK bits})}{\#(\text{Total NACK bits})},$$ + +where: + +- $\#(\text{Total NACK bits})$ denotes the total number of NACK bits transmitted +- $\#(\text{NACK bits decoded as ACK bits})$ denotes the number of NACK bits decoded as ACK bits at the receiver, i.e., the number of received ACK bits +- NACK bits in the definition do not contain the NACK bits which are mapped from DTX, i.e., NACK bits received when DTX is sent should not be considered. + +Random codeword selection is assumed. + +**Table 8.3.7.2.1.1-1: Test Parameters for multi-slot PUCCH format 1** + +| Parameter | Test | +|------------------------------------------------------------|-------------------------------------------| +| Number of information bits | 2 | +| Number of PRBs | 1 | +| Number of symbols | 14 | +| First PRB prior to frequency hopping | 0 | +| Intra-slot frequency hopping | disabled | +| Inter-slot frequency hopping | enabled | +| First PRB after frequency hopping | The largest PRB index
– (nrofPRBs – 1) | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Initial cyclic shift | 0 | +| First symbol | 0 | +| Index of orthogonal cover code
( timeDomainOCC ) | 0 | +| Number of slots for PUCCH repetition | 2 | + +#### 8.3.7.2.1.2 Minimum requirements + +The multi-slot NACK to ACK probability shall not exceed 0.1% at the SNR given in table 8.3.7.2.1.2-1 and 8.3.7.2.1.2-2. + +**Table 8.3.7.2.1.2-1: Minimum requirements for multi-slot PUCCH format 1 with 15kHz SCS 5MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 0.6 | +| | 2 | Normal | NTN-TDLA100-200 Low | -6.6 | + +**Table 8.3.7.2.1.2-2: Minimum requirements for multi-slot PUCCH format 1 with 30kHz SCS 10MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | 1.2 | +| | 2 | Normal | NTN-TDLA100-200 Low | -5.6 | + +#### 8.3.7.2.2 ACK missed detection requirements + +##### 8.3.7.2.2.1 General + +The ACK missed detection probability is the probability of not detecting an ACK when an ACK was sent. The test parameters in table 8.3.7.2.1.1-1 are configured. + +#### 8.3.7.2.2.2 Minimum requirements + +The multi-slot ACK missed detection probability shall not exceed 1% at the SNR given in table 8.3.7.2.2.2-1 and 8.3.7.2.2.2-2. + +**Table 8.3.7.2.2.2-1: Minimum requirements for multi-slot PUCCH format 1 with 15kHz SCS 5MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | -1.9 | +| | 2 | Normal | NTN-TDLA100-200 Low | -8.0 | + +**Table 8.3.7.2.2.2-2: Minimum requirements for multi-slot PUCCH format 1 with 30kHz SCS 10MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 1 | Normal | NTN-TDLA100-200 Low | -1.2 | +| | 2 | Normal | NTN-TDLA100-200 Low | -7.6 | + +## 8.4 Performance requirements for PRACH + +### 8.4.1 PRACH False alarm probability + +#### 8.4.1.1 General + +The false alarm requirement is valid for any number of receive antennas, for any channel bandwidth. + +The false alarm probability is the conditional total probability of erroneous detection of the preamble (i.e. erroneous detection from any detector) when input is only noise. + +#### 8.4.1.2 Minimum requirement + +The false alarm probability shall be less than or equal to 0.1%. + +### 8.4.2 PRACH detection requirements + +#### 8.4.2.1 General + +The probability of detection is the conditional probability of correct detection of the preamble when the signal is present. There are several error cases – detecting different preamble than the one that was sent, not detecting a preamble at all or correct preamble detection but with the wrong timing estimation. For AWGN, NTN-TDLA100, a timing estimation error occurs if the estimation error of the timing of the strongest path is larger than the time error tolerance given in Table 8.4.2.1-1. + +**Table 8.4.2.1-1: Time error tolerance for AWGN, NTN-TDLA100-200** + +| PRACH preamble | PRACH SCS (kHz) | Time error tolerance | | +|----------------|-----------------|----------------------|-------------| +| | | AWGN | NTN-TDLA100 | +| 0 | 1.25 | 1.04 us | 1.324 us | +| 2 | 1.25 | 1.04 us | 1.324 us | +| B4, C2 | 15 | 0.52 us | 0.804 us | +| | 30 | 0.26 us | 0.544 us | + +The test preambles are listed in table A.4 and the test parameter *msg1-FrequencyStart* is set to 0. + +#### 8.4.2.2 Minimum requirements + +The probability of detection shall be equal to or exceed 99% for the SNR levels listed in Tables 8.4.2.2-1 to 8.4.2.2-3. + +**Table 8.4.2.2-1: PRACH missed detection test requirements, 1.25 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Frequency offset | SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|----------------|----------------| +| | | | | Burst format 0 | Burst format 2 | +| 1 | 1 | AWGN | 0 | -12.0 | -17.4 | +| | | NTN-TDLA100-200 Low | 200 Hz | 0.7 | -9.7 | +| | 2 | AWGN | 0 | -14.5 | -19.8 | +| | | NTN-TDLA100-200 Low | 200 Hz | -6.8 | -14.9 | + +**Table 8.4.2.2-2: PRACH missed detection test requirements, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Frequency offset | SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|-----------------|-----------------| +| | | | | Burst format B4 | Burst format C2 | +| 1 | 1 | AWGN | 0 | -14.6 | -9.2 | +| | | NTN-TDLA100-200 Low | 200 Hz | -2.7 | 1.9 | +| | 2 | AWGN | 0 | -16.8 | -12.5 | +| | | NTN-TDLA100-200 Low | 200 Hz | -4.8 | -4.8 | + +**Table 8.4.2.2-3: PRACH missed detection test requirements, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Frequency offset | SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|-----------------|-----------------| +| | | | | Burst format B4 | Burst format C2 | +| 1 | 1 | AWGN | 0 | -14.4 | -9.2 | +| | | NTN-TDLA100-200 Low | 200 Hz | -4.3 | 0.1 | +| | 2 | AWGN | 0 | -16.5 | -11.9 | +| | | NTN-TDLA100-200 Low | 200 Hz | -10.0 | -5.8 | + +## 9 Radiated transmitter characteristics + +### 9.1 General + +Radiated transmitter characteristics requirements apply on the *SAN type 1-H* or *SAN type 1-O* including all its functional components active and for all foreseen modes of operation of the SAN unless otherwise stated. + +### 9.2 Radiated transmit power + +#### 9.2.1 General + +*SAN type 1-H* and *SAN type 1-O* are declared to support one or more beams, as per manufacturer's declarations specified in TS 38.181 [3]. 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 SAN 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 38.181 [3]. + +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 SAN type 1-H and SAN type 1-O + +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 $\pm 2.2$ dB of the claimed value. + +Normal conditions are defined in TS 38.181, annex B [3]. + +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 OTA Satellite Access Node output power + +## 9.3.1 General + +OTA SAN output power is declared as the TRP radiated requirement, with the output power accuracy requirement defined at the RIB. TRP does not change with beamforming settings as long as the *beam peak direction* is within the *OTA peak directions set*. Thus the TRP accuracy requirement must be met for any beamforming setting for which the *beam peak direction* is within the *OTA peak directions set*. + +The SAN *rated carrier TRP output power* for SAN type 1-O shall be based on manufacturer declaration. + +Despite the general requirements for the SAN output power described in clause 9.3.2, additional regional requirements might be applicable. + +## 9.3.2 Minimum requirement for SAN type 1-O + +In normal conditions, the *SAN type 1-O maximum carrier TRP output power*, $P_{\max,c,TRP}$ measured at the RIB shall remain within $\pm 2$ dB of the *rated carrier TRP output power* $P_{\text{rated},c,TRP}$ , as declared by the manufacturer. + +Normal conditions are defined in TS 38.181 [3], annex B. + +# 9.4 OTA output power dynamics + +## 9.4.1 General + +Transmit signal quality (as specified in clause 9.6) shall be maintained for the output power dynamics requirements. + +The OTA output power requirements are *directional requirements* and apply to the *beam peak directions* over the *OTA peak directions set*. + +## 9.4.2 OTA RE power control dynamic range + +### 9.4.2.1 General + +The OTA RE power control dynamic range is the difference between the power of an RE and the average RE power for a SAN at maximum output power ( $P_{\max,c,EIRP}$ ) for a specified reference condition. + +This requirement shall apply at each RIB supporting transmission in the *operating band*. + +### 9.4.2.2 Minimum requirement for SAN type 1-O + +The OTA RE power control dynamic range is specified the same as the conducted RE power control dynamic range requirement for SAN type 1-H in table 6.3.2.2-1. + +## 9.4.3 OTA total power dynamic range + +### 9.4.3.1 General + +The OTA total power dynamic range is the difference between the maximum and the minimum transmit power of an OFDM symbol for a specified reference condition. + +This requirement shall apply at each RIB supporting transmission in the *operating band*. + +NOTE 1: The upper limit of the OTA total power dynamic range is the SAN maximum carrier EIRP ( $P_{\max,c,EIRP}$ ) when transmitting on all RBs. The lower limit of the OTA total power dynamic range is the average EIRP for single RB transmission in the same direction using the same beam. The OFDM symbol carries PDSCH and not contain RS or SSB. + +### 9.4.3.2 Minimum requirement for SAN type 1-O + +OTA total power dynamic range minimum requirement for SAN type 1-O is specified such as for each NR carrier it shall be larger than or equal to the levels specified for the conducted requirement for SAN type 1-H in table 6.3.3.2-1. + +## 9.5 OTA transmit ON/OFF power + +The requirement is not applicable in this version of the specification. + +## 9.6 OTA transmitted signal quality + +### 9.6.1 OTA frequency error + +#### 9.6.1.1 General + +OTA frequency error is the measure of the difference between the actual SAN transmit frequency and the assigned frequency. The same source shall be used for RF frequency and data clock generation. + +OTA frequency error requirement is defined as a *directional requirement* at the RIB and shall be met within the *OTA coverage range*. + +### 9.6.1.2 Minimum requirement for SAN type 1-O + +The modulated carrier frequency of each carrier configured by the SAN shall be accurate to within 0.05 ppm observed over 1 ms. + +## 9.6.2 OTA modulation quality + +### 9.6.2.1 General + +Modulation quality is defined by the difference between the measured carrier signal and an ideal signal. Modulation quality can e.g. be expressed as Error Vector Magnitude (EVM). Details about how the EVM is determined are specified in annex B for FR1. + +OTA modulation quality requirement is defined as a *directional requirement* at the RIB and shall be met within the *OTA coverage range*. + +### 9.6.2.2 Minimum requirement for SAN type 1-O + +For *SAN type 1-O*, the EVM levels of each carrier for different modulation schemes on PDSCH outlined in table 6.5.2.2-1 shall be met. Requirements shall be the same as clause 6.5.2.2 and follow EVM frame structure from clause 6.5.2.3. + +## 9.6.3 OTA time alignment error + +The requirement is not applicable in this version of the specification. + +## 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 ITU-R SM.329 [2]. In ITU terminology, out of band emissions are unwanted emissions immediately outside the *SAN 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 OTA out-of-band emissions requirement for the *SAN type 1-O* is specified both in terms of Adjacent Channel Leakage power Ratio (ACLR) and out-of-band emissions (OOBE). The unwanted emission requirements are applied per cell for all the configurations. Requirements for OTA unwanted emissions are captured as TRP requirements or *directional requirements*, as described per requirement. + +There is in addition a requirement for occupied bandwidth. + +### 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 [8]. + +The value of $\beta/2$ shall be taken as 0.5%. + +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. + +#### 9.7.2.2 Minimum requirement for SAN type 1-O + +The OTA occupied bandwidth for each carrier shall be less than the *SAN channel bandwidth*. + +### 9.7.3 OTA Adjacent Channel Leakage Power Ratio (ACLR) + +#### 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. + +The requirement shall be applied per RIB. + +#### 9.7.3.2 Minimum requirement for SAN type 1-O + +The ACLR limit specified in tables 6.6.3.2-1 for SAN GEO class and 6.6.3.2-2 for SAN LEO class shall apply. + +For a RIB operating in multi-carrier, the ACLR requirements in clause 6.6.3.2 shall apply to SAN channel bandwidths of the outermost carrier for the frequency ranges defined in tables 6.6.3.2-1 and 6.6.3.2-2. + +### 9.7.4 OTA out-of-band emissions + +#### 9.7.4.1 General + +The OTA limits for out-of-band emissions are specified as TRP per RIB unless otherwise stated. + +#### 9.7.4.2 Minimum requirement for SAN type 1-O + +Out-of-band emissions in FR1 are limited by OTA out-of-band emission limits. Unless otherwise stated, the out-of-band emission limits in FR1 are defined from channel edge up to frequencies separated from the channel edge by 200% of the necessary bandwidth. The requirements shall apply whatever the type of transmitter considered and for all transmission modes foreseen by the manufacturer's specification. For a RIB operating in multi-carrier, the requirements apply to SAN channel bandwidths of the outermost carrier for the frequency ranges defined in clause 6.6.4.1. + +The OTA out-of-band emissions requirement for SAN type 1-O shall not exceed each applicable limit in clause 6.6.4.2. + +### 9.7.5 OTA transmitter spurious emissions + +#### 9.7.5.1 General + +Unless otherwise stated, all requirements are measured as mean power. + +The OTA spurious emissions limits are specified as TRP per RIB unless otherwise stated. + +## 9.7.5.2 Minimum requirement for SAN type 1-O + +### 9.7.5.2.1 General + +The OTA transmitter spurious emission limits for FR1 shall apply from 30 MHz to the 5th harmonic of the upper frequency edge of the DL operating band, excluding the *SAN transponder bandwidth* $BW_{SAN}$ and the frequency range where the out-of-band emissions apply. + +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 specification. + +### 9.7.5.2.2 General OTA transmitter spurious emissions requirements + +The *basic limits* of table 9.7.5.2.2-1 shall apply. The application of those limits shall be the same as for operating band unwanted emissions in clause 6.6.4. + +**Table 9.7.5.2.2-1: General SAN transmitter spurious emission limits in FR1** + +| Spurious frequency range | $P_{\text{rated,c,TRP}}$ (dBm) | Basic limit (dBm) | Measurement bandwidth (kHz) | Notes | +|----------------------------------------------------------------------------------------|--------------------------------|----------------------------------------|-----------------------------|------------------------| +| 30 MHz – 5 th harmonic of the upper frequency edge of the DL operating band | $\leq 47$ | -13 | 4 | NOTE 1, NOTE 2, NOTE 3 | +| | $> 47$ | $P_{\text{rated,c,TRP}} - 60\text{dB}$ | | | + +NOTE 1: Measurement bandwidths as in ITU-R SM.329 [2], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [2], s2.5 table 1. +NOTE 3: The lower frequency limit is replaced by 0.7 times the waveguide cut-off frequency, according to ITU-R SM.329 [2], for systems having an integral antenna incorporating a waveguide section, or with an antenna connection in such form, and of unperturbed length equal to at least twice the cut-off. + +### 9.7.5.2.3 Protection of the SAN receiver + +The co-location requirement is not applicable for SAN in this version of the specification. + +### 9.7.5.2.4 Additional spurious emissions requirements + +The additional spurious emissions requirement is not applicable for SAN. + +## 9.8 OTA transmitter intermodulation + +The requirement is not applicable in this version of the specification. + +## 10 Radiated receiver characteristics + +### 10.1 General + +Radiated receiver characteristics are specified at RIB for *SAN type 1-H* or *SAN type 1-O*, with full complement of transceivers for the configuration in normal operating condition. + +Unless otherwise stated, the following arrangements apply for the radiated receiver characteristics requirements in clause 10: + +- Requirements shall be met for any transmitter setting. +- The requirements shall be met with the transmitter unit(s) ON. +- Throughput requirements defined for the radiated receiver characteristics do not assume HARQ retransmissions. +- When SAN is configured to receive multiple carriers, all the throughput requirements are applicable for each received carrier. +- For ACS and blocking characteristics, the negative offsets of the interfering signal apply relative to the lower *SAN RF Bandwidth* edge, and the positive offsets of the interfering signal apply relative to the upper *SAN RF Bandwidth* edge. +- Each requirement shall be met over the RoAoA specified. + +NOTE 1: In normal operating condition the SAN in FDD operation is configured to transmit and receive at the same time. + +For FR1 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)}$$ + +## 10.2 OTA sensitivity + +### 10.2.1 General + +The OTA sensitivity requirement is a *directional requirement* based upon the declaration of one or more *OTA sensitivity direction declarations* (OSDD), related to a *SAN type 1-H* and *SAN type 1-O* receiver. + +The *SAN type 1-H* and *SAN type 1-O* may optionally be capable of redirecting/changing the *receiver target* by means of adjusting SAN settings resulting in multiple *sensitivity RoAoA*. The *sensitivity RoAoA* resulting from the current SAN settings is the active *sensitivity RoAoA*. + +If the SAN is capable of redirecting the *receiver target* related to the OSDD then the OSDD shall include: + +- *SAN 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 SAN. + +- Five declared *sensitivity RoAoA* comprising the conformance testing directions as detailed in TS 38.181 [3]. +- 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. + +If the SAN is not capable of redirecting the *receiver target* related to the OSDD, then the OSDD includes only: + +- The set(s) of RAT, *SAN 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 3: For SAN 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 SAN type 1-O + +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 in clause 7.2 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 and *SAN channel bandwidth*. + +## 10.3 OTA reference sensitivity level + +### 10.3.1 General + +The OTA REFSENS requirement is a *directional requirement* and is intended to ensure the minimum OTA reference sensitivity level for a declared *OTA REFSENS RoAoA*. The OTA reference sensitivity power level $EIS_{REFSENS}$ is the minimum 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 SAN type 1-O + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in the corresponding table and annex A.1 when the OTA test signal is at the corresponding $EIS_{REFSENS}$ level and arrives from any direction within the *OTA REFSENS RoAoA*. + +Table 10.3.2-1: SAN GEO class reference sensitivity levels + +| SAN channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | OTA reference sensitivity level, $EIS_{REFSENS}$ (dBm) | +|-----------------------------|---------------------------|-------------------------------|--------------------------------------------------------| +| 5, 10, 15 | 15 | G-FR1-A1-1 | -99.3 - $\Delta OTAREFSENS$ | +| 10, 15 | 30 | G-FR1-A1-2 | -99.4 - $\Delta OTAREFSENS$ | +| 10, 15 | 60 | G-FR1-A1-3 | -96.5 - $\Delta OTAREFSENS$ | +| 20 | 15 | G-FR1-A1-4 | -92.9 - $\Delta OTAREFSENS$ | +| 20 | 30 | G-FR1-A1-5 | -93.2 - $\Delta OTAREFSENS$ | +| 20 | 60 | G-FR1-A1-6 | -93.3 - $\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 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 SAN channel bandwidth. + +Table 10.3.2-2: SAN LEO class reference sensitivity levels + +| SAN channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | OTA reference sensitivity level, $EIS_{REFSENS}$ (dBm) | +|-----------------------------|---------------------------|-------------------------------|--------------------------------------------------------| +| 5, 10, 15 | 15 | G-FR1-A1-1 | -102.4 - $\Delta OTAREFSENS$ | +| 10, 15 | 30 | G-FR1-A1-2 | -102.5 - $\Delta OTAREFSENS$ | +| 10, 15 | 60 | G-FR1-A1-3 | -99.6 - $\Delta OTAREFSENS$ | +| 20 | 15 | G-FR1-A1-4 | -96.0 - $\Delta OTAREFSENS$ | +| 20 | 30 | G-FR1-A1-5 | -96.3 - $\Delta OTAREFSENS$ | +| 20 | 60 | G-FR1-A1-6 | -96.4 - $\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 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 SAN channel bandwidth. + +## 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 SAN channel bandwidth. + +The requirement shall apply 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 SAN type 1-O + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.2 with parameters specified in table 10.4.2-1 for LEO SAN. + +Table 10.4.2-1: SAN LEO class dynamic range + +| SAN 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 | +|-----------------------------|--------------------------|-------------------------------|--------------------------------------|------------------------------------------------------------|----------------------------| +| 5 | 15 | G-FR1-A2-1 | -76.4 - $\Delta_{\text{OTAREFSENS}}$ | -88.2 - $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | -77.1 - $\Delta_{\text{OTAREFSENS}}$ | | | +| 10 | 15 | G-FR1-A2-1 | -76.4 - $\Delta_{\text{OTAREFSENS}}$ | -85.0 - $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | -77.1 - $\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-3 | -74.1 - $\Delta_{\text{OTAREFSENS}}$ | | | +| 15 | 15 | G-FR1-A2-1 | -76.4 - $\Delta_{\text{OTAREFSENS}}$ | -83.2 - $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | -77.1 - $\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-3 | -74.1 - $\Delta_{\text{OTAREFSENS}}$ | | | +| 20 | 15 | G-FR1-A2-4 | -70.2 - $\Delta_{\text{OTAREFSENS}}$ | -81.9 - $\Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | -70.2 - $\Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | -70.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 SAN channel bandwidth. + +## 10.5 OTA in-band selectivity and blocking + +### 10.5.1 OTA adjacent channel selectivity + +#### 10.5.1.1 General + +OTA Adjacent channel selectivity (ACS) is a measure of the receiver's ability to receive an OTA wanted signal at its assigned channel frequency in the presence of an OTA adjacent channel signal with a specified centre frequency offset of the interfering signal to the band edge of a victim system. + +#### 10.5.1.2 Minimum requirement for SAN type 1-O + +The requirement shall apply 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*. + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel. + +For FR1, the OTA wanted signal and the interfering signal are specified in table 10.5.1.2-1 and table 10.5.1.2-2 for OTA ACS. The reference measurement channel for the OTA wanted signal is further specified in annex A.1. The characteristic of the interfering signal is further specified in annex C. + +The OTA ACS requirement is applicable outside the SAN RF Bandwidth or Radio Bandwidth. The OTA interfering signal offset is defined relative to the SAN RF Bandwidth edges or Radio Bandwidth edges. + +**Table 10.5.1.2-1: OTA ACS requirement for SAN type 1-O** + +| SAN channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) (NOTE 2) | Interfering signal mean power (dBm) | +|--------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|----------------------------------------------------------------------------------------| +| 5, 10, 15, 20 (NOTE 1) | EIS minSENS + 6 dB | SAN LEO class: -60 – Δ minSENS
SAN GEO class: -57 – Δ minSENS | +| NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the SAN for that bandwidth | | | +| NOTE 2: EIS minSENS depends on the SAN channel bandwidth | | | + +**Table 10.5.1.2-2: OTA ACS interferer frequency offset for SAN type 1-O** + +| SAN channel bandwidth of the lowest/highest carrier received (MHz) | Interfering signal centre frequency offset from the lower/upper SAN RF Bandwidth edge or sub-block edge inside a sub-block gap (MHz) | Type of interfering signal | +|--------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| 5 | ±2.5025 | 5 MHz CP-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 10 | ±2.5075 | | +| 15 | ±2.5125 | | +| 20 | ±2.5025 | | + +## 10.5.2 OTA in-band blocking + +The requirement is not applicable in this version of the specification. + +## 10.6 OTA out-of-band blocking + +### 10.6.1 General + +The OTA out-of-band 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. + +### 10.6.2 Minimum requirement for SAN type 1-O + +#### 10.6.2.1 General minimum requirement + +The requirement shall apply at the RIB when the AoA of the incident wave of the received signal and the interfering signal are from 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. + +For OTA wanted and OTA interfering signals provided at the RIB using the parameters in table 10.6.2.1-1, the following requirements shall be met: + +- The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel. The reference measurement channel for the OTA wanted signal is identified in clause 10.3.2 for each *SAN channel bandwidth* and further specified in annex A.1. + +For *SAN type 1-O* the OTA out-of-band blocking requirement apply from 30 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 *SAN operating band*. The $\Delta f_{OOB}$ for *SAN type 1-O* is defined in table 10.6.2.1-2. + +Table 10.6.2.1-1: OTA out-of-band 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.0029
(NOTE 2) | CW carrier | + +NOTE 1: EISminSENS depends on the *channel bandwidth* as specified in clause 10.2. +NOTE 2: The RMS field-strength level in V/m is related to the interferer EIRP level at a distance described as $E = \frac{\sqrt{30EIRP}}{r}$ , where EIRP is in W and r is in m. + +Table 10.6.2.1-2: $\Delta f_{OOb}$ offset for satellite operating bands + +| SAN type | Operating band characteristics | $\Delta f_{OOb}$ (MHz) | +|--------------|--------------------------------------|------------------------| +| SAN type 1-O | $F_{UL,high} - F_{UL,low} < 100$ MHz | 20 | + +## 10.7 OTA receiver spurious emissions + +The requirement is not applicable in this version of the specification. + +### 10.7.1 Void + +### 10.7.2 Void + +## 10.8 OTA receiver intermodulation + +The requirement is not applicable in this version of the specification. + +## 10.9 OTA in-channel selectivity + +### 10.9.1 General + +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. The interfering signal shall be an NR signal as specified in annex A.1 and shall be time aligned with the wanted signal. + +### 10.9.2 Minimum requirement for SAN type 1-O + +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 each supported polarization, under the assumption of *polarization match*. + +For a wanted and an interfering signal coupled to the RIB, the following requirements shall be met: + +- For *SAN type 1-O*, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.1 with parameters specified in table 10.9.2-1 for GEO SAN, in table 10.9.2-2 for LEO SAN. The characteristics of the interfering signal is further specified in annex C. + +Table 10.9.2-1: SAN GEO classICS requirement + +| SAN channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|-----------------------------|--------------------------|-------------------------------|--------------------------------|-------------------------------------|------------------------------------------| +| 5 | 15 | G-FR1-A1-7 | -98.2 - $\Delta_{minSENS}$ | -92.0 - $\Delta_{minSENS}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10,15,20 | 15 | G-FR1-A1-1 | -96.3 - $\Delta_{minSENS}$ | -88.1 - $\Delta_{minSENS}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 5 | 30 | G-FR1-A1-8 | -98.9 - $\Delta_{minSENS}$ | -92.0 - $\Delta_{minSENS}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 5 RBs | +| 10,15,20 | 30 | G-FR1-A1-2 | -96.4 - $\Delta_{minSENS}$ | -89.0 - $\Delta_{minSENS}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 10,15,20 | 60 | G-FR1-A1-9 | -95.8 - $\Delta_{minSENS}$ | -89.0 - $\Delta_{minSENS}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | + +NOTE: Wanted and interfering signal are placed adjacently around $F_c$ , where the $F_c$ is defined for *SAN channel bandwidth* of the wanted signal according to the table 5.4.2.2-1. The aggregated wanted and interferer signal shall be centred in the *SAN channel bandwidth* of the wanted signal. + +Table 10.9.2-2: SAN LEO class ICS requirement + +| SAN channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|-----------------------------|--------------------------|-------------------------------|--------------------------------|-------------------------------------|------------------------------------------| +| 5 | 15 | G-FR1-A1-7 | -101.3 - $\Delta_{minSENS}$ | -83.1 - $\Delta_{minSENS}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10,15,20 | 15 | G-FR1-A1-1 | -99.4 - $\Delta_{minSENS}$ | -79.2 - $\Delta_{minSENS}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 5 | 30 | G-FR1-A1-8 | -102.0 - $\Delta_{minSENS}$ | -83.1 - $\Delta_{minSENS}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 5 RBs | +| 10,15,20 | 30 | G-FR1-A1-2 | -99.5 - $\Delta_{minSENS}$ | -80.1 - $\Delta_{minSENS}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 10,15,20 | 60 | G-FR1-A1-9 | -98.9 - $\Delta_{minSENS}$ | -80.1 - $\Delta_{minSENS}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | + +NOTE: Wanted and interfering signal are placed adjacently around $F_c$ , where the $F_c$ is defined for *SAN channel bandwidth* of the wanted signal according to the table 5.4.2.2-1. The aggregated wanted and interferer signal shall be centred in the *SAN channel bandwidth* of the wanted signal. + +## 11 Radiated performance requirements + +### 11.1 General + +#### 11.1.1 Scope and definitions + +Radiated performance requirements specify the ability of the *SAN type 1-0* to correctly transmit and receive radiated signals in various conditions and configurations. Radiated performance requirements are specified at the RIB. + +Radiated performance requirements for the SAN are specified for the fixed reference channels defined in annex A and for the propagation conditions defined in Recommendation ITU-R P.618 (*Propagation data and prediction methods required for the design of Earth-space telecommunication systems*). The requirements only apply to those FRCs that are supported by the SAN. + +The radiated performance requirements for *SAN type 1-O* are limited to two OTA *demodulation branches* as described in clause 11.1.2. Conformance requirements can only be tested for 1 or 2 *demodulation branches* depending on the number of polarizations supported by the SAN, with the required SNR applied separately per polarization. + +Unless stated otherwise, radiated performance requirements apply for a single carrier only. Radiated performance requirements for a SAN supporting carrier aggregation are defined in terms of single carrier requirements. + +For *SAN type 1-O* 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 1: *SAN type 1-O* in normal operating conditions in FDD operation is 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 TS 38.181[3]. + +In tests performed with signal generators a synchronization signal may be provided from the SAN to the signal generator, to enable correct timing of the wanted signal. + +Whenever the "RX antennas" term is used for the radiated performance requirements description, it shall refer to the *demodulation branches* (i.e. not physical antennas of the antenna array). + +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 power in a slot on a RIB. + +*N* is the noise density integrated in a bandwidth corresponding to the *transmission bandwidth* over the duration where signal energy exists on a RIB. + +## 11.1.2 OTA demodulation branches + +Radiated performance requirements are only specified for up to 2 *demodulation branches*. + +If the *SAN type 1-O* uses polarization diversity and has the ability to maintain isolation between the signals for each of the *demodulation branches*, then radiated performance requirements can be tested for up to two *demodulation branches* (i.e. 1RX or 2RX test setups). When tested for two *demodulation branches*, each demodulation branch maps to one polarization. + +If the *SAN type 1-O* does not use polarization diversity then radiated performance requirements can only be tested for a single *demodulation branch* (i.e. 1RX test setup). + +## 11.2 Performance requirements for PUSCH + +### 11.2.1 Requirements for PUSCH with transform precoding disabled + +Apply the requirements defined in clause 8.2.1. + +### 11.2.2 Requirements for PUSCH with transform precoding enabled + +Apply the requirements defined in clause 8.2.2. + +### 11.2.3 Requirements for UL timing adjustment + +Apply the requirements defined in clause 8.2.3. + +### 11.2.4 Requirements for PUSCH repetition Type A + +Apply the requirements defined in clause 8.2.4. + +## 11.3 Performance requirements for PUCCH + +### 11.3.1 Requirements for *SAN type 1-O* + +#### 11.3.1.1 DTX to ACK probability + +Apply the requirements defined in clause 8.3.1. + +#### 11.3.1.2 Performance requirements for PUCCH format 0 + +Apply the requirements defined in clause 8.3.2 for 1Rx and 2Rx. + +#### 11.3.1.3 Performance requirements for PUCCH format 1 + +Apply the requirements defined in sub-clause 8.3.3 for 1Rx and 2Rx. + +#### 11.3.1.4 Performance requirements for PUCCH format 2 + +Apply the requirements defined in clause 8.3.4 for 1Rx and 2Rx. + +#### 11.3.1.5 Performance requirements for PUCCH format 3 + +Apply the requirements defined in clause 8.3.5 for 1Rx and 2Rx. + +#### 11.3.1.6 Performance requirements for PUCCH format 4 + +Apply the requirements defined in clause 8.3.6 for 1Rx and 2Rx. + +#### 11.3.1.7 Performance requirements for multi-slot PUCCH + +Apply the requirements defined in clause 8.3.7 for 1Rx and 2Rx. + +## 11.4 Performance requirements for PRACH + +### 11.4.1 PRACH False alarm probability + +Apply the requirements defined in clause 8.4.1. + +### 11.4.2 PRACH detection requirements + +Apply the requirements defined in clause 8.4.2. + +## Annex A (normative): Reference measurement channels + +### A.1 Fixed Reference Channels for RF Rx requirements in FR1 (QPSK, R=1/3) + +The parameters for the reference measurement channels are specified in table A.1-1 for FR1 reference sensitivity level, ACS, out-of-band blocking, in-channel selectivity, OTA sensitivity, OTA reference sensitivity level, OTA ACS, OTA out-of-band blocking and OTA in-channel selectivity. + +The reference measurement channels for the dynamic range requirement are captured in annex A.2. + +**Table A.1-1: Fixed Reference Channels for SAN Rx requirements, FR1** + +| Reference channel | G-FR1-A1-1 | G-FR1-A1-2 | G-FR1-A1-3 | G-FR1-A1-4 | G-FR1-A1-5 | G-FR1-A1-6 | G-FR1-A1-7 | G-FR1-A1-8 | G-FR1-A1-9 | +|-----------------------------------------------|------------|------------|------------|------------|------------|------------|------------|------------|------------| +| Subcarrier spacing (kHz) | 15 | 30 | 60 | 15 | 30 | 60 | 15 | 30 | 60 | +| Allocated resource blocks | 25 | 11 | 11 | 106 | 51 | 24 | 15 | 6 | 6 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 1/3 | 1/3 | 1/3 | 1/3 | 1/3 | 1/3 | 1/3 | 1/3 | 1/3 | +| Payload size (bits) | 2152 | 984 | 984 | 9224 | 4352 | 2088 | 1320 | 528 | 528 | +| Transport block CRC (bits) | 16 | 16 | 16 | 24 | 24 | 16 | 16 | 16 | 16 | +| Code block CRC size (bits) | - | - | - | 24 | - | - | - | - | - | +| Number of code blocks - C | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | +| Code block size including CRC (bits) (Note 3) | 2168 | 1000 | 1000 | 4648 | 4376 | 2104 | 1336 | 544 | 544 | +| Total number of bits per slot | 7200 | 3168 | 3168 | 30528 | 14688 | 6912 | 4320 | 1728 | 1728 | +| Total symbols per slot | 3600 | 1584 | 1584 | 15264 | 7344 | 3456 | 2160 | 864 | 864 | + +NOTE 1: *UL-DMRS-config-type* = 1 with *UL-DMRS-max-len* = 1, *UL-DMRS-add-pos* = 1 with *l0* = 2, *l* = 11 as per table 6.4.1.1.3-3 of TS 38.211 [5]. + +NOTE 2: MCS index 4 and target coding rate = 308/1024 are adopted to calculate payload size for receiver sensitivity and in-channel selectivity. + +NOTE 3: Code block size including CRC (bits) equals to *K'* in clause 5.2.2 of TS 38.212 [10]. + +### A.2 Fixed Reference Channels for dynamic range (16QAM, R=2/3) + +The parameters for the reference measurement channels are specified in table A.2-1 for FR1 dynamic range and OTA dynamic range. + +**Table A.2-1: Fixed Reference Channels for dynamic range and OTA dynamic range, FR1** + +| Reference channel | G-FR1-A2-1 | G-FR1-A2-2 | G-FR1-A2-3 | G-FR1-A2-4 | G-FR1-A2-5 | G-FR1-A2-6 | +|-----------------------------------------------|------------|------------|------------|------------|------------|------------| +| Subcarrier spacing (kHz) | 15 | 30 | 60 | 15 | 30 | 60 | +| Allocated resource blocks | 25 | 11 | 11 | 106 | 51 | 24 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | +| Code rate (Note 2) | 2/3 | 2/3 | 2/3 | 2/3 | 2/3 | 2/3 | +| Payload size (bits) | 9224 | 4032 | 4032 | 38936 | 18960 | 8968 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | - | - | 24 | 24 | 24 | +| Number of code blocks – C | 2 | 1 | 1 | 5 | 3 | 2 | +| Code block size including CRC (bits) (Note 3) | 4648 | 4056 | 4056 | 7816 | 6352 | 4520 | +| Total number of bits per slot | 14400 | 6336 | 6336 | 61056 | 29376 | 13824 | +| Total symbols per slot | 3600 | 1584 | 1584 | 15264 | 7344 | 3456 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS, additional DM-RS position = pos1 with $l_0 = 2$ , $l = 11$ as per table 6.4.1.1.3-3 of TS 38.211 [5]. + +NOTE 2: MCS index 16 and target coding rate = 658/1024 are adopted to calculate payload size. + +NOTE 3: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [10]. + +## A.3 Fixed Reference Channels for performance requirements (QPSK, R=308/1024) + +The parameters for the reference measurement channel are specified in table A.3-1 for FR1 PUSCH performance requirements: + +- FRC parameters are specified in table A.3-1 for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos0 and 1 transmission layer. +- FRC parameters are specified in table A.3-2 for FR1 PUSCH with transform precoding enabled, additional DM-RS position = pos0 and 1 transmission layer. + +**Table A.3-1: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=308/1024)** + +| Reference channel | G-FR1-A3-1 | G-FR1-A3-2 | G-FR1-A3-3 | G-FR1-A3-4 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------|------------|------------| +| Subcarrier spacing (kHz) | 15 | 15 | 30 | 30 | +| Allocated resource blocks | 25 | 12 | 24 | 12 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | +| Modulation | QPSK | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 308/1024 | 308/1024 | 308/1024 | 308/1024 | +| Payload size (bits) | 2152 | 1032 | 2024 | 1032 | +| Transport block CRC (bits) | 16 | 16 | 16 | 16 | +| Code block CRC size (bits) | - | - | - | - | +| Number of code blocks - C | 1 | 1 | 1 | 1 | +| Code block size including CRC (bits) (Note 2) | 2168 | 1048 | 2040 | 1048 | +| Total number of bits per slot | 7200 | 3456 | 6912 | 3456 | +| Total resource elements per slot | 3600 | 1728 | 3456 | 1728 | +| NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1, $l_0 = 2$ and $l = 11$ for PUSCH mapping type A, $l_0 = 0$ and $l = 10$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [5]. | | | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [10]. | | | | | + +**Table A.3-2: FRC parameters for FR1 PUSCH performance requirements, transform precoding enabled, additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=308/1024)** + +| Reference channel | G-FR1-A3-5 | G-FR1-A3-6 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------| +| Subcarrier spacing (kHz) | 15 | 30 | +| Allocated resource blocks | 25 | 24 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 12 | 12 | +| Modulation | QPSK | QPSK | +| Code rate (Note 2) | 308/1024 | 308/1024 | +| Payload size (bits) | 2152 | 2088 | +| Transport block CRC (bits) | 16 | 16 | +| Code block CRC size (bits) | - | - | +| Number of code blocks - C | 1 | 1 | +| Code block size including CRC (bits) (Note 2) | 2168 | 2104 | +| Total number of bits per slot | 7200 | 6912 | +| Total resource elements per slot | 3600 | 3456 | +| NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1, $l_0 = 2$ and $l = 11$ for PUSCH mapping type A, $l_0 = 0$ and $l = 10$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [5]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [10]. | | | + +## A.3A Fixed Reference Channels for performance requirements (QPSK, R=99/1024) + +The parameters for the reference measurement channel are specified in table A.3A-1 for FR1 PUSCH performance requirements: + +- FRC parameters are specified in table A.3A-1 for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer. + +**Table A.3A-1: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=99/1024)** + +| Reference channel | G-FR1-A3A-1 | G-FR1-A3A-2 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Subcarrier spacing (kHz) | 15 | 30 | +| Allocated resource blocks | 25 | 24 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 12 | 12 | +| Modulation | QPSK | QPSK | +| Code rate (Note 2) | 99/1024 | 99/1024 | +| Payload size (bits) | 704 | 672 | +| Transport block CRC (bits) | 16 | 16 | +| Code block CRC size (bits) | - | - | +| Number of code blocks - C | 1 | 1 | +| Code block size including CRC (bits) (Note 2) | 720 | 688 | +| Total number of bits per slot | 7200 | 6912 | +| Total resource elements per slot | 3600 | 3456 | +| NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1, $l_0 = 2$ and $l = 11$ for PUSCH mapping type A, $l_0 = 0$ and $l = 10$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [5]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [10]. | | | + +## A.4 PRACH test preambles + +**Table A.4-1 Test preambles in FR1** + +| Burst format | SCS (kHz) | Ncs | Logical sequence index | v | +|--------------|-----------|-----|------------------------|----| +| 0 | 1.25 | 13 | 22 | 32 | +| 2 | 1.25 | 13 | 22 | 32 | +| B4, C2 | 15 | 23 | 0 | 0 | +| | 30 | 46 | 0 | 0 | + +## Annex B (normative): Error Vector Magnitude (FR1) + +### B.1 Reference point for measurement + +The EVM shall be measured at the point after the FFT and a zero-forcing (ZF) equalizer in the receiver, as depicted in figure B.1-1 below. + +![Figure B.1-1: Reference point for EVM measurement. The diagram shows a signal flow from SAN TX to Remove CP, then to FFT, then to Per-subcarrier Amplitude/phase correction, and finally to Symbol detection/decoding. A block labeled 'Pre-/post FFT time / frequency synchronization' has dashed arrows pointing to the Remove CP, FFT, and Per-subcarrier Amplitude/phase correction blocks. A dashed arrow from a 'Reference point for EVM measurement' block points to the Per-subcarrier Amplitude/phase correction block.](694df81535f89c7bfb9ef0df6f130dc0_img.jpg) + +``` + +graph LR + SAN_TX[SAN TX] --> Remove_CP[Remove CP] + Remove_CP --> FFT[FFT] + FFT --> Per_subcarrier[Per-subcarrier Amplitude/phase correction] + Per_subcarrier --> Symbol_Detection[Symbol detection/decoding] + Sync[Pre-/post FFT time / frequency synchronization] -.-> Remove_CP + Sync -.-> FFT + Sync -.-> Per_subcarrier + Ref[Reference point for EVM measurement] -.-> Per_subcarrier + +``` + +Figure B.1-1: Reference point for EVM measurement. The diagram shows a signal flow from SAN TX to Remove CP, then to FFT, then to Per-subcarrier Amplitude/phase correction, and finally to Symbol detection/decoding. A block labeled 'Pre-/post FFT time / frequency synchronization' has dashed arrows pointing to the Remove CP, FFT, and Per-subcarrier Amplitude/phase correction blocks. A dashed arrow from a 'Reference point for EVM measurement' block points to the Per-subcarrier Amplitude/phase correction block. + +Figure B.1-1: Reference point for EVM measurement + +## B.2 Basic unit of measurement + +The basic unit of EVM measurement is defined over one slot in the time domain and $N_{BW}^{RB}$ subcarriers in the frequency domain: + +$$EVM = \sqrt{\frac{\sum_{t \in T} \sum_{f \in F(t)} |Z'(t, f) - I(t, f)|^2}{\sum_{t \in T} \sum_{f \in F(t)} |I(t, f)|^2}}$$ + +where + +$T$ is the set of symbols with the considered modulation scheme being active within the slot, + +$F(t)$ is the set of subcarriers within the $N_{BW}^{RB}$ subcarriers with the considered modulation scheme being active in symbol $t$ , + +$I(t, f)$ is the ideal signal reconstructed by the measurement equipment in accordance with relevant Tx models, + +$Z'(t, f)$ is the modified signal under test defined in annex B.3. + +NOTE: Although the basic unit of measurement is one slot, the equalizer is calculated over 10 ms measurement interval to reduce the impact of noise in the reference signals. The boundaries of the 10 ms measurement intervals need not be aligned with radio frame boundaries. + +## B.3 Modified signal under test + +Implicit in the definition of EVM is an assumption that the receiver is able to compensate a number of transmitter impairments. The signal under test is equalized and decoded according to: + +$$Z'(t, f) = \frac{FFT\{z(v - \Delta \tilde{t}) \cdot e^{-j2\pi \tilde{f} v}\} e^{j2\pi f \Delta \tilde{t}}}{\tilde{a}(f) \cdot e^{j\tilde{\phi}(f)}}$$ + +where + +$z(v)$ is the time domain samples of the signal under test. + +$\Delta\tilde{t}$ is the sample timing difference between the FFT processing window in relation to nominal timing of the ideal signal. Note that two timing offsets are determined, the corresponding EVM is measured and the maximum used as described in annex B.7. + +$\Delta\tilde{f}$ is the RF frequency offset. + +$\tilde{\varphi}(f)$ is the phase response of the TX chain. + +$\tilde{a}(f)$ is the amplitude response of the TX chain. + +## B.4 Estimation of frequency offset + +The observation period for determining the frequency offset $\Delta\tilde{f}$ shall be 1 slot. + +## B.5 Estimation of time offset + +### B.5.1 General + +The observation period for determining the sample timing difference $\Delta\tilde{t}$ shall be 1 slot. + +In the following $\Delta\tilde{c}$ represents the middle sample of the EVM window of length $W$ (defined in annex B.5.2) or the last sample of the first window half if $W$ is even. + +$\Delta\tilde{c}$ is estimated so that the EVM window of length $W$ is centred on the measured cyclic prefix of the considered OFDM symbol. To minimize the estimation error the timing shall be based on demodulation reference signals. To limit time distortion of any transmit filter the reference signals in the 1 outer RBs are not taken into account in the timing estimation + +Two values for $\Delta\tilde{t}$ are determined: + +$$\Delta\tilde{t}_l = \Delta\tilde{c} + \alpha - \left\lfloor \frac{W}{2} \right\rfloor \text{ and}$$ + +$$\Delta\tilde{t}_h = \Delta\tilde{c} + \left\lfloor \frac{W}{2} \right\rfloor \text{ where } \alpha = 0 \text{ if } W \text{ is odd and } \alpha = 1 \text{ if } W \text{ is even.}$$ + +When the cyclic prefix length varies from symbol to symbol then $T$ shall be further restricted to the subset of symbols with the considered modulation scheme being active and with the considered cyclic prefix length type. + +### B.5.2 Window length + +Table B.5.2-1, B.5.2-2, B.5.2-3 specify the EVM window length ( $W$ ) for normal CP. + +**Table B.5.2-1: EVM window length for normal CP, FR1, 15 kHz SCS** + +| Channel bandwidth (MHz) | FFT size | CP length for symbols 1-6 and 8-13 in FFT samples | EVM window length $W$ | Ratio of $W$ to total CP length for symbols 1-6 and 8-13 (Note) (%) | +|-------------------------|----------|---------------------------------------------------|-----------------------|---------------------------------------------------------------------| +| 5 | 512 | 36 | 14 | 40 | +| 10 | 1024 | 72 | 28 | 40 | +| 15 | 1536 | 108 | 44 | 40 | +| 20 | 2048 | 144 | 58 | 40 | + +NOTE: These percentages are informative and apply to a slot's symbols 1 to 6 and 8 to 13. Symbols 0 and 7 have a longer CP and therefore a lower percentage. + +**Table B.5.2-2: EVM window length for normal CP, FR1, 30 kHz SCS** + +| Channel bandwidth (MHz) | FFT size | CP length for symbols 1-13 in FFT samples | EVM window length $W$ | Ratio of $W$ to total CP length for symbols 1-13 (Note) (%) | +|-------------------------|----------|-------------------------------------------|-----------------------|-------------------------------------------------------------| +| 5 | 256 | 18 | 8 | 40 | +| 10 | 512 | 36 | 14 | 40 | +| 15 | 768 | 54 | 22 | 40 | +| 20 | 1024 | 72 | 28 | 40 | + +NOTE: These percentages are informative and apply to a slot's symbols 1 through 13. Symbol 0 has a longer CP and therefore a lower percentage. + +**Table B.5.2-3: EVM window length for normal CP, FR1, 60 kHz SCS** + +| Channel bandwidth (MHz) | FFT size | CP length in FFT samples | EVM window length $W$ | Ratio of $W$ to total CP length (Note) (%) | +|-------------------------|----------|--------------------------|-----------------------|--------------------------------------------| +| 10 | 256 | 18 | 8 | 40 | +| 15 | 384 | 27 | 11 | 40 | +| 20 | 512 | 36 | 14 | 40 | + +NOTE: These percentages are informative and apply to all OFDM symbols within subframe except for symbol 0 of slot 0 and slot 2. Symbol 0 of slot 0 and slot 2 may have a longer CP and therefore a lower percentage. + +Table B.5.2-4 below specifies the EVM window length ( $W$ ) for extended CP. The number of CP samples excluded from the EVM window is the same as for normal CP length. + +**Table B.5.2-4: EVM window length for extended CP, FR1, 60 kHz SCS** + +| Channel bandwidth (MHz) | FFT size | CP length in FFT samples | EVM window length $W$ | Ratio of $W$ to total CP length (Note) (%) | +|-------------------------|----------|--------------------------|-----------------------|--------------------------------------------| +| 10 | 256 | 64 | 54 | 84 | +| 15 | 384 | 96 | 80 | 83 | +| 20 | 512 | 128 | 106 | 83 | + +NOTE: These percentages are informative. + +## B.6 Estimation of TX chain amplitude and frequency response parameters + +The equalizer coefficients $\tilde{a}(f)$ and $\tilde{\varphi}(f)$ are determined as follows: + +1. Calculate the complex ratios (amplitude and phase) of the post-FFT acquired signal $Z'(t, f)$ and the post-FFT ideal signal $I_2(t, f)$ , for each reference signal, over 10ms measurement interval. This process creates a set of complex ratios: + +$$a(t, f) \cdot e^{j\varphi(t, f)} = \frac{Z'(t, f)}{I_2(t, f)}$$ + +Where the post-FFT ideal signal $I_2(t, f)$ is constructed by the measuring equipment according to the relevant TX specifications, using the following parameters: i.e. nominal demodulation reference signals, (all other modulation symbols are set to 0 V), nominal carrier frequency, nominal amplitude and phase for each applicable subcarrier, nominal timing. + +2. Perform time averaging at each reference signal subcarrier of the complex ratios, the time-averaging length is 10ms measurement interval. Prior to the averaging of the phases $\varphi(t_i, f)$ an unwrap operation must be performed according to the following definition: The unwrap operation corrects the radian phase angles of $\varphi(t_i, f)$ by adding multiples of $2\pi$ when absolute phase jumps between consecutive time instances $t_i$ are greater than or equal to the jump tolerance of $\pi$ radians. This process creates an average amplitude and phase for each reference signal subcarrier (i.e. every second subcarrier). + +$$a(f) = \frac{\sum_{i=1}^N a(t_i, f)}{N}$$ + +$$\varphi(f) = \frac{\sum_{i=1}^N \varphi(t_i, f)}{N}$$ + +Where $N$ is the number of reference signal; time-domain locations $t_i$ from $Z'(t, f)$ for each reference signal subcarrier $f$ . + +3. The equalizer coefficients for amplitude and phase $\hat{a}(f)$ and $\hat{\varphi}(f)$ at the reference signal subcarriers are obtained by computing the moving average in the frequency domain of the time-averaged reference signal subcarriers, i.e. every second subcarrier. The moving average window size is 19 and averaging is over the DM-RS subcarriers in the allocated RBs. For DM-RS subcarriers at or near the edge of the channel, or when the number of available DM-RS subcarriers within a set of contiguously allocated RBs is smaller than the moving average window size, the window size is reduced accordingly as per figure B.6-1. +4. Perform linear interpolation from the equalizer coefficients $\hat{a}(f)$ and $\hat{\varphi}(f)$ to compute coefficients $\tilde{a}(f)$ , $\tilde{\varphi}(f)$ for each subcarrier. + +![Figure B.6-1: Reference subcarrier smoothing in the frequency domain. The figure contains two diagrams, A and B, illustrating the process of smoothing reference subcarriers. Diagram A shows 'Moving averaging at channel edge', where subcarriers are averaged using a window that grows from 3 subcarriers at the start to 19 subcarriers at the 10th subcarrier, then shrinks back to 1 at the upper edge. Diagram B shows 'Moving averaging for the case when the number of available reference subcarriers within a set of contiguously allocated RBs is smaller than the moving average window size', where a reduced window size of 5 subcarriers is used for the entire set of 7 subcarriers. Both diagrams show a curve representing the EVM values across subcarriers, with arrows indicating the averaging process.](92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg) + +The subsequent 7 subcarriers are averaged over 5, 7 .. 17 subcarriers + +From the 10th subcarrier onwards the window size is 19 until the upper edge of the channel is reached and the window size reduces back to 1 + +The second reference subcarrier is the average of the first three subcarriers + +The first reference subcarrier is not averaged + +Reference subcarriers + +A. Moving averaging at channel edge + +Figure B shows an example of 1RB allocation using a reduced window size of five subcarriers for averaging. The same method applies for RB allocations with fewer than 19 subcarriers available for the moving average size. For the case of 2 and 3 RB allocations, 11 and 17 are the window sizes, respectively. + +The first, second and third reference subcarriers are the average of the five subcarriers on left + +The first, second and third reference subcarriers are the average of the five subcarriers on right + +Reference subcarriers + +B. Moving averaging for the case when the number of available reference subcarriers within a set of contiguously allocated RBs is smaller than the moving average window size + +Figure B.6-1: Reference subcarrier smoothing in the frequency domain. The figure contains two diagrams, A and B, illustrating the process of smoothing reference subcarriers. Diagram A shows 'Moving averaging at channel edge', where subcarriers are averaged using a window that grows from 3 subcarriers at the start to 19 subcarriers at the 10th subcarrier, then shrinks back to 1 at the upper edge. Diagram B shows 'Moving averaging for the case when the number of available reference subcarriers within a set of contiguously allocated RBs is smaller than the moving average window size', where a reduced window size of 5 subcarriers is used for the entire set of 7 subcarriers. Both diagrams show a curve representing the EVM values across subcarriers, with arrows indicating the averaging process. + +Figure B.6-1: Reference subcarrier smoothing in the frequency domain + +## B.7 Averaged EVM + +EVM is averaged over all allocated downlink resource blocks with the considered modulation scheme in the frequency domain, and a minimum of $N_{dl}$ slots where $N_{dl}$ is the number of slots in a 10 ms measurement interval. + +For FDD the averaging in the time domain equals the $N_{dl}$ slot duration of the 10 ms measurement interval from the equalizer estimation step. + +$$\overline{EVM}_{frame} = \sqrt{\frac{1}{\sum_{i=1}^{N_{dl}} N_i} \sum_{i=1}^{N_{dl}} \sum_{j=1}^{N_i} EVM_{i,j}^2}$$ + +- Where $N_i$ is the number of resource blocks with the considered modulation scheme in slot $i$ . +- The EVM requirements shall be tested against the maximum of the RMS average at the window $W$ extremities of the EVM measurements: +- Thus $\overline{EVM}_{frame,l}$ is calculated using $\Delta\tilde{t} = \Delta\tilde{t}_l$ in the expressions above and $\overline{EVM}_{frame,h}$ is calculated using $\Delta\tilde{t} = \Delta\tilde{t}_h$ in the $\overline{EVM}_{frame}$ calculation. +- Thus we get: + +$$\overline{EVM} = \max(\overline{EVM}_{frame,l}, \overline{EVM}_{frame,h})$$ + +## Annex C (normative): Characteristics of the interfering signals + +The interfering signal shall be a PUSCH or PDSCH containing data and DM-RS symbols. Normal cyclic prefix is used. The data content shall be uncorrelated to the wanted signal and modulated according to clause 6 of TS 38.211 [9]. Mapping of PUSCH or PDSCH modulation to receiver requirement are specified in table C-1. + +**Table C-1: Modulation of the interfering signal** + +| Receiver requirement | Modulation | Interfering signal | Clauses | +|------------------------------|------------|--------------------|-----------------| +| In-channel selectivity | 16QAM | PUSCH | 7.8
10.9 | +| Adjacent channel selectivity | QPSK | PDSCH | 7.4.1
10.5.1 | + +## Annex D (Normative): Propagation conditions + +### D.1 Static propagation condition + +The propagation for the static performance measurement is an Additive White Gaussian Noise (AWGN) environment. No fading or multi-paths exist for this propagation model. + +### D.2 Multi-path fading propagation conditions + +The multipath propagation conditions consist of several parts: + +- A delay profile in the form of a "tapped delay-line", characterized by a number of taps at fixed positions on a sampling grid. The profile can be further characterized by the r.m.s. delay spread and the maximum delay spanned by the taps. +- A combination of channel model parameters that include the Delay profile and the Doppler spectrum that is characterized by a classical spectrum shape and a maximum Doppler frequency. + +#### D.2.1 Delay profiles + +The delay profiles are simplified from the TR 38.811 [13] TDL models. The simplification steps are shown below for information. These steps are only used when new delay profiles are created. Otherwise, the delay profiles specified in G.2.1.1 can be used as such. + +- Step 1: Use the original TDL model from TR 38.811 [13]. +- Step 2: Re-order the taps in ascending delays +- Step 3: Perform delay scaling according to the procedure described in clause 7.7.2 in TR 38.901 [12]. +- Step 4: Apply the quantization to the delay resolution 5 ns. This is done simply by rounding the tap delays to the nearest multiple of the delay resolution. +- Step 5: If multiple Rayleigh taps are rounded to the same delay bin, merge them by calculating their linear power sum. +- Step 6: If there is a LOS path in the model, the power for all paths could be slightly adjusted to keep the RMS delay spread is close to target delay spread and mean power is 0dB. + +- Step 7: Round the amplitudes of taps to one decimal (e.g. -8.78 dB → -8.8 dB) +- Step 8: If the delay spread has slightly changed due to the tap merge, adjust the final delay spread by increasing or decreasing the power of the last tap so that the delay spread is corrected. +- Step 9: Re-normalize the highest Rayleigh tap to 0 dB when there is no LOS path in the model. + +Note 1: Some values of the delay profile created by the simplification steps may differ from the values in tables G.2.1.1-2 and G.2.1.1-3 for the corresponding model. + +Note 2: For Step 5 and Step 6, the power values are expressed in the linear domain using 6 digits of precision. The operations are in the linear domain. + +### D.2.1.1 Delay profiles for FR1 + +The delay profiles for FR1 are selected to be representative of low, medium and high delay spread environment. The resulting model parameters are specified in table D.2.1.1-1 and the tapped delay line models are specified in tables D.2.1.1-2 ~ D.2.1.1-4. + +**Table D.2.1.1-1: Delay profiles for NR channel models** + +| Model | Number of channel taps | Delay spread (r.m.s.) | Maximum excess tap delay (span) | Delay resolution | +|-------------|------------------------|-----------------------|---------------------------------|------------------| +| NTN-TDLA100 | 3 | 100 ns | 285 | 5ns | +| NTN-TDLC5 | 2 | 5 ns | 60 | 5ns | + +**Table D.2.1.1-2: NTN-TDLA100 (DS = 100 ns)** + +| Tap # | Delay (ns) | Power (dB) | Fading distribution | +|-------|------------|------------|---------------------| +| 1 | 0 | 0 | Rayleigh | +| 2 | 110 | -4.7 | Rayleigh | +| 3 | 285 | -6.5 | Rayleigh | + +**Table D.2.1.1-3: NTN-TDLC5 (DS = 5 ns)** + +| Tap # | Delay (ns) | Power (dB) | Fading distribution | +|-------|------------|------------|---------------------| +| 1 | 0 | -0.6 | LOS path | +| | 0 | -8.9 | Rayleigh | +| 2 | 60 | -21.5 | Rayleigh | + +### D.2.2 Combinations of channel model parameters + +The propagation conditions used for the performance measurements in multi-path fading environment are indicated as a combination of a channel model name and a maximum Doppler frequency, i.e., NTN-TDLA- or NTN-TDLC- where '' indicates the desired delay spread and '' indicates the maximum Doppler frequency (Hz). + +Table D.2.2-1 show the propagation conditions that are used for the performance measurements in multi-path fading environment. + +**Table D.2.2-1: Channel model parameters for FR1** + +| Combination name | Tapped delay line model | Maximum Doppler frequency | +|------------------|-------------------------|---------------------------| +| NTN-TDLA100-200 | NTN-TDLA100 | 200 Hz | +| NTN-TDLC5-200 | NTN-TDLC5 | 200 Hz | + +## D.2.3 MIMO channel correlation matrices + +The MIMO channel correlation matrices defined in annex D.2.3 apply for the antenna configuration using uniform linear arrays at both SAN and UE and for the antenna configuration using cross polarized antennas. + +### D.2.3.1 MIMO correlation matrices using Uniform Linear Array + +The MIMO channel correlation matrices defined in annex D.2.3.1 apply for the antenna configuration using uniform linear array (ULA) at both SAN and UE. + +#### D.2.3.1.1 Definition of MIMO correlation matrices + +Table D.2.3.1.1-1 defines the correlation matrix for the SAN. + +**Table D.2.3.1.1-1: SAN correlation matrix** + +| | gNB correlation | +|--------------|----------------------------------------------------------------------| +| One antenna | $R_{gNB} = 1$ | +| Two antennas | $R_{gNB} = \begin{pmatrix} 1 & \alpha \\ \alpha^* & 1 \end{pmatrix}$ | + +Table D.2.3.1.1-2 defines the correlation matrix for the UE: + +**Table D.2.3.1.1-2: UE correlation matrix** + +| | One antenna | +|----------------|--------------| +| UE correlation | $R_{UE} = 1$ | + +Table D.2.3.1.1-3 defines the channel spatial correlation matrix $R_{spat}$ . The parameters, $\alpha$ and $\beta$ in table D.2.3.1.1-3 defines the spatial correlation between the antennas at the SAN and UE respectively. + +**Table D.2.3.1.1-3: $R_{spat}$ correlation matrices** + +| | | +|----------|---------------------------------------------------------------------------------| +| 1x1 case | $R_{spat} = R_{SAN} = 1$ | +| 1x2 case | $R_{spat} = R_{SAN} = \begin{bmatrix} 1 & \alpha \\ \alpha^* & 1 \end{bmatrix}$ | + +For cases with more antennas at either SAN or UE or both, the channel spatial correlation matrix can still be expressed as the Kronecker product of $R_{UE}$ and $R_{SAN}$ according to $R_{spat} = R_{UE} \otimes R_{SAN}$ . + +#### D.2.3.1.2 MIMO correlation matrices at high, medium and low level + +The $\alpha$ and $\beta$ for different correlation types are given in table D.2.3.1.2-1. + +**Table D.2.3.1.2-1: Correlation for high, medium and low level** + +| Low correlation | | Medium correlation | | High correlation | | +|-----------------|---------|--------------------|---------|------------------|---------| +| $\alpha$ | $\beta$ | $\alpha$ | $\beta$ | $\alpha$ | $\beta$ | +| 0 | 0 | 0.9 | 0.3 | 0.9 | 0.9 | + +The correlation matrices for high, medium and low correlation are defined in table D.2.3.1.2-2, D.2.3.1.2-3 and D.2.3.1.2-4 as below. + +Table D.2.3.1.2-2: MIMO correlation matrices for high correlation + +| | | +|----------|---------------------------------------------------------------| +| 1x1 case | $R_{high} = \mathbf{I}_1$ | +| 1x2 case | $R_{high} = \begin{pmatrix} 1 & 0.9 \\ 0.9 & 1 \end{pmatrix}$ | + +Table D.2.3.1.2-3: MIMO correlation matrices for medium correlation + +| | | +|----------|-----| +| 1x1 case | N/A | +| 1x2 case | N/A | + +Table D.2.3.1.2-4: MIMO correlation matrices for low correlation + +| | | +|----------|--------------------------| +| 1x1 case | $R_{low} = \mathbf{I}_1$ | +| 1x2 case | $R_{low} = \mathbf{I}_2$ | + +In table D.2.3.1.2-4, $\mathbf{I}_d$ is a $d \times d$ identity matrix. + +NOTE: For completeness, the correlation matrices were defined for high, medium and low correlation but performance requirements exist only for low correlation. + +## D.3 Moving propagation conditions + +Figure D.3-1 illustrates the moving propagation conditions for the test of the UL timing adjustment performance. The time difference between the reference timing and the first tap is according Equation (D.3-1). The timing difference between moving UE and stationary UE is equal to $\Delta\tau - (T_A - 31) \times 16 \times 64 T_c$ for 15kHz SCS, $\Delta\tau - (T_A - 31) \times 16 \times 32 T_c$ for 30kHz SCS and $\Delta\tau - (T_A - 31) \times 16 \times 8 T_c$ for 120kHz SCS. The relative timing among all taps is fixed. The parameters for the moving propagation conditions are shown in Table D.3-1. + +![Figure D.3-1: Moving propagation conditions. A diagram showing a horizontal time axis with two points, t0 and t1. At t0, a solid vertical arrow labeled 'Ref' points upwards. At t1, a dashed vertical arrow labeled 'P1' points upwards. A horizontal double-headed arrow between t0 and t1 is labeled Δτ. To the right of t1, there are two more dashed vertical arrows of decreasing height, with a horizontal dashed line connecting their bases.](cf64ff479b0c6bc567effa28e2c1d2ea_img.jpg) + +Figure D.3-1: Moving propagation conditions. A diagram showing a horizontal time axis with two points, t0 and t1. At t0, a solid vertical arrow labeled 'Ref' points upwards. At t1, a dashed vertical arrow labeled 'P1' points upwards. A horizontal double-headed arrow between t0 and t1 is labeled Δτ. To the right of t1, there are two more dashed vertical arrows of decreasing height, with a horizontal dashed line connecting their bases. + +Figure D.3-1: Moving propagation conditions + +$$\Delta\tau = \frac{A}{2} \cdot \sin(\Delta\omega \cdot t) \quad (D.3-1)$$ + +**Table D.3-1: Parameters for UL timing adjustment** + +| Parameter | Scenario X | +|------------------|--------------------------------------------------------------| +| Channel model | Stationary UE: AWGN
Moving UE: NTN-TDLA100-200 Low | +| UE speed | 120 km/h | +| CP length | Normal | +| A | 15 kHz: 10 us
30 kHz: 5 us | +| $\Delta\omega$ | 15 kHz: 0.04 s -1
30 kHz: 0.08 s -1 | + + + +## Annex E (informative): Change history + +| Change history | | | | | | | | +|----------------|----------------|------------|----|-----|-----|-------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-01 | RAN4#101-bis-e | R4-2201830 | | | | Initial Skeleton Revised in R4-2203087 | 0.0.1 | +| 2022-01 | RAN4#101-bis-e | R4-2203087 | | | | Initial Skeleton | 0.0.1 | +| 2022-03 | RAN4#102-e | R4-2203955 | | | | TP for 38.108: clause 7.1&7.2 on Rx refsens sensitivity | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2205057 | | | | pCR to TS 38.108 -Radiated Tx general and transmit power | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207331 | | | | TP for 38.108: clause 5.3&5.4 on system parameters | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207335 | | | | TP for TS 38.108: General (5.1) and Operating Band (5.2) | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207336 | | | | Draft text proposal for Clause 4.4 Satellite Access Node classes - TS 38.108 | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207337 | | | | TP for 38.108: clause 4.3 requirement reference point | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207340 | | | | TP to TR 38.108 on 4.5 Regional Requirement | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207354 | | | | pCR to TS 38.108 - Scope and general | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207355 | | | | TP to TS 38.108: section 4 | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207356 | | | | TP to TS 38.108: section 3 | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207357 | | | | TP for 38.108: clause 9.7 OTA unwanted emissions | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207359 | | | | TP for TS 38.108 OTA output power dynamics(9.4) | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207361 | | | | TP to TS 38.108: 9.5 (OTA Tx ON/OFF), 9.6 (OTA TX signal quality) and 9.8 (OTA Tx IMD) | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207362 | | | | TP for 38.108: clause 9.3 OTA Satellite Access Node output power | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207363 | | | | TP for TS 38.108 Annex B | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207364 | | | | TP for 38.108: clause 10.5 OTA in-band selectivity and blocking | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207365 | | | | pCR to TS 38.108 - Radiated Rx general and sensitivity | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207366 | | | | TP for TS 38.108 OTA Rx requirements(10.3, 10.4,10.6 and 10.9) | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207368 | | | | TP to TS 38.108: section 10.7 (OTA Rx spur) and 10.8 (OTA Rx IMD) | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207371 | | | | TP to TS 38.108: section 10.7 (OTA Rx spur) and 10.8 (OTA Rx IMD) | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207372 | | | | Draft text proposal for Clause 6.1 and 6.2 Satellite Access Node output power - TS 38.108 | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207373 | | | | TP to TS 38.108: section 6.4 (Tx ON/OFF) and 6.5 (TX signal quality) | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207374 | | | | TP to TS 38.108: section 6.7 (Tx IMD) | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207377 | | | | pCR to TS 38.108 - In-band selectivity and blocking | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207378 | | | | TP for TS 38.108 Dynamic range(7.3) and In channel selectivity(7.8) | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207380 | | | | Draft text proposal for Clause 7.5 Out-of-band blocking - TS 38.108 | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207382 | | | | TP to TS 38.108: section 7.6 (Rx spur) and section 7.7 (Rx IMD) | 0.1.0 | +| 2022-03 | RAN4#102-e | R4-2207383 | | | | TP to TS 38.108: annex A (FRC) | 0.1.0 | +| 2022-05 | RAN4#103-e | R4-2208663 | | | | TP to TS 38.108 on Conducted receiver characteristics | 0.2.0 | +| 2022-05 | RAN4#103-e | R4-2210849 | | | | pCR for Clause 4.3 Requirement reference points - TS 38.108 | 0.2.0 | +| 2022-05 | RAN4#103-e | R4-2210850 | | | | pCR for Annex D - TS 38.108 | 0.2.0 | +| 2022-05 | RAN4#103-e | R4-2210854 | | | | TP for 38.108: clause 7.3.2 Conducted transmission characteristics | 0.2.0 | +| 2022-05 | RAN4#103-e | R4-2210855 | | | | pCR to TS 38.108 – Transmitter spurious | 0.2.0 | +| 2022-05 | RAN4#103-e | R4-2210856 | | | | pCR to TS 38.108 – cleanup - alignment | 0.2.0 | +| 2022-05 | RAN4#103-e | R4-2210857 | | | | TP to TS 38.108 on 6.0 Conducted transmitter characteristics | 0.2.0 | +| 2022-05 | RAN4#103-e | R4-2210861 | | | | pCR for Clause 7.4 In-band selectivity and blocking - TS 38.108 | 0.2.0 | +| 2022-05 | RAN4#103-e | R4-2210862 | | | | pCR for Clause 7.5 Out-of-band blocking - TS 38.108 | 0.2.0 | +| 2022-05 | RAN4#103-e | R4-2210863 | | | | pCR for Clause 7.6 Receiver spurious emissions - TS 38.108 | 0.2.0 | +| 2022-05 | RAN4#103-e | R4-2210864 | | | | pCR for Clause 10.6.2 Minimum requirement for SAN type 1-O - TS 38.108 | 0.2.0 | +| 2022-05 | RAN4#103-e | R4-2210873 | | | | TP for TS 38.108, 6.6.4 Operating band unwanted emissions | 0.2.0 | +| 2022-05 | RAN4#103-e | R4-2211135 | | | | TP to TS 38.108: TS corrections; RF requirements | 0.2.0 | +| 2022-05 | RAN4#103-e | R4-2211202 | | | | TP to TS 38.108: removal of extreme conditions requirements | 0.2.0 | +| 2022-06 | RAN#96 | RP-221342 | | | | For RAN 1-step approval | 1.0.0 | + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|----------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-06 | RAN#96 | | | | | Approved by plenary – Rel-17 spec under change control | 17.0.0 | +| 2022-09 | RAN#97 | RP-222035 | 0001 | 1 | F | CR to TS 38.108 - conducted Tx requirements issues fixes | 17.1.0 | +| 2022-09 | RAN#97 | RP-222035 | 0002 | 1 | F | CR to TS 38.108 - conducted Rx requirements issues fixes | 17.1.0 | +| 2022-09 | RAN#97 | RP-222035 | 0003 | 1 | F | CR to TS 38.108 - OTA Tx requirements issues fixes | 17.1.0 | +| 2022-09 | RAN#97 | RP-222035 | 0004 | 1 | F | CR to TS 38.108 - OTA Rx requirements issues fixes | 17.1.0 | +| 2022-09 | RAN#97 | RP-222035 | 0006 | 1 | D | Correction of OTA ACLR absolute basic limit | 17.1.0 | +| 2022-09 | RAN#97 | RP-222035 | 0008 | 1 | F | Correction of OTA receiver spurious emission requirement | 17.1.0 | +| 2022-09 | RAN#97 | RP-222035 | 0010 | 1 | F | Correction of conducted receiver spurious emission requirement | 17.1.0 | +| 2022-09 | RAN#97 | RP-222035 | 0011 | | F | CR to TS 38.108: removal of NTN SAN output power accuracy requirements for the extreme test conditions, Rel-17 | 17.1.0 | +| 2022-12 | RAN#98-e | RP-223306 | 0012 | 1 | F | Corrections to SAN TS 38.108 | 17.2.0 | +| 2022-12 | RAN#98-e | RP-223306 | 0013 | | F | CR for TS 38.108, Correct definition order in sub-clause 3.1 | 17.2.0 | +| 2022-12 | RAN#98-e | RP-223311 | 0022 | 1 | B | Description of general performance part sections for SAN TS 38.108 | 17.2.0 | +| 2022-12 | RAN#98-e | RP-223303 | 0024 | | B | Big CR on NTN SAN performance requirements (TS38.108, Rel-17) | 17.2.0 | +| 2022-12 | RAN#98-e | RP-223311 | 0025 | | F | CR to TS 38.108: removal of colocation requirements | 17.2.0 | +| 2023-03 | RAN#99 | RP-230516 | 0028 | 1 | F | CR to TS 38.108: OBUE and open issues clarifications | 17.3.0 | +| 2023-03 | RAN#99 | RP-230516 | 0027 | 1 | F | CR for TS 38.108, Correct unwanted emission requirements applicability for SAN type 1-H | 17.3.0 | +| 2023-03 | RAN#99 | RP-230516 | 0030 | 1 | F | CR to TS 38.108: corrections | 17.3.0 | +| 2023-06 | RAN#100 | RP-231344 | 0036 | | F | CR on NTN SAN performance requirements (TS38.108, Rel-17) | 17.4.0 | +| 2023-06 | RAN#100 | RP-231344 | 0037 | 1 | F | Corrections to SAN TS 38.108 | 17.4.0 | +| 2023-09 | RAN#101 | RP-232494 | 0038 | | F | CR for TS 38.108, Correction on antenna connector | 17.5.0 | +| 2023-09 | RAN#101 | RP-232494 | 0040 | 1 | F | CR to 38.108: Application of unwanted emissions requirements | 17.5.0 | +| 2023-09 | RAN#101 | RP-232494 | 0042 | | F | [INR_NTN_solutions-Perf] CR for channel model description in SAN PRACH demodulation requirement | 17.5.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-09 | RAN#101 | | | | | Approved by plenary – Rel-18 spec under change control | 18.0.0 | +| 2023-12 | RAN#102 | RP-233349 | 0045 | | A | CR for TS 38.108, Correction on out-of-band emissions | 18.1.0 | +| 2023-12 | RAN#102 | RP-233366 | 0046 | | B | CR to TS38.108 Introduction of the satellite L-/S-band | 18.1.0 | +| 2023-12 | RAN#102 | RP-233365 | 0048 | 1 | B | CR to TS 38.108: Introduction of an enhanced channel raster | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38115-1/124c6108c63173818afb8ed49521e22d_img.jpg b/marked/Rel-18/38_series/38115-1/124c6108c63173818afb8ed49521e22d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..644785de5cebed99e1eb3251ddafaf647772f918 --- /dev/null +++ b/marked/Rel-18/38_series/38115-1/124c6108c63173818afb8ed49521e22d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:136a9de31dcaae3d562a2a11805612de878c09edf0230926b12709479cc092e4 +size 31478 diff --git a/marked/Rel-18/38_series/38115-1/145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg b/marked/Rel-18/38_series/38115-1/145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bb4282cec886fe670a7fca4609d4cbddc6414ea --- /dev/null +++ b/marked/Rel-18/38_series/38115-1/145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b96030fb322b39dc0d2e6ada30220e96136b5bbe2125730f2b8472edc1e5f176 +size 30755 diff --git a/marked/Rel-18/38_series/38115-1/28f2f470a7b2446ae5f525123534383c_img.jpg b/marked/Rel-18/38_series/38115-1/28f2f470a7b2446ae5f525123534383c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1aad937db8d89ffd19483882851f2bd17019dd5b --- /dev/null +++ b/marked/Rel-18/38_series/38115-1/28f2f470a7b2446ae5f525123534383c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e829bde0a279eb8d2b19adf6b99f5b0cfc3f99f726cb00e3dfc5e8061b3403e +size 28492 diff --git a/marked/Rel-18/38_series/38115-1/4aeaa51a3999fab21171224e238cb571_img.jpg b/marked/Rel-18/38_series/38115-1/4aeaa51a3999fab21171224e238cb571_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6ae19dea7fbf2b3ca8e846b3c6796b926ec06f2 --- /dev/null +++ b/marked/Rel-18/38_series/38115-1/4aeaa51a3999fab21171224e238cb571_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17856e5b4dfe28ad887e5376ea819603fa2e2c3dd2b9ea6036c25b72cc3705ac +size 29029 diff --git a/marked/Rel-18/38_series/38115-1/4dd5f00d74e7db5bbb2d011609bcc43d_img.jpg b/marked/Rel-18/38_series/38115-1/4dd5f00d74e7db5bbb2d011609bcc43d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ae718031e26565074738455049cb3901f73603c --- /dev/null +++ b/marked/Rel-18/38_series/38115-1/4dd5f00d74e7db5bbb2d011609bcc43d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25de3c6c709d9966e7ed9e77f7e346e38ad257b7b71b40014afeeb341d8c0215 +size 31592 diff --git a/marked/Rel-18/38_series/38115-1/55048d730ad7a041082df5cc76d53219_img.jpg b/marked/Rel-18/38_series/38115-1/55048d730ad7a041082df5cc76d53219_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d70347dd2852ab2ad41b52cbe49b73fdaf1f2809 --- /dev/null +++ b/marked/Rel-18/38_series/38115-1/55048d730ad7a041082df5cc76d53219_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e45591d14deee4e7360598b5a917b228b7e1407c66caf409dabcdd9843e1c46 +size 37817 diff --git a/marked/Rel-18/38_series/38115-1/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38115-1/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1edcc9d814eff1823f002764f5aa33d0042b7b4 --- /dev/null +++ b/marked/Rel-18/38_series/38115-1/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e3363ab34b11e5ae86184b03060d870e81d9898b1372d2c55a53607477c0fb9 +size 9535 diff --git a/marked/Rel-18/38_series/38115-1/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38115-1/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b02fa68a1630c910d198a42d19ace9edf3a538c --- /dev/null +++ b/marked/Rel-18/38_series/38115-1/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0ed921b5eb3234dc9873ed23df067fd4a5acb1b554205a69ecbb9edccb8e289 +size 5733 diff --git a/marked/Rel-18/38_series/38115-1/69f52512bb7387a5dc9f952279513019_img.jpg b/marked/Rel-18/38_series/38115-1/69f52512bb7387a5dc9f952279513019_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b004e39b6a2bc59ff5efb64f9364484569b96479 --- /dev/null +++ b/marked/Rel-18/38_series/38115-1/69f52512bb7387a5dc9f952279513019_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9eb469b50f35907ad97f2cd1c74c10fbcb6957832907bc3ebcacf7a4249ec057 +size 16817 diff --git a/marked/Rel-18/38_series/38115-1/8a0a9aa5fac5d73eefb772afd44649f6_img.jpg b/marked/Rel-18/38_series/38115-1/8a0a9aa5fac5d73eefb772afd44649f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b074b16beb9825fddbd4a10233f27e11152297c --- /dev/null +++ b/marked/Rel-18/38_series/38115-1/8a0a9aa5fac5d73eefb772afd44649f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3673be6905ac9b0f84c9bf40321816f6b1ce74c81b9647c7e5556d24bd1f050f +size 43145 diff --git a/marked/Rel-18/38_series/38115-1/8f8caebe58364416a2eda21039d8c7bf_img.jpg b/marked/Rel-18/38_series/38115-1/8f8caebe58364416a2eda21039d8c7bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db827aecfa54190dfafa1673c0ac88ee45c1f875 --- /dev/null +++ b/marked/Rel-18/38_series/38115-1/8f8caebe58364416a2eda21039d8c7bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c3d409559b85da40d27bc19e6b92f9bd530aeeb251fa85176493e7591617cc3 +size 24562 diff --git a/marked/Rel-18/38_series/38115-1/9058545957858eea01975496aa340d5b_img.jpg b/marked/Rel-18/38_series/38115-1/9058545957858eea01975496aa340d5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..313a294ae0d21b26d3750261d6bd1df86312a214 --- /dev/null +++ b/marked/Rel-18/38_series/38115-1/9058545957858eea01975496aa340d5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01ad550ad0fd9bfc1ecb1e8ef19faaccdf80cbd15fe2bea5313e14f34051c4dd +size 36552 diff --git a/marked/Rel-18/38_series/38115-1/a9d7ac06dfdc2152f9b2fcf977a9ba6f_img.jpg b/marked/Rel-18/38_series/38115-1/a9d7ac06dfdc2152f9b2fcf977a9ba6f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a46c403216b10d04d2defad04459aa1e58fa1889 --- /dev/null +++ b/marked/Rel-18/38_series/38115-1/a9d7ac06dfdc2152f9b2fcf977a9ba6f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00168b29c41cc85ffd3013947f9e9c0fb37eaf5b137e43808e14212efdaa2ed9 +size 61957 diff --git a/marked/Rel-18/38_series/38115-1/bf2aa2e550e42aa4a70d02c8ce9e9f0d_img.jpg b/marked/Rel-18/38_series/38115-1/bf2aa2e550e42aa4a70d02c8ce9e9f0d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17005d52d2e6601b95e7efff855f8e3b6a2aaa96 --- /dev/null +++ b/marked/Rel-18/38_series/38115-1/bf2aa2e550e42aa4a70d02c8ce9e9f0d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73e647349225aab0a0dfc19d2614ec8f818de85630d62a41c0cb14e83361fba2 +size 60448 diff --git a/marked/Rel-18/38_series/38115-1/c6e0b9030f9fb81435eaf9cb71532614_img.jpg b/marked/Rel-18/38_series/38115-1/c6e0b9030f9fb81435eaf9cb71532614_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ed74440546497f60a0803b5ba6d9245620dea2c --- /dev/null +++ b/marked/Rel-18/38_series/38115-1/c6e0b9030f9fb81435eaf9cb71532614_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08b0f2bb057065a2bdf1803e8f3fab60932e89bfa7c7d21ba4c84b22cec2aaab +size 29517 diff --git a/marked/Rel-18/38_series/38115-1/e4c6fa93821e3546ee9fcae897ae2771_img.jpg b/marked/Rel-18/38_series/38115-1/e4c6fa93821e3546ee9fcae897ae2771_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc9a805c8babd64a7068ce3cb747abc124e031dc --- /dev/null +++ b/marked/Rel-18/38_series/38115-1/e4c6fa93821e3546ee9fcae897ae2771_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf6eb9fd9ee2dff931fb5f1cfd632fad15754034ff0a6f09bc27f7cacf5d3029 +size 17738 diff --git a/marked/Rel-18/38_series/38115-1/f92e919c70b7adda2d0e778889f44fae_img.jpg b/marked/Rel-18/38_series/38115-1/f92e919c70b7adda2d0e778889f44fae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6602eeeb8fcbf3179caf85d16230ecebd78ca8b --- /dev/null +++ b/marked/Rel-18/38_series/38115-1/f92e919c70b7adda2d0e778889f44fae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e456a8d3defa01676f20595f09665879f6e963766015ac5feb30f5ad7565fc9 +size 26524 diff --git a/marked/Rel-18/38_series/38115-1/raw.md b/marked/Rel-18/38_series/38115-1/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..14f65d41ea034399a1b88f660e3893885cd226f6 --- /dev/null +++ b/marked/Rel-18/38_series/38115-1/raw.md @@ -0,0 +1,3632 @@ + + +# 3GPP TS 38.115-1 V18.3.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Repeater 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, 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 ..... | 12 | +| 1 Scope..... | 14 | +| 2 References..... | 14 | +| 3 Definitions of terms, symbols and abbreviations..... | 15 | +| 3.1 Terms..... | 15 | +| 3.2 Symbols..... | 16 | +| 3.3 Abbreviations ..... | 16 | +| 4 General conducted test conditions and declarations ..... | 17 | +| 4.1 Measurement uncertainties and test requirements ..... | 17 | +| 4.1.1 General ..... | 17 | +| 4.1.2 Acceptable uncertainty of Test System ..... | 17 | +| 4.1.2.1 General..... | 17 | +| 4.1.2.2 Conducted characteristics measurements ..... | 18 | +| 4.1.3 Interpretation of measurement results ..... | 19 | +| 4.2 Conducted requirement reference points..... | 19 | +| 4.3 Repeater classes..... | 19 | +| 4.3.1 Repeater class for downlink ..... | 19 | +| 4.3.2 Repeater class for uplink ..... | 20 | +| 4.4 Regional requirements..... | 20 | +| 4.5 Repeater configurations..... | 20 | +| 4.5.1 General configurations ..... | 20 | +| 4.5.2 Transmission with multiple BS-side antenna connectors..... | 20 | +| 4.5.3 Transmission with multiple UE-side antenna connectors ..... | 21 | +| 4.5.4 Duplexers..... | 21 | +| 4.5.5 Power supply options ..... | 21 | +| 4.5.6 Ancillary RF amplifiers ..... | 21 | +| 4.5.7 Combining of repeaters ..... | 22 | +| 4.6 Manufacturer declarations..... | 22 | +| 4.7 Test configurations..... | 24 | +| 4.7.1 General ..... | 24 | +| 4.7.2 Test signal used to build Test Configurations ..... | 24 | +| 4.7.3 RTC1: Contiguous spectrum operation ..... | 24 | +| 4.7.3.1 RTC1 generation..... | 24 | +| 4.7.3.2 RTC1 power allocation..... | 25 | +| 4.7.5 RTC2: Non-contiguous spectrum operation..... | 25 | +| 4.7.5.1 RTC2 generation..... | 25 | +| 4.7.5.2 RTC2 power allocation..... | 25 | +| 4.7.6 RTC3: Multi-band test configuration for full carrier allocation..... | 25 | +| 4.7.6.1 RTC3 generation..... | 25 | +| 4.7.6.2 RTC3 power allocation..... | 26 | +| 4.7.7 RTC4: Multi-band test configuration with high PSD per carrier ..... | 26 | +| 4.7.7.1 RTC4 generation..... | 26 | +| 4.7.7.2 RTC4 power allocation..... | 26 | +| 4.8 Applicability of requirements..... | 26 | +| 4.8.1 General ..... | 26 | +| 4.8.2 Applicability of test configurations for single-band operation..... | 26 | +| 4.8.4 Applicability of test configurations for multi-band operation..... | 27 | +| 4.9 RF channels and test models ..... | 28 | +| 4.9.1 RF channels ..... | 28 | +| 4.9.2 Test models..... | 29 | +| 4.9.2.1 General..... | 29 | +| 4.9.2.2 FR1 test models for repeater type 1-C for DL ..... | 29 | +| 4.9.2.3 FR1 test models for repeater type 1-C for UL ..... | 29 | +| 4.9.2.3.1 General ..... | 29 | +| 4.9.2.3.2 FR1 test model 1.1 (RUL-FR1-TM1.1) ..... | 30 | + +| | | | +|-------------|-----------------------------------------------------------------------------------------------|----| +| 4.9.2.3.3 | FR1 test model 2 (RUL-FR1-TM2) ..... | 31 | +| 4.9.2.3.3a | FR1 test model 2a (RUL-FR1-TM2a)..... | 31 | +| 4.9.2.3.4 | FR1 test model 3.1 (RUL-FR1-TM3.1) ..... | 31 | +| 4.9.2.3.5 | FR1 test model 3.1a (RUL-FR1-TM3.1a)..... | 31 | +| 4.9.2.4 | Data content of Physical channels and Signals for RUL-FR1-TM ..... | 32 | +| 4.9.2.4.1 | General ..... | 32 | +| 4.9.2.4.2 | PUSCH..... | 32 | +| 4.10 | Requirements for contiguous and non-contiguous spectrum ..... | 32 | +| 4.11 | Requirements for repeater capable of multi-band operation..... | 33 | +| 4.12 | Format and interpretation of tests..... | 33 | +| 5 | Operating bands and channel arrangement ..... | 34 | +| 6 | Conducted characteristics ..... | 34 | +| 6.1 | General ..... | 34 | +| 6.2 | Repeater output power ..... | 34 | +| 6.2.1 | Definition and applicability ..... | 34 | +| 6.2.2 | Minimum requirement ..... | 35 | +| 6.2.3 | Test purpose..... | 35 | +| 6.2.4 | Method of test..... | 35 | +| 6.2.4.1 | Initial conditions ..... | 35 | +| 6.2.4.2 | Procedure ..... | 36 | +| 6.2.5 | Test requirement..... | 36 | +| 6.3 | Frequency stability ..... | 36 | +| 6.3.1 | Definition and applicability ..... | 36 | +| 6.3.2 | Minimum Requirement ..... | 36 | +| 6.3.3 | Test purpose..... | 37 | +| 6.3.4 | Method of test..... | 37 | +| 6.3.5 | Test Requirements ..... | 37 | +| 6.4 | Out of band gain..... | 37 | +| 6.4.1 | Definition and applicability ..... | 37 | +| 6.4.2 | Minimum Requirement ..... | 37 | +| 6.4.3 | Test purpose..... | 37 | +| 6.4.4 | Method of test..... | 37 | +| 6.4.4.1 | Initial conditions ..... | 37 | +| 6.4.4.2 | Procedure ..... | 37 | +| 6.4.5 | Test Requirements ..... | 37 | +| 6.5 | Unwanted emissions..... | 38 | +| 6.5.1 | General ..... | 38 | +| 6.5.2 | Adjacent Channel Leakage Power Ratio (ACLR)..... | 39 | +| 6.5.2.1 | Definition and applicability ..... | 39 | +| 6.5.2.2 | Minimum requirement ..... | 39 | +| 6.5.2.3 | Test purpose..... | 39 | +| 6.5.2.4 | Method of test..... | 39 | +| 6.5.2.4.1 | Initial conditions..... | 39 | +| 6.5.2.4.2 | Procedure..... | 39 | +| 6.5.2.5 | Test requirements..... | 40 | +| 6.5.3 | Operating band unwanted emissions ..... | 44 | +| 6.5.3.1 | Definition and applicability ..... | 44 | +| 6.5.3.2 | Minimum requirement ..... | 45 | +| 6.5.3.3 | Test purpose..... | 45 | +| 6.5.3.4 | Method of test ..... | 46 | +| 6.5.3.4.1 | Initial conditions..... | 46 | +| 6.5.3.4.2 | Procedure..... | 46 | +| 6.5.3.4 | Test requirements..... | 46 | +| 6.5.3.4.1 | Minimum requirements for Wide Area repeater type 1-C (Category A)..... | 46 | +| 6.5.3.4.2 | Minimum requirements for Wide Area repeater type 1-C (Category B)..... | 48 | +| 6.5.3.4.2.1 | Category B requirements (Option 1)..... | 48 | +| 6.5.3.4.2.2 | Category B requirements (Option 2)..... | 49 | +| 6.5.3.4.3 | Minimum requirements for Medium Range repeater type 1-C (Category A and B) for DL..... | 50 | +| 6.5.3.4.4 | Minimum requirements for Local Area repeater type 1-C (Category A and B)..... | 52 | +| 6.5.3.4.5 | Minimum requirements for additional requirements ..... | 53 | + +| | | | +|-----------|-------------------------------------------------------------------------|----| +| 6.5.4 | Transmitter spurious emissions ..... | 53 | +| 6.5.4.1 | Definition and applicability ..... | 53 | +| 6.5.4.2 | Minimum requirement ..... | 54 | +| 6.5.4.3 | Test purpose..... | 54 | +| 6.5.4.4 | Method of test..... | 54 | +| 6.5.4.4.1 | Initial conditions..... | 54 | +| 6.5.4.4.2 | Procedure..... | 54 | +| 6.5.4.5 | Test requirements..... | 55 | +| 6.5.4.5.1 | General transmitter spurious emissions requirements..... | 55 | +| 6.5.4.5.2 | Additional spurious emissions requirements..... | 56 | +| 6.5.4.5.3 | Co-location with base stations and repeater type 1-C Nodes ..... | 66 | +| 6.5.5 | Receiver spurious emissions..... | 71 | +| 6.5.5.1 | Definition and applicability ..... | 71 | +| 6.5.5.2 | Minimum requirement ..... | 71 | +| 6.5.5.3 | Test purpose..... | 71 | +| 6.5.5.4 | Method of test..... | 71 | +| 6.5.5.4.1 | Initial conditions..... | 71 | +| 6.5.5.4.2 | Procedure..... | 71 | +| 6.5.5.5 | Test requirements..... | 72 | +| 6.6 | Repeater Error Vector Magnitude..... | 72 | +| 6.6.1 | Downlink repeater error vector magnitude..... | 72 | +| 6.6.1.1 | General ..... | 72 | +| 6.6.1.2 | Minimum requirements..... | 73 | +| 6.6.1.3 | Test purpose..... | 73 | +| 6.6.1.4 | Method of test..... | 73 | +| 6.6.1.4.1 | Initial conditions..... | 73 | +| 6.6.1.4.2 | Procedure..... | 73 | +| 6.6.1.5 | Test requirement ..... | 74 | +| 6.6.2 | Uplink repeater error vector magnitude..... | 74 | +| 6.6.2.1 | General ..... | 74 | +| 6.6.2.2 | Minimum requirement ..... | 74 | +| 6.6.2.3 | Test purpose..... | 75 | +| 6.6.2.3 | Method of test ..... | 75 | +| 6.6.2.3.1 | Initial conditions..... | 75 | +| 6.6.2.3.2 | Procedure..... | 75 | +| 6.6.2.4 | Test requirement ..... | 76 | +| 6.7 | Input intermodulation ..... | 76 | +| 6.7.1 | Definition and applicability ..... | 76 | +| 6.7.1.1 | General ..... | 76 | +| 6.7.1.2 | Minimum requirements..... | 76 | +| 6.7.1.3 | Test purpose..... | 76 | +| 6.7.1.4 | Method of test..... | 76 | +| 6.7.1.4.1 | Initial conditions..... | 76 | +| 6.7.1.4.2 | Procedure..... | 76 | +| 6.7.1.5 | Test requirements..... | 77 | +| 6.7.1.5.1 | General requirement..... | 77 | +| 6.7.1.5.2 | Co-location with BS/Repeater in other systems..... | 77 | +| 6.7.1.5.3 | Co-existence with other systems..... | 78 | +| 6.8 | Output intermodulation ..... | 79 | +| 6.8.1 | Definition and applicability ..... | 79 | +| 6.8.1.1 | General ..... | 79 | +| 6.8.1.2 | Minimum requirements..... | 79 | +| 6.8.1.3 | Test purpose..... | 79 | +| 6.8.1.4 | Method of test..... | 79 | +| 6.8.1.4.1 | Initial conditions..... | 79 | +| 6.8.1.4.2 | Procedure..... | 79 | +| 6.8.1.5 | Test requirements..... | 80 | +| 6.8.1.5.1 | General requirements ..... | 80 | +| 6.8.1.5.2 | Additional requirements..... | 80 | +| 6.9 | Adjacent Channel Rejection Ratio (ACRR)..... | 81 | +| 6.9.1 | Definitions and applicability ..... | 81 | +| 6.9.2 | Co-existence with UTRA, E-UTRA and NR ..... | 81 | + +| | | | +|-------------------------------------------------------------------------------|-------------------------------------------------------------|-----------| +| 6.9.2.1 | Minimum requirements..... | 81 | +| 6.9.2.2 | Test purpose..... | 81 | +| 6.9.2.3 | Method of test..... | 81 | +| 6.9.2.3.1 | Initial conditions..... | 81 | +| 6.9.2.3.2 | Procedure..... | 81 | +| 6.9.2.3.3 | Test Requirements..... | 82 | +| 6.10 | Transmit ON/OFF power ..... | 83 | +| 6.10.1 | Transmitter OFF power ..... | 83 | +| 6.10.1.1 | Definition and applicability ..... | 83 | +| 6.10.1.2 | Minimum requirement ..... | 83 | +| 6.10.1.3 | Test purpose..... | 83 | +| 6.10.1.4 | Method of test ..... | 84 | +| 6.10.1.5 | Test requirements..... | 84 | +| 6.10.2 | Transmitter transient period ..... | 84 | +| 6.10.2.1 | Definition and applicability ..... | 84 | +| 6.10.2.2 | Minimum requirement ..... | 84 | +| 6.10.2.3 | Test purpose..... | 84 | +| 6.10.2.4 | Method of test ..... | 85 | +| 6.10.2.4.1 | Initial conditions..... | 85 | +| 6.10.2.4.2 | Procedure..... | 85 | +| Annex A (normative): Repeater stimulus signals..... | | 86 | +| A.1 | Repeater stimulus signal 1 ..... | 86 | +| A.2 | Repeater stimulus signal 2 ..... | 86 | +| A.3 | Repeater stimulus signal spectral purity requirements ..... | 86 | +| Annex B (normative): Environmental requirements for the repeater ..... | | 87 | +| B.1 | General..... | 87 | +| B.2 | Normal test environment..... | 87 | +| B.3 | Extreme test environment ..... | 88 | +| B.3.1 | Extreme temperature ..... | 88 | + +| | | | +|-----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|------------| +| B.4 | Vibration ..... | 88 | +| B.5 | Power supply..... | 89 | +| B.6 | Measurement of test environments ..... | 89 | +| Annex C (informative): Test tolerances and derivation of test requirements ..... | | 89 | +| C.1 | Measurement of conducted characteristics ..... | 90 | +| Annex D (informative): Measurement system set-up ..... | | 90 | +| D.1 | Repeater output power and transmit ON/OFF power ..... | 91 | +| D.2 | Out of band gain..... | 91 | +| D.3 | Unwanted emission: Operating band unwanted emission, transmitter spurious emission, and ACLR..... | 92 | +| D.4 | Modulation Accuracy: Repeater Error Vector Magnitude and Frequency Stability ..... | 92 | +| D.5 | Input intermodulation..... | 93 | +| D.6 | Output Intermodulation..... | 93 | +| D.7 | Adjacent Channel Rejection Ratio..... | 94 | +| D.8 | Rx spurious emission requirement..... | 94 | +| Annex E (normative): In-channel TX tests ..... | | 94 | +| E.1 | General..... | 95 | +| E.2 | Basic principles ..... | 95 | +| E.2.1 | Output signal of the repeater under test ..... | 95 | +| E.2.2 | Ideal signal ..... | 95 | +| E.2.3 | Measurement results..... | 96 | +| E.2.4 | Measurement points ..... | 96 | +| E.3 | Pre-FFT minimization process..... | 97 | +| E.4 | Timing of the FFT window ..... | 97 | +| E.5 | Resource element TX power..... | 98 | +| E.6 | Post-FFT equalisation ..... | 98 | +| E.7 | EVM..... | 100 | +| E.7.0 | General ..... | 100 | +| E.7.1 | Averaged EVM (FDD)..... | 100 | +| E.7.2 | Averaged EVM (TDD)..... | 101 | +| Annex F (informative): Change history ..... | | 102 | + +# 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 repeater *type 1-C*. These have been derived from, and are consistent with the conducted requirements for *repeater type 1-C* in NR repeater specification defined in TS 38.106 [2]. + +A *repeater type 1-C* only has conducted requirements so it requires compliance to this specification only. + +A *repeater type 2-O* has only radiated requirements so it requires compliance to TS 38.115-2 [3] only. + +# 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.106: "NR; Repeater Radio Transmission and Reception" +- [3] 3GPP TS 38.115-2: "NR; Repeater conformance testing, Part 2: Radiated conformance testing" +- [4] ITU-R Recommendation SM.329: "Unwanted emissions in the spurious domain" +- [5] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception" +- [6] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception" +- [7] 3GPP TS 38.141-1: "NR; Base Station (BS) conformance testing, Part 1: Conducted conformance testing" +- [8] 3GPP TS 38.211: "NR; Physical channels and modulation" +- [9] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone" +- [10] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification" +- [11] ITU-R Recommendation M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications – 2000" +- [12] ITU-T Recommendation O.150, "Equipment for the measurement of digital and analogue/digital parameters" +- [13] Federal Communications Commission: "Title 47 of the Code of Federal Regulations (CFR) " +- [14] 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)" +- [15] 3GPP TR 25.942: "RF system scenarios" +- [16] IEC 60 721-3-3: "Classification of environmental conditions - Part 3-3: Classification of groups of environmental parameters and their severities - Stationary use at weather protected locations" + +- [17] IEC 60 721-3-4: "Classification of environmental conditions - Part 3: Classification of groups of environmental parameters and their severities - Clause 4: Stationary use at non-weather protected locations" +- [18] IEC 60 721: "Classification of environmental conditions" +- [19] IEC 60 068-2-1 (2007): "Environmental testing - Part 2: Tests. Tests A: Cold" +- [20] IEC 60 068-2-2: (2007): "Environmental testing - Part 2: Tests. Tests B: Dry heat" +- [21] IEC 60 068-2-6: (2007): "Environmental testing - Part 2: Tests - Test Fc: Vibration (sinusoidal)" + +# 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]. + +**Antenna connector:** connector at the conducted interface of the *repeater type 1-C* + +**Fractional bandwidth:** *fractional bandwidth* FBW is defined as $FBW = 200 \cdot \frac{F_{FBWhigh} - F_{FBWlow}}{F_{FBWhigh} + F_{FBWlow}} \%$ + +**gap between passbands:** frequency gap between two consecutive passbands that belong to the same *operating band*, where the RF requirements in the gap are based on co-existence for un-coordinated operation + +**Inter-passband gap:** The frequency gap between two supported consecutive *passbands* that belong to different operating bands. + +**Maximum passband output power:** mean power level measured per *passband* at the *antenna connector*, during the *transmitter ON state* in a specified reference condition. + +**multi-band connector:** *Antenna Connector* for a *Multi-band repeater*. + +**Multi-band repeater:** *Repeater Type 1-C* whose *antenna connector* is associated with a transmitter and/or receiver that is characterized by the ability to process two or more *passband(s)* in common active RF components simultaneously, where at least one *passband* is configured at a different operating band than the other *passband(s)* and where this different operating band is not a sub-band or superseding-band of another supported operating band + +**Nominal channel bandwidth:** Bandwidth calculated as $\min(100\text{MHz}, BW_{\text{passband}})$ in FR1 or $\min(400\text{MHz}, BW_{\text{passband}})$ in FR2. If this bandwidth is not defined for BS channel bandwidth for the operating band, *nominal channel bandwidth* shall be defined as the widest BS channel bandwidth for the operating band which is narrower than $BW_{\text{passband}}$ . + +**Non-contiguous spectrum:** spectrum consisting of two or more *passbands* separated by *inter-passband gap(s)*. + +**Operating band:** frequency range in which NR operates (paired or unpaired), that is defined with a specific set of technical requirements + +**passband edge:** Frequency at the edge of the passband + +**Repeater type 1-C:** Repeater operating at FR1 with a requirement set consisting only of conducted requirements defined at individual *antenna connectors*. + +**Requirement set:** one of the NR requirements set as defined for *NR repeater* + +**single-band connector:** *Repeater type 1-C antenna 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 connector*. + +**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 transmission and reception by the repeater. + +**Superseding-band:** A *superseding-band* of an operating band includes the whole of the uplink and downlink frequency range of the operating band. + +**Transmitter OFF state:** Time period during which the repeater downlink or uplink is not allowed to transmit in the corresponding direction. + +**Transmitter ON state:** Time period during which the repeater is transmitting downlink or uplink signals in the corresponding direction. + +**Transmitter transient period:** Time period during which the repeater is changing from the OFF state to the ON state or vice versa. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| BW Config | Transmission bandwidth configuration, where $BW_{Config} = N_{RB} \times SCS \times 12$ | +| BW Nominal | Nominal channel bandwidth | +| BW Passband | Passband bandwidth | +| $\Delta f$ | Separation between the passband edge frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency | +| $\Delta f_{max}$ | $f\_offset_{max}$ minus half of the bandwidth of the measuring filter | +| $\Delta f_{OBUE}$ | Maximum offset of the operating band unwanted emissions mask from the operating band edge | +| $F_{DL,low}$ | The lowest frequency of the downlink operating band | +| $F_{DL,high}$ | The highest frequency of the downlink operating band | +| $F_{FBW,high}$ | Highest supported frequency within supported operating band, for which fractional bandwidth support was declared | +| $F_{FBW,low}$ | Lowest supported frequency within supported operating band, for which fractional bandwidth support was declared | +| $F_{filter}$ | Filter centre frequency | +| $F_{offset,high}$ | Frequency offset from $F_{C,high}$ to the upper passband edge | +| $F_{offset,low}$ | Frequency offset from $F_{C,low}$ to the lower passband edge | +| $f\_offset$ | Separation between the passband edge frequency and the centre of the measuring | +| $f\_offset_{max}$ | The offset to the frequency $\Delta f_{OBUE}$ outside the operating band | +| $F_{UL,low}$ | The lowest frequency of the uplink operating band | +| $F_{UL,high}$ | The highest frequency of the uplink operating band | +| $P_{EM,n50/n75,ind}$ | Declared emission level for Band n50/n75; ind = a, b | +| $P_{EM,n54,ind}$ | Declared emission level for Band n54 in the band 1518-1559 MHz; ind = a, b, c, d, e, $fP_{max,p,AC}$ | +| | Maximum passband output power measured per antenna connector | +| $P_{rated,in}$ | Rated pass band input power to the repeater for the test per antenna connector | +| $P_{rated,p,AC}$ | Rated passband output power per antenna connector | +| $P_{rated,t,AC}$ | Rated total output power declared per antenna connector $W_{gap}$ Inter passband Bandwidth gap size | + +## 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]. + +| | | +|------------|----------------------------------------| +| ACLR | Adjacent Channel Leakage Ratio | +| BW | Bandwidth | +| CACLR | Cumulative ACLR | +| CP-OFDM | Cyclic Prefix-OFDM | +| DFT-s-OFDM | Discrete Fourier Transform-spread-OFDM | +| DL | Downlink | +| EVM | Error Vector Magnitude | + +| | | +|-------|------------------------------------------------------------------------| +| FBW | Fractional Bandwidth | +| FR | Frequency Range | +| ITU-R | Radiocommunication Sector of the International Telecommunication Union | +| LA | Local Area | +| MR | Medium Range | +| NR | New Radio | +| OBUE | Operating Band Unwanted Emissions | +| OOB | Out-of-band | +| QAM | Quadrature Amplitude Modulation | +| RF | Radio Frequency | +| RX | Receiver | +| SCS | Sub-Carrier Spacing | +| TX | Transmitter | +| UL | Uplink | +| WA | Wide Area | + +# --- 4 General conducted 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 tests defined for FR1. The frequency ranges FR1 and FR2 are defined in clause 5.1 of TS 38.106 [2]. + +The minimum requirements are given in TS 38.106 [2]. Test Tolerances for the conducted test requirements explicitly stated in the present document are given in annex C of the present document. + +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. + +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 Conducted characteristics measurements + +**Table 4.1.2.2-1: Maximum Test System uncertainty for conducted characteristics tests** + +| Clause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6.2 Repeater output power | ±0.7 dB, $f \leq 3$ GHz
±1.0 dB, $3$ GHz $< f \leq 7.125$ GHz | | +| 6.3 Frequency stability | ±12 Hz
Measurement results of ± 500 Hz | | +| 6.4 Out of band gain | ±0,5 dB, $f \leq 3.0$ GHz
±0,8 dB, $3.0$ GHz $< f \leq 4.2$ GHz
Calibration of test set-up shall be made without DUT in order to achieve the accuracy | | +| 6.5.2 ACLR/ CACLR | BW $\leq 20$ MHz: ±0.8 dB
BW $> 20$ MHz: ±1.2 dB

Absolute power ±2.0 dB, $f \leq 3$ GHz
Absolute power ±2.5 dB, $3$ GHz $< f \leq 7.125$ GHz | | +| 6.5.3 Operating band unwanted emission | ±1,5 dB, $f \leq 3.0$ GHz
±1,8 dB, $3.0$ GHz $< f \leq 4.2$ GHz

The interference from the signal generator ACLR shall be minimum 10 dB below that of a NR repeater according to clause 6.5.2. | | +| 6.5.4 Spurious emissions | In NR and coexistence receive bands:
for results $> -60$ dBm ±2,0 dB
for results $< -60$ dBm ±3,0 dB
Outside above range:
emission power;
$9$ kHz $< f \leq 4$ GHz ±2,0 dB
$4$ GHz $< f \leq 19$ GHz ±4,0 dB.

The interference from the signal generator ACLR shall be minimum 10 dB below that of a NR repeater according to clause 6.5.2. | | +| 6.6 EVM | 1% signal analyser
2% stimulus signal | | +| 6.7 Input intermodulation | ±1,2 dB | Formula:
RSS CW1 level error, 2 x CW2 level error, and measurement error (using all errors = ±0,5 dB) | +| 6.8 Output intermodulation | For operating band unwanted emission:
±2,1 dB
The interference from the signal generator ACLR shall be minimum 10 dB below that of a NR repeater according to clause 6.5.2.

For spurious emission:
In NR and coexistence receive bands:
for results $> -60$ dBm ±2,0 dB
for results $< -60$ dBm ±3,0 dB
Outside above range:
emission power;
$9$ kHz $< f \leq 4$ GHz ±2,0 dB;
$4$ GHz $< f \leq 19$ GHz ±4,0 dB.

The interference signal must have a spurious emission level at least 10 dB below the spurious levels required in 6.5.4 and 6.5.5. | Formula:
RSS 2x Interference signal level error and operating band unwanted emission measurement level error.
(1 dB interference signal level error is assumed). | +| 6.9 ACRR | ±0,7 dB | | +| 6.10.1 Transmit ON/OFF power | ±2.0 dB , $f \leq 3$ GHz
±2.5 dB, $3$ GHz $< f \leq 7.125$ GHz | | + +| Clause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|---------------------------|---------------------------------|---------------------------------------| +| 6.10.1 Transmit OFF power | N/A | | + +### 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 [11]. + +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 requirement reference points + +For *repeater type 1-C*, the requirements are applied at the repeater *antenna connector* (BS-side connector or UE-side connector) for downlink or uplink for the configuration in normal operating conditions. + +![Diagram of Repeater type 1-C downlink and uplink interface. A blue rectangular box represents the repeater. Inside, there are two triangles representing antennas. The top antenna has an arrow pointing right, labeled 'Downlink'. The bottom antenna has an arrow pointing left, labeled 'Uplink'. On the left side of the box, there is a connector labeled 'BS-side connector'. On the right side, there is a connector labeled 'UE-side connector'. Arrows point from the connectors to the antennas.](e4c6fa93821e3546ee9fcae897ae2771_img.jpg) + +Diagram of Repeater type 1-C downlink and uplink interface. A blue rectangular box represents the repeater. Inside, there are two triangles representing antennas. The top antenna has an arrow pointing right, labeled 'Downlink'. The bottom antenna has an arrow pointing left, labeled 'Uplink'. On the left side of the box, there is a connector labeled 'BS-side connector'. On the right side, there is a connector labeled 'UE-side connector'. Arrows point from the connectors to the antennas. + +Figure 4.2-1: *Repeater type 1-C* downlink and uplink interface + +## 4.3 Repeater classes + +### 4.3.1 Repeater class for downlink + +The requirements in this specification apply to downlink Wide Area repeaters, downlink Medium Range repeaters and downlink Local Area repeaters unless otherwise stated. The associated deployment scenarios for each class are exactly the same for repeater with and without connectors. + +For *repeater type 1-C*, repeater downlink classes are defined as indicated below: + +- Wide Area repeaters are characterised by requirements derived from Macro Cell scenarios with a repeater to UE minimum distance along the ground equal to 35 m. + +- Medium Range repeaters are characterised by requirements derived from Micro Cell scenarios with a repeater to UE minimum distance along the ground equal to 5 m. +- Local Area repeaters are characterised by requirements derived from Pico Cell scenarios with a repeater to UE minimum distance along the ground equal to 2 m. + +### 4.3.2 Repeater class for uplink + +The requirements in this specification apply to uplink Wide Area repeaters and uplink Local Area repeaters unless otherwise stated. The associated deployment scenarios for each class are exactly the same for repeater with and without connectors. + +For *repeater type 1-C*, repeater uplink classes are defined as indicated below: + +- Wide Area repeaters are characterised by requirements derived from Macro Cell and/or Micro Cell scenarios. +- Local Area repeaters are characterised by requirements derived from Pico Cell and/or Micro Cell scenarios. + +## 4.4 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.4-1 lists all requirements in the present specification that may be applied differently in different regions. + +## 4.5 Repeater configurations + +### 4.5.1 General configurations + +For *repeater type 1-C*, the requirements are applied at the repeater *antenna connector* (BS-side connector or UE-side connector) for downlink or uplink for the configuration in normal operating conditions. + +![Diagram of Repeater type 1-C test ports showing internal components and external test ports.](69f52512bb7387a5dc9f952279513019_img.jpg) + +The diagram illustrates the internal architecture of a Repeater type 1-C. It features a rectangular box representing the repeater unit. Inside, there are two triangular symbols representing amplifiers. The top amplifier is connected to two internal test points, with an arrow labeled 'Downlink' pointing to the right. The bottom amplifier is also connected to two internal test points, with an arrow labeled 'Uplink' pointing to the left. Outside the box, on the left, is a 'BS-side test port' connected to the top amplifier's internal test points. On the right, a 'UE-side test port' is connected to the bottom amplifier's internal test points. + +Diagram of Repeater type 1-C test ports showing internal components and external test ports. + +**Figure 4.5.1-1: Repeater type 1-C test ports** + +### 4.5.2 Transmission with multiple BS-side antenna connectors + +Unless otherwise stated, for the tests in clause 6 of the present document, the requirement applies for each BS-side *antenna connector* in the case of transmission with multiple BS-side *antenna connectors*. + +Requirements are tested at the *antenna connector*, with the remaining *antenna connector(s)* being terminated. If the manufacturer has declared the antenna connectors to be equivalent (D.13), it is sufficient to measure the signal at any one of the BS-side *antenna connectors*. + +### 4.5.3 Transmission with multiple UE-side antenna connectors + +Unless otherwise stated, for the tests in clause 6 of the present document, the requirement applies for each UE-side *antenna connector* in the case of transmission with multiple UE-side *antenna connectors*. + +Requirements are tested at the *antenna connector*, with the remaining *antenna connector(s)* being terminated. If the manufacturer has declared the antenna connectors to be equivalent (D.13), it is sufficient to measure the signal at any one of the UE-side *antenna connectors*. + +### 4.5.4 Duplexers + +The requirements of the present document shall be met with a duplexer fitted, if a duplexer is supplied as part of the repeater. If the duplexer is supplied as an option by the manufacturer, sufficient tests should be repeated with and without the duplexer fitted to verify that the repeater meets the requirements of the present document in both cases. + +The following tests shall be performed with the duplexer fitted, and without it fitted if this is an option: + +- 1) clause 6.2, repeater output power, for the highest static power step only, if this is measured at the antenna connector; +- 2) clause 6.4, out of band gain; outside the repeater downlink or uplink band; +- 3) clause 6.5, unwanted emissions; outside the repeater downlink or uplink band; +- 4) clause 6.7, output intermodulation; for the testing of conformance, the carrier frequencies should be selected to minimize intermodulation products from the transmitters falling in receive channels. +- 5) clause 6.9, Adjacent Channel Rejection Ratio; outside the repeater downlink or uplink band. + +The remaining tests may be performed with or without the duplexer fitted. + +NOTE 1: When performing receiver tests with a duplexer fitted, it is important to ensure that the output from the transmitters does not affect the test apparatus. This can be achieved using a combination of attenuators, isolators and filters. + +NOTE 2: When duplexers are used, intermodulation products will be generated, not only in the duplexer but also in the antenna system. The intermodulation products generated in the antenna system are not controlled by 3GPP specifications, and may degrade during operation (e.g. due to moisture ingress). Therefore, to ensure continued satisfactory operation of a repeater, an operator will normally select NR-ARFCNs to minimize intermodulation products falling on receive channels. For testing of complete conformance, an operator may specify the NR-ARFCNs to be used. + +### 4.5.5 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. + +### 4.5.6 Ancillary RF amplifiers + +The *repeater type 1-C* requirements of the present document shall be met with the ancillary RF amplifier fitted. At tests, the ancillary amplifier is connected to the repeater 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 repeater. The applicable connecting network loss range is declared by the manufacturer (D.14). 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 repeater 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 the table below, where "x" denotes that the test is applicable: + +**Table 4.5.6-1: Tests applicable to ancillary RF amplifiers** + +| Clause | Ancillary RF amplifier needed | +|--------|-------------------------------| +| 6.2 | x | +| 6.4 | x | +| 6.5 | x | +| 6.7 | x | +| 6.8 | x | +| 6.9 | x | + +In repeater output power test (clause 6.2) highest applicable attenuation value is applied. + +### 4.5.7 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 4.5.7-1. + +![Figure 4.5.7-1: Example of repeater configuration. The diagram shows a signal flow from a 'Test port' on the left, through a 'Combiner / Splitter', then splitting into two parallel 'Repeater' units. The outputs of these repeaters are combined by another 'Combiner / Splitter', which then connects to a 'Test port' on the right. Vertical dashed lines labeled 'Antenna connector' are placed between the combiner/splitter and the repeaters, and between the repeaters and the second combiner/splitter.](124c6108c63173818afb8ed49521e22d_img.jpg) + +Figure 4.5.7-1: Example of repeater configuration. The diagram shows a signal flow from a 'Test port' on the left, through a 'Combiner / Splitter', then splitting into two parallel 'Repeater' units. The outputs of these repeaters are combined by another 'Combiner / Splitter', which then connects to a 'Test port' on the right. Vertical dashed lines labeled 'Antenna connector' are placed between the combiner/splitter and the repeaters, and between the repeaters and the second combiner/splitter. + +**Figure 4.5.7-1: Example of repeater configuration** + +## 4.6 Manufacturer declarations + +The following repeater declarations listed in table 4.6-1, when applicable to the repeater under test, are required to be provided by the manufacturer for the conducted requirements testing of the *repeater type 1-C*. Declarations can be made independently for UL and DL. + +Table 4.6-1: Manufacturer declarations for *repeater type 1-C* conducted test requirements + +| Declaration identifier | Declaration | Description | +|------------------------|---------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| D.1 | Repeater class | Repeater class of the repeater, declared as Wide Area repeater, Medium Range repeater, or Local Area repeater. | +| D.2 | Operating bands and passband frequency ranges | List of NR operating band(s) supported by single-band connector(s) and/or multi-band connector(s) of the repeater and passband frequency range(s) within the operating band(s) that the repeater can operate in. Declarations shall be made per antenna connector . | +| D.3 | Spurious emission category | Declare the repeater 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 [4]. | +| D.4 | Additional operating band unwanted emissions | The manufacturer shall declare whether the repeater under test is intended to operate in geographic areas where the additional operating band unwanted emission limits defined in clause 6.6.4.5.6 apply. (Note 2, Note 3). | +| D.5 | Co-existence with other systems | The manufacturer shall declare whether the repeater 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, PHS and/or NR operating in another band are deployed. | +| D.6 | Co-location with other base stations, repeaters and IABs | The manufacturer shall declare whether the repeater under test is intended to operate co-located with Base Stations, repeaters and IABs of one or more of the systems GSM850, GSM900, DCS1800, PCS1900, UTRA FDD, UTRA TDD, E-UTRA and/or NR operating in another band. | +| D.7 | Single band connector or multi-band connector | Declaration of the single band or multi-band capability of single band connector(s) or multi-band connector(s) , declared for every connector. | +| D.8 | Other band combination multi-band restrictions | Declare any other limitations under simultaneous operation in the declared band combinations (D.12) for each multi-band connector which have any impact on the test configuration generation. Declared for every multi-band connector . | +| D.9 | Rated output power per passband ( $P_{\text{rated,p,AC}}$ ) | Conducted rated output power per passband, per single band connector or multi-band connector . Declared per supported passband , per antenna connector . (Note 1) | +| D.10 | Rated total output power ( $P_{\text{rated,t,AC}}$ ) | Conducted total rated output power. Declared per supported operating band , per antenna connector . For multi-band connectors declared for each supported operating band in each supported band combination. (Note 1) | +| D.11 | Rated multi-band total output power, $P_{\text{rated,MB,TABC}}$ | Conducted multi-band rated total output power. Declared per supported operating band combinations, per multi-band connector . (Note 1) | +| D.12 | Operating band combination support | List of operating bands combinations supported by single-band connector(s) and/or multi-band connector(s) of the repeater. Declared per antenna connector . | +| D.13 | Equivalent connectors | List of antenna connectors which have been declared equivalent. Equivalent connectors imply that the antenna connector are expected to behave in the same way when presented with identical signals under the same operating conditions. All declarations made for the antenna connector are identical and the transmitter unit and/or receiver unit driving the antenna connector are of identical design. | +| D.14 | Connecting network loss range for repeater testing with ancillary RF amplifiers | Declaration of the range of connecting network losses (in dB) for repeater type 1-C testing with ancillary Tx RF amplifier only, or with Rx RF amplifier only, or with combined Tx/Rx RF amplifiers. (Note 4) | +| D.15 | Long delay repeater | Declared only if the repeater internal delay between the input and output for this repeater does not fit within the TDD transient time. The repeater is intended for situations in which it will not cause interference to other nodes. This is achieved by RF isolation or by reservation of longer guard periods, which degrades frame utilization. The length of repeaters internal delay is declared using this declaration. | +| D.16 | Input signal power level for maximum output power | Declaration of input signal power level required to reach maximum output power. Declared per passband. | +| D.17 | Repeater radiating direction | Declaration on whether the repeater is intended to radiate in DL, UL or both. Testing shall be performed only for the direction(s) in which the repeater radiates. | + +- NOTE 1: If a repeater is capable of 256QAM operation then up to two rated output power declarations may be made. One declaration is applicable when configured for 256QAM operation, and the other declaration is applicable when not configured for 256QAM operation. If a repeater is not capable of 256QAM operation, only one declaration can be made. +- NOTE 2: If repeater is declared to support Band n20 (D.2), the manufacturer shall declare if the repeater may operate in geographical areas allocated to broadcasting (DTT). Additionally, related declarations of the emission levels and maximum output power shall be declared. +- NOTE 3: If repeater BS is declared to support Band n24 (D.2), the manufacturer shall declare if the repeater may operate in geographical areas where FCC regulations apply. Additionally, related declarations of the emission levels and maximum output power shall be declared. +- NOTE 4: This manufacturer declaration is optional. + +## 4.7 Test configurations + +### 4.7.1 General + +Test configurations in this specification refer to the configuration of test signals from test equipment that are provided to the repeater input. + +The test configurations shall be constructed using the methods defined below, subject to the parameters declared by the manufacturer for the supported RF configurations as listed in clause 4.6. The test configurations to use for conformance testing are defined for each supported RF configuration in clauses 4.8.3 and 4.8.4. + +The applicable test models for generation of the carrier transmit test signal are defined in clause 4.9. + +NOTE: If required, carriers are shifted to align with the channel raster. + +### 4.7.2 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.7.2-1. + +**Table 4.7.2-1: Signal to be used to build NR repeater TCs** + +| Operating Band characteristics | | $F_{DL\_high} - F_{DL\_low}$ or $F_{UL\_high} - F_{UL\_low} < 100$ MHz (Note 2) | $F_{DL\_high} - F_{DL\_low}$ or $F_{UL\_high} - F_{UL\_low} \geq 100$ MHz (Note 2) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| TC signal characteristics | BW channel | 5 MHz (Note 1) | 20 MHz (Note 1) | +| | Subcarrier spacing | Smallest supported subcarrier spacing of the operating band | | +| NOTE 1: If this channel bandwidth is not supported for the operating band, the narrowest supported channel bandwidth shall be used.
NOTE 2: Either the DL operating band characteristics or the UL operating band characteristics should be considered (if different) depending on the tested transmission direction. | | | | + +### 4.7.3 RTC1: Contiguous spectrum operation + +The purpose of test configuration RTC1 is to test all repeater requirements that need an input signal in the *passband* when there is only one *passband* per *operating band*. + +#### 4.7.3.1 RTC1 generation + +RTC1 shall be constructed on a per band basis using the following method: + +- Declared maximum *passband* Bandwidth supported shall be used; +- Select the carrier to be tested according to 4.7.2 and place it adjacent to the lower *passband* edge. If the width of the *passband* is at least twice the bandwidth of the signal to be tested then place a second signal adjacent to the upper *passband* edge. Otherwise reposition the carrier to be tested according to the single carrier test frequencies described in section 4.9.1. + +The test configuration should be constructed sequentially on a per band basis using the same *antenna connector*. All configured component carriers are transmitted simultaneously in the tests where the repeater should be ON. + +#### 4.7.3.2 RTC1 power allocation + +Set the power spectral density of each carrier to the same level so that the sum of the carrier powers equals the expected input power to the repeater for the test (i.e., either $P_{\text{rated,in}}$ or $P_{\text{rated,in}} + 10\text{dB}$ ) according to the manufacturer's declaration in clause 4.6. + +### 4.7.5 RTC2: Non-contiguous spectrum operation + +The purpose of RTC2 is to test all repeater requirements that need an input signal in the *passband* when there is more than one *passband* per *operating band*. + +#### 4.7.5.1 RTC2 generation + +RTC2 is constructed on a per band basis using the following method: + +- The repeater *passband* bandwidths shall be the maximum *passband* Bandwidth supported for multiple passbands (D.11). The repeater RF Bandwidth consists of one sub-block gap and the two highest and lowest declared *passbands*. +- For each *passband*, select the carrier to be tested according to 4.7.2. If the the width of the *passband* is at least twice that of the carrier to be tested then place a carrier adjacent to the upper *passband* edge and another carrier (as described in 4.7.2) adjacent to the lower *passband* edge. Otherwise, tests shall be applied with one carrier adjacent to the lower sub-block edge and one carrier adjacent to the upper sub-block edge for each sub-block gap. +- The sub-block edges adjacent to the sub-block gap shall be determined using the specified $F_{\text{offset\_high}}$ and $F_{\text{offset\_low}}$ for the carriers adjacent to the sub-block gap. + +#### 4.7.5.2 RTC2 power allocation + +Set the power of each carrier to the same level so that the sum of the carrier powers equals the expected input power to the repeater for the test (i.e., either $P_{\text{rated,in}}$ or $P_{\text{rated,in}} + 10\text{dB}$ ) according to the manufacturer's declaration in clause 4.6. + +### 4.7.6 RTC3: Multi-band test configuration for full carrier allocation + +The purpose of RTC3 is to test multi-band operation aspects. + +#### 4.7.6.1 RTC3 generation + +RTC3 is based on re-using the previously specified test configurations applicable per band involved in multi-band operation. It is constructed using the following method: + +- The repeater RF Bandwidth of each supported operating band shall be the declared maximum repeater RF Bandwidth in multi-band operation (D.12). +- The number of carriers of each supported *operating band* shall be sufficient to fill all of the *passbands* with one or two carriers (depending on the passband bandwidth). Carriers shall be selected according to 4.7.2 and shall first be placed at the outermost edges of the declared repeater Radio Bandwidth. Additional carriers shall next be placed at the repeater RF Bandwidths edges, if possible. +- Each concerned band shall be considered as an independent band and the carrier placement in each band shall be according to RTC1, 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. +- If the bandwidth of any *passband* is insufficient to accommodate two carriers then tests shall be repeated with the test carriers positioned such that there is a carrier adjacent to the lower edge of a sub-block gap or inter-band gap and a carrier adjacent to the upper edge of the sub-block gap or inter-band gap, for each sub-block gap or inter-block gap. + +#### 4.7.6.2 RTC3 power allocation + +Unless otherwise stated, set the power of each carrier in all supported *operating bands* to the same level so that the sum of the carrier powers equals the expected input power to the repeater for the test (i.e., either $P_{\text{rated,in}}$ or $P_{\text{rated,in}} + 10\text{dB}$ ) according to the manufacturer's declaration in clause 4.6. + +### 4.7.7 RTC4: Multi-band test configuration with high PSD per carrier + +The purpose of RTC4 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. + +#### 4.7.7.1 RTC4 generation + +RTC4 is based on re-using the existing test configuration applicable per band involved in multi-band operation. It is constructed using the following method: + +- The repeater RF Bandwidth of each supported *operating band* shall be the declared maximum repeater RF Bandwidth in multi-band operation (D.12). +- The allocated repeater RF Bandwidth of the outermost bands shall be located at the outermost edges of the declared Maximum Radio Bandwidth. +- The maximum number of carriers is limited to two per band. Carriers shall be selected according to 4.7.2 and shall first be placed at the outermost edges of the declared Maximum Radio Bandwidth for outermost bands and at the Repeater RF Bandwidths edges for middle band(s) if any. Additional carriers shall next be placed at the Repeater RF Bandwidths edges, if possible. +- Each concerned band shall be considered as an independent band and the carrier placement in each band shall be according to RTC3, where the declared parameters for multi-band operation shall apply. Narrowest supported NR channel bandwidth and smallest subcarrier spacing shall be used in the test configuration. +- 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. + +#### 4.7.7.2 RTC4 power allocation + +Unless otherwise stated, set the power of each carrier in all supported operating bands to the same level so that the sum of the carrier powers equals the expected input power to the repeater for the test (i.e., either $P_{\text{rated,in}}$ or $P_{\text{rated,in}} + 10\text{dB}$ ) according to the manufacturer's declaration in clause 4.6. + +## 4.8 Applicability of requirements + +### 4.8.1 General + +### 4.8.2 Applicability of test configurations for single-band operation + +The applicable test configurations are specified in the tables below for each the supported RF configuration, which shall be declared according to clause 4.6. The generation and power allocation for each test configuration is defined in clause 4.7. This clause contains the test configurations for a repeater capable of single carrier, and/or multi-carrier operation in both contiguous and non-contiguous spectrum in single band. + +For a repeater declared to support a single *passband* within a single band (D.2), the test configurations in the second column of table 4.8.3-1 shall be used for testing. + +For a repeater declared to support more than one *passband* within a single band (D.2) and where the parameters in the manufacturer's declaration according to clause 4.6 are identical for all passbands, the test configurations in the third column of table 4.8.3-1 shall be used for testing. + +For a repeater declared to support more than one *passband* within a single band (D.2) and where the parameters in the manufacturer's declaration according to clause 4.6 are not identical for all passbands, the test configurations in the fourth column of table 4.8.3-1 shall be used for testing. + +**Table 4.8.3-1: Test configurations for a repeater capable of single or multiple *passbands* in a single band** + +| Test case | Single passband repeater | Multiple passband capable repeater with identical parameters per passband | Multiple passband capable repeater with different parameters per passband | +|----------------------------------------------------------|------------------------------------|---------------------------------------------------------------------------|---------------------------------------------------------------------------| +| Repeater output power | RTC1 | RTC1 | RTC1, RTC2 | +| Frequency stability | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| Out of band gain | N/A | N/A | N/A | +| Transmit ON/OFF power (only applied for NR TDD repeater) | RTC1 | RTC1 | RTC1, RTC2 | +| Error Vector Magnitude | RTC1 | RTC1 | RTC1, RTC2 | +| Adjacent Channel Leakage power Ratio (ACLR) | RTC1 | RTC1, RTC2 | RTC1, RTC2 | +| Cumulative ACLR requirement in non-contiguous spectrum | - | RTC2 | RTC2 | +| Operating band unwanted emissions | RTC1 | RTC1, RTC2 | RTC1, RTC2 | +| Transmitter spurious emissions | RTC1 | RTC1, RTC2 | RTC1, RTC2 | +| Output intermodulation | RTC1 | RTC1, RTC2 | RTC1, RTC2 | +| Input intermodulation | N/A | N/A | N/A | +| Adjacent Channel Rejection Ratio (ACRR) | RTC1 | RTC2 | RTC1, RTC2 | +| Receiver spurious emissions | RTC1 | RTC1, RTC2 | RTC1, RTC2 | + +### 4.8.4 Applicability of test configurations for multi-band operation + +For a repeater declared to be capable of multi-band operation, the test configuration in table 4.8.4-1 and/or table 4.8.3-1 shall be used for testing. In the case where multiple bands are mapped on common *multi-band connector*, the test configuration in the second column of table 4.8.4-1 shall be used. In the case where multiple bands are mapped on common *single-band connector*, the test configuration in table 4.8.3-1 shall be used. In the case where multiple bands are mapped on separate *single-band connector* or *multi-band connector*, the test configuration in the third column of table 4.8.4-1 shall be used. + +**Table 4.8.4-1: Test configuration for a BS capable of multi-band operation** + +| BS test case | Test configuration | | +|--------------------------------------------------------|------------------------------------|--------------------------------------| +| | Common connector | Separate connectors | +| Repeater output power | RTC1/2 (Note 1), RTC3 | RTC1/2 (Note 1), RTC3 | +| Frequency stability | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| Out of band gain | N/A | N/A | +| Transmit ON/OFF power (only applied for NR TDD BS) | RTC3 | RTC3 | +| Frequency error | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| Error Vector Magnitude (Note 8) | RTC1/2 (Note 1), RTC3 | RTC1/2 (Note 1), RTC3 | +| Adjacent Channel Leakage power Ratio (ACLR) | RTC1/2 (Note 1), RTC4 (Note 2) | RTC1/2 (Note 1, 3), RTC4 (Note 2, 3) | +| Cumulative ACLR requirement in non-contiguous spectrum | RTC2 (Note 1), RTC4 (Note 2) | RTC2 (Note 1, 3) | +| Operating band unwanted emissions | RTC1/2 (Note 1), RTC4 | RTC1/2 (Note 1, 3), RTC4 (Note 3) | +| Transmitter spurious emissions | RTC1/2 (Note 1), RTC4 | RTC1/2 (Note 1, 3), RTC4 (Note 3) | +| Output intermodulation | RTC1/2 (Note 1) | RTC1/2 (Note 1, 3) | +| Input Intermodulation | N/A | N/A | +| Adjacent Channel Rejection Ratio | RTC1/2 (Note 1), RTC4 (Note 2) | RTC1/2 (Note 1, 3), RTC4 (Note 2, 3) | +| Receiver spurious emissions | RTC1/2 (Note 1), RTC4 | RTC1/2 (Note 1, 3), RTC4 (Note 3) | + +Note 1: RTC1 and/or RTC2 shall be applied in each supported operating band. + +Note 2: RTC4 may be applied for Inter RF Bandwidth gap only. + +Note 3: For single-band operation test, other antenna connector(s) is (are) terminated. + +## 4.9 RF channels and test models + +### 4.9.1 RF channels + +For the single passband testing many tests in this TS are performed with appropriate frequencies in the bottom, middle and top channels of the supported frequency range of the repeater. These are denoted as RF channels B (bottom), M (middle) and T (top). + +Unless otherwise stated, the test shall be performed with a single passband at each of the RF channels B, M and T. + +Many tests in this TS are performed with the maximum repeater 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 repeater RF Bandwidth located at the bottom of the supported frequency range in the operating band. +- $M_{\text{RFBW}}$ : maximum repeater RF Bandwidth located in the middle of the supported frequency range in the operating band. +- $T_{\text{RFBW}}$ : maximum repeater RF Bandwidth located at the top of the supported frequency range in the operating band. + +For repeater capable of multi-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 *repeater 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. + +- $B'_{\text{RFBW\_T\_RFBW}}$ : the *repeater 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. + +NOTE: $B_{\text{RFBW\_T\_RFBW}} = B'_{\text{RFBW\_T\_RFBW}} = B_{\text{RFBW\_T\_RFBW}}$ when the declared Maximum Radio Bandwidth spans all operating bands. $B_{\text{RFBW\_T\_RFBW}}$ means the *repeater 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 passband, $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ for single band operation, 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.9.2 Test models + +#### 4.9.2.1 General + +The following clauses will describe the FR1 test models needed for *repeater type 1-C*. + +#### 4.9.2.2 FR1 test models for repeater type 1-C for DL + +FR1 test model in clause 4.9.2.2 in TS 38.141-1[7] applies to *repeater type 1-C* as below: + +- NR-FR1-TM1.1 applies to RDL-FR1-TM1.1 +- NR-FR1-TM1.2 applies to RDL-FR1-TM1.2 +- NR-FR1-TM2 applies to RDL-FR1-TM2 +- NR-FR1-TM2a applies to RDL-FR1-TM2a +- NR-FR1-TM3.1 applies to RDL-FR1-TM3.1 +- NR-FR1-TM3.1a applies to RDL-FR1-TM3.1a +- NR-FR1-TM3.2 applies to RDL-FR1-TM3.2 +- NR-FR1-TM3.3 applies to RDL-FR1-TM3.3 + +Testing models applying to NB-IoT operation in clause 4.9.2.2 in TS 38.141-1[7] are not applicable to repeaters. + +#### 4.9.2.3 FR1 test models for repeater type 1-C for UL + +##### 4.9.2.3.1 General + +The set-up of physical channels for transmitter tests shall be according to one of the FR1 test models (R-TMs) below. A reference to the applicable test model is made within each test. + +The following general parameters are used by all repeater test models: + +- Duration is 2 radio frames for TDD (20 ms) +- The slots are numbered 0 to $10 \times 2^\mu - 1$ where $\mu$ is the numerology corresponding to the subcarrier spacing +- $N_{\text{RB}}$ is the maximum transmission bandwidth configuration seen in clause 5.3.2 in TS 38.106 [2]. +- Normal CP +- Virtual resource blocks of localized type + +Repeater test models are derived based on the uplink/downlink configuration as shown in the table 4.9.2.2.1-1 using information element *TDD-UL-DL-ConfigCommon* as defined in TS 38.331 [10]. + +**Table 4.9.2.3.1-1: Configurations of TDD for *repeater type 1-C* test models** + +| Field name | Value | | | +|----------------------------------------------------|-------|----|----| +| referenceSubcarrierSpacing (kHz) | 15 | 30 | 60 | +| Periodicity (ms) for dl-UL-TransmissionPeriodicity | 5 | 5 | 5 | +| nrofDownlinkSlots | 3 | 7 | 14 | +| nrofDownlinkSymbols | 10 | 6 | 12 | +| nrofUplinkSlots | 1 | 2 | 4 | +| nrofUplinkSymbols | 2 | 4 | 8 | + +Common physical channel parameters for all repeater FR1 test models are specified in table 4.9.2.3.1-2 and table 4.9.2.3.1-3 for PUSCH. Specific physical channel parameters for repeater FR1 test models are described in clauses 4.9.2.3.2 to 4.9.2.3.5. + +**Table 4.9.2.3.1-2: Common physical channel parameters for PUSCH for *repeater type 1-C* test models** + +| Parameter | Value | +|---------------------------------------------------------------|----------------------| +| Mapping type | PUSCH mapping type A | +| dmrs-TypeA-Position for the first DM-RS symbol | pos2 | +| dmrs-AdditionalPosition for additional DM-RS symbol(s) | Pos1 | +| dmrs-Type for comb pattern | Configuration type 1 | +| maxLength | 1 | +| Ratio of PUSCH EPRE to DM-RS EPRE | 0 dB | + +**Table 4.9.2.3.1-3: Common physical channel parameters for PUSCH by RNTI for *repeater type 1-C* test models** + +| Parameter | Value | +|-----------------------------|-------| +| PUSCH $n_{\text{RNTI}} = 0$ | | + +##### 4.9.2.3.2 FR1 test model 1.1 (RUL-FR1-TM1.1) + +This model shall be used for tests on: + +- Repeater output power +- Out of band gain +- Unwanted emissions + - ACLR + - Operating band unwanted emissions + - Transmitter spurious emissions + - Receiver spurious emissions +- Transmitter intermodulation +- +- Input intermodulation +- Output intermodulation +- ACRR +- Transmitter ON/OFF power + +Common physical channel parameters are defined in clause 4.9.2.3.1. Specific physical channel parameters for RUL-FR1-TM1.1 are defined in table 4.9.2.3.2-1. + +**Table 4.9.2.2.2-1: Specific physical channel parameters of RUL-FR1-TM1.1** + +| Parameter | Value | +|------------------|----------| +| # of PRBs PUSCH | $N_{RB}$ | +| Modulation PUSCH | QPSK | + +##### **4.9.2.3.3 FR1 test model 2 (RUL-FR1-TM2)** + +This model shall be used for tests on: + +- Transmitted signal quality +- Uplink repeater EVM of single 64QAM PRB allocation (at lower PSD TX power limit at min power)- Frequency stability (at min power) + +Common physical channel parameters are defined in clause 4.9.2.3.1. Specific physical channel parameters for RUL-FR1-TM2 are defined in table 4.9.2.3.3-1. + +**Table 4.9.2.3.3-1: Specific physical channel parameters of RUL-FR1-TM2** + +| Parameter | Value | | | +|-----------------------------------------|--------------|---------------------------------------------|----------------------------------------------------------------------------| +| # of 64QAM PUSCH PRBs | 1 | | | +| Level of boosting (dB) | 0 | | | +| Location of 64QAM PRB | | | | +| | Slot | RB | n | +| | $3n$ | 0 | $n = 0, \dots, \left\lceil \frac{10 \times 2^\mu}{3} \right\rceil - 1$ | +| | $3n+1$ | $\left\lceil \frac{N_{RB}}{2} \right\rceil$ | $n = 0, \dots, \left\lceil \frac{10 \times 2^\mu - 1}{3} \right\rceil - 1$ | +| | $3n+2$ | $N_{RB} - 1$ | $n = 0, \dots, \left\lceil \frac{10 \times 2^\mu - 2}{3} \right\rceil - 1$ | +| # of PUSCH PRBs which are not allocated | $N_{RB} - 1$ | | | + +##### **4.9.2.3.3a FR1 test model 2a (RUL-FR1-TM2a)** + +This model shall be used for tests on: + +- Uplink repeater EVM of single 256QAM PRB allocation (at min power) +- Frequency stability (at min power) + +Common physical channel parameters are defined in clause 4.9.2.3.3. Physical channel parameters and numbers of the allocated PRB are defined in table 4.9.2.3.3-1 with all 64QAM PUSCH PRBs replaced by 256QAM PUSCH PRBs. + +##### **4.9.2.3.4 FR1 test model 3.1 (RUL-FR1-TM3.1)** + +This model shall be used for tests on: + +- Transmitted signal quality +- Frequency stability (at max power) +- Uplink repeater EVM for modulation (at max power) + +Common physical channel parameters are defined in clause 4.9.2.3.1. Physical channel parameters are defined in table 4.9.2.3.2-1 with all QPSK PUSCH PRBs replaced with selected modulation order PUSCH PRBs according to the corresponding test procedure. + +##### **4.9.2.3.5 FR1 test model 3.1a (RUL-FR1-TM3.1a)** + +This model shall be used for tests on: + +- Transmitted signal quality + - Frequency stability (at max power) + - Uplink repeater EVM for 256QAM modulation (at max power) + +Common physical channel parameters are defined in clause 4.9.2.3.1. Physical channel parameters are defined in table 4.9.2.3.2-1 with all QPSK PUSCH PRBs replaced by 256QAM PUSCH PRBs. + +#### 4.9.2.4 Data content of Physical channels and Signals for RUL-FR1-TM + +##### 4.9.2.4.1 General + +Randomisation of the data content is obtained by utilizing a PN sequence generator and the length-31 Gold sequence scrambling of TS 38.211 [8], clause 5.2.1 which is invoked by all physical channels prior to modulation and mapping to the RE grid. + +Initialization of the scrambler and RE-mappers as defined in TS 38.211 [8] use the following additional parameters: + +- $N_{\text{ID}}^{\text{cell}}$ , Physical layer cell identity = 1 is used as the default physical layer cell identity +- $q = 0$ (single code word) +- Rank 1, single layer + +##### 4.9.2.4.2 PUSCH + +- Generate the required amount of bits from the output of the PN23 sequence generator [12]. The PN sequence generator is initialized with a starting seed of "all ones" in the first allocated slot of each frame. The PN sequence is continuous over the slot boundaries. +- Perform user specific scrambling according to TS 38.211 [8], clause 6.3.1.1. +- Perform modulation of the scrambled bits with the modulation scheme defined for each user according to TS 38.211 [8], clause 6.3.1.2 +- $n_{\text{ID}} = N_{\text{ID}}^{\text{cell}}$ +- Perform mapping of the complex-valued symbols to layer according to TS 38.211 [8], clause 6.3.1.3. +- Perform PUSCH mapping according to TS 38.211 [8] using parameters listed in table 4.9.2.3-2. +- DM-RS sequence generation according to TS 38.211 [8], clause 6.4.1.1.1 where $l$ is the OFDM symbol number within the slot with the symbols indicated by table 4.9.2.2-3. +- $N_{\text{ID}}^{n_{\text{SCID}}} = N_{\text{ID}}^{\text{cell}}$ +- $n_{\text{SCID}} = 0$ +- DM-RS mapping according to TS 38.211 [8], clause 6.4.1.1.3 using parameters listed in table 4.9.2.2-3. + +## 4.10 Requirements for contiguous and non-contiguous spectrum + +A spectrum allocation where a repeater operates can either be contiguous or non-contiguous. Unless otherwise stated, the requirements in the present specification apply for repeater configured for both contiguous spectrum operation and non-contiguous spectrum operation. + +For repeater operation in non-contiguous spectrum, some requirements apply both at the repeater *passband* edges and inside the sub-block gaps. For each such requirement, it is stated how the limits apply relative to the repeater *passband* edges and the sub-block edges respectively. + +## 4.11 Requirements for repeater capable of multi-band operation + +For *multi-band connector* the conducted test requirements in clause 6 and 7 apply separately to each supported *operating band* unless otherwise stated. For some conducted test requirements, it is explicitly stated that specific additions or exclusions to the requirement apply at *multi-band connector(s)* as detailed in the requirement clause. For repeater capable of multi-band operation, various structures in terms of combinations of different transceivers in downlink and transceivers in uplink implementations (multi-band or single band) with mapping of transceivers to one or more *antenna connectors* for *repeater type 1-C* in different ways are possible. For *multi-band connector(s)* the exclusions or provisions for multi-band apply. For *single-band connector(s)*, the following applies: + +- Single-band transmitter spurious emissions, *operating band* unwanted emissions, ACLR, output intermodulation, ACRR and receiver spurious emissions requirements apply to this *connector* that is mapped to single-band. +- If the repeater is configured for single-band operation, *single-band requirements* shall apply to this connector configured for single-band operation and no exclusions or provisions for multi-band capable repeater are applicable. *Single-band requirements* are tested separately at the connector configured for single-band operation, with all other connectors terminated. + +For *multi-band connectors* supporting the bands for TDD, the RF requirements in the present specification assume no simultaneous uplink and downlink occur between the bands. + +NOTE 1: The conducted test requirements for multi-band connectors supporting bands for both FDD and TDD are not covered by the present release of this specification. + +## 4.12 Format and interpretation of tests + +Each test 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 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. + +#### X.4.2y.2 Procedure + +This clause describes the steps necessary to perform the test and provides further details of the test definition like 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. + +# --- 5 Operating bands and channel arrangement + +For the NR operation in NR operating bands specification, their channel bandwidth configurations, channel spacing and raster, as well as synchronization raster specification, refer to TS 38.106 [2], clause 5 and its relevant clauses. + +For the conducted testing purposes in this specification, only FR1 operating bands are considered. + +# --- 6 Conducted characteristics + +## 6.1 General + +Unless otherwise stated, the conducted transmitter characteristics are specified at the *antenna connector* for *repeater type 1-C* configuration in normal operating conditions. + +Requirements apply in both DL and UL. + +For the DL the *antenna connector* on the BS side is the input and the *antenna connector* on the UE side is the output. + +For the UL the *antenna connector* on the UE side is the input and the *antenna connector* on the BS side is the output. + +General test conditions for conducted tests of the *repeater type 1-C* are given in clause 4, including interpretation of measurement results and configurations for testing. Repeater configurations for the tests are defined in clause 4.5. + +If a number of *single-band connectors*, or *multi-band connectors* have been declared equivalent (D.13), only a representative one is necessary to be tested to demonstrate conformance. + +## 6.2 Repeater output power + +### 6.2.1 Definition and applicability + +The repeater conducted output power requirements are specified at *single-band connector*, or at *multi-band connector*. + +The *rated passband output power* $P_{\text{rated,p,AC}}$ of the *repeater type 1-C* shall be as specified in table 6.2.1-1 and table 6.2.1-2. + +**Table 6.2.1-1: Repeater type 1-C DL transmission classes rated output power limits for repeater classes** + +| Repeater class | $P_{\text{rated,p,AC}}$ | +|-------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| Wide Area repeater | Note 1 | +| Medium Range repeater | $\leq 38 \text{ dBm} + X$ , Note 2 | +| Local Area repeater | $\leq 24 \text{ dBm} + X$ , Note 2 | +| NOTE 1: There is no upper limit for the $P_{\text{rated,p,AC}}$ rated passband output power of the Wide Area repeater. | | +| NOTE 2: $X = 10 \cdot \log(\text{ceil}(\text{passband bandwidth}/20\text{MHz}))$ | | + +**Table 6.2.1-2: Repeater type 1-C UL transmission classes rated output power limits for repeater classes** + +| Repeater class | $P_{\text{rated,p,AC}}$ | +|-------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| Wide Area repeater | Note 1 | +| Local Area repeater | $\leq 24 \text{ dBm} + X$ , Note 2 | +| NOTE 1: There is no upper limit for the $P_{\text{rated,p,AC}}$ rated passband output power of the Wide Area repeater. | | +| NOTE 2: $X = 10 \cdot \log(\text{ceil}(\text{passband bandwidth}/20\text{MHz}))$ | | + +The output power limit for the respective repeater classes in tables 6.2.1-1 and 6.2.1-2 shall be compared to the rated output power and the declared repeater class. It is not subject to testing. + +### 6.2.2 Minimum requirement + +The minimum requirement applies per *single-band connector*, or per *multi-band connector* supporting transmission in the *passband*. + +The minimum requirement for *repeater type 1-C* is defined for normal and extreme conditions in TS 38.106 [2], clause 6.2.2. + +### 6.2.3 Test purpose + +The test purpose is to verify that the repeater output power accuracy of the *rated passband output power* across the frequency range and under normal and extreme conditions is within the limit specified by the minimum requirement in 6.2.2. + +### 6.2.4 Method of test + +#### 6.2.4.1 Initial conditions + +Test environment: + +- Normal, see annex B.2, +- Extreme, see annexes B.3 and B.5. + +A measurement system set-up is shown in annex x. + +RF channels to be tested for single carrier: B, M and T; see clause 4.9.1. + +RF channels positions to be tested for multi-carrier and/or CA: + +- $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ for *single-band connector(s)*, see clause 4.9.1. +- $B_{\text{RFBW\_T}}_{\text{RFBW}}$ and $B'_{\text{RFBW\_T}}_{\text{RFBW}}$ for *multi-band connector(s)*, see clause 4.9.1. + +Under extreme test environment, it is sufficient to test on one NR-ARFCN or one RF bandwidth position, and with one applicable test configuration defined in clauses 4.7 and 4.8. 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. + +Power levels to be tested: + +- The lowest input power ( $P_{\text{in,p,AC}}$ ) that produces the *rated passband output power* ( $P_{\text{rated,p,AC}}$ ). +- The lowest input power ( $P_{\text{in,p,AC}}$ ) that produces the *rated passband output power* ( $P_{\text{rated,p,AC}}$ ), plus 10 dB. + +#### 6.2.4.2 Procedure + +- 1) Connect the power measuring equipment to the output *single-band connector(s)* or to *multi-band connector(s)* and the signal generator equipment to the input *single-band connector(s)* or to *multi-band connector(s)* under test as shown in annex D.1.1. All connectors not under test shall be terminated. +- 2) For single carrier set the signal generator to transmit according to the applicable test configuration in clause 4.8 using the corresponding test models or set of physical channels in clause 4.9.2 at power levels to be tested, as in clause 6.2.4.1. + +For a connector under test declared to be capable of multi-carrier and/or CA operation set the connector under test to transmit on all carriers configured using the applicable test configuration and corresponding power setting specified in clauses 4.7 and 4.8 using the corresponding test models or set of physical channels in clause 4.9.2. + +- 3) Measure the *maximum passband output power measured per antenna connector* ( $P_{\text{max,p,AC}}$ ) for each carrier at each connector under test. + +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.2.5 Test requirement + +For each *single-band connector* or *multi-band connector* under test, the power measured in clause 6.2.4.2 in step 3 ( $P_{\text{max,p,AC}}$ ) shall remain within the values provided in table 6.2.5-1 for normal and extreme test environments, relative to the manufacturer's declared $P_{\text{rated,p,AC}}$ for *repeater type 1-C* (D.9): + +**Table 6.2.5-1: Test requirements for conducted repeater output power accuracy** + +| Normal test environment | Extreme test environment | +|------------------------------------------------------------------|------------------------------------------------------------------| +| $f \leq 3.0 \text{ GHz}: \pm 2.7 \text{ dB}$ | $f \leq 3.0 \text{ GHz}: \pm 3.2 \text{ dB}$ | +| $3.0 \text{ GHz} < f \leq 7.125 \text{ GHz}: \pm 3.0 \text{ dB}$ | $3.0 \text{ GHz} < f \leq 7.125 \text{ GHz}: \pm 3.5 \text{ dB}$ | + +## 6.3 Frequency stability + +### 6.3.1 Definition and applicability + +Frequency stability is the ability to maintain the same frequency on the output signal with respect to the input signal. + +### 6.3.2 Minimum Requirement + +The minimum requirement is in TS 38.106 [2], clause 6.3.2. + +### 6.3.3 Test purpose + +The test purpose is to verify that frequency stability is within the limit specified by the minimum requirement. + +### 6.3.4 Method of test + +Requirement is tested together with modulation quality test, as described in clause 6.6. + +### 6.3.5 Test Requirements + +The frequency deviation of the output signal with respect to the input signal shall be accurate to within $\pm(0.01 \text{ ppm} + 12 \text{ Hz})$ observed over 1 ms. + +## 6.4 Out of band gain + +### 6.4.1 Definition and applicability + +Out of band gain refers to the gain of the repeater outside the *passband*. + +### 6.4.2 Minimum Requirement + +The minimum requirement is in TS 38.106 [2], clause 6.4.2. + +### 6.4.3 Test purpose + +The test purpose is to verify that out of band gain is within the limit specified by the minimum requirement. + +### 6.4.4 Method of test + +#### 6.4.4.1 Initial conditions + +Test environment: + +- Normal, see annex B.2, + +#### 6.4.4.2 Procedure + +- 1) Connect the CW generator to the input and power measuring equipment to the output *single-band connector(s)* or to *multi-band connector(s)* under test as shown in annex D.1.1. All connectors not under test shall be terminated. +- 2) Set the CW generator to generate a test signal with an input power equivalent to $P_{\text{in,p,AC}}$ . +- 3) Measure the for each carrier at each connector under test. The out of band gain at the frequency under test is given by the difference in dB between the measured output power and the power of the input signal. +- 4) Repeat steps 2-3, shifting the offset frequency of the CW from the edge of the *passband* from 200kHz to 10MHz in steps of 200kHz for each *passband* and, for the case of multi-band connectors each operating band. + +### 6.4.5 Test Requirements + +The gain outside the *passband* shall not exceed the maximum level specified in table 6.4.5-1 or table 6.4.5-2 or table 6.4.5-3, where: + +- $f_{\text{offset\_CW}}$ is the offset between the outer channel edge frequency of the outer channel in the *passband* and a CW signal. + +Table 6.4.5-1: Out of band gain limits 1 for bands below 2496 MHz + +| Frequency offset, $f\_offset\_CW$ | Maximum gain | +|-------------------------------------|--------------| +| $0,2 \leq f\_offset\_CW < 1,0$ MHz | 60.5 dB | +| $1,0 \leq f\_offset\_CW < 5,0$ MHz | 45.5 dB | +| $5,0 \leq f\_offset\_CW < 10,0$ MHz | 45.5 dB | +| $10,0$ MHz $\leq f\_offset\_CW$ | 35.5 dB | + +Table 6.4.5-2: Out of band gain limits 1 for bands above 2496 MHz and below 3000 MHz + +| Frequency offset, $f\_offset\_CW$ | Maximum gain | +|-----------------------------------|--------------| +| $[0,2] < f\_offset\_CW < 4,0$ MHz | 60.5 dB | +| $4,0 < f\_offset\_CW < 15,0$ MHz | 45.5 dB | +| $15,0$ MHz $< f\_offset\_CW$ | 35.5 dB | + +Table 6.4.5-3: Out of band gain limits 1 for bands above above 3000 MHz + +| Frequency offset, $f\_offset\_CW$ | Maximum gain | +|-----------------------------------|--------------| +| $[0,2] < f\_offset\_CW < 4,0$ MHz | 60.8 dB | +| $4,0 < f\_offset\_CW < 15,0$ MHz | 45.8 dB | +| $15,0$ MHz $< f\_offset\_CW$ | 35.8 dB | + +## 6.5 Unwanted emissions + +### 6.5.1 General + +Unwanted emissions consist of out-of-band emissions and spurious emissions according to ITU definitions [4]. 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. + +The out-of-band emissions requirement for the Repeater transmitter is specified both in terms of Adjacent Channel Leakage power Ratio (ACLR) and *operating band* unwanted emissions (OBUE). + +The maximum offset of the *operating band* unwanted emissions mask from the *operating band* edge is $\Delta f_{OBUE}$ . The Operating band unwanted emissions define all unwanted emissions in each supported downlink *operating band* of *repeater type 1-C* DL and uplink *operating band* of *repeater type 1-C* UL, plus the frequency ranges $\Delta f_{OBUE}$ above and $\Delta f_{OBUE}$ below each band. Unwanted emissions outside of this frequency range are limited by a spurious emissions requirement. + +The values of $\Delta f_{OBUE}$ are defined in tables 6.5.1-1 and 6.5.1-2 for the NR *operating bands*. + +Table 6.5.1-1: Maximum offset of OBUE outside the downlink *operating band* of *repeater type 1-C* DL + +| Repeater type | Operating band characteristics | $\Delta f_{OBUE}$ (MHz) | +|-------------------|--------------------------------------------------------|-------------------------| +| Repeater type 1-C | $F_{DL,high} - F_{DL,low} < 200$ MHz | 10 | +| | $200$ MHz $\leq F_{DL,high} - F_{DL,low} \leq 900$ MHz | 40 | + +Table 6.5.1-2: Maximum offset of OBUE outside the uplink *operating band* of *repeater 1-C* UL + +| Repeater type | Operating band characteristics | $\Delta f_{OBUE}$ (MHz) | +|-------------------|--------------------------------------------------------|-------------------------| +| Repeater type 1-C | $F_{UL,high} - F_{UL,low} < 200$ MHz | 10 | +| | $200$ MHz $\leq F_{UL,high} - F_{UL,low} \leq 900$ MHz | 40 | + +### 6.5.2 Adjacent Channel Leakage Power Ratio (ACLR) + +#### 6.5.2.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. + +The requirements shall apply outside the *repeater type 1-C passband* whatever the type of transmitter considered (single carrier or multi-carrier) and for all transmission modes foreseen by the manufacturer's specification. + +For a *repeater* operating in *non-contiguous spectrum*, the ACLR requirement in clause 6.5.2.5 shall apply in *gaps between passbands* for the frequency ranges defined in table 6.5.2.5-3 or 6.5.2.5-3a, while the CACLR requirement in clause 6.5.2.5 shall apply in *gaps between passbands* for the frequency ranges defined in table 6.5.2.5-4 or 6.5.2.5-4a. + +For a *multi-band connector*, the ACLR requirement in clause 6.5.2.5 shall apply in *inter-passband gaps* for the frequency ranges defined in table 6.5.2.5-3 or 6.5.2.5-3a, while the CACLR requirement in clause 6.5.2.5 shall apply in *inter-passband gaps* for the frequency ranges defined in table 6.5.2.5-4 or 6.5.2.5-4a. + +The requirement shall apply during the *transmitter ON state*. + +#### 6.5.2.2 Minimum requirement + +The minimum requirement applies per *single-band connector*, or per *multi-band connector* supporting transmission in the *operating band*. + +The minimum requirement in TS 38.106 [2], clause 6.5.2.2. + +#### 6.5.2.3 Test purpose + +To verify that the adjacent channel leakage power ratio requirement shall be met as specified by the minimum requirement. + +#### 6.5.2.4 Method of test + +##### 6.5.2.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.9.1. + +##### 6.5.2.4.2 Procedure + +- 1) Connect the *single-band connector* or *multi-band connector* under test to measurement equipment as shown in annex D.3. All connectors not under test shall be terminated. + +The measurement device characteristics shall be: + +- Measurement filter bandwidth: defined in clause 6.5.2.5. + - Detection mode: true RMS voltage or true average power. +- 2) Set the input signal to the representative connectors under test according to the applicable test configuration in clause 4.7 using the corresponding test models RDL-FR1-TM1.1 and RUL-FR1-TM1.1 in clause 4.9.2 at the input power intended to produce the maximum rated output power, $P_{\text{in,p,AC}} + 10\text{dB}$ . + - 3) Measure ACLR for the frequency offsets both side of the passband edge as specified in clause 6.5.2.5. In multiple carrier case only offset frequencies below the lowest and above the highest carrier frequency used shall be measured. + - 4) For the ACLR requirement applied inside *gap between passbands*, or inside *Inter passband gap* for multi-band operation: + +- a) Measure ACLR inside *gap between passbands* or *Inter passband gap* as specified in clause 6.5.2.5, if applicable. + - b) Measure CACLR inside *gap between passbands* or *Inter passband gap* as specified in clause 6.5.2.5, if applicable. +- 5) Repeat the test with the channel set-up according to RDL-FR1-TM1.2 for DL and RUL-FR1-TM1.2 for UL in clause 4.9.2. + +In addition, for *multi-band connectors*, the following steps shall apply: + +- 6) 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.5.2.5 Test requirements + +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. + +The ACLR shall be higher than the value specified in table 6.5.2.5-1 for *repeater type 1-C* for DL and UL for Wide Area class. + +For *repeater type 1-C* for DL and for UL for WA class, the ACLR (CACLR) absolute limits in table 6.5.2.5-2, 6.5.2.5-5 or the ACLR (CACLR) *limits* in table 6.5.2.5-1, 6.5.2.5-3 or 6.5.2.5-4, whichever is less stringent, shall apply for each *antenna connector*. + +For Band n41 and n90 operation in Japan, absolute ACLR limits shall be applied to the sum of the absolute ACLR power over all *antenna connectors* for *repeater type 1-C*. + +**Table 6.5.2.5-1: Repeater type 1-C ACLR limit for DL and for UL for Wide Area class** + +| Repeater type 1-C nominal channel bandwidth BW_{Nominal} (MHz) | Repeater type 1-C adjacent channel centre frequency offset below or above the passband edge | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------|--------------------------------------| +| 5, 10, 15, 20 | $BW_{Nominal}/2$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 44.2 dB (Note 4)
37.2 dB (Note 5) | +| | $1.5 \times BW_{Nominal}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 44.2 dB (Note 4)
37.2 dB (Note 5) | +| | 2.5 MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 44.2 dB (Note 3) | +| | 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_{Nominal}/2$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 43.8 dB (Note 4)
36.8 dB (Note 5) | +| | $1.5 \times BW_{Nominal}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 43.8 dB (Note 4)
36.8 dB (Note 5) | +| | 2.5 MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 43.8 dB (Note 3) | +| | 7.5 MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 43.8 dB (Note 3) | + +NOTE 1: $BW_{Nominal}$ is the *nominal channel bandwidth*. $BW_{Config}$ is the *transmission bandwidth configuration* assumed for the adjacent channel. +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. +NOTE 4: Applicable to bands other than n104. +NOTE 5: Applicable to band n104. + +The ACLR absolute limit is specified in table 6.5.2.5-2. + +The ACLR shall be higher than the value specified in table 6.5.2.5-1a for *repeater type 1-C* for UL Local Area. + +Table 6.5.2.5-1a: Repeater type 1-C ACLR limit for UL for Local Area + +| Repeater type 1-C nominal channel bandwidth $BW_{Nominal}$ (MHz) | Repeater type 1-C adjacent channel centre frequency offset below above the passband edge | Assumed adjacent channel carrier (informative) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit | +|------------------------------------------------------------------|------------------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------|------------| +| 5, 10, 15, 20 | $BW_{Nominal}/2$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 30.2 dB | +| | $1.5 \times BW_{Nominal}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 30.2 dB | +| | 2.5 MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 30.2 dB | +| | 7.5 MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 30.2 dB | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $BW_{Nominal}/2$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 29.8 dB | +| | $1.5 \times BW_{Nominal}$ | NR of same BW (Note 2) | Square ( $BW_{Config}$ ) | 29.8 dB | +| | 2.5 MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 29.8 dB | +| | 7.5 MHz | 5 MHz E-UTRA | Square (4.5 MHz) | 29.8 dB | + +NOTE 1: $BW_{Nominal}$ is the *nominal channel bandwidth*. $BW_{Config}$ is the *transmission bandwidth configuration* assumed for the adjacent channel. + +NOTE 2: With SCS that provides the largest *transmission bandwidth configuration* ( $BW_{Config}$ ). + +NOTE 3: The requirements are applicable when the band is also defined for E-UTRA or UTRA. + +Table 6.5.2.5-2: Repeater type 1-C ACLR absolute limit for DL and UL for WA class, for DL for MR class and for DL for LA class + +| Repeater category / class | ACLR absolute limit | +|--------------------------------|---------------------| +| Category A Wide Area DL and UL | -13 dBm/MHz | +| Category B Wide Area DL and UL | -15 dBm/MHz | +| Medium Range DL | -25 dBm/MHz | +| Local Area DL | -32 dBm/MHz | + +For operation in non-contiguous spectrum or multiple bands, the ACLR shall be higher than the value specified in Table 6.5.2.5-3 or Table 6.5.2.5-3a. + +Table 6.5.2.5-3: Repeater type 1-C ACLR limit in non-contiguous spectrum or multiple bands for DL (all repeater classes) and for UL for Wide Area class + +| Repeater type 1-C nominal channel bandwidth $BW_{Nominal}$ (MHz) | Gap between passbands or inter-passband gap size ( $W_{gap}$ ) where the limit applies (MHz) | Repeater type 1-C adjacent channel centre frequency offset below or above the passband 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 (Note 5)
37.2 dB (Note 6) | +| | $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 (Note 5)
37.2 dB (Note 6) | +| 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 (Note 5)
36.8 dB (Note 6) | +| | $W_{gap} \geq 80$ (Note 4)
$W_{gap} \geq 50$ (Note 3) | 30 MHz | 20 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 43.8 dB (Note 5)
36.8 dB (Note 6) | + +NOTE 1: $BW_{Nominal}$ is the *nominal channel bandwidth*. $BW_{Config}$ is the *transmission bandwidth configuration* assumed for the adjacent channel. + +NOTE 2: With SCS that provides the largest *transmission bandwidth configuration* ( $BW_{Config}$ ). + +NOTE 3: Applicable in case the *repeater type 1-C nominal channel bandwidth* at the other edge of the gap is $\leq 20$ MHz. + +NOTE 4: Applicable in case the *repeater type 1-C nominal channel bandwidth* at the other edge of the gap is $> 20$ MHz. + +NOTE 5: Applicable to bands other than n104. + +NOTE 6: Applicable to band n104. + +**Table 6.5.2.5-3a: Repeater type 1-C ACLR limit in non-contiguous spectrum or multiple bands for UL for Local Area class** + +| Repeater type 1-C nominal channel bandwidth BW_{Nominal} (MHz) | Gap between passbands or inter-passband gap size (W_{gap}) where the limit applies (MHz) | Repeater type 1-C adjacent channel centre frequency offset below or above the passband 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}$ ) | 30.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}$ ) | 30.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}$ ) | 29.8 dB | +| | $W_{gap} \geq 80$ (Note 4)
$W_{gap} \geq 50$ (Note 3) | 30 MHz | 20 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 29.8 dB | + +NOTE 1: $BW_{Nominal}$ is the *nominal channel bandwidth*. $BW_{Config}$ is the *transmission bandwidth configuration* assumed for the adjacent channel. + +NOTE 2: With SCS that provides the largest *transmission bandwidth configuration* ( $BW_{Config}$ ). + +NOTE 3: Applicable in case the *repeater type 1-C nominal channel bandwidth* at the other edge of the gap is $\leq 20$ MHz. + +NOTE 4: Applicable in case the *repeater type 1-C nominal channel bandwidth* at the other edge of the gap is $> 20$ MHz. + +The Cumulative Adjacent Channel Leakage power Ratio (CACLR) in a *gap between passband* or the *inter-passband 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 *gap between passband* or the *inter-passband gap*, and +- the filtered mean power centred on a frequency channel adjacent to one of the respective *repeater type 1-C passband edges*. + +The assumed filter for the adjacent channel frequency is defined in table 6.5.2.5-4 and 6.5.2.5-4a and the filters on the assigned channels are defined in table 6.5.2.5-6. + +For operation in *non-contiguous spectrum* or multiple bands, the CACLR for *repeater type 1-C* for DL and for UL for WA class for NR carriers located on either side of the *gap between passband* or the *inter-passband gap* shall be higher than the value specified in table 6.5.2.5-4. + +Table 6.5.2.5-4: Repeater type 1-C CACLR limit for DL and for UL for Wide Area class + +| Repeater type 1-C nominal channel bandwidth $BW_{Nominal}$ (MHz) | Gap between passbands or inter-passband gap size ( $W_{gap}$ ) where the limit applies (MHz) | Repeater type 1-C adjacent channel centre frequency offset below or above the passband 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) | Square ( $BW_{Config}$ ) | 44.2 dB | +| 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) | Square ( $BW_{Config}$ ) | 43.8 dB | + +NOTE 1: $BW_{Nominal}$ is the *nominal channel bandwidth*. $BW_{Config}$ is the *transmission bandwidth configuration* assumed for the adjacent channel. + +NOTE 2: With SCS that provides the largest *transmission bandwidth configuration* ( $BW_{Config}$ ). + +NOTE 3: Applicable in case the *repeater type 1-C nominal channel bandwidth* at the other edge of the gap is $\leq 20$ MHz. + +NOTE 4: Applicable in case the *repeater type 1-C nominal channel bandwidth* at the other edge of the gap is $> 20$ MHz. + +The CACLR shall be higher than the value specified in table 6.5.2.5-4a for *repeater type 1-C* for UL Local Area. + +Table 6.5.2.5-4a: Repeater type 1-C CACLR limit for UL for Local Area + +| Repeater type 1-C nominal channel bandwidth $BW_{Nominal}$ (MHz) | Gap between passbands or inter-passband gap size ( $W_{gap}$ ) where the limit applies (MHz) | Repeater type 1-C adjacent channel centre frequency offset below or above the passband 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}$ ) | 30.2 dB | +| | $10 < W_{gap} < 20$ (Note 3)
$10 \leq W_{gap} < 50$ (Note 4) | 7.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 30.2 dB | +| 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}$ ) | 29.8 dB | +| | $40 < W_{gap} < 80$ (Note 4)
$40 \leq W_{gap} < 50$ (Note 3) | 30 MHz | 20 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 29.8 dB | + +NOTE 1: $BW_{Nominal}$ is the *nominal channel bandwidth*. $BW_{Config}$ is the *transmission bandwidth configuration* assumed for the adjacent channel. + +NOTE 2: With SCS that provides the largest *transmission bandwidth configuration* ( $BW_{Config}$ ). + +NOTE 3: Applicable in case the *repeater type 1-C nominal channel bandwidth* at the other edge of the gap is $\leq 20$ MHz. + +NOTE 4: Applicable in case the *repeater type 1-C nominal channel bandwidth* at the other edge of the gap is $> 20$ MHz. + +The CACLR absolute limit is specified in table 6.5.2.5-5. + +**Table 6.5.2.5-5: Repeater type 1-C CACLR absolute limit for DL and UL for WA class, for DL for MR class and for DL for LA class** + +| Repeater type 1-C category / class | CACLR absolute limit | +|------------------------------------|----------------------| +| Category A Wide Area DL and UL | -13 dBm/MHz | +| Category B Wide Area DL and UL | -15 dBm/MHz | +| Medium Range DL | -25 dBm/MHz | +| Local Area DL | -32 dBm/MHz | + +**Table 6.5.2.5-6: Filter parameters for the assigned channel** + +| RAT of the carrier adjacent to the gap between passbands or inter-passband gap | Filter on the assigned channel frequency and corresponding filter bandwidth | +|--------------------------------------------------------------------------------|-----------------------------------------------------------------------------------| +| NR | NR of same BW with SCS that provides largest transmission bandwidth configuration | + +### 6.5.3 Operating band unwanted emissions + +#### 6.5.3.1 Definition and applicability + +Unless otherwise stated, the operating band unwanted emission (OBUE) limits for *repeater type 1-C* DL are defined from $\Delta f_{\text{OBUE}}$ below the lowest frequency of each supported downlink *operating band* 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.5.1-1 for the NR *operating bands*. + +Unless otherwise stated, the operating band unwanted emission (OBUE) limits for *repeater type 1-C* UL are defined from $\Delta f_{\text{OBUE}}$ below the lowest frequency of each supported uplink *operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of each supported uplink *operating band*. The values of $\Delta f_{\text{OBUE}}$ are defined in table 6.5.1-2 for the NR *operating bands*. + +The requirements shall apply whatever the type of transmitter considered and for all transmission modes foreseen by the manufacturer's specification. In addition, for *repeater type 1-C* operating in *non-contiguous spectrum*, the requirements apply inside any *gap between passband*. In addition, for a *repeater type 1-C* operating in multiple bands, the requirements apply inside any *inter-passband gap*. + +*Limits* are specified in the tables below, where: + +- $\Delta f$ is the separation between the *passband edge* frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency. +- $f_{\text{offset}}$ is the separation between the *passband 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* of *repeater type 1-C* DL and uplink *operating band* of *repeater type 1-C* UL, where $\Delta f_{\text{OBUE}}$ is defined in tables 6.5.1-1 and 6.5.1-2. +- $\Delta f_{\text{max}}$ is equal to $f_{\text{offsetmax}}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band connector* inside any *inter-passband gaps* with $W_{\text{gap}} < 2 * \Delta f_{\text{OBUE}}$ , a combined minimum requirement shall be applied which is the cumulative sum of the minimum requirement specified at the *repeater type 1-C passband edges* on each side of the *inter-passband gap*. + +- $\Delta f$ is the separation between the *repeater type 1-C passband edge* frequency and the nominal -3 dB point of the measuring filter closest to the *repeater type 1-C passband edge*. +- $f_{\text{offset}}$ is the separation from the *repeater type 1-C passband edge* frequency to the centre of the measuring filter. +- $f_{\text{offsetmax}}$ is equal to the *inter-passband 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 connector* of *repeater type 1-C DL*, the operating band unwanted emission limits apply also in a supported downlink *operating band* without any carrier transmitted, in the case where there are carrier(s) transmitted in another supported downlink *operating band*. In this case, no cumulative minimum requirement 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 * \Delta f_{\text{OBUE}}$ , $f\_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 minimum requirement 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 minimum requirement 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 *multi-band connector* of *repeater type 1-C UL*, the operating band unwanted emission limits apply also in a supported uplink *operating band* without any carrier transmitted, in the case where there are carrier(s) transmitted in another supported uplink *operating band*. In this case, no cumulative minimum requirement is applied in the *inter-band gap* between a supported uplink *operating band* with carrier(s) transmitted and a supported uplink *operating band* without any carrier transmitted and + +- In case the *inter-band gap* between a supported uplink *operating band* with carrier(s) transmitted and a supported uplink *operating band* without any carrier transmitted is less than $2 * \Delta f_{\text{OBUE}}$ , $f\_offset_{\max}$ shall be the offset to the frequency $\Delta f_{\text{OBUE}}$ MHz outside the outermost edges of the two supported uplink *operating bands* and the operating band unwanted emission minimum requirement of the band where there are carriers transmitted, as defined in the tables of the present clause, shall apply across both uplink bands. +- In other cases, the operating band unwanted emission minimum requirements 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 uplink *operating band* without any carrier transmitted. + +In addition, inside any *gap between passband* for a *single-band connector* operating in *non-contiguous spectrum*, a combined minimum requirement shall be applied which is the cumulative sum of the minimum requirement specified for the adjacent *sub-blocks* on each side of the *gap between passband*. + +- $\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 *gap between passband* 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. + +#### 6.5.3.2 Minimum requirement + +The minimum requirement applies per *single-band connector*, or per *multi-band connector* supporting transmission in the *operating band*. + +The minimum requirement is defined in TS 38.106 [2], clause 6.5.3.2 + +#### 6.5.3.3 Test purpose + +This test measures the emissions close to the assigned channel bandwidth of the wanted signal, while the transmitter is in operation. + +#### 6.5.3.4 Method of test + +##### 6.5.3.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.9.1. + +##### 6.5.3.4.2 Procedure + +- 1) Connect the *single-band connector* or *multi-band connector* under test to measurement equipment as shown in annex D.1.1. All 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. + +- 2) Set the input signal to the representative connectors under test according to the applicable test configuration in clause 4.8 using the corresponding test models NR-FR1-TM 1.1 in clause 4.9.2 at the input power intended to produce the maximum rated output power, $P_{\text{in,p,AC}} + 10\text{dB}$ . +- 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. For connector under test declared to operate in multiple bands or non-contiguous spectrum, the emission within the *Inter passband Bandwidth* or *sub-block gap* shall be measured using the specified measurement bandwidth from the closest RF Bandwidth or sub block edge. +- 4) Repeat the test for the remaining test cases, with the channel set-up according to NR-FR1-TM 1.2. + +In addition, for *multi-band connectors*, the following steps shall apply: + +- 5) 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.5.3.4 Test requirements + +##### 6.5.3.4.1 Minimum requirements for Wide Area repeater type 1-C (Category A) + +For repeater operating in Bands n5, n8, n12, n13, n14, n18, n26, n28, n29, n31, n71, n72, n85, n106, minimum requirements are specified in table 6.5.3.4.1-1. + +**Table 6.5.3.4.1-1: Wide Area repeater type 1-C operating band unwanted emission minimum requirements (NR bands below 1 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirements (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.5 \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})$ | -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 3) | 100 kHz | + +NOTE 1: For a *repeater type 1-C* supporting *non-contiguous spectrum* operation within any *operating band*, the emission limits within *gaps between passbands* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* on each side of the *gap between passband*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent *sub-blocks* on each side of the *gap between passband*, where the emission limits within *gaps between passbands* shall be -13 dBm/1 MHz. + +NOTE 2: For a *multi-band connector* with *inter-passband gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the emission limits within the *inter-passband gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* or *passband* on each side of the *inter-passband gap*, where the contribution from the far-end *sub-block* or *passband* shall be scaled according to the *measurement bandwidth* of the near-end *sub-block* or *passband*. + +NOTE 3: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +For *repeater type 1-C* operating in Bands n1, n2, n3, n7, n24, n25, n30, n34, n38, n39, n40, n41, n50, n54, n65, n66, n70, n74, n75, n92, n94, n109 minimum requirements are specified in table 6.5.3.4.1-2: + +**Table 6.5.3.4.1-2: Wide Area repeater type 1-C operating band unwanted emission minimum requirements (1GHz < NR bands $\leq$ 3GHz) 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 | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-5.5 \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})$ | -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 3) | 1MHz | + +NOTE 1: For a *repeater* 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 -13 dBm/1 MHz. + +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*, 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}$ . + +For *repeater type 1-C* operating in Bands n48, n77, n78, n79, *minimum requirements* are specified in table 6.5.3.4.1-3: + +**Table 6.5.3.4.1-3: Wide Area repeater type 1-C operating band unwanted emission limits (NR bands >3GHz) 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 | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-5.2 \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})$ | -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 3) | 1MHz | + +NOTE 1: For a repeater 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 -13 dBm/1 MHz. + +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, 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}$ . + +##### 6.5.3.4.2 Minimum requirements for Wide Area repeater type 1-C (Category B) + +For Category B Operating band unwanted emissions, there are two options for the *minimum requirements* that may be applied regionally. Either the *minimum requirements* in clause 6.5.3.4.2.1 or clause 6.5.3.4.2.2 shall be applied. + +###### 6.5.3.4.2.1 Category B requirements (Option 1) + +For *repeater type 1-C* operating in Bands n5, n8, n12, n20, n26, n28, n29, n31, n67, n71, n72, n85, the minimum requirements are specified in table 6.5.3.4.2.1-1: + +**Table 6.5.3.4.2.1-1: Wide Area repeater type 1-C operating band unwanted emission minimum requirements (NR bands below 1 GHz) 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 | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-5.5 \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})$ | -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}$ | -16 dBm (Note 3) | 100 kHz | + +NOTE 1: For a *repeater type 1-C* supporting *non-contiguous spectrum* operation within any *operating band*, the emission limits within *gaps between passbands* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* on each side of the *gap between passband*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent *sub-blocks* on each side of the *gap between passband*, where the emission limits within *gaps between passbands* shall be -15 dBm/1 MHz. + +NOTE 2: For a *multi-band connector* with *inter-passband gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the emission limits within the *inter-passband gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* or *passband* on each side of the *inter-passband gap*. + +NOTE 3: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +For *repeater type 1-C* operating in Bands n1, n2, n3, n7, n25, n34, n38, n39, n40, n41, n48, n50, n65, n66, n70, n75, n92, n94, n109, minimum requirements are specified in table 6.5.3.4.2.1-2: + +**Table 6.5.3.4.2.1-2: Wide Area repeater type 1-C operating band unwanted emission limits (1GHz < NR bands ≤ 3GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirements (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.5 \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})$ | -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 *repeater type 1-C* supporting *non-contiguous spectrum* operation within any *operating band*, the emission limits within *gaps between passbands* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* on each side of the *gap between passband*, 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 *gap between passband*, where the emission limits within *gaps between passbands* shall be -15 dBm/1 MHz. + +NOTE 2: For a *multi-band connector* with *inter-passband gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the emission limits within the *inter-passband gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* or *passband* on each side of the *inter-passband gap*, where the contribution from the far-end *sub-block* or *passband* shall be scaled according to the *measurement bandwidth* of the near-end *sub-block* or *passband*. + +NOTE 3: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +For *repeater type 1-C* operating in Bands n48, n77, n78, n79, *minimum requirements* are specified in tables 6.5.3.4.2.1-3: + +**Table 6.5.3.4.2.1-3: Wide Area repeater operating band unwanted emission limits (NR bands >3GHz) 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 | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-5.2 \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})$ | -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 *repeater* 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 \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*, 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}$ . + +###### 6.5.3.4.2.2 Category B requirements (Option 2) + +The limits in this clause are intended for Europe and may be applied regionally for *repeater type 1-C* operating in bands n1, n3, n7, n8, n38, n65. + +For a *repeater type 1-C* operating in bands n1, n3, n7, n8, n38 or n65, *minimum requirements* are specified in Table 6.5.3.4.2.2-1: + +**Table 6.5.3.4.2.2-1: Regional Wide Area *repeater type 1-C* operating band unwanted emission minimum requirements for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirements (Note 1, 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}$ | 30 kHz | +| (Note 4) | $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 3) | 1 MHz | + +NOTE 1: For a *repeater type 1-C* supporting *non-contiguous spectrum* operation within any *operating band*, the emission limits within *gaps between passbands* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* on each side of the *gap between passband*, 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 *gap between passband*, where the emission limits within *gaps between passbands* shall be -15 dBm/1 MHz. + +NOTE 2: For a *multi-band connector* with *inter-passband gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the emission limits within the *inter-passband gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* or *passband* on each side of the *inter-passband gap*, where the contribution from the far-end *sub-block* or *passband* shall be scaled according to the *measurement bandwidth* of the near-end *sub-block* or *passband*. + +NOTE 3: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +NOTE 4: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +##### 6.5.3.4.3 Minimum requirements for Medium Range *repeater type 1-C* (Category A and B) for DL + +For Medium Range *repeater type 1-C* for DL, minimum requirements are specified in table 6.5.3.4.3-1 to table 6.5.3.4.3-4. + +For the tables in this clause for *repeater type 1-C*, $P_{\text{rated},x} = P_{\text{rated,p,AC}} - 10 \cdot \log(\text{ceil}(\text{BW}_{\text{Passband}}/20 \text{ MHz}))$ + +**Table 6.5.3.4.3-1: Medium Range *repeater type 1-C* operating band unwanted emission minimum requirements, $31 < P_{\text{rated},x} \leq 38 \text{ dBm}$ (NR bands $\leq 3 \text{ GHz}$ )** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirements (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},x} - 51.5 \text{ dB} - \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})$ | $P_{\text{rated},x} - 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}$ | $\text{Min}(P_{\text{rated},x} - 60 \text{ dB}, -25 \text{ dBm})$ (Note 3) | 100 kHz | + +NOTE 1: For a *repeater type 1-C* DL supporting *non-contiguous spectrum* operation within any *operating band* the emission limits within *gaps between passbands* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* on each side of the *gap between passband*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent *sub-blocks* on each side of the *gap between passband*, where the emission limits within *gaps between passbands* shall be $\text{Min}(P_{\text{rated},x} - 60 \text{ dB}, -25 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band connector* with *inter-passband gap* $< 2 \cdot \Delta f_{\text{OBUE}}$ the emission limits within the *inter-passband gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* or *passband* on each side of the *inter-passband gap*. + +NOTE 3: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.5.3.4.3-2: Medium Range repeater type 1-C operating band unwanted emission minimum requirements, $P_{\text{rated,x}} \leq 31$ dBm (NR bands $\leq 3$ GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirements (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}$ | $-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 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 3) | 100 kHz | + +NOTE 1: For a repeater type 1-C DL supporting non-contiguous spectrum operation within any operating band the emission limits within gaps between passbands is calculated as a cumulative sum of contributions from adjacent sub-blocks on each side of the gap between passband. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent sub-blocks on each side of the gap between passband, where the emission limits within gaps between passbands shall be -29dBm/100kHz. + +NOTE 2: For a multi-band connector with inter-passband gap $< 2 * \Delta f_{\text{OBUE}}$ the emission limits within the inter-passband gaps is calculated as a cumulative sum of contributions from adjacent sub-blocks or passband on each side of the inter-passband gap. + +NOTE 3: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.5.3.4.3-3: Medium Range repeater operating band unwanted emission limits, $31 < P_{\text{rated,x}} \leq 38$ dBm (NR bands $> 3 \text{ GHz}$ )** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirements (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,x}} - 51.2 \text{ dB} - \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})$ | $P_{\text{rated,x}} - 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,x}} - 60 \text{ dB}, -25 \text{ dBm})$ (Note 3) | 100 kHz | + +NOTE 1: For a repeater 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,x}} - 60 \text{ dB}, -25 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a multi-band connector with Inter RF Bandwidth gap $< 2 * \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_{\max} < 10 \text{ MHz}$ . + +**Table 6.5.3.4.3-4: Medium Range repeater operating band unwanted emission limits, $P_{\text{rated,x}} \leq 31$ dBm (NR bands >3GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirements (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}$ | $-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 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 3) | 100 kHz | + +NOTE 1: For a repeater 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 * \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_{\max} < 10 \text{ MHz}$ . + +##### 6.5.3.4.4 Minimum requirements for Local Area *repeater type 1-C* (Category A and B) + +For Local Area *repeater type 1-C* in NR bands $\leq 3 \text{ GHz}$ , *minimum requirements* are specified in table 6.5.3.4.4-1. + +For Local Area *repeater type 1-C* in NR bands $> 3 \text{ GHz}$ , *minimum requirements* are specified in table 6.5.3.4.4-2. + +**Table 6.5.3.4.4-1: Local Area *repeater type 1-C* operating band unwanted emission limits (NR bands $\leq 3 \text{ GHz}$ )** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirements (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}$ | $-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 10) | 100 kHz | + +NOTE 1: For a *repeater type 1-C* supporting *non-contiguous spectrum* operation within any *operating band* the emission limits within *gaps between passbands* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* on each side of the *gap between passband*. Exception is $\Delta f \geq 10 \text{ MHz}$ from both adjacent *sub-blocks* on each side of the *gap between passband*, where the emission limits within *gaps between passbands* shall be -37dBm/100kHz. + +NOTE 2: For a *multi-band connector* with *inter-passband gap* $< 2 * \Delta f_{\text{OBUE}}$ the emission limits within the *inter-passband gaps* is calculated as a cumulative sum of contributions from adjacent *sub-blocks* or *passband* on each side of the *inter-passband gap* + +NOTE 3: The requirement is not applicable when $\Delta f_{\max} < 10 \text{ MHz}$ . + +**Table 6.5.3.4.4-2: Local Area repeater operating band unwanted emission limits (NR bands >3GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirements (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}$ | $-28.2 \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})$ | -35.2 dBm | | +| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 dBm (Note 3) | | + +NOTE 1: For a repeater 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 -37dBm/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_{\max} < 10 \text{ MHz}$ . + +##### 6.5.3.4.5 Minimum requirements for additional requirements + +###### 6.5.3.4.5.1 Limits in FCC Title 47 + +In addition to the requirements in clauses 6.5.3.4.1, 6.5.3.4.2, 6.5.3.4.3 and 6.5.3.4.4, the *repeater type 1-C* may have to comply with the applicable emission limits established by FCC Title 47 [13], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +###### 6.5.3.4.5.2 Protection of DTT + +In certain regions the following requirement may apply for protection of DTT. For *repeater type 1-C* operating in Band 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.5.3.4.5.2-1, a minimum requirements $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.5.3.4.5.2-1: Declared emissions minimum requirement for protection of DTT** + +| Filter centre frequency, $F_{\text{filter}}$ | Measurement bandwidth | Declared emission minimum requirement (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 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 36.104 [5], annex E. + +### 6.5.4 Transmitter spurious emissions + +#### 6.5.4.1 Definition and applicability + +For *repeater type 1-C*, the transmitter spurious emission limits shall apply from 9 kHz to 12.75 GHz, excluding the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of each supported downlink *operating band*, up to $\Delta f_{\text{OBUE}}$ above the highest frequency of each supported downlink *operating band*, where the $\Delta f_{\text{OBUE}}$ is defined in table 6.5.1-1. For some *operating bands*, the upper 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 [4]. + +For a *multi-band connector*, for each supported *operating band* together with $\Delta f_{\text{OBUE}}$ around the band is excluded from the transmitter spurious emissions requirement. + +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 specification. + +Unless otherwise stated, all requirements are measured as mean power (RMS). + +For Band n41 and n90 operation in Japan, the sum of the spurious emissions over all *antenna connectors* for *Repeater type 1-C* shall not exceed the *minimum requirements* defined in clause 6.5.4.5. + +#### 6.5.4.2 Minimum requirement + +The minimum requirement applies per *single-band connector*, or per *multi-band connector* supporting transmission in the *operating band*. + +The minimum requirement is defined in TS 38.106 [2], clause 6.5.4.2. + +#### 6.5.4.3 Test purpose + +This test measures conducted spurious emissions while the transmitter is in operation. + +#### 6.5.4.4 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 when testing the spurious emissions below $F_{\text{DL\_low}} - \Delta f_{\text{OBUE}}$ , +- T when testing the spurious emissions above $F_{\text{DL\_high}} + \Delta f_{\text{OBUE}}$ ; see clause 4.9.1. + +##### 6.5.4.4.2 Procedure + +- 1) Connect the *single-band connector* or *multi-band connector* under test to measurement equipment as shown in annex D.1.1. All connectors not under test shall be terminated. +- 2) Measurements shall use a measurement bandwidth in accordance to the conditions in clause 6.5.4.5. + +The measurement device characteristics shall be: + +- Detection mode: True RMS. + + - 3) Set the input signal to the representative connectors under test according to the applicable test configuration in clause 4.8 using the corresponding test models NR-FR1-TM 1.1 in clause 4.9.2 at the input power intended to produce the maximum rated output power, $P_{\text{in,p,AC}} + 10\text{dB}$ . + - 4) Measure the emission at the specified frequencies with specified measurement bandwidth. + +In addition, for *multi-band connectors*, the following steps shall apply: + +- 5) 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.5.4.5 Test requirements + +##### 6.5.4.5.1 General transmitter spurious emissions requirements + +The *minimum requirements* of either table 6.5.4.5.1-1, table 6.5.4.5.1-2 (Category A limits) or table 6.5.4.5.1-3 (Category B limits) shall apply. The application of either Category A or Category B limits shall be the same as for operating band unwanted emissions in clause 6.5.3. + +**Table 6.5.4.5.1-1: General *repeater type 1-C* transmitter spurious emission minimum requirements for DL in FR1, Category A** + +| Spurious frequency range | Minimum requirements | Measurement bandwidth | Notes | +|---------------------------------------------------------------------------------------------------------|----------------------|-----------------------|------------------------| +| 9 kHz – 150 kHz | -13 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 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 [4], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [4], s2.5 table 1. +NOTE 3: For *repeater type 1-C* DL, 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. + +**Table 6.5.4.5.1-2: General *repeater type 1-C* transmitter spurious emission minimum requirements for UL in FR1, Category A** + +| Spurious frequency range | Minimum requirements | 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 | -30 dBm | 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 [4], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [4], s2.5 table 1. +NOTE 3: For *repeater type 1-C* UL, 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. + +**Table 6.5.4.5.1-3: General *repeater type 1-C* transmitter spurious emission minimum requirements in FR1, Category B** + +| Spurious frequency range | minimum requirements | 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 | -30 dBm | 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 [4], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [4], s2.5 table 1. +NOTE 3: For *repeater type 1-C* DL, 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. +For *repeater type 1-C* UL, 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. + +##### 6.5.4.5.2 Additional spurious emissions requirements + +These requirements may be applied for the protection of system operating in other frequency ranges. The limits may apply as an optional protection of such systems that are deployed in the same geographical area as the repeater-Node, or they may be set by local or regional regulation as a mandatory requirement for an NR *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. + +Some requirements may apply for the protection of specific equipment (UE, MS and/or BS) or equipment operating in specific systems (GSM, CDMA, UTRA, E-UTRA, NR, etc.) as listed below. + +The spurious emission *minimum requirements* are provided in table 6.5.4.5.2-1 where requirements for co-existence with the system listed in the first column apply for *repeater type 1-C*. For a *multi-band connector*, the exclusions and conditions in the Note column of table 6.5.4.5.2-1 apply for each supported *operating band*. + +**Table 6.5.4.5.2-1: Repeater type 1-C spurious emissions minimum requirements for co-existence with systems operating in other frequency bands** + +| System type to co-exist with | Frequency range for co-existence requirement | Minimum requirements | Measurement bandwidth | Note | +|--------------------------------------------------|----------------------------------------------|----------------------|-----------------------|--------------------------------------------------------------------------------------------------------| +| GSM900 | 921 – 960 MHz | -57 dBm | 100 kHz | This requirement does not apply to repeater operating in band n8 | +| | 876 – 915 MHz | -61 dBm | 100 kHz | For the frequency range 880-915 MHz, this requirement does not apply to repeater operating in band n8. | +| DCS1800 | 1805 – 1880 MHz | -47 dBm | 100 kHz | This requirement does not apply to repeater operating in band n3. | +| | 1710 – 1785 MHz | -61 dBm | 100 kHz | This requirement does not apply to repeater operating in band n3. | +| PCS1900 | 1930 – 1990 MHz | -47 dBm | 100 kHz | This requirement does not apply to repeater operating in band n2, n25 or band n70. | +| | 1850 – 1910 MHz | -61 dBm | 100 kHz | This requirement does not apply to repeater operating in band n2 or n25. | +| GSM850 or | 869 – 894 MHz | -57 dBm | 100 kHz | This requirement does not apply to repeater operating in band n5 or n26. | +| CDMA850 | 824 – 849 MHz | -61 dBm | 100 kHz | This requirement does not apply to repeater operating in band n5 or n26. | +| UTRA FDD | 2110 – 2170 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n1 or n65 | +| Band I or E-UTRA Band 1 or NR Band n1 | 1920 – 1980 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n1 or n65. | +| UTRA FDD | 1930 – 1990 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n2 or n70. | +| Band II or E-UTRA Band 2 or NR Band n2 | 1850 – 1910 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n2. | +| UTRA FDD | 1805 – 1880 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n3. | +| Band III or E-UTRA Band 3 or NR Band n3 | 1710 – 1785 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n3. | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 – 2155 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n66 | +| | 1710 – 1755 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n66. | +| 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 repeater operating in band n5 or n26. | +| | 824 – 849 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n5 or n26. | +| UTRA FDD | 860 – 890 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n18. | +| Band VI, XIX or | 815 – 830 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n18. | +| E-UTRA Band 6, 18, 19 or NR Band n18 | 830 – 845 MHz | -49 dBm | 1 MHz | | +| 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 repeater operating in band n7. | +| | 2500 – 2570 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n7. | + +| | | | | | +|----------------------------------------------------|---------------------|---------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 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 repeater operating in band n8. | +| | 880 – 915 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n8. | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 – 1879.9 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n3. | +| | 1749.9 – 1784.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n3. | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 – 2170 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n66 | +| | 1710 – 1770 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n66. | +| 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 repeater operating in band n50, n74, n75, n92 or n94. | +| | 1427.9 – 1447.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n50, n51, n74, n75, n76, n91, n92, n93 or n94. | +| | 1447.9 – 1462.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n50, n74, n75, 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 repeater operating in band n12 or n85. | +| | 699 – 716 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n12 or n85.
For NR repeater operating in n29, it applies 1 MHz below the Band n29 downlink operating band (Note 5). | +| UTRA FDD Band XIII or E-UTRA Band 13 | 746 – 756 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n13. | +| | 777 – 787 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n13. | +| 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 repeater operating in band n14. | +| | 788 – 798 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n14. | +| E-UTRA Band 17 | 734 – 746 MHz | -52 dBm | 1 MHz | | +| | 704 – 716 MHz | -49 dBm | 1 MHz | For NR repeater operating in n29, it applies 1 MHz below the Band n29 downlink operating band (Note 5). | +| 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 repeater operating in band n20 or n28. | +| | 832 – 862 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n20. | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 – 3590 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n48, n77 or n78. | +| | 3410 – 3490 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n77 or n78. | + +| | | | | | +|-----------------------------------------------------|---------------------|---------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 24 | 1525 – 1559 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n24. | +| | 1626.5 – 1660.5 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n24. | +| 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 repeater operating in band n2, n25 or n70. | +| | 1850 – 1915 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n25 since it is already covered by the requirement in clause 6.5.4.5.2. For repeater operating in Band n2, it applies for 1910 MHz to 1915 MHz, while the rest is covered in clause 6.5.4.5.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 repeater operating in band n5 or n26. | +| | 814 – 849 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n26 since it is already covered by the requirement in clause 6.5.4.5.2. For repeater operating in Band n5, it applies for 814 MHz to 824 MHz, while the rest is covered in clause 6.5.4.5.2. | +| E-UTRA Band 27 | 852 – 869 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n5. | +| | 807 – 824 MHz | -49 dBm | 1 MHz | This requirement also applies to repeater operating in Band n28, starting 4 MHz above the Band n28 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 repeater operating in band n20, n67 or n28. | +| | 703 – 748 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n28.. For repeater operating in band n67, it applies for 703 MHz to 736 MHz. | +| E-UTRA Band 29 or NR Band n29 | 717 – 728 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n29 or n85 | +| E-UTRA Band 30 or NR Band n30 | 2350 – 2360 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n30 | +| | 2305 – 2315 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n30. | +| E-UTRA Band 31 or NR Band n31 | 462.5 – 467.5 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n31 or n72. | +| | 452.5 – 457.5 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n31, since it is already covered by the requirement in clause 6.5.4.5.2. This requirement does not apply to repeater operating in band n72. | +| UTRA FDD band XXXII or E-UTRA band 32 | 1452 – 1496 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n50, n74, n75, n92 or n94. | +| 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 or NR band n34 | 2010 – 2025 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n34. | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -52 dBm | 1 MHz | | + +| | | | | | +|---------------------------------------------------|-------------------|---------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 – 1990 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n2 or n25. | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 – 1930 MHz | -52 dBm | 1 MHz | | +| 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 repeater operating in Band n38. | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n39. | +| UTRA TDD Band e) or E-UTRA Band 40 or NR Band n40 | 2300 – 2400MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n30 or n40. | +| E-UTRA Band 41 or NR Band n41, n90 | 2496 – 2690 MHz | -52 dBm | 1 MHz | This is not applicable to repeater operating in Band n41, n53 or [n90]. | +| E-UTRA Band 42 | 3400 – 3600 MHz | -52 dBm | 1 MHz | This is not applicable to repeater operating in Band n48, n77 or n78. | +| E-UTRA Band 43 | 3600 – 3800 MHz | -52 dBm | 1 MHz | This is not applicable to repeater operating in Band n48, n77 or n78. | +| E-UTRA Band 44 | 703 – 803 MHz | -52 dBm | 1 MHz | This is not applicable to repeater operating in Band n28. | +| E-UTRA Band 45 | 1447 – 1467 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 46 | 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 repeater operating in Band n48, n77 or n78. | +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n50, n51, n74, n75, n76, n91, n92, n93, n94 or n109. | +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n50, n51, n75, n76, n91, n92, n93, n94 or n109. | +| E-UTRA Band 53 or NR Band n53 | 2483.5 - 2495 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n41, n53 or n90. | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n54 | +| E-UTRA Band 65 or NR Band n65 | 2110 – 2200 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n1 or n65. | +| | 1920 – 2010 MHz | -49 dBm | 1 MHz | For repeater operating in Band n1, it applies for 1980 MHz to 2010 MHz, while the rest is covered in clause 6.5.4.5.2.
This requirement does not apply to repeater operating in band n65. | +| E-UTRA Band 66 or NR Band n66 | 2110 – 2200 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n66. | +| | 1710 – 1780 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n66. | +| E-UTRA Band 67 or NR Band n67 | 738 – 758 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n28 or n67. | + +| | | | | | +|-------------------------------|-----------------|---------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 68 | 753 -783 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n28. | +| | 698-728 MHz | -49 dBm | 1 MHz | For repeater operating in Band n28, this requirement applies between 698 MHz and 703 MHz, while the rest is covered in clause 6.5.4.5.2. | +| E-UTRA Band 69 | 2570 – 2620 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n38. | +| E-UTRA Band 70 or NR Band n70 | 1995 – 2020 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n2, n25 or n70 | +| | 1695 – 1710 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n70.. | +| E-UTRA Band 71 or NR Band n71 | 617 – 652 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n71 or n105. | +| | 663 – 698 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n71 or n105. | +| E-UTRA Band 72 or NR Band n72 | 461 – 466 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n31 or n72. | +| | 451 – 456 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n72, since it is already covered by the requirement in clause 6.5.4.5.2. This requirement does not apply to BS operating in band n31. | +| E-UTRA Band 74 or NR Band n74 | 1475 – 1518 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n50, n74, n75, n92, n94 or n109. | +| | 1427 – 1470 MHz | -49 dBm | 1MHz | This requirement does not apply to repeater operating in band n50, n51, n74, n75, n76, n91, n92, n93, n94 or n109. | +| E-UTRA Band 75 or NR Band n75 | 1432 – 1517 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n50, n51, n74, n75, n76, n91, n92, n93, n94 or n109. | +| E-UTRA Band 76 or NR Band n76 | 1427 – 1432 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n50, n51, n75, n76, n91, n92, n93, n94 or n109. | +| NR Band n77 | 3.3 – 4.2 GHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n48, n77 or n78 | +| NR Band n78 | 3.3 – 3.8 GHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n48, n77 or n78 | +| NR Band n79 | 4.4 – 5.0 GHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n79 | +| NR Band n80 | 1710 – 1785 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n3. | +| NR Band n81 | 880 – 915 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n8. | +| NR Band n82 | 832 – 862 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n20. | +| NR Band n83 | 703 – 748 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n28.
For repeater operating in Band n67, it applies for 703 MHz to 736 MHz. | +| NR Band n84 | 1920 – 1980 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n1. | +| E-UTRA Band 85 or NR Band n85 | 728 – 746 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n12 or n85.
For NR repeater operating in n29, it applies 1 MHz below the Band n29 downlink operating band (Note 5). | +| | 698 – 716 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n12 or n85. | +| NR Band n86 | 1710 – 1780 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n66. | +| NR Band n89 | 824 – 849 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n5. | +| NR Band n91 | 1427 – 1432 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n50, n51, n75, n76 or n109. | + +| | | | | | +|---------------------------------|---------------------|---------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 832 – 862 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n20, since it is already covered by the requirement in clause 6.5.4.5.2. | +| NR Band n92 | 1432 – 1517 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n50, n51, n74, n75, n76 or n109. | +| | 832 – 862 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n20, since it is already covered by the requirement in clause 6.5.4.5.2. | +| NR Band n93 | 1427 – 1432 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n50, n51, n75, n76 or n109. | +| | 880 – 915 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n8, since it is already covered by the requirement in clause 6.5.4.5.2. | +| NR Band n94 | 1432 – 1517 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n50, n51, n74, n75, n76 or n109. | +| | 880 – 915 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n8, since it is already covered by the requirement in clause 6.5.4.5.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 repeater operating in band n24. | +| NR Band n100 | 919.4 – 925 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n8 or n100. | +| | 874.4 – 880 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band n100. | +| NR band n101 | 1900 – 1910 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in Band n101. | +| 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 | This requirement does not apply to repeater operating in Band n104 | +| NR band n105 | 612 – 652 MHz | -52 dBm | 1 MHz | This requirement does not apply to repeater operating in band n71 or n105. | +| | 663 – 703 MHz | -49 dBm | 1 MHz | This requirement does not apply to repeater operating in band 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 n106. | +| | 896 – 901 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n106, since it is already covered by the requirement in clause 6.6.5.2.2.
This requirement does not apply to BS operating in band n5 or n26. | +| NR band n109 | 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, n94 or n109 | +| | 703 – 733 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n109, since it is already covered by the requirement in clause 6.6.5.2.4. | + +NOTE 1: As defined in the scope for spurious emissions in this clause, except for the cases where the noted requirements apply to a repeater operating in Band n28, the co-existence requirements in table 6.5.4.5.2 - 1 do not apply for the $\Delta f_{\text{OBUE}}$ frequency range immediately outside the downlink *operating band*. Emission limits for this excluded frequency range may be covered by local or regional requirements. + +NOTE 2: Table 6.5.4.5.2 -1 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 3: For unsynchronized operation, special co-existence requirements may apply that are not covered by the 3GPP specifications. + +NOTE 4: For NR Band n28 repeater, specific solutions may be required to fulfil the spurious emissions limits for repeater for co-existence with E-UTRA Band 27 UL *operating band*. + +NOTE 5: For NR Band n29 repeater, specific solutions may be required to fulfil the spurious emissions limits for NR repeater 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 or NR Band n85 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 repeater transmitter frequency of the downlink *operating band* and $\Delta f_{\text{OBUE}}$ above the highest repeater transmitter frequency of the downlink *operating band*. $\Delta f_{\text{OBUE}}$ is defined in clause 6.5.1. + +The spurious emission *minimum requirements* for this requirement are: + +**Table 6.5.4.5.2-2: Repeater spurious emissions minimum requirements for repeater for co-existence with PHS for DL** + +| Frequency range | minimum requirements | Measurement Bandwidth | Note | +|---------------------|-----------------------------|------------------------------|-------------------------------------------------------------------------------| +| 1884.5 – 1915.7 MHz | -41 dBm | 300 kHz | Applicable when co-existence with PHS system operating in 1884.5 – 1915.7 MHz | + +In certain regions, the following requirement may apply to NR repeater operating in Band n50 and n75 within the 1432 – 1452 MHz, and in Band n51 and Band n76. The *minimum requirements* are specified in Table 6.5.4.5.2-3. This requirement is also applicable at the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the repeater downlink *operating band* up to $\Delta f_{\text{OBUE}}$ above the highest frequency of the repeater downlink *operating band*. + +**Table 6.5.4.5.2-3: Additional operating band unwanted emission minimum requirement for NR repeater operating in Band n50 and n75 within 1432 – 1452 MHz, and in Band n51 and n76** + +| Filter centre frequency, $F_{\text{filter}}$ | Minimum requirements | Measurement Bandwidth | +|----------------------------------------------|-----------------------------|------------------------------| +| $F_{\text{filter}} = 1413.5$ MHz | -42 dBm | 27 MHz | + +In certain regions, the following requirement may apply to repeater operating in NR Band n50 and n75 within 1492-1517 MHz and in Band n74 within 1492-1518 MHz. The maximum level of emissions, measured on centre frequencies $F_{\text{filter}}$ with filter bandwidth according to Table 6.5.4.5.2-4, shall be defined according to the *minimum requirements* $P_{\text{EM,n50/n75,a}}$ nor $P_{\text{EM,n50/n75,b}}$ declared by the manufacturer. + +**Table 6.5.4.5.2-4: Operating band n50, n74 and n75 declared emission above 1518 MHz** + +| Filter centre frequency, $F_{\text{filter}}$ | Declared minimum requirements (dBm) | Measurement bandwidth | +|-------------------------------------------------------|--------------------------------------------|------------------------------| +| $1518.5$ MHz $\leq F_{\text{filter}} \leq 1519.5$ MHz | $P_{\text{EM,n50/n75,a}}$ | 1 MHz | +| $1520.5$ MHz $\leq F_{\text{filter}} \leq 1558.5$ MHz | $P_{\text{EM,n50/n75,b}}$ | 1 MHz | + +In certain regions, the following requirement shall be applied to repeater operating in Band n13 and n14 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 repeater downlink *operating band* up to 10 MHz above the highest frequency of the repeater downlink *operating band*. + +The power of any spurious emission shall not exceed: + +**Table 6.5.4.5.2-5: Repeater spurious emissions limits for protection of 700 MHz public safety operations** + +| Operating Band | Frequency range | Maximum Level | Measurement Bandwidth | +|----------------|-----------------|---------------|-----------------------| +| n13 | 763 - 775 MHz | -46 dBm | 6.25 kHz | +| n13 | 793 - 805 MHz | -46 dBm | 6.25 kHz | +| n14 | 769 - 775 MHz | -46 dBm | 6.25 kHz | +| n14 | 799 - 805 MHz | -46 dBm | 6.25 kHz | + +In certain regions, the following requirement may apply to NR repeater operating in Band n30. This requirement is also applicable at the frequency range from 10 MHz below the lowest frequency of the repeater downlink operating band up to 10 MHz above the highest frequency of the repeater downlink operating band. + +The power of any spurious emission shall not exceed: + +**Table 6.5.4.5.2-6: Additional NR repeater spurious emissions minimum requirements for Band n30** + +| Frequency range | Minimum requirements | Measurement Bandwidth | Note | +|-------------------|----------------------|-----------------------|------| +| 2200 – 2345 MHz | -45 dBm | 1 MHz | | +| 2362.5 – 2365 MHz | -25 dBm | 1 MHz | | +| 2365 – 2367.5 MHz | -40 dBm | 1 MHz | | +| 2367.5 – 2370 MHz | -42 dBm | 1 MHz | | +| 2370 – 2395 MHz | -45 dBm | 1 MHz | | + +The following requirement may apply to repeater operating in Band n48 in certain regions. The power of any spurious emission shall not exceed: + +**Table 6.5.4.5.2-7: Additional repeater spurious emissions limits for Band n48** + +| Frequency range | Maximum Level | Measurement Bandwidth (NOTE) | Note | +|--------------------------------------------|---------------|------------------------------|----------------------------------------------------------| +| 3530 MHz – 3720 MHz | -25 dBm | 1 MHz | Applicable 10 MHz from the assigned passband edge | +| 3100 MHz – 3530 MHz
3720 MHz – 4200 MHz | -40 dBm | 1 MHz | | + +NOTE: 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: The regional requirement, included in [14], 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 F. + +The following requirement shall be applied to repeater operating in Band n26 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 repeater downlink operating band up to 10 MHz above the highest frequency of the repeater downlink operating band. + +The power of any spurious emission shall not exceed: + +**Table 6.5.4.5.2-8: Repeater spurious emissions limits for protection of 800 MHz public safety operations** + +| Operating Band | Frequency range | Maximum Level | Measurement Bandwidth | Note | +|----------------|-----------------|---------------|-----------------------|----------------------------------------------------------------| +| n26 | 851 - 859 MHz | -13 dBm | 100 kHz | Applicable for offsets > 37.5kHz from the passband edge | + +The following requirement may apply to Repeater for Band n41 and n90 operation in Japan. This requirement is also applicable at the frequency range from $\Delta f_{OBUE}$ below the lowest frequency of the Repeater downlink operating band up to $\Delta f_{OBUE}$ above the highest frequency of the Repeater downlink operating band. + +The power of any spurious emission shall not exceed: + +**Table 6.5.4.5.2-9: Additional repeater spurious emissions minimum requirements for Band n41 and n90** + +| Frequency range | Minimum requirement | Measurement Bandwidth | +|-----------------------------------------------------------------------------|---------------------|-----------------------| +| 2505 MHz – 2535 MHz | -42 dBm | 1 MHz | +| NOTE: This requirement applies for carriers allocated within 2545-2645 MHz. | | | + +The following requirement may apply to repeater operating in 3.45-3.55 GHz in Band n77 in certain regions. Emissions shall not exceed the maximum levels specified in table 6.5.4.2.3-11. + +**Table 6.5.4.5.2-10: Additional repeater spurious emissions limits for Band n77** + +| Channel bandwidth [MHz] | Frequency range [MHz] | Filter centre frequency, $F_{filter}$ [MHz] | Minimum requirement [dBm] | Measurement bandwidth [MHz] | +|-------------------------|----------------------------|------------------------------------------------------------------------|---------------------------|-----------------------------| +| All | 3430 – 3440
3560 – 3570 | $3430.5 \leq F_{filter} < 3439.5$
$3560.5 \leq F_{filter} < 3569.5$ | -25 | 1 | +| All | $\leq 3430$
$> 3570$ | $F_{filter} < 3429.5$
$3570.5 \leq F_{filter}$ | -40 | 1 | + +NOTE: 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. + +The following requirement may also apply to repeater operating in Band n54 in certain regions. The level of emissions in the 1541 – 1650 MHz band, measured in measurement bandwidth according to Table 6.5.4.5.2-11 shall not exceed the maximum emission levels $P_{EM,n54,a}$ , $P_{EM,n54,b}$ , $P_{EM,n54,c}$ , $P_{EM,n54,d}$ , $P_{EM,n54,e}$ and $P_{EM,n54,f}$ declared by the manufacturer. + +**Table 6.5.4.5.2-11: Declared Band n54 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) | +|----------------|-----------------|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| +| n54 | 1541 - 1559 MHz | $P_{EM,n54,a}$ | | $P_{EM,n54,f}$ | +| | 1559 - 1610 MHz | $P_{EM,n54,b}$ | $P_{EM,n54,d}$ | | +| | 1610 - 1650 MHz | $P_{EM,n54,c}$ | $P_{EM,n54,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 repeater 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 repeater unwanted emission level at the antenna connector, $G_{\text{ant}}$ equals the repeater 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.5.4.5.3 Co-location with base stations and *repeater type 1-C* Nodes + +These requirements may be applied for the protection of other BS, IAB-DU, IAB-MT and *repeater type 1-C* receivers when GSM900, DCS1800, PCS1900, GSM850, CDMA850, UTRA FDD, UTRA TDD, E-UTRA, NR BS, IAB-DU, IAB-MT, or *repeater type 1-C* are co-located with *repeater type 1-C*. + +The requirements assume a 30 dB coupling loss between transmitter and receiver and are based on co-location with same class. + +The *minimum requirements* are in table 6.5.4.5.3-1 for a *repeater type 1-C*. Requirements for co-location with a system listed in the first column apply, depending on the declared *repeater type 1-C* class. For a *multi-band connector*, the exclusions and conditions in the Note column of table 6.5.4.5.3-1 shall apply for each supported *operating band*. + +**Table 6.5.4.5.3-1: Repeater type 1-C spurious emissions minimum requirements for co-location with BS, IAB-Node or repeater-Node** + +| Type of co-located BS | Frequency range for co-location requirement | Minimum requirements | | | Measurement bandwidth | Note | +|-----------------------------------------------------|---------------------------------------------|----------------------|-------------|-------------|-----------------------|-------------------------------------------------------------------------------------| +| | | WA repeater | MR repeater | LA repeater | | | +| GSM900 | 876 – 915 MHz | -98 dBm | -91 dBm | -70 dBm | 100 kHz | | +| DCS1800 | 1710 – 1785 MHz | -98 dBm | -91 dBm | -80 dBm | 100 kHz | | +| PCS1900 | 1850 – 1910 MHz | -98 dBm | -91 dBm | -80 dBm | 100 kHz | | +| GSM850 or CDMA850 | 824 – 849 MHz | -98 dBm | -91 dBm | -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 repeater operating in Band n50, n75, 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 repeater operating in Band n50, n75, n92 or n94 | +| 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 repeater operating in Band n48, n77 or n78 | +| 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 | | +| E-UTRA Band 30 or NR Band n30 | 2305 – 2315 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| 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 | | +| 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 repeater operating in Band n34 | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| 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 repeater operating in Band n2 or band n25 | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 – 1930 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| 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 repeater operating in Band n38. | +| 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 repeater operating in Band n39 | +| 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 repeater operating in Band n30 or n40. | +| E-UTRA Band 41 or NR Band n41, n90 | 2496 – 2690 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n41, n53 or [n90] | + +| | | | | | | | +|-------------------------------|-------------------|---------|---------|---------|---------|-----------------------------------------------------------------------------------------------| +| E-UTRA Band 42 | 3400 – 3600 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n48, n77 or n78 | +| E-UTRA Band 43 | 3600 – 3800 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n48, n77 or n78 | +| E-UTRA Band 44 | 703 – 803 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n28 | +| E-UTRA Band 45 | 1447 – 1467 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 46 or NR Band n46 | 5150 – 5925 MHz | N/A | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n46 or n96 | +| E-UTRA Band 48 or NR Band n48 | 3550 – 3700 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n48, n77 or n78 | +| E-UTRA Band 50 or NR Band n50 | 1432 – 1517 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater 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 repeater operating in Band n50, n74, n75, n76, n91, n92, n93 or n94 | +| 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 repeater operating in Band n41, n53 or n90 | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n54 | +| 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 74 or NR Band n74 | 1427 – 1470 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater 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 repeater operating in Band n48, n77 or n78 | +| NR Band n78 | 3.3 – 3.8 GHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to repeater operating in Band n48, n77 or n78 | +| 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 | | +| 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 | | +| NR Band n102 | 5925 – 6425 MHz | N/A | -90 dBm | -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 | This requirement does not apply to repeater operating in Band n104. | +| 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 | | + +NOTE 1: As defined in the scope for spurious emissions in this clause, the co-location requirements in table 6.5.4.5.3-1 do not apply for the frequency range extending $\Delta f_{\text{OBUE}}$ immediately outside the transmit frequency range of a *repeater type 1-C*. 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 antenna to antenna minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [15]. + +NOTE 2: Table 6.5.4.5.3-1 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. + +### 6.5.5 Receiver spurious emissions + +#### 6.5.5.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 *antenna connector*. The requirements only apply to *repeater type 1-C* for TDD operation. + +For each *antenna connectors* on BS-side and UE-side supporting both RX and TX in TDD, the requirements apply during the *transmitter OFF state*. For *antenna connectors* both BS-side and UE-side in FDD, the RX spurious emissions requirements are superseded by the TX spurious emissions requirements, as specified in clause 6.5.4.5. + +For *multi-band connectors* that both transmit and receive in *operating band* supporting TDD, RX spurious emissions requirements are applicable during the *TX OFF state*, and are subject to exclusion zones in each supported *operating band*. + +For Band n41 and n90 operation in Japan, the sum of receiver spurious emissions requirements over all *antenna connectors* for *repeater type 1-C* shall not exceed *minimum requirements* defined in clause 6.5.5.5. + +#### 6.5.5.2 Minimum requirement + +The minimum requirements are in TS 38.106 [2], clause 6.5.5.2. + +#### 6.5.5.3 Test purpose + +The test purpose is to verify the ability of the repeater to limit the interference caused by receiver spurious emissions to other systems. + +#### 6.5.5.4 Method of test + +##### 6.5.5.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +##### 6.5.5.4.2 Procedure + +The minimum requirement is applied to all connectors under test, + +- 1) Connect the connector under test to measurement equipment as shown in annex D.9. +- 2) Ensure the transmitter is OFF. + +- 3) Set the measurement equipment parameters as specified in table 6.5.5.5-1. +- 4) Measure the spurious emissions over each frequency range described in table 6.5.5.5-1. + +In addition, for a *multi-band connector*, the following steps shall apply: + +- 5) For *multi-band connector* 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.5.5 Test requirements + +The receiver spurious emissions requirements for *repeater type 1-C* are that for each *antenna connector*, the power of emissions shall not exceed the value specified in table 6.5.5.5-1. + +**Table 6.5.5.5-1: Repeater type 1-C receiver spurious emissions limits** + +| Spurious frequency range | Basic limits | Measurement bandwidth | Note | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------------------|------------------------| +| 30 MHz – 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 | +| 12.75 GHz - 26 GHz | -47 dBm | 1 MHz | Note 1, Note 2 | +| NOTE 1: Measurement bandwidths as in ITU-R SM.329 [4], s4.1. | | | | +| NOTE 2: Upper frequency as in ITU-R SM.329 [4], s2.5 table 1. | | | | +| NOTE 3: 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 4: The frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of the repeater transmitter operating band to $\Delta f_{\text{OBUE}}$ above the highest frequency of the repeater transmitter operating band may be excluded from the requirement. $\Delta f_{\text{OBUE}}$ is defined in clause 6.5.1. For multi-band connectors , the exclusion applies for all supported operating bands. | | | | + +## 6.6 Repeater Error Vector Magnitude + +### 6.6.1 Downlink repeater error vector magnitude + +#### 6.6.1.1 General + +The Repeater Error Vector Magnitude (EVM) is a measure of the difference between the symbols provided at the input of repeater and the measured signal symbols at the output of the repeater after the equalization by the measurement equipment. This difference is called the error vector. Details about how the repeater EVM is determined are the same as specified in TS 38.104 Annex B for FR1. The repeater EVM result is defined as the square root of the ratio of the mean error vector power to the mean reference power expressed in percent. The accuracy of the input symbols is counted in the measurement uncertainty. + +The repeater EVM requirement is applicable for a repeater operating at an input power in the range from what is required to reach the maximum output power to the minimum power level in table 6.6.1.1-1. + +**Table 6.6.1.1-1: Minimum input power for repeater EVM** + +| Repeater DL class | Minimum input power spectral density (dBm/MHz) | | +|-------------------------------------------------------|------------------------------------------------|---------------------| +| | QPSK, 16 QAM, 64QAM | 256QAM 1 | +| WA | -82 | -75 | +| MR | -77 | -70 | +| LA | -74 | -67 | +| Note 1: support of 256QAM is based on the declaration | | | + +#### 6.6.1.2 Minimum requirements + +The minimum requirement is in TS 38.106 [2] clause 6.6.1.2. + +#### 6.6.1.3 Test purpose + +To verify that the downlink repeater EVM deterioration is within the limit specified by the minimum requirements after the signal passed through the Repeater. + +#### 6.6.1.4 Method of test + +##### 6.6.1.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.9.1. + +RF bandwidth positions to be tested for multi-carrier and/or CA: + +- 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. + +##### 6.6.1.4.2 Procedure + +The minimum requirement is applied to all *antenna connectors*, they may be tested one at a time or multiple *antenna connectors* may be tested in parallel as shown in annex D.1.1 for *repeater type 1-C*. Whichever method is used the procedure is repeated until all *antenna connectors* necessary to demonstrate conformance have been tested. + +- 1) For an *antenna connector* declared to be capable of single carrier operation only (D.16), set the *antenna connector* under test to transmit a signal according to the applicable test configuration in clause 4.8 using the corresponding test models: + - RDL-FR1-TM3.1a if 256QAM is supported by repeater without power back off, or + - RDL-FR1-TM3.1a at manufacturer's declared rated output power if 256QAM is supported by repeater with power back off, and RDL-FR1-TM3.1 at maximum power, or + - RDL-FR1-TM3.1 if highest modulation order supported by repeater is 64QAM, or + - RDL-FR1-TM3.2 if highest modulation order supported by repeater is 16QAM, or + - RDL-FR1-TM3.3 if highest modulation order supported by repeater is QPSK. + +For an *antenna connector* declared to be capable of multi-carrier operation (D.15-D.16), set the *antenna connector* under test to transmit according to the applicable test configuration and corresponding power setting specified in clauses 4.7 and 4.8 using the corresponding test models on all carriers configured: + +- +- RDL-FR1-TM3.1a if 256QAM is supported by repeater without power back off, or +- RDL-FR1-TM3.1a at manufacturer's declared rated output power if 256QAM is supported by repeater with power back off, and RDL-FR1-TM3.1 at maximum power, or +- RDL-FR1-TM3.1 if highest modulation order supported by repeater is 64QAM, or +- RDL-FR1-TM3.2 if highest modulation order supported by repeater is 16QAM, or +- RDL-FR1-TM3.3 if highest modulation order supported by repeater is QPSK. + +For RDL-FR1-TM3.1a, power back-off shall be applied if it is declared. + +- 2) Measure the repeater EVM and frequency error as defined in annex H. + +- 3) Repeat steps 1 and 2 for RDL-FR1-TM2 if 256QAM is not supported by repeater or for RDL-FR1-TM2a if 256QAM is supported by repeater . For RDL-FR1-TM2 and RDL-FR1-TM2a, the OFDM symbol TX power (OSTP) shall be at the lower limit of the dynamic range according to the test procedure in clause 6.3.3.4 and test requirements in clause 6.3.3.5. + +In addition, for *multi-band connector(s)*, the following steps shall apply: + +- 4) For *multi-band 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.1.5 Test requirement + +The downlink of the Repeater EVM levels for different modulation schemes shall not exceed values in table 6.6.1.5-1. + +**Table 6.6.1.5-1: Repeater EVM test requirements** + +| Parameter | Required test repeater EVM | +|--------------------------------------------------------|----------------------------| +| QPSK, 16QAM, 64QAM | [9.25 %] | +| 256QAM | [4.75 %] 1 | +| Note 1: support of 256QAM is based on the declaration. | | + +### 6.6.2 Uplink repeater error vector magnitude + +#### 6.6.2.1 General + +The Repeater Error Vector Magnitude is a measure of the difference between the reference waveform provided at the input of the repeater and the measured waveform at the output of the repeater. This difference is called the error vector. Details about how the repeater EVM is determined are the same as specified in TS 38.101-1[9] Annex F. Before calculating the repeater EVM the measured waveform is corrected by the sample timing offset and RF frequency offset. Then the carrier leakage shall be removed from the measured waveform before calculating the repeater EVM. + +The measured waveform is further equalised using the channel estimates subjected to the repeater EVM equaliser spectrum flatness requirement specified in TS 38.101-1[9] clause 6.4.2.4. For DFT-s-OFDM waveforms, the repeater EVM result is defined after the front-end FFT and IDFT as the square root of the ratio of the mean error vector power to the mean reference power expressed as a %. For CP-OFDM waveforms, the repeater EVM result is defined after the front-end FFT as the square root of the ratio of the mean error vector power to the mean reference power expressed as a %. The accuracy of the input waveform is counted in the measurement uncertainty. + +The basic repeater EVM measurement interval in one slot in the time domain. The repeater EVM measurement interval is reduced by any symbols that contains an allowable power transient in the measurement interval, as defined in TS 38.101-1 [9] clause 6.3.3 for EVM for UE. + +The repeater EVM requirement is applicable for a repeater operating at an input power in the range from what is required to reach the maximum output power to the minimum power level in table 6.6.2.1-1. + +**Table 6.6.2.1-1: Minimum input power for repeater EVM** + +| Repeater UL class | Minimum input power spectral density (dBm/MHz) | | +|-------------------------------------------------------|------------------------------------------------|---------------------| +| | QPSK, 16 QAM, 64QAM | 256QAM 1 | +| WA | -82 | -75 | +| LA | -74 | -67 | +| Note 1: support of 256QAM is based on the declaration | | | + +#### 6.6.2.2 Minimum requirement + +The minimum requirement is in TS 38.106 [9] clause 6.6.2.2. + +#### 6.6.2.3 Test purpose + +To verify that the uplink repeater EVM deterioration is within the limit specified by the minimum requirements after the signal passed through the Repeater. + +#### 6.6.2.3 Method of test + +##### 6.6.2.3.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.9.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.9.1; +- $B_{\text{RFBW\_T}}$ and $B'_{\text{RFBW\_T}}$ in multi-band operation, see clause 4.9.1. + +##### 6.6.2.3.2 Procedure + +For repeater, the minimum requirement is applied to all *antenna connectors*, they may be tested one at a time or multiple *antenna connectors* may be tested in parallel as shown in annex D.1.1 for *repeater type 1-C*. Whichever method is used the procedure is repeated until all *antenna connectors* necessary to demonstrate conformance have been tested. + +- 1) For an *antenna connector* declared to be capable of single carrier operation only (D.16), set the *antenna connector* under test to transmit a signal according to the applicable test configuration in clause 4.8 using the corresponding test models: + - RUL-TM3.1a if 256QAM is supported by repeater without power back off, or + - RUL-FR1-TM3.1a at manufacturer's declared rated output power if 256QAM is supported by repeater with power back off, and RUL-FR1-TM3.1 at maximum power, or + - RUL-FR1-TM3.1 with highest modulation order supported by repeater. + +For an *antenna connector* declared to be capable of multi-carrier operation (D.15-D.16), set the *antenna connector* under test to transmit according to the applicable test configuration and corresponding power setting specified in clauses 4.7 and 4.8 using the corresponding test models on all carriers configured: + +- RUL-FR1-TM3.1a if 256QAM is supported by repeater without power back off, or +- RUL-FR1-TM3.1a at manufacturer's declared rated output power if 256QAM is supported by repeater with power back off, and RUL-FR1-TM3.1 at maximum power, or +- RUL-FR1-TM3.1 with highest modulation order supported by repeater. + +For RUL-FR1-TM3.1a, power back-off shall be applied if it is declared. + +- 2) Measure the repeater EVM and frequency error as defined in annex H. +- 3) Repeat steps 1 and 2 for RUL-FR1-TM2 if 256QAM is not supported by repeater or for RUL-FR1-TM2a if 256QAM is supported by repeater. For RUL-FR1-TM2 and RUL-FR1-TM2a the OFDM symbol TX power (OSTP) shall be at the lower limit of the dynamic range according to the test procedure in clause 6.3.3.4 and test requirements in clause 6.3.3.5. + +In addition, for *multi-band connector(s)*, the following steps shall apply: + +- 4) For *multi-band 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 Test requirement + +The uplink of the Repeater EVM levels for different modulation schemes shall not exceed values in table 6.6.2.4-1. + +**Table 6.6.2.4-1: Repeater EVM test requirements** + +| Parameter | Required test repeater EVM | +|--------------------------------------------------------|----------------------------| +| QPSK, 16QAM, 64QAM | [9.25 %] | +| 256QAM | [4.75 %] 1 | +| Note 1: support of 256QAM is based on the declaration. | | + +## 6.7 Input intermodulation + +### 6.7.1 Definition and applicability + +#### 6.7.1.1 General + +The input intermodulation is a measure of the capability of the Repeater to inhibit the generation of interference in the passband, in the presence of interfering signals on frequencies other than the passband. + +Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the Repeater to maintain the wanted frequency free of internally created interference. + +The measurements shall apply to both uplink and downlink paths of the Repeater, during the *transmitter ON state* at maximum gain. + +#### 6.7.1.2 Minimum requirements + +The minimum requirement is in TS 38.106 [2] clauses 6.7.1.2, 6.7.2.2 and 6.7.3.2. + +#### 6.7.1.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. + +#### 6.7.1.4 Method of test + +##### 6.7.1.4.1 Initial conditions + +Test environment: normal; see Annex A.2 + +A measurement system set-up is shown in Annex D. + +- 1) Set the Repeater to maximum gain. +- 2) Connect two signal generators with a combining circuit or one signal generator with the ability to generate several CW carriers to the input. +- 3) Connect a spectrum analyser to the output of the Repeater. + +##### 6.7.1.4.2 Procedure + +- 1) Adjust the frequency of the input signals, either below or above the passband, so that one carrier, $f_1$ , is 1 MHz outside the channel edge frequency of the first or last channel in the passband, and the lowest order intermodulation product from the two carriers is positioned in the centre of the passband. +- 2) Measure the increase in output power in the passband when the interferer is applied. + +3) Repeat the measurement for the opposite path of the Repeater. + +#### 6.7.1.5 Test requirements + +##### 6.7.1.5.1 General requirement + +The intermodulation performance should be met when the following signals are applied to the NR Repeater: + +**Table 6.7.1.5.1-1: Input intermodulation requirement** + +| $f_1$ offset | Interfering Signal Levels | Type of signals | Measurement bandwidth | +|--------------|---------------------------|-----------------|-----------------------| +| 1,0 MHz | -40 dBm | 2 CW carriers | 1 MHz | + +$f_1$ offset is the offset from the channel edge frequency of the first or last channel in the passband of the closer carrier. + +For the parameters specified in Table 6.7.1.5.1-1, the power in the pass band shall not increase by more than [10+TT] 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. + +##### 6.7.1.5.2 Co-location with BS/Repeater in other systems + +This additional input intermodulation requirement may be applied for the protection of NR repeater receivers when GSM, CDMA, UTRA, E-UTRA, NR BS or repeater operating in a different frequency band are co-located with a NR repeater. + +The following requirement applies for interfering signals depending on the repeaters *passband*. + +This requirement applies to the uplink and downlink of the repeater. If the BS side is declared to meet co-location requirements, then it should meet input intermodulation co-location requirements for the downlink. If the UE side is declared to meet co-location requirements, then it should meet input intermodulation co-location requirements for the uplink. + +**Table 6.7.1.5.2-1: input intermodulation requirement for NR repeater DL when co-located with BS/repeater in other frequency bands.** + +| Frequency range of interfering signal | Interfering signal mean power for repeater with WA UE side (dBm) | Interfering signal mean power for repeater with MR UE side(dBm) | Interfering signal mean power for repeater with LA UE side(dBm) | Type of interfering signals | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|-----------------------------------------------------------------|-----------------------------------------------------------------|-----------------------------| +| Frequency range of co-located BS's downlink operating band or located repeater's passband | +16 | +8 | x (Note 1) | 2 CW carriers | +| NOTE 1: x = -7 dBm for NR repeater co-located with Pico GSM850 or Pico CDMA850
x = -4 dBm for NR repeater co-located with Pico DCS1800 or Pico PCS1900
x = -6 dBm for NR repeater co-located with UTRA bands or E-UTRA bands or NR bands
NOTE 2: The requirement does not apply when the interfering signal falls within the passband .
NOTE 3: For unsynchronized base stations or repeaters (except in band n46 and n96), special co-location requirements may apply that are not covered by the 3GPP specifications. | | | | | + +**Table 6.7.1.5.2-2: input intermodulation requirement for NR repeater UL when co-located with BS/repeater in other frequency bands.** + +| Frequency range of interfering signal | Interfering signal mean power for repeater with WA BS side(dBm) | Interfering signal mean power for repeater with LA BS side(dBm) | Type of interfering signals | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|-----------------------------------------------------------------|-----------------------------| +| Frequency range of co-located BS's downlink operating band or located repeater's passband | +16 | $P_{\text{rated,p,AC}} - 30$ | 2 CW carriers | +| NOTE 1: The requirement does not apply when the interfering signal falls within the passband . | | | | +| NOTE 2: For unsynchronized base stations or repeaters (except in band n46 and n96), special co-location requirements may apply that are not covered by the 3GPP specifications. | | | | + +NOTE 1: The co-location requirements in Table 6.7.1.5.2-1 and 6.7.1.5.2-2 do not apply when the Repeaters passband frequency range is adjacent to the frequency range of the co-location requirement in the Table 6.7.1.5.2-1 or Table 6.7.1.5.2-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 [15]. + +NOTE 2: The Table 6.7.1.5.2-1 and Table 6.7.1.5.2-2 assumes that two operating bands, where the corresponding BS or Repeater 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. + +For the parameters specified in table Table 6.7.1.5.2-1 and 6.7.1.5.2-2, the power in the passband shall not increase with more than $[10 + TT]$ dB B at the output of the repeater as measured in the centre of the passband, compared to the level obtained without interfering signals applied. + +##### 6.7.1.5.3 Co-existence with other systems + +This input intermodulation existence requirement may be applied for the protection of NR repeater receivers when GSM, CDMA, UTRA, E-UTRA, NR BS or repeater operating in another frequency band co-exist with a NR repeater. + +The intermodulation performance should be met when the signals in Table 6.7.1.5.3-1 are applied to the Repeater: + +**Table 6.7.1.5.3-1: input intermodulation requirement for NR repeater when co-exist with BS/repeater in other non-overlapping frequency bands** + +| Frequency range of interfering signal | Interfering signal mean power (dBm) | Type of interfering signals | Measurement bandwidth | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|-----------------------------|-----------------------| +| Frequency range of co-existence system operating band | -15 | 2 CW carriers | 1MHz | +| NOTE 1: All the interfering signals should be limited into the frequency ranges that are either X MHz higher than $F_{\text{UL,high}}$ or X MHz lower than $F_{\text{UL,low}}$ , where X equals to 20MHz when $F_{\text{UL,high}} - F_{\text{UL,low}}$ is not larger than 200MHz, otherwise X equals to 60MHz | | | | + +NOTE 1: The co-existence requirements in Table 6.7.1.5.3-1 do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-existence requirement in the Table 6.7.1.5.3-1. The current state-of-the-art technology does not allow a single generic solution for co-existence. + +NOTE 2: The Table 6.7.1.5.3-1 assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. + +For the parameters specified in Table 6.7.1.5.3-1, the power in the pass band shall not increase with more than $[10 + \text{TT}]$ 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. + +## 6.8 Output intermodulation + +### 6.8.1 Definition and applicability + +#### 6.8.1.1 General + +The output intermodulation requirement is a measure of the capability of the repeater to inhibit the generation of signals in its non-linear elements caused by presence of the wanted signal and an interfering signal reaching the repeater via the output port. The requirement shall apply during the *transmitter ON state* and the *transmitter transient period*. + +The requirement shall apply to the uplink and downlink of the Repeater. + +For *repeater type I-C*, the output intermodulation level is the power of the intermodulation products when an interfering signal is injected into the *antenna connector*. + +#### 6.8.1.2 Minimum requirements + +The minimum requirement is in TS 38.106 [2] clause 6.8.2. + +#### 6.8.1.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. + +#### 6.8.1.4 Method of test + +##### 6.8.1.4.1 Initial conditions + +Test environment: normal; see Annex A.2 + +A measurement system set-up is shown in Annex D. + +- 1) Connect a signal generator to the input port of the Repeater (wanted signal). Connect a signal generator to the output port (interfering signal) and make sure the signal generator power is directed to the repeater output port. +- 2) Detection mode: True RMS. + +##### 6.8.1.4.2 Procedure + +- 1) Set the Repeater to maximum gain. +- 2) Set the signal generator at the repeater input port (wanted signal) to generate a signal in accordance to test model R-FR1-TM1.1, with a bandwidth as defined in Table 6.8.1.5.1-1, at the level which produce the manufacturer specified maximum output power at maximum gain. +- 3) Set the signal generator at the repeater output port (interference signal) to generate a signal in accordance to test model R-FR1-TM1.1, with a bandwidth, level and frequency offset as defined in Table 6.8.1.5.1-1. +- 4) Measure the emission at the specified frequencies with specified measurement bandwidth as described in the test requirements 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 the test from step 3 on until all interfering signal centre frequency offsets in Table 6.8.1.5.1-1 has been tested, but exclude interfering signal frequencies that are outside of the allocated frequency band for NR downlink. +- 6) For repeater supporting Band n41 and n90 operation in Japan, repeat the test using wanted and interfering signal parameters as defined in Table 6.8.1.5.2-1. + +NOTE: 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.8.1.5 Test requirements + +##### 6.8.1.5.1 General requirements + +Test requirement shall be met using interfering and wanted signal parameters according to Table 6.8.1.5.1-1 + +**Table 6.8.1.5.1-1: Interfering and wanted signals for the output intermodulation requirement** + +| Parameter | Value | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal type | NR signal, filling all supported passbands in the operating band and with sufficient carriers to fill each passband . Minimum defined SCS for the operating band | +| Interfering signal type | NR signal, with the minimum SCS and channel bandwidth defined in the operating band in [2] | +| Interfering signal level | Rated total output power ( $P_{\text{rated,t,AC}}$ ) in the passband – 30 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 | $f_{\text{offset}} = \pm \text{minimum pass band} \left( n - \frac{1}{2} \right)$
, for n=1, 2 and 3 | +| NOTE 1: Interfering signal positions that are partially or completely outside of any downlink operating band of the repeater 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 38.115-1 [7] provides further guidance regarding appropriate test requirements. | | +| NOTE 2: In Japan, NOTE 1 is not applied in Band n77, n78, n79. | | + +In all measurements, the requirements according to either clause [6.5.3] Operating band unwanted emission (Category A) and the downlink requirements of [6.5.4] Spurious emission (Category A) or [6.5.3] Operating band unwanted emissions (Category B) and the downlink requirements of [6.5.4] Spurious emission (Category B) shall be fulfilled. + +##### 6.8.1.5.2 Additional requirements + +For repeater supporting Band n41 and n90 operation in Japan, the sum of output intermodulation level over all *antenna connectors* shall not exceed the unwanted emission limits in clauses 6.5 in the presence of an NR interfering signal according to table 6.8.1.5.2-1. + +**Table 6.8.1.5.2-1: Interfering and wanted signals for the additional output intermodulation requirement for Band n41 and n90** + +| Parameter | Value | +|-----------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------| +| Wanted signal | NR signal (NOTE) | +| Interfering signal type | NR signal of 10 MHz passband bandwidth | +| Interfering signal level | Rated total output power (Prated,t,AC) in the passband – 30 dB | +| Interfering signal centre frequency offset from the lower/upper passband centre frequency of the wanted signal | ± 5 MHz
± 15 MHz
± 25 MHz | +| NOTE: | This requirement applies for passband allocated within 2545-2645 MHz. | + +## 6.9 Adjacent Channel Rejection Ratio (ACRR) + +### 6.9.1 Definitions and applicability + +Adjacent Channel Rejection Ratio (ACRR) is the ratio of the average gain over a carrier of the repeater in the *passband* to the average gain of the repeater over an adjacent channel outside the repeater *passband*. The carrier in the *passband* and in the adjacent channel shall be of the same type (reference carrier) with bandwidths as defined by *nominal channel bandwidth*. In case of Local Area repeater above 2496 MHz, the channel within the *passband* and the adjacent channel are assumed to have a bandwidth of 10 MHz + +The requirement is differentiated between uplink and downlink. + +The requirement shall apply during the *transmitter ON state*. + +### 6.9.2 Co-existence with UTRA, E-UTRA and NR + +This requirement shall be applied for the protection of UTRA, E-UTRA and NR signals in geographic areas in which NR Repeater, NR BS, E-UTRA BS and UTRA BS are deployed so that they serve adjacent channels. The reference carrier is a NR carrier. + +#### 6.9.2.1 Minimum requirements + +The minimum requirement is in TS 38.106 [2] sub-clause 6.9.2. + +#### 6.9.2.2 Test purpose + +To verify that the Repeater ACRR requirement is met as specified in sub-clause 6.9.2.1. + +#### 6.9.2.3 Method of test + +##### 6.9.2.3.1 Initial conditions + +Test environment: normal; see Annex A2. [RF channels to be updated] + +RF channels to be tested for single carrier: B, T; see clause 4.9.1. + +*Repeater RF Bandwidth* positions to be tested for multi-carrier: + +- BRFBW 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. + +##### 6.9.2.3.2 Procedure + +- 1) Set the signal generator to transmit a signal modulated with test model XX for downlink and test model XX for uplink as defined in section 4.9 at the first or last channel with channel offset from frequency range of *passband* defined in section 6.9.2.3.3 within the *pass band*. + +- 2) Adjust the input power to the Repeater to create the maximum nominal Repeater output power at maximum gain +- 3) Measure the RRC filtered mean power at the RF output port over a certain slot. +- 4) Set the signal generator to transmit the same signal and the same input power at one of the channel offsets outside the repeater pass band according to Tables in section 6.9.2.3.3. +- 5) Measure the 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 Tables in section 6.9.2.3.3 are measured. + +### 6.9.2.3.3 Test Requirements + +For a repeater operating at *passband* below 2496 MHz, the ACRR requirements in table 6.9.2.3.3-1 shall apply in downlink. In normal conditions the ACRR for downlink shall be higher than the value specified in the Table 6.9.2.3.3-1. + +**Table 6.9.2.3.3-1: Repeater Downlink ACRR below 2496MHz** + +| Co-existence with other systems | Repeater Class | Channel offset from frequency edge of passband (MHz) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACRR limit | +|---------------------------------|-----------------------|-------------------------------------------------------------|-----------------------------------------------------------------------------|-----------------| +| UTRA, E-UTRA, NR | Wide Area repeater | $BW_{Nominal}/2$ | Square ( $BW_{Config}$ ) | 44.3dB | +| | Medium Range repeater | $BW_{Nominal}/2$ | Square ( $BW_{Config}$ ) | 44.3dB | +| | Local Area repeater | $BW_{Nominal}/2$ | Square ( $BW_{Config}$ ) | 32.3dB (Note 1) | + +NOTE 1: This requirement does not applicable if the *passband* occupies the entire *operating band*. +NOTE 2: $BW_{Nominal}$ is the *nominal channel bandwidth*. $BW_{Config}$ is the *transmission bandwidth configuration* assumed for the adjacent channel. +NOTE 3: With SCS that provides largest *transmission bandwidth configuration* ( $BW_{Config}$ ). + +For a repeater operating at *passband* above 2496 MHz, the ACRR requirements in table 6.9.2.3.3-1a shall apply in downlink. In normal conditions the ACRR for downlink shall be higher than the value specified in the Table 6.9.2.3.3-1a. + +**Table 6.9.2.3.3-1a: Repeater Downlink ACRR above 2496 MHz** + +| Co-existence with other systems | Repeater Class | Channel offset from frequency edge of passband (MHz) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACRR limit | +|---------------------------------|-----------------------|-------------------------------------------------------------|-----------------------------------------------------------------------------|-----------------| +| UTRA, E-UTRA, NR | Wide Area repeater | $BW_{Nominal}/2$ | Square ( $BW_{Config}$ ) | 32.3dB | +| | Medium Range repeater | $BW_{Nominal}/2$ | Square ( $BW_{Config}$ ) | 32.3dB | +| | Local Area repeater | $BW_{Nominal}/2$ | Square ( $BW_{Config}$ ) | 32.3dB (Note 1) | + +NOTE 1: This requirement does not applicable if the *passband* occupies the entire *operating band*. +NOTE 2: $BW_{Nominal}$ is the *nominal channel bandwidth*. $BW_{Config}$ is the *transmission bandwidth configuration* assumed for the adjacent channel. +NOTE 3: With SCS that provides largest *transmission bandwidth configuration* ( $BW_{Config}$ ). + +For a repeater operating at *passband* below 2496 MHz, the ACRR requirements in table 6.9.2.3.3-2 shall apply in uplink. In normal conditions the ACRR for uplink shall be higher than the value specified in the Table 6.9.2.3.3-2. + +Table 6.9.2.3.3-2: Repeater Uplink ACRR below 2496 MHz + +| Co-existence with other systems | Repeater Class | Channel offset from frequency edge of passband (MHz) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACRR limit | +|---------------------------------|---------------------|-------------------------------------------------------------|-----------------------------------------------------------------------------|-----------------| +| UTRA, E-UTRA, NR | Wide Area repeater | BW Nominal /2 | Square (BW Config ) | 32.3dB | +| | Local Area repeater | BW Nominal /2 | Square (BW Config ) | 32.3dB (Note 1) | + +NOTE 1: This requirement does not applicable if the *passband* occupies the entire *operating band*. +NOTE 2: BWNominal is the *nominal channel bandwidth*. BWConfig is the *transmission bandwidth configuration* assumed for the adjacent channel. +NOTE 3: With SCS that provides largest *transmission bandwidth configuration* (BWConfig). + +For a repeater operating at *passband* above 2496 MHz, the ACRR requirements in table 6.9.2.3.3-2a shall apply in uplink. In normal conditions the ACRR for uplink shall be higher than the value specified in the Table 6.9.2.3.3-2a. + +Table 6.9.2.3.3-2a: Repeater Uplink ACRR above 2496 MHz + +| Co-existence with other systems | Repeater Class | Channel offset from frequency edge of passband (MHz) | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACRR limit | +|---------------------------------|---------------------|-------------------------------------------------------------|-----------------------------------------------------------------------------|-------------------------| +| UTRA, E-UTRA, NR | Wide Area repeater | BW Nominal /2 | Square (BW Config ) | 32.3dB | +| | Local Area repeater | 5MHz | 9 MHz | 19.3dB (Note 1, Note 2) | +| | | BW Nominal /2 | Square (BW Config ) | 32.3dB (Note 1) | + +NOTE 1: This requirement does not applicable if the *passband* occupies the entire *operating band*. +NOTE 2: In this case, the channel within the *passband* and the adjacent channel are assumed to have a bandwidth of 10 MHz +NOTE 3: BWNominal is the *nominal channel bandwidth*. BWConfig is the *transmission bandwidth configuration* assumed for the adjacent channel. +NOTE 4: With SCS that provides largest *transmission bandwidth configuration* (BWConfig). + +## 6.10 Transmit ON/OFF power + +### 6.10.1 Transmitter OFF power + +#### 6.10.1.1 Definition and applicability + +Transmit OFF power requirements apply only to TDD operation of the repeater. The requirement applies to both downlink and uplink of the repeater. + +Transmitter OFF power is defined as the mean power measured over 70/N us filtered with a square filter of bandwidth equal to the *passband bandwidth* of the repeater (BWpassband) centred on the assigned channel frequency during the *transmitter OFF state*. N = SCS/15, where SCS is Sub Carrier Spacing in kHz of the input signal. + +For *multi-band connectors* and for *single band connectors* supporting transmission in multiple *operating bands*, the requirement is only applicable during the *transmitter OFF state* in all supported *operating bands*. + +#### 6.10.1.2 Minimum requirement + +The minimum requirement for *repeater type 1-C* is in TS 38.106 [2], clause 6.10.1.2. + +#### 6.10.1.3 Test purpose + +The purpose of this test is to verify the transmitter OFF power is within the limits of the minimum requirements. + +### 6.10.1.4 Method of test + +Requirement is tested together with transmitter transient period, as described in clause 6.10.2.4. + +### 6.10.1.5 Test requirements + +The conformance testing of transmit OFF power is included in the conformance testing of transmitter transient period; therefore, see clause 6.10.2.5 for test requirements. + +## 6.10.2 Transmitter transient period + +### 6.10.2.1 Definition and applicability + +*Transmitter transient period* requirements apply only to TDD operation of the repeater. The requirement applies to both downlink and uplink of the repeater. + +The *transmitter transient state* is the time period during which the transmitter is changing from the *transmitter OFF state* to the *transmitter ON period* or vice versa. The *transmitter transient period* is illustrated in figure 6.10.2.1-1. + +![Figure 6.10.2.1-1: Example of relations between transmitter ON state, transmitter OFF state 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 horizontal dashed lines: 'ON power level' and 'OFF power level'. The x-axis is divided into three main regions: 'UL/DL transmission' (left), 'Transmitter ON state (DL/UL transmission)' (middle), and 'GP or UL/DL transmission' (right). The 'ON power level' region is a solid horizontal line. The 'OFF power level' region is a hatched area below the 'ON power level' line. The 'Transmitter transient period' is indicated by two double-headed arrows: one at the start of the 'ON state' and one at the end of the 'ON state'. The 'Transmit OFF state' is indicated by two double-headed arrows: one at the beginning of the 'UL/DL transmission' region and one at the end of the 'GP or UL/DL transmission' region.](a9d7ac06dfdc2152f9b2fcf977a9ba6f_img.jpg) + +Figure 6.10.2.1-1: Example of relations between transmitter ON state, transmitter OFF state 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 horizontal dashed lines: 'ON power level' and 'OFF power level'. The x-axis is divided into three main regions: 'UL/DL transmission' (left), 'Transmitter ON state (DL/UL transmission)' (middle), and 'GP or UL/DL transmission' (right). The 'ON power level' region is a solid horizontal line. The 'OFF power level' region is a hatched area below the 'ON power level' line. The 'Transmitter transient period' is indicated by two double-headed arrows: one at the start of the 'ON state' and one at the end of the 'ON state'. The 'Transmit OFF state' is indicated by two double-headed arrows: one at the beginning of the 'UL/DL transmission' region and one at the end of the 'GP or UL/DL transmission' region. + +**Figure 6.10.2.1-1: Example of relations between transmitter ON state, transmitter OFF state and transmitter transient period** + +For *repeater type 1-C* this requirement shall be applied at the *antenna connector* supporting transmission in the *operating band*. + +For a repeater that is not declared to be a long delay repeater (D.15), the beginning and end point of downlink and uplink bursts are referenced to the slot timing at the input. + +For a repeater that is declared to be a long delay repeater (D.15), the beginning and end point of downlink and uplink bursts are referenced to the slot timing at the input plus the declared repeater delay. + +### 6.10.2.2 Minimum requirement + +The minimum requirement for *repeater type 1-C* is in TS 38.106 [2], clause 6.10.2.2. + +### 6.10.2.3 Test purpose + +The purpose of this test is to verify the transmitter transient periods are within the limits of the minimum requirements. + +#### 6.10.2.4 Method of test + +##### 6.10.2.4.1 Initial conditions + +Test environment: + +- normal; see annex B.2. + +RF channels to be tested for single carrier: + +- M; see clause 4.9.1. + +##### 6.10.2.4.2 Procedure + +The minimum requirement is applied to all *antenna connectors*, they may be tested one at a time or multiple *antenna connectors* may be tested in parallel as shown in annex D.1.1. Whichever method is used the procedure is repeated until all *antenna connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect *antenna connector* for input and output signals to measurement equipment as shown in annex D.1.1. All *antenna 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) Set the input signal to the representative connectors under test according to the applicable test configuration in clause 4.8 using the corresponding test models in clause 4.9.2 at the input power intended to produce the maximum rated output power, $P_{\text{rated,in, AC}} + 10\text{dB}$ . +- 3) 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 state + $10 \mu\text{s}$ to $35/N \mu\text{s}$ before start of next transmitter ON state – $10 \mu\text{s}$ . $N = \text{SCS}/15$ , where SCS is Sub Carrier Spacing in kHz. + +In addition, for *multi-band connector(s)*, the following steps shall apply: + +- 4) For *multi-band 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.10.2.5 Test requirements + +For *repeater type 1-C downlink*, the requirements for transmitter OFF power spectral density shall be less than -83 dBm/MHz per *antenna connector* for carrier frequency $f \leq 3.0 \text{ GHz}$ . + +For *repeater type 1-C downlink*, the requirements for transmitter OFF power spectral density shall be less than -82.5 dBm/MHz per *antenna connector* for carrier frequency $3.0 \text{ GHz} < f \leq 6.0 \text{ GHz}$ . + +For *repeater type 1-C uplink*, the requirements for transmitter OFF power spectral density shall be less than $-48\text{dBm} / (\text{SCS} * (12 * N_{\text{RB}} + 1) / 1000) \text{ MHz}$ per *antenna connector*, where SCS is Sub Carrier Spacing in kHz for carrier frequency $f \leq 3.0 \text{ GHz}$ . + +For *repeater type 1-C uplink*, the requirements for transmitter OFF power spectral density shall be less than $-47.5\text{dBm} / (\text{SCS} * (12 * N_{\text{RB}} + 1) / 1000) \text{ MHz}$ per *antenna connector*, where SCS is Sub Carrier Spacing in kHz for carrier frequency $3.0 \text{ GHz} < f \leq 6.0 \text{ GHz}$ . + +For *multi-band connector*, the requirement is only applicable during the transmitter OFF state in all supported operating bands. + +--- + +## Annex A (normative): Repeater stimulus signals + +--- + +### A.1 Repeater stimulus signal 1 + +This repeater stimulus signal shall be used for the following tests: + +- Uplink maximum output power +- Uplink operating band unwanted emissions +- Uplink spurious emissions + +Two uplink fixed reference channels for performance requirements (16QAM $\frac{3}{4}$ ) for FDD according to the TS38.141-1 [7], [A.4 table A.4-1, channel reference AX-X of 5] MHz bandwidth generated on separate centre frequencies with equal power and combined with a time difference of 266,7 us (4 OFDM symbols) + +The PUSCH data payload shall contain only zeroes (0000 0000). + +Each reference channel shall be subjected to time windowing and filtering so that it fulfils the spectral purity requirements defined in A.3. + +--- + +### A.2 Repeater stimulus signal 2 + +This repeater stimulus signal shall be used for the following tests: + +- Downlink operating band unwanted emissions +- Downlink spurious emissions + +Two NR-FR1-TM1.1 channels according to the TS38.141-1 [7] of 5 MHz bandwidth generated on separate centre frequencies with equal power and combined with a time difference of [1400 us (21 OFDM symbols)]. + +Each NR-FR1-TM1.1 channel shall be subjected to time windowing and filtering so that it fulfils the spectral purity requirements defined in A.3. + +--- + +### A.3 Repeater stimulus signal spectral purity requirements + +The reference channels or test models constituting the repeater stimulus signal shall fulfil the spectral purity requirements defined in table A.3-1 and A.3-2, where: + +- the minimum spectral density suppression is related to the reference spectral density. + +**Table A.3-1: Repeater stimulus signal spectral purity requirements for nominal channel bandwidth of passband $\leq 20\text{MHz}$** + +| Center frequency of measurement filter | Minimum requirements | Measurement filter type and filter bandwidth | Integration bandwidth | +|-------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------------------------------|-----------------------| +| 50.0 kHz outside from channel edge | 46.8 dBc (Note 1) | Square (100 kHz) | 100 kHz | +| Center of adjacent channel frequency with same nominal channel BW | 46.8 dBc (Note 2) | Square (nominal channel BW) | Nominal channel BW | +| NOTE 1: the reference spectral density shall be taken at the carrier center frequency with an integration bandwidth of 100 kHz. | | | | +| NOTE 2: the reference spectral density shall be taken at the carrier center frequency with an integration bandwidth of nominal carrier BW | | | | + +**Table A.3-2: Repeater stimulus signal spectral purity requirements for nominal channel bandwidth of passband $> 20\text{MHz}$** + +| Center frequency of measurement filter | Minimum requirements | Measurement filter type and filter bandwidth | Integration bandwidth | +|-------------------------------------------------------------------------------------------------------------------------------------------|----------------------|----------------------------------------------|-----------------------| +| 50.0 kHz outside from channel edge | 47.2 dBc (Note 1) | Square (100 kHz) | 100 kHz | +| Center of adjacent channel frequency with same nominal channel BW | 47.2 dBc (Note 2) | Square (nominal channel BW) | Nominal channel BW | +| NOTE 1: the reference spectral density shall be taken at the carrier center frequency with an integration bandwidth of 100 kHz. | | | | +| NOTE 2: the reference spectral density shall be taken at the carrier center frequency with an integration bandwidth of nominal carrier BW | | | | + +--- + +## Annex B (normative): Environmental requirements for the repeater + +--- + +### B.1 General + +For each test in the present document, the environmental conditions under which the repeater is to be tested are defined. + +--- + +### 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. + +NOTE: This may, for instance, be the case for measurements of radiated emissions performed on an open field test site. + +## 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 60 721-3-3 [16]; +- 2) The equipment class for the equipment under test, as defined in the IEC 60 721-3-4 [17]; +- 3) The equipment that does not comply with the mentioned classes, the relevant classes from IEC 60 721 [18] documentation for temperature, humidity and vibration shall be declared. + +NOTE: Reduced functionality for conditions that fall outside of the standard operational conditions is 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 60 068-2-1 [19]. + +#### Maximum temperature: + +The test shall be performed with the environmental test equipment and methods including the required environmental phenomena into the equipment, conforming to the test procedure of IEC 60 068-2-2 [20]. + +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 60 068-2-6 [21]. Other environmental conditions shall be within the ranges specified in annex 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 60 068-2-1 [19] Test Ab/Ad and IEC 60 068-2-2 [20] Test Bb/Bd: Dry heat. + +### Lower voltage limit: + +The equipment shall be supplied with a voltage equal to the lower limit declared by the manufacturer (as measured at the input terminals to the equipment). The tests shall be carried out at the steady state minimum and maximum temperature limits declared by the manufacturer for the equipment, to the methods described in IEC 60 068-2-1 [19] Test Ab/Ad and IEC 60 068-2-2 [20] Test Bb/Bd: Dry heat. + +--- + +## B.6 Measurement of test environments + +The measurement accuracy of the repeater test environments defined in annex B 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 + +## C.1 Measurement of conducted characteristics + +Table C.1-1: Derivation of test requirements (conducted tests) + +| Test | Minimum requirement in TS 38.106 [2] | Test Tolerance (TT) | Test requirement in the present document | +|----------------------------------------|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------| +| 6.2 Repeater output power | See TS 38.106 [2], clause 6.2 | Normal and extreme conditions:
0.7 dB, $f \leq 3.0$ GHz
1.0 dB, $3.0$ GHz $< f \leq 7.125$ GHz | Formula:
Upper limit + TT,
Lower limit – TT | +| 6.3 Frequency stability | See TS 38.106 [2], clause 6.3 | 12 Hz | Formula:
Frequency Error limit + TT | +| 6.4 Out of band gain | See TS 38.106 [2], clause 6.4 | 0.5 dB, $f \leq 3.0$ GHz
0.8 dB, $3.0$ GHz $< f \leq 7.125$ GHz | Formula:
Minimum Requirement + TT | +| 6.5.2 ACLR/ CACL | See TS 38.106 [2], clause 6.5.2 | Relative ACLR/CACL:
BW $\leq 20$ MHz: 0.8 dB
BW $> 20$ MHz: 1.2 dB

Absolute ACLR/CACL: 0 dB | Formula:
ACLR Minimum Requirement - TT
Absolute limit + TT | +| 6.5.3 Operating band unwanted emission | See TS 38.106 [2], clause 6.5.3 | Offsets $< 10$ MHz:
1.5 dB, $f \leq 3.0$ GHz
1.8 dB, $3.0$ GHz $< f \leq 7.125$ GHz

Offsets $\geq 10$ MHz: 0 dB | Formula:
Minimum Requirement + TT | +| 6.5.4 Spurious emissions | See TS 38.106 [2], clause 6.5.4 | 0 dB | Formula:
Minimum Requirement + TT | +| 6.6 EVM | See TS 38.106 [2], clause 6.6 | 1.25% | Formula:
EVM limit + TT | +| 6.7 Input intermodulation | See TS 38.106 [2], clause 6.7 | 0 dB | Formula:
Minimum Requirement + TT | +| 6.8 Output intermodulation | See TS 38.106 [2], clause 6.8 | 0 dB | Formula:
Minimum Requirement + TT | +| 6.9 ACRR | See TS 38.106 [2], clause 6.9 | 0.7 dB | Formula:
Minimum Requirement – TT | +| 6.10.1 Transmit ON/OFF power | See TS 38.106 [2], clause 6.10.1 | 2.0 dB, $f \leq 3.0$ GHz
2.5 dB, $3.0$ GHz $< f \leq 7.125$ GHz | Formula:
Minimum Requirement + TT | +| 6.10.2 Transmitter transient period | See TS 38.106 [2], clause 6.10.2 | N/A | | + +NOTE: TT values are applicable for normal condition unless otherwise stated. + +## Annex D (informative): Measurement system set-up + +Example of measurement system set-ups are attached below as an informative annex. + +## D.1 Repeater output power and transmit ON/OFF power + +![Block diagram of the measuring system set-up for repeater output power and transmit ON/OFF power. It shows three main components connected in a linear sequence: an NR Signal Generator, a Repeater under test, and a Power Meter or equivalent. Arrows indicate the flow of signal from left to right.](4dd5f00d74e7db5bbb2d011609bcc43d_img.jpg) + +``` +graph LR; A[NR Signal Generator] --> B[Repeater under test]; B --> C[Power Meter or equivalent]; +``` + +Block diagram of the measuring system set-up for repeater output power and transmit ON/OFF power. It shows three main components connected in a linear sequence: an NR Signal Generator, a Repeater under test, and a Power Meter or equivalent. Arrows indicate the flow of signal from left to right. + +**Figure D.1-1: Measuring system set-up for repeater output power and transmit ON/OFF power** + +Note 1: The repeater is a bi-directional device. The signal generator may need protection. + +Note 2: UL/DL timing can be provided to the repeater. + +## D.2 Out of band gain + +![Block diagram of the measuring system set-up for out of band gain. It shows three main components connected in a linear sequence: a CW Signal Generator, a Repeater under test, and a Spectrum Analyser. Arrows indicate the flow of signal from left to right.](f92e919c70b7adda2d0e778889f44fae_img.jpg) + +``` +graph LR; A[CW Signal Generator] --> B[Repeater under test]; B --> C[Spectrum Analyser]; +``` + +Block diagram of the measuring system set-up for out of band gain. It shows three main components connected in a linear sequence: a CW Signal Generator, a Repeater under test, and a Spectrum Analyser. Arrows indicate the flow of signal from left to right. + +**Figure D.2-1: Measuring system set-up for out of band gain** + +Note: The repeater is a bi-directional device. The signal generator may need protection. + +## D.3 Unwanted emission: Operating band unwanted emission, transmitter spurious emission, and ACLR + +![Figure D.3-1: Measuring system set-up for unwanted emission. The diagram shows three main components connected in a linear sequence from left to right: an 'NR Signal Generator', a 'Repeater under test', and a 'Spectrum analyser'. Each component is represented by a rectangular box, and they are connected by large, hollow, right-pointing arrows. The entire setup is enclosed within a larger rectangular frame.](8f8caebe58364416a2eda21039d8c7bf_img.jpg) + +Figure D.3-1: Measuring system set-up for unwanted emission. The diagram shows three main components connected in a linear sequence from left to right: an 'NR Signal Generator', a 'Repeater under test', and a 'Spectrum analyser'. Each component is represented by a rectangular box, and they are connected by large, hollow, right-pointing arrows. The entire setup is enclosed within a larger rectangular frame. + +**Figure D.3-1: Measuring system set-up for unwanted emission: Operating band unwanted emission, transmitter spurious emission, and ACLR** + +Note 1: The repeater is a bi-directional device. The signal generator may need protection. + +Note 2: UL/DL timing can be provided to the repeater. + +## D.4 Modulation Accuracy: Repeater Error Vector Magnitude and Frequency Stability + +![Figure D.4-1: Measuring system set-up for repeater error vector magnitude and frequency stability. The diagram shows three main components connected in a linear sequence from left to right: an 'NR Signal Generator', a 'Repeater under test', and a 'Signal analyser'. Each component is represented by a rectangular box, and they are connected by large, hollow, right-pointing arrows. The entire setup is enclosed within a larger rectangular frame.](c6e0b9030f9fb81435eaf9cb71532614_img.jpg) + +Figure D.4-1: Measuring system set-up for repeater error vector magnitude and frequency stability. The diagram shows three main components connected in a linear sequence from left to right: an 'NR Signal Generator', a 'Repeater under test', and a 'Signal analyser'. Each component is represented by a rectangular box, and they are connected by large, hollow, right-pointing arrows. The entire setup is enclosed within a larger rectangular frame. + +**Figure D.4-1: Measuring system set-up for repeater error vector magnitude and frequency stability** + +Note 1: The repeater is a bi-directional device. The signal generator may need protection. + +Note 2: UL/DL timing can be provided to the repeater. + +## D.5 Input intermodulation + +![Block diagram for input intermodulation measurement. Two CW Generators are connected to a Coupler. The output of the Coupler is connected to a Repeater under test. The output of the Repeater is connected to a Spectrum Analyser.](28f2f470a7b2446ae5f525123534383c_img.jpg) + +``` +graph LR; CW1[CW Generator] --> Coupler; CW2[CW Generator] --> Coupler; Coupler --> Repeater[Repeater under test]; Repeater --> SA[Spectrum Analyser]; +``` + +Block diagram for input intermodulation measurement. Two CW Generators are connected to a Coupler. The output of the Coupler is connected to a Repeater under test. The output of the Repeater is connected to a Spectrum Analyser. + +Figure D.5-1: Measuring system set-up for input intermodulation. + +Note: The repeater is a bi-directional device. The signal generator may need protection. + +## D.6 Output Intermodulation + +![Block diagram for output intermodulation measurement. An NR Signal Generator F1 is connected to a Repeater under test via an isolator. The output of the Repeater is connected to a Circulator. A second NR Signal Generator F2 is also connected to the Circulator. The output of the Circulator is connected to a Spectrum Analyser.](8a0a9aa5fac5d73eefb772afd44649f6_img.jpg) + +``` +graph LR; F1[NR Signal Generator F1] --> Isolator1(( )); Isolator1 --> Repeater[Repeater under test]; Repeater --> Circulator(( )); F2[NR Signal Generator F2] --> Circulator; Circulator --> SA[Spectrum Analyser]; +``` + +Block diagram for output intermodulation measurement. An NR Signal Generator F1 is connected to a Repeater under test via an isolator. The output of the Repeater is connected to a Circulator. A second NR Signal Generator F2 is also connected to the Circulator. The output of the Circulator is connected to a Spectrum Analyser. + +Figure D.6-1: Measuring system set-up for output intermodulation. + +Note 1: The repeater is a bi-directional device. The signal generator may need protection. + +Note 2: UL/DL timing can be provided to the repeater. + +## D.7 Adjacent Channel Rejection Ratio + +![Figure D.7-1: Measuring system set-up for Adjacent Channel Rejection Ratio](145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg) + +A block diagram showing the measuring system set-up for Adjacent Channel Rejection Ratio. It consists of three main components connected in a linear sequence from left to right: an 'NR Signal Generator', a 'Repeater under test', and a 'Spectrum Analyser'. Each component is represented by a rectangular box, and they are connected by large, hollow, right-pointing arrows. The entire sequence is enclosed within a larger rectangular frame. + +Figure D.7-1: Measuring system set-up for Adjacent Channel Rejection Ratio + +**Figure D.7-1: Measuring system set-up for Adjacent Channel Rejection Ratio** + +Note 1: The repeater is a bi-directional device. The signal generator may need protection. + +Note 2: UL/DL timing can be provided to the repeater. + +## D.8 Rx spurious emission requirement + +![Figure D.8-1: Measuring system set-up for receiver spurious emission](4aeaa51a3999fab21171224e238cb571_img.jpg) + +A block diagram showing the measuring system set-up for receiver spurious emission. It consists of three main components connected in a linear sequence from left to right: an 'NR Signal Generator (optional)', a 'Repeater under test', and a 'Spectrum Analyser'. Each component is represented by a rectangular box, and they are connected by large, hollow, right-pointing arrows. The entire sequence is enclosed within a larger rectangular frame. + +Figure D.8-1: Measuring system set-up for receiver spurious emission + +**Figure D.8-1: Measuring system set-up for receiver spurious emission** + +Note 1: The repeater is a bi-directional device. The signal generator may need protection. + +Note 2: UL/DL timing can be provided to the repeater. + +## Annex E (normative): In-channel TX tests + +## E.1 General + +The in-channel TX test enables the measurement of all relevant parameters that describe the in-channel quality of the output signal of the repeater under test in a single measurement process. + +The parameters describing the in-channel quality of a transmitter, however, are not necessarily independent. The algorithm chosen for description inside this annex places particular emphasis on the exclusion of all interdependencies among the parameters. + +## E.2 Basic principles + +The process is based on the comparison of the actual output signal of the repeater under test, received by an ideal receiver, with an ideal signal, that is generated by the measuring equipment and represents an ideal error free received signal. All signals are represented as equivalent (generally complex) baseband signals. + +The description below uses numbers and illustrations as examples only. These numbers are taken from a FDD frame structure with normal CP length, 30 kHz SCS and a transmission bandwidth configuration of 100 MHz ( $N_{RB} = 273$ ). The application of the text below, however, is not restricted to this parameter set. + +### E.2.1 Output signal of the repeater under test + +The output signal of the repeater under test is acquired by the measuring equipment and stored for further processing. It is sampled at a sampling rate which is the product of the SCS and the *FFT size*, and it is named $z(v)$ . The *FFT size* is determined by the transmission bandwidth in table 6.6.3.5-2 for 15 kHz SCS, table 6.6.3.5-3 for 30 kHz SCS and table 6.5.3.5-4 for 60 kHz SCS in [6]. In the time domain, it comprises at least 10 ms. It is modelled as a signal with the following parameters: + +- demodulated data content, +- carrier frequency, +- amplitude and phase for each subcarrier. + +For the example in the annex, the *FFT size* is 4096 based on table 6.6.3.5-3 in [6]. The sampling rate of 122.88 Msps is the product of the *FFT size* and SCS. + +### E.2.2 Ideal signal + +Two types of ideal signals are defined: + +The first ideal signal $i_1(v)$ is constructed by the measuring equipment according to the relevant TX specifications, using the following parameters: + +- demodulated data content, +- nominal carrier frequency, +- nominal amplitude and phase for each subcarrier. + +It is represented as a sequence of samples at the sampling rate determined from annex E.2.1 in the time domain. The structure of the signal is described in the test models. + +The second ideal signal $i_2(v)$ is constructed by the measuring equipment according to the relevant TX specifications, using the following parameters: + +- nominal demodulation reference signals (all other modulation symbols are set to 0 V), +- nominal carrier frequency, +- nominal amplitude and phase for each applicable subcarrier, + +- nominal timing. + +It is represented as a sequence of samples at the sampling rate determined from annex E.2.1 in the time domain. + +## E.2.3 Measurement results + +The measurement results, achieved by the in-channel TX test are the following: + +- Carrier frequency stability +- EVM + +## E.2.4 Measurement points + +The EVM shall be measured at the point after the FFT and a zero-forcing (ZF) equalizer in the receiver, as depicted for FR1 in figure E.2.4-1. The FFT window of *FFT size* samples out of (*FFT size* + cyclic prefix length) samples in the time domain is selected in the "Remove CP" box. The *FFT size* and the cyclic prefix length are obtained from table 6.6.3.5-2 for 15 kHz SCS, table 6.6.3.5-3 for 30 kHz SCS and table 6.6.3.5-4 for 60 kHz SCS in [6]. + +In one subframe, there are two symbols with the length of the cyclic prefix larger than the values listed in tables 6.6.3.5-2, 6.6.3.5-3 and 6.6.3.5-4 in [6]. Table E.2.4-1 lists the slot number and the symbol number and the formula how to compute the length of cyclic prefix for those two symbols according to the sampling rate. + +**Table E.2.4-1: Slot number and symbol number identifying the longer CP length for normal CP** + +| SCS (kHz) | # slots in subframe | Symbol # and slot # with longer CP | Longer CP length | +|-----------|---------------------|------------------------------------------|-----------------------------------| +| 15 | 1 | (symbol 0, slot 0)
(symbol 7, slot 0) | CP length + FFT size / 128 | +| 30 | 2 | (symbol 0, slot 0)
(symbol 0, slot 1) | CP length + FFT size / 64 | +| 60 | 4 | (symbol 0, slot 0)
(symbol 0, slot 2) | CP length + FFT size / 32 | + +For the example used in the annex, the "Remove CP" box selects 4096 samples out of 4384 samples. Symbol 0 has 64 more samples in the cyclic prefix than the other 13 symbols in the slot (the longer CP length = 352). + +![Block diagram showing the signal flow for FR1 EVM measurements: repeater TX -> Remove CP -> FFT -> Per-subcarrier Amplitude/phase correction -> Symbol detection/decoding. A 'Pre-/post FFT time / frequency synchronization' block is connected to the 'Remove CP', 'FFT', and 'Per-subcarrier Amplitude/phase correction' blocks. A 'Reference point for EVM measurement' is indicated below the 'Per-subcarrier Amplitude/phase correction' block.](55048d730ad7a041082df5cc76d53219_img.jpg) + +``` + +graph LR + TX[repeater TX] --> CP[Remove CP] + CP --> FFT[FFT] + FFT --> PC[Per-subcarrier Amplitude/phase correction] + PC --> SD[Symbol detection/decoding] + Sync[Pre-/post FFT time / frequency synchronization] -.-> CP + Sync -.-> FFT + Sync -.-> PC + Ref[Reference point for EVM measurement] -.-> PC + +``` + +Block diagram showing the signal flow for FR1 EVM measurements: repeater TX -> Remove CP -> FFT -> Per-subcarrier Amplitude/phase correction -> Symbol detection/decoding. A 'Pre-/post FFT time / frequency synchronization' block is connected to the 'Remove CP', 'FFT', and 'Per-subcarrier Amplitude/phase correction' blocks. A 'Reference point for EVM measurement' is indicated below the 'Per-subcarrier Amplitude/phase correction' block. + +**Figure E.2.4-1: Reference point for FR1 EVM measurements** + +## E.3 Pre-FFT minimization process + +Sample Timing, Carrier Frequency in $z(v)$ are varied in order to minimise the difference between $z(v)$ and $i_1(v)$ , after the amplitude ratio of $z(v)$ and $i_1(v)$ has been scaled. Best fit (minimum difference) is achieved when the RMS difference value between $z(v)$ and $i_1(v)$ is an absolute minimum. + +The carrier frequency variation is the measurement result: carrier frequency stability. + +From the acquired samples, one value of carrier frequency stability can be derived. + +NOTE 1: The minimisation process, to derive the RF error can be supported by post-FFT operations. However the minimisation process defined in the pre-FFT domain comprises all acquired samples (i.e. it does not exclude the samples inbetween the FFT widths and it does not exclude the bandwidth outside the transmission bandwidth configuration). + +NOTE 2: The algorithm would allow to derive carrier frequency error and sample frequency error of the TX under test separately. However there are no requirements for sample frequency error. Hence the algorithm models the RF and the sample frequency commonly (not independently). It returns one error and does not distinguish between both. + +After this process, the samples $z(v)$ are called $z^0(v)$ . + +## E.4 Timing of the FFT window + +The FFT window length is *FFT size* samples per OFDM symbol. For FDD, there are $14N_{dt}$ FFTs performed where $N_{dt}$ is the number of slots in a 10 ms measurement interval, and the number of symbols in a slot for normal CP is 14. + +The position in time for the FFT shall be determined. + +For the example used in the annex, the FFT window length is 4096 samples per OFDM symbol. 280 FFTs (i.e. 1,146,880 samples) cover less than the acquired number of samples (i.e. 1,228,800 samples in 10 ms). + +In an ideal signal, the FFT may start at any instant within the cyclic prefix without causing an error. The TX filter, however, reduces the window. The EVM requirements shall be met within a window $W < CP$ . There are three different instants for FFT: + +- Centre of the reduced window, called $\Delta\tilde{c}$ , +- $\Delta c - W/2$ , and +- $\Delta c + W/2$ . + +The value of EVM window length $W$ is obtained from tables 6.6.3.5-2 for 15 kHz SCS, 6.6.3.5-3 for 30 kHz SCS and 6.6.3.5-4 for 60 kHz SCS in [6] and the transmission bandwidth. + +The repeater shall transmit a signal according to the test models intended for EVM. The demodulation reference signal of the second ideal signal shall be used to find the centre of the FFT window. + +The timing of the measured signal is determined in the pre-FFT domain as follows, using $z^0(v)$ and $i_2(v)$ : + +1. The measured signal is delay spread by the TX filter. Hence the distinct borders between the OFDM symbols and between data and CP are also spread and the timing is not obvious. +2. In the ideal signal $i_2(v)$ , the timing is known. + +Correlation between bullet (1) and (2) will result in a correlation peak. The meaning of the correlation peak is approximately the "impulse response" of the TX filter. + +3. The meaning of "impulse response" assumes that the autocorrelation of the ideal signal $i_2(v)$ is a Dirac peak and that the correlation between the ideal signal $i_2(v)$ and the data in the measured signal is 0. The correlation peak, (the highest, or in case of more than one highest, the earliest) indicates the timing in the measured signal. + +The number of samples used for FFT is reduced compared to $z^0(v)$ . This subset of samples is called $z'(v)$ . + +From the acquired samples one timing can be derived. + +The timing of the centre $\Delta\tilde{c}$ is determined according to the cyclic prefix length of the OFDM symbols. For normal CP, there are two values for $\Delta\tilde{c}$ in a 1 ms period: + +- $\Delta\tilde{c}$ = length of cyclic prefix / 2, +- $\Delta\tilde{c}$ = Longer CP length - length of cyclic prefix / 2, + +Where the length of cyclic prefix is obtained from table 6.6.3.5-2 for 15 kHz SCS, table 6.6.3.5-3 for 30 kHz SCS and table 6.6.3.5-4 for 60 kHz SCS in [6], and the longer CP length is obtained from table F.2.4-1. + +As per the example values: + +- $\Delta\tilde{c}$ = 144 within the CP of length 288 for OFDM symbols 1 to 13 of a slot, +- $\Delta\tilde{c}$ = 208 = 352 - 144) within the CP of length 352 for OFDM symbol 0 of a slot. + +## E.5 Resource element TX power + +Perform FFT on $z'(v)$ with the FFT window timing $\Delta\tilde{c}$ . The result is called $Z'(t, f)$ . The RE TX power (RETP) is then defined as: + +$$RETP = |Z'(t, f)|^2 SCS$$ + +Where SCS is the subcarrier spacing in Hz. + +From RETP the OFDM Symbol TX power (OSTP) is derived as follows: + +$$OSTP = \frac{1}{N_{sym}} \sum RETP$$ + +Where the summation accumulates $N_{RB} N_{sc}^{RB}$ RETP values of all $N_{sym}$ OFDM symbols that carry PDSCH and not containing PDCCH, RS or SSB within a slot. + +From the acquired samples, $N_{dl}$ values for each OSTP can be obtained and averaged where $N_{dl}$ is the number of slots in a 10 ms measurement interval for FDD. For TDD, $N_{dl}$ is the number of slots with downlink symbols in a 10 ms measurement interval and is computed according to the values in table 4.9.2.2-1 in [6]. + +For the example used in the annex, $N_{dl} = 20$ and $N_{RB} = 273$ . + +## E.6 Post-FFT equalisation + +Perform $14N_{dl}$ FFTs on $z'(v)$ , one for each OFDM symbol within 10 ms measurement interval with the FFT window timing to produce an array of samples, $14N_{dl}$ in the time axis $t$ by $FFT\ size$ in the frequency axis $f$ . + +For the example in the annex, 280 FFTs are performed on $z'(v)$ . The result is an array of samples, 280 in the time axis by 4096 in the frequency axis. + +The equalizer coefficients $\tilde{a}(f)$ and $\tilde{\varphi}(f)$ are determined as follows: + +1. Calculate the complex ratios (amplitude and phase) of the post-FFT acquired signal $Z'(t, f)$ and the post-FFT ideal signal $I_2(t, f)$ for each demodulation reference signal, over 10 ms measurement interval. This process creates a set of complex ratios: + +$$a(t, f) e^{j\varphi(t, f)} = \frac{Z'(t, f)}{I_2(t, f)}$$ + +2. Perform time averaging at each demodulation reference signal subcarrier of the complex ratios, the time-averaging length is 10 ms measurement interval. Prior to the averaging of the phases $\varphi(t_i, f)$ an unwrap operation must be performed according to the following definition: + +- The unwrap operation corrects the radian phase angles of $\varphi(t_i, f)$ by adding multiples of $2 * \pi$ when absolute phase jumps between consecutive time instances $t_i$ are greater than or equal to the jump tolerance of $\pi$ radians. +- This process creates an average amplitude and phase for each demodulation reference signal subcarrier (i.e. every second subcarrier). + +$$a(f) = \frac{\sum_{i=1}^N a(t_i, f)}{N}$$ + +and + +$$\varphi(f) = \frac{\sum_{i=1}^N \varphi(t_i, f)}{N}$$ + +Where $N$ is the number of demodulation reference signals time-domain locations $t_i$ from $Z'(t, f)$ for each demodulation reference signal subcarrier $f$ . + +3. The equalizer coefficients for amplitude and phase $\hat{a}(f)$ and $\hat{\varphi}(f)$ at the demodulation reference signal subcarriers are obtained by computing the moving average in the frequency domain of the time-averaged demodulation reference signal subcarriers. The moving average window size is 19 and averaging is over the DM-RS subcarriers in the allocated RBs. For DM-RS subcarriers at or near the edge of the channel, or when the number of available DM-RS subcarriers within a set of contiguously allocated RBs is smaller than the moving average window size, the window size is reduced accordingly as per figure F.6-1. +4. Perform linear interpolation from the equalizer coefficients $\hat{a}(f)$ and $\hat{\varphi}(f)$ to compute coefficients $\tilde{a}(f)$ , $\tilde{\varphi}(f)$ for each subcarrier. + +![Diagram A: Moving averaging at channel edge. A graph showing reference subcarriers on the x-axis. The first subcarrier is not averaged. The second is the average of the first three. The third and subsequent 7 subcarriers are averaged over 5, 7 .. 17 subcarriers. From the 10th subcarrier onwards, the window size is 19 until the upper edge of the channel is reached, and then it reduces back to 1.](bf2aa2e550e42aa4a70d02c8ce9e9f0d_img.jpg) + +The first reference subcarrier is not averaged + +The second reference subcarrier is the average of the first three subcarriers + +The subsequent 7 subcarriers are averaged over 5, 7 .. 17 subcarriers + +From the 10th subcarrier onwards the window size is 19 until the upper edge of the channel is reached and the window size reduces back to 1 + +Reference subcarriers + +Diagram A: Moving averaging at channel edge. A graph showing reference subcarriers on the x-axis. The first subcarrier is not averaged. The second is the average of the first three. The third and subsequent 7 subcarriers are averaged over 5, 7 .. 17 subcarriers. From the 10th subcarrier onwards, the window size is 19 until the upper edge of the channel is reached, and then it reduces back to 1. + +A. Moving averaging at channel edge + +Figure B shows an example of 1RB allocation using a reduced window size of five subcarriers for averaging. The same method applies for RB allocations with fewer than 19 subcarriers available for the moving average size. For the case of 2 and 3 RB allocations, 11 and 17 are the window sizes, respectively. + +![Diagram B: Moving averaging for the case when the number of available reference subcarriers within a set of contiguously allocated RBs is smaller than the moving average window size. A graph showing 5 reference subcarriers. The first, second, and third reference subcarriers are the average of the five subcarriers on the left. The fourth, fifth, and sixth reference subcarriers are the average of the five subcarriers on the right.](9058545957858eea01975496aa340d5b_img.jpg) + +The first, second and third reference subcarriers are the average of the five subcarriers on left + +The first, second and third reference subcarriers are the average of the five subcarriers on right + +Reference subcarriers + +Diagram B: Moving averaging for the case when the number of available reference subcarriers within a set of contiguously allocated RBs is smaller than the moving average window size. A graph showing 5 reference subcarriers. The first, second, and third reference subcarriers are the average of the five subcarriers on the left. The fourth, fifth, and sixth reference subcarriers are the average of the five subcarriers on the right. + +B. Moving averaging for the case when the number of available reference subcarriers within a set of contiguously allocated RBs is smaller than the moving average window size + +Figure E.6-1: Reference subcarrier smoothing in the frequency domain + +## E.7 EVM + +### E.7.0 General + +For EVM create two sets of $Z_{eq}'(t, f)$ , according to the timing $(\Delta c - W/2)$ and $(\Delta c + W/2)$ , using the equalizer coefficients from F.6. + +The equivalent ideal samples are calculated from $i_1(v)$ (annex E.2.2) and are called $I(t, f)$ . + +The EVM is the difference between the ideal signal and the equalized measured signal. + +$$EVM = \sqrt{\frac{\sum_{t \in T} \sum_{f \in F(t)} |Z_{eq}'(t, f) - I(t, f)|^2}{\sum_{t \in T} \sum_{f \in F(t)} |I(t, f)|^2}}$$ + +Where: + +- $T$ is the set of symbols with the considered modulation scheme being active within the slot, +- $F(t)$ is the set of subcarriers within the resource blocks with the considered modulation scheme being active in symbol $t$ , +- $I(t, f)$ is the ideal signal reconstructed by the measurement equipment in accordance with relevant test models, +- $Z_{eq}'(t, f)$ is the equalized signal under test. + +NOTE: Although the basic unit of measurement is one slot, the equalizer is calculated over the entire 10 ms measurement interval to reduce the impact of noise in the reference signals. + +### E.7.1 Averaged EVM (FDD) + +EVM is averaged over all allocated downlink resource blocks with the considered modulation scheme in the frequency domain, and a minimum of $N_{dl}$ slots where $N_{dl}$ is the number of slots in a 10 ms measurement interval. The averaging in the time domain equals the $N_{dl}$ slot duration of the 10 ms measurement interval from the equalizer estimation step. + +$$\overline{EVM}_{frame} = \sqrt{\frac{\frac{1}{\sum_{i=1}^{N_{dl}} N_i} \sum_{i=1}^{N_{dl}} \sum_{j=1}^{N_i} EVM_{i,j}^2}{}}$$ + +Where $N_i$ is the number of resource blocks with the considered modulation scheme in slot $i$ . + +The EVM requirements shall be tested against the maximum of the RMS average at the window $W$ extremities of the EVM measurements: + +Thus $\overline{EVM}_{frame,l}$ is calculated using $\bar{t} = \Delta \bar{t}_l$ in the expressions above and $\overline{EVM}_{frame,h}$ is calculated using $\bar{t} = \Delta \bar{t}_h$ in the $\overline{EVM}_{frame}$ calculation where ( $l$ and $h$ , low and high; where low is the timing $(\Delta c - W/2)$ and high is the timing $(\Delta c + W/2)$ ). + +Thus: + +$$\overline{EVM} = \max(\overline{EVM}_{frame,l}, \overline{EVM}_{frame,h})$$ + +The resulting $\overline{EVM}$ is compared against the limit. + +## E.7.2 Averaged EVM (TDD) + +Let $N_{dl}^{TDD}$ be the number of slots with downlink symbols within a 10 ms measurement interval. For TDD, the averaging in the time domain can be calculated from $N_{dl}^{TDD}$ slots of different 10 ms measurement intervals and should have a minimum of $N_{dl}$ slots averaging length where $N_{dl}$ is the number of slots in a 10 ms measurement interval. + +$\overline{EVM}_{frame}$ is derived by: Square the EVM results in each 10 ms measurement interval. Sum the squares, divide the sum by the number of EVM relevant locations, square-root the quotient (RMS). + +$$\overline{EVM}_{frame} = \sqrt{\frac{1}{\sum_{i=1}^{N_{dl}^{TDD}} N_i} \sum_{i=1}^{N_{dl}^{TDD}} \sum_{j=1}^{N_i} EVM_{i,j}^2}$$ + +Where $N_i$ is the number of resource blocks with the considered modulation scheme in slot $i$ . + +The $\overline{EVM}_{frame}$ is calculated, using the maximum of $\overline{EVM}_{frame}$ at the window $W$ extremities. Thus $\overline{EVM}_{frame,l}$ is calculated using $\tilde{t} = \Delta\tilde{t}_l$ and $\overline{EVM}_{frame,h}$ is calculated using $\tilde{t} = \Delta\tilde{t}_h$ ( $l$ and $h$ , low and high; where low is the timing $(\Delta c - W/2)$ and and high is the timing $(\Delta c + W/2)$ ). + +$$EVM_{frame} = \max(\overline{EVM}_{frame,l}, \overline{EVM}_{frame,h})$$ + +In order to unite at least $N_{dl}$ slots, consider the minimum integer number of 10 ms measurement intervals, where $N_{frame}$ is determined by. + +$$N_{frame} = \left\lceil \frac{10 \times N_{slot}}{N_{dl}^{TDD}} \right\rceil$$ + +and $N_{slot} = 1$ for 15 kHz SCS, $N_{slot} = 2$ for 30 kHz SCS and $N_{slot} = 4$ for 60 kHz SCS normal CP. + +Unite by RMS. + +$$\overline{EVM} = \sqrt{\frac{1}{N_{frame}} \sum_{k=1}^{N_{frame}} EVM_{frame,k}^2}$$ + +The resulting $\overline{EVM}$ is compared against the limit. + +## Annex F (informative): Change history + +| Change history | | | | | | | | +|----------------|------------|------------|----|-----|-----|---------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-05 | RAN4#103e | | | | | TS skeleton | 0.0.1 | +| 2022-08 | RAN4#104e | R4-2211701 | | | | TP for TS 38.115-1: Clause 5 operating bands | 0.1.0 | +| 2022-08 | RAN4#104e | R4-2212840 | | | | TP to TS 38.115-1 clause 6.8 Output intermodulation - conducted | 0.1.0 | +| 2022-08 | RAN4#104e | R4-2213719 | | | | TP for TS 38.115-1: section 4.10~4.12 | 0.1.0 | +| 2022-08 | RAN4#104e | R4-2213976 | | | | TP to TS 38.115-1 Annex A Repeater stimulus signals | 0.1.0 | +| 2022-08 | RAN4#104e | R4-2214740 | | | | TP for TS 38.115-1: Clause 3 definitions | 0.1.0 | +| 2022-08 | RAN4#104e | R4-2214741 | | | | TP for TS 38.115-1: Clause 4.2-4.5 | 0.1.0 | +| 2022-08 | RAN4#104e | R4-2214785 | | | | TP to TS 38.115-1: Test Configurations and Requirement applicability | 0.1.0 | +| 2022-08 | RAN4#104e | R4-2214787 | | | | TP to TS 38.115-1: Frequency Stability, Out of band gain, unwanted emissions | 0.1.0 | +| 2022-08 | RAN4#104e | R4-2214789 | | | | TP to TS 38.115-1: In-band measurements Annex | 0.1.0 | +| 2022-08 | RAN4#104e | R4-2214791 | | | | TP to TS 38.115-1: TDD Switching | 0.1.0 | +| 2022-08 | RAN4#104e | R4-2214801 | | | | TP to TS 38.115-1: Manufacturer declarations for NR FR1 repeaters | 0.1.0 | +| 2022-08 | RAN4#104e | R4-2214803 | | | | TP to TS 38.115-1 clause 6.7 Input intermodulation - conducted | 0.1.0 | +| 2022-08 | RAN4#104e | R4-2214840 | | | | TP for TS 38.115-1: Section 6.9 | 0.1.0 | +| 2022-08 | RAN4#104e | R4-2214841 | | | | TP for TS 38.115-1: Annex D | 0.1.0 | +| 2022-08 | RAN4#104e | R4-2214865 | | | | TP to TS 38.115-1 clause 4.9 RF channels and test models | 0.1.0 | +| 2022-08 | RAN4#104e | R4-2214867 | | | | TP to TS 38.115-1 clause 6.6 EVM - conducted | 0.1.0 | +| 2022-10 | RAN4#104be | R4-2216839 | | | | TP to TS 38.115-1: Annex B: Environmental requirements for the repeater | 0.2.0 | +| 2022-10 | RAN4#104be | R4-2216840 | | | | TP to TS 38.115-1: Annex C: Test tolerances and derivation of test requirements | 0.2.0 | +| 2022-10 | RAN4#104be | R4-2216841 | | | | TP to TS 38.115-1: Annex E: Characteristics of interfering signals | 0.2.0 | +| 2022-10 | RAN4#104be | R4-2217293 | | | | TP to TS 38.115-1: Repeater output power (6.1, 6.2) | 0.2.0 | +| 2022-10 | RAN4#104be | R4-2217296 | | | | TP for TS 38.115-1: scope and reference | 0.2.0 | +| 2022-10 | RAN4#104be | R4-2217297 | | | | TP to TS 38.115-1: Measurement uncertainties and test requirements (4.1) | 0.2.0 | +| 2022-11 | RAN4#105 | R4-2218486 | | | | Correction TP for TS 38.115-1 | 0.3.0 | +| 2022-11 | RAN4#105 | R4-2220214 | | | | TP to 38.115-1: ACLR requirement | 0.3.0 | +| 2022-11 | RAN4#105 | R4-2220217 | | | | TP to 38.115-1: EVM requirement | 0.3.0 | +| 2022-11 | RAN4#105 | R4-2220226 | | | | Draft CR to 38.115-1: Spectrum purity | 0.3.0 | +| 2022-11 | RAN4#105 | R4-2220270 | | | | TP to 38.115-1: ACRR requirement | 0.3.0 | +| 2022-12 | RAN#98e | RP-222843 | | | | Editorial update for 1.0.0 version | 1.0.0 | + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|-----------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-12 | RAN#98-e | | | | | Approved by plenary – Rel-17 spec under change control | 17.0.0 | +| 2023-03 | RAN#99 | RP-230518 | 0001 | 1 | F | CR for TS 38.115-1: Correction of some errors | 17.1.0 | +| 2023-03 | RAN#99 | RP-230518 | 0003 | 1 | B | CR to TS38.106 the introduction of band n104 | 17.1.0 | +| 2023-03 | RAN#99 | RP-230518 | 0005 | | F | CR to 38.115-1: Correction on repeater EVM test procedure | 17.1.0 | +| 2023-03 | RAN#99 | RP-230518 | 0006 | | F | CR to 38.115-1: Correction on repeater ACLR requirement | 17.1.0 | +| 2023-03 | RAN#99 | RP-230518 | 0007 | | F | CR to 38.115-1: NR repeater measurement system set-up | 17.1.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-03 | RAN#99 | RP-230535 | 0002 | | B | CR to 38.115-1 on introduction of Band n54 | 18.0.0 | +| 2023-03 | RAN#99 | RP-230533 | 0004 | | B | CR to TS38.115-1 the introduction of APT600MHz | 18.0.0 | +| 2023-06 | RAN#100 | RP-231339 | 0009 | | A | CR for TS 38.115-1, Add manufacturer declarations for test configurations and RF channels | 18.1.0 | +| 2023-06 | RAN#100 | RP-231339 | 0011 | | A | CR to 38.115-1: Corrections on repeater transient period requirements (Rel-18) | 18.1.0 | +| 2023-06 | RAN#100 | RP-231339 | 0013 | | A | CR to TS 38.115-1: Addition of missing bands for repeater co-existence and co-location requirements | 18.1.0 | +| 2023-06 | RAN#100 | RP-231339 | 0015 | | A | CR to TS 38.115-1: Clarifications for repeater test models | 18.1.0 | +| 2023-09 | RAN#101 | RP-232496 | 0017 | | A | [NR repeaters] CR to 38.115-1: Input intermodulation | 18.2.0 | +| 2023-12 | RAN#102 | RP-233366 | 0018 | | B | CR to TS38.115-1: introduction of NR bands n31 and n72 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233366 | 0019 | 1 | B | CR to TS38.115-1: introduction of band n106 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233366 | 0020 | | B | CR to TS 38.115-1 - Introduction of band n109 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233350 | 0022 | | A | CR to 38.115-1: Correction of terminologies for NR repeaters (Rel-18) | 18.3.0 | +| 2023-12 | RAN#102 | RP-233350 | 0024 | | F | CR to TS 38.115-1 with correction of co-existence and co-location requirements | 18.3.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38141-1/00bb8c9fd2ec7fa7da34a98f824468b6_img.jpg b/marked/Rel-18/38_series/38141-1/00bb8c9fd2ec7fa7da34a98f824468b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5c632beec9c344a30788c18b8edd67fab96dff0 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/00bb8c9fd2ec7fa7da34a98f824468b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9a7130ea9dae1183d1c75b9b1d914e3c7a0d3e5bf8ef53c4f35255592ca37c1 +size 5534 diff --git a/marked/Rel-18/38_series/38141-1/068981837b91c115a6ac8b11ad50a49a_img.jpg b/marked/Rel-18/38_series/38141-1/068981837b91c115a6ac8b11ad50a49a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43cb40ac0f7ce8ca5b2d26ff8188994bd9ea8e15 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/068981837b91c115a6ac8b11ad50a49a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa43445c46f5b4f07f09268f4567b2f44b66fc28fd5fe6f58485c10fe3e74767 +size 53462 diff --git a/marked/Rel-18/38_series/38141-1/09b3589ff2a5c24911954d02059cb9b4_img.jpg b/marked/Rel-18/38_series/38141-1/09b3589ff2a5c24911954d02059cb9b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..997b2a87c2b279f0cc17d765fd11ad0a0561fdad --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/09b3589ff2a5c24911954d02059cb9b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59abdcd5b96a98cdac88f6ab260d545c4fef61c36b393bc8b446636f186c1ca1 +size 29656 diff --git a/marked/Rel-18/38_series/38141-1/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-18/38_series/38141-1/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc0d354e2757f055990e1d665746d030014c7a6a --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44f438ee1a78d5d244d99f9e81a6058cd12670981f4b4487e1d3bf89364af571 +size 30625 diff --git a/marked/Rel-18/38_series/38141-1/0cbb609996cfd29997216c8f50dceee7_img.jpg b/marked/Rel-18/38_series/38141-1/0cbb609996cfd29997216c8f50dceee7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8800fa6031c45e371326faa73b530489a959001c --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/0cbb609996cfd29997216c8f50dceee7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91e16537373319c8a0ce77378c8ed591476f631b300275ca95523fd8bf601d47 +size 40014 diff --git a/marked/Rel-18/38_series/38141-1/0e83feb3f1198525296af300ae5e2604_img.jpg b/marked/Rel-18/38_series/38141-1/0e83feb3f1198525296af300ae5e2604_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5475cf07e53840c85c7a489d73b11b14f6045266 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/0e83feb3f1198525296af300ae5e2604_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44bbbeb2c26677ae46cac7e35607f17411cc505558e8f5e00c3ffdad62dec646 +size 5507 diff --git a/marked/Rel-18/38_series/38141-1/14b4b0349989d63cec07229938e57ffd_img.jpg b/marked/Rel-18/38_series/38141-1/14b4b0349989d63cec07229938e57ffd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0ce4ad09cd3cabf835ad1b0c8c0aae19fa8624a --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/14b4b0349989d63cec07229938e57ffd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:078232b2148a4452d88f8bf01f910160c1b295345ae6eac9231e5af58f94bcf0 +size 42210 diff --git a/marked/Rel-18/38_series/38141-1/19babf72812f45dcc737d237e423d2c0_img.jpg b/marked/Rel-18/38_series/38141-1/19babf72812f45dcc737d237e423d2c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..561e25ea293649f20ab0da51e133dbad38cdd952 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/19babf72812f45dcc737d237e423d2c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32d11c0035213712f7e96db0c7652270889ea2f7026539885337ed4443ec3196 +size 43761 diff --git a/marked/Rel-18/38_series/38141-1/200e4dcbe6f9ac71fa87da9310aac99a_img.jpg b/marked/Rel-18/38_series/38141-1/200e4dcbe6f9ac71fa87da9310aac99a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc674b563b20467e92bc2217988ffdde2c89f437 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/200e4dcbe6f9ac71fa87da9310aac99a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd763862b0447c7efb21a1b4d8af348aa1cae742e2fad9274dd381fdfd5281b2 +size 19571 diff --git a/marked/Rel-18/38_series/38141-1/236b5a83f488c361479b9b44e462f978_img.jpg b/marked/Rel-18/38_series/38141-1/236b5a83f488c361479b9b44e462f978_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..577d23a4883729c66138c65e9f6b47bdacb12868 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/236b5a83f488c361479b9b44e462f978_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:200fa96613cb34c5816912bbf5c77dd257baaf17494735adb0bb6344811aec85 +size 5092 diff --git a/marked/Rel-18/38_series/38141-1/2ce4c14cc166ab2d1635adf7c1a2dda9_img.jpg b/marked/Rel-18/38_series/38141-1/2ce4c14cc166ab2d1635adf7c1a2dda9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a5d3b62e69458960b72fdec1a3dcab0ede5f935 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/2ce4c14cc166ab2d1635adf7c1a2dda9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:952d9bcd2340d3127b11480a574521221d65c214f0b23a01840e64959b6b0107 +size 5200 diff --git a/marked/Rel-18/38_series/38141-1/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-18/38_series/38141-1/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..777b9bfc3dceb4017c2b49a793260028cdc04af8 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4c3b84da00c8f525acd5d2c1618aed60c89606f7974b1c09ac5c70ee0e96c3f +size 29275 diff --git a/marked/Rel-18/38_series/38141-1/34921caa1996eef32dd520e93a1e64b8_img.jpg b/marked/Rel-18/38_series/38141-1/34921caa1996eef32dd520e93a1e64b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8be2fc62e47427ccf86a6e03c48c0df91f02cdcc --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/34921caa1996eef32dd520e93a1e64b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7473fb0374c0863397e759752ce32ce366757a8984f392910ed10642455624f6 +size 20710 diff --git a/marked/Rel-18/38_series/38141-1/34e6c9b53bd1e85bf2448540c7ed2484_img.jpg b/marked/Rel-18/38_series/38141-1/34e6c9b53bd1e85bf2448540c7ed2484_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b662399ce3be5ae15c4b2e9ae1662123d10159db --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/34e6c9b53bd1e85bf2448540c7ed2484_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:213870df4967351c20e1a679486b6b297c61b8ff86dc6aba403b3bfaf32b8882 +size 34210 diff --git a/marked/Rel-18/38_series/38141-1/34f6baf47c53b490142dbe71f900f406_img.jpg b/marked/Rel-18/38_series/38141-1/34f6baf47c53b490142dbe71f900f406_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..352456c0847b9f076297e971e4910d1c5cd9e05f --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/34f6baf47c53b490142dbe71f900f406_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb1714ec4cb5b7a60af9fba18e75f6aba98f0e5ab93343f1a219c787b1677429 +size 5591 diff --git a/marked/Rel-18/38_series/38141-1/3b5dee61a2394578df7e680b9a098fa7_img.jpg b/marked/Rel-18/38_series/38141-1/3b5dee61a2394578df7e680b9a098fa7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..267aec0cba5c0a18f4c396110b146a1e406a07f8 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/3b5dee61a2394578df7e680b9a098fa7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7215473c82bb423f84eedfc00c12da6f8599dde0e90ce0003b9fffead134331 +size 37396 diff --git a/marked/Rel-18/38_series/38141-1/3c34a281971985392326517db208286d_img.jpg b/marked/Rel-18/38_series/38141-1/3c34a281971985392326517db208286d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1dac5928ce901f64443c69ab260441913cb0e962 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/3c34a281971985392326517db208286d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f8717349d4883fc5d3a83868d22419fe6343c86f035898d3bae83d94251d23f +size 5786 diff --git a/marked/Rel-18/38_series/38141-1/3f09464f0a8ac9446981a53f9b78df2c_img.jpg b/marked/Rel-18/38_series/38141-1/3f09464f0a8ac9446981a53f9b78df2c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59c2f0391d935b1c02781c9293fca897c9772577 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/3f09464f0a8ac9446981a53f9b78df2c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e74e70954cfc77488fe99b0e1306dc57467892d9eb47d2f773745d52446b4ad +size 19651 diff --git a/marked/Rel-18/38_series/38141-1/408c4798ea60469e0728a7cbbd598668_img.jpg b/marked/Rel-18/38_series/38141-1/408c4798ea60469e0728a7cbbd598668_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e7d46d4d73424e69f3bee5b0215124203a4ee84 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/408c4798ea60469e0728a7cbbd598668_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01e1e7f26191dead2d547df3c306a33e8d6f9fa1fc9937a595010cf8aab4ae6a +size 32938 diff --git a/marked/Rel-18/38_series/38141-1/43cd26e92a1c09efb81d26db4787dcb6_img.jpg b/marked/Rel-18/38_series/38141-1/43cd26e92a1c09efb81d26db4787dcb6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e79bed95f79a05ee7f46e559ab0aea0a8a75bbc4 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/43cd26e92a1c09efb81d26db4787dcb6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16240bb19cf7fb6a5f4da93d48075bbc63efb853dff4243d85f8fa5f84e727c1 +size 61063 diff --git a/marked/Rel-18/38_series/38141-1/4405b71aa114882a0a9a7ef6dafa6da7_img.jpg b/marked/Rel-18/38_series/38141-1/4405b71aa114882a0a9a7ef6dafa6da7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ca91b736975188caab49a45655ed9267fa68f45 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/4405b71aa114882a0a9a7ef6dafa6da7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51974a3953f7432793ffd65619685697daedd93b43fe0a84f035c10f15809cba +size 45115 diff --git a/marked/Rel-18/38_series/38141-1/4621799daaf18ba4b3b6ada011a1ba10_img.jpg b/marked/Rel-18/38_series/38141-1/4621799daaf18ba4b3b6ada011a1ba10_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41ba9b54be8c50fb21f120b0408281119218b915 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/4621799daaf18ba4b3b6ada011a1ba10_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a24b7c04f7a067f31d548b55c463dee2a44311ef6181dbcacd92ade362fe942c +size 39915 diff --git a/marked/Rel-18/38_series/38141-1/46b1709f96fe48aa2b3395915d00a8ad_img.jpg b/marked/Rel-18/38_series/38141-1/46b1709f96fe48aa2b3395915d00a8ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..390a01a1c2b1798c83315b5d81083310a4b19ef8 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/46b1709f96fe48aa2b3395915d00a8ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7696e1470eb80832b16a2c48acb5aabb1bfe2ede33eb2efc27c5be06619172df +size 137687 diff --git a/marked/Rel-18/38_series/38141-1/49fafbd71e0dd98b8cf7b2db58559f01_img.jpg b/marked/Rel-18/38_series/38141-1/49fafbd71e0dd98b8cf7b2db58559f01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d9b7b3757a3788e8789a700c6cf392cb4d2e615 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/49fafbd71e0dd98b8cf7b2db58559f01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55686608772cbce944611056b2fa41df545aafb35170fe3f7d5a6b74633cdd77 +size 49052 diff --git a/marked/Rel-18/38_series/38141-1/4b4b9c9c016880edb872f25cefc85eb1_img.jpg b/marked/Rel-18/38_series/38141-1/4b4b9c9c016880edb872f25cefc85eb1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..137b361546094d3e9c986dafda1166d603d3e548 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/4b4b9c9c016880edb872f25cefc85eb1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea0eb449633fb7babbb158f4a340633319d47585f59dfd19eb299be076144781 +size 32977 diff --git a/marked/Rel-18/38_series/38141-1/4e774fb157e9d60398aa1a61b5c01f35_img.jpg b/marked/Rel-18/38_series/38141-1/4e774fb157e9d60398aa1a61b5c01f35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e308a7dc8a597d0ebf6dd19d9a3b1600cae326f2 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/4e774fb157e9d60398aa1a61b5c01f35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:508d2df0c17a7dd8b81f75e834c07d154b88310f882f92e632d6d4dff38e74a8 +size 38772 diff --git a/marked/Rel-18/38_series/38141-1/50391d55e6cee28152373f50742e9b9b_img.jpg b/marked/Rel-18/38_series/38141-1/50391d55e6cee28152373f50742e9b9b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04fedf8e1b9d1a38b7714771a148cb957539acb6 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/50391d55e6cee28152373f50742e9b9b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef2095dd45bc00cb27718f67264b5e1b6d06554494c3a9bef26ba8703708429a +size 20353 diff --git a/marked/Rel-18/38_series/38141-1/5be0a1a31ceab44c46b7f4ff2b369c9e_img.jpg b/marked/Rel-18/38_series/38141-1/5be0a1a31ceab44c46b7f4ff2b369c9e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3a7fa63babedafeff0048b7a5cb6d5387e454c9 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/5be0a1a31ceab44c46b7f4ff2b369c9e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bc9464f31e259d2e876fc7676d169d68d97f5252909e96a86298385d504d24a +size 61417 diff --git a/marked/Rel-18/38_series/38141-1/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38141-1/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ec7e5ffb0327e0a5bb5429a964441fb730c48c4 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ed68a221b9d150b6f05d1e70460bdbdb51ca835afecf50be229620d31813c5d +size 9330 diff --git a/marked/Rel-18/38_series/38141-1/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38141-1/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82c905d8723a73a55bacc0c6a01a39eff9be97dd --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:207dfb0c296db498788aefb6e306365a83e13aa838a97174b6522b410cf8c0a0 +size 5498 diff --git a/marked/Rel-18/38_series/38141-1/6656b8a5dfd7e3f7f7f0316de0481f1b_img.jpg b/marked/Rel-18/38_series/38141-1/6656b8a5dfd7e3f7f7f0316de0481f1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8091cd3abd641212d2a26547584c364dec46d88c --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/6656b8a5dfd7e3f7f7f0316de0481f1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dac854ec605da8ecf06d6ac52c1abfee5dfb6e4b9d4c77c89aa5d7c76bf72954 +size 32396 diff --git a/marked/Rel-18/38_series/38141-1/689d331d83fef38df69d4bb17c7ace6d_img.jpg b/marked/Rel-18/38_series/38141-1/689d331d83fef38df69d4bb17c7ace6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bde00d76aa24aa2fa32af742009ae342a66bfe08 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/689d331d83fef38df69d4bb17c7ace6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:741215b2672e92ebdc2a9d10ee0665c40c03feba565cad09baa8e75466d2aa11 +size 37095 diff --git a/marked/Rel-18/38_series/38141-1/6de875eb7a49c3352b45075b92e5ea9b_img.jpg b/marked/Rel-18/38_series/38141-1/6de875eb7a49c3352b45075b92e5ea9b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..689601b9b9a675a7bb5c3bb3f20555ae208641e9 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/6de875eb7a49c3352b45075b92e5ea9b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:318f35a4fc3b7727a90d043c47ad51609cb6b658052fe559894276dc82609b78 +size 37103 diff --git a/marked/Rel-18/38_series/38141-1/6eb451dee00e06ac8710c477f258463d_img.jpg b/marked/Rel-18/38_series/38141-1/6eb451dee00e06ac8710c477f258463d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4de49606c0d36e4796ea2544274888e6975b4c74 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/6eb451dee00e06ac8710c477f258463d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b38cde37f260f627d4e281043165165261c762bb554a1a599c242b56651d4a2 +size 41139 diff --git a/marked/Rel-18/38_series/38141-1/6f27cea0d83b6f1bc74e4f4fee27f4a4_img.jpg b/marked/Rel-18/38_series/38141-1/6f27cea0d83b6f1bc74e4f4fee27f4a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0cd57bfc86dfec9f373bfa278ae40a49923b17ee --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/6f27cea0d83b6f1bc74e4f4fee27f4a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86ebf1fcd4de88e1ca685b24b4a4205488e56ca05e50c4c4f8a7d34bc5480df6 +size 5629 diff --git a/marked/Rel-18/38_series/38141-1/71e9881885098f5d35adad3ffb6c4687_img.jpg b/marked/Rel-18/38_series/38141-1/71e9881885098f5d35adad3ffb6c4687_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7aa979f5558f7f7a099782650cd54c3f42f5580 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/71e9881885098f5d35adad3ffb6c4687_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:640265b5b0b7b2acd67cea2dc238f87fe58b0d0743dc292eb67a00ea84da5ef8 +size 41629 diff --git a/marked/Rel-18/38_series/38141-1/7804e53c30a2aabd89fa25b8c2f28e14_img.jpg b/marked/Rel-18/38_series/38141-1/7804e53c30a2aabd89fa25b8c2f28e14_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfbf9aa0149e11541d9a2deb398d6740a4f9d919 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/7804e53c30a2aabd89fa25b8c2f28e14_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94e8f2525b013bd3ca9e36bba6a6eb35adc1c2400ae473bb1214e2ea62019dd0 +size 5168 diff --git a/marked/Rel-18/38_series/38141-1/7e2d5e19c1a94ed931dd102da45f4f8f_img.jpg b/marked/Rel-18/38_series/38141-1/7e2d5e19c1a94ed931dd102da45f4f8f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e827a9e4ce2000e2e9004e8a07236bd4e0f69273 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/7e2d5e19c1a94ed931dd102da45f4f8f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91b5de3c1fd1a01e4cafe65e9c8a12cf0dd91a203f2689326ab415d67bb687ac +size 35071 diff --git a/marked/Rel-18/38_series/38141-1/87661c01f79c13b3ea49e7d3e9782c48_img.jpg b/marked/Rel-18/38_series/38141-1/87661c01f79c13b3ea49e7d3e9782c48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9501658fe6c9b66e3873b3d1b76641b8a7cc6b5 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/87661c01f79c13b3ea49e7d3e9782c48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c46cd0348192cb61e8f70fe5137bd1cb7adc7faf7bab4e76b006b445f061c0d4 +size 31340 diff --git a/marked/Rel-18/38_series/38141-1/888ca03f14a7d40e9cf34ed55778a679_img.jpg b/marked/Rel-18/38_series/38141-1/888ca03f14a7d40e9cf34ed55778a679_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2e4c17de3511550585a5c59e810154f23cf9a87 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/888ca03f14a7d40e9cf34ed55778a679_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eabe1da66350229bc0570c756eddea7029fd0c704bd45e940697003b8658eebc +size 32486 diff --git a/marked/Rel-18/38_series/38141-1/94e473ccc93bae938bf71dacb5e4727d_img.jpg b/marked/Rel-18/38_series/38141-1/94e473ccc93bae938bf71dacb5e4727d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62856c62e5993bdabe78a0279344ced99e384e38 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/94e473ccc93bae938bf71dacb5e4727d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b1722b37ee8718c738269bceafa5df6b88db33c6a520d9f6e77958561749773 +size 37456 diff --git a/marked/Rel-18/38_series/38141-1/9832c14a1af451896d75b69abc97654f_img.jpg b/marked/Rel-18/38_series/38141-1/9832c14a1af451896d75b69abc97654f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00201cc3a33c2c9b55e79b46f941de5de9b5458d --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/9832c14a1af451896d75b69abc97654f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a8ff7f4d5217063f740461acd661f5df5f2ad1b94c4edfd20779bafae896691 +size 5472 diff --git a/marked/Rel-18/38_series/38141-1/9c79df43d06f2243e8e0bb02eda0cdf6_img.jpg b/marked/Rel-18/38_series/38141-1/9c79df43d06f2243e8e0bb02eda0cdf6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be85f22087ea8bbadea572fc6f484181e99f16c9 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/9c79df43d06f2243e8e0bb02eda0cdf6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3d3731a1076ce6e1810713b286998d6f3b5a73f833b767a33754a0b6fafd557 +size 32580 diff --git a/marked/Rel-18/38_series/38141-1/9cf46aa4fa95213299ac07f37ed34ce9_img.jpg b/marked/Rel-18/38_series/38141-1/9cf46aa4fa95213299ac07f37ed34ce9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bed4511b9575fc5eae623f17fa34fd4569112f67 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/9cf46aa4fa95213299ac07f37ed34ce9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f16975965e23ee5f305eb9d2a6e7ea7268b9f6a59f23ea1a2c367646c6b83f2 +size 5482 diff --git a/marked/Rel-18/38_series/38141-1/9e23e88f57c8d963f343c29619ebdbf2_img.jpg b/marked/Rel-18/38_series/38141-1/9e23e88f57c8d963f343c29619ebdbf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a4dc1ac9a5cf78cfb425306ad67f228539a577c --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/9e23e88f57c8d963f343c29619ebdbf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:720e4d4394918334ce4ccfaab3e4da21217bc91e08ac96ff40b237ec51cda883 +size 33482 diff --git a/marked/Rel-18/38_series/38141-1/9f2de980bdf4633bdf738b33d2ed8ff1_img.jpg b/marked/Rel-18/38_series/38141-1/9f2de980bdf4633bdf738b33d2ed8ff1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e44c4e480927b8211612fac02610b2d1b4c745cd --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/9f2de980bdf4633bdf738b33d2ed8ff1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95ed6f27676e0393d577699908bdcc6262d3263f433326be1196a12b1d90f73b +size 25041 diff --git a/marked/Rel-18/38_series/38141-1/b5051df103b6f1292dae89e60d9a4790_img.jpg b/marked/Rel-18/38_series/38141-1/b5051df103b6f1292dae89e60d9a4790_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08a30f7da1b616522942927513b94e6b6295c337 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/b5051df103b6f1292dae89e60d9a4790_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:123d6f8d2ed4fcc6241557db71299bed0181091c772bbb04e8cc1c8742dfc1a1 +size 18085 diff --git a/marked/Rel-18/38_series/38141-1/b7fd98a4fcc4990a613abfc31c5bdb5e_img.jpg b/marked/Rel-18/38_series/38141-1/b7fd98a4fcc4990a613abfc31c5bdb5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29f34904b514bab3b5e3ea6024db838b0ad971de --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/b7fd98a4fcc4990a613abfc31c5bdb5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5884751797b24c5b14b69b48121241d46aaa2a792c530ba899bafef9485868f +size 33864 diff --git a/marked/Rel-18/38_series/38141-1/c05aca0e296f64ce88749630314a61c3_img.jpg b/marked/Rel-18/38_series/38141-1/c05aca0e296f64ce88749630314a61c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0963d61084a1ed6c99748209ace3b3c3b3136b3b --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/c05aca0e296f64ce88749630314a61c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e36dd30872f17296f70c5f1d465669e2f05a36edcb6c58c170c4af0831aab959 +size 38591 diff --git a/marked/Rel-18/38_series/38141-1/c291a9ff5dc662dd6c7d9f8a4e567235_img.jpg b/marked/Rel-18/38_series/38141-1/c291a9ff5dc662dd6c7d9f8a4e567235_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ffc8d3235102a313d19e547cfbcec2576e2074e --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/c291a9ff5dc662dd6c7d9f8a4e567235_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9db2eb04b56c7324b72d22ec8fa284902e00e08c978170cb1acb8ea0b9531f64 +size 13955 diff --git a/marked/Rel-18/38_series/38141-1/c5a20f7bae219fc4c31f7376b7eb11e1_img.jpg b/marked/Rel-18/38_series/38141-1/c5a20f7bae219fc4c31f7376b7eb11e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56f43d6f125250fb9c40207670fbc85680de7dba --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/c5a20f7bae219fc4c31f7376b7eb11e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa41c7ce8caba06315aa92eeda927d0df2b209b0efa7b8d43833dbbcf6f5d854 +size 30752 diff --git a/marked/Rel-18/38_series/38141-1/c9b6396dc9aa7e326dd536c39047fe28_img.jpg b/marked/Rel-18/38_series/38141-1/c9b6396dc9aa7e326dd536c39047fe28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfae446224996203fe9b5554ef975c674e149ea0 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/c9b6396dc9aa7e326dd536c39047fe28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98f936dd37fc9b020ab6f25f47ed63acf7ccbe0f21e2d156617b5aec7037e61f +size 37319 diff --git a/marked/Rel-18/38_series/38141-1/d3b965960ca88db8118f308a5be4cb75_img.jpg b/marked/Rel-18/38_series/38141-1/d3b965960ca88db8118f308a5be4cb75_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf105b76fe42fcc69dd9cc7b28dc96c3b4c4de93 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/d3b965960ca88db8118f308a5be4cb75_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8ab71f68bc1e6f26a73d1391a6d08b6f21432ec61732cde84a5ed46a17d1ff4 +size 56308 diff --git a/marked/Rel-18/38_series/38141-1/d4a2b8bf6c326b6d627c2a051d13f728_img.jpg b/marked/Rel-18/38_series/38141-1/d4a2b8bf6c326b6d627c2a051d13f728_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1143082bcfc0b6cc048d52cbf0512fa44639080 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/d4a2b8bf6c326b6d627c2a051d13f728_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1313353a3973a320bd265e5f1e97561d17fa988a263c654dc9458377aa5cdda8 +size 33984 diff --git a/marked/Rel-18/38_series/38141-1/d51c36816d3c1c3219454679a83120e1_img.jpg b/marked/Rel-18/38_series/38141-1/d51c36816d3c1c3219454679a83120e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a19256a20205a77907183d45a2437f89685e7ace --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/d51c36816d3c1c3219454679a83120e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c61338d059e2f087abd8e02df288477a950e047d7136dab2735ebb8245a3cdd0 +size 5737 diff --git a/marked/Rel-18/38_series/38141-1/d7a98a717edbc26ca1508aaab7a566f4_img.jpg b/marked/Rel-18/38_series/38141-1/d7a98a717edbc26ca1508aaab7a566f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4fbe4b770bd8349be4881c8d7069675bcd1d8ee6 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/d7a98a717edbc26ca1508aaab7a566f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aaf0659ba9a35e3d09bc00e691403d801612d8a60e65d8674817a59726269a51 +size 12678 diff --git a/marked/Rel-18/38_series/38141-1/df11b35ddcfb1f54dc4e92fb39797ac8_img.jpg b/marked/Rel-18/38_series/38141-1/df11b35ddcfb1f54dc4e92fb39797ac8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e927052a89d774a5b17d48095f4d1fc8839810d --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/df11b35ddcfb1f54dc4e92fb39797ac8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d631ed55eb0887959be9a1077995cfda1a4ce854f28126d5502d7184321613ef +size 41250 diff --git a/marked/Rel-18/38_series/38141-1/e70285b7d75f2ab0c351640618082c0d_img.jpg b/marked/Rel-18/38_series/38141-1/e70285b7d75f2ab0c351640618082c0d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1f6c8888257c710fb9cee063ba609398b66d64e --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/e70285b7d75f2ab0c351640618082c0d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef0e3becec571283a077230428ef9120a9396cb0fd78be46a284c8dc29a21889 +size 24532 diff --git a/marked/Rel-18/38_series/38141-1/e7511e4fa0a0df6c02eb793c62524690_img.jpg b/marked/Rel-18/38_series/38141-1/e7511e4fa0a0df6c02eb793c62524690_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6dac3ed1eff9adf849291e093938f6d85f72aff9 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/e7511e4fa0a0df6c02eb793c62524690_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc14a62f36d8ae3a20caaf096a9224e362bc60627e241082fa57eb6a942d4715 +size 28417 diff --git a/marked/Rel-18/38_series/38141-1/eb39abb910e46289d79b0f4ae52fc612_img.jpg b/marked/Rel-18/38_series/38141-1/eb39abb910e46289d79b0f4ae52fc612_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..039509f52b002f7e1e0025da359821c0f558e7f7 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/eb39abb910e46289d79b0f4ae52fc612_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d53197f977e3fdca75f4ae8b0429e288d0d186ae09989cade8b7e7d2a935017 +size 50862 diff --git a/marked/Rel-18/38_series/38141-1/eec8a7a6584d308ede104bddbf4dc7f3_img.jpg b/marked/Rel-18/38_series/38141-1/eec8a7a6584d308ede104bddbf4dc7f3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed4d2c8372b326f3c4192571c7effb8f710ce5e0 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/eec8a7a6584d308ede104bddbf4dc7f3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3aea329074b17e5992add6ef17d4fd29c134e04bddfa4498a62a11d879937b6f +size 29186 diff --git a/marked/Rel-18/38_series/38141-1/f288907445f0de048c603b6980c3db58_img.jpg b/marked/Rel-18/38_series/38141-1/f288907445f0de048c603b6980c3db58_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0a606e1bb5e851fe0e3e647e9ec93999fd43e87 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/f288907445f0de048c603b6980c3db58_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ffeaedaffa61b5473996d3c4a7b69280a71674582a62b4a70b8498f258bb91eb +size 49974 diff --git a/marked/Rel-18/38_series/38141-1/f6dcf82b673244b5b8c95616ca0d0556_img.jpg b/marked/Rel-18/38_series/38141-1/f6dcf82b673244b5b8c95616ca0d0556_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d41e73f9d91c5f2176b073b49fda801cd40650be --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/f6dcf82b673244b5b8c95616ca0d0556_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c26f1e84e648c5a189b93693e568567ef305f4ebd506ccf3ca640395dde65f0 +size 41469 diff --git a/marked/Rel-18/38_series/38141-1/f9dc060faad1fb842976b395498accd7_img.jpg b/marked/Rel-18/38_series/38141-1/f9dc060faad1fb842976b395498accd7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff5531b7adda144a869d89a60e4afd03b2af2f54 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/f9dc060faad1fb842976b395498accd7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6464a8ff9754be4c40a693f7ec6c502a36c517b1ff7beb82311384695d2b3171 +size 45063 diff --git a/marked/Rel-18/38_series/38141-1/fa534498004572deb292e53e11c13a3c_img.jpg b/marked/Rel-18/38_series/38141-1/fa534498004572deb292e53e11c13a3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e07bceee1bacb25d2b108866cfbb90fa97e4cadb --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/fa534498004572deb292e53e11c13a3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:626ce883e8b56aa84ce239fcd7f7de604920f9d69999227c528928e32dcc1e68 +size 49950 diff --git a/marked/Rel-18/38_series/38141-1/fd76efce549d3713543bb5ed9b023c2e_img.jpg b/marked/Rel-18/38_series/38141-1/fd76efce549d3713543bb5ed9b023c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b5e180e052a11f53798ac07f5f6cbd54aae6963 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/fd76efce549d3713543bb5ed9b023c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c76711c3a542f61a3474cd706f9262a773dc2482e8e3e9067ccd902064201aff +size 42793 diff --git a/marked/Rel-18/38_series/38141-1/fe958e930d35081b9a5616ebc6780d65_img.jpg b/marked/Rel-18/38_series/38141-1/fe958e930d35081b9a5616ebc6780d65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9a4b725835b1bbb0921d160bbba0af9853a5a52 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/fe958e930d35081b9a5616ebc6780d65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:255f9d6a00ad5d73e4b69ea01b9a21a0fbb262d2b134397aa4b1d75e12ab4313 +size 52402 diff --git a/marked/Rel-18/38_series/38141-1/raw.md b/marked/Rel-18/38_series/38141-1/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2d9e24c42114168295dd135974dc5cd8c79c2d43 --- /dev/null +++ b/marked/Rel-18/38_series/38141-1/raw.md @@ -0,0 +1,12891 @@ + + +# 3GPP TS 38.141-1 V18.4.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; 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 text 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. + +© 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..... | 16 | +| 1 Scope..... | 18 | +| 2 References..... | 18 | +| 3 Definitions, symbols and abbreviations..... | 20 | +| 3.1 Definitions..... | 20 | +| 3.2 Symbols..... | 22 | +| 3.3 Abbreviations..... | 24 | +| 4 General conducted test conditions and declarations..... | 26 | +| 4.1 Measurement uncertainties and test requirements..... | 26 | +| 4.1.1 General..... | 26 | +| 4.1.2 Acceptable uncertainty of Test System..... | 26 | +| 4.1.2.1 General..... | 26 | +| 4.1.2.2 Measurement of transmitter..... | 27 | +| 4.1.2.3 Measurement of receiver..... | 29 | +| 4.1.2.4 Measurement of performance requirements..... | 33 | +| 4.1.3 Interpretation of measurement results..... | 33 | +| 4.2 Conducted requirement reference points..... | 33 | +| 4.2.1 BS type 1-C ..... | 33 | +| 4.2.2 BS type 1-H ..... | 34 | +| 4.3 Base station classes..... | 35 | +| 4.4 Regional requirements..... | 35 | +| 4.5 BS configurations..... | 37 | +| 4.5.1 BS type 1-C ..... | 37 | +| 4.5.1.1 Transmit configurations..... | 37 | +| 4.5.1.1.1 General..... | 37 | +| 4.5.1.1.2 Transmission with multiple transmitter antenna connectors..... | 37 | +| 4.5.1.2 Receive configurations..... | 37 | + +| | | | +|-----------|------------------------------------------------------------------------------|----| +| 4.5.1.2.1 | General..... | 37 | +| 4.5.1.2.2 | Reception with multiple receiver antenna connectors, receiver diversity..... | 38 | +| 4.5.1.3 | Duplexers..... | 38 | +| 4.5.1.4 | Power supply options..... | 38 | +| 4.5.1.5 | Ancillary RF amplifiers..... | 38 | +| 4.5.2 | BS type I-H ..... | 39 | +| 4.5.2.1 | Transmit configurations..... | 39 | +| 4.5.2.2 | Receive configurations..... | 40 | +| 4.5.2.3 | Power supply options..... | 40 | +| 4.5.3 | BS with integrated Iuant BS modem..... | 41 | +| 4.6 | Manufacturer declarations..... | 41 | +| 4.7 | Test configurations..... | 47 | +| 4.7.1 | General..... | 47 | +| 4.7.2 | Test signal used to build Test Configurations..... | 48 | +| 4.7.3 | NRTC1: Contiguous spectrum operation..... | 48 | +| 4.7.3.1 | NRTC1 generation..... | 48 | +| 4.7.3.2 | NRTC1 power allocation..... | 48 | +| 4.7.4 | NRTC2: Contiguous CA occupied bandwidth..... | 48 | +| 4.7.4.1 | NRTC2 generation..... | 48 | +| 4.7.4.2 | NRTC2 power allocation..... | 49 | +| 4.7.5 | NRTC3: Non-contiguous spectrum operation..... | 49 | +| 4.7.5.1 | NRTC3 generation..... | 49 | +| 4.7.5.2 | NRTC3 power allocation..... | 50 | +| 4.7.6 | NRTC4: Multi-band test configuration for full carrier allocation..... | 50 | +| 4.7.6.1 | NRTC4 generation..... | 50 | +| 4.7.6.2 | NRTC4 power allocation..... | 50 | +| 4.7.7 | NRTC5: Multi-band test configuration with high PSD per carrier..... | 50 | +| 4.7.7.1 | NRTC5 generation..... | 51 | +| 4.7.7.2 | NRTC5 power allocation..... | 51 | +| 4.7.8 | NRTC6: Non-contiguous spectrum operation in band n46, n96 and n102..... | 51 | + +| | | | +|------------|---------------------------------------------------------------------|----| +| 4.7.8.1 | NRTC6 generation..... | 51 | +| 4.7.8.2 | NRTC6 power allocation..... | 52 | +| 4.8 | Applicability of requirements..... | 52 | +| 4.8.1 | General..... | 52 | +| 4.8.2 | Requirement set applicability..... | 52 | +| 4.8.3 | Applicability of test configurations for single-band operation..... | 52 | +| 4.8.4 | Applicability of test configurations for multi-band operation..... | 54 | +| 4.8.5 | Additional conformance..... | 55 | +| 4.9 | RF channels and test models..... | 55 | +| 4.9.1 | RF channels..... | 55 | +| 4.9.2 | Test models..... | 56 | +| 4.9.2.1 | General..... | 56 | +| 4.9.2.2 | FR1 test models..... | 56 | +| 4.9.2.2.1 | FR1 test model 1.1 (NR-FR1-TM1.1)..... | 58 | +| 4.9.2.2.2 | FR1 test model 1.2 (NR-FR1-TM1.2)..... | 59 | +| 4.9.2.2.3 | FR1 test model 2 (NR-FR1-TM2)..... | 59 | +| 4.9.2.2.4 | FR1 test model 2a (NR-FR1-TM2a)..... | 60 | +| 4.9.2.2.4A | FR1 test model 2b (NR-FR1-TM2b)..... | 60 | +| 4.9.2.2.5 | FR1 test model 3.1 (NR-FR1-TM3.1)..... | 60 | +| 4.9.2.2.6 | FR1 test model 3.1a (NR-FR1-TM3.1a)..... | 61 | +| 4.9.2.2.6A | FR1 test model 3.1b (NR-FR1-TM3.1b)..... | 61 | +| 4.9.2.2.7 | FR1 test model 3.2 (NR-FR1-TM3.2)..... | 61 | +| 4.9.2.2.8 | FR1 test model 3.3 (NR-FR1-TM3.3)..... | 62 | +| 4.9.2.2.9 | NB-IoT operation in NR in-band test model (NR-N-TM)..... | 63 | +| 4.9.2.3 | Data content of Physical channels and Signals for NR-FR1-TM..... | 63 | +| 4.9.2.3.1 | PDCCH..... | 63 | +| 4.9.2.3.2 | PDSCH..... | 64 | +| 4.9.2.4 | Data content of Physical channels and Signals for NR-N-TM..... | 65 | +| 4.9.3 | NB-IoT testing..... | 65 | +| 4.10 | Requirements for contiguous and non-contiguous spectrum..... | 65 | + +| | | | +|-----------|----------------------------------------------------------|----| +| 4.11 | Requirements for BS capable of multi-band operation..... | 66 | +| 4.12 | Format and interpretation of tests..... | 66 | +| 5 | Operating bands and channel arrangement..... | 68 | +| 6 | Conducted transmitter characteristics..... | 69 | +| 6.1 | General..... | 69 | +| 6.1.1 | BS type 1-C..... | 69 | +| 6.1.2 | BS type 1-H..... | 69 | +| 6.2 | Base station output power..... | 69 | +| 6.2.1 | Definition and applicability..... | 69 | +| 6.2.2 | Minimum requirement..... | 70 | +| 6.2.3 | Test purpose..... | 70 | +| 6.2.4 | Method of test..... | 71 | +| 6.2.4.1 | Initial conditions..... | 71 | +| 6.2.4.2 | Procedure..... | 71 | +| 6.2.5 | Test requirement..... | 71 | +| 6.3 | Output power dynamics..... | 72 | +| 6.3.1 | General..... | 72 | +| 6.3.2 | RE power control dynamic range..... | 72 | +| 6.3.2.1 | Definition and applicability..... | 72 | +| 6.3.2.2 | Minimum requirement..... | 72 | +| 6.3.2.3 | Test purpose..... | 72 | +| 6.3.3 | Total power dynamic range..... | 72 | +| 6.3.3.1 | Definition and applicability..... | 72 | +| 6.3.3.2 | Minimum requirement..... | 72 | +| 6.3.3.3 | Test purpose..... | 73 | +| 6.3.3.4 | Method of test..... | 73 | +| 6.3.3.4.1 | Initial conditions..... | 73 | +| 6.3.3.4.2 | Procedure..... | 73 | +| 6.3.3.5 | Test requirements..... | 73 | + +| | | | +|-----------|------------------------------------|----| +| 6.3.4 | NB-IoT RB power dynamic range..... | 74 | +| 6.3.4.1 | Definition and applicability..... | 74 | +| 6.3.4.2 | Minimum requirement..... | 74 | +| 6.3.4.3 | Test purpose..... | 74 | +| 6.3.4.4 | Method of test..... | 74 | +| 6.3.4.5 | Test requirements..... | 74 | +| 6.4 | Transmit ON/OFF power..... | 75 | +| 6.4.1 | Transmitter OFF power..... | 75 | +| 6.4.1.1 | Definition and applicability..... | 75 | +| 6.4.1.2 | Minimum requirement..... | 75 | +| 6.4.1.3 | Test purpose..... | 75 | +| 6.4.1.4 | Method of test..... | 75 | +| 6.4.1.5 | Test requirements..... | 75 | +| 6.4.2 | Transmitter transient period..... | 76 | +| 6.4.2.1 | Definition and applicability..... | 76 | +| 6.4.2.2 | Minimum requirement..... | 76 | +| 6.4.2.3 | Test purpose..... | 76 | +| 6.4.2.4 | Method of test..... | 76 | +| 6.4.2.4.1 | Initial conditions..... | 76 | +| 6.4.2.4.2 | Procedure..... | 77 | +| 6.4.2.5 | Test requirements..... | 77 | +| 6.5 | Transmitted signal quality..... | 77 | +| 6.5.1 | General..... | 77 | +| 6.5.2 | Frequency error..... | 78 | +| 6.5.2.1 | Definition and applicability..... | 78 | +| 6.5.2.2 | Minimum Requirement..... | 78 | +| 6.5.2.3 | Test purpose..... | 78 | +| 6.5.2.4 | Method of test..... | 78 | +| 6.5.2.5 | Test Requirements..... | 78 | +| 6.5.3 | Modulation quality..... | 78 | + +| | | | +|-----------|--------------------------------------------------|----| +| 6.5.3.1 | Definition and applicability..... | 78 | +| 6.5.3.2 | Minimum Requirement..... | 78 | +| 6.5.3.3 | Test purpose..... | 79 | +| 6.5.3.4 | Method of test..... | 79 | +| 6.5.3.4.1 | Initial conditions..... | 79 | +| 6.5.3.4.2 | Procedure..... | 79 | +| 6.5.3.5 | Test requirements..... | 80 | +| 6.5.4 | Time alignment error..... | 82 | +| 6.5.4.1 | Definition and applicability..... | 82 | +| 6.5.4.2 | Minimum requirement..... | 82 | +| 6.5.4.3 | Test purpose..... | 82 | +| 6.5.4.4 | Method of test..... | 82 | +| 6.5.4.4.1 | Initial conditions..... | 82 | +| 6.5.4.4.2 | Procedure..... | 82 | +| 6.5.4.5 | Test requirement..... | 83 | +| 6.6 | Unwanted emissions..... | 83 | +| 6.6.1 | General..... | 83 | +| 6.6.2 | Occupied bandwidth..... | 84 | +| 6.6.2.1 | Definition and applicability..... | 84 | +| 6.6.2.2 | Minimum Requirements..... | 84 | +| 6.6.2.3 | Test purpose..... | 84 | +| 6.6.2.4 | Method of test..... | 85 | +| 6.6.2.4.1 | Initial conditions..... | 85 | +| 6.6.2.4.2 | Procedure..... | 85 | +| 6.6.2.5 | Test requirements..... | 86 | +| 6.6.3 | Adjacent Channel Leakage Power Ratio (ACLR)..... | 86 | +| 6.6.3.1 | Definition and applicability..... | 86 | +| 6.6.3.2 | Minimum requirement..... | 86 | +| 6.6.3.3 | Test purpose..... | 86 | +| 6.6.3.4 | Method of test..... | 86 | + +| | | | +|-------------|----------------------------------------------------------------------------------------------------|-----| +| 6.6.3.4.1 | Initial conditions..... | 86 | +| 6.6.3.4.2 | Procedure..... | 87 | +| 6.6.3.5 | Test requirements..... | 87 | +| 6.6.3.5.1 | General requirements..... | 87 | +| 6.6.3.5.2 | Limits and basic limits ..... | 87 | +| 6.6.3.5.3 | BS type 1-C ..... | 91 | +| 6.6.3.5.4 | BS type 1-H..... | 91 | +| 6.6.4 | Operating band unwanted emissions..... | 92 | +| 6.6.4.1 | Definition and applicability..... | 92 | +| 6.6.4.2 | Minimum requirement..... | 93 | +| 6.6.4.3 | Test purpose..... | 93 | +| 6.6.4.4 | Method of test..... | 94 | +| 6.6.4.4.1 | Initial conditions..... | 94 | +| 6.6.4.4.2 | Procedure..... | 94 | +| 6.6.4.5 | Test requirements..... | 95 | +| 6.6.4.5.1 | General requirements..... | 95 | +| 6.6.4.5.2 | Basic limits for Wide Area BS (Category A)..... | 95 | +| 6.6.4.5.3 | Basic limits for Wide Area BS (Category B)..... | 96 | +| 6.6.4.5.3.1 | Category B requirements (Option 1)..... | 96 | +| 6.6.4.5.3.2 | Category B requirements (Option 2)..... | 98 | +| 6.6.4.5.4 | Basic limits for Medium Range BS (Category A and B)..... | 99 | +| 6.6.4.5.5 | Basic limits for Local Area BS (Category A and B)..... | 103 | +| 6.6.4.5.5A | Basic limits for Local Area and Medium Range BS for band n46, n96 and n102 (Category A and B)..... | 105 | +| 6.6.4.5.6 | Basic limits for additional requirements..... | 108 | +| 6.6.4.5.6.1 | Limits in FCC Title 47..... | 108 | +| 6.6.4.5.6.2 | Protection of DTT..... | 108 | +| 6.6.4.5.6.3 | Additional operating band unwanted emissions limits for Band n48..... | 108 | +| 6.6.4.5.6.4 | Additional operating band unwanted emissions limits for Band n53..... | 108 | +| 6.6.4.5.6.5 | Protection of GPS..... | 109 | +| 6.6.4.5.7 | BS type 1-C ..... | 110 | + +| | | | +|-------------|-----------------------------------------------------------|-----| +| 6.6.4.5.8 | BS type 1-H ..... | 110 | +| 6.6.5 | Transmitter spurious emissions..... | 110 | +| 6.6.5.1 | Definition and applicability..... | 110 | +| 6.6.5.2 | Minimum requirement..... | 111 | +| 6.6.5.3 | Test purpose..... | 111 | +| 6.6.5.4 | Method of test..... | 111 | +| 6.6.5.4.1 | Initial conditions..... | 111 | +| 6.6.5.4.2 | Procedure..... | 111 | +| 6.6.5.5 | Test requirements..... | 112 | +| 6.6.5.5.1 | Basic limits..... | 112 | +| 6.6.5.5.1.1 | Tx spurious emissions..... | 112 | +| 6.6.5.5.1.2 | Protection of the BS receiver of own or different BS..... | 113 | +| 6.6.5.5.1.3 | Additional spurious emissions requirements..... | 113 | +| 6.6.5.5.1.4 | Co-location with other base stations..... | 124 | +| 6.6.5.5.2 | (void)..... | 130 | +| 6.6.5.5.3 | BS type 1-C ..... | 130 | +| 6.6.5.5.4 | BS type 1-H ..... | 130 | +| 6.7 | Transmitter intermodulation..... | 130 | +| 6.7.1 | Definition and applicability..... | 130 | +| 6.7.2 | Minimum requirement..... | 131 | +| 6.7.3 | Test purpose..... | 131 | +| 6.7.4 | Method of test..... | 131 | +| 6.7.4.1 | Initial conditions..... | 131 | +| 6.7.4.2 | Procedure..... | 131 | +| 6.7.5 | Test requirements..... | 132 | +| 6.7.5.1 | BS type 1-C ..... | 132 | +| 6.7.5.1.1 | Co-location minimum requirements..... | 132 | +| 6.7.5.1.2 | Additional requirements..... | 133 | +| 6.7.5.2 | BS type 1-H ..... | 134 | +| 6.7.5.2.1 | Co-location minimum requirements..... | 134 | + +| | | | +|-----------|-----------------------------------------|-----| +| 6.7.5.2.2 | Intra-system minimum requirements..... | 134 | +| 6.7.5.2.3 | Additional requirements..... | 135 | +| 7 | Conducted receiver characteristics..... | 136 | +| 7.1 | General..... | 136 | +| 7.2 | Reference sensitivity level..... | 136 | +| 7.2.1 | Definition and applicability..... | 136 | +| 7.2.2 | Minimum requirement..... | 136 | +| 7.2.3 | Test purpose..... | 137 | +| 7.2.4 | Method of test..... | 137 | +| 7.2.4.1 | Initial conditions..... | 137 | +| 7.2.4.2 | Procedure..... | 137 | +| 7.2.5 | Test requirements..... | 137 | +| 7.3 | Dynamic range..... | 142 | +| 7.3.1 | Definition and applicability..... | 142 | +| 7.3.2 | Minimum requirement..... | 142 | +| 7.3.3 | Test purpose..... | 143 | +| 7.3.4 | Method of test..... | 143 | +| 7.3.4.1 | Initial conditions..... | 143 | +| 7.3.4.2 | Procedure..... | 143 | +| 7.3.5 | Test requirements..... | 143 | +| 7.4 | In-band selectivity and blocking..... | 155 | +| 7.4.1 | Adjacent Channel Selectivity (ACS)..... | 155 | +| 7.4.1.1 | Definition and applicability..... | 155 | +| 7.4.1.2 | Minimum requirement..... | 155 | +| 7.4.1.3 | Test purpose..... | 155 | +| 7.4.1.4 | Method of test..... | 156 | +| 7.4.1.4.1 | Initial conditions..... | 156 | +| 7.4.1.4.2 | Procedure..... | 156 | +| 7.4.1.5 | Test requirements..... | 156 | +| 7.4.2 | In-band blocking..... | 158 | + +| | | | +|-----------|---------------------------------------------------------------|-----| +| 7.4.2.1 | Definition and applicability..... | 158 | +| 7.4.2.2 | Minimum requirement..... | 159 | +| 7.4.2.3 | Test purpose..... | 159 | +| 7.4.2.4 | Method of test..... | 159 | +| 7.4.2.4.1 | Initial conditions..... | 159 | +| 7.4.2.4.2 | Procedure for general blocking..... | 159 | +| 7.4.2.4.3 | Procedure for narrowband blocking..... | 160 | +| 7.4.2.5 | Test requirements..... | 160 | +| 7.4.2.5.1 | Additional narrowband blocking requirement for Band n100..... | 164 | +| 7.5 | Out-of-band blocking..... | 165 | +| 7.5.1 | Definition and applicability..... | 165 | +| 7.5.2 | Minimum requirement..... | 165 | +| 7.5.3 | Test purpose..... | 165 | +| 7.5.4 | Method of test..... | 165 | +| 7.5.4.1 | Initial conditions..... | 165 | +| 7.5.4.2 | Procedure..... | 165 | +| 7.5.5 | Test requirements..... | 166 | +| 7.5.5.1 | General requirements..... | 166 | +| 7.5.5.2 | Co-location requirements..... | 167 | +| 7.5.5.3 | Additional requirement..... | 168 | +| 7.5.5.3.1 | Additional requirement for Band n101..... | 168 | +| 7.6 | Receiver spurious emissions..... | 168 | +| 7.6.1 | Definition and applicability..... | 168 | +| 7.6.2 | Minimum requirement..... | 169 | +| 7.6.3 | Test purpose..... | 169 | +| 7.6.4 | Method of test..... | 169 | +| 7.6.4.1 | Initial conditions..... | 169 | +| 7.6.4.2 | Procedure..... | 169 | +| 7.6.5 | Test requirements..... | 170 | +| 7.6.5.1 | Basic limits..... | 170 | + +| | | | +|-----------|-------------------------------------------------------------------------------------|-----| +| 7.6.5.2 | BS type 1-C..... | 171 | +| 7.6.5.3 | BS type 1-H..... | 171 | +| 7.7 | Receiver intermodulation..... | 171 | +| 7.7.1 | Definition and applicability..... | 171 | +| 7.7.2 | Minimum requirement..... | 171 | +| 7.7.3 | Test purpose..... | 171 | +| 7.7.4 | Method of test..... | 171 | +| 7.7.4.1 | Initial conditions..... | 171 | +| 7.7.4.2 | Procedure..... | 172 | +| 7.7.5 | Test requirements..... | 172 | +| 7.7.5.1 | Additional narrowband intermodulation requirement for Band n100..... | 178 | +| 7.8 | In-channel selectivity..... | 178 | +| 7.8.1 | Definition and applicability..... | 178 | +| 7.8.2 | Minimum requirement..... | 178 | +| 7.8.3 | Test purpose..... | 178 | +| 7.8.4 | Method of test..... | 179 | +| 7.8.4.1 | Initial conditions..... | 179 | +| 7.8.4.2 | Procedure..... | 179 | +| 7.8.5 | Test requirements..... | 179 | +| 8 | Conducted performance characteristics..... | 190 | +| 8.1 | General..... | 190 | +| 8.1.1 | Scope and definitions..... | 190 | +| 8.1.2 | Applicability rule..... | 191 | +| 8.1.2.0 | General..... | 191 | +| 8.1.2.1 | Applicability of PUSCH performance requirements..... | 191 | +| 8.1.2.1.1 | Applicability of requirements for different subcarrier spacings..... | 191 | +| 8.1.2.1.2 | Applicability of requirements for different channel bandwidths..... | 191 | +| 8.1.2.1.3 | Applicability of requirements for different configurations..... | 191 | +| 8.1.2.1.7 | Applicability of 2-step RA type requirements for different subcarrier spacings..... | 192 | +| 8.1.2.1.8 | Applicability of PUSCH with 0.001% BLER requirements..... | 192 | + +| | | | +|-----------|-----------------------------------------------------------------------------------------------|-----| +| 8.1.2.1.9 | Applicability of PUSCH repetition type A requirements..... | 192 | +| 8.1.2.2 | Applicability of PUCCH performance requirements..... | 192 | +| 8.1.2.2.1 | Applicability of requirements for different formats..... | 192 | +| 8.1.2.2.2 | Applicability of requirements for different subcarrier spacings..... | 192 | +| 8.1.2.2.3 | Applicability of requirements for different channel bandwidths..... | 192 | +| 8.1.2.2.4 | Applicability of requirements for different configurations..... | 192 | +| 8.1.2.2.5 | Applicability of requirements for multi-slot PUCCH..... | 193 | +| 8.1.2.2.6 | Applicability of requirements for PUCCH sub-slot based repetition..... | 193 | +| 8.1.2.3 | Applicability of PRACH performance requirements..... | 193 | +| 8.1.2.3.1 | Applicability of requirements for different formats..... | 193 | +| 8.1.2.3.2 | Applicability of requirements for different subcarrier spacings..... | 193 | +| 8.1.2.3.3 | Applicability of requirements for different channel bandwidths..... | 193 | +| 8.1.2.3.4 | Applicability of requirements for different restricted set types of long PRACH format 0..... | 193 | +| 8.1.2.4 | Applicability of PUSCH for high speed train performance requirements..... | 193 | +| 8.1.2.4.1 | Applicability of requirements for different speeds..... | 193 | +| 8.1.2.4.2 | Applicability of requirements for 1T1R..... | 193 | +| 8.1.2.5 | Applicability of interlaced PUSCH performance requirements..... | 194 | +| 8.1.2.5.1 | General applicability of interlaced PUSCH performance requirements..... | 194 | +| 8.1.2.5.2 | Applicability of requirements for different subcarrier spacings..... | 194 | +| 8.1.2.5.3 | Applicability of requirements for different channel bandwidths..... | 194 | +| 8.1.2.5.4 | Applicability of requirements for different configurations..... | 194 | +| 8.1.2.5.5 | Applicability of CG-UCI multiplexed on PUSCH requirements..... | 194 | +| 8.1.2.6 | Applicability of interlaced PUCCH performance requirements..... | 194 | +| 8.1.2.6.1 | General applicability of interlaced PUCCH performance requirements..... | 194 | +| 8.1.2.6.2 | Applicability of requirements for different formats..... | 194 | +| 8.1.2.6.3 | Applicability of requirements for different subcarrier spacings..... | 194 | +| 8.1.2.6.4 | Applicability of requirements for different channel bandwidths..... | 195 | +| 8.1.2.7 | Applicability of performance requirements for PRACH with $L_{RA}=1151$ and $L_{RA}=571$ ..... | 195 | +| 8.1.2.7.1 | Applicability of requirements for different formats..... | 195 | +| 8.1.2.7.2 | Applicability of requirements for different subcarrier spacings..... | 195 | + +| | | | +|------------|-----------------------------------------------------------------------------------|-----| +| 8.1.2.7.3 | Applicability of requirements for different channel bandwidths..... | 195 | +| 8.1.2.8 | Applicability of performance requirements for PUSCH with TB over Multi-Slots..... | 195 | +| 8.1.2.8.1 | Applicability of requirements for different UL-DL patterns..... | 195 | +| 8.1.2.9 | Applicability of performance requirements for PUSCH with DM-RS bundling..... | 195 | +| 8.1.2.9.1 | Applicability of requirements for TDD with different subcarrier spacings..... | 195 | +| 8.1.2.9.2 | Applicability of requirements for TDD with different UL-DL patterns..... | 195 | +| 8.1.2.9.3 | Applicability of requirements for different receiver antenna connectors..... | 196 | +| 8.1.2.10 | Applicability of performance requirements for PUCCH with DM-RS bundling..... | 196 | +| 8.1.2.10.1 | Applicability of requirements for TDD with different subcarrier spacings..... | 196 | +| 8.1.2.10.2 | Applicability of requirements for TDD with different UL-DL patterns..... | 196 | +| 8.2 | Performance requirements for PUSCH..... | 196 | +| 8.2.1 | Performance requirements for PUSCH with transform precoding disabled..... | 196 | +| 8.2.1.1 | Definition and applicability..... | 196 | +| 8.2.1.2 | Minimum Requirement..... | 196 | +| 8.2.1.3 | Test Purpose..... | 196 | +| 8.2.1.4 | Method of test..... | 196 | +| 8.2.1.4.1 | Initial Conditions..... | 196 | +| 8.2.1.4.2 | Procedure..... | 197 | +| 8.2.1.5 | Test Requirement..... | 198 | +| 8.2.2 | Performance requirements for PUSCH with transform precoding enabled..... | 205 | +| 8.2.2.1 | Definition and applicability..... | 205 | +| 8.2.2.2 | Minimum Requirement..... | 205 | +| 8.2.2.3 | Test Purpose..... | 205 | +| 8.2.2.4 | Method of test..... | 205 | +| 8.2.2.4.1 | Initial Conditions..... | 205 | +| 8.2.2.4.2 | Procedure..... | 206 | +| 8.2.2.5 | Test Requirement..... | 207 | +| 8.2.3 | Performance requirements for UCI multiplexed on PUSCH..... | 207 | +| 8.2.3.1 | Definition and applicability..... | 207 | +| 8.2.3.2 | Minimum Requirements..... | 208 | + +| | | | +|-----------|--------------------------------------------------------------|-----| +| 8.2.3.3 | Test purpose..... | 208 | +| 8.2.3.4 | Method of test..... | 208 | +| 8.2.3.4.1 | Initial conditions..... | 208 | +| 8.2.3.4.2 | Procedure..... | 208 | +| 8.2.3.5 | Test Requirement..... | 209 | +| 8.2.4 | Performance requirements for PUSCH for high speed train..... | 210 | +| 8.2.4.1 | Definition and applicability..... | 210 | +| 8.2.4.2 | Minimum Requirement..... | 210 | +| 8.2.4.3 | Test Purpose..... | 210 | +| 8.2.4.4 | Method of test..... | 211 | +| 8.2.4.4.1 | Initial Conditions..... | 211 | +| 8.2.4.4.2 | Procedure..... | 211 | +| 8.2.4.5 | Test Requirement..... | 212 | +| 8.2.5 | Performance requirements for UL timing adjustment..... | 215 | +| 8.2.5.1 | Definition and applicability..... | 215 | +| 8.2.5.2 | Minimum Requirement..... | 215 | +| 8.2.5.3 | Test Purpose..... | 215 | +| 8.2.5.4 | Method of test..... | 215 | +| 8.2.5.4.1 | Initial Conditions..... | 215 | +| 8.2.5.4.2 | Procedure..... | 215 | +| 8.2.5.5 | Test Requirement for High Speed Train..... | 218 | +| 8.2.6 | Performance requirements for PUSCH with 0.001% BLER..... | 219 | +| 8.2.6.1 | Definition and applicability..... | 219 | +| 8.2.6.2 | Minimum Requirement..... | 219 | +| 8.2.6.3 | Test Purpose..... | 219 | +| 8.2.6.4 | Method of test..... | 219 | +| 8.2.6.4.1 | Initial Conditions..... | 219 | +| 8.2.6.4.2 | Procedure..... | 219 | +| 8.2.6.5 | Test Requirement..... | 220 | +| 8.2.7 | Performance requirements for PUSCH repetition Type A..... | 221 | + +| | | | +|------------|-----------------------------------------------------------------------------------|-----| +| 8.2.7.1 | Definition and applicability..... | 221 | +| 8.2.7.2 | Minimum Requirement..... | 222 | +| 8.2.7.3 | Test Purpose..... | 222 | +| 8.2.7.4 | Method of test..... | 222 | +| 8.2.7.4.1 | Initial Conditions..... | 222 | +| 8.2.7.4.2 | Procedure..... | 222 | +| 8.2.7.5 | Test Requirement..... | 223 | +| 8.2.8 | Performance requirements for PUSCH Mapping Type B with non-slot transmission..... | 225 | +| 8.2.8.1 | Definition and applicability..... | 225 | +| 8.2.8.2 | Minimum Requirement..... | 225 | +| 8.2.8.3 | Test Purpose..... | 225 | +| 8.2.8.4 | Method of test..... | 225 | +| 8.2.8.4.1 | Initial Conditions..... | 225 | +| 8.2.8.4.2 | Procedure..... | 225 | +| 8.2.8.5 | Test Requirement..... | 226 | +| 8.2.9 | Performance requirements for PUSCH msgA for 2-step RA type..... | 227 | +| 8.2.9.1 | Definition and applicability..... | 227 | +| 8.2.9.2 | Minimum Requirement..... | 227 | +| 8.2.9.3 | Test Purpose..... | 227 | +| 8.2.9.4 | Method of test..... | 227 | +| 8.2.9.4.1 | Initial Conditions..... | 227 | +| 8.2.9.4.2 | Procedure..... | 227 | +| 8.2.9.5 | Test Requirement..... | 229 | +| 8.2.10 | Requirements for interlaced PUSCH..... | 230 | +| 8.2.10.1 | Definition and applicability..... | 230 | +| 8.2.10.2 | Minimum Requirement..... | 230 | +| 8.2.10.3 | Test Purpose..... | 231 | +| 8.2.10.4 | Method of test..... | 231 | +| 8.2.10.4.1 | Initial Conditions..... | 231 | +| 8.2.10.4.2 | Procedure..... | 231 | + +| | | | +|------------|-------------------------------------------------------------------------------|-----| +| 8.2.10.5 | Test Requirement..... | 232 | +| 8.2.11 | Performance requirements for CG-UCI multiplexed on interlaced PUSCH..... | 233 | +| 8.2.11.1 | Definition and applicability..... | 233 | +| 8.2.11.2 | Minimum Requirements..... | 233 | +| 8.2.11.3 | Test purpose..... | 234 | +| 8.2.11.4 | Method of test..... | 234 | +| 8.2.11.4.1 | Initial conditions..... | 234 | +| 8.2.11.4.2 | Procedure..... | 234 | +| 8.2.11.5 | Test Requirement..... | 235 | +| 8.2.12 | Performance requirements for TB processing over multi-slot PUSCH (TBoMS)..... | 236 | +| 8.2.12.1 | Definition and applicability..... | 236 | +| 8.2.12.2 | Minimum Requirement..... | 236 | +| 8.2.12.3 | Test Purpose..... | 236 | +| 8.2.12.4 | Method of test..... | 236 | +| 8.2.12.4.1 | Initial Conditions..... | 236 | +| 8.2.12.4.2 | Procedure..... | 237 | +| 8.2.12.5 | Test Requirement..... | 238 | +| 8.2.13 | Performance requirements for PUSCH with DMRS bundling..... | 239 | +| 8.2.13.1 | Definition and applicability..... | 239 | +| 8.2.13.2 | Minimum Requirement..... | 239 | +| 8.2.13.3 | Test Purpose..... | 239 | +| 8.2.13.4 | Method of test..... | 239 | +| 8.2.13.4.1 | Initial Conditions..... | 239 | +| 8.2.13.4.2 | Procedure..... | 239 | +| 8.2.13.5 | Test Requirement..... | 240 | +| 8.3 | Performance requirements for PUCCH..... | 242 | +| 8.3.1 | Performance requirements for PUCCH format 0..... | 242 | +| 8.3.1.1 | Definition and applicability..... | 242 | +| 8.3.1.2 | Minimum Requirement..... | 243 | +| 8.3.1.3 | Test purpose..... | 243 | + +| | | | +|-------------|--------------------------------------------------|-----| +| 8.3.1.4 | Method of test..... | 243 | +| 8.3.1.4.1 | Initial conditions..... | 243 | +| 8.3.1.4.2 | Procedure..... | 243 | +| 8.3.1.5 | Test Requirement..... | 244 | +| 8.3.2 | Performance requirements for PUCCH format 1..... | 245 | +| 8.3.2.1 | NACK to ACK detection..... | 245 | +| 8.3.2.1.1 | Definition and applicability..... | 245 | +| 8.3.2.1.2 | Minimum Requirement..... | 245 | +| 8.3.2.1.3 | Test purpose..... | 245 | +| 8.3.2.1.4 | Method of test..... | 245 | +| 8.3.2.1.4.1 | Initial Conditions..... | 245 | +| 8.3.2.1.4.2 | Procedure..... | 245 | +| 8.3.2.1.5 | Test Requirement..... | 246 | +| 8.3.2.2 | ACK missed detection..... | 247 | +| 8.3.2.2.1 | Definition and applicability..... | 247 | +| 8.3.2.2.2 | Minimum Requirement..... | 247 | +| 8.3.2.2.3 | Test purpose..... | 247 | +| 8.3.2.2.4 | Method of test..... | 248 | +| 8.3.2.2.4.1 | Initial Conditions..... | 248 | +| 8.3.2.2.4.2 | Procedure..... | 248 | +| 8.3.2.2.5 | Test Requirement..... | 249 | +| 8.3.3 | Performance requirements for PUCCH format 2..... | 249 | +| 8.3.3.1 | ACK missed detection..... | 249 | +| 8.3.3.1.1 | Definition and applicability..... | 249 | +| 8.3.3.1.2 | Minimum requirements..... | 249 | +| 8.3.3.1.3 | Test purpose..... | 250 | +| 8.3.3.1.4 | Method of test..... | 250 | +| 8.3.3.1.4.1 | Initial Condition..... | 250 | +| 8.3.3.1.4.2 | Procedure..... | 250 | +| 8.3.3.1.5 | Test requirements..... | 251 | + +| | | | +|-------------|-------------------------------------------------------------|-----| +| 8.3.3.2 | UCI BLER performance requirements..... | 251 | +| 8.3.3.2.1 | Definition and applicability..... | 251 | +| 8.3.3.2.2 | Minimum Requirement..... | 251 | +| 8.3.3.2.3 | Test purpose..... | 251 | +| 8.3.3.2.4 | Method of test..... | 252 | +| 8.3.3.2.4.1 | Initial Condition..... | 252 | +| 8.3.3.2.4.2 | Procedure..... | 252 | +| 8.3.3.2.5 | Test requirements..... | 253 | +| 8.3.4 | Performance requirements for PUCCH format 3..... | 253 | +| 8.3.4.1 | Definition and applicability..... | 253 | +| 8.3.4.2 | Minimum requirement..... | 253 | +| 8.3.4.3 | Test purpose..... | 253 | +| 8.3.4.4 | Method of test..... | 254 | +| 8.3.4.4.1 | Initial conditions..... | 254 | +| 8.3.4.4.2 | Procedure..... | 254 | +| 8.3.4.5 | Test requirement..... | 255 | +| 8.3.5 | Performance requirements for PUCCH format 4..... | 256 | +| 8.3.5.1 | Definition and applicability..... | 256 | +| 8.3.5.2 | Minimum requirement..... | 256 | +| 8.3.5.3 | Test purpose..... | 256 | +| 8.3.5.4 | Method of test..... | 256 | +| 8.3.5.4.1 | Initial conditions..... | 256 | +| 8.3.5.4.2 | Procedure..... | 256 | +| 8.3.5.5 | Test requirement..... | 257 | +| 8.3.6 | Performance requirements for multi-slot PUCCH..... | 258 | +| 8.3.6.1 | Performance requirements for multi-slot PUCCH format 1..... | 258 | +| 8.3.6.1.1 | NACK to ACK detection..... | 258 | +| 8.3.6.1.1.1 | Definition and applicability..... | 258 | +| 8.3.6.1.1.2 | Minimum Requirement..... | 258 | +| 8.3.6.1.1.3 | Test purpose..... | 258 | + +| | | | +|---------------|-------------------------------------------------------------|-----| +| 8.3.6.1.1.4 | Method of test..... | 258 | +| 8.3.6.1.1.4.1 | Initial conditions..... | 258 | +| 8.3.6.1.1.4.2 | Procedure..... | 259 | +| 8.3.6.1.1.5 | Test Requirement..... | 259 | +| 8.3.6.1.2 | ACK missed detection..... | 260 | +| 8.3.6.1.2.1 | Definition and applicability..... | 260 | +| 8.3.6.1.2.2 | Minimum Requirement..... | 260 | +| 8.3.6.1.2.3 | Test purpose..... | 260 | +| 8.3.6.1.2.4 | Method of test..... | 260 | +| 8.3.6.1.2.4.1 | Initial conditions..... | 260 | +| 8.3.6.1.2.4.2 | Procedure..... | 260 | +| 8.3.6.1.2.5 | Test Requirement..... | 261 | +| 8.3.7 | Performance requirements for interlaced PUCCH format 0..... | 262 | +| 8.3.7.1 | Definition and applicability..... | 262 | +| 8.3.7.2 | Minimum Requirement..... | 262 | +| 8.3.7.3 | Test purpose..... | 262 | +| 8.3.7.4 | Method of test..... | 262 | +| 8.3.7.4.1 | Initial conditions..... | 262 | +| 8.3.7.4.2 | Procedure..... | 262 | +| 8.3.7.5 | Test Requirement..... | 263 | +| 8.3.8 | Performance requirements for interlaced PUCCH format 1..... | 264 | +| 8.3.8.1 | NACK to ACK detection..... | 264 | +| 8.3.8.1.1 | Definition and applicability..... | 264 | +| 8.3.8.1.2 | Minimum Requirement..... | 264 | +| 8.3.8.1.3 | Test purpose..... | 264 | +| 8.3.8.1.4 | Method of test..... | 264 | +| 8.3.8.1.4.1 | Initial Conditions..... | 264 | +| 8.3.8.1.4.2 | Procedure..... | 264 | +| 8.3.8.1.5 | Test Requirement..... | 265 | +| 8.3.8.2 | ACK missed detection..... | 266 | + +| | | | +|-------------|----------------------------------------------------------------------------|-----| +| 8.3.8.2.1 | Definition and applicability..... | 266 | +| 8.3.8.2.2 | Minimum Requirement..... | 266 | +| 8.3.8.2.3 | Test purpose..... | 266 | +| 8.3.8.2.4 | Method of test..... | 266 | +| 8.3.8.2.4.1 | Initial Conditions..... | 266 | +| 8.3.8.2.4.2 | Procedure..... | 266 | +| 8.3.8.2.5 | Test Requirement..... | 267 | +| 8.3.9 | Performance requirements for interlaced PUCCH format 2..... | 267 | +| 8.3.9.1 | Definition and applicability..... | 267 | +| 8.3.9.2 | Minimum requirement..... | 268 | +| 8.3.9.3 | Test purpose..... | 268 | +| 8.3.9.4 | Method of test..... | 268 | +| 8.3.9.4.1 | Initial conditions..... | 268 | +| 8.3.9.4.2 | Procedure..... | 268 | +| 8.3.9.5 | Test requirement..... | 269 | +| 8.3.10 | Performance requirements for interlaced PUCCH format 3..... | 269 | +| 8.3.10.1 | Definition and applicability..... | 269 | +| 8.3.10.2 | Minimum requirement..... | 270 | +| 8.3.10.3 | Test purpose..... | 270 | +| 8.3.10.4 | Method of test..... | 270 | +| 8.3.10.4.1 | Initial conditions..... | 270 | +| 8.3.10.4.2 | Procedure..... | 270 | +| 8.3.10.5 | Test requirement..... | 271 | +| 8.3.11 | Performance requirements for PUCCH sub-slot based repetition format 0..... | 271 | +| 8.3.11.1 | Definition and applicability..... | 271 | +| 8.3.11.2 | Minimum Requirement..... | 272 | +| 8.3.11.3 | Test purpose..... | 272 | +| 8.3.11.4 | Method of test..... | 272 | +| 8.3.11.4.1 | Initial conditions..... | 272 | +| 8.3.11.4.2 | Procedure..... | 272 | + +| | | | +|--------------|----------------------------------------------------------------------|-----| +| 8.3.11.5 | Test Requirement..... | 273 | +| 8.3.12 | Performance requirements PUCCH format 1 with DM-RS bundling..... | 273 | +| 8.3.12.1 | NACK to ACK detection..... | 273 | +| 8.3.12.1.1 | Definition and applicability..... | 273 | +| 8.3.12.1.2 | Minimum Requirement..... | 273 | +| 8.3.12.1.3 | Test purpose..... | 273 | +| 8.3.12.1.4 | Method of test..... | 274 | +| 8.3.12.1.4.1 | Initial conditions..... | 274 | +| 8.3.12.1.4.2 | Procedure..... | 274 | +| 8.3.12.1.5 | Test Requirement..... | 275 | +| 8.3.12.2 | ACK missed detection..... | 275 | +| 8.3.12.2.1 | Definition and applicability..... | 275 | +| 8.3.12.2.2 | Minimum Requirement..... | 275 | +| 8.3.12.2.3 | Test purpose..... | 275 | +| 8.3.12.2.4 | Method of test..... | 275 | +| 8.3.12.2.4.1 | Initial conditions..... | 275 | +| 8.3.12.2.4.2 | Procedure..... | 276 | +| 8.3.12.2.5 | Test Requirement..... | 277 | +| 8.3.13 | Performance requirements for PUCCH format 3 with DM-RS bundling..... | 277 | +| 8.3.13.1 | Definition and applicability..... | 277 | +| 8.3.13.2 | Minimum requirement..... | 277 | +| 8.3.13.3 | Test purpose..... | 277 | +| 8.3.13.4 | Method of test..... | 277 | +| 8.3.13.4.1 | Initial conditions..... | 277 | +| 8.3.13.4.2 | Procedure..... | 277 | +| 8.3.13.5 | Test requirement..... | 278 | +| 8.4 | Performance requirements for PRACH..... | 279 | +| 8.4.1 | PRACH false alarm probability and missed detection..... | 279 | +| 8.4.1.1 | Definition and applicability..... | 279 | +| 8.4.1.2 | Minimum requirement..... | 280 | + +| | | | +|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| 8.4.1.3 | Test purpose..... | 280 | +| 8.4.1.4 | Method of test..... | 280 | +| 8.4.1.4.1 | Initial conditions..... | 280 | +| 8.4.1.4.2 | Procedure..... | 280 | +| 8.4.1.5 | Test requirement for Normal Mode..... | 281 | +| 8.4.1.6 | Test requirement for high speed train..... | 282 | +| 8.4.1.7 | Test requirement for PRACH with $L_{RA}=1151$ and $L_{RA}=571$ ..... | 283 | +| Annex A (normative): Reference measurement channels..... | | 285 | +| A.1 | Fixed Reference Channels for reference sensitivity level, ACS, in-band blocking, out-of-band blocking, receiver intermodulation and in-channel selectivity (QPSK, $R=1/3$ )..... | 285 | +| A.2 | Fixed Reference Channels for dynamic range (16QAM, $R=2/3$ )..... | 286 | +| A.3 | Fixed Reference Channels for performance requirements (QPSK, $R=193/1024$ )..... | 288 | +| A.3A | Fixed Reference Channels for performance requirements (QPSK, $R=99/1024$ )..... | 290 | +| A.3B | Fixed Reference Channels for performance requirements (QPSK, $R=308/1024$ )..... | 291 | +| A.4 | Fixed Reference Channels for performance requirements (16QAM, $R=658/1024$ )..... | 293 | +| A.5 | Fixed Reference Channels for performance requirements (64QAM, $R=567/1024$ )..... | 295 | +| A.6 | PRACH test preambles..... | 297 | +| A.7 | Fixed Reference Channels for performance requirements (QPSK, $R=157/1024$ )..... | 298 | +| A.8 | Fixed Reference Channels for performance requirements (256QAM, $R=682.5/1024$ )..... | 299 | +| A.9 | Fixed Reference Channels for performance requirements (16QAM, $R=434/1024$ )..... | 300 | +| Annex B (normative): Environmental requirements for the BS equipment..... | | 301 | +| B.1 | General..... | 301 | +| B.2 | Normal test environment..... | 301 | +| B.3 | Extreme test environment..... | 301 | +| B.3.1 | Extreme temperature..... | 301 | + +| | | | +|----------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|------------| +| B.4 | Vibration..... | 302 | +| B.5 | Power supply..... | 302 | +| B.6 | Measurement of test environments..... | 302 | +| Annex C (informative): Test tolerances and derivation of test requirements..... | | 303 | +| C.1 | Measurement of transmitter..... | 303 | +| C.2 | Measurement of receiver..... | 305 | +| C.3 | Measurement of performance requirements..... | 306 | +| Annex D (informative): Measurement system set-up..... | | 309 | +| D.1 | BS type 1-C transmitter..... | 309 | +| D.1.1 | Base station output power, output power dynamics, transmitter ON/OFF power, frequency error, EVM, unwanted emissions for BS type 1-C..... | 309 | +| D.1.2 | Transmitter intermodulation for BS type 1-C..... | 309 | +| D.1.3 | Time alignment error for BS type 1-C ..... | 310 | +| D.2 | BS type 1-C receiver..... | 310 | +| D.2.1 | Reference sensitivity level for BS type 1-C..... | 310 | +| D.2.2 | Dynamic range for BS type 1-C..... | 311 | +| D.2.3 | In-channel selectivity for BS type 1-C..... | 311 | +| D.2.4 | Adjacent Channel Selectivity (ACS) and narrowband blocking for BS type 1-C..... | 312 | +| D.2.5 | Blocking characteristics for BS type 1-C..... | 312 | +| D.2.6 | Receiver spurious emission for BS type 1-C..... | 313 | +| D.2.7 | Intermodulation characteristics for BS type 1-C..... | 313 | +| D.3 | BS type 1-H transmitter..... | 314 | +| D.3.1 | Base station output power, output power dynamics, transmitter ON/OFF power, frequency error, EVM, unwanted emissions for BS type 1-H..... | 314 | +| D.3.2 | Transmitter intermodulation for BS type 1-H..... | 315 | +| D.3.3 | Transmitter spurious emissions for BS type 1-H..... | 315 | +| D.3.4 | Time alignment error for BS type 1-H ..... | 317 | + +| | | | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| D.4 | BS type 1-H receiver..... | 317 | +| D.4.1 | Reference sensitivity level for BS type 1-H..... | 317 | +| D.4.2 | Receiver dynamic range for BS type 1-H..... | 318 | +| D.4.3 | Receiver adjacent channel selectivity and narrowband blocking for BS type 1-H..... | 318 | +| D.4.4 | Receiver spurious emissions..... | 318 | +| D.4.5 | Receiver In-channel selectivity for BS type 1-H..... | 320 | +| D.4.6 | Receiver intermodulation for BS type 1-H..... | 321 | +| D.5 | BS type 1-C performance requirements..... | 321 | +| D.5.1 | Performance requirements for PUSCH, single user PUCCH, PRACH on single antenna port in multipath fading conditions and for high speed condition..... | 321 | +| D.5.2 | Performance requirements for PUSCH transmission on two antenna ports in multipath fading conditions. . | 322 | +| D.5.3 | Performance requirements for PUSCH and PRACH in static conditions..... | 322 | +| D.5.4 | Performance requirements for UL timing adjustment..... | 323 | +| D.6 | BS type 1-H performance requirements..... | 323 | +| D.6.1 | Performance requirements for PUSCH, single user PUCCH, PRACH on single antenna port in multipath fading conditions and for high speed condition..... | 323 | +| D.6.2 | Performance requirements for PUSCH transmission on two antenna ports in multipath fading conditions. . | 324 | +| D.6.3 | Performance requirements for PUSCH and PRACH in static conditions..... | 324 | +| D.6.4 | Performance requirements for UL timing adjustment..... | 325 | +| Annex E (normative): | Characteristics of interfering signals..... | 326 | +| Annex F (normative): | Void | 327 | +| Annex G (normative): | Propagation conditions..... | 328 | +| G.1 | Static propagation condition..... | 328 | +| G.2 | Multi-path fading propagation conditions..... | 328 | +| G.2.1 | Delay profiles..... | 328 | +| G.2.1.1 | Delay profiles for FR1..... | 329 | +| G.2.2 | Combinations of channel model parameters..... | 330 | +| G.2.3 | MIMO channel correlation matrices..... | 331 | +| G.2.3.1 | MIMO correlation matrices using Uniform Linear Array..... | 331 | + +| | | | +|------------------------------------------------------|-----------------------------------------------------------------------------|------------| +| G.2.3.1.1 | Definition of MIMO correlation matrices..... | 331 | +| G.2.3.1.2 | MIMO correlation matrices at high, medium and low level..... | 332 | +| G.2.3.2 | Multi-antenna channel models using cross polarized antennas..... | 334 | +| G.2.3.2.1 | Definition of MIMO correlation matrices using cross polarized antennas..... | 335 | +| G.2.3.2.2 | Spatial correlation matrices at UE and gNB sides..... | 335 | +| G.2.3.2.2.1 | Spatial correlation matrices at UE side..... | 335 | +| G.2.3.2.2.2 | Spatial correlation matrices at gNB side..... | 335 | +| G.2.3.2.3 | MIMO correlation matrices using cross polarized antennas..... | 336 | +| G.3 | High speed train condition..... | 336 | +| G.4 | Moving propagation conditions..... | 340 | +| Annex H (normative): In-channel TX tests..... | | 342 | +| H.1 | General..... | 342 | +| H.2 | Basic principles..... | 342 | +| H.2.1 | Output signal of the TX under test..... | 342 | +| H.2.2 | Ideal signal..... | 342 | +| H.2.3 | Measurement results..... | 343 | +| H.2.4 | Measurement points..... | 343 | +| H.3 | Pre-FFT minimization process..... | 344 | +| H.4 | Timing of the FFT window..... | 344 | +| H.5 | Resource element TX power..... | 345 | +| H.6 | Post-FFT equalisation..... | 346 | +| H.7 | EVM..... | 347 | +| H.7.0 | General..... | 347 | +| H.7.1 | Averaged EVM (FDD)..... | 348 | +| H.7.2 | Averaged EVM (TDD)..... | 348 | + +| | | +|-----------------------------------------------------------------------------------------|------------| +| Annex I (normative): General rules for statistical testing..... | 349 | +| I.1 Testing methodology of PUSCH performance requirements with 0.001% BLER..... | 349 | +| I.1.1 General..... | 349 | +| I.1.2 Numerical definition of the pass-fail limits for testing PUSCH 0.001% BLER..... | 350 | +| I.1.3 Theory to derive the early pass/fail limits in I.1.2 (informative)..... | 351 | +| I.1.3.1 Numerical definition of the pass-fail limits for testing PUSCH 0.001% BLER..... | 351 | +| I.1.3.2 Simulation to derive the pass-fail limits for testing PUSCH 0.001% BLER..... | 351 | +| Annex J (informative): Change history..... | 353 | + +## 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 and NB-IoT operation in NR in-band Base Station (BS) *Type 1-C* and *Type 1-H*. These have been derived from, and are consistent with the conducted requirements for *BS Type 1-C* and *BS Type 1-H* in NR BS specification defined in TS 38.104 [2]. + +A *BS type 1-C* only has conducted requirements so it requires compliance to this specification only. + +A *BS type 1-H* has both conducted and radiated requirements so it requires compliance to the applicable requirements of this specification and TS 38.141-2 [3]. + +*BS type 1-O* and *BS type 2-O* have only radiated requirements so they require compliance to TS 38.141-2 [3] only. + +--- + +# 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.104: "NR Base Station (BS) radio transmission and reception" +- [3] 3GPP TS 38.141-2: "NR, Base Station (BS) conformance testing, Part 2: Radiated conformance testing" +- [4] ITU-R Recommendation M.1545, "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000" +- [5] ITU-R Recommendation SM.329: "Unwanted emissions in the spurious domain" +- [6] IEC 60 721-3-3: "Classification of environmental conditions - Part 3-3: Classification of groups of environmental parameters and their severities - Stationary use at weather protected locations" +- [7] IEC 60 721-3-4: "Classification of environmental conditions - Part 3: Classification of groups of environmental parameters and their severities - Clause 4: Stationary use at non-weather protected locations" +- [8] IEC 60 721: "Classification of environmental conditions" +- [9] IEC 60 068-2-1 (2007): "Environmental testing - Part 2: Tests. Tests A: Cold" +- [10] IEC 60 068-2-2: (2007): "Environmental testing - Part 2: Tests. Tests B: Dry heat" +- [11] IEC 60 068-2-6: (2007): "Environmental testing - Part 2: Tests - Test Fc: Vibration (sinusoidal)" +- [12] ITU-R Recommendation SM.328: "Spectra and bandwidth of emissions" + +- [13] Federal Communications Commission: "Title 47 of the Code of Federal Regulations (CFR) " +- [14] 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)" +- [15] 3GPP TR 25.942: "RF system scenarios" +- [16] 3GPP TS 38.212: "NR; Multiplexing and channel coding" +- [17] 3GPP TS 38.211: "NR; Physical channels and modulation" +- [18] 3GPP TS 38.214: "NR; Physical layer procedures for data" +- [19] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification" +- [20] 3GPP TR 38.901: "Study on channel model for frequencies from 0.5 to 100 GHz" +- [21] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone" +- [22] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception" +- [23] ITU-T Recommendation O.150, "Equipment for the measurement of digital and analogue/digital parameters" +- [24] 3GPP TS 36.141: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) conformance testing" +- [25] ECC Decision(20)02: "Harmonised use of the paired frequency bands 874.4-880.0 MHz and 919.4-925.0 MHz and of the unpaired frequency band 1900-1910 MHz for Railway Mobile Radio (RMR)" +- [26] 3GPP TS 37.141: "E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) conformance testing". +- [27] 3GPP TS 37.145-1: "Active Antenna System (AAS) 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 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]. + +**aggregated BS channel bandwidth:** the RF bandwidth in which a Base Station transmits and receives multiple contiguously aggregated carriers. The *aggregated BS channel bandwidth* is measured in MHz + +**antenna connector:** connector at the conducted interface of the *BS type 1-C* + +**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 a *BS type 1-C antenna connector*, or to one or more *BS type 1-H TAB connectors* at the *transceiver array boundary* + +**Base Station RF Bandwidth:** RF bandwidth in which a base station transmits and/or receives single or multiple carrier(s) within a supported *operating band* + +NOTE: In single carrier operation, the *Base Station RF Bandwidth* is equal to the *BS channel bandwidth*. + +**Base Station RF Bandwidth edge:** frequency of one of the edges of the *Base Station RF Bandwidth* + +**basic limit:** emissions limit relating to the power supplied by a single transmitter to a single antenna transmission line in ITU-R SM.329 [5] used for the formulation of unwanted emission requirements for FR1 + +**BS channel bandwidth:** RF bandwidth supporting a single NR RF carrier with the transmission bandwidth configured in the uplink or downlink + +NOTE 1: The *BS channel bandwidth* is measured in MHz and is used as a reference for transmitter and receiver RF requirements. + +NOTE 2: It is possible for the BS to transmit to and/or receive from one or more UE bandwidth parts that are smaller than or equal to the BS transmission bandwidth configuration, in any part of the BS transmission bandwidth configuration. + +**BS type 1-C:** NR base station operating at FR1 with requirements set consisting only of conducted requirements defined at individual *antenna 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 + +NOTE: *BS type 1-O* conformance requirements are captured in TS 38.141-2 [3] and are out of scope of this specification. + +**BS type 2-O:** NR base station operating at FR2 with a requirement set consisting only of OTA requirements defined at the RIB + +NOTE: *BS type 2-O* conformance requirements are captured in TS 38.141-2 [3] and are out of scope of this specification. + +**channel edge:** lowest or highest frequency of the NR carrier, separated by the *BS channel bandwidth* + +**carrier aggregation:** aggregation of two or more component carriers in order to support wider transmission bandwidths + +**carrier aggregation configuration:** a set of one or more *operating bands* across which the BS aggregates carriers with a specific set of technical requirements + +**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 + +**contiguous spectrum:** spectrum consisting of a contiguous block of spectrum with no sub-block gap(s) + +**highest carrier:** The carrier with the highest carrier frequency transmitted/received in a specified frequency band + +**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. + +**Inter-band gap:** The frequency gap between two supported consecutive operating bands + +**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 frequency band + +**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 carrier output power:** mean power level measured per carrier at the indicated interface, during the *transmitter ON period* in a specified reference condition + +**maximum total output power:** mean power level measured within the *operating band* at the indicated interface, during the *transmitter ON period* in a specified reference condition + +**measurement bandwidth:** RF bandwidth in which an emission level is specified + +**multi-band connector:** *antenna connector* of the *BS type 1-C* or *TAB connector* of the *BS type 1-H* 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-carrier transmission configuration:** set of one or more contiguous or non-contiguous carriers that a BS is able to transmit simultaneously according to the manufacturer's specification + +**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. + +**non-contiguous spectrum:** spectrum consisting of two or more sub-blocks separated by *sub-block gap(s)* + +**operating band:** frequency range in which NR 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 according to the designations in TS 38.104 [2], tables 5.2-1 and 5.2-2. + +**Radio Bandwidth:** frequency difference between the upper edge of the highest used carrier and the lower edge of the lowest used carrier + +**rated carrier output power:** mean power level associated with a particular carrier the manufacturer has declared to be available at the indicated interface, during the *transmitter ON period* in a specified reference condition + +**rated total output power:** mean power level associated with a particular *operating band* the manufacturer has declared to be available at the indicated interface, during the *transmitter ON period* in a specified reference condition + +**requirement set:** one of the NR base station requirement's set as defined for *BS type 1-C*, *BS type 1-H*, *BS type 1-O*, and *BS type 2-O* + +**single-band connector:** *antenna connector* of the *BS type 1-C* or *TAB connector* of the *BS type 1-H* 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* + +**sub-band:** 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 transmission and reception 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 un-coordinated operation + +**superseding-band:** superseding-band of an operating band includes the whole of the uplink and downlink frequency range of the operating band + +**TAB connector:** *transceiver array boundary connector* + +**TAB connector RX min cell group:** *operating band* specific declared group of *TAB connectors* to which *BS type 1-H* conducted 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 *BS type 1-H* setting corresponding to the declared minimum number of cells with reception 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 *BS type 1-H* conducted 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 *BS type 1-H* 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 + +**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 + +**transmitter OFF period:** time period during which the BS transmitter is not allowed to transmit + +**transmitter ON period:** time period during which the BS transmitter is transmitting data and/or reference symbols + +**transmitter transient period:** time period during which the transmitter is changing from the OFF period to the ON period or vice versa + +**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}}$ | BS channel bandwidth | +| $BW_{\text{Channel\_CA}}$ | Aggregated BS channel bandwidth , expressed in MHz. $BW_{\text{Channel\_CA}} = F_{\text{edge\_high}} - F_{\text{edge\_low}}$ . | +| $BW_{\text{Channel\_block}}$ | Sub-block bandwidth, expressed in MHz. $BW_{\text{Channel\_block}} = F_{\text{edge\_block\_high}} - F_{\text{edge\_block\_low}}$ . | +| $BW_{\text{Config}}$ | Transmission bandwidth configuration, expressed in MHz, where $BW_{\text{Config}} = N_{\text{RB}} \times \text{SCS} \times 12 \text{ kHz}$ | +| $BW_{\text{tot}}$ | Total RF bandwidth | +| $\Delta f$ | Separation between the channel edge frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency | +| $\Delta f_{\text{BE\_offset}}$ | Separation between the edge of the last transmitted channel of the channels assigned for NR-U channel bandwidth and the nominal -3 dB point of the measuring filter closest to the carrier frequency | +| $\Delta f_{\text{max}}$ | $f_{\text{offset\_max}}$ minus half of the bandwidth of the measuring filter | +| $\Delta F_{\text{Global}}$ | Global frequency raster granularity | +| $\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 | +| $\Delta F_{\text{Raster}}$ | Channel raster granularity | +| $\Delta_{\text{SUL}}$ | Channel raster offset for SUL | +| $F_{\text{C}}$ | RF reference frequency on the channel raster | +| $F_{\text{C\_block\_high}}$ | $F_{\text{C}}$ of the highest transmitted/received carrier in a sub-block | +| $F_{\text{C\_block\_low}}$ | $F_{\text{C}}$ of the lowest transmitted/received carrier in a sub-block | +| $F_{\text{C\_low}}$ | The $F_{\text{C}}$ of the lowest carrier, expressed in MHz | +| $F_{\text{C\_high}}$ | The $F_{\text{C}}$ of the highest carrier, expressed in MHz | +| $F_{\text{edge\_low}}$ | The lower edge of aggregated BS channel bandwidth , expressed in MHz. $F_{\text{edge\_low}} = F_{\text{C\_low}} - F_{\text{offset\_low}}$ | +| $F_{\text{edge\_high}}$ | The upper edge of aggregated BS channel bandwidth , expressed in MHz. $F_{\text{edge\_high}} = F_{\text{C\_high}} + F_{\text{offset\_high}}$ . | +| $F_{\text{edge\_block\_low}}$ | The lower sub-block edge, where $F_{\text{edge\_block\_low}} = F_{\text{C\_block\_low}} - F_{\text{offset\_low}}$ | +| $F_{\text{edge\_block\_high}}$ | The upper sub-block edge, where $F_{\text{edge\_block\_high}} = F_{\text{C\_block\_high}} + F_{\text{offset\_high}}$ | +| $F_{\text{offset\_high}}$ | Frequency offset from $F_{\text{C\_high}}$ to the upper Base Station RF Bandwidth edge , or from $F_{\text{C\_block\_high}}$ to the upper sub-block edge | +| $F_{\text{offset\_low}}$ | Frequency offset from $F_{\text{C\_low}}$ to the lower Base Station RF Bandwidth edge , or from $F_{\text{C\_block\_low}}$ to the lower sub-block edge | +| $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{offset}}$ | Separation between the channel edge frequency and the centre of the measuring filter | +| $f_{\text{offset\_max}}$ | The offset to the frequency $\Delta f_{\text{OBUE}}$ outside the downlink operating band | +| $F_{\text{REF}}$ | RF reference frequency | +| $F_{\text{REF\_SUL}}$ | RF reference frequency for Supplementary Uplink (SUL) bands | +| $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 [2] clause 5.3.3 | +| $I_{\text{uant}}$ | gNB internal logical interface between the implementation specific O&M function and the RET antennas and TMAs control unit function of the gNB | + +| | | +|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $N_{\text{cells}}$ | The declared number corresponding to the minimum number of cells that can be transmitted by an BS type 1-H in a particular operating band | +| $N_{\text{RB}}$ | Transmission bandwidth configuration, expressed in resource blocks | +| $N_{\text{REF}}$ | NR Absolute Radio Frequency Channel Number (NR-ARFCN) | +| $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 conducted Rx spurious emission scaling, as calculated in clause 7.6.1 | +| $N_{\text{RXU,countedpercell}}$ | The number of active receiver units that are taken into account for conducted RX spurious emissions scaling per cell, as calculated in clause 7.6.1 | +| $N_{\text{TXU,counted}}$ | The number of active transmitter units as calculated in clause 6.1, that are taken into account for conducted TX output power limit in clause 6.2.1, and for unwanted TX emissions scaling | +| $N_{\text{TXU,countedpercell}}$ | The number of active transmitter units that are taken into account for conducted TX emissions scaling per cell, as calculated in clause 6.1 | +| $P_{\text{EM,n50,ind}}$ | Declared emission level for Band n50 in the band 1518-1559 MHz; ind = a, b | +| $P_{\text{EM,n54,ind}}$ | Declared emission level for Band n54 in the band 1518-1559 MHz; ind = a, b, c, d, e, f | +| $P_{\text{max,c,AC}}$ | Maximum carrier output power measured per antenna connector | +| $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{rated,c,AC}}$ | The rated carrier output power per antenna connector | +| $P_{\text{rated,c,sys}}$ | The sum of $P_{\text{rated,c,TABC}}$ for all TAB connectors for a single carrier | +| $P_{\text{rated,c,TABC}}$ | The rated carrier output power per TAB connector | +| $P_{\text{rated,t,AC}}$ | The rated total output power declared at the antenna connector | +| $P_{\text{rated,t,TABC}}$ | The rated total output power declared at TAB connector | +| $P_{\text{REFSENS}}$ | Conducted Reference Sensitivity power level | +| $SS_{\text{REF}}$ | SS block reference frequency position | +| $W_{\text{gap}}$ | Sub-block gap or Inter RF Bandwidth gap size | + +### 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 | +| ACLR | Adjacent Channel Leakage Ratio | +| ACS | Adjacent Channel Selectivity | +| AWGN | Additive White Gaussian Noise | +| BS | Base Station | +| BW | Bandwidth | +| CA | Carrier Aggregation | +| CACLR | Cumulative ACLR | +| CP-OFDM | Cyclic Prefix-OFDM | +| CW | Continuous Wave | +| DFT-s-OFDM | Discrete Fourier Transform-spread-OFDM | +| DM-RS | Demodulation Reference Signal | +| E-UTRA | Evolved UTRA | +| EVM | Error Vector Magnitude | +| FDD | Frequency Division Duplex | +| FR | Frequency Range | +| GSCN | Global Synchronization Channel Number | +| GSM | Global System for Mobile communications | +| ITU-R | Radiocommunication Sector of the International Telecommunication Union | + +| | | +|----------|--------------------------------------------| +| ICS | In-Channel Selectivity | +| LA | Local Area | +| LNA | Low Noise Amplifier | +| MR | Medium Range | +| NB-IoT | Narrowband – Internet of Things | +| NR | New Radio | +| NR-ARFCN | NR Absolute Radio Frequency Channel Number | +| OBUE | Operating Band Unwanted Emissions | +| OCC | Orthogonal Covering Code | +| OTA | Over The Air | +| RB | Resource Block | +| RDN | Radio Distribution Network | +| REFSENS | Reference Sensitivity | +| RF | Radio Frequency | +| RIB | Radiated Interface Boundary | +| RMS | Root Mean Square (value) | +| RS | Reference Signal | +| RV | Redundancy Version | +| RX | Receiver | +| SCS | Sub-Carrier Spacing | +| SDL | Supplementary Downlink | +| SSB | Synchronization Signal Block | +| SUL | Supplementary Uplink | +| TAB | Transceiver Array Boundary | +| TAE | Time Alignment Error | +| TDD | Time division Duplex | +| TDL | Tapped Delay Line | +| TX | Transmitter | +| TT | Test Tolerance | +| UCI | Uplink Control Information | +| ZF | Zero Forcing | + +--- + +## 4 General conducted 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 tests defined for FR1. The frequency ranges FR1 and FR2 are defined in clause 5.1 of TS 38.104 [2]. + +The minimum requirements are given in TS 38.104 [2] and the references therein. Test Tolerances for the conducted test requirements explicitly stated in the present document are given in annex C of the present document. + +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. + +For *BS type I-H* 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, $f \leq 3$ GHz
±1.0 dB, $3$ GHz $< f \leq 7.125$ GHz (Note)
±1.5 dB, for bands n46, n96 and n102 | | +| 6.3 Output power dynamics | ± 0.4 dB | | +| 6.4.1 Transmit OFF power | ±2.0 dB , $f \leq 3$ GHz
±2.5 dB, $3$ GHz $< f \leq 7.125$ GHz (Note)
±3 dB, for bands n46, n96 and n102 | | +| 6.4.2 Transmitter transient period | N/A | | +| 6.5.2 Frequency error | ± 12 Hz | | +| 6.5.3 EVM | ± 1% | | +| 6.5.4 Time alignment error | ± 25ns | | +| 6.6.2 Occupied bandwidth | 5 MHz, 10 MHz BS Channel BW: ±100 kHz
15 MHz, 20 MHz, 25 MHz, 30 MHz, 35 MHz, 40 MHz,
45 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) | ACLR/ CACLR
BW $\leq 20$ MHz: ±0.8 dB
BW $> 20$ MHz: ±1.2 dB

Absolute power ±2.0 dB, $f \leq 3$ GHz
Absolute power ±2.5 dB, $3$ GHz $< f \leq 7.125$ GHz (Note)
Absolute power ±3 dB, for bands n46, n96 and n102

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

CACLR absolute power ±2.0 dB , $f \leq 3$ GHz
CACLR absolute power ±2.5 dB, $3$ GHz $< f \leq 7.125$ GHz
CACLR absolute power ±3 dB, for bands n46, n96 and n102
(Note) | | +| 6.6.4 Operating band unwanted emissions | ±1.5 dB, $f \leq 3$ GHz
±1.8 dB, $3$ GHz $< f \leq 7.125$ GHz (Note)
±2.2 dB, for bands n46, n96 and n102 | | +| 6.6.5.5.1.1 Transmitter spurious emissions, Mandatory Requirements | 9 kHz $< f \leq 4$ GHz: ±2.0 dB
4 GHz $< f \leq 19$ GHz: ±4.0 dB
19 GHz $< f \leq 26$ GHz: ±4.5 dB | | +| 6.6.5.5.1.2 Transmitter spurious emissions, Protection of BS receiver | ±3.0 dB | | +| 6.6.5.5.1.3 Transmitter spurious emissions, Additional spurious emission requirements | ±2.0 dB for $> -60$ dBm, $f \leq 3$ GHz
±2.5 dB, $3$ GHz $< f \leq 4.2$ GHz
±3.0 dB, $4.2$ GHz $< f \leq 7.125$ GHz
±3.0 dB for $\leq -60$ dBm, $f \leq 3$ GHz
±3.5 dB, $3$ GHz $< f \leq 4.2$ GHz
±4.0 dB, $4.2$ GHz $< f \leq 7.125$ GHz
±4.0 dB, for bands n46 and n96 | | +| 6.6.5.2.4 Transmitter spurious emissions, Co-location | ±3.0 dB | | + +| Clause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------| +| 6.7 Transmitter intermodulation (interferer requirements)
This tolerance applies to the stimulus and not the measurements defined in 6.6.3, 6.6.4 and 6.6.5 | The value below applies only to the interfering signal and is unrelated to the measurement uncertainty of the tests in 6.6.3 (ACLR), 6.6.4 (OBUE) and 6.6.5 (spurious emissions) which have to be carried out in the presence of the interferer.

$\pm 1.0$ dB | The uncertainty of interferer has double the effect on the result due to the frequency offset | +| NOTE: Test system uncertainty values for $4.2 \text{ GHz} < f \leq 7.125 \text{ GHz}$ apply for BS operates in licensed spectrum only. | | | + +#### 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 Reference sensitivity level | $\pm 0.7$ dB, $f \leq 3$ GHz
$\pm 1.0$ dB, $3$ GHz $< f \leq 4.2$ GHz
$\pm 1.2$ dB, $4.2$ GHz $< f \leq 6$ GHz
$\pm 1.5$ dB, $6$ GHz $< f \leq 7.125$ GHz
$\pm 1.5$ dB, for bands n46, n96 and n102 | | +| 7.3 Dynamic range | $\pm 0.3$ dB | | +| 7.4.1 Adjacent channel selectivity | $\pm 1.4$ dB, $f \leq 3$ GHz
$\pm 1.8$ dB, $3$ GHz $< f \leq 4.2$ GHz
$\pm 2.1$ dB, $4.2$ GHz $< f \leq 6$ GHz (Note 2)
$\pm 2.5$ dB, $6$ GHz $< f \leq 7.125$ GHz
$\pm 2.5$ dB, for bands n46, n96 and n102 |

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 GHz
Wanted signal level \pm 0.7 dB
Interferer signal level \pm 0.7 dB

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

4.2 GHz < f \leq 6 GHz
Wanted signal level \pm 1.22 dB
Interferer signal level \pm 1.22 dB

6 GHz < f \leq 7.125 GHz
Wanted signal level \pm 1.5 dB
Interferer signal level \pm 1.8 dB Bands n46, n96 and n102
Wanted signal level \pm 1.5 dB
Interferer signal level \pm 1.8 dB

f \leq 7.125 GHz
Impact of interferer leakage 0.4 dB

| +| 7.4.2.4.2 In-band blocking (General blocking) | $\pm 1.6$ dB, $f \leq 3$ GHz
$\pm 2.0$ dB, $3$ GHz $< f \leq 4.2$ GHz
$\pm 2.2$ dB, $4.2$ GHz $< f \leq 6$ GHz (Note 2)
$\pm 2.7$ dB, $6$ GHz $< f \leq 7.125$ GHz
$\pm 2.7$ dB, for bands n46, n96 and n102 | | +| 7.4.2.4.3 In-band blocking (Narrow band blocking) | $\pm 1.4$ dB, $f \leq 3$ GHz
$\pm 1.8$ dB, $3$ GHz $< f \leq 4.2$ GHz
$\pm 2.1$ dB, $4.2$ GHz $< f \leq 6$ GHz (Note 2) | | +| 7.5.5.1 Out-of-band blocking (General requirements) | $f_{\text{wanted}} \leq 3$ GHz
$1$ MHz $< f_{\text{interferer}} \leq 3$ GHz: $\pm 1.3$ dB
$3.0$ GHz $< f_{\text{interferer}} \leq 4.2$ GHz: $\pm 1.5$ dB
$4.2$ GHz $< f_{\text{interferer}} \leq 12.75$ GHz: $\pm 3.2$ dB

$3$ GHz $< f_{\text{wanted}} \leq 4.2$ GHz:
$1$ MHz $< f_{\text{interferer}} \leq 3$ GHz: $\pm 1.5$ dB |

Overall system uncertainty comprises three quantities:

  1. Wanted signal level error
  2. Interferer signal level error
  3. Interferer broadband noise
| + +| | | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

3.0\text{GHz} < f_{\text{interferer}} \leq 4.2\text{ GHz}: \pm 1.7\text{ dB}
4.2\text{GHz} < f_{\text{interferer}} \leq 12.75\text{ GHz}: \pm 3.3\text{ dB}
4.2\text{GHz} < f_{\text{wanted}} \leq 6.0\text{GHz}:
1\text{MHz} < f_{\text{interferer}} \leq 3\text{ GHz}: \pm 1.7\text{ dB}
3.0\text{GHz} < f_{\text{interferer}} \leq 4.2\text{ GHz}: \pm 1.8\text{ dB}
4.2\text{GHz} < f_{\text{interferer}} \leq 12.75\text{ GHz}: \pm 3.3\text{ dB}
6\text{GHz} < f_{\text{wanted}} \leq 7.125\text{GHz}:
1\text{MHz} < f_{\text{interferer}} \leq 3\text{ GHz}: \pm 1.9\text{ dB}
3.0\text{GHz} < f_{\text{interferer}} \leq 4.2\text{ GHz}: \pm 2.0\text{ dB}
4.2\text{GHz} < f_{\text{interferer}} \leq 12.75\text{ GHz}: \pm 3.5\text{ dB}
f_{\text{wanted}}: for bands n46, n96 and n102
1\text{MHz} < f_{\text{interferer}} \leq 3\text{ GHz}: \pm 1.9\text{ dB}
3.0\text{GHz} < f_{\text{interferer}} \leq 4.2\text{ GHz}: \pm 2.0\text{ dB}
4.2\text{GHz} < f_{\text{interferer}} \leq 12.75\text{ GHz}: \pm 3.5\text{ dB}

|

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\text{ dB} up to 3 GHz
\pm 1.0\text{ dB} up to 4.2 GHz
\pm 1.22\text{ dB} up to 6 GHz
\pm 1.5\text{ dB} up to 7.125 GHz
Interferer signal level:
\pm 1.0\text{ dB} up to 3 GHz
\pm 1.2\text{ dB} up to 4.2 GHz
\pm 3.0\text{ dB} up to 12.75 GHz
Impact of interferer Broadband noise 0.1 dB

| +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | +|---------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 7.5.5.2 Out-of-band blocking (Co-location requirements) | Co-location blocking, using CW interferer:
±2.5 dB, $f \leq 3.0$ GHz
±2.6 dB, $3.0$ GHz $< f \leq 4.2$ GHz
±2.7 dB, $4.2$ GHz $< f \leq 6.0$ GHz
±2.9 dB, $6$ GHz $< f \leq 7.125$ GHz
±2.9 dB, for bands n46, n96 and n102 | Co-location blocking, using CW interferer:
$f \leq 3.0$ GHz
Wanted signal level $\pm 0.7$ dB
$3.0$ GHz $< f \leq 4.2$ GHz
Wanted signal level $\pm 1.0$ dB
$4.2$ GHz $< f \leq 6.0$ GHz
Wanted signal level $\pm 1.22$ dB
$6$ GHz $< f \leq 7.125$ GHz
Wanted signal level $\pm 1.5$ dB
For bands n46, n96 and n102
Wanted signal level $\pm 1.5$ dB

$f \leq 7.125$ GHz
Interferer signal level:
$\pm 2.0$ dB
Interferer signal level for band n46, n96 and n102:
$\pm 2.0$ dB

Interferer ACLR not applicable
Impact of interferer Broadband noise 0.4 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
$19$ GHz $< f \leq 26$ GHz: $\pm 4.5$ dB | | +| 7.7 Receiver intermodulation | $\pm 1.8$ dB, $f \leq 3.0$ GHz
$\pm 2.4$ dB, $3.0$ GHz $< f \leq 4.2$ GHz
$\pm 3.0$ dB, $4.2$ GHz $< f \leq 6.0$ GHz (Note 2)
$\pm 3.3$ dB, $6$ GHz $< f \leq 7.125$ GHz
$\pm 3.3$ dB, for bands n46, n96 and n102 | 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
$4.2$ GHz $< f \leq 6$ GHz
Wanted signal level $\pm 1.22$ dB
CW Interferer level $\pm 0.98$ dB
Mod Interferer level $\pm 1.22$ dB
$6$ GHz $< f \leq 7.125$ GHz | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Wanted signal level $\pm 1.5\text{dB}$
CW Interferer level $\pm 1.0\text{dB}$
Mod Interferer level $\pm 1.5\text{dB}$
For bands n46, n96 and n102
Wanted signal level $\pm 1.5\text{dB}$
CW Interferer level $\pm 1.0\text{dB}$
Mod Interferer level $\pm 1.5\text{dB}$

$f \leq 7.125\text{ GHz}$
Impact of interferer ACLR 0.4 dB | +| 7.8 In-channel selectivity | $\pm 1.4\text{ dB}$ , $f \leq 3\text{ GHz}$
$\pm 1.8\text{ dB}$ , $3\text{ GHz} < f \leq 4.2\text{ GHz}$
$\pm 2.1\text{ dB}$ , $4.2\text{ GHz} < f \leq 6\text{ GHz}$ (Note 2)
$\pm 2.5\text{ dB}$ , $6\text{ GHz} < f \leq 7.125\text{ GHz}$ $\pm 2.5\text{ dB}$ ,
for bands n46, n96 and n102 | | +| NOTE 1: Unless otherwise noted, only the Test System stimulus error is considered here. The effect of errors in the throughput measurements due to finite test duration is not considered. | | | +| NOTE 2: Test system uncertainty values for $4.2\text{ GHz} < f \leq 7.125\text{ GHz}$ apply for BS operates in licensed spectrum only. | | | + +#### 4.1.2.4 Measurement of performance requirements + +**Table 4.1.2.4-1: Maximum Test System Uncertainty for performance requirements** + +| Clause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|-------------------------------------------------------------------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8 PUSCH, PUCCH, PRACH with single antenna port and fading channel | $\pm 0.6\text{ dB}$ | Overall system uncertainty for fading conditions comprises two quantities:
1. Signal-to-noise ratio uncertainty
2. Fading profile power uncertainty

Items 1 and 2 are assumed to be uncorrelated so can be root sum squared:
$\text{Test System uncertainty} = [\text{SQRT} (\text{Signal-to-noise ratio uncertainty}^2 + \text{Fading profile power uncertainty}^2)]$
Signal-to-noise ratio uncertainty $\pm 0.3\text{ dB}$
Fading profile power uncertainty $\pm 0.5\text{ dB}$ | +| 8 PUSCH, PRACH with single antenna port and AWGN | $\pm 0.3\text{ dB}$ | Signal-to-noise ratio uncertainty $\pm 0.3\text{ dB}$ | +| 8 PUSCH with two antenna port and fading channel | $\pm 0.8\text{ dB}$ | Overall system uncertainty for fading conditions comprises two quantities:
1. Signal-to-noise ratio uncertainty
2. Fading profile power uncertainty

Items 1 and 2 are assumed to be uncorrelated so can be root sum squared:
$\text{Test System uncertainty} = [\text{SQRT} (\text{Signal-to-noise ratio uncertainty}^2 + \text{Fading profile power uncertainty}^2)]$
Signal-to-noise ratio uncertainty $\pm 0.3\text{ dB}$
Fading profile power uncertainty $\pm 0.7\text{ dB}$ for MIMO | + +### 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 [4]. + +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 requirement reference points + +### 4.2.1 BS type 1-C + +*BS type 1-C* requirements are applied at the BS *antenna connector* (port A) for a single transmitter or receiver with a full complement of transceivers for the configuration in normal operating conditions. If any external apparatus such as an amplifier, a filter or the combination of such devices is used, requirements apply at the far end *antenna connector* (port B). + +![Diagram of BS type 1-C transmitter interface showing a BS cabinet connected to an External PA (if any) and an External device (e.g. TX filter, if any), with Port A at the BS cabinet and Port B at the far end towards the antenna connector.](3f09464f0a8ac9446981a53f9b78df2c_img.jpg) + +The diagram illustrates the transmitter interface for a BS type 1-C. 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 connections are represented by wavy lines. Port A is indicated by an arrow pointing to the connector on the BS cabinet. Port B is indicated by an arrow pointing to the connector on the External device. To the right of Port B, a dashed line with an arrow points towards the text 'Towards antenna connector'. + +Diagram of BS type 1-C transmitter interface showing a BS cabinet connected to an External PA (if any) and an External device (e.g. TX filter, if any), with Port A at the BS cabinet and Port B at the far end towards the antenna connector. + +Figure 4.2.1-1: BS type 1-C transmitter interface + +![Figure 4.2.1-2: BS type 1-C receiver interface diagram. It shows a block diagram of the receiver chain. From left to right: a 'BS cabinet' block, a wavy line representing a cable, an 'External LNA (if any)' block containing a triangle symbol, another wavy line representing a cable, an 'External device e.g. RX filter (if any)' block, and a final wavy line representing a cable. Port A is indicated by an arrow pointing to the connection between the BS cabinet and the first cable. Port B is indicated by an arrow pointing to the connection between the external device and the final cable. An arrow labeled 'From antenna connector' points to the input of the final cable from the right.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +Figure 4.2.1-2: BS type 1-C receiver interface diagram. It shows a block diagram of the receiver chain. From left to right: a 'BS cabinet' block, a wavy line representing a cable, an 'External LNA (if any)' block containing a triangle symbol, another wavy line representing a cable, an 'External device e.g. RX filter (if any)' block, and a final wavy line representing a cable. Port A is indicated by an arrow pointing to the connection between the BS cabinet and the first cable. Port B is indicated by an arrow pointing to the connection between the external device and the final cable. An arrow labeled 'From antenna connector' points to the input of the final cable from the right. + +Figure 4.2.1-2: BS type 1-C receiver interface + +## 4.2.2 BS type 1-H + +BS type 1-H requirements are defined for two points of reference, signified by radiated requirements and conducted requirements. + +![Figure 4.2.2-1: Radiated and conducted reference points for BS type 1-H diagram. This diagram shows the internal structure of a BS type 1-H. On the left, a dashed box labeled 'Transceiver unit array (TRXUA) 1 to M' contains multiple units labeled #1, #2, ..., #K. Each unit has a connector at its right side. These connectors are located at a vertical dashed line labeled 'Transceiver array boundary'. Below this boundary, an arrow points to one of the connectors, labeled 'Transceiver array boundary connector (TAB)'. To the right of the boundary, the signal flows into a dashed box labeled 'Composite antenna', which contains two sub-blocks: 'Radio Distribution Network RDN' and 'Antenna Array (AA)'. A second vertical dashed line to the right of the composite antenna is labeled 'Radiated interface boundary (RIB)'.](fd76efce549d3713543bb5ed9b023c2e_img.jpg) + +Figure 4.2.2-1: Radiated and conducted reference points for BS type 1-H diagram. This diagram shows the internal structure of a BS type 1-H. On the left, a dashed box labeled 'Transceiver unit array (TRXUA) 1 to M' contains multiple units labeled #1, #2, ..., #K. Each unit has a connector at its right side. These connectors are located at a vertical dashed line labeled 'Transceiver array boundary'. Below this boundary, an arrow points to one of the connectors, labeled 'Transceiver array boundary connector (TAB)'. To the right of the boundary, the signal flows into a dashed box labeled 'Composite antenna', which contains two sub-blocks: 'Radio Distribution Network RDN' and 'Antenna Array (AA)'. A second vertical dashed line to the right of the composite antenna is labeled 'Radiated interface boundary (RIB)'. + +Figure 4.2.2-1: Radiated and conducted reference points for BS type 1-H + +Radiated characteristics are defined over the air (OTA), where the *operating band* specific radiated interface is referred to as the *Radiated Interface Boundary* (RIB). Radiated requirements are also referred to as OTA requirements. The (spatial) characteristics in which the OTA requirements apply are detailed for each requirement. + +NOTE: Radiated conformance requirements are captured in TS 38.141-2 [3] and are out of scope of this specification. + +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 clause. + +## 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. + +BS classes for *BS type 1-C* and 1-H are defined as indicated below: + +- 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. +- 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. + +## 4.4 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.4-1 lists all requirements in the present specification that may be applied differently in different regions. + +**Table 4.4-1: List of regional requirements** + +| Clause number | Requirement | Comments | +|-------------------------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 5 | Operating bands | Some NR operating bands may be applied regionally. | +| 6.2.1 | Base station output power | Additional output power limits 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 in present specification. | +| 6.6.3.5.3 | Adjacent Channel Leakage Power Ratio | For Band n41 and n90 operation in Japan, absolute ACLR limits shall be applied to the sum of the absolute ACLR power over all antenna connectors for BS type 1-C. | +| 6.6.4.5 | Operating band unwanted emission | Category A or Category B operating band unwanted emission limits may be applied regionally.
For operation with shared spectrum channel access, the BS may have to comply with the applicable BS power limits established regionally, when deployed in regions where those limits apply and under the conditions declared by the manufacturer. | +| 6.6.4.5.6.1 | Operating band unwanted emissions:
Limits in FCC Title 47 | The BS may have to comply with the additional requirements, when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. | +| 6.6.4.5.6.2 | Operating band unwanted emission
Protection of DTT | The BS operating in Band n20 may have to comply with the additional requirements for protection of DTT, when deployed in certain regions. | +| 6.6.4.5.6.5 | Operating band unwanted emissions
Additional requirements for n24 | The BS operating in Band n24 may have to comply with the additional requirements when deployed in regions where FCC regulation applies. | +| 6.6.4.5.7 | Operating band unwanted emission, | For Band n41 and n90 operation in Japan, the operating band unwanted emissions limits shall be applied to the sum of the emission power over all antenna connectors for BS type 1-C. | +| 6.6.5.5.1.1 | Transmitter spurious emissions | Category A or Category B spurious emission limits, as defined in ITU-R Recommendation SM.329 [5], may apply regionally.
The emission limits for BS type 1-H specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation. In addition, for operation with shared spectrum channel access, the BS may have to comply with the applicable spurious emission limits established regionally, when deployed in regions where those limits apply and under the conditions declared by the manufacturer. | +| 6.6.5.5.1.3 | Transmitter spurious emissions: additional requirements | These requirements may be applied for the protection of system operating in frequency ranges other than the BS operating band. | +| 6.6.5.5.3 | Transmitter spurious emissions | For Band n41 and n90 operation in Japan, the sum of the spurious emissions over all antenna connectors for BS type 1-C shall not exceed the basic limits . | +| 6.7.5.1.1,
6.7.5.2.1 | Transmitter intermodulation | Interfering signal positions that are partially or completely outside of any downlink operating band of the base station are not excluded from the requirement in Japan in Band n77, n78, n79. | +| 6.7.5.1.2,
6.7.5.2.3 | Transmitter intermodulation | The BS may have to comply with the additional requirements, when deployed in certain regions. | +| 6.7.5.1.2,
6.7.5.2.3 | Transmitter intermodulation | For Band n26 and n28 operation in Japan, the BS shall comply with the additional requirements when the narrowest channel bandwidth supported by the BS is 5MHz or wider, | +| 7.6.5.2,
7.6.5.3 | Receiver spurious emissions | The emission limits for BS type 1-H specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation. For Band n41 and n90 operation in Japan, the sum of RX spurious emissions over all antenna connectors for BS type 1-C shall not exceed basic limits | + +## 4.5 BS configurations + +### 4.5.1 BS type 1-C + +#### 4.5.1.1 Transmit configurations + +##### 4.5.1.1.1 General + +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), with Test port A at the BS cabinet and Test port B at the far end antenna connector.](c5a20f7bae219fc4c31f7376b7eb11e1_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 connections are represented by wavy lines. 'Test port A' is indicated by an arrow pointing to the connector between the BS cabinet and the External PA. 'Test port B' is indicated by an arrow pointing to the connector at the far end of the External device. To the right of Test port B, a dashed line with an arrow points towards the text '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 far end antenna connector. + +Figure 4.5.1.1.1-1: Transmitter test ports + +##### 4.5.1.1.2 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 (D.32), it is sufficient to measure the signal at any one of the transmitter *antenna connectors*. + +#### 4.5.1.2 Receive configurations + +##### 4.5.1.2.1 General + +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 output, and Test port B is at the External device output. A signal source is indicated as 'From antenna connector' pointing to Test port B.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +The diagram illustrates the receiver test ports for a base station. It shows a sequence of components connected in series: a 'BS cabinet', an 'External LNA (if any)', and an 'External device e.g. RX filter (if any)'. The connections between these components are represented by wavy lines. 'Test port A' is indicated by an arrow pointing to the output of the BS cabinet. 'Test port B' is indicated by an arrow pointing to the output of the External device. A dashed line with an arrow pointing towards Test port B is labeled '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 output, and Test port B is at the External device output. A signal source is indicated as 'From antenna connector' pointing to Test port B. + +**Figure 4.5.1.2.1-1: Receiver test ports** + +#### 4.5.1.2.2 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 (D.32), it is sufficient to apply the specified test signal at any one of the receiver *antenna connectors*. + +For a *BS type 1-C* supporting multi-band operation, multi-band tests for ACS, 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 connector* at a time. *Antenna connectors* to which no signals are applied are terminated. + +#### 4.5.1.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. If the duplexer is supplied as an option by the manufacturer, sufficient tests should be repeated with and without the duplexer fitted to verify that the BS meets the requirements of the present document in both cases. + +The following tests shall be performed with the duplexer fitted, and without it fitted if this is an option: + +- 1) clause 6.2, base station output power, for the highest static power step only, if this is measured at the antenna connector; +- 2) clause 6.6, unwanted emissions; outside the BS transmit band; +- 3) clause 6.6.5.5.1.2, protection of the BS receiver; +- 4) clause 6.7, transmit intermodulation; for the testing of conformance, the carrier frequencies should be selected to minimize intermodulation products from the transmitters falling in receive channels. + +The remaining tests may be performed with or without the duplexer fitted. + +NOTE 1: When performing receiver tests with a duplexer fitted, it is important to ensure that the output from the transmitters does not affect the test apparatus. This can be achieved using a combination of attenuators, isolators and filters. + +NOTE 2: When duplexers are used, intermodulation products will be generated, not only in the duplexer but also in the antenna system. The intermodulation products generated in the antenna system are not controlled by 3GPP specifications, and may degrade during operation (e.g. due to moisture ingress). Therefore, to ensure continued satisfactory operation of a BS, an operator will normally select NR-ARFCNs to minimize intermodulation products falling on receive channels. For testing of complete conformance, an operator may specify the NR-ARFCNs to be used. + +#### 4.5.1.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.5.1.5 Ancillary RF amplifiers + +The *BS type 1-C* 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 (D.35). 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 the table below, where "x" denotes that the test is applicable: + +**Table 4.5.1.5-1: Tests applicable to ancillary RF amplifiers** + +| | Clause | TX amplifier only | RX amplifier only | TX/RX amplifiers combined (Note 1, 2) | +|--------------------------|---------------------------|-------------------|-------------------|---------------------------------------| +| Receiver tests | 7.2 | | x | x | +| | 7.4 (Narrowband blocking) | | x | x | +| | 7.5 | | x | x | +| | 7.6 | | x | x | +| | 7.7 | | x | | +| Transmitter tests | 6.2 | x | | x | +| | 6.6.2 | x | | x | +| | 6.6.3 | x | | x | +| | 6.6.4 | x | | x | +| | 6.6.5 | x | | x | +| | 6.7 | x | | x | + +NOTE 1: 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. + +NOTE 2: Unless otherwise stated, BS with both TX and RX amplifiers are tested once with both amplifiers active for each test. + +In base station output power test (clause 6.2) and reference sensitivity level test (clause 7.2) highest applicable attenuation value is applied. + +## 4.5.2 BS type 1-H + +### 4.5.2.1 Transmit configurations + +Unless otherwise stated, the conducted transmitter characteristics in clause 6 are specified at the *transceiver array boundary* at the *TAB connector(s)* with a full complement of transceiver units for the configuration in normal operating conditions. + +![Diagram of transmitter test ports for BS type 1-H.](408c4798ea60469e0728a7cbbd598668_img.jpg) + +The diagram illustrates the transmitter test ports for BS type 1-H. 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. An arrow points to connector #K with the label 'Transceiver array boundary connector TAB(n)'. Connector #1 is connected to a box labeled 'Measurement Equipment'. Connectors #2 and #K are each connected to a box labeled 'Load'. Vertical ellipsis symbols between #2 and #K indicate additional connectors. + +Diagram of transmitter test ports for BS type 1-H. + +**Figure 4.5.2.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.5.2.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 for BS type 1-H.](b7fd98a4fcc4990a613abfc31c5bdb5e_img.jpg) + +The diagram illustrates the receiver test ports for BS type 1-H. It is similar to the transmitter diagram but with a key difference: an arrow points from the 'Measurement Equipment' box to connector #1, indicating the receive test port. Connectors #2 and #K are still connected to 'Load' boxes. The 'transceiver unit array', 'transceiver array boundary', and 'Transceiver array boundary connector TAB(n)' labels and components are identical to the transmitter diagram. + +Diagram of receiver test ports for BS type 1-H. + +**Figure 4.5.2.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.5.2.3 Power supply options + +If the *BS type 1-H* 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.5.3 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.5 and 7.6 shall be measured only for frequencies above 20 MHz with the integrated Iuant BS modem switched ON. + +### 4.6 Manufacturer declarations + +The following BS declarations listed in table 4.6-1, when applicable to the BS under test, are required to be provided by the manufacturer for the conducted requirements testing of the *BS type 1-C* and *BS type 1-H*. + +For the *BS type 1-H* declarations required for the radiated requirements testing, refer to TS 38.141-2 [3]. + +**Table 4.6-1 Manufacturer declarations for BS type 1-C and BS type 1-H conducted test requirements** + +| Declaration identifier | Declaration | Description | Applicability | | +|------------------------|-------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------| +| | | | BS type 1-C | BS type 1-H | +| D.1 | BS requirements set | Declaration of one of the NR base station requirement's set as defined for BS type 1-C , or BS type 1-H . | x | x | +| D.2 | BS class | BS class of the BS, declared as Wide Area BS, Medium Range BS, or Local Area BS. | x | x | +| D.3 | Operating bands and frequency ranges | List of NR operating band(s) supported by single-band connector(s) and/or multi-band 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 antenna connector for BS type 1-C , or TAB connector for BS type 1-H . | x | x | +| D.4 | Spurious emission category | Declare the 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 [5]. | x | x | +| D.5 | 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.4.5.6 apply. (Note 3, Note 6). | x | x | +| D.6 | 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, PHS and/or NR operating in another band are deployed. | x | x | +| D.7 | 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. | x | x | +| D.8 | Single band connector or multi-band connector | Declaration of the single band or multi-band capability of single band connector(s) or multi-band connector(s) , declared for every connector. | x | x | +| D.9 | Contiguous or non-contiguous spectrum operation support | Ability to support contiguous or non-contiguous (or both) frequency distribution of carriers when operating multi-carrier. Declared per single band connector or multi-band connector , per operating band . | x | x | +| D.10 | void | void | x | x | +| D.11 | Maximum Base Station RF Bandwidth | Maximum Base Station RF Bandwidth in the operating band for single-band operation. Declared per supported operating band , per antenna connector for BS type 1-C , or TAB connector for BS type 1-H . (Note 2) | x | x | +| D.12 | Maximum Base Station RF Bandwidth for multi-band operation | Maximum Base Station RF Bandwidth for multi-band operation. Declared per supported operating band , per antenna connector for BS type 1-C , or TAB connector for BS type 1-H . | x | x | + +| | | | | | +|------|----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---| +| D.13 | Total RF bandwidth ( $BW_{tot}$ ) | Total RF bandwidth $BW_{tot}$ of transmitter and receiver, declared per the band combinations (D.27). | x | x | +| D.14 | NR supported channel bandwidths and SCS | NR supported SCS and channel bandwidths per supported SCS. Declared per supported operating band , per antenna connector for BS type 1-C, or TAB connector for BS type 1-H. | x | x | +| D.15 | CA only operation | Declaration of CA-only operation (with equal power spectral density among carriers) but not multiple carriers, declared per operating band per antenna connector for BS type 1-C, or TAB connector for BS type 1-H. | x | x | +| D.16 | Single or multiple carrier | Capable of operating with a single carrier (only) or multiple carriers. Declared per supported operating band , per antenna connector for BS type 1-C, or TAB connector for BS type 1-H. | x | x | +| D.17 | Maximum number of supported carriers per operating band in single band operation | Maximum number of supported carriers per supported operation band in single band operation. Declared per supported operating band , per antenna connector for BS type 1-C, or TAB connector for BS type 1-H. (Note 2) | x | x | +| D.18 | Maximum number of supported carriers per operating band in multi-band operation | Maximum number of supported carriers per supported operation band in multi-band operation. (Note 2) | x | x | +| D.19 | Total maximum number of supported carriers in multi-band operation | Maximum number of supported carriers for all supported operating bands in multi-band operation. Declared for all connectors (D.18). | x | x | +| D.20 | Other band combination multi-band restrictions | Declare any other limitations under simultaneous operation in the declared band combinations (D.35) for each multi-band connector which have any impact on the test configuration generation. Declared for every multi-band connector . | x | x | +| D.21 | Rated carrier output power ( $P_{rated,c,AC}$ , or $P_{rated,c,TABC}$ ) | Conducted rated carrier output power, per single band connector or multi-band connector . Declared per supported operating band , per antenna connector for BS type 1-C, or TAB connector for BS type 1-H. (Note 1, 2, 7) | x | x | +| D.22 | Rated total output power ( $P_{rated,t,AC}$ , or $P_{rated,t,TABC}$ ) | Conducted total rated output power. Declared per supported operating band , per antenna connector for BS type 1-C, or TAB connector for BS type 1-H. For multi-band connectors declared for each supported operating band in each supported band combination. (Note 1, 2, 7) | x | x | +| D.23 | Rated multi-band total output power, $P_{rated,MB,TABC}$ | Conducted multi-band rated total output power. Declared per supported operating band combinations, per multi-band connector . (Note 1, 7) | x | x | +| D.24 | $N_{cells}$ | Number corresponding to the minimum number of cells that can be transmitted by a BS in a particular operating band with transmission on all TAB connectors supporting the operating band . | | x | +| D.25 | Maximum supported power difference between carriers | Maximum supported power difference between carriers. Declared per supported operating band , per antenna connector for BS type 1-C, or TAB connector for BS type 1-H. | x | x | + +| | | | | | +|------|-----------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---| +| D.26 | Maximum supported power difference between carriers is different operating bands | Supported power difference between any two carriers in any two different supported operating bands . Declared per supported operating band combination, per multi-band connector . | x | x | +| D.27 | Operating band combination support | List of operating bands combinations supported by single-band connector(s) and/or multi-band connector(s) of the BS. Declared per antenna connector for BS type 1-C, or TAB connector for BS type 1-H. | x | x | +| D.28 | void | void | x | x | +| D.29 | Intra-system interfering signal declaration list | List of single band connector(s) or multi-band connector(s) 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. | | x | +| D.30 | Intra-system interfering signal level | The interfering signal level in dBm. Declared per supported operating band , per TAB connector for BS type 1-H covered by D.29. | | x | +| D.31 | TAE groups | Set of declared TAB connector beam forming groups on which the TAE requirements apply. All TAB connectors belong to at least one TAB connector beam forming group (even if it's a TAB connector beam forming group consisting of one 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 per supported operating band . | | x | +| D.32 | Equivalent connectors | List of antenna connectors of BS type 1-C, or TAB connector of BS type 1-H, which have been declared equivalent.
Equivalent connectors imply that the antenna connector of BS type 1-C, or TAB connector of BS type 1-H, are expected to behave in the same way when presented with identical signals under the same operating conditions. All declarations made for the antenna connector of BS type 1-C, or TAB connector of BS type 1-H are identical and the transmitter unit and/or receiver unit driving the antenna connector of BS type 1-C or TAB connector of BS type 1-H are of identical design. | x | x | +| D.33 | 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 BS type 1-H setting corresponding to the declared minimum number of cells ( $N_{\text{cells}}$ ) with transmission on all TAB connectors supporting an operating band . | | x | + +| | | | | | +|-------|--------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---| +| D.34 | TAB connector TX min cell group | Declared group of TAB connectors to which TX requirements are applied. This declaration corresponds to group of TAB connectors which are responsible for transmitting a cell when the BS type 1-H setting corresponding to the declared minimum number of cells ( $N_{cells}$ ) with transmission on all TAB connectors supporting an operating band . | | x | +| D.35 | Connecting network loss range for BS testing with ancillary RF amplifiers | Declaration of the range of connecting network losses (in dB) for BS type 1-C testing with ancillary Tx RF amplifier only, or with Rx RF amplifier only, or with combined Tx/Rx RF amplifiers. (Note 4) | x | | +| D.36 | Relation between supported maximum RF bandwidth, number of carriers and Rated total output power | If the rated total output power and total number of supported carriers are not simultaneously supported, the manufacturer shall declare the following additional parameters:
  • - The reduced number of supported carriers at the rated total output power;
  • - The reduced total output power at the maximum number of supported carriers.
| x | x | +| D.37 | 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. | | x | +| D.38 | Inter-band CA | Band combinations declared to support inter-band CA (per CA capable multi-band connector(s) , as in D.15).
Declared for every multi-band connector which support CA. | x | x | +| D.39 | Intra-band contiguous CA | Bands declared to support intra-band contiguous CA (per CA capable single band connector(s) or multi-band connector(s) , as in D.15).
Declared per antenna connector for BS type 1-C , or TAB connector for BS type 1-H . | x | x | +| D.40 | Intra-band non-contiguous CA | Bands declared to support intra-band non-contiguous CA (per CA capable single band connector(s) or multi-band connector(s) , as in D.15).
Declared per antenna connector for BS type 1-C , or TAB connector for BS type 1-H . | x | x | +| D.41 | NB-IoT operation | Manufacturer shall declare the support of NB-IoT operation in NR in-band and the number of supported NB-IoT carriers in total and for each supported band, frequency range and channel bandwidth. | x | | +| D.42 | NB-IoT sub-carrier spacing | If the BS supports NB-IoT operation in NR in-band, manufacturer shall declare if it supports 15 kHz sub-carrier spacing, 3.75 kHz sub-carrier spacing, or both for NPUSCH. | x | | +| D.43 | NB-IoT power dynamic range | 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 of +6dB or +3dB as specified in clause 6.3.4 of TS 38.104 [2] (Note 5). | x | | +| D.100 | PUSCH mapping type | Declaration of the supported PUSCH mapping type as specified in TS 38.211 [17], i.e., type A, type B or both. | x | x | + +| | | | | | +|-------|------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---| +| D.101 | PUSCH additional DM-RS positions | Declaration of the supported additional DM-RS position(s), i.e., pos0, pos1 or both. | | | +| D.102 | PUCCH format | Declaration of the supported PUCCH format(s) as specified in TS 38.211 [17], i.e., format 0, format 1, format 2, format 3, format 4. | x | x | +| D.103 | PRACH format and SCS | Declaration of the supported PRACH format(s) as specified in TS 38.211 [17], i.e., format: 0, A1, A2, A3, B4, C0, C2.
Declaration of the supported SCS(s) per supported PRACH format with short sequence, as specified in TS 38.211 [17], i.e., 15 kHz, 30 kHz or both. | x | x | +| D.104 | Additional DM-RS for PUCCH format 3 | Declaration of the supported additional DM-RS for PUCCH format 3: without additional DM-RS, with additional DM-RS or both. | x | x | +| D.105 | Additional DM-RS for PUCCH format 4 | Declaration of the supported additional DM-RS for PUCCH format 4: without additional DM-RS, with additional DM-RS or both. | x | x | +| D.106 | PUCCH multi-slot | Declaration of multi-slot PUCCH support. | x | x | +| D.107 | UL CA | For the highest supported SCS, declaration of the carrier combination with the largest aggregated bandwidth. If there is more than one combination, the carrier combination with the largest number of carriers shall be declared. | x | x | +| D.108 | High speed train | Declaration of high speed train scenario support, i.e. HST support or no HST support | x | x | +| D.109 | Maximum speed of high speed train for PUSCH | Declaration of supported maximum speed for high speed train scenario, i.e. 350 km/h or 500 km/h. This declaration is applicable to PUSCH for high speed train and UL timing adjustment only if BS declares to support high speed train in D.108. | x | X | +| D.110 | PRACH format for high speed train | Declaration of supported PRACH format(s) for high speed train scenario, i.e. format 0 restricted set type A, format 0 restricted set type B, format A2, format B4, format C2.
This declaration is applicable to PRACH for high speed train only if BS declares to support high speed train in D.108. | x | x | +| D.111 | Interlaced formats | Declaration of support of interlaced PUSCH and PUCCH formats. | x | x | +| D.112 | PRACH format with $L_{RA} = 1151$ for 15 kHz SCS and $L_{RA} = 571$ for 30 kHz SCS | Declaration of the supported PRACH format(s) as specified in TS 38.211 [17], i.e., format: A2, B4, C2.

Declaration of the supported SCS(s) per supported PRACH format as specified in TS 38.211 [17], i.e., 15 kHz, 30 kHz or both. | x | x | +| D.113 | CG-UCI | Declaration of support of GC-UCI multiplexed on PUSCH as specified in TS 38.211 [17]. | x | x | +| D.114 | 2-step RA | Declaration of support of 2-step RA type. | x | x | +| D.115 | PUSCH 256QAM | Declaration of PUSCH 256QAM support | x | x | +| D.116 | PUCCH sub-slot based repetition formats | Declaration of PUCCH sub-slot based repetition formats | x | x | +| D.117 | PUSCH TB over Multi-slots | BS support TBoMS over physical consecutive UL slots | x | x | +| D.118 | PUSCH TB over Multi-slots | BS support TBoMS over physical non-consecutive UL slots | x | x | + +| | | | | | +|-------|---------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|---|---| +| D.119 | Supported SCS for TDD PUSCH DM-RS bundling and PUCCH DM-RS bundling | Declaration of supported SCS for TDD PUSCH DM-RS bundling and and PUCCH DM-RS bundling and, i.e. {15kHz, 30kHz, 60kHz 120kHz} | x | x | +| D.120 | Supported FDD PUSCH DM-RS bundling and and PUCCH DM-RS bundling and | Declaration of supporting FDD PUSCH DM-RS bundling and PUCCH DM-RS bundling | x | x | +| D.121 | MCS index table 3 | Declaration of support MCS index table 3 as specified in TS 38.214 [18]. | x | x | +| D.122 | PUSCH repetition type A | Declaration of support PUSCH repetition type A | x | x | + +NOTE 1: 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 256QAM transmissions and the other declaration is applicable when configured neither for 256QAM nor 1024QAM transmissions. + +NOTE 2: Parameters for contiguous or non-contiguous spectrum operation in the operating band are assumed to be the same unless they are separately declared. When separately declared, they shall still use the same declaration identifier. + +NOTE 3: If BS is declared to support Band n20 (D.3), the manufacturer shall declare if the BS may operate in geographical areas allocated to broadcasting (DTT). Additionally, related declarations of the emission levels and maximum output power shall be declared. + +NOTE 4: This manufacturer declaration is optional. + +NOTE 5: This manufacturer may declare two values, one with a minimum of +6dB and the other with a minimum of +3dB. + +NOTE 6: If BS is declared to support Band n24 (D.3), the manufacturer shall declare if the BS may operate in geographical areas where FCC regulations apply. Additionally, related declarations of the emission levels and maximum output power shall be declared. + +NOTE 7: If a BS is capable of 256QAM DL operation but not capable of 1024QAM DL operation then up to 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 + +## 4.7 Test configurations + +### 4.7.1 General + +The test configurations shall be constructed using the methods defined below, subject to the parameters declared by the manufacturer for the supported RF configurations as listed in clause 4.6. The test configurations to use for conformance testing are defined for each supported RF configuration in clauses 4.8.3 and 4.8.4. + +The applicable test models for generation of the carrier transmit test signal are defined in clause 4.9. + +NOTE: If required, carriers are shifted to align with the channel raster. + +### 4.7.2 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.7.2-1. + +**Table 4.7.2-1: Signal to be used to build NR TCs** + +| Operating Band characteristics | | FDL_high – FDL_low < 100 MHz | FDL_high – FDL_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.7.3 NRTC1: Contiguous spectrum operation + +The purpose of test configuration NRTC1 is to test all BS requirements excluding CA occupied bandwidth. + +For NRTC1 used in receiver tests only the two outermost carriers within each supported operating band need to be generated by the test equipment; + +### 4.7.3.1 NRTC1 generation + +NRTC1 shall be constructed on a per band basis using the following method: + +- Declared maximum Base Station RF Bandwidth supported for contiguous spectrum operation (D.11) shall be used; +- Select the carrier to be tested according to 4.7.2 and place it adjacent to the lower Base Station RF Bandwidth edge. Place same signal adjacent to the upper Base Station RF Bandwidth edge. +- If NB-IoT operation in NR in-band is supported, place the power boosted NB-IoT RB at the lower outermost RB at the lower Base Station RF Bandwidth edge eligible for NB-IoT operation in NR in-band according to clause 5.7.3 of TS 36.104 [22] and the definition in clause 3.1. If more than one NB-IoT carrier is supported with NB-IoT operation in NR in-band, place the power boosted NB-IoT RB at the upper outermost RB at the upper Base Station RF Bandwidth edge eligible for NB-IoT operation in NR in-band. +- For transmitter tests, select as many carriers (according to 4.7.2) that the BS supports within an *operating band* and fit in the rest of the declared maximum Base Station RF Bandwidth (D.11). Place the carriers adjacent to each other starting from the upper Base Station RF Bandwidth edge. The nominal channel spacing defined in TS 38.104 [2], clause 5.4.1 shall apply. + +The test configuration should be constructed sequentially on a per band basis for all component carriers of the inter-band CA bands declared to be supported by the BS and are transmitted using the same *antenna connector*. All configured component carriers are transmitted simultaneously in the tests where the transmitter should be ON. + +### 4.7.3.2 NRTC1 power allocation + +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 (Prated,t,AC, or Prated,t,TABC, D.22) according to the manufacturer's declaration in clause 4.6. + +## 4.7.4 NRTC2: Contiguous CA occupied bandwidth + +NRTC2 in this clause is used to test CA occupied bandwidth. + +### 4.7.4.1 NRTC2 generation + +The CA specific test configuration should be constructed on a per band basis using the following method: + +- Of all component carrier combinations supported by the BS, those which have smallest and largest sum of channel bandwidth of component carriers, 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 with the smallest supported subcarrier spacing at the lower Base Station RF Bandwidth edge. +- Of the combinations selected in the previous step, select one with the narrowest carrier with the smallest supported subcarrier spacing 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 with the smallest supported subcarrier spacing being adjacent to the lowest carrier. +- If there are multiple combinations fulfilling previous steps, select the one with the widest carrier with the smallest supported subcarrier spacing being adjacent to the highest carrier. +- If there are multiple combinations fulfilling previous steps, select the one with the widest carrier with the smallest supported subcarrier spacing 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 channel spacing defined in TS 38.104 [2], clause 5.4.1 shall apply. + +#### 4.7.4.2 NRTC2 power allocation + +Set the power spectral density of each carrier to be the same level so that the sum of the carrier powers equals the rated total output power ( $P_{\text{rated,t,AC}}$ or $P_{\text{rated,t,TABC}}$ , D.22) for NR according to the manufacturer's declaration in clause 4.6. + +#### 4.7.5 NRTC3: Non-contiguous spectrum operation + +The purpose of NRTC3 is to test all BS requirements excluding CA occupied bandwidth. + +For NRTC3 used in receiver tests, outermost carriers for each sub-block need to be generated by the test equipment; other supported carriers are optional to be generated. + +##### 4.7.5.1 NRTC3 generation + +NRTC3 is constructed on a per band basis using the following method: + +- The Base Station RF Bandwidth shall be the maximum Base Station RF Bandwidth supported for non-contiguous spectrum operation (D.11). The Base Station RF Bandwidth consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum supported Base Station RF Bandwidth (D.11). +- Select the carrier to be tested according to 4.7.2. Place it adjacent to the upper Base Station RF Bandwidth edge and another carrier (as described in 4.7.2) adjacent to the lower Base Station RF Bandwidth edge. +- If NB-IoT operation in NR in-band is supported, place the power boosted NB-IoT RB at the lower outermost RB at the lower Base Station RF Bandwidth edge eligible for NB-IoT operation in NR in-band according to clause 5.7.3 of TS 36.104 [22] and the definition in clause 3.1. If more than one NB-IoT carrier is supported with + +NB-IoT operation in NR in-band, place the power boosted NB-IoT RB at the upper outermost RB at the upper Base Station RF Bandwidth edge eligible for NB-IoT operation in NR in-band. + +- For single-band operation receiver tests, if the remaining gap is at least 15 MHz (or 60 MHz if channel bandwidth of the carrier to be tested is 20 MHz) plus two times the channel BW used in the previous step and the BS supports at least 4 carriers, place a carrier of this BW adjacent to each already placed carrier for each sub-block. The nominal channel spacing defined in TS 38.104 [2], clause 5.4.1 shall apply. +- The sub-block edges adjacent to the sub-block gap shall be determined using the specified $F_{\text{offset\_high}}$ and $F_{\text{offset\_low}}$ for the carriers adjacent to the sub-block gap. + +#### 4.7.5.2 NRTC3 power allocation + +Set the power 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,AC}}$ , or $P_{\text{rated,t,TABC}}$ , D.22) according to the manufacturer's declaration in clause 4.6. + +### 4.7.6 NRTC4: Multi-band test configuration for full carrier allocation + +The purpose of NRTC4 is to test multi-band operation aspects considering maximum supported number of carriers. + +#### 4.7.6.1 NRTC4 generation + +NRTC4 is based on re-using the previously specified test configurations applicable per band involved in multi-band operation. It 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 (D.12). +- The number of carriers of each supported *operating band* shall be the declared maximum number of supported carriers per operating band in multi-band operation (D. 18). Carriers shall be selected according to 4.7.2 and shall first be placed at the outermost edges of the declared maximum Radio Bandwidth. Additional carriers shall next be placed at the Base Station RF Bandwidths 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 NRTC1, 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. +- If only three carriers are supported, 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* in the other band. +- If the sum of the maximum Base Station RF Bandwidths of each supported *operating bands* is larger than the declared *Total RF Bandwidth* $BW_{\text{tot}}$ (D.13) 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 carriers per operating band in multi-band operation (D.18) is larger than the declared total maximum number of supported carriers in multi-band operation (D. 19), 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. + +#### 4.7.6.2 NRTC4 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 ( $P_{\text{rated,t,AC}}$ or $P_{\text{rated,t,TABC}}$ , D.22) 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 output power declared for that carrier, the exceeded power shall, if possible, be reallocated into the other carriers. + +#### 4.7.7 NRTC5: Multi-band test configuration with high PSD per carrier + +The purpose of NRTC5 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. + +##### 4.7.7.1 NRTC5 generation + +NRTC5 is based on re-using the existing test configuration applicable per band involved in multi-band operation. It 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 (D.12). +- 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 is limited to two per band. Carriers shall be selected according to 4.7.2 and shall first be placed at the outermost edges of the declared Maximum Radio Bandwidth for outermost bands and at the Base Station RF Bandwidths edges for middle band(s) if any. Additional carriers shall next be placed at the Base Station RF Bandwidths edges, if possible. +- Each concerned band shall be considered as an independent band and the carrier placement in each band shall be according to NRTC3, where the declared parameters for multi-band operation shall apply. Narrowest supported NR channel bandwidth and smallest subcarrier spacing shall be used in the test configuration. +- 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* $BW_{\text{tot}}$ (D.13) 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* $BW_{\text{tot}}$ of transmitter and receiver is not exceeded and vice versa. + +##### 4.7.7.2 NRTC5 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 total rated output power ( $P_{\text{rated,t,AC}}$ or $P_{\text{rated,t,TABC}}$ , D.22) 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 output power declared for that carrier, the exceeded power shall, if possible, be reallocated into the other carriers. + +## 4.7.8 NRTC6: Non-contiguous spectrum operation in band n46, n96 and n102 + +The purpose of test configuration NRTC6 is to test operating band unwanted emission (OBUE) for one or two non-transmitted 20 MHz channels for band n46, n96 and n102 operation with 60 MHz and or 80 MHz channel bandwidth. + +### 4.7.8.1 NRTC6 generation + +NRTC6 shall be constructed on a per band basis using the following method: + +- Declared maximum Base Station RF Bandwidth supported for contiguous spectrum operation (D.11) shall be used. +- For 60 MHz channel bandwidth, place 60 MHz carrier with ON-OFF-ON pattern for non-contiguous transmission at the upper edge of the BS channel bandwidth for the carrier adjacent to the upper Base Station RF Bandwidth edge and 60 MHz carrier with ON-OFF-ON pattern for non-contiguous transmission at the lower edge of the BS channel bandwidth for the carrier adjacent to the lower Base Station RF Bandwidth edge. +- For 80MHz channel bandwidth, place 80 MHz carrier with ON-OFF-OFF-ON pattern for non-contiguous transmission at the upper edge of the BS channel bandwidth for the carrier adjacent to the upper Base Station RF Bandwidth edge and 80 MHz carrier with ON-OFF-OFF-ON pattern for non-contiguous transmission at the lower edge of the BS channel bandwidth for the carrier adjacent to the lower Base Station RF Bandwidth edge. +- For transmitter tests, select as many 60 MHz channel bandwidth (with ON-OFF-ON pattern for non-contiguous transmission) or 80 MHz channel bandwidth (with ON-OFF-OFF-ON pattern for non-contiguous transmission) that the BS supports within an *operating band* and fit in the rest of the declared maximum Base Station RF Bandwidth (D.11). Place the 60 MHz channel bandwidth (with ON-OFF-ON pattern for non-contiguous transmission) or 80 MHz channel bandwidth (with ON-OFF-OFF-ON pattern for non-contiguous transmission) adjacent to each other starting from the upper Base Station RF Bandwidth edge. The nominal channel spacing defined in TS 38.104 [2], clause 5.4.1 shall apply. + +The test configuration should be constructed sequentially on a per band basis for all component carriers of the inter-band CA bands declared to be supported by the BS and are transmitted using the same *antenna connector*. All configured component carriers are transmitted simultaneously in the tests where the transmitter should be ON. + +### 4.7.8.2 NRTC6 power allocation + +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,AC}}$ , or $P_{\text{rated,t,TABC}}$ , D.22) according to the manufacturer's declaration in clause 4.6. + +## 4.8 Applicability of requirements + +### 4.8.1 General + +### 4.8.2 Requirement set applicability + +In table 4.8.2-1, the requirement applicability for each requirement set is defined. For each requirement, the applicable requirement clause in the specification is identified. + +**Table 4.8.2-1: Requirement set applicability** + +| Requirement | Requirement set | | +|-----------------------------------|-----------------|-----------| +| | 1-C | 1-H | +| BS output power | 6.2 | 6.2 | +| Output power dynamics | 6.3 | 6.3 | +| Transmit ON/OFF power | 6.4 | 6.4 | +| Transmitted signal quality | 6.5 | 6.5 | +| Occupied bandwidth | 6.6.2 | 6.6.2 | +| ACLR | 6.6.3.5.3 | 6.6.3.5.4 | +| Operating band unwanted emissions | 6.6.4.5.7 | 6.6.4.5.8 | +| Transmitter spurious emissions | 6.6.5.5.3 | 6.6.5.5.4 | +| Transmitter intermodulation | 6.7.5.1 | 6.7.5.2 | +| Reference sensitivity level | 7.2 | 7.2 | +| Dynamic range | 7.3 | 7.3 | +| In-band selectivity and blocking | 7.4 | 7.4 | +| Out-of-band blocking | 7.5 | 7.5 | +| Receiver spurious emissions | 7.6.5.2 | 7.6.5.3 | +| Receiver intermodulation | 7.7 | 7.7 | +| In-channel selectivity | 7.8 | 7.8 | +| Performance requirements | 8 | 8 | + +### 4.8.3 Applicability of test configurations for single-band operation + +The applicable test configurations are specified in the tables below for each the supported RF configuration, which shall be declared according to clause 4.6. The generation and power allocation for each test configuration is defined in clause 4.7. This clause contains the test configurations for a BS capable of single carrier, multi-carrier and/or CA operation in both contiguous and non-contiguous spectrum in single band. + +For a BS declared to be capable of single carrier operation only (D.16), a single carrier (SC) shall be used for testing. + +For a BS declared to support multi-carrier and/or CA operation in contiguous spectrum within a single band (D.15-D.16), the test configurations in the second column of table 4.8.3-1 shall be used for testing. + +For a BS declared to support multi-carrier and/or CA operation in contiguous and non-contiguous spectrum within a single band (D.15-D.16) and where the parameters in the manufacture's declaration according to clause 4.6 are identical for contiguous (C) and non-contiguous (NC) spectrum operation (D.9), the test configurations in the third column of table 4.8.3-1 shall be used for testing. + +For a BS declared to support multi-carrier and/or CA in operation contiguous and non-contiguous spectrum within a single band (D.15-D.16) and where the parameters in the manufacture's declaration according to clause 4.6 are not identical for contiguous (C) and non-contiguous (NC) spectrum operation (D.9), the test configurations in the fourth column of table 4.8.3-1 shall be used for testing. + +For a BS declared to support band n46, n96 and/or band n102 operation with 60 MHz and or 80 MHz channel bandwidth with non-contiguous transmission, the test configuration NRTC6 shall be used for operation band unwanted emission. + +Unless otherwise stated, single carrier configuration (SC) tests shall be performed using signal with narrowest supported channel bandwidth and the smallest supported sub-carrier spacing. + +**Table 4.8.3-1: Test configurations for a BS capable of multi-carrier and/or CA in a single band** + +| BS test case | Contiguous spectrum capable BS | C and NC capable BS with identical parameters | C and NC capable BS with different parameters | +|--------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|------------------------------------------------| +| Base station output power | NRTC1 | NRTC1 | NRTC1, NRTC3 | +| RE Power control dynamic range | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| Total power dynamic range (Note 3) | SC | SC | SC | +| Transmit ON/OFF power (only applied for NR TDD BS) | NRTC1 | NRTC1 | NRTC1, NRTC3 | +| Frequency error | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| Error Vector Magnitude (Note 3) | NRTC1 | NRTC1 | NRTC1, NRTC3 | +| Time alignment error (Note 3) | NRTC1 | NRTC1 | NRTC1, NRTC3 | +| Occupied bandwidth | SC, NRTC2 (Note 1) | SC, NRTC2 (Note 1) | SC, NRTC2 (Note 1) | +| Adjacent Channel Leakage power Ratio (ACLR) | NRTC1 | NRTC3 | NRTC1, NRTC3 | +| Cumulative ACLR requirement in non-contiguous spectrum | - | NRTC3 | NRTC3 | +| Operating band unwanted emissions | NRTC1, SC (Note 2)
NRTC6 (Note 4) | NRTC1, NRTC3,
SC (Note 2)
NRTC6 (Note 4) | NRTC1, NRTC3,
SC (Note 2)
NRTC6 (Note 4) | +| Transmitter spurious emissions | NRTC1 | NRTC3 | NRTC1, NRTC3 | +| Transmitter intermodulation | NRTC1 | NRTC1, NRTC3 | NRTC1, NRTC3 | +| Reference sensitivity level | SC | SC | SC | +| Dynamic range | SC | SC | SC | +| Adjacent Channel Selectivity (ACS) | NRTC1 | NRTC3 | NRTC1, NRTC3 | +| In-band blocking | NRTC1 | NRTC3 | NRTC1, NRTC3 | +| Out-of-band blocking | NRTC1 | NRTC3 | NRTC1, NRTC3 | +| Receiver spurious emissions | NRTC1 | NRTC3 | NRTC1, NRTC3 | +| Receiver intermodulation | NRTC1 | NRTC3 | NRTC1, NRTC3 | +| In-channel selectivity | SC | SC | SC | +| Note 1: | NRTC2 is only applicable when contiguous CA is supported. | | | +| Note 2: | OBUE SC shall be tested using the widest supported channel bandwidth and the highest supported sub-carrier spacing. | | | +| Note 3: | There is no specific test for NB-IoT operation in NR in-band for these requirements, tests could be performed using NR signal only, without NB-IoT. | | | +| Note 4: | NRTC6 is only applicable for band n46, n96 and n102 when 60 MHz or 80 MHz channel bandwidth with non-contiguous transmission is supported. | | | + +#### 4.8.4 Applicability of test configurations for multi-band operation + +For a BS declared to be capable of multi-band operation, the test configuration in table 4.8.4-1 and/or table 4.8.3-1 shall be used for testing. In the case where multiple bands are mapped on common *multi-band connector*, the test configuration in the second column of table 4.8.4-1 shall be used. In the case where multiple bands are mapped on common *single-band connector*, the test configuration in table 4.8.3-1 shall be used. In the case where multiple bands are mapped on separate *single-band connector* or *multi-band connector*, the test configuration in the third column of table 4.8.4-1 shall be used. + +Unless otherwise stated, single carrier configuration (SC) tests shall be performed using signal with narrowest supported channel bandwidth and the smallest supported sub-carrier spacing. + +**Table 4.8.4-1: Test configuration for a BS capable of multi-band operation** + +| BS test case | Test configuration | | +|--------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------| +| | Common connector | Separate connectors | +| Base station output power | NRTC1/3 (Note 1), NRTC4 | NRTC1/3 (Note 1), NRTC4 | +| RE Power control dynamic range | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| Total power dynamic range (Note 8) | SC | SC | +| Transmit ON/OFF power (only applied for NR TDD BS) | NRTC4 | NRTC4 | +| Frequency error | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| Error Vector Magnitude (Note 8) | NRTC1/3 (Note 1), NRTC4 | NRTC1/3 (Note 1), NRTC4 | +| Time alignment error (Note 8) | NRTC1/3 (Note 1), NRTC5 (Note 2) | NRTC1/3 (Note 1), NRTC5 (Note 2) | +| Occupied bandwidth | SC, NRTC2 (Note 3) | SC, NRTC2 (Note 3) | +| Adjacent Channel Leakage power Ratio (ACLR) | NRTC1/3 (Note 1), NRTC5 (Note 4) | NRTC1/3 (Note 1, 5), NRTC5 (Note 4, 5) | +| Cumulative ACLR requirement in non-contiguous spectrum | NRTC3 (Note 1), NRTC5 (Note 4) | NRTC3 (Note 1, 5) | +| Operating band unwanted emissions | NRTC1/3 (Note 1), NRTC5, SC (Note 7)
NRTC6 (Note 9) | NRTC1/3 (Note 1, 5), NRTC5 (Note 5),
SC (Note 7)
NRTC6 (Note 9) | +| Transmitter spurious emissions | NRTC1/3 (Note 1), NRTC5 | NRTC1/3 (Note 1, 5), NRTC5 (Note 5) | +| Transmitter intermodulation | NRTC1/3 (Note 1) | NRTC1/3 (Note 1, 5) | +| Reference sensitivity level | SC | SC | +| Dynamic range | SC | SC | +| Adjacent Channel Selectivity(ACS) | NRTC5 | NRTC1/3 (Note 1), NRTC5 (Note 6) | +| In-band blocking | NRTC5 | NRTC1/3 (Note 1), NRTC5 (Note 6) | +| Out-of-band blocking | NRTC5 | NRTC1/3 (Note 1), NRTC5 (Note 6) | +| Receiver spurious emissions | NRTC1/3 (Note 1), NRTC5 | NRTC1/3 (Note 1, 5), NRTC5 (Note 5) | +| Receiver intermodulation | NRTC5 | NRTC1/3 (Note 1), NRTC5 (Note 6) | +| In-channel selectivity | SC | SC | +| Note 1: | NRTC1 and/or NRTC3 shall be applied in each supported operating band. | | +| Note 2: | NRTC5 is only applicable when inter-band CA is supported. | | +| Note 3: | NRTC2 is only applicable when contiguous CA is supported. | | +| Note 4: | NRTC5 may be applied for Inter RF Bandwidth gap only. | | +| Note 5: | For single-band operation test, other antenna connector(s) is (are) terminated. | | +| Note 6: | NRTC5 is only applicable for multi-band receiver. | | +| Note 7: | OBUE SC shall be tested using the widest supported channel bandwidth and the highest supported sub-carrier spacing. | | +| Note 8: | There is no specific test for NB-IoT operation in NR in-band for these requirements, tests could be performed using NR signal only, without NB-IoT. | | +| Note 9: | NRTC6 is only applicable for band n46, n96 and n102 when 60 MHz or 80 MHz channel bandwidth with non-contiguous transmission is supported. | | + +## 4.8.5 Additional conformance + +For a BS type 1-C additionally conforming to TS 37.141 [26], conformance to some of the RF requirements in the present document can be demonstrated through the corresponding requirements in TS 37.141 [26] as listed in Table 4.8.5-1. + +**Table 4.8.5-1: Alternative RF test requirements for a BS additionally conforming to TS 37.141 [26]** + +| RF requirement | Clause in the present document | Alternative clause in TS 37.141 [26] | +|--------------------------------------|--------------------------------|----------------------------------------------| +| Base station output power | 6.2.5 | 6.2.1.5 | +| Transmit ON/OFF power | 6.4 | 6.4 | +| Unwanted emissions | | | +| Transmitter spurious emissions | 6.6.5.5(except for 6.6.5.5.4) | 6.6.1.5 (except for 6.6.1.5.3) | +| Operating band unwanted emissions | 6.6.4.5(except for 6.6.4.5.8) | 6.6.2.5 (except for 6.6.2.5.3 and 6.6.2.5.4) | +| Transmitter intermodulation | 6.7.5.1 | 6.7.5.1 | +| Narrowband blocking | 7.4.2.5 | 7.4.5.2 | +| Blocking | 7.4.2.5 | 7.4.5.1 | +| Out-of-band blocking | 7.5.5.1 | 7.5.5.1 | +| Co-location with other base stations | 7.5.5.2 | 7.5.5.2 | +| Receiver spurious emissions | 7.6.5(except for 7.6.5.3) | 7.6.5.1 | +| Intermodulation | 7.7.5 | 7.7.5.1 | +| Narrowband intermodulation | 7.7.5 | 7.7.5.2 | + +For a BS type 1-H additionally conforming to TS 37.145-1 [27], conformance to some of the RF requirements in the present document can be demonstrated through the corresponding requirements in TS 37.145-1 [27] as listed in Table 4.8.5-2. + +**Table 4.8.5-2: Alternative RF test requirements for a BS additionally conforming to TS 37.145-1 [27]** + +| RF requirement | Clause in the present document | Alternative clause in TS 37.145-1 [27] | +|--------------------------------------|--------------------------------|----------------------------------------| +| Base station output power | 6.2.5 | 6.2.2.5 | +| Transmit ON/OFF power | 6.4 | 6.4 | +| Unwanted emissions | | | +| Transmitter spurious emissions | 6.6.5.5(except for 6.6.5.5.3) | 6.6.6.5 | +| Operating band unwanted emissions | 6.6.4.5(except for 6.6.4.5.7) | 6.6.5.5 (except for 6.6.5.5.5) | +| Transmitter intermodulation | 6.7.5.2 | 6.7.5.1 | +| Narrowband blocking | 7.4.2.5 | 7.4.5.1.2 | +| Blocking | 7.4.2.5 | 7.4.5.1.1 | +| Out-of-band blocking | 7.5.5.1 | 7.5.5.1.1 | +| Co-location with other base stations | 7.5.5.2 | 7.5.5.1.2 | +| Receiver spurious emissions | 7.6.5(except for 7.6.5.2) | 7.6.5.2.1 | +| Intermodulation | 7.7.5 | 7.7.5.1.1 | +| Narrowband intermodulation | 7.7.5 | 7.7.5.1.2 | + +## 4.9 RF channels and test models + +### 4.9.1 RF channels + +For the single carrier testing many tests in this TS are performed with appropriate frequencies in the bottom, middle and top channels of the supported frequency range of the BS. These are denoted as RF channels B (bottom), M (middle) and T (top). + +Unless otherwise stated, the test 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. +- $T_{\text{RFBW}}$ : maximum Base Station RF Bandwidth located at the top of the supported frequency range in the operating band. + +Occupied bandwidth test in this TS is performed with the *aggregated BS 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 BS channel bandwidth* located at the bottom of the supported frequency range in each operating band; +- $M_{\text{BW Channel CA}}$ : *aggregated BS channel bandwidth* located close in the middle of the supported frequency range in each operating band; +- $T_{\text{BW Channel CA}}$ : *aggregated BS channel bandwidth* located at the top of the supported frequency range in each operating band. + +For BS capable of multi-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 lowest operating band and at the highest possible simultaneous frequency position, within the Maximum Radio Bandwidth, in the highest operating band. +- $B'_{\text{RFBW\_T RFBW}}$ : 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. + +NOTE: $B_{\text{RFBW\_T'RFBW}} = B'_{\text{RFBW\_T RFBW}} = B_{\text{RFBW\_T RFBW}}$ when the declared Maximum Radio Bandwidth spans all 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_{RFBW}$ , $M_{RFBW}$ and $T_{RFBW}$ for single band operation, $B_{BW\ Channel\ CA}$ , $M_{BW\ Channel\ CA}$ and $T_{BW\ Channel\ CA}$ for contiguous spectrum operation in each supported operating band, the position of $B_{RFBW\_T'_{RFBW}}$ and $B'_{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.9.2 Test models + +### 4.9.2.1 General + +The following clauses will describe the NR FR1 test models needed for *BS type 1-C* and *BS type 1-H*. Note that the NR FR1 test models are also applicable to *BS type 1-O* conformance testing in TS 38.141-2 [3]. + +### 4.9.2.2 FR1 test models + +The set-up of physical channels for transmitter tests shall be according to one of the NR FR1 test models (NR-FR1-TM) below. A reference to the applicable test model is made within each test. + +The following general parameters are used by all NR test models: + +- Duration is 1 radio frame (10 ms) for FDD and 2 radio frames for TDD (20 ms) +- The slots are numbered 0 to $10 \times 2^\mu - 1$ where $\mu$ is the numerology corresponding to the subcarrier spacing +- $N_{RB}$ is the maximum transmission bandwidth configuration seen in table 5.3.2-1 in TS 38.104 [2]. +- Normal CP +- Virtual resource blocks of localized type + +For FR1-TDD without NB-IoT operation in NR in-band, test models are derived based on the uplink/downlink configuration as shown in the table 4.9.2.2-1 using information element *TDD-UL-DL-ConfigCommon* as defined in TS 38.331 [19]. + +**Table 4.9.2.2-1: Configurations of TDD for *BS type 1-C* and *BS type 1-H* test models** + +| Field name | Value | | | +|----------------------------------------------------|-------|----|----| +| referenceSubcarrierSpacing (kHz) | 15 | 30 | 60 | +| Periodicity (ms) for dl-UL-TransmissionPeriodicity | 5 | 5 | 5 | +| nrofDownlinkSlots | 3 | 7 | 14 | +| nrofDownlinkSymbols | 10 | 6 | 12 | +| nrofUplinkSlots | 1 | 2 | 4 | +| nrofUplinkSymbols | 2 | 4 | 8 | + +For FR1-TDD with NB-IoT operation in NR in-band, test models are derived based on the uplink/downlink configuration as shown in the table 4.9.2.2-1a using information elements *TDD-UL-DL-ConfigCommon* and *TDD-UL-DL-ConfigDedicated* as defined in TS 38.331 [19]. + +**Table 4.9.2.2-1a: Configurations of TDD for NR with NB-IoT operation in NR in-band test models** + +| Field name | Value | +|-----------------------------------------------------------|----------------| +| Tdd-UL-DL-Configuration | | +| referenceSubcarrierSpacing | 15 | +| Periodicity (ms) for dl-UL-TransmissionPeriodicity | 5 | +| nrofDownlinkSlots | 1 | +| nrofDownlinkSymbols | 0 | +| nrofUplinkSlots | 0 | +| nrofUplinkSymbols | 0 | +| Tdd-UL-DL-ConfigDedicated | | +| nrofDownlinkSymbols | For Slot#1: 10 | +| nrofUplinkSymbols | For Slot#1: 2 | +| slotIndex | 1 | +| nrofDownlinkSymbols | 10 | +| nrofUplinkSymbols | 2 | +| slotIndex | 2,3 | +| symbols | allUplink | +| slotIndex | 4 | +| symbols | allDownlink | + +Common physical channel parameters for all NR FR1 test models are specified in the following tables: table 4.9.2.2-2 for PDCCH, table 4.9.2.2-3 and table 4.9.2.2-4 for PDSCH. Specific physical channel parameters for NR FR1 test models are described in clauses 4.9.2.2.1 to 4.9.2.2.8. + +**Table 4.9.2.2-2: Common physical channel parameters for PDCCH for BS type 1-C and BS type 1-H test models** + +| Parameter | Value | +|-------------------------------------------------|--------------| +| # of symbols used for control channel | 2 | +| Starting symbol number for control channel | 0 | +| # of CCEs allocated to PDCCH | 1 | +| Starting RB location for PDCCH | 0 | +| # of available REGs | 6 | +| Aggregation level | 1 | +| # of RBs not allocated for PDCCH in each symbol | $N_{RB} - 3$ | +| Ratio of PDCCH EPRE to DM-RS EPRE | 0 dB | +| Boosting level of control channel | 0 dB | + +**Table 4.9.2.2-3: Common physical channel parameters for PDSCH for BS type 1-C and BS type 1-H test models** + +| Parameter | Value | +|---------------------------------------------------------------|----------------------| +| Mapping type | PDSCH mapping type A | +| dmrs-TypeA-Position for the first DM-RS symbol | pos2 | +| dmrs-AdditionalPosition for additional DM-RS symbol(s) | 1 | +| dmrs-Type for comb pattern | Configuration type 1 | +| maxLength | 1 | +| Ratio of PDSCH EPRE to DM-RS EPRE | 0 dB | + +**Table 4.9.2.2-4: Common physical channel parameters for PDSCH by RNTI for BS type 1-C and BS type 1-H test models** + +| Parameter | Value | +|-----------------------------------|-------| +| PDSCH | | +| Starting symbol | 0 | +| Ratio of PDSCH EPRE to PDCCH EPRE | 0 dB | +| PDSCH | | +| Starting symbol | 0 | +| Ratio of PDSCH EPRE to PDCCH EPRE | 0 dB | +| PDSCH | | +| Starting symbol | 2 | +| Ratio of PDSCH EPRE to PDCCH EPRE | 0 dB | +| Starting PRB location | 0 | +| Number of PRBs | 3 | + +#### 4.9.2.2.1 FR1 test model 1.1 (NR-FR1-TM1.1) + +This model shall be used for tests on: + +- BS output power +- Transmit ON/OFF power +- TAE +- Unwanted emissions + - Occupied bandwidth + - ACLR + - Operating band unwanted emissions + - Transmitter spurious emissions +- Transmitter intermodulation +- Receiver spurious emissions + +Common physical channel parameters are defined in clause 4.9.2.2. Specific physical channel parameters for NR-FR1-TM1.1 are defined in table 4.9.2.2.1-1. + +**Table 4.9.2.2.1-1: Specific physical channel parameters of NR-FR1-TM1.1** + +| Parameter | Value | +|-------------------------------|--------------| +| # of PRBs PDSCH | $N_{RB} - 3$ | +| Modulation PDSCH | QPSK | +| Starting RB location of PDSCH | 3 | +| Modulation of PDSCH | QPSK | +| Starting RB location of PDSCH | 0 | + +#### 4.9.2.2.2 FR1 test model 1.2 (NR-FR1-TM1.2) + +This model shall be used for tests on: + +- Unwanted emissions + +- ACLR +- Operating band unwanted emissions + +Common physical channel parameters are defined in clause 4.9.2.2. Specific physical channel parameters for NR-FR1-TM1.2 are defined in table 4.9.2.2.2-1. + +**Table 4.9.2.2.2-1: Specific physical channel parameters of NR-FR1-TM1.2** + +| Parameter | Value | +|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------| +| Target percent of QPSK PDSCH PRBs boosted | $x=40\%$ | +| # of QPSK PDSCH RBGs which are boosted | , where P is determined from table 5.1.2.2.1-1 from TS 38.214 [18], configuration 1 column using as the size of the bandwidth part and | +| Locations of PDSCH RBGs which are boosted | and if , 1, 3, ..., | +| Level of boosting (dB) | 3 | +| # of QPSK PDSCH PRBs which are deboosted | | +| Locations of PDSCH RBGs which are deboosted | Starting at RB#3 and excluding PRBs of RBGs which are boosted | +| Level of deboosting (dB) | | +| Modulation of PDSCH PRBs with | QPSK | + +#### 4.9.2.2.3 FR1 test model 2 (NR-FR1-TM2) + +This model shall be used for tests on: + +- Total power dynamic range (lower OFDM symbol TX power limit (OSTP) at min power) +- EVM of single 64QAM PRB allocation (at min power) +- Frequency error (at min power) + +Common physical channel parameters are defined in clause 4.9.2.2. Specific physical channel parameters for NR-FR1-TM2 are defined in table 4.9.2.2.3-1. + +**Table 4.9.2.2.3-1: Specific physical channel parameters of NR-FR1-TM2** + +| Parameter | Value | | | +|-----------------------------------------|--------|----|---| +| # of 64QAM PDSCH PRBs | 1 | | | +| Level of boosting (dB) | 0 | | | +| Location of 64QAM PRB | | | | +| | Slot | RB | n | +| | $3n$ | 0 | | +| | $3n+1$ | | | +| | $3n+2$ | | | +| # of PDSCH PRBs which are not allocated | | | | + +#### 4.9.2.2.4 FR1 test model 2a (NR-FR1-TM2a) + +This model shall be used for tests on: + +- Total power dynamic range (lower OFDM symbol TX power limit (OSTP) at min power) +- EVM of single 256QAM PRB allocation (at min power) +- Frequency error (at min power) + +Common physical channel parameters are defined in clause 4.9.2.2. Physical channel parameters and numbers of the allocated PRB are defined in table 4.9.2.2.3-1 with all 64QAM PDSCH PRBs replaced by 256QAM PDSCH PRBs. + +#### 4.9.2.2.4A FR1 test model 2b (NR-FR1-TM2b) + +This model shall be used for tests on: + +- Total power dynamic range (lower OFDM symbol TX power limit (OSTP) at min power) +- EVM of single 1024QAM PRB allocation (at min power) +- Frequency error (at min power) + +Common physical channel parameters are defined in clause 4.9.2.2. Physical channel parameters and numbers of the allocated PRB are defined in table 4.9.2.2.3-1 with all 64QAM PDSCH PRBs replaced by 1024QAM PDSCH PRBs. + +#### 4.9.2.2.5 FR1 test model 3.1 (NR-FR1-TM3.1) + +This model shall be used for tests on: + +- Output power dynamics +- Total power dynamic range (upper OFDM symbol TX power limit (OSTP) at max power with all 64QAM PRBs allocated) +- Transmitted signal quality +- Frequency error +- EVM for 64QAM modulation (at max power) + +NOTE: EVM shall be evaluated over PDSCH allocated PRBs with and + +Common physical channel parameters are defined in clause 4.9.2.2. Physical channel parameters are defined in table 4.9.2.2.1-1 with all QPSK PDSCH PRBs replaced by 64QAM PDSCH PRBs. + +#### 4.9.2.2.6 FR1 test model 3.1a (NR-FR1-TM3.1a) + +This model shall be used for tests on: + +- Output power dynamics +- Total power dynamic range (upper OFDM symbol TX power limit (OSTP) at max power with all 256QAM PRBs allocated) +- Transmitted signal quality +- Frequency error + +- EVM for 256QAM modulation (at max power) + +NOTE: EVM shall be evaluated over PDSCH allocated PRBs with and + +Common physical channel parameters are defined in clause 4.9.2.2. Physical channel parameters are defined in table 4.9.2.2.1-1 with all QPSK PDSCH PRBs replaced by 256QAM PDSCH PRBs. + +#### 4.9.2.2.6A FR1 test model 3.1b (NR-FR1-TM3.1b) + +This model shall be used for tests on: + +- Output power dynamics + - Total power dynamic range (upper OFDM symbol TX power limit (OSTP) at max power with all 1024QAM PRBs allocated) +- Transmitted signal quality + - Frequency error + - EVM for 1024QAM modulation (at max power) + +NOTE: EVM shall be evaluated over PDSCH allocated PRBs with and + +Common physical channel parameters are defined in clause 4.9.2.2. Physical channel parameters are defined in table 4.9.2.2.1-1 with all QPSK PDSCH PRBs replaced by 1024QAM PDSCH PRBs. + +#### 4.9.2.2.7 FR1 test model 3.2 (NR-FR1-TM3.2) + +This model shall be used for tests on: + +- Transmitted signal quality + - Frequency error + - EVM for 16QAM modulation + +Common physical channel parameters are defined in clause 4.9.2.2. Specific physical channel parameters for NR-FR1-TM3.2 are defined in table 4.9.2.2.7-1. + +**Table 4.9.2.2.7-1: Specific physical channel parameters of NR-FR1-TM3.2** + +| Parameter | Value | +|--------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------| +| Target percent of 16QAM PDSCH PRBs deboosted | $x = 60\%$ | +| # of 16QAM PDSCH RBGs within a slot for which EVM is measured | , where P is determined from table 5.1.2.2.1-1 from TS 38.214 [18], configuration 1 column using as the size of the bandwidth part and | +| Locations of 16QAM RBGs which are deboosted | and if , 1, 3, ..., | +| Level of deboosting (dB) | -3 | +| # of QPSK PDSCH PRBs within a slot for which EVM is not measured (used for power balancing only) | | +| Locations of PDSCH RBGs which are boosted | Starting at RB#3 and excluding PRBs of RBGs which are deboosted | +| Level of boosting (dB) | | +| Modulation of PDSCH PRBs with for which EVM is not measured | QPSK | + +#### 4.9.2.2.8 FR1 test model 3.3 (NR-FR1-TM3.3) + +This model shall be used for tests on: + +- Transmitted signal quality + - Frequency error + - EVM for QPSK modulation + +Common physical channel parameters are defined in clause 4.9.2.2. Specific physical channel parameters for NR-FR1-TM3.3 are defined in table 4.9.2.2.8-1. + +**Table 4.9.2.2.8-1: Specific physical channel parameters of NR-FR1-TM3.3** + +| Parameter | Value | +|--------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------| +| Target percent of QPSK PDSCH PRBs deboosted | $x = 50 \%$ | +| # of QPSK PDSCH RBGs within a slot for which EVM is measured | , where P is determined from table 5.1.2.2.1-1 from TS 38.214 [18], configuration 1 column using as the size of the bandwidth part and | +| Level of deboosting (dB) | -6 | +| Locations of QPSK RBGs which are deboosted | and if , 1, 3, ..., | +| Level of deboosting (dB) | -6 | +| # of QPSK PDSCH PRBs within a slot for which EVM is not measured (used for power balancing only) | | +| Locations of QPSK RBGs for power balancing | Starting at RB#3 and excluding PRBs of RBGs which are deboosted | +| Level of boosting (dB) | | +| Modulation of PDSCH PRBs with for which EVM is not measured | QPSK | + +#### 4.9.2.2.9 NB-IoT operation in NR in-band test model (NR-N-TM) + +The NB-IoT operation in NR in-band test shall be performed by puncturing one NR RB at the eligible (according to clause 5.7.3 of TS 36.104 [22] and the definition in clause 3.1) in-band position closest to NR minimum guard band. + +The set-up of physical channels for transmitter tests shall be according to the FR1 test model 1.1 (NR-FR1-TM1.1) on all NR carriers and the NB-IoT Test Model (N-TM) defined in TS 36.141 [24] on all NB-IoT carriers. + +The power for NR RE and NB-IoT RE is set by following procedures: + +- The average power per RE over all RBs (both NR and NB-IoT) is calculated according to manufacturer's declared rated carrier output power ( $P_{\text{rated,c,AC}}$ , D.21); +- The power of boosted NB-IoT RE ( $P_{\text{NB-IoT}}$ ) is calculated according to manufacturer's declared rated NB-IoT maximum power dynamic range ( $X \text{ dB} \geq 6 \text{ dB}$ or $3 \text{ dB}$ ), with the power boosting only applies on the $N_{\text{NB-IoT}}$ REs containing NB-IoT signal. +- The remaining power is allocated to $N_{\text{NR}}$ NR REs. + +#### 4.9.2.3 Data content of Physical channels and Signals for NR-FR1-TM + +Randomisation of the data content is obtained by utilizing a PN sequence generator and the length-31 Gold sequence scrambling of TS 38.211 [17], clause 5.2.1 which is invoked by all physical channels prior to modulation and mapping to the RE grid. + +Initialization of the scrambler and RE-mappers as defined in TS 38.211 [17] use the following additional parameters: + +- for the lowest configured carrier, for the 2nd lowest configured carrier, ..., for the $n^{\text{th}}$ configured carrier +- Antenna ports starting with 2000 for PDCCH +- $q = 0$ (single code word) + +For NR-FR1-TM1.1 when used for TAE requirement of two layers MIMO transmission + +- Rank 2, two layers, no precoding +- Antenna ports starting with 1000 and 1001 for PDSCH + +Otherwise + +- Rank 1, single layer +- Antenna port starting with 1000 for PDSCH +- Rank 1, single layer (except for TAE requirement of 2 layer MIMO transmission) + +#### 4.9.2.3.1 PDCCH + +- +- PDCCH modulation to be QPSK as described in TS 38.211 [17], clause 5.1.3 + +- For each slot the required amount of bits for all PDCCHs is as follows: $1(\# \text{ of PDCCH}) * 1(\# \text{ of CCE per PDCCH}) * 6(\text{REG per CCE}) * 9(\text{data RE per REG}) * 2(\text{bits per RE})$ with these parameters according to the NR-FR1-TM definitions in clause 4.9.2.2 +- Generate this amount of bits from the output of the PN23 sequence generator [23]. The PN sequence generator is initialized with a starting seed of "all ones" in the first allocated slot of each frame. The PN sequence is continuous over the slot boundaries. +- 1 CCE shall be according to TS 38.211 [17], clause 7.3.2 using non-interleaved CCE-to-REG mapping. PDCCH occupies the first 2 symbols for 6 resource-element groups, where a resource element group equals one resource block during one OFDM symbol. +- Perform PDCCH scrambling according to TS 38.211 [17], clause 7.3.2.3 +- in DM-RS sequence generation in TS 38.211 [17], clause 7.4.1.3 +- in scrambling sequence generation in TS 38.211 [17], clause 7.3.2.3 +- Perform mapping to REs according to TS 38.211 [17], clause 7.3.2.5. + +#### 4.9.2.3.2 PDSCH + +- Generate the required amount of bits from the output of the PN23 sequence generator [23]. The PN sequence generator is initialized with a starting seed of "all ones" in the first allocated slot of each frame. The PN sequence is continuous over the slot boundaries. For TDD TMs, the PN sequence can be generated for all symbols (in the DL, UL or special slots) or only DL symbols (in the DL or special slots). For TMs with multi-users, the PN sequence can be generated per user ( $n_{\text{RNTI}}$ ). +- NR-FR1-TMs utilize 1, 2 or 3 user PDSCH transmissions distinguished by . For each NR-FR1-TM, PRBs are mapped to user () as follows: + +**Table 4.9.2.3.2-1: Mapping of PRBs to $n_{\text{RNTI}}$ for NR-FR1-TM** + +| Test model | $n_{\text{RNTI}}$ | Number of users | +|---------------|-----------------------------------------------------------------------------------------------------------------------------|-----------------| +| NR-FR1-TM1.1 | 2 for PRBs located in PRB#0-2
0 for remaining PRBs | 2 | +| NR-FR1-TM1.2 | 0 for boosted PRBs
1 for de-boosted PRBs
2 for PRBs located in PRB#0-2 | 3 | +| NR-FR1-TM2 | 2 for all PRBs | 1 | +| NR-FR1-TM2a | 2 for all PRBs | 1 | +| NR-FR1-TM2b | 2 for all PRBs | 1 | +| NR-FR1-TM3.1 | 2 for PRBs located in PRB#0-2
0 for remaining PRBs | 2 | +| NR-FR1-TM3.1a | 2 for PRBs located in PRB#0-2
0 for remaining PRBs | 2 | +| NR-FR1-TM3.1b | 2 for PRBs located in PRB#0-2
0 for remaining PRBs | 2 | +| NR-FR1-TM3.2 | 0 for QPSK PRBs
1 for 16QAM PRBs
2 for PRBs located in PRB#0-2 | 3 | +| NR-FR1-TM3.3 | 0 for QPSK PRBs for which EVM is not measured
1 for QPSK PRBs for which EVM is measured
2 for PRBs located in PRB#0-2 | 3 | + +- Perform user specific scrambling according to TS 38.211 [17], clause 7.3.1.1. + +- Perform modulation of the scrambled bits with the modulation scheme defined for each user according to TS 38.211 [17], clause 7.3.1.1 +- +- Perform mapping of the complex-valued symbols to layer according to TS 38.211 [17], clause 7.3.1.3. Complex-valued modulation symbols for codeword $c$ shall be mapped onto the layers $l$ , where $l$ is equal to number of layers. +- Perform PDSCH mapping according to TS 38.211 [17] using parameters listed in table 4.9.2.2-3. +- PDSCH resource allocation according to TS 38.214 [18] as following; + - NR-FR1-TM1.1, NR-FR1-TM3.1, NR-FR1-TM3.1a, NR-FR1-TM3.1b: type 1 for PDSCH with $n_{\text{RNTI}} = 0$ and $n_{\text{RNTI}} = 2$ , + - NR-FR1-TM1.2, NR-FR1-TM3.2, NR-FR1-TM3.3: type 0 for PDSCH with $n_{\text{RNTI}} = 0$ and $n_{\text{RNTI}} = 1$ , type 1 for PDSCH with $n_{\text{RNTI}} = 2$ , + - NR-FR1-TM2, NR-FR1-TM2a, NR-FR1-TM2b: type 1 for PDSCH with $n_{\text{RNTI}} = 2$ . +- DM-RS sequence generation according to TS 38.211 [17], clause 7.4.1.1.1 where $l$ is the OFDM symbol number within the slot with the symbols indicated by table 4.9.2.2-3. +- +- +- DM-RS mapping according to TS 38.211 [17], clause 7.4.1.1.2 using parameters listed in table 4.9.2.2-3. + +#### 4.9.2.4 Data content of Physical channels and Signals for NR-N-TM + +Detailed configuration for the transmitter characteristic tests are defined in TS 36.141 [24], + +### 4.9.3 NB-IoT testing + +Unless otherwise stated, the NB-IoT operation in NR in-band test shall be performed by puncturing one NR RB at the eligible (according to clause 5.7.3 of TS 36.104 [22] and the definition in clause 3.1) in-band position closest to NR minimum guard band; those are denoted $L_{\text{NB-IoT}}$ (Left) and $R_{\text{NB-IoT}}$ (Right). + +Unless otherwise stated, the NB-IoT operation in NR in-band receiver tests shall be performed by using the tone located on the NB-IoT RB's edge, which is closest to NR minimum guard band; those are denoted $B_{\text{NB-IoT}}$ for $L_{\text{NB-IoT}}$ and $T_{\text{NB-IoT}}$ for $R_{\text{NB-IoT}}$ . + +Unless otherwise stated, a BS declared to be capable of NB-IoT operation in NR in-band is only required to pass the transmitter tests for NR with NB-IoT operation in NR in-band; it is not required to perform the transmitter tests again for NR only. + +Unless otherwise stated, a BS declared to be capable of NB-IoT operation in NR in-band is only required to pass the receiver tests for NR with NB-IoT operation in NR in-band; it is not required to perform the receiver tests again for NR only. + +NOTE: The BS should be configured (RRC signalling) for the NB-IoT E-UTRA *guardband* mode during the tests. + +## 4.10 Requirements for contiguous and non-contiguous spectrum + +A spectrum allocation where a 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 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.11 Requirements for BS capable of multi-band operation + +For *multi-band connector* the conducted test requirements in clause 6 and 7 apply separately to each supported *operating band* unless otherwise stated. For some conducted test requirements, it is explicitly stated that specific additions or exclusions to the requirement apply at *multi-band connector(s)* as detailed in the requirement clause. 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 connectors* for BS *type 1-C* or *TAB connectors* for BS *type 1-H* in different ways are possible. For *multi-band connector(s)* the exclusions or provisions for multi-band apply. For *single-band connector(s)*, the following applies: + +- Single-band transmitter spurious emissions, *operating band* unwanted emissions, ACLR, transmitter intermodulation and receiver spurious emissions requirements apply to this connector that is mapped to single-band. +- If the BS is configured for single-band operation, *single-band requirements* shall apply to this 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 connector configured for single-band operation, with all other connectors terminated. + +A BS *type 1-H* 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 connectors*. + - Different sets of *single-band connectors* support different *operating bands*, but each *TAB connector* supports only operation in one single *operating band*. + - Sets of *single-band connectors* support operation in multiple *operating bands* with some *single-band connectors* supporting more than one *operating band*. +- All *TAB connectors* are *multi-band connectors*. +- A combination of single-band sets and multi-band sets of *TAB connectors* provides support of the type BS *type 1-H* capability of operation in multiple *operating bands*. + +Unless otherwise stated all conducted test requirements specified for an *operating band* apply only to the set of *TAB connectors* supporting that *operating band*. + +In the case of an *operating band* being supported only by *single-band 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*. + +In the case of an *operating band* being supported only by *multi-band 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*. + +For *multi-band connectors* supporting the bands for TDD, the RF requirements in the present specification assume no simultaneous uplink and downlink occur between the bands. + +NOTE 1: The case of an *operating band* being supported by both *multi-band connectors* and *single-band 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. + +NOTE 2: The case of an *operating band* being supported by *multi-band 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. + +NOTE 3: The conducted test requirements for *multi-band connectors* supporting bands for both FDD and TDD are not covered by the present release of this specification. + +## 4.12 Format and interpretation of tests + +Each test 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 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. + +###### **X.4.2y.2 Procedure** + +This clause describes the steps necessary to perform the test and provides further details of the test definition like 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. + +--- + +## 5 Operating bands and channel arrangement + +For the NR and NB-IoT operation in NR in-band operating bands specification, their channel bandwidth configurations, channel spacing and raster, as well as synchronization raster specification, refer to TS 38.104 [2], clause 5 and its relevant clauses. + +For the conducted testing purposes in this specification, only FR1 operating bands are considered. + +## 6 Conducted transmitter characteristics + +### 6.1 General + +#### 6.1.1 BS type 1-C + +General test conditions for conducted 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.5. + +If a number of *single-band connectors*, or *multi-band connectors* have been declared equivalent (D.32), only a representative one is necessary to be tested to demonstrate conformance. + +#### 6.1.2 BS type 1-H + +General test conditions for conducted 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.5. + +If a number of *single-band connectors*, or *multi-band connectors* have been declared equivalent (D.32), only a representative one is necessary to be tested to demonstrate conformance. + +In clause 6.6.3.5.4, 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}}$ , D.24) relates to the 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* (D.34). 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 *BS type 1-H* is calculated as follows: + +$$N_{\text{TXU, counted}} = \min(N_{\text{TXU, active}}, 8 \cdot N_{\text{cells}})$$ + +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}}$ . + +For *BS type 1-H* there is no requirement specified for band n46, n100, n101 and n102. + +### 6.2 Base station output power + +#### 6.2.1 Definition and applicability + +The conducted BS output power requirements are specified at *single-band connector*, or at *multi-band connector*. + +The *rated carrier output power* of the *BS type 1-C* shall be as specified in table 6.2.1-1. + +**Table 6.2.1-1: Rated carrier output power limits for BS type 1-C** + +| BS class | $P_{\text{rated,c,AC}}$ | +|-----------------------------------------------------------------------------------------------------------------|-------------------------| +| Wide Area BS | (Note) | +| Medium Range BS | $\leq 38$ dBm | +| Local Area BS | $\leq 24$ dBm | +| NOTE: There is no upper limit for the $P_{\text{rated,c,AC}}$ rated output power of the Wide Area Base Station. | | + +The rated carrier output power of the BS type 1-H shall be as specified in table 6.2.1-2. + +**Table 6.2.1-2: Rated carrier output power limits for BS type 1-H** + +| BS class | $P_{\text{rated,c,sys}}$ | $P_{\text{rated,c,TABC}}$ | +|----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|---------------------------| +| Wide Area BS | (Note) | (Note) | +| Medium Range BS | $\leq 38$ dBm + $10\log(N_{\text{TXU,counted}})$ | $\leq 38$ dBm | +| Local Area BS | $\leq 24$ dBm + $10\log(N_{\text{TXU,counted}})$ | $\leq 24$ dBm | +| NOTE: There is no upper limit for the $P_{\text{rated,c,sys}}$ or $P_{\text{rated,c,TABC}}$ of the Wide Area Base Station. | | | + +In addition, for operation with shared spectrum channel access operation, the BS may have to comply with the applicable BS power limits established regionally, when deployed in regions where those limits apply and under the conditions declared by the manufacturer. + +For Band n41 and n90 operation in Japan, the rated output power, $P_{\text{rated,c,sys}}$ for BS type 1-H or the sum of $P_{\text{rated,c,AC}}$ over all antenna connectors for BS type 1-C declared by the manufacturer shall be equal to or less than 20 W per 10 MHz bandwidth. + +For band n100 in CEPT countries, $P_{\text{rated,c,AC}}$ shall not exceed $51.5$ dBm/5MHz + $(f_{\text{DL}} - 922.1) \times 40/3$ dB, with $f_{\text{DL}}$ being the centre frequency in MHz. This limit is derived from ECC Decision (20)02 [25] assuming a 17 dBi maximum antenna gain and 4dB losses, and assuming one antenna connector. The above rated output power limit for band n100 applies to uncoordinated deployments and in case of coordinated deployments, higher output power values may be allowed. + +For band n101 in CEPT countries, $P_{\text{rated,c,AC}}$ shall not exceed 51 dBm/10MHz or 48 dBm/5MHz. This limit is derived from ECC Decision (20)02 [25] assuming a 18 dBi maximum antenna gain and 4dB losses, and assuming one antenna connector. The above rated output power limit for band n101 applies to uncoordinated deployments and in case of coordinated deployments, higher output power values may be allowed. + +The output power limit for the respective BS classes in tables 6.2.1-1 and 6.2.1-2 shall be compared to the rated output power and the declared BS class. It is not subject to testing. + +## 6.2.2 Minimum requirement + +The minimum requirement applies per *single-band connector*, or per *multi-band connector* supporting transmission in the *operating band*. + +The minimum requirement for BS type 1-C is defined in TS 38.104 [2], clause 6.2.2. + +The minimum requirement for BS type 1-H is defined in TS 38.104 [2], clause 6.2.3. + +## 6.2.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. + +## 6.2.4 Method of test + +### 6.2.4.1 Initial conditions + +Test environment: + +- Normal, see annex B.2, +- Extreme, see annexes B.3 and B.5. + +RF channels to be tested for single carrier: B, M and T; see clause 4.9.1 + +*Base Station RF Bandwidth* positions to be tested for multi-carrier and/or CA: + +- $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ for *single-band connector(s)*, see clause 4.9.1. +- $B_{\text{RFBW\_T}}$ and $B'_{\text{RFBW\_T}}$ for *multi-band connector(s)*, see clause 4.9.1. + +Under extreme test environment, it is sufficient to test on one NR-ARFCN or one RF bandwidth position, and with one applicable test configuration defined in clauses 4.7 and 4.8. 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.4.2 Procedure + +For *BS type I-H* where there may be multiple *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex D.3.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 *single-band connector(s)* or to *multi-band connector(s)* under test as shown in annex D.1.1 for *BS type I-C* or in annex D.3.1 for *BS type I-H*. All connectors not under test shall be terminated. +- 2) For single carrier set the connector under test to transmit according to the applicable test configuration in clause 4.8 using the corresponding test models or set of physical channels in clause 4.9.2 at *rated carrier output power* $P_{\text{rated,c,AC}}$ for *BS type I-C* and $P_{\text{rated,c,TABC}}$ for *BS type I-H* (D.21). + +For a connector under test declared to be capable of multi-carrier and/or CA operation (D.15-D.16) set the connector under test to transmit on all carriers configured using the applicable test configuration and corresponding power setting specified in clauses 4.7 and 4.8 using the corresponding test models or set of physical channels in clause 4.9.2. + +- 3) Measure the *maximum carrier output power* ( $P_{\text{max,c,AC}}$ for *BS type I-C* and $P_{\text{max,c,TABC}}$ for *BS type I-H*) for each carrier at each connector under test. + +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.2.5 Test requirement + +For each *single-band connector* or *multi-band connector* under test, the power measured in clause 6.2.4.2 in step 3 shall remain within the values provided in table 6.2.5-1 for normal and extreme test environments, relative to the manufacturer's declared $P_{\text{rated,c,AC}}$ for *BS type I-C*, or relative to the manufacturer's declared $P_{\text{rated,c,TABC}}$ for *BS type I-H* (D.21): + +**Table 6.2.5-1: Test requirement for conducted BS output power** + +| | Normal test environment | Extreme test environment | +|--------------------|------------------------------------------------------------------|------------------------------------------------------------------| +| BS type 1-C | $f \leq 3.0 \text{ GHz}: \pm 2.7 \text{ dB}$ | $f \leq 3.0 \text{ GHz}: \pm 3.2 \text{ dB}$ | +| BS type 1-H | $3.0 \text{ GHz} < f \leq 7.125 \text{ GHz}: \pm 3.0 \text{ dB}$ | $3.0 \text{ GHz} < f \leq 7.125 \text{ GHz}: \pm 3.5 \text{ dB}$ | + +NOTE: 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 shall apply for $P_{\max,c,AC}$ and $P_{\text{rated,c,AC}}$ . + +## 6.3 Output power dynamics + +### 6.3.1 General + +The requirements in clause 6.3 apply during the *transmitter ON period*. Transmit signal quality requirements (as specified in clause 6.5) shall be maintained for the output power dynamics requirements of this clause. + +### 6.3.2 RE power control dynamic range + +#### 6.3.2.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 BS at *maximum carrier output power* ( $P_{\max,c,TABC}$ or $P_{\max,c,AC}$ ) for a specified reference condition. + +#### 6.3.2.2 Minimum requirement + +The minimum requirement applies per *single-band connector*, or per *multi-band connector* supporting transmission in the *operating band*. + +The minimum requirement for *BS type 1-C* and for *BS type 1-H* is defined in TS 38.104 [2], clause 6.3.2.2. + +#### 6.3.2.3 Test purpose + +No specific test or test requirements are defined for conducted RE power control dynamic range. The Error Vector Magnitude (EVM) test, as described in clause 6.5.4 provides sufficient test coverage for this requirement. + +### 6.3.3 Total power dynamic range + +#### 6.3.3.1 Definition and applicability + +The BS 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 1: The upper limit of the total power dynamic range is the OFDM symbol TX power (OSTP) for a BS at maximum output power when transmitting on all RBs. The lower limit of the total power dynamic range is the average power for single RB transmission. The OFDM symbols shall carry PDSCH and not contain PDCCH, RS, or SSB. + +NOTE 2: The requirement does not apply to operation with shared spectrum channel access. + +### 6.3.3.2 Minimum requirement + +The minimum requirement applies per *single-band connector*, or per *multi-band connector*. + +The minimum requirement for *BS type 1-C* and for *BS type 1-H* is in TS 38.104 [2], clause 6.3.3.2. + +### 6.3.3.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.3.4 Method of test + +#### 6.3.3.4.1 Initial conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested: M; see clause 4.9.1. + +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. + +#### 6.3.3.4.2 Procedure + +For *BS type 1-H* where there may be multiple *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex D.3.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect the *single-band connector(s)* under test as shown in annex D.1.1 for *BS type 1-C* and in annex D.3.1 for *BS type 1-H*. All connectors not under test shall be terminated. + - 2) Set each connector under test to transmit according to the applicable test configuration in clause 4.8 using the corresponding test models in clause 4.9.2 at *rated carrier output power* $P_{\text{rated,c,AC}}$ for *BS type 1-C* and $P_{\text{rated,c,TABC}}$ for *BS type 1-H* (D.21). + - 3) For *BS type 1-C* and *BS type 1-H*, 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-TM3.1a if 1024QAM is not supported by BS without power back off but 256QAM is supported by BS without power back off, or + - NR-FR1-TM3.1 if 1024QAM and 256QAM are both not supported by BS without power back off. + - 4) Measure the OFDM symbol TX power (OSTP) as defined in the annex H. + - 5) For *BS type 1-C* and *BS type 1-H*, set the BS to transmit a signal according to: + - NR-FR1-TM2b if 1024QAM is supported by BS, or + - NR-FR1-TM2a if 1024QAM is not supported by BS and 256QAM is supported; + - NR-FR1-TM2 if 1024QAM and 256QAM are both not supported; + - 6) Measure the OFDM symbol TX power (OSTP) as defined in the annex H. +- In addition, for *multi-band connectors*, the following steps shall apply: +- 7) 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.3.5 Test requirements + +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-1. + +**Table 6.3.3.5-1: BS 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: Additional test requirements for the EVM at the lower limit of the dynamic range are defined in clause 6.5.4. + +## 6.3.4 NB-IoT RB power dynamic range + +### 6.3.4.1 Definition and applicability + +The NB-IoT RB power dynamic range (or NB-IoT power boosting) is the difference between the average power of NB-IoT REs (which occupy certain REs within a NR transmission bandwidth configuration plus 15 kHz at each edge but not within the NR minimum guard band $GB_{\text{channel}}$ ) and the average power over all REs (from both NB-IoT and the NR carrier containing the NB-IoT REs). + +### 6.3.4.2 Minimum requirement + +The minimum requirement applies per *single-band connector*, or per *multi-band connector*. + +The minimum requirement for *BS type 1-C* is in TS 38.104 [2], clause 6.3.4.2. + +### 6.3.4.3 Test purpose + +The test purpose is to verify that the NB-IoT RB power dynamic range for NB-IoT operation in NR in-band is met as specified by the minimum requirement. + +### 6.3.4.4 Method of test + +Requirement is tested together with operating band unwanted emissions test, as described in clause 6.6.4. + +### 6.3.4.5 Test requirements + +NB-IoT RB power dynamic range for NB-IoT operation in NR in-band shall be larger than or equal to the level specified in Table 6.3.4.5-1 or the NB-IoT power dynamic range declared by the BS manufacturer (D.43). This power dynamic range level is only required for one NB-IoT RB. + +**Table 6.3.4.5-1: NB-IoT RB power dynamic range for NB-IoT operation in NR in-band** + +| BS channel bandwidth (MHz) | NB-IoT RB frequency position | NB-IoT RB power dynamic range (dB) | +|---------------------------------------------|---------------------------------------------------------------------|------------------------------------| +| 5, 10 | Any | +5.6 | +| 15 | Within center $77 \cdot 180\text{kHz} + 15\text{kHz}$ at each edge | +5.6 | +| | Other | +2.6 | +| 20 | Within center $102 \cdot 180\text{kHz} + 15\text{kHz}$ at each edge | +5.6 | +| | Other | +2.6 | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | Within center 90% of BS channel bandwidth | +5.6 | +| | Other | +2.6 | + +## 6.4 Transmit ON/OFF power + +### 6.4.1 Transmitter OFF power + +#### 6.4.1.1 Definition and applicability + +Transmit OFF power requirements apply only to TDD operation of the BS. + +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_{\text{Config}}$ ) centred on the assigned channel frequency during the *transmitter OFF period*. $N = \text{SCS}/15$ , where SCS is Sub Carrier Spacing in kHz. + +For *multi-band connectors* and for *single band connectors* supporting transmission in multiple operating bands, the requirement is only applicable during the *transmitter OFF period* in all supported operating bands. + +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_{\text{Channel\_CA}}$ centred on $(F_{\text{edge\_high}} + F_{\text{edge\_low}})/2$ during the *transmitter OFF period*. $N = \text{SCS}/15$ , where SCS is the smallest supported Sub Carrier Spacing in kHz in the *aggregated BS channel bandwidth*. + +#### 6.4.1.2 Minimum requirement + +The minimum requirement for *BS type I-C* is in TS 38.104 [2], clause 6.4.1.2. + +The minimum requirement for *BS type I-H* is in TS 38.104 [2], clause 6.4.1.3. + +#### 6.4.1.3 Test purpose + +The purpose of this test is to verify the transmitter OFF power is within the limits of the minimum requirements. + +#### 6.4.1.4 Method of test + +Requirement is tested together with transmitter transient period, as described in clause 6.4.2.4. + +### 6.4.1.5 Test requirements + +The conformance testing of transmit OFF power is included in the conformance testing of transmitter transient period; therefore, see clause 6.4.2.5 for test requirements. + +## 6.4.2 Transmitter transient period + +### 6.4.2.1 Definition and applicability + +*Transmitter transient period* requirements apply only to TDD operation of the BS. + +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.2.1-1. + +![Figure 6.4.2.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 horizontal dashed lines representing the ON power level and OFF power level. The x-axis is divided into three main segments: 'UL transmission' on the left, 'Transmitter ON period (DL transmission)' in the center, and 'GP or UL transmission' on the right. The 'Transmitter transient period' is indicated by two double-headed arrows: one at the start of the ON period and one at the end. The 'Transmitter OFF period' is indicated by two double-headed arrows: one before the start of the ON period and one after the end of the ON period.](43cd26e92a1c09efb81d26db4787dcb6_img.jpg) + +Figure 6.4.2.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 horizontal dashed lines representing the ON power level and OFF power level. The x-axis is divided into three main segments: 'UL transmission' on the left, 'Transmitter ON period (DL transmission)' in the center, and 'GP or UL transmission' on the right. The 'Transmitter transient period' is indicated by two double-headed arrows: one at the start of the ON period and one at the end. The 'Transmitter OFF period' is indicated by two double-headed arrows: one before the start of the ON period and one after the end of the ON period. + +**Figure 6.4.2.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period** + +This requirement applies at each *antenna connector* or *TAB connector* supporting transmission in the operating band. + +### 6.4.2.2 Minimum requirement + +The minimum requirement for *BS type 1-C* and *BS type 1-H* is in TS 38.104 [2], clause 6.4.2.2. + +### 6.4.2.3 Test purpose + +The purpose of this test is to verify the transmitter transient periods are 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.2. + +RF channels to be tested for single carrier: + +- M; see clause 4.9.1. + +RF bandwidth positions to be tested for multi-carrier and/or CA: + +- $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. + +#### 6.4.2.4.2 Procedure + +The minimum requirement is applied to all *antenna connectors* or *TAB connectors*, they may be tested one at a time or multiple *antenna connectors* or *TAB connectors* may be tested in parallel as shown in annex D.1.1 for *BS type 1-C* or in annex D.3.1 for *BS type 1-H*. Whichever method is used the procedure is repeated until all *antenna connectors* or *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect *antenna connector* or *TAB connector* to measurement equipment as shown in annex D.1.1 for *BS type 1-C* or in annex D.3.1 for *BS type 1-H*. All *antenna connectors* or *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 single carrier set the *antenna connector* or *TAB connector* under test to transmit according to the applicable test configuration in clause 4.8 using the corresponding test models or set of physical channels in clause 4.9.2 at manufacturers declared *rated carrier output power* per *antenna connector* or *TAB connector* ( $P_{\text{rated,c,AC}}$ , or $P_{\text{rated,c,TABC}}$ , D.21). + +For a connector under test declared to be capable of multi-carrier and/or CA operation (D.15-D.16) set the connector under test to transmit on all carriers configured using the applicable test configuration and corresponding power setting specified in clauses 4.7 and 4.8 using the corresponding test models or set of physical channels in clause 4.9.2. + +- 3) 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* or *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 = \text{SCS}/15$ , where SCS is Sub Carrier Spacing in kHz. + +- 4) For an *antenna connector* or *TAB connector* supporting contiguous CA, measure the mean power spectral density 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$ . $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 = \text{SCS}/15$ , where SCS is the smallest supported Sub Carrier Spacing in kHz in the *aggregated BS channel bandwidth*. + +In addition, for *multi-band connector(s)*, the following steps shall apply: + +- 5) For *multi-band 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 \text{ 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 \text{ GHz} < f \leq 7.125 \text{ GHz}$ . + +For *multi-band connector*, the requirement is only applicable during the transmitter OFF period in all supported operating bands. + +## 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 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. + +For *BS type 1-C* this requirement shall be applied at the *antenna connector* supporting transmission in the *operating band*. + +For *BS type 1-H* this requirement shall be applied at each *TAB connector* supporting transmission in the *operating band*. + +#### 6.5.2.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2], clause 6.5.1.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 modulation quality test, as described in clause 6.5.3. + +#### 6.5.2.5 Test Requirements + +The modulated carrier frequency of each NR carrier configured by the BS shall be accurate to within the accuracy range given in table 6.5.2.5-1 observed over 1 ms. + +**Table 6.5.2.5-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})$ | + +The frequency error requirement for NB-IoT is specified in TS 36.141 [24] clause 6.5.1.5. + +## 6.5.3 Modulation quality + +### 6.5.3.1 Definition and applicability + +Modulation quality is defined by the difference between the measured carrier signal and an ideal signal. Modulation quality can e.g. be expressed as Error Vector Magnitude (EVM). The Error Vector Magnitude is a measure of the difference between the ideal symbols and the measured symbols after the equalization. This difference is called the error vector. + +For *BS type 1-C* this requirement shall be applied at the *antenna connector* supporting transmission in the *operating band*. + +For *BS type 1-H* this requirement shall be applied at each *TAB connector* supporting transmission in the *operating band*. + +### 6.5.3.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2], clause 6.5.2.2. + +### 6.5.3.3 Test purpose + +The test purpose is to verify that modulation quality is within the limit specified by the minimum requirement. + +### 6.5.3.4 Method of test + +#### 6.5.3.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.9.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.9.1; +- $B_{\text{RFBW\_T\_RFBW}}$ and $B'_{\text{RFBW\_T\_RFBW}}$ in multi-band operation, see clause 4.9.1. + +#### 6.5.3.4.2 Procedure + +The minimum requirement is applied to all *antenna connectors* or *TAB connectors*, they may be tested one at a time or multiple *antenna connectors* or *TAB connectors* may be tested in parallel as shown in annex D.1.1 for *BS type 1-C* or in annex D.3.1 for *BS type 1-H*. Whichever method is used the procedure is repeated until all *antenna connectors* or *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) For an *antenna connector* or *TAB connector* declared to be capable of single carrier operation only (D.16), set the *antenna connector* or the *TAB connector* under test to transmit a signal according to the applicable test configuration in clause 4.8 using the corresponding test models: + - NR-FR1-TM 3.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-TM 3.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. + +For an *antenna connector* or *TAB connector* declared to be capable of multi-carrier and/or CA operation (D.15-D.16), set the *antenna connector* or the *TAB connector* under test to transmit according to the applicable test configuration and corresponding power setting specified in clauses 4.7 and 4.8 using the corresponding test models on all carriers configured: + +- NR-FR1-TM 3.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. + +For NR-FR1-TM3.1a and NR-FR1-TM3.1b, power back-off shall be applied if it is declared. + +- 2) Measure the EVM and frequency error as defined in annex H. +- 3) Repeat steps 1 and 2 for NR-FR1-TM2 if 256QAM and 1024QAM is not supported by BS or for NR-FR1-TM2a if 256QAM is supported by BS and 1024QAM is not supported by BS or for NR-FR1-TM2b if 1024QAM is supported. For NR-FR1-TM2, NR-FR1-TM2a and NR-FR1-TM2b, the OFDM symbol TX power (OSTP) shall be at the lower limit of the dynamic range according to the test procedure in clause 6.3.3.4 and test requirements in clause 6.3.3.5. + +In addition, for *multi-band connector(s)*, the following steps shall apply: + +- 4) For *multi-band 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 requirements + +The EVM of each NR carrier for different modulation schemes on PDSCH shall be less than the limits in table 6.5.3.5-1. + +**Table 6.5.3.5-1 EVM requirements for BS type 1-C and BS type 1-H** + +| 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. | | + +EVM shall be evaluated for each NR carrier over all allocated resource blocks and downlink slots. Different modulation schemes listed in table 6.5.3.5-1 shall be considered for rank 1. + +For all bandwidths, the EVM measurement shall be performed for each NR carrier over all allocated resource blocks and downlink slots within 10 ms measurement periods. The boundaries of the EVM measurement periods need not be aligned with radio frame boundaries. + +Table 6.5.3.5-2, 6.5.3.5-3, 6.5.3.5-4 below specify the EVM window length (*W*) for normal CP for BS type 1-C and BS type 1-H. + +**Table 6.5.3.5-2 EVM window length for normal CP for NR, FR1, 15 kHz SCS** + +| Channel bandwidth (MHz) | FFT size | Cyclic prefix length for symbols 1-6 and 8-13 in FFT samples | EVM window length W | Ratio of W to total CP length for symbols 1-6 and 8-13 (%) (Note) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|--------------------------------------------------------------|----------------------------|--------------------------------------------------------------------------| +| 5 | 512 | 36 | 14 | 40 | +| 10 | 1024 | 72 | 28 | 40 | +| 15 | 1536 | 108 | 44 | 40 | +| 20 | 2048 | 144 | 58 | 40 | +| 25 | 2048 | 144 | 72 | 50 | +| 30 | 3072 | 216 | 108 | 50 | +| 35 | 3072 | 216 | 108 | 50 | +| 40 | 4096 | 288 | 144 | 50 | +| 45 | 4096 | 288 | 144 | 50 | +| 50 | 4096 | 288 | 144 | 50 | +| Note: These percentages are informative and apply to a slot's symbols 1 to 6 and 8 to 13. Symbols 0 and 7 have a longer CP and therefore a lower percentage. | | | | | + +**Table 6.5.3.5-3 EVM window length for normal CP for NR, FR1, 30 kHz SCS** + +| Channel bandwidth (MHz) | FFT size | Cyclic prefix length for symbols 1-13 in FFT samples | EVM window length W | Ratio of W to total CP length for symbols 1-13 (%) (Note) | +|-------------------------|----------|------------------------------------------------------|----------------------------|------------------------------------------------------------------| +| 5 | 256 | 18 | 8 | 40 | +| 10 | 512 | 36 | 14 | 40 | +| 15 | 768 | 54 | 22 | 40 | +| 20 | 1024 | 72 | 28 | 40 | +| 25 | 1024 | 72 | 36 | 50 | +| 30 | 1536 | 108 | 54 | 50 | +| 35 | 1536 | 108 | 54 | 50 | +| 40 | 2048 | 144 | 72 | 50 | +| 45 | 2048 | 144 | 72 | 50 | +| 50 | 2048 | 144 | 72 | 50 | +| 60 | 3072 | 216 | 130 | 60 | +| 70 | 3072 | 216 | 130 | 60 | +| 80 | 4096 | 288 | 172 | 60 | +| 90 | 4096 | 288 | 172 | 60 | +| 100 | 4096 | 288 | 172 | 60 | + +Note: These percentages are informative and apply to a slot's symbols 1 through 13. Symbol 0 has a longer CP and therefore a lower percentage. + +**Table 6.5.3.5-4 EVM window length for normal CP for NR, FR1, 60 kHz SCS** + +| Channel bandwidth (MHz) | FFT size | Cyclic prefix length in FFT samples | EVM window length W | Ratio of W to total CP length (%) (Note) | +|-------------------------|----------|-------------------------------------|----------------------------|-------------------------------------------------| +| 10 | 256 | 18 | 8 | 40 | +| 15 | 384 | 27 | 11 | 40 | +| 20 | 512 | 36 | 14 | 40 | +| 25 | 512 | 36 | 18 | 50 | +| 30 | 768 | 54 | 26 | 50 | +| 35 | 768 | 54 | 26 | 50 | +| 40 | 1024 | 72 | 36 | 50 | +| 45 | 1024 | 72 | 36 | 50 | +| 50 | 1024 | 72 | 36 | 50 | +| 60 | 1536 | 108 | 64 | 60 | +| 70 | 1536 | 108 | 64 | 60 | +| 80 | 2048 | 144 | 86 | 60 | +| 90 | 2048 | 144 | 86 | 60 | +| 100 | 2048 | 144 | 86 | 60 | + +Note: These percentages are informative and apply to all OFDM symbols within subframe except for symbol 0 of slot 0 and slot 2. Symbol 0 of slot 0 and slot 2 has a longer CP and therefore a lower percentage. + +The modulation quality requirements for NB-IoT are specified in TS 36.141 [24] clause 6.5.2.5. + +## 6.5.4 Time alignment error + +### 6.5.4.1 Definition and applicability + +This requirement applies to frame timing in MIMO transmission, carrier aggregation and their combinations. + +Frames of the NR signals present at the BS transmitter *antenna connectors* or *TAB connectors* are not perfectly aligned in time and may experience certain timing differences in relation to each other. + +For *BS type 1-C*, the TAE is defined as the largest timing difference between any two signals belonging to different *antenna connectors* for a specific set of signals/transmitter configuration/transmission mode. + +For *BS type 1-H*, the TAE is defined as the largest timing difference between any two signals belonging to *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 MIMO transmission, *carrier aggregation* for a specific set of signals/transmitter configuration/transmission mode. + +#### 6.5.4.2 Minimum requirement + +The minimum requirements for *BS type 1-C* and *BS type 1-H* are in TS 38.104 [2], clause 6.5.3.2. + +#### 6.5.4.3 Test purpose + +To verify that the time alignment error is within the limit specified by the minimum requirement. + +#### 6.5.4.4 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: M; see clause 4.9.1. + +RF bandwidth positions to be tested for multi-carrier and/or CA: + +- $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. + +##### 6.5.4.4.2 Procedure + +For *BS type 1-C antenna connectors* to be tested are for a specific set of signals/transmitter configuration/transmission mode. + +For *BS type 1-H TAB connectors* to be tested are identified from the declared sets of *TAB connector beam forming groups* in the TAE groups declaration (D.31). + +Compliance is to be demonstrated between all pairs of *single-band connectors and/or multi-band connectors*, however it is not required to exhaustively measure TAE between every combination of pairs of representative connectors. Compliance can be demonstrated by comparison of a reduced set of representative measurement results. + +###### 1) Conducted measurement setup: + +- For *BS type 1-C*: Connect two *antenna connectors* to the measurement equipment according to annex D.1.3. Terminate any unused *antenna connector(s)*. +- For *BS type 1-H*: Connect two representative *TAB connectors* one from separate TAE group (D.31) to the measurement equipment according to annex D.3.4. Terminate any unused *TAB connector(s)*. + +###### 2) Set the connectors under test to transmit NR-FR1-TM 1.1 or any DL signal using MIMO transmission or carrier aggregation. + +NOTE: For MIMO transmission, different ports may be configured in NR-FR1-TM 1.1 (using *PDSCH DMRS ports 1000 and 1001*). + +3) For a connectors declared to be capable of single carrier operation only (D.16), set the representative connectors under test to transmit according to the applicable test configuration in clause 4.8 using the corresponding test models in clause 4.9.2 at *rated carrier output power* ( $P_{\text{rated,c,AC}}$ , or $P_{\text{rated,c,TABC}}$ , D.21). + +If the connector under test supports intra band contiguous CA, set the representative connectors to transmit using the applicable test configuration and corresponding power setting specified in clauses 4.7 and 4.8. + +If the BS supports inter band CA, set the representative 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.7 and 4.8. + +For a connector declared to be capable of multi-carrier operation (D.15), set the BS to transmit according to the applicable test signal configuration and corresponding power setting specified in clauses 4.7 and 4.8 using the corresponding test model in clause 4.9.2 on all carriers configured. + +4) Measure the time alignment error between the different PDSCH demodulation reference signals on different antenna ports belonging to different connectors on the carrier(s) from the representative connectors under test. + +5) Repeat step 1 - 4 for any other configuration of connectors, which could be required to demonstrate compliance. + +In addition, for *multi-band connectors*, the following steps shall apply: + +6) 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.5.4.5 Test requirement + +For MIMO transmission, 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. + +The time alignment error requirements for NB-IoT are specified in TS 36.141 [24] clause 6.5.3.5. + +## 6.6 Unwanted emissions + +### 6.6.1 General + +Unwanted emissions consist of out-of-band emissions and spurious emissions according to ITU definitions in recommendation ITU-R SM.329 [5]. 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. + +The out-of-band emissions requirement for the BS transmitter is specified both in terms of Adjacent Channel Leakage power Ratio (ACLR) and operating band unwanted emissions (OBUE). + +The maximum offset of the operating band unwanted emissions mask from the operating band edge is $\Delta f_{\text{OBUE}}$ . The operating band unwanted emissions define all unwanted emissions in each supported downlink *operating band* plus the frequency ranges $\Delta f_{\text{OBUE}}$ above and $\Delta f_{\text{OBUE}}$ below each band. Unwanted 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-1 for the NR *operating bands*. + +**Table 6.6.1-1: Maximum offset of OBUE outside the downlink *operating band*** + +| BS type | Operating band characteristics | $\Delta f_{\text{OBUE}}$ (MHz) | +|-------------|--------------------------------------------------------------------------------------|--------------------------------| +| BS type 1-C | $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 | +| BS type 1-H | $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 | + +For band n46, n96 and n102, the values of $\Delta f_{\text{OBUE}}$ are defined in table 6.6.1-1a. + +**Table 6.6.1-1a: Maximum offset of OBUE outside the downlink *operating band*** + +| Operating band | $\Delta f_{\text{OBUE}}$ (MHz) | +|----------------|--------------------------------| +| n46, n102 | 40 | +| n96 | 50 | + +For band n104, the values of $\Delta f_{\text{OBUE}}$ are defined in table 6.6.1-1b. + +**Table 6.6.1-1b: Maximum offset of OBUE outside the downlink *operating band* for band n104** + +| BS type | Operating band | $\Delta f_{\text{OBUE}}$ (MHz) | +|-------------|----------------|--------------------------------| +| BS type 1-H | n104 | 100 | +| BS type 1-C | n104 | 40 | + +For BS type 1-H the unwanted emission requirements are applied per the *TAB connector TX min cell groups* for all the configurations supported by the BS. The *basic limits* and corresponding emissions scaling are defined in each relevant clause. + +There is in addition a requirement for occupied bandwidth. + +## 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 [12]. + +The value of $\beta/2$ shall be taken as 0.5%. + +The occupied bandwidth requirement shall apply 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. + +For BS type 1-C this requirement shall be applied at the *antenna connector* supporting transmission in the *operating band*. + +For BS type 1-H this requirement shall be applied at each *TAB connector* supporting transmission in the *operating band*. + +### 6.6.2.2 Minimum Requirements + +The minimum requirement for BS type 1-C and BS type 1-H is in TS 38.104 [2] clause 6.6.2 + +### 6.6.2.3 Test purpose + +The test purpose is to verify that the emission at the *antenna connector* or *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 + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +*Aggregated BS channel bandwidth* positions to be tested for contiguous carrier aggregation: $M_{BW\ Channel\ CA}$ ; see clause 4.9.1. + +1) Connect the measurement device to the BS *antenna connector* or *TAB connector* as shown in annex D1.1 for BS type 1-C or D3.1 for BS type 1-H. + +2) For a BS declared to be capable of single carrier operation (D.16), start transmission according to the applicable test configuration in clause 4.8 using the corresponding test model NR-FR1-TM1.1 at manufacturer's declared rated output power ( $P_{rated,c,AC}$ , or $P_{rated,c,TABC}$ , D.21). + +For a BS declared to be capable of contiguous CA operation, set the BS to transmit according to NR-FR1-TM1.1 on all carriers configured using the applicable test configuration and corresponding power setting specified in clauses 4.7.4 and 4.8. + +For a BS declared to be capable of NB-IoT operation in NR in-band (D.41), test shall be performed using N-TM according to clause 4.9.2.2.9. + +#### 6.6.2.4.2 Procedure + +- 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-1. The selected resolution bandwidth (RBW) filter of the analyser shall be 30 kHz or less. + +**Table 6.6.2.4.2-1: Span and number of measurement points for OBW measurements** + +| 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\lceil \frac{2 \times BW_{Channel}}{100kHz} \right\rceil$ | $\left\lceil \frac{2 \times BW_{Channel\_CA}}{100kHz} \right\rceil$ | + +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 must be 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, f2, for which the sum of all power in the measurement cells from f2 to the end of the span exceeds P1. +- 5) Compute the occupied bandwidth as f2 - f1. + +In addition, for a multi-band capable BS, the following step shall apply: + +- 6) For multi-band capable BS and single band tests, repeat the steps above 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. + +### 6.6.2.5 Test requirements + +The occupied bandwidth for each carrier shall be less than the channel bandwidth as defined in TS 38.104 [2], table 5.3.5-1 for *BS type 1-C* and *BS type 1-H*. For contiguous CA, the occupied bandwidth shall be less than or equal to the *aggregated BS channel bandwidth* as defined in TS 38.104 [2], clause 5.3A. + +## 6.6.3 Adjacent Channel Leakage Power Ratio (ACLR) + +### 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. + +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. + +The requirements shall also apply if the BS supports NB-IoT operation in NR in-band. + +For a BS operating in non-contiguous spectrum, the ACLR requirement in clause 6.6.3.2 shall apply in *sub block gaps*, while the CACLR requirement in clause 6.6.3.2 shall apply in *sub block gaps*. + +For a *multi-band connector*, the ACLR requirement in clause 6.6.3.2 shall apply in *Inter RF Bandwidth gaps*, while the CACLR requirement in clause 6.6.3.2 shall apply in *Inter RF Bandwidth gaps*. + +The requirement applies during the *transmitter ON period*. + +### 6.6.3.2 Minimum requirement + +The minimum requirement applies per *single-band connector*, or per *multi-band connector* supporting transmission in the *operating band*. + +The minimum requirement for *BS type 1-C* is defined in TS 38.104 [2], clause 6.6.3.3. + +The minimum requirement for *BS type 1-H* is defined in TS 38.104 [2], clause 6.6.3.4. + +### 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 + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: B, M and T; see clause 4.9.1. + +*Base Station 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.9.1. +- $B_{\text{RFBW\_T}}$ and $B'_{\text{RFBW\_T}}$ in multi-band operation, see clause 4.9.1. + +#### 6.6.3.4.2 Procedure + +For *BS type 1-H* where there may be multiple *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 for *BS type 1-C* or in annex D.3.1 for *BS type 1-H*. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect the *single-band connector* or *multi-band connector* under test to measurement equipment as shown in annex D.1.1 for *BS type 1-C* and in annex D.3.1 for *BS type 1-H*. All 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 a connectors declared to be capable of single carrier operation only (D.16), set the representative connectors under test to transmit according to the applicable test configuration in clause 4.8 using the corresponding test models NR-FR1-TM 1.1 in clause 4.9.2 at *rated carrier output power* $P_{\text{rated,c,AC}}$ for *BS type 1-C* and $P_{\text{rated,c,TABC}}$ for *BS type 1-H* (D.21). + +For a connector under test declared to be capable of multi-carrier and/or CA operation (D.15-D.16) set the connector under test to transmit on all carriers configured using the applicable test configuration and corresponding power setting specified in clauses 4.7 and 4.8 using the corresponding test models or set of physical channels in clause 4.9.2. + +For a BS declared to be capable of NB-IoT operation in NR in-band (D.41), test shall be performed using N-TM according to clause 4.9.2.2.9. + +- 3) Measure ACLR for the frequency offsets both side of channel frequency as specified in table 6.6.3.5.2-1. In multiple carrier case only offset frequencies below the lowest and above the highest carrier frequency used shall be measured. +- 4) 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.2, if applicable. + - b) Measure CACLR inside sub-block gap or *Inter RF Bandwidth gap* as specified in clause 6.6.3.5.2, if applicable. +- 5) Repeat the test with the channel set-up according to NR-FR1-TM 1.2 in clause 4.9.2. + +In addition, for *multi-band connectors*, the following steps shall apply: + +- 6) 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.6.3.5 Test requirements + +### 6.6.3.5.1 General requirements + +The ACLR requirements in clause 6.6.3.5.2 shall apply as described in clauses 6.6.3.5.3 or 6.6.3.5.4. + +### 6.6.3.5.2 Limits and *basic limits* + +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 operation in paired and unpaired spectrum except for band n46, n96 and n102, the ACLR shall be higher than the value specified in table 6.6.3.5.2-1. + +**Table 6.6.3.5.2-1: Base station 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 | ACLR limit | +|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------|-----------------------------| +| 5, 10, 15, 20 | $BW_{\text{Channel}}$ | NR of same BW (Note 2) | Square ( $BW_{\text{Config}}$ ) | 44.2 dB
37.2 dB (NOTE 4) | +| | $2 \times BW_{\text{Channel}}$ | NR of same BW (Note 2) | Square ( $BW_{\text{Config}}$ ) | 44.2 dB
37.2 dB (NOTE 4) | +| | $BW_{\text{Channel}}/2 + 2.5 \text{ MHz}$ | 5 MHz E-UTRA | Square (4.5 MHz) | 44.2 dB (NOTE 3) | +| | $BW_{\text{Channel}}/2 + 7.5 \text{ 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_{\text{Channel}}$ | NR of same BW (Note 2) | Square ( $BW_{\text{Config}}$ ) | 43.8 dB
36.8 dB (NOTE 4) | +| | $2 \times BW_{\text{Channel}}$ | NR of same BW (Note 2) | Square ( $BW_{\text{Config}}$ ) | 43.8 dB
36.8 dB (NOTE 4) | +| | $BW_{\text{Channel}}/2 + 2.5 \text{ MHz}$ | 5 MHz E-UTRA | Square (4.5 MHz) | 43.8 dB (NOTE 3) | +| | $BW_{\text{Channel}}/2 + 7.5 \text{ MHz}$ | 5 MHz E-UTRA | Square (4.5 MHz) | 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. + +Note 4: For BS operating in band n104, ACLR requirement 37.2 or 36.8 dB applies. For BS operating in other bands, ACLR requirement 44.2 or 43.8 dB applies. + +For band n46, n96 and n102, the ACLR shall be higher than the value specified in Table 6.6.3.5.2-1a. + +**Table 6.6.3.5.2-1a: Base station ACLR limit for band n46, n96 and n102** + +| 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 | ACLR limit | +|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------|-------------------| +| 10, 20, 40, 60, 80 | $BW_{\text{Channel}}$ | NR of same BW (Note 2) | Square ( $BW_{\text{Config}}$ ) | 35 dB | +| | $2 \times BW_{\text{Channel}}$ | NR of same BW (Note 2) | Square ( $BW_{\text{Config}}$ ) | 40 dB | + +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}}$ ). + +The ACLR absolute *basic limit* is specified in table 6.6.3.5.2-2. + +**Table 6.6.3.5.2-2: Base station ACLR absolute *basic limit*** + +| BS category / BS class | ACLR 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 | + +For operation in non-contiguous spectrum or multiple bands except for band n46, n96 and n102, the ACLR shall be higher than the value specified in table 6.6.3.5.2-3. + +**Table 6.6.3.5.2-3: Base Station 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_{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
37.2 dB (Note 5) | +| | $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
36.8 dB (Note 5) | +| | $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 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.
Note 5: For BS operating in band n104, ACLR requirement 37.2 or 36.8 dB applies. For BS operating in other bands, ACLR requirement 44.2 or 43.8 dB applies. | | | | | | + +For operation in non-contiguous spectrum for band n46, n96 and n102, the ACLR shall be higher than the value specified in Table 6.6.3.2-3a. + +**Table 6.6.3.5.2-3a: Base Station ACLR limit in non-contiguous spectrum for band n46, n96 and n102** + +| BS channel bandwidth of NR carrier transmitted BW_{\text{Channel}} adjacent to sub-block gap or inter RF Bandwidth gap (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 | ACLR limit | +|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|-------------------| +| 10, 20, 40, 60, 80 | $W_{\text{gap}} \geq 60$ | 10 MHz | 20 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 35 dB | +| | $W_{\text{gap}} \geq 80$ | 30 MHz | 20 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 40 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}}$ ). | | | | | | + +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 assumed filter for the adjacent channel frequency is defined in table 6.6.3.5.2-4 and the filters on the assigned channels are defined in table 6.6.3.5.2-6. + +For operation in non-contiguous spectrum or multiple bands except for band n46, n96 and n102, the CACLR for NR 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.2-4. + +**Table 6.6.3.5.2-4: Base station CACLR limit** + +| 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 | CACLR limit | +|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|-----------------------------| +| 5, 10, 15, 20 | $5 \leq W_{\text{gap}} < 15$ (Note 3) | 2.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 44.2 dB
37.2 dB (Note 5) | +| | $5 \leq W_{\text{gap}} < 45$ (Note 4) | 7.5 MHz | 5 MHz NR (Note 2) | | | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $10 < W_{\text{gap}} < 20$ (Note 3)
$10 \leq W_{\text{gap}} < 50$ (Note 4) | 10 MHz | 20 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 43.8 dB
36.8 dB (Note 5) | +| | $20 \leq W_{\text{gap}} < 60$ (Note 4)
$20 \leq W_{\text{gap}} < 30$ (Note 3) | 30 MHz | 20 MHz NR (Note 2) | | | + +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 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. +Note 5: For BS operating in band n104, ACLR requirement 37.2 or 36.8 dB applies. For BS operating in other bands, ACLR requirement 44.2 or 43.8 dB applies. + +For operation in non-contiguous spectrum for band n46, n96 and n102, the CACLR for NR carriers located on either side of the sub-block gap shall be higher than the value specified in Table 6.6.3.5.2-4a. + +**Table 6.6.3.5.2-4a: Base Station CACLR limit for band n46, n96 and n102** + +| BS channel bandwidth of NR carrier transmitted BWchannel adjacent to sub-block gap or inter RF Bandwidth gap (MHz) | Sub-block or Inter RF Bandwidth gap size (Wgap) 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 | +|--------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|--------------------| +| 10, 20, 40, 60, 80 | $20 \leq W_{gap} < 60$ | 10 MHz | 20 MHz NR (Note 2) | Square (BW Config ) | 35 dB | +| | $40 < W_{gap} < 80$ | 30 MHz | 20 MHz NR (Note 2) | Square (BW Config ) | 40 dB | + +Note 1: BWConfig is the transmission bandwidth configuration of the assumed adjacent channel carrier. + +Note 2: With SCS that provides largest transmission bandwidth configuration (BWConfig). + +The CACLR absolute *basic limit* is specified in table 6.6.3.5.2-5. + +**Table 6.6.3.5.2-5: Base station CACLR absolute *basic limit*** + +| BS category / BS class | 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 | + +**Table 6.6.3.5.2-6: 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 | +|-------------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| NR | NR of same BW with SCS that provides largest transmission bandwidth configuration | + +### 6.6.3.5.3 BS type 1-C + +The ACLR test requirements for *BS type 1-C* are given in table 6.6.3.5.2-1 or 6.6.3.5.2-3 applies per *antenna connector*. Conformance can be shown by meeting the ACLR limit in table 6.6.3.5.2-1 or 6.6.3.5.2-3, or the absolute *basic limits* in table 6.6.3.5.2-2, whichever is less stringent. + +The CACLR test requirements for *BS type 1-C* are given in table 6.6.3.5.2-4 applies per *antenna connector*. Conformance can be shown by meeting the CACLR limit in table 6.6.3.5.2-4 or the absolute *basic limits* in table 6.6.3.5.2-5, whichever is less stringent. + +For Band n41 and n90 operation in Japan, absolute ACLR limits shall be applied to the sum of the absolute ACLR power over all *antenna connectors* for *BS type 1-C*. + +### 6.6.3.5.4 BS type 1-H + +The ACLR absolute *basic limits* in table 6.6.3.5.2-2+ X (where $X = 10\log_{10}(N_{TXU,countedpercell})$ ) or the ACLR *limits* in table 6.6.3.5.2-1, or 6.6.3.5.2-3, whichever is less stringent, shall apply for each *TAB connector TX min cell group*. + +The CACLR absolute *basic limits* in table 6.6.3.5.2-5 + X, (where $X = 10\log_{10}(N_{TXU,countedpercell})$ ) or the CACLR *limits* in table 6.6.3.5.2-4, whichever is less stringent, shall apply for each *TAB connector TX min cell group*. + +Conformance to the *BS type 1-H* ACLR (CACLR) limit 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 (CACLR) limit of the BS. This shall apply 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 this *TAB connector* centred on the adjacent channel frequency shall be greater than or equal to the ACLR (CACLR) limit of the 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 (CACLR) absolute *basic limit* of *BS type 1-H* are 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 (CACLR) absolute *basic limit* + X (where $X = 10\log_{10}(N_{\text{TXU, countedpercell}})$ ) of the BS. This shall apply 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 (CACLR) absolute *basic limit* of the BS scaled by $X - 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.4 Operating band unwanted emissions + +### 6.6.4.1 Definition and applicability + +Unless otherwise stated, the operating band unwanted emission (OBUE) limits in FR1 are defined from $\Delta f_{\text{OBUE}}$ below the lowest frequency of each supported downlink *operating band* 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 the NR *operating bands*. + +The requirements shall apply whatever the type of transmitter considered and for all transmission modes foreseen by the manufacturer's specification. In addition, for a BS operating in non-contiguous spectrum, the requirements apply inside any sub-block gap. In addition, for a BS operating in multiple bands, the requirements apply inside any Inter RF Bandwidth gap. + +*Basic limits* are specified in the tables below, where: + +- $\Delta f$ is the separation between the channel 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 channel edge frequency and the centre of the measuring filter. +- $f_{\text{offset}_{\text{max}}}$ is the offset to the frequency $\Delta f_{\text{OBUE}}$ outside the downlink *operating band*, where $\Delta f_{\text{OBUE}}$ is defined in table 6.6.1-1. +- $\Delta f_{\text{max}}$ is equal to $f_{\text{offset}_{\text{max}}}$ minus half of the bandwidth of the measuring filter. + +For a *multi-band 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 *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 clauses 6.6.4.5.2 to 6.6.4.5.5 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 a *multi-band 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 *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 * \Delta f_{OBUE}$ , $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 *basic 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 *basic limits* 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. + +For a multicarrier *single-band connector* or a *single-band 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 *single-band 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 subclauses 6.6.4.5.2 to 6.6.4.5.5 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 Wide Area BS, the requirements of either clause 6.6.4.5.2 (Category A limits) or clause 6.6.4.5.3 (Category B limits) shall apply. + +For Medium Range BS, the requirements in clause 6.6.4.5.4 shall apply (Category A and B). + +For Local Area BS, the requirements of clause 6.6.4.5.5 shall apply (Category A and B). + +The requirements shall also apply if the BS supports NB-IoT operation in NR in-band. + +The application of either Category A or Category B *basic limits* shall be the same as for transmitter spurious emissions in clause 6.6.5. + +#### 6.6.4.2 Minimum requirement + +The minimum requirement applies per *single-band connector*, or per *multi-band connector* supporting transmission in the *operating band*. + +The minimum requirement for *BS type 1-C* is defined in TS 38.104 [2], clause 6.6.4.3. + +The minimum requirement for *BS type 1-H* is defined in TS 38.104 [2], clause 6.6.4.4. + +#### 6.6.4.3 Test purpose + +This test measures the emissions close to the assigned channel bandwidth of the wanted signal, while the transmitter is in operation. + +#### 6.6.4.4 Method of test + +##### 6.6.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.9.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.9.1. +- $B_{\text{RFBW\_T}}$ and $B'_{\text{RFBW\_T}}$ in multi-band operation, see clause 4.9.1. + +##### 6.6.4.4.2 Procedure + +For *BS type 1-H* where there may be multiple *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex D.3.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect the *single-band connector* or *multi-band connector* under test to measurement equipment as shown in annex D.1.1 for *BS type 1-C* or in annex D.3.1 for *BS type 1-H*. All 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) For a connectors declared to be capable of single carrier operation only, set the representative connectors under test to transmit according to the applicable test configuration in clause 4.8 at *rated carrier output power* $P_{\text{rated,c,AC}}$ for *BS type 1-C* and $P_{\text{rated,c,TABC}}$ for *BS type 1-H* (D.21). Channel set-up shall be according to NR-FR1-TM 1.1. + +For a connector under test declared to be capable of multi-carrier and/or CA operation set the connector under test to transmit on all carriers configured using the applicable test configuration and corresponding power setting specified in clauses 4.7 and 4.8 using the corresponding test models or set of physical channels in clause 4.9.2. + +For a BS declared to be capable of NB-IoT operation in NR in-band (D.41), test shall be performed using N-TM according to clause 4.9.2.2.9. + +- 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. For connector under test declared to operate 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. +- 4) Repeat the test for the remaining test cases, with the channel set-up according to NR-FR1-TM 1.2. + +In addition, for *multi-band connectors*, the following steps shall apply: + +- 5) 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.6.4.5 Test requirements + +### 6.6.4.5.1 General requirements + +### 6.6.4.5.2 Basic limits for Wide Area BS (Category A) + +For BS operating in Bands n5, n8, n12, n13, n14, n18, n26, n28, n29, n31, n71, n72, n85, n105, n106, *basic limits* are specified in table 6.6.4.5.2-1. + +**Table 6.6.4.5.2-1: Wide Area BS operating band unwanted emission limits (NR bands below 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 (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}$ | -13 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 -13 dBm/100 kHz. | | | | | +| NOTE 2: For a multi-band connector with Inter RF Bandwidth gap $< 2 * \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_{\max} < 10 \text{ MHz}$ . | | | | | + +For BS operating in Bands n1, n2, n3, n7, n24, n25, n30, n34, n38, n39, n40, n41, n50, n54, n65, n66, n70, n74, n75, n92, n94, n109 *basic limits* are specified in table 6.6.4.5.2-2: + +**Table 6.6.4.5.2-2: Wide Area BS operating band unwanted emission limits +(1GHz < NR bands ≤ 3GHz) 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 | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------|-----------------------| +| $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 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 -13 dBm/1 MHz. + +NOTE 2: For a *multi-band connector* with Inter RF Bandwidth gap $< 2 * \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, 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}$ . + +For BS operating in Bands n48, n77, n78, n79, *basic limits* are specified in table 6.6.4.5.2-3: + +**Table 6.6.4.5.2-3: Wide Area BS operating band unwanted emission limits +(NR bands >3GHz) 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 | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------|-----------------------| +| $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 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 -13 dBm/1 MHz. + +NOTE 2: For a *multi-band connector* with Inter RF Bandwidth gap $< 2 * \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, 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}$ . + +#### 6.6.4.5.3 Basic limits for Wide Area BS (Category B) + +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 clause 6.6.4.5.3.1 or clause 6.6.4.5.3.2 shall be applied. + +##### 6.6.4.5.3.1 Category B requirements (Option 1) + +For BS operating in Bands n5, n8, n12, n20, n26, n28, n29, n31, n67, n72, n71, n85, n105, *basic limits* are specified in table 6.6.4.5.3.1-1: + +**Table 6.6.4.5.3.1-1: Wide Area BS operating band unwanted emission limits +(NR bands below 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 (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, 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}$ . | | | | | + +For BS operating in Bands n1, n2, n3, n7, n25, n34, n38, n39, n40, n41, n50, n65, n66, n70, n75, n92, n94, n109 *basic limits* are specified in tables 6.6.4.5.3.1-2: + +**Table 6.6.4.5.3.1-2: Wide Area BS operating band unwanted emission limits +(1GHz < NR bands $\leq$ 3GHz) 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 | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------|-------------------------|-----------------------|--| +| $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.5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -15 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, 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}$ . | | | | | + +For BS operating in Bands n48, n77, n78, n79, *basic limits* are specified in tables 6.6.4.5.3.1-3: + +**Table 6.6.4.5.3.1-3: Wide Area BS operating band unwanted emission limits (NR bands >3GHz) 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 | +|----------------------------------------------------------------------|------------------------------------------------------------------------------|-------------------------|-----------------------| +| $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 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}$ . + +For BS type 1-C operating in Band n104, the limits are specified in table 6.6.4.5.3.1-4: + +**Table 6.6.4.5.3.1-4: Wide Area BS type 1-C operating band unwanted emission limits for band n104 for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 20 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 20.05 \text{ MHz}$ | | 100 kHz | +| $20 \text{ MHz} \leq \Delta f < \min(40 \text{ MHz}, \Delta f_{max})$ | $20.05 \text{ MHz} \leq f\_offset < \min(40.05 \text{ MHz}, f\_offset_{max})$ | -12.2 dBm | 100 kHz | +| $40 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $40.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*. Exception is $\Delta f \geq 40 \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*. + +NOTE 3: The requirement is not applicable when $\Delta f_{max} < 40 \text{ MHz}$ . + +For BS type 1-H operating in Band n104, *basic limits* are specified in table 6.6.4.5.3.1-5: + +**Table 6.6.4.5.3.1-5: Wide Area BS type 1-H operating band unwanted emission limits for band n104 for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits | Measurement bandwidth | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 50 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 50.05 \text{ MHz}$ | | 100 kHz | +| $50 \text{ MHz} \leq \Delta f < \min(100 \text{ MHz}, \Delta f_{\max})$ | $50.05 \text{ MHz} \leq f\_offset < \min(100.05 \text{ MHz}, f\_offset_{\max})$ | -12.2 dBm | 100 kHz | +| $100 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $100.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 . Exception is $\Delta f \geq 100 \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_{\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_{\max} < 100 \text{ MHz}$ . | | | | + +#### 6.6.4.5.3.2 Category B requirements (Option 2) + +The limits in this clause are intended for Europe and may be applied regionally for BS operating in Bands n1, n3, n7, n8, n38, n65, n100 or n101. + +For a BS operating in Bands n1, n3, n8, n65 or BS type 1-C operating in bands n7, n38, n100 or n101, *basic limits* are specified in table 6.6.4.5.3.2-1: + +**Table 6.6.4.5.3.2-1: Regional Wide Area BS operating band unwanted emission limits 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 | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|-------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$ | -12.5dBm | 30 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | (Note 5) | 30 kHz | +| (Note 4) | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$ | -24.5dBm (Note 5) | 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.5dBm (Note 5) | 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 3) | 1 MHz | +| NOTE 1: For a 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. For BS supporting multi-band operation, either this limit or -16dBm/100kHz ( $f\_offset$ adjusted according to the measurement bandwidth), whichever is less stringent, shall apply at $\Delta f \geq 10 \text{ MHz}$ for operating bands $< 1 \text{ GHz}$ . | | | | +| NOTE 2: For a multi-band connector 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 , 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}$ . | | | | +| NOTE 4: This frequency range ensures that the range of values of $f\_offset$ is continuous. | | | | +| NOTE 5: For BS supporting multi-band operation, either this limit or -16dBm/100kHz ( $f\_offset$ adjusted according to the measurement bandwidth), whichever is less stringent, shall apply for operating bands $< 1 \text{ GHz}$ . | | | | + +#### 6.6.4.5.4 Basic limits for Medium Range BS (Category A and B) + +For Medium Range BS in NR bands $\leq 3$ GHz, *basic limits* are specified in table 6.6.4.5.4-1 and table 6.6.4.5.4-2, except for Band n104. + +For Medium Range BS in NR bands $> 3$ GHz, *basic limits* are specified in table 6.6.4.5.4-3 and table 6.6.4.5.4-4, except for Band n104. + +For the tables in this clause for *BS type 1-C* $P_{\text{rated,x}} = P_{\text{rated,c,AC}}$ , and for *BS type 1-H* $P_{\text{rated,x}} = P_{\text{rated,c,cell}} - 10 \cdot \log_{10}(N_{\text{TXU, counted per cell}})$ , and for *BS type 1-O* $P_{\text{rated,x}} = P_{\text{rated,c,TRP}} - 9$ dB. + +**Table 6.6.4.5.4-1: Medium Range BS operating band unwanted emission limits, $31 < P_{\text{rated,x}} \leq 38$ dBm (NR bands $\leq 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})$ | $P_{\text{rated,x}} - 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,x}} - 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,x}} - 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_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.4.5.4-2: Medium Range BS operating band unwanted emission limits, $P_{\text{rated,x}} \leq 31$ dBm (NR bands $\leq 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}$ | $-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 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 $-29 \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_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.4.5.4-3: Medium Range BS operating band unwanted emission limits, $31 < P_{\text{rated,x}} \leq 38$ dBm (NR bands >3GHz)** + +| 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})$ | $P_{\text{rated,x}} - 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,x}} - 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,x}} - 60 \text{ dB}, -25 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band connector* with Inter RF Bandwidth gap $< 2 * \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_{\max} < 10 \text{ MHz}$ . + +**Table 6.6.4.5.4-4: Medium Range BS operating band unwanted emission limits, $P_{\text{rated,x}} \leq 31$ dBm (NR bands >3GHz)** + +| 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}$ | $-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 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 $-29 \text{ dBm}/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band connector* with Inter RF Bandwidth gap $< 2 * \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_{\max} < 10 \text{ MHz}$ . + +For BS type I-C operating in Band n104, the limits are specified in Table 6.6.4.5.4-5 and Table 6.6.4.5.4-7. + +**Table 6.6.4.5.4-5: Medium Range BS type 1-C operating band unwanted emission limits for band n104, $31 < P_{\text{rated,x}} \leq 38$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits | Measurement bandwidth | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|----------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 20 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 20.05 \text{ MHz}$ | | 100 kHz | +| $20 \text{ MHz} \leq \Delta f < \min(40 \text{ MHz}, \Delta f_{\max})$ | $20.05 \text{ MHz} \leq f\_offset < \min(40.05 \text{ MHz}, f\_offset_{\max})$ | $P_{\text{rated,x}} - 58.2 \text{ dB}$ | 100 kHz | +| $40 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $40.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\text{Min}(P_{\text{rated,x}} - 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 40 \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,x}} - 60 \text{ dB}, -25 \text{ dBm})/100 \text{ kHz}$ . | | | | +| NOTE 2: For a multi-band connector with Inter RF Bandwidth gap $< 2 * \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_{\max} < 40 \text{ MHz}$ . | | | | + +For BS type 1-H operating in Band n104, *basic limits* are specified in Table 6.6.4.5.4-6 and Table 6.6.4.5.4-8: + +**Table 6.6.4.5.4-6: Medium Range BS type 1-H operating band unwanted emission limits for band n104, $31 < P_{\text{rated,x}} \leq 38$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits | Measurement bandwidth | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|----------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 50 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 50.05 \text{ MHz}$ | | 100 kHz | +| $50 \text{ MHz} \leq \Delta f < \min(100 \text{ MHz}, \Delta f_{\max})$ | $50.05 \text{ MHz} \leq f\_offset < \min(100.05 \text{ MHz}, f\_offset_{\max})$ | $P_{\text{rated,x}} - 58.2 \text{ dB}$ | 100 kHz | +| $100 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $100.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\text{Min}(P_{\text{rated,x}} - 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 100 \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,x}} - 60 \text{ dB}, -25 \text{ dBm})/100 \text{ kHz}$ . | | | | +| NOTE 2: For a multi-band connector with Inter RF Bandwidth gap $< 2 * \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_{\max} < 100 \text{ MHz}$ . | | | | + +**Table 6.6.4.5.4-7: Medium Range BS type 1-C operating band unwanted emission limits for band 104,** + $P_{\text{rated,x}} \leq 31 \text{ dBm}$ + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits | Measurement bandwidth | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 20 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 20.05 \text{ MHz}$ | | 100 kHz | +| $20 \text{ MHz} \leq \Delta f < \min(40 \text{ MHz}, \Delta f_{\max})$ | $20.05 \text{ MHz} \leq f\_offset < \min(40.05 \text{ MHz}, f\_offset_{\max})$ | -27.2 dBm | 100 kHz | +| $40 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $40.05 \text{ MHz} \leq f\_offset < f\_offset_{\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 40 \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 -29 dBm/100kHz. | | | | +| NOTE 2: For a multi-band connector with Inter RF Bandwidth gap $< 2 * \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_{\max} < 40 \text{ MHz}$ . | | | | + +**Table 6.6.4.5.4-8: Medium Range BS type 1-H operating band unwanted emission limits for band 104,** + $P_{\text{rated,x}} \leq 31 \text{ dBm}$ + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits | Measurement bandwidth | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 50 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 50.05 \text{ MHz}$ | | 100 kHz | +| $50 \text{ MHz} \leq \Delta f < \min(100 \text{ MHz}, \Delta f_{\max})$ | $50.05 \text{ MHz} \leq f\_offset < \min(100.05 \text{ MHz}, f\_offset_{\max})$ | -27.2 dBm | 100 kHz | +| $100 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $100.5 \text{ MHz} \leq f\_offset < f\_offset_{\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 100 \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 -29 dBm/100kHz. | | | | +| NOTE 2: For a multi-band connector with Inter RF Bandwidth gap $< 2 * \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_{\max} < 100 \text{ MHz}$ . | | | | + +#### 6.6.4.5.5 Basic limits for Local Area BS (Category A and B) + +For Local Area BS in NR bands $\leq 3 \text{ GHz}$ , *basic limits* are specified in table 6.6.4.5.5-1 except for n46, n96, n102 and n104. + +For Local Area BS in NR bands $> 3 \text{ GHz}$ , *basic limits* are specified in table 6.6.4.5.5-2 except for n46, n96, n102 and n104. + +**Table 6.6.4.5.5-1: Local Area BS operating band unwanted emission limits (NR 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 (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}$ | $-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 | | +| $10\text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05\text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 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 -37dBm/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_{\max} < 10\text{ MHz}$ . + +**Table 6.6.4.5.5-2: Local Area BS operating band unwanted emission limits (NR bands $> 3\text{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 | | +| $10\text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $10.05\text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 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 -37dBm/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_{\max} < 10\text{ MHz}$ . + +For BS type 1-C operating in Band n104, the limits are specified in Table 6.6.4.5.5-3. + +**Table 6.6.4.5.5-3: Local Area BS type 1-C operating band unwanted emission limits for band n104** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits (Note 1, 2) | Measurement bandwidth | +|----------------------------------------------------------------------|------------------------------------------------------------------------------|--------------------------|-----------------------| +| $0\text{ MHz} \leq \Delta f < 20\text{ MHz}$ | $0.05\text{ MHz} \leq f\_offset < 20.05\text{ MHz}$ | | 100 kHz | +| $20\text{ MHz} \leq \Delta f < \min(40\text{ MHz}, \Delta f_{\max})$ | $20.05\text{ MHz} \leq f\_offset < \min(40.05\text{ MHz}, f\_offset_{\max})$ | -35.2 dBm | 100 kHz | +| $40\text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $40.05\text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 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 40\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 -37dBm/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_{\max} < 40\text{ MHz}$ . + +For BS type 1-H operating in Band n104, basic limits are specified in Table 6.6.4.5.5-4. + +**Table 6.6.4.5.5-4: Local Area BS type 1-H operating band unwanted emission limits for band n104** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits (Note 1, 2) | Measurement bandwidth | +|-------------------------------------------------------------------------|---------------------------------------------------------------------------------|--------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 50 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 50.05 \text{ MHz}$ | | 100 kHz | +| $50 \text{ MHz} \leq \Delta f < \min(100 \text{ MHz}, \Delta f_{\max})$ | $50.05 \text{ MHz} \leq f\_offset < \min(100.05 \text{ MHz}, f\_offset_{\max})$ | -35.2 dBm | 100 kHz | +| $100 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $100.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -37 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 100 \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 -37dBm/100kHz. + +NOTE 2: For a *multi-band connector* with *Inter RF Bandwidth gap* $< 2 * \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_{\max} < 100 \text{ MHz}$ . + +#### 6.6.4.5.5A Basic limits for Local Area and Medium Range BS for band n46, n96 and n102 (Category A and B) + +For Local Area and Medium Range BS operating in Band n46, basic limits for 10 MHz channel bandwidth are specified in table 6.6.4.5.5A-1. For Local Area and Medium Range BS operating in Band n46, n96 and Band n102, basic limits for 20 MHz, 40 MHz, 60 MHz and 80 MHz channel bandwidth are specified in table 6.6.4.5.5A-2. The nominal bandwidth $N = BW_{\text{Channel}}$ of the transmitted carrier. For one non-transmitted channel basic limits are specified in table 6.6.4.5.5A-3, and for two non-transmitted channels basic limits are specified in table 6.6.4.5.5A-4. + +**Table 6.6.4.5.5A-1: Medium Range BS and Local Area BS operating band unwanted emission limits for 10 MHz channel bandwidth for band n46** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits (Note 1) | Measurement bandwidth | +|-------------------------------------------------------------------------|---------------------------------------------------------------------------------|---------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 0.55 \text{ MHz}$ | | 100 kHz | +| $0.5 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.55 \text{ MHz} \leq f\_offset < \min(5.05 \text{ MHz}, f\_offset_{\max})$ | | 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})$ | | 100 kHz | +| $10 \text{ MHz} \leq \Delta f < \min(85 \text{ MHz}, \Delta f_{\max})$ | $10.05 \text{ MHz} \leq f\_offset < \min(85.05 \text{ MHz}, f\_offset_{\max})$ | $\text{Max}(P_{\text{rated},x} - 57.3 \text{ dB}, -40 \text{ dBm})$ | 100 kHz | +| $85 \text{ MHz} \leq \Delta f < \min(103 \text{ MHz}, \Delta f_{\max})$ | $85.05 \text{ MHz} \leq f\_offset < \min(103.05 \text{ MHz}, f\_offset_{\max})$ | $\text{Max}(P_{\text{rated},x} - 59.3 \text{ dB}, -40 \text{ dBm})$ | 100 kHz | +| $103 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $103.05 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $\text{Max}(P_{\text{rated},x} - 64.3 \text{ dB}, -40 \text{ dBm})$ | 100 kHz | + +NOTE 1: For a 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 $\text{Max}(P_{\text{rated},x} - 57.3 \text{ dB}, -40 \text{ dBm})/100 \text{ kHz}$ . + +**Table 6.6.4.5.5A-2: Medium Range BS and Local Area BS operating band unwanted emission limits for 20 MHz, 40 MHz, 60 MHz and 80 MHz channel bandwidth for band n46, n96 and n102** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits (Note 1) | Measurement bandwidth | +|----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|-----------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.05 \text{ MHz}$ | | 100 kHz | +| $1 \text{ MHz} \leq \Delta f < \min(0.5N \text{ MHz}, \Delta f_{max})$ | $1.05 \text{ MHz} \leq f\_offset < \min((0.5N+0.05) \text{ MHz}, f\_offset_{max})$ | | 100 kHz | +| $0.5N \text{ MHz} \leq \Delta f < \min(N \text{ MHz}, \Delta f_{max})$ | $(0.5N+0.05) \text{ MHz} \leq f\_offset < \min((N+0.05) \text{ MHz}, f\_offset_{max})$ | | 100 kHz | +| $0 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 1.05 \text{ MHz}$ | | 100 kHz | +| $8.5N \text{ MHz} \leq \Delta f < \min(10.3N \text{ MHz}, \Delta f_{max})$ | $(8.5N+0.05) \text{ MHz} \leq f\_offset < \min((10.3N+0.05) \text{ MHz}, f\_offset_{max})$ | | 100 kHz | +| $10.3N \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $(10.3N+0.05) \text{ MHz} \leq f\_offset < f\_offset_{max}$ | | 100 kHz | + +NOTE 1: For a 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 N \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 . + +In the case of one or two non-transmitted 20 MHz channels between transmitted channels, when a NR-U channel bandwidth of 60 MHz or 80 MHz have been assigned, the spectrum emission mask for non-transmitted channels specified in Table 6.6.4.5.5A-3 and Table 6.6.4.5.5A-4 applies for one and two non-transmitted channels respectively. The spectrum emission mask for non-transmitted channels apply to frequencies ( $\Delta f_{BE\_offset}$ ) starting from the edge of the last transmitted channel of the channels assigned for NR-U channel bandwidth. The relative power of any BS emission shall not exceed the most stringent levels given by Table 6.6.4.5.5A-2 and Table 6.6.4.5.5A-3 in the case of non-transmitted channels between transmitted channels. + +**Table 6.6.4.5.5A-3: Medium Range BS operating band unwanted emission limits for one non-transmitted channel for 60 MHz and 80MHz channel bandwidth for band n46, n96 and n102** + +| Frequency offset of measurement filter -3dB point, $\Delta f_{BE\_offset}$ | Frequency offset of measurement filter centre frequency, $f\_BE\_offset$ | Basic limits | Measurement bandwidth | +|----------------------------------------------------------------------------|--------------------------------------------------------------------------|---------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f_{BE\_offset} < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_BE\_offset < 1.05 \text{ MHz}$ | | 100 kHz | +| $1 \text{ MHz} \leq \Delta f_{BE\_offset} < 10 \text{ MHz}$ | $1.05 \text{ MHz} \leq f\_BE\_offset < 10.05 \text{ MHz}$ | | 100 kHz | +| $10 \text{ MHz} \leq \Delta f_{BE\_offset} < 19 \text{ MHz}$ | $10.05 \text{ MHz} \leq f\_BE\_offset < 19.05 \text{ MHz}$ | | 100 kHz | +| $19 \text{ MHz} \leq \Delta f_{BE\_offset} < 19.9 \text{ MHz}$ | $19.05 \text{ MHz} \leq f\_BE\_offset < 19.95 \text{ MHz}$ | | 100 kHz | + +**Table 6.6.4.5.5A-4: Medium Range BS and Local Area BS operating band unwanted emission limits for two non-transmitted channels of 80 MHz channel bandwidth for band n46, n96 and n102** + +| Frequency offset of measurement filter -3dB point, $\Delta f_{BE\_offset}$ | Frequency offset of measurement filter centre frequency, $f\_BE\_offset$ | Basic limits | Measurement bandwidth | +|----------------------------------------------------------------------------|--------------------------------------------------------------------------|---------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f_{BE\_offset} < 1 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_BE\_offset < 1.05 \text{ MHz}$ | | 100 kHz | +| $1 \text{ MHz} \leq \Delta f_{BE\_offset} < 10 \text{ MHz}$ | $1.05 \text{ MHz} \leq f\_BE\_offset < 10.05 \text{ MHz}$ | | 100 kHz | +| $10 \text{ MHz} \leq \Delta f_{BE\_offset} < 30 \text{ MHz}$ | $10.05 \text{ MHz} \leq f\_BE\_offset < 30.05 \text{ MHz}$ | | 100 kHz | +| $30 \text{ MHz} \leq \Delta f_{BE\_offset} < 39 \text{ MHz}$ | $30.05 \text{ MHz} \leq f\_BE\_offset < 39.05 \text{ MHz}$ | | 100 kHz | +| $39 \text{ MHz} \leq \Delta f_{BE\_offset} < 39.9 \text{ MHz}$ | $39.05 \text{ MHz} \leq f\_BE\_offset < 39.95 \text{ MHz}$ | | 100 kHz | + +In the case of non-transmitted 20 MHz channel(s) on the edges of an assigned NR-U channel bandwidth the general spectrum emission mask specified in Table 6.6.4.5.5A-2 is applied to the remaining transmitted channels to form an additional spectrum emission mask. The additional spectrum emission mask is applied to the total bandwidth of the remaining transmitted channels. + +The additional spectrum emission mask is floored at t . + +The relative power of any BS emission shall not exceed the most stringent levels given by the initial general spectrum emission mask with full channel bandwidth and the additional spectrum emission mask with the channel bandwidth of the transmitted channels in the case of non-transmitted channels at the edge of an assigned NR-U channel bandwidth. + +#### 6.6.4.5.6 Basic limits for additional requirements + +##### 6.6.4.5.6.1 Limits in FCC Title 47 + +In addition to the requirements in clauses 6.6.4.5.2 to 6.6.4.5.5, the BS may have to comply with the applicable emission limits established by FCC Title 47 [13], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +##### 6.6.4.5.6.2 Protection of DTT + +In certain regions the following requirement may apply for protection of DTT. For *BS type 1-C* or *BS type 1-H* operating in Band 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.4.5.6.2-1, *basic limit* is $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.4.5.6.2-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$ (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 BS needed to verify compliance with the regional requirement. Compliance with the regional requirement can be determined using the method outlined in TS 36.104 [22], annex G. + +##### 6.6.4.5.6.3 Additional operating band unwanted emissions limits for Band n48 + +The following requirement may apply to BS operating in Band n48 in certain regions. Emissions shall not exceed the maximum levels specified in Table 6.6.4.5.6.3-1. + +**Table 6.6.4.5.6.3-1: Additional operating band unwanted emission limits for Band n48** + +| 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 (Note) | +|-------------------|---------------------------------------------------------------|------------------------------------------------------------------------------|---------------------|------------------------------| +| 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 | + +NOTE: 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.6.4.5.6.4 Additional operating band unwanted emissions limits for Band n53 + +The following requirement may apply to BS operating in Band n53 in certain regions. Emissions shall not exceed the maximum levels specified in table 6.6.4.5.6.4-1. + +**Table 6.6.4.5.6.4-1: Additional operating band unwanted emission limits for Band n53** + +| 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 (Note) | +|-------------------------|-----------------------|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------|------------------------------| +| 5 | 2400 - 2477.5 | $6 \text{ MHz} < \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 | +| 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 | +| 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 | +| 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 | + +NOTE: 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.6.4.5.6.5 Protection of GPS + +In regions where FCC regulation applies, requirements for protection of GPS according to FCC Order DA 10-48 applies for operation in Band n24. The following normative requirement covers *BS type 1-C* or *BS type 1-H* operating in Band n24, to be used together with other information about the site installation to verify compliance with the requirement in FCC Order DA 10-48. + +The level of emissions in the 1541 – 1650 MHz band, measured in measurement bandwidth according to Table 6.6.4.5.6.5-1 shall not exceed the *basic limits* $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.4.5.6.5-1: Declared emissions *basic limits* for protection of GPS** + +| 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) | +|----------------|-----------------------|---------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| n24 | 1541 - 1559 | $P_{EM\_B24,a}$ | | $P_{EM\_B24,f}$ | +| | 1559 - 1610 | $P_{EM\_B24,b}$ | $P_{EM\_B24,d}$ | | +| | 1610 - 1650 | $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_{EM} + G_{ant}$ where $P_{EM}$ denotes the unwanted emission level at the antenna connector and $G_{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. + +#### 6.6.4.5.6.6 Additional operating band unwanted emissions limits for operation with shared spectrum channel access + +In addition, for operation with shared spectrum channel access, the BS may have to comply with the applicable operating band unwanted emission limits established regionally, when deployed in regions where those limits apply and under the conditions declared by the manufacturer. The regional requirements may be in the form of conducted power, power spectral density, EIRP and other types of limits. In case of regulatory limits based on EIRP, assessment of the EIRP level is described in Annex F.2. + +#### 6.6.4.5.6.7 Additional operating band unwanted emissions limits for Band n100 + +In CEPT countries where ECC Decision (20)02 ([25]) applies, the emissions shall not exceed the maximum levels specified in table 6.6.4.5.6.7-1. + +**Table 6.6.4.5.6.7-1: Additional operating band unwanted emission limits for Band n100** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Basic limits (Note) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ | $0.1 \text{ MHz} \leq f\_offset < 0.3 \text{ MHz}$ | 19.5 dBm | 200 kHz | +| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$ | $0.6 \text{ MHz} \leq f\_offset < 1.4 \text{ MHz}$ | 1 dBm | 800 kHz | +| $1 \text{ MHz} \leq \Delta f \leq 10 \text{ MHz}$ | $1.5 \text{ MHz} \leq f\_offset < 10.5$ | -8 dBm | 1 MHz | + +NOTE: The basic limits are derived from ECC Decision(20)02 [25] assuming a 17 dBi maximum antenna gain and 4dB losses, and assuming one antenna connector. + +#### 6.6.4.5.7 BS type 1-C + +The operating band unwanted emissions for *BS type 1-C* for each *antenna connector* shall be below the applicable *basic limits* defined in clauses 6.6.4.5.2 – 6.6.4.5.6. + +For Band n41 and n90 operation in Japan, the operating band unwanted emissions limits shall be applied to the sum of the emission power over all *antenna connectors* for *BS type 1-C*. + +#### 6.6.4.5.8 BS type 1-H + +The operating band unwanted emissions requirements for *BS type 1-H* are that for each *TAB connector TX min cell group* and each applicable *basic limit* in clauses 6.6.4.5.2 – 6.6.4.5.6, the power summation emissions at the *TAB connectors* of the *TAB connector TX min cell group* shall not exceed a BS limit specified as the *basic limit* + X, where $X = 10\log_{10}(N_{\text{TXU, countedpercell}})$ . + +NOTE: Conformance to the *BS type 1-H* 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 limit as defined in this clause for the respective frequency span. + +Or + +- 2) The unwanted emissions power at each *TAB connector* shall be less than or equal to the *BS type 1-H* limit as defined in this clause 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.5 Transmitter spurious emissions + +### 6.6.5.1 Definition and applicability + +The transmitter spurious emission limits shall apply from 9 kHz to 12.75 GHz, excluding the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of each supported downlink *operating band*, up to $\Delta f_{\text{OBUE}}$ above the highest frequency of each supported downlink *operating band*, where the $\Delta f_{\text{OBUE}}$ is defined in table 6.6.1. For some *operating bands*, the upper 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 [5]. + +For a *multi-band connector*, each supported *operating band* together with $\Delta f_{\text{OBUE}}$ around the band is excluded from the transmitter spurious emissions requirement. + +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 specification. + +The requirements shall apply to BS that support NR or NR with NB-IoT operation in NR in-band. + +Unless otherwise stated, all requirements are measured as mean power (RMS). + +For operation in region 2, where the FCC guidance for MIMO systems in FCC Title 47 [13] is applicable, $N_{\text{TXU, counted per cell}}$ shall be equal to one for the purposes of calculating the spurious emissions limits in clauses 6.6.5. For all other unwanted emissions requirements, $N_{\text{TXU, counted per cell}}$ shall be the value calculated according to clause 6.1. + +### 6.6.5.2 Minimum requirement + +The minimum requirement applies per *single-band connector*, or per *multi-band connector* supporting transmission in the *operating band*. + +The minimum requirement for *BS type 1-C* is defined in TS 38.104 [2], clause 6.6.5.3. + +The minimum requirement for *BS type 1-H* is defined in TS 38.104 [2], clause 6.6.5.4. + +### 6.6.5.3 Test purpose + +This test measures conducted spurious emissions while the transmitter is in operation. + +### 6.6.5.4 Method of test + +#### 6.6.5.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: + +- B when testing the spurious emissions below $F_{\text{DL\_low}} - \Delta f_{\text{OBUE}}$ , +- T when testing the spurious emissions above $F_{\text{DL\_high}} + \Delta f_{\text{OBUE}}$ ; see clause 4.9.1. + +*Base Station RF Bandwidth* positions to be tested for multi-carrier and/or CA: + +- $B_{\text{RFBW}}$ when testing the spurious frequencies below $F_{\text{DL\_low}} - \Delta f_{\text{OBUE}}$ ; $T_{\text{RFBW}}$ when testing the spurious frequencies above $F_{\text{DL\_high}} + \Delta f_{\text{OBUE}}$ in single-band operation; see clause 4.9.1. +- $B_{\text{RFBW\_T}}$ when testing the spurious frequencies below $F_{\text{DL\_low}} - \Delta f_{\text{OBUE}}$ of the lowest operating band; + $B'_{\text{RFBW\_T}}$ when testing the spurious frequencies above $F_{\text{DL\_high}} + \Delta f_{\text{OBUE}}$ of the highest operating band in multi-band operation, see clause 4.9.1. + +#### 6.6.5.4.2 Procedure + +For *BS type 1-H* where there may be multiple *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex D.3.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect the *single-band connector* or *multi-band connector* under test to measurement equipment as shown in annex D.1.1 for *BS type 1-C* and in annex D.3.1 for *BS type 1-H*. All connectors not under test shall be terminated. +- 2) Measurements shall use a measurement bandwidth in accordance to the conditions in clause 6.6.5.5. + +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) For a connectors declared to be capable of single carrier operation only (D.16), set the representative connectors under test to transmit according to the applicable test configuration in clause 4.8 at *rated carrier output power* ( $P_{\text{rated,c,AC}}$ , or $P_{\text{rated,c,TABC}}$ , D.21). Channel set-up shall be according to NR-FR1-TM 1.1. + +For a connector under test declared to be capable of multi-carrier and/or CA operation (D.15-D.16) set the connector under test to transmit on all carriers configured using the applicable test configuration and corresponding power setting specified in clauses 4.7 and 4.8 using the corresponding test models or set of physical channels in clause 4.9.2. + +For a BS declared to be capable of NB-IoT operation in NR in-band (D.41), test shall be performed using N-TM according to clause 4.9.2.2.9. + +- 4) Measure the emission at the specified frequencies with specified measurement bandwidth. + +In addition, for *multi-band connectors*, the following steps shall apply: + +- 5) 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.6.5.5 Test requirements + +### 6.6.5.5.1 Basic limits + +#### 6.6.5.5.1.1 Tx spurious emissions + +The limits of either table 6.6.5.5.1.1-1 (Category A limits) or table 6.6.5.5.1.1-2 (Category B limits) shall apply. The application of either Category A or Category B limits shall be the same as for operating band unwanted emissions in clause 6.6.4, and as declared by the manufacturer (D.4). + +**Table 6.6.5.5.1.1-1: General BS transmitter spurious emission limits in FR1, Category A** + +| Spurious frequency range | Basic limit | Measurement bandwidth | Notes | +|---------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------|------------------------| +| 9 kHz – 150 kHz | -13 dBm | 1 kHz | Note 1, Note 4 | +| 150 kHz – 30 MHz | | 10 kHz | Note 1, Note 4 | +| 30 MHz – 1 GHz | | 100 kHz | Note 1 | +| 1 GHz – 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 | +| 12.75 GHz - 26 GHz | -13 dBm | 1 MHz | Note 1, Note 2, Note 5 | +| NOTE 1: Measurement bandwidths as in ITU-R SM.329 [5], s4.1. | | | | +| NOTE 2: Upper frequency as in ITU-R SM.329 [5], s2.5 table 1. | | | | +| NOTE 3: Applies for Band for which the upper frequency edge of the DL operating band is greater than 2.55 GHz and less than or equal to 5.2 GHz. | | | | +| NOTE 4: This spurious frequency range applies only to BS type 1-C and BS type 1-H . | | | | +| NOTE 5: Applies for Band for which the upper frequency edge of the DL operating band is greater than 5.2 GHz. | | | | + +**Table 6.6.5.5.1.1-2: General BS transmitter spurious emission limits in FR1, Category B** + +| Spurious frequency range | Basic limit | Measurement bandwidth | Notes | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------|------------------------|--| +| 9 kHz – 150 kHz | -36 dBm | 1 kHz | Note 1, Note 4 | | +| 150 kHz – 30 MHz | | 10 kHz | Note 1, Note 4 | | +| 30 MHz – 1 GHz | | 100 kHz | Note 1 | | +| 1 GHz – 12.75 GHz | -30 dBm | 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 | | +| 12.75 GHz - 26 GHz | | 1 MHz | Note 1, Note 2, Note 5 | | +| NOTE 1: Measurement bandwidths as in ITU-R SM.329 [5], s4.1. | | | | | +| NOTE 2: Upper frequency as in ITU-R SM.329 [5], s2.5 table 1. | | | | | +| NOTE 3: Applies for Band for which the upper frequency edge of the DL operating band is greater than 2.55 GHz and less than or equal to 5.2 GHz. | | | | | +| NOTE 4: This spurious frequency range applies only to BS type 1-C and BS type 1-H . | | | | | +| NOTE 5: Applies for Band for which the upper frequency edge of the DL operating band is greater than 5.2 GHz. | | | | | + +#### 6.6.5.5.1.2 Protection of the BS receiver of own or different BS + +This requirement shall be applied for NR FDD operation in order to prevent the receivers of the BSs being desensitised by emissions from a BS transmitter. It is measured at the transmit *antenna connector* for *BS type 1-C* or at the *TAB* + +connector for BS type 1-H for any type of BS which has common or separate Tx/Rx antenna connectors / TAB connectors. + +The *basic limits* are provided in table 6.6.5.5.1.2-1. + +**Table 6.6.5.5.1.2-1: BS spurious emissions *basic limits* for protection of the BS receiver** + +| BS class | Frequency range | Basic limit | Measurement bandwidth | +|-----------------------------------------------------------------------------|------------------------------|-------------|-----------------------| +| Wide Area BS | $F_{UL\_low} - F_{UL\_high}$ | -96 dBm | 100 kHz | +| Medium Range BS | | -91 dBm | | +| Local Area BS | | -88 dBm | | +| NOTE 1: For BS operating in band n104, the basic limit is increased by 1dB. | | | | + +#### 6.6.5.5.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 NR *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, CDMA, UTRA, E-UTRA, NR, etc.) as listed below. + +The power of any spurious emission shall not exceed the *basic limits* of table 6.6.5.5.1.3-1 for a BS where requirements for co-existence with the system listed in the first column apply. For a *multi-band connector*, the exclusions and conditions in the Note column of table 6.6.5.5.1.3-1 apply for each supported *operating band*. + +**Table 6.6.5.5.1.3-1: BS spurious emissions limits for BS for co-existence with systems operating in other frequency bands** + +| System type for NR to co-exist with | Frequency range for co-existence requirement | Basic limit | Measurement bandwidth | Note | +|---------------------------------------------------------------|----------------------------------------------|-------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 921 – 960 MHz | -57 dBm | 100 kHz | This requirement does not apply to 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 BS operating in band n8, since it is already covered by the requirement in clause 6.6.5.5.1.2. | +| DCS1800 | 1805 – 1880 MHz | -47 dBm | 100 kHz | This requirement does not apply to BS operating in band n3. | +| | 1710 – 1785 MHz | -61 dBm | 100 kHz | This requirement does not apply to BS operating in band n3, since it is already covered by the requirement in clause 6.6.5.5.1.2. | +| PCS1900 | 1930 – 1990 MHz | -47 dBm | 100 kHz | This requirement does not apply to BS operating in band n2, n25 or band n70. | +| | 1850 – 1910 MHz | -61 dBm | 100 kHz | This requirement does not apply to BS operating in band n2 or n25 since it is already covered by the requirement in clause 6.6.5.5.1.2. | +| GSM850 or CDMA850 | 869 – 894 MHz | -57 dBm | 100 kHz | This requirement does not apply to BS operating in band n5 or n26. | +| | 824 – 849 MHz | -61 dBm | 100 kHz | This requirement does not apply to BS operating in band n5 or n26, since it is already covered by the requirement in clause 6.6.5.5.1.2. | +| 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 n1 or n65 | +| | 1920 – 1980 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n1 or n65, since it is already covered by the requirement in clause 6.6.5.5.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 n2 or n70. | +| | 1850 – 1910 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n2, since it is already covered by the requirement in clause 6.6.5.5.1.2. | +| 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 BS operating in band n3. | +| | 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.5.5.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 n66 | +| | 1710 – 1755 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.5.5.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 n5 or n26. | +| | 824 – 849 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n5 or n26, since it is already covered by the requirement in clause 6.6.5.5.1.2. | +| 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 n18. | +| | 815 – 830 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n18, since it is already covered by the requirement in clause 6.6.5.5.1.2. | +| | 830 – 845 MHz | -49 dBm | 1 MHz | | + +| | | | | | +|-----------------------------------------------------|---------------------|---------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 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 n7. | +| | 2500 – 2570 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n7, since it is already covered by the requirement in clause 6.6.5.5.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 n8 or n100. | +| | 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.5.5.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 n3. | +| | 1749.9 – 1784.9 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.5.5.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 n66 | +| | 1710 – 1770 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.5.5.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 n50, n74, n75, n92, n94 or n109. | +| | 1427.9 – 1447.9 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 or n109. | +| | 1447.9 – 1462.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n74, n75, n92 or n94 or n109. | +| 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 n12 or n85. | +| | 699 – 716 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n12 or n85, since it is already covered by the requirement in clause 6.6.5.5.1.2.
For NR BS operating in n29, it applies 1 MHz below the Band n29 downlink operating band (Note 5). | +| 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 n13. | +| | 777 – 787 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n13, since it is already covered by the requirement in clause 6.6.5.5.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 n14. | +| | 788 – 798 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n14, since it is already covered by the requirement in clause 6.6.5.5.1.2 | +| E-UTRA Band 17 | 734 – 746 MHz | -52 dBm | 1 MHz | | +| | 704 – 716 MHz | -49 dBm | 1 MHz | For NR BS operating in n29, it applies 1 MHz below the Band n29 downlink operating band (Note 5). | +| 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 n20 or n28. | +| | 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.5.5.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 n48, n77 or n78. | +| | 3410 – 3490 MHz | -49 dBm | 1 MHz | This is not applicable to BS operating in Band n77 or n78. | +| E-UTRA Band 24 or NR Band n24 | 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 or NR band n25 | 1930 – 1995 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band n2, n25 or n70. | +| | 1850 – 1915 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n25 since it is already covered by the requirement in clause 6.6.5.5.1.2. For BS operating in Band n2, it applies for 1910 MHz to 1915 MHz, while the rest is covered in clause 6.6.5.5.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 n5 or n26. | +| | 814 – 849 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n26 since it is already covered by the requirement in clause 6.6.5.5.1.2. For BS operating in Band n5, it applies for 814 MHz to 824 MHz, while the rest is covered in clause 6.6.5.5.1.2. | +| E-UTRA Band 27 | 852 – 869 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n5. | +| | 807 – 824 MHz | -49 dBm | 1 MHz | This requirement also applies to BS operating in Band n28, starting 4 MHz above the Band n28 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 BS operating in band n20, n67 or n28. | +| | 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.5.5.1.2. For BS operating in band n67, it applies for 703 MHz to 736 MHz. | +| 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 n29 or n85. | +| 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 n30. | +| | 2305 – 2315 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n30, since it is already covered by the requirement in clause 6.6.5.5.1.2. | +| 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 n31 or n72. | +| | 452.5 -457.5 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n31, since it is already covered by the requirement in clause 6.6.5.5.1.2. This requirement does not apply to BS operating in band n72. | +| 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 n50, n74, n75, n92, n94 or n109. | + +| | | | | | +|---------------------------------------------------|-----------------|---------|-------|--------------------------------------------------------------------------------------------------------------| +| 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 or NR band n34 | 2010 – 2025 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n34. | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -52 dBm | 1 MHz | | +| 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 n2 or n25. | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 – 1930 MHz | -52 dBm | 1 MHz | | +| 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 n38. | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n39. | +| UTRA TDD Band e) or E-UTRA Band 40 or NR Band n40 | 2300 – 2400MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Bands n30 or n40. | +| E-UTRA Band 41 or NR Band n41 | 2496 – 2690 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band n41 or n53. | +| E-UTRA Band 42 | 3400 – 3600 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band n48, n77 or n78. | +| E-UTRA Band 43 | 3600 – 3800 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band n48, n77 or n78. | +| E-UTRA Band 44 | 703 – 803 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band n28. | +| E-UTRA Band 45 | 1447 – 1467 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 46 or NR Band n46 | 5150 – 5925 MHz | -52 dBm | 1 MHz | This is not applicable to BS operating in Band n46, n96 or n102. | +| 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 requirement does not apply to BS operating in Band n48, n77 and n78. | +| 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, n94 or n109. | + +| | | | | | +|-------------------------------|-------------------|---------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 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, n94 or n109. | +| E-UTRA Band 53 or NR Band n53 | 2483.5 - 2495 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n41, n53 or n90. | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n54 | +| 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 n1 or n65 | +| | 1920 – 2010 MHz | -49 dBm | 1 MHz | For BS operating in Band n1, it applies for 1980 MHz to 2010 MHz, while the rest is covered in clause 6.6.5.5.1.2.
This requirement does not apply to BS operating in band n65, since it is already covered by the requirement in clause 6.6.5.5.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 n66. | +| | 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.5.5.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 n28 or n67. | +| E-UTRA Band 68 | 753 -783 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in band n28. | +| | 698-728 MHz | -49 dBm | 1 MHz | For BS operating in Band n28, this requirement applies between 698 MHz and 703 MHz, while the rest is covered in clause 6.6.5.5.1.2. | +| E-UTRA Band 69 | 2570 – 2620 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n38. | +| 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 n2, n25 or n70 | +| | 1695 – 1710 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n70, since it is already covered by the requirement in clause 6.6.5.5.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 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.5.5.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 n31 or n72. | +| | 451 – 456 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n72, since it is already covered by the requirement in clause 6.6.5.5.1.2. This requirement does not apply to BS operating in band n31. | +| 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, n75, n76, n92, n94 or n109. | +| | 1427 – 1470 MHz | -49 dBm | 1MHz | This requirement does not apply to BS operating in Band n50, n51, n74, n75, n76, n91, n92, n93, n94 or n109. | + +| | | | | | +|-------------------------------|-----------------|---------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 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, n94 or n109. | +| 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, n94 or n109. | +| NR Band n77 | 3.3 – 4.2 GHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n48, n77 or n78 | +| NR Band n78 | 3.3 – 3.8 GHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n48, n77 or n78 | +| NR Band n79 | 4.4 – 5.0 GHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n79 | +| 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.5.5.1.2. | +| 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.5.5.1.2. | +| 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.5.5.1.2. | +| 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.5.5.1.2.
For BS operating in Band n67, it applies for 703 MHz to 736 MHz. | +| 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.5.5.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 n12 or n85. | +| | 698 - 716 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n12 or n85, since it is already covered by the requirement in clause 6.6.5.5.1.2.
For NR BS operating in n29, it applies 1 MHz below the Band n29 downlink operating band (Note 5). | +| 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.5.5.1.2. | +| NR Band n89 | 824 – 849 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n5, since it is already covered by the requirement in clause 6.6.5.5.1.2. | +| NR Band n91 | 1427 – 1432 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n75, n76 or n109. | +| | 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.5.5.1.2. | +| 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 or n109. | +| | 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.5.5.1.2. | +| NR Band n93 | 1427 – 1432 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n50, n51, n75, n76 or n109. | +| | 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.5.5.1.2. | + +| | | | | | +|---------------------------------|---------------------|---------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 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 or n109. | +| | 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.5.5.1.2. | +| NR Band n95 | 2010 – 2025 MHz | -52 dBm | 1 MHz | | +| NR Band n96 | 5925 – 7125 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n46, n96, n102 or n104. | +| 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 n24, since it is already covered by the requirement in clause 6.6.5.5.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 n8 or n100. | +| | 874.4 – 880 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n100, since it is already covered by the requirement in clause 6.6.5.5.1.2. | +| NR Band n101 | 1900 – 1910 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n101. | +| NR Band n102 | 5925 – 6425 MHz | -52 dBm | 1 MHz | This requirement does not apply to BS operating in Band n46, n96, n102 or n104. | +| 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 | This requirement does not apply to BS operating in Band n96, n102 or n104 | +| 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 band n105, since it is already covered by the requirement in clause 6.6.5.5.1.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 n106 | +| | 896 – 901 MHz | -49 dBm | 1 MHz | This requirement does not apply to BS operating in band n106, since it is already covered by the requirement in clause 6.6.5.5.1.2.
This requirement does not apply to BS operating in Band n5 or n26. | +| NR Band n109 | 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, n94 or n109. | +| | 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, n94 or n109. | + +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 n28, the co-existence requirements in table 6.6.5.5.1.3-1do not apply for the $\Delta f_{\text{OBUE}}$ frequency range immediately outside the downlink *operating band* (see TS 38.104 [2], table 5.2-1). Emission limits for this excluded frequency range may be covered by local or regional requirements. + +NOTE 2: Table 6.6.5.5.1.3-1 assumes that two *operating bands*, where the frequency ranges in TS 38.104 [2], table 5.2-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: 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 4: For Band n28 BS, specific solutions may be required to fulfil the spurious emissions limits for BS for co-existence with E-UTRA Band 27 UL *operating band*. + +NOTE 5: For NR Band n29 BS, specific solutions may be required to fulfil the spurious emissions limits for NR 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 or NR Band n85 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*. $\Delta f_{\text{OBUE}}$ is defined in clause 6.6.1. + +The *basic limits* for this requirement is: + +**Table 6.6.5.5.1.3-2: BS spurious emissions *basic limits* for BS for co-existence with PHS** + +| Frequency range | Basic limit | Measurement bandwidth | Note | +|---------------------|-------------|-----------------------|-------------------------------------------------------------------------------| +| 1884.5 – 1915.7 MHz | -41 dBm | 300 kHz | Applicable when co-existence with PHS system operating in 1884.5 - 1915.7 MHz | + +**Table 6.6.5.5.1.3-3: Void** + +In certain regions, the following requirement may apply to BS operating in Band n50 and n75 within 1432-1452 MHz, and in Band n51 and Band n76. The *basic limits* are specified in table 6.6.5.5.1.3-4. 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*. + +**Table 6.6.5.5.1.3-4: Additional operating band unwanted emission *basic limits* for BS operating in Band n50 and n75 within 1432-1452 MHz, and in Band 51 and 76** + +| Filter centre frequency, 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 NR Band n50 within 1492-1517 MHz. The maximum level of emissions, measured on centre frequencies $F_{\text{filter}}$ with filter bandwidth according to table 6.6.5.5.1.3-5, shall be defined according to the *basic limits* $P_{\text{EM,n50,a}}$ and $P_{\text{EM,n50,b}}$ declared by the manufacturer. + +**Table 6.6.5.5.1.3-5: Operating band n50, n74 and n75 declared emission above 1518 MHz** + +| Filter centre frequency, $F_{\text{filter}}$ | Declared emission basic limit (dBm) | Measurement bandwidth | +|---------------------------------------------------------------------|--------------------------------------------|-----------------------| +| $1518.5 \text{ MHz} \leq F_{\text{filter}} \leq 1519.5 \text{ MHz}$ | $P_{\text{EM,n50,a}}$ | 1 MHz | +| $1520.5 \text{ MHz} \leq F_{\text{filter}} \leq 1558.5 \text{ MHz}$ | $P_{\text{EM,n50,b}}$ | 1 MHz | + +NOTE: The regional requirement, included in ECC/DEC/(17)06 [14], 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 38.104 [2] annex E. + +In certain regions, the following requirement shall be applied to BS operating in Band n13 and n14 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 power of any spurious emission shall not exceed: + +**Table 6.6.5.5.1.3-6: BS Spurious emissions limits for protection of 700 MHz public safety operations** + +| Operating Band | Frequency range | Maximum Level | Measurement Bandwidth | +|----------------|-----------------|---------------|-----------------------| +| n13 | 763 - 775 MHz | -46 dBm | 6.25 kHz | +| n13 | 793 - 805 MHz | -46 dBm | 6.25 kHz | +| n14 | 769 – 775 MHz | -46 dBm | 6.25 kHz | +| n14 | 799 – 805 MHz | -46 dBm | 6.25 kHz | + +The following requirement may apply to NR BS operating in Band n30 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.5.5.1.3-7: Additional NR BS Spurious emissions limits for Band n30** + +| Frequency range | Basic limit | Measurement bandwidth | +|-------------------|-------------|-----------------------| +| 2200 – 2345 MHz | -45 dBm | 1 MHz | +| 2362.5 – 2365 MHz | -25 dBm | | +| 2365 – 2367.5 MHz | -40 dBm | | +| 2367.5 – 2370 MHz | -42 dBm | | +| 2370 – 2395 MHz | -45 dBm | | + +The following requirement may apply to BS operating in Band n48 in certain regions. The power of any spurious emission shall not exceed: + +**Table 6.6.5.2.3-8: Additional BS Spurious emissions limits for Band n48** + +| Frequency range | Maximum Level | Measurement Bandwidth (NOTE) | Note | +|----------------------------------------|---------------|------------------------------|-------------------------------------------------| +| 3530MHz – 3720MHz | -25dBm | 1 MHz | Applicable 10MHz from the assigned channel edge | +| 3100MHz – 3530MHz
3720MHz – 4200MHz | -40dBm | 1 MHz | | + +NOTE: 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. + +The following requirement shall be applied to BS operating in Band n26 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 power of any spurious emission shall not exceed: + +**Table 6.6.5.2.3-9: BS Spurious emissions limits for protection of 800 MHz public safety operations** + +| Operating Band | Frequency range | Maximum Level | Measurement Bandwidth | Note | +|----------------|-----------------|---------------|-----------------------|--------------------------------------------------------| +| n26 | 851 - 859 MHz | -13 dBm | 100 kHz | Applicable for offsets > 37.5kHz from the channel edge | + +The following requirement may apply to BS for Band n41 and n90 operation in Japan. 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. + +The power of any spurious emission shall not exceed: + +**Table 6.6.5.1.3-10: Additional BS Spurious emissions limits for Band n41 and n90** + +| Frequency range | Basic limit | Measurement Bandwidth | +|-----------------------------------------------------------------------------|-------------|-----------------------| +| 2505 MHz – 2535 MHz | -42 dBm | 1 MHz | +| NOTE: This requirement applies for carriers allocated within 2545-2645 MHz. | | | + +The following requirement may apply to BS operating in 3.45-3.55 GHz in Band n77 in certain regions. Emissions shall not exceed the maximum levels specified in table 6.6.5.1.3-11. + +**Table 6.6.5.1.3-11: Additional BS spurious emissions limits for Band n77** + +| Channel bandwidth [MHz] | Frequency range [MHz] | Filter centre frequency, $F_{filter}$ [MHz] | Minimum requirement [dBm] | Measurement bandwidth [MHz] | +|-------------------------|----------------------------|------------------------------------------------------------------------|---------------------------|-----------------------------| +| All | 3430 – 3440
3560 – 3570 | $3430.5 \leq F_{filter} < 3439.5$
$3560.5 \leq F_{filter} < 3569.5$ | -25 | 1 | +| All | $\leq 3430$
$> 3570$ | $F_{filter} < 3429.5$
$3570.5 \leq F_{filter}$ | -40 | 1 | + +NOTE: 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. + +The following requirement shall apply to BS operating in Band n101 in CEPT countries. The power of any spurious emission shall not exceed: + +**Table 6.6.5.5.1.3-12: Additional BS Spurious emissions limits for Band n101** + +| Frequency range | Maximum Level | Measurement Bandwidth | Note | +|---------------------|---------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| 1920 MHz – 1980 MHz | -57 dBm | 5 MHz | This limit is derived from ECC Decision (20)02 [25] assuming a 18 dBi maximum antenna gain and 4dB losses, and assuming one antenna connector. | + +The following requirement shall apply to BS operating in Band n100 in CEPT countries. The power of any spurious emission shall not exceed: + +**Table 6.6.5.5.1.3-13: Additional BS Spurious emissions limits for Band n100** + +| Frequency range | Maximum Level | Measurement Bandwidth | Note | +|-------------------|---------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| 880 MHz – 915 MHz | -62 dBm | 5 MHz | This limit is derived from ECC Decision (20)02 [25] assuming a 17 dBi maximum antenna gain and 4dB losses, and assuming one antenna connector. | + +The following requirement may also apply to BS operating in Band n54 in certain regions. The level of emissions in the 1541 – 1650 MHz band, measured in measurement bandwidth according to Table 6.6.5.5.1.3-14 shall not exceed the maximum emission levels $P_{EM,n54,a}$ , $P_{EM,n54,b}$ , $P_{EM,n54,c}$ , $P_{EM,n54,d}$ , $P_{EM,n54,e}$ and $P_{EM,n54,f}$ declared by the manufacturer. + +**Table 6.6.5.5.1.3-14: Declared Band n54 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) | +|----------------|-----------------|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| +| n54 | 1541 - 1559 MHz | $P_{EM,n54,a}$ | | $P_{EM,n54,f}$ | +| | 1559 - 1610 MHz | $P_{EM,n54,b}$ | $P_{EM,n54,d}$ | | +| | 1610 - 1650 MHz | $P_{EM,n54,c}$ | $P_{EM,n54,e}$ | | + +Note: The regional requirements 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 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 specified in attachment to the FCC reference document, 0007135419. + +#### 6.6.5.5.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 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 limits* are in table 6.6.5.5.1.4-1 for a BS where requirements for co-location with a BS type listed in the first column apply, depending on the declared BS class (D.2). For a *multi-band connector*, the exclusions and conditions in the Note column of table 6.6.5.5.1.4-1 shall apply for each supported *operating band*. + +**Table 6.6.5.5.1.4-1: BS spurious emissions *basic limits* for BS co-located with another BS** + +| Type of co-located BS | Frequency range for co-location requirement | Basic limit | | | Measurement bandwidth | Note | +|-----------------------------------------------------|---------------------------------------------|-------------|---------|---------|-----------------------|-------------------------------------------------------------------------------------| +| | | WA BS | MR BS | LA BS | | | +| GSM900 | 876-915 MHz | -98 dBm | -91 dBm | -70 dBm | 100 kHz | | +| DCS1800 | 1710 – 1785 MHz | -98 dBm | -91 dBm | -80 dBm | 100 kHz | | +| PCS1900 | 1850 – 1910 MHz | -98 dBm | -91 dBm | -80 dBm | 100 kHz | | +| GSM850 or CDMA850 | 824 – 849 MHz | -98 dBm | -91 dBm | -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 n50, n75, n91, n92, n93, n94 or n109 | +| 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 n50, n75, n92, n94 or n109 | +| 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 n48, n77, n78 or n109 | +| 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 | | +| E-UTRA Band 30 or NR Band n30 | 2305 – 2315 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| 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 | | +| 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 n34 | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| 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 n2 or band n25 | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 – 1930 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| 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 n38. | +| 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 n39 | +| 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 Bands n30 or n40. | +| E-UTRA Band 41 or NR Band n41 | 2496 – 2690 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band n41 or n53 | +| E-UTRA Band 42 | 3400 – 3600 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not | + +| | | | | | | | +|--|--|-----|-----|-----|--|----------------------------------------------------| +| | | dBm | dBm | dBm | | applicable to BS operating in Band n48, n77 or n78 | +|--|--|-----|-----|-----|--|----------------------------------------------------| + +| | | | | | | | +|-------------------------------|-------------------|---------|---------|---------|---------|------------------------------------------------------------------------------------------| +| E-UTRA Band 43 | 3600 – 3800 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band n48, n77 or n78 | +| E-UTRA Band 44 | 703 – 803 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band n28 | +| E-UTRA Band 45 | 1447 – 1467 MHz | -96 dBm | -91 dBm | -88 dBm | 100 kHz | | +| E-UTRA Band 46 or NR Band n46 | 5150 – 5925 MHz | N/A | -91 dBm | -88 dBm | 100 kHz | This is not applicable to BS operating in Band n46, n96 or n102 | +| 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 n48, n77 or n78 | +| 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, n94 or n109 | +| 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 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 n41, n53 or n90 | +| 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 n54 | +| 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 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 n48, n77 or n78 | +| 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 n48, n77 or n78 | +| 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 | | +| 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 | This is not applicable to BS operating in Band n46, n96, n102 or n104 | +| 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 | -90 dBm | -87 dBm | 100 kHz | This is not applicable to BS operating in Band n46, n96, n102 or n104 | + +| | | | | | | | +|---------------------------------|-----------------|---------|---------|---------|---------|----------------------------------------------------------------------------| +| 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 | This requirement does not apply to BS operating in Band n96, n102 or n104. | +| 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 | | + +NOTE 1: As defined in the scope for spurious emissions in this clause, the co-location requirements in table 6.6.5.5.1.4-1 do not apply for the frequency range extending $\Delta f_{\text{OBUE}}$ immediately outside the BS transmit frequency range of a downlink *operating band* (see TS 38.104 [2] table 5.2-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 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 [15]. + +NOTE 2: Table 6.6.5.5.1.4-1 assumes that two *operating bands*, where the corresponding BS transmit and receive frequency ranges in TS 38.104 [2] table 5.2-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. + +#### 6.6.5.5.2 (void) + +#### 6.6.5.5.3 BS type 1-C + +The Tx spurious emissions for *BS type 1-C* for each *antenna connector* shall not exceed the *basic limits* specified in clause 6.6.5.5.1. + +For Band n41 and n90 operation in Japan, the sum of the spurious emissions over all *antenna connectors* for *BS type 1-C* shall not exceed the *basic limits* defined in clause 6.6.5.5.1. + +#### 6.6.5.5.4 BS type 1-H + +The Tx spurious emissions requirements for *BS type 1-H* are that for each *TAB connector TX min cell group* and each applicable *basic limit* in clause 6.6.5.5.1, the power summation emissions at the *TAB connectors* of the *TAB connector TX min 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. + +NOTE: Conformance to the *BS type 1-H* 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 limit as defined in this clause for the respective frequency span. + +Or + +2) The unwanted emissions power at each *TAB connector* shall be less than or equal to the *BS type 1-H* limit as defined in this clause 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 Definition and applicability + +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 antenna, RDN and antenna array. The requirement shall apply during the transmitter ON period and the *transmitter transient period*. + +For *BS type 1-C*, the transmitter intermodulation level is the power of the intermodulation products when an interfering signal is injected into the *antenna connector*. + +For *BS type 1-H*, the transmitter intermodulation level is the power of the intermodulation products when an interfering signal is injected into the *TAB connector*. + +For *BS type 1-H*, 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 *BS type 1-H*. + +For *BS type 1-H*, the co-location transmitter intermodulation requirement is considered sufficient if the interference signal for the co-location requirement is higher than the declared interference signal for intra-system transmitter (D.30) intermodulation requirement. + +### 6.7.2 Minimum requirement + +The minimum requirement applies per *single-band connector*, or per *multi-band connector* supporting transmission in the *operating band*. + +The minimum requirement for *BS type 1-C* is defined in TS 38.104 [2], clause 6.7.2. + +The minimum requirement for *BS type 1-H* is defined in TS 38.104 [2], clause 6.7.3. + +### 6.7.3 Test purpose + +The test purpose is to verify the ability of the transmitter units associated with the *single-band connectors* or *multi-band 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 annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +*Base Station RF Bandwidth* positions to be tested for multi-carrier and/or CA: + +- $M_{RFBW}$ in single-band operation; see clause 4.9.1. +- $B_{RFBW\_T}{}_{RFBW}$ and $B'_{RFBW\_T}{}_{RFBW}$ in multi-band operation, see clause 4.9.1. + +NOTE: When testing in M (or $M_{RFBW}$ ), if the interferer is fully or partially located outside the supported frequency range, then the test shall be done instead in B (or $B_{RFBW}$ ) and T (or $T_{RFBW}$ ), and only with the interferer located inside the supported frequency range. + +## 6.7.4.2 Procedure + +For *BS type 1-H* where there may be multiple *TAB connectors*, they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex D.3.1. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect the *single-band connector* or *multi-band connector* under test to measurement equipment as shown in annex D.1.2 for *BS type 1-C* and in annex D.3.2 for *BS type 1-H*. All 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) For a connectors declared to be capable of single carrier operation only (D.16), set the representative connectors under test to transmit according to the applicable test configuration in clause 4.8 at *rated carrier output power* $P_{\text{rated,c,AC}}$ for *BS type 1-C* and $P_{\text{rated,c,TABC}}$ for *BS type 1-H* (D.21). Channel set-up shall be according to NR-FR1-TM 1.1. + +For a connector under test declared to be capable of multi-carrier and/or CA operation (D.15-D.16) set the connector under test to transmit on all carriers configured using the applicable test configuration and corresponding power setting specified in clauses 4.7 and 4.8 using the corresponding test models or set of physical channels in clause 4.9.2. + +For a BS declared to be capable of NB-IoT operation in NR in-band (D.41), test shall be performed using N-TM according to clause 4.9.2.2.9. + +- 4) Generate the interfering signal according to NR-FR1-TM-1.1, as defined in clause 4.9.2, with the minimum channel bandwidth ( $BW_{\text{Channel}}$ ) with 15 kHz SCS of the band defined in clause 5.3.5 of TS 38.104 [2] and a centre frequency offset from the lower/upper edge of the wanted signal or edge of sub-block inside a sub-block gap , for $n = 1, 2$ and $3$ , 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 ATT attenuator (as in the test setup in annex D.1.2 for *BS type 1-C* and in annex D.3.2 for *BS type 1-H*) so that level of the interfering signal is as defined in clause 6.7.5. +- 6) Perform the unwanted emission tests specified in clauses 6.6.3 and 6.6.4 for all third and fifth order intermodulation products which appear in the frequency ranges defined in clauses 6.6.3 and 6.6.4. The width of the intermodulation products shall be taken into account. +- 7) Perform the transmitter spurious emissions test as specified in clause 6.6.5, for all third and fifth order intermodulation products which appear in the frequency ranges defined in clause 6.6.5. 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 step 4. +- 10) Repeat the test for the remaining test signals defined in clause 6.7.5 for additional requirements and for *BS type 1-H* intra-system requirements. + +In addition, for *multi-band connectors*, the following steps shall apply: + +- 11) 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*. + +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 wanted signal RF bandwidth or channel bandwidth in case of single carrier, or sub-block bandwidth and $BW_{F2}$ represents the interfering signal channel bandwidth. + +## 6.7.5 Test requirements + +### 6.7.5.1 BS type 1-C + +#### 6.7.5.1.1 Co-location minimum requirements + +For *BS type 1-C*, the wanted signal and interfering signal centre frequency is specified in table 6.7.5.1.1-1, where interfering signal level is *rated total output power* ( $P_{\text{rated,t,AC}}$ ) at *antenna connector* in the *operating band* – 30 dB. + +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 a 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 a *multi-band connector*, the requirement shall apply relative to the Base Station RF Bandwidth edges of each supported operating band. In case the Inter RF Bandwidth gap is less than $3 * BW_{\text{Channel}}$ MHz (where $BW_{\text{Channel}}$ is the minimal *BS channel bandwidth* of the band), the requirement in the gap shall apply only for interfering signal offsets where the interfering signal falls completely within the Inter RF Bandwidth gap. + +The transmitter intermodulation level shall not exceed the unwanted emission limits in clauses 6.6.3, 6.6.4 and 6.6.5 in the presence of an NR interfering signal according to table 6.7.5.1.1-1. + +**Table 6.7.5.1.1-1: Interfering and wanted signals for the co-location transmitter intermodulation requirement** + +| Parameter | Value | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal type | NR single carrier, or multi-carrier, or multiple intra-band contiguously or non-contiguously aggregated carriers, with NB-IoT operation in NR in-band if supported. | +| Interfering signal type | NR signal, the minimum BS channel bandwidth ( $BW_{\text{Channel}}$ ) with 15 kHz SCS of the band defined in clause 5.3.5 of TS 38.104 [2]. | +| Interfering signal level | Rated total output power ( $P_{\text{rated,t,AC}}$ ) in the operating band – 30 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 | , for n=1, 2 and 3 | +| NOTE 1: Interfering signal positions that are partially or completely outside of any downlink operating band of the BS 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: In Japan, NOTE 1 is not applied in Band n77, n78, n79. | | + +#### 6.7.5.1.2 Additional requirements + +For Band n41 and n90 operation in Japan, the sum of transmitter intermodulation level over all *antenna connectors* shall not exceed the unwanted emission limits in clauses 6.6.3, 6.6.4 and 6.6.5 in the presence of an NR interfering signal according to table 6.7.5.1.2-1. + +**Table 6.7.5.1.2-1 Interfering and wanted signals for the additional transmitter intermodulation requirement for Band n41 and n90** + +| Parameter | Value | +|---------------------------------------------------------------------------------------------------------------|--------------------------------------------------------| +| Wanted signal | NR single carrier (NOTE) | +| Interfering signal type | NR signal of 10 MHz channel bandwidth | +| Interfering signal level | Rated total output power in the operating band – 30 dB | +| Interfering signal centre frequency offset from the lower/upper carrier centre frequency of the wanted signal | ± 5 MHz
± 15 MHz
± 25 MHz | +| NOTE: This requirement applies for NR carriers allocated within 2545-2645 MHz. | | + +For Band n26 and n28 operation in Japan, when the narrowest channel bandwidth supported by the BS is 5MHz or wider, the transmitter intermodulation level shall not exceed the unwanted emission limits in clauses 6.6.3, 6.6.4 and 6.6.5 in the presence of an NR interfering signal according to table 6.7.5.1.2-2. + +**Table 6.7.5.1.2-2 Interfering and wanted signals for the additional transmitter intermodulation requirement for Band n26 and n28 when the narrowest channel bandwidth supported by the BS is 5MHz or wider** + +| Parameter | Value | +|-------------------------------------------------------------------------------------------|--------------------------------------------------------| +| Wanted signal | NR single carrier | +| Interfering signal type | NR signal of 5 MHz channel bandwidth | +| Interfering signal level | Rated total output power in the operating band – 30 dB | +| Interfering signal centre frequency offset from the lower/upper edge of the wanted signal | ± 2.5 MHz
± 7.5 MHz
± 12.5 MHz | + +## 6.7.5.2 BS type 1-H + +### 6.7.5.2.1 Co-location minimum requirements + +The transmitter intermodulation level shall not exceed the unwanted emission limits in clauses 6.6.3, 6.6.4 and 6.6.5 in the presence of an NR interfering signal according to table 6.7.5.2.1-1. + +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 *multi-band connector*, the requirement shall apply relative to the *Base Station RF Bandwidth edges* of each operating band. In case the inter *RF Bandwidth gap* is less than $3 \cdot BW_{\text{Channel}}$ MHz (where $BW_{\text{Channel}}$ is the minimal *BS channel bandwidth* of the band), the requirement in the gap shall apply only for interfering signal offsets where the interfering signal falls completely within the inter *RF Bandwidth gap*. + +**Table 6.7.5.2.1-1: Interfering and wanted signals for the co-location transmitter intermodulation requirement** + +| Parameter | Value | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal type | NR single carrier, or multi-carrier, or multiple intra-band contiguously or non-contiguously aggregated carriers | +| Interfering signal type | NR signal, the minimum BS channel bandwidth ( $BW_{\text{Channel}}$ ) with 15 kHz SCS of the band defined in clause 5.3.5 of TS 38.104 [2]. | +| Interfering signal level | Rated total output power per TAB connector ( $P_{\text{rated,T,TABC}}$ ) in the operating band – 30 dB | +| Interfering signal centre frequency offset from the lower/upper edge of the wanted signal or edge of sub-block inside a gap | , for n=1, 2 and 3 | +| 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. | | +| NOTE 2: In Japan, NOTE 1 is not applied in Band n77, n78, n79. | | + +### 6.7.5.2.2 Intra-system minimum requirements + +The transmitter intermodulation level shall not exceed the unwanted emission limits in clauses 6.6.3 and 6.6.4 in the presence of an NR interfering signal according to table 6.7.5.2.2-1. + +**Table 6.7.5.2.2-1: Interfering and wanted signals for intra-system transmitter intermodulation requirement** + +| Parameter | Value | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------| +| Wanted signal type | NR signal | +| Interfering signal type | NR signal of the same BS channel bandwidth and SCS as the wanted signal (Note 1). | +| Interfering signal level | Power level declared by the BS manufacturer in D.29 (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.5.2.3 Additional requirements + +For Band n41 operation in Japan, the transmitter intermodulation level shall not exceed the unwanted emission limits in clauses 6.6.3, 6.6.4 and 6.6.5 in the presence of an NR interfering signal according to table 6.7.5.2.3-1. + +**Table 6.7.5.2.3-1 Interfering and wanted signals for the additional transmitter intermodulation requirement for Band n41 and n90** + +| Parameter | Value | +|---------------------------------------------------------------------------------------------------------------|--------------------------------------------------------| +| Wanted signal | NR single carrier (NOTE) | +| Interfering signal type | NR signal of 10 MHz channel bandwidth | +| Interfering signal level | Rated total output power in the operating band – 30 dB | +| Interfering signal centre frequency offset from the lower/upper carrier centre frequency of the wanted signal | $\pm 5$ MHz
$\pm 15$ MHz
$\pm 25$ MHz | +| NOTE: This requirement applies for NR carriers allocated within 2545-2645 MHz. | | + +For Band n26 and n28 operation in Japan, when the narrowest channel bandwidth supported by the BS is 5 MHz or wider, the transmitter intermodulation level shall not exceed the unwanted emission limits in clauses 6.6.3, 6.6.4 and 6.6.5 in the presence of an NR interfering signal according to table 6.7.5.2.3-2. + +**Table 6.7.5.2.3-2 Interfering and wanted signals for the additional transmitter intermodulation requirement for Band n26 and n28 when the narrowest channel bandwidth supported by the BS is 5MHz or wider** + +| Parameter | Value | +|----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| +| Wanted signal | NR single carrier | +| Interfering signal type | NR signal of 5 MHz channel bandwidth | +| Interfering signal level | Rated total output power per TAB connector ( $P_{\text{rated,t,TABC}}$ ) in the operating band – 30 dB | +| Interfering signal centre frequency offset from the lower/upper edge of the wanted signal or | $\pm 2.5$ MHz
$\pm 7.5$ MHz
$\pm 12.5$ MHz | + +## 7 Conducted receiver characteristics + +### 7.1 General + +Conducted receiver characteristics are specified at the *antenna connector* for *BS type 1-C* and at the *TAB connector* for *BS type 1-H*, with full complement of transceivers for the configuration in normal operating condition. + +Unless otherwise stated, the following arrangements apply for conducted receiver characteristics requirements in clause 7: + +- Requirements apply during the BS receive period. +- Requirements shall be met for any transmitter setting. +- For FDD operation the requirements shall be met with the transmitter unit(s) ON. +- Throughput requirements defined for the conducted receiver characteristics do not assume HARQ retransmissions. +- When BS is configured to receive multiple carriers, all the throughput requirements are applicable for each received carrier. +- For ACS, blocking and intermodulation characteristics, the negative offsets of the interfering signal apply relative to the lower *Base Station RF Bandwidth* edge or *sub-block* edge inside a *sub-block gap*, and the positive offsets of the interfering signal apply relative to the upper *Base Station RF Bandwidth* edge or *sub-block* edge inside a *sub-block gap*. +- Requirements shall also apply for BS supporting NB-IoT operation in NR in-band. The corresponding NB-IoT requirements are specified in clause 7 of TS 36.141 [24]. + +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*. + +For *BS type 1-H* if a number of *TAB connectors* have been declared equivalent (D.32), only a representative one is necessary to demonstrate conformance. + +In clause 7.6.5.3, if representative *TAB connectors* are used then per connector criteria (option 2) shall be applied. + +For *BS type 1-H* there is no requirement specified for band n46, n100, n101 and n102. + +## 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 *antenna connector* for *BS type 1-C* or *TAB connector* for *BS type 1-H* at which a throughput requirement shall be met for a specified reference measurement channel. + +## 7.2.2 Minimum requirement + +The minimum requirement for *BS type 1-C* is in TS 38.104 [2], clause 7.2.2. + +The minimum requirement for *BS type 1-H* is in TS 38.104 [2], clause 7.2.2. + +## 7.2.3 Test purpose + +To verify that for the *BS type 1-C* receiver and each *BS type 1-H TAB connector* at the reference sensitivity level the throughput requirement 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 annex B.2. +- Extreme, see annexes B.3 and B.5. + +RF channels to be tested for single carrier: B, M and T; see clause 4.9.1. + +Under extreme test environment, the test shall be performed on each of B, M and T under extreme power supply conditions as defined in annex B.5. + +NOTE: Tests under extreme power supply conditions also test extreme temperatures. + +### 7.2.4.2 Procedure + +The minimum requirement is applied to all connectors under test. + +For *BS type 1-H* the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested; see clause 7.1. + +- 1) Connect the connector under test to measurement equipment as shown in annex D.2.1 for *BS type 1-C* and in annex D.4.1 for *BS type 1-H*. +- 2) For FDD operation, set the BS to transmit a signal using the applicable test configuration and corresponding power setting specified in clauses 4.7 and 4.8 using the corresponding test models or set of physical channels in clause 4.9.2, for *BS type 1-C* set the *antenna connector* to the manufacturers declared *rated carrier output power* ( $P_{\text{rated,c,AC}}$ or $P_{\text{rated,c,TABC}}$ , D.21). +- 3) Start the signal generator for the wanted signal to transmit the Fixed Reference Channels for reference sensitivity according to annex A.1, as well as annex A.14 of TS 36.141 [24] for a BS declared to be capable of NB-IoT operation in NR in-band (D.41). +- 4) Set the signal generator for the wanted signal power as specified in clause 7.2.5. +- 5) Measure the throughput according to annex A.1, as well as annex A.14 of TS 36.141 [24] for a BS declared to be capable of NB-IoT operation in NR in-band (D.41). + +In addition, for a *multi-band connector*, the following steps shall apply: + +- 6) For *multi-band connector* 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 + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.1 with parameters specified in table 7.2.5-1 for Wide Area BS, in table 7.2.5-2 for Medium Range BS and in table 7.2.5-3 for Local Area BS in any operating band except for band n46, n96, n102, and n104. + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.2 with parameters specified in table 7.2.5-2a for Medium Range BS and in table 7.3.5-3a for Local Area BS, for band n46. + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.2 with parameters specified in table 7.2.5-2b for Medium Range BS and in table 7.2.5-3b for Local Area BS, for band n96 and n102. + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.1 with parameters specified in table 7.2.5-1a for Wide Area BS, in table 7.2.5-2c for Medium Range BS and in table 7.2.5-3c for Local Area BS for band n104. + +The reference sensitivity level requirements for NB-IoT are specified in clause 7.2.5 of TS 36.141 [24]. + +**Table 7.2.5-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 (Note 1) | -101 | -100.7 | -100.5 | +| | | G-FR1-A1-10 (Note 3) | -101 (Note 2) | -100.7 (Note 2) | -100.5 (Note 2) | +| 10, 15 | 30 | G-FR1-A1-2 (Note 1) | -101.1 | -100.8 | -100.6 | +| 10, 15 | 60 | G-FR1-A1-3 (Note 1) | -98.2 | -97.9 | -97.7 | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 (Note 1) | -94.6 | -94.3 | -94.1 | +| | | G-FR1-A1-11 (Note 4) | -94.6 (Note 2) | -94.3 (Note 2) | -94.1 (Note 2) | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 (Note 1) | -94.9 | -94.6 | -94.4 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 (Note 1) | -95 | -94.7 | -94.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 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 2: The requirements apply to BS that supports NB-IoT operation in NR in-band. + +NOTE 3: $P_{\text{REFSENS}}$ is the power level of a single instance of the reference measurement channel. This requirement shall be met for a single instance of G-FR1-A1-10 mapped to the 24 NR resource blocks adjacent to the NB-IoT PRB, and for each consecutive application of a single instance of G-FR1-A1-1 mapped to disjoint frequency ranges with a width of 25 resource blocks each. + +NOTE 4: $P_{\text{REFSENS}}$ is the power level of a single instance of the reference measurement channel. This requirement shall be met for a single instance of G-FR1-A1-11 mapped to the 105 NR resource blocks adjacent to the NB-IoT PRB, and for each consecutive application of a single instance of G-FR1-A1-4 mapped to disjoint frequency ranges with a width of 106 resource blocks each. + +**Table 7.2.5-1a: NR Wide Area BS reference sensitivity levels for band n104** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | Reference sensitivity power level, P_{\text{REFSENS}} (dBm) (Note 6) | +|-------------------------------------|----------------------------------|--------------------------------------|------------------------------------------------------------------------------------------| +| 20, 30, 40, 50 | 15 | G-FR1-A1-4 (Note 1) | -92.8 | +| 20, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 (Note 1) | -93.1 | +| 20, 30, 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 (Note 1) | -93.2 | + +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 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-2: NR Medium Range BS reference sensitivity levels** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel (Note 5) | 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 (Note 1) | -96 | -95.7 | -95.5 | +| | | G-FR1-A1-10 (Note 3) | -96 (Note 2) | -95.7 (Note 2) | -95.5 (Note 2) | +| 10, 15 | 30 | G-FR1-A1-2 (Note 1) | -96.1 | -95.8 | -95.6 | +| 10, 15 | 60 | G-FR1-A1-3 (Note 1) | -93.2 | -92.9 | -92.7 | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 (Note 1) | -89.6 | -89.3 | -89.1 | +| | | G-FR1-A1-11 (Note 4) | -89.6 (Note 2) | -89.3 (Note 2) | -89.1 (Note 2) | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 (Note 1) | -89.9 | -89.6 | -89.4 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 (Note 1) | -90 | -89.7 | -89.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 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 2: The requirements apply to BS that supports NB-IoT operation in NR in-band. + +NOTE 3: $P_{\text{REFSENS}}$ is the power level of a single instance of the reference measurement channel. This requirement shall be met for a single instance of G-FR1-A1-10 mapped to the 24 NR resource blocks adjacent to the NB-IoT PRB, and for each consecutive application of a single instance of G-FR1-A1-1 mapped to disjoint frequency ranges with a width of 25 resource blocks each. + +NOTE 4: $P_{\text{REFSENS}}$ is the power level of a single instance of the reference measurement channel. This requirement shall be met for a single instance of G-FR1-A1-11 mapped to the 105 NR resource blocks adjacent to the NB-IoT PRB, and for each consecutive application of a single instance of G-FR1-A1-4 mapped to disjoint frequency ranges with a width of 106 resource blocks each. + +NOTE 5: These reference measurement channels are not applied for band n46, n96 and n102. + +**Table 7.2.5-2a: NR Medium Range BS reference sensitivity levels for band n46** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | Reference sensitivity power level, P_{REFSENS} (dBm) | +|-----------------------------------|---------------------------|-------------------------------|--------------------------------------------------------------------------| +| 10 | 15 | G-FR1-A1-12 (Note 2) | -101.5 | +| | 30 | G-FR1-A1-13 (Note 2) | -99.2 | +| | 60 | G-FR1-A1-3 (Note 1, 3) | -92.4 | +| 20 | 15 | G-FR1-A1-14 (Note 2) | -98.6 | +| | 30 | G-FR1-A1-15 (Note 2) | -95.6 | +| | 60 | G-FR1-A1-6 (Note 1, 3) | -89.2 | +| 40 | 15 | G-FR1-A1-16 (Note 2) | -95.5 | +| | 30 | G-FR1-A1-17 (Note 2) | -92.5 | +| | 60 | G-FR1-A1-6 (Note 1, 3) | -89.2 | +| 60 | 30 | G-FR1-A1-18 (Note 2) | -90.9 | +| | 60 | G-FR1-A1-6 (Note 1, 3) | -89.2 | +| 80 | 30 | G-FR1-A1-19 (Note 2) | -89.6 | +| | 60 | G-FR1-A1-6 (Note 1, 3) | -89.2 | + +NOTE 1: $P_{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 2: $P_{REFSENS}$ is the power level of a single instance of the reference measurement channel. This requirement shall be met for each interleaved 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 3: For 60kHz SCS reference measurement channel is reused from Table 7.2.5-2. + +**Table 7.2.5-2b: NR Medium Range BS reference sensitivity levels for band n96 and n102** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | Reference sensitivity power level, P_{REFSENS} (dBm) | +|-----------------------------------|---------------------------|-------------------------------|--------------------------------------------------------------------------| +| 20 | 15 | G-FR1-A1-14 (Note 2) | -97.6 | +| | 30 | G-FR1-A1-15 (Note 2) | -94.6 | +| | 60 | G-FR1-A1-6 (Note 1, 3) | -88.2 | +| 40 | 15 | G-FR1-A1-16 (Note 2) | -94.5 | +| | 30 | G-FR1-A1-17 (Note 2) | -91.5 | +| | 60 | G-FR1-A1-6 (Note 1, 3) | -88.2 | +| 60 | 30 | G-FR1-A1-18 (Note 2) | -89.9 | +| | 60 | G-FR1-A1-6 (Note 1, 3) | -88.2 | +| 80 | 30 | G-FR1-A1-19 (Note 2) | -88.6 | +| | 60 | G-FR1-A1-6 (Note 1, 3) | -88.2 | + +NOTE 1: $P_{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 2: $P_{REFSENS}$ is the power level of a single instance of the reference measurement channel. This requirement shall be met for each interleaved 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 3: For 60kHz SCS reference measurement channel is reused from Table 7.2.5-2. + +**Table 7.2.5-2c: NR Medium Range BS reference sensitivity levels for band n104** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel (Note 5) | Reference sensitivity power level, P_{\text{REFSENS}} (dBm) | +|-------------------------------------|----------------------------------|-----------------------------------------------|---------------------------------------------------------------------------------| +| 20, 30, 40, 50 | 15 | G-FR1-A1-4 (Note 1) | -87.8 | +| 20, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 (Note 1) | -88.1 | +| 20, 30, 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 (Note 1) | -88.2 | + +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 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-3: NR Local Area BS reference sensitivity levels** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel (Note 5) | 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 (Note 1) | -93 | -92.7 | -92.5 | +| | | G-FR1-A1-10 (Note 3) | -93 (Note 2) | -92.7 (Note 2) | -92.5 (Note 2) | +| 10, 15 | 30 | G-FR1-A1-2 (Note 1) | -93.1 | -92.8 | -92.6 | +| 10, 15 | 60 | G-FR1-A1-3 (Note 1) | -90.2 | -89.9 | -89.7 | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 (Note 1) | -86.6 | -86.3 | -86.1 | +| | | G-FR1-A1-11 (Note 4) | -86.6 (Note 2) | -86.3 (Note 2) | -86.1 (Note 2) | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 (Note 1) | -86.9 | -86.6 | -86.4 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 (Note 1) | -87 | -86.7 | -86.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 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 2: The requirements apply to BS that supports NB-IoT operation in NR in-band. + +Note 3: $P_{\text{REFSENS}}$ is the power level of a single instance of the reference measurement channel. This requirement shall be met for a single instance of G-FR1-A1-10 mapped to the 24 NR resource blocks adjacent to the NB-IoT PRB, and for each consecutive application of a single instance of G-FR1-A1-1 mapped to disjoint frequency ranges with a width of 25 resource blocks each. + +Note 4: $P_{\text{REFSENS}}$ is the power level of a single instance of the reference measurement channel. This requirement shall be met for a single instance of G-FR1-A1-11 mapped to the 105 NR resource blocks adjacent to the NB-IoT PRB, and for each consecutive application of a single instance of G-FR1-A1-4 mapped to disjoint frequency ranges with a width of 106 resource blocks each. + +Note 5: These reference measurement channels are not applied for band n46, n96 and n102. + +**Table 7.2.5-3a: NR Local Area BS reference sensitivity levels for band n46** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | Reference sensitivity power level, P_{\text{REFSENS}} (dBm) | +|-----------------------------------|----------------------------------|--------------------------------------|---------------------------------------------------------------------------------| +| 10 | 15 | G-FR1-A1-12 (Note 2) | -98.5 | +| | 30 | G-FR1-A1-13 (Note 2) | -96.2 | +| | 60 | G-FR1-A1-3 (Note 1, 3) | -89.4 | +| 20 | 15 | G-FR1-A1-14 (Note 2) | -95.6 | +| | 30 | G-FR1-A1-15 (Note 2) | -92.6 | +| | 60 | G-FR1-A1-6 (Note 1, 3) | -86.2 | +| 40 | 15 | G-FR1-A1-16 (Note 2) | -92.5 | +| | 30 | G-FR1-A1-17 (Note 2) | -89.5 | +| | 60 | G-FR1-A1-6 (Note 1, 3) | -86.2 | +| 60 | 30 | G-FR1-A1-18 (Note 2) | -87.9 | +| | 60 | G-FR1-A1-6 (Note 1, 3) | -86.2 | +| 80 | 30 | G-FR1-A1-19 (Note 2) | -86.6 | +| | 60 | G-FR1-A1-6 (Note 1, 3) | -86.2 | + +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 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 2: $P_{\text{REFSENS}}$ is the power level of a single instance of the reference measurement channel. This requirement shall be met for each interleaved 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 3: For 60kHz SCS reference measurement channel is reused from Table 7.2.5-3.. + +**Table 7.2.5-3b: NR Local Area BS reference sensitivity levels for band n96 and n102** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | Reference sensitivity power level, P_{\text{REFSENS}} (dBm) | +|-----------------------------------|----------------------------------|--------------------------------------|---------------------------------------------------------------------------------| +| 20 | 15 | G-FR1-A1-14 (Note 2) | -94.6 | +| | 30 | G-FR1-A1-15 (Note 2) | -91.6 | +| | 60 | G-FR1-A1-6 (Note 1, 3) | -85.2 | +| 40 | 15 | G-FR1-A1-16 (Note 2) | -91.5 | +| | 30 | G-FR1-A1-17 (Note 2) | -88.5 | +| | 60 | G-FR1-A1-6 (Note 1, 3) | -85.2 | +| 60 | 30 | G-FR1-A1-18 (Note 2) | -86.9 | +| | 60 | G-FR1-A1-6 (Note 1, 3) | -85.2 | +| 80 | 30 | G-FR1-A1-19 (Note 2) | -85.6 | +| | 60 | G-FR1-A1-6 (Note 1, 3) | -85.2 | + +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 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 2: $P_{\text{REFSENS}}$ is the power level of a single instance of the reference measurement channel. This requirement shall be met for each interleaved 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 3: For 60kHz SCS reference measurement channel is reused from Table 7.2.5-3. + +**Table 7.2.5-3c: NR Local Area BS reference sensitivity levels for band n104** + +| BS channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel (Note 5) | Reference sensitivity power level, P_{\text{REFSENS}} (dBm) | +|-------------------------------------|----------------------------------|-----------------------------------------------|---------------------------------------------------------------------------------| +| 20, 30, 40, 50 | 15 | G-FR1-A1-4 (Note 1) | -84.8 | +| 20, 30, 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 (Note 1) | -85.1 | +| 20, 30, 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 (Note 1) | -85.2 | + +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 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.3 Dynamic range + +### 7.3.1 Definition and applicability + +The dynamic range is specified as a measure of the capability of the receiver to receive a wanted signal in the presence of an interfering signal at the *antenna connector* for BS type I-C or *TAB connector* for BS type I-H inside the received BS channel bandwidth. In this condition, a throughput requirement shall be met for a specified reference measurement channel. The interfering signal for the dynamic range requirement is an AWGN signal. + +### 7.3.2 Minimum requirement + +The minimum requirement for BS type I-C is in TS 38.104 [2], clause 7.3.2. + +The minimum requirement for BS type I-H is in TS 38.104 [2], clause 7.3.2. + +### 7.3.3 Test purpose + +To verify that the BS type I-C receiver and each BS type I-H TAB connector receiver dynamic range, the relative throughput shall fulfil the specified limit. + +### 7.3.4 Method of test + +#### 7.3.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +#### 7.3.4.2 Procedure + +The minimum requirement is applied to all connectors under test. + +For BS type I-H the procedure is repeated until all TAB connectors necessary to demonstrate conformance have been tested; see clause 7.1. + +- 1) Connect the connector under test to measurement equipment as shown in annex D.2.2 for BS type I-C and in annex D.4.2 for BS type I-H. + +- 2) Set the signal generator for the wanted signal to transmit as specified in table 7.3.5-1 to table 7.3.5-3 according to the appropriate BS class, as well as table 7.3.5-1a to table 7.3.5-3a for a BS declared to be capable of NB-IoT operation in NR in-band (D.41). +- 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 to table 7.3.5-3 according to the appropriate BS class, as well as table 7.3.5-1a to table 7.3.5-3a for a BS declared to be capable of NB-IoT operation in NR in-band (D.41). +- 4) Measure the throughput according to annex A.2, as well as annex A.15 of TS 36.141 [24] for a BS declared to be capable of NB-IoT operation in NR in-band (D.41). + +In addition, for a *multi-band connector*, the following steps shall apply: + +- 5) For *multi-band connector* 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 + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.2 with parameters specified in table 7.3.2-1 for Wide Area BS, in table 7.3.2-2 for Medium Range BS and in table 7.3.2-3 for Local Area BS in any operating band except for band n46, n96, n102 and n104. + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.2 with parameters specified in table 7.3.5-2b for Medium Range BS and in table 7.3.5-3b for Local Area BS, for band n46. + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.2 with parameters specified in table 7.3.5-2c for Medium Range BS and in table 7.3.5-3c for Local Area BS, for band n96 and n102. + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.2 with parameters specified in table 7.3.5-1b for Wide Area BS, in table 7.3.5-2d for Medium Range BS and in table 7.3.5-3d for Local Area BS in band n104. + +For NB-IoT operation in NR in-band, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in Annex A of TS 36.141 [24] with parameters specified in table 7.3.5-1a for Wide Area BS, in table 7.3.5-2a for Medium Range BS and in table 7.3.5-3a for Local Area BS. + +**Table 7.3.5-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-1a: Wide Area BS dynamic range for NB-IoT operation in NR in-band** + +| BS channel bandwidth (MHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / BWConfig | Type of interfering signal | +|-----------------------------------|-------------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 5 | FRC A15-1 in Annex A.15 in TS 36.141 [24] | -99.4 | -82.5 | AWGN | +| 10 | | | -79.3 | | +| 15 | | | -77.5 | | +| 20 | | | -76.2 | | +| 25 | | | -75.2 | | +| 30 | | | -74.4 | | +| 35 | | | -73.7 | | +| 40 | | | -73.1 | | +| 45 | | | -72.6 | | +| 50 | | | -72.1 | | +| 5 | FRC A15-2 in Annex A.15 in TS 36.141 [24] | -105.3 | -82.5 | AWGN | +| 10 | | | -79.3 | | +| 15 | | | -77.5 | | +| 20 | | | -76.2 | | +| 25 | | | -75.2 | | +| 30 | | | -74.4 | | +| 35 | | | -73.7 | | +| 40 | | | -73.1 | | +| 45 | | | -72.6 | | +| 50 | | | -72.1 | | + +**Table 7.3.5-1b: Wide Area BS dynamic range for n104** + +| 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 | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 20 | 15 | G-FR1-A2-4 | -63.2 | -75.2 | AWGN | +| | 30 | G-FR1-A2-5 | -63.2 | | | +| | 60 | G-FR1-A2-6 | -63.5 | | | +| 30 | 15 | G-FR1-A2-4 | -63.2 | -73.4 | AWGN | +| | 30 | G-FR1-A2-5 | -63.2 | | | +| | 60 | G-FR1-A2-6 | -63.5 | | | +| 40 | 15 | G-FR1-A2-4 | -63.2 | -72.1 | AWGN | +| | 30 | G-FR1-A2-5 | -63.2 | | | +| | 60 | G-FR1-A2-6 | -63.5 | | | +| 50 | 15 | G-FR1-A2-4 | -63.2 | -71.1 | AWGN | +| | 30 | G-FR1-A2-5 | -63.2 | | | +| | 60 | G-FR1-A2-6 | -63.5 | | | +| 60 | 30 | G-FR1-A2-5 | -63.2 | -70.3 | AWGN | +| | 60 | G-FR1-A2-6 | -63.5 | | | +| 70 | 30 | G-FR1-A2-5 | -63.2 | -69.7 | AWGN | +| | 60 | G-FR1-A2-6 | -63.5 | | | +| 80 | 30 | G-FR1-A2-5 | -63.2 | -69.1 | AWGN | +| | 60 | G-FR1-A2-6 | -63.5 | | | +| 90 | 30 | G-FR1-A2-5 | -63.2 | -68.5 | AWGN | +| | 60 | G-FR1-A2-6 | -63.5 | | | +| 100 | 30 | G-FR1-A2-5 | -63.2 | -68.1 | AWGN | +| | 60 | G-FR1-A2-6 | -63.5 | | | + +NOTE 1: 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-2: Medium Range BS dynamic range** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel (Note 2) | 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 1: 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 2: These reference measurement channels are not applied for band n46, n96 and n102. + +**Table 7.3.5-2a: Medium Range BS dynamic range for NB-IoT operation in NR in-band** + +| BS channel bandwidth (MHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / BWConfig | Type of interfering signal | +|-----------------------------------|-------------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 5 | FRC A15-1 in Annex A.15 in TS 36.141 [24] | -94.4 | -77.5 | AWGN | +| 10 | | | -74.3 | | +| 15 | | | -72.5 | | +| 20 | | | -71.2 | | +| 25 | | | -70.2 | | +| 30 | | | -69.4 | | +| 35 | | | -68.7 | | +| 40 | | | -68.1 | | +| 45 | | | -67.6 | | +| 50 | | | -67.1 | | +| 5 | FRC A15-2 in Annex A.15 in TS 36.141 [24] | -100.3 | -77.5 | AWGN | +| 10 | | | -74.3 | | +| 15 | | | -72.5 | | +| 20 | | | -71.2 | | +| 25 | | | -70.2 | | +| 30 | | | -69.4 | | +| 35 | | | -68.7 | | +| 40 | | | -68.1 | | +| 45 | | | -67.6 | | +| 50 | | | -67.1 | | + +**Table 7.3.5-2b: Medium Range BS dynamic range for band n46** + +| 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 | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 10 | 15 | G-FR1-A2-7 (Note 2) | -72.5 | -74.3 | AWGN | +| | 30 | G-FR1-A2-8 (Note 2) | -70.3 | | | +| | 60 | G-FR1-A2-3 (Note 1, 3) | -63.1 | | | +| 20 | 15 | G-FR1-A2-9 (Note 2) | -69.5 | -71.2 | AWGN | +| | 30 | G-FR1-A2-10 (Note 2) | -66.5 | | | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -59.5 | | | +| 40 | 15 | G-FR1-A2-11 (Note 2) | -66.4 | -68.1 | AWGN | +| | 30 | G-FR1-A2-12 (Note 2) | -63.4 | | | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -59.5 | | | +| 60 | 30 | G-FR1-A2-13 (Note 2) | -61.6 | -66.3 | AWGN | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -59.5 | | | +| 80 | 30 | G-FR1-A2-14 (Note 2) | -60.4 | -65.1 | AWGN | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -59.5 | | | + +NOTE 1: 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 2: 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 interleaved 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 3: For 60kHz SCS reference measurement channel is reused from Table 7.3.5-2. + +**Table 7.3.5-2c: Medium Range BS dynamic range for band n96 and n102** + +| 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 | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 20 | 15 | G-FR1-A2-9 (Note 2) | -68.5 | -70.2 | AWGN | +| | 30 | G-FR1-A2-10 (Note 2) | -65.5 | | | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -58.5 | | | +| 40 | 15 | G-FR1-A2-11 (Note 2) | -65.4 | -67.1 | AWGN | +| | 30 | G-FR1-A2-12 (Note 2) | -62.4 | | | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -58.5 | | | +| 60 | 30 | G-FR1-A2-13 (Note 2) | -60.6 | -65.3 | AWGN | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -58.5 | | | +| 80 | 30 | G-FR1-A2-14 (Note 2) | -59.4 | -64.1 | AWGN | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -58.5 | | | + +NOTE 1: 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 2: 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 interleaved 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 3: For 60kHz SCS reference measurement channel is reused from Table 7.3.5-2. + +**Table 7.3.5-2d: Medium Range BS dynamic range for n104** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel (Note 2) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / BWConfig | Type of interfering signal | +|-----------------------------------|---------------------------------|-----------------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 20 | 15 | G-FR1-A2-4 | -58.2 | -70.2 | AWGN | +| | 30 | G-FR1-A2-5 | -58.2 | | | +| | 60 | G-FR1-A2-6 | -58.5 | | | +| 30 | 15 | G-FR1-A2-4 | -58.2 | -68.4 | AWGN | +| | 30 | G-FR1-A2-5 | -58.2 | | | +| | 60 | G-FR1-A2-6 | -58.5 | | | +| 40 | 15 | G-FR1-A2-4 | -58.2 | -67.1 | AWGN | +| | 30 | G-FR1-A2-5 | -58.2 | | | +| | 60 | G-FR1-A2-6 | -58.5 | | | +| 50 | 15 | G-FR1-A2-4 | -58.2 | -66.1 | AWGN | +| | 30 | G-FR1-A2-5 | -58.2 | | | +| | 60 | G-FR1-A2-6 | -58.5 | | | +| 60 | 30 | G-FR1-A2-5 | -58.2 | -65.3 | AWGN | +| | 60 | G-FR1-A2-6 | -58.5 | | | +| 70 | 30 | G-FR1-A2-5 | -58.2 | -64.7 | AWGN | +| | 60 | G-FR1-A2-6 | -58.5 | | | +| 80 | 30 | G-FR1-A2-5 | -58.2 | -64.1 | AWGN | +| | 60 | G-FR1-A2-6 | -58.5 | | | +| 90 | 30 | G-FR1-A2-5 | -58.2 | -63.5 | AWGN | +| | 60 | G-FR1-A2-6 | -58.5 | | | +| 100 | 30 | G-FR1-A2-5 | -58.2 | -63.1 | AWGN | +| | 60 | G-FR1-A2-6 | -58.5 | | | + +NOTE 1: 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-3: Local Area BS dynamic range** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel (Note 2) | 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 1: 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 2: These reference measurement channels are not applied for band n46, n96 and n102. + +**Table 7.3.5-3a: Local Area BS dynamic range for NB-IoT operation in NR in-band** + +| BS channel bandwidth (MHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / BWConfig | Type of interfering signal | +|-----------------------------------|-------------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 5 | FRC A15-1 in Annex A.15 in TS 36.141 [24] | -91.4 | -74.5 | AWGN | +| 10 | | | -71.3 | | +| 15 | | | -69.5 | | +| 20 | | | -68.2 | | +| 25 | | | -67.2 | | +| 30 | | | -66.4 | | +| 35 | | | -65.7 | | +| 40 | | | -65.1 | | +| 45 | | | -64.6 | | +| 50 | | | -64.1 | | +| 5 | FRC A15-2 in Annex A.15 in TS 36.141 [24] | -97.3 | -74.5 | AWGN | +| 10 | | | -71.3 | | +| 15 | | | -69.5 | | +| 20 | | | -68.2 | | +| 25 | | | -67.2 | | +| 30 | | | -66.4 | | +| 35 | | | -65.7 | | +| 40 | | | -65.1 | | +| 45 | | | -64.6 | | +| 50 | | | -64.1 | | + +**Table 7.3.5-3b: Local Area BS dynamic range for band n46** + +| 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 | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 10 | 15 | G-FR1-A2-7 (Note 2) | -69.5 | -71.3 | AWGN | +| | 30 | G-FR1-A2-8 (Note 2) | -67.3 | | | +| | 60 | G-FR1-A2-3 (Note 1, 3) | -60.1 | | | +| 20 | 15 | G-FR1-A2-9 (Note 2) | -66.5 | -68.2 | AWGN | +| | 30 | G-FR1-A2-10 | -63.5 | | | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -56.5 | | | +| 40 | 15 | G-FR1-A2-11 (Note 2) | -63.4 | -65.1 | AWGN | +| | 30 | G-FR1-A2-12 (Note 2) | -60.4 | | | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -56.5 | | | +| 60 | 30 | G-FR1-A2-13 (Note 2) | -58.6 | -63.3 | AWGN | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -56.5 | | | +| 80 | 30 | G-FR1-A2-14 (Note 2) | -57.4 | -62.1 | AWGN | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -56.5 | | | + +NOTE 1: 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 2: 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 interleaved 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 3: For 60kHz SCS reference measurement channel is reused from Table 7.3.5-2. + +**Table 7.3.5-3c: Local area BS dynamic range for band n96 and n102** + +| 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 | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 20 | 15 | G-FR1-A2-9 (Note 2) | -65.5 | -67.2 | AWGN | +| | 30 | G-FR1-A2-10 (Note 2) | -62.5 | | | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -55.5 | | | +| 40 | 15 | G-FR1-A2-11 (Note 2) | -62.4 | -64.1 | AWGN | +| | 30 | G-FR1-A2-12 (Note 2) | -59.4 | | | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -55.5 | | | +| 60 | 30 | G-FR1-A2-13 (Note 2) | -57.6 | -62.3 | AWGN | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -55.5 | | | +| 80 | 30 | G-FR1-A2-14 (Note 2) | -56.4 | -61.1 | AWGN | +| | 60 | G-FR1-A2-6 (Note 1, 3) | -55.5 | | | + +NOTE 1: 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 2: 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 interleaved 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 3: For 60kHz SCS reference measurement channel is reused from Table 7.3.5-2. + +**Table 7.3.5-3d: Local Area BS dynamic range for n104** + +| 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 | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|------------------------------------------------------------------|-----------------------------------| +| 20 | 15 | G-FR1-A2-4 | -55.2 | -67.2 | AWGN | +| | 30 | G-FR1-A2-5 | -55.2 | | | +| | 60 | G-FR1-A2-6 | -55.5 | | | +| 30 | 15 | G-FR1-A2-4 | -55.2 | -65.4 | AWGN | +| | 30 | G-FR1-A2-5 | -55.2 | | | +| | 60 | G-FR1-A2-6 | -55.5 | | | +| 40 | 15 | G-FR1-A2-4 | -55.2 | -64.1 | AWGN | +| | 30 | G-FR1-A2-5 | -55.2 | | | +| | 60 | G-FR1-A2-6 | -55.5 | | | +| 50 | 15 | G-FR1-A2-4 | -55.2 | -63.1 | AWGN | +| | 30 | G-FR1-A2-5 | -55.2 | | | +| | 60 | G-FR1-A2-6 | -55.5 | | | +| 60 | 30 | G-FR1-A2-5 | -55.2 | -62.3 | AWGN | +| | 60 | G-FR1-A2-6 | -55.5 | | | +| 70 | 30 | G-FR1-A2-5 | -55.2 | -61.7 | AWGN | +| | 60 | G-FR1-A2-6 | -55.5 | | | +| 80 | 30 | G-FR1-A2-5 | -55.2 | -61.1 | AWGN | +| | 60 | G-FR1-A2-6 | -55.5 | | | +| 90 | 30 | G-FR1-A2-5 | -55.2 | -60.5 | AWGN | +| | 60 | G-FR1-A2-6 | -55.5 | | | +| 100 | 30 | G-FR1-A2-5 | -55.2 | -60.1 | AWGN | +| | 60 | G-FR1-A2-6 | -55.5 | | | + +NOTE 1: 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.4 In-band selectivity and blocking + +### 7.4.1 Adjacent Channel Selectivity (ACS) + +#### 7.4.1.1 Definition and applicability + +Adjacent channel selectivity (ACS) is a measure of the receiver's ability to receive a wanted signal at its assigned channel frequency at the *antenna connector* for BS type I-C or *TAB connector* for BS type I-H 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. + +#### 7.4.1.2 Minimum requirement + +The minimum requirement for BS type I-C and BS type I-H are in TS 38.104 [2], clause 7.4.1.2. + +#### 7.4.1.3 Test purpose + +The test purpose is to verify the ability of the BS receiver filter to suppress interfering signals in the channels adjacent to the wanted channel. + +#### 7.4.1.4 Method of test + +##### 7.4.1.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier (SC): M; see clause 4.9.1. + +*Base Station RF Bandwidth* positions to be tested for multi-carrier (MC): + +- $M_{\text{RFBW}}$ for *single-band connector(s)*, see clause 4.9.1, +- $B'_{\text{RFBW\_T\_RFBW}}$ and $B'_{\text{RFBW\_T\_RFBW}}$ for *multi-band connector(s)*, see clause 4.9.1. + +##### 7.4.1.4.2 Procedure + +The minimum requirement is applied to all connectors under test. + +For *BS type 1-H* the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested; see clause 7.1. + +- 1) Connect the connector under test to measurement equipment as shown in annex D.2.3 for *BS type 1-C* and in annex D.4.3 for *BS type 1-H*. +- 2) For FDD operation, set the BS to transmit: + - For single carrier operation set the connector under test to transmit at manufacturers declared *rated carrier output power* ( $P_{\text{rated,c,AC}}$ or $P_{\text{rated,c,TABC}}$ , D.21). + - For a connector under test declared to be capable of multi-carrier and/or CA operation (D.15-D.16) set the connector under test to transmit on all carriers configured using the applicable test configuration and corresponding power setting specified in clauses 4.7 and 4.8 using the corresponding test models or set of physical channels in clause 4.9.2 +- 3) Set the signal generator for the wanted signal to transmit as specified in table 7.4.1.5-1. +- 4) Set the signal generator for the interfering signal to transmit at the frequency offset and as specified in table 7.4.1.5-1 and 7.4.1.5-2. +- 5) Measure the throughput according to annex A.1, as well as annex A.14 of TS 36.141 [24] for a BS declared to be capable of NB-IoT operation in NR in-band (D.41). + +In addition, for a *multi-band connector*, the following steps shall apply: + +- 6) For *multi-band connector* 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.1.5 Test requirements + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel. + +For BS operating except for band n46, n96, n102 and n104, the wanted and the interfering signal coupled to the *BS type 1-C antenna connector* or *BS type 1-H TAB connector* are specified in table 7.4.1.5-1 and the frequency offset between the wanted and interfering signal in table 7.4.1.5-2 for ACS. The reference measurement channel for the wanted signal is identified in table 7.2.5-1, 7.2.5-2 and 7.2.5-3 for each channel bandwidth in any operating band except for band n46, n96, n102 and n104 and further specified in annex A.1. The characteristics of the interfering signal is further specified in annex E. + +For BS operating in band n46, n96 and n102, the wanted and the interfering signal coupled to the BS type 1-C antenna connector or BS type 1-H TAB connector are specified in table 7.4.1.5-1a, 7.4.1.5-1b and the frequency offset between the wanted and interfering signal in table 7.4.1.5-2a for ACS. The reference measurement channel for the wanted signal is identified in table 7.2.5-2a, 7.2.5-3a and 7.2.5-3b for each BS channel bandwidth and further specified in annex A.1a. The characteristics of the interfering signal is further specified in annex D. + +For BS operating in band n104, the wanted and the interfering signal coupled to the BS type 1-C antenna connector or BS type 1-H TAB connector are specified in table 7.4.1.5-1b and the frequency offset between the wanted and interfering signal in table 7.4.1.5-2 for ACS. The reference measurement channel for the wanted signal is identified in table 7.2.5-1a, 7.2.5-2c, and 7.2.5-3c for each *BS channel bandwidth* and further specified in annex A.1. The characteristics of the interfering signal is further specified in annex D. + +For BS supporting NB-IoT operation in NR in-band, the wanted and the interfering signal coupled to the *BS type 1-C antenna connector* are specified in table 7.4.1.5-1 and the frequency offset between the wanted and interfering signal in table 7.4.1.5-2 for ACS. The reference measurement channel for the NB-IoT wanted signal is identified in clause 7.2.5 of TS 36.141 [24]. The characteristics of the interfering signal is further specified in annex E. + +The ACS 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 ACS requirement shall apply in addition inside any sub-block gap, in case the sub-block gap size is at least as wide as the NR interfering signal in table 7.4.1.5-2. The interfering signal offset is defined relative to the sub-block edges inside the sub-block gap. + +For a *multi-band connector*, the ACS requirement shall apply in addition inside any Inter RF Bandwidth gap, in case the Inter RF Bandwidth gap size is at least as wide as the NR interfering signal in table 7.4.1.5-2. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges inside the Inter RF Bandwidth gap + +Conducted requirement is defined at the *antenna connector* for *BS type 1-C* and at the *TAB connector* for *BS type 1-H*. + +**Table 7.4.1.5-1: Base station ACS requirement** + +| BS channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|-----------------------------------------------------------------| +| 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $P_{\text{REFSENS}} + 6 \text{ dB}$ | Wide Area BS: -52
Medium Range BS: -47
Local Area BS: -44 | +| NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the BS for that bandwidth.
NOTE 2: $P_{\text{REFSENS}}$ depends on the RAT. For NR, $P_{\text{REFSENS}}$ depends also on the BS channel bandwidth as specified in TS 38.104 [2], table 7.2.2-1, 7.2.2-2 and 7.2.2-3. For NB-IoT, $P_{\text{REFSENS}}$ depends also on the sub-carrier spacing as specified in tables 7.2.1-5, 7.2.1-5a and 7.2.1-5c of TS 36.104 [22]. | | | + +**Table 7.4.1.5-1a: Base station ACS requirement for band n46, n96 and n102** + +| BS channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|--------------------------------------------| +| 10, 20, 40, 60, 80 (Note 1) | $P_{REFSENS} + 6$ dB | Medium Range BS: -47
Local Area BS: -44 | +| NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the BS for that bandwidth.
NOTE 2: $P_{REFSENS}$ depends on the RAT. For NR, $P_{REFSENS}$ depends also on the BS channel bandwidth as specified in tables 7.2.2-2a, 7.2.2-2b, 7.2.2-3a, 7.2.2-3b of TS 38.104[2]. | | | + +**Table 7.4.1.5-1b: Base station ACS requirement for band n104** + +| BS channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|-----------------------------------------------------------------| +| 20, 30, 40, 50, 60, 70, 80, 90, 100 (Note 1) | $P_{REFSENS} + 6$ dB | Wide Area BS: -55
Medium Range BS: -50
Local Area BS: -47 | +| NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the BS for that bandwidth.
NOTE 2: $P_{REFSENS}$ depends on the RAT. For NR, $P_{REFSENS}$ depends also on the BS channel bandwidth as specified in tables 7.2.2-1a, 7.2.2-2c, 7.2.2-3c of TS 38.104[2]. | | | + +**Table 7.4.1.5-2: Base Station ACS interferer frequency offset values** + +| BS channel bandwidth of the lowest/highest carrier received (MHz) | 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 | +|--------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------| +| 5 | $\pm 2.5025$ | 5 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 10 | $\pm 2.5075$ | | +| 15 | $\pm 2.5125$ | | +| 20 | $\pm 2.5025$ | | +| 25 | $\pm 9.4675$ | 20 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 30 | $\pm 9.4725$ | | +| 35 | $\pm 9.4625$ | | +| 40 | $\pm 9.4675$ | | +| 45 | $\pm 9.4725$ | | +| 50 | $\pm 9.4625$ | | +| 60 | $\pm 9.4725$ | | +| 70 | $\pm 9.4675$ | | +| 80 | $\pm 9.4625$ | | +| 90 | $\pm 9.4725$ | | +| 100 | $\pm 9.4675$ | | + +**Table 7.4.1.5-2a: Base Station ACS interferer frequency offset values for band n46, n96 and n102** + +| BS channel bandwidth of the lowest/highest carrier received (MHz) | 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 | +|--------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------| +| 10 | ±9.4675 | 20 MHz DFT-s-OFDM NR signal
15 kHz SCS, 100 RBs | +| 20 | ±9.4625 | | +| 40 | ±9.4675 | | +| 60 | ±9.4725 | | +| 80 | ±9.4625 | | + +## 7.4.2 In-band blocking + +### 7.4.2.1 Definition and applicability + +The in-band blocking characteristics is a measure of the receiver's ability to receive a wanted signal at its assigned channel at the *antenna connector* for *BS type 1-C* or *TAB connector* for *BS type 1-H* in the presence of an unwanted interferer, which is an NR signal for general blocking or an NR signal with one resource block for narrowband blocking. + +### 7.4.2.2 Minimum requirement + +The minimum requirements for *BS type 1-C* and *BS type 1-H* are in TS 38.104 [2], clause 7.4.2.2. + +### 7.4.2.3 Test purpose + +The test purpose is to verify the ability of the BS receiver to withstand high-levels of in-band interference from unwanted signals at specified frequency offsets without undue degradation of its sensitivity. + +### 7.4.2.4 Method of test + +#### 7.4.2.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier (SC): M; see clause 4.9.1 + +*Base Station RF Bandwidth* positions to be tested for multi-carrier (MC) and/or CA: + +- $M_{\text{RFBW}}$ for *single-band connector(s)*, see clause 4.9.1, +- $B_{\text{RFBW\_T}}$ and $B'_{\text{RFBW\_T}}$ for *multi-band connector(s)*, see clause 4.9.1. + +NOTE: When testing in M (or $M_{\text{RFBW}}$ ), if the interferer is fully or partially located outside the supported frequency range, then the test shall be done instead in B (or $B_{\text{RFBW}}$ ) and T (or $T_{\text{RFBW}}$ ), and only with the interferer located inside the supported frequency range. + +#### 7.4.2.4.2 Procedure for general blocking + +The minimum requirement is applied to all connectors under test. + +For *BS type 1-H* the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested; see clause 7.1. + +- 1) Connect the connector under test to measurement equipment as shown in annex D.2.3 for *BS type 1-C* and in annex D.4.3 for *BS type 1-H*. +- 2) For FDD operation, set the BS to transmit: + - For single carrier operation set the connector under test to transmit at manufacturers declared *rated carrier output power* ( $P_{\text{rated,c,AC}}$ or $P_{\text{rated,c,TABC}}$ , D.21). + - For a connector under test declared to be capable of multi-carrier and/or CA operation (D.15-D.16) set the connector under test to transmit on all carriers configured using the applicable test configuration and corresponding power setting specified in clauses 4.7 and 4.8 using the corresponding test models or set of physical channels in clause 4.9.2. +- 3) Set the signal generator for the wanted signal to transmit as specified in table 7.4.2.5-1. +- 4) Set the signal generator for the interfering signal to transmit at the frequency offset and as specified in table 7.4.2.5-1. 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.2.5-1. +- 5) Measure the throughput according to annex A.1, as well as annex A.14 of TS 36.141 [24] for a BS declared to be capable of NB-IoT operation in NR in-band (D.41). + +In addition, for a *multi-band connector*, the following steps shall apply: + +- 6) For *multi-band connector* 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.2.4.3 Procedure for narrowband blocking + +The minimum requirement is applied to all connectors under test. + +For *BS type 1-H* the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested; see clause 7.1. + +- 1) Connect the connector under test to measurement equipment as shown in annex D.2.3 for *BS type 1-C* and in annex D.4.3 for *BS type 1-H*. +- 2) For FDD operation, set the BS to transmit: + - For single carrier operation set the connector under test to transmit at manufacturers declared *rated carrier output power* ( $P_{\text{rated,c,AC}}$ or $P_{\text{rated,c,TABC}}$ , D.21). + - For a connector under test declared to be capable of multi-carrier and/or CA operation (D.15-D.16) set the connector under test to transmit on all carriers configured using the applicable test configuration and corresponding power setting specified in clauses 4.7 and 4.8 using the corresponding test models or set of physical channels in clause 4.9.2. +- 3) Set the signal generator for the wanted signal to transmit as specified in table 7.4.2.5-2, as well as table 7.4.2.5-2a for a BS declared to be capable of NB-IoT operation in NR in-band (D.41). +- 4) Set the signal generator for the interfering signal to transmit at the frequency offset and as specified in table 7.4.2.5-2 and 7.4.2.5-3, as well as table 7.4.2.5-2a for a BS declared to be capable of NB-IoT operation in NR in-band (D.41). Set-up and sweep the interfering RB centre frequency offset to the channel edge of the wanted signal according to table 7.4.2.5-3. + +- 5) Measure the throughput according to annex A.1, as well as annex A.14 of TS 36.141 [24] for a BS declared to be capable of NB-IoT operation in NR in-band (D.41). + +In addition, for a *multi-band connector*, the following steps shall apply: + +- 6) For *multi-band connector* 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.2.5 Test requirements + +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 type 1-C antenna connector* or *BS type 1-H TAB connector* using the parameters in tables 7.4.2.5-1, 7.4.2.5-2 and 7.4.2.5-3 for general blocking and narrowband blocking requirements. Narrowband blocking requirements are not applied for band n46, n96, n102 and n104. The reference measurement channel for the wanted signal is identified in clause 7.2.5 for each channel bandwidth and further specified in annex A.1. The characteristics of the interfering signal is further specified in annex E. + +For NB-IoT operation in NR in-band, 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 type 1-C antenna connector* using the parameters in tables 7.4.2.5-1, 7.4.2.5-2a and 7.4.2.5-3 for general blocking and narrowband blocking requirements. The reference measurement channel for the NB-IoT wanted signal is identified in clause 7.2.5 of TS 36.141 [24]. The characteristics of the interfering signal is further specified in annex E. + +The in-band blocking requirements apply 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 type 1-C* and *BS type 1-H*, 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}$ for *BS type 1-C* and *BS type 1-H* is defined in table 7.4.2.5-0. + +Minimum conducted requirement is defined at the *antenna connector* for *BS type 1-C* and at the *TAB connector* for *BS type 1-H*. + +**Table 7.4.2.5-0: $\Delta f_{OOB}$ offset for NR operating bands** + +| BS type | Operating band characteristics | $\Delta f_{OOB}$ (MHz) | +|--------------------|----------------------------------------------------------|------------------------| +| BS type 1-C | $F_{UL\_high} - F_{UL\_low} \leq 200$ MHz | 20 | +| | $200$ MHz $< F_{UL\_high} - F_{UL\_low} \leq 900$ MHz | 60 | +| BS type 1-H | $F_{UL\_high} - F_{UL\_low} < 100$ MHz | 20 | +| | $100$ MHz $\leq F_{UL\_high} - F_{UL\_low} \leq 900$ MHz | 60 | +| | $100$ MHz $\leq F_{UL\_high} - F_{UL\_low} \leq 900$ MHz | 60 | + +For band n46, n96 and n102, $\Delta f_{OOB}$ is defined in table 7.4.2.5-0a. + +**Table 7.4.2.5-0a: $\Delta f_{OOB}$ offset for NR operating bands** + +| Operating band | $\Delta f_{OOB}$ (MHz) | +|----------------|------------------------| +| n46, n102 | 60 | +| n96 | 70 | + +For band n104, $\Delta f_{OOB}$ for *BS type 1-C* and *BS type 1-H* is defined in table 7.4.2.5-0b. + +**Table 7.4.2.5-0b: $\Delta f_{\text{OOB}}$ offset for NR operating bands for band n104** + +| BS type | Operating band | $\Delta f_{\text{OOB}}$ (MHz) | +|-------------|----------------|-------------------------------| +| BS type 1-H | n104 | 100 | +| BS type 1-C | n104 | 60 | + +For a BS operating in non-contiguous spectrum within any *operating band*, the in-band blocking requirements apply 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.4.2.5-1. The interfering signal offset is defined relative to the sub-block edges inside the sub-block gap. + +For a *multi-band connector*, the blocking requirements apply in the in-band blocking frequency ranges 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.4.2.5-1. + +For a BS 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 NR interfering signal in table 7.4.2.5-3. The interfering signal offset is defined relative to the sub-block edges inside the sub-block gap. + +For a *multi-band 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 NR interfering signal in table 7.4.2.5-3. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges inside the Inter RF Bandwidth gap. + +**Table 7.4.2.5-1: Base station general blocking requirement** + +| BS channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) (Note 2) | Interfering 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 | +|-------------------------------------------------------------------|-----------------------------------------|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------| +| 5, 10, 15, 20 | $P_{\text{REFSENS}} + x$ dB | Wide Area BS: -43
Medium Range BS: -38
Local Area BS: -35 | $\pm 7.5$ | 5 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $P_{\text{REFSENS}} + x$ dB | Wide Area BS: -43
Medium Range BS: -38
Local Area BS: -35 | $\pm 30$ | 20 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | + +NOTE 1: $P_{\text{REFSENS}}$ depends on the RAT. For NR, $P_{\text{REFSENS}}$ depends also on the *BS channel bandwidth* as specified in TS 38.104 [2], table 7.2.2-1, 7.2.2-2 and 7.2.2-3. For band n104, $P_{\text{REFSENS}}$ depends on the *BS channel bandwidth* as specified in tables 7.2.2-1a, 7.2.2-2c, 7.2.2-3c of TS 38.104[2]. For NB-IoT, $P_{\text{REFSENS}}$ depends also on the *sub-carrier spacing* as specified in tables 7.2.1-5, 7.2.1-5a and 7.2.1-5c of TS 36.104 [22]. + +NOTE 2: For a BS capable of single band operation only, "x" is equal to 6 dB. For a BS capable of multi-band operation, "x" is equal to 6 dB 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. + +**Table 7.4.2.5-1a: Base station general blocking requirement for n46** + +| BS channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering 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 | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------| +| 10, 20, 40, 60, 80 | $P_{\text{REFSENS}} + 6$ dB | Medium Range BS: -38
Local Area BS: -35 | $\pm 30$ | 20 MHz DFT-s-OFDM NR signal
15 kHz SCS, 100 RBs | +| NOTE: $P_{\text{REFSENS}}$ depends on the RAT. For NR, $P_{\text{REFSENS}}$ depends also on the BS channel bandwidth as specified in tables 7.2.2-2a and 7.2.2-3a of TS 38.104[2]. | | | | | + +**Table 7.4.2.5-1b: Base station general blocking requirement for n96 and n102** + +| BS channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering 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 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------| +| 20, 40, 60, 80 | $P_{\text{REFSENS}} + 6$ dB | Medium Range BS: -38
Local Area BS: -35 | $\pm 30$ | 20 MHz DFT-s-OFDM NR signal
15 kHz SCS, 100 RBs | +| NOTE: $P_{\text{REFSENS}}$ depends on the RAT. For NR, $P_{\text{REFSENS}}$ depends also on the BS channel bandwidth as specified in tables 7.2.2-2b and 7.2.2-3b of TS 38.104[2].. | | | | | + +**Table 7.4.2.5-2: Base station narrowband blocking requirement** + +| BS channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | +|--------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-----------------------------------------------------------------| +| 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100
(Note 1) | $P_{\text{REFSENS}} + 6$ dB | Wide Area BS: -49
Medium Range BS: -44
Local Area BS: -41 | +| NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the BS for that BS channel bandwidth | | | +| NOTE 2: $P_{\text{REFSENS}}$ depends on the BS channel bandwidth as specified in TS 38.104 [2], table 7.2.2-1, 7.2.2-2 and 7.2.2-3. | | | +| NOTE 3: 7.5 kHz shift is not applied to the wanted signal. | | | + +**Table 7.4.2.5-2a: Base Station narrowband blocking requirement for NB-IoT operation in NR in-band** + +| BS channel bandwidth (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|--------------------------------------------------------| +| 5, 10, 15, 20, 25, 30, 35, 40, 45, 50 | $P_{\text{REFSENS}} + x$ dB
(Note 2) | Wide Area: -49
Medium Range: -44
Local Area: -41 | +| NOTE 1: $P_{\text{REFSENS}}$ depends on the sub-carrier spacing as specified in tables 7.2.1-5, 7.2.1-5a and 7.2.1-5c of TS 36.104 [22].
NOTE 2: "x" is equal to 8 in case of 5 MHz channel bandwidth and equal to 6 otherwise. | | | + +**Table 7.4.2.5-3: Base station narrowband blocking interferer frequency offsets** + +| BS channel bandwidth 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) (Note 2) | Type of interfering signal | +|--------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------| +| 5 | $\pm(350+m*180)$ ,
m=0, 1, 2, 3, 4, 9, 14, 19, 24 | 5 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 1 RB | +| 10 | $\pm(355+m*180)$ ,
m=0, 1, 2, 3, 4, 9, 14, 19, 24 | | +| 15 | $\pm(360+m*180)$ ,
m=0, 1, 2, 3, 4, 9, 14, 19, 24 | | +| 20 | $\pm(350+m*180)$ ,
m=0, 1, 2, 3, 4, 9, 14, 19, 24 | | +| 25 | $\pm(565+m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | 20 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 1 RB | +| 30 | $\pm(570+m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 35 | $\pm(560+m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 40 | $\pm(565+m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 45 | $\pm(570+m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 50 | $\pm(560+m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 60 | $\pm(570+m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 70 | $\pm(565+m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 80 | $\pm(560+m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 90 | $\pm(570+m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 100 | $\pm(565+m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | + +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 lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap. + +NOTE 2: The centre of the interfering RB refers to the frequency location between the two central subcarriers. + +#### 7.4.2.5.1 Additional narrowband blocking requirement for Band n100 + +The following requirement shall apply to BS operating in Band n100 in CEPT countries. For the wanted and interfering signal coupled to the *antenna connector*, using the parameters in table 7.4.2.5.1-1 and 7.4.2.5.1-2, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel. + +**Table 7.4.2.5.1-1: Additional narrowband blocking requirement for n100** + +| BS channel bandwidth of the lowest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | +|-----------------------------------------------------------|--------------------------------|-------------------------------------| +| 5 | $P_{\text{REFSENS}} + 6$ dB | Wide Area BS: -39 (Note 2) | + +NOTE 1: $P_{\text{REFSENS}}$ depends on the *BS channel bandwidth* as specified in clause 7.2.2 of TS 38.104[2]. + +NOTE 2: Interfering signal mean power level was derived considering an interfering signal with 10% duty cycle. For more details, refer to TR 38.853. + +**Table 7.4.2.5.1-2: Interferer frequency for additional narrowband blocking requirement for n100** + +| BS channel bandwidth of the lowest carrier received (MHz) | Interfering RB centre frequency (Note 2) | Type of interfering signal | +|-----------------------------------------------------------|-------------------------------------------------------------------------|----------------------------------------------| +| 5 | 874.4 MHz - (350 kHz + $m \cdot 180$ kHz), $m=0, 1, 2, 3, 4, 9, 14, 19$ | 5 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 1 RB | + +NOTE 1: Interfering signal consisting of one resource block positioned at the stated frequency, the *channel bandwidth* of the interfering signal is located adjacently to the lower UL *operating band edge*. + +NOTE 2: The centre of the interfering RB refers to the frequency location between the two central subcarriers. + +## 7.5 Out-of-band blocking + +### 7.5.1 Definition and applicability + +The out-of-band blocking characteristics is a measure of the receiver ability to receive a wanted signal at its assigned channel at the *antenna connector* for *BS type 1-C* or *TAB connector* for *BS type 1-H* in the presence of an unwanted interferer out of the *operating band*, which is a CW signal for out-of-band blocking. + +### 7.5.2 Minimum requirement + +The minimum requirements for *BS type 1-C* and *BS type 1-H* are in TS 38.104 [2], clause 7.5.2. + +### 7.5.3 Test purpose + +To verify that the *BS type 1-C* receiver and each *BS type 1-H TAB connector* receiver dynamic range, the relative throughput shall fulfil the specified limit. + +### 7.5.4 Method of test + +#### 7.5.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier (SC): + +- M; see clause 4.9.1 + +*Base Station RF Bandwidth* positions to be tested for multi-carrier (MC): + +- $M_{\text{RFBW}}$ for *single-band connector(s)*, see clause 4.9.1, +- $B_{\text{RFBW\_T}}^{\text{RFBW}}$ and $B'_{\text{RFBW\_T}}^{\text{RFBW}}$ for *multi-band connector(s)*, see clause 4.9.1. + +In addition, for a multi-band *connector*: + +- For $B'_{\text{RFBW\_T}}$ , out-of-band blocking testing above the highest operating band may be omitted. +- For $B'_{\text{RFBW\_T}}$ , out-of-band blocking testing below the lowest operating band may be omitted. + +#### 7.5.4.2 Procedure + +The minimum requirement is applied to all connectors under test. + +For *BS type 1-H* the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested; see clause 7.1. + +- 1) Connect the connector under test to measurement equipment as shown in annex D.2.5 for *BS type 1-C* and in annex D.4.3 for *BS type 1-H*. +- 2) For FDD operation, set the BS to transmit a signal according to clause 4.9.2, connector under test to transmit on all carriers configured using the applicable test configuration and corresponding power setting specified in clauses 4.7 and 4.8. + +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. + +- 3) Set the signal generator for the wanted signal as defined in clause 7.5.5 to transmit as specified in table 7.5.5.1-1 and 7.5.5.2-1. +- 4) Set the Signal generator for the interfering signal to transmit at the frequency offset and as specified in table 7.5.5.1-1 and 7.5.5.2-1. The CW interfering signal shall be swept with a step size of 1 MHz over the range 1 MHz to $(F_{\text{UL\_low}} - \Delta f_{\text{OOB}})$ MHz and $(F_{\text{UL\_high}} + \Delta f_{\text{OOB}})$ MHz to 12750 MHz. +- 5) Measure the throughput according to annex A.1, as well as annex A.14 of TS 36.141 [24] for a BS declared to be capable of NB-IoT operation in NR in-band (D.41). + +In addition, for a *multi-band connector*, the following steps shall apply: + +- 6) For *multi-band connector* 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 General requirements + +Except for band n46, n96, n102 and n104, 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 type 1-C antenna connector* or *BS type 1-H TAB connector* using the parameters in table 7.5.5.1-1. The reference measurement channel for the wanted signal is identified in clause 7.2.2 for each channel bandwidth and further specified in annex A.1. + +For band n46, n96 and n102, 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 type 1-C antenna connector or BS type 1-H TAB connector using the parameters in table 7.5.5.1-1a. + +For *BS type 1-C* operating in band n104, 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 type 1-C antenna connector using the parameters in table 7.5.5.1-1a. + +For *BS type 1-H* operating in band n104, 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 type 1-H TAB connector using the parameters in table 7.5.5.1-1. + +For NB-IoT operation in NR in-band, 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 type 1-C antenna connector* using the parameters in table 7.5.5.1-1. The reference measurement channel for the NB-IoT wanted signal is identified in clause 7.2.5 of TS 36.141 [24]. The characteristics of the interfering signal is further specified in annex E. + +For *BS type 1-C* and *BS type 1-H* the out-of-band blocking requirement apply 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}$ for or *BS type 1-C* and *BS type 1-H* is defined in table 7.4.2.5-0. + +Minimum conducted requirement is defined at the *antenna connector* for *BS type 1-C* and at the *TAB connector* for *BS type 1-H*. + +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 clause 7.4.2.5 shall be excluded from the out-of-band blocking requirement. + +**Table 7.5.5.1-1: Out-of-band blocking performance requirement** + +| Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|----------------------------| +| $P_{REFSENS} + 6$ dB
(Note 1) | -15 | CW carrier | +| NOTE 1: $P_{REFSENS}$ depends on the RAT. For NR, $P_{REFSENS}$ depends also on the BS channel bandwidth as specified in TS 38.104 [2], table 7.2.2-1, 7.2.2-2 and 7.2.2-3. For band n104, $P_{REFSENS}$ depends also on the BS channel bandwidth as specified in TS 38.104 [2], table 7.2.2-1a, 7.2.2-2c and 7.2.2-3c. For NB-IoT, $P_{REFSENS}$ depends also on the sub-carrier spacing as specified in tables 7.2.1-5, 7.2.1-5a and 7.2.1-5c of TS 36.104 [22]. | | | +| NOTE 2: 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. | | | + +**Table 7.5.5.1-1a: Out-of-band blocking performance requirement for NR band n46, n96, n102 and n104 for BS type 1-C** + +| Operating Band | Centre Frequency of Interfering Signal [MHz] | Wanted Signal mean power (dBm) | Interfering Signal mean power (dBm) | Type of Interfering Signal | +|----------------|--------------------------------------------------------------------------------------------------------------------------|--------------------------------|-------------------------------------|----------------------------| +| n46, n96, n102 | $(F_{UL\_low} - 500)$ to $(F_{UL\_low} - \Delta f_{OOB})$
$(F_{UL\_high} + \Delta f_{OOB})$ to $(F_{UL\_high} + 500)$ | $P_{REFSENS} + 6\text{dB}$ | -35 | CW carrier | +| | 1 to $(F_{UL\_low} - 500)$
$(F_{UL\_high} + 500)$ to 12750 | $P_{REFSENS} + 6\text{dB}$ | -15 | CW carrier | +| n104 | $(F_{UL\_low} - 100)$ to $(F_{UL\_low} - \Delta f_{OOB})$
$(F_{UL\_high} + \Delta f_{OOB})$ to $(F_{UL\_high} + 100)$ | $P_{REFSENS} + 6\text{dB}$ | -35 | CW carrier | +| | 1 to $(F_{UL\_low} - 100)$
$(F_{UL\_high} + 100)$ to 12750 | $P_{REFSENS} + 6\text{dB}$ | -15 | CW carrier | + +NOTE 1: For band n46, n96, n102, $P_{REFSENS}$ depends on the BS channel bandwidth as specified in tables 7.2.2-2a, 7.2.2-2b, 7.2.2-3a, 7.2.2-3b of TS 38.104[2]. + +NOTE 2: For band n104, $P_{REFSENS}$ depends on the BS channel bandwidth as specified in tables 7.2.2-1a, 7.2.2-2c, 7.2.2-3c of TS 38.104[2]. + +### 7.5.5.2 Co-location requirements + +This additional blocking requirement may be applied for the protection of NR BS receivers when GSM, CDMA, UTRA, E-UTRA BS or NR BS operating in a different frequency band are co-located with a NR BS. The requirement is applicable to all channel bandwidths supported by the NR BS. + +The requirements in this clause assume a 30 dB coupling loss between interfering transmitter and NR BS receiver and are based on co-location with base stations of the same class. + +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 table 7.5.5.2-1 for all the BS classes. The reference measurement channel for the wanted signal is identified in tables 7.2.5-1, 7.2.5-2 and 7.2.5-3 for each channel bandwidth and further specified in annex A.1. + +For BS type 1-C and BS type 1-H blocking requirement for co-location with BS in other bands is applied for all operating bands for which co-location protection is provided. + +Minimum conducted requirement is defined at the antenna connector for BS type 1-C and at the TAB connector for BS type 1-H. + +**Table 7.5.5.2-1: Blocking performance requirement for NR BS when co-located with BS in other frequency bands.** + +| Frequency range of interfering signal | Wanted signal mean power for WA BS (dBm) | Interfering signal mean power for WA BS (dBm) | Interfering signal mean power for MR BS (dBm) | Interfering signal mean power for LA BS (dBm) | Type of interfering signal | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|----------------------------| +| Frequency range of co-located downlink operating band | $P_{\text{REFSENS}} + 6\text{dB}$ (Note 1) | +16 | +8 | x (Note 2) | CW carrier | +| NOTE 1: $P_{\text{REFSENS}}$ depends on the BS channel bandwidth as specified in TS 38.104 [2], table 7.2.2-1, 7.2.2-2 and 7.2.2-3. | | | | | | +| NOTE 2: x = -7 dBm for NR BS co-located with Pico GSM850 or Pico CDMA850
x = -4 dBm for NR BS co-located with Pico DCS1800 or Pico PCS1900
x = -6 dBm for NR BS co-located with UTRA bands or E-UTRA bands or NR bands | | | | | | +| NOTE 3: The requirement does not apply when the interfering signal falls within any of the supported uplink operating band(s) or in $\Delta f_{\text{OOB}}$ immediately outside any of the supported uplink operating band(s). | | | | | | +| NOTE 4: For unsynchronized base stations (except in band n46, n96 and n102), special co-location requirements may apply that are not covered by the 3GPP specifications | | | | | | + +### 7.5.5.3 Additional requirement + +#### 7.5.5.3.1 Additional requirement for Band n101 + +The following requirement may apply to BS operating in Band n101 in CEPT countries. For the wanted and interfering signal coupled to the *antenna connector*, using the parameters in table 7.5.5.3.1-1, the throughput shall be $\geq 95\%$ of the *maximum throughput* of the reference measurement channel. + +**Table 7.5.5.3.1-1: Additional out-of-band blocking requirement for n101** + +| BS channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering 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 | +|----------------------------------------------------------------------------------------------------------------|------------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| 5, 10 | $P_{\text{REFSENS}} + 3\text{ dB}$ | -20 | 1807.5 - 1877.5 | 5 MHz LTE signal | +| NOTE: $P_{\text{REFSENS}}$ depends on the BS channel bandwidth as specified in table 7.2.2-1 of TS 38.104[2].. | | | | | + +## 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 *antenna connector* (for BS type 1-C) or at the *TAB connector* (for BS type 1-H). The requirements apply to all BS with separate RX and TX *antenna connectors / TAB connectors*. + +NOTE: In this case for FDD operation the test is performed when both TX and RX are ON, with the TX *antenna connectors / TAB connectors* terminated. + +For *antenna connectors / TAB connectors* supporting both RX and TX in TDD, the requirements apply during the *transmitter OFF period*. For *antenna connectors / TAB connectors* supporting both RX and TX in FDD, the RX spurious emissions requirements are superseded by the TX spurious emissions requirements, as specified in clause 6.6.5. + +For RX-only *multi-band connectors*, the spurious emissions requirements are subject to exclusion zones in each supported *operating band*. For *multi-band connectors* 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*. + +For BS type 1-H manufacturer shall declare *TAB connector RX min cell groups* (D.33). Every *TAB connector* of BS type 1-H supporting reception in an *operating band* shall map to one *TAB connector RX min cell group*, where mapping of *TAB connectors* to cells/beams is implementation dependent. + +The number of active receiver units that are considered when calculating the conducted RX spurious emission limits ( $N_{RXU,counted}$ ) for BS type 1-H is calculated as follows: + +$$N_{RXU,counted} = \min(N_{RXU,active}, 8 \times N_{cells})$$ + +$N_{RXU,countedpercell}$ is used for scaling of *basic limits* and is derived as $N_{RXU,countedpercell} = N_{RXU,counted} / N_{cells}$ , where $N_{cells}$ is defined in clause 6.1. + +NOTE: $N_{RXU,active}$ is the number of actually active receiver units and is independent to the declaration of $N_{cells}$ . + +### 7.6.2 Minimum requirement + +The minimum requirements for BS type 1-C and BS type 1-H are in TS 38.104 [2], clause 7.6.2. + +### 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. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +*Base Station RF Bandwidth* positions to be tested for multi-carrier: + +- $M_{RFBW}$ in single-band operation, see clause 4.9.1, + +- $B_{RFBW\_T'_{RFBW}}$ and $B'_{RFBW\_T_{RFBW}}$ in multi-band operation, see clause 4.9.1. + +## 7.6.4.2 Procedure + +The minimum requirement is applied to all connectors under test, + +For *BS type 1-H* where there may be multiple *TAB connectors* they may be tested one at a time or multiple *TAB connectors* may be tested in parallel as shown in annex D.4.4. Whichever method is used the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested. + +- 1) Connect the connector under test to measurement equipment as shown in annex D.2.6 for *BS type 1-C* and in annex D.4.4 for *BS type 1-H*. +- 2) For FDD operation, for separate RX only connectors with single carrier operation set the connector under test to transmit at manufacturers declared *rated carrier output power* ( $P_{\text{rated,c,AC}}$ or $P_{\text{rated,c,TABC}}$ , D.21). Channel set-up shall be according to NR-FR1-TM 1.1. + +For FDD operation, for separate RX only connectors declared to be capable of multi-carrier and/or CA operation (D.15-D.16) set the connector under test to transmit on all carriers configured using the applicable test configuration and corresponding power setting specified in clauses 4.7 and 4.8 using the corresponding test models or set of physical channels in clause 4.9. + +For separate RX only connectors declared to be capable of NB-IoT operation in NR in-band (D.41), test shall be performed using N-TM according to clause 4.9.2.2.9. + +For TDD connectors capable of transmit and receive ensure the transmitter is OFF. + +- 3) Set the measurement equipment parameters as specified in table 7.6.5.1-1. + +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. + +- 4) Measure the spurious emissions over each frequency range described in table 7.6.5.1-1. + +In addition, for a *multi-band connector*, the following steps shall apply: + +- 5) For *multi-band connector* 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 Basic limits + +The receiver spurious emissions limits are provided in table 7.6.5.1-1. + +**Table 7.6.5.1-1: General BS receiver spurious emissions limits** + +| Spurious frequency range | Basic limit | Measurement bandwidth | Notes | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------|------------------------| +| 30 MHz – 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 | +| 12.75 GHz - 26 GHz | -47 dBm | 1 MHz | Note 1, Note 2, Note 6 | +| NOTE 1: Measurement bandwidths as in ITU-R SM.329 [5], s4.1. | | | | +| NOTE 2: Upper frequency as in ITU-R SM.329 [5], s2.5 table 1. | | | | +| NOTE 3: Applies for Band for which the upper frequency edge of the UL operating band is greater than 2.55 GHz and less than or equal to 5.2 GHz. | | | | +| NOTE 4: The frequency range from $\Delta f_{OBUE}$ below the lowest frequency of the BS transmitter operating band to $\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 connectors , the exclusion applies for all supported operating bands . | | | | +| NOTE 5: Void | | | | +| NOTE 6: Applies for Band for which the upper frequency edge of the UL operating band is greater than 5.2 GHz. | | | | + +### 7.6.5.2 BS type 1-C + +The RX spurious emissions requirements for *BS type 1-C* are that for each *antenna connector*, the power of emissions shall not exceed *basic limits* specified in table 7.6.5.1-1. + +For Band n41 and n90 operation in Japan, the sum of RX spurious emissions over all *antenna connectors* for *BS type 1-C* shall not exceed *basic limits* specified in table 7.6.5.1-1. The Rx spurious emissions requirements shall apply to BS that support NR or NR with NB-IoT operation in NR in-band. + +### 7.6.5.3 BS type 1-H + +The RX spurious emissions requirements for *BS type 1-H* are that for each applicable *basic limit* specified in table 7.6.5.1-1 for each *TAB connector RX min cell group*, the power sum of emissions at respective *TAB connectors* shall not exceed the BS limits specified as the *basic limits* + X, where $X = 10\log_{10}(N_{RXU,countedpercell})$ , unless stated differently in regional regulation. + +The RX spurious emission requirements are applied per the *TAB connector RX min cell group* for all the configurations supported by the BS. + +NOTE: Conformance to the 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 BS limit above for the respective frequency span. + +Or + +- 2) The spurious emissions power at each *TAB connector* shall be less than or equal to the 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 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 at the *antenna connector* for *BS type 1-C* or *TAB connector* for *BS type 1-H* in the presence of two interfering signals which have a specific frequency relationship to the wanted signal. + +### 7.7.2 Minimum requirement + +The minimum requirements for *BS type 1-C* and *BS type 1-H* are in TS 38.104 [2], clause 7.7.2. + +### 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. + +RF channels to be tested for single carrier (SC): M; see clause 4.9.1 + +*Base Station RF Bandwidth* positions to be tested for multi-carrier (MC) and/or CA: + +- $M_{\text{RFBW}}$ for *single-band connector(s)*, see clause 4.9.1, +- $B'_{\text{RFBW\_T}}{}_{\text{RFBW}}$ and $B'_{\text{RFBW\_T}}{}_{\text{RFBW}}$ for *multi-band connector(s)*, see clause 4.9.1. + +NOTE: When testing in M (or $M_{\text{RFBW}}$ ), if the interferer is fully or partially located outside the supported frequency range, then the test shall be done instead in B (or $B_{\text{RFBW}}$ ) and T (or $T_{\text{RFBW}}$ ), and only with the interferer located inside the supported frequency range. + +#### 7.7.4.2 Procedure + +The minimum requirement is applied to all connectors under test. + +For *BS type 1-H* the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested; see clause 7.1. + +- 1) Connect the connector under test to measurement equipment as shown in annex D.2.7 for *BS type 1-C* and in annex D.4.6 for *BS type 1-H*. +- 2) For FDD operation, set the BS to transmit: + - For single carrier operation set the connector under test to transmit at manufacturers declared *rated carrier output power* ( $P_{\text{rated,c,AC}}$ or $P_{\text{rated,c,TABC}}$ , D.21). + +- For a connector under test declared to be capable of multi-carrier and/or CA operation (D.15-D.16) set the connector under test to transmit on all carriers configured using the applicable test configuration and corresponding power setting specified in clauses 4.7 and 4.8 using the corresponding test models or set of physical channels in clause 4.9.2. +- 3) Set the signal generator for the wanted signal to transmit as specified in table 7.7.5-1 and 7.7.5-3. + - 4) Set the signal generator for the interfering signal to transmit at the frequency offset and as specified in table 7.7.5-2 and 7.7.5-4. + - 5) Measure the throughput according to annex A.1, as well as annex A.14 of TS 36.141 [24] for a BS declared to be capable of NB-IoT operation in NR in-band (D.41). + +In addition, for a *multi-band connector*, the following steps shall apply: + +- 6) For *multi-band connector* 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 + +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 coupled to the *BS type 1-C antenna connector* or *BS type 1-H TAB connector*, with the conditions specified in tables 7.7.5-1 and 7.7.5-2 for intermodulation performance in any operating band except for band n46, n96 and n102, and 7.7.5-1a for band n46, n96 and n102 and in tables 7.7.5-3, and 7.7.5-4 for narrowband intermodulation performance. Narrowband intermodulation requirements are not applied for band n46, n96, n102 and n104. The reference measurement channel for the wanted signal is identified in tables 7.2.5-1 to 7.2.5-3 for each channel bandwidth and further specified in annex A.1. The characteristics of the interfering signal is further specified in annex E. + +For NB-IoT operation in NR in-band, 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 coupled to the *BS type 1-C antenna connector*, with the conditions specified in tables 7.7.5-1 and 7.7.5-2 for intermodulation performance and in tables 7.7.5-3, and 7.7.5-4 for narrowband intermodulation performance. The reference measurement channel for the NB-IoT wanted signal is identified in clause 7.2.5 of TS 36.141 [24]. The characteristics of the interfering signal is further specified in annex E. + +The subcarrier spacing for the modulated interfering signal shall in general be the same as the subcarrier spacing for the wanted signal, except for the case of wanted signal subcarrier spacing 60 kHz and BS channel bandwidth $\leq 20\text{MHz}$ , for which the subcarrier spacing of the interfering signal should be 30 kHz. + +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 a BS 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 NR interfering signal in table 7.7.5-2 or 7.7.5-4. The interfering signal offset is defined relative to the sub-block edges inside the sub-block gap. + +For a *multi-band connectors*, 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 NR interfering signal centre frequency offset from the Base Station RF Bandwidth edge. + +For a *multi-band connectors*, 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 NR interfering signal in tables 7.7.5-2 and 7.7.5-4. The interfering signal offset is defined relative to the Base Station RF Bandwidth edges inside the Inter RF Bandwidth gap. + +**Table 7.7.5-1: General intermodulation requirement** + +| Base Station type | Wanted Signal mean power (dBm) | Mean power of interfering signals (dBm) | Type of interfering signals | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-----------------------------------------|-----------------------------| +| Wide Area BS | $P_{\text{REFSENS}} + 6$ dB | -52 | See table 7.7.5-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 RAT and the BS class. For NR, $P_{\text{REFSENS}}$ depends also on the BS channel bandwidth as specified in TS 38.104 [2], table 7.2.2-1, 7.2.2-2 and 7.2.2-3. For NB-IoT, $P_{\text{REFSENS}}$ depends also on the sub-carrier spacing as specified in tables 7.2.1-5, 7.2.1-5a and 7.2.1-5c of TS 36.104 [22]. | | | | + +**Table 7.7.5-1a: General intermodulation requirement for band n46, n96 and n102** + +| Base Station Type | Wanted Signal mean power (dBm) | Mean power of interfering signals (dBm) | Type of interfering signals | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-----------------------------------------|-----------------------------| +| Medium Range BS | $P_{\text{REFSENS}} + 6$ dB | -47 | See Table 7.7.5-2a | +| Local Area BS | $P_{\text{REFSENS}} + 6$ dB | -44 | | +| NOTE: $P_{\text{REFSENS}}$ depends on the RAT and the BS class. For NR, $P_{\text{REFSENS}}$ depends also on the BS channel bandwidth , see clause 7.2.5 of TS 38.104[2]. | | | | + +**Table 7.7.5-2: Interfering signals for intermodulation requirement** + +| BS 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 (Note 3) | +|--------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|--------------------------------------------| +| 5 | $\pm 7.5$ | CW | +| | $\pm 17.5$ | 5 MHz DFT-s-OFDM NR signal, (Note 1) | +| 10 | $\pm 7.465$ | CW | +| | $\pm 17.5$ | 5 MHz DFT-s-OFDM NR signal, (Note 1) | +| 15 | $\pm 7.43$ | CW | +| | $\pm 17.5$ | 5 MHz DFT-s-OFDM NR signal, (Note 1) | +| 20 | $\pm 7.395$ | CW | +| | $\pm 17.5$ | 5 MHz DFT-s-OFDM NR signal, (Note 1) | +| 25 | $\pm 7.465$ | CW | +| | $\pm 25$ | 20 MHz DFT-s-OFDM NR signal, (Note 2) | +| 30 | $\pm 7.43$ | CW | +| | $\pm 25$ | 20 MHz DFT-s-OFDM NR signal, (Note 2) | +| 35 | $\pm 7.44$ | CW | +| | $\pm 25$ | 20 MHz DFT-s-OFDM NR signal, (Note 2) | +| 40 | $\pm 7.45$ | CW | +| | $\pm 25$ | 20 MHz DFT-s-OFDM NR signal, (Note 2) | +| 45 | $\pm 7.37$ | CW | +| | $\pm 25$ | 20 MHz DFT-s-OFDM NR signal, (Note 2) | +| 50 | $\pm 7.35$ | CW | +| | $\pm 25$ | 20 MHz DFT-s-OFDM NR signal, (Note 2) | +| 60 | $\pm 7.49$ | CW | +| | $\pm 25$ | 20 MHz DFT-s-OFDM NR signal, (Note 2) | +| 70 | $\pm 7.42$ | CW | +| | $\pm 25$ | 20 MHz DFT-s-OFDM NR signal, (Note 2) | +| 80 | $\pm 7.44$ | CW | +| | $\pm 25$ | 20 MHz DFT-s-OFDM NR signal, (Note 2) | +| 90 | $\pm 7.46$ | CW | +| | $\pm 25$ | 20 MHz DFT-s-OFDM NR signal, (Note 2) | +| 100 | $\pm 7.48$ | CW | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|---------------------------------------| +| | ±25 | 20 MHz DFT-s-OFDM NR signal, (Note 2) | +| NOTE 1: For the 15 kHz subcarrier spacing, the number of RB is 25. For the 30 kHz subcarrier spacing, the number of RB is 10. | | | +| NOTE 2: For the 15 kHz subcarrier spacing, the number of RB is 100. For the 30 kHz subcarrier spacing, the number of RB is 50. For the 60 kHz subcarrier spacing, the number of RB is 24. | | | +| NOTE 3: The RBs shall be placed adjacent to the transmission bandwidth configuration edge which is closer to the Base Station RF Bandwidth edge. | | | + +**Table 7.7.5-2a: Interfering signals for intermodulation requirement for band n46, n96 and n102** + +| BS 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 (Note 2) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|--------------------------------------------| +| 10 | ±7.57 | CW (Note 3) | +| | ±25 | 20 MHz DFT-s-OFDM NR signal (Note 1, 3) | +| 20 | ±7.50 | CW | +| | ±25 | 20 MHz DFT-s-OFDM NR signal (Note 1) | +| 40 | ±7.45 | CW | +| | ±25 | 20 MHz DFT-s-OFDM NR signal (Note 1) | +| 60 | ±7.49 | CW | +| | ±25 | 20 MHz DFT-s-OFDM NR signal (Note 1) | +| 80 | ±7.44 | CW | +| | ±25 | 20 MHz DFT-s-OFDM NR signal (Note 1) | +| NOTE 1: Number of RBs is 100 for 15 kHz subcarrier spacing and 50 for 30 kHz subcarrier spacing. | | | +| NOTE 2: The RBs shall be placed adjacent to the transmission bandwidth configuration edge which is closer to the Base Station RF Bandwidth edge. | | | +| NOTE 3: This type of interfering signal is only applied for band n46, n96 and n102. | | | + +**Table 7.7.5-3: Narrowband intermodulation performance requirement in FR1** + +| BS type | Wanted signal mean power (dBm)
(Note 1) | Mean power of interfering signals (dBm) | Type of interfering signal | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|-----------------------------------------|----------------------------| +| Wide Area BS | $P_{\text{REFSENS}} + 6$ dB | -52 | See table 7.7.5-4 | +| Medium Range BS | $P_{\text{REFSENS}} + 6$ dB | -47 | | +| Local Area BS | $P_{\text{REFSENS}} + 6$ dB | -44 | | +|

NOTE 1: P_{\text{REFSENS}} depends on the RAT. For NR, P_{\text{REFSENS}} depends also on the BS channel bandwidth as specified in TS 38.104 [2], table 7.2.2-1, 7.2.2-2 and 7.2.2-3. For NB-IoT, P_{\text{REFSENS}} depends also on the sub-carrier spacing as specified in tables 7.2.1-5, 7.2.1-5a and 7.2.1-5c of TS 36.104 [22].

NOTE 2: For NB-IoT, the requirement shall apply only for a FRC A1-3 of TS 36.141 [24] mapped to the frequency range at the channel edge adjacent to the interfering signals.

NOTE 3: For NB-IoT, the frequency offset shall be adjusted to accommodate the IMD product to fall in the NB-IoT RB for NB-IoT operation in NR in-band.

NOTE 4: For NB-IoT, 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 NR 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.

| | | | + +**Table 7.7.5-4: Interfering signals for narrowband intermodulation requirement in FR1** + +| BS channel bandwidth of the lowest/highest carrier received (MHz) | Interfering RB centre frequency offset from the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap (kHz) (Note 3) | Type of interfering signals | +|--------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------| +| 5 | ±360 | CW | +| | ±1420 | 5 MHz DFT-s-OFDM NR signal, 1 RB (Note 1) | +| 10 | ±370 | CW | +| | ±1960 | 5 MHz DFT-s-OFDM NR signal, 1 RB (Note 1) | +| 15 (Note 2) | ±380 | CW | +| | ±1960 | 5 MHz DFT-s-OFDM NR signal, 1 RB (Note 1) | +| 20 (Note 2) | ±390 | CW | +| | ±2320 | 5 MHz DFT-s-OFDM NR signal, 1 RB (Note 1) | +| 25 (Note 2) | ±325 | CW | +| | ±2350 | 20 MHz DFT-s-OFDM NR signal, 1 RB (Note 1) | +| 30 (Note 2) | ±335 | CW | +| | ±2350 | 20 MHz DFT-s-OFDM NR signal, 1 RB (Note 1) | +| 35 (Note 2) | ±345 | CW | +| | ±2350 | 20 MHz DFT-s-OFDM NR signal, 1 RB (Note 1) | +| 40 (Note 2) | ±355 | CW | +| | ±2710 | 20 MHz DFT-s-OFDM NR signal, 1 RB (Note 1) | +| 45 (Note 2) | ±365 | CW | +| | ±2710 | 20 MHz DFT-s-OFDM NR signal, 1 RB (Note 1) | +| 50 (Note 2) | ±375 | CW | +| | ±2710 | 20 MHz DFT-s-OFDM NR signal, 1 RB (Note 1) | +| 60 (Note 2) | ±395 | CW | +| | ±2710 | 20 MHz DFT-s-OFDM NR signal, 1 RB (Note 1) | +| 70 (Note 2) | ±415 | CW | +| | ±2710 | 20 MHz DFT-s-OFDM NR signal, 1 RB (Note 1) | +| 80 (Note 2) | ±435 | CW | +| | ±2710 | 20 MHz DFT-s-OFDM NR signal, 1 RB (Note 1) | +| 90 (Note 2) | ±365 | CW | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|--------------------------------------------| +| | ±2530 | 20 MHz DFT-s-OFDM NR signal, 1 RB (Note 1) | +| 100 (Note 2) | ±385 | CW | +| | ±2530 | 20 MHz DFT-s-OFDM NR signal, 1 RB (Note 1) | +| Note 1: Interfering signal consisting of one resource block positioned at the stated offset, the BS channel bandwidth of the interfering signal is located adjacently to the lower/upper Base Station RF Bandwidth edge or sub-block edge inside a sub-block gap. | | | +| Note 2: This requirement shall apply only for a G-FRC mapped to the frequency range at the channel edge adjacent to the interfering signals. | | | +| Note 3: The centre of the interfering RB refers to the frequency location between the two central subcarriers. | | | + +### 7.7.5.1 Additional narrowband intermodulation requirement for Band n100 + +The following requirement shall apply to BS operating in Band n100 in CEPT countries. For the wanted and interfering signals coupled to the *antenna connector*, using the parameters in table 7.7.5.1-1 and 7.7.5.1-2, the throughput shall be $\geq 95$ % of the *maximum throughput* of the reference measurement channel. + +**Table 7.7.5.1-1: Additional narrowband intermodulation requirement for n100** + +| Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signals | +|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|-----------------------------| +| $P_{\text{REFSENS}} + 6\text{dB}$ | Wide Area BS: -39 (Note 2) | See Table 7.7.5.1-2 | +| NOTE 1: $P_{\text{REFSENS}}$ depends on the BS channel bandwidth as specified in clause 7.2.2 of TS 38.104[2]. | | | +| NOTE 2: Interfering signal mean power level was derived considering an interfering signal with 10% duty cycle. For more details, refer to TR 38.853. | | | + +**Table 7.7.5.1-2: Interferer frequency offset for additional narrowband intermodulation requirement for n100** + +| BS channel bandwidth of the lowest carrier received (MHz) | Interfering RB centre frequency offset from the lower Base Station RF Bandwidth edge (kHz) (Note 3) | Type of interfering signal | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|-------------------------------------------------------| +| 5 | -360 | CW | +| | -1420 | 5 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 1 RB (Note 1) | +| NOTE 1: Interfering signal consisting of one resource block positioned at the stated offset, the BS channel bandwidth of the interfering signal is located adjacently to the lower Base Station RF Bandwidth edge . | | | +| NOTE 2: This requirement shall apply only for a G-FRC mapped to the frequency range at the channel edge adjacent to the interfering signals. | | | +| NOTE 3: The centre of the interfering RB refers to the frequency location between the two central subcarriers. | | | + +## 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 at the *antenna connector* for *BS type 1-C* or *TAB connector* for *BS type 1-H* 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 interfering signal shall be an NR signal which is time aligned with the wanted signal. + +## 7.8.2 Minimum requirement + +The minimum requirements for *BS type 1-C* and *BS type 1-H* are in TS 38.104 [2], clause 7.8.2. + +## 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 test + +### 7.8.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +### 7.8.4.2 Procedure + +The minimum requirement is applied to all connectors under test. + +For *BS type 1-H* the procedure is repeated until all *TAB connectors* necessary to demonstrate conformance have been tested; see clause 7.1. + +- 1) Set the signal generator for the wanted signal to transmit as specified from table 7.8.5-1 to 7.8.5-3, as well as table 7.8.5-1a to 7.8.5-3a for a BS declared to be capable of NB-IoT operation in NR in-band (D.41). +- 2) Set the signal generator for the interfering signal to transmit at the frequency offset and as specified from table 7.8.5-1 to 7.8.5-3, as well as table 7.8.5-1a to 7.8.5-3a for a BS declared to be capable of NB-IoT operation in NR in-band (D.41). +- 3) Measure the throughput according to annex A.1, as well as annex A.14 of TS 36.141 [24] for a BS declared to be capable of NB-IoT operation in NR in-band (D.41). + +In addition, for a *multi-band connector*, the following steps shall apply: + +- 4) For *multi-band connector* 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 *BS type 1-C* and *BS type 1-H*, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.1 with parameters specified in table 7.8.5-1 for Wide Area BS except for band n104, in table 7.8.5-1b for Wide Area BS for band n104, in table 7.8.5-2 for Medium Range BS except for band n46, n96, n102 and n104, in table 7.8.5-2b for Medium Range BS for band n46, in table 7.8.5-2c for Medium Range BS for band n96 and n102, in table 7.8.5-2d for Medium Range BS for band n104, in table 7.8.5-3 for Local Area BS except for band n46, n96, n102 and n104, in table 7.8.5-3b for Local Area BS for band n46, in table 7.8.5-3c for Local Area BS for band n96 and n102, and in table 7.8.5-3d for Local Area BS for band 104. The characteristics of the interfering signal is further specified in annex E. + +For NB-IoT operation in NR in-band, the throughput shall be $\geq 95\%$ of the maximum throughput of the NB-IoT reference measurement channel as specified in Annex A of TS 36.141 [24] with parameters specified in table 7.8.5-1a for Wide Area BS, in table 7.8.5-2a for Medium Range BS and in table 7.8.5-3a for Local Area BS. + +**Table 7.8.5-1: Wide Area BS in-channel selectivity** + +| 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 ≤ 3.0 GHz | 3.0 GHz < f ≤ 4.2 GHz | 4.2 GHz < f ≤ 6.0 GHz | | | +| 5 | 15 | G-FR1-A1-7 | -99.2 | -98.8 | -98.5 | -81.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10, 15, 20, 25, 30, 35 | 15 | G-FR1-A1-1 | -97.3 | -96.9 | -96.6 | -77.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 45, 50 | 15 | G-FR1-A1-4 | -90.9 | -90.5 | -90.2 | -71.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 5 | 30 | G-FR1-A1-8 | -99.9 | -99.5 | -99.2 | -81.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 5 RBs | +| 10, 15, 20, 25, 30, 35 | 30 | G-FR1-A1-2 | -97.4 | -97 | -96.7 | -78.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -91.2 | -90.8 | -90.5 | -71.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 10, 15, 20, 25, 30, 35 | 60 | G-FR1-A1-9 | -96.8 | -96.4 | -96.1 | -78.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -91.3 | -90.9 | -90.6 | -71.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | +| 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 [2]. The aggregated wanted and interferer signal shall be centred in the BS channel bandwidth of the wanted signal. | | | | | | | | + +**Table 7.8.5-1a: Wide Area BS in-channel selectivity for NB-IoT operation in NR in-band** + +| BS channel bandwidth (MHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / BWConfig | Type of interfering signal | +|-----------------------------------|-------------------------------------------|---------------------------------------|------------------------------------------------------------------|-------------------------------------------| +| 5 | FRC A14-1 in Annex A.14 in TS 36.141 [24] | -122.9 | -81.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10, 15, 20, 25, 30, 35 | | | -77.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 45, 50 | | | -71.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 5 | FRC A14-2 in Annex A.14 in TS 36.141 [24] | -128.8 | -81.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10, 15, 20, 25, 30, 35 | | | -77.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 45, 50 | | | -71.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | + +NOTE: Interfering signal is placed in one side of the $F_c$ , while the NB-IoT PRB is placed on the other side. Both interfering signal and NB-IoT PRB are placed at the middle of the available PRB locations. The wanted NB-IoT tone is placed at the centre of this NB-IoT PRB. + +**Table 7.8.5-1b: Wide Area BS in-channel selectivity for band n104** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|--------------------------------------------|-------------------------------------------| +| 20, 30 | 15 | G-FR1-A1-1 | -95.2 | -76.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 50 | 15 | G-FR1-A1-4 | -88.8 | -70.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 20, 30 | 30 | G-FR1-A1-2 | -95.3 | -77.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -89.1 | -70.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 20, 30 | 60 | G-FR1-A1-9 | -94.7 | -77.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -89.2 | -70.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | + +NOTE 1: 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. The aggregated wanted and interferer signal shall be centred in the *BS channel bandwidth* of the wanted signal. + +**Table 7.8.5-2: Medium Range BS in-channel selectivity** + +| 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.5 | -76.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10, 15, 20, 25, 30, 35 | 15 | G-FR1-A1-1 | -92.3 | -91.9 | -91.6 | -72.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 45, 50 | 15 | G-FR1-A1-4 | -85.9 | -85.5 | -85.2 | -66.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 5 | 30 | G-FR1-A1-8 | -94.9 | -94.5 | -94.2 | -76.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 5 RBs | +| 10, 15, 20, 25, 30, 35 | 30 | G-FR1-A1-2 | -92.4 | -92 | -91.7 | -73.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -86.2 | -85.8 | -85.5 | -66.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 10, 15, 20, 25, 30, 35 | 60 | G-FR1-A1-9 | -91.8 | -91.4 | -91.1 | -73.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -86.3 | -85.9 | -85.6 | -66.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | + +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 [2]. The aggregated wanted and interferer signal shall be centred in the BS channel bandwidth of the wanted signal. + +**Table 7.8.5-2a: Medium Range BS in-channel selectivity for NB-IoT operation in NR in-band** + +| BS channel bandwidth (MHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / $BW_{\text{Config}}$ | Type of interfering signal | +|----------------------------|-------------------------------------------|--------------------------------|------------------------------------------------------------|-------------------------------------------| +| 5 | FRC A14-1 in Annex A.14 in TS 36.141 [24] | -117.9 | -76.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10, 15, 20, 25, 30, 35 | | | -72.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 45, 50 | | | -66.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 5 | FRC A14-2 in Annex A.14 in TS 36.141 [24] | -123.8 | -76.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10, 15, 20, 25, 30, 35 | | | -72.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 45, 50 | | | -66.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | + +NOTE: Interfering signal is placed in one side of the $F_c$ , while the NB-IoT PRB is placed on the other side. Both interfering signal and NB-IoT PRB are placed at the middle of the available PRB locations. The wanted NB-IoT tone is placed at the centre of this NB-IoT PRB. + +**Table 7.8.5-2b: Medium Range BS in-channel selectivity for band n46** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|----------------------------|--------------------------|-------------------------------|--------------------------------|-------------------------------------|------------------------------------------| +| 10 | 15 | G-FR1-A1-12 | -97.5 | -79.5 | CP-OFDM NR signal, 15 kHz SCS, 10 RBs | +| | 30 | G-FR1-A1-13 | -95.2 | -77.4 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-9 | -90.7 | -73.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 20 | 15 | G-FR1-A1-14 | -94.6 | -76.4 | CP-OFDM NR signal, 15 kHz SCS, 10 RBs | +| | 30 | G-FR1-A1-15 | -91.6 | -73.4 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-9 | -90.7 | -73.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40 | 15 | G-FR1-A1-16 | -91.5 | -73.2 | CP-OFDM NR signal, 15 kHz SCS, 20 RBs | +| | 30 | G-FR1-A1-17 | -88.5 | -70.2 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-6 | -85.2 | -66.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | +| 60 | 30 | G-FR1-A1-18 | -86.9 | -68.4 | CP-OFDM NR signal, 30 kHz SCS, 20 RBs | +| | 60 | G-FR1-A1-6 | -85.2 | -66.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | +| 80 | 30 | G-FR1-A1-19 | -85.6 | -67.1 | CP-OFDM NR signal, 30 kHz SCS, 20 RBs | +| | 60 | G-FR1-A1-6 | -85.2 | -66.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | + +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. The aggregated wanted and interferer signal shall be centred in the BS channel bandwidth of the wanted signal. + +**Table 7.8.5-2c: Medium Range BS in-channel selectivity for band n96 and n102** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|--------------------------------------------|------------------------------------------| +| 20 | 15 | G-FR1-A1-14 | -93.6 | -75.4 | CP-OFDM NR signal, 15 kHz SCS, 10 RBs | +| | 30 | G-FR1-A1-15 | -90.6 | -72.4 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-9 | -89.7 | -72.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40 | 15 | G-FR1-A1-16 | -90.5 | -72.2 | CP-OFDM NR signal, 15 kHz SCS, 20 RBs | +| | 30 | G-FR1-A1-17 | -87.5 | -69.2 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-6 | -84.2 | -65.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | +| 60 | 30 | G-FR1-A1-18 | -85.9 | -67.4 | CP-OFDM NR signal, 30 kHz SCS, 20 RBs | +| | 60 | G-FR1-A1-6 | -84.2 | -65.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | +| 80 | 30 | G-FR1-A1-19 | -84.6 | -66.1 | CP-OFDM NR signal, 30 kHz SCS, 20 RBs | +| | 60 | G-FR1-A1-6 | -84.2 | -65.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | + +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. The aggregated wanted and interferer signal shall be centred in the BS channel bandwidth of the wanted signal. + +**Table 7.8.5-2d: Medium Range BS in-channel selectivity for band n104** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|--------------------------------------------|-------------------------------------------| +| 20, 30 | 15 | G-FR1-A1-1 | -90.2 | -71.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 50 | 15 | G-FR1-A1-4 | -83.8 | -65.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 20, 30 | 30 | G-FR1-A1-2 | -90.3 | -72.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -84.1 | -65.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 20, 30 | 60 | G-FR1-A1-9 | -89.7 | -72.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -84.2 | -65.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | + +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. The aggregated wanted and interferer signal shall be centred in the *BS channel bandwidth* of the wanted signal. + +**Table 7.8.5-3: Local area BS in-channel selectivity** + +| 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.5 | -73.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10, 15, 20, 25, 30, 35 | 15 | G-FR1-A1-1 | -89.3 | -88.9 | -88.6 | -69.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RB | +| 40, 45, 50 | 15 | G-FR1-A1-4 | -82.9 | -82.5 | -82.2 | -63.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 5 | 30 | G-FR1-A1-8 | -91.9 | -91.5 | -91.2 | -73.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 5 RBs | +| 10, 15, 20, 25, 30, 35 | 30 | G-FR1-A1-2 | -89.4 | -89 | -88.7 | -70.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -83.2 | -82.8 | -82.5 | -63.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 10, 15, 20, 25, 30, 35 | 60 | G-FR1-A1-9 | -88.8 | -88.4 | -88.1 | -70.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -83.3 | -82.9 | -82.6 | -63.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | +| 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 [2]. The aggregated wanted and interferer signal shall be centred in the BS channel bandwidth of the wanted signal. | | | | | | | | + +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 [2]. The aggregated wanted and interferer signal shall be centred in the BS channel bandwidth of the wanted signal. + +**Table 7.8.5-3a: Local Area BS in-channel selectivity for NB-IoT operation in NR in-band** + +| BS channel bandwidth (MHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / BWConfig | Type of interfering signal | +|-----------------------------------|-------------------------------------------|---------------------------------------|------------------------------------------------------------------|-------------------------------------------| +| 5 | FRC A14-1 in Annex A.14 in TS 36.104 [13] | -114.9 | -73.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10, 15, 20, 25, 30, 35 | | | -69.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 45, 50 | | | -63.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 5 | FRC A14-2 in Annex A.14 in TS 36.104 [13] | -120.8 | -73.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 10 RBs | +| 10, 15, 20, 25, 30, 35 | | | -69.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 45, 50 | | | -63.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | + +NOTE: Interfering signal is placed in one side of the Fc, while the NB-IoT PRB is placed on the other side. Both interfering signal and NB-IoT PRB are placed at the middle of the available PRB locations. The wanted NB-IoT tone is placed at the centre of this NB-IoT PRB. + +**Table 7.8.5-3b: Local Area BS in-channel selectivity for band n46** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|----------------------------|--------------------------|-------------------------------|--------------------------------|-------------------------------------|------------------------------------------| +| 10 | 15 | G-FR1-A1-12 | -94.5 | -76.5 | CP-OFDM NR signal, 15 kHz SCS, 10 RBs | +| | 30 | G-FR1-A1-13 | -92.2 | -74.4 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-9 | -87.7 | -70.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 20 | 15 | G-FR1-A1-14 | -91.6 | -73.4 | CP-OFDM NR signal, 15 kHz SCS, 10 RBs | +| | 30 | G-FR1-A1-15 | -88.6 | -70.4 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-9 | -87.7 | -70.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40 | 15 | G-FR1-A1-16 | -88.5 | -70.2 | CP-OFDM NR signal, 15 kHz SCS, 20 RBs | +| | 30 | G-FR1-A1-17 | -85.5 | -67.2 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-6 | -82.2 | -63.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | +| 60 | 30 | G-FR1-A1-18 | -83.9 | -65.4 | CP-OFDM NR signal, 30 kHz SCS, 20 RBs | +| | 60 | G-FR1-A1-6 | -82.2 | -63.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | +| 80 | 30 | G-FR1-A1-19 | -82.6 | -64.1 | CP-OFDM NR signal, 30 kHz SCS, 20 RBs | +| | 60 | G-FR1-A1-6 | -82.2 | -63.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | + +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. The aggregated wanted and interferer signal shall be centred in the BS channel bandwidth of the wanted signal. + +**Table 7.8.5-3c: Local Area BS in-channel selectivity for band n96 and n102** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|--------------------------------------------|------------------------------------------| +| 20 | 15 | G-FR1-A1-14 | -90.6 | -72.4 | CP-OFDM NR signal, 15 kHz SCS, 10 RBs | +| | 30 | G-FR1-A1-15 | -87.6 | -69.4 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-9 | -86.7 | -69.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40 | 15 | G-FR1-A1-16 | -87.5 | -69.2 | CP-OFDM NR signal, 15 kHz SCS, 20 RBs | +| | 30 | G-FR1-A1-17 | -84.5 | -66.2 | CP-OFDM NR signal, 30 kHz SCS, 10 RBs | +| | 60 | G-FR1-A1-6 | -81.2 | -62.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | +| 60 | 30 | G-FR1-A1-18 | -82.9 | -64.4 | CP-OFDM NR signal, 30 kHz SCS, 20 RBs | +| | 60 | G-FR1-A1-6 | -81.2 | -62.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | +| 80 | 30 | G-FR1-A1-19 | -81.6 | -63.1 | CP-OFDM NR signal, 30 kHz SCS, 20 RBs | +| | 60 | G-FR1-A1-6 | -81.2 | -62.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | + +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. The aggregated wanted and interferer signal shall be centred in the BS channel bandwidth of the wanted signal. + +**Table 7.8.5-3d: Local area BS in-channel selectivity for band n104** + +| BS channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|-----------------------------------|---------------------------------|--------------------------------------|---------------------------------------|--------------------------------------------|-------------------------------------------| +| 20, 30 | 15 | G-FR1-A1-1 | -87.2 | -68.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 50 | 15 | G-FR1-A1-4 | -80.8 | -62.4 | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 20, 30 | 30 | G-FR1-A1-2 | -87.3 | -69.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -81.1 | -62.4 | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 20, 30 | 60 | G-FR1-A1-9 | -86.7 | -69.4 | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -81.2 | -62.6 | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | + +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. The aggregated wanted and interferer signal shall be centred in the *BS channel bandwidth* of the wanted signal. + +## 8 Conducted performance characteristics + +### 8.1 General + +#### 8.1.1 Scope and definitions + +Conducted performance requirements specify the ability of the *BS type 1-C* or *BS type 1-H* to correctly demodulate signals in various conditions and configurations. Conducted performance requirements are specified at the *antenna connector(s)* (for *BS type 1-C*) and at the *TAB connector(s)* (for *BS type 1-H*). + +Conducted performance requirements for the BS are specified for the fixed reference channels and the propagation conditions defined in TS 38.104 [2] annex A and annex H, respectively. The requirements only apply to those FRCs that are supported by the BS. + +Unless stated otherwise, performance requirements apply for a single carrier only. Performance requirements for a BS supporting CA 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 *antenna connectors* (for *BS type 1-C*) or *TAB connectors* (for *BS type 1-H*) in the *operating band* turned ON. + +NOTE: In normal operating conditions *antenna connectors* (for *BS type 1-C*) or *TAB connectors* (for *BS type 1-H*) 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. + +In tests performed with signal generators a synchronization signal may be provided between the BS and the signal generator, to enable correct timing of the wanted signal. + +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 single *antenna connector* (for BS type 1-C) or on a single *TAB connector* (for BS type 1-H). + +N is the noise energy in a bandwidth corresponding to the transmission bandwidth over the same duration where signal energy exists. + +## 8.1.2 Applicability rule + +### 8.1.2.0 General + +Unless otherwise stated, for a BS supporting more than 8 antenna connectors (for BS type 1-C) or *TAB connectors* (for BS type 1-H) (see D.37 in table 4.6-1), the performance requirement tests for 8 RX antennas shall apply, and the specific connectors used for testing are based on manufacturer declaration. + +Unless otherwise stated, for a BS supporting different numbers of antenna connectors (for BS type 1-C) or *TAB connectors* (for BS type 1-H) (see D.37 in table 4.6-1), the tests with low MIMO correlation level shall apply only for the lowest and highest numbers of supported connectors, and the specific connectors used for testing are based on manufacturer declaration. + +### 8.1.2.1 Applicability of PUSCH performance requirements + +#### 8.1.2.1.1 Applicability of requirements for different subcarrier spacings + +Unless otherwise stated, PUSCH requirement tests shall apply only for each subcarrier spacing declared to be supported (see D.14 in table 4.6-1). + +Unless otherwise stated, PUSCH requirement tests with 30% of maximum throughput shall apply only for the lowest subcarrier spacing declared to be supported (see D.14 in table 4.6-1) for each frequency range. + +#### 8.1.2.1.2 Applicability of requirements for different channel bandwidths + +For each subcarrier spacing declared to be supported, the test requirements for a specific channel bandwidth shall apply only if the BS supports it (see D.14 in table 4.6-1). + +Unless otherwise stated, for each subcarrier spacing declared to be supported, the tests shall be done only for the widest supported channel bandwidth. If performance requirement is not specified for this widest supported channel bandwidth, the tests shall be done by using performance requirement for the closest channel bandwidth lower than this widest supported bandwidth; the tested PRBs shall then be centered in this widest supported channel bandwidth. + +#### 8.1.2.1.3 Applicability of requirements for different configurations + +Unless otherwise stated, PUSCH requirement tests shall apply only for the mapping type declared to be supported (see D.100 in table 4.6-1). If both mapping type A and type B are declared to be supported, the tests shall be done for either type A or type B; the same chosen mapping type shall then be used for all tests except the requirement for PUSCH mapping Type B with 2 symbol length allocated. + +#### 8.1.2.1.4 Applicability of requirements for uplink carrier aggregation + +The tests for uplink carrier aggregation shall be carried out according to the declaration (see D.107 in table 4.6-1). + +Unless otherwise stated, the tests for uplink carrier aggregation shall apply only for PUSCH with transform precoding disabled, and shall be conducted on per component carrier basis. + +#### 8.1.2.1.5 Applicability of requirements for TDD with different UL-DL patterns + +Unless otherwise stated, for each subcarrier spacing declared to be supported, if BS supports multiple TDD UL-DL patterns, only one of the supported TDD UL-DL patterns shall be used for all tests. + +Note: For PUSCH Performance test cases, FRCs are not expected to be defined for the special slots, unless otherwise stated. + +#### 8.1.2.1.6 Applicability of UL timing adjustment requirements for different scenarios + +Unless otherwise stated, the tests for UL timing adjustment for scenario Y and scenario Z shall apply only if high speed train is declared to be supported (see D.109 in table 4.6-1). A BS that passes the tests for scenario Y or scenario Z, can also consider the tests for scenario X passed. + +#### 8.1.2.1.7 Applicability of 2-step RA type requirements for different subcarrier spacings + +In 2-step RA type requirements, unless otherwise stated, MsgA PUSCH tests shall be done for a BS declaring support of 2-step RA (see D.114 in table 4.6-1) only for one (freely selected) subcarrier spacing declared to be supported (see D.14 in table 4.6-1). + +#### 8.1.2.1.8 Applicability of PUSCH with 0.001% BLER requirements + +Unless otherwise stated, PUSCH with 0.001% BLER requirements shall apply only for a BS declaring support of low spectral efficiency MCS index table 3 (see D.121 in table 4.6-1). + +#### 8.1.2.1.9 Applicability of PUSCH repetition type A requirements + +Unless otherwise stated, PUSCH repetition type A requirements shall apply only for a BS declaring support of low spectral efficiency MCS index table 3 and PUSCH repetition type A (see D.121 and D.122 in table 4.6-1). + +### 8.1.2.2 Applicability of PUCCH performance requirements + +#### 8.1.2.2.1 Applicability of requirements for different formats + +Unless otherwise stated, PUCCH requirement tests shall apply only for each PUCCH format declared to be supported (see D.102 in table 4.6-1). + +#### 8.1.2.2.2 Applicability of requirements for different subcarrier spacings + +Unless otherwise stated, PUCCH requirement tests shall apply only for each subcarrier spacing declared to be supported (see D.14 in table 4.6-1). + +#### 8.1.2.2.3 Applicability of requirements for different channel bandwidths + +For each subcarrier spacing declared to be supported by the BS, the test requirements for a specific channel bandwidth shall apply only if the BS supports it (see D.14 in table 4.6-1). + +Unless otherwise stated, for each subcarrier spacing declared to be supported, the tests shall be done only for the widest supported channel bandwidth. If performance requirement is not specified for this widest supported channel bandwidth, the tests shall be done by using performance requirement for the closest channel bandwidth lower than this widest supported bandwidth; the tested PRBs shall then be centered in this widest supported channel bandwidth. + +#### 8.1.2.2.4 Applicability of requirements for different configurations + +Unless otherwise stated, PUCCH format 3 requirement tests shall apply only for the additional DM-RS configuration declared to be supported (see D.104 in table 4.6-1). If both options (without and with additional DM-RS) are declared to be supported, the tests shall be done for either without or with additional DM-RS; the same chosen option shall then be used for all tests. + +Unless otherwise stated, PUCCH format 4 requirement tests shall apply only for the additional DM-RS configuration declared to be supported (see D.105 in table 4.6-1). If both options (without and with additional DM-RS) are declared to be supported, the tests shall be done for either without or with additional DM-RS; the same chosen option shall then be used for all tests. + +#### 8.1.2.2.5 Applicability of requirements for multi-slot PUCCH + +Unless otherwise stated, multi-slot PUCCH requirement tests shall apply only if the BS supports it (see D.106 in table 4.6-1). + +#### 8.1.2.2.6 Applicability of requirements for PUCCH sub-slot based repetition + +Unless otherwise stated, PUCCH sub-slot based repetition requirement tests shall apply only if the BS supports it (see D.116 in table 4.6-1). + +### 8.1.2.3 Applicability of PRACH performance requirements + +#### 8.1.2.3.1 Applicability of requirements for different formats + +Unless otherwise stated, PRACH requirement tests shall apply only for each PRACH format declared to be supported (see D.103 in table 4.6-1). + +Unless otherwise stated, PRACH requirement tests for high speed train shall apply only for each PRACH formats declared to be supported (see D.110 in table 4.6-1). + +#### 8.1.2.3.2 Applicability of requirements for different subcarrier spacings + +Unless otherwise stated, for each PRACH format with short sequence declared to be supported, for each FR, the tests shall apply only for the smallest supported subcarrier spacing in the FR (see D.103 in table 4.6-1). + +#### 8.1.2.3.3 Applicability of requirements for different channel bandwidths + +Unless otherwise stated, for the subcarrier spacing to be tested, the test requirements shall apply only for anyone channel bandwidth declared to be supported (see D.14 in table 4.6-1). + +#### 8.1.2.3.4 Applicability of requirements for different restricted set types of long PRACH format 0 + +Unless otherwise stated, PRACH requirement tests for long PRACH preamble format 0 with restricted set Type A and B shall apply only for the restricted set type declared to be supported (see D.110 in table 4.6-1). If both restricted set + +type A and type B are declared to be supported, the tests shall be done for type B; the same chosen mapping type shall then be used for all tests. + +#### 8.1.2.4 Applicability of PUSCH for high speed train performance requirements + +##### 8.1.2.4.1 Applicability of requirements for different speeds + +Unless otherwise stated, a BS that declares to support 500km/h (see D.109 in table 4.6-1) and passes the tests for 500km/h, can also consider the tests for 350km/h as passed. + +##### 8.1.2.4.2 Applicability of requirements for 1T1R + +In high speed train requirements, unless otherwise stated, for a BS supporting different numbers of antenna connectors (for BS type 1-C) or TAB connectors (for BS type 1-H) (see D.37 in table 4.6-1), if the BS supports 1RX, the tests with low MIMO correlation level shall apply only for either one connector or the second lowest number of supported connectors, in addition to the highest numbers of supported connectors, and the specific connectors used for testing are based on manufacturer declaration. + +If the BS doesn't support 1RX, the tests with low MIMO correlation level shall apply only for the lowest and highest numbers of supported connectors, and the specific connectors used for testing are based on manufacturer declaration. + +Note: The highest number of connectors can simultaneously be second lowest number. + +#### 8.1.2.5 Applicability of interlaced PUSCH performance requirements + +##### 8.1.2.5.1 General applicability of interlaced PUSCH performance requirements + +Interlaced PUSCH requirement tests shall apply only for a BS declaring support of interlaced formats (see D.111 in table 4.6-1). + +##### 8.1.2.5.2 Applicability of requirements for different subcarrier spacings + +Unless otherwise stated, PUSCH requirement tests shall apply only for each subcarrier spacing declared to be supported (see D.14 in table 4.6-1). + +Unless otherwise stated, for each subcarrier-spacing declared to be supported for interlaced PUSCH, the tests shall apply only for the supported subcarrier spacing. If both 15kHz and 30kHz SCS are declared to be supported, the tests shall be done for 30kHz SCS (see D.14 in table 4.6-1). + +##### 8.1.2.5.3 Applicability of requirements for different channel bandwidths + +For each subcarrier spacing declared to be supported, the tests for a specific channel bandwidth shall apply only if the BS supports it (see D.14 in table 4.6-1). + +Unless otherwise stated, for each subcarrier spacing declared to be supported, the tests shall be done only for the widest supported channel bandwidth. If performance requirement is not specified for this widest supported channel bandwidth, the tests shall be done by using performance requirement defined for 20 MHz channel bandwidth. For 15kHz subcarrier spacing, the tested RB's are uniformly spaced over the channel bandwidth at RB index {110, 120, ..., 210}. For 30kHz subcarrier spacing, the tested RB's are uniformly spaced over the channel bandwidth at RB index {55, 60, ..., 105}. + +##### 8.1.2.5.4 Applicability of requirements for different configurations + +Unless otherwise stated, PUSCH requirement tests shall apply only for the mapping type declared to be supported (see D.100 in table 4.6-1). If both mapping type A and type B are declared to be supported, the tests shall be done for either type A or type B; the same chosen mapping type shall then be used for all tests. + +#### 8.1.2.5.5 Applicability of CG-UCI multiplexed on PUSCH requirements + +Unless otherwise stated, interlaced CG-UCI multiplexed on interlaced PUSCH requirements shall apply only for a BS declaring support of CG-UCI (see D.113 in table 4.6-1). + +#### 8.1.2.6 Applicability of interlaced PUCCH performance requirements + +##### 8.1.2.6.1 General applicability of interlaced PUCCH performance requirements + +Interlaced PUCCH requirement tests shall apply only for a BS declaring support of interlaced formats (see D.111 in table 4.6-1). + +##### 8.1.2.6.2 Applicability of requirements for different formats + +Unless otherwise stated, interlaced PUCCH requirement tests shall apply only for each interlaced PUCCH format declared to be supported (see D.102 in table 4.6-1). + +##### 8.1.2.6.3 Applicability of requirements for different subcarrier spacings + +Unless otherwise stated, PUCCH requirement tests shall apply only for each subcarrier spacing declared to be supported (see D.14 in table 4.6-1). + +##### 8.1.2.6.4 Applicability of requirements for different channel bandwidths + +For each subcarrier spacing declared to be supported by the BS, the tests for a specific channel bandwidth shall apply only if the BS supports it (see D.14 in table 4.6-1). + +Unless otherwise stated, for each subcarrier spacing declared to be supported, the tests shall be done only for the widest supported channel bandwidth. If performance requirement is not specified for this widest supported channel bandwidth, the tests shall be done by using performance requirement defined for 20 MHz channel bandwidth. For 15kHz subcarrier spacing, the tested RB's are uniformly spaced over the channel bandwidth at RB index {110, 120, ..., 210} for PUCCH formats 0, 1, and 2, and {110, 120, ..., 200} for PUCCH format 3. For 30kHz subcarrier spacing, the tested RB's are uniformly spaced over the channel bandwidth at RB index {55, 60, ..., 105} for PUCCH formats 0, 1, and 2, and {55, 60, ..., 100} for PUCCH format 3. + +#### 8.1.2.7 Applicability of performance requirements for PRACH with $L_{RA}=1151$ and $L_{RA}=571$ + +##### 8.1.2.7.1 Applicability of requirements for different formats + +Unless otherwise stated, PRACH requirement tests shall apply only for each PRACH format declared to be supported (see D.112 in table 4.6-1). + +##### 8.1.2.7.2 Applicability of requirements for different subcarrier spacings + +Unless otherwise stated, for each PRACH format with $L_{RA}=1151$ and $L_{RA}=571$ declared to be supported, the tests shall apply only for the supported subcarrier spacing. If both 15kHz and 30kHz SCS are declared to be supported, the tests shall be done for 30kHz SCS (see D.112 in table 4.6-1). + +##### 8.1.2.7.3 Applicability of requirements for different channel bandwidths + +Unless otherwise stated, for the subcarrier spacing to be tested, the tests shall apply only for anyone channel bandwidth not less than 20MHz declared to be supported (see D.14 in table 4.6-1). + +#### 8.1.2.8 Applicability of performance requirements for PUSCH with TB over Multi-Slots + +##### 8.1.2.8.1 Applicability of requirements for different UL-DL patterns + +Unless otherwise stated, PUSCH with TB over Multi-slots requirement tests shall apply only for UL-DL pattern characters declared to be supported (see D.117 and D.118 in table 4.6-1). + +Unless otherwise stated, for each UL-DL pattern character declared to be supported, if BS supports multiple TDD UL-DL patterns, only one of the supported TDD UL-DL patterns shall be used for PUSCH with TB over Multi-slots performance tests. + +#### 8.1.2.9 Applicability of performance requirements for PUSCH with DM-RS bundling + +##### 8.1.2.9.1 Applicability of requirements for TDD with different subcarrier spacings + +Unless otherwise stated, PUSCH with DM-RS bundling requirement tests shall apply only for each subcarrier spacing declared to be supported (see D.119 and D.120 in table 4.6-1). + +##### 8.1.2.9.2 Applicability of requirements for TDD with different UL-DL patterns + +Unless otherwise stated, for each subcarrier spacing declared to be supported, if BS supports multiple TDD UL-DL patterns, only one of the supported TDD UL-DL patterns with more than one consecutive UL slots shall be used for the PUSCH with DM-RS bundling performance tests. + +##### 8.1.2.9.3 Applicability of requirements for different receiver antenna connectors + +Unless otherwise stated, for a BS supporting different numbers of antenna connectors (for *BS type 1-C*) or *TAB connectors* (for *BS type 1-H*) (see D.37 in table 4.6-1), the PUSCH with DM-RS bundling performance tests with low MIMO correlation level shall apply only for the highest numbers of supported connectors, and the specific connectors used for testing are based on manufacturer declaration. + +#### 8.1.2.10 Applicability of performance requirements for PUCCH with DM-RS bundling + +##### 8.1.2.10.1 Applicability of requirements for TDD with different subcarrier spacings + +Unless otherwise stated, PUCCH with DM-RS bundling requirement tests shall apply only for each subcarrier spacing declared to be supported (see D.119 and D.120 in table 4.6-1). + +##### 8.1.2.10.2 Applicability of requirements for TDD with different UL-DL patterns + +Unless otherwise stated, for each subcarrier spacing declared to be supported, if BS supports multiple TDD UL-DL patterns, only one of the supported TDD UL-DL patterns with more than one consecutive UL slots shall be used for the PUCCH with DM-RS bundling performance tests. + +## 8.2 Performance requirements for PUSCH + +### 8.2.1 Performance requirements for PUSCH with transform precoding disabled + +#### 8.2.1.1 Definition and applicability + +The performance requirement of PUSCH is determined by a minimum required throughput for a given SNR. The required throughput is expressed as a fraction of maximum throughput for the FRCs listed in annex A. The performance requirements assume HARQ re-transmissions. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2.1. + +#### 8.2.1.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2] clause 8.2.1. + +#### 8.2.1.3 Test Purpose + +The test shall verify the receiver's ability to achieve throughput under multipath fading propagation conditions for a given SNR. + +#### 8.2.1.4 Method of test + +##### 8.2.1.4.1 Initial Conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: $M$ ; see clause 4.9.1. + +RF channels to be tested for carrier aggregation: $M_{BW\ Channel\ CA}$ ; see clause 4.9.1. + +##### 8.2.1.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type I-C* and *type I-H* respectively. +- 2) Adjust the AWGN generator, according to the channel bandwidth, defined in table 8.2.1.4.2-1. + +**Table 8.2.1.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|----------------------| +| 15 kHz | 5 | -86.5 dBm / 4.5MHz | +| | 10 | -83.3 dBm / 9.36MHz | +| | 20 | -80.2 dBm / 19.08MHz | +| 30 kHz | 10 | -83.6 dBm / 8.64MHz | +| | 20 | -80.4 dBm / 18.36MHz | +| | 40 | -77.2 dBm / 38.16MHz | +| | 100 | -73.1 dBm / 98.28MHz | + +NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 3) The characteristics of the wanted signal shall be configured according to the corresponding UL reference measurement channel defined in annex A and the test parameters in table 8.2.1.4.2-2. + +**Table 8.2.1.4.2-2: Test parameters for testing PUSCH** + +| Parameter | Value | +|--------------------------------------------------------------------------------------------|-------------------------------------------------------------------------| +| Transform precoding | Disabled | +| Default TDD UL-DL pattern (Note 1) | 15 kHz SCS:
3D1S1U, S=10D:2G:2U
30 kHz SCS:
7D1S2U, S=6D:4G:4U | +| HARQ | Maximum number of HARQ transmissions | +| | 4 | +| DM-RS | RV sequence | +| | 0, 2, 3, 1 | +| | DM-RS configuration type | +| | 1 | +| | DM-RS duration | +| | single-symbol DM-RS | +| | Additional DM-RS position | +| | pos1 | +| Time domain resource assignment | Number of DM-RS CDM group(s) without data | +| | 2 | +| | Ratio of PUSCH EPRE to DM-RS EPRE | +| | -3 dB | +| | DM-RS port(s) | +| | {0}, {0, 1} | +| | DM-RS sequence generation | +| | $N_{ID}^0=0, n_{SCID}=0$ | +| Frequency domain resource assignment | PUSCH mapping type | +| | A, B | +| | Start symbol | +| | 0 | +| | Allocation length | +| | 14 | +| TPMI index for 2Tx two layer spatial multiplexing transmission | RB assignment | +| | Full applicable test bandwidth | +| Code block group based PUSCH transmission | Frequency hopping | +| | Disabled | +| | 0 | +| | Disabled | +| NOTE 1: The same requirements are applicable to FDD and TDD with different UL-DL patterns. | | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjust the equipment so that required SNR specified in table 8.2.1.5-1 to 8.2.1.5-18 is achieved at the BS input. +- 6) For each of the reference channels in table 8.2.1.5-1 to 8.2.1.5-18 applicable for the base station, measure the throughput. + +### 8.2.1.5 Test Requirement + +The throughput measured according to clause 8.2.1.4.2 shall not be below the limits for the SNR levels specified in table 8.2.1.5-1 to 8.2.1.5-18. + +**Table 8.2.1.5-1: Test requirements for PUSCH with 70% of maximum throughput, Type A, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-8 | pos1 | -1.7 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-8 | pos1 | 10.7 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-8 | pos1 | 12.9 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-1 | pos1 | 19.7 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-8 | pos1 | -5.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-8 | pos1 | 6.8 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-8 | pos1 | 9.4 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-1 | pos1 | 16.1 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-8 | pos1 | -8.1 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-8 | pos1 | 3.6 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-8 | pos1 | 6.2 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-1 | pos1 | 13.0 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-22 | pos1 | 1.8 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-22 | pos1 | 19.0 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-22 | pos1 | -1.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-22 | pos1 | 11.8 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-22 | pos1 | -4.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-22 | pos1 | 7.6 | + +**Table 8.2.1.5-2: Test requirements for PUSCH with 70% of maximum throughput, Type A, 10 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-9 | pos1 | -1.9 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-9 | pos1 | 10.8 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-9 | pos1 | 12.8 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-2 | pos1 | 20.1 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-9 | pos1 | -5.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-9 | pos1 | 6.9 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-9 | pos1 | 9.2 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-2 | pos1 | 16.5 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-9 | pos1 | -8.1 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-9 | pos1 | 3.7 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-9 | pos1 | 6.1 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-2 | pos1 | 13.2 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-23 | pos1 | 2.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-23 | pos1 | 19.1 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-23 | pos1 | -1.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-23 | pos1 | 12.0 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-23 | pos1 | -4.7 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-23 | pos1 | 7.6 | + +**Table 8.2.1.5-3: Test requirements for PUSCH with 70% of maximum throughput, Type A, 20 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-10 | pos1 | -1.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-10 | pos1 | 10.6 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-10 | pos1 | 13.0 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-10 | pos1 | -4.9 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-10 | pos1 | 6.8 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-10 | pos1 | 9.2 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-10 | pos1 | -7.9 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-10 | pos1 | 3.6 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-10 | pos1 | 6.1 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-24 | pos1 | 2.9 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-24 | pos1 | 19.1 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-24 | pos1 | -1.0 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-24 | pos1 | 11.9 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-24 | pos1 | -4.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-24 | pos1 | 7.7 | + +**Table 8.2.1.5-4: Test requirements for PUSCH with 70% of maximum throughput, Type A, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-11 | pos1 | -1.7 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-11 | pos1 | 10.8 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-11 | pos1 | 13.4 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-3 | pos1 | 19.9 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-11 | pos1 | -5.0 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-11 | pos1 | 7.0 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-11 | pos1 | 9.2 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-3 | pos1 | 16.2 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-11 | pos1 | -8.0 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-11 | pos1 | 3.9 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-11 | pos1 | 6.1 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-3 | pos1 | 13.2 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-25 | pos1 | 2.1 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-25 | pos1 | 19.2 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-25 | pos1 | -1.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-25 | pos1 | 12.0 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-25 | pos1 | -4.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-25 | pos1 | 7.8 | + +**Table 8.2.1.5-5: Test requirements for PUSCH with 70% of maximum throughput, Type A, 20 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-12 | pos1 | -2.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-12 | pos1 | 10.8 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-12 | pos1 | 13.1 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-12 | pos1 | -5.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-12 | pos1 | 7.0 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-12 | pos1 | 9.2 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-12 | pos1 | -8.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-12 | pos1 | 3.8 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-12 | pos1 | 6.1 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-26 | pos1 | 2.1 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-26 | pos1 | 18.9 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-26 | pos1 | -1.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-26 | pos1 | 12.1 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-26 | pos1 | -4.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-26 | pos1 | 7.7 | + +**Table 8.2.1.5-6: Test requirements for PUSCH with 70% of maximum throughput, Type A, 40 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-13 | pos1 | -1.9 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-13 | pos1 | 10.6 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-13 | pos1 | 13.0 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-4 | pos1 | 20.5 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-13 | pos1 | -5.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-13 | pos1 | 6.9 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-13 | pos1 | 9.1 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-4 | pos1 | 16.7 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-13 | pos1 | -8.1 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-13 | pos1 | 3.7 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-13 | pos1 | 6.0 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-4 | pos1 | 13.2 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-27 | pos1 | 2.1 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-27 | pos1 | 20.3 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-27 | pos1 | -1.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-27 | pos1 | 12.1 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-27 | pos1 | -4.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-27 | pos1 | 7.7 | + +**Table 8.2.1.5-7: Test requirements for PUSCH with 70% of maximum throughput, Type A, 100 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-14 | pos1 | -2.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-14 | pos1 | 10.8 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-14 | pos1 | 13.6 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-5 | pos1 | 21.7 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-14 | pos1 | -5.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-14 | pos1 | 7.1 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-14 | pos1 | 9.6 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-5 | pos1 | 17.3 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-14 | pos1 | -8.1 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-14 | pos1 | 3.8 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-14 | pos1 | 6.4 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-5 | pos1 | 13.7 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-28 | pos1 | 2.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-28 | pos1 | 20.0 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-28 | pos1 | -1.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-28 | pos1 | 12.4 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-28 | pos1 | -4.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-28 | pos1 | 7.9 | + +**Table 8.2.1.5-8: Test requirements for PUSCH with 70% of maximum throughput, Type B, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-8 | pos1 | -1.7 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-8 | pos1 | 10.8 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-8 | pos1 | 13.1 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-1 | pos1 | 19.7 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-8 | pos1 | -5.1 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-8 | pos1 | 6.9 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-8 | pos1 | 9.5 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-1 | pos1 | 16.1 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-8 | pos1 | -8.1 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-8 | pos1 | 3.6 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-8 | pos1 | 6.3 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-1 | pos1 | 12.9 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-22 | pos1 | 2.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-22 | pos1 | 19.1 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-22 | pos1 | -1.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-22 | pos1 | 11.9 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-22 | pos1 | -4.6 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-22 | pos1 | 7.6 | + +**Table 8.2.1.5-9: Test requirements for PUSCH with 70% of maximum throughput, Type B, 10 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-9 | pos1 | -1.7 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-9 | pos1 | 11.1 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-9 | pos1 | 13.2 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-2 | pos1 | 20.1 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-9 | pos1 | -5.1 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-9 | pos1 | 7.1 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-9 | pos1 | 9.5 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-2 | pos1 | 16.5 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-9 | pos1 | -8.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-9 | pos1 | 3.8 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-9 | pos1 | 6.4 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-2 | pos1 | 13.1 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-23 | pos1 | 2.8 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-23 | pos1 | 19.5 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-23 | pos1 | -1.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-23 | pos1 | 12.1 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-23 | pos1 | -4.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-23 | pos1 | 7.8 | + +**Table 8.2.1.5-10: Test requirements for PUSCH with 70% of maximum throughput, Type B, 20 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-10 | pos1 | -1.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-10 | pos1 | 11.0 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-10 | pos1 | 12.9 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-10 | pos1 | -5.1 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-10 | pos1 | 6.9 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-10 | pos1 | 9.4 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-10 | pos1 | -7.9 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-10 | pos1 | 3.7 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-10 | pos1 | 6.3 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-24 | pos1 | 2.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-24 | pos1 | 18.9 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-24 | pos1 | -1.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-24 | pos1 | 12.0 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-24 | pos1 | -4.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-24 | pos1 | 7.7 | + +**Table 8.2.1.5-11: Test requirements for PUSCH with 70% of maximum throughput, Type B, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-11 | pos1 | -1.8 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-11 | pos1 | 10.7 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-11 | pos1 | 13.1 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-3 | pos1 | 19.8 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-11 | pos1 | -5.1 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-11 | pos1 | 7.0 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-11 | pos1 | 9.2 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-3 | pos1 | 16.3 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-11 | pos1 | -8.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-11 | pos1 | 3.8 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-11 | pos1 | 6.2 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-3 | pos1 | 13.0 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-25 | pos1 | 1.9 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-25 | pos1 | 19.3 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-25 | pos1 | -1.7 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-25 | pos1 | 12.1 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-25 | pos1 | -4.8 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-25 | pos1 | 7.8 | + +**Table 8.2.1.5-12: Test requirements for PUSCH with 70% of maximum throughput, Type B, 20 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-12 | pos1 | -2.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-12 | pos1 | 10.7 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-12 | pos1 | 13.1 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-12 | pos1 | -5.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-12 | pos1 | 6.9 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-12 | pos1 | 9.2 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-12 | pos1 | -8.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-12 | pos1 | 3.7 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-12 | pos1 | 6.2 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-26 | pos1 | 2.1 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-26 | pos1 | 19.0 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-26 | pos1 | -1.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-26 | pos1 | 12.0 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-26 | pos1 | -4.6 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-26 | pos1 | 7.8 | + +**Table 8.2.1.5-13: Test requirements for PUSCH with 70% of maximum throughput, Type B, 40 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-13 | pos1 | -1.9 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-13 | pos1 | 10.6 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-13 | pos1 | 13.1 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-4 | pos1 | 20.5 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-13 | pos1 | -5.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-13 | pos1 | 6.8 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-13 | pos1 | 9.3 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-4 | pos1 | 16.6 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-13 | pos1 | -8.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-13 | pos1 | 3.6 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-13 | pos1 | 6.1 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-4 | pos1 | 13.3 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-27 | pos1 | 2.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-27 | pos1 | 19.5 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-27 | pos1 | -1.3 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-27 | pos1 | 12.0 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-27 | pos1 | -4.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-27 | pos1 | 7.7 | + +**Table 8.2.1.5-14: Test requirements for PUSCH with 70% of maximum throughput, Type B, 100 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-14 | pos1 | -1.9 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-14 | pos1 | 10.7 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-14 | pos1 | 13.7 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-5 | pos1 | 21.7 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-14 | pos1 | -5.2 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-14 | pos1 | 6.9 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-14 | pos1 | 9.8 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-5 | pos1 | 17.5 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-14 | pos1 | -8.1 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-14 | pos1 | 3.7 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A5-14 | pos1 | 6.5 | +| | | Normal | TDLA30-10 Low | 70% | G-FR1-A8-5 | pos1 | 13.8 | +| 2 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-28 | pos1 | 2.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-28 | pos1 | 20.1 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-28 | pos1 | -1.4 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-28 | pos1 | 12.4 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-28 | pos1 | -4.5 | +| | | Normal | TDLC300-100 Low | 70 % | G-FR1-A4-28 | pos1 | 7.9 | + +**Table 8.2.1.5-15: Test requirements for PUSCH with 30% of maximum throughput, Type A, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLC300-100 Low | 30 % | G-FR1-A4-8 | pos1 | 3.5 | + +**Table 8.2.1.5-16: Test requirements for PUSCH with 30% of maximum throughput, Type A, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLC300-100 Low | 30 % | G-FR1-A4-11 | pos1 | 3.4 | + +**Table 8.2.1.5-17: Test requirements for PUSCH with 30% of maximum throughput, Type B, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLC300-100 Low | 30 % | G-FR1-A4-8 | pos1 | 3.4 | + +**Table 8.2.1.5-18: Test requirements for PUSCH with 30% of maximum throughput, Type B, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLC300-100 Low | 30 % | G-FR1-A4-11 | pos1 | 3.5 | + +## 8.2.2 Performance requirements for PUSCH with transform precoding enabled + +### 8.2.2.1 Definition and applicability + +The performance requirement of PUSCH is determined by a minimum required throughput for a given SNR. The required throughput is expressed as a fraction of maximum throughput for the FRCs listed in annex A. The performance requirements assume HARQ re-transmissions. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2. + +### 8.2.2.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2] clause 8.2.2. + +### 8.2.2.3 Test Purpose + +The test shall verify the receiver's ability to achieve throughput under multipath fading propagation conditions for a given SNR. + +### 8.2.2.4 Method of test + +#### 8.2.2.4.1 Initial Conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +#### 8.2.2.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type I-C* and *type I-H* respectively. +- 2) Adjust the AWGN generator, according to the SCS and channel bandwidth, defined in table 8.2.2.4.2-1. + +**Table 8.2.2.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------| +| 15 | 5 | -86.5 dBm / 4.5MHz | +| 30 | 10 | -83.6 dBm / 8.64MHz | +| NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. | | | + +- 3) The characteristics of the wanted signal shall be configured according to the corresponding UL reference measurement channel defined in annex A and the test parameters in table 8.2.2.4.2-2. + +**Table 8.2.2.4.2-2: Test parameters for testing PUSCH** + +| Parameter | | Value | +|--------------------------------------------------------------------------------------------|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------| +| Transform precoding | | Enabled | +| Default TDD UL-DL pattern (Note 1) | | 15 kHz SCS:
3D1S1U, S=10D:2G:2U
30 kHz SCS:
7D1S2U, S=6D:4G:4U | +| HARQ | Maximum number of HARQ transmissions | 4 | +| | RV sequence | 0, 2, 3, 1 | +| DM-RS | DM-RS configuration type | 1 | +| | DM-RS duration | single-symbol DM-RS | +| | Additional DM-RS position | pos1 | +| | Number of DM-RS CDM group(s) without data | 2 | +| | Ratio of PUSCH EPRE to DM-RS EPRE | -3 dB | +| | DM-RS port(s) | 0 | +| | DM-RS sequence generation | $N_{ID}^0=0$ , group hopping and sequence hopping are disabled | +| | | | +| Time domain resource assignment | PUSCH mapping type | A, B | +| | Start symbol | 0 | +| | Allocation length | 14 | +| Frequency domain resource assignment | RB assignment | 15 kHz SCS: 25 PRBs in the middle of the test bandwidth
30 kHz SCS: 24 PRBs in the middle of the test bandwidth | +| | Frequency hopping | Disabled | +| Code block group based PUSCH transmission | | Disabled | +| NOTE 1: The same requirements are applicable to FDD and TDD with different UL-DL patterns. | | | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjust the equipment so that required SNR specified in table 8.2.2.5-1 to 8.2.2.5-4 is achieved at the BS input. +- 6) For each of the reference channels in table 8.2.2.5-1 to 8.2.2.5-4 applicable for the base station, measure the throughput. + +## 8.2.2.5 Test Requirement + +The throughput measured according to clause 8.2.2.4.2 shall not be below the limits for the SNR levels specified in table 8.2.2.5-1 to 8.2.2.5-4. + +**Table 8.2.2.5-1: Test requirements for PUSCH with 70% of maximum throughput, Type A, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-31 | pos1 | -1.8 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-31 | pos1 | -5.1 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-31 | pos1 | -7.9 | + +**Table 8.2.2.5-2: Test requirements for PUSCH with 70% of maximum throughput, Type A, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-32 | pos1 | -1.9 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-32 | pos1 | -5.1 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-32 | pos1 | -7.8 | + +**Table 8.2.2.5-3: Test requirements for PUSCH with 70% of maximum throughput, Type B, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-31 | pos1 | -1.7 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-31 | pos1 | -5.2 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-31 | pos1 | -8.0 | + +**Table 8.2.2.5-4: Test requirements for PUSCH with 70% of maximum throughput, Type B, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-32 | pos1 | -2.1 | +| | 4 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-32 | pos1 | -5.4 | +| | 8 | Normal | TDLB100-400 Low | 70 % | G-FR1-A3-32 | pos1 | -8.2 | + +## 8.2.3 Performance requirements for UCI multiplexed on PUSCH + +### 8.2.3.1 Definition and applicability + +The performance requirement of UCI multiplexed on PUSCH is determined by two parameters: block error probability (BLER) of CSI part 1 and block error probability of CSI part 2. The performance is measured by the required SNR at block error probability of CSI part 1 not exceeding 0.1 %, and the required SNR at block error probability of CSI part 2 not exceeding 1 %. + +The CSI part 1 BLER is defined as the probability of incorrectly decoding the CSI part 1 information when the CSI part 1 information is sent. + +The CSI part 2 BLER is defined as the probability of incorrectly decoding the CSI part 2 information when the CSI part 2 information is sent. + +In the test of UCI multiplexed on PUSCH, the UCI information only contains CSI part 1 and CSI part 2 information, there is no HACK/ACK information transmitted. + +The number of UCI information bit payload per slot is defined for two cases as follows: + +- 7 bits: 5 bits in CSI part 1, 2 bits in CSI part 2, + +- 40 bits: 20 bits in CSI part 1, 20 bits in CSI part 2. + +The 7 bits UCI information case is further defined with the bitmap $[c_0\ c_1\ c_2\ c_3\ c_4] = [0\ 1\ 0\ 1\ 0]$ for CSI part 1 information, where $c_0$ is mapping to the RI information, and with the bitmap $[c_0\ c_1] = [1\ 0]$ for CSI part 2 information. + +The 40 bits UCI information case is assumed random information bit selection. + +In both tests, PUSCH data, CSI part 1 and CSI part 2 are transmitted simultaneously. + +Which specific test(s) is applicable to BS is based on the test applicability rule defined in clause 8.1.2. + +### 8.2.3.2 Minimum Requirements + +The minimum requirements are in TS 38.104 [2] clause 8.2.3. + +### 8.2.3.3 Test purpose + +The test shall verify the receiver's ability to detect UCI with CSI part 1 and CSI part 2 bits multiplexed on PUSCH under multipath fading propagation conditions for a given SNR. + +### 8.2.3.4 Method of test + +#### 8.2.3.4.1 Initial conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +#### 8.2.3.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *type 1-H* respectively. +- 2) Adjust the AWGN generator, according to combination of SCS and channel bandwidth defined in table 8.2.3.4.2-1. + +**Table 8.2.3.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------| +| 30 | 10 | -80.6 dBm / 8.64 MHz | +| NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. | | | + +- 3) The characteristics of the wanted signal shall be configured according to the corresponding UL reference measurement channel defined in annex A and the specific test parameters are configured as below. The UCI information bit payload per slot is equal to 7 bits with CSI part 1 5bits, CSI part 2 2bit; and the UCI information bit payload per slot is equal to 40 bits with CSI part 1 20bits, CSI part 2 20bits. + +**Table: 8.2.3.4.2-2: Test parameters for testing UCI multiplexed on PUSCH** + +| Parameter | | Value | +|--------------------------------------------------------------------------------------------|------------------------------------------------------------------|-----------------------------------| +| Transform precoding | | Disabled | +| Default TDD UL-DL pattern (Note 1) | | 30 kHz SCS:
7D1S2U, S=6D:4G:4U | +| HARQ | Maximum number of HARQ transmissions | 1 | +| | RV sequence | 0 | +| DM-RS | DM-RS configuration type | 1 | +| | DM-RS duration | Single-symbol DM-RS | +| | Additional DM-RS position | pos1 | +| | Number of DM-RS CDM group(s) without data | 2 | +| | Ratio of PUSCH EPRE to DM-RS EPRE | -3 dB | +| | DM-RS port(s) | {0} | +| | DM-RS sequence generation | $N_{ID}^0 = 0, n_{scid} = 0$ | +| Time domain resource assignment | PUSCH mapping type | A, B | +| | Start symbol | 0 | +| | Allocation length | 14 | +| Frequency domain resource assignment | RB assignment | Full applicable test bandwidth | +| | Frequency hopping | Disabled | +| Code block group based PUSCH transmission | | Disabled | +| UC | Number of CSI part 1 and CSI part 2 information bit payload | {5,2}, {20, 20} | +| | scaling | 1 | +| | betaOffsetACK-Index1 | 11 | +| | betaOffsetCSI-Part1-Index1 and betaOffsetCSI-Part1-Index2 | 13 | +| | betaOffsetCSI-Part2-Index1 and betaOffsetCSI-Part2-Index2 | 13 | +| | UCI partition for frequency hopping | Disabled | +| NOTE 1: The same requirements are applicable to FDD and TDD with different UL-DL patterns. | | | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjust the equipment so that required SNR specified in table 8.2.3.5-1 to 8.2.3.5-4 is achieved at the BS input during the UCI multiplexed on PUSCH transmissions. +- 6) The signal generators sends a test pattern where UCI with CSI part 1 and CSI part 2 information can be multiplexed on PUSCH. The following statistics are kept: the number of incorrectly decoded CSI part 1 information transmission, the number of incorrectly decoded CSI part 2 information transmission during UCI multiplexed on PUSCH transmission. + +### 8.2.3.5 Test Requirement + +The fractional of incorrectly decoded UCI with CSI part 1 according to clause 8.2.3.4.2 shall be less than 0.1 % for SNR listed in table 8.2.3.5-1 and table 8.2.3.5-2. The fractional of incorrectly decoded UCI with CSI part 2 according to clause 8.2.3.4.2 shall be less than 1 % for SNR listed in table 8.2.3.5-3 and table 8.2.3.5-4. + +**Table 8.2.3.5-1: Test requirements for UCI multiplexed on PUSCH, Type A, CSI part 1, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | UCI bits (CSI part 1, CSI part 2) | Additional DM-RS position | FRC (Annex A) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-----------------------------------|---------------------------|---------------|----------| +| 1 | 2 | Normal | TDLC300-100 Low | 7 (5, 2) | pos1 | G-FR1-A4-11 | 6.0 | +| | 2 | Normal | TDLC300-100 Low | 40 (20,20) | pos1 | G-FR1-A4-11 | 4.9 | + +**Table 8.2.3.5-2: Test requirements for UCI multiplexed on PUSCH, Type B, CSI part 1, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | UCI bits (CSI part 1, CSI part 2) | Additional DM-RS position | FRC (Annex A) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-----------------------------------|---------------------------|---------------|----------| +| 1 | 2 | Normal | TDLC300-100 Low | 7 (5, 2) | pos1 | G-FR1-A4-11 | 6.4 | +| | 2 | Normal | TDLC300-100 Low | 40 (20,20) | pos1 | G-FR1-A4-11 | 4.7 | + +**Table 8.2.3.5-3: Test requirements for UCI multiplexed on PUSCH, Type A, CSI part 2, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | UCI bits (CSI part 1, CSI part 2) | Additional DM-RS position | FRC (Annex A) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-----------------------------------|---------------------------|---------------|----------| +| 1 | 2 | Normal | TDLC300-100 Low | 7 (5, 2) | pos1 | G-FR1-A4-11 | 0.4 | +| | 2 | Normal | TDLC300-100 Low | 40 (20,20) | pos1 | G-FR1-A4-11 | 3.0 | + +**Table 8.2.3.5-4: Test requirements for UCI multiplexed on PUSCH, Type B, CSI part 2, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | UCI bits (CSI part 1, CSI part 2) | Additional DM-RS position | FRC (Annex A) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-----------------------------------|---------------------------|---------------|----------| +| 1 | 2 | Normal | TDLC300-100 Low | 7 (5, 2) | pos1 | G-FR1-A4-11 | 0.9 | +| | 2 | Normal | TDLC300-100 Low | 40 (20,20) | pos1 | G-FR1-A4-11 | 3.2 | + +## 8.2.4 Performance requirements for PUSCH for high speed train + +### 8.2.4.1 Definition and applicability + +The performance requirement of PUSCH is determined by a minimum required throughput for a given SNR. The required throughput is expressed as a fraction of maximum throughput for the FRCs listed in annex A. The performance requirements assume HARQ re-transmissions. The performance requirements for high speed train conditions are optional. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2.1 and clause 8.1.2.4. + +The performance requirements for PUSCH for high speed train only apply to Wide Area Base Stations and Medium Range Base Stations (Subject to declaration). + +### 8.2.4.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2] clause 8.2.4. + +### 8.2.4.3 Test Purpose + +The test shall verify the receiver's ability to achieve throughput under high speed train conditions for a given SNR. + +### 8.2.4.4 Method of test + +#### 8.2.4.4.1 Initial Conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested: $M_j$ ; see clause 4.9.1. + +RF channels to be tested for carrier aggregation: $M_{BW\ Channel\ CA_j}$ ; see clause 4.9.1. + +#### 8.2.4.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, channel simulators and AWGN generators to all BS antenna connectors (depending on HST scenario) for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *type 1-H* respectively. +- 2) Adjust the AWGN generator, according to the channel bandwidth, defined in table 8.2.4.4.2-1. + +**Table 8.2.4.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|----------------------| +| 15 kHz | 5 | -86.5dBm / 4.5MHz | +| | 10 | -83.3 dBm / 9.36MHz | +| 30 kHz | 10 | -83.6dBm / 8.64MHz | +| | 40 | -77.2 dBm / 38.16MHz | + +NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 3) The characteristics of the wanted signal shall be configured according to the corresponding UL reference measurement channel defined in annex A and the test parameters in table 8.2.4.4.2-2. + +**Table 8.2.4.4.2-2: Test parameters for testing high speed train PUSCH** + +| Parameter | Value | +|---------------------------------------------|-------------------------------------------------------------------------| +| Transform precoding | Disabled | +| Uplink-downlink allocation for TDD (Note 1) | 15 kHz SCS:
3D1S1U, S=10D:2G:2U
30 kHz SCS:
7D1S2U, S=6D:4G:4U | +| HARQ | Maximum number of HARQ transmissions | +| | 4 | +| DM-RS | RV sequence | +| | 0, 2, 3, 1 | +| | DM-RS configuration type | +| | 1 | +| | DM-RS duration | +| | single-symbol DM-RS | +| | First DM-RS position | +| | pos2 or pos3 (NOTE2) | +| Time domain resource assignment | Additional DM-RS position | +| | pos2 | +| | Number of DM-RS CDM group(s) without data | +| | 2 | +| | Ratio of PUSCH EPRE to DM-RS EPRE | +| | -3 dB | +| | DM-RS port | +| | {0} | +| | DM-RS sequence generation | +| | $N_{ID}^0=0, n_{SCID}=0$ | +| Frequency domain resource assignment | PUSCH mapping type | +| | A | +| | Start symbol | +| | 0 | +| | Allocation length | +| | 14 | +| Code block group based PUSCH transmission | RB assignment | +| | Full applicable test bandwidth | +| | Frequency hopping | +| | Disabled | +| | Disabled | + +NOTE 1: The same requirements are applicable to FDD and TDD with different UL-DL patterns. +NOTE 2: Either pos2 or pos3 may be selected for conformance testing. + +- 4) The channel simulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjust the equipment so that required SNR specified in table 8.2.4.5-1 to 8.2.4.5-10 is achieved at the BS input. +- 6) For each of the reference channels in table 8.2.4.5-1 to 8.2.4.5-10 applicable for the base station, measure the throughput. + +## 8.2.4.5 Test Requirement + +The throughput measured according to clause 8.2.4.4.2 shall not be below the limits for the SNR levels specified in table 8.2.4.5-1 to 8.2.4.5-10. Unless stated otherwise, the MIMO correlation matrices for the gNB are defined in annex G for low correlation. + +**Table 8.2.4.5-1: Test requirements for PUSCH, Type A, 10 MHz channel bandwidth, 15 kHz SCS, 350km/h** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | HST Scenario 3-NR350 | 70 % | G-FR1-A3-33 | pos2 | -0.5 | +| | 2 | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A3-33 | pos2 | -3.4 | +| | | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A4-29 | pos2 | 8.7 | +| | | Normal | HST Scenario 3-NR350 | 70 % | G-FR1-A3-33 | pos2 | -3.3 | +| | | Normal | HST Scenario 3-NR350 | 70 % | G-FR1-A4-29 | pos2 | 9.0 | +| | 8 | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A3-33 | pos2 | -8.9 | +| | | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A4-29 | pos2 | 2.9 | + +**Table 8.2.4.5-2: Test requirements for PUSCH, Type A, 40 MHz channel bandwidth, 30 kHz SCS, 350km/h** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | HST Scenario 3-NR350 | 70% | G-FR1-A3-34 | pos2 | -0.3 | +| | 2 | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A3-34 | pos2 | -3.4 | +| | | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A4-30 | pos2 | 8.8 | +| | | Normal | HST Scenario 3-NR350 | 70 % | G-FR1-A3-34 | pos2 | -3.2 | +| | | Normal | HST Scenario 3-NR350 | 70 % | G-FR1-A4-30 | pos2 | 9.1 | +| | 8 | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A3-34 | pos2 | -8.8 | +| | | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A4-30 | pos2 | 3.0 | + +**Table 8.2.4.5-3: Test requirements for PUSCH, Type A, 10 MHz channel bandwidth, 15 kHz SCS, 500km/h** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | HST Scenario 3-NR500 | 70% | G-FR1-A3-33 | pos2 | -0.4 | +| | 2 | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A3-33 | pos2 | -3.6 | +| | | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A4-29 | pos2 | 8.8 | +| | | Normal | HST Scenario 3-NR500 | 70 % | G-FR1-A3-33 | pos2 | -3.3 | +| | | Normal | HST Scenario 3-NR500 | 70 % | G-FR1-A4-29 | pos2 | 9.5 | +| | 8 | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A3-33 | pos2 | -9.1 | +| | | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A4-29 | pos2 | 3.0 | + +**Table 8.2.4.5-4: Test requirements for PUSCH, Type A, 40 MHz channel bandwidth, 30 kHz SCS, 500km/h** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | HST Scenario 3-NR500 | 70% | G-FR1-A3-34 | pos2 | -0.2 | +| | 2 | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A3-34 | pos2 | -3.6 | +| | | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A4-30 | pos2 | 9.0 | +| | | Normal | HST Scenario 3-NR500 | 70 % | G-FR1-A3-34 | pos2 | -3.1 | +| | | Normal | HST Scenario 3-NR500 | 70 % | G-FR1-A4-30 | pos2 | 10.5 | +| | 8 | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A3-34 | pos2 | -8.9 | +| | | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A4-30 | pos2 | 3.1 | + +**Table 8.2.4.5-5: Test requirements for PUSCH, Type A, 5 MHz channel bandwidth, 15 kHz SCS, 350km/h** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | HST Scenario 3-NR350 | 70% | G-FR1-A3-33A | pos2 | -0.4 | +| | 2 | Normal | HST Scenario 1-NR350 | 70% | G-FR1-A3-33A | pos2 | -3.4 | +| | | Normal | HST Scenario 1-NR350 | 70% | G-FR1-A4-29A | pos2 | 8.8 | +| | | Normal | HST Scenario 3-NR350 | 70% | G-FR1-A3-33A | pos2 | -3.3 | +| | | Normal | HST Scenario 3-NR350 | 70% | G-FR1-A4-29A | pos2 | 8.9 | +| | 8 | Normal | HST Scenario 1-NR350 | 70% | G-FR1-A3-33A | pos2 | -8.8 | +| | | Normal | HST Scenario 1-NR350 | 70% | G-FR1-A4-29A | pos2 | 3.1 | + +**Table 8.2.4.5-6: Test requirements for PUSCH, Type A, 10 MHz channel bandwidth, 30 kHz SCS, 350km/h** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | HST Scenario 3-NR350 | 70 % | G-FR1-A3-34A | pos2 | -0.4 | +| | 2 | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A3-34A | pos2 | -3.3 | +| | | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A4-30A | pos2 | 8.6 | +| | | Normal | HST Scenario 3-NR350 | 70 % | G-FR1-A3-34A | pos2 | -3.3 | +| | | Normal | HST Scenario 3-NR350 | 70 % | G-FR1-A4-30A | pos2 | 8.9 | +| | 8 | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A3-34A | pos2 | -8.7 | +| | | Normal | HST Scenario 1-NR350 | 70 % | G-FR1-A4-30A | pos2 | 2.9 | + +**Table 8.2.4.5-7: Test requirements for PUSCH, Type A, 5 MHz channel bandwidth, 15 kHz SCS, 500km/h** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | HST Scenario 3-NR500 | 70 % | G-FR1-A3-33A | pos2 | -0.3 | +| | 2 | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A3-33A | pos2 | -3.3 | +| | | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A4-29A | pos2 | 9.0 | +| | | Normal | HST Scenario 3-NR500 | 70 % | G-FR1-A3-33A | pos2 | -3.2 | +| | | Normal | HST Scenario 3-NR500 | 70 % | G-FR1-A4-29A | pos2 | 9.1 | +| | 8 | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A3-33A | pos2 | -8.8 | +| | | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A4-29A | pos2 | 3.3 | + +**Table 8.2.4.5-8: Test requirements for PUSCH, Type A, 10 MHz channel bandwidth, 30 kHz SCS, 500km/h** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 1 | Normal | HST Scenario 3-NR500 | 70 % | G-FR1-A3-34A | pos2 | -0.2 | +| | 2 | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A3-34A | pos2 | -3.3 | +| | | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A4-30A | pos2 | 8.9 | +| | | Normal | HST Scenario 3-NR500 | 70 % | G-FR1-A3-34A | pos2 | -3.1 | +| | | Normal | HST Scenario 3-NR500 | 70 % | G-FR1-A4-30A | pos2 | 8.9 | +| | 8 | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A3-34A | pos2 | -8.5 | +| | | Normal | HST Scenario 1-NR500 | 70 % | G-FR1-A4-30A | pos2 | 3.2 | + +**Table 8.2.4.5-9: Test requirements for PUSCH, Type A, 5 MHz channel bandwidth, 15 kHz SCS, multi-path fading channel under high Doppler value** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLC300-600 | 70 % | G-FR1-A3-33A | pos2 | -1.3 | + +**Table 8.2.4.5-10: Test requirements for PUSCH, Type A, 10 MHz channel bandwidth, 30 kHz SCS, multi-path fading channel under high Doppler value** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLC300-1200 | 70 % | G-FR1-A3-34A | pos2 | -1.4 | + +## 8.2.5 Performance requirements for UL timing adjustment + +### 8.2.5.1 Definition and applicability + +The performance requirement of UL timing adjustment is determined by a minimum required throughput measured for the moving UE at given SNR. The performance requirements assume HARQ retransmissions. The performance requirements for UL timing adjustment scenario Y and scenario Z defined in Annex G.4 are optional. + +In the tests for UL timing adjustment, two signals are configured, one being transmitted by a moving UE and the other being transmitted by a stationary UE. The transmission of SRS from UE is optional. FRC parameters in Table A.4-2B are applied for both UEs. The received power for both UEs is the same. The resource blocks allocated for both UEs are consecutive. In Scenario Y and Scenario Z, Doppler shift is not taken into account. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2.1. + +### 8.2.5.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2] clause 8.2.5. + +### 8.2.5.3 Test Purpose + +The test shall verify the receiver's ability to achieve throughput measured for the moving UE at given SNR under moving propagation conditions. + +### 8.2.5.4 Method of test + +#### 8.2.5.4.1 Initial Conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested: M; see clause 4.9.1. + +RF channels to be tested for carrier aggregation: MBW Channel CA; see clause 4.9.1. + +#### 8.2.5.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for BS type 1-C and type 1-H respectively. +- 2) Adjust the AWGN generator, according to combination of SCS and channel bandwidth defined in table 8.2.5.4.2-1. + +**Table 8.2.5.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|----------------------------------|--------------------------------|-------------------------| +| 15 | 5 | -86.5 dBm / 4.5MHz | +| | 10 | -83.3 dBm / 9.36MHz | +| 30 | 10 | -83.6 dBm / 8.64MHz | +| | 40 | -77.2 dBm / 38.16MHz | + +NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 3) The characteristics of the wanted signals (transmitted by moving UE) shall be configured according to the corresponding UL reference measurement channel defined in annex A and the test parameters in Table 8.2.5.4.2-2. + +**Table 8.2.5.4.2-2 Test parameters for testing UL timing adjustment** + +| Parameter | | Value | +|--------------------------------------------|---------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Transform precoding | | Disabled | +| Uplink-downlink allocation for TDD (Note1) | | 15 kHz SCS:
3D1S1U, S=10D:2G:2U
30 kHz SCS:
7D1S2U, S=6D:4G:4U | +| HARQ | Maximum number of HARQ transmissions | 4 | +| | RV sequence | 0, 2, 3, 1 | +| DM-RS | DM-RS configuration type | 1 | +| | DM-RS duration | single-symbol DM-RS | +| | Additional DM-RS position | Pos2 | +| | Number of DM-RS CDM group(s) without data | 2 | +| | Ratio of PUSCH EPRE to DM-RS EPRE | -3 dB | +| | DM-RS port(s) | {0} | +| | DM-RS sequence generation | $N_{ID}^0=0$ , $n_{SCID}=0$ for moving UE
$N_{ID}^0=1$ , $n_{SCID}=1$ for stationary UE | +| Time domain resource assignment | PUSCH mapping type | A, B | +| | Allocation length | 14 | +| Frequency domain resource assignment | RB assignment | 5 MHz CBW/15kHz SCS:
12 RB for each UE
10MHz CBW/15kHz SCS:
25 RB for each UE
10MHz CBW/30kHz SCS:
12 RB for each UE
40MHz CBW/30kHz SCS:
50 RB for each UE | +| | Starting PRB index | Moving UE: 0
Stationary UE: 12 for 5MHz CBW/15kHz SCS,
25 for 10 MHz CBW/15kHz SCS, 12 for 10MHz CBW/30kHz SCS and 50 for 40 MHz CBW/30kHz SCS | +| | Frequency hopping | Disabled | +| SRS resource allocation | Slots in which sounding RS is transmitted (Note2) | For FDD: slot #1 in radio frames
For TDD:
last symbol in slot #3 in radio frames for 15kHz
last symbol in slot #7 in radio frames for 30kHz | +| | SRS resource allocation | 15 kHz SCS:
$C_{SRS}=5$ , $B_{SRS}=0$ , for 20 RB
$C_{SRS}=11$ , $B_{SRS}=0$ , for 40 RB
30 kHz SCS:
$C_{SRS}=5$ , $B_{SRS}=0$ , for 20 RB
$C_{SRS}=21$ , $B_{SRS}=0$ , for 80 RB | + +NOTE 1: The same requirements are applicable to FDD and TDD with different UL-DL patterns. +NOTE 2: The transmission of SRS is optional. And the transmission comb and SRS periodicity are configured as $K_{TC} = 2$ , and $T_{SRS} = 10$ for 15 kHz SCS, $T_{SRS} = 20$ for 30 kHz SCS respectively. + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G.4. +- 5) Adjust the equipment so that required SNR specified in Table 8.2.5.5-1 to Table 8.2.5.5-2 is achieved at the BS input for high speed train. + +Adjust the equipment so that required SNR specified in Table 8.2.5.6-1 to Table 8.2.5.6-2 is achieved at the BS input for normal mode. + +- 6) For each of the reference channels in Table 8.2.5.5-1 to Table 8.2.5.5-2 applicable for the base station, measure the throughput for high speed train. + +For each of the reference channels in Table 8.2.5.6-1 to Table 8.2.5.6-2 applicable for the base station, measure the throughput for normal mode. + +### 8.2.5.5 Test Requirement for High Speed Train + +The throughput shall be $\geq 70\%$ of the maximum throughput of the reference measurement channel as specified in annex A for the moving UE at the SNR given in table 8.2.5.5-1 for mapping type A and table 8.2.5.5-2 for mapping type B respectively. + +**Table 8.2.5.5-1: Test requirements for UL timing adjustment with mapping type A for high speed train** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Channel Bandwidth [MHz] | SCS [kHz] | Moving propagation conditions and correlation matrix (Annex G) | FRC (Annex A) | SNR [dB] | +|-----------------------|-----------------------|---------------|-------------------------|-----------|----------------------------------------------------------------|---------------|----------| +| 1 | 2 | Normal | 5 | 15 | Scenario Y | G-FR1-A4-31A | 8.5 | +| | | | | | Scenario Z | G-FR1-A4-31A | 8.6 | +| | | | 10 | 15 | Scenario Y | G-FR1-A4-31 | 8.8 | +| | | | | | Scenario Z | G-FR1-A4-31 | 8.7 | +| | | | 10 | 30 | Scenario Y | G-FR1-A4-32A | 8.6 | +| | | | | | Scenario Z | G-FR1-A4-32A | 8.6 | +| | | | 40 | 30 | Scenario Y | G-FR1-A4-32 | 8.7 | +| | | | | | Scenario Z | G-FR1-A4-32 | 8.8 | + +**Table 8.2.5.5-2: Test requirements for UL timing adjustment with mapping type B for high speed train** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Channel Bandwidth [MHz] | SCS [kHz] | Moving propagation conditions and correlation matrix (Annex G) | FRC (Annex A) | SNR [dB] | +|-----------------------|-----------------------|---------------|-------------------------|-----------|----------------------------------------------------------------|---------------|----------| +| 1 | 2 | Normal | 5 | 15 | Scenario Y | G-FR1-A4-31A | 8.6 | +| | | | | | Scenario Z | G-FR1-A4-31A | 8.6 | +| | | | 10 | 15 | Scenario Y | G-FR1-A4-31 | 8.8 | +| | | | | | Scenario Z | G-FR1-A4-31 | 8.8 | +| | | | 10 | 30 | Scenario Y | G-FR1-A4-32A | 8.6 | +| | | | | | Scenario Z | G-FR1-A4-32A | 8.7 | +| | | | 40 | 30 | Scenario Y | G-FR1-A4-32 | 8.7 | +| | | | | | Scenario Z | G-FR1-A4-32 | 8.8 | + +### 8.2.5.6 Test Requirement for Normal Mode + +The throughput shall be $\geq 70\%$ of the maximum throughput of the reference measurement channel as specified in annex A for the moving UE at the SNR given in table 8.2.5.6-1 for mapping type A and table 8.2.5.6-2 for mapping type B respectively. + +**Table 8.2.5.6-1: Test requirements for UL timing adjustment with mapping type A** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Channel Bandwidth [MHz] | SCS [kHz] | Moving propagation conditions and correlation matrix (Annex G) | FRC (Annex A) | SNR [dB] | +|-----------------------|-----------------------|---------------|-------------------------|-----------|----------------------------------------------------------------|---------------|----------| +| 1 | 2 | Normal | 5 | 15 | Scenario X | G-FR1-A4-31A | 11.2 | +| | | | 10 | 15 | Scenario X | G-FR1-A4-31 | 11.8 | +| | | | 10 | 30 | Scenario X | G-FR1-A4-32A | 11.4 | +| | | | 40 | 30 | Scenario X | G-FR1-A4-32 | 12.6 | + +**Table 8.2.5.6-2: Test requirements for UL timing adjustment with mapping type B** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Channel Bandwidth [MHz] | SCS [kHz] | Moving propagation conditions and correlation matrix (Annex G) | FRC (Annex A) | SNR [dB] | +|-----------------------|-----------------------|---------------|-------------------------|-----------|----------------------------------------------------------------|---------------|----------| +| 1 | 2 | Normal | 5 | 15 | Scenario X | G-FR1-A4-31A | 11.2 | +| | | | 10 | 15 | Scenario X | G-FR1-A4-31 | 11.9 | +| | | | 10 | 30 | Scenario X | G-FR1-A4-32A | 11.3 | +| | | | 40 | 30 | Scenario X | G-FR1-A4-32 | 13.0 | + +## 8.2.6 Performance requirements for PUSCH with 0.001% BLER + +### 8.2.6.1 Definition and applicability + +The performance requirement of PUSCH is determined by a maximum required transport block error rate (BLER) for a given SNR. The required BLER is defined as the probability of incorrectly decoding the transport block after reaching the maximum number of HARQ transmissions for the FRCs listed in annex A. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2.1. + +### 8.2.6.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2] clause 8.2.6.2. + +### 8.2.6.3 Test Purpose + +The test shall verify the receiver's ability to achieve 0.001% BLER under AWGN conditions for a given SNR. + +### 8.2.6.4 Method of test + +#### 8.2.6.4.1 Initial Conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +RF channels to be tested for carrier aggregation: $M_{BW\ Channel\ CA}$ ; see clause 4.9.1. + +#### 8.2.6.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *type 1-H* respectively. +- 2) Adjust the AWGN generator, according to the channel bandwidth, defined in table 8.2.6.4.2-1. + +**Table 8.2.6.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|----------------------| +| 15 kHz | 5 | -86.5 dBm / 4.5MHz | +| | 10 | -83.3 dBm / 9.36MHz | +| 30 kHz | 10 | -83.6 dBm / 8.64MHz | +| | 40 | -77.2 dBm / 38.16MHz | + +NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 3) The characteristics of the wanted signal shall be configured according to the corresponding UL reference measurement channel defined in annex A and the test parameters in table 8.2.6.4.2-2. + +**Table 8.2.6.4.2-2: Test parameters for testing PUSCH with 0.001% BLER** + +| Parameter | Value | +|-------------------------------------------|------------------------------------------------------------------------------------| +| Transform precoding | Disabled | +| Default TDD UL-DL pattern (Note 1) | 15 kHz SCS:
3D1S1U, S=10D:2G:2U
30 kHz SCS:
7D1S2U, S=6D:4G:4U | +| HARQ | Maximum number of HARQ transmissions | +| | 1 | +| DM-RS | RV sequence | +| | 0 | +| | DM-RS configuration type | +| | 1 | +| | DM-RS duration | +| | single-symbol DM-RS | +| | Additional DM-RS position | +| | Pos1 | +| | Number of DM-RS CDM group(s) without data | +| | 1 | +| | Ratio of PUSCH EPRE to DM-RS EPRE | +| | -3 dB | +| | DM-RS port(s) | +| | {0} | +| | DM-RS sequence generation | +| | $N_{ID}^0=0, n_{SCID}=0$ | +| Time domain resource assignment | PUSCH mapping type | +| | A, B | +| | Start symbol | +| | 0 | +| | Allocation length | +| | 14 | +| Frequency domain resource assignment | RB assignment | +| | Full applicable test bandwidth | +| | Frequency hopping | +| | Disabled | +| Code block group based PUSCH transmission | Disabled | +| Note 1: | The same requirements are applicable to FDD and TDD with different UL-DL patterns. | + +- 4) No multipath fading channel is included in the test. +- 5) Adjust the equipment so that required SNR specified in table 8.2.6.5-1 to 8.2.6.5-8 is achieved at the BS input. + +- 6) For each of the reference channels in table 8.2.6.5-1 to 8.2.6.5-8 applicable for the base station, measure the BLER. BLER is evaluated based on the test methodology described in Annex I. + +## 8.2.6.5 Test Requirement + +The BLER according to clause 8.2.6.4.2 shall not be below the limits for the SNR levels specified in table 8.2.6.5-1 to 8.2.6.5-8. + +**Table 8.2.6.5-1: Test requirements for PUSCH with 0.001% BLER, Type A, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions | BLER | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|------------------------|--------|---------------|---------------------------|----------| +| 1 | 2 | Normal | AWGN | 0.001% | G-FR1-A3A-1 | Pos1 | -3.8 | + +**Table 8.2.6.5-2: Test requirements for PUSCH with 0.001% BLER, Type A, 10 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions | BLER | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|------------------------|--------|---------------|---------------------------|----------| +| 1 | 2 | Normal | AWGN | 0.001% | G-FR1-A3A-2 | Pos1 | -4.6 | + +**Table 8.2.6.5-3: Test requirements for PUSCH with 0.001% BLER, Type A, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions | BLER | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|------------------------|--------|---------------|---------------------------|----------| +| 1 | 2 | Normal | AWGN | 0.001% | G-FR1-A3A-3 | Pos1 | -4.1 | + +**Table 8.2.6.5-4: Test requirements for PUSCH with 0.001% BLER, Type A, 40 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions | BLER | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|------------------------|--------|---------------|---------------------------|----------| +| 1 | 2 | Normal | AWGN | 0.001% | G-FR1-A3A-4 | Pos1 | -4.9 | + +**Table 8.2.6.5-5: Test requirements for PUSCH with 0.001% BLER, Type B, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions | BLER | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|------------------------|--------|---------------|---------------------------|----------| +| 1 | 2 | Normal | AWGN | 0.001% | G-FR1-A3A-1 | Pos1 | -3.9 | + +**Table 8.2.6.5-6: Test requirements for PUSCH with 0.001% BLER, Type B, 10 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions | BLER | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|------------------------|--------|---------------|---------------------------|----------| +| 1 | 2 | Normal | AWGN | 0.001% | G-FR1-A3A-2 | Pos1 | -4.6 | + +**Table 8.2.6.5-7: Test requirements for PUSCH with 0.001% BLER, Type B, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions | BLER | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|------------------------|--------|---------------|---------------------------|----------| +| 1 | 2 | Normal | AWGN | 0.001% | G-FR1-A3A-3 | Pos1 | -4.1 | + +**Table 8.2.6.5-8: Test requirements for PUSCH with 0.001% BLER, Type B, 40 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions | BLER | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|------------------------|--------|---------------|---------------------------|----------| +| 1 | 2 | Normal | AWGN | 0.001% | G-FR1-A3A-4 | Pos1 | -4.9 | + +## 8.2.7 Performance requirements for PUSCH repetition Type A + +### 8.2.7.1 Definition and applicability + +The performance requirement of PUSCH with slot aggregation factor configured is determined by a maximum target BLER for a given SNR. The required BLER is defined as the probability of incorrectly decoding the PUSCH information when the PUSCH information is sent for the FRCs listed in annex A. The performance requirements assume HARQ re-transmissions. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2.1. + +### 8.2.7.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2] clause 8.2.7. + +### 8.2.7.3 Test Purpose + +The test shall verify the receiver's ability to achieve 1% BLER with PUSCH repetition Type A under multipath fading propagation conditions for a given SNR. + +### 8.2.7.4 Method of test + +#### 8.2.7.4.1 Initial Conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +RF channels to be tested for carrier aggregation: $M_{BW\ Channel\ CA}$ ; see clause 4.9.1. + +#### 8.2.7.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *type 1-H* respectively. +- 2) Adjust the AWGN generator, according to the channel bandwidth, defined in table 8.2.7.4.2-1. + +**Table 8.2.7.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|----------------------| +| 15 kHz | 5 | -86.5 dBm / 4.5MHz | +| | 10 | -83.3 dBm / 9.36MHz | +| 30 kHz | 10 | -83.6 dBm / 8.64MHz | +| | 40 | -77.2 dBm / 38.16MHz | + +NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 3) The characteristics of the wanted signal shall be configured according to the corresponding UL reference measurement channel defined in annex A and the test parameters in table 8.2.7.4.2-2. + +**Table 8.2.7.4.2-2: Test parameters for testing PUSCH repetition Type A** + +| Parameter | | Value | +|------------------------------------|-------------------------------------------|-------------------------------------------------------------------------| +| Transform precoding | | Disabled | +| Default TDD UL-DL pattern (Note 1) | | 15 kHz SCS:
3D1S1U, S=10D:2G:2U
30 kHz SCS:
7D1S2U, S=6D:4G:4U | +| HARQ | Maximum number of HARQ transmissions | 4 | +| | RV sequence | 0, 3, 0, 3 [Note 2] | +| DM-RS | DM-RS configuration type | 1 | +| | DM-RS duration | single-symbol DM-RS | +| | Additional DM-RS position | pos1 | +| | Number of DM-RS CDM group(s) without data | 2 | +| | Ratio of PUSCH EPRE to DM-RS EPRE | -3 dB | +| | DM-RS port | 0 | +| | DM-RS sequence generation | $N_{ID}^0=0, n_{SCID}=0$ | +| Time domain resource assignment | PUSCH mapping type | A, B | +| | Start symbol | 0 | +| | Allocation length | 14 | +| | PUSCH aggregation factor | 30 kHz SCS: n2
15 kHz SCS: n2 for FDD and n8 for TDD [Note 3] | +| Frequency domain resource | RB assignment | Full applicable test bandwidth | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------| +| assignment | Frequency hopping | Disabled | +| Code block group based PUSCH transmission | | Disabled | +| Note 1: The same requirements are applicable to FDD and TDD with different UL-DL pattern. | | | +| Note 2: The effective RV sequence is {0, 2, 3, 1} with slot aggregation. | | | +| Note 3: The intention of this configuration is to have two effective transmissions of the transport block. To achieve this for the standard TDD pattern captured in this table, a value of n8 is necessary, while for FDD a value of n2 is necessary. | | | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjust the equipment so that required SNR specified in table 8.2.7.5-1 to 8.2.7.5-8 is achieved at the BS input. +- 6) For each of the reference channels in table 8.2.7.5-1 to 8.2.7.5-8 applicable for the base station, measure the BLER. + +## 8.2.7.5 Test Requirement + +The BLER measured according to clause 8.2.7.4.2 shall not be above the limits for the SNR levels specified in table 8.2.7.5-1 to 8.2.7.5-14. + +**Table 8.2.7.5-1: Minimum requirements for PUSCH, Type A, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Target BLER | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 1% (Note 1) | G-FR1-A3A-1 | pos1 | -7.8 | +| Note 1: BLER is defined as residual BLER; i.e. ratio of incorrectly received transport blocks / sent transport blocks, independently of the number HARQ transmission(s) for each transport block. | | | | | | | | + +**Table 8.2.7.5-2: Minimum requirements for PUSCH, Type A, 10 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Target BLER | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 1% (Note 1) | G-FR1- A3A -2 | pos1 | -9.6 | +| Note 1: BLER is defined as residual BLER; i.e. ratio of incorrectly received transport blocks / sent transport blocks, independently of the number HARQ transmission(s) for each transport block. | | | | | | | | + +**Table 8.2.7.5-3: Minimum requirements for PUSCH, Type A, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Target BLER | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 1% (Note 1) | G-FR1- A3A -3 | pos1 | -10.2 | +| Note 1: BLER is defined as residual BLER; i.e. ratio of incorrectly received transport blocks / sent transport blocks, independently of the number HARQ transmission(s) for each transport block. | | | | | | | | + +**Table 8.2.7.5-4: Minimum requirements for PUSCH, Type A, 40 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Target BLER | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 1% (Note 1) | G-FR1- A3A -4 | pos1 | -10.9 | + +Note 1: BLER is defined as residual BLER; i.e. ratio of incorrectly received transport blocks / sent transport blocks, independently of the number HARQ transmission(s) for each transport block. + +**Table 8.2.7.5-5: Minimum requirements for PUSCH, Type B, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Target BLER | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 1% (Note 1) | G-FR1- A3A -1 | pos1 | -7.6 | + +Note 1: BLER is defined as residual BLER; i.e. ratio of incorrectly received transport blocks / sent transport blocks, independently of the number HARQ transmission(s) for each transport block. + +**Table 8.2.7.5-6: Minimum requirements for PUSCH, Type B, 10 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Target BLER | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 1% (Note 1) | G-FR1- A3A -2 | pos1 | -9.5 | + +Note 1: BLER is defined as residual BLER; i.e. ratio of incorrectly received transport blocks / sent transport blocks, independently of the number HARQ transmission(s) for each transport block. + +**Table 8.2.7.5-7: Minimum requirements for PUSCH, Type B, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Target BLER | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 1% (Note 1) | G-FR1- A3A -3 | pos1 | -10.2 | + +Note 1: BLER is defined as residual BLER; i.e. ratio of incorrectly received transport blocks / sent transport blocks, independently of the number HARQ transmission(s) for each transport block. + +**Table 8.2.7.5-8: Minimum requirements for PUSCH, Type B, 40 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Target BLER | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLB100-400 Low | 1% (Note 1) | G-FR1- A3A -4 | pos1 | -10.8 | + +Note 1: BLER is defined as residual BLER; i.e. ratio of incorrectly received transport blocks / sent transport blocks, independently of the number HARQ transmission(s) for each transport block. + +## 8.2.8 Performance requirements for PUSCH Mapping Type B with non-slot transmission + +### 8.2.8.1 Definition and applicability + +The performance requirement of PUSCH mapping Type B is determined by a minimum required throughput for a given SNR. The required throughput is expressed as a fraction of maximum throughput for the FRCs listed in annex A. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2.1. + +### 8.2.8.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2] clause 8.2.8. + +### 8.2.8.3 Test Purpose + +The test shall verify the receiver's ability to achieve throughput for PUSCH mapping Type B with 2 symbol length allocated in time domain under multipath fading propagation conditions for a given SNR. + +### 8.2.8.4 Method of test + +#### 8.2.8.4.1 Initial Conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +RF channels to be tested for carrier aggregation: $M_{BW\ Channel\ CA}$ ; see clause 4.9.1. + +#### 8.2.8.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type I-C* and *type I-H* respectively. +- 2) Adjust the AWGN generator, according to the channel bandwidth, defined in table 8.2.8.4.2-1. + +**Table 8.2.8.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|----------------------| +| 15 kHz | 5 | -86.5 dBm / 4.5MHz | +| | 10 | -83.3 dBm / 9.36MHz | +| 30 kHz | 10 | -83.6 dBm / 8.64MHz | +| | 40 | -77.2 dBm / 38.16MHz | + +NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 3) The characteristics of the wanted signal shall be configured according to the corresponding UL reference measurement channel defined in annex A and the test parameters in table 8.2.8.4.2-2. + +**Table 8.2.8.4.2-2: Test parameters for testing PUSCH Mapping Type B with non-slot transmission** + +| Parameter | | Value | +|-------------------------------------------------------------------------------------------|-------------------------------------------|-------------------------------------------------------------------------| +| Transform precoding | | Disabled | +| Default TDD UL-DL pattern (Note 1) | | 15 kHz SCS:
3D1S1U, S=10D:2G:2U
30 kHz SCS:
7D1S2U, S=6D:4G:4U | +| HARQ | Maximum number of HARQ transmissions | 1 | +| | RV sequence | 0 | +| DM-RS | DM-RS configuration type | 1 | +| | DM-RS duration | single-symbol DM-RS | +| | Number of additional DM-RS | 0 | +| | Number of DM-RS CDM group(s) without data | 2 | +| | Ratio of PUSCH EPRE to DM-RS EPRE | -3 dB | +| | DM-RS port | {0} | +| | DM-RS sequence generation | $N_{id}^0=0, n_{scid}=0$ | +| Time domain resource assignment | PUSCH mapping type | B | +| | Start symbol | 0 | +| | Allocation length | 2 | +| | PUSCH aggregation factor | 1 | +| Frequency domain resource assignment | RB assignment | Full applicable test bandwidth | +| | Frequency hopping | Disabled | +| Code block group based PUSCH transmission | | Disabled | +| Note 1: The same requirements are applicable to FDD and TDD with different UL-DL pattern. | | | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjust the equipment so that required SNR specified in table 8.2.8.5-1 to 8.2.8.5-4 is achieved at the BS input. +- 6) For each of the reference channels in table 8.2.8.5-1 to 8.2.8.5-8 applicable for the base station, measure the throughput. + +### 8.2.8.5 Test Requirement + +The throughput measured according to clause 8.2.8.4.2 shall not be below the limits for the SNR levels specified in table 8.2.8.5-1 to 8.2.8.5-4. + +**Table 8.2.8.5-1: Minimum requirements for PUSCH, Type B, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (Annex A) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|----------| +| 1 | 2 | Normal | TDLC300-100 Low | 70% | G-FR1-A3B-1 | 1.1 | + +**Table 8.2.8.5-2: Minimum requirements for PUSCH, Type B, 10 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (Annex A) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|----------| +| 1 | 2 | Normal | TDLC300-100 Low | 70% | G-FR1- A3B -2 | 0.9 | + +**Table 8.2.8.5-3: Minimum requirements for PUSCH, Type B, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (Annex A) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|----------| +| 1 | 2 | Normal | TDLC300-100 Low | 70% | G-FR1- A3B -3 | 0.9 | + +**Table 8.2.8.5-4: Minimum requirements for PUSCH, Type B, 40 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (Annex A) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|----------| +| 1 | 2 | Normal | TDLC300-100 Low | 70% | G-FR1- A3B -4 | 0.6 | + +## 8.2.9 Performance requirements for PUSCH msgA for 2-step RA type + +### 8.2.9.1 Definition and applicability + +The performance requirement of MsgA PUSCH is determined by a minimum required block error rate of MsgA received by BS at given SNR for FRCs listed in annex A. The performance requirements assume that the precedent preamble of MsgA is correctly detected. The performance requirements of assume no HARQ retransmission. + +These requirements are applicable for wide area and medium range BS that support 2-step RA type. The requirements are not applied for a local area BS that supports 2-step RA type. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2.1. + +### 8.2.9.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2] clause 8.2.9. + +### 8.2.9.3 Test Purpose + +The test shall verify the receiver's ability to achieve maximum BLER for a given SNR. + +### 8.2.9.4 Method of test + +#### 8.2.9.4.1 Initial Conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested: M; see clause 4.9.1. + +RF channels to be tested for carrier aggregation: $M_{BW\ Channel\ CA}$ ; see clause 4.9.1. + +#### 8.2.9.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, channel simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type I-C* and *type I-H* respectively. +- 2) Adjust the AWGN generator, according to the channel bandwidth, defined in table 8.2.9.4.2-1. + +**Table 8.2.9.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|----------------------| +| 15 kHz | 10 | -83.3 dBm / 9.36MHz | +| 30 kHz | 40 | -77.2 dBm / 38.16MHz | + +NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 3) The characteristics of the wanted signal shall be configured according to the corresponding UL reference measurement channel defined in annex A and the test parameters in table 8.2.9.4.2-2. + +**Table 8.2.9.4.2-2: Test parameters for testing msgA PUSCH for 2-step RA type** + +| Parameter | Value | +|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Transform precoding | Disabled | +| Channel bandwidth | 15 kHz SCS: 10 MHz
30 kHz SCS: 40 MHz | +| MCS | 1 | +| DM-RS | DM-RS configuration type 1 | +| | DM-RS duration single-symbol DM-RS | +| | DM-RS position ( $l_0$ ) 2 | +| | Additional DM-RS position pos2 or pos1 (Note 2) | +| | Number of DM-RS CDM group(s) without data 2 | +| | Ratio of PUSCH EPRE to DM-RS EPRE -3 dB | +| | DM-RS port {0} | +| | DM-RS sequence generation $N_{ID}^0=0, n_{SCID} = 0$ | +| Time domain resource assignment | PUSCH mapping type Both A and B | +| | Allocation length 14 | +| Frequency domain resource assignment | RB assignment 2 PRBs | +| | Starting PRB index 0 | +| | Frequency hopping Disabled | +| Time offset (TO) Cycling ( $\mu$ s) | start:step:end 15k SCS: 0:0.2:3.8 | +| | 30k SCS: 0:0.1:2 | +| Test Metric | BLER 0.01 | +| Note 1: | The same requirements are applicable to FDD and TDD with different UL-DL patterns. | +| Note 2: | For FR1, either pos 1 or pos 2 may be used for the test FRC. A pass with either of these possibilities is sufficient to demonstrate compliance to the core requirement. | +| Note 3: | The power ratio between preamble and msgA (msgA-DeltaPreamble) is set to be sufficient to achieve 100% preamble detection. The SNR for the requirement is defined on the msgA PUSCH. | + +- 4) The channel simulators shall be configured according to the corresponding channel model defined in annex G.3. + +- 5) Adjust the equipment so that required SNR specified in table 8.2.9.5-1 to 8.2.9.5-4 is achieved at the BS input. +- 6) The test signal generator send a MsgA including a preamble and PUSCH signal and the receiver tries to detect the MsgA signal. The MsgA signal is sent with a timing offset as described below. + +The timing offset base value for MsgA signal is set to 0. For each newly transmitted MsgA, this offset is increased within the loop. For 15 kHz SCS, add a value of 0.2 us in each step until the end of the tested rage which is 3.8 us. For 30 kHz SCS, add a value of 0.1 us in each step until the end of tested rage which is 2 us. At the end of the testing range, the offset is reset to zero. The timing offset scheme for MsgA transmission is presented in Figure 8.2.9.4.2-1 for 30 kHz SCS and in Figure 8.2.9.4.2-2 for 15 kHz SCS. + +![Figure 8.2.9.4.2-1: Timing offset scheme for MsgA transmission for BS type 1-C and type 1-H with 30 kHz SCS. The diagram shows a horizontal timeline with 20 boxes representing time intervals. Below the boxes, time values are marked from 0us to 2.0us in 0.1us increments. A curved arrow starts at the 0us mark and loops back to it after the last box, indicating a continuous loop of transmission with increasing timing offsets.](7e2d5e19c1a94ed931dd102da45f4f8f_img.jpg) + +Figure 8.2.9.4.2-1: Timing offset scheme for MsgA transmission for BS type 1-C and type 1-H with 30 kHz SCS. The diagram shows a horizontal timeline with 20 boxes representing time intervals. Below the boxes, time values are marked from 0us to 2.0us in 0.1us increments. A curved arrow starts at the 0us mark and loops back to it after the last box, indicating a continuous loop of transmission with increasing timing offsets. + +**Figure 8.2.9.4.2-1: Timing offset scheme for MsgA transmission for BS type 1-C and type 1-H with 30 kHz SCS** + +![Figure 8.2.9.4.2-2: Timing offset scheme for MsgA transmission for BS type 1-C and type 1-H with 15 kHz SCS. The diagram shows a horizontal timeline with 19 boxes representing time intervals. Below the boxes, time values are marked from 0us to 3.8us in 0.2us increments. A curved arrow starts at the 0us mark and loops back to it after the last box, indicating a continuous loop of transmission with increasing timing offsets.](4621799daaf18ba4b3b6ada011a1ba10_img.jpg) + +Figure 8.2.9.4.2-2: Timing offset scheme for MsgA transmission for BS type 1-C and type 1-H with 15 kHz SCS. The diagram shows a horizontal timeline with 19 boxes representing time intervals. Below the boxes, time values are marked from 0us to 3.8us in 0.2us increments. A curved arrow starts at the 0us mark and loops back to it after the last box, indicating a continuous loop of transmission with increasing timing offsets. + +**Figure 8.2.9.4.2-2: Timing offset scheme for MsgA transmission for BS type 1-C and type 1-H with 15 kHz SCS** + +- 7) For each of the reference channels in table 8.2.9.5-1 to 8.2.9.5-4 applicable for the base station, measure the BLER. + +## 8.2.9.5 Test Requirement + +The BLER measured according to clause 8.2.9.4.2 shall not be below the limits for the SNR levels specified in Table 8.2.9.5-1 to 8.2.9.5-4. Unless stated otherwise, the MIMO correlation metrics for the gNB are defined in Annex G for low correlation. + +**Table 8.2.9.5-1: Test requirements for msgA PUSCH for 2-step RA type, Type A, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions (Annex G) | BLER | FRC (Annex A) | Time offset [ $\mu\text{s}$ ] (Note 1) | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|------|--------------------------|----------------------------------------|----------| +| 1 | 2 | Normal | TDLC300-100 | 1% | G-FR1-A7-1 or G-FR1-A7-3 | 0, 0.2, 3.8 | 7.9 | + +Note 1: The time offset values are described as X, Y, Z where X is the first TO value, Y is the step in which the TO should be incremented, and Z is the largest TO value in the range. + +**Table 8.2.9.5-2: Test requirements for msgA PUSCH for 2-step RA type, Type A, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions (Annex G) | BLER | FRC (Annex A) | Time offset [ $\mu\text{s}$ ] (Note 1) | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|------|--------------------------|----------------------------------------|----------| +| 1 | 2 | Normal | TDLC300-100 | 1% | G-FR1-A7-2 or G-FR1-A7-4 | 0, 0.1, 2.0 | 7.7 | + +Note 1: The time offset values are described as X, Y, Z where X is the first TO value, Y is the step in which the TO should be incremented, and Z is the largest TO value in the range. + +**Table 8.2.9.5-3: Test requirements for msgA PUSCH for 2-step RA type, Type B, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions (Annex G) | BLER | FRC (Annex A) | Time offset [ $\mu\text{s}$ ] (Note 1) | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|------|--------------------------|----------------------------------------|----------| +| 1 | 2 | Normal | TDLC300-100 | 1% | G-FR1-A7-1 or G-FR1-A7-3 | 0, 0.2, 3.8 | 7.6 | + +Note 1: The time offset values are described as X, Y, Z where X is the first TO value, Y is the step in which the TO should be incremented, and Z is the largest TO value in the range. + +**Table 8.2.9.5-4: Test requirements for msgA PUSCH for 2-step RA type, Type B, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions (Annex G) | BLER | FRC (Annex A) | Time offset [ $\mu\text{s}$ ] (Note 1) | SNR (dB) | +|-----------------------|-----------------------|---------------|----------------------------------|------|--------------------------|----------------------------------------|----------| +| 1 | 2 | Normal | TDLC300-100 | 1% | G-FR1-A7-2 or G-FR1-A7-4 | 0, 0.1, 2.0 | 8.2 | + +Note 1: The time offset values are described as X, Y, Z where X is the first TO value, Y is the step in which the TO should be incremented, and Z is the largest TO value in the range. + +## 8.2.10 Requirements for interlaced PUSCH + +### 8.2.10.1 Definition and applicability + +The performance requirement of PUSCH with interlace allocation is determined by a minimum required throughput for a given SNR. The required throughput is expressed as a fraction of maximum throughput for the FRCs listed in annex A. The performance requirements assume HARQ retransmissions. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2.5. + +### 8.2.10.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2] clause 8.2.10. + +### 8.2.10.3 Test Purpose + +The test shall verify the receiver's ability to achieve throughput under multipath fading propagation conditions for a given SNR + +### 8.2.10.4 Method of test + +#### 8.2.10.4.1 Initial Conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +RF channels to be tested for carrier aggregation: $M_{BW\ Channel\ CA}$ ; see clause 4.9.1. + +#### 8.2.10.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *type 1-H* respectively. +- 2) Adjust the AWGN generator, according to the channel bandwidth, defined in table 8.2.10.4.2-1. + +**Table 8.2.10.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------| +| 15 | 20 | -80.2 dBm / 19.08MHz | +| 30 | 20 | -80.4 dBm / 18.36MHz | +| NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. | | | + +- 3) The characteristics of the wanted signal shall be configured according to the corresponding UL reference measurement channel defined in annex A and the test parameters in table 8.2.10.4.2-2 + +**Table 8.2.10.4.2-2: Test parameters for testing PUSCH** + +| Parameter | | Value | +|--------------------------------------------------------------------------------------------|-------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Transform precoding | | Disabled | +| Default TDD UL-DL pattern (Note 1) | | 15 kHz SCS:
3D1S1U, S=10D:2G:2U
30 kHz SCS:
7D1S2U, S=6D:4G:4U | +| HARQ | Maximum number of HARQ transmissions | 4 | +| | RV sequence | 0, 2, 3, 1 | +| DM-RS | DM-RS configuration type | 1 | +| | DM-RS duration | single-symbol DM-RS | +| | Additional DM-RS position | pos1 | +| | Number of DM-RS CDM group(s) without data | 2 | +| | Ratio of PUSCH EPRE to DM-RS EPRE | -3 dB | +| | DM-RS port(s) | 0 | +| | DM-RS sequence generation | $N_{ID}^0=0, n_{SCID}=0$ | +| Time domain resource assignment | PUSCH mapping type | A, B | +| | Start symbol | 0 | +| | Allocation length | 14 | +| Frequency domain resource assignment | RB assignment | Full applicable test bandwidth.
First interlace with RBs 0,10,20,...,100 are allocated for tests with 15kHz and first interlace with RBs 0,5,10,...,50 are allocated for tests with 30kHz. | +| | Frequency hopping | Disabled | +| Code block group based PUSCH transmission | | Disabled | +| NOTE 1: The same requirements are applicable to FDD and TDD with different UL-DL patterns. | | | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjust the equipment so that required SNR specified in table 8.2.1.5-1 to 8.2.1.5-18 is achieved at the BS input. +- 6) For each of the reference channels in table 8.2.1.5-1 to 8.2.1.5-18 applicable for the base station, measure the throughput. + +## 8.2.10.5 Test Requirement + +The throughput measured according to clause 8.2.10.4.2 shall not be below the limits for the SNR levels specified in tables 8.2.10.5-1 to 8.2.10.5-4. + +**Table 8.2.10.5-1: Minimum requirements for PUSCH with 70% of maximum throughput, Type A, 20 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | 70% | G-FR1-A5-15 | pos1 | 12.9 | + +**Table 8.2.10.5-2: Minimum requirements for PUSCH with 70% of maximum throughput, Type A, 20 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | 70% | G-FR1-A5-16 | pos1 | 12.8 | + +**Table 8.2.10.2-3: Minimum requirements for PUSCH with 70% of maximum throughput, Type B, 20 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | 70% | G-FR1-A5-15 | pos1 | 12.9 | + +**Table 8.2.10.2-4: Minimum requirements for PUSCH with 70% of maximum throughput, Type B, 20 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | 70% | G-FR1-A5-16 | pos1 | 12.8 | + +## 8.2.11 Performance requirements for CG-UCI multiplexed on interlaced PUSCH + +### 8.2.11.1 Definition and applicability + +The performance requirement of CG-UCI multiplexed on interlaced PUSCH is determined by the parameter: block error probability (BLER) of CG-UCI. The performance is measured by the required SNR at block error probability of CG-UCI not exceeding 1 %. + +The CG-UCI BLER is defined as the probability of incorrectly decoding the CG-UCI information when the CG-UCI information is sent. + +In the test of UCI multiplexed on interlaced PUSCH, the UCI information only contains CG-UCI information, there is no HACK/ACK, CSI part 1 or CSI part 2 information transmitted. + +The 18 bits CG-UCI information is further defined with the bitmap [c0 c1 c2 ... c17] as follows: + +- HARQ process number: [c0 c1 c2 c3] = [ 0 0 0 1 ] +- RV sequence: [c4 c5] = [0 0] +- NDI: [c6] = [1] +- COT sharing information field: [c7 c8 ... c17] = [0 0 0 0 0 0 0 0 0 0] + +In the test, PUSCH data and CG-UCI are transmitted simultaneously. + +Which specific test(s) is applicable to BS is based on the test applicability rule defined in clause 8.1.2 + +### 8.2.11.2 Minimum Requirements + +The minimum requirements are in TS 38.104 [2] clause 8.2.11. + +### 8.2.11.3 Test purpose + +The test shall verify the receiver's ability to detect CG-UCI multiplexed on interlaced PUSCH under multipath fading propagation conditions for a given SNR. + +### 8.2.11.4 Method of test + +#### 8.2.11.4.1 Initial conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +#### 8.2.11.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *type 1-H* respectively. +- 2) Adjust the AWGN generator, according to combination of SCS and channel bandwidth defined in table 8.2.11.4.2-1. + +**Table 8.2.11.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 | 20 | -80.2 dBm / 19.08MHz | +| 30 | 20 | -80.4 dBm / 18.36 MHz | + +- 3) The characteristics of the wanted signal shall be configured according to the corresponding UL reference measurement channel defined in annex A and the specific test parameters are configured as below. The CG-UCI information bit payload per slot is equal to 18 bits. + +**Table: 8.2.11.4.2-2: Test parameters for testing CG-UCI multiplexed on interlaced PUSCH** + +| Parameter | | Value | +|-------------------------------------------|-------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Transform precoding | | Disabled | +| Default TDD UL-DL pattern | | 15 kHz SCS:
3D1S1U, S=10D:2G:2U
30 kHz SCS:
7D1S2U, S=6D:4G:4U | +| HARQ | Maximum number of HARQ transmissions | 1 | +| | RV sequence | 0 | +| DM-RS | DM-RS configuration type | 1 | +| | DM-RS duration | Single-symbol DM-RS | +| | Additional DM-RS position | pos1 | +| | Number of DM-RS CDM group(s) without data | 2 | +| | Ratio of PUSCH EPRE to DM-RS EPRE | -3 dB | +| | DM-RS port(s) | {0} | +| | DM-RS sequence generation | $N_{ID}^0 = 0, n_{scid} = 0$ | +| | DM-RS sequence generation | $N_{ID}^0 = 0, n_{scid} = 0$ | +| Time domain resource assignment | PUSCH mapping type | A, B | +| | Start symbol | 0 | +| | Allocation length | 14 | +| Frequency domain resource assignment | RB assignment | Full applicable test bandwidth. First interlace with RBs 0, 10, 20, ..., 100 are allocated for tests with 15kHz SCS and first interlace with RBs 0, 5, 10, ..., 50 are allocated for tests with 30kHz SCS. | +| | Frequency hopping | Disabled | +| Code block group based PUSCH transmission | | Disabled | +| CG-UC | Number of CG-UCI information bits | 18 | +| | Scaling | 1 | +| | betaOffsetCG-UCI-Index1 | 8 | +| | UCI pattern for frequency hopping | Disabled | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjust the equipment so that required SNR specified in table 8.2.11.5-1 to 8.2.11.5-4 is achieved at the BS input during the CG-UCI multiplexed on interlaced PUSCH transmissions. +- 6) The signal generators send a test pattern where CG-UCI can be multiplexed on interlaced PUSCH. The following statistics are kept: the number of incorrectly decoded CG-UCI information during UCI multiplexed on PUSCH transmission. + +## 8.2.11.5 Test Requirement + +The fractional of incorrectly decoded CG-UCI according to clause 8.2.11.4.2 shall be less than 1 % for SNR listed in table 8.2.11.5-1 to table 8.2.11.5-4. + +**Table 8.2.11.5-1: Test requirements for CG-UCI multiplexed on interlace PUSCH, Type A, 20 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | CG-UCI bits | Additional DM-RS position | FRC (Annex A) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------------------|---------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | 18 | pos1 | G-FR1-A5-15 | 5.2 | + +**Table 8.2.11.5-2: Test requirements for CG-UCI multiplexed on interlaced PUSCH, Type A, 20 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | CG-UCI bits | Additional DM-RS position | FRC (Annex A) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------------------|---------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | 18 | pos1 | G-FR1-A5-16 | 5.3 | + +**Table 8.2.11.5-3: Test requirements for CG-UCI multiplexed on interlaced PUSCH, Type B, 20 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | CG-UCI bits | Additional DM-RS position | FRC (Annex A) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------------------|---------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | 18 | pos1 | G-FR1-A5-15 | 5.2 | + +**Table 8.2.11.5-4: Test requirements for CG-UCI multiplexed on interlaced PUSCH, Type B, 20 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | CG-UCI bits | Additional DM-RS position | FRC (Annex A) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|-------------|---------------------------|---------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | 18 | pos1 | G-FR1-A5-16 | 5.6 | + +## 8.2.12 Performance requirements for TB processing over multi-slot PUSCH (TBOMS) + +### 8.2.12.1 Definition and applicability + +The performance requirement of PUSCH TBOMS is determined by a minimum required throughput for a given SNR. The required throughput is expressed as a fraction of maximum throughput for the FRCs listed in annex A. The performance requirements assume HARQ retransmissions. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2.8. + +### 8.2.12.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2] clause 8.2.12. + +### 8.2.12.3 Test Purpose + +The test shall verify the receiver's ability to achieve throughput under multipath fading propagation conditions for a given SNR. + +### 8.2.12.4 Method of test + +#### 8.2.12.4.1 Initial Conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +RF channels to be tested for carrier aggregation: $M_{BW\ Channel\ CA}$ ; see clause 4.9.1. + +#### 8.2.12.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *type 1-H* respectively. +- 2) Adjust the AWGN generator, according to the channel bandwidth, defined in table 8.2.12.4.2-1. + +**Table 8.2.12.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------| +| 15 kHz | 5 | -86.5 dBm / 4.5MHz | +| 30 kHz | 10 | -83.6 dBm / 8.64MHz | +| NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. | | | + +- 3) The characteristics of the wanted signal shall be configured according to the corresponding UL reference measurement channel defined in annex A and the test parameters in table 8.2.12.4.2-2. + +**Table 8.2.12.4.2-2: Test parameters for testing PUSCH TBoMS** + +| Parameter | | Value | +|-----------------------------------------------------------------------------------|-------------------------------------------|-------------------------------------------------------------------------| +| Transform precoding | | Disabled | +| Default TDD UL-DL pattern (Note 1) | | 15 kHz SCS:
3D1S1U, S=10D:2G:2U
30 kHz SCS:
7D1S2U, S=6D:4G:4U | +| HARQ | Maximum number of HARQ transmissions | 4 | +| | RV sequence | 0, 2, 3, 1 | +| DM-RS | DM-RS configuration type | 1 | +| | DM-RS duration | single-symbol DM-RS | +| | Additional DM-RS position | pos1 | +| | Number of DM-RS CDM group(s) without data | 2 | +| | Ratio of PUSCH EPRE to DM-RS EPRE | -3 dB | +| | DM-RS port | 0 | +| | DM-RS sequence generation | $N_{id}^0=0, n_{scid}=0$ | +| Time domain resource assignment | PUSCH mapping type | A, B | +| | Start symbol | 0 | +| | Allocation length | 14 | +| | Number of slots allocated for TBoMS PUSCH | 4 for FDD
2 for TDD | +| | Number of repetitions of a single TBoMS | 1 | +| Frequency domain resource assignment | RB assignment | 5 RBs in the middle of the test bandwidth | +| | Frequency hopping | Disabled | +| Code block group based PUSCH transmission | | Disabled | +| Note 1: The same requirements are applicable to TDD with different UL-DL pattern. | | | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjust the equipment so that required SNR specified in table 8.2.12.5-1 to 8.2.12.5-4 is achieved at the BS input. +- 6) For each of the reference channels in table 8.2.12.5-1 to 8.2.12.5-4 applicable for the base station, measure the throughput. + +## 8.2.12.5 Test Requirement + +The throughput measured according to clause 8.2.12.4.2 shall not be below the limits for the SNR levels specified in table 8.2.12.5-1 to 8.2.12.5-4. + +**Table 8.2.12.5-1: Test requirements for PUSCH TBoMS, Type A, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Duplex | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|--------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | FDD | TDLB100-400 Low | 70% | G-FR1-A3-36 | pos1 | -1.7 | +| 1 | 2 | Normal | TDD | TDLB100-400 Low | 70% | G-FR1-A3-35 | pos1 | -1.9 | + +**Table 8.2.12.5-2: Test requirements for PUSCH TBoMS, Type A, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Duplex | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|--------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | FDD | TDLB100-400 Low | 70% | G-FR1-A3-38 | pos1 | -1.8 | +| 1 | 2 | Normal | TDD | TDLB100-400 Low | 70% | G-FR1-A3-37 | pos1 | -1.9 | + +**Table 8.2.12.5-3: Test requirements for PUSCH TBoMS, Type B, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Duplex | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|--------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | FDD | TDLB100-400 Low | 70% | G-FR1-A3-36 | pos1 | -1.5 | +| 1 | 2 | Normal | TDD | TDLB100-400 Low | 70% | G-FR1-A3-35 | pos1 | -1.9 | + +**Table 8.2.12.5-4: Test requirements for PUSCH TBoMS, Type B, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Duplex | Propagation conditions and correlation matrix (Annex G) | Fraction of maximum throughput | FRC (Annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|--------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | FDD | TDLB100-400 Low | 70% | G-FR1-A3-38 | pos1 | -1.8 | +| 1 | 2 | Normal | TDD | TDLB100-400 Low | 70% | G-FR1-A3-37 | pos1 | -1.9 | + +## 8.2.13 Performance requirements for PUSCH with DMRS bundling + +### 8.2.13.1 Definition and applicability + +The performance requirement of PUSCH with DMRS bundling is determined by a minimum required throughput for a given SNR. The required throughput is expressed as a fraction of maximum throughput for the FRCs listed in annex A. The performance requirements assume HARQ re-transmissions. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2.9. + +### 8.2.13.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2] clause 8.2.13. + +### 8.2.13.3 Test Purpose + +The test shall verify the receiver's ability to achieve throughput under multipath fading propagation conditions for a given SNR with DMRS bundling. + +### 8.2.13.4 Method of test + +#### 8.2.13.4.1 Initial Conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: $M$ ; see clause 4.9.1. + +RF channels to be tested for carrier aggregation: $M_{\text{BW Channel CA}}$ ; see clause 4.9.1. + +#### 8.2.13.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *type 1-H* respectively. +- 2) Adjust the AWGN generator, according to the channel bandwidth, defined in table 8.2.13.4.2-1. + +**Table 8.2.13.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------| +| 15kHz | 5 | -86.5 dBm / 4.5MHz | +| 30kHz | 10 | -83.6 dBm / 8.64MHz | +| NOTE: | The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. | | + +- 3) The characteristics of the wanted signal shall be configured according to the corresponding UL reference measurement channel defined in annex A and the test parameters in table 8.2.13.4.2-2. + +**Table 8.2.13.4.2-2: Test parameters for testing PUSCH with DMRS bundling** + +| Parameter | | Value | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|------------------------------------------| +| Transform precoding | | Disabled | +| Example TDD UL-DL pattern (Note 1) | | 7D1S2U, S=6D:4G:4U | +| HARQ | Maximum number of HARQ transmissions | 4 | +| | RV sequence (Note 2) | 0, 3, 0, 3 for TDD
0, 0, 0, 0 for FDD | +| DM-RS | DM-RS configuration type | 1 | +| | DM-RS duration | single-symbol DM-RS | +| | Additional DM-RS position | pos0, pos1 | +| | Number of DM-RS CDM group(s) without data | 2 | +| | Ratio of PUSCH EPRE to DM-RS EPRE | -3 dB | +| | DM-RS port(s) | {0} | +| | DM-RS sequence generation | $N_{ID}^0=0, n_{scid}=0$ | +| Time domain resource assignment | PUSCH mapping type | A, B | +| | Start symbol | 0 | +| | Allocation length | 14 | +| | PUSCH aggregation factor | 8 slots for FDD
2 slots for TDD | +| pusch-TimeDomainWindowLength | | 2 for TDD
8 for FDD | +| Frequency domain resource assignment | RB assignment | Full applicable test bandwidth | +| | Frequency hopping | Disabled | +| Code block group based PUSCH transmission | | Disabled | +| NOTE 1: The same TDD requirements are applicable to different UL-DL patterns with more than one consecutive UL slots when both pusch-TimeDomainWindowLength and PUSCH aggregation factor are configured as 2 slots. The UL (re)transmission of PUSCH is only scheduled for the actual TDW including 2 consecutive UL slots. | | | +| NOTE 2: The effective RV sequence is {0, 2, 3, 1} with slot aggregation. | | | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjust the equipment so that required SNR specified in table 8.2.13.5-1 to table 8.2.13.5-8 is achieved at the BS input. +- 6) For each of the reference channels in table 8.2.13.5-1 to table 8.2.13.5-8 applicable for the base station, measure the throughput. + +## 8.2.13.5 Test Requirement + +The throughput measured according to clause 8.2.13.4.2 shall not be below the limits for the SNR levels specified in table 8.2.13.5-1 to table 8.2.13.5-8. + +**Table 8.2.13.5-1: Test requirements for PUSCH with 70% of maximum throughput, Type A, 5 MHz channel bandwidth, FDD 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-7 | pos0 | -9.3 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-5 | pos1 | -7.3 | +| | 4 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-7 | pos0 | -11.7 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-5 | pos1 | -11.2 | +| | 8 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-7 | pos0 | -15.0 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-5 | pos1 | -14.4 | + +**Table 8.2.13.5-2: Test requirements for PUSCH with 70% of maximum throughput, Type A, 5 MHz channel bandwidth, TDD 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-7 | pos0 | -3.0 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-5 | pos1 | -2.0 | +| | 4 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-7 | pos0 | -6.2 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-5 | pos1 | -5.6 | +| | 8 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-7 | pos0 | -10.0 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-5 | pos1 | -8.8 | + +**Table 8.2.13.5-3: Test requirements for PUSCH with 70% of maximum throughput, Type A, 10 MHz channel bandwidth, FDD 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-8 | pos0 | -8.9 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-6 | pos1 | -9.2 | +| | 4 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-8 | pos0 | -12.5 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-6 | pos1 | -12.4 | +| | 8 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-8 | pos0 | -15.2 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-6 | pos1 | -14.7 | + +**Table 8.2.13.5-4: Test requirements for PUSCH with 70% of maximum throughput, Type A, 10 MHz channel bandwidth, TDD 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-8 | pos0 | -3.2 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-6 | pos1 | -2.3 | +| | 4 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-8 | pos0 | -6.4 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-6 | pos1 | -5.9 | +| | 8 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-8 | pos0 | -9.7 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-6 | pos1 | -9.7 | + +| | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------|------------------------------|----------------------|----------------------------------------------------------------|---------------------------------------|----------------------|----------------------------------|-----------------| +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-6 | pos1 | -9.1 | +| Table 8.2.13.5-5: Test requirements for PUSCH with 70% of maximum throughput, Type B, 5 MHz channel bandwidth, FDD 15 kHz SCS | | | | | | | | +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +| 1 | 2 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-7 | pos0 | -9.3 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-5 | pos1 | -7.7 | +| | 4 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-7 | pos0 | -11.7 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-5 | pos1 | -11.2 | +| | 8 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-7 | pos0 | -15.0 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-5 | pos1 | -14.4 | +| Table 8.2.13.5-6: Test requirements for PUSCH with 70% of maximum throughput, Type B, 5 MHz channel bandwidth, TDD 15 kHz SCS | | | | | | | | +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +| 1 | 2 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-7 | pos0 | -2.8 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-5 | pos1 | -2.0 | +| | 4 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-7 | pos0 | -6.2 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-5 | pos1 | -5.7 | +| | 8 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-7 | pos0 | -10.0 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-5 | pos1 | -8.8 | +| Table 8.2.13.5-7: Test requirements for PUSCH with 70% of maximum throughput, Type B, 10 MHz channel bandwidth, FDD 30 kHz SCS | | | | | | | | +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +| 1 | 2 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-8 | pos0 | -8.9 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-6 | pos1 | -9.2 | +| | 4 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-8 | pos0 | -12.5 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-6 | pos1 | -12.7 | +| | 8 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-8 | pos0 | -15.2 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-6 | pos1 | -14.9 | + +**Table 8.2.13.5-8: Test requirements for PUSCH with 70% of maximum throughput, Type B, 10 MHz channel bandwidth, TDD 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic prefix | Propagation conditions and correlation matrix (annex G) | Fraction of maximum throughput | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------------|---------------------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-8 | pos0 | -2.7 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-6 | pos1 | -2.2 | +| | 4 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-8 | pos0 | -6.4 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-6 | pos1 | -5.9 | +| | 8 | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-8 | pos0 | -9.7 | +| | | Normal | TDLA30-10 Low | 70 % | G-FR1-A3B-6 | pos1 | -9.1 | + +## 8.3 Performance requirements for PUCCH + +### 8.3.1 Performance requirements for PUCCH format 0 + +#### 8.3.1.1 Definition and applicability + +The performance requirement of single user PUCCH format 0 for ACK missed detection is determined by the two parameters: probability of false detection of the ACK and the probability of detection of ACK. The performance is measured by the required SNR at probability of detection equal to 0.99. The probability of false detection of the ACK shall be 0.01 or less. + +The probability of false detection of the ACK is defined as a conditional probability of erroneous detection of the ACK when input is only noise. + +The probability of detection of ACK is defined as conditional probability of detection of the ACK when the signal is present. + +The transient period as specified in TS 38.101-1 [21] clause 6.3.3.1 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the CC center, i.e. intra-slot frequency hopping is enabled. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2. + +#### 8.3.1.2 Minimum Requirement + +The minimum requirements are in TS 38.104 [2] clause 8.3.1 and 8.3.2. + +#### 8.3.1.3 Test purpose + +The test shall verify the receiver's ability to detect ACK under multipath fading propagation conditions for a given SNR. + +#### 8.3.1.4 Method of test + +##### 8.3.1.4.1 Initial conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested: single carrier M; see clause 4.9.1. + +### 8.3.1.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *type 1-H* respectively. +- 2) Adjust the AWGN generator, according to the channel bandwidth and sub-carrier spacing defined in table 8.3.1.4.2-1. + +**Table 8.3.1.4.2-1: AWGN power level at the BS input** + +| Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------------------|-------------------------|-----------------------| +| 15 | 5 | -83.5 dBm / 4.5 MHz | +| | 10 | -80.3 dBm / 9.36 MHz | +| | 20 | -77.2 dBm / 19.08 MHz | +| 30 | 10 | -80.6 dBm / 8.64 MHz | +| | 20 | -77.4 dBm / 18.36 MHz | +| | 40 | -74.2 dBm / 38.16 MHz | +| | 100 | -70.1 dBm / 98.28 MHz | + +NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [17] and the specific test parameters are configured as mentioned in table 8.3.1.4.2-2: + +**Table 8.3.1.4.2-2: Test Parameters** + +| Parameter | Test | +|--------------------------------------|----------------------------------------------| +| number of UCI information bits | 1 | +| Number of PRBs | 1 | +| First PRB prior to frequency hopping | 0 | +| Intra-slot frequency hopping | N/A for 1 symbol
Enabled for 2 symbols | +| First PRB after frequency hopping | The largest PRB index – (Number of PRBs – 1) | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Initial cyclic shift | 0 | +| First symbol | 13 for 1 symbol
12 for 2 symbols | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex B. +- 5) Adjust the equipment so that the SNR specified in table 8.3.1.5-1 or table 8.3.1.5-2 is achieved at the BS input during the ACK transmissions. +- 6) The signal generator sends a test pattern with the pattern outlined in figure 8.3.1.4.2-1. The following statistics are kept: the number of ACKs detected in the idle periods and the number of missed ACKs. + +![Figure 8.3.1.4.2-1: Test signal pattern for single user PUCCH format 0 demodulation tests. The diagram shows three boxes labeled 'ACK' followed by three dots, representing a sequence of ACK signals.](00bb8c9fd2ec7fa7da34a98f824468b6_img.jpg) + +Figure 8.3.1.4.2-1: Test signal pattern for single user PUCCH format 0 demodulation tests. The diagram shows three boxes labeled 'ACK' followed by three dots, representing a sequence of ACK signals. + +**Figure 8.3.1.4.2-1: Test signal pattern for single user PUCCH format 0 demodulation tests** + +### 8.3.1.5 Test Requirement + +The fraction of falsely detected ACKs shall be less than 1% and the fraction of correctly detected ACKs shall be larger than 99% for the SNR listed in table 8.3.1.5-1 and in table 8.3.1.5-2. + +**Table 8.3.1.5-1: Test requirements for PUCCH format 0 and 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex G) | Number of OFDM symbols | Channel bandwidth / SNR (dB) | | | +|-----------------------|-----------------------|---------------------------------------------------------|------------------------|------------------------------|--------|--------| +| | | | | 5 MHz | 10 MHz | 20 MHz | +| 1 | 2 | TDLC-300-100 Low | 1 | 10.0 | 9.4 | 9.9 | +| | | | 2 | 3.4 | 4.3 | 3.9 | +| 1 | 4 | TDLC-300-100 Low | 1 | 3.6 | 3.5 | 3.8 | +| | | | 2 | -0.4 | 0.1 | -0.2 | +| 1 | 8 | TDLC-300-100 Low | 1 | -0.5 | -0.5 | -0.5 | +| | | | 2 | -3.5 | -3.3 | -3.4 | + +**Table 8.3.1.5-2: Test requirements for PUCCH format 0 and 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex G) | Number of OFDM symbols | Channel bandwidth / SNR (dB) | | | | +|-----------------------|-----------------------|---------------------------------------------------------|------------------------|------------------------------|--------|--------|---------| +| | | | | 10 MHz | 20 MHz | 40 MHz | 100 MHz | +| 1 | 2 | TDLC-300-100 Low | 1 | 10.4 | 10.4 | 10.1 | 9.8 | +| | | | 2 | 4.8 | 4.2 | 4.4 | 4.1 | +| 1 | 4 | TDLC-300-100 Low | 1 | 4.0 | 4.0 | 3.6 | 3.9 | +| | | | 2 | 0.3 | 0.2 | 0.1 | -0.2 | +| 1 | 8 | TDLC-300-100 Low | 1 | -0.4 | -0.4 | -0.5 | -0.4 | +| | | | 2 | -3.1 | -3.2 | -3.4 | -3.3 | + +## 8.3.2 Performance requirements for PUCCH format 1 + +### 8.3.2.1 NACK to ACK detection + +#### 8.3.2.1.1 Definition and applicability + +The performance requirement of PUCCH format 1 for NACK to ACK detection is determined by the two parameters: probability of false detection of the ACK and the NACK to ACK detection probability. The performance is measured by the required SNR at probability of the NACK to ACK detection equal to 0.1% or less. The probability of false detection of the ACK shall be 0.01 or less. + +The probability of false detection of the ACK is defined as a conditional probability of erroneous detection of the ACK at particular bit position when input is only noise. Each false bit detection is counted as one error. + +The NACK to ACK detection probability is the probability of detecting an ACK bit when an NACK bit was sent on particular bit position. Each NACK bit erroneously detected as ACK bit is counted as one error. Erroneously detected NACK bits in the definition do not contain the NACK bits which are mapped from DTX, i.e. NACK bits received when DTX is sent should not be considered. + +The transient period as specified in TS 38.101-1 [21] clause 6.3.3.1 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the CC center, i.e. intra-slot frequency hopping is enabled. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2. + +#### 8.3.2.1.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2] clause 8.3.3. + +#### 8.3.2.1.3 Test purpose + +The test shall verify the receiver's ability not to falsely detect NACK bits as ACK bits under multipath fading propagation conditions for a given SNR. + +#### 8.3.2.1.4 Method of test + +##### 8.3.2.1.4.1 Initial Conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested: for single carrier: M; see clause 4.9.1. + +##### 8.3.2.1.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *type 1-H* respectively. +- 2) Adjust the AWGN generator, according to the combinations of SCS and channel bandwidth defined in table 8.3.2.1.4.2-1. + +**Table 8.3.2.1.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 kHz | 5 | -83.5 dBm / 4.5 MHz | +| | 10 | -80.3 dBm / 9.36 MHz | +| | 20 | -77.2 dBm / 19.08 MHz | +| 30 kHz | 10 | -80.6 dBm / 8.64 MHz | +| | 20 | -77.4 dBm / 18.36 MHz | +| | 40 | -74.2 dBm / 38.16 MHz | +| | 100 | -70.1 dBm / 98.28 MHz | + +NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [17], and the specific test parameters are configured as below: + +**Table 8.3.2.1.4.2-2: Test parameters** + +| Parameter | Values | +|---------------------------------------------------------|------------------------------------------| +| Number of information bits | 2 | +| Number of PRBs | 1 | +| Number of symbols | 14 | +| First PRB prior to frequency hopping | 0 | +| Intra-slot frequency hopping | enabled | +| First PRB after frequency hopping | The largest PRB index -
(nrofPRBs -1) | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Initial cyclic shift | 0 | +| First symbol | 0 | +| Index of orthogonal cover code ( timeDomainOCC ) | 0 | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjusting the equipment so that the SNR specified in table 8.3.2.1.5-1 and table 8.3.2.1.5-2 is achieved at the BS input during the transmissions. +- 6) The signal generator sends random codeword from applicable codebook, in regular time periods. The following statistics are kept: the number of ACK bits detected in the idle periods and the number of NACK bits detected as ACK. + +#### 8.3.2.1.5 Test Requirement + +The fraction of falsely detected ACK bits shall be less than 1% and the fraction of NACK bits falsely detected as ACK shall be less than 0.1% for the SNR listed in tables 8.3.2.1.5-1 and table 8.3.2.1.5-2. + +**Table 8.3.2.1.5-1: Required SNR for PUCCH format 1 with 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Channel bandwidth / SNR (dB) | | | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|------------------------------|--------|--------| +| | | | | 5 MHz | 10 MHz | 20 MHz | +| 1 | 2 | Normal | TDLC-300-100 Low | -3.2 | -3.0 | -3.0 | +| | 4 | Normal | TDLC-300-100 Low | -7.8 | -7.0 | -7.8 | +| | 8 | Normal | TDLC-300-100 Low | -11.2 | -10.8 | -10.8 | + +**Table 8.3.2.1.5-2: Required SNR for PUCCH format 1 with 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Channel bandwidth / SNR (dB) | | | | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|------------------------------|--------|--------|---------| +| | | | | 10 MHz | 20 MHz | 40 MHz | 100 MHz | +| 1 | 2 | Normal | TDLC-300-100 Low | -2.2 | -2.7 | -3.3 | -2.9 | +| | 4 | Normal | TDLC-300-100 Low | -7.5 | -7.7 | -6.9 | -7.4 | +| | 8 | Normal | TDLC-300-100 Low | -10.9 | -10.6 | -10.1 | -10.7 | + +### 8.3.2.2 ACK missed detection + +#### 8.3.2.2.1 Definition and applicability + +The performance requirement of PUCCH format 1 for ACK missed detection is determined by the two parameters: probability of false detection of the ACK and the probability of detection of ACK. The performance is measured by the required SNR at probability of detection equal to 0.99. The probability of false detection of the ACK shall be 0.01 or less. + +The probability of false detection of the ACK is defined as a conditional probability of erroneous detection of the ACK when input is only noise. + +The probability of detection of ACK is defined as conditional probability of detection of the ACK when the signal is present. + +The transient period as specified in TS 38.101-1 [21] clause 6.3.3.1 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the CC center, i.e. intra-slot frequency hopping is enabled. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2. + +#### 8.3.2.2.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2] clause 8.3.3. + +#### 8.3.2.2.3 Test purpose + +The test shall verify the receiver's ability to detect ACK bits under multipath fading propagation conditions for a given SNR. + +#### 8.3.2.2.4 Method of test + +##### 8.3.2.2.4.1 Initial Conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested: for single carrier (SC): M; see clause 4.9.1. + +##### 8.3.2.2.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type I-C* and *type I-H* respectively. + +- 2) Adjust the AWGN generator, according to the combinations of SCS and channel bandwidth defined in table 8.3.2.2.4.2-1. + +**Table 8.3.2.2.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 kHz | 5 | -83.5 dBm / 4.5 MHz | +| | 10 | -80.3 dBm / 9.36 MHz | +| | 20 | -77.2 dBm / 19.08 MHz | +| 30 kHz | 10 | -80.6 dBm / 8.64 MHz | +| | 20 | -77.4 dBm / 18.36 MHz | +| | 40 | -74.2 dBm / 38.16 MHz | +| | 100 | -70.1 dBm / 98.28 MHz | + +NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [17], and the specific test parameters are configured as below: + +**Table 8.3.2.2.4.2-2: Test parameters** + +| Parameter | Values | +|---------------------------------------------------------|-------------------------------------------| +| Number of information bits | 2 | +| Number of PRBs | 1 | +| Number of symbols | 14 | +| First PRB prior to frequency hopping | 0 | +| Intra-frequency hopping | enabled | +| First PRB after frequency hopping | The largest PRB index -
(nrofPRBs - 1) | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Initial cyclic shift | 0 | +| First symbol | 0 | +| Index of orthogonal cover code ( timeDomainOCC ) | 0 | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjusting the equipment so that the SNR specified in table 8.3.2.2.5-1 and table 8.3.2.2.5-2 is achieved at the BS input during the transmissions. +- 6) The signal generator sends random codewords from applicable codebook, in regular time periods. The following statistics are kept: the number of ACK bits falsely detected in the idle periods and the number of missed ACK bits. Each falsely detected ACK bit in the idle periods is accounted as one error for the statistics of false ACK detection, and each missed ACK bit is accounted as one error for the statistics of missed ACK detection. + +Note that the procedure described in this clause for ACK missed detection has the same condition as that described in clause 8.3.2.1.4.2 for NACK to ACK detection. Both statistics are measured in the same testing. + +**Figure 8.3.2.2.4.2-1: Void****8.3.2.2.5 Test Requirement** + +The fraction of falsely detected ACK bits shall be less than 1% and the fraction of correctly detected ACK bits shall be larger than 99% for the SNR listed in tables 8.3.2.2.5-1 and table 8.3.2.2.5-2. + +**Table 8.3.2.2.5-1 Required SNR for PUCCH format 1 with 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Channel bandwidth / SNR (dB) | | | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|------------------------------|--------|--------| +| | | | | 5 MHz | 10 MHz | 20 MHz | +| 1 | 2 | Normal | TDLC300-100 Low | -4.4 | -3.8 | -4.4 | +| | 4 | Normal | TDLC300-100 Low | -8.0 | -7.6 | -7.9 | +| | 8 | Normal | TDLC300-100 Low | -10.1 | -10.9 | -10.9 | + +**Table 8.3.2.2.5-2 Required SNR for PUCCH format 1 with 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Channel bandwidth / SNR (dB) | | | | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|------------------------------|--------|--------|---------| +| | | | | 10 MHz | 20 MHz | 40 MHz | 100 MHz | +| 1 | 2 | Normal | TDLC300-100 Low | -3.3 | -3.8 | -3.8 | -3.6 | +| | 4 | Normal | TDLC300-100 Low | -7.4 | -7.5 | -7.8 | -7.7 | +| | 8 | Normal | TDLC300-100 Low | -10.8 | -10.8 | -10.8 | -10.8 | + +**8.3.3 Performance requirements for PUCCH format 2****8.3.3.1 ACK missed detection****8.3.3.1.1 Definition and applicability** + +The performance requirement of PUCCH format 2 for ACK missed detection is determined by the two parameters: probability of false detection of the ACK and the probability of detection of ACK. The performance is measured by the required SNR at probability of detection equal to 0.99. The probability of false detection of the ACK shall be 0.01 or less. + +The probability of false detection of the ACK is defined as a probability of erroneous detection of the ACK when input is only noise. + +The probability of detection of ACK is defined as probability of detection of the ACK when the signal is present. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2. + +### 8.3.3.1.2 Minimum requirements + +The minimum requirements are in TS 38.104 [2] clause 8.3.4. + +### 8.3.3.1.3 Test purpose + +The test shall verify the receiver's ability to detect ACK bits under multipath fading propagation conditions for a given SNR. + +### 8.3.3.1.4 Method of test + +#### 8.3.3.1.4.1 Initial Condition + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier; M; see clause 4.9.1 + +#### 8.3.3.1.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for BS type 1-C and *type 1-H* respectively. +- 2) Adjust the AWGN generator, according to the channel bandwidth defined in table 8.3.3.1.4.2-1. + +**Table 8.3.3.1.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 | 5 | -83.5 dBm / 4.5 MHz | +| | 10 | -80.3 dBm / 9.36 MHz | +| | 20 | -77.2 dBm / 19.08 MHz | +| 30 | 10 | -80.6 dBm / 8.64 MHz | +| | 20 | -77.4 dBm / 18.36 MHz | +| | 40 | -74.2 dBm / 38.16 MHz | +| | 100 | -70.1 dBm / 98.28 MHz | + +NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [17], and the specific test parameters are configured as blow: + +**Table 8.3.3.1.4.2-2: Test parameters** + +| Parameter | Values | +|------------------------------------|--------------| +| Modulation order | QPSK | +| Starting RB location | 0 | +| Intra-slot frequency hopping | N/A | +| Number of PRBs | 4 | +| Number of symbols | 1 | +| The number of UCI information bits | 4 | +| First symbol | 13 | +| DM-RS sequence generation | $N_{ID}^0=0$ | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjust the equipment so that the SNR specified in table 8.3.3.1.5-1 and table 8.3.3.1.5-2 is achieved at the BS input during the UCI transmissions. +- 6) The signal generator sends a test pattern with the pattern outlined in figure 8.3.3.1.4.2-1. The following statistics are kept: the number of ACKs detected in the idle periods and the number of missed ACKs. + +![Figure 8.3.3.1.4.2-1: Test signal pattern for PUCCH format 2 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'ACK', arranged horizontally. To the right of the third box are three dots, indicating a repeating pattern.](236b5a83f488c361479b9b44e462f978_img.jpg) + +Figure 8.3.3.1.4.2-1: Test signal pattern for PUCCH format 2 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'ACK', arranged horizontally. To the right of the third box are three dots, indicating a repeating pattern. + +**Figure 8.3.3.1.4.2-1: Test signal pattern for PUCCH format 2 demodulation tests** + +### 8.3.3.1.5 Test requirements + +The fraction of falsely detected ACKs shall be less than 1% and the fraction of correctly detected ACKs shall be larger than 99% for the SNR listed in table 8.3.3.1.5-1 and table 8.3.3.1.5-2. + +**Table 8.3.3.1.5-1: Required SNR for PUCCH format 2 with 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Channel bandwidth / SNR (dB) | | | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|------------------------------|--------|--------| +| | | | | 5 MHz | 10 MHz | 20 MHz | +| 1 | 2 | Normal | TDLC300-100 Low | 6.4 | 6.2 | 6.5 | +| | 4 | Normal | TDLC300-100 Low | 1.0 | 1.1 | 0.9 | +| | 8 | Normal | TDLC300-100 Low | -2.9 | -2.9 | -2.9 | + +**Table 8.3.3.1.5-2: Required SNR for PUCCH format 2 with 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Channel bandwidth / SNR (dB) | | | | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|------------------------------|-------|-------|--------| +| | | | | 10MHz | 20MHz | 40MHz | 100MHz | +| 1 | 2 | Normal | TDLC300-100 Low | 6.1 | 6.2 | 6.1 | 6.3 | +| | 4 | Normal | TDLC300-100 Low | 0.9 | 0.8 | 0.9 | 1.0 | +| | 8 | Normal | TDLC300-100 Low | -3.0 | -3.0 | -2.9 | -2.7 | + +### 8.3.3.2 UCI BLER performance requirements + +#### 8.3.3.2.1 Definition and applicability + +The performance is measured by the required SNR at UCI block error probability not exceeding 1%. + +The UCI block error probability is defined as the probability of incorrectly decoding the UCI information when the UCI information is sent. The UCI information does not contain CSI part 2. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2 + +The transient period as specified in TS 38.101-1 [21] clause 6.3.3.1 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the CC center, i.e. intra-slot frequency hopping is enabled. + +#### 8.3.3.2.2 Minimum Requirement + +The minimum requirement is TS 38.104 [2] clause 8.3.4. + +#### 8.3.3.2.3 Test purpose + +The test shall verify the receiver's ability to detect UCI under multipath fading propagation conditions for a given SNR. + +#### 8.3.3.2.4 Method of test + +##### 8.3.3.2.4.1 Initial Condition + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier; M; see clause 4.9.1 + +##### 8.3.3.2.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for BS type 1-C and BS type 1-H respectively. +- 2) Adjust the AWGN generator, according to the channel bandwidth defined in table 8.3.3.2.4.2-1. + +**Table 8.3.3.2.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 | 5 | -83.5 dBm / 4.5 MHz | +| | 10 | -80.3 dBm / 9.36 MHz | +| | 20 | -77.2 dBm / 19.08 MHz | +| 30 | 10 | -80.6 dBm / 8.64 MHz | +| | 20 | -77.4 dBm / 18.36 MHz | +| | 40 | -74.2 dBm / 38.16 MHz | +| | 100 | -70.1 dBm / 98.28 MHz | + +NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [17], and the specific test parameters are configured as blow: + +**Table 8.3.3.2.4.2-2: Test parameters** + +| Parameter | Values | +|--------------------------------------|----------------------------------------------| +| Modulation order | QPSK | +| First PRB prior to frequency hopping | 0 | +| Intra-slot frequency hopping | enabled | +| First PRB after frequency hopping | The largest PRB index – (Number of PRBs - 1) | +| Number of PRBs | 9 | +| Number of symbols | 2 | +| The number of UCI information bits | 22 | +| First symbol | 12 | +| DM-RS sequence generation | $N_{ID}^0=0$ | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjust the equipment so that the SNR specified in table 8.3.3.2.5-1 or table 8.3.3.2.5-2 is achieved at the BS input during the UCI transmissions. +- 6) The signal generator sends a test pattern with the pattern outlined in figure 8.3.3.2.4.2-1. The following statistics are kept: the number of incorrectly decoded UCI. + +![Figure 8.3.3.2.4.2-1: Test signal pattern for PUCCH format 2 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'UCI', arranged horizontally. To the right of the third box are three dots (ellipsis), indicating a repeating pattern.](3c34a281971985392326517db208286d_img.jpg) + +Figure 8.3.3.2.4.2-1: Test signal pattern for PUCCH format 2 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'UCI', arranged horizontally. To the right of the third box are three dots (ellipsis), indicating a repeating pattern. + +**Figure 8.3.3.2.4.2-1: Test signal pattern for PUCCH format 2 demodulation tests** + +### 8.3.3.2.5 Test requirements + +The fraction of incorrectly decoded UCI shall be less than 1% for the SNR listed in table 8.3.3.2.5-1 and table 8.3.3.2.5-2. + +**Table 8.3.3.2.5-1: Required SNR for PUCCH format 2 with 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Channel bandwidth / SNR (dB) | | | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|------------------------------|--------|--------| +| | | | | 5 MHz | 10 MHz | 20 MHz | +| 1 | 2 | Normal | TDLC300-100 Low | 0.8 | 1.4 | 1.8 | +| | 4 | Normal | TDLC300-100 Low | -3.0 | -2.6 | -2.6 | +| | 8 | Normal | TDLC300-100 Low | -6.2 | -6.1 | -6.2 | + +**Table 8.3.3.2.5-2: Required SNR for PUCCH format 2 with 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Channel bandwidth / SNR (dB) | | | | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|------------------------------|-------|-------|--------| +| | | | | 10MHz | 20MHz | 40MHz | 100MHz | +| 1 | 2 | Normal | TDLC300-100 Low | 1.1 | 1.7 | 1.0 | 0.9 | +| | 4 | Normal | TDLC300-100 Low | -2.7 | -2.3 | -2.7 | -2.8 | +| | 8 | Normal | TDLC300-100 Low | -5.2 | -5.2 | -6.1 | -5.3 | + +## 8.3.4 Performance requirements for PUCCH format 3 + +### 8.3.4.1 Definition and applicability + +The performance is measured by the required SNR at UCI block error probability not exceeding 1%. + +The UCI block error probability is defined as the conditional probability of incorrectly decoding the UCI information when the UCI information is sent. The UCI information does not contain CSI part 2. + +The transient period as specified in TS 38.101-1 [21] clause 6.3.3.1 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the CC center, i.e. intra-slot frequency hopping is enabled. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2.2. + +### 8.3.4.2 Minimum requirement + +The minimum requirement is in TS 38.104 [2] clause 8.3.5. + +### 8.3.4.3 Test purpose + +The test shall verify the receiver's ability to detect UCI under multipath fading propagation conditions for a given SNR. + +### 8.3.4.4 Method of test + +#### 8.3.4.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1 + +#### 8.3.4.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *BS type 1-H* respectively. +- 2) Adjust the AWGN generator, according to the subcarrier spacing and channel bandwidth defined in table 8.3.4.4.2-1. + +**Table 8.3.4.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 | 5 | -83.5 dBm / 4.5 MHz | +| | 10 | -80.3 dBm / 9.36 MHz | +| | 20 | -77.2 dBm / 19.08 MHz | +| 30 | 10 | -80.6 dBm / 8.64 MHz | +| | 20 | -77.4 dBm / 18.36 MHz | +| | 40 | -74.2 dBm / 38.16 MHz | +| | 100 | -70.1 dBm / 98.28 MHz | + +NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [17]. The specific test parameters are configured as below: + +**Table 8.3.4.4.2-2: Test parameters** + +| Parameter | Test 1 | Test 2 | +|--------------------------------------|----------------------------------------------|--------| +| Modulation order | QPSK | | +| First PRB prior to frequency hopping | 0 | | +| Intra-slot frequency hopping | enabled | | +| First PRB after frequency hopping | The largest PRB index - (Number of PRBs - 1) | | +| Group and sequence hopping | neither | | +| Hopping ID | 0 | | +| Number of PRBs | 1 | 3 | +| Number of symbols | 14 | 4 | +| The number of UCI information bits | 16 | 16 | +| First symbol | 0 | 0 | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjust the equipment so that the SNR specified in table 8.3.4.5-1 or table 8.3.4.5-2 is achieved at the BS input during the UCI transmissions. +- 6) The signal generator sends a test pattern with the pattern outlined in figure 8.3.4.4.2-1. The following statistics are kept: the number of incorrectly decoded UCI. + +![Figure 8.3.4.4.2-1: Test signal pattern for PUCCH format 3 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'UCI', arranged horizontally. To the right of the third box is an ellipsis (three dots), indicating a repeating pattern.](9832c14a1af451896d75b69abc97654f_img.jpg) + +Figure 8.3.4.4.2-1: Test signal pattern for PUCCH format 3 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'UCI', arranged horizontally. To the right of the third box is an ellipsis (three dots), indicating a repeating pattern. + +**Figure 8.3.4.4.2-1: Test signal pattern for PUCCH format 3 demodulation tests** + +### 8.3.4.5 Test requirement + +The fraction of incorrectly decoded UCI is shall be less than 1% for the SNR listed in table 8.3.4.5-1 and table 8.3.4.5-2. + +**Table 8.3.4.5-1: Required SNR for PUCCH format 3 with 15 kHz SCS** + +| Test Number | Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | | | +|-------------|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------|--------|--------| +| | | | | | | 5 MHz | 10 MHz | 20 MHz | +| 1 | 1 | 2 | Normal | TDLC300-100 Low | No additional DM-RS | 0.8 | 1.7 | 0.9 | +| | | | | | Additional DM-RS | 0.5 | 1.1 | 0.5 | +| | | 4 | Normal | TDLC300-100 Low | No additional DM-RS | -3.2 | -2.7 | -3.2 | +| | | | | | Additional DM-RS | -3.7 | -3.4 | -3.4 | +| | | 8 | Normal | TDLC300-100 Low | No additional DM-RS | -6.4 | -6.1 | -6.3 | +| | | | | | Additional DM-RS | -7.1 | -6.9 | -7.1 | +| 2 | 1 | 2 | Normal | TDLC300-100 Low | No additional DM-RS | 2.0 | 2.8 | 2.6 | +| | | 4 | Normal | TDLC300-100 Low | No additional DM-RS | -2.5 | -1.9 | -1.9 | +| | | 8 | Normal | TDLC300-100 Low | No additional DM-RS | -5.9 | -5.4 | -5.6 | + +**Table 8.3.4.5-2: Required SNR for PUCCH format 3 with 30 kHz SCS** + +| Test Number | Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | | | | +|-------------|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------|--------|--------|---------| +| | | | | | | 10 MHz | 20 MHz | 40 MHz | 100 MHz | +| 1 | 1 | 2 | Normal | TDLC300-100 Low | No additional DM-RS | 1.5 | 1.2 | 1.2 | 1.5 | +| | | | | | Additional DM-RS | 1.1 | 0.9 | 0.6 | 0.7 | +| | | 4 | Normal | TDLC300-100 Low | No additional DM-RS | -2.5 | -2.8 | -2.6 | -2.9 | +| | | | | | Additional DM-RS | -3.1 | -3.5 | -3.4 | -3.6 | +| | | 8 | Normal | TDLC300-100 Low | No additional DM-RS | -6.0 | -6.1 | -6.2 | -6.2 | +| | | | | | Additional DM-RS | -6.9 | -7.0 | -7.0 | -7.1 | +| 2 | 1 | 2 | Normal | TDLC300-100 Low | No additional DM-RS | 2.4 | 2.6 | 2.6 | 2.1 | +| | | 4 | Normal | TDLC300-100 Low | No additional DM-RS | -2.3 | -2.4 | -1.8 | -2.4 | +| | | 8 | Normal | TDLC300-100 Low | No additional DM-RS | -5.8 | -5.4 | -5.8 | -5.6 | + +## 8.3.5 Performance requirements for PUCCH format 4 + +### 8.3.5.1 Definition and applicability + +The performance is measured by the required SNR at UCI block error probability not exceeding 1%. + +The UCI block error probability is defined as the conditional probability of incorrectly decoding the UCI information when the UCI information is sent. The UCI information does not contain CSI part 2. + +The transient period as specified in TS 38.101-1 [21] clause 6.3.3.1 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the CC center, i.e. intra-slot frequency hopping is enabled. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2.2. + +### 8.3.5.2 Minimum requirement + +The minimum requirement is in TS 38.104 [2] clause 8.3.6. + +### 8.3.5.3 Test purpose + +The test shall verify the receiver's ability to detect UCI under multipath fading propagation conditions for a given SNR. + +### 8.3.5.4 Method of test + +#### 8.3.5.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1 + +#### 8.3.5.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *BS type 1-H* respectively. +- 2) Adjust the AWGN generator, according to the subcarrier spacing and channel bandwidth defined in table 8.3.5.4.2-1. + +**Table 8.3.5.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 | 5 | -83.5 dBm / 4.5 MHz | +| | 10 | -80.3 dBm / 9.36 MHz | +| | 20 | -77.2 dBm / 19.08 MHz | +| 30 | 10 | -80.6 dBm / 8.64 MHz | +| | 20 | -77.4 dBm / 18.36 MHz | +| | 40 | -74.2 dBm / 38.16 MHz | +| | 100 | -70.1 dBm / 98.28 MHz | + +NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [17]. The test parameters are configured as below: + +**Table 8.3.5.4.2-2: Test parameters** + +| Parameter | Values | +|--------------------------------------|----------------------------------------------| +| Modulation order | QPSK | +| First PRB prior to frequency hopping | 0 | +| Number of PRBs | 1 | +| Intra-slot frequency hopping | enabled | +| First PRB after frequency hopping | The largest PRB index - (Number of PRBs - 1) | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Number of symbols | 14 | +| The number of UCI information bits | 22 | +| First symbol | 0 | +| Length of the orthogonal cover code | n2 | +| Index of the orthogonal cover code | n0 | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjust the equipment so that the SNR specified in table 8.3.5.5-1 or table 8.3.5.5-2 is achieved at the BS input during the UCI transmissions. +- 6) The signal generator sends a test pattern with the pattern outlined in figure 8.3.5.4.2-1. The following statistics are kept: the number of incorrectly decoded UCI. + +![Figure 8.3.5.4.2-1: Test signal pattern for PUCCH format 4 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'UCI', arranged horizontally. To the right of the third box are three dots, indicating a sequence of similar boxes.](34f6baf47c53b490142dbe71f900f406_img.jpg) + +Figure 8.3.5.4.2-1: Test signal pattern for PUCCH format 4 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'UCI', arranged horizontally. To the right of the third box are three dots, indicating a sequence of similar boxes. + +**Figure 8.3.5.4.2-1: Test signal pattern for PUCCH format 4 demodulation tests** + +### 8.3.5.5 Test requirement + +The fraction of incorrectly decoded UCI is shall be less than 1% for the SNR listed in table 8.3.5.5-1 and table 8.3.5.5-2. + +**Table 8.3.5.5-1: Required SNR for PUCCH format 4 with 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | | | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------|--------|--------| +| | | | | | 5 MHz | 10 MHz | 20 MHz | +| 1 | 2 | Normal | TDLC300-100 Low | No additional DM-RS | 2.4 | 3.2 | 2.8 | +| | | | | Additional DM-RS | 2.2 | 3.0 | 2.4 | +| | 4 | Normal | TDLC300-100 Low | No additional DM-RS | -1.7 | -1.3 | -1.6 | +| | | | | Additional DM-RS | -2.3 | -2.0 | -2.1 | +| | 8 | Normal | TDLC300-100 Low | No additional DM-RS | -5.3 | -5.1 | -5.2 | +| | | | | Additional DM-RS | -6.0 | -5.8 | -5.7 | + +**Table 8.3.5.5-2: Required SNR for PUCCH format 4 with 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | | | | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------|--------|--------|---------| +| | | | | | 10 MHz | 20 MHz | 40 MHz | 100 MHz | +| 1 | 2 | Normal | TDLC300-100 Low | No additional DM-RS | 3.7 | 3.4 | 3.7 | 3.4 | +| | | | | Additional DM-RS | 3.4 | 2.9 | 3.7 | 2.8 | +| | 4 | Normal | TDLC300-100 Low | No additional DM-RS | -1.1 | -1.3 | -1.1 | -1.5 | +| | | | | Additional DM-RS | -1.4 | -1.9 | -1.9 | -1.8 | +| | 8 | Normal | TDLC300-100 Low | No additional DM-RS | -5.0 | -4.9 | -4.9 | -4.9 | +| | | | | Additional DM-RS | -5.6 | -5.5 | -5.8 | -5.6 | + +## 8.3.6 Performance requirements for multi-slot PUCCH + +### 8.3.6.1 Performance requirements for multi-slot PUCCH format 1 + +#### 8.3.6.1.1 NACK to ACK detection + +##### 8.3.6.1.1.1 Definition and applicability + +The performance requirement of multi-slot PUCCH format 1 for NACK to ACK detection is determined by the two parameters: probability of false detection of the ACK and the NACK to ACK detection probability. The performance is measured by the required SNR at probability of the NACK to ACK detection equal to 0.1 % or less. The probability of false detection of the ACK shall be 1 % or less. + +The probability of false detection of the ACK is defined as a conditional probability of erroneous detection of the ACK at particular bit position when input is only noise. Each false bit detection is counted as one error. + +The NACK to ACK detection probability is the probability of detecting an ACK bit when an NACK bit was sent on particular bit position. Each NACK bit erroneously detected as ACK bit is counted as one error. Erroneously detected NACK bits in the definition do not contain the NACK bits which are mapped from DTX, i.e. NACK bits received when DTX is sent should not be considered. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2.2. + +##### 8.3.6.1.1.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2] clause 8.3.3. + +##### 8.3.6.1.1.3 Test purpose + +The test shall verify the receiver's ability not to falsely detect NACK bits as ACK bits under multipath fading propagation conditions for a given SNR. + +##### 8.3.6.1.1.4 Method of test + +###### 8.3.6.1.1.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested: for single carrier: M; see clause 4.9.1. + +## 8.3.6.1.1.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type I-C* and *BS type I-H* respectively. +- 2) Adjust the AWGN generator, according to the combinations of SCS and channel bandwidth defined in Table 8.3.6.1.1.4.2-1. + +**Table 8.3.6.1.1.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 | 5 | -83.5 dBm / 4.5 MHz | +| | 10 | -80.3 dBm / 9.36 MHz | +| | 20 | -77.2 dBm / 19.08 MHz | +| 30 | 10 | -80.6 dBm / 8.64 MHz | +| | 20 | -77.4 dBm / 18.36 MHz | +| | 40 | -74.2 dBm / 38.16 MHz | +| | 100 | -70.1 dBm / 98.28 MHz | + +NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [17], and the specific test parameters are configured as below: + +**Table 8.3.6.1.1.4.2-2: Test parameters for multi-slot PUCCH format 1** + +| Parameter | Test | +|---------------------------------------------------------|----------------------------------------| +| Number of information bits | 2 | +| Number of PRBs | 1 | +| Number of symbols | 14 | +| First PRB prior to frequency hopping | 0 | +| Intra-slot frequency hopping | disabled | +| Inter-slot frequency hopping | enabled | +| First PRB after frequency hopping | The largest PRB index - (nrofPRBs - 1) | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Initial cyclic shift | 0 | +| First symbol | 0 | +| Index of orthogonal cover code ( timeDomainOCC ) | 0 | +| Number of slots for PUCCH repetition | 2 | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjusting the equipment so that the SNR specified in table 8.3.6.1.1.5-1 is achieved at the BS input during the transmissions. + +- 6) The signal generator sends random codeword from applicable codebook, in regular time periods. The following statistics are kept: the number of ACK bits detected in the idle periods and the number of NACK bits detected as ACK. + +#### 8.3.6.1.1.5 Test Requirement + +The fraction of falsely detected ACK bits shall be less than 1 % and the fraction of NACK bits falsely detected as ACK shall be less than 0.1 % for the SNR listed in table 8.3.6.1.1.5-1. + +**Table 8.3.6.1.1.5-1: Minimum requirements for multi-slot PUCCH format 1 with 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Channel bandwidth / SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | 40 MHz | +| 1 | 2 | Normal | TDLC-300-100 Low | -5.7 | + +#### 8.3.6.1.2 ACK missed detection + +##### 8.3.6.1.2.1 Definition and applicability + +The performance requirement of PUCCH format 1 for ACK missed detection is determined by the two parameters: probability of false detection of the ACK and the probability of detection of ACK. The performance is measured by the required SNR at probability of detection equal to 0.99. The probability of false detection of the ACK shall be 0.01 or less. + +The probability of false detection of the ACK is defined as a conditional probability of erroneous detection of the ACK when input is only noise. + +The probability of detection of ACK is defined as conditional probability of detection of the ACK when the signal is present. + +##### 8.3.6.1.2.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2] clause 8.3.3. + +##### 8.3.6.1.2.3 Test purpose + +The test shall verify the receiver's ability to detect ACK bits under multipath fading propagation conditions for a given SNR. + +##### 8.3.6.1.2.4 Method of test + +###### 8.3.6.1.2.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested: for single carrier: M; see clause 4.9.1. + +###### 8.3.6.1.2.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *BS type 1-H* respectively. + +- 2) Adjust the AWGN generator, according to the combinations of SCS and channel bandwidth defined in table 8.3.6.1.2.4.2-1. + +**Table 8.3.6.1.2.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 | 5 | -83.5 dBm / 4.5 MHz | +| | 10 | -80.3 dBm / 9.36 MHz | +| | 20 | -77.2 dBm / 19.08 MHz | +| 30 | 10 | -80.6 dBm / 8.64 MHz | +| | 20 | -77.4 dBm / 18.36 MHz | +| | 40 | -74.2 dBm / 38.16 MHz | +| | 100 | -70.1 dBm / 98.28 MHz | + +NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [17], and the specific test parameters are configured as below: + +**Table 8.3.6.1.2.4.2-2: Test parameters for multi-slot PUCCH format 1** + +| Parameter | Test | +|---------------------------------------------------------|-------------------------------------------| +| Number of information bits | 2 | +| Number of PRBs | 1 | +| Number of symbols | 14 | +| First PRB prior to frequency hopping | 0 | +| Intra-slot frequency hopping | disabled | +| Inter-slot frequency hopping | enabled | +| First PRB after frequency hopping | The largest PRB index -
(nrofPRBs - 1) | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Initial cyclic shift | 0 | +| First symbol | 0 | +| Index of orthogonal cover code ( timeDomainOCC ) | 0 | +| Number of slots for PUCCH repetition | 2 | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjusting the equipment so that the SNR specified in table 8.3 is achieved at the BS input during the transmissions. +- 6) The signal generator sends random codewords from applicable codebook, in regular time periods. The following statistics are kept: the number of ACK bits falsely detected in the idle periods and the number of missed ACK bits. Each falsely detected ACK bit in the idle periods is accounted as one error for the statistics of false ACK detection, and each missed ACK bit is accounted as one error for the statistics of missed ACK detection. + +Note that the procedure described in this clause for ACK missed detection has the same condition as that described in clause 8.3.6.1.1.4.2 for NACK to ACK detection. Both statistics are measured in the same testing. + +#### 8.3.6.1.2.5 Test Requirement + +The fraction of falsely detected ACK bits shall be less than 1 % and the fraction of correctly detected ACK bits shall be larger than 99 % for the SNR listed in table 8.3.6.1.2.5-1. + +**Table 8.3.6.1.2.5-1: Minimum requirements for multi-slot PUCCH format 1 with 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Channel bandwidth / SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | 40 MHz | +| 1 | 2 | Normal | TDLC-300-100 Low | -7.0 | + +### 8.3.7 Performance requirements for interlaced PUCCH format 0 + +#### 8.3.7.1 Definition and applicability + +The performance requirement of single user interlaced PUCCH format 0 for ACK missed detection is determined by the two parameters: probability of false detection of the ACK and the probability of detection of ACK. The performance is measured by the required SNR at probability of detection equal to 0.99. The probability of false detection of the ACK shall be 0.01 or less. + +The probability of false detection of the ACK is defined as a conditional probability of erroneous detection of the ACK when input is only noise. + +The probability of detection of ACK is defined as conditional probability of detection of the ACK when the signal is present. + +The ACK missed detection requirement only applies to the PUCCH format 0 with 1 UCI bits. The UCI information only constrains ACK information + +The 1bit UCI information is further defined with bitmap as [1]. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2.6. + +#### 8.3.7.2 Minimum Requirement + +The minimum requirements are in TS 38.104 [2] clause 8.3.8. + +#### 8.3.7.3 Test purpose + +The test shall verify the receiver's ability to detect ACK under multipath fading propagation conditions for a given SNR. + +#### 8.3.7.4 Method of test + +##### 8.3.7.4.1 Initial conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested: single carrier M; see clause 4.9.1. + +### 8.3.7.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *type 1-H* respectively. +- 2) Adjust the AWGN generator, according to the channel bandwidth and sub-carrier spacing defined in table 8.3.7.4.2-1. + +**Table 8.3.7.4.2-1: AWGN power level at the BS input** + +| Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------------------|-------------------------|-----------------------| +| 15 | 20 | -77.2 dBm / 19.08 MHz | +| 30 | 20 | -77.4 dBm / 18.36 MHz | + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [17] and the specific test parameters are configured as mentioned in table 8.3.7.4.2-2: + +**Table 8.3.7.4.2-2: Test Parameters** + +| Parameter | Test | +|--------------------------------------------------------------------------------------------------------------------|--------------------| +| Number of UCI information bits | 1 | +| Number of symbols | 1 | +| Intra-slot frequency hopping | N/A | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Initial cyclic shift | 0 | +| First symbol | 13 | +| Number of interlaces | 1 | +| Interlace index | 0 Note1 | +| NOTE 1: RBs 0, 10, 20, ..., 100 are allocated for 15kHz SCS and RBs 0, 5, 10, ..., 50 are allocated for 30kHz SCS. | | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex B. +- 5) Adjust the equipment so that the SNR specified in table 8.3.7.5-1 or table 8.3.7.5-2 is achieved at the BS input during the ACK transmissions. +- 6) The signal generator sends a test pattern with the pattern outlined in figure 8.3.7.4.2-1. The following statistics are kept: the number of ACKs detected in the idle periods and the number of missed ACKs. + +![Figure 8.3.7.4.2-1: Test signal pattern for single user interlaced PUCCH format 0 demodulation tests. The diagram shows a sequence of three rectangular boxes, each containing the text 'ACK', followed by three dots (ellipsis) indicating a repeating pattern.](0e83feb3f1198525296af300ae5e2604_img.jpg) + +Figure 8.3.7.4.2-1: Test signal pattern for single user interlaced PUCCH format 0 demodulation tests. The diagram shows a sequence of three rectangular boxes, each containing the text 'ACK', followed by three dots (ellipsis) indicating a repeating pattern. + +**Figure 8.3.7.4.2-1: Test signal pattern for single user interlaced PUCCH format 0 demodulation tests** + +### 8.3.7.5 Test Requirement + +The fraction of falsely detected ACKs shall be less than 1% and the fraction of correctly detected ACKs shall be larger than 99% for the SNR listed in table 8.3.7.5-1. + +**Table 8.3.7.5-1: Test requirements for interlaced PUCCH format 0 with 15 kHz SCS, 20MHz channel bandwidth** + +| Number of Tx antennas | Number of RX antennas | Propagation conditions and correlation matrix (Annex G) | Number of OFDM symbols | SNR (dB) | +|-----------------------|-----------------------|---------------------------------------------------------|------------------------|----------| +| 1 | 2 | TDLA30-10 Low | 1 | -2.2 | + +**Table 8.3.7.5-2: Test requirements for interlaced PUCCH format 0 with 30 kHz SCS, 20MHz channel bandwidth** + +| Number of Tx antennas | Number of RX antennas | Propagation conditions and correlation matrix (Annex G) | Number of OFDM symbols | SNR (dB) | +|-----------------------|-----------------------|---------------------------------------------------------|------------------------|----------| +| 1 | 2 | TDLA30-10 Low | 1 | -1.4 | + +## 8.3.8 Performance requirements for interlaced PUCCH format 1 + +### 8.3.8.1 NACK to ACK detection + +#### 8.3.8.1.1 Definition and applicability + +The performance requirement of interlaced PUCCH format 1 for NACK to ACK detection is determined by the two parameters: probability of false detection of the ACK and the NACK to ACK detection probability. The performance is measured by the required SNR at probability of the NACK to ACK detection equal to 0.1% or less. The probability of false detection of the ACK shall be 0.01 or less. + +The probability of false detection of the ACK is defined as a conditional probability of erroneous detection of the ACK at particular bit position when input is only noise. Each false bit detection is counted as one error. + +The NACK to ACK detection probability is the probability of detecting an ACK bit when a NACK bit was sent on particular bit position. Each NACK bit erroneously detected as ACK bit is counted as one error. Erroneously detected NACK bits in the definition do not contain the NACK bits which are mapped from DTX, i.e. NACK bits received when DTX is sent should not be considered. + +The NACK to ACK detection requirement only applies to the PUCCH format 1 with 2 UCI bits. The UCI information only contains ACK/NACK information + +The 2bits UCI information is further defined with bitmap as [0 1]. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2.6. + +#### 8.3.8.1.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2] clause 8.3.9. + +#### 8.3.8.1.3 Test purpose + +The test shall verify the receiver's ability not to falsely detect NACK bits as ACK bits under multipath fading propagation conditions for a given SNR. + +#### 8.3.8.1.4 Method of test + +##### 8.3.8.1.4.1 Initial Conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested: for single carrier: M; see clause 4.9.1. + +##### 8.3.8.1.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type I-C* and *type I-H* respectively. +- 2) Adjust the AWGN generator, according to the combinations of SCS and channel bandwidth defined in table 8.3.8.1.4.2-1. + +**Table 8.3.8.1.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 | 20 | -77.2 dBm / 19.08 MHz | +| 30 | 20 | -77.4 dBm / 18.36 MHz | + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [17], and the specific test parameters are configured as below: + +**Table 8.3.8.1.4.2-2: Test parameters** + +| Parameter | Test | +|-----------------------------------------------------------------------------------------------------------------------|--------------------| +| Number of information bits | 2 | +| Number of symbols | 14 | +| Intra-slot frequency hopping | N/A | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Initial cyclic shift | 0 | +| First symbol | 0 | +| Index of orthogonal cover code
( timeDomainOCC ) | 0 | +| Number of interlace | 1 | +| Interlace index | 0 Note1 | +| NOTE 1: RBs 0, 10, 20, ..., 100 are allocated for 15kHz SCS and
RBs 0, 5, 10, ..., 50 are allocated for 30kHz SCS. | | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjusting the equipment so that the SNR specified in table 8.3.8.1.5-1 and table 8.3.8.1.5-2 is achieved at the BS input during the transmissions. +- 6) The signal generator sends random codeword from applicable codebook, in regular time periods. The following statistics are kept: the number of ACK bits detected in the idle periods and the number of NACK bits detected as ACK. + +### 8.3.8.1.5 Test Requirement + +The fraction of falsely detected ACK bits shall be less than 1% and the fraction of NACK bits falsely detected as ACK shall be less than 0.1% for the SNR listed in tables 8.3.8.1.5-1. + +**Table 8.3.8.1.5-1: Required SNR for interlaced PUCCH format 1 with 15 kHz SCS, 20MHz channel bandwidth** + +| Number of Tx antennas | Number of RX antennas | Cyclic-Prefix | Propagation conditions and correlation matrix (Annex G) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | -13.2 | + +**Table 8.3.8.1.5-2: Required SNR for interlaced PUCCH format 1 with 30 kHz SCS, 20MHz channel bandwidth** + +| Number of Tx antennas | Number of RX antennas | Cyclic-Prefix | Propagation conditions and correlation matrix (Annex G) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | -12.7 | + +### 8.3.8.2 ACK missed detection + +#### 8.3.8.2.1 Definition and applicability + +The performance requirement of interlaced PUCCH format 1 for ACK missed detection is determined by the two parameters: probability of false detection of the ACK and the probability of detection of ACK. The performance is measured by the required SNR at probability of detection equal to 0.99. The probability of false detection of the ACK shall be 0.01 or less. + +The probability of false detection of the ACK is defined as a conditional probability of erroneous detection of the ACK when input is only noise. + +The probability of detection of ACK is defined as conditional probability of detection of the ACK when the signal is present. + +The ACK missed detection requirement only applies to the PUCCH format 1 with 2 UCI bits. The UCI information only contains ACK/NACK information. + +The 2bits UCI information is further defined with bitmap as [0 1]. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2.6. + +#### 8.3.8.2.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2] clause 8.3.9. + +#### 8.3.8.2.3 Test purpose + +The test shall verify the receiver's ability to detect ACK bits under multipath fading propagation conditions for a given SNR. + +#### 8.3.8.2.4 Method of test + +##### 8.3.8.2.4.1 Initial Conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested: for single carrier (SC): M; see clause 4.9.1. + +##### 8.3.8.2.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *type 1-H* respectively. +- 2) Adjust the AWGN generator, according to the combinations of SCS and channel bandwidth defined in table 8.3.8.2.4.2-1. + +**Table 8.3.8.2.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 | 20 | -77.2 dBm / 19.08 MHz | +| 30 | 20 | -77.4 dBm / 18.36 MHz | + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [17], and the specific test parameters are configured as below: + +**Table 8.3.8.2.4.2-2: Test parameters** + +| Parameter | Test | +|-----------------------------------------------------------------------------------------------------------------------|--------------------| +| Number of information bits | 2 | +| Number of symbols | 14 | +| Intra-slot frequency hopping | N/A | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Initial cyclic shift | 0 | +| First symbol | 0 | +| Index of orthogonal cover code
( timeDomainOCC ) | 0 | +| Number of interlace | 1 | +| Interlace index | 0 Note1 | +| NOTE 1: RBs 0, 10, 20, ..., 100 are allocated for 15kHz SCS and
RBs 0, 5, 10, ..., 50 are allocated for 30kHz SCS. | | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjusting the equipment so that the SNR specified in table 8.3.8.2.5-1 and table 8.3.8.2.5-2 is achieved at the BS input during the transmissions. +- 6) The signal generator sends random codewords from applicable codebook, in regular time periods. The following statistics are kept: the number of ACK bits falsely detected in the idle periods and the number of missed ACK bits. Each falsely detected ACK bit in the idle periods is accounted as one error for the statistics of false ACK detection, and each missed ACK bit is accounted as one error for the statistics of missed ACK detection. + +Note that the procedure described in this clause for ACK missed detection has the same condition as that described in clause 8.3.8.1.4.2 for NACK to ACK detection. Both statistics are measured in the same testing. + +#### 8.3.8.2.5 Test Requirement + +The fraction of falsely detected ACK bits shall be less than 1% and the fraction of correctly detected ACK bits shall be larger than 99% for the SNR listed in tables 8.3.8.2.5-1. + +**Table 8.3.8.2.5-1 Required SNR for interlaced PUCCH format 1 with 15 kHz SCS, 20MHz channel bandwidth** + +| Number of Tx antennas | Number of RX antennas | Cyclic-Prefix | Propagation conditions and correlation matrix (Annex G) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | -13.8 | + +**Table 8.3.8.2.5-2 Required SNR for interlaced PUCCH format 1 with 30 kHz SCS, 20MHz channel bandwidth** + +| Number of Tx antennas | Number of RX antennas | Cyclic-Prefix | Propagation conditions and correlation matrix (Annex G) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 2 | Normal | TDLA30-10 Low | -13.5 | + +### 8.3.9 Performance requirements for interlaced PUCCH format 2 + +#### 8.3.9.1 Definition and applicability + +The performance is measured by the required SNR at UCI block error probability not exceeding 1%. + +The UCI block error probability (BLER) is defined as the probability of incorrectly decoding the UCI information when the UCI information is sent. The UCI information does not contain CSI part 2. + +The UCI block error probability performance requirement only applies to the PUCCH format 2 with 22 UCI bits. + +The 22bits UCI information case is assumed random information bit selection. + +Which specific test(s) are applicable to BS is based on the test applicability rules defines in clause 8.1.2.6. + +#### 8.3.9.2 Minimum requirement + +The minimum requirement is in TS 38.104 [2] clause 8.3.10. + +#### 8.3.9.3 Test purpose + +The test shall verify the receiver's ability to detect UCI under multipath fading propagation conditions for a given SNR. + +#### 8.3.9.4 Method of test + +##### 8.3.9.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1 + +### 8.3.9.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *BS type 1-H* respectively. +- 2) Adjust the AWGN generator, according to the subcarrier spacing and channel bandwidth defined in table 8.3.9.4.2-1. + +**Table 8.3.9.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 | 20 | -77.2 dBm / 19.08 MHz | +| 30 | 20 | -77.4 dBm / 18.36 MHz | + +NOTE 1: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [17]. The specific test parameters are configured as below: + +**Table 8.3.9.4.2-2: Test parameters** + +| Parameter | Value | +|------------------------------------|----------------| +| Modulation order | QSPK | +| Intra-slot frequency hopping | N/A | +| Number of symbols | 1 | +| The number of UCI information bits | 22 | +| First symbol | 13 | +| DM-RS sequence generation | $N_{ID}^0=0$ | +| Number of interlaces | 1 | +| Interlace index | 0(note 1) | +| OCC-length-r16 | Not configured | + +NOTE 1: RBs 0,10,20,...,100 are allocated for 15kHz SCS and RBs 0, 5, 10,...,50 are allocated for 30kHz SCS + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjust the equipment so that the SNR specified in table 8.3.9.5-1 or table 8.3.9.5-2 is achieved at the BS input during the UCI transmissions. +- 6) The signal generator sends a test pattern with the pattern outlined in figure 8.3.9.4.2-1. The following statistics are kept: the number of incorrectly decoded UCI. + +![Figure 8.3.9.4.2-1: Test signal pattern for interlaced PUCCH format 2 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'UCI', arranged horizontally. To the right of the third box are three dots, indicating a repeating pattern.](9cf46aa4fa95213299ac07f37ed34ce9_img.jpg) + +Figure 8.3.9.4.2-1: Test signal pattern for interlaced PUCCH format 2 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'UCI', arranged horizontally. To the right of the third box are three dots, indicating a repeating pattern. + +**Figure 8.3.9.4.2-1: Test signal pattern for interlaced PUCCH format 2 demodulation tests** + +### 8.3.9.5 Test requirement + +The fraction of incorrectly decoded UCI is shall be less than 1% for the SNR listed in table 8.3.9.5-1 and table 8.3.9.5-2. + +**Table 8.3.9.5-1: Required SNR for interlaced PUCCH format 2 with 15 kHz SCS, 20 MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | SNR(dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|---------| +| 1 | 2 | Normal | TDLA30-10 Low | 4.1 | + +**Table 8.3.9.5-2: Required SNR for interlaced PUCCH format 2 with 30 kHz SCS, 20 MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | SNR(dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|---------| +| 1 | 2 | Normal | TDLA30-10 Low | 4.5 | + +## 8.3.10 Performance requirements for interlaced PUCCH format 3 + +### 8.3.10.1 Definition and applicability + +The performance requirement of interlaced PUCCH format 3 for ACK missed detection is determined by the two parameters: probability of false detection of the ACK and the probability of detection of ACK. The performance is measured by the required SNR at probability of detection equal to 0.99. The probability of false detection of the ACK shall be 0.01 or less. + +The probability of false detection of the ACK is defined as a probability of erroneous detection of the ACK when input is only noise. + +The probability of detection of ACK is defined as probability of detection of the ACK when the signal is present. + +The ACK missed detection requirement only applies to the PUCCH format 3 with 4 UCI bits. The UCI information only contains ACK information. + +The 4bits UCI information case is further defined with the bitmap as [1 1 1 1]. + +Which specific test(s) are applicable to BS is based on the test applicability rules defines in clause 8.1.2.6. + +### 8.3.10.2 Minimum requirement + +The minimum requirement is in TS 38.104 [2] clause 8.3.11. + +### 8.3.10.3 Test purpose + +The test shall verify the receiver's ability to detect ACK bits under multipath fading propagation conditions for a given SNR. + +### 8.3.10.4 Method of test + +#### 8.3.10.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1 + +#### 8.3.10.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type I-C* and *BS type I-H* respectively. +- 2) Adjust the AWGN generator, according to the subcarrier spacing and channel bandwidth defined in table 8.3.10.4.2-1. + +**Table 8.3.10.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|-----------------------| +| 15 | 20 | -77.2 dBm / 19.08 MHz | +| 30 | 20 | -77.4 dBm / 18.36 MHz | + +NOTE 1: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [17]. The specific test parameters are configured as below: + +**Table 8.3.10.4.2-2: Test parameters** + +| Parameter | Value | +|----------------------------------------------------------------------------------------------------------|----------------| +| Modulation order | QPSK | +| Intra-slot frequency hopping | N/A | +| Group and sequence hopping | Neither | +| Hopping ID | 0 | +| Number of symbols | 4 | +| The number of UCI information bits | 4 | +| Index of OCC | Not configured | +| Length of OCC | Not configured | +| Cyclic shift index for DMRS | 0 | +| Number of Interlace | 1 | +| Interlace index | 0(note 1) | +| NOTE 1: RBs 0,10,20,...,90 are allocated for 15kHz SCS and RBs 0,5,10,...,45 are allocated for 30kHz SCS | | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjust the equipment so that the SNR specified in table 8.3.10.5-1 or table 8.3.10.5-2 is achieved at the BS input during the UCI transmissions. + +- 6) The signal generator sends a test pattern with the pattern outlined in figure 8.3.10.4.2-1. The following statistics are kept: the number of ACKs detected in the idle periods and the number of missed ACKs. + +![Figure 8.3.10.4.2-1: Test signal pattern for interlaced PUCCH format 3 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'ACK', representing detected acknowledgments. To the right of the third box are three dots, indicating a sequence of such detections over time.](6f27cea0d83b6f1bc74e4f4fee27f4a4_img.jpg) + +Figure 8.3.10.4.2-1: Test signal pattern for interlaced PUCCH format 3 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'ACK', representing detected acknowledgments. To the right of the third box are three dots, indicating a sequence of such detections over time. + +**Figure 8.3.10.4.2-1: Test signal pattern for interlaced PUCCH format 3 demodulation tests** + +### 8.3.10.5 Test requirement + +The fraction of falsely detected ACKs shall be less than 1% and the fraction of correctly detected ACKs shall be larger than 99% for the SNR listed in table 8.3.10.5-1 and table 8.3.10.5-2. + +**Table 8.3.10.5-1: Required SNR for interlaced PUCCH format 3 with 15 kHz SCS, 20 MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Additional DM-RS configuration | SNR(dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------| +| 1 | 2 | Normal | TDLA30-10 Low | No additional DM-RS | -5.4 | + +**Table 8.3.10.5-2: Required SNR for interlaced PUCCH format 3 with 30 kHz SCS, 20 MHz channel bandwidth** + +| Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | Additional DM-RS configuration | SNR(dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|---------| +| 1 | 2 | Normal | TDLA30-10 Low | No additional DM-RS | -4.8 | + +## 8.3.11 Performance requirements for PUCCH sub-slot based repetition format 0 + +### 8.3.11.1 Definition and applicability + +The performance requirement of single user PUCCH sub-slot based repetition format 0 for ACK missed detection is determined by the parameters: probability of detection of ACK. The performance is measured by the required SNR at probability of detection equal to 0.99. The probability of false detection of the ACK shall be 0.01 or less. + +The probability of false detection of the ACK is defined as a conditional probability of erroneous detection of the ACK when input is only noise. + +The probability of detection of ACK is defined as conditional probability of detection of the ACK when the signal is present. + +The ACK missed detection requirement only applies to the PUCCH format 0 with 1 UCI bits. The UCI information only constrains ACK information + +The 1bit UCI information is further defined with bitmap as [1]. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2.2.6. + +### 8.3.11.2 Minimum Requirement + +The minimum requirements are in TS 38.104 [2] clause 8.3.14. + +### 8.3.11.3 Test purpose + +The test shall verify the receiver's ability to detect ACK under multipath fading propagation conditions for a given SNR. + +### 8.3.11.4 Method of test + +#### 8.3.11.4.1 Initial conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested: single carrier M; see clause 4.9.1. + +#### 8.3.11.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *type 1-H* respectively. +- 2) Adjust the AWGN generator, according to the channel bandwidth and sub-carrier spacing defined in table 8.3.11.4.2-1. + +**Table 8.3.11.4.2-1: AWGN power level at the BS input** + +| Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------------------|-------------------------|-----------------------| +| 30 | 10 | -80.6 dBm / 18.36 MHz | + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [17] and the specific test parameters are configured as mentioned in table 8.3.11.4.2-2: + +**Table 8.3.11.4.2-2: Test Parameters** + +| Parameter | Test | +|--------------------------------------------------------------------|-------------------------------------------------| +| Number of UCI information bits | 1 | +| Number of PRBs | 1 | +| Number of PUCCH symbols
( nrofSymobls ) | 2 | +| Number of sub-slot PUCCH repetitions
( nrofSlots ) | 2 | +| Number of Sub-slot symbols
( subslotLengthForPUCCH-r16 ) | 7 | +| First symbol of sub-slot
( startingSymbolIndex ) | 5 | +| First PRB prior to frequency hopping | 0 | +| First PRB after frequency hopping | The largest PRB index –
(Number of PRBs – 1) | +| Intra-slot frequency hopping | disabled | +| Inter-slot frequency hopping | enabled | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Initial cyclic shift | 0 | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex B. +- 5) Adjust the equipment so that the SNR specified in table 8.3.11.5-1 is achieved at the BS input during the ACK transmissions. +- 6) The signal generator sends a test pattern with the pattern outlined in figure 8.3.11.4.2-1. The following statistics are kept: the number of ACKs detected in the idle periods and the number of missed ACKs. + +![Figure 8.3.11.4.2-1: Test signal pattern for PUCCH sub-slot based repetition format 0 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'ACK', representing ACK transmissions. To the right of the third box are three dots, indicating a sequence of transmissions.](2ce4c14cc166ab2d1635adf7c1a2dda9_img.jpg) + +Figure 8.3.11.4.2-1: Test signal pattern for PUCCH sub-slot based repetition format 0 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'ACK', representing ACK transmissions. To the right of the third box are three dots, indicating a sequence of transmissions. + +**Figure 8.3.11.4.2-1: Test signal pattern for PUCCH sub-slot based repetition format 0 demodulation tests** + +### 8.3.11.5 Test Requirement + +The ACK missed detection probability shall not exceed 1% at the SNR listed in table 8.3.11.5-1. + +**Table 8.3.11.5-1: Test requirements for sub-slot PUCCH format 0 repetition with 30 kHz SCS, 10MHz channel bandwidth** + +| Number of Tx antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (Annex G) | SNR (dB) | +|-----------------------|-----------------------|---------------|---------------------------------------------------------|----------| +| 1 | 2 | Normal | TDLC300-100 Low | 2.1 | + +## 8.3.12 Performance requirements PUCCH format 1 with DM-RS bundling + +### 8.3.12.1 NACK to ACK detection + +#### 8.3.12.1.1 Definition and applicability + +The performance requirement of PUCCH format 1 with DM-RS bundling for NACK to ACK detection is determined by the two parameters: probability of false detection of the ACK and the NACK to ACK detection probability. The performance is measured by the required SNR at probability of the NACK to ACK detection equal to 0.1 % or less. The probability of false detection of the ACK shall be 1 % or less. + +The probability of false detection of the ACK is defined as a conditional probability of erroneous detection of the ACK at particular bit position when input is only noise. Each false bit detection is counted as one error. + +The NACK to ACK detection probability is the probability of detecting an ACK bit when a NACK bit was sent on particular bit position. Each NACK bit erroneously detected as ACK bit is counted as one error. Erroneously detected NACK bits in the definition do not contain the NACK bits which are mapped from DTX, i.e. NACK bits received when DTX is sent should not be considered. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2.10. + +#### 8.3.12.1.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2] clause 8.3.3. + +#### 8.3.12.1.3 Test purpose + +The test shall verify the receiver's ability not to falsely detect NACK bits as ACK bits under multipath fading propagation conditions for a given SNR. + +#### 8.3.12.1.4 Method of test + +##### 8.3.12.1.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested: for single carrier: M; see clause 4.9.1. + +##### 8.3.12.1.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type I-C* and *BS type I-H* respectively. +- 2) Adjust the AWGN generator, according to the combinations of SCS and channel bandwidth defined in Table 8.3.12.1.4.2-1. + +**Table 8.3.12.1.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------| +| 15 | 5 | -83.5 dBm / 4.5 MHz | +| 30 | 10 | -80.6 dBm / 8.64 MHz | +| NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. | | | + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [17], and the specific test parameters are configured as below: + +**Table 8.3.12.1.4.2-2: Test parameters for PUCCH format 1 with DM-RS bundling** + +| Parameter | Test 1 [TDD] | Test 2 [FDD] | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|--------------| +| Example TDD UL-DL pattern (Note1) | 15 / 30 kHz SCS: 7D1S2U, S=6D:4G:4U | | +| Number of information bits | 2 | 2 | +| Number of PRBs | 1 | 1 | +| Number of symbols | 14 | 14 | +| Intra-slot frequency hopping | disabled | disabled | +| Inter-slot frequency hopping | disabled | disabled | +| Hopping ID | 0 | 0 | +| Initial cyclic shift | 0 | 0 | +| First symbol | 0 | 0 | +| Index of orthogonal cover code
(timeDomainOCC) | 0 | 0 | +| Number of slots for PUCCH repetition | 2 | 8 | +| PUCCH-TimeDomainWindowLength | 2 | 8 | +| Note 1: The same TDD requirements are applicable to different UL-DL patterns with more than one consecutive UL slots when both pucch-TimeDomainWindowLength and PUCCH aggregation factor are configured as 2 slots.
The UL (re)transmission of PUCCH is only scheduled for the actual TDW including 2 consecutive UL slots. | | | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjusting the equipment so that the SNR specified in table 8.3.12.1.5-1 is achieved at the BS input during the transmissions. +- 6) The signal generator sends random codeword from applicable codebook, in regular time periods that conform with the required *actual Time Domain Window* (aTDW) needed by the tests (see subclause 8.2.xxx). The following statistics are kept: the number of ACK bits detected in the idle periods and the number of NACK bits detected as ACK. + +### 8.3.12.1.5 Test Requirement + +The fraction of falsely detected ACK bits shall be less than 1 % and the fraction of NACK bits falsely detected as ACK shall be less than 0.1 % for the SNR listed in table 8.3.12.1.5-1. + +**Table 8.3.12.1.5-1: Minimum requirements for PUCCH format 1 with DM-RS bundling with 15 kHz SCS** + +| Test Number | Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|-----------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | | 5 MHz | +| 1 | 1 | 2 | Normal | TDLA30-10 Low | -2.4 | +| 2 | 1 | 2 | Normal | TDLA30-10 Low | -8.5 | + +**Table 8.3.12.1.5-1: Minimum requirements for PUCCH format 1 with DM-RS bundling with 30 kHz SCS** + +| Test Number | Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|-----------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | | 10 MHz | +| 1 | 1 | 2 | Normal | TDLA30-10 Low | -2.4 | +| 2 | 1 | 2 | Normal | TDLA30-10 Low | -8.1 | + +## 8.3.12.2 ACK missed detection + +### 8.3.12.2.1 Definition and applicability + +The performance requirement of PUCCH format 1 for ACK missed detection is determined by the two parameters: probability of false detection of the ACK and the probability of detection of ACK. The performance is measured by the required SNR at probability of detection equal to 0.99. The probability of false detection of the ACK shall be 0.01 or less. + +The probability of false detection of the ACK is defined as a conditional probability of erroneous detection of the ACK when input is only noise. + +The probability of detection of ACK is defined as conditional probability of detection of the ACK when the signal is present. + +### 8.3.12.2.2 Minimum Requirement + +The minimum requirement is in TS 38.104 [2] clause 8.3.3. + +### 8.3.12.2.3 Test purpose + +The test shall verify the receiver's ability to detect ACK bits under multipath fading propagation conditions for a given SNR. + +### 8.3.12.2.4 Method of test + +#### 8.3.12.2.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested: for single carrier: M; see clause 4.9.1. + +## 8.3.12.2.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *BS type 1-H* respectively. +- 2) Adjust the AWGN generator, according to the combinations of SCS and channel bandwidth defined in table 8.3.12.2.4.2-1. + +**Table 8.3.12.2.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------| +| 15 | 5 | -83.5 dBm / 4.5 MHz | +| 30 | 10 | -80.6 dBm / 8.64 MHz | +| NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. | | | + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [17], and the specific test parameters are configured as below: + +**Table 8.3.12.2.4.2-2: Test parameters for PUCCH format 1 with DM-RS bundling** + +| Parameter | Test 1 [TDD] | Test 2 [FDD] | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|--------------| +| Example TDD UL-DL pattern (Note1) | 15 / 30 kHz SCS: 7D1S2U, S=6D:4G:4U | | +| Number of information bits | 2 | 2 | +| Number of PRBs | 1 | 1 | +| Number of symbols | 14 | 14 | +| Intra-slot frequency hopping | disabled | disabled | +| Inter-slot frequency hopping | disabled | disabled | +| Group and sequence hopping | neither | neither | +| Hopping ID | 0 | 0 | +| Initial cyclic shift | 0 | 0 | +| First symbol | 0 | 0 | +| Index of orthogonal cover code ( timeDomainOCC ) | 0 | 0 | +| Number of slots for PUCCH repetition | 2 | 8 | +| PUCCH-TimeDomainWindowLength | 2 | 8 | +| Note 1: The same TDD requirements are applicable to different UL-DL patterns with more than one consecutive UL slots when both pucch-TimeDomainWindowLength and PUCCH aggregation factor are configured as 2 slots.
The UL (re)transmission of PUCCH is only scheduled for the actual TDW including 2 consecutive UL slots. | | | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjusting the equipment so that the SNR specified in table 8.3.12.2.5-1 is achieved at the BS input during the transmissions. +- 6) The signal generator sends random codewords from applicable codebook, in regular time periods. The following statistics are kept: the number of ACK bits falsely detected in the idle periods and the number of missed ACK bits. Each falsely detected ACK bit in the idle periods is accounted as one error for the statistics of false ACK detection, and each missed ACK bit is accounted as one error for the statistics of missed ACK detection. + +Note that the procedure described in this clause for ACK missed detection has the same condition as that described in clause 8.3.12.1.4.2 for NACK to ACK detection. Both statistics are measured in the same testing. + +### 8.3.12.2.5 Test Requirement + +The fraction of falsely detected ACK bits shall be less than 1 % and the fraction of correctly detected ACK bits shall be larger than 99 % for the SNR listed in table 8.3.12.2.5-1 and table 8.3.12.2.5-2. + +**Table 8.3.12.2.5-1: Minimum requirements for PUCCH format 1 with DM-RS bundling with 15 kHz SCS** + +| Test Number | Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|-----------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | | 5 MHz | +| 1 | 1 | 2 | Normal | TDLA30-10 | -3.3 | +| 2 | 1 | 2 | Normal | TDLA30-10 | -8.3 | + +**Table 8.3.12.2.5-2: Minimum requirements for PUCCH format 1 with DM-RS bundling with 30 kHz SCS** + +| Test Number | Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|-----------------------|---------------|---------------------------------------------------------|------------------------------| +| | | | | | 10 MHz | +| 1 | 1 | 2 | Normal | TDLA30-10 | -3.2 | +| 2 | 1 | 2 | Normal | TDLA30-10 | -7.9 | + +## 8.3.13 Performance requirements for PUCCH format 3 with DM-RS bundling + +### 8.3.13.1 Definition and applicability + +The performance is measured by the required SNR at UCI block error probability not exceeding 1%. + +The UCI block error probability is defined as the conditional probability of incorrectly decoding the UCI information when the UCI information is sent. The UCI information does not contain CSI part 2. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2.10. + +### 8.3.13.2 Minimum requirement + +The minimum requirement is in TS 38.104 [2] clause 8.3.5. + +### 8.3.13.3 Test purpose + +The test shall verify the receiver's ability to detect UCI under multipath fading propagation conditions for a given SNR. + +### 8.3.13.4 Method of test + +#### 8.3.13.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1 + +#### 8.3.13.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *BS type 1-H* respectively. +- 2) Adjust the AWGN generator, according to the subcarrier spacing and channel bandwidth defined in table 8.3.13.4.2-1. + +**Table 8.3.13.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| 15 | 5 | -83.5 dBm / 4.5 MHz | +| 30 | 10 | -80.6 dBm / 8.64 MHz | +| NOTE: | The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. | | + +- 3) The characteristics of the wanted signal shall be configured according to TS 38.211 [17]. The specific test parameters are configured as below: + +**Table 8.3.13.4.2-2: Test parameters** + +| Parameter | Test 1 [TDD] | Test 2 [FDD] | +|------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------| +| Example TDD UL-DL pattern (Note1) | 15 / 30 kHz SCS: 7D1S2U, S=6D:4G:4U | | +| Modulation order | QPSK | QPSK | +| Intra-slot frequency hopping | disabled | disabled | +| Number of PRBs | 1 | 1 | +| Number of symbols | 14 | 14 | +| The number of UCI information bits | 16 | 16 | +| First symbol | 0 | 0 | +| Number of slots for PUCCH repetition | 2 | 8 | +| PUCCH-TimeDomainWindowLength | 2 | 8 | +| Note 1: | The same TDD requirements are applicable to different UL-DL patterns with more than one consecutive UL slots when both pucch-TimeDomainWindowLength and PUCCH aggregation factor are configured as 2 slots.
The UL (re)transmission of PUCCH is only scheduled for the actual TDW including 2 consecutive UL slots. | | + +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjust the equipment so that the SNR specified in table 8.3.13.5-1 or table 8.3.13.5-2 is achieved at the BS input during the UCI transmissions. +- 6) The signal generator sends a test pattern with the pattern outlined in figure 8.3.13.4.2-1. The following statistics are kept: the number of incorrectly decoded UCI. + +![Figure 8.3.13.4.2-1: Test signal pattern for PUCCH format 3 demodulation tests. The diagram shows three boxes labeled 'UCI' followed by three dots, representing a sequence of UCI blocks.](d51c36816d3c1c3219454679a83120e1_img.jpg) + +Figure 8.3.13.4.2-1: Test signal pattern for PUCCH format 3 demodulation tests. The diagram shows three boxes labeled 'UCI' followed by three dots, representing a sequence of UCI blocks. + +Figure 8.3.13.4.2-1: Test signal pattern for PUCCH format 3 demodulation tests + +### 8.3.13.5 Test requirement + +The fraction of incorrectly decoded UCI shall be less than 1% for the SNR listed in table 8.3.13.5-1 and table 8.3.13.5-2. + +Table 8.3.13.5-1: Required SNR for PUCCH format 3 with 15 kHz SCS + +| Test Number | Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------| +| | | | | | | 5 MHz | +| 1 | 1 | 2 | Normal | TDLA30-10 Low | No additional DM-RS | -0.9 | +| | | | | | Additional DM-RS | 0.5 | +| 2 | 1 | 2 | Normal | TDLA30-10 Low | No additional DM-RS | -4.7 | +| | | | | | Additional DM-RS | -5.2 | + +Table 8.3.13.5-2: Required SNR for PUCCH format 3 with 30 kHz SCS + +| Test Number | Number of TX antennas | Number of RX antennas | Cyclic Prefix | Propagation conditions and correlation matrix (annex G) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | +|-------------|-----------------------|-----------------------|---------------|---------------------------------------------------------|--------------------------------|------------------------------| +| | | | | | | 10 MHz | +| 1 | 1 | 2 | Normal | TDLA30-10 Low | No additional DM-RS | 0.8 | +| | | | | | Additional DM-RS | 0.6 | +| 2 | 1 | 2 | Normal | TDLA30-10 Low | No additional DM-RS | -4.6 | +| | | | | | Additional DM-RS | -5 | + +## 8.4 Performance requirements for PRACH + +### 8.4.1 PRACH false alarm probability and missed detection + +#### 8.4.1.1 Definition and applicability + +The performance requirement of PRACH for preamble detection is determined by the two parameters: total probability of false detection of the preamble ( $P_{fa}$ ) and the probability of detection of preamble ( $P_d$ ). The performance is measured by the required SNR at probability of detection, $P_d$ of 99%. $P_{fa}$ shall be 0.1% or less. + +$P_{fa}$ is defined as a conditional total probability of erroneous detection of the preamble (i.e. erroneous detection from any detector) when input is only noise. + +$P_d$ is defined as conditional probability of detection of the preamble when the signal is present. The erroneous detection consists of several error cases – detecting only different preamble(s) than the one that was sent, not detecting any preamble at all, or detecting the correct preamble but with the out-of-bounds timing estimation value. + +For AWGN and TDLC300-100, and TDLA30-10, a timing estimation error occurs if the estimation error of the timing of the strongest path is larger than the time error tolerance values given in table 8.4.1.1-1. + +**Table 8.4.1.1-1: Time error tolerance for AWGN and TDLC300-100** + +| PRACH preamble | PRACH SCS (kHz) | Time error tolerance | | | +|------------------------|-----------------|----------------------|-------------|-----------| +| | | AWGN | TDLC300-100 | TDLA30-10 | +| 0 | 1.25 | 1.04 us | 2.55 us | N/A | +| A1, A2, A3, B4, C0, C2 | 15 | 0.52 us | 2.03 us | 0.67 us | +| | 30 | 0.26 us | 1.77 us | 0.41 us | + +The test preambles for normal mode are listed in table A.6-1. The test preambles for high speed train restricted set type A are listed in table A.6-3 and the test preambles for high speed train restricted set type B are listed in table A.6-4. The test preambles for high speed train short formats are listed in table A.6-5. The test preambles for PRACH with $L_{RA}=1151$ and $L_{RA}=571$ are listed in table A.6-6. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.2. The performance requirements for high speed train (table 8.4.1. 6-1 to 8.4.1.6-4) are optional. + +#### 8.4.1.2 Minimum requirement + +The minimum requirement is in TS 38.104 [2] clause 8.4.1.2 and 8.4.2.2, 8.4.2.3, and 8.4.2.4. + +#### 8.4.1.3 Test purpose + +The test shall verify the receiver's ability to detect PRACH preamble under static conditions and multipath fading propagation conditions for a given SNR. + +#### 8.4.1.4 Method of test + +##### 8.4.1.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested: for single carrier: M; see clause 4.9.1. + +##### 8.4.1.4.2 Procedure + +- 1) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to all BS antenna connectors for diversity reception via a combining network as shown in annex D.5 and D.6 for *BS type 1-C* and *BS type 1-H* respectively. +- 2) Adjust the AWGN generator, according to the SCS and channel bandwidth. + +**Table 8.4.1.4.2-1: AWGN power level at the BS input** + +| Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------|-------------------------|----------------------| +| 15 | 5 | -83.5 dBm / 4.5MHz | +| | 10 | -80.3 dBm / 9.36MHz | +| | 20 | -77.2 dBm / 19.08MHz | +| 30 | 10 | -80.6 dBm / 8.64MHz | +| | 20 | -77.4 dBm / 18.36MHz | +| | 40 | -74.2 dBm / 38.16MHz | +| | 100 | -70.1 dBm / 98.28MHz | + +NOTE: The AWGN power level contains an AWGN offset of 16dB by default. If needed for test purposes, the AWGN level can be reduced from the default by any value in the range 0dB to 16dB. Changing the AWGN level does not impact the validity of the test, as it reduces the effective base band SNR level. + +- 3) The characteristics of the wanted signal shall be configured according to the corresponding UL reference measurement channel defined in annex A and the test parameter *msg1-FrequencyStart* is set to 0. +- 4) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex G. +- 5) Adjust the frequency offset of the test signal according to table 8.4.1.5-1 or 8.4.1.5-2 or 8.4.1.5-3 or 8.4.1.6-1 or 8.4.1.6-2 or 8.4.1.6-3 or 8.4.1.6-4 or 8.4.1.7-1 or 8.4.1.7-2. +- 6) Adjust the equipment so that the SNR specified in table 8.4.1.5-1 or 8.4.1.5-2 or 8.4.1.5-3 or 8.4.1.6-1 or 8.4.1.6-2 or 8.4.1.6-3 or 8.4.1.6-4 or 8.4.1.7-1 or 8.4.1.7-2 is achieved at the BS input during the PRACH preambles. +- 7) The test signal generator sends a preamble and the receiver tries to detect the preamble. This pattern is repeated as illustrated in figure 8.4.1.4.2-1. The preambles are sent with certain timing offsets as described below. The following statistics are kept: the number of preambles detected in the idle period and the number of missed preambles. + +![Figure 8.4.1.4.2-1: PRACH preamble test pattern. The diagram shows two rectangular boxes, each containing the word 'Preamble', separated by a horizontal line. To the right of the second box, there are three dots (ellipsis) indicating a continuation of the pattern.](7804e53c30a2aabd89fa25b8c2f28e14_img.jpg) + +Figure 8.4.1.4.2-1: PRACH preamble test pattern. The diagram shows two rectangular boxes, each containing the word 'Preamble', separated by a horizontal line. To the right of the second box, there are three dots (ellipsis) indicating a continuation of the pattern. + +**Figure 8.4.1.4.2-1: PRACH preamble test pattern** + +The timing offset base value for PRACH preamble format 0 is set to 50% of $N_{cs}$ . This offset is increased within the loop, by adding in each step a value of 0.1us, until the end of the tested range, which is 0.9us. Then the loop is being reset and the timing offset is set again to 50% of $N_{cs}$ . The timing offset scheme for PRACH preamble format 0 is presented in figure 8.4.1.4.2-2. + +![Timing offset scheme for PRACH preamble format 0 diagram](34921caa1996eef32dd520e93a1e64b8_img.jpg) + +A diagram illustrating the timing offset scheme for PRACH preamble format 0. It shows a horizontal timeline with 8 equal segments. Below each segment is a semi-circular arc pointing downwards, with an arrowhead at its center. A large curved arrow at the top points from the start of the first segment to the start of the eighth segment, indicating a loop or reset mechanism. + +Timing offset scheme for PRACH preamble format 0 diagram + +**Figure 8.4.1.4.2-2: Timing offset scheme for PRACH preamble format 0** + +The timing offset base value for PRACH preamble format A1, A2, A3, B4, C0 and C2 is set to 0. This offset is increased within the loop, by adding in each step a value of 0.1us, until the end of the tested range, which is 0.8 us. Then the loop is being reset and the timing offset is set again to 0. The timing offset scheme for PRACH preamble format A1, A2, A3, B4, C0 and C2 is presented in figure 8.4.1.4.2-3. + +![Timing offset scheme for PRACH preamble format A1 A2, A3, B4, C0 and C2 diagram](200e4dcbe6f9ac71fa87da9310aac99a_img.jpg) + +A diagram illustrating the timing offset scheme for PRACH preamble format A1, A2, A3, B4, C0 and C2. It is identical to the previous diagram, showing a horizontal timeline with 8 equal segments, semi-circular arcs with arrowheads below each, and a large curved arrow at the top indicating a loop or reset mechanism. + +Timing offset scheme for PRACH preamble format A1 A2, A3, B4, C0 and C2 diagram + +**Figure 8.4.1.4.2-3: Timing offset scheme for PRACH preamble format A1 A2, A3, B4, C0 and C2** + +**8.4.1.5 Test requirement for Normal Mode** + +Pfa shall not exceed 0.1%. Pd shall not be below 99% for the SNRs in tables 8.4.1.5-1 to 8.4.1.5-3. + +**Table 8.4.1.5-1: PRACH missed detection test requirements for Normal Mode, 1.25 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex G) | Frequency offset | SNR (dB) | +|-----------------------|-----------------------|---------------------------------------------------------|------------------|----------------| +| | | | | Burst format 0 | +| 1 | 2 | AWGN | 0 | -14.2 | +| | | TDLC300-100 Low | 400 Hz | -6.0 | +| | 4 | AWGN | 0 | -16.4 | +| | | TDLC300-100 Low | 400 Hz | -11.3 | +| | 8 | AWGN | 0 | -18.6 | +| | | TDLC300-100 Low | 400 Hz | -15.2 | + +**Table 8.4.1.5-2: PRACH missed detection test requirements for Normal Mode, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex G) | Frequency offset | SNR (dB) | | | | | | +|-----------------------|-----------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | | | | Burst format A1 | Burst format A2 | Burst format A3 | Burst format B4 | Burst format C0 | Burst format C2 | +| 1 | 2 | AWGN | 0 | -9.0 | -12.3 | -13.9 | -16.5 | -6.0 | -12.2 | +| | | TDLC300-100 Low | 400 Hz | -1.5 | -4.2 | -6.0 | -8.2 | 1.4 | -4.3 | +| | 4 | AWGN | 0 | -11.3 | -14.0 | -15.7 | -18.7 | -8.4 | -13.8 | +| | | TDLC300-100 Low | 400 Hz | -6.7 | -9.7 | -11.1 | -13.2 | -3.7 | -9.6 | +| | 8 | AWGN | 0 | -13.5 | -16.4 | -17.9 | -20.9 | -10.8 | -16.3 | +| | | TDLC300-100 Low | 400 Hz | -10.4 | -13.3 | -14.6 | -16.7 | -7.5 | -13.3 | + +**Table 8.4.1.5-3: PRACH missed detection test requirements for Normal Mode, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex G) | Frequency offset | SNR (dB) | | | | | | +|-----------------------|-----------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | | | | Burst format A1 | Burst format A2 | Burst format A3 | Burst format B4 | Burst format C0 | Burst format C2 | +| 1 | 2 | AWGN | 0 | -8.8 | -11.7 | -13.5 | -16.2 | -5.8 | -11.6 | +| | | TDLC300-100 Low | 400 Hz | -2.2 | -5.1 | -6.8 | -9.3 | 0.7 | -5.0 | +| | 4 | AWGN | 0 | -11.1 | -13.9 | -15.6 | -18.7 | -8.3 | -13.8 | +| | | TDLC300-100 Low | 400 Hz | -6.6 | -9.8 | -11.4 | -13.9 | -3.9 | -9.8 | +| | 8 | AWGN | 0 | -13.4 | -16.3 | -17.8 | -20.8 | -10.7 | -16.2 | +| | | TDLC300-100 Low | 400 Hz | -10.1 | -13.1 | -14.5 | -17.0 | -7.2 | -13.1 | + +**Table 8.4.1.5-4: Void****Table 8.4.1.5-5: Void** + +#### 8.4.1.6 Test requirement for high speed train + +Pfa shall not exceed 0.1%. Pd shall not be below 99% for the SNRs in tables 8.4.1.6-1 to 8.4.1.6-4. + +**Table 8.4.1.6-1: PRACH missed detection requirements for high speed train, burst format 0, restricted set type A, 1.25 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex G) | Frequency offset | SNR (dB) | +|-----------------------|-----------------------|---------------------------------------------------------|------------------|----------------| +| | | | | Burst format 0 | +| 1 | 2 | AWGN | 625 Hz | -11.7 | +| | | AWGN | 1340 Hz | -13.5 | +| | | TDLC300-100 Low | 0 Hz | -5.7 | +| | 4 | AWGN | 625 Hz | -14.2 | +| | | AWGN | 1340 Hz | -15.9 | +| | | TDLC300-100 Low | 0 Hz | -11.2 | +| | 8 | AWGN | 625 Hz | -16.2 | +| | | AWGN | 1340 Hz | -18.1 | +| | | TDLC300-100 Low | 0 Hz | -15.6 | + +**Table 8.4.1.6-2: PRACH missed detection requirements for high speed train, burst format 0, restricted set type B, 1.25 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (annex G) | Frequency offset | SNR (dB) | +|-----------------------|-----------------------|---------------------------------------------------------|------------------|----------------| +| | | | | Burst format 0 | +| 1 | 2 | AWGN | 625 Hz | -11.3 | +| | | AWGN | 2334 Hz | -12.8 | +| | | TDLC300-100 Low | 0 Hz | -5.4 | +| | 4 | AWGN | 625 Hz | -13.7 | +| | | AWGN | 2334 Hz | -15.1 | +| | | TDLC300-100 Low | 0 Hz | -11.1 | +| | 8 | AWGN | 625 Hz | -16.0 | +| | | AWGN | 2334 Hz | -17.1 | +| | | TDLC300-100 Low | 0 Hz | -15.4 | + +**Table 8.4.1.6-3: PRACH missed detection requirements for high speed train, 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (Annex G) | Frequency offset | SNR (dB) | | | +|-----------------------|-----------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------| +| | | | | Burst format A2 | Burst format B4 | Burst format C2 | +| 1 | 2 | AWGN | 1740 Hz | -11.0 | -14.0 | -10.8 | +| | 4 | AWGN | 1740 Hz | -13.2 | -16.4 | -13.1 | +| | 8 | AWGN | 1740 Hz | -15.3 | -17.9 | -15.2 | + +**Table 8.4.1.6-4: PRACH missed detection requirements for high speed train, 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (Annex G) | Frequency offset | SNR (dB) | | | +|-----------------------|-----------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------| +| | | | | Burst format A2 | Burst format B4 | Burst format C2 | +| 1 | 2 | AWGN | 3334 Hz | -10.9 | -14.3 | -10.7 | +| | 4 | AWGN | 3334 Hz | -13.1 | -16.4 | -13.1 | +| | 8 | AWGN | 3334 Hz | -15.1 | -18.1 | -15.1 | + +#### 8.4.1.7 Test requirement for PRACH with $L_{RA}=1151$ and $L_{RA}=571$ + +Pfa shall not exceed 0.1%. Pd shall not be below 99% for the SNRs in tables 8.4.1.7-1 and 8.4.1.7-2. + +**Table 8.4.1.7-1: Missed detection requirements for PRACH with $L_{RA}=1151$ , 15 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (Annex G) | Frequency offset | SNR (dB) | | | +|-----------------------|-----------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------| +| | | | | Burst format A2 | Burst format B4 | Burst format C2 | +| 1 | 2 | AWGN | 0 | -20.8 | -24.8 | -20.8 | +| | | TDLA30-10 Low | 400 Hz | -14.5 | -17.7 | -14.6 | + +**Table 8.4.1.7-2: Missed detection requirements for PRACH with $L_{RA}=571$ , 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (Annex G) | Frequency offset | SNR (dB) | | | +|-----------------------|-----------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------| +| | | | | Burst format A2 | Burst format B4 | Burst format C2 | +| 1 | 2 | AWGN | 0 | -17.8 | -21.7 | -17.8 | +| | | TDLA30-10 Low | 400 Hz | -11.5 | -15.2 | -11.5 | + +## Annex A (normative): Reference measurement channels + +### A.1 Fixed Reference Channels for reference sensitivity level, ACS, in-band blocking, out-of-band blocking, receiver intermodulation and in-channel selectivity (QPSK, R=1/3) + +The parameters for the reference measurement channels are specified in table A.1-1 for FR1 reference sensitivity level, ACS, in-band blocking, out-of-band blocking, receiver intermodulation and in-channel selectivity. The parameters for the band n46, n96 and n102 reference measurement channels are specified in table A.1-1a for reference sensitivity level, ACS, in-band blocking, out-of-band blocking, receiver intermodulation, in-channel selectivity. + +**Table A.1-1: FRC parameters for FR1 reference sensitivity level, ACS, in-band blocking, out-of-band blocking, receiver intermodulation and in-channel selectivity** + +| Reference channel | G-FR1-A1-1 | G-FR1-A1-2 | G-FR1-A1-3 | G-FR1-A1-4 | G-FR1-A1-5 | G-FR1-A1-6 | G-FR1-A1-7 | G-FR1-A1-8 | G-FR1-A1-9 | G-FR1-A1-10 | G-FR1-A1-11 | +|-----------------------------------------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|-------------|-------------| +| Subcarrier spacing (kHz) | 15 | 30 | 60 | 15 | 30 | 60 | 15 | 30 | 60 | 15 | 15 | +| Allocated resource blocks | 25 | 11 | 11 | 106 | 51 | 24 | 15 | 6 | 6 | 24 | 105 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 1/3 | 1/3 | 1/3 | 1/3 | 1/3 | 1/3 | 1/3 | 1/3 | 1/3 | 1/3 | 1/3 | +| Payload size (bits) | 2152 | 984 | 984 | 9224 | 4352 | 2088 | 1320 | 528 | 528 | [2088] | [8968] | +| Transport block CRC (bits) | 16 | 16 | 16 | 24 | 24 | 16 | 16 | 16 | 16 | 16 | 24 | +| Code block CRC size (bits) | - | - | - | 24 | - | - | - | - | - | - | 24 | +| Number of code blocks - C | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | +| Code block size including CRC (bits) (Note 3) | 2168 | 1000 | 1000 | 4648 | 4376 | 2104 | 1336 | 544 | 544 | [2104] | [4520] | +| Total number of bits per slot | 7200 | 3168 | 3168 | 30528 | 14688 | 6912 | 4320 | 1728 | 1728 | [6912] | [30240] | +| Total symbols per slot | 3600 | 1584 | 1584 | 15264 | 7344 | 3456 | 2160 | 864 | 864 | [3456] | [15120] | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS, additional DM-RS position = pos1 with $l_0 = 2$ , $l = 11$ as per table 6.4.1.1.3-3 of TS 38.211 [17]. + +NOTE 2: MCS index 4 and target coding rate = 308/1024 are adopted to calculate payload size. + +NOTE 3: Code block size including CRC (bits) equals to $K'$ in TS 38.212 [16], clause 5.2.2. + +**Table A.1-1a: FRC parameters for band n46, n96 and n102 reference sensitivity level, ACS, in-band blocking, out-of-band blocking, receiver intermodulation, in-channel selectivity** + +| Reference channel | G-FR1-A1-12 | G-FR1-A1-13 | G-FR1-A1-14 | G-FR1-A1-15 | G-FR1-A1-16 | G-FR1-A1-17 | G-FR1-A1-18 | G-FR1-A1-19 | +|-----------------------------------------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------| +| Channel bandwidth (MHz) | 10 | 10 | 20 | 20 | 40 | 40 | 60 | 80 | +| Subcarrier spacing (kHz) | 15 | 30 | 15 | 30 | 15 | 30 | 30 | 30 | +| Allocated resource blocks | 5 | 4 | 10 | 10 | 21 | 21 | 32 | 43 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 1/3 | 1/3 | 1/3 | 1/3 | 1/3 | 1/3 | 1/3 | 1/3 | +| Payload size (bits) | 432 | 352 | 888 | 888 | 1864 | 1864 | 2792 | 3752 | +| Transport block CRC (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | +| Code block CRC size (bits) | - | - | - | - | - | - | - | - | +| Number of code blocks - C | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| Code block size including CRC (bits) (Note 3) | 448 | 368 | 904 | 904 | 1880 | 1880 | 2808 | 3768 | +| Total number of bits per slot | 1440 | 1152 | 2880 | 2880 | 6048 | 6048 | 9216 | 12384 | +| Total symbols per slot | 720 | 576 | 1440 | 1440 | 3024 | 3024 | 4608 | 6192 | + +NOTE 1: *UL-DMRS-config-type = 1* with *UL-DMRS-max-len = 1*, *UL-DMRS-add-pos = 1* with *2*, *2*, *11* as per table 6.4.1.1.3-3 of TS 38.211 [17]. + +NOTE 2: MCS index 4 and target coding rate = 308/1024 are adopted to calculate payload size for receiver sensitivity and in-channel selectivity + +NOTE 3: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [16]. + +NOTE 4: For reference channel A1-12, the allocated RB's are uniformly spaced over the channel bandwidth at RB index N, N+10, N+20, N+30, N+40 where N={0,1,2,3,4,...,9}. + +NOTE 5: For reference channel A1-13, the allocated RB's are uniformly spaced over the channel bandwidth at RB index N, N+5, N+10, N+15 where N={0,1,2,3,4}. + +NOTE 7: For reference channel A1-14, the allocated RB's are uniformly spaced over the channel bandwidth at RB index N, N+10,N+20,...,N+90 where N={0,1,2,3,...,9}. + +NOTE 8: For reference channel A1-15, the allocated RB's are uniformly spaced over the channel bandwidth at RB index N, N+5,N+10,...,N+45 where N={0,1,2,3,4}. + +NOTE 10: For reference channel A1-16, the allocated RB's are uniformly spaced over the channel bandwidth at RB index N, N+10,N+20,...,N+200 where N={0,1,2,3,4,...,9}. + +NOTE 11: For reference channel A1-17, the allocated RB's are uniformly spaced over the channel bandwidth at RB index N, N+5, N+10, ..., N+100 where N={0,1,2,3,4}. + +NOTE 12: For reference channel A1-18, the allocated RB's are uniformly spaced over the channel bandwidth at RB index N, N+5,N+10,...,N+155 where N={0,1,2,3,4}. + +NOTE 13: For reference channel A1-19, the allocated RB's are uniformly spaced over the channel bandwidth at RB index N, N+5,N+10,...,N+210 where N={0,1,2,3,4}. + +## A.2 Fixed Reference Channels for dynamic range (16QAM, R=2/3) + +The parameters for the reference measurement channels are specified in table A.2-1 for FR1 dynamic range. The parameters for the band n46, n96 and n102 reference measurement channels are specified in table A.2-1a and A.2-1b for band n46, n96 and n102 dynamic range. + +**Table A.2-1: FRC parameters for FR1 dynamic range** + +| Reference channel | G-FR1-A2-1 | G-FR1-A2-2 | G-FR1-A2-3 | G-FR1-A2-4 | G-FR1-A2-5 | G-FR1-A2-6 | +|-----------------------------------------------|------------|------------|------------|------------|------------|------------| +| Subcarrier spacing (kHz) | 15 | 30 | 60 | 15 | 30 | 60 | +| Allocated resource blocks | 25 | 11 | 11 | 106 | 51 | 24 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | +| Code rate (Note 2) | 2/3 | 2/3 | 2/3 | 2/3 | 2/3 | 2/3 | +| Payload size (bits) | 9224 | 4032 | 4032 | 38936 | 18960 | 8968 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | - | - | 24 | 24 | 24 | +| Number of code blocks - C | 2 | 1 | 1 | 5 | 3 | 2 | +| Code block size including CRC (bits) (Note 3) | 4648 | 4056 | 4056 | 7816 | 6352 | 4520 | +| Total number of bits per slot | 14400 | 6336 | 6336 | 61056 | 29376 | 13824 | +| Total symbols per slot | 3600 | 1584 | 1584 | 15264 | 7344 | 3456 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS, additional DM-RS position = pos1 with $l_0 = 2$ , $l = 11$ as per table 6.4.1.1.3-3 of TS 38.211 [17]. + +NOTE 2: MCS index 16 and target coding rate = 658/1024 are adopted to calculate payload size. + +NOTE 3: Code block size including CRC (bits) equals to $K'$ in TS 38.212 [16], clause 5.2.2. + +**Table A.2-1a: FRC parameters for dynamic range for band n46, n96 and n102** + +| Reference channel | G-FR1-A2-7 | G-FR1-A2-8 | G-FR1-A2-9 | G-FR1-A2-10 | G-FR1-A2-11 | G-FR1-A2-12 | G-FR1-A2-13 | G-FR1-A2-14 | +|-----------------------------------------------|------------|------------|------------|-------------|-------------|-------------|-------------|-------------| +| Channel bandwidth (MHz) | 10 | 10 | 20 | 20 | 40 | 40 | 60 | 80 | +| Subcarrier spacing (kHz) | 15 | 30 | 15 | 30 | 15 | 30 | 30 | 30 | +| Allocated resource blocks | 5 | 4 | 10 | 10 | 21 | 21 | 32 | 43 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | +| Code rate (Note 2) | 2/3 | 2/3 | 2/3 | 2/3 | 2/3 | 2/3 | 2/3 | 2/3 | +| Payload size (bits) | 1864 | 1480 | 3752 | 3752 | 7808 | 7808 | 11784 | 15880 | +| Transport block CRC (bits) | 16 | 16 | 16 | 16 | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | - | - | - | - | - | - | 24 | 24 | +| Number of code blocks - C | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | +| Code block size including CRC (bits) (Note 3) | 1880 | 1496 | 3768 | 3768 | 7832 | 7832 | 5928 | 7976 | +| Total number of bits per slot | 2880 | 2304 | 5760 | 5760 | 12096 | 12096 | 18432 | 24768 | +| Total symbols per slot | 720 | 576 | 1440 | 1440 | 3024 | 3024 | 4608 | 6192 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS, additional DM-RS position = pos1 with l0= 2, l = 11 as per table 6.4.1.1.3-3 of TS 38.211 [17]. + +NOTE 2: MCS index 16 and target coding rate = 658/1024 are adopted to calculate payload size. + +NOTE 3: Code block size including CRC (bits) equals to K' in sub-clause 5.2.2 of TS 38.212 [16]. + +NOTE 4: For reference channel A2-7, the allocated RB's are uniformly spaced over the channel bandwidth at RB index N, N+10, N+20, N+30, N+40 where N={0,1,2,3,4,5,6,7,8,9}. + +NOTE 5: For reference channel A2-8, the allocated RB's are uniformly spaced over the channel bandwidth at RB index N, N+5, N+10, N+15 where N={0,1,2,3,4}. + +NOTE 6: For reference channel A2-9, the allocated RB's are uniformly spaced over the channel bandwidth at RB index N, N+10,N+20,...,N+90 where N={0,1,2,3,...,9}. + +NOTE 7: For reference channel A2-10, the allocated RB's are uniformly spaced over the channel bandwidth at RB index N, N+5,N+10,..., N+45 where N={0,1,2,3,4}. + +NOTE 8: For reference channel A2-11, the allocated RB's are uniformly spaced over the channel bandwidth at RB index N, N+10,N+20,...,N+200 where N={0,1,2,3,4,...,9}. + +NOTE 9: For reference channel A2-12, the allocated RB's are uniformly spaced over the channel bandwidth at RB index N, N+5, N+10, ..., N+100 where N={0,1,2,3,4}. + +NOTE 10: For reference channel A2-13, the allocated RB's are uniformly spaced over the channel bandwidth at RB index N, N+5,N+10,..., N+155 where N={0,1,2,3,4}. + +NOTE 11: For reference channel A2-14, the allocated RB's are uniformly spaced over the channel bandwidth at RB index N, N+5,N+10,..., N+210 where N={0,1,2,3,4}. + +## A.3 Fixed Reference Channels for performance requirements (QPSK, R=193/1024) + +The parameters for the reference measurement channels are specified in table A.3-2, table A.3-2A, table A.3-4 and table A.3-6 for FR1 PUSCH performance requirements: + +- FRC parameters are specified in table A.3-2 for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer. +- FRC parameters are specified in table A.3-2A for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos2 and 1 transmission layer. +- FRC parameters are specified in table A.3-4 for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 2 transmission layers. + +- FRC parameters are specified in table A.3-6 for FR1 PUSCH with transform precoding enabled, additional DM-RS position = pos1 and 1 transmission layer. + +The parameters for the reference measurement channels are specified in table A.3-7 for FR1 PUSCH performance requirements for TBoMS: + +- FRC parameters are specified in table A.3-7 for FR1 PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer. + +**Table A.3-1: Void** + +**Table A.3-2: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | G-FR1-A3-8 | G-FR1-A3-9 | G-FR1-A3-10 | G-FR1-A3-11 | G-FR1-A3-12 | G-FR1-A3-13 | G-FR1-A3-14 | +|-----------------------------------------------|------------|------------|-------------|-------------|-------------|-------------|-------------| +| Subcarrier spacing (kHz) | 15 | 15 | 15 | 30 | 30 | 30 | 30 | +| Allocated resource blocks | 25 | 52 | 106 | 24 | 51 | 106 | 273 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 193/1024 | 193/1024 | 193/1024 | 193/1024 | 193/1024 | 193/1024 | 193/1024 | +| Payload size (bits) | 1352 | 2856 | 5768 | 1320 | 2792 | 5768 | 14856 | +| Transport block CRC (bits) | 16 | 16 | 24 | 16 | 16 | 24 | 24 | +| Code block CRC size (bits) | - | - | 24 | - | - | 24 | 24 | +| Number of code blocks - C | 1 | 1 | 2 | 1 | 1 | 2 | 4 | +| Code block size including CRC (bits) (Note 2) | 1368 | 2872 | 2920 | 1336 | 2808 | 2920 | 3744 | +| Total number of bits per slot | 7200 | 14976 | 30528 | 6912 | 14688 | 30528 | 78624 | +| Total symbols per slot | 3600 | 7488 | 15264 | 3456 | 7344 | 15264 | 39312 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1, $l_o = 2$ and $l = 11$ for PUSCH mapping type A, $l_o = 0$ and $l = 10$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [17]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [16]. + +**Table A.3-2A: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos2 and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | G-FR1-A3-33 | G-FR1-A3-33A | G-FR1-A3-34 | G-FR1-A3-34A | +|------------------------------------------------|-------------|--------------|-------------|--------------| +| Subcarrier spacing (kHz) | 15 | 15 | 30 | 30 | +| Allocated resource blocks | 52 | 25 | 106 | 24 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 11 | 11 | 11 | 11 | +| Modulation | QPSK | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 193/1024 | 193/1024 | 193/1024 | 193/1024 | +| Payload size (bits) | 2600 | 1256 | 5256 | 1192 | +| Transport block CRC (bits) | 16 | 16 | 24 | 16 | +| Code block CRC size (bits) | - | - | 24 | - | +| Number of code blocks - C | 1 | 1 | 2 | 1 | +| Code block size including CRC (bits) (Note 2) | 2616 | 1272 | 2664 | 1208 | +| Total number of bits per slot | 13728 | 6600 | 27984 | 6336 | +| Total resource elements per slot | 6846 | 3300 | 13992 | 3168 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, Additional DM-RS position = pos2, and $l_0$ = 2 or 3 for PUSCH mapping type A, as per table 6.4.1.1.3-3 of TS 38.211 [17]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [16]. + +**Table A.3-3: Void****Table A.3-4: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 2 transmission layers (QPSK, R=193/1024)** + +| Reference channel | G-FR1-A3-22 | G-FR1-A3-23 | G-FR1-A3-24 | G-FR1-A3-25 | G-FR1-A3-26 | G-FR1-A3-27 | G-FR1-A3-28 | +|-----------------------------------------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------| +| Subcarrier spacing (kHz) | 15 | 15 | 15 | 30 | 30 | 30 | 30 | +| Allocated resource blocks | 25 | 52 | 106 | 24 | 51 | 106 | 273 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 193/1024 | 193/1024 | 193/1024 | 193/1024 | 193/1024 | 193/1024 | 193/1024 | +| Payload size (bits) | 2728 | 5640 | 11528 | 2600 | 5512 | 11528 | 29736 | +| Transport block CRC (bits) | 16 | 24 | 24 | 16 | 24 | 24 | 24 | +| Code block CRC size (bits) | - | 24 | 24 | - | 24 | 24 | 24 | +| Number of code blocks - C | 1 | 2 | 4 | 1 | 2 | 4 | 8 | +| Code block size including CRC (bits) (Note 2) | 2744 | 2856 | 2912 | 2616 | 2792 | 2912 | 3744 | +| Total number of bits per slot | 14400 | 29952 | 61056 | 13824 | 29376 | 61056 | 157248 | +| Total symbols per slot | 7200 | 14976 | 30528 | 6912 | 14688 | 30528 | 78624 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1, $l_0$ = 2 and $l$ = 11 for PUSCH mapping type A, $l_0$ = 0 and $l$ = 10 for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [17]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [16]. + +**Table A.3-5: Void****Table A.3-6: FRC parameters for FR1 PUSCH performance requirements, transform precoding enabled, additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | G-FR1-A3-31 | G-FR1-A3-32 | +|-----------------------------------------------|-------------|-------------| +| Subcarrier spacing (kHz) | 15 | 30 | +| Allocated resource blocks | 25 | 24 | +| DFT-s-OFDM Symbols per slot (Note 1) | 12 | 12 | +| Modulation | QPSK | QPSK | +| Code rate (Note 2) | 193/1024 | 193/1024 | +| Payload size (bits) | 1352 | 1320 | +| Transport block CRC (bits) | 16 | 16 | +| Code block CRC size (bits) | - | - | +| Number of code blocks - C | 1 | 1 | +| Code block size including CRC (bits) (Note 2) | 1368 | 1336 | +| Total number of bits per slot | 7200 | 6912 | +| Total symbols per slot | 3600 | 3456 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1, $l_0 = 2$ and $l = 11$ for PUSCH mapping type A, $l_0 = 0$ and $l = 10$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [17]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [16]. + +**Table A.3-7: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | G-FR1-A3-35 | G-FR1-A3-36 | G-FR1-A3-37 | G-FR1-A3-38 | +|------------------------------------------------|-------------|-------------|-------------|-------------| +| Number of TBoMS slots | 2 | 4 | 2 | 4 | +| Subcarrier spacing [kHz] | 15 | 15 | 30 | 30 | +| Allocated resource blocks per slot | 5 | 5 | 5 | 5 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | +| Modulation | QPSK | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 193/1024 | 193/1024 | 193/1024 | 193/1024 | +| Payload size (bits) | 552 | 1128 | 552 | 1128 | +| Transport block CRC (bits) | 16 | 16 | 16 | 16 | +| Code block CRC size (bits) | - | - | - | - | +| Number of code blocks - C | 1 | 1 | 1 | 1 | +| Code block size including CRC (bits) (Note 2) | 568 | 1144 | 568 | 1144 | +| Total number of bits over all TBoMS slots | 2880 | 5760 | 2880 | 5760 | +| Total resource elements over all TBoMS slots | 1440 | 2880 | 1440 | 2880 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1, $l_0 = 2$ and $l = 11$ for PUSCH mapping type A, $l_0 = 0$ and $l = 10$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [17]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [16]. + +## A.3A Fixed Reference Channels for performance requirements (QPSK, R=99/1024) + +The parameters for the reference measurement channel are specified in table A.3A-1 for FR1 PUSCH performance requirements: + +- FRC parameters are specified in table A.3A-1 for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer. + +**Table A.3A-1: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=99/1024)** + +| Reference channel | G-FR1-A3A-1 | G-FR1-A3A-2 | G-FR1-A3A-3 | G-FR1-A3A-4 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|-------------|-------------| +| Subcarrier spacing (kHz) | 15 | 15 | 30 | 30 | +| Allocated resource blocks | 25 | 52 | 24 | 106 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | +| Modulation | QPSK | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 99/1024 | 99/1024 | 99/1024 | 99/1024 | +| Payload size (bits) | 704 | 1480 | 672 | 2976 | +| Transport block CRC (bits) | 16 | 16 | 16 | 16 | +| Code block CRC size (bits) | - | - | - | - | +| Number of code blocks - C | 1 | 1 | 1 | 1 | +| Code block size including CRC (bits) (Note 2) | 720 | 1496 | 688 | 2992 | +| Total number of bits per slot | 7200 | 14976 | 6912 | 30528 | +| Total symbols per slot | 3600 | 7488 | 3456 | 15264 | +| NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1, $l_0 = 2$ and $l = 11$ for PUSCH mapping type A, $l_0 = 0$ and $l = 10$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [17]. | | | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [16]. | | | | | + +## A.3B Fixed Reference Channels for performance requirements (QPSK, R=308/1024) + +The parameters for the reference measurement channel is specified in table A.3B-1 for FR1 PUSCH performance requirements: + +- FRC parameters are specified in table A.3B-1 for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos0 and 1 transmission layer. + +The parameters for the reference measurement channel are specified in table A.3B-2 and table A.3B-3 for FR1 PUSCH performance requirements with DM-RS bundling: + +- FRC parameters are specified in table A.3B-2 for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer. +- FRC parameters are specified in table A.3B-3 for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos0 and 1 transmission layer. + +Note: The FRC table A.3B-4, table A.3B-5, table A.3B-6 and table A.3B-7 defined in TS38.104 [2] and TS38.141-2 [3] are not used in this specification. + +**Table A.3B-1: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos0 and 1 transmission layer (QPSK, R=308/1024)** + +| Reference channel | G-FR1-A3B-1 | G-FR1-A3B-2 | G-FR1-A3B-3 | G-FR1-A3B-4 | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|-------------|-------------| +| Subcarrier spacing (kHz) | 15 | 15 | 30 | 30 | +| Allocated resource blocks | 25 | 52 | 24 | 106 | +| CP-OFDM Symbols per slot (Note 1) | 1 | 1 | 1 | 1 | +| Modulation | QPSK | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 308/1024 | 308/1024 | 308/1024 | 308/1024 | +| Payload size (bits) | 176 | 368 | 168 | 768 | +| Transport block CRC (bits) | 16 | 16 | 16 | 16 | +| Code block CRC size (bits) | - | - | - | - | +| Number of code blocks - C | 1 | 1 | 1 | 1 | +| Code block size including CRC (bits) (Note 2) | 192 | 384 | 184 | 784 | +| Total number of bits per slot | 600 | 1248 | 576 | 2544 | +| Total symbols per slot | 300 | 624 | 288 | 1272 | +| NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos0, $l_0 = 0$ as per table 6.4.1.1.3-3 of TS 38.211 [17]. | | | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [16]. | | | | | + +**Table A.3B-2: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer (QPSK, R=308/1024)** + +| Reference channel | G-FR1-A3B-5 | G-FR1-A3B-6 | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Subcarrier spacing [kHz] | 15 | 30 | +| Allocated resource blocks | 25 | 24 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | +| Modulation | QPSK | QPSK | +| Code rate (Note 2) | 308/1024 | 308/1024 | +| Payload size (bits) | 2152 | 2088 | +| Transport block CRC (bits) | 16 | 16 | +| Code block CRC size (bits) | - | - | +| Number of code blocks - C | 1 | 1 | +| Code block size including CRC (bits) (Note 2) | 2168 | 2104 | +| Total number of bits per slot | 7200 | 6912 | +| Total resource elements per slot | 3600 | 3456 | +| NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1 , $l_0 = 2$ and $l = 11$ for PUSCH mapping type A, $l_0 = 0$ and $l = 10$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [20]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. | | | + +**Table A.3B-3: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, *Additional DM-RS position = pos0* and 1 transmission layer (QPSK, R=308/1024)** + +| Reference channel | G-FR1-A3B-7 | G-FR1-A3B-8 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Subcarrier spacing [kHz] | 15 | 30 | +| Allocated resource blocks | 25 | 24 | +| CP-OFDM Symbols per slot (Note 1) | 13 | 13 | +| Modulation | QPSK | QPSK | +| Code rate (Note 2) | 308/1024 | 308/1024 | +| Payload size (bits) | 2408 | 2280 | +| Transport block CRC (bits) | 16 | 16 | +| Code block CRC size (bits) | - | - | +| Number of code blocks - C | 1 | 1 | +| Code block size including CRC (bits) (Note 2) | 2424 | 2296 | +| Total number of bits per slot | 7800 | 7488 | +| Total resource elements per slot | 3900 | 3744 | +| NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos0 with $l_0 = 2$ for PUSCH mapping type A, $l_0 = 0$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [20]. | | | +| NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [15]. | | | + +## A.4 Fixed Reference Channels for performance requirements (16QAM, R=658/1024) + +The parameters for the reference measurement channels are specified in table A.4-2, table A.4-2A and table A.4-4 for FR1 PUSCH performance requirements: + +- FRC parameters are specified in table A.4-2 for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer. +- FRC parameters are specified in table A.4-2A for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos2 and 1 transmission layer. +- FRC parameters are specified in table A.4-2B for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos2 and 1 transmission layers. +- FRC parameters are specified in table A.4-4 for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 2 transmission layers. + +**Table A.4-1: Void** + +**Table A.4-2: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer (16QAM, R=658/1024)** + +| Reference channel | G-FR1-A4-8 | G-FR1-A4-9 | G-FR1-A4-10 | G-FR1-A4-11 | G-FR1-A4-12 | G-FR1-A4-13 | G-FR1-A4-14 | +|-----------------------------------------------|------------|------------|-------------|-------------|-------------|-------------|-------------| +| Subcarrier spacing (kHz) | 15 | 15 | 15 | 30 | 30 | 30 | 30 | +| Allocated resource blocks | 25 | 52 | 106 | 24 | 51 | 106 | 273 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | +| Code rate (Note 2) | 658/1024 | 658/1024 | 658/1024 | 658/1024 | 658/1024 | 658/1024 | 658/1024 | +| Payload size (bits) | 9224 | 19464 | 38936 | 8968 | 18960 | 38936 | 100392 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | 24 | 24 | 24 | 24 | +| Number of code blocks - C | 2 | 3 | 5 | 2 | 3 | 5 | 12 | +| Code block size including CRC (bits) (Note 2) | 4648 | 6520 | 7816 | 4520 | 6352 | 7816 | 8392 | +| Total number of bits per slot | 14400 | 29952 | 61056 | 13824 | 29376 | 61056 | 157248 | +| Total symbols per slot | 3600 | 7488 | 15264 | 3456 | 7344 | 15264 | 39312 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1, $l_o = 2$ and $l = 11$ for PUSCH mapping type A, $l_o = 0$ and $l = 10$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [17]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [16]. + +**Table A.4-2A: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos2 and 1 transmission layer (16QAM, R=658/1024)** + +| Reference channel | G-FR1-A4-29 | G-FR1-A4-29A | G-FR1-A4-30 | G-FR1-A4-30A | +|------------------------------------------------|-------------|--------------|-------------|--------------| +| Subcarrier spacing (kHz)) | 15 | 15 | 30 | 30 | +| Allocated resource blocks | 52 | 25 | 106 | 24 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 11 | 11 | 11 | 11 | +| Modulation | 16QAM | 16QAM | 16QAM | 16QAM | +| Code rate (Note 2) | 658/1024 | 658/1024 | 658/1024 | 658/1024 | +| Payload size (bits) | 17424 | 8456 | 35856 | 8064 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | - | +| Number of code blocks - C | 3 | 2 | 5 | 1 | +| Code block size including CRC (bits) (Note 2) | 5840 | 4264 | 7200 | 8088 | +| Total number of bits per slot | 27456 | 13200 | 55968 | 12672 | +| Total resource elements per slot | 6846 | 3300 | 13992 | 3168 | + +NOTE 1: *DM-RS configuration type = 1* with *DM-RS duration = single-symbol DM-RS* and the number of DM-RS CDM groups without data is 2, *Additional DM-RS position = pos2*, and $l_0 = 2$ or 3 for PUSCH mapping type A, as per table 6.4.1.1.3-3 of TS 38.211 [17]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [16]. + +**Table A.4-2B: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos2 and 1 transmission layer (16QAM, R=658/1024)** + +| Reference channel | G-FR1-A4-31A | G-FR1-A4-31 | G-FR1-A4-32A | G-FR1-A4-32 | +|-----------------------------------------------|--------------|-------------|--------------|-------------| +| Subcarrier spacing [kHz] | 15 | 15 | 30 | 30 | +| Allocated resource blocks | 12 | 25 | 12 | 50 | +| CP-OFDM Symbols per slot (Note 1) | 11 | 11 | 11 | 11 | +| Modulation | 16QAM | 16QAM | 16QAM | 16QAM | +| Code rate (Note 2) | 658/1024 | 658/1024 | 658/1024 | 658/1024 | +| Payload size (bits) | 4032 | 8456 | 4032 | 16896 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | - | 24 | - | 24 | +| Number of code blocks - C | 1 | 2 | 1 | 3 | +| Code block size including CRC (bits) (Note 2) | 4056 | 4264 | 4056 | 5664 | +| Total number of bits per slot | 6336 | 13200 | 6336 | 26400 | +| Total symbols per slot | 1584 | 3300 | 1584 | 6600 | + +NOTE 1: *DM-RS configuration type = 1* with *DM-RS duration = single-symbol DM-RS* and the number of DM-RS CDM groups without data is 2, *Additional DM-RS position = pos2*, $l_0 = 2$ for PUSCH mapping type A, $l_0 = 2$ for PUSCH mapping type B, as per table 6.4.1.1.3-3 of TS 38.211 [17]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [16]. + +**Table A.4-3: Void****Table A.4-4: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 2 transmission layers (16QAM, R=658/1024)** + +| Reference channel | G-FR1-A4-22 | G-FR1-A4-23 | G-FR1-A4-24 | G-FR1-A4-25 | G-FR1-A4-26 | G-FR1-A4-27 | G-FR1-A4-28 | +|-----------------------------------------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------| +| Subcarrier spacing (kHz) | 15 | 15 | 15 | 30 | 30 | 30 | 30 | +| Allocated resource blocks | 25 | 52 | 106 | 24 | 51 | 106 | 273 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | +| Code rate (Note 2) | 658/1024 | 658/1024 | 658/1024 | 658/1024 | 658/1024 | 658/1024 | 658/1024 | +| Payload size (bits) | 18432 | 38936 | 77896 | 17928 | 37896 | 77896 | 200808 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | 24 | 24 | 24 | 24 | +| Number of code blocks - C | 3 | 5 | 10 | 3 | 5 | 10 | 24 | +| Code block size including CRC (bits) (Note 2) | 6176 | 7816 | 7816 | 6008 | 7608 | 7816 | 8392 | +| Total number of bits per slot | 28800 | 59904 | 122112 | 27648 | 58752 | 122112 | 314496 | +| Total symbols per slot | 7200 | 14976 | 30528 | 6912 | 14688 | 30528 | 78624 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1, $l_o = 2$ and $l = 11$ for PUSCH mapping type A, $l_o = 0$ and $l = 10$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [17]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [16]. + +## A.5 Fixed Reference Channels for performance requirements (64QAM, R=567/1024) + +The parameters for the reference measurement channels are specified in table A.5-2 and table A.5-3 for FR1 PUSCH performance requirements: + +- FRC parameters are specified in table A.5-2 for FR1 PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer. +- FRC parameters are specified in table A.5-3 for FR1 interlaced PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer. + +Table A.5-1: Void + +Table A.5-2: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer (64QAM, R=567/1024) + +| Reference channel | G-FR1-A5-8 | G-FR1-A5-9 | G-FR1-A5-10 | G-FR1-A5-11 | G-FR1-A5-12 | G-FR1-A5-13 | G-FR1-A5-14 | +|-----------------------------------------------|------------|------------|-------------|-------------|-------------|-------------|-------------| +| Subcarrier spacing (kHz) | 15 | 15 | 15 | 30 | 30 | 30 | 30 | +| Allocated resource blocks | 25 | 52 | 106 | 24 | 51 | 106 | 273 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | 64QAM | 64QAM | 64QAM | 64QAM | 64QAM | 64QAM | 64QAM | +| Code rate (Note 2) | 567/1024 | 567/1024 | 567/1024 | 567/1024 | 567/1024 | 567/1024 | 567/1024 | +| Payload size (bits) | 12040 | 25104 | 50184 | 11528 | 24576 | 50184 | 131176 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | 24 | 24 | 24 | 24 | +| Number of code blocks - C | 2 | 3 | 6 | 2 | 3 | 6 | 16 | +| Code block size including CRC (bits) (Note 2) | 6056 | 8400 | 8392 | 5800 | 8224 | 8392 | 8224 | +| Total number of bits per slot | 21600 | 44928 | 91584 | 20736 | 44064 | 91584 | 235872 | +| Total symbols per slot | 3600 | 7488 | 15264 | 3456 | 7344 | 15264 | 39312 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1, $l_o = 2$ and $l = 11$ for PUSCH mapping type A, $l_o = 0$ and $l = 10$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [17]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [16]. + +**Table A.5-3: FRC parameters for FR1 interlaced PUSCH performance requirements, transform precoding disabled, *additional DM-RS position = pos1* and 1 transmission layer (64QAM, R=567/1024)** + +| Reference channel | G-FR1-A5-15 | G-FR1-A5-16 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| Subcarrier spacing [kHz] | 15 | 30 | +| Allocated resource blocks | 11 | 11 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | +| Modulation | 64QAM | 64QAM | +| Code rate | 567/1024 | 567/1024 | +| Payload size (bits) | 5248 | 5248 | +| Transport block CRC (bits) | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | +| Number of code blocks - C | 1 | 1 | +| Code block size including CRC (bits) (Note 2) | 5272 | 5272 | +| Total number of bits per slot (Note 3) | 9504 | 9504 | +| Total symbols per slot (Note 3) | 1584 | 1584 | +| NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, Additional DM-RS position = pos1 , l0= 2 and l =11 for PUSCH mapping type A, l0= 0 and l =10 for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [17].
NOTE 2: Code block size including CRC (bits) equals to K' in clause 5.2.2 of TS 38.212 [16].
NOTE 3: The calculation of the “Total number of bits per slot” and “Total symbols per slot” fields include the REs taken up by CG-UCI, if present. | | | + +## A.6 PRACH test preambles + +**Table A.6-1 Test preambles for Normal Mode in FR1** + +| Burst format | SCS (kHz) | Ncs | Logical sequence index | v | +|------------------------|-----------|-----|------------------------|----| +| 0 | 1.25 | 13 | 22 | 32 | +| A1, A2, A3, B4, C0, C2 | 15 | 23 | 0 | 0 | +| | 30 | 46 | 0 | 0 | + +**Table A.6-2: Void** + +**Table A.6-3: Test preambles for high speed train restricted set type A** + +| Burst format | SCS (kHz) | Ncs | Logical sequence index | v | +|--------------|-----------|-----|------------------------|---| +| 0 | 1.25 | 15 | 384 | 0 | + +**Table A.6-4: Test preambles for high speed train restricted set type B** + +| Burst format | SCS (kHz) | Ncs | Logical sequence index | v | +|--------------|-----------|-----|------------------------|----| +| 0 | 1.25 | 15 | 30 | 30 | + +**Table A.6-5: Test preambles for high speed train short formats** + +| Burst format | SCS (kHz) | Ncs | Logical sequence index | v | +|--------------|-----------|-----|------------------------|---| +| A2, B4, C2 | 15 | 23 | 0 | 0 | +| | 30 | 46 | 0 | 0 | + +**Table A.6-6: Test preambles for PRACH with $L_{RA}=1151$ and $L_{RA}=571$** + +| Burst format | SCS (kHz) | Ncs | Logical sequence index | v | +|--------------|-----------|-----|------------------------|---| +| A2, B4, C2 | 15 | 164 | 0 | 0 | +| | 30 | 190 | 0 | 0 | + +## A.7 Fixed Reference Channels for performance requirements (QPSK, $R=157/1024$ ) + +Note: [Different FRC numbers are assigned in](#) TS 38.104 [2] and TS 38.141-2 [3] [for the](#) FRCs in this annex. + +The parameters for the reference measurement channels are specified in table A.7-1 for FR1 PUSCH performance requirements for 2-step RA type: + +- FRC parameters are specified in table A.7-1 for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos2 and 1 transmission layer. +- FRC parameters are specified in table A.7-2 for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer. + +**Table A.7-1: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos2 and 1 transmission layer (QPSK, R=157/1024)** + +| Reference channel | G-FR1-A7-1 | G-FR1-A7-2 | +|------------------------------------------------|------------|------------| +| Subcarrier spacing (kHz) | 15 | 30 | +| Allocated resource blocks | 2 | 2 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 11 | 11 | +| Modulation | QPSK | QPSK | +| Code rate (Note 2) | 157/1024 | 157/1024 | +| Payload size (bits) | 80 | 80 | +| Transport block CRC (bits) | 16 | 16 | +| Code block CRC size (bits) | - | - | +| Number of code blocks – C | 1 | 1 | +| Code block size including CRC (bits) (Note 2) | 96 | 96 | +| Total number of bits per slot | 528 | 528 | +| Total resource elements per slot | 264 | 264 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos2, and $l_0 = 2$ or 3 for PUSCH mapping type A, $l_0 = 0$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [17]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [16]. + +**Table A.7-2: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=157/1024)** + +| Reference channel | G-FR1-A7-3 | G-FR1-A7-4 | +|------------------------------------------------|------------|------------| +| Subcarrier spacing (kHz) | 15 | 30 | +| Allocated resource blocks | 2 | 2 | +| Data bearing CP-OFDM Symbols per slot (Note 1) | 12 | 12 | +| Modulation | QPSK | QPSK | +| Code rate (Note 2) | 157/1024 | 157/1024 | +| Payload size (bits) | 88 | 88 | +| Transport block CRC (bits) | 16 | 16 | +| Code block CRC size (bits) | - | - | +| Number of code blocks - C | 1 | 1 | +| Code block size including CRC (bits) (Note 2) | 104 | 104 | +| Total number of bits per slot | 576 | 576 | +| Total resource elements per slot | 288 | 288 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1, $l_0 = 2$ and $l = 11$ for PUSCH mapping type A, $l_0 = 0$ and $l = 10$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [17]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [16]. + +## A.8 Fixed Reference Channels for performance requirements (256QAM, R=682.5/1024) + +Note: Different FRC numbers are assigned in TS 38.104 [2] and TS 38.141-2 [3] for the FRCs in this annex. + +The parameters for the reference measurement channels are specified in table A.8-1 for FR1 PUSCH performance requirements: + +- FRC parameters are specified in table A.8-1 for FR1 PUSCH with transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer. + +**Table A.8-1: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, *Additional DM-RS position = pos1* and 1 transmission layer (256QAM, R=682.5/1024)** + +| Reference channel | G-FR1-A8-1 | G-FR1-A8-2 | G-FR1-A8-3 | G-FR1-A8-4 | G-FR1-A8-5 | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------|------------|------------|------------| +| Subcarrier spacing [kHz] | 15 | 15 | 30 | 30 | 30 | +| Allocated resource blocks | 25 | 52 | 24 | 106 | 273 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | +| Modulation | 256QAM | 256QAM | 256QAM | 256QAM | 256QAM | +| Code rate (Note 2) | 682.5/1024 | 682.5/1024 | 682.5/1024 | 682.5/1024 | 682.5/1024 | +| Payload size (bits) | 18960 | 39936 | 18432 | 81976 | 208976 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | 24 | 24 | +| Number of code blocks - C | 3 | 5 | 3 | 10 | 25 | +| Code block size including CRC (bits) (Note 2) | 6352 | 8016 | 6176 | 8224 | 8384 | +| Total number of bits per slot | 28800 | 59904 | 27648 | 122112 | 314496 | +| Total symbols per slot | 3600 | 7488 | 3456 | 15264 | 39312 | +| NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, Additional DM-RS position = pos1 , l0 = 2 and l = 11 for PUSCH mapping type A, l0 = 0 and l = 10 for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [17]. | | | | | | +| NOTE 2: Code block size including CRC (bits) equals to K' in clause 5.2.2 of TS 38.212 [16]. | | | | | | + +## A.9 Fixed Reference Channels for performance requirements (16QAM, R=434/1024) + +Fixed Reference Channels for performance requirements (16QAM, R=434/1024) is not used in this specification. + +--- + +## 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. + +--- + +### 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. + +NOTE: This may, for instance, be the case for measurements of radiated emissions performed on an open field test site. + +--- + +### 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 60 721-3-3 [6]; +- 2) The equipment class for the equipment under test, as defined in the IEC 60 721-3-4 [7]; +- 3) The equipment that does not comply with the mentioned classes, the relevant classes from IEC 60 721 [8] documentation for temperature, humidity and vibration shall be declared. + +NOTE: Reduced functionality for conditions that fall outside of the standard operational conditions is 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 60 068-2-1 [9]. + +**Maximum temperature:** + +The test shall be performed with the environmental test equipment and methods including the required environmental phenomena into the equipment, conforming to the test procedure of IEC 60 068-2-2 [10]. + +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 60 068-2-6 [11]. Other environmental conditions shall be within the ranges specified in annex 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 60 068-2-1 [9] Test Ab/Ad and IEC 60 068-2-2 [10] Test Bb/Bd: Dry heat. + +**Lower voltage limit:** + +The equipment shall be supplied with a voltage equal to the lower limit declared by the manufacturer (as measured at the input terminals to the equipment). The tests shall be carried out at the steady state minimum and maximum temperature limits declared by the manufacturer for the equipment, to the methods described in IEC 60 068-2-1 [9] Test Ab/Ad and IEC 60 068-2-2 [10] Test Bb/Bd: Dry heat. + +--- + +## B.6 Measurement of test environments + +The measurement accuracy of the BS test environments defined in annex B 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 + +### C.1 Measurement of transmitter + +**Table C.1-1: Derivation of test requirements (Transmitter tests)** + +| Test | Minimum requirement in TS 38.104 [2] | Test Tolerance (TT) | Test requirement in the present document | +|----------------------------------------------------------------------------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------| +| 6.2 Base station output power | See TS 38.104 [2], clause 6.2 | Normal and extreme conditions:
0.7 dB, $f \leq 3.0$ GHz
1.0 dB, $3.0$ GHz $< f \leq 7.125$ GHz (Note)
1.5 dB, for bands n46, n96 and n102 | Formula:
Upper limit + TT, Lower limit - TT | +| 6.3 Output power dynamics | See TS 38.104 [2], clause 6.3 | 0.4 dB | Formula:
Total power dynamic range – TT (dB) | +| 6.4.1 Transmitter OFF power | See TS 38.104 [2], clause 6.4.1 | 2.0 dB, $f \leq 3.0$ GHz
2.5 dB, $3.0$ GHz $< f \leq 7.125$ GHz (Note)
3 dB, for bands n46, n96 and n102 | Formula:
Minimum Requirement + TT | +| 6.4.2 Transient period | See TS 38.104 [2], clause 6.4.2 | N/A | | +| 6.5.2 Frequency error | See TS 38.104 [2], clause 6.5.1 | 12 Hz | Formula:
Frequency Error limit + TT | +| 6.5.4 Time alignment error | See TS 38.104 [2], clause 6.5.3 | 25ns | Formula:
Time alignment error limit + TT + TT | +| 6.5.3 Modulation quality (EVM) | See TS 38.104 [2], clause 6.5.2 | 1% | Formula:
EVM limit + TT | +| 6.6.2 Occupied bandwidth | See TS 38.104 [2], clause 6.6.2 | 0 Hz | Formula:
Minimum Requirement + TT | +| 6.6.3 Adjacent Channel Leakage Power Ratio (ACLR) | See TS 38.104 [2], clause 6.6.3 | ACLR/CACLR:
BW $\leq 20$ MHz:
0.8dB

BW $> 20$ MHz:
1.2 dB

Absolute ACLR/CACLR:
0 dB | Formula:
ACLR Minimum Requirement - TT
Absolute limit + TT | +| 6.6.4 Operating band unwanted emissions | See TS 38.104 [2], clause 6.6.4 | Offsets $< 10$ MHz
1.5 dB, $f \leq 3.0$ GHz
1.8 dB, $3.0$ GHz $< f \leq 7.125$ GHz (Note)
2.2 dB, for bands n46, n96 and n102

Offsets $\geq 10$ MHz
0dB | Formula:
Minimum Requirement + TT | +| 6.6.5.5.1.1 General transmitter spurious emissions requirements Category A | See TS 38.104 [2], clause 6.6.5.1 | 0dB | Formula:
Minimum Requirement + TT | +| 6.6.5.5.1.1 General transmitter spurious emissions requirements Category B | See TS 38.104 [2], clause 6.6.5.1 | 0dB | Formula:
Minimum Requirement + TT | +| 6.6.5.5.1.2 Protection of the BS receiver of own or different BS | See TS 38.104 [2], clause 6.6.5.2.2 | 0dB | Formula:
Minimum Requirement + TT | + +| | | | | +|------------------------------------------------------------------------------------------------|-------------------------------------|-----|-----------------------------------| +| 6.6.5.5.1.3 Additional spurious emissions requirements | See TS 38.104 [2], clause 6.6.5.2.3 | 0dB | Formula: Minimum Requirement + TT | +| 6.6.5.5.1.4 Co-location with other base stations | See TS 38.104 [2], clause 6.6.5.2.4 | 0dB | Formula: Minimum Requirement + TT | +| 6.7 Transmitter intermodulation | See TS 38.104 [2], clause 6.7 | 0dB | Formula: Ratio + TT | +| NOTE 1: TT values for 4.2 GHz < f ≤ 7.125 GHz apply for BS operates in licensed spectrum only. | | | | +| NOTE 2: TT values are applicable for normal condition unless otherwise stated. | | | | + +## C.2 Measurement of receiver + +**Table C.2-1: Derivation of test requirements (Receiver tests)** + +| Test | Minimum requirement in TS 38.104 [2] | Test Tolerance (TT) | Test requirement in the present document | +|------------------------------------------------------------------------------|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------| +| 7.2 Reference sensitivity level | See TS 38.104 [2], clause 7.2 | Normal and extreme conditions:
0.7 dB, f ≤ 3.0 GHz
1.0 dB, 3.0 GHz < f ≤ 4.2 GHz
1.2 dB, 4.2 GHz < f ≤ 6.0 GHz
1.5 dB, 6 GHz < f ≤ 7.125 GHz
1.5 dB, for bands n46, n96 and n102 | Formula: Reference sensitivity power level + TT | +| 7.3 Dynamic range | See TS 38.104 [2], clause 7.3 | 0.3 dB | Formula: Wanted signal power + TT | +| 7.4 In-band selectivity and blocking | See TS 38.104 [2], clause 7.4 | 0dB | Formula: Wanted signal power + TT | +| 7.5 Out-of-band blocking | See TS 38.104 [2], clause 7.5 | 0dB | Formula: Wanted signal power + TT | +| 7.6 Receiver spurious emissions | See TS 38.104 [2], clause 7.6 | 0dB | Formula: Minimum Requirement + TT | +| 7.7 Receiver intermodulation | See TS 38.104 [2], clause 7.7 | 0dB | Formula: Wanted signal power + TT | +| 7.8 In-channel selectivity | See TS 38.104 [2], clause 7.8 | 1.4 dB, f ≤ 3.0 GHz
1.8 dB, 3.0 GHz < f ≤ 4.2 GHz
2.1 dB, 4.2 GHz < f ≤ 6.0 GHz
2.5 dB, 6 GHz < f ≤ 7.125 GHz
2.5 dB, for bands n46, n96 and n102 | Formula: Wanted signal power + TT | +| NOTE: TT values are applicable for normal condition unless otherwise stated. | | | | + +--- + +## C.3 Measurement of performance requirements + +**Table C.3-1: Derivation of Test Requirements (Performance tests)** + +| Test | Minimum Requirement in TS 38.104 [2] | Test Tolerance (TT) | Test requirement in the present document | +|------------------------------------------------------------------------------------|--------------------------------------|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.2.1 Performance requirements for PUSCH with transform precoding disabled | SNRs as specified | 0.6 dB for 1Tx cases
0.8 dB for 2Tx cases | Formula: SNR + TT
T-put limit unchanged | +| 8.2.2 Performance requirements for PUSCH with transform precoding enabled | SNRs as specified | 0.6 dB | Formula: SNR + TT
T-put limit unchanged | +| 8.2.3 Performance requirements for UCI multiplexed on PUSCH | SNRs as specified | 0.6 dB | Formula: SNR + TT
BLER limit unchanged | +| 8.2.4 Performance requirements for PUSCH for high speed train | SNRs as specified | 0.3 dB | Formula: SNR + TT
T-put limit unchanged | +| 8.2.5 Performance requirements for UL timing adjustment | SNRs as specified | 0.3 dB for AWGN | Formula: SNR + TT
T-put limit unchanged | +| 8.2.6 Performance requirements for PUSCH with 0.001% BLER | SNRs as specified | 0.3 dB | Formula: SNR + TT + 1dB

1dB is added to the test requirement to facilitate early test pass. The BLER delivered by the device during the test will be lower than the test requirement, which enables compliance to the requirement to be demonstrated with a number of observed block errors lower than a certain threshold. | +| 8.2.7 Performance requirements for PUSCH repetition Type A | SNRs as specified | 0.6 dB | Formula: SNR + TT
BLER limit unchanged | +| 8.2.8 Performance requirements for PUSCH Mapping Type B with non-slot transmission | SNRs as specified | 0.6 dB | Formula: SNR + TT
T-put limit unchanged | +| 8.2.12 Performance requirements for PUSCH TB over Multi-Slots | SNRs as specified | 0.6 dB | Formula: SNR + TT
T-put limit unchanged | +| 8.2.13 Performance requirements for PUSCH with DM-RS bundling | SNRs as specified | 0.6 dB | Formula: SNR + TT
T-put limit unchanged | +| 8.3.1 Performance requirements for PUCCH format 0 | SNRs as specified | 0.6 dB | Formula: SNR + TT
False ACK limit unchanged
Correct ACK limit unchanged | + +| | | | | +|------------------------------------------------------------------------|-------------------|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| 8.3.2 Performance requirements for PUCCH format 1 | SNRs as specified | 0.6 dB | Formula: SNR + TT
False ACK limit unchanged
False NACK limit unchanged
Correct ACK limit unchanged | +| 8.3.3 Performance requirements for PUCCH format 2 | SNRs as specified | 0.6 dB | Formula: SNR + TT
False ACK limit unchanged
Correct ACK limit unchanged
UCI BLER limit unchanged | +| 8.3.4 Performance requirements for PUCCH format 3 | SNRs as specified | 0.6 dB | Formula: SNR + TT
UCI BLER limit unchanged | +| 8.3.5 Performance requirements for PUCCH format 4 | SNRs as specified | 0.6 dB | Formula: SNR + TT
UCI BLER limit unchanged | +| 8.3.6 Performance requirements for multi-slot PUCCH | SNRs as specified | 0.6 dB | Formula: SNR + TT
False ACK limit unchanged
False NACK limit unchanged
Correct ACK limit unchanged | +| 8.3.12 Performance requirements for PUCCH format 1 with DM-RS bundling | SNRs as specified | 0.6 dB | Formula: SNR + TT
False ACK limit unchanged
False NACK limit unchanged
Correct ACK limit unchanged
UCI BLER limit unchanged | +| 8.3.13 Performance requirements for PUCCH format 3 with DM-RS bundling | SNRs as specified | 0.6 dB | Formula: SNR + TT
UCI BLER limit unchanged | +| 8.4.1 PRACH false alarm probability and missed detection | SNRs as specified | 0.6 dB for fading cases
0.3 dB for AWGN cases | Formula: SNR + TT
PRACH false detection limit unchanged
PRACH detection limit unchanged | + +## Annex D (informative): Measurement system set-up + +### D.1 BS type 1-C transmitter + +#### D.1.1 Base station output power, output power dynamics, transmitter ON/OFF power, frequency error, EVM, unwanted emissions for BS type 1-C + +![Block diagram of the measuring system set-up for BS type 1-C output power, output power dynamics, frequency error, EVM, unwanted emissions. A box labeled 'BS under TX test' has a 'TX' output connected to a box labeled 'Measurement equipment'.](d7a98a717edbc26ca1508aaab7a566f4_img.jpg) + +``` +graph LR; A[BS under TX test] -- TX --> B[Measurement equipment] +``` + +Block diagram of the measuring system set-up for BS type 1-C output power, output power dynamics, frequency error, EVM, unwanted emissions. A box labeled 'BS under TX test' has a 'TX' output connected to a box labeled 'Measurement equipment'. + +Figure D.1.1-1: Measuring system set-up for BS type 1-C output power, output power dynamics, frequency error, EVM, unwanted emissions + +#### D.1.2 Transmitter intermodulation for BS type 1-C + +![Block diagram of the measuring system set-up for BS type 1-C transmitter intermodulation. A 'Signal Generator for the NR Modulated signal' is connected to an 'ATT1' block, which is connected to a circulator. The circulator is also connected to a 'BS Under Tx test' block (labeled 'RX/TX or TX') and a 'Spectrum analyser'.](6656b8a5dfd7e3f7f7f0316de0481f1b_img.jpg) + +``` +graph LR; A[Signal Generator for the NR Modulated signal] --> B[ATT1]; B --> C((Circulator)); C --> D[BS Under Tx test
RX/TX or TX]; C --> E[Spectrum analyser] +``` + +Block diagram of the measuring system set-up for BS type 1-C transmitter intermodulation. A 'Signal Generator for the NR Modulated signal' is connected to an 'ATT1' block, which is connected to a circulator. The circulator is also connected to a 'BS Under Tx test' block (labeled 'RX/TX or TX') and a 'Spectrum analyser'. + +Figure D.1.2-1: Measuring system set-up for BS type 1-C transmitter intermodulation + +### D.1.3 Time alignment error for BS type 1-C + +![Diagram of the measuring system set-up for BS type 1-C test of time alignment error.](87661c01f79c13b3ea49e7d3e9782c48_img.jpg) + +The diagram shows a 'BS under TAE test' on the left. It has four output lines: TX #1, TX #2, TX #3, and TX #4. TX #1 and TX #2 are connected to a 'Measurement equipment:' box on the right, which contains 'Timing difference measurement'. TX #3 and TX #4 are connected to two separate 'Load' boxes. + +Diagram of the measuring system set-up for BS type 1-C test of time alignment error. + +Figure D.1.3-1: Measuring system set-up for BS type 1-C test of time alignment error + +## D.2 BS type 1-C receiver + +### D.2.1 Reference sensitivity level for BS type 1-C + +![Diagram of the measuring system set-up for BS type 1-C reference sensitivity level test.](50391d55e6cee28152373f50742e9b9b_img.jpg) + +The diagram shows an 'RF signal source' on the left with an 'RF out' connected to a 'BS under RX Test' box on the right. Inside the 'BS under RX Test' box, the signal is received by 'RX1 or RX1/TX'. The 'RX2' output of the box is connected to a 'Termination (If needed)' box at the bottom. + +Diagram of the measuring system set-up for BS type 1-C reference sensitivity level test. + +Figure D.2.1-1: Measuring system set-up for BS type 1-C reference sensitivity level test + +## D.2.2 Dynamic range for BS type 1-C + +![Block diagram of the measuring system set-up for BS type 1-C dynamic range. It shows two signal generators on the left connected to a Hybrid. The top generator is for the wanted signal, and the bottom is for the AWGN interfering signal. The Hybrid has two outputs: one connected to the BS under RX test (with RX1 and RX2) and the other connected to a Termination (if needed).](e7511e4fa0a0df6c02eb793c62524690_img.jpg) + +``` +graph LR; A[Signal generator for the wanted signal] --> H[Hybrid]; B[Signal generator for the AWGN interfering signal] --> H; H --> BS[BS under RX test
RX1
RX2]; H --> T[Termination
(if needed)]; +``` + +Block diagram of the measuring system set-up for BS type 1-C dynamic range. It shows two signal generators on the left connected to a Hybrid. The top generator is for the wanted signal, and the bottom is for the AWGN interfering signal. The Hybrid has two outputs: one connected to the BS under RX test (with RX1 and RX2) and the other connected to a Termination (if needed). + +Figure D.2.2-1: Measuring system set-up for BS type 1-C dynamic range + +## D.2.3 In-channel selectivity for BS type 1-C + +![Block diagram of the measuring system set-up for BS type 1-C in-channel selectivity. It shows a single signal generator on the left connected to a Hybrid. The generator is for the wanted signal and NR interfering signal. The Hybrid has two outputs: one connected to the BS under RX test (with RX1 and RX2) and the other connected to a Termination (if needed).](e70285b7d75f2ab0c351640618082c0d_img.jpg) + +``` +graph LR; A[Signal generator for the wanted signal and
NR interfering signal] --> H[Hybrid]; H --> BS[BS under RX test
RX1
RX2]; H --> T[Termination
(if needed)]; +``` + +Block diagram of the measuring system set-up for BS type 1-C in-channel selectivity. It shows a single signal generator on the left connected to a Hybrid. The generator is for the wanted signal and NR interfering signal. The Hybrid has two outputs: one connected to the BS under RX test (with RX1 and RX2) and the other connected to a Termination (if needed). + +Figure D.2.3-1: Measuring system Set-up for BS type 1-C in-channel selectivity + +## D.2.4 Adjacent Channel Selectivity (ACS) and narrowband blocking for BS type 1-C + +![Block diagram of the measuring system set-up for BS type 1-C ACS and narrowband blocking. It shows two signal generators (wanted and interfering) connected through attenuators (ATT1, ATT2) to a hybrid coupler. The hybrid's output is connected to the RX1 port of the BS under test, while the RX2 port is connected to a termination.](888ca03f14a7d40e9cf34ed55778a679_img.jpg) + +The diagram illustrates the test setup for Adjacent Channel Selectivity (ACS) and narrowband blocking. On the left, two signal generators are shown: 'Signal Generator for the wanted signal' and 'Signal Generator for the interfering signal'. The wanted signal path includes an attenuator labeled 'ATT1', and the interfering signal path includes an attenuator labeled 'ATT2'. Both attenuators connect to a 'HYBRID' coupler. The output of the hybrid coupler is connected to the 'RX1' port of the 'BS Under RX Test'. The 'RX2' port of the BS is connected to a 'TERMINATION' block. + +Block diagram of the measuring system set-up for BS type 1-C ACS and narrowband blocking. It shows two signal generators (wanted and interfering) connected through attenuators (ATT1, ATT2) to a hybrid coupler. The hybrid's output is connected to the RX1 port of the BS under test, while the RX2 port is connected to a termination. + +Figure D.2.4-1: Measuring system set-up for BS type 1-C adjacent channel selectivity and narrowband blocking + +## D.2.5 Blocking characteristics for BS type 1-C + +![Block diagram of the measuring system set-up for BS type 1-C blocking characteristics. It shows two signal generators (wanted and interfering) connected through attenuators (ATT1, ATT2) to a hybrid coupler. The hybrid's output is connected to a circulator, which is also connected to a termination and the RX1/TX port of the BS under test. The RX2 port of the BS is also connected to a termination.](eec8a7a6584d308ede104bddbf4dc7f3_img.jpg) + +The diagram illustrates the test setup for blocking characteristics. On the left, two signal generators are shown: 'Signal Generator for the wanted signal' and 'Signal Generator for the interfering signal'. The wanted signal path includes an attenuator labeled 'ATT1', and the interfering signal path includes an attenuator labeled 'ATT2'. Both attenuators connect to a 'HYBRID' coupler. The output of the hybrid coupler is connected to a circulator. One input of the circulator is connected to a 'Termination' block, and its output is connected to the 'RX1/TX' port of the 'BS under RX Test'. The 'RX2' port of the BS is also connected to a 'Termination' block. + +Block diagram of the measuring system set-up for BS type 1-C blocking characteristics. It shows two signal generators (wanted and interfering) connected through attenuators (ATT1, ATT2) to a hybrid coupler. The hybrid's output is connected to a circulator, which is also connected to a termination and the RX1/TX port of the BS under test. The RX2 port of the BS is also connected to a termination. + +Figure D.2.5-1: Measuring system set-up for BS type 1-C blocking characteristics + +## D.2.6 Receiver spurious emission for BS type 1-C + +![Block diagram of the measuring system set-up for BS type 1-C receiver spurious emission. A 'BS under RX Test' block has three ports: TX, RX1, and RX2. The TX port is connected to two 'Termination' blocks. The RX1 port is connected to a 'Termination' block. The RX2 port is connected to a 'TX notch' block, which is then connected to a 'Measurement receiver' block.](9f2de980bdf4633bdf738b33d2ed8ff1_img.jpg) + +Block diagram of the measuring system set-up for BS type 1-C receiver spurious emission. A 'BS under RX Test' block has three ports: TX, RX1, and RX2. The TX port is connected to two 'Termination' blocks. The RX1 port is connected to a 'Termination' block. The RX2 port is connected to a 'TX notch' block, which is then connected to a 'Measurement receiver' block. + +Figure D.2.6-1: Measuring system set-up for BS type 1-C receiver spurious emission + +## D.2.7 Intermodulation characteristics for BS type 1-C + +![Block diagram of the measuring system set-up for BS type 1-C intermodulation characteristics. 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'. The wanted signal goes through 'ATT1' to a 'Hybrid' block. The CW interfering signal goes through 'ATT2' to another 'Hybrid' block. The modulated interfering signal goes through 'ATT3' to the second 'Hybrid' block. The output of the first 'Hybrid' block is connected to the RX1 port of the 'BS under test' block. The output of the second 'Hybrid' block is connected to the RX2 port of the 'BS under test' block. A 'Termination' block is connected to the RX2 port of the 'BS under test' block.](b5051df103b6f1292dae89e60d9a4790_img.jpg) + +Block diagram of the measuring system set-up for BS type 1-C intermodulation characteristics. 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'. The wanted signal goes through 'ATT1' to a 'Hybrid' block. The CW interfering signal goes through 'ATT2' to another 'Hybrid' block. The modulated interfering signal goes through 'ATT3' to the second 'Hybrid' block. The output of the first 'Hybrid' block is connected to the RX1 port of the 'BS under test' block. The output of the second 'Hybrid' block is connected to the RX2 port of the 'BS under test' block. A 'Termination' block is connected to the RX2 port of the 'BS under test' block. + +Figure D.2.7-1: Measuring system set-up for BS type 1-C intermodulation characteristics + +## D.3 BS type 1-H transmitter + +### D.3.1 Base station output power, output power dynamics, transmitter ON/OFF power, frequency error, EVM, unwanted emissions for BS type 1-H + +*TAB connectors* may be connected to the measurement equipment singularly and tested one at a time (figure D.3.1-1), or may be tested simultaneously in groups (figure D.3.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 BS type 1-H output power, output power dynamics, transmitter ON/OFF power, frequency error, EVM, unwanted emissions for a single TAB connector.](4b4b9c9c016880edb872f25cefc85eb1_img.jpg) + +The diagram illustrates the measuring system set-up 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'. Along this boundary, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a box labeled 'Measurement equipment'. Connectors #2 and #K are each connected to a box labeled 'Load'. Vertical ellipses between #2 and #K indicate additional connectors. An arrow points from the text 'Transceiver array boundary connector TAB(n)' to connector #K. + +Diagram of the measuring system set-up for BS type 1-H output power, output power dynamics, transmitter ON/OFF power, frequency error, EVM, unwanted emissions for a single TAB connector. + +**Figure D.3.1-1: Measuring system set-up for BS type 1-H output power, output power dynamics, transmitter ON/OFF power, frequency error, EVM, unwanted emissions for a single *TAB connector*** + +![Figure D.3.1-2: Measuring system set-up for BS type 1-H output power, output power dynamics, transmitter ON/OFF power, frequency error, EVM, unwanted emissions for multiple TAB connectors. The diagram shows a dashed box labeled 'transceiver unit array' on the left. A vertical dashed line labeled 'transceiver array boundary' separates it from the right side. Multiple horizontal lines, labeled #1, #2, ..., #K, pass from the array through the boundary to a box labeled 'Measurement Equipment'. Each line has a small square connector at the boundary. An arrow points to one of these connectors with the label 'Transceiver array boundary connector TAB(n)'.](9e23e88f57c8d963f343c29619ebdbf2_img.jpg) + +Figure D.3.1-2: Measuring system set-up for BS type 1-H output power, output power dynamics, transmitter ON/OFF power, frequency error, EVM, unwanted emissions for multiple TAB connectors. The diagram shows a dashed box labeled 'transceiver unit array' on the left. A vertical dashed line labeled 'transceiver array boundary' separates it from the right side. Multiple horizontal lines, labeled #1, #2, ..., #K, pass from the array through the boundary to a box labeled 'Measurement Equipment'. Each line has a small square connector at the boundary. An arrow points to one of these connectors with the label 'Transceiver array boundary connector TAB(n)'. + +**Figure D.3.1-2: Measuring system set-up for BS type 1-H output power, output power dynamics, transmitter ON/OFF power, frequency error, EVM, unwanted emissions for multiple *TAB connectors*** + +### D.3.2 Transmitter intermodulation for BS type 1-H + +![Figure D.3.2-1: Measuring system set-up for BS type 1-H transmitter intermodulation. The diagram shows a dashed box on the left representing the transceiver array. A vertical dashed line labeled 'Transceiver Array Boundary (TAB)' separates it from the test equipment. Inside the array, multiple horizontal lines are labeled #1, #2, ..., #n, ..., #N_TABC. Lines #1 and #N_TABC terminate in 'Load' blocks. Line #n is labeled 'Wanted signal' and points to a circulator. Another signal, 'Interferring signal', also enters the circulator. The circulator's output goes to a 'Spectrum analyser'. A 'Test signal' block is connected to an 'Att' (attenuator), which is connected to the circulator. An arrow points to the circulator with the label 'TAB connector under test'. Another arrow points to the boundary line with the label 'TAB connector'.](49fafbd71e0dd98b8cf7b2db58559f01_img.jpg) + +Figure D.3.2-1: Measuring system set-up for BS type 1-H transmitter intermodulation. The diagram shows a dashed box on the left representing the transceiver array. A vertical dashed line labeled 'Transceiver Array Boundary (TAB)' separates it from the test equipment. Inside the array, multiple horizontal lines are labeled #1, #2, ..., #n, ..., #N\_TABC. Lines #1 and #N\_TABC terminate in 'Load' blocks. Line #n is labeled 'Wanted signal' and points to a circulator. Another signal, 'Interferring signal', also enters the circulator. The circulator's output goes to a 'Spectrum analyser'. A 'Test signal' block is connected to an 'Att' (attenuator), which is connected to the circulator. An arrow points to the circulator with the label 'TAB connector under test'. Another arrow points to the boundary line with the label 'TAB connector'. + +**Figure D.3.2-1: Measuring system set-up for BS type 1-H transmitter intermodulation** + +### D.3.3 Transmitter spurious emissions for BS type 1-H + +*TAB connectors* may be connected to the measurement equipment singularly and tested one at a time (figure D.3.3-1), or may be tested simultaneously in groups (figure D.3.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. A dashed box on the left represents the 'Transceiver unit array'. A vertical dashed line represents the 'Transceiver array boundary'. To the right of the boundary, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'TX notch' block, which is then connected to 'Measurement equipment'. Connectors #2 and #K are connected to 'Load' blocks. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'.](6de875eb7a49c3352b45075b92e5ea9b_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. A dashed box on the left represents the 'Transceiver unit array'. A vertical dashed line represents the 'Transceiver array boundary'. To the right of the boundary, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a 'TX notch' block, which is then connected to 'Measurement equipment'. Connectors #2 and #K are connected to 'Load' blocks. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'. + +**Figure D.3.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. A dashed box on the left represents the 'Transceiver unit array'. A vertical dashed line represents the 'Transceiver array boundary'. To the right of the boundary, there are multiple connectors labeled #1, #2, ..., #K. Each connector is connected to its own 'TX notch' block. All 'TX notch' blocks are connected to a single 'Measurement equipment' block. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'.](0cbb609996cfd29997216c8f50dceee7_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. A dashed box on the left represents the 'Transceiver unit array'. A vertical dashed line represents the 'Transceiver array boundary'. To the right of the boundary, there are multiple connectors labeled #1, #2, ..., #K. Each connector is connected to its own 'TX notch' block. All 'TX notch' blocks are connected to a single 'Measurement equipment' block. An arrow points to the boundary line with the label 'Transceiver array boundary connector TAB(n)'. + +**Figure D.3.3-2: Measuring system set-up for transmitter spurious emissions for multiple *TAB connectors* in parallel test** + +### D.3.4 Time alignment error for BS type 1-H + +![Diagram of measuring system set-up for BS type 1-H test of time alignment error. It shows a 'Transceiver unit array' on the left and a 'Transceiver array boundary' indicated by a dashed vertical line. At the boundary, there are multiple connectors labeled #1, #2, #3, ..., #K. Connector #1 and #2 are connected to 'Measurement equipment: Timing difference measurement'. Connector #3 and #K are connected to 'Load' blocks. An arrow points to the boundary line labeled 'Transceiver array boundary connector TAB(n)'.](f6dcf82b673244b5b8c95616ca0d0556_img.jpg) + +Diagram of measuring system set-up for BS type 1-H test of time alignment error. It shows a 'Transceiver unit array' on the left and a 'Transceiver array boundary' indicated by a dashed vertical line. At the boundary, there are multiple connectors labeled #1, #2, #3, ..., #K. Connector #1 and #2 are connected to 'Measurement equipment: Timing difference measurement'. Connector #3 and #K are connected to 'Load' blocks. An arrow points to the boundary line labeled 'Transceiver array boundary connector TAB(n)'. + +Figure D.3.4-1: Measuring system set-up for BS type 1-H test of time alignment error + +## D.4 BS type 1-H receiver + +### D.4.1 Reference sensitivity level for BS type 1-H + +![Diagram of measuring system set-up for BS type 1-H reference sensitivity level test. It shows a 'transceiver unit array' on the left and a 'transceiver array boundary' indicated by a dashed vertical line. At the boundary, there are multiple connectors labeled #1, #2, #3, ..., #K. Connector #1 is connected to a 'Signal generator for the wanted signal'. Connector #2 and #K are connected to 'Load' blocks. An arrow points to the boundary line labeled 'Transceiver array boundary connector TAB(n)'.](d4a2b8bf6c326b6d627c2a051d13f728_img.jpg) + +Diagram of measuring system set-up for BS type 1-H reference sensitivity level test. It shows a 'transceiver unit array' on the left and a 'transceiver array boundary' indicated by a dashed vertical line. At the boundary, there are multiple connectors labeled #1, #2, #3, ..., #K. Connector #1 is connected to a 'Signal generator for the wanted signal'. Connector #2 and #K are connected to 'Load' blocks. An arrow points to the boundary line labeled 'Transceiver array boundary connector TAB(n)'. + +Figure D.4.1-1: Measuring system set-up for BS type 1-H reference sensitivity level test + +## D.4.2 Receiver dynamic range for BS type 1-H + +![Figure D.4.2-1: Measuring system set-up for BS type 1-H dynamic range test. The diagram shows a 'transceiver unit array' (dashed box) connected to a 'transceiver array boundary' (dashed vertical line). 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. 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 with the label 'Transceiver array boundary connector TAB(n)'.](df11b35ddcfb1f54dc4e92fb39797ac8_img.jpg) + +Figure D.4.2-1: Measuring system set-up for BS type 1-H dynamic range test. The diagram shows a 'transceiver unit array' (dashed box) connected to a 'transceiver array boundary' (dashed vertical line). 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. 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 with the label 'Transceiver array boundary connector TAB(n)'. + +Figure D.4.2-1: Measuring system set-up for *BS type 1-H* dynamic range test + +## D.4.3 Receiver adjacent channel selectivity and narrowband blocking for BS type 1-H + +![Figure D.4.3-1: Measuring system set-up for BS type 1-H adjacent channel selectivity and narrowband blocking test. The diagram is similar to Figure D.4.2-1 but includes two attenuators, 'ATT1' and 'ATT2'. The 'Signal generator for the wanted signal' is connected to 'ATT1', which is then connected to the 'Hybrid' block. The 'Signal generator for the interfering signal' is connected to 'ATT2', which is then connected to the 'Hybrid' block. All other components and connections remain the same as in Figure D.4.2-1.](f9dc060faad1fb842976b395498accd7_img.jpg) + +Figure D.4.3-1: Measuring system set-up for BS type 1-H adjacent channel selectivity and narrowband blocking test. The diagram is similar to Figure D.4.2-1 but includes two attenuators, 'ATT1' and 'ATT2'. The 'Signal generator for the wanted signal' is connected to 'ATT1', which is then connected to the 'Hybrid' block. The 'Signal generator for the interfering signal' is connected to 'ATT2', which is then connected to the 'Hybrid' block. All other components and connections remain the same as in Figure D.4.2-1. + +Figure D.4.3-1: Measuring system set-up for *BS type 1-H* adjacent channel selectivity and narrowband blocking test + +## D.4.4 Receiver spurious emissions + +*TAB connector(s)* may be connected to the measurement equipment singularly and tested one at a time (figure D.4.2-1), or may be tested simultaneously in groups (figure D.4.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 BS type 1-H receiver spurious emissions for a single TAB connector. A dashed box on the left is labeled 'transceiver unit array'. A vertical dashed line to its right is labeled 'transceiver array boundary'. Below this line is an arrow pointing to a connector labeled 'Transceiver array boundary connector TAB(n)'. Inside the array, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a block labeled 'TX notch', which is then connected to a block labeled 'Measurement receiver'. Connectors #2 and #K are each connected to a block labeled 'Load'. Vertical ellipsis dots are shown between connectors #2 and #K.](689d331d83fef38df69d4bb17c7ace6d_img.jpg) + +Diagram of measuring system set-up for BS type 1-H receiver spurious emissions for a single TAB connector. A dashed box on the left is labeled 'transceiver unit array'. A vertical dashed line to its right is labeled 'transceiver array boundary'. Below this line is an arrow pointing to a connector labeled 'Transceiver array boundary connector TAB(n)'. Inside the array, there are multiple connectors labeled #1, #2, ..., #K. Connector #1 is connected to a block labeled 'TX notch', which is then connected to a block labeled 'Measurement receiver'. Connectors #2 and #K are each connected to a block labeled 'Load'. Vertical ellipsis dots are shown between connectors #2 and #K. + +**Figure D.4.4-1: Measuring system set-up for BS type 1-H receiver spurious emissions for a single TAB connector** + +![Diagram of measuring system set-up for BS type 1-H receiver spurious emissions for multiple TAB connectors. A dashed box on the left is labeled 'transceiver unit array'. A vertical dashed line to its right is labeled 'transceiver array boundary'. Below this line is an arrow pointing to a connector labeled 'Transceiver array boundary connector TAB(n)'. Inside the array, there are multiple connectors labeled #1, #2, ..., #K. Each of these connectors is connected to a block labeled 'TX'. All 'TX' blocks are connected to a single large block on the right labeled 'Measurement receiver(s)'. Vertical ellipsis dots are shown between connectors #2 and #K.](94e473ccc93bae938bf71dacb5e4727d_img.jpg) + +Diagram of measuring system set-up for BS type 1-H receiver spurious emissions for multiple TAB connectors. A dashed box on the left is labeled 'transceiver unit array'. A vertical dashed line to its right is labeled 'transceiver array boundary'. Below this line is an arrow pointing to a connector labeled 'Transceiver array boundary connector TAB(n)'. Inside the array, there are multiple connectors labeled #1, #2, ..., #K. Each of these connectors is connected to a block labeled 'TX'. All 'TX' blocks are connected to a single large block on the right labeled 'Measurement receiver(s)'. Vertical ellipsis dots are shown between connectors #2 and #K. + +**Figure D.4.4-2: Measuring system set-up for BS type 1-H receiver spurious emissions for multiple TAB connectors** + +## D.4.5 Receiver In-channel selectivity for BS type 1-H + +![Diagram of the measuring system set-up for BS type 1-H in-channel selectivity test.](9c79df43d06f2243e8e0bb02eda0cdf6_img.jpg) + +The diagram illustrates the measuring system set-up for BS type 1-H in-channel selectivity test. On the left, a dashed rectangle labeled "transceiver unit array" contains multiple ports. A vertical dashed line labeled "transceiver array boundary" separates the array from the external test equipment. To the right of this boundary, the first port is labeled "#1" and is connected to a block labeled "Hybrid". The second port is labeled "#2" and is connected to a block labeled "Load". Vertical ellipsis dots indicate additional ports between #2 and #K. The K-th port is labeled "#K" and is also connected to a block labeled "Load". An arrow points from the bottom of the diagram towards the "#K" port. The "Hybrid" block is connected to a block labeled "Signal generator for the wanted signal and interfering signal". + +Diagram of the measuring system set-up for BS type 1-H in-channel selectivity test. + +**Figure D.4.5-1: Measuring system set-up for BS type 1-H in-channel selectivity test** + +## D.4.6 Receiver intermodulation for BS type 1-H + +![Diagram of measuring system set-up for BS type 1-H receiver intermodulation test. It shows a transceiver unit array connected via connectors #1, #2, and #K to a transceiver array boundary. At the boundary, connector #1 leads to a Hybrid, #2 leads to a Load, and #K leads to another Load. The Hybrid from #1 is connected to ATT1, which is connected to a 'Signal generator for the wanted signal'. The Hybrid from #1 also connects to another Hybrid, which is connected to ATT2 (connected to 'Signal generator for the CW interfering signal') and ATT3 (connected to 'Signal generator for the NR interfering signal').](fe958e930d35081b9a5616ebc6780d65_img.jpg) + +Diagram of measuring system set-up for BS type 1-H receiver intermodulation test. It shows a transceiver unit array connected via connectors #1, #2, and #K to a transceiver array boundary. At the boundary, connector #1 leads to a Hybrid, #2 leads to a Load, and #K leads to another Load. The Hybrid from #1 is connected to ATT1, which is connected to a 'Signal generator for the wanted signal'. The Hybrid from #1 also connects to another Hybrid, which is connected to ATT2 (connected to 'Signal generator for the CW interfering signal') and ATT3 (connected to 'Signal generator for the NR interfering signal'). + +Figure D.4.6-1: Measuring system set-up for BS type 1-H receiver intermodulation test + +## D.5 BS type 1-C performance requirements + +### D.5.1 Performance requirements for PUSCH, single user PUCCH, PRACH on single antenna port in multipath fading conditions and for high speed condition + +![Functional set-up for performance requirements for PUSCH, single user PUCCH, PRACH on single antenna port in multipath fading conditions and for High Speed Train conditions for BS with Rx diversity (2 Rx case shown). A BS tester is connected to a splitter. One output of the splitter goes to a Channel Simulator, which is then connected to RX A of the Base Station under test. The other output of the splitter goes to another Channel Simulator, which is connected to RX B of the Base Station under test. Both RX A and RX B are also connected to an AWGN Generator. A HARQ Feedback (only for PUSCH) line is shown from the Base Station under test back to the BS tester.](fa534498004572deb292e53e11c13a3c_img.jpg) + +Functional set-up for performance requirements for PUSCH, single user PUCCH, PRACH on single antenna port in multipath fading conditions and for High Speed Train conditions for BS with Rx diversity (2 Rx case shown). A BS tester is connected to a splitter. One output of the splitter goes to a Channel Simulator, which is then connected to RX A of the Base Station under test. The other output of the splitter goes to another Channel Simulator, which is connected to RX B of the Base Station under test. Both RX A and RX B are also connected to an AWGN Generator. A HARQ Feedback (only for PUSCH) line is shown from the Base Station under test back to the BS tester. + +Figure D.5.1-1: Functional set-up for performance requirements for PUSCH, single user PUCCH, PRACH on single antenna port in multipath fading conditions and for High Speed Train conditions for BS with Rx diversity (2 Rx case shown) + +NOTE 1: For HST tests which are specified in static conditions, the Channel Simulators are assumed to simulate the Doppler shift. + +NOTE 2: The HARQ Feedback could be done as an RF feedback or as a digital feedback. The HARQ Feedback should be error free. + +### D.5.2 Performance requirements for PUSCH transmission on two antenna ports in multipath fading conditions + +![Functional set-up for performance requirements for PUSCH transmission on two antenna ports in multipath fading conditions (2 Rx case shown).](5be0a1a31ceab44c46b7f4ff2b369c9e_img.jpg) + +The diagram illustrates a functional test setup for PUSCH transmission. On the left, a 'BS Tester' has two transmit ports, 'TX A' and 'TX B'. Each port is connected to a directional coupler. The forward path from each coupler leads to a 'Channel Simulator' block. There are four 'Channel Simulator' blocks in total. The outputs of these simulators are then connected to another set of directional couplers. The forward path from these couplers leads to the 'BS Station Under test', which has two receive ports, 'RX A' and 'RX B'. Additionally, there are two 'AWGN Generator' blocks. The outputs of the AWGN generators are combined and fed into the receive path of the BS Station Under test. A 'HARQ Feedback' line is shown, originating from the bottom of the BS Station Under test and returning to the BS Tester. + +Functional set-up for performance requirements for PUSCH transmission on two antenna ports in multipath fading conditions (2 Rx case shown). + +Figure D.5.2-1: Functional set-up for performance requirements for PUSCH transmission on two antenna ports in multipath fading conditions (2 Rx case shown) + +### D.5.3 Performance requirements for PUSCH and PRACH in static conditions + +![Functional set-up for performance requirements for PUSCH and PRACH in static conditions for BS with Rx diversity (2 Rx case shown).](09b3589ff2a5c24911954d02059cb9b4_img.jpg) + +The diagram illustrates a functional test setup for PUSCH and PRACH in static conditions. On the left, a 'BS tester' is connected to a directional coupler. The forward path from the coupler leads to the 'Base Station under test', which has two receive ports, 'RX A' and 'RX B'. The outputs from the receive ports are combined and fed into two 'AWGN Generator' blocks. The diagram shows the Base Station under test with receive diversity using two antennas (RX A and RX B). + +Functional set-up for performance requirements for PUSCH and PRACH in static conditions for BS with Rx diversity (2 Rx case shown). + +Figure D.5.3-1: Functional set-up for performance requirements for PUSCH and PRACH in static conditions for BS with Rx diversity (2 Rx case shown) + +## D.5.4 Performance requirements for UL timing adjustment + +![Functional set-up for performance requirement for UL timing adjustment (Scenario Y case shown).](4405b71aa114882a0a9a7ef6dafa6da7_img.jpg) + +The diagram illustrates a functional set-up for UL timing adjustment. On the left, a 'BS tester' contains two dashed boxes: 'Stationary UE' and 'Moving UE'. Each UE is connected to a directional coupler (represented by a square with an 'X'). The outputs of these couplers are connected to a 'BS under test' on the right. The 'BS under test' has two receivers, 'Rx A' and 'Rx B'. The output of the 'Stationary UE' coupler is connected to 'Rx A' via another directional coupler. The output of the 'Moving UE' coupler is connected to 'Rx B' via another directional coupler. Below the 'BS under test', there are two 'AWGN generator' blocks. The outputs of these generators are connected to the 'HARQ feedback + TA commands' line, which is then connected back to the 'Moving UE' in the 'BS tester'. + +Functional set-up for performance requirement for UL timing adjustment (Scenario Y case shown). + +**Figure D.5.4-1: Functional set-up for performance requirement for UL timing adjustment (Scenario Y case shown)** + +NOTE: The HARQ feedback and TA commands could be done as an RF feedback or as a digital feedback. The HARQ feedback and TA commands should be error free. + +## D.6 BS type 1-H performance requirements + +### D.6.1 Performance requirements for PUSCH, single user PUCCH, PRACH on single antenna port in multipath fading conditions and for high speed condition + +![Functional set-up for performance requirements for PUSCH, single user PUCCH, PRACH on single antenna port in multipath fading conditions and for High Speed Train conditions for BS with Rx diversity (2 Rx case shown).](eb39abb910e46289d79b0f4ae52fc612_img.jpg) + +The diagram illustrates the functional set-up for performance requirements. On the left, a dashed box labeled 'transceiver unit array' contains multiple antenna ports labeled #1, #2, ..., #K. A vertical dashed line labeled 'transceiver array boundary' separates the unit array from the external test equipment. To the right of the boundary, each antenna port is connected to a circulator. The first two ports (#1 and #2) are connected to a 'Channel Simulator' and an 'AWGN Generator'. The K-th port (#K) is connected to a 'Load'. All circulators are connected to a common 'BS tester'. A feedback line labeled 'HARQ feedback (only for PUSCH)' is shown between the BS tester and the transceiver unit array. A label 'Transceiver array boundary connector TAB(n)' points to the boundary line. + +Functional set-up for performance requirements for PUSCH, single user PUCCH, PRACH on single antenna port in multipath fading conditions and for High Speed Train conditions for BS with Rx diversity (2 Rx case shown). + +**Figure D.6.1-1: Functional set-up for performance requirements for PUSCH, single user PUCCH, PRACH on single antenna port in multipath fading conditions and for High Speed Train conditions for BS with Rx diversity (2 Rx case shown)** + +NOTE 1: For HST tests which are specified in static conditions, the Channel Simulators are assumed to simulate the Doppler shift. + +NOTE 2: The HARQ Feedback could be done as an RF feedback or as a digital feedback. The HARQ Feedback should be error free. + +## D.6.2 Performance requirements for PUSCH transmission on two antenna ports in multipath fading conditions + +![Functional set-up for performance requirements for PUSCH transmission on two antenna ports in multipath fading conditions (2 Rx case shown).](d3b965960ca88db8118f308a5be4cb75_img.jpg) + +The diagram illustrates the functional set-up for performance requirements for PUSCH transmission on two antenna ports in multipath fading conditions. A dashed box on the left represents the 'transceiver unit array'. Inside this array, there are multiple ports labeled #1, #2, ..., #K. Port #K is connected to a 'Load' block. A vertical dashed line labeled 'transceiver array boundary' separates the array from the external components. To the right of this boundary, each port (#1, #2, ..., #K) is connected to a directional coupler. The forward path of each coupler leads to a 'Channel Simulator' block. There are four 'Channel Simulator' blocks in total. The outputs of these simulators are connected to two 'Tx' (Transmitter) blocks, labeled 'Tx 1' and 'Tx 2'. Additionally, there are two 'AWGN Generator' blocks connected to the 'Tx 1' and 'Tx 2' blocks. A 'BS tester' block is connected to the 'Tx 1' and 'Tx 2' blocks. A line labeled 'HARQ feedback' connects the 'BS tester' back to the 'transceiver unit array'. A label 'Transceiver array boundary connector TAB(n)' points to the boundary between the array and the external components. + +Functional set-up for performance requirements for PUSCH transmission on two antenna ports in multipath fading conditions (2 Rx case shown). + +Figure D.6.2-1: Functional set-up for performance requirements for PUSCH transmission on two antenna ports in multipath fading conditions (2 Rx case shown) + +## D.6.3 Performance requirements for PUSCH and PRACH in static conditions + +![Functional set-up for performance requirements for PUSCH and PRACH in static conditions for BS with Rx diversity (2 Rx case shown).](6eb451dee00e06ac8710c477f258463d_img.jpg) + +The diagram illustrates the functional set-up for performance requirements for PUSCH and PRACH in static conditions for BS with Rx diversity (2 Rx case shown). A dashed box on the left represents the 'transceiver unit array'. Inside this array, there are multiple ports labeled #1, #2, ..., #K. Port #K is connected to a 'Load' block. A vertical dashed line labeled 'transceiver array boundary' separates the array from the external components. To the right of this boundary, each port (#1, #2, ..., #K) is connected to a directional coupler. The forward path of each coupler leads to an 'AWGN Generator' block. There are two 'AWGN Generator' blocks in total. The outputs of these generators are connected to a 'BS tester' block. A label 'Transceiver array boundary connector TAB(n)' points to the boundary between the array and the external components. + +Functional set-up for performance requirements for PUSCH and PRACH in static conditions for BS with Rx diversity (2 Rx case shown). + +Figure D.6.3-1: Functional set-up for performance requirements for PUSCH and PRACH in static conditions for BS with Rx diversity (2 Rx case shown) + +## D.6.4 Performance requirements for UL timing adjustment + +![Functional set-up for performance requirement for UL timing adjustment (Scenario Y case shown)](f288907445f0de048c603b6980c3db58_img.jpg) + +The diagram illustrates the functional set-up for performance requirements for UL timing adjustment. On the left, a dashed box labeled 'transceiver unit array' contains multiple transceivers, with the first labeled '#1', the second '#2', and the K-th labeled '#K'. A vertical dashed line to the right of the array is labeled 'transceiver array boundary'. Each transceiver connects to a circulator at the boundary. The first two circulators are connected to 'AWGN Generator' blocks. The K-th circulator is connected to a 'Load' block. All circulators are connected to a common 'BS tester' block on the far right. The 'BS tester' block contains 'Stationary UE' and 'Moving UE' components. A feedback line labeled 'HARQ feedback (only for PUSCH)' originates from the BS tester and points to the K-th transceiver. An arrow labeled 'Transceiver array boundary connector TAB(n)' points to the boundary line between the transceiver unit array and the circulators. + +Functional set-up for performance requirement for UL timing adjustment (Scenario Y case shown) + +**Figure D.6.4-1: Functional set-up for performance requirement for UL timing adjustment (Scenario Y case shown)** + +NOTE: The HARQ feedback and TA commands could be done as an RF feedback or as a digital feedback. The HARQ feedback and TA commands should be error free. + +--- + +## Annex E (normative): + +### Characteristics of interfering signals + +The interfering signal shall be a PUSCH containing data and DMRS symbols. Normal cyclic prefix is used. The data content shall be uncorrelated to the wanted signal and modulated according to clause 6 of TS 38.211 [17]. Mapping of PUSCH modulation to receiver requirement are specified in table E-1. + +**Table E-1: Modulation of the interfering signal** + +| Receiver requirement | Modulation | +|-------------------------------------------------------|------------| +| In-channel selectivity | 16QAM | +| Adjacent channel selectivity and narrow-band blocking | QPSK | +| General blocking | QPSK | +| Receiver intermodulation | QPSK | + +--- + +## Annex F (normative): + +Void + +--- + +## Annex G (normative): Propagation conditions + +--- + +### G.1 Static propagation condition + +The propagation for the static performance measurement is an Additive White Gaussian Noise (AWGN) environment. No fading or multi-paths exist for this propagation model. + +--- + +### G.2 Multi-path fading propagation conditions + +The multipath propagation conditions consist of several parts: + +- A delay profile in the form of a "tapped delay-line", characterized by a number of taps at fixed positions on a sampling grid. The profile can be further characterized by the r.m.s. delay spread and the maximum delay spanned by the taps. +- A combination of channel model parameters that include the Delay profile and the Doppler spectrum that is characterized by a classical spectrum shape and a maximum Doppler frequency. +- Different models are used for FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz – 52.6 GHz). + +#### G.2.1 Delay profiles + +The delay profiles are simplified from the TR 38.901 [20] TDL models. The simplification steps are shown below for information. These steps are only used when new delay profiles are created. Otherwise, the delay profiles specified in G.2.1.1 can be used as such. + +- Step 1: Use the original TDL model from TR 38.901 [20]. +- Step 2: Re-order the taps in ascending delays +- Step 3: Perform delay scaling according to the procedure described in clause 7.7.3 in TR 38.901 [20]. +- Step 4: Apply the quantization to the delay resolution 5 ns. This is done simply by rounding the tap delays to the nearest multiple of the delay resolution. +- Step 5: If multiple taps are rounded to the same delay bin, merge them by calculating their linear power sum. +- Step 6: If there are more than 12 taps in the quantized model, merge the taps as follows + - Find the weakest tap from all taps (both merged and unmerged taps are considered) + - If there are two or more taps having the same value and are the weakest, select the tap with the smallest delay as the weakest tap. + - When the weakest tap is the first delay tap, merge taps as follows + - Update the power of the first delay tap as the linear power sum of the weakest tap and the second delay tap. + - Remove the second delay tap. + +- When the weakest tap is the last delay tap, merge taps as follows + - Update the power of the last delay tap as the linear power sum of the second-to-last tap and the last tap. + - Remove the second-to-last tap. +- Otherwise + - For each side of the weakest tap, identify the neighbour tap that has the smaller delay difference to the weakest tap. + - When the delay difference between the weakest tap and the identified neighbour tap on one side equals the delay difference between the weakest tap and the identified neighbour tap on the other side. + - Select the neighbour tap that is weaker in power for merging. + - Otherwise, select the neighbour tap that has smaller delay difference for merging. + - To merge, the power of the merged tap is the linear sum of the power of the weakest tap and the selected tap. + - When the selected tap is the first tap, the location of the merged tap is the location of the first tap. The weakest tap is removed. + - When the selected tap is the last tap, the location of the merged tap is the location of the last tap. The weakest tap is removed. + - Otherwise, the location of the merged tap is based on the average delay of the weakest tap and selected tap. If the average delay is on the sampling grid, the location of the merged tap is the average delay. Otherwise, the location of the merged tap is rounded towards the direction of the selected tap (e.g. 10 ns & 20 ns → 15 ns, 10 ns & 25 ns → 20 ns, if 25 ns had higher or equal power; 15 ns, if 10 ns had higher power). The weakest tap and the selected tap are removed. +- Repeat step 6 until the final number of taps is 12. +- Step 7: Round the amplitudes of taps to one decimal (e.g. -8.78 dB → -8.8 dB) +- Step 8: If the delay spread has slightly changed due to the tap merge, adjust the final delay spread by increasing or decreasing the power of the last tap so that the delay spread is corrected. +- Step 9: Re-normalize the highest tap to 0 dB. + +Note 1: Some values of the delay profile created by the simplification steps may differ from the values in tables G.2.1.1-2, G.2.1.1-3, and G.2.1.1-4 for the corresponding model. + +Note 2: For Step 5 and Step 6, the power values are expressed in the linear domain using 6 digits of precision. The operations are in the linear domain. + +## G.2.1.1 Delay profiles for FR1 + +The delay profiles for FR1 are selected to be representative of low, medium and high delay spread environment. The resulting model parameters are specified in G.2.1.1-1 and the tapped delay line models are specified in tables G.2.1.1-2 ~ table G.2.1.1-4. + +**Table G.2.1.1-1: Delay profiles for NR channel models** + +| Model | Number of channel taps | Delay spread (r.m.s.) | Maximum excess tap delay (span) | Delay resolution | +|---------|------------------------|-----------------------|---------------------------------|------------------| +| TDLA30 | 12 | 30 ns | 290 ns | 5 ns | +| TDLB100 | 12 | 100 ns | 480 ns | 5 ns | +| TDLC300 | 12 | 300 ns | 2595 ns | 5 ns | + +**Table G.2.1.1-2: TDLA30 (DS = 30 ns)** + +| Tap # | Delay (ns) | Power (dB) | Fading distribution | +|-------|------------|------------|---------------------| +| 1 | 0 | -15.5 | Rayleigh | +| 2 | 10 | 0 | | +| 3 | 15 | -5.1 | | +| 4 | 20 | -5.1 | | +| 5 | 25 | -9.6 | | +| 6 | 50 | -8.2 | | +| 7 | 65 | -13.1 | | +| 8 | 75 | -11.5 | | +| 9 | 105 | -11.0 | | +| 10 | 135 | -16.2 | | +| 11 | 150 | -16.6 | | +| 12 | 290 | -26.2 | | + +**Table G.2.1.1-3: TDLB100 (DS = 100ns)** + +| Tap # | Delay (ns) | Power (dB) | Fading distribution | +|-------|------------|------------|---------------------| +| 1 | 0 | 0 | Rayleigh | +| 2 | 10 | -2.2 | | +| 3 | 20 | -0.6 | | +| 4 | 30 | -0.6 | | +| 5 | 35 | -0.3 | | +| 6 | 45 | -1.2 | | +| 7 | 55 | -5.9 | | +| 8 | 120 | -2.2 | | +| 9 | 170 | -0.8 | | +| 10 | 245 | -6.3 | | +| 11 | 330 | -7.5 | | +| 12 | 480 | -7.1 | | + +**Table G.2.1.1-4: TDLC300 (DS = 300 ns)** + +| Tap # | Delay (ns) | Power (dB) | Fading distribution | +|-------|------------|------------|---------------------| +| 1 | 0 | -6.9 | Rayleigh | +| 2 | 65 | 0 | | +| 3 | 70 | -7.7 | | +| 4 | 190 | -2.5 | | +| 5 | 195 | -2.4 | | +| 6 | 200 | -9.9 | | +| 7 | 240 | -8.0 | | +| 8 | 325 | -6.6 | | +| 9 | 520 | -7.1 | | +| 10 | 1045 | -13.0 | | +| 11 | 1510 | -14.2 | | +| 12 | 2595 | -16.0 | | + +## G.2.2 Combinations of channel model parameters + +The propagation conditions used for the performance measurements in multi-path fading environment are indicated as a combination of a channel model name and a maximum Doppler frequency, i.e., TDLA-, TDLB- or TDLC- where '' indicates the desired delay spread and '' indicates the maximum Doppler frequency (Hz). + +Table G.2.2-1 show the propagation conditions that are used for the performance measurements in multi-path fading environment for low, medium and high Doppler frequencies for FR1. + +**Table G.2.2-1: Channel model parameters for FR1** + +| Combination name | Model | Maximum Doppler frequency | +|------------------|---------|---------------------------| +| TDLA30-5 | TDLA30 | 5 Hz | +| TDLA30-10 | TDLA30 | 10 Hz | +| TDLB100-400 | TDLB100 | 400 Hz | +| TDLC300-100 | TDLC300 | 100 Hz | +| TDLC300-600 | TDLC300 | 600 Hz | +| TDLC300-1200 | TDLC300 | 1200 Hz | + +## G.2.3 MIMO channel correlation matrices + +The MIMO channel correlation matrices defined in annex G.2.3 apply for the antenna configuration using uniform linear arrays at both gNB and UE and for the antenna configuration using cross polarized antennas. + +### G.2.3.1 MIMO correlation matrices using Uniform Linear Array + +The MIMO channel correlation matrices defined in annex G.2.3.1 apply for the antenna configuration using uniform linear array (ULA) at both gNB and UE. + +#### G.2.3.1.1 Definition of MIMO correlation matrices + +Table G.2.3.1.1-1 defines the correlation matrix for the gNB. + +**Table G.2.3.1.1-1: gNB correlation matrix** + +| | gNB correlation | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| One antenna | $R_{gNB} = 1$ | +| Two antennas | $R_{gNB} = \begin{pmatrix} 1 & \alpha \\ \alpha^* & 1 \end{pmatrix}$ | +| Four antennas | $R_{gNB} = \begin{pmatrix} 1 & \alpha^{1/9} & \alpha^{4/9} & \alpha \\ \alpha^{1/9*} & 1 & \alpha^{1/9} & \alpha^{4/9} \\ \alpha^{4/9*} & \alpha^{1/9*} & 1 & \alpha^{1/9} \\ \alpha^* & \alpha^{4/9*} & \alpha^{1/9*} & 1 \end{pmatrix}$ | +| Eight antennas | $R_{gNB} = \begin{pmatrix} 1 & \alpha^{1/49} & \alpha^{4/49} & \alpha^{9/49} & \alpha^{16/49} & \alpha^{25/49} & \alpha^{36/49} & \alpha \\ \alpha^{1/49*} & 1 & \alpha^{1/49} & \alpha^{4/49} & \alpha^{9/49} & \alpha^{16/49} & \alpha^{25/49} & \alpha^{36/49} \\ \alpha^{4/49*} & \alpha^{1/49*} & 1 & \alpha^{1/49} & \alpha^{4/49} & \alpha^{9/49} & \alpha^{16/49} & \alpha^{25/49} \\ \alpha^{9/49*} & \alpha^{4/49*} & \alpha^{1/49*} & 1 & \alpha^{1/49} & \alpha^{4/49} & \alpha^{9/49} & \alpha^{16/49} \\ \alpha^{16/49*} & \alpha^{9/49*} & \alpha^{4/49*} & \alpha^{1/49*} & 1 & \alpha^{1/49} & \alpha^{4/49} & \alpha^{9/49} \\ \alpha^{25/49*} & \alpha^{16/49*} & \alpha^{9/49*} & \alpha^{4/49*} & \alpha^{1/49*} & 1 & \alpha^{1/49} & \alpha^{4/49} \\ \alpha^{36/49*} & \alpha^{25/49*} & \alpha^{16/49*} & \alpha^{9/49*} & \alpha^{4/49*} & \alpha^{1/49*} & 1 & \alpha^{1/49} \\ \alpha^* & \alpha^{36/49*} & \alpha^{25/49*} & \alpha^{16/49*} & \alpha^{9/49*} & \alpha^{4/49*} & \alpha^{1/49*} & 1 \end{pmatrix}$ | + +Table G.2.3.1.1-2 defines the correlation matrix for the UE: + +**Table G.2.3.1.1-2: UE correlation matrix** + +| | One antenna | Two antennas | Four antennas | +|----------------|--------------------|-------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UE correlation | $R_{UE} = 1$ | $R_{UE} = \begin{pmatrix} 1 & \beta \\ \beta^* & 1 \end{pmatrix}$ | $R_{UE} = \begin{pmatrix} 1 & \beta^{1/9} & \beta^{4/9} & \beta \\ \beta^{1/9*} & 1 & \beta^{1/9} & \beta^{4/9} \\ \beta^{4/9*} & \beta^{1/9*} & 1 & \beta^{1/9} \\ \beta^* & \beta^{4/9*} & \beta^{1/9*} & 1 \end{pmatrix}$ | + +Table G.2.3.1.1-3 defines the channel spatial correlation matrix $R_{spat}$ . The parameters, $\alpha$ and $\beta$ in table G.2.3.1.1-3 defines the spatial correlation between the antennas at the gNB and UE respectively. + +**Table G.2.3.1.1-3:** $R_{spat}$ correlation matrices + +| | | +|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1x2 case | $R_{spat} = R_{gNB} = \begin{bmatrix} 1 & \alpha \\ \alpha^* & 1 \end{bmatrix}$ | +| 1x4 case | $R_{spat} = R_{gNB} = \begin{pmatrix} 1 & \alpha^{1/3} & \alpha^{4/9} & \alpha \\ \alpha^{1/3*} & 1 & \alpha^{1/3} & \alpha^{4/9} \\ \alpha^{4/9*} & \alpha^{1/3*} & 1 & \alpha^{1/3} \\ \alpha^* & \alpha^{4/9*} & \alpha^{1/3*} & 1 \end{pmatrix}$ | +| 2x2 case | $R_{spat} = R_{UE} \otimes R_{gNB} = \begin{pmatrix} 1 & \beta \\ \beta^* & 1 \end{pmatrix} \otimes \begin{pmatrix} 1 & \alpha \\ \alpha^* & 1 \end{pmatrix} = \begin{pmatrix} 1 & \alpha & \beta & \beta\alpha \\ \alpha^* & 1 & \beta\alpha^* & \beta \\ \beta^* & \beta^*\alpha & 1 & \alpha \\ \beta^*\alpha^* & \beta^* & \alpha^* & 1 \end{pmatrix}$ | +| 2x4 case | $R_{spat} = R_{UE} \otimes R_{gNB} = \begin{pmatrix} 1 & \beta \\ \beta^* & 1 \end{pmatrix} \otimes \begin{pmatrix} 1 & \alpha^{1/3} & \alpha^{4/9} & \alpha \\ \alpha^{1/3*} & 1 & \alpha^{1/3} & \alpha^{4/9} \\ \alpha^{4/9*} & \alpha^{1/3*} & 1 & \alpha^{1/3} \\ \alpha^* & \alpha^{4/9*} & \alpha^{1/3*} & 1 \end{pmatrix}$ | +| 4x4 case | $R_{spat} = R_{UE} \otimes R_{gNB} = \begin{pmatrix} 1 & \beta^{1/3} & \beta^{4/9} & \beta \\ \beta^{1/3*} & 1 & \beta^{1/3} & \beta^{4/9} \\ \beta^{4/9*} & \beta^{1/3*} & 1 & \beta^{1/3} \\ \beta^* & \beta^{4/9*} & \beta^{1/3*} & 1 \end{pmatrix} \otimes \begin{pmatrix} 1 & \alpha^{1/3} & \alpha^{4/9} & \alpha \\ \alpha^{1/3*} & 1 & \alpha^{1/3} & \alpha^{4/9} \\ \alpha^{4/9*} & \alpha^{1/3*} & 1 & \alpha^{1/3} \\ \alpha^* & \alpha^{4/9*} & \alpha^{1/3*} & 1 \end{pmatrix}$ | + +For cases with more antennas at either gNB or UE or both, the channel spatial correlation matrix can still be expressed as the Kronecker product of $R_{UE}$ and $R_{gNB}$ according to $R_{spat} = R_{UE} \otimes R_{gNB}$ . + +### G.2.3.1.2 MIMO correlation matrices at high, medium and low level + +The $\alpha$ and $\beta$ for different correlation types are given in table G.2.3.1.2-1. + +**Table G.2.3.1.2-1: Correlation for high, medium and low level** + +| Low correlation | | Medium correlation | | High correlation | | +|-----------------|---------|--------------------|---------|------------------|---------| +| $\alpha$ | $\beta$ | $\alpha$ | $\beta$ | $\alpha$ | $\beta$ | +| 0 | 0 | 0.9 | 0.3 | 0.9 | 0.9 | + +The correlation matrices for high, medium and low correlation are defined in table G.2.3.1.2-2, G.2.3.1.2-3 and G.2.3.1.2-4 as below. + +The values in table G.2.3.1.2-2 have been adjusted for the 2x4 and 4x4 high correlation cases to insure the correlation matrix is positive semi-definite after round-off to 4 digit precision. This is done using the equation: + +$$\mathbf{R}_{high} = [\mathbf{R}_{spatial} + a\mathbf{I}_n] / (1 + a)$$ + +Where the value "a" is a scaling factor such that the smallest value is used to obtain a positive semi-definite result. For the 2x4 high correlation case, a = 0.00010. For the 4x4 high correlation case, a = 0.00012. + +The same method is used to adjust the 4x4 medium correlation matrix in table G.2.3.1.2-3 to insure the correlation matrix is positive semi-definite after round-off to 4 digit precision with a = 0.00012. + +**Table G.2.3.1.2-2: MIMO correlation matrices for high correlation** + +| | | +|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1x2 case | $R_{high} = \begin{pmatrix} 1 & 0.9 \\ 0.9 & 1 \end{pmatrix}$ | +| 2x2 case | $R_{high} = \begin{pmatrix} 1 & 0.9 & 0.9 & 0.81 \\ 0.9 & 1 & 0.81 & 0.9 \\ 0.9 & 0.81 & 1 & 0.9 \\ 0.81 & 0.9 & 0.9 & 1 \end{pmatrix}$ | +| 2x4 case | $R_{high} = \begin{bmatrix} 1.0000 & 0.9883 & 0.9542 & 0.8999 & 0.8999 & 0.8894 & 0.8587 & 0.8099 \\ 0.9883 & 1.0000 & 0.9883 & 0.9542 & 0.8894 & 0.8999 & 0.8894 & 0.8587 \\ 0.9542 & 0.9883 & 1.0000 & 0.9883 & 0.8587 & 0.8894 & 0.8999 & 0.8894 \\ 0.8999 & 0.9542 & 0.9883 & 1.0000 & 0.8099 & 0.8587 & 0.8894 & 0.8999 \\ 0.8999 & 0.8894 & 0.8587 & 0.8099 & 1.0000 & 0.9883 & 0.9542 & 0.8999 \\ 0.8894 & 0.8999 & 0.8894 & 0.8587 & 0.9883 & 1.0000 & 0.9883 & 0.9542 \\ 0.8587 & 0.8894 & 0.8999 & 0.8894 & 0.9542 & 0.9883 & 1.0000 & 0.9883 \\ 0.8099 & 0.8587 & 0.8894 & 0.8999 & 0.8999 & 0.9542 & 0.9883 & 1.0000 \end{bmatrix}$ | +| 4x4 case | $R_{high} = \begin{bmatrix} 1.0000 & 0.9882 & 0.9541 & 0.8999 & 0.9882 & 0.9767 & 0.9430 & 0.8894 & 0.9541 & 0.9430 & 0.9105 & 0.8587 & 0.8999 & 0.8894 & 0.8587 & 0.8099 \\ 0.9882 & 1.0000 & 0.9882 & 0.9541 & 0.9767 & 0.9882 & 0.9767 & 0.9430 & 0.9430 & 0.9541 & 0.9430 & 0.9105 & 0.8894 & 0.8999 & 0.8894 & 0.8587 \\ 0.9541 & 0.9882 & 1.0000 & 0.9882 & 0.9430 & 0.9767 & 0.9882 & 0.9767 & 0.9105 & 0.9430 & 0.9541 & 0.9430 & 0.8587 & 0.8894 & 0.8999 & 0.8894 \\ 0.8999 & 0.9541 & 0.9882 & 1.0000 & 0.8894 & 0.9430 & 0.9767 & 0.9882 & 0.8587 & 0.9105 & 0.9430 & 0.9541 & 0.8099 & 0.8587 & 0.8894 & 0.8999 \\ 0.9882 & 0.9767 & 0.9430 & 0.8894 & 1.0000 & 0.9882 & 0.9541 & 0.8999 & 0.9882 & 0.9767 & 0.9430 & 0.8894 & 0.9541 & 0.9430 & 0.9105 & 0.8587 \\ 0.9767 & 0.9882 & 0.9767 & 0.9430 & 0.9882 & 1.0000 & 0.9882 & 0.9541 & 0.9767 & 0.9882 & 0.9767 & 0.9430 & 0.9430 & 0.9541 & 0.9430 & 0.9105 \\ 0.9430 & 0.9767 & 0.9882 & 0.9767 & 0.9541 & 0.9882 & 1.0000 & 0.9882 & 0.9430 & 0.9767 & 0.9882 & 0.9767 & 0.9105 & 0.9430 & 0.9541 & 0.9430 \\ 0.8894 & 0.9430 & 0.9767 & 0.9882 & 0.8999 & 0.9541 & 0.9882 & 1.0000 & 0.8894 & 0.9430 & 0.9767 & 0.9882 & 0.8587 & 0.9105 & 0.9430 & 0.9541 \\ 0.9541 & 0.9430 & 0.9105 & 0.8587 & 0.9882 & 0.9767 & 0.9430 & 0.8894 & 1.0000 & 0.9882 & 0.9541 & 0.8999 & 0.9882 & 0.9767 & 0.9430 & 0.8894 \\ 0.9430 & 0.9541 & 0.9430 & 0.9105 & 0.9767 & 0.9882 & 0.9767 & 0.9430 & 0.9882 & 1.0000 & 0.9882 & 0.9541 & 0.9767 & 0.9882 & 0.9767 & 0.9430 \\ 0.9105 & 0.9430 & 0.9541 & 0.9430 & 0.9430 & 0.9767 & 0.9882 & 0.9767 & 0.9541 & 0.9882 & 1.0000 & 0.9882 & 0.9430 & 0.9767 & 0.9882 & 0.9767 \\ 0.8587 & 0.9105 & 0.9430 & 0.9541 & 0.8894 & 0.9430 & 0.9767 & 0.9882 & 0.8999 & 0.9541 & 0.9882 & 1.0000 & 0.8894 & 0.9430 & 0.9767 & 0.9882 \\ 0.8999 & 0.8894 & 0.8587 & 0.8099 & 0.9541 & 0.9430 & 0.9105 & 0.8587 & 0.9882 & 0.9767 & 0.9430 & 0.8894 & 1.0000 & 0.9882 & 0.9541 & 0.8999 \\ 0.8894 & 0.8999 & 0.8894 & 0.8587 & 0.9430 & 0.9541 & 0.9430 & 0.9105 & 0.9767 & 0.9882 & 0.9767 & 0.9430 & 0.9882 & 1.0000 & 0.9882 & 0.9541 \\ 0.8587 & 0.8894 & 0.8999 & 0.8894 & 0.9105 & 0.9430 & 0.9541 & 0.9430 & 0.9430 & 0.9767 & 0.9882 & 0.9767 & 0.9541 & 0.9882 & 1.0000 & 0.9882 \\ 0.8099 & 0.8587 & 0.8894 & 0.8999 & 0.8587 & 0.9105 & 0.9430 & 0.9541 & 0.8894 & 0.9430 & 0.9767 & 0.9882 & 0.8999 & 0.9541 & 0.9882 & 1.0000 \end{bmatrix}$ | + +**Table G.2.3.1.2-3: MIMO correlation matrices for medium correlation** + +| | | | +|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| 1x2 case | [N/A] | | +| 2x2 case | $R_{medium} = \begin{pmatrix} 1.0000 & 0.9000 & 0.3000 & 0.2700 \\ 0.9000 & 1.0000 & 0.2700 & 0.3000 \\ 0.3000 & 0.2700 & 1.0000 & 0.9000 \\ 0.2700 & 0.3000 & 0.9000 & 1.0000 \end{pmatrix}$ | | +| 2x4 case | $R_{medium} = \begin{pmatrix} 1.0000 & 0.9884 & 0.9543 & 0.9000 & 0.3000 & 0.2965 & 0.2863 & 0.2700 \\ 0.9884 & 1.0000 & 0.9884 & 0.9543 & 0.2965 & 0.3000 & 0.2965 & 0.2863 \\ 0.9543 & 0.9884 & 1.0000 & 0.9884 & 0.2863 & 0.2965 & 0.3000 & 0.2965 \\ 0.9000 & 0.9543 & 0.9884 & 1.0000 & 0.2700 & 0.2863 & 0.2965 & 0.3000 \\ 0.3000 & 0.2965 & 0.2863 & 0.2700 & 1.0000 & 0.9884 & 0.9543 & 0.9000 \\ 0.2965 & 0.3000 & 0.2965 & 0.2863 & 0.9884 & 1.0000 & 0.9884 & 0.9543 \\ 0.2863 & 0.2965 & 0.3000 & 0.2965 & 0.9543 & 0.9884 & 1.0000 & 0.9884 \\ 0.2700 & 0.2863 & 0.2965 & 0.3000 & 0.9000 & 0.9543 & 0.9884 & 1.0000 \end{pmatrix}$ | | +| 4x4 case | $R_{medium} = \begin{pmatrix} 1.0000 & 0.9882 & 0.9541 & 0.8999 & 0.8747 & 0.8645 & 0.8347 & 0.7872 & 0.5855 & 0.5787 & 0.5588 & 0.5270 & 0.3000 & 0.2965 & 0.2862 & 0.2700 \\ 0.9882 & 1.0000 & 0.9882 & 0.9541 & 0.8645 & 0.8747 & 0.8645 & 0.8347 & 0.5787 & 0.5855 & 0.5787 & 0.5588 & 0.2965 & 0.3000 & 0.2965 & 0.2862 \\ 0.9541 & 0.9882 & 1.0000 & 0.9882 & 0.8347 & 0.8645 & 0.8747 & 0.8645 & 0.5588 & 0.5787 & 0.5855 & 0.5787 & 0.2862 & 0.2965 & 0.3000 & 0.2965 \\ 0.8999 & 0.9541 & 0.9882 & 1.0000 & 0.7872 & 0.8347 & 0.8645 & 0.8747 & 0.5270 & 0.5588 & 0.5787 & 0.5855 & 0.2700 & 0.2862 & 0.2965 & 0.3000 \\ 0.8747 & 0.8645 & 0.8347 & 0.7872 & 1.0000 & 0.9882 & 0.9541 & 0.8999 & 0.8747 & 0.8645 & 0.8347 & 0.7872 & 0.5855 & 0.5787 & 0.5588 & 0.5270 \\ 0.8645 & 0.8747 & 0.8645 & 0.8347 & 0.9882 & 1.0000 & 0.9882 & 0.9541 & 0.8645 & 0.8747 & 0.8645 & 0.8347 & 0.5787 & 0.5855 & 0.5787 & 0.5588 \\ 0.8347 & 0.8645 & 0.8747 & 0.8645 & 0.9541 & 0.9882 & 1.0000 & 0.9882 & 0.8347 & 0.8645 & 0.8747 & 0.8645 & 0.5588 & 0.5787 & 0.5855 & 0.5787 \\ 0.7872 & 0.8347 & 0.8645 & 0.8747 & 0.8999 & 0.9541 & 0.9882 & 1.0000 & 0.7872 & 0.8347 & 0.8645 & 0.8747 & 0.5270 & 0.5588 & 0.5787 & 0.5855 \\ 0.5855 & 0.5787 & 0.5588 & 0.5270 & 0.8747 & 0.8645 & 0.8347 & 0.7872 & 1.0000 & 0.9882 & 0.9541 & 0.8999 & 0.8747 & 0.8645 & 0.8347 & 0.7872 \\ 0.5787 & 0.5855 & 0.5787 & 0.5588 & 0.8645 & 0.8747 & 0.8645 & 0.8347 & 0.9882 & 1.0000 & 0.9882 & 0.9541 & 0.8645 & 0.8747 & 0.8645 & 0.8347 \\ 0.5588 & 0.5787 & 0.5855 & 0.5787 & 0.8347 & 0.8645 & 0.8747 & 0.8645 & 0.9541 & 0.9882 & 1.0000 & 0.9882 & 0.8347 & 0.8645 & 0.8747 & 0.8645 \\ 0.5270 & 0.5588 & 0.5787 & 0.5855 & 0.7872 & 0.8347 & 0.8645 & 0.8747 & 0.8999 & 0.9541 & 0.9882 & 1.0000 & 0.7872 & 0.8347 & 0.8645 & 0.8747 \\ 0.3000 & 0.2965 & 0.2862 & 0.2700 & 0.5855 & 0.5787 & 0.5588 & 0.5270 & 0.8747 & 0.8645 & 0.8347 & 0.7872 & 1.0000 & 0.9882 & 0.9541 & 0.8999 \\ 0.2965 & 0.3000 & 0.2965 & 0.2862 & 0.5787 & 0.5855 & 0.5787 & 0.5588 & 0.8645 & 0.8747 & 0.8645 & 0.8347 & 0.9882 & 1.0000 & 0.9882 & 0.9541 \\ 0.2862 & 0.2965 & 0.3000 & 0.2965 & 0.5588 & 0.5787 & 0.5855 & 0.5787 & 0.8347 & 0.8645 & 0.8747 & 0.8645 & 0.9541 & 0.9882 & 1.0000 & 0.9882 \\ 0.2700 & 0.2862 & 0.2965 & 0.3000 & 0.5270 & 0.5588 & 0.5787 & 0.5855 & 0.7872 & 0.8347 & 0.8645 & 0.8747 & 0.8999 & 0.9541 & 0.9882 & 1.0000 \end{pmatrix}$ | | + +**Table G.2.3.1.2-4: MIMO correlation matrices for low correlation** + +| | | +|----------|--| +| 1x2 case | | +| 1x4 case | | +| 1x8 case | | +| 2x2 case | | +| 2x4 case | | +| 2x4 case | | +| 4x4 case | | + +In table G.2.3.1.2-4, $\mathbf{I}_d$ is a $d \times d$ identity matrix. + +NOTE: For completeness, the correlation matrices were defined for high, medium and low correlation but performance requirements exist only for low correlation. + +## G.2.3.2 Multi-antenna channel models using cross polarized antennas + +The MIMO channel correlation matrices defined in annex G.2.3.2 apply to two cases as presented below: + +- One TX antenna and multiple RX antennas case, with cross polarized antennas used at gNB +- Multiple TX antennas and multiple RX antennas case, with cross polarized antennas used at both UE and gNB + +The cross-polarized antenna elements with +/-45 degrees polarization slant angles are deployed at gNB. For one TX antenna case, antenna element with +90 degree polarization slant angle is deployed at UE. For multiple TX antennas case, cross-polarized antenna elements with +90/0 degrees polarization slant angles are deployed at UE. + +For the cross-polarized antennas, the N antennas are labelled such that antennas for one polarization are listed from 1 to N/2 and antennas for the other polarization are listed from N/2+1 to N, where N is the number of TX or RX antennas. + +### G.2.3.2.1 Definition of MIMO correlation matrices using cross polarized antennas + +For the channel spatial correlation matrix, the following is used: + +$$R_{spat} = P_{UL} (R_{UE} \otimes \Gamma_{UL} \otimes R_{gNB}) P_{UL}^T$$ + +Where + +- $R_{UE}$ is the spatial correlation matrix at the UE with same polarization, +- $R_{gNB}$ is the spatial correlation matrix at the gNB with same polarization, +- $\Gamma_{UL}$ is a polarization correlation matrix, +- $P_{UL}$ is a permutation matrix, and +- $(\cdot)^T$ denotes transpose. + +Table G.2.3.2.1-1 defines the polarization correlation matrix. + +**Table G.2.3.2.1-1: Polarization correlation matrix** + +| | One TX antenna | Multiple TX antennas | +|---------------------------------|--------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| Polarization correlation matrix | $\Gamma_{UL} = \begin{bmatrix} 1 & -\gamma \\ -\gamma & 1 \end{bmatrix}$ | $\Gamma_{UL} = \begin{bmatrix} 1 & -\gamma & 0 & 0 \\ -\gamma & 1 & 0 & 0 \\ 0 & 0 & 1 & \gamma \\ 0 & 0 & \gamma & 1 \end{bmatrix}$ | + +The matrix $P_{UL}$ is defined as + +$$P_{UL}(a,b) = \begin{cases} 1 & \text{for } a = (j-1)N_r + i \text{ and } b = 2(j-1)N_r + i, & i = 1, \dots, N_r, j = 1, \dots, \lceil N_t/2 \rceil \\ 1 & \text{for } a = (j-1)N_r + i \text{ and } b = 2(j - \lceil N_t/2 \rceil)N_r - N_r + i, & i = 1, \dots, N_r, j = \lceil N_t/2 \rceil + 1, \dots, N_t \\ 0 & \text{otherwise} & \end{cases}$$ + +where $N_t$ and $N_r$ is the number of TX and RX antennas respectively, and $\lceil \cdot \rceil$ is the ceiling operator. + +The matrix $P_{UL}$ is used to map the spatial correlation coefficients in accordance with the antenna element labelling system described in G.2.3.2. + +### G.2.3.2.2 Spatial correlation matrices at UE and gNB sides + +#### G.2.3.2.2.1 Spatial correlation matrices at UE side + +For 1-antenna transmitter, $R_{UE} = 1$ . + +For 2-antenna transmitter using one pair of cross-polarized antenna elements, $R_{UE} = 1$ . + +$$R_{UE} = \begin{pmatrix} 1 & \beta \\ \beta^* & 1 \end{pmatrix}$$ + +For 4-antenna transmitter using two pairs of cross-polarized antenna elements, + +**G.2.3.2.2.2 Spatial correlation matrices at gNB side** + +For 2-antenna receiver using one pair of cross-polarized antenna elements, $R_{gNB} = \mathbf{I}_2$ . + +For 4-antenna receiver using two pairs of cross-polarized antenna elements, + +$$R_{gNB} = \begin{bmatrix} 1 & \alpha \\ \alpha^* & 1 \end{bmatrix}$$ + +For 8-antenna receiver using four pairs of cross-polarized antenna elements, + +$$R_{gNB} = \begin{pmatrix} 1 & \alpha^{1/3} & \alpha^{4/3} & \alpha \\ \alpha^{1/3*} & 1 & \alpha^{1/3} & \alpha^{4/3} \\ \alpha^{4/3*} & \alpha^{1/3*} & 1 & \alpha^{1/3} \\ \alpha^* & \alpha^{4/3*} & \alpha^{1/3*} & 1 \end{pmatrix}$$ + +**G.2.3.2.3 MIMO correlation matrices using cross polarized antennas** + +The values for parameters $\alpha$ , $\beta$ and $\gamma$ for low spatial correlation are given in table G.2.3.2.3-1. + +**Table G.2.3.2.3-1: Values for parameters $\alpha$ , $\beta$ and $\gamma$** + +| Low spatial correlation | | | +|------------------------------------------------------------------------------------------------------------|---------|----------| +| $\alpha$ | $\beta$ | $\gamma$ | +| 0 | 0 | 0 | +| Note 1: Value of $\alpha$ applies when more than one pair of cross-polarized antenna elements at gNB side. | | | +| Note 2: Value of $\beta$ applies when more than one pair of cross-polarized antenna elements at UE side. | | | + +The correlation matrices for low spatial correlation are defined in table G.2.3.2.3-2 as below. + +**Table G.2.3.2.3-2: MIMO correlation matrices for low spatial correlation** + +| | | +|----------|-----------------------------| +| 1x8 case | $R_{low} = \mathbf{I}_8$ | +| 2x8 case | $R_{low} = \mathbf{I}_{16}$ | + +In table G.2.3.2.3-2, $\mathbf{I}_d$ is a $d \times d$ identity matrix. + +## G.3 High speed train condition + +High speed train conditions are as follows: + +- Scenario 1-NR350 / Scenario 1-NR500: Open space +- Scenario 3-NR350 / Scenario 3-NR500: Tunnel + +The high speed train conditions for the test of the baseband performance are two non-fading propagation channels. For BS with Rx diversity, the Doppler shift time variation is the same for each antenna at each time instant. + +Doppler shift for both scenarios is given by: + +$$(G.3.1)$$ + +where $f_D$ is the Doppler shift and $f_{Dmax}$ is the maximum Doppler frequency. The cosine of angle is given by: + +$$(G.3.2)$$ + +$$(G.3.3)$$ + +$$(G.3.4)$$ + +where $d_0$ is the initial distance of the train from BS, and $d$ is BS-Railway track distance, both in meters; $V$ is the velocity of the train in m/s, $t$ is time in seconds. + +The required input parameters are listed in table G.3-1 and G.3-2. The resulting time varying Doppler shift is shown in Figure G.3-1, G.3-2, G.3-3 and G.3-4 for 350km/h scenarios, and in Figure G.3-5, G.3-6, G.3-7 and G.3-8 for 500km/h scenarios. For 350km/h scenarios, the Doppler shift was derived such that it corresponds to a velocity of around 350km/h for band n1 for the 15kHz SCS and for band n77 for the 30kHz SCS. For 500km/h scenarios, the Doppler shift was derived such that it corresponds to a velocity of around 500km/h for band n3 for the 15kHz SCS and for band n77 for the 30kHz SCS. However, the same Doppler shift requirement shall be applied regardless of the frequency of operation of the base station and thus for lower frequencies, the supported speed is higher. + +**Table G.3-1: Parameters for high speed train conditions for UE velocity 350 km/h** + +| Parameter | Value | | +|-----------|------------------------------------------------|------------------------------------------------| +| | Scenario 1-NR350 | Scenario 3-NR350 | +| $d_0$ | 700 m | 300 m | +| $d$ | 150 m | 2 m | +| $V$ | 350 km/h | 350 km/h | +| $f_D$ | 1340 Hz for 15kHz SCS
2334 Hz for 30kHz SCS | 1340 Hz for 15kHz SCS
2334 Hz for 30kHz SCS | + +**Table G.3-2: Parameters for high speed train conditions for UE velocity 500 km/h** + +| Parameter | Value | | +|-----------|------------------------------------------------|------------------------------------------------| +| | Scenario 1-NR500 | Scenario 3-NR500 | +| $d_0$ | 700 m | 300 m | +| $d$ | 150 m | 2 m | +| $V$ | 500 km/h | 500 km/h | +| $f_D$ | 1740 Hz for 15kHz SCS
3334 Hz for 30kHz SCS | 1740 Hz for 15kHz SCS
3334 Hz for 30kHz SCS | + +![Graph of Doppler Shift (Hz) vs Time (sec) for scenario 1-NR350 (15 kHz SCS). The plot shows a smooth sinusoidal-like wave oscillating between approximately 1200 Hz and -1200 Hz over a 50-second period.](34e6c9b53bd1e85bf2448540c7ed2484_img.jpg) + +This graph shows the Doppler shift trajectory for scenario 1-NR350 with a 15 kHz subcarrier spacing. The y-axis represents the Doppler Shift in Hz, ranging from -3000 to 3000 with major grid lines every 1000 Hz. The x-axis represents Time in seconds, ranging from 0 to 50 with major grid lines every 10 seconds. The curve starts at approximately 1200 Hz at 0 seconds, decreases to a minimum of about -1200 Hz at 8 seconds, increases to a peak of about 1200 Hz at 15 seconds, decreases again to -1200 Hz at 22 seconds, increases to 1200 Hz at 29 seconds, decreases to -1200 Hz at 36 seconds, increases to 1200 Hz at 43 seconds, and finally decreases to about -1000 Hz at 50 seconds. + +Graph of Doppler Shift (Hz) vs Time (sec) for scenario 1-NR350 (15 kHz SCS). The plot shows a smooth sinusoidal-like wave oscillating between approximately 1200 Hz and -1200 Hz over a 50-second period. + +Figure G.3-1: Doppler shift trajectory for scenario 1-NR350 (15 kHz SCS) + +![Graph of Doppler Shift (Hz) vs Time (sec) for scenario 3-NR350 (15 kHz SCS). The plot shows a square wave oscillating between approximately 1200 Hz and -1200 Hz over a 50-second period.](c05aca0e296f64ce88749630314a61c3_img.jpg) + +This graph shows the Doppler shift trajectory for scenario 3-NR350 with a 15 kHz subcarrier spacing. The y-axis represents the Doppler Shift in Hz, ranging from -3000 to 3000 with major grid lines every 1000 Hz. The x-axis represents Time in seconds, ranging from 0 to 50 with major grid lines every 10 seconds. The plot is a square wave that starts at approximately 1200 Hz at 0 seconds, drops to -1200 Hz at 2 seconds, returns to 1200 Hz at 4 seconds, drops to -1200 Hz at 6 seconds, returns to 1200 Hz at 8 seconds, drops to -1200 Hz at 10 seconds, returns to 1200 Hz at 12 seconds, drops to -1200 Hz at 14 seconds, returns to 1200 Hz at 16 seconds, drops to -1200 Hz at 18 seconds, returns to 1200 Hz at 20 seconds, drops to -1200 Hz at 22 seconds, returns to 1200 Hz at 24 seconds, drops to -1200 Hz at 26 seconds, returns to 1200 Hz at 28 seconds, drops to -1200 Hz at 30 seconds, returns to 1200 Hz at 32 seconds, drops to -1200 Hz at 34 seconds, returns to 1200 Hz at 36 seconds, drops to -1200 Hz at 38 seconds, returns to 1200 Hz at 40 seconds, drops to -1200 Hz at 42 seconds, returns to 1200 Hz at 44 seconds, drops to -1200 Hz at 46 seconds, returns to 1200 Hz at 48 seconds, and ends at 1200 Hz at 50 seconds. + +Graph of Doppler Shift (Hz) vs Time (sec) for scenario 3-NR350 (15 kHz SCS). The plot shows a square wave oscillating between approximately 1200 Hz and -1200 Hz over a 50-second period. + +Figure G.3-2: Doppler shift trajectory for scenario 3-NR350 (15 kHz SCS) + +![Graph of Doppler Shift (Hz) vs Time (sec) for scenario 1-NR350 (30 kHz SCS). The plot shows a smooth sinusoidal-like wave oscillating between approximately 2000 Hz and -2000 Hz over a 50-second period.](c9b6396dc9aa7e326dd536c39047fe28_img.jpg) + +This graph shows the Doppler shift trajectory for scenario 1-NR350 with a 30 kHz subcarrier spacing. The y-axis represents the Doppler Shift in Hz, ranging from -3000 to 3000 with major grid lines every 1000 Hz. The x-axis represents Time in seconds, ranging from 0 to 50 with major grid lines every 10 seconds. The curve starts at approximately 2000 Hz at 0 seconds, decreases to a minimum of about -2000 Hz at 8 seconds, increases to a peak of about 2000 Hz at 15 seconds, decreases again to -2000 Hz at 22 seconds, increases to 2000 Hz at 29 seconds, decreases to -2000 Hz at 36 seconds, increases to 2000 Hz at 43 seconds, and finally decreases to about -1800 Hz at 50 seconds. + +Graph of Doppler Shift (Hz) vs Time (sec) for scenario 1-NR350 (30 kHz SCS). The plot shows a smooth sinusoidal-like wave oscillating between approximately 2000 Hz and -2000 Hz over a 50-second period. + +Figure G.3-3: Doppler shift trajectory for scenario 1-NR350 (30 kHz SCS) + +![Figure G.3-4: Doppler shift trajectory for scenario 3-NR350 (30 kHz SCS). The graph shows a square wave oscillating between approximately 2500 Hz and -2500 Hz over a 50-second time period.](71e9881885098f5d35adad3ffb6c4687_img.jpg) + +This graph displays the Doppler shift trajectory for scenario 3-NR350 with a 30 kHz SCS. The y-axis is labeled 'Doppler Shift (Hz)' and ranges from -3000 to 3000 in increments of 1000. The x-axis is labeled 'Time (sec)' and ranges from 0 to 50 in increments of 10. The plot shows a square wave that starts at approximately 2500 Hz at 0 seconds, drops to approximately -2500 Hz at about 2.5 seconds, returns to 2500 Hz at 5 seconds, drops again to -2500 Hz at 7.5 seconds, and continues this pattern with a period of 5 seconds for a total of 10 cycles over the 50-second duration. + +Figure G.3-4: Doppler shift trajectory for scenario 3-NR350 (30 kHz SCS). The graph shows a square wave oscillating between approximately 2500 Hz and -2500 Hz over a 50-second time period. + +Figure G.3-4: Doppler shift trajectory for scenario 3-NR350 (30 kHz SCS) + +![Figure G.3-5: Doppler shift trajectory for scenario 1-NR500 (15 kHz SCS). The graph shows a smooth, sinusoidal-like wave oscillating between approximately 1500 Hz and -1500 Hz over a 50-second time period.](4e774fb157e9d60398aa1a61b5c01f35_img.jpg) + +This graph displays the Doppler shift trajectory for scenario 1-NR500 with a 15 kHz SCS. The y-axis is labeled 'Doppler Shift (Hz)' and ranges from -3000 to 3000 in increments of 1000. The x-axis is labeled 'Time (sec)' and ranges from 0 to 50 in increments of 10. The plot shows a smooth, sinusoidal-like wave that starts at approximately 1500 Hz at 0 seconds, decreases to a minimum of approximately -1500 Hz at about 5 seconds, increases back to 1500 Hz at 10 seconds, decreases to -1500 Hz at 15 seconds, and continues this pattern with a period of 10 seconds for a total of 5 cycles over the 50-second duration. + +Figure G.3-5: Doppler shift trajectory for scenario 1-NR500 (15 kHz SCS). The graph shows a smooth, sinusoidal-like wave oscillating between approximately 1500 Hz and -1500 Hz over a 50-second time period. + +Figure G.3-5: Doppler shift trajectory for scenario 1-NR500 (15 kHz SCS) + +![Figure G.3-6: Doppler shift trajectory for scenario 3-NR500 (15 kHz SCS). The graph shows a square wave oscillating between approximately 1800 Hz and -1800 Hz over a 50-second time period.](19babf72812f45dcc737d237e423d2c0_img.jpg) + +This graph displays the Doppler shift trajectory for scenario 3-NR500 with a 15 kHz SCS. The y-axis is labeled 'Doppler Shift (Hz)' and ranges from -3000 to 3000 in increments of 1000. The x-axis is labeled 'Time (sec)' and ranges from 0 to 50 in increments of 10. The plot shows a square wave that starts at approximately 1800 Hz at 0 seconds, drops to approximately -1800 Hz at about 2.5 seconds, returns to 1800 Hz at 5 seconds, drops again to -1800 Hz at 7.5 seconds, and continues this pattern with a period of 5 seconds for a total of 10 cycles over the 50-second duration. + +Figure G.3-6: Doppler shift trajectory for scenario 3-NR500 (15 kHz SCS). The graph shows a square wave oscillating between approximately 1800 Hz and -1800 Hz over a 50-second time period. + +Figure G.3-6: Doppler shift trajectory for scenario 3-NR500 (15 kHz SCS) + +![Figure G.3-7: Doppler shift trajectory for scenario 1-NR500 (30 kHz SCS). The graph shows a sinusoidal Doppler shift (Hz) over time (sec). The y-axis ranges from -3000 to 3000 Hz, and the x-axis ranges from 0 to 50 seconds. The signal starts at 3000 Hz at 0 seconds, decreases to -3000 Hz at approximately 5 seconds, increases back to 3000 Hz at 10 seconds, and continues this pattern with a period of 10 seconds.](14b4b0349989d63cec07229938e57ffd_img.jpg) + +Figure G.3-7: Doppler shift trajectory for scenario 1-NR500 (30 kHz SCS). The graph shows a sinusoidal Doppler shift (Hz) over time (sec). The y-axis ranges from -3000 to 3000 Hz, and the x-axis ranges from 0 to 50 seconds. The signal starts at 3000 Hz at 0 seconds, decreases to -3000 Hz at approximately 5 seconds, increases back to 3000 Hz at 10 seconds, and continues this pattern with a period of 10 seconds. + +Figure G.3-7: Doppler shift trajectory for scenario 1-NR500 (30 kHz SCS) + +![Figure G.3-8: Doppler shift trajectory for scenario 3-NR500 (30 kHz SCS). The graph shows a square wave Doppler shift (Hz) over time (sec). The y-axis ranges from -3000 to 3000 Hz, and the x-axis ranges from 0 to 50 seconds. The signal alternates between 3000 Hz and -3000 Hz every 2.5 seconds, starting at 3000 Hz at 0 seconds.](068981837b91c115a6ac8b11ad50a49a_img.jpg) + +Figure G.3-8: Doppler shift trajectory for scenario 3-NR500 (30 kHz SCS). The graph shows a square wave Doppler shift (Hz) over time (sec). The y-axis ranges from -3000 to 3000 Hz, and the x-axis ranges from 0 to 50 seconds. The signal alternates between 3000 Hz and -3000 Hz every 2.5 seconds, starting at 3000 Hz at 0 seconds. + +Figure G.3-8: Doppler shift trajectory for scenario 3-NR500 (30 kHz SCS) + +## G.4 Moving propagation conditions + +Figure G.4-1 illustrate the moving propagation conditions for the test of the UL timing adjustment performance. The time difference between the reference timing and the first tap is according Equation (G.4-1). The timing difference between moving UE and stationary UE is equal to $\Delta\tau - (T_A - 31) \times 16 \times 64 T_c$ for 15kHz SCS and $\Delta\tau - (T_A - 31) \times 16 \times 32 T_c$ for 30kHz SCS. The relative timing among all taps is fixed. The parameters for the moving propagation conditions are shown in Table G.4-1. + +![Figure G.4-1: Moving propagation conditions diagram. It shows a timeline with a reference signal 'Ref' at time t0 and a first tap 'P1' at time t1. The time difference between them is labeled Δτ. There are also dashed vertical lines representing other taps at later times.](c291a9ff5dc662dd6c7d9f8a4e567235_img.jpg) + +Figure G.4-1: Moving propagation conditions diagram. It shows a timeline with a reference signal 'Ref' at time t0 and a first tap 'P1' at time t1. The time difference between them is labeled Δτ. There are also dashed vertical lines representing other taps at later times. + +Figure G.4-1: Moving propagation conditions + +(G.4-1) + +**Table G.4-1: Parameters for UL timing adjustment** + +| Parameter | Scenario X | Scenario Y | Scenario Z | +|----------------|--------------------------------------------------------------|--------------------------------------------------------------|--------------------------------------------------------------| +| Channel model | Stationary UE: AWGN
Moving UE: TDLC300-400 | Stationary UE: AWGN
Moving UE: AWGN | Stationary UE: AWGN
Moving UE: AWGN | +| UE speed | 120 km/h | 350 km/h | 500 km/h | +| CP length | Normal | Normal | Normal | +| A | 15 kHz: 10 $\mu\text{s}$
30 kHz: 5 $\mu\text{s}$ | 15 kHz: 10 $\mu\text{s}$
30 kHz: 5 $\mu\text{s}$ | 15 kHz: 10 $\mu\text{s}$
30 kHz: 5 $\mu\text{s}$ | +| $\Delta\omega$ | 15 kHz: 0.04 $\text{s}^{-1}$
30 kHz: 0.08 $\text{s}^{-1}$ | 15 kHz: 0.13 $\text{s}^{-1}$
30 kHz: 0.26 $\text{s}^{-1}$ | 15 kHz: 0.18 $\text{s}^{-1}$
30 kHz: 0.36 $\text{s}^{-1}$ | + +NOTE: Doppler shift is not taken into account in UL TA scenario Y and scenario Z. + +--- + +## Annex H (normative): In-channel TX tests + +### H.1 General + +The in-channel TX test enables the measurement of all relevant parameters that describe the in-channel quality of the output signal of the TX under test in a single measurement process. + +The parameters describing the in-channel quality of a transmitter, however, are not necessarily independent. The algorithm chosen for description inside this annex places particular emphasis on the exclusion of all interdependencies among the parameters. + +--- + +### H.2 Basic principles + +The process is based on the comparison of the actual output signal of the TX under test, received by an ideal receiver, with an ideal signal, that is generated by the measuring equipment and represents an ideal error free received signal. All signals are represented as equivalent (generally complex) baseband signals. + +The description below uses numbers and illustrations as examples only. These numbers are taken from a FDD frame structure with normal CP length, 30 kHz SCS and a transmission bandwidth configuration of 100 MHz ( $N_{RB}=273$ ). The application of the text below, however, is not restricted to this parameter set. + +#### H.2.1 Output signal of the TX under test + +The output signal of the TX under test is acquired by the measuring equipment and stored for further processing. It is sampled at a sampling rate which is the product of the SCS and the *FFT size*, and it is named $s_{TX}$ . The *FFT size* is determined by the transmission bandwidth in table 6.5.3.5-2 for 15 kHz SCS, table 6.5.3.5-3 for 30 kHz SCS and table 6.5.3.5-4 for 60 kHz SCS. In the time domain, it comprises at least 10 ms. It is modelled as a signal with the following parameters: + +- demodulated data content, +- carrier frequency, +- amplitude and phase for each subcarrier. + +For the example in the annex, the *FFT size* is 4096 based on table 6.5.3.5-3. The sampling rate of 122.88 Msps is the product of the *FFT size* and SCS. + +#### H.2.2 Ideal signal + +Two types of ideal signals are defined: + +The first ideal signal is constructed by the measuring equipment according to the relevant TX specifications, using the following parameters: + +- demodulated data content, +- nominal carrier frequency, +- nominal amplitude and phase for each subcarrier. + +It is represented as a sequence of samples at the sampling rate determined from annex H.2.1 in the time domain. The structure of the signal is described in the test models. + +The second ideal signal is constructed by the measuring equipment according to the relevant TX specifications, using the following parameters: + +- nominal demodulation reference signals (all other modulation symbols are set to 0 V), +- nominal carrier frequency, +- nominal amplitude and phase for each applicable subcarrier, +- nominal timing. + +It is represented as a sequence of samples at the sampling rate determined from annex H.2.1 in the time domain. + +## H.2.3 Measurement results + +The measurement results, achieved by the in-channel TX test are the following: + +- Carrier frequency error +- EVM +- Resource element TX power + - OFDM symbol TX power (OSTP) + +Other side results are: residual amplitude- and phase response of the TX chain after equalisation. + +## H.2.4 Measurement points + +The resource element TX power is measured after the FFT box as described in figure H.2.4-1. The EVM shall be measured at the point after the FFT and a zero-forcing (ZF) equalizer in the receiver, as depicted for FR1 in figure H.2.4-1. The FFT window of *FFT size* samples out of (*FFT size* + cyclic prefix length) samples in the time domain is selected in the "Remove CP" box. The *FFT size* and the cyclic prefix length are obtained from table 6.5.3.5-2 for 15 kHz SCS, table 6.5.3.5-3 for 30 kHz SCS and table 6.5.3.5-4 for 60 kHz SCS. + +In one subframe, there are two symbols with the length of the cyclic prefix larger than the values listed in tables 6.5.3.5-2, 6.5.3.5-3 and 6.5.3.5-4. Table H.2.4-1 lists the slot number and the symbol number and the formula how to compute the length of cyclic prefix for those two symbols according to the sampling rate. + +**Table H.2.4-1: Slot number and symbol number identifying the longer CP length for normal CP** + +| SCS (kHz) | # slots in subframe | Symbol # and slot # with longer CP | Longer CP length | +|-----------|---------------------|------------------------------------------|-----------------------------------| +| 15 | 1 | (symbol 0, slot 0)
(symbol 7, slot 0) | CP length + FFT size / 128 | +| 30 | 2 | (symbol 0, slot 0)
(symbol 0, slot 1) | CP length + FFT size / 64 | +| 60 | 4 | (symbol 0, slot 0)
(symbol 0, slot 2) | CP length + FFT size / 32 | + +For the example used in the annex, the "Remove CP" box selects 4096 samples out of 4384 samples. Symbol 0 has 64 more samples in the cyclic prefix than the other 13 symbols in the slot (the longer CP length = 352). + +![Figure H.2.4-1: Reference point for FR1 EVM measurements. The diagram shows a signal flow from BS TX to Remove CP, then to FFT, then to Per-subcarrier Amplitude/phase correction, and finally to Symbol detection/decoding. A box labeled 'Pre-/post FFT time / frequency synchronization' has dashed arrows pointing to the Remove CP, FFT, and Per-subcarrier Amplitude/phase correction blocks. A dashed arrow from a box labeled 'Reference point for EVM measurement' points to the Per-subcarrier Amplitude/phase correction block.](3b5dee61a2394578df7e680b9a098fa7_img.jpg) + +``` + +graph LR + BS_TX[BS TX] --> Remove_CP[Remove CP] + Remove_CP --> FFT[FFT] + FFT --> Per_subcarrier[Per-subcarrier Amplitude/phase correction] + Per_subcarrier --> Symbol_detection[Symbol detection/decoding] + Sync[Pre-/post FFT time / frequency synchronization] -.-> Remove_CP + Sync -.-> FFT + Sync -.-> Per_subcarrier + Ref[Reference point for EVM measurement] -.-> Per_subcarrier + +``` + +Figure H.2.4-1: Reference point for FR1 EVM measurements. The diagram shows a signal flow from BS TX to Remove CP, then to FFT, then to Per-subcarrier Amplitude/phase correction, and finally to Symbol detection/decoding. A box labeled 'Pre-/post FFT time / frequency synchronization' has dashed arrows pointing to the Remove CP, FFT, and Per-subcarrier Amplitude/phase correction blocks. A dashed arrow from a box labeled 'Reference point for EVM measurement' points to the Per-subcarrier Amplitude/phase correction block. + +**Figure H.2.4-1: Reference point for FR1 EVM measurements** + +## H.3 Pre-FFT minimization process + +Sample Timing, Carrier Frequency in are varied in order to minimise the difference between and , after the amplitude ratio of and has been scaled. Best fit (minimum difference) is achieved when the RMS difference value between and is an absolute minimum. + +The carrier frequency variation is the measurement result: carrier frequency error. + +From the acquired samples, one value of carrier frequency error can be derived. + +- Note 1: The minimisation process, to derive the RF error can be supported by post-FFT operations. However the minimisation process defined in the pre-FFT domain comprises all acquired samples (i.e. it does not exclude the samples inbetween the FFT widths and it does not exclude the bandwidth outside the transmission bandwidth configuration). +- Note 2: The algorithm would allow to derive carrier frequency error and sample frequency error of the TX under test separately. However there are no requirements for sample frequency error. Hence the algorithm models the RF and the sample frequency commonly (not independently). It returns one error and does not distinguish between both. + +After this process, the samples are called . + +## H.4 Timing of the FFT window + +The FFT window length is *FFT size* samples per OFDM symbol. For FDD, there are FFTs performed where is the number of slots in a 10 ms measurement interval, and the number of symbols in a slot for normal CP is 14. + +The position in time for the FFT shall be determined. + +For the example used in the annex, the FFT window length is 4096 samples per OFDM symbol. 280 FFTs (i.e. 1,146,880 samples) cover less than the acquired number of samples (i.e. 1,228,800 samples in 10 ms). + +In an ideal signal, the FFT may start at any instant within the cyclic prefix without causing an error. The TX filter, however, reduces the window. The EVM requirements shall be met within a window $W < CP$ . There are three different instants for FFT: + +- Centre of the reduced window, called $t_{FFT}$ , +- $t_{CP}$ , and +- $t_{data}$ . + +The value of EVM window length $W$ is obtained from tables 6.5.3.5-2 for 15 kHz SCS, 6.5.3.5-3 for 30 kHz SCS and 6.5.3.5-4 for 60 kHz SCS and the transmission bandwidth. + +The BS shall transmit a signal according to the test models intended for EVM. The demodulation reference signal of the second ideal signal shall be used to find the centre of the FFT window. + +The timing of the measured signal is determined in the pre-FFT domain as follows, using $t_{CP}$ and $t_{data}$ : + +1. The measured signal is delay spread by the TX filter. Hence the distinct borders between the OFDM symbols and between data and CP are also spread and the timing is not obvious. +2. In the ideal signal $t_{CP}$ , the timing is known. + +Correlation between bullet (1) and (2) will result in a correlation peak. The meaning of the correlation peak is approximately the "impulse response" of the TX filter. + +3. The meaning of "impulse response" assumes that the autocorrelation of the ideal signal $t_{CP}$ is a Dirac peak and that the correlation between the ideal signal $t_{data}$ and the data in the measured signal is 0. The correlation peak, (the highest, or in case of more than one highest, the earliest) indicates the timing in the measured signal. + +The number of samples used for FFT is reduced compared to $N_{FFT}$ . This subset of samples is called $N_{FFT,red}$ . + +From the acquired samples one timing can be derived. + +The timing of the centre $t_{FFT}$ is determined according to the cyclic prefix length of the OFDM symbols. For normal CP, there are two values for $t_{FFT}$ in a 1 ms period: + +- $t_{FFT} = \text{length of cyclic prefix} / 2$ , +- $t_{FFT} = \text{Longer CP length} - \text{length of cyclic prefix} / 2$ , + +Where the length of cyclic prefix is obtained from table 6.5.3.5-2 for 15 kHz SCS, table 6.5.3.5-3 for 30 kHz SCS and table 6.5.3.5-4 for 60 kHz SCS, and the longer CP length is obtained from table H.2.4-1. + +As per the example values: + +- $t_{FFT} = 144$ within the CP of length 288 for OFDM symbols 1 to 13 of a slot, +- $t_{FFT} = 208 (= 352 - 144)$ within the CP of length 352 for OFDM symbol 0 of a slot. + +## H.5 Resource element TX power + +Perform FFT on $s_{measured}$ with the FFT window timing $t_{FFT}$ . The result is called $S_{FFT}$ . The RE TX power (RETP) is then defined as: + +Where SCS is the subcarrier spacing in Hz. + +From RETP the OFDM Symbol TX power (OSTP) is derived as follows: + +Where the summation accumulates RETP values of all $N_{sym}$ OFDM symbols that carry PDSCH and not containing PDCCH, RS or SSB within a slot. + +From the acquired samples, values for each OSTP can be obtained and averaged where $N$ is the number of slots in a 10 ms measurement interval for FDD. For TDD, $N$ is the number of slots with downlink symbols in a 10 ms measurement interval and is computed according to the values in table 4.9.2.2-1. + +For the example used in the annex, $N = 10$ . + +## H.6 Post-FFT equalisation + +Perform FFTs on $s$ , one for each OFDM symbol within 10 ms measurement interval with the FFT window timing to produce an array of samples, $s_f$ in the time axis $t$ by *FFT size* in the frequency axis $f$ . + +For the example in the annex, 280 FFTs are performed on $s$ . The result is an array of samples, 280 in the time axis by 4096 in the frequency axis. + +The equalizer coefficients $\hat{h}_f$ and $\hat{p}_f$ are determined as follows: + +1. Calculate the complex ratios (amplitude and phase) of the post-FFT acquired signal and the post-FFT ideal signal for each demodulation reference signal, over 10 ms measurement interval. This process creates a set of complex ratios: +2. Perform time averaging at each demodulation reference signal subcarrier of the complex ratios, the time-averaging length is 10 ms measurement interval. Prior to the averaging of the phases an unwrap operation must be performed according to the following definition: + - The unwrap operation corrects the radian phase angles of $\hat{p}_f$ by adding multiples of $2 * \pi$ when absolute phase jumps between consecutive time instances are greater than or equal to the jump tolerance of $\pi$ radians. + - This process creates an average amplitude and phase for each demodulation reference signal subcarrier (i.e. every second subcarrier). + +and + +Where $N$ is the number of demodulation reference signals time-domain locations from $s$ for each demodulation reference signal subcarrier $f$ . + +3. The equalizer coefficients for amplitude and phase $\hat{h}_f$ and $\hat{p}_f$ at the demodulation reference signal subcarriers are obtained by computing the moving average in the frequency domain of the time-averaged demodulation reference signal subcarriers. The moving average window size is 19 and averaging is over the DM-RS subcarriers in the allocated RBs. For DM-RS subcarriers at or near the edge of the channel, or when the number of available DM-RS subcarriers within a set of contiguously allocated RBs is smaller than the moving average window size, the window size is reduced accordingly as per figure H.6-1. +4. Perform linear interpolation from the equalizer coefficients $\hat{h}_f$ and $\hat{p}_f$ to compute coefficients, $\tilde{h}_f$ and $\tilde{p}_f$ , for each subcarrier. + +![Figure H.6-1: Reference subcarrier smoothing in the frequency domain. The figure consists of two diagrams, A and B, illustrating moving averaging of reference subcarriers. Diagram A shows the process at the channel edge, where the window size increases from 1 to 19 and then decreases back to 1. Diagram B shows the process for a case where the number of available reference subcarriers is smaller than the moving average window size.](46b1709f96fe48aa2b3395915d00a8ad_img.jpg) + +From the 10th subcarrier onwards the window size is 19 until the upper edge of the channel is reached and the window size reduces back to 1 + +The subsequent 7 subcarriers are averaged over 5, 7 .. 17 subcarriers + +The second reference subcarrier is the average of the first three subcarriers + +The first reference subcarrier is not averaged + +Reference subcarriers + +A. Moving averaging at channel edge + +Figure B shows an example of 1RB allocation using a reduced window size of five subcarriers for averaging. The same method applies for RB allocations with fewer than 19 subcarriers available for the moving average size. For the case of 2 and 3 RB allocations, 11 and 17 are the window sizes, respectively. + +The first, second and third reference subcarriers are the average of the five subcarriers on left + +The first, second and third reference subcarriers are the average of the five subcarriers on right + +Reference subcarriers + +B. Moving averaging for the case when the number of available reference subcarriers within a set of contiguously allocated RBs is smaller than the moving average window size + +Figure H.6-1: Reference subcarrier smoothing in the frequency domain. The figure consists of two diagrams, A and B, illustrating moving averaging of reference subcarriers. Diagram A shows the process at the channel edge, where the window size increases from 1 to 19 and then decreases back to 1. Diagram B shows the process for a case where the number of available reference subcarriers is smaller than the moving average window size. + +Figure H.6-1: Reference subcarrier smoothing in the frequency domain + +## H.7 EVM + +### H.7.0 General + +For EVM create two sets of $\hat{s}_{t,k}$ , according to the timing $t$ and $k$ , using the equalizer coefficients from H.6. + +The equivalent ideal samples are calculated from (annex H.2.2) and are called $s_{t,k}$ . + +The EVM is the difference between the ideal signal and the equalized measured signal. + +Where: + +- $T$ is the set of symbols with the considered modulation scheme being active within the slot, +- $k$ is the set of subcarriers within the resource blocks with the considered modulation scheme being active in symbol $t$ , +- $s_{t,k}$ is the ideal signal reconstructed by the measurement equipment in accordance with relevant test models, +- $\hat{s}_{t,k}$ is the equalized signal under test. + +NOTE: Although the basic unit of measurement is one slot, the equalizer is calculated over the entire 10 ms measurement interval to reduce the impact of noise in the reference signals. + +## H.7.1 Averaged EVM (FDD) + +EVM is averaged over all allocated downlink resource blocks with the considered modulation scheme in the frequency domain, and a minimum of $N$ slots where $N$ is the number of slots in a 10 ms measurement interval. The averaging in the time domain equals the slot duration of the 10 ms measurement interval from the equalizer estimation step. + +Where $N_i$ is the number of resource blocks with the considered modulation scheme in slot $i$ . + +The EVM requirements shall be tested against the maximum of the RMS average at the window $W$ extremities of the EVM measurements: + +Thus $EVM_{RMS}$ is calculated using $EVM_{i,j}$ in the expressions above and $EVM_{RMS}$ is calculated using $EVM_{RMS}$ in the calculation where ( $l$ and $h$ , low and high; where low is the timing $t_{low}$ and high is the timing $t_{high}$ ). + +Thus: + +The resulting $EVM_{RMS}$ is compared against the limit. + +## H.7.2 Averaged EVM (TDD) + +Let $N$ be the number of slots with downlink symbols within a 10 ms measurement interval. For TDD, the averaging in the time domain can be calculated from $N$ slots of different 10 ms measurement intervals and should have a minimum of $N$ slots averaging length where $N$ is the number of slots in a 10 ms measurement interval. + +$EVM_{RMS}$ is derived by: Square the EVM results in each 10 ms measurement interval. Sum the squares, divide the sum by the number of EVM relevant locations, square-root the quotient (RMS). + +Where $N_i$ is the number of resource blocks with the considered modulation scheme in slot $i$ . + +The $EVM_{RMS}$ is calculated, using the maximum of $EVM_{RMS}$ at the window $W$ extremities. Thus $EVM_{RMS}$ is calculated using $EVM_{RMS}$ in the calculation where ( $l$ and $h$ , low and high; where low is the timing $t_{low}$ and high is the timing $t_{high}$ ). + +In order to unite at least $N$ slots, consider the minimum integer number of 10 ms measurement intervals, where $N$ is determined by. + +and for 15 kHz SCS, $N = 10$ ; for 30 kHz SCS and $N = 20$ for 60 kHz SCS normal CP. + +Unite by RMS. + +The resulting $EVM_{RMS}$ is compared against the limit. + +--- + +## Annex I (normative): General rules for statistical testing + +### I.1 Testing methodology of PUSCH performance requirements with 0.001% BLER + +#### I.1.1 General + +The test framework for the 0.001% BLER test is based upon examining received blocks and determining pass, fail or continue each time a block error occurs. + +The pass/fail decision is made based on so-called decision co-ordinates ( $n_e$ , $n_s$ ). $n_e$ is the number of block errors encountered during the test and $n_s$ is the total number of received blocks during the test, up to the current block error. The $n_s$ is compared with the $n_{sp}$ and $n_{sf}$ entries corresponding to $n_e$ in table I.1.1-1. If $n_s$ is greater than the $n_{sp}$ value in I.1.1-1, a pass may be declared. If $n_s$ is lower than the $n_{sf}$ value, a fail may be declared. Otherwise, the test continues. + +The objective of the approach is to minimize testing time and the basis of the approach is an early termination statistical framework described in clause I.1.3.1. The minimum testing time is defined by the possible decision coordinates detailed in clause I.1.2. + +As with all statistical tests, there is a non-zero risk of the test result being incorrect due to statistical variations. There are two possibilities for an incorrect decision: + +- As BS, whose BLER is greater than the requirement (i.e., the BS does not comply to the requirement), is declared to pass the test. +- A BS, whose BLER is lower than the requirement (i.e., a BS that does comply to the requirement), is declared to fail the test. + +The outcome of the statistical test is a decision. This decision may be correct with confidence level of 99.999%, i.e., BSs whose BLER is greater than 0.001% being declared to fail, and BSs whose BLER is smaller or equal to 0.001% being declared to pass, or in-correct (as detailed above). + +## I.1.2 Numerical definition of the pass-fail limits for testing PUSCH 0.001% BLER + +**Table I.1.2-1: Pass fail limits** + +| ne | ns p | ns f | ne | ns p | ns f | ne | ns p | ns f | +|----|-----------------|-----------------|----|-----------------|-----------------|-----------------------------|-----------------|-----------------| +| 0 | 1074532 | 1067 | 39 | 5369517 | 1508043 | (*) | (*) | (*) | +| 1 | 1074532 | 1067 | 40 | 5463478 | 1568438 | 608 | 49669522 | 49113220 | +| 2 | 1274645 | 1067 | 41 | 5557107 | 1629304 | 609 | 49743206 | 49202955 | +| 3 | 1444583 | 1067 | 42 | 5650414 | 1690627 | 610 | 49816884 | 49292699 | +| 4 | 1599072 | 4727 | 43 | 5743410 | 1752389 | 611 | 49890556 | 49382451 | +| 5 | 1743641 | 12160 | 44 | 5836108 | 1814577 | 612 | 49964222 | 49472211 | +| 6 | 1881111 | 23683 | 45 | 5928516 | 1877177 | 613 | 50037883 | 49561980 | +| 7 | 2013164 | 39190 | 46 | 6020643 | 1940175 | 614 | 50111538 | 49651757 | +| 8 | 2140902 | 58403 | 47 | 6112500 | 2003560 | 615 | 50185187 | 49741542 | +| 9 | 2265092 | 81000 | 48 | 6204094 | 2067319 | 616 | 50258831 | 49831335 | +| 10 | 2386297 | 106667 | 49 | 6295434 | 2131442 | 617 | 50332469 | 49921137 | +| 11 | 2504945 | 135116 | 50 | 6386526 | 2195916 | 618 | 50406101 | 50010947 | +| 12 | 2621369 | 166089 | 51 | 6477380 | 2260734 | 619 | 50479728 | 50100765 | +| 13 | 2735834 | 199360 | 52 | 6568000 | 2325884 | 620 | 50553349 | 50190592 | +| 14 | 2848557 | 234730 | 53 | 6658395 | 2391358 | 621 | 50626965 | 50280427 | +| 15 | 2959718 | 272025 | 54 | 6748569 | 2457146 | 622 | 50700575 | 50370269 | +| 16 | 3069467 | 311091 | 55 | 6838530 | 2523241 | 623 | 50774179 | 50460120 | +| 17 | 3177931 | 351792 | 56 | 6928283 | 2589634 | 624 | 50847778 | 50549980 | +| 18 | 3285220 | 394009 | 57 | 7017834 | 2656318 | 625 | 50921372 | 50639847 | +| 19 | 3391428 | 437636 | 58 | 7107187 | 2723285 | 626 | 50994959 | 50729722 | +| 20 | 3496637 | 482577 | 59 | 7196348 | 2790528 | 627 | 51068542 | 50819605 | +| 21 | 3600921 | 528746 | 60 | 7285321 | 2858041 | 628 | 51142119 | 50909497 | +| 22 | 3704343 | 576068 | 61 | 7374112 | 2925816 | 629 | 51215690 | 50999396 | +| 23 | 3806960 | 624473 | 62 | 7462724 | 2993848 | 630 | 51289256 | 51089304 | +| 24 | 3908823 | 673898 | 63 | 7551162 | 3062130 | 631 | 51362816 | 51179219 | +| 25 | 4009977 | 724286 | 64 | 7639430 | 3130657 | 632 | 51436371 | 51269143 | +| 26 | 4110465 | 775585 | 65 | 7727532 | 3199424 | 633 | 51509921 | 51359074 | +| 27 | 4210324 | 827748 | 66 | 7815471 | 3268424 | 634 | 51583465 | 51449013 | +| 28 | 4309587 | 880730 | 67 | 7903252 | 3337653 | 635 | 51657003 | 51538961 | +| 29 | 4408285 | 934492 | 68 | 7990878 | 3407105 | 636 | 51730537 | 51628916 | +| 30 | 4506448 | 988997 | 69 | 8078352 | 3476777 | 637 | 51804065 | 51718879 | +| 31 | 4604101 | 1044211 | 70 | 8165677 | 3546663 | 638 | 51877587 | 51808850 | +| 32 | 4701268 | 1100101 | 71 | 8252857 | 3616759 | 639 | 51951104 | 51898828 | +| 33 | 4797972 | 1156638 | 72 | 8339894 | 3687060 | 640 | 52024616 | 51988815 | +| 34 | 4894232 | 1213795 | 73 | 8426792 | 3757563 | 641 | 52098123 | 52078809 | +| 35 | 4990069 | 1271547 | 74 | 8513553 | 3828263 | 642 | 52171624 | 52168811 | +| 36 | 5085500 | 1329869 | 75 | 8600181 | 3899156 | | | | +| 37 | 5180542 | 1388740 | 76 | 8686677 | 3970239 | | | | +| 38 | 5275209 | 1448137 | 77 | 8773044 | 4041508 | *) Follow I.1.3.2 to derive | | | + +NOTE 1: The first column is the number of errors (ne = number of NACK) + +NOTE 2: The second column is the number of samples for the pass limit (nsp, ns=Number of Samples= number of NACK + ACK) + +NOTE 3: The third column is the number of samples for the fail limit (nsf) + +NOTE 4: An ideal DUT passes after 1074532 samples. The maximum test time is 52171625 samples. A DUT passes, if the maximum number of samples is reached and it did not fail before. + +## I.1.3 Theory to derive the early pass/fail limits in I.1.2 (informative) + +**Editor's note:** This clause of the Annex I is for information only and it describes the background theory and information for statistical testing. + +### I.1.3.1 Numerical definition of the pass-fail limits for testing PUSCH 0.001% BLER + +A statistical test is characterized by test time, selectivity and confidence level. The outcome of the statistical test is a decision. This decision may be correct, i.e., BSs whose BLER is greater than 0.001% being declared to fail, and BSs whose BLER is smaller or equal to 0.001% being declared to pass, or in-correct (as detailed above). The Confidence Level (CL) describes the probability that the decision is a correct one. The complement is the wrong decision probability (risk) $D = 1 - CL$ . + +When testing BLER, transport blocks or "samples" are observed and the numbers of correctly and erroneously received blocks are recorded. For a "standard" test, a pre-defined number of samples are observed, and a pass/fail decision is made based on the number of observed errors being above/below a threshold. This threshold is based on the targeted BLER and the design target CL. There is always some risk of a statistical variation leading to an incorrect pass/fail decision. The greater the number of samples that are recorded, the lower is the risk of such an error. The number of samples that are observed in a standard test is dimensioned to achieve an acceptable low risk of error (i.e., an acceptable high confidence level) for BS that just meet the BLER limit. + +The standard test works well where the BLER level is relatively high and confidence level relatively low (both are chosen to be on a comparable order of magnitude). However, for ultra-low BLER testing the length of time required for observing sufficient samples to achieve a 99.999% confidence level is excessive. In many cases, the BS will in fact have a much lower true BLER than the limit, i.e., design target of the test, (in which case, the number of samples needed to achieve high confidence that the BLER is lower than the limit is much smaller) or, if failing the requirement will have a much higher true BLER (in which case, errors occur more frequently and it can be demonstrated that the BS is above the BLER limit with fewer samples). + +To avoid long test times, an alternative test method called early pass/fail is adopted. With the early pass/fail, each time a block error is encountered, a decision is made on whether the BS can be passed/failed with 99.999% CL or the test needs to continue until another error is encountered. In the case of very good BSs, the test can also be passed, when the number of samples permissible for one error event is reached and no error event is recorded. Pass/Fail is decided based on the total number of observed samples and errors, and a statistical calculation based on an inverse binomial cumulative distribution. The calculation involves one parameter, one variable and the result: + +- Parameter: $d$ (per step decision probability). +- Variable: $n_e$ (number of observed errors). +- Result: $n_s$ (number of expected samples for pass/fail, depending on which one is calculated). + +The per step decision probability risk, $d$ , expresses the probability of making an incorrect pass/fail decision in the current step (i.e., for the current decision coordinate). $d$ is determined by simulation such that the overall risk of making a wrong decision over all steps of each test of a large number of tests on a large number of BSs that exactly meet the BLER limit is $D=0.001\%$ (and hence the CL 99.999%). + +It should be noted that $d$ is determined separately considering early pass and early fail testing. + +For a marginal BS (i.e., a BS almost exactly meeting the BLER), the unmodified early pass/early fail approach is unable to distinguish whether the BS has just passed or just failed the BLER ( $\epsilon \rightarrow 0$ ), and can thus terminate with an "undecided" result. To avoid this undecided result and provide selectivity, a so-called "bad device factor" ( $M$ ) is introduced into the early pass calculation. This factor biases the decision towards avoiding failing good BS. + +### I.1.3.2 Simulation to derive the pass-fail limits for testing PUSCH 0.001% BLER + +There is freedom to design the decision co-ordinates (ne, ns), as captured in clause I.1.2. + +The binomial distribution and its inverse are used to design the pass and fail limits. Note that this method is not unique and that other methods exist. + +$$\text{fail}(ne, d_f) := \frac{ne}{ns_f} = \frac{ne}{(ne + \text{qnbinom}(d_f, ne, ER))}$$ + +$$\text{pass}(ne, cl_p, M) := \frac{ne}{ns_p} = \frac{ne}{(ne + \text{qnbinom}(cl_p, ne, ER \cdot M))}$$ + +Where + +- $\text{fail}(\dots)$ is the error ratio for the fail limit. +- $\text{pass}(\dots)$ is the error ratio for the pass limit. +- ER is the specified error ratio $1e-5$ . +- ne is the number of bad results. This is the variable in both equations. +- M is the Bad DUT factor $M=1.5$ . +- $d_f$ is the wrong decision probability of a single (ne, ns) co-ordinate for the fail limit. It is found by simulation to be $d_f = 2e-7$ . +- $cl_p$ is the confidence level of a single (ne, ns) co-ordinate for the pass limit. It is found by simulation to be $cl_p = 0.9999999$ . +- $\text{qnbinom}(\dots)$ : The inverse cumulative function of the negative binomial distribution. + +The simulation works as follows: + +- A large population of limit DUTs with true ER = $1e-5$ is decided against the pass and fail limits. +- $cl_p$ and $d_f$ are tuned such that CL (99.999 %) of the population passes and D (0.001 %) of the population fails. +- A population of Bad DUTs with true ER = $M \cdot 1e-5$ is decided against the same pass and fail limits. +- $cl_p$ and $d_f$ are tuned such that CL (99.999 %) of the population fails and D (0.001 %) of the population passes. +- The number of DUTs decrease during the simulation, as the decided DUTs leave the population. That number decreases with an approximately exponential characteristics. After 642 bad results all DUTs of the population are decided. + +NOTE: The exponential decrease of the population is an optimal design goal for the decision co-ordinates (ne, ns), which can be achieved with other formulas or methods as well. + +## Annex J (informative): Change history + +| Change history | | | | | | | | +|----------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|------|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Re v | Cat | Subject/Comment | New version | +| 2017-11 | RAN4#84 bis | R4-1711982 | - | - | - | TS skeleton | 0.0.1 | +| 2018-04 | RAN4#86 bis | R4-1803913 | - | - | - | R4-1803410 Draft CR to TS 38.141-1: Addition of applicability table in clause 4.7
R4-1803411 TP to TS 38.141-1 Applicability of requirements clause (4.7) | 0.1.0 | +| 2018-04 | RAN4#86 bis | R4-1805424, R4-1806022 | - | - | - | Implementation of TPs agreed during RAN4#86bis, on top of the agreed R4-1803913:
- R4-1805424 TP to TS 38.141-1 v0.1.0 Clauses 1-3
- R4-1806022 TP to TS 38.141-1 v0.1.0 Clause 4 | 0.2.0 | +| 2018-06 | RAN4#87 | R4-1808321, R4-1808322, R4-1808324, R4-1808326, R4-1808482 | - | - | - | Implementation of TPs agreed during RAN4#87, on top of R4-1807254:
- R4-1808321 TP to TS 38.141-1: conducted manufacturers declarations for NR BS (4.6)
- R4-1808322 TP to TS 38.141-1: removal of OTA terms and definitions
- R4-1808324 TP to TS 38.141-1: NR channel numbering correction
- R4-1808326 TP to TS 38.141-1: Correction of the BS type 1-H architecture figure
- R4-1808482 TP to TS 38.141-1: multi-band operation | 0.3.0 | +| 2018-07 | RAN4-AH-1807 | R4-1808980, R4-1808981, R4-1808987, R4-1808991, R4-1808992, R4-1808994, R4-1808995, R4-1808997, R4-1809464, R4-1809469, R4-1809470, R4-1809471, R4-1809472, R4-1809474, R4-1809475, R4-1809476, R4-1809478, R4-1809479, R4-1809481, R4-1809482, R4-1809483, R4-1809484, R4-1809558, R4-1809560, R4-1809563, R4-1809564 | - | - | - | Implementation of TPs approved during RAN4-AH-1807, on top of R4-1809264 (TS 38.141-1, v0.3.0):
- R4-1808980 TP to TS 38.141-1: Conducted TAE requirements (6.5.4)
- R4-1808981 TP to TS 38.141-1: General clause for unwanted emission requirements (6.6.1)
- R4-1808987 TP to TS 38.141-1: General (7.1)
- R4-1808991 TP to TS 38.141-1: Out-of-band blocking (7.5)
- R4-1808992 TP to TS 38.141-1: Receiver spurious emissions (7.6)
- R4-1808994 TP to TS 38.141-1: In-channel selectivity (7.8)
- R4-1808995 TP to TS 38.141-1: Environmental requirements for the BS equipment (Annex B)
- R4-1808997 TP to TS 38.141-1: General clauses (1-5)
- R4-1809464 TP to TS 38.141-1 - 4.7 Test Configurations
- R4-1809469 TP to TS 38.141-1: MU and TT for NR BS
- R4-1809470 TP to TS 38.141-1: Applicability of test configurations
- R4-1809471 TP to TS 38.141-1: Conducted BS output power requirements (6.2)
- R4-1809472 TP to TS 38.141-1: Conducted output power dynamics requirements (6.3)
- R4-1809474 TP to TS 38.141-1: Frequency error (6.5.2)
- R4-1809475 TP to TS 38.141-1: Modulation quality (6.5.3)
- R4-1809476 TP to TS 38.141-1: Conducted ACLR requirements (6.6.3)
- R4-1809478 TP to TS 38.141-1: Conducted Tx spurious emission requirements (6.6.5)
- R4-1809479 TP to TS 38.141-1: Conducted Tx IMD requirements (6.7)
- R4-1809481 TP to TS 38.141-1: Reference sensitivity level (7.2)
- R4-1809482 TP to TS 38.141-1: Dynamic range (7.3)
- R4-1809483 TP to TS 38.141-1: In-band selectivity and blocking (7.4)
- R4-1809484 TP to TS 38.141-1: Receiver intermodulation (7.7)
- R4-1809558 TP to TS 38.141-1: General clause for conducted Tx requirements (6.1)
- R4-1809560 TP to TS 38.141-1: Transmit ON/OFF power (6.4) | 0.4.0 | + +| | | | | | | | | +|---------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| | | | | | | - R4-1809563 TP to TS 38.141-1: NR BS conducted declarations corrections
- R4-1809564 TP for TS38.141-1: Occupied bandwidth (clause 4.1.2 and 6.7.2) | | +| 2018-08 | RAN4#88 | R4-1809711,
R4-1810355,
R4-1810813,
R4-1810814,
R4-1810825,
R4-1811537,
R4-1811617,
R4-1811622,
R4-1811625,
R4-1811627,
R4-1811628,
R4-1811630,
R4-1811631,
R4-1811632,
R4-1811761,
R4-1811764,
R4-1811765,
R4-1811843 | - | - | - | Implementation of TPs approved during RAN4#88, on top of R4-1810575 (TS 38.141-1, v0.4.0):
- R4-1809711 TP to TR 38.141-1: NR BS manufacturers declarations for conducted test requirements (4.6)
- R4-1810355 TP to TS 38.141-1: NR BS occupied bandwidth (6.6.2)
- R4-1810813 TP to TS 38.141-1: Operating bands and channel arrangement (5)
- R4-1810814 TP to TS 38.141-1: Requirements for contiguous and non-contiguous spectrum (4.10)
- R4-1810825 TP to TS 38.141-1: cleanup
- R4-1811537 TP for introduction of band n74 for TS38.141-1
- R4-1811617 Correction on general clause for 38.141-1
- R4-1811622 TP to TS 38.141-1 Test configuration(Clauses 4.7)
- R4-1811625 TP to TS 38.141-1: NR Test Models
- R4-1811627 TBDs on acceptable uncertainty of Test System (4.1.2)
- R4-1811628 TP to TS 38.141-1: Annex
- R4-1811630 TP to TS 38.141-1: Regional requirements (4.4)
- R4-1811631 TP to TS 38.141-1: Ancillary RF amplifiers (4.5.1.5)
- R4-1811632 TP to TS 38.141-1: 6.6.4 Operating band unwanted emissions
- R4-1811761 TP: Add parameters band n50 in TS 38.141-1
- R4-1811764 TP to TS 38.141-1: Remaining issues on conducted declarations (4.6)
- R4-1811765 TP to TS 38.141-1: Conducted declarations renumbering (4.6)
- R4-1811843 TP for TR38.141-1: RF channel for BS conducted conformance test | 0.5.0 | +| 2018-09 | RAN#81 | RP-181663 | - | - | - | Presented to TSG RAN for information. | 1.0.0 | +| 2018-11 | RAN4#88 bis | R4-1812583
R4-1812675
R4-1812676
R4-1812680
R4-1813307
R4-1813531
R4-1813535
R4-1813746
R4-1813748
R4-1813750
R4-1813751
R4-1813752
R4-1813753
R4-1813876
R4-1813880
R4-1813886
R4-1813887
R4-1813888
R4-1813889
R4-1813891
R4-1813892
R4-1813893
R4-1813894
R4-1814063
R4-1814119
R4-1814178 | - | - | - | Implementation of TPs approved during RAN4#88bis, on top of RP-181663 (TS 38.141-1, v1.0.0):
- R4-1812583 TP to TS 38.141-1: Correction on NOTE for wanted signal mean power for NR BS RX requirements
- R4-1812675 TP to TS 38.141-1: Update on MU and TT
- R4-1812676 TP to TS 38.141-1: Correction on reference sensitivity level
- R4-1812680 TP to TS 38.141-1: Clarification Note on non-zero Test Tolerance
- R4-1813307 TP to TS 38.141-1: connecting network loss declaration for BS type 1-C
- R4-1813531 TP to TS 38.141-1: Corrections to Modulation quality test in Clause 6.5.3
- R4-1813535 TP to TS 38.141-1: Correction to clause 4.7.2 Test signal used to build Test Configurations
- R4-1813746 TP to TS 38.141-1: Conducted performance requirements (8)
- R4-1813748 TP to TS 38.141-1: Conducted performance requirements for DFT-s-OFDM based PUSCH
- R4-1813750 TP for TS38.141-1: PUCCH format 1 conducted conformance test
- R4-1813751 Draft TP for 38.141-1 clause 8 about PUCCH formats 3 and 4 conformance testing
- R4-1813752 TP to TS38.141-1: Performance requirements for PRACH
- R4-1813753 TP to TS 38.141-1: FRC definitions for NR FR1 PUSCH demodulation requirements
- R4-1813876 TP for TS38.141-1: Adding a note for some specific requirements on RF channel
- R4-1813880 TP to TS 38.141-1: Data content for FR1
- R4-1813886 TP to TS 38.141-1: Corrections to align with 38.104 update
- R4-1813887 TP to 38.141-1: Clause 4.6 - correction for | 1.1.0 | + +| | | | | | | | | +|---------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| | | | | | | manufacturer declaration
- R4-1813888 TP to TS 38.141-1: operating bands applicable for spurious emissions testing above 12.75 GHz
- R4-1813889 TP to TS 38.141-1: Update for NR BS occupied bandwidth requirement (6.6.2)
- R4-1813891 TP to TS 38.141-1: Correction of interferer for the RX intermodulation requirement
- R4-1813892 TP to TS 38.141-1: In-channel selectivity (7.8)
- R4-1813893 TP to TS 38.141-1: Measurement system set-up and test tolerances for NR BS performance requirements
- R4-1813894 TP to TS 38.141-1: Inclusion of MU for performance requirements
- R4-1814063 TP for 38.141 on NR PUSCH test requirements with CP-OFDM and FR1
- R4-1814119 TP to TS 38.141-1: Correction on the FRCs in Annex A1 and A2
- R4-1814178 TP to TS 38.141-1: Clean up on method of test | | +| 2018-11 | RAN4#89 | R4-1815282
R4-1814435
R4-1814443
R4-1814620
R4-1815284
R4-1815292
R4-1815295
R4-1815372
R4-1815688
R4-1816273
R4-1816276
R4-1816282
R4-1816283
R4-1816284
R4-1816287
R4-1816308
R4-1816352
R4-1816355
R4-1816358
R4-1816373
R4-1816378
R4-1816442
R4-1816592
R4-1816691
R4-1816719
R4-1816724
R4-1816725
R4-1816730
R4-1816731 | - | - | - | Implementation of TPs approved during RAN4#89, on top of R4-1815276 (TS 38.141-1, v1.1.0):
- R4-1815282 TP to TS 38.141-1: Cleanup
- R4-1814435 TP to TS 38.141-1: Measurement system set-up for BS type 1-H performance requirements
- R4-1814443 TP to TS 38.141-1: FRC definitions for FR1 DFT-s-OFDM based PUSCH
- R4-1814620 TP to TS 38.141-1 on Characteristics of the interfering signals
- R4-1815284 TP to TS 38.141-1: Corrections on additional spurious emissions requirements
- R4-1815292 TP to 38.141-1: Clause 6.6.5 – correction of RF channels for test
- R4-1815295 TP to 38.141-1: Correction to Clause 7.1 Conducted receiver characteristics
- R4-1815372 TP to TS 38.141-1: Interpretation of measurement results and the Shared Risk principle
- R4-1815688 TP to 38.141-1: Out-of-band blocking co-location requirement (7.5)
- R4-1816273 TP to TS 38.141-1: Transmit ON/OFF power (Clause 6.4)
- R4-1816276 TP to TS 38.141-1: Remaining annexes
- R4-1816282 TP to TS 38.141-1 on manufacturer declarations for NR conducted requirements testing
- R4-1816283 TP to TS 38.141-1: On Applicability of test configurations
- R4-1816284 TP to TS 38.141-1: Correction to description of ACLR test limits
- R4-1816287 TP to TS 38.141-1: Addition of declaration of TAB connectors used for demodulation testing
- R4-1816308 TP to TS 38.141-1 Corrections on transmitter intermodulation (clause 3.2 and 6.7)
- R4-1816352 TP to TS 38.141-1: Update of AWGN power level and FRC index for DFT-s-OFDM based PUSCH demodulation requirements
- R4-1816355 TP for TS 38.141-1 on NR PUCCH format2 conducted performance requirements
- R4-1816358 TP to TS38.141-1: Performance requirements for PRACH
- R4-1816373 TP for 38.141-1 on PUSCH requirements with CP-OFDM and FR1
- R4-1816378 TP for introducing propagation conditions in TS 38.141-1
- R4-1816442 TP to TS 38.141-1: Cleanup to conducted requirements text
- R4-1816592 TP to TS 38.141-1: PUCCH format 0 requirement testing
- R4-1816691 TP for TS38.141-1 conductive requirements for PUCCH format 1 performance
- R4-1816719 TP for updating 38.141-1 clause 8 about PUCCH | 1.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|--|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| | | | | | | formats 3 and 4 conformance testing
- R4-1816724 TP for TS38.141-1 base conformation test models (Clause 4.9.2.2)
- R4-1816725 TP to TS 38.141-1: 4.9.2.3 Data content of Physical channels and Signals for NR-FR1-TM
- R4-1816730 TP to TS38.141-1: total power dynamic range(Clause 6.3.3)
- R4-1816731 TP to TS 38.141-1: transmitted signal quality (Clause 6.5) | | +| 2018-12 | RAN#82 | RP-182583 | | | | Presented to TSG RAN for approval. | 2.0.0 | +| 2018-12 | RAN#82 | | | | | Approved by plenary – Rel-15 spec under change control | 15.0.0 | +| 2019-03 | RAN#83 | RP-190403 | 0001 | | B | CR to TS 38.141-1

Implementation of the following draft CRs, which were Endorsed during RAN4#90, on top of v15.0.0:
- R4-1900285 Draft CR on NR PUCCH format2 conducted performance requirements for TS 38.141-1
- R4-1900390 CR to 38.141-1: Introduction of n48
- R4-1900764 Draft CR to TS 38.141-1: Update of test requirement numbers for DFT-s-OFDM based PUSCH
- R4-1900969 Draft CR for 38.141-1: Conducted test requirements for NR PUCCH format 1
- R4-1901324 Draft CR to 38.141-1: 6.3.3 Total power dynamic range - correction
- R4-1901331 Draft CR to 38.141-1: Updates for Abbreviations clause
- R4-1901373 CR to TS 38.141-1: Editorial Changes to Align Texts Throughout
- R4-1901388 Draft CR to TS 38.141-1 BS demodulation PUCCH format 0 requirements
- R4-1901475 Draft CR to TS 38.141-1: Corrections on transmitter co-existence and co-location requirements
- R4-1901484 Draft CR to TS 38.141-1: Corrections on in-band blocking requirements
- R4-1901744 DraftCR to TS 38.141-1: Removal of FR2 remainings
- R4-1901748 DraftCR to TS 38.141-1: Band 85 correction for Tx spur coexistence
- R4-1902266 DraftCR to TS 38.141-1: addition of the Iuant BS modem clause
- R4-1902269 CR to TS 38.141-1: Adding clause 4.8 reference to test procedures
- R4-1902270 Draft CR to TS 38.141-1_Correction on test procedures for single-carrier and multi-carrier operation for Tx requirements
- R4-1902292 Draft CR for TS 38.141-1: Correction on TM applicability
- R4-1902294 Corrections to 38.141-1 clause 4.9.2 base conformation test models
- R4-1902326 Draft CR to TS 38.141-1 on Correction of unwanted emissions scaling
- R4-1902342 CR to TS 38.141-1: FR frequency limit corrections
- R4-1902384 Draft CR to TS 38.141-1: Applicability rule for BS conducted demodulation test
- R4-1902390 draftCR for 38.141-1: Conducted test requirements for CP-OFDM based PUSCH in FR1
- R4-1902397 draftCR: Updates to PUCCH formats 3 and 4 conducted conformance testing in TS 38.141-1
- R4-1902400 Draft CR for updating PRACH performance requirements in TS38.141-1
- R4-1902572 Corrections to 38.141-1 Delay profile calculation
- R4-1902646 Draft CR to TS 38.141-1: Data Content of physical channels and signals for NR-FR1-TM (Clause 4.9.2.3)
- R4-1902654 DraftCR to TS 38.141-1: corrections for the single-band / multi-band connector terminology | 15.1.0 | + +| | | | | | | | | +|---------|--------|-----------|------|--|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2019-06 | RAN#84 | RP-191240 | 0007 | | B |

CR to TS 38.141-1: Implementation of endorsed draft CRs from RAN4#90bis and RAN4#91

Implementation of Draft CRs into the draft merged CR based on the endorsed tdocs during RAN4#90bis, on top of TS 38.141-1, v15.1.0:

  • - R4-1902842 Draft CR to TS 38.141-1: Removal of the square brackets on MU and TT for FR1 conducted BS demodulation test
  • - R4-1903323 Draft CR to TS 38.141-1: performance measure correction for the Rx requirements
  • - R4-1903324 Draft CR to TS 38.141-1: cleanup
  • - R4-1903330 Draft CR to TS 38.141-1: OSDD information correction
  • - R4-1903500 Draft CR to 38.141-1: Correction to unwanted emissions mask for bands n7 and n38
  • - R4-1904235 draftCR: Correlation matrix for 8Rx in TS 38.141-1
  • - R4-1904721 Draft CR to TS 38.141-1: Update of applicability rule for BS conducted demodulation test
  • - R4-1904724 Draft CR to TS 38.141-1: Update of conducted test requirements for DFT-s-OFDM based PUSCH
  • - R4-1904727 draftCR for 38.141-1: Conducted test requirements for CP-OFDM based PUSCH in FR1
  • - R4-1904730 Draft CR on PRACH performance requirements in TS38.141-1
  • - R4-1904732 Draft CR on TS 38.141-1 Conducted test requirements for PUCCH format 1
  • - R4-1904736 Draft CR on NR PUCCH format2 conducted performance requirements for TS 38.141-1
  • - R4-1904740 Draft CR to TS 38.141-1 BS demodulation PUCCH format 0 requirements
  • - R4-1904746 draftCR: Updates to PUCCH formats 3 and 4 conducted conformance testing in TS 38.141-1
  • - R4-1904798 Draft CR to TS 38.141-1 Adding required vendor declaration items for BS demodulation
  • - R4-1904802 Draft CR to TS 38.141-1: FRC update for PUSCH FR1 mapping type B
  • - R4-1904817 Draft CR: Clarification on step 5 and step 6 for delay profiles calculation (38.141-1)
  • - R4-1905121 draft CR to TS38.141-1 on test model(Clause 4.9.2)
  • - R4-1905124 draft CR to 38.141-1 for TAE requirements
  • - R4-1905141 Draft CR: editorial correction on FR1 spurious emission requirement in TS38.141-1
  • - R4-1905146 Draft CR to TS 38.141-1: Clarification on application of interfering signal offsets for ACS, blocking and intermodulation requirements
  • - R4-1905149 Draft CR to TS 38.141-1: Corrections on out-of-band blocking requirement
  • - R4-1905172 Editorial corrections to TS 38.141-1
  • - R4-1905174 Draft CR to TS 38.141-1: FRC reference corrections for the Rx requirements
  • - R4-1905176 Draft CR to TS 38.141-1: consideration of supported frequency range of the operating band
  • - R4-1905178 Draft CR to TS 38.141-1: test setup for TAE
  • - R4-1905179 Draft CR for TS 38.141-1: Addition of NOTE for transmitter intermodulation requirements in certain regions
  • - R4-1905188 draft CR to introduce n18 to TS 38.141-1
  • - R4-1905214 Corrections to TS38.141-1 clause 6.5.3.5 EVM measurement

Implementation of Draft CRs into the merged CR based on the endorsed tdocs during RAN4#91, on top of TS 38.141-1 in R4-1905215:

  • - R4-1906003 Draft CR to 38.141-1: 6.7 Transmitter intermodulation – correction of interfering signal type
  • - R4-1906312 Draft CR to 38.141-1: Correction on FRC (Annex A)
  • - R4-1906919 Draft CR to TS 38.141-1: Clarification on type of interfering signal for ACS, in-band blocking and ICS requirements
  • - R4-1907056 Draft CR to 38.141-1: Removal of n48 in Rel'15
| 15.2.0 | +|---------|--------|-----------|------|--|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| + +| | | | | | | | +|--|--|--|--|--|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | | |
  • - R4-1907111 Draft CR to TS 38.141-1: correction of the fundamental frequency limit of 2.55GHz for the spurious emissions
  • - R4-1907244 Draft CR to TS 38.141-1: Update of applicability rule for BS conducted demodulation test
  • - R4-1907247 Draft CR to TS 38.141-1: Update of conducted test requirements for DFT-s-OFDM based PUSCH
  • - R4-1907250 Draft CR to TS 38.141-1: Correction on the terminology in PUSCH FRC tables
  • - R4-1907253 Draft CR to TS38.141-1: Updates of PRACH performance requirements
  • - R4-1907256 Draft CR on NR PUCCH format2 conducted performance requirements for TS 38.141-1
  • - R4-1907259 Draft CR on NR UCI on PUSCH conducted performance requirements for TS 38.141-1
  • - R4-1907262 draftCR: Updates to PUCCH formats 3 and 4 conducted conformance testing in TS 38.141-1
  • - R4-1907264 Draft CR on TS 38.141-1 Conducted test requirements for PUCCH format 1
  • - R4-1907268 Draft CR on TS 38.141-1 Conducted test requirements for multi-slot PUCCH format 1
  • - R4-1907270 Draft CR to TS 38.141-1 Manufacturer declaration for BS demodulation
  • - R4-1907273 Draft CR to TS 38.141-1 BS demodulation PUCCH format 0 requirements
  • - R4-1907278 draftCR for 38.141-1: Conducted test requirements for CP-OFDM based PUSCH in FR1
  • - R4-1907624 Draft CR for TS38.141-1: adding demodulation reference signals for PDSCH for TAE requirement
  • - R4-1907630 Draft CR to 38.141-1: Term "reference signal" replacing by term "ideal signal" in EVM context
  • - R4-1907632 Draft CR to 38.141-1: corrections to the Annex F structure
  • - R4-1907636 Draft CR to TS38.141-1 on target resource block clarification for EVM measurement (4.9.2.2, 4.9.2.3, 6.5.3.5)
  • - R4-1907638 Draft CR to TS38.141-1: Correction on test model TM1.2, 3.2, 3.3 (4.9.2.2, 4.9.2.3)
  • - R4-1907665 Draft CR to 38.141-1: Clarification of interferer RB frequency for narrowband blocking
  • - R4-1907674 DraftCR to TS 38.141-1: removal of Rel-16 CRs from Rel-15 specification
| +|--|--|--|--|--|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2019-06 | RAN#84 | RP-191242 | 0002 | | B | CR to TS 38.141-1: Introduction of band n14 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191246 | 0003 | | B | Introduction of band n30 - CR to TS 38.141-1 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191244 | 0004 | | B | introduce n18 into TS38.141-1 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191250 | 0005 | 1 | B | n65 introduction to 38.141-1 | 16.0.0 | +| 2019-06 | RAN#84 | RP-191248 | 0006 | | B | CR to 38.141-1: Introduction of n48 | 16.0.0 | +| 2019-09 | RAN#85 | RP-192029 | 0008 | | F | CR on Protection of SUL band n89 to TS 38.141-1 | 16.1.0 | +| 2019-09 | RAN#85 | RP-192034 | 0009 | | B | n29 introduction to 38.141-1 | 16.1.0 | +| 2019-09 | RAN#85 | RP-192022 | 0011 | 1 | A | CR to TS 38.141-1: Implementation of endorsed draft CRs from RAN4#92 (Rel-16)
- Mirrors changes in R4-1910359 for Rel-15 TS 38.141-1 | 16.1.0 | +| 2019-12 | RAN#86 | RP-193000 | 0015 | 1 | A | CR to TS 38.141-1: Further update of applicability rule for BS conducted demodulation test (Rel-16) | 16.2.0 | +| 2019-12 | RAN#86 | RP-193000 | 0017 | 1 | A | CR to TS 38.141-1: Update of conducted test requirements for DFT-s-OFDM based PUSCH (Rel-16) | 16.2.0 | +| 2019-12 | RAN#86 | RP-193013 | 0018 | | B | Introduction of 2010-2025MHz SUL band into Rel-16 TS 38.141-1 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193000 | 0022 | 1 | A | CR on correction of NR PUCCH format2 conducted performance requirements (Rel-16) for TS 38.141-1 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193000 | 0024 | 1 | A | CR on correction of NR UCI on PUSCH conducted performance requirements (Rel-16) for TS 38.141-1 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193000 | 0026 | | A | CR on correction on FRC table for FR1 PUSCH conducted performance requirements (Rel-16) for TS 38.141-1 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193000 | 0028 | 1 | A | CR for 38.141-1: Conducted test requirements for CP-OFDM based PUSCH in FR1 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193000 | 0031 | | A | Updates to PRACH conducted tests in TS 38.141-1 for Rel-16 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192988 | 0034 | | A | CR for TS38.141-1: correction on NR TM1.1 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192987 | 0036 | | A | CR to TS 38.141-1: Correction on interference level of receiver dynamic range requirement | 16.2.0 | +| 2019-12 | RAN#86 | RP-192987 | 0038 | | A | CR to TS 38.141-1: Finalization of interfering RB centre frequency offsets in receiver narrowband blocking requirement | 16.2.0 | +| 2019-12 | RAN#86 | RP-192987 | 0040 | | A | CR to TS 38.141-1: Correction on interfering signal frequency offsets for receiver intermodulation requirements | 16.2.0 | +| 2019-12 | RAN#86 | RP-192987 | 0046 | | A | CR to TS38.141-1: further updates on the abbreviations (clause 3.3)-R16 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192988 | 0052 | | A | CR to 38.141-1: Annex H.5 Resource element TX power | 16.2.0 | +| 2019-12 | RAN#86 | RP-193000 | 0054 | | A | CR to TS 38.141-1 BS demodulation PUCCH format 0 requirements | 16.2.0 | +| 2019-12 | RAN#86 | RP-192987 | 0058 | 1 | A | CR to TS 38.141-1: Correcting TM 3.3 Definition | 16.2.0 | +| 2019-12 | RAN#86 | RP-192988 | 0060 | 2 | A | CR to TS 38.141-1: Editorial Changes of NR TM Power Balancing Readability | 16.2.0 | +| 2019-12 | RAN#86 | RP-192987 | 0062 | | A | CR Corrections to EVM 38.141-1 Annex H.7 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192987 | 0064 | | A | CR to TS 38.141-1: removal of [] for multiple requirements, Rel-16 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192988 | 0066 | | A | CR to TS 38.141-1: MR BS class terminology correction, Rel-16 | 16.2.0 | +| 2019-12 | RAN#86 | RP-193000 | 0068 | | A | CR: Updates to manufacture's declarations for demodulation requirements in TS 38.141-1 (Rel-16) | 16.2.0 | +| 2019-12 | RAN#86 | RP-193000 | 0070 | | A | CR: Updates for PUCCH formats 3 and 4 conducted conformance testing in TS 38.141-1 (Rel-16) | 16.2.0 | +| 2019-12 | RAN#86 | RP-192988 | 0072 | | A | Corrections of references in measurement uncertainty table | 16.2.0 | +| 2019-12 | RAN#86 | RP-192988 | 0074 | | A | Clarification for the number of interfering signals | 16.2.0 | +| 2019-12 | RAN#86 | RP-192988 | 0076 | | A | Editorial corrections | 16.2.0 | +| 2019-12 | RAN#86 | RP-192988 | 0080 | | A | Removal of FFS and brackets in RF requirements | 16.2.0 | +| 2019-12 | RAN#86 | RP-193000 | 0081 | | A | CR for 38.141-1 Conducted test requirements for NR PUCCH format 1 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192987 | 0082 | | A | CR for 38.141-1 Conducted test requirements for NR multi-slot PUCCH format 1 | 16.2.0 | +| 2019-12 | RAN#86 | RP-192987 | 0083 | | A | CR to TS 38.141-1: Corrections to BS classes and transmit configurations | 16.2.0 | +| 2020-03 | RAN#87 | RP-200402 | 0085 | | A | CR on correction of NR UCI on PUSCH conducted performance requirements for TS 38.141-1 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200402 | 0090 | 1 | A | CR to TS 38.141-1: Corrections on rated carrier output power symbols | 16.3.0 | +| 2020-03 | RAN#87 | RP-200402 | 0100 | | A | IntraSlot frequency hopping applicability in the one OFDM symbol test case | 16.3.0 | +| 2020-03 | RAN#87 | RP-200402 | 0103 | | A | CR to 38.141-1 updates for OSTP calculations | 16.3.0 | +| 2020-03 | RAN#87 | RP-200402 | 0105 | | A | CR to 38.141-1 Corrections to test models, TPDR and | 16.3.0 | + +| | | | | | | | | +|--|--|--|--|--|--|----------------------------------|--| +| | | | | | | modulation quality tests clauses | | +|--|--|--|--|--|--|----------------------------------|--| + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2020-03 | RAN#87 | RP-200402 | 0107 | | A | CR to TS 38.141-1: Random data content for NR BS Test Models | 16.3.0 | +| 2020-03 | RAN#87 | RP-200381 | 0086 | | B | Introduction of n26 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200382 | 0087 | | B | Introduction of n53 | 16.3.0 | +| 2020-03 | RAN#87 | RP-200410 | 0093 | 1 | B | CR to TS 38.141-1: Introduction of NB-IoT operation in NR channel bandwidth | 16.3.0 | +| 2020-03 | RAN#87 | RP-200407 | 0101 | 1 | B | CR for TS 38.141-1: Introduction of PRACH demodulation requirements for NR HST | 16.3.0 | +| 2020-03 | RAN#87 | RP-200407 | 0109 | 1 | B | CR for TS 38.141-1: Introduction of NR PUSCH performance requirements for HST | 16.3.0 | +| 2020-03 | RAN#87 | RP-200471 | 0110 | | B | CR for TS 38.141-1: Introduction of NR PUSCH performance Annex including both FRC and channel model for HST | 16.3.0 | +| 2020-06 | RAN#88 | RP-200986 | 0118 | | A | CR to TS 38.141-1: Corrections on generation of test configurations | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0120 | | A | CR to TS 38.141-1: Clarifications and corrections on extreme test environment | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0124 | | A | CR 38.141-1 Rel16 4.9.2.3 corrections for random data generation | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0126 | | A | CR to TS 38.141-1: Correction to out-of-band blocking requirement is clause 7.5 | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0134 | | A | CR to 38.141-1: Adding missing TT value for BS demod testing (C.3) | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0136 | | A | CR to 38.141-1 Rel-16 with correction to TPDR test procedure | 16.4.0 | +| 2020-06 | RAN#88 | RP-200975 | 0127 | 1 | B | CR for TS 38.141-1: Introduction of NR PUSCH performance requirements for HST | 16.4.0 | +| 2020-06 | RAN#88 | RP-200975 | 0128 | 1 | B | CR for TS 38.141-1: Introduction of NR PUSCH performance Annex including FRC and channel model for HST | 16.4.0 | +| 2020-06 | RAN#88 | RP-200975 | 0129 | 1 | F | CR for 38.141-1 Introduction of PRACH conducted conformance testing for NR HST | 16.4.0 | +| 2020-06 | RAN#88 | RP-201043 | 0121 | 1 | B | CR for TS 38.141-1: Introduce PUSCH performance requirements at 30% throughput test point | 16.4.0 | +| 2020-06 | RAN#88 | RP-200975 | 0122 | 1 | B | CR for TS 38.141-1, Introduction of high speed support declaration for NR HST | 16.4.0 | +| 2020-06 | RAN#88 | RP-200986 | 0118 | | A | CR to TS 38.141-1: Corrections on generation of test configurations | 16.4.0 | +| 2020-09 | RAN#89 | RP-201497 | 0141 | 1 | B | CR for TS 38.141-1: Updates of NR PUSCH performance requirements for HST | 16.5.0 | +| 2020-09 | RAN#89 | RP-201497 | 0142 | 1 | B | CR for TS 38.141-1: Updates of NR PUSCH performance Annex including FRC and channel model for HST | 16.5.0 | +| 2020-09 | RAN#89 | RP-201497 | 0143 | | F | CR for TS 38.141-1: Add maximum test system uncertainty for NR HST PUSCH with single port and AWGN | 16.5.0 | +| 2020-09 | RAN#89 | RP-201497 | 0144 | 1 | B | CR for TS 38.141-1, Introduction of high speed support declaration for NR HST PRACH | 16.5.0 | +| 2020-09 | RAN#89 | RP-201497 | 0145 | 1 | B | CR on UL timing adjustment conducted performance requirement for TS 38.141-1 | 16.5.0 | +| 2020-09 | RAN#89 | RP-201497 | 0148 | 1 | F | CR for TS 38.141-1: Introduction of test tolerance for HST PRACH and update measurement setup of performance requirements for NR HST | 16.5.0 | +| 2020-09 | RAN#89 | RP-201512 | 0150 | 1 | A | CR to 38.141-1: Annex H clarification on equalisation calculation (H.6) | 16.5.0 | +| 2020-12 | RAN#90 | RP-202422 | 0153 | 1 | B | CR for TS 38.141-1: Updates of NR PUSCH performance requirements for Multi-path fading channel models under high Doppler values and applicability rules. | 16.6.0 | +| 2020-12 | RAN#90 | RP-202415 | 0154 | 1 | B | Introduction of 2-step RACH FRC tables in 38.141-1 | 16.6.0 | +| 2020-12 | RAN#90 | RP-202416 | 0155 | 1 | B | FRCs for URLLC | 16.6.0 | +| 2020-12 | RAN#90 | RP-202416 | 0156 | 1 | B | Test requirements for 0.001% BLER | 16.6.0 | +| 2020-12 | RAN#90 | RP-202416 | 0157 | 1 | B | CR for 38.141-1: URLLC testing methodology appendix | 16.6.0 | +| 2020-12 | RAN#90 | RP-202422 | 0158 | 1 | B | CR on UL timing adjustment conducted performance requirement for TS 38.141-1 | 16.6.0 | +| 2020-12 | RAN#90 | RP-202416 | 0162 | 1 | B | CR to TS 38.141-1: Addition of BS conformance testing for URLLC demodulation requirements with higher BLER | 16.6.0 | +| 2020-12 | RAN#90 | RP-202416 | 0163 | 1 | F | CR to TS 38.141-1: Applicability of URLLC BS demodulation requirements | 16.6.0 | +| 2020-12 | RAN#90 | RP-202422 | 0166 | 1 | B | CR for 38.141-1 Introduction of conformance testing for NR HST PRACH under fading channel | 16.6.0 | +| 2020-12 | RAN#90 | RP-202415 | 0167 | 1 | B | CR to 38.141-1 Introduction of test procedure and requirements for | 16.6.0 | + +| | | | | | | | | +|--|--|--|--|--|--|-------------|--| +| | | | | | | 2-step RACH | | +|--|--|--|--|--|--|-------------|--| + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------------|--------| +| 2020-12 | RAN#90 | RP-202451 | 0151 | - | B | Introduction of 1880-1920MHz SUL band into Rel-17 TS 38.141-1 | 17.0.0 | +| 2020-12 | RAN#90 | RP-202452 | 0152 | - | B | Introduction of 2300-2400MHz SUL band into Rel-17 TS 38.141-1 | 17.0.0 | +| 2020-12 | RAN#90 | RP-202448 | 0164 | - | B | CR to TS 38.141-1: introduction of NR band n13 | 17.0.0 | +| 2021-03 | RAN#91 | RP-210097 | 0168 | | B | CR for TS 38.141-1 introduction of NR band n24 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210096 | 0169 | | B | CR to 38.141-1 on introducing new SUL band n99 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210116 | 0172 | | A | CR for 38.141-1: BS demodulation synchronization in test setup | 17.1.0 | +| 2021-03 | RAN#91 | RP-210116 | 0175 | | A | CR for 38.141-1: BS demodulation different channel bandwidths applicability rules | 17.1.0 | +| 2021-03 | RAN#91 | RP-210073 | 0177 | | A | Corrections on 2-step RACH demodulation requirements | 17.1.0 | +| 2021-03 | RAN#91 | RP-210078 | 0179 | | A | CR on UL timing adjustment conducted performance requirement for TS 38.141-1 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210078 | 0181 | | A | CR for TS 38.141-1 Updates of NR PUSCH performance requirements for HST | 17.1.0 | +| 2021-03 | RAN#91 | RP-210116 | 0184 | | A | CR to TS 38.141-1: Additions of regional requirements for n41 and n90 in Japan Rel-17 | 17.1.0 | +| 2021-03 | RAN#91 | RP-210073 | 0186 | | A | CR on update applicability rule for 2-step RACH in 38.141-1 (Rel-17) | 17.1.0 | +| 2021-03 | RAN#91 | RP-210078 | 0188 | | A | CR for 38.141-1 Cleanup of conformance testing for NR HST PRACH under fading channel (Rel-17) | 17.1.0 | +| 2021-03 | RAN#91 | RP-210068 | 0190 | | A | CR to TS38.141-1 Correction of BS conformance testing for URLLC demodulation requirements with higher BLER (Rel-17) | 17.1.0 | +| 2021-03 | RAN#91 | RP-210116 | 0194 | | A | CR to TS 141-1 clarification on PN23 sequence generation | 17.1.0 | +| 2021-03 | RAN#91 | RP-210116 | 0200 | | A | CR to TS38.141-1: Receiver requirement corrections | 17.1.0 | +| 2021-03 | RAN#91 | RP-210068 | 0202 | | A | CR to TS 38.141-1 Update of 0.001% BLER test requirements | 17.1.0 | +| 2021-06 | RAN#92 | RP-211094 | 0209 | | A | Big CR for NR-U BS conducted conformance testing in TS38.141-1 (catA) | 17.2.0 | +| 2021-06 | RAN#92 | RP-211105 | 0213 | | A | CR for TS 38.141-1 Updates of NR PUSCH performance requirements for HST | 17.2.0 | +| 2021-06 | RAN#92 | RP-211105 | 0215 | | A | CR on correction of UL timing adjustment conducted performance requirement for TS 38.141-1 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211086 | 0218 | | A | CR to TS 38.141-1: NRTC2 correction | 17.2.0 | +| 2021-06 | RAN#92 | RP-211116 | 0219 | 1 | B | CR to TS 38.141-1: Introduction of band n67 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211116 | 0220 | 1 | B | CR to TS 38.141-1: Introduction of band n85 | 17.2.0 | +| 2021-06 | RAN#92 | RP-211087 | 0224 | | A | CR to 38.141-1: BS PUCCH Format 3 demod requirement error correction (8.3.4) | 17.2.0 | +| 2021-06 | RAN#92 | RP-211103 | 0227 | 1 | F | CR to TS38.141-1 Cleanup of BS conformance testing for URLLC demodulation requirements with higher BLER (Rel-17) | 17.2.0 | +| 2021-06 | RAN#92 | RP-211108 | 0229 | | A | CR for 38.141-1: HST demodulation specification maintenance | 17.2.0 | +| 2021-06 | RAN#92 | RP-211094 | 0231 | | A | CR to TS 38.141-1: introduction of NR-U BS | 17.2.0 | +| 2021-06 | RAN#92 | RP-211088 | 0234 | | A | CR to TS 38.141-1: Receiver IMD requirement corrections | 17.2.0 | +| 2021-06 | RAN#92 | RP-211090 | 0237 | | A | CR to 38.141-1: In-band blocking for multi-band Base Stations | 17.2.0 | +| 2021-06 | RAN#92 | RP-211083 | 0240 | | A | CR for 38.141-1: Add AWGN Offset note to FR1 demod noise levels | 17.2.0 | +| 2021-09 | RAN#93 | RP-211909 | 0241 | | B | CR to TS 38.141-1: Introduction of CBWs 35 MHz and 45 MHz | 17.3.0 | +| 2021-09 | RAN#93 | RP-211926 | 0246 | | A | Big CR for TS 38.141-1 Maintenance RF part (Rel-17, CAT A) | 17.3.0 | +| 2021-09 | RAN#93 | RP-211926 | 0249 | | A | Big CR for TS 38.141-1 Maintenance Demod part (Rel-17, CAT A) | 17.3.0 | +| 2021-12 | RAN#94 | RP-212855 | 0254 | | A | Big CR for TS 38.141-1 Maintenance RF part (Rel-17, CAT A) | 17.4.0 | +| 2021-12 | RAN#94 | RP-212847 | 0257 | | A | Big CR for TS 38.141-1 Maintenance Demod part (Rel-17, CAT A) | 17.4.0 | +| 2022-03 | RAN#95 | RP-220349 | 0258 | | B | CR to TS 38.141-1: Introduction of 1024 QAM in FR1 | 17.5.0 | +| 2022-03 | RAN#95 | RP-220361 | 0259 | | B | BigCR for FR1 PUSCH 256QAM requirements in TS 38.141-1 | 17.5.0 | +| 2022-03 | RAN#95 | RP-220357 | 0261 | | B | CR to 38.141-1 on introduction of n102 requirements | 17.5.0 | +| 2022-03 | RAN#95 | RP-220347 | 0262 | 1 | B | CR to TS 38.141-1: implementation of LTE_upper_700MHz_A band 103 | 17.5.0 | +| 2022-03 | RAN#95 | RP-220337 | 0265 | 1 | A | Big CR for TS 38.141-1 Maintenance RF part (Rel-17, CAT A) | 17.5.0 | +| 2022-03 | RAN#95 | RP-220337 | 0268 | | A | Big CR for TS 38.141-1 Maintenance Demod part (Rel-17, CAT A) | 17.5.0 | +| 2022-03 | RAN#95 | RP-220376 | 0269 | | B | CR to TS 38.141-1: RMR 1900MHz band n101 introduction | 17.5.0 | +| 2022-06 | RAN#96 | RP-221675 | 0271 | | F | CR to 38.141-1: BS RF conformance requirements for 1024QAM in FR1 | 17.6.0 | +| 2022-06 | RAN#96 | RP-221684 | 0272 | 1 | B | CR to 38.141-1 on introduction of n100 requirements | 17.6.0 | +| 2022-06 | RAN#96 | RP-221659 | 0274 | | F | Big CR for TS 38.141-1 Maintenance RF part (Rel-17, CAT F) | 17.6.0 | +| 2022-09 | RAN#97 | RP-222038 | 0278 | 1 | F | CR to 38.141-1 on n100 corrections | 17.7.0 | +| 2022-09 | RAN#97 | RP-222037 | 0275 | 1 | B | Introducing 6GHz licensed operation into TS 38.141-1 (Rel-17) | 17.7.0 | +| 2022-09 | RAN#97 | RP-222026 | 0287 | | F | Big CR for TS 38.141-1 Maintenance RF part (Rel-17, CAT F) | 17.7.0 | +| 2022-09 | RAN#97 | RP-222026 | 0290 | | F | Big CR for TS 38.141-1 Maintenance Demod part (Rel-17, CAT F) | 17.7.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|-----------------------------------------------------------------------------------------|---------| +| 2022-12 | RAN#98-e | RP-223290 | 0291 | | F | CR for TS 38.141-1, Correct Mapping of PRBs to n_RNTI for NR-FR1-TM in clause 4.9.2.3.2 | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223300 | 0293 | | B | Big CR for TS38.141-1 NR coverage enhancement demodulation requirement | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223302 | 0294 | | B | Big CR for TS38.141-1 URLLC and IIoT requirements | 17.8.0- | +| 2022-12 | RAN#98-e | RP-223309 | 0296 | 1 | F | CR to 38.141-1: Spurious emission requirements, Rel-17 | 17.8.0 | +| 2022-12 | RAN#98-e | RP-223293 | 0299 | | A | CR to 38.141-1: Additional BS conformance to other standards | 17.8.0 | + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-12 | RAN#98-e | RP-223319 | 0292 | 1 | B | CR to TS 38.141-1: Introduction of NR band n105 | 18.0.0 | +| 2022-12 | RAN#98-e | RP-223315 | 0300 | | B | CR to 38.141-1 on introduction of Band 54 | 18.0.0 | +| 2023-03 | RAN#99 | RP-230513 | 0303 | | A | CR for TS38.141 NR coverage enh demod requirement (cat A) | 18.1.0 | +| 2023-03 | RAN#99 | RP-230515 | 0305 | | A | CR for TS38.141-1 NR URLLC IIoT enh demod (cat A) | 18.1.0 | +| 2023-03 | RAN#99 | RP-230535 | 0306 | 1 | B | CR to 38.141-1 on introduction of Band n54 | 18.1.0 | +| 2023-03 | RAN#99 | RP-230506 | 0309 | | A | CR to 38.141-1: FRC number corrections (Rel-18) | 18.1.0 | +| 2023-03 | RAN#99 | RP-230501 | 0312 | | A | CR to 38.141-1: BS Demod Step size correction on 2-Step RACH (8.2.9) | 18.1.0 | +| 2023-03 | RAN#99 | RP-230514 | 0317 | | A | CR to 38.141-1: MU values for OBW requirements (Rel-18) | 18.1.0 | +| 2023-03 | RAN#99 | RP-230509 | 0320 | | A | CR for TS38.141-1 correction on the value of SNR in test requirements for PUSCH | 18.1.0 | +| 2023-06 | RAN#100 | RP-231357 | 0326 | | A | CR to TS 38.141-1 on corrections of Wide Area BS Category B operating band unwanted emission limits | 18.2.0 | +| 2023-06 | RAN#100 | RP-231348 | 0328 | | A | CR to TS 38.141-1 on corrections and clarifications of operating band unwanted emission limits for band n104 | 18.2.0 | +| 2023-06 | RAN#100 | RP-231348 | 0330 | | A | CR for TR 38.141-1, Correction on reference of PREFSENS for in-band blocking and out-of-band blocking for band n104 | 18.2.0 | +| 2023-06 | RAN#100 | RP-231347 | 0339 | | A | CR for TS38.141-1 FRC tables for FR2-2 PUSCH demodulation_Rel-18 | 18.2.0 | +| 2023-06 | RAN#100 | RP-231352 | 0342 | 1 | A | CR for TS 38.141-1: Operating band unwanted emissions for Single RAT BS supporting multi-band operation | 18.2.0 | +| 2023-06 | RAN#100 | RP-231339 | 0344 | | A | CR to TS 38.141-1 - Maintenance related to bands n100 and n101 | 18.2.0 | +| 2023-06 | RAN#100 | RP-231362 | 0346 | | B | CR to 38.141-1 on introduction of Band 106 | 18.2.0 | +| 2023-06 | RAN#100 | RP-231358 | 0349 | | A | Update to PUSCH performance test cases | 18.2.0 | +| 2023-06 | RAN#100 | RP-231358 | 0353 | | A | CR to 38.141-1: Correction to ACLR and CACLR requirement | 18.2.0 | +| 2023-06 | RAN#100 | RP-231358 | 0356 | | A | CR for TS 38.141-1, Add sweep time for true RMS detection mode for receiver spurious emissions | 18.2.0 | +| 2023-09 | RAN#101 | RP-232496 | | | | [NR_RAIL_EU_900MHz-Core, NR_RAIL_EU_1900MHz_TDD-Core] CR to TS 38.141-1: corrections of RMR-specific BS requirements for band n100 and n101, Rel-18 | 18.3.0 | +| | | | 377 | - | A | | | +| 2023-09 | RAN#101 | RP-232492 | | | | [NR_L1enh_URLLC-Perf] CR to 38.141-1: Correction on BLER test requirement R18 | 18.3.0 | +| | | | 375 | - | A | | | +| 2023-09 | RAN#101 | RP-232504 | | | | | 18.3.0 | +| | | | 370 | - | A | CR to 38.141-1: Correction to ACLR and CACLR requirement | | +| 2023-09 | RAN#101 | RP-232492 | | | | | 18.3.0 | +| | | | 367 | - | A | CR for TS38.141-1 add declaration and applicability rule for URLLC requirements | | +| 2023-09 | RAN#101 | RP-232488 | | | | | 18.3.0 | +| | | | 364 | - | A | CR for TS38.141-1 correction for TBoMS configuration | | +| 2023-09 | RAN#101 | RP-232488 | | | | | 18.3.0 | +| | | | 362 | - | A | Update to Test Case 8.2.13 (FDD case, PUSCH Aggregation Factor 8), Rel18, 38.141-1 | | +| 2023-12 | RAN#102 | RP-233333 | 0380 | | A | CR for TS 38.141-1, Correction on reference of PREFSENS | 18.4.0 | +| 2023-12 | RAN#102 | RP-233342 | 0383 | | A | [NR_unlic-Perf] CR to TS 38.141-1 on correction of table numbers for Local Area BS in-channel selectivity for bands n46, n96 and n102 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233366 | 0387 | 1 | B | CR to TS 38.141-1 on introduction NR bands n31 and n72 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233342 | 0399 | | A | CR on 38.141-1: Correction on applicability rules for different bandwidth for PRACH with LRA=1151 and 571(Rel-18) | 18.4.0 | +| 2023-12 | RAN#102 | RP-233366 | 0400 | | B | CR to 38.141-1 on introduction of Band n106 | 18.4.0 | +| 2023-12 | RAN#102 | RP-233363 | 0389 | 1 | F | [NR_FR1_lessthan_5MHz_BW-Core] CR for Tx intermodulation requirements in certain region | 18.4.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------|--------| +| 2023-12 | RAN#102 | RP-233339 | 0386 | 1 | A | [NR_n18-Perf] CR to TS 38.141-1 on correction of table reference for Band n18 transmitter spurious emissions | 18.4.0 | +| 2023-12 | RAN#102 | RP-233366 | 0391 | 1 | B | CR to TS38.141-1 Introduction of n109 | 18.4.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38176-2/013c7ae7b0f9a1da5881cce6ab610a7c_img.jpg b/marked/Rel-18/38_series/38176-2/013c7ae7b0f9a1da5881cce6ab610a7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d7893156a261748aab66ce312897df8da2ca4ee --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/013c7ae7b0f9a1da5881cce6ab610a7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae5ad9ba5f43bab35ac9fdd7042904c23344013c1301947c974dab804f307214 +size 139645 diff --git a/marked/Rel-18/38_series/38176-2/04da196e79f7ac195f928904a244f0f9_img.jpg b/marked/Rel-18/38_series/38176-2/04da196e79f7ac195f928904a244f0f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1c5c5c879d2c7436f36132a0690f983f312f01d --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/04da196e79f7ac195f928904a244f0f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:441eb30d27bf3d60e250d156da6e4ab85caf75c2bff13f22116104603684daa3 +size 5885 diff --git a/marked/Rel-18/38_series/38176-2/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg b/marked/Rel-18/38_series/38176-2/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5592da65b33eada66232b16f6f4e150582affad7 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:497b65de23a368c101afee9d71fa2367d173e90bd62b674de82dcc80307612a3 +size 64546 diff --git a/marked/Rel-18/38_series/38176-2/17b315c49985d42848e8d673a66dce7f_img.jpg b/marked/Rel-18/38_series/38176-2/17b315c49985d42848e8d673a66dce7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f930db04d1bef3e2003fb3b3b957d0198be6af4f --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/17b315c49985d42848e8d673a66dce7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47c2356e3118d2a271b4c415949efba7a1ad30c8cae13e2c63c6b58819111ed2 +size 75846 diff --git a/marked/Rel-18/38_series/38176-2/180f1fb534ad2c1d918ede57612b3fb0_img.jpg b/marked/Rel-18/38_series/38176-2/180f1fb534ad2c1d918ede57612b3fb0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1eabd5edee75dffa661a734462e45e2cafead72f --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/180f1fb534ad2c1d918ede57612b3fb0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5642e9d207247885d07f875136e3ee986371e235c410e28a897a9b259f2347a8 +size 5509 diff --git a/marked/Rel-18/38_series/38176-2/294cfcd2dffc2040d25dd92a01ec70c3_img.jpg b/marked/Rel-18/38_series/38176-2/294cfcd2dffc2040d25dd92a01ec70c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..195fe8cbd29c8ec7ef74790a9edb0e3475a4d89d --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/294cfcd2dffc2040d25dd92a01ec70c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14ded6f154b420de9badfc8d6c07fdf019028758c1605ea04f2c1fd4b1c81af4 +size 70287 diff --git a/marked/Rel-18/38_series/38176-2/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-18/38_series/38176-2/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..089c294241ee2aeb6784b19251766e813b55e322 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3bd83dad41652901495d167b8a23fa014dd64f0a0d1c2b12aa25c5ba7c66f78e +size 52983 diff --git a/marked/Rel-18/38_series/38176-2/34b047489058d6400b412cd0ae2334ba_img.jpg b/marked/Rel-18/38_series/38176-2/34b047489058d6400b412cd0ae2334ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75f1654da24f3e8d975019e67cbdf3719fc13836 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/34b047489058d6400b412cd0ae2334ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7927c01adf6c11794257b3ded35c0c41645f7efe2974bfb42fcde274b2c52489 +size 61238 diff --git a/marked/Rel-18/38_series/38176-2/4c6037bc72ca92a1c2e48825c56fb56f_img.jpg b/marked/Rel-18/38_series/38176-2/4c6037bc72ca92a1c2e48825c56fb56f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..514ee66d0e7f60805a197d5dad3b358a7e5badad --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/4c6037bc72ca92a1c2e48825c56fb56f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77a0e45a1a8c3c5d15da7e1ce80645e3a22cd7333f303399d43ee3049a84f5ad +size 5598 diff --git a/marked/Rel-18/38_series/38176-2/4d9c52be1198628362ec7871f6e0f530_img.jpg b/marked/Rel-18/38_series/38176-2/4d9c52be1198628362ec7871f6e0f530_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..024aa8cc7a6036c51b37ba49ef3c0110bd3f5a68 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/4d9c52be1198628362ec7871f6e0f530_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11b07e2f268db5b639264a50b5e8acc96ec913c07b3d8e7250ac601fedbd8ed5 +size 5816 diff --git a/marked/Rel-18/38_series/38176-2/52e09725c3a496132a24092e9971bb2f_img.jpg b/marked/Rel-18/38_series/38176-2/52e09725c3a496132a24092e9971bb2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25b54045bf532815c7d02f7ab58ca3bf48e2e37a --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/52e09725c3a496132a24092e9971bb2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53a5f55954727df88ce2ad8e8e762b4ec0909aa53ede9d254d7822fd0f506daf +size 41910 diff --git a/marked/Rel-18/38_series/38176-2/55ae388f215d5291df7c3ca240351d14_img.jpg b/marked/Rel-18/38_series/38176-2/55ae388f215d5291df7c3ca240351d14_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fbed007dc2c46a43a13416d3490259b7a076bbb --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/55ae388f215d5291df7c3ca240351d14_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea8501cf78c55bd0e680d99bb0b45202e919a9e3e3fa8b355c75a29f1c4291e1 +size 18525 diff --git a/marked/Rel-18/38_series/38176-2/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-18/38_series/38176-2/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74a2d0b51a7a82d365254fd400c9c5cd7475d77f --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f62767393272a9e90f9e0c59d52aad364f800ae20e5827d0efc06e2dd1b7b89 +size 61138 diff --git a/marked/Rel-18/38_series/38176-2/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38176-2/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c82198430ad8c751aebe10ef2294666fdc65860 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3ef3896a0df0cfee120af6c8113430ecfe1913d6a35d913ac42b0d1c150a7fc +size 9275 diff --git a/marked/Rel-18/38_series/38176-2/5ff967638ed80b570723c608aa77fa39_img.jpg b/marked/Rel-18/38_series/38176-2/5ff967638ed80b570723c608aa77fa39_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b97c33b99be877b2099555b6b1dc1f27c35ecf5 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/5ff967638ed80b570723c608aa77fa39_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5898bda3514128712c9fe0c63de8e82fe8a09cea4513e18dbbe1e61b2526976e +size 81461 diff --git a/marked/Rel-18/38_series/38176-2/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38176-2/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05331e4db9d00e34003a1ffb27043f59756e3b02 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bedd09843461af3af948dc753098b4826c03a7011a1b14904483e69b2ccfae1c +size 5506 diff --git a/marked/Rel-18/38_series/38176-2/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-18/38_series/38176-2/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6cf59c19a8f19e80f232fcd4210dc4fc0dbea25 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d316fbc2ff298fad9ba80d78cbbdfcd736e5f6606badf5a6cf18b2b2c71e7fd6 +size 37988 diff --git a/marked/Rel-18/38_series/38176-2/6b29eb8374b62e0ef0bfcaa6764de39e_img.jpg b/marked/Rel-18/38_series/38176-2/6b29eb8374b62e0ef0bfcaa6764de39e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b77a271fe55ed401b27e0c61f0a9b9c6b843d6d7 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/6b29eb8374b62e0ef0bfcaa6764de39e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:325f59c5631c6693c0769f67e869b20f7946613de47652c4bc7cf38034eaf8b3 +size 75699 diff --git a/marked/Rel-18/38_series/38176-2/6d05c026b02a4762fcd1dcb5171327ac_img.jpg b/marked/Rel-18/38_series/38176-2/6d05c026b02a4762fcd1dcb5171327ac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af8ab4740a930fcd68ff7701071e7c123e7e7ba3 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/6d05c026b02a4762fcd1dcb5171327ac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43dc3fddf5f361ac00fcc3acb85a96ad2d9979f5985d9b64193d0774e772676b +size 69898 diff --git a/marked/Rel-18/38_series/38176-2/6fd4c6c23098ef713797b9e98ec299e8_img.jpg b/marked/Rel-18/38_series/38176-2/6fd4c6c23098ef713797b9e98ec299e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6322c5205de9ee3eb6276dfd29a8298cce9ad897 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/6fd4c6c23098ef713797b9e98ec299e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a27b82a8613f78de32beff732be51c710b799c71ddf312ab46d5b086498700c1 +size 82814 diff --git a/marked/Rel-18/38_series/38176-2/8c43614237e5bb57f1d5cf614291b32e_img.jpg b/marked/Rel-18/38_series/38176-2/8c43614237e5bb57f1d5cf614291b32e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7c816dab983417542cc631e624bd07b44da25fe --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/8c43614237e5bb57f1d5cf614291b32e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36e815693a954cc08b82641900815cfc74250d2c350a17733953f2fa38674dfa +size 46823 diff --git a/marked/Rel-18/38_series/38176-2/9ad891694657f787cf68e07db7060576_img.jpg b/marked/Rel-18/38_series/38176-2/9ad891694657f787cf68e07db7060576_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32a7d2fa88cd0c3a92139a503fbbc3105d44e365 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/9ad891694657f787cf68e07db7060576_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:440529066065dbd3eb5fa11367c2c1053e2cc30b652bf08e151544b0cbbc6c18 +size 67093 diff --git a/marked/Rel-18/38_series/38176-2/9b33f26612e373d186f5199dc2c83400_img.jpg b/marked/Rel-18/38_series/38176-2/9b33f26612e373d186f5199dc2c83400_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8032ddc698afbcb10501f84ddfedfb2c11b668a9 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/9b33f26612e373d186f5199dc2c83400_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:728f83bad8a43eab8ed978a63b41271305143315466c9ad2fd3db0bb508b0ee8 +size 48240 diff --git a/marked/Rel-18/38_series/38176-2/9ecaf3842a06bb8defd6bea7de551283_img.jpg b/marked/Rel-18/38_series/38176-2/9ecaf3842a06bb8defd6bea7de551283_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..357779e16b123b9e87753e48c108a8a64f6edb14 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/9ecaf3842a06bb8defd6bea7de551283_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80b43deef201167a08a63be0d2135bae097a94be741631f851eb1b768ad7e38d +size 53288 diff --git a/marked/Rel-18/38_series/38176-2/9ff1b32449ea068bba9647d71904bd59_img.jpg b/marked/Rel-18/38_series/38176-2/9ff1b32449ea068bba9647d71904bd59_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e30fbf5b686ce6e63d1b68269f42ae7165b873e --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/9ff1b32449ea068bba9647d71904bd59_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc8589cd0d18979660834d929a4e6231d1d986ba4091db0756497971c8294d38 +size 45963 diff --git a/marked/Rel-18/38_series/38176-2/b1ec498620251169dcfc839e18443154_img.jpg b/marked/Rel-18/38_series/38176-2/b1ec498620251169dcfc839e18443154_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9839fef9b9bf22f49faa22e2828739a20618bbf2 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/b1ec498620251169dcfc839e18443154_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:467a9d45bc1cffdb12b3ff048a8eebc11b1b9dfd2d7b9a07297222a4be99b588 +size 82496 diff --git a/marked/Rel-18/38_series/38176-2/b427b2e83302ee2f122a80fcb0fbb5d8_img.jpg b/marked/Rel-18/38_series/38176-2/b427b2e83302ee2f122a80fcb0fbb5d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ab31156423c664934d9cb1b13ba132f16ee36db --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/b427b2e83302ee2f122a80fcb0fbb5d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d056441ff92a896d9ac74cbfcee60f754a5a8db1bf7431d2873fa715dfe3f3b +size 66260 diff --git a/marked/Rel-18/38_series/38176-2/b6f6f51bf96aef85ffe1dcd9d57f398b_img.jpg b/marked/Rel-18/38_series/38176-2/b6f6f51bf96aef85ffe1dcd9d57f398b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0e9c88e5319823af1871c308079d4d2184a1a05 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/b6f6f51bf96aef85ffe1dcd9d57f398b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc4cf0eaf83f3b0e17a71dcfa61efd2b9332c9b6fd791ffd31b8f5394683c4d8 +size 5424 diff --git a/marked/Rel-18/38_series/38176-2/b9c42023cf4cb9547293c74191ea87a9_img.jpg b/marked/Rel-18/38_series/38176-2/b9c42023cf4cb9547293c74191ea87a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9202dd9a77118186d1d596b5fe0f75be33dd5a02 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/b9c42023cf4cb9547293c74191ea87a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb5c98c512d66530bd3b874a366d4c5a76c244535a5370eea081e1b65fd3f16e +size 58691 diff --git a/marked/Rel-18/38_series/38176-2/bb0e323a672fa2f89e0132b1db61cfb3_img.jpg b/marked/Rel-18/38_series/38176-2/bb0e323a672fa2f89e0132b1db61cfb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed80606ee2db472835c6f554661ec768ec399e0c --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/bb0e323a672fa2f89e0132b1db61cfb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af7f3e522e51390ab63943d214bae7540faa1974ba2d3ec2a420bf374c743b0a +size 65468 diff --git a/marked/Rel-18/38_series/38176-2/c06522346dd1926105a7273be1069715_img.jpg b/marked/Rel-18/38_series/38176-2/c06522346dd1926105a7273be1069715_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..569c76b74627acbd6281b9c664ca5e9118601575 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/c06522346dd1926105a7273be1069715_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72a498f937f8e7074a48de1361b06586c19e27490219c6be6f322a5c5991f4fc +size 26418 diff --git a/marked/Rel-18/38_series/38176-2/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-18/38_series/38176-2/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7f0e709d1b7e4a2f43618b6aa6349988a94359e --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac4256090e6a114dfb688c14636fc33143248f95f54d41d1a6f60bddd2a3f8fa +size 45137 diff --git a/marked/Rel-18/38_series/38176-2/d532466167e07c3d3dbbe3ffc0a84b3f_img.jpg b/marked/Rel-18/38_series/38176-2/d532466167e07c3d3dbbe3ffc0a84b3f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ddfc8099a26df1e6de7a9d8d71a3d92ce44a69a1 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/d532466167e07c3d3dbbe3ffc0a84b3f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec9a103992cbf3541804e5c9bccb851b73a89e42a93f5f2a05512a4d7f1b706b +size 69511 diff --git a/marked/Rel-18/38_series/38176-2/d7dd49b6b46d5db93258cc8769da942b_img.jpg b/marked/Rel-18/38_series/38176-2/d7dd49b6b46d5db93258cc8769da942b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05ec915564f4ed87544d5171e2bb3c61487133bf --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/d7dd49b6b46d5db93258cc8769da942b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd035f8244e397955fd1b8a77368c8edaeb58b3f809a514e82d9e28c4bc1e6f6 +size 65079 diff --git a/marked/Rel-18/38_series/38176-2/d7fd3bb81478f33c406af557efa5f4fb_img.jpg b/marked/Rel-18/38_series/38176-2/d7fd3bb81478f33c406af557efa5f4fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..848c6b1b2c862da652d3a7ef8b4e125c63c613d7 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/d7fd3bb81478f33c406af557efa5f4fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5c38ea9d3f2792eda53b8e005032cdfb89870bfec9b1b4b443b377493a0ed61 +size 77555 diff --git a/marked/Rel-18/38_series/38176-2/db593abff40ea8eb76129baab7f23b16_img.jpg b/marked/Rel-18/38_series/38176-2/db593abff40ea8eb76129baab7f23b16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22415a53d8629930f96ff28a53add803b48696ff --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/db593abff40ea8eb76129baab7f23b16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01e835051ebb9cd5607dad572b4ae777f127c866c4d2c8550744a6f61ef62827 +size 22347 diff --git a/marked/Rel-18/38_series/38176-2/e0304e6389e07d2620a7aac6efa6c940_img.jpg b/marked/Rel-18/38_series/38176-2/e0304e6389e07d2620a7aac6efa6c940_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..528d3d1a23e2036a7a7ee2c96711c34738f1f4fc --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/e0304e6389e07d2620a7aac6efa6c940_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b1afaaea3c076344dcdb7c52368c6fcffe1ba7052440c3a4b434918b939ba72 +size 68271 diff --git a/marked/Rel-18/38_series/38176-2/e0eba715b26e99c0beececdd6112ee58_img.jpg b/marked/Rel-18/38_series/38176-2/e0eba715b26e99c0beececdd6112ee58_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d82cc05b7390d8a0ff0d14a5871d619b8694cf9b --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/e0eba715b26e99c0beececdd6112ee58_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b94552490cf4628c8f13ac7118331f92ceeaf892c12117cc9f81bfdf87e3988 +size 76466 diff --git a/marked/Rel-18/38_series/38176-2/f2c8124b953b46b53423532cff4903e8_img.jpg b/marked/Rel-18/38_series/38176-2/f2c8124b953b46b53423532cff4903e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f79ae77bfb1ace272ae1be473c8a0d011b4b414e --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/f2c8124b953b46b53423532cff4903e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1916e1d8a78c0a9928d92ea8e9ed72d85ebb5c449ea80463837c4d5c12af45d +size 69776 diff --git a/marked/Rel-18/38_series/38176-2/f39d3a124ba232478c81cfc995e1acdf_img.jpg b/marked/Rel-18/38_series/38176-2/f39d3a124ba232478c81cfc995e1acdf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a9b86bfb20e9a4b6acc084e935230aca5e6b233 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/f39d3a124ba232478c81cfc995e1acdf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf4d7da965d8358db4e95c476765df7ceb6968329edb01e663adef901e2400fe +size 20027 diff --git a/marked/Rel-18/38_series/38176-2/f5d21653d7ae301d33b64eda6dfb40b8_img.jpg b/marked/Rel-18/38_series/38176-2/f5d21653d7ae301d33b64eda6dfb40b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d898f0b487212622783b0d31aa32ffb9e4f52e91 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/f5d21653d7ae301d33b64eda6dfb40b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74c103d3deeef9791a602d50131ffbba58677408953f1b7f21b9ef4fc8b56c64 +size 88010 diff --git a/marked/Rel-18/38_series/38176-2/fa0736695e26abf36c4ab5114e8c9c14_img.jpg b/marked/Rel-18/38_series/38176-2/fa0736695e26abf36c4ab5114e8c9c14_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..453216900ab5fdb4daee72ffc271d91ffbdeafcd --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/fa0736695e26abf36c4ab5114e8c9c14_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bdee808587f26fcdd82b22b5a1c4bd6cafe88b9b86de6e6ccd103dd45a7faa1 +size 44482 diff --git a/marked/Rel-18/38_series/38176-2/raw.md b/marked/Rel-18/38_series/38176-2/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e184c70bd8c019b6ec1104a640b56fef0d7cd8d3 --- /dev/null +++ b/marked/Rel-18/38_series/38176-2/raw.md @@ -0,0 +1,12099 @@ + + +# 3GPP TS 38.176-2 V18.3.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Integrated Access and Backhaul (IAB) conformance testing; Part 2: Radiated conformance testing; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green wave-like graphic 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 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. + +© 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..... | 24 | +| 1 Scope..... | 26 | +| 2 References..... | 26 | +| 3 Definitions of terms, symbols and abbreviations..... | 27 | +| 3.1 Terms..... | 27 | +| 3.2 Symbols..... | 31 | +| 3.3 Abbreviations..... | 33 | +| 4 General radiated test conditions and declarations..... | 35 | +| 4.1 Measurement uncertainties and test requirements..... | 35 | +| 4.1.1 General..... | 35 | +| 4.1.2 Acceptable uncertainty of OTA Test System..... | 37 | +| 4.1.2.1 General..... | 37 | +| 4.1.2.2 Measurement of transmitter..... | 38 | +| 4.1.2.3 Measurement of receiver..... | 40 | +| 4.1.2.4 Measurement of performance requirement..... | 43 | +| 4.1.3 Interpretation of measurement results..... | 46 | +| 4.2 Radiated requirement reference points..... | 47 | +| 4.3 IAB classes..... | 48 | +| 4.3.1 IAB-DU class ..... | 48 | +| 4.3.2 IAB-MT class ..... | 48 | +| 4.4 Regional requirements..... | 49 | +| 4.5 IAB configurations..... | 49 | +| 4.5.1 Transmit configurations..... | 49 | +| 4.5.2 Receive configurations..... | 50 | +| 4.5.3 Power supply options..... | 51 | +| 4.5.4 IAB with integrated Iuant BS modem..... | 52 | +| 4.6 Manufacturer's declarations..... | 52 | +| 4.7 Test configurations..... | 61 | +| 4.7.1 General..... | 61 | +| 4.7.2 Test signal configurations..... | 61 | +| 4.7.2.1 Test signal used to build Test Configurations..... | 61 | +| 4.7.2.2 IABTC1: Contiguous spectrum operation..... | 62 | +| 4.7.2.2.1 IABTC1 generation..... | 62 | +| 4.7.2.2.2 IABTC1 power allocation..... | 63 | +| 4.7.2.3 IABTC2: Contiguous CA occupied bandwidth..... | 63 | +| 4.7.2.3.1 IABTC2 generation..... | 63 | +| 4.7.2.3.2 IABTC2 power allocation..... | 63 | +| 4.7.2.4 IABTC3: Non-contiguous spectrum operation..... | 63 | +| 4.7.2.4.1 IABTC3 generation..... | 64 | +| 4.7.2.4.2 IABTC3 power allocation..... | 64 | +| 4.7.2.5 IABTC4: Multi-band test configuration for full carrier allocation..... | 64 | +| 4.7.2.5.1 IABTC4 generation..... | 64 | +| 4.7.2.5.2 IABTC4 power allocation..... | 65 | +| 4.7.2.6 IABTC5: Multi-band test configuration with high PSD per carrier..... | 65 | +| 4.7.2.6.1 IABTC5 generation..... | 65 | +| 4.7.2.6.2 IABTC5 power allocation..... | 66 | +| 4.8 Applicability of requirements..... | 66 | +| 4.8.1 Requirement set applicability..... | 66 | +| 4.8.2 Applicability of test configurations for single-band RIB..... | 66 | +| 4.8.3 Applicability of test configurations for multi-band RIB..... | 68 | +| 4.9 RF channels and test models..... | 70 | +| 4.9.1 RF channels..... | 70 | +| 4.9.2 Test models..... | 71 | +| 4.9.2.1 General..... | 71 | +| 4.9.2.2 FR2-1 test models for IAB-DU..... | 71 | + +| | | | +|------------|---------------------------------------------------------------------------|----| +| 4.9.2.3 | FR2-1 test models for IAB-MT..... | 71 | +| 4.9.2.3.1 | FR2-1 test model 1.1 (IAB-MT-FR2-TM1.1)..... | 72 | +| 4.9.2.3.2 | FR2-1 test model 2 (IAB-MT-FR2-TM2)..... | 72 | +| 4.9.2.3.2a | FR2-1 test model 2a (IAB-MT-FR2-TM2a)..... | 73 | +| 4.9.2.3.3 | FR2-1 test model 3.1 (IAB-MT-FR2-TM3.1)..... | 73 | +| 4.9.2.3.4 | FR2-1 test model 3.1a (IAB-MT-FR2-TM3.1a)..... | 73 | +| 4.9.2.3 | Data content of physical channels and signals for IAB-MT-FR2-TM..... | 74 | +| 4.9.2.3.1 | PUSCH..... | 74 | +| 4.10 | Requirements for contiguous and non-contiguous spectrum..... | 74 | +| 4.11 | Requirements for IAB capable of multi-band operation..... | 75 | +| 4.12 | Co-location requirements..... | 75 | +| 4.12.1 | General..... | 75 | +| 4.12.2 | Co-location test antenna..... | 76 | +| 4.12.2.1 | General..... | 76 | +| 4.12.2.2 | Co-location test antenna characteristics..... | 76 | +| 4.12.2.3 | Co-location test antenna alignment..... | 76 | +| 4.13 | Test efficiency optimization..... | 77 | +| 4.14 | Format and interpretation of tests..... | 79 | +| 4.15 | Reference coordinate system..... | 80 | +| 4.16 | Requirements for IAB-DU and IAB-MT capable of simultaneous operation..... | 80 | +| 5 | Operating bands and channel arrangement..... | 81 | +| 6 | Radiated transmitter characteristics..... | 81 | +| 6.1 | General..... | 81 | +| 6.2 | Radiated transmit power..... | 81 | +| 6.2.1 | Definition and applicability..... | 81 | +| 6.2.2 | Minimum requirement..... | 82 | +| 6.2.3 | Test purpose..... | 82 | +| 6.2.4 | Method of test..... | 82 | +| 6.2.4.1 | Initial conditions..... | 82 | +| 6.2.4.2 | Procedure..... | 83 | +| 6.2.5 | Test requirement..... | 83 | +| 6.2.5.1 | IAB-DU..... | 83 | +| 6.2.5.2 | IAB-MT..... | 83 | +| 6.3 | IAB output power..... | 84 | +| 6.3.1 | Definition and applicability..... | 84 | +| 6.3.2 | Minimum requirement..... | 84 | +| 6.3.3 | Test purpose..... | 84 | +| 6.3.4 | Method of test..... | 85 | +| 6.3.4.1 | Initial conditions..... | 85 | +| 6.3.4.2 | Procedure..... | 85 | +| 6.3.5 | Test requirement..... | 85 | +| 6.3.5.1 | IAB type 1-O ..... | 85 | +| 6.3.5.2 | IAB type 2-O ..... | 86 | +| 6.4 | OTA output power dynamics..... | 86 | +| 6.4.1 | IAB-DU OTA Output Power Dynamics..... | 86 | +| 6.4.1.1 | General..... | 86 | +| 6.4.1.2 | OTA RE power control dynamic range..... | 86 | +| 6.4.1.2.1 | Definition and applicability..... | 86 | +| 6.4.1.2.2 | Minimum requirement..... | 86 | +| 6.4.1.2.3 | Test purpose..... | 86 | +| 6.4.1.3 | OTA total power dynamic range..... | 86 | +| 6.4.1.3.1 | Definition and applicability..... | 86 | +| 6.4.1.3.2 | Minimum requirement..... | 87 | +| 6.4.1.3.3 | Test purpose..... | 87 | +| 6.4.1.3.4 | Method of test..... | 87 | +| 6.4.1.3.5 | Test requirements..... | 88 | +| 6.4.2 | IAB-MT OTA Output Power Dynamics..... | 89 | +| 6.4.2.1 | OTA total power dynamic range..... | 89 | +| 6.4.2.1.1 | Definition and applicability..... | 89 | +| 6.4.2.1.2 | Minimum requirement..... | 89 | + +| | | | +|-----------|------------------------------------------------------|-----| +| 6.4.2.1.3 | Test purpose..... | 89 | +| 6.4.2.1.4 | Method of test..... | 89 | +| 6.4.2.1.5 | Test requirements..... | 90 | +| 6.4.2.2 | Relative power tolerance for local area IAB-MT..... | 91 | +| 6.4.2.2.1 | Definition and applicability..... | 91 | +| 6.4.2.2.2 | Minimum requirement..... | 91 | +| 6.4.2.2.3 | Test purpose..... | 91 | +| 6.4.2.3 | Aggregate power tolerance for local area IAB-MT..... | 91 | +| 6.4.2.3.1 | Definition and applicability..... | 91 | +| 6.4.2.3.2 | Minimum requirement..... | 91 | +| 6.4.2.3.3 | Test purpose..... | 91 | +| 6.5 | OTA transmit ON/OFF power..... | 91 | +| 6.5.1 | OTA transmitter OFF power..... | 91 | +| 6.5.1.1 | Definition and applicability..... | 91 | +| 6.5.1.2 | Minimum requirement..... | 92 | +| 6.5.1.3 | Test purpose..... | 92 | +| 6.5.1.4 | Method of test..... | 92 | +| 6.5.1.5 | Test requirements..... | 92 | +| 6.5.2 | OTA transmitter transient period..... | 92 | +| 6.5.2.1 | Definition and applicability..... | 92 | +| 6.5.2.2 | Minimum requirement..... | 93 | +| 6.5.2.3 | Test purpose..... | 93 | +| 6.5.2.4 | Method of test..... | 93 | +| 6.5.2.4.1 | Initial conditions..... | 93 | +| 6.5.2.4.2 | Procedure..... | 93 | +| 6.5.2.5 | Test requirements..... | 94 | +| 6.5.2.5.1 | IAB type 1-O ..... | 94 | +| 6.5.2.5.2 | IAB type 2-O ..... | 95 | +| 6.6 | OTA transmitted signal quality..... | 95 | +| 6.6.1 | General..... | 95 | +| 6.6.2 | OTA frequency error..... | 95 | +| 6.6.2.1 | IAB-DU OTA frequency error..... | 95 | +| 6.6.2.1.1 | Definition and applicability..... | 95 | +| 6.6.2.1.2 | Minimum Requirement..... | 95 | +| 6.6.2.1.3 | Test purpose..... | 95 | +| 6.6.2.1.4 | Method of test..... | 95 | +| 6.6.2.1.5 | Test Requirements..... | 96 | +| 6.6.2.2 | IAB-MT OTA frequency error..... | 96 | +| 6.6.2.2.1 | Definition and applicability..... | 96 | +| 6.6.2.2.2 | Minimum Requirement..... | 96 | +| 6.6.2.2.3 | Test purpose..... | 96 | +| 6.6.2.2.4 | Method of test..... | 96 | +| 6.6.2.2.5 | Test Requirements..... | 96 | +| 6.6.3 | OTA modulation quality..... | 96 | +| 6.6.3.1 | Definition and applicability..... | 96 | +| 6.6.3.2 | Minimum Requirement..... | 97 | +| 6.6.3.3 | Test purpose..... | 97 | +| 6.6.3.4 | Method of test..... | 97 | +| 6.6.3.4.1 | Initial conditions..... | 97 | +| 6.6.3.4.2 | Procedure for IAB-DU..... | 97 | +| 6.6.3.4.3 | Procedure for IAB-MT..... | 99 | +| 6.6.3.5 | Test requirements..... | 100 | +| 6.6.3.5.1 | IAB-DU type 1-O and IAB-MT type 1-O ..... | 100 | +| 6.6.3.5.2 | IAB-DU type 2-O and IAB-MT type 2-O ..... | 101 | +| 6.6.4 | OTA time alignment error..... | 102 | +| 6.6.4.1 | Definition and applicability..... | 102 | +| 6.6.4.2 | Minimum requirement..... | 102 | +| 6.6.4.3 | Test purpose..... | 102 | +| 6.6.4.4 | Method of test..... | 102 | +| 6.6.4.4.1 | Initial conditions..... | 102 | +| 6.6.4.4.2 | Procedure for IAB-DU..... | 103 | + +| | | | +|-----------|-----------------------------------------------------------------|-----| +| 6.6.4.5 | Test Requirement..... | 104 | +| 6.6.4.5.1 | IAB-DU type 1-O ..... | 104 | +| 6.6.4.5.2 | IAB-DU type 2-O ..... | 104 | +| 6.6.5 | Timing error between IAB-DU and IAB-MT..... | 104 | +| 6.6.5.1 | Definition and applicability..... | 104 | +| 6.6.5.2 | Minimum requirement..... | 104 | +| 6.6.5.3 | Test purpose..... | 104 | +| 6.6.5.4 | Method of test..... | 104 | +| 6.6.5.4.1 | Initial conditions..... | 104 | +| 6.6.5.4.2 | Procedure..... | 105 | +| 6.6.5.5 | Test Requirement..... | 105 | +| 6.6.5.5.1 | IAB type 1-O..... | 105 | +| 6.6.5.5.2 | IAB type 2-O..... | 105 | +| 6.7 | OTA unwanted emissions..... | 105 | +| 6.7.1 | General..... | 105 | +| 6.7.2 | OTA occupied bandwidth..... | 106 | +| 6.7.2.1 | Definition and applicability..... | 106 | +| 6.7.2.2 | Minimum requirement..... | 106 | +| 6.7.2.3 | Test purpose..... | 106 | +| 6.7.2.4 | Method of test..... | 107 | +| 6.7.2.4.1 | Initial conditions..... | 107 | +| 6.7.2.4.2 | Procedure..... | 107 | +| 6.7.2.5 | Test requirement..... | 108 | +| 6.7.2.5.1 | IAB-DU type 1-O and IAB-DU type 2-O ..... | 108 | +| 6.7.2.5.2 | IAB-MT type 1-O and IAB-MT type 2-O ..... | 108 | +| 6.7.3 | OTA Adjacent Channel Leakage Power Ratio (ACLR)..... | 109 | +| 6.7.3.1 | Definition and applicability..... | 109 | +| 6.7.3.2 | Minimum requirement..... | 109 | +| 6.7.3.3 | Test purpose..... | 109 | +| 6.7.3.4 | Method of test..... | 109 | +| 6.7.3.4.1 | Initial conditions..... | 109 | +| 6.7.3.4.2 | Procedure..... | 109 | +| 6.7.3.5 | Test requirements..... | 110 | +| 6.7.3.5.1 | IAB-DU type 1-O and IAB-MT type 1-O ..... | 110 | +| 6.7.3.5.2 | IAB-DU type 2-O and Wide Area IAB-MT type 2-O ..... | 113 | +| 6.7.3.5.3 | Local Area IAB-MT type 2-O ..... | 116 | +| 6.7.4 | OTA operating band unwanted emissions..... | 119 | +| 6.7.4.1 | Definition and applicability..... | 119 | +| 6.7.4.1.1 | IAB-DU type 1-O ..... | 119 | +| 6.7.4.1.2 | IAB-MT type 1-O ..... | 119 | +| 6.7.4.1.3 | IAB-DU type 2-O and IAB-MT type 2-O ..... | 119 | +| 6.7.4.2 | Minimum requirement..... | 119 | +| 6.7.4.3 | Test purpose..... | 119 | +| 6.7.4.4 | Method of test..... | 119 | +| 6.7.4.4.1 | Initial conditions..... | 119 | +| 6.7.4.4.2 | Procedure..... | 120 | +| 6.7.4.5 | Test requirements..... | 120 | +| 6.7.4.5.1 | IAB type 1-O ..... | 120 | +| 6.7.4.6.1 | Medium Range IAB-DU (Category A and B)..... | 125 | +| 6.7.4.6.2 | Local Area IAB-DU and Local Area IAB-MT (Category A and B)..... | 127 | +| 6.7.4.6.3 | Additional requirements..... | 129 | +| 6.7.4.6.4 | IAB type 2-O ..... | 129 | +| 6.7.5 | OTA transmitter spurious emissions..... | 132 | +| 6.7.5.1 | General..... | 132 | +| 6.7.5.2 | General OTA transmitter spurious emissions requirements..... | 133 | +| 6.7.5.2.1 | Definition and applicability..... | 133 | +| 6.7.5.2.2 | Minimum requirement..... | 133 | +| 6.7.5.2.3 | Test purpose..... | 133 | +| 6.7.5.2.4 | Method of test..... | 133 | +| 6.7.5.2.5 | Test requirement..... | 134 | +| 6.7.5.3 | Void..... | 136 | + +| | | | +|-----------|-------------------------------------------------------------------------------|-----| +| 6.7.5.4 | Additional spurious emissions requirements..... | 136 | +| 6.7.5.4.1 | Definition and applicability..... | 136 | +| 6.7.5.4.2 | Minimum Requirement..... | 137 | +| 6.7.5.4.3 | Test purpose..... | 137 | +| 6.7.5.4.4 | Method of test..... | 137 | +| 6.7.5.4.5 | Test requirement..... | 139 | +| 6.7.5.5 | Co-location requirements..... | 146 | +| 6.7.5.5.1 | Definition and applicability..... | 146 | +| 6.7.5.5.2 | Minimum requirements..... | 147 | +| 6.7.5.5.3 | Test purpose..... | 147 | +| 6.7.5.5.4 | Method of test..... | 147 | +| 6.7.5.5.5 | Test requirements..... | 148 | +| 6.8 | OTA transmitter intermodulation..... | 152 | +| 6.8.1 | Definition and applicability..... | 152 | +| 6.8.2 | Minimum requirement..... | 152 | +| 6.8.3 | Test purpose..... | 153 | +| 6.8.4 | Method of test..... | 153 | +| 6.8.4.1 | Initial conditions..... | 153 | +| 6.8.4.2 | Procedure..... | 153 | +| 6.8.5 | Test requirements..... | 155 | +| 6.8.5.1 | Requirement for IAB type 1-O ..... | 155 | +| 7 | Radiated receiver characteristics..... | 155 | +| 7.1 | General..... | 155 | +| 7.2 | OTA sensitivity..... | 156 | +| 7.2.1 | Definition and applicability..... | 156 | +| 7.2.2 | Minimum requirement..... | 157 | +| 7.2.3 | Test purpose..... | 157 | +| 7.2.4 | Method of test..... | 157 | +| 7.2.4.1 | Initial conditions..... | 157 | +| 7.2.4.2 | Procedure..... | 157 | +| 7.2.5 | Test requirements..... | 158 | +| 7.2.5.1 | General..... | 158 | +| 7.2.5.2 | Test requirements for IAB-DU type 1-H and IAB-DU type 1-O ..... | 158 | +| 7.2.5.3 | Test requirements for IAB-MT type 1-H and IAB-MT type 1-O ..... | 158 | +| 7.3 | OTA reference sensitivity level..... | 159 | +| 7.3.1 | Definition and applicability..... | 159 | +| 7.3.2 | Minimum requirement..... | 159 | +| 7.3.3 | Test Purpose..... | 159 | +| 7.3.4 | Method of test..... | 159 | +| 7.3.4.1 | Initial conditions..... | 159 | +| 7.3.4.2 | Procedure..... | 160 | +| 7.3.5 | Test requirements..... | 160 | +| 7.3.5.1 | General..... | 160 | +| 7.3.5.2 | IAB-DU OTA reference sensitivity level..... | 160 | +| 7.3.5.2.1 | Test requirements for IAB-DU type 1-O ..... | 160 | +| 7.3.5.2.2 | Test requirements for IAB-DU type 2-O ..... | 162 | +| 7.3.5.3 | IAB-MT OTA reference sensitivity level..... | 163 | +| 7.3.5.3.1 | Test requirement for IAB-MT type 1-O ..... | 163 | +| 7.3.5.3.2 | Minimum requirement for IAB-MT type 2-O ..... | 163 | +| 7.4 | OTA dynamic range..... | 164 | +| 7.4.1 | Definition and applicability..... | 164 | +| 7.4.2 | Minimum requirement..... | 164 | +| 7.4.3 | Test purpose..... | 164 | +| 7.4.4 | Method of test..... | 164 | +| 7.4.4.1 | Initial conditions..... | 164 | +| 7.4.4.2 | Procedure..... | 165 | +| 7.4.5 | Test requirement..... | 165 | +| 7.4.5.1 | General..... | 165 | +| 7.4.5.2 | Test requirements for IAB-DU type 1-O ..... | 165 | +| 7.5 | OTA in-band selectivity and blocking..... | 169 | +| 7.5.1 | OTA adjacent channel selectivity..... | 169 | + +| | | | +|-----------|-------------------------------------------------------------|-----| +| 7.5.1.1 | Definition and applicability..... | 169 | +| 7.5.1.2 | Minimum requirement..... | 169 | +| 7.5.1.3 | Test purpose..... | 169 | +| 7.5.1.4 | Method of test..... | 169 | +| 7.5.1.4.1 | Initial conditions..... | 169 | +| 7.5.1.4.2 | Procedure..... | 169 | +| 7.5.1.5 | Test requirement..... | 170 | +| 7.5.1.5.1 | General..... | 170 | +| 7.5.1.5.2 | Test requirements for IAB-DU type 1-O ..... | 170 | +| 7.5.1.5.3 | Test requirements for IAB-DU type 2-O ..... | 171 | +| 7.5.1.5.4 | Test requirements for IAB-MT type 1-O ..... | 172 | +| 7.5.1.5.5 | Test requirements for IAB-MT type 2-O ..... | 173 | +| 7.5.2 | OTA in-band blocking..... | 174 | +| 7.5.2.1 | Definition and applicability..... | 174 | +| 7.5.2.2 | Minimum requirement..... | 174 | +| 7.5.2.3 | Test purpose..... | 174 | +| 7.5.2.4 | Method of test..... | 174 | +| 7.5.2.4.1 | Initial conditions..... | 174 | +| 7.5.2.4.2 | Procedure..... | 175 | +| 7.5.2.5 | Test requirement..... | 177 | +| 7.5.2.5.1 | General..... | 177 | +| 7.5.2.5.2 | Test requirements for IAB-DU type 1-O ..... | 177 | +| 7.5.2.5.3 | Test requirements for IAB-DU type 2-O ..... | 181 | +| 7.5.2.5.4 | Test requirements for IAB-MT type 1-O ..... | 182 | +| 7.5.2.5.5 | Test requirements for IAB-MT type 2-O ..... | 185 | +| 7.6 | OTA out-of-band blocking..... | 185 | +| 7.6.1 | Definition and applicability..... | 185 | +| 7.6.2 | Minimum requirement..... | 186 | +| 7.6.3 | Test purpose..... | 186 | +| 7.6.4 | Method of test..... | 186 | +| 7.6.4.1 | Initial conditions..... | 186 | +| 7.6.4.2 | Procedure..... | 186 | +| 7.6.4.2.1 | IAB type 1-O procedure for out-of-band blocking..... | 186 | +| 7.6.4.2.2 | IAB type 1-O procedure for co-location blocking..... | 187 | +| 7.6.4.2.3 | IAB type 2-O procedure for out-of-band blocking..... | 187 | +| 7.6.5 | Test requirements..... | 188 | +| 7.6.5.1 | Requirement for IAB Type 1-O ..... | 188 | +| 7.6.5.1.1 | General..... | 188 | +| 7.6.5.1.2 | Co-location requirement..... | 189 | +| 7.6.5.2 | Requirement for IAB type 2-O ..... | 189 | +| 7.6.5.2.1 | General requirement..... | 189 | +| 7.7 | OTA receiver spurious emissions..... | 190 | +| 7.7.1 | Definition and applicability..... | 190 | +| 7.7.2 | Minimum requirement..... | 190 | +| 7.7.3 | Test purpose..... | 191 | +| 7.7.4 | Method of test..... | 191 | +| 7.7.4.1 | Initial conditions..... | 191 | +| 7.7.4.2 | Procedure..... | 191 | +| 7.7.5 | Test requirement..... | 192 | +| 7.7.5.1 | Test requirement for IAB type 1-O ..... | 192 | +| 7.7.5.2 | Test requirement for IAB type 2-O ..... | 192 | +| 7.8 | OTA receiver intermodulation..... | 193 | +| 7.8.1 | Definition and applicability..... | 193 | +| 7.8.2 | Minimum requirement..... | 194 | +| 7.8.3 | Test purpose..... | 194 | +| 7.8.4 | Method of test..... | 194 | +| 7.8.4.1 | Initial conditions..... | 194 | +| 7.8.4.2 | Procedure..... | 194 | +| 7.8.5 | Test requirement..... | 195 | +| 7.8.5.1 | IAB-DU type 1-O..... | 195 | +| 7.8.5.2 | IAB-DU type 2-O..... | 200 | + +| | | | +|-----------|---------------------------------------------------------------------------|-----| +| 7.8.5.3 | IAB-MT type 1-O..... | 200 | +| 7.9 | OTA in-channel selectivity..... | 204 | +| 7.9.1 | Definition and applicability..... | 204 | +| 7.9.2 | Minimum requirement..... | 205 | +| 7.9.3 | Test purpose..... | 205 | +| 7.9.4 | Method of test..... | 205 | +| 7.9.4.1 | Initial conditions..... | 205 | +| 7.9.4.2 | Procedure..... | 205 | +| 7.9.5 | Test requirement..... | 206 | +| 7.9.5.1 | IAB-DU type 1-O ..... | 206 | +| 7.9.5.2 | IAB-DU type 2-O ..... | 208 | +| 8 | Radiated performance requirements..... | 209 | +| 8.1 | IAB-DU performance requirements..... | 209 | +| 8.1.1 | General..... | 209 | +| 8.1.1.1 | Scope and definitions..... | 209 | +| 8.1.1.2 | OTA demodulation branches..... | 210 | +| 8.1.1.3 | Applicability rule..... | 210 | +| 8.1.1.3.1 | General..... | 210 | +| 8.1.1.3.2 | Applicability of PUSCH performance requirements..... | 210 | +| 8.1.1.3.3 | Applicability of PUCCH performance requirements..... | 211 | +| 8.1.1.3.4 | Applicability of PRACH performance requirements..... | 212 | +| 8.1.2 | Performance requirements for PUSCH..... | 212 | +| 8.1.2.1 | Performance requirements for PUSCH with transform precoding disabled..... | 212 | +| 8.1.2.1.1 | Definition and applicability..... | 212 | +| 8.1.2.1.2 | Minimum Requirement..... | 212 | +| 8.1.2.1.3 | Test purpose..... | 212 | +| 8.1.2.1.4 | Method of test..... | 212 | +| 8.1.2.1.5 | Test Requirement..... | 214 | +| 8.1.2.2 | Performance requirements for PUSCH with transform precoding enabled..... | 220 | +| 8.1.2.2.1 | Definition and applicability..... | 220 | +| 8.1.2.2.2 | Minimum Requirement..... | 220 | +| 8.1.2.2.3 | Test Purpose..... | 220 | +| 8.1.2.2.4 | Method of test..... | 220 | +| 8.1.2.2.5 | Test Requirement..... | 222 | +| 8.1.2.3 | Performance requirements for UCI multiplexed on PUSCH..... | 223 | +| 8.1.2.3.1 | Definition and applicability..... | 223 | +| 8.1.2.3.2 | Minimum Requirement..... | 223 | +| 8.1.2.3.3 | Test Purpose..... | 224 | +| 8.1.2.3.4 | Method of test..... | 224 | +| 8.1.2.3.5 | Test Requirement..... | 226 | +| 8.1.3 | Performance requirements for PUCCH..... | 227 | +| 8.1.3.1 | Performance requirements for PUCCH format 0..... | 227 | +| 8.1.3.1.1 | Definition and applicability..... | 227 | +| 8.1.3.1.2 | Minimum Requirement..... | 228 | +| 8.1.3.1.3 | Test Purpose..... | 228 | +| 8.1.3.1.4 | Method of test..... | 228 | +| 8.1.3.1.5 | Test Requirement..... | 230 | +| 8.1.3.2 | Performance requirements for PUCCH format 1..... | 230 | +| 8.1.3.2.1 | NACK to ACK detection..... | 230 | +| 8.1.3.2.2 | ACK missed detection..... | 233 | +| 8.1.3.3 | Performance requirements for PUCCH format 2..... | 236 | +| 8.1.3.3.1 | ACK missed detection performance requirements..... | 236 | +| 8.1.3.3.2 | UCI BLER performance requirements..... | 239 | +| 8.1.3.4 | Performance requirements for PUCCH format 3..... | 241 | +| 8.1.3.4.1 | Definition and applicability..... | 241 | +| 8.1.3.4.2 | Minimum Requirement..... | 242 | +| 8.1.3.4.3 | Test Purpose..... | 242 | +| 8.1.3.4.4 | Method of test..... | 242 | +| 8.1.3.4.5 | Test Requirement..... | 243 | +| 8.1.3.5 | Performance requirements for PUCCH format 4..... | 244 | +| 8.1.3.5.1 | Definition and applicability..... | 244 | + +| | | | +|-----------|--------------------------------------------------------------|-----| +| 8.1.3.5.2 | Minimum Requirement..... | 245 | +| 8.1.3.5.3 | Test Purpose..... | 245 | +| 8.1.3.5.4 | Method of test..... | 245 | +| 8.1.3.5.5 | Test Requirement..... | 246 | +| 8.1.3.6 | Performance requirements for multi-slot PUCCH..... | 247 | +| 8.1.3.6.1 | Performance requirements for multi-slot PUCCH format 1 ..... | 247 | +| 8.1.4 | Performance requirements for PRACH..... | 251 | +| 8.1.4.1 | PRACH false alarm probability and missed detection..... | 251 | +| 8.1.4.1.1 | Definition and applicability..... | 251 | +| 8.1.4.1.2 | Minimum requirement..... | 251 | +| 8.1.4.1.3 | Test purpose..... | 251 | +| 8.1.4.1.4 | Method of test..... | 251 | +| 8.1.4.1.5 | Test requirement for Normal Mode..... | 253 | +| 8.2 | IAB-MT performance requirements..... | 254 | +| 8.2.1 | General..... | 254 | +| 8.2.1.1 | Scope and definitions..... | 254 | +| 8.2.2 | Demodulation performance requirements..... | 255 | +| 8.2.2.1 | General..... | 255 | +| 8.2.2.1.1 | Applicability rule for IAB-MT..... | 255 | +| 8.2.2.2 | Performance requirements for PDSCH..... | 256 | +| 8.2.2.2.1 | Definition and applicability..... | 256 | +| 8.2.2.2.2 | Minimum requirements..... | 256 | +| 8.2.2.2.3 | Test purpose..... | 256 | +| 8.2.2.2.4 | Method of test..... | 256 | +| 8.2.2.2.5 | Test requirements..... | 258 | +| 8.2.2.3 | Demodulation performance requirements for PDCCH..... | 259 | +| 8.2.2.3.1 | Definition and applicability..... | 259 | +| 8.2.2.3.2 | Minimum requirement..... | 259 | +| 8.2.2.3.3 | Test purpose..... | 259 | +| 8.2.2.3.4 | Method of test..... | 259 | +| 8.2.2.3.5 | Test requirements..... | 260 | +| 8.2.3 | CSI reporting requirements..... | 261 | +| 8.2.3.1 | General..... | 261 | +| 8.2.3.1.1 | Applicability of requirements..... | 261 | +| 8.2.3.1.2 | Common test parameters..... | 262 | +| 8.2.3.2 | Reporting of Channel Quality Indicator (CQI)..... | 263 | +| 8.2.3.2.1 | Definition and applicability..... | 263 | +| 8.2.3.2.2 | Minimum requirement..... | 263 | +| 8.2.3.2.3 | Test purpose..... | 264 | +| 8.2.3.2.4 | Method of test..... | 264 | +| 8.2.3.2.5 | Test requirement..... | 267 | +| 8.2.3.3 | Reporting of Precoding Matrix Information (PMI)..... | 267 | +| 8.2.3.3.1 | Definition and applicability..... | 267 | +| 8.2.3.3.2 | Minimum requirement..... | 268 | +| 8.2.3.3.3 | Test purpose..... | 268 | +| 8.2.3.3.4 | Method of test..... | 268 | +| 8.2.3.3.5 | Test requirement..... | 271 | +| 8.2.3.4 | Reporting of Rank Information (RI)..... | 272 | +| 8.2.3.4.1 | Definition and applicability..... | 272 | +| 8.2.3.4.2 | Minimum requirement..... | 272 | +| 8.2.3.4.3 | Test purpose..... | 272 | +| 8.2.3.4.4 | Method of test..... | 272 | +| 8.2.3.4.5 | Test requirement..... | 274 | + +**Annex A (normative): Reference measurement channels..... 275** + +| | | | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| A.1 | IAB-DU and IAB-MT Reference measurement channels..... | 275 | +| A.1.1 | IAB-DU Reference measurement channels..... | 275 | +| A.1.2 | IAB-MT Reference measurement channels..... | 275 | +| A.1.2.1 | Fixed Reference Channels for reference sensitivity level, ACS, in-band blocking, out-of-band blocking and receiver intermodulation (QPSK, R=1/3)..... | 275 | + +| | | | +|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| A.2 | IAB-DU Fixed Reference Channels..... | 276 | +| A.2.1 | Fixed Reference Channels for PUSCH performance requirements (QPSK, R=193/1024)..... | 276 | +| A.2.2 | Fixed Reference Channels for PUSCH performance requirements (16QAM, R=434/1024)..... | 281 | +| A.2.3 | Fixed Reference Channels for PUSCH performance requirements (16QAM, R=658/1024)..... | 282 | +| A.2.4 | Fixed Reference Channels for PUSCH performance requirements (64QAM, R=567/1024)..... | 285 | +| A.2.5 | PRACH Test preambles..... | 287 | +| A.3 | IAB-MT Fixed Reference Channels..... | 287 | +| A.3.1 | Fixed Reference Channels for PDSCH performance requirements (16QAM)..... | 287 | +| A.3.2 | Fixed Reference Channels for PDSCH performance requirements (64QAM)..... | 288 | +| A.3.3 | Fixed Reference Channels for PDSCH performance requirements (256QAM)..... | 289 | +| A.3.4 | Fixed Reference Channels for PDCCH performance requirements..... | 290 | +| A.3.5 | Fixed Reference Channels for CSI reporting requirements..... | 290 | +| Annex B (normative): | Environmental requirements for the BS equipment..... | 293 | +| B.1 | General..... | 293 | +| B.2 | Normal test environment..... | 293 | +| B.3 | Extreme test environment..... | 293 | +| B.3.1 | General..... | 293 | +| B.3.2 | Extreme temperature..... | 293 | +| B.4 | Vibration..... | 294 | +| B.5 | Power supply..... | 294 | +| B.6 | Measurement of test environments..... | 294 | +| B.7 | OTA extreme test methods..... | 295 | +| B.7.1 | Direct far field method..... | 295 | +| B.7.2 | Relative method..... | 295 | +| Annex C (informative): | Test tolerances and derivation of test requirements..... | 297 | +| C.1 | Measurement of transmitter..... | 298 | +| C.2 | Measurement of receiver..... | 304 | +| C.3 | Measurement of performance requirements..... | 306 | +| C.3.1 | IAB-DU Test Tolerances..... | 306 | +| C.3.2 | IAB-MT Test Tolerances..... | 307 | +| C.3.2.1 | Demodulation Performance..... | 307 | +| C.3.2.2 | Channel State Information Reporting..... | 307 | +| Annex D (normative): | Calibration..... | 308 | +| D.1 | General..... | 308 | +| Annex E (informative): | OTA measurement system set-up..... | 309 | +| E.1 | Transmitter..... | 309 | +| E.1.1 | Radiated transmit power, OTA output power dynamics, OTA transmitted signal quality, OTA occupied bandwidth, and OTA transmit ON/OFF power ( IAB type 2-O )..... | 309 | +| E.1.2 | OTA IAB output power, OTA ACLR, OTA operating band unwanted emissions..... | 310 | +| E.1.3 | OTA spurious emissions..... | 310 | +| E.1.4 | OTA co-location emissions, OTA transmit ON/OFF power ( IAB type 1-O )..... | 311 | +| E.1.5 | OTA transmitter intermodulation..... | 312 | +| E.2 | Receiver..... | 312 | +| E.2.1 | OTA sensitivity and OTA reference sensitivity level..... | 312 | +| E.2.2 | OTA dynamic range..... | 313 | +| E.2.3 | OTA adjacent channel selectivity, general OTA blocking, and OTA narrowband blocking..... | 313 | + +| | | | +|---------|--------------------------------------------------------------------|-----| +| E.2.4 | OTA blocking..... | 314 | +| E.2.4.1 | General OTA out-of-band blocking..... | 314 | +| E.2.4.2 | OTA co-location blocking..... | 315 | +| E.2.5 | OTA receiver spurious emissions..... | 315 | +| E.2.6 | OTA receiver intermodulation..... | 316 | +| E.2.7 | OTA in-channel selectivity..... | 316 | +| E.3 | Measurement set-up IAB-MT and IAB-DU performance requirements..... | 317 | +| E.3.1 | PUSCH and PUCCH single antenna port in multipath fading..... | 317 | +| E.3.2 | 2 antenna port PUSCH, PDCCH, PDSCH in multi-path fading..... | 317 | +| E.3.3 | PUSCH, PRACH, CSI in static AWGN..... | 318 | + +**Annex F (normative): Void 320** + +**Annex G (informative): Transmitter spatial emissions declaration.....321** + +| | | | +|-----|-------------------|-----| +| G.1 | General..... | 321 | +| G.2 | Declarations..... | 322 | + +**Annex H (normative): Characteristics of the interfering signals.....323** + +| | | | +|-----|------------------------------------------------------------|-----| +| H.1 | Characteristics of the interfering signals for IAB-DU..... | 323 | +| H.2 | Characteristics of the interfering signals for IAB-MT..... | 323 | + +**Annex I (normative): TRP measurement procedures.....324** + +**Annex J (normative): Propagation conditions.....325** + +| | | | +|-------------|-----------------------------------------------------------------------------|-----| +| J.1 | Static propagation condition..... | 325 | +| J.1.1 | IAB-MT Receiver with 2 Rx..... | 325 | +| J.2 | Multi-path fading propagation conditions..... | 325 | +| J.2.1 | Delay profiles..... | 325 | +| J.2.1.1 | Delay profiles for FR1..... | 327 | +| J.2.1.2 | Delay profiles for FR2-1..... | 328 | +| J.2.2 | Combinations of channel model parameters..... | 328 | +| J.2.3 | MIMO channel correlation matrices..... | 328 | +| J.2.3.1 | MIMO correlation matrices using Uniform Linear Array (ULA)..... | 329 | +| J.2.3.1.1 | Definition of MIMO correlation matrices..... | 329 | +| J.2.3.1.2 | MIMO correlation matrices at high, medium and low level..... | 330 | +| J.2.3.2 | Multi-antenna channel models using cross polarized antennas..... | 332 | +| J.2.3.2.1 | Definition of MIMO correlation matrices using cross polarized antennas..... | 332 | +| J.2.3.2.2 | Spatial correlation matrices at IAB-MT and IAB-DU sides..... | 333 | +| J.2.3.2.2.1 | Spatial correlation matrices at IAB-MT side..... | 333 | +| J.2.3.2.2.2 | Spatial correlation matrices at IAB-DU side..... | 333 | +| J.2.3.2.3 | MIMO correlation matrices using cross polarized antennas..... | 333 | +| J.2.3.2.4 | Beam steering approach..... | 334 | +| J.3 | Physical signals, channels mapping and precoding..... | 335 | +| J.3.1 | General..... | 335 | + +**Annex K (informative): Measuring noise close to noise-floor.....337** + +**Annex L (normative): In-channel TX tests for IAB-DU.....338** + +**Annex M (normative): In-channel TX tests for IAB-MT.....338** + +| | | | +|-----|--------------------|-----| +| M.0 | Applicability..... | 338 | +|-----|--------------------|-----| + +| | | | +|------------------------------------------------------------------------|-----------------------------------------|------------| +| M.1 | General..... | 338 | +| M.2 | Basic principles..... | 338 | +| M.2.1 | Output signal of the TX under test..... | 338 | +| M.2.2 | Ideal signal..... | 339 | +| M.2.3 | Measurement results..... | 339 | +| M.2.4 | Measurement points..... | 339 | +| M.3 | Pre-FFT minimization process..... | 341 | +| M.4 | Timing of the FFT window..... | 341 | +| M.5 | Resource element TX power..... | 342 | +| M.6 | Post-FFT equalisation..... | 343 | +| M.7 | EVM..... | 345 | +| M.7.0 | General..... | 345 | +| M.7.1 | Averaged EVM (TDD)..... | 345 | +| Annex N (normative): General rules for statistical testing..... | | 347 | +| Annex O (informative): Change history..... | | 347 | + +## 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 specifies document the Radio Frequency (RF) test methods and conformance requirements for NR Integrated access and backhaul: *IAB type 1-H*, *IAB type 1-O* and *IAB type 2-O*. These have been derived from, and are consistent with the radiated requirements for *IAB type 1-H*, *IAB type 1-O* and *IAB type 2-O* in BS specification defined in TS 38.174 [2]. + +A *IAB type 1-H* has both conducted and radiated requirements, so it requires compliance to the applicable requirements of the present document and TS 38.176-1 [3]. + +*IAB type 1-O* and *IAB type 2-O* have only radiated requirements, so they require compliance to the present document only. + +# 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.174: "NR; Integrated access and backhaul radio transmission and reception". +- [3] 3GPP TS 38.176-1: " NR; Integrated Access and Backhaul (IAB) conformance testing; Part 1: Conducted conformance testing". +- [4] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception". +- [5] 3GPP TS 38.141-1: "NR, Base Station (BS) conformance testing, Part 1: Conducted conformance testing". +- [6] 3GPP TS 38.141-2: "NR, Base Station (BS) conformance testing, Part 2: Radiated conformance testing". +- [7] 3GPP TS 38.211: "NR; Physical channels and modulation". +- [8] 3GPP TS 38.212: "NR; Multiplexing and channel coding". +- [9] 3GPP TS 38.213: "NR; Physical layer procedures for control". +- [10] Recommendation ITU-R SM.329: "Unwanted emissions in the spurious domain". +- [11] ERC Recommendation 74-01: "Unwanted emissions in the spurious domain". +- [12] Recommendation ITU-R M.1545, "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000". +- [13] Recommendation ITU-R SM.328: "Spectra and bandwidth of emissions". +- [14] "Title 47 of the Code of Federal Regulations (CFR)", Federal Communications Commission. +- [15] 3GPP TR 25.942: "RF system scenarios". +- [16] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". + +- [17] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone". +- [18] 3GPP TS 38.101-4: "NR; User Equipment (UE) radio transmission and reception; Part 4: Performance requirements". +- [19] IEC 60 721-3-3: "Classification of environmental conditions - Part 3-3: Classification of groups of environmental parameters and their severities - Stationary use at weather protected locations". +- [20] IEC 60 721-3-4: "Classification of environmental conditions - Part 3: Classification of groups of environmental parameters and their severities - Clause 4: Stationary use at non-weather protected locations". +- [21] IEC 60 721: "Classification of environmental conditions". +- [22] IEC 60 068-2-1 (2007): "Environmental testing - Part 2: Tests. Tests A: Cold". +- [23] IEC 60 068-2-2: (2007): "Environmental testing - Part 2: Tests. Tests B: Dry heat". +- [24] IEC 60 068-2-6: (2007): "Environmental testing - Part 2: Tests - Test Fc: Vibration (sinusoidal)". +- [25] 3GPP TR 37.941: "Radio Frequency (RF) conformance testing background for radiated Base Station (BS) requirements". +- [26] 3GPP TR 38.901: "Study on channel model for frequencies from 0.5 to 100 GHz". +- [27] 3GPP TS 38.214: "NR; Physical layer procedures for data". +- [28] 3GPP TS 38.521-1: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Range 1 standalone". +- [29] 3GPP TS 38.521-2: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 2: Range 2 standalone". + +--- + +## 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]. + +**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 *IAB type 1-H TAB connectors* at the *transceiver array boundary* + +**Aggregated IAB-DU channel bandwidth:** The RF bandwidth in which an IAB-DU transmits and receives multiple contiguously aggregated carriers. The aggregated IAB-DU channel bandwidth is measured in MHz. + +**Aggregated IAB-MT channel bandwidth:** The RF bandwidth in which an IAB-MT transmits and receives multiple contiguously aggregated carriers. The aggregated IAB-MT channel bandwidth is measured in MHz. + +**Aggregated IAB channel bandwidth:** The RF bandwidth in which IAB-DU and IAB-MT transmit or receives multiple contiguously aggregated carriers simultaneously. The aggregated IAB channel bandwidth is measured in MHz. + +**basic limit:** emissions limit relating to the power supplied by a single transmitter to a single antenna transmission line in ITU-R SM.329 [16] used for the formulation of unwanted emission requirements for FR1 + +**beam:** beam (of the antenna) is the main lobe of the radiation pattern of an *antenna array* + +NOTE: For certain *antenna array*, there may be more than one beam. + +**beam centre direction:** direction equal to the geometric centre of the half-power 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 found + +**beamwidth:** beam which has a half-power contour that is essentially elliptical, the half-power beamwidths in the two pattern cuts that respectively contain the major and minor axis of the ellipse + +**Carrier aggregation:** aggregation of two or more component carriers in order to support wider *transmission bandwidths* + +**Carrier aggregation configuration:** a set of one or more *operating bands* across which the IAB-DU or IAB-MT aggregates carriers with a specific set of technical requirements + +**Channel edge:** lowest or highest frequency of the NR carrier, separated by the *IAB-MT channel bandwidth* or *IAB-DU channel bandwidth*. + +**co-location reference antenna:** a passive antenna used as reference for co-location requirements + +**Contiguous spectrum:** spectrum consisting of a contiguous block of spectrum with no *sub-block gap(s)*. + +**directional requirement:** 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 REFSENS RoAoA* or the *minSENS RoAoA* as appropriate for the receiver + +**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 specific requirement is met. + +NOTE 2: Isotropic directivity is equal in all directions (i.e. 0 dBi). + +**fractional bandwidth:** *fractional bandwidth* FBW is defined as + +$$FBW = 200 \cdot \frac{F_{FBWhigh} - F_{FBWlow}}{F_{FBWhigh} + F_{FBWlow}} \%$$ + +**highest carrier:** The carrier with the highest carrier frequency transmitted/received in a specified frequency band. + +**IAB-DU channel bandwidth:** RF bandwidth supporting a single IAB-DU RF carrier with the *transmission bandwidth* configured in the uplink or downlink + +NOTE 1: The *IAB-DU channel bandwidth* is measured in MHz and is used as a reference for transmitter and receiver RF requirements. + +NOTE 2: It is possible for the IAB to transmit to and/or receive from one or more IAB-MT bandwidth parts that are smaller than or equal to the *IAB transmission bandwidth configuration*, in any part of the *IAB transmission bandwidth configuration*. + +**IAB-donor:** gNB that provides network access to UEs via a network of backhaul and access links. + +**IAB-DU RF Bandwidth:** RF bandwidth in which an IAB-DU transmits and/or receives single or multiple carrier(s) within a supported *operating band* + +**IAB-DU RF Bandwidth edge:** frequency of one of the edges of the *IAB-DU RF Bandwidth*. + +**IAB-MT channel bandwidth:** RF bandwidth supporting a single IAB-MT RF carrier with the *transmission bandwidth* configured in the uplink or downlink + +NOTE 1: The *IAB-MT channel bandwidth* is measured in MHz and is used as a reference for transmitter and receiver RF requirements. + +**IAB-MT RF Bandwidth:** RF bandwidth in which an IAB-MT transmits and/or receives single or multiple carrier(s) within a supported *operating band* + +NOTE: In single carrier operation, the *IAB-MT RF Bandwidth* is equal to the *IAB-MT channel bandwidth*. + +**IAB-MT RF Bandwidth edge:** frequency of one of the edges of the *IAB-MT RF Bandwidth*. + +**IAB RF Bandwidth:** RF bandwidth in which an IAB-DU and/or IAB-MT transmits and/or receives single or multiple carrier(s) within a supported *operating band* + +**IAB RF Bandwidth edge:** frequency of one of the edges of the *IAB RF Bandwidth*. + +**IAB Simultaneous Operation:** IAB-DU and IAB-MT operating with simultaneous transmission, or simultaneous reception. + +**IAB type 1-H:** IAB-DU or IAB-MT operating at FR1 with a *requirement set* consisting of conducted requirements defined at individual *TAB connectors* and OTA requirements defined at RIB + +**IAB type 1-O:** IAB-DU or IAB-MT operating at FR1 with a *requirement set* consisting only of OTA requirements defined at the RIB + +**IAB type 2-O:** IAB-DU or IAB-MT operating at FR2 with a *requirement set* consisting only of OTA requirements defined at the RIB + +**inter-band gap:** The frequency gap between two supported consecutive *operating bands*. + +**Inter RF Bandwidth gap:** frequency gap between two consecutive *IAB-DU and/or IAB-MT RF Bandwidths* that are placed within two supported *operating bands* + +**lowest Carrier:** The carrier with the lowest carrier frequency transmitted/received in a specified frequency band. + +**maximum carrier output power:** mean power level measured per carrier at the indicated interface, during the *transmitter ON period* in a specified reference condition + +**maximum carrier TRP output power:** 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 output power* ( $P_{\text{rated,c,TRP}}$ ) + +**measurement bandwidth:** RF bandwidth in which an emission level is specified + +**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 + +**multi-band connector:** *TAB connector* of *IAB type 1-H* 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 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* + +**Non-contiguous spectrum:** spectrum consisting of two or more *sub-blocks* separated by *sub-block gap(s)*. + +**operating band:** frequency range in which NR operates (paired or unpaired), that is defined with a specific set of technical requirements + +NOTE: The *operating band(s)* for an IAB-DU and IAB-MT are declared by the manufacturer + +**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: 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. + +**OTA REFSENS RoAoA:** 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 beamwidth. + +**OTA sensitivity directions declaration:** set of manufacturer declarations comprising at least one set of declared minimum EIS values (with *IAB-DU* or *IAB-MT channel bandwidth*), and related directions over which the EIS applies + +NOTE: All the directions apply to all the EIS values in an OSDD. + +**Parent node:** IAB-MT's next hop neighbour node; the parent node can be IAB-node or IAB-donor. + +**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 + +**rated beam EIRP:** For a declared beam and *beam direction pair*, the *rated beam EIRP* level is the maximum power that the IAB-DU or IAB-MT is declared to radiate at the associated *beam peak direction* during the *transmitter ON period* + +**rated carrier output power:** mean power level associated with a particular carrier the manufacturer has declared to be available at the indicated interface, during the *transmitter ON period* in a specified reference condition + +**rated carrier TRP output power:** mean power level declared by the manufacturer per carrier, for IAB-DU or IAB-MT operating in single carrier, multi-carrier, carrier aggregation configurations, or *IAB Simultaneous Operation* that the manufacturer has declared to be available at the RIB during the *transmitter ON period* + +**rated total output power:** mean power level associated with a particular *operating band* the manufacturer has declared to be available at the indicated interface, during the *transmitter ON period* in a specified reference condition + +**rated total TRP output power:** mean power level declared by the manufacturer, that the manufacturer has declared to be available at the RIB during the *transmitter ON period* + +**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* + +**receiver target:** AoA in which reception is performed by *IAB type 1-H* or *IAB type 1-O* + +**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 RoAoA:** the *sensitivity RoAoA* associated with the *receiver target reference direction* for each OSDD. + +**requirement set:** one of the NR requirement sets as defined for *IAB type 1-H*, *IAB type 1-O*, and *IAB type 2-O* + +**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 IAB-DU or IAB-MT direction setting + +**single-band connector:** *IAB type 1-H 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 connector*. + +**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 transmission and reception by the same IAB-DU and/or IAB-MT + +NOTE: There may be multiple instances of *sub-blocks* within a *IAB RF Bandwidth*. + +**sub-block gap:** frequency gap between two consecutive sub-blocks within a *IAB 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. + +**TAB connector:** *transceiver array boundary* connector + +**TAB connector RX min cell group:** *operating band* specific declared group of *TAB connectors* to which *IAB type 1-H* conducted 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 *IAB type 1-H* setting corresponding to the declared minimum number of cells with reception 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 *IAB type 1-H* conducted 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 *IAB type 1-H* 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 + +**total radiated power:** is the total power radiated by the antenna + +NOTE: The *total radiated power* is the power radiating in all direction for two orthogonal polarizations. *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 transmission from an IAB-DU or IAB-MT, measured in resource block units + +**transmitter OFF period:** time period during which the IAB-DU or IAB-MT transmitter is not allowed to transmit + +**transmitter ON period:** time period during which the IAB-DU or IAB-MT transmitter is transmitting data and/or reference symbols + +**transmitter transient period:** time period during which the transmitter is changing from the OFF period to the ON period or vice versa + +## 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 | +| $\text{BeW}_{\theta, \text{REFSENS}}$ | Beamwidth equivalent to the OTA REFSENS RoAoA in the $\theta$ -axis in degrees. Applicable for FR1 only. | +| $\text{BeW}_{\phi, \text{REFSENS}}$ | Beamwidth equivalent to the OTA REFSENS RoAoA in the $\phi$ -axis in degrees. Applicable for FR1 only. | +| $\text{BW}_{\text{Channel}}$ | IAB channel bandwidth | +| $\text{BW}_{\text{Channel\_CA}}$ | Aggregated IAB Channel Bandwidth , expressed in MHz. $\text{BW}_{\text{Channel\_CA}} = F_{\text{edge,high}} - F_{\text{edge,low}}$ . | +| $\text{BW}_{\text{Config}}$ | Transmission bandwidth configuration , where $\text{BW}_{\text{Config}} = N_{\text{RB}} \times \text{SCS} \times 12$ | + +| | | +|-----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BW Contiguous | Contiguous transmission bandwidth , i.e. IAB channel bandwidth for single carrier or Aggregated IAB channel bandwidth for contiguously aggregated carriers. For non-contiguous operation within a band the term is applied per sub-block . | +| Δf | Separation between the channel edge frequency and the nominal -3 dB point of the measuring filter closest to the carrier frequency | +| Δf max | f offsetmax minus half of the bandwidth of the measuring filter | +| Δf OBUE | Maximum offset of the operating band unwanted emissions mask from the downlink operating band edge | +| Δf OOB | Maximum offset of the out-of-band boundary from the uplink operating band edge | +| Δ FR2_REFSENS | Offset applied to the FR2 OTA REFSENS depending on the AoA | +| Δ minSENS | Difference between conducted reference sensitivity and minSENS | +| Δ OTAREFSENS | Difference between conducted reference sensitivity and OTA REFSENS | +| EIS minSENS | The EIS declared for the minSENS RoAoA | +| EIS REFSENS | OTA REFSENS EIS value | +| EIS REFSENS_50M | Declared OTA reference sensitivity basis level for FR2 based on a reference measurement channel with 50MHz IAB channel bandwidth | +| Ês | Received energy per RE (power normalized to the subcarrier spacing) during the useful part of the symbol, i.e. excluding the cyclic prefix, at the IAB-MT antenna connector | +| F FBhigh | Highest supported frequency within supported operating band , for which fractional bandwidth support was declared | +| F FBlow | Lowest supported frequency within supported operating band , for which fractional bandwidth support was declared | +| F C,low | The F c of the lowest carrier , expressed in MHz. | +| F C,high | The F c of the highest carrier , expressed in MHz. | +| 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 IAB Channel Bandwidth , expressed in MHz. F edge,low = F C,low - F offset,low . | +| F edge,high | The upper edge of Aggregated IAB Channel Bandwidth , expressed in MHz. F edge,high = F C,high + F offset,high . | +| f offset | Separation between the channel edge frequency and the centre of the measuring | +| f offsetmax | The offset to the frequency Δf OBUE outside the downlink operating band | +| F step,X | Frequency steps for the OTA transmitter spurious emissions (Category B) | +| F UL,low | The lowest frequency of the uplink operating band | +| F UL,high | The highest frequency of the uplink operating band | +| I o | The total received power density, including signal and interference, as measured at the IAB-MT antenna connector. | +| I oc | The power spectral density (integrated in a noise bandwidth equal to the chip rate and normalized to the chip rate) of a band limited noise source (simulating interference from cells, which are not defined in a test procedure) as measured at the IAB-MT antenna connector. | +| I ot | The received power spectral density of the total noise and interference for a certain IAB-MT (power integrated over the RE and normalized to the subcarrier spacing) as measured at the IAB-MT antenna connector | +| | The power spectral density of a white noise source (average power per RE normalised to the subcarrier spacing), simulating interference from cells that are not defined in a test procedure, as measured at the IAB-MT antenna connector | +| N cells | The declared number corresponding to the minimum number of cells that can be transmitted by an IAB type 1-H in a particular operating band | +| N RXU,active | The number of active receiver units. The same as the number of demodulation branches to which compliance is declared for clause 8 performance requirements | +| N RXU,counted | The number of active receiver units that are taken into account for conducted Rx spurious emission scaling, as calculated in clause 7.6.1 | +| N RXU,countedpercell | The number of active receiver units that are taken into account for conducted RX spurious emissions scaling per cell, as calculated in clause 7.6.1 | +| | Timing offset between uplink and downlink radio frames at the UE, as defined in clause 4.2.3 in TS 38.213 [9] | +| N TXU,counted | The number of active transmitter units as calculated in clause 6.1, that are taken into account for conducted TX output power limit in clause 6.2.1, and for unwanted TX emissions scaling | +| N TXU,countedpercell | The number of active transmitter units that are taken into account for conducted TX emissions scaling per cell, as calculated in clause 6.1 | +| P CMAX,f,c | The configured maximum output power for carrier f of serving cell c in each slot | + +| | | +|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| $P_{\max,c,TABC}$ | The maximum carrier output power per TAB connector | +| $P_{\max,c,TRP}$ | Maximum carrier TRP output power measured at the RIB(s), and corresponding to the declared rated carrier TRP output power ( $P_{\text{rated,c,TRP}}$ ) | +| $P_{\max,c,EIRP}$ | The maximum carrier EIRP when the IAB is configured at the maximum rated carrier output TRP ( $P_{\text{rated,c,TRP}}$ ) | +| $P_{\text{rated,c,cell}}$ | The rated carrier output power per TAB connector TX min cell group | +| $P_{\text{rated,c,EIRP}}$ | The rated carrier EIRP output power declared per RIB | +| $P_{\text{rated,c,FBWhigh}}$ | 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,FBWlow}}$ | 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,sys}}$ | The sum of $P_{\text{rated,c,TABC}}$ for all TAB connectors for a single carrier | +| $P_{\text{rated,c,TABC}}$ | The rated carrier output power per TAB connector | +| $P_{\text{rated,c,TRP}}$ | Rated carrier TRP output power declared per RIB | +| $P_{\text{rated,t,TABC}}$ | The rated total output power declared at TAB connector | +| $P_{\text{rated,t,TRP}}$ | Rated total TRP output power declared per RIB | +| $P_{\text{REFSENS}}$ | Conducted Reference Sensitivity power level | +| SSB_RP | Received (linear) average power of the resource elements that carry SSB signals and channels, measured at the IAB-MT antenna connector | +| $T_c$ | Basic time unit, defined in clause 4.1 of TS 38.211 [7] | +| $W_{\text{gap}}$ | Sub-block gap or Inter RF Bandwidth gap size | + +### 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]. + +| | | +|---------|-------------------------------------| +| AA | Antenna Array | +| ACLR | Adjacent Channel Leakage Ratio | +| ACS | Adjacent Channel Selectivity | +| AoA | Angle of Arrival | +| AWGN | Additive White Gaussian Noise | +| BFD | Beam Failure Detection | +| BFD-RS | BFD Reference Signal | +| BLER | Block Error Rate | +| BM-RS | Beam Management Reference Signal | +| BS | Base Station | +| BW | Bandwidth | +| BWP | Bandwidth Part | +| CA | Carrier Aggregation | +| CACLR | Cumulative ACLR | +| CBD | Candidate Beam Detection | +| CCE | Control Channel Element | +| CORESET | Control Resource Set | +| CP | Cyclic Prefix | +| CP-OFDM | Cyclic Prefix-OFDM | +| CSI | Channel-State Information | +| CSI-RS | CSI Reference Signal | +| CW | Continuous Wave | +| DCI | Downlink Control Information | +| DL | Downlink | +| DMRS | Demodulation Reference Signal | +| DM-RS | Demodulation Reference Signal | +| DRX | Discontinuous Reception | +| EIS | Equivalent Isotropic Sensitivity | +| EIRP | Equivalent Isotropic Radiated Power | +| E-UTRA | Evolved UTRA | +| EVM | Error Vector Magnitude | +| FBW | Fractional Bandwidth | +| FR | Frequency Range | + +| | | +|----------|----------------------------------------------------------------------------------------------------------------------------------------| +| FRC | Fixed Reference Channel | +| GSM | Global System for Mobile communications | +| IAB | Integrated Access and Backhaul | +| IAB-DU | IAB Distribution Unit | +| IAB-MT | IAB Mobile Termination | +| ITU-R | Radiocommunication Sector of the International Telecommunication Union | +| ICS | In-Channel Selectivity | +| L1-RSRP | Layer 1 RSRP | +| LA | Local Area | +| MCS | Modulation and Coding Scheme | +| MGRP | Measurement Gap Repetition Period | +| MR | Medium Range | +| NB-IoT | Narrowband – Internet of Things | +| NR | New Radio | +| NR-ARFCN | NR Absolute Radio Frequency Channel Number | +| OBUE | Operating Band Unwanted Emissions | +| OOB | Out-of-band | +| OSDD | OTA Sensitivity Directions Declaration | +| OTA | Over-The-Air | +| PCell | Primary Cell | +| PDCCH | Physical Downlink Control Channel | +| PDSCH | Physical Downlink Shared Channel | +| PCell | Primary Cell | +| PRACH | Physical RACH | +| PDCCH | Physical Downlink Control Channel | +| PDSCH | Physical Downlink Shared Channel | +| PRACH | Physical RACH | +| PRB | Physical Resource Block | +| PSCell | Primary SCell | +| PSS | Primary Synchronization Signal | +| pTAG | Primary Timing Advance Group | +| PUCCH | Physical Uplink Control Channel | +| PUSCH | Physical Uplink Shared Channel | +| QAM | Quadrature Amplitude Modulation | +| QCL | Quasi Co-Location | +| RB | Resource Block | +| RDN | Radio Distribution Network | +| RE | Resource Element | +| REFSENS | Reference Sensitivity | +| REG | Resource Element Group | +| RF | Radio Frequency | +| RIB | Radiated Interface Boundary | +| RLM | Radio Link Monitoring | +| RLM-RS | Reference Signal for RLM | +| RMS | Root Mean Square (value) | +| RoAoA | Range of Angles of Arrival | +| RRC | Radio Resource Control | +| RRM | Radio Resource Management | +| RX | Receiver | +| SCell | Secondary Cell | +| SCS | Sub-Carrier Spacing | +| SMTC | SSB-based Measurement Timing configuration | +| SpCell | Special Cell | +| SRS | Sounding Reference Signal | +| SS-RSRP | Synchronization Signal based Reference Signal Received Power | +| SSB | Synchronization Signal Block | +| SSB_RP | Received (linear) average power of the resource elements that carry NR SSB signals and channels, measured at the UE antenna connector. | +| SSS | Secondary Synchronization Signal | +| TA | Timing Advance | +| TAB | Transceiver Array Boundary | + +| | | +|------|--------------------------------------| +| TCI | Transmission Configuration Indicator | +| TX | Transmitter | +| TRP | Total Radiated Power | +| UTRA | Universal Terrestrial Radio Access | +| WA | Wide Area | + +--- + +## 4 General radiated 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 TS 38.176-2 (the present document), i.e. to all radiated tests defined in FR1 for *IAB type 1-H*, *IAB type 1-O* and radiated tests defined in FR2-1 for *IAB type 2-O*. The frequency ranges FR1 and FR2-1 are defined in clause 5.1 of TS 38.174 [2]. + +The minimum requirements are given in TS 38.174 [2]. Test Tolerances for the radiated test requirements ( $TT_{OTA}$ ) explicitly stated in the present document are given in annex C. + +Test Tolerances are individually calculated for each test. 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. + +The requirements are classified according to spatial characteristics as shown in table 4.1.1-1 and table 4.1.1-2. + +**Table 4.1.1-1: Overview of radiated Tx requirements** + +| Tx requirement | Classification | Coverage range | | Number of conformance directions | +|--------------------------------------|--------------------------------------|-------------------------|----------------------------------|----------------------------------| +| | | FR1 | FR2 | | +| Radiated transmit power | Directional | OTA peak directions set | OTA peak directions set | 5 | +| OTA IAB output power | TRP | See annex I | | | +| OTA output power dynamics | Directional | OTA peak directions set | OTA peak directions set | 1 | +| OTA transmitter OFF power | Co-location | See clause 4.12 | N/A | See clause 4.12 | +| | Directional | N/A | OTA peak directions set (Note 2) | 1 | +| OTA transient period | Co-location | See clause 4.12 | N/A | See clause 4.12 | +| | Directional | N/A | OTA peak directions set (Note 2) | 1 | +| OTA modulation quality | Directional | OTA coverage range | OTA coverage range | 5 | +| OTA frequency error | Directional | OTA coverage range | OTA coverage range | 1 | +| OTA time alignment error | Directional | OTA coverage range | OTA coverage range | 1 | +| OTA occupied bandwidth | Directional | OTA coverage range | OTA coverage range | 1 | +| OTA ACLR | TRP | N/A | N/A | See annex I | +| OTA operating band unwanted emission | TRP | N/A | N/A | See annex I | +| OTA transmitter spurious emission | General requirement | TRP | N/A | See annex I | +| | Additional spurious emissions | TRP | N/A | See annex I | +| | Co-location with other base stations | Co-location | See clause 4.12 | See clause 4.12 | +| OTA transmitter intermodulation | Co-location | See clause 4.12 | N/A | See clause 4.12 | + +NOTE 1: Directional requirement does not imply one compliance direction only. The directional requirement applies to a single direction at a time. + +NOTE 2: For FR2, RF Core requirements are defined on TRP levels. Conformance requirements are verified by EIRP measurements in the reference direction. + +**Table 4.1.1-2: Overview of radiated Rx requirements** + +| Rx requirement | Classification | Applicability levels | | Coverage range | | Number of conformance directions | +|----------------------------------|--------------------------------------|-------------------------|----------------|-------------------------------------|-------------------|----------------------------------| +| | | FR1 | FR2 | FR1 | FR2 | | +| OTA sensitivity | Directional | Minimum EIS | N/A | OSDD | N/A | 5 | +| OTA reference sensitivity | Directional | OTA REFSENS | OTA REFSENS | OTA REFSENS RoAoA | | 5 | +| OTA Dynamic range | Directional | OTA REFSENS | N/A | OTA REFSENS RoAoA | N/A | 1 | +| OTA adjacent channel selectivity | Directional | minSENS | OTA REFSENS | minSENS RoAoA | OTA REFSENS RoAoA | 1 | +| OTA in-band blocking | Directional | OTA REFSENS and minSENS | OTA REFSENS | OTA REFSENS RoAoA and minSENS RoAoA | OTA REFSENS RoAoA | 5 | +| OTA out-of-band blocking | General requirement | Directional | minSENS | OTA REFSENS | minSENS RoAoA | 1 | +| | Co-location with other base stations | Co-location (Note 2) | minSENS | N/A | minSENS RoAoA | 1 | +| OTA receiver spurious emissions | TRP | See clause 7.7 | See clause 7.7 | N/A | N/A | See annex I | +| OTA receiver intermodulation | Directional | OTA REFSENS and minSENS | OTA REFSENS | OTA REFSENS RoAoA and minSENS RoAoA | OTA REFSENS RoAoA | 1 | +| OTA in-channel selectivity | Directional | minSENS | OTA REFSENS | minSENS RoAoA | OTA REFSENS RoAoA | 1 | + +NOTE 1: Directional requirement does not imply one compliance direction only. The directional requirement applies to a single direction at a time. + +NOTE 2: The compliance direction for co-location blocking is applicable for the wanted signal only but not the interfering signal. + +## 4.1.2 Acceptable uncertainty of OTA Test System + +### 4.1.2.1 General + +The maximum acceptable uncertainty of the OTA Test System is specified below for each radiated test defined explicitly in the present specification, where appropriate. + +The OTA Test System shall enable the stimulus signals in the test case to be adjusted to within the specified tolerance and the EUT 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 [25]. + +#### 4.1.2.2 Measurement of transmitter + +The maximum OTA Test System uncertainty for OTA transmitter tests minimum requirements are given in tables 4.1.2.2-1 and 4.1.2.2-2. Details for derivation of OTA Test System uncertainty are given in corresponding clauses in TR 37.941 [25]. + +**Table 4.1.2.2-1: Maximum OTA Test System uncertainty for FR1 OTA transmitter tests** + +| Clause | Maximum OTA Test System uncertainty | +|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6.2 Radiated transmit power | Normal condition:
$\pm 1.1$ dB, $f \leq 3$ GHz
$\pm 1.3$ dB, $3$ GHz $< f \leq 6$ GHz
Extreme condition:
$\pm 2.5$ dB, $f \leq 3$ GHz
$\pm 2.6$ dB, $3$ GHz $< f \leq 6$ GHz | +| 6.3 OTA IAB output power | $\pm 1.4$ dB, $f \leq 3.0$ GHz
$\pm 1.5$ dB, $3.0$ GHz $< f \leq 4.2$ GHz
$\pm 1.5$ dB, $4.2$ GHz $< f \leq 6.0$ GHz | +| 6.4.1 IAB-DU OTA Output Power Dynamics | $\pm 0.4$ dB | +| 6.4.2 IAB-MT OTA Output Power Dynamics | $\pm 0.7$ dB, $BW \leq 40$ MHz
$\pm 1.0$ dB, $40$ MHz $< f \leq 100$ MHz | +| 6.5.1 OTA transmitter OFF power | $\pm 3.4$ dB, $f \leq 3.0$ GHz
$\pm 3.6$ dB, $3.0$ GHz $< f \leq 6$ GHz
(Note 1) | +| 6.5.2 OTA transmitter transient period | N/A | +| 6.6.2.1 IAB-DU OTA Frequency error | $\pm 12$ Hz | + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6.6.2.2 OTA IAB-MT Frequency error | $\pm 15$ Hz, $f \leq 3.0$ GHz
$\pm 36$ Hz, $f > 3.0$ GHz | +| 6.6.3 OTA modulation quality | $\pm 1$ % | +| 6.6.4 OTA time alignment error | $\pm 25$ ns | +| 6.6.5 OTA timing error between IAB-DU and IAB-MT | $\pm 25$ ns | +| 6.7.2 OTA occupied bandwidth | $\pm 100$ kHz, $BW_{\text{Channel}}$ 5 MHz, 10 MHz
$\pm 300$ kHz, $BW_{\text{Channel}}$ 15 MHz, 20 MHz, 25 MHz, 30 MHz, 40 MHz, 50 MHz
$\pm 600$ kHz, $BW_{\text{Channel}}$ 60 MHz, 70 MHz, 80 MHz, 90 MHz, 100 MHz | +| 6.7.3 OTA ACLR/CACL | $f \leq 3.0$ GHz
$\pm 1$ dB, $BW \leq 20$ MHz
$\pm 1$ dB, $BW > 20$ MHz

$3.0$ GHz $< f \leq 6.0$ GHz
$\pm 1.2$ dB, $BW \leq 20$ MHz
$\pm 1.2$ dB, $BW > 20$ MHz

Absolute power $\pm 2.2$ dB, $f \leq 3.0$ GHz
Absolute power $\pm 2.7$ dB, $3.0$ GHz $< f \leq 4.2$ GHz
Absolute power $\pm 2.7$ dB, $4.2$ GHz $< f \leq 6.0$ GHz | +| 6.7.4 OTA operating band unwanted emissions | Absolute power $\pm 1.8$ dB, $f \leq 3.0$ GHz
Absolute power $\pm 2$ dB, $3.0$ GHz $< f \leq 4.2$ GHz
Absolute power $\pm 2$ dB, $4.2$ GHz $< f \leq 6.0$ GHz | +| 6.7.5.2 OTA transmitter spurious emissions, mandatory requirements | $\pm 2.3$ dB, $30$ MHz $< f \leq 6$ GHz
$\pm 4.2$ dB, $6$ GHz $< f \leq 26$ GHz | +| 6.7.5.4 OTA transmitter spurious emissions, additional spurious emissions requirements | $\pm 2.6$ dB, $f \leq 3$ GHz
$\pm 3.0$ , $3$ GHz $< f \leq 4.2$ GHz
$\pm 3.5$ , $4.2$ GHz $< f \leq 6$ GHz | +| 6.7.5.5 OTA transmitter spurious emissions, co-location | $\pm 3.1$ dB, $f \leq 3$ GHz
$\pm 3.3$ dB, $3$ GHz $< f \leq 4.2$ GHz
$\pm 3.4$ , $4.2$ GHz $< f \leq 6$ GHz
(Note 1) | +| 6.8 OTA transmitter intermodulation | The value below applies only to the interfering signal and is unrelated to the measurement uncertainty of the tests in 6.7.3 (ACLR), 6.7.4 (OBUE) and 6.7.5 (spurious emissions) which have to be carried out in the presence of the interferer.
$\pm 3.2$ dB, $f \leq 3.0$ GHz
$\pm 3.4$ dB, $3.0$ GHz $< f \leq 4.2$ GHz
$\pm 3.5$ dB, $4.2$ GHz $< f \leq 6$ GHz
(Note 1) | +| NOTE 1: Fulfilling the criteria for CLTA selection and placement in clause 4.12 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 [25] shall be used for evaluating the test system uncertainty. | | +| NOTE 2: Test system uncertainty values are applicable for normal condition unless otherwise stated. | | + +**Table 4.1.2.2-2: Maximum OTA Test System uncertainty for FR2-1 OTA transmitter tests** + +| Clause | Maximum OTA Test System uncertainty | | +|---------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | IAB-DU | IAB-MT | +| 6.2 Radiated transmit power | Normal condition:
$\pm 1.7$ dB (24.25 – 29.5 GHz)
$\pm 2.0$ dB (37 – 43.5 GHz)
Extreme condition:
$\pm 3.1$ dB (24.25 – 29.5 GHz)
$\pm 3.3$ dB (37 – 43.5 GHz) | Normal condition:
$\pm 2.6$ dB (24.25 – 29.5 GHz)
$\pm 2.6$ dB (37 – 43.5 GHz)
Extreme condition:
$\pm 3.7$ dB (24.25 – 29.5 GHz)
$\pm 3.7$ dB (37 – 43.5 GHz) | +| 6.3 OTA base station output power | $\pm 2.1$ dB (24.25 – 29.5 GHz)
$\pm 2.4$ dB (37 – 43.5 GHz) | $\pm 2.8$ dB (24.25 – 29.5 GHz)
$\pm 2.9$ dB (37 – 43.5 GHz) | +| 6.4.1 IAB-DU OTA Output Power Dynamics | $\pm 0.4$ dB | N/A | +| 6.4.2 IAB-MT OTA Output Power Dynamics | N/A | $\pm 0.7$ dB, BW $\leq 40$ MHz
$\pm 1.0$ dB, 40 MHz $< f \leq 100$ MHz | +| 6.5.1 OTA transmitter OFF power | $\pm 2.9$ dB (24.25 – 29.5 GHz)
$\pm 3.3$ dB (37 – 43.5 GHz) | | +| 6.5.2 OTA transmitter transient period | N/A | | +| 6.6.2 OTA frequency error | $\pm 12$ Hz | $\pm 0.01$ ppm | +| 6.6.3 OTA modulation quality | 1% | | +| 6.6.4 OTA time alignment error | $\pm 25$ ns | | +| 6.6.5 OTA timing error between IAB-DU and IAB-MT | $\pm 25$ ns | | +| 6.7.2 OTA occupied bandwidth | 600 kHz | | +| 6.7.3 OTA ACLR | Relative ACLR:
$\pm 2.3$ dB (24.25 – 29.5 GHz)
$\pm 2.6$ dB (37 – 43.5 GHz)

Absolute ACLR:
$\pm 2.7$ dB (24.25 – 29.5 GHz)
$\pm 2.7$ dB (37 – 43.5 GHz) | Relative ACLR:
$\pm 2.8$ dB (24.25 – 29.5 GHz)
$\pm 2.9$ dB (37 – 43.5 GHz)

Absolute ACLR:
$\pm 2.9$ dB (24.25 – 29.5 GHz)
$\pm 3.0$ dB (37 – 43.5 GHz) | +| 6.7.4 OTA operating band unwanted emissions | $\pm 2.7$ dB (24.25 – 29.5 GHz)
$\pm 2.7$ dB (37 – 43.5 GHz) | $\pm 2.9$ dB (24.25 – 29.5 GHz)
$\pm 3.0$ dB (37 – 43.5 GHz) | +| 6.7.5.2 OTA transmitter spurious emissions, mandatory requirements | $\pm 2.3$ dB, 30 MHz $\leq f \leq 6$ GHz
$\pm 2.7$ dB, 6 GHz $< f \leq 40$ GHz
$\pm 5.0$ dB, 40 GHz $< f \leq 60$ GHz | $\pm 2.3$ dB, 30 MHz $\leq f \leq 6$ GHz
$\pm 2.9$ dB, 6 GHz $< f \leq 40$ GHz
$\pm 5.2$ dB, 40 GHz $< f \leq 60$ GHz | +| 6.7.5.4 OTA transmitter spurious emissions, additional requirements | $\pm 2.3$ dB, 30 MHz $\leq f \leq 6$ GHz
$\pm 2.7$ dB, 6 GHz $< f \leq 40$ GHz
$\pm 5.0$ dB, 40 GHz $< f \leq 60$ GHz | $\pm 2.3$ dB, 30 MHz $\leq f \leq 6$ GHz
$\pm 2.9$ dB, 6 GHz $< f \leq 40$ GHz
$\pm 5.2$ dB, 40 GHz $< f \leq 60$ GHz | + +Note: Test system uncertainty values are applicable for normal condition unless otherwise stated. + +#### 4.1.2.3 Measurement of receiver + +The maximum OTA Test System uncertainty for OTA receiver tests minimum requirements are given in tables 4.1.2.3-1 and 4.1.2.3-2. Details for derivation of OTA Test System uncertainty are given in corresponding clauses in TR 37.941 [25]. + +**Table 4.1.2.3-1: Maximum OTA Test System uncertainty for FR1 OTA receiver tests** + +| Clause | Maximum OTA Test System uncertainty | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 7.2 OTA sensitivity | $\pm 1.3$ dB, $f \leq 3.0$ GHz
$\pm 1.4$ dB, $3.0$ GHz $< f \leq 4.2$ GHz
$\pm 1.6$ dB, $4.2$ GHz $< f \leq 6.0$ GHz | +| 7.3 OTA reference sensitivity level | $\pm 1.3$ dB, $f \leq 3.0$ GHz
$\pm 1.4$ dB, $3.0$ GHz $< f \leq 4.2$ GHz
$\pm 1.6$ dB, $4.2$ GHz $< f \leq 6.0$ GHz | +| 7.4 OTA dynamic range | $\pm 0.3$ dB | +| 7.5.1 OTA adjacent channel selectivity | $\pm 1.7$ dB, $f \leq 3.0$ GHz
$\pm 2.1$ dB, $3.0$ GHz $< f \leq 4.2$ GHz
$\pm 2.4$ dB, $4.2$ GHz $< f \leq 6.0$ GHz | +| 7.5.2 In-band blocking (General) | $\pm 1.9$ dB, $f \leq 3.0$ GHz
$\pm 2.2$ dB, $3.0$ GHz $< f \leq 4.2$ GHz
$\pm 2.5$ dB, $4.2$ GHz $< f \leq 6.0$ GHz | +| 7.5.2 In-band blocking (Narrowband) | $\pm 1.7$ dB, $f \leq 3.0$ GHz
$\pm 2.1$ dB, $3.0$ GHz $< f \leq 4.2$ GHz
$\pm 2.4$ dB, $4.2$ GHz $< f \leq 6.0$ GHz | +| 7.6 OTA out-of-band blocking (General) | $f_{\text{wanted}} \leq 3.0$ GHz:
$\pm 2.0$ dB, $f_{\text{interferer}} \leq 3.0$ GHz
$\pm 2.1$ dB, $3.0$ GHz $< f_{\text{interferer}} \leq 6.0$ GHz
$\pm 3.5$ dB, $6.0$ GHz $< f_{\text{interferer}} \leq 12.75$ GHz

$3$ GHz $< f_{\text{wanted}} \leq 4.2$ GHz:
$\pm 2.0$ dB, $f_{\text{interferer}} \leq 3.0$ GHz
$\pm 2.1$ dB, $3.0$ GHz $< f_{\text{interferer}} \leq 6.0$ GHz
$\pm 3.6$ dB, $6.0$ GHz $< f_{\text{interferer}} \leq 12.75$ GHz

$4.2$ GHz $< f_{\text{wanted}} \leq 6.0$ GHz:
$\pm 2.2$ dB, $f_{\text{interferer}} \leq 3.0$ GHz
$\pm 2.3$ dB, $3.0$ GHz $< f_{\text{interferer}} \leq 6.0$ GHz
$\pm 3.6$ dB, $6.0$ GHz $< f_{\text{interferer}} \leq 12.75$ GHz | +| 7.6 OTA out-of-band blocking (Co-location) (Note 1) | $f_{\text{wanted}} \leq 3.0$ GHz:
$\pm 3.4$ dB, $f_{\text{interferer}} \leq 3.0$ GHz
$\pm 3.5$ dB, $3.0$ GHz $< f_{\text{interferer}} \leq 4.2$ GHz
$\pm 3.7$ dB, $4.2$ GHz $< f_{\text{interferer}} \leq 6.0$ GHz

$3$ GHz $< f_{\text{wanted}} \leq 4.2$ GHz:
$\pm 3.5$ dB, $f_{\text{interferer}} \leq 3.0$ GHz
$\pm 3.6$ dB, $3.0$ GHz $< f_{\text{interferer}} \leq 4.2$ GHz
$\pm 3.7$ dB, $4.2$ GHz $< f_{\text{interferer}} \leq 6.0$ GHz

$4.2$ GHz $< f_{\text{wanted}} \leq 6.0$ GHz:
$\pm 3.6$ dB, $f_{\text{interferer}} \leq 3.0$ GHz
$\pm 3.7$ dB, $3.0$ GHz $< f_{\text{interferer}} \leq 4.2$ GHz
$\pm 3.8$ dB, $4.2$ GHz $< f_{\text{interferer}} \leq 6.0$ GHz | +| 7.7 OTA receiver spurious emissions | $\pm 2.5$ dB, $30$ MHz $\leq f \leq 6.0$ GHz
$\pm 4.2$ dB, $6.0$ GHz $< f \leq 26$ GHz | +| 7.8 OTA receiver intermodulation | $\pm 2.0$ dB, $f \leq 3.0$ GHz
$\pm 2.6$ dB, $3.0$ GHz $< f \leq 4.2$ GHz
$\pm 3.2$ dB, $4.2$ GHz $< f \leq 6.0$ GHz | +| 7.9 OTA in-channel selectivity | $\pm 1.7$ dB, $f \leq 3.0$ GHz
$\pm 2.1$ dB, $3.0$ GHz $< f \leq 4.2$ GHz
$\pm 2.4$ dB, $4.2$ GHz $< f \leq 6.0$ GHz | +| NOTE 1: Fulfilling the criteria for CLTA selection and placement in clause 4.12 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 [25], shall be used for evaluating the test system uncertainty. | | +| NOTE 2: Test system uncertainty values are applicable for normal condition unless otherwise stated. | | + +**Table 4.1.2.3-2: Maximum OTA Test System uncertainty for FR2-1 OTA receiver tests** + +| Clause | Maximum OTA Test System uncertainty | | +|----------------------------------------|--------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------| +| | IAB-DU | IAB-MT | +| 7.3 OTA reference sensitivity level | ±2.4 dB, 24.25 GHz < f ≤ 29.5 GHz
±2.4 dB, 37 GHz < f ≤ 43.5 GHz | ±3.3 dB, 24.25 GHz < f ≤ 29.5 GHz
±3.3 dB, 37 GHz < f ≤ 43.5 GHz | +| 7.5.1 OTA adjacent channel selectivity | ±3.4 dB, 24.25 GHz < f ≤ 29.5 GHz
±3.4 dB, 37 GHz < f ≤ 43.5 GHz | ±4.2 dB, 24.25 GHz < f ≤ 29.5 GHz
±4.2 dB, 37 GHz < f ≤ 43.5 GHz | +| 7.5.2 In-band blocking (General) | ±3.4 dB, 24.25 GHz < f ≤ 29.5 GHz
±3.4 dB, 37 GHz < f ≤ 43.5 GHz | ±4.2 dB, 24.25 GHz < f ≤ 29.5 GHz
±4.2 dB, 37 GHz < f ≤ 43.5 GHz | +| 7.6 OTA out-of-band blocking | ±3.6 dB, 24.25 GHz < f ≤ 29.5 GHz
±3.6 dB, 37 GHz < f ≤ 43.5 GHz | ±4.4 dB, 24.25 GHz < f ≤ 29.5 GHz
±4.4 dB, 37 GHz < f ≤ 43.5 GHz | +| 7.7 OTA receiver spurious emissions | ±2.5 dB, 30 MHz ≤ f ≤ 6 GHz
±2.7 dB, 6 GHz < f ≤ 40 GHz
±5.0 dB, 40 GHz < f ≤ 60 GHz | ±2.5 dB, 30 MHz ≤ f ≤ 6 GHz
±2.9 dB, 6 GHz < f ≤ 40 GHz
±5.2 dB, 40 GHz < f ≤ 60 GHz | +| 7.8 OTA receiver intermodulation | ±3.9 dB, 24.25 GHz < f ≤ 29.5 GHz
±3.9 dB, 37 GHz < f ≤ 43.5 GHz | N/A | +| 7.9 OTA in-channel selectivity | ±3.4 dB, 24.25 GHz < f ≤ 29.5 GHz
±3.4 dB, 37 GHz < f ≤ 43.5 GHz | N/A | + +NOTE: Test system uncertainty values are applicable for normal condition unless otherwise stated. + +#### 4.1.2.4 Measurement of performance requirement + +**Table 4.1.2.4-1: Maximum Test System Uncertainty for FR1 OTA performance requirements** + +| Clause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|---------------------------------------------------------------------|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.1 PUSCH, PUCCH, PRACH with single antenna port and fading channel | ± 0.6 dB | Overall system uncertainty for fading conditions comprises two quantities:
1. Signal-to-noise ratio uncertainty
2. Fading profile power uncertainty

Items 1 and 2 are assumed to be uncorrelated so can be root sum squared:
Test System uncertainty = [SQRT (Signal-to-noise ratio uncertainty 2 + Fading profile power uncertainty 2 )]
Signal-to-noise ratio uncertainty ±0.3 dB
Fading profile power uncertainty ±0.5 dB | +| 8.1 PRACH with single antenna port and AWGN | ± 0.3 dB | Signal-to-noise ratio uncertainty ±0.3 dB | +| 8.1 PUSCH with two antenna port and fading channel | ± 0.8 dB | Overall system uncertainty for fading conditions comprises two quantities:
1. Signal-to-noise ratio uncertainty
2. Fading profile power uncertainty

Items 1 and 2 are assumed to be uncorrelated so can be root sum squared:
Test System uncertainty = [SQRT (Signal-to-noise ratio uncertainty 2 + Fading profile power uncertainty 2 )]
Signal-to-noise ratio uncertainty ±0.3 dB
Fading profile power uncertainty ±0.7 dB for MIMO | +| 8.2 PDCCH with 1Tx and fading channel | ± 0.6 dB | Overall system uncertainty for fading conditions comprises two quantities:
1. Signal-to-noise ratio uncertainty
2. Fading profile power uncertainty

Items 1 and 2 are assumed to be uncorrelated so can be root sum squared:
Test System uncertainty = [SQRT (Signal-to-noise ratio uncertainty 2 + Fading profile power uncertainty 2 )]
Signal-to-noise ratio uncertainty ±0.3 dB
Fading profile power uncertainty ±0.5 dB | +| 8.2 PDSCH, PDCCH, CSI reporting with 2Tx and fading channel | ± 0.8 dB | Overall system uncertainty for fading conditions comprises two quantities:
1. Signal-to-noise ratio uncertainty
2. Fading profile power uncertainty

Items 1 and 2 are assumed to be uncorrelated so can be root sum squared:
Test System uncertainty = [SQRT (Signal-to-noise ratio uncertainty 2 + Fading profile power uncertainty 2 )]
Signal-to-noise ratio uncertainty ±0.3 dB
Fading profile power uncertainty ±0.7 dB for MIMO | +| 8.2 PDSCH, CSI reporting with 4Tx and fading channel | ± 0.8 dB | Overall system uncertainty for fading conditions comprises two quantities:
1. Signal-to-noise ratio uncertainty
2. Fading profile power uncertainty

Items 1 and 2 are assumed to be uncorrelated so can be root sum squared:
Test System uncertainty = [SQRT (Signal-to-noise ratio uncertainty 2 + Fading profile power uncertainty 2 )]
Signal-to-noise ratio uncertainty ±0.3 dB
Fading profile power uncertainty ±0.7 dB for MIMO | + +| Clause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|-----------------------------------------------|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.2 CSI reporting with 8Tx and fading channel | [ $\pm 0.8$ dB] |

Overall system uncertainty for fading conditions comprises two quantities:

  1. 1. Signal-to-noise ratio uncertainty
  2. 2. Fading profile power uncertainty

Items 1 and 2 are assumed to be uncorrelated so can be root sum squared:

Test System uncertainty = [\sqrt{(\text{Signal-to-noise ratio uncertainty}^2 + \text{Fading profile power uncertainty}^2)}]

Signal-to-noise ratio uncertainty \pm 0.3 dB
Fading profile power uncertainty [\pm 0.7 dB] for MIMO

| +| 8.2 CSI reporting with 2Tx and AWGN | $\pm 0.3$ dB | Signal-to-noise ratio uncertainty $\pm 0.3$ dB | + +**Table 4.1.2.4-2: Maximum Test System Uncertainty for FR1 OTA performance requirements** + +| Clause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|---------------------------------------------------------------------|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8.1 PUSCH, PUCCH, PRACH with single antenna port and fading channel | ± 0.6 dB | Overall system uncertainty for fading conditions comprises two quantities:
1. Signal-to-noise ratio uncertainty
2. Fading profile power uncertainty

Items 1 and 2 are assumed to be uncorrelated so can be root sum squared:
Test System uncertainty = [SQRT (Signal-to-noise ratio uncertainty 2 + Fading profile power uncertainty 2 )]
Signal-to-noise ratio uncertainty ±0.3 dB
Fading profile power uncertainty ±0.5 dB | +| 8.1 PRACH with single antenna port and AWGN | ± 0.3 dB | Signal-to-noise ratio uncertainty ±0.3 dB | +| 8.1 PUSCH with two antenna port and fading channel | ± 0.8 dB | Overall system uncertainty for fading conditions comprises two quantities:
1. Signal-to-noise ratio uncertainty
2. Fading profile power uncertainty

Items 1 and 2 are assumed to be uncorrelated so can be root sum squared:
Test System uncertainty = [SQRT (Signal-to-noise ratio uncertainty 2 + Fading profile power uncertainty 2 )]
Signal-to-noise ratio uncertainty ±0.3 dB
Fading profile power uncertainty ±0.7 dB for MIMO | +| 8.2 PDCCH with 1Tx and fading channel | ± 0.6 dB | Overall system uncertainty for fading conditions comprises two quantities:
1. Signal-to-noise ratio uncertainty
2. Fading profile power uncertainty

Items 1 and 2 are assumed to be uncorrelated so can be root sum squared:
Test System uncertainty = [SQRT (Signal-to-noise ratio uncertainty 2 + Fading profile power uncertainty 2 )]
Signal-to-noise ratio uncertainty ±0.3 dB
Fading profile power uncertainty ±0.5 dB | +| 8.2 PDSCH, PDCCH, CSI reporting with 2Tx and fading channel | ± 0.8 dB | Overall system uncertainty for fading conditions comprises two quantities:
1. Signal-to-noise ratio uncertainty
2. Fading profile power uncertainty

Items 1 and 2 are assumed to be uncorrelated so can be root sum squared:
Test System uncertainty = [SQRT (Signal-to-noise ratio uncertainty 2 + Fading profile power uncertainty 2 )]
Signal-to-noise ratio uncertainty ±0.3 dB
Fading profile power uncertainty ±0.7 dB for MIMO | +| 8.2 CSI reporting with 2Tx and AWGN | ± 0.3 dB | Signal-to-noise ratio uncertainty ±0.3 dB | + +#### 4.1.3 Interpretation of measurement results + +The measurement results returned by the OTA Test System are compared - without any modification - against the test requirements as defined by the Shared Risk principle in Recommendation ITU-R M.1545 [12]. + +The actual measurement uncertainty of the OTA Test System for the measurement of each parameter shall be included in the test report. + +The recorded value for the OTA Test System uncertainty shall be, for each OTA measurement, equal to or lower than the appropriate figure in clause 4.1.2 of the present document. + +If the OTA Test System for an OTA 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 OTA Test System over and above that specified in clause 4.1.2 shall be used to tighten the OTA 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 an OTA Test System not compliant with clause 4.1.2 does not increase the chance of passing a EUT where that device would otherwise have failed the test if an OTA Test System compliant with clause 4.1.2 had been used. + +## 4.2 Radiated requirement reference points + +Radiated characteristics for *IAB type 1-H*, *IAB type 1-O* and *IAB type 2-O* are defined over the air (OTA) where the operating band specific radiated interface is referred to as the *Radiated Interface Boundary* (RIB). Radiated requirements are also referred to as OTA requirements. The (spatial) characteristics in which the OTA requirements apply are detailed for each requirement. For *IAB type 1-H* the requirements are defined for two points of reference, signified by radiated requirements at the RIB and the conducted requirements at *transceiver array boundary* (TAB). The OTA requirements of *IAB type 1-H* are tested in the far field (Fraunhofer) region. + +General architecture and reference points of *IAB type 1-H*, *IAB type 1-O* and *IAB type 2-O* are presented on the following figures 4.2-1 and 4.2-2. + +![Figure 4.2-1: General architecture of IAB type 1-H. The diagram shows a 'Transceiver unit array (TRXUA) 1 to M' on the left, connected via horizontal lines to a 'Composite antenna' on the right. The composite antenna consists of a 'Radio Distribution Network (RDN)' and an 'Antenna Array (AA)'. A vertical dashed line labeled 'Transceiver array boundary' separates the TRXUA from the composite antenna. Another vertical dashed line labeled 'Radiated interface boundary (RIB)' is to the right of the composite antenna. Three connectors, labeled #1, #2, and #K, are shown on the TRXUA side of the transceiver array boundary. An arrow points from the text 'Transceiver array boundary connector (TAB)' to these connectors.](9ff1b32449ea068bba9647d71904bd59_img.jpg) + +Figure 4.2-1: General architecture of IAB type 1-H. The diagram shows a 'Transceiver unit array (TRXUA) 1 to M' on the left, connected via horizontal lines to a 'Composite antenna' on the right. The composite antenna consists of a 'Radio Distribution Network (RDN)' and an 'Antenna Array (AA)'. A vertical dashed line labeled 'Transceiver array boundary' separates the TRXUA from the composite antenna. Another vertical dashed line labeled 'Radiated interface boundary (RIB)' is to the right of the composite antenna. Three connectors, labeled #1, #2, and #K, are shown on the TRXUA side of the transceiver array boundary. An arrow points from the text 'Transceiver array boundary connector (TAB)' to these connectors. + +**Figure 4.2-1: General architecture of *IAB type 1-H*** + +The present document details only radiated test requirements and hence only requires the radiated reference points. + +![Figure 4.2-2: General architecture of IAB type 1-O and IAB type 2-O. The diagram shows a 'Transceiver unit array (TRXUA) 1 to P' on the left, connected to a 'Composite antenna' on the right. The 'Composite antenna' is composed of a 'Radio Distribution Network (RDN)' and an 'Antenna Array (AA)'. A dashed line labeled 'Radiated interface boundary (RIB)' is positioned to the right of the antenna array.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +The diagram illustrates the general architecture of IAB type 1-O and IAB type 2-O. On the left, a dashed box represents the 'Transceiver unit array (TRXUA) 1 to P'. This array is connected via a horizontal line to a central dashed box labeled 'Radio Distribution Network (RDN)'. The RDN is further connected to another dashed box on the right labeled 'Antenna Array (AA)'. The RDN and AA together form a 'Composite antenna', indicated by a label below the AA box. A vertical dashed line to the right of the AA box is labeled 'Radiated interface boundary (RIB)'. + +Figure 4.2-2: General architecture of IAB type 1-O and IAB type 2-O. The diagram shows a 'Transceiver unit array (TRXUA) 1 to P' on the left, connected to a 'Composite antenna' on the right. The 'Composite antenna' is composed of a 'Radio Distribution Network (RDN)' and an 'Antenna Array (AA)'. A dashed line labeled 'Radiated interface boundary (RIB)' is positioned to the right of the antenna array. + +**Figure 4.2-2: General architecture of IAB type 1-O and IAB type 2-O** + +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. + +## 4.3 IAB classes + +### 4.3.1 IAB-DU class + +The requirements in the present document apply to Wide Area IAB-DU, Medium Range IAB-DU and Local Area IAB-DU unless otherwise stated. The associated deployment scenarios for each class are exactly the same for IAB-DU with and without connectors. + +For IAB type 1-O and 2-O, IAB-DU classes are defined as indicated below: + +- Wide Area IAB-DU 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 IAB-DU 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 IAB-DU are characterised by requirements derived from Pico Cell scenarios with a BS to UE minimum distance along the ground equal to 2 m. + +The manufacturer shall declare the intended class of the IAB under test. + +### 4.3.2 IAB-MT class + +The requirements in the present document apply to Wide Area IAB-MT and Local Area IAB-MT classes unless otherwise stated. + +For IAB type 1-O, and IAB type 2-O, IAB-MT classes are defined as indicated below: + +- Wide Area IAB-MT are characterised by requirements derived from Macro Cell and/or Micro Cell scenarios. +- Local Area IAB-MT are characterised by requirements derived from Pico Cell and /or Micro Cell scenarios. + +## 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. + +**Table 4.4-1: List of regional requirements** + +| Clause | Requirement | Comments | +|------------------------|-----------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 5.2 | Operating bands | Some NR operating bands may be applied regionally. | +| 6.2.3 | IAB output power:
Additional requirements | These requirements may be applied regionally as additional IAB output power requirements. | +| 9.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 in present specification. | +| 9.7.4.2
9.7.4.3 | OTA operating band unwanted emissions | Category A or Category B operating band unwanted emissions limits may be applied regionally. | +| 9.7.4.4.1 | OTA operating band unwanted emissions:
Limits in FCC Title 47 [14] | The IAB may have to comply with the additional requirements, when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. | +| 9.7.5.2.2
9.7.5.3.2 | OTA Tx spurious emissions | Category A or Category B spurious emission limits, as defined in Recommendation ITU-R SM.329 [2], may apply regionally.
The emission limits for IAB type 1-O specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation. | +| 9.7.5.2.3
9.7.5.3.3 | OTA Tx spurious emissions: additional requirements | These requirements may be applied for the protection of system operating in frequency ranges other than the IAB operating band . | +| 9.8.2 | OTA transmitter intermodulation | Interfering signal positions that are partially or completely outside of any downlink operating band of the IAB are not excluded from the requirement in Japan in Band n77, n78, n79. | +| 10.7.2
10.7.3 | OTA Rx spurious emissions | The emission limits for IAB type 1-O specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation. | + +## 4.5 IAB configurations + +### 4.5.1 Transmit configurations + +Unless otherwise stated, the radiated transmitter characteristics in clause 6 are specified at RIB, with a full complement of transceiver units for the configuration in normal operating conditions. + +![Diagram of transmitter test interfaces showing the IAB, RDN, AA, and measurement equipment.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +This diagram illustrates the transmitter test interfaces for an Integrated Access and Backhaul (IAB) node. The IAB is represented by a dashed rectangle containing two sub-components: the Radio Distribution Network (RDN) and the Antenna Array (AA). The RDN is shown as a dashed rectangle with internal connections, and the AA is another dashed rectangle. The entire IAB assembly is enclosed within a larger dashed rectangle labeled 'Radiated interface boundary'. A large arrow points from the AA to a 'Measurement equipment' block, which is connected to a test antenna. + +Diagram of transmitter test interfaces showing the IAB, RDN, AA, and measurement equipment. + +Figure 4.5.1-1: Transmitter test interfaces + +![Diagram of transmitter test interfaces for co-location concept, including top view and main view.](0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg) + +This diagram shows the transmitter test interfaces for the co-location concept. It consists of two parts: a 'Top view' and a main view. In the 'Top view', a 'Measurement equipment' block is connected to a 'Co-location reference antenna', which is represented by a dashed rectangle. An arrow points from the main view below to this reference antenna. The main view shows the IAB (dashed rectangle) containing the RDN and AA. A large arrow points from the AA to a 'Test antenna', which is connected to a 'Measurement equipment' block. + +Diagram of transmitter test interfaces for co-location concept, including top view and main view. + +Figure 4.5.1-2: Transmitter test interfaces for co-location concept + +### 4.5.2 Receive configurations + +Unless otherwise stated, the radiated receiver characteristics in clause 7 are specified at RIB, with a full complement of transceiver units for the configuration in normal operating conditions. + +![Diagram of receiver test interface showing an IAB unit with Transceiver unit array, RDN, and AA components, connected to measurement equipment via a test antenna.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +The diagram shows an Integrated Access and Backhaul (IAB) unit represented by a large dashed rectangle. Inside, there are three dashed rectangles: 'Transceiver unit array' on the left, 'Radio Distribution Network (RDN)' in the center, and 'Antenna Array (AA)' on the right. The RDN and AA are grouped together under the label 'Composite antenna'. A large hollow arrow points from the AA towards a 'Measurement equipment' box which is connected to a test antenna. + +Diagram of receiver test interface showing an IAB unit with Transceiver unit array, RDN, and AA components, connected to measurement equipment via a test antenna. + +Figure 4.5.2-1: Receiver test interface + +![Diagram of receiver test interfaces for co-location concept, showing a top view of measurement equipment connected to a co-location reference antenna, which is then connected to the IAB unit's antenna array via a test antenna.](34b047489058d6400b412cd0ae2334ba_img.jpg) + +This diagram illustrates the co-location concept for receiver test interfaces. At the top, a 'Top view' shows 'Measurement equipment' connected to a 'Co-location reference antenna' (a dashed rectangle). A large hollow arrow points down to a lower level. On this lower level, the 'IAB' unit (dashed rectangle) contains 'Transceiver unit array', 'Radio Distribution Network (RDN)', and 'Antenna Array (AA)' (grouped as 'Composite antenna'). A 'Test antenna' connected to 'Measurement equipment' is shown on the right, with a large hollow arrow pointing from it into the 'Antenna Array (AA)'. + +Diagram of receiver test interfaces for co-location concept, showing a top view of measurement equipment connected to a co-location reference antenna, which is then connected to the IAB unit's antenna array via a test antenna. + +Figure 4.5.2-2: Receiver test interfaces for co-location concept + +### 4.5.3 Power supply options + +If the IAB 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.5.4 IAB 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.6 Manufacturer's declarations + +The following IAB manufacturer's declarations listed in table 4.6-1, when applicable to the IAB under test, are required to be provided by the manufacturer for radiated requirements testing for *IAB type 1-H*, *IAB type 1-O* and *IAB type 2-O*. Declarations may be provided independently for IAB-MT and IAB-DU. The applicability columns for different IAB-types in table 4.6-1 designate applicability for both IAB-DU and IAB-MT, unless otherwise stated. + +For the *IAB type 1-H* declarations required for the conducted requirements testing, refer to TS 38.176-1 [3], clause 4.6. + +**Table 4.6-1: Manufacturers declarations for *IAB type 1-H*, *IAB type 1-O* and *IAB type 2-O* radiated test requirements** + +| Declaration identifier | Declaration | Description | Applicability (Note 1) | | | +|------------------------|-----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|---------------------|---------------------| +| | | | IAB type 1-H (Note 2) | IAB type 1-O | IAB type 2-O | +| D.1 | Coordinate system reference point | Location of coordinated system reference point in reference to an identifiable physical feature of the IAB-MT or IAB-DU enclosure. | x | x | x | +| D.2 | Coordinate system orientation | Orientation of the coordinate system in reference to an identifiable physical feature of the IAB enclosure. | x | x | x | +| D.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, corresponds 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_\theta and narrowest intended BeW_\phi possible when narrowest intended BeW_\theta 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_\theta and widest intended BeW_\phi possible when widest intended BeW_\theta 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.

When selecting the above five beam widths for declaration, all beams that the IAB 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.

(Note 3)

| x | x | x | + +| Declaration identifier | Declaration | Description | Applicability
(Note 1) | | | +|------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|---|---| +| | | | C | X | X | +| D.4 | Operating bands and frequency ranges | List of NR operating band(s) supported by the IAB-DU or IAB-MT and if applicable, frequency range(s) within the operating band(s) that the IAB can operate in supported bands declared for every beam (D.3).
(Note 4) | c | x | x | +| D.5 | IAB requirements set | Declaration of one of the IAB requirement's set as defined for IAB type 1-H, IAB type 1-O, or IAB type 2-O . | c | x | x | +| D.6 | IAB class | Declared as Wide Area IAB-DU, Medium Range IAB-DU, or Local Area IAB-DU.
Declared as Wide Area IAB-MT, or Local Area IAB-MT. | c | x | x | +| D.7 | IAB channel band width and SCS support | IAB-DU or IAB-MT supported SCS and channel bandwidth per supported SCS. Declared for each beam (D.3) and each operating band (D.4). | c | x | x | +| D.8 | OTA peak directions set reference beam direction pair | The beam direction pair, describing the reference beam peak direction and the reference beam centre direction. Declared for every beam (D.3). | x | x | x | +| D.9 | OTA peak directions set | The OTA peak directions set for each beam. Declared for every beam (D.3). | x | x | x | +| D.10 | OTA peak directions set maximum steering direction(s) | The beam direction pair(s) corresponding to the following points:
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) 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) 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) 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 (D.3). | x | x | x | +| D.11 | 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 (D.10), as well as the reference beam direction pair (D.8). Declared for every beam (D.3).
(Note 12, 14, 18) | x | x | x | +| D.12 | Beamwidth | The beamwidth for the reference beam direction pair and the four maximum steering directions. Declared for every beam (D.3). | x | x | x | + +| Declaration identifier | Declaration | Description | Applicability
(Note 1) | | | +|------------------------|------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|---|-----| +| | | | | | | +| D.13 | 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 (D.4 – D.12) made for the beams are identical and the transmitter unit, RDN and antenna array responsible for generating the beam are of identical design. | x | x | x | +| D.14 | Parallel beams | List of beams which have been declared equivalent (D.13) 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. | x | x | x | +| D.15 | Number of carriers at maximum TRP | The number of carriers per operating band the IAB is capable of generating at maximum TRP declared for every beam (D.3). | n/a | x | x | +| D.16 | Operating bands with multi-band dependencies | List of operating bands which are generated using transceiver units supporting operation in multiple operating bands through common active RF components. Declared for each operating band for which multi-band transceiver is used. | c | x | n/a | +| D.17 | Maximum radiated IAB RF Bandwidth | Maximum Base Station RF Bandwidth in the operating band , declared for each supported operating band (D.4).
(Note 15) | c | x | x | +| D.18 | 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 (D.16). | c | x | n/a | +| D.19 | Total RF bandwidth ( $BW_{tot}$ ) | Total RF bandwidth $BW_{tot}$ of transmitter and receiver, declared per the band combinations (D.52). | c | x | x | +| D.20 | CA-only operation | Declared of CA-only (with equal power spectral density among carriers) but not multiple carriers operation, declared per operating band (D.4) and per beam (D.3). | c | x | x | +| D.21 | Maximum number of supported carriers per operating band in multi-band operations | Maximum number of supported carriers per supported operating band declared to have multi-band dependencies (D.16). | c | x | n/a | +| D.22 | Contiguous or non-contiguous spectrum operation support | Ability of IAB-DU or IAB-MT to support contiguous or non-contiguous (or both) frequency distribution of carriers when operating multi-carrier in an operating band. | c | x | x | +| D.23 | OSDD identifier | A unique identifier for the OSDD. | x | x | n/a | +| D.24 | OSDD operating band support | Operating band supported by the OSDD, declared for every OSDD (D.23).
(Note 5) | x | x | n/a | +| D.25 | OTA sensitivity supported IAB channel bandwidth and SCS | The IAB-DU or IAB-MT supported SCS and channel bandwidth per supported SCS by each OSDD. | x | x | n/a | +| D.26 | Redirection of receiver target support | Ability to redirect the receiver target related to the OSDD. | x | x | n/a | + +| Declaration identifier | Declaration | Description | Applicability (Note 1) | | | +|------------------------|------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----|-----| +| | | | | | | +| D.27 | Minimum EIS for FR1 ( $EIS_{minSENS}$ ) | The minimum $EIS_{minSENS}$ requirement (i.e. maximum allowable EIS value) applicable to all sensitivity RoAoA per OSDD. Declared per NR supported channel BW for the OSDD (D.30).
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 6) | x | x | n/a | +| D.28 | EIS REFSSENS for FR2-1 ( $EIS_{REFSENS\_50M}$ ) | The $EIS_{REFSENS\_50M}$ level applicable in the OTA REFSSENS RoAoA, (used as a basis for the derivation of the FR2-1 $EIS_{REFSENS}$ for other channel bandwidths supported by IAB). (Note 7) | n/a | n/a | x | +| D.29 | Receiver target reference direction
Sensitivity Range of Angle of Arrival | The sensitivity RoAoA associated with the receiver target reference direction (D.31) for each OSDD. | x | x | n/a | +| D.30 | 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.
(Note 8) | x | x | n/a | +| D.31 | Receiver target reference direction | For each OSDD an associated direction inside the receiver target redirection range (D.30).
(Note 9) | x | x | n/a | +| D.32 | Conformance test directions sensitivity RoAoA | For each OSDD that includes a receiver target redirection range, four sensitivity RoAoA comprising the conformance test directions (D.33). | x | x | n/a | + +| Declaration identifier | Declaration | Description | Applicability (Note 1) | | | +|------------------------|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---|-----| +| D.33 | 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.
| x | x | n/a | + +| Declaration identifier | Declaration | Description | Applicability
(Note 1) | | | +|------------------------|-----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|---|-----| +| | | | | | | +| D.34 | OTA coverage range | Declared as a single range of directions within which selected TX OTA requirements are intended to be met.
(Note 10) | x | x | x | +| D.35 | OTA coverage range reference direction | The direction describing the reference direction of the OTA coverage range (D.34).
(Note 11) | x | x | x | +| D.36 | 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. | x | x | x | +| D.37 | The rated carrier OTA IAB power, $P_{\text{rated,c,TRP}}$ | $P_{\text{rated,c,TRP}}$ is declared as TRP OTA power per carrier, declared per supported operating band.
(Notes 12, 14, 18) | n/a | x | x | +| D.38 | Rated transmitter TRP, $P_{\text{rated,t,TRP}}$ | Rated total radiated output power.
Declared per supported operating band .
(Notes 12, 14, 18) | n/a | x | x | +| D.39 | CLTA placement for co-location test | The manufacturer shall declare the side of EUT where radiating elements are placed closest to the edge of EUT when applicable. The CLTA shall be placed at the EUT side where radiating elements are placed closest. | n/a | x | n/a | +| D.40 | Spurious emission category | Declare the IAB-DU or IAB-MT 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 [5]. | c | x | x | +| D.41 | Additional operating band unwanted emissions | The manufacturer shall declare whether the IAB under test is intended to operate in geographic areas where the additional operating band unwanted emission limits defined in clause 6.7.4 apply. | c | x | x | +| D.42 | Co-existence with other systems | The manufacturer shall declare whether the IAB 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. | c | x | x | +| D.43 | Co-location with other base stations | The manufacturer shall declare whether the IAB 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. | c | x | n/a | +| D.44 | Single-band RIB or multi-band RIB | List of single-band RIB and/or multi-band RIB for the supported operating bands (D.4). | c | x | n/a | +| D.45 | Single or multiple carrier | IAB capability to operate with a single carrier (only) or multiple carriers. Declared per supported operating band, per RIB.
(Note 17) | c | x | x | + +| Declaration identifier | Declaration | Description | Applicability
(Note 1) | | | +|------------------------|-------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-----|-----| +| | | | c | x | x | +| D.46 | Maximum number of supported carriers per operating band | Maximum number of supported carriers. Declared per supported operating band, per RIB. (Note 15) | c | x | x | +| D.47 | Total maximum number of supported carriers | Maximum number of supported carriers for all supported operating bands. Declared per RIB. | c | x | x | +| D.48 | Other band combination multi-band restrictions | Declare any other limitation under simultaneous operation in the declared band combinations (D.16), which have any impact on the test configuration generation. | c | x | n/a | +| D.49 | N cells | Number corresponding to the minimum number of cells that can be transmitted by an IAB-DU or IAB-MT in a particular operating band . Declared per operating band (D.4). | c | n/a | n/a | +| D.50 | Maximum supported power difference between carriers | Maximum supported power difference between carriers in each supported operating band . Declared per operating band (D.4). | c | x | x | +| D.51 | Maximum supported power difference between carriers in different operating bands | Maximum supported power difference between any two carriers in any two different supported operating bands . Declared per operating bands combination (D.52). (Note 19) | c | x | n/a | +| D.52 | Operating band combination support | List of operating bands combinations supported by single-band RIB(s) and/or multi-band RIB(s) of the IAB-DU or IAB-MT. | c | x | n/a | +| D.53 | OTA REFSSENS RoAoA | Range of angles of arrival associated with the OTA REFSSENS. | n/a | x | x | +| D.54 | OTA REFSSENS receiver target reference direction | Reference direction inside the OTA REFSSENS RoAoA (D.53). | n/a | x | x | +| D.55 | OTA REFSSENS conformance test directions | The following four OTA REFSSENS conformance test directions shall be declared:
1) The direction determined by the maximum $\phi$ value achievable inside the OTA REFSSENS RoAoA, while $\theta$ value being the closest possible to the OTA REFSSENS receiver target reference direction.
2) The direction determined by the minimum $\phi$ value achievable inside the OTA REFSSENS RoAoA, while $\theta$ value being the closest possible to the OTA REFSSENS receiver target reference direction.
3) The direction determined by the maximum $\theta$ value achievable inside the OTA REFSSENS RoAoA, while $\phi$ value being the closest possible to the OTA REFSSENS receiver target reference direction.
4) The direction determined by the minimum $\theta$ value achievable inside the OTA REFSSENS RoAoA, while $\phi$ value being the closest possible to the OTA REFSSENS receiver target reference direction. | n/a | x | x | +| D.56 | 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%. | x | x | x | +| D.57 | Rated beam EIRP at lower end 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 (D.10), as well as the reference beam direction pair (D.8). Declared per beam for all supported frequency ranges (D.56). (Notes 12, 13, 14, 15, 18) | x | x | x | + +| Declaration identifier | Declaration | Description | Applicability
(Note 1) | | | +|------------------------|---------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-----|-----| +| | | | | | | +| D.58 | 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 (D.10), as well as the reference beam direction pair (D.8).
Declared per beam for all supported frequency ranges in (D.56).
(Notes 12, 13, 14, 15, 18) | x | x | x | +| D.59 | Relation between supported maximum RF bandwidth, number of carriers and Rated maximum TRP | If the rated transmitter TRP and total number of supported carriers are not simultaneously supported, the manufacturer shall declare the following additional parameters:
- The reduced number of supported carriers at the rated transmitter TRP;
- The reduced total output power at the maximum number of supported carriers. | n/a | x | x | +| D.60 | Inter-band CA | Declaration of operating band(s) combinations supporting inter-band CA. Declared per operating band combination (D.52). | c | x | x | +| D.61 | Intra-band contiguous CA | Declaration of operating band(s) supporting intra-band contiguous CA. Declared per operating band with CA support. | c | x | x | +| D.62 | Intra-band non-contiguous CA | Declaration of operating band(s) supporting intra-band non-contiguous CA. Declared per operating band with CA support. | c | x | x | +| D.63 | Total maximum number of supported carriers in multi-band operation | Maximum number of supported carriers for all supported operating bands declared to have multi-band dependencies (D.16). | c | x | n/a | +| D.IAB-1 | Same RF implementation | Declaration whether IAB-MT and IAB-DU have the same RF implementation. | c | x | x | +| D.IAB-2 | IAB-MT test model PT-RS configuration | Declaration of PT-RS configuration in IAB-MT test model: without PT-RS, with PT-RS or both. | n/a | n/a | x | +| D.IAB-3 | IAB simultaneous operation | Declare support of IAB simultaneous operation, simultaneous transmission, or simultaneous reception or both. | c | x | x | +| D.IAB-4 | Maximum power imbalance for IAB simultaneous transmission | Declare the maximum PSD offset in dB of IAB-MT carrier and IAB-DU carrier for IAB simultaneous transmission | c | x | x | +| D.100 | PUSCH mapping type | IAB-DU only: Declaration of the supported PUSCH mapping type for FR1 as specified in TS 38.211 [7], i.e., type A, type B or both. | c | x | n/a | +| D.101 | PUSCH additional DM-RS positions | IAB-DU only: Declaration of the supported additional DM-RS position(s) for FR2-1, i.e., pos0, pos1, or both. | n/a | n/a | x | +| D.102 | PUCCH format | IAB-DU only: Declaration of the supported PUCCH format(s) as specified in TS 38.211 [7], i.e., format 0, format 1, format 2, format 3, format 4. | c | x | x | +| D.103 | PRACH format and SCS | IAB-DU only: Declaration of the supported PRACH format(s) as specified in [x], i.e., format: 0, A1, A2, A3, B4, C0, C2.
Declaration of the supported SCS(s) per supported PRACH format with short sequence, as specified in TS 38.211 [7], i.e.:
- For IAB type 1-O : 15 kHz, 30 kHz or both.
- For IAB type 2-O : 60 kHz, 120 kHz or both. | c | x | x | +| D.104 | Additional DM-RS for PUCCH format 3 | IAB-DU only: Declaration of the supported additional DM-RS for PUCCH format 3: without additional DM-RS, with additional DM-RS or both. | c | x | x | + +| Declaration identifier | Declaration | Description | Applicability
(Note 1) | | | +|------------------------|---------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-----|-----| +| | | | c | x | x | +| D.105 | Additional DM-RS for PUCCH format 4 | IAB-DU only: Declaration of the supported additional DM-RS for PUCCH format 4: without additional DM-RS, with additional DM-RS or both. | c | x | x | +| D.106 | PUSCH PT-RS | IAB-DU only: Declaration of PT-RS in PUSCH support: without PT-RS, with PT-RS or both. | n/a | n/a | x | +| D.107 | PUCCH multi-slot | Declaration of multi-slot PUCCH support. | c | x | n/a | +| D.108 | UL CA | IAB-DU only: For the highest supported SCS, declaration of the carrier combination with the largest aggregated bandwidth. If there is more than one combination, the carrier combination with the largest number of carriers shall be declared. | c | x | x | +| D.109 | Modulation order | IAB-DU only: Declaration of the supported modulation orders: QPSK, 16QAM, 64QAM | c | x | x | +| D.110 | Transform precoding | IAB-DU only: Declaration on the supporting of transform precoding | c | x | x | +| D.200 | 256QAM for PDSCH for FR1 | Declaration of the supported of 256QAM modulation scheme for PDSCH for FR1, i.e. supported or not supported. | c | x | n/a | +| D.201 | Maximum number of ports across all configured NZP-CSI-RS resources per CC | Declaration of the maximum number of ports across all configured NZP-CSI-RS resources per CC, i.e. 2, 4, 8, 12, 16, 24, 32, 40, 48 ... ,256 or not supported. | c | x | n/a | +| D.202 | Maximum number of PDSCH MIMO layers | Declaration of the the maximum number of spatial multiplexing layer(s) supported by the UE for DL reception, i.e. 2, 4, 8 or not supported. | c | x | x | +| D.203 | 1 port of DL PTRS | Declaration of the supported of PT-RS with 1 antenna port in DL reception, i.e. supported or not supported. | n/a | n/a | x | + +| Declaration identifier | Declaration | Description | Applicability (Note 1) | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|------------------------| +| NOTE 1: | Manufacturer declarations applicable per IAB requirement set were marked as "x". Manufacturer declarations not applicable per IAB requirement set were marked as "n/a". | | | +| NOTE 2: | For IAB type 1-H , the only radiated declarations are related to EIRP and EIS requirements. For IAB type 1-H declarations required for the conducted requirements testing, refer to TS 38.176-1 [3]. For declarations marked as 'c', related conducted declarations in TS 38.176-1 [3] apply. When separately declared, they shall still use the same declaration identifier. | | | +| NOTE 3: | Depending on the capability of the system some of these beams may be the same. For those same beams, testing is not repeated. | | | +| NOTE 4: | These operating bands are related to their respective single-band RIBs. | | | +| NOTE 5: | As each identified OSDD has a declared minimum EIS value (D.27), multiple operating band can only be declared if they have the same minimum EIS declaration. | | | +| NOTE 6: | If the IAB type 1-H or IAB type 1-O is not capable of redirecting the receiver target related to the OSDD then there is only one RoAoA applicable to the OSDD. | | | +| NOTE 7: | Although EIS REFSENS_50M level is based on a reference measurement channel with BW Channel = 50 MHz, it does not imply that IAB-DU or IAB-MT has to support 50 MHz channel bandwidth. | | | +| NOTE 8: | Not applicable for IAB type 2-O . | | | +| NOTE 9: | For an OSDD without receiver target redirection range, this is a direction inside the sensitivity RoAoA. | | | +| NOTE 10: | OTA coverage range is used for conformance testing of such TX OTA requirements as occupied bandwidth, frequency error, TAE or EVM. | | | +| NOTE 11: | The OTA coverage reference direction may be the same as the Reference beam direction pair (D.8) but does not have to be. | | | +| NOTE 12: | If an IAB type 2-O is capable of 64QAM DL operation but not capable of 256QAM DL operation, then up to two rated output power declarations may be made. One declaration is applicable when configured for 64QAM transmissions and the other declaration is applicable when not configured for 64QAM transmissions. | | | +| NOTE 13: | If D.57 and D.58 are declared for certain frequency range (D.56), there shall be no "Rated beam EIRP" declaration (D.11) for the operating band containing that particular frequency range. | | | +| NOTE 14: | If an IAB type 1-H or IAB type 1-O is capable of 256QAM 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 15: | Parameters for contiguous or non-contiguous spectrum operation in the operating band are assumed to be the same unless they are separately declared. | | | +| NOTE 16: | void | | | +| NOTE 17: | In case of IAB type 1-H , this declaration applies per TAB connector . | | | +| NOTE 18: | If a IAB type 2-O is capable of 256QAM DL operation, then up to three rated output power declarations may be made. One declaration is applicable when configured for 256QAM transmissions, a different declaration is applicable when configured for 64QAM transmissions and the other declaration is applicable when not configured neither for 256QAM nor 64QAM transmissions. | | | +| NOTE 19: | The power difference is declared at highest rated output power (D.38). | | | +| NOTE 20: | For declaration applied both IAB-MT and IAB-DU, it can be applied to IAB simultaneous operation where applicable. | | | + +## 4.7 Test configurations + +### 4.7.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.6. + +The applicable test models for generation of the carrier transmit test signal are defined in clause 4.9.2. + +NOTE: If required, carriers are shifted to align with the channel raster. + +### 4.7.2 Test signal configurations + +#### 4.7.2.1 Test signal used to build Test Configurations + +The signal's *IAB-DU and IAB-MT channel bandwidth* and subcarrier spacing used to build IAB-DU and IAB-MT Test Configurations shall be selected according to tables 4.7.2.1-1 and 4.7.2.1-2. + +**Table 4.7.2.1-1: Signal to be used to build IAB TCs for IAB type 1-H and IAB type 1-O** + +| Operating band characteristics | | FDL_high – FDL_low < 100 MHz | FDL_high – FDL_low ≥ 100 MHz | +|------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------------------------------------------------------------|-----------------------------------------------------------| +| TC signal characteristics | BW channel | 10 MHz (Note) | 20 MHz (Note) | +| | Subcarrier spacing | Smallest supported subcarrier spacing declared per operating band (D.7) | | +| NOTE: If this IAB channel bandwidth is not supported, the narrowest supported IAB channel bandwidth declared per operating band (D.7) shall be used. | | | | + +**Table 4.7.2.1-2: Signal to be used to build IAB TCs for IAB type 2-O** + +| Operating band characteristics | | FDL_high – FDL_low ≤ 3250 MHz | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------------------------------------------------------------------| +| TC signal characteristics | BW channel | 100 MHz (Note 1, Note 2) | +| | Subcarrier spacing | Smallest supported subcarrier spacing declared per operating band (D.7) | +| NOTE 1: IAB vendor can decide to test with 50 MHz IAB channel bandwidth and smallest supported SCS declared per operating band (D.7) instead of 100 MHz IAB channel bandwidth in certain regions, where spectrum allocation and regulation require testing with 50 MHz.
NOTE 2: If this IAB channel bandwidth is not supported, the narrowest supported IAB channel bandwidth declared per operating band (D.7) shall be used. | | | + +#### 4.7.2.2 IABTC1: Contiguous spectrum operation + +The purpose of test configuration IABTC1 is to test all IAB-DU and IAB-MT requirements excluding CA occupied bandwidth. + +For IABTC1 used in receiver tests only the two outermost UL carriers and two outermost DL carriers within each supported operating band need to be generated by the test equipment. + +##### 4.7.2.2.1 IABTC1 generation + +IABTC1 shall be constructed on a per band basis using the following method: + +- The *IAB RF Bandwidth* of each supported operating band shall be the declared maximum radiated *IAB RF Bandwidth* for contiguous operation (D.17). +- For IAB not supporting simultaneous transmission between IAB-DU and IAB-MT, select the IAB-DU and IAB-MT carrier to be tested according to 4.7.2.1 and place them adjacent to the lower *IAB-DU and IAB-MT RF Bandwidth edge*. Place same signals adjacent to the upper *IAB-DU and IAB-MT RF Bandwidth edge*. +- For IAB supporting simultaneous transmission between IAB-DU and IAB-MT, select the IAB UL carrier to be tested according to 4.7.2 and place it adjacent to the lower IAB RF Bandwidth edge. Place the same IAB UL carrier adjacent to the upper IAB RF Bandwidth edge. Select the IAB DL carrier to be tested according to 4.7.2.1 and place it adjacent to the already placed IAB UL carrier at the lower IAB RF Bandwidth edge. Place the same IAB DL carrier adjacent to the already placed IAB UL carrier at the upper. +- For transmitter tests, select as many IAB-DU and IAB-MT carriers (according to 4.7.2.1) that the beam supports within a band and that fit in the rest of the declared maximum *IAB RF Bandwidth*. Place the carriers adjacent to each other starting from the upper *IAB RF Bandwidth edge*. The nominal carrier spacing defined in TS 38.174 [2] clause 5.4.1 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 (D.60). All configured component carriers are transmitted simultaneously in the tests where the transmitter should be on. + +#### 4.7.2.2.2 IABTC1 power allocation + +Set the number of carriers to the number of carriers at maximum TRP (D.15). + +For EIRP accuracy requirements set each beam to rated beam EIRP (D.11) 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 the rated transmitter TRP $P_{\text{rated,t,TRP}}$ (D.38). + +For a beam declared to support CA-only operation (D.20), 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.7.2.3 IABTC2: Contiguous CA occupied bandwidth + +IABTC2 in this clause is used to test CA occupied bandwidth. + +##### 4.7.2.3.1 IABTC2 generation + +IABTC2 shall be constructed on a per band basis using the following method: + +- All component carrier combinations supported by the beam, which have different sum of channel bandwidths of component carrier, shall be tested. For all component carrier combinations which have the same sum of channel bandwidths of component carriers, only one of the component carrier combinations shall be tested. +- Of all component carrier combinations which have same sum of channel bandwidths of component carrier, select those with the narrowest carrier with the smallest supported subcarrier spacing declared per *operating band* (D.7) at the lower *IAB RF Bandwidth edge*. +- Of the combinations selected in the previous step, select one with the narrowest carrier with the smallest supported subcarrier spacing declared per *operating band* (D.7) at the upper *IAB 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 with the smallest supported subcarrier spacing declared per *operating band* (D.7) being adjacent to the lowest carrier. +- If there are multiple combinations fulfilling previous steps, select the one with the widest carrier with the smallest supported subcarrier spacing declared per *operating band* (D.7) being adjacent to the highest carrier. +- If there are multiple combinations fulfilling previous steps, select the one with the widest carrier with the smallest supported subcarrier spacing declared per *operating band* (D.7) 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 channel spacing defined in TS 38.174 [2] clause 5.4.1 shall apply. + +##### 4.7.2.3.2 IABTC2 power allocation + +Set the number of carriers to the number of carriers at maximum TRP (D.15). + +For EIRP accuracy requirements set each beam to rated beam EIRP (D.11) for the tested *beam direction pair*. + +Set the power spectral density of each carrier to the same level so that the sum of the carrier powers equals the rated transmitter TRP $P_{\text{rated,t,TRP}}$ (D.38). + +#### 4.7.2.4 IABTC3: Non-contiguous spectrum operation + +The purpose of IABTC3 is to test NR multicarrier non-contiguous aspects. + +For IABTC3 used in receiver tests, outermost DL and UL carriers for each sub-block need to be generated by the test equipment; other supported carriers are optional to be generated. + +#### 4.7.2.4.1 IABTC3 generation + +IABTC3 is constructed on a per band basis using the following method: + +- The *IAB RF Bandwidth* of each supported operating band shall be the declared maximum radiated *IAB RF Bandwidth* for non-contiguous operation (D.17). The *IAB RF Bandwidth* consists of one sub-block gap and two sub-blocks located at the edges of the declared maximum radiated *IAB RF Bandwidth* for non-contiguous operation (D.17). +- For IAB not supporting simultaneous transmission between IAB-DU and IAB-MT, select the IAB-DU carrier and IAB-MT carrier to be tested according to 4.7.2.1. Place them adjacent to the upper *IAB RF Bandwidth edge* and place the same signals adjacent to the lower *IAB RF Bandwidth edge*. +- For IAB supporting simultaneous transmission between IAB-DU and IAB-MT, select the IAB UL carrier to be tested according to 4.7.2 and place it adjacent to the lower IAB RF Bandwidth edge. Place the same IAB UL carrier adjacent to the upper IAB RF Bandwidth edge. Select the IAB DL carrier to be tested according to 4.7.2.1 and place it adjacent to the already placed IAB UL carrier at the lower IAB RF Bandwidth edge. Place the same IAB DL carrier adjacent to the already placed IAB UL carrier at the upper. +- For single-band operation receiver tests, if the remaining gap is at least 15 MHz (or 60 MHz if channel bandwidth of the carrier to be tested is 20 MHz) for FR1 or 150 MHz for FR2-1 plus two times the *channel bandwidth* used in the previous step and the beam supports at least 4 carriers, place a IAB-DU carrier and IAB-MT carrier of this *channel bandwidth* adjacent to each already placed carrier for each sub-block. The nominal channel spacing defined in TS 38.174 [2] clause 5.4.1 shall apply. +- The sub-block edges adjacent to the sub-block gap shall be determined using the specified $F_{\text{offset\_high}}$ and $F_{\text{offset\_low}}$ for the carriers adjacent to the sub-block gap. + +#### 4.7.2.4.2 IABTC3 power allocation + +Set the number of carriers to the number of carriers at maximum TRP (D.15). + +For EIRP accuracy requirements set each beam to rated beam EIRP (D.11) 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 the rated transmitter TRP $P_{\text{rated, t, TRP}}$ (D.38). + +#### 4.7.2.5 IABTC4: Multi-band test configuration for full carrier allocation + +The purpose of IABTC4 is to test beams which have been generated using transceiver units supporting operation in multiple operating bands through common active RF components, considering maximum supported number of carriers. + +##### 4.7.2.5.1 IABTC4 generation + +IABTC4 is based on re-using the existing test configuration applicable per band on beams generated using Multi-band transceiver units and hence have declared multi-band dependencies (D.16). It is constructed using the following method: + +- The *IAB RF Bandwidth* of each supported operating band shall be the declared maximum radiated *IAB RF Bandwidth* (D.17). +- The number of carriers of each supported operating band shall be the declared maximum number of supported carriers per *operating band* in multi-band operation (D.21). Carriers shall be selected according to 4.7.2.1 and shall first be placed at the outermost edges of the declared maximum radiated *Radio Bandwidth* (D.18). Additional carriers shall next be placed at the edges of *IAB RF Bandwidth*, if possible. +- The allocated *IAB RF Bandwidth* of the outermost bands shall be located at the outermost edges of the declared maximum radiated *Radio Bandwidth* (D.18). +- 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. + +- 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* in the other band. +- If the sum of the maximum *IAB RF bandwidths* of each of the supported operating bands is greater than the declared *total RF bandwidth* $BW_{tot}$ (D.19) of transmitter and receiver for the declared band combinations of the IAB, then repeat the steps above for test configurations where the *IAB 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 carriers per *operating band* in multi-band operation (D.21) is larger than the declared total maximum number of supported carriers in multi-band operation (D.63), 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. + +#### 4.7.2.5.2 IABTC4 power allocation + +Set the number of carriers to the total maximum number of supported carriers in multi-band operation (D.63). + +For EIRP accuracy requirements set each beam to rated beam EIRP (D.11) 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 the rated transmitter TRP $P_{rated, t, TRP}$ (D.38). + +If the allocated number of carriers in an operating band exceeds the declared number of carriers at maximum TRP in an operating band (D.15) the carriers should if possible be allocated to a different operating band. + +#### 4.7.2.6 IABTC5: Multi-band test configuration with high PSD per carrier + +The purpose of IABTC5 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. + +##### 4.7.2.6.1 IABTC5 generation + +IABTC5 is based on re-using the existing test configuration applicable for operating bands using multi-band transceiver units and hence have declared multi-band dependencies (D.16). It is constructed using the following method: + +- The *IAB RF Bandwidth* of each supported operating band shall be the declared maximum radiated *IAB RF Bandwidth* (D.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 (D.18). +- The maximum number of carriers is limited to two per band. Carriers shall be selected according to 4.7.2.1 and shall be placed at the outermost edges of the declared maximum *Radio Bandwidth* of the operating band with multi-band dependencies (D.18). +- Each concerned band shall be considered as an independent band and the carrier placement in each band shall be according to IABTC3, where the declared parameters for multi-band operation shall apply. Narrowest supported *IAB channel bandwidth* with the smallest subcarrier spacing declared per *operating band* (D.7) shall be used in the test configuration. +- 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* in the other band. +- If the sum of the maximum *IAB RF bandwidths* of each of the supported *operating bands* is greater than the declared *total RF bandwidth* $BW_{tot}$ (D.19) of transmitter and receiver for the declared band combinations of the IAB, then repeat the steps above for test configurations where the *IAB RF Bandwidth* of one of the *operating band* shall be reduced so that the declared *total RF bandwidth* $BW_{tot}$ of the *operating band* with multi-band dependencies (D.18) is not exceeded and vice versa. + +#### 4.7.2.6.2 IABTC5 power allocation + +Set the number of carriers to the total maximum number of supported carriers in multi-band operation (D.63). + +For EIRP accuracy requirements set each beam to rated beam EIRP (D.11) 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 the rated transmitter TRP $P_{\text{rated, t, TRP}}$ (D.38). + +If the sum of the TRP for all carriers in an operating band(s) exceeds the sum of the rated carrier TRP output power $P_{\text{rated, c, TRP}}$ (D.37) for the number of carriers at maximum TRP (D.15) 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 rated carrier OTA IAB power, $P_{\text{rated, c, TRP}}$ , the exceeded power shall, if possible, be reallocated into the other carriers. + +### 4.8 Applicability of requirements + +#### 4.8.1 Requirement set applicability + +In table 4.8.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 4.8.1-1: Requirement set applicability for IAB-DU and IAB-MT** + +| Requirement | Requirement set | | | | | | +|--------------------------------------|------------------------|------------------------|------------------------|------------------------|------------------------|------------------------| +| | IAB-DU type 1-H | IAB-DU type 1-O | IAB-DU type 2-O | IAB-MT type 1-H | IAB-MT type 1-O | IAB-MT type 2-O | +| Radiated transmit power | 6.2 | 6.2 | 6.2 | 6.2 | 6.2 | 6.2 | +| OTA IAB-DU output power | | 6.3 | 6.3 | | 6.3 | 6.3 | +| OTA output power dynamics | | 6.4 | 6.4 | | 6.4 | 6.4 | +| OTA transmit ON/OFF power | | 6.5 | 6.5 | | 6.5 | 6.5 | +| OTA transmitted signal quality | | 6.6 | 6.6 | | 6.6 | 6.6 | +| OTA occupied bandwidth | NA | 6.7.2 | 6.7.2 | NA | 6.7.2 | 6.7.2 | +| OTA ACLR | | 6.7.3 | 6.7.3 | | 6.7.3 | 6.7.3 | +| OTA out-of-band emission | | 6.7.4 | 6.7.4 | | 6.7.4 | 6.7.4 | +| OTA transmitter spurious emission | | 6.7.5 | 6.7.5 | | 6.7.5 | 6.7.5 | +| OTA transmitter intermodulation | | 6.8 | NA | | 6.8 | NA | +| OTA sensitivity | 7.2 | 7.2 | NA | 7.2 | 7.2 | NA | +| OTA reference sensitivity level | | 7.3 | 7.3 | | 7.3 | 7.3 | +| OTA dynamic range | | 7.4 | NA | | NA | NA | +| OTA in-band selectivity and blocking | | 7.5 | 7.5 | | 7.5 | 7.5 | +| OTA out-of-band blocking | NA | 7.6 | 7.6 | NA | 7.6 | 7.6 | +| OTA receiver spurious emission | | 7.7 | 7.7 | | 7.7 | 7.7 | +| OTA receiver intermodulation | | 7.8 | 7.8 | | 7.8 | 7.8 | +| OTA in-channel selectivity | | 7.9 | 7.9 | | NA | NA | +| Radiated performance requirements | | 8 | 8 | | 8 | 8 | + +#### 4.8.2 Applicability of test configurations for single-band RIB + +The applicable test configurations are specified in the tables below for each the supported RF configuration, which shall be declared according to clause 4.6. The generation and power allocation for each test configuration is defined in clause 4.7. This clause contains the test configurations for *single-band RIB*. + +For an IAB node declared to be capable of single carrier operation only, a single carrier (SC) shall be used for testing. + +For a *single-band RIB* declared to support multi-carrier and/or CA operation in contiguous spectrum operation, the test configurations in the second column of table 4.8.2-1 shall be used for testing. + +For a *single-band RIB* declared to support multi-carrier and/or CA operation in contiguous and non-contiguous spectrum and where the parameters in the manufacturer's declaration according to clause 4.6 are identical for contiguous + +(C) and non-contiguous (NC) spectrum operation, the test configurations in the third column of table 4.8.2-1 shall be used for testing. + +For a *single-band RIB* declared to support multi-carrier and/or CA in contiguous and non-contiguous spectrum and where the parameters in the manufacture's declaration according to clause 4.6 are not identical for contiguous and non-contiguous spectrum operation, the test configurations in the fourth column of table 4.8.2-1 shall be used for testing. + +For a *single-band RIB* declared to support multi-carrier and/or CA and IAB simultaneous operation (D.x) in contiguous and non-contiguous spectrum and where the parameters in the manufacture's declaration according to clause 4.6 are identical for contiguous and non-contiguous spectrum operation, the test configurations in the third column of table 4.8.2-2 shall be used for testing. + +For a *single-band RIB* declared to support multi-carrier and/or CA and IAB simultaneous operation (D.x) in contiguous and non-contiguous spectrum and where the parameters in the manufacture's declaration according to clause 4.6 are not identical for contiguous and non-contiguous spectrum operation, the test configurations in the fourth column of table 4.8.2-2 shall be used for testing. + +Unless otherwise stated, single carrier configuration (SC) tests shall be performed using signal with narrowest supported *IAB-DU* or *IAB-MT channel bandwidth* with the smallest supported subcarrier spacing declared per *operating band* (D.7). + +**Table 4.8.2-1: Test configurations for a *single-band RIB* of IAB** + +| IAB test case | Contiguous spectrum capable IAB | C and NC capable IAB with identical parameters | C and NC capable IAB with different parameters | +|----------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-------------------------------------------------------|-------------------------------------------------------| +| Radiated transmit power | IABTC1 | IABTC1 | IABTC1, IABTC3 | +| OTA IAB maximum output power | IABTC1 | IABTC1 | IABTC1, IABTC3 | +| OTA RE Power control dynamic range (only applied to IAB-DU) | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| OTA total power dynamic range | SC | SC | SC | +| OTA transmit ON/OFF power (only applied to NR TDD IAB) | IABTC1 | IABTC1 | IABTC1, IABTC3 | +| OTA frequency error | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| OTA error Vector Magnitude | IABTC1 | IABTC1 | IABTC1, IABTC3 | +| OTA time alignment error | IABTC1 | IABTC1 | IABTC1, IABTC3 | +| OTA Occupied bandwidth | SC, IABTC2 (Note 1) | SC, IABTC2 (Note 1) | SC, IABTC2 (Note 1) | +| OTA ACLR | IABTC1 | IABTC1, IABTC3 | IABTC1, IABTC3 | +| OTA CACLR | - | IABTC3 | IABTC3 | +| OTA operating band unwanted emissions | IABTC1, SC (Note 2) | IABTC1, IABTC3, SC (Note 2) | IABTC1, IABTC3, SC (Note 2) | +| OTA transmitter spurious emissions | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| OTA transmitter intermodulation | IABTC1 | IABTC1, IABTC3 | IABTC1, IABTC3 | +| OTA sensitivity | SC | SC | SC | +| OTA reference sensitivity level | SC | SC | SC | +| OTA dynamic range (only applied to IAB-DU) | SC | SC | SC | +| OTA adjacent channel selectivity | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| In-band blocking | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| OTA out-of-band blocking | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| OTA receiver spurious emissions | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| OTA receiver intermodulation | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| OTA in-channel selectivity (only applied to IAB-DU) | SC | SC | SC | +| NOTE 1: IABTC2 is only applicable when contiguous CA is supported. | | | | +| NOTE 2: OBUE SC shall be tested using the widest supported channel bandwidth and the highest supported subcarrier spacing. | | | | + +**Table 4.8.2-2: Test configurations for a *single-band RIB* of IAB capable of simultaneous operation** + +| IAB test case | Contiguous spectrum capable IAB | C and NC capable IAB with identical parameters | C and NC capable IAB with different parameters | +|-------------------------------------------------------------|----------------------------------------|-------------------------------------------------------|-------------------------------------------------------| +| Radiated transmit power | IABTC1 | IABTC1 | IABTC1, IABTC3 | +| OTA IAB maximum output power | IABTC1 | IABTC1 | IABTC1, IABTC3 | +| OTA RE Power control dynamic range (only applied to IAB-DU) | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| OTA transmit ON/OFF power (only applied to NR TDD IAB) | IABTC1 | IABTC1 | IABTC1, IABTC3 | +| OTA frequency error | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | Tested with Error Vector Magnitude | +| OTA error Vector Magnitude | IABTC1 | IABTC1 | IABTC1, IABTC3 | +| OTA time alignment error between IAB-DU and IAB-MT | IABTC1 | IABTC1 | IABTC1, IABTC3 | +| OTA ACLR | IABTC1 | IABTC1, IABTC3 | IABTC1, IABTC3 | +| OTA CACLR | - | IABTC3 | IABTC3 | +| OTA operating band unwanted emissions | IABTC1 | IABTC1, IABTC3 | IABTC1, IABTC3 | +| OTA transmitter spurious emissions | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| OTA transmitter intermodulation (NOTE 1) | IABTC1 | IABTC1, IABTC3 | IABTC1, IABTC3 | +| OTA adjacent channel selectivity | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| In-band blocking | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| OTA out-of-band blocking | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| OTA receiver spurious emissions | IABTC1 | IABTC3 | IABTC1, IABTC3 | +| OTA receiver intermodulation (NOTE 1) | IABTC1 | IABTC3 | IABTC1, IABTC3 | + +NOTE 1: Test case does not apply to IAB type 2-O. + +### 4.8.3 Applicability of test configurations for multi-band RIB + +For a *multi-band RIB*, the test configuration in table 4.8.3-1 shall be used for testing. + +For a *multi-band RIB* and IAB capable of simultaneous operation, the test configuration in table 4.8.3-2 shall be used for testing. + +Unless otherwise stated, single carrier configuration (SC) tests shall be performed using signal with narrowest supported *IAB-DU* or *IAB-MT* channel bandwidth with the smallest supported subcarrier spacing declared per *operating band* (D.7). + +NOTE: The applicability of test configurations in table 4.8.3-1 are not applicable to *IAB type 2-O*. + +**Table 4.8.3-1: Test configuration for a *multi-band RIB* of IAB** + +| IAB test case | Test configuration | +|-----------------------------------------------------------------------------------------------------------------------------|----------------------------------------| +| Radiated transmit power | IABTC1/3 (Note 1), IABTC4 | +| OTA IAB-DU maximum output power | IABTC1/3 (Note 1), IABTC4 | +| OTA RE power control dynamic range (only applied to IAB-DU) | Tested with Error Vector Magnitude | +| OTA total power dynamic range | SC | +| OTA transmit ON/OFF power (only applied to NR TDD IAB) | IABTC4 | +| OTA frequency error | Tested with Error Vector Magnitude | +| OTA Error Vector Magnitude | IABTC1/3 (Note 1), IABTC4 | +| OTA time alignment error | IABTC1/3 (Note 1), IABTC5 (Note 2) | +| OTA occupied bandwidth | SC, IABTC2 (Note 3) | +| OTA ACLR | IABTC1/3 (Note 1), IABTC5 (Note 4) | +| OTA CACLR | IABTC3 (Note 1), IABTC5 (Note 4) | +| OTA operating band unwanted emissions | IABTC1/3 (Note 1), IABTC5, SC (Note 5) | +| OTA transmitter spurious emissions | IABTC1/3 (Note 1), IABTC5 | +| OTA transmitter intermodulation | IABTC1/3 (Note 1) | +| OTA sensitivity | SC | +| OTA reference sensitivity level | SC | +| OTA dynamic range (only applied to IAB-DU) | SC | +| OTA adjacent channel selectivity | IABTC5 | +| In-band blocking | IABTC5 | +| OTA out-of-band blocking | IABTC5 | +| OTA receiver spurious emissions | IABTC1/3 (Note 1), IABTC5 | +| OTA receiver intermodulation | IABTC5 | +| OTA in-channel selectivity (only applied to IAB-DU) | SC | +| NOTE 1: IABTC1 and/or IABTC3 shall be applied in each supported operating band. | | +| NOTE 2: IABTC5 is only applicable when inter-band CA is supported. | | +| NOTE 3: IABTC2 is only applicable when contiguous CA is supported. | | +| NOTE 4: IABTC5 may be applied for Inter RF Bandwidth gap only. | | +| NOTE 5: OBUE SC shall be tested using the widest supported channel bandwidth and the highest supported sub-carrier spacing. | | + +**Table 4.8.3-2: Test configuration for a *multi-band RIB* of IAB capable of simultaneous operation** + +| IAB test case | Test configuration | +|---------------------------------------------------------------------------------|----------------------------------------| +| Radiated transmit power | IABTC1/3 (Note 1), IABTC4 | +| OTA IAB-DU maximum output power | IABTC1/3 (Note 1), IABTC4 | +| OTA transmit ON/OFF power (only applied to NR TDD IAB) | IABTC4 | +| OTA frequency error | Tested with Error Vector Magnitude | +| OTA Error Vector Magnitude | IABTC1/3 (Note 1), IABTC4 | +| OTA time alignment error between IAB-DU and IAB-MT | IABTC1/3 (Note 1), IABTC5 | +| OTA ACLR | IABTC1/3 (Note 1), IABTC5 (Note 4) | +| OTA CACLR | IABTC3 (Note 1), IABTC5 (Note 4) | +| OTA operating band unwanted emissions | IABTC1/3 (Note 1), IABTC5, SC (Note 5) | +| OTA transmitter spurious emissions | IABTC1/3 (Note 1), IABTC5 | +| OTA transmitter intermodulation | IABTC1/3 (Note 1) | +| OTA adjacent channel selectivity | IABTC5 | +| In-band blocking | IABTC5 | +| OTA out-of-band blocking | IABTC5 | +| OTA receiver spurious emissions | IABTC1/3 (Note 1), IABTC5 | +| OTA receiver intermodulation | IABTC5 | +| NOTE 1: IABTC1 and/or IABTC3 shall be applied in each supported operating band. | | +| NOTE 2: Void | | +| NOTE 3: Void | | +| NOTE 4: IABTC5 may be applied for Inter RF Bandwidth gap only. | | + +## 4.9 RF channels and test models + +### 4.9.1 RF channels + +For the single carrier testing many tests in the present document are performed with appropriate frequencies in the bottom, middle and top channels of the supported frequency range of the IAB. These are denoted as RF channels B (bottom), M (middle) and T (top). + +Unless otherwise stated, the test shall be performed with a single carrier at each of the RF channels B, M and T. + +Many tests in the present document are performed with the maximum *IAB 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 *IAB RF Bandwidth* located at the bottom of the supported frequency range in the operating band. +- $M_{\text{RFBW}}$ : maximum *IAB RF Bandwidth* located in the middle of the supported frequency range in the operating band. +- $T_{\text{RFBW}}$ : maximum *IAB RF Bandwidth* located at the top of the supported frequency range in the operating band. + +For a IAB capable of multi-band operation and 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 *IAB 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 *IAB 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 clause 4.6) spans both operating bands. $B_{\text{RFBW\_T'RFBW}}$ means the *IAB 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. + +Occupied bandwidth test in the present document are performed with the *aggregated IAB 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 IAB channel bandwidth* located at the bottom of the supported frequency range in each operating band; +- $M_{\text{BW Channel CA}}$ : *aggregated IAB channel bandwidth* located close in the middle of the supported frequency range in each operating band; +- $T_{\text{BW Channel CA}}$ : *aggregated IAB channel bandwidth* located at the top of the supported frequency range in each 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 the 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.9.2 Test models + +### 4.9.2.1 General + +The following clauses will describe the test models needed for *IAB type 2-O*. Note the IAB FR1 test models described in TS 38.176-1 [3] are also applicable for *IAB type 1-O* conformance testing. + +### 4.9.2.2 FR2-1 test models for IAB-DU + +FR2-1 test model in clause 4.9.2.2 in TS 38.141-2 [6] applies to IAB-DU as below: + +NR-FR2-TM1.1 applies to IAB-DU-FR2-TM1.1 + +NR-FR2-TM2 applies to IAB-DU-FR2-TM2 + +NR-FR2-TM2a applies to IAB-DU-FR2-TM2a + +NR-FR2-TM3.1 applies to IAB-DU-FR2-TM3.1 + +NR-FR2-TM3.1a applies to IAB-DU-FR2-TM3.1a + +### 4.9.2.3 FR2-1 test models for IAB-MT + +The set-up of physical channels for transmitter tests shall be according to one of the test models (IAB-MT-FR2-TM) below. A reference to the applicable test model is made within each test. + +The following general parameters are used by all NR test models: + +- Duration is 2 radio frames for TDD (20 ms) +- The slots are numbered 0 to $10 \times 2^\mu - 1$ where $\mu$ is the numerology corresponding to the subcarrier spacing +- $N_{RB}$ is the maximum transmission bandwidth configuration seen in table 5.3.2-2 in TS 38.174 [2]. +- Normal CP +- Virtual resource blocks of localized type + +For FR2-1 TDD, IAB-MT test models are derived based on the uplink/downlink configuration as shown in the table 4.9.2.3-1 using information element *TDD-UL-DL-ConfigCommon* as defined in TS 38.331 [z]. + +**Table 4.9.2.3-1: Configurations of TDD for *IAB-MT type 2-O* test models** + +| Field name | Value | | +|----------------------------------------------------|-------|------| +| referenceSubcarrierSpacing (kHz) | 60 | 120 | +| Periodicity (ms) for dl-UL-TransmissionPeriodicity | 1.25 | 1.25 | +| nrofDownlinkSlots | 3 | 7 | +| nrofDownlinkSymbols | 10 | 6 | +| nrofUplinkSlots | 1 | 2 | +| nrofUplinkSymbols | 2 | 4 | + +Common physical channel parameters for all FR2-1 test models are specified in table 4.9.2.3-2 and table 4.9.2.3-3 for PUSCH. Specific physical channel parameters for FR2-1 test models are described in clauses 4.9.2.3.1 to 4.9.2.3.3. + +**Table 4.9.2.3-2: Common physical channel parameters for IAB-MT type 2-O PUSCH** + +| Parameter | Value | +|---------------------------------------------------------------|------------------------------------| +| mapping type | PUSCH mapping type A | +| dmrs-TypeA-Position for the first DM-RS symbol | 'pos2' | +| dmrs-AdditionalPosition for additional DM-RS symbol(s) | 'pos0' | +| dmrs-Type for comb pattern | Configuration type 1 | +| maxLength | 1 | +| Ratio of PUSCH EPRE to DM-RS EPRE | 0 dB | +| PTRS configuration and density | $L_{PT-RS} = 4$
$K_{PT-RS} = 2$ | +| Ratio of PT-RS EPRE to DM-RS EPRE | 0 dB | + +**Table 4.9.2.3-3: Common physical channel parameters for PUSCH by RNTI for IAB-MT type 2-O test models** + +| Parameter | Value | +|-----------|-------| +| PUSCH | | + +**4.9.2.3.1 FR2-1 test model 1.1 (IAB-MT-FR2-TM1.1)** + +This model shall be used for tests on: + +- Radiated transmit power +- IAB output power +- Transmit ON/OFF power +- Unwanted emissions + - Occupied bandwidth + - ACLR + - Operating band unwanted emissions + - Transmitter spurious emissions +- Receiver spurious emissions + +Common physical channel parameters are defined in clause 4.9.2.3. Specific physical channel parameters for IAB-MT-FR2-TM1.1 are defined in table 4.9.2.3.1-1. + +**Table 4.9.2.3.1-1: Specific physical channel parameters of IAB-MT-FR2-TM1.1** + +| Parameter | Value | +|------------------|----------| +| # of PRBs PUSCH | $N_{RB}$ | +| Modulation PUSCH | QPSK | + +**4.9.2.3.2 FR2-1 test model 2 (IAB-MT-FR2-TM2)** + +This model shall be used for tests on: + +- Total power dynamic range (at lower PSD TX power limit at min power) +- EVM of single PRB allocation (at lower PSD TX power limit at min power) +- Frequency error (at lower PSD TX power limit at min power) + +Common physical channel parameters are defined in clause 4.9.2.3. Specific physical channel parameters for IAB-MT-FR2-TM2 are defined in table 4.9.2.3.2-1 for 64QAM. For 16QAM and QPSK, specific physical channel parameters for IAB-MT-FR2-TM2 are defined in table 4.9.2.3.2-1 with 64QAM PUSCH PRB replaced with selected modulation order PUSCH PRB according to the corresponding test procedure. + +**Table 4.9.2.3.2-1: Specific physical channel parameters of IAB-MT-FR2-TM2** + +| Parameter | Value | | | +|-----------------------------------------|--------|----|---| +| # of 64QAM PUSCH PRBs | 1 | | | +| Level of boosting (dB) | 0 | | | +| Location of 64QAM PRB | Slot | RB | n | +| | $3n$ | 0 | | +| | $3n+1$ | | | +| | $3n+2$ | | | +| # of PUSCH PRBs which are not allocated | | | | + +#### 4.9.2.3.2a FR2-1 test model 2a (IAB-MT-FR2-TM2a) + +This model shall be used for tests on: + +- Total power dynamic range (at lower PSD TX power limit at min power) +- EVM of single PRB allocation (at lower PSD TX power limit at min power) +- Frequency error (at lower PSD TX power limit at min power) + +Common physical channel parameters are defined in clause 4.9.2.3. Specific physical channel parameters for IAB-MT-FR2-TM2a are defined in table 4.9.2.3.2-1 with all 64QAM PUSCH PRBs replaced by 256QAM PUSCH PRBs. + +#### 4.9.2.3.3 FR2-1 test model 3.1 (IAB-MT-FR2-TM3.1) + +This model shall be used for tests on: + +- Output power dynamics + - Total power dynamic range (upper TX PSD power limit at max power with all 64QAM PRBs allocated) +- Transmitted signal quality + - Frequency error (at max power) + - EVM for modulation (at max power) + +Common physical channel parameters are defined in clause 4.9.2.3. Specific physical channel parameters for IAB-MT-FR2-TM3.1 are defined in table 4.9.2.3.1-1 with all QPSK PUSCH PRBs replaced with selected modulation order PUSCH PRBs according to the corresponding test procedure. + +#### 4.9.2.3.4 FR2-1 test model 3.1a (IAB-MT-FR2-TM3.1a) + +This model shall be used for tests on: + +- Output power dynamics + - Total power dynamic range (upper TX PSD power limit at max power with all 256QAM PRBs allocated) +- Transmitted signal quality + - Frequency error (at max power) + - EVM for 256QAM modulation (at max power) + +Common physical channel parameters are defined in clause 4.9.2.3. Specific physical channel parameters for IAB-MT-FR2-TM3.1a shall be defined in table 4.9.2.3.1-1 with all QPSK PUSCH PRBs replaced by 256QAM. + +#### 4.9.2.3 Data content of physical channels and signals for IAB-MT-FR2-TM + +Randomisation of the data content is obtained by utilizing a PN sequence generator and the length-31 Gold sequence scrambling of TS 38.211 [7], clause 5.2.1 which is invoked by all physical channels prior to modulation and mapping to the RE grid. + +Initialization of the scrambler and RE-mappers as defined in TS 38.211 [7] use the following additional parameters: + +- +- $q = 0$ (single code word) +- Rank 1, single layer + +##### 4.9.2.3.1 PUSCH + +- Generate the required amount of bits from the output of the PN23 sequence generator [28]. The PN sequence generator is initialized with a starting seed of "all ones" in the first allocated slot of each frame. The PN sequence is continuous over the slot boundaries. +- Perform user specific scrambling according to TS 38.211 [7], clause 6.3.1.1. +- +- Perform modulation of the scrambled bits with the modulation scheme defined for each user according to TS 38.211 [7], clause 6.3.1.3. +- Perform mapping of the complex-valued symbols to layer according to TS 38.211 [7], clause 6.3.1.3. +- Perform PDSCH mapping type A according to TS 38.211 [7]. +- DM-RS sequence generation according to TS 38.211 [7], clause 6.4.1.1.1 where $l$ is the OFDM symbol number within the slot with symbols indicated by table 4.9.2.2-3. +- +- +- DM-RS mapping according to TS 38.211 [7], clause 6.4.1.1.3 with parameters listed in table 4.9.2.2-3. +- For NR-IAB-MT-FR2-TM PT-RS sequence generation according to TS 38.211 [7], clause 6.4.1.2.1, with parameters listed in table 4.9.2.2-3. +- For NR-IAB-MT-FR2-TM PT-RS mapping according to TS 38.211 [7], clause 6.4.1.2.2, with parameters listed in table 4.9.2.2-3. + +## 4.10 Requirements for contiguous and non-contiguous spectrum + +A spectrum allocation where an IAB operates can either be contiguous or non-contiguous. Unless otherwise stated, the requirements in the present specification apply for IAB configured for both *contiguous spectrum* operation and *non-contiguous spectrum* operation. + +For IAB operation in *non-contiguous spectrum*, some requirements apply both at the *IAB-DU RF Bandwidth edges* or *IAB-MT RF bandwidth edges* and inside the *sub-block gaps*. For each such requirement, it is stated how the limits apply relative to the *IAB-DU RF Bandwidth edges* or *IAB-MT RF bandwidth edges* and the *sub-block edges* respectively. + +## 4.11 Requirements for IAB capable of multi-band operation + +For *multi-band RIB*, the RF requirements in clause 6 and 7 apply separately to each supported *operating band* unless otherwise stated. For some requirements, it is explicitly stated that specific additions or exclusions to the requirement apply at *multi-band RIB(s)* as detailed in the requirement clause. + +*IAB type I-O* 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 *multi-band RIBs*. +- A combination of *single-band RIBs* and *multi-band RIBs* provides support of the *IAB type 1-O* capability of operation in multiple *operating bands*. + +For *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. + +## 4.12 Co-location requirements + +### 4.12.1 General + +Co-location requirements are requirements which are based on assuming the *IAB type 1-O* is co-located with another BS or IAB 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.12.1-1 rely on a *co-location reference antenna* used to mimic an IAB to base station or IAB co-location scenario. + +**Table 4.12.1-1: Co-location requirements** + +| Clause number | Requirement | Co-location reference antenna operation | Type | +|--------------------|--------------------------------------------------------------------------------------|-----------------------------------------|-------------------------------| +| 6.5 | OTA transmit ON/OFF power for FR1 | Measure emission | Mandatory | +| 6.7.5.3
6.7.5.5 | OTA spurious emission: Protection of the IAB receiver of own or different BS and IAB | Measure emission | Optional based on declaration | +| | OTA spurious emission: Co-location with other base stations and IAB-Nodes | | | +| 6.8 | OTA transmitter intermodulation | Inject the interferer signal | Mandatory | +| 7.6 | OTA out-of-band blocking: Co-location with other base stations or IAB-Nodes | 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 38.174 [2]. + +### 4.12.2 Co-location test antenna + +#### 4.12.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.12.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 with the requirements specified in table 4.12.2.2-1. + +Translation of the requirements to other test antennas are not precluded but suitable translations between the co-location reference antenna and test antenna must be provided to demonstrate that the method is within the specified MU. + +NOTE: The currently defined CLTAs are suitable for testing *IAB type 1-O* implemented with a planar antenna array. The method for testing IAB with other antenna array implementations is not covered by the present release of the present document. + +**Table 4.12.2.2-1: CLTA characteristics** + +| Parameter | In-band CLTA | Out-of-band CLTAs | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| Vertical radiating dimension (h) | Test object vertical radiating length $\pm 30\%$ | N/A | +| 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 (D.3) vertical beamwidth $\pm 3^\circ$ | +| Polarization | Match | Match to in-band | +| Conducted interface return loss | $> 10$ dB | $> 10$ dB | +| NOTE: If a multi-column or multi-band antenna is used the column closest to the NR IAB shall be selected while other columns are terminated during testing. | | | + +#### 4.12.2.3 Co-location test antenna alignment + +The alignment between the NR IAB under test and the *co-location test antenna* is described in table 4.12.2.3-1 and figure 4.12.2.3-1. The same physical alignment applies to in-band and out-of-band co-location requirements. + +**Table 4.12.2.3-1: CLTA alignment tolerances** + +| Parameter | | +|------------------------------------------------------------|------------------------------------| +| Edge-to-edge separation between the NR IAB and the CLTA, d | $0.1 \text{ m} \pm 0.01 \text{ m}$ | +| Vertical alignment | Centre $\pm 0.01 \text{ m}$ | +| Front alignment | Radome front $\pm 0.01 \text{ m}$ | + +![Figure 4.12.2.3-1: Alignment of NR IAB and CLTA. The diagram shows three views: Horizontal View, Vertical View, and Side View. In the Horizontal View, an NR IAB type 1 -O (represented by a square with an 'X') and a CLTA (represented by a narrow rectangle with an 'X') are shown. A horizontal dashed line connects their centers, and a horizontal double-headed arrow labeled 'd' indicates the distance between them. In the Vertical View, the NR IAB is shown as a rectangle and the CLTA as a smaller rectangle. Vertical dashed lines extend downwards from each to labels 'Mechanical bore-sight direction'. In the Side View, the NR IAB is shown as a rectangle with a dashed line representing the 'Back side' and a solid line representing the 'Front side'. The CLTA is shown as a narrow rectangle with a dashed line representing the 'Back side' and a solid line representing the 'Front side'.](5801c19431e76330430e92a598cc7a16_img.jpg) + +Figure 4.12.2.3-1: Alignment of NR IAB and CLTA. The diagram shows three views: Horizontal View, Vertical View, and Side View. In the Horizontal View, an NR IAB type 1 -O (represented by a square with an 'X') and a CLTA (represented by a narrow rectangle with an 'X') are shown. A horizontal dashed line connects their centers, and a horizontal double-headed arrow labeled 'd' indicates the distance between them. In the Vertical View, the NR IAB is shown as a rectangle and the CLTA as a smaller rectangle. Vertical dashed lines extend downwards from each to labels 'Mechanical bore-sight direction'. In the Side View, the NR IAB is shown as a rectangle with a dashed line representing the 'Back side' and a solid line representing the 'Front side'. The CLTA is shown as a narrow rectangle with a dashed line representing the 'Back side' and a solid line representing the 'Front side'. + +**Figure 4.12.2.3-1: Alignment of NR IAB and CLTA** + +## 4.13 Test efficiency optimization + +When manufacture declares the same RF implementation for IAB-MT and IAB-DU (D.IAB-1) and the declarations in table 4.13-1 are the same for IAB-DU and IAB-MT, it is sufficient to test only IAB-MT or IAB-DU with the test requirement applicability according to table 4.13-2 for Tx requirements and table 4.13-3 for Rx requirements. + +For *IAB type 1-H* the test efficiency optimization for radiated requirements apply only for radiated transmit power and OTA sensitivity. Test efficiency optimization for conducted requirements is defined in TS 38.176-1 [3]. + +For *IAB type 1-O* and *IAB type 2-O* it is required that the DUT selection between requirements follows following rules: + +- out of radiated transmit power, OTA modulation quality and OTA frequency error, IAB-DU and IAB-MT are required to be the DUT at least once, +- out of OTA ACLR, OTA operating band unwanted emissions and OTA transmitter general spurious emissions, are required to be the DUT at least once, +- out of OTA reference sensitivity, OTA ACS, OTA receiver intermodulation, IAB-DU and IAB-MT are required to be the DUT at least once. + +In some cases, the test requirements are the same but the MU for the IAB-MT is larger than for the IAB-DU. When the test efficiency optimization is applicable for such cases, the lower MU value should be used. + +**Table 4.13-1: Declarations required to be the same for IAB-DU and IAB-MT for test efficiency optimization to apply** + +| Declaration identifier | Declaration | Additional conditions | Applicability (Note 1) | | | +|------------------------|----------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|------------------------|--------------|--------------| +| | | | IAB type 1-H | IAB type 1-O | IAB type 2-O | +| D.4 | Operating bands and frequency ranges | | c | x | x | +| D.6 | IAB class | Medium range IAB-DU can apply test efficiency optimization with wide area IAB-MT other declarations in this table are the same. | c | x | x | +| D.11 | Rated beam EIRP | | x | x | x | +| D.17 | Maximum radiated IAB RF Bandwidth | | c | x | x | +| D.19 | Total RF bandwidth (BW tot ) | | c | x | x | +| D.21 | Maximum number of supported carriers per operating band in multi-band operations | | c | x | n/a | +| D.27 | Minimum EIS for FR1 (EIS minSENS ) | | x | x | n/a | +| D.28 | EIS REFSENS for FR2-1 (EIS REFSENS_50M ) | | n/a | n/a | x | +| D.33 | Conformance test directions | Required only for IAB type 1-H | x | x | n/a | +| D.34 | OTA coverage range | | x | x | x | +| D.37 | The rated carrier OTA IAB power, P rated,c,TRP | | n/a | x | x | +| D.44 | Single-band RIB or multi-band RIB | | c | x | n/a | +| D.46 | Maximum number of supported carriers per operating band | | c | x | x | +| D.48 | Other band combination multi-band restrictions | | c | x | n/a | +| D.53 | OTA REFSENS RoAoA | | n/a | x | x | +| D.63 | Total maximum number of supported carriers in multi-band operation | | c | x | n/a | + +NOTE 1: Manufacturer declarations applicable per IAB requirement set were marked as "x". Manufacturer declarations not applicable per IAB requirement set were marked as "n/a". For declarations marked as 'c', related conducted declarations in TS 38.176-1 [3] apply. + +**Table 4.13-2: Test requirement applicability for TX requirements** + +| Tx requirement | | Test efficiency optimization applicable | Test requirement applicability (Note 1) | +|---------------------------------------------|---------------------|-----------------------------------------|-----------------------------------------| +| Radiated transmit power | | Yes | FR2-1: IAB-DU | +| OTA output power | | Yes | FR2-1: IAB-DU | +| OTA Output power dynamics (only for IAB-DU) | | No | (Note 3) | +| OTA Output power dynamics (only for IAB-MT) | | No | (Note 3) | +| OTA Transmitter OFF power | | Yes | | +| OTA Transient period | | Yes | | +| IAB-DU OTA Frequency Error | | No | | +| IAB-MT OTA Frequency Error | | No | | +| OTA Modulation quality | | Yes | | +| OTA Time alignment error (only for IAB-DU) | | No | (Note 3) | +| OTA Occupied bandwidth | | Yes | | +| OTA ACLR | | Yes | FR2-1: IAB-DU (Note 2) | +| OTA Operating band unwanted emission | | Yes | FR2-1: IAB-DU | +| OTA Transmitter spurious | General requirement | FR2-1: IAB-DU | FR2: IAB-DU | + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|---------------|---------------| +| emission | Additional spurious emissions | FR2-1: IAB-DU | FR2: IAB-DU | +| | Co-location with other base stations | | | +| OTA transmitter intermodulation | | Yes | FR2-1: IAB-DU | +| NOTE 1: Test requirement applicability defines how to select whether IAB-DU or IAB-MT test requirement is applied. In case no applicability definition is provided or the applicability definition test requirement is the same for IAB-DU and IAB-MT, either can apply. | | | | +| NOTE 2: Local Area IAB-MT type 2-O is required to use IAB-DU test requirement. | | | | +| NOTE 3: Test efficiency optimization is not applicable and therefore original test requirement applies. | | | | + +**Table 4.13-3: Test requirement applicability for Rx requirements** + +| Rx requirement | Test efficiency optimization applicable | Test requirement applicability (Note 1) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|-----------------------------------------| +| OTA sensitivity | Yes | FR2-1: IAB-DU | +| OTA reference sensitivity | Yes | FR2-1: IAB-DU | +| OTA Dynamic range (only for IAB-DU) | No | (Note 2) | +| OTA Adjacent channel selectivity | Yes | IAB-MT | +| OTA In-band blocking | Yes | IAB-MT | +| OTA Out-of-band blocking | General requirement | | +| | Co-location requirement | | +| OTA Receiver spurious emissions | Yes | FR2-1: IAB-DU | +| OTA Receiver intermodulation | Yes | IAB-MT | +| OTA In-channel selectivity (only for IAB-DU) | No | (Note 2) | +| NOTE 1: Test requirement applicability defines how to select whether IAB-DU or IAB-MT test requirement is applied. In case no applicability definition is provided or the applicability definition test requirement is the same for IAB-DU and IAB-MT, either can apply. | | | +| NOTE 2: Test efficiency optimization is not applicable and therefore original test requirement applies. | | | + +## 4.14 Format and interpretation of tests + +Each test 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 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. + +###### **X.4.2y.2 Procedure** + +This clause describes the steps necessary to perform the test and provides further details of the test definition like 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. + +## 4.15 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.15-1. + +![Figure 4.15-1: Reference coordinate system. A 3D Cartesian coordinate system with axes x, y, and z. The z-axis is vertical, pointing upwards. The y-axis is horizontal, pointing to the right. The x-axis is diagonal, pointing towards the bottom-left. A vector originates from the origin and points into the space. 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 vector itself is labeled theta (θ).](db593abff40ea8eb76129baab7f23b16_img.jpg) + +Figure 4.15-1: Reference coordinate system. A 3D Cartesian coordinate system with axes x, y, and z. The z-axis is vertical, pointing upwards. The y-axis is horizontal, pointing to the right. The x-axis is diagonal, pointing towards the bottom-left. A vector originates from the origin and points into the space. 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 vector itself is labeled theta (θ). + +Figure 4.15-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.16 Requirements for IAB-DU and IAB-MT capable of simultaneous operation + +IAB-DU and IAB-MT can be configured as *IAB Simultaneous Operation* based on declaration. Unless otherwise stated, for IAB-DU and IAB-MT simultaneous transmission, the requirements of IAB-DU apply and for IAB-DU and IAB-MT simultaneous reception, the requirements of IAB-MT apply. + +For IAB-node in *IAB Simultaneous Operation*, as detailed in the requirement clause, transmitter requirements apply whatever the type of transmitter considered and for all transmission modes foreseen by the manufacturer's specification as detailed in the requirement clause. + +NOTE: For IAB node operating as simultaneous transmission of IAB-DU and IAB-MT, the manufacturer can provide declaration on power imbalance between IAB-DU and IAB-MT (D.IAB-4) for verification on Modulation quality and ACLR according to the conformance specification requirements. + +For IAB-node in *IAB Simultaneous Operation*, as detailed in the requirement clause, receiver requirements shall be met for any transmitter setting unless otherwise stated. + +--- + +## 5 Operating bands and channel arrangement + +For the IAB operation in NR operating bands specification, their channel bandwidth configurations, channel spacing and raster, as well as synchronization raster specification, refer to TS 38.174 [2], clause 5 and its relevant clauses. + +For radiated testing purposes in the present document, FR1 and FR2-1 operating bands are considered. + +--- + +## 6 Radiated 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. IAB configurations for the tests are defined in clause 4.5. + +If beams have been declared equivalent and parallel (D.13, D.14), only a representative beam is necessary to be tested to demonstrate conformance. + +### 6.2 Radiated transmit power + +#### 6.2.1 Definition and applicability + +*IAB-DU* and *IAB-MT type 1-H*, *IAB-DU* and *IAB-MT type 1-O* and *IAB-DU* and *IAB-MT type 2-O* are declared to support one or more beams, as per manufacturer's declarations. Radiated transmit power is defined as the EIRP level for a declared beam at a specific *beam peak direction*. Declarations are done for IAB-DU and IAB-MT separately. + +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 IAB-DU or IAB-MT 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. + +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. + +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 + +Radiated transmit power minimum requirement for *IAB-DU type 1-H*, *IAB-DU type 1-O*, *IAB-MT type 1-H* and *IAB-MT type 1-O* is defined in TS 38.174 [2], clause 9.2.2. + +Radiated transmit power minimum requirement for *IAB-DU type 2-O* and *IAB-MT type 2-O* is defined in TS 38.174 [2], clause 9.2.3. + +## 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 *IAB-DU type 1-H*, *IAB-DU type 1-O*, *IAB-MT type 1-H*, *IAB-MT type 1-O*, *IAB-DU type 2-O* and *IAB-MT type 2-O*. + +## 6.2.4 Method of test + +### 6.2.4.1 Initial conditions + +Test environments: + +- Normal, see annex B.2. + +RF channels to be tested for single carrier: B, M and T; see clause 4.9.1. + +*IAB 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.9.1, +- $B_{\text{RFBW\_T}}$ and $B'_{\text{RFBW\_T}}$ in multi-band operation, see clause 4.9.1. + +Directions to be tested: + +- OTA peak directions set reference beam direction pair (D.8), and +- OTA peak directions set maximum steering directions (D.10). + +Beams to be tested: Declared beam with the highest intended EIRP for the narrowest intended beam corresponding to the smallest $\text{BeW}\theta$ , or for the narrowest intended beam corresponding to the smallest $\text{BeW}\phi$ (D.3, D.11). + +NOTE: Tests under extreme power supply conditions also test extreme temperatures. + +### 6.2.4.2 Procedure + +For normal test environment conditions in OTA domain, the test procedure is as follows: + +- 1) Place the IAB at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the IAB with the test system. +- 3) Orient the positioner (and IAB) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the *beam peak direction* of the IAB according to the declared *beam direction pair*. +- 5) Set the IAB to transmit according to the applicable test configuration in clause 4.8 using the corresponding test model(s) in clause 4.9.2. + +For a IAB declared to be capable of multi-carrier and/or CA operation use the applicable test signal configuration and corresponding power setting specified in clauses 4.7.2 and 4.8 using the corresponding test model(s) in clause 4.9.2 on all carriers configured. + +For an IAB node declared to be capable of simultaneous transmission between IAB-DU and IAB-MT (D.IAB-3), use the applicable test signal configuration and corresponding power setting specified in clauses 4.7.2 and 4.8 using the corresponding test model(s) in clause 4.9.2 for IAB-MT and IAB-DU. + +- 6) 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}$ . +- 7) Test steps 3 to 6 are repeated for all declared beams (D.3) and their reference *beam direction pairs* and *maximum steering directions* (D.8 and D.10). + +For multi-band capable IAB and single band tests, repeat the steps above per involved *operating band* where single band test configurations and test models shall apply with no carriers activated in the other band. + +For extreme conditions tests the methods in annex B.7 may be used. + +## 6.2.5 Test requirement + +### 6.2.5.1 IAB-DU + +For each declared conformance *beam direction pair*, the EIRP measurement results in clause 6.2.4.2 shall remain within the values provided in table 6.2.5.1-1, relative to the manufacturer's declared rated beam EIRP (D.11) value: + +**Table 6.2.5.1-1: Test requirement for radiated transmit power for IAB-DU** + +| | Normal test environment | +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| IAB-DU type 1-H | $f \leq 3 \text{ GHz}: \pm 3.3 \text{ dB}$ | +| | $3 \text{ GHz} < f \leq 6 \text{ GHz}: \pm 3.5 \text{ dB}$ | +| IAB-DU type 1-O | $f \leq 3 \text{ GHz}: \pm 3.3 \text{ dB}$ | +| | $3 \text{ GHz} < f \leq 6 \text{ GHz}: \pm 3.5 \text{ dB}$ | +| IAB-DU type 2-O | $24.15 \text{ GHz} < f \leq 29.5 \text{ GHz}: \pm 5.1 \text{ dB}$
$37 \text{ GHz} < f \leq 43.5 \text{ GHz}: \pm 5.4 \text{ dB}$ | + +### 6.2.5.2 IAB-MT + +For each declared conformance *beam direction pair*, the EIRP measurement results in clause 6.2.4.2 shall remain within the values provided in table 6.2.5.2-1, relative to the manufacturer's declared rated beam EIRP (D.11) value: + +**Table 6.2.5.2-1: Test requirement for radiated transmit power for IAB-MT** + +| | Normal test environment | +|------------------------|-----------------------------------------------------------------------------------------| +| IAB-MT type 1-H | $f \leq 3$ GHz: $\pm 3.3$ dB | +| | $3$ GHz $< f \leq 6$ GHz: $\pm 3.5$ dB | +| IAB-MT type 1-O | $f \leq 3$ GHz: $\pm 3.3$ dB | +| | $3$ GHz $< f \leq 6$ GHz: $\pm 3.5$ dB | +| IAB-MT type 2-O | $24.15$ GHz $< f \leq 29.5$ GHz: $\pm 6$ dB
$37$ GHz $< f \leq 43.5$ GHz: $\pm 6$ dB | + +## 6.3 IAB output power + +### 6.3.1 Definition and applicability + +OTA IAB output power is declared as the TRP radiated requirement, with the output power accuracy requirement defined at the RIB during the *transmitter ON period*. TRP does not change with beamforming settings as long as the *beam peak direction* is within the *OTA peak directions set*. Thus the TRP accuracy requirement must be met for any beamforming setting for which the *beam peak direction* is within the *OTA peak directions set*. Declarations are made separately for IAB-DU and IAB-MT. + +The IAB rated carrier TRP output power for IAB type 1-O shall be within limits as specified in table 6.3.1-1 for IAB-DU type 1-O and in table 6.3.1-2 for IAB-MT type 1-O. + +**Table 6.3.1-1: IAB-DU rated carrier TRP output power limits for IAB-DU type 1-O** + +| IAB-DU class | $P_{\text{rated,c,TRP}}$ | +|----------------------------------------------------------------------------------------|--------------------------| +| Wide Area IAB-DU | (Note) | +| Medium Range IAB-DU | $\leq +47$ dBm | +| Local Area IAB-DU | $\leq +33$ dBm | +| NOTE: There is no upper limit for the $P_{\text{rated,c,TRP}}$ of the Wide Area IAB-DU | | + +**Table 6.3.1-2: IAB-MT rated carrier TRP output power limits for IAB-MT type 1-O** + +| IAB-MT class | $P_{\text{rated,c,TRP}}$ | +|-----------------------------------------------------------------------------------------|---------------------------------------------------| +| Wide Area IAB-MT | (Note) | +| Local Area IAB-MT | $\leq 24$ dBm + $10\log(N_{\text{TXU, counted}})$ | +| NOTE: There is no upper limit for the $P_{\text{rated,c,TRP}}$ of the Wide Area IAB-MT. | | + +There is no upper limit for the *rated carrier TRP output power* of IAB type 2-O. + +Despite the general requirements for the IAB output power described in clauses 6.3.2 – 6.3.3, additional regional requirements might be applicable. + +NOTE: In certain regions, power limits corresponding to IAB classes may apply for IAB type 2-O. + +### 6.3.2 Minimum requirement + +The minimum requirement for IAB-DU type 1-O and IAB-MT type 1-O is in TS 38.174 [2], clause 6.3.2. + +The minimum requirement for IAB type 2-O is in TS 38.174 [2], clause 6.3.3. + +### 6.3.3 Test purpose + +The test purpose is to verify the accuracy of the *maximum carrier TRP* ( $P_{\text{max,c,TRP}}$ ) across the frequency range for all RIBs. + +## 6.3.4 Method of test + +### 6.3.4.1 Initial conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: B, M, T; see clause 4.9.1. + +*IAB 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.9.1. +- $B_{\text{RFBW\_T'RFBW}}$ and $B'_{\text{RFBW\_T'RFBW}}$ in multi-band operation, see clause 4.9.1. + +Beams to be tested: + +As the requirement is TRP the beam pattern(s) may be set up to optimise the TRP measurement procedure (see annex I) as long as the required TRP level is achieved. + +### 6.3.4.2 Procedure + +The following procedure for measuring TRP is based on the directional power measurements as described in annex I. An alternative method to measure TRP is to use a characterized and calibrated reverberation chamber if so follow steps 1, 3, 5, and 7. + +- 1) Place the IAB at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the IAB with the test system. +- 3) Configure the IAB 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 IAB to transmit according to the applicable test configuration in clause 4.8 using the corresponding test model(s) in clause 4.9.2. + +For a IAB declared to be capable of multi-carrier and/or CA operation use the applicable test signal configuration and corresponding power setting specified in clauses 4.7.2 and 4.8 using the corresponding test model(s) in clause 4.9.2 on all carriers configured. + +For an IAB node declared to be capable of Simultaneous transmission between IAB-DU and IAB-MT (D.IAB-3), use the applicable test signal configuration and corresponding power setting specified in clauses 4.7.2 and 4.8 using the corresponding test model(s) in clause 4.9.2 for IAB-MT and IAB-DU. + +- 5) Orient the positioner (and IAB) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see annex I). +- 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 $\text{EIRP} = \text{EIRPp1} + \text{EIRPp2}$ . + +If the test chamber is a reverberation chamber measure TRP directly. + +- 7) Repeat step 6-7 for all directions in the appropriated TRP measurement grid needed for full TRP estimation (see annex I). +- 8) Calculate TRP using the EIRP measurements. + +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 carriers activated in the other band. + +## 6.3.5 Test requirement + +### 6.3.5.1 IAB type 1-O + +The final TRP measurement result in clause 6.3.4.2 shall remain: + +- within +3.4 dB and -3.4 dB of the manufacturer's declared *rated carrier TRP* $P_{\text{rated,c,TRP}}$ carrier frequency $f \leq 3.0$ GHz; +- within +3.5 dB and -3.5 dB of the manufacturer's declared *rated carrier TRP* $P_{\text{rated,c,TRP}}$ for carrier frequency $3.0$ GHz $< f \leq 4.2$ GHz. +- within +3.5 dB and -3.5 dB of the manufacturer's declared *rated carrier TRP* $P_{\text{rated,c,TRP}}$ for carrier frequency $4.2$ GHz $< f \leq 6.0$ GHz. + +### 6.3.5.2 IAB type 2-O + +The final TRP measurement result in clause 6.3.4.2 shall remain: + +- within +5.1 dB and -5.1 dB of the manufacturer's declared *rated carrier TRP* $P_{\text{rated,c,TRP}}$ carrier frequency $24.25$ GHz $< f \leq 29.5$ GHz. +- within +5.4 dB and -5.4 dB of the manufacturer's declared *rated carrier TRP* $P_{\text{rated,c,TRP}}$ for carrier frequency $37$ GHz $< f \leq 43.5$ GHz. + +## 6.4 OTA output power dynamics + +### 6.4.1 IAB-DU OTA Output Power Dynamics + +#### 6.4.1.1 General + +The requirements in clause 6.4 apply during the *transmitter ON period*. Transmit signal quality (as specified in clause 6.6) shall be maintained for the output power dynamics requirements. + +The OTA output power requirements are single direction requirements and apply to the beam peak directions over the OTA peak directions set. + +#### 6.4.1.2 OTA RE power control dynamic range + +##### 6.4.1.2.1 Definition and applicability + +The OTA RE power control dynamic range is the difference between the power of an RE and the average RE power for a IAB-DU at maximum output power ( $P_{\text{max,c,EIRP}}$ ) for a specified reference condition. + +This requirement shall apply at each RIB supporting transmission in the *operating band*. + +##### 6.4.1.2.2 Minimum requirement + +The minimum requirement for *IAB-DU type 1-O* is in TS 38.174 [2], clause 9.4.1.2. + +##### 6.4.1.2.3 Test purpose + +No specific test or test requirements are defined for RE power control dynamic range. The Error Vector Magnitude (EVM) test, as described in clause 6.5.4 provides sufficient test coverage for this requirement. + +### 6.4.1.3 OTA total power dynamic range + +#### 6.4.1.3.1 Definition and applicability + +The OTA total power dynamic range is the difference between the maximum and the minimum transmit power of an OFDM symbol for a specified reference condition. + +This requirement shall apply at each RIB supporting transmission in the *operating band*. + +NOTE: The upper limit of the OTA total power dynamic range is the IAB-DU maximum carrier EIRP ( $P_{\max,c,EIRP}$ ) when transmitting on all RBs. The lower limit of the OTA total power dynamic range is the average EIRP for single RB transmission in the same direction using the same beam. The OFDM symbols shall carry PDSCH and not contain PDCCH, RS or SSB. + +#### 6.4.1.3.2 Minimum requirement + +The minimum requirement for *IAB type 1-O* is in TS 38.174 [2], clause 9.4.1.3.2. + +The minimum requirement for *IAB type 2-O* is in TS 38.174 [2], clause 9.4.1.3.3. + +#### 6.4.1.3.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.1.3.4 Method of test + +##### 6.4.1.3.4.1 Initial conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +Beams to be tested: Declared beam with the highest intended EIRP for the narrowest intended beam corresponding to the smallest $BeW_{\phi}$ , or for the narrowest intended beam corresponding to the smallest $BeW_{\phi}$ (D.3, D.11). + +Directions to be tested: The OTA peak directions set reference beam direction pair (D.8). + +##### 6.4.1.3.4.2 Procedure + +- 1) Place the IAB-DU at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the IAB-DU with the test system. +- 3) Orient the positioner (and IAB-DU) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beam peak direction of the IAB-DU according to the declared beam direction pair. +- 5) For *IAB type 1-O*, set the IAB-DU to transmit a signal according to the applicable test configuration in clause 4.8 using the corresponding test models: + - IAB-DU-FR1-TM3.1a if 256QAM is supported by IAB-DU without power back off; + - IAB-DU-FR1-TM3.1 if 256QAM is not supported by IAB-DU; + - IAB-DU-FR1-TM3.1 if 256QAM is supported by IAB-DU with power back off; + For *IAB type 2-O*, set the BS to transmit a signal according to the applicable test configuration in clause 4.8 using the corresponding test model: + - IAB-DU-FR2-TM3.1a if 256QAM is supported by IAB-DU without power back off, or + - IAB-DU-FR2-TM3.1 if 256QAM is supported by BS with power back off, or 256QAM is not supported by IAB-DU; with 64QAM signals if 64QAM is supported by IAB-DU without power back off, or; + +- IAB-DU-FR2-TM3.1 with highest modulation order supported without power back off if 64QAM is not supported by IAB-DU, or; + - IAB-DU-FR2-TM3.1 with highest modulation order supported without power back off if 64QAM is supported by IAB-DU with power back off; +- 6) Measure the OFDM symbol TX power as defined in annex L 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}$ . +- 7) For *IAB type 1-O*, set the BS to transmit a signal according to the applicable test configuration in clause 4.8 using the corresponding test models: +- IAB-DU-FR1-TM2a if 256QAM is supported by IAB-DU; + - IAB-DU-FR1-TM2 if 256QAM is not supported by IAB-DU; +- For *IAB type 2-O*, set the BS to transmit a signal according to the applicable test configuration in clause 4.8 using the corresponding test models: +- IAB-DU-FR2-TM2a if 256QAM is supported by IAB-DU, or; + - IAB-DU-FR2-TM2 with highest modulation order supported if 256QAM is not supported by IAB-DU; +- 8) Measure the OFDM symbol TX power (OSTP) as defined in annex L 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}$ . + +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.1.3.5 Test requirements + +##### 6.4.1.3.5.1 IAB type 1-O + +The downlink (DL) total power dynamic range for each NR carrier shall be larger than or equal to the level in table 6.4.1.3.5.1-1. + +**Table 6.4.1.3.5.1-1: Total power dynamic range** + +| IAB channel bandwidth (MHz) | Total power dynamic range (dB) | | | +|-----------------------------|--------------------------------|------------|------------| +| | 15 kHz SCS | 30 kHz SCS | 60 kHz SCS | +| 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.3 | 19.2 | 16 | +| 40 | 22.9 | 19.8 | 16.6 | +| 45 | 23.4 | 20.3 | 17.2 | +| 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: Additional test requirements for the Error Vector Magnitude (EVM) at the lower limit of the dynamic range are defined in clause 6.6. + +#### 6.4.1.3.5.2 IAB type 2-O + +OTA total power dynamic range minimum requirement for IAB-DU *type 2-O* is specified such as for each NR carrier it shall be larger than or equal to the levels specified in table 6.3.1.3.5.2-1. + +**Table 6.4.1.3.5.2-1: Minimum requirement for IAB-DU *type 2-O* total power dynamic range** + +| SCS
(kHz) | 50 MHz | 100 MHz | 200 MHz | 400 MHz | +|--------------|------------------------------------|---------|---------|---------| +| | OTA total power dynamic range (dB) | | | | +| 60 | 17.7 | 20.8 | 23.8 | N.A | +| 120 | 14.6 | 17.7 | 20.8 | 23.8 | + +NOTE: Additional test requirements for the EVM at the lower limit of the dynamic range are defined in clause 6.6. + +## 6.4.2 IAB-MT OTA Output Power Dynamics + +### 6.4.2.1 OTA total power dynamic range + +#### 6.4.2.1.1 Definition and applicability + +The OTA total power dynamic range is the difference between the maximum and the minimum controlled transmit power in the channel bandwidth for a specified reference condition. The maximum and minimum output powers are defined as the mean power in at least one sub-frame 1ms + +NOTE: The specified reference condition(s) are specified in the conformance specification. Changes in the controlled transmit power in the channel bandwidth due to changes in the specified reference condition are not include as part of the dynamic range. + +This requirement shall apply at each RIB supporting transmission in the *operating band*. + +#### 6.4.2.1.2 Minimum requirement + +The IAB-MT total power dynamic range is defined in TS 38.174 [2], clause 9.4.2.1. + +#### 6.4.2.1.3 Test purpose + +The test purpose is to verify that the IAB-MT OTA total power dynamic range is within the limits specified by the minimum requirement. + +#### 6.4.2.1.4 Method of test + +##### 6.4.2.1.4.1 Initial conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +Beams to be tested: Declared beam with the highest intended EIRP for the narrowest intended beam corresponding to the smallest $BeW_0$ , or for the narrowest intended beam corresponding to the smallest $BeW_\phi$ (D.3, D.11). + +Directions to be tested: The OTA peak directions set reference beam direction pair (D.8). + +##### 6.4.2.1.4.2 Procedure + +- 1) Place the IAB-MT at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the IAB-MT with the test system. +- 3) Orient the positioner (and IAB-MT) in order that the direction to be tested aligns with the test antenna. + +- 4) Configure the beam peak direction of the IAB-MT according to the declared beam direction pair. +- 5) For IAB *type 1-O*, set the IAB-MT to transmit a signal according to the applicable test configuration in clause 4.8 using the corresponding test models: + - IAB-MT-FR1-TM3.1 + For IAB *type 2-O*, set the IAB-MT to transmit a signal according to the applicable test configuration in clause 4.8 using the corresponding test model: + - IAB-MT-FR2-TM3.1; +- 6) Measure the power by measuring the EIRP for any two orthogonal polarizations (denoted p1 and p2) over 1ms and calculate total EIRP for particular *beam direction pair* as $EIRP = EIRP_{p1} + EIRP_{p2}$ . +- 7) For IAB *type 1-O*, set the IAB-MT to transmit a signal according to the applicable test configuration in clause 4.8 using the corresponding test models: + - IAB-MT-FR1-TM2 + For IAB *type 2-O*, set the IAB-MT to transmit a signal according to the applicable test configuration in clause 4.8 using the corresponding test models: + - IAB-MT-FR2-TM2; +- 8) Measure the power by measuring the EIRP for any two orthogonal polarizations (denoted p1 and p2) over 1ms and calculate total EIRP for particular *beam direction pair* as $EIRP = EIRP_{p1} + EIRP_{p2}$ . + +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.1.5 Test requirements + +##### 6.4.2.1.5.1 IAB type 1-O + +For IAB-MT the $\Delta P$ between the power measured in step 6 and step 8 of clause 6.4.2.1.4.2 shall be: + +**Table 6.4.2.1.5.1-1: IAB type 1-O Output power dynamics test requirements.** + +| IAB-MT Type | IAB-MT channel bandwidth | Requirement (Note 1) | +|-------------|-----------------------------------------------|--------------------------------------------------------------------------------------| +| Wide area | $\leq 40\text{MHz}$ | $10 \log(\text{Maximum RB}) - 1.2 < \Delta P \leq 10 \log(\text{Maximum RB}) + 11.2$ | +| | $40\text{MHz} < \text{BW} \leq 100\text{MHz}$ | $10 \log(\text{Maximum RB}) - 1.5 < \Delta P \leq 10 \log(\text{Maximum RB}) + 11.5$ | +| Local area | $\leq 40\text{MHz}$ | $10 \log(\text{Maximum RB}) + 3.8 < \Delta P \leq 10 \log(\text{Maximum RB}) + 15.2$ | +| | $40\text{MHz} < \text{BW} \leq 100\text{MHz}$ | $10 \log(\text{Maximum RB}) + 3.5 < \Delta P \leq 10 \log(\text{Maximum RB}) + 16.5$ | + +##### 6.4.2.1.5.2 IAB type 2-O + +For IAB-MT the $\Delta P$ between the power measured in step 6 and step 8 of clause 6.4.2.1.4.2 shall be: + +**Table 6.4.2.1.5.2-1: IAB type 2-O Output power dynamics test requirements.** + +| IAB-MT Type | IAB-MT channel bandwidth | Requirement | +|-------------|-----------------------------------------------|--------------------------------------------------------------------------------------| +| Wide area | $\leq 40\text{MHz}$ | $10 \log(\text{Maximum RB}) - 1.2 < \Delta P \leq 10 \log(\text{Maximum RB}) + 11.2$ | +| | $40\text{MHz} < \text{BW} \leq 100\text{MHz}$ | $10 \log(\text{Maximum RB}) - 1.5 < \Delta P \leq 10 \log(\text{Maximum RB}) + 11.5$ | +| Local area | $\leq 40\text{MHz}$ | $10 \log(\text{Maximum RB}) + 3.8 < \Delta P \leq 10 \log(\text{Maximum RB}) + 15.2$ | +| | $40\text{MHz} < \text{BW} \leq 100\text{MHz}$ | $10 \log(\text{Maximum RB}) + 3.5 < \Delta P \leq 10 \log(\text{Maximum RB}) + 16.5$ | + +## 6.4.2.2 Relative power tolerance for local area IAB-MT + +### 6.4.2.2.1 Definition and applicability + +The relative power tolerance is the ability of the transmitter to set its output power in a target sub-frame (1 ms) relatively to the power of the most recently transmitted reference sub-frame (1 ms) if the transmission gap between these sub-frames is less than or equal to 20 ms. + +### 6.4.2.2.2 Minimum requirement + +The Power control for local area *IAB-MT type 1-O* is defined in TS 38.174 [2], clause 9.4.3.1.1 + +The Power control for local area *IAB-MT type 2-O* is defined in TS 38.174 [2], clause 9.4.3.2.1 + +### 6.4.2.2.3 Test purpose + +No specific test or test requirements are defined for Relative power tolerance. The Total power dynamic range test, as described in clause 6.4.2.1 provides sufficient test coverage for this requirement. + +## 6.4.2.3 Aggregate power tolerance for local area IAB-MT + +### 6.4.2.3.1 Definition and applicability + +The aggregate power control tolerance is the ability of the transmitter to maintain its power in a sub-frame (1 ms) during non-contiguous transmissions within [21 ms] in response to 0 dB commands with respect to the first transmission and all other power control parameters as specified in 3GPP TS 38.213 [9] kept constant. + +### 6.4.2.3.2 Minimum requirement + +The IAB-MT Aggregate power tolerance for local area *IAB-MT type 1-O* is defined in TS 38.174 [2], clause 9.4.3.1.2. + +The IAB-MT Aggregate power tolerance for local area *IAB-MT type 2-O* is defined in TS 38.174 [2], clause 9.4.3.2.2. + +### 6.4.2.3.3 Test purpose + +No specific test or test requirements are defined for IAB-MT Aggregate power tolerance. + +## 6.5 OTA transmit ON/OFF power + +### 6.5.1 OTA transmitter OFF power + +#### 6.5.1.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 *transmission bandwidth configuration* of the IAB ( $BW_{\text{Config}}$ ) centred on the assigned channel frequency during the *transmitter OFF period*. $N = \text{SCS}/15$ , where SCS is Sub Carrier Spacing in kHz. + +For IAB node supporting intra-band contiguous CA, the 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 *aggregated IAB-DU channel bandwidth* or *IAB-MT channel bandwidth* $BW_{\text{Channel\_CA}}$ centred on $(F_{\text{edge,high}} + F_{\text{edge,low}})/2$ during the *transmitter OFF period*. $N = \text{SCS}/15$ , where SCS is the smallest supported Sub Carrier Spacing in kHz in the *aggregated IAB-DU channel bandwidth* or *aggregated IAB-MT channel bandwidth*. + +For *IAB type 1-O*, the transmitter OFF power is defined as the output power at the *co-location reference antenna* conducted output(s). For *IAB type 2-O* the transmitter OFF power is defined as TRP. + +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*. + +### 6.5.1.2 Minimum requirement + +The minimum requirement for *IAB-DU type 1-O* is in TS 38.174 [2], clause 9.5.2.2. + +The minimum requirement for *IAB-DU type 2-O* is in TS 38.174 [2], clause 9.5.2.3. + +The minimum requirement for *IAB-MT type 1-O* is in TS 38.174 [2], clause 9.5.2.4. + +The minimum requirement for *IAB-MT type 2-O* is in TS 38.174 [2], clause 9.5.2.5. + +### 6.5.1.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.1.4 Method of test + +Requirement is tested together with transmitter transient period, as described in clause 6.5.2.4. + +### 6.5.1.5 Test requirements + +The conformance testing of transmit OFF power is included in the conformance testing of transmitter transient period; therefore, see clause 6.5.2.5 for test requirements. + +## 6.5.2 OTA transmitter transient period + +### 6.5.2.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.2.1-1. + +![Figure 6.5.2.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period for IAB. The 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' and 'OFF power level'. The x-axis is divided into three main segments: 'UL/DL transmission' (left), 'Transmitter ON period (DL/UL transmission)' (middle), and 'GP or UL/DL transmission' (right). The 'Transmitter transient period' is indicated by two double-headed arrows: one at the start of the ON period and one at the end. The 'Transmitter OFF period' is indicated by two double-headed arrows: one before the start of the ON period and one after the end of the ON period.](b9c42023cf4cb9547293c74191ea87a9_img.jpg) + +Figure 6.5.2.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period for IAB. The 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' and 'OFF power level'. The x-axis is divided into three main segments: 'UL/DL transmission' (left), 'Transmitter ON period (DL/UL transmission)' (middle), and 'GP or UL/DL transmission' (right). The 'Transmitter transient period' is indicated by two double-headed arrows: one at the start of the ON period and one at the end. The 'Transmitter OFF period' is indicated by two double-headed arrows: one before the start of the ON period and one after the end of the ON period. + +**Figure 6.5.2.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period for IAB** + +For *IAB type 1-O*, this requirement applies for RIB supporting transmission in the *operating band* and is measured at the *co-location test antenna* conducted outputs. For *IAB type 2-O*, the requirement applies at each RIB supporting transmission in the *operating band*. + +### 6.5.2.2 Minimum requirement + +The minimum requirement for *IAB-DU type 1-O* is in TS 38.174 [2], clause 9.5.3.2. + +The minimum requirement for *IAB-DU type 2-O* is in TS 38.174 [2], clause 9.5.3.3. + +The minimum requirement for *IAB-MT type 1-O* is in TS 38.174 [2], clause 9.5.3.4. + +The minimum requirement for *IAB-MT type 2-O* is in TS 38.174 [2], clause 9.5.3.5. + +### 6.5.2.3 Test purpose + +The purpose of this test is to verify the OTA transmitter transient periods are 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 B.2. + +RF channels to be tested: M; see clause 4.9.1. + +*Base Station RF Bandwidth* positions to be tested for multi-carrier and/or CA: + +- $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. + +Directions to be tested: + +- The requirement for *IAB type 1-O* is specified as co-location requirement. For general description of co-location requirements, refer to clause 4.12. +- The requirement for *IAB type 2-O* is verified by an EIRP measurement at a direction corresponding to the OTA peak directions set reference beam direction pair (D.8) for the beam identifier (D.3) which provides the highest intended EIRP. + +#### 6.5.2.4.2 Procedure + +##### 6.5.2.4.2.1 General procedure + +- 1) Place the IAB node at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the IAB node with the test system. + +##### 6.5.2.4.2.2 IAB type 1-O + +- 3) Set the IAB node 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.12. +- 5) Configure the beam peak direction of the IAB node according to the declared beam direction pair. +- 6) Set the IAB node to transmit according to the applicable test configuration in clause 4.8 using the corresponding test models or set of physical channels in clause 4.9.2. + +For an IAB node declared to be capable of Simultaneous transmission between IAB-DU and IAB-MT (D. IAB-3), above steps will apply for IAB-MT or IAB-DU respectively according to test singal configuration and test models specified in clauses 4.7.2 and 4.8 with both IAB-MT and IAB-DU configured. + +For an IAB node declared to be capable of multi-carrier and/or CA operation, use the applicable test signal configuration and corresponding power setting specified in clauses 4.7.2 and 4.8 using the corresponding test models or set of physical channels in clause 4.9.2 on all carriers configured. + +- 7) Measure the mean power spectral density at the output(s) of co-location test antenna as power sum over two orthogonal polarizations over $70/N \mu\text{s}$ filtered with a square filter of bandwidth equal to the RF bandwidth of the IAB node 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 = \text{SCS}/15$ , where SCS is Sub Carrier Spacing in kHz. +- 8) For an IAB node supporting contiguous CA, measure the mean power spectral density at the output(s) of co-location test antenna as power sum over two orthogonal polarizations over $70/N \mu\text{s}$ filtered with a square filter of bandwidth equal to the *aggregated IAB-DU channel bandwidth* or *aggregated IAB-MT channel bandwidth* $\text{BW}_{\text{Channel\_CA}}$ centred on $(F_{\text{edge\_high}} + F_{\text{edge\_low}})/2$ . $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 = \text{SCS}/15$ , where SCS is the smallest supported Sub Carrier Spacing in kHz in the *aggregated IAB-DU channel bandwidth* or *aggregated IAB-MT channel bandwidth*. + +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.4.2.3 IAB type 2-O + +- 3) Set the IAB node in the direction of the declared beam peak direction of the *beam direction pair*, for the beam to be tested. +- 4) Set the IAB node to transmit according to the applicable test configuration in clause 4.8 using the corresponding test model IAB-DU-FR2-TM1.1 or IAB-MT-FR2-TM1.1 and set of physical channels in clause 4.9.2. + +For a IAB node declared to be capable of multi-carrier and/or CA operation, use the applicable test signal configuration and corresponding power setting specified in clauses 4.7.2 and 4.8 using the corresponding test model IAB-DU-FR2-TM1.1 or IAB-MT-FR2-TM1.1 and set of physical channels in clause 4.9.2 on all carriers configured. + +For an IAB node declared to be capable of Simultaneous transmission between IAB-DU and IAB-MT (D. IAB-3), above steps will apply for IAB-MT or IAB-DU respectively according to test signal configuration and test models specified in clauses 4.7.2 and 4.8 with both IAB-MT and IAB-DU configured. + +- 5) Measure the mean EIRP spectral density as the power sum over two orthogonal polarizations over $70/N \mu\text{s}$ filtered with a square filter of bandwidth equal to the RF bandwidth of the IAB node 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 + $3 \mu\text{s}$ to $35/N \mu\text{s}$ before start of next transmitter ON period - $3 \mu\text{s}$ . $N = \text{SCS}/15$ , where SCS is Sub Carrier Spacing in kHz. + +NOTE: Make sure that the measurement receiver is not overloaded. + +- 6) For an IAB node supporting contiguous CA, measure the mean EIRP spectral density as the power sum over two orthogonal polarizations over $70/N \mu\text{s}$ filtered with a square filter of bandwidth equal to the *aggregated IAB-DU channel bandwidth* or *aggregated IAB-MT channel bandwidth* $\text{BW}_{\text{Channel\_CA}}$ centred on $(F_{\text{edge\_high}} + F_{\text{edge\_low}})/2$ . $70/N \mu\text{s}$ average window centre is set from $35/N \mu\text{s}$ after end of one transmitter ON period + $3 \mu\text{s}$ to $35/N \mu\text{s}$ before start of next transmitter ON period - $3 \mu\text{s}$ . $N = \text{SCS}/15$ , where SCS is the smallest supported Sub Carrier Spacing in kHz in the *aggregated IAB-DU channel bandwidth* or *aggregated IAB-MT channel bandwidth*. + +#### 6.5.2.5 Test requirements + +##### 6.5.2.5.1 IAB type 1-O + +The mean power spectral density measured according to clause 6.5.2.4.2 shall be less than $-102.6 \text{ dBm/MHz}$ for carrier frequency $f \leq 3.0 \text{ 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 \text{ GHz} < f \leq 6.0 \text{ GHz}$ . + +For *multi-band RIB*, the requirement is only applicable during the transmitter OFF period in all supported operating bands. + +For *IAB simultaneous transmission*, the requirement is only applicable during the transmitter OFF period for both IAB-DU and IAB-MT. + +#### 6.5.2.5.2 IAB type 2-O + +The measured mean EIRP spectral density according to clause 6.5.2.4.2 shall be less than $-33.1 + P_{\text{rated,c,EIRP}} - P_{\text{rated,c,TRP}}$ dBm/MHz for carrier frequency $24.15 \text{ GHz} < f \leq 29.5 \text{ GHz}$ , where $P_{\text{rated,c,EIRP}}$ is the value declared for the *reference beam direction pair* (D.8) for the beam identifier (D.3) which provides the highest intended EIRP. + +The measured mean EIRP spectral density according to clause 6.5.2.4.2 shall be less than $-32.7 + P_{\text{rated,c,EIRP}} - P_{\text{rated,c,TRP}}$ dBm/MHz for carrier frequency $37 \text{ GHz} < f \leq 43.5 \text{ GHz}$ , where $P_{\text{rated,c,EIRP}}$ is the value declared for the *reference beam direction pair* (D.8) for the beam identifier (D.3) which provides the highest intended EIRP. + +For *IAB simultaneous transmission*, the requirement is only applicable during the transmitter OFF period for both IAB-DU and IAB-MT. + +## 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 IAB-DU OTA frequency error + +##### 6.6.2.1.1 Definition and applicability + +For IAB-DU, OTA frequency error is the measure of the difference between the actual IAB-DU transmit frequency and the assigned frequency. The same source shall be used for RF frequency and data clock generation. + +For IAB-DU, 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.1.2 Minimum Requirement + +The minimum requirements for *IAB-DU type 1-O* and *IAB-DU type 2-O* are in TS 38.174 [2], clause 9.6.1.1. + +##### 6.6.2.1.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.1.4 Method of test + +Requirement is tested together with OTA modulation quality test, as described in clause 6.6.3. + +##### 6.6.2.1.4.1 Initial conditions + +Directions to be tested: OTA coverage range reference direction (D.35). + +#### 6.6.2.1.5 Test Requirements + +For IAB-DU, the modulated carrier frequency of each NR carrier configured by the IAB-DU shall be accurate to within the accuracy range given in table 6.6.2.1.5-1 observed over 1 ms. + +**Table 6.6.2.1.5-1: OTA frequency error test requirement for IAB-DU type 1-O and IAB-DU type 2-O** + +| IAB-DU class | Accuracy | +|---------------------|-----------------------------------------| +| Wide Area IAB-DU | $\pm(0.05 \text{ ppm} + 12 \text{ Hz})$ | +| Medium Range IAB-DU | $\pm(0.1 \text{ ppm} + 12 \text{ Hz})$ | +| Local Area IAB-DU | $\pm(0.1 \text{ ppm} + 12 \text{ Hz})$ | + +#### 6.6.2.2 IAB-MT OTA frequency error + +##### 6.6.2.2.1 Definition and applicability + +For IAB-MT, OTA frequency error is the measure of the difference between actual IAB-MT transmit frequency and the carrier frequency received from the parent node. + +For IAB-MT, 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.2 Minimum Requirement + +The minimum requirement for IAB-MT type 1-O and IAB-MT type 2-O are in TS 38.174 [2], clause 9.6.1.2. + +##### 6.6.2.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.2.4 Method of test + +Requirement is tested together with OTA modulation quality test, as described in clause 6.6.3. + +###### 6.6.2.2.4.1 Initial conditions + +Directions to be tested: OTA coverage range reference direction (D.35). + +##### 6.6.2.2.5 Test Requirements + +For IAB-MT type 1-O and IAB-MT type 2-O, the mean value of basic measurements of IAB-MT modulated carrier frequency shall be accurate to within the accuracy range given in table 6.6.2.2.5-1 observed over 1 ms cumulated measurement intervals compared to the carrier frequency received from the parent node. + +**Table 6.6.2.2.5-1: OTA frequency error test requirement for IAB-MT type 1-O** + +| IAB-MT frequency range | Accuracy | +|-----------------------------------------------|-------------------------------------------| +| $f \leq 3.0 \text{ GHz}$ | $\pm(0.1 \text{ ppm} + 15 \text{ Hz})$ | +| $3.0 \text{ GHz} < f \leq 7.125 \text{ GHz}$ | $\pm(0.1 \text{ ppm} + 36 \text{ Hz})$ | +| $24.25 \text{ GHz} < f \leq 52.6 \text{ GHz}$ | $\pm(0.1 \text{ ppm} + 0.01 \text{ ppm})$ | + +#### 6.6.3 OTA modulation quality + +##### 6.6.3.1 Definition and applicability + +OTA modulation quality is defined by the difference between the measured carrier signal and an ideal signal. Modulation quality can e.g. be expressed as Error Vector Magnitude (EVM). The Error Vector Magnitude is a measure + +of the difference between the ideal symbols and the measured symbols after the equalization. This difference is called the error vector. + +OTA modulation quality 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 + +The minimum requirement for *IAB-DU type 1-O*, is in TS 38.174 [2], clause 9.6.2.1. + +The minimum requirement for *IAB-DU type 2-O*, is in TS 38.174 [2], clause 9.6.2.1. + +The minimum requirement for *IAB-MT type 1-O*, is in TS 38.174 [2], clause 9.6.2.2. + +The minimum requirement for *IAB-MT type 2-O*, is in TS 38.174 [2], clause 9.6.2.3. + +### 6.6.3.3 Test purpose + +The test purpose is to verify that OTA modulation quality is within the limit specified by the minimum requirement. + +### 6.6.3.4 Method of test + +#### 6.6.3.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: + +- B and T; see clause 4.9.1. + +*IAB 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.9.1; +- $B_{\text{RFBW\_T'}}$ and $B'_{\text{RFBW\_T}}$ in multi-band operation, see clause 4.9.1. + +Directions to be tested: + +- The OTA coverage range reference direction (D.35). +- The OTA coverage range maximum directions (D.36). + +Polarizations to be tested: For dual polarized systems the requirement shall be tested and met for both polarizations. + +#### 6.6.3.4.2 Procedure for IAB-DU + +- 1) Place the IAB-DU at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the IAB-DU with the test system. +- 3) Orient the positioner (and IAB-DU) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beamforming settings of the IAB-DU according to the direction to be tested. +- 5) Set the IAB-DU to output according to the applicable test configuration in clause 4.8 using the corresponding test models or set of physical channels in clause 4.9.2. + +For *IAB-DU type 1-O* declared to be capable of single carrier operation only, set the IAB-DU to transmit a signal according to: + +- IAB-DU-FR1-TM3.1a if 256QAM is supported by IAB-DU without power back off +- or IAB-DU-FR1-TM3.1a if 256QAM is supported by IAB-DU with power back off, at manufacturer's declared rated output power ( $P_{\text{rated,c,EIRP}}$ ) and IAB-DU-FR1-TM3.1 at maximum power + +- or IAB-DU-FR1-TM3.1 if highest modulation order supported by IAB-DU is 64QAM +- or IAB-DU-FR1-TM3.2 if highest modulation order supported by IAB-DU is 16QAM +- or IAB-DU-FR1-TM3.3 if highest modulation order supported by IAB-DU is QPSK. + +For *IAB-DU type 1-O* declared to be capable of multi-carrier and/or CA operation, set the IAB-DU to transmit according to the applicable test signal configuration and corresponding power setting specified in clauses 4.7.2 and 4.8 using the corresponding test models on all carriers configured: + +- IAB-DU-FR1-TM3.1a if 256QAM is supported by IAB-DU without power back off +- or IAB-DU-FR1-TM3.1a if 256QAM is supported by IAB-DU with power back off, at manufacturer's declared rated output power ( $P_{\text{rated,c,EIRP}}$ ) and IAB-DU-FR1-TM3.1 at maximum power +- or IAB-DU-FR1-TM3.1 if highest modulation order supported by IAB-DU is 64QAM +- or IAB-DU-FR1-TM3.2 if highest modulation order supported by IAB-DU is 16QAM +- or IAB-DU-FR1-TM3.3 if highest modulation order supported by IAB-DU is QPSK. + +For *IAB-DU type 2-O* declared to be capable of single carrier operation only, set the IAB-DU to transmit a signal according to the applicable test signal configuration and corresponding power setting specified in clause 4.7.2 and 4.8 using the corresponding test models on all carriers configured: + +- IAB-DU-FR2-TM3.1a with 256QAM signal if 256QAM is supported by IAB-DU without power back off, or +- IAB-DU-FR2-TM3.1a at manufacturer's declared rated output power if 256QAM is supported by IAB-DU with power back off, and IAB-DU-FR2-TM3.1 with highest modulation order supported without power back off, or +- IAB-DU-FR2-TM3.1 with 64QAM signal if 64QAM is supported by IAB-DU without power back off, or +- IAB-DU-FR2-TM 3.1 with highest modulation order without power back off if 64QAM is not supported by IAB-DU, or +- if 64 QAM is supported by IAB-DU with power back off, IAB-DU-FR2-TM 3.1 with 64QAM at manufacturer's declared rated output power ( $P_{\text{rated,c,EIRP}}$ ) and IAB-DU-FR2-TM3.1 with highest modulation order supported at maximum power. + +For *IAB-DU type 2-O* declared to be capable of multi-carrier and/or CA operation, set the IAB-DU or IAB-MT to transmit according to: + +- IAB-DU-FR2-TM3.1a with 256QAM signal if 256QAM is supported by IAB-DU without power back off, or +- IAB-DU-FR2-TM3.1a at manufacturer's declared rated output power if 256QAM is supported by IAB-DU with power back off, and IAB-DU-FR2-TM3.1 at maximum power, or +- IAB-DU-FR2-TM3.1 with 64QAM signal if 64QAM is supported by IAB-DU without power back off, or +- IAB-DU-FR2-TM3.1 with highest modulation order supported without power back off if 64QAM is not supported by IAB-DU, or +- if 64QAM is supported by IAB-DU with power back off, IAB-DU-FR2-TM3.1 with 64QAM signal at manufacturer's declared rated output power ( $P_{\text{rated,c,EIRP}}$ ) and IAB-DU-FR2-TM3.1 with highest supported modulation order at maximum power + +For IAB-DU-FR1-TM 3.1a and IAB-DU-FR2-TM 3.1, power back-off shall be applied if it is declared. + +- 6) For each carrier, measure the EVM and frequency error as defined in annex L. +- 7) Repeat steps 5 and 6 for IAB-DU-FR1-TM2 if 256QAM is not supported by *IAB-DU type 1-O* or for IAB-DU-FR1-TM2a if 256QAM is supported by *IAB-DU type 1-O*. For IAB-DU-FR1-TM2 and IAB-DU-FR1-TM2a 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.3.4.2 and test requirements in clause 6.4.3.5.1. + +Repeat steps 5 and 6 for IAB-DU-FR2-TM2 if 256QAM is not supported by *IAB-DU type 2-O* or for IAB-DU-FR2-TM2a if 256QAM is supported by *IAB-DU type 2-O*. For IAB-DU-FR2-TM2 and IAB-DU-FR1-TM2a 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.3.4.2 and test requirements in clause 6.4.3.5.2. + +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.3.4.3 Procedure for IAB-MT + +- 1) Place the IAB-MT at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the IAB-MT with the test system. +- 3) Orient the positioner (and IAB-MT) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beamforming settings of the IAB-MT according to the direction to be tested. +- 5) Set the IAB-MT to output according to the applicable test configuration in clause 4.8 using the corresponding test models or set of physical channels in clause 4.9.2. + +For *IAB-MT type 1-O* declared to be capable of single carrier operation only, set the IAB-MT to transmit a signal according to: + +- IAB-MT-FR1-TM3.1a if 256QAM is supported by IAB-MT without power back off +- or IAB-MT-FR1-TM3.1a if 256QAM is supported by IAB-MT with power back off, at manufacturer's declared rated output power ( $P_{\text{rated,c,EIRP}}$ ) and IAB-MT-FR1-TM3.1 at maximum power +- or IAB-MT-FR1-TM3.1 with highest modulation order supported by IAB-MT. + +For *IAB-MT type 1-O* declared to be capable of multi-carrier and/or CA operation, set the IAB-MT to transmit according to the applicable test signal configuration and corresponding power setting specified in clauses 4.7.2 and 4.8 using the corresponding test models on all carriers configured: + +- IAB-MT-FR1-TM3.1a if 256QAM is supported by IAB-MT without power back off +- or IAB-MT-FR1-TM3.1a if 256QAM is supported by IAB-MT with power back off, at manufacturer's declared rated output power ( $P_{\text{rated,c,EIRP}}$ ) and IAB-MT-FR1-TM3.1 at maximum power +- or IAB-MT-FR1-TM3.1 with highest modulation order supported by IAB-MT. + +For *IAB-MT type 2-O* declared to be capable of single carrier operation only, set the IAB-MT to transmit a signal according to the applicable test signal configuration and corresponding power setting specified in clause 4.7.2 and 4.8 using the corresponding test models on all carriers configured: + +- IAB-MT-FR2-TM3.1 with 64QAM signal if 64QAM is supported by IAB-MT without power back off, or +- IAB-MT-FR2-TM 3.1 with highest modulation order without power back off if 64QAM is not supported by IAB-MT, or +- if 64 QAM is supported by IAB-MT with power back off, IAB-MT-FR2-TM 3.1 with 64QAM at manufacturer's declared rated output power ( $P_{\text{rated,c,EIRP}}$ ) and IAB-MT-FR2-TM3.1 with highest modulation order supported at maximum power. + +For *IAB-MT type 2-O* declared to be capable of multi-carrier and/or CA operation, set the IAB-MT to transmit according to: + +- IAB-MT-FR2-TM3.1 with 64QAM signal if 64QAM is supported by IAB-MT without power back off, or +- IAB-MT-FR2-TM3.1 with highest modulation order supported without power back off if 64QAM is not supported by IAB-MT, or +- if 64QAM is supported by IAB-MT with power back off, IAB-MT-FR2-TM3.1 with 64QAM signal at manufacturer's declared rated output power ( $P_{\text{rated,c,EIRP}}$ ) and IAB-MT-FR2-TM3.1 with highest supported modulation order at maximum power + +For IAB-MT-FR1-TM 3.1a and IAB-MT-FR2-TM 3.1, power back-off shall be applied if it is declared. + +- 6) For each carrier, measure the EVM and frequency error as defined in annex L. +- 7) Repeat steps 5 and 6 for IAB-MT-FR1-TM2 if 256QAM is not supported by *IAB-MT type 1-O* or for IAB-MT-FR1-TM2a if 256QAM is supported by *IAB-MT type 1-O*. For IAB-MT-FR1-TM2 and IAB-MT-FR1-TM2a 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.3.4.2 and test requirements in clause 6.4.3.5.1. + +Repeat steps 5 and 6 for IAB-MT-FR2-TM2 if 256QAM is not supported by *IAB-MT type 2-O* or for IAB-MT-FR2-TM2a if 256QAM is supported by *IAB-MT type 2-O*. For IAB-DU-FR2-TM2 and IAB-DU-FR1-TM2a 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.3.4.2 and test requirements in clause 6.4.3.5.2. + +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.3.5 Test requirements + +#### 6.6.3.5.1 *IAB-DU type 1-O* and *IAB-MT type 1-O* + +For *IAB-DU type 1-O* or *IAB-MT type 1-O*, the EVM of each NR carrier for different modulation schemes on PDSCH or PUSCH shall be less than the limits in table 6.6.3.5.1-1. + +**Table 6.6.3.5.1-1: EVM requirements for *IAB type 1-O*** + +| Modulation scheme for PDSCH or PUSCH | Required EVM (%) | +|--------------------------------------|------------------| +| QPSK | 18.5 | +| 16QAM | 13.5 | +| 64QAM | 9 | +| 256QAM | 4.5 | + +EVM shall be evaluated for each NR carrier over all allocated resource blocks and downlink slots for IAB-DU or uplink slots for IAB-MT. Different modulation schemes listed in table 6.6.3.5.1-1 shall be considered for rank 1. + +For all bandwidths, the EVM measurement shall be performed for each NR carrier over all allocated resource blocks and downlink slots for IAB-DU or uplink slots for IAB-MT within 10 ms measurement periods. The boundaries of the EVM measurement periods need not be aligned with radio frame boundaries. + +Tables 6.6.3.5.1-2, 6.6.3.5.1-3, 6.6.3.5.1-4 below specify the EVM window length (*W*) for normal CP for *IAB type 1-O*. + +6.6.3.5.1-3, 6.6.3.5.1-4 below specify the EVM window length (*W*) for normal CP for *IAB type 1-O*. + +**Table 6.6.3.5.1-2: EVM window length for normal CP, FR1, 15 kHz SCS** + +| Channel bandwidth (MHz) | FFT size | Cyclic prefix length for symbols 1-6 and 8-13 in FFT samples | EVM window length W | Ratio of W to total CP length for symbols 1-6 and 8-13 (Note) (%) | +|-------------------------|----------|--------------------------------------------------------------|----------------------------|--------------------------------------------------------------------------| +| 10 | 1024 | 72 | 28 | 40 | +| 15 | 1536 | 108 | 44 | 40 | +| 20 | 2048 | 144 | 58 | 40 | +| 25 | 2048 | 144 | 72 | 50 | +| 30 | 3072 | 216 | 108 | 50 | +| 35 | 3072 | 216 | 108 | 50 | +| 40 | 4096 | 288 | 144 | 50 | +| 45 | 4096 | 288 | 144 | 50 | +| 50 | 4096 | 288 | 144 | 50 | + +NOTE: These percentages are informative and apply to a slot's symbols 1 to 6 and 8 to 13. Symbols 0 and 7 have a longer CP and therefore a lower percentage. + +**Table 6.6.3.5.1-3: EVM window length for normal CP, FR1, 30 kHz SCS** + +| Channel bandwidth (MHz) | FFT size | Cyclic prefix length for symbols 1-13 in FFT samples | EVM window length W | Ratio of W to total CP length for symbols 1-13 (Note) (%) | +|-------------------------|----------|------------------------------------------------------|----------------------------|------------------------------------------------------------------| +| 10 | 512 | 36 | 14 | 40 | +| 15 | 768 | 54 | 22 | 40 | +| 20 | 1024 | 72 | 28 | 40 | +| 25 | 1024 | 72 | 36 | 50 | +| 30 | 1536 | 108 | 54 | 50 | +| 35 | 1536 | 108 | 54 | 50 | +| 40 | 2048 | 144 | 72 | 50 | +| 45 | 2048 | 144 | 72 | 50 | +| 50 | 2048 | 144 | 72 | 50 | +| 60 | 3072 | 216 | 130 | 60 | +| 70 | 3072 | 216 | 130 | 60 | +| 80 | 4096 | 288 | 172 | 60 | +| 90 | 4096 | 288 | 172 | 60 | +| 100 | 4096 | 288 | 172 | 60 | + +NOTE: These percentages are informative and apply to a slot's symbols 1 through 13. Symbol 0 has a longer CP and therefore a lower percentage. + +**Table 6.6.3.5.1-4: EVM window length for normal CP for NR, FR1, 60 kHz SCS** + +| Channel bandwidth (MHz) | FFT size | Cyclic prefix length in FFT samples | EVM window length W | Ratio of W to total CP (Note) (%) | +|-------------------------|----------|-------------------------------------|----------------------------|------------------------------------------| +| 10 | 256 | 18 | 8 | 40 | +| 15 | 384 | 27 | 11 | 40 | +| 20 | 512 | 36 | 14 | 40 | +| 25 | 512 | 36 | 18 | 50 | +| 30 | 768 | 54 | 26 | 50 | +| 35 | 768 | 54 | 26 | 50 | +| 40 | 1024 | 72 | 36 | 50 | +| 45 | 1024 | 72 | 36 | 50 | +| 50 | 1024 | 72 | 36 | 50 | +| 60 | 1536 | 108 | 64 | 60 | +| 70 | 1536 | 108 | 64 | 60 | +| 80 | 2048 | 144 | 86 | 60 | +| 90 | 2048 | 144 | 86 | 60 | +| 100 | 2048 | 144 | 86 | 60 | + +NOTE: These percentages are informative and apply to all OFDM symbols within subframe except for symbol 0 of slot 0 and slot 2. Symbol 0 of slot 0 and slot 2 may have a longer CP and therefore a lower percentage. + +### 6.6.3.5.2 IAB-DU type 2-O and IAB-MT type 2-O + +For IAB-DU type 2-O and IAB-MT type 2-O, the EVM of each NR carrier for different modulation schemes on PDSCH or PUSCH shall be less than the limits in table 6.6.3.5.2-1. + +**Table 6.6.3.5.2-1: EVM requirements for IAB type 2-O** + +| Modulation scheme for PDSCH or PUSCH | Required EVM (%) | +|--------------------------------------|------------------| +| QPSK | 18.5 | +| 16QAM | 13.5 | +| 64QAM | 9 | +| 256QAM | 4.5 | + +NOTE: 256QAM is not supported by FR2-1 IAB-MT PUSCH + +EVM requirements shall apply for each NR carrier over all allocated resource blocks and downlink slots for IAB-DU or uplink slots for IAB-MT. PT-RS should be configured for localized setting for every fourth symbol for every second RB for IAB-DU and IAB-MT. Different modulation schemes listed in table 6.6.3.5.2-1 shall be considered for rank 1. + +For all bandwidths, the EVM measurement shall be performed for each NR carrier over all allocated resource blocks and downlink slots for IAB-DU or uplink slots for IAB-MT within 10 ms measurement periods. The boundaries of the EVM measurement periods need not be aligned with radio frame boundaries. + +Tables 6.6.3.5.2-2 and 6.6.3.5.2-3 below specify the EVM window length ( $W$ ) for normal CP for *IAB-DU type 2-O* and *IAB-MT type 2-O*. + +**Table 6.6.3.5.2-2: EVM window length for normal CP, FR2-1, 60 kHz SCS** + +| Channel bandwidth (MHz) | FFT size | Cyclic prefix length in FFT samples | EVM window length $W$ | Ratio of $W$ to total CP length (Note) (%) | +|-------------------------|----------|-------------------------------------|-----------------------|--------------------------------------------| +| 50 | 1024 | 72 | 36 | 50 | +| 100 | 2048 | 144 | 72 | 50 | +| 200 | 4096 | 288 | 144 | 50 | + +NOTE: These percentages are informative and apply to all OFDM symbols within subframe except for symbol 0 of slot 0 and slot 2. Symbol 0 of slot 0 and slot 2 may have a longer CP and therefore a lower percentage. + +**Table 6.6.3.5.2-3: EVM window length for normal CP, FR2-1, 120 kHz SCS** + +| Channel bandwidth (MHz) | FFT size | Cyclic prefix length in FFT samples | EVM window length $W$ | Ratio of $W$ to total CP length (Note) (%) | +|-------------------------|----------|-------------------------------------|-----------------------|--------------------------------------------| +| 50 | 512 | 36 | 18 | 50 | +| 100 | 1024 | 72 | 36 | 50 | +| 200 | 2048 | 144 | 72 | 50 | +| 400 | 4096 | 288 | 144 | 50 | + +NOTE: These percentages are informative and apply to all OFDM symbols within subframe except for symbol 0 of slot 0 and slot 4. Symbol 0 of slot 0 and slot 4 may have a longer CP and therefore a lower percentage. + +## 6.6.4 OTA time alignment error + +### 6.6.4.1 Definition and applicability + +For IAB-DU, this requirement shall apply to frame timing in MIMO transmission, carrier aggregation and their combinations. There's no time alignment error requirement for IAB-MT. + +Frames of the 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 NR signals. 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.4.2 Minimum requirement + +The minimum requirement for *IAB-DU type 1-O* is in TS 38.174 [2], clause 9.6.3.1. + +The minimum requirement for *IAB-DU type 2-O* is in TS 38.174 [2], clause 9.6.3.1. + +### 6.6.4.3 Test purpose + +To verify that the OTA time alignment error is within the limit specified by the minimum requirement. + +### 6.6.4.4 Method of test + +#### 6.6.4.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +*IAB-DU RF Bandwidth* positions to be tested for multi-carrier and/or CA: + +- $M_{\text{RFBW}}$ in single-band operation, see clause 4.9.1; +- $B_{\text{RFBW\_T\_RFBW}}$ and $B'_{\text{RFBW\_T\_RFBW}}$ in multi-band operation, see clause 4.9.1. + +Directions to be tested: OTA coverage range reference direction (D.35). + +Polarizations to be tested: 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 IAB-DU polarisations such that it receives half the power from each polarisation. + +#### 6.6.4.4.2 Procedure for IAB-DU + +- 1) Place the IAB-DU at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the IAB-DU with the test system. +- 3) Orient the positioner (and IAB-DU) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beamforming settings of the IAB-DU according to the direction of the testing. +- 5) Set the *IAB-DU type 1-O* to transmit IAB-DU-FR1-TM1.1 or any DL signal using MIMO transmission or carrier aggregation, using the configuration with the minimum number of cells and reference signals. + +Set the *IAB-DU type 2-O* to transmit IAB-DU-FR2-TM 1.1 or any DL signal using MIMO transmission or carrier aggregation, using the configuration with the minimum number of cells and reference signals. + +NOTE: For MIMO transmission, different ports may be configured in IAB-DU-FR1-TM1.1 and IAB-DU-FR2-TM 1.1 (using DMRS ports $p = 1000$ and $1001$ with CDM). + +For an IAB-DU declared to be capable of single carrier operation only, set the IAB-DU to transmit according to the applicable test configuration in clause 4.8 using the corresponding test model at manufacturer's declared rated output power, $P_{\text{rated,c,TRP}}$ . + +If the IAB-DU supports intra band contiguous or non-contiguous Carrier Aggregation set the IAB-DU to transmit using the applicable test configuration and corresponding power setting specified in clauses 4.7.2 and 4.8. + +If the IAB-DU supports inter band carrier aggregation set the IAB-DU to transmit, for each band, a single carrier or all carriers, using the applicable test configuration and corresponding power setting specified in clauses 4.7.2 and 4.8. + +For *IAB-DU type 1-O* declared to be capable of multi-carrier operation, set the IAB-DU to transmit according to the applicable test signal configuration and corresponding power setting specified in clauses 4.7.2 and 4.8 using the corresponding test model on all carriers configured. + +For *IAB-DU type 2-O* declared to be capable of multi-carrier operation, set the IAB-DU to transmit according to the applicable test signal configuration and corresponding power setting specified in clauses 4.7.2 and 4.8 using the corresponding test model on all carriers configured. + +- 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.4.5 Test Requirement + +##### 6.6.4.5.1 *IAB-DU type 1-O* + +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 µs. + +For inter-band carrier aggregation, with or without MIMO, OTA TAE shall not exceed 3.025 µs. + +##### 6.6.4.5.2 *IAB-DU type 2-O* + +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 155 ns. + +For intra-band non-contiguous carrier aggregation, with or without MIMO, OTA TAE shall not exceed 285 ns. + +For inter-band carrier aggregation, with or without MIMO, OTA TAE shall not exceed 3.025 µs. + +#### 6.6.5 Timing error between IAB-DU and IAB-MT + +##### 6.6.5.1 Definition and applicability + +This requirement shall apply to IAB-DU DL and IAB-MT UL simultaneous transmission. + +The timing error between IAB-DU and IAB-MT is specified for a specific set of simultaneous signals/transmitter configuration/transmission mode. + +##### 6.6.5.2 Minimum requirement + +The minimum requirement for *IAB type 1-O* is in TS 38.174 [2], clause 6.5.4. + +The minimum requirement for *IAB type 2-O* is in TS 38.174 [2], clause 9.6.4. + +##### 6.6.5.3 Test purpose + +To verify that the OTA timing error between IAB-DU and IAB-MT simultaneous transmission is within the limit specified by the minimum requirement. + +##### 6.6.5.4 Method of test + +###### 6.6.5.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +*IAB-DU RF Bandwidth* positions to be tested for multi-carrier and/or CA: + +- $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. + +Directions to be tested: OTA coverage range reference direction (D.35). + +Polarizations to be tested: 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 IAB-DU polarisations such that it receives half the power from each polarisation. + +#### 6.6.5.4.2 Procedure + +- 1) Place the IAB-DU and IAB-MT at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the IAB-DU and IAB-MT with the test system. +- 3) Orient the positioner (and IAB-DU and IAB-MT) in order that the direction to be tested aligns with the test antenna. +- 4) Configure the beamforming settings of the IAB-DU and IAB-MT according to the direction of the testing. +- 5) Set the *IAB type 1-O* to transmit IAB-DU-FR1-TM1.1 or IAB-MT-FR1-TM1.1, using the configuration with the minimum number of cells and reference signals. + - Set the *IAB type 2-O* to transmit IAB-DU-FR2-TM 1.1 or IAB-MT-FR1-TM1.1 using the configuration with the minimum number of cells and reference signals. + - For an IAB-DU declared to be capable of single carrier operation only, set the IAB-DU to transmit according to the applicable test configuration in clause 4.8 using the corresponding test model at manufacturer's declared rated output power, $P_{\text{rated,c,TRP}}$ . + - For *IAB type 1-O* declared to be capable of multi-carrier operation, set the IAB-DU and IAB-MT to transmit according to the applicable test signal configuration and corresponding power setting specified in clauses 4.7.2 and 4.8 using the corresponding test model on all carriers configured. + - For *IAB type 2-O* declared to be capable of multi-carrier operation, set the IAB-DU and IAB-MT to transmit according to the applicable test signal configuration and corresponding power setting specified in clauses 4.7.2 and 4.8 using the corresponding test model on all carriers configured. +- 6) Measure the timing error between the DM-RS symbols on the IAB-DU and IAB-MT beams. Note that the possible difference in DM-RS symbol position and slot number shall be compensated for in the measured timing error. + +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.5.5 Test Requirement + +##### 6.6.5.5.1 IAB type 1-O + +The timing error between IAB-DU and IAB-MT shall not exceed minimum requirement plus measurement uncertainty defined in Table 4.1.2.2-1. + +##### 6.6.5.5.2 IAB type 2-O + +The timing error between IAB-DU and IAB-MT shall not exceed minimum requirement plus measurement uncertainty defined in Table 4.1.2.2-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 ITU-R SM.329 [10]. 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. + +The OTA out-of-band emissions requirement for the *IAB-MT type 1-O*, *IAB-DU type 1-O*, *IAB-DU type 1-O* and *IAB-DU type 2-O* transmitter is specified both in terms of Adjacent Channel Leakage power Ratio (ACLR) and operating band unwanted emissions (OBUE). OTA Unwanted emissions outside of this frequency range are limited by an OTA spurious emissions requirement. + +The maximum offset of the operating band unwanted emissions mask from the *operating band* edge is $\Delta f_{\text{OBUE}}$ . The value of $\Delta f_{\text{OBUE}}$ is defined in table 6.7.1-1 *IAB-DU type 1-O* and *type 2-O* and in table 6.7.1-2 *IAB-MT type 1-O* and *type 2-O* for NR *operating bands*. + +**Table 6.7.1-1: Maximum offset $\Delta f_{\text{OBUE}}$ outside the downlink *operating band* for IAB-DU** + +| IAB-DU type | Operating band characteristics | \Delta f_{\text{OBUE}} (MHz) | +|------------------------|------------------------------------------------------------------------------------|--------------------------------------------------| +| IAB-DU type 1-O | $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 | +| IAB-DU type 2-O | $F_{\text{DL,high}} - F_{\text{DL,low}} \leq 4000 \text{ MHz}$ | 1500 | + +**Table 6.7.1-2: Maximum offset $\Delta f_{\text{OBUE}}$ outside the uplink *operating band* for IAB-MT** + +| IAB-MT type | Operating band characteristics | \Delta f_{\text{OBUE}} (MHz) | +|------------------------|------------------------------------------------------------------------------------|--------------------------------------------------| +| IAB-MT type 1-O | $F_{\text{UL,high}} - F_{\text{UL,low}} < 100 \text{ MHz}$ | 10 | +| | $100 \text{ MHz} \leq F_{\text{UL,high}} - F_{\text{UL,low}} \leq 900 \text{ MHz}$ | 40 | +| IAB-MT type 2-O | $F_{\text{UL,high}} - F_{\text{UL,low}} \leq 4000 \text{ MHz}$ | 1500 | + +The unwanted emission requirements are applied per cell for all the configurations. 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. + +## 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 [13]. + +The value of $\beta/2$ shall be taken as 0.5%. + +The OTA occupied bandwidth requirement shall apply 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 + +The minimum requirement for *IAB-DU type 1-O* and *IAB-DU type 2-O* are in TS 38.174 [2], clause 9.7.2.2. + +The minimum requirement for *IAB-MT type 1-O* and *IAB-MT type 2-O* are in TS 38.174 [2], clause 9.7.2.3. + +### 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 + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +Directions to be tested: OTA coverage range reference direction (D.35). + +Beams to be tested: Declared beam with the highest intended EIRP for the narrowest intended beam corresponding to the smallest $\text{BeW}\theta$ , or for the narrowest intended beam corresponding to the smallest $\text{BeW}\phi$ (D.3, D.11). + +*Aggregated IAB channel bandwidth* positions to be tested for contiguous carrier aggregation: $M_{\text{BW Channel CA}}$ ; see clause 4.9.1. + +For a IAB declared to be capable of single carrier operation, start transmission according to the applicable test configuration in clause 4.8 using the corresponding test model IAB-DU-FR1-TM1.1 for *IAB-DU type 1-O*, IAB-MT-FR1-TM1.1 for *IAB-MT type 1-O*, IAB-DU-FR2-TM1.1 for *IAB-DU type 2-O* or IAB-MT-FR2-TM1.1 for *IAB-MT type 2-O* in clause 4.9.2 at manufacturers declared rated carrier EIRP ( $P_{\text{rated,c,EIRP}}$ , D.11). + +For a IAB declared to be capable of contiguous carrier aggregation operation, set the IAB to transmit according to IABDU-FR1-TM1.1 for *IAB-DU type 1-O*, IAB-MT-FR1-TM1.1 for *IAB-MT type 1-O*, IAB-DU-FR2-TM1.1 for *IAB-DU type 2-O* or IAB-MT-FR2-TM1.1 for *IAB-MT type 2-O* in clause 4.9.2 on all carriers configured using the applicable test configuration and corresponding power setting specified in clauses 4.7.2.3.1 and 4.8. + +For an IAB declared to be capable of Simultaneous transmission between IAB-DU and IAB-MT (D. IAB-3), set the IAB to transmit according to IABDU-FR1-TM1.1 for *IAB-DU type 1-O*, IAB-MT-FR1-TM1.1 for *IAB-MT type 1-O*, IAB-DU-FR2-TM1.1 for *IAB-DU type 2-O* or IAB-MT-FR2-TM1.1 for *IAB-MT type 2-O* in clause 4.9.2 using the applicable test configuration and corresponding power setting specified in clauses 4.7.2 and 4.8. + +#### 6.7.2.4.2 Procedure + +- 1) Place the IAB at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the IAB with the test system. +- 3) Orient the positioner (and IAB) in order that the direction to be tested aligns with the test antenna.. +- 4) Configure the beam peak direction of the IAB according to the declared beam direction pair. +- 5) Set the IAB to transmit signal. +- 6) 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 and table 6.7.2.4.2-2. The selected resolution bandwidth (RBW) filter of the analyser shall be 30 kHz or less. + +NOTE: The detection mode of the spectrum analyser 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 | IAB channel bandwidth
BW Channel (MHz) | | | | Aggregated IAB
channel bandwidth
BW Channel_CA (MHz) | +|--------------------------------------|------------------------------------------------------|----|----|------|-----------------------------------------------------------------------| +| | 10 | 15 | 20 | > 20 | > 20 | +| Span (MHz) | | | | | $2 \times BW_{Channel\_CA}$ | +| Minimum number of measurement points | 400 | | | | $\left\lceil \frac{2 \times BW_{Channel\_CA}}{100kHz} \right\rceil$ | + +**Table 6.7.2.4.2-2: Span and number of measurement points for OBW measurements for FR2** + +| Bandwidth | IAB channel bandwidth
BW Channel (MHz) | | | | Aggregated IAB
channel bandwidth
BW Channel_CA (MHz) | +|--------------------------------------|-----------------------------------------------------------------|-----|-----|-----|-----------------------------------------------------------------------| +| | 50 | 100 | 200 | 400 | > 50 | +| Span (MHz) | $2 \times BW_{Channel}$ | | | | $2 \times BW_{Channel\_CA}$ | +| Minimum number of measurement points | $\left\lceil \frac{2 \times BW_{Channel}}{200kHz} \right\rceil$ | | | | $\left\lceil \frac{2 \times BW_{Channel\_CA}}{200kHz} \right\rceil$ | + +- 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. 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 IAB-DU type 1-O and IAB-DU type 2-O + +The OTA occupied bandwidth for each NR carrier shall be less than the *IAB-DU channel bandwidth*. For intra-band contiguous CA, the OTA occupied bandwidth shall be less than or equal to the *Aggregated IAB-DU Channel Bandwidth*. + +### 6.7.2.5.2 IAB-MT type 1-O and IAB-MT type 2-O + +The OTA occupied bandwidth for each NR carrier shall be less than the *IAB-MT channel bandwidth*. For intra-band contiguous CA, the OTA occupied bandwidth shall be less than or equal to the *Aggregated IAB-MT Channel Bandwidth*. + +## 6.7.3 OTA Adjacent Channel Leakage Power Ratio (ACLR) + +### 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. + +The requirement shall be applied per RIB during the *transmitter ON period*. + +### 6.7.3.2 Minimum requirement + +The minimum requirement for *IAB-DU type 1-O* and *IAB-MT type 1-O* is in TS 38.174 [2], clause 9.7.3.2. + +The minimum requirement for *IAB-DU type 2-O* and *Wide Area IAB-MT type 2-O* is in TS 38.174 [2], clause 9.7.3.3. + +### 6.7.3.3 Test purpose + +To verify that the OTA adjacent channel leakage 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 + +Test environment: normal; see annex B.2. + +RF channels to be tested for single carrier: B and T; see clause 4.9.1. + +*IAB 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.9.1; +- $B_{\text{RFBW\_T'RFBW}}$ and $B'_{\text{RFBW\_T'RFBW}}$ in multi-band operation, see clause 4.9.1. + +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 I) as long as the required TRP level is achieved. + +#### 6.7.3.4.2 Procedure + +The following procedure for measuring TRP is based on the directional power measurements as described in annex I. An alternative method to measure TRP is to use a characterized and calibrated reverberation chamber if so follow steps 1, 3, 4, 6, 8, 9, 10, 11, 12 and 13. + +- 1) Place the IAB at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the IAB 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. +- 4) For single carrier operation, set the IAB to transmit according to the applicable test configuration in clause 4.8 using the corresponding test model(s) in clause 4.9.2 at manufacturers declared *rated carrier output power* ( $P_{\text{rated,c,TRP}}$ ). + - For a IAB declared to be capable of multi-carrier and/or CA operation use the applicable test signal configuration and corresponding power setting specified in clauses 4.7.2 and 4.8 using the corresponding test model(s) in clause 4.9.2 on all carriers configured. + +- For an IAB node declared to be capable of Simultaneous transmission between IAB-DU and IAB-MT (D. IAB-3), use the applicable test signal configuration and corresponding power setting in clauses 4.7.2 and 4.8 using the corresponding test model(s) in clause 4.9.2 for IAB-MT and IAB-DU. +- 5) Orient the positioner (and IAB) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see annex I). +- 6) Measure the absolute power of the assigned channel frequency and the (adjacent channel frequency). +- 7) Repeat step 5-6 for all directions in the appropriated TRP measurement grid needed for TRPEstimate (see annex I). +- 8) Calculate TRPEstimate for the absolute total radiated power of the wanted channel and the adjacent channel 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. + +- 10) Measure OTA ACLR for the frequency offsets both side of channel frequency as specified in table 6.7.3.5.1-1 for *IAB type 1-O* or table 6.7.3.5.2-1 for *IAB type 2-O* respectively. In multiple carrier case only offset frequencies below the lowest and above the highest carrier frequency used shall be measured. +- 11) 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*, if applicable. + - b) Measure OTA CACLR inside sub-block gap or *Inter RF Bandwidth gap*, if applicable. +- 12) Repeat the test with the channel set-up using IAB- FR1-TM1.2 defined in clause 4.9.2 in TS 38.176-1 [3] for *IAB type 1-O*. + +In addition, for *multi-band RIB*, the following steps shall apply: + +- 13) For *IAB type 1-O* and *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 requirements + +### 6.7.3.5.1 *IAB-DU type 1-O* and *IAB-MT type 1-O* + +For the OTA ACLR requirement either the OTA ACLR limits in tables 6.7.3.5.1-1/3 or the OTA ACLR absolute limits in table 6.7.3.5.1-2 shall apply, whichever is less stringent. The OTA CACLR limits in table 6.7.3.5.1-4 or the OTA CACLR absolute limits in table 6.7.3.5.1-5 shall apply, whichever is less stringent. + +The CACLR in a sub-block gap and 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 assumed filter for the adjacent channel frequency is defined in table 6.7.3.5.1-4 and the filters on the assigned channels are defined in table 6.7.3.5.1-6. + +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-1. + +**Table 6.7.3.5.1-1: IAB-DU and IAB-MT type 1-O ACLR limit** + +| IAB channel bandwidth of lowest/highest NR carrier transmitted BW_{\text{Channel}} (MHz) | IAB 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) | +|--------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------|-----------------------------------|-----------------------------------| +| 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 IAB 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-2. + +**Table 6.7.3.5.1-2: IAB-DU and IAB-MT type 1-O ACLR absolute limit** + +| IAB category / IAB class | OTA ACLR absolute limit | +|-------------------------------------------------------------|--------------------------------| +| Category A Wide Area IAB-DU and Category A Wide Area IAB-MT | -4 dBm/MHz | +| Category B Wide Area IAB-DU and Category B Wide Area IAB-MT | -6 dBm/MHz | +| Medium Range IAB-DU | -16 dBm/MHz | +| Local Area IAB-DU and Local Area IAB-MT | -23 dBm/MHz | + +NOTE 1: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. + +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-3. + +**Table 6.7.3.5.1-3: IAB-DU and IAB-MT type 1-O ACLR limit in non-contiguous spectrum or multiple bands** + +| IAB-DU and IAB-MT 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) | IAB-DU and IAB-MT 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) | +|---------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|--------------------------------|--------------------------------| +| 10, 15, 20 | $W_{gap} \geq 15$ (Note 3) | 2.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 44 dB | 43.8 dB | +| | $W_{gap} \geq 45$ (Note 4) | | | | | | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $W_{gap} \geq 20$ (Note 3)
$W_{gap} \geq 50$ (Note 4) | 7.5 MHz | 5 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 44 dB | 43.8 dB | +| | $W_{gap} \geq 60$ (Note 4)
$W_{gap} \geq 30$ (Note 3) | 10 MHz | 20 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 44 dB | 43.8 dB | +| | $W_{gap} \geq 80$ (Note 4)
$W_{gap} \geq 50$ (Note 3) | 30 MHz | 20 MHz NR (Note 2) | Square ( $BW_{Config}$ ) | 44 dB | 43.8 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 IAB channel bandwidth of the NR carrier transmitted at the other edge of the gap is 10, 15, 20 MHz. +NOTE 4: Applicable in case the IAB 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. + +**Table 6.7.3.5.1-4: IAB-DU and IAB-MT type 1-O CACLR limit** + +| IAB-DU and IAB-MT channel bandwidth of lowest/highest NR carrier transmitted BWchannel (MHz) | Sub-block or Inter RF Bandwidth gap size (Wgap) where the limit applies (MHz) | IAB-DU and IAB-MT 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 CACLR limit (0-3 GHz) | OTA CACLR limit (3-6 GHz) | +|----------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------|----------------------------------|----------------------------------| +| 10, 15, 20 | 5 ≤ W gap < 15 (Note 3)
5 ≤ W gap < 45 (Note 4) | 2.5 MHz | 5 MHz NR (Note 2) | Square (BW Config ) | 44 dB | 43.8 dB | +| | 10 < W gap < 20 (Note 3)
10 ≤ W gap < 50 (Note 4) | 7.5 MHz | 5 MHz NR (Note 2) | Square (BW Config ) | 44 dB | 43.8 dB | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 20 ≤ W gap < 60 (Note 4)
20 ≤ W gap < 30 (Note 3) | 10 MHz | 20 MHz NR (Note 2) | Square (BW Config ) | 44 dB | 43.8 dB | +| | 40 < W gap < 80 (Note 4)
40 ≤ W gap < 50 (Note 3) | 30 MHz | 20 MHz NR (Note 2) | Square (BW Config ) | 44 dB | 43.8 dB | + +NOTE 1: BWConfig is the transmission bandwidth configuration of the assumed adjacent channel carrier. +NOTE 2: With SCS that provides largest transmission bandwidth configuration (BWConfig). +NOTE 3: Applicable in case the IAB channel bandwidth of the NR carrier transmitted at the other edge of the gap is 10, 15, 20 MHz. +NOTE 4: Applicable in case the IAB 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. + +The absolute total power measurement shall not exceed the OTA CACLR absolute limit specified in table 6.7.3.5.1-5. + +**Table 6.7.3.5.1-5: IAB-DU and IAB-MT type 1-O CACLR absolute limit** + +| IAB category / IAB class | OTA CACLR absolute limit | +|-------------------------------------------------------------|---------------------------------| +| Category A Wide Area IAB-DU and Category A Wide Area IAB-MT | -4 dBm/MHz | +| Category B Wide Area IAB-DU and Category B Wide Area IAB-MT | -6 dBm/MHz | +| Medium Range IAB-DU | -16 dBm/MHz | +| Local Area IAB-DU and Local Area IAB-MT | -23 dBm/MHz | + +NOTE 1: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. + +**Table 6.7.3.5.1-6: 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 | +|-------------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| NR | NR of same BW with SCS that provides largest transmission bandwidth configuration | + +## 6.7.3.5.2 IAB-DU type 2-O and Wide Area IAB-MT type 2-O + +The OTA ACLR absolute limit in table 6.7.3.5.2-2 or the OTA ACLR limit in table 6.7.3.5.2-1/3, whichever is less stringent, shall apply. The OTA CACLR absolute limit in table 6.7.3.5.2-5 or the OTA CACLR limit in table 6.7.3.5.2-4, whichever is less stringent, shall apply. + +For a *RIB* operating in multi-carrier or contiguous CA, the OTA ACLR requirements in table 6.7.3.5.2-1 shall apply to *IAB-DU* and *IAB-MT channel bandwidths* of the outermost carrier for the frequency ranges defined in the table. For a *RIB* operating in *non-contiguous spectrum*, the OTA ACLR requirement in table 6.7.3.5.2-3 shall apply in *sub-block gaps* for the frequency ranges defined in the table, while the OTA CACLR requirement in table 6.7.3.5.2-4 shall apply in *sub-block gaps* for the frequency ranges defined in the table. + +The CACLR in a *sub-block 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*, and +- the filtered mean power centred on a frequency channel adjacent to one of the respective *sub-block* edges. + +The assumed filter for the adjacent channel frequency is defined in table 6.7.3.5.2-4 and the filters on the assigned channels are defined in table 6.7.3.5.2-6. + +For operation in *non-contiguous spectrum*, the CACLR for NR carriers located on either side of the *sub-block gap* shall be higher than the value specified in table 6.7.3.5.2-4. + +**Table 6.7.3.5.2-1: IAB-DU type 2-O and Wide area IAB-MT type 2-O ACLR limit** + +| IAB-DU and IAB-MT channel bandwidth of lowest/highest carrier transmitted $BW_{\text{Channel}}$ (MHz) | IAB-DU and IAB-MT adjacent channel centre frequency offset below the lowest or above the highest carrier centre frequency transmitted | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit (dB) | +|-------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| 50, 100, 200, 400 | $BW_{\text{Channel}}$ | NR of same BW (Note 2) | Square ( $BW_{\text{Config}}$ ) | 25.7 for IAB-DU (Note 3)
23.4 for IAB-DU (Note 4)
25.2 for IAB-MT (Note 3)
23.1 for IAB-MT (Note 4) | + +NOTE 1: $BW_{\text{Channel}}$ and $BW_{\text{Config}}$ are the *IAB-DU* and *IAB-MT channel bandwidth* and *transmission bandwidth configuration* of the lowest/highest carrier transmitted on the assigned channel frequency. + +NOTE 2: With SCS that provides largest *transmission bandwidth configuration* ( $BW_{\text{Config}}$ ). + +NOTE 3: Applicable to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz + +NOTE 4: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz + +**Table 6.7.3.5.2-2: IAB-DU type 2-O and Wide area IAB-MT type 2-O ACLR absolute limit** + +| IAB-DU and IAB-MT class | ACLR absolute limit | +|-------------------------|--------------------------------------------------| +| Wide area IAB-DU | -10.3 dBm/MHz | +| Wide Area IAB-MT | -10.1 dBm/MHz (Note 1)
-10.0 dBm/MHz (Note 2) | +| Medium range IAB-DU | -17.3 dBm/MHz | +| Local area IAB-DU | -17.3 dBm/MHz | + +NOTE 1: Applicable to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz + +NOTE 2: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz + +**Table 6.7.3.5.2-3: IAB DU type 2-O and Wide Area IAB-MT type 2-O ACLR limit in non-contiguous spectrum** + +| IAB-DU and IAB-MT channel bandwidth of lowest/highest carrier transmitted (MHz) | Sub-block gap size ( $W_{\text{gap}}$ ) where the limit applies (MHz) | IAB-DU and IAB-MT 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 (dB) | +|---------------------------------------------------------------------------------|--------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| 50, 100 | $W_{\text{gap}} \geq 100$ (Note 5)
$W_{\text{gap}} \geq 250$ (Note 6) | 25 MHz | 50 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 25.7 for IAB-DU (Note 3)
23.4 for IAB-DU (Note 4)
25.2 for IAB-MT (Note 3)
23.1 for IAB-MT (Note 4) | +| 200, 400 | $W_{\text{gap}} \geq 400$ (Note 6)
$W_{\text{gap}} \geq 250$ (Note 5) | 100 MHz | 200 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 25.7 for IAB-DU (Note 3)
23.4 for IAB-DU (Note 4)
25.2 for IAB-MT (Note 3)
23.1 for IAB-MT (Note 4) | + +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 to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz. + +NOTE 4: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz. + +NOTE 5: Applicable in case the *IAB-DU or IAB-MT channel bandwidth* of the NR carrier transmitted at the other edge of the gap is 50 or 100 MHz. + +NOTE 6: Applicable in case the *IAB-DU or IAB-MT channel bandwidth* of the NR carrier transmitted at the other edge of the gap is 200 or 400 MHz. + +**Table 6.7.3.5.2-4: IAB DU type 2-O and Wide Area IAB-MT type 2-O CACLR limit in non-contiguous spectrum** + +| IAB-DU and IAB-MT channel bandwidth of lowest/highest carrier transmitted (MHz) | Sub-block gap size ( $W_{\text{gap}}$ ) where the limit applies (MHz) | IAB-DU and IAB-MT 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 | CACLR limit (dB) | +|---------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| 50, 100 | $50 \leq W_{\text{gap}} < 100$ (Note 5)
$50 \leq W_{\text{gap}} < 250$ (Note 6) | 25 MHz | 50 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 25.7 for IAB-DU (Note 3)
23.4 for IAB-DU (Note 4)
25.2 for IAB-MT (Note 3)
23.1 for IAB-MT (Note 4) | +| 200, 400 | $200 \leq W_{\text{gap}} < 400$ (Note 6)
$200 \leq W_{\text{gap}} < 250$ (Note 5) | 100 MHz | 200 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 25.7 for IAB-DU (Note 3)
23.4 for IAB-DU (Note 4)
25.2 for IAB-MT (Note 3)
23.1 for IAB-MT (Note 4) | + +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 to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz. +NOTE 4: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz. +NOTE 5: Applicable in case the IAB-DU or IAB-MT channel bandwidth of the NR carrier transmitted at the other edge of the gap is 50 or 100 MHz. +NOTE 6: Applicable in case the IAB-DU or IAB-MT channel bandwidth of the NR carrier transmitted at the other edge of the gap is 200 or 400 MHz. + +**Table 6.7.3.5.2-5: IAB-DU type 2-O and Wide area IAB-MT type 2-O CACLR absolute limit** + +| IAB-DU and IAB-MT class | CACLR absolute limit | +|-------------------------|--------------------------------------------------| +| Wide area IAB-DU | -10.3 dBm/MHz | +| Wide area IAB-MT | -10.1 dBm/MHz (Note 1)
-10.0 dBm/MHz (Note 2) | +| Medium range IAB-DU | -17.3 dBm/MHz | +| Local area IAB-DU | -17.3 dBm/MHz | + +NOTE 1: Applicable to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz +NOTE 2: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz + +**Table 6.7.3.5.2-6: Filter parameters for the assigned channel** + +| RAT of the carrier adjacent to the sub-block gap | Filter on the assigned channel frequency and corresponding filter bandwidth | +|--------------------------------------------------|-----------------------------------------------------------------------------------| +| NR | NR of same BW with SCS that provides largest transmission bandwidth configuration | + +### 6.7.3.5.3 Local Area IAB-MT type 2-O + +The OTA ACLR absolute limit in table 6.7.3.5.3-2 or the ACLR limit in table 6.7.3.5.3-1/3, whichever is less stringent, shall apply. The OTA CACLR absolute limit in table 6.7.3.5.3-5 or the CACLR limit in table 6.7.3.5.3-4, whichever is less stringent, shall apply. + +Requirements specified for Local Area IAB-DU type 2-O in clause 6.7.3.5.3 shall apply to Local Area IAB-MT type 2-O during transmission in DL timeslot. + +For a RIB operating in multi-carrier or contiguous CA, the OTA ACLR requirements in table 6.7.3.5.3-1 shall apply to IAB-MT channel bandwidths of the outermost carrier for the frequency ranges defined in the table. For a RIB + +operating in *non-contiguous spectrum*, the OTA ACLR requirement in table 6.7.3.5.3-3 shall apply in *sub-block gaps* for the frequency ranges defined in the table, while the OTA CACLR requirement in table 6.7.3.5.3-4 shall apply in *sub-block gaps* for the frequency ranges defined in the table. + +The CACLR in a *sub-block 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*, and +- the filtered mean power centred on a frequency channel adjacent to one of the respective *sub-block* edges. + +The assumed filter for the adjacent channel frequency is defined in table 6.7.3.5.3-4 and the filters on the assigned channels are defined in table 6.7.3.5.3-6. + +For operation in *non-contiguous spectrum*, the CACLR for NR carriers located on either side of the *sub-block gap* shall be higher than the value specified in table 6.7.3.5.3-4. + +**Table 6.7.3.3.5-1: Local Area IAB-MT type 2-O ACLR limit** + +| IAB-MT channel bandwidth of lowest/highest carrier transmitted $BW_{\text{Channel}}$ (MHz) | IAB-MT adjacent channel centre frequency offset below the lowest or above the highest carrier centre frequency transmitted | Assumed adjacent channel carrier | Filter on the adjacent channel frequency and corresponding filter bandwidth | ACLR limit (dB) | +|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|--------------------------------| +| 50, 100, 200, 400 | $BW_{\text{Channel}}$ | NR of same BW (Note 2) | Square ( $BW_{\text{Config}}$ ) | 21.2 (Note 3)
21.1 (Note 4) | + +NOTE 1: $BW_{\text{Channel}}$ and $BW_{\text{Config}}$ are the IAB-MT channel bandwidth and transmission bandwidth configuration of the lowest/highest carrier transmitted on the assigned channel frequency. + +NOTE 2: With SCS that provides largest transmission bandwidth configuration ( $BW_{\text{Config}}$ ). + +NOTE 3: Applicable to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz + +NOTE 4: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz + +**Table 6.7.3.5.3-2: Local Area IAB-MT type 2-O ACLR absolute limit** + +| IAB-MT class | ACLR absolute limit | +|-------------------|--------------------------------------------------| +| Local area IAB-MT | -17.1 dBm/MHz (Note 1)
-17.0 dBm/MHz (Note 2) | + +NOTE 1: Applicable to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz + +NOTE 2: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz + +**Table 6.7.3.5.3-3: Local Area IAB-MT type 2-O ACLR limit in non-contiguous spectrum** + +| IAB-MT channel bandwidth of lowest/highest carrier transmitted (MHz) | Sub-block gap size ( $W_{\text{gap}}$ ) where the limit applies (MHz) | IAB-MT 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 | +|----------------------------------------------------------------------|--------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|--------------------------------| +| 50, 100 | $W_{\text{gap}} \geq 100$ (Note 4)
$W_{\text{gap}} \geq 250$ (Note 5) | 25 MHz | 50 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 21.2 (Note 3)
21.1 (Note 6) | +| 200, 400 | $W_{\text{gap}} \geq 400$ (Note 5)
$W_{\text{gap}} \geq 250$ (Note 4) | 100 MHz | 200 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 21.2 (Note 3)
21.1 (Note 6) | + +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 to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz. + +NOTE 4: Applicable in case the *IAB-MT channel bandwidth* of the NR carrier transmitted at the other edge of the gap is 50 or 100 MHz.NOTE 5: Applicable in case the *IAB-MT channel bandwidth* of the NR carrier transmitted at the other edge of the gap is 200 or 400 MHz. + +NOTE 6: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz. + +**Table 6.7.3.5.3-4: Local Area IAB-MT type 2-O CACLR limit in non-contiguous spectrum** + +| IAB-MT channel bandwidth of lowest/highest carrier transmitted (MHz) | Sub-block gap size ( $W_{\text{gap}}$ ) where the limit applies (MHz) | IAB-MT 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 | CACLR limit | +|----------------------------------------------------------------------|--------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|----------------------------------|-----------------------------------------------------------------------------|--------------------------------| +| 50, 100 | $50 \leq W_{\text{gap}} < 100$ (Note 4)
$50 \leq W_{\text{gap}} < 250$ (Note 5) | 25 MHz | 50 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 21.2 (Note 3)
21.1 (Note 6) | +| 200, 400 | $200 \leq W_{\text{gap}} < 400$ (Note 5)
$200 \leq W_{\text{gap}} < 250$ (Note 4) | 100 MHz | 200 MHz NR (Note 2) | Square ( $BW_{\text{Config}}$ ) | 21.2 (Note 3)
21.1 (Note 6) | + +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 to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz. + +NOTE 4: Applicable in case the *IAB-MT channel bandwidth* of the NR carrier transmitted at the other edge of the gap is 50 or 100 MHz.NOTE 5: Applicable in case the *IAB-MT channel bandwidth* of the NR carrier transmitted at the other edge of the gap is 200 or 400 MHz.**Table 6.7.3.5.3-5: Local Area IAB-MT type 2-O CACLR absolute limit** + +| IAB-MT class | CACLR absolute limit | +|-------------------|--------------------------------------------------| +| Local area IAB-MT | -17.1 dBm/MHz (Note 1)
-17.0 dBm/MHz (Note 2) | + +NOTE 1: Applicable to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz + +NOTE 2: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz + +**Table 6.7.3.5.3-6: Filter parameters for the assigned channel** + +| RAT of the carrier adjacent to the sub-block gap | Filter on the assigned channel frequency and corresponding filter bandwidth | +|--------------------------------------------------|------------------------------------------------------------------------------------------| +| NR | NR of same BW with SCS that provides largest transmission bandwidth configuration | + +## 6.7.4 OTA operating band unwanted emissions + +### 6.7.4.1 Definition and applicability + +The OTA limits for operating band unwanted emissions are specified as TRP per RIB, unless otherwise stated. + +#### 6.7.4.1.1 IAB-DU type 1-O + +For *IAB-DU type 1-O*, for a *RIB* operating in multi-carrier or contiguous CA, the requirements apply to *IAB-DU channel bandwidths* of the outermost carrier. In addition, for a *RIB* operating in non-contiguous spectrum, the requirements shall apply inside any sub-block gap. In addition, for a *multi-band RIB*, the requirements shall apply inside any Inter RF Bandwidth gap. + +#### 6.7.4.1.2 IAB-MT type 1-O + +For *IAB-MT type 1-O*, for a *RIB* operating in multi-carrier or contiguous CA, the requirements apply to *IAB-MT channel bandwidths* of the outermost carrier. In addition, for a *RIB* operating in non-contiguous spectrum, the requirements shall apply inside any sub-block gap. In addition, for a *multi-band RIB*, the requirements shall apply inside any Inter RF Bandwidth gap. + +#### 6.7.4.1.3 IAB-DU type 2-O and IAB-MT type 2-O + +For *IAB-DU type 2-O* and *IAB-MT type 2-O*, for a *RIB* operating in multi-carrier or contiguous CA, the requirements apply to the frequencies ( $\Delta f_{\text{OBUE}}$ ) starting from the edge of the *contiguous transmission bandwidth*. In addition, for a *RIB* operating in non-contiguous spectrum, the requirements apply inside any sub-block gap. + +### 6.7.4.2 Minimum requirement + +The minimum requirement for *IAB-DU type 1-O* is defined in TS 38.174 [2], clause 9.7.4.2. + +The minimum requirement for *IAB-MT type 1-O* is defined in TS 38.174 [2], clause 9.7.4.3. + +The minimum requirement for *IAB-DU type 2-O* and *IAB-MT type 2-O* are defined in TS 38.174 [2], clause 9.7.4.5. + +### 6.7.4.3 Test purpose + +This test measures the emissions of the IAB-Node, close to the assigned channel bandwidth of the wanted signal, while the IAB-Node is in operation. + +### 6.7.4.4 Method of test + +#### 6.7.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.9.1. + +*IAB 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.9.1; +- $B_{\text{RFBW\_T}}$ and $B'_{\text{RFBW\_T}}$ in multi-band operation, see clause 4.9.1. + +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 I) as long as the required TRP level is achieved. + +#### 6.7.4.4.2 Procedure + +The following procedure for measuring TRP is based on the directional power measurements as described in annex I. 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. + +- 1) Place the IAB-Node at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the IAB-Node with the test system. +- 3) The measurement devices characteristics shall be: + - measurement filter bandwidth: defined in clause 6.7.4.5. + - detection mode: true RMS voltage or true power averaging. +- 4) For single carrier operation, set the IAB-Node to transmit according to the applicable test configuration in clause 4.8 using the corresponding test model(s) in clause 4.9.2 at manufacturers declared *rated carrier output power* ( $P_{\text{rated,c,TRP}}$ ). + - For a IAB 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.7.2 and 4.8 using the corresponding test model(s) in clause 4.9.2 on all carriers configured. + - For an IAB node declared to be capable of Simultaneous transmission between IAB-DU and IAB-MT (D.IAB-3), use the applicable test signal configuration and corresponding power setting in clauses 4.7.2 and 4.8 using the corresponding test model(s) in clause 4.9.2 for IAB-DU and IAB-MT. +- 5) Orient the positioner (and IAB) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see annex I). +- 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 5-6 for all directions in the appropriated TRP measurement grid needed for $\text{TRP}_{\text{Estimate}}$ (see annex I). +- 8) Calculate $\text{TRP}_{\text{Estimate}}$ using the measurements made in step 6. +- 9) For *IAB type 1-O* and *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 requirements + +##### 6.7.4.5.1 IAB type 1-O + +The emission measurement result shall not exceed the maximum levels specified in tables 6.7.4.5.1.1-1 to 6.7.4.5.1.5-3, 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{offsetmax}}$ 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{offsetmax}}$ 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 * \Delta f_{\text{OBUE}}$ , emissions shall not exceed the cumulative sum of the test requirements specified at the *IAB RF Bandwidth edges* on each side of the *Inter RF Bandwidth gap*. The test requirement for *IAB RF Bandwidth edge* is specified in the tables 6.7.4.5.1.1-1 to 6.7.4.5.1.5-3 below, where in this case: + +- $\Delta f$ is the separation between the *IAB RF Bandwidth edge* frequency and the nominal -3 dB point of the measuring filter closest to the *IAB RF Bandwidth edge*. + +- $f\_offset$ is the separation between the *IAB 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 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 * \Delta f_{OBUE}$ , $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 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. + +For a multicarrier *single-band RIB* or a *single-band 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 *single-band 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 test requirement for each sub block is specified in the tables 6.7.4.5.1.1-1 to 6.7.4.5.1.5-3 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. + +#### 6.7.4.5.1.1 Wide Area IAB-DU and Wide Area IAB-MT (Category A) + +For operating in Bands n41, n77, n78, n79, emissions shall not exceed the maximum levels specified in tables 6.7.4.5.1.1-1 to 6.7.4.5.1.1-3: + +**Table 6.7.4.5.1.1-1: Wide Area IAB-DU and Wide Area IAB-MT operating band unwanted emission limits +(1 GHz < NR 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 (Note 1, 2, 4) | 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 3) | 100 kHz | + +NOTE 1: For a IAB 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 -4 dBm/100 kHz. + +NOTE 2: For a *multi-band RIB* 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}$ . + +NOTE 4: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. + +**Table 6.7.4.5.1.1-2: Wide Area IAB-DU and Wide Area IAB-MT operating band unwanted emission limits +(3 GHz < NR bands ≤ 4.2 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 1, 2, 4) | 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 3) | 1MHz | + +NOTE 1: For a IAB 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 -4 dBm/1 MHz. + +NOTE 2: For a *multi-band R/B* with Inter RF Bandwidth gap $< 2 * \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, 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}$ . + +NOTE 4: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. + +**Table 6.7.4.5.1.1-3: Wide Area IAB-DU and Wide Area IAB-MT operating band unwanted emission limits +(4.2 GHz < NR bands ≤ 6 GHz) for Category A** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 1, 2, 4) | 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 3) | 1MHz | + +NOTE 1: For a IAB 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 -4 dBm/1 MHz. + +NOTE 2: For a *multi-band R/B* with Inter RF Bandwidth gap $< 2 * \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, 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}$ . + +NOTE 4: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. + +NOTE 5: Void + +#### 6.7.4.5.1.2 Wide Area IAB-DU and Wide Area IAB-MT (Category B) + +For IAB-DU and IAB-MT operating in Bands n41, n77, n78, n79 for Category B emissions shall not exceed the maximum levels specified in tables 6.7.4.5.1.2-1 to 6.7.4.5.1.2-3: + +**Table 6.7.4.5.1.2-1: Wide Area IAB-DU and IAB-MT operating band unwanted emission limits +(1 GHz < NR 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 (Note 1, 2, 4) | 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 (3) | 1MHz | + +NOTE 1: For a IAB 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 -6 dBm/1 MHz. + +NOTE 2: For a *multi-band RIB* with Inter RF Bandwidth gap $< 2 * \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, 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}$ . + +NOTE 4: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. + +**Table 6.7.4.5.1.2-2: Wide Area IAB-DU and IAB-MT operating band unwanted emission limits +(1 GHz < NR 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 (Note 1, 2, 4) | 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 3) | 1MHz | + +NOTE 1: For a IAB 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 -6 dBm/1 MHz. + +NOTE 2: For a *multi-band RIB* with Inter RF Bandwidth gap $< 2 * \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, 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}$ . + +NOTE 4: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. + +**Table 6.7.4.5.1.2-2: Wide Area IAB-DU and IAB-MT operating band unwanted emission limits +(4.2 GHz < NR bands ≤ 6 GHz) for Category B** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 1, 2, 4) | 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 3) | 1MHz | + +NOTE 1: For a IAB 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 -6 dBm/1 MHz. + +NOTE 2: For a *multi-band RIB* with Inter RF Bandwidth gap $< 2 * \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, 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}$ . + +NOTE 4: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. + +#### 6.7.4.6.1 Medium Range IAB-DU (Category A and B) + +For Medium Range IAB-DU in NR bands $\leq 3 \text{ GHz}$ , emissions shall not exceed the maximum levels specified in tables 6.7.4.6.1-1 and 6.7.4.6.1-4. + +For Medium Range IAB-DU in $3 \text{ GHz} < \text{NR bands} \leq 4.2 \text{ GHz}$ , emissions shall not exceed the maximum levels specified in tables 6.7.4.6.1-2 and 6.7.4.6.1-5. + +For Medium Range IAB-DU in $4.2 \text{ GHz} < \text{NR bands} \leq 6 \text{ GHz}$ , emissions shall not exceed the maximum levels specified in tables 6.7.4.6.1-3 and 6.7.4.6.1-6. + +For the tables in this clause for *IAB-DU type 1-O* $P_{\text{rated},x} = P_{\text{rated},c,\text{TRP}} - 9 \text{ dB}$ . + +**Table 6.7.4.6.1-1: Medium Range IAB-DU operating band unwanted emission limits, $31 < P_{\text{rated},x} \leq 38 \text{ dBm}$ (NR 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 (Note 1, 2, 4) | 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,\text{TRP}} - 51.2 \text{ dB} - \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})$ | - 58.2 dB | 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,\text{TRP}} - 60 \text{ dB}, -16 \text{ dBm})$ (Note 3) | 100 kHz | + +NOTE 1: For a IAB 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,\text{TRP}} - 60 \text{ dB}, -16 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band RIB* with Inter RF Bandwidth gap $< 2 * \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_{\max} < 10 \text{ MHz}$ . + +NOTE 4: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. + +**Table 6.7.4.6.1-2: Medium Range IAB-DU operating band unwanted emission limits, $31 < P_{\text{rated,x}} \leq 38$ dBm (3 GHz < NR bands $\leq 4.2$ GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 1, 2, 4) | 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} - \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_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | $P_{\text{rated,c,TRP}} - 58 \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 3) | 100 kHz | + +NOTE 1: For a IAB 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,TRP}} - 60 \text{ dB}, -16 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band RIB* with Inter RF Bandwidth gap $< 2 * \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}$ . + +NOTE 4: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. + +**Table 6.7.4.6.1-3: Medium Range IAB-DU operating band unwanted emission limits, $31 < P_{\text{rated,x}} \leq 38$ dBm (3 GHz < NR bands $\leq 4.2$ GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 1, 2, 4) | 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} - \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_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | $P_{\text{rated,c,TRP}} - 58 \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 3) | 100 kHz | + +NOTE 1: For a IAB 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,TRP}} - 60 \text{ dB}, -16 \text{ dBm})/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band RIB* with Inter RF Bandwidth gap $< 2 * \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}$ . + +NOTE 4: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. + +**Table 6.7.4.6.1-4: Medium Range IAB-DU operating band unwanted emission limits, $P_{\text{rated,x}} \leq 31$ dBm (NR 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, 4) | Measurement bandwidth | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $- 11.2 \text{ dB} - \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_{\text{max}})$ | $5.05 \text{ MHz} \leq f\_offset < \min(10.05 \text{ MHz}, f\_offset_{\text{max}})$ | $-18.2 \text{ 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 \text{ dBm}$ (Note 3) | 100 kHz | + +NOTE 1: For a IAB 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 $-20 \text{ dBm}/100 \text{ kHz}$ . + +NOTE 2: For a *multi-band RIB* with Inter RF Bandwidth gap $< 2 * \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}$ . + +NOTE 4: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. + +**Table 6.7.4.6.1-5: Medium Range IAB-DU operating band unwanted emission limits, $P_{\text{rated,x}} \leq 31$ dBm (3 GHz < NR bands $\leq 4.2$ GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 1, 2, 4) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-11\text{dB} - \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})$ | -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 3) | 100 kHz | + +NOTE 1: For a IAB 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 -20 dBm/100kHz. + +NOTE 2: For a *multi-band RIB* with Inter RF Bandwidth gap $< 2 * \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_{\max} < 10 \text{ MHz}$ . + +NOTE 4: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. + +**Table 6.7.4.6.1-6: Medium Range IAB-DU operating band unwanted emission limits, $P_{\text{rated,x}} \leq 31$ dBm (4.2 GHz < NR bands $\leq 6$ GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 1, 2, 4) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-11\text{dB} - \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})$ | -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 3) | 100 kHz | + +NOTE 1: For a IAB 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 -20 dBm/100kHz. + +NOTE 2: For a *multi-band RIB* with Inter RF Bandwidth gap $< 2 * \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_{\max} < 10 \text{ MHz}$ . + +NOTE 4: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. + +#### 6.7.4.6.2 Local Area IAB-DU and Local Area IAB-MT (Category A and B) + +For Local Area IAB-DU and Local Area IAB-MT in NR bands $\leq 3$ GHz, emissions shall not exceed the maximum levels specified in table 6.7.4.6.2-1. + +For Local Area IAB-DU and Local Area IAB-MT in 3 GHz < NR bands $\leq 4.2$ GHz, emissions shall not exceed the maximum levels specified in table 6.7.4.6.2-2. + +For Local Area IAB-DU and Local Area IAB-MT in 4.2 GHz < NR bands $\leq 6$ GHz, emissions shall not exceed the maximum levels specified in table 6.7.4.6.2-3. + +**Table 6.7.4.6.2-1: Local Area IAB-DU and Local Area IAB-MT operating band unwanted emission limits (NR 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, 4) | 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{dB} - \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})$ | -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 3) | 100 kHz | + +NOTE 1: For a IAB 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 -28 dBm/100kHz. + +NOTE 2: For a *multi-band RIB* with Inter RF Bandwidth gap $< 2 * \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_{\max} < 10 \text{ MHz}$ . + +NOTE 4: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. + +NOTE 5: Void + +**Table 6.7.4.6.2-2: Local Area IAB-DU and Local Area IAB-MT operating band unwanted emission limits ( $3 \text{ GHz} < \text{NR bands} \leq 4.2 \text{ GHz}$ )** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 1, 2, 4) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-19\text{dB} - \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})$ | -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 3) | 100 kHz | + +NOTE 1: For a IAB 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 -28 dBm/100kHz. + +NOTE 2: For a *multi-band RIB* with Inter RF Bandwidth gap $< 2 * \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_{\max} < 10 \text{ MHz}$ . + +NOTE 4: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. + +**Table 6.7.4.6.2-3: Local Area IAB-DU and Local Area IAB-MT operating band unwanted emission limits (4.2 GHz < NR bands ≤ 6 GHz)** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement (Note 1, 2, 4) | Measurement bandwidth | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 5 \text{ MHz}$ | $0.05 \text{ MHz} \leq f\_offset < 5.05 \text{ MHz}$ | $-19 \text{ dB} - \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})$ | -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 3) | 100 kHz | + +NOTE 1: For a IAB 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 -28 dBm/100kHz. + +NOTE 2: For a *multi-band RIB* with Inter RF Bandwidth gap $< 2 * \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_{\max} < 10 \text{ MHz}$ . + +NOTE 4: The test requirement is derived from the basic limit a scaling factor of 9 dB and any applicable TT. + +### 6.7.4.6.3 Additional requirements + +#### 6.7.4.6.3.1 Limits in FCC Title 47 + +In addition to the requirements in clauses 6.6.4.2.1, 6.6.4.2.2, 6.6.4.2.3 and 6.6.4.2.4 in TS 38.174 [2], the IAB-DU and IAB-MT may have to comply with the applicable emission limits established by FCC Title 47 [14], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer. + +#### 6.7.4.6.4 IAB type 2-O + +The requirements of either clause 6.7.4.6.4.1 (Category A limits) or clause 6.7.4.6.4.1 (Category B limits) shall apply. The application of either Category A or Category B limits shall be the same as for General OTA transmitter spurious emissions requirements (*IAB type 2-O*) in clause 6.7.5.2.5.2. In addition, the limits in clause 6.7.4.5.2.4 may also apply. The emission measurement result shall not exceed the maximum levels specified in the tables below, where: + +- $\Delta f$ is the separation between the *contiguous transmission bandwidth* edge frequency and the nominal -3dB point of the measuring filter closest to the *contiguous transmission bandwidth* edge. +- $f\_offset$ is the separation between the *contiguous transmission 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*, where $\Delta f_{\text{OBUE}}$ is defined in table 6.7.1-1. + +In addition, 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 test requirement for each sub-block is specified in the clauses 6.7.4.5.2.2 and 6.7.4.5.2.3 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. + +#### 6.7.4.6.4.1 OTA operating band unwanted emission limits (Category A) + +The power of unwanted emission of IAB-DU shall not exceed the limits in table 6.7.4.6.4.1-1 or 6.7.4.6.4.1-2. The power of unwanted emission of IAB-MT shall not exceed the limits in table 6.7.4.6.4.1-3 or 6.7.4.6.4.1-4. + +**Table 6.7.4.6.4.1-1: OBUE limits applicable for IAB-DU in the frequency range 24.25 – 33.4 GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test limit | Measurement bandwidth | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.1 \cdot \text{BW}_{\text{contiguous}}$ | $0.5 \text{ MHz} \leq f\_offset < 0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz}$ | $\text{Min}(-2.3 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 32.3 \text{ dB}, -9.3 \text{ dBm}))$ | 1 MHz | +| $0.1 \cdot \text{BW}_{\text{contiguous}} \leq \Delta f < \Delta f_{\text{max}}$ | $0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 43 \text{ dB}, -20 \text{ dBm}))$ | 1 MHz | +| NOTE: For non-contiguous spectrum operation within any operating band the 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. | | | | + +**Table 6.7.4.6.4.1-2: OBUE limits applicable for IAB-DU in the frequency range 37 GHz – 52.6 GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test limit | Measurement bandwidth | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.1 \cdot \text{BW}_{\text{contiguous}}$ | $0.5 \text{ MHz} \leq f\_offset < 0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz}$ | $\text{Min}(-2.3 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 30.3 \text{ dB}, -9.3 \text{ dBm}))$ | 1 MHz | +| $0.1 \cdot \text{BW}_{\text{contiguous}} \leq \Delta f < \Delta f_{\text{max}}$ | $0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 41 \text{ dB}, -20 \text{ dBm}))$ | 1 MHz | +| NOTE: For non-contiguous spectrum operation within any operating band the 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. | | | | + +**Table 6.7.4.6.4.1-3: OBUE limits applicable for IAB-MT in the frequency range 24.25 – 33.4 GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test limit | Measurement bandwidth | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.1 \cdot \text{BW}_{\text{contiguous}}$ | $0.5 \text{ MHz} \leq f\_offset < 0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz}$ | $\text{Min}(-2.1 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 32.1 \text{ dB}, -9.1 \text{ dBm}))$ | 1 MHz | +| $0.1 \cdot \text{BW}_{\text{contiguous}} \leq \Delta f < \Delta f_{\text{max}}$ | $0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 43 \text{ dB}, -20 \text{ dBm}))$ | 1 MHz | +| NOTE: For non-contiguous spectrum operation within any operating band the 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. | | | | + +**Table 6.7.4.6.4.1-4: OBUE limits applicable for IAB-MT in the frequency range 37 GHz – 52.6 GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test limit | Measurement bandwidth | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.1 \cdot \text{BW}_{\text{contiguous}}$ | $0.5 \text{ MHz} \leq f\_offset < 0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz}$ | $\text{Min}(-2.0 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 30.0 \text{ dB}, -9.0 \text{ dBm}))$ | 1 MHz | +| $0.1 \cdot \text{BW}_{\text{contiguous}} \leq \Delta f < \Delta f_{\text{max}}$ | $0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 41 \text{ dB}, -20 \text{ dBm}))$ | 1 MHz | +| NOTE: For non-contiguous spectrum operation within any operating band the 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. | | | | + +#### 6.7.4.6.4.2 OTA operating band unwanted emission limits (Category B) + +The power of unwanted emission of IAB-DU shall not exceed the limits in table 6.7.4.6.4.2-1 or 6.7.4.6.4.2-2. The power of unwanted emission of IAB-MT shall not exceed the limits in table 6.7.4.6.4.2-3 or 6.7.4.6.4.2-4. + +**Table 6.7.4.6.4.2-1: OBUE limits applicable for IAB-DU in the frequency range 24.25 – 33.4 GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test limit | Measurement bandwidth | +|-------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.1 \cdot \text{BW}_{\text{contiguous}}$ | $0.5 \text{ MHz} \leq f\_offset < 0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz}$ | $\text{Min}(-2.3 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 32.3 \text{ dB}, -9.3 \text{ dBm}))$ | 1 MHz | +| $0.1 \cdot \text{BW}_{\text{contiguous}} \leq \Delta f < \Delta f_B$ | $0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz} \leq f\_offset < \Delta f_B + 0.5 \text{ MHz}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 43 \text{ dB}, -20 \text{ dBm}))$ | 1 MHz | +| $\Delta f_B \leq \Delta f < \Delta f_{\text{max}}$ | $\Delta f_B + 5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\text{Min}(-5 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 33 \text{ dB}, -10 \text{ dBm}))$ | 10 MHz | + +NOTE 1: For non-contiguous spectrum operation within any *operating band* the 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 2: $\Delta f_B = 2 \cdot \text{BW}_{\text{contiguous}}$ when $\text{BW}_{\text{contiguous}} \leq 500 \text{ MHz}$ , otherwise $\Delta f_B = \text{BW}_{\text{contiguous}} + 500 \text{ MHz}$ . + +**Table 6.7.4.6.4.2-2: OBUE limits applicable for IAB-DU in the frequency range 37 – 52.6 GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test limit | Measurement bandwidth | +|-------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.1 \cdot \text{BW}_{\text{contiguous}}$ | $0.5 \text{ MHz} \leq f\_offset < 0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz}$ | $\text{Min}(-2.3 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 30.3 \text{ dB}, -9.3 \text{ dBm}))$ | 1 MHz | +| $0.1 \cdot \text{BW}_{\text{contiguous}} \leq \Delta f < \Delta f_B$ | $0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz} \leq f\_offset < \Delta f_B + 0.5 \text{ MHz}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 41 \text{ dB}, -20 \text{ dBm}))$ | 1 MHz | +| $\Delta f_B \leq \Delta f < \Delta f_{\text{max}}$ | $\Delta f_B + 5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\text{Min}(-5 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 31 \text{ dB}, -10 \text{ dBm}))$ | 10 MHz | + +NOTE 1: For non-contiguous spectrum operation within any *operating band* the 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 2: $\Delta f_B = 2 \cdot \text{BW}_{\text{contiguous}}$ when $\text{BW}_{\text{contiguous}} \leq 500 \text{ MHz}$ , otherwise $\Delta f_B = \text{BW}_{\text{contiguous}} + 500 \text{ MHz}$ . + +**Table 6.7.4.6.4.2-3: OBUE limits applicable for IAB-MT in the frequency range 24.25 – 33.4 GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test limit | Measurement bandwidth | +|-------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.1 \cdot \text{BW}_{\text{contiguous}}$ | $0.5 \text{ MHz} \leq f\_offset < 0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz}$ | $\text{Min}(-2.1 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 32.1 \text{ dB}, -9.1 \text{ dBm}))$ | 1 MHz | +| $0.1 \cdot \text{BW}_{\text{contiguous}} \leq \Delta f < \Delta f_B$ | $0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz} \leq f\_offset < \Delta f_B + 0.5 \text{ MHz}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 43 \text{ dB}, -20 \text{ dBm}))$ | 1 MHz | +| $\Delta f_B \leq \Delta f < \Delta f_{\text{max}}$ | $\Delta f_B + 5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\text{Min}(-5 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 33 \text{ dB}, -10 \text{ dBm}))$ | 10 MHz | + +NOTE 1: For non-contiguous spectrum operation within any *operating band* the 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 2: $\Delta f_B = 2 \cdot \text{BW}_{\text{contiguous}}$ when $\text{BW}_{\text{contiguous}} \leq 500 \text{ MHz}$ , otherwise $\Delta f_B = \text{BW}_{\text{contiguous}} + 500 \text{ MHz}$ . + +**Table 6.7.4.6.4.2-4: OBUE limits applicable for IAB- MT in the frequency range 37 – 52.6 GHz** + +| Frequency offset of measurement filter -3 dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test limit | Measurement bandwidth | +|-------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|-----------------------| +| $0 \text{ MHz} \leq \Delta f < 0.1 \cdot \text{BW}_{\text{contiguous}}$ | $0.5 \text{ MHz} \leq f\_offset < 0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz}$ | $\text{Min}(-2.0 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 30.0 \text{ dB}, -9.0 \text{ dBm}))$ | 1 MHz | +| $0.1 \cdot \text{BW}_{\text{contiguous}} \leq \Delta f < \Delta f_B$ | $0.1 \cdot \text{BW}_{\text{contiguous}} + 0.5 \text{ MHz} \leq f\_offset < \Delta f_B + 0.5 \text{ MHz}$ | $\text{Min}(-13 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 41 \text{ dB}, -20 \text{ dBm}))$ | 1 MHz | +| $\Delta f_B \leq \Delta f < \Delta f_{\text{max}}$ | $\Delta f_B + 5 \text{ MHz} \leq f\_offset < f\_offset_{\text{max}}$ | $\text{Min}(-5 \text{ dBm}, \text{Max}(P_{\text{rated,t,TRP}} - 31 \text{ dB}, -10 \text{ dBm}))$ | 10 MHz | + +NOTE 1: For non-contiguous spectrum operation within any *operating band* the 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 2: $\Delta f_B = 2 \cdot \text{BW}_{\text{contiguous}}$ when $\text{BW}_{\text{contiguous}} \leq 500 \text{ MHz}$ , otherwise $\Delta f_B = \text{BW}_{\text{contiguous}} + 500 \text{ MHz}$ . + +#### 6.7.4.6.4.3 Additional OTA operating band unwanted emission limits + +##### 6.7.4.6.4.3.1 Protection of Earth Exploration Satellite Service + +For IAB-Node operating in the frequency range 24.25 – 27.5 GHz, the power of unwanted emission shall not exceed the limits in table 6.7.4.6.4.3.1-1. + +**Table 6.7.4.6.4.3.1-1: OBUE limits for protection of Earth Exploration Satellite Service** + +| Frequency range | Measurement filter centre frequency range | Limit | Measurement Bandwidth | +|-----------------|-------------------------------------------|-----------------|-----------------------| +| 23.6 – 24 GHz | 23.7 – 23.9 GHz | -3 dBm (Note 1) | 200 MHz | +| 23.6 – 24 GHz | 23.7 – 23.9 GHz | -9 dBm (Note 2) | 200 MHz | + +NOTE 1: This limit applies to IAB-DU and IAB-MT brought into use on or before 1 September 2027. +NOTE 2: This limit applies to IAB-DU and IAB-MT brought into use after 1 September 2027. + +## 6.7.5 OTA transmitter spurious emissions + +### 6.7.5.1 General + +For IAB-DU, the OTA transmitter spurious emission limits for FR1 shall apply from 30 MHz to 12.75 GHz, excluding the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of each supported downlink *operating band*, up to $\Delta f_{\text{OBUE}}$ above the highest frequency of each supported downlink *operating band*, where the $\Delta f_{\text{OBUE}}$ is defined in table 9.7.1-1. For some FR1 *operating bands*, the upper limit is higher than 12.75 GHz in order to comply with the 5th harmonic limit of the downlink *operating band*, as specified in Recommendation ITU-R SM.329 [10]. + +For IAB-MT, the OTA transmitter spurious emission limits for FR1 shall apply from 30 MHz to 12.75 GHz, excluding the frequency range from $\Delta f_{\text{OBUE}}$ below the lowest frequency of each supported uplink *operating band*, up to $\Delta f_{\text{OBUE}}$ above the highest frequency of each supported uplink *operating band*, where the $\Delta f_{\text{OBUE}}$ is defined in table 9.7.1-2. For some FR1 *operating bands*, the upper limit is higher than 12.75 GHz in order to comply with the 5th harmonic limit of the uplink *operating band*, as specified in Recommendation ITU-R SM.329 [10]. + +For *multi-band RIB* each supported *operating band* and $\Delta f_{\text{OBUE}}$ MHz around each band are excluded from the OTA transmitter spurious emissions requirements. + +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 specification. + +*IAB-DU type 1-O* and *IAB-MT type 1-O* requirements consist of OTA transmitter spurious emission requirements based on TRP and co-location requirements not based on TRP. + +## 6.7.5.2 General OTA transmitter spurious emissions requirements + +### 6.7.5.2.1 Definition and applicability + +The general OTA transmitter spurious emissions requirements are specified as TRP per RIB, per cell, unless otherwise specified. + +### 6.7.5.2.2 Minimum requirement + +The minimum requirement for *IAB type 1-O* is specified in TS 38.174 [2], clause 9.7.5.2. + +The minimum requirement for *IAB type 2-O* is specified in TS 38.174 [2], clause 9.7.5.3. + +### 6.7.5.2.3 Test purpose + +The test purpose is to verify if the radiated spurious emissions from the IAB at the RIB are within the specified minimum requirements. + +### 6.7.5.2.4 Method of test + +#### 6.7.5.2.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier, see clause 4.9.1: + +- For FR1: + - B when testing from 30 MHz to $F_{DL\_low} - \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_low} - \Delta f_{OBUE}$ for IAB-MT + - T when testing from $F_{DL\_high} + \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_high} + \Delta f_{OBUE}$ for IAB-MT to 12.75 GHz (or to 5th harmonic) +- For FR2: + - B when testing from 30 MHz to $F_{DL\_low} - \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_low} - \Delta f_{OBUE}$ for IAB-MT + - T when testing from $F_{DL\_high} + \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_high} + \Delta f_{OBUE}$ for IAB-MT to 2nd harmonic (or to 60 GHz) + +RF bandwidth positions to be tested in single-band multi-carrier operation, see clause 4.9.1: + +- For FR1: + - $B_{RFBW}$ when testing from 30 MHz to $F_{DL\_low} - \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_low} - \Delta f_{OBUE}$ for IAB-MT + - $T_{RFBW}$ when testing from $F_{DL\_high} + \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_high} + \Delta f_{OBUE}$ for IAB-MT to 12.75 GHz (or 5th harmonic) +- For FR2: + - $B_{RFBW}$ when testing from 30 MHz to $F_{DL\_low} - \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_low} - \Delta f_{OBUE}$ for IAB-MT + - $T_{RFBW}$ when testing from $F_{DL\_high} + \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_high} + \Delta f_{OBUE}$ for IAB-MT to 2nd harmonic (or to 60 GHz) + +RF bandwidth positions to be tested in multi-band multi-carrier operation, see clause 4.9.1: + +- For FR1: + - $B'_{RFBW\_T'_{RFBW}}$ when testing from 30 MHz to $F_{DL\_Blow\_low} - \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_Blow\_low} - \Delta f_{OBUE}$ for IAB-MT + - $B'_{RFBW\_T'_{RFBW}}$ when testing from $F_{DL\_Bhigh\_high} + \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_Bhigh\_high} + \Delta f_{OBUE}$ for IAB-MT 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}$ for IAB-DU or $F_{UL\_Blow\_high} + \Delta f_{OBUE}$ to $F_{UL\_Bhigh\_low} - \Delta f_{OBUE}$ for IAB-MT + +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 I) as long as the required TRP level is achieved. + +#### 6.7.5.2.4.2 Procedure + +The following procedure for measuring TRP is based on directional power measurements as described in annex I. 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. + +- 1) Place the IAB-Node at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the IAB with the test system. +- 3) Measurements shall use a measurement bandwidth in accordance to the conditions in clause 6.7.5.2.5. +- 4) The measurement device characteristics shall be: + - Detection mode: True RMS. +- 5) Set the IAB to transmit: + - For RIB declared to be capable of single carrier operation only, set the RIB to transmit a signal according to the applicable test configuration in clause 4.8 using the corresponding test model in clause 4.9.2 (i.e. IAB-DU-FR1-TM1.1 for *IAB-DU type 1-O*, IAB-MT-FR1-TM1.1 for *IAB-MT type 1-O*, IAB-DU-FR2-TM1.1 for *IAB-DU type 2-O* or IAB-MT-FR2-TM1.1 for *IAB-MT type 2-O*), at manufacturer's declared rated output power $P_{\text{rated,c,TRP}}$ . + - For a RIB declared to be capable of multi-carrier and/or CA operation, set the RIB to transmit according to the corresponding test model in clause 4.9.2 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.7.2 and 4.8. + - For an IAB node declared to be capable of Simultaneous transmission between IAB-DU and IAB-MT (D.IAB-3), using the corresponding test model(s) in clause 4.9.2 for IAB-MT and IAB-DU using the applicable test configuration and corresponding power setting specified in clause 4.7.2 and 4.8. +- 6) Orient the positioner (and IAB) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see annex I). +- 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 I). + +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 *IAB type 1-O* and *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.5.2.5 Test requirement + +##### 6.7.5.2.5.1 Test requirement for *IAB type 1-O* + +For a IAB meeting category A the TRP of any spurious emission shall not exceed the limits in table 6.7.5.2.5.1-1. + +**Table 6.7.5.2.5.1-1: General IAB-DU and IAB-MT transmitter spurious emission limits in FR1 (Category A)** + +| Spurious frequency range | Test limit | Measurement bandwidth | Notes | +|---------------------------------------------------------------------------------------------------------|-------------|-----------------------|--------------------------------| +| 30 MHz – 1 GHz | -13 + X dBm | 100 kHz | Note 1, Note 6 | +| 1 GHz – 12.75 GHz | | 1 MHz | Note 1, Note 2, Note 6 | +| 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 6 | + +NOTE 1: Measurement bandwidths as in ITU-R SM.329 [10], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [10], 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. +NOTE 4: Void. +NOTE 5: Void. +NOTE 6: X = 9 dB, unless stated differently in regional regulation. + +For a IAB meeting category B the TRP of any spurious emission shall not exceed the limits in table 6.7.5.2.5.1-2. + +**Table 6.7.5.2.5.1-2: General IAB-DU and IAB-MT transmitter spurious emission limits in FR1 (Category B)** + +| Spurious frequency range | Test limit | Measurement bandwidth | Notes | +|---------------------------------------------------------------------------------------------------------|-------------|-----------------------|--------------------------------| +| 30 MHz – 1 GHz | -36 + X dBm | 100 kHz | Note 1, Note 5 | +| 1 GHz – 12.75 GHz | | 1 MHz | Note 1, Note 2, Note 5 | +| 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 5 | + +NOTE 1: Measurement bandwidths as in ITU-R SM.329 [10], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [105], 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.75GHz. +NOTE 4: Void. +NOTE 5: X = 9 dB, unless stated differently in regional regulation. + +#### 6.7.5.2.5.2 Test requirement for IAB type 2-O + +##### 6.7.5.2.5.2.1 General + +The requirements of either clause 6.7.5.2.5.2.2 (Category A limits) or clause 6.7.5.2.5.2.3 (Category B limits) shall apply. The application of either Category A or Category B limits shall be the same as for Operating band unwanted emissions in clause 6.7.1. + +##### 6.7.5.2.5.2.2 OTA transmitter spurious emissions (Category A) + +The power of any spurious emission shall not exceed the limits in table 6.7.5.2.5.2.2-1. + +**Table 6.7.5.2.5.2.2-1: General IAB-DU and IAB-MT transmitter spurious emission limits in FR2-1 (Category A)** + +| Spurious frequency range | Test limit | Measurement bandwidth | Notes | +|-----------------------------------------------------------------------------------------------------------|------------|-----------------------|----------------| +| 30 MHz – 1 GHz | -13 dBm | 100 kHz | Note 1 | +| 1 GHz – min(2 nd harmonic of the upper frequency edge of the DL operating band in GHz; 60 GHz) | | 1 MHz | Note 1, Note 2 | + +NOTE 1: Measurement bandwidth as in ITU-R SM.329 [10], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [10], s2.5 table 1. + +#### 6.7.5.2.5.2.3 OTA transmitter spurious emissions (Category B) + +The power of any spurious emission shall not exceed the limits in table 6.7.5.2.5.2.3-1. + +**Table 6.7.5.2.5.2.3-1: IAB-DU and IAB-MT radiated Tx spurious emission limits in FR2-1 (Category B)** + +| Frequency range (Note 4) | Test limit | Measurement Bandwidth | Note | +|-------------------------------------------------------------------------------------------------------------------------|------------|-----------------------|----------------| +| 30 MHz ↔ 1 GHz | -36 dBm | 100 kHz | Note 1 | +| 1 GHz ↔ 18 GHz | -30 dBm | 1 MHz | Note 1 | +| 18 GHz ↔ F step,1 | -20 dBm | 10 MHz | Note 2 | +| F step,1 ↔ F step,2 | -15 dBm | 10 MHz | Note 2 | +| F step,2 ↔ F step,3 | -10 dBm | 10 MHz | Note 2 | +| F step,4 ↔ F step,5 | -10 dBm | 10 MHz | Note 2 | +| F step,5 ↔ F step,6 | -15 dBm | 10 MHz | Note 2 | +| F step,6 ↔ min(2 nd harmonic of the upper frequency edge of the DL operating band in GHz; 60 GHz) | -20 dBm | 10 MHz | Note 2, Note 3 | + +NOTE 1: Bandwidth as in ITU-R SM.329 [10], s4.1 +NOTE 2: Limit and bandwidth as in ERC Recommendation 74-01 [11], annex 2. +NOTE 3: Upper frequency as in ITU-R SM.329 [10], s2.5 table 1. +NOTE 4: The step frequencies Fstep,x are defined in table 6.7.5.2.5.2.3-2. + +**Table 6.7.5.2.5.2.3-2: Step frequencies for defining the IAB-DU and IAB-MT radiated Tx spurious emission limits in FR2-1 (Category B)** + +| Operating band | F step,1 (GHz) | F step,2 (GHz) | F step,3 (GHz) (Note 2) | F step,4 (GHz) (Note 2) | F step,5 (GHz) | F step,6 (GHz) | +|----------------|---------------------------|---------------------------|------------------------------------|------------------------------------|---------------------------|---------------------------| +| n257 | 18 | 23.5 | 25 | 31 | 32.5 | 41.5 | +| n258 | 18 | 21 | 22.75 | 29 | 30.75 | 40.5 | +| n259 | 23.5 | 35.5 | 38 | 45 | 47.5 | 59.5 | + +NOTE 1: Fstep,x are based on ERC Recommendation 74-01 [11], annex 2. +NOTE 2: Fstep,3 and Fstep,4 are aligned with the values for ΔfOBUE in table 6.7.1-1. + +#### 6.7.5.3 Void + +#### 6.7.5.4 Additional spurious emissions requirements + +##### 6.7.5.4.1 Definition and applicability + +These requirements may be applied for the protection of systems operating in frequency ranges other than the IAB downlink operating band. The limits may apply as an optional protection of such systems that are deployed in the same geographical area as the IAB-Node, or they may be set by local or regional regulation as a mandatory requirement for an NR 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, CDMA, UTRA, E-UTRA, NR, etc.). + +The requirement shall apply at each RIB supporting transmission in the *operating band*. + +All additional spurious requirements are TRP unless otherwise stated. + +#### 6.7.5.4.2 Minimum Requirement + +The minimum requirement for *IAB type 1-O* is specified in TS 38.174 [2], clause 9.7.5.2.3. + +The minimum requirement for *IAB type 2-O* is specified in TS 38.174 [2], clause 9.7.5.3.3. + +#### 6.7.5.4.3 Test purpose + +The test purpose is to verify the radiated spurious emissions from the IAB at the RIB are within the specified additional spurious emissions requirements. + +#### 6.7.5.4.4 Method of test + +##### 6.7.5.4.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: + +- For FR1: + - B when testing from 30 MHz to $F_{DL\_low} - \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_low} - \Delta f_{OBUE}$ for IAB-MT + - T when testing from $F_{DL\_high} + \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_high} + \Delta f_{OBUE}$ for IAB-MT to 12.75 GHz (or to 5th harmonic) +- For FR2: + - B when testing from 30 MHz to $F_{DL\_low} - \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_low} - \Delta f_{OBUE}$ for IAB-MT + - T when testing from $F_{DL\_high} + \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_high} + \Delta f_{OBUE}$ for IAB-MT to 60 GHz (or to 2nd harmonic) + +RF bandwidth positions to be tested in single-band multi-carrier operation: + +- For FR1: + - $B_{RFBW}$ when testing from 30 MHz to $F_{DL\_low} - \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_low} - \Delta f_{OBUE}$ for IAB-MT + - $T_{RFBW}$ when testing from $F_{DL\_high} + \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_high} + \Delta f_{OBUE}$ for IAB-MT to 12.75 GHz (or to 5th harmonic) +- For FR2: + - $B_{RFBW}$ when testing from 30 MHz to $F_{DL\_low} - \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_low} - \Delta f_{OBUE}$ for IAB-MT + - $T_{RFBW}$ when testing from $F_{DL\_high} + \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_high} + \Delta f_{OBUE}$ for IAB-MT to 60 GHz (or to 2nd harmonic) + +RF bandwidth positions to be tested in multi-band multi-carrier operation: + +- For FR1: + - $B_{RFBW\_T'_{RFBW}}$ when testing from 30 MHz to $F_{DL\_Blow\_low} - \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_low} - \Delta f_{OBUE}$ for IAB-MT + - $B'_{RFBW\_T_{RFBW}}$ when testing from $F_{DL\_Bhigh\_high} + \Delta f_{OBUE}$ for IAB-DU or $F_{UL\_Bhigh\_high} + \Delta f_{OBUE}$ for IAB-MT 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}$ for IAB-DU or $F_{UL\_Blow\_high} + \Delta f_{OBUE}$ to $F_{UL\_Bhigh\_low} - \Delta f_{OBUE}$ for IAB-MT + +Directions to be tested: As the requirements are TRP the beam pattern(s) may be set up to optimise the TRP measurement procedure (see annex I) as long as the required TRP level is achieved. + +#### 6.7.5.4.4.2 Procedure + +The following procedure for measuring TRP is based on the directional power measurements as described in annex I. 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. + +- 1) Place the IAB-Node at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the IAB with the test system. +- 3) Measurements shall use a measurement bandwidth in accordance to the conditions in clause 6.7.5.4.5. +- 4) The measurement device characteristics shall be: + - Detection mode: True RMS. +- 5) Set the IAB-Node to transmit: + - For RIB declared to be capable of single carrier operation only, set the RIB to transmit a signal according to the applicable test configuration in clause 4.8 using the corresponding test model in clause 4.9.2 (IAB-DU-FR1-TM1.1 for *IAB-DU type 1-O*, IAB-MT-FR1-TM1.1 for *IAB-MT type 1-O*, IAB-DU-FR2-TM1.1 for *IAB-DU type 2-O* or IAB-MT-FR2-TM1.1 for *IAB-MT type 2-O*), at manufacturer's declared rated output power $P_{rated,c,TRP}$ . + - For a RIB declared to be capable of multi-carrier and/or CA operation, set the RIB to transmit according to IAB-DU-FR1-TM1.1 for *IAB-DU type 1-O*, IAB-MT-FR1-TM1.1 for *IAB-MT type 1-O*, IAB-DU-FR2-TM1.1 for *IAB-DU type 2-O* or IAB-MT-FR2-TM1.1 for *IAB-MT type 2-O* in clause 4.9.2 on all carriers configured using the applicable test configuration and corresponding power setting specified in clause 4.7.2 and 4.8. + - For an IAB node declared to be capable of Simultaneous transmission between IAB-DU and IAB-MT (D.IAB-3), set the RIB to transmit according to IAB-DU-FR1-TM1.1 for *IAB-DU type 1-O*, IAB-MT-FR1-TM1.1 for *IAB-MT type 1-O*, IAB-DU-FR2-TM1.1 for *IAB-DU type 2-O* or IAB-MT-FR2-TM1.1 for *IAB-MT type 2-O* in clause 4.9.2 using the applicable test configuration and corresponding power setting specified in clause 4.7.2 and 4.8. +- 6) Orient the positioner (and IAB) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see annex I). +- 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 I). + +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.5.4.5 Test requirement + +##### 6.7.5.4.5.1 Test requirement for *IAB type 1-O* + +The power of any spurious emission shall not exceed the test limits in table 6.7.5.4.5-1 for a IAB 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 Note column of table 6.7.5.4.5-1 apply for each supported *operating band*. + +**Table 6.7.5.4.5.1-1: IAB-DU and IAB-MT spurious emissions basic limits for co-existence with systems operating in other frequency bands** + +| System type to co-exist with | Frequency range for co-existence requirement | Test limits | Measurement bandwidth | Note | +|------------------------------------------------------|----------------------------------------------|-------------|-----------------------|------| +| GSM900 | 921 – 960 MHz | -45.4 dBm | 100 kHz | | +| | 876 – 915 MHz | -49.4 dBm | 100 kHz | | +| DCS1800 | 1805 – 1880 MHz | -35.4 dBm | 100 kHz | | +| | 1710 – 1785 MHz | -49.4 dBm | 100 kHz | | +| PCS1900 | 1930 – 1990 MHz | -35.4 dBm | 100 kHz | | +| | 1850 – 1910 MHz | -49.4 dBm | 100 kHz | | +| GSM850 or | 869 – 894 MHz | -45.4 dBm | 100 kHz | | +| CDMA850 | 824 – 849 MHz | -49.4 dBm | 100 kHz | | +| UTRA FDD | 2110 – 2170 MHz | -40.4 dBm | 1 MHz | | +| Band I or E-UTRA Band 1 or NR Band n1 | 1920 – 1980 MHz | -37.4 dBm | 1 MHz | | +| UTRA FDD | 1930 – 1990 MHz | -40.4 dBm | 1 MHz | | +| Band II or E-UTRA Band 2 or NR Band n2 | 1850 – 1910 MHz | -37.4 dBm | 1 MHz | | +| UTRA FDD | 1805 – 1880 MHz | -40.4 dBm | 1 MHz | | +| Band III or E-UTRA Band 3 or NR Band n3 | 1710 – 1785 MHz | -37.4 dBm | 1 MHz | | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 – 2155 MHz | -40.4 dBm | 1 MHz | | +| | 1710 – 1755 MHz | -37.4 dBm | 1 MHz | | +| UTRA FDD Band V or E-UTRA Band 5 or NR Band n5 | 869 – 894 MHz | -40.4 dBm | 1 MHz | | +| | 824 – 849 MHz | -37.4 dBm | 1 MHz | | +| UTRA FDD | 860 – 890 MHz | -40.4 dBm | 1 MHz | | +| Band VI, XIX or E-UTRA Band 6, 18, 19 or NR Band n18 | 815 – 830 MHz | -37.4 dBm | 1 MHz | | +| | 830 – 845 MHz | -37.4 dBm | 1 MHz | | +| UTRA FDD Band VII or E-UTRA Band 7 or NR Band n7 | 2620 – 2690 MHz | -40.4 dBm | 1 MHz | | +| | 2500 – 2570 MHz | -37.4 dBm | 1 MHz | | + +| System type to co-exist with | Frequency range for co-existence requirement | Test limits | Measurement bandwidth | Note | +|----------------------------------------------------|----------------------------------------------|-------------|-----------------------|------------------------------------------------------------------------------------| +| UTRA FDD Band VIII or E-UTRA Band 8 or NR Band n8 | 925 – 960 MHz | -40.4 dBm | 1 MHz | | +| | 880 – 915 MHz | -37.4 dBm | 1 MHz | | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 – 1879.9 MHz | -40.4 dBm | 1 MHz | | +| | 1749.9 – 1784.9 MHz | -37.4 dBm | 1 MHz | | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 – 2170 MHz | -40.4 dBm | 1 MHz | | +| | 1710 – 1770 MHz | -37.4 dBm | 1 MHz | | +| UTRA FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1475.9 – 1510.9 MHz | -40.4 dBm | 1 MHz | | +| | 1427.9 – 1447.9 MHz | -37.4 dBm | 1 MHz | | +| | 1447.9 – 1462.9 MHz | -37.4 dBm | 1 MHz | | +| UTRA FDD Band XII or E-UTRA Band 12 or NR Band n12 | 729 – 746 MHz | -40.4 dBm | 1 MHz | | +| | 699 – 716 MHz | -37.4 dBm | 1 MHz | | +| UTRA FDD Band XIII or E-UTRA Band 13 | 746 – 756 MHz | -40.4 dBm | 1 MHz | | +| | 777 – 787 MHz | -37.4 dBm | 1 MHz | | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR band n14 | 758 – 768 MHz | -40.4 dBm | 1 MHz | | +| | 788 – 798 MHz | -37.4 dBm | 1 MHz | | +| E-UTRA Band 17 | 734 – 746 MHz | -40.4 dBm | 1 MHz | | +| | 704 – 716 MHz | -37.4 dBm | 1 MHz | | +| UTRA FDD Band XX or E-UTRA Band 20 or NR Band n20 | 791 – 821 MHz | -40.4 dBm | 1 MHz | | +| | 832 – 862 MHz | -37.4 dBm | 1 MHz | | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 – 3590 MHz | -40 dBm | 1 MHz | This requirement does not apply to IAB-DU and IAB-MT operating in band n77 or n78. | +| | 3410 – 3490 MHz | -37 dBm | 1 MHz | This requirement does not apply to IAB-DU and IAB-MT operating in band n77 or n78. | + +| System type to co-exist with | Frequency range for co-existence requirement | Test limits | Measurement bandwidth | Note | +|-----------------------------------------------------|----------------------------------------------|-------------|-----------------------|------| +| E-UTRA Band 24 | 1525 – 1559 MHz | -40.4 dBm | 1 MHz | | +| | 1626.5 – 1660.5 MHz | -37.4 dBm | 1 MHz | | +| UTRA FDD Band XXV or E-UTRA Band 25 or NR band n25 | 1930 – 1995 MHz | -40.4 dBm | 1 MHz | | +| | 1850 – 1915 MHz | -37.4 dBm | 1 MHz | | +| UTRA FDD Band XXVI or E-UTRA Band 26 or NR Band n26 | 859 – 894 MHz | -40.4 dBm | 1 MHz | | +| | 814 – 849 MHz | -37.4 dBm | 1 MHz | | +| E-UTRA Band 27 | 852 – 869 MHz | -40.4 dBm | 1 MHz | | +| | 807 – 824 MHz | -37.4 dBm | 1 MHz | | +| E-UTRA Band 28 or NR Band n28 | 758 – 803 MHz | -40.4 dBm | 1 MHz | | +| | 703 – 748 MHz | -37.4 dBm | 1 MHz | | +| E-UTRA Band 29 or NR Band n29 | 717 – 728 MHz | -40.4 dBm | 1 MHz | | +| E-UTRA Band 30 or NR Band n30 | 2350 – 2360 MHz | -40.4 dBm | 1 MHz | | +| | 2305 – 2315 MHz | -37.4 dBm | 1 MHz | | +| E-UTRA Band 31 or NR Band n31 | 462.5 – 467.5 MHz | -40.4 dBm | 1 MHz | | +| | 452.5 – 457.5 MHz | -37.4 dBm | 1 MHz | | +| UTRA FDD band XXXII or E-UTRA band 32 | 1452 – 1496 MHz | -40.4 dBm | 1 MHz | | +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 – 1920 MHz | -40.4 dBm | 1 MHz | | +| UTRA TDD Band a) or E-UTRA Band 34 or NR band n34 | 2010 – 2025 MHz | -40.4 dBm | 1 MHz | | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -40.4 dBm | 1 MHz | | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 – 1990 MHz | -40.4 dBm | 1 MHz | | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 – 1930 MHz | -40.4 dBm | 1 MHz | | + +| System type to co-exist with | Frequency range for co-existence requirement | Test limits | Measurement bandwidth | Note | +|---------------------------------------------------|----------------------------------------------|-------------|-----------------------|---------------------------------------------------------------------------| +| UTRA TDD Band d) or E-UTRA Band 38 or NR Band n38 | 2570 – 2620 MHz | -40.4 dBm | 1 MHz | | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920MHz | -40.4 dBm | 1 MHz | | +| UTRA TDD Band e) or E-UTRA Band 40 or NR Band n40 | 2300 – 2400MHz | -40.4 dBm | 1 MHz | | +| E-UTRA Band 41 or NR Band n41, n90 | 2496 – 2690 MHz | -40.4 dBm | 1 MHz | This is not applicable IAB-DU and IAB-MT operating in Band n41. | +| E-UTRA Band 42 | 3400 – 3600 MHz | -40 dBm | 1 MHz | This is not applicable to IAB-DU and IAB-MT operating in Band n77 or n78. | +| E-UTRA Band 43 | 3600 – 3800 MHz | -40 dBm | 1 MHz | This is not applicable to IAB-DU and IAB-MT operating in Band n77 or n78. | +| E-UTRA Band 44 | 703 – 803 MHz | -40.4 dBm | 1 MHz | | +| E-UTRA Band 45 | 1447 – 1467 MHz | -40.4 dBm | 1 MHz | | +| 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 dBm | 1 MHz | This is not applicable to IAB-DU and IAB-MT operating in Band n77 or n78. | +| E-UTRA Band 50 or NR band n50 | 1432 – 1517 MHz | -40.4 dBm | 1 MHz | | +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | -40.4 dBm | 1 MHz | | +| E-UTRA Band 53 or NR Band n53 | 2483.5 – 2495 MHz | -40.4 dBm | 1 MHz | This is not applicable to IAB-DU and IAB-MT operating in Band n41. | +| E-UTRA Band 54 or NR Band n54 | 1670 – 1675 MHz | -40.4 dBm | 1 MHz | | +| E-UTRA Band 65 or NR Band n65 | 2110 – 2200 MHz | -40.4 dBm | 1 MHz | | +| | 1920 – 2010 MHz | -37.4 dBm | 1 MHz | | +| E-UTRA Band 66 or NR Band n66 | 2110 – 2200 MHz | -40.4 dBm | 1 MHz | | +| | 1710 – 1780 MHz | -37.4 dBm | 1 MHz | | +| E-UTRA Band 67 or NR Band n67 | 738 – 758 MHz | -40.4 dBm | 1 MHz | | +| E-UTRA Band 68 | 753 – 783 MHz | -40.4 dBm | 1 MHz | | +| | 698-728 MHz | -37.4 dBm | 1 MHz | | + +| System type to co-exist with | Frequency range for co-existence requirement | Test limits | Measurement bandwidth | Note | +|-------------------------------|----------------------------------------------|-------------|-----------------------|-----------------------------------------------------------------------------------| +| E-UTRA Band 69 | 2570 – 2620 MHz | -40.4 dBm | 1 MHz | | +| E-UTRA Band 70 or NR Band n70 | 1995 – 2020 MHz | -40.4 dBm | 1 MHz | | +| | 1695 – 1710 MHz | -37.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 74 or NR Band n74 | 1475 – 1518 MHz | -40.4 dBm | 1 MHz | | +| | 1427 – 1470 MHz | -37.4 dBm | 1 MHz | | +| E-UTRA Band 75 or NR Band n75 | 1432 – 1517 MHz | -40.4 dBm | 1 MHz | | +| E-UTRA Band 76 or NR Band n76 | 1427 – 1432 MHz | -40.4 dBm | 1 MHz | | +| NR Band n77 | 3.3 – 4.2 GHz | -40 dBm | 1 MHz | This requirement does not apply to IAB-DU and IAB-MT operating in Band n77 or n78 | +| NR Band n78 | 3.3 – 3.8 GHz | -40 dBm | 1 MHz | This requirement does not apply to IAB-DU and IAB-MT operating in Band n77 or n78 | +| NR Band n79 | 4.4 – 5.0 GHz | -39.5 dBm | 1 MHz | This requirement does not apply to IAB-DU and IAB-MT operating in Band n79 | +| NR Band n80 | 1710 – 1785 MHz | -37.4 dBm | 1 MHz | | +| NR Band n81 | 880 – 915 MHz | -40.4 dBm | 1 MHz | | +| NR Band n82 | 832 – 862 MHz | -45.4 dBm | 1 MHz | | +| NR Band n83 | 703 – 748 MHz | -49.4 dBm | 1 MHz | | +| NR Band n84 | 1920 – 1980 MHz | -35.4 dBm | 1 MHz | | +| E-UTRA Band 85 or NR Band n85 | 728 – 746 MHz | -49.4 dBm | 1 MHz | | +| | 698 – 716 MHz | -35.4 dBm | 1 MHz | | +| NR Band n86 | 1710 – 1780 MHz | -49.4 dBm | 1 MHz | | +| NR Band n89 | 824 – 849 MHz | -45.4 dBm | 1 MHz | | +| NR Band n91 | 1427 – 1432 MHz | -40.4 dBm | 1 MHz | | +| | 832 – 862 MHz | -37.4 dBm | 1 MHz | | +| NR Band n92 | 1432 – 1517 MHz | -40.4 dBm | 1 MHz | | +| | 832 – 862 MHz | -37.4 dBm | 1 MHz | | +| NR Band n93 | 1427 – 1432 MHz | -37.4 dBm | 1 MHz | | + +| System type to co-exist with | Frequency range for co-existence requirement | Test limits | Measurement bandwidth | Note | +|---------------------------------|----------------------------------------------|-------------|-----------------------|------| +| | 880 – 915 MHz | -40.4 dBm | 1 MHz | | +| NR Band n94 | 1432 – 1517 MHz | -40.4 dBm | 1 MHz | | +| | 880 – 915 MHz | -37.4 dBm | 1 MHz | | +| 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 – 2400MHz | -40.4 dBm | 1 MHz | | +| NR Band n98 | 1880 – 1920MHz | -40.4 dBm | 1 MHz | | +| NR Band n99 | 1626.5 – 1660.5 MHz | -37.4 dBm | 1 MHz | | +| NR Band n100 | 919.4 – 925 MHz | -40.4 dBm | 1 MHz | | +| | 874.4 – 880 MHz | -37.4 dBm | 1MHz | | +| NR Band n101 | 1900 - 1910 MHz | -40.4 dBm | 1 MHz | | +| NR Band n102 | 6425 – 7125 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 | | +| | 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 | | +| NR Band n109 | 1432 – 1517 MHz | -40.4 dBm | 1 MHz | | +| | 703 – 733 MHz | -37.4 dBm | 1 MHz | | + +NOTE 1: As defined in the scope for spurious emissions in this clause the co-existence requirements in table 6.7.5.4.5.1-1 do not apply for the $\Delta f_{OBUE}$ frequency range immediately outside the downlink *operating band* (see table 5.2-1). Emission limits for this excluded frequency range may be covered by local or regional requirements. + +NOTE 2: Table 6.7.5.4.5.1-1 assumes that two *operating bands*, where the frequency ranges in table 5.2-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. + +## 6.7.5.5 Co-location requirements + +### 6.7.5.5.1 Definition and applicability + +These requirements may be applied for the protection of other BS, IAB-DU or IAB-MT receivers when GSM900, DCS1800, PCS1900, GSM850, CDMA850, UTRA FDD, UTRA TDD, E-UTRA, NR BS, IAB-DU or IAB-MT are co-located with IAB-MT and/or IAB-DU. + +The requirements assume a 30 dB coupling loss between transmitter and receiver and are based on co-location with same class. + +#### 6.7.5.5.2 Minimum requirements + +The minimum requirement for *IAB type I-O* is defined in TS 38.174 [2], clause 9.7.5.2. + +#### 6.7.5.5.3 Test purpose + +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.5.5.4 Method of test + +##### 6.7.5.5.4.1 Initial conditions + +Test environment: normal; see clause B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +*IAB RF Bandwidth* positions to be tested for multi-carrier: + +- $M_{\text{RFBW}}$ in *single-band RIB*, see clause 4.9.1; +- $B_{\text{RFBW\_T}}^{\text{RFBW}}$ and $B'_{\text{RFBW\_T}}^{\text{RFBW}}$ in *multi-band RIB*, see clause 4.9.1. + +In addition, for *multi-band RIB*: + +- For $B_{\text{RFBW\_T}}^{\text{RFBW}}$ , emission testing above the highest operating band may be omitted. +- For $B'_{\text{RFBW\_T}}^{\text{RFBW}}$ , emission testing below the lowest operating band may be omitted. + +Directions to be tested: The FR1 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.5.5.4.2 Procedure + +- 1) Select and place the IAB-Node and CLTA as described in clause 4.12, with parameters as specified in table 4.12.2.2-1 and table 4.12.2.3-1. +- 2) Several CLTAs might be required to cover the whole co-location spurious emission frequency ranges. +- 3) Place test antenna in reference direction at far-field distance, aligned in all supported polarizations (single or dual) with the IAB-Node as depicted in annex E.1.3. +- 4) The test antenna shall be dual (or single) polarized with the same frequency range as the IAB-Node for co-location spurious emission test case. +- 5) Connect test antenna and CLTA to the measurement equipment as depicted in annex E.1.3. +- 6) OTA co-location spurious emission is measured as the power sum over all supported polarizations at the CLTA conducted output(s). +- 7) The measurement device (signal analyser) characteristics shall be: + - Detection mode: True RMS. +- 8) Set the *IAB type I-O* to transmit: + - Set the IAB-Node to transmit maximum power according to the applicable test configuration in clause 4.8 using the corresponding test models or set of physical channels in clause 4.9.2. + +- For the IAB-Node declared to be capable of multi-carrier and/or CA operation, set the IAB-Node to transmit according to the applicable test configuration and corresponding power setting specified in clause 4.7.2 and 4.8 using the corresponding test models on all carriers configured. +- For an IAB-Node declared to be capable of Simultaneous transmission between IAB-DU and IAB-MT (D.IAB-3), set the IAB-Node to transmit according to the applicable test configuration and corresponding power setting specified in clause 4.7.2 and 4.8 for IAB-DU and IAB-MT. + +9) Measure the emission at the specified frequencies with specified measurement bandwidth. + +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.5 Test requirements + +#### 6.7.5.5.5.1 Test requirement for *IAB type 1-O* + +These requirements may be applied for the protection of other IAB receivers when GSM900, DCS1800, PCS1900, GSM850, CDMA850, UTRA FDD, UTRA TDD, E-UTRA and/or NR BS are co-located with a IAB Node. + +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. + +This requirement is a co-location requirement as defined in clause 4.9, in TS 38.174 [2], the power levels are specified at the CLTA output. + +The output of the CLTA of any spurious emission shall not exceed the test limit in table 6.7.5.5.5.1-1. + +For a *multi-band RIB*, the exclusions and conditions in the notes column of table 6.7.5.5.5.1-1 apply for each supported operating band. + +**Table 6.7.5.5.5.1-1: IAB-DU and IAB-MT spurious emissions basic limits for co-location with BS or IAB-Node** + +| Co-located system | Frequency range for co-location requirement | Test limits | | | Measurement bandwidth | Note | +|--------------------------------------------------|---------------------------------------------|-------------------------|------------|-------------------------|-----------------------|------| +| | | WA IAB-DU and WA IAB-MT | MR IAB-DU | LA IAB-DU and LA IAB-MT | | | +| GSM900 | 876 – 915 MHz | -115.9 dBm | -108.9 dBm | -87.9 dBm | 100 kHz | | +| DCS1800 | 1710 – 1785 MHz | -115.9 dBm | -108.9 dBm | -97.9 dBm | 100 kHz | | +| PCS1900 | 1850 – 1910 MHz | -115.9 dBm | -108.9 dBm | -97.9 dBm | 100 kHz | | +| GSM850 or CDMA850 | 824 – 849 MHz | -115.9 dBm | -108.9 dBm | -87.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 | | + +| Co-located system | Frequency range for co-location requirement | Test limits | | | Measurement bandwidth | Note | +|-----------------------------------------------------|---------------------------------------------|-------------------------|------------|-------------------------|-----------------------|--------------------------------------------------------------------------| +| | | WA IAB-DU and WA IAB-MT | MR IAB-DU | LA IAB-DU and LA IAB-MT | | | +| 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 | | +| 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 | 777 – 787 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA FDD Band XIV or E-UTRA Band 14 or NR Band n14 | 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 IAB-DU and IAB-MT operating in Band n77 or n78 | +| E-UTRA Band 23 | 2000 – 2020 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 24 | 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 | | +| E-UTRA Band 30 or NR Band n30 | 2305 – 2315 MHz | -113.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 | | +| 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 | | +| UTRA TDD Band b) or E-UTRA Band 35 | 1850 – 1910 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | + +| Co-located system | Frequency range for co-location requirement | Test limits | | | Measurement bandwidth | Note | +|---------------------------------------------------|---------------------------------------------|-------------------------|------------|-------------------------|-----------------------|--------------------------------------------------------------------------| +| | | WA IAB-DU and WA IAB-MT | MR IAB-DU | LA IAB-DU and LA IAB-MT | | | +| UTRA TDD Band b) or E-UTRA Band 36 | 1930 – 1990 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA TDD Band c) or E-UTRA Band 37 | 1910 – 1930 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| 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 | | +| UTRA TDD Band f) or E-UTRA Band 39 or NR band n39 | 1880 – 1920MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| UTRA TDD Band e) or E-UTRA Band 40 or NR Band n40 | 2300 – 2400MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 41 or NR Band n41, n90 | 2496 – 2690 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | This is not applicable to IAB-DU and IAB-MT operating in Band n41 | +| E-UTRA Band 42 | 3400 – 3600 MHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to IAB-DU and IAB-MT operating in Band 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 IAB-DU and IAB-MT operating in Band n77 or n78 | +| E-UTRA Band 44 | 703 – 803 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| E-UTRA Band 45 | 1447 – 1467 MHz | -113.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 IAB-DU and IAB-MT operating in Band 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 | | +| E-UTRA Band 51 or NR Band n51 | 1427 – 1432 MHz | N/A | N/A | -105.9 dBm | 100 kHz | | +| 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 IAB-DU and IAB-MT operating in Band n41 | +| 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 | 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 | | + +| Co-located system | Frequency range for co-location requirement | Test limits | | | Measurement bandwidth | Note | +|-------------------------------|---------------------------------------------|-------------------------|------------|-------------------------|-----------------------|--------------------------------------------------------------------------| +| | | WA IAB-DU and WA IAB-MT | MR IAB-DU | LA IAB-DU and LA IAB-MT | | | +| E-UTRA Band 74 or NR Band n74 | 1427 – 1470 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR Band n77 | 3.3 – 4.2 GHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to IAB-DU and IAB-MT operating in Band n77 or n78 | +| NR Band n78 | 3.3 – 3.8 GHz | -113.7 dBm | -108.7 dBm | -105.7 dBm | 100 kHz | This is not applicable to IAB-DU and IAB-MT operating in Band n77 or n78 | +| NR Band n79 | 4.4 – 5.0 GHz | -113.6 dBm | -108.6 dBm | -105.6 dBm | 100 kHz | This is not applicable to IAB-DU and IAB-MT operating in Band n79 | +| 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 | | +| NR Band n89 | 824 – 849 MHz | -113.9 dBm | -108.9 dBm | -105.9 dBm | 100 kHz | | +| NR Band n91 | 832 – 862 MHz | -113.9 dBm | -108.9 dBm | -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 | -113.9 dBm | -108.9 dBm | -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 | | + +| Co-located system | Frequency range for co-location requirement | Test limits | | | Measurement bandwidth | Note | +|---------------------------------|---------------------------------------------|-------------------------|------------|-------------------------|-----------------------|------| +| | | WA IAB-DU and WA IAB-MT | MR IAB-DU | LA IAB-DU and LA IAB-MT | | | +| NR Band n97 | 2300 – 2400MHz | -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 | 6425 – 7125 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 | | + +NOTE 1: As defined in the scope for spurious emissions in this clause, the co-location requirements in table 6.6.5.2.3-1 do not apply for the frequency range extending $\Delta f_{\text{OBUE}}$ immediately outside the transmit frequency range of a IAB-MT and IAB-DU. 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 antenna to antenna minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [15]. + +NOTE 2: Table 6.6.5.2.3-1 assumes that two operating bands, where the corresponding transmit and receive frequency ranges in table 5.2-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. + +## 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 *IAB type 1-O*, 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 *IAB -DU type 1-O* and *IAB -MT type 1-O* is defined in TS 38.174 [2], clause 9.8.2. + +The OTA transmitter intermodulation requirement is not applicable for *IAB type 2-O*. + +### 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 B.2. + +RF channels to be tested for single carrier: *M*; see clause 4.9.1. + +*IAB RF Bandwidth* positions to be tested for multi-carrier: + +- $M_{\text{RFBW}}$ in *single-band RIB*, see clause 4.9.1; +- $B_{\text{RFBW\_T'}}$ and $B'_{\text{RFBW\_T'}}$ in *multi-band RIB*, see clause 4.9.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. + +Directions to be tested: The FR1 requirement is specified as co-location requirement. For general description of co-location requirements, refer to clause 4.12. + +#### 6.8.4.2 Procedure + +- 1) Select a CLTA according to the description in clause 4.12 and parameters given in table 4.12.2.2-1. +- 2) Place the CLTA according to the description in clause 4.12 and parameters given in table 4.12.2.3-1. +- 3) The test antenna(s) shall be dual (or single) polarized covering the same frequency range as the IAB and the emission frequencies. +- 4) Several test antennas are required to cover both the IAB and the whole emission frequency range. +- 5) Connect test antenna and CLTA to the measurement equipment as shown in annex E.1.5. +- 6) During the OTA emission measurements at the test antenna conducted output(s), both IAB and CLTA are rotated around same axis. +- 7) The OTA emission measurement method shall be TRP, according to the procedure described in annex I. +- 8) The measurement device (signal analyser) characteristics shall be: + - Detection mode: True RMS. +- 9) Set the IAB node to transmit: + +For IAB-DU: + + - Set the IAB-DU to transmit maximum power according to the applicable test configuration in clause 4.8 using the corresponding test models or set of physical channels in clause 4.9.2. + - For the IAB-DU declared to be capable of multi-carrier and/or CA operation, set the IAB-DU to transmit according to the applicable test configuration and corresponding power setting specified in clause 4.7.2 and 4.8 using the corresponding test models on all carriers configured. + +For IAB-MT: + +- Set the IAB-MT to transmit maximum power according to the applicable test configuration in clause 4.8 using the corresponding test models or set of physical channels in clause 4.9.2. +- For the IAB-MT declared to be capable of multi-carrier and/or CA operation, set the IAB-MT to transmit according to the applicable test configuration and corresponding power setting specified in clause 4.7.2 and 4.8 using the corresponding test models on all carriers configured. + +For IAB node declared to be capable of Simultaneous transmission between IAB-DU and IAB-MT(D.IAB-3), set IAB-DU and IAB-MT to transmit maximum power within maximum power imbalance declared by manufacturer according to the applicable test configuration and test models specified in clauses 4.7.2 and 4.8 with both IAB-MT and IAB-DU configured. + +- 10) Generate the interfering signal for *IAB node* via the CLTA. The CLTA is fed with a power level equal to declared $P_{\text{rated,t,TRP}}$ , divided over all the supported polarizations, from the same signal generator source: + +For IAB-DU: + +- using test model as defined in clause 4.9.2.2 for IAB-DU, at a centre frequency offset according to the conditions in table 9.8.2-1 in TS 38.174 [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. + +For IAB-MT: + +- using test model as defined in clause 4.9.2.3 for IAB-MT, at a centre frequency offset according to the conditions in table 9.8.2-1 in TS 38.174 [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. + +- 11) Adjust the interfering signal level at the CLTA conducted input(s) as defined in: + +- transmitter intermodulation table 9.8.2-1 in TS 38.174 [2]. + +- 12) If the interferer signal is applicable according to clause 4.7, perform the unwanted emission tests specified in clauses 6.7.3 (OTA ACLR) and 6.7.4 (OTA OBUE) for all third and fifth order intermodulation products which appear in the frequency ranges defined in clauses 6.7.3 and 6.7.4 (Note 2). The width of the intermodulation products shall be taken into account. + +- 13) If the interferer signal is applicable according to clause 4.7, perform the Transmitter spurious emissions test as specified in clause 6.7.5 (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.5 (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: + +- transmitter intermodulation table 9.8.2-1 in TS 38.174 [2]. + +- 16) Repeat the test for the remaining interfering signals defined in clause 4.7 for requirements 6.7.3 (OTA ACLR), 6.7.4 (OTA OBUE) and 6.7.5 (OTA spurious emission), except OTA co-location spurious emission. + +In addition, for *multi-band RIB*, the following steps shall apply: + +- 17) 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. + +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 wanted signal RF bandwidth or channel bandwidth in case of single carrier, or sub-block bandwidth and $BW_{F2}$ represents the interfering signal channel bandwidth. + +NOTE 2: During the conformance test the interferer 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 requirements + +### 6.8.5.1 Requirement for IAB type 1-O + +The transmitter intermodulation level shall not exceed the TRP unwanted emission limits specified for OTA transmitter spurious emission in clause 6.7.5 (except co-location with other base stations), OTA out-of-band emissions in clause 6.7.4 and OTA ACLR in clause 6.7.3 in the presence of a wanted signal and an interfering signal, defined in table 6.8.5.1-1. + +The requirement is applicable outside the *IAB RF Bandwidth edges*. The interfering signal offset is defined relative to the *IAB 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 RIBs supporting operation in multiple *operating bands*, the requirement shall apply relative to the *IAB RF Bandwidth edges* of each *operating band*. In case the inter RF Bandwidth gap is less than $3 * BW_{\text{Channel}}$ MHz (where $BW_{\text{Channel}}$ is the minimal *IAB channel bandwidth* of the band), the requirement in the gap shall apply only for interfering signal offsets where the interfering signal falls completely within the inter RF Bandwidth gap. + +**Table 6.8.5.1-1: Interfering and wanted signals for the OTA transmitter intermodulation requirement** + +| Parameter | Value | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Wanted signal | NR single or multi-carrier, or multiple intra-band contiguously or non-contiguously aggregated carriers | +| Interfering signal type | NR signal the minimum IAB-DU channel bandwidth ( $BW_{\text{Channel}}$ ) or IAB-MT channel bandwidth ( $BW_{\text{Channel}}$ ) with 15 kHz SCS of the band defined in clause 5.3.5 | +| Interfering signal level | The interfering signal level is the same power level as the IAB ( $P_{\text{rated,t,TRP}}$ ) fed into a co-location reference antenna .. | +| Interfering signal centre frequency offset from the lower (upper) edge of the wanted signal or edge of sub-block inside a gap | , for n=1, 2 and 3 | +| NOTE 1: Interfering signal positions that are partially or completely outside of any downlink operating band of the IAB 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: In Japan, note 1 is not applied in Band n77, n78, n79. | | +| NOTE 3: The $P_{\text{rated,t,TRP}}$ is split between supported polarizations at the CLTA input ports. | | + +## 7 Radiated 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. IAB configurations for the tests are defined in clause 4.5. + +Unless otherwise stated, the following arrangements apply for radiated receiver characteristics requirements in clause 7: + +- Requirements apply during the IAB receive period. +- Requirements shall be met for any transmitter setting. +- Throughput requirements defined for the radiated receiver characteristics do not assume HARQ retransmissions. +- When IAB is configured to receive multiple carriers, all the throughput requirements are applicable for each received carrier. +- For ACS, blocking and intermodulation characteristics, the negative offsets of the interfering signal apply relative to the lower *IAB RF Bandwidth* edge or *sub-block* edge inside a *sub-block gap*, and the positive offsets of the interfering signal apply relative to the upper *IAB RF Bandwidth* edge or *sub-block* edge inside a *sub-block gap*. + +NOTE 1: In normal operating condition the IAB in TDD operation is configured to TX OFF power during *receive period*. + +Each requirement, except OTA receiver spurious emissions, shall be met over the RoAoA specified. + +For FR1 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)} \text{ 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)} \text{ 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)}$$ + +For FR2-1 requirements which are to be met over the *OTA REFSENS RoAoA* absolute requirement values are offset by the following term: + +$$\Delta_{\text{FR2\_REFSENS}} = -3 \text{ dB for the reference direction}$$ + +and + +$$\Delta_{\text{FR2\_REFSENS}} = 0 \text{ dB for all other directions}$$ + +## 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 a IAB *type 1-H* and IAB *type 1-O* receiver. + +The *IAB type 1-H* and IAB *type 1-O* 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 BS settings is the active *sensitivity RoAoA*. + +If the IAB is capable of redirecting the *receiver target* related to the OSDD then the OSDD shall include: + +- IAB *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 BS. + +- Five declared *sensitivity RoAoA* comprising the conformance testing directions as detailed in TR 37. 941 [29]. +- 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. + +If the *IAB* is not capable of redirecting the *receiver target* related to the OSDD, then the OSDD includes only: + +- IAB *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 3: For *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 *IAB-DU type 1-H* and *IAB-DU type 1-O* is in TS 38.174 [2], clause 10.2.1. + +The minimum requirement for *IAB-MT type 1-H* and *IAB-MT type 1-O* is in TS 38.174 [2], clause 10.2.2. + +## 7.2.3 Test purpose + +The test purpose is to verify that the BS can meet the 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 B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +Directions to be tested: + +- receiver target reference direction (D.31), +- conformance test directions (D.33). + +### 7.2.4.2 Procedure + +- 1) Place the BS with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.2.1. +- 2) Align the manufacturer declared coordinate system orientation of the 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 BS under test. +- 5) Start the signal generator for the wanted signal to transmit: + - The test signal as specified in clause 7.2.5. + +- 6) Set the test signal mean power so the calibrated radiated power at the BS Antenna Array coordinate system reference point is as specified in clause 7.2.5. +- 7) Measure the throughput according to annex A.1 for each supported polarization. +- 8) Repeat steps 3 to 9 for all OSDD(s) declared for the BS (D.23), and supported polarizations. + +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 carriers activated in the other band. + +## 7.2.5 Test requirements + +### 7.2.5.1 General + +The minimum EIS level is a declared figure (D.27, D.28) for each OSDD (D.23). The test requirement is calculated from the declared value offset by the EIS Test Tolerance specified in clause 4.1. + +### 7.2.5.2 Test requirements for IAB-DU type 1-H and IAB-DU type 1-O + +For each measured carrier, the throughput measured in step 7 of clause 7.2.4.2 shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.1 with parameters specified in table 7.2.5.2-1. + +**Table 7.2.5.2-1: EIS levels** + +| IAB-DU channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel (annex A.1) | OTA sensitivity level, EIS (dBm) | | | +|-------------------------------------------------|---------------------------|-------------------------------------------|-----------------------------------|-----------------------------------|-----------------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6.0$ GHz | +| 10, 15 | 15 | G-FR1-A1-1 | Declared minimum EIS

+ 1.3 | Declared minimum EIS

+ 1.4 | Declared minimum EIS

+ 1.6 | +| 10, 15 | 30 | G-FR1-A1-2 | | | | +| 10, 15 | 60 | G-FR1-A1-3 | | | | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 | | | | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | | | | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | | | | + +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 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 IAB-DU channel bandwidth. + +### 7.2.5.3 Test requirements for IAB-MT type 1-H and IAB-MT type 1-O + +For each measured carrier, the throughput measured in step 7 of clause 7.2.4.2 shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.1 with parameters specified in table 7.2.5.2-1. + +**Table 7.2.5.3-1: EIS levels** + +| IAB-MT channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel (annex A.1) | OTA sensitivity level, EIS (dBm) | | | +|-------------------------------------------------|---------------------------|-------------------------------------------|----------------------------------|------------------------------|------------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6.0$ GHz | +| 10, 15 | 30 | G-FR1-A1-22 (Note 1) | | | | +| 10, 15 | 60 | G-FR1-A1-23 (Note 1) | | | | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-25 (Note 1) | Declared minimum EIS + 1.3 | Declared minimum EIS + 1.4 | Declared minimum EIS + 1.6 | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-26 (Note 1) | | | | + +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 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 IAB-MT channel bandwidth. + +## 7.3 OTA reference sensitivity level + +### 7.3.1 Definition and applicability + +The OTA REFSENS requirement is a directional requirement and is intended to ensure the minimum OTA reference sensitivity level for a declared *OTA REFSENS RoAoA*. The OTA reference sensitivity power level $EIS_{REFSENS}$ is the minimum mean power received at the RIB at which a reference performance requirement shall be met for a specified reference measurement channel. + +The OTA REFSENS EIS level declaration shall apply to each supported polarization, under the assumption of *polarization match*. + +### 7.3.2 Minimum requirement + +For IAB-DU type 1-O the minimum requirement is in TS 38.174 [2], clause 10.3.2.1. + +For IAB-DU type 2-O the minimum requirement is in TS 38.174 [2], clause 10.3.3.2. + +For IAB-MT type 1-O the minimum requirement is in TS 38.174 [2], clause 10.3.3.2. + +For IAB-MT type 2-O the minimum requirement is in TS 38.174 [2], clause 10.3.3.3. + +### 7.3.3 Test Purpose + +The test purpose is to verify that the IAB can meet the 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 B.2. + +RF channels to be tested for single carrier: + +- B, M and T; see clause 4.9.1. + +Directions to be tested: + +- OTA REFSENS receiver target reference direction (D.54), + +- OTA REFSENS conformance test directions (D.55). + +### 7.3.4.2 Procedure + +- 1) Place the IAB with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.2.1. +- 2) Align the manufacturer declared coordinate system orientation of the IAB with the test system. +- 3) Align the IAB 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 IAB under test. +- 5) Start the signal generator for the wanted signal to transmit: + - The test signal as specified in clause 7.3.5. +- 6) Set the test signal mean power so the calibrated radiated power at the BS Antenna Array coordinate system reference point is as specified in clause 7.3.5. +- 7) Measure the throughput according to annex A.1 for each supported polarization. +- 9) Repeat steps 3 to 9 for all OTA REFSENS conformance test directions of the IAB (D.55), and supported polarizations. + +For multi-band capable FR1 IAB 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 requirements + +### 7.3.5.1 General + +The FR1 EISREFSENS level is the conducted REFSENS requirement value offset by $\Delta_{\text{OTAREFSENS}}$ . The test requirement is calculated from the EISREFSENS level offset by the EISREFSENS Test Tolerance specified in clause 4.1. + +### 7.3.5.2 IAB-DU OTA reference sensitivity level + +#### 7.3.5.2.1 Test requirements for IAB-DU type 1-O + +For each measured carrier, the throughput measured in step 7 of clause 7.3.4.2 shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.1 with parameters specified in tables 7.3.5.2.1-1 to 7.3.5.2.1-3. + +**Table 7.3.5.2.1-1: Wide Area IAB-DU EISREFSENS levels** + +| IAB-DU channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel (annex A.1) | OTA reference sensitivity level, EIS REFSENS (dBm) | | | +|-------------------------------------------------|---------------------------|-------------------------------------------|---------------------------------------------------------------|------------------------------------------|------------------------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6.0$ GHz | +| 10, 15 | 15 | G-FR1-A1-1 | -100.4 –
$\Delta_{\text{OTAREFSENS}}$ | -100.3 –
$\Delta_{\text{OTAREFSENS}}$ | -100.1 –
$\Delta_{\text{OTAREFSENS}}$ | +| 10, 15 | 30 | G-FR1-A1-2 | -100.5 –
$\Delta_{\text{OTAREFSENS}}$ | -100.4 –
$\Delta_{\text{OTAREFSENS}}$ | -100.2 –
$\Delta_{\text{OTAREFSENS}}$ | +| 10, 15 | 60 | G-FR1-A1-3 | -97.6 –
$\Delta_{\text{OTAREFSENS}}$ | -97.5 –
$\Delta_{\text{OTAREFSENS}}$ | -97.3 –
$\Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 | -94 – $\Delta_{\text{OTAREFSENS}}$ | -93.9 –
$\Delta_{\text{OTAREFSENS}}$ | -93.7 –
$\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}}$ | -94 – $\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}}$ | -94.1 –
$\Delta_{\text{OTAREFSENS}}$ | + +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 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 IAB-DU channel bandwidth. + +**Table 7.3.5.2-2: Medium Range IAB-DU EISREFSENS levels** + +| IAB-DU channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel (annex A.1) | EIS REFSENS (dBm) | | | +|-------------------------------------------------|---------------------------|-------------------------------------------|-----------------------------------------|-----------------------------------------|-----------------------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6.0$ GHz | +| 10, 15 | 15 | G-FR1-A1-1 | -95.4 –
$\Delta_{\text{OTAREFSENS}}$ | -95.3 –
$\Delta_{\text{OTAREFSENS}}$ | -95.1 –
$\Delta_{\text{OTAREFSENS}}$ | +| 10, 15 | 30 | G-FR1-A1-2 | -95.5 –
$\Delta_{\text{OTAREFSENS}}$ | -95.4 –
$\Delta_{\text{OTAREFSENS}}$ | -95.2 –
$\Delta_{\text{OTAREFSENS}}$ | +| 10, 15 | 60 | G-FR1-A1-3 | -92.6 –
$\Delta_{\text{OTAREFSENS}}$ | -92.5 –
$\Delta_{\text{OTAREFSENS}}$ | -92.3 –
$\Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 | -89 – $\Delta_{\text{OTAREFSENS}}$ | -88.9 –
$\Delta_{\text{OTAREFSENS}}$ | -88.7 –
$\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}}$ | -89 – $\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}}$ | -89.1 –
$\Delta_{\text{OTAREFSENS}}$ | + +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 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 IAB-DU channel bandwidth. + +**Table 7.3.5.2.1-3: Local Area IAB-DU EISREFSENS levels** + +| IAB-DU channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel (annex A.1) | OTA reference sensitivity level, EIS REFSENS (dBm) | | | +|-------------------------------------------------|---------------------------|-------------------------------------------|---------------------------------------------------------------|-----------------------------------------|-----------------------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6.0$ GHz | +| 10, 15 | 15 | G-FR1-A1-1 | -92.4 –
$\Delta_{\text{OTAREFSENS}}$ | -92.3 –
$\Delta_{\text{OTAREFSENS}}$ | -92.1 –
$\Delta_{\text{OTAREFSENS}}$ | +| 10, 15 | 30 | G-FR1-A1-2 | -92.5 –
$\Delta_{\text{OTAREFSENS}}$ | -92.4 –
$\Delta_{\text{OTAREFSENS}}$ | -92.2 –
$\Delta_{\text{OTAREFSENS}}$ | +| 10, 15 | 60 | G-FR1-A1-3 | -89.6 –
$\Delta_{\text{OTAREFSENS}}$ | -89.5 –
$\Delta_{\text{OTAREFSENS}}$ | -89.3 –
$\Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50 | 15 | G-FR1-A1-4 | -86 – $\Delta_{\text{OTAREFSENS}}$ | -85.9 –
$\Delta_{\text{OTAREFSENS}}$ | -85.7 –
$\Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-5 | -86.3 –
$\Delta_{\text{OTAREFSENS}}$ | -86.2 –
$\Delta_{\text{OTAREFSENS}}$ | -86 – $\Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -86.4 –
$\Delta_{\text{OTAREFSENS}}$ | -86.3 –
$\Delta_{\text{OTAREFSENS}}$ | -86.1 –
$\Delta_{\text{OTAREFSENS}}$ | + +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 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 IAB-DU channel bandwidth. + +### 7.3.5.2.2 Test requirements for IAB-DU type 2-O + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.1 when the OTA test signal is at the corresponding EISREFSENS level and arrives from any direction within the OTA REFSENS RoAoA. + +EISREFSENS levels are derived from a single declared basis level EISREFSENS\_50M, which is based on a reference measurement channel with 50 MHz IAB-DU channel bandwidth. EISREFSENS\_50M itself is not a requirement and although it is based on a reference measurement channel with 50 MHz IAB channel bandwidth it does not imply that IAB-DU has to support 50 MHz IAB-DU channel bandwidth. + +For Wide Area IAB-DU, EISREFSENS\_50M is an integer value in the range -96 to -119 dBm. The specific value is declared by the vendor. + +For Medium Range IAB-DU, EISREFSENS\_50M is an integer value in the range -91 to -114 dBm. The specific value is declared by the vendor. + +For Local Area IAB-DU, EISREFSENS\_50M is an integer value in the range -86 to -109 dBm. The specific value is declared by the vendor. + +**Table 7.3.5.2.2-1 FR2-1 OTA reference sensitivity requirement** + +| IAB-DU channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel (annex A.1) | OTA reference sensitivity level, EIS REFSENS (dBm) | +|--------------------------------|---------------------------|-------------------------------------------|-----------------------------------------------------------------------| +| 50, 100, 200 | 60 | G-FR2-A1-1 | EIS REFSENS_50M + 2.4 + $\Delta_{\text{FR2\_REFSENS}}$ | +| 50 | 120 | G-FR2-A1-2 | EIS REFSENS_50M + 2.4 + $\Delta_{\text{FR2\_REFSENS}}$ | +| 100, 200, 400 | 120 | G-FR2-A1-3 | EIS REFSENS_50M + 3 + 2.4 + $\Delta_{\text{FR2\_REFSENS}}$ | + +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 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 IAB-DU channel bandwidth. + +NOTE 2: The declared EISREFSENS\_50M shall be within the range specified above. + +### 7.3.5.3 IAB-MT OTA reference sensitivity level + +#### 7.3.5.3.1 Test requirement for IAB-MT type 1-O + +For each measured carrier, the throughput measured in step 7 of clause 7.3.4.2 shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.1 with parameters specified in tables 7.3.5.3.1-1 to 7.3.5.3.12. + +**Table 7.3.5.3.1-1: Wide Area IAB-MT type 1-O reference sensitivity levels** + +| IAB-MT channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | OTA reference sensitivity level, EIS REFSENS (dBm) | | | +|-------------------------------------------------|---------------------------|-------------------------------|---------------------------------------------------------------|------------------------------------------|------------------------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6.0$ GHz | +| 10, 15 | 30 | G-FR1-A1-22 | -100.7 -
$\Delta_{\text{OTAREFSENS}}$ | -100.6 -
$\Delta_{\text{OTAREFSENS}}$ | -100.4 -
$\Delta_{\text{OTAREFSENS}}$ | +| 10, 15 | 60 | G-FR1-A1-23 | -97.7 -
$\Delta_{\text{OTAREFSENS}}$ | -97.6 -
$\Delta_{\text{OTAREFSENS}}$ | -97.4 -
$\Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-25 | -94.1 -
$\Delta_{\text{OTAREFSENS}}$ | -94.0 -
$\Delta_{\text{OTAREFSENS}}$ | -93.8 -
$\Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-26 | -94.3 -
$\Delta_{\text{OTAREFSENS}}$ | -94.2 -
$\Delta_{\text{OTAREFSENS}}$ | -94.0 -
$\Delta_{\text{OTAREFSENS}}$ | + +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 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 IAB-MT channel bandwidth. + +**Table 7.3.5.3.1-2: Local Area IAB-MT type 1-O reference sensitivity levels** + +| IAB-MT channel bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | OTA reference sensitivity level, EIS REFSENS (dBm) | | | +|-------------------------------------------------|---------------------------|-------------------------------|---------------------------------------------------------------|-----------------------------------------|-----------------------------------------| +| | | | $f \leq 3.0$ GHz | $3.0$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6.0$ GHz | +| 10, 15 | 30 | G-FR1-A1-22 | -92.7 -
$\Delta_{\text{OTAREFSENS}}$ | -92.6 -
$\Delta_{\text{OTAREFSENS}}$ | -92.4 -
$\Delta_{\text{OTAREFSENS}}$ | +| 10, 15 | 60 | G-FR1-A1-23 | -89.7 -
$\Delta_{\text{OTAREFSENS}}$ | -89.6 -
$\Delta_{\text{OTAREFSENS}}$ | -89.4 -
$\Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 30 | G-FR1-A1-25 | -86.1 -
$\Delta_{\text{OTAREFSENS}}$ | -86.0 -
$\Delta_{\text{OTAREFSENS}}$ | -85.8 -
$\Delta_{\text{OTAREFSENS}}$ | +| 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-26 | -86.3 -
$\Delta_{\text{OTAREFSENS}}$ | -86.2 -
$\Delta_{\text{OTAREFSENS}}$ | -86.0 -
$\Delta_{\text{OTAREFSENS}}$ | + +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 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 IAB-MT channel bandwidth. + +#### 7.3.5.3.2 Minimum requirement for IAB-MT type 2-O + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in the corresponding table and annex A.1 when the OTA test signal is at the corresponding EISREFSENS level and arrives from any direction within the OTA REFSENS RoAoA. + +EISREFSENS levels are derived from a single declared basis level EISREFSENS\_50M, which is based on a reference measurement channel with 50 MHz IAB-MT channel bandwidth. EISREFSENS\_50M itself is not a requirement and although it is based on a reference measurement channel with 50 MHz IAB-MT channel bandwidth it does not imply that IAB-MT has to support 50 MHz IAB-MT channel bandwidth. + +For Wide Area IAB-MT, EISREFSENS\_50M is an integer value in the range -96 to -119 dBm. The specific value is declared by the vendor. + +For Local Area IAB-MT, $EIS_{REFSENS\_50M}$ is an integer value in the range -86 to -114 dBm. The specific value is declared by the vendor. + +**Table 7.3.5.3.2-1: FR2-1 OTA reference sensitivity requirement** + +| IAB-MT channel Bandwidth (MHz) | Sub-carrier spacing (kHz) | Reference measurement channel | OTA reference sensitivity level, EIS_{REFSENS} (dBm) | +|----------------------------------------------|----------------------------------|--------------------------------------|--------------------------------------------------------------------------| +| 50, 100, 200 | 60 | G-FR2-A1-21 | $EIS_{REFSENS\_50M} + 3.3 + \Delta_{FR2\_REFSENS}$ | +| 50 | 120 | G-FR2-A1-22 | $EIS_{REFSENS\_50M} + 3.3 + \Delta_{FR2\_REFSENS}$ | +| 100, 200, 400 | 120 | G-FR2-A1-23 | $EIS_{REFSENS\_50M} + 3.3 + 3 + \Delta_{FR2\_REFSENS}$ | + +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 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 *IAB-MT channel bandwidth*. + +NOTE 2: The declared $EIS_{REFSENS\_50M}$ shall be within the range specified above. + +## 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 *IAB-DU channel bandwidth*. + +The requirement shall apply 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 *IAB-DU type I-O*, the minimum requirement is in TS 38.174 [2], clause 10.4.1. + +### 7.4.3 Test purpose + +The test purpose is to verify that at the IAB-DU receiver dynamic range, the relative throughput shall fulfil the specified limit. + +### 7.4.4 Method of test + +#### 7.4.4.1 Initial conditions + +Test environment: Normal: see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +Directions to be tested: OTA REFSENS receiver target reference direction (D.54). + +#### 7.4.4.2 Procedure + +- 1) Place the IAB-DU with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.2.2. + +- 2) Align the manufacturer declared coordinate system orientation of the IAN-DU with the test system. +- 3) Align the IAB-DU 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 IAB-DU under test. +- 5) Set the test signal mean power so that the calibrated radiated power at the IAB-DU Antenna Array coordinate system reference point is as follows: + - a) Set the signal generator for the wanted signal to transmit as specified in table 7.4.5.2-1 to 7.4.5.2-3. + - 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.2-1 to 7.4.5.2-3. +- 6) Measure the throughput according to annex A.2 for each supported polarization. + +For *multi-band RIB(s)* 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.4.5 Test requirement + +### 7.4.5.1 General + +The test requirement is calculated from the OTA wanted signal mean power level offset by the OTA dynamic range Test Tolerance specified in clause 4.1. + +### 7.4.5.2 Test requirements for *IAB-DU type 1-O* + +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 annex A.2 with parameters specified in tables 7.4.5.2-1 to 7.4.5.2-3. + +Table 7.4.5.2-1: Wide Area IAB-DU dynamic range + +| IAB-DU channel bandwidth (MHz) | Subcarrier | Reference | Wanted signal mean power (dBm) | Interfering | Type of | +|--------------------------------|---------------|---------------------------------|---------------------------------|------------------------------------------------|--------------------| +| | spacing (kHz) | measurement channel (annex A.2) | | signal mean power (dBm) / BW Config | interfering signal | +| 10 | 15 | G-FR1-A2-1 | -70.4 – Δ OTAREFSENS | -79.3 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-2 | -71.1 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-3 | -68.1 – Δ OTAREFSENS | | | +| 15 | 15 | G-FR1-A2-1 | -70.4 – Δ OTAREFSENS | -77.5 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-2 | -71.1 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-3 | -68.1 – Δ OTAREFSENS | | | +| 20 | 15 | G-FR1-A2-4 | -64.2 – Δ OTAREFSENS | -76.2 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -64.5 – Δ OTAREFSENS | | | +| 25 | 15 | G-FR1-A2-4 | -64.2 – Δ OTAREFSENS | -75.2 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -64.5 – Δ OTAREFSENS | | | +| 30 | 15 | G-FR1-A2-4 | -64.2 – Δ OTAREFSENS | -74.4 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -64.5 – Δ OTAREFSENS | | | +| 35 | 15 | G-FR1-A2-4 | -64.2 – Δ OTAREFSENS | -73.7 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -64.5 – Δ OTAREFSENS | | | +| 40 | 15 | G-FR1-A2-4 | -64.2 – Δ OTAREFSENS | -73.1 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -64.5 – Δ OTAREFSENS | | | +| 45 | 15 | G-FR1-A2-4 | -64.2 – Δ OTAREFSENS | -72.6 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -64.5 – Δ OTAREFSENS | | | +| 50 | 15 | G-FR1-A2-4 | -64.2 – Δ OTAREFSENS | -72.1 – Δ OTAREFSENS | AWGN | +| | 30 | G-FR1-A2-5 | -64.2 – Δ OTAREFSENS | | | +| | 60 | G-FR1-A2-6 | -64.5 – Δ OTAREFSENS | | | +| 60 | 30 | G-FR1-A2-5 | -64.2 – Δ OTAREFSENS | -71.3 – Δ OTAREFSENS | AWGN | +| | 60 | G-FR1-A2-6 | -64.5 – Δ OTAREFSENS | | | +| 70 | 30 | G-FR1-A2-5 | -64.2 – Δ OTAREFSENS | -70.7 – Δ OTAREFSENS | AWGN | +| | 60 | G-FR1-A2-6 | -64.5 – Δ OTAREFSENS | | | +| 80 | 30 | G-FR1-A2-5 | -64.2 – Δ OTAREFSENS | -70.1 – Δ OTAREFSENS | AWGN | +| | 60 | G-FR1-A2-6 | -64.5 – Δ OTAREFSENS | | | +| 90 | 30 | G-FR1-A2-5 | -64.2 – Δ OTAREFSENS | -69.5 – Δ OTAREFSENS | AWGN | +| | 60 | G-FR1-A2-6 | -64.5 – Δ OTAREFSENS | | | +| 100 | 30 | G-FR1-A2-5 | -64.2 – Δ OTAREFSENS | -69.1 – Δ OTAREFSENS | AWGN | +| | 60 | G-FR1-A2-6 | -64.5 – Δ 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 IAB-DU channel bandwidth. + +**Table 7.4.5.2-2: Medium Range IAB-DU dynamic range** + +| IAB-DU
channel
bandwidth (MHz) | Subcarrier
spacing (kHz) | Reference
measurement
channel
(annex A.2) | Wanted signal mean power (dBm) | Interfering
signal mean
power (dBm) /
BWConfig | Type of
interfering signal | +|-----------------------------------------------|-------------------------------------|--------------------------------------------------------------|---------------------------------------|------------------------------------------------------------------------------|---------------------------------------| +| 10 | 15 | G-FR1-A2-1 | $-65.4 - \Delta_{\text{OTAREFSENS}}$ | $-74.3 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | $-66.1 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-3 | $-63.1 - \Delta_{\text{OTAREFSENS}}$ | | | +| 15 | 15 | G-FR1-A2-1 | $-65.4 - \Delta_{\text{OTAREFSENS}}$ | $-72.5 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-2 | $-66.1 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-3 | $-63.1 - \Delta_{\text{OTAREFSENS}}$ | | | +| 20 | 15 | G-FR1-A2-4 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-71.2 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 25 | 15 | G-FR1-A2-4 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-70.2 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 30 | 15 | G-FR1-A2-4 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-69.4 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 35 | 15 | G-FR1-A2-4 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-68.7 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 40 | 15 | G-FR1-A2-4 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-68.1 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 45 | 15 | G-FR1-A2-4 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-67.6 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 50 | 15 | G-FR1-A2-4 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-67.1 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | | | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 60 | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-66.3 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 70 | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-65.7 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 80 | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-65.1 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 90 | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.5 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-59.5 - \Delta_{\text{OTAREFSENS}}$ | | | +| 100 | 30 | G-FR1-A2-5 | $-59.2 - \Delta_{\text{OTAREFSENS}}$ | $-64.1 - \Delta_{\text{OTAREFSENS}}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-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 IAB-DU channel bandwidth. + +Table 7.4.5.2-3: Local Area IAB-DU dynamic range + +| IAB-DU channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel (annex A.2) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) / $BW_{Config}$ | Type of interfering signal | +|--------------------------------|--------------------------|-------------------------------------------|--------------------------------|-----------------------------------------------------|----------------------------| +| 10 | 15 | G-FR1-A2-1 | $-62.4 - \Delta_{OTAREFSENS}$ | $-71.3 - \Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-2 | $-64.1 - \Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-3 | $-60.1 - \Delta_{OTAREFSENS}$ | | | +| 15 | 15 | G-FR1-A2-1 | $-62.4 - \Delta_{OTAREFSENS}$ | $-69.5 - \Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-2 | $-64.1 - \Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-3 | $-60.1 - \Delta_{OTAREFSENS}$ | | | +| 20 | 15 | G-FR1-A2-4 | $-56.2 - \Delta_{OTAREFSENS}$ | $-68.2 - \Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{OTAREFSENS}$ | | | +| 25 | 15 | G-FR1-A2-4 | $-56.2 - \Delta_{OTAREFSENS}$ | $-67.2 - \Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{OTAREFSENS}$ | | | +| 30 | 15 | G-FR1-A2-4 | $-56.2 - \Delta_{OTAREFSENS}$ | $-66.4 - \Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{OTAREFSENS}$ | | | +| 35 | 15 | G-FR1-A2-4 | $-56.2 - \Delta_{OTAREFSENS}$ | $-65.7 - \Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{OTAREFSENS}$ | | | +| 40 | 15 | G-FR1-A2-4 | $-56.2 - \Delta_{OTAREFSENS}$ | $-65.1 - \Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{OTAREFSENS}$ | | | +| 45 | 15 | G-FR1-A2-4 | $-56.2 - \Delta_{OTAREFSENS}$ | $-64.6 - \Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{OTAREFSENS}$ | | | +| 50 | 15 | G-FR1-A2-4 | $-56.2 - \Delta_{OTAREFSENS}$ | $-64.1 - \Delta_{OTAREFSENS}$ | AWGN | +| | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{OTAREFSENS}$ | | | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{OTAREFSENS}$ | | | +| 60 | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{OTAREFSENS}$ | $-63.3 - \Delta_{OTAREFSENS}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{OTAREFSENS}$ | | | +| 70 | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{OTAREFSENS}$ | $-62.7 - \Delta_{OTAREFSENS}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{OTAREFSENS}$ | | | +| 80 | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{OTAREFSENS}$ | $-62.1 - \Delta_{OTAREFSENS}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{OTAREFSENS}$ | | | +| 90 | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{OTAREFSENS}$ | $-61.5 - \Delta_{OTAREFSENS}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{OTAREFSENS}$ | | | +| 100 | 30 | G-FR1-A2-5 | $-56.2 - \Delta_{OTAREFSENS}$ | $-61.1 - \Delta_{OTAREFSENS}$ | AWGN | +| | 60 | G-FR1-A2-6 | $-56.5 - \Delta_{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 IAB-DU channel bandwidth. + +## 7.5 OTA in-band selectivity and blocking + +### 7.5.1 OTA adjacent channel selectivity + +#### 7.5.1.1 Definition and applicability + +OTA Adjacent channel selectivity (ACS) is a measure of the receiver's ability to receive an OTA wanted signal at its assigned channel frequency in the presence of an OTA adjacent channel signal with a specified centre frequency offset of the interfering signal to the band edge of a victim system. The wanted and interfering signals apply to each supported polarization, under the assumption of polarization match. + +#### 7.5.1.2 Minimum requirement + +For *IAB-DU type 1-O*, the minimum requirements are in TS 38.174 [2], clause 10.5.1.2. + +For *IAB-DU type 2-O*, The minimum requirements are in TS 38.174 [2], clause 10.5.1.3. + +For *IAB-MT type 1-O*, The minimum requirements are in TS 38.174 [2], clause 10.5.1.5. + +For *IAB-MT type 2-O*, The minimum requirements are in TS 38.174 [2], clause 10.5.1.4. + +#### 7.5.1.3 Test purpose + +The test purpose is to verify the ability of the IAB receiver filter to suppress interfering signals in the channels adjacent to the wanted channel. + +#### 7.5.1.4 Method of test + +##### 7.5.1.4.1 Initial conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: + +- M; see clause 4.9.1. + +*IAB RF Bandwidth* edge position to be tested for multi-carrier and/or CA: + +- $M_{\text{RFBW}}$ in single-band operation, see clause 4.9.1; +- $B_{\text{RFBW\_T'RFBW}}$ and $B'_{\text{RFBW\_T'RFBW}}$ in multi-band operation, see clause 4.9.1. + +Directions to be tested: + +- For *IAB type 1-O*, receiver target reference direction (D.31), +- For *IAB type 2-O*, OTA REFSENS receiver target reference direction (D.54). + +##### 7.5.1.4.2 Procedure + +- 1) Place the IAB with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.2.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB with the test system. +- 3) Align the IAB with the test antenna in the declared direction to be tested. +- 4) Align the IAB so that the wanted signal and interferer signal is *polarization matched* with the test antenna(s). +- 5) Configure the beam peak direction for the transmitter according to the declared reference beam direction pair for the appropriate beam identifier. + +- 6) Set the test signal mean power so that the calibrated radiated power at the IAB Antenna Array coordinate system reference point is as follows: + - a) For *IAB-DU type 1-O*, set the signal generator for the wanted signal to transmit as specified in table 7.5.1.5.2-1. + For *IAB-DU type 2-O*, set the signal generator for the wanted signal to transmit as specified in Table 7.5.1.5.3-1. + For *IAB-MT type 1-O*, set the signal generator for the wanted signal to transmit as specified in table 7.5.1.5.4-1. + For *IAB-MT type 2-O*, set the signal generator for the wanted signal to transmit as specified in table 7.5.1.5.5-1. + For simultaneous operation tests for IAB type 1-O, set the signal generator for the wanted signal of IAB-DU type 1-O to transmit as specified in table 7.5.1.5.2-1 and for the wanted signal of IAB-MT type 1-O to transmit in table 7.5.1.5.4-1. For simultaneous operation tests for IAB type 2-O, set the signal generator for the wanted signal of IAB-DU type 2-O to transmit as specified in table 7.5.1.5.3-1 and for the wanted signal of IAB-MT type 2-O to transmit in table 7.5.1.5.5-1. + - b) For IAB-DU type 1-O, set the signal generator for the interfering signal at the adjacent channel frequency of the wanted signal to transmit as specified in table 7.5.1.5.2-2. + For IAB-DU type 2-O, set the signal generator for the interfering signal at the adjacent channel frequency of the wanted signal to transmit as specified in table 7.5.1.5.3-2. + For *IAB-MT type 1-O*, set the signal generator for the interfering signal at the adjacent channel frequency of the wanted signal to transmit as specified in table 7.5.1.5.4-2. + For *IAB-MT type 2-O*, set the signal generator for the interfering signal at the adjacent channel frequency of the wanted signal to transmit as specified in table 7.5.1.5.5-2. + For simultaneous operation tests for IAB type 1-O, set the signal generator for the interfering signal at the adjacent channel frequency of the wanted signal to transmit as specified in table 7.5.1.5.4-2. + For simultaneous operation tests for IAB type 2-O, set the signal generator for the interfering signal at the adjacent channel frequency of the wanted signal to transmit as specified in table 7.5.1.5.5-2. +- 7) Measure throughput according to annex A.1 for each supported polarization, for multi-carrier and/or CA operation the throughput shall be measured for relevant carriers specified by the test configuration specified in clauses 4.7.2 and 4.8. + +For *multi-band RIB(s)* 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.5.1.5 Test requirement + +### 7.5.1.5.1 General + +The test requirement is calculated from the OTA wanted signal mean power level offset by the OTA ACS Test Tolerance specified in annex C. + +### 7.5.1.5.2 Test requirements for *IAB-DU type 1-O* + +The requirement shall apply at the RIB when the AoA of the incident wave of a received signal and the interfering signal are from the same direction, and 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*. + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel. + +For FR1, the OTA wanted and the interfering signal are specified in table 7.5.1.5.2-1 and table 7.5.1.5.2-2 for ACS. The reference measurement channel for the OTA wanted signal is identified in clause 7.3.5.2 and is further specified in annex A.1. The characteristics of the interfering signal is further specified in annex H. + +The OTA ACS requirement is applicable outside the IAB RF Bandwidth or Radio Bandwidth. The OTA interfering signal offset is defined relative to the IAB RF Bandwidth edges or Radio Bandwidth edges. + +For RIBs supporting operation in *non-contiguous spectrum* within any operating band, the OTA ACS requirement shall apply in addition inside any sub-block gap, in case the sub-block gap size is at least as wide as the NR interfering signal in table 7.5.1.5.2-2. The OTA interfering signal offset is defined relative to the sub-block edges inside the sub-block gap. + +For *multi-band RIBs*, the OTA ACS requirement shall apply in addition inside any Inter RF Bandwidth gap, in case the Inter RF Bandwidth gap size is at least as wide as the NR interfering signal in table 7.5.1.5.2-2. The interfering signal offset is defined relative to the IAB RF Bandwidth edges inside the Inter RF Bandwidth gap. + +**Table 7.5.1.5.2-1: OTA ACS requirement for IAB-DU type 1-O** + +| IAB-DU channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) (Note 2) | | | Interfering signal mean power (dBm) | +|------------------------------------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------|-----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| | f \leq 3.0 GHz | 3.0 \text{ GHz} < f \leq 4.2 \text{ GHz} | 4.2 \text{ GHz} < f \leq 6.0 \text{ GHz} | | +| 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100
(Note 1) | $EIS_{\min SENS} + 6 \text{ dB}$ | | | Wide Area IAB: -52 – $\Delta_{\min SENS}$
Medium Range IAB: -47 – $\Delta_{\min SENS}$
Local Area IAB: -44 – $\Delta_{\min SENS}$ | + +NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the IAB-DU for that bandwidth. + +NOTE 2: $EIS_{\min SENS}$ depends on the *IAB-DU channel bandwidth* as specified in TS 38.104 [4], clause 10.2.1. + +**Table 7.5.1.5.2-2: OTA ACS interferer frequency offset for IAB-DU type 1-O** + +| IAB-DU channel bandwidth of the lowest/highest carrier received (MHz) | Interfering signal centre frequency offset from the lower/upper IABF Bandwidth edge or sub-block edge inside a sub-block gap (MHz) | Type of interfering signal | +|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------| +| 10 | $\pm 2.5075$ | 5 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 15 | $\pm 2.5125$ | | +| 20 | $\pm 2.5025$ | | +| 25 | $\pm 9.4675$ | 20 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 30 | $\pm 9.4725$ | | +| 35 | $\pm 9.4625$ | | +| 40 | $\pm 9.4675$ | | +| 45 | $\pm 9.4725$ | | +| 50 | $\pm 9.4625$ | | +| 60 | $\pm 9.4725$ | | +| 70 | $\pm 9.4675$ | | +| 80 | $\pm 9.4625$ | | +| 90 | $\pm 9.4725$ | | +| 100 | $\pm 9.4675$ | | + +### 7.5.1.5.3 Test requirements for IAB-DU type 2-O + +The requirement shall apply 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*. + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel. + +For FR2, the OTA wanted and the interfering signal are specified in table 7.5.1.5.3-1 and table 7.5.1.5.3-2 for ACS. The reference measurement channel for the OTA wanted signal is identified in clause 7.3.5.3 and is further specified in annex A.1. The characteristics of the interfering signal is further specified in annex H. + +The OTA ACS requirement is applicable outside the IAB RF Bandwidth. The OTA interfering signal offset is defined relative to the IAB RF Bandwidth edges. + +For RIBs supporting operation in *non-contiguous spectrum* within any *operating band*, the OTA ACS requirement shall apply in addition inside any sub-block gap, in case the sub-block gap size is at least as wide as the NR interfering signal in table 7.5.1.5.3-2. The OTA interfering signal offset is defined relative to the sub-block edges inside the sub-block gap. + +**Table 7.5.1.5.3-1: OTA ACS requirement for IAB-DU type 2-O** + +| IAB-DU channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | | Interfering signal mean power (dBm) | +|-----------------------------------------------------------------------|----------------------------------------|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| | 24.24 GHz < f ≤ 33.4 GHz | 37 GHz < f ≤ 52.6 GHz | | +| 50, 100, 200, 400 | EIS REFSENS + 6 dB (Note 3) | EIS REFSENS + 6 dB (Note 3) | EIS REFSENS_50M + 27.7 + Δ FR2_REFSENS (Note 1)
EIS REFSENS_50M + 26.7 + Δ FR2_REFSENS (Note 2) | + +NOTE 1: Applicable to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz. + +NOTE 2: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz. + +NOTE 3: EISREFSENS is specified in TS 38.174 [2], clause 10.3.3. + +**Table 7.5.1.5.3-2: OTA ACS interferer frequency offset for IAB-DU type 2-O** + +| IAB-DU channel bandwidth of the lowest/highest carrier received (MHz) | Interfering signal centre frequency offset from the lower/upper IAB Bandwidth edge or sub-block edge inside a sub-block gap (MHz) | Type of interfering signal | +|-----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------| +| 50 | ±24.29 | 50 MHz DFT-s-OFDM NR signal, 60 kHz SCS, 64 RBs | +| 100 | ±24.31 | | +| 200 | ±24.29 | | +| 400 | ±24.31 | | + +#### 7.5.1.5.4 Test requirements for IAB-MT type 1-O + +The requirement shall apply 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*. + +The throughput shall be ≥ 95% of the maximum throughput of the reference measurement channel. + +For FR1, the OTA wanted and the interfering signal are specified in table 7.5.1.5.4-1, table 7.5.1.5.4-2 for OTA ACS. The reference measurement channel for the OTA wanted signal is further specified in annex A.1. The characteristics of the interfering signal is further specified in annex H. + +The OTA ACS requirement is applicable outside the *IAB-MT RF Bandwidth* or *Radio Bandwidth*. The OTA interfering signal offset is defined relative to the *IAB-MT RF Bandwidth edges* or *Radio Bandwidth edges*. + +For RIBs supporting operation in *non-contiguous spectrum* within any *operating band*, the OTA ACS requirement shall apply in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least as wide as the NR interfering signal in table 7.5.1.5.4-2. The OTA interfering signal offset is defined relative to the *sub-block edges* inside the *sub-block gap*. + +For *multi-band RIBs*, the OTA ACS requirement shall apply in addition inside any *Inter RF Bandwidth gap*, in case the *Inter RF Bandwidth gap* size is at least as wide as the NR interfering signal in table 7.5.1.5.4-2. The interfering signal offset is defined relative to the *IAB-MT RF Bandwidth edges* inside the *Inter RF Bandwidth gap*. + +**Table 7.5.1.5.4-1: OTA ACS requirement for IAB-MT** + +| IAB-MT channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) (Note 2) | Interfering signal mean power (dBm) | +|-----------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-------------------------------------------------------------------------------------------| +| 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 (Note 1) | $EIS_{minSENS} + 6$ dB | Wide Area IAB-MT: $-52 - \Delta_{minSENS}$
Local Area IAB-MT: $-44 - \Delta_{minSENS}$ | +| NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the IAB-MT for that bandwidth | | | +| NOTE 2: $EIS_{minSENS}$ depends on the IAB-MT channel bandwidth | | | + +**Table 7.5.1.5.4-2: OTA ACS interferer frequency offset for IAB-MT type 1-O** + +| IAB-MT channel bandwidth of the lowest/highest carrier received (MHz) | Interfering signal centre frequency offset from the lower/upper IAB-MT RF Bandwidth edge or sub-block edge inside a sub-block gap (MHz) | Type of interfering signal | +|------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------| +| 10 | $\pm 2.5075$ | 5 MHz CP-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 15 | $\pm 2.5125$ | | +| 20 | $\pm 2.5025$ | | +| 25 | $\pm 9.4675$ | 20 MHz CP-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 30 | $\pm 9.4725$ | | +| 35 | $\pm 9.4625$ | | +| 40 | $\pm 9.4675$ | | +| 45 | $\pm 9.4725$ | | +| 50 | $\pm 9.4625$ | | +| 60 | $\pm 9.4725$ | | +| 70 | $\pm 9.4675$ | | +| 80 | $\pm 9.4625$ | | +| 90 | $\pm 9.4725$ | | +| 100 | $\pm 9.4675$ | | + +### 7.5.1.5.5 Test requirements for IAB-MT type 2-O + +The requirement shall apply 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 all supported polarizations, under the assumption of *polarization match*. + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel. + +For FR2, the OTA wanted and the interfering signal are specified in table 7.5.1.5.5-1 and table 7.5.1.5.5-2 for ACS. The reference measurement channel for the OTA wanted signal is further specified in annex A.1. The characteristics of the interfering signal is further specified in annex H. + +The OTA ACS requirement is applicable outside the *IAB-MT RF Bandwidth*. The OTA interfering signal offset is defined relative to the *IAB-MT RF Bandwidth edges*. + +For Wide Area IAB-MT, for RIBs supporting operation in *non-contiguous spectrum* within any *operating band*, the OTA ACS requirement shall apply in addition inside any sub-block gap, in case the sub-block gap size is at least as wide as the NR interfering signal in table 7.5.1.5.5-2. The OTA interfering signal offset is defined relative to the sub-block edges inside the sub-block gap. + +**Table 7.5.1.5.5-1: OTA ACS requirement for Wide Area and Local Area IAB MT** + +| IAB-MT channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | +|---------------------------------------------------------------------------------------------|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| 50, 100, 200, 400 | EIS REFSENS + 6 dB (Note 3) | EIS REFSENS_50M + 27.7 + Δ FR2_REFSENS (Note 1)
EIS REFSENS_50M + 26.7 + Δ FR2_REFSENS (Note 2) | +| NOTE 1: Applicable to bands defined within the frequency spectrum range of 24.25 – 33.4 GHz | | | +| NOTE 2: Applicable to bands defined within the frequency spectrum range of 37 – 52.6 GHz | | | +| NOTE 3: EIS REFSENS is given in subclause 7.3.5.3 | | | + +**Table 7.5.1.5.5-2: OTA ACS interferer frequency offset for IAB-MT type 2-O** + +| IAB-MT channel bandwidth of the lowest/highest carrier received (MHz) | Interfering signal centre frequency offset from the lower/upper IAB-MT RF Bandwidth edge or sub-block edge inside a sub-block gap (MHz) | Type of interfering signal | +|------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------| +| 50 | ±24.29 | 50 MHz CP-OFDM NR signal, 60 kHz SCS, 64 RBs | +| 100 | ±24.31 | | +| 200 | ±24.29 | | +| 400 | ±24.31 | | + +## 7.5.2 OTA in-band blocking + +### 7.5.2.1 Definition and applicability + +The OTA in-band blocking characteristics is a measure of the receiver's ability to receive a OTA wanted signal at its assigned channel in the presence of an unwanted OTA interferer, which is an NR signal for general blocking or an NR signal with one RB for narrowband blocking. + +### 7.5.2.2 Minimum requirement + +For IAB-DU type 1-O, the minimum requirements are in TS 38.174 [2], clause 10.5.2.2. + +For IAB-DU type 2-O, The minimum requirements are in TS 38.174 [2], clause 10.5.2.3. + +For IAB-MT type 1-O, The minimum requirements are in TS 38.174 [2], clause 10.5.2.5. + +For IAB-MT type 2-O, The minimum requirements are in TS 38.174 [2], clause 10.5.2.4 + +### 7.5.2.3 Test purpose + +The test purpose is to verify the ability of the IAB receiver to withstand high-levels of in-band interference from unwanted signals at specified frequency offsets without undue degradation of its sensitivity. + +### 7.5.2.4 Method of test + +#### 7.5.2.4.1 Initial conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +*IAB RF Bandwidth* edge position to be tested for multi-carrier and/or CA: + +- $M_{\text{RFBW}}$ in single-band operation, see clause 4.9.1; +- $B_{\text{RFBW\_T'RFBW}}$ and $B'_{\text{RFBW\_T'RFBW}}$ in multi-band operation, see clause 4.9.1. + +Directions to be tested: + +For *IAB type 1-O*: + +- receiver target reference direction for the minSENS OSDD (D.31), +- OTA REFSENS conformance test directions (D.55), + +For *IAB type 2-O*: + +- OTA REFSENS receiver target reference direction (D.54), +- OTA REFSENS conformance test directions (D.55). + +#### 7.5.2.4.2 Procedure + +- 1) Place the IAB with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.2.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB with the test system. +- 3) Align the IAB with the test antenna in the declared direction to be tested. +- 4) Align the IAB to that the wanted signal and interferer signal is *polarization matched* with the test antenna(s). +- 5) Configure the beam peak direction for the transmitter according to the declared reference beam direction pair for the appropriate beam identifier. +- 6) Set the test signal mean power so that the calibrated radiated power at the IAB Antenna Array coordinate system reference point is as follows: + +For general OTA blocking: + +- a) For *IAB-DU type 1-O*, set the signal generator for the wanted signal to transmit as specified in table 7.5.2.5.2-1. + +For *IAB-DU type 2-O*, set the signal generator for the wanted signal to transmit as specified in table 7.5.2.5.3-1. + +For *IAB-MT type 1-O*, set the signal generator for the wanted signal to transmit as specified in table 7.5.2.5.4-1. + +For *IAB-MT type 2-O*, set the signal generator for the wanted signal to transmit as specified in table 7.5.2.5.5-1. + +For simultaneous operation tests for IAB type 1-O, set the signal generator for the wanted signal of IAB-DU type 1-O to transmit as specified in table 7.5.2.5.2-1 and for the wanted signal of IAB-MT type 1-O to transmit in table 7.5.2.5.4-1. + +For simultaneous operation tests for IAB type 2-O, set the signal generator for the wanted signal of IAB-DU type 2-O to transmit as specified in table 7.5.2.5.3-1 and for the wanted signal of IAB-MT type 2-O to transmit in table 7.5.2.5.5-1. b) For *IAB-DU type 1-O*, set the signal generator for the interfering signal at the specified frequency offset from the wanted signal to transmit as specified in table 7.5.2.5.2-1. 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. + +For *IAB-DU type 2-O*, set the signal generator for the interfering signal at the specified frequency offset from the wanted signal to transmit as specified in table 7.5.2.5.3-1. The interfering signal shall be swept + +with a step size indicated in Table 7.5.2.4.2-1 starting from the minimum offset to the channel edges of the wanted signals. + +For *IAB-MT type 1-O*, set the signal generator for the interfering signal at the specified frequency offset from the wanted signal to transmit as specified in table 7.5.2.5.4-1. 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. + +For *IAB-MT type 2-O*, set the signal generator for the interfering signal at the specified frequency offset from the wanted signal to transmit as specified in table 7.5.2.5.5-1. The interfering signal shall be swept with a step size indicated in Table 7.5.2.4.2-1 starting from the minimum offset to the channel edges of the wanted signals. + +For IAB simultaneous operation tests for IAB type 1-O, set the signal generator for the interfering signal at the specified frequency offset from the wanted signal to transmit as specified in table 7.5.2.5.4-1. 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. + +For IAB simultaneous operation tests for IAB type 2-O, set the signal generator for the interfering signal at the specified frequency offset from the wanted signal to transmit as specified in table 7.5.2.5.5-1. The interfering signal shall be swept with a step size indicated in Table 7.5.2.4.2-1 starting from the minimum offset to the channel edges of the wanted signals. + +**Table 7.5.2.4.2-1: FR2-1 Interferer signal step size** + +| Minimum supported IAB channel bandwidth (MHz) | Measurement step size (MHz) | +|------------------------------------------------------|-----------------------------| +| 50 | 15 | +| 100 | 30 | +| 200 | 60 | +| 400 | 60 | + +For OTA narrowband blocking: + +- a) For *IAB-DU type 1-O*, set the signal generator for the wanted signal to transmit as specified in table 7.5.2.5.2-2. + +For *IAB-DU type 2-O*, set the signal generator for the wanted signal to transmit as specified in table 7.5.2.5.3-2. + +For *IAB-MT type 1-O*, set the signal generator for the wanted signal to transmit as specified in table 7.5.2.5.4-2. + +For *IAB-MT type 2-O*, set the signal generator for the wanted signal to transmit as specified in table 7.5.2.5.5-2. + +For simultaneous operation tests for IAB type 1-O, set the signal generator for the wanted signal of IAB-DU type 1-O to transmit as specified in table 7.5.2.5.2-2 and for the wanted signal of IAB-MT type 1-O to transmit in table 7.5.2.5.4-2. + +For simultaneous operation tests for IAB type 2-O, set the signal generator for the wanted signal of IAB-DU type 2-O to transmit as specified in table 7.5.2.5.3-2 and for the wanted signal of IAB-MT type 2-O to transmit in table 7.5.2.5.5-2. + +- b) For *IAB-DU type 1-O*, set the signal generator for the interfering signal at the specified frequency offset from the wanted signal to transmit as specified in tables 7.5.2.5.2-2 and 7.5.2.5.2-3. Set-up and sweep the interfering RB centre frequency offset to the channel edge of the wanted signal according to table 7.5.2.5.2-3. + +For *IAB-DU type 2-O*, set the signal generator for the interfering signal at the specified frequency offset from the wanted signal to transmit as specified in tables 7.5.2.5.3-2 and 7.5.2.5.3-3. Set-up and sweep the interfering RB centre frequency offset to the channel edge of the wanted signal according to table 7.5.2.5.3-3. + +For *IAB-MT type 1-O*, set the signal generator for the interfering signal at the specified frequency offset from the wanted signal to transmit as specified in tables 7.5.2.5.4-2 and 7.5.2.5.4-3. Set-up and sweep the interfering RB centre frequency offset to the channel edge of the wanted signal according to table 7.5.2.5.4-3. + +For *IAB-MT type 2-O*, set the signal generator for the interfering signal at the specified frequency offset from the wanted signal to transmit as specified in tables 7.5.2.5.5-2 and 7.5.2.5.5-3. Set-up and sweep the interfering RB centre frequency offset to the channel edge of the wanted signal according to table 7.5.2.5.5-3. + +For IAB simultaneous operation tests for IAB type 1-O, set the signal generator for the interfering signal at the specified frequency offset from the wanted signal to transmit as specified in tables 7.5.2.5.4-2 and 7.5.2.5.4-3. Set-up and sweep the interfering RB centre frequency offset to the channel edge of the wanted signal according to table 7.5.2.5.2-3. + +For IAB simultaneous operation tests for IAB type 2-O, set the signal generator for the interfering signal at the specified frequency offset from the wanted signal to transmit as specified in tables 7.5.2.5.5-2 and 7.5.2.5.5-3. Set-up and sweep the interfering RB centre frequency offset to the channel edge of the wanted signal according to table 7.5.2.5.3-3. + +- 7) Measure throughput according to annex A.1 for each supported polarization, for multi-carrier and/or CA operation the throughput shall be measured for relevant carriers specified by the test configuration specified in clauses 4.7.2 and 4.8. +- 8) Repeat steps 3 to 8 for all the specified measurement directions. + +For *multi-band RIB(s)* 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.5.2.5 Test requirement + +### 7.5.2.5.1 General + +The test requirement is calculated from the OTA wanted signal mean power level offset by the OTA in-band blocking Test Tolerance specified in annex C. + +### 7.5.2.5.2 Test requirements for *IAB-DU type 1-O* + +The requirement shall apply 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*. + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel, with OTA wanted and OTA interfering signal specified in tables 7.5.2.5.2-1, table 7.5.2.5.2-2 and table 7.5.2.5.2-3 for general OTA and narrowband OTA blocking requirements. The reference measurement channel for the OTA wanted signal is identified in clause 7.3.5.2 and is further specified in annex A.1. The characteristics of the interfering signal is further specified in annex H. + +The OTA in-band blocking requirements apply outside the *IAB RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *IAB RF Bandwidth edges* or *Radio Bandwidth edges*. + +For *IAB-DU type 1-O* the OTA in-band blocking requirement shall apply in the in-band blocking frequency range, which is defined within frequency range from $F_{UL\_low} - \Delta f_{FOB}$ to $F_{UL\_high} + \Delta f_{FOB}$ , where the $\Delta f_{FOB}$ for *IAB type 1-O* is defined in table 7.5.2.5.2-0. + +**Table 7.5.2.5.2-0: $\Delta f_{\text{OoB}}$ offset for NR operating bands in FR1** + +| IAB-DU type | Operating band characteristics | \Delta f_{\text{OoB}} (MHz) | +|--------------------|--------------------------------------------------------------------------------------|-------------------------------------------------| +| IAB-DU type
1-O | $F_{\text{UL\_high}} - F_{\text{UL\_low}} < 100 \text{ MHz}$ | 20 | +| | $100 \text{ MHz} \leq F_{\text{UL\_high}} - F_{\text{UL\_low}} \leq 900 \text{ MHz}$ | 60 | + +For RIBs supporting operation in *non-contiguous spectrum* within any *operating band*, the OTA in-band blocking requirements apply 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.2.5.2-1. The interfering signal offset is defined relative to the sub-block edges inside the sub-block gap. + +For *multi-band RIBs*, the OTA in-band blocking requirements apply in the in-band blocking frequency ranges for each supported *operating band*. The requirement shall apply 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 tables 7.5.2.5.2-1 and 7.5.2.5.2-3. + +For a RIBs supporting operation in *non-contiguous spectrum* within any operating band, the OTA narrowband blocking requirements apply in addition inside any sub-block gap, in case the sub-block gap size is at least as wide as the interfering signal minimum offset in table 7.5.2.5.2-3. The interfering signal offset is defined relative to the sub-block edges inside the sub-block gap. + +For a *multi-band RIBs*, the OTA narrowband blocking requirements apply in the narrowband blocking frequency ranges for each supported *operating band*. The requirement shall apply in addition inside any *Inter RF Bandwidth gap*, in case the *Inter RF Bandwidth gap* size is at least as wide as the interfering signal minimum offset in table 7.5.2.5.2-3. + +**Table 7.5.2.5.2-1: General OTA blocking requirement for IAB-DU type 1-O** + +| IAB-DU channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | | | Interfering signal mean power (dBm) | Interfering signal centre frequency minimum offset from the lower/upper IAB RF Bandwidth edge or sub-block edge inside a sub-block gap (MHz) | 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 | | | | +| 10, 15, 20 | $EIS_{REFSENS} + 6$ dB (NOTE 2) | | | Wide Area IAB: -43 - $\Delta_{OTAREFSENS}$
Medium Range IAB: -38 - $\Delta_{OTAREFSENS}$
Local Area IAB: -35 - $\Delta_{OTAREFSENS}$ (NOTE 2) | $\pm 7.5$ | 5 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| | $EIS_{minSENS} + 6$ dB (NOTE 3) | | | Wide Area IAB: -43 - $\Delta_{minSENS}$
Medium Range IAB: -38 - $\Delta_{minSENS}$
Local Area IAB: -35 - $\Delta_{minSENS}$ (NOTE 3) | | | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $EIS_{REFSENS} + 6$ dB (NOTE 2) | | | Wide Area IAB: -43 - $\Delta_{OTAREFSENS}$
Medium Range IAB: -38 - $\Delta_{OTAREFSENS}$
Local Area IAB: -35 - $\Delta_{OTAREFSENS}$ (NOTE 2) | $\pm 30$ | 20 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| | $EIS_{minSENS} + 6$ dB (NOTE 3) | | | Wide Area IAB: -43 - $\Delta_{minSENS}$
Medium Range IAB: -38 - $\Delta_{minSENS}$
Local Area IAB: -35 - $\Delta_{minSENS}$ (NOTE 3) | | | + +NOTE 1: $EIS_{REFSENS}$ and $EIS_{minSENS}$ depends on the IAB-DU channel bandwidth as specified in TS 38.174 [2], clause 10.3.2 and 10.2.1. + +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.2.5.2-2: OTA narrowband blocking requirement for IAB-DU type 1-O** + +| IAB-DU channel bandwidth of the lowest/highest carrier received (MHz) | OTA Wanted signal mean power (dBm) | | | OTA Interfering signal mean power (dBm) | +|------------------------------------------------------------------------------|-----------------------------------------|--------------------------------------------|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| | $f \leq 3.0$ GHz | $3.0 \text{ GHz} < f \leq 4.2 \text{ GHz}$ | $4.2 \text{ GHz} < f \leq 6.0 \text{ GHz}$ | | +| 10, 15, 20 | $EIS_{REFSENS} + 6 \text{ dB}$ (NOTE 3) | | | Wide Area IAB: $-49 - \Delta_{OTAREFSENS}$
Medium Range IAB: $-44 - \Delta_{OTAREFSENS}$
Local Area IAB: $-41 - \Delta_{OTAREFSENS}$ | +| | $EIS_{minSENS} + 6 \text{ dB}$ (NOTE 4) | | | Wide Area IAB: $-49 - \Delta_{minSENS}$
Medium Range IAB: $-44 - \Delta_{minSENS}$
Local Area IAB: $-41 - \Delta_{minSENS}$ | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $EIS_{REFSENS} + 6 \text{ dB}$ (NOTE 3) | | | Wide Area IAB: $-49 - \Delta_{OTAREFSENS}$
Medium Range IAB: $-44 - \Delta_{OTAREFSENS}$
Local Area IAB: $-41 - \Delta_{OTAREFSENS}$ | +| | $EIS_{minSENS} + 6 \text{ dB}$ (NOTE 4) | | | Wide Area IAB: $-49 - \Delta_{minSENS}$
Medium Range IAB: $-44 - \Delta_{minSENS}$
Local Area IAB: $-41 - \Delta_{minSENS}$ | + +NOTE 1: The SCS for the lowest/highest carrier received is the lowest SCS supported by the IAB-DU for that bandwidth. + +NOTE 2: $EIS_{REFSENS}$ and $EIS_{minSENS}$ depends on the *IAB-DU channel bandwidth* as specified in TS 38.174 [2], clause 10.3.2 and 10.2.1. + +NOTE 3: This test requirement is only applied in the OTA REFSENS conformance test directions. + +NOTE 4: This test requirement is only applied in the OTA minSENS receiver target reference direction. + +NOTE 5: 7.5 kHz shift is not applied to the wanted signal. + +**Table 7.5.2.5.2-3: OTA narrowband blocking interferer frequency offsets for IAB-DU type 1-O** + +| IAB-DU channel bandwidth of the lowest/highest carrier received (MHz) | Interfering RB centre frequency offset to the lower/upper IAB RF Bandwidth edge or sub-block edge inside a sub-block gap (kHz) (Note 2) | Type of interfering signal | +|------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------| +| 10 | $\pm(355 + m*180)$ ,
m=0, 1, 2, 3, 4, 9, 14, 19, 24 | 5 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 1 RB | +| 15 | $\pm(360 + m*180)$ ,
m=0, 1, 2, 3, 4, 9, 14, 19, 24 | | +| 20 | $\pm(350 + m*180)$ ,
m=0, 1, 2, 3, 4, 9, 14, 19, 24 | | +| 25 | $\pm(565 + m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | 20 MHz DFT-s-OFDM NR signal, 15 kHz SCS, 1 RB | +| 30 | $\pm(570 + m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 35 | $\pm(560 + m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 40 | $\pm(565 + m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 45 | $\pm(570 + m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 50 | $\pm(560 + m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 60 | $\pm(570 + m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 70 | $\pm(565 + m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 80 | $\pm(560 + m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 90 | $\pm(570 + m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 100 | $\pm(565 + m*180)$ ,
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | + +NOTE 1: 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 IAB RF Bandwidth edge. + +NOTE 2: The centre of the interfering RB refers to the frequency location between the two central subcarriers. + +### 7.5.2.5.3 Test requirements for IAB-DU type 2-O + +The requirement shall apply 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*. + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel. + +For *IAB-DU type 2-O*, the OTA wanted and OTA interfering signals are provided at RIB using the parameters in table 7.5.2.5.3-1 for general OTA blocking requirements. The reference measurement channel for the OTA wanted signal is identified in clause 7.3.5.3 and is further specified in annex A.1. The characteristics of the interfering signal is further specified in annex H. + +The OTA blocking requirements are applicable outside the *IAB RF Bandwidth*. The interfering signal offset is defined relative to the *IAB RF Bandwidth edges*. + +For *IAB-DU type 2-O* the OTA blocking requirement shall apply in the in-band blocking frequency range, which is defined within frequency range from $F_{UL\_low} - \Delta f_{OOB}$ to $F_{UL\_high} + \Delta f_{OOB}$ , where the $\Delta f_{OOB}$ for *IAB-DU type 2-O* is defined in table 7.5.2.5.3-0. + +**Table 7.5.2.5.3-0: $\Delta f_{\text{OOB}}$ offset for NR operating bands in FR2** + +| IAB-DU type | Operating band characteristics | $\Delta f_{\text{OOB}}$ (MHz) | +|-----------------|----------------------------------------------------------|-------------------------------| +| IAB-DU type 2-O | $F_{\text{UL\_high}} - F_{\text{UL\_low}} \leq 4000$ MHz | 1500 | + +For a RIBs supporting operation in *non-contiguous spectrum* within any *operating band*, the OTA blocking requirements apply 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.2.5.3-1. The interfering signal offset is defined relative to the sub-block edges inside the sub-block gap. + +**Table 7.5.2.5.3-1: General OTA blocking requirement for IAB-DU type 2-O** + +| IAB-DU channel bandwidth of the lowest/highest carrier received (MHz) | OTA wanted signal mean power (dBm) | | OTA interfering signal mean power (dBm) | OTA interfering signal centre frequency offset from the lower/upper IAB RF Bandwidth edge or sub-block edge inside a sub-block gap (MHz) | Type of OTA interfering signal | +|-----------------------------------------------------------------------|-----------------------------------------------|----------------------------------------------|-------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------| +| | $24.24 \text{ GHz} < f \leq 33.4 \text{ GHz}$ | $37 \text{ GHz} < f \leq 52.6 \text{ GHz}$ | | | | +| 50, 100, 200, 400 | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | $\text{EIS}_{\text{REFSENS}} + 6 \text{ dB}$ | $\text{EIS}_{\text{REFSENS\_50M}} + 33 + \Delta f_{\text{FR2\_REFSENS}} \text{ dB}$ | $\pm 75$ | 50 MHz DFT-s-OFDM NR signal, 60 kHz SCS, 64 RBs | + +NOTE: $\text{EIS}_{\text{REFSENS}}$ and $\text{EIS}_{\text{REFSENS\_50M}}$ are given in TS 38.104 [2], clause 10.3.3. + +#### 7.5.2.5.4 Test requirements for IAB-MT type 1-O + +The requirement shall apply 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*. + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel, with OTA wanted and OTA interfering signal specified in tables 10.5.2.5-1, table 10.5.2.5-2 and table 10.5.2.5-3 for general OTA and narrowband OTA blocking requirements. The reference measurement channel for the OTA wanted signal is identified in clause 10.3.3 and are further specified in annex A.1. The characteristics of the interfering signal is further specified in annex H. + +The OTA in-band blocking requirements apply outside the *IAB-MT RF Bandwidth* or *Radio Bandwidth*. The interfering signal offset is defined relative to the *IAB-MT RF Bandwidth edges* or *Radio Bandwidth edges*. + +For *IAB-MT type 1-O* the OTA in-band blocking requirement shall apply in the in-band blocking frequency range, which is from $F_{\text{DL\_low}} - \Delta f_{\text{OOB}}$ to $F_{\text{DL\_high}} + \Delta f_{\text{OOB}}$ . The $\Delta f_{\text{OOB}}$ for *wide area IAB-MT type 1-O* is defined in table 10.5.2.5-0. + +**Table 7.5.2.5.4-0: $\Delta f_{\text{OOB}}$ offset for NR operating bands in FR1** + +| IAB-MT type | Operating band characteristics | $\Delta f_{\text{OOB}}$ (MHz) | +|-----------------|--------------------------------------------------------------------------------------|-------------------------------| +| IAB-MT type 1-O | $F_{\text{DL\_high}} - F_{\text{DL\_low}} < 100 \text{ MHz}$ | 20 | +| | $100 \text{ MHz} \leq F_{\text{DL\_high}} - F_{\text{DL\_low}} \leq 900 \text{ MHz}$ | 60 | + +For RIBs supporting operation in *non-contiguous spectrum* within any *operating band*, the OTA in-band blocking requirements apply 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 10.5.2.2-1. The interfering signal offset is defined relative to the *sub-block* edges inside the *sub-block gap*. + +For *multi-band RIBs*, the OTA in-band blocking requirements apply in the in-band blocking frequency ranges for each supported *operating band*. The requirement shall apply 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 tables 10.5.2.5-1 and 10.5.2.5-3. + +For a RIBs supporting operation in *non-contiguous spectrum* within any *operating band*, the OTA narrowband blocking requirements apply in addition inside any *sub-block gap*, in case the *sub-block gap* size is at least as wide as the interfering signal minimum offset in table 10.5.2.5-3. The interfering signal offset is defined relative to the *sub-block* edges inside the *sub-block gap*. + +For a *multi-band RIBs*, the OTA narrowband blocking requirements apply in the narrowband blocking frequency ranges for each supported *operating band*. The requirement shall apply in addition inside any *Inter RF Bandwidth gap*, in case the *Inter RF Bandwidth gap* size is at least as wide as the interfering signal minimum offset in table 10.5.2.5-3. + +**Table 7.5.2.5.4-1: General OTA blocking requirement for IAB-MT type 1-O** + +| IAB-MT channel bandwidth of the lowest/highest carrier received (MHz) | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Interfering signal centre frequency minimum offset from the lower/upper IAB-MT RF Bandwidth edge or sub-block edge inside a sub-block gap (MHz) | Type of interfering signal | +|-----------------------------------------------------------------------|--------------------------------|-------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------| +| 10, 15, 20 | $EIS_{REFSENS} + 6$ dB | Wide Area IAB-MT: -43 - $\Delta_{OTAREFSENS}$
Local Area IAB-MT: -35 - $\Delta_{OTAREFSENS}$ | $\pm 7.5$ | 5 MHz CP-OFDM NR signal, 15 kHz SCS, 25 RBs | +| | $EIS_{minSENS} + 6$ dB | Wide Area IAB-MT: -43 - $\Delta_{minSENS}$
Local Area IAB-MT: -35 - $\Delta_{minSENS}$ | $\pm 7.5$ | | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | $EIS_{REFSENS} + 6$ dB | Wide Area IAB-MT: -43 - $\Delta_{OTAREFSENS}$
Local Area IAB-MT: -35 - $\Delta_{OTAREFSENS}$ | $\pm 30$ | 20 MHz CP-OFDM NR signal, 15 kHz SCS, 100 RBs | +| | $EIS_{minSENS} + 6$ dB | Wide Area IAB-MT: -43 - $\Delta_{minSENS}$
Local Area IAB-MT: -35 - $\Delta_{minSENS}$ | $\pm 30$ | | + +**Table 7.5.2.5.4-2: OTA narrowband blocking requirement for IAB-MT type 1-O** + +| IAB-MT channel bandwidth of the lowest/highest carrier received (MHz) | OTA Wanted signal mean power (dBm) | OTA Interfering signal mean power (dBm) | +|------------------------------------------------------------------------------|-------------------------------------------|-----------------------------------------------------------------------------------------------------| +| 10, 15, 20 | EIS REFSENS + 6 dB | Wide Area IAB-MT: -49 - Δ OTAREFSENS
Local Area IAB-MT: -41 - Δ OTAREFSENS | +| | EIS minSENS + 6 dB | Wide Area IAB-MT: -49 - Δ minSENS
Local Area IAB-MT: -41 - Δ OTAREFSENS | +| 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | EIS REFSENS + 6 dB | Wide Area IAB-MT: -49 - Δ OTAREFSENS
Local Area IAB-MT: -41 - Δ OTAREFSENS | +| | EIS minSENS + 6 dB | Wide Area IAB-MT: -49 - Δ minSENS
Local Area IAB-MT: -41 - Δ OTAREFSENS | + +NOTE 1: The SCS for the *lowest/highest carrier* received is the lowest SCS supported by the IAB-MT for that bandwidth. +NOTE 2: 7.5 kHz shift is not applied to the wanted signal. + +**Table 7.5.2.5.4-3: OTA narrowband blocking interferer frequency offsets for IAB-MT type 1-O** + +| IAB-MT channel bandwidth of the lowest/highest carrier received (MHz) | Interfering RB centre frequency offset to the lower/upper IAB-MT RF Bandwidth edge or sub-block edge inside a sub-block gap (kHz) (Note 2) | Type of interfering signal | +|------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------| +| 10 | ±(355 + m*180),
m=0, 1, 2, 3, 4, 9, 14, 19, 24 | 5 MHz CP-OFDM NR signal, 15 kHz SCS, 1 RB | +| 15 | ±(360 + m*180),
m=0, 1, 2, 3, 4, 9, 14, 19, 24 | | +| 20 | ±(350 + m*180),
m=0, 1, 2, 3, 4, 9, 14, 19, 24 | | +| 25 | ±(565 + m*180),
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | 20 MHz CP-OFDM NR signal, 15 kHz SCS, 1 RB | +| 30 | ±(570 + m*180),
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 35 | ±(560+m*180),
m=0, 1, 2, 3, 4, 29, 54, 79, 9 | | +| 40 | ±(565 + m*180),
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 45 | ±(570+m*180),
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 50 | ±(560 + m*180),
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 60 | ±(570 + m*180),
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 70 | ±(565 + m*180),
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 80 | ±(560 + m*180),
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 90 | ±(570 + m*180),
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | +| 100 | ±(565 + m*180),
m=0, 1, 2, 3, 4, 29, 54, 79, 99 | | + +NOTE 1: 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 IAB-MT RF Bandwidth edge or sub-block edge inside a sub-block gap. +NOTE 2: The centre of the interfering RB refers to the frequency location between the two central subcarriers. + +### 7.5.2.5.5 Test requirements for IAB-MT type 2-O + +The requirement shall apply 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*. + +The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel. + +For Wide Area IAB-MT type 2-O, the OTA wanted and OTA interfering signals are provided at RIB using the parameters in table 7.5.2.5.5-1 for general OTA blocking requirements. The reference measurement channel for the wanted signal is further specified in annex A.1. The characteristics of the interfering signal is further specified in annex H. + +The OTA blocking requirements are applicable outside the IAB-MT RF Bandwidth. The interfering signal offset is defined relative to the *IAB-MT RF Bandwidth edges*. + +For Wide Area IAB-MT type 2-O the OTA in-band blocking requirement shall apply from $F_{DL\_low} - \Delta f_{OOB}$ to $F_{DL\_high} + \Delta f_{OOB}$ . The $\Delta f_{OOB}$ for IAB-MT type 2-O is defined in table 7.5.2.5.5-0. + +**Table 7.5.2.5.5-0: $\Delta f_{OOB}$ offset for NR operating bands for Wide Area IAB-MT in FR2** + +| IAB-MT type | Operating band characteristics | $\Delta f_{OOB}$ (MHz) | +|-----------------|--------------------------------------------|------------------------| +| IAB-MT type 2-O | $F_{DL\_high} - F_{DL\_low} \leq 3250$ MHz | 1500 | + +For Wide Area IAB-MT and for a RIBs supporting operation in *non-contiguous spectrum* within any *operating band*, the OTA blocking requirements apply 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.2.5.5-1. The interfering signal offset is defined relative to the sub-block edges inside the sub-block gap. + +**Table 7.5.2.5.5-1: General OTA blocking requirement for Wide Area IAB-MT** + +| IAB MT channel bandwidth of the lowest/highest carrier received (MHz) | OTA wanted signal mean power (dBm) | OTA interfering signal mean power (dBm) | OTA interfering signal centre frequency offset from the lower/upper IAB MT [ RF Bandwidth] edge or sub-block edge inside a sub-block gap (MHz) | Type of OTA interfering signal | +|-----------------------------------------------------------------------|------------------------------------|------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------| +| 50, 100, 200, 400 | $EI_{S_{REFSENS}} + 6$ dB | $EI_{S_{REFSENS\_50M}} + 33 + \Delta_{FR2\_REFSENS}$ | $\pm 75$ | 50 MHz CP-OFDM NR signal, 60 kHz SCS, 64 RBs | + +NOTE: $EI_{S_{REFSENS}}$ and $EI_{S_{REFSENS\_50M}}$ are given in subclause 10.3.3. + +## 7.6 OTA out-of-band blocking + +### 7.6.1 Definition and applicability + +The OTA out-of-band 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. + +For the general OTA out-of-band blocking the requirement applies to the wanted signal for 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 Minimum requirement + +For *IAB type 1-O*, the minimum requirements are defined in TS 38.174 [2], clause 10.6.2. Co-location minimum requirements are defined in TS 38.174[2], clause 10.6.4. + +For *IAB type 2-O*, the minimum requirements are defined in TS 38.174 [2], clause 10.6.3. + +## 7.6.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.4 Method of test + +### 7.6.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier (SC): M; see clause 4.9.1. + +*IAB RF Bandwidth* positions to be tested for multi-carrier (MC): + +- $M_{\text{RFBW}}$ in *single-band RIB*, see clause 4.9.1; $B_{\text{RFBW\_T}}$ and $B'_{\text{RFBW\_T}}$ in *multi-band RIB*, see clause 4.9.1. + +In addition, for *multi-band RIB*: + +- For $B_{\text{RFBW\_T}}$ , blocking testing above the highest operating band may be omitted. +- For $B'_{\text{RFBW\_T}}$ , blocking testing below the lowest operating band may be omitted. + +Directions to be tested: + +- For *IAB type 1-O*, receiver target reference direction (D.31). +- For *IAB type 2-O*, OTA REFESENS receiver target reference direction (D.54). + +### 7.6.4.2 Procedure + +#### 7.6.4.2.1 *IAB type 1-O* procedure for out-of-band blocking + +- 1) Place IAB and the test antenna(s) according to annex E.2.4.1. +- 2) Align the IAB and test antenna(s) according to the directions to be tested. +- 3) Connect test antenna(s) to the measurement equipment as shown in annex E.2.4.1. +- 4) The test antenna(s) shall be dual (or single) polarized covering the same frequency ranges as the *IAB* 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) Generate the wanted signal in receiver target reference direction, according to the applicable test configuration (see clause 4.8) using applicable reference measurement channel to the RIB, according to annex A.1. + +For simultaneous operation tests for IAB type 1-O, set the signal generator for the wanted signal of IAB-DU type 1-O to transmit as specified in table 7.6.5.1.1-1 and for the wanted signal of IAB-MT type 1-O to transmit in table 7.6.5.1.1-1.7. 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.5.1.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. + +- 8) The CW interfering signal shall be swept with a step size of 1 MHz within the frequency range specified in clause 7.6.5.1.1. +- 9) 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.7 and 4.8. +- 10) Repeat for all supported polarizations. + +In addition, for *multi-band RIB*, the following steps shall apply: + +- 11) 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.4.2.2 IAB type 1-O procedure for co-location blocking + +- 1) Place NR IAB and CLTA as specified in clause 4.12.2.3. +- 2) Several CLTA are required to cover the whole co-location blocking frequency ranges. The CLTA shall be selected according to clause 4.12.2.2. +- 3) Align the NR IAB and test antenna(s) according to the directions to be tested. +- 4) Connect test antenna and CLTA to the measurement equipment as depicted in annex E.2.4.2. +- 5) The NR IAB receives the wanted signal in all supported polarizations, in the receiver target reference direction from the test antenna. +- 6) The OTA co-location blocking interferer is injected via the CLTA. The CLTA is fed with the specified co-location blocking interferer power per supported polarization. +- 7) Generate the wanted signal in receiver target reference direction, all supported polarizations, from the test antenna, according to the applicable test configuration (see clause 4.8) using applicable reference measurement channel to the RIB, according to annex A.1. + +For simultaneous operation tests for IAB type 1-O, set the signal generator for the wanted signal of IAB-DU type 1-O to transmit as specified in Table 7.6.5.1.2-1 and for the wanted signal of IAB-MT type 1-O to transmit in Table 7.6.5.1.2-1. + +- 8) 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.5.1.1-1 and, when applicable, for co-location test requirements in table 7.6.5.1.2-1. +- 9) The CW interfering signal shall be swept with a step size of 1 MHz within the frequency range corresponding to downlink operating bands related to co-located systems (according to declaration D.43). +- 10) 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.7 and 4.8. + +In addition, for *multi-band RIB*, the following steps shall apply: + +- 11) 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.4.2.3 IAB type 2-O procedure for out-of-band blocking + +- 1) Place IAB and the test antenna(s) according to annex E.2.4.1. +- 2) Align the IAB and test antenna(s) according to the directions to be tested. +- 3) Connect test antenna(s) to the measurement equipment as shown in annex E.2.4.1. +- 4) The test antenna(s) shall be dual (or single) polarized covering the same frequency ranges as the *IAB* 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) Generate the wanted signal, according to the applicable test configuration (see clause 4.7 and 4.8) using applicable reference measurement channel to the RIB, according to annex A.1. + +For simultaneous operation tests for IAB type 1-O, set the signal generator for the wanted signal of IAB-DU type 1-O to transmit as specified in Table 7.6.5.2.1-1 and for the wanted signal of IAB-MT type 1-O to transmit in Table 7.6.5.2.1-1. + +- 7) 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.5.2.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. +- 8) The interfering signal shall be swept within the frequency range specified in table 7.6.5.2.1-1 with the step size specified in table 7.6.4.2.3-1. +- 9) 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.7 and 4.8. + +**Table 7.6.4.2.3-1: Interferer signal step size** + +| Frequency range (MHz) | Minimum supported IAB channel bandwidth (MHz) | Measurement step size (MHz) | +|-----------------------|-----------------------------------------------|-----------------------------| +| 30 to 6000 | 50, 100, 200, 400 | 1 | +| 6000 to 60000 | 50 | 15 | +| | 100 | 30 | +| | 200 | 60 | +| | 400 | 60 | + +- 10) Repeat for all supported polarizations. + +## 7.6.5 Test requirements + +### 7.6.5.1 Requirement for IAB Type 1-O + +The test requirement consists of general and co-location requirements. + +#### 7.6.5.1.1 General + +For OTA wanted and OTA interfering signals provided at the RIB using the parameters in table 7.6.5.1.1-1, the following requirements shall be met: + +- The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel. The reference measurement channel for the OTA wanted signal is identified in clause 10.3.2 in TS 38.104 [4] for each IAB channel bandwidth and further specified in annex A.1. + +For a *multi-band RIB*, the OTA out-of-band requirement shall apply for each supported *operating band*, with the exception that the in-band blocking frequency ranges of all supported *operating bands* according to clause 7.4.2.2 in TS 38.104 [4] shall be excluded from the OTA out-of-band blocking requirement. + +For IAB type 1-O the OTA out-of-band blocking requirement apply from 30 MHz to $F_{UL\_low} - \Delta f_{OOB}$ and from $F_{UL\_high} + \Delta f_{OOB}$ up to 12750 MHz. The $\Delta f_{OOB}$ for IAB type 1-O is defined in table 7.5.2.5.2-0. + +**Table 7.6.5.1.1-1: OTA out-of-band 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: EISminSENS depends on the *channel bandwidth* as specified in TS 38.104 [4], clause 10.2.1. +NOTE 2: The RMS field-strength level in V/m is related to the interferer EIRP level at a distance described as + +$$E = \frac{\sqrt{30EIRP}}{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. + +### 7.6.5.1.2 Co-location requirement + +This additional OTA out-of-band blocking requirement may be applied for the protection of IAB receivers when NR, E-UTRA BS, UTRA BS, CDMA BS, GSM/EDGE BS or IAB-DU and/or IAB-MT operating in a different frequency band are co-located with an IAB-Node. + +The requirement is a co-location requirement. The interferer power levels are specified at the *co-location reference antenna* conducted input. The interfering signal power is specified per supported polarization. + +The requirement is valid over the *minSENS RoAoA*. + +For OTA wanted and OTA interfering signal provided at the RIB using the parameters in table 7.6.5.1.2-1, the following requirements shall be met: + +- The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel. The reference measurement channel for the OTA wanted signal is identified in TS 38.174 [2] clause 10.3 for each *IAB channel bandwidth* and further specified in annex A.1. The characteristics of the interfering signal is further specified in annex H. + +For *IAB type 1-O* the OTA blocking requirement for co-location with BS or IAB-Node in other frequency bands is applied for all *operating bands* for which co-location protection is provided. + +**Table 7.6.5.1.2-1: OTA blocking requirement for co-location with BS or IAB-Node in other frequency bands** + +| Frequency range of interfering signal | Wanted signal mean power (dBm) | Interfering signal mean power for WA IAB-Node (dBm) | Interfering signal mean power for MR IAB-Node (dBm) | Interfering signal mean power for LA IAB-Node (dBm) | Type of interfering signal | +|--------------------------------------------------------------|-------------------------------------------|-----------------------------------------------------|-----------------------------------------------------|-----------------------------------------------------|----------------------------| +| Frequency range of co-located downlink operating band | EIS minSENS + 6 dB
(Note 1) | +46 | +38 | +24 | CW carrier | + +NOTE 1: EISminSENS depends on the IAB class and on the *IAB channel bandwidth*, see TS 38.174 [2] clause 10.3. +NOTE 2: The requirement does not apply when the interfering signal falls within any of the supported downlink *operating band(s)* or in $\Delta f_{OoB}$ immediately outside any of the supported downlink *operating band(s)*. + +### 7.6.5.2 Requirement for *IAB type 2-O* + +The test requirement consists of general requirements. + +#### 7.6.5.2.1 General requirement + +For OTA wanted and OTA interfering signals provided at the RIB using the parameters in table 7.6.5.2.1-1, the following requirements shall be met: + +- The throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel. The reference measurement channel for the OTA wanted signal is identified in clause 10.3.3 in TS 38.174 [2] for each *IAB channel bandwidth* and further specified in annex A.1. + +For *IAB type 2-O* the OTA out-of-band blocking requirement apply from 30 MHz to $F_{UL\_low} - \Delta f_{OOB}$ and from $F_{UL\_high} + \Delta f_{OOB}$ up to $\min(2^{\text{nd}}$ harmonic of the upper frequency edge of the *operating band*, 60 GHz). The $\Delta f_{OOB}$ for *IAB type 2-O* is defined in table 7.5.2.5.3-0. + +**Table 7.6.5.2.1-1: OTA out-of-band blocking performance requirement** + +| Frequency range of interfering signal (MHz) | Wanted signal mean power (dBm) | Interferer RMS field-strength (V/m) | Type of interfering signal | +|----------------------------------------------------------------------------------------------------------------------------|--------------------------------|-------------------------------------|----------------------------| +| 30 to 12750 | $EIS_{REFSENS} + 6$ dB | 0.36 | CW carrier | +| 12750 to $F_{UL\_low} - \Delta f_{OOB}$ | | 0.1 | | +| $F_{UL\_high} + \Delta f_{OOB}$ to $\min(2^{\text{nd}}$ harmonic of the upper frequency edge of the operating band, 60000) | | 0.1 | | + +NOTE: $EIS_{REFSENS}$ is given in TS 38.174 [2], clause 10.3.3. + +## 7.7 OTA receiver spurious emissions + +### 7.7.1 Definition and applicability + +The OTA RX spurious emission is the power of the emissions radiated from the antenna array from a receiver unit. + +Unless otherwise stated, all requirements are measured as mean power. + +The OTA receiver spurious emission limits for FR1 shall apply from 30 MHz to 12.75 GHz, excluding the frequency range from $\Delta f_{OBUE}$ below the lowest frequency of each supported downlink *operating band*, up to $\Delta f_{OBUE}$ above the highest frequency of each supported downlink *operating band*, where the $\Delta f_{OBUE}$ is defined in clause [6.7.1]. For some *operating bands*, the upper limit of the spurious range might be higher than 12.75 GHz in order to comply with the 5th harmonic limit of the uplink *operating band*, as specified in Recommendation ITU-R SM.329 [10]. + +For *multi-band RIB* the above exclusion applies for each supported *operating band*. + +The OTA receiver spurious emission limits for FR2-1 shall apply from 30 MHz to 2nd harmonic of the upper frequency edge of the uplink *operating band*, excluding the frequency range from $\Delta f_{OBUE}$ below the lowest frequency of each supported downlink *operating band*, up to $\Delta f_{OBUE}$ above the highest frequency of each supported downlink *operating band*, where the $\Delta f_{OBUE}$ is defined in clause [6.7.1]. + +For a IAB operating in TDD, the OTA RX spurious emissions requirement shall apply during the *transmitter OFF period* only. + +The metric used to capture OTA receiver spurious emissions for *IAB type 1-O* and *IAB type 2-O* is total radiated power (TRP), with the requirement defined at the RIB. + +### 7.7.2 Minimum requirement + +The minimum requirement for *IAB-DU type 1-O* is specified in TS 38.174 [2], clause 10.7.1.2. + +The minimum requirement for *IAB-DU type 2-O* is specified in TS 38.174 [2], clause 10.7.2.2. + +The minimum requirement for *IAB-MT type 1-O* is specified in TS 38.174 [2], clause 10.7.3.1. + +The minimum requirement for *IAB-MT type 2-O* is specified in TS 38.174 [2], clause 10.7.3.2. + +### 7.7.3 Test purpose + +The test purpose is to verify if the receiver radiated spurious emissions from the IAB at the RIB are within the specified minimum requirements. + +### 7.7.4 Method of test + +#### 7.7.4.1 Initial conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier, see clause 4.9.1: + +- For FR1: + - B when testing from 30 MHz to $F_{DL\_low} - \Delta f_{OBUE}$ + - T when testing from $F_{DL\_high} + \Delta f_{OBUE}$ to 12.75 GHz (or to 5th harmonic) +- For FR2: + - B when testing from 30 MHz to $F_{DL\_low} - \Delta f_{OBUE}$ + - T when testing from $F_{DL\_high} + \Delta f_{OBUE}$ to 2nd harmonic (or to 60 GHz) + +RF bandwidth positions to be tested in single-band operation, see clause 4.9.1: + +- For FR1: + - $B_{RFBW}$ when testing from 30 MHz to $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) +- For FR2: + - $B_{RFBW}$ when testing from 30 MHz to $F_{DL\_low} - \Delta f_{OBUE}$ + - $T_{RFBW}$ when testing from $F_{DL\_high} + \Delta f_{OBUE}$ to 2nd harmonic (or to 60 GHz) + +RF bandwidth positions to be tested in multi-band operation, see clause 4.9.1: + +- For FR1: + - $B_{RFBW\_T'_{RFBW}}$ when testing from 30 MHz to $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 I) as long as the required TRP level is achieved. + +#### 7.7.4.2 Procedure + +The following procedure for measuring TRP is based on the directional power measurements as described in annex I. 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. + +- 1) Place the IAB at the positioner. +- 2) Align the manufacturer declared coordinate system orientation (D.2) of the IAB with the test system. +- 3) Measurements shall use a measurement bandwidth in accordance to the conditions in clause 7.7.5. +- 4) The measurement device characteristics shall be: + +- Detection mode: True RMS. +- 5) Set the TDD IAB to receive only. For *IAB type 1-O* and *IAB type 2-O* supporting simultaneous reception of IAB-DU and IAB-MT (D.IAB-3), both IAB-DU and IAB-MT shall be configured to simultaneously receive only during the test. +- 6) Orient the positioner (and IAB) in order that the direction to be tested aligns with the test antenna such that measurements to determine TRP can be performed (see annex I). +- 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 I). + +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 *IAB type 1-O* and *multi-band RIB(s)* 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 + +### 7.7.5.1 Test requirement for *IAB type 1-O* + +For RX only *multi-band RIB*, the OTA receiver spurious emissions requirements are subject to exclusion zones in each supported *operating band*. + +The power of any spurious emission shall not exceed the levels in table 7.7.5.1-1: + +**Table 7.7.5.1-1: General OTA receiver spurious emission limits for *IAB type 1-O*** + +| Spurious frequency range | Test limits (Note 6, Note 8) | Measurement bandwidth | Notes | +|---------------------------------------------------------------------------------------------------------|------------------------------|-----------------------|--------------------------------| +| 30 MHz – 1 GHz | -36 + X dBm | 100 kHz | Note 1, Note 6 | +| 1 GHz – 6 GHz | -30 + X dBm | 1 MHz | Note 1, Note 2, Note 6 | +| 12.75 GHz – 5 th harmonic of the upper frequency edge of the UL operating band in GHz | -30 + X dBm | 1 MHz | Note 1, Note 2, Note 3, Note 6 | + +NOTE 1: Measurement bandwidths as in ITU-R SM.329 [10], s4.1. +NOTE 2: Upper frequency as in ITU-R SM.329 [10], 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 $\Delta f_{OBUE}$ below the lowest frequency of the IAB transmitter operating band to $\Delta f_{OBUE}$ above the highest frequency of the IAB transmitter *operating band* may be excluded from the requirement. $\Delta f_{OBUE}$ is defined in clause 6.7.1. For *multi-band RIBs*, the exclusion applies for all supported *operating bands*. +NOTE 5: Void +NOTE 6: X = 9 dB, unless stated differently in regional regulation. +NOTE 7: Void +NOTE 8: Additional limits may apply regionally. + +### 7.7.5.2 Test requirement for *IAB type 2-O* + +The power of any receiver spurious emission shall not exceed the limits in table 7.7.5.2-1. + +**Table 7.7.5.2-1: Radiated Rx spurious emission limits for IAB type 2-O** + +| Spurious frequency range (Note 4) | Limit (Note 5) | Measurement Bandwidth | Note | +|-----------------------------------------------------------------------------------------------------------------------------------------|----------------|-----------------------|----------------| +| 30 MHz $\leftrightarrow$ 1 GHz | -36 dBm | 100 kHz | Note 1 | +| 1 GHz $\leftrightarrow$ 18 GHz | -30 dBm | 1 MHz | Note 1 | +| 18 GHz $\leftrightarrow$ F step,1 | -20 dBm | 10 MHz | Note 2 | +| F step,1 $\leftrightarrow$ F step,2 | -15 dBm | 10 MHz | Note 2 | +| F step,2 $\leftrightarrow$ F step,3 | -10 dBm | 10 MHz | Note 2 | +| F step,4 $\leftrightarrow$ F step,5 | -10 dBm | 10 MHz | Note 2 | +| F step,5 $\leftrightarrow$ F step,6 | -15 dBm | 10 MHz | Note 2 | +| F step,6 $\leftrightarrow$ min(2 nd harmonic of the upper frequency edge of the UL operating band in GHz; 60 GHz) | -20 dBm | 10 MHz | Note 2, Note 3 | + +NOTE 1: Bandwidth as in ITU-R SM.329 [10], s4.1. +NOTE 2: Limit and bandwidth as in ERC Recommendation 74-01 [11], Annex 2. +NOTE 3: Upper frequency as in ITU-R SM.329 [10], s2.5 table 1. +NOTE 4: The step frequencies Fstep,x are defined in table 7.7.5.2-2. +NOTE 5: Additional limits may apply regionally. + +**Table 7.7.5.2-2: Step frequencies for defining the radiated Rx spurious emission limits for IAB-DU type 2-O** + +| Operating band | F step,1 (GHz) | F step,2 (GHz) | F step,3 (GHz) | F step,4 (GHz) | F step,5 (GHz) | F step,6 (GHz) | +|----------------|---------------------------|---------------------------|---------------------------|---------------------------|---------------------------|---------------------------| +| n257 | 18 | 23.5 | 25 | 31 | 32.5 | 41.5 | +| n258 | 18 | 21 | 22.75 | 29 | 30.75 | 40.5 | +| n259 | 23.5 | 35.5 | 38 | 45 | 47.5 | 59.5 | +| n260 | 25 | 34 | 35.5 | 41.5 | 43 | 52 | +| n261 | 18 | 25.5 | 26.0 | 29.85 | 30.35 | 38.35 | + +In addition, the following requirement may be applied for protection of EESS for IAB operating in frequency range 24.25 – 27.5 GHz. + +The power of any receiver spurious emission shall not exceed the limits in Table 7.7.5.2-3. + +**Table 7.7.5.2-3: Limits for protection of Earth Exploration Satellite Service** + +| Frequency range | Limit | Measurement Bandwidth | Note | +|-----------------|--------|-----------------------|--------| +| 23.6 – 24 GHz | -3 dBm | 200 MHz | Note 1 | +| 23.6 – 24 GHz | -9 dBm | 200 MHz | Note 2 | + +NOTE 1: This limit applies to IAB brought into use on or before 1 September 2027 and enters into force from [January 1], 2021. +NOTE 2: This limit applies to IAB brought into use after 1 September 2027. + +## 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 is defined as a directional requirement at the RIB. + +The wanted and interfering signals apply to each supported polarization, under the assumption of *polarization match*. + +## 7.8.2 Minimum requirement + +The minimum requirements for *IAB-DU type 1-O* are in TS 38.174 [2], clause 10.8.2. + +The minimum requirements for *IAB-DU type 2-O* are in TS 38.174 [2], clause 10.8.3. + +The minimum requirements for *IAB-MT type 1-O* are in TS 38.174 [2], clause 10.8.4. + +## 7.8.3 Test purpose + +The test purpose is to verify the ability of the IAB 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, annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +*IAB RF Bandwidth* positions to be tested for multi-carrier and/or CA: + +- $M_{\text{RFBW}}$ for single-band operation, see clause 4.9.1. +- $B_{\text{RFBW\_T}}^{\text{RFBW}}$ and $B'_{\text{RFBW\_T}}^{\text{RFBW}}$ for multi-band operation, see clause 4.9.1. + +Directions to be tested: + +- OTA REFSENS receiver target reference direction (D.54). +- In addition, for *IAB type 1-O*, receiver target reference direction (D.31). + +### 7.8.4.2 Procedure + +- 1) Place the IAB with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.2.6. +- 2) Align the manufacturer declared coordinate system orientation of the IAB with the test system. +- 3) Align the IAB with the test antenna in the declared direction to be tested. +- 4) Align the IAB to that the wanted signal and interferer signal is *polarization matched* with the test antenna(s). +- 5) Configure the beam peak direction of the IAB according to declared reference beam direction pair for the appropriate beam identifier. +- 6) Set the test signal mean power so the calibrated radiated power at the IAB 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 sub-clause 7.8.5.1 for *IAB-DU type 1-O*, sub-clause 7.8.5.2 for *IAB-DU type 2-O* and sub-clause 7.8.5.3 for *IAB-MT type 1-O*. + - b) Set the signal generator for the interfering signal at the same frequency as the wanted signal to transmit as specified in sub-clause 7.8.5.1 for *IAB-DU type 1-O*, sub-clause 7.8.5.2 for *IAB-DU type 2-O* and sub-clause 7.8.5.3 for *IAB-MT type 1-O*. +- 7) Set the signal generator for the interfering signal to transmit at the frequency offset and as specified in sub-clause 7.8.5.1 for *IAB-DU type 1-O*, sub-clause 7.8.5.2 for *IAB-DU type 2-O* and sub-clause 7.8.5.3 for *IAB-MT type 1-O*. + +- 8) Measure the throughput according to annex A.1 for each supported polarization, for multi-carrier and/or CA operation the throughput shall be measured for relevant carriers specified by the test configuration specified in clause 4.7. For an *IAB type 1-O* node declared to be capable of Simultaneous reception between IAB-DU and IAB-MT (D.IAB-3) the throughput shall be measured for both IAB-MT and IAB-DU according to applicable test signal configuration and test models specified in clauses 4.7.2 and 4.8. +- 9) Repeat for all the specified measurement directions and supported polarizations. + +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.8.5 Test requirement + +### 7.8.5.1 IAB-DU type 1-O + +The requirement shall apply 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 EISREFSENS: the AoA of the incident wave of a received signal and the interfering signal are within the *FRI OTA REFSENS RoAoA*. +- when the wanted signal is based on EISminSENS: the AoA of the incident wave of a received signal and the interfering signal are within the *minSENS RoAoA*. + +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.1-1 and 7.8.5.1-2 for intermodulation performance and in tables 7.8.5.1-3 and 7.8.5.1-4 for narrowband intermodulation performance. + +The reference measurement channel for the wanted signal is identified in table 7.3.5.2-1, table 7.3.5.2-2 and table 7.3.5.2-3 for each *IAB-DU channel bandwidth* and further specified in annex A.1. + +The subcarrier spacing for the modulated interfering signal shall be the same as the subcarrier spacing for the wanted signal, except for the case of wanted signal subcarrier spacing 60 kHz and *IAB-DU channel bandwidth* $\leq 20$ MHz, for which the subcarrier spacing of the interfering signal should be 30 kHz. + +The receiver intermodulation requirement is applicable outside the IAB-DU RF Bandwidth or Radio Bandwidth edges. The interfering signal offset is defined relative to the IAB-DU RF Bandwidth edges or Radio Bandwidth edges. + +For a RIBs supporting operation in non-contiguous spectrum within any *operating band*, the narrowband intermodulation requirement shall apply in addition inside any sub-block gap in case the sub-block gap is at least as wide as the *IAB-DU channel bandwidth* of the NR interfering signal in tables 7.8.5.1-2 and 7.8.5.1-4. The interfering signal offset is defined relative to the sub-block edges inside the sub-block gap. + +For *multi-band RIBs*, the intermodulation requirement shall apply in addition inside any Inter RF Bandwidth gap, in case the gap size is at least twice as wide as the NR interfering signal centre frequency offset from the IAB-DU RF Bandwidth edge. + +For *multi-band RIBs*, the narrowband intermodulation requirement shall apply in addition inside any Inter RF Bandwidth gap in case the gap size is at least as wide as the NR interfering signal in tables 7.8.5.1-2 and 7.8.5.1-4. The interfering signal offset is defined relative to the IAB-DU RF Bandwidth edges inside the Inter RF Bandwidth gap. + +**Table 7.8.5.1-1: General intermodulation requirement** + +| IAB-DU class | Wanted Signal mean power (dBm) | Mean power of interfering signals (dBm) | Type of interfering signal | +|---------------------|---------------------------------------|------------------------------------------------|-----------------------------------| +| Wide Area | $EIS_{REFSENS} + 6$ dB | $-52 - \Delta_{OTAREFSENS}$ | See table 7.8.5.1-2 | +| | $EIS_{minSENS} + 6$ dB | $-52 - \Delta_{minSENS}$ | | +| Medium Range | $EIS_{REFSENS} + 6$ dB | $-47 - \Delta_{OTAREFSENS}$ | | +| | $EIS_{minSENS} + 6$ dB | $-47 - \Delta_{minSENS}$ | | +| Local Area | $EIS_{REFSENS} + 6$ dB | $-44 - \Delta_{OTAREFSENS}$ | | +| | $EIS_{minSENS} + 6$ dB | $-44 - \Delta_{minSENS}$ | | + +NOTE: $EIS_{REFSENS}$ and $EIS_{minSENS}$ depend on the IAB-DU class and on the IAB-DU *channel bandwidth* as specified in TS 38.174 [2], clause 10.2.1.1 and 10.3.2.1. + +**Table 7.8.5.1-2: Interfering signals for intermodulation requirement** + +| IAB-DU channel bandwidth of the lowest/highest carrier received (MHz) | Interfering signal centre frequency offset from the lower/upper IAB-DU RF Bandwidth edge (MHz) | Type of interfering signal (Note 3) | +|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|--------------------------------------------| +| 10 | ±7.465 | CW | +| | ±17.5 | 5MHz DFT-s-OFDM NR signal (Note 1) | +| 15 | ±7.43 | CW | +| | ±17.5 | 5MHz DFT-s-OFDM NR signal (Note 1) | +| 20 | ±7.395 | CW | +| | ±17.5 | 5MHz DFT-s-OFDM NR signal (Note 1) | +| 25 | ±7.465 | CW | +| | ±25 | 20 MHz DFT-s-OFDM NR signal (Note 2) | +| 30 | ±7.43 | CW | +| | ±25 | 20MHz DFT-s-OFDM NR signal (Note 2) | +| 35 | ±7.44 | CW | +| | ±25 | 20MHz DFT-s-OFDM NR signal (Note 2) | +| 40 | ±7.45 | CW | +| | ±25 | 20MHz DFT-s-OFDM NR signal (Note 2) | +| 45 | ±7.37 | CW | +| | ±25 | 20MHz DFT-s-OFDM NR signal (Note 2) | +| 50 | ±7.35 | CW | +| | ±25 | 20MHz DFT-s-OFDM NR signal (Note 2) | +| 60 | ±7.49 | CW | +| | ±25 | 20MHz DFT-s-OFDM NR signal (Note 2) | +| 70 | ±7.42 | CW | +| | ±25 | 20 MHz DFT-s-OFDM NR signal (Note 2) | +| 80 | ±7.44 | CW | +| | ±25 | 20MHz DFT-s-OFDM NR signal (Note 2) | +| 90 | ±7.46 | CW | +| | ±25 | 20 MHz DFT-s-OFDM NR signal (Note 2) | +| 100 | ±7.48 | CW | +| | ±25 | 20MHz DFT-s-OFDM NR signal (Note 2) | + +NOTE 1: For the 15 kHz subcarrier spacing, the number of RB is 25. For the 30 kHz subcarrier spacing, the number of RB is 10. + +NOTE 2: For the 15 kHz subcarrier spacing, the number of RB is 100. For the 30 kHz subcarrier spacing, the number of RB is 50. For the 60 kHz subcarrier spacing, the number of RB is 24. + +NOTE 3: The RBs shall be placed adjacent to the transmission bandwidth configuration edge which is closer to the *IAB-DU RF Bandwidth* edge. + +**Table 7.8.5.1-3: Narrowband intermodulation performance requirement in FR1** + +| IAB-DU class | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|---------------------|---------------------------------------|--------------------------------------------|-----------------------------------| +| Wide Area | $EIS_{REFSENS} + 6$ dB
(Note 1) | $-52 - \Delta_{OTAREFSENS}$ | See table 7.8.5.1-4 | +| | $EIS_{minSENS} + 6$ dB
(Note 1) | $-52 - \Delta_{minSENS}$ | | +| Medium Range | $EIS_{REFSENS} + 6$ dB
(Note 1) | $-47 - \Delta_{OTAREFSENS}$ | | +| | $EIS_{minSENS} + 6$ dB
(Note 1) | $-47 - \Delta_{minSENS}$ | | +| Local Area | $EIS_{REFSENS} + 6$ dB
(Note 1) | $-44 - \Delta_{OTAREFSENS}$ | | +| | $EIS_{minSENS} + 6$ dB
(Note 1) | $-44 - \Delta_{minSENS}$ | | + +NOTE: $EIS_{REFSENS}$ and $EIS_{minSENS}$ depends on the IAB *channel bandwidth* as specified in TS 38.174 [2], clause 10.2.1.1 and 10.3.2.1. + +**Table 7.8.5.1-4: Interfering signals for narrowband intermodulation requirement in FR1** + +| IAB-DU channel bandwidth of the lowest/highest carrier received (MHz) | Interfering RB centre frequency offset from the lower/upper IAB-DU RF Bandwidth edge or sub-block edge inside a sub-block gap (kHz) (Note 3) | Type of interfering signal | +|------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| +| 10 | ±370 | CW | +| | ±1960 | 5MHz DFT-s-OFDM NR signal, 1 RB (NOTE 1) | +| 15 (NOTE 2) | ±380 | CW | +| | ±1960 | 5MHz DFT-s-OFDM NR signal, 1 RB (NOTE 1) | +| 20 (NOTE 2) | ±390 | CW | +| | ±2320 | 5MHz DFT-s-OFDM NR signal, 1 RB (NOTE 1) | +| 25 (NOTE 2) | ±325 | CW | +| | ±2350 | 20MHz DFT-s-OFDM NR signal, 1 RB (NOTE 1) | +| 30 (NOTE 2) | ±335 | CW | +| | ±2350 | 20MHz DFT-s-OFDM NR signal, 1 RB (NOTE 1) | +| 35 (NOTE 2) | ±345 | CW | +| | ±2710 | 20MHz DFT-s-OFDM NR signal, 1 RB (NOTE 1) | +| 40 (NOTE 2) | ±355 | CW | +| | ±2710 | 20MHz DFT-s-OFDM NR signal, 1 RB (NOTE 1) | +| 45 (NOTE 2) | ±365 | CW | +| | ±2710 | 20MHz DFT-s-OFDM NR signal, 1 RB (NOTE 1) | +| 50 (NOTE 2) | ±375 | CW | +| | ±2710 | 20MHz DFT-s-OFDM NR signal, 1 RB (NOTE 1) | +| 60 (NOTE 2) | ±395 | CW | +| | ±2710 | 20MHz DFT-s-OFDM NR signal, 1 RB (NOTE 1) | +| 70 (NOTE 2) | ±415 | CW | +| | ±2710 | 20MHz DFT-s-OFDM NR signal, 1 RB (NOTE 1) | +| 80 (NOTE 2) | ±435 | CW | +| | ±2710 | 20MHz DFT-s-OFDM NR signal, 1 RB (NOTE 1) | +| 90 (NOTE 2) | ±365 | CW | +| | ±2530 | 20MHz DFT-s-OFDM NR signal, 1 RB (NOTE 1) | +| 100 (NOTE 2) | ±385 | CW | +| | ±2530 | 20MHz DFT-s-OFDM NR signal, 1 RB (NOTE 1) | + +NOTE 1: Interfering signal consisting of one resource block positioned at the stated offset, the *IAB-DU channel bandwidth* of the interfering signal is located adjacently to the lower/upper IAB-DU RF Bandwidth edge. + +NOTE 2: This requirement shall apply only for a G-FRC mapped to the frequency range at the channel edge adjacent to the interfering signals. + +NOTE 3: The centre of the interfering RB refers to the frequency location between the two central subcarriers. + +### 7.8.5.2 IAB-DU type 2-O + +Throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel, with OTA wanted signal at the assigned channel frequency and two OTA interfering signals provided at the RIB using the parameters in tables 7.8.5.2-1 and 7.8.5.2-2. All of the OTA test signals arrive from the same direction, and the requirement is valid if the signals arrive from any direction within the *FR2-1 OTA REFSENS RoAoA*. The reference measurement channel for the wanted signal is identified in table 7.3.5.3-1 for each *IAB-DU channel bandwidth* and further specified in annex A.1. + +The subcarrier spacing for the modulated interfering signal shall be the same as the subcarrier spacing for the wanted signal. + +The receiver intermodulation requirement is applicable outside the IAB-DU RF Bandwidth. The interfering signal offset is defined relative to the IAB-DU RF Bandwidth edges. + +**Table 7.8.5.2-1: General intermodulation requirement** + +| IAB-DU channel bandwidth of the lowest/highest carrier received (MHz) | Mean power of interfering signals (dBm) | Wanted signal mean power (dBm) | Type of interfering signal | +|------------------------------------------------------------------------------|--------------------------------------------------------------|---------------------------------------|-----------------------------------| +| 50, 100, 200, 400 | $EIS_{REFSENS\_50M} + 25 + \Delta_{FR2\_REFSENS} \text{ dB}$ | $EIS_{REFSENS} + 6 \text{ dB}$ | See table 7.8.5.2-2 | + +NOTE: $EIS_{REFSENS}$ and $EIS_{REFSENS\_50M}$ are given in TS 38.174 [2], clause 10.3.2.2. + +**Table 7.8.5.2-2: Interfering signals for intermodulation requirement** + +| IAB-DU channel bandwidth of the lowest/highest carrier received (MHz) | Interfering signal centre frequency offset from the IAB-DU RF Bandwidth edge (MHz) | Type of interfering signal | +|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|-----------------------------------| +| 50 MHz | $\pm 7.5$ | CW | +| | $\pm 40$ | 50MHz DFT-s-OFDM NR signal (Note) | +| 100 MHz | $\pm 6.88$ | CW | +| | $\pm 40$ | 50MHz DFT-s-OFDM NR signal (Note) | +| 200 MHz | $\pm 5.64$ | CW | +| | $\pm 40$ | 50MHz DFT-s-OFDM NR signal (Note) | +| 400 MHz | $\pm 6.02$ | CW | +| | $\pm 45$ | 50MHz DFT-s-OFDM NR signal (Note) | + +NOTE: For the 60 kHz subcarrier spacing, the number of RB is 64. For the 120 kHz subcarrier spacing, the number of RB is 32. + +### 7.8.5.3 IAB-MT type 1-O + +The requirement shall apply 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 *FR1 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 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 and 7.8.5.3-4 for narrowband intermodulation performance. + +The reference measurement channel for the wanted signal is identified in table 7.3.5.2-1, table 7.3.5.2-2 and table 7.3.5.2-3 for each *IAB-MT channel bandwidth* and further specified in annex A.1. + +The subcarrier spacing for the modulated interfering signal shall be the same as the subcarrier spacing for the wanted signal, except for the case of wanted signal subcarrier spacing 60 kHz and *IAB-MT channel bandwidth* $\leq 20$ MHz, for which the subcarrier spacing of the interfering signal should be 30 kHz. + +The receiver intermodulation requirement is applicable outside the IAB-MT RF Bandwidth or Radio Bandwidth edges. The interfering signal offset is defined relative to the IAB-MT RF Bandwidth edges or Radio Bandwidth edges. + +For a RIBs supporting operation in non-contiguous spectrum within any *operating band*, the narrowband intermodulation requirement shall apply in addition inside any sub-block gap in case the sub-block gap is at least as wide as the *IAB-MT channel bandwidth* of the NR interfering signal in tables 7.8.5.3-1 and 7.8.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 intermodulation requirement shall apply in addition inside any Inter RF Bandwidth gap, in case the gap size is at least twice as wide as the NR interfering signal centre frequency offset from the IAB-MT RF Bandwidth edge. + +For *multi-band RIBs*, the narrowband intermodulation requirement shall apply in addition inside any Inter RF Bandwidth gap in case the gap size is at least as wide as the NR interfering signal in tables 7.8.5.3-3 and 7.8.5.3-4. The interfering signal offset is defined relative to the IAB-MT RF Bandwidth edges inside the Inter RF Bandwidth gap. + +**Table 7.8.5.3-1: General intermodulation requirement** + +| IAB-MT class | Wanted Signal mean power (dBm) | Mean power of interfering signals (dBm) | Type of interfering signal | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-----------------------------------------|----------------------------| +| Wide Area | $EIS_{REFSENS} + 6$ dB | $-52 - \Delta_{OTAREFSENS}$ | See table 7.8.5.3-2 | +| | $EIS_{minSENS} + 6$ dB | $-52 - \Delta_{minSENS}$ | | +| Local Area | $EIS_{REFSENS} + 6$ dB | $-44 - \Delta_{OTAREFSENS}$ | | +| | $EIS_{minSENS} + 6$ dB | $-44 - \Delta_{minSENS}$ | | +| NOTE: $EIS_{REFSENS}$ and $EIS_{minSENS}$ depend on the IAB-MT class and on the IAB-MT channel bandwidth as specified in TS 38.174 [2], clause 10.2.2.1.2 and 10.3.3.2. | | | | + +**Table 7.8.5.3-2: Interfering signals for intermodulation requirement** + +| IAB-DU channel bandwidth of the lowest/highest carrier received (MHz) | Interfering signal centre frequency offset from the lower/upper IAB-DU RF Bandwidth edge (MHz) | Type of interfering signal (Note 3) | +|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|--------------------------------------------| +| 10 | ±7.465 | CW | +| | ±17.5 | 5MHz CP-OFDM NR signal (Note 1) | +| 15 | ±7.43 | CW | +| | ±17.5 | 5MHz CP-OFDM NR signal (Note 1) | +| 20 | ±7.395 | CW | +| | ±17.5 | 5MHz CP-OFDM NR signal (Note 1) | +| 25 | ±7.465 | CW | +| | ±25 | 20 MHz CP-OFDM NR signal (Note 2) | +| 30 | ±7.43 | CW | +| | ±25 | 20MHz CP-OFDM NR signal (Note 2) | +| 35 | ±7.44 | CW | +| | ±25 | 20MHz CP-OFDM NR signal (Note 2) | +| 40 | ±7.45 | CW | +| | ±25 | 20MHz CP-OFDM NR signal (Note 2) | +| 45 | ±7.37 | CW | +| | ±25 | 20MHz CP-OFDM NR signal (Note 2) | +| 50 | ±7.35 | CW | +| | ±25 | 20MHz CP-OFDM NR signal (Note 2) | +| 60 | ±7.49 | CW | +| | ±25 | 20MHz CP-OFDM NR signal (Note 2) | +| 70 | ±7.42 | CW | +| | ±25 | 20 MHz CP-OFDM NR signal (Note 2) | +| 80 | ±7.44 | CW | +| | ±25 | 20MHz CP-OFDM NR signal (Note 2) | +| 90 | ±7.46 | CW | +| | ±25 | 20 MHz CP-OFDM NR signal (Note 2) | +| 100 | ±7.48 | CW | +| | ±25 | 20MHz CP-OFDM NR signal (Note 2) | + +NOTE 1: For the 15 kHz subcarrier spacing, the number of RB is 25. For the 30 kHz subcarrier spacing, the number of RB is 10. + +NOTE 2: For the 15 kHz subcarrier spacing, the number of RB is 100. For the 30 kHz subcarrier spacing, the number of RB is 50. For the 60 kHz subcarrier spacing, the number of RB is 24. + +NOTE 3: The RBs shall be placed adjacent to the transmission bandwidth configuration edge which is closer to the IAB-MT RF Bandwidth edge. + +**Table 7.8.5.3-3: Narrowband intermodulation performance requirement in FR1** + +| IAB-MT class | Wanted signal mean power (dBm) | Interfering signal mean power (dBm) | Type of interfering signal | +|---------------------|---------------------------------------|--------------------------------------------|-----------------------------------| +| Wide Area | $EIS_{REFSENS} + 6$ dB
(Note 1) | $-52 - \Delta_{OTAREFSENS}$ | See table 7.8.5.3-4 | +| | $EIS_{minSENS} + 6$ dB
(Note 1) | $-52 - \Delta_{minSENS}$ | | +| Local Area | $EIS_{REFSENS} + 6$ dB
(Note 1) | $-44 - \Delta_{OTAREFSENS}$ | | +| | $EIS_{minSENS} + 6$ dB
(Note 1) | $-44 - \Delta_{minSENS}$ | | + +NOTE: $EIS_{REFSENS}$ and $EIS_{minSENS}$ depends on the *IAB-MT channel bandwidth* as specified in TS 38.174 [2], clause 10.2.2.1.2 and 10.3.3.2. + +**Table 7.8.5.3-4: Interfering signals for narrowband intermodulation requirement in FR1** + +| IAB-MT channel bandwidth of the lowest/highest carrier received (MHz) | Interfering RB centre frequency offset from the lower/upper IAB-MT RF Bandwidth edge or sub-block edge inside a sub-block gap (kHz) (Note 3) | Type of interfering signal | +|------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------| +| 10 | ±370 | CW | +| | ±1960 | 5MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 15 (NOTE 2) | ±380 | CW | +| | ±1960 | 5MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 20 (NOTE 2) | ±390 | CW | +| | ±2320 | 5MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 25 (NOTE 2) | ±325 | CW | +| | ±2350 | 20MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 30 (NOTE 2) | ±335 | CW | +| | ±2350 | 20MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 35 (NOTE 2) | ±345 | CW | +| | ±2710 | 20MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 40 (NOTE 2) | ±355 | CW | +| | ±2710 | 20MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 45 (NOTE 2) | ±365 | CW | +| | ±2710 | 20MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 50 (NOTE 2) | ±375 | CW | +| | ±2710 | 20MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 60 (NOTE 2) | ±395 | CW | +| | ±2710 | 20MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 70 (NOTE 2) | ±415 | CW | +| | ±2710 | 20MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 80 (NOTE 2) | ±435 | CW | +| | ±2710 | 20MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 90 (NOTE 2) | ±365 | CW | +| | ±2530 | 20MHz CP-OFDM NR signal, 1 RB (Note 1) | +| 100 (NOTE 2) | ±385 | CW | +| | ±2530 | 20MHz CP-OFDM NR signal, 1 RB (Note 1) | + +NOTE 1: Interfering signal consisting of one resource block positioned at the stated offset, the *IAB-MT channel bandwidth* of the interfering signal is located adjacently to the lower/upper IAB-MT RF Bandwidth edge. + +NOTE 2: This requirement shall apply only for a G-FRC mapped to the frequency range at the channel edge adjacent to the interfering signals. + +NOTE 3: The centre of the interfering RB refers to the frequency location between the two central subcarriers. + +## 7.9 OTA in-channel selectivity + +### 7.9.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. The interfering signal shall be an NR signal as specified in annex E in TS 38.176-1 [3] and shall be time aligned with the wanted signal. + +## 7.9.2 Minimum requirement + +The minimum requirement for *IAB-DU type 1-O* is in TS 38.174 [2], clause 10.9.2. + +The minimum requirement for *IAB-DU type 2-O* is in TS 38.174 [2], clause 10.9.3. + +## 7.9.3 Test purpose + +The purpose of this test is to verify the IAB receiver ability to suppress the IQ leakage. + +## 7.9.4 Method of test + +### 7.9.4.1 Initial conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +Directions to be tested: + +- For *IAB type 1-O*, receiver target reference direction (D.31), +- For *IAB type 2-O*, OTA REFSSENS receiver target reference direction (D.54). + +### 7.9.4.2 Procedure + +- 1) Place the IAB-DU with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.2.7. +- 2) Align the manufacturer declared coordinate system orientation of the IAB node with the test system. +- 3) Align the IAB-DU with the test antenna in the declared direction to be tested. +- 4) Align the IAB-DU to that the wanted signal and interferer signal is *polarization matched* with the test antenna(s). +- 5) Configure the beam peak direction for the transmitter according to the declared reference beam direction pair for the appropriate beam identifier. +- 6) Set the test signal mean power so the calibrated radiated power at the IAB Antenna Array coordinate system reference point is as specified as follows: + - a) Adjust the signal generator for the wanted signal as specified in subclause 7.9.5.1 for *IAB-DU type 1-O* and subclause 7.9.5.2 for *IAB-DU type 2-O*; + - b) Adjust the signal generator for the interfering signal as specified in subclause 7.9.5.1 for *IAB-DU type 1-O* and subclause 7.9.5.2 for *IAB-DU type 2-O*; +- 7) Measure throughput according to annex A.1 for each supported polarization. +- 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 the specified measurement directions and supported polarizations. + +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 IAB-DU type 1-O + +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 each supported polarization, under the assumption of *polarization match*. + +For a wanted and an interfering signal coupled to the RIB, the following requirements shall be met: + +- For *IAB-DU 1-O*, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.1 with parameters specified in table 7.9.5.1-1 for Wide Area IAB-DU, in table 7.9.5.1-2 for Medium Range IAB-DU and in table 7.9.5.1-3 for Local Area IAB-DU. + +**Table 7.9.5.1-1: Wide Area IAB-DU in-channel selectivity** + +| NR channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel (annex A.1) | 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 | | | +| 10, 15, 20, 25, 30, 35 | 15 | G-FR1-A1-1 | -97-
$\Delta_{\min\text{SENS}}$ | -96.6-
$\Delta_{\min\text{SENS}}$ | -96.3-
$\Delta_{\min\text{SENS}}$ | -77.4 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 45, 50 | 15 | G-FR1-A1-4 | -90.6-
$\Delta_{\min\text{SENS}}$ | -90.2-
$\Delta_{\min\text{SENS}}$ | -89.9-
$\Delta_{\min\text{SENS}}$ | -71.4 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 10, 15, 20, 25, 30, 35 | 30 | G-FR1-A1-2 | -97.1-
$\Delta_{\min\text{SENS}}$ | -96.7-
$\Delta_{\min\text{SENS}}$ | -96.4-
$\Delta_{\min\text{SENS}}$ | -78.4 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 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}}$ | -90.2-
$\Delta_{\min\text{SENS}}$ | -71.4 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 10, 15, 20, 25, 30, 35 | 60 | G-FR1-A1-9 | -96.5-
$\Delta_{\min\text{SENS}}$ | -96.1-
$\Delta_{\min\text{SENS}}$ | -95.8-
$\Delta_{\min\text{SENS}}$ | -78.4 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -91-
$\Delta_{\min\text{SENS}}$ | -90.6-
$\Delta_{\min\text{SENS}}$ | -90.3-
$\Delta_{\min\text{SENS}}$ | -71.6 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | + +NOTE: Wanted and interfering signal are placed adjacently around $F_c$ , where the $F_c$ is defined for *IAB-DU channel bandwidth* of the wanted signal according to the table 5.4.2.2-1 in TS 38.104 [4]. The aggregated wanted and interferer signal shall be centred in the IAB-DU channel bandwidth of the wanted signal. + +**Table 7.9.5.1-2: Medium Range IAB-DU in-channel selectivity** + +| NR channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel (annex A.1) | Wanted signal mean power (dBm) | | | Interfering signal mean power (dBm) | Type of interfering signal | +|---------------------------------|--------------------------|-------------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|-------------------------------------|-------------------------------------------| +| | | | $f \leq 3.0$ GHz | $3.0 \text{ GHz} < f \leq 4.2$ GHz | $4.2 \text{ GHz} < f \leq 6.0$ GHz | | | +| 10, 15, 20, 25, 30, 35 | 15 | G-FR1-A1-1 | -92-
$\Delta_{\min\text{SENS}}$ | -91.6-
$\Delta_{\min\text{SENS}}$ | -91.3-
$\Delta_{\min\text{SENS}}$ | -72.4 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 45, 50 | 15 | G-FR1-A1-4 | -85.6-
$\Delta_{\min\text{SENS}}$ | -85.2-
$\Delta_{\min\text{SENS}}$ | -84.9-
$\Delta_{\min\text{SENS}}$ | -66.4 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 10, 15, 20, 25, 30, 35 | 30 | G-FR1-A1-2 | -92.1-
$\Delta_{\min\text{SENS}}$ | -91.7-
$\Delta_{\min\text{SENS}}$ | -91.4-
$\Delta_{\min\text{SENS}}$ | -73.4 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 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}}$ | -85.2-
$\Delta_{\min\text{SENS}}$ | -66.4 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 10, 15, 20, 25, 30, 35 | 60 | G-FR1-A1-9 | -91.5-
$\Delta_{\min\text{SENS}}$ | -91.1-
$\Delta_{\min\text{SENS}}$ | -90.8-
$\Delta_{\min\text{SENS}}$ | -73.4 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -86-
$\Delta_{\min\text{SENS}}$ | -85.6-
$\Delta_{\min\text{SENS}}$ | -85.3-
$\Delta_{\min\text{SENS}}$ | -66.6 - $\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | + +NOTE: Wanted and interfering signal are placed adjacently around $F_c$ , where the $F_c$ is defined for *IAB-DU channel bandwidth* of the wanted signal according to the table 5.4.2.2-1 in TS 38.104 [4]. The aggregated wanted and interferer signal shall be centred in the IAB-DU channel bandwidth of the wanted signal. + +**Table 7.9.5.1-3: Local area IAB-DU in-channel selectivity** + +| NR channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel (annex A.1) | Wanted signal mean power (dBm) | | | Interfering signal mean power (dBm) | Type of interfering signal | +|---------------------------------|--------------------------|-------------------------------------------|--------------------------------------|--------------------------------------------|--------------------------------------|---------------------------------------|-------------------------------------------| +| | | | $f \leq 3.0$ GHz | $3.0 \text{ GHz} < f \leq 4.2 \text{ GHz}$ | $4.2 \text{ GHz} < f \leq 6.0$ GHz | | | +| 10, 15, 20, 25, 30, 35 | 15 | G-FR1-A1-1 | -89-
$\Delta_{\min\text{SENS}}$ | -88.6-
$\Delta_{\min\text{SENS}}$ | -88.3-
$\Delta_{\min\text{SENS}}$ | -69.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 25 RBs | +| 40, 45, 50 | 15 | G-FR1-A1-4 | -82.6-
$\Delta_{\min\text{SENS}}$ | -82.2-
$\Delta_{\min\text{SENS}}$ | -81.9-
$\Delta_{\min\text{SENS}}$ | -63.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 15 kHz SCS, 100 RBs | +| 10, 15, 20, 25, 30, 35 | 30 | G-FR1-A1-2 | -89.1-
$\Delta_{\min\text{SENS}}$ | -88.7-
$\Delta_{\min\text{SENS}}$ | -88.4-
$\Delta_{\min\text{SENS}}$ | -70.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 10 RBs | +| 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}}$ | -82.2-
$\Delta_{\min\text{SENS}}$ | -63.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 30 kHz SCS, 50 RBs | +| 10, 15, 20, 25, 30, 35 | 60 | G-FR1-A1-9 | -88.5-
$\Delta_{\min\text{SENS}}$ | -88.1-
$\Delta_{\min\text{SENS}}$ | -87.8-
$\Delta_{\min\text{SENS}}$ | -70.4 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 5 RBs | +| 40, 45, 50, 60, 70, 80, 90, 100 | 60 | G-FR1-A1-6 | -83-
$\Delta_{\min\text{SENS}}$ | -82.6-
$\Delta_{\min\text{SENS}}$ | -82.3-
$\Delta_{\min\text{SENS}}$ | -63.6 -
$\Delta_{\min\text{SENS}}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 24 RBs | + +NOTE: Wanted and interfering signal are placed adjacently around $F_c$ , where the $F_c$ is defined for IAB-DU channel bandwidth of the wanted signal according to the table 5.4.2.2-1 in TS 38.104 [4]. The aggregated wanted and interferer signal shall be centred in the IAB-DU channel bandwidth of the wanted signal. + +### 7.9.5.2 IAB-DU type 2-O + +For IAB-DU type 2-O, the throughput shall be $\geq 95\%$ of the maximum throughput of the reference measurement channel as specified in annex A.1 with parameters specified in table 7.9.5.2-1. + +The wanted and interfering signals applies to each supported polarization, under the assumption of *polarization match*. + +**Table 7.9.5.2-1: OTA in-channel selectivity requirement for IAB-DU type 2-O** + +| NR channel bandwidth (MHz) | Subcarrier spacing (kHz) | Reference measurement channel (annex A.1) | Wanted signal mean power (dBm) (Note 2) | Interfering signal mean power (dBm) (Note 2) | Type of interfering signal | +|----------------------------|--------------------------|-------------------------------------------|----------------------------------------------------|---------------------------------------------------|-------------------------------------------| +| 50 | 60 | G-FR2-A1-4 | $EIS_{REFSENS\_50M} + 3.4 + \Delta_{FR2\_REFSENS}$ | $EIS_{REFSENS\_50M} + 10 + \Delta_{FR2\_REFSENS}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 32 RBs | +| 100, 200 | 60 | G-FR2-A1-1 | $EIS_{REFSENS\_50M} + 6.4 + \Delta_{FR2\_REFSENS}$ | $EIS_{REFSENS\_50M} + 13 + \Delta_{FR2\_REFSENS}$ | DFT-s-OFDM NR signal, 60 kHz SCS, 64 RBs | +| 50 | 120 | G-FR2-A1-5 | $EIS_{REFSENS\_50M} + 3.4 + \Delta_{FR2\_REFSENS}$ | $EIS_{REFSENS\_50M} + 10 + \Delta_{FR2\_REFSENS}$ | DFT-s-OFDM NR signal, 120 kHz SCS, 16 RBs | +| 100, 200, 400 | 120 | G-FR2-A1-2 | $EIS_{REFSENS\_50M} + 6.4 + \Delta_{FR2\_REFSENS}$ | $EIS_{REFSENS\_50M} + 13 + \Delta_{FR2\_REFSENS}$ | DFT-s-OFDM NR signal, 120 kHz SCS, 32 RBs | + +NOTE 1: Wanted and interfering signal are placed adjacently around $F_c$ , where the $F_c$ is defined for *IAB-DU channel bandwidth* of the wanted signal according to the table 5.4.2.2-1 in TS 38.104 [4]. The aggregated wanted and interferer signal shall be centred in the IAB-DU channel bandwidth of the wanted signal. + +NOTE 2: $EIS_{REFSENS\_50M}$ is defined in TS 38.174 [2], clause 10.2.1.2. + +## 8 Radiated performance requirements + +### 8.1 IAB-DU performance requirements + +#### 8.1.1 General + +##### 8.1.1.1 Scope and definitions + +Radiated performance requirements specify the ability of the *IAB type 1-O* or *IAB type 2-O* to correctly demodulate radiated signals in various conditions and configurations. Radiated performance requirements are specified at the RIB. + +Radiated performance requirements for the BS are specified for the fixed reference channels and propagation conditions defined in TS 38.174 [2] annex A and annex G, respectively. The requirements only apply to those FRCs that are supported by the IAB-DU. + +The radiated performance requirements for *IAB type 1-O* and for the *IAB type 2-O* are limited to two OTA *demodulation branches* as described in clause 8.1.1.2. Conformance requirements can only be tested for 1 or 2 *demodulation branches* depending on the number of polarizations supported by the IAB-DU, with the required SNR applied separately per polarization. + +NOTE: IAB-DU 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 a IAB-DU supporting CA are defined in terms of single carrier requirements. + +The method of synchronization with the TE is left to implementation. Neither the use of downlink signal configuration nor the use of proprietary means is precluded. In tests performed with signal generators a synchronization signal may be provided between the IAB-DU and the signal generator, or a common (e.g., GNSS) source may be provided to both IAB node and the signal generator, to enable correct timing of the wanted signal. + +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 a slot on a RIB. + +N is the noise energy in a bandwidth corresponding to the transmission bandwidth over the duration of a slot. + +### 8.1.1.2 OTA demodulation branches + +Radiated performance requirements are only specified for up to 2 *demodulation branches*. + +If the *IAB type 1-O*, or the *IAB type 2-O* uses polarization diversity and has the ability to maintain isolation between the signals for each of the *demodulation branches*, then radiated performance requirements can be tested for up to two *demodulation branches* (i.e. 1RX or 2RX test setups). When tested for two *demodulation branches*, each demodulation branch maps to one polarization. + +If the *IAB type 1-O*, or the *IAB type 2-O* does not use polarization diversity then radiated performance requirements can only be tested for a single *demodulation branch* (i.e. 1RX test setup). + +### 8.1.1.3 Applicability rule + +#### 8.1.1.3.1 General + +Unless otherwise stated, for a IAB-DU declared to support more than 2 demodulation branches (for *IAB type 1-O* and *IAB type 2-O*), the performance requirement tests for 2 demodulation branches shall apply, and the mapping between connectors and demodulation branches is up to BS implementation. + +The tests requiring more than [20] dB SNR level are set to N/A in the test requirements. + +#### 8.1.1.3.2 Applicability of PUSCH performance requirements + +##### 8.1.1.3.2.1 Applicability of requirements for different subcarrier spacings + +Unless otherwise stated, PUSCH requirement tests shall apply only for each subcarrier spacing declared to be supported (see D.7 in table 4.6-1). + +Unless otherwise stated, if IAB-DU supports more than one SCS then PUSCH requirement tests with highest modulation order (see D.109 in table 4.6-1) shall apply only with lowest supported SCS and PUSCH requirement tests with other modulation orders (see D.109 in table 4.6-1) shall apply only with highest supported SCS. Otherwise, all modulation orders are tested on supported SCS. + +##### 8.1.1.3.2.2 Applicability of requirements for different channel bandwidths + +For each subcarrier spacing declared to be supported, the test requirements for a specific channel bandwidth shall apply only if the IAB-DU supports it (see D.7 in table 4.6-1). + +Unless otherwise stated, for each subcarrier spacing declared to be supported, the tests shall be done only for the widest supported channel bandwidth. If performance requirement is not specified for this widest supported channel bandwidth, the tests shall be done by using performance requirement for the closest channel bandwidth lower than this widest supported bandwidth; the tested PRBs shall then be centered in this widest supported channel bandwidth. + +##### 8.1.1.3.2.3 Applicability of requirements for different configurations + +Unless otherwise stated, for *IAB type 1-O*, PUSCH requirement tests shall apply only for the mapping type declared to be supported (see D.100 in table 4.6-1). If both mapping type A and type B are declared to be supported, the tests shall be done for either type A or type B; the same chosen mapping type shall then be used for all tests. + +Unless otherwise stated, for *IAB type 2-O*, PUSCH requirement tests shall apply only for the additional DM-RS position declared to be supported (see D.101 in table 4.6-1). If both options (i.e., pos0 and pos1) are declared to be supported, the tests shall be done for pos1. + +Unless otherwise stated, for *IAB type 2-O*, PUSCH requirement tests with transform precoding disabled shall apply for the PT-RS option declared to be supported (see D.106 in table 4.6-1). If both PT-RS options (without and with PT-RS) + +are declared to be supported, the tests shall be done for either without or with PT-RS only; the same chosen option shall then be used for all tests. + +Unless otherwise stated, for *IAB type 2-O*, PUSCH requirement tests with transform precoding enabled shall be done for without PT-RS. + +#### 8.1.1.3.2.4 Applicability of requirements for uplink carrier aggregation + +The tests for uplink carrier aggregation shall be carried out according to the declaration (see D.108 in table 4.6-1). + +Unless otherwise stated, the tests for uplink carrier aggregation shall apply only for PUSCH with transform precoding disabled, and shall be conducted on per component carrier basis. + +#### 8.1.1.3.2.5 Applicability of requirements for TDD with different UL-DL patterns + +Unless otherwise stated, for each subcarrier spacing declared to be supported, if IAB-DU supports multiple TDD UL-DL patterns, only one of the supported TDD UL-DL patterns shall be used for all tests. + +#### 8.1.1.3.2.6 Applicability of requirements for transform precoding + +Unless otherwise stated, the tests with transform precoding enabled shall apply only, if the IAB-DU supports it (see D.110 in table 4.6-1). + +### 8.1.1.3.3 Applicability of PUCCH performance requirements + +#### 8.1.1.3.3.1 Applicability of requirements for different formats + +Unless otherwise stated, PUCCH requirement tests shall apply only for each PUCCH format declared to be supported (see D.102 in table 4.6-1). + +#### 8.1.1.3.3.2 Applicability of requirements for different subcarrier spacings + +Unless otherwise stated, PUCCH requirement tests shall apply only for each subcarrier spacing declared to be supported (see D.7 in table 4.6-1). If multiple subcarrier spacings are declared to be supported, each supported PUCCH format can be tested on one subcarrier spacing. + +#### 8.1.1.3.3.3 Applicability of requirements for different channel bandwidths + +For each subcarrier spacing declared to be supported by the IAB-DU, the test requirements for a specific channel bandwidth shall apply only if the IAB-DU supports it (see D.7 in table 4.6-1). + +Unless otherwise stated, for each subcarrier spacing declared to be supported, the tests shall be done only for the widest supported channel bandwidth. If performance requirement is not specified for this widest supported channel bandwidth, the tests shall be done by using performance requirement for the closest channel bandwidth lower than this widest supported bandwidth; the tested PRBs shall then be centered in this widest supported channel bandwidth. + +#### 8.1.1.3.3.4 Applicability of requirements for different configurations + +Unless otherwise stated, PUCCH format 3 requirement tests shall apply only for the additional DM-RS configuration declared to be supported (see D.104 in table 4.6-1). If both options (without and with additional DM-RS) are declared to be supported, the tests shall be done for either without or with additional DM-RS; the same chosen option shall then be used for all tests. + +Unless otherwise stated, PUCCH format 4 requirement tests shall apply only for the additional DM-RS configuration declared to be supported (see D.105 in table 4.6-1). If both options (without and with additional DM-RS) are declared to be supported, the tests shall be done for either without or with additional DM-RS; the same chosen option shall then be used for all tests. + +#### 8.1.1.3.3.5 Applicability of requirements for multi-slot PUCCH + +Unless otherwise stated, multi-slot PUCCH requirement tests shall apply only if the IAB-DU supports it (see D.107 in table 4.6-1). + +#### 8.1.1.3.4 Applicability of PRACH performance requirements + +##### 8.1.1.3.4.1 Applicability of requirements for different formats + +Unless otherwise stated, PRACH requirement tests shall apply only for PRACH formats declared to be supported (see D.103 in table 4.6-1). + +For IAB-DU declares to support more than one PRACH formats, limit the number of tests to any two cases chosen by the manufacturer. If IAB-DU declares to support more than one PRACH formats where formats for both long and short PRACH sequences are presented, require choosing formats with different sequences (see D.103 in table 4.6-1). + +##### 8.1.1.3.4.2 Applicability of requirements for different subcarrier spacings + +Unless otherwise stated, for each PRACH format with short sequence declared to be supported, for each FR, the tests shall apply only for the smallest supported subcarrier spacing in the FR (see D.103 in table 4.6-1). + +##### 8.1.1.3.4.3 Applicability of requirements for different channel bandwidths + +Unless otherwise stated, for the subcarrier spacing to be tested, the test requirements shall apply only for anyone channel bandwidth declared to be supported (see D.7 in table 4.6-1). + +### 8.1.2 Performance requirements for PUSCH + +#### 8.1.2.1 Performance requirements for PUSCH with transform precoding disabled + +##### 8.1.2.1.1 Definition and applicability + +The performance requirement of PUSCH is determined by a minimum required throughput for a given SNR. The required throughput is expressed as a fraction of maximum throughput for the FRCs listed in annex A. The performance requirements assume HARQ re-transmissions. + +Which specific test(s) are applicable to IAB-DU is based on the test applicability rules defined in clause 8.1.1.3.2. + +##### 8.1.2.1.2 Minimum Requirement + +For *BS type 1-O*, the minimum requirement is in TS 38.174 [2], clause 11.1.2.1.1. + +For *BS type 2-O*, the minimum requirement is in TS 38.174 [2], clause 11.1.2.2.1 + +##### 8.1.2.1.3 Test purpose + +The test shall verify the receiver's ability to achieve throughput under multipath fading propagation conditions for a given SNR. + +##### 8.1.2.1.4 Method of test + +###### 8.1.2.1.4.1 Initial conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: M, see clause 4.9.1. + +RF channels to be tested for carrier aggregation: $M_{\text{BW Channel CA}}$ ; see clause 4.9.1. + +Direction to be tested: OTA REFSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +## 8.1.2.1.4.2 Procedure + +- 1) Place the IAB-DU with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB-DU with the test system. +- 3) Set the IAB-DU in the declared direction to be tested. +- 4) Connect the IAB-DU tester generating the wanted signal, multipath fading simulators and AWGN generators to a test antenna via a combining network in OTA test setup, as shown in annex E.3. Each of the demodulation branch signals should be transmitted on one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to the corresponding UL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.1.2.1.4.2-1. + +**Table 8.1.2.1.4.2-1: Test parameters for testing PUSCH** + +| Parameter | | IAB type 1-O | IAB type 2-O | +|----------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|-------------------------------------------------------------------------|-----------------------------------------------| +| Transform precoding | | Disabled | | +| Cyclic prefix | | Normal | | +| Default TDD UL-DL pattern (Note) | | 15 kHz SCS:
3D1S1U, S=10D:2G:2U
30 kHz SCS:
7D1S2U, S=6D:4G:4U | 60 kHz and 120kHz SCS:
3D1S1U, S=10D:2G:2U | +| HARQ | Maximum number of HARQ transmissions | 4 | | +| | RV sequence | 0, 2, 3, 1 | | +| DM-RS | DM-RS configuration type | 1 | | +| | DM-RS duration | single-symbol DM-RS | | +| | Additional DM-RS position | pos1 | {pos0, pos1} | +| | Number of DM-RS CDM group(s) without data | 2 | | +| | Ratio of PUSCH EPRE to DM-RS EPRE | -3 dB | | +| | DM-RS port(s) | {0}, {0,1} | | +| | DM-RS sequence generation | $N_{ID}^0=0, n_{SCID}=0$ | | +| Time domain resource assignment | PUSCH mapping type | A, B | B | +| | Start symbol | 0 | 0 | +| | Allocation length | 14 | 10 | +| Frequency domain resource assignment | RB assignment | Full applicable test bandwidth | | +| | Frequency hopping | Disabled | | +| TPMI index for 2Tx two layer spatial multiplexing transmission | | 0 | | +| Code block group based PUSCH transmission | | Disabled | | +| PTRS configuration | Frequency density ( $K_{PT-RS}$ ) | N.A. | 2, Disabled | +| | Time density ( $L_{PT-RS}$ ) | N.A. | 1, Disabled | +| NOTE: The same requirements are applicable with different UL-DL patterns for IAB type 1-O and IAB type 2-O . | | | | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex J. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the IAB-DU receiver is as specified in clause 8.1.2.1.5.1 and 8.1.2.1.5.2 for *IAB type 1-O* and *IAB type 2-O* respectively, and that the SNR at the IAB-DU 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 in table 8.1.2.1.4.2-2. + +**Table 8.1.2.1.4.2-2: AWGN power level at the IAB-DU input** + +| IAB-DU type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------|---------------------------|-------------------------|---------------------------------------------------------------------------------------------------------| +| IAB type 1-O | 15 | 10 | $-83.3 - \Delta_{\text{OTAREFSENS}}$ dBm / 9.36 MHz | +| | | 20 | $-80.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 19.08 MHz | +| | 30 | 10 | $-83.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | +| | | 20 | $-80.4 - \Delta_{\text{OTAREFSENS}}$ dBm / 18.36 MHz | +| | | 40 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16 MHz | +| | | 100 | $-73.1 - \Delta_{\text{OTAREFSENS}}$ dBm / 98.28 MHz | +| IAB type 2-O | 60 | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15 \text{ dBm} / 47.52 \text{ MHz}$ | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18 \text{ dBm} / 95.04 \text{ MHz}$ | +| | 120 | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15 \text{ dBm} / 46.08 \text{ MHz}$ | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18 \text{ dBm} / 95.04 \text{ MHz}$ | +| | | 200 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 21 \text{ dBm} / 190.08 \text{ MHz}$ | + +NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. +NOTE 2: $\Delta_{\text{FR2\_REFSENS}} = -3 \text{ dB}$ as described in clause 7.1, since the OTA REFSENS reference direction (as declared in D.54 in table 4.6-1) is used for testing. +NOTE 3: $\text{EIS}_{\text{REFSENS\_50M}}$ as declared in D.28 in table 4.6-1. + +- 8) For reference channels applicable to the IAB-DU, measure the throughput. + +#### 8.1.2.1.5 Test Requirement + +##### 8.1.2.1.5.1 Test requirement for IAB type 1-O + +The throughput measured according to clause 8.1.2.1.4.2 shall not be below the limits for the SNR levels specified in table 8.1.2.1.5.1-1 to table 8.1.2.1.5.1-14 for 1Tx and for 2Tx two layer spatial multiplexing transmission. + +**Table 8.1.2.1.5.1-1: Void****Table 8.1.2.1.5.1-2: Test requirements for PUSCH with 70% of maximum throughput, Type A, 10 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|---------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-2 | pos1 | -1.9 | +| | | TDLC300-100 Low | D-FR1-A.2.3-2 | pos1 | 10.8 | +| | | TDLA30-10 Low | D-FR1-A.2.4-2 | pos1 | 12.8 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-9 | pos1 | 2.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-9 | pos1 | 19.1 | + +**Table 8.1.2.1.5.1-3: Test requirements for PUSCH with 70% of maximum throughput, Type A, 20 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-3 | pos1 | -1.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-3 | pos1 | 10.6 | +| | | TDLA30-10 Low | D-FR1-A.2.4-3 | pos1 | 13.0 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-10 | pos1 | 2.9 | +| | | TDLC300-100 Low | D-FR1-A.2.3-10 | pos1 | 19.1 | + +**Table 8.1.2.1.5.1-4: Test requirements for PUSCH with 70% of maximum throughput, Type A, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-4 | pos1 | -1.7 | +| | | TDLC300-100 Low | D-FR1-A.2.3-4 | pos1 | 10.8 | +| | | TDLA30-10 Low | D-FR1-A.2.4-4 | pos1 | 13.4 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-11 | pos1 | 2.1 | +| | | TDLC300-100 Low | D-FR1-A.2.3-11 | pos1 | 19.2 | + +**Table 8.1.2.1.5.1-5: Test requirements for PUSCH with 70% of maximum throughput, Type A, 20 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-5 | pos1 | -2.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-5 | pos1 | 10.8 | +| | | TDLA30-10 Low | D-FR1-A.2.4-5 | pos1 | 13.1 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-12 | pos1 | 2.1 | +| | | TDLC300-100 Low | D-FR1-A.2.3-12 | pos1 | 18.9 | + +**Table 8.1.2.1.5.1-6: Test requirements for PUSCH with 70% of maximum throughput, Type A, 40 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-6 | pos1 | -1.9 | +| | | TDLC300-100 Low | D-FR1-A.2.3-6 | pos1 | 10.6 | +| | | TDLA30-10 Low | D-FR1-A.2.4-6 | pos1 | 13.0 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-13 | pos1 | 2.1 | +| | | TDLC300-100 Low | D-FR1-A.2.3-13 | pos1 | 20.3 | + +**Table 8.1.2.1.5.1-7: Test requirements for PUSCH with 70% of maximum throughput, Type A, 100 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-7 | pos1 | -2.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-7 | pos1 | 10.8 | +| | | TDLA30-10 Low | D-FR1-A.2.4-7 | pos1 | 13.6 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-14 | pos1 | 2.2 | +| | | TDLC300-100 Low | D-FR1-A.2.3-14 | pos1 | 20.0 | + +**Table 8.1.2.1.5.1-8: Void****Table 8.1.2.1.5.1-9: Test requirements for PUSCH with 70% of maximum throughput, Type B, 10 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|---------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-2 | pos1 | -1.7 | +| | | TDLC300-100 Low | D-FR1-A.2.3-2 | pos1 | 11.1 | +| | | TDLA30-10 Low | D-FR1-A.2.4-2 | pos1 | 13.2 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-9 | pos1 | 2.8 | +| | | TDLC300-100 Low | D-FR1-A.2.3-9 | pos1 | 19.5 | + +**Table 8.1.2.1.5.1-10: Test requirements for PUSCH with 70% of maximum throughput, Type B, 20 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-3 | pos1 | -1.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-3 | pos1 | 11.0 | +| | | TDLA30-10 Low | D-FR1-A.2.4-3 | pos1 | 12.9 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-10 | pos1 | 2.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-10 | pos1 | 18.9 | + +**Table 8.1.2.1.5.1-11: Test requirements for PUSCH with 70% of maximum throughput, Type B, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-4 | pos1 | -1.8 | +| | | TDLC300-100 Low | D-FR1-A.2.3-4 | pos1 | 10.7 | +| | | TDLA30-10 Low | D-FR1-A.2.4-4 | pos1 | 13.1 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-11 | pos1 | 1.9 | +| | | TDLC300-100 Low | D-FR1-A.2.3-11 | pos1 | 19.3 | + +**Table 8.1.2.1.5.1-12: Test requirements for PUSCH with 70% of maximum throughput, Type B, 20 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-5 | pos1 | -2.3 | +| | | TDLC300-100 Low | D-FR1-A.2.3-5 | pos1 | 10.7 | +| | | TDLA30-10 Low | D-FR1-A.2.4-5 | pos1 | 13.1 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-12 | pos1 | 2.1 | +| | | TDLC300-100 Low | D-FR1-A.2.3-12 | pos1 | 19.0 | + +**Table 8.1.2.1.5.1-13: Test requirements for PUSCH with 70% of maximum throughput, Type B, 40 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-6 | pos1 | -1.9 | +| | | TDLC300-100 Low | D-FR1-A.2.3-6 | pos1 | 10.6 | +| | | TDLA30-10 Low | D-FR1-A.2.4-6 | pos1 | 13.1 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-13 | pos1 | 2.5 | +| | | TDLC300-100 Low | D-FR1-A.2.3-13 | pos1 | 19.5 | + +**Table 8.1.2.1.5.1-14: Test requirements for PUSCH with 70% of maximum throughput, Type B, 100 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-7 | pos1 | -1.9 | +| | | TDLC300-100 Low | D-FR1-A.2.3-7 | pos1 | 10.7 | +| | | TDLA30-10 Low | D-FR1-A.2.4-7 | pos1 | 13.7 | +| 2 | 2 | TDLB100-400 Low | D-FR1-A.2.1-14 | pos1 | 2.4 | +| | | TDLC300-100 Low | D-FR1-A.2.3-14 | pos1 | 20.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 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex C. + +#### 8.1.2.1.5.2 Test requirement for IAB type 2-O + +The throughput measured according to clause 8.1.2.1.4.2 shall not be below the limits for the SNR levels specified in table 8.1.2.1.5.2-1 to 8.1.2.1.5.2-7. + +**Table 8.1.2.1.5.2-1: Test requirements for PUSCH with 70% of maximum throughput, 50 MHz Channel Bandwidth, 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|-------|----------| +| 1 | 2 | TDLA30-300 Low | D-FR2-A.2.1-1 | pos0 | No | -1.4 | +| | | | D-FR2-A.2.1-13 | pos1 | No | -1.6 | +| | | TDLA30-300 Low | D-FR2-A.2.3-1 | pos0 | Yes | 12.6 | +| | | | | | No | 12.1 | +| | | | D-FR2-A.2.3-11 | pos1 | Yes | 11.3 | +| | | | | | No | 11.3 | +| | | TDLA30-75 Low | D-FR2-A.2.4-1 | pos0 | Yes | 14.3 | +| | | | | | No | 13.7 | +| | | | D-FR2-A.2.4-6 | pos1 | Yes | 14.0 | +| | | | | | No | 13.5 | +| | | TDLA30-300 Low | D-FR2-A.2.1-6 | pos0 | No | 2.3 | +| | | | D-FR2-A.2.1-18 | pos1 | No | 2.0 | +| 2 | 2 | TDLA30-300 Low | D-FR2-A.2.2-1 | pos0 | Yes | 16.0 | +| | | | No | | 15.1 | | +| | | TDLA30-300 Low | D-FR2-A.2.2-6 | pos1 | Yes | 14.6 | +| | | | | | No | 13.8 | + +**Table 8.1.2.1.5.2-2: Test requirements for PUSCH with 70% of maximum throughput, 100 MHz Channel Bandwidth, 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|-------|----------| +| 1 | 2 | TDLA30-300 Low | D-FR2-A.2.1-2 | pos0 | No | -1.5 | +| | | | D-FR2-A.2.1-14 | pos1 | No | -1.8 | +| | | TDLA30-300 Low | D-FR2-A.2.3-2 | pos0 | Yes | 12.8 | +| | | | | | No | 11.8 | +| | | | D-FR2-A.2.3-12 | pos1 | Yes | 11.8 | +| | | | | | No | 11.2 | +| | | TDLA30-75 Low | D-FR2-A.2.4-2 | pos0 | Yes | 14.8 | +| | | | | | No | 13.9 | +| | | | D-FR2-A.2.4-7 | pos1 | Yes | 14.3 | +| | | | | | No | 13.7 | +| | | TDLA30-300 Low | D-FR2-A.2.1-7 | pos0 | No | 2.3 | +| | | | D-FR2-A.2.1-19 | pos1 | No | 2.0 | +| 2 | 2 | TDLA30-300 Low | D-FR2-A.2.2-2 | pos0 | Yes | 16.8 | +| | | | No | | 15.7 | | +| | | TDLA30-300 Low | D-FR2-A.2.2-7 | pos1 | Yes | 14.6 | +| | | | | | No | 13.9 | + +**Table 8.1.2.1.5.2-3: Test requirements for PUSCH with 70% of maximum throughput, 50 MHz Channel Bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|-------|----------| +| 1 | 2 | TDLA30-300 Low | D-FR2-A.2.1-3 | pos0 | No | -1.2 | +| | | | D-FR2-A.2.1-15 | pos1 | No | -1.5 | +| | | TDLA30-300 Low | D-FR2-A.2.3-3 | pos0 | Yes | 12.2 | +| | | | | | No | 11.5 | +| | | | D-FR2-A.2.3-13 | pos1 | Yes | 11.5 | +| | | | | | No | 11.1 | +| | | TDLA30-75 Low | D-FR2-A.2.4-3 | pos0 | Yes | 14.3 | +| | | | | | No | 13.7 | +| | | | D-FR2-A.2.4-8 | pos1 | Yes | 13.8 | +| | | | | | No | 13.6 | +| | | TDLA30-300 Low | D-FR2-A.2.1-8 | pos0 | No | 2.2 | +| | | | D-FR2-A.2.1-20 | pos1 | No | 2.1 | +| 2 | | TDLA30-300 Low | D-FR2-A.2.2-3 | pos0 | Yes | 15.0 | +| | | | | | No | 14.4 | +| | | TDLA30-300 Low | D-FR2-A.2.2-8 | Pos1 | Yes | 14.7 | +| | | | | | No | 13.9 | + +**Table 8.1.2.1.5.2-4: Test requirements for PUSCH with 70% of maximum throughput, 100 MHz Channel Bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|-------|----------| +| 1 | 2 | TDLA30-300 Low | D-FR2-A.2.1-4 | pos0 | No | -1.8 | +| | | | D-FR2-A.2.1-16 | pos1 | No | -1.9 | +| | | TDLA30-300 Low | D-FR2-A.2.3-4 | pos0 | Yes | 12.5 | +| | | | | | No | 11.1 | +| | | | D-FR2-A.2.3-14 | pos1 | Yes | 11.7 | +| | | | | | No | 11.1 | +| | | TDLA30-75 Low | D-FR2-A.2.4-4 | pos0 | Yes | 14.1 | +| | | | | | No | 13.5 | +| | | | D-FR2-A.2.4-9 | pos1 | Yes | 14.0 | +| | | | | | No | 13.4 | +| | | TDLA30-300 Low | D-FR2-A.2.1-9 | pos0 | No | 2.2 | +| | | | D-FR2-A.2.1-21 | pos1 | No | 2.0 | +| 2 | | TDLA30-300 Low | D-FR2-A.2.2-4 | pos0 | Yes | 14.7 | +| | | | | | No | 14.0 | +| | | TDLA30-300 Low | D-FR2-A.2.2-9 | pos1 | Yes | 14.3 | +| | | | | | No | 13.7 | + +**Table 8.1.2.1.5.2-5: Test requirements for PUSCH with 70% of maximum throughput, 200 MHz Channel Bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | PT-RS | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|-------|----------| +| 1 | 2 | TDLA30-300 Low | D-FR2-A.2.1-5 | pos0 | No | -1.5 | +| | | | D-FR2-A.2.1-17 | pos1 | No | -1.8 | +| | | TDLA30-300 Low | D-FR2-A.2.3-5 | pos0 | Yes | 11.9 | +| | | | | | No | 11.5 | +| | | | D-FR2-A.2.3-15 | pos1 | Yes | 11.8 | +| | | | | | No | 11.3 | +| | | TDLA30-75 Low | D-FR2-A.2.4-5 | pos0 | Yes | 14.7 | +| | | | | | No | 14.0 | +| | | | D-FR2-A.2.4-10 | pos1 | Yes | 14.3 | +| | | | | | No | 13.9 | +| 2 | | TDLA30-300 Low | D-FR2-A.2.1-10 | pos0 | No | 2.2 | +| | | | D-FR2-A.2.1-22 | pos1 | No | 1.9 | +| | | TDLA30-300 Low | D-FR2-A.2.2-5 | pos0 | Yes | 14.8 | +| | | | | | No | 14.1 | +| | | | D-FR2-A.2.2-10 | pos1 | Yes | 14.4 | +| | | | | | No | 13.8 | + +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.1.2.2 Performance requirements for PUSCH with transform precoding enabled + +### 8.1.2.2.1 Definition and applicability + +The performance requirement of PUSCH is determined by a minimum required throughput for a given SNR. The required throughput is expressed as a fraction of maximum throughput for the FRCs listed in annex A. The performance requirements assume HARQ re-transmissions. + +Which specific test(s) are applicable to IAB-DU is based on the test applicability rules defined in clause 8.1.1.3.2. + +### 8.1.2.2.2 Minimum Requirement + +For IAB type 1-O, the minimum requirement is in TS 38.174 [2], clause 11.1.2.1.2. + +For IAB type 2-O, the minimum requirement is in TS 38.174 [2], clause 11.1.2.2.2. + +### 8.1.2.2.3 Test Purpose + +The test shall verify the receiver's ability to achieve throughput under multipath fading propagation conditions for a given SNR. + +### 8.1.2.2.4 Method of test + +#### 8.1.2.2.4.1 Initial Conditions + +Test environment: Normal, see clause B.2. + +RF channels to be tested for single carrier: M, see clause 4.9.1. + +Direction to be tested: OTA REFSSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +## 8.1.2.2.4.2 Procedure + +- 1) Place the IAB-DU with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB-DU with the test system. +- 3) Set the IAB-DU in the declared direction to be tested. +- 4) Connect the IAB-DU tester generating the wanted signal, multipath fading simulators and AWGN generators to a test antenna via a combining network in OTA test setup, as shown in annex E.3. Each of the demodulation branch signals should be transmitted on one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to the corresponding UL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.1.2.2.4.2-1. + +**Table 8.1.2.2.4.2-1: Test parameters for testing PUSCH** + +| Parameter | | IAB type 1-O | IAB type 2-O | +|-------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------|-----------------------------------------------| +| Transform precoding | | Enabled | | +| Cyclic prefix | | Normal | | +| Default TDD UL-DL pattern (Note) | | 15 kHz SCS:
3D1S1U, S=10D:2G:2U
30 kHz SCS:
7D1S2U, S=6D:4G:4U | 60 kHz and 120kHz SCS:
3D1S1U, S=10D:2G:2U | +| HARQ | Maximum number of HARQ transmissions | 4 | | +| | RV sequence | 0, 2, 3, 1 | | +| DM-RS | DM-RS configuration type | 1 | | +| | DM-RS duration | single-symbol DM-RS | | +| | Additional DM-RS position | pos1 | pos0, pos1 | +| | Number of DM-RS CDM group(s) without data | 2 | | +| | Ratio of PUSCH EPRE to DM-RS EPRE | -3 dB | | +| | DM-RS port(s) | 0 | | +| | DM-RS sequence generation | $N_{ID}^0=0$ , group hopping and sequence hopping are disabled | | +| Time domain resource assignment | PUSCH mapping type | A, B | B | +| | Start symbol | 0 | | +| | Allocation length | 14 | | +| Frequency domain resource assignment | RB assignment | 15 kHz SCS: 25 PRBs in the middle of the test bandwidth
30 kHz SCS: 24 PRBs in the middle of the test bandwidth | 30 PRBs in the middle of the test bandwidth | +| | Frequency hopping | Disabled | | +| Code block group based PUSCH transmission | | Disabled | | +| PT-RS | | Not configured | | +| NOTE: The same requirements are applicable to TDD with different UL-DL patterns for IAB type 1-O , and IAB type 2-O . | | | | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex J. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the IAB-DU receiver is as specified in clause 8.1.2.2.5.1 and 8.1.2.2.5.2 for *IAB type 1-O* and *IAB type 2-O* respectively, and that the SNR at the IAB-DU 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 in table 8.1.2.2.4.2-2. + +**Table 8.1.2.2.4.2-2: AWGN power level at the BS input** + +| IAB-DU type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------|---------------------------|-------------------------|--------------------------------------------------------------------------------------------------------| +| IAB type 1-O | 15 | 5 | $-86.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz | +| | 30 | 10 | $-83.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | +| IAB type 2-O | 60 | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15 \text{ dBm} / 47.52 \text{ MHz}$ | +| | 120 | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15 \text{ dBm} / 46.08 \text{ MHz}$ | + +NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. +NOTE 2: $\Delta_{\text{FR2\_REFSENS}} = -3 \text{ dB}$ as described in clause 7.1, since the OTA REFSENS reference direction (as declared in D.54 in table 4.6-1) is used for testing. +NOTE 3: $\text{EIS}_{\text{REFSENS\_50M}}$ as declared in D.28 in table 4.6-1. + +8) For reference channels applicable to the IAB-DU, measure the throughput. + +#### 8.1.2.2.5 Test Requirement + +##### 8.1.2.2.5.1 Test requirement for *IAB type 1-O* + +The throughput measured according to clause 8.1.2.2.4.2 shall not be below the limits for the SNR levels specified in table 8.1.2.2.5.1-1 to table 8.1.2.2.5.1-4. + +**Table 8.1.2.2.5.1-1: Test requirements for PUSCH with 70% of maximum throughput, Type A, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-15 | pos1 | -1.8 | + +**Table 8.1.2.2.5.1-2: Test requirements for PUSCH with 70% of maximum throughput, Type A, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-16 | pos1 | -1.9 | + +**Table 8.1.2.2.5.1-3: Test requirements for PUSCH with 70% of maximum throughput, Type B, 5 MHz channel bandwidth, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-15 | pos1 | -1.7 | + +**Table 8.1.2.2.5.1-4: Test requirements for PUSCH with 70% of maximum throughput, Type B, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLB100-400 Low | D-FR1-A.2.1-16 | pos1 | -2.1 | + +#### 8.1.2.2.5.2 Test requirement for IAB type 2-O + +The throughput measured according to clause 8.1.2.2.4.2 shall not be below the limits for the SNR levels specified in table 8.1.2.2.5.2-1 to table 8.1.2.2.5.2-2. + +**Table 8.1.2.2.5.2-1: Test requirements for PUSCH with 70% of maximum throughput, Type B, 50 MHz channel bandwidth, 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLA30-300 Low | D-FR2-A.2.1-11 | Pos0 | -1.2 | +| | | | D-FR2-A.2.1-23 | pos1 | -1.3 | + +**Table 8.1.2.2.5.2-2: Test requirements for PUSCH with 70% of maximum throughput, Type B, 50 MHz channel bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | FRC (annex A) | Additional DM-RS position | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|----------------|---------------------------|----------| +| 1 | 2 | TDLA30-300 Low | D-FR2-A.2.1-12 | Pos0 | -1.2 | +| | | | D-FR2-A.2.1-24 | pos1 | -1.3 | + +#### 8.1.2.3 Performance requirements for UCI multiplexed on PUSCH + +##### 8.1.2.3.1 Definition and applicability + +The performance requirement of UCI multiplexed on PUSCH is determined by two parameters: block error probability (BLER) of CSI part 1 and block error probability of CSI part 2. The performance is measured by the required SNR at block error probability of CSI part 1 not exceeding 0.1 %, and the required SNR at block error probability of CSI part 2 not exceeding 1 %. + +The CSI part 1 BLER is defined as the probability of incorrectly decoding the CSI part 1 information when the CSI part 1 information is sent. + +The CSI part 2 BLER is defined as the probability of incorrectly decoding the CSI part 2 information when the CSI part 2 information is sent. + +In the test of UCI multiplexed on PUSCH, the UCI information only contains CSI part 1 and CSI part 2 information, there is no HACK/ACK information transmitted. + +The number of UCI information bit payload per slot is defined for two cases as follows: + +- 7 bits: 5 bits in CSI part 1, 2 bits in CSI part 2 +- 40 bits: 20 bits in CSI part 1, 20 bits in CSI part 2 + +The 7 bits UCI information case is further defined with the bitmap $[c0\ c1\ c2\ c3\ c4] = [0\ 1\ 0\ 1\ 0]$ for CSI part 1 information, where c0 is mapping to the RI information, and with the bitmap $[c0\ c1] = [1\ 0]$ for CSI part 2 information. + +The 40 bits UCI information case is assumed random information bit selection. + +In both tests, PUSCH data, CSI part 1 and CSI part 2 are transmitted simultaneously. + +Which specific test(s) is applicable to IAB-DU is based on the test applicability rule defined in clause 8.1.1.3.2. + +##### 8.1.2.3.2 Minimum Requirement + +For IAB type 1-O, the minimum requirement is in TS 38.174 [2] clause 11.1.2.1.3. + +For *IAB type 2-O*, the minimum requirement is in TS 38.174 [2] clause 11.1.2.2.3. + +#### 8.1.2.3.3 Test Purpose + +The test shall verify the receiver's ability to detect UCI with CSI part 1 and CSI part 2 bits multiplexed on PUSCH under multipath fading propagation conditions for a given SNR. + +#### 8.1.2.3.4 Method of test + +##### 8.1.2.3.4.1 Initial Conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1 + +Direction to be tested: OTA REFSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +##### 8.1.2.3.4.2 Procedure + +- 1) Place the IAB-DU with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB-DU with the test system. +- 3) Set the IAB-DU in the declared direction to be tested. +- 4) Connect the IAB-DU tester generating the wanted signal, multipath fading simulators and AWGN generators to a test antenna via a combining network in OTA test setup, as shown in annex E.3. Each of the demodulation branch signals should be transmitted on one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured to the corresponding UL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.1.2.3.4.2-1. The UCI information bit payload per slot is equal to 7bits with CSI part 1 5bits, CSI part 2 2bits, and the UCI information bit payload per slot is equal to 40 bits with CSI part 1 20bits, CSI part 2 20 bits. + +**Table: 8.1.2.3.4.2-1 Test parameters for testing UCI multiplexed on PUSCH** + +| Parameter | | IAB type 1-O | IAB type 2-O | +|-------------------------------------------|-------------------------------------------------------------------|--------------------------------------|----------------------------------------| +| Transform precoding | | Disabled | | +| Cyclic prefix | | Normal | | +| Default TDD UL-DL pattern (Note) | | 30 kHz SCS:
7D1S2U,
S=6D:4G:4U | 120 kHz SCS:
3D1S1U,
S=10D:2G:2U | +| HARQ | Maximum number of HARQ transmissions | 1 | | +| | RV sequence | 0 | | +| DM-RS | DM-RS configuration type | 1 | | +| | DM-RS duration | Single-symbol DM-RS | | +| | Additional DM-RS position | pos1 | pos0,pos1 | +| | Number of DM-RS CDM group(s) without data | 2 | | +| | Ratio of PUSCH EPRE to DM-RS EPRE | -3 dB | | +| | DM-RS port(s) | {0} | {0} | +| | DM-RS sequence generation | $N_{ID}^0=0, n_{SCID}=0$ | | +| Time domain resource assignment | PUSCH mapping type | A,B | B | +| | Start symbol | 0 | | +| | Allocation length | 14 | 10 | +| Frequency domain resource assignment | RB assignment | Full applicable test bandwidth | | +| | Frequency hopping | Disabled | | +| Code block group based PUSCH transmission | | Disabled | | +| PT-RS configuration | PT-RS | Disabled | Enabled | +| | Frequency density ( $K_{PT-RS}$ ) | N.A. | 2 | +| | Time density ( $L_{PT-RS}$ ) | N.A. | 1 | +| UCI | Number of CSI part1 and CSI part2 information bit payload scaling | {5, 2}, {20,20} | | +| | betaOffsetACK-Index1 | 1 | | +| | betaOffsetCSI-Part1-Index1 and betaOffsetCSI-Part1-Index2 | 11 | | +| | betaOffsetCSI-Part2-Index1 and betaOffsetCSI-Part2-Index2 | 13 | | +| | UCI partition for frequency hopping | Disabled | | +| | | | | +| | | | | + +NOTE: The same requirements are applicable to TDD with different UL-DL patterns for *IAB type 1-O* and *IAB type 2-O*. + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex J. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the IAB-DU receiver is as specified in clause 8.1.2.3.5.1 and 8.1.2.3.5.2 for *IAB type 1-O* and *IAB type 2-O* respectively, 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 equal to the AWGN level in table 8.1.2.3.4.2-2. + +**Table 8.1.2.3.4.2-2: AWGN power level at the BS input** + +| IAB-DU type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------|----------------------------------|--------------------------------|-------------------------------------------------------------------| +| IAB type 1-O | 30 | 10 | $-83.6 - \Delta_{OTAREFSENS}$ dBm / 8.64 MHz | +| IAB type 2-O | 120 | 50 | $EIS_{REFSENS\_50M} + \Delta_{FR2\_REFSENS} + 15$ dBm / 46.08 MHz | + +NOTE 1: $\Delta_{OTAREFSENS}$ as declared in D.53 in table 4.6-1 and clause 7.1. + +NOTE 2: $\Delta_{FR2\_REFSENS} = -3$ dB as declared in clause 7.1, since the OTA REFSENS reference direction (as declared in D.54 in table 4.6-1) is used for testing. + +NOTE 3: $EIS_{REFSENS\_50M}$ as declared in D.28 in table 4.6-1. + +- 8) The signal generator sends a test pattern where UCI with CSI part 1 and CSI part 2 information can be multiplexed on PUSCH. The following statistics are kept: the number of incorrectly decoded CSI part 1 + +information transmitted, the number of incorrectly decoded CSI part 2 information transmitted during UCI multiplexed on PUSCH transmission. + +### 8.1.2.3.5 Test Requirement + +#### 8.1.2.3.5.1 Test requirement for IAB type 1-O + +The fraction of incorrectly decoded UCI with CSI part 1 according to clause 8.1.2.3.4.2 shall be less than 0.1 % for the SNR listed in table 8.1.2.3.5.1-1 and table 8.1.2.3.5.1-2. The fraction of incorrectly decoded UCI with CSI part 2 according to clause 8.1.2.3.4.2 shall be less than 1 % for the SNR listed in table 8.1.2.3.5.1-3 and table 8.1.2.3.5.1-4. + +**Table 8.1.2.3.5.1-1: Test requirements for UCI multiplexed on PUSCH, Type A, CSI part 1, 10 MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex J) | UCI bits (CSI part 1, CSI part 2) | Additional DM-RS position | FRC (Annex A) | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|-----------------------------------|---------------------------|---------------|----------| +| 1 | 2 | TDLC300-100 Low | 7 (5, 2) | pos1 | D-FR1-A.2.3-4 | 6.0 | +| | 2 | TDLC300-100 Low | 40 (20,20) | pos1 | D-FR1-A.2.3-4 | 4.9 | + +**Table 8.1.2.3.5.1-2: Test requirements for UCI multiplexed on PUSCH, Type B, CSI part 1, 10MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex J) | UCI bits (CSI part 1, CSI part 2) | Additional DM-RS position | FRC (Annex A) | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|-----------------------------------|---------------------------|---------------|----------| +| 1 | 2 | TDLC300-100 Low | 7 (5, 2) | pos1 | D-FR1-A.2.3-4 | 6.4 | +| | 2 | TDLC300-100 Low | 40 (20,20) | pos1 | D-FR1-A.2.3-4 | 4.7 | + +**Table 8.1.2.3.5.1-3: Test requirements for UCI multiplexed on PUSCH, Type A, CSI part 2, 10MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex J) | UCI bits (CSI part 1, CSI part 2) | Additional DM-RS position | FRC (Annex A) | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|-----------------------------------|---------------------------|---------------|----------| +| 1 | 2 | TDLC300-100 Low | 7 (5, 2) | pos1 | D-FR1-A.2.3-4 | 0.4 | +| | 2 | TDLC300-100 Low | 40 (20,20) | pos1 | D-FR1-A.2.3-4 | 3.0 | + +**Table 8.1.2.3.5.1-4: Test requirements for UCI multiplexed on PUSCH, Type B, CSI part 2, 10MHz channel bandwidth, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex J) | UCI bits (CSI part 1, CSI part 2) | Additional DM-RS position | FRC (Annex A) | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|-----------------------------------|---------------------------|---------------|----------| +| 1 | 2 | TDLC300-100 Low | 7 (5, 2) | pos1 | D-FR1-A.2.3-4 | 0.9 | +| | 2 | TDLC300-100 Low | 40 (20,20) | pos1 | D-FR1-A.2.3-4 | 3.2 | + +#### 8.1.2.3.5.2 Test requirement for IAB type 2-O + +The fraction of incorrectly decoded UCI with CSI part 1 measured according to clause 8.1.2.3.4.2 shall be less than 0.1 % for the SNR listed in table 8.1.2.3.5.2-1 and table 8.1.2.3.5.2-2. The fraction of incorrectly decoded UCI with CSI part 2 measured according to clause 8.1.2.3.4.2 shall be less than 1 % for the SNR listed in table 8.1.2.3.5.2-3 and table 8.1.2.3.5.2-4. + +**Table 8.1.2.3.5.2-1: Test requirements for UCI multiplexed on PUSCH, Type B, with PT-RS, CSI part 1, 50 MHz channel bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex J) | UCI bits (CSI part 1, CSI part 2) | Additional DM-RS position | FRC (Annex A) | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|-----------------------------------|---------------------------|----------------|----------| +| 1 | 2 | TDLA30-300 Low | 7 (5, 2) | pos0 | D-FR2-A.2.3-3 | 7.8 | +| | 2 | TDLA30-300 Low | 40 (20,20) | pos0 | D-FR2-A.2.3-3 | 6.4 | +| | 2 | TDLA30-300 Low | 7 (5, 2) | pos1 | D-FR2-A.2.3-13 | 8.4 | +| | 2 | TDLA30-300 Low | 40 (20,20) | pos1 | D-FR2-A.2.3-13 | 6.5 | + +**Table 8.1.2.3.5.2-2: Test requirements for UCI multiplexed on PUSCH, Type B, without PT-RS, CSI part 1, 50MHz channel bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex J) | UCI bits (CSI part 1, CSI part 2) | Additional DM-RS position | FRC (Annex A) | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|-----------------------------------|---------------------------|----------------|----------| +| 1 | 2 | TDLA30-300 Low | 7 (5, 2) | pos0 | D-FR2-A.2.3-3 | 7.7 | +| | 2 | TDLA30-300 Low | 40 (20,20) | pos0 | D-FR2-A.2.3-3 | 6.4 | +| | 2 | TDLA30-300 Low | 7 (5, 2) | pos1 | D-FR2-A.2.3-13 | 7.9 | +| | 2 | TDLA30-300 Low | 40 (20,20) | pos1 | D-FR2-A.2.3-13 | 6.1 | + +**Table 8.1.2.3.5.2-3: Test requirements for UCI multiplexed on PUSCH, Type B, with PT-RS, CSI part 2, 50 MHz channel bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex J) | UCI bits (CSI part 1, CSI part 2) | Additional DM-RS position | FRC (Annex A) | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|-----------------------------------|---------------------------|----------------|----------| +| 1 | 2 | TDLA30-300 Low | 7 (5, 2) | pos0 | D-FR2-A.2.3-3 | 1.7 | +| | 2 | TDLA30-300 Low | 40 (20,20) | pos0 | D-FR2-A.2.3-3 | 4.6 | +| | 2 | TDLA30-300 Low | 7 (5, 2) | pos1 | D-FR2-A.2.3-13 | 1.9 | +| | 2 | TDLA30-300 Low | 40 (20,20) | pos1 | D-FR2-A.2.3-13 | 4.6 | + +**Table 8.1.2.3.5.2-4: Test requirements for UCI multiplexed on PUSCH, Type B, Without PT-RS, CSI part 2, 50MHz channel bandwidth, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (Annex J) | UCI bits (CSI part 1, CSI part 2) | Additional DM-RS position | FRC (Annex A) | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|-----------------------------------|---------------------------|----------------|----------| +| 1 | 2 | TDLA30-300 Low | 7 (5, 2) | pos0 | D-FR2-A.2.3-3 | 1.7 | +| | 2 | TDLA30-300 Low | 40 (20,20) | pos0 | D-FR2-A.2.3-3 | 4.5 | +| | 2 | TDLA30-300 Low | 7 (5, 2) | pos1 | D-FR2-A.2.3-13 | 1.8 | +| | 2 | TDLA30-300 Low | 40 (20,20) | pos1 | D-FR2-A.2.3-13 | 4.3 | + +## 8.1.3 Performance requirements for PUCCH + +### 8.1.3.1 Performance requirements for PUCCH format 0 + +#### 8.1.3.1.1 Definition and applicability + +The performance requirement of single user PUCCH format 0 for ACK missed detection is determined by the two parameters: probability of false detection of the ACK and the probability of detection of ACK. The performance is measured by the required SNR at probability of detection equal to 0.99. The probability of false detection of the ACK shall be 0.01 or less. + +The probability of false detection of the ACK is defined as a conditional probability of erroneous detection of the ACK when input is only noise. + +The probability of detection of ACK is defined as conditional probability of detection of the ACK when the signal is present. + +The transient period as specified in TS 38.101-1 [16] clause 6.3.3.1 and TS 38.101-2 [17] clause 6.3.3.1 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the CC center, i.e. intra-slot frequency hopping is enabled. + +Which specific test(s) are applicable to IAB-DU is based on the test applicability rules defined in clause 8.1.1.3.3. + +#### 8.1.3.1.2 Minimum Requirement + +For *IAB type 1-O*, the minimum requirements are in TS 38.174 [2] clause 11.3.1.1 and 11.1.3.1.2. + +For *IAB type 2-O*, the minimum requirements are in TS 38.174 [2] clause 11.3.2.1 and 11.1.3.2.2. + +#### 8.1.3.1.3 Test Purpose + +The test shall verify the receiver's ability to detect ACK under multipath fading propagation conditions for a given SNR. + +#### 8.1.3.1.4 Method of test + +##### 8.1.3.1.4.1 Initial Conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested: single carrier M; see clause 4.9.1. + +Direction to be tested: OTA REFSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +##### 8.1.3.1.4.2 Procedure + +- 1) Place the IAB-DU with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB-DU with the test system. +- 3) Set the IAB-DU in the declared direction to be tested. +- 4) Connect the BS tester generating the wanted signal, multipath fading simulators and AWGN generators to a test antenna via a combining network in OTA test setup, as shown in annex E.3. Each of the demodulation branch signals should be transmitted on one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to TS 38.211 [7] and according to additional test parameters listed in table 8.1.3.1.4.2-1. + +**Table 8.1.3.1.4.2-1: Test parameters** + +| Parameter | IAB type 1-O | IAB type 2-O | +|--------------------------------------|-------------------------------------------------|-------------------------------------------------| +| number of UCI information bits | 1 | 1 | +| Number of PRBs | 1 | 1 | +| First PRB prior to frequency hopping | 0 | 0 | +| Intra-slot frequency hopping | N/A for 1 symbol
Enabled for 2 symbols | N/A for 1 symbol
Enabled for 2 symbols | +| First PRB after frequency hopping | The largest PRB index –
(number of PRBs – 1) | The largest PRB index –
(number of PRBs – 1) | +| Group and sequence hopping | neither | neither | +| Hopping ID | 0 | 0 | +| Initial cyclic shift | 0 | 0 | +| First symbol | 13 for 1 symbol
12 for 2 symbols | 13 for 1 symbol
12 for 2 symbols | +| Cyclic prefix | normal | | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex J.2. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the IAB-DU receiver is as specified in clause 8.1.3.1.5.1 and 8.1.3.1.5.2 for *IAB type 1-O* and *IAB type 2-O* respectively, and that the SNR at the IAB-DU 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 table 8.1.3.1.4.2-2. + +**Table 8.1.3.1.4.2-2: AWGN power level at the IAB-DU input** + +| IAB-DU type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------|---------------------------|-------------------------|-----------------------------------------------------------------------------------------| +| IAB type 1-O | 15 | 10 | $-80.3 - \Delta_{\text{OTAREFSENS}}$ dBm / 9.36 MHz | +| | | 20 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 19.08 MHz | +| | 30 | 10 | $-80.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | +| | | 20 | $-77.4 - \Delta_{\text{OTAREFSENS}}$ dBm / 18.36 MHz | +| | | 40 | $-74.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16 MHz | +| IAB type 2-O | 60 | 100 | $-70.1 - \Delta_{\text{OTAREFSENS}}$ dBm / 98.28 MHz | +| | | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15$ dBm / 47.52 MHz | +| | 120 | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18$ dBm / 95.04 MHz | +| | | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15$ dBm / 46.08 MHz | +| | | 200 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 21$ dBm / 190.08 MHz | + +NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. +NOTE 2: $\Delta_{\text{FR2\_REFSENS}} = -3$ dB as described in clause 7.1 since the OTA REFSENS reference direction (as declared in D.54 in table 4.6-1) is used for testing. +NOTE 3: $\text{EIS}_{\text{REFSENS\_50M}}$ as declared in D.28 in table 4.6-1. + +- 8) The signal generator sends a test pattern with the pattern outlined in figure 8.1.3.1.4.2-1. The following statistics are kept: the number of ACKs detected in the idle periods and the number of missed ACKs. + +![Figure 8.1.3.1.4.2-1: Test signal pattern for single user PUCCH format 0 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'ACK', representing detected acknowledgments. To the right of the third box are three dots, indicating a continuation of the pattern.](180f1fb534ad2c1d918ede57612b3fb0_img.jpg) + +Figure 8.1.3.1.4.2-1: Test signal pattern for single user PUCCH format 0 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'ACK', representing detected acknowledgments. To the right of the third box are three dots, indicating a continuation of the pattern. + +**Figure 8.1.3.1.4.2-1: Test signal pattern for single user PUCCH format 0 demodulation tests** + +### 8.1.3.1.5 Test Requirement + +#### 8.1.3.1.5.1 Test requirement for *IAB type 1-O* + +The fraction of falsely detected ACKs shall be less than 1% and the fraction of correctly detected ACKs shall be larger than 99% for the SNR listed in table 8.1.3.1.5.1-1 and in table 8.1.3.1.5.1-2. + +**Table 8.1.3.1.5.1-1: Test requirements for PUCCH format 0 and 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Number of OFDM symbols | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------|------------------------------|--------| +| | | | | 10 MHz | 20 MHz | +| 1 | 2 | TDLC300-100 Low | 1 | 9.4 | 9.9 | +| | | | 2 | 4.3 | 3.9 | + +**Table 8.1.3.1.5.1-2: Test requirements for PUCCH format 0 and 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Number of OFDM symbols | Channel bandwidth / SNR (dB) | | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------|------------------------------|--------|--------|---------| +| | | | | 10 MHz | 20 MHz | 40 MHz | 100 MHz | +| 1 | 2 | TDLC300-100 Low | 1 | 10.4 | 10.4 | 10.1 | 9.8 | +| | | | 2 | 4.8 | 4.2 | 4.4 | 4.1 | + +#### 8.1.3.1.5.2 Test requirement for IAB type 2-O + +The fraction of falsely detected ACKs shall be less than 1% and the fraction of correctly detected ACKs shall be larger than 99% for the SNR listed in table 8.1.3.1.5.2-1 and in table 8.1.3.1.5.2-2. + +**Table 8.1.3.1.5.2-1: Test requirements for PUCCH format 0 and 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Number of OFDM symbols | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------|------------------------------|---------| +| | | | | 50 MHz | 100 MHz | +| 1 | 2 | TDLA30-300 Low | 1 | 9.9 | 9.6 | +| | | | 2 | 4.8 | 4.6 | + +**Table 8.1.3.1.5.2-2: Test requirements for PUCCH format 0 and 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Number of OFDM symbols | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------|------------------------------|---------|---------| +| | | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | TDLA30-300 Low | 1 | 10.1 | 9.8 | 10.3 | +| | | | 2 | 4.7 | 4.4 | 4.6 | + +#### 8.1.3.2 Performance requirements for PUCCH format 1 + +##### 8.1.3.2.1 NACK to ACK detection + +###### 8.1.3.2.1.1 Definition and applicability + +The performance requirement of PUCCH format 1 for NACK to ACK detection is determined by the two parameters: probability of false detection of the ACK and the NACK to ACK detection probability. The performance is measured by the required SNR at probability of the NACK to ACK detection equal to 0.1% or less. The probability of false detection of the ACK shall be 0.01 or less. + +The probability of false detection of the ACK is defined as a conditional probability of erroneous detection of the ACK at particular bit position when input is only noise. Each false bit detection is counted as one error. + +The NACK to ACK detection probability is the probability of detecting an ACK bit when an NACK bit was sent on particular bit position. Each NACK bit erroneously detected as ACK bit is counted as one error. Erroneously detected NACK bits in the definition do not contain the NACK bits which are mapped from DTX, i.e. NACK bits received when DTX is sent should not be considered. + +The transient period as specified in TS 38.101-1 [16] and TS 38.101-2 [17] clause 6.3.3.1 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the CC center, i.e. intra-slot frequency hopping is enabled. + +Which specific test(s) are applicable to IAB-DU is based on the test applicability rules defined in clause 8.1.1.3.3. + +###### 8.1.3.2.1.2 Minimum Requirement + +For BS type 1-O, the minimum requirement is in TS 38.174 [2], clause 11.1.3.1.3. + +For BS type 2-O, the minimum requirement is in TS 38.174 [2], clause 11.1.3.2.3. + +#### 8.1.3.2.1.3 Test Purpose + +The test shall verify the receiver's ability not to falsely detect NACK bits as ACK bits under multipath fading propagation conditions for a given SNR. + +#### 8.1.3.2.1.4 Method of test + +##### 8.1.3.2.1.4.1 Initial Conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1 + +Direction to be tested: OTA REFSENS receiver target reference direction (see D.54 in table 4.6-1). + +##### 8.1.3.2.1.4.2 Procedure + +- 1) Place the IAB-DU with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB-DU with the test system. +- 3) Set the IAB-DU in the declared direction to be tested. +- 4) Connect the IAB-DU tester generating the wanted signal, multipath fading simulators and AWGN generators to a test antenna via a combining network in OTA test setup, as shown in annex E.3. Each of the demodulation branch signals should be transmitted on one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to TS 38.211 [7], and according to additional test parameters listed in table 8.1.3.2.1.4.2-1. + +**Table 8.1.3.2.1.4.2-1: Test parameters** + +| Parameter | Test | +|---------------------------------------------------------|----------------------------------------| +| Number of information bits | 2 | +| Number of PRBs | 1 | +| Number of symbols | 14 | +| First PRB prior to frequency hopping | 0 | +| Intra-slot frequency hopping | enabled | +| First PRB after frequency hopping | The largest PRB index - (nrofPRBs - 1) | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Initial cyclic shift | 0 | +| First symbol | 0 | +| Index of orthogonal cover code ( timeDomainOCC ) | 0 | +| Cyclic prefix | normal | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex J. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the IAB-DU receiver is as specified in clause 8.1.3.2.1.5.1 and 8.1.3.2.1.5.2 for *IAB type 1-O* and *IAB type 2-O* respectively, and that the SNR at the IAB-DU 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 in table 8.1.3.2.1.4.2-2. + +**Table 8.1.3.2.1.4.2-2: AWGN power level at the BS input** + +| IAB type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------|--------------------------|-------------------------|---------------------------------------------------------------------------------------------------------| +| IAB type 1-O | 15 kHz | 10 | $-80.3 - \Delta_{\text{OTAREFSENS}}$ dBm / 9.36 MHz | +| | | 20 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 19.08 MHz | +| | 30 kHz | 10 | $-80.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | +| | | 20 | $-77.4 - \Delta_{\text{OTAREFSENS}}$ dBm / 18.36 MHz | +| | | 40 | $-74.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16 MHz | +| | | 100 | $-70.1 - \Delta_{\text{OTAREFSENS}}$ dBm / 98.28 MHz | +| IAB type 2-O | 60 kHz | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15 \text{ dBm} / 47.52 \text{ MHz}$ | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18 \text{ dBm} / 95.04 \text{ MHz}$ | +| | | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15 \text{ dBm} / 46.08 \text{ MHz}$ | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18 \text{ dBm} / 95.04 \text{ MHz}$ | +| | | 200 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 21 \text{ dBm} / 190.08 \text{ MHz}$ | + +NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. +NOTE 2: $\Delta_{\text{FR2\_REFSENS}} = -3 \text{ dB}$ as described in clause 7.1, since the OTA REFSENS reference direction (as declared in D.54 in table 4.6-1) is used for testing. +NOTE 3: $\text{EIS}_{\text{REFSENS\_50M}}$ as declared in D.28 in table 4.6-1. + +- 8) The signal generator sends random codeword from applicable codebook, in regular time periods. The following statistics are kept: the number of ACK bits detected in the idle periods and the number of NACK bits detected as ACK. + +#### 8.1.3.2.1.5 Test Requirement + +##### 8.1.3.2.1.5.1 Test requirement for *IAB type 1-O* + +The fraction of falsely detected ACK bits shall be less than 1 % and the fraction of NACK bits falsely detected as ACK shall be less than 0.1 % for the SNR listed in tables 8.1.3.2.1.5.1-1 and table 8.1.3.2.1.5.1-2. + +**Table 8.1.3.2.1.5.1-1: Required SNR for PUCCH format 1 with 15 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|--------| +| | | | 10 MHz | 20 MHz | +| 1 | 2 | TDLC300-100 Low | -3.0 | -3.0 | + +**Table 8.1.3.2.1.5.1-2: Required SNR for PUCCH format 1 with 30 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|--------|--------|---------| +| | | | 10 MHz | 20 MHz | 40 MHz | 100 MHz | +| 1 | 2 | TDLC300-100 Low | -2.2 | -2.7 | -3.3 | -2.9 | + +##### 8.1.3.2.1.5.2 Test requirement for *IAB type 2-O* + +The fraction of falsely detected ACK bits shall be less than 1 % and the fraction of NACK bits falsely detected as ACK shall be less than 0.1 % for the SNR listed in tables 8.1.3.2.1.5.2-1 and table 8.1.3.2.1.5.2-2. + +**Table 8.1.3.2.1.5.2-1: Required SNR for PUCCH format 1 with 60 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|---------| +| | | | 50 MHz | 100 MHz | +| 1 | 2 | TDLA30-300 Low | -0.6 | -3.6 | + +**Table 8.1.3.2.1.5.2-2: Required SNR for PUCCH format 1 with 120 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|---------|---------| +| | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | TDLA30-300 Low | -3.3 | -3.3 | -2.4 | + +## 8.1.3.2.2 ACK missed detection + +### 8.1.3.2.2.1 Definition and applicability + +The performance requirement of PUCCH format 1 for ACK missed detection is determined by the two parameters: probability of false detection of the ACK and the probability of detection of ACK. The performance is measured by the required SNR at probability of detection equal to 0.99. The probability of false detection of the ACK shall be 0.01 or less. + +The probability of false detection of the ACK is defined as a conditional probability of erroneous detection of the ACK when input is only noise. + +The probability of detection of ACK is defined as conditional probability of detection of the ACK when the signal is present. + +The transient period as specified in TS 38.101-1 [16] and TS 38.101-2 [17] clause 6.3.3.1 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the CC center, i.e. intra-slot frequency hopping is enabled. + +Which specific test(s) are applicable to IAB DU is based on the test applicability rules defined in clause 8.1.1.3.3. + +### 8.1.3.2.2.2 Minimum Requirement + +For *IAB type 1-O*, the minimum requirement is in TS 38.174 [7], clause 11.1.3.1.3. + +For *IAB type 2-O*, the minimum requirement is in TS 38.174 [7], clause 11.1.3.2.3. + +### 8.1.3.2.2.3 Test Purpose + +The test shall verify the receiver's ability to detect ACK bits under multipath fading propagation conditions for a given SNR. + +### 8.1.3.2.2.4 Method of test + +#### 8.1.3.2.2.4.1 Initial Conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +Direction to be tested: OTA REFSSENS receiver target reference direction (see D.54 in table 4.6-1). + +## 8.1.3.2.2.4.2 Procedure + +- 1) Place the IAB DU with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB DU with the test system. +- 3) Set the IAB DU in the declared direction to be tested. +- 4) Connect the IAB DU tester generating the wanted signal, multipath fading simulators and AWGN generators to a test antenna via a combining network in OTA test setup, as shown in annex E.3. Each of the demodulation branch signals should be transmitted on one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to TS 38.211 [7], and according to additional test parameters listed in table 8.1.3.2.2.4.2-1. + +**Table 8.1.3.2.2.4.2-1: Test Parameters** + +| Parameter | Test | +|---------------------------------------------------------|----------------------------------------| +| Number of information bits | 2 | +| Number of PRBs | 1 | +| Number of symbols | 14 | +| First PRB prior to frequency hopping | 0 | +| Intra-slot frequency hopping | enabled | +| First PRB after frequency hopping | The largest PRB index – (nrofPRBs – 1) | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Initial cyclic shift | 0 | +| First symbol | 0 | +| Index of orthogonal cover code ( timeDomainOCC ) | 0 | +| Cyclic prefix | normal | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex J.2. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the IAB DU receiver is as specified in clause 8.1.3.2.2.5.1 and 8.1.3.2.2.5.2 for *IAB type 1-O* and *IAB type 2-O* respectively, and that the SNR at the IAB DU 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 in table 8.1.3.2.2.4.2-2. + +**Table 8.1.3.2.2.4.2-2: AWGN power level at the BS input** + +| IAB type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------|--------------------------|-------------------------|--------------------------------------------------------------------------------------------------------| +| IAB type 1-O | 15 kHz | 10 | $-80.3 - \Delta_{\text{OTAREFSENS}}$ dBm / 9.36 MHz | +| | | 20 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 19.08 MHz | +| | 30 kHz | 10 | $-80.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | +| | | 20 | $-77.4 - \Delta_{\text{OTAREFSENS}}$ dBm / 18.36 MHz | +| | | 40 | $-74.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16 MHz | +| | | 100 | $-70.1 - \Delta_{\text{OTAREFSENS}}$ dBm / 98.28 MHz | +| IAB type 2-O | 60 kHz | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15 \text{ dBm} / 47.52 \text{ MHz}$ | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18 \text{ dBm} / 95.04 \text{ MHz}$ | +| | | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15 \text{ dBm} / 46.08 \text{ MHz}$ | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18 \text{ dBm} / 95.04 \text{ MHz}$ | +| | | 200 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 21 \text{ dBm} / 47.52 \text{ MHz}$ | + +NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. + +NOTE 2: $\Delta_{\text{FR2\_REFSENS}} = -3 \text{ dB}$ as described in clause 7.1, since the OTA REFSENS reference direction (as declared in D.54 in table 4.6-1) is used for testing. + +NOTE 3: $\text{EIS}_{\text{REFSENS\_50M}}$ as declared in D.28 in table 4.6-1. + +- 8) The tester sends random codewords from applicable codebook, in regular time periods. The following statistics are kept: the number of ACK bits falsely detected in the idle periods and the number of missed ACK bits. Each falsely detected ACK bit in the idle periods is accounted as one error for the statistics of false ACK detection, and each missed ACK bit is accounted as one error for the statistics of missed ACK detection. + +Note that the procedure described in this clause for ACK missed detection has the same condition as that described in clause 8.1.3.2.1.4.2 for NACK to ACK detection. Both statistics are measured in the same testing. + +#### 8.1.3.2.2.5 Test Requirement + +##### 8.1.3.2.2.5.1 Test requirement for *IAB type 1-O* + +The fraction of falsely detected ACK bits shall be less than 1% and the fraction of correctly detected ACK bits shall be larger than 99% for the SNR listed in tables 8.1.3.2.2.5-1 and table 8.1.3.2.2.5-2. + +**Table 8.1.3.2.2.5.1-1: Required SNR for PUCCH format 1 with 15 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|--------| +| | | | 10 MHz | 20 MHz | +| 1 | 2 | TDLC300-100 Low | -3.8 | -4.4 | + +**Table 8.1.3.2.2.5.1-2: Required SNR for PUCCH format 1 with 30 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|--------|--------|---------| +| | | | 10 MHz | 20 MHz | 40 MHz | 100 MHz | +| 1 | 2 | TDLC300-100 Low | -3.3 | -3.8 | -3.8 | -3.6 | + +##### 8.1.3.2.2.5.2 Test requirement for *IAB type 2-O* + +The fraction of falsely detected ACK bits shall be less than 1% and the fraction of correctly detected ACK bits shall be larger than 99% for the SNR listed in tables 8.1.3.2.2.5.2-1 and table 8.1.3.2.2.5.2-2. + +**Table 8.1.3.2.2.5.2-1: Required SNR for PUCCH format 1 with 60 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|---------| +| | | | 50 MHz | 100 MHz | +| 1 | 2 | TDLA30-300 Low | -3.3 | -3.6 | + +**Table 8.1.3.2.2.5.2-2: Required SNR for PUCCH format 1 with 120 kHz SCS** + +| Number of TX antennas | Number of Demodulation Branches | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|---------|---------| +| | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | TDLA30-300 Low | -4.1 | -4.0 | -4.0 | + +### 8.1.3.3 Performance requirements for PUCCH format 2 + +#### 8.1.3.3.1 ACK missed detection performance requirements + +##### 8.1.3.3.1.1 Definition and applicability + +The performance requirement of PUCCH format 2 for ACK missed detection is determined by the two parameters: probability of false detection of the ACK and the probability of detection of ACK on the wanted signal. The performance is measured by the required SNR at probability of detection equal to 0.99. The probability of false detection of the ACK shall be 0.01 or less. + +The probability of false detection of the ACK is defined as a probability of erroneous detection of the ACK when input is only noise. + +The probability of detection of ACK is defined as probability of detection of the ACK when the signal is present. + +Which specific test(s) are applicable to IAB DU is based on the test applicability rules defined in clause 8.1.1.3. + +The transient period as specified in TS 38.101-1 [16] and TS 38.101-2 [17] clause 6.3.3.1 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the CC center, i.e. intra-slot frequency hopping is enabled. + +##### 8.1.3.3.1.2 Minimum Requirement + +For *IAB type 1-O*, the minimum requirement is in TS 38.174 [2] clause 11.1.3.1.4. + +For *IAB type 2-O*, the minimum requirement is in TS 38.174 [2] clause 11.1.3.2.4. + +##### 8.1.3.3.1.3 Test Purpose + +The test shall verify the receiver's ability to detect ACK bits under multipath fading propagation conditions for a given SNR. + +##### 8.1.3.3.1.4 Method of test + +###### 8.1.3.3.1.4.1 Initial Conditions + +Test environment: Normal, see clause B.2. + +RF channels to be tested for single carrier; M; see clause 4.9.1. + +Direction to be tested: OTA REFSENS *receiver target reference direction* (see D.54 in table.4.6-1). + +## 8.1.3.3.1.4.2 Procedure + +- 1) Place the IAB DU with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB DU with the test system. +- 3) Set the IAB DU in the declared direction to be tested. +- 4) Connect the IAB DU tester generating the wanted signal, multipath fading simulators and AWGN generators to a test antenna via a combining network in OTA test setup, as shown in annex E.3. Each of the demodulation branch signals should be transmitted one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to TS 38.211 [7], and according to additional test parameters listed in table 8.1.3.3.1.4.2-1. + +**Table 8.1.3.3.1.4.2-1: Test parameters** + +| Parameter | Value | +|--------------------------------------|--------------------------------------------| +| Modulation order | QPSK | +| First PRB prior to frequency hopping | 0 | +| Intra-slot frequency hopping | N/A | +| First PRB after frequency hopping | The largest PRB index - (Number of PRBs-1) | +| Number of PRBs | 4 | +| Number of symbols | 1 | +| The number of UCI information bits | 4 | +| First symbol | 13 | +| DM-RS sequence generation | $N_{ID}^0=0$ | +| Cyclic prefix | normal | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex J. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the IAB DU receiver is as specified in clause 8.1.3.3.1.5.1 and 8.1.3.3.1.5.2 for *IAB type 1-O* and *IAB type 2-O* respectively, and that the SNR at the IAB DU 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 in table 8.1.3.3.1.4.2-2. + +**Table 8.1.3.3.1.4.2-2: AWGN power level at the BS input** + +| IAB type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------|---------------------------|-------------------------|--------------------------------------------------------------------| +| IAB type 1-O | 15 kHz | 10 | $-80.3 - \Delta_{OTAREFSENS}$ dBm / 9.36 MHz | +| | | 20 | $-77.2 - \Delta_{OTAREFSENS}$ dBm / 19.08 MHz | +| | 30 kHz | 10 | $-80.6 - \Delta_{OTAREFSENS}$ dBm / 8.64 MHz | +| | | 20 | $-77.4 - \Delta_{OTAREFSENS}$ dBm / 18.36 MHz | +| | | 40 | $-74.2 - \Delta_{OTAREFSENS}$ dBm / 38.16 MHz | +| IAB type 2-O | 60 kHz | 100 | $-70.1 - \Delta_{OTAREFSENS}$ dBm / 98.28 MHz | +| | | 50 | $EIS_{REFSENS\_50M} + \Delta_{FR2\_REFSENS} + 15$ dBm / 47.52 MHz | +| | 120 kHz | 100 | $EIS_{REFSENS\_50M} + \Delta_{FR2\_REFSENS} + 18$ dBm / 95.04 MHz | +| | | 50 | $EIS_{REFSENS\_50M} + \Delta_{FR2\_REFSENS} + 15$ dBm / 46.08 MHz | +| | | 200 | $EIS_{REFSENS\_50M} + \Delta_{FR2\_REFSENS} + 21$ dBm / 190.08 MHz | + +NOTE 1: $\Delta_{OTAREFSENS}$ as declared in D.53 in table 4.6-1 and clause 7.1. +NOTE 2: $\Delta_{FR2\_REFSENS} = -3$ dB as declared in clause 7.1, since the OTA REFSENS receiver target reference direction (as declared in D.54 in table 4.6-1) is used for testing. +NOTE 3: $EIS_{REFSENS\_50M}$ as declared in D.28 in table 4.6-1. + +- 8) The tester sends a test pattern with pattern outlined in figure 8.1.3.3.1.4.2-1. The following statistics are kept: the number of ACK bits detected in the idle periods and the number of missed ACKs. + +![Figure 8.1.3.3.1.4.2-1: Test signal pattern for PUCCH format 2 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'ACK', representing detected ACK bits. To the right of the third box are three dots, indicating a continuation of the pattern.](4d9c52be1198628362ec7871f6e0f530_img.jpg) + +Figure 8.1.3.3.1.4.2-1: Test signal pattern for PUCCH format 2 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'ACK', representing detected ACK bits. To the right of the third box are three dots, indicating a continuation of the pattern. + +**Figure 8.1.3.3.1.4.2-1: Test signal pattern for PUCCH format 2 demodulation tests** + +**8.1.3.3.1.5 Test Requirement** + +**8.1.3.3.1.5.1 Test requirement for IAB type 1-O** + +The fraction of falsely detected ACKs shall be less than 1% and the fraction of correctly detected ACKs shall be larger than 99% for the SNR listed in table 8.1.3.3.1.5.1-1 and table 8.1.3.3.1.5.1-2. + +**Table 8.1.3.3.1.5.1-1: Required SNR for PUCCH format 2 with 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|--------| +| | | | 10 MHz | 20 MHz | +| 1 | 2 | TDLC300-100 Low | 6.2 | 6.5 | + +**Table 8.1.3.3.1.5.1-2: Required SNR for PUCCH format 2 with 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Channel bandwidth/ SNR (dB) | | | | +|-----------------------|---------------------------------|---------------------------------------------------------|-----------------------------|-------|-------|--------| +| | | | 10MHz | 20MHz | 40MHz | 100MHz | +| 1 | 2 | TDLC300-100 Low | 6.1 | 6.2 | 6.1 | 6.3 | + +**8.1.3.3.1.5.2 Test requirement for IAB type 2-O** + +The fraction of falsely detected ACKs shall be less than 1% and the fraction of correctly detected ACKs shall be larger than 99% for the SNR listed in table 8.1.3.3.1.5.2-1 and table 8.1.3.3.1.5.2-2. + +**Table 8.1.3.3.1.5.2-1: Required SNR for PUCCH format 2 with 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|---------| +| | | | 50 MHz | 100 MHz | +| 1 | 2 | TDLA30-300 Low | 7.3 | 7.8 | + +**Table 8.1.3.3.1.5.2-2: Required SNR for PUCCH format 2 with 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|---------|---------| +| | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | TDLA30-300 Low | 7.2 | 6.9 | 7.2 | + +### 8.1.3.3.2 UCI BLER performance requirements + +#### 8.1.3.3.2.1 Definition and applicability + +The UCI block error probability is defined as the probability of incorrectly decoding the UCI information when the UCI information is sent. The UCI information does not contain CSI part 2. + +Which specific test(s) are applicable to IAB DU is based on the test applicability rules defined in clause 8.1.2. + +The transient period as specified in TS 38.101-1 [16] and TS 38.101-2 [17] clause 6.3.3.1 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the CC center, i.e. intra-slot frequency hopping is enabled. + +#### 8.1.3.3.2.2 Minimum Requirement + +For *IAB type 1-O*, the minimum requirement is in TS 38.174 [2] clause 11.1.3.1.4. + +For *IAB type 2-O*, the minimum requirement is in TS 38.174 [2] clause 11.1.3.2.4. + +#### 8.1.3.3.2.3 Test Purpose + +The test shall verify the receiver's ability to detect UCI under multipath fading propagation conditions for a given SNR. + +#### 8.1.3.3.2.4 Method of test + +##### 8.1.3.3.2.4.1 Initial Conditions + +Test environment: Normal, see clause B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1 + +Direction to be tested: OTA REFSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +##### 8.1.3.3.2.4.2 Procedure + +- 1) Place the IAB DU with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB DU with the test system. +- 3) Set the IAB DU in the declared direction to be tested. +- 4) Connect the IAB DU tester generating the wanted signal, multipath fading simulators and AWGN generators to a test antenna via a combining network in OTA test setup, as shown in annex E.3. Each of the demodulation branches signals should be transmitted on each polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to TS 38.211 [7], and according to additional test parameters listed in table 8.1.3.3.2.4.2-1. + +**Table 8.1.3.3.2.4.2-1: Test parameters** + +| Parameter | Value | +|--------------------------------------|--------------------------------------------| +| Modulation order | QPSK | +| First PRB prior to frequency hopping | 0 | +| Intra-slot frequency hopping | enabled | +| First PRB after frequency hopping | The largest PRB index - (Number of PRBs-1) | +| Number of PRBs | 9 | +| Number of symbols | 2 | +| The number of UCI information bits | 22 | +| First symbol | 12 | +| DM-RS sequence generation | $N_{ID}^0=0$ | +| Cyclic prefix | normal | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex J. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the IAB DU receiver is as specified in clause 8.1.3.3.2.5.1 and 8.1.3.3.2.5.2 for *IAB type 1-O* and *IAB type 2-O* respectively, and that the SNR at the IAB DU 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 in table 8.3.3.2.4.2-2. + +**Table 8.1.3.3.2.4.2-2: AWGN power level at the BS input** + +| IAB type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------|----------------------------------|--------------------------------|-----------------------------------------------------------------------------------------| +| IAB type 1-O | 15 kHz | 10 | $-80.3 - \Delta_{\text{OTAREFSENS}}$ dBm / 9.36 MHz | +| | | 20 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 19.08 MHz | +| | 30 kHz | 10 | $-80.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | +| | | 20 | $-77.4 - \Delta_{\text{OTAREFSENS}}$ dBm / 18.36 MHz | +| | | 40 | $-74.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16 MHz | +| IAB type 2-O | 60 kHz | 100 | $-70.1 - \Delta_{\text{OTAREFSENS}}$ dBm / 98.28 MHz | +| | | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15$ dBm / 47.52 MHz | +| | 120 kHz | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18$ dBm / 95.04 MHz | +| | | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15$ dBm / 46.08 MHz | +| | | 200 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 21$ dBm / 190.08 MHz | + +NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. +NOTE 2: $\Delta_{\text{FR2\_REFSENS}} = -3$ dB as declared in clause 7.1. +NOTE 3: $\text{EIS}_{\text{REFSENS\_50M}}$ as declared in D.28 in table 4.6-1. + +- 8) The tester sends a test pattern with the pattern outlined in figure 8.1.3.3.2.4.2-1. The following statistics are kept: the number of incorrectly decoded UCI. + +![Figure 8.1.3.3.2.4.2-1: Test signal pattern for PUCCH format 2 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'UCI', arranged horizontally. To the right of the third box are three dots (ellipsis), indicating a sequence of such boxes.](4c6037bc72ca92a1c2e48825c56fb56f_img.jpg) + +Figure 8.1.3.3.2.4.2-1: Test signal pattern for PUCCH format 2 demodulation tests. The diagram shows three rectangular boxes, each containing the text 'UCI', arranged horizontally. To the right of the third box are three dots (ellipsis), indicating a sequence of such boxes. + +**Figure 8.1.3.3.2.4.2-1: Test signal pattern for PUCCH format 2 demodulation tests** + +**8.1.3.3.2.5 Test Requirement** + +**8.1.3.3.2.5.1 Test requirement for *IAB type 1-O*** + +The fraction of incorrectly decoded UCI is shall be less than 1% for the SNR listed in table 8.1.3.3.2.5.1-1 and table 8.1.3.3.2.5.1-2. + +**Table 8.1.3.3.2.5.1-1: Required SNR for PUCCH format 2 with 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | +|------------------------------|----------------------------------------|----------------------------------------------------------------|-------------------------------------|---------------| +| | | | 10 MHz | 20 MHz | +| 1 | 2 | TDLC300-100 Low | 1.4 | 1.8 | + +**Table 8.1.3.3.2.5.1-2: Required SNR for PUCCH format 2 with 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Channel bandwidth/ SNR (dB) | | | | +|-----------------------|---------------------------------|---------------------------------------------------------|-----------------------------|-------|-------|--------| +| | | | 10MHz | 20MHz | 40MHz | 100MHz | +| 1 | 2 | TDLC300-100 Low | 1.1 | 1.7 | 1.0 | 0.9 | + +#### 8.1.3.3.2.5.2 Test requirement for IAB type 2-O + +The fraction of incorrectly decoded UCI is shall be less than 1% for the SNR listed in table 8.1.3.3.2.5.2-1 and table 8.1.3.3.2.5.2-2. + +**Table 8.1.3.3.2.5.2-1: Required SNR for PUCCH format 2 with 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|---------| +| | | | 50 MHz | 100 MHz | +| 1 | 2 | TDLA30-300 Low | 3.2 | 1.7 | + +**Table 8.1.3.3.2.5.2-2: Required SNR for PUCCH format 2 with 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------------------|---------|---------| +| | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 2 | TDLA30-300 Low | 1.8 | 1.8 | 1.7 | + +### 8.1.3.4 Performance requirements for PUCCH format 3 + +#### 8.1.3.4.1 Definition and applicability + +The performance is measured by the required SNR at UCI block error probability not exceeding 1%. + +The UCI block error probability is defined as the conditional probability of incorrectly decoding the UCI information when the UCI information is sent. The UCI information does not contain CSI part 2. + +The transient period as specified in TS 38.101-1 [16] clause 6.3.3.1 and TS 38.101-2 [17] clause 6.3.3.1 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the CC center, i.e. intra-slot frequency hopping is enabled. + +Which specific test(s) are applicable to IAB DU is based on the test applicability rules defined in clause 8.1.1.3. + +#### 8.1.3.4.2 Minimum Requirement + +For *IAB type 1-O*, the minimum requirement is in TS 38.174 [7], clause 11.1.3.1.5. + +For *IAB type 2-O*, the minimum requirement is in TS 38.174 [7], clause 11.1.3.2.5. + +#### 8.1.3.4.3 Test Purpose + +The test shall verify the receiver's ability to detect UCI under multipath fading propagation conditions for a given SNR. + +#### 8.1.3.4.4 Method of test + +##### 8.1.3.4.4.1 Initial Conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1 + +Direction to be tested: + +- OTA REFSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +#### 8.1.3.4.4.2 Procedure + +- 1) Place the IAB DU with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB DU with the test system. +- 3) Set the IAB DU in the declared direction to be tested. +- 4) Connect the IAB DU tester generating the wanted signal, multipath fading simulators and AWGN generators to a test antenna via a combining network in OTA test setup, as shown in annex E.3. Each of the demodulation branch signals should be transmitted on one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to TS 38.211 [7], and according to additional test parameters listed in table 8.1.3.4.4.2-1. + +**Table 8.1.3.4.4.2-1: Test parameters** + +| Parameter | Test 1 | Test 2 | +|--------------------------------------|---------------------------------------------|--------| +| Modulation order | QPSK | | +| Cyclic prefix | normal | | +| First PRB prior to frequency hopping | 0 | | +| Intra-slot frequency hopping | enabled | | +| First PRB after frequency hopping | The largest PRB index - (Number of PRBs -1) | | +| Group and sequence hopping | neither | | +| Hopping ID | 0 | | +| Number of PRBs | 1 | 3 | +| Number of symbols | 14 | 4 | +| The number of UCI information bits | 16 | 16 | +| First symbol | 0 | 0 | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex J. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the IAB-DU receiver is as specified in clause 8.1.3.4.5.1 and 8.1.3.4.5.2 for *IAB type 1-O* and *IAB type 2-O* respectively, and the SNR at the IAB-DU 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 in table 8.1.3.4.4.2-2. + +**Table 8.1.3.4.4.2-2: AWGN power level at the BS input** + +| IAB type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------|--------------------------|-------------------------|---------------------------------------------------------------------------------------------------------| +| IAB type 1-O | 15 | 10 | $-80.3 - \Delta_{\text{OTAREFSENS}}$ dBm / 9.36MHz | +| | | 20 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 19.08MHz | +| | 30 | 10 | $-80.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64MHz | +| | | 20 | $-77.4 - \Delta_{\text{OTAREFSENS}}$ dBm / 18.36MHz | +| | | 40 | $-74.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16MHz | +| IAB type 2-O | 60 | 100 | $-70.1 - \Delta_{\text{OTAREFSENS}}$ dBm / 98.28MHz | +| | | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15 \text{ dBm} / 47.52\text{MHz}$ | +| | 120 | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18 \text{ dBm} / 95.04 \text{ MHz}$ | +| | | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15 \text{ dBm} / 46.08 \text{ MHz}$ | +| | | 200 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 21 \text{ dBm} / 190.08 \text{ MHz}$ | + +NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. +NOTE 2: $\Delta_{\text{FR2\_REFSENS}} = -3 \text{ dB}$ as described in clause 7.1, since the OTA REFSENS receiver target reference direction (as declared in D.54 in table 4.6-1) is used for testing. +NOTE 3: $\text{EIS}_{\text{REFSENS\_50M}}$ as declared in D.28 in table 4.6-1. + +### 8.1.3.4.5 Test Requirement + +#### 8.1.3.4.5.1 Test requirement for *IAB type 1-O* + +The fraction of incorrectly decoded UCI is shall be less than 1% for the SNR listed in table 8.1.3.4.5.1-1 and table 8.1.3.4.5.1-2. + +**Table 8.1.3.4.5.1-1: Required SNR for PUCCH format 3 with 15 kHz SCS** + +| Test Number | Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | | +|-------------|-----------------------|---------------------------------|---------------------------------------------------------|--------------------------------|------------------------------|--------| +| | | | | | 10 MHz | 20 MHz | +| 1 | 1 | 2 | TDLC300-100 Low | No additional DM-RS | 1.7 | 0.9 | +| | | | | Additional DM-RS | 1.1 | 0.5 | +| 2 | 1 | 2 | TDLC300-100 Low | No additional DM-RS | 2.8 | 2.6 | + +**Table 8.1.3.4.5.1-2: Required SNR for PUCCH format 3 with 30 kHz SCS** + +| Test Number | Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | | | | +|-------------|-----------------------|---------------------------------|---------------------------------------------------------|--------------------------------|------------------------------|--------|--------|---------| +| | | | | | 10 MHz | 20 MHz | 40 MHz | 100 MHz | +| 1 | 1 | 2 | TDLC300-100 Low | No additional DM-RS | 1.5 | 1.2 | 1.2 | 1.5 | +| | | | | Additional DM-RS | 1.1 | 0.9 | 0.6 | 0.7 | +| 2 | 1 | 2 | TDLC300-100 Low | No additional DM-RS | 2.4 | 2.6 | 2.6 | 2.1 | + +#### 8.1.3.4.5.2 Test requirement for IAB type 2-O + +The fraction of incorrectly decoded UCI is shall be less than 1% for the SNR listed in table 8.1.3.4.5.2-1 and table 8.1.3.4.5.2-2. + +**Table 8.1.3.4.5.2-1: Required SNR for PUCCH format 3 with 60 kHz SCS** + +| Test Number | Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | | +|-------------|-----------------------|---------------------------------|---------------------------------------------------------|--------------------------------|------------------------------|---------| +| | | | | | 50 MHz | 100 MHz | +| 1 | 1 | 2 | TDLA30-300 Low | No additional DM-RS | 2.2 | 1.3 | +| | | | | Additional DM-RS | 1.9 | 1.5 | +| 2 | 1 | 2 | TDLA30-300 Low | No additional DM-RS | 3.6 | 3.0 | + +**Table 8.1.3.4.5.2-2: Required SNR for PUCCH format 3 with 120 kHz SCS** + +| Test Number | Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | | | +|-------------|-----------------------|---------------------------------|---------------------------------------------------------|--------------------------------|------------------------------|---------|---------| +| | | | | | 50 MHz | 100 MHz | 200 MHz | +| 1 | 1 | 2 | TDLA30-300 Low | No additional DM-RS | 2.0 | 1.3 | 1.3 | +| | | | | Additional DM-RS | 1.9 | 2.0 | 1.5 | +| 2 | 1 | 2 | TDLA30-300 Low | No additional DM-RS | 1.7 | 3.5 | 2.0 | + +### 8.1.3.5 Performance requirements for PUCCH format 4 + +#### 8.1.3.5.1 Definition and applicability + +The performance is measured by the required SNR at UCI block error probability not exceeding 1%. + +The UCI block error probability is defined as the conditional probability of incorrectly decoding the UCI information when the UCI information is sent. The UCI information does not contain CSI part 2. + +The transient period as specified in TS 38.101-1 [16] and TS 38.101-2 [17] clause 6.3.3.1 is not taken into account for performance requirement testing, where the RB hopping is symmetric to the CC center, i.e. intra-slot frequency hopping is enabled. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.1.3.3. + +#### 8.1.3.5.2 Minimum Requirement + +For IAB type 1-O, the minimum requirement is in TS 38.174 [2], clause 11.1.3.1.6. + +For IAB type 2-O, the minimum requirement is in TS 38.174 [2], clause 11.1.3.2.6. + +#### 8.1.3.5.3 Test Purpose + +The test shall verify the receiver's ability to detect UCI under multipath fading propagation conditions for a given SNR. + +#### 8.1.3.5.4 Method of test + +##### 8.1.3.5.4.1 Initial Conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1 + +Direction to be tested: + +- OTA REFSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +#### 8.1.3.5.4.2 Procedure + +- 1) Place the IAB DU with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB DU with the test system. +- 3) Set the IAB DU in the declared direction to be tested. +- 4) Connect the IAB DU tester generating the wanted signal, multipath fading simulators and AWGN generators to a test antenna via a combining network in OTA test setup, as shown in annex E.3. Each of the demodulation branch signals should be transmitted on one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to TS 38.211 [7], and according to additional test parameters listed in table 8.1.3.4.2-1. + +**Table 8.1.3.5.4.2-1: Test parameters** + +| Parameter | Value | +|--------------------------------------|----------------------------------------------| +| Modulation order | QPSK | +| Cyclic prefix | normal | +| First PRB prior to frequency hopping | 0 | +| Number of PRBs | 1 | +| Intra-slot frequency hopping | enabled | +| First PRB after frequency hopping | The largest PRB index - (Number of PRBs - 1) | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Number of symbols | 14 | +| The number of UCI information bits | 22 | +| First symbol | 0 | +| Length of the orthogonal cover code | n2 | +| Index of the orthogonal cover code | n0 | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex J. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the IAB DU receiver is as specified in clause 8.1.3.5.5.1 and 8.1.3.5.5.2 for *IAB type 1-O* and *IAB type 2-O* respectively, and that the SNR at the IAB DU 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 in table 8.1.3.5.4.2-2. + +**Table 8.1.3.5.4.2-2: AWGN power level at the BS input** + +| IAB type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------|--------------------------|-------------------------|---------------------------------------------------------------------------------------------------------| +| IAB type 1-O | 15 | 10 | $-80.3 - \Delta_{\text{OTAREFSENS}}$ dBm / 9.36MHz | +| | | 20 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 19.08MHz | +| | 30 | 10 | $-80.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64MHz | +| | | 20 | $-77.4 - \Delta_{\text{OTAREFSENS}}$ dBm / 18.36MHz | +| | | 40 | $-74.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16MHz | +| | | 100 | $-70.1 - \Delta_{\text{OTAREFSENS}}$ dBm / 98.28MHz | +| IAB type 2-O | 60 | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15 \text{ dBm} / 47.52 \text{ MHz}$ | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18 \text{ dBm} / 95.04 \text{ MHz}$ | +| | 120 | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15 \text{ dBm} / 46.08 \text{ MHz}$ | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18 \text{ dBm} / 95.04 \text{ MHz}$ | +| | | 200 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 21 \text{ dBm} / 190.08 \text{ MHz}$ | + +NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. + +NOTE 2: $\Delta_{\text{FR2\_REFSENS}} = -3 \text{ dB}$ as described in clause 7.1, since the OTA REFSENS receiver target reference direction (as declared in D.54 in table 4.6-1) is used for testing. + +NOTE 3: $\text{EIS}_{\text{REFSENS\_50M}}$ as declared in D.28 in table 4.6-1. + +#### 8.1.3.5.5 Test Requirement + +##### 8.1.3.5.5.1 Test requirement for *IAB type 1-O* + +The fraction of incorrectly decoded UCI is shall be less than 1% for the SNR listed in table 8.1.3.5.5.1-1 and table 8.1.3.5.5.1-2. + +**Table 8.1.3.5.5.1-1: Required SNR for PUCCH format 4 with 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|--------------------------------|------------------------------|--------| +| | | | | 10 MHz | 20 MHz | +| 1 | 2 | TDLC300-100 Low | No additional DM-RS | 3.2 | 2.8 | +| | | | Additional DM-RS | 3.0 | 2.4 | + +**Table 8.1.3.5.5.1-2: Required SNR for PUCCH format 4 with 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | | | | +|-----------------------|---------------------------------|---------------------------------------------------------|--------------------------------|------------------------------|--------|--------|---------| +| | | | | 10 MHz | 20 MHz | 40 MHz | 100 MHz | +| 1 | 2 | TDLC300-100 Low | No additional DM-RS | 3.7 | 3.4 | 3.7 | 3.4 | +| | | | Additional DM-RS | 3.4 | 2.9 | 3.7 | 2.8 | + +##### 8.1.3.5.5.2 Test requirement for *IAB type 2-O* + +The fraction of incorrectly decoded UCI is shall be less than 1% for the SNR listed in table 8.1.3.5.5.2-1 and table 8.1.3.5.5.2-2. + +**Table 8.1.3.5.5.2-1: Required SNR for PUCCH format 4 with 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | | +|-----------------------|---------------------------------|---------------------------------------------------------|--------------------------------|------------------------------|---------| +| | | | | 50 MHz | 100 MHz | +| 1 | 2 | TDLA30-300 Low | No additional DM-RS | 3.6 | 3.3 | +| | | | Additional DM-RS | 3.7 | 4.1 | + +**Table 8.1.3.5.5.2-2: Required SNR for PUCCH format 4 with 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Additional DM-RS configuration | Channel bandwidth / SNR (dB) | | | +|-----------------------|---------------------------------|---------------------------------------------------------|--------------------------------|------------------------------|---------|--------| +| | | | | 50 MHz | 100 MHz | 200MHz | +| 1 | 2 | TDLA30-300 Low | No additional DM-RS | 3.4 | 3.4 | 4.1 | +| | | | Additional DM-RS | 4.2 | 4.4 | 3.8 | + +### 8.1.3.6 Performance requirements for multi-slot PUCCH + +#### 8.1.3.6.1 Performance requirements for multi-slot PUCCH format 1 + +##### 8.1.3.6.1.1 NACK to ACK detection + +###### 8.1.3.6.1.1.1 Definition and applicability + +The performance requirement of PUCCH format 1 for NACK to ACK detection is determined by the two parameters: probability of false detection of the ACK and the NACK to ACK detection probability. The performance is measured by the required SNR at probability of the NACK to ACK detection equal to 0.1% or less. The probability of false detection of the ACK shall be 0.01 or less. + +The probability of false detection of the ACK is defined as a conditional probability of erroneous detection of the ACK at particular bit position when input is only noise. Each false bit detection is counted as one error. + +The NACK to ACK detection probability is the probability of detecting an ACK bit when an NACK bit was sent on particular bit position. Each NACK bit erroneously detected as ACK bit is counted as one error. Erroneously detected NACK bits in the definition do not contain the NACK bits which are mapped from DTX, i.e. NACK bits received when DTX is sent should not be considered. + +Which specific test(s) are applicable to IAB DU is based on the test applicability rules defined in clause 8.1.1.3.3. + +###### 8.1.3.6.1.1.2 Minimum Requirement + +For *IAB type 1-O*, the minimum requirement is in TS 38.174 [2], clause 11.1.3.1.7. + +###### 8.1.3.6.1.1.3 Test Purpose + +###### 8.1.3.6.1.1.4 Method of test + +The test shall verify the receiver's ability not to falsely detect NACK bits as ACK bits under multipath fading propagation conditions for a given SNR. + +###### 8.1.3.6.1.1.4.1 Initial Conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1 + +Direction to be tested: OTA REFSSENS *receiver target reference direction* (D.54). + +## 8.1.3.6.1.1.4.2 Procedure + +- 1) Place the IAB DU with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB DU with the test system. +- 3) Set the IAB DU in the declared direction to be tested. +- 4) Connect the IAB DU tester generating the wanted signal, multipath fading simulators and AWGN generators to a test antenna via a combining network in OTA test setup, as shown in annex E.3. Each of the demodulation branch signals should be transmitted on one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to TS 38.211 [7], and according to additional test parameters listed in table 8.1.3.6.1.1.4.2-1. + +**Table 8.1.3.6.1.1.4.2-1: Test Parameters for multi-slot PUCCH format 1** + +| Parameter | Test | +|---------------------------------------------------------|----------------------------------------| +| Number of information bits | 2 | +| Number of PRBs | 1 | +| Number of symbols | 14 | +| First PRB prior to frequency hopping | 0 | +| Intra-slot frequency hopping | disabled | +| Inter-slot frequency hopping | enabled | +| First PRB after frequency hopping | The largest PRB index - (nrofPRBs – 1) | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Initial cyclic shift | 0 | +| First symbol | 0 | +| Index of orthogonal cover code ( timeDomainOCC ) | 0 | +| Number of slots for PUCCH repetition | 2 | +| Cyclic prefix | normal | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex J. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the IAB DU receiver is as specified in clause 8.1.3.6.1.1.5.1 for *IAB type 1-O*, and that the SNR at the IAB DU 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 in table 8.1.3.6.1.1.4.2-2. + +**Table 8.1.3.6.1.1.4.2-2: AWGN power level at the BS input** + +| IAB type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------------------------------------------------------------------------|--------------------------|-------------------------|------------------------------------------------------| +| IAB type 1-O | 15 kHz | 10 | $-80.3 - \Delta_{\text{OTAREFSENS}}$ dBm / 9.36 MHz | +| | | 20 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 19.08 MHz | +| | 30 kHz | 10 | $-80.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | +| | | 20 | $-77.4 - \Delta_{\text{OTAREFSENS}}$ dBm / 18.36 MHz | +| | | 40 | $-74.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16 MHz | +| | | 100 | $-70.1 - \Delta_{\text{OTAREFSENS}}$ dBm / 98.28 MHz | +| NOTE: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. | | | | + +- 8) The tester sends random codeword from applicable codebook, in regular time periods. The following statistics are kept: the number of ACK bits detected in the idle periods and the number of NACK bits detected as ACK. + +## 8.1.3.6.1.1.5 Test Requirement + +8.1.3.6.1.1.5.1 Test requirement for *IAB type 1-O* + +The fraction of falsely detected ACK bits shall be less than 1% and the fraction of NACK bits falsely detected as ACK shall be less than 0.1% for the SNR listed in table 8.1.3.6.1.1.5.1-1. + +**Table 8.1.3.6.1.1.5.1-1: Required SNR for multi-slot PUCCH format 1 with 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (Annex J) | Channel bandwidth (MHz) / | +|-----------------------|-----------------------|---------------------------------------------------------|---------------------------| +| | | | 40 MHz | +| 1 | 2 | TDLC-300-100 Low | -5.7 | + +## 8.1.3.6.1.2 ACK missed detection + +## 8.1.3.6.1.2.1 Definition and applicability + +The performance requirement of PUCCH format 1 for ACK missed detection is determined by the two parameters: probability of false detection of the ACK and the probability of detection of ACK. The performance is measured by the required SNR at probability of detection equal to 0.99. The probability of false detection of the ACK shall be 0.01 or less. + +The probability of false detection of the ACK is defined as a conditional probability of erroneous detection of the ACK when input is only noise. + +The probability of detection of ACK is defined as conditional probability of detection of the ACK when the signal is present. + +## 8.1.3.6.1.2.2 Minimum Requirement + +For *IAB type 1-O*, the minimum requirement is in TS 38.174 [2], clause 11.1.3.1.7. + +## 8.1.3.6.1.2.3 Test Purpose + +The test shall verify the receiver's ability to detect ACK bits under multipath fading propagation conditions for a given SNR. + +## 8.1.3.6.1.2.4 Method of test + +## 8.1.3.6.1.2.4.1 Initial Conditions + +Test environment: Normal; see annex B.2. + +RF channels to be tested for single carrier (SC): M; see clause 4.9.1 + +Direction to be tested: OTA REFSENS *receiver target reference direction* (D.54). + +## 8.1.3.6.1.2.4.2 Procedure + +- 1) Place the IAB DU with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB DU with the test system. +- 3) Set the IAB DU in the declared direction to be tested. +- 4) Connect the IAB DU tester generating the wanted signal, multipath fading simulators and AWGN generators to a test antenna via a combining network in OTA test setup, as shown in annex E.3. Each of the demodulation branch signals should be transmitted on one polarization of the test antenna(s). + +- 5) The characteristics of the wanted signal shall be configured according to TS 38.211 [7], and according to additional test parameters listed in table 8.1.3.6.1.2.4.2-1. + +**Table 8.1.3.6.1.2.4.2-1: Test Parameters for multi-slot PUCCH format 1** + +| Parameter | Test | +|---------------------------------------------------------|----------------------------------------| +| Number of information bits | 2 | +| Number of PRBs | 1 | +| Number of symbols | 14 | +| First PRB prior to frequency hopping | 0 | +| Intra-slot frequency hopping | disabled | +| Inter-slot frequency hopping | enabled | +| First PRB after frequency hopping | The largest PRB index - (nrofPRBs - 1) | +| Group and sequence hopping | neither | +| Hopping ID | 0 | +| Initial cyclic shift | 0 | +| First symbol | 0 | +| Index of orthogonal cover code ( timeDomainOCC ) | 0 | +| Number of slots for PUCCH repetition | 2 | +| Cyclic prefix | normal | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex J. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the IAB DU receiver is as specified in clause 8.1.3.6.1.2.5.1 for *IAB type 1-O*, and that the SNR at the IAB DU 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 in table 8.1.3.6.1.2.4.2-2. + +**Table 8.1.3.6.1.2.4.2-2: AWGN power level at the BS input** + +| IAB type | Subcarrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------|--------------------------|-------------------------|------------------------------------------------------| +| IAB type 1-O | 15 kHz | 10 | $-80.3 - \Delta_{\text{OTAREFSENS}}$ dBm / 9.36 MHz | +| | | 20 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 19.08 MHz | +| | 30 kHz | 10 | $-80.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64 MHz | +| | | 20 | $-77.4 - \Delta_{\text{OTAREFSENS}}$ dBm / 18.36 MHz | +| | | 40 | $-74.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16 MHz | +| | | 100 | $-70.1 - \Delta_{\text{OTAREFSENS}}$ dBm / 98.28 MHz | + +NOTE: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. + +- 8) The tester sends a test pattern with the pattern outlined in figure 8.1.3.6.1.2.4.2-1. The following statistics are kept: the number of ACKs detected in the idle periods and the number of missed ACKs. + +![Figure 8.1.3.6.1.2.4.2-1: Test signal pattern for PUCCH format 1 demodulation tests. The diagram shows a sequence of three rectangular boxes, each containing the text 'ACK', representing detected acknowledgments. To the right of the third box is an ellipsis (three dots), indicating a continuation of the pattern.](04da196e79f7ac195f928904a244f0f9_img.jpg) + +Figure 8.1.3.6.1.2.4.2-1: Test signal pattern for PUCCH format 1 demodulation tests. The diagram shows a sequence of three rectangular boxes, each containing the text 'ACK', representing detected acknowledgments. To the right of the third box is an ellipsis (three dots), indicating a continuation of the pattern. + +**Figure 8.1.3.6.1.2.4.2-1: Test signal pattern for PUCCH format 1 demodulation tests** + +#### 8.1.3.6.1.2.5 Test Requirement + +##### 8.1.3.6.1.2.5.1 Test requirement for *IAB type 1-O* + +The fraction of falsely detected ACK bits shall be less than 1% and the fraction of correctly detected ACK bits shall be larger than 99% for the SNR listed in table 8.1.3.6.1.2.5.1-1. + +**Table 8.1.3.6.1.2.5.1-1: Required SNR for multi-slot PUCCH format 1 with 30 kHz SCS** + +| Number of TX antennas | Number of RX antennas | Propagation conditions and correlation matrix (Annex G) | Channel bandwidth (MHz) / SNR (dB) | +|-----------------------|-----------------------|---------------------------------------------------------|------------------------------------| +| | | | 40 MHz | +| 1 | 2 | TDLC-300-100 Low | -7.0 | + +## 8.1.4 Performance requirements for PRACH + +### 8.1.4.1 PRACH false alarm probability and missed detection + +#### 8.1.4.1.1 Definition and applicability + +The performance requirement of PRACH for preamble detection is determined by the two parameters: total probability of false detection of the preamble (Pfa) and the probability of detection of preamble (Pd). The performance is measured by the required SNR at probability of detection, Pd of 99%. Pfa shall be 0.1% or less. + +Pfa is defined as a conditional total probability of erroneous detection of the preamble (i.e. erroneous detection from any detector) when input is only noise. + +Pd is defined as conditional probability of detection of the preamble when the signal is present. The erroneous detection consists of several error cases – detecting only different preamble(s) than the one that was sent, not detecting any preamble at all, or detecting the correct preamble but with the out-of-bounds timing estimation value. For AWGN, TDLC300-100 and TDLA30-300, a timing estimation error occurs if the estimation error of the timing of the strongest path is larger than the time error tolerance values given in table 8.1.4.1.1-1. + +**Table 8.1.4.1.1-1: Time error tolerance for AWGN, TDLC300-100 and TDLA30-300** + +| PRACH preamble | PRACH SCS (kHz) | Time error tolerance | | | +|------------------------|-----------------|----------------------|-------------|------------| +| | | AWGN | TDLC300-100 | TDLA30-300 | +| 0 | 1.25 | 1.04 us | 2.55 us | N/A | +| A1, A2, A3, B4, C0, C2 | 15 | 0.52 us | 2.03 us | N/A | +| | 30 | 0.26 us | 1.77 us | N/A | +| | 60 (FR2) | 0.13 us | N/A | 0.28 us | +| | 120 | 0.07 us | N/A | 0.22 us | + +The test preambles for normal mode are listed in table A.2.5-1 and A.2.5-2. + +Which specific test(s) are applicable to BS is based on the test applicability rules defined in clause 8.1.1.3.4. + +#### 8.1.4.1.2 Minimum requirement + +For IAB type 1-O, the minimum requirement is in TS 38.174 [2] clause 11.1.4.1.1 and 11.1.4.1.2. + +For IAB type 2-O, the minimum requirement is in TS 38.174 [2] clause 11.1.4.2.1 and 11.1.4.2.2. + +#### 8.1.4.1.3 Test purpose + +The test shall verify the receiver's ability to detect PRACH preamble under static conditions and multipath fading propagation conditions for a given SNR. + +#### 8.1.4.1.4 Method of test + +##### 8.1.4.1.4.1 Initial conditions + +Test environment: Normal, see clause B.2. + +RF channels to be tested: for single carrier: M; see clause 4.9.1. + +Direction to be tested: OTA REFSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +#### 8.1.4.1.4.2 Procedure + +- 1) Place the IAB DU with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB DU with the test system. +- 3) Set the IAB DU in the declared direction to be tested. +- 4) Connect the IAB DU tester generating the wanted signal, multipath fading simulators and AWGN generators to a test antenna via a combining network in OTA test setup, as shown in annex E.3. Each of the demodulation branch signals should be transmitted on one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to the corresponding UL reference measurement channel defined in annex A and the test parameter *msg1-FrequencyStart* is set to 0. +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex J. +- 7) Adjust the AWGN generator, according to the SCS and channel bandwidth. The power level for the transmission may be set such that the AWGN level at the RIB is equal to the AWGN level in table 8.1.4.1.4.2-1. + +**Table 8.1.4.1.4.2-1: AWGN power level at the BS input** + +| IAB type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|---------------------|---------------------------|-------------------------|---------------------------------------------------------------------------------------------------------| +| IAB type 1-O | 15 | 10 | $-80.3 - \Delta_{\text{OTAREFSENS}}$ dBm / 9.36MHz | +| | | 20 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 19.08MHz | +| | 30 | 10 | $-80.6 - \Delta_{\text{OTAREFSENS}}$ dBm / 8.64MHz | +| | | 20 | $-77.4 - \Delta_{\text{OTAREFSENS}}$ dBm / 18.36MHz | +| | | 40 | $-74.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16MHz | +| | | 100 | $-70.1 - \Delta_{\text{OTAREFSENS}}$ dBm / 98.28MHz | +| IAB type 2-O | 60 | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15 \text{ dBm} / 47.52 \text{ MHz}$ | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18 \text{ dBm} / 95.04 \text{ MHz}$ | +| | 120 | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15 \text{ dBm} / 46.08 \text{ MHz}$ | +| | | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18 \text{ dBm} / 95.04 \text{ MHz}$ | +| | | 200 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 21 \text{ dBm} / 190.08 \text{ MHz}$ | + +NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. +NOTE 2: $\Delta_{\text{FR2\_REFSENS}} = -3 \text{ dB}$ as described in clause 7.1, since the OTA REFSENS receiver target reference direction (as declared in D.54 in table 4.6-1) is used for testing. +NOTE 3: $\text{EIS}_{\text{REFSENS\_50M}}$ as declared in D.28 in table 4.6-1. + +- 8) Adjust the frequency offset of the test signal according to table 8.1.4.1.5.1-1 or 8.1.4.1.5.1-2 or 8.1.4.1.5.1-3 or 8.1.4.1.6.1-1 or 8.1.4.1.6.1-2 or 8.1.4.1.6.1-3 or 8.1.4.1.6.1-4 or 8.1.4.1.5.2-1 or 8.1.4.1.5.2-2. +- 9) Adjust the equipment so that the SNR specified in table 8.1.4.1.5.1-1 or 8.1.4.1.5.1-2 or 8.1.4.1.5.1-3 or 8.1.4.1.6.1-1 or 8.1.4.1.6.1-2 or 8.1.4.1.6.1-3 or 8.1.4.1.6.1-4 or 8.1.4.1.5.2-1 or 8.1.4.1.5.2-2 is achieved at the BS input during the PRACH preambles. +- 10) The test signal generator sends a preamble and the receiver tries to detect the preamble. This pattern is repeated as illustrated in figure 8.1.4.1.4.2-1. The preambles are sent with certain timing offsets as described below. The following statistics are kept: the number of preambles detected in the idle period and the number of missed preambles. + +![Diagram showing two 'Preamble' boxes with an ellipsis between them, representing a PRACH preamble test pattern.](b6f6f51bf96aef85ffe1dcd9d57f398b_img.jpg) + +Diagram showing two 'Preamble' boxes with an ellipsis between them, representing a PRACH preamble test pattern. + +**Figure 8.1.4.1.4.2-1: PRACH preamble test pattern** + +The timing offset base value for PRACH preamble format 0 is set to 50% of Ncs. This offset is increased within the loop, by adding in each step a value of 0.1us, until the end of the tested range, which is 0.9us. Then the loop is being reset and the timing offset is set again to 50% of Ncs. The timing offset scheme for PRACH preamble format 0 is presented in Figure 8.1.4.1.4.2-2. + +![Timing diagram for PRACH preamble format 0 showing a sequence of pulses with timing offsets indicated by arrows and a feedback loop.](f39d3a124ba232478c81cfc995e1acdf_img.jpg) + +Timing diagram for PRACH preamble format 0 showing a sequence of pulses with timing offsets indicated by arrows and a feedback loop. + +**Figure 8.1.4.1.4.2-2: Timing offset scheme for PRACH preamble format 0** + +The timing offset base value for PRACH preamble format A1, A2, A3, B4, C0 and C2 is set to 0. This offset is increased within the loop, by adding in each step a value of 0.1us, until the end of the tested range, which is 0.8us. Then the loop is being reset and the timing offset is set again to 0. The timing offset scheme for PRACH preamble format A1, A2, A3, B4, C0 and C2 is presented in Figure 8.1.4.1.4.2-3. + +![Timing diagram for PRACH preamble formats A1, A2, A3, B4, C0 and C2 showing a sequence of pulses with timing offsets indicated by arrows and a feedback loop.](55ae388f215d5291df7c3ca240351d14_img.jpg) + +Timing diagram for PRACH preamble formats A1, A2, A3, B4, C0 and C2 showing a sequence of pulses with timing offsets indicated by arrows and a feedback loop. + +**Figure 8.1.4.1.4.2-3: Timing offset scheme for PRACH preamble format A1, A2, A3, B4, C0 and C2** + +**8.1.4.1.5 Test requirement for Normal Mode** + +**8.1.4.1.5.1 Test requirement for IAB type 1-O** + +Pfa shall not exceed 0.1%. Pd shall not be below 99% for the SNRs in tables 8.1.4.1.5.1-1 to 8.1.4.1.5.1-3. + +**Table 8.1.4.1.5.1-1: PRACH missed detection test requirements for Normal Mode, 1.25 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Frequency offset | SNR (dB) | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|----------------| +| | | | | Burst format 0 | +| 1 | 2 | AWGN | 0 | -14.2 | +| | | TDLC300-100 Low | 400 Hz | -6.0 | + +**Table 8.1.4.1.5.1-2: PRACH missed detection test requirements for Normal Mode, 15 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Frequency offset | SNR (dB) | | | | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | | | | Burst format A1 | Burst format A2 | Burst format A3 | Burst format B4 | Burst format C0 | Burst format C2 | +| 1 | 2 | AWGN | 0 | -9.0 | -12.3 | -13.9 | -16.5 | -6.0 | -12.2 | +| | | TDLC300-100 Low | 400 Hz | -1.5 | -4.2 | -6.0 | -8.2 | 1.4 | -4.3 | + +**Table 8.1.4.1.5.1-3: PRACH missed detection test requirements for Normal Mode, 30 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Frequency offset | SNR (dB) | | | | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | | | | Burst format A1 | Burst format A2 | Burst format A3 | Burst format B4 | Burst format C0 | Burst format C2 | +| 1 | 2 | AWGN | 0 | -8.8 | -11.7 | -13.5 | -16.2 | -5.8 | -11.6 | +| | | TDLC300-100 Low | 400 Hz | -2.2 | -5.1 | -6.8 | -9.3 | 0.7 | -5.0 | + +#### 8.1.4.1.5.2 Test requirement for IAB type 2-O + +Pfa shall not exceed 0.1%. Pd shall not be below 99% for the SNRs in tables 8.1.4.1.5.2-1 to 8.1.4.1.5.2-2. + +**Table 8.1.4.1.5.2-1: PRACH missed detection test requirements for Normal Mode, 60 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Frequency offset | SNR (dB) | | | | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | | | | Burst format A1 | Burst format A2 | Burst format A3 | Burst format B4 | Burst format C0 | Burst format C2 | +| 1 | 2 | AWGN | 0 | -8.6 | -11.6 | -13.2 | -15.5 | -5.7 | -11.5 | +| | | TDLA30-300 Low | 4000 Hz | -1.0 | -3.2 | -4.2 | -6.3 | 1.7 | -3.3 | + +**Table 8.1.4.1.5.2-2: PRACH missed detection test requirements for Normal Mode, 120 kHz SCS** + +| Number of TX antennas | Number of demodulation branches | Propagation conditions and correlation matrix (annex J) | Frequency offset | SNR (dB) | | | | | | +|-----------------------|---------------------------------|---------------------------------------------------------|------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | | | | Burst format A1 | Burst format A2 | Burst format A3 | Burst format B4 | Burst format C0 | Burst format C2 | +| 1 | 2 | AWGN | 0 | -8.4 | -11.2 | -13.0 | -15.5 | -5.5 | -11.1 | +| | | TDLA30-300 Low | 4000 Hz | -1.1 | -3.8 | -5.2 | -6.9 | 1.8 | -3.6 | + +## 8.2 IAB-MT performance requirements + +### 8.2.1 General + +#### 8.2.1.1 Scope and definitions + +Radiated performance requirements specify the ability of the *IAB-MT type 1-O* and *IAB-MT type 2-O* to correctly demodulate signals in various conditions and configurations. Radiated performance requirements are specified at the RIB. + +Radiated performance requirements for the IAB-MT are specified for the fixed reference channels defined in annex A and the propagation conditions in annex J. The requirements only apply to those FRCs that are supported by the IAB-MT. + +The radiated performance requirements for *IAB-MT type 1-O* and for *IAB-MT type 2-O* are limited to two OTA *demodulations branches* as described in clause 8.1.1.2. Conformance requirements can only be tested for 1 or 2 *demodulation branches* depending on the number of polarizations supported by the IAB-MT, with the required SNR applied separately per polarization. + +NOTE: IAB-MT 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 the slot on a single *TAB connector* (for *IAB-MT type 1-H*). + +N is the noise energy in a bandwidth corresponding to the transmission bandwidth over the duration of a slot on a single *TAB connector* (for *IAB-MT type 1-H*). + +## 8.2.2 Demodulation performance requirements + +### 8.2.2.1 General + +#### 8.2.2.1.1 Applicability rule for IAB-MT + +##### 8.2.2.1.1.1 General + +Unless otherwise stated, for an IAB-MT declared to support more than 2 demodulation branches (for *IAB-MT type 1-O* and *IAB-MT type 2-O*), the performance requirement tests for 2 demodulation branches shall apply, and the mapping between connectors and demodulation branches is up to IAB-MT implementation. + +The tests requiring more than [20] dB SNR level are set to N/A in the test requirements. + +##### 8.2.2.1.1.2 Applicability of requirements for different subcarrier spacings + +Unless otherwise stated, the tests shall apply only for each subcarrier spacing declared to be supported (see D.7 in table 4.6-1). + +##### 8.2.2.1.1.3 Applicability of requirements for TDD with different UL-DL patterns + +Unless otherwise stated, for each subcarrier spacing declared to be supported, if IAB-MT supports multiple TDD UL-DL patterns, only one of the supported TDD UL-DL patterns shall be used for all tests. + +##### 8.2.2.1.1.4 Applicability of requirements for IAB-MT features + +Unless otherwise stated, for *IAB type 1-O*, the PDSCH 256QAM tests (Test 1-1 of Clause 8.2.2.2.5.1) shall apply only for the 256QAM for PDSCH for FR1 declared to be supported (see D.200 in table 4.6-1, *pdsch-256QAM-FR1*). + +Unless otherwise stated, for both *IAB type 1-O* and *IAB type 2-O*, the PDSCH tests shall apply only in case the PDSCH MIMO rank in the test case does not exceed the maximum number of PDSCH MIMO layers declared to be supported (see D.202 in table 4.6-1, *maxNumberMIMO-LayersPDSCH*). + +Unless otherwise stated, for *IAB type 2-O*, the PDSCH tests shall apply only for the PT-RS option declared to be supported (see D.203 in table 4.6-1, *onePortsPTRS* (MSB)). + +Note: Applicability information may be obtained based on vendor declaration (Section 4.6) or alternatively from reading capability signaling. + +## 8.2.2.2 Performance requirements for PDSCH + +### 8.2.2.2.1 Definition and applicability + +The performance requirement of PDSCH is determined by a minimum required throughput for a given SNR. The required throughput is expressed as a fraction of maximum throughput for the FRCs listed in annex A. The performance requirements assume HARQ re-transmissions. + +Which specific test(s) are applicable to IAB-MT is based on the test applicability rules defined in clause 8.2.2.1.1. + +### 8.2.2.2.2 Minimum requirements + +For *IAB type 1-O*, the minimum requirement is in TS 38.174 [2], clause 11.2.2.1.1. + +For *IAB type 2-O*, the minimum requirement is in TS 38.174 [2], clause 11.2.2.2.1. + +### 8.2.2.2.3 Test purpose + +The test shall verify the receiver's ability to achieve throughput under multipath fading propagation conditions for a given SNR. + +### 8.2.2.2.4 Method of test + +#### 8.2.2.2.4.1 Initial conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: M, see clause 4.9.1. + +RF channels to be tested for carrier aggregation: $M_{\text{BW Channel CA}}$ ; see clause 4.9.1. + +Direction to be tested: OTA REFSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +#### 8.2.2.2.4.2 Test procedure + +- 1) Place the IAB-MT with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB-MT with the test system. +- 3) Set the IAB-MT in the declared direction to be tested. +- 4) Connect the IAB-MT tester generating the wanted signal, multipath fading simulators and AWGN generators to a test antenna via a combining network in OTA test setup, as shown in annex E.3. Each of the demodulation branch signals should be transmitted on one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to the corresponding DL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.2.2.2.4.2-1. + +**Table: 8.2.2.2.4.2-1 Test parameters for testing PDSCH** + +| Parameter | | IAB type 1-O | IAB type 2-O | +|----------------------------------------------------------------------------------|-------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cyclic prefix | | Normal | Normal | +| Default TDD UL-DL pattern (Note) | | 7D1S2U, S=6D:4G:4U | 3D1S1U, S=10D:2G:2U | +| HARQ | Maximum number of HARQ transmissions | 4 | 4 | +| | RV sequence | 0, 2, 3, 1 | 0, 2, 3, 1 | +| DM-RS | DM-RS configuration type | 1 | 1 | +| | DM-RS duration | single-symbol DM-RS | single-symbol DM-RS | +| | DM-RS position ( $l_0$ ) | 2 | 2 | +| | Additional DM-RS position | pos1 | pos1 | +| | Number of DM-RS CDM group(s) without data | 1 for Rank 1 and Rank 2 tests
2 for Rank 3 and Rank 4 tests | 1 | +| | DM-RS port(s) | {1000} for Rank 1 tests
{1000-1001} for Rank 2 tests
{1000-1002} for Rank 3 tests
{1000-1003} for Rank 4 tests | {1000} for Rank 1 tests
{1000-1001} for Rank 2 tests | +| | DM-RS sequence generation | NID0=0 | NID0=0 | +| | PDSCH mapping type | A | A | +| Time domain resource assignment | Start symbol | 2 | 1 | +| | Allocation length | 12 | 13 | +| Frequency domain resource assignment | RB assignment | Full applicable test bandwidth | Full applicable test bandwidth | +| PT-RS configuration | Frequency density ( $K_{PT-RS}$ ) | Not configured | 2 | +| | Time density ( $L_{PT-RS}$ ) | | 1 | +| PRB bundling size | | 2 | 2 | +| VRB-to-PRB mapping type | | Not interleaved | Not interleaved | +| PDSCH & PDSCH DMRS Precoding configuration | | Single Panel Type I, Random precoder selection updated per slot, with equal probability of each applicable i1, i2 combination, and with PRB bundling granularity | Single Panel Type I, Random precoder selection updated per slot, with equal probability of each applicable i1, i2 combination, and with PRB bundling granularity | +| NOTE: The same requirements are applicable to TDD with different UL-DL patterns. | | | | + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex J. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the IAB-MT receiver is as specified in clause 8.2.2.2.5.1 and 8.2.2.2.5.2 for *IAB type 1-O* and *IAB type 2-O* respectively, and that the SNR at the IAB 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 in table 8.2.2.2.4.2-2. + +**Table 8.2.2.2.4.2-2: AWGN power level at the IAB-MT input** + +| IAB type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------|---------------------------|-------------------------|----------------------------------------------------------------------------------------| +| IAB type 1-O | 30 | 40 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16 MHz | +| IAB type 2-O | 60 | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15$ dBm / 47.52 MHz | +| | 120 | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18$ dBm / 95.04 MHz | + +NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. +NOTE 2: $\Delta_{\text{FR2\_REFSENS}} = -3$ dB as described in clause 7.1, since the OTA REFSENS reference direction (as declared in D.54 in table 4.6-1) is used for testing. +NOTE 3: $\text{EIS}_{\text{REFSENS\_50M}}$ as declared in D.28 in table 4.6-1. + +8) For reference channels applicable to the IAB, measure the throughput. + +## 8.2.2.2.5 Test requirements + +### 8.2.2.2.5.1 Test requirement for IAB type 1-O + +The throughput shall be equal to or larger than the fraction of maximum throughput for the FRCs stated in Tables 8.2.2.2.5.1-1 and 8.2.2.2.5.1-2 at the given SNR with the test parameters stated in Table 8.2.2.2.4.2-1. + +**Table 8.2.2.2.5.1-1: Minimum requirements for PDSCH Type A with Rank 1** + +| Test number | FRC (Annex A) | Bandwidth (MHz) / Subcarrier spacing (kHz) | Propagation conditions (Annex J) | Antenna configuration | Fraction of maximum throughput (%) | SNR (dB) | +|-------------|---------------|--------------------------------------------|----------------------------------|-----------------------|------------------------------------|----------| +| 1-1 | M-FR1-A.3.3-1 | 40/30 | TDLA30-10 | 2x2, ULA Low | 70 | 26.3 | +| 1-2 | M-FR1-A.3.1-1 | 40/30 | TDLA30-10 | 2x2, ULA Low | 30 | 3.2 | + +**Table 8.2.2.2.5.1-2: Minimum requirements for PDSCH Type A with Rank 2** + +| Test number | FRC (Annex A) | Bandwidth (MHz) / Subcarrier spacing (kHz) | Propagation conditions (Annex J) | Antenna configuration | Fraction of maximum throughput (%) | SNR (dB) | +|-------------|---------------|--------------------------------------------|----------------------------------|-----------------------|------------------------------------|----------| +| 2-1 | M-FR1-A.3.2-1 | 40/30 | TDLA30-10 | 2x2, ULA Low | 70 | 20.8 | + +### 8.2.2.2.5.2 Test requirement for IAB type 2-O + +The throughput shall be equal to or larger than the fraction of maximum throughput for the FRCs stated in Tables 8.2.2.2.5.2-1 and 8.2.2.2.5.2-2 at the given SNR with the test parameters stated in Table 8.2.2.2.4.2-1. + +**Table 8.2.2.2.5.2-1: Minimum requirements for PDSCH Type A with Rank 1** + +| Test number | FRC (Annex A) | Bandwidth (MHz) / Subcarrier spacing (kHz) | Propagation conditions (Annex J) | Antenna configuration | Fraction of maximum throughput (%) | SNR (dB) | +|-------------|---------------|--------------------------------------------|----------------------------------|-----------------------|------------------------------------|----------| +| 1-1 | M-FR2-A.3.1-1 | 100/120 | TDLA30-75 | 2x2, ULA Low | 30 | 4.1 | +| 1-2 | M-FR2-A.3.2-1 | 100/120 | TDLA30-75 | 2x2, ULA Low | 70 | 13.5 | + +**Table 8.2.2.2.5.2-2: Minimum requirements for PDSCH Type A with Rank 2** + +| Test number | FRC (Annex A) | Bandwidth (MHz) / Subcarrier spacing (kHz) | Propagation conditions (Annex J) | Antenna configuration | Fraction of maximum throughput (%) | SNR (dB) | +|-------------|---------------|--------------------------------------------|----------------------------------|-----------------------|------------------------------------|----------| +| 2-1 | M-FR2-A.3.1-2 | 100/120 | TDLA30-75 | 2x2, ULA Low | 70 | 15.9 | +| 2-2 | M-FR2-A.3.1-3 | 50/60 | TDLA30-75 | 2x2, ULA Low | 70 | 16.0 | +| 2-3 | M-FR2-A.3.2-2 | 100/120 | TDLA30-75 | 2x2, ULA Low | 70 | 20.3 | + +## 8.2.2.3 Demodulation performance requirements for PDCCH + +### 8.2.2.3.1 Definition and applicability + +The receiver characteristics of the PDCCH are determined by the probability of miss-detection of the Downlink Scheduling Grant (Pm-dsg). + +Which specific test(s) are applicable to IAB-MT is based on the test applicability rules defined in clause 8.2.2.1.1. + +### 8.2.2.3.2 Minimum requirement + +For *IAB type 1-O*, the minimum requirement is in TS 38.174 [2], clause 11.2.2.1.2. + +For *IAB type 2-O*, the minimum requirement is in TS 38.174 [2], clause 11.2.2.2.2. + +### 8.2.2.3.3 Test purpose + +The test shall verify the receiver's ability to detect the Downlink Scheduling Grant (Pm-dsg) under multipath fading propagation conditions for a given SNR. + +### 8.2.2.3.4 Method of test + +#### 8.2.2.3.4.1 Initial conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: M, see clause 4.9.1. + +RF channels to be tested for carrier aggregation: $M_{BW\ Channel\ CA}$ ; see clause 4.9.1. + +Direction to be tested: OTA REFSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +#### 8.2.2.3.4.2 Test procedure + +- 1) Place the IAB-MT with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB-MT with the test system. +- 3) Set the IAB-MT in the declared direction to be tested. +- 4) Connect the IAB-MT tester generating the wanted signal, multipath fading simulators and AWGN generators to a test antenna via a combining network in OTA test setup, as shown in annex E.3. Each of the demodulation branch signals should be transmitted on one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to the corresponding DL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.2.2.3.4.2-1. + +**Table: 8.2.2.3.4.2-1 Test parameters for testing PDSCH** + +| Parameter | IAB type 1-O | IAB-type 2-O | +|-------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cyclic prefix | Normal | Normal | +| Default TDD UL-DL pattern (Note) | 7D1S2U, S=6D:4G:4U | 3D1S1U, S=10D:2G:2U | +| DM-RS sequence generation | NID=0 | NID=0 | +| Frequency domain resource allocation for CORESET | Start from RB = 0 with contiguous RB allocation | Start from RB = 0 with contiguous RB allocation | +| CCE to REG mapping type | Interleaved | Interleaved | +| Interleaver size | 3 | 3 for test with aggregation level 2, 8
2 for test with aggregation level 4 | +| REG bundle size | 2 for test with aggregation level 2, 4
6 for test with aggregation level 8 | 2 for test with aggregation level 2, 8
6 for test with aggregation level 4 | +| Shift Index | 0 | 0 | +| Slots for PDCCH monitoring | Each slot | Each slot | +| Number of PDCCH candidates for the tested aggregation level | 1 | 1 | +| PDCCH Precoding configuration | Single Panel Type I, Random precoder selection updated per slot, with equal probability of each applicable $i_1, i_2$ combination with REG bundling granularity for number of Tx larger than 1 | Single Panel Type I, Random precoder selection updated per slot, with equal probability of each applicable $i_1, i_2$ combination with REG bundling granularity for number of Tx larger than 1 | + +NOTE: The same requirements are applicable to TDD with different UL-DL patterns. + +- 6) The multipath fading emulators shall be configured according to the corresponding channel model defined in annex J. +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the IAB-MT receiver is as specified in clause 8.2.2.3.5.1 and 8.2.2.3.5.2 for *IAB type 1-O* and *IAB type 2-O* respectively, and that the SNR at the IAB 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 in table 8.2.2.3.4.2-2. + +**Table 8.2.2.3.4.2-2: AWGN power level at the IAB-MT input** + +| IAB type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------|---------------------------|-------------------------|----------------------------------------------------------------------------------------| +| IAB type 1-O | 30 | 40 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16 MHz | +| IAB type 2-O | 60 | 50 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 15$ dBm / 47.52 MHz | +| | 120 | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18$ dBm / 95.04 MHz | + +NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. + +NOTE 2: $\Delta_{\text{FR2\_REFSENS}} = -3$ dB as described in clause 7.1, since the OTA REFSENS reference direction (as declared in D.54 in table 4.6-1) is used for testing. + +NOTE 3: $\text{EIS}_{\text{REFSENS\_50M}}$ as declared in D.28 in table 4.6-1. + +- 8) For reference channels applicable to the IAB, measure the miss-detection of the Downlink Scheduling Grant (Pm-dsg). + +## 8.2.2.3.5 Test requirements + +### 8.2.2.3.5.1 Test requirement for *IAB type 1-O* + +The Pm-dsg shall be equal to or smaller than 1%, for the cases stated in Table 8.2.2.3.5.1-1 at the given SNR with the test parameters stated in Table 8.2.2.3.4.2-1. + +**Table 8.2.2.3.5.1-1: Minimum requirements for PDCCH** + +| Test number | Bandwidth (MHz) / Subcarrier spacing (kHz) | CORESET RB | CORESET duration | Aggregation level | FRC (Annex A) | Propagation conditions (Annex J) | Antenna configuration | Pm-dsg (%) | SNR (dB) | +|-------------|--------------------------------------------|------------|------------------|-------------------|---------------|----------------------------------|-----------------------|------------|----------| +| 1 | 40/30 | 102 | 1 | 2 | M-FR1-A.3.4-1 | TDLA30-10 | 1x2, ULA Low | 1 | 7.9 | +| 2 | 40/30 | 102 | 1 | 4 | M-FR1-A.3.4-2 | TDLA30-10 | 1x2, ULA Low | 1 | 5.8 | +| 3 | 40/30 | 90 | 1 | 8 | M-FR1-A.3.4-3 | TDLA30-10 | 2x2, ULA Low | 1 | 0.3 | + +#### 8.2.2.3.5.2 Test requirement for IAB type 2-O + +The Pm-dsg shall be equal to or smaller than 1%, for the cases stated in Table 8.2.2.3.5.2-1 at the given SNR with the test parameters stated in Table 8.2.2.3.4.2-1. + +**Table 8.2.2.3.5.2-1: Minimum requirements for PDCCH** + +| Test number | Bandwidth (MHz) / Subcarrier spacing (kHz) | CORESET RB | CORESET duration | Aggregation level | FRC (Annex A) | Propagation conditions (Annex J) | Antenna configuration | Pm-dsg (%) | SNR (dB) | +|-------------|--------------------------------------------|------------|------------------|-------------------|---------------|----------------------------------|-----------------------|------------|----------| +| 1 | 100/120 | 60 | 1 | 2 | M-FR2-A.3.4-1 | TDLA30-75 | 1x2, ULA Low | 1 | 8.1 | +| 2 | 100/120 | 60 | 1 | 4 | M-FR2-A.3.4-2 | TDLA30-75 | 1x2, ULA Low | 1 | 4.6 | +| 3 | 100/120 | 60 | 1 | 8 | M-FR2-A.3.4-3 | TDLA30-75 | 2x2, ULA Low | 1 | 1.9 | + +### 8.2.3 CSI reporting requirements + +#### 8.2.3.1 General + +##### 8.2.3.1.1 Applicability of requirements + +###### 8.2.3.1.1.1 General + +Unless otherwise stated, for a IAB-MT declared to support more than 2 demodulation branches (for *IAB-MT type 1-O* and *IAB-MT type 2-O*), the performance requirement tests for 2 demodulation branches shall apply, and the mapping between connectors and demodulation branches is up to IAB-MT implementation. + +The tests requiring more than [20] dB SNR level are set to N/A in the test requirements. + +###### 8.2.3.1.1.2 Applicability of requirements for different subcarrier spacings + +Unless otherwise stated, the tests shall apply only for each subcarrier spacing declared to be supported (see D.7 in table 4.6-1). + +###### 8.2.3.1.1.3 Applicability of requirements for TDD with different UL-DL patterns + +Unless otherwise stated, for each subcarrier spacing declared to be supported, if IAB-MT supports multiple TDD UL-DL patterns, only one of the supported TDD UL-DL patterns shall be used for all tests. + +#### 8.2.3.1.1.4 Applicability of PMI/RI requirements + +Testing of performance requirements for RI and PMI reporting is optional. + +#### 8.2.3.1.1.5 Applicability of requirements for IAB-MT features + +Unless otherwise stated, for *IAB type 1-O*, the CSI reporting tests (clauses 8.2.3.3, 8.2.3.4) shall apply only in case the number of NZP-CSI-RS ports in the test case satisfies maximum number of ports across all configured NZP-CSI-RS resources per CC declared to be supported (see D.201 in table 4.6-1, *maxConfigNumberPortsAcrossNZP-CSI-RS-PerCC*). + +Unless otherwise stated, for *IAB type 1-O*, the CSI reporting tests (clauses 8.2.3.2, 8.2.3.3, 8.2.3.4) shall apply only in case the PDSCH MIMO rank in the test case does not exceed the maximum number of PDSCH MIMO layers declared to be supported (see D.202 in table 4.6-1, *maxNumberMIMO-LayersPDSCH*). + +Unless otherwise stated, for *IAB type 2-O*, the CSI reporting tests (clauses 8.2.3.2, 8.2.3.3, 8.2.3.4) shall apply only for the PT-RS option declared to be supported (see D.203 in table 4.6-1, *onePortPTRS*). + +NOTE: Applicability information may be obtained based on vendor declaration (Section 4.6) or alternatively from reading capability signaling. + +#### 8.2.3.1.2 Common test parameters + +Parameters specified in Table 8.2.3.1.2-1 are applied for all test cases in this clause unless otherwise stated. + +**Table 8.2.3.1.2-1: Test parameters for CSI test cases** + +| Parameter | | Unit | Value FR1 | Value FR2 | +|------------------------------------|----------------------------------------------------------------------------------|------|------------------------------------------------------------------------------------------------------------|-------------------------------------------| +| PDSCH transmission scheme | | | Transmission scheme 1 | Transmission scheme 1 | +| Duplex mode | | | TDD | TDD | +| PTRS epre-Ratio | | | N/A | 0 | +| Actual carrier configuration | Offset between Point A and the lowest usable subcarrier on this carrier (Note 3) | RBs | 0 | 0 | +| | Subcarrier spacing | kHz | 30 | 120 | +| DL BWP configuration #1 | Cyclic prefix | | Normal | Normal | +| | RB offset | RBs | 0 | 0 | +| | Number of contiguous PRB | PRBs | 106 | 66 | +| Active DL BWP index | | | 1 | 1 | +| PDSCH configuration | Mapping type | | Type A | Type A | +| | k0 | | 0 | 0 | +| | Starting symbol (S) | | 2 | 2 | +| | Length (L) | | 12 | 12 | +| | PDSCH aggregation factor | | 1 | 1 | +| | PRB bundling type | | Static | Static | +| | PRB bundling size | | 2 | 2 | +| | Resource allocation type | | Type 0 | type 0 | +| | RBG size | | | Config 2 | +| | VRB-to-PRB mapping type | | Non-interleaved | Non-interleaved | +| | VRB-to-PRB mapping interleaver bundle size | | N/A | N/A | +| PDSCH DMRS configuration | DMRS Type | | Type 1 | Type 1 | +| | Number of additional DMRS | | 1 | 1 | +| | Maximum number of OFDM symbols for DL front loaded DMRS | | 1 | 1 | +| | DMRS ports indexes | | {1000} for Rank1
{1000,1001} for Rank2
{1000,1001,1002} for Rank3
{1000,1001,1002,1003} for Rank4 | {1000} for Rank1
{1000,1001} for Rank2 | +| | Number of PDSCH DMRS CDM group(s) without data | | 2 | 2 | +| PTRS configuration | Frequency density ( $K_{PT-RS}$ ) | | N/A | 2 | +| | Time density ( $L_{PT-RS}$ ) | | N/A | 1 | +| | Resource Element Offset | | N/A | 2 | +| NZP CSI-RS for CSI acquisition | Frequency Occupation | | Start PRB 0
Number of PRB = BWP size | Start PRB 0
Number of PRB = BWP size | +| Redundancy version coding sequence | | | {0,2,3,1} | {0,2,3,1} | + +NOTE 1: PDSCH is not scheduled on slots containing CSI-RS or slots which are not full DL. + +NOTE 2: Point A coincides with minimum guard band as specified in Table 5.3.3-1 from TS 38.101-1 [16] or 38.101-2 [17] for tested channel bandwidth and subcarrier spacing. + +## 8.2.3.2 Reporting of Channel Quality Indicator (CQI) + +### 8.2.3.2.1 Definition and applicability + +The performance requirement of CSI reporting is determined by the reporting variance and the BLER performance using the transport format indicated by the reported CQI. The purpose is to verify that the reported CQI values are in accordance with the CQI definition given in TS 38.214 [27]. To account for sensitivity of the input SNR the reporting definition is considered to be verified if the reporting accuracy is met for at least one of two SNR levels separated by an offset of 1 dB. + +### 8.2.3.2.2 Minimum requirement + +The minimum requirement for IAB-MT type I-O is in TS 38.174 [2] clause 11.2.3.1.1 + +The minimum requirement for *IAB-MT type 2-O* is in TS 38.174 [2] clause 11.2.3.2.2. + +#### 8.2.3.2.3 Test purpose + +The test shall verify the receiver's ability to report correct median CQI and expected BLER performance under AWGN conditions. + +#### 8.2.3.2.4 Method of test + +##### 8.2.3.2.4.1 Initial conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: $M$ ; see clause 4.9.1. + +RF channels to be tested for carrier aggregation: $M_{\text{BW Channel CA}}$ ; see clause 4.9.1. + +Direction to be tested: OTA REFSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +##### 8.2.3.2.4.2 Procedure + +- 1) Place the IAB-MT with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB-MT with the test system. +- 3) Set the IAB-MT in the declared direction to be tested. +- 4) Connect the IAB-MT tester generating the wanted signal and AWGN generators to a test antenna via a combining network in OTA test setup, as shown in annex E.3. Each of the demodulation branch signals should be transmitted on one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to the corresponding DL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.2.3.2.4.2-2 or 8.2.3.2.4.2-2. + +**Table 8.2.3.2.4.2-1: Test parameters for testing CQI reporting requirements for FR1** + +| Parameter | Unit | Test 1 | | Test 2 | | | | | | +|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|------|--------|----|--|--|--|--| +| Bandwidth | MHz | 40 | | | | | | | | +| Subcarrier spacing | kHz | 30 | | | | | | | | +| Duplex Mode | | TDD | | | | | | | | +| SNR | dB | 8 | 9 | 14 | 15 | | | | | +| Propagation channel | | AWGN | | | | | | | | +| Antenna configuration | | 2×2 with static channel specified in Annex J.1 | | | | | | | | +| Beamforming Model | | As specified in Annex J.3.1 | | | | | | | | +| NZP CSI-RS for CSI acquisition | CSI-RS resource Type | Periodic | | | | | | | | +| | Number of CSI-RS ports (X) | 2 | | | | | | | | +| | CDM Type | FD-CDM2 | | | | | | | | +| | Density (p) | 1 | | | | | | | | +| | First subcarrier index in the PRB used for CSI-RS ( $k_0, k_1$ ) | Row 3,(6,-) | | | | | | | | +| | First OFDM symbol in the PRB used for CSI-RS ( $l_0$ ) | 13 | | | | | | | | +| | NZP CSI-RS-timeConfig periodicity and offset | slot | 10/1 | | | | | | | +| ReportConfigType | | Periodic | | | | | | | | +| CQI-table | | Table 2 | | | | | | | | +| reportQuantity | | cri-RI-PMI-CQI | | | | | | | | +| cqi-FormatIndicator | | Wideband | | | | | | | | +| pmi-FormatIndicator | | Wideband | | | | | | | | +| Sub-band Size | RB | 16 | | | | | | | | +| Csi-ReportingBand | | 1111111 | | | | | | | | +| CSI-Report periodicity and offset | slot | 10/9 | | | | | | | | +| Codebook configuration | Codebook Type | typeI-SinglePanel | | | | | | | | +| | Codebook Mode | 1 | | | | | | | | +| | (CodebookConfig-N1, CodebookConfig-N2) | Not configured | | | | | | | | +| | CodebookSubsetRestriction | 010000 | | | | | | | | +| | RI Restriction | N/A | | | | | | | | +| CQI/RI/PMI delay | ms | 9.5 | | | | | | | | +| Maximum number of HARQ transmission | | 1 | | | | | | | | +| Measurement channel | | As specified in Table A.2.6-1, M-FR1-A.3.5-1 | | | | | | | | +| Note 1: | The same requirements are applicable for TDD with different UL-DL pattern. | | | | | | | | | +| Note 2: | SSB, TRS, CSI-RS and/or other unspecified test parameters with respect to TS 38.101-4 [18] are left up to test implementation, if transmitted or needed. | | | | | | | | | +| Note 3: | If the IAB-MT reports in an available uplink reporting instance at slot #n based on CQI estimation at a downlink slot not later than slot#(n-4), this reported CQI cannot be applied at the gNB downlink before slot#(n+4). | | | | | | | | | + +**Table 8.2.3.2.4.2-2: Test parameters for testing CQI reporting requirements for FR2** + +| Parameter | Unit | Test 1 | | Test 2 | | | | | | | | | +|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-----|--------|----|--|--|--|--|--|--|--| +| Bandwidth | MHz | 100 | | | | | | | | | | | +| Subcarrier spacing | kHz | 120 | | | | | | | | | | | +| Duplex Mode | | TDD | | | | | | | | | | | +| SNR BB | dB | 8 | 9 | 14 | 15 | | | | | | | | +| Propagation channel | | AWGN | | | | | | | | | | | +| Antenna configuration | | 2×2 with static channel specified in Annex J.1 | | | | | | | | | | | +| Beamforming Model | | As specified in Annex J.3.1 | | | | | | | | | | | +| NZP CSI-RS for CSI acquisition | CSI-RS resource Type | Periodic | | | | | | | | | | | +| | Number of CSI-RS ports (X) | 2 | | | | | | | | | | | +| | CDM Type | fd-CDM2 | | | | | | | | | | | +| | Density (p) | 1 | | | | | | | | | | | +| | First subcarrier index in the PRB used for CSI-RS (k 0 , k 1 ) | 6 | | | | | | | | | | | +| | First OFDM symbol in the PRB used for CSI-RS (l 0 , l 1 ) | 13 | | | | | | | | | | | +| | NZP CSI-RS-timeConfig periodicity and offset | slot | 5/1 | | | | | | | | | | +| ReportConfigType | | Periodic | | | | | | | | | | | +| CQI-table | | Table 1 | | | | | | | | | | | +| reportQuantity | | cri-RI-PMI-CQI | | | | | | | | | | | +| timeRestrictionForChannelMeasurements | | Not configured | | | | | | | | | | | +| timeRestrictionForInterferenceMeasurements | | Not configured | | | | | | | | | | | +| cqi-FormatIndicator | | Wideband | | | | | | | | | | | +| pmi-FormatIndicator | | Wideband | | | | | | | | | | | +| Sub-band Size | RB | 8 | | | | | | | | | | | +| csi-ReportingBand | | 1111111111 | | | | | | | | | | | +| CSI-Report periodicity and offset | slot | 5/4 | | | | | | | | | | | +| Codebook configuration | Codebook Type | type1-SinglePanel | | | | | | | | | | | +| | Codebook Mode | 1 | | | | | | | | | | | +| | (CodebookConfig-N1, CodebookConfig-N2) | Not configured | | | | | | | | | | | +| | CodebookSubsetRestriction | 010000 | | | | | | | | | | | +| | RI Restriction | N/A | | | | | | | | | | | +| CQI/RI/PMI delay | ms | 1.75 | | | | | | | | | | | +| Maximum number of HARQ transmission | | 1 | | | | | | | | | | | +| Measurement channel | | As specified in Table A.2.6-3, M-FR2-A.3.5-2 | | | | | | | | | | | +| Note 1: | The same requirements are applicable for TDD with different UL-DL pattern. | | | | | | | | | | | | +| Note 2: | SSB, TRS, CSI-RS and/or other unspecified test parameters with respect to TS 38.101-4 [18] are left up to test implementation, if transmitted or needed. | | | | | | | | | | | | +| Note 3: | If the IAB-MT reports in an available uplink reporting instance at slot #n based on PMI estimation at a downlink slot not later than slot#(n-4), this reported PMI cannot be applied at the gNB downlink before slot#(n+4). | | | | | | | | | | | | + +- Adjust the test signal mean power so the calibrated radiated SNR value at the IAB-MT receiver is as specified in clause 8.2.3.2.5.1 and 8.2.3.2.5.2 for *IAB type 1-O* and *IAB type 2-O* respectively, and that the SNR at the IAB-MT 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 in table 8.2.3.2.4.2-2. + +**Table 8.2.3.2.4.2-2: AWGN power level at the IAB-MT input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-------------------------|----------------------------------------------------------------------------------------| +| IAB-MT type 1-O | 30 | 40 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16 MHz | +| IAB-MT type 2-O | 120 | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18$ dBm / 95.04 MHz | +| NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. | | | | +| NOTE 2: $\Delta_{\text{FR2\_REFSENS}} = -3$ dB as described in clause 7.1, since the OTA REFSENS reference direction (as declared in D.54 in table 4.6-1) is used for testing. | | | | +| NOTE 3: $\text{EIS}_{\text{REFSENS\_50M}}$ as declared in D.28 in table 4.6-1. | | | | + +- 8) For reference channels applicable to the IAB-MT, measure the median CQI and the BLER at (median CQI +1) and (median CQI -1). + +### 8.2.3.2.5 Test requirement + +#### 8.2.3.2.5.1 Test requirement for IAB type 1-O + +For the parameters specified in Table 8.2.3.2.4.2-1, the minimum requirements are specified by the following: + +- The reported CQI value according to the reference channel shall be in the range of $\pm 1$ of the reported median more than 90% of the time. +- If the PDSCH BLER using the transport format indicated by median CQI is less than or equal to 0.1, then the BLER using the transport format indicated by the (median CQI+1) shall be greater than 0.1. If the PDSCH BLER using the transport format indicated by the median CQI is greater than 0.1, then the BLER using transport format indicated by (median CQI-1) shall be less than or equal to 0.1. + +#### 8.2.3.2.5.2 Test requirement for IAB type 2-O + +For the parameters specified in Table 8.2.3.2.4.2-2, the minimum requirements are specified by the following: + +- the reported CQI value shall be in the range of $\pm 1$ of the reported median more than 90% of the time; +- if the PDSCH BLER using the transport format indicated by median CQI is less than or equal to 0.1, the BLER using the transport format indicated by the (median CQI + 1) shall be greater than 0.1. If the PDSCH BLER using the transport format indicated by the median CQI is greater than 0.1, the BLER using transport format indicated by (median CQI – 1) shall be less than or equal to 0.1. + +### 8.2.3.3 Reporting of Precoding Matrix Information (PMI) + +#### 8.2.3.3.1 Definition and applicability + +The minimum performance requirements of PMI reporting are defined based on the precoding gain, expressed as the relative increase in throughput when the transmitter is configured according to the IAB-MT reported PMI compared to the case when the transmitter is using random precoding, respectively. When the transmitter uses random precoding, for each PDSCH allocation a precoder is randomly generated with equal probability of each applicable $i_1$ and $i_2$ combination and applied to the PDSCH. A fixed transport format (FRC) is configured for all requirements. + +The requirements for transmission mode 1 with higher layer parameter *codebookType* set to 'typeI-SinglePanel' are specified in terms of the ratio: + +In the definition of $\gamma$ , for 4TX, 8TX PMI requirements, $t_{\text{follow1, follow2}}$ is 90 % of the maximum throughput obtained at $\text{SNR}_{\text{follow1, follow2}}$ using the precoders configured according to the IAB-MT reports, and $t_{\text{rnd1, rnd2}}$ is the throughput measured at $\text{SNR}_{\text{follow1, follow2}}$ with random precoding. + +#### 8.2.3.3.2 Minimum requirement + +The minimum requirement for *IAB-MT type 1-O* is in TS 38.174 [2] clause 11.2.3.1.2. + +The minimum requirement for *IAB-MT type 2-O* is in TS 38.174 [2] clause 11.2.3.2.3. + +#### 8.2.3.3.3 Test purpose + +The test shall verify the receiver's ability to report correct PMI under the defined fading conditions. + +#### 8.2.3.3.4 Method of test + +##### 8.2.3.3.4.1 Initial conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: M; see clause 4.9.1. + +RF channels to be tested for carrier aggregation: $M_{\text{BW Channel CA}}$ ; see clause 4.9.1. + +Direction to be tested: OTA REFSSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +##### 8.2.3.3.4.2 Procedure + +- 1) Place the IAB-MT with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB-MT with the test system. +- 3) Set the IAB-MT in the declared direction to be tested. +- 4) Connect the IAB-MT tester generating the wanted signal and AWGN generators to a test antenna via a combining network in OTA test setup, as shown in annex E.3. Each of the demodulation branch signals should be transmitted on one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to the corresponding DL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.2.3.3.4.2-1. + +**Table 8.2.3.3.4.2-1: Test parameters for testing PMI reporting requirements** + +| Parameter | Unit | FR1 | FR2 | +|-------------------------------------|--------------------------------------------------------------------------------------|--------------------------------------------------------------------------|-----------------------------| +| Bandwidth | MHz | 40 | 100 | +| Subcarrier spacing | kHz | 30 | 120 | +| Duplex Mode | | TDD | TDD | +| TDD DL-UL configuration | | 7D1S2U, S=6D:4G:4U | 3D1S1U, S=10D:2G:2U | +| Propagation channel | | TDLA30-5 | TDLA30-35 | +| Antenna configuration | | High XP 4 x 2
(N1,N2) = (2,1)

High XP 8 x 2
(N1,N2) = (4,1) | 2 x 2 ULA Low | +| Beamforming Model | | As specified in Annex J.3.1 | As specified in Annex J.3.1 | +| NZP CSI-RS for CSI acquisition | CSI-RS resource Type | Periodic | | +| | Number of CSI-RS ports (X) | Test for 4 TX ports: 4
Test for 8 TX ports: 8 | 2 | +| | CDM Type | Test for 4 TX ports: FD-CDM2
Test for 8 TX ports: CDM4 (FD2, TD2) | FD-CDM2 | +| | Density (p) | 1 | 1 | +| | First subcarrier index in the PRB used for CSI-RS (k 0 , k 1 ) | Test for 4 TX ports: Row 4 (0,-)
Test for 8 TX ports: Row 8, (4,6) | Row 3, (6,-) | +| | First OFDM symbol in the PRB used for CSI-RS (l 0 , l 1 ) | Test for 4 TX ports, 2RX: (13,-)
Test for 8 TX ports: (5,-) | (13,-) | +| | NZP CSI-RS-timeConfig periodicity and offset | Slot 10/1 | 5/1 | +| ReportConfigType | | Periodic | Periodic | +| Sub-band Size | RB | 16 | 8 | +| csi-ReportingBand | | 11111111 | 1111111111 | +| CSI-Report periodicity and offset | slot | 10/9 | 5/4 | +| pmi-FormatIndicator | | Wideband | Wideband | +| Codebook configuration | Codebook Type | typeI-SinglePanel | typeI-SinglePanel | +| | Codebook Mode | 1 | 1 | +| | (CodebookConfig-N1,CodebookConfig-N2) | Test for 4 TX ports: (2,1)
Test for 8 TX ports: (4,1) | NA | +| | (CodebookConfig-O1,CodebookConfig-O2) | Test for 4 TX ports: (4,1)
Test for 8 TX ports: (4,1) | NA | +| | CodebookSubsetRestriction | Test for 4 TX ports: 11111111
Test for 8 TX ports: 0x FFFF | 001111 | +| | RI Restriction | Test for 4 TX ports: 00000001
Test for 8 TX ports: 00000010 | NA | +| Maximum number of HARQ transmission | | 4 | 4 | +| CQI/RI/PMI delay | ms | 5.5 | 1.75 | +| Measurement channel | | Test for 4 TX ports: M-FR1-A.3.5-1
Test for 8 TX ports: M-FR1-A.3.5-2 | M-FR2-A.3.5-3 | + +NOTE 1: The same requirements are applicable for TDD with different UL-DL pattern. +NOTE 2: When Throughput is measured using random precoder selection, the precoder shall be updated in each slot (0.5 ms FR1 / 0.125 ms FR2 granularity) with equal probability of each applicable i1, i2 combination. +NOTE 3: If the IAB-MT reports in an available uplink reporting instance at slot #n based on PMI estimation at a downlink slot not later than slot#(n-4), this reported PMI cannot be applied at the gNB downlink before + +| Parameter | Unit | FR1 | FR2 | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|-----| +| slot#(n+4). | | | | +| NOTE 4: Randomization of the principle beam direction shall be used as specified in Annex J.2.3.2.3. | | | | +| NOTE 5: SSB, TRS, CSI-RS and/or other unspecified test parameters with respect to TS 38.101-4 [18] are left up to test implementation, if transmitted or needed. | | | | + +- 7) Adjust the test signal mean power so the calibrated radiated SNR value at the IAB-MT receiver is as specified in clause 8.2.3.3.5.1 and 8.2.3.3.5.2 for *IAB type 1-O* and *IAB type 2-O* respectively, and that the SNR at the IAB-MT 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 in table 8.2.3.3.4.2-2. + +**Table 8.2.3.3.4.2-2: AWGN power level at the IAB-MT input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-------------------------|----------------------------------------------------------------------------------------| +| IAB-MT type 1-O | 30 | 40 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16 MHz | +| IAB-MT type 2-O | 120 | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18$ dBm / 95.04 MHz | +| NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. | | | | +| NOTE 2: $\Delta_{\text{FR2\_REFSENS}} = -3$ dB as described in clause 7.1, since the OTA REFSENS reference direction (as declared in D.54 in table 4.6-1) is used for testing. | | | | +| NOTE 3: $\text{EIS}_{\text{REFSENS\_50M}}$ as declared in D.28 in table 4.6-1. | | | | + +- 8) For reference channels applicable to the IAB-MT, measure the ratio of the throughput obtained when following the PMI feedback to the throughput obtained when applying random PMI as described in subclause 8.2.3.3.1. + +### 8.2.3.3.5 Test requirement + +#### 8.2.3.3.5.1 Test requirement for *IAB type 1-O* + +$\gamma$ as defined in subclause 8.2.3.3.1 shall be greater than the indicated requirement. + +**Table 8.2.3.3.5.1-1: PMI reporting requirements for FR1** + +| Parameter | Test | Requirement | +|-----------|----------|-------------| +| $\gamma$ | 4TX, 2RX | 1.3 | +| $\gamma$ | 8TX, 2RX | 1.5 | + +#### 8.2.3.3.5.2 Test requirement for *IAB type 2-O* + +$\gamma$ as defined in subclause 8.2.3.3.1 shall be greater than the indicated requirement. + +**Table 8.2.3.3.5.1-2: PMI reporting requirements for FR2** + +| Parameter | Requirement | +|-----------|-------------| +| $\gamma$ | 1.05 | + +### 8.2.3.4 Reporting of Rank Information (RI) + +#### 8.2.3.4.1 Definition and applicability + +The purpose of this test is to verify that the reported rank indicator accurately represents the channel rank. The accuracy of RI reporting is determined by the relative increase of the throughput obtained when transmitting based on the reported rank compared to the case for which a fixed rank is used for transmission. + +#### 8.2.3.4.2 Minimum requirement + +The minimum requirement for *IAB-MT type 1-O* is in TS 38.174 [2] clause 11.2.3.1.3. + +The minimum requirement for *IAB-MT type 2-O* is in TS 38.174 [2] clause 11.2.3.2.4. + +#### 8.2.3.4.3 Test purpose + +The test shall verify the receiver's ability to report correct RI under the defined fading conditions. + +#### 8.2.3.4.4 Method of test + +##### 8.2.3.4.4.1 Initial conditions + +Test environment: Normal, see annex B.2. + +RF channels to be tested for single carrier: $M_i$ ; see clause 4.9.1. + +RF channels to be tested for carrier aggregation: $M_{\text{BW Channel CA}}$ ; see clause 4.9.1. + +Direction to be tested: OTA REFSSENS *receiver target reference direction* (see D.54 in table 4.6-1). + +##### 8.2.3.4.4.2 Procedure + +- 1) Place the IAB-MT with its manufacturer declared coordinate system reference point in the same place as calibrated point in the test system, as shown in annex E.3. +- 2) Align the manufacturer declared coordinate system orientation of the IAB-MT with the test system. +- 3) Set the IAB-MT in the declared direction to be tested. +- 4) Connect the IAB-MT tester generating the wanted signal and AWGN generators to a test antenna via a combining network in OTA test setup, as shown in annex E.3. Each of the demodulation branch signals should be transmitted on one polarization of the test antenna(s). +- 5) The characteristics of the wanted signal shall be configured according to the corresponding DL reference measurement channel defined in annex A, and according to additional test parameters listed in table 8.2.3.4.4.2-1. + +**Table 8.2.3.4.4.2-1: Test parameters for testing RI reporting requirements** + +| Parameter | Unit | FR1 | FR2 | +|-------------------------------------|------------------------------------------------------------------|------------------------------------------------------------------------------|------------------------------------------------------------------------------| +| Bandwidth | MHz | 40 | 100 | +| Subcarrier spacing | kHz | 30 | 120 | +| Duplex Mode | | TDD | TDD | +| TDD Slot Configuration | | 7D1S2U, S=6D:4G:4U | 3D1S1U, S=10D:2G:2U | +| SNR | dB | Test 1: 0
Test 2: 20
Test 3: 20 | Test 1: 0
Test 2: 16
Test 3: 16 | +| Propagation channel | | TDLA30-5 | TDLA30-35 | +| Antenna configuration | | Test 1, 2: ULA Low 2x2
Test 3: ULA High 2x2 | Test 1, 2: ULA Low 2x2
Test 3: XP High 2x2 | +| Beamforming Model | | As defined in Annex J.3.1 | As defined in Annex J.3.1 | +| NZP CSI-RS for CSI acquisition | CSI-RS resource Type | Periodic | Periodic | +| | Number of CSI-RS ports (X) | 2 | 2 | +| | CDM Type | FD-CDM2 | FD-CDM2 | +| | Density (ρ) | 1 | 1 | +| | First subcarrier index in the PRB used for CSI-RS ( $k_0, k_1$ ) | Row 3 (6,-) | Row 3 (6,-) | +| | First OFDM symbol in the PRB used for CSI-RS ( $l_0, l_1$ ) | (13,-) | (13,-) | +| | NZP CSI-RS-timeConfig periodicity and offset | slot 10/1 | 5/1 | +| ReportConfigType | | Periodic | Periodic | +| CQI-table | | Table 2 | Table 1 | +| reportQuantity | | cri-RI-PMI-CQI | cri-RI-PMI-CQI | +| cqi-FormatIndicator | | Wideband | Wideband | +| pmi-FormatIndicator | | Wideband | Wideband | +| Sub-band Size | RB | 16 | 8 | +| csi-ReportingBand | | 1111111 | 1111111 | +| CSI-Report periodicity and offset | slot | 10/9 | 5/4 | +| Codebook configuration | Codebook Type | typeI-SinglePanel | typeI-SinglePanel | +| | Codebook Mode | 1 | 1 | +| | (CodebookConfig-N1, CodebookConfig-N2) | N/A | N/A | +| | CodebookSubsetRestriction | 000011 for fixed rank 1, 010000 for fixed rank 2, 010011 for following rank | 000011 for fixed rank 1, 010000 for fixed rank 2, 010011 for following rank | +| | RI Restriction | N/A | N/A | +| CQI/RI/PMI delay | ms | 9.5 | 1.75 | +| Maximum number of HARQ transmission | | 1 | 1 | +| RI Configuration | | Test 1: Fixed RI = 2 and follow RI
Tests 2, 3: Fixed RI = 1 and follow RI | Test 1: Fixed RI = 2 and follow RI
Tests 2, 3: Fixed RI = 1 and follow RI | + +NOTE 1: The same requirements are applicable to with different UL-DL patterns. + +NOTE 2: SSB, TRS, CSI-RS and/or other unspecified test parameters with respect to TS 38.101-4 [18] are left up to test implementation, if transmitted or needed. + +NOTE 3: If the IAB-MT reports in an available uplink reporting instance at slot #n based on RI estimation at a downlink slot not later than slot#(n-4), this reported RI cannot be applied at the gNB downlink before slot#(n+4). + +7) Adjust the test signal mean power so the calibrated radiated SNR value at the IAB-MT receiver is as specified in table 8.2.3.4.4.2-1 for *IAB type 1-O* and *IAB type 2-O* respectively, and that the SNR at the IAB-MT 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 in table 8.2.3.4.4.2-2. + +**Table 8.2.3.4.4.2-2: AWGN power level at the IAB-MT input** + +| BS type | Sub-carrier spacing (kHz) | Channel bandwidth (MHz) | AWGN power level | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-------------------------|----------------------------------------------------------------------------------------| +| IAB-MT type 1-O | 30 | 40 | $-77.2 - \Delta_{\text{OTAREFSENS}}$ dBm / 38.16 MHz | +| IAB-MT type 2-O | 120 | 100 | $\text{EIS}_{\text{REFSENS\_50M}} + \Delta_{\text{FR2\_REFSENS}} + 18$ dBm / 95.04 MHz | +| NOTE 1: $\Delta_{\text{OTAREFSENS}}$ as declared in D.53 in table 4.6-1 and clause 7.1. | | | | +| NOTE 2: $\Delta_{\text{FR2\_REFSENS}} = -3$ dB as described in clause 7.1, since the OTA REFSENS reference direction (as declared in D.54 in table 4.6-1) is used for testing. | | | | +| NOTE 3: $\text{EIS}_{\text{REFSENS\_50M}}$ as declared in D.28 in table 4.6-1. | | | | + +- 8) For reference channels applicable to the IAB-MT, measure the ratio of the throughput obtained when following the RI feedback to the throughput obtained when applying random RI as described in subclause 8.2.3.4.5. + +#### 8.2.3.4.5 Test requirement + +##### 8.2.3.4.5.1 Test requirement for IAB type 1-O + +The test requirement for RI reporting is defined as + +- The ratio of the throughput obtained when transmitting based on IAB-MT reported RI and that obtained when transmitting with fixed rank 1 shall be $\geq \gamma_1$ ; +- The ratio of the throughput obtained when transmitting based on IAB-MT reported RI and that obtained when transmitting with fixed rank 2 shall be $\geq \gamma_2$ ; + +For the parameters specified in Table 8.2.3.4.4.2-1, the test requirements are specified in Table 8.2.3.4.5.1-1. + +**Table 8.2.3.4.5.1-1: Test requirements for RI reporting** + +| | Test 1 | Test 2 | Test 3 | +|------------|--------|--------|--------| +| $\gamma_1$ | N/A | 1.05 | 0.9 | +| $\gamma_2$ | 1.0 | N/A | N/A | + +##### 8.2.3.4.5.2 Test requirement for IAB type 2-O + +The test requirement for RI reporting is defined as + +- The ratio of the throughput obtained when transmitting based on IAB-MT reported RI and that obtained when transmitting with fixed rank 1 shall be $\geq \gamma_1$ ; +- The ratio of the throughput obtained when transmitting based on IAB-MT reported RI and that obtained when transmitting with fixed rank 2 shall be $\geq \gamma_2$ ; + +For the parameters specified in Table 8.2.3.4.4.2-1, the test requirements are specified in Table 8.2.3.4.5.2-1. + +**Table 8.2.3.4.5.2-1: Test requirements for RI reporting** + +| | Test 1 | Test 2 | Test 3 | +|------------|--------|--------|--------| +| $\gamma_1$ | N/A | 1.05 | 1.05 | +| $\gamma_2$ | 1.0 | N/A | N/A | + +## Annex A (normative): Reference measurement channels + +### A.1 IAB-DU and IAB-MT Reference measurement channels + +#### A.1.1 IAB-DU Reference measurement channels + +The Annex A in TS 38.141-2 [6] applies to IAB-DU. + +#### A.1.2 IAB-MT Reference measurement channels + +##### A.1.2.1 Fixed Reference Channels for reference sensitivity level, ACS, in-band blocking, out-of-band blocking and receiver intermodulation (QPSK, R=1/3) + +The parameters for the reference measurement channels are specified in tables A.1.2.1-1 for FR1 reference sensitivity level, ACS, in-band blocking, out-of-band blocking, receiver intermodulation, OTA sensitivity, OTA reference sensitivity level, OTA ACS, OTA in-band blocking, OTA out-of-band blocking, and OTA receiver intermodulation. + +The parameters for the reference measurement channels are specified in tables A.1.2.1-2 for FR2-1 OTA reference sensitivity level, OTA ACS, OTA in-band blocking, and OTA out-of-band blocking. + +**Table A1.2.1-1: FRC parameters for FR1 reference sensitivity level for IAB-MT.** + +| Reference channel | G-FR1-A1-22 | G-FR1-A1-23 | G-FR1-A1-25 | G-FR1-A1-26 | +|-----------------------------------------------|-------------|-------------|-------------|-------------| +| Subcarrier spacing (kHz) | 30 | 60 | 30 | 60 | +| Allocated resource blocks | 11 | 11 | 51 | 24 | +| CP-OFDM Symbols per slot (Note 1) | 9 | 9 | 9 | 9 | +| Modulation | QPSK | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 1/3 | 1/3 | 1/3 | 1/3 | +| Payload size (bits) | 736 | 736 | 3368 | 1608 | +| Transport block CRC (bits) | 16 | 16 | 16 | 16 | +| Code block CRC size (bits) | - | - | - | - | +| Number of code blocks - C | 1 | 1 | 1 | 1 | +| Code block size including CRC (bits) (Note 3) | 752 | 752 | 3384 | 1624 | +| Total number of bits per slot | 2376 | 2376 | 11016 | 5184 | +| Total symbols per slot | 1188 | 1188 | 5508 | 2592 | + +NOTE 1 : *DL-DMRS-config-type* = 1 with *DL-DMRS-max-len* = 1, *DL-DMRS-add-pos* = pos2 with $\mu$ = 2, $\nu$ = 6 and 9 as per Table 7.4.1.1.2-3 of TS 38.211 [7]. + +NOTE 2 : MCS index 4 and target coding rate = 308/1024 are adopted to calculate payload size for receiver sensitivity + +NOTE 3 : Code block size including CRC (bits) equals to in sub-clause 5.2.2 of TS 38.212 [8]. + +**Table A1.2.1-2: FRC parameters for FR2-1 reference sensitivity level for IAB-MT.** + +| Reference channel | G-FR2-A1-21 | G-FR2-A1-22 | G-FR2-A1-23 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------|-------------| +| Subcarrier spacing (kHz) | 60 | 120 | 120 | +| Allocated resource blocks | 66 | 32 | 66 | +| CP-OFDM
Symbols per slot (Note 1) | 9 | 9 | 9 | +| Modulation | QPSK | QPSK | QPSK | +| Code rate (Note 2) | 1/3 | 1/3 | 1/3 | +| Payload size (bits) | 5632 | 2792 | 5632 | +| Transport block CRC (bits) | 24 | 16 | 24 | +| Code block CRC size (bits) | - | - | - | +| Number of code blocks - C | 1 | 1 | 1 | +| Code block size including CRC (bits) (Note 3) | 4248 | 2104 | 4248 | +| Total number of bits per slot | 14256 | 6912 | 14256 | +| Total symbols per slot | 7128 | 3456 | 7128 | +| NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS, additional DM-RS position = pos2 with $l_0 = 2$ , $l = 6$ and 9 as per Table 7.4.1.1.2-3 of TS 38.211 [7].
NOTE 2: MCS index 4 and target coding rate = 308/1024 are adopted to calculate payload size. | | | | + +## A.2 IAB-DU Fixed Reference Channels + +### A.2.1 Fixed Reference Channels for PUSCH performance requirements (QPSK, R=193/1024) + +The parameters for the reference measurement channels are specified in table A.2.1-1 and table A.2.1-2 for FR1 PUSCH performance requirements: + +- FRC parameters are specified in table A.2.1-1 for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer. +- FRC parameters are specified in table A.2.1-2 for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 2 transmission layers. +- FRC parameters are specified in table A.2.1-3 for FR1 PUSCH with transform precoding enabled, additional DM-RS position = pos1 and 1 transmission layer. + +The parameters for the reference measurement channels are specified in table A.2.1-3 to table A.2.1-9 for FR2-1 PUSCH performance requirements: + +- FRC parameters are specified in table A.2.1-4 for FR2-1 PUSCH with transform precoding disabled, additional DM-RS position = pos0 and 1 transmission layer. + +- FRC parameters are specified in table A.2.1-5 for FR2-1 PUSCH with transform precoding disabled, additional DM-RS position = pos0 and 2 transmission layers. +- FRC parameters are specified in table A.2.1-6 for FR2-1 PUSCH with transform precoding enabled, additional DM-RS position = pos0 and 1 transmission layer. +- FRC parameters are specified in table A.2.1-7 for FR2-1 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer. +- FRC parameters are specified in table A.2.1-8 for FR2-1 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 2 transmission layers. +- FRC parameters are specified in table A.2.1-9 for FR2-1 PUSCH with transform precoding enabled, additional DM-RS position = pos1 and 1 transmission layer. + +**Table A.2.1-1: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | D-FR1-A.2.1-1 | D-FR1-A.2.1-2 | D-FR1-A.2.1-3 | D-FR1-A.2.1-4 | D-FR1-A.2.1-5 | D-FR1-A.2.1-6 | D-FR1-A.2.1-7 | +|-----------------------------------------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------| +| Subcarrier spacing (kHz) | 15 | 15 | 15 | 30 | 30 | 30 | 30 | +| Allocated resource blocks | 25 | 52 | 106 | 24 | 51 | 106 | 273 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | +| Code rate | 193/1024 | 193/1024 | 193/1024 | 193/1024 | 193/1024 | 193/1024 | 193/1024 | +| Payload size (bits) | 1352 | 2856 | 5768 | 1320 | 2792 | 5768 | 14856 | +| Transport block CRC (bits) | 16 | 16 | 24 | 16 | 16 | 24 | 24 | +| Code block CRC size (bits) | - | - | 24 | - | - | 24 | 24 | +| Number of code blocks - C | 1 | 1 | 2 | 1 | 1 | 2 | 4 | +| Code block size including CRC (bits) (Note 2) | 1368 | 2872 | 2920 | 1336 | 2808 | 2920 | 3744 | +| Total number of bits per slot | 7200 | 14976 | 30528 | 6912 | 14688 | 30528 | 78624 | +| Total symbols per slot | 3600 | 7488 | 15264 | 3456 | 7344 | 15264 | 39312 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1, $l_0 = 2$ and $l = 11$ for PUSCH mapping type A, $l_0 = 0$ and $l = 10$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [8]. + +**Table A.2.1-2: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 2 transmission layers (QPSK, R=193/1024)** + +| Reference channel | D-FR1-A.2.1-8 | D-FR1-A.2.1-9 | D-FR1-A.2.1-10 | D-FR1-A.2.1-11 | D-FR1-A.2.1-12 | D-FR1-A.2.1-13 | D-FR1-A.2.1-14 | +|-----------------------------------------------|---------------|---------------|----------------|----------------|----------------|----------------|----------------| +| Subcarrier spacing (kHz) | 15 | 15 | 15 | 30 | 30 | 30 | 30 | +| Allocated resource blocks | 25 | 52 | 106 | 24 | 51 | 106 | 273 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | QPSK | +| Code rate | 193/1024 | 193/1024 | 193/1024 | 193/1024 | 193/1024 | 193/1024 | 193/1024 | +| Payload size (bits) | 2728 | 5640 | 11528 | 2600 | 5512 | 11528 | 29736 | +| Transport block CRC (bits) | 16 | 24 | 24 | 16 | 24 | 24 | 24 | +| Code block CRC size (bits) | - | 24 | 24 | - | 24 | 24 | 24 | +| Number of code blocks - C | 1 | 2 | 4 | 1 | 2 | 4 | 8 | +| Code block size including CRC (bits) (Note 2) | 2744 | 2856 | 2912 | 2616 | 2792 | 2912 | 3744 | +| Total number of bits per slot | 14400 | 29952 | 61056 | 13824 | 29376 | 61056 | 157248 | +| Total symbols per slot | 7200 | 14976 | 30528 | 6912 | 14688 | 30528 | 78624 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1, $l_0 = 2$ and $l = 11$ for PUSCH mapping type A, $l_0 = 0$ and $l = 10$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [8]. + +**Table A.2.1-3: FRC parameters for FR1 PUSCH performance requirements, transform precoding enabled, additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | D-FR1-A.2.1-15 | D-FR1-A.2.1-16 | +|-----------------------------------------------|----------------|----------------| +| Subcarrier spacing (kHz) | 15 | 30 | +| Allocated resource blocks | 25 | 24 | +| DFT-s-OFDM Symbols per slot (Note 1) | 12 | 12 | +| Modulation | QPSK | QPSK | +| Code rate | 193/1024 | 193/1024 | +| Payload size (bits) | 1352 | 1320 | +| Transport block CRC (bits) | 16 | 16 | +| Code block CRC size (bits) | - | - | +| Number of code blocks - C | 1 | 1 | +| Code block size including CRC (bits) (Note 2) | 1368 | 1336 | +| Total number of bits per slot | 7200 | 6912 | +| Total symbols per slot | 3600 | 3456 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1, $l_0 = 2$ and $l = 11$ for PUSCH mapping type A, $l_0 = 0$ and $l = 10$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [8]. + +**Table A.2.1-4: FRC parameters for FR2-1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos0 and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | D-FR2-A.2.1-1 | D-FR2-A.2.1-2 | D-FR2-A.2.1-3 | D-FR2-A.2.1-4 | D-FR2-A.2.1-5 | +|-----------------------------------------------|---------------|---------------|---------------|---------------|---------------| +| Subcarrier spacing (kHz) | 60 | 60 | 120 | 120 | 120 | +| Allocated resource blocks | 66 | 132 | 32 | 66 | 132 | +| CP-OFDM Symbols per slot (Note 1) | 9 | 9 | 9 | 9 | 9 | +| Modulation | QPSK | QPSK | QPSK | QPSK | QPSK | +| Code rate | 193/1024 | 193/1024 | 193/1024 | 193/1024 | 193/1024 | +| Payload size (bits) | 2664 | 5384 | 1320 | 2664 | 5384 | +| Transport block CRC (bits) | 16 | 24 | 16 | 16 | 24 | +| Code block CRC size (bits) | - | 24 | - | - | 24 | +| Number of code blocks - C | 1 | 2 | 1 | 1 | 2 | +| Code block size including CRC (bits) (Note 2) | 2680 | 2728 | 1336 | 2680 | 2728 | +| Total number of bits per slot | 14256 | 28512 | 6912 | 14256 | 28512 | +| Total symbols per slot | 7128 | 14256 | 3456 | 7128 | 14256 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos0 with $l_0 = 0$ as per table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [8]. + +**Table A.2.1-5: FRC parameters for FR2-1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos0 and 2 transmission layers (QPSK, R=193/1024)** + +| Reference channel | D-FR2-A.2.1-6 | D-FR2-A.2.1-7 | D-FR2-A.2.1-8 | D-FR2-A.2.1-9 | D-FR2-A.2.1-10 | +|-----------------------------------------------|---------------|---------------|---------------|---------------|----------------| +| Subcarrier spacing (kHz) | 60 | 60 | 120 | 120 | 120 | +| Allocated resource blocks | 66 | 132 | 32 | 66 | 132 | +| CP-OFDM Symbols per slot (Note 1) | 9 | 9 | 9 | 9 | 9 | +| Modulation | QPSK | QPSK | QPSK | QPSK | QPSK | +| Code rate | 193/1024 | 193/1024 | 193/1024 | 193/1024 | 193/1024 | +| Payload size (bits) | 5384 | 10752 | 2600 | 5384 | 10752 | +| Transport block CRC (bits) | 24 | 24 | 16 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | - | 24 | 24 | +| Number of code blocks - C | 2 | 3 | 1 | 2 | 3 | +| Code block size including CRC (bits) (Note 2) | 2728 | 3616 | 2616 | 2728 | 3616 | +| Total number of bits per slot | 28512 | 57024 | 13824 | 28512 | 57024 | +| Total symbols per slot | 14256 | 28512 | 6912 | 14256 | 28512 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos0 with $l_0 = 0$ as per table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [8]. + +**Table A.2.1-6: FRC parameters for FR2-1 PUSCH performance requirements, transform precoding enabled, additional DM-RS position = pos0 and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | D-FR2-A.2.1-11 | D-FR2-A.2.1-12 | +|-----------------------------------------------|----------------|----------------| +| Subcarrier spacing (kHz) | 60 | 120 | +| Allocated resource blocks | 30 | 30 | +| DFT-s-OFDM Symbols per slot (Note 1) | 9 | 9 | +| Modulation | QPSK | QPSK | +| Code rate | 193/1024 | 193/1024 | +| Payload size (bits) | 1224 | 1224 | +| Transport block CRC (bits) | 16 | 16 | +| Code block CRC size (bits) | - | - | +| Number of code blocks - C | 1 | 1 | +| Code block size including CRC (bits) (Note 2) | 1240 | 1240 | +| Total number of bits per slot | 6480 | 6480 | +| Total symbols per slot | 3240 | 3240 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos0 with $l_0 = 0$ as per table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [8]. + +**Table A.2.1-7: FRC parameters for FR2-1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | D-FR2-A.2.1-13 | D-FR2-A.2.1-14 | D-FR2-A.2.1-15 | D-FR2-A.2.1-16 | D-FR2-A.2.1-17 | +|-----------------------------------------------|----------------|----------------|----------------|----------------|----------------| +| Subcarrier spacing (kHz) | 60 | 60 | 120 | 120 | 120 | +| Allocated resource blocks | 66 | 132 | 32 | 66 | 132 | +| CP-OFDM Symbols per slot (Note 1) | 8 | 8 | 8 | 8 | 8 | +| Modulation | QPSK | QPSK | QPSK | QPSK | QPSK | +| Code rate | 193/1024 | 193/1024 | 193/1024 | 193/1024 | 193/1024 | +| Payload size (bits) | 2408 | 4744 | 1160 | 2408 | 4744 | +| Transport block CRC (bits) | 16 | 24 | 16 | 16 | 24 | +| Code block CRC size (bits) | - | 24 | - | - | 24 | +| Number of code blocks - C | 1 | 2 | 1 | 1 | 2 | +| Code block size including CRC (bits) (Note 2) | 2424 | 2408 | 1176 | 2424 | 2408 | +| Total number of bits per slot | 12672 | 25344 | 6144 | 12672 | 25344 | +| Total symbols per slot | 6336 | 12672 | 3072 | 6336 | 12672 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1 with $l_0 = 0$ and $l = 8$ as per table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [8]. + +**Table A.2.1-8: FRC parameters for FR2-1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 2 transmission layers (QPSK, R=193/1024)** + +| Reference channel | D-FR2-A.2.1-18 | D-FR2-A.2.1-19 | D-FR2-A.2.1-20 | D-FR2-A.2.1-21 | D-FR2-A.2.1-22 | +|-----------------------------------------------|----------------|----------------|----------------|----------------|----------------| +| Subcarrier spacing (kHz) | 60 | 60 | 120 | 120 | 120 | +| Allocated resource blocks | 66 | 132 | 32 | 66 | 132 | +| CP-OFDM Symbols per slot (Note 1) | 8 | 8 | 8 | 8 | 8 | +| Modulation | QPSK | QPSK | QPSK | QPSK | QPSK | +| Code rate | 193/1024 | 193/1024 | 193/1024 | 193/1024 | 193/1024 | +| Payload size (bits) | 4744 | 9480 | 2408 | 4744 | 9480 | +| Transport block CRC (bits) | 24 | 24 | 16 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | - | 24 | 24 | +| Number of code blocks - C | 2 | 3 | 1 | 2 | 3 | +| Code block size including CRC (bits) (Note 2) | 2408 | 3192 | 2424 | 2408 | 3192 | +| Total number of bits per slot | 25344 | 50688 | 12288 | 25344 | 50688 | +| Total symbols per slot | 12672 | 25344 | 6144 | 12672 | 25344 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1 with $l_0 = 0$ and $l = 8$ as per table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [8]. + +**Table A.2.1-9: FRC parameters for FR2-1 PUSCH performance requirements, transform precoding enabled, additional DM-RS position = pos1 and 1 transmission layer (QPSK, R=193/1024)** + +| Reference channel | D-FR2-A.2.1-23 | D-FR2-A.2.1-24 | +|-----------------------------------------------|----------------|----------------| +| Subcarrier spacing (kHz) | 60 | 120 | +| Allocated resource blocks | 30 | 30 | +| DFT-s-OFDM Symbols per slot (Note 1) | 8 | 8 | +| Modulation | QPSK | QPSK | +| Code rate | 193/1024 | 193/1024 | +| Payload size (bits) | 1128 | 1128 | +| Transport block CRC (bits) | 16 | 16 | +| Code block CRC size (bits) | - | - | +| Number of code blocks - C | 1 | 1 | +| Code block size including CRC (bits) (Note 2) | 1144 | 1144 | +| Total number of bits per slot | 5760 | 5760 | +| Total symbols per slot | 2880 | 2880 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1 with $l_0 = 0$ and $l = 8$ as per table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [8]. + +## A.2.2 Fixed Reference Channels for PUSCH performance requirements (16QAM, R=434/1024) + +The parameters for the reference measurement channels are specified in table A.2.2-1 for FR2-1 PUSCH performance requirements with transform precoding disabled, additional DM-RS position = pos0 and 2 transmission layers. + +The parameters for the reference measurement channels are specified in table A.2.2-2 for FR2-1 PUSCH performance requirements with transform precoding disabled, additional DM-RS position = pos1 and 2 transmission layers. + +**Table A.2.2-1: FRC parameters for FR2-1 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos0 and 2 transmission layers (16QAM, R=434/1024)** + +| Reference channel | D-FR2-A.2.2-1 | D-FR2-A.2.2-2 | D-FR2-A.2.2-3 | D-FR2-A.2.2-4 | D-FR2-A.2.2-5 | +|-----------------------------------------------|---------------|---------------|---------------|---------------|---------------| +| Subcarrier spacing (kHz) | 60 | 60 | 120 | 120 | 120 | +| Allocated resource blocks | 66 | 132 | 32 | 66 | 132 | +| CP-OFDM Symbols per slot (Note 1) | 9 | 9 | 9 | 9 | 9 | +| Modulation | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | +| Code rate | 434/1024 | 434/1024 | 434/1024 | 434/1024 | 434/1024 | +| Payload size (bits) | 24072 | 48168 | 11784 | 24072 | 48168 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | 24 | 24 | +| Number of code blocks - C | 3 | 6 | 2 | 3 | 6 | +| Code block size including CRC (bits) (Note 2) | 8056 | 8056 | 5928 | 8056 | 8056 | +| Total number of bits per slot | 57024 | 114048 | 27648 | 57024 | 114048 | +| Total symbols per slot | 14256 | 28512 | 6912 | 14256 | 28512 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, Additional DM-RS position = pos0 with $l_0 = 0$ as per Table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [8]. + +**Table A.2.2-2: FRC parameters for FR2-1 PUSCH performance requirements, transform precoding disabled, Additional DM-RS position = pos1 and 2 transmission layers (16QAM, R=434/1024)** + +| Reference channel | D-FR2-A.2.2-6 | D-FR2-A.2.2-7 | D-FR2-A.2.2-8 | D-FR2-A.2.2-9 | D-FR2-A.2.2-10 | +|-----------------------------------------------|---------------|---------------|---------------|---------------|----------------| +| Subcarrier spacing (kHz) | 60 | 60 | 120 | 120 | 120 | +| Allocated resource blocks | 66 | 132 | 32 | 66 | 132 | +| CP-OFDM Symbols per slot (Note 1) | 8 | 8 | 8 | 8 | 8 | +| Modulation | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | +| Code rate | 434/1024 | 434/1024 | 434/1024 | 434/1024 | 434/1024 | +| Payload size (bits) | 21504 | 43032 | 10504 | 21504 | 43032 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | 24 | 24 | +| Number of code blocks - C | 3 | 6 | 2 | 3 | 6 | +| Code block size including CRC (bits) (Note 2) | 7200 | 7200 | 5288 | 7200 | 7200 | +| Total number of bits per slot | 50688 | 101376 | 24576 | 50688 | 101376 | +| Total symbols per slot | 12672 | 25344 | 6144 | 12672 | 25344 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, Additional DM-RS position = pos1 with $l_0 = 0$ and $l = 8$ as per Table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in sub-clause 5.2.2 of TS 38.212 [8]. + +## A.2.3 Fixed Reference Channels for PUSCH performance requirements (16QAM, R=658/1024) + +The parameters for the reference measurement channels are specified in table A.2.3-1 and table A.2.3-2 for FR1 PUSCH performance requirements: + +- FRC parameters are specified in table A.2.3-1 for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer. +- FRC parameters are specified in table A.2.3-2 for FR1 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 2 transmission layers. + +The parameters for the reference measurement channels are specified in table A.2.3-3 to table A.2.3-6 for FR2-1 PUSCH performance requirements: + +- FRC parameters are specified in table A.2.3-3 for FR2-1 PUSCH with transform precoding disabled, additional DM-RS position = pos0 and 1 transmission layer. + +- FRC parameters are specified in table A.2.3-4 for FR2-1 PUSCH with transform precoding disabled, additional DM-RS position = pos0 and 2 transmission layers. +- FRC parameters are specified in table A.1.3-5 for FR2-1 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer. +- FRC parameters are specified in table A.2.3-6 for FR2-1 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 2 transmission layers. + +**Table A.2.3-1: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer (16QAM, R=658/1024)** + +| Reference channel | D-FR1-A.2.3-1 | D-FR1-A.2.3-2 | D-FR1-A.2.3-3 | D-FR1-A.2.3-4 | D-FR1-A.2.3-5 | D-FR1-A.2.3-6 | D-FR1-A.2.3-7 | +|-----------------------------------------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------| +| Subcarrier spacing (kHz) | 15 | 15 | 15 | 30 | 30 | 30 | 30 | +| Allocated resource blocks | 25 | 52 | 106 | 24 | 51 | 106 | 273 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | +| Code rate | 658/1024 | 658/1024 | 658/1024 | 658/1024 | 658/1024 | 658/1024 | 658/1024 | +| Payload size (bits) | 9224 | 19464 | 38936 | 8968 | 18960 | 38936 | 100392 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | 24 | 24 | 24 | 24 | +| Number of code blocks - C | 2 | 3 | 5 | 2 | 3 | 5 | 12 | +| Code block size including CRC (bits) (Note 2) | 4648 | 6520 | 7816 | 4520 | 6352 | 7816 | 8392 | +| Total number of bits per slot | 14400 | 29952 | 61056 | 13824 | 29376 | 61056 | 157248 | +| Total symbols per slot | 3600 | 7488 | 15264 | 3456 | 7344 | 15264 | 39312 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1, $l_0 = 2$ and $l = 11$ for PUSCH mapping type A, $l_0 = 0$ and $l = 10$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [8]. + +**Table A.2.3-2: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 2 transmission layers (16QAM, R=658/1024)** + +| Reference channel | D-FR1-A.2.3-8 | D-FR1-A.2.3-9 | D-FR1-A.2.3-10 | D-FR1-A.2.3-11 | D-FR1-A.2.3-12 | D-FR1-A.2.3-13 | D-FR1-A.2.3-14 | +|-----------------------------------------------|---------------|---------------|----------------|----------------|----------------|----------------|----------------| +| Subcarrier spacing (kHz) | 15 | 15 | 15 | 30 | 30 | 30 | 30 | +| Allocated resource blocks | 25 | 52 | 106 | 24 | 51 | 106 | 273 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | +| Code rate | 658/1024 | 658/1024 | 658/1024 | 658/1024 | 658/1024 | 658/1024 | 658/1024 | +| Payload size (bits) | 18432 | 38936 | 77896 | 17928 | 37896 | 77896 | 200808 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | 24 | 24 | 24 | 24 | +| Number of code blocks - C | 3 | 5 | 10 | 3 | 5 | 10 | 24 | +| Code block size including CRC (bits) (Note 2) | 6176 | 7816 | 7816 | 6008 | 7608 | 7816 | 8392 | +| Total number of bits per slot | 28800 | 59904 | 122112 | 27648 | 58752 | 122112 | 314496 | +| Total symbols per slot | 7200 | 14976 | 30528 | 6912 | 14688 | 30528 | 78624 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1, $l_0 = 2$ and $l = 11$ for PUSCH mapping type A, $l_0 = 0$ and $l = 10$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [8]. + +**Table A.2.3-3: FRC parameters for FR2-1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos0 and 1 transmission layer (16QAM, R=658/1024)** + +| Reference channel | D-FR2-A.2.3-1 | D-FR2-A.2.3-2 | D-FR2-A.2.3-3 | D-FR2-A.2.3-4 | D-FR2-A.2.3-5 | +|-----------------------------------------------|---------------|---------------|---------------|---------------|---------------| +| Subcarrier spacing (kHz) | 60 | 60 | 120 | 120 | 120 | +| Allocated resource blocks | 66 | 132 | 32 | 66 | 132 | +| CP-OFDM Symbols per slot (Note 1) | 9 | 9 | 9 | 9 | 9 | +| Modulation | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | +| Code rate | 658/1024 | 658/1024 | 658/1024 | 658/1024 | 658/1024 | +| Payload size (bits) | 18432 | 36896 | 8968 | 18432 | 36896 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | 24 | 24 | +| Number of code blocks - C | 3 | 5 | 2 | 3 | 5 | +| Code block size including CRC (bits) (Note 2) | 6176 | 7408 | 4520 | 6176 | 7408 | +| Total number of bits per slot | 28512 | 57024 | 13824 | 28512 | 57024 | +| Total symbols per slot | 7128 | 14256 | 3456 | 7128 | 14256 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos0 with $l_0 = 0$ as per table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [8]. + +**Table A.2.3-4: FRC parameters for FR2-1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos0 and 2 transmission layers (16QAM, R=658/1024)** + +| Reference channel | D-FR2-A.2.3-6 | D-FR2-A.2.3-7 | D-FR2-A.2.3-8 | D-FR2-A.2.3-9 | D-FR2-A.2.3-10 | +|-----------------------------------------------|---------------|---------------|---------------|---------------|----------------| +| Subcarrier spacing (kHz) | 60 | 60 | 120 | 120 | 120 | +| Allocated resource blocks | 66 | 132 | 32 | 66 | 132 | +| CP-OFDM Symbols per slot (Note 1) | 9 | 9 | 9 | 9 | 9 | +| Modulation | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | +| Code rate | 658/1024 | 658/1024 | 658/1024 | 658/1024 | 658/1024 | +| Payload size (bits) | 36896 | 73776 | 17928 | 36896 | 73776 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | 24 | 24 | +| Number of code blocks - C | 5 | 9 | 3 | 5 | 9 | +| Code block size including CRC (bits) (Note 2) | 7408 | 8224 | 6008 | 7408 | 8224 | +| Total number of bits per slot | 57024 | 114048 | 27648 | 57024 | 114048 | +| Total symbols per slot | 14256 | 28512 | 6912 | 14256 | 28512 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos0 with $l_0 = 0$ as per table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [8]. + +**Table A.2.3-5: FRC parameters for FR2-1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer (16QAM, R=658/1024)** + +| Reference channel | D-FR2-A.2.3-11 | D-FR2-A.2.3-12 | D-FR2-A.2.3-13 | D-FR2-A.2.3-14 | D-FR2-A.2.3-15 | +|-----------------------------------------------|----------------|----------------|----------------|----------------|----------------| +| Subcarrier spacing (kHz) | 60 | 60 | 120 | 120 | 120 | +| Allocated resource blocks | 66 | 132 | 32 | 66 | 132 | +| CP-OFDM Symbols per slot (Note 1) | 8 | 8 | 8 | 8 | 8 | +| Modulation | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | +| Code rate | 658/1024 | 658/1024 | 658/1024 | 658/1024 | 658/1024 | +| Payload size (bits) | 16392 | 32776 | 7936 | 16392 | 32776 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | - | 24 | 24 | +| Number of code blocks - C | 2 | 4 | 1 | 2 | 4 | +| Code block size including CRC (bits) (Note 2) | 8232 | 8224 | 7960 | 8232 | 8224 | +| Total number of bits per slot | 25344 | 50688 | 12288 | 25344 | 50688 | +| Total symbols per slot | 6336 | 12672 | 3072 | 6336 | 12672 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1 with $l_0 = 0$ and $l = 8$ as per table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [8]. + +**Table A.2.3-6: FRC parameters for FR2-1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 2 transmission layers (16QAM, R=658/1024)** + +| Reference channel | D-FR2-A.2.3-16 | D-FR2-A.2.3-17 | D-FR2-A.2.3-18 | D-FR2-A.2.3-19 | D-FR2-A.2.3-20 | +|-----------------------------------------------|----------------|----------------|----------------|----------------|----------------| +| Subcarrier spacing (kHz) | 60 | 60 | 120 | 120 | 120 | +| Allocated resource blocks | 66 | 132 | 32 | 66 | 132 | +| CP-OFDM Symbols per slot (Note 1) | 8 | 8 | 8 | 8 | 8 | +| Modulation | 16QAM | 16QAM | 16QAM | 16QAM | 16QAM | +| Code rate | 658/1024 | 658/1024 | 658/1024 | 658/1024 | 658/1024 | +| Payload size (bits) | 32776 | 65576 | 15880 | 32776 | 65576 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | 24 | 24 | +| Number of code blocks - C | 4 | 8 | 2 | 4 | 8 | +| Code block size including CRC (bits) (Note 2) | 8224 | 8224 | 7976 | 8224 | 8224 | +| Total number of bits per slot | 50688 | 101376 | 24576 | 50688 | 101376 | +| Total symbols per slot | 12672 | 25344 | 6144 | 12672 | 25344 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1 with $l_0 = 0$ and $l = 8$ as per table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [8]. + +## A.2.4 Fixed Reference Channels for PUSCH performance requirements (64QAM, R=567/1024) + +The parameters for the reference measurement channels are specified in table A.2.4-1 for FR1 PUSCH performance requirements: + +- FRC parameters are specified in table A.2.4-1 for FR1 PUSCH with transform precoding disabled, Additional DM-RS position = pos1 and 1 transmission layer. + +The parameters for the reference measurement channels are specified in table A.2.4-2 and table A.2.4-3 for FR2-1 PUSCH performance requirements: + +- FRC parameters are specified in table A.2.4-2 for FR2-1 PUSCH with transform precoding disabled, additional DM-RS position = pos0 and 1 transmission layer. +- FRC parameters are specified in table A.2.4-3 for FR2-1 PUSCH with transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer. + +**Table A.2.4-1: FRC parameters for FR1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer (64QAM, R=567/1024)** + +| Reference channel | D-FR1-A.2.4-1 | D-FR1-A.2.4-2 | D-FR1-A.2.4-3 | D-FR1-A.2.4-4 | D-FR1-A.2.4-5 | D-FR1-A.2.4-6 | D-FR1-A.2.4-7 | +|-----------------------------------------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------| +| Subcarrier spacing (kHz) | 15 | 15 | 15 | 30 | 30 | 30 | 30 | +| Allocated resource blocks | 25 | 52 | 106 | 24 | 51 | 106 | 273 | +| CP-OFDM Symbols per slot (Note 1) | 12 | 12 | 12 | 12 | 12 | 12 | 12 | +| Modulation | 64QAM | 64QAM | 64QAM | 64QAM | 64QAM | 64QAM | 64QAM | +| Code rate | 567/1024 | 567/1024 | 567/1024 | 567/1024 | 567/1024 | 567/1024 | 567/1024 | +| Payload size (bits) | 12040 | 25104 | 50184 | 11528 | 24576 | 50184 | 131176 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | 24 | 24 | 24 | 24 | +| Number of code blocks - C | 2 | 3 | 6 | 2 | 3 | 6 | 16 | +| Code block size including CRC (bits) (Note 2) | 6056 | 8400 | 8392 | 5800 | 8224 | 8392 | 8224 | +| Total number of bits per slot | 21600 | 44928 | 91584 | 20736 | 44064 | 91584 | 235872 | +| Total symbols per slot | 3600 | 7488 | 15264 | 3456 | 7344 | 15264 | 39312 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1, $l_0 = 2$ and $l = 11$ for PUSCH mapping type A, $l_0 = 0$ and $l = 10$ for PUSCH mapping type B as per table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [8]. + +**Table A.2.4-2: FRC parameters for FR2-1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos0 and 1 transmission layer (64QAM, R=567/1024)** + +| Reference channel | D-FR2-A.2.4-1 | D-FR2-A.2.4-2 | D-FR2-A.2.4-3 | D-FR2-A.2.4-4 | D-FR2-A.2.4-5 | +|-----------------------------------------------|---------------|---------------|---------------|---------------|---------------| +| Subcarrier spacing (kHz) | 60 | 60 | 120 | 120 | 120 | +| Allocated resource blocks | 66 | 132 | 32 | 66 | 132 | +| CP-OFDM Symbols per slot (Note 1) | 9 | 9 | 9 | 9 | 9 | +| Modulation | 64QAM | 64QAM | 64QAM | 64QAM | 64QAM | +| Code rate | 567/1024 | 567/1024 | 567/1024 | 567/1024 | 567/1024 | +| Payload size (bits) | 23568 | 47112 | 11528 | 23568 | 47112 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | 24 | 24 | +| Number of code blocks - C | 3 | 6 | 2 | 3 | 6 | +| Code block size including CRC (bits) (Note 2) | 7888 | 7880 | 5800 | 7888 | 7880 | +| Total number of bits per slot | 42768 | 85536 | 20736 | 42768 | 85536 | +| Total symbols per slot | 7128 | 14256 | 3456 | 7128 | 14256 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos0 with $l_0 = 0$ as per table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [8]. + +**Table A.2.4-3: FRC parameters for FR2-1 PUSCH performance requirements, transform precoding disabled, additional DM-RS position = pos1 and 1 transmission layer (64QAM, R=567/1024)** + +| Reference channel | D-FR2-A.2.4-6 | D-FR2-A.2.4-7 | D-FR2-A.2.4-8 | D-FR2-A.2.4-9 | D-FR2-A.2.4-10 | +|-----------------------------------------------|---------------|---------------|---------------|---------------|----------------| +| Subcarrier spacing (kHz) | 60 | 60 | 120 | 120 | 120 | +| Allocated resource blocks | 66 | 132 | 32 | 66 | 132 | +| CP-OFDM Symbols per slot (Note 1) | 8 | 8 | 8 | 8 | 8 | +| Modulation | 64QAM | 64QAM | 64QAM | 64QAM | 64QAM | +| Code rate | 567/1024 | 567/1024 | 567/1024 | 567/1024 | 567/1024 | +| Payload size (bits) | 21000 | 42016 | 10248 | 21000 | 42016 | +| Transport block CRC (bits) | 24 | 24 | 24 | 24 | 24 | +| Code block CRC size (bits) | 24 | 24 | 24 | 24 | 24 | +| Number of code blocks - C | 3 | 5 | 2 | 3 | 5 | +| Code block size including CRC (bits) (Note 2) | 7032 | 8432 | 5160 | 7032 | 8432 | +| Total number of bits per slot | 38016 | 76032 | 18432 | 38016 | 76032 | +| Total symbols per slot | 6336 | 12672 | 3072 | 6336 | 12672 | + +NOTE 1: DM-RS configuration type = 1 with DM-RS duration = single-symbol DM-RS and the number of DM-RS CDM groups without data is 2, additional DM-RS position = pos1 with $l_0 = 0$ and $l = 8$ as per table 6.4.1.1.3-3 of TS 38.211 [7]. + +NOTE 2: Code block size including CRC (bits) equals to $K'$ in clause 5.2.2 of TS 38.212 [8]. + +## A.2.5 PRACH Test preambles + +**Table A.2.5-1 Test preambles for Normal Mode in FR1** + +| Burst format | SCS (kHz) | Ncs | Logical sequence index | v | +|------------------------|-----------|-----|------------------------|----| +| 0 | 1.25 | 13 | 22 | 32 | +| A1, A2, A3, B4, C0, C2 | 15 | 23 | 0 | 0 | +| | 30 | 46 | 0 | 0 | + +**Table A.2.5-2 Test preambles for Normal Mode in FR2** + +| Burst format | SCS (kHz) | Ncs | Logical sequence index | v | +|------------------------|-----------|-----|------------------------|---| +| A1, A2, A3, B4, C0, C2 | 60 | 69 | 0 | 0 | +| | 120 | 69 | 0 | 0 | + +## A.3 IAB-MT Fixed Reference Channels + +### A.3.1 Fixed Reference Channels for PDSCH performance requirements (16QAM) + +The parameters for the reference measurement channels are specified in table A.3.1-1 for FR1 PDSCH performance requirements. + +The parameters for the reference measurement channels are specified in table A.3.1-2 for FR2-1 PDSCH performance requirements. + +**Table A.3.1-1: Fixed Reference Channels for FR1 PDSCH (16QAM)** + +| Reference channel | M-FR1-A.3.1-1 | M-FR1-A.3.1-2 | M-FR1-A.3.1-3 | +|-----------------------------------------|---------------|---------------|---------------| +| Channel bandwidth (MHz) | 40 | 40 | 40 | +| Subcarrier spacing (kHz) | 30 | 30 | 30 | +| Allocated resource blocks | 106 | 106 | 106 | +| Number of consecutive PDSCH symbols | 12 | 12 | 12 | +| MCS table | 64QAM | 64QAM | 64QAM | +| MCS index | 13 | 13 | 13 | +| Modulation | 16QAM | 16QAM | 16QAM | +| Target Coding Rate | 490/1024 | 490/1024 | 490/1024 | +| Number of MIMO layers | 1 | 3 | 4 | +| Number of DMRS REs | 12 | 24 | 24 | +| Overhead for TBS determination | 0 | 0 | 0 | +| Information Bit Payload per Slot (bits) | 26632 | 73776 | 98376 | +| Transport block CRC per Slot (bits) | 24 | 24 | 24 | +| Number of Code Blocks per Slot | 4 | 9 | 12 | +| Binary Channel Bits Per Slot (bits) | 55968 | 152640 | 203520 | + +**Table A.3.1-2: Fixed Reference Channels for FR2-1 PDSCH (16QAM)** + +| Reference channel | M-FR2-A.3.1-1 | M-FR2-A.3.1-2 | M-FR2-A.3.1-3 | +|-----------------------------------------|---------------|---------------|---------------| +| Channel bandwidth (MHz) | 100 | 100 | 50 | +| Subcarrier spacing (kHz) | 120 | 120 | 60 | +| Allocated resource blocks | 66 | 66 | 66 | +| Number of consecutive PDSCH symbols | 13 | 13 | 13 | +| MCS table | 64QAM | 64QAM | 64QAM | +| MCS index | 13 | 13 | 13 | +| Modulation | 16QAM | 16QAM | 16QAM | +| Target Coding Rate | 490/1024 | 490/1024 | 490/1024 | +| Number of MIMO layers | 1 | 2 | 2 | +| Number of DMRS REs | 12 | 12 | 12 | +| Overhead for TBS determination | 6 | 6 | 6 | +| Information Bit Payload per Slot (bits) | 17424 | 34816 | 34816 | +| Transport block CRC per Slot (bits) | 24 | 24 | 24 | +| Number of Code Blocks per Slot | 3 | 5 | 5 | +| Binary Channel Bits Per Slot (bits) | 36564 | 73128 | 73128 | + +## A.3.2 Fixed Reference Channels for PDSCH performance requirements (64QAM) + +The parameters for the reference measurement channels are specified in table A.3.2-1 for FR1 PDSCH performance requirements. + +The parameters for the reference measurement channels are specified in table A.3.2-2 for FR2-1 PDSCH performance requirements. + +**Table A.3.2-1: Fixed Reference Channels for FR1 PDSCH (64QAM)** + +| Reference channel | M-FR1-A.3.2-1 | +|-----------------------------------------|---------------| +| Channel bandwidth (MHz) | 40 | +| Subcarrier spacing (kHz) | 30 | +| Allocated resource blocks | 106 | +| Number of consecutive PDSCH symbols | 12 | +| MCS table | 64QAM | +| MCS index | 19 | +| Modulation | 64QAM | +| Target Coding Rate | 517/1024 | +| Number of MIMO layers | 2 | +| Number of DMRS REs | 12 | +| Overhead for TBS determination | 0 | +| Information Bit Payload per Slot (bits) | 83976 | +| Transport block CRC per Slot (bits) | 24 | +| Number of Code Blocks per Slot | 10 | +| Binary Channel Bits Per Slot (bits) | 167904 | + +**Table A.3.2-2: Fixed Reference Channels for FR2-1 PDSCH (64QAM)** + +| Reference channel | M-FR2-A.3.2-1 | M-FR2-A.3.2-2 | +|-----------------------------------------|---------------|---------------| +| Channel bandwidth (MHz) | 100 | 100 | +| Subcarrier spacing (kHz) | 120 | 120 | +| Allocated resource blocks | 66 | 66 | +| Number of consecutive PDSCH symbols | 13 | 13 | +| MCS table | 64QAM | 64QAM | +| MCS index | 18 | 17 | +| Modulation | 64QAM | 64QAM | +| Target Coding Rate | 466/1024 | 438/1024 | +| Number of MIMO layers | 1 | 2 | +| Number of DMRS REs | 12 | 12 | +| Overhead for TBS determination | 6 | 6 | +| Information Bit Payload per Slot (bits) | 25104 | 47112 | +| Transport block CRC per Slot (bits) | 24 | 24 | +| Number of Code Blocks per Slot | 3 | 6 | +| Binary Channel Bits Per Slot (bits) | 54846 | 109692 | + +### A.3.3 Fixed Reference Channels for PDSCH performance requirements (256QAM) + +The parameters for the reference measurement channels are specified in table A.3.3-1 for FR1 PDSCH performance requirements. + +**Table A.3.3-1: Fixed Reference Channels for FR1 PDSCH (256QAM)** + +| Reference channel | M-FR1-A.3.3-1 | +|-----------------------------------------|---------------| +| Channel bandwidth (MHz) | 40 | +| Subcarrier spacing (kHz) | 30 | +| Allocated resource blocks | 106 | +| Number of consecutive PDSCH symbols | 12 | +| MCS table | 256QAM | +| MCS index | 24 | +| Modulation | 256QAM | +| Target Coding Rate | 0.82 | +| Number of MIMO layers | 1 | +| Number of DMRS REs | 12 | +| Overhead for TBS determination | 0 | +| Information Bit Payload per Slot (bits) | 92200 | +| Transport block CRC per Slot (bits) | 24 | +| Number of Code Blocks per Slot | 11 | +| Binary Channel Bits Per Slot (bits) | 111936 | + +### A.3.4 Fixed Reference Channels for PDCCH performance requirements + +The parameters for the reference measurement channels are specified in table A.3.4-1 for FR1 PDCCH performance requirements. + +The parameters for the reference measurement channels are specified in table A.3.4-2 for FR2-1 PDCCH performance requirements. + +**Table A.3.4-1: Fixed Reference Channels for FR1 PDCCH** + +| Reference channel | M-FR1-A.3.4-1 | M-FR1-A.3.4-2 | M-FR1-A.3.4-3 | +|-------------------------------------|---------------|---------------|---------------| +| Subcarrier spacing (kHz) | 30 | 30 | 30 | +| CORESET frequency domain allocation | 102 | 102 | 90 | +| CORESET time domain allocation | 1 | 1 | 1 | +| Aggregation level | 2 | 4 | 8 | +| DCI Format | 1_0 | 1_1 | 1_1 | +| Payload (without CRC) (bits) | 41 | 53 | 53 | + +**Table A.3.4-2: Fixed Reference Channels for FR2-1 PDCCH** + +| Reference channel | M-FR2-A.3.4-1 | M-FR2-A.3.4-2 | M-FR2-A.3.4-3 | +|-------------------------------------|---------------|---------------|---------------| +| Subcarrier spacing (kHz) | 120 | 120 | 120 | +| CORESET frequency domain allocation | 60 | 60 | 60 | +| CORESET time domain allocation | 1 | 1 | 1 | +| Aggregation level | 2 | 4 | 8 | +| DCI Format | 1_0 | 1_1 | 1_1 | +| Payload (without CRC) (bits) | 40 | 56 | 56 | + +### A.3.5 Fixed Reference Channels for CSI reporting requirements + +The parameters for the reference measurement channels are specified in table A.3.5-1 for FR1 CQI and RI reporting requirements with CQI table 2 and MCS table 2. + +The parameters for the reference measurement channels are specified in table A.3.5-2 for FR1 PMI reporting requirements. + +The parameters for the reference measurement channels are specified in table A.3.5-3 for FR2-1 CQI and RI reporting requirements with CQI table 1 and MCS table 1. + +The parameters for the reference measurement channels are specified in table A.3.5-4 for FR2-1 PMI reporting requirements. + +**Table A.3.5-1: FRC for FR1 CQI and RI reporting with CQI table 2 and MCS table 2** + +| Reference channel | | | | M-FR1-A.3.5-1 | M-FR1-A.3.5-2 | M-FR1-A.3.5-3 | M-FR1-A.3.5-4 | +|-------------------------------------------|---------------------|-----------|------------|----------------------------------|---------------|---------------|---------------| +| Number of allocated PDSCH resource blocks | | | | 106 | 106 | 106 | 106 | +| Number of consecutive PDSCH symbols | | | | 12 | 12 | 12 | 12 | +| Number of PDSCH MIMO layers | | | | 1 | 2 | 3 | 4 | +| Number of DMRS REs (Note 1) | | | | 24 | 24 | 24 | 24 | +| Overhead for TBS determination | | | | 0 | 0 | 0 | 0 | +| Available RE-s for PDSCH | | | | 12720 | 12720 | 12720 | 12720 | +| CQI index | Spectral efficiency | MCS index | Modulation | Information Bit Payload per Slot | | | | +| 0 | OOR | OOR | OOR | N/A | N/A | N/A | N/A | +| 1 | 0.1523 | 0 | QPSK | 2976 | 5896 | 8976 | 11784 | +| 2 | 0.3770 | 1 | | 4744 | 9480 | 14344 | 18976 | +| 3 | 0.8770 | 3 | | 11016 | 22536 | 33816 | 45096 | +| 4 | 1.4766 | 5 | 16QAM | 18960 | 37896 | 56368 | 75792 | +| 5 | 1.9141 | 7 | | 24576 | 49176 | 73776 | 98376 | +| 6 | 2.4063 | 9 | | 30728 | 61480 | 92200 | 122976 | +| 7 | 2.7305 | 11 | 64QAM | 34816 | 69672 | 104496 | 139376 | +| 8 | 3.3223 | 13 | | 42016 | 83976 | 127080 | 167976 | +| 9 | 3.9023 | 15 | | 49176 | 98376 | 147576 | 196776 | +| 10 | 4.5234 | 17 | 256QAM | 57376 | 114776 | 172176 | 229576 | +| 11 | 5.1152 | 19 | | 65576 | 131176 | 196776 | 262376 | +| 12 | 5.5547 | 21 | | 69672 | 139376 | 213176 | 278776 | +| 13 | 6.2266 | 23 | | 79896 | 159880 | 237776 | 319784 | +| 14 | 6.9141 | 25 | | 88064 | 176208 | 262376 | 352440 | +| 15 | 7.4063 | 27 | | 94248 | 188576 | 278776 | 376896 | + +NOTE 1: Number of DMRS REs includes the overhead of the DM-RS CDM groups without data. + +NOTE 2: PDSCH is only scheduled on slots which are full DL. + +**Table A.3.5-2: Fixed Reference Channels for FR1 PMI reporting (16QAM)** + +| Reference channel | M-FR1-A.3.5-5 | M-FR1-A.3.5-6 | +|-----------------------------------------|---------------|---------------| +| Channel bandwidth (MHz) | 40 | 40 | +| Subcarrier spacing (kHz) | 30 | 30 | +| Allocated resource blocks | 106 | 106 | +| Number of consecutive PDSCH symbols | 12 | 12 | +| MCS table | 64QAM | 64QAM | +| MCS index | 13 | 13 | +| Modulation | 16QAM | 16QAM | +| Target Coding Rate | 490/1024 | 490/1024 | +| Number of MIMO layers | 1 | 2 | +| Number of DMRS REs | 24 | 24 | +| Overhead for TBS determination | 0 | 0 | +| Information Bit Payload per Slot (bits) | 24576 | 49176 | +| Transport block CRC per Slot (bits) | 24 | 24 | +| Number of Code Blocks per Slot | 3 | 6 | +| Binary Channel Bits Per Slot (bits) | 50880 | 101760 | + +**Table A.3.5-3: FRC for FR2-1 CQI and RI reporting with CQI table 1 and MCS table 1** + +| Reference channel | | | | M-FR2-A.3.5-1 | M-FR2-A.3.5-2 | +|-------------------------------------------|---------------------|-----------|------------|----------------------------------|---------------| +| Number of allocated PDSCH resource blocks | | | | 66 | 66 | +| Number of consecutive PDSCH symbols | | | | 12 | 12 | +| Number of PDSCH MIMO layers | | | | 1 | 2 | +| Number of DMRS REs (Note 1) | | | | 24 | 24 | +| Overhead for TBS determination | | | | 6 | 6 | +| Available RE-s | | | | 7590 | 7590 | +| CQI index | Spectral efficiency | MCS index | Modulation | Information Bit Payload per Slot | | +| 0 | OOR | OOR | OOR | N/A | N/A | +| 1 | 0.1523 | 0 | QPSK | 1800 | 3624 | +| 2 | 0.2344 | 0 | | 1800 | 3624 | +| 3 | 0.3770 | 2 | | 2856 | 5640 | +| 4 | 0.6016 | 4 | | 4480 | 8968 | +| 5 | 0.8770 | 6 | | 6528 | 13064 | +| 6 | 1.1758 | 8 | | 8712 | 17928 | +| 7 | 1.4766 | 11 | 16QAM | 11016 | 22032 | +| 8 | 1.9141 | 13 | | 14343 | 28680 | +| 9 | 2.4063 | 15 | | 17928 | 35856 | +| 10 | 2.7305 | 18 | 64QAM | 20496 | 40976 | +| 11 | 3.3223 | 20 | | 25104 | 50184 | +| 12 | 3.9023 | 22 | | 29192 | 58384 | +| 13 | 4.5234 | 24 | | 33816 | 67584 | +| 14 | 5.1152 | 26 | | 38936 | 77896 | +| 15 | 5.5547 | 28 | | 42016 | 83976 | + +NOTE 1: Number of DMRS REs includes the overhead of the DM-RS CDM groups without data. + +NOTE 2: PDSCH is only scheduled on slots which are full DL. + +**Table A.3.5-4: Fixed Reference Channels for FR2-1 PMI reporting (16QAM)** + +| Reference channel | M-FR2-A.3.5-3 | +|-----------------------------------------|---------------| +| Channel bandwidth (MHz) | 100 | +| Subcarrier spacing (kHz) | 120 | +| Allocated resource blocks | 66 | +| Number of consecutive PDSCH symbols | 12 | +| MCS table | 64QAM | +| MCS index | 13 | +| Modulation | 16QAM | +| Target Coding Rate | 490/1024 | +| Number of MIMO layers | 1 | +| Number of DMRS REs | 24 | +| Overhead for TBS determination | 6 | +| Information Bit Payload per Slot (bits) | 14344 | +| Transport block CRC per Slot (bits) | 24 | +| Number of Code Blocks per Slot | 2 | +| Binary Channel Bits Per Slot (bits) | 30360 | + +## 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 IAB is to be tested are defined. + +For OTA requirements where it is not possible to environmentally control the entire calibrated OTA chamber either localised control of the IAB hardware or alternative OTA measurements which are then related to the original specification are acceptable, see annex B.7. + +### 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. + +NOTE: This may, for instance, be the case for measurements of radiated emissions performed on an open field test site. + +### 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 60 721-3-3 [19]; +- 2) The equipment class for the equipment under test, as defined in the IEC 60 721-3-4 [20]; +- 3) The equipment that does not comply with the mentioned classes, the relevant classes from IEC 60 721 [21] documentation for temperature, humidity and vibration shall be declared. + +NOTE: Reduced functionality for conditions that fall outside of the standard operational conditions is 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 60 068-2-1 [22]. + +Maximum temperature: + +The test shall be performed with the environmental test equipment and methods including the required environmental phenomena into the equipment, conforming to the test procedure of IEC 60 068-2-2 [23]. + +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 60 068-2-6 [24]. Other environmental conditions shall be within the ranges specified in annex 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 60 068-2-1 [10] Test Ab/Ad and IEC 60 068-2-2 [11] Test Bb/Bd: Dry heat. + +Lower voltage limit: + +The equipment shall be supplied with a voltage equal to the lower limit declared by the manufacturer (as measured at the input terminals to the equipment). The tests shall be carried out at the steady state minimum and maximum temperature limits declared by the manufacturer for the equipment, to the methods described in IEC 60 068-2-1 [10] Test Ab/Ad and IEC 60 068-2-2 [11] Test Bb/Bd: Dry heat. + +--- + +## B.6 Measurement of test environments + +The measurement accuracy of the IAB test environments defined in annex B 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. + +## B.7 OTA extreme test methods + +### B.7.1 Direct far field method + +The IAB under test is placed inside a sealed RF transparent environmental enclosure, as showed in Figure B.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 B.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 system enclosure with a jagged, sawtooth-like inner boundary representing RF transparent walls. Inside, a 'Radome like enclosure' contains the 'IAB' (Integrated Access and Backhaul) unit. A 'Temperature control system' is connected to this enclosure. A 'Test system Calibrated point' is marked on the IAB. A 'Test antenna' is positioned outside the enclosure, connected to 'Measurement equipment'. The 'AAS declared coordinate reference point and orientation' is indicated by a dashed line and angles theta and phi.](17b315c49985d42848e8d673a66dce7f_img.jpg) + +Figure B.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 system enclosure with a jagged, sawtooth-like inner boundary representing RF transparent walls. Inside, a 'Radome like enclosure' contains the 'IAB' (Integrated Access and Backhaul) unit. A 'Temperature control system' is connected to this enclosure. A 'Test system Calibrated point' is marked on the IAB. A 'Test antenna' is positioned outside the enclosure, connected to 'Measurement equipment'. The 'AAS declared coordinate reference point and orientation' is indicated by a dashed line and angles theta and phi. + +**Figure B.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, frequencies and temperatures if necessary. + +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}}$ . + +### B.7.2 Relative method + +The IAB 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 conditions inside the chamber are absorptive and capable of dissipating the power of the IAB 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 'IAB' is surrounded by a 'Small shield anechoic and environmental chamber' represented by a thick border with sawtooth patterns. To the left, a 'Temperature control system' box is connected to the chamber by a thick grey bar. To the right, a 'Test antenna/Probe' is positioned inside the chamber, pointing towards the IAB. An arrow from the probe points to a 'Measurement equipment' box on the far right.](fa0736695e26abf36c4ab5114e8c9c14_img.jpg) + +Diagram of the measurement setup for extreme conditions for EIRP accuracy using the difference method. A central square labeled 'IAB' is surrounded by a 'Small shield anechoic and environmental chamber' represented by a thick border with sawtooth patterns. To the left, a 'Temperature control system' box is connected to the chamber by a thick grey bar. To the right, a 'Test antenna/Probe' is positioned inside the chamber, pointing towards the IAB. An arrow from the probe points to a 'Measurement equipment' box on the far right. + +**Figure B.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 C (informative): Test tolerances and derivation of test requirements + +The test requirements explicitly defined in the present document have been calculated by relaxing the minimum requirements of the core specification TS 38.174 [2] using the test tolerances (TT) defined here. When the TT value is zero, the test requirement will be the same as the minimum requirement. When the TT value 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 $TT_{OTA}$ values are derived from OTA Test System uncertainties, regulatory requirements and criticality to system performance. As a result, the $TT_{OTA}$ values may sometimes be set to zero. + +The $TT_{OTA}$ values should not be modified for any reason e.g. to take account of commonly known OTA Test System errors (such as mismatch, cable loss, etc.). + +Note that a formula for applying $TT_{OTA}$ values is provided for all OTA tests, even those with a test tolerance of zero. This is necessary in the case where the OTA 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 $TT_{OTA}$ value in order to generate the correct tightened test requirements as defined in this annex. + +--- + +## C.1 Measurement of transmitter + +**Table C.1-1: Derivation of test requirements (FR1 OTA transmitter tests)** + +| Test | Minimum requirement in TS 38.174 [2] | Test Tolerance (TT OTA ) | Test requirement in the present document | +|------------------------------------------------------------------------|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------| +| 6.2 Radiated transmit power | See TS 38.174 [2], clause 9.2 | Normal conditions:
1.1 dB, $f \leq 3.0$ GHz
1.3 dB, $3.0$ GHz $< f \leq 4.2$ GHz
1.3 dB, $4.2$ GHz $< f \leq 6.0$ GHz
Extreme conditions:
2.5 dB, $f \leq 3.0$ GHz
2.6 dB, $3.0$ GHz $< f \leq 4.2$ GHz
2.6 dB, $4.2$ GHz $< f \leq 6.0$ GHz | Formula:
Upper limit + TT, Lower limit – TT | +| 6.3 IAB output power | See TS 38.174 [2], clause 9.3 | 1.4 dB, $f \leq 3.0$ GHz
1.5 dB, $3.0$ GHz $< f \leq 4.2$ GHz
1.5 dB, $4.2$ GHz $< f \leq 6.0$ GHz | Formula:
Upper limit + TT, Lower limit – TT | +| [6.4.1.3] IAB-DU OTA output power dynamics | See TS 38.174 [2], clause 9.4.1 | 0.4 dB | Formula:
Total power dynamic range – TT | +| [6.4.2] IAB-MT OTA output power dynamics | See TS 38.174 [2], clause 9.4.2 | $f \leq 3.0$ GHz
$\pm 0.7$ dB, $BW \leq 40$ MHz
$\pm 1.0$ dB, $40$ MHz $< BW \leq 100$ MHz

$3.0$ GHz $< f \leq 4.2$ GHz
$\pm 1.0$ dB, $BW \leq 40$ MHz
$\pm 1.6$ dB, $40$ MHz $< BW \leq 100$ MHz

$4.2$ GHz $< f \leq 6.0$ GHz
$\pm 1.3$ dB, $BW \leq 20$ MHz
$\pm 1.5$ dB, $20$ MHz $< BW \leq 40$ MHz
$\pm 1.6$ dB, $40$ MHz $< BW \leq 100$ MHz | Formula:
Total power dynamic range – TT | +| 6.5.1 OTA transmitter OFF power | See TS 38.174 [2], clause 9.5.2 | 3.4 dB, $f \leq 3.0$ GHz
3.6 dB, $3.0$ GHz $< f \leq 4.2$ GHz
3.6 dB, $4.2$ GHz $< f \leq 6.0$ GHz | Formula:
Minimum Requirement + TT | +| 6.6.2.1 IAB-DU OTA frequency Error | See TS 38.174 [2], clause 9.6.1.1 | 12 Hz | Formula:
Frequency Error limit + TT | +| 6.6.2.2 IAB-MT OTA frequency error | See TS 38.174 [2], clause 9.6.1.2 | $\pm 15$ Hz, $f \leq 3.0$ GHz
$\pm 36$ Hz, $f > 3.0$ GHz | Formula:
Frequency Error limit + TT | +| 6.6.3 OTA Modulation quality (EVM) | See TS 38.174 [2], clause 9.6.2 | 1% | Formula:
EVM limit + TT | +| 6.6.4 OTA time alignment error | See TS 38.174 [2], clause 9.6.3 | 25 ns | | +| 6.7.2 OTA occupied bandwidth | See TS 38.174 [2], clause 9.7.2 | 0 Hz | Formula:
Minimum Requirement + TT | +| 6.7.3 OTA Adjacent Channel Leakage Power Ratio (ACLR) | See TS 38.174 [2], clause 9.7.3 | Relative:
1.0 dB, $f \leq 3.0$ GHz
1.2 dB, $3.0$ GHz $< f \leq 4.2$ GHz
1.2 dB, $4.2$ GHz $< f \leq 6.0$ GHz

Absolute:
0 dB | Formula:
Relative limit - TT
Absolute limit + TT | +| 6.7.4 OTA operating band unwanted emissions | See TS 38.174 [2], clause 9.7.4 | Offsets $< 10$ MHz
1.8 dB, $f \leq 3.0$ GHz
2 dB, $3.0$ GHz $< f \leq 4.2$ GHz
2 dB, $4.2$ GHz $< f \leq 6.0$ GHz

Offsets $\geq 10$ MHz
0 dB | Formula:
Minimum Requirement + TT | +| 6.7.5.2 General transmitter spurious emissions requirements Category A | See TS 38.174 [2], clause 9.7.5.2.2 | 0 dB | Formula:
Minimum Requirement + TT | + +| Test | Minimum requirement in TS 38.174 [2] | Test Tolerance (TT OTA ) | Test requirement in the present document | +|------------------------------------------------------------------------|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| 6.7.5.2 General transmitter spurious emissions requirements Category B | See TS 38.174 [2], clause 9.7.5.2.2 | 0 dB | Formula:
Minimum Requirement + TT | +| 6.7.5.3 Additional spurious emissions requirements | See TS 38.174 [2], clause 9.7.5.2.3 | 2.6 dB, $f \leq 3$ GHz
3.0 dB, $3$ GHz $< f \leq 4.2$ GHz
3.5 dB, $4.2$ GHz $< f \leq 6$ GHz

For co-existence with PHS
0 dB | Formula:
Minimum Requirement + TT | +| 6.7.5.4 Co-location with other base stations | See TS 38.174 [2], clause 9.7.5.2.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 | Formula:
Minimum Requirement + TT | +| 6.8 OTA transmitter intermodulation | See TS 38.174 [2], clause 9.8 | 0 dB | | + +NOTE: TT values are applicable for normal condition unless otherwise stated. + +**Table C.1-2: Derivation of test requirements (FR2-1 OTA transmitter tests)** + +| Test | Minimum requirement in TS 38.174 [2] | Test Tolerance (TT OTA ) | | Test requirement in the present document | +|-------------------------------------------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| +| | | IAB-DU | IAB-MT | | +| 6.2 Radiated transmit power | See TS 38.174 [2], clause 9.2 | Normal conditions:
1.7 dB, 24.25GHz < f ≤ 29.5GHz
2.0 dB, 37GHz < f ≤ 43.5GHz
Extreme conditions:
3.1 dB, 24.25GHz < f ≤ 29.5GHz
3.3 dB, 37GHz < f ≤ 43.5GHz | Normal condition:
±2.6 dB (24.25 – 29.5 GHz)
±2.6 dB (37 – 43.5 GHz)

Extreme condition:
±3.7 dB (24.25 – 29.5 GHz)
±3.7 dB (37 – 43.5 GHz) | Formula:
Upper limit + TT,
Lower limit – TT | +| 6.3 IAB output power | See TS 38.174 [2], clause 9.3 | 2.1 dB, 24.25GHz < f ≤ 29.5GHz
2.4 dB, 37GHz < f ≤ 43.5GHz | ±2.8 dB (24.25 – 29.5 GHz)
±2.9 dB (37 – 43.5 GHz) | Formula:
Upper limit + TT,
Lower limit – TT | +| 6.4.1.3 IAB-DU OTA output power dynamics | See TS 38.174 [2], clause 9.4.1.3 | 0.4 dB | N/A | Formula:
Total power dynamic range – TT | +| 6.4.2 IAB-MT OTA output power dynamics | See TS 38.174 [2], clause 9.4.2 | N/A | ±0.7 dB, BW ≤ 40MHz
±1.0 dB, 40MHz < f ≤ 100MHz | Formula:
Total power dynamic range – TT | +| 6.5.1 OTA transmitter OFF power | See TS 38.174 [2], clause 9.5.2 | 2.9 dB, 24.25GHz < f ≤ 29.5GHz
3.3 dB, 37GHz < f ≤ 43.5GHz | | Formula:
Minimum Requirement + TT | +| 6.6.2 OTA frequency Error | See TS 38.174 [2], clause 9.6.1 | 12 Hz | [± 0.01 ppm] | Formula:
Frequency Error limit + TT | +| 6.6.3 OTA Modulation quality (EVM) | See TS 38.174 [2], clause 9.6.2 | 1 % | | Formula:
EVM limit + TT | +| 6.6.4 OTA time alignment error | See TS 38.174 [2], clause 9.6.3 | 25 ns | N/A | | +| 6.7.2 OTA occupied bandwidth | See TS 38.174 [2], clause 9.7.2 | 0 Hz | | Formula:
Minimum Requirement + TT | +| 6.7.3 OTA Adjacent Channel Leakage Power Ratio (ACLR) | See TS 38.174 [2], clause 9.7.3 | Relative:
2.3 dB, 24.25GHz < f ≤ 29.5GHz
2.6 dB, 37GHz < f ≤ 43.5GHz
Absolute:
2.7 dB, 24.25GHz < f ≤ 29.5GHz
2.7 dB, 37GHz < f ≤ 43.5GHz | Relative ACLR:
±2.8 dB (24.25 – 29.5 GHz)
±2.9 dB (37 – 43.5 GHz)

Absolute ACLR:
±2.9 dB (24.25 – 29.5 GHz)
±3.0 dB (37 – 43.5 GHz) | Formula:
Relative limit - TT
Absolute limit +TT | + +| Test | Minimum requirement in TS 38.174 [2] | Test Tolerance (TT OTA ) | | Test requirement in the present document | +|------------------------------------------------------------------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| | | IAB-DU | IAB-MT | | +| 6.7.4 OTA operating band unwanted emissions | See TS 38.174 [2], clause 9.7.4 | $0 \text{ MHz} \le \Delta f < 0.1 \cdot \text{BWcontiguous}$
$2.7 \text{ dB}, 24.25 \text{ GHz} < f \le 29.5 \text{ GHz}$
$2.7 \text{ dB}, 37 \text{ GHz} < f \le 43.5 \text{ GHz}$
$0.1 \cdot \text{BWcontiguous} \le \Delta f < \Delta f_{\max}$
$0 \text{ dB}$

For co-existence with Earth Exploration Satellite Service 0 dB | $0 \text{ MHz} \le \Delta f < 0.1 \cdot \text{BWcontiguous}$
$\pm 2.9 \text{ dB} (24.25 - 29.5 \text{ GHz})$
$\pm 3.0 \text{ dB} (37 - 43.5 \text{ GHz})$
$0.1 \cdot \text{BWcontiguous} \le \Delta f < \Delta f_{\max}$
$0 \text{ dB}$

For co-existence with Earth Exploration Satellite Service 0 dB | Formula:
Minimum Requirement + TT | +| 6.7.5.2 General transmitter spurious emissions requirements Category A | See TS 38.174 [2], clause 9.7.5.2.2 | 0 dB | | Formula:
Minimum Requirement + TT | +| 6.7.5.2 General transmitter spurious emissions requirements Category B | See TS 38.174 [2], clause 9.7.5.2.2 | 0 dB | | Formula:
Minimum Requirement + TT | +| 6.7.5.4 OTA transmitter spurious emissions, additional requirements | See TS 38.174 [2], clause 9.7.5.3.3 | For co-existence with Earth Exploration Satellite Service 0 dB | | Formula:
Minimum Requirement + TT | +| NOTE: TT values are applicable for normal condition unless otherwise stated. | | | | | + +## C.2 Measurement of receiver + +Table C.2-1: Derivation of test requirements (FR1 OTA receiver tests) + +| Test | Minimum requirement in TS 38.174 [2] | Test Tolerance (TT OTA ) | Test requirement in the present document | +|------------------------------------------------------------------------------|--------------------------------------|----------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| 7.2 OTA sensitivity | See TS 38.174 [2], clause 10.2 | 1.3 dB, $f \leq 3.0$ GHz
1.4 dB, $3.0$ GHz $< f \leq 4.2$ GHz
1.6 dB, $4.2$ GHz $< f \leq 6.0$ GHz | Formula:
Declared Minimum EIS + TT | +| 7.3 OTA reference sensitivity level | See TS 38.174 [2], clause 10.3 | 1.3 dB, $f \leq 3.0$ GHz
1.4 dB, $3.0$ GHz $< f \leq 4.2$ GHz
1.6 dB, $4.2$ GHz $< f \leq 6.0$ GHz | Formula:
$EIS_{REFSENS} + TT$ | +| 7.4 OTA dynamic range | See TS 38.174 [2], clause 10.4 | 0.3 dB, $f \leq 6$ GHz | Formula:
Wanted signal power + TT

Interferer signal power unchanged. | +| 7.5.1 OTA adjacent channel selectivity | See TS 38.174 [2], clause 10.5.1 | 0 dB | Formula:
Wanted signal power + TT

Interferer signal power unchanged. | +| 7.5.2 In-band blocking (General) | See TS 38.174 [2], clause 10.5.2 | 0 dB | Formula:
Wanted signal power + TT

Interferer signal power unchanged. | +| 7.5.2 In-band blocking (Narrowband) | See TS 38.174 [2], clause 10.5.2 | 0 dB | Formula:
Wanted signal power + TT

Interferer signal power unchanged. | +| 7.6 OTA out-of-band blocking (General) | See TS 38.174 [2], clause 10.6 | 0 dB | Formula:
Wanted signal power + TT

Interferer signal power unchanged. | +| 7.6 OTA out-of-band blocking (Co-location) | See TS 38.174 [2], clause 10.6 | 0 dB | Formula:
Wanted signal power unchanged

Interferer signal power - TT. | +| 7.7 OTA receiver spurious emissions | See TS 38.174 [2], clause 10.7 | 0 dB | Formula:
Minimum Requirement + TT | +| 7.8 OTA receiver intermodulation | See TS 38.174 [2], clause 10.8 | 0 dB | Formula:
Wanted signal power + TT

Interferer signal power unchanged | +| 7.9 OTA in-channel selectivity | See TS 38.174 [2], clause 10.9 | 1.7 dB, $f \leq 3.0$ GHz
2.1 dB, $3.0$ GHz $< f \leq 4.2$ GHz
2.4 dB, $4.2$ GHz $< f \leq 6.0$ GHz | Formula:
Wanted signal power + TT

Interferer signal power unchanged | +| NOTE: TT values are applicable for normal condition unless otherwise stated. | | | | + +**Table C.2-2: Derivation of test requirements (FR2-1 OTA receiver tests)** + +| Test | Minimum requirement in TS 38.174 [2] | Test Tolerance (TT OTA ) | | Test requirement in the present document | +|----------------------------------------|--------------------------------------|-------------------------------------------------------------------|---------------------------------------------------------------------|--------------------------------------------------------------------------------| +| | | IAB-DU | IAB-MT | | +| 7.3 OTA reference sensitivity level | See TS 38.174 [2], clause 10.3 | 2.4 dB, 24.25 GHz < f ≤ 33.4 GHz
2.4 dB, 37 GHz < f ≤ 43.5 GHz | ±3.3 dB, 24.25 GHz < f ≤ 29.5 GHz
±3.3 dB, 37 GHz < f ≤ 43.5 GHz | Formula:
EISREFSENS+ TT | +| 7.5.1 OTA adjacent channel selectivity | See TS 38.174 [2], clause 10.5.1 | 0 dB | 0 dB | Formula:
Wanted signal power + TT

Interferer signal power unchanged. | +| 7.5.2 In-band blocking | See TS 38.174 [2], clause 10.5.2 | 0 dB | 0 dB | Formula:
Wanted signal power + TT

Interferer signal power unchanged. | +| 7.6 OTA out-of-band blocking | See TS 38.174 [2], clause 10.6 | 0 dB | 0 dB | Formula:
Wanted signal power + TT
Interferer signal power unchanged | +| 7.7 OTA receiver spurious emissions | See TS 38.174 [2], clause 10.7 | 0 dB | 0 dB | Formula:
Minimum Requirement + TT | +| 7.8 OTA receiver intermodulation | See TS 38.174 [2], clause 10.8 | 0 dB | N/A | Formula:
Wanted signal power + TT

Interferer signal power unchanged. | +| 7.9 OTA in-channel selectivity | See TS 38.174 [2], clause 10.9 | 3.4 dB, 24.25 GHz < f ≤ 33.4 GHz
3.4 dB, 37 GHz < f ≤ 43.5 GHz | N/A | Formula:
Wanted signal power + TT

Interferer signal power unchanged. | + +NOTE: TT values are applicable for normal condition unless otherwise stated. + +## C.3 Measurement of performance requirements + +### C.3.1 IAB-DU Test Tolerances + +Table C.3.1-1: Derivation of test requirements (FR1 and FR2-1 performance tests) + +| Test | Minimum Requirement in TS 38.174 [2] | Test Tolerance (TT OTA ) | Test requirement in the present document | +|----------------------------------------------------------------------|--------------------------------------|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------| +| Performance requirements for PUSCH with transform precoding disabled | SNRs as specified | 0.6 dB | Formula: SNR + TT OTA
T-put limit unchanged | +| Performance requirements for PUSCH with transform precoding enabled | SNRs as specified | 0.6 dB | Formula: SNR + TT OTA
T-put limit unchanged | +| Performance requirements for UCI multiplexed on PUSCH | SNRs as specified | 0.6 dB | Formula: SNR + TT OTA
BLER limit unchanged | +| Performance requirements for PUCCH format 0 | SNRs as specified | 0.6 dB | Formula: SNR + TT OTA
False ACK limit unchanged
Correct ACK limit unchanged | +| Performance requirements for PUCCH format 1 | SNRs as specified | 0.6 dB | Formula: SNR + TT OTA
False ACK limit unchanged
False NACK limit unchanged
Correct ACK limit unchanged | +| Performance requirements for PUCCH format 2 | SNRs as specified | 0.6 dB | Formula: SNR + TT OTA
False ACK limit unchanged
Correct ACK limit unchanged
UCI BLER limit unchanged | +| Performance requirements for PUCCH format 3 | SNRs as specified | 0.6 dB | Formula: SNR + TT OTA
UCI BLER limit unchanged | +| Performance requirements for PUCCH format 4 | SNRs as specified | 0.6 dB | Formula: SNR + TT OTA
UCI BLER limit unchanged | +| Performance requirements for multi-slot PUCCH | SNRs as specified | 0.6 dB | Formula: SNR + TT OTA
False ACK limit unchanged
False NACK limit unchanged
Correct ACK limit unchanged | +| PRACH false alarm probability and missed detection | SNRs as specified | 0.3 dB | Formula: SNR + TT OTA
PRACH False detection limit unchanged
PRACH detection limit unchanged | + +NOTE: TT values are applicable for normal condition unless otherwise stated. + +## C.3.2 IAB-MT Test Tolerances + +### C.3.2.1 Demodulation Performance + +**Table C.3.2.1-1: Derivation of Test Requirements (FR1 demodulation performance tests)** + +| Test | Minimum Requirement in TS 38.174 [2] | Test Tolerance (TT) | Test requirement in the present document | +|------------------------------------------------------------------|--------------------------------------|-------------------------------------------------------|--------------------------------------------| +| Performance requirements for PDSCH | SNRs as specified | 0.9 dB for > 10 Hz doppler
1.0 dB for 10Hz doppler | Formula: SNR + TT
T-put limit unchanged | +| Performance requirements for PDCCH with 1 Tx antenna performance | SNRs as specified | 1.0 dB | Formula: SNR + TT
T-put limit unchanged | +| Performance requirements for PDCCH with 2 Tx antenna performance | SNRs as specified | 0.9 dB | Formula: SNR + TT
T-put limit unchanged | + +**Table C.3.2.1-2: Derivation of Test Requirements (FR2-1 demodulation performance tests)** + +| Test | Minimum Requirement in TS 38.174 [2] | Test Tolerance (TT) | Test requirement in the present document | +|------------------------------------------------------|--------------------------------------|----------------------------------------------------------------------------------------------|--------------------------------------------| +| Performance requirements for PDSCH | SNRs as specified | 2Tx, Rank 1:
1.8 dB

2Tx, Rank 2:
1.7 dB for doppler < 100Hz
1.6 dB otherwise | Formula: SNR + TT
T-put limit unchanged | +| Performance requirements for PDCCH with 1 Tx antenna | SNRs as specified | 1Tx, rank1:
1.7 dB | Formula: SNR + TT
T-put limit unchanged | +| Performance requirements for PDCCH with 2 Tx antenna | SNRs as specified | 2Tx, rank1:
1.8 dB | Formula: SNR + TT
T-put limit unchanged | + +### C.3.2.2 Channel State Information Reporting + +**Table C.3.2.2-1: Derivation of Test Requirements (FR1 and FR2-1 CSI reporting tests)** + +| Test | Minimum Requirement in TS 38.174 [2] | Test Tolerance (TT) | Test requirement in the present document | +|---------------|------------------------------------------------------------|----------------------------------------------------|-----------------------------------------------------| +| CQI reporting | SNRs as specified
Limits as in the Test Procedure | SNR 0 dB
$\gamma' - 0.01$ | SNR unchanged | +| PMI reporting | SNRs as specified
$\gamma'$ as specified | SNR 0 dB
$\gamma_1 - 0.01$
$\gamma_2 - 0.01$ | SNR unchanged
$\gamma' - TT$ | +| RI reporting | SNRs as specified
$\gamma_1$ or $\gamma_2$ as specified | SNR 0 dB
$\gamma' - 0.01$ | SNR unchanged
$\gamma_1 - TT$ or $\gamma_2 - TT$ | + +--- + +## Annex D (normative): Calibration + +### D.1 General + +OTA test requirements specific and OTA measurement chamber specific calibration (and measurement) procedures were captured in TR 37.941 [25] for the following requirements sets: + +- TX and Rx directional requirements +- In-band and out-of-band TRP requirements +- Co-location requirements +- In-band and out-of-band blocking requirements + +All the calibrations procedures in TR 37.941 [25] for the BS are assumed to be also applicable to *IAB type 1-H* and *IAB type 1-O* for the FR1 frequency range (i.e. up to 6 GHz), as well as for *IAB type 2-O* for the FR2-1 frequency range, unless stated otherwise. + +## Annex E (informative): OTA measurement system set-up + +### E.1 Transmitter + +#### E.1.1 Radiated transmit power, OTA output power dynamics, OTA transmitted signal quality, OTA occupied bandwidth, and OTA transmit ON/OFF power (*IAB type 2-O*) + +![Diagram of the measurement set-up for radiated transmit power, OTA output power dynamics, OTA transmitted signal quality, OTA occupied bandwidth, and OTA transmit ON/OFF power (IAB type 2-O).](d7dd49b6b46d5db93258cc8769da942b_img.jpg) + +The diagram illustrates the measurement setup within a test system enclosure lined with sawtooth-shaped electromagnetic wave absorbers. Inside, an IAB (Integrated Access and Backhaul) unit is positioned on the left. A 'Test system Calibrated point' is marked by a vertical dashed line. A 'declared coordinate reference point and orientation' is indicated by a dot at the center of the IAB, with a vertical dashed line passing through it. Two angles, $\theta$ and $\varphi$ , are shown originating from this reference point. On the right side of the enclosure, a 'Test antenna' is mounted, connected to 'Measurement equipment' outside the enclosure. The entire structure is labeled 'Test system enclosure' at the bottom. + +Diagram of the measurement set-up for radiated transmit power, OTA output power dynamics, OTA transmitted signal quality, OTA occupied bandwidth, and OTA transmit ON/OFF power (IAB type 2-O). + +**Figure E.1.1-1: Measurement set up for radiated transmit power, OTA output power dynamics, OTA transmitted signal quality, OTA occupied bandwidth, and OTA transmit ON/OFF power (*IAB type 2-O*)** + +The OTA chamber shown in figure E.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.) + +## E.1.2 OTA IAB output power, OTA ACLR, OTA operating band unwanted emissions + +![Diagram of measurement setup for OTA IAB output power, OTA ACLR, and OTA operating band unwanted emissions. It shows an IAB device on a positioner inside a test system enclosure with a calibrated point and coordinate reference. A test antenna is connected to a measurement receiver outside the enclosure.](e0304e6389e07d2620a7aac6efa6c940_img.jpg) + +The diagram illustrates the measurement setup for OTA IAB output power, OTA ACLR, and OTA operating band unwanted emissions. It features a rectangular 'Test system enclosure' with jagged edges representing RF shielding. Inside, an 'IAB' (Integrated Access and Backhaul) device is mounted on a 'Positioner'. A 'Test system Calibrated point' is marked on the IAB, and a 'declared coordinate reference point and orientation' is indicated by a dashed line. The IAB is shown with a circular arrow indicating rotation, and a coordinate system with $\theta$ and $\phi$ angles. Outside the enclosure, a 'Test antenna' is positioned to receive signals from the IAB, and it is connected to a 'Measurement receiver'. + +Diagram of measurement setup for OTA IAB output power, OTA ACLR, and OTA operating band unwanted emissions. It shows an IAB device on a positioner inside a test system enclosure with a calibrated point and coordinate reference. A test antenna is connected to a measurement receiver outside the enclosure. + +**Figure E.1.2-1: Measurement set up for OTA IAB output power, OTA ACLR, OTA operating band unwanted emissions** + +The OTA chamber shown in figure E.1.2-1 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, Near field chamber, etc.) + +## E.1.3 OTA spurious emissions + +![Diagram of measurement setup for OTA spurious emissions. It shows an IAB device on a positioner inside a test system enclosure with a calibrated point and coordinate reference. A test antenna is connected to a measurement receiver outside the enclosure.](b427b2e83302ee2f122a80fcb0fbb5d8_img.jpg) + +The diagram illustrates the measurement setup for OTA spurious emissions. It is identical to the setup shown in Figure E.1.2-1, featuring a 'Test system enclosure' with an 'IAB' device on a 'Positioner'. The 'Test system Calibrated point' and 'declared coordinate reference point and orientation' are also present. The 'Test antenna' is connected to a 'Measurement receiver' outside the enclosure to measure spurious emissions from the IAB. + +Diagram of measurement setup for OTA spurious emissions. It shows an IAB device on a positioner inside a test system enclosure with a calibrated point and coordinate reference. A test antenna is connected to a measurement receiver outside the enclosure. + +**Figure E.1.3-1: Measurement set up for OTA spurious emissions** + +The OTA chamber shown in figure E.1.3-1 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, etc.). + +### E.1.4 OTA co-location emissions, OTA transmit ON/OFF power (IAB type 1-O) + +![Diagram of the measurement setup for OTA co-location emissions, OTA transmit ON/OFF power (IAB type 1-O).](b1ec498620251169dcfc839e18443154_img.jpg) + +The diagram illustrates the measurement setup for OTA co-location emissions, OTA transmit ON/OFF power (IAB type 1-O). It features a 'Test system enclosure' with a sawtooth pattern on its walls. Inside, an 'IAB' (Integrated Access and Backhaul) unit is mounted on a 'Positioner' that allows for rotation. A 'Test system Calibrated point' is marked on the IAB, and a 'declared coordinate reference point and orientation' is indicated. A 'Co-Location Test Antenna' is positioned near the IAB. A 'Test antenna' is located outside the enclosure, connected to a 'Measurement receiver'. A red line connects the IAB to a 'Switch, limiter or filter', which is then connected to a 'Measurement Device'. + +Diagram of the measurement setup for OTA co-location emissions, OTA transmit ON/OFF power (IAB type 1-O). + +**Figure E.1.4-1: Measurement set up for OTA co-location emissions, OTA transmit ON/OFF power (IAB type 1-O)** + +The OTA chamber shown in figure E.1.4-1 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, Near field chamber, etc.) + +## E.1.5 OTA transmitter intermodulation + +![Figure E.1.5-1: Measurement set up for OTA transmitter intermodulation. The diagram shows a test system enclosure with a jagged border. Inside, an IAB (Integrated Access and Backhaul) device is mounted on a positioner. A 'Test system Calibrated point' is marked on the IAB. A 'declared coordinate reference point and orientation' is indicated by a dashed line. A 'Co-Location Test Antenna' is positioned near the IAB. A 'Test antenna' is located on the right side of the enclosure, connected to a 'Measurement receiver'. A 'Signal Generator for the interfering signal' is connected to the Co-Location Test Antenna via a red line. The IAB is shown with a circular arrow indicating rotation, and angles θ and φ are marked.](5ff967638ed80b570723c608aa77fa39_img.jpg) + +Figure E.1.5-1: Measurement set up for OTA transmitter intermodulation. The diagram shows a test system enclosure with a jagged border. Inside, an IAB (Integrated Access and Backhaul) device is mounted on a positioner. A 'Test system Calibrated point' is marked on the IAB. A 'declared coordinate reference point and orientation' is indicated by a dashed line. A 'Co-Location Test Antenna' is positioned near the IAB. A 'Test antenna' is located on the right side of the enclosure, connected to a 'Measurement receiver'. A 'Signal Generator for the interfering signal' is connected to the Co-Location Test Antenna via a red line. The IAB is shown with a circular arrow indicating rotation, and angles θ and φ are marked. + +Figure E.1.5-1: Measurement set up for OTA transmitter intermodulation + +The OTA chamber shown in figure E.1.5-1 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, etc.). When injecting the interferer signal into the CLTA ports, a splitter might be needed. For testing emission far out-of-band an additional test antenna might be needed. + +## E.2 Receiver + +### E.2.1 OTA sensitivity and OTA reference sensitivity level + +![Figure E.2.1-1: Measurement set up for OTA sensitivity and OTA reference sensitivity level. The diagram shows a test system enclosure with a jagged border. Inside, an IAB device is mounted. A 'Test system Calibrated point' is marked on the IAB. A 'declared coordinate reference point and orientation' is indicated by a dashed line. A 'Test antenna' is positioned on the left side of the enclosure, connected to a 'Signal generator for the wanted signal'. The IAB is shown with a circular arrow indicating rotation, and angles θ and φ are marked. A label 'Test antenna polarisation can be adjusted' points to the test antenna.](d532466167e07c3d3dbbe3ffc0a84b3f_img.jpg) + +Figure E.2.1-1: Measurement set up for OTA sensitivity and OTA reference sensitivity level. The diagram shows a test system enclosure with a jagged border. Inside, an IAB device is mounted. A 'Test system Calibrated point' is marked on the IAB. A 'declared coordinate reference point and orientation' is indicated by a dashed line. A 'Test antenna' is positioned on the left side of the enclosure, connected to a 'Signal generator for the wanted signal'. The IAB is shown with a circular arrow indicating rotation, and angles θ and φ are marked. A label 'Test antenna polarisation can be adjusted' points to the test antenna. + +Figure E.2.1-1: Measurement set up for OTA sensitivity and OTA reference sensitivity level + +The OTA chamber shown in figure E.2.1-1 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, etc.). + +## E.2.2 OTA dynamic range + +![Figure E.2.2-1: Measurement set up for OTA dynamic range. The diagram shows a signal generator for the wanted signal connected to ATT1, and a signal generator for the AWGN interfering signal connected to ATT2. Both ATT1 and ATT2 are connected to a Hybrid. The Hybrid is connected to a Test antenna inside a Test system enclosure. The Test antenna's polarization can be adjusted. The Test system enclosure contains a Test system Calibrated point and an IAB (Integrated Access and Backhaul) unit. The IAB is shown with a coordinate system (theta, phi) and a declared coordinate reference point and orientation.](e0eba715b26e99c0beececdd6112ee58_img.jpg) + +Figure E.2.2-1: Measurement set up for OTA dynamic range. The diagram shows a signal generator for the wanted signal connected to ATT1, and a signal generator for the AWGN interfering signal connected to ATT2. Both ATT1 and ATT2 are connected to a Hybrid. The Hybrid is connected to a Test antenna inside a Test system enclosure. The Test antenna's polarization can be adjusted. The Test system enclosure contains a Test system Calibrated point and an IAB (Integrated Access and Backhaul) unit. The IAB is shown with a coordinate system (theta, phi) and a declared coordinate reference point and orientation. + +**Figure E.2.2-1: Measurement set up for OTA dynamic range** + +The OTA chamber shown in figure E.2.2-1 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, etc.). + +## E.2.3 OTA adjacent channel selectivity, general OTA blocking, and OTA narrowband blocking + +![Figure E.2.3-1: Measurement set up for OTA ACS and OTA narrowband blocking. The diagram shows a signal generator for the wanted signal connected to ATT1, and a signal generator for the interfering signal connected to ATT2. Both ATT1 and ATT2 are connected to a Hybrid. The Hybrid is connected to a Test antenna inside a Test system enclosure. The Test antenna's polarization can be adjusted. The Test system enclosure contains a Test system Calibrated point and an IAB (Integrated Access and Backhaul) unit. The IAB is shown with a coordinate system (theta, phi) and a declared coordinate reference point and orientation.](294cfcd2dffc2040d25dd92a01ec70c3_img.jpg) + +Figure E.2.3-1: Measurement set up for OTA ACS and OTA narrowband blocking. The diagram shows a signal generator for the wanted signal connected to ATT1, and a signal generator for the interfering signal connected to ATT2. Both ATT1 and ATT2 are connected to a Hybrid. The Hybrid is connected to a Test antenna inside a Test system enclosure. The Test antenna's polarization can be adjusted. The Test system enclosure contains a Test system Calibrated point and an IAB (Integrated Access and Backhaul) unit. The IAB is shown with a coordinate system (theta, phi) and a declared coordinate reference point and orientation. + +**Figure E.2.3-1: Measurement set up for OTA ACS and OTA narrowband blocking** + +The OTA chamber shown in figure E.2.3-1 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, etc.). + +![Measurement setup for general OTA blocking diagram](6d05c026b02a4762fcd1dcb5171327ac_img.jpg) + +This diagram illustrates the measurement setup for general OTA blocking. On the left, two signal generators are shown: one for the wanted signal and another for the interfering signal. The wanted signal path includes an attenuator (ATT1) and a hybrid combiner. The interfering signal path includes an attenuator (ATT2) and the same hybrid combiner. The output of the hybrid is connected to a circulator, with its third port connected to a termination. The circulator's output port is positioned inside a test system enclosure, facing a test antenna. A label indicates that the test antenna's polarization can be adjusted. Inside the enclosure, a 'declared coordinate reference point and orientation' is marked. To the right, an inset shows the 'Test system Calibrated point' relative to the 'IAB' (Integrated Access and Backhaul) unit, with angles $\theta$ and $\varphi$ defined from a vertical dashed line. + +Measurement setup for general OTA blocking diagram + +**Figure E.2.3-2: Measurement set up for general OTA blocking** + +The OTA chamber shown in figure E.2.3-2 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, etc.). + +## E.2.4 OTA blocking + +### E.2.4.1 General OTA out-of-band blocking + +![Measurement setup for general OTA out-of-band blocking diagram](6fd4c6c23098ef713797b9e98ec299e8_img.jpg) + +This diagram illustrates the measurement setup for general OTA out-of-band blocking. Two signal generators are shown on the left: one for the wanted signal and another for the interfering signal. Both signals are directed into the test system enclosure. Inside the enclosure, the wanted signal is received by a 'Test antenna (in band)' and the interfering signal by a 'Test antenna (out of band)'. A label indicates that the test antenna polarization can be adjusted. A 'declared coordinate reference point and orientation' is marked inside the enclosure. An inset on the right shows the 'Test system Calibrated point' relative to the 'IAB' unit, with angles $\theta$ and $\varphi$ defined from a vertical dashed line. + +Measurement setup for general OTA out-of-band blocking diagram + +**Figure E.2.4.1-1: Measurement set up for general OTA out-of-band blocking** + +The OTA chamber shown in figure E.2.4.1-1 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, etc.). + +### E.2.4.2 OTA co-location blocking + +![Measurement set up for OTA co-location blocking diagram](f5d21653d7ae301d33b64eda6dfb40b8_img.jpg) + +This diagram illustrates the measurement setup for OTA co-location blocking. It features a rectangular test system enclosure with jagged edges representing anechoic chamber walls. Inside, a 'Test antenna (in band)' is positioned on the left, with a note that its 'Test antenna polarisation can be adjusted'. This antenna is connected to a 'Signal Generator for the wanted signal'. On the right, a 'Co-Location Test Antenna' is mounted on a circular 'IAB' (In-Antenna Block) which can rotate, as indicated by a curved arrow. This antenna is connected to a 'Signal Generator for the interfering signal' via a triangular amplifier. A vertical dashed line marks the 'Test system Calibrated point'. A 'declared coordinate reference point and orientation' is indicated by a small square with axes at the center of the IAB. The angles $\theta$ and $\phi$ are shown relative to this reference point. The entire setup is labeled 'Test system enclosure' at the bottom right. + +Measurement set up for OTA co-location blocking diagram + +Figure E.2.4.2-1: Measurement set up for OTA co-location blocking + +The OTA chamber shown in figure E.2.4.2-1 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, etc.). For testing blocking far out-of-band several CLTAs might be needed. + +### E.2.5 OTA receiver spurious emissions + +![Measurement set up for OTA receiver spurious emissions diagram](9ad891694657f787cf68e07db7060576_img.jpg) + +This diagram shows the measurement setup for OTA receiver spurious emissions. A rectangular 'Test system enclosure' contains a circular 'IAB' (In-Antenna Block) mounted on a 'Positioner', which allows for rotation as shown by a curved arrow. The 'IAB' has a 'declared coordinate reference point and orientation' marked by a small square with axes. The angles $\theta$ and $\phi$ are defined relative to this point. A 'Test system Calibrated point' is marked by a vertical dashed line. To the right of the IAB, a 'Test antenna' is positioned, which is connected to a 'Measurement receiver'. + +Measurement set up for OTA receiver spurious emissions diagram + +Figure E.2.5-1: Measurement set up for OTA receiver spurious emissions + +The OTA chamber shown in figure E.2.5-1 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, etc.). + +## E.2.6 OTA receiver intermodulation + +![Measurement set up for OTA receiver intermodulation diagram](6b29eb8374b62e0ef0bfcaa6764de39e_img.jpg) + +This 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'. The first two are connected to attenuators labeled 'ATT1' and 'ATT2' respectively, which then feed into a 'Hybrid' combiner. The third signal generator is connected to an attenuator labeled 'ATT3', which feeds into another 'Hybrid' combiner. This second hybrid's output is connected to the first hybrid. The output of the first hybrid is connected to a 'Test antenna' inside a 'Test system enclosure'. An arrow points to the test antenna with the text 'Test antenna polarisation can be adjusted'. Inside the enclosure, the test antenna is positioned relative to a 'declared coordinate reference point and orientation'. To the right, an 'IAB' (Integrated Access and Backhaul) unit is shown at a 'Test system Calibrated point'. A coordinate system is defined with the origin at the calibrated point, with the vertical axis labeled $\theta$ and the horizontal axis labeled $\varphi$ . + +Measurement set up for OTA receiver intermodulation diagram + +**Figure E.2.6-1: Measurement set up for OTA receiver intermodulation** + +The OTA chamber shown in figure E.2.6-1 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, etc.). + +## E.2.7 OTA in-channel selectivity + +![Measurement set up for OTA in-channel selectivity diagram](d7fd3bb81478f33c406af557efa5f4fb_img.jpg) + +This diagram illustrates the measurement setup for OTA in-channel selectivity. On the left, a single signal generator is shown, labeled 'Signal Generator for the wanted signal and the interfering signal', which is connected to a 'Hybrid' combiner. The output of the hybrid is connected to a 'Test antenna' inside a 'Test system enclosure'. An arrow points to the test antenna with the text 'Test antenna polarisation can be adjusted'. Inside the enclosure, the test antenna is positioned relative to a 'declared coordinate reference point and orientation'. To the right, an 'IAB' (Integrated Access and Backhaul) unit is shown at a 'Test system Calibrated point'. A coordinate system is defined with the origin at the calibrated point, with the vertical axis labeled $\theta$ and the horizontal axis labeled $\varphi$ . + +Measurement set up for OTA in-channel selectivity diagram + +**Figure E.2.7-1: Measurement set up for OTA in-channel selectivity** + +The OTA chamber shown in figure E.2.7-1 is intended to be generic and can be replaced with any suitable OTA chamber (Far field anechoic chamber, CATR, etc.). + +## E.3 Measurement set-up IAB-MT and IAB-DU performance requirements + +### E.3.1 PUSCH and PUCCH single antenna port in multipath fading + +![Functional set-up for PUSCH and PUCCH single antenna port performance requirements in multipath fading. The diagram shows a Tester connected to a Channel Simulator, which is also connected to an AWGN Generator. The output of the Channel Simulator is combined with the AWGN Generator output and sent to a Device under test inside an OTA chamber. A feedback loop connects the Device under test back to the Tester. A Time/frequency synchronization source (if used, see NOTE 2) is connected to both the Tester and the Device under test.](9ecaf3842a06bb8defd6bea7de551283_img.jpg) + +The diagram illustrates the functional set-up for PUSCH and PUCCH single antenna port performance requirements in multipath fading. It consists of the following components and connections: + +- Tester**: The main control unit, connected to the Channel Simulator and receiving feedback from the Device under test. +- Channel Simulator**: Provides the multipath fading channel model, connected to the Tester and the combiner. +- AWGN Generator**: Generates Additive White Gaussian Noise, connected to the combiner. +- Combiner**: Combines the output of the Channel Simulator and the AWGN Generator. +- OTA Chamber**: A large box containing the **Device under test**. The combined signal is transmitted into the chamber via an antenna. +- Device under test**: The unit being tested, shown with a coordinate system (θ, φ, 0) indicating its orientation. +- Feedback**: A signal path from the Device under test back to the Tester. +- Time/frequency synchronization source (if used, see NOTE 2)**: A dashed box providing synchronization signals to both the Tester and the Device under test. + +Functional set-up for PUSCH and PUCCH single antenna port performance requirements in multipath fading. The diagram shows a Tester connected to a Channel Simulator, which is also connected to an AWGN Generator. The output of the Channel Simulator is combined with the AWGN Generator output and sent to a Device under test inside an OTA chamber. A feedback loop connects the Device under test back to the Tester. A Time/frequency synchronization source (if used, see NOTE 2) is connected to both the Tester and the Device under test. + +**Figure E.3.1-1: Functional set-up for PUSCH and PUCCH single antenna port performance requirements in multipath fading** + +The OTA chamber shown in Figure E.3.1-1 is intended to be generic and can be replaced with any suitable OTA chamber (e.g. far field anechoic chamber, CATR, etc.). + +NOTE 1: The feedback could be done as an RF feedback, either using NR channels or using other means, or as a digital feedback. The HARQ Feedback should be error free. + +NOTE 2: In tests performed with signal generators, a synchronization signal may be provided between the IAB node and the signal generator, or a common (e.g., GNSS) source may be provided to both IAB node and the signal generator, to enable correct timing of the wanted signal. The method of synchronization with the TE is left to test implementation. + +NOTE 3: It is left up to implementation how L1/L2 is configured for testing. + +### E.3.2 2 antenna port PUSCH, PDCCH, PDSCH in multi-path fading + +![Figure E.3.2-1: Functional set-up for PUSCH, PDCCH, PDSCH performance requirements with Rx diversity (2 Rx case shown).](f2c8124b953b46b53423532cff4903e8_img.jpg) + +The diagram illustrates the functional set-up for testing PUSCH, PDCCH, and PDSCH performance requirements with Rx diversity, specifically for a 2 Rx case. On the left, a 'Tester' block is connected to a switch. The switch outputs are connected to two 'Channel Simulator' blocks and two 'AWGN Generator' blocks. The outputs of the two 'Channel Simulator' blocks are combined and then connected to the 'Device under test' (DUT) via two antennas. The outputs of the two 'AWGN Generator' blocks are also combined and connected to the DUT via the same two antennas. The DUT is shown within a dashed box representing an OTA chamber, with internal labels for angles $\theta$ and $\phi$ . A 'Feedback' line is shown from the DUT back to the Tester. At the bottom, a 'Time/ frequency synchronization source (if used. See NOTE 2)' is connected to the Tester and the DUT via dashed lines. + +Figure E.3.2-1: Functional set-up for PUSCH, PDCCH, PDSCH performance requirements with Rx diversity (2 Rx case shown). + +**Figure E.3.2-1: Functional set-up for PUSCH, PDCCH, PDSCH performance requirements with Rx diversity (2 Rx case shown)** + +The OTA chamber shown in Figure E.3.2-1 is intended to be generic and can be replaced with any suitable OTA chamber (e.g. far field anechoic chamber, CATR, etc.). + +NOTE 1: The feedback could be done as an RF feedback, either using NR channels or using other means, or as a digital feedback. The HARQ Feedback should be error free. + +NOTE 2: In tests performed with signal generators, a synchronization signal may be provided between the IAB node and the signal generator, or a common (e.g., GNSS) source may be provided to both IAB node and the signal generator, to enable correct timing of the wanted signal. The method of synchronization with the TE is left to test implementation. + +NOTE 3: It is left up to implementation how L1/L2 is configured for testing. + +### E.3.3 PUSCH, PRACH, CSI in static AWGN + +![Functional set-up for PUSCH, PRACH, CSI reporting performance requirements in static AWGN channel with Rx diversity (2 Rx case shown).](bb0e323a672fa2f89e0132b1db61cfb3_img.jpg) + +The diagram illustrates the functional set-up for testing. On the left, a 'Tester' block is connected to a signal splitter. The output of the splitter is connected to two 'AWGN Generator' blocks. The outputs of these generators are combined and then connected to a 'Device Under test' (DUT) inside an OTA chamber. The DUT has two receive antennas, labeled with angles $\theta$ and $\phi$ . A 'Feedback' line is shown from the DUT back to the Tester. A 'Time/ frequency synchronization source (if used, see NOTE 2)' is shown at the bottom, connected to both the Tester and the DUT via dashed lines. + +Functional set-up for PUSCH, PRACH, CSI reporting performance requirements in static AWGN channel with Rx diversity (2 Rx case shown). + +**Figure E.3.3-1: Functional set-up for PUSCH, PRACH, CSI reporting performance requirements in static AWGN channel with Rx diversity (2 Rx case shown)** + +The OTA chamber shown in Figure E.3.3-1 is intended to be generic and can be replaced with any suitable OTA chamber (e.g. far field anechoic chamber, CATR, etc.). + +NOTE 1: The feedback could be done as an RF feedback, either using NR channels or using other means, or as a digital feedback. The HARQ Feedback should be error free. + +NOTE 2: In tests performed with signal generators, a synchronization signal may be provided between the IAB node and the signal generator, or a common (e.g., GNSS) source may be provided to both IAB node and the signal generator, to enable correct timing of the wanted signal. The method of synchronization with the TE is left to test implementation. + +NOTE 3: It is left up to implementation how L1/L2 is configured for testing. + +--- + +## Annex F (normative): Void + +## Annex G (informative): Transmitter spatial emissions declaration + +### G.1 General + +The transmitter spatial emission declaration is an optional declaration which provides additional information on the power level of emission in the intended (in cell) spatial directions and the unintended (out of cell) spatial directions. The declarations are only valid when the beam is configured in one of the EIRP conformance directions. + +![Figure G.1-1: Example of out of cell directions set and declared single beam at a single extreme steering direction. The figure consists of two parts. The top part is a 'Directions diagram' showing a rectangular area representing the 'Out of cell directions set'. Inside this area, a dashed ellipse represents the 'OTA peak directions set'. Red 'X' marks indicate specific directions within the peak set. The horizontal axis is labeled with the Greek letter phi (φ) and the vertical axis with theta (θ). The bottom part is a graph showing power level versus phi (φ). A red curve represents the power level, with a prominent peak at the extreme steering direction. Two horizontal dashed lines indicate the 'In cell Power level (Average)' and the 'Out of cell power level (Average)'.](52e09725c3a496132a24092e9971bb2f_img.jpg) + +The figure illustrates the spatial emission declaration for a single beam at an extreme steering direction. The top part, titled 'Directions diagram', shows a rectangular region labeled 'Out of cell directions set'. Within this region, a dashed ellipse represents the 'OTA peak directions set'. Red 'X' marks indicate specific directions within the peak set. The horizontal axis is labeled with the Greek letter phi (φ) and the vertical axis with theta (θ). The bottom part is a graph showing power level versus phi (φ). A red curve represents the power level, with a prominent peak at the extreme steering direction. Two horizontal dashed lines indicate the 'In cell Power level (Average)' and the 'Out of cell power level (Average)'. + +Figure G.1-1: Example of out of cell directions set and declared single beam at a single extreme steering direction. The figure consists of two parts. The top part is a 'Directions diagram' showing a rectangular area representing the 'Out of cell directions set'. Inside this area, a dashed ellipse represents the 'OTA peak directions set'. Red 'X' marks indicate specific directions within the peak set. The horizontal axis is labeled with the Greek letter phi (φ) and the vertical axis with theta (θ). The bottom part is a graph showing power level versus phi (φ). A red curve represents the power level, with a prominent peak at the extreme steering direction. Two horizontal dashed lines indicate the 'In cell Power level (Average)' and the 'Out of cell power level (Average)'. + +**Figure G.1-1: Example of out of cell directions set and declared single beam at a single extreme steering direction** + +The declaration of unwanted spatial emission may in many circumstances not directly relate to system performance on its own. This is because it is often not possible to differentiate wanted and unwanted radiation, and furthermore because the benefits of optimizing beamforming performance may outweigh the impacts of "unwanted" radiation, leading to systems with apparently higher unwanted radiation also providing superior throughput performance. System performance should additionally be characterized taking all factors into account. + +## G.2 Declarations + +**Table G.2-1: Optional manufacturer declarations** + +| Declaration identifier | Declaration | Description | +|------------------------|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| Dxx.1 | Out of cell directions set | The set of directions which are outside the intended directions of radiation or outside the wanted cell. Declared per operating band. | +| Dxx.2 | Out of cell power level | Declared in band average power inside each of the out of cell directions set(s) (DE.1) declared for each of the 5 conformance directions (D9.x) | +| Dxx.3 | In cell power level | Declared in band average power outside the out of cell directions set(s) (DE.1) declared for each of the 5 conformance directions (D9.x) | +| Dxx.4 | Average out of cell power level | Declared in band average power inside each of the out of cell directions set(s) (DE.1) averaged over the 5 conformance directions (D9.x). | +| DE.5 | Average in cell power level | Declared in band average power inside each of the out of cell directions set(s) (DE.1) averaged over the 5 conformance directions (D9.x) | + +NOTE 1: The declaration of unwanted spatial emission may in many circumstances not directly relate to system performance on its own. This is because it is often not possible to differentiate wanted and unwanted radiation, and furthermore because the benefits of optimizing beamforming performance may outweigh the impacts of "unwanted" radiation, leading to systems with apparently higher unwanted radiation also providing superior throughput performance. System performance should additionally be characterized taking all factors into account. + +NOTE 2: The average out of cell power level reflects the impact of out of cell radiation on other cells more accurately than the out of cell power level for individual test beams. + +--- + +## Annex H (normative): Characteristics of the interfering signals + +### H.1 Characteristics of the interfering signals for IAB-DU + +The Annex D in TS 38.104 [4] apply to FR2-1 IAB-DU. + +--- + +### H.2 Characteristics of the interfering signals for IAB-MT + +The interfering signal shall be configured with PDSCH and PDCCH containing data and DM-RS symbols. Normal cyclic prefix is used. The data content shall be uncorrelated to the wanted signal and modulated according to clause 7 of TS 38.211 [7]. Mapping of PDSCH modulation to receiver requirement are specified in table E.2-1. + +**Table E.2-1: Modulation of the interfering signal** + +| Receiver requirement | Modulation | +|-------------------------------------------------------|------------| +| Adjacent channel selectivity and narrow-band blocking | QPSK | +| General blocking | QPSK | +| Receiver intermodulation | QPSK | + +--- + +## Annex I (normative): TRP measurement procedures + +The Annex I in TS38.141-2[6] applies to IAB. + +## Annex J (normative): Propagation conditions + +### J.1 Static propagation condition + +The propagation for the static performance measurement is an Additive White Gaussian Noise (AWGN) environment. No fading or multi-paths exist for this propagation model. + +#### J.1.1 IAB-MT Receiver with 2 Rx + +For 1 port transmission the channel matrix is defined in the frequency domain by: + +$$\mathbf{H} = \begin{pmatrix} 1 \\ 1 \end{pmatrix}.$$ + +For 2 port transmission the channel matrix is defined in the frequency domain by: + +$$\mathbf{H} = \begin{pmatrix} 1 & j \\ 1 & -j \end{pmatrix}.$$ + +For 4 port transmission the channel matrix is defined in the frequency domain by: + +$$\mathbf{H} = \begin{bmatrix} 1 & 1 & j & j \\ 1 & 1 & -j & -j \end{bmatrix}$$ + +For 8 port transmission the channel matrix is defined in the frequency domain by: + +$$\mathbf{H} = \begin{bmatrix} 1 & 1 & 1 & 1 & j & j & j & j \\ 1 & 1 & 1 & 1 & -j & -j & -j & -j \end{bmatrix}$$ + +### J.2 Multi-path fading propagation conditions + +The multipath propagation conditions consist of several parts: + +- A delay profile in the form of a "tapped delay-line", characterized by a number of taps at fixed positions on a sampling grid. The profile can be further characterized by the r.m.s. delay spread and the maximum delay spanned by the taps. +- A combination of channel model parameters that include the Delay profile and the Doppler spectrum that is characterized by a classical spectrum shape and a maximum Doppler frequency. +- Different models are used for FR1 (410 MHz - 7.125GHz) and FR2-1 (24.25 GHz – 52.6 GHz). + +#### J.2.1 Delay profiles + +The delay profiles are simplified from the TR 38.901 [26] TDL models. The simplification steps are shown below for information. These steps are only used when new delay profiles are created. Otherwise, the delay profiles specified in annex J.2.1.1 and J.2.1.2 can be used as such. + +Step 1: Use the original TDL model from TR 38.901 [26]. + +Step 2: Re-order the taps in ascending delays. + +Step 3: Perform delay scaling according to the procedure described in clause 7.7.3 in TR 38.901 [26]. + +Step 4: Apply the quantization to the delay resolution 5 ns. This is done simply by rounding the tap delays to the nearest multiple of the delay resolution. + +Step 5: If multiple taps are rounded to the same delay bin, merge them by calculating their linear power sum. + +Step 6: If there are more than 12 taps in the quantized model, merge the taps as follows: + +- Find the weakest tap from all taps (both merged and unmerged taps are considered) +- If there are two or more taps having the same value and are the weakest, select the tap with the smallest delay as the weakest tap. +- When the weakest tap is the first delay tap, merge taps as follows: + - Update the power of the first delay tap as the linear power sum of the weakest tap and the second delay tap. + - Remove the second delay tap. +- When the weakest tap is the last delay tap, merge taps as follows: + - Update the power of the last delay tap as the linear power sum of the second-to-last tap and the last tap. + - Remove the second-to-last tap. +- Otherwise: + - For each side of the weakest tap, identify the neighbour tap that has the smaller delay difference to the weakest tap. + - When the delay difference between the weakest tap and the identified neighbour tap on one side equals the delay difference between the weakest tap and the identified neighbour tap on the other side. + - Select the neighbour tap that is weaker in power for merging. + - Otherwise, select the neighbour tap that has smaller delay difference for merging. + - To merge, the power of the merged tap is the linear sum of the power of the weakest tap and the selected tap. + - When the selected tap is the first tap, the location of the merged tap is the location of the first tap. The weakest tap is removed. + - When the selected tap is the last tap, the location of the merged tap is the location of the last tap. The weakest tap is removed. + - Otherwise, the location of the merged tap is based on the average delay of the weakest tap and selected tap. If the average delay is on the sampling grid, the location of the merged tap is the average delay. Otherwise, the location of the merged tap is rounded towards the direction of the selected tap (e.g. 10 ns & 20 ns → 15 ns, 10 ns & 25 ns → 20 ns, if 25 ns had higher or equal power; 15 ns, if 10 ns had higher power). The weakest tap and the selected tap are removed. +- Repeat step 6 until the final number of taps is 12. + +Step 7: Round the amplitudes of taps to one decimal (e.g. -8.78 dB → -8.8 dB) + +Step 8: If the delay spread has slightly changed due to the tap merge, adjust the final delay spread by increasing or decreasing the power of the last tap so that the delay spread is corrected. + +Step 9: Re-normalize the highest tap to 0 dB. + +NOTE 1: Some values of the delay profile created by the simplification steps may differ from the values in tables J.2.1.1-2, J.2.1.1-3, J.2.1.1-4, and J.2.1.2-2 for the corresponding model. + +NOTE 2: For Step 5 and Step 6, the power values are expressed in the linear domain using 6 digits of precision. The operations are in the linear domain. + +### J.2.1.1 Delay profiles for FR1 + +The delay profiles for FR1 are selected to be representative of low, medium and high delay spread environment. The resulting model parameters are specified in Table J.2.1.1-1 and the tapped delay line models are specified in tables J.2.1.1-2 to J.2.1.1-4. + +**Table J.2.1.1-1: Delay profiles for NR channel models** + +| Model | Number of channel taps | Delay spread (r.m.s.) | Maximum excess tap delay (span) | Delay resolution | +|---------|------------------------|-----------------------|---------------------------------|------------------| +| TDLA30 | 12 | 30 ns | 290 ns | 5 ns | +| TDLB100 | 12 | 100 ns | 480 ns | 5 ns | +| TDLC300 | 12 | 300 ns | 2595 ns | 5 ns | + +**Table J.2.1.1-2: TDLA30 (DS = 30 ns)** + +| Tap # | Delay (ns) | Power (dB) | Fading distribution | +|-------|------------|------------|---------------------| +| 1 | 0 | -15.5 | Rayleigh | +| 2 | 10 | 0 | | +| 3 | 15 | -5.1 | | +| 4 | 20 | -5.1 | | +| 5 | 25 | -9.6 | | +| 6 | 50 | -8.2 | | +| 7 | 65 | -13.1 | | +| 8 | 75 | -11.5 | | +| 9 | 105 | -11.0 | | +| 10 | 135 | -16.2 | | +| 11 | 150 | -16.6 | | +| 12 | 290 | -26.2 | | + +**Table J.2.1.1-3: TDLB100 (DS = 100ns)** + +| Tap # | Delay (ns) | Power (dB) | Fading distribution | +|-------|------------|------------|---------------------| +| 1 | 0 | 0 | Rayleigh | +| 2 | 10 | -2.2 | | +| 3 | 20 | -0.6 | | +| 4 | 30 | -0.6 | | +| 5 | 35 | -0.3 | | +| 6 | 45 | -1.2 | | +| 7 | 55 | -5.9 | | +| 8 | 120 | -2.2 | | +| 9 | 170 | -0.8 | | +| 10 | 245 | -6.3 | | +| 11 | 330 | -7.5 | | +| 12 | 480 | -7.1 | | + +**Table J.2.1.1-4: TDLC300 (DS = 300 ns)** + +| Tap # | Delay (ns) | Power (dB) | Fading distribution | +|-------|------------|------------|---------------------| +| 1 | 0 | -6.9 | Rayleigh | +| 2 | 65 | 0 | | +| 3 | 70 | -7.7 | | +| 4 | 190 | -2.5 | | +| 5 | 195 | -2.4 | | +| 6 | 200 | -9.9 | | +| 7 | 240 | -8.0 | | +| 8 | 325 | -6.6 | | +| 9 | 520 | -7.1 | | +| 10 | 1045 | -13.0 | | +| 11 | 1510 | -14.2 | | +| 12 | 2595 | -16.0 | | + +### J.2.1.2 Delay profiles for FR2-1 + +The delay profiles for FR2-1 are specified in J.2.1.2-1 and the tapped delay line models are specified in table J.2.1.2-2. + +**Table J.2.1.2-1: Delay profiles for NR channel models** + +| Model | Number of channel taps | Delay spread (r.m.s.) | Maximum excess tap delay (span) | Delay resolution | +|--------|------------------------|-----------------------|---------------------------------|------------------| +| TDLA30 | 12 | 30 ns | 290 ns | 5 ns | + +**Table J.2.1.2-2: TDLA30 (DS = 30 ns)** + +| Tap # | Delay (ns) | Power (dB) | Fading distribution | +|-------|------------|------------|---------------------| +| 1 | 0 | -15.5 | Rayleigh | +| 2 | 10 | 0 | | +| 3 | 15 | -5.1 | | +| 4 | 20 | -5.1 | | +| 5 | 25 | -9.6 | | +| 6 | 50 | -8.2 | | +| 7 | 65 | -13.1 | | +| 8 | 75 | -11.5 | | +| 9 | 105 | -11.0 | | +| 10 | 135 | -16.2 | | +| 11 | 150 | -16.6 | | +| 12 | 290 | -26.2 | | + +### J.2.2 Combinations of channel model parameters + +The propagation conditions used for the performance measurements in multi-path fading environment are indicated as a combination of a channel model name and a maximum Doppler frequency, i.e., TDLA-, TDLB- or TDLC- where '' indicates the desired delay spread and '' indicates the maximum Doppler frequency (Hz). + +Table J.2.2-1 and J.2.2-2 show the propagation conditions that are used for the performance measurements in multi-path fading environment for low, medium and high Doppler frequencies for FR1 and FR2, respectively. + +**Table J.2.2-1: Channel model parameters for FR1** + +| Combination name | Model | Maximum Doppler frequency | +|------------------|---------|---------------------------| +| TDLA30-5 | TDLA30 | 5 Hz | +| TDLA30-10 | TDLA30 | 10 Hz | +| TDLB100-400 | TDLB100 | 400 Hz | +| TDLC300-100 | TDLC300 | 100 Hz | + +**Table J.2.2-2: Channel model parameters for FR2** + +| Combination name | Model | Maximum Doppler frequency | +|------------------|--------|---------------------------| +| TDLA30-75 | TDLA30 | 75 Hz | +| TDLA30-300 | TDLA30 | 300 Hz | + +### J.2.3 MIMO channel correlation matrices + +The MIMO channel correlation matrices defined in J.2.3 apply for the antenna configuration using uniform linear arrays at both IAB-DU and IAB-MT and for the antenna configuration using cross polarized antennas. + +### J.2.3.1 MIMO correlation matrices using Uniform Linear Array (ULA) + +The MIMO channel correlation matrices defined in J.2.3.1 apply for the antenna configuration using uniform linear array (ULA) at both IAB-DU and IAB-MT. + +#### J.2.3.1.1 Definition of MIMO correlation matrices + +Table J.2.3.1.1-1 defines the correlation matrix for the IAB-DU. + +**Table J.2.3.1.1-1: IAB-DU correlation matrix** + +| | | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| One antenna | IAB-DU correlation
$R_{gNB} = 1$ | +| Two antennas | $R_{gNB} = \begin{pmatrix} 1 & \alpha \\ \alpha^* & 1 \end{pmatrix}$ | +| Four antennas | $R_{gNB} = \begin{pmatrix} 1 & \alpha^{1/9} & \alpha^{4/9} & \alpha \\ \alpha^{1/9*} & 1 & \alpha^{1/9} & \alpha^{4/9} \\ \alpha^{4/9*} & \alpha^{1/9*} & 1 & \alpha^{1/9} \\ \alpha^* & \alpha^{4/9*} & \alpha^{1/9*} & 1 \end{pmatrix}$ | +| Eight antennas | $R_{gNB} = \begin{pmatrix} 1 & \alpha^{1/49} & \alpha^{4/49} & \alpha^{9/49} & \alpha^{16/49} & \alpha^{25/49} & \alpha^{36/49} & \alpha \\ \alpha^{1/49*} & 1 & \alpha^{1/49} & \alpha^{4/49} & \alpha^{9/49} & \alpha^{16/49} & \alpha^{25/49} & \alpha^{36/49} \\ \alpha^{4/49*} & \alpha^{1/49*} & 1 & \alpha^{1/49} & \alpha^{4/49} & \alpha^{9/49} & \alpha^{16/49} & \alpha^{25/49} \\ \alpha^{9/49*} & \alpha^{4/49*} & \alpha^{1/49*} & 1 & \alpha^{1/49} & \alpha^{4/49} & \alpha^{9/49} & \alpha^{16/49} \\ \alpha^{16/49*} & \alpha^{9/49*} & \alpha^{4/49*} & \alpha^{1/49*} & 1 & \alpha^{1/49} & \alpha^{4/49} & \alpha^{9/49} \\ \alpha^{25/49*} & \alpha^{16/49*} & \alpha^{9/49*} & \alpha^{4/49*} & \alpha^{1/49*} & 1 & \alpha^{1/49} & \alpha^{4/49} \\ \alpha^{36/49*} & \alpha^{25/49*} & \alpha^{16/49*} & \alpha^{9/49*} & \alpha^{4/49*} & \alpha^{1/49*} & 1 & \alpha^{1/49} \\ \alpha^* & \alpha^{36/49*} & \alpha^{25/49*} & \alpha^{16/49*} & \alpha^{9/49*} & \alpha^{4/49*} & \alpha^{1/49*} & 1 \end{pmatrix}$ | + +Table J.2.3.1.1-2 defines the correlation matrix for the IAB-MT: + +**Table J.2.3.1.1-2: IAB-MT correlation matrix** + +| | One antenna | Two antennas | Four antennas | +|--------------------|--------------|-------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IAB-MT correlation | $R_{UE} = 1$ | $R_{UE} = \begin{pmatrix} 1 & \beta \\ \beta^* & 1 \end{pmatrix}$ | $R_{UE} = \begin{pmatrix} 1 & \beta^{1/9} & \beta^{4/9} & \beta \\ \beta^{1/9*} & 1 & \beta^{1/9} & \beta^{4/9} \\ \beta^{4/9*} & \beta^{1/9*} & 1 & \beta^{1/9} \\ \beta^* & \beta^{4/9*} & \beta^{1/9*} & 1 \end{pmatrix}$ | + +Table J.2.3.1.1-3 defines the channel spatial correlation matrix $R_{spat}$ . The parameters, $\alpha$ and $\beta$ in table J.2.3.1.1-3 defines the spatial correlation between the antennas at the IAB-DU and IAB-MT respectively. + +**Table J.2.3.1.1-3: $R_{spat}$ correlation matrices** + +| | | +|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1x2 case | $R_{spat} = R_{gNB} = \begin{bmatrix} 1 & \alpha \\ \alpha^* & 1 \end{bmatrix}$ | +| 1x4 case | $R_{spat} = R_{gNB} = \begin{bmatrix} 1 & \alpha^{1/3} & \alpha^{2/3} & \alpha \\ \alpha^{1/3*} & 1 & \alpha^{1/3} & \alpha^{2/3} \\ \alpha^{2/3*} & \alpha^{1/3*} & 1 & \alpha^{1/3} \\ \alpha^* & \alpha^{2/3*} & \alpha^{1/3*} & 1 \end{bmatrix}$ | +| 2x2 case | $R_{spat} = R_{UE} \otimes R_{gNB} = \begin{pmatrix} 1 & \beta \\ \beta^* & 1 \end{pmatrix} \otimes \begin{pmatrix} 1 & \alpha \\ \alpha^* & 1 \end{pmatrix} = \begin{pmatrix} 1 & \alpha & \beta & \beta\alpha \\ \alpha^* & 1 & \beta\alpha^* & \beta \\ \beta^* & \beta^*\alpha & 1 & \alpha \\ \beta^*\alpha^* & \beta^* & \alpha^* & 1 \end{pmatrix}$ | +| 2x4 case | $R_{spat} = R_{UE} \otimes R_{gNB} = \begin{pmatrix} 1 & \beta \\ \beta^* & 1 \end{pmatrix} \otimes \begin{pmatrix} 1 & \alpha^{1/3} & \alpha^{2/3} & \alpha \\ \alpha^{1/3*} & 1 & \alpha^{1/3} & \alpha^{2/3} \\ \alpha^{2/3*} & \alpha^{1/3*} & 1 & \alpha^{1/3} \\ \alpha^* & \alpha^{2/3*} & \alpha^{1/3*} & 1 \end{pmatrix}$ | +| 4x4 case | $R_{spat} = R_{UE} \otimes R_{gNB} = \begin{pmatrix} 1 & \beta^{1/3} & \beta^{2/3} & \beta \\ \beta^{1/3*} & 1 & \beta^{1/3} & \beta^{2/3} \\ \beta^{2/3*} & \beta^{1/3*} & 1 & \beta^{1/3} \\ \beta^* & \beta^{2/3*} & \beta^{1/3*} & 1 \end{pmatrix} \otimes \begin{pmatrix} 1 & \alpha^{1/3} & \alpha^{2/3} & \alpha \\ \alpha^{1/3*} & 1 & \alpha^{1/3} & \alpha^{2/3} \\ \alpha^{2/3*} & \alpha^{1/3*} & 1 & \alpha^{1/3} \\ \alpha^* & \alpha^{2/3*} & \alpha^{1/3*} & 1 \end{pmatrix}$ | + +For cases with more antennas at either IAB-DU or IAB-MT or both, the channel spatial correlation matrix can still be expressed as the Kronecker product of $R_{UE}$ and $R_{gNB}$ according to $R_{spat} = R_{UE} \otimes R_{gNB}$ . + +### J.2.3.1.2 MIMO correlation matrices at high, medium and low level + +The $\alpha$ and $\beta$ for different correlation types are given in table J.2.3.1.2-1. + +**Table J.2.3.1.2-1: Correlation for high, medium and low level** + +| Low correlation | | Medium correlation | | High correlation | | +|-----------------|---------|--------------------|---------|------------------|---------| +| $\alpha$ | $\beta$ | $\alpha$ | $\beta$ | $\alpha$ | $\beta$ | +| 0 | 0 | 0.9 | 0.3 | 0.9 | 0.9 | + +The correlation matrices for high, medium and low correlation are defined in tables J.2.3.1.2-2, J.2.3.1.2-3 and J.2.3.1.2-4 as below. + +The values in table J.2.3.1.2-2 have been adjusted for the 2x4 and 4x4 high correlation cases to ensure the correlation matrix is positive semi-definite after round-off to 4 digit precision. This is done using the equation: + +$$\mathbf{R}_{high} = [\mathbf{R}_{spatial} + a\mathbf{I}_n] / (1 + a)$$ + +Where the value "a" is a scaling factor such that the smallest value is used to obtain a positive semi-definite result. For the 2x4 high correlation case, a=0.00010. For the 4x4 high correlation case, a=0.00012. + +The same method is used to adjust the 4x4 medium correlation matrix in table J.2.3.1.2-3 to ensure the correlation matrix is positive semi-definite after round-off to 4 digit precision with a =0.00012. + +**Table J.2.3.1.2-2: MIMO correlation matrices for high correlation** + +| | | +|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1x2 case | $R_{high} = \begin{pmatrix} 1 & 0.9 \\ 0.9 & 1 \end{pmatrix}$ | +| 2x2 case | $R_{high} = \begin{pmatrix} 1 & 0.9 & 0.9 & 0.81 \\ 0.9 & 1 & 0.81 & 0.9 \\ 0.9 & 0.81 & 1 & 0.9 \\ 0.81 & 0.9 & 0.9 & 1 \end{pmatrix}$ | +| 2x4 case | $R_{high} = \begin{bmatrix} 1.0000 & 0.9883 & 0.9542 & 0.8999 & 0.8999 & 0.8894 & 0.8587 & 0.8099 \\ 0.9883 & 1.0000 & 0.9883 & 0.9542 & 0.8894 & 0.8999 & 0.8894 & 0.8587 \\ 0.9542 & 0.9883 & 1.0000 & 0.9883 & 0.8587 & 0.8894 & 0.8999 & 0.8894 \\ 0.8999 & 0.9542 & 0.9883 & 1.0000 & 0.8099 & 0.8587 & 0.8894 & 0.8999 \\ 0.8999 & 0.8894 & 0.8587 & 0.8099 & 1.0000 & 0.9883 & 0.9542 & 0.8999 \\ 0.8894 & 0.8999 & 0.8894 & 0.8587 & 0.9883 & 1.0000 & 0.9883 & 0.9542 \\ 0.8587 & 0.8894 & 0.8999 & 0.8894 & 0.9542 & 0.9883 & 1.0000 & 0.9883 \\ 0.8099 & 0.8587 & 0.8894 & 0.8999 & 0.8999 & 0.9542 & 0.9883 & 1.0000 \end{bmatrix}$ | +| 4x4 case | $R_{high} = \begin{bmatrix} 1.0000 & 0.9882 & 0.9541 & 0.8999 & 0.9882 & 0.9767 & 0.9430 & 0.8894 & 0.9541 & 0.9430 & 0.9105 & 0.8587 & 0.8999 & 0.8894 & 0.8587 & 0.8099 \\ 0.9882 & 1.0000 & 0.9882 & 0.9541 & 0.9767 & 0.9882 & 0.9767 & 0.9430 & 0.9430 & 0.9541 & 0.9430 & 0.9105 & 0.8894 & 0.8999 & 0.8894 & 0.8587 \\ 0.9541 & 0.9882 & 1.0000 & 0.9882 & 0.9430 & 0.9767 & 0.9882 & 0.9767 & 0.9105 & 0.9430 & 0.9541 & 0.9430 & 0.8587 & 0.8894 & 0.8999 & 0.8894 \\ 0.8999 & 0.9541 & 0.9882 & 1.0000 & 0.8894 & 0.9430 & 0.9767 & 0.9882 & 0.8587 & 0.9105 & 0.9430 & 0.9541 & 0.8099 & 0.8587 & 0.8894 & 0.8999 \\ 0.9882 & 0.9767 & 0.9430 & 0.8894 & 1.0000 & 0.9882 & 0.9541 & 0.8999 & 0.9882 & 0.9767 & 0.9430 & 0.8894 & 0.9541 & 0.9430 & 0.9105 & 0.8587 \\ 0.9767 & 0.9882 & 0.9767 & 0.9430 & 0.9882 & 1.0000 & 0.9882 & 0.9541 & 0.9767 & 0.9882 & 0.9767 & 0.9430 & 0.9430 & 0.9541 & 0.9430 & 0.9105 \\ 0.9430 & 0.9767 & 0.9882 & 0.9767 & 0.9541 & 0.9882 & 1.0000 & 0.9882 & 0.9430 & 0.9767 & 0.9882 & 0.9767 & 0.9105 & 0.9430 & 0.9541 & 0.9430 \\ 0.8894 & 0.9430 & 0.9767 & 0.9882 & 0.8999 & 0.9541 & 0.9882 & 1.0000 & 0.8894 & 0.9430 & 0.9767 & 0.9882 & 0.8587 & 0.9105 & 0.9430 & 0.9541 \\ 0.9541 & 0.9430 & 0.9105 & 0.8587 & 0.9882 & 0.9767 & 0.9430 & 0.8894 & 1.0000 & 0.9882 & 0.9541 & 0.8999 & 0.9882 & 0.9767 & 0.9430 & 0.8894 \\ 0.9430 & 0.9541 & 0.9430 & 0.9105 & 0.9767 & 0.9882 & 0.9767 & 0.9430 & 0.9882 & 1.0000 & 0.9882 & 0.9541 & 0.9767 & 0.9882 & 0.9767 & 0.9430 \\ 0.9105 & 0.9430 & 0.9541 & 0.9430 & 0.9430 & 0.9767 & 0.9882 & 0.9767 & 0.9541 & 0.9882 & 1.0000 & 0.9882 & 0.9430 & 0.9767 & 0.9882 & 0.9767 \\ 0.8587 & 0.9105 & 0.9430 & 0.9541 & 0.8894 & 0.9430 & 0.9767 & 0.9882 & 0.8999 & 0.9541 & 0.9882 & 1.0000 & 0.8894 & 0.9430 & 0.9767 & 0.9882 \\ 0.8999 & 0.8894 & 0.8587 & 0.8099 & 0.9541 & 0.9430 & 0.9105 & 0.8587 & 0.9882 & 0.9767 & 0.9430 & 0.8894 & 1.0000 & 0.9882 & 0.9541 & 0.8999 \\ 0.8894 & 0.8999 & 0.8894 & 0.8587 & 0.9430 & 0.9541 & 0.9430 & 0.9105 & 0.9767 & 0.9882 & 0.9767 & 0.9430 & 0.9882 & 1.0000 & 0.9882 & 0.9541 \\ 0.8587 & 0.8894 & 0.8999 & 0.8894 & 0.9105 & 0.9430 & 0.9541 & 0.9430 & 0.9430 & 0.9767 & 0.9882 & 0.9767 & 0.9541 & 0.9882 & 1.0000 & 0.9882 \\ 0.8099 & 0.8587 & 0.8894 & 0.8999 & 0.8587 & 0.9105 & 0.9430 & 0.9541 & 0.8894 & 0.9430 & 0.9767 & 0.9882 & 0.8999 & 0.9541 & 0.9882 & 1.0000 \end{bmatrix}$ | + +**Table J.2.3.1.2-3: MIMO correlation matrices for medium correlation** + +| | | +|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1x2 case | N/A | +| 2x2 case | $R_{medium} = \begin{pmatrix} 1.0000 & 0.9000 & 0.3000 & 0.2700 \\ 0.9000 & 1.0000 & 0.2700 & 0.3000 \\ 0.3000 & 0.2700 & 1.0000 & 0.9000 \\ 0.2700 & 0.3000 & 0.9000 & 1.0000 \end{pmatrix}$ | +| 2x4 case | $R_{medium} = \begin{bmatrix} 1.0000 & 0.9884 & 0.9543 & 0.9000 & 0.3000 & 0.2965 & 0.2863 & 0.2700 \\ 0.9884 & 1.0000 & 0.9884 & 0.9543 & 0.2965 & 0.3000 & 0.2965 & 0.2863 \\ 0.9543 & 0.9884 & 1.0000 & 0.9884 & 0.2863 & 0.2965 & 0.3000 & 0.2965 \\ 0.9000 & 0.9543 & 0.9884 & 1.0000 & 0.2700 & 0.2863 & 0.2965 & 0.3000 \\ 0.3000 & 0.2965 & 0.2863 & 0.2700 & 1.0000 & 0.9884 & 0.9543 & 0.9000 \\ 0.2965 & 0.3000 & 0.2965 & 0.2863 & 0.9884 & 1.0000 & 0.9884 & 0.9543 \\ 0.2863 & 0.2965 & 0.3000 & 0.2965 & 0.9543 & 0.9884 & 1.0000 & 0.9884 \\ 0.2700 & 0.2863 & 0.2965 & 0.3000 & 0.9000 & 0.9543 & 0.9884 & 1.0000 \end{bmatrix}$ | +| 4x4 case | $R_{medium} = \begin{bmatrix} 1.0000 & 0.9882 & 0.9541 & 0.8999 & 0.8747 & 0.8645 & 0.8347 & 0.7872 & 0.5855 & 0.5787 & 0.5588 & 0.5270 & 0.3000 & 0.2965 & 0.2862 & 0.2700 \\ 0.9882 & 1.0000 & 0.9882 & 0.9541 & 0.8645 & 0.8747 & 0.8645 & 0.8347 & 0.5787 & 0.5855 & 0.5787 & 0.5588 & 0.2965 & 0.3000 & 0.2965 & 0.2862 \\ 0.9541 & 0.9882 & 1.0000 & 0.9882 & 0.8347 & 0.8645 & 0.8747 & 0.8645 & 0.5588 & 0.5787 & 0.5855 & 0.5787 & 0.2862 & 0.2965 & 0.3000 & 0.2965 \\ 0.8999 & 0.9541 & 0.9882 & 1.0000 & 0.7872 & 0.8347 & 0.8645 & 0.8747 & 0.5270 & 0.5588 & 0.5787 & 0.5855 & 0.2700 & 0.2862 & 0.2965 & 0.3000 \\ 0.8747 & 0.8645 & 0.8347 & 0.7872 & 1.0000 & 0.9882 & 0.9541 & 0.8999 & 0.8747 & 0.8645 & 0.8347 & 0.7872 & 0.5855 & 0.5787 & 0.5588 & 0.5270 \\ 0.8645 & 0.8747 & 0.8645 & 0.8347 & 0.9882 & 1.0000 & 0.9882 & 0.9541 & 0.8645 & 0.8747 & 0.8645 & 0.8347 & 0.5787 & 0.5855 & 0.5787 & 0.5588 \\ 0.8347 & 0.8645 & 0.8747 & 0.8645 & 0.9541 & 0.9882 & 1.0000 & 0.9882 & 0.8347 & 0.8645 & 0.8747 & 0.8645 & 0.5588 & 0.5787 & 0.5855 & 0.5787 \\ 0.7872 & 0.8347 & 0.8645 & 0.8747 & 0.8999 & 0.9541 & 0.9882 & 1.0000 & 0.7872 & 0.8347 & 0.8645 & 0.8747 & 0.5270 & 0.5588 & 0.5787 & 0.5855 \\ 0.5855 & 0.5787 & 0.5588 & 0.5270 & 0.8747 & 0.8645 & 0.8347 & 0.7872 & 1.0000 & 0.9882 & 0.9541 & 0.8999 & 0.8747 & 0.8645 & 0.8347 & 0.7872 \\ 0.5787 & 0.5855 & 0.5787 & 0.5588 & 0.8645 & 0.8747 & 0.8645 & 0.8347 & 0.9882 & 1.0000 & 0.9882 & 0.9541 & 0.8645 & 0.8747 & 0.8645 & 0.8347 \\ 0.5588 & 0.5787 & 0.5855 & 0.5787 & 0.8347 & 0.8645 & 0.8747 & 0.8645 & 0.9541 & 0.9882 & 1.0000 & 0.9882 & 0.8347 & 0.8645 & 0.8747 & 0.8645 \\ 0.5270 & 0.5588 & 0.5787 & 0.5855 & 0.7872 & 0.8347 & 0.8645 & 0.8747 & 0.8999 & 0.9541 & 0.9882 & 1.0000 & 0.7872 & 0.8347 & 0.8645 & 0.8747 \\ 0.3000 & 0.2965 & 0.2862 & 0.2700 & 0.5855 & 0.5787 & 0.5588 & 0.5270 & 0.8747 & 0.8645 & 0.8347 & 0.7872 & 1.0000 & 0.9882 & 0.9541 & 0.8999 \\ 0.2965 & 0.3000 & 0.2965 & 0.2862 & 0.5787 & 0.5855 & 0.5787 & 0.5588 & 0.8645 & 0.8747 & 0.8645 & 0.8347 & 0.9882 & 1.0000 & 0.9882 & 0.9541 \\ 0.2862 & 0.2965 & 0.3000 & 0.2965 & 0.5588 & 0.5787 & 0.5855 & 0.5787 & 0.8347 & 0.8645 & 0.8747 & 0.8645 & 0.9541 & 0.9882 & 1.0000 & 0.9882 \\ 0.2700 & 0.2862 & 0.2965 & 0.3000 & 0.5270 & 0.5588 & 0.5787 & 0.5855 & 0.7872 & 0.8347 & 0.8645 & 0.8747 & 0.8999 & 0.9541 & 0.9882 & 1.0000 \end{bmatrix}$ | + +**Table J.2.3.1.2-4: MIMO correlation matrices for low correlation** + +| | | +|----------|-----------------------------| +| 1x2 case | $R_{low} = \mathbf{I}_2$ | +| 1x4 case | $R_{low} = \mathbf{I}_4$ | +| 1x8 case | | +| 2x2 case | $R_{low} = \mathbf{I}_4$ | +| 2x4 case | $R_{low} = \mathbf{I}_8$ | +| 2x8 case | | +| 4x4 case | $R_{low} = \mathbf{I}_{16}$ | + +In table J.2.3.1.2-4, $\mathbf{I}_d$ is a $d \times d$ identity matrix. + +NOTE: For completeness, the correlation matrices were defined for high, medium and low correlation but performance requirements exist only for low correlation. + +## J.2.3.2 Multi-antenna channel models using cross polarized antennas + +The MIMO channel correlation matrices defined in J.2.3.2 apply to two cases as presented below: + +- One TX antenna and multiple RX antennas case, with cross polarized antennas used at gNB +- Multiple TX antennas and multiple RX antennas case, with cross polarized antennas used at both UE and gNB + +The cross-polarized antenna elements with +/-45 degrees polarization slant angles are deployed at gNB. For one TX antenna case, antenna element with +90 degree polarization slant angle is deployed at UE. For multiple TX antennas case, cross-polarized antenna elements with +90/0 degrees polarization slant angles are deployed at UE. + +For the cross-polarized antennas, the N antennas are labelled such that antennas for one polarization are listed from 1 to N/2 and antennas for the other polarization are listed from N/2+1 to N, where N is the number of TX or RX antennas. + +### J.2.3.2.1 Definition of MIMO correlation matrices using cross polarized antennas + +For the channel spatial correlation matrix, the following is used: + +$$R_{spat} = P_{UL} (R_{UE} \otimes \Gamma_{UL} \otimes R_{gNB}) P_{UL}^T$$ + +Where + +- $R_{UE}$ is the spatial correlation matrix at the UE with same polarization, +- $R_{gNB}$ is the spatial correlation matrix at the gNB with same polarization, +- $\Gamma_{UL}$ is a polarization correlation matrix, +- $P_{UL}$ is a permutation matrix, and +- $(\bullet)^T$ denotes transpose. + +Table J.2.3.2.1-1 defines the polarization correlation matrix. + +**Table J.2.3.2.1-1 : Polarization correlation matrix** + +| | One TX antenna | Multiple TX antennas | +|---------------------------------|--------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| Polarization correlation matrix | $\Gamma_{UL} = \begin{bmatrix} 1 & -\gamma \\ -\gamma & 1 \end{bmatrix}$ | $\Gamma_{UL} = \begin{bmatrix} 1 & -\gamma & 0 & 0 \\ -\gamma & 1 & 0 & 0 \\ 0 & 0 & 1 & \gamma \\ 0 & 0 & \gamma & 1 \end{bmatrix}$ | + +The matrix $P_{UL}$ is defined as + +$$P_{UL}(a,b) = \begin{cases} 1 & \text{for } a = (j - 1)N_r + i \text{ and } b = 2(j - 1)N_r + i, \quad i = 1, \dots, N_r, j = 1, \dots, \lceil N_t / 2 \rceil \\ 1 & \text{for } a = (j - 1)N_r + i \text{ and } b = 2(j - \lceil N_t / 2 \rceil)N_r - N_r + i, \quad i = 1, \dots, N_r, j = \lceil N_t / 2 \rceil + 1, \dots, N_t \\ 0 & \text{otherwise} \end{cases}$$ + +where $N_t$ and $N_r$ is the number of TX and RX antennas respectively, and $\lceil \cdot \rceil$ is the ceiling operator. + +The matrix $P_{UL}$ is used to map the spatial correlation coefficients in accordance with the antenna element labelling system described in J.2.3.2. + +### J.2.3.2.2 Spatial correlation matrices at IAB-MT and IAB-DU sides + +#### J.2.3.2.2.1 Spatial correlation matrices at IAB-MT side + +For 1-antenna transmitter, $R_{UE} = 1$ . + +For 2-antenna transmitter using one pair of cross-polarized antenna elements, $R_{UE} = 1$ . + +$$R_{UE} = \begin{pmatrix} 1 & \beta \\ \beta^* & 1 \end{pmatrix}$$ + +For 4-antenna transmitter using two pairs of cross-polarized antenna elements, + +#### J.2.3.2.2.2 Spatial correlation matrices at IAB-DU side + +For 2-antenna receiver using one pair of cross-polarized antenna elements, $R_{gNB} = 1$ . + +$$R_{gNB} = \begin{bmatrix} 1 & \alpha \\ \alpha^* & 1 \end{bmatrix}$$ + +For 4-antenna receiver using two pairs of cross-polarized antenna elements, + +$$R_{gNB} = \begin{pmatrix} 1 & \alpha^{1/2} & \alpha^{4/2} & \alpha \\ \alpha^{1/2*} & 1 & \alpha^{1/2} & \alpha^{4/2} \\ \alpha^{4/2*} & \alpha^{1/2*} & 1 & \alpha^{1/2} \\ \alpha^* & \alpha^{4/2*} & \alpha^{1/2*} & 1 \end{pmatrix}$$ + +For 8-antenna receiver using four pairs of cross-polarized antenna elements, + +#### J.2.3.2.3 MIMO correlation matrices using cross polarized antennas + +The values for parameters $\alpha$ , $\beta$ and $\gamma$ for low spatial correlation are given in table J.2.3.2.3-1. + +**Table J.2.3.2.3-1: Values for parameters $\alpha$ , $\beta$ and $\gamma$** + +| Low spatial correlation | | | +|-------------------------|---------|----------| +| $\alpha$ | $\beta$ | $\gamma$ | +| 0 | 0 | 0 | + +NOTE 1: Value of $\alpha$ applies when more than one pair of cross-polarized antenna elements at gNB side. +NOTE 2: Value of $\beta$ applies when more than one pair of cross-polarized antenna elements at UE side. + +The correlation matrices for low spatial correlation are defined in table J.2.3.2.3-2 as below. + +**Table J.2.3.2.3-2: MIMO correlation matrices for low spatial correlation** + +| | | +|----------|-----------------------------| +| 1x8 case | $R_{low} = \mathbf{I}_8$ | +| 2x8 case | $R_{low} = \mathbf{I}_{16}$ | + +In table J.2.3.2.3-2, $\mathbf{I}_d$ is a $d \times d$ identity matrix. + +### J.2.3.2.4 Beam steering approach + +For the 2D cross-polarized antenna array at gNB, given the channel spatial correlation matrix in J.2.3.2.1, J.2.3.2.2 and J.2.3.2.3, the corresponding random channel matrix $H$ can be calculated. The signal model for the $k$ -th slot is denoted as + +And the steering matrix is further expressed as following: + +where + +- $H$ is the $N_r \times N_t$ channel matrix per subcarrier. +- $\mathbf{A}$ is the steering matrix, +- $\mathbf{A}_1$ is the steering matrix in first dimension with same polarization, +- $\mathbf{A}_2$ is the steering matrix in second dimension with same polarization, +- $N_{r1}$ is the number of antenna elements in first dimension with same polarization, +- $N_{r2}$ is the number of antenna elements in second dimension with same polarization, +- For antenna array with only one direction, number of antenna element in second direction equals 1. + +For 1 antenna element with the same polarization in one direction, + +. + +For 2 antenna elements with the same polarization in one direction, + +. + +For 3 antenna elements with the same polarization in one direction, + +. + +For 4 antenna elements with the same polarization in one direction, + +. + +where the index $i$ stands for first dimension and second dimension respectively. + +- controls the phase variation in first dimension and second dimension respectively, and the phase for k-th subframe is denoted by, where is the random start value with the uniform distribution, i.e., , is the step of phase variation, which is defined in Table J.2.3.2.4-1, and k is the linear increment of 2u for every slot throughout the simulation, the index stands for first dimension and second dimension respectively. +- is the precoding matrix for Nt transmission antennas, +- y is the received signal, x is the transmitted signal, and n is AWGN. +- corresponds to subcarrier spacing configuration, + +For the 1D cross-polarized antenna array at gNB, the corresponding random channel matrix H can be calculated by letting N2=1, i.e., + +**Table J.2.3.2.4-1: The step of phase variation** + +| Variation Step | Value (rad/ms) | +|----------------|-------------------------| +| | 1.2566×10 -3 | + +## J.3 Physical signals, channels mapping and precoding + +### J.3.1 General + +Unless otherwise stated, the transmission on antenna port(s) $p = p_0, p_0 + 1, \dots, p_0 + N_p - 1$ is defined by using a precoder matrix of size $N_{ANT} \times N_p$ , where $N_{ANT}$ is the number of physical transmit antenna elements configured per test, $N_p$ is the number of ports for a reference signal or physical channel configured per test, and $p_0$ is the first port for that reference signal or physical channel as defined in clauses 7.3 and 7.4 in TS 38.211 [9]. This precoder takes as an input a block of signals for antenna port(s) $p = p_0, p_0 + 1, \dots, p_0 + N_p - 1$ , $y^{(p)}(i) = [y^{(p_0)}(i) \ y^{(p_0+1)}(i) \ \dots \ y^{(p_0+N_p-1)}(i)]^T$ , with $N$ being the number of modulation symbols per antenna port including the reference signal symbols, and generates a block of signals $y_{bf}^{(q)}(i) = [y_{bf}^{(0)}(i) \ y_{bf}^{(1)}(i) \ \dots \ y_{bf}^{(N_{ANT}-1)}(i)]^T$ the elements of which are to be mapped onto the frequency-time index pair as per the test configuration but transmitted on different physical antenna elements: + +$$y_{bf}^{(q)}(i) = W(i)y^{(p)}(i)$$ + +For Clause 6 and 8, the transmission of PDCCH and PDCCH DMRS on antenna port $p = p_0$ is defined by using a precoder matrix of size 2x1. This precoder takes as an input a block of signals for antenna port(s) $p = p_0$ , + +$y^{(p)}(i) = y^{(p_0)}(i)$ and generates a block of signals $y_{bf}^{(q)}(i) = \begin{bmatrix} y_{bf}^{(0)}(i) & y_{bf}^{(\frac{N_{ANT}}{2})}(i) \end{bmatrix}^T$ the elements of which are to be mapped onto the frequency-time index pair as per the test configuration but transmitted on different physical antenna elements: + +$$y_{bf}^{(q)}(i) = W(i)y^{(p)}(i)$$ + +The precoder matrix is specific to the test case configuration is defined in Clause 5.2.2.2 of TS 38.214 [24]. + +The transmission on PT-RS antenna port is associated (using same precoder) with the lowest indexed DM-RS antenna port among the DM-RS antenna ports assigned for the PDSCH. + +The physical antenna elements are identified by indices, where is the number of physical antenna elements configured per test. + +Modulation symbols $y^{(p)}(i)$ with $p \in \{4000\}$ (i.e. PSS, SSS, PBCH and DM-RS for PBCH) are directly mapped to first physical antenna element. + +Modulation symbols for CSI-RS resources which configured for tracking with one port are directly mapped to first physical antenna element. + +Modulation symbols for CSI-RS resources which configured for beam refinement with one port are directly mapped to first physical antenna element. + +Modulation symbols for NZP CSI-RS which configured for CSI acquisition with $p$ are mapped to the physical antenna index $j = p - p_0$ where $p_0$ is the number of NZP CSI-RS ports configured per test. + +## Annex K (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. For the situation where the noise level is stable, the noise level change can be identified by a relative noise measurement method. This method measures the relative noise change extracted from when the test object is operating and when the power is disconnected. From the two measured noise levels the relative noise change can be determined. 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 the left drawing in figure K-1. + +![Figure K-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, 26) and decreases monotonically, approaching the x-axis as delta_1 increases.](c06522346dd1926105a7273be1069715_img.jpg) + +Figure K-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, 26) and decreases monotonically, approaching the x-axis as delta\_1 increases. + +**Figure K-1: Relative noise measurement** + +The absolute emission level in decibel scale is determined from a relative measurement of $\delta_1$ as: + +where $N_0$ is the noise floor of the measurement receiver and $\delta_2$ is plotted as function of $\delta_1$ at the right in figure K-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 L (normative): In-channel TX tests for IAB-DU + +The Annex H in TS 38.141-2 [6] applies to FR1 and FR2-1 IAB-DU + +--- + +## Annex M (normative): In-channel TX tests for IAB-MT + +### M.0 Applicability + +IAB-MT EVM can be determined by the process according to following alternatives: + +- Alternative 1: Annex E in TS 38.521-1 [28] for FR1 IAB-MT and Annex E in TS 38.521-2 [29] for FR2-1 IAB-MT . Only CP-OFDM waveform of PUSCH is measured for IAB-MT; or +- Alternative 2: from Annex M.1 to Annex M.7. + +--- + +### M.1 General + +The in-channel TX test enables the measurement of all relevant parameters that describe the In-channel quality of the output signal of the TX under test in a single measurement process. + +The parameters describing the in-channel quality of a transmitter, however, are not necessarily independent. The algorithm chosen for description inside this annex places particular emphasis on the exclusion of all interdependencies among the parameters. + +--- + +### M.2 Basic principles + +The process is based on the comparison of the actual output signal of the TX under test, received by an ideal receiver, with an ideal signal, that is generated by the measuring equipment and represents an ideal error free received signal. All signals are represented as equivalent (generally complex) baseband signals. + +The description below uses numbers and illustrations as examples only. These numbers are taken from a TDD frame structure with normal CP length, 120 kHz SCS and a transmission bandwidth configuration of 400 MHz ( $N_{RB} = 264$ ). The application of the text below, however, is not restricted to this parameter set. + +#### M.2.1 Output signal of the TX under test + +The output signal of the TX under test is acquired by the measuring equipment and stored for further processing. It is sampled at a sampling rate which is the product of the SCS and the *FFT size*, and it is named . + +For FR1, *FFT size* is determined by the transmission bandwidth in TS 38.176-1 [3] table 6.5.3.5-2 for 15 kHz SCS, table 6.5.3.5-3 for 30 kHz SCS and table 6.5.3.5-4 for 60 kHz SCS. + +For FR2, *FFT size* is determined by the transmission bandwidth in table 6.6.3.5.2-2 for 60 kHz SCS, and table 6.6.3.5.2-3 for 120 kHz SCS. In the time domain it comprises at least 10 ms. It is modelled as a signal with the following parameters: + +- demodulated data content, +- carrier frequency, +- amplitude and phase for each subcarrier. + +For the example in the annex, the *FFT size* is 4096 based on table 6.6.3.5.2-3. The sampling rate of 491.52 Msps is the product of the *FFT size* and SCS. + +## M.2.2 Ideal signal + +Two types of ideal signals are defined: + +The first ideal signal is constructed by the measuring equipment according to the relevant TX specifications, using the following parameters: + +- demodulated data content, +- nominal carrier frequency, +- nominal amplitude and phase for each subcarrier. + +It is represented as a sequence of samples at the sampling rate determined from annex M.2.1 in the time domain. The structure of the signal is described in the test models. + +The second ideal signal is constructed by the measuring equipment according to the relevant TX specifications, using the following parameters for FR1 and FR2: + +- nominal demodulation reference signal and nominal PT-RS if present (all other modulation symbols are set to 0 V), +- nominal carrier frequency, +- nominal amplitude and phase for each applicable subcarrier, +- nominal timing. + +It is represented as a sequence of samples at the sampling rate determined from annex M.2.1 in the time domain. + +## M.2.3 Measurement results + +The measurement results, achieved by the in-channel TX test are the following: + +- Carrier frequency error. +- EVM. +- Resource element TX power. +- OFDM symbol TX power (OSTP). + +Other side results are: residual amplitude- and phase response of the TX chain after equalisation. + +## M.2.4 Measurement points + +The resource element TX power is measured after the FFT box as described in figure M.2.4-1 for FR1 and in figure M.2.4.2. The EVM shall be measured at the point after the FFT and a zero-forcing (ZF) equalizer in the receiver, as depicted in for FR1 in figure M.2.4-1 and for FR2-1 in figure M.2.4-2. The FFT window of *FFT size* samples out of (*FFT size* + cyclic prefix length) samples in the time domain is selected in the "Remove CP" box. + +For FR1, The *FFT size* and the cyclic prefix length are obtained from TS 38.176-1 [3] table 6.5.3.5-2 for 15 kHz SCS, table 6.5.3.5-3 for 30 kHz SCS and table 6.5.3.5-4 for 60 kHz SCS. + +For FR2-1, *FFT size* and the cyclic prefix length is determined from table 6.6.3.5.2-2 for 60 kHz SCS, and table 6.6.3.5.2-3 for 120 kHz SCS. + +In one subframe, there are two symbols with the length of the cyclic prefix larger than the values listed in TS 38.176-1 [3] tables 6.5.3.5-2, 6.5.3.5-3 and 6.5.3.5-4 for FR1 and table 6.6.3.5.2-2 and table 6.6.3.5.2-3 for FR2-1. Table M.2.4-1 lists the slot number and the symbol number and the formula how to compute the length of cyclic prefix for those two symbols according to the sampling rate. + +**Table M.2.4-1: Slot number and symbol number identifying the longer CP length for normal CP** + +| SCS (kHz) | Frequency Range | # slots in subframe | Symbol # and slot # with longer CP | Longer CP length | +|-----------|-----------------|---------------------|------------------------------------------|-------------------------------| +| 15 | FR1 | 1 | (symbol 0, slot 0)
(symbol 7, slot 0) | CP length + $FFT\ size / 128$ | +| 30 | | 2 | (symbol 0, slot 0)
(symbol 0, slot 1) | CP length + $FFT\ size / 64$ | +| 60 | | 4 | (symbol 0, slot 0)
(symbol 0, slot 2) | CP length + $FFT\ size / 32$ | +| 60 | FR2-1 | 4 | (symbol 0, slot 0)
(symbol 0, slot 2) | CP length + $FFT\ size / 32$ | +| 120 | | 8 | (symbol 0, slot 0)
(symbol 0, slot 4) | CP length + $FFT\ size / 16$ | + +For the example used in the annex, the "Remove CP" box selects 4096 samples out of 4384 samples. Symbol 0 of slot 0 and slot 4 has 256 more samples in the cyclic prefix than the other symbols (the longer CP length = 544). + +![Block diagram showing the signal processing flow for FR1 EVM measurements. The flow starts with IAB-MT TX, followed by Remove CP, FFT, Per-subcarrier Amplitude/phase correction, and Symbol detection/decoding. A Pre-/post FFT time / frequency synchronization block is connected to the Remove CP, FFT, and Per-subcarrier Amplitude/phase correction blocks. A Reference point for EVM measurement is indicated below the Per-subcarrier Amplitude/phase correction block.](8c43614237e5bb57f1d5cf614291b32e_img.jpg) + +``` + +graph LR + TX[IAB-MT TX] --> RemoveCP[Remove CP] + RemoveCP --> FFT[FFT] + FFT --> PerSubcarrier[Per-subcarrier Amplitude/phase correction] + PerSubcarrier --> Detection[Symbol detection/decoding] + Sync[Pre-/post FFT time / frequency synchronization] -.-> RemoveCP + Sync -.-> FFT + Sync -.-> PerSubcarrier + Ref[Reference point for EVM measurement] -.-> PerSubcarrier + +``` + +Block diagram showing the signal processing flow for FR1 EVM measurements. The flow starts with IAB-MT TX, followed by Remove CP, FFT, Per-subcarrier Amplitude/phase correction, and Symbol detection/decoding. A Pre-/post FFT time / frequency synchronization block is connected to the Remove CP, FFT, and Per-subcarrier Amplitude/phase correction blocks. A Reference point for EVM measurement is indicated below the Per-subcarrier Amplitude/phase correction block. + +**Figure M.2.4-1: Reference point for FR1 EVM measurements** + +![Figure M.2.4-2: Reference point for FR2-1 EVM measurements. The diagram shows a signal processing flow: IAB-MT TX -> Remove CP -> FFT -> Per-subcarrier Amplitude/phase and CPE correction -> Symbol detection/decoding. A 'Pre-/post FFT time / frequency synchronization' block is connected to the 'Remove CP', 'FFT', and 'Per-subcarrier' blocks. A 'Reference point for EVM measurement' block is connected to the 'Symbol detection/decoding' block.](9b33f26612e373d186f5199dc2c83400_img.jpg) + +``` + +graph LR + TX[IAB-MT TX] --> CP[Remove CP] + CP --> FFT[FFT] + FFT --> CPE[Per-subcarrier Amplitude/phase and CPE correction] + CPE --> SD[Symbol detection/decoding] + Sync[Pre-/post FFT time / frequency synchronization] -.-> CP + Sync -.-> FFT + Sync -.-> CPE + Ref[Reference point for EVM measurement] -.-> SD + +``` + +Figure M.2.4-2: Reference point for FR2-1 EVM measurements. The diagram shows a signal processing flow: IAB-MT TX -> Remove CP -> FFT -> Per-subcarrier Amplitude/phase and CPE correction -> Symbol detection/decoding. A 'Pre-/post FFT time / frequency synchronization' block is connected to the 'Remove CP', 'FFT', and 'Per-subcarrier' blocks. A 'Reference point for EVM measurement' block is connected to the 'Symbol detection/decoding' block. + +Figure M.2.4-2: Reference point for FR2-1 EVM measurements + +## M.3 Pre-FFT minimization process + +Sample timing, carrier frequency in are varied in order to minimise the difference between and , after the amplitude ratio of and has been scaled. Best fit (minimum difference) is achieved when the RMS difference value between and is an absolute minimum. + +The carrier frequency variation is the measurement result: carrier frequency error. + +From the acquired samples, one value of carrier frequency error can be derived. + +NOTE 1: The minimisation process, to derive the RF error can be supported by post-FFT operations. However the minimisation process defined in the pre-FFT domain comprises all acquired samples (i.e. it does not exclude the samples in-between the FFT widths and it does not exclude the bandwidth outside the transmission bandwidth configuration). + +NOTE 2: The algorithm would allow to derive carrier frequency error and sample frequency error of the TX under test separately. However there are no requirements for sample frequency error. Hence the algorithm models the RF and the sample frequency commonly (not independently). It returns one error and does not distinguish between both. + +After this process the samples are called . + +## M.4 Timing of the FFT window + +The FFT window length is *FFT size* samples per OFDM symbol. For TDD, the number of FFTs performed is the number of uplink symbols in the measurement interval. + +The position in time for the FFT shall be determined. + +In an ideal signal, the FFT may start at any instant within the cyclic prefix without causing an error. The TX filter, however, reduces the window. The EVM requirements shall be met within a window $W < CP$ . There are three different instants for FFT: + +- Centre of the reduced window, called , + +- , and +- . + +The value of EVM window length $W$ is obtained from the transmission bandwidth and TS 38.176-1 [3] table 6.5.3.5-2 for 15 kHz SCS, table 6.5.3.5-3 for 30 kHz SCS and table 6.5.3.5-4 for 60 kHz SCS for FR1, and table 6.6.3.5.2-2 for 60 kHz SCS, and table 6.6.3.5.2-3 for 120 kHz SCS for FR2-1. + +The IAB-MT shall transmit a signal according to the test models intended for EVM. The demodulation reference signal of the second ideal signal shall be used to find the centre of the FFT window. + +The timing of the measured signal is determined in the pre FFT domain as follows, using $\Delta$ and $\Delta_{CP}$ : + +1. The measured signal is delay spread by the TX filter. Hence the distinct borders between the OFDM symbols and between data and CP are also spread and the timing is not obvious. +2. In the ideal signal $\Delta$ , the timing is known. +Correlation between bullet (1) and (2) will result in a correlation peak. The meaning of the correlation peak is approximately the "impulse response" of the TX filter. +3. The meaning of "impulse response" assumes that the autocorrelation of the ideal signal $\Delta$ is a Dirac peak and that the correlation between the ideal signal $\Delta$ and the data in the measured signal is 0. The correlation peak, (the highest, or in case of more than one highest, the earliest) indicates the timing in the measured signal. + +The number of samples, used for FFT is reduced compared to $N_{sym}$ . This subset of samples is called $N_{FFT}$ . + +From the acquired samples one timing can be derived. + +The timing of the centre $\Delta$ is determined according to the cyclic prefix length of the OFDM symbols. For normal CP, there are two values for $\Delta$ in a 1 ms period: + +- $\Delta = \text{length of cyclic prefix} / 2$ , +- $\Delta = \text{Longer CP length} - \text{length of cyclic prefix} / 2$ , + +Where the length of cyclic prefix is obtained from TS 38.176-1 [3] table 6.5.3.5-2 for 15 kHz SCS, table 6.5.3.5-3 for 30 kHz SCS and table 6.5.3.5-4 for 60 kHz SCS for FR1, and table 6.6.3.5.2-2 for 60 kHz SCS, and table 6.6.3.5.2-3 for 120 kHz SCS for FR2-1, and the longer CP length is obtained from table M.2.4-1. + +As per the example values. + +- $\Delta$ within the CP of length 288 for most OFDM symbols in 1 ms, +- $\Delta (= 544 - 144)$ within the CP of length 544 for OFDM symbol 0 of slot 0 and slot 4. + +## M.5 Resource element TX power + +Perform FFT on $\Delta$ with the FFT window timing $\Delta$ . + +The result is called $\Delta$ . The RE TX (RETP) power is then defined as: + +where SCS is the subcarrier spacing in Hz. + +From RETP, the OFDM symbol TX power (OSTP) is derived as follows: + +Where the summation accumulates values of all $N_{sym}$ OFDM symbols that carry PUSCH and not containing PUCCH, SRS or PRACH within a slot. + +For TDD, $N_{\text{slots}}$ is the number of slots with downlink symbols in a 10 ms measurement interval and is computed according to the values in table 4.9.2.2-1. + +For the example used in the annex, $N_{\text{slots}} = 1120$ . + +## M.6 Post-FFT equalisation + +Perform FFTs on $s(t)$ , one for each OFDM symbol within 10 ms measurement interval with the FFT window timing to produce an array of samples, $S(f)$ , in the time axis $t$ by *FFT size* in the frequency axis $f$ . + +For the example in the annex, 1120 FFTs are performed on $s(t)$ . The result is an array of samples, 1120 in the time axis by 4096 in the frequency axis. + +The equalizer coefficients $\hat{h}(f)$ and $\hat{\phi}(f)$ are determined as follows: + +1. Calculate the complex ratios (amplitude and phase) of the post-FFT acquired signal $S(f)$ and the post-FFT ideal signal $S_{\text{ideal}}(f)$ , for each demodulation reference signal, over 10 ms measurement interval. This process creates a set of complex ratios: +2. Perform time averaging at each demodulation reference signal subcarrier of the complex ratios, the time-averaging length is 10 ms measurement interval. Prior to the averaging of the phases an unwrap operation must be performed according to the following definition: + - The unwrap operation corrects the radian phase angles of $\hat{\phi}(f)$ by adding multiples of $2 * \pi$ when absolute phase jumps between consecutive time instances are greater than or equal to the jump tolerance of $\pi$ radians. + - This process creates an average amplitude and phase for each demodulation reference signal subcarrier (i.e. every second subcarrier). + +Where $N$ is the number of demodulation reference signal time-domain locations from $s(t)$ for each demodulation reference signal subcarrier $f$ . + +3. The equalizer coefficients for amplitude $\hat{h}(f)$ and phase $\hat{\phi}(f)$ at the demodulation reference signal subcarriers are obtained by computing the moving average in the frequency domain of the time-averaged demodulation reference signal subcarriers. The moving average window size is 19 and averaging is over the DM-RS subcarriers in the allocated RBs. For DM-RS subcarriers at or near the edge of the channel, or when the number of available DM-RS subcarriers within a set of contiguously allocated RBs is smaller than the moving average window size, the window size is reduced accordingly as per figure M.6-1. +4. Perform linear interpolation from the equalizer coefficients $\hat{h}(f)$ and $\hat{\phi}(f)$ to compute coefficients $\tilde{h}(f)$ and $\tilde{\phi}(f)$ , for each subcarrier. + +![Figure M.6-1: Reference subcarrier smoothing in the frequency domain. The figure contains two diagrams, A and B, and a descriptive text block. Diagram A, titled 'Moving averaging at channel edge', shows a series of vertical arrows representing reference subcarriers. The first arrow is labeled 'The first reference subcarrier is not averaged'. The second arrow is labeled 'The second reference subcarrier is the average of the first three subcarriers'. A group of arrows is labeled 'The subsequent 7 subcarriers are averaged over 5, 7 .. 17 subcarriers'. The final arrows are labeled 'From the 10th subcarrier onwards the window size is 19 until the upper edge of the channel is reached and the window size reduces back to 1'. Diagram B, titled 'Moving averaging for the case when the number of available reference subcarriers within a set of contiguously allocated RBs is smaller than the moving average window size', shows a smaller group of five arrows. The first, second, and third arrows are labeled 'The first, second and third reference subcarriers are the average of the five subcarriers on left'. The fourth and fifth arrows are labeled 'The first, second and third reference subcarriers are the average of the five subcarriers on right'. A text block to the right of the diagrams states: 'Figure B shows an example of 1RB allocation using a reduced window size of five subcarriers for averaging. The same method applies for RB allocations with fewer than 19 subcarriers available for the moving average size. For the case of 2 and 3 RB allocations, 11 and 17 are the window sizes, respectively.'](013c7ae7b0f9a1da5881cce6ab610a7c_img.jpg) + +Figure M.6-1: Reference subcarrier smoothing in the frequency domain. The figure contains two diagrams, A and B, and a descriptive text block. Diagram A, titled 'Moving averaging at channel edge', shows a series of vertical arrows representing reference subcarriers. The first arrow is labeled 'The first reference subcarrier is not averaged'. The second arrow is labeled 'The second reference subcarrier is the average of the first three subcarriers'. A group of arrows is labeled 'The subsequent 7 subcarriers are averaged over 5, 7 .. 17 subcarriers'. The final arrows are labeled 'From the 10th subcarrier onwards the window size is 19 until the upper edge of the channel is reached and the window size reduces back to 1'. Diagram B, titled 'Moving averaging for the case when the number of available reference subcarriers within a set of contiguously allocated RBs is smaller than the moving average window size', shows a smaller group of five arrows. The first, second, and third arrows are labeled 'The first, second and third reference subcarriers are the average of the five subcarriers on left'. The fourth and fifth arrows are labeled 'The first, second and third reference subcarriers are the average of the five subcarriers on right'. A text block to the right of the diagrams states: 'Figure B shows an example of 1RB allocation using a reduced window size of five subcarriers for averaging. The same method applies for RB allocations with fewer than 19 subcarriers available for the moving average size. For the case of 2 and 3 RB allocations, 11 and 17 are the window sizes, respectively.' + +**Figure M.6-1: Reference subcarrier smoothing in the frequency domain** + +- a) In case of FR2-1 EVM, to account for the common phase error (CPE) experienced in millimetre wave frequencies, , in the estimated coefficients contain phase rotation due to the CPE, , in addition to the phase of the equalizer coefficient , that is: + +For OFDM symbols where PT-RS does not exist, can be estimated by performing linear interpolation from neighboring symbols where PT-RS is present. + +In order to separate component of the CPE,, contained in, , estimation and compensation of the CPE needs to follow. is the common phase error (CPE), that rotates all the subcarriers of the OFDM symbol at time . + +Estimate of the CPE , at OFDM symbol time, , can then be obtained from using the PT-RS employing the expression: + +In the above equation, is the set of subcarriers where PT-RS are mapped, where is the set of OFDM symbols where PT-RS are mapped while and are the post-FFT acquired signal and the ideal PT-RS signal respectively. That is, estimate of the CPE at a given OFDM symbol is obtained from frequency correlation of the complex ratios at the PT-RS positions with the conjugate of the estimated equalizer complex coefficients. The estimated CPE can be subtracted from to remove influence of the CPE, and obtain estimate of the complex coefficient's phase: + +(t) + +## M.7 EVM + +### M.7.0 General + +For EVM create two sets of $s$ , according to the timing $t$ and $i$ , using the equalizer coefficients from M.6. + +The equivalent ideal samples are calculated from (annex M.2.2) and are called $s_{ideal}$ . + +The EVM is the difference between the ideal signal and the equalized measured signal. + +Where: + +- $T$ is the set of symbols with the considered modulation scheme being active within the slot, +- $i$ is the set of subcarriers within the resource blocks with the considered modulation scheme being active in symbol $t$ , +- $s_{ideal}$ is the ideal signal reconstructed by the measurement equipment in accordance with relevant test models, +- $s$ is the equalized signal under test. + +NOTE: Although the basic unit of measurement is one slot, the equalizer is calculated over the entire 10 ms measurement interval to reduce the impact of noise in the reference signals. + +### M.7.1 Averaged EVM (TDD) + +Let $N$ be the number of slots with uplink symbols within a 10 ms measurement interval. For TDD, the averaging in the time domain can be calculated from slots of different 10 ms measurement intervals and should have a minimum of $N$ slots averaging length where $N$ is the number of slots in a 10 ms measurement interval. + +$EVM_{RMS}$ is derived by: Square the EVM results in each 10 ms measurement interval. Sum the squares, divide the sum by the number of EVM relevant locations, square-root the quotient (RMS). + +Where $N$ is the number of resource blocks with the considered modulation scheme in slot $i$ . + +The $EVM_{RMS}$ is calculated, using the maximum of $EVM$ at the window $W$ extremities. Thus $EVM$ is calculated using $s$ and $s_{ideal}$ using ( $l$ and $h$ , low and high; where low is the timing $t$ and high is the timing $t$ ). + +In order to unite at least $N$ slots, consider the minimum integer number of 10 ms measurement intervals, where $N$ is determined by + +And for FR1, $N$ for 15 kHz SCS, $N$ for 30 kHz SCS and $N$ for 60 kHz SCS normal CP. For FR2, $N$ for 60 kHz SCS and $N$ for 120 kHz SCS. + +Unite by RMS. + +The resulting $EVM_{RMS}$ is compared against the limit. + +--- + +**Annex N (normative):** +**General rules for statistical testing** + +--- + +**Annex O (informative):** +**Change history** + +| Change history | | | | | | | | | +|----------------|--------------|------------|------|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2021-04 | RAN4#98bis-e | R4-2106313 | | | | TS skeleton | | 0.0.1 | +| 2021-05 | RAN4#99-e | R4-2110944 | | | | TS 38.176-2 skeleton after RAN4#98bis-e

Update of IAB conducted conformance TS with agreed TP in RAN4#98bis-e:
1. R4-2106057 TP to TS 38.xxx-2: Clause 4.2-4.5
2. R4-2106055 TP to TS38.176-2 on subclause 4.10 -5
3. R4-2106073 TP for TS 38.176-2: OTA transmit ON/OFF power
4. R4-2106076 TP to TS 38.xxx-2: TX IMD requirements
5. R4-2106077 TP to TS 38.176-2 Annex A for IAB OTA test specification
6. R4-2106078 TP to TS 38.xxx-2: RX IMD requirements
7. R4-2106080 TP to TS 38.176-2 - OTA Sensitivity, clause 7.2, 7.3
8. R4-2106081 TP to TS 38.176-2 - OTA Rx dynamic range, clause 7.3
9. R4-2106082 TP on IBB, OBB and RX spurious for OTA receiver characteristic test
10. R4-2106083 TP to TS 38.146-2 Clause 4.6 Declarations for IAB radiated test specification
11. R4-2106084 TP to TS 38.176-2 - Annex D&E
12. R4-2106051 TP for Annex G and H for OTA IAB test specification | | 0.1.0 | +| 2021-06 | RAN4#99-e | R4-2108096 | | | | Big TP to 38.176-2 on RF part

Update of IAB conducted conformance TS with endorsed TP in RAN4#99-e:
1. R4-2108566 TP to TS 38.176-2 on test efficiency clause 4.13
2. R4-2108570 TP for TS 38.176-2: Test configurations and applicability of requirements
3. R4-2108568 TP to TS 38.176-2:IAB Common test issue on test model-OTA
4. R4-2108572 TP for TS 38.176-2: Annex B and C
5. R4-2108574 TP to TS 38.176-2 -Clause 4.1
7. R4-2108578 TP to 38.176-2 Editor update – editorials
8. R4-2108579 TP for TS 38.176-2: OTA transmitted signal quality
9. R4-2108580 TP to TS 38.176-2: clauses 6.1, 6.2, 6.3 and 6.7
10. R4-2108088 TP to TS 38.176-2 - OTA Tx dynamic range, clause 6.4
11. R4-2110608 TP to TS 38.176-2: RX ICS requirements, ZTE
12. R4-2111178 TP on IBB, OBB and RX spurious for OTA receiver characteristic test
13. R4-2111406 TP to TS 38.176-2 - OTA Sensitivity, clause 7.2, 7.3
14. R4-2108583 TP to TS 38.176-2 Clause 4.6 Declarations for IAB radiated test specification
15. R4-2108584 TP to TS38.176-2 on Annex I and Annex K
16. R4-2108585 TP to TS 38.176-2: Annex L and M: In-channel TX test
17. R4-2108586 TP to TS 38.176-2 – Clause 3
18. R4-2108587 IAB-MT specific declaration FR2 | | 0.2.0 | +| 2021-06 | RAN#92-e | RP-211312 | | | | Presented to TSG RAN for approval.
(Including RF and Demod parts:
R4-2108096, Big TP to TS 38.176-2 on RF part
R4-2111396, Big TP draft to TS 38.176-2 Demodulation performance) | | 1.0.0 | +| 2021-06 | RAN#92 | | | | | TS was approved by RAN plenary | | 16.0.0 | +| 2021-09 | RAN#93 | RP-211892 | 0002 | | F | Big CR for TS 38.176-2 Maintenance (Rel-16, CAT F) | | 16.1.0 | +| 2021-12 | RAN#94 | RP-212851 | 0003 | | F | Big CR for TS 38.176-2 Maintenance (Rel-16, CAT F) | | 16.2.0 | +| 2022-03 | RAN#95 | RP-220334 | 0005 | | F | Big CR for TS 38.176-2 Maintenance (Rel-16, CAT F) | | 16.3.0 | + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-03 | RAN#95 | | | | | Approved by plenary – Rel-17 spec under change control | 17.0.0 | +| 2022-06 | RAN#96 | RP-221673 | 0006 | | B | CR to TS 38.176-2 - Introduction of licensed 6GHz band n104 | 17.1.0 | +| 2022-06 | RAN#96 | RP-221665 | 0008 | | F | Big CR for TS 38.176-2 Maintenance (Rel-17, CAT F) | 17.1.0 | +| 2022-09 | RAN#97 | RP-222049 | 0013 | | B | Big CR for TS 38.176-2 (Rel-17, CAT B) | 17.2.0 | +| 2022-12 | RAN#98-e | RP-223310 | 0014 | | F | CR on eIAB performance -general requirement -38.176-2 | 17.3.0 | +| 2023-03 | RAN#99 | RP-230515 | 0016 | | A | CR to TS 38.176-2 with updates to OTA modulation quality | 17.4.0 | +| 2023-03 | RAN#99 | RP-230515 | 0017 | | F | CR to TS 38.176-2 with bracket removal for measurement uncertainties for OTA timing error between IAB-DU and IAB-MT | 17.4.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-03 | RAN#99 | RP-230535 | 0018 | | B | CR to 38.176-2 on introduction of Band n54 | 18.0.0 | +| 2023-03 | RAN#99 | RP-230533 | 0019 | | B | CR to TS 38.176-2: Introduction of NR band n105 | 18.0.0 | +| 2023-06 | RAN#100 | RP-231353 | 0021 | | A | CR to TS 38.176-2: Addition of missing bands for IAB co-existence and co-location requirements | 18.1.0 | +| 2023-06 | RAN#100 | RP-231353 | 0024 | | A | Clean up for IAB demodulation conformance testing in TS 38.176-2 (Rel-18) | 18.1.0 | +| 2023-06 | RAN#100 | RP-231353 | 0026 | | A | CR to TS 38.176-2 Maintenance of IAB for supported BW R18 | 18.1.0 | +| 2023-09 | RAN#101 | RP-232491 | 0033 | | F | [NR_IAB-Perf] CR on NR IAB performance requirements (TS38.176-2, Rel-18) | 18.2.0 | +| 2023-12 | RAN#102 | RP-233338 | 0036 | | A | CR for TS 38.176-2, Correction on scaling factor for IAB-DU type 1-O | 18.3.0 | +| 2023-12 | RAN#102 | RP-233366 | 0037 | | B | CR to TS38.176-2: introduction of NR bands n31 and n72 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233366 | 0038 | | B | CR to TS38.176-2: introduction of band n106 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233347 | 0039 | | F | CR to TS 38.176-2 with correction of co-existence and co-location requirements | 18.3.0 | +| 2023-12 | RAN#102 | RP-233366 | 0041 | | B | CR to 38.176-2 on introduction of Band n109 | 18.3.0 | +| 2023-12 | RAN#102 | RP-233347 | 0043 | | A | CR to update FR2 range in IAB specification | 18.3.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38212/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38212/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bfa19a3924bea77884784716fed1fab2bd789ec --- /dev/null +++ b/marked/Rel-18/38_series/38212/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a42531e878a9547fcce2d08f472ff3e0a57fff4cfba77c3b6ab40618e0f96ab +size 9575 diff --git a/marked/Rel-18/38_series/38212/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38212/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b776e1bac7ae08c7e7fd94a7062145c9d9d0869f --- /dev/null +++ b/marked/Rel-18/38_series/38212/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5fb2f682f8f29570127df0536a9de8246f9f5f693b7f244cacf3d3b2f3a480ea +size 5702 diff --git a/marked/Rel-18/38_series/38212/raw.md b/marked/Rel-18/38_series/38212/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f9779d51735060adb515c903b3625187afec0dd0 --- /dev/null +++ b/marked/Rel-18/38_series/38212/raw.md @@ -0,0 +1,10531 @@ + + +# 3GPP TS 38.212 V18.1.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Multiplexing and channel coding (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 '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. + +© 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 of terms, symbols and abbreviations..... | 8 | +| 3.1 Terms..... | 8 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations..... | 9 | +| 4 Mapping to physical channels..... | 10 | +| 4.1 Uplink..... | 10 | +| 4.2 Downlink..... | 10 | +| 4.3 Sidelink..... | 10 | +| 5 General procedures..... | 11 | +| 5.1 CRC calculation..... | 11 | +| 5.2 Code block segmentation and code block CRC attachment..... | 12 | +| 5.2.1 Polar coding..... | 12 | +| 5.2.2 Low density parity check coding..... | 12 | +| 5.3 Channel coding..... | 14 | +| 5.3.1 Polar coding..... | 15 | +| 5.3.1.1 Interleaving..... | 15 | +| 5.3.1.2 Polar encoding..... | 16 | +| 5.3.2 Low density parity check coding..... | 19 | +| 5.3.3 Channel coding of small block lengths..... | 24 | +| 5.3.3.1 Encoding of 1-bit information..... | 24 | +| 5.3.3.2 Encoding of 2-bit information..... | 25 | +| 5.3.3.3 Encoding of other small block lengths..... | 25 | +| 5.4 Rate matching..... | 26 | +| 5.4.1 Rate matching for Polar code..... | 26 | +| 5.4.1.1 Sub-block interleaving..... | 26 | +| 5.4.1.2 Bit selection..... | 27 | +| 5.4.1.3 Interleaving of coded bits..... | 28 | +| 5.4.2 Rate matching for LDPC code..... | 29 | +| 5.4.2.1 Bit selection..... | 29 | +| 5.4.2.2 Bit interleaving..... | 32 | +| 5.4.3 Rate matching for channel coding of small block lengths..... | 32 | +| 5.5 Code block concatenation..... | 33 | +| 6 Uplink transport channels and control information..... | 33 | +| 6.1 Random access channel..... | 33 | +| 6.2 Uplink shared channel..... | 33 | +| 6.2.1 Transport block CRC attachment..... | 33 | +| 6.2.2 LDPC base graph selection..... | 34 | +| 6.2.3 Code block segmentation and code block CRC attachment..... | 34 | +| 6.2.4 Channel coding of UL-SCH..... | 34 | +| 6.2.5 Rate matching..... | 34 | +| 6.2.6 Code block concatenation..... | 35 | +| 6.2.7 Data and control multiplexing..... | 35 | +| 6.3 Uplink control information..... | 46 | +| 6.3.1 Uplink control information on PUCCH..... | 46 | +| 6.3.1.1 UCI bit sequence generation..... | 47 | +| 6.3.1.1.1 HARQ-ACK/SR only..... | 47 | +| 6.3.1.1.2 CSI only..... | 47 | +| 6.3.1.1.3 HARQ-ACK/SR and CSI..... | 65 | +| 6.3.1.1.4 UCI with different priority indexes..... | 66 | +| 6.3.1.2 Code block segmentation and CRC attachment..... | 66 | +| 6.3.1.2.1 UCI encoded by Polar code..... | 66 | + +| | | | +|------------|-------------------------------------------------------------------------------------------|-----| +| 6.3.1.2.2 | UCI encoded by channel coding of small block lengths..... | 67 | +| 6.3.1.3 | Channel coding of UCI..... | 67 | +| 6.3.1.3.1 | UCI encoded by Polar code..... | 67 | +| 6.3.1.3.2 | UCI encoded by channel coding of small block lengths..... | 67 | +| 6.3.1.4 | Rate matching..... | 67 | +| 6.3.1.4.1 | UCI encoded by Polar code..... | 67 | +| 6.3.1.4.2 | UCI encoded by channel coding of small block lengths..... | 68 | +| 6.3.1.4.3 | UCI with different priority indexes encoded by Polar code..... | 69 | +| 6.3.1.4.4 | UCI with different priority indexes encoded by channel coding of small block lengths..... | 69 | +| 6.3.1.5 | Code block concatenation..... | 69 | +| 6.3.1.6 | Multiplexing of coded UCI bits to PUCCH..... | 70 | +| 6.3.2 | Uplink control information on PUSCH..... | 72 | +| 6.3.2.1 | UCI bit sequence generation..... | 72 | +| 6.3.2.1.1 | HARQ-ACK..... | 72 | +| 6.3.2.1.2 | CSI..... | 73 | +| 6.3.2.1.3 | CG-UCI..... | 95 | +| 6.3.2.1.3A | UTO-UCI..... | 96 | +| 6.3.2.1.4 | HARQ-ACK and CG-UCI/UTO-UCI..... | 96 | +| 6.3.2.1.5 | UCI with different priority indexes..... | 97 | +| 6.3.2.2 | Code block segmentation and CRC attachment..... | 99 | +| 6.3.2.2.1 | UCI encoded by Polar code..... | 99 | +| 6.3.2.2.2 | UCI encoded by channel coding of small block lengths..... | 99 | +| 6.3.2.3 | Channel coding of UCI..... | 99 | +| 6.3.2.3.1 | UCI encoded by Polar code..... | 99 | +| 6.3.2.3.2 | UCI encoded by channel coding of small block lengths..... | 99 | +| 6.3.2.4 | Rate matching..... | 99 | +| 6.3.2.4.1 | UCI encoded by Polar code..... | 99 | +| 6.3.2.4.2 | UCI encoded by channel coding of small block lengths..... | 113 | +| 6.3.2.5 | Code block concatenation..... | 116 | +| 6.3.2.6 | Multiplexing of coded UCI bits to PUSCH..... | 116 | +| 6.3.2.7 | Multiplexing of coded UCI bits with different priority indexes to PUSCH..... | 116 | +| 7 | Downlink transport channels and control information..... | 117 | +| 7.1 | Broadcast channel..... | 117 | +| 7.1.1 | PBCH payload generation..... | 117 | +| 7.1.2 | Scrambling..... | 118 | +| 7.1.3 | Transport block CRC attachment..... | 119 | +| 7.1.4 | Channel coding..... | 119 | +| 7.1.5 | Rate matching..... | 120 | +| 7.2 | Downlink shared channel and paging channel..... | 120 | +| 7.2.1 | Transport block CRC attachment..... | 120 | +| 7.2.2 | LDPC base graph selection..... | 120 | +| 7.2.3 | Code block segmentation and code block CRC attachment..... | 120 | +| 7.2.4 | Channel coding..... | 120 | +| 7.2.5 | Rate matching..... | 121 | +| 7.2.6 | Code block concatenation..... | 121 | +| 7.3 | Downlink control information..... | 121 | +| 7.3.1 | DCI formats..... | 121 | +| 7.3.1.0 | DCI size alignment..... | 123 | +| 7.3.1.0.1 | DCI size alignment for DCI formats for scheduling of sidelink..... | 126 | +| 7.3.1.1 | DCI formats for scheduling of PUSCH..... | 126 | +| 7.3.1.1.1 | Format 0_0..... | 126 | +| 7.3.1.1.2 | Format 0_1..... | 130 | +| 7.3.1.1.3 | Format 0_2..... | 202 | +| 7.3.1.1.4 | Format 0_3..... | 214 | +| 7.3.1.2 | DCI formats for scheduling of PDSCH..... | 224 | +| 7.3.1.2.1 | Format 1_0..... | 224 | +| 7.3.1.2.2 | Format 1_1..... | 228 | +| 7.3.1.2.3 | Format 1_2..... | 254 | +| 7.3.1.2.4 | Format 1_3..... | 259 | +| 7.3.1.3 | DCI formats for other purposes..... | 268 | +| 7.3.1.3.1 | Format 2_0..... | 268 | + +| | | | +|-------------------------------|---------------------------------------------------------------------|------------| +| 7.3.1.3.2 | Format 2_1..... | 268 | +| 7.3.1.3.3 | Format 2_2..... | 268 | +| 7.3.1.3.4 | Format 2_3..... | 269 | +| 7.3.1.3.5 | Format 2_4..... | 270 | +| 7.3.1.3.6 | Format 2_5..... | 270 | +| 7.3.1.3.7 | Format 2_6..... | 270 | +| 7.3.1.3.8 | Format 2_7..... | 270 | +| 7.3.1.3.9 | Format 2_8..... | 271 | +| 7.3.1.3.10 | Format 2_9..... | 271 | +| 7.3.1.4 | DCI formats for scheduling of sidelink..... | 272 | +| 7.3.1.4.1 | Format 3_0..... | 272 | +| 7.3.1.4.2 | Format 3_1..... | 273 | +| 7.3.1.4.3 | Format 3_2..... | 273 | +| 7.3.1.5 | DCI formats for scheduling of MBS..... | 274 | +| 7.3.1.5.1 | Format 4_0..... | 274 | +| 7.3.1.5.2 | Format 4_1..... | 274 | +| 7.3.1.5.3 | Format 4_2..... | 275 | +| 7.3.2 | CRC attachment..... | 277 | +| 7.3.3 | Channel coding..... | 277 | +| 7.3.4 | Rate matching..... | 277 | +| 8 | Sidelink transport channels and control information..... | 277 | +| 8.1 | Sidelink broadcast channel..... | 277 | +| 8.1.1 | Void..... | 278 | +| 8.2 | Sidelink shared channel..... | 278 | +| 8.2.1 | Data and control multiplexing..... | 278 | +| 8.3 | Sidelink control information on PSCCH..... | 279 | +| 8.3.1 | 1 st -stage SCI formats..... | 279 | +| 8.3.1.1 | SCI format 1-A..... | 279 | +| 8.3.1.2 | SCI format 1-B..... | 281 | +| 8.3.2 | CRC attachment..... | 282 | +| 8.3.3 | Channel coding..... | 282 | +| 8.3.4 | Rate Matching..... | 282 | +| 8.4 | Sidelink control information on PSSCH..... | 282 | +| 8.4.1 | 2 nd -stage SCI formats..... | 282 | +| 8.4.1.1 | SCI format 2-A..... | 282 | +| 8.4.1.2 | SCI format 2-B..... | 283 | +| 8.4.1.3 | SCI format 2-C..... | 284 | +| 8.4.1.4 | SCI format 2-D..... | 285 | +| 8.4.2 | CRC attachment..... | 286 | +| 8.4.3 | Channel coding..... | 286 | +| 8.4.4 | Rate Matching..... | 286 | +| 8.4.5 | Multiplexing of coded 2 nd -stage SCI bits to PSSCH..... | 287 | +| Annex A (informative): | Change history..... | 288 | + +# 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 coding, multiplexing and mapping to physical channels for 5G 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] void. +- [3] void. +- [4] 3GPP TS 38.211: "NR; Physical channels and modulation". +- [5] 3GPP TS 38.213: "NR; Physical layer procedures for control". +- [6] 3GPP TS 38.214: "NR; Physical layer procedures for data". +- [7] void. +- [8] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification". +- [9] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification". +- [10] 3GPP TS 38.473: "NG-RAN; F1 Application Protocol (F1AP)". +- [11] 3GPP TS 36.212: "Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding". +- [12] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services". +- [13] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [14] 3GPP TS 37.213: "Physical layer procedures for shared spectrum channel access". + +# --- 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 + +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]. + +| | | +|----------|---------------------------------------------------| +| BCH | Broadcast Channel | +| CAPC | Channel Access Priority Class | +| CBG | Code Block Group | +| CBGTI | Code Block Group Transmission Information | +| CG | Configured Grant | +| CG-DFI | CG - Downlink Feedback Information | +| CG-UCI | CG - Uplink Control Information | +| CORESET | Control Resource Set | +| COT | Channel Occupancy Time | +| CQI | Channel Quality Indicator | +| CRC | Cyclic Redundancy Check | +| CRI | CSI-RS Resource Indicator | +| CSI | Channel State Information | +| CSI-RS | CSI - Reference Signal | +| DAI | Downlink Assignment Index | +| DCI | Downlink Control Information | +| DL | Downlink | +| DL-SCH | Downlink - Shared Channel | +| DMRS | Demodulation Reference Signal | +| HARQ | Hybrid Automatic repeat Request | +| HARQ-ACK | Hybrid Automatic repeat Request - Acknowledgement | +| LDPC | Low Density Parity Check | +| LI | Layer Indicator | +| MBS | Multicast Broadcast Services | +| MCS | Modulation and Coding Scheme | +| NCR | Network-controlled repeater | +| OFDM | Orthogonal Frequency Division Multiplex | +| PBCH | Physical Broadcast Channel | +| PCH | Paging Channel | +| PDCCH | Physical Downlink Control Channel | +| PDSCH | Physical Downlink Shared Channel | +| PMI | Precoding Matrix Indicator | +| PRB | Physical Resource Block | +| PRACH | Physical Random Access Channel | +| PSBCH | Physical Sidelink Broadcast Channel | +| PSCCH | Physical Sidelink Control Channel | +| PSFCH | Physical Sidelink Feedback Channel | +| PSSCH | Physical Sidelink Shared Channel | +| PTRS | Phase-Tracking Reference Signal | +| PUCCH | Physical Uplink Control Channel | +| PUSCH | Physical Uplink Shared Channel | +| RACH | Random Access Channel | +| RI | Rank Indicator | +| RSRP | Reference Signal Received Power | +| SCI | Sidelink Control Information | +| SFCI | Sidelink Feedback Control Information | +| SFN | System Frame Number | +| SL | Sidelink | +| SL-BCH | Sidelink - Broadcast Channel | +| SL PRS | Sidelink Positioning Reference Signal | +| SL-SCH | Sidelink - Shared Channel | +| SR | Scheduling Request | +| SRS | Sounding Reference Signal | +| SS | Synchronisation Signal | +| SUL | Supplementary Uplink | + +| | | +|-----------|-----------------------------------------------------------| +| TCI | Transmission Configuration Indicator | +| TPC | Transmit Power Control | +| TrCH | Transport Channel | +| UCI | Uplink Control Information | +| UE | User Equipment | +| UL | Uplink | +| UL-SCH | Uplink Shared Channel | +| UTO-UCI | Unused Transmission Occasion - Uplink Control Information | +| VRB | Virtual Resource Block | +| ZP CSI-RS | Zero power CSI-RS | + +# 4 Mapping to physical channels + +## 4.1 Uplink + +Table 4.1-1 specifies the mapping of the uplink transport channels to their corresponding physical channels. Table 4.1-2 specifies the mapping of the uplink control channel information to its corresponding physical channel. + +**Table 4.1-1** + +| TrCH | Physical Channel | +|--------|------------------| +| UL-SCH | PUSCH | +| RACH | PRACH | + +**Table 4.1-2** + +| Control information | Physical Channel | +|---------------------|------------------| +| UCI | PUCCH, PUSCH | + +## 4.2 Downlink + +Table 4.2-1 specifies the mapping of the downlink transport channels to their corresponding physical channels. + +Table 4.2-2 specifies the mapping of the downlink control channel information to its corresponding physical channel. + +**Table 4.2-1** + +| TrCH | Physical Channel | +|--------|------------------| +| DL-SCH | PDSCH | +| BCH | PBCH | +| PCH | PDSCH | + +**Table 4.2-2** + +| Control information | Physical Channel | +|---------------------|------------------| +| DCI | PDCCH | + +## 4.3 Sidelink + +Table 4.3-1 specifies the mapping of the sidelink transport channels to their corresponding physical channels. Table 4.3-2 specifies the mapping of the sidelink control information and sidelink feedback control information to their corresponding physical channels. + +**Table 4.3-1** + +| TrCH | Physical Channel | +|--------|------------------| +| SL-SCH | PSSCH | +| SL-BCH | PSBCH | + +**Table 4.3-2** + +| Control information | Physical Channel | +|----------------------------|------------------| +| 1 st -stage SCI | PSCCH | +| 2 nd -stage SCI | PSSCH | +| SFCI | PSFCH | + +# 5 General procedures + +Data and control streams from/to MAC layer are encoded /decoded to offer transport and control services over the radio transmission link. Channel coding scheme is a combination of error detection, error correcting, rate matching, interleaving and transport channel or control information mapping onto/splitting from physical channels. + +## 5.1 CRC calculation + +Denote the input bits to the CRC computation by $u$ , and the parity bits by $p$ , where $N$ is the size of the input sequence and $L$ is the number of parity bits. The parity bits are generated by one of the following cyclic generator polynomials: + +- for a CRC length $L=16$ ; +- for a CRC length $L=24$ ; +- for a CRC length $L=32$ ; +- for a CRC length $L=40$ ; +- for a CRC length $L=48$ ; +- for a CRC length $L=64$ . + +The encoding is performed in a systematic form, which means that in GF(2), the polynomial: + +yields a remainder equal to 0 when divided by the corresponding CRC generator polynomial. + +The bits after CRC attachment are denoted by $u'$ , where $N' = N + L$ . The relation between $u$ and $u'$ is: + +for + +for $L$ . + +## 5.2 Code block segmentation and code block CRC attachment + +### 5.2.1 Polar coding + +The input bit sequence to the code block segmentation is denoted by $u$ , where $N$ is the size of the input sequence. + +if + +Number of code blocks: $C$ ; + +else + +Number of code blocks: $C = 1$ + +end if + +; + +for to + +; + +end for + +for to + +; + +end for + +; + +for to + +for to + +; + +; + +end for + +The sequence is used to calculate the CRC parity bits according to Clause 5.1 with a generator polynomial of length . + +for to + +; + +end for + +end for + +The value of is no larger than 1706. + +### 5.2.2 Low density parity check coding + +The input bit sequence to the code block segmentation is denoted by , where . If is larger than the maximum code block size , segmentation of the input bit sequence is performed and an additional CRC sequence of bits is attached to each code block. + +For LDPC base graph 1, the maximum code block size is: + +- . + +For LDPC base graph 2, the maximum code block size is: + +- . + +Total number of code blocks $C$ is determined by: + +if + +Number of code blocks: + +else + +Number of code blocks: . + +end if + +The bits output from code block segmentation are denoted by $c_{r,k}$ , where $r$ is the code block number, and $k$ is the number of bits for the code block number $r$ . + +The number of bits $K_r$ in each code block is calculated as: + +``` + +; +For LDPC base graph 1, +; +For LDPC base graph 2, +if +; +elseif +; +elseif +; +else +; +end if +find the minimum value of $Z$ in all sets of lifting sizes in Table 5.3.2-1, denoted as $Z_{min}$ , such that $Z_{min} \geq K_r$ , and set $Z$ for LDPC base graph 1 and $Z$ for LDPC base graph 2; + +``` + +The bit sequence $c_{r,k}$ is calculated as: + +``` + +; +for to + for to + ; + ; + ; + end for + if + The sequence $c_{r,k}$ is used to calculate the CRC parity bits $a_{r,k}$ according to Clause 5.1 with the generator polynomial + ; + for to + ; + end for + end if + for to -- Insertion of filler bits + ; + end for +end for + +``` + +## 5.3 Channel coding + +Usage of coding scheme for the different types of TrCH is shown in table 5.3-1. Usage of coding scheme for the different control information types is shown in table 5.3-2. + +**Table 5.3-1: Usage of channel coding scheme for TrCHs** + +| TrCH | Coding scheme | +|--------|---------------| +| UL-SCH | LDPC | +| DL-SCH | | +| PCH | | +| BCH | Polar code | + +**Table 5.3-2: Usage of channel coding scheme for control information** + +| Control Information | Coding scheme | +|---------------------|---------------| +| DCI | Polar code | +| UCI | Block code | +| | Polar code | + +### 5.3.1 Polar coding + +The bit sequence input for a given code block to channel coding is denoted by $\mathbf{a}$ , where $K$ is the number of bits to encode. After encoding the bits are denoted by $\mathbf{c}$ , where $E$ and the value of $n_{pc}$ is determined by the following: + +Denote by $E$ the rate matching output sequence length as given in Clause 5.4.1; + +If and + +; + +else + +; + +end if + +; + +; + +where . + +UE is not expected to be configured with $K + n_{pc} > E$ , where $n_{pc}$ is the number of parity check bits defined in Clause 5.3.1.2. + +#### 5.3.1.1 Interleaving + +The bit sequence $\mathbf{a}$ is interleaved into bit sequence $\mathbf{c}$ as follows: + +, + +where the interleaving pattern $\mathbf{i}$ is given by the following: + +if + +, + +else + +; + +for to + +if + +; + +; + +end if + +end for + +end if + +where $\mathbf{i}$ is given by Table 5.3.1.1-1 and . + +Table 5.3.1.1-1: Interleaving pattern + +| | | | | | | | | | | | | +|----|----|----|-----|----|-----|-----|-----|-----|-----|-----|-----| +| 0 | 0 | 28 | 67 | 56 | 122 | 84 | 68 | 112 | 33 | 140 | 38 | +| 1 | 2 | 29 | 69 | 57 | 123 | 85 | 73 | 113 | 36 | 141 | 144 | +| 2 | 4 | 30 | 70 | 58 | 126 | 86 | 78 | 114 | 44 | 142 | 39 | +| 3 | 7 | 31 | 71 | 59 | 127 | 87 | 84 | 115 | 47 | 143 | 145 | +| 4 | 9 | 32 | 72 | 60 | 129 | 88 | 90 | 116 | 64 | 144 | 40 | +| 5 | 14 | 33 | 76 | 61 | 132 | 89 | 92 | 117 | 74 | 145 | 146 | +| 6 | 19 | 34 | 77 | 62 | 134 | 90 | 94 | 118 | 79 | 146 | 41 | +| 7 | 20 | 35 | 81 | 63 | 138 | 91 | 96 | 119 | 85 | 147 | 147 | +| 8 | 24 | 36 | 82 | 64 | 139 | 92 | 99 | 120 | 97 | 148 | 148 | +| 9 | 25 | 37 | 83 | 65 | 140 | 93 | 102 | 121 | 100 | 149 | 149 | +| 10 | 26 | 38 | 87 | 66 | 1 | 94 | 105 | 122 | 103 | 150 | 150 | +| 11 | 28 | 39 | 88 | 67 | 3 | 95 | 107 | 123 | 117 | 151 | 151 | +| 12 | 31 | 40 | 89 | 68 | 5 | 96 | 109 | 124 | 125 | 152 | 152 | +| 13 | 34 | 41 | 91 | 69 | 8 | 97 | 112 | 125 | 131 | 153 | 153 | +| 14 | 42 | 42 | 93 | 70 | 10 | 98 | 114 | 126 | 136 | 154 | 154 | +| 15 | 45 | 43 | 95 | 71 | 15 | 99 | 116 | 127 | 142 | 155 | 155 | +| 16 | 49 | 44 | 98 | 72 | 21 | 100 | 121 | 128 | 12 | 156 | 156 | +| 17 | 50 | 45 | 101 | 73 | 27 | 101 | 124 | 129 | 17 | 157 | 157 | +| 18 | 51 | 46 | 104 | 74 | 29 | 102 | 128 | 130 | 23 | 158 | 158 | +| 19 | 53 | 47 | 106 | 75 | 32 | 103 | 130 | 131 | 37 | 159 | 159 | +| 20 | 54 | 48 | 108 | 76 | 35 | 104 | 133 | 132 | 48 | 160 | 160 | +| 21 | 56 | 49 | 110 | 77 | 43 | 105 | 135 | 133 | 75 | 161 | 161 | +| 22 | 58 | 50 | 111 | 78 | 46 | 106 | 141 | 134 | 80 | 162 | 162 | +| 23 | 59 | 51 | 113 | 79 | 52 | 107 | 6 | 135 | 86 | 163 | 163 | +| 24 | 61 | 52 | 115 | 80 | 55 | 108 | 11 | 136 | 137 | | | +| 25 | 62 | 53 | 118 | 81 | 57 | 109 | 16 | 137 | 143 | | | +| 26 | 65 | 54 | 119 | 82 | 60 | 110 | 22 | 138 | 13 | | | +| 27 | 66 | 55 | 120 | 83 | 63 | 111 | 30 | 139 | 18 | | | + +#### 5.3.1.2 Polar encoding + +The Polar sequence is given by Table 5.3.1.2-1, where denotes a bit index before Polar encoding for and . The Polar sequence is in ascending order of reliability , where denotes the reliability of bit index . + +For any code block encoded to bits, a same Polar sequence is used. The Polar sequence is a subset of Polar sequence with all elements of values less than , ordered in ascending order of reliability . + +Denote as a set of bit indices in Polar sequence , and as the set of other bit indices in Polar sequence , where and are given in Clause 5.4.1.1, , and is the number of parity check bits. + +Denote as the -th Kronecker power of matrix , where . + +For a bit index with , denote as the -th row of and as the row weight of , where is the number of ones in . Denote the set of bit indices for parity check bits as , where . A number of parity check bits are placed in the least reliable bit indices in . A number of other parity check bits are placed in the bit indices of minimum row weight in , where denotes the most reliable bit indices in ; if there are more than bit indices of the same minimum row weight in , the other parity check bits are placed in the bit indices of the highest reliability and the minimum row weight in . + +Generate according to the following: + +``` + +; +if + ; ; ; ; ; + for to + ; ; ; ; ; + if + if + ; + else + ; + ; + ; + +``` + +``` + + end if + else + ; + end if +end for +else + for to + if + ; + ; + else + ; + end if + end for +end if + +``` + +The output after encoding is obtained by . The encoding is performed in GF(2). + +**Table 5.3.1.2-1: Polar sequence and its corresponding reliability** + +| | | | | | | | | | | | | | | | | +|----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| 0 | 0 | 128 | 518 | 256 | 94 | 384 | 214 | 512 | 364 | 640 | 414 | 768 | 819 | 896 | 966 | +| 1 | 1 | 129 | 54 | 257 | 204 | 385 | 309 | 513 | 654 | 641 | 223 | 769 | 814 | 897 | 755 | +| 2 | 2 | 130 | 83 | 258 | 298 | 386 | 188 | 514 | 659 | 642 | 663 | 770 | 439 | 898 | 859 | +| 3 | 4 | 131 | 57 | 259 | 400 | 387 | 449 | 515 | 335 | 643 | 692 | 771 | 929 | 899 | 940 | +| 4 | 8 | 132 | 521 | 260 | 608 | 388 | 217 | 516 | 480 | 644 | 835 | 772 | 490 | 900 | 830 | +| 5 | 16 | 133 | 112 | 261 | 352 | 389 | 408 | 517 | 315 | 645 | 619 | 773 | 623 | 901 | 911 | +| 6 | 32 | 134 | 135 | 262 | 325 | 390 | 609 | 518 | 221 | 646 | 472 | 774 | 671 | 902 | 871 | +| 7 | 3 | 135 | 78 | 263 | 533 | 391 | 596 | 519 | 370 | 647 | 455 | 775 | 739 | 903 | 639 | +| 8 | 5 | 136 | 289 | 264 | 155 | 392 | 551 | 520 | 613 | 648 | 796 | 776 | 916 | 904 | 888 | +| 9 | 64 | 137 | 194 | 265 | 210 | 393 | 650 | 521 | 422 | 649 | 809 | 777 | 463 | 905 | 479 | +| 10 | 9 | 138 | 85 | 266 | 305 | 394 | 229 | 522 | 425 | 650 | 714 | 778 | 843 | 906 | 946 | +| 11 | 6 | 139 | 276 | 267 | 547 | 395 | 159 | 523 | 451 | 651 | 721 | 779 | 381 | 907 | 750 | +| 12 | 17 | 140 | 522 | 268 | 300 | 396 | 420 | 524 | 614 | 652 | 837 | 780 | 497 | 908 | 969 | +| 13 | 10 | 141 | 58 | 269 | 109 | 397 | 310 | 525 | 543 | 653 | 716 | 781 | 930 | 909 | 508 | +| 14 | 18 | 142 | 168 | 270 | 184 | 398 | 541 | 526 | 235 | 654 | 864 | 782 | 821 | 910 | 861 | +| 15 | 128 | 143 | 139 | 271 | 534 | 399 | 773 | 527 | 412 | 655 | 810 | 783 | 726 | 911 | 757 | +| 16 | 12 | 144 | 99 | 272 | 537 | 400 | 610 | 528 | 343 | 656 | 606 | 784 | 961 | 912 | 970 | +| 17 | 33 | 145 | 86 | 273 | 115 | 401 | 657 | 529 | 372 | 657 | 912 | 785 | 872 | 913 | 919 | +| 18 | 65 | 146 | 60 | 274 | 167 | 402 | 333 | 530 | 775 | 658 | 722 | 786 | 492 | 914 | 875 | +| 19 | 20 | 147 | 280 | 275 | 225 | 403 | 119 | 531 | 317 | 659 | 696 | 787 | 631 | 915 | 862 | +| 20 | 256 | 148 | 89 | 276 | 326 | 404 | 600 | 532 | 222 | 660 | 377 | 788 | 729 | 916 | 758 | +| 21 | 34 | 149 | 290 | 277 | 306 | 405 | 339 | 533 | 426 | 661 | 435 | 789 | 700 | 917 | 948 | +| 22 | 24 | 150 | 529 | 278 | 772 | 406 | 218 | 534 | 453 | 662 | 817 | 790 | 443 | 918 | 977 | +| 23 | 36 | 151 | 524 | 279 | 157 | 407 | 368 | 535 | 237 | 663 | 319 | 791 | 741 | 919 | 923 | +| 24 | 7 | 152 | 196 | 280 | 656 | 408 | 652 | 536 | 559 | 664 | 621 | 792 | 845 | 920 | 972 | +| 25 | 129 | 153 | 141 | 281 | 329 | 409 | 230 | 537 | 833 | 665 | 812 | 793 | 920 | 921 | 761 | +| 26 | 66 | 154 | 101 | 282 | 110 | 410 | 391 | 538 | 804 | 666 | 484 | 794 | 382 | 922 | 877 | +| 27 | 512 | 155 | 147 | 283 | 117 | 411 | 313 | 539 | 712 | 667 | 430 | 795 | 822 | 923 | 952 | +| 28 | 11 | 156 | 176 | 284 | 212 | 412 | 450 | 540 | 834 | 668 | 838 | 796 | 851 | 924 | 495 | +| 29 | 40 | 157 | 142 | 285 | 171 | 413 | 542 | 541 | 661 | 669 | 667 | 797 | 730 | 925 | 703 | +| 30 | 68 | 158 | 530 | 286 | 776 | 414 | 334 | 542 | 808 | 670 | 488 | 798 | 498 | 926 | 935 | +| 31 | 130 | 159 | 321 | 287 | 330 | 415 | 233 | 543 | 779 | 671 | 239 | 799 | 880 | 927 | 978 | +| 32 | 19 | 160 | 31 | 288 | 226 | 416 | 555 | 544 | 617 | 672 | 378 | 800 | 742 | 928 | 883 | +| 33 | 13 | 161 | 200 | 289 | 549 | 417 | 774 | 545 | 604 | 673 | 459 | 801 | 445 | 929 | 762 | +| 34 | 48 | 162 | 90 | 290 | 538 | 418 | 175 | 546 | 433 | 674 | 622 | 802 | 471 | 930 | 503 | +| 35 | 14 | 163 | 545 | 291 | 387 | 419 | 123 | 547 | 720 | 675 | 627 | 803 | 635 | 931 | 925 | +| 36 | 72 | 164 | 292 | 292 | 308 | 420 | 658 | 548 | 816 | 676 | 437 | 804 | 932 | 932 | 878 | +| 37 | 257 | 165 | 322 | 293 | 216 | 421 | 612 | 549 | 836 | 677 | 380 | 805 | 687 | 933 | 735 | +| 38 | 21 | 166 | 532 | 294 | 416 | 422 | 341 | 550 | 347 | 678 | 818 | 806 | 903 | 934 | 993 | +| 39 | 132 | 167 | 263 | 295 | 271 | 423 | 777 | 551 | 897 | 679 | 461 | 807 | 825 | 935 | 885 | +| 40 | 35 | 168 | 149 | 296 | 279 | 424 | 220 | 552 | 243 | 680 | 496 | 808 | 500 | 936 | 939 | +| 41 | 258 | 169 | 102 | 297 | 158 | 425 | 314 | 553 | 662 | 681 | 669 | 809 | 846 | 937 | 994 | +| 42 | 26 | 170 | 105 | 298 | 337 | 426 | 424 | 554 | 454 | 682 | 679 | 810 | 745 | 938 | 980 | +| 43 | 513 | 171 | 304 | 299 | 550 | 427 | 395 | 555 | 318 | 683 | 724 | 811 | 826 | 939 | 926 | +| 44 | 80 | 172 | 296 | 300 | 672 | 428 | 673 | 556 | 675 | 684 | 841 | 812 | 732 | 940 | 764 | +| 45 | 37 | 173 | 163 | 301 | 118 | 429 | 583 | 557 | 618 | 685 | 629 | 813 | 446 | 941 | 941 | +| 46 | 25 | 174 | 92 | 302 | 332 | 430 | 355 | 558 | 898 | 686 | 351 | 814 | 962 | 942 | 967 | +| 47 | 22 | 175 | 47 | 303 | 579 | 431 | 287 | 559 | 781 | 687 | 467 | 815 | 936 | 943 | 886 | + +| | | | | | | | | | | | | | | | | +|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|------|------| +| 48 | 136 | 176 | 267 | 304 | 540 | 432 | 183 | 560 | 376 | 688 | 438 | 816 | 475 | 944 | 831 | +| 49 | 260 | 177 | 385 | 305 | 389 | 433 | 234 | 561 | 428 | 689 | 737 | 817 | 853 | 945 | 947 | +| 50 | 264 | 178 | 546 | 306 | 173 | 434 | 125 | 562 | 665 | 690 | 251 | 818 | 867 | 946 | 507 | +| 51 | 38 | 179 | 324 | 307 | 121 | 435 | 557 | 563 | 736 | 691 | 462 | 819 | 637 | 947 | 889 | +| 52 | 514 | 180 | 208 | 308 | 553 | 436 | 660 | 564 | 567 | 692 | 442 | 820 | 907 | 948 | 984 | +| 53 | 96 | 181 | 386 | 309 | 199 | 437 | 616 | 565 | 840 | 693 | 441 | 821 | 487 | 949 | 751 | +| 54 | 67 | 182 | 150 | 310 | 784 | 438 | 342 | 566 | 625 | 694 | 469 | 822 | 695 | 950 | 942 | +| 55 | 41 | 183 | 153 | 311 | 179 | 439 | 316 | 567 | 238 | 695 | 247 | 823 | 746 | 951 | 996 | +| 56 | 144 | 184 | 165 | 312 | 228 | 440 | 241 | 568 | 359 | 696 | 683 | 824 | 828 | 952 | 971 | +| 57 | 28 | 185 | 106 | 313 | 338 | 441 | 778 | 569 | 457 | 697 | 842 | 825 | 753 | 953 | 890 | +| 58 | 69 | 186 | 55 | 314 | 312 | 442 | 563 | 570 | 399 | 698 | 738 | 826 | 854 | 954 | 509 | +| 59 | 42 | 187 | 328 | 315 | 704 | 443 | 345 | 571 | 787 | 699 | 899 | 827 | 857 | 955 | 949 | +| 60 | 516 | 188 | 536 | 316 | 390 | 444 | 452 | 572 | 591 | 700 | 670 | 828 | 504 | 956 | 973 | +| 61 | 49 | 189 | 577 | 317 | 174 | 445 | 397 | 573 | 678 | 701 | 783 | 829 | 799 | 957 | 1000 | +| 62 | 74 | 190 | 548 | 318 | 554 | 446 | 403 | 574 | 434 | 702 | 849 | 830 | 255 | 958 | 892 | +| 63 | 272 | 191 | 113 | 319 | 581 | 447 | 207 | 575 | 677 | 703 | 820 | 831 | 964 | 959 | 950 | +| 64 | 160 | 192 | 154 | 320 | 393 | 448 | 674 | 576 | 349 | 704 | 728 | 832 | 909 | 960 | 863 | +| 65 | 520 | 193 | 79 | 321 | 283 | 449 | 558 | 577 | 245 | 705 | 928 | 833 | 719 | 961 | 759 | +| 66 | 288 | 194 | 269 | 322 | 122 | 450 | 785 | 578 | 458 | 706 | 791 | 834 | 477 | 962 | 1008 | +| 67 | 528 | 195 | 108 | 323 | 448 | 451 | 432 | 579 | 666 | 707 | 367 | 835 | 915 | 963 | 510 | +| 68 | 192 | 196 | 578 | 324 | 353 | 452 | 357 | 580 | 620 | 708 | 901 | 836 | 638 | 964 | 979 | +| 69 | 544 | 197 | 224 | 325 | 561 | 453 | 187 | 581 | 363 | 709 | 630 | 837 | 748 | 965 | 953 | +| 70 | 70 | 198 | 166 | 326 | 203 | 454 | 236 | 582 | 127 | 710 | 685 | 838 | 944 | 966 | 763 | +| 71 | 44 | 199 | 519 | 327 | 63 | 455 | 664 | 583 | 191 | 711 | 844 | 839 | 869 | 967 | 974 | +| 72 | 131 | 200 | 552 | 328 | 340 | 456 | 624 | 584 | 782 | 712 | 633 | 840 | 491 | 968 | 954 | +| 73 | 81 | 201 | 195 | 329 | 394 | 457 | 587 | 585 | 407 | 713 | 711 | 841 | 699 | 969 | 879 | +| 74 | 50 | 202 | 270 | 330 | 527 | 458 | 780 | 586 | 436 | 714 | 253 | 842 | 754 | 970 | 981 | +| 75 | 73 | 203 | 641 | 331 | 582 | 459 | 705 | 587 | 626 | 715 | 691 | 843 | 858 | 971 | 982 | +| 76 | 15 | 204 | 523 | 332 | 556 | 460 | 126 | 588 | 571 | 716 | 824 | 844 | 478 | 972 | 927 | +| 77 | 320 | 205 | 275 | 333 | 181 | 461 | 242 | 589 | 465 | 717 | 902 | 845 | 968 | 973 | 995 | +| 78 | 133 | 206 | 580 | 334 | 295 | 462 | 565 | 590 | 681 | 718 | 686 | 846 | 383 | 974 | 765 | +| 79 | 52 | 207 | 291 | 335 | 285 | 463 | 398 | 591 | 246 | 719 | 740 | 847 | 910 | 975 | 956 | +| 80 | 23 | 208 | 59 | 336 | 232 | 464 | 346 | 592 | 707 | 720 | 850 | 848 | 815 | 976 | 887 | +| 81 | 134 | 209 | 169 | 337 | 124 | 465 | 456 | 593 | 350 | 721 | 375 | 849 | 976 | 977 | 985 | +| 82 | 384 | 210 | 560 | 338 | 205 | 466 | 358 | 594 | 599 | 722 | 444 | 850 | 870 | 978 | 997 | +| 83 | 76 | 211 | 114 | 339 | 182 | 467 | 405 | 595 | 668 | 723 | 470 | 851 | 917 | 979 | 986 | +| 84 | 137 | 212 | 277 | 340 | 643 | 468 | 303 | 596 | 790 | 724 | 483 | 852 | 727 | 980 | 943 | +| 85 | 82 | 213 | 156 | 341 | 562 | 469 | 569 | 597 | 460 | 725 | 415 | 853 | 493 | 981 | 891 | +| 86 | 56 | 214 | 87 | 342 | 286 | 470 | 244 | 598 | 249 | 726 | 485 | 854 | 873 | 982 | 998 | +| 87 | 27 | 215 | 197 | 343 | 585 | 471 | 595 | 599 | 682 | 727 | 905 | 855 | 701 | 983 | 766 | +| 88 | 97 | 216 | 116 | 344 | 299 | 472 | 189 | 600 | 573 | 728 | 795 | 856 | 931 | 984 | 511 | +| 89 | 39 | 217 | 170 | 345 | 354 | 473 | 566 | 601 | 411 | 729 | 473 | 857 | 756 | 985 | 988 | +| 90 | 259 | 218 | 61 | 346 | 211 | 474 | 676 | 602 | 803 | 730 | 634 | 858 | 860 | 986 | 1001 | +| 91 | 84 | 219 | 531 | 347 | 401 | 475 | 361 | 603 | 789 | 731 | 744 | 859 | 499 | 987 | 951 | +| 92 | 138 | 220 | 525 | 348 | 185 | 476 | 706 | 604 | 709 | 732 | 852 | 860 | 731 | 988 | 1002 | +| 93 | 145 | 221 | 642 | 349 | 396 | 477 | 589 | 605 | 365 | 733 | 960 | 861 | 823 | 989 | 893 | +| 94 | 261 | 222 | 281 | 350 | 344 | 478 | 215 | 606 | 440 | 734 | 865 | 862 | 922 | 990 | 975 | +| 95 | 29 | 223 | 278 | 351 | 586 | 479 | 786 | 607 | 628 | 735 | 693 | 863 | 874 | 991 | 894 | +| 96 | 43 | 224 | 526 | 352 | 645 | 480 | 647 | 608 | 689 | 736 | 797 | 864 | 918 | 992 | 1009 | +| 97 | 98 | 225 | 177 | 353 | 593 | 481 | 348 | 609 | 374 | 737 | 906 | 865 | 502 | 993 | 955 | +| 98 | 515 | 226 | 293 | 354 | 535 | 482 | 419 | 610 | 423 | 738 | 715 | 866 | 933 | 994 | 1004 | +| 99 | 88 | 227 | 388 | 355 | 240 | 483 | 406 | 611 | 466 | 739 | 807 | 867 | 743 | 995 | 1010 | +| 100 | 140 | 228 | 91 | 356 | 206 | 484 | 464 | 612 | 793 | 740 | 474 | 868 | 760 | 996 | 957 | +| 101 | 30 | 229 | 584 | 357 | 95 | 485 | 680 | 613 | 250 | 741 | 636 | 869 | 881 | 997 | 983 | +| 102 | 146 | 230 | 769 | 358 | 327 | 486 | 801 | 614 | 371 | 742 | 694 | 870 | 494 | 998 | 958 | +| 103 | 71 | 231 | 198 | 359 | 564 | 487 | 362 | 615 | 481 | 743 | 254 | 871 | 702 | 999 | 987 | +| 104 | 262 | 232 | 172 | 360 | 800 | 488 | 590 | 616 | 574 | 744 | 717 | 872 | 921 | 1000 | 1012 | +| 105 | 265 | 233 | 120 | 361 | 402 | 489 | 409 | 617 | 413 | 745 | 575 | 873 | 501 | 1001 | 999 | +| 106 | 161 | 234 | 201 | 362 | 356 | 490 | 570 | 618 | 603 | 746 | 913 | 874 | 876 | 1002 | 1016 | +| 107 | 576 | 235 | 336 | 363 | 307 | 491 | 788 | 619 | 366 | 747 | 798 | 875 | 847 | 1003 | 767 | +| 108 | 45 | 236 | 62 | 364 | 301 | 492 | 597 | 620 | 468 | 748 | 811 | 876 | 992 | 1004 | 989 | +| 109 | 100 | 237 | 282 | 365 | 417 | 493 | 572 | 621 | 655 | 749 | 379 | 877 | 447 | 1005 | 1003 | +| 110 | 640 | 238 | 143 | 366 | 213 | 494 | 219 | 622 | 900 | 750 | 697 | 878 | 733 | 1006 | 990 | +| 111 | 51 | 239 | 103 | 367 | 568 | 495 | 311 | 623 | 805 | 751 | 431 | 879 | 827 | 1007 | 1005 | +| 112 | 148 | 240 | 178 | 368 | 832 | 496 | 708 | 624 | 615 | 752 | 607 | 880 | 934 | 1008 | 959 | +| 113 | 46 | 241 | 294 | 369 | 588 | 497 | 598 | 625 | 684 | 753 | 489 | 881 | 882 | 1009 | 1011 | +| 114 | 75 | 242 | 93 | 370 | 186 | 498 | 601 | 626 | 710 | 754 | 866 | 882 | 937 | 1010 | 1013 | +| 115 | 266 | 243 | 644 | 371 | 646 | 499 | 651 | 627 | 429 | 755 | 723 | 883 | 963 | 1011 | 895 | +| 116 | 273 | 244 | 202 | 372 | 404 | 500 | 421 | 628 | 794 | 756 | 486 | 884 | 747 | 1012 | 1006 | +| 117 | 517 | 245 | 592 | 373 | 227 | 501 | 792 | 629 | 252 | 757 | 908 | 885 | 505 | 1013 | 1014 | +| 118 | 104 | 246 | 323 | 374 | 896 | 502 | 802 | 630 | 373 | 758 | 718 | 886 | 855 | 1014 | 1017 | +| 119 | 162 | 247 | 392 | 375 | 594 | 503 | 611 | 631 | 605 | 759 | 813 | 887 | 924 | 1015 | 1018 | + +| | | | | | | | | | | | | | | | | +|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|------|------| +| 120 | 53 | 248 | 297 | 376 | 418 | 504 | 602 | 632 | 848 | 760 | 476 | 888 | 734 | 1016 | 991 | +| 121 | 193 | 249 | 770 | 377 | 302 | 505 | 410 | 633 | 690 | 761 | 856 | 889 | 829 | 1017 | 1020 | +| 122 | 152 | 250 | 107 | 378 | 649 | 506 | 231 | 634 | 713 | 762 | 839 | 890 | 965 | 1018 | 1007 | +| 123 | 77 | 251 | 180 | 379 | 771 | 507 | 688 | 635 | 632 | 763 | 725 | 891 | 938 | 1019 | 1015 | +| 124 | 164 | 252 | 151 | 380 | 360 | 508 | 653 | 636 | 482 | 764 | 698 | 892 | 884 | 1020 | 1019 | +| 125 | 768 | 253 | 209 | 381 | 539 | 509 | 248 | 637 | 806 | 765 | 914 | 893 | 506 | 1021 | 1021 | +| 126 | 268 | 254 | 284 | 382 | 111 | 510 | 369 | 638 | 427 | 766 | 752 | 894 | 749 | 1022 | 1022 | +| 127 | 274 | 255 | 648 | 383 | 331 | 511 | 190 | 639 | 904 | 767 | 868 | 895 | 945 | 1023 | 1023 | + +### 5.3.2 Low density parity check coding + +The bit sequence input for a given code block to channel coding is denoted by $u$ , where $u$ is the number of bits to encode as defined in Clause 5.2.2. After encoding the bits are denoted by $u$ , where $u$ for LDPC base graph 1 and $u$ for LDPC base graph 2, and the value of $u$ is given in Clause 5.2.2. + +For a code block encoded by LDPC, the following encoding procedure applies: + +- 1) Find the set with index $l$ in Table 5.3.2-1 which contains $u$ . +- 2) for $i$ to $u-1$ + - if $u_i = 0$ + - $u_i = 0$ ; + - else + - $u_i = 1$ ; + - end if +- 3) Generate parity bits $p$ such that $Hp^T = 0$ , where $H$ is a column vector of all elements equal to 0. The encoding is performed in GF(2). + +For LDPC base graph 1, a matrix $H$ of $u$ has 46 rows with row indices $0$ to $45$ and 68 columns with column indices $0$ to $67$ . For LDPC base graph 2, a matrix $H$ of $u$ has 42 rows with row indices $0$ to $41$ and 52 columns with column indices $0$ to $51$ . The elements in $H$ with row and column indices given in Table 5.3.2-2 (for LDPC base graph 1) and Table 5.3.2-3 (for LDPC base graph 2) are of value 1, and all other elements in $H$ are of value 0. + +The matrix $H$ is obtained by replacing each element of $H$ with a matrix, according to the following: + +- Each element of value 0 in $H$ is replaced by an all zero matrix of size $Z_l$ ; +- Each element of value 1 in $H$ is replaced by a circular permutation matrix of size $Z_l$ , where $i$ and $j$ are the row and column indices of the element, and $P$ is obtained by circularly shifting the identity matrix of size $Z_l$ to the right $i-j$ times. The value of $Z_l$ is given by $l$ . The value of $Z_l$ is given by Tables 5.3.2-2 and 5.3.2-3 according to the set index $l$ and LDPC base graph. + +- 4) for $i$ to $u-1$ + +- $u_i = u_i \oplus p_i$ ; + +end for + +**Table 5.3.2-1: Sets of LDPC lifting size** + +| Set index ( $l$ ) | Set of lifting sizes ( $Z_l$ ) | +|-------------------|----------------------------------| +| 0 | {2, 4, 8, 16, 32, 64, 128, 256} | +| 1 | {3, 6, 12, 24, 48, 96, 192, 384} | +| 2 | {5, 10, 20, 40, 80, 160, 320} | +| 3 | {7, 14, 28, 56, 112, 224} | +| 4 | {9, 18, 36, 72, 144, 288} | +| 5 | {11, 22, 44, 88, 176, 352} | +| 6 | {13, 26, 52, 104, 208} | +| 7 | {15, 30, 60, 120, 240} | + +**Table 5.3.2-2: LDPC base graph 1 ( ) and its parity check matrices ( )** + +| Row index | Column index | Set index | | | | | | | | Row index | Column index | Set index | | | | | | | | +|-----------|--------------|-----------|-----|-----|-----|-----|-----|-----|-----|-----------|--------------|-----------|-----|-----|-----|-----|-----|-----|-----| +| | | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| 0 | 0 | 250 | 307 | 73 | 223 | 211 | 294 | 0 | 135 | 15 | 1 | 96 | 2 | 290 | 120 | 0 | 348 | 6 | 138 | +| | 1 | 69 | 19 | 15 | 16 | 198 | 118 | 0 | 227 | | 10 | 65 | 210 | 60 | 131 | 183 | 15 | 81 | 220 | +| | 2 | 226 | 50 | 103 | 94 | 188 | 167 | 0 | 126 | | 13 | 63 | 318 | 130 | 209 | 108 | 81 | 182 | 173 | +| | 3 | 159 | 369 | 49 | 91 | 186 | 330 | 0 | 134 | | 18 | 75 | 55 | 184 | 209 | 68 | 176 | 53 | 142 | +| | 5 | 100 | 181 | 240 | 74 | 219 | 207 | 0 | 84 | | 25 | 179 | 269 | 51 | 81 | 64 | 113 | 46 | 49 | +| | 6 | 10 | 216 | 39 | 10 | 4 | 165 | 0 | 83 | | 37 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 9 | 59 | 317 | 15 | 0 | 29 | 243 | 0 | 53 | 16 | 1 | 64 | 13 | 69 | 154 | 270 | 190 | 88 | 78 | +| | 10 | 229 | 288 | 162 | 205 | 144 | 250 | 0 | 225 | | 3 | 49 | 338 | 140 | 164 | 13 | 293 | 198 | 152 | +| | 11 | 110 | 109 | 215 | 216 | 116 | 1 | 0 | 205 | | 11 | 49 | 57 | 45 | 43 | 99 | 332 | 160 | 84 | +| | 12 | 191 | 17 | 164 | 21 | 216 | 339 | 0 | 128 | | 20 | 51 | 289 | 115 | 189 | 54 | 331 | 122 | 5 | +| | 13 | 9 | 357 | 133 | 215 | 115 | 201 | 0 | 75 | | 22 | 154 | 57 | 300 | 101 | 0 | 114 | 182 | 205 | +| | 15 | 195 | 215 | 298 | 14 | 233 | 53 | 0 | 135 | | 38 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 16 | 23 | 106 | 110 | 70 | 144 | 347 | 0 | 217 | 17 | 0 | 7 | 260 | 257 | 56 | 153 | 110 | 91 | 183 | +| | 18 | 190 | 242 | 113 | 141 | 95 | 304 | 0 | 220 | | 14 | 164 | 303 | 147 | 110 | 137 | 228 | 184 | 112 | +| | 19 | 35 | 180 | 16 | 198 | 216 | 167 | 0 | 90 | | 16 | 59 | 81 | 128 | 200 | 0 | 247 | 30 | 106 | +| | 20 | 239 | 330 | 189 | 104 | 73 | 47 | 0 | 105 | | 17 | 1 | 358 | 51 | 63 | 0 | 116 | 3 | 219 | +| | 21 | 31 | 346 | 32 | 81 | 261 | 188 | 0 | 137 | | 21 | 144 | 375 | 228 | 4 | 162 | 190 | 155 | 129 | +| | 22 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | | 39 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 23 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 18 | 1 | 42 | 130 | 260 | 199 | 161 | 47 | 1 | 183 | +| 1 | 0 | 2 | 76 | 303 | 141 | 179 | 77 | 22 | 96 | | 12 | 233 | 163 | 294 | 110 | 151 | 286 | 41 | 215 | +| | 2 | 239 | 76 | 294 | 45 | 162 | 225 | 11 | 236 | | 13 | 8 | 280 | 291 | 200 | 0 | 246 | 167 | 180 | +| | 3 | 117 | 73 | 27 | 151 | 223 | 96 | 124 | 136 | | 18 | 155 | 132 | 141 | 143 | 241 | 181 | 68 | 143 | +| | 4 | 124 | 288 | 261 | 46 | 256 | 338 | 0 | 221 | | 19 | 147 | 4 | 295 | 186 | 144 | 73 | 148 | 14 | +| | 5 | 71 | 144 | 161 | 119 | 160 | 268 | 10 | 128 | | 40 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 7 | 222 | 331 | 133 | 157 | 76 | 112 | 0 | 92 | 19 | 0 | 60 | 145 | 64 | 8 | 0 | 87 | 12 | 179 | +| | 8 | 104 | 331 | 4 | 133 | 202 | 302 | 0 | 172 | | 1 | 73 | 213 | 181 | 6 | 0 | 110 | 6 | 108 | +| | 9 | 173 | 178 | 80 | 87 | 117 | 50 | 2 | 56 | | 7 | 72 | 344 | 101 | 103 | 118 | 147 | 166 | 159 | +| | 11 | 220 | 295 | 129 | 206 | 109 | 167 | 16 | 11 | | 8 | 127 | 242 | 270 | 198 | 144 | 258 | 184 | 138 | +| | 12 | 102 | 342 | 300 | 93 | 15 | 253 | 60 | 189 | | 10 | 224 | 197 | 41 | 8 | 0 | 204 | 191 | 196 | +| | 14 | 109 | 217 | 76 | 79 | 72 | 334 | 0 | 95 | | 41 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 15 | 132 | 99 | 266 | 9 | 152 | 242 | 6 | 85 | 20 | 0 | 151 | 187 | 301 | 105 | 265 | 89 | 6 | 77 | +| | 16 | 142 | 354 | 72 | 118 | 158 | 257 | 30 | 153 | | 3 | 186 | 206 | 162 | 210 | 81 | 65 | 12 | 187 | +| | 17 | 155 | 114 | 83 | 194 | 147 | 133 | 0 | 87 | | 9 | 217 | 264 | 40 | 121 | 90 | 155 | 15 | 203 | +| | 19 | 255 | 331 | 260 | 31 | 156 | 9 | 168 | 163 | | 11 | 47 | 341 | 130 | 214 | 144 | 244 | 5 | 167 | +| | 21 | 28 | 112 | 301 | 187 | 119 | 302 | 31 | 216 | | 22 | 160 | 59 | 10 | 183 | 228 | 30 | 30 | 130 | +| | 22 | 0 | 0 | 0 | 0 | 0 | 0 | 105 | 0 | | 42 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 23 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 21 | 1 | 249 | 205 | 79 | 192 | 64 | 162 | 6 | 197 | +| | 24 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 5 | 121 | 102 | 175 | 131 | 46 | 264 | 86 | 122 | +| 2 | 0 | 106 | 205 | 68 | 207 | 258 | 226 | 132 | 189 | | 16 | 109 | 328 | 132 | 220 | 266 | 346 | 96 | 215 | +| | 1 | 111 | 250 | 7 | 203 | 167 | 35 | 37 | 4 | 20 | 131 | 213 | 283 | 50 | 9 | 143 | 42 | 65 | | +| | 2 | 185 | 328 | 80 | 31 | 220 | 213 | 21 | 225 | 21 | 171 | 97 | 103 | 106 | 18 | 109 | 199 | 216 | | +| | 4 | 63 | 332 | 280 | 176 | 133 | 302 | 180 | 151 | 43 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | +| | 5 | 117 | 256 | 38 | 180 | 243 | 111 | 4 | 236 | 22 | 0 | 64 | 30 | 177 | 53 | 72 | 280 | 44 | 25 | +| | 6 | 93 | 161 | 227 | 186 | 202 | 265 | 149 | 117 | | 12 | 142 | 11 | 20 | 0 | 189 | 157 | 58 | 47 | +| | 7 | 229 | 267 | 202 | 95 | 218 | 128 | 48 | 179 | | 13 | 188 | 233 | 55 | 3 | 72 | 236 | 130 | 126 | +| | 8 | 177 | 160 | 200 | 153 | 63 | 237 | 38 | 92 | | 17 | 158 | 22 | 316 | 148 | 257 | 113 | 131 | 178 | +| | 9 | 95 | 63 | 71 | 177 | 0 | 294 | 122 | 24 | | 44 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 10 | 39 | 129 | 106 | 70 | 3 | 127 | 195 | 68 | 23 | 1 | 156 | 24 | 249 | 88 | 180 | 18 | 45 | 185 | +| | 13 | 142 | 200 | 295 | 77 | 74 | 110 | 155 | 6 | | 2 | 147 | 89 | 50 | 203 | 0 | 6 | 18 | 127 | +| | 14 | 225 | 88 | 283 | 214 | 229 | 286 | 28 | 101 | | 10 | 170 | 61 | 133 | 168 | 0 | 181 | 132 | 117 | +| | 15 | 225 | 53 | 301 | 77 | 0 | 125 | 85 | 33 | | 18 | 152 | 27 | 105 | 122 | 165 | 304 | 100 | 199 | +| | 17 | 245 | 131 | 184 | 198 | 216 | 131 | 47 | 96 | | 45 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 18 | 205 | 240 | 246 | 117 | 269 | 163 | 179 | 125 | 24 | 0 | 112 | 298 | 289 | 49 | 236 | 38 | 9 | 32 | +| | 19 | 251 | 205 | 230 | 223 | 200 | 210 | 42 | 67 | | 3 | 86 | 158 | 280 | 157 | 199 | 170 | 125 | 178 | +| | 20 | 117 | 13 | 276 | 90 | 234 | 7 | 66 | 230 | | 4 | 236 | 235 | 110 | 64 | 0 | 249 | 191 | 2 | +| | 24 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 11 | 116 | 339 | 187 | 193 | 266 | 288 | 28 | 156 | +| | 25 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 22 | 222 | 234 | 281 | 124 | 0 | 194 | 6 | 58 | +| 3 | 0 | 121 | 276 | 220 | 201 | 187 | 97 | 4 | 128 | | 46 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 1 | 89 | 87 | 208 | 18 | 145 | 94 | 6 | 23 | 25 | 1 | 23 | 72 | 172 | 1 | 205 | 279 | 4 | 27 | +| | 3 | 84 | 0 | 30 | 165 | 166 | 49 | 33 | 162 | | 6 | 136 | 17 | 295 | 166 | 0 | 255 | 74 | 141 | +| | 4 | 20 | 275 | 197 | 5 | 108 | 279 | 113 | 220 | | 7 | 116 | 383 | 96 | 65 | 0 | 111 | 16 | 11 | +| | 6 | 150 | 199 | 61 | 45 | 82 | 139 | 49 | 43 | | 14 | 182 | 312 | 46 | 81 | 183 | 54 | 28 | 181 | +| | 7 | 131 | 153 | 175 | 142 | 132 | 166 | 21 | 186 | | 47 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 8 | 243 | 56 | 79 | 16 | 197 | 91 | 6 | 96 | 26 | 0 | 195 | 71 | 270 | 107 | 0 | 325 | 21 | 163 | +| | 10 | 136 | 132 | 281 | 34 | 41 | 106 | 151 | 1 | | 2 | 243 | 81 | 110 | 176 | 0 | 326 | 142 | 131 | +| | 11 | 86 | 305 | 303 | 155 | 162 | 246 | 83 | 216 | | 4 | 215 | 76 | 318 | 212 | 0 | 226 | 192 | 169 | +| | 12 | 246 | 231 | 253 | 213 | 57 | 345 | 154 | 22 | | 15 | 61 | 136 | 67 | 127 | 277 | 99 | 197 | 98 | +| | 13 | 219 | 341 | 164 | 147 | 36 | 269 | 87 | 24 | | 48 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 14 | 211 | 212 | 53 | 69 | 115 | 185 | 5 | 167 | 27 | 1 | 25 | 194 | 210 | 208 | 45 | 91 | 98 | 165 | +| | 16 | 240 | 304 | 44 | 96 | 242 | 249 | 92 | 200 | | 6 | 104 | 194 | 29 | 141 | 36 | 326 | 140 | 232 | +| | 17 | 76 | 300 | 28 | 74 | 165 | 215 | 173 | 32 | | 8 | 194 | 101 | 304 | 174 | 72 | 268 | 22 | 9 | +| | 18 | 244 | 271 | 77 | 99 | 0 | 143 | 120 | 235 | | 49 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 20 | 144 | 39 | 319 | 30 | 113 | 121 | 2 | 172 | | 28 | 0 | 128 | 222 | 11 | 146 | 275 | 102 | 4 | +| | 21 | 12 | 357 | 68 | 158 | 108 | 121 | 142 | 219 | 4 | | 165 | 19 | 293 | 153 | 0 | 1 | 1 | 43 | +| 4 | 22 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 19 | | 181 | 244 | 50 | 217 | 155 | 40 | 40 | 200 | +| | 25 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 29 | 21 | 63 | 274 | 234 | 114 | 62 | 167 | 93 | 205 | +| 4 | 0 | 157 | 332 | 233 | 170 | 246 | 42 | 24 | 64 | | 50 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 1 | 102 | 181 | 205 | 10 | 235 | 256 | 204 | 211 | | 1 | 86 | 252 | 27 | 150 | 0 | 273 | 92 | 232 | +| 4 | 26 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 29 | 14 | 236 | 5 | 308 | 11 | 180 | 104 | 136 | 32 | +| 5 | 0 | 205 | 195 | 83 | 164 | 261 | 219 | 185 | 2 | 29 | 18 | 84 | 147 | 117 | 53 | 0 | 243 | 106 | 118 | +| | 1 | 236 | 14 | 292 | 59 | 181 | 130 | 100 | 171 | | 25 | 6 | 78 | 29 | 68 | 42 | 107 | 6 | 103 | +| | 3 | 194 | 115 | 50 | 86 | 72 | 251 | 24 | 47 | | 51 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | + +**3GPP** + +| Row index | Column index | Set index | | | | | | | | Row index | Column index | Set index | | | | | | | | +|-----------|--------------|-----------|-----|-----|-----|-----|-----|-----|-----|-----------|--------------|-----------|-----|-----|-----|-----|-----|-----|-----| +| | | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| 6 | 12 | 231 | 166 | 318 | 80 | 283 | 322 | 65 | 143 | 30 | 0 | 216 | 159 | 91 | 34 | 0 | 171 | 2 | 170 | +| | 16 | 28 | 241 | 201 | 182 | 254 | 295 | 207 | 210 | | 10 | 73 | 229 | 23 | 130 | 90 | 16 | 88 | 199 | +| | 21 | 123 | 51 | 267 | 130 | 79 | 258 | 161 | 180 | | 13 | 120 | 260 | 105 | 210 | 252 | 95 | 112 | 26 | +| | 22 | 115 | 157 | 279 | 153 | 144 | 283 | 72 | 180 | | 24 | 9 | 90 | 135 | 123 | 173 | 212 | 20 | 105 | +| | 27 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 52 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 0 | 183 | 278 | 289 | 158 | 80 | 294 | 6 | 199 | | 1 | 95 | 100 | 222 | 175 | 144 | 101 | 4 | 73 | +| 7 | 6 | 22 | 257 | 21 | 119 | 144 | 73 | 27 | 22 | 31 | 7 | 177 | 215 | 308 | 49 | 144 | 297 | 49 | 149 | +| | 10 | 28 | 1 | 293 | 113 | 169 | 330 | 163 | 23 | | 22 | 172 | 258 | 66 | 177 | 166 | 279 | 125 | 175 | +| | 11 | 67 | 351 | 13 | 21 | 90 | 99 | 50 | 100 | | 25 | 61 | 256 | 162 | 128 | 19 | 222 | 194 | 108 | +| | 13 | 244 | 92 | 232 | 63 | 59 | 172 | 48 | 92 | | 53 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 17 | 11 | 253 | 302 | 51 | 177 | 150 | 24 | 207 | | 0 | 221 | 102 | 210 | 192 | 0 | 351 | 6 | 103 | +| | 18 | 157 | 18 | 138 | 136 | 151 | 284 | 38 | 52 | | 12 | 112 | 201 | 22 | 209 | 211 | 265 | 126 | 110 | +| 8 | 20 | 211 | 225 | 235 | 116 | 108 | 305 | 91 | 13 | 32 | 14 | 199 | 175 | 271 | 58 | 36 | 338 | 63 | 151 | +| | 28 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 24 | 121 | 287 | 217 | 30 | 162 | 83 | 20 | 211 | +| | 0 | 220 | 9 | 12 | 17 | 169 | 3 | 145 | 77 | | 54 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 1 | 44 | 62 | 88 | 76 | 189 | 103 | 88 | 146 | | 1 | 2 | 323 | 170 | 114 | 0 | 56 | 10 | 199 | +| | 4 | 159 | 316 | 207 | 104 | 154 | 224 | 112 | 209 | | 2 | 187 | 8 | 20 | 49 | 0 | 304 | 30 | 132 | +| | 7 | 31 | 333 | 50 | 100 | 184 | 297 | 153 | 32 | | 11 | 41 | 361 | 140 | 161 | 76 | 141 | 6 | 172 | +| 9 | 8 | 167 | 290 | 25 | 150 | 104 | 215 | 159 | 166 | 33 | 21 | 211 | 105 | 33 | 137 | 18 | 101 | 92 | 65 | +| | 14 | 104 | 114 | 76 | 158 | 164 | 39 | 76 | 18 | | 55 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 29 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 0 | 127 | 230 | 187 | 82 | 197 | 60 | 4 | 161 | +| | 0 | 112 | 307 | 295 | 33 | 54 | 348 | 172 | 181 | | 7 | 167 | 148 | 296 | 186 | 0 | 320 | 153 | 237 | +| | 1 | 4 | 179 | 133 | 95 | 0 | 75 | 2 | 105 | | 15 | 164 | 202 | 5 | 68 | 108 | 112 | 197 | 142 | +| | 3 | 7 | 165 | 130 | 4 | 252 | 22 | 131 | 141 | | 17 | 159 | 312 | 44 | 150 | 0 | 54 | 155 | 180 | +| 10 | 12 | 211 | 18 | 231 | 217 | 41 | 312 | 141 | 223 | 34 | 56 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 16 | 102 | 39 | 296 | 204 | 98 | 224 | 96 | 177 | | 1 | 161 | 320 | 207 | 192 | 199 | 100 | 4 | 231 | +| | 19 | 164 | 224 | 110 | 39 | 46 | 17 | 99 | 145 | | 6 | 197 | 335 | 158 | 173 | 278 | 210 | 45 | 174 | +| | 21 | 109 | 368 | 269 | 58 | 15 | 59 | 101 | 199 | | 12 | 207 | 2 | 55 | 26 | 0 | 195 | 168 | 145 | +| | 22 | 241 | 67 | 245 | 44 | 230 | 314 | 35 | 153 | | 22 | 103 | 266 | 285 | 187 | 205 | 268 | 185 | 100 | +| | 24 | 90 | 170 | 154 | 201 | 54 | 244 | 116 | 38 | | 57 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 11 | 30 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 35 | 0 | 37 | 210 | 259 | 222 | 216 | 135 | 6 | 11 | +| | 0 | 103 | 366 | 189 | 9 | 162 | 156 | 6 | 169 | | 14 | 105 | 313 | 179 | 157 | 16 | 15 | 200 | 207 | +| | 1 | 182 | 232 | 244 | 37 | 159 | 88 | 10 | 12 | | 15 | 51 | 297 | 178 | 0 | 0 | 35 | 177 | 42 | +| | 10 | 109 | 321 | 36 | 213 | 93 | 293 | 145 | 206 | | 18 | 120 | 21 | 160 | 6 | 0 | 188 | 43 | 100 | +| | 11 | 21 | 133 | 286 | 105 | 134 | 111 | 53 | 221 | | 58 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 13 | 142 | 57 | 151 | 89 | 45 | 92 | 201 | 17 | | 1 | 198 | 269 | 298 | 81 | 72 | 319 | 82 | 59 | +| 12 | 17 | 14 | 303 | 267 | 185 | 132 | 152 | 4 | 212 | 36 | 13 | 220 | 82 | 15 | 195 | 144 | 236 | 2 | 204 | +| | 18 | 61 | 63 | 135 | 109 | 76 | 23 | 164 | 92 | | 23 | 122 | 115 | 115 | 138 | 0 | 85 | 135 | 161 | +| | 20 | 216 | 82 | 209 | 218 | 209 | 337 | 173 | 205 | | 59 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 31 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 0 | 167 | 185 | 151 | 123 | 190 | 164 | 91 | 121 | +| | 1 | 98 | 101 | 14 | 82 | 178 | 175 | 126 | 116 | | 9 | 151 | 177 | 179 | 90 | 0 | 196 | 64 | 90 | +| | 2 | 149 | 339 | 80 | 165 | 1 | 253 | 77 | 151 | | 10 | 157 | 289 | 64 | 73 | 0 | 209 | 198 | 26 | +| 13 | 4 | 167 | 274 | 211 | 174 | 28 | 27 | 156 | 70 | 37 | 12 | 163 | 214 | 181 | 10 | 0 | 246 | 100 | 140 | +| | 7 | 160 | 111 | 75 | 19 | 267 | 231 | 16 | 230 | | 60 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 8 | 49 | 383 | 161 | 194 | 234 | 49 | 12 | 115 | | 1 | 173 | 258 | 102 | 12 | 153 | 236 | 4 | 115 | +| | 14 | 58 | 354 | 311 | 103 | 201 | 267 | 70 | 84 | | 3 | 139 | 93 | 77 | 77 | 0 | 264 | 28 | 188 | +| | 32 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 7 | 149 | 346 | 192 | 49 | 165 | 37 | 109 | 168 | +| | 0 | 77 | 48 | 16 | 52 | 55 | 25 | 184 | 45 | | 19 | 0 | 297 | 208 | 114 | 117 | 272 | 188 | 52 | +| 14 | 1 | 41 | 102 | 147 | 11 | 23 | 322 | 194 | 115 | 38 | 61 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 12 | 83 | 8 | 290 | 2 | 274 | 200 | 123 | 134 | | 0 | 157 | 175 | 32 | 67 | 216 | 304 | 10 | 4 | +| | 16 | 182 | 47 | 289 | 35 | 181 | 351 | 16 | 1 | | 8 | 137 | 37 | 80 | 45 | 144 | 237 | 84 | 103 | +| | 21 | 78 | 188 | 177 | 32 | 273 | 166 | 104 | 152 | | 17 | 149 | 312 | 197 | 96 | 2 | 135 | 12 | 30 | +| | 22 | 252 | 334 | 43 | 84 | 39 | 338 | 109 | 165 | | 62 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 23 | 22 | 115 | 280 | 201 | 26 | 192 | 124 | 107 | | 1 | 167 | 52 | 154 | 23 | 0 | 123 | 2 | 53 | +| 15 | 33 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 39 | 3 | 173 | 314 | 47 | 215 | 0 | 77 | 75 | 189 | +| | 0 | 160 | 77 | 229 | 142 | 225 | 123 | 6 | 186 | | 9 | 139 | 139 | 124 | 60 | 0 | 25 | 142 | 215 | +| | 1 | 42 | 186 | 235 | 175 | 162 | 217 | 20 | 215 | | 18 | 151 | 288 | 207 | 167 | 183 | 272 | 128 | 24 | +| | 10 | 21 | 174 | 169 | 136 | 244 | 142 | 203 | 124 | | 63 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 11 | 32 | 232 | 48 | 3 | 151 | 110 | 153 | 180 | | 0 | 149 | 113 | 226 | 114 | 27 | 288 | 163 | 222 | +| | 13 | 234 | 50 | 105 | 28 | 238 | 176 | 104 | 98 | | 4 | 157 | 14 | 65 | 91 | 0 | 83 | 10 | 170 | +| 16 | 18 | 7 | 74 | 52 | 182 | 243 | 76 | 207 | 80 | 40 | 24 | 137 | 218 | 126 | 78 | 35 | 17 | 162 | 71 | +| | 34 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 64 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 0 | 177 | 313 | 39 | 81 | 231 | 311 | 52 | 220 | | 1 | 151 | 113 | 228 | 206 | 52 | 210 | 1 | 22 | +| | 3 | 248 | 177 | 302 | 56 | 0 | 251 | 147 | 185 | | 16 | 163 | 132 | 69 | 22 | 243 | 3 | 163 | 127 | +| | 7 | 151 | 266 | 303 | 72 | 216 | 265 | 1 | 154 | | 18 | 173 | 114 | 176 | 134 | 0 | 53 | 99 | 49 | +| | 20 | 185 | 115 | 160 | 217 | 47 | 94 | 16 | 178 | | 25 | 139 | 168 | 102 | 161 | 270 | 167 | 98 | 125 | +| 17 | 23 | 62 | 370 | 37 | 78 | 36 | 81 | 46 | 150 | 41 | 65 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 35 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 0 | 139 | 80 | 234 | 84 | 18 | 79 | 4 | 191 | +| | 0 | 206 | 142 | 78 | 14 | 0 | 22 | 1 | 124 | | 7 | 157 | 78 | 227 | 4 | 0 | 244 | 6 | 211 | +| | 12 | 55 | 248 | 299 | 175 | 186 | 322 | 202 | 144 | | 9 | 163 | 163 | 259 | 9 | 0 | 293 | 142 | 187 | +| | 15 | 206 | 137 | 54 | 211 | 253 | 277 | 118 | 182 | | 22 | 173 | 274 | 260 | 12 | 57 | 272 | 3 | 148 | +| | 16 | 127 | 89 | 61 | 191 | 16 | 156 | 130 | 95 | | 66 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 18 | 17 | 16 | 347 | 179 | 51 | 0 | 66 | 1 | 72 | 42 | 1 | 149 | 135 | 101 | 184 | 168 | 82 | 181 | 177 | +| | 21 | 229 | 12 | 258 | 43 | 79 | 78 | 2 | 76 | | 6 | 151 | 149 | 228 | 121 | 0 | 67 | 45 | 114 | +| | 36 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 45 | 10 | 167 | 15 | 126 | 29 | 144 | 235 | 153 | 93 | +| 15 | 0 | 40 | 241 | 229 | 90 | 170 | 176 | 173 | 39 | 45 | 67 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | + +**Table 5.3.2-3: LDPC base graph 2 ( ) and its parity check matrices ( )** + +| Row index | Column index | Set index | | | | | | | | Row index | Column index | Set index | | | | | | | | +|-----------|--------------|-----------|-----|-----|-----|-----------------|-----|-----|-----|-----------|--------------|-----------|-----|-----|-----|-----------------|-----------------|-----|-----| +| | | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| 0 | 0 | 9 | 174 | 0 | 72 | 3 | 156 | 143 | 145 | 16 | 26 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 1 | 117 | 97 | 0 | 110 | 26 | 143 | 19 | 131 | 17 | 1 | 254 | 158 | 0 | 48 | 12 0 | 134 | 57 | 196 | +| | 2 | 204 | 166 | 0 | 23 | 53 | 14 | 176 | 71 | | 5 | 124 | 23 | 24 | 132 | 43 | 23 | 201 | 173 | +| | 3 | 26 | 66 | 0 | 181 | 35 | 3 | 165 | 21 | | 11 | 114 | 9 | 109 | 206 | 65 | 62 | 142 | 195 | +| | 6 | 189 | 71 | 0 | 95 | 11 5 | 40 | 196 | 23 | | 12 | 64 | 6 | 18 | 2 | 42 | 163 | 35 | 218 | +| | 9 | 205 | 172 | 0 | 8 | 12 7 | 123 | 13 | 112 | | 27 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 10 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | | 0 | 220 | 186 | 0 | 68 | 17 | 173 | 129 | 128 | +| | 11 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 6 | 194 | 6 | 18 | 16 | 10 6 | 31 | 203 | 211 | +| 1 | 0 | 167 | 27 | 137 | 53 | 19 | 17 | 18 | 142 | 18 | 7 | 50 | 46 | 86 | 156 | 14 2 | 22 | 140 | 210 | +| | 3 | 166 | 36 | 124 | 156 | 94 | 65 | 27 | 174 | | 28 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 4 | 253 | 48 | 0 | 115 | 10 4 | 63 | 3 | 183 | | 0 | 87 | 58 | 0 | 35 | 79 | 13 | 110 | 39 | +| | 5 | 125 | 92 | 0 | 156 | 66 | 1 | 102 | 27 | 19 | 1 | 20 | 42 | 158 | 138 | 28 | 135 | 124 | 84 | +| | 6 | 226 | 31 | 88 | 115 | 84 | 55 | 185 | 96 | | 10 | 185 | 156 | 154 | 86 | 41 | 145 | 52 | 88 | +| | 7 | 156 | 187 | 0 | 200 | 98 | 37 | 17 | 23 | | 29 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 8 | 224 | 185 | 0 | 29 | 69 | 171 | 14 | 9 | | 1 | 26 | 76 | 0 | 6 | 2 | 128 | 196 | 117 | +| | 9 | 252 | 3 | 55 | 31 | 50 | 133 | 180 | 167 | 20 | 4 | 105 | 61 | 148 | 20 | 10 3 | 52 | 35 | 227 | +| | 11 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 11 | 29 | 153 | 104 | 141 | 78 | 173 | 114 | 6 | +| 2 | 12 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 30 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 0 | 81 | 25 | 20 | 152 | 95 | 98 | 126 | 74 | | 0 | 76 | 157 | 0 | 80 | 91 | 156 | 10 | 238 | +| | 1 | 114 | 114 | 94 | 131 | 10 6 | 168 | 163 | 31 | 21 | 8 | 42 | 175 | 17 | 43 | 75 | 166 | 122 | 13 | +| | 3 | 44 | 117 | 99 | 46 | 92 | 107 | 47 | 3 | | 13 | 210 | 67 | 33 | 81 | 81 | 40 | 23 | 11 | +| | 4 | 52 | 110 | 9 | 191 | 11 0 | 82 | 183 | 53 | | 31 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 8 | 240 | 114 | 108 | 91 | 11 1 | 142 | 132 | 155 | | 1 | 222 | 20 | 0 | 49 | 54 | 18 | 202 | 195 | +| | 10 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 0 | 22 | 2 | 63 | 52 | 4 | 1 | 13 2 | 163 | 126 | 44 | +| | 12 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 32 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 3 | 13 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 0 | 23 | 106 | 0 | 156 | 68 | 110 | 52 | 5 | +| | 1 | 8 | 136 | 38 | 185 | 12 0 | 53 | 36 | 239 | 23 | 3 | 235 | 86 | 75 | 54 | 11 5 | 132 | 170 | 94 | +| | 2 | 58 | 175 | 15 | 6 | 12 1 | 174 | 48 | 171 | | 5 | 238 | 95 | 158 | 134 | 56 | 150 | 13 | 111 | +| | 4 | 158 | 113 | 102 | 36 | 22 | 174 | 18 | 95 | | 33 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 5 | 104 | 72 | 146 | 124 | 4 | 127 | 111 | 110 | | 24 | 1 | 46 | 182 | 0 | 153 | 30 | 113 | 113 | +| | 6 | 209 | 123 | 12 | 124 | 73 | 17 | 203 | 159 | 2 | | 139 | 153 | 69 | 88 | 42 | 108 | 161 | 19 | +| | 7 | 54 | 118 | 57 | 110 | 49 | 89 | 3 | 199 | 24 | 9 | 8 | 64 | 87 | 63 | 10 1 | 61 | 88 | 130 | +| | 8 | 18 | 28 | 53 | 156 | 12 8 | 17 | 191 | 43 | | 34 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 9 | 128 | 186 | 46 | 133 | 79 | 105 | 160 | 75 | 25 | 0 | 228 | 45 | 0 | 211 | 12 8 | 72 | 197 | 66 | +| | 10 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | | 5 | 156 | 21 | 65 | 94 | 63 | 136 | 194 | 95 | +| 4 | 13 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 35 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 0 | 179 | 72 | 0 | 200 | 42 | 86 | 43 | 29 | 26 | 2 | 29 | 67 | 0 | 90 | 14 2 | 36 | 164 | 146 | +| | 1 | 214 | 74 | 136 | 16 | 24 | 67 | 27 | 140 | | 7 | 143 | 137 | 100 | 6 | 28 | 38 | 172 | 66 | +| | 11 | 71 | 29 | 157 | 101 | 51 | 83 | 117 | 180 | | 12 | 160 | 55 | 13 | 221 | 10 0 | 53 | 49 | 190 | +| 5 | 14 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 13 | 122 | 85 | 7 | 6 | 13 3 | 145 | 161 | 86 | +| | 0 | 231 | 10 | 0 | 185 | 40 | 79 | 136 | 121 | 27 | 36 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 1 | 41 | 44 | 131 | 138 | 14 0 | 84 | 49 | 41 | | 0 | 8 | 103 | 0 | 27 | 13 | 42 | 168 | 64 | +| | 5 | 194 | 121 | 142 | 170 | 84 | 35 | 36 | 169 | | 6 | 151 | 50 | 32 | 118 | 10 | 104 | 193 | 181 | +| | 7 | 159 | 80 | 141 | 219 | 13 7 | 103 | 132 | 88 | 27 | 37 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 11 | 103 | 48 | 64 | 193 | 71 | 60 | 62 | 207 | | 1 | 98 | 70 | 0 | 216 | 10 6 | 64 | 14 | 7 | +| 6 | 15 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 2 | 101 | 111 | 126 | 212 | 77 | 24 | 186 | 144 | +| | 0 | 155 | 129 | 0 | 123 | 10 9 | 47 | 7 | 137 | 28 | 5 | 135 | 168 | 110 | 193 | 43 | 149 | 46 | 16 | +| | 5 | 228 | 92 | 124 | 55 | 87 | 154 | 34 | 72 | | 38 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 7 | 45 | 100 | 99 | 31 | 10 7 | 10 | 198 | 172 | | 29 | 0 | 18 | 110 | 0 | 108 | 13 3 | 139 | 50 | +| | 9 | 28 | 49 | 45 | 222 | 13 3 | 155 | 168 | 124 | 4 | | 28 | 17 | 154 | 61 | 25 | 161 | 27 | 57 | +| | 11 | 158 | 184 | 148 | 209 | 13 9 | 29 | 12 | 56 | 39 | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 7 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 30 | 2 | 71 | 120 | 0 | 106 | 87 | 84 | 70 | 37 | +| | 1 | 129 | 80 | 0 | 103 | 97 | 48 | 163 | 86 | | 5 | 240 | 154 | 35 | 44 | 56 | 173 | 17 | 139 | +| | 5 | 147 | 186 | 45 | 13 | 13 5 | 125 | 78 | 186 | | 7 | 9 | 52 | 51 | 185 | 10 4 | 93 | 50 | 221 | +| | 7 | 140 | 16 | 148 | 105 | 35 | 24 | 143 | 87 | | 9 | 84 | 56 | 134 | 176 | 70 | 29 | 6 | 17 | +| | 11 | 3 | 102 | 96 | 150 | 10 | 47 | 107 | 172 | | 40 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | + +| Row index | Column n | Set index | | | | | | | Row index | Column n | Set index | | | | | | | | | +|-----------|----------|-----------|-----|-----|-----|-----------------|-----|-----|-----------|----------|-----------|-----|-----|-----|-----|-----------------|-----|-----|-----| +| | | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | | +| | | | | | | 8 | | | | | | | | | | | | | | +| | 13 | 116 | 143 | 78 | 181 | 65 | 55 | 58 | 154 | 31 | 1 | 106 | 3 | 0 | 147 | 80 | 117 | 115 | 201 | +| | 17 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 13 | 1 | 170 | 20 | 182 | 13 9 | 148 | 189 | 46 | +| 8 | 0 | 142 | 118 | 0 | 147 | 70 | 53 | 101 | 176 | | 41 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 1 | 94 | 70 | 65 | 43 | 69 | 31 | 177 | 169 | | 0 | 242 | 84 | 0 | 108 | 32 | 116 | 110 | 179 | +| | 12 | 230 | 152 | 87 | 152 | 88 | 161 | 22 | 225 | 32 | 5 | 44 | 8 | 20 | 21 | 89 | 73 | 0 | 14 | +| | 18 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 12 | 166 | 17 | 122 | 110 | 71 | 142 | 163 | 116 | +| 9 | 1 | 203 | 28 | 0 | 2 | 97 | 104 | 186 | 167 | | 42 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 8 | 205 | 132 | 97 | 30 | 40 | 142 | 27 | 238 | | 2 | 132 | 165 | 0 | 71 | 13 5 | 105 | 163 | 46 | +| | 10 | 61 | 185 | 51 | 184 | 24 | 99 | 205 | 48 | 33 | 7 | 164 | 179 | 88 | 12 | 6 | 137 | 173 | 2 | +| | 11 | 247 | 178 | 85 | 83 | 49 | 64 | 81 | 68 | | 10 | 235 | 124 | 13 | 109 | 2 | 29 | 179 | 106 | +| | 19 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 43 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 10 | 0 | 11 | 59 | 0 | 174 | 46 | 111 | 125 | 38 | | 0 | 147 | 173 | 0 | 29 | 37 | 11 | 197 | 184 | +| | 1 | 185 | 104 | 17 | 150 | 41 | 25 | 60 | 217 | | 12 | 85 | 177 | 19 | 201 | 25 | 41 | 191 | 135 | +| | 6 | 0 | 22 | 156 | 8 | 10 1 | 174 | 177 | 208 | 34 | 13 | 36 | 12 | 78 | 69 | 11 4 | 162 | 193 | 141 | +| | 7 | 117 | 52 | 20 | 56 | 96 | 23 | 51 | 232 | | 44 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 20 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 1 | 57 | 77 | 0 | 91 | 60 | 126 | 157 | 85 | +| 11 | 0 | 11 | 32 | 0 | 99 | 28 | 91 | 39 | 178 | | 5 | 40 | 184 | 157 | 165 | 13 7 | 152 | 167 | 225 | +| | 7 | 236 | 92 | 7 | 138 | 30 | 175 | 29 | 214 | | 11 | 63 | 18 | 6 | 55 | 93 | 172 | 181 | 175 | +| | 9 | 210 | 174 | 4 | 110 | 11 6 | 24 | 35 | 168 | 35 | 45 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 13 | 56 | 154 | 2 | 99 | 64 | 141 | 8 | 51 | | 0 | 140 | 25 | 0 | 1 | 12 1 | 73 | 197 | 178 | +| | 21 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 2 | 38 | 151 | 63 | 175 | 12 9 | 154 | 167 | 112 | +| 12 | 1 | 63 | 39 | 0 | 46 | 33 | 122 | 18 | 124 | | 7 | 154 | 170 | 82 | 83 | 26 | 129 | 179 | 106 | +| | 3 | 111 | 93 | 113 | 217 | 12 2 | 11 | 155 | 122 | | 46 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 11 | 14 | 11 | 48 | 109 | 13 1 | 4 | 49 | 72 | | 10 | 219 | 37 | 0 | 40 | 97 | 167 | 181 | 154 | +| | 22 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 37 | 13 | 151 | 31 | 144 | 12 | 56 | 38 | 193 | 114 | +| 13 | 0 | 83 | 49 | 0 | 37 | 76 | 29 | 32 | 48 | | 47 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 1 | 2 | 125 | 112 | 113 | 37 | 91 | 53 | 57 | | 1 | 31 | 84 | 0 | 37 | 1 | 112 | 157 | 42 | +| | 8 | 38 | 35 | 102 | 143 | 62 | 27 | 95 | 167 | 38 | 5 | 66 | 151 | 93 | 97 | 70 | 7 | 173 | 41 | +| | 13 | 222 | 166 | 26 | 140 | 47 | 127 | 186 | 219 | | 11 | 38 | 190 | 19 | 46 | 1 | 19 | 191 | 105 | +| | 23 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 48 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 14 | 1 | 115 | 19 | 0 | 36 | 14 3 | 11 | 91 | 82 | | 0 | 239 | 93 | 0 | 106 | 11 9 | 109 | 181 | 167 | +| | 6 | 145 | 118 | 138 | 95 | 51 | 145 | 20 | 232 | | 7 | 172 | 132 | 24 | 181 | 32 | 6 | 157 | 45 | +| | 11 | 3 | 21 | 57 | 40 | 13 0 | 8 | 52 | 204 | 39 | 12 | 34 | 57 | 138 | 154 | 14 2 | 105 | 173 | 189 | +| | 13 | 232 | 163 | 27 | 116 | 97 | 166 | 109 | 162 | | 49 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 24 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 2 | 0 | 103 | 0 | 98 | 6 | 160 | 193 | 78 | +| 15 | 0 | 51 | 68 | 0 | 116 | 13 9 | 137 | 174 | 38 | | 10 | 75 | 107 | 36 | 35 | 73 | 156 | 163 | 67 | +| | 10 | 175 | 63 | 73 | 200 | 96 | 103 | 108 | 217 | | 13 | 120 | 163 | 143 | 36 | 10 2 | 82 | 179 | 180 | +| | 11 | 213 | 81 | 99 | 110 | 12 8 | 40 | 102 | 157 | | 50 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 25 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | | 1 | 129 | 147 | 0 | 120 | 48 | 132 | 191 | 53 | +| 16 | 1 | 203 | 87 | 0 | 75 | 48 | 78 | 125 | 170 | | 5 | 229 | 7 | 2 | 101 | 47 | 6 | 197 | 215 | +| | 9 | 142 | 177 | 79 | 158 | 9 | 158 | 31 | 23 | | 11 | 118 | 60 | 55 | 81 | 19 | 8 | 167 | 230 | +| | 11 | 8 | 135 | 111 | 134 | 28 | 17 | 54 | 175 | | 51 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 12 | 242 | 64 | 143 | 97 | 8 | 165 | 176 | 202 | | | | | | | | | | | + +### 5.3.3 Channel coding of small block lengths + +The bit sequence input for a given code block to channel coding is denoted by $u$ , where $u$ is the number of bits to encode. After encoding the bits are denoted by $u$ . + +#### 5.3.3.1 Encoding of 1-bit information + +For $u$ , the code block is encoded according to Table 5.3.3.1-1, where $u$ and $u$ is the modulation order for the code block. + +**Table 5.3.3.1-1: Encoding of 1-bit information** + +| | Encoded bits | +|----------|--------------| +| 1 | | +| 2 | | +| 4 | | +| 6 | | +| 8 | | + +The "x" and "y" in Table 5.3.3.1-1 are placeholders for Clauses 6.3.1.1, 6.3.2.5.1, 6.3.2.6.1 of [4, TS 38.211] to scramble the information bits in a way that maximizes the Euclidean distance of the modulation symbols carrying the information bits. + +#### 5.3.3.2 Encoding of 2-bit information + +For $L=2$ , the code block is encoded according to Table 5.3.3.2-1, where $Q_m$ is the modulation order for the code block. + +**Table 5.3.3.2-1: Encoding of 2-bit information** + +| $Q_m$ | Encoded bits | +|-------|----------------------------------| +| | $b_0, b_1, \dots, b_{M_{bit}-1}$ | +| 1 | | +| 2 | | +| 4 | | +| 6 | | +| 8 | | + +The "x" in Table 5.3.3.2-1 are placeholders for Clause 6.3.1.1 of [4, TS 38.211] to scramble the information bits in a way that maximizes the Euclidean distance of the modulation symbols carrying the information bits. + +#### 5.3.3.3 Encoding of other small block lengths + +For $3 \le L \le 11$ , the code block is encoded by $b_i = \sum_{n=0}^{L-1} (a_n \cdot M_{i,n}) \text{ mod } 2$ , where $i = 0, 1, \dots, 31$ , and $M_{i,n}$ represents the basis sequences as defined in Table 5.3.3.3-1. + +**Table 5.3.3.3-1: Basis sequences for (32, $L$ ) code** + +| i | M i,0 | M i,1 | M i,2 | M i,3 | M i,4 | M i,5 | M i,6 | M i,7 | M i,8 | M i,9 | M i,10 | +|----|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|------------------|-------------------| +| 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | +| 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | +| 2 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 1 | 1 | +| 3 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | +| 4 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | +| 5 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | +| 6 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | +| 7 | 1 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | +| 8 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | 1 | 1 | +| 9 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | +| 10 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | +| 11 | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | +| 12 | 1 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 1 | +| 13 | 1 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | +| 14 | 1 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | +| 15 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | +| 16 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | +| 17 | 1 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | +| 18 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | +| 19 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | +| 20 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | +| 21 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | +| 22 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | +| 23 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | +| 24 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 0 | +| 25 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 1 | +| 26 | 1 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | +| 27 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | +| 28 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | +| 29 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 0 | +| 30 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 31 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | + +## 5.4 Rate matching + +### 5.4.1 Rate matching for Polar code + +The rate matching for Polar code is defined per coded block and consists of sub-block interleaving, bit collection, and bit interleaving. The input bit sequence to rate matching is $\mathbf{u}$ . The output bit sequence after rate matching is denoted as $\mathbf{v}$ . + +#### 5.4.1.1 Sub-block interleaving + +The bits input to the sub-block interleaver are the coded bits $\mathbf{u}$ . The coded bits are divided into 32 sub-blocks. The bits output from the sub-block interleaver are denoted as $\mathbf{u}'$ , generated as follows: + +``` + +for $i$ to +: +: +: +: +end for + +``` + +where the sub-block interleaver pattern is given by Table 5.4.1.1-1. + +**Table 5.4.1.1-1: Sub-block interleaver pattern** + +| | | | | | | | | | | | | | | | | +|---|---|---|---|----|----|----|----|----|----|----|----|----|----|----|----| +| 0 | 0 | 4 | 3 | 8 | 8 | 12 | 10 | 16 | 12 | 20 | 14 | 24 | 24 | 28 | 27 | +| 1 | 1 | 5 | 5 | 9 | 16 | 13 | 18 | 17 | 20 | 21 | 22 | 25 | 25 | 29 | 29 | +| 2 | 2 | 6 | 6 | 10 | 9 | 14 | 11 | 18 | 13 | 22 | 15 | 26 | 26 | 30 | 30 | +| 3 | 4 | 7 | 7 | 11 | 17 | 15 | 19 | 19 | 21 | 23 | 23 | 27 | 28 | 31 | 31 | + +The sets of bit indices $\mathcal{A}_i$ and $\mathcal{A}_i^c$ are determined as follows, where $\mathcal{A}_i$ , $\mathcal{A}_i^c$ , and $\mathcal{A}_i^r$ are defined in Clause 5.3.1 + +``` + +if + if -- puncturing + for $i$ to + : + end for + if + : + else + : + end if + else -- shortening + for $i$ to + : + end for + end if +end if + +; + $\mathcal{A}_i$ comprises most reliable bit indices in $\mathcal{A}_i$ ; +; + +``` + +#### 5.4.1.2 Bit selection + +The bit sequence after the sub-block interleaver from Clause 5.4.1.1 is written into a circular buffer of length $N$ . + +Denoting by $n$ the rate matching output sequence length, the bit selection output bit sequence $\mathbf{v}$ , is generated as follows: + +``` + +if -- repetition + +``` + +``` + + for to + ; + end for +else + if -- puncturing + for to + ; + end for + else -- shortening + for to + ; + end for + end if +end if + +``` + +#### 5.4.1.3 Interleaving of coded bits + +The bit sequence $\tilde{d}_i$ is interleaved into bit sequence $\hat{d}_i$ , as follows: + +If + +Denote $\Delta$ as the smallest integer such that ; + +``` + +; +for to + for to + if + ; + else + ; + end if + ; +end for +end for +; +for to + for to + if + ; + end if +end for +end for +else + for to + ; +end for +end if + +``` + +The value of $\Delta$ is no larger than 8192. + +### 5.4.2 Rate matching for LDPC code + +The rate matching for LDPC code is defined per coded block and consists of bit selection and bit interleaving. The input bit sequence to rate matching is $\tilde{d}_i$ . The output bit sequence after rate matching is denoted as $\hat{d}_i$ . + +#### 5.4.2.1 Bit selection + +The bit sequence after encoding from Clause 5.3.2 is written into a circular buffer of length $N_{cb}$ for the $t$ -th coded block, where $t$ is defined in Clause 5.3.2. + +For the $t$ -th code block, let $X$ be $\min(N_{cb}, 256)$ and otherwise, where $X$ is determined according to Clause 6.1.4.2 in [6, TS 38.214] for UL-SCH and Clause 5.1.3.2 in [6, TS 38.214] for DL-SCH/PCH, assuming the following: + +For one TB for DL-SCH with PDSCH scheduled by DCI format 4\_0/4\_1/4\_2: + +- if the PDSCH is scheduled by DCI format 4\_1/4\_2: + - maximum number of layers is given by $X$ , where: + - if the higher layer parameter *maxMIMO-Layers* of *pdsch-ConfigMulticast* is configured, $X$ is given by that parameter; + - otherwise, $X$ equals to 1; + - if the higher layer parameter *mcs-Table* given by a *pdsch-ConfigMulticast* or by *pdsch-ConfigMTCH* for at least one common frequency resource (CFR) is set to 'qam256', maximum modulation order is assumed for DL-SCH; otherwise a maximum modulation order is assumed for DL-SCH; +- if the PDSCH is scheduled by DCI format 4\_0: + - maximum number of layers is 1; + - if the higher layer parameter *mcs-Table* given by a *pdsch-ConfigMCCH* is set to 'qam256', maximum modulation order is assumed for DL-SCH; otherwise a maximum modulation order is assumed for DL-SCH; + - if the higher layer parameter *mcs-Table* given by a *pdsch-ConfigMTCH* is set to 'qam256', maximum modulation order is assumed for DL-SCH; otherwise a maximum modulation order is assumed for DL-SCH; +- $X$ is given by Table 5.4.2.1-1, where the value of $X$ for DL-SCH is determined according to the size of the associated CFR if configured to the UE; +- maximum coding rate of 948/1024; +- $t$ ; +- $t$ is the number of code blocks of the transport block determined according to Clause 5.2.2. + +For one TB for UL-SCH, or for one TB for DL-SCH/PCH except for DL-SCH with PDSCH scheduled by DCI format 4\_0/4\_1/4\_2: + +- maximum number of layers for one TB for UL-SCH is given by the minimum of $X$ and 4, where: + - if the higher layer parameter *maxMIMO-Layers* of *PUSCH-ServingCellConfig* of the serving cell is configured, $X$ is given by that parameter; + - elseif the higher layer parameter *maxRank* of *pusch-Config* of the serving cell is configured, $X$ is given by the maximum value of *maxRank* across all BWPs of the serving cell; + - otherwise, $X$ is given by the maximum number of layers for PUSCH supported by the UE for the serving cell; +- maximum number of layers for one TB for DL-SCH/PCH is given by the minimum of $X$ and 4, where: + - if the higher layer parameter *maxMIMO-Layers* of *PDSCH-ServingCellConfig* of the serving cell is configured, $X$ is given by that parameter; + - otherwise, $X$ is given by the maximum number of layers for PDSCH supported by the UE for the serving cell; +- if the higher layer parameter *mcs-Table-r17* or *mcs-TableDCI-1-2-r17* given by a *pdsch-Config* for at least one DL BWP of the serving cell is set to 'qam1024', maximum modulation order is assumed for DL-SCH, else if the higher layer parameter *mcs-Table* or *mcs-TableDCI-1-2* given by a *pdsch-Config* for at least one DL BWP of the serving cell is set to 'qam256', maximum modulation order $Q_m = 8$ is assumed for DL-SCH; otherwise a maximum modulation order is assumed for DL-SCH; +- if the higher layer parameter *mcs-Table* or *mcs-TableTransformPrecoder* or *mcs-TableDCI-0-2* or *mcs-TableTransformPrecoderDCI-0-2* given by a *pusch-Config* or the higher layer parameter *mcs-Table* or *mcs-TableTransformPrecoder* given by *configuredGrantConfig* for at least one UL BWP of the serving cell + +is set to 'qam256', maximum modulation order $Q_m = 8$ is assumed for UL-SCH; otherwise a maximum modulation order is assumed for UL-SCH; + +- maximum coding rate of 948/1024; +- is given by Table 5.4.2.1-1, where the value of for DL-SCH is determined according to the initial downlink bandwidth part if there is no other downlink bandwidth part configured to the UE; +- $N_{RE} = 156 \cdot n_{PRB}$ ; +- is the number of code blocks of the transport block determined according to Clause 5.2.2. + +**Table 5.4.2.1-1: Value of** + +| Maximum number of PRBs across all configured DL BWPs and UL BWPs of a carrier for DL-SCH and UL-SCH, respectively, or Maximum number of PRBs across all CFRs of a carrier for DL-SCH with PDSCH scheduled by DCI format 4_0/4_1/4_2 | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| Less than 33 | 32 | +| 33 to 66 | 66 | +| 67 to 107 | 107 | +| 108 to 135 | 135 | +| 136 to 162 | 162 | +| 163 to 217 | 217 | +| Larger than 217 | 273 | + +Denoting by the rate matching output sequence length for the -th coded block, where the value of is determined as follows: + +Set + +for to + +if the -th coded block is not scheduled for transmission as indicated by CBGTI according to Clause 5.1.7.2 for DL-SCH and 6.1.5.2 for UL-SCH in [6, TS 38.214]: + +``` + +; +else + if + ; + else + ; + end if + ; +end if +end for + +``` + +where: + +- is the number of transmission layers that the transport block is mapped onto; +- is the modulation order; +- is the total number of coded bits available for transmission of the transport block; +- if CBGTI is not present in the DCI scheduling the transport block and is the number of scheduled code blocks of the transport block if CBGTI is present in the DCI scheduling the transport block. + +Denote by the redundancy version number for this transmission ( $= 0, 1, 2$ or $3$ ), the rate matching output bit sequence, is generated as follows, where is given by Table 5.4.2.1-2 according to the value of and LDPC base graph: + +``` + +; +; +while + +``` + +``` + +if +; +; +end if +; +end while + +``` + +**Table 5.4.2.1-2: Starting position of different redundancy versions,** + +| | LDPC base graph 1 | LDPC base graph 2 | +|---|-------------------|-------------------| +| 0 | | | +| 1 | | | +| 2 | | | +| 3 | | | + +#### 5.4.2.2 Bit interleaving + +The bit sequence $\tilde{u}$ is interleaved to bit sequence $\tilde{u}_i$ , according to the following, where the value of $i$ is the modulation order: + +``` + +for to + for to + ; + end for +end for + +``` + +### 5.4.3 Rate matching for channel coding of small block lengths + +The input bit sequence to rate matching is $\tilde{u}$ . The output bit sequence after rate matching is denoted as $\tilde{u}_r$ , where $r$ is the rate matching output sequence length. The bit sequence $\tilde{u}_r$ is obtained by the following: + +``` + +for to +; +end for + +``` + +## 5.5 Code block concatenation + +The input bit sequence for the code block concatenation block are the sequences $\tilde{u}_r$ , for $r$ and $r$ , where $r$ is the number of rate matched bits for the $r$ -th code block. The output bit sequence from the code block concatenation block is the sequence $\tilde{u}$ for $r$ . + +The code block concatenation consists of sequentially concatenating the rate matching outputs for the different code blocks. Therefore: + +``` + +Set $\tilde{u}$ and $r$ +while + Set $\tilde{u}$ + while + +end while + +``` + +end while + +# 6 Uplink transport channels and control information + +## 6.1 Random access channel + +The sequence index for the random access channel is received from higher layers and is processed according to [4, TS 38.211]. + +## 6.2 Uplink shared channel + +### 6.2.1 Transport block CRC attachment + +Error detection is provided on each UL-SCH transport block through a Cyclic Redundancy Check (CRC). + +The entire transport block is used to calculate the CRC parity bits. Denote the bits in a transport block delivered to layer 1 by $A$ , and the parity bits by $P$ , where $A$ is the payload size and $P$ is the number of parity bits. The lowest order information bit is mapped to the most significant bit of the transport block as defined in Clause 6.1.1 of [TS38.321]. + +The parity bits are computed and attached to the UL-SCH transport block according to Clause 5.1, by setting $P$ to 24 bits and using the generator polynomial $G_1$ if $A > 524$ ; and by setting $P$ to 16 bits and using the generator polynomial $G_2$ otherwise. + +The bits after CRC attachment are denoted by $A'$ , where $A'$ is the payload size. + +### 6.2.2 LDPC base graph selection + +For initial transmission of a transport block with coding rate $R$ indicated by the MCS index according to Clause 6.1.4.1 in [6, TS 38.214] and subsequent re-transmission of the same transport block, each code block of the transport block is encoded with either LDPC base graph 1 or 2 according to the following: + +- if $A' \leq 296$ or if $A' > 296$ and $R \leq 0.325$ , LDPC base graph 2 is used; +- otherwise, LDPC base graph 1 is used, + +where $A'$ is the payload size as described in Clause 6.2.1. + +### 6.2.3 Code block segmentation and code block CRC attachment + +The bits input to the code block segmentation are denoted by $A'$ where $A'$ is the number of bits in the transport block (including CRC). + +Code block segmentation and code block CRC attachment are performed according to Clause 5.2.2. + +The bits after code block segmentation are denoted by $C_i$ , where $i$ is the code block number and $C_i$ is the number of bits for code block number $i$ according to Clause 5.2.2. + +When the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI is larger than 1, the value of $B$ is no larger than 3840 if $R \leq 0.325$ and no larger than 8448 otherwise, where coding rate $R$ is indicated by the MCS index according to Clause 6.1.4.1 in [6, TS 38.214]. + +### 6.2.4 Channel coding of UL-SCH + +Code blocks are delivered to the channel coding block. The bits in a code block are denoted by $C_i$ , where $i$ is the code block number, and $C_i$ is the number of bits in code block number $i$ . The total number of code blocks is denoted by $N$ and each code block is individually LDPC encoded according to Clause 5.3.2. + +After encoding the bits are denoted by $E_i$ , where the values of $E_i$ is given in Clause 5.3.2. + +### 6.2.5 Rate matching + +Coded bits for each code block, denoted as $c_{n,k}$ , are delivered to the rate match block, where $n$ is the code block number, and $k$ is the number of encoded bits in code block number $n$ . The total number of code blocks is denoted by $N$ and each code block is individually rate matched according to Clause 5.4.2 by setting $\text{rateMatching}$ if higher layer parameter *rateMatching* is set to *limitedBufferRM* and by setting $\text{numberOfSlotsTBoMS}$ otherwise, if *numberOfSlotsTBoMS* is not present in the resource allocation table, or if *numberOfSlotsTBoMS* is present in the resource allocation table and the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI is equal to 1. When the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI is larger than 1, each code block is individually rate matched per slot according to Clause 5.4.2 by setting: + +- if higher layer parameter *rateMatching* is set to *limitedBufferRM* and by setting otherwise; +- as the total number of coded bits available for transmission of the transport block in the slot; +- as given by Table 5.4.2.1-2 according to the value of $N$ and LDPC base graph if the slot is the first slot within the slots allocated for the transmission of TB processing over multiple slots, and setting if the slot is a slot except for the first one within the slots, where $n$ is the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI, $k_{start}$ denotes the index of starting coded bit in the previous slot within the slots, $k_{end}$ is the total number of coded bits available for transmission of the transport block in the previous slot within the slots assuming no UCI multiplexing, and $k_{skipped}$ denotes the number of skipped filler bits if any in the previous slot within the slots according to Clause 5.4.2.1 by assuming no UCI multiplexing. + +After rate matching, the bits are denoted by $\hat{c}_{n,k}$ , where $\hat{k}$ is the number of rate matched bits for code block number $n$ . + +### 6.2.6 Code block concatenation + +The input bit sequence for the code block concatenation block are the sequences $\hat{c}_{n,k}$ , for $n$ and where $\hat{k}$ is the number of rate matched bits for the $n$ -th code block. + +Code block concatenation is performed according to Clause 5.5. + +The bits after code block concatenation are denoted by $c_k$ , where $K$ is the total number of coded bits for transmission. + +### 6.2.7 Data and control multiplexing + +In case where there are more than one UL-SCH transport blocks for the PUSCH transmission, the UCI information is multiplexed only on the UL-SCH transport block with highest $I_{MCS}$ value for the initial PUSCH, where $I_{MCS}$ is as defined in Clause 6.1.4.1 in [6, TS 38.214]. In case the two transport blocks have the same $I_{MCS}$ value for the initial PUSCH, the UCI information is multiplexed with data only on the first transport block. The PUSCH for UCI multiplexing in this Clause refers to the UL-SCH transport block for UCI multiplexing. + +If the higher layer parameter *nrof\_UTO\_UCI* is configured, the procedure in this clause 6.2.7 applies by replacing CG-UCI with UTO-UCI in all the notations and texts, and replacing "when higher layer parameter *cg-UCI-Multiplexing* is configured" with "when UTO-UCI and HARQ-ACK are transmitted on a PUSCH". + +Denote the coded bits for UL-SCH as $d_k$ . + +Denote the coded bits for HARQ-ACK or jointly coded bits for HARQ-ACK and CG-UCI when the high layer parameter *cg-UCI-Multiplexing* is configured, if any, as $a_k$ . + +Denote the coded bits for CSI part 1, if any, as $c_k$ . + +Denote the coded bits for CSI part 2, if any, as $c_k$ . + +Denote the coded bits for CG-UCI without HARQ-ACK, if any, as $c_k$ . + +Denote the multiplexed data and control coded bit sequence as $\tilde{d}_k$ . + +Denote $s$ as the OFDM symbol index of the scheduled PUSCH, starting from 0 to $S-1$ , where $S$ is the total number of OFDM symbols of the PUSCH, including all OFDM symbols used for DMRS. + +Denote $u$ as the subcarrier index of the scheduled PUSCH, starting from 0 to $N_{SC} - 1$ , where $N_{SC}$ is expressed as a number of subcarriers. + +Denote $\Phi_l^{\text{UL-SCH}}$ as the set of resource elements, in ascending order of indices , available for transmission of data in OFDM symbol $l$ , for . + +Denote $M_{\text{sc}}^{\text{UL-SCH}}(l) = |\Phi_l^{\text{UL-SCH}}|$ as the number of elements in set $\Phi_l^{\text{UL-SCH}}$ . Denote $\Phi_l^{\text{UL-SCH}}(j)$ as the $j$ -th element in $\Phi_l^{\text{UL-SCH}}$ . + +Denote $\Phi_l^{\text{UCI}}$ as the set of resource elements, in ascending order of indices , available for transmission of UCI in OFDM symbol $l$ , for . Denote $M_{\text{sc}}^{\text{UCI}}(l) = |\Phi_l^{\text{UCI}}|$ as the number of elements in set $\Phi_l^{\text{UCI}}$ . Denote $\Phi_l^{\text{UCI}}(j)$ as the $j$ -th element in $\Phi_l^{\text{UCI}}$ . For any OFDM symbol that carries DMRS of the PUSCH, $\Phi_l^{\text{UCI}} = \emptyset$ . For any OFDM symbol that does not carry DMRS of the PUSCH, $\Phi_l^{\text{UCI}} = \Phi_l^{\text{UL-SCH}}$ . + +If frequency hopping is configured for the PUSCH, + +- denote $l_1$ as the OFDM symbol index of the first OFDM symbol after the first set of consecutive OFDM symbol(s) carrying DMRS in the first hop; +- denote $l_2$ as the OFDM symbol index of the first OFDM symbol after the first set of consecutive OFDM symbol(s) carrying DMRS in the second hop; +- denote $l_3$ as the OFDM symbol index of the first OFDM symbol that does not carry DMRS in the first hop; +- denote $l_4$ as the OFDM symbol index of the first OFDM symbol that does not carry DMRS in the second hop; +- if HARQ-ACK is present for transmission on the PUSCH with UL-SCH or if both HARQ-ACK and CG-UCI are present on the same PUSCH with UL-SCH, let: + +- $l_1$ and $l_2$ ; + +- if CSI is present for transmission on the PUSCH with UL-SCH, let: + +- $l_1$ ; +- $l_2$ ; +- $l_3$ ; and +- $l_4$ ; + +- if CG-UCI is present for transmission on the PUSCH with UL-SCH and without HARQ-ACK, let: + +- $l_1$ and $l_2$ + +- if only HARQ-ACK and CSI part 1 are present for transmission on the PUSCH without UL-SCH, let: + +$$G^{\text{ACK}}(l) = \min \left( N_L \cdot Q_m \cdot \left\lceil G^{\text{ACK}} / (2 \cdot N_L \cdot Q_m) \right\rceil, M_3 \cdot N_L \cdot Q_m \right),$$ + +- $l_1$ ; +- $l_2$ ; and +- $l_3$ ; + +- if HARQ-ACK, CSI part 1 and CSI part 2 are present for transmission on the PUSCH without UL-SCH, let: + +$$G^{\text{ACK}}(l) = \min \left( N_L \cdot Q_m \cdot \left\lceil G^{\text{ACK}} / (2 \cdot N_L \cdot Q_m) \right\rceil, M_3 \cdot N_L \cdot Q_m \right),$$ + +- $l_1$ ; + +- if the number of HARQ-ACK information bits is more than 2, ; otherwise, + +$$G^{\text{CSI-part1}}(l) = \min \left( N_L \cdot Q_m \cdot \left\lceil G^{\text{CSI-part1}} / (2 \cdot N_L \cdot Q_m) \right\rceil, M_1 \cdot N_L \cdot Q_m - G^{\text{ACK}}(l) \right)$$ + +- $l_2$ ; + +- if the number of HARQ-ACK information bits is no more than 2, and $l_3$ otherwise; and + +- if the number of HARQ-ACK information bits is no more than 2, and $l_4$ otherwise; and + +- if only CSI part 1 and CSI part 2 are present for transmission on the PUSCH without UL-SCH, let: + +$$G^{\text{CSI-part1}}(l) = \min \left( N_L \cdot Q_m \cdot \left\lceil G^{\text{CSI-part1}} / (2 \cdot N_L \cdot Q_m) \right\rceil, M_1 \cdot N_L \cdot Q_m - G^{\text{ACK}}(l) \right),$$ + +- $l_1$ ; +- $l_2$ ; and +- $l_3$ ; + +- let $l_1$ and $l_2$ , as the number of OFDM symbols of the PUSCH in the first and second hop, respectively; + +- $N_{\text{layers}}$ is the number of transmission layers of the PUSCH; +- $Q_m$ is the modulation order of the PUSCH; +- $l$ ; +- $l$ ; + +$$M_3 = \sum_{l=0}^{N_{\text{symbol}}^{\text{PUSCH}}(l)-1} M_{\text{sc}}^{\text{UCI}}(l)$$ + +If frequency hopping is not configured for the PUSCH, + +- $l_0$ denote as the OFDM symbol index of the first OFDM symbol after the first set of consecutive OFDM symbol(s) carrying DMRS; +- $l_1$ denote as the OFDM symbol index of the first OFDM symbol that does not carry DMRS; +- if HARQ-ACK is present for transmission on the PUSCH or if both HARQ-ACK and CG-UCI are present on the same PUSCH with UL-SCH, let $l_2 = l_0$ ; +- if CSI is present for transmission on the PUSCH, let $l_2 = l_1$ ; +- if CG-UCI is present for transmission on the PUSCH without HARQ-ACK, let $l_2 = l_1$ ; +- let $l_3 = l_0$ and $l_4 = l_1$ . + +The multiplexed data and control coded bit sequence is obtained according to the following: + +#### **Step 1:** + +$$\text{Set } \bar{\Phi}_l^{\text{UL-SCH}} = \Phi_l^{\text{UL-SCH}} \text{ for } l;$$ + +$$\text{Set } \bar{M}_{\text{sc}}^{\text{UL-SCH}}(l) = |\bar{\Phi}_l^{\text{UL-SCH}}| \text{ for } l;$$ + +$$\text{Set } \bar{\Phi}_l^{\text{UCI}} = \Phi_l^{\text{UCI}} \text{ for } l;$$ + +$$\text{Set } \bar{M}_{\text{sc}}^{\text{UCI}}(l) = |\bar{\Phi}_l^{\text{UCI}}| \text{ for } l;$$ + +if the number of HARQ-ACK information bits to be transmitted on PUSCH is 0, 1 or 2 bits and without CG-UCI: + +the number of reserved resource elements for potential HARQ-ACK transmission is calculated according to + +$$\text{Clause 6.3.2.4.2.1, by setting } O_{\text{ACK}} = 2;$$ + +denote $G_{\text{rvd}}^{\text{ACK}}$ as the number of coded bits for potential HARQ-ACK transmission using the reserved resource elements; + +$$\text{if frequency hopping is configured for the PUSCH, let } G_{\text{rvd}}^{\text{ACK}}(1) = N_L \cdot Q_m \cdot \left\lceil G_{\text{rvd}}^{\text{ACK}} / (2 \cdot N_L \cdot Q_m) \right\rceil \text{ and } G_{\text{rvd}}^{\text{ACK}}(2) = N_L \cdot Q_m \cdot \left\lceil G_{\text{rvd}}^{\text{ACK}} / (2 \cdot N_L \cdot Q_m) \right\rceil;$$ + +$$\text{if frequency hopping is not configured for the PUSCH, let } G_{\text{rvd}}^{\text{ACK}}(1) = G_{\text{rvd}}^{\text{ACK}};$$ + +denote as the set of reserved resource elements for potential HARQ-ACK transmission, in OFDM symbol $l$ , for $l$ ; + +Set $\mathcal{R}_l$ ; + +Set $\mathcal{R}_l$ ; + +for $l$ ; + +for to + +; + +``` + +while $m_{\text{count}}^{\text{ACK}}(i) < G_{\text{rvd}}^{\text{ACK}}(i)$ + if $\bar{M}_{\text{sc}}^{\text{UCI}}(l) > 0$ + if $G_{\text{rvd}}^{\text{ACK}}(i) - m_{\text{count}}^{\text{ACK}}(i) \geq \bar{M}_{\text{sc}}^{\text{UCI}}(l) \cdot N_L \cdot Q_m$ + ; + $m_{\text{count}}^{\text{RE}} = \bar{M}_{\text{sc}}^{\text{UL-SCH}}(l)$ ; + end if + if $G_{\text{rvd}}^{\text{ACK}}(i) - m_{\text{count}}^{\text{ACK}}(i) < \bar{M}_{\text{sc}}^{\text{UCI}}(l) \cdot N_L \cdot Q_m$ + $d = \left\lceil \bar{M}_{\text{sc}}^{\text{UCI}}(l) \cdot N_L \cdot Q_m / (G_{\text{rvd}}^{\text{ACK}}(i) - m_{\text{count}}^{\text{ACK}}(i)) \right\rceil$ ; + $m_{\text{count}}^{\text{RE}} = \left\lceil (G_{\text{rvd}}^{\text{ACK}}(i) - m_{\text{count}}^{\text{ACK}}(i)) / (N_L \cdot Q_m) \right\rceil$ ; + end if + for to + $\bar{\Phi}_l^{\text{rvd}} = \bar{\Phi}_l^{\text{rvd}} \cup \{ \bar{\Phi}_l^{\text{UL-SCH}}(j \cdot d) \}$ + ; + end for + end if + ; +end while +end for + +``` + +else + +for ; + +end if + +Denote $n$ as the number of elements in $\bar{\Phi}_l^{\text{rvd}}$ . + +#### **Step 2:** + +if HARQ-ACK is present for transmission on the PUSCH and the number of HARQ-ACK information bits is more than 2 or if both HARQ-ACK and CG-UCI are present on the same PUSCH with UL-SCH: + +Set ; + +Set ; + +Set ; + +for to + +``` + +; +while + +``` + +``` + + if $\bar{M}_{\text{sc}}^{\text{UCI}}(l) > 0$ + if $G_{\text{rvd}}^{\text{ACK}}(i) - m_{\text{count}}^{\text{ACK}}(i) \geq \bar{M}_{\text{sc}}^{\text{UCI}}(l) \cdot N_L \cdot Q_m$ + ; + $m_{\text{count}}^{\text{RE}} = \bar{M}_{\text{sc}}^{\text{UCI}}(l)$ ; + end if + if $G_{\text{rvd}}^{\text{ACK}}(i) - m_{\text{count}}^{\text{ACK}}(i) < \bar{M}_{\text{sc}}^{\text{UCI}}(l) \cdot N_L \cdot Q_m$ + $d = \left\lceil \bar{M}_{\text{sc}}^{\text{UCI}}(l) \cdot N_L \cdot Q_m / (G_{\text{rvd}}^{\text{ACK}}(i) - m_{\text{count}}^{\text{ACK}}(i)) \right\rceil$ ; + ; + end if + for to + $k = \bar{\Phi}_l^{\text{UCI}}(j \cdot d)$ ; + end for + end if + +``` + +``` + + for to + : + : + : + : + end for + end for + $\bar{\Phi}_{l,tmp}^{UCI} = \emptyset$ ; + for to + $\bar{\Phi}_{l,tmp}^{UCI} = \bar{\Phi}_{l,tmp}^{UCI} \cup \bar{\Phi}_l^{UCI} (j \cdot d)$ ; + end for + $\bar{\Phi}_l^{UCI} = \bar{\Phi}_l^{UCI} \setminus \bar{\Phi}_{l,tmp}^{UCI}$ ; + $\bar{\Phi}_l^{UL-SCH} = \bar{\Phi}_l^{UL-SCH} \setminus \bar{\Phi}_{l,tmp}^{UCI}$ ; + $\bar{M}_{sc}^{UCI} (l) = |\bar{\Phi}_l^{UCI}|$ ; + $\bar{M}_{sc}^{UL-SCH} (l) = |\bar{\Phi}_l^{UL-SCH}|$ ; + end if + ; +end while +end for +end if + +``` + +#### **Step 2A:** + +If CG-UCI is present for transmission on the PUSCH without HARQ-ACK: + +``` + +Set ; +Set ; +Set ; +for to +; +while () +if + if + : + : + : + end if + if + : + : + : + end if + for to + : + for to + : + : + : + : + end for + end for + ; + for to + : + end for + : + : + : + : + +``` + +``` + + ; + end if + ; +end while +end for +end if + +``` + +#### **Step 3:** + +if CSI is present for transmission on the PUSCH: + +``` + +Set ; +Set ; +Set ; +for to +; +while $\bar{M}_{sc}^{UCI}(l) - \bar{M}_{sc, rvd}^{\bar{\Phi}}(l) \leq 0$ +; +end while +while +if $\bar{M}_{sc}^{UCI}(l) - \bar{M}_{sc, rvd}^{\bar{\Phi}}(l) > 0$ +if $G^{CSI-part1}(i) - m_{count}^{CSI-part1}(i) \geq (\bar{M}_{sc}^{UCI}(l) - \bar{M}_{sc, rvd}^{\bar{\Phi}}(l)) \cdot N_L \cdot Q_m$ +; + $m_{count}^{RE} = \bar{M}_{sc}^{UCI}(l) - \bar{M}_{sc, rvd}^{\bar{\Phi}}(l)$ +; +end if +if $G^{CSI-part1}(i) - m_{count}^{CSI-part1}(i) < (\bar{M}_{sc}^{UCI}(l) - \bar{M}_{sc, rvd}^{\bar{\Phi}}(l)) \cdot N_L \cdot Q_m$ + $d = \left\lceil (\bar{M}_{sc}^{UCI}(l) - \bar{M}_{sc, rvd}^{\bar{\Phi}}(l)) \cdot N_L \cdot Q_m / (G^{CSI-part1}(i) - m_{count}^{CSI-part1}(i)) \right\rceil$ +; +end if + $\bar{\Phi}_l^{temp} = \bar{\Phi}_l^{UCI} \setminus \bar{\Phi}_l^{rvd}$ +; +for to + $k = \bar{\Phi}_l^{temp}(j \cdot d)$ +; +for to +; +; +; +end for +end for + $\bar{\Phi}_{l,tmp}^{UCI} = \emptyset$ +; +for to + $\bar{\Phi}_{l,tmp}^{UCI} = \bar{\Phi}_{l,tmp}^{UCI} \cup \bar{\Phi}_l^{temp}(j \cdot d)$ +; +end for + $\bar{\Phi}_l^{UCI} = \bar{\Phi}_l^{UCI} \setminus \bar{\Phi}_{l,tmp}^{UCI}$ +; + $\bar{\Phi}_l^{UL-SCH} = \bar{\Phi}_l^{UL-SCH} \setminus \bar{\Phi}_{l,tmp}^{UCI}$ +; + $\bar{M}_{sc}^{UCI}(l) = |\bar{\Phi}_l^{UCI}|$ +; + $\bar{M}_{sc}^{UL-SCH}(l) = |\bar{\Phi}_l^{UL-SCH}|$ +; +end if + +``` + +``` + + ; + end while +end for +Set ; +Set ; +Set ; +for to + ; + while $\bar{M}_{sc}^{UCI}(l) \leq 0$ + ; + end while + while + if $\bar{M}_{sc}^{UCI}(l) > 0$ + if $G^{CSI-part2}(i) - m_{count}^{CSI-part2}(i) \geq \bar{M}_{sc}^{UCI}(l) \cdot N_L \cdot Q_m$ + ; + $m_{count}^{RE} = \bar{M}_{sc}^{UCI}(l)$ ; + end if + if $G^{CSI-part2}(i) - m_{count}^{CSI-part2}(i) < \bar{M}_{sc}^{UCI}(l) \cdot N_L \cdot Q_m$ + $d = \left\lceil \bar{M}_{sc}^{UCI}(l) \cdot N_L \cdot Q_m / (G^{CSI-part2}(i) - m_{count}^{CSI-part2}(i)) \right\rceil$ ; + ; + end if + for to + $k = \bar{\Phi}_l^{UCI}(j \cdot d)$ ; + for to + ; + ; + ; + ; + end for + end for + $\bar{\Phi}_{l,tmp}^{UCI} = \emptyset$ ; + for to + $\bar{\Phi}_{l,tmp}^{UCI} = \bar{\Phi}_{l,tmp}^{UCI} \cup \bar{\Phi}_l^{UCI}(j \cdot d)$ ; + end for + $\bar{\Phi}_l^{UCI} = \bar{\Phi}_l^{UCI} \setminus \bar{\Phi}_{l,tmp}^{UCI}$ ; + $\bar{\Phi}_l^{UL-SCH} = \bar{\Phi}_l^{UL-SCH} \setminus \bar{\Phi}_{l,tmp}^{UCI}$ ; + $\bar{M}_{sc}^{UCI}(l) = |\bar{\Phi}_l^{UCI}|$ ; + $\bar{M}_{sc}^{UL-SCH}(l) = |\bar{\Phi}_l^{UL-SCH}|$ ; + end if + ; + end while +end for +end if + +``` + +#### **Step 4:** + +if UL-SCH is present for transmission on the PUSCH: + +``` + +Set ; +for to + if $\bar{M}_{sc}^{UL-SCH}(l) > 0$ + for to $\bar{M}_{sc}^{UL-SCH}(l) - 1$ + $k = \bar{\Phi}_l^{UL-SCH}(j)$ ; + for to + ; + ; + end for + end for + end if +end for +end if + +``` + +#### Step 5: + +if HARQ-ACK is present for transmission on the PUSCH without CG-UCI and the number of HARQ-ACK information bits is no more than 2: + +``` + +Set ; +Set ; +Set ; +for to + ; + while + if $\bar{M}_{sc, rvd}^{\bar{\Phi}}(l) > 0$ + if $G^{ACK}(i) - m_{count}^{ACK}(i) \geq \bar{M}_{sc, rvd}^{\bar{\Phi}}(l) \cdot N_L \cdot Q_m$ + ; + $m_{count}^{RE} = \bar{M}_{sc, rvd}^{\bar{\Phi}}(l)$ ; + end if + if $G^{ACK}(i) - m_{count}^{ACK}(i) < \bar{M}_{sc, rvd}^{\bar{\Phi}}(l) \cdot N_L \cdot Q_m$ + $d = \left\lceil \bar{M}_{sc, rvd}^{\bar{\Phi}}(l) \cdot N_L \cdot Q_m / (G^{ACK}(i) - m_{count}^{ACK}(i)) \right\rceil$ ; + ; + end if + for to + $k = \bar{\Phi}_l^{rvd}(j \cdot d)$ ; + for to + ; + ; + ; + end for + end for + end if + ; + end while +end for +end if + +``` + +#### Step 6: + +Set ; + +for to + +for to $M_{sc}^{UL-SCH}(l) - 1$ + +$k = \Phi_l^{UL-SCH}(j)$ ; + +for to + +; + +; + +end for + +end for + +end for + +## 6.3 Uplink control information + +### 6.3.1 Uplink control information on PUCCH + +The procedure in this clause applies to PUCCH formats 2/3/4. + +The following clauses 6.3.1.2, 6.3.1.3 and 6.3.1.5 apply regardless of whether the higher layer parameter *uci-MuxWithDiffPrio* is configured or not. The following clauses 6.3.1.1, 6.3.1.4 and 6.3.1.6 apply by assuming *uci-MuxWithDiffPrio* is not configured, or *uci-MuxWithDiffPrio* is configured and the UCIs for transmission on a PUCCH are of the same priority index, unless stated otherwise. + +If the UE is configured with a PUCCH-SCell, *uci-MuxWithDiffPrio* is replaced by *uci-MuxWithDiffPrioSecondaryPUCCHgroup* for the secondary PUCCH group in this clause. + +#### 6.3.1.1 UCI bit sequence generation + +##### 6.3.1.1.1 HARQ-ACK/SR only + +If only HARQ-ACK bits are transmitted on a PUCCH, the UCI bit sequence $a_0, a_1, a_2, a_3, \dots, a_{A-1}$ is determined by setting $a_i = \tilde{o}_i^{ACK}$ for $i = 0, 1, \dots, O^{ACK} - 1$ and $A = O^{ACK}$ , where the HARQ-ACK bit sequence $\tilde{o}_0^{ACK}, \tilde{o}_1^{ACK}, \dots, \tilde{o}_{O^{ACK}-1}^{ACK}$ is given by Clause 9.1 of [5, TS38.213]. + +If only HARQ-ACK and SR bits are transmitted on a PUCCH, the UCI bit sequence $a_0, a_1, a_2, a_3, \dots, a_{A-1}$ is determined by setting $a_i = \tilde{o}_i^{ACK}$ for $i = 0, 1, \dots, O^{ACK} - 1$ , for $i = O^{ACK}, O^{ACK} + 1, \dots, O^{ACK} + O^{SR} - 1$ , and $A = O^{ACK} + O^{SR}$ , where the HARQ-ACK bit sequence $\tilde{o}_0^{ACK}, \tilde{o}_1^{ACK}, \dots, \tilde{o}_{O^{ACK}-1}^{ACK}$ is given by Clause 9.1 of [5, TS 38.213], and the SR bit sequence $\tilde{o}_0^{SR}, \tilde{o}_1^{SR}, \dots, \tilde{o}_{O^{SR}-1}^{SR}$ is given by Clause 9.2.5.1 of [5, TS 38.213]. + +##### 6.3.1.1.2 CSI only + +If *cqi-BitsPerSubband* is configured, this Clause 6.3.1.1.2 applies by taking Subband CQI as Subband differential CQI and replacing the corresponding number of bits 2 by 4. + +If *csi-ReportSubConfig* is configured, for a corresponding CSI sub-report, the bitwidth of a CSI field of the CSI sub-report is determined following the procedure in this clause 6.3.1.1.2 by taking configurations in *CSI-ReportSubConfig* when applicable. If *csi-ReportSubConfig* configures a list of CSI-RS resource IDs, for the determination of the bitwidth of a CRI field, the value of is the number of CSI-RS resources configured in the corresponding *csi-ReportSubConfig*. + +The bitwidth for PMI of *codebookType=typeI-SinglePanel* with 2 CSI-RS ports is 2 for Rank=1 and 1 for Rank=2, according to Clause 5.2.2.2.1 in [6, TS 38.214]. + +The bitwidth for PMI of *codebookType*=*typeI-SinglePanel* with more than 2 CSI-RS ports is provided in Table 6.3.1.1.2-1, where the values of $(N_1, N_2)$ and $(O_1, O_2)$ are given by Clause 5.2.2.2.1 in [6, TS 38.214]. + +**Table 6.3.1.1.2-1: PMI of *codebookType*=*typeI-SinglePanel*** + +| | Information field for wideband PMI | | | Information field for wideband PMI or per subband PMI | | +|----------------------------------------------------------------------------------|--------------------------------------------------------------------------|------------------------------------------------------------------------------------|-----------|-------------------------------------------------------|------------------------| +| | $(i_1)$ | | $i_{1,3}$ | $i_2$ | | +| | codebookMode =1 | codebookMode =2 | | codebookMode =1 | codebookMode =2 | +| Rank = 1 with >2 CSI-RS ports, | $(\lceil \log_2 N_1 O_1 \rceil, \lceil \log_2 N_2 O_2 \rceil)$ | $(\lceil \log_2 \frac{N_1 O_1}{2} \rceil, \lceil \log_2 \frac{N_2 O_2}{2} \rceil)$ | N/A | 2 | 4 | +| Rank = 1 with >2 CSI-RS ports, | $(\lceil \log_2 N_1 O_1 \rceil, \lceil \log_2 N_2 O_2 \rceil)$ | $(, 0)$ | N/A | 2 | 4 | +| Rank=2 with 4 CSI-RS ports, | $(\lceil \log_2 N_1 O_1 \rceil, \lceil \log_2 N_2 O_2 \rceil)$ | $(, 0)$ | 1 | 1 | 3 | +| Rank=2 with >4 CSI-RS ports, | $(\lceil \log_2 N_1 O_1 \rceil, \lceil \log_2 N_2 O_2 \rceil)$ | $(\lceil \log_2 \frac{N_1 O_1}{2} \rceil, \lceil \log_2 \frac{N_2 O_2}{2} \rceil)$ | 2 | 1 | 3 | +| Rank=2 with >4 CSI-RS ports, | $(\lceil \log_2 N_1 O_1 \rceil, \lceil \log_2 N_2 O_2 \rceil)$ | $(, 0)$ | 2 | 1 | 3 | +| Rank=3 or 4, with 4 CSI-RS ports | $(\lceil \log_2 N_1 O_1 \rceil, \lceil \log_2 N_2 O_2 \rceil)$ | | 0 | 1 | | +| Rank=3 or 4, with 8 or 12 CSI-RS ports | $(\lceil \log_2 N_1 O_1 \rceil, \lceil \log_2 N_2 O_2 \rceil)$ | | 2 | 1 | | +| Rank=3 or 4, with >=16 CSI-RS ports | $(\lceil \log_2 \frac{N_1 O_1}{2} \rceil, \lceil \log_2 N_2 O_2 \rceil)$ | | 2 | 1 | | +| Rank=5 or 6 | $(\lceil \log_2 N_1 O_1 \rceil, \lceil \log_2 N_2 O_2 \rceil)$ | | N/A | 1 | | +| Rank=7 or 8, $N_1 = 4, N_2 = 1$ | $(\lceil \log_2 \frac{N_1 O_1}{2} \rceil, \lceil \log_2 N_2 O_2 \rceil)$ | | N/A | 1 | | +| Rank=7 or 8, $N_1 > 2, N_2 = 2$ | $(\lceil \log_2 N_1 O_1 \rceil, \lceil \log_2 \frac{N_2 O_2}{2} \rceil)$ | | N/A | 1 | | +| Rank=7 or 8, with $N_1 > 4, N_2 = 1$ or $N_1 = 2, N_2 = 2$ or $N_1 > 2, N_2 > 2$ | $(\lceil \log_2 N_1 O_1 \rceil, \lceil \log_2 N_2 O_2 \rceil)$ | | N/A | 1 | | + +The bitwidth for PMI of *codebookType*=*typeI-MultiPanel* is provided in Table 6.3.1.1.2-2, where the values of $(N_g, N_1, N_2)$ and are given by Clause 5.2.2.2.2 in [6, TS 38.214]. + +**Table 6.3.1.1.2-2: PMI of *codebookType*= *typeI-MultiPanel*** + +| | Information fields for wideband | | | | | Information fields for wideband or per subband | | | | +|----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|-----|---|-----|-----|------------------------------------------------|-----|-----|-----| +| | ( i 1 ) | | | | | i 2 | | | | +| Rank=1 with codebookMode =1 | $\left( \begin{array}{c} \lceil \log_2 N_1 O_1 \rceil \\ \lceil \log_2 N_2 O_2 \rceil \end{array} \right)$ | N/A | 2 | N/A | N/A | 2 | N/A | N/A | N/A | +| Rank=1 with codebookMode =1 | $\left( \begin{array}{c} \lceil \log_2 N_1 O_1 \rceil \\ \lceil \log_2 N_2 O_2 \rceil \end{array} \right)$ | N/A | 2 | 2 | 2 | 2 | N/A | N/A | N/A | +| Rank=2 with , $N_1 N_2 = 2$ , codebookMode =1 | $\left( \begin{array}{c} \lceil \log_2 N_1 O_1 \rceil \\ \lceil \log_2 N_2 O_2 \rceil \end{array} \right)$ | 1 | 2 | N/A | N/A | 1 | N/A | N/A | N/A | +| Rank=3 or 4 with , $N_1 N_2 = 2$ , codebookMode =1 | $\left( \begin{array}{c} \lceil \log_2 N_1 O_1 \rceil \\ \lceil \log_2 N_2 O_2 \rceil \end{array} \right)$ | 0 | 2 | N/A | N/A | 1 | N/A | N/A | N/A | +| Rank=2 or 3 or 4 with , $N_1 N_2 > 2$ , codebookMode =1 | $\left( \begin{array}{c} \lceil \log_2 N_1 O_1 \rceil \\ \lceil \log_2 N_2 O_2 \rceil \end{array} \right)$ | 2 | 2 | N/A | N/A | 1 | N/A | N/A | N/A | +| Rank=2 with , $N_1 N_2 = 2$ , codebookMode =1 | $\left( \begin{array}{c} \lceil \log_2 N_1 O_1 \rceil \\ \lceil \log_2 N_2 O_2 \rceil \end{array} \right)$ | 1 | 2 | 2 | 2 | 1 | N/A | N/A | N/A | +| Rank=3 or 4 with , $N_1 N_2 = 2$ , codebookMode =1 | $\left( \begin{array}{c} \lceil \log_2 N_1 O_1 \rceil \\ \lceil \log_2 N_2 O_2 \rceil \end{array} \right)$ | 0 | 2 | 2 | 2 | 1 | N/A | N/A | N/A | +| Rank=2 or 3 or 4 with , $N_1 N_2 > 2$ , codebookMode =1 | $\left( \begin{array}{c} \lceil \log_2 N_1 O_1 \rceil \\ \lceil \log_2 N_2 O_2 \rceil \end{array} \right)$ | 2 | 2 | 2 | 2 | 1 | N/A | N/A | N/A | +| Rank=1 with codebookMode =2 | $\left( \begin{array}{c} \lceil \log_2 N_1 O_1 \rceil \\ \lceil \log_2 N_2 O_2 \rceil \end{array} \right)$ | N/A | 2 | 2 | N/A | N/A | 2 | 1 | 1 | +| Rank=2 with , $N_1 N_2 = 2$ , codebookMode =2 | $\left( \begin{array}{c} \lceil \log_2 N_1 O_1 \rceil \\ \lceil \log_2 N_2 O_2 \rceil \end{array} \right)$ | 1 | 2 | 2 | N/A | N/A | 1 | 1 | 1 | +| Rank=3 or 4 with , $N_1 N_2 = 2$ , codebookMode =2 | $\left( \begin{array}{c} \lceil \log_2 N_1 O_1 \rceil \\ \lceil \log_2 N_2 O_2 \rceil \end{array} \right)$ | 0 | 2 | 2 | N/A | N/A | 1 | 1 | 1 | +| Rank=2 or 3 or 4 with , $N_1 N_2 > 2$ , codebookMode =2 | $\left( \begin{array}{c} \lceil \log_2 N_1 O_1 \rceil \\ \lceil \log_2 N_2 O_2 \rceil \end{array} \right)$ | 2 | 2 | 2 | N/A | N/A | 1 | 1 | 1 | + +The bitwidth for PMI with 1 CSI-RS port is 0. + +The bitwidth for RI/LI/CQI/CRI of *codebookType*=*typeI-SinglePanel* or *reportQuantity* set to 'cri-RI-CQI' or 1 CSI-RS port is provided in Table 6.3.1.1.2-3. + +**Table 6.3.1.1.2-3: RI, LI, CQI, and CRI of *codebookType=typeI-SinglePanel*, or *reportQuantity* set to 'cri-RI-CQI', or 1 CSI-RS port** + +| Field | Bitwidth | | | | | +|---------------------------------------------------------------|----------------|----------------------------|-------------------------------------|-------------------------------------|-------------------------------------| +| | 1 antenna port | 2 antenna ports | 4 antenna ports | >4 antenna ports | | +| | | | | Rank1~4 | Rank5~8 | +| Rank Indicator when codebookType=typeI-SinglePanel | 0 | | | | | +| Rank Indicator when reportQuantity set to 'cri-RI-CQI' | 0 | 1 | 2 | 3 | 3 | +| Layer Indicator | 0 | $\lceil \log_2 \nu \rceil$ | $\min(2, \lceil \log_2 \nu \rceil)$ | $\min(2, \lceil \log_2 \nu \rceil)$ | $\min(2, \lceil \log_2 \nu \rceil)$ | +| Wide-band CQI for the first TB | 4 | 4 | 4 | 4 | 4 | +| Wideband CQI for the second TB | 0 | 0 | 0 | 0 | 4 | +| Subband differential CQI for the first TB | 2 | 2 | 2 | 2 | 2 | +| Subband differential CQI for the second TB | 0 | 0 | 0 | 0 | 2 | +| CRI | | | | | | + +in Table 6.3.1.1.2-3 is the number of allowed rank indicator values according to Clause 5.2.2.2.1 [6, TS 38.214]. $\nu$ is the value of the rank. The value of $\nu$ is the number of CSI-RS resources in the corresponding resource set. The values of the rank indicator field are mapped to allowed rank indicator values with increasing order, where '0' is mapped to the smallest allowed rank indicator value. For higher layer parameter *reportQuantity* set to 'cri-RI-CQI', the values of the rank indicator field are mapped to rank indicator values with increasing order, where '0' is mapped to rank-1. + +**Table 6.3.1.1.2-3A: RI, LI, CQI, and CRI associated with one CSI-RS resource pair and *csi-ReportMode= Mode 1* or *Mode 2*** + +| Field | Bitwidth | | +|-------------------------------------------|-----------------------------|--------------------------------| +| | 1 antenna port per Resource | > 1 antenna ports per Resource | +| Rank Combination Indicator | 0 | | +| The first Layer Indicator | 0 | | +| The second Layer Indicator | 0 | | +| Wide-band CQI for the first TB | 4 | 4 | +| Subband differential CQI for the first TB | 2 | 2 | +| CRI if csi-ReportMode= Mode 1 | | | +| CRI if csi-ReportMode= Mode 2 | | | + +**Table 6.3.1.1.2-3B: RI, LI, CQI, and CRI associated with one CSI-RS resource and *csi-ReportMode= Mode 1 or Mode 2*** + +| Field | Bitwidth | | | | | | +|---------------------------------------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|--| +| | 1 antenna port | 2 antenna ports | 4 antenna ports | >4 antenna ports | | | +| | | | | Rank1~4 | Rank5~8 | | +| Rank Indicator | 0 | | | | | | +| Layer Indicator | 0 | | | | | | +| Wide-band CQI for the first TB | 4 | 4 | 4 | 4 | 4 | | +| Wideband CQI for the second TB | 0 | 0 | 0 | 0 | 4 | | +| Subband differential CQI for the first TB | 2 | 2 | 2 | 2 | 2 | | +| Subband differential CQI for the second TB | 0 | 0 | 0 | 0 | 2 | | +| CRI if csi-ReportMode= Mode 1 and numberOfSingleTR P-CSI-Mode1 = 1 | | | | | | | +| CRI if csi-ReportMode= Mode 1 and numberOfSingleTR P-CSI-Mode1 = 2 | for the first CRI;
for the second CRI | for the first CRI;
for the second CRI | for the first CRI;
for the second CRI | for the first CRI;
for the second CRI | for the first CRI;
for the second CRI | | +| CRI if csi-ReportMode= Mode 2 | | | | | | | + +in Table 6.3.1.1.2-3A is the number of allowed rank combination indicator values associated with one CSI-RS resource pair according to Clause 5.2.1.4.2 [6, TS 38.214]. The values of the rank combination indicator field are mapped to allowed rank combinations in the following order: {1,1}, {1,2}, {2,1}, {2,2}, where '0' is mapped to the first allowed rank combination. $v$ and $w$ are the values of the first and the second rank associated with two CSI-RS resources of the CSI-RS resource pair respectively. + +in Table 6.3.1.1.2-3B is the number of allowed rank indicator values associated with one CSI-RS resource according to Clause 5.2.1.4.2 [6, TS 38.214]. $v$ is the value of the rank associated with the CSI-RS resource. The values of the rank indicator field are mapped to allowed rank indicator values with increasing order, where '0' is mapped to the smallest allowed rank indicator value. + +The value of $N$ in Table 6.3.1.1.2-3A and Table 6.3.1.1.2-3B is the number of CSI-RS resource pairs configured within a CSI-RS resource set. The values of $M_1$ and $M_2$ in Table 6.3.1.1.2-3A and Table 6.3.1.1.2-3B are given by + +- If *sharedCMR* = "Enabled", $M_1 = K_1$ and $M_2 = K_2$ +- If *sharedCMR* is absent and $N = 1$ , $M_1 = K_1 - 1$ and $M_2 = K_2 - 1$ +- If *sharedCMR* is absent and $N = 2$ , + - $M_1 = K_1 - 2$ and $M_2 = K_2 - 2$ , if the two resource pairs do not share any CSI-RS resource + - $M_1 = K_1 - 1$ and $M_2 = K_2 - 2$ , if the two resource pairs share the same CSI-RS resource from the first CSI-RS resource group + - $M_1 = K_1 - 2$ and $M_2 = K_2 - 1$ , if the two resource pairs share the same CSI-RS resource from the second CSI-RS resource group + +where the values of $K_1$ and $K_2$ are the numbers of CSI-RS resources in the first and second CSI-RS resource groups within the CSI-RS resource set respectively. + +The bitwidth for RI/LI/CQI/CRI of *codebookType= typeI-MultiPanel* is provided in Table 6.3.1.1.2-4. + +**Table 6.3.1.1.2-4: RI, LI, CQI, and CRI of *codebookType*=*typeI-MultiPanel*** + +| Field | Bitwidth | +|--------------------------|-------------------------------------| +| Rank Indicator | | +| Layer Indicator | $\min(2, \lceil \log_2 \nu \rceil)$ | +| Wide-band CQI | 4 | +| Subband differential CQI | 2 | +| CRI | | + +where $\nu$ is the number of allowed rank indicator values according to Clause 5.2.2.2.2 [6, TS 38.214], $\nu$ is the value of the rank, and $\nu$ is the number of CSI-RS resources in the corresponding resource set. The values of the rank indicator field are mapped to allowed rank indicator values with increasing order, where '0' is mapped to the smallest allowed rank indicator value. + +The bitwidth for RI/LI/CQI of *codebookType*=*typeII* or *codebookType*=*typeII-PortSelection* is provided in Table 6.3.1.1.2-5. + +**Table 6.3.1.1.2-5: RI, LI, and CQI of *codebookType*=*typeII* or *typeII-PortSelection*** + +| Field | Bitwidth | +|-------------------------------------------------------------------------------|-------------------------------------| +| Rank Indicator | | +| Layer Indicator | $\min(2, \lceil \log_2 \nu \rceil)$ | +| Wide-band CQI | 4 | +| Subband differential CQI | 2 | +| Indicator of the number of non-zero wideband amplitude coefficients for layer | | + +where $\nu$ is the number of allowed rank indicator values according to Clauses 5.2.2.2.3 and 5.2.2.2.4 [6, TS 38.214] and $\nu$ is the value of the rank. The values of the rank indicator field are mapped to allowed rank indicator values with increasing order, where '0' is mapped to the smallest allowed rank indicator value. + +The bitwidth for CRI, SSBRI, RSRP, differential RSRP, and CapabilityIndex are provided in Table 6.3.1.1.2-6. + +**Table 6.3.1.1.2-6: CRI, SSBRI, RSRP, and CapabilityIndex** + +| Field | Bitwidth | +|-------------------|----------| +| CRI | | +| SSBRI | | +| RSRP | 7 | +| Differential RSRP | 4 | +| CapabilityIndex | 2 | + +where $\nu$ is the number of CSI-RS resources in the corresponding resource set, and $\nu$ is the configured number of SS/PBCH blocks in the corresponding resource set for reporting 'ssb-Index-RSRP'. + +The bitwidth for CRI, SSBRI, SINR, differential SINR, and CapabilityIndex are provided in Table 6.3.1.1.2-6A. + +**Table 6.3.1.1.2-6A: CRI, SSBRI, SINR, and CapabilityIndex** + +| Field | Bitwidth | +|-------------------|----------| +| CRI | | +| SSBRI | | +| SINR | 7 | +| Differential SINR | 4 | +| CapabilityIndex | 2 | + +where $N_{CSI}$ is the number of CSI-RS resources in the corresponding resource set, and $N_{SS}$ is the configured number of SS/PBCH blocks in the corresponding resource set for reporting 'ssb-Index-SINR'. + +If *csi-ReportSubConfig* is configured, for a corresponding CSI sub-report, the mapping order of CSI fields of one CSI sub-report is determined following the procedure in this clause 6.3.1.1.2, by replacing CSI report #n in the following Tables 6.3.1.1.2-7, 6.3.1.1.2-9 and 6.3.1.1.2-10 with CSI sub-report #n, and taking only Tables 6.3.1.1.2-1/2/3/4 for the determination of the bitwidth of a CSI field. + +**Table 6.3.1.1.2-7: Mapping order of CSI fields of one CSI report, *pmi-FormatIndicator=widebandPMI* and *cqi-FormatIndicator=widebandCQI* or *reportQuantity* set to 'cri-RI-CQI' and *cqi-FormatIndicator=widebandCQI*** + +| CSI report number | CSI fields | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n | CRI as in Tables 6.3.1.1.2-3/4, if reported | +| | Rank Indicator as in Tables 6.3.1.1.2-3/4, if reported | +| | Layer Indicator as in Tables 6.3.1.1.2-3/4, if reported | +| | Zero padding bits , if needed | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1/2, if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1/2, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214], if reported | +| | Wideband CQI for the first TB as in Tables 6.3.1.1.2-3/4, if reported | +| | Wideband CQI for the second TB as in Tables 6.3.1.1.2-3/4, if reported | + +The number of zero padding bits in Table 6.3.1.1.2-7 is 0 for 1 CSI-RS port and for more than 1 CSI-RS port, where: + +- $N_{RS}$ and $N_{ports}$ is the set of rank values that are allowed to be reported; +- $\hat{r}$ , where $\hat{r}$ is the reported rank; +- For 2 CSI-RS ports, $\hat{r} \leq 2$ ; +- For more than 2 CSI-RS ports, $\hat{r} \leq 4$ ; +- if PMI is reported, $\hat{r} \leq N_{ports}$ ; otherwise, $\hat{r} = 0$ ; +- if PMI is reported, $\hat{r}$ is obtained according to Tables 6.3.1.1.2-1/2; otherwise, $\hat{r} = 0$ ; +- if PMI is reported, $\hat{r}$ is obtained according to Tables 6.3.1.1.2-1/2; otherwise, $\hat{r} = 0$ ; +- if CQI is reported, $\hat{r}$ is obtained according to Tables 6.3.1.1.2-3/4; otherwise, $\hat{r} = 0$ ; +- if LI is reported, $\hat{r}$ is obtained according to Tables 6.3.1.1.2-3/4; otherwise, $\hat{r} = 0$ . + +**Table 6.3.1.1.2-7A: Mapping order of CSI fields of one CSI report, *pmi-FormatIndicator=widebandPMI*, *cqi-FormatIndicator=widebandCQI*, *csi-ReportMode= Mode 1* and *numberOfSingleTRP-CSI-Mode1=0*** + +| CSI report number | CSI fields | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n | CRI as in Tables 6.3.1.1.2-3A, if reported | +| | Rank Combination Indicator as in Tables 6.3.1.1.2-3A, if reported | +| | Two Layer Indicators as in Table 6.3.1.1.2-3A, where the first Layer Indicator and the second Layer Indicator are associated with the first resource and the second resource within the resource pair respectively and if reported; | +| | Zero padding bits , if needed | +| | PMI wideband information fields $X_1$ , from left to right as in Tables 6.3.1.1.2-1 associated with the first resource within the CSI-RS resource pair, if reported | +| | PMI wideband information fields $X_2$ , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] associated with the first CSI-RS resource within the CSI-RS resource pair, if reported | +| | PMI wideband information fields $X_1$ , from left to right as in Tables 6.3.1.1.2-1 associated with the second resource within the CSI-RS resource pair, if reported | +| | PMI wideband information fields $X_2$ , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] associated with the second CSI-RS resource within the CSI-RS resource pair, if reported | +| | Wideband CQI for the first TB as in Tables 6.3.1.1.2-3A, if reported | + +The number of zero padding bits in Table 6.3.1.1.2-7A is 0 for 1 CSI-RS port and for more than 1 CSI-RS port, where: + +- and $\mathcal{R}$ is the set of rank combination values of $\mathcal{R}$ that are allowed to be reported; +- where $\mathcal{R}$ is the reported rank combination; +- For 2 CSI-RS ports, $\mathcal{R}$ ; +- For more than 2 CSI-RS ports, $\mathcal{R}$ ; +- if PMI is reported, $\mathcal{R}$ and $\mathcal{R}$ ; otherwise,; +- if PMI is reported, $\mathcal{R}$ and $\mathcal{R}$ are obtained according to Tables 6.3.1.1.2-1; otherwise, ; +- if PMI is reported, $\mathcal{R}$ and $\mathcal{R}$ are obtained according to Tables 6.3.1.1.2-1; otherwise, ; +- if CQI is reported, $\mathcal{R}$ is obtained according to Tables 6.3.1.1.2-3A; otherwise,; +- if LI is reported, $\mathcal{R}$ and $\mathcal{R}$ are obtained according to Tables 6.3.1.1.2-3A; otherwise , . + +**Table 6.3.1.1.2-8: Mapping order of CSI fields of one report for CRI/RSRP or SSBRI/RSRP or CRI/RSRP/CapabilityIndex or SSBRI/RSRP/CapabilityIndex reporting, or mapping order of CSI fields of one report for inter-cell SSBRI/RSRP reporting** + +| CSI report number | CSI fields | +|-------------------|-----------------------------------------------------------| +| CSI report #n | CRI or SSBRI #1 as in Table 6.3.1.1.2-6, if reported | +| | CRI or SSBRI #2 as in Table 6.3.1.1.2-6, if reported | +| | CRI or SSBRI #3 as in Table 6.3.1.1.2-6, if reported | +| | CRI or SSBRI #4 as in Table 6.3.1.1.2-6, if reported | +| | RSRP #1 as in Table 6.3.1.1.2-6, if reported | +| | Differential RSRP #2 as in Table 6.3.1.1.2-6, if reported | +| | Differential RSRP #3 as in Table 6.3.1.1.2-6, if reported | +| | Differential RSRP #4 as in Table 6.3.1.1.2-6, if reported | +| | CapabilityIndex #1 as in Table 6.3.1.1.2-6, if reported | +| | CapabilityIndex #2 as in Table 6.3.1.1.2-6, if reported | +| | CapabilityIndex #3 as in Table 6.3.1.1.2-6, if reported | +| | CapabilityIndex #4 as in Table 6.3.1.1.2-6, if reported | + +**Table 6.3.1.1.2-8A: Mapping order of CSI fields of one report for CRI/SINR or SSBRI/SINR or CRI/SINR/CapabilityIndex or SSBRI/SINR/CapabilityIndex reporting** + +| CSI report number | CSI fields | +|-------------------|------------------------------------------------------------| +| CSI report #n | CRI or SSBRI #1 as in Table 6.3.1.1.2-6A, if reported | +| | CRI or SSBRI #2 as in Table 6.3.1.1.2-6A, if reported | +| | CRI or SSBRI #3 as in Table 6.3.1.1.2-6A, if reported | +| | CRI or SSBRI #4 as in Table 6.3.1.1.2-6A, if reported | +| | SINR #1 as in Table 6.3.1.1.2-6A, if reported | +| | Differential SINR #2 as in Table 6.3.1.1.2-6A, if reported | +| | Differential SINR #3 as in Table 6.3.1.1.2-6A, if reported | +| | Differential SINR #4 as in Table 6.3.1.1.2-6A, if reported | +| | CapabilityIndex #1 as in Table 6.3.1.1.2-6, if reported | +| | CapabilityIndex #2 as in Table 6.3.1.1.2-6, if reported | +| | CapabilityIndex #3 as in Table 6.3.1.1.2-6, if reported | +| | CapabilityIndex #4 as in Table 6.3.1.1.2-6, if reported | + +**Table 6.3.1.1.2-8B: Mapping order of CSI fields of one report for group-based CRI/RSRP or SSBR/RSRP reporting** + +| CSI report number | CSI fields | +|-------------------|------------------------------------------------------------------------------------------------| +| CSI report #n | Resource set indicator | +| | CRI or SSBR #1 of 1st resource group as in Table 6.3.1.1.2-6, if reported | +| | CRI or SSBR #2 of 1st resource group as in Table 6.3.1.1.2-6, if reported | +| | CRI or SSBR #1 of 2nd resource group as in Table 6.3.1.1.2-6, if reported | +| | CRI or SSBR #2 of 2nd resource group as in Table 6.3.1.1.2-6, if reported | +| | CRI or SSBR #1 of 3rd resource group as in Table 6.3.1.1.2-6, if reported | +| | CRI or SSBR #2 of 3rd resource group as in Table 6.3.1.1.2-6, if reported | +| | CRI or SSBR #1 of 4th resource group as in Table 6.3.1.1.2-6, if reported | +| | CRI or SSBR #2 of 4th resource group as in Table 6.3.1.1.2-6, if reported | +| | RSRP of CRI or SSBR #1 of 1st resource group as in Table 6.3.1.1.2-6 | +| | Differential RSRP of CRI or SSBR #2 of 1st resource group as in Table 6.3.1.1.2-6 | +| | Differential RSRP of CRI or SSBR #1 of 2nd resource group as in Table 6.3.1.1.2-6, if reported | +| | Differential RSRP of CRI or SSBR #2 of 2nd resource group as in Table 6.3.1.1.2-6, if reported | +| | Differential RSRP of CRI or SSBR #1 of 3rd resource group as in Table 6.3.1.1.2-6, if reported | +| | Differential RSRP of CRI or SSBR #2 of 3rd resource group as in Table 6.3.1.1.2-6, if reported | +| | Differential RSRP of CRI or SSBR #1 of 4th resource group as in Table 6.3.1.1.2-6, if reported | +| | Differential RSRP of CRI or SSBR #2 of 4th resource group as in Table 6.3.1.1.2-6, if reported | + +where the 1-bit resource set indicator, with value of 0 or 1, indicates the 1st or the 2nd channel measurement resource set respectively, from which CRI or SSBR #1 of 1st resource group is reported from; and all remaining resource groups, if reported, follow the same mapping order as the 1st resource group where CRI or SSBR #1 of all remaining resource groups is reported from the indicated channel measurement resource set. For all reported resource groups, CRI or SSBR #1 and CRI or SSBR #2 are reported from different channel measurement resource sets. + +**Table 6.3.1.1.2-8C: Mapping order of CSI fields of one report for SSBR/RSRP reporting for L1/L2-triggered mobility** + +| CSI report number | CSI fields | +|-------------------|-----------------------------------------------------------| +| CSI report #n | SSBR #1 as in Table 6.3.1.1.2-6, if reported | +| | SSBR #2 as in Table 6.3.1.1.2-6, if reported | +| | ... | +| | SSBR # as in Table 6.3.1.1.2-6, if reported | +| | RSRP #1 as in Table 6.3.1.1.2-6, if reported | +| | Differential RSRP #2 as in Table 6.3.1.1.2-6, if reported | +| | ... | +| | Differential RSRP # as in Table 6.3.1.1.2-6, if reported | + +NOTE: *L* is the number of reported cells provided by higher layer parameter *noOfReportedCell* and *M* is the number of reported SSBR/RSRP pairs per cell and equal to the value provided by higher layer parameter *nrofReportedRSPerCell*. + +**Table 6.3.1.1.2-9: Mapping order of CSI fields of one CSI report, CSI part 1, *pmi-FormatIndicator=subbandPMI* or *cqi-FormatIndicator=subbandCQI*** + +| CSI report number | CSI fields | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
CSI part 1 | CRI as in Tables 6.3.1.1.2-3/4, if reported | +| | Rank Indicator as in Tables 6.3.1.1.2-3/4/5, if reported | +| | Wideband CQI for the first TB as in Tables 6.3.1.1.2-3/4/5, if reported | +| | Subband differential CQI for the first TB with increasing order of subband number as in Tables 6.3.1.1.2-3/4/5, if reported | +| | Indicator of the number of non-zero wideband amplitude coefficients for layer 0 as in Table 6.3.1.1.2-5, if reported | +| | Indicator of the number of non-zero wideband amplitude coefficients for layer 1 as in Table 6.3.1.1.2-5 (if the rank according to the reported RI is equal to one, this field is set to all zeros), if 2-layer PMI reporting is allowed according to the rank restriction in Clauses 5.2.2.2.3 and 5.2.2.2.4 [6, TS 38.214] and if reported | +| NOTE: Subbands for given CSI report n indicated by the higher layer parameter csi-ReportingBand with value set to '1' are numbered continuously in the increasing order with the lowest subband of csi-ReportingBand with value set to '1' as subband 0. | | + +**Table 6.3.1.1.2-9A: Mapping order of CSI fields of one CSI report, CSI part 1, *csi-ReportMode= Mode 1*** + +| CSI report number | CSI fields | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
CSI part 1 | CRI as in Tables 6.3.1.1.2-3A, if associated with one CSI-RS resource pair and if reported | +| | Rank Combination Indicator as in Tables 6.3.1.1.2-3A, if reported | +| | Wideband CQI for the first TB as in Tables 6.3.1.1.2-3A, if reported | +| | Subband differential CQI for the first TB with increasing order of subband number as in Tables 6.3.1.1.2-3A, if reported | +| | CRI as in Tables 6.3.1.1.2-3B, if associated with one CSI-RS resource, numberOfSingleTRP-CSI-Mode1 = 1 and if reported;
First CRI as in Tables 6.3.1.1.2-3B, if associated with one CSI-RS resource, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | Rank Indicator associated with CRI as in Tables 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 1 and if reported;
Rank Indicator associated with the first CRI as in Tables 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | Wideband CQI associated with CRI for the first TB as in Tables 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 1 and if reported;
Wideband CQI associated with the first CRI for the first TB as in Tables 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | Subband differential CQI associated with CRI for the first TB with increasing order of subband number as in Tables 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 1 if reported;
Subband differential CQI associated with the first CRI for the first TB with increasing order of subband number as in Tables 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | Second CRI as in Tables 6.3.1.1.2-3B, if associated with one CSI-RS resource, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | Rank Indicator associated with the second CRI as in Tables 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | Wideband CQI associated with the second CRI for the first TB as in Tables 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | Subband differential CQI associated with the second CRI for the first TB with increasing order of subband number as in Tables 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| NOTE: Subbands for given CSI report n indicated by the higher layer parameter csi-ReportingBand with value set to '1' are numbered continuously in the increasing order with the lowest subband of csi-ReportingBand with value set to '1' as subband 0. | | + +**Table 6.3.1.1.2-9B: Mapping order of CSI fields of one CSI report, CSI part 1, *csi-ReportMode= Mode 2*** + +| CSI report number | CSI fields | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
CSI part 1 | CRI as in Tables 6.3.1.1.2-3A, if associated with one CSI-RS resource pair and if reported;
CRI as in Tables 6.3.1.1.2-3B, if associated with one CSI-RS resource and if reported | +| | Rank Combination Indicator as in Tables 6.3.1.1.2-3A, if associated with one CSI-RS resource pair and if reported;
Rank Indicator as in Tables 6.3.1.1.2-3B, if associated with one CSI-RS resource and if reported;
Zero padding bits , if needed | +| | Wideband CQI for the first TB as in Tables 6.3.1.1.2-3A, if associated with one CSI-RS resource pair and if reported;
Wideband CQI for the first TB as in Tables 6.3.1.1.2-3B, if associated with one CSI-RS resource and if reported | +| | Subband differential CQI for the first TB with increasing order of subband number as in Tables 6.3.1.1.2-3A, if associated with one CSI-RS resource pair and if reported;
Subband differential CQI for the first TB with increasing order of subband number as in Tables 6.3.1.1.2-3B, if associated with one CSI-RS resource and if reported | + +NOTE: Subbands for given CSI report *n* indicated by the higher layer parameter *csi-ReportingBand* with value set to '1' are numbered continuously in the increasing order with the lowest subband of *csi-ReportingBand* with value set to '1' as subband 0. + +The number of zero padding bits in Table 6.3.1.1.2-9B is 0 for 1 CSI-RS port and for more than 1 CSI-RS port, where: + +- $\mathcal{R}$ is the set of rank and rank combination values *r* that are allowed to be reported. $\mathcal{R}$ is obtained according to Tables 6.3.1.1.2-3A/3B for rank combination indicator and rank indicator respectively. +- $\mathcal{R}$ is obtained according to Tables 6.3.1.1.2-3A for rank combination indicator and *R* is the reported rank combination. +- $\mathcal{R}$ is obtained according to Tables 6.3.1.1.2-3B for rank indicator and *R* is the reported rank. + +**Table 6.3.1.1.2-10: Mapping order of CSI fields of one CSI report, CSI part 2 wideband, *pmi-FormatIndicator= subbandPMI* or *cqi-FormatIndicator=subbandCQI*** + +| CSI report number | CSI fields | +|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
CSI part 2
wideband | Wideband CQI for the second TB as in Tables 6.3.1.1.2-3/4/5, if present and reported | +| | Layer Indicator as in Tables 6.3.1.1.2-3/4/5, if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1/2, if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1/2, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214], if pmi-FormatIndicator= widebandPMI and if reported | + +**Table 6.3.1.1.2-10A: Mapping order of CSI fields of one CSI report, +CSI part 2 wideband, *csi-ReportMode*= *Mode 1*** + +| CSI report number | CSI fields | +|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
CSI part 2
wideband | Two Layer Indicators as in Table 6.3.1.1.2-3A, where the first Layer Indicator and the second Layer Indicator are associated with the first resource and the second resource within the resource pair respectively and if reported; | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1 associated with the first resource within the CSI-RS resource pair, if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] associated with the first CSI-RS resource within the CSI-RS resource pair, if pmi-FormatIndicator = widebandPMI and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1 associated with the second resource within the CSI-RS resource pair, if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] associated with the second CSI-RS resource within the CSI-RS resource pair, if pmi-FormatIndicator = widebandPMI and if reported | +| | Wideband CQI for the second TB as in Tables 6.3.1.1.2-3B, if associated with CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 1 and if reported; | +| | Wideband CQI for the second TB as in Tables 6.3.1.1.2-3B, if associated with the first CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | Layer Indicator as in Table 6.3.1.1.2-3B, if associated with CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 1 and if reported; | +| | Layer Indicator as in Table 6.3.1.1.2-3B, if associated with the first CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, if associated with CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 1 and if reported; | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, if associated with the first CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214], if associated with CRI in CSI part 1, pmi-FormatIndicator = widebandPMI , numberOfSingleTRP-CSI-Mode1 = 1 and if reported; | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214], if associated with the first CRI in CSI part 1, pmi-FormatIndicator = widebandPMI , numberOfSingleTRP-CSI-Mode1 = 2 and if reported | + +**Table 6.3.1.1.2-10B: Mapping order of CSI fields of one CSI report, CSI part 2 wideband, *csi-ReportMode= Mode 2*** + +| CSI report number | CSI fields | +|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
CSI part 2 wideband | Wideband CQI for the second TB as in Tables 6.3.1.1.2-3B, if reported part 1 is associated with one CSI-RS resource and if reported | +| | Two Layer Indicators as in Table 6.3.1.1.2-3A, if reported part 1 is associated with one CSI-RS resource pair, where the first Layer Indicator and the second Layer Indicator are associated with the first resource and the second resource within the resource pair respectively and if reported; | +| | Layer Indicator as in Table 6.3.1.1.2-3B, if reported part 1 is associated with one CSI-RS resource and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1 associated with the first resource within the CSI-RS resource pair, if reported part 1 is associated with one CSI-RS resource pair and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] associated with the first CSI-RS resource within the CSI-RS resource pair, if pmi-FormatIndicator= widebandPMI and reported part 1 is associated with one CSI-RS resource pair and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1 associated with the second CSI-RS resource within the CSI-RS resource pair, if reported part 1 is associated with one CSI-RS resource pair and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] associated with the second CSI-RS resource within the CSI-RS resource pair, if pmi-FormatIndicator= widebandPMI and reported part 1 is associated with one CSI-RS resource pair and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, if reported part 1 is associated with one CSI-RS resource and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214], if pmi-FormatIndicator= widebandPMI and reported part 1 is associated with one CSI-RS resource and if reported | + +**Table 6.3.1.1.2-11: Mapping order of CSI fields of one CSI report, CSI part 2 subband, *pmi-FormatIndicator= subbandPMI* or *cqi-FormatIndicator=subbandCQI*** + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
Part 2 subband | Subband differential CQI for the second TB of all even subbands with increasing order of subband number, as in Tables 6.3.1.1.2-3/4/5, if cqi-FormatIndicator=subbandCQI and if reported | +| | PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported | +| | Subband differential CQI for the second TB of all odd subbands with increasing order of subband number, as in Tables 6.3.1.1.2-3/4/5, if cqi-FormatIndicator=subbandCQI and if reported | +| | PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported | +| NOTE: Subbands for given CSI report n indicated by the higher layer parameter csi-ReportingBand with value set to '1' are numbered continuously in the increasing order with the lowest subband of csi-ReportingBand with value set to '1' as subband 0. | | + +**Table 6.3.1.1.2-11A: Mapping order of CSI fields of one CSI report, CSI part 2 subband, *csi-ReportMode= Mode 1*** + +| | | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
Part 2 subband | PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the first resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported | +| | PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with | + +| | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

the second resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported

| +|

Subband differential CQI for the second TB of all even subbands with increasing order of subband number associated with CRI in CSI part 1, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 1 and if reported;

Subband differential CQI for the second TB of all even subbands with increasing order of subband number associated with the first CRI in CSI part 1, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported

| +|

PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with CRI in CSI part 1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI, numberOfSingleTRP-CSI-Mode1 = 1 and if reported;

PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the first CRI in CSI part 1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported

| +|

Subband differential CQI for the second TB of all even subbands with increasing order of subband number associated with the second CRI in CSI part 1, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported

| +|

PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the second CRI in CSI part 1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported

| +|

PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the first resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported

| +|

PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the second resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported

| +|

Subband differential CQI for the second TB of all odd subbands with increasing order of subband number associated with CRI in CSI part 1, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 1 and if reported;

Subband differential CQI for the second TB of all odd subbands with increasing order of subband number associated with the first CRI in CSI part 1, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported

| +|

PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with CRI in CSI part 1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI, numberOfSingleTRP-CSI-Mode1 = 1 and if reported;

PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the first CRI in CSI part 1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported

| +|

Subband differential CQI for the second TB of all odd subbands with increasing order of subband number associated with the second CRI in CSI part 1, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported

| +|

PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the second CRI in CSI part 1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported

| + +**Table 6.3.1.1.2-11B: Mapping order of CSI fields of one CSI report, CSI part 2 subband, *csi-ReportMode= Mode 2*** + +| | | +|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
Part 2 subband | PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the first resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource pair and if reported | +| | PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the second resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource pair and if reported | +| | PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the first resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource pair and if reported | +| | PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the second resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource pair and if reported | +| | Subband differential CQI for the second TB of all even subbands with increasing order of subband number associated with one CSI-RS resource, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI and reported part 1 is associated with one CSI-RS resource and if reported | +| | PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with one CSI-RS resource according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource and if reported | +| | Subband differential CQI for the second TB of all odd subbands with increasing order of subband number associated with one CSI-RS resource, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI and reported part 1 is associated with one CSI-RS resource and if reported | +| | PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2, or codebook index for 2 antenna ports associated with one CSI-RS resource according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource and if reported | + +**Table 6.3.1.1.2-11C: Mapping order of CSI fields of one CSI report containing CSI sub-report(s), CSI part 2 subband, *pmi-FormatIndicator*= *subbandPMI* or *cqi-FormatIndicator*=*subbandCQI*** + +| | | +|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
Part 2 subband | Subband differential CQI of CSI sub-report #1 for the second TB of all even subbands with increasing order of subband number, as in Tables 6.3.1.1.2-3/4, if cqi-FormatIndicator = subbandCQI and if reported | +| | PMI subband information fields of CSI sub-report #1 of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2, or codebook index for 2 antenna ports of CSI sub-report #1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator = subbandPMI and if reported | +| | Subband differential CQI of CSI sub-report #2 for the second TB of all even subbands with increasing order of subband number, as in Tables 6.3.1.1.2-3/4, if cqi-FormatIndicator = subbandCQI and if reported | +| | PMI subband information fields of CSI sub-report #2 of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2, or codebook index for 2 antenna ports of CSI sub-report #2 according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator = subbandPMI and if reported | +| | ... | +| | Subband differential CQI of CSI sub-report # for the second TB of all even subbands with increasing order of subband number, as in Tables 6.3.1.1.2-3/4, if cqi-FormatIndicator = subbandCQI and if reported | +| | PMI subband information fields of CSI sub-report # of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2, or codebook index for 2 antenna ports of CSI sub-report # according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator = subbandPMI and if reported | +| | Subband differential CQI of CSI sub-report #1 for the second TB of all odd subbands with increasing order of subband number, as in Tables 6.3.1.1.2-3/4, if cqi-FormatIndicator = subbandCQI and if reported | +| | PMI subband information fields of CSI sub-report #1 of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2, or codebook index for 2 antenna ports of CSI sub-report #1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator = subbandPMI and if reported | +| | Subband differential CQI of CSI sub-report #2 for the second TB of all odd subbands with increasing order of subband number, as in Tables 6.3.1.1.2-3/4, if cqi-FormatIndicator = subbandCQI and if reported | +| | PMI subband information fields of CSI sub-report #2 of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2, or codebook index for 2 antenna ports CSI sub-report #2 according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator = subbandPMI and if reported | +| | ... | +| | Subband differential CQI of CSI sub-report # for the second TB of all odd subbands with increasing order of subband number, as in Tables 6.3.1.1.2-3/4, if cqi-FormatIndicator = subbandCQI and if reported | +| | PMI subband information fields of CSI sub-report # of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2, or codebook index for 2 antenna ports of CSI sub-report # according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator = subbandPMI and if reported | + +NOTE: Subbands for given CSI report *n* indicated by the higher layer parameter *csi-ReportingBand* with value set to '1' are numbered continuously in the increasing order with the lowest subband of *csi-ReportingBand* with value set to '1' as subband 0. CSI sub-report #1, CSI sub-report #2, ..., CSI sub-report # correspond to the CSI sub-reports in increasing order of *CSI-ReportSubConfigID*. + +If none of the CSI reports for transmission on a PUCCH is of two parts, the CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.1.1.2-12, are mapped to the UCI bit sequence starting with $i_0$ . The most significant bit of each field is mapped to the lowest order information bit for that field, e.g. the most significant bit of the first field is mapped to $i_0$ . + +**Table 6.3.1.1.2-12: Mapping order of CSI reports to UCI bit sequence , without two-part CSI report(s)** + +| UCI bit sequence | CSI report number | +|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | CSI report #1
as in Table 6.3.1.1.2-7/7A/8/8B | +| | CSI report #2
as in Table 6.3.1.1.2-7/7A/8/8B | +| | ... | +| | CSI report #n
as in Table 6.3.1.1.2-7/7A/8/8B | +| NOTE: | For a CSI report #i containing CSI sub-reports, where $i$ , all CSI sub-reports within the CSI report #i are mapped to the corresponding segment of the UCI bit sequence of CSI report #i, from upper part to lower part of the segment, in increasing order of CSI sub-report number. CSI sub-report #1, CSI sub-report #2, ..., CSI sub-report # correspond to the CSI sub-reports in increasing order of CSI-ReportSubConfigID . | + +If at least one of the CSI reports for transmission on a PUCCH is of two parts, two UCI bit sequences are generated, $i_0$ and $i_1$ . The CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.1.1.2-13, are mapped to the UCI bit sequence starting with $i_0$ . The most significant bit of each field is mapped to the lowest order information bit for that field, e.g. the most significant bit of the first field is mapped to $i_0$ . The CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.1.1.2-14, are mapped to the UCI bit sequence starting with $i_1$ . The most significant bit of each field is mapped to the lowest order information bit for that field, e.g. the most significant bit of the first field is mapped to $i_1$ . If the length of UCI bit sequence is less than 3 bits, zeros shall be appended to the UCI bit sequence until its length equals 3. + +**Table 6.3.1.1.2-13: Mapping order of CSI reports to UCI bit sequence , with two-part CSI report(s)** + +| UCI bit sequence | CSI report number | +|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | CSI report #1 if CSI report #1 is not of two parts, or
CSI report #1, CSI part 1, if CSI report #1 is of two parts,
as in Table 6.3.1.1.2-7/7A/8/8B/9/9A/9B | +| | CSI report #2 if CSI report #2 is not of two parts, or
CSI report #2, CSI part 1, if CSI report #2 is of two parts,
as in Table 6.3.1.1.2-7/7A/8/8B/9/9A/9B | +| | ... | +| | CSI report #n if CSI report #n is not of two parts, or
CSI report #n, CSI part 1, if CSI report #n is of two parts,
as in Table 6.3.1.1.2-7/7A/8/8B/9/9A/9B | +| NOTE: | For a CSI report #i containing CSI sub-reports, where $i$ , either all CSI sub-reports not of two parts or CSI part 1 of all CSI sub-reports of two parts, are mapped to the corresponding segment of the UCI bit sequence of CSI report #i, from upper part to lower part of the segment, in increasing order of CSI sub-report number. CSI sub-report #1, CSI sub-report #2, ..., CSI sub-report # correspond to the CSI sub-reports in increasing order of CSI-ReportSubConfigID . | + +where CSI report #1, CSI report #2, ..., CSI report #n in Table 6.3.1.1.2-13 correspond to the CSI reports in increasing order of CSI report priority values according to Clause 5.2.5 of [6, TS38.214]. + +**Table 6.3.1.1.2-14: Mapping order of CSI reports to UCI bit sequence , with two-part CSI report(s)** + +| UCI bit sequence | CSI report number | +|------------------|-------------------------------------------------------------------------------------------------------------------| +| | CSI report #1, CSI part 2 wideband, as in Table 6.3.1.1.2-10/10A/10B
if CSI part 2 exists for CSI report #1 | +| | CSI report #2, CSI part 2 wideband, as in Table 6.3.1.1.2-10/10A/10B
if CSI part 2 exists for CSI report #2 | +| | ... | +| | CSI report #n, CSI part 2 wideband, as in Table 6.3.1.1.2-10/10A/10B
if CSI part 2 exists for CSI report #n | +| | CSI report #1, CSI part 2 subband, as in Table 6.3.1.1.2-11/11A/11B/11C
if CSI part 2 exists for CSI report #1 | +| | CSI report #2, CSI part 2 subband, as in Table 6.3.1.1.2-11/11A/11B/11C
if CSI part 2 exists for CSI report #2 | +| | ... | +| | CSI report #n, CSI part 2 subband, as in Table 6.3.1.1.2-11/11A/11B/11C
if CSI part 2 exists for CSI report #n | + +NOTE: For a CSI report #i containing CSI sub-reports, where : + +- CSI part 2 widebands of all CSI sub-reports are mapped to the corresponding segment of the UCI bit sequence of CSI report #i, from upper part to lower part of the segment, in increasing order of CSI sub-report number; +- CSI sub-report #1, CSI sub-report #2, ..., CSI sub-report # correspond to the CSI sub-reports in increasing order of *CSI-ReportSubConfigID*. + +where CSI report #1, CSI report #2, ..., CSI report #n in Table 6.3.1.1.2-14 correspond to the CSI reports in increasing order of CSI report priority values according to Clause 5.2.5 of [6, TS38.214]. + +##### 6.3.1.1.3 HARQ-ACK/SR and CSI + +If none of the CSI reports for transmission on a PUCCH is of two parts, the UCI bit sequence is generated according to the following, where : + +- if there is HARQ-ACK for transmission on the PUCCH, the HARQ-ACK bits are mapped to the UCI bit sequence , where for , the HARQ-ACK bit sequence is given by Clause 9.1 of [5, TS38.213], and is number of HARQ-ACK bits; if there is no HARQ-ACK for transmission on the PUCCH, set ; +- if there is SR for transmission on the PUCCH, set for , where the SR bit sequence is given by Clause 9.2.5.1 of [5, TS 38.213]; if there is no SR for transmission on the PUCCH, set ; +- the CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.1.1.2-12, are mapped to the UCI bit sequence starting with , where is the number of CSI bits. + +If at least one of the CSI reports for transmission on a PUCCH is of two parts, two UCI bit sequences are generated, and , according to the following, where and : + +- if there is HARQ-ACK for transmission on the PUCCH, the HARQ-ACK bits are mapped to the UCI bit sequence , where for , the HARQ-ACK bit sequence is given by Clause 9.1 of [5, TS38.213], and is number of HARQ-ACK bits; if there is no HARQ-ACK for transmission on the PUCCH, set ; +- if there is SR for transmission on the PUCCH, set for , where the SR bit sequence is given by Clause 9.2.5.1 of [5, TS 38.213]; if there is no SR for transmission on the PUCCH, set ; +- the CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.1.1.2-13, are mapped to the UCI bit sequence starting with , where is the number of CSI bits in CSI part 1 of all CSI reports; +- the CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.1.1.2-14, are mapped to the UCI bit sequence starting with , where is the number of CSI bits in CSI part 2 of all CSI reports. If the length of UCI bit sequence is less than 3 bits, zeros shall be appended to the UCI bit sequence until its length equals 3. + +##### 6.3.1.1.4 UCI with different priority indexes + +If *uci-MuxWithDiffPrio* is configured, and HARQ-ACK bits associated with priority index 0, HARQ-ACK bits associated with priority index 1, and SR associated with priority index 1 if any are transmitted on a PUCCH, two UCI bit sequences are generated, and , according to the following, where and : + +- the HARQ-ACK bits associated with priority index 1 are mapped to the UCI bit sequence , where for , the HARQ-ACK bit sequence is given by Clause 9.1 of [5, TS 38.213], and is the number of HARQ-ACK bits associated with priority index 1; +- if there is SR associated with priority index 1 for transmission on the PUCCH, set for , where the SR bit sequence is given by Clause 9.2.5.1 of [5, TS 38.213]; if there is no SR associated with priority index 1 for transmission on the PUCCH, set ; +- the HARQ-ACK bits associated with priority index 0 are mapped to the UCI bit sequence , where for , the HARQ-ACK bit sequence is given by Clause 9.1 of [5, TS 38.213], and is the number of HARQ-ACK bits associated with priority index 0. + +#### 6.3.1.2 Code block segmentation and CRC attachment + +The UCI bit sequence from clause 6.3.1.1 is denoted by , where is the payload size. The procedure in Clause 6.3.1.2.1 applies for and the procedure in Clause 6.3.1.2.2 applies for . + +##### 6.3.1.2.1 UCI encoded by Polar code + +If the payload size , code block segmentation and CRC attachment is performed according to Clause 5.2.1. If ( and ) or if $A \geq 1013$ , ; otherwise , where is the rate matching output sequence length as given in Clauses 6.3.1.4.1 and 6.3.1.4.3. + +If , the parity bits in Clause 5.2.1 are computed by setting to 6 bits and using the generator polynomial in Clause 5.1, resulting in the sequence where is the code block number and is the number of bits for code block number . + +If , the parity bits in Clause 5.2.1 are computed by setting to 11 bits and using the generator polynomial in Clause 5.1, resulting in the sequence where is the code block number and is the number of bits for code block number . + +##### 6.3.1.2.2 UCI encoded by channel coding of small block lengths + +If the payload size , CRC bits are not attached. + +The output bit sequence is denoted by , where for and . + +#### 6.3.1.3 Channel coding of UCI + +##### 6.3.1.3.1 UCI encoded by Polar code + +Information bits are delivered to the channel coding block. They are denoted by , where is the code block number, and is the number of bits in code block number . The total number of code blocks is denoted by and each code block is individually encoded by the following: + +If , the information bits are encoded via Polar coding according to Clause 5.3.1, by setting , , if and if , where is the rate matching output sequence length as given in Clauses 6.3.1.4.1 and 6.3.1.4.3. + +If , the information bits are encoded via Polar coding according to Clause 5.3.1, by setting , , and . + +After encoding the bits are denoted by , where is the number of coded bits in code block number . + +##### 6.3.1.3.2 UCI encoded by channel coding of small block lengths + +Information bits are delivered to the channel coding block. They are denoted by , where is the number of bits. + +The information bits are encoded according to Clause 5.3.3. + +After encoding the bits are denoted by , where is the number of coded bits. + +#### 6.3.1.4 Rate matching + +For PUCCH formats 2/3/4, the total rate matching output sequence length is given by Table 6.3.1.4-1, where $N_{\text{symbols}}$ , $N_{\text{PRB}}$ , and $K$ are the number of symbols carrying UCI for PUCCH formats 2/3/4 respectively; $N_{\text{PRB}}$ are the number of PRBs that are determined by the UE for PUCCH formats 2/3/4 transmission respectively according to Clause 9.2 of [5, TS38.213]; and $K$ are the spreading factors for PUCCH format 2, PUCCH format 3, and PUCCH format 4, respectively. + +**Table 6.3.1.4-1: Total rate matching output sequence length** + +| PUCCH format | Modulation order | | +|---------------------|-------------------------|---------------| +| | QPSK | $\pi/2$ -BPSK | +| PUCCH format 2 | | N/A | +| PUCCH format 3 | | | +| PUCCH format 4 | | | + +##### 6.3.1.4.1 UCI encoded by Polar code + +The input bit sequence to rate matching is $w$ where $w$ is the code block number, and $w$ is the number of coded bits in code block number $w$ . + +**Table 6.3.1.4.1-1: Rate matching output sequence length** + +| UCI(s) for transmission on a PUCCH | UCI for encoding | Value of | +|---------------------------------------------|--------------------------|----------| +| HARQ-ACK | HARQ-ACK | | +| HARQ-ACK, SR | HARQ-ACK, SR | | +| CSI
(CSI not of two parts) | CSI | | +| HARQ-ACK, CSI
(CSI not of two parts) | HARQ-ACK, CSI | | +| HARQ-ACK, SR, CSI
(CSI not of two parts) | HARQ-ACK, SR, CSI | | +| CSI
(CSI of two parts) | CSI part 1 | | +| | CSI part 2 | | +| HARQ-ACK, CSI
(CSI of two parts) | HARQ-ACK, CSI part 1 | | +| | CSI part 2 | | +| HARQ-ACK, SR, CSI
(CSI of two parts) | HARQ-ACK, SR, CSI part 1 | | +| | CSI part 2 | | + +Rate matching is performed according to Clause 5.4.1 by setting $N_{\text{input}}$ and the rate matching output sequence length to $N_{\text{output}}$ , where $N_{\text{input}}$ is the number of code blocks for UCI determined according to Clause 6.3.1.2.1 and the value of $N_{\text{output}}$ is given by Table 6.3.1.4.1-1: + +- $N_{\text{input}}$ is the number of bits for HARQ-ACK for transmission on the current PUCCH; +- $N_{\text{input}}$ is the number of bits for SR for transmission on the current PUCCH; +- $N_{\text{input}}$ is the number of bits for CSI part 1 for transmission on the current PUCCH; +- $N_{\text{input}}$ is the number of bits for CSI part 2 for transmission on the current PUCCH; +- if $A \geq 360$ , $L = 11$ ; otherwise, $N_{\text{input}}$ is the number of CRC bits determined according to Clause 6.3.1.2.1, where $A$ equals for "CSI (CSI of two parts)", equals $O^{\text{ACK}} + O^{\text{CSI-part1}}$ for "HARQ-ACK, CSI (CSI of two parts)", and equals $O^{\text{ACK}} + O^{\text{SR}} + O^{\text{CSI-part1}}$ for "HARQ-ACK, SR, CSI (CSI of two parts)" respectively in Table 6.3.1.4.1-1; +- $N_{\text{output}}$ is the configured maximum PUCCH coding rate; +- $N_{\text{output}}$ is given by Table 6.3.1.4-1. + +The output bit sequence after rate matching is denoted as $\tilde{c}_{i,n}$ where $n$ is the length of rate matching output sequence in code block number $i$ . + +##### 6.3.1.4.2 UCI encoded by channel coding of small block lengths + +The input bit sequence to rate matching is $\mathbf{u}$ . + +The value of $N$ is determined according to Table 6.3.1.4.1-1 by setting $\mathbf{u}$ . + +Rate matching is performed according to Clause 5.4.3 by setting the rate matching output sequence length $N$ . + +The output bit sequence after rate matching is denoted as $\tilde{c}_{i,n}$ . + +##### 6.3.1.4.3 UCI with different priority indexes encoded by Polar code + +The following procedure in this clause 6.3.1.4.3 applies if *uci-MuxWithDiffPrio* is configured, and HARQ-ACK bits associated with priority index 0, HARQ-ACK bits associated with priority index 1 and SR associated with priority index 1 if any are transmitted on a PUCCH. + +The input bit sequence to rate matching is $\mathbf{u}$ where $i$ is the code block number, and $n$ is the number of coded bits in code block number $i$ . + +**Table 6.3.1.4.3-1: Rate matching output sequence length for UCIs with different priority indexes** + +| UCIs for transmission on a PUCCH | UCI for encoding | Value of $N$ | +|------------------------------------------------------------------------------------|------------------------------------------------------|--------------| +| HARQ-ACK of priority index 1, HARQ-ACK of priority index 0 | HARQ-ACK of priority index 1 | | +| | HARQ-ACK of priority index 0 | | +| HARQ-ACK of priority index 1, SR of priority index 1, HARQ-ACK of priority index 0 | HARQ-ACK of priority index 1, SR of priority index 1 | | +| | HARQ-ACK of priority index 0 | | + +Rate matching is performed according to Clause 5.4.1 by setting $N$ and the rate matching output sequence length to $N$ , where $N$ is the number of code blocks for UCI determined according to Clause 6.3.1.2.1 and the value of $N$ is given by Table 6.3.1.4.3-1: + +- $N$ is the number of bits for HARQ-ACK associated with priority index 1 for transmission on the current PUCCH; +- $N$ is the number of bits for SR associated with priority index 1 for transmission on the current PUCCH; +- if $N=11$ ; otherwise, $N$ is the number of CRC bits determined according to clause 6.3.1.2.1, where $N$ equals for the case of "HARQ-ACK of priority index 1, HARQ-ACK of priority index 0", and equals for the case of "HARQ-ACK of priority index 1, SR of priority index 1, HARQ-ACK of priority index 0" respectively in Table 6.3.1.4.3-1; +- $N$ is the configured maximum PUCCH coding rate of priority index 1; +- $N$ is given by Table 6.3.1.4-1. + +The output bit sequence after rate matching is denoted as $\tilde{c}_{i,n}$ where $n$ is the length of rate matching output sequence in code block number $i$ . + +##### 6.3.1.4.4 UCI with different priority indexes encoded by channel coding of small block lengths + +The following procedure in this clause 6.3.1.4.4 applies if *uci-MuxWithDiffPrio* is configured, and HARQ-ACK bits associated with priority index 0, HARQ-ACK bits associated with priority index 1 and SR associated with priority index 1 if any are transmitted on a PUCCH. + +The input bit sequence to rate matching is $\mathbf{u}$ . + +The value of $N$ is determined according to Table 6.3.1.4.3-1 by setting $\mathbf{u}=0$ . + +Rate matching is performed according to Clause 5.4.3 by setting the rate matching output sequence length . + +The output bit sequence after rate matching is denoted as . + +#### 6.3.1.5 Code block concatenation + +The input bit sequence for the code block concatenation block are the sequences, for and where is the number of rate matched bits for the -th code block. + +Code block concatenation is performed according to Clause 5.5. + +The bits after code block concatenation are denoted by, where with the values of and given in Clauses 6.3.1.4.1 and 6.3.1.4.3. Let be the total number of coded bits for transmission and . Set for . + +#### 6.3.1.6 Multiplexing of coded UCI bits to PUCCH + +If CSI of two parts or UCIs with different priority indexes are transmitted on a PUCCH, the coded bits corresponding to UCI bit sequence is denoted by and the coded bits corresponding to UCI bit sequence is denoted by . + +For PUCCH format 2 when *uci-MuxWithDiffPrio* is configured, the coded bit sequence is generated for UCIs with different priority indexes by setting for , and setting for . + +For PUCCH format 3/4, the coded bit sequence , where , is generated according to the following. + +**Table 6.3.1.6-1: PUCCH DMRS and UCI symbols** + +| PUCCH duration (symbols) | PUCCH DMRS symbol indices | Number of UCI symbol indices sets | 1 st UCI symbol indices set | 2 nd UCI symbol indices set | 3 rd UCI symbol indices set | +|--------------------------|---------------------------|-----------------------------------|----------------------------------------|----------------------------------------|----------------------------------------| +| 4 | {1} | 2 | {0,2} | {3} | - | +| 4 | {0,2} | 1 | {1,3} | - | - | +| 5 | {0, 3} | 1 | {1, 2, 4} | - | - | +| 6 | {1, 4} | 1 | {0, 2, 3, 5} | - | - | +| 7 | {1, 4} | 2 | {0, 2, 3, 5} | {6} | - | +| 8 | {1, 5} | 2 | {0, 2, 4, 6} | {3, 7} | - | +| 9 | {1, 6} | 2 | {0, 2, 5, 7} | {3, 4, 8} | - | +| 10 | {2, 7} | 2 | {1, 3, 6, 8} | {0, 4, 5, 9} | - | +| 10 | {1, 3, 6, 8} | 1 | {0,2,4,5,7,9} | - | - | +| 11 | {2, 7} | 3 | {1,3,6,8} | {0,4,5,9} | {10} | +| 11 | {1,3,6,9} | 1 | {0,2,4,5,7,8,10} | - | - | +| 12 | {2, 8} | 3 | {1,3,7,9} | {0,4,6,10} | {5, 11} | +| 12 | {1,4,7,10} | 1 | {0,2,3,5,6,8,9,11} | - | - | +| 13 | {2, 9} | 3 | {1,3,8,10} | {0,4,7,11} | {5,6,12} | +| 13 | {1,4,7,11} | 2 | {0,2,3,5,6,8,10,12} | {9} | - | +| 14 | {3, 10} | 3 | {2,4,9,11} | {1,5,8,12} | {0,6,7,13} | +| 14 | {1,5,8,12} | 2 | {0,2,4,6,7,9,11,13} | {3, 10} | - | + +Denote as UCI OFDM symbol index. Denote as the number of elements in UCI symbol indices set for , where and are given by Table 6.3.1.6-1 according to the PUCCH duration and the PUCCH DMRS configuration. Denote as the number of OFDM symbols carrying UCI in the PUCCH. Denote as the modulation order of the PUCCH. + +For PUCCH formats 3/4, set , where is the number of PRBs that is determined by the UE for the corresponding PUCCH format transmission according to Clause 9.2 of [5, TS 38.213], and is the spreading factor for the corresponding PUCCH format [4, TS 38.211], where . + +Find the smallest such that . + +Set ; + +Set ; + +Set ; + +Set ; + +``` + +for to + if + for to + for to + ; + ; + ; + end for + end for + elseif + if + ; + else + ; + end if + ; + for to + for to + ; + ; + ; + end for + end for + for to + for to + ; + ; + ; + end for + end for + else + for to + for to + ; + ; + ; + end for + end for + end if +end for + +Set + +for to + for to + for to + ; + ; + ; + end for + end for +end for + +``` + +### 6.3.2 Uplink control information on PUSCH + +The following clauses 6.3.2.2, 6.3.2.3, and 6.3.2.5 apply regardless of whether the higher layer parameter *uci-MuxWithDiffPrio* is configured or not. The following clauses 6.3.2.1, 6.3.2.4, and 6.3.2.6 apply by assuming *uci-MuxWithDiffPrio* is not configured, or *uci-MuxWithDiffPrio* is configured and the UCIs for transmission on a PUSCH are of the same priority index, unless stated otherwise. + +If the UE is configured with a PUCCH-SCell, *uci-MuxWithDiffPrio* is replaced by *uci-MuxWithDiffPrioSecondaryPUCCHgroup* for the secondary PUCCH group in this clause. + +#### 6.3.2.1 UCI bit sequence generation + +##### 6.3.2.1.1 HARQ-ACK + +If HARQ-ACK bits are transmitted on a PUSCH, the UCI bit sequence is determined as follows: + +- If UCI is transmitted on PUSCH without UL-SCH and the UCI includes CSI part 1 without CSI part 2, + - if there is no HARQ-ACK bit given by Clause 9.1 of [5, TS 38.213], set $n_{ACK}$ , $n_{RI}$ , and $n_{CQI}$ to 0; + - if there is only one HARQ-ACK bit given by Clause 9.1 of [5, TS 38.213], set $n_{ACK}$ , $n_{RI}$ , and $n_{CQI}$ to 1; +- otherwise, set $n_{ACK}$ for $n_{RI}$ and $n_{CQI}$ , where the HARQ-ACK bit sequence is given by Clause 9.1 of [5, TS 38.213]. + +##### 6.3.2.1.2 CSI + +If *cqi-BitsPerSubband* is configured, this Clause 6.3.2.1.2 applies by taking Subband CQI as Subband differential CQI and replacing the corresponding number of bits 2 by 4. + +If *csi-ReportSubConfig* is configured, for a corresponding CSI sub-report, the bitwidth of a CSI field of the CSI sub-report is determined following the procedure in this clause 6.3.2.1.2 by taking configurations in *CSI-ReportSubConfig* when applicable. If *csi-ReportSubConfig* configures a list of CSI-RS resource IDs, for the determination of the bitwidth of a CRI field, the value of $n_{CRI}$ is the number of CSI-RS resources configured in the corresponding *csi-ReportSubConfig*. + +The bitwidth for PMI of *codebookType=typeI-SinglePanel* and *codebookType=typeI-MultiPanel* is specified in Clause 6.3.1.1.2. + +The bitwidth for RI/LI/CQI/CRI of *codebookType=typeI-SinglePanel* and *codebookType=typeI-MultiPanel* is specified in Clause 6.3.1.1.2. + +The bitwidth for PMI/RI/LI/CQI/CRI with 1 CSI-RS port is specified in Clause 6.3.1.1.2. + +The bitwidth for PMI of *codebookType=typeII* is provided in Tables 6.3.2.1.2-1, where the values of $n_{PMI}$ , $n_{RI}$ , $n_{LI}$ , $n_{CQI}$ , and $n_{CRI}$ are given by Clause 5.2.2.2.3 in [6, TS 38.214]. + +**Table 6.3.2.1.2-1: PMI of *codebookType= typeII*** + +| | Information fields for wideband PMI | | | | | | Information fields for wideband PMI or per subband PMI | | | | +|----------------------|-------------------------------------|----------|----------|-----------|-----------|-----|--------------------------------------------------------|----------|----------|-----------| +| | $n_{PMI}$ | $n_{RI}$ | $n_{LI}$ | $n_{CQI}$ | $n_{CRI}$ | | $n_{PMI}$ | $n_{RI}$ | $n_{LI}$ | $n_{CQI}$ | +| Rank=1
SB Amp off | | | | | N/A | N/A | | N/A | N/A | N/A | +| Rank=2
SB Amp off | | | | | | | | | N/A | N/A | +| Rank=1
SB Amp on | | | | | N/A | N/A | | N/A | | N/A | +| Rank=2
SB Amp on | | | | | | | | | | | + +The bitwidth for PMI of *codebookType=typeII-r16* is provided in Tables 6.3.2.1.2-1A, where the values of $n_{PMI}$ , $n_{RI}$ , $n_{LI}$ , $n_{CQI}$ , and $n_{CRI}$ are given by Clause 5.2.2.2.5 in [6, TS 38.214]. + +**Table 6.3.2.1.2-1A: PMI of *codebookType*= *typeII-r16*** + +| | Information fields | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-----|-----|-----|-----|--|-----|-----|-----|--|--|--| +| | | | | | | | | | | | | | +| Rank=1 | | | | | | | N/A | N/A | N/A | | | | +| Rank=2 | | | | | | | | N/A | N/A | | | | +| Rank=3 | | | | | | | | | N/A | | | | +| Rank=4 | | | | | | | | | | | | | +| Rank=1 | | | | | | | N/A | N/A | N/A | | | | +| Rank=2 | | | | | | | | N/A | N/A | | | | +| Rank=3 | | | | | | | | | N/A | | | | +| Rank=4 | | | | | | | | | | | | | +| | Information fields | | | | | | | | | | | | +| | | | | | | | | | | | | | +| Rank=1 | 4 | N/A | N/A | N/A | N/A | | N/A | N/A | N/A | | | | +| Rank=2 | 4 | 4 | N/A | N/A | N/A | | | N/A | N/A | | | | +| Rank=3 | 4 | 4 | 4 | N/A | N/A | | | | N/A | | | | +| Rank=4 | 4 | 4 | 4 | 4 | N/A | | | | | | | | +| Rank=1 | 4 | N/A | N/A | N/A | | | N/A | N/A | N/A | | | | +| Rank=2 | 4 | 4 | N/A | N/A | | | | N/A | N/A | | | | +| Rank=3 | 4 | 4 | 4 | N/A | | | | | N/A | | | | +| Rank=4 | 4 | 4 | 4 | 4 | | | | | | | | | +| Note: the bitwidth for $K_{NZ,l}$ , $M_l$ and $N_3$ shown in Table 6.3.2.1.2-1A is the total bitwidth of $K_{NZ,l}$ , $M_l$ and $N_3$ up to Rank = $\nu$ , respectively, and the corresponding per layer bitwidths are $K_{NZ,l}$ , $M_l$ , and 4, (i.e., 1, 3, and 4 bits for each respective indicator elements $k_{l,i}^{(1)}$ , $k_{l,i}^{(2)}$ , and $n_{3,l,i}$ , respectively), where $K_{NZ,l}$ as defined in Clause 5.2.2.2.5 in TS 38.214 [6] is the number of nonzero coefficients for layer $l$ such that $K_{NZ,l} \leq 2K_0$ . | | | | | | | | | | | | | + +The bitwidth for PMI of *codebookType*=*typeII-CJT* is provided in Tables 6.3.2.1.2-1B, where the values of $N_{NZ}$ , $M_l$ , $L$ , $p$ , $n_3$ , and $k_{NZ}$ are given by Clause 5.2.2.2.8 in [6, TS 38.214]. + +**Table 6.3.2.1.2-1B: PMI of *codebookType*= *typeII-CJT*** + +| | Information fields | | | | | | +|--------|--------------------|--|-----|-----|-----|--| +| | | | | | | | +| Rank=1 | | | N/A | N/A | N/A | | +| Rank=2 | | | | N/A | N/A | | +| Rank=3 | | | | | N/A | | +| Rank=4 | | | | | | | + +| | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-----|---------------------------------------------|-----|-----|--|-----| +| Rank=1 | | | | N/A | N/A | | N/A | +| Rank=2 | | | | | N/A | | N/A | +| Rank=3 | | | | | | | N/A | +| Rank=4 | | | | | | | | +| | Information fields | | | | | | | +| Rank=1 | 4 | N/A | N/A | N/A | N/A | | N/A | +| Rank=2 | 4 | 4 | N/A | N/A | N/A | | | +| Rank=3 | 4 | 4 | 4 | N/A | N/A | | | +| Rank=4 | 4 | 4 | 4 | 4 | N/A | | | +| Rank=1 | 4 | N/A | N/A | N/A | | | N/A | +| Rank=2 | 4 | 4 | N/A | N/A | | | | +| Rank=3 | 4 | 4 | 4 | N/A | | | | +| Rank=4 | 4 | 4 | 4 | 4 | | | | +| | Information fields | | | | | | | +| Rank=1 | N/A | N/A | if Mode1 is configured, NA otherwise | | | | | +| Rank=2 | N/A | N/A | if Mode1 is configured, NA otherwise | | | | | +| Rank=3 | | N/A | if Mode1 is configured, NA otherwise | | | | | +| Rank=4 | | | if Mode1 is configured, NA otherwise | | | | | +| Rank=1 | N/A | N/A | if Mode1 is configured, NA otherwise | | | | | +| Rank=2 | N/A | N/A | if Mode1 is configured, NA otherwise | | | | | +| Rank=3 | | N/A | if Mode1 is configured, NA otherwise | | | | | +| Rank=4 | | | if Mode1 is configured, NA otherwise | | | | | +| NOTE: the bitwidth for , and shown in Table 6.3.2.1.2-1B is the total bitwidth of , and up to Rank = , respectively, and the corresponding per layer bitwidths are , , and 4, (i.e., 1, 3, and 4 bits for each respective indicator elements , , and , respectively), where as defined in Clause 5.2.2.2.8 in [6, TS 38.214] is the number of nonzero coefficients for layer such that . | | | | | | | | + +The bitwidth for PMI of *codebookType=typeII-Doppler* is provided in Tables 6.3.2.1.2-1C, where the values of , , , , *Q* and are given by Clause 5.2.2.2.10 in [6, TS 38.214]. + +**Table 6.3.2.1.2-1C: PMI of *codebookType=typeII-Doppler*** + +| | | | | | | | +|--------|---------------------------|--|--|-----|-----|-----| +| | Information fields | | | | | | +| Rank=1 | | | | N/A | N/A | N/A | + +| | | | | | | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-------------------------|-------------------------|-----|-----|-----|-----| +| Rank=2 | | | | | | | N/A | N/A | +| Rank=3 | | | | | | | | N/A | +| Rank=4 | | | | | | | | | +| Rank=1 | | | | | | N/A | N/A | N/A | +| Rank=2 | | | | | | | N/A | N/A | +| Rank=3 | | | | | | | | N/A | +| Rank=4 | | | | | | | | | +| Information fields | | | | | | | | | +| Rank=1 | 4 | N/A | N/A | N/A | N/A | | N/A | N/A | +| Rank=2 | 4 | 4 | N/A | N/A | N/A | | | N/A | +| Rank=3 | 4 | 4 | 4 | N/A | N/A | | | N/A | +| Rank=4 | 4 | 4 | 4 | 4 | N/A | | | | +| Rank=1 | 4 | N/A | N/A | N/A | | | N/A | N/A | +| Rank=2 | 4 | 4 | N/A | N/A | | | | N/A | +| Rank=3 | 4 | 4 | 4 | N/A | | | | N/A | +| Rank=4 | 4 | 4 | 4 | 4 | | | | | +| Information fields | | | | | | | | | +| Rank=1 | if $Q=2$ , NA otherwise | NA | NA | NA | | | | | +| Rank=2 | if $Q=2$ , NA otherwise | if $Q=2$ , NA otherwise | NA | NA | | | | | +| Rank=3 | if $Q=2$ , NA otherwise | if $Q=2$ , NA otherwise | if $Q=2$ , NA otherwise | NA | | | | | +| Rank=4 | if $Q=2$ , NA otherwise | if $Q=2$ , NA otherwise | if $Q=2$ , NA otherwise | if $Q=2$ , NA otherwise | | | | | +| Rank=1 | if $Q=2$ , NA otherwise | NA | NA | NA | | | | | +| Rank=2 | if $Q=2$ , NA otherwise | if $Q=2$ , NA otherwise | NA | NA | | | | | +| Rank=3 | if $Q=2$ , NA otherwise | if $Q=2$ , NA otherwise | if $Q=2$ , NA otherwise | NA | | | | | +| Rank=4 | if $Q=2$ , NA otherwise | if $Q=2$ , NA otherwise | if $Q=2$ , NA otherwise | if $Q=2$ , NA otherwise | | | | | +| NOTE: | the bitwidth for $\hat{c}_{i,j,k}$ , and shown in Table 6.3.2.1.2-1C is the total bitwidth of $\hat{c}_{i,j,k}$ , and up to Rank = $\hat{Q}$ , respectively, and the corresponding per layer bitwidths are $\hat{c}_{i,j,k}$ , and 4, (i.e., 1, 3, and 4 bits for each respective indicator elements $\hat{c}_{i,j,k}$ , and $\hat{c}_{i,j,k}$ , respectively), where $\hat{Q}$ as defined in Clause 5.2.2.2.10 in [6, TS 38.214] is the number of nonzero coefficients for layer $\hat{Q}$ such that $\sum_{k=0}^{\hat{Q}-1} \hat{c}_{i,j,k} \neq 0$ . | | | | | | | | + +The bitwidth for PMI of *codebookType*= *typeII-PortSelection* is provided in Tables 6.3.2.1.2-2, where the values of $\hat{c}_{i,j,k}$ , $\hat{c}_{i,j,k}$ , $\hat{c}_{i,j,k}$ , and $\hat{c}_{i,j,k}$ are given by Clause 5.2.2.2.4 in [6, TS 38.214]. + +**Table 6.3.2.1.2-2: PMI of *codebookType= typeII-PortSelection*** + +| | Information fields for wideband PMI | | | | | Information fields for wideband PMI or per subband PMI | | | | +|-----------------------------|-------------------------------------|--|--|-----|-----|--------------------------------------------------------|-----|-----|-----| +| | | | | | | | | | | +| Rank
=1
SBAm
p off | | | | N/A | N/A | | N/A | N/A | N/A | +| Rank
=2
SBAm
p off | | | | | | | | N/A | N/A | +| Rank
=1
SBAm
p on | | | | N/A | N/A | | N/A | | N/A | +| Rank
=2
SBAm
p on | | | | | | | | | | + +The bitwidth for PMI of *codebookType=typeII-PortSelection-r16* is provided in Tables 6.3.2.1.2-2A, where the values of $\dots$ and $\dots$ are given by Clause 5.2.2.2.6 in [6, TS 38.214]. + +**Table 6.3.2.1.2-2A: PMI of *codebookType= typeII-PortSelection-r16*** + +| | Information fields | | | | | | | | | | | | +|--------|--------------------|-----|-----|-----|-----|--|--|-----|-----|-----|--|-----| +| | | | | | | | | | | | | | +| Rank=1 | | | | | | | | N/A | N/A | | | N/A | +| Rank=2 | | | | | | | | | N/A | | | N/A | +| Rank=3 | | | | | | | | | | | | N/A | +| Rank=4 | | | | | | | | | | | | | +| Rank=1 | | | | | | | | N/A | N/A | | | N/A | +| Rank=2 | | | | | | | | | N/A | | | N/A | +| Rank=3 | | | | | | | | | | | | N/A | +| Rank=4 | | | | | | | | | | | | | +| | Information fields | | | | | | | | | | | | +| | | | | | | | | | | | | | +| Rank=1 | 4 | N/A | N/A | N/A | N/A | | | N/A | N/A | N/A | | | +| Rank=2 | 4 | 4 | N/A | N/A | N/A | | | | N/A | N/A | | | +| Rank=3 | 4 | 4 | 4 | N/A | N/A | | | | | N/A | | | +| Rank=4 | 4 | 4 | 4 | 4 | N/A | | | | | | | | +| Rank=1 | 4 | N/A | N/A | N/A | | | | N/A | N/A | N/A | | | +| Rank=2 | 4 | 4 | N/A | N/A | | | | | N/A | N/A | | | +| Rank=3 | 4 | 4 | 4 | N/A | | | | | | N/A | | | +| Rank=4 | 4 | 4 | 4 | 4 | | | | | | | | | + +NOTE: the bitwidth for , and shown in Table 6.3.2.1.2-2A is the total bitwidth of , and up to Rank = , respectively, and the corresponding per layer bitwidths are , , and 4, (i.e., 1, 3, and 4 bits for each respective indicator elements , , and , respectively), where as defined in Clause 5.2.2.2.5 in TS 38.214 [6] is the number of nonzero coefficients for layer such that . + +The bitwidth for PMI of *codebookType=typeII-PortSelection-r17* is provided in Tables 6.3.2.1.2-2B, where the values of , , , and are given by Clause 5.2.2.2.7 in [6, TS 38.214]. + +**Table 6.3.2.1.2-2B: PMI of *codebookType= typeII-PortSelection-r17*** + +| | Information fields | | | | | | | +|--|--------------------|---|------------------------------|-----|-----|-----|--------------------| +| | Rank=1 | | if $N > M=2$ , N/A otherwise | | N/A | N/A | N/A | +| | Rank=2 | | if $N > M=2$ , N/A otherwise | | | N/A | N/A | +| | Rank=3 | | if $N > M=2$ , N/A otherwise | | | | N/A | +| | Rank=4 | | if $N > M=2$ , N/A otherwise | | | | | +| | Information fields | | | | | | | +| | Rank=1 | 4 | N/A | N/A | N/A | | N/A if ; otherwise | +| | Rank=2 | 4 | 4 | N/A | N/A | | N/A if ; otherwise | +| | Rank=3 | 4 | 4 | 4 | N/A | | | +| | Rank=4 | 4 | 4 | 4 | 4 | | | + +NOTE: the bitwidth for , and shown in Table 6.3.2.1.2-2B is the total bitwidth of , and up to Rank = , respectively, and the corresponding per layer bitwidths are , , and 4, (i.e., 1, 3, and 4 bits for each respective indicator elements , , and , respectively), where as defined in Clause 5.2.2.2.7 in TS 38.214 [6] is the number of nonzero coefficients for layer such that . + +If *csi-ReportSubConfig* is configured, for a corresponding CSI sub-report, the mapping order of CSI fields of one CSI sub-report is determined following the procedure in this clause 6.3.2.1.2, by replacing CSI report #n in the following Tables 6.3.2.1.2-3 and 6.3.2.1.2-4 with CSI sub-report #n, and taking only Tables 6.3.1.1.2-1/2/3/4 for the determination of the bitwidth of a CSI field. + +The bitwidth for PMI of *codebookType=typeII-CJT-PortSelection* is provided in Tables 6.3.2.1.2-2C, where the values of , , , and are given by Clause 5.2.2.2.9 in [6, TS 38.214]. + +**Table 6.3.2.1.2-2C: PMI of *codebookType= typeII-CJT-PortSelection*** + +| | Information fields | | | | | | | | +|--|--------------------|---|------------------------------|-----|-----|-----|---------------------------------------------|--------------------| +| | Rank=1 | | if $N > M=2$ , N/A otherwise | | N/A | N/A | N/A | | +| | Rank=2 | | if $N > M=2$ , N/A otherwise | | | N/A | N/A | | +| | Rank=3 | | if $N > M=2$ , N/A otherwise | | | | N/A | | +| | Rank=4 | | if $N > M=2$ , N/A otherwise | | | | | | +| | Information fields | | | | | | | | +| | Rank=1 | 4 | N/A | N/A | N/A | | if Mode1 is configured, NA otherwise | N/A if ; otherwise | +| | Rank=2 | 4 | 4 | N/A | N/A | | if Mode1 is configured, NA otherwise | N/A if ; otherwise | +| | Rank=3 | 4 | 4 | 4 | N/A | | if Mode1 is configured, NA otherwise | | +| | Rank=4 | 4 | 4 | 4 | 4 | | if Mode1 is configured, NA otherwise | | + +NOTE: the bitwidth for , and shown in Table 6.3.2.1.2-2C is the total bitwidth of , and up to Rank = , respectively, and the corresponding per layer bitwidths are , , and 4, (i.e., 1, 3, and 4 bits for each respective indicator elements , , and , respectively), where as defined in Clause 5.2.2.2.9 in [6, TS 38.214] is the number of nonzero coefficients for layer such that . + +The bitwidth for PMI of *codebookType=typeII-Doppler-PortSelection* is provided in Tables 6.3.2.1.2-2D, where the values of , , , and are given by Clause 5.2.2.2.11 in [6, TS 38.214]. + +**Table 6.3.2.1.2-2D: PMI of *codebookType= typeII-Doppler-PortSelection*** + +| | Information fields | | | | | | | +|--|--------------------|---|------------------------------|-----|-----|-----|--------------------| +| | Rank=1 | | if $N > M=2$ , N/A otherwise | | N/A | N/A | N/A | +| | Rank=2 | | if $N > M=2$ , N/A otherwise | | | N/A | N/A | +| | Rank=3 | | if $N > M=2$ , N/A otherwise | | | | N/A | +| | Rank=4 | | if $N > M=2$ , N/A otherwise | | | | | +| | Information fields | | | | | | | +| | Rank=1 | 4 | N/A | N/A | N/A | | N/A if ; otherwise | +| | Rank=2 | 4 | 4 | N/A | N/A | | N/A if ; otherwise | +| | Rank=3 | 4 | 4 | 4 | N/A | | | +| | Rank=4 | 4 | 4 | 4 | 4 | | | + +NOTE: the bitwidth for , and shown in Table 6.3.2.1.2-2D is the total bitwidth of , and up to Rank = , respectively, and the corresponding per layer bitwidths are , , and 4, (i.e., 1, 3, and 4 bits for each respective indicator elements , , and , respectively), where as defined in Clause 5.2.2.2.11 in [6, TS 38.214] is the number of nonzero coefficients for layer such that . + +For CSI on PUSCH, two UCI bit sequences are generated, and . The CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.2.1.2-6, are mapped to the UCI bit sequence starting with . The CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.2.1.2-7, are mapped to the UCI bit sequence starting with . + +The mapping order of CSI fields of one report for CRI/RSRP or SSBR/RSRP or CRI/RSRP/CapabilityIndex or SSBR/RSRP/CapabilityIndex reporting is provided in Table 6.3.1.1.2-8. The mapping order of CSI fields of one report for inter-cell SSBR/RSRP reporting is provided in Table 6.3.1.1.2-8. The mapping order of CSI fields of one report for CRI/SINR or SSBR/SINR or CRI/SINR/CapabilityIndex or SSBR/SINR/CapabilityIndex reporting is provided in Table 6.3.1.1.2-8A. The mapping order of CSI fields of one report for group-based CRI/RSRP or SSBR/RSRP reporting is provided in Table 6.3.1.1.2-8B. The mapping order of CSI fields of one report for TDCP reporting is provided in Table 6.3.2.1.2-3C. The mapping order of CSI fields of one report for SSBR/RSRP reporting for L1/L2-triggered mobility is provided in Table 6.3.1.1.2-8C. The procedure in clause 6.3.2 described for CSI part 1 is also applicable for one report for CRI/RSRP, SSBR/RSRP, CRI/SINR, SSBR/SINR reporting, or TDCP reporting. + +**Table 6.3.2.1.2-3: Mapping order of CSI fields of one CSI report, CSI part 1** + +| CSI report number | CSI fields | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
CSI part 1 | CRI as in Tables 6.3.1.1.2-3/4/6, if reported | +| | Rank Indicator as in Tables 6.3.1.1.2-3/4/5 or 6.3.2.1.2-8/8A/8B/9/9A, if reported | +| | Wideband CQI for the first TB as in Tables 6.3.1.1.2-3/4/5 or 6.3.2.1.2-8/8A/8B/9/9A, if reported | +| | Subband differential CQI for the first TB with increasing order of subband number as in Tables 6.3.1.1.2-3/4/5 or 6.3.2.1.2-8/8A/8B/9/9A, if reported | +| | Indicator of the number of non-zero wideband amplitude coefficients for layer 0 as in Table 6.3.1.1.2-5, if reported | +| | Indicator of the number of non-zero wideband amplitude coefficients for layer 1 as in Table 6.3.1.1.2-5 (if the rank according to the reported RI is equal to one, this field is set to all zeros), if 2-layer PMI reporting is allowed according to the rank restriction in Clauses 5.2.2.2.3 and 5.2.2.2.4 [6, TS 38.214] and if reported | +| | Indicator of the selected CSI-RS resources by a bitmap with bits, this field is present only if and restrictedCMR-Selection is configured to OFF | +| | Indicator of selected value combination or value combination with bitwidth of , this field is present only if | +| | Indicator of the total number of non-zero coefficients summed across all layers as in Tables 6.3.2.1.2-8/8A/8B/9/9A, if reported | +| | NOTE: Subbands for given CSI report n indicated by the higher layer parameter csi-ReportingBand are numbered continuously in the increasing order with the lowest subband of csi-ReportingBand as subband 0. | + +**Table 6.3.2.1.2-3A: Mapping order of CSI fields of one CSI report, CSI part 1, *csi-ReportMode= Mode 1*** + +| CSI report number | CSI fields | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
CSI part 1 | CRI as in Table 6.3.1.1.2-3A, if associated with one CSI-RS resource pair and if reported | +| | Rank Combination Indicator as in Table 6.3.1.1.2-3A, if reported | +| | Wideband CQI for the first TB as in Table 6.3.1.1.2-3A, if reported | +| | Subband differential CQI for the first TB with increasing order of subband number as in Table 6.3.1.1.2-3A, if reported | +| | CRI as in Tables 6.3.1.1.2-3B, if associated with one CSI-RS resource, numberOfSingleTRP-CSI-Mode1 = 1 and if reported; | +| | First CRI as in Table 6.3.1.1.2-3B, if associated with one CSI-RS resource, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | Rank Indicator associated with CRI as in Table 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 1 and if reported; | +| | Rank Indicator associated with the first CRI as in Table 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | Wideband CQI associated with CRI for the first TB as in Table 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 1 and if reported; | +| | Wideband CQI associated with the first CRI for the first TB as in Table 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | Subband differential CQI associated with CRI for the first TB with increasing order of subband number as in Table 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 1 if reported; | +| | Subband differential CQI associated with the first CRI for the first TB with increasing order of subband number as in Table 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | Second CRI as in Table 6.3.1.1.2-3B, if associated with one CSI-RS resource, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | Rank Indicator associated with the second CRI as in Table 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | Wideband CQI associated with the second CRI for the first TB as in Table 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | Subband differential CQI associated with the second CRI for the first TB with increasing order of subband number as in Table 6.3.1.1.2-3B, if numberOfSingleTRP-CSI-Mode1 = 2 and if reported | + +NOTE: Subbands for given CSI report *n* indicated by the higher layer parameter *csi-ReportingBand* are numbered continuously in the increasing order with the lowest subband of *csi-ReportingBand* as subband 0. + +**Table 6.3.2.1.2-3B: Mapping order of CSI fields of one CSI report, CSI part 1, *csi-ReportMode= Mode 2*** + +| CSI report number | CSI fields | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
CSI part 1 | CRI as in Table 6.3.1.1.2-3A, if associated with one CSI-RS resource pair and if reported; | +| | CRI as in Table 6.3.1.1.2-3B, if associated with one CSI-RS resource and if reported | +| | Rank Combination Indicator as in Table 6.3.1.1.2-3A, if associated with one CSI-RS resource pair and if reported; | +| | Rank Indicator as in Table 6.3.1.1.2-3B, if associated with one CSI-RS resource and if reported; | +| | Zero padding bits , if needed | +| | Wideband CQI for the first TB as in Table 6.3.1.1.2-3A, if associated with one CSI-RS resource pair and if reported; | +| | Wideband CQI for the first TB as in Table 6.3.1.1.2-3B, if associated with one CSI-RS resource and if reported | +| | Subband differential CQI for the first TB with increasing order of subband number as in Table 6.3.1.1.2-3A, if associated with one CSI-RS resource pair and if reported; | +| | Subband differential CQI for the first TB with increasing order of subband number as in Table 6.3.1.1.2-3B, if associated with one CSI-RS resource and if reported | + +NOTE: Subbands for given CSI report *n* indicated by the higher layer parameter *csi-ReportingBand* are numbered continuously in the increasing order with the lowest subband of *csi-ReportingBand* as subband 0. + +**Table 6.3.2.1.2-3C: Mapping order of CSI fields of one CSI report for *reportQuantity=tdcp*** + +| CSI report number | CSI fields | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n | Amplitude value for the configured delay values as in Table 6.3.2.1.2-10 based on the order from the first configured delay to the last configured delay | +| | Phase value for the configured delay values as in Table 6.3.2.1.2-10 based on the order from the first configured delay to the last configured delay, if reported | + +The number of zero padding bits in Table 6.3.1.1.2-9B is 0 for 1 CSI-RS port and for more than 1 CSI-RS port, where: + +- $\mathcal{R}$ is the set of rank and rank combination values $r$ that are allowed to be reported. $\mathcal{R}$ is obtained according to Tables 6.3.1.1.2-3A/3B for rank combination indicator and rank indicator respectively. +- $\mathcal{R}$ is obtained according to Tables 6.3.1.1.2-3A for rank combination indicator and $R$ is the reported rank combination +- $\mathcal{R}$ is obtained according to Tables 6.3.1.1.2-3B for rank indicator and $R$ is the reported rank + +**Table 6.3.2.1.2-4: Mapping order of CSI fields of one CSI report, CSI part 2 wideband** + +| CSI report number | CSI fields | +|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
CSI part 2
wideband | Wideband CQI for the second TB as in Tables 6.3.1.1.2-3/4/5, if present and reported | +| | Layer Indicator as in Tables 6.3.1.1.2-3/4/5, if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1/2 or 6.3.2.1.2-1/2, if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1/2 or 6.3.2.1.2-1/2, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214], if pmi-FormatIndicator= widebandPMI and if reported | + +**Table 6.3.2.1.2-4A: Mapping order of CSI fields of one CSI report, CSI part 2 wideband, *csi-ReportMode= Mode 1*** + +| CSI report number | CSI fields | +|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
CSI part 2
wideband | Two Layer Indicators as in Table 6.3.1.1.2-3A, where the first Layer Indicator and the second Layer Indicator are associated with the first resource and the second resource within the resource pair respectively and if reported; | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1 associated with the first resource within the CSI-RS resource pair, if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] associated with the first CSI-RS resource within the CSI-RS resource pair, if pmi-FormatIndicator= widebandPMI and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1 associated with the second resource within the CSI-RS resource pair, if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] associated with the second CSI-RS resource within the CSI-RS resource pair, if pmi-FormatIndicator= widebandPMI and if reported | +| | Wideband CQI for the second TB as in Tables 6.3.1.1.2-3B, if associated with CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 1 and if reported;
Wideband CQI for the second TB as in Tables 6.3.1.1.2-3B, if associated with the first CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | Layer Indicator as in Table 6.3.1.1.2-3B, if associated with CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 1 and if reported; | +| | Layer Indicator as in Table 6.3.1.1.2-3B, if associated with the first CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, if associated with CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 1 and if reported; | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, if associated with the first CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214], if associated with CRI in CSI part 1, pmi-FormatIndicator= widebandPMI , numberOfSingleTRP-CSI-Mode1 = 1 and if reported; | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214], if associated with the first CRI in CSI part 1, pmi-FormatIndicator= widebandPMI , numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | Wideband CQI for the second TB as in Tables 6.3.1.1.2-3B, if associated with the second CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | Layer Indicator as in Table 6.3.1.1.2-3B, if associated with the second CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, if associated with the second CRI in CSI part 1, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214], if associated with the second CRI in CSI part 1, pmi-FormatIndicator= widebandPMI , numberOfSingleTRP-CSI-Mode1 = 2 and if reported | + +**Table 6.3.2.1.2-4B: Mapping order of CSI fields of one CSI report, CSI part 2 wideband, *csi-ReportMode= Mode 2*** + +| CSI report number | CSI fields | +|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
CSI part 2 wideband | Wideband CQI for the second TB as in Tables 6.3.1.1.2-3B, if reported part 1 is associated with one CSI-RS resource and if reported | +| | Two Layer Indicators as in Table 6.3.1.1.2-3A, if reported part 1 is associated with one CSI-RS resource pair, where the first Layer Indicator and the second Layer Indicator are associated with the first resource and the second resource within the resource pair respectively and if reported;
Layer Indicator as in Table 6.3.1.1.2-3B, if reported part 1 is associated with one CSI-RS resource and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1 associated with the first resource within the CSI-RS resource pair, if reported part 1 is associated with one CSI-RS resource pair and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] associated with the first CSI-RS resource within the CSI-RS resource pair, if pmi-FormatIndicator= widebandPMI and reported part 1 is associated with one CSI-RS resource pair and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1 associated with the second CSI-RS resource within the CSI-RS resource pair, if reported part 1 is associated with one CSI-RS resource pair and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] associated with the second CSI-RS resource within the CSI-RS resource pair, if pmi-FormatIndicator= widebandPMI and reported part 1 is associated with one CSI-RS resource pair and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, if reported part 1 is associated with one CSI-RS resource and if reported | +| | PMI wideband information fields , from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214], if pmi-FormatIndicator= widebandPMI and reported part 1 is associated with one CSI-RS resource and if reported | + +**Table 6.3.2.1.2-5: Mapping order of CSI fields of one CSI report, CSI part 2 subband** + +| | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
Part 2 subband | Subband differential CQI for the second TB of all even subbands with increasing order of subband number, as in Tables 6.3.1.1.2-3/4/5, if cqi-FormatIndicator=subbandCQI and if reported | +| | PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2 or 6.3.2.1.2-1/2, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported | +| | Subband differential CQI for the second TB of all odd subbands with increasing order of subband number, as in Tables 6.3.1.1.2-3/4/5, if cqi-FormatIndicator=subbandCQI and if reported | +| | PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2 or 6.3.2.1.2-1/2, or codebook index for 2 antenna ports according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported | +| NOTE: Subbands for given CSI report n indicated by the higher layer parameter csi-ReportingBand are numbered continuously in the increasing order with the lowest subband of csi-ReportingBand as subband 0. | | + +**Table 6.3.2.1.2-5A: Mapping order of CSI fields of one CSI report, CSI part 2 of *codebookType=typeII-r16* or *typeII-PortSelection-r16*** + +| CSI report number | CSI fields | +|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
CSI part 2, group 0 | PMI fields , from left to right as in Tables 6.3.2.1.2-1A/2A, if reported | +| CSI report #n
CSI part 2, group 1 | The following PMI fields , from left to right, as in Tables 6.3.2.1.2-1A/2A: , and highest priority bits of highest priority bits of and highest priority bits of , in decreasing order of priority based on the corresponding function defined in clause 5.2.3 of TS 38.214 [6], if reported | +| CSI report #n
CSI part 2, group 2 | The following PMI fields , from left to right, as in Tables 6.3.2.1.2-1A/2A lowest priority bits of lowest priority bits of and lowest priority bits of , in decreasing order of priority based on the corresponding function defined in clause 5.2.3 of TS 38.214 [6], if reported | + +**Table 6.3.2.1.2-5B: Mapping order of CSI fields of one CSI report, CSI part 2 of codebookType=typeII-PortSelection-r17 or typeII-Doppler-PortSelection** + +| CSI report number | CSI fields | +|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
CSI part 2, group 0 | PMI fields , from left to right as in Table 6.3.2.1.2-2B, if reported | +| CSI report #n
CSI part 2, group 1 | The following PMI fields , from left to right, as in Table 6.3.2.1.2-2B: highest priority bits of highest priority bits of and highest priority bits of, in decreasing order of priority based on the corresponding function defined in clause 5.2.3 of TS 38.214 [6], if reported | +| CSI report #n
CSI part 2, group 2 | The following PMI fields , from left to right, as in Table 6.3.2.1.2-2B lowest priority bits of lowest priority bits of and lowest priority bits of , in decreasing order of priority based on the corresponding function defined in clause 5.2.3 of TS 38.214 [6], if reported | + +**Table 6.3.2.1.2-5C: Mapping order of CSI fields of one CSI report, CSI part 2 subband, ReportMode= Mode 1** + +| | | +|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
Part 2 subband | PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the first resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported | +| | PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the second resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported | +| | Subband differential CQI for the second TB of all even subbands with increasing order of subband number associated with CRI in CSI part 1, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 1 and if reported;
Subband differential CQI for the second TB of all even subbands with increasing order of subband number associated with the first CRI in CSI part 1, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with CRI in CSI part 1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI, numberOfSingleTRP-CSI-Mode1 = 1 and if reported;
PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the first CRI in CSI part 1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | Subband differential CQI for the second TB of all even subbands with increasing order of subband number associated with the second CRI in CSI part 1, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the second CRI in CSI part 1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the first resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported | +| | PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the second resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported | +| | Subband differential CQI for the second TB of all odd subbands with increasing order of subband number associated with CRI in CSI part 1, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 1 and if reported;
Subband differential CQI for the second TB of all odd subbands with increasing order of subband number associated with the first CRI in CSI part 1, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | | + +| | | +|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with CRI in CSI part 1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI, numberOfSingleTRP-CSI-Mode1 = 1 and if reported;

PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the first CRI in CSI part 1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported

| +| | Subband differential CQI for the second TB of all odd subbands with increasing order of subband number associated with the second CRI in CSI part 1, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | +| | PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the second CRI in CSI part 1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI, numberOfSingleTRP-CSI-Mode1 = 2 and if reported | + +**Table 6.3.2.1.2-5D: Mapping order of CSI fields of one CSI report, CSI part 2 subband, *ReportMode= Mode 2*** + +| | | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
Part 2 subband |

PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the first resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource pair and if reported

| +| |

PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the second resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource pair and if reported

| +| |

PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the first resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource pair and if reported

| +| |

PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with the second resource within the CSI-RS resource pair, according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource pair and if reported

| +| | Subband differential CQI for the second TB of all even subbands with increasing order of subband number associated with one CSI-RS resource, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI and reported part 1 is associated with one CSI-RS resource and if reported | +| |

PMI subband information fields of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1, or codebook index for 2 antenna ports associated with one CSI-RS resource according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource and if reported

| +| | Subband differential CQI for the second TB of all odd subbands with increasing order of subband number associated with one CSI-RS resource, as in Tables 6.3.1.1.2-3B, if cqi-FormatIndicator=subbandCQI and reported part 1 is associated with one CSI-RS resource and if reported | +| |

PMI subband information fields of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2, or codebook index for 2 antenna ports associated with one CSI-RS resource according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and reported part 1 is associated with one CSI-RS resource and if reported

| + +**Table 6.3.2.1.2-5E: Mapping order of CSI fields of one CSI report, CSI part 2 of +*codebookType=typeII-CJT*** + +| CSI report number | CSI fields | +|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
CSI part 2, group 0 | PMI fields , from left to right as in Table 6.3.2.1.2-1B, if reported; | +| CSI report #n
CSI part 2, group 1 | The following PMI fields , from left to right, as in Table 6.3.2.1.2-1B: $\hat{h}_{p,1}$ , $\hat{h}_{p,2}$ , $\hat{h}_{p,3}$ , and highest priority bits of $\hat{h}_{p,1}$ and highest priority bits of $\hat{h}_{p,2}$ , in decreasing order of priority based on the corresponding function defined in clause 5.2.3 of TS 38.214 [6] where $\hat{h}_{p,1}$ is equivalent to $\hat{h}_{p,1}$ , if present and if reported; | +| CSI report #n
CSI part 2, group 2 | The following PMI fields , from left to right, as in Table 6.3.2.1.2-1B lowest priority bits of $\hat{h}_{p,1}$ and lowest priority bits of $\hat{h}_{p,2}$ , in decreasing order of priority based on the corresponding function defined in clause 5.2.3 of TS 38.214 [6] where $\hat{h}_{p,1}$ is equivalent to $\hat{h}_{p,1}$ , if reported; | + +**Table 6.3.2.1.2-5F: Mapping order of CSI fields of one CSI report, CSI part 2 of +*codebookType= typeII-Doppler*** + +| CSI report number | CSI fields | +|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
CSI part 2, group 0 | PMI fields , from left to right as in Table 6.3.2.1.2-1C, if reported;
The second time-domain wideband CQI as in Table 6.3.1.1.2-8B, if present and reported | +| CSI report #n
CSI part 2, group 1 | The following PMI fields , from left to right, as in Table 6.3.2.1.2-1C: $\hat{h}_{p,1}$ , $\hat{h}_{p,2}$ , $\hat{h}_{p,3}$ , and highest priority bits of $\hat{h}_{p,1}$ and highest priority bits of $\hat{h}_{p,2}$ , in decreasing order of priority based on the corresponding function for $\hat{h}_{p,1}$ or for $\hat{h}_{p,2}$ defined in clause 5.2.3 of TS 38.214 [6], if present and if reported;
The second time-domain subband differential CQI of all even subbands with increasing order of subband number, as in Table 6.3.1.1.2-8B, if present and if reported | +| CSI report #n
CSI part 2, group 2 | The following PMI fields , from left to right, as in Table 6.3.2.1.2-1C lowest priority bits of $\hat{h}_{p,1}$ and lowest priority bits of $\hat{h}_{p,2}$ , in decreasing order of priority based on the corresponding function for $\hat{h}_{p,1}$ or for $\hat{h}_{p,2}$ defined in clause 5.2.3 of TS 38.214 [6], if reported;
The second time-domain subband differential CQI of all odd subbands with increasing order of subband number, as in Table 6.3.1.1.2-8B, if present and if reported | + +**Table 6.3.2.1.2-5G: Mapping order of CSI fields of one CSI report, CSI part 2 of +*codebookType=typeII-CJT-PortSelection*** + +| CSI report number | CSI fields | +|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
CSI part 2, group 0 | PMI fields , from left to right as in Table 6.3.2.1.2-2C, if reported | +| CSI report #n
CSI part 2, group 1 | The following PMI fields , from left to right, as in Table 6.3.2.1.2-2C: highest priority bits of $\hat{h}_{p,1}$ and highest priority bits of $\hat{h}_{p,2}$ , in decreasing order of priority based on the corresponding function defined in clause 5.2.3 of TS 38.214 [6] where $\hat{h}_{p,1}$ is equivalent to $\hat{h}_{p,1}$ , if present and if reported | +| CSI report #n
CSI part 2, group 2 | The following PMI fields , from left to right, as in Table 6.3.2.1.2-2C lowest priority bits of $\hat{h}_{p,1}$ and lowest priority bits of $\hat{h}_{p,2}$ , in decreasing order of priority based on the corresponding function defined in clause 5.2.3 of TS 38.214 [6] where $\hat{h}_{p,1}$ is equivalent to $\hat{h}_{p,1}$ , if reported | + +**Table 6.3.2.1.2-5H: Mapping order of CSI fields of one CSI report containing CSI sub-report(s), CSI part 2 subband** + +| | | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CSI report #n
Part 2 subband | Subband differential CQI of CSI sub-report #1 for the second TB of all even subbands with increasing order of subband number, as in Tables 6.3.1.1.2-3/4, if cqi-FormatIndicator=subbandCQI and if reported | +| | PMI subband information fields of CSI sub-report #1 of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2, or codebook index for 2 antenna ports of CSI sub-report #1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported | +| | Subband differential CQI of CSI sub-report #2 for the second TB of all even subbands with increasing order of subband number, as in Tables 6.3.1.1.2-3/4, if cqi-FormatIndicator=subbandCQI and if reported | +| | PMI subband information fields of CSI sub-report #2 of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2, or codebook index for 2 antenna ports of CSI sub-report #2 according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported | +| | ... | +| | Subband differential CQI of CSI sub-report # for the second TB of all even subbands with increasing order of subband number, as in Tables 6.3.1.1.2-3/4, if cqi-FormatIndicator=subbandCQI and if reported | +| | PMI subband information fields of CSI sub-report # of all even subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2, or codebook index for 2 antenna ports of CSI sub-report # according to Clause 5.2.2.2.1 in [6, TS38.214] of all even subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported | +| | Subband differential CQI of CSI sub-report #1 for the second TB of all odd subbands with increasing order of subband number, as in Tables 6.3.1.1.2-3/4, if cqi-FormatIndicator=subbandCQI and if reported | +| | PMI subband information fields of CSI sub-report #1 of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2, or codebook index for 2 antenna ports of CSI sub-report #1 according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported | +| | Subband differential CQI of CSI sub-report #2 for the second TB of all odd subbands with increasing order of subband number, as in Tables 6.3.1.1.2-3/4, if cqi-FormatIndicator=subbandCQI and if reported | +| | PMI subband information fields of CSI sub-report #2 of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2, or codebook index for 2 antenna ports of CSI sub-report #2 according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported | +| | ... | +| | Subband differential CQI of CSI sub-report # for the second TB of all odd subbands with increasing order of subband number, as in Tables 6.3.1.1.2-3/4, if cqi-FormatIndicator=subbandCQI and if reported | +| | PMI subband information fields of CSI sub-report # of all odd subbands with increasing order of subband number, from left to right as in Tables 6.3.1.1.2-1/2, or codebook index for 2 antenna ports of CSI sub-report # according to Clause 5.2.2.2.1 in [6, TS38.214] of all odd subbands with increasing order of subband number, if pmi-FormatIndicator= subbandPMI and if reported | + +Note: +Subbands for given CSI report *n* indicated by the higher layer parameter *csi-ReportingBand* with value set to '1' are numbered continuously in the increasing order with the lowest subband of *csi-ReportingBand* with value set to '1' as subband 0. +CSI sub-report #1, CSI sub-report #2, ..., CSI sub-report # correspond to the CSI sub-reports in increasing order of *CSI-ReportSubConfigID*. + +**Table 6.3.2.1.2-6: Mapping order of CSI reports to UCI bit sequence , with two-part CSI report(s)** + +| UCI bit sequence | CSI report number | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | CSI part 1 of CSI report #1 as in Table 6.3.2.1.2-3/3A/3B or Table 6.3.1.1.2-8/8A/8B/8C or Table 6.3.2.1.2-3C | +| | CSI part 1 of CSI report #2 as in Table 6.3.2.1.2-3/3A/3B or Table 6.3.1.1.2-8/8A/8B/8C or Table 6.3.2.1.2-3C | +| | ... | +| | CSI part 1 of CSI report #n as in Table 6.3.2.1.2-3/3A/3B or Table 6.3.1.1.2-8/8A/8B/8C or Table 6.3.2.1.2-3C | +| NOTE: | For a CSI report #i containing CSI sub-reports, where , CSI part 1 of all CSI sub-reports are mapped to the corresponding segment of the UCI bit sequence of CSI report #i, from upper part to lower part of the segment, in increasing order of CSI sub-report number. CSI sub-report #1, CSI sub-report #2, ..., CSI sub-report # correspond to the CSI sub-reports in increasing order of CSI-ReportSubConfigID . | + +where CSI report #1, CSI report #2, ..., CSI report #n in Table 6.3.2.1.2-6 correspond to the CSI reports in increasing order of CSI report priority values according to Clause 5.2.5 of [6, TS38.214]. + +**Table 6.3.2.1.2-7: Mapping order of CSI reports to UCI bit sequence , with two-part CSI report(s)** + +| UCI bit sequence | CSI report number | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | CSI report #1, CSI part 2 wideband, as in Table 6.3.2.1.2-4/4A/4B,
or CSI part 2 with group 0, as in Table 6.3.2.1.2-5A/5B/5E/5F/5G,
if CSI part 2 exists for CSI report #1 | +| | CSI report #2, CSI part 2 wideband, as in Table 6.3.2.1.2-4/4A/4B,
or CSI part 2 with group 0, as in Table 6.3.2.1.2-5A/5B/5E/5F/5G,
if CSI part 2 exists for CSI report #2 | +| | ... | +| | CSI report #n, CSI part 2 wideband, as in Table 6.3.2.1.2-4/4A/4B,
or CSI part 2 with group 0, as in Table 6.3.2.1.2-5A/5B/5E/5F/5G,
if CSI part 2 exists for CSI report #n | +| | CSI report #1, CSI part 2 subband, as in Table 6.3.2.1.2-5/5C/5D/5H,
or CSI part 2 with group 1 and 2, as in Table 6.3.2.1.2-5A/5B/5E/5F/5G,
if CSI part 2 exists for CSI report #1 | +| | CSI report #2, CSI part 2 subband, as in Table 6.3.2.1.2-5/5C/5D/5H,
or CSI part 2 with group 1 and 2, as in Table 6.3.2.1.2-5A/5B/5E/5F/5G,
if CSI part 2 exists for CSI report #2 | +| | ... | +| | CSI report #n, CSI part 2 subband, as in Table 6.3.2.1.2-5/5C/5D/5H,
or CSI part 2 with group 1 and 2, as in Table 6.3.2.1.2-5A/5B/5E/5F/5G,
if CSI part 2 exists for CSI report #n | +| NOTE: | For a CSI report #i containing CSI sub-reports, where ,
  • - CSI part 2 wideband of all CSI sub-reports are mapped to the corresponding segment of the UCI bit sequence of CSI report #i, from upper part to lower part of the segment, in increasing order of CSI sub-report number;
  • - CSI sub-report #1, CSI sub-report #2, ..., CSI sub-report # correspond to the CSI sub-reports in increasing order of CSI-ReportSubConfigID.
| + +where CSI report #1, CSI report #2, ..., CSI report #n in Table 6.3.2.1.2-7 correspond to the CSI reports in increasing order of CSI report priority values according to Clause 5.2.5 of [6, TS38.214]. + +The bitwidth for RI/CQI of *codebookType= typeII-r16* or *codebookType=typeII-PortSelection-r16* is provided in Table 6.3.2.1.2-8. + +**Table 6.3.2.1.2-8: RI and CQI of *codebookType=typeII-r16* or *typeII-PortSelection-r16*** + +| Field | Bitwidth | +|---------------------------------------------------------------------------------|----------------------------------------| +| Rank Indicator | | +| Wide-band CQI | 4 | +| Subband differential CQI | 2 | +| Indicator of the total number of non-zero coefficients summed across all layers | if max allowed rank is 1;
otherwise | + +where $N_{RI}$ is the number of allowed rank indicator values according to Clauses 5.2.2.2.5 and 5.2.2.2.6 [6, TS 38.214], $N_{WB}$ , $N_{SB}$ , and $N_{NZ}$ are given by Clause 5.2.2.2.5 and 5.2.2.2.6 in [6, TS 38.214]. The values of the rank indicator field are mapped to allowed rank indicator values with increasing order, where '0' is mapped to the smallest allowed rank indicator value. The values of the indicator field are mapped to the allowed values of $N_{NZ}$ , according to Clauses 5.2.2.2.5 and 5.2.2.2.6 [6, TS 38.214], with increasing order, where '0' is mapped to . + +The bitwidth for RI/CQI of *codebookType= typeII-CJT* is provided in Table 6.3.2.1.2-8A. + +**Table 6.3.2.1.2-8A: RI and CQI of *codebookType= typeII-CJT*** + +| Field | Bitwidth | +|--------------------------------------------------------------------------------------------------------------------------|----------------------------------------| +| Rank Indicator | | +| Wide-band CQI | 4 | +| Subband differential CQI | 2 | +| Indicator of the total number of non-zero coefficients summed across all layers, and all CSI-RS resources if configured, | if max allowed rank is 1;
otherwise | + +Where $N_{RI}$ is the number of allowed rank indicator values according to Clause 5.2.2.2.8 TS 38.214 [6], $N_{max}$ is the maximum of $N_{RI}$ for all configured combinations, where $N_{RI}$ , $N_{WB}$ , $N_{SB}$ , and $N_{NZ}$ are given by Clause 5.2.2.2.8 in TS 38.214 [6]. The values of the rank indicator field are mapped to allowed rank indicator values with increasing order, where '0' is mapped to the smallest allowed rank indicator value. The values of the indicator field are mapped to the allowed values of $N_{NZ}$ , according to Clause 5.2.2.2.8 TS 38.214 [6], with increasing order, where '0' is mapped to . + +The bitwidth for RI/CQI of *codebookType= typeII-Doppler* is provided in Table 6.3.2.1.2-8B. + +**Table 6.3.2.1.2-8B: RI and CQI of *codebookType= typeII-Doppler*** + +| Field | Bitwidth | +|---------------------------------------------------------------------------------|----------------------------------------| +| Rank Indicator | | +| Wide-band CQI | 4 | +| Subband differential CQI | 2 | +| The second time-domain wide-band CQI | 4 | +| The second time-domain subband differential CQI | 2 | +| Indicator of the total number of non-zero coefficients summed across all layers | if max allowed rank is 1;
otherwise | + +Where $N_{RI}$ is the number of allowed rank indicator values according to Clause 5.2.2.2.10 TS 38.214 [6], $N_{max}$ , $N_{WB}$ , $N_{SB}$ , and $N_{NZ}$ are given by Clause 5.2.2.2.10 in TS 38.214 [6]. The values of the rank indicator field are mapped to allowed rank indicator values with increasing order, where '0' is mapped to the smallest allowed rank indicator value. The values of the indicator field are mapped to the allowed values of $N_{NZ}$ , according to Clause 5.2.2.2.10 TS 38.214 [6], with increasing order, where '0' is mapped to . + +The bitwidth for RI/CQI of *codebookType*=*typeII-PortSelection-r17* or *typeII-Doppler-PortSelection* is provided in Table 6.3.2.1.2-9. + +**Table 6.3.2.1.2-9: RI and CQI of *codebookType*=*typeII-PortSelection-r17* or *typeII-Doppler-PortSelection-r18*** + +| Field | Bitwidth | +|---------------------------------------------------------------------------------|----------------------------------------| +| Rank Indicator | | +| Wide-band CQI | 4 | +| Subband differential CQI | 2 | +| Indicator of the total number of non-zero coefficients summed across all layers | if max allowed rank is 1;
otherwise | + +where $N_{RI}$ is the number of allowed rank indicator values according to Clauses 5.2.2.2.7 and Clauses 5.2.2.2.11 [6, TS 38.214], where $N_{WB}$ , $N_{SB}$ , and $N_{NZ}$ are given by Clause 5.2.2.2.7 and Clauses 5.2.2.2.11 in [6, TS 38.214]. The values of the rank indicator field are mapped to allowed rank indicator values with increasing order, where '0' is mapped to the smallest allowed rank indicator value. The values of the indicator field are mapped to the allowed values of $N_{NZ}$ , according to Clauses 5.2.2.2.7 and Clauses 5.2.2.2.11 [6, TS 38.214], with increasing order, where '0' is mapped to 0. + +The bitwidth for RI/CQI of *codebookType*=*typeII-CJT-PortSelection* is provided in Table 6.3.2.1.2-9A. + +**Table 6.3.2.1.2-9A: RI and CQI of *codebookType*= *typeII-CJT-PortSelection*** + +| Field | Bitwidth | +|--------------------------------------------------------------------------------------------------------------------------|----------------------------------------| +| Rank Indicator | | +| Wide-band CQI | 4 | +| Subband differential CQI | 2 | +| Indicator of the total number of non-zero coefficients summed across all layers, and all CSI-RS resources if configured, | if max allowed rank is 1;
otherwise | + +Where $N_{RI}$ is the number of allowed rank indicator values according to Clause 5.2.2.2.9 TS 38.214 [6] is the maximum of $N_{RI}$ for all configured combinations, where $N_{WB}$ , $N_{SB}$ , and $N_{NZ}$ are given by Clause 5.2.2.2.9 in TS 38.214 [6], and $N_{NZ}$ . The values of the rank indicator field are mapped to allowed rank indicator values with increasing order, where '0' is mapped to the smallest allowed rank indicator value. The values of the indicator field are mapped to the allowed values of $N_{NZ}$ , according to Clause 5.2.2.2.9 TS 38.214 [6], with increasing order, where '0' is mapped to 0. + +The bitwidth for *reportQuantity*=*tdcp* is provided in Table 6.3.2.1.2-10. + +**Table 6.3.2.1.2-10: Amplitude and phase values for *reportQuantity*=*tdcp*** + +| Field | Bitwidth | +|-----------------|----------| +| Amplitude value | 4 | +| Phase value | 4 | + +##### 6.3.2.1.3 CG-UCI + +For CG-UCI bits transmitted on a CG PUSCH when the higher layer parameter *cg-RetransmissionTimer* is configured, the CG-UCI bit sequence is determined as follows: + +- set $b_{CG}$ for $n=0, 1, \dots, N_{CG}-1$ , where the CG-UCI bit sequence is given by Table 6.3.2.1.3-1, mapped in the order from upper part to lower part. + +**Table 6.3.2.1.3-1: Mapping order of CG-UCI fields** + +| Field | Bitwidth | +|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HARQ process number | 5 if nrofHARQ-Processes-v1700 in ConfiguredGrantConfig is configured;
4 otherwise. | +| Redundancy version | 2 | +| New data indicator | 1 | +| Channel Occupancy Time (COT) sharing information |

if both higher layer parameter ul-toDL-COT-SharingED-Threshold and higher layer parameter cg-COT-SharingList are configured, or if both higher layer parameter semiStaticChannelAccessConfigUE and higher layer parameter cg-COT-SharingList are configured, or if higher layer parameter cg-COT-SharingList is configured in frequency range 2-2, where C is the number of combinations configured in cg-COT-SharingList;

1 if higher layer parameter ul-toDL-COT-SharingED-Threshold is not configured, and if higher layer parameter semiStaticChannelAccessConfigUE is not configured, and if higher layer parameter cg-COT-SharingOffset is configured;

0 otherwise.

If a UE indicates COT sharing other than "no sharing" in a CG PUSCH within the UE's initiated COT, the UE should provide consistent COT sharing information in all the subsequent CG PUSCHs, if any, occurring within the same UE's initiated COT such that the same DL starting point and duration are maintained.

| + +##### 6.3.2.1.3A UTO-UCI + +For UTO-UCI bits transmitted on a CG PUSCH when the higher layer parameter *nrof\_UTO\_UCI* is configured, the UTO-UCI bit sequence is determined as follows: + +- set *UTO-UCI bits* for *nrof\_UTO\_UCI*, where *nrof\_UTO\_UCI* is provided by *nrof\_UTO\_UCI*, and the UTO-UCI bit sequence is given by clause 9.3.1 of [5, TS 38.213]. + +##### 6.3.2.1.4 HARQ-ACK and CG-UCI/UTO-UCI + +If the higher layer parameter *nrof\_UTO\_UCI* is configured, the procedure in this clause 6.3.2.1.4 applies by replacing CG-UCI with UTO-UCI in all the notations and texts, and replacing "When higher layer parameter *cg-UCI-Multiplexing* is configured" with "When UTO-UCI and HARQ-ACK have the same priority index and are jointly encoded and transmitted on a PUSCH". + +When higher layer parameter *cg-UCI-Multiplexing* is configured, the UCI bit sequence is determined as follows, where *C* is number of CG-UCI bits; + +- The CG-UCI bits are mapped to the UCI bit sequence, where for *C*. The CG-UCI bit sequence is given by Table 6.3.2.1.3-1 mapped in the order from upper part to lower part, and *C* is number of CG-UCI bits; +- The HARQ-ACK bits are mapped to the UCI bit sequence, where for *A*. The HARQ-ACK bit sequence is given by Clause 9.1 of [5, TS38.213], and *A* is number of HARQ-ACK bits. + +##### 6.3.2.1.5 UCI with different priority indexes + +If the higher layer parameter *nrof\_UTO\_UCI* is configured, the procedure in this clause 6.3.2.1.5 applies by replacing CG-UCI with UTO-UCI in all the notations and texts, and replacing "is given by Table 6.3.2.1.3-1 mapped in the order from upper part to lower part" with "is given by clause 9.3.1 of [5, TS 38.213]". + +If *uci-MuxWithDiffPrio* is configured, and HARQ-ACK bits associated with priority index 0, and CSI part 1 if any are transmitted on a PUSCH associated with priority index 1, the following UCI bit sequences are generated, , and if any, according to the following: + +- If CSI part 1 is also transmitted on the PUSCH, + - Set for as the bit sequence of CSI part 1, where the CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.2.1.2-6, are mapped to the UCI bit sequence starting with . + - Set for and , where the HARQ-ACK bit sequence associated with priority index 0 is given by Clause 9.1 of [5, TS 38.213]. +- Otherwise, set for and , where the HARQ-ACK bit sequence associated with priority index 0 is given by Clause 9.1 of [5, TS 38.213]. + +If *uci-MuxWithDiffPrio* is configured, and HARQ-ACK bits associated with priority index 1, and CSI if any are transmitted on a PUSCH associated with priority index 0, the following UCI bit sequences are generated,, if any, and if any, according to the following: + +- If HARQ-ACK bits associated with priority index 1 and CSI are transmitted on the PUSCH without UL-SCH and the CSI includes CSI part 1 without CSI part 2, and there is only one HARQ-ACK bit associated with priority index 1 given by Clause 9.1 of [5, TS 38.213], set , , and ; otherwise, set for and , where the HARQ-ACK bit sequence associated with priority index 1 is given by Clause 9.1 of [5, TS 38.213]; +- Set for as the bit sequence of CSI part 1, if CSI part 1 is also transmitted on the PUSCH, where the CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.2.1.2-6, are mapped to the UCI bit sequence starting with ; +- Set for as the bit sequence of CSI part 2, if CSI part 2 is also transmitted on the PUSCH, where the CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.2.1.2-7, are mapped to the UCI bit sequence starting with . + +If *uci-MuxWithDiffPrio* is configured, and HARQ-ACK bits associated with priority index 0, HARQ-ACK bits associated with priority index 1 and/or CG-UCI associated with priority index 1, and CSI part 1 if any are transmitted on a PUSCH, the following UCI bit sequences are generated,, , and if any, according to the following: + +- Set for and if HARQ-ACK bits associated with priority index 1 are transmitted without CG-UCI associated with priority index 1, where the HARQ-ACK bit sequence associated with priority index 1 is given by Clause 9.1 of [5, TS 38.213]; +- Set for and if CG-UCI associated with priority index 1 is transmitted without HARQ-ACK bits associated with priority index 1, where the CG-UCI bit sequence associated with priority index 1 is given by Table 6.3.2.1.3-1 mapped in the order from upper part to lower part; +- Set as follows, if both CG-UCI associated with priority index 1 and HARQ-ACK bits associated with priority index 1 are transmitted, where + - The CG-UCI bits are mapped to the UCI bit sequence , where for . The CG-UCI bit sequence is given by Table 6.3.2.1.3-1 mapped in the order from upper part to lower part, and is number of CG-UCI bits + - The HARQ-ACK bits are mapped to the UCI bit sequence , where for . The HARQ-ACK bit sequence associated with priority index 1 is given by Clause 9.1 of [5, TS 38.213]. +- If CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 1, + - Set for as the bit sequence of CSI part 1, where the CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.2.1.2-6, are mapped to the UCI bit sequence starting with . + - Set for and , where the HARQ-ACK bit sequence associated with priority index 0 is given by Clause 9.1 of [5, TS 38.213]. +- Otherwise, + - Set for and , where the HARQ-ACK bit sequence associated with priority index 0 is given by Clause 9.1 of [5, TS 38.213]. + - Set for and , if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 0, where the CSI part 1 sequence is given by Table 6.3.2.1.2-6 by replacing , and the CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.2.1.2-6, are mapped to the CSI part 1 sequence starting with . + +If *uci-MuxWithDiffPrio* is configured, and CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 if any, HARQ-ACK bits associated with priority index 1, and CSI part 1 if any are transmitted on a + +PUSCH associated with priority index 0, the following UCI bit sequences are generated, $\mathbf{b}_{ack}$ , $\mathbf{b}_{cqi}$ and $\mathbf{b}_{csi}$ if any, according to the following: + +- Set $\mathbf{b}_{ack}$ for $\mathbf{b}_{ack}$ , where the HARQ-ACK bit sequence associated with priority index 1 is given by Clause 9.1 of [5, TS 38.213]; +- Set $\mathbf{b}_{cqi}$ for $\mathbf{b}_{cqi}$ if CG-UCI associated with priority index 0 is transmitted without HARQ-ACK bits associated with priority index 0, where the CG-UCI bit sequence associated with priority index 0 is given by Table 6.3.2.1.3-1 mapped in the order from upper part to lower part; +- Set $\mathbf{b}_{csi}$ as follows if both CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 are transmitted, where + - The CG-UCI bits are mapped to the UCI bit sequence $\mathbf{b}_{cqi}$ , where for $\mathbf{b}_{cqi}$ . The CG-UCI bit sequence is given by Table 6.3.2.1.3-1 mapped in the order from upper part to lower part, and $N_{cqi}$ is number of CG-UCI bits + - The HARQ-ACK bits are mapped to the UCI bit sequence $\mathbf{b}_{ack}$ , where for $\mathbf{b}_{ack}$ . The HARQ-ACK bit sequence associated with priority index 0 is given by Clause 9.1 of [5, TS 38.213]. +- Set $\mathbf{b}_{csi}$ for $\mathbf{b}_{csi}$ , if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 0, where the CSI part 1 sequence is given by Table 6.3.2.1.2-6 by replacing $\mathbf{b}_{cqi}$ , and the CSI fields of all CSI reports, in the order from upper part to lower part in Table 6.3.2.1.2-6, are mapped to the CSI part 1 sequence starting with $\mathbf{b}_{csi}$ . + +#### 6.3.2.2 Code block segmentation and CRC attachment + +Denote the bits of the payload by $\mathbf{b}$ , where $N$ is the payload size. The procedure in 6.3.2.2.1 applies for $\mathbf{b}_{ack}$ and the procedure in Clause 6.3.2.2.2 applies for $\mathbf{b}_{cqi}$ . + +##### 6.3.2.2.1 UCI encoded by Polar code + +Code block segmentation and CRC attachment is performed according to Clause 6.3.1.2.1. + +##### 6.3.2.2.2 UCI encoded by channel coding of small block lengths + +The procedure in Clause 6.3.1.2.2 applies. + +#### 6.3.2.3 Channel coding of UCI + +##### 6.3.2.3.1 UCI encoded by Polar code + +Channel coding is performed according to Clause 6.3.1.3.1, except that the rate matching output sequence length is given in Clause 6.3.2.4.1. + +##### 6.3.2.3.2 UCI encoded by channel coding of small block lengths + +Information bits are delivered to the channel coding block. They are denoted by $\mathbf{b}$ , where $N$ is the number of bits. + +The information bits are encoded according to Clause 5.3.3. + +After encoding the bits are denoted by $\mathbf{b}$ , where $N$ is the number of coded bits. + +#### 6.3.2.4 Rate matching + +In case where there are more than one UL-SCH transport blocks for the PUSCH transmission, the UCI information is multiplexed only on the UL-SCH transport block with highest $I_{MCS}$ value for the initial PUSCH, where $I_{MCS}$ is as defined in Clause 6.1.4.1 in [6, TS 38.214]. In case the two transport blocks have the same $I_{MCS}$ value for the initial PUSCH, the UCI information is multiplexed with data only on the first transport block. The PUSCH for UCI multiplexing in this Clause refers to the UL-SCH transport block for UCI multiplexing. + +##### 6.3.2.4.1 UCI encoded by Polar code + +If the higher layer parameter *nrof\_UTO\_UCI* is configured, the procedures in this clause and the clauses it refers to apply by replacing CG-UCI with UTO-UCI in all the notations and texts, when applicable. + +###### 6.3.2.4.1.1 HARQ-ACK + +For HARQ-ACK transmission on PUSCH not using repetition type B with UL-SCH and if *numberOfSlotsTBoMS* is not present in the resource allocation table, or if *numberOfSlotsTBoMS* is present in the resource allocation table and the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI is equal to 1, the number of coded modulation symbols per layer for HARQ-ACK transmission, denoted as $O_{ACK}$ , is determined as follows: + +where + +- $O_{ACK}$ is the number of HARQ-ACK bits; +- if $O_{ACK} \geq 360$ , $L_{ACK} = 11$ ; otherwise $L_{ACK}$ is the number of CRC bits for HARQ-ACK determined according to Clause 6.3.1.2.1; +- $N_{CB}$ is the number of code blocks for UL-SCH of the PUSCH transmission; +- if the DCI format scheduling the PUSCH transmission includes a CBGTI field indicating that the UE shall not transmit the $i$ -th code block, $C_{i,0} = 0$ ; otherwise, $C_{i,0}$ is the $i$ -th code block size for UL-SCH of the PUSCH transmission; +- $B$ is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers; +- $M_{sc}^{PT-RS}(l)$ is the number of subcarriers in OFDM symbol $l$ that carries PTRS, in the PUSCH transmission; +- $M_{sc}^{UCI}(l)$ is the number of resource elements that can be used for transmission of UCI in OFDM symbol $l$ , for $l$ , in the PUSCH transmission and $l$ is the total number of OFDM symbols of the PUSCH, including all OFDM symbols used for DMRS; + - for any OFDM symbol that carries DMRS of the PUSCH, $M_{sc}^{UCI}(l) = 0$ ; + - for any OFDM symbol that does not carry DMRS of the PUSCH, $M_{sc}^{UCI}(l) = M_{sc}^{PUSCH} - M_{sc}^{PT-RS}(l)$ ; +- $\alpha$ is configured by higher layer parameter *scaling*; +- $l_0$ is the symbol index of the first OFDM symbol that does not carry DMRS of the PUSCH, after the first DMRS symbol(s), in the PUSCH transmission. + +For HARQ-ACK transmission on PUSCH not using repetition type B with UL-SCH, and if *numberOfSlotsTBoMS* is present in the resource allocation table and the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI is larger than 1, the number of coded modulation symbols per layer for HARQ-ACK transmission, denoted as $O_{ACK}$ , is determined as follows: + +where + +- $numberOfSlotsTBoMS$ is the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI; +- $B$ is the number of subcarriers in OFDM symbol $l$ that carries PTRS, in the PUSCH transmission of TB processing over multiple slots in the slot with the HARQ-ACK transmission; +- $M_{sc}^{UCI}(l)$ is the number of resource elements that can be used for transmission of UCI in OFDM symbol $l$ , for $l$ , in the PUSCH transmission of TB processing over multiple slots in the slot with the HARQ-ACK transmission and $l$ is the total number of OFDM symbols of the PUSCH in the slot, including all OFDM symbols used for DMRS; + +- is the symbol index of the first OFDM symbol that does not carry DMRS of the PUSCH, after the first DMRS symbol(s), in the PUSCH transmission of TB processing over multiple slots in the slot with the HARQ-ACK transmission; +- and all the other notations in the formula are defined the same as for PUSCH not using repetition type B and if *numberOfSlotsTBoMS* is not present in the resource allocation table. + +For HARQ-ACK transmission on an actual repetition of a PUSCH with repetition Type B with UL-SCH, the number of coded modulation symbols per layer for HARQ-ACK transmission, denoted as $Q'_{ACK}$ , is determined as follows: + +where + +- is the number of resource elements that can be used for transmission of UCI in OFDM symbol $l$ , for $l$ , in the PUSCH transmission assuming a nominal repetition without segmentation, and $N_{symb,all}^{PUSCH}$ is the total number of OFDM symbols in a nominal repetition of the PUSCH, including all OFDM symbols used for DMRS; +- for any OFDM symbol that carries DMRS of the PUSCH assuming a nominal repetition without segmentation, $l$ ; +- for any OFDM symbol that does not carry DMRS of the PUSCH assuming a nominal repetition without segmentation, where $M_{sc}^{PT-RS}(l)$ is the number of subcarriers in OFDM symbol $l$ that carries PTRS, in the PUSCH transmission assuming a nominal repetition without segmentation; +- is the number of resource elements that can be used for transmission of UCI in OFDM symbol $l$ , for $l$ , in the actual repetition of the PUSCH transmission, and $N_{symb,all}^{PUSCH}$ is the total number of OFDM symbols in the actual repetition of the PUSCH transmission, including all OFDM symbols used for DMRS; +- for any OFDM symbol that carries DMRS of the actual repetition of the PUSCH transmission, $l$ ; +- for any OFDM symbol that does not carry DMRS of the actual repetition of the PUSCH transmission, where $M_{sc}^{PT-RS}(l)$ is the number of subcarriers in OFDM symbol $l$ that carries PTRS, in the actual repetition of the PUSCH transmission; +- and all the other notations in the formula are defined the same as for PUSCH not using repetition type B and if *numberOfSlotsTBoMS* is not present in the resource allocation table. + +For HARQ-ACK transmission on PUSCH without UL-SCH, the number of coded modulation symbols per layer for HARQ-ACK transmission, denoted as $Q'_{ACK}$ , is determined as follows: + +$$Q'_{ACK} = \min \left\{ \left\lceil \frac{(O_{ACK} + L_{ACK}) \cdot \beta_{offset}^{PUSCH}}{R \cdot Q_m} \right\rceil, \left\lceil \alpha \cdot \sum_{l=0}^{N_{symb,all}^{PUSCH}-1} M_{sc}^{UCI}(l) \right\rceil \right\}$$ + +where + +- is the number of HARQ-ACK bits; +- if $O_{ACK} \geq 360$ , $L_{ACK} = 11$ ; otherwise $L_{ACK}$ is the number of CRC bits for HARQ-ACK defined according to Clause 6.3.1.2.1; +- $\beta_{offset}^{PUSCH} = \beta_{offset}^{HARQ-ACK}$ ; +- is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers; +- $M_{sc}^{PT-RS}(l)$ is the number of subcarriers in OFDM symbol $l$ that carries PTRS, in the PUSCH transmission; +- $M_{sc}^{UCI}(l)$ is the number of resource elements that can be used for transmission of UCI in OFDM symbol $l$ , for $l$ , in the PUSCH transmission and $N_{symb,all}^{PUSCH}$ is the total number of OFDM symbols of the PUSCH, including all OFDM symbols used for DMRS; +- for any OFDM symbol that carries DMRS of the PUSCH, $M_{sc}^{UCI}(l) = 0$ ; +- for any OFDM symbol that does not carry DMRS of the PUSCH, $M_{sc}^{UCI}(l) = M_{sc}^{PUSCH} - M_{sc}^{PT-RS}(l)$ ; + +- $l_0$ is the symbol index of the first OFDM symbol that does not carry DMRS of the PUSCH, after the first DMRS symbol(s), in the PUSCH transmission; +- $R$ is the code rate of the PUSCH, determined according to Clause 6.1.4.1 of [6, TS38.214]; +- $M$ is the modulation order of the PUSCH; +- $\alpha$ is configured by higher layer parameter *scaling*. + +The input bit sequence to rate matching is denoted as $w_{k,n}$ where $k$ is the code block number, and $n$ is the number of coded bits in code block number $k$ . + +Rate matching is performed according to Clause 5.4.1 by setting $N_{\text{info}}$ and the rate matching output sequence length to $N_{\text{info}}$ , where + +- $N_{\text{info}}$ is the number of code blocks for UCI determined according to Clause 5.2.1; +- $M$ is the number of transmission layers of the PUSCH; +- $\alpha$ is the modulation order of the PUSCH; +- $\beta$ is the number of bits per modulation symbol. + +The output bit sequence after rate matching is denoted as $w'_{k,n}$ where $n$ is the length of rate matching output sequence in code block number $k$ . + +###### 6.3.2.4.1.2 CSI part 1 + +For CSI part 1 transmission on PUSCH not using repetition type B with UL-SCH and if *numberOfSlotsTBoMS* is not present in the resource allocation table, or if *numberOfSlotsTBoMS* is present in the resource allocation table and the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI is equal to 1, the number of coded modulation symbols per layer for CSI part 1 transmission, denoted as $O_{\text{CSI-1}}$ , is determined as follows: + +where + +- $O_{\text{CSI-1}}$ is the number of bits for CSI part 1; +- if $O_{\text{CSI-1}} \geq 360$ , $L_{\text{CSI-1}} = 11$ ; otherwise $L_{\text{CSI-1}}$ is the number of CRC bits for CSI part 1 determined according to Clause 6.3.1.2.1; +- $N_{\text{CB}}$ is the number of code blocks for UL-SCH of the PUSCH transmission; +- if the DCI format scheduling the PUSCH transmission includes a CBGTI field indicating that the UE shall not transmit the $k$ -th code block, $C_{k,n} = 0$ ; otherwise, $C_{k,n}$ is the $k$ -th code block size for UL-SCH of the PUSCH transmission; +- $N_{\text{sc}}$ is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers; +- $M_{\text{sc}}^{\text{PT-RS}}(l)$ is the number of subcarriers in OFDM symbol $l$ that carries PTRS, in the PUSCH transmission; +- if HARQ-ACK is present for transmission on the same PUSCH with UL-SCH and without CG-UCI, where $Q'_{\text{ACK}}$ is the number of coded modulation symbols per layer for HARQ-ACK transmitted on the PUSCH as defined in + +$$Q'_{\text{ACK}} = \sum_{l=0}^{N_{\text{symbol}}^{\text{PUSCH}} - 1} \bar{M}_{\text{sc, rvd}}^{\text{ACK}}(l)$$ + +clause 6.3.2.4.1.1 if number of HARQ-ACK information bits is more than 2, and + +if the number of HARQ-ACK information bits is no more than 2 bits, where $\bar{M}_{\text{sc, rvd}}^{\text{ACK}}(l)$ is the number of reserved resource elements for potential HARQ-ACK transmission in OFDM symbol $l$ , for $l$ , in the PUSCH transmission, defined in Clause 6.2.7; or + +- if both HARQ-ACK and CG-UCI are present on the same PUSCH with UL-SCH, where $M_{sc}^{UCI}(l)$ is the number of coded modulation symbols per layer for HARQ-ACK and CG-UCI transmitted on the PUSCH as defined in clause 6.3.2.4.1.5; or +- if CG-UCI is present on the same PUSCH with UL-SCH and without HARQ-ACK, where $M_{sc}^{UCI}(l)$ is the number of coded modulation symbols per layer for CG-UCI transmitted on the PUSCH as defined in clause 6.3.2.4.1.4; +- $M_{sc}^{UCI}(l)$ is the number of resource elements that can be used for transmission of UCI in OFDM symbol $l$ , for $l$ , in the PUSCH transmission and $L$ is the total number of OFDM symbols of the PUSCH, including all OFDM symbols used for DMRS; + - for any OFDM symbol that carries DMRS of the PUSCH, $M_{sc}^{UCI}(l) = 0$ ; + - for any OFDM symbol that does not carry DMRS of the PUSCH, $M_{sc}^{UCI}(l) = M_{sc}^{PUSCH} - M_{sc}^{PTRS}(l)$ ; +- $\alpha$ is configured by higher layer parameter *scaling*. + +For CSI part 1 transmission on PUSCH not using repetition type B with UL-SCH, and if *numberOfSlotsTBoMS* is present in the resource allocation table and the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI is larger than 1, the number of coded modulation symbols per layer for CSI part 1 transmission, denoted as $M_{sc}^{CSI}$ , is determined as follows: + +where + +- $L$ is the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI; +- $N_{sc}^{PTRS}$ is the number of subcarriers in OFDM symbol $l$ that carries PTRS, in the PUSCH transmission of TB processing over multiple slots in the slot with the CSI part 1 transmission; +- $M_{sc}^{UCI}(l)$ is the number of resource elements that can be used for transmission of UCI in OFDM symbol $l$ , for $l$ , in the PUSCH transmission of TB processing over multiple slots in the slot with the CSI part 1 transmission and $L$ is the total number of OFDM symbols of the PUSCH in the slot, including all OFDM symbols used for DMRS; +- and all the other notations in the formula are defined the same as for PUSCH not using repetition type B and if *numberOfSlotsTBoMS* is not present in the resource allocation table. + +For CSI part 1 transmission on an actual repetition of a PUSCH with repetition Type B with UL-SCH, the number of coded modulation symbols per layer for CSI part 1 transmission, denoted as $M_{sc}^{CSI}$ , is determined as follows: + +where + +- $L$ is the number of resource elements that can be used for transmission of UCI in OFDM symbol $l$ , for $l$ , in the PUSCH transmission assuming a nominal repetition without segmentation, and $L$ is the total number of OFDM symbols in a nominal repetition of the PUSCH, including all OFDM symbols used for DMRS; + - for any OFDM symbol that carries DMRS of the PUSCH assuming a nominal repetition without segmentation, $M_{sc}^{UCI}(l) = 0$ ; + - for any OFDM symbol that does not carry DMRS of the PUSCH assuming a nominal repetition without segmentation, where $N_{sc}^{PTRS}$ is the number of subcarriers in OFDM symbol $l$ that carries PTRS, in the PUSCH transmission assuming a nominal repetition without segmentation; +- $M_{sc}^{UCI}(l)$ is the number of resource elements that can be used for transmission of UCI in OFDM symbol $l$ , for $l$ , in the actual repetition of the PUSCH transmission, and $L$ is the total number of OFDM symbols in the actual repetition of the PUSCH transmission, including all OFDM symbols used for DMRS; + - for any OFDM symbol that carries DMRS of the actual repetition of the PUSCH transmission, $M_{sc}^{UCI}(l) = 0$ ; + - for any OFDM symbol that does not carry DMRS of the actual repetition of the PUSCH transmission, where $N_{sc}^{PTRS}$ is the number of subcarriers in OFDM symbol $l$ that carries PTRS, in the actual repetition of the PUSCH transmission; +- and all the other notations in the formula are defined the same as for PUSCH not using repetition type B and if *numberOfSlotsTBoMS* is not present in the resource allocation table. + +For CSI part 1 transmission on PUSCH without UL-SCH, the number of coded modulation symbols per layer for CSI part 1 transmission, denoted as $Q'_{CSI-1}$ , is determined as follows: + +if there is CSI part 2 to be transmitted on the PUSCH, + +$$Q'_{CSI-1} = \min \left\{ \left\lceil \frac{(O_{CSI-1} + L_{CSI-1}) \cdot \beta_{offset}^{PUSCH}}{R \cdot Q_m} \right\rceil, \sum_{l=0}^{N_{symbolall}^{PUSCH}-1} M_{sc}^{UCI}(l) - Q'_{ACK} \right\}$$ + +else + +$$Q'_{CSI-1} = \sum_{l=0}^{N_{symbolall}^{PUSCH}-1} M_{sc}^{UCI}(l) - Q'_{ACK}$$ + +end if + +where + +- $O_{CSI-1}$ is the number of bits for CSI part 1; +- if $O_{CSI-1} \geq 360$ , $L_{CSI-1} = 11$ ; otherwise $L_{CSI-1}$ is the number of CRC bits for CSI part 1 determined according to Clause 6.3.1.2.1; +- $R$ is the code rate of the PUSCH, determined according to Clause 6.1.4.1 of [6, TS38.214]; +- $Q_m$ is the modulation order of the PUSCH. +- $M_{sc}^{PT-RS}(l)$ is the number of subcarriers in OFDM symbol $l$ that carries PTRS, in the PUSCH transmission; +- $Q'_{ACK}$ is the number of coded modulation symbols per layer for HARQ-ACK transmitted on the PUSCH if number of HARQ-ACK information bits is more than 2, and + +$$Q'_{ACK} = \sum_{l=0}^{N_{symbolall}^{PUSCH}-1} \bar{M}_{sc, rvd}^{ACK}(l)$$ + +if the number of HARQ-ACK information bits is no more than 2 bits, where $\bar{M}_{sc, rvd}^{ACK}(l)$ is the number of reserved resource elements for potential HARQ-ACK transmission in OFDM symbol $l$ , for $l$ , in the PUSCH transmission, defined in Clause 6.2.7; + +- $M_{sc}^{UCI}(l)$ is the number of resource elements that can be used for transmission of UCI in OFDM symbol $l$ , for $l$ , in the PUSCH transmission and $N_{symbolall}^{PUSCH}$ is the total number of OFDM symbols of the PUSCH, including all OFDM symbols used for DMRS; + - for any OFDM symbol that carries DMRS of the PUSCH, $M_{sc}^{UCI}(l) = 0$ ; + - for any OFDM symbol that does not carry DMRS of the PUSCH, $M_{sc}^{UCI}(l) = M_{sc}^{PUSCH} - M_{sc}^{PT-RS}(l)$ ; +- $R$ is the code rate of the PUSCH, determined according to Clause 6.1.4.1 of [6, TS38.214]; +- $Q_m$ is the modulation order of the PUSCH. + +The input bit sequence to rate matching is $c_{n,k}$ where $n$ is the code block number, and $k$ is the number of coded bits in code block number $n$ . + +Rate matching is performed according to Clause 5.4.1 by setting $N_{info}$ and the rate matching output sequence length to $N_{info}$ , where + +- $N_{info}$ is the number of code blocks for UCI determined according to Clause 5.2.1; +- $N_{layers}$ is the number of transmission layers of the PUSCH; +- $Q_m$ is the modulation order of the PUSCH; +- $\beta_{offset}^{PUSCH}$ is the beta offset value for UCI determined according to Clause 5.2.1. + +The output bit sequence after rate matching is denoted as $o_{r,m}$ where $m$ is the length of rate matching output sequence in code block number $r$ . + +###### 6.3.2.4.1.3 CSI part 2 + +For CSI part 2 transmission on PUSCH not using repetition type B with UL-SCH and if *numberOfSlotsTBoMS* is not present in the resource allocation table, or if *numberOfSlotsTBoMS* is present in the resource allocation table and the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI is equal to 1, the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as $Q'_{\text{CSI-2}}$ , is determined as follows: + +where + +- $O_{\text{CSI-2}}$ is the number of bits for CSI part 2; +- if $O_{\text{CSI-2}} \geq 360$ , $L_{\text{CSI-2}} = 11$ ; otherwise $L_{\text{CSI-2}}$ is the number of CRC bits for CSI part 2 determined according to Clause 6.3.1.2.1; +- $N_{\text{CB}}$ is the number of code blocks for UL-SCH of the PUSCH transmission; +- if the DCI format scheduling the PUSCH transmission includes a CBGTI field indicating that the UE shall not transmit the $n$ -th code block, $n=0$ ; otherwise, $n$ is the $n$ -th code block size for UL-SCH of the PUSCH transmission; +- $B$ is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers; +- $M_{\text{sc}}^{\text{PT-RS}}(l)$ is the number of subcarriers in OFDM symbol $l$ that carries PTRS, in the PUSCH transmission; +- if HARQ-ACK is present for transmission on the same PUSCH with UL-SCH and without CG-UCI, where $Q'_{\text{ACK}}$ is the number of coded modulation symbols per layer for HARQ-ACK transmitted on the PUSCH as defined in clause 6.3.2.4.1.1 if number of HARQ-ACK information bits is more than 2, and if the number of HARQ-ACK information bits is 1 or 2 bits; or +- if both HARQ-ACK and CG-UCI are present on the same PUSCH with UL-SCH, where $Q'_{\text{ACK}}$ is the number of coded modulation symbols per layer for HARQ-ACK and CG-UCI transmitted on the PUSCH as defined in clause 6.3.2.4.1.5; or +- if CG-UCI is present on the same PUSCH with UL-SCH and without HARQ-ACK, where $Q'_{\text{CG-UCI}}$ is the number of coded modulation symbols per layer for CG-UCI transmitted on the PUSCH as defined in clause 6.3.2.4.1.4; +- $Q'_{\text{CSI-1}}$ is the number of coded modulation symbols per layer for CSI part 1 transmitted on the PUSCH; +- $M_{\text{sc}}^{\text{UCI}}(l)$ is the number of resource elements that can be used for transmission of UCI in OFDM symbol $l$ , for $l$ , in the PUSCH transmission and $N_{\text{symb}}^{\text{PUSCH}}$ is the total number of OFDM symbols of the PUSCH, including all OFDM symbols used for DMRS; + - for any OFDM symbol that carries DMRS of the PUSCH, $M_{\text{sc}}^{\text{UCI}}(l) = 0$ ; + - for any OFDM symbol that does not carry DMRS of the PUSCH, $M_{\text{sc}}^{\text{UCI}}(l) = M_{\text{sc}}^{\text{PUSCH}} - M_{\text{sc}}^{\text{PT-RS}}(l)$ . +- $\alpha$ is configured by higher layer parameter *scaling*. + +For CSI part 2 transmission on PUSCH not using repetition type B with UL-SCH, and if *numberOfSlotsTBoMS* is present in the resource allocation table and the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI is larger than 1, the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as $Q'_{\text{CSI-2}}$ , is determined as follows: + +where + +- is the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI; +- is the number of subcarriers in OFDM symbol $l$ , for $l$ , in the PUSCH transmission of TB processing over multiple slots in the slot with the CSI part 2 transmission; +- is the number of resource elements that can be used for transmission of UCI in OFDM symbol $l$ , for $l$ , in the PUSCH transmission of TB processing over multiple slots in the slot with the CSI part 2 transmission and is the total number of OFDM symbols of the PUSCH in the slot, including all OFDM symbols used for DMRS; +- and all the other notations in the formula are defined the same as for PUSCH not using repetition type B and if *numberOfSlotsTBoMS* is not present in the resource allocation table. + +For CSI part 2 transmission on an actual repetition of a PUSCH with repetition Type B with UL-SCH, the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as $Q'_{CSI-2}$ , is determined as follows: + +where + +- is the number of resource elements that can be used for transmission of UCI in OFDM symbol $l$ , for $l$ , in the PUSCH transmission assuming a nominal repetition without segmentation, and $N_{\text{symb,all}}^{\text{PUSCH}}$ is the total number of OFDM symbols in a nominal repetition of the PUSCH, including all OFDM symbols used for DMRS; +- for any OFDM symbol that carries DMRS of the PUSCH assuming a nominal repetition without segmentation, $M_{\text{sc}}^{\text{PT-RS}}(l) = 0$ ; +- for any OFDM symbol that does not carry DMRS of the PUSCH assuming a nominal repetition without segmentation, where $M_{\text{sc}}^{\text{PT-RS}}(l)$ is the number of subcarriers in OFDM symbol $l$ that carries PTRS, in the PUSCH transmission assuming a nominal repetition without segmentation; +- is the number of resource elements that can be used for transmission of UCI in OFDM symbol $l$ , for $l$ , in the actual repetition of the PUSCH transmission, and $N_{\text{symb,all}}^{\text{PUSCH}}$ is the total number of OFDM symbols in the actual repetition of the PUSCH transmission, including all OFDM symbols used for DMRS; +- for any OFDM symbol that carries DMRS of the actual repetition of the PUSCH transmission, $M_{\text{sc}}^{\text{PT-RS}}(l) = 0$ ; +- for any OFDM symbol that does not carry DMRS of the actual repetition of the PUSCH transmission, where $M_{\text{sc}}^{\text{PT-RS}}(l)$ is the number of subcarriers in OFDM symbol $l$ that carries PTRS, in the actual repetition of the PUSCH transmission; +- and all the other notations in the formula are defined the same as for PUSCH not using repetition type B and if *numberOfSlotsTBoMS* is not present in the resource allocation table. + +For CSI part 2 transmission on PUSCH without UL-SCH, the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as $Q'_{CSI-2}$ , is determined as follows: + +$$Q'_{CSI-2} = \sum_{l=0}^{N_{\text{symb,all}}^{\text{PUSCH}}-1} M_{\text{sc}}^{\text{UCI}}(l) - Q'_{\text{ACK}} - Q'_{CSI-1}$$ + +where + +- is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers; +- $M_{\text{sc}}^{\text{PT-RS}}(l)$ is the number of subcarriers in OFDM symbol $l$ that carries PTRS, in the PUSCH transmission; +- is the number of coded modulation symbols per layer for HARQ-ACK transmitted on the PUSCH if number of HARQ-ACK information bits is more than 2, and 0 if the number of HARQ-ACK information bits is 1 or 2 bits; +- $Q'_{CSI-1}$ is the number of coded modulation symbols per layer for CSI part 1 transmitted on the PUSCH; +- $M_{\text{sc}}^{\text{UCI}}(l)$ is the number of resource elements that can be used for transmission of UCI in OFDM symbol $l$ , for $l$ , in the PUSCH transmission and $N_{\text{symb,all}}^{\text{PUSCH}}$ is the total number of OFDM symbols of the PUSCH, including all OFDM symbols used for DMRS; +- for any OFDM symbol that carries DMRS of the PUSCH, $M_{\text{sc}}^{\text{UCI}}(l) = 0$ ; +- for any OFDM symbol that does not carry DMRS of the PUSCH, $M_{\text{sc}}^{\text{UCI}}(l) = M_{\text{sc}}^{\text{PUSCH}} - M_{\text{sc}}^{\text{PT-RS}}(l)$ . + +The input bit sequence to rate matching is $b_{i,k}$ where $i$ is the code block number, and $k$ is the number of coded bits in code block number $i$ . + +Rate matching is performed according to Clause 5.4.1 by setting $N_{cb}$ and the rate matching output sequence length to $N_{out}$ , where + +- $N_{cb}$ is the number of code blocks for UCI determined according to Clause 5.2.1; +- $N_{out}$ is the number of transmission layers of the PUSCH; +- $N_{out}$ is the modulation order of the PUSCH; +- $N_{out}$ is the number of transmission layers of the PUSCH; + +The output bit sequence after rate matching is denoted as $b'_{i,k}$ where $k$ is the length of rate matching output sequence in code block number $i$ . + +###### 6.3.2.4.1.4 CG-UCI + +For CG-UCI transmission on PUSCH with UL-SCH and if *numberOfSlotsTBoMS* is not present in the resource allocation table, or if *numberOfSlotsTBoMS* is present in the resource allocation table and the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI is equal to 1, the number of coded modulation symbols per layer for CG-UCI transmission, denoted as $N_{CGUCI}$ , is determined as follows: + +where + +- $N_{CGUCI}$ is the number of CG-UCI bits; +- $N_{CRC}$ is the number of CRC bits for CG-UCI determined according to Clause 6.3.1.2.1; +- $N_{CB}$ is the number of code blocks for UL-SCH of the PUSCH transmission; +- $N_{CB,r}$ is the $r$ -th code block size for UL-SCH of the PUSCH transmission; +- $N_{SC}$ is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers; +- $N_{SC,l}$ is the number of subcarriers in OFDM symbol $l$ that carries PTRS, in the PUSCH transmission; +- $N_{RE,l}$ is the number of resource elements that can be used for transmission of UCI in OFDM symbol $l$ , for $l=0,1,2,\dots,N_{sym}-1$ , in the PUSCH transmission and $N_{sym}$ is the total number of OFDM symbols of the PUSCH, including all OFDM symbols used for DMRS; + - for any OFDM symbol that carries DMRS of the PUSCH, $N_{RE,l}=0$ ; + - for any OFDM symbol that does not carry DMRS of the PUSCH, $N_{RE,l}=N_{SC}-N_{SC,l}$ ; + - $N_{SC,l}$ is configured by higher layer parameter *scaling*; +- $l_{start}$ is the symbol index of the first OFDM symbol that does not carry DMRS of the PUSCH, after the first DMRS symbol(s), in the PUSCH transmission. + +For CG-UCI transmission on PUSCH with UL-SCH, and if *numberOfSlotsTBoMS* is present in the resource allocation table and the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI is larger than 1, the number of coded modulation symbols per layer for CG-UCI transmission, denoted as $N_{CGUCI}$ , is determined as follows: + +where + +- $N_{CGUCI}$ is the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI; +- $N_{SC}$ is the number of subcarriers in OFDM symbol that carries PTRS, in the PUSCH transmission of TB processing over multiple slots in the slot with the CG-UCI transmission; + +- is the number of resource elements that can be used for transmission of UCI in OFDM symbol $l$ , for $l = 0, 1, 2, \dots, n_{\text{symbols}}$ , in the PUSCH transmission of TB processing over multiple slots in the slot with the CG-UCI transmission and $n_{\text{symbols}}$ is the total number of OFDM symbols of the PUSCH in the slot, including all OFDM symbols used for DMRS; +- is the symbol index of the first OFDM symbol that does not carry DMRS of the PUSCH, after the first DMRS symbol(s), in the PUSCH transmission of TB processing over multiple slots in the slot with the CG-UCI transmission; +- and all the other notations in the formula are defined the same as for PUSCH with UL-SCH and if *numberOfSlotsTBoMS* is not present in the resource allocation table. + +The input bit sequence to rate matching is $\mathbf{b}_{r,0}, \mathbf{b}_{r,1}, \dots, \mathbf{b}_{r,n_r-1}$ where $r$ is the code block number, and $n_r$ is the number of coded bits in code block number $r$ . + +Rate matching is performed according to Clause 5.4.1 by setting $n_{\text{info}}$ and the rate matching output sequence length to $n_r$ , where + +- $n_{\text{info}}$ is the number of code blocks for UCI determined according to Clause 5.2.1; +- $n_{\text{info}}$ is the number of transmission layers of the PUSCH; +- $n_{\text{info}}$ is the modulation order of the PUSCH; +- $n_r$ is the number of coded bits in code block number $r$ . + +The output bit sequence after rate matching is denoted as $\mathbf{b}_{r,0}, \mathbf{b}_{r,1}, \dots, \mathbf{b}_{r,n_r-1}$ where $n_r$ is the length of rate matching output sequence in code block number $r$ . + +###### 6.3.2.4.1.5 HARQ-ACK and CG-UCI + +For HARQ-ACK and CG-UCI transmission on PUSCH with UL-SCH and if *numberOfSlotsTBoMS* is not present in the resource allocation table, or if *numberOfSlotsTBoMS* is present in the resource allocation table and the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI is equal to 1, the number of coded modulation symbols per layer for HARQ-ACK and CG-UCI transmission, denoted as $n_{\text{symbols}}$ , is determined as follows: + +where + +- $n_{\text{ACK}}$ is the number of HARQ-ACK bits; +- $n_{\text{UCI}}$ is the number of CG-UCI bits; +- if $n_{\text{ACK}} > 0$ or $n_{\text{UCI}} > 0$ , $n_{\text{CRC}}$ is the number of CRC bits for HARQ-ACK and CG-UCI determined according to Clause 6.3.1.2.1; +- $n_{\text{info}}$ is the number of code blocks for UL-SCH of the PUSCH transmission; +- $n_r$ is the $r$ -th code block size for UL-SCH of the PUSCH transmission; +- $n_{\text{sc}}$ is the scheduled bandwidth of the PUSCH transmission, expressed as a number of subcarriers; +- $n_{\text{sc,l}}$ is the number of subcarriers in OFDM symbol $l$ that carries PTRS, in the PUSCH transmission; +- $n_{\text{RE,l}}$ is the number of resource elements that can be used for transmission of UCI in OFDM symbol $l$ , for $l = 0, 1, 2, \dots, n_{\text{symbols}}$ , in the PUSCH transmission and $n_{\text{symbols}}$ is the total number of OFDM symbols of the PUSCH, including all OFDM symbols used for DMRS; + - for any OFDM symbol that carries DMRS of the PUSCH, $n_{\text{RE,l}} = 0$ ; + - for any OFDM symbol that does not carry DMRS of the PUSCH, $n_{\text{RE,l}} = n_{\text{sc}}$ ; +- $n_{\text{sc}}$ is configured by higher layer parameter *scaling*; +- is the symbol index of the first OFDM symbol that does not carry DMRS of the PUSCH, after the first DMRS symbol(s), in the PUSCH transmission. + +For HARQ-ACK and CG-UCI transmission on PUSCH with UL-SCH, and if *numberOfSlotsTBoMS* is present in the resource allocation table and the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI is larger than 1, the number of coded modulation symbols per layer for HARQ-ACK and CG-UCI transmission, denoted as $\bar{Q}$ , is determined as follows: + +where + +- $\bar{Q}$ is the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI; +- $N_{sc}$ is the number of subcarriers in OFDM symbol $s$ that carries PTRS, in the PUSCH transmission of TB processing over multiple slots in the slot with the HARQ-ACK and CG-UCI transmission; +- $N_{RE}$ is the number of resource elements that can be used for transmission of UCI in OFDM symbol $s$ , for $s$ , in the PUSCH transmission of TB processing over multiple slots in the slot with the HARQ-ACK and CG-UCI transmission and $N_{RE}$ is the total number of OFDM symbols of the PUSCH in the slot, including all OFDM symbols used for DMRS; +- $s_{start}$ is the symbol index of the first OFDM symbol that does not carry DMRS of the PUSCH, after the first DMRS symbol(s), in the PUSCH transmission of TB processing over multiple slots in the slot with the HARQ-ACK and CG-UCI transmission; +- and all the other notations in the formula are defined the same as for PUSCH with UL-SCH and if *numberOfSlotsTBoMS* is not present in the resource allocation table. + +The input bit sequence to rate matching is $\mathbf{b}_{r,0}, \dots, \mathbf{b}_{r,n_r-1}$ where $r$ is the code block number, and $n_r$ is the number of coded bits in code block number $r$ . + +Rate matching is performed according to Clause 5.4.1 by setting $N_{cb}$ and the rate matching output sequence length to $\bar{Q}$ , where + +- $N_{cb}$ is the number of code blocks for UCI determined according to Clause 5.2.1; +- $N_{layers}$ is the number of transmission layers of the PUSCH; +- $M$ is the modulation order of the PUSCH; +- $\bar{Q}$ . + +The output bit sequence after rate matching is denoted as $\mathbf{b}'_{r,0}, \dots, \mathbf{b}'_{r,n'_r-1}$ where $n'_r$ is the length of rate matching output sequence in code block number $r$ . + +###### 6.3.2.4.1.6 UCI with different priority indexes + +In this clause, $\bar{Q}_{ACK}$ is equal to $\bar{Q}$ defined in [5, TS38.213] in case of PUSCH associated with priority index 1, and equal to $\bar{Q}$ defined in [5, TS38.213] in case of PUSCH associated with priority index 0. $\bar{Q}_{CSI}$ is equal to $\bar{Q}$ defined in [5, TS38.213] in case of PUSCH associated with priority index 0, and equal to $\bar{Q}$ defined in [5, TS38.213] in case of PUSCH associated with priority index 1. + +If *uci-MuxWithDiffPrio* is configured, and HARQ-ACK bits associated with priority index 0, and CSI part 1 if any are transmitted on a PUSCH associated with priority index 1: + +- If CSI part 1 is also transmitted on the PUSCH, + - Perform rate matching for CSI part 1 according to clause 6.3.2.4.1.2, by assuming the number of HARQ-ACK information bits to be transmitted on PUSCH in clause 6.3.2.4.1.2 is 0 bit. + - Perform rate matching for HARQ-ACK with priority index 0 according to clause 6.3.2.4.1.3, by taking HARQ-ACK with priority index 0 as CSI part 2 and replacing $\bar{Q}$ by $\bar{Q}_{ACK}$ , and assuming the number of HARQ-ACK information bits to be transmitted on PUSCH in clause 6.3.2.4.1.3 is 0 bit. +- Otherwise, perform rate matching for HARQ-ACK with priority index 0 according to clause 6.3.2.4.1.2, by taking HARQ-ACK with priority index 0 as CSI-part 1 and replacing $\bar{Q}$ by $\bar{Q}_{ACK}$ , and assuming the number of HARQ-ACK information bits to be transmitted on PUSCH in clause 6.3.2.4.1.2 is 0 bit. + +If *uci-MuxWithDiffPrio* is configured, and HARQ-ACK bits associated with priority index 1, and CSI if any are transmitted on a PUSCH associated with priority index 0: + +- Perform rate matching for HARQ-ACK with priority index 1 according to clause 6.3.2.4.1.1, by taking HARQ-ACK with priority index 1 as HARQ-ACK and replacing by . +- Perform rate matching for CSI part 1 according to clause 6.3.2.4.1.2, by taking HARQ-ACK with priority index 1 as HARQ-ACK, if CSI part 1 is also transmitted on the PUSCH. +- Perform rate matching for CSI part 2 according to clause 6.3.2.4.1.3, by taking HARQ-ACK with priority index 1 as HARQ-ACK, if CSI part 2 is also transmitted on the PUSCH. + +If *uci-MuxWithDiffPrio* is configured, and HARQ-ACK bits associated with priority index 0, HARQ-ACK bits associated with priority index 1 and/or CG-UCI associated with priority index 1, and CSI part 1 if any are transmitted on a PUSCH: + +- Perform rate matching for HARQ-ACK with priority index 1 according to clause 6.3.2.4.1.1, by taking HARQ-ACK with priority index 1 as HARQ-ACK and replacing by , if HARQ-ACK bits associated with priority index 1 are transmitted without CG-UCI associated with priority index 1. +- Perform rate matching for CG-UCI with priority index 1 according to clause 6.3.2.4.1.4, if CG-UCI associated with priority index 1 is transmitted without HARQ-ACK bits associated with priority index 1. +- Perform rate matching for CG-UCI with priority index 1 and HARQ-ACK with priority index 1 according to clause 6.3.2.4.1.5, if both CG-UCI associated with priority index 1 and HARQ-ACK bits associated with priority index 1 are transmitted, by taking HARQ-ACK with priority index 1 as HARQ-ACK and replacing by . +- If CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 1, + - Perform rate matching for CSI part 1 according to clause 6.3.2.4.1.2, by taking HARQ-ACK with priority index 1 if any as HARQ-ACK, and taking CG-UCI associated with priority index 1 if any as CG-UCI. + - Perform rate matching for HARQ-ACK with priority index 0 according to clause 6.3.2.4.1.3, by taking HARQ-ACK with priority index 0 as CSI part 2 and replacing by , and taking HARQ-ACK with priority index 1 if any as HARQ-ACK, and taking CG-UCI associated with priority index 1 if any as CG-UCI. +- Otherwise, + - Perform rate matching for HARQ-ACK with priority index 0 according to clause 6.3.2.4.1.2, by taking HARQ-ACK with priority index 0 as CSI-part 1 and replacing by and taking HARQ-ACK with priority index 1 if any as HARQ-ACK, and taking CG-UCI associated with priority index 1 if any as CG-UCI. + - Perform rate matching for CSI part 1 according to clause 6.3.2.4.1.3, by taking CSI part 1 as CSI part 2 and replacing by , taking HARQ-ACK with priority index 0 as CSI-part 1 and taking HARQ-ACK with priority index 1 as HARQ-ACK, if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 0. + +If *uci-MuxWithDiffPrio* is configured, and CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 if any, HARQ-ACK bits associated with priority index 1, and CSI part 1 if any are transmitted on a PUSCH associated with priority index 0: + +- Perform rate matching for HARQ-ACK with priority index 1 according to clause 6.3.2.4.1.1, by taking HARQ-ACK with priority index 1 as HARQ-ACK and replacing by . +- Perform rate matching for CG-UCI associated with priority index 0 according to clause 6.3.2.4.1.2, if CG-UCI associated with priority index 0 is transmitted without HARQ-ACK bits associated with priority index 0, by taking CG-UCI associated with priority index 0 as CSI-part 1 and replacing by and taking HARQ-ACK with priority index 1 as HARQ-ACK. +- Perform rate matching for CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 according to clause 6.3.2.4.1.2, if both CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 are transmitted, by taking CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 as CSI-part 1 and replacing by and taking HARQ-ACK with priority index 1 as HARQ-ACK. +- Perform rate matching for CSI part 1 according to clause 6.3.2.4.1.3, by taking CSI part 1 as CSI part 2 and replacing by , taking CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 if any as CSI-part 1 and taking HARQ-ACK with priority index 1 as HARQ-ACK, if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 0. + +##### 6.3.2.4.2 UCI encoded by channel coding of small block lengths + +If the higher layer parameter *nrof\_UTO\_UCI* is configured, the procedures in this clause and the clauses it refers to apply by replacing CG-UCI with UTO-UCI in all the notations and texts. + +###### 6.3.2.4.2.1 HARQ-ACK + +For HARQ-ACK transmission on PUSCH, the number of coded modulation symbols per layer for HARQ-ACK transmission, denoted as $N_{\text{symbols}}$ , is determined according to Clause 6.3.2.4.1.1, by setting the number of CRC bits $N_{\text{CRC}}$ . + +The input bit sequence to rate matching is $\mathbf{a}$ . + +Rate matching is performed according to Clause 5.4.3, by setting the rate matching output sequence length $N_{\text{output}}$ , where + +- $N_{\text{layers}}$ is the number of transmission layers of the PUSCH; +- $M$ is the modulation order of the PUSCH. + +The output bit sequence after rate matching is denoted as $\mathbf{b}$ . + +###### 6.3.2.4.2.2 CSI part 1 + +For CSI part 1 transmission on PUSCH, the number of coded modulation symbols per layer for CSI part 1 transmission, denoted as $N_{\text{symbols}}$ , is determined according to Clause 6.3.2.4.1.2, by setting the number of CRC bits $N_{\text{CRC}}$ . + +Rate matching is performed according to Clause 5.4.3, by setting the rate matching output sequence length $N_{\text{output}}$ , where + +- $N_{\text{layers}}$ is the number of transmission layers of the PUSCH; +- $M$ is the modulation order of the PUSCH. + +The output bit sequence after rate matching is denoted as $\mathbf{b}$ . + +###### 6.3.2.4.2.3 CSI part 2 + +For CSI part 2 transmission on PUSCH, the number of coded modulation symbols per layer for CSI part 2 transmission, denoted as $N_{\text{symbols}}$ , is determined according to Clause 6.3.2.4.1.3, by setting the number of CRC bits $N_{\text{CRC}}$ . + +Rate matching is performed according to Clause 5.4.3, by setting the rate matching output sequence length $N_{\text{output}}$ , where + +- $N_{\text{layers}}$ is the number of transmission layers of the PUSCH; +- $M$ is the modulation order of the PUSCH. + +The output bit sequence after rate matching is denoted as $\mathbf{b}$ . + +###### 6.3.2.4.2.4 CG-UCI + +For CG-UCI transmission on PUSCH, the number of coded modulation symbols per layer for CG-UCI transmission, denoted as $N_{\text{symbols}}$ , is determined according to Clause 6.3.2.4.1.4, by setting the number of CRC bits $N_{\text{CRC}}$ . + +The input bit sequence to rate matching is $\mathbf{a}$ . + +Rate matching is performed according to Clause 5.4.3, by setting the rate matching output sequence length + +$N_{\text{output}}$ , where + +- $N_{\text{layers}}$ is the number of transmission layers of the PUSCH; +- $M$ is the modulation order of the PUSCH. + +The output bit sequence after rate matching is denoted as $\mathbf{b}$ . + +###### 6.3.2.4.2.5 HARQ-ACK and CG-UCI + +For HARQ-ACK and CG-UCI transmission on PUSCH, the number of coded modulation symbols per layer for HARQ-ACK and CG-UCI transmission, denoted as $\tilde{O}_{ACK}$ , is determined according to Clause 6.3.2.4.1.5, by setting the number of CRC bits $\tilde{O}_{CRC}$ . + +The input bit sequence to rate matching is $\tilde{O}_{ACK}$ . + +Rate matching is performed according to Clause 5.4.3, by setting the rate matching output sequence length $\tilde{O}_{ACK}$ , where + +- $\tilde{O}_{ACK}$ is the number of transmission layers of the PUSCH; +- $\tilde{O}_{ACK}$ is the modulation order of the PUSCH. + +The output bit sequence after rate matching is denoted as $\tilde{O}_{ACK}$ . + +###### 6.3.2.4.2.6 UCI with different priority indexes + +In this clause, $\tilde{O}_{ACK}$ is equal to $\tilde{O}_{ACK}$ defined in [5, TS38.213] in case of PUSCH associated with priority index 1, and equal to $\tilde{O}_{ACK}$ defined in [5, TS38.213] in case of PUSCH associated with priority index 0. $\tilde{O}_{CSI}$ is equal to $\tilde{O}_{CSI}$ defined in [5, TS38.213] in case of PUSCH associated with priority index 0, and equal to $\tilde{O}_{CSI}$ defined in [5, TS38.213] in case of PUSCH associated with priority index 1. + +If *uci-MuxWithDiffPrio* is configured, and HARQ-ACK bits associated with priority index 0, and CSI part 1 if any are transmitted on a PUSCH associated with priority index 1: + +- If CSI part 1 is also transmitted on the PUSCH, + - Perform rate matching for CSI part 1 according to clause 6.3.2.4.2.2, by assuming the number of HARQ-ACK information bits to be transmitted on PUSCH in clause 6.3.2.4.2.2 is 0 bit. + - Perform rate matching for HARQ-ACK with priority index 0 according to clause 6.3.2.4.2.3, by taking HARQ-ACK with priority index 0 as CSI part 2 and replacing $\tilde{O}_{ACK}$ by $\tilde{O}_{ACK}$ , and assuming the number of HARQ-ACK information bits to be transmitted on PUSCH in clause 6.3.2.4.2.3 is 0 bit. +- Otherwise, perform rate matching for HARQ-ACK with priority index 0 according to clause 6.3.2.4.2.2, by taking HARQ-ACK with priority index 0 as CSI-part 1 and replacing $\tilde{O}_{ACK}$ by $\tilde{O}_{ACK}$ , and assuming the number of HARQ-ACK information bits to be transmitted on PUSCH in clause 6.3.2.4.2.2 is 0 bit. + +If *uci-MuxWithDiffPrio* is configured, and HARQ-ACK bits associated with priority index 1, and CSI if any are transmitted on a PUSCH associated with priority index 0: + +- Perform rate matching for HARQ-ACK with priority index 1 according to clause 6.3.2.4.2.1, by taking HARQ-ACK with priority index 1 as HARQ-ACK and replacing $\tilde{O}_{ACK}$ by $\tilde{O}_{ACK}$ . +- Perform rate matching for CSI part 1 according to clause 6.3.2.4.2.2, by taking HARQ-ACK with priority index 1 as HARQ-ACK, if CSI part 1 is also transmitted on the PUSCH. +- Perform rate matching for CSI part 2 according to clause 6.3.2.4.2.3, by taking HARQ-ACK with priority index 1 as HARQ-ACK, if CSI part 2 is also transmitted on the PUSCH. + +If *uci-MuxWithDiffPrio* is configured, and HARQ-ACK bits associated with priority index 0, HARQ-ACK bits associated with priority index 1 and/or CG-UCI associated with priority index 1, and CSI part 1 if any are transmitted on a PUSCH: + +- Perform rate matching for HARQ-ACK with priority index 1 according to clause 6.3.2.4.2.1, by taking HARQ-ACK with priority index 1 as HARQ-ACK and replacing $\tilde{O}_{ACK}$ by $\tilde{O}_{ACK}$ , if HARQ-ACK bits associated with priority index 1 are transmitted without CG-UCI associated with priority index 1. +- Perform rate matching for CG-UCI with priority index 1 according to clause 6.3.2.4.2.4, if CG-UCI associated with priority index 1 is transmitted without HARQ-ACK bits associated with priority index 1. +- Perform rate matching for CG-UCI with priority index 1 and HARQ-ACK with priority index 1 according to clause 6.3.2.4.2.5, if both CG-UCI associated with priority index 1 and HARQ-ACK bits associated with priority index 1 are transmitted, by taking HARQ-ACK with priority index 1 as HARQ-ACK and replacing $\tilde{O}_{ACK}$ by $\tilde{O}_{ACK}$ . +- If CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 1, + +- Perform rate matching for CSI part 1 according to clause 6.3.2.4.2.2, by taking HARQ-ACK with priority index 1 if any as HARQ-ACK, and taking CG-UCI associated with priority index 1 if any as CG-UCI. +- Perform rate matching for HARQ-ACK with priority index 0 according to clause 6.3.2.4.2.3, by taking HARQ-ACK with priority index 0 as CSI part 2 and replacing $\beta$ by $\beta$ , and taking HARQ-ACK with priority index 1 if any as HARQ-ACK, and taking CG-UCI associated with priority index 1 if any as CG-UCI. +- Otherwise, + - Perform rate matching for HARQ-ACK with priority index 0 according to clause 6.3.2.4.2.2, by taking HARQ-ACK with priority index 0 as CSI-part 1 and replacing $\beta$ by $\beta$ and taking HARQ-ACK with priority index 1 if any as HARQ-ACK, and taking CG-UCI associated with priority index 1 if any as CG-UCI. + - Perform rate matching for CSI part 1 according to clause 6.3.2.4.2.3, by taking CSI part 1 as CSI part 2 and replacing $\beta$ by $\beta$ , taking HARQ-ACK with priority index 0 as CSI-part 1 and taking HARQ-ACK with priority index 1 as HARQ-ACK, if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 0. + +If *uci-MuxWithDiffPrio* is configured, and CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 if any, HARQ-ACK bits associated with priority index 1, and CSI part 1 if any are transmitted on a PUSCH associated with priority index 0: + +- Perform rate matching for HARQ-ACK with priority index 1 according to clause 6.3.2.4.2.1, by taking HARQ-ACK with priority index 1 as HARQ-ACK and replacing $\beta$ by $\beta$ . +- Perform rate matching for CG-UCI associated with priority index 0 according to clause 6.3.2.4.2.2, if CG-UCI associated with priority index 0 is transmitted without HARQ-ACK bits associated with priority index 0, by taking CG-UCI associated with priority index 0 as CSI-part 1 and replacing $\beta$ by $\beta$ and taking HARQ-ACK with priority index 1 as HARQ-ACK. +- Perform rate matching for CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 according to clause 6.3.2.4.2.2, if both CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 are transmitted, by taking CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 as CSI-part 1 and replacing $\beta$ by $\beta$ and taking HARQ-ACK with priority index 1 as HARQ-ACK. +- Perform rate matching for CSI part 1 according to clause 6.3.2.4.2.3, by taking CSI part 1 as CSI part 2 and replacing $\beta$ by $\beta$ , taking CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 if any as CSI-part 1 and taking HARQ-ACK with priority index 1 as HARQ-ACK, if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 0. + +#### 6.3.2.5 Code block concatenation + +Code block concatenation is performed according to Clause 6.3.1.5, except that the values of $E_{\text{UCI}}$ and $C_{\text{UCI}}$ given in Clause 6.3.2.4.1. + +#### 6.3.2.6 Multiplexing of coded UCI bits to PUSCH + +The coded UCI bits are multiplexed onto PUSCH according to the procedures in Clause 6.2.7. + +#### 6.3.2.7 Multiplexing of coded UCI bits with different priority indexes to PUSCH + +If the higher layer parameter *nrof\_UTO\_UCI* is configured, the procedure in this clause 6.3.2.7 applies by replacing CG-UCI with UTO-UCI in all the notations and texts, when applicable. + +If *uci-MuxWithDiffPrio* is configured, and HARQ-ACK bits associated with priority index 0, and CSI part 1 if any are transmitted on a PUSCH associated with priority index 1, + +- If CSI part 1 is also transmitted on the PUSCH, the coded UCI bits are multiplexed onto PUSCH according to the procedures in Clause 6.2.7 by taking HARQ-ACK with priority index 0 as CSI part 2, and assuming the number of HARQ-ACK information in Clause 6.2.7 is 0 bit; +- Otherwise, the coded UCI bits are multiplexed onto PUSCH according to the procedures in Clause 6.2.7 by taking HARQ-ACK with priority index 0 as CSI-part 1, and assuming the number of HARQ-ACK information in Clause 6.2.7 is 0 bit. + +If *uci-MuxWithDiffPrio* is configured, and HARQ-ACK bits associated with priority index 1, and CSI if any are transmitted on a PUSCH associated with priority index 0, the coded UCI bits are multiplexed onto PUSCH according to the procedures in Clause 6.2.7 by taking HARQ-ACK with priority index 1 as HARQ-ACK. + +If *uci-MuxWithDiffPrio* is configured, and HARQ-ACK bits associated with priority index 0, HARQ-ACK bits associated with priority index 1 and/or CG-UCI associated with priority index 1, and CSI part 1 if any are transmitted on a PUSCH, + +- if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 1, the coded UCI bits are multiplexed onto PUSCH according to the procedures in Clause 6.2.7 by taking HARQ-ACK with priority index 1 as HARQ-ACK, and taking HARQ-ACK with priority index 0 as CSI part 2; +- otherwise, the coded UCI bits are multiplexed onto PUSCH according to the procedures in Clause 6.2.7 by taking HARQ-ACK with priority index 1 if any as HARQ-ACK, taking CG-UCI associated with priority index 1 if any as CG-UCI, taking HARQ-ACK with priority index 0 as CSI part 1, and taking CSI part 1 as CSI part 2 if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 0. + +If *uci-MuxWithDiffPrio* is configured, and CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 if any, HARQ-ACK bits associated with priority index 1, and CSI part 1 if any are transmitted on a PUSCH associated with priority index 0, the coded UCI bits are multiplexed onto PUSCH according to the procedures in Clause 6.2.7 by taking HARQ-ACK with priority index 1 as HARQ-ACK, taking CG-UCI associated with priority index 0 and HARQ-ACK bits associated with priority index 0 if any as CSI part 1, and taking CSI part 1 as CSI part 2 if CSI part 1 is also transmitted on the PUSCH and the PUSCH is associated with priority index 0. + +# 7 Downlink transport channels and control information + +## 7.1 Broadcast channel + +Data arrives to the coding unit in the form of a maximum of one transport block every 80ms. The following coding steps can be identified: + +- Payload generation +- Scrambling +- Transport block CRC attachment +- Channel coding +- Rate matching + +### 7.1.1 PBCH payload generation + +Denote the bits in a transport block delivered to layer 1 by $b$ , where $b$ is the payload size generated by higher layers. The lowest order information bit is mapped to the most significant bit of the transport block as defined in Clause 6.1.1 of [8, TS 38.321]. + +Generate the following additional timing related PBCH payload bits $b$ , where: + +- $b$ are the 4th, 3rd, 2nd, and 1st LSB of SFN, respectively; +- $b$ is the half frame bit ; +- if $b$ as defined in Clause 4.1 of [5, TS38.213], + - $b$ is the MSB of $b$ as defined in Clause 7.4.3.1 of [4, TS 38.211]. + - $b$ is reserved. + - $b$ is the MSB of candidate SS/PBCH block index. +- else if $b$ as defined in Clause 4.1 of [5, TS38.213], + - $b$ is the MSB of $b$ as defined in Clause 7.4.3.1 of [4, TS 38.211]. + - $b$ , $b$ are the 5th and 4th bits of the candidate SS/PBCH block index, respectively. +- else if $b$ as defined in Clause 4.1 of [5, TS38.213], + +$b_{6,5,4}$ are the 6th, 5th, and 4th bits of the candidate SS/PBCH block index, respectively. + +- else + - $b_{15}$ is the MSB of $n_{SFN}$ as defined in Clause 7.4.3.1 of [4, TS 38.211]. + - $b_{14,13,12}$ are reserved. +- end if + +Let $b_{11,10,9,8}$ ; ; ; ; + +for $i$ to $N_{SSB}$ + +if $b_{11,10,9,8}$ is an SFN bit + +; + +elseif $b_{11,10,9,8}$ is the half radio frame bit + +elseif + +; + +else + +; + +end if + +end for + +where $N_{SSB}$ is the number of candidate SS/PBCH blocks in a half frame according to Clause 4.1 of [5, TS38.213], and the value of $b_{11,10,9,8}$ is given by Table 7.1.1-1. + +**Table 7.1.1-1: Value of PBCH payload interleaver pattern** + +| | | | | | | | | | | | | | | | | +|---|----|---|----|----|----|----|---|----|----|----|----|----|----|----|----| +| 0 | 16 | 4 | 8 | 8 | 24 | 12 | 3 | 16 | 9 | 20 | 14 | 24 | 21 | 28 | 27 | +| 1 | 23 | 5 | 30 | 9 | 7 | 13 | 2 | 17 | 11 | 21 | 15 | 25 | 22 | 29 | 28 | +| 2 | 18 | 6 | 10 | 10 | 0 | 14 | 1 | 18 | 12 | 22 | 19 | 26 | 25 | 30 | 29 | +| 3 | 17 | 7 | 6 | 11 | 5 | 15 | 4 | 19 | 13 | 23 | 20 | 27 | 26 | 31 | 31 | + +### 7.1.2 Scrambling + +For PBCH transmission in a frame, the bit sequence $b_{0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15}$ is scrambled into a bit sequence $\tilde{b}_{0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15}$ , where $\tilde{b}_i$ for $i = 0, 1, \dots, 15$ is generated according to the following: + +; + +; + +while + +if $b_i$ corresponds to any one of the bits belonging to the candidate SS/PBCH block index, the half frame index, and 2nd and 3rd least significant bits of the system frame number + +; + +else + +; + +; + +end if + +; + +end while + +The scrambling sequence is given by Clause 5.2.1 of [4, TS38.211] and initialized with at the start of each SFN satisfying ; for or , for , for , and for , where is the number of candidate SS/PBCH blocks in a half frame according to Clause 4.1 of [5, TS38.213]; and is determined according to Table 7.1.2-1 using the 3rd and 2nd LSB of the SFN in which the PBCH is transmitted. + +**Table 7.1.2-1: Value of for PBCH scrambling** + +| (3rd LSB of SFN, 2nd LSB of SFN) | Value of | +|---------------------------------------------------------------|-----------------| +| (0, 0) | 0 | +| (0, 1) | 1 | +| (1, 0) | 2 | +| (1, 1) | 3 | + +### 7.1.3 Transport block CRC attachment + +Error detection is provided on BCH transport blocks through a Cyclic Redundancy Check (CRC). + +The entire transport block is used to calculate the CRC parity bits. The input bit sequence is denoted by , and the parity bits by, where is the payload size and is the number of parity bits. + +The parity bits are computed and attached to the BCH transport block according to Clause 5.1 by setting to 24 bits and using the generator polynomial , resulting in the sequence, where . + +The bit sequence is the input bit sequence to the channel encoder, where for and . + +### 7.1.4 Channel coding + +Information bits are delivered to the channel coding block. They are denoted by , where is the number of bits, and they are encoded via Polar coding according to Clause 5.3.1, by setting , , and . + +After encoding the bits are denoted by , where is the number of coded bits. + +### 7.1.5 Rate matching + +The input bit sequence to rate matching is . + +The rate matching output sequence length . + +Rate matching is performed according to Clause 5.4.1 by setting . + +The output bit sequence after rate matching is denoted as . + +## 7.2 Downlink shared channel and paging channel + +### 7.2.1 Transport block CRC attachment + +Error detection is provided on each transport block through a Cyclic Redundancy Check (CRC). + +The entire transport block is used to calculate the CRC parity bits. Denote the bits in a transport block delivered to layer 1 by, and the parity bits by, where is the payload size and is the number of parity bits. The lowest order information bit is mapped to the most significant bit of the transport block as defined in Clause 6.1.1 of [TS38.321]. + +The parity bits are computed and attached to the DL-SCH transport block according to Clause 5.1, by setting to 24 bits and using the generator polynomial if ; and by setting to 16 bits and using the generator polynomial otherwise. + +The bits after CRC attachment are denoted by , where . + +### 7.2.2 LDPC base graph selection + +For initial transmission of a transport block with coding rate indicated by the MCS index according to Clause 5.1.3.1 in [6, TS 38.214] and subsequent re-transmission of the same transport block, each code block of the transport block is encoded with either LDPC base graph 1 or 2 according to the following: + +- if $K_{cb} \geq 296$ and $K_{cb} \leq 8448$ , LDPC base graph 2 is used; +- otherwise, LDPC base graph 1 is used, + +where $K_{cb}$ is the payload size in Clause 7.2.1. + +### 7.2.3 Code block segmentation and code block CRC attachment + +The bits input to the code block segmentation are denoted by $A$ where $A$ is the number of bits in the transport block (including CRC). + +Code block segmentation and code block CRC attachment are performed according to Clause 5.2.2. + +The bits after code block segmentation are denoted by $B_{cb}$ , where $cb$ is the code block number and $B_{cb}$ is the number of bits for code block number $cb$ according to Clause 5.2.2. + +### 7.2.4 Channel coding + +Code blocks are delivered to the channel coding block. The bits in a code block are denoted by $B_{cb}$ , where $cb$ is the code block number, and $B_{cb}$ is the number of bits in code block number $cb$ . The total number of code blocks is denoted by $C$ and each code block is individually LDPC encoded according to Clause 5.3.2. + +After encoding the bits are denoted by $C_{cb}$ , where the values of $C_{cb}$ is given in Clause 5.3.2. + +### 7.2.5 Rate matching + +Coded bits for each code block, denoted as $C_{cb}$ , are delivered to the rate match block, where $cb$ is the code block number, and $C_{cb}$ is the number of encoded bits in code block number $cb$ . The total number of code blocks is denoted by $C$ and each code block is individually rate matched according to Clause 5.4.2 by setting $K_{cb}$ . + +After rate matching, the bits are denoted by $D_{cb}$ , where $D_{cb}$ is the number of rate matched bits for code block number $cb$ . + +### 7.2.6 Code block concatenation + +The input bit sequence for the code block concatenation block are the sequences $D_{cb}$ , for $cb$ and where $D_{cb}$ is the number of rate matched bits for the $cb$ -th code block. + +Code block concatenation is performed according to Clause 5.5. + +The bits after code block concatenation are denoted by $E$ , where $E$ is the total number of coded bits for transmission. + +## 7.3 Downlink control information + +A DCI transports downlink control information for one or more cells with one RNTI. + +The following coding steps can be identified: + +- Information element multiplexing +- CRC attachment +- Channel coding +- Rate matching + +### 7.3.1 DCI formats + +The DCI formats defined in table 7.3.1-1 are supported. + +**Table 7.3.1-1: DCI formats** + +| DCI format | Usage | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0_0 | Scheduling of PUSCH in one cell | +| 0_1 | Scheduling of one or multiple PUSCH in one cell, or indicating downlink feedback information for configured grant PUSCH (CG-DFI) | +| 0_2 | Scheduling of PUSCH in one cell | +| 0_3 | Scheduling of one PUSCH in one cell, or multiple PUSCHs in multiple cells with one PUSCH per cell | +| 1_0 | Scheduling of PDSCH in one cell | +| 1_1 | Scheduling of one or multiple PDSCH in one cell, and/or triggering one shot HARQ-ACK codebook feedback | +| 1_2 | Scheduling of PDSCH in one cell | +| 1_3 | Scheduling of one PDSCH in one cell, or multiple PDSCHs in multiple cells with one PDSCH per cell | +| 2_0 | Notifying a group of UEs of the slot format, available RB sets, COT duration and search space set group switching | +| 2_1 | Notifying a group of UEs of the PRB(s) and OFDM symbol(s) where UE may assume no transmission is intended for the UE | +| 2_2 | Transmission of TPC commands for PUCCH and PUSCH | +| 2_3 | Transmission of a group of TPC commands for SRS transmissions by one or more UEs | +| 2_4 | Notifying a group of UEs of the PRB(s) and OFDM symbol(s) where UE cancels the corresponding UL transmission from the UE | +| 2_5 | Notifying the availability of soft resources as defined in Clause 9.3.1 of [10, TS 38.473] | +| 2_6 | Notifying the power saving information outside DRX Active Time for one or more UEs | +| 2_7 | Notifying paging early indication and TRS availability indication for one or more UEs | +| 2_8 | Notifying the aperiodic beam indication and associated time resources | +| 2_9 | Activating or de-activating the cell DTX and/or DRX configuration of one or multiple serving cells for one or more UEs, and/or for providing NES-mode indication of the primary cell for one or more UEs | +| 3_0 | Scheduling of NR sidelink in one cell | +| 3_1 | Scheduling of LTE sidelink in one cell | +| 3_2 | Scheduling of NR SL PRS in one cell | +| 4_0 | Scheduling of PDSCH with CRC scrambled by MCCH-RNTI/G-RNTI for broadcast or by multicast-MCCH-RNTI for multicast in RRC_INACTIVE state | +| 4_1 | Scheduling of PDSCH with CRC scrambled by G-RNTI/G-CS-RNTI for multicast in RRC_CONNECTED state or by G-RNTI for multicast in RRC_INACTIVE state | +| 4_2 | Scheduling of PDSCH with CRC scrambled by G-RNTI/G-CS-RNTI for multicast in RRC_CONNECTED state | + +The fields defined in the DCI formats below are mapped to the information bits as follows. + +Each field is mapped in the order in which it appears in the description, including the zero-padding bit(s), if any, with the first field mapped to the lowest order information bit and each successive field mapped to higher order information bits. The most significant bit of each field is mapped to the lowest order information bit for that field, e.g. the most significant bit of the first field is mapped to . + +If the number of information bits in a DCI format is less than 12 bits, zeros shall be appended to the DCI format until the payload size equals 12. + +The size of each DCI format except for DCI format 0\_3/1\_3 is determined by the configuration of the corresponding active bandwidth part of the scheduled cell and shall be adjusted as described in clause 7.3.1.0 if necessary. + +For a cell set configured by higher layer parameter *MC-DCI-SetofCellsToAddModList*, the size of DCI format 0\_3/1\_3 is determined as follows and shall be adjusted as described in Clause 7.3.1.0 if necessary: + +- If *ScheduledCellCombo-ListDCI-0-3* for the cell set is configured, the size of DCI format 0\_3 is determined by the configuration of the corresponding active bandwidth part(s) of the scheduled cells in the entry which results in the largest size among the entries in the higher layer parameter *ScheduledCellCombo-ListDCI-0-3*; Otherwise, the size of DCI format 0\_3 is determined by the configuration of the corresponding active bandwidth part(s) of the cells configured by higher layer parameter *ScheduledCell-ListDCI-0-3* for the cell set. + +- If *ScheduledCellCombo-ListDCI-1-3* for the cell set is configured, the size of DCI format 1\_3 is determined by the configuration of the corresponding active bandwidth part(s) of the scheduled cells in the entry which results in the largest size among the entries in the higher layer parameter *ScheduledCellCombo-ListDCI-1-3*; Otherwise, the size of DCI format 1\_3 is determined by the configuration of the corresponding active bandwidth part(s) of the cells configured by higher layer parameter *ScheduledCell-ListDCI-1-3* for the cell set. + +If a UE is configured with *pdsch-HARQ-ACK-CodebookList-r16*, *pdsch-HARQ-ACK-Codebook* is replaced by the relevant entry in *pdsch-HARQ-ACK-CodebookList-r16* in this clause. + +If a UE is configured with *pdsch-HARQ-ACK-CodebookListMulticast-r17*, *pdsch-HARQ-ACK-Codebook* is replaced by the relevant entry in *pdsch-HARQ-ACK-CodebookListMulticast-r17* in this clause. + +For a cell detected in cell search procedure with synchronization raster defined in Table 5.4.3.1-2 or Table 5.4.3.1-3 of [13, TS 38.101-1], the size of CORESET 0 for the cell in this clause refers to the size of punctured CORESET 0 as defined in clause 7.3.2.2 of [4, TS 38.211] if any. + +#### 7.3.1.0 DCI size alignment + +If necessary, padding or truncation shall be applied to the DCI formats according to the following steps executed in the order below: + +Step 0: + +- Determine DCI format 0\_0 monitored in a common search space according to clause 7.3.1.1.1 where *W* is the size of the initial UL bandwidth part. +- Determine DCI format 1\_0 monitored in a common search space according to clause 7.3.1.2.1 where *W* is given by + - the size of CORESET 0 if CORESET 0 is configured for the cell; and + - the size of initial DL bandwidth part if CORESET 0 is not configured for the cell. +- If DCI format 0\_0 is monitored in common search space and if the number of information bits in the DCI format 0\_0 prior to padding is less than the payload size of the DCI format 1\_0 monitored in common search space for scheduling the same serving cell, a number of zero padding bits are generated for the DCI format 0\_0 until the payload size equals that of the DCI format 1\_0. +- If DCI format 0\_0 is monitored in common search space and if the number of information bits in the DCI format 0\_0 prior to truncation is larger than the payload size of the DCI format 1\_0 monitored in common search space for scheduling the same serving cell, the bitwidth of the frequency domain resource assignment field in the DCI format 0\_0 is reduced by truncating the first few most significant bits such that the size of DCI format 0\_0 equals the size of the DCI format 1\_0. + +Step 1: + +- Determine DCI format 0\_0 monitored in a UE-specific search space according to clause 7.3.1.1.1 where *W* is the size of the active UL bandwidth part. +- Determine DCI format 1\_0 monitored in a UE-specific search space according to clause 7.3.1.2.1 where *W* is the size of the active DL bandwidth part. +- For a UE configured with *supplementaryUplink* in *ServingCellConfig* in a cell, if PUSCH is configured to be transmitted on both the SUL and the non-SUL of the cell and if the number of information bits in DCI format 0\_0 in UE-specific search space for the SUL is not equal to the number of information bits in DCI format 0\_0 in UE-specific search space for the non-SUL, a number of zero padding bits are generated for the smaller DCI format 0\_0 until the payload size equals that of the larger DCI format 0\_0. +- If DCI format 0\_0 is monitored in UE-specific search space and if the number of information bits in the DCI format 0\_0 prior to padding is less than the payload size of the DCI format 1\_0 monitored in UE-specific search space for scheduling the same serving cell, a number of zero padding bits are generated for the DCI format 0\_0 until the payload size equals that of the DCI format 1\_0. +- If DCI format 1\_0 is monitored in UE-specific search space and if the number of information bits in the DCI format 1\_0 prior to padding is less than the payload size of the DCI format 0\_0 monitored in UE-specific search space for scheduling the same serving cell, zeros shall be appended to the DCI format 1\_0 until the payload size equals that of the DCI format 0\_0 + +Step 2: + +- Determine DCI format 0\_1 monitored in a UE-specific search space according to clause 7.3.1.1.2. +- Determine DCI format 1\_1 monitored in a UE-specific search space according to clause 7.3.1.2.2. +- For a UE configured with *supplementaryUplink* in *ServingCellConfig* in a cell, if PUSCH is configured to be transmitted on both the SUL and the non-SUL of the cell and if the number of information bits in format 0\_1 for the SUL is not equal to the number of information bits in format 0\_1 for the non-SUL, zeros shall be appended to smaller format 0\_1 until the payload size equals that of the larger format 0\_1. +- If the size of DCI format 0\_1 monitored in a UE-specific search space equals that of a DCI format 0\_0/1\_0 monitored in another UE-specific search space, one bit of zero padding shall be appended to DCI format 0\_1. +- If the size of DCI format 1\_1 monitored in a UE-specific search space equals that of a DCI format 0\_0/1\_0 monitored in another UE-specific search space, one bit of zero padding shall be appended to DCI format 1\_1. + +##### Step 2A: + +- Determine DCI format 0\_2 monitored in a UE-specific search space according to clause 7.3.1.1.3. +- Determine DCI format 1\_2 monitored in a UE-specific search space according to clause 7.3.1.2.3. +- For a UE configured with *supplementaryUplink* in *ServingCellConfig* in a cell, if PUSCH is configured to be transmitted on both the SUL and the non-SUL of the cell and if the number of information bits in format 0\_2 for the SUL is not equal to the number of information bits in format 0\_2 for the non-SUL, zeros shall be appended to smaller format 0\_2 until the payload size equals that of the larger format 0\_2. + +##### Step 2B: + +- If the cell is the serving cell for counting the size of one or both DCI format 0\_3 and DCI format 1\_3 as defined in Clause 10.1 of [5, TS38.213], + - Determine DCI format 0\_3 monitored in a UE-specific search space according to clause 7.3.1.1.4. + - Determine DCI format 1\_3 monitored in a UE-specific search space according to clause 7.3.1.2.4. + +##### Step 3: + +- If both of the following conditions are fulfilled the size alignment procedure is complete + - the total number of different DCI sizes configured to monitor is no more than 4 for the cell + - the total number of different DCI sizes with C-RNTI configured to monitor is no more than 3 for the cell + +##### Step 4: + +- Otherwise + +##### Step 4A: + +- Remove the padding bit (if any) introduced in step 2 above. +- Determine DCI format 1\_0 monitored in a UE-specific search space according to clause 7.3.1.2.1 where is given by + - the size of CORESET 0 if CORESET 0 is configured for the cell; and + - the size of initial DL bandwidth part if CORESET 0 is not configured for the cell. +- Determine DCI format 0\_0 monitored in a UE-specific search space according to clause 7.3.1.1.1 where is the size of the initial UL bandwidth part. +- If the number of information bits in the DCI format 0\_0 monitored in a UE-specific search space prior to padding is less than the payload size of the DCI format 1\_0 monitored in UE-specific search space for scheduling the same serving cell, a number of zero padding bits are generated for the DCI format 0\_0 monitored in a UE-specific search space until the payload size equals that of the DCI format 1\_0 monitored in a UE-specific search space. +- If the number of information bits in the DCI format 0\_0 monitored in a UE-specific search space prior to truncation is larger than the payload size of the DCI format 1\_0 monitored in UE-specific search space for scheduling the same serving cell, the bitwidth of the frequency domain resource assignment field in the DCI format 0\_0 is reduced by truncating the first few most significant bits such that the size of DCI format 0\_0 monitored in a UE-specific search space equals the size of the DCI format 1\_0 monitored in a UE-specific search space. + +##### Step 4B: + +- If the total number of different DCI sizes configured to monitor is more than 4 for the cell after applying the above steps, or if the total number of different DCI sizes with C-RNTI configured to monitor is more than 3 for the cell after applying the above steps + +- If the number of information bits in the DCI format 0\_2 prior to padding is less than the payload size of the DCI format 1\_2 for scheduling the same serving cell, a number of zero padding bits are generated for the DCI format 0\_2 until the payload size equals that of the DCI format 1\_2. +- If the number of information bits in the DCI format 1\_2 prior to padding is less than the payload size of the DCI format 0\_2 for scheduling the same serving cell, zeros shall be appended to the DCI format 1\_2 until the payload size equals that of the DCI format 0\_2. + +Step 4C: + +- If the total number of different DCI sizes configured to monitor is more than 4 for the cell after applying the above steps, or if the total number of different DCI sizes with C-RNTI configured to monitor is more than 3 for the cell after applying the above steps + - If the number of information bits in the DCI format 0\_1 prior to padding is less than the payload size of the DCI format 1\_1 for scheduling the same serving cell, a number of zero padding bits are generated for the DCI format 0\_1 until the payload size equals that of the DCI format 1\_1. + - If the number of information bits in the DCI format 1\_1 prior to padding is less than the payload size of the DCI format 0\_1 for scheduling the same serving cell, zeros shall be appended to the DCI format 1\_1 until the payload size equals that of the DCI format 0\_1. + +Step 4D: + +- If the total number of different DCI sizes configured to monitor is more than 4 for the cell after applying the above steps and the cell is the serving cell for counting the size of one or both DCI format 0\_3 and DCI format 1\_3 as defined in Clause 10.1 of [5, TS38.213], or if the total number of different DCI sizes with C-RNTI configured to monitor is more than 3 for the cell after applying the above steps and the cell is the serving cell for counting the size of one or both DCI format 0\_3 and DCI format 1\_3 as defined in Clause 10.1 of [5, TS38.213] + - If the number of information bits in the DCI format 0\_3 prior to padding is less than the payload size of the DCI format 1\_3 for scheduling the same cell set, a number of zero padding bits are generated for the DCI format 0\_3 until the payload size equals that of the DCI format 1\_3. + - If the number of information bits in the DCI format 1\_3 prior to padding is less than the payload size of the DCI format 0\_3 for scheduling the same cell set, zeros shall be appended to the DCI format 1\_3 until the payload size equals that of the DCI format 0\_3. + +The UE is not expected to handle a configuration that, after applying the above steps, results in + +- the total number of different DCI sizes configured to monitor is more than 4 for the cell; or +- the total number of different DCI sizes with C-RNTI configured to monitor is more than 3 for the cell; or +- the size of DCI format 0\_0 in a UE-specific search space is equal to DCI format 0\_1 in another UE-specific search space; or +- the size of DCI format 1\_0 in a UE-specific search space is equal to DCI format 1\_1 in another UE-specific search space; or +- the size of DCI format 0\_0 in a UE-specific search space is equal to DCI format 0\_2 in another UE-specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 0\_0 and 0\_2 are mapped to the same resource; or +- the size of DCI format 1\_0 in a UE-specific search space is equal to DCI format 1\_2 in another UE-specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 1\_0 and 1\_2 are mapped to the same resource; or +- the size of DCI format 0\_1 in a UE-specific search space is equal to DCI format 0\_2 in the same or another UE-specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 0\_1 and 0\_2 are mapped to the same resource; or +- the size of DCI format 1\_1 in a UE-specific search space is equal to DCI format 1\_2 in the same or another UE-specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 1\_1 and 1\_2 are mapped to the same resource; or +- the size of DCI format 0\_0 in a UE-specific search space is equal to DCI format 0\_3 in another UE-specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 0\_0 and 0\_3 are mapped to the same resource; or +- the size of DCI format 1\_0 in a UE-specific search space is equal to DCI format 1\_3 in another UE-specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 1\_0 and 1\_3 are mapped to the same resource; or + +- the size of DCI format 0\_1 in a UE-specific search space is equal to DCI format 0\_3 in another UE-specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 0\_1 and 0\_3 are mapped to the same resource; or +- the size of DCI format 1\_1 in a UE-specific search space is equal to DCI format 1\_3 in another UE-specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 1\_1 and 1\_3 are mapped to the same resource. +- the size of DCI format 0\_2 in a UE-specific search space is equal to DCI format 0\_3 in another UE-specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 0\_2 and 0\_3 are mapped to the same resource; or +- the size of DCI format 1\_2 in a UE-specific search space is equal to DCI format 1\_3 in another UE-specific search space when at least one pair of the corresponding PDCCH candidates of DCI formats 1\_2 and 1\_3 are mapped to the same resource. + +##### 7.3.1.0.1 DCI size alignment for DCI formats for scheduling of sidelink + +If DCI format 3\_0, and/or DCI format 3\_1, and/or DCI format 3\_2 is monitored on a cell, DCI size alignment for DCI format 3\_0, DCI format 3\_1, and DCI format 3\_2 is performed as described in this clause after performing the DCI size alignment described in Clause 7.3.1.0. The size(s) of the DCI formats configured to monitor for a cell in this clause refers to that after performing the DCI size alignment described in Clause 7.3.1.0. + +If DCI format 3\_0, and/or DCI format 3\_1, and/or DCI format 3\_2 is monitored on a cell and the total number of DCI sizes of the DCI formats configured to monitor for the cell and DCI format 3\_0, and/or DCI format 3\_1, and/or DCI format 3\_2 is more than 4, zeros shall be appended to DCI format 3\_0 if configured, to DCI format 3\_1 if configured, and to DCI format 3\_2 if configured, until the payload size of DCI format 3\_0, DCI format 3\_1, and DCI format 3\_2 equals that of the smallest DCI format configured to monitor for the cell that is larger than DCI format 3\_0, DCI format 3\_1, and DCI format 3\_2. + +The UE is not expected to handle a configuration that results in: + +- the total number of different DCI sizes configured to monitor for the cell and DCI format 3\_0, and/or DCI format 3\_1, and/or DCI format 3\_2 is more than 4; and +- the payload size of DCI format 3\_0, and/or DCI format 3\_1, and/or DCI format 3\_2 is larger than the payload size of all other DCI formats configured to monitor for the cell. + +#### 7.3.1.1 DCI formats for scheduling of PUSCH + +##### 7.3.1.1.1 Format 0\_0 + +DCI format 0\_0 is used for the scheduling of PUSCH in one cell. + +The following information is transmitted by means of the DCI format 0\_0 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI: + +- Identifier for DCI formats - 1 bit + - The value of this bit field is always set to 0, indicating an UL DCI format +- Frequency domain resource assignment - number of bits determined by the following: + - bits if neither of the higher layer parameters *useInterlacePUCCH-PUSCH* in *BWP-UplinkCommon* and *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated* is configured, where is defined in clause 7.3.1.0 + - For PUSCH hopping with resource allocation type 1: + - MSB bits are used to indicate the frequency offset according to Clause 6.3 of [6, TS 38.214], where if the higher layer parameter *frequencyHoppingOffsetLists* contains two offset values and if the higher layer parameter *frequencyHoppingOffsetLists* contains four offset values + - bits provide the frequency domain resource allocation according to Clause 6.1.2.2.2 of [6, TS 38.214] + - For non-PUSCH hopping with resource allocation type 1: + - bits provide the frequency domain resource allocation according to Clause 6.1.2.2.2 of [6, TS 38.214] + - If any of the higher layer parameters *useInterlacePUCCH-PUSCH* in *BWP-UplinkCommon* and *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated* is configured + +- 5+Y bits provide the frequency domain resource allocation according to Clause 6.1.2.2.3 of [6, TS 38.214] if the subcarrier spacing for the active UL bandwidth part is 30 kHz. +- 6+Y bits provide the frequency domain resource allocation according to Clause 6.1.2.2.3 of [6, TS 38.214] if the subcarrier spacing for the active UL bandwidth part is 15 kHz. + +If the DCI format 0\_0 is monitored in a UE-specific search space, the value of Y is determined by where is the number of RB sets contained in the active UL BWP as defined in clause 7 of [6, TS38.214]. If the DCI 0\_0 is monitored in a common search space Y = 0. + +- Time domain resource assignment - 4 bits as defined in Clause 6.1.2.1 of [6, TS 38.214] +- Frequency hopping flag - 1 bit according to Table 7.3.1.1.1-3, as defined in Clause 6.3 of [6, TS 38.214] +- Modulation and coding scheme - 5 bits as defined in Clause 6.1.4.1 of [6, TS 38.214] +- New data indicator - 1 bit +- Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2 +- HARQ process number - 4 bits +- TPC command for scheduled PUSCH - 2 bits as defined in Clause 7.1.1 of [5, TS 38.213] +- ChannelAccess-CPext - 2 bits indicating combinations of channel access type and CP extension as defined in Table 7.3.1.1.1-4, or Table 7.3.1.1.1-4A if *channelAccessMode-r16* = "semiStatic" is provided, for operation in a cell with shared spectrum channel access in frequency range 1; 2 bits indicating channel access type as defined in Table 7.3.1.1.1-4B if *ChannelAccessMode2-r17* is provided for operation in a cell in frequency range 2-2; 0 bit otherwise. +- Padding bits, if required. +- UL/SUL indicator - 1 bit for UEs configured with *supplementaryUplink* in *ServingCellConfig* in the cell as defined in Table 7.3.1.1.1-1 and the number of bits for DCI format 1\_0 before padding is larger than the number of bits for DCI format 0\_0 before padding; 0 bit otherwise. The UL/SUL indicator, if present, locates in the last bit position of DCI format 0\_0, after the padding bit(s). + - If the UL/SUL indicator is present in DCI format 0\_0 and the higher layer parameter *pusch-Config* is not configured on both UL and SUL the UE ignores the UL/SUL indicator field in DCI format 0\_0, and the corresponding PUSCH scheduled by the DCI format 0\_0 is for the UL or SUL for which high layer parameter *pucch-Config* is configured; + - If the UL/SUL indicator is not present in DCI format 0\_0 and *pucch-Config* is configured, the corresponding PUSCH scheduled by the DCI format 0\_0 is for the UL or SUL for which high layer parameter *pucch-Config* is configured. + - If the UL/SUL indicator is not present in DCI format 0\_0 and *pucch-Config* is not configured, the corresponding PUSCH scheduled by the DCI format 0\_0 is for the uplink on which the latest PRACH is transmitted. + +The following information is transmitted by means of the DCI format 0\_0 with CRC scrambled by TC-RNTI: + +- Identifier for DCI formats - 1 bit + - The value of this bit field is always set to 0, indicating an UL DCI format +- Frequency domain resource assignment - number of bits determined by the following: + - bits if the higher layer parameter *useInterlacePUCCH-PUSCH* in *BWP-UplinkCommon* is not configured, where + - is the size of the initial UL bandwidth part. + - For PUSCH hopping with resource allocation type 1: + - MSB bits are used to indicate the frequency offset according to Table 8.3-1 in Clause 8.3 of [5, TS 38.213], where if and otherwise + - bits provide the frequency domain resource allocation according to Clause 6.1.2.2.2 of [6, TS 38.214] + - For non-PUSCH hopping with resource allocation type 1: + - bits provide the frequency domain resource allocation according to Clause 6.1.2.2.2 of [6, TS 38.214] + - If the higher layer parameter *useInterlacePUCCH-PUSCH* in *BWP-UplinkCommon* is configured + - 5 bits provide the frequency domain resource allocation according to Clause 6.1.2.2.3 of [6, TS 38.214] if the subcarrier spacing for the active UL bandwidth part is 30 kHz + - 6 bits provide the frequency domain resource allocation according to Clause 6.1.2.2.3 of [6, TS 38.214] if the subcarrier spacing for the active UL bandwidth part is 15 kHz +- Time domain resource assignment - 4 bits as defined in Clause 6.1.2.1 of [6, TS 38.214] + +- Frequency hopping flag - 1 bit according to Table 7.3.1.1.1-3, as defined in Clause 6.3 of [6, TS 38.214] +- Modulation and coding scheme - 5 bits + - If the UE requests repetition of PUSCH scheduled by RAR UL grant [8, TS 38.321], 5 bits as defined in Clause 6.1.2.1 and Clause 6.1.4.1 of [6, TS 38.214]; + - otherwise 5 bits as defined in Clause 6.1.4.1 of [6, TS 38.214]. +- New data indicator - 1 bit, reserved +- Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2 +- HARQ process number - 4 bits, reserved +- TPC command for scheduled PUSCH - 2 bits as defined in Clause 7.1.1 of [5, TS 38.213] +- ChannelAccess-CPext - 2 bits indicating combinations of channel access type and CP extension as defined in Table 7.3.1.1.1-4, or Table 7.3.1.1.1-4A if *channelAccessMode-r16* = "semiStatic" is provided, for operation in a cell with shared spectrum channel access in frequency range 1; 2 bits indicating channel access type as defined in Table 7.3.1.1.1-4B if *ChannelAccessMode2-r17* is provided for operation in a cell in frequency range 2-2; 0 bit otherwise +- Padding bits, if required. +- UL/SUL indicator - 1 bit if the cell has two ULs and the number of bits for DCI format 1\_0 before padding is larger than the number of bits for DCI format 0\_0 before padding; 0 bit otherwise. The UL/SUL indicator, if present, locates in the last bit position of DCI format 0\_0, after the padding bit(s). +- If 1 bit, reserved, and the corresponding PUSCH is always on the same UL carrier as the previous transmission of the same TB + +**Table 7.3.1.1.1-1: UL/SUL indicator** + +| Value of UL/SUL indicator | Uplink | +|---------------------------|------------------------------| +| 0 | The non-supplementary uplink | +| 1 | The supplementary uplink | + +**Table 7.3.1.1.1-2: Redundancy version** + +| Value of the Redundancy version field | Value of to be applied | +|---------------------------------------|------------------------| +| 00 | 0 | +| 01 | 1 | +| 10 | 2 | +| 11 | 3 | + +**Table 7.3.1.1.1-3: Frequency hopping indication** + +| Bit field mapped to index | PUSCH frequency hopping | +|---------------------------|-------------------------| +| 0 | Disabled | +| 1 | Enabled | + +**Table 7.3.1.1.1-4: Channel access type & CP extension for DCI format 0\_0 and DCI format 1\_0 for frequency range 1** + +| Bit field mapped to index | Channel Access Type | The CP extension T_"ext" index defined in Clause 5.3.1 of [4, TS 38.211] | +|---------------------------|----------------------------------------------------------------------|--------------------------------------------------------------------------| +| 0 | Type2C-ULChannelAccess defined in clause 4.2.1.2.3 in TS 37.213 [14] | 2 | +| 1 | Type2A-ULChannelAccess defined in clause 4.2.1.2.1 in TS 37.213 [14] | 3 | +| 2 | Type2A-ULChannelAccess defined in clause 4.2.1.2.1 in TS 37.213 [14] | 1 | +| 3 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 0 | + +**Table 7.3.1.1.1-4A: Channel access type & CP extension if *channelAccessMode-r16* = "semiStatic" is provided** + +| Bit field mapped to index | Channel Access Type | The CP extension T "ext" index defined in Clause 5.3.1 of [4, TS 38.211] | Initiator of the channel occupancy associated with the UL transmission as described in Clause 4.3.1 in TS 37.213 | +|---------------------------|---------------------------------------------------------------------------|-------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| +| 0 | No sensing as defined in Clause 4.3 in TS 37.213 [14] | 0 | gNB | +| 1 | No sensing as defined in Clause 4.3 in TS 37.213 [14] | 2 | gNB | +| 2 | Sensing within a 25us interval as defined in Clause 4.3 in TS 37.213 [14] | 0 | gNB | +| 3 | Sensing as defined in Clause 4.3.1.2 in TS 37.213 [14] | 0 | UE | + +NOTE: Row index 3 is only applicable if *semiStaticChannelAccessConfigUE* is provided. Otherwise, the row is reserved. + +**Table 7.3.1.1.1-4B: Channel access type for DCI format 0\_0 and DCI format 1\_0 for frequency range 2-2** + +| Bit field mapped to index | Channel Access Type | +|---------------------------|-----------------------------------------------------------------| +| 0 | Type 1 channel access defined in clause 4.4.1 of TS 37.213 [14] | +| 1 | Type 2 channel access defined in clause 4.4.2 of TS 37.213 [14] | +| 2 | Type 3 channel access defined in clause 4.4.3 of TS 37.213 [14] | +| 3 | Reserved | + +##### 7.3.1.1.2 Format 0\_1 + +DCI format 0\_1 is used for the scheduling of one or multiple PUSCH in one cell, or indicating CG downlink feedback information (CG-DFI) to a UE. + +The following information is transmitted by means of the DCI format 0\_1 with CRC scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI: + +- Identifier for DCI formats - 1 bit + - The value of this bit field is always set to 0, indicating an UL DCI format +- Carrier indicator - 0 or 3 bits, as defined in Clause 10.1 of [5, TS38.213]. This field is reserved when this format is carried by PDCCH on the primary cell and the UE is configured for scheduling on the primary cell from an SCell, with the same number of bits as that in this format carried by PDCCH on the SCell for scheduling on the primary cell. +- DFI flag - 0 or 1 bit + - 1 bit if the UE is configured to monitor DCI format 0\_1 with CRC scrambled by CS-RNTI and for operation in a cell with shared spectrum channel access when the higher layer parameter *cg-RetransmissionTimer* is configured. For a DCI format 0\_1 with CRC scrambled by CS-RNTI, the bit value of 0 indicates activating or releasing type 2 CG transmission and the bit value of 1 indicates CG-DFI. For a DCI format 0\_1 with CRC scrambled by C-RNTI/SP-CSI-RNTI/MCS-C-RNTI and for operation in a cell with shared spectrum channel access, the bit is reserved. + - 0 bit otherwise; + +If DCI format 0\_1 is used for indicating CG-DFI, all the remaining fields are set as follows: + +- HARQ-ACK bitmap - 16 bits if *nrofHARQ-Processes-v1700* in *ConfiguredGrantConfig* is not configured or 32 bits if *nrofHARQ-Processes-v1700* in *ConfiguredGrantConfig* is configured, where the order of the bitmap to HARQ process index mapping is such that HARQ process indices are mapped in ascending order from MSB to LSB of the bitmap. For each bit of the bitmap, value 1 indicates ACK, and value 0 indicates NACK. +- TPC command for scheduled PUSCH - 2 bits as defined in Clause 7.1.1 of [5, TS38.213] +- All the remaining bits in format 0\_1 are set to zero. + +Otherwise, all the remaining fields are set as follows: + +- UL/SUL indicator - 0 bit for UEs not configured with *supplementaryUplink* in *ServingCellConfig* in the cell or UEs configured with *supplementaryUplink* in *ServingCellConfig* in the cell but only one carrier in the cell is configured for PUSCH transmission; otherwise, 1 bit as defined in Table 7.3.1.1.1-1. +- Bandwidth part indicator - 0, 1 or 2 bits as determined by the number of UL BWPs $n_{\text{BWP,RRC}}$ configured by higher layers, excluding the initial UL bandwidth part. The bitwidth for this field is determined as bits, where + - if $n_{\text{BWP,RRC}} \leq 3$ , in which case the bandwidth part indicator is equivalent to the ascending order of the higher layer parameter *BWP-Id*; + - otherwise, in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1; + If a UE does not support active BWP change via DCI, the UE ignores this bit field. +- Frequency domain resource assignment - number of bits determined by the following, where $N$ is the size of the active UL bandwidth part: + - If higher layer parameter *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated* is not configured + - $\lceil \log_2(N) \rceil$ bits if only resource allocation type 0 is configured, where $\lceil \log_2(N) \rceil$ is defined in Clause 6.1.2.2.1 of [6, TS 38.214], + - $\lceil \log_2(N) \rceil$ bits if only resource allocation type 1 is configured, or $\lceil \log_2(N) \rceil$ bits if *resourceAllocation* is configured as 'dynamicSwitch'. + - If *resourceAllocation* is configured as 'dynamicSwitch', the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit value of 1 indicates resource allocation type 1. + - For resource allocation type 0, the LSBs provide the resource allocation as defined in Clause 6.1.2.2.1 of [6, TS 38.214]. + - For resource allocation type 1, the LSBs provide the resource allocation as follows: + - For PUSCH hopping with resource allocation type 1: + - MSB bits are used to indicate the frequency offset according to Clause 6.3 of [6, TS 38.214], where if the higher layer parameter *frequencyHoppingOffsetLists* contains two offset values and if the higher layer parameter *frequencyHoppingOffsetLists* contains four offset values + - bits provide the frequency domain resource allocation according to Clause 6.1.2.2.2 of [6, TS 38.214] + - For non-PUSCH hopping with resource allocation type 1: + - bits provide the frequency domain resource allocation according to Clause 6.1.2.2.2 of [6, TS 38.214] + +If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if *resourceAllocation* is configured as 'dynamicSwitch' for the indicated bandwidth part, the UE assumes resource allocation type 0 for the indicated bandwidth part if the bitwidth of the "Frequency domain resource assignment" field of the active bandwidth part is smaller than the bitwidth of the "Frequency domain resource assignment" field of the indicated bandwidth part. + +- If the higher layer parameter *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated* is configured + - $5 + Y$ bits provide the frequency domain resource allocation according to Clause 6.1.2.2.3 of [6, TS 38.214] if the subcarrier spacing for the active UL bandwidth part is 30 kHz. The 5 MSBs provide the interlace allocation and the $Y$ LSBs provide the RB set allocation. + - $6 + Y$ bits provide the frequency domain resource allocation according to Clause 6.1.2.2.3 of [6, TS 38.214] if the subcarrier spacing for the active UL bandwidth part is 15 kHz. The 6 MSBs provide the interlace allocation and the $Y$ LSBs provide the RB set allocation. + +The value of $Y$ is determined by where $Y$ is the number of RB sets contained in the active UL BWP as defined in clause 7 of [6, TS38.214]. + +- Time domain resource assignment - 0, 1, 2, 3, 4, 5, or 6 bits + - If the higher layer parameter *pusch-TimeDomainAllocationListDCI-0-1* is not configured and if the higher layer parameter *pusch-TimeDomainAllocationListForMultiPUSCH* is not configured and if the higher layer + +parameter *pusch-TimeDomainAllocationList* is configured, 0, 1, 2, 3, or 4 bits as defined in Clause 6.1.2.1 of [6, TS38.214]. The bitwidth for this field is determined as bits, where *I* is the number of entries in the higher layer parameter *pusch-TimeDomainAllocationList*; + +- If the higher layer parameter *pusch-TimeDomainAllocationListDCI-0-1* is configured or if the higher layer parameter *pusch-TimeDomainAllocationListForMultiPUSCH* is configured, 0, 1, 2, 3, 4, 5 or 6 bits as defined in Clause 6.1.2.1 of [6, TS38.214]. The bitwidth for this field is determined as bits, where *I* is the number of entries in the higher layer parameter *pusch-TimeDomainAllocationListDCI-0-1* or *pusch-TimeDomainAllocationListForMultiPUSCH*; +- otherwise the bitwidth for this field is determined as bits, where *I* is the number of entries in the default table. +- Frequency hopping flag - 0 or 1 bit: +- 0 bit if only resource allocation type 0 is configured, or if the higher layer parameter *frequencyHopping* is not configured and the higher layer parameter *pusch-RepTypeIndicatorDCI-0-1* is not configured to *pusch-RepTypeB*, or if the higher layer parameter *frequencyHoppingDCI-0-1* is not configured and *pusch-RepTypeIndicatorDCI-0-1* is configured to *pusch-RepTypeB*, or if only resource allocation type 2 is configured; +- 1 bit according to Table 7.3.1.1.1-3 otherwise, only applicable to resource allocation type 1, as defined in Clause 6.3 of [6, TS 38.214]. + +For transport block 1: + +- Modulation and coding scheme - 5 bits as defined in Clause 6.1.4.1 of [6, TS 38.214] +- New data indicator - 1 bit if the number of scheduled PUSCH indicated by the Time domain resource assignment field is 1; otherwise 2, 3, 4, 5, 6, 7 or 8 bits determined based on the maximum number of schedulable PUSCH among all entries in the higher layer parameter *pusch-TimeDomainAllocationListForMultiPUSCH*, where each bit corresponds to one scheduled PUSCH as defined in clause 6.1.4 in [6, TS 38.214]. +- Redundancy version - - number of bits determined by the following: + - 2 bits as defined in Table 7.3.1.1.1-2 if the number of scheduled PUSCH indicated by the Time domain resource assignment field is 1; + - otherwise 2, 3, 4, 5, 6, 7 or 8 bits determined by the maximum number of schedulable PUSCHs among all entries in the higher layer parameter *pusch-TimeDomainAllocationListForMultiPUSCH*, where each bit corresponds to one scheduled PUSCH as defined in clause 6.1.4 in [6, TS 38.214] and redundancy version is determined according to Table 7.3.1.1.2-34. + +For transport block 2 (only present if *maxRank* > 4 or *maxMIMO-Layers* > 4): + +- Modulation and coding scheme - 5 bits as defined in Clause 6.1.4.1 of [6, TS 38.214] +- New data indicator - 1 bit +- Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2 + +If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part, the value of *maxRank* or *maxMIMO-Layers* for the indicated bandwidth part is larger than 4 and the value of *maxRank* or *maxMIMO-Layers* for the active bandwidth part is no more than 4, the UE assumes zeros are padded when interpreting the "Modulation and coding scheme", "New data indicator", and "Redundancy version" fields for transport block 2 according to Clause 12 of [5, TS38.213], and the UE ignores the "Modulation and coding scheme", "New data indicator", and "Redundancy version" fields of transport block 2 for the indicated bandwidth part. + +- Transform precoder indicator - 0 or 1 bit + - 1 bit if the higher layer parameter *dynamicTransformPrecoderIndicationDCI-0-1* is configured to 'enabled' and if the UE is configured to monitor DCI format 0\_1 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI, where the bit value of 0 indicates that transform precoder is enabled and the bit value of 1 indicates that transform precoder is disabled. For a DCI format 0\_1 with CRC scrambled by CS-RNTI and the value indicated by new data indicator field is 0, or for a DCI format 0\_1 with CRC scrambled by SP-CSI-RNTI, the bit is reserved. + - 0 bit otherwise. +- HARQ process number - 5 bits if higher layer parameter *harq-ProcessNumberSizeDCI-0-1* is configured; otherwise 4 bits +- 1st downlink assignment index - 1, 2 or 4 bits: + - 1 bit for semi-static HARQ-ACK codebook for unicast and multicast if *pdsch-HARQ-ACK-Codebook* = *semiStatic* is configured for both unicast and multicast and the higher layer parameter *fdmed-ReceptionMulticast* is not configured; otherwise for semi-static HARQ-ACK codebook for unicast; + - 2 bits for dynamic HARQ-ACK codebook for unicast, or for enhanced dynamic HARQ-ACK codebook without *UL-TotalDAI-Included* configured; + +- 4 bits for enhanced dynamic HARQ-ACK codebook and with *UL-TotalDAI-Included = true*. +When two HARQ-ACK codebooks are configured by *pdsch-HARQ-ACK-CodebookList* for the same serving cell and if higher layer parameter *priorityIndicatorDCI-0-1* is configured, if the bit width of the 1st downlink assignment index in DCI format 0\_1 for one HARQ-ACK codebook is not equal to that of the 1st downlink assignment index in DCI format 0\_1 for the other HARQ-ACK codebook, a number of most significant bits with value set to '0' are inserted to smaller 1st downlink assignment index until the bit width of the 1st downlink assignment index in DCI format 0\_1 for the two HARQ-ACK codebooks are the same. +- 2nd downlink assignment index - 0, 2 or 4 bits: + - 2 bits for dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks for unicast, or for enhanced dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks and without *UL-TotalDAI-Included* configured; + - 4 bits for enhanced dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks and with *UL-TotalDAI-Included = true*; + - 0 bit otherwise. +When two HARQ-ACK codebooks are configured by *pdsch-HARQ-ACK-CodebookList* for the same serving cell and if higher layer parameter *priorityIndicatorDCI-0-1* is configured, if the bit width of the 2nd downlink assignment index in DCI format 0\_1 for one HARQ-ACK codebook is not equal to that of the 2nd downlink assignment index in DCI format 0\_1 for the other HARQ-ACK codebook, a number of most significant bits with value set to '0' are inserted to smaller 2nd downlink assignment index until the bit width of the 2nd downlink assignment index in DCI format 0\_1 for the two HARQ-ACK codebooks are the same. +- 3rd downlink assignment index - 0, 1 or 2 bits: + - 1 bit for semi-static HARQ-ACK codebook for multicast if the higher layer parameter *fdmed-ReceptionMulticast* is configured; + - 2 bits for the dynamic HARQ-ACK codebook for multicast; + - 0 bit otherwise. +When two HARQ-ACK codebooks are configured by *pdsch-HARQ-ACK-CodebookListMulticast* for the same serving cell and if higher layer parameter *priorityIndicatorDCI-0-1* is configured, if the bit width of the 3rd downlink assignment index in DCI format 0\_1 for one HARQ-ACK codebook is not equal to that of the 3rd downlink assignment index in DCI format 0\_1 for the other HARQ-ACK codebook, a number of most significant bits with value set to '0' are inserted to smaller 3rd downlink assignment index until the bit width of the 3rd downlink assignment index in DCI format 0\_1 for the two HARQ-ACK codebooks are the same. +- TPC command for scheduled PUSCH - 2 bits as defined in Clause 7.1.1 of [5, TS38.213] +- Second TPC command for scheduled PUSCH - 2 bits as defined in Clause 7.1.1 of [5, TS38.213] if higher layer parameter *SecondTPCFieldDCI-0-1* is configured; 0 bit otherwise. +- SRS resource set indicator - 0 or 2 bits + - 2 bits according to Table 7.3.1.1.2-36 if + - *txConfig = nonCodeBook*, and there are two SRS resource sets configured by *srs-ResourceSetToAddModList* and associated with the *usage* of value '*nonCodeBook*', and is not configured with *coresetPoolIndex* or the value of *coresetPoolIndex* is the same for all CORESETs if *coresetPoolIndex* is provided, or + - *txConfig=codebook*, and there are two SRS resource sets configured by *srs-ResourceSetToAddModList* and associated with *usage* of value '*codebook*', and is not configured with *coresetPoolIndex* or the value of *coresetPoolIndex* is the same for all CORESETs if *coresetPoolIndex* is provided; + - 0 bit otherwise. +- SRS resource indicator -number of bits determined by the following: + - bits according to Tables 7.3.1.1.2-28/28A/29/29B/30/30B/31/31B/31C/31D/31E/31F if the higher layer parameter *txConfig = nonCodeBook*, where + - is the number of configured SRS resources in the SRS resource set indicated by SRS resource set indicator field if present, + - is the number of configured SRS resources in the SRS resource set associated with the *coresetPoolIndex* value for the CORESET used for the PDCCH carrying the DCI format 0\_1, if the UE is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with value 0 for the first CORESETs, and is provided *coresetPoolIndex* with value 1 for the second CORESETs, and is provided *enableSTx2PofmDCI*, + - otherwise is the number of configured SRS resources in the SRS resource set configured by higher layer parameter *srs-ResourceSetToAddModList* and associated with the higher layer parameter *usage* of value '*nonCodeBook*', + +and + +- if UE supports operation with *maxMIMO-Layers* and the higher layer parameter *maxMIMO-Layers* of *PUSCH-ServingCellConfig* of the serving cell is configured, + - $L_{max}$ is given by $\max\{maxMIMO-Layers, maxMIMO-LayersforSdm\}$ if *maxMIMO-LayersforSdm* is configured + - $L_{max}$ is given by $\max\{maxMIMO-Layers, maxMIMO-LayersforSfn\}$ if *maxMIMO-LayersforSfn* is configured + - $L_{max}$ is given by *maxMIMO-Layers* otherwise +- otherwise, $L_{max}$ is given by the maximum number of layers for PUSCH supported by the UE for the serving cell for non-codebook based operation. +- bits according to Tables 7.3.1.1.2-32, 7.3.1.1.2-32A and 7.3.1.1.2-32B if the higher layer parameter *txConfig* = *codebook*, where + - is the number of configured SRS resources in the SRS resource set indicated by SRS resource set indicator field if present, + - is the number of configured SRS resources in the SRS resource set associated with the *coresetPoolIndex* value for the CORESET used for the PDCCH carrying the DCI format 0\_1, if the UE is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with value 0 for the first CORESETs, and is provided *coresetPoolIndex* with value 1 for the second CORESETs, and is provided *enableSTx2PofmDCI*, + - otherwise is the number of configured SRS resources in the SRS resource set configured by higher layer parameter *srs-ResourceSetToAddModList* and associated with the higher layer parameter *usage* of value 'codeBook'. + +When the UE is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with value 0 for the first CORESETs, and is provided *coresetPoolIndex* with value 1 for the second CORESETs, and is provided *enableSTx2PofmDCI*, and there are two SRS resource sets configured by *srs-ResourceSetToAddModList* and associated with *usage* of value 'codebook' or 'nonCodeBook', the first SRS resource set is associated with *coresetPoolIndex* value 0 and the second SRS resource set is associated with *coresetPoolIndex* value 1, where the first and the second SRS resource sets are respectively the ones with lower and higher *srs-ResourceSetId* of the two SRS resources sets. + +- Second SRS resource indicator - number of bits determined by the following: + - bits according to Tables 7.3.1.1.2-28/29A/30A/31A with the same number of layers indicated by SRS resource indicator field if the higher layer parameter *txConfig* = *nonCodebook*, the higher layer parameter *maxMIMO-LayersforSdm* is not configured, and SRS resource set indicator field is present, where is the number of configured SRS resources in the second SRS resource set, and + - if UE supports operation with *maxMIMO-Layers* and the higher layer parameter *maxMIMO-Layers* of *PUSCH-ServingCellConfig* of the serving cell is configured, + - $L_{max}$ is given by *maxMIMO-LayersforSfn* if *maxMIMO-LayersforSfn* is configured + - $L_{max}$ is given by *maxMIMO-Layers* otherwise + - otherwise, $L_{max}$ is given by the maximum number of layers for PUSCH supported by the UE for the serving cell for non-codebook based operation. + - bits according to Tables 7.3.1.1.2-28/29 if the higher layer parameter *txConfig* = *nonCodebook*, the higher layer parameter *maxMIMO-LayersforSdm* is configured and SRS resource set indicator field is present, where is the number of configured SRS resources in the second SRS resource set, and $L_{max}$ is given by *maxMIMO-LayersforSdm*. + - bits according to Tables 7.3.1.1.2-32, 7.3.1.1.2-32A and 7.3.1.1.2-32B if the higher layer parameter *txConfig* = *codebook* and SRS resource set indicator field is present, where is the number of configured SRS resources in the second SRS resource set. + - 0 bit otherwise. +- Precoding information and number of layers - number of bits determined by the following: + - 0 bits if the higher layer parameter *txConfig* = *nonCodeBook*; + - 0 bits for 1 antenna port and if the higher layer parameter *txConfig* = *codebook*; + - 4, 5, or 6 bits according to Table 7.3.1.1.2-2 for 4 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, transform precoder is disabled, and according to the values of higher layer parameters *maxRank* if *multipanelScheme* is not configured or $\max\{maxRank, maxRankSfn\}$ if *multipanelScheme* = *sfnScheme* or $\max\{maxRank, maxRankSdm\}$ if *multipanelScheme* = *sdmScheme*, and *codebookSubset*; + - 4 or 5 bits according to Table 7.3.1.1.2-2A for 4 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, *maxRank*=2 if *multipanelScheme* is not configured or $\max\{maxRank, maxRankSfn\}$ = 2 if *multipanelScheme* = *sfnScheme* or $\max\{maxRank, maxRankSdm\}$ = 2 if *multipanelScheme* = *sdmScheme*, transform precoder is disabled, and according to the values of higher layer parameter *codebookSubset*; + +- 4 or 6 bits according to Table 7.3.1.1.2-2B for 4 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, *maxRank*=3 or 4, transform precoder is disabled, and according to the values of higher layer parameter *codebookSubset*; +- 2, 4, or 5 bits according to Table 7.3.1.1.2-3 for 4 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to whether transform precoder is enabled or disabled, and *maxRank*=1 if *multipanelScheme* is not configured or $\max\{\maxRank, \maxRankSfn\} = 1$ if *multipanelScheme* = *sfnScheme* or $\max\{\maxRank, \maxRankSdm\} = 1$ if *multipanelScheme* = *sdmScheme*, and *codebookSubset*; +- 3 or 4 bits according to Table 7.3.1.1.2-3A for 4 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, *maxRank*=1 if *multipanelScheme* is not configured or $\max\{\maxRank, \maxRankSfn\} = 1$ if *multipanelScheme* = *sfnScheme* or $\max\{\maxRank, \maxRankSdm\} = 1$ if *multipanelScheme* = *sdmScheme*, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameter *codebookSubset*; +- 2 or 4 bits according to Table 7.3.1.1.2-4 for 2 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, transform precoder is disabled, and according to the values of higher layer parameters *maxRank* if *multipanelScheme* is not configured or $\max\{\maxRank, \maxRankSfn\}$ if *multipanelScheme* = *sfnScheme* or $\max\{\maxRank, \maxRankSdm\}$ if *multipanelScheme* = *sdmScheme*, and *codebookSubset*; +- 2 bits according to Table 7.3.1.1.2-4A for 2 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, transform precoder is disabled, *maxRank*=2 if *multipanelScheme* is not configured or $\max\{\maxRank, \maxRankSfn\} = 2$ if *multipanelScheme* = *sfnScheme* or $\max\{\maxRank, \maxRankSdm\} = 2$ if *multipanelScheme* = *sdmScheme*, and *codebookSubset*=*nonCoherent*; +- 1 or 3 bits according to Table 7.3.1.1.2-5 for 2 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to whether transform precoder is enabled or disabled, and *maxRank*=1 if *multipanelScheme* is not configured or $\max\{\maxRank, \maxRankSfn\} = 1$ if *multipanelScheme* = *sfnScheme* or $\max\{\maxRank, \maxRankSdm\} = 1$ if *multipanelScheme* = *sdmScheme*, and *codebookSubset*; +- 2 bits according to Table 7.3.1.1.2-5A for 2 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, *maxRank*=1 if *multipanelScheme* is not configured or $\max\{\maxRank, \maxRankSfn\} = 1$ if *multipanelScheme* = *sfnScheme* or $\max\{\maxRank, \maxRankSdm\} = 1$ if *multipanelScheme* = *sdmScheme*, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameter *codebookSubset*; +- 7 bits according to Table 7.3.1.1.2-5B for 8 antenna ports, if *CodebookType*=*Codebook1*, transform precoder is disabled, *maxRank* = 8, and according to *ULcodebookFC-N1N2*; +- 7 bits according to Table 7.3.1.1.2-5C for 8 antenna ports, if *CodebookType*=*Codebook1*, transform precoder is disabled, *maxRank* = 7, and according to *ULcodebookFC-N1N2*; +- 7 bits according to Table 7.3.1.1.2-5D for 8 antenna ports, if *CodebookType*=*Codebook1*, transform precoder is disabled, *maxRank* = 4, 5 or 6, and according to *maxRank*; +- 4, 6 or 7 bits according to Table 7.3.1.1.2-5E for 8 antenna ports, if *CodebookType*=*Codebook1*, transform precoder is enabled or *maxRank* = 1, 2 or 3 if transform precoder is disabled, and according to transform precoder and *maxRank*; +- 8 bits according to Table 7.3.1.1.2-5F for 8 antenna ports, if *CodebookType*=*Codebook4*, transform precoder is disabled, *maxRank*=5, 6, 7 or 8, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to *maxRank*; +- 6 or 7 or 8 bits according to Table 7.3.1.1.2-5G for 8 antenna ports, if *CodebookType*=*Codebook4*, transform precoder is disabled, *maxRank*=2, 3 or 4, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to *maxRank*; +- 3 bits according to Table 7.3.1.1.2-5H for 8 antenna ports, if *CodebookType*=*Codebook4*, transform precoder is enabled or *maxRank*=1 if transform precoder is disabled, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*. +- 10 bits according to Table 7.3.1.1.2-5I for 8 antenna ports, if *CodebookType*=*Codebook2*, transform precoder is disabled, *maxRank*=5, 6, 7 or 8, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to *maxRank*; +- 5, 9 or 10 bits according to Table 7.3.1.1.2-5J for 8 antenna ports, if *CodebookType*=*Codebook2*, transform precoder is enabled or *maxRank* = 1, 2, 3 or 4 if transform precoder is disabled, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to transform precoder and *maxRank*; +- 10 bits according to Table 7.3.1.1.2-5K for 8 antenna ports, if *CodebookType*=*Codebook3*, transform precoder is disabled, *maxRank*=5, 6, 7 or 8, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to *maxRank*; + +- 4, 7, 9 or 10 bits according to Table 7.3.1.1.2-5L for 8 antenna ports, if *CodebookType=Codebook3*, transform precoder is enabled or *maxRank*=1, 2, 3 or 4 if transform precoder is disabled, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to transform precoder and *maxRank*; +- 6 or 7 or 8 bits according to Table 7.3.1.1.2-5M for 8 antenna ports, if *CodebookType=Codebook4*, transform precoder is disabled, *maxRank*=2, 3 or 4, *ul-FullPowerTransmission* is configured to *fullpowerMode1*, and according to *maxRank*; +- 4 bits according to Table 7.3.1.1.2-5N for 8 antenna ports, if *CodebookType=Codebook4*, transform precoder is enabled or *maxRank*=1 if transform precoder is disabled, *ul-FullPowerTransmission* is configured to *fullpowerMode1*. +- 6, 9 or 10 bits according to Table 7.3.1.1.2-5O for 8 antenna ports, if *CodebookType=Codebook2*, transform precoder is enabled or *maxRank*=1, 2, 3 or 4 if transform precoder is disabled, *ul-FullPowerTransmission* is configured to *fullpowerMode1*, and according to transform precoder and *maxRank*; +- 5, 7, 9 or 10 bits according to Table 7.3.1.1.2-5P for 8 antenna ports, if *CodebookType=Codebook3*, transform precoder is enabled or *maxRank*=1, 2, 3, or 4 if transform precoder is disabled, *ul-FullPowerTransmission* is configured to *fullpowerMode1*, and according to transform precoder and *maxRank*; +- 8 or 9 bits according to Table 7.3.1.1.2-5Q for 8 antenna ports, if *CodebookType=Codebook4*, transform precoder is disabled, *maxRank*=5, 6, 7 or 8, *ul-FullPowerTransmission* is configured to *fullpowerMode1*, and according to *maxRank*; +- 10 bits according to Table 7.3.1.1.2-5R for 8 antenna ports, if *CodebookType=Codebook2*, transform precoder is disabled, *maxRank*=5, 6, 7 or 8, *ul-FullPowerTransmission* is configured to *fullpowerMode1*, and according to *maxRank*; +- 10 bits according to Table 7.3.1.1.2-5S for 8 antenna ports, if *CodebookType=Codebook3*, transform precoder is disabled, *maxRank*=5, 6, 7, or 8, *ul-FullPowerTransmission* is configured to *fullpowerMode1*, and according to *maxRank*; + +For the higher layer parameter *txConfig=codebook*, if *ul-FullPowerTransmission* is configured to *fullpowerMode2*, *maxRank* is configured to be larger than 2, and at least one SRS resource with 4 antenna ports or 8 antenna ports is configured in the SRS resource set indicated by SRS resource set indicator field if present, otherwise in an SRS resource set with usage set to 'codebook', and an SRS resource with 2 antenna ports is indicated via SRI in the same SRS resource set, then Table 7.3.1.1.2-4 is used. + +For the higher layer parameter *txConfig=codebook*, if *ul-FullPowerTransmission* is configured to *fullpowerMode2*, *maxRank* is configured to be larger than 4, and at least one SRS resource with 8 antenna ports is configured in the SRS resource set with usage set to 'codebook', and an SRS resource with 4 antenna ports is indicated via SRI in the same SRS resource set, then Table 7.3.1.1.2-2 is used. + +For the higher layer parameter *txConfig = codebook*, if different SRS resources with different number of antenna ports are configured, the bitwidth is determined according to the maximum number of ports in an SRS resource among the configured SRS resources in all SRS resource set(s) with usage set to 'codebook'. If the number of ports for a configured SRS resource in the set is less than the maximum number of ports in an SRS resource among the configured SRS resources, a number of most significant bits with value set to '0' are inserted to the field. + +When the UE is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with value 0 for the first CORESETs, and is provided *coresetPoolIndex* with value 1 for the second CORESETs, and is provided *enableSTx2PofmDCI*, and there are two SRS resource sets configured by *srs-ResourceSetToAddModList* and associated with *usage* of value 'codebook' or 'nonCodeBook', the Precoding information and number of layers field is associated with the SRS resource set that is associated with the *coresetPoolIndex* value for the CORESET used for the PDCCH carrying the DCI format 0\_1. + +For the higher layer parameter *txConfig = codebook*, when the Transform precoder indicator field is present, if the bit width of the Precoding information and number of layers field for the case with transform precoder enabled is not equal to that for the case with transform precoder disabled, a number of most significant bits with value set to '0' are inserted to the Precoding information and number of layers field for the case with smaller bit width until the bit width of the Precoding information and number of layers field for the two cases are the same. + +- Second Precoding information - number of bits determined by the following: + - 0 bits if SRS resource set indicator field is not present; + - 0 bits if the higher layer parameter *txConfig = nonCodeBook*; + - 0 bits for 1 antenna port and if the higher layer parameter *txConfig = codebook*; + - 3, 4, or 5 bits according to Table 7.3.1.1.2-2C with the same number of layers indicated by Precoding information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present, + +*txConfig = codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, transform precoder is disabled, and according to the values of higher layer parameters *maxRank* if *multipanelScheme* is not configured or *maxRankSfn* if *multipanelScheme = sfnScheme*, and *codebookSubset*; + +- 3 or 4 bits according to Table 7.3.1.1.2-2D with the same number of layers indicated by Precoding information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present, *txConfig = codebook*, *ul-FullPowerTransmission = fullpowerMode1*, *maxRank=2* if *multipanelScheme* is not configured or *maxRankSfn=2* if *multipanelScheme = sfnScheme*, transform precoder is disabled, and according to the values of higher layer parameter *codebookSubset*; +- 3 or 4 bits according to Table 7.3.1.1.2-2E with the same number of layers indicated by Precoding information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present, *txConfig = codebook*, *ul-FullPowerTransmission = fullpowerMode1*, *maxRank=3 or 4*, transform precoder is disabled, and according to the values of higher layer parameter *codebookSubset*; +- 2, 4, or 5 bits according to Table 7.3.1.1.2-3 with the same number of layers indicated by Precoding information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present, *txConfig = codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters *maxRank* if *multipanelScheme* is not configured or *maxRankSfn* if *multipanelScheme = sfnScheme*, and *codebookSubset*; +- 3 or 4 bits according to Table 7.3.1.1.2-3A with the same number of layers indicated by Precoding information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present, *txConfig = codebook*, *ul-FullPowerTransmission = fullpowerMode1*, *maxRank=1* if *multipanelScheme* is not configured or *maxRankSfn=1* if *multipanelScheme = sfnScheme*, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameter *codebookSubset*; +- 1 or 3 bits according to Table 7.3.1.1.2-4B with the same number of layers indicated by Precoding information and number of layers field for 2 antenna ports, if SRS resource set indicator field is present, *txConfig = codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, transform precoder is disabled, and according to the values of higher layer parameters *maxRank* if *multipanelScheme* is not configured or *maxRankSfn* if *multipanelScheme = sfnScheme*, and *codebookSubset*; +- 2 bits according to Table 7.3.1.1.2-4C with the same number of layers indicated by Precoding information and number of layers field for 2 antenna ports, if SRS resource set indicator field is present, *txConfig = codebook*, *ul-FullPowerTransmission = fullpowerMode1*, transform precoder is disabled, *maxRank=2* if *multipanelScheme* is not configured or *maxRankSfn=2* if *multipanelScheme = sfnScheme*, and *codebookSubset=nonCoherent*; +- 1 or 3 bits according to Table 7.3.1.1.2-5 with the same number of layers indicated by Precoding information and number of layers field for 2 antenna ports, if SRS resource set indicator field is present, *txConfig = codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters *maxRank* if *multipanelScheme* is not configured or *maxRankSfn* if *multipanelScheme = sfnScheme*, and *codebookSubset*; +- 2 bits according to Table 7.3.1.1.2-5A with the same number of layers indicated by Precoding information and number of layers field for 2 antenna ports, if SRS resource set indicator field is present, *txConfig = codebook*, *ul-FullPowerTransmission = fullpowerMode1*, *maxRank=1* if *multipanelScheme* is not configured or *maxRankSfn=1* if *multipanelScheme = sfnScheme*, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameter *codebookSubset*; +- 4, 5, or 6 bits according to Table 7.3.1.1.2-2 for 4 antenna ports, if *txConfig = codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, transform precoder is disabled, and according to the values of higher layer parameters *maxRankSdm* if *multipanelScheme = sdmScheme*, and *codebookSubset*; +- 4 or 5 bits according to Table 7.3.1.1.2-2A for 4 antenna ports, if *txConfig = codebook*, *ul-FullPowerTransmission = fullpowerMode1*, *maxRankSdm = 2* if *multipanelScheme = sdmScheme*, transform precoder is disabled, and according to the values of higher layer parameter *codebookSubset*; +- 2, 4, or 5 bits according to Table 7.3.1.1.2-3 for 4 antenna ports, if *txConfig = codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters *maxRankSdm* if *multipanelScheme = sdmScheme*, and *codebookSubset*; +- 3 or 4 bits according to Table 7.3.1.1.2-3A for 4 antenna ports, if *txConfig = codebook*, *ul-FullPowerTransmission = fullpowerMode1*, *maxRankSdm = 1* if *multipanelScheme = sdmScheme*, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameter *codebookSubset*; + +- 2 or 4 bits according to Table 7.3.1.1.2-4 for 2 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, transform precoder is disabled, and according to the values of higher layer parameters *maxRankSdm* if *multipanelScheme* = *sdmScheme*, and *codebookSubset*; +- 2 bits according to Table 7.3.1.1.2-4A for 2 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, transform precoder is disabled, *maxRankSdm* = 2 if *multipanelScheme* = *sdmScheme*, and *codebookSubset* = *nonCoherent*; +- 1 or 3 bits according to Table 7.3.1.1.2-5 for 2 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to whether transform precoder is enabled or disabled, and *maxRankSdm* = 1 if *multipanelScheme* = *sdmScheme*, and *codebookSubset*; +- 2 bits according to Table 7.3.1.1.2-5A for 2 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, *maxRankSdm* = 1 if *multipanelScheme* = *sdmScheme*, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameter *codebookSubset*; + +For the higher layer parameter *txConfig* = *codebook*, if *ul-FullPowerTransmission* is configured to *fullpowerMode2*, *maxRank* is configured to be larger than 2, and at least one SRS resource with 4 antenna ports is configured in the SRS resource set indicated by SRS resource set indicator field, and an SRS resource with 2 antenna ports is indicated via Second SRS resource indicator field in the same SRS resource set, then Table 7.3.1.1.2-4B is used. + +For the higher layer parameter *txConfig* = *codebook*, if different SRS resources with different number of antenna ports are configured, the bitwidth is determined according to the maximum number of ports in an SRS resource among the configured SRS resources in the second SRS resource set with usage set to 'codebook' as defined in Table 7.3.1.1.2-36. If the number of ports for a configured SRS resource in the set is less than the maximum number of ports in an SRS resource among the configured SRS resources, a number of most significant bits with value set to '0' are inserted to the field. + +For the higher layer parameter *txConfig* = *codebook*, when the Transform precoder indicator field is present, if the bit width of the Second Precoding information field for the case with transform precoder enabled is not equal to that for the case with transform precoder disabled, a number of most significant bits with value set to '0' are inserted to the Second Precoding information field for the case with smaller bit width until the bit width of the Second Precoding information field for the two cases are the same. + +- Antenna ports - number of bits determined by the following + - 2 bits as defined by Tables 7.3.1.1.2-6, if transform precoder is enabled, *dmrs-Type*=1, and *maxLength*=1, except that *dmrs-UplinkTransformPrecoding* and *tp-pi2BPSK* are both configured and $\pi/2$ BPSK modulation is used; + - 2 bits as defined by Tables 7.3.1.1.2-6A, if transform precoder is enabled and *dmrs-UplinkTransformPrecoding* and *tp-pi2BPSK* are both configured, $\pi/2$ BPSK modulation is used, *dmrs-Type*=1, and *maxLength*=1, where *nSCID* is the scrambling identity for antenna ports defined in Clause 6.4.1.1.1.2, TS 38.211 [4]; + - 4 bits as defined by Tables 7.3.1.1.2-7, if transform precoder is enabled, *dmrs-Type*=1, and *maxLength*=2, except that *dmrs-UplinkTransformPrecoding* and *tp-pi2BPSK* are both configured and $\pi/2$ BPSK modulation is used; + - 4 bits as defined by Tables 7.3.1.1.2-7A, if transform precoder is enabled and *dmrs-UplinkTransformPrecoding* and *tp-pi2BPSK* are both configured, $\pi/2$ BPSK modulation is used, *dmrs-Type*=1, and *maxLength*=2, where *nSCID* is the scrambling identity for antenna ports defined in Clause 6.4.1.1.1.2, TS 38.211 [4]; + - 3 bits as defined by Tables 7.3.1.1.2-8/9/10/10A/11 according to the value of rank, if transform precoder is disabled, *dmrs-Type*=1, *enhanced-dmrs-Type* is not configured, and *maxLength*=1; + - 4 bits as defined by Tables 7.3.1.1.2-12/13/14/15/15A/15B/15C/15D according to the value of rank, if transform precoder is disabled, *dmrs-Type*=1, *enhanced-dmrs-Type* is not configured, and *maxLength*=2; + - 4 bits as defined by Tables 7.3.1.1.2-16/17/18/18A/19/19A/19B according to the value of rank, if transform precoder is disabled, *dmrs-Type*=2, *enhanced-dmrs-Type* is not configured, and *maxLength*=1; + - 5 bits as defined by Tables 7.3.1.1.2-20/21/22/22A/23/23A/23B/23C/23D according to the value of rank, if transform precoder is disabled, *dmrs-Type*=2, *enhanced-dmrs-Type* is not configured, and *maxLength*=2. + - 4 bits as defined by Tables 7.3.1.1.2-38/39/40/40A/41/42/43/44/45, if transform precoder is disabled, *dmrs-Type*=1, *enhanced-dmrs-Type* is configured, and *maxLength*=1; + - 5 bits as defined by Tables 7.3.1.1.2-46/47/48/48A/49/50/51/52/53, if transform precoder is disabled, *dmrs-Type*=1, *enhanced-dmrs-Type* is configured, and *maxLength*=2; + +- 5 bits as defined by Tables 7.3.1.1.2-54/55/56/56A/57/58/59/60/61, if transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is configured, and *maxLength=1*; +- 6 bits as defined by Tables 7.3.1.1.2-62/63/64/64A/65/66/67/68/69, if transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is configured, and *maxLength=2*. + +where the number of CDM groups without data of values 1, 2, and 3 in Tables 7.3.1.1.2-6 to 7.3.1.1.2-23 refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively, and the value of rank is: + +- the sum of the value determined according to the SRS resource indicator field and the value determined according to the second SRS resource indicator field, if *txConfig = nonCodebook*, *multipanelScheme = sdmScheme* and SRS resource set indicator field equals "10" +- the sum of the value determined according to the Precoding information and number of layers field and the value determined according to the Second Precoding information, if *txConfig = codebook*, *multipanelScheme = sdmScheme* and SRS resource set indicator field equals "10" +- determined according to the SRS resource indicator field if the higher layer parameter *txConfig = nonCodebook* and *multipanelScheme = sdmScheme* is not configured, or if the higher layer parameter *txConfig = nonCodebook*, *multipanelScheme = sdmScheme* and SRS resource set indicator field equals "00" or "01", +- determined according to the Precoding information and number of layers field if the higher layer parameter *txConfig = codebook* and *multipanelScheme = sdmScheme* is not configured, or if the higher layer parameter *txConfig = codebook*, *multipanelScheme = sdmScheme* and SRS resource set indicator field equals "00" or "01". + +If a UE is configured with both *dmrs-UplinkForPUSCH-MappingTypeA* and *dmrs-UplinkForPUSCH-* + +*MappingTypeB*, the bitwidth of this field equals $\max\{x_A, x_B\}$ , where $x_A$ is the "Antenna ports" bitwidth derived according to *dmrs-UplinkForPUSCH-MappingTypeA* and $x_B$ is the "Antenna ports" bitwidth derived according to *dmrs-UplinkForPUSCH-MappingTypeB*. A number of $|x_A - x_B|$ zeros are padded in the MSB of this field, if the mapping type of the PUSCH corresponds to the smaller value of $x_A$ and $x_B$ . + +When the Transform precoder indicator field is present, if the bit width of the Antenna ports field for the case with transform precoder enabled is not equal to that for the case with transform precoder disabled, a number of most significant bits with value set to '0' are inserted to the Antenna ports field for the case with smaller bit width until the bit width of the Antenna ports field for the two cases are the same. + +- SRS request - 2 bits as defined by Table 7.3.1.1.2-24 for UEs not configured with *supplementaryUplink* in *ServingCellConfig* in the cell; 3 bits for UEs configured with *supplementaryUplink* in *ServingCellConfig* in the cell where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-1 and the second and third bits are defined by Table 7.3.1.1.2-24. This bit field may also indicate the associated CSI-RS according to Clause 6.1.1.2 of [6, TS 38.214]. +- SRS offset indicator - 0, 1 or 2 bits. + - 0 bit if higher layer parameter *AvailableSlotOffset* is not configured for any aperiodic SRS resource set in the scheduled cell, or if higher layer parameter *AvailableSlotOffset* is configured for at least one aperiodic SRS resource set in the scheduled cell and the maximum number of entries of *availableSlotOffsetList* configured for all aperiodic SRS resource set(s) is 1; + - otherwise, bits are used to indicate available slot offset according to Table 7.3.1.1.2-37 and Clause 6.2.1 of [6, TS 38.214], where K is the maximum number of entries of *availableSlotOffsetList* configured for all aperiodic SRS resource set(s) in the scheduled cell; +- CSI request - 0, 1, 2, 3, 4, 5, or 6 bits determined by higher layer parameter *reportTriggerSize*. +- CBG transmission information (CBGTI) - 0 bit if higher layer parameter *codeBlockGroupTransmission* for PUSCH is not configured or if the number of scheduled PUSCH indicated by the Time domain resource assignment field is larger than 1; otherwise, 2, 4, 6, or 8 bits as defined in Clause 6.1.5 of [6, TS38.214], determined by higher layer parameter *maxCodeBlockGroupsPerTransportBlock* and *maxRank* or *maxMIMO-Layers* for PUSCH. +- PTRS-DMRS association - number of bits determined as follows + - 0 bit if *PTRS-UplinkConfig* is not configured in either *dmrs-UplinkForPUSCH-MappingTypeA* or *dmrs-UplinkForPUSCH-MappingTypeB* and transform precoder is disabled, or if transform precoder is enabled, or if *maxRank=1* and *multipanelScheme* is not configured, or if *maxRank=1* and *maxRankSfn=1*, or if *maxRank=1* and *maxRankSdm=1* when two PTRS ports are configured by *maxNrofPortsforSdm*; + +- 2 or 4 bits otherwise, where Table 7.3.1.1.2-25/7.3.1.1.2-25A/7.3.1.1.2-25B/7.3.1.1.2-26/7.3.1.1.2-26A are used to indicate the association between PTRS port(s) and DMRS port(s), and the DMRS ports are indicated by the Antenna ports field. +- 2 bits when one PTRS port or two PTRS ports are configured by *maxNrofPorts* in *PTRS-UplinkConfig*, SRS resource set indicator field is absent or SRS resource set indicator field is present and equals "00" or "01" and *maxRank*≤4, this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to SRS resource indicator field and/or Precoding information and number of layers field according to Tables 7.3.1.1.2-25 and 7.3.1.1.2-26. +- 2 bits when one PTRS port or two PTRS ports are configured by *maxNrofPorts* in *PTRS-UplinkConfig*, the SRS resource set indicator field is present and equals "10" or "11", *maxRank*=3 or 4 and *multipanelScheme* is not configured, this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to SRS resource indicator field and/or Precoding information and number of layers field according to Tables 7.3.1.1.2-25 and 7.3.1.1.2-26. +- 2 bits when one PTRS port is configured by *maxNrofPorts* in *PTRS-UplinkConfig*, the SRS resource set indicator field is present and equals "10" and "11", *maxRank*=2 and *multipanelScheme* is not configured, the MSB of this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to SRS resource indicator and/or Precoding information and number of layers field, and the LSB of this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to Second SRS resource indicator field and/or Second Precoding information field, according to Table 7.3.1.1.2-25A. +- 2 bits when two PTRS ports are configured by *maxNrofPortsforSDM* in *PTRS-UplinkConfig*, the SRS resource set indicator field is present and equals "10" and *multipanelScheme* is configured to *sdmScheme*, the MSB of this field indicates the association between PTRS port 0 and DMRS port(s) corresponding to SRS resource indicator field and/or Precoding information and number of layers field, and the LSB of this field indicates the association between PTRS port 1 and DMRS port(s) corresponding to Second SRS resource indicator field and/or Second Precoding information field, according to Table 7.3.1.1.2-25A. +- 2 bits when one PTRS port is configured by *maxNrofPortsforSDM* in *PTRS-UplinkConfig*, SRS resource set indicator field is present and equals "10" and *multipanelScheme* is configured to *sdmScheme*, this field indicates the association between PTRS port and DMRS ports corresponding to SRS resource indicator field and Second SRS resource indicator field and/or Precoding information and number of layers field and Second Precoding information field according to Table 7.3.1.1.2-25. +- 2 bits when one PTRS port or two PTRS ports are configured by *maxNrofPorts* in *PTRS-UplinkConfig*, SRS resource set indicator field is present and equals "10", *multipanelScheme* is configured to *sfnScheme*, this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to SRS resource indicator field and/or Precoding information and number of layers field according to Tables 7.3.1.1.2-25 and 7.3.1.1.2-26. +- 2 bits when one PTRS port is configured by *maxNrofPorts* in *PTRS-UplinkConfig*, the SRS resource set indicator field is absent, *maxRank*>4 and *multipanelScheme* is not configured, this field indicates the association between PTRS port and DMRS port(s) corresponding to the selected codeword according to Table 7.3.1.1.2-25B, where the selected codeword is the codeword with higher MCS for the initial PUSCH if the MCS indices of the two codewords are different for the initial PUSCH, or codeword 0 otherwise. +- 4 bits when two PTRS ports are configured by *maxNrofPorts* in *PTRS-UplinkConfig*, the SRS resource set indicator field is absent, *maxRank*>4 and *multipanelScheme* is not configured, this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to SRS resource indicator field and/or Precoding information and number of layers field according to Table 7.3.1.1.2-26A. + +If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and the "PTRS-DMRS association" field is present for the indicated bandwidth part but not present for the active bandwidth part, the UE assumes the "PTRS-DMRS association" field is not present for the indicated bandwidth part. + +When the Transform precoder indicator field is present, if the bit width of PTRS-DMRS association field for the case with transform precoder enabled is not equal to that for the case with transform precoder disabled, a number of most significant bits with value set to '0' are inserted to the PTRS-DMRS association field for the case with smaller bit width until the bit width of the PTRS-DMRS association field for the two cases are the same. + +- Second PTRS-DMRS association - 2 bits if PTRS-DMRS association field and SRS resource set indicator field are present and *maxRank*>2 and *multipanelScheme* is not configured; 0 bit otherwise. Tables 7.3.1.1.2-25 and 7.3.1.1.2-26 are used to indicate the association between PTRS port(s) and DMRS port(s) corresponding to Second SRS resource indicator field and/or Second precoding information field when one PTRS port and two PTRS ports are configured by *maxNrofPorts* in *PTRS-UplinkConfig* respectively, and the DMRS ports are indicated by the Antenna ports field. + +- beta\_offset indicator - 0 if the higher layer parameter *betaOffsets* = *semiStatic*; otherwise 2 bits as defined by Table 9.3-3 in [5, TS 38.213]. + +When two HARQ-ACK codebooks are configured by *pdsch-HARQ-ACK-CodebookList* or by *pdsch-HARQ-ACK-CodebookListMulticast* for the same serving cell and if higher layer parameter *priorityIndicatorDCI-0-1* is configured, if the bit width of the beta\_offset indicator in DCI format 0\_1 for one HARQ-ACK codebook is not equal to that of the beta\_offset indicator in DCI format 0\_1 for the other HARQ-ACK codebook, a number of most significant bits with value set to '0' are inserted to smaller beta\_offset indicator until the bit width of the beta\_offset indicator in DCI format 0\_1 for the two HARQ-ACK codebooks are the same. + +- DMRS sequence initialization – 0 bit if transform precoder is enabled by higher layers and the Transform precoder indicator field is not present; 1 bit if transform precoder is disabled by higher layers or if the Transform precoder indicator field is present. If the Transform precoder indicator field is present and set to '0', the bit is reserved. +- UL-SCH indicator - 0 or 1 bit as follows + - 0 bit if the number of scheduled PUSCH indicated by the Time domain resource assignment field is larger than 1; + - 1 bit otherwise. A value of "1" indicates UL-SCH shall be transmitted on the PUSCH and a value of "0" indicates UL-SCH shall not be transmitted on the PUSCH. If a UE does not support triggering SRS only in DCI, except for DCI format 0\_1 with CRC scrambled by SP-CSI-RNTI, the UE is not expected to receive a DCI format 0\_1 with UL-SCH indicator of "0" and CSI request of all zero(s). If a UE supports triggering SRS only in DCI, except for DCI format 0\_1 with CRC scrambled by SP-CSI-RNTI, the UE is not expected to receive a DCI format 0\_1 with UL-SCH indicator of "0", CSI request of all zero(s) and SRS request of all zero(s). The UE is not expected to receive a DCI format 0\_1 with UL-SCH indicator of "0", when the indicated number of layers is larger than 4. +- ChannelAccess-CPext-CAPC - 0, 1, 2, 3, 4, 5 or 6 bits. The bitwidth for this field is determined as *I* bits, where *I* is the number of entries in the higher layer parameter *ul-AccessConfigListDCI-0-1* or in Table 7.3.1.1.1-4A if *channelAccessMode-r16* = "*semiStatic*" is provided, for operation in a cell with shared spectrum channel access in frequency range 1, or for operation in frequency range 2-2 if *ChannelAccessMode2-r17* is provided; otherwise 0 bit. One or more entries from Table 7.3.1.1.2-35 or Table 7.3.1.1.2-35A are configured by the higher layer parameter *ul-AccessConfigListDCI-0-1*. +- Open-loop power control parameter set indication - 0 or 1 or 2 bits. + - 0 bit if the higher layer parameter *p0-PUSCH-SetList* is not configured; + - 1 or 2 bits otherwise, + - 1 bit if SRS resource indicator is present in the DCI format 0\_1; + - 1 or 2 bits as determined by higher layer parameter *olpc-ParameterSetDCI-0-1* if SRS resource indicator is not present in the DCI format 0\_1. +- Priority indicator - 0 bit if higher layer parameter *priorityIndicatorDCI-0-1* is not configured; otherwise 1 bit as defined in Clause 9 in [5, TS 38.213]. +- Invalid symbol pattern indicator - 0 bit if higher layer parameter *invalidSymbolPatternIndicatorDCI-0-1* is not configured; otherwise 1 bit as defined in Clause 6.1.2.1 in [6, TS 38.214]. +- Minimum applicable scheduling offset indicator - 0 or 1 bit + - 0 bit if higher layer parameter *minimumSchedulingOffsetK2* is not configured; + - 1 bit if higher layer parameter *minimumSchedulingOffsetK2* is configured. The 1 bit indication is used to determine the minimum applicable K2 for the active UL BWP and the minimum applicable K0 value for the active DL BWP, if configured respectively, according to Table 7.3.1.1.2-33. If the minimum applicable K0 is indicated, the minimum applicable value of the aperiodic CSI-RS triggering offset for an active DL BWP shall be the same as the minimum applicable K0 value. +- SCell dormancy indication - 0 bit if higher layer parameter *dormancyGroupWithinActiveTime* is not configured; otherwise 1, 2, 3, 4 or 5 bits bitmap determined according to the number of different *DormancyGroupID(s)* provided by higher layer parameter *dormancyGroupWithinActiveTime*, where each bit corresponds to one of the SCell group(s) configured by higher layers parameter *dormancyGroupWithinActiveTime*, with MSB to LSB of the bitmap corresponding to the first to last configured SCell group in ascending order of *DormancyGroupID*. The field is only present when this format is carried by PDCCH on the primary cell within DRX Active Time and the UE is configured with at least two DL BWPs for an SCell. +- Sidelink assignment index - 0, 1 or 2 bits: + +- 1 bit if the UE is configured with *pdsch-HARQ-ACK-Codebook = semi-static* and, in addition, the UE is configured with a SL configured grant type 1 or to monitor DCI format 3\_0 with CRC scrambled by SL-RNTI or SL-CS-RNTI; +- 2 bits if the UE is configured with *pdsch-HARQ-ACK-Codebook = dynamic* and, in addition, the UE is configured with a SL configured grant type 1 or to monitor DCI format 3\_0 with CRC scrambled by SL-RNTI or SL-CS-RNTI; +- 0 bit otherwise. +- PDCCH monitoring adaptation indication - 0, 1 or 2 bits + - 1 or 2 bits, if *searchSpaceGroupIdList-r17* is not configured and if *pdcch-SkippingDurationList* is configured + - 1 bit if the UE is configured with only one duration by *pdcch-SkippingDurationList*; + - 2 bits if the UE is configured with more than one duration by *pdcch-SkippingDurationList*. + - 1 or 2 bits, if *pdcch-SkippingDurationList* is not configured and if *searchSpaceGroupIdList-r17* is configured + - 1 bit if the UE is configured by *searchSpaceGroupIdList-r17* with search space set(s) with group index 0 and search space set(s) with group index 1, and if the UE is not configured by *searchSpaceGroupIdList-r17* with any search space set with group index 2; + - 2 bits if the UE is configured by *searchSpaceGroupIdList-r17* with search space set(s) with group index 0, search space set(s) with group index 1 and search space set(s) with group index 2; + - 2 bits, if *pdcch-SkippingDurationList* is configured and if *searchSpaceGroupIdList-r17* is configured + - 0 bit, otherwise + +A UE does not expect that the bit width of a field in DCI format 0\_1 with CRC scrambled by CS-RNTI is larger than corresponding bit width of same field in DCI format 0\_1 with CRC scrambled by C-RNTI for the same serving cell. If the bit width of a field in the DCI format 0\_1 with CRC scrambled by CS-RNTI is not equal to that of the corresponding field in the DCI format 0\_1 with CRC scrambled by C-RNTI for the same serving cell, a number of most significant bits with value set to '0' are inserted to the field in DCI format 0\_1 with CRC scrambled by CS-RNTI until the bit width equals that of the corresponding field in the DCI format 0\_1 with CRC scrambled by C-RNTI for the same serving cell. + +If the number of information bits in DCI format 0\_1 scheduling a single PUSCH prior to padding is not equal to the number of information bits in DCI format 0\_1 scheduling multiple PUSCHs for the same serving cell, zeros shall be appended to the DCI format 0\_1 with smaller size until the payload size is the same for scheduling a single PUSCH and multiple PUSCHs. + +For a UE configured with scheduling on the primary cell from an SCell, if prior to padding the number of information bits in DCI format 0\_1 carried by PDCCH on the primary cell is not equal to the number of information bits in DCI format 0\_1 carried by PDCCH on the SCell for scheduling on the primary cell, zeros shall be appended to the DCI format 0\_1 with smaller size until the payload size is the same. + +- If application of step 4C in clause 7.3.1.0 results in additional zero padding for DCI format 0\_1 for scheduling on the primary cell, corresponding zeros shall be appended to both DCI format 0\_1 monitored on the primary cell and DCI format 0\_1 monitored on the SCell for scheduling on the primary cell. +- If the SCell is deactivated and *firstActiveDownlinkBWP-Id* is not set to dormant BWP, the UE determines the number of information bits in DCI format 0\_1 carried by PDCCH on the primary cell based on a DL BWP provided by *firstActiveDownlinkBWP-Id* for the SCell. If the active DL BWP of the SCell is a dormant DL BWP, or if the SCell is deactivated and *firstActiveDownlinkBWP-Id* is set to dormant BWP, the UE determines the number of information bits in DCI format 0\_1 carried by PDCCH on the primary cell based on a DL BWP provided by *firstWithinActiveTimeBWP-Id* for the SCell if provided; otherwise, based on a DL BWP provided by *firstOutsideActiveTimeBWP-Id* for the SCell. + +**Table 7.3.1.1.2-1: Bandwidth part indicator** + +| Value of BWP indicator field | Bandwidth part | +|------------------------------|--------------------------------| +| 2 bits | | +| 00 | Configured BWP with BWP-Id = 1 | +| 01 | Configured BWP with BWP-Id = 2 | +| 10 | Configured BWP with BWP-Id = 3 | +| 11 | Configured BWP with BWP-Id = 4 | + +**Table 7.3.1.1.2-2: Precoding information and number of layers or Second Precoding information, for 4 antenna ports, if transform precoder is disabled, $\max\text{Rank} = 2$ or $3$ or $4$ or $\max\{\max\text{Rank}, \max\text{RankSfn}\} = 2$ or $3$ or $4$ or $\max\{\max\text{Rank}, \max\text{RankSdm}\} = 2$ or $3$ or $4$ or $\max\text{RankSdm} = 2$ , and *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*** + +| Bit field mapped to index | codebookSubset = fullyAndPartialAndNonCoherent | Bit field mapped to index | codebookSubset = partialAndNonCoherent | Bit field mapped to index | codebookSubset = nonCoherent | +|---------------------------|-------------------------------------------------------|---------------------------|-----------------------------------------------|---------------------------|-------------------------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| 1 | 1 layer: TPMI=1 | 1 | 1 layer: TPMI=1 | 1 | 1 layer: TPMI=1 | +| ... | ... | ... | ... | ... | ... | +| 3 | 1 layer: TPMI=3 | 3 | 1 layer: TPMI=3 | 3 | 1 layer: TPMI=3 | +| 4 | 2 layers: TPMI=0 | 4 | 2 layers: TPMI=0 | 4 | 2 layers: TPMI=0 | +| ... | ... | ... | ... | ... | ... | +| 9 | 2 layers: TPMI=5 | 9 | 2 layers: TPMI=5 | 9 | 2 layers: TPMI=5 | +| 10 | 3 layers: TPMI=0 | 10 | 3 layers: TPMI=0 | 10 | 3 layers: TPMI=0 | +| 11 | 4 layers: TPMI=0 | 11 | 4 layers: TPMI=0 | 11 | 4 layers: TPMI=0 | +| 12 | 1 layer: TPMI=4 | 12 | 1 layer: TPMI=4 | 12-15 | reserved | +| ... | ... | ... | ... | | | +| 19 | 1 layer: TPMI=11 | 19 | 1 layer: TPMI=11 | | | +| 20 | 2 layers: TPMI=6 | 20 | 2 layers: TPMI=6 | | | +| ... | ... | ... | ... | | | +| 27 | 2 layers: TPMI=13 | 27 | 2 layers: TPMI=13 | | | +| 28 | 3 layers: TPMI=1 | 28 | 3 layers: TPMI=1 | | | +| 29 | 3 layers: TPMI=2 | 29 | 3 layers: TPMI=2 | | | +| 30 | 4 layers: TPMI=1 | 30 | 4 layers: TPMI=1 | | | +| 31 | 4 layers: TPMI=2 | 31 | 4 layers: TPMI=2 | | | +| 32 | 1 layers: TPMI=12 | | | | | +| ... | ... | | | | | +| 47 | 1 layers: TPMI=27 | | | | | +| 48 | 2 layers: TPMI=14 | | | | | +| ... | ... | | | | | +| 55 | 2 layers: TPMI=21 | | | | | +| 56 | 3 layers: TPMI=3 | | | | | +| ... | ... | | | | | +| 59 | 3 layers: TPMI=6 | | | | | +| 60 | 4 layers: TPMI=3 | | | | | +| 61 | 4 layers: TPMI=4 | | | | | +| 62-63 | reserved | | | | | + +**Table 7.3.1.1.2-2A: Precoding information and number of layers for 4 antenna ports or Second Precoding information,, if transform precoder is disabled, $\max\text{Rank} = 2$ or $\max\{\max\text{Rank}, \max\text{RankSfn}\} = 2$ or $\max\{\max\text{Rank}, \max\text{RankSdm}\} = 2$ or $\max\text{RankSdm} = 2$ , and $\text{ul-FullPowerTransmission} = \text{fullpowerMode1}$** + +| Bit field mapped to index | codebookSubset = partialAndNonCoherent | Bit field mapped to index | codebookSubset= nonCoherent | +|---------------------------|-----------------------------------------------|---------------------------|------------------------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| 1 | 1 layer: TPMI=1 | 1 | 1 layer: TPMI=1 | +| ... | ... | ... | ... | +| 3 | 1 layer: TPMI=3 | 3 | 1 layer: TPMI=3 | +| 4 | 2 layers: TPMI=0 | 4 | 2 layers: TPMI=0 | +| ... | ... | ... | ... | +| 9 | 2 layers: TPMI=5 | 9 | 2 layers: TPMI=5 | +| 10 | 1 layer: TPMI=13 | 10 | 1 layer: TPMI=13 | +| 11 | 2 layer: TPMI=6 | 11 | 2 layer: TPMI=6 | +| 12 | 1 layer: TPMI=4 | 12-15 | Reserved | +| ... | ... | | | +| 20 | 1 layer: TPMI=12 | | | +| 21 | 1 layer: TPMI=14 | | | +| 22 | 1 layer: TPMI=15 | | | +| 23 | 2 layers: TPMI=7 | | | +| ... | ... | | | +| 29 | 2 layers: TPMI=13 | | | +| 30-31 | Reserved | | | + +**Table 7.3.1.1.2-2B: Precoding information and number of layers for 4 antenna ports, if transform precoder is disabled, $\max\text{Rank} = 3$ or 4, and $\text{ul-FullPowerTransmission} = \text{fullpowerMode1}$** + +| Bit field mapped to index | codebookSubset = partialAndNonCoherent | Bit field mapped to index | codebookSubset= nonCoherent | +|---------------------------|-----------------------------------------------|---------------------------|------------------------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| 1 | 1 layer: TPMI=1 | 1 | 1 layer: TPMI=1 | +| ... | ... | ... | ... | +| 3 | 1 layer: TPMI=3 | 3 | 1 layer: TPMI=3 | +| 4 | 2 layers: TPMI=0 | 4 | 2 layers: TPMI=0 | +| ... | ... | ... | ... | +| 9 | 2 layers: TPMI=5 | 9 | 2 layers: TPMI=5 | +| 10 | 3 layers: TPMI=0 | 10 | 3 layers: TPMI=0 | +| 11 | 4 layers: TPMI=0 | 11 | 4 layers: TPMI=0 | +| 12 | 1 layer: TPMI=13 | 12 | 1 layer: TPMI=13 | +| 13 | 2 layer: TPMI=6 | 13 | 2 layer: TPMI=6 | +| 14 | 3 layer: TPMI=1 | 14 | 3 layer: TPMI=1 | +| 15 | 1 layer: TPMI=4 | 15 | Reserved | +| ... | ... | | | +| 23 | 1 layer: TPMI=12 | | | +| 24 | 1 layer: TPMI=14 | | | +| 25 | 1 layer: TPMI=15 | | | +| 26 | 2 layers: TPMI=7 | | | +| ... | ... | | | +| 32 | 2 layers: TPMI=13 | | | +| 33 | 3 layers: TPMI=2 | | | +| 34 | 4 layers: TPMI=1 | | | +| 35 | 4 layers: TPMI=2 | | | +| 36-63 | Reserved | | | + +**Table 7.3.1.1.2-2C: Second precoding information, for 4 antenna ports, if transform precoder is disabled, *maxRank* = 2 or 3 or 4 or *maxRankSfn* = 2, and *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*** + +| Bit field mapped to index | codebookSubset = fullyAndPartialAndNonCoherent | Bit field mapped to index | codebookSubset = partialAndNonCoherent | Bit field mapped to index | codebookSubset = nonCoherent | +|---------------------------|--------------------------------------------------------------|---------------------------|------------------------------------------------------|---------------------------|--------------------------------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| ... | ... | ... | ... | ... | ... | +| 27 | 1 layer: TPMI=27 | 11 | 1 layer: TPMI=11 | 3 | 1 layer: TPMI=3 | +| 28-31 | 1 layer: reserved | 12-15 | 1 layer: reserved | 4-7 | 1 layer: reserved | +| 0 | 2 layers: TPMI=0 | 0 | 2 layers: TPMI=0 | 0 | 2 layers: TPMI=0 | +| ... | ... | ... | ... | ... | ... | +| 21 | 2 layers: TPMI=21 | 13 | 2 layers: TPMI=13 | 5 | 2 layers: TPMI=5 | +| 22-31 | 2 layers: reserved | 14-15 | 2 layers: reserved | 6-7 | 2 layers: reserved | +| 0 | 3 layers: TPMI=0 | 0 | 3 layers: TPMI=0 | 0 | 3 layers: TPMI=0 | +| ... | ... | ... | ... | 1-7 | 3 layers: reserved | +| 6 | 3 layers: TPMI=6 | 2 | 3 layers: TPMI=2 | 0 | 4 layers: TPMI=0 | +| 7-31 | 3 layers: reserved | 3-15 | 3 layers: reserved | 1-7 | 4 layers: reserved | +| 0 | 4 layers: TPMI=0 | 0 | 4 layers: TPMI=0 | | | +| ... | ... | ... | ... | | | +| 4 | 4 layers: TPMI=4 | 2 | 4 layers: TPMI=2 | | | +| 5-31 | 4 layers: reserved | 3-15 | 4 layers: reserved | | | + +**Table 7.3.1.1.2-2D: Second precoding information for 4 antenna ports, if transform precoder is disabled, *maxRank* = 2 or *maxRankSfn* = 2, and *ul-FullPowerTransmission* = *fullpowerMode1*** + +| Bit field mapped to index | codebookSubset = partialAndNonCoherent | Bit field mapped to index | codebookSubset = nonCoherent | +|---------------------------|------------------------------------------------------|---------------------------|--------------------------------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| ... | ... | ... | ... | +| 14 | 1 layer: TPMI=14 | 3 | 1 layer: TPMI=3 | +| 15 | 1 layer: TPMI=15 | 4 | 1 layer: TPMI=13 | +| 0 | 2 layers: TPMI=0 | 5-7 | 1 layer: reserved | +| ... | ... | 0 | 2 layers: TPMI=0 | +| 13 | 2 layers: TPMI=13 | ... | ... | +| 14-15 | 2 layers: reserved | 6 | 2 layers: TPMI=6 | +| | | 7 | 2 layers: reserved | + +**Table 7.3.1.1.2-2E: Second precoding information for 4 antenna ports, if transform precoder is disabled, *maxRank* = 3 or 4, and *ul-FullPowerTransmission* = *fullpowerMode1*** + +| Bit field mapped to index | codebookSubset = partialAndNonCoherent | Bit field mapped to index | codebookSubset = nonCoherent | +|---------------------------|------------------------------------------------------|---------------------------|--------------------------------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| ... | ... | ... | ... | +| 14 | 1 layer: TPMI=14 | 3 | 1 layer: TPMI=3 | +| 15 | 1 layer: TPMI=15 | 4 | 1 layer: TPMI=13 | +| 0 | 2 layers: TPMI=0 | 5-7 | 1 layer: reserved | +| ... | ... | 0 | 2 layers: TPMI=0 | +| 13 | 2 layers: TPMI=13 | ... | ... | +| 14-15 | 2 layers: reserved | 6 | 2 layers: TPMI=6 | +| 0 | 3 layers: TPMI=0 | 7 | 2 layers: reserved | +| ... | ... | 0 | 3 layers: TPMI=0 | +| 2 | 3 layers: TPMI=2 | 1 | 3 layer: TPMI=1 | +| 3-15 | 3 layers: reserved | 2-7 | 3 layers: reserved | +| 0 | 4 layers: TPMI=0 | 0 | 4 layers: TPMI=0 | +| ... | ... | 1-7 | 4 layers: reserved | +| 2 | 4 layers: TPMI=2 | | | +| 3-15 | 4 layers: reserved | | | + +**Table 7.3.1.1.2-3: Precoding information and number of layers or Second Precoding information, for 4 antenna ports, if transform precoder is enabled and *ul-FullPowerTransmission* is either not configured or configured to *fullpowerMode2* or configured to *fullpower*, or if transform precoder is disabled, *maxRank* = 1 or $\max\{\maxRank, \maxRankSfn\} = 1$ or $\max\{\maxRank, \maxRankSdm\} = 1$ or *maxRankSdm* = 1 or *maxRankSfn* = 1, and *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*** + +| Bit field mapped to index | codebookSubset = fullyAndPartialAndNonCoherent | Bit field mapped to index | codebookSubset= partialAndNonCoherent | Bit field mapped to index | codebookSubset= nonCoherent | +|---------------------------|-------------------------------------------------------|---------------------------|----------------------------------------------|---------------------------|------------------------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| 1 | 1 layer: TPMI=1 | 1 | 1 layer: TPMI=1 | 1 | 1 layer: TPMI=1 | +| ... | ... | ... | ... | ... | ... | +| 3 | 1 layer: TPMI=3 | 3 | 1 layer: TPMI=3 | 3 | 1 layer: TPMI=3 | +| 4 | 1 layer: TPMI=4 | 4 | 1 layer: TPMI=4 | | | +| ... | ... | ... | ... | | | +| 11 | 1 layer: TPMI=11 | 11 | 1 layer: TPMI=11 | | | +| 12 | 1 layers: TPMI=12 | 12-15 | reserved | | | +| ... | ... | | | | | +| 27 | 1 layers: TPMI=27 | | | | | +| 28-31 | reserved | | | | | + +**Table 7.3.1.1.2-3A: Precoding information and number of layers or Second Precoding information, for 4 antenna ports, if transform precoder is enabled and *ul-FullPowerTransmission* = *fullpowerMode1*, or if transform precoder is disabled, *maxRank* = 1 or $\max\{\maxRank, \maxRankSfn\} = 1$ or $\max\{\maxRank, \maxRankSdm\} = 1$ or *maxRankSdm* = 1 or *maxRankSfn* = 1, and *ul-FullPowerTransmission* = *fullpowerMode1*** + +| Bit field mapped to index | codebookSubset= partialAndNonCoherent | Bit field mapped to index | codebookSubset= nonCoherent | +|---------------------------|----------------------------------------------|---------------------------|------------------------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| 1 | 1 layer: TPMI=1 | 1 | 1 layer: TPMI=1 | +| ... | ... | ... | ... | +| 3 | 1 layer: TPMI=3 | 3 | 1 layer: TPMI=3 | +| 4 | 1 layer: TPMI=13 | 4 | 1 layer: TPMI=13 | +| 5 | 1 layer: TPMI=4 | 5-7 | Reserved | +| ... | ... | | | +| 13 | 1 layer: TPMI=12 | | | +| 14 | 1 layer: TPMI=14 | | | +| 15 | 1 layer: TPMI=15 | | | + +**Table 7.3.1.1.2-4: Precoding information and number of layers or Second Precoding information, for 2 antenna ports, if transform precoder is disabled, *maxRank* = 2 or $\max\{\maxRank, \maxRankSfn\} = 2$ or $\max\{\maxRank, \maxRankSdm\} = 2$ or *maxRankSdm* = 2, and *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*** + +| Bit field mapped to index | codebookSubset = fullyAndPartialAndNonCoherent | Bit field mapped to index | codebookSubset = nonCoherent | +|---------------------------|-------------------------------------------------------|---------------------------|-------------------------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| 1 | 1 layer: TPMI=1 | 1 | 1 layer: TPMI=1 | +| 2 | 2 layers: TPMI=0 | 2 | 2 layers: TPMI=0 | +| 3 | 1 layer: TPMI=2 | 3 | reserved | +| 4 | 1 layer: TPMI=3 | | | +| 5 | 1 layer: TPMI=4 | | | +| 6 | 1 layer: TPMI=5 | | | +| 7 | 2 layers: TPMI=1 | | | +| 8 | 2 layers: TPMI=2 | | | +| 9-15 | reserved | | | + +**Table 7.3.1.1.2-4A: Precoding information and number of layers or Second Precoding information, for 2 antenna ports, if transform precoder is disabled, $\max\text{Rank} = 2$ or $\max\{\max\text{Rank}, \max\text{RankSfn}\} = 2$ or $\max\{\max\text{Rank}, \max\text{RankSdm}\} = 2$ or $\max\text{RankSdm} = 2$ , and $\text{ul-FullPowerTransmission} = \text{fullpowerMode1}$** + +| Bit field mapped to index | codebookSubset= nonCoherent | +|---------------------------|------------------------------------| +| 0 | 1 layer: TPMI=0 | +| 1 | 1 layer: TPMI=1 | +| 2 | 2 layers: TPMI=0 | +| 3 | 1 layer: TPMI=2 | + +**Table 7.3.1.1.2-4B: Second precoding information, for 2 antenna ports, if transform precoder is disabled, $\max\text{Rank} = 2$ or $\max\text{RankSfn} = 2$ , and $\text{ul-FullPowerTransmission}$ is not configured or configured to *fullpowerMode2* or configured to *fullpower*** + +| Bit field mapped to index | codebookSubset = fullyAndPartialAndNonCoherent | Bit field mapped to index | codebookSubset = nonCoherent | +|---------------------------|-------------------------------------------------------|---------------------------|-------------------------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| 1 | 1 layer: TPMI=1 | 1 | 1 layer: TPMI=1 | +| ... | ... | 0 | 2 layers: TPMI=0 | +| 5 | 1 layer: TPMI=5 | 1 | 2 layers: reserved | +| 6-7 | 1 layer: reserved | | | +| 0 | 2 layers: TPMI=0 | | | +| ... | ... | | | +| 2 | 2 layers: TPMI=2 | | | +| 3-7 | 2 layers: reserved | | | + +**Table 7.3.1.1.2-4C: Second precoding information, for 2 antenna ports, if transform precoder is disabled, $\max\text{Rank} = 2$ or $\max\text{RankSfn} = 2$ , and $\text{ul-FullPowerTransmission} = \text{fullpowerMode1}$** + +| Bit field mapped to index | codebookSubset= nonCoherent | +|---------------------------|------------------------------------| +| 0 | 1 layer: TPMI=0 | +| ... | ... | +| 2 | 1 layer: TPMI=2 | +| 3 | 1 layer: reserved | +| 0 | 2 layers: TPMI=0 | +| 1-3 | 2 layers: reserved | + +**Table 7.3.1.1.2-5: Precoding information and number of layers or Second Precoding information, for 2 antenna ports, if transform precoder is enabled and $\text{ul-FullPowerTransmission}$ is not configured or configured to *fullpowerMode2* or configured to *fullpower*, or if transform precoder is disabled, $\max\text{Rank} = 1$ or $\max\{\max\text{Rank}, \max\text{RankSfn}\} = 1$ or $\max\{\max\text{Rank}, \max\text{RankSdm}\} = 1$ or $\max\text{RankSdm} = 1$ or $\max\text{RankSfn} = 1$ , and $\text{ul-FullPowerTransmission}$ is not configured or configured to *fullpowerMode2* or configured to *fullpower*** + +| Bit field mapped to index | codebookSubset = fullyAndPartialAndNonCoherent | Bit field mapped to index | codebookSubset = nonCoherent | +|---------------------------|-------------------------------------------------------|---------------------------|-------------------------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| 1 | 1 layer: TPMI=1 | 1 | 1 layer: TPMI=1 | +| 2 | 1 layer: TPMI=2 | | | +| 3 | 1 layer: TPMI=3 | | | +| 4 | 1 layer: TPMI=4 | | | +| 5 | 1 layer: TPMI=5 | | | +| 6-7 | reserved | | | + +**Table 7.3.1.1.2-5A: Precoding information and number of layers or Second Precoding information, for 2 antenna ports or Second Precoding information, if transform precoder is enabled and *ul-FullPowerTransmission = fullpowerMode1*, or if transform precoder is disabled, *maxRank = 1* or *max{maxRank, maxRankSfn} = 1* or *max{maxRank, maxRankSdm} = 1* or *maxRankSdm = 1* or *maxRankSfn = 1*, and *ul-FullPowerTransmission = fullpowerMode1*** + +| Bit field mapped to index | codebookSubset= nonCoherent | +|---------------------------|------------------------------------| +| 0 | 1 layer: TPMI=0 | +| 1 | 1 layer: TPMI=1 | +| 2 | 1 layer: TPMI=2 | +| 3 | Reserved | + +**Table 7.3.1.1.2-5B: Precoding information and number of layers, for 8 antenna ports, if transform precoder is disabled, *maxRank = 8*, and *CodebookType=Codebook1*** + +| Bit field mapped to index | ULcodebookFC-N1N2 = (4, 1) | Bit field mapped to index | ULcodebookFC-N1N2 = (2, 2) | +|---------------------------|-----------------------------------|---------------------------|-----------------------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| 1 | 1 layer: TPMI=1 | 1 | 1 layer: TPMI=1 | +| ... | ... | ... | ... | +| 15 | 1 layer: TPMI=15 | 15 | 1 layer: TPMI=15 | +| 16 | 2 layers: TPMI=0 | 16 | 2 layer2: TPMI=0 | +| 17 | 2 layers: TPMI=1 | 17 | 2 layer2: TPMI=1 | +| ... | ... | ... | ... | +| 47 | 2 layers: TPMI=31 | 47 | 2 layers: TPMI=31 | +| 48 | 3 layers: TPMI=0 | 48 | 3 layers: TPMI=0 | +| 49 | 3 layers: TPMI=1 | 49 | 3 layers: TPMI=1 | +| ... | ... | ... | ... | +| 71 | 3 layers: TPMI=23 | 71 | 3 layers: TPMI=23 | +| 72 | 4 layers: TPMI=0 | 72 | 4 layers: TPMI=0 | +| 73 | 4 layers: TPMI=1 | 73 | 4 layers: TPMI=1 | +| ... | ... | ... | ... | +| 95 | 4 layers: TPMI=23 | 95 | 4 layers: TPMI=23 | +| 96 | 5 layers: TPMI=0 | 96 | 5 layers: TPMI=0 | +| 97 | 5 layers: TPMI=1 | 97 | 5 layers: TPMI=1 | +| ... | ... | ... | ... | +| 103 | 5 layers: TPMI=7 | 103 | 5 layers: TPMI=7 | +| 104 | 6 layers: TPMI=0 | 104 | 6 layers: TPMI=0 | +| 105 | 6 layers: TPMI=1 | 105 | 6 layers: TPMI=1 | +| ... | ... | ... | ... | +| 111 | 6 layers: TPMI=7 | 111 | 6 layers: TPMI=7 | +| 112 | 7 layers: TPMI=0 | 112 | 7 layers: TPMI=0 | +| 113 | 7 layers: TPMI=1 | 113 | 7 layers: TPMI=1 | +| ... | ... | ... | ... | +| 115 | 7 layers: TPMI=3 | 119 | 7 layers: TPMI=7 | +| 116 | 8 layers: TPMI=0 | 120 | 8 layers: TPMI=0 | +| 117 | 8 layers: TPMI=1 | 121 | 8 layers: TPMI=1 | +| ... | ... | ... | ... | +| 119 | 8 layers: TPMI=3 | 127 | 8 layers: TPMI=7 | +| 120-127 | reserved | | | + +**Table 7.3.1.1.2-5C: Precoding information and number of layers, for 8 antenna ports, if transform precoder is disabled, *maxRank* = 7, and *CodebookType*=*Codebook1*** + +| Bit field mapped to index | ULcodebookFC-N1N2 = (4, 1) | Bit field mapped to index | ULcodebookFC-N1N2 = (2, 2) | +|---------------------------|-----------------------------------|---------------------------|-----------------------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| 1 | 1 layer: TPMI=1 | 1 | 1 layer: TPMI=1 | +| ... | ... | ... | ... | +| 15 | 1 layer: TPMI=15 | 15 | 1 layer: TPMI=15 | +| 16 | 2 layers: TPMI=0 | 16 | 2 layer2: TPMI=0 | +| 17 | 2 layers: TPMI=1 | 17 | 2 layer2: TPMI=1 | +| ... | ... | ... | ... | +| 47 | 2 layers: TPMI=31 | 47 | 2 layers: TPMI=31 | +| 48 | 3 layers: TPMI=0 | 48 | 3 layers: TPMI=0 | +| 49 | 3 layers: TPMI=1 | 49 | 3 layers: TPMI=1 | +| ... | ... | ... | ... | +| 71 | 3 layers: TPMI=23 | 71 | 3 layers: TPMI=23 | +| 72 | 4 layers: TPMI=0 | 72 | 4 layers: TPMI=0 | +| 73 | 4 layers: TPMI=1 | 73 | 4 layers: TPMI=1 | +| ... | ... | ... | ... | +| 95 | 4 layers: TPMI=23 | 95 | 4 layers: TPMI=23 | +| 96 | 5 layers: TPMI=0 | 96 | 5 layers: TPMI=0 | +| 97 | 5 layers: TPMI=1 | 97 | 5 layers: TPMI=1 | +| ... | ... | ... | ... | +| 103 | 5 layers: TPMI=7 | 103 | 5 layers: TPMI=7 | +| 104 | 6 layers: TPMI=0 | 104 | 6 layers: TPMI=0 | +| 105 | 6 layers: TPMI=1 | 105 | 6 layers: TPMI=1 | +| ... | ... | ... | ... | +| 111 | 6 layers: TPMI=7 | 111 | 6 layers: TPMI=7 | +| 112 | 7 layers: TPMI=0 | 112 | 7 layers: TPMI=0 | +| 113 | 7 layers: TPMI=1 | 113 | 7 layers: TPMI=1 | +| ... | ... | ... | ... | +| 115 | 7 layers: TPMI=3 | 119 | 7 layers: TPMI=7 | +| 116-127 | reserved | 120-127 | reserved | + +**Table 7.3.1.1.2-5D: Precoding information and number of layers, for 8 antenna ports, if transform precoder is disabled, *maxRank* = 4, 5 or 6, *CodebookType*=*Codebook1*, *ULcodebookFC-N1N2* = (4,1) or (2,2)** + +| Bit field mapped to index | maxRank =4 | Bit field mapped to index | maxRank =5 | Bit field mapped to index | maxRank =6 | +|---------------------------|-------------------|---------------------------|-------------------|---------------------------|-------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| 1 | 1 layer: TPMI=1 | 1 | 1 layer: TPMI=1 | 1 | 1 layer: TPMI=1 | +| ... | ... | ... | ... | ... | ... | +| 15 | 1 layer: TPMI=15 | 15 | 1 layer: TPMI=15 | 15 | 1 layer: TPMI=15 | +| 16 | 2 layers: TPMI=0 | 16 | 2 layers: TPMI=0 | 16 | 2 layer2: TPMI=0 | +| 17 | 2 layers: TPMI=1 | 17 | 2 layers: TPMI=1 | 17 | 2 layer2: TPMI=1 | +| ... | ... | ... | ... | ... | ... | +| 47 | 2 layers: TPMI=31 | 47 | 2 layers: TPMI=31 | 47 | 2 layers: TPMI=31 | +| 48 | 3 layers: TPMI=0 | 48 | 3 layers: TPMI=0 | 48 | 3 layers: TPMI=0 | +| 49 | 3 layers: TPMI=1 | 49 | 3 layers: TPMI=1 | 49 | 3 layers: TPMI=1 | +| ... | ... | ... | ... | ... | ... | +| 71 | 3 layers: TPMI=23 | 71 | 3 layers: TPMI=23 | 71 | 3 layers: TPMI=23 | +| 72 | 4 layers: TPMI=0 | 72 | 4 layers: TPMI=0 | 72 | 4 layers: TPMI=0 | +| 73 | 4 layers: TPMI=1 | 73 | 4 layers: TPMI=1 | 73 | 4 layers: TPMI=1 | +| ... | ... | ... | ... | ... | ... | +| 95 | 4 layers: TPMI=23 | 95 | 4 layers: TPMI=23 | 95 | 4 layers: TPMI=23 | +| 96-127 | reserved | 96 | 5 layers: TPMI=0 | 96 | 5 layers: TPMI=0 | +| | | 97 | 5 layers: TPMI=1 | 97 | 5 layers: TPMI=1 | +| | | ... | ... | ... | ... | +| | | 103 | 5 layers: TPMI=7 | 103 | 5 layers: TPMI=7 | +| | | 104-127 | reserved | 104 | 6 layers: TPMI=0 | +| | | | | 105 | 6 layers: TPMI=1 | +| | | | | ... | ... | +| | | | | 111 | 6 layers: TPMI=7 | +| | | | | 112-127 | reserved | + +**Table 7.3.1.1.2-5E: Precoding information and number of layers, for 8 antenna ports, if transform precoder is enabled or *maxRank*=1 or 2 or 3 if transform precoder is disabled, *CodebookType*=*Codebook1*, *ULcodebookFC-N1N2* = (4,1) or (2,2)** + +| Bit field mapped to index | transform precoder is enabled, or maxRank =1 if transform precoder is disabled | Bit field mapped to index | transform precoder is disabled, and maxRank =2 | Bit field mapped to index | transform precoder is disabled, and maxRank =3 | +|---------------------------|---------------------------------------------------------------------------------------|---------------------------|-------------------------------------------------------|---------------------------|-------------------------------------------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| 1 | 1 layer: TPMI=1 | 1 | 1 layer: TPMI=1 | 1 | 1 layer: TPMI=1 | +| ... | ... | ... | ... | ... | ... | +| 15 | 1 layer: TPMI=15 | 15 | 1 layer: TPMI=15 | 15 | 1 layer: TPMI=15 | +| | | 16 | 2 layer2: TPMI=0 | 16 | 2 layer2: TPMI=0 | +| | | 17 | 2 layer2: TPMI=1 | 17 | 2 layer2: TPMI=1 | +| | | ... | ... | ... | ... | +| | | 47 | 2 layers: TPMI=31 | 47 | 2 layers: TPMI=31 | +| | | 48-63 | reserved | 48 | 3 layers: TPMI=0 | +| | | | | 49 | 3 layers: TPMI=1 | +| | | | | ... | ... | +| | | | | 71 | 3 layers: TPMI=23 | +| | | | | 72-127 | reserved | + +**Table 7.3.1.1.2-5F: Precoding information and number of layers, for 8 antenna ports, if transform precoder is disabled, *maxRank* = 5, 6, 7 or 8, and *CodebookType*=*Codebook4*** + +| Bit field mapped to index | maxRank = 5 | Bit field mapped to index | maxRank = 6 | Bit field mapped to index | maxRank = 7 | Bit field mapped to index | maxRank = 8 | +|---------------------------|-----------------------|---------------------------|-----------------------|---------------------------|-----------------------|---------------------------|-----------------------| +| 0 | 1 layer:
TPMI=0 | 0 | 1 layer:
TPMI=0 | 0 | 1 layer:
TPMI=0 | 0 | 1 layer:
TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 7 | 1 layer:
TPMI=7 | 7 | 1 layer:
TPMI=7 | 7 | 1 layer:
TPMI=7 | 7 | 1 layer:
TPMI=7 | +| 8 | 2 layers:
TPMI=8 | 8 | 2 layers:
TPMI=8 | 8 | 2 layers:
TPMI=8 | 8 | 2 layers:
TPMI=8 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 35 | 2 layers:
TPMI=35 | 35 | 2 layers:
TPMI=35 | 35 | 2 layers:
TPMI=35 | 35 | 2 layers:
TPMI=35 | +| 36 | 3 layers:
TPMI=36 | 36 | 3 layers:
TPMI=36 | 36 | 3 layers:
TPMI=36 | 36 | 3 layers:
TPMI=36 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 91 | 3 layers:
TPMI=91 | 91 | 3 layers:
TPMI=91 | 91 | 3 layers:
TPMI=91 | 91 | 3 layers:
TPMI=91 | +| 92 | 4 layers:
TPMI=92 | 92 | 4 layers:
TPMI=92 | 92 | 4 layers:
TPMI=92 | 92 | 4 layers:
TPMI=92 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 161 | 4 layers:
TPMI=161 | 161 | 4 layers:
TPMI=161 | 161 | 4 layers:
TPMI=161 | 161 | 4 layers:
TPMI=161 | +| 162 | 5 layers:
TPMI=162 | 162 | 5 layers:
TPMI=162 | 162 | 5 layers:
TPMI=162 | 162 | 5 layers:
TPMI=162 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 217 | 5 layers:
TPMI=217 | 217 | 5 layers:
TPMI=217 | 217 | 5 layers:
TPMI=217 | 217 | 5 layers:
TPMI=217 | +| 218-255 | reserved | 218 | 6 layers:
TPMI=218 | 218 | 6 layers:
TPMI=218 | 218 | 6 layers:
TPMI=218 | +| | | ... | ... | ... | ... | ... | ... | +| | | 245 | 6 layers:
TPMI=245 | 245 | 6 layers:
TPMI=245 | 245 | 6 layers:
TPMI=245 | +| | | 246-255 | reserved | 246 | 7 layers:
TPMI=246 | 246 | 7 layers:
TPMI=246 | +| | | | | ... | ... | ... | ... | +| | | | | 253 | 7 layers:
TPMI=253 | 253 | 7 layers:
TPMI=253 | +| | | | | 254-255 | reserved | 254 | 8 layers:
TPMI=254 | +| | | | | | | 255 | reserved | + +**Table 7.3.1.1.2-5G: Precoding information and number of layers, for 8 antenna ports, if transform precoder is disabled, *maxRank* = 2, 3 or 4, *CodebookType*=*Codebook4*, and *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*** + +| Bit field mapped to index | maxRank = 2 | Bit field mapped to index | maxRank = 3 | Bit field mapped to index | maxRank = 4 | +|---------------------------|--------------------|---------------------------|--------------------|---------------------------|--------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| ... | ... | ... | ... | ... | ... | +| 7 | 1 layer: TPMI=7 | 7 | 1 layer: TPMI=7 | 7 | 1 layer: TPMI=7 | +| 8 | 2 layers: TPMI=8 | 8 | 2 layers: TPMI=8 | 8 | 2 layers: TPMI=8 | +| ... | ... | ... | ... | ... | ... | +| 35 | 2 layers: TPMI=35 | 35 | 2 layers: TPMI=35 | 35 | 2 layers: TPMI=35 | +| 36-63 | reserved | 36 | 3 layers: TPMI=36 | 36 | 3 layers: TPMI=36 | +| | | ... | ... | ... | ... | +| | | 91 | 3 layers: TPMI=91 | 91 | 3 layers: TPMI=91 | +| | | 92-127 | reserved | 92 | 4 layers: TPMI=92 | +| | | | | ... | ... | +| | | | | 161 | 4 layers: TPMI=161 | +| | | | | 162-255 | reserved | + +**Table 7.3.1.1.2-5H: Precoding information and number of layers, for 8 antenna ports, if transform precoder is enabled or *maxRank*=1 if transform is disabled, *CodebookType*=*Codebook4*, and *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*** + +| Bit field mapped to index | Precoding information and number of layers | +|---------------------------|--------------------------------------------| +| 0 | 1 layer: TPMI=0 | +| ... | ... | +| 7 | 1 layer: TPMI=7 | + +**Table 7.3.1.1.2-5I: Precoding information and number of layers, for 8 antenna ports, if transform precoder is disabled, *maxRank* = 5, 6, 7 or 8, and *CodebookType*=Codebook2** + +| Bit field mapped to index | maxRank = 5 | Bit field mapped to index | maxRank = 6 | Bit field mapped to index | maxRank = 7 | Bit field mapped to index | maxRank = 8 | +|---------------------------|-----------------------|---------------------------|-----------------------|---------------------------|-----------------------|---------------------------|-----------------------| +| 0 | 1 layer:
TPMI=0 | 0 | 1 layer:
TPMI=0 | 0 | 1 layer:
TPMI=0 | 0 | 1 layer:
TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 31 | 1 layer:
TPMI=31 | 31 | 1 layer:
TPMI=31 | 31 | 1 layer:
TPMI=31 | 31 | 1 layer:
TPMI=31 | +| 32 | 2 layers:
TPMI=0 | 32 | 2 layers:
TPMI=0 | 32 | 2 layers:
TPMI=0 | 32 | 2 layers:
TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 303 | 2 layers:
TPMI=271 | 303 | 2 layers:
TPMI=271 | 303 | 2 layers:
TPMI=271 | 303 | 2 layers:
TPMI=271 | +| 304 | 3 layers:
TPMI=0 | 304 | 3 layers:
TPMI=0 | 304 | 3 layers:
TPMI=0 | 304 | 3 layers:
TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 567 | 3 layers:
TPMI=263 | 567 | 3 layers:
TPMI=263 | 567 | 3 layers:
TPMI=263 | 567 | 3 layers:
TPMI=263 | +| 568 | 4 layers:
TPMI=0 | 568 | 4 layers:
TPMI=0 | 568 | 4 layers:
TPMI=0 | 568 | 4 layers:
TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 635 | 4 layers:
TPMI=67 | 635 | 4 layers:
TPMI=67 | 635 | 4 layers:
TPMI=67 | 635 | 4 layers:
TPMI=67 | +| 636 | 5 layers:
TPMI=0 | 636 | 5 layers:
TPMI=0 | 636 | 5 layers:
TPMI=0 | 636 | 5 layers:
TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 667 | 5 layers:
TPMI=31 | 667 | 5 layers:
TPMI=31 | 667 | 5 layers:
TPMI=31 | 667 | 5 layers:
TPMI=31 | +| 698-1023 | reserved | 668 | 6 layers:
TPMI=0 | 668 | 6 layers:
TPMI=0 | 668 | 6 layers:
TPMI=0 | +| | | ... | ... | ... | ... | ... | ... | +| | | 683 | 6 layers:
TPMI=15 | 683 | 6 layers:
TPMI=15 | 683 | 6 layers:
TPMI=15 | +| | | 684-1023 | reserved | 684 | 7 layers:
TPMI=0 | 684 | 7 layers:
TPMI=0 | +| | | | | ... | ... | ... | ... | +| | | | | 691 | 7 layers:
TPMI=7 | 691 | 7 layers:
TPMI=7 | +| | | | | 692-1023 | reserved | 692 | 8 layers:
TPMI=0 | +| | | | | | | ... | ... | +| | | | | | | 695 | 8 layers:
TPMI=3 | +| | | | | | | 696-1023 | reserved | + +**Table 7.3.1.1.2-5J: Precoding information and number of layers, for 8 antenna ports, if transform precoder is enabled, or *maxRank* = 1, 2, 3 or 4 if transform precoder is disabled, *CodebookType*=*Codebook2*, and *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*** + +| Bit field mapped to index | Transform precoder is enabled, or maxRank = 1 if transform precoder is disabled | Bit field mapped to index | transform precoder is disabled and maxRank = 2 | Bit field mapped to index | transform precoder is disabled and maxRank = 3 | Bit field mapped to index | transform precoder is disabled and maxRank = 4 | +|---------------------------|----------------------------------------------------------------------------------------|---------------------------|-------------------------------------------------------|---------------------------|-------------------------------------------------------|---------------------------|-------------------------------------------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 31 | 1 layer: TPMI=31 | 31 | 1 layer: TPMI=31 | 31 | 1 layer: TPMI=31 | 31 | 1 layer: TPMI=31 | +| | | 32 | 2 layers: TPMI=0 | 32 | 2 layers: TPMI=0 | 32 | 2 layers: TPMI=0 | +| | | ... | ... | ... | ... | ... | ... | +| | | 303 | 2 layers: TPMI=271 | 303 | 2 layers: TPMI=271 | 303 | 2 layers: TPMI=271 | +| | | 303-511 | reserved | 304 | 3 layers: TPMI=0 | 304 | 3 layers: TPMI=0 | +| | | | | ... | ... | ... | ... | +| | | | | 567 | 3 layers: TPMI=263 | 567 | 3 layers: TPMI=263 | +| | | | | 568-1023 | reserved | 568 | 4 layers: TPMI=0 | +| | | | | | | ... | ... | +| | | | | | | 635 | 4 layers: TPMI=67 | +| | | | | | | 636-1023 | reserved | + +**Table 7.3.1.1.2-5K: Precoding information and number of layers, for 8 antenna ports, if transform precoder is disabled, *maxRank* = 5, 6, 7 or 8, and *CodebookType*=*Codebook3*** + +| Bit field mapped to index | maxRank = 5 | Bit field mapped to index | maxRank = 6 | Bit field mapped to index | maxRank = 7 | Bit field mapped to index | maxRank = 8 | +|---------------------------|-----------------------|---------------------------|-----------------------|---------------------------|-----------------------|---------------------------|-----------------------| +| 0 | 1 layer:
TPMI=0 | 0 | 1 layer:
TPMI=0 | 0 | 1 layer:
TPMI=0 | 0 | 1 layer:
TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 15 | 1 layer:
TPMI=15 | 15 | 1 layer:
TPMI=15 | 15 | 1 layer:
TPMI=15 | 15 | 1 layer:
TPMI=15 | +| 16 | 2 layers:
TPMI=0 | 16 | 2 layers:
TPMI=0 | 16 | 2 layers:
TPMI=0 | 16 | 2 layers:
TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 119 | 2 layers:
TPMI=103 | 119 | 2 layers:
TPMI=103 | 119 | 2 layers:
TPMI=103 | 119 | 2 layers:
TPMI=103 | +| 120 | 3 layers:
TPMI=0 | 120 | 3 layers:
TPMI=0 | 120 | 3 layers:
TPMI=0 | 120 | 3 layers:
TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 423 | 3 layers:
TPMI=303 | 423 | 3 layers:
TPMI=303 | 423 | 3 layers:
TPMI=303 | 423 | 3 layers:
TPMI=303 | +| 424 | 4 layers:
TPMI=0 | 424 | 4 layers:
TPMI=0 | 424 | 4 layers:
TPMI=0 | 424 | 4 layers:
TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 703 | 4 layers:
TPMI=279 | 703 | 4 layers:
TPMI=279 | 703 | 4 layers:
TPMI=279 | 703 | 4 layers:
TPMI=279 | +| 704 | 5 layers:
TPMI=0 | 704 | 5 layers:
TPMI=0 | 704 | 5 layers:
TPMI=0 | 704 | 5 layers:
TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 863 | 5 layers:
TPMI=159 | 863 | 5 layers:
TPMI=159 | 863 | 5 layers:
TPMI=159 | 863 | 5 layers:
TPMI=159 | +| 864-1023 | reserved | 864 | 6 layers:
TPMI=0 | 864 | 6 layers:
TPMI=0 | 864 | 6 layers:
TPMI=0 | +| | | ... | ... | ... | ... | ... | ... | +| | | 943 | 6 layers:
TPMI=79 | 943 | 6 layers:
TPMI=79 | 943 | 6 layers:
TPMI=79 | +| | | 944-1023 | reserved | 944 | 7 layers:
TPMI=0 | 944 | 7 layers:
TPMI=0 | +| | | | | ... | ... | ... | ... | +| | | | | 975 | 7 layers:
TPMI=31 | 975 | 7 layers:
TPMI=31 | +| | | | | 976-1023 | reserved | 976 | 8 layers:
TPMI=0 | +| | | | | | | ... | ... | +| | | | | | | 991 | 8 layers:
TPMI=15 | +| | | | | | | 992-1023 | reserved | + +**Table 7.3.1.1.2-5L: Precoding information and number of layers, for 8 antenna ports, if transform precoder is enabled, or *maxRank* = 1, 2, 3 or 4 if transform precoder is disabled, *CodebookType*=*Codebook3*, and *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*** + +| Bit field mapped to index | Transform precoder is enabled, or maxRank = 1 if transform precoder is disabled | Bit field mapped to index | transform precoder is disabled and maxRank = 2 | Bit field mapped to index | transform precoder is disabled and maxRank = 3 | Bit field mapped to index | transform precoder is disabled and maxRank = 4 | +|---------------------------|----------------------------------------------------------------------------------------|---------------------------|-------------------------------------------------------|---------------------------|-------------------------------------------------------|---------------------------|-------------------------------------------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 15 | 1 layer: TPMI=15 | 15 | 1 layer: TPMI=15 | 15 | 1 layer: TPMI=15 | 15 | 1 layer: TPMI=15 | +| | | 16 | 2 layers: TPMI=0 | 16 | 2 layers: TPMI=0 | 16 | 2 layers: TPMI=0 | +| | | ... | ... | ... | ... | ... | ... | +| | | 119 | 2 layers: TPMI=103 | 119 | 2 layers: TPMI=103 | 119 | 2 layers: TPMI=103 | +| | | 119-127 | reserved | 120 | 3 layers: TPMI=0 | 120 | 3 layers: TPMI=0 | +| | | | | ... | ... | ... | ... | +| | | | | 423 | 3 layers: TPMI=303 | 423 | 3 layers: TPMI=303 | +| | | | | 424-511 | reserved | 424 | 4 layers: TPMI=0 | +| | | | | | | ... | ... | +| | | | | | | 703 | 4 layers: TPMI=279 | +| | | | | | | 704-1024 | reserved | + +**Table 7.3.1.1.2-5M: Precoding information and number of layers, for 8 antenna ports, if transform precoder is disabled, *maxRank* = 2, 3 or 4, *CodebookType*=*Codebook4*, and *ul-FullPowerTransmission* configured to *fullpowerMode1*** + +| Bit field mapped to index | maxRank = 2 | Bit field mapped to index | maxRank = 3 | Bit field mapped to index | maxRank = 4 | +|---------------------------|--------------------|---------------------------|--------------------|---------------------------|--------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| ... | ... | ... | ... | ... | ... | +| 7 | 1 layer: TPMI=7 | 7 | 1 layer: TPMI=7 | 7 | 1 layer: TPMI=7 | +| 8 | 2 layers: TPMI=8 | 8 | 2 layers: TPMI=8 | 8 | 2 layers: TPMI=8 | +| ... | ... | ... | ... | ... | ... | +| 35 | 2 layers: TPMI=35 | 35 | 2 layers: TPMI=35 | 35 | 2 layers: TPMI=35 | +| 36 | 1 layer: TPMI=255 | 36 | 3 layers: TPMI=36 | 36 | 3 layers: TPMI=36 | +| 37 | 2 layers: TPMI=256 | ... | ... | ... | ... | +| 38-63 | reserved | 91 | 3 layers: TPMI=91 | 91 | 3 layers: TPMI=91 | +| | | 92 | 1 layer: TPMI=255 | 92 | 4 layers: TPMI=92 | +| | | 93 | 2 layers: TPMI=256 | ... | ... | +| | | 94 | 3 layers: TPMI=257 | 161 | 4 layers: TPMI=161 | +| | | 95-127 | reserved | 162 | 1 layer: TPMI=255 | +| | | | | 163 | 2 layers: TPMI=256 | +| | | | | 164 | 3 layers: TPMI=257 | +| | | | | 165 | 4 layers: 258 | +| | | | | 166-255 | reserved | + +**Table 7.3.1.1.2-5N: Precoding information and number of layers, for 8 antenna ports, if transform precoder is enabled or *maxRank*=1 if transform is disabled, *CodebookType*=*Codebook4*, and *ul-FullPowerTransmission* configured to *fullpowerMode1*** + +| Bit field mapped to index | Precoding information and number of layers | +|---------------------------|--------------------------------------------| +| 0 | 1 layer: TPMI=0 | +| ... | ... | +| 7 | 1 layer: TPMI=7 | +| 8 | 1 layer: TPMI=255 | +| 9-15 | reserved | + +**Table 7.3.1.1.2-5O: Precoding information and number of layers, for 8 antenna ports, if transform precoder is enabled, or *maxRank* = 1, 2, 3 or 4 if transform precoder is disabled, *CodebookType*=*Codebook2*, and *ul-FullPowerTransmission* configured to *fullpowerMode1*** + +| Bit field mapped to index | Transform precoder is enabled, or maxRank = 1 if transform precoder is disabled | Bit field mapped to index | Transform precoder is disabled and maxRank = 2 | Bit field mapped to index | Transform precoder is disabled and maxRank = 3 | Bit field mapped to index | Transform precoder is disabled and maxRank = 4 | +|---------------------------|----------------------------------------------------------------------------------------|---------------------------|-------------------------------------------------------|---------------------------|-------------------------------------------------------|---------------------------|-------------------------------------------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 31 | 1 layer: TPMI=31 | 31 | 1 layer: TPMI=31 | 31 | 1 layer: TPMI=31 | 31 | 1 layer: TPMI=31 | +| 32 | 1 layer: TPMI=32 | 32 | 2 layers: TPMI=0 | 32 | 2 layers: TPMI=0 | 32 | 2 layers: TPMI=0 | +| 33-63 | reserved | ... | ... | ... | ... | ... | ... | +| | | 303 | 2 layers: TPMI=271 | 303 | 2 layers: TPMI=271 | 303 | 2 layers: TPMI=271 | +| | | 304 | 1 layer: TPMI=32 | 304 | 3 layers: TPMI=0 | 304 | 3 layers: TPMI=0 | +| | | 305-511 | reserved | ... | ... | ... | ... | +| | | | | 567 | 3 layers: TPMI=263 | 567 | 3 layers: TPMI=263 | +| | | | | 568 | 1 layer: TPMI=32 | 568 | 4 layers: TPMI=0 | +| | | | | 569-1023 | reserved | ... | ... | +| | | | | | | 635 | 4 layers: TPMI=67 | +| | | | | | | 636 | 1 layer: TPMI=32 | +| | | | | | | 637-1023 | reserved | + +**Table 7.3.1.1.2-5P: Precoding information and number of layers, for 8 antenna ports, if transform precoder is enabled, or *maxRank* = 1, 2, 3 or 4 if transform precoder is disabled, *CodebookType*=*Codebook3*, and *ul-FullPowerTransmission* is configured to *fullpowerMode1*** + +| Bit field mapped to index | Transform precoder is enabled, or maxRank = 1 if transform precoder is disabled | Bit field mapped to index | transform precoder is disabled and maxRank = 2 | Bit field mapped to index | transform precoder is disabled and maxRank = 3 | Bit field mapped to index | transform precoder is disabled and maxRank = 4 | +|---------------------------|----------------------------------------------------------------------------------------|---------------------------|-------------------------------------------------------|---------------------------|-------------------------------------------------------|---------------------------|-------------------------------------------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 15 | 1 layer: TPMI=15 | 15 | 1 layer: TPMI=15 | 15 | 1 layer: TPMI=15 | 15 | 1 layer: TPMI=15 | +| 16 | 1 layer: TPMI=16 | 16 | 2 layers: TPMI=0 | 16 | 2 layers: TPMI=0 | 16 | 2 layers: TPMI=0 | +| 17-31 | reserved | ... | ... | ... | ... | ... | ... | +| | | 119 | 2 layers: TPMI=103 | 119 | 2 layers: TPMI=103 | 119 | 2 layers: TPMI=103 | +| | | 120 | 1 layer: TPMI=16 | 120 | 3 layers: TPMI=0 | 120 | 3 layers: TPMI=0 | +| | | 121 | 2 layers: TPMI=104 | ... | ... | ... | ... | +| | | 122-127 | reserved | 423 | 3 layers: TPMI=303 | 423 | 3 layers: TPMI=303 | +| | | | | 424 | 1 layer: TPMI=16 | 424 | 4 layers: TPMI=0 | +| | | | | 425 | 2 layers: TPMI=104 | ... | ... | +| | | | | 426 | 3 layers: 304 | 703 | 4 layers: TPMI=279 | +| | | | | 427-511 | reserved | 704 | 1 layer: TPMI=16 | +| | | | | | | 705 | 2 layers: TPMI=104 | +| | | | | | | 706 | 3 layers: TPMI=304 | +| | | | | | | 707-1023 | reserved | + +**Table 7.3.1.1.2-5Q: Precoding information and number of layers, for 8 antenna ports, if transform precoder is disabled, *maxRank* = 5, 6, 7, 8, *CodebookType*=*Codebook4*, and *ul-FullPowerTransmission* is configured to *fullpowerMode1*** + +| Bit field mapped to index | maxRank = 5 | Bit field mapped to index | maxRank = 6 | Bit field mapped to index | maxRank = 7 | Bit field mapped to index | maxRank = 8 | +|---------------------------|--------------------|---------------------------|--------------------|---------------------------|--------------------|---------------------------|--------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 7 | 1 layer: TPMI=7 | 7 | 1 layer: TPMI=7 | 7 | 1 layer: TPMI=7 | 7 | 1 layer: TPMI=7 | +| 8 | 2 layers: TPMI=8 | 8 | 2 layers: TPMI=8 | 8 | 2 layers: TPMI=8 | 8 | 2 layers: TPMI=8 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 35 | 2 layers: TPMI=35 | 35 | 2 layers: TPMI=35 | 35 | 2 layers: TPMI=35 | 35 | 2 layers: TPMI=35 | +| 36 | 3 layers: TPMI=36 | 36 | 3 layers: TPMI=36 | 36 | 3 layers: TPMI=36 | 36 | 3 layers: TPMI=36 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 91 | 3 layers: TPMI=91 | 91 | 3 layers: TPMI=91 | 91 | 3 layers: TPMI=91 | 91 | 3 layers: TPMI=91 | +| 92 | 4 layers: TPMI=92 | 92 | 4 layers: TPMI=92 | 92 | 4 layers: TPMI=92 | 92 | 4 layers: TPMI=92 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 161 | 4 layers: TPMI=161 | 161 | 4 layers: TPMI=161 | 161 | 4 layers: TPMI=161 | 161 | 4 layers: TPMI=161 | +| 162 | 5 layers: TPMI=162 | 162 | 5 layers: TPMI=162 | 162 | 5 layers: TPMI=162 | 162 | 5 layers: TPMI=162 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 217 | 5 layers: TPMI=217 | 217 | 5 layers: TPMI=217 | 217 | 5 layers: TPMI=217 | 217 | 5 layers: TPMI=217 | +| 218 | 1 layer: TPMI=255 | 218 | 6 layers: TPMI=218 | 218 | 6 layers: TPMI=218 | 218 | 6 layers: TPMI=218 | +| 219 | 2 layers: TPMI=256 | ... | ... | ... | ... | ... | ... | +| 220 | 3 layers: TPMI=257 | 245 | 6 layers: TPMI=245 | 245 | 6 layers: TPMI=245 | 245 | 6 layers: TPMI=245 | +| 221 | 4 layers: TPMI=258 | 246 | 1 layer: TPMI=255 | 246 | 7 layers: TPMI=246 | 246 | 7 layers: TPMI=246 | +| 222-255 | reserved | 247 | 2 layers: TPMI=256 | ... | ... | ... | ... | +| | | 248 | 3 layers: TPMI=257 | 253 | 7 layers: TPMI=253 | 253 | 7 layers: TPMI=253 | +| | | 249 | 4 layers: TPMI=258 | 254 | 1 layer: TPMI=255 | 254 | 8 layers: TPMI=254 | +| | | 250-255 | reserved | 255 | 2 layers: | 255 | 1 layer: | + +| | | | | | | | | +|--|--|--|--|---------|-----------------------|---------|-----------------------| +| | | | | 256 | 3 layers:
TPMI=257 | 256 | 2 layers:
TPMI=256 | +| | | | | 257 | 4 layers:
TPMI=258 | 257 | 3 layers:
TPMI=257 | +| | | | | 258-511 | reserved | 258 | 4 layers:
TPMI=258 | +| | | | | | | 259-511 | reserved | + +**Table 7.3.1.1.2-5R: Precoding information and number of layers, for 8 antenna ports, if transform precoder is disabled, *maxRank* = 5, 6, 7, 8, *CodebookType*=*Codebook2*, and *ul-FullPowerTransmission* is configured to *fullpowerMode1*** + +| Bit field mapped to index | maxRank = 5 | Bit field mapped to index | maxRank = 6 | Bit field mapped to index | maxRank = 7 | Bit field mapped to index | maxRank = 8 | +|---------------------------|--------------------|---------------------------|--------------------|---------------------------|--------------------|---------------------------|--------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 31 | 1 layer: TPMI=31 | 31 | 1 layer: TPMI=31 | 31 | 1 layer: TPMI=31 | 31 | 1 layer: TPMI=31 | +| 32 | 2 layers: TPMI=0 | 32 | 2 layers: TPMI=0 | 32 | 2 layers: TPMI=0 | 32 | 2 layers: TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 303 | 2 layers: TPMI=271 | 303 | 2 layers: TPMI=271 | 303 | 2 layers: TPMI=271 | 303 | 2 layers: TPMI=271 | +| 304 | 3 layers: TPMI=0 | 304 | 3 layers: TPMI=0 | 304 | 3 layers: TPMI=0 | 304 | 3 layers: TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 567 | 3 layers: TPMI=263 | 567 | 3 layers: TPMI=263 | 567 | 3 layers: TPMI=263 | 567 | 3 layers: TPMI=263 | +| 568 | 4 layers: TPMI=0 | 568 | 4 layers: TPMI=0 | 568 | 4 layers: TPMI=0 | 568 | 4 layers: TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 635 | 4 layers: TPMI=67 | 635 | 4 layers: TPMI=67 | 635 | 4 layers: TPMI=67 | 635 | 4 layers: TPMI=67 | +| 636 | 5 layers: TPMI=0 | 636 | 5 layers: TPMI=0 | 636 | 5 layers: TPMI=0 | 636 | 5 layers: TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 667 | 5 layers: TPMI=31 | 667 | 5 layers: TPMI=31 | 667 | 5 layers: TPMI=31 | 667 | 5 layers: TPMI=31 | +| 668 | 1 layer: TPMI=32 | 668 | 6 layers: TPMI=0 | 668 | 6 layers: TPMI=0 | 668 | 6 layers: TPMI=0 | +| 669-1023 | reserved | ... | ... | ... | ... | ... | ... | +| | | 683 | 6 layers: TPMI=15 | 683 | 6 layers: TPMI=15 | 683 | 6 layers: TPMI=15 | +| | | 684 | 1 layer: TPMI=32 | 684 | 7 layers: TPMI=0 | 684 | 7 layers: TPMI=0 | +| | | 685-1023 | reserved | ... | ... | ... | ... | +| | | | | 691 | 7 layers: TPMI=7 | 691 | 7 layers: TPMI=7 | +| | | | | 692 | 1 layer: TPMI=32 | 692 | 8 layers: TPMI=0 | +| | | | | 693- | reserved | ... | ... | + +| | | | | | | | | +|--|--|--|--|--|--|--------------|---------------------| +| | | | | | | 695 | 8 layers:
TPMI=3 | +| | | | | | | 696 | 1 layer:
TPMI=32 | +| | | | | | | 697-
1023 | reserved | + +**Table 7.3.1.1.2-5S: Precoding information and number of layers, for 8 antenna ports, if transform precoder is disabled, *maxRank* = 5, 6, 7, 8, *CodebookType*=*Codebook3*, and *ul-FullPowerTransmission* is configured to *fullpowerMode1*** + +| Bit field mapped to index | maxRank = 5 | Bit field mapped to index | maxRank = 6 | Bit field mapped to index | maxRank = 7 | Bit field mapped to index | maxRank = 8 | +|---------------------------|--------------------|---------------------------|--------------------|---------------------------|--------------------|---------------------------|--------------------| +| 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | 0 | 1 layer: TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 15 | 1 layer: TPMI=15 | 15 | 1 layer: TPMI=15 | 15 | 1 layer: TPMI=15 | 15 | 1 layer: TPMI=15 | +| 16 | 2 layers: TPMI=0 | 16 | 2 layers: TPMI=0 | 16 | 2 layers: TPMI=0 | 16 | 2 layers: TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 119 | 2 layers: TPMI=103 | 119 | 2 layers: TPMI=103 | 119 | 2 layers: TPMI=103 | 119 | 2 layers: TPMI=103 | +| 120 | 3 layers: TPMI=0 | 120 | 3 layers: TPMI=0 | 120 | 3 layers: TPMI=0 | 120 | 3 layers: TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 423 | 3 layers: TPMI=303 | 423 | 3 layers: TPMI=303 | 423 | 3 layers: TPMI=303 | 423 | 3 layers: TPMI=303 | +| 424 | 4 layers: TPMI=0 | 424 | 4 layers: TPMI=0 | 424 | 4 layers: TPMI=0 | 424 | 4 layers: TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 703 | 4 layers: TPMI=279 | 703 | 4 layers: TPMI=279 | 703 | 4 layers: TPMI=279 | 703 | 4 layers: TPMI=279 | +| 704 | 5 layers: TPMI=0 | 704 | 5 layers: TPMI=0 | 704 | 5 layers: TPMI=0 | 704 | 5 layers: TPMI=0 | +| ... | ... | ... | ... | ... | ... | ... | ... | +| 863 | 5 layers: TPMI=159 | 863 | 5 layers: TPMI=159 | 863 | 5 layers: TPMI=159 | 863 | 5 layers: TPMI=159 | +| 864 | 1 layer: TPMI=16 | 864 | 6 layers: TPMI=0 | 864 | 6 layers: TPMI=0 | 864 | 6 layers: TPMI=0 | +| 865 | 2 layers: TPMI=104 | ... | ... | ... | ... | ... | ... | +| 866 | 3 layers: TPMI=304 | 943 | 6 layers: TPMI=79 | 943 | 6 layers: TPMI=79 | 943 | 6 layers: TPMI=79 | +| 867-1023 | reserved | 944 | 1 layer: TPMI=16 | 944 | 7 layers: TPMI=0 | 944 | 7 layers: TPMI=0 | +| | | 945 | 2 layers: TPMI=104 | ... | ... | ... | ... | +| | | 946 | 3 layers: TPMI=304 | 975 | 7 layers: TPMI=31 | 975 | 7 layers: TPMI=31 | +| | | 944-1023 | reserved | 976 | 1 layer: TPMI=16 | 976 | 8 layers: TPMI=0 | +| | | | | 977 | 2 layers: | ... | ... | + +| | | | | | | | | +|--|--|--|--|----------|-----------------------|----------|-----------------------| +| | | | | 978 | 3 layers:
TPMI=304 | 991 | 8 layers:
TPMI=15 | +| | | | | 979-1023 | reserved | 992 | 1 layer:
TPMI=16 | +| | | | | | | 993 | 2 layers:
TPMI=104 | +| | | | | | | 994 | 3 layers:
TPMI=304 | +| | | | | | | 995-1023 | reserved | + +**Table 7.3.1.1.2-6: Antenna port(s), transform precoder is enabled, *dmrs-Type=1*, *maxLength=1*, except that *dmrs-UplinkTransformPrecoding* and *tp-pi2BPSK* are both configured and $\pi/2$ -BPSK modulation is used** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 2 | 0 | +| 1 | 2 | 1 | +| 2 | 2 | 2 | +| 3 | 2 | 3 | + +**Table 7.3.1.1.2-6A: Antenna port(s), transform precoder is enabled, *dmrs-UplinkTransformPrecoding* and *tp-pi2BPSK* are both configured, $\pi/2$ -BPSK modulation is used, *dmrs-Type=1*, *maxLength=1*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|-----------------| +| 0 | 2 | 0, $n_{SCID}=0$ | +| 1 | 2 | 0, $n_{SCID}=1$ | +| 2 | 2 | 2, $n_{SCID}=0$ | +| 3 | 2 | 2, $n_{SCID}=1$ | + +**Table 7.3.1.1.2-7: Antenna port(s), transform precoder is enabled, *dmrs-Type=1*, *maxLength=2*, except that *dmrs-UplinkTransformPrecoding* and *tp-pi2BPSK* are both configured and $\pi/2$ -BPSK modulation is used** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 2 | 0 | 1 | +| 1 | 2 | 1 | 1 | +| 2 | 2 | 2 | 1 | +| 3 | 2 | 3 | 1 | +| 4 | 2 | 0 | 2 | +| 5 | 2 | 1 | 2 | +| 6 | 2 | 2 | 2 | +| 7 | 2 | 3 | 2 | +| 8 | 2 | 4 | 2 | +| 9 | 2 | 5 | 2 | +| 10 | 2 | 6 | 2 | +| 11 | 2 | 7 | 2 | +| 12-15 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-7A: Antenna port(s), transform precoder is enabled, *dmrs-UplinkTransformPrecoding* and *tp-pi2BPSK* are both configured, $\pi/2$ -BPSK modulation is used, *dmrs-Type*=1, *maxLength*=2** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|-----------------|------------------------------| +| 0 | 2 | 0, $n_{SCID}=0$ | 1 | +| 1 | 2 | 0, $n_{SCID}=1$ | 1 | +| 2 | 2 | 2, $n_{SCID}=0$ | 1 | +| 3 | 2 | 2, $n_{SCID}=1$ | 1 | +| 4 | 2 | 0, $n_{SCID}=0$ | 2 | +| 5 | 2 | 0, $n_{SCID}=1$ | 2 | +| 6 | 2 | 2, $n_{SCID}=0$ | 2 | +| 7 | 2 | 2, $n_{SCID}=1$ | 2 | +| 8 | 2 | 4, $n_{SCID}=0$ | 2 | +| 9 | 2 | 4, $n_{SCID}=1$ | 2 | +| 10 | 2 | 6, $n_{SCID}=0$ | 2 | +| 11 | 2 | 6, $n_{SCID}=1$ | 2 | +| 12-15 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-8: Antenna port(s), transform precoder is disabled, *dmrs-Type*=1, *enhanced-dmrs-Type* is not configured, *maxLength*=1, rank = 1** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 1 | 0 | +| 1 | 1 | 1 | +| 2 | 2 | 0 | +| 3 | 2 | 1 | +| 4 | 2 | 2 | +| 5 | 2 | 3 | +| 6-7 | Reserved | Reserved | + +**Table 7.3.1.1.2-9: Antenna port(s), transform precoder is disabled, *dmrs-Type*=1, *enhanced-dmrs-Type* is not configured, *maxLength*=1, rank = 2** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 1 | 0,1 | +| 1 | 2 | 0,1 | +| 2 | 2 | 2,3 | +| 3 | 2 | 0,2 | +| 4-7 | Reserved | Reserved | + +**Table 7.3.1.1.2-10: Antenna port(s), transform precoder is disabled, *multipanelScheme* is not configured to *sdmScheme*, *dmrs-Type*=1, *enhanced-dmrs-Type* is not configured, *maxLength*=1, rank = 3** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 2 | 0-2 | +| 1-7 | Reserved | Reserved | + +**Table 7.3.1.1.2-10A: Antenna port(s), transform precoder is disabled, *multipanelScheme* = *sdmScheme*, *dmrs-Type*=1, *enhanced-dmrs-Type* is not configured, *maxLength*=1, rank = 3** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 2 | 0-2 | +| 1 | 2 | 0,2,3 | +| 2-7 | Reserved | Reserved | + +**Table 7.3.1.1.2-11: Antenna port(s), transform precoder is disabled, *dmrs-Type*=1, *enhanced-dmrs-Type* is not configured, *maxLength*=1, rank = 4** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 2 | 0-3 | +| 1-7 | Reserved | Reserved | + +**Table 7.3.1.1.2-12: Antenna port(s), transform precoder is disabled, *dmrs-Type*=1, *enhanced-dmrs-Type* is not configured, *maxLength*=2, rank = 1** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 1 | 0 | 1 | +| 1 | 1 | 1 | 1 | +| 2 | 2 | 0 | 1 | +| 3 | 2 | 1 | 1 | +| 4 | 2 | 2 | 1 | +| 5 | 2 | 3 | 1 | +| 6 | 2 | 0 | 2 | +| 7 | 2 | 1 | 2 | +| 8 | 2 | 2 | 2 | +| 9 | 2 | 3 | 2 | +| 10 | 2 | 4 | 2 | +| 11 | 2 | 5 | 2 | +| 12 | 2 | 6 | 2 | +| 13 | 2 | 7 | 2 | +| 14-15 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-13: Antenna port(s), transform precoder is disabled, *dmrs-Type*=1, *enhanced-dmrs-Type* is not configured, *maxLength*=2, rank = 2** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 1 | 0,1 | 1 | +| 1 | 2 | 0,1 | 1 | +| 2 | 2 | 2,3 | 1 | +| 3 | 2 | 0,2 | 1 | +| 4 | 2 | 0,1 | 2 | +| 5 | 2 | 2,3 | 2 | +| 6 | 2 | 4,5 | 2 | +| 7 | 2 | 6,7 | 2 | +| 8 | 2 | 0,4 | 2 | +| 9 | 2 | 2,6 | 2 | +| 10-15 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-14: Antenna port(s), transform precoder is disabled, *multipanelScheme* is not to *sdmScheme*, *dmrs-Type*=1, *enhanced-dmrs-Type* is not configured, *maxLength*=2, rank = 3** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 2 | 0-2 | 1 | +| 1 | 2 | 0,1,4 | 2 | +| 2 | 2 | 2,3,6 | 2 | +| 3-15 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-14A: Antenna port(s), transform precoder is disabled, *multipanelScheme = sdmScheme*, *dmrs-Type=1*, *enhanced-dmrs-Type* is not configured, *maxLength=2*, *rank = 3*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 2 | 0-2 | 1 | +| 1 | 2 | 0,1,4 | 2 | +| 2 | 2 | 2,3,6 | 2 | +| 3 | 2 | 0,2,3 | 1 | +| 4-15 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-15: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *enhanced-dmrs-Type* is not configured, *maxLength=2*, *rank = 4*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 2 | 0-3 | 1 | +| 1 | 2 | 0,1,4,5 | 2 | +| 2 | 2 | 2,3,6,7 | 2 | +| 3 | 2 | 0,2,4,6 | 2 | +| 4-15 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-15A: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *enhanced-dmrs-Type* is not configured, *maxLength=2*, *rank = 5*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 2 | 0-4 | 2 | +| 1-15 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-15B Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *enhanced-dmrs-Type* is not configured, *maxLength=2*, *rank = 6*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 2 | 0,1,2,3,4,6 | 2 | +| 1-15 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-15C: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *enhanced-dmrs-Type* is not configured, *maxLength=2*, *rank = 7*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|---------------|------------------------------| +| 0 | 2 | 0,1,2,3,4,5,6 | 2 | +| 1-15 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-15D: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *enhanced-dmrs-Type* is not configured, *maxLength=2*, *rank = 8*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|-----------------|------------------------------| +| 0 | 2 | 0,1,2,3,4,5,6,7 | 2 | +| 1-15 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-16: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is not configured, *maxLength=1*, *rank=1*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 1 | 0 | +| 1 | 1 | 1 | +| 2 | 2 | 0 | +| 3 | 2 | 1 | +| 4 | 2 | 2 | +| 5 | 2 | 3 | +| 6 | 3 | 0 | +| 7 | 3 | 1 | +| 8 | 3 | 2 | +| 9 | 3 | 3 | +| 10 | 3 | 4 | +| 11 | 3 | 5 | +| 12-15 | Reserved | Reserved | + +**Table 7.3.1.1.2-17: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is not configured, *maxLength=1*, *rank=2*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 1 | 0,1 | +| 1 | 2 | 0,1 | +| 2 | 2 | 2,3 | +| 3 | 3 | 0,1 | +| 4 | 3 | 2,3 | +| 5 | 3 | 4,5 | +| 6 | 2 | 0,2 | +| 7-15 | Reserved | Reserved | + +**Table 7.3.1.1.2-18: Antenna port(s), transform precoder is disabled, *multipanelScheme* is not configured to *sdmScheme*, *dmrs-Type=2*, *enhanced-dmrs-Type* is not configured, *maxLength=1*, *rank =3*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 2 | 0-2 | +| 1 | 3 | 0-2 | +| 2 | 3 | 3-5 | +| 3-15 | Reserved | Reserved | + +**Table 7.3.1.1.2-18A: Antenna port(s), transform precoder is disabled, *multipanelScheme = sdmScheme*, *dmrs-Type=2*, *enhanced-dmrs-Type* is not configured, *maxLength=1*, *rank =3*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 2 | 0-2 | +| 1 | 3 | 0-2 | +| 2 | 3 | 3-5 | +| 3 | 2 | 0,2,3 | +| 4 | 3 | 0,2,3 | +| 3-15 | Reserved | Reserved | + +**Table 7.3.1.1.2-19: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is not configured, *maxLength=1*, *rank =4*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 2 | 0-3 | +| 1 | 3 | 0-3 | +| 2-15 | Reserved | Reserved | + +**Table 7.3.1.1.2-19A: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is not configured, *maxLength=1*, rank = 5** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 3 | 0-4 | +| 1-15 | Reserved | Reserved | + +**Table 7.3.1.1.2-19B: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is not configured, *maxLength=1*, rank = 6** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 3 | 0-5 | +| 1-15 | Reserved | Reserved | + +**Table 7.3.1.1.2-20: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is not configured, *maxLength=2*, rank=1** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 1 | 0 | 1 | +| 1 | 1 | 1 | 1 | +| 2 | 2 | 0 | 1 | +| 3 | 2 | 1 | 1 | +| 4 | 2 | 2 | 1 | +| 5 | 2 | 3 | 1 | +| 6 | 3 | 0 | 1 | +| 7 | 3 | 1 | 1 | +| 8 | 3 | 2 | 1 | +| 9 | 3 | 3 | 1 | +| 10 | 3 | 4 | 1 | +| 11 | 3 | 5 | 1 | +| 12 | 3 | 0 | 2 | +| 13 | 3 | 1 | 2 | +| 14 | 3 | 2 | 2 | +| 15 | 3 | 3 | 2 | +| 16 | 3 | 4 | 2 | +| 17 | 3 | 5 | 2 | +| 18 | 3 | 6 | 2 | +| 19 | 3 | 7 | 2 | +| 20 | 3 | 8 | 2 | +| 21 | 3 | 9 | 2 | +| 22 | 3 | 10 | 2 | +| 23 | 3 | 11 | 2 | +| 24 | 1 | 0 | 2 | +| 25 | 1 | 1 | 2 | +| 26 | 1 | 6 | 2 | +| 27 | 1 | 7 | 2 | +| 28-31 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-21: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is not configured, *maxLength=2*, *rank=2*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 1 | 0,1 | 1 | +| 1 | 2 | 0,1 | 1 | +| 2 | 2 | 2,3 | 1 | +| 3 | 3 | 0,1 | 1 | +| 4 | 3 | 2,3 | 1 | +| 5 | 3 | 4,5 | 1 | +| 6 | 2 | 0,2 | 1 | +| 7 | 3 | 0,1 | 2 | +| 8 | 3 | 2,3 | 2 | +| 9 | 3 | 4,5 | 2 | +| 10 | 3 | 6,7 | 2 | +| 11 | 3 | 8,9 | 2 | +| 12 | 3 | 10,11 | 2 | +| 13 | 1 | 0,1 | 2 | +| 14 | 1 | 6,7 | 2 | +| 15 | 2 | 0,1 | 2 | +| 16 | 2 | 2,3 | 2 | +| 17 | 2 | 6,7 | 2 | +| 18 | 2 | 8,9 | 2 | +| 19-31 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-22: Antenna port(s), transform precoder is disabled, *multipanelScheme* is not configured to *sdmScheme*, *dmrs-Type=2*, *enhanced-dmrs-Type* is not configured, *maxLength=2*, *rank=3*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 2 | 0-2 | 1 | +| 1 | 3 | 0-2 | 1 | +| 2 | 3 | 3-5 | 1 | +| 3 | 3 | 0,1,6 | 2 | +| 4 | 3 | 2,3,8 | 2 | +| 5 | 3 | 4,5,10 | 2 | +| 6-31 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-22A: Antenna port(s), transform precoder is disabled, *multipanelScheme* = *sdmScheme*, *dmrs-Type=2*, *enhanced-dmrs-Type* is not configured, *maxLength=2*, *rank=3*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 2 | 0-2 | 1 | +| 1 | 3 | 0-2 | 1 | +| 2 | 3 | 3-5 | 1 | +| 3 | 3 | 0,1,6 | 2 | +| 4 | 3 | 2,3,8 | 2 | +| 5 | 3 | 4,5,10 | 2 | +| 6 | 2 | 0,2,3 | 1 | +| 7 | 3 | 0,2,3 | 1 | +| 8-31 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-23: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is not configured, *maxLength=2*, *rank=4*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 2 | 0-3 | 1 | +| 1 | 3 | 0-3 | 1 | +| 2 | 3 | 0,1,6,7 | 2 | +| 3 | 3 | 2,3,8,9 | 2 | +| 4 | 3 | 4,5,10,11 | 2 | +| 5-31 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-23A: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is not configured, *maxLength=2*, *rank = 5*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 3 | 0-4 | 1 | +| 1 | 2 | 0,1,2,3,6 | 2 | +| 12-31 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-23B Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is not configured, *maxLength=2*, *rank = 6*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 3 | 0-5 | 1 | +| 1 | 2 | 0,1,2,3,6,8 | 2 | +| 2-31 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-23C: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is not configured, *maxLength=2*, *rank = 7*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|---------------|------------------------------| +| 0 | 2 | 0,1,2,3,6,7,8 | 2 | +| 1-31 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-23D: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is not configured, *maxLength=2*, *rank = 8*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|-----------------|------------------------------| +| 0 | 2 | 0,1,2,3,6,7,8,9 | 2 | +| 1-31 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-24: SRS request** + +| Value of SRS request field, or value of 'SRS request' index for each cell in the scheduled cell set indicated by SRS request field in DCI 0_3 or 1_3 | Triggered aperiodic SRS resource set(s) for DCI format 0_1, 0_2, 0_3, 1_1, 1_2, 1_3, and 2_3 configured with higher layer parameter srs-TPC-PDCCH-Group set to 'typeB' | Triggered aperiodic SRS resource set(s) for DCI format 2_3 configured with higher layer parameter srs-TPC-PDCCH-Group set to 'typeA' | +|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 00 | No aperiodic SRS resource set triggered | No aperiodic SRS resource set triggered | +| 01 |

SRS resource set(s) configured by SRS-ResourceSet with higher layer parameter aperiodicSRS-ResourceTrigger set to 1 or an entry in aperiodicSRS-ResourceTriggerList set to 1

SRS resource set(s) configured by SRS-PosResourceSet with an entry in aperiodicSRS-ResourceTriggerList set to 1 when triggered by DCI formats 0_1, 0_2, 0_3, 1_1, 1_2 and 1_3

| SRS resource set(s) configured with higher layer parameter usage in SRS-ResourceSet set to 'antennaSwitching' and resourceType in SRS-ResourceSet set to 'aperiodic' for a 1 st set of serving cells configured by higher layers | +| 10 |

SRS resource set(s) configured by SRS-ResourceSet with higher layer parameter aperiodicSRS-ResourceTrigger set to 2 or an entry in aperiodicSRS-ResourceTriggerList set to 2

SRS resource set(s) configured by SRS-PosResourceSet with an entry in aperiodicSRS-ResourceTriggerList set to 2 when triggered by DCI formats 0_1, 0_2, 0_3, 1_1, 1_2 and 1_3

| SRS resource set(s) configured with higher layer parameter usage in SRS-ResourceSet set to 'antennaSwitching' and resourceType in SRS-ResourceSet set to 'aperiodic' for a 2 nd set of serving cells configured by higher layers | +| 11 |

SRS resource set(s) configured by SRS-ResourceSet with higher layer parameter aperiodicSRS-ResourceTrigger set to 3 or an entry in aperiodicSRS-ResourceTriggerList set to 3

SRS resource set(s) configured by SRS-PosResourceSet with an entry in aperiodicSRS-ResourceTriggerList set to 3 when triggered by DCI formats 0_1, 0_2, 0_3, 1_1, 1_2 and 1_3

| SRS resource set(s) configured with higher layer parameter usage in SRS-ResourceSet set to 'antennaSwitching' and resourceType in SRS-ResourceSet set to 'aperiodic' for a 3 rd set of serving cells configured by higher layers | + +**Table 7.3.1.1.2-25: PTRS-DMRS association or Second PTRS-DMRS association for UL PTRS port 0** + +| Value | DMRS port | +|-------|-------------------------------------| +| 0 | 1 st scheduled DMRS port | +| 1 | 2 nd scheduled DMRS port | +| 2 | 3 rd scheduled DMRS port | +| 3 | 4 th scheduled DMRS port | + +**Table 7.3.1.1.2-25A: PTRS-DMRS association for UL PTRS port 0 or for the actual UL PT-RS port if *multipanelScheme* is not configured, or PTRS-DMRS association for UL PTRS port 0 and 1 if *multipanelScheme* is configured to *sdmScheme* and *maxNrofPortsforSDM* is set to 2** + +| Value of MSB | DMRS port | Value of LSB | DMRS port | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------| +| 0 | 1 st scheduled DMRS port corresponding to SRS resource indicator field and/or Precoding information and number of layers field | 0 | 1 st scheduled DMRS port corresponding to Second SRS resource indicator field and/or Second Precoding information field | +| 1 | 2 nd scheduled DMRS port corresponding to SRS resource indicator field and/or Precoding information and number of layers field | 1 | 2 nd scheduled DMRS port corresponding to Second SRS resource indicator field and/or Second Precoding information field | + +**Table 7.3.1.1.2-25B: PTRS-DMRS association for UL PTRS port 0, *maxRank*>4** + +| Value | DMRS port | +|-------|----------------------------------------------------------------------------| +| 0 | 1 st scheduled DMRS port corresponding to the selected Codeword | +| 1 | 2 nd scheduled DMRS port corresponding to the selected Codeword | +| 2 | 3 rd scheduled DMRS port corresponding to the selected Codeword | +| 3 | 4 th scheduled DMRS port corresponding to the selected Codeword | + +**Table 7.3.1.1.2-26: PTRS-DMRS association or Second PTRS-DMRS association for UL PTRS ports 0 and 1** + +| Value of MSB | DMRS port | Value of LSB | DMRS port | +|--------------|----------------------------------------------------|--------------|----------------------------------------------------| +| 0 | 1 st DMRS port which shares PTRS port 0 | 0 | 1 st DMRS port which shares PTRS port 1 | +| 1 | 2 nd DMRS port which shares PTRS port 0 | 1 | 2 nd DMRS port which shares PTRS port 1 | + +**Table 7.3.1.1.2-26A: PTRS-DMRS association for UL PTRS ports 0 and 1, *maxRank*>4** + +| Value of 2 MSBs | DMRS port | Value of 2 LSBs | DMRS port | +|-----------------|----------------------------------------------------|-----------------|----------------------------------------------------| +| 0 | 1 st DMRS port which shares PTRS port 0 | 0 | 1 st DMRS port which shares PTRS port 1 | +| 1 | 2 nd DMRS port which shares PTRS port 0 | 1 | 2 nd DMRS port which shares PTRS port 1 | +| 2 | 3 rd DMRS port which shares PTRS port 0 | 2 | 3 rd DMRS port which shares PTRS port 1 | +| 3 | 4 th DMRS port which shares PTRS port 0 | 3 | 4 th DMRS port which shares PTRS port 1 | + +**Table 7.3.1.1.2-27: void** + +**Table 7.3.1.1.2-28: SRI indication or Second SRI indication, for non-codebook based PUSCH transmission,** + +| Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | +|---------------------------|---------|---------------------------|----------|---------------------------|---------| +| 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | 1 | 1 | 1 | 1 | +| | | 2 | 2 | 2 | 2 | +| | | 3 | reserved | 3 | 3 | + +**Table 7.3.1.1.2-28A: SRI indication, for non-codebook based PUSCH transmission, ,** + +| Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | +|---------------------------|----------|---------------------------|----------|---------------------------|----------|---------------------------|---------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | +| 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | +| 5-7 | reserved | 5 | 5 | 5 | 5 | 5 | 5 | +| | | 6-7 | reserved | 6 | 6 | 6 | 6 | +| | | | | 7 | reserved | 7 | 7 | + +**Table 7.3.1.1.2-29: SRI indication or Second SRI indication, for non-codebook based PUSCH transmission,** + +| Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | +|---------------------------|----------|---------------------------|----------|---------------------------|----------| +| 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | 1 | 1 | 1 | 1 | +| 2 | 0,1 | 2 | 2 | 2 | 2 | +| 3 | reserved | 3 | 0,1 | 3 | 3 | +| | | 4 | 0,2 | 4 | 0,1 | +| | | 5 | 1,2 | 5 | 0,2 | +| | | 6-7 | reserved | 6 | 0,3 | +| | | | | 7 | 1,2 | +| | | | | 8 | 1,3 | +| | | | | 9 | 2,3 | +| | | | | 10-15 | reserved | + +**Table 7.3.1.1.2-29A: Second SRI indication for non-codebook based PUSCH transmission,** + +| Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | +|---------------------------|--------------------|---------------------------|--------------------|---------------------------|--------------------| +| 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | 1 | 1 | 1 | 1 | +| 0 | 0,1 | 2 | 2 | 2 | 2 | +| 1 | 2 layers: reserved | 3 | 1 layer: reserved | 3 | 3 | +| | | 0 | 0,1 | 4-7 | 1 layer: reserved | +| | | 1 | 0,2 | 0 | 0,1 | +| | | 2 | 1,2 | 1 | 0,2 | +| | | 3 | 2 layers: reserved | 2 | 0,3 | +| | | | | 3 | 1,2 | +| | | | | 4 | 1,3 | +| | | | | 5 | 2,3 | +| | | | | 6-7 | 2 layers: reserved | + +**Table 7.3.1.1.2-29B: SRI indication, for non-codebook based PUSCH transmission, ,** + +| Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | +|---------------------------|----------|---------------------------|----------|---------------------------|----------|---------------------------|----------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | +| 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | +| 5 | | 5 | 5 | 5 | 5 | 5 | 5 | +| ... | ... | 6 | | 6 | 6 | 6 | 6 | +| 14 | | ... | ... | 7 | | 7 | 7 | +| 15 | reserved | 20 | | ... | ... | 8 | | +| | | 21-31 | reserved | 27 | | ... | ... | +| | | | | 28-31 | reserved | 35 | | +| | | | | | | 36-63 | reserved | + +where SRIs are as given in Table 7.3.1.1.2-29B-1. + +**Table 7.3.1.1.2-29B-1: SRI(s) for 2 layers,** + +| SRI(s) | SRI(s) for 2 layers, | SRI(s) for 2 layers, | SRI(s) for 2 layers, | SRI(s) for 2 layers, | +|--------|----------------------|----------------------|----------------------|----------------------| +| | 0,1 | 0,1 | 0,1 | 0,1 | +| | 0,2 | 0,2 | 0,2 | 0,2 | +| | 0,3 | 0,3 | 0,3 | 0,3 | +| | 0,4 | 0,4 | 0,4 | 0,4 | +| | 1,2 | 0,5 | 0,5 | 0,5 | +| | 1,3 | 1,2 | 0,6 | 0,6 | +| | 1,4 | 1,3 | 1,2 | 0,7 | +| | 2,3 | 1,4 | 1,3 | 1,2 | +| | 2,4 | 1,5 | 1,4 | 1,3 | +| | 3,4 | 2,3 | 1,5 | 1,4 | +| | | 2,4 | 1,6 | 1,5 | +| | | 2,5 | 2,3 | 1,6 | +| | | 3,4 | 2,4 | 1,7 | +| | | 3,5 | 2,5 | 2,3 | +| | | 4,5 | 2,6 | 2,4 | +| | | | 3,4 | 2,5 | +| | | | 3,5 | 2,6 | +| | | | 3,6 | 2,7 | +| | | | 4,5 | 3,4 | +| | | | 4,6 | 3,5 | +| | | | 5,6 | 3,6 | +| | | | | 3,7 | +| | | | | 4,5 | +| | | | | 4,6 | +| | | | | 4,7 | +| | | | | 5,6 | +| | | | | 5,7 | +| | | | | 6,7 | + +**Table 7.3.1.1.2-30: SRI indication for non-codebook based PUSCH transmission,** + +| Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | +|---------------------------|----------|---------------------------|----------|---------------------------|----------| +| 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | 1 | 1 | 1 | 1 | +| 2 | 0,1 | 2 | 2 | 2 | 2 | +| 3 | reserved | 3 | 0,1 | 3 | 3 | +| | | 4 | 0,2 | 4 | 0,1 | +| | | 5 | 1,2 | 5 | 0,2 | +| | | 6 | 0,1,2 | 6 | 0,3 | +| | | 7 | reserved | 7 | 1,2 | +| | | | | 8 | 1,3 | +| | | | | 9 | 2,3 | +| | | | | 10 | 0,1,2 | +| | | | | 11 | 0,1,3 | +| | | | | 12 | 0,2,3 | +| | | | | 13 | 1,2,3 | +| | | | | 14-15 | reserved | + +**Table 7.3.1.1.2-30A: Second SRI indication for non-codebook based PUSCH transmission, if *multipanelScheme* is not configured,** + +| Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | +|---------------------------|--------------------|---------------------------|--------------------|---------------------------|--------------------| +| 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | 1 | 1 | 1 | 1 | +| 0 | 0,1 | 2 | 2 | 2 | 2 | +| 1 | 2 layers: reserved | 3 | 1 layer: reserved | 3 | 3 | +| | | 0 | 0,1 | 4-7 | 1 layer: reserved | +| | | 1 | 0,2 | 0 | 0,1 | +| | | 2 | 1,2 | 1 | 0,2 | +| | | 3 | 2 layers: reserved | 2 | 0,3 | +| | | 0 | 0,1,2 | 3 | 1,2 | +| | | 1-3 | 3 layers: reserved | 4 | 1,3 | +| | | | | 5 | 2,3 | +| | | | | 6-7 | 2 layers: reserved | +| | | | | 0 | 0,1,2 | +| | | | | 1 | 0,1,3 | +| | | | | 2 | 0,2,3 | +| | | | | 3 | 1,2,3 | +| | | | | 4-7 | 3 layers: reserved | + +**Table 7.3.1.1.2-30B: SRI indication, for non-codebook based PUSCH transmission, ,** + +| Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | +|---------------------------|----------|---------------------------|----------|---------------------------|----------|---------------------------|----------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | +| 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | +| 5 | | 5 | 5 | 5 | 5 | 5 | 5 | +| ... | ... | 6 | | 6 | 6 | 6 | 6 | +| 14 | | ... | ... | 7 | | 7 | 7 | +| 15 | | 20 | | ... | ... | 8 | | +| ... | ... | 21 | | 27 | | ... | ... | +| 24 | | ... | ... | 28 | | 35 | | +| 25-31 | reserved | 40 | | ... | ... | 36 | | +| | | 41-63 | reserved | 62 | | ... | ... | +| | | | | 63-127 | reserved | 91 | | +| | | | | | | 92-127 | reserved | + +where SRIs are as given in Table 7.3.1.1.2-29B-1 and Table 7.3.1.1.2-30B-1. + +**Table 7.3.1.1.2-30B-1: SRI combinations for 3 layers,** + +| SRI(s) for 3 layers, | SRI(s) for 3 layers, | SRI(s) for 3 layers, | SRI(s) for 3 layers, | +|----------------------|----------------------|----------------------|----------------------| +| 0,1,2 | 0,1,2 | 0,1,2 | 0,1,2 | +| 0,1,3 | 0,1,3 | 0,1,3 | 0,1,3 | +| 0,1,4 | 0,1,4 | 0,1,4 | 0,1,4 | +| 0,2,3 | 0,1,5 | 0,1,5 | 0,1,5 | +| 0,2,4 | 0,2,3 | 0,1,6 | 0,1,6 | +| 0,3,4 | 0,2,4 | 0,2,3 | 0,1,7 | +| 1,2,3 | 0,2,5 | 0,2,4 | 0,2,3 | +| 1,2,4 | 0,3,4 | 0,2,5 | 0,2,4 | +| 1,3,4 | 0,3,5 | 0,2,6 | 0,2,5 | +| 2,3,4 | 0,4,5 | 0,3,4 | 0,2,6 | +| | 1,2,3 | 0,3,5 | 0,2,7 | +| | 1,2,4 | 0,3,6 | 0,3,4 | +| | 1,2,5 | 0,4,5 | 0,3,5 | +| | 1,3,4 | 0,4,6 | 0,3,6 | +| | 1,3,5 | 0,5,6 | 0,3,7 | +| | 1,4,5 | 1,2,3 | 0,4,5 | +| | 2,3,4 | 1,2,4 | 0,4,6 | +| | 2,3,5 | 1,2,5 | 0,4,7 | +| | 2,4,5 | 1,2,6 | 0,5,6 | +| | 3,4,5 | 1,3,4 | 0,5,7 | +| | | 1,3,5 | 0,6,7 | +| | | 1,3,6 | 1,2,3 | +| | | 1,4,5 | 1,2,4 | +| | | 1,4,6 | 1,2,5 | +| | | 1,5,6 | 1,2,6 | +| | | 2,3,4 | 1,2,7 | +| | | 2,3,5 | 1,3,4 | +| | | 2,3,6 | 1,3,5 | +| | | 2,4,5 | 1,3,6 | +| | | 2,4,6 | 1,3,7 | +| | | 2,5,6 | 1,4,5 | +| | | 3,4,5 | 1,4,6 | +| | | 3,4,6 | 1,4,7 | +| | | 3,5,6 | 1,5,6 | +| | | 4,5,6 | 1,5,7 | +| | | | 1,6,7 | +| | | | 2,3,4 | +| | | | 2,3,5 | +| | | | 2,3,6 | + +| | SRI(s) for 3 layers, | SRI(s) for 3 layers, | SRI(s) for 3 layers, | SRI(s) for 3 layers, | +|--|-----------------------------|-----------------------------|-----------------------------|-----------------------------| +| | | | | 2,3,7 | +| | | | | 2,4,5 | +| | | | | 2,4,6 | +| | | | | 2,4,7 | +| | | | | 2,5,6 | +| | | | | 2,5,7 | +| | | | | 2,6,7 | +| | | | | 3,4,5 | +| | | | | 3,4,6 | +| | | | | 3,4,7 | +| | | | | 3,5,6 | +| | | | | 3,5,7 | +| | | | | 3,6,7 | +| | | | | 4,5,6 | +| | | | | 4,5,7 | +| | | | | 4,6,7 | +| | | | | 5,6,7 | + +**Table 7.3.1.1.2-31: SRI indication for non-codebook based PUSCH transmission,** + +| Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | +|----------------------------------|----------------|----------------------------------|----------------|----------------------------------|----------------| +| 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | 1 | 1 | 1 | 1 | +| 2 | 0,1 | 2 | 2 | 2 | 2 | +| 3 | reserved | 3 | 0,1 | 3 | 3 | +| | | 4 | 0,2 | 4 | 0,1 | +| | | 5 | 1,2 | 5 | 0,2 | +| | | 6 | 0,1,2 | 6 | 0,3 | +| | | 7 | reserved | 7 | 1,2 | +| | | | | 8 | 1,3 | +| | | | | 9 | 2,3 | +| | | | | 10 | 0,1,2 | +| | | | | 11 | 0,1,3 | +| | | | | 12 | 0,2,3 | +| | | | | 13 | 1,2,3 | +| | | | | 14 | 0,1,2,3 | +| | | | | 15 | reserved | + +**Table 7.3.1.1.2-31A: Second SRI indication for non-codebook based PUSCH transmission, if *multipanelScheme* is not configured,** + +| Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | +|---------------------------|--------------------|---------------------------|--------------------|---------------------------|--------------------| +| 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | 1 | 1 | 1 | 1 | +| 0 | 0,1 | 2 | 2 | 2 | 2 | +| 1 | 2 layers: reserved | 3 | 1 layer: reserved | 3 | 3 | +| | | 0 | 0,1 | 4-7 | 1 layer: reserved | +| | | 1 | 0,2 | 0 | 0,1 | +| | | 2 | 1,2 | 1 | 0,2 | +| | | 3 | 2 layers: reserved | 2 | 0,3 | +| | | 0 | 0,1,2 | 3 | 1,2 | +| | | 1-3 | 3 layers: reserved | 4 | 1,3 | +| | | | | 5 | 2,3 | +| | | | | 6-7 | 2 layers: reserved | +| | | | | 0 | 0,1,2 | +| | | | | 1 | 0,1,3 | +| | | | | 2 | 0,2,3 | +| | | | | 3 | 1,2,3 | +| | | | | 4-7 | 3 layer: reserved | +| | | | | 0 | 0,1,2,3 | +| | | | | 1-7 | 4 layers: reserved | + +**Table 7.3.1.1.2-31B: SRI indication, for non-codebook based PUSCH transmission, ,** + +| Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | +|---------------------------|----------|---------------------------|----------|---------------------------|----------|---------------------------|----------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | +| 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | +| 5 | | 5 | 5 | 5 | 5 | 5 | 5 | +| ... | ... | 6 | | 6 | 6 | 6 | 6 | +| 14 | | ... | ... | 7 | | 7 | 7 | +| 15 | | 20 | | ... | ... | 8 | | +| ... | ... | 21 | | 27 | | ... | ... | +| 24 | | ... | ... | 28 | | 35 | | +| 25 | | 40 | | ... | ... | 36 | | +| ... | ... | 41 | | 62 | | ... | ... | +| 29 | | ... | ... | 63 | | 91 | | +| 30-31 | reserved | 55 | | ... | ... | 92 | | +| | | 56-63 | reserved | 97 | | ... | ... | +| | | | | 98-127 | reserved | 161 | | +| | | | | | | 162-255 | reserved | + +where SRIs are as given in Table 7.3.1.1.2-29B-1, Table 7.3.1.1.2-30B-1 and Table 7.3.1.1.2-31B-1. + +**Table 7.3.1.1.2-31B-1: SRI combinations for 4 layers,** + +| | SRI(s) for 4 layers, | SRI(s) for 4 layers, | SRI(s) for 4 layers, | SRI(s) for 4 layers, | +|--|----------------------|----------------------|----------------------|----------------------| +| | 0,1,2,3 | 0,1,2,3 | 0,1,2,3 | 0,1,2,3 | +| | 0,1,2,4 | 0,1,2,4 | 0,1,2,4 | 0,1,2,4 | +| | 0,1,3,4 | 0,1,2,5 | 0,1,2,5 | 0,1,2,5 | +| | 0,2,3,4 | 0,1,3,4 | 0,1,2,6 | 0,1,2,6 | +| | 1,2,3,4 | 0,1,3,5 | 0,1,3,4 | 0,1,2,7 | +| | | 0,1,4,5 | 0,1,3,5 | 0,1,3,4 | +| | | 0,2,3,4 | 0,1,3,6 | 0,1,3,5 | + +| | SRI(s) for 4 layers, | SRI(s) for 4 layers, | SRI(s) for 4 layers, | SRI(s) for 4 layers, | +|--|-----------------------------|-----------------------------|-----------------------------|-----------------------------| +| | | 0,2,3,5 | 0,1,4,5 | 0,1,3,6 | +| | | 0,2,4,5 | 0,1,4,6 | 0,1,3,7 | +| | | 0,3,4,5 | 0,1,5,6 | 0,1,4,5 | +| | | 1,2,3,4 | 0,2,3,4 | 0,1,4,6 | +| | | 1,2,3,5 | 0,2,3,5 | 0,1,4,7 | +| | | 1,2,4,5 | 0,2,3,6 | 0,1,5,6 | +| | | 1,3,4,5 | 0,2,4,5 | 0,1,5,7 | +| | | 2,3,4,5 | 0,2,4,6 | 0,1,6,7 | +| | | | 0,2,5,6 | 0,2,3,4 | +| | | | 0,3,4,5 | 0,2,3,5 | +| | | | 0,3,4,6 | 0,2,3,6 | +| | | | 0,3,5,6 | 0,2,3,7 | +| | | | 0,4,5,6 | 0,2,4,5 | +| | | | 1,2,3,4 | 0,2,4,6 | +| | | | 1,2,3,5 | 0,2,4,7 | +| | | | 1,2,3,6 | 0,2,5,6 | +| | | | 1,2,4,5 | 0,2,5,7 | +| | | | 1,2,4,6 | 0,2,6,7 | +| | | | 1,2,5,6 | 0,3,4,5 | +| | | | 1,3,4,5 | 0,3,4,6 | +| | | | 1,3,4,6 | 0,3,4,7 | +| | | | 1,3,5,6 | 0,3,5,6 | +| | | | 1,4,5,6 | 0,3,5,7 | +| | | | 2,3,4,5 | 0,3,6,7 | +| | | | 2,3,4,6 | 0,4,5,6 | +| | | | 2,3,5,6 | 0,4,5,7 | +| | | | 2,4,5,6 | 0,4,6,7 | +| | | | 3,4,5,6 | 0,5,6,7 | +| | | | | 1,2,3,4 | +| | | | | 1,2,3,5 | +| | | | | 1,2,3,6 | +| | | | | 1,2,3,7 | +| | | | | 1,2,4,5 | +| | | | | 1,2,4,6 | +| | | | | 1,2,4,7 | +| | | | | 1,2,5,6 | +| | | | | 1,2,5,7 | +| | | | | 1,2,6,7 | +| | | | | 1,3,4,5 | +| | | | | 1,3,4,6 | +| | | | | 1,3,4,7 | +| | | | | 1,3,5,6 | +| | | | | 1,3,5,7 | +| | | | | 1,3,6,7 | +| | | | | 1,4,5,6 | +| | | | | 1,4,5,7 | +| | | | | 1,4,6,7 | +| | | | | 1,5,6,7 | +| | | | | 2,3,4,5 | +| | | | | 2,3,4,6 | +| | | | | 2,3,4,7 | +| | | | | 2,3,5,6 | +| | | | | 2,3,5,7 | +| | | | | 2,3,6,7 | +| | | | | 2,4,5,6 | +| | | | | 2,4,5,7 | +| | | | | 2,4,6,7 | +| | | | | 2,5,6,7 | +| | | | | 3,4,5,6 | +| | | | | 3,4,5,7 | +| | | | | 3,4,6,7 | +| | | | | 3,5,6,7 | +| | | | | 4,5,6,7 | + +**Table 7.3.1.1.2-31C: SRI indication, for non-codebook based PUSCH transmission, ,** + +| Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | +|---------------------------|-----------|---------------------------|----------|---------------------------|----------|---------------------------|----------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | +| 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | +| 5 | | 5 | 5 | 5 | 5 | 5 | 5 | +| ... | ... | 6 | | 6 | 6 | 6 | 6 | +| 14 | | ... | ... | 7 | | 7 | 7 | +| 15 | | 20 | | ... | ... | 8 | | +| ... | ... | 21 | | 27 | | ... | ... | +| 24 | | ... | ... | 28 | | 35 | | +| 25 | | 40 | | ... | ... | 36 | | +| ... | ... | 41 | | 62 | | ... | ... | +| 29 | | ... | ... | 63 | | 91 | | +| 30 | 0,1,2,3,4 | 55 | | ... | ... | 92 | | +| 31 | reserved | 56 | | 97 | | ... | ... | +| | | ... | ... | 98 | | 161 | | +| | | 61 | | ... | ... | 162 | | +| | | 62-63 | reserved | 118 | | ... | ... | +| | | | | 119-127 | reserved | 217 | | +| | | | | | | 218-255 | reserved | + +where SRIs are as given in Table 7.3.1.1.2-29B-1, Table 7.3.1.1.2-30B-1, Table 7.3.1.1.2-31B-1 and Table 7.3.1.1.2-31C-1. + +**Table 7.3.1.1.2-31C-1: SRI combinations for 5 layers,** + +| | SRI(s) for 5 layers, | SRI(s) for 5 layers, | SRI(s) for 5 layers, | +|--|----------------------|----------------------|----------------------| +| | 0,1,2,3,4 | 0,1,2,3,4 | 0,1,2,3,4 | +| | 0,1,2,3,5 | 0,1,2,3,5 | 0,1,2,3,5 | +| | 0,1,2,4,5 | 0,1,2,3,6 | 0,1,2,3,6 | +| | 0,1,3,4,5 | 0,1,2,4,5 | 0,1,2,3,7 | +| | 0,2,3,4,5 | 0,1,2,4,6 | 0,1,2,4,5 | +| | 1,2,3,4,5 | 0,1,2,5,6 | 0,1,2,4,6 | +| | | 0,1,3,4,5 | 0,1,2,4,7 | +| | | 0,1,3,4,6 | 0,1,2,5,6 | +| | | 0,1,3,5,6 | 0,1,2,5,7 | +| | | 0,1,4,5,6 | 0,1,2,6,7 | +| | | 0,2,3,4,5 | 0,1,3,4,5 | +| | | 0,2,3,4,6 | 0,1,3,4,6 | +| | | 0,2,3,5,6 | 0,1,3,4,7 | +| | | 0,2,4,5,6 | 0,1,3,5,6 | +| | | 0,3,4,5,6 | 0,1,3,5,7 | +| | | 1,2,3,4,5 | 0,1,3,6,7 | +| | | 1,2,3,4,6 | 0,1,4,5,6 | +| | | 1,2,3,5,6 | 0,1,4,5,7 | +| | | 1,2,4,5,6 | 0,1,4,6,7 | +| | | 1,3,4,5,6 | 0,1,5,6,7 | +| | | 2,3,4,5,6 | 0,2,3,4,5 | +| | | | 0,2,3,4,6 | +| | | | 0,2,3,4,7 | +| | | | 0,2,3,5,6 | +| | | | 0,2,3,5,7 | +| | | | 0,2,3,6,7 | +| | | | 0,2,4,5,6 | +| | | | 0,2,4,5,7 | + +| | SRI(s) for 5 layers, | SRI(s) for 5 layers, | SRI(s) for 5 layers, | +|--|----------------------|----------------------|----------------------| +| | | | 0,2,4,6,7 | +| | | | 0,2,5,6,7 | +| | | | 0,3,4,5,6 | +| | | | 0,3,4,5,7 | +| | | | 0,3,4,6,7 | +| | | | 0,3,5,6,7 | +| | | | 0,4,5,6,7 | +| | | | 1,2,3,4,5 | +| | | | 1,2,3,4,6 | +| | | | 1,2,3,4,7 | +| | | | 1,2,3,5,6 | +| | | | 1,2,3,5,7 | +| | | | 1,2,3,6,7 | +| | | | 1,2,4,5,6 | +| | | | 1,2,4,5,7 | +| | | | 1,2,4,6,7 | +| | | | 1,2,5,6,7 | +| | | | 1,3,4,5,6 | +| | | | 1,3,4,5,7 | +| | | | 1,3,4,6,7 | +| | | | 1,3,5,6,7 | +| | | | 1,4,5,6,7 | +| | | | 2,3,4,5,6 | +| | | | 2,3,4,5,7 | +| | | | 2,3,4,6,7 | +| | | | 2,3,5,6,7 | +| | | | 2,4,5,6,7 | +| | | | 3,4,5,6,7 | + +Table 7.3.1.1.2-31D: SRI indication, for non-codebook based PUSCH transmission, , + +| Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | +|---------------------------|-----------|---------------------------|-------------|---------------------------|----------|---------------------------|----------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | +| 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | +| 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | +| ... | ... | 6 | ... | 6 | 6 | 6 | 6 | +| 14 | ... | ... | ... | 7 | ... | 7 | 7 | +| 15 | ... | 20 | ... | ... | ... | 8 | ... | +| ... | ... | 21 | ... | 27 | ... | ... | ... | +| 24 | ... | ... | ... | 28 | ... | 35 | ... | +| 25 | ... | 40 | ... | ... | ... | 36 | ... | +| ... | ... | 41 | ... | 62 | ... | ... | ... | +| 29 | ... | ... | ... | 63 | ... | 91 | ... | +| 30 | 0,1,2,3,4 | 55 | ... | ... | ... | 92 | ... | +| 31 | reserved | 56 | ... | 97 | ... | ... | ... | +| | | ... | ... | 98 | ... | 161 | ... | +| | | 61 | ... | ... | ... | 162 | ... | +| | | 62 | 0,1,2,3,4,5 | 118 | ... | ... | ... | +| | | 63 | reserved | 119 | ... | 217 | ... | +| | | | | ... | ... | 218 | ... | +| | | | | 125 | ... | ... | ... | +| | | | | 126-127 | reserved | 245 | ... | +| | | | | | | 246-255 | reserved | + +where SRIs are as given in Table 7.3.1.1.2-29B-1, Table 7.3.1.1.2-30B-1, Table 7.3.1.1.2-31B-1, Table 7.3.1.1.2-31C-1 and Table 7.3.1.1.2-31D-1. + +**Table 7.3.1.1.2-31D-1: SRI combinations for 6 layers,** + +| | SRI(s) for 6 layers, | SRI(s) for 6 layers, | +|--|-----------------------------|-----------------------------| +| | 0,1,2,3,4,5 | 0,1,2,3,4,5 | +| | 0,1,2,3,4,6 | 0,1,2,3,4,6 | +| | 0,1,2,3,5,6 | 0,1,2,3,4,7 | +| | 0,1,2,4,5,6 | 0,1,2,3,5,6 | +| | 0,1,3,4,5,6 | 0,1,2,3,5,7 | +| | 0,2,3,4,5,6 | 0,1,2,3,6,7 | +| | 1,2,3,4,5,6 | 0,1,2,4,5,6 | +| | | 0,1,2,4,5,7 | +| | | 0,1,2,4,6,7 | +| | | 0,1,2,5,6,7 | +| | | 0,1,3,4,5,6 | +| | | 0,1,3,4,5,7 | +| | | 0,1,3,4,6,7 | +| | | 0,1,3,5,6,7 | +| | | 0,1,4,5,6,7 | +| | | 0,2,3,4,5,6 | +| | | 0,2,3,4,5,7 | +| | | 0,2,3,4,6,7 | +| | | 0,2,3,5,6,7 | +| | | 0,2,4,5,6,7 | +| | | 0,3,4,5,6,7 | +| | | 1,2,3,4,5,6 | +| | | 1,2,3,4,5,7 | +| | | 1,2,3,4,6,7 | +| | | 1,2,3,5,6,7 | +| | | 1,2,4,5,6,7 | +| | | 1,3,4,5,6,7 | +| | | 2,3,4,5,6,7 | + +**Table 7.3.1.1.2-31E: SRI indication, for non-codebook based PUSCH transmission, ,** + +| Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | +|---------------------------|-----------|---------------------------|-------------|---------------------------|---------------|---------------------------|---------------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | +| 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | +| 5 | | 5 | 5 | 5 | 5 | 5 | 5 | +| ... | ... | 6 | | 6 | 6 | 6 | 6 | +| 14 | | ... | ... | 7 | | 7 | 7 | +| 15 | | 20 | | ... | ... | 8 | | +| ... | ... | 21 | | 27 | | ... | ... | +| 24 | | ... | ... | 28 | | 35 | | +| 25 | | 40 | | ... | ... | 36 | | +| ... | ... | 41 | | 62 | | ... | ... | +| 29 | | ... | ... | 63 | | 91 | | +| 30 | 0,1,2,3,4 | 55 | | ... | ... | 92 | | +| 31 | reserved | 56 | | 97 | | ... | ... | +| | | ... | ... | 98 | | 161 | | +| | | 61 | | ... | ... | 162 | | +| | | 62 | 0,1,2,3,4,5 | 118 | | ... | ... | +| | | 63 | reserved | 119 | | 217 | | +| | | | | ... | ... | 218 | | +| | | | | 125 | | ... | ... | +| | | | | 126 | 0,1,2,3,4,5,6 | 245 | | +| | | | | 127 | reserved | 246 | 0,1,2,3,4,5,6 | +| | | | | | | 247 | 0,1,2,3,4,5,7 | +| | | | | | | 248 | 0,1,2,3,4,6,7 | +| | | | | | | 249 | 0,1,2,3,5,6,7 | +| | | | | | | 250 | 0,1,2,4,5,6,7 | +| | | | | | | 251 | 0,1,3,4,5,6,7 | +| | | | | | | 252 | 0,2,3,4,5,6,7 | +| | | | | | | 253 | 1,2,3,4,5,6,7 | +| | | | | | | 254-255 | reserved | + +where SRIs are as given in Table 7.3.1.1.2-29B-1, Table 7.3.1.1.2-30B-1, Table 7.3.1.1.2-31B-1, Table 7.3.1.1.2-31C-1 and Table 7.3.1.1.2-31D-1. + +**Table 7.3.1.1.2-31F: SRI indication, for non-codebook based PUSCH transmission, ,** + +| Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | Bit field mapped to index | SRI(s), | +|---------------------------|-----------|---------------------------|-------------|---------------------------|---------------|---------------------------|-----------------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | +| 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | +| 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | +| ... | ... | 6 | ... | 6 | 6 | 6 | 6 | +| 14 | ... | ... | ... | 7 | ... | 7 | 7 | +| 15 | ... | 20 | ... | ... | ... | 8 | ... | +| ... | ... | 21 | ... | 27 | ... | ... | ... | +| 24 | ... | ... | ... | 28 | ... | 35 | ... | +| 25 | ... | 40 | ... | ... | ... | 36 | ... | +| ... | ... | 41 | ... | 62 | ... | ... | ... | +| 29 | ... | ... | ... | 63 | ... | 91 | ... | +| 30 | 0,1,2,3,4 | 55 | ... | ... | ... | 92 | ... | +| 31 | reserved | 56 | ... | 97 | ... | ... | ... | +| | | ... | ... | 98 | ... | 161 | ... | +| | | 61 | ... | ... | ... | 162 | ... | +| | | 62 | 0,1,2,3,4,5 | 118 | ... | ... | ... | +| | | 63 | reserved | 119 | ... | 217 | ... | +| | | | | ... | ... | 218 | ... | +| | | | | 125 | ... | ... | ... | +| | | | | 126 | 0,1,2,3,4,5,6 | 245 | ... | +| | | | | 127 | reserved | 246 | 0,1,2,3,4,5,6 | +| | | | | | | 247 | 0,1,2,3,4,5,7 | +| | | | | | | 248 | 0,1,2,3,4,6,7 | +| | | | | | | 249 | 0,1,2,3,5,6,7 | +| | | | | | | 250 | 0,1,2,4,5,6,7 | +| | | | | | | 251 | 0,1,3,4,5,6,7 | +| | | | | | | 252 | 0,2,3,4,5,6,7 | +| | | | | | | 253 | 1,2,3,4,5,6,7 | +| | | | | | | 254 | 0,1,2,3,4,5,6,7 | +| | | | | | | 255 | reserved | + +where SRIs are as given in Table 7.3.1.1.2-29B-1, Table 7.3.1.1.2-30B-1, Table 7.3.1.1.2-31B-1, Table 7.3.1.1.2-31C-1 and Table 7.3.1.1.2-31D-1. + +**Table 7.3.1.1.2-32: SRI indication or Second SRI indication, for codebook based PUSCH transmission, if *ul-FullPowerTransmission* is not configured, or *ul-FullPowerTransmission* = *fullpowerMode1*, or *ul-FullPowerTransmission* = *fullpowerMode2*, or *ul-FullPowerTransmission* = *fullpower* and** + +| Bit field mapped to index | SRI(s), | +|---------------------------|---------| +| 0 | 0 | +| 1 | 1 | + +**Table 7.3.1.1.2-32A: SRI indication or Second SRI indication, for codebook based PUSCH transmission, if *ul-FullPowerTransmission* = *fullpowerMode2* and** + +| Bit field mapped to index | SRI(s), | +|---------------------------|----------| +| 0 | 0 | +| 1 | 1 | +| 2 | 2 | +| 3 | Reserved | + +**Table 7.3.1.1.2-32B: SRI indication or Second SRI indication, for codebook based PUSCH transmission, if *ul-FullPowerTransmission = fullpowerMode2* and** + +| Bit field mapped to index | SRI(s), | +|---------------------------|---------| +| 0 | 0 | +| 1 | 1 | +| 2 | 2 | +| 3 | 3 | + +**Table 7.3.1.1.2-33: Joint indication of minimum applicable scheduling offset K0/K2** + +| Bit field mapped to index | Minimum applicable K0 for the active DL BWP, if minimumSchedulingOffsetK0 is configured for the DL BWP | Minimum applicable K2 for the active UL BWP, if minimumSchedulingOffsetK2 is configured for the UL BWP | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| 0 | The first value configured by minimumSchedulingOffsetK0 for the active DL BWP | The first value configured by minimumSchedulingOffsetK2 for the active UL BWP | +| 1 | The second value configured by minimumSchedulingOffsetK0 for the active DL BWP if the second value is configured; 0 otherwise | The second value configured by minimumSchedulingOffsetK2 for the active UL BWP if the second value is configured; 0 otherwise | + +**Table 7.3.1.1.2-34: Redundancy version** + +| Value of the Redundancy version field | Value of to be applied | +|---------------------------------------|------------------------| +| 0 | 0 | +| 1 | 2 | + +**Table 7.3.1.1.2-35: Allowed entries for DCI format 0\_1 and DCI format 0\_2, configured by higher layer parameter *ul-AccessConfigListDCI-0-1* and *ul-AccessConfigListDCI-0-2*, respectively, in frequency range 1** + +| Entry index | Channel Access Type | The CP extension T "ext" index defined in Clause 5.3.1 of [4, 38.211] | CAPC | +|-------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------|------| +| 0 | Type2C-ULChannelAccess defined in clause 4.2.1.2.3 in TS 37.213 [14] | 0 | 1 | +| 1 | Type2C-ULChannelAccess defined in clause 4.2.1.2.3 in TS 37.213 [14] | 0 | 2 | +| 2 | Type2C-ULChannelAccess defined in clause 4.2.1.2.3 in TS 37.213 [14] | 0 | 3 | +| 3 | Type2C-ULChannelAccess defined in clause 4.2.1.2.3 in TS 37.213 [14] | 0 | 4 | +| 4 | Type2C-ULChannelAccess defined in clause 4.2.1.2.3 in TS 37.213 [14] | 2 | 1 | +| 5 | Type2C-ULChannelAccess defined in clause 4.2.1.2.3 in TS 37.213 [14] | 2 | 2 | +| 6 | Type2C-ULChannelAccess defined in clause 4.2.1.2.3 in TS 37.213 [14] | 2 | 3 | +| 7 | Type2C-ULChannelAccess defined in clause 4.2.1.2.3 in TS 37.213 [14] | 2 | 4 | +| 8 | Type2B-ULChannelAccess defined in clause 4.2.1.2.2 in TS 37.213 [14] | 0 | 1 | +| 9 | Type2B-ULChannelAccess defined in clause 4.2.1.2.2 in TS 37.213 [14] | 0 | 2 | +| 10 | Type2B-ULChannelAccess defined in clause 4.2.1.2.2 in TS 37.213 [14] | 0 | 3 | +| 11 | Type2B-ULChannelAccess defined in clause 4.2.1.2.2 in TS 37.213 [14] | 0 | 4 | +| 12 | Type2B-ULChannelAccess defined in clause 4.2.1.2.2 in TS 37.213 [14] | 2 | 1 | +| 13 | Type2B-ULChannelAccess defined in clause 4.2.1.2.2 in TS 37.213 [14] | 2 | 2 | + +| Entry index | Channel Access Type | The CP extension T_"ext" index defined in Clause 5.3.1 of [4, 38.211] | CAPC | +|-------------|----------------------------------------------------------------------|-----------------------------------------------------------------------|------| +| | TS 37.213 [14] | | | +| 14 | Type2B-ULChannelAccess defined in clause 4.2.1.2.2 in TS 37.213 [14] | 2 | 3 | +| 15 | Type2B-ULChannelAccess defined in clause 4.2.1.2.2 in TS 37.213 [14] | 2 | 4 | +| 16 | Type2A-ULChannelAccess defined in clause 4.2.1.2.1 in TS 37.213 [14] | 0 | 1 | +| 17 | Type2A-ULChannelAccess defined in clause 4.2.1.2.1 in TS 37.213 [14] | 0 | 2 | +| 18 | Type2A-ULChannelAccess defined in clause 4.2.1.2.1 in TS 37.213 [14] | 0 | 3 | +| 19 | Type2A-ULChannelAccess defined in clause 4.2.1.2.1 in TS 37.213 [14] | 0 | 4 | +| 20 | Type2A-ULChannelAccess defined in clause 4.2.1.2.1 in TS 37.213 [14] | 1 | 1 | +| 21 | Type2A-ULChannelAccess defined in clause 4.2.1.2.1 in TS 37.213 [14] | 1 | 2 | +| 22 | Type2A-ULChannelAccess defined in clause 4.2.1.2.1 in TS 37.213 [14] | 1 | 3 | +| 23 | Type2A-ULChannelAccess defined in clause 4.2.1.2.1 in TS 37.213 [14] | 1 | 4 | +| 24 | Type2A-ULChannelAccess defined in clause 4.2.1.2.1 in TS 37.213 [14] | 3 | 1 | +| 25 | Type2A-ULChannelAccess defined in clause 4.2.1.2.1 in TS 37.213 [14] | 3 | 2 | +| 26 | Type2A-ULChannelAccess defined in clause 4.2.1.2.1 in TS 37.213 [14] | 3 | 3 | +| 27 | Type2A-ULChannelAccess defined in clause 4.2.1.2.1 in TS 37.213 [14] | 3 | 4 | +| 28 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 0 | 1 | +| 29 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 0 | 2 | +| 30 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 0 | 3 | +| 31 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 0 | 4 | +| 32 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 1 | 1 | +| 33 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 1 | 2 | +| 34 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 1 | 3 | +| 35 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 1 | 4 | +| 36 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 2 | 1 | +| 37 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 2 | 2 | +| 38 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 2 | 3 | +| 39 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 2 | 4 | +| 40 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 3 | 1 | +| 41 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 3 | 2 | +| 42 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 3 | 3 | +| 43 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 3 | 4 | + +**Table 7.3.1.1.2-35A: Allowed entries for DCI format 0\_1 and DCI format 0\_2, configured by higher layer parameter *ul-AccessConfigListDCI-0-1* in frequency range 2-2** + +| Entry index | Channel Access Type | +|-------------|-----------------------------------------------------------------| +| 0 | Type 1 channel access defined in clause 4.4.1 of TS 37.213 [14] | +| 1 | Type 2 channel access defined in clause 4.4.2 of TS 37.213 [14] | +| 2 | Type 3 channel access defined in clause 4.4.3 of TS 37.213 [14] | + +**Table 7.3.1.1.2-36: SRS resource set indication** + +| Bit field mapped to index | SRS resource set indication | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | SRS resource indicator field and Precoding information and number of layers field are associated with the first SRS resource set;
Second SRS resource indicator field and Second Precoding information field are reserved;
If there are two indicated joint/UL TCI states, the first indicated joint/UL TCI state is applied to the corresponding PUSCH transmission occasions. | +| 1 | SRS resource indicator field and Precoding information and number of layers field are associated with the second SRS resource set;
Second SRS resource indicator field and Second Precoding information field are reserved;
If there are two indicated joint/UL TCI states, the second indicated joint/UL TCI state is applied to the corresponding PUSCH transmission occasions. | +| 2 | SRS resource indicator field and Precoding information and number of layers field are associated with the first SRS resource set;
Second SRS resource indicator field and Second Precoding information field are associated with the second SRS resource set;
If there are two indicated joint/UL TCI states, the first indicated joint/UL TCI state is applied to the PUSCH transmission occasions/antenna ports associated with the first SRS resource set, and the second indicated joint/UL TCI state is applied to the PUSCH transmission occasions/antenna ports associated with the second SRS resource set. | +| 3 | SRS resource indicator field and Precoding information and number of layers field are associated with the first SRS resource set;
Second SRS resource indicator field and Second Precoding information field are associated with the second SRS resource set;
If there are two indicated joint/UL TCI states, the first indicated joint/UL TCI state is applied to the PUSCH transmission occasions associated with the first SRS resource set, and the second indicated 3UL TCI state is applied to the PUSCH transmission occasions associated with the second SRS resource set.
If multipanelScheme is configured, this row is reserved. | +| NOTE 1: The first and the second SRS resource sets are respectively the ones with lower and higher srs-ResourceSetId of the two SRS resources sets configured by higher layer parameter srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 , and associated with the higher layer parameter usage of value 'nonCodeBook' if txConfig=nonCodebook or 'codebook' if txConfig=codebook . When only one SRS resource set is configured by higher layer parameter srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 , and associated with the higher layer parameter usage of value 'codebook' or 'nonCodeBook' respectively, the first SRS resource set is the SRS resource set. The association of the first and second SRS resource sets to PUSCH repetitions for each bit field index value is as defined in Clause 6.1.2.1 of TS 38.214 [6]. | | +| NOTE 2: For DCI format 0_2, the first and second SRS resource sets configured by higher layer parameter srs-ResourceSetToAddModListDCI-0-2 are composed of the first SRS resources together with other configurations in the first and second SRS resource sets configured by higher layer parameter srs-ResourceSetToAddModList , if any, and associated with the higher layer parameter usage of value 'codebook' or 'nonCodeBook', respectively, except for the higher layer parameters ' srs-ResourceSetId ' and ' srs-ResourceIdList '. | | + +**Table 7.3.1.1.2-37: SRS offset indicator** + +| Bit field mapped to index | Available slot offset, K=2 | Bit field mapped to index | Available slot offset, K=3 | Bit field mapped to index | Available slot offset, K=4 | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------|---------------------------|------------------------------------------------------------------------------------------------------------------------------|---------------------------|------------------------------------------------------------------------------------------------------------------------------| +| 0 | The 1 st entry in availableSlotOffsetList , if configured for the aperiodic SRS resource set; 0, otherwise | 0 | The 1 st entry in availableSlotOffsetList , if configured for the aperiodic SRS resource set; 0, otherwise | 0 | The 1 st entry in availableSlotOffsetList , if configured for the aperiodic SRS resource set; 0, otherwise | +| 1 | The 2 nd entry in availableSlotOffsetList , if configured for the aperiodic SRS resource set; 0, otherwise | 1 | The 2 nd entry in availableSlotOffsetList , if configured for the aperiodic SRS resource set; 0, otherwise | 1 | The 2 nd entry in availableSlotOffsetList , if configured for the aperiodic SRS resource set; 0, otherwise | +| | | 2 | The 3 rd entry in availableSlotOffsetList , if configured for the aperiodic SRS resource set; 0, otherwise | 2 | The 3 rd entry in availableSlotOffsetList , if configured for the aperiodic SRS resource set; 0, otherwise | +| | | 3 | Reserved | 3 | The 4 th entry in availableSlotOffsetList , if configured for the aperiodic SRS resource set; 0, otherwise | + +**Table 7.3.1.1.2-38: Antenna port(s), transform precoder is disabled, *dmrs-Type*=1, *enhanced-dmrs-Type* is configured, *maxLength*=1, rank = 1** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 1 | 0 | +| 1 | 1 | 1 | +| 2 | 2 | 0 | +| 3 | 2 | 1 | +| 4 | 2 | 2 | +| 5 | 2 | 3 | +| 6 | 1 | 8 | +| 7 | 1 | 9 | +| 8 | 2 | 8 | +| 9 | 2 | 9 | +| 10 | 2 | 10 | +| 11 | 2 | 11 | +| 12-15 | Reserved | Reserved | + +**Table 7.3.1.1.2-39: Antenna port(s), transform precoder is disabled, *dmrs-Type*=1, *enhanced-dmrs-Type* is configured, *maxLength*=1, rank = 2** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 1 | 0,1 | +| 1 | 2 | 0,1 | +| 2 | 2 | 2,3 | +| 3 | 2 | 0,2 | +| 4 | 1 | 8,9 | +| 5 | 2 | 8,9 | +| 6 | 2 | 10,11 | +| 7 | 2 | 9,11 | +| 8-15 | Reserved | Reserved | + +**Table 7.3.1.1.2-40: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *multipanelScheme* is not configured to *sdmScheme*, *enhanced-dmrs-Type* is configured, *maxLength=1*, rank = 3** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 2 | 0-2 | +| 1 | 2 | 8-10 | +| 2 | 1 | 0,1,8 | +| 3 | 2 | 0,1,8 | +| 4 | 2 | 2,3,10 | +| 5-15 | Reserved | Reserved | + +**Table 7.3.1.1.2-40A: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *multipanelScheme* is configured to *sdmScheme*, *enhanced-dmrs-Type* is configured, *maxLength=1*, rank = 3** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 2 | 0-2 | +| 1 | 2 | 8-10 | +| 2 | 1 | 0,1,8 | +| 3 | 2 | 0,1,8 | +| 4 | 2 | 2,3,10 | +| 5 | 2 | 0,2,3 | +| 6-15 | Reserved | Reserved | + +**Table 7.3.1.1.2-41: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *enhanced-dmrs-Type* is configured, *maxLength=1*, rank = 4** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 2 | 0-3 | +| 1 | 2 | 8-11 | +| 2 | 1 | 0,1,8,9 | +| 3 | 2 | 0,1,8,9 | +| 4 | 2 | 2,3,10,11 | +| 5-15 | Reserved | Reserved | + +**Table 7.3.1.1.2-42: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *enhanced-dmrs-Type* is configured, *maxLength=1*, rank = 5** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 2 | 0,1,2,3,8 | +| 1-15 | Reserved | Reserved | + +**Table 7.3.1.1.2-43: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *enhanced-dmrs-Type* is configured, *maxLength=1*, rank = 6** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 2 | 0,1,2,3,8,10 | +| 1-15 | Reserved | Reserved | + +**Table 7.3.1.1.2-44: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *enhanced-dmrs-Type* is configured, *maxLength=1*, rank = 7** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|----------------| +| 0 | 2 | 0,1,2,3,8,9,10 | +| 1-15 | Reserved | Reserved | + +**Table 7.3.1.1.2-45: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *enhanced-dmrs-Type* is configured, *maxLength=1*, rank = 8** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|-------------------| +| 0 | 2 | 0,1,2,3,8,9,10,11 | +| 1-15 | Reserved | Reserved | + +**Table 7.3.1.1.2-46: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *enhanced-dmrs-Type* is configured, *maxLength=2*, rank = 1** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 1 | 0 | 1 | +| 1 | 1 | 1 | 1 | +| 2 | 2 | 0 | 1 | +| 3 | 2 | 1 | 1 | +| 4 | 2 | 2 | 1 | +| 5 | 2 | 3 | 1 | +| 6 | 2 | 0 | 2 | +| 7 | 2 | 1 | 2 | +| 8 | 2 | 2 | 2 | +| 9 | 2 | 3 | 2 | +| 10 | 2 | 4 | 2 | +| 11 | 2 | 5 | 2 | +| 12 | 2 | 6 | 2 | +| 13 | 2 | 7 | 2 | +| 14 | 1 | 8 | 1 | +| 15 | 1 | 9 | 1 | +| 16 | 2 | 8 | 1 | +| 17 | 2 | 9 | 1 | +| 18 | 2 | 10 | 1 | +| 19 | 2 | 11 | 1 | +| 20 | 2 | 8 | 2 | +| 21 | 2 | 9 | 2 | +| 22 | 2 | 10 | 2 | +| 23 | 2 | 11 | 2 | +| 24 | 2 | 12 | 2 | +| 25 | 2 | 13 | 2 | +| 26 | 2 | 14 | 2 | +| 27 | 2 | 15 | 2 | +| 28 | 1 | 0 | 2 | +| 29 | 1 | 1 | 2 | +| 30 | 1 | 8 | 2 | +| 31 | 1 | 9 | 2 | + +**Table 7.3.1.1.2-47: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *enhanced-dmrs-Type* is configured, *maxLength=2*, rank = 2** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 1 | 0,1 | 1 | +| 1 | 2 | 0,1 | 1 | +| 2 | 2 | 2,3 | 1 | +| 3 | 2 | 0,2 | 1 | +| 4 | 2 | 0,1 | 2 | +| 5 | 2 | 2,3 | 2 | +| 6 | 2 | 4,5 | 2 | +| 7 | 2 | 6,7 | 2 | +| 8 | 2 | 0,4 | 2 | +| 9 | 2 | 2,6 | 2 | +| 10 | 1 | 8,9 | 1 | +| 11 | 2 | 8,9 | 1 | +| 12 | 2 | 10,11 | 1 | +| 13 | 2 | 8,9 | 2 | +| 14 | 2 | 10,11 | 2 | + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 15 | 2 | 12,13 | 2 | +| 16 | 2 | 14,15 | 2 | +| 17 | 2 | 9,11 | 1 | +| 18 | 2 | 1,3 | 1 | +| 19 | 2 | 0,2 | 2 | +| 20 | 2 | 1,3 | 2 | +| 21 | 2 | 4,6 | 2 | +| 22 | 2 | 5,7 | 2 | +| 23 | 2 | 8,10 | 2 | +| 24 | 2 | 9,11 | 2 | +| 25 | 2 | 12,14 | 2 | +| 26 | 2 | 13,15 | 2 | +| 27 | 1 | 0,1 | 2 | +| 28 | 1 | 8,9 | 2 | +| 29 | 1 | 4,5 | 2 | +| 30 | 1 | 12,13 | 2 | +| 31 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-48: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *multipanelScheme* is not configured to *sdmScheme*, *enhanced-dmrs-Type* is configured, *maxLength=2*, *rank = 3*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 2 | 0-2 | 1 | +| 1 | 2 | 0,1,4 | 2 | +| 2 | 2 | 2,3,6 | 2 | +| 3 | 2 | 9-11 | 1 | +| 4 | 2 | 8,9,12 | 2 | +| 5 | 2 | 10,11,14 | 2 | +| 6 | 1 | 0,1,8 | 1 | +| 7 | 2 | 0,1,8 | 1 | +| 8 | 2 | 2,3,10 | 1 | +| 9 | 2 | 0,1,8 | 2 | +| 10 | 2 | 4,5,12 | 2 | +| 11 | 2 | 2,3,10 | 2 | +| 12 | 2 | 6,7,14 | 2 | +| 13 | 2 | 5,8,9 | 2 | +| 14 | 2 | 7,10,11 | 2 | +| 15 | 2 | 7,12,13 | 2 | +| 16-31 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-48A: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *multipanelScheme* is configured to *sdmScheme*, *enhanced-dmrs-Type* is configured, *maxLength=2*, *rank = 3*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 2 | 0-2 | 1 | +| 1 | 2 | 0,1,4 | 2 | +| 2 | 2 | 2,3,6 | 2 | +| 3 | 2 | 9-11 | 1 | +| 4 | 2 | 8,9,12 | 2 | +| 5 | 2 | 10,11,14 | 2 | +| 6 | 1 | 0,1,8 | 1 | +| 7 | 2 | 0,1,8 | 1 | +| 8 | 2 | 2,3,10 | 1 | +| 9 | 2 | 0,1,8 | 2 | +| 10 | 2 | 4,5,12 | 2 | +| 11 | 2 | 2,3,10 | 2 | +| 12 | 2 | 6,7,14 | 2 | +| 13 | 2 | 5,8,9 | 2 | +| 14 | 2 | 7,10,11 | 2 | +| 15 | 2 | 7,12,13 | 2 | +| 16 | 2 | 0,2,3 | 1 | +| 17-31 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-49: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *enhanced-dmrs-Type* is configured, *maxLength=2*, rank = 4** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 2 | 0-3 | 1 | +| 1 | 2 | 0,1,4,5 | 2 | +| 2 | 2 | 2,3,6,7 | 2 | +| 3 | 2 | 0,2,4,6 | 2 | +| 4 | 2 | 8-11 | 1 | +| 5 | 2 | 8,9,12,13 | 2 | +| 6 | 2 | 10,11,14,15 | 2 | +| 7 | 2 | 1,3,5,7 | 2 | +| 8 | 1 | 0,1,8,9 | 1 | +| 9 | 2 | 0,1,8,9 | 1 | +| 10 | 2 | 2,3,10,11 | 1 | +| 11 | 1 | 0,1,8,9 | 2 | +| 12 | 1 | 4,5,12,13 | 2 | +| 13 | 2 | 0,1,8,9 | 2 | +| 14 | 2 | 4,5,12,13 | 2 | +| 15 | 2 | 2,3,10,11 | 2 | +| 16 | 2 | 6,7,14,15 | 2 | +| 17-31 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-50: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *enhanced-dmrs-Type* is configured, *maxLength=2*, rank = 5** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 2 | 0-4 | 2 | +| 1 | 2 | 0,1,2,3,8 | 1 | +| 2 | 1 | 0,1,4,5,8 | 2 | +| 3 | 2 | 0,1,4,5,8 | 2 | +| 4-31 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-51: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *enhanced-dmrs-Type* is configured, *maxLength=2*, rank = 6** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 2 | 0,1,2,3,4,6 | 2 | +| 1 | 2 | 0,1,2,3,8,10 | 1 | +| 2 | 1 | 0,1,4,5,8,12 | 2 | +| 3 | 2 | 0,1,4,5,8,12 | 2 | +| 4-31 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-52: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *enhanced-dmrs-Type* is configured, *maxLength=2*, rank = 7** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|----------------|------------------------------| +| 0 | 2 | 0,1,2,3,4,5,6 | 2 | +| 1 | 2 | 0,1,2,3,8,9,10 | 1 | +| 2 | 1 | 0,1,4,5,8,9,12 | 2 | +| 3 | 2 | 0,1,4,5,8,9,12 | 2 | +| 4-31 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-53: Antenna port(s), transform precoder is disabled, *dmrs-Type=1*, *enhanced-dmrs-Type* is configured, *maxLength=2*, rank = 8** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|-------------------|------------------------------| +| 0 | 2 | 0,1,2,3,4,5,6,7 | 2 | +| 1 | 2 | 0,1,2,3,8,9,10,11 | 1 | +| 2 | 1 | 0,1,4,5,8,9,12,13 | 2 | +| 3 | 2 | 0,1,4,5,8,9,12,13 | 2 | +| 4-31 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-54: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is configured, *maxLength=1*, rank = 1** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 1 | 0 | +| 1 | 1 | 1 | +| 2 | 2 | 0 | +| 3 | 2 | 1 | +| 4 | 2 | 2 | +| 5 | 2 | 3 | +| 6 | 3 | 0 | +| 7 | 3 | 1 | +| 8 | 3 | 2 | +| 9 | 3 | 3 | +| 10 | 3 | 4 | +| 11 | 3 | 5 | +| 12 | 1 | 12 | +| 13 | 1 | 13 | +| 14 | 2 | 12 | +| 15 | 2 | 13 | +| 16 | 2 | 14 | +| 17 | 2 | 15 | +| 18 | 3 | 12 | +| 19 | 3 | 13 | +| 20 | 3 | 14 | +| 21 | 3 | 15 | +| 22 | 3 | 16 | +| 23 | 3 | 17 | +| 24-31 | Reserved | Reserved | + +**Table 7.3.1.1.2-55: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is configured, *maxLength=1*, rank = 2** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 1 | 0,1 | +| 1 | 2 | 0,1 | +| 2 | 2 | 2,3 | +| 3 | 3 | 0,1 | +| 4 | 3 | 2,3 | +| 5 | 3 | 4,5 | +| 6 | 2 | 0,2 | +| 7 | 1 | 12,13 | +| 8 | 2 | 12,13 | +| 9 | 2 | 14,15 | +| 10 | 3 | 12,13 | +| 11 | 3 | 14,15 | +| 12 | 3 | 16,17 | +| 13 | 3 | 13,15 | +| 14 | 2 | 13,15 | +| 15-31 | Reserved | Reserved | + +**Table 7.3.1.1.2-56: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *multipanelScheme* is not configured to *sdmScheme*, *enhanced-dmrs-Type* is configured, *maxLength=1*, rank = 3** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 2 | 0-2 | +| 1 | 3 | 0-2 | +| 2 | 3 | 3-5 | +| 3 | 1 | 0,1,12 | +| 4 | 2 | 0,1,12 | +| 5 | 2 | 2,3,14 | + +| | | | +|-------|----------|----------| +| 6 | 3 | 0,1,12 | +| 7 | 3 | 2,3,14 | +| 8 | 3 | 4,5,16 | +| 9 | 3 | 13,15,17 | +| 10-31 | Reserved | Reserved | + +**Table 7.3.1.1.2-56A: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *multipanelScheme* is configured to *sdmScheme*, *enhanced-dmrs-Type* is configured, *maxLength=1*, *rank = 3*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 2 | 0-2 | +| 1 | 3 | 0-2 | +| 2 | 3 | 3-5 | +| 3 | 1 | 0,1,12 | +| 4 | 2 | 0,1,12 | +| 5 | 2 | 2,3,14 | +| 6 | 3 | 0,1,12 | +| 7 | 3 | 2,3,14 | +| 8 | 3 | 4,5,16 | +| 9 | 3 | 13,15,17 | +| 10 | 2 | 0,2,3 | +| 11-31 | Reserved | Reserved | + +**Table 7.3.1.1.2-57: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is configured, *maxLength=1*, *rank = 4*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 2 | 0-3 | +| 1 | 3 | 0-3 | +| 2 | 1 | 0,1,12,13 | +| 3 | 2 | 0,1,12,13 | +| 4 | 2 | 2,3,14,15 | +| 5 | 3 | 0,1,12,13 | +| 6 | 3 | 2,3,14,15 | +| 7 | 3 | 4,5,16,17 | +| 8-31 | Reserved | Reserved | + +**Table 7.3.1.1.2-58: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is configured, *maxLength=1*, *rank = 5*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 3 | 0-4 | +| 1 | 2 | 0,1,2,3,12 | +| 2 | 3 | 0,1,2,3,12 | +| 3-31 | Reserved | Reserved | + +**Table 7.3.1.1.2-59: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is configured, *maxLength=1*, *rank = 6*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|---------------| +| 0 | 3 | 0-5 | +| 1 | 2 | 0,1,2,3,12,14 | +| 2 | 3 | 0,1,2,3,12,14 | +| 3-31 | Reserved | Reserved | + +**Table 7.3.1.1.2-60: Antenna port(s), transform precoder is disabled, *dmrs-Type*=2, *enhanced-dmrs-Type* is configured, *maxLength*=1, rank = 7** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 2 | 0-3,12-14 | +| 1 | 3 | 0-3,12-14 | +| 2-31 | Reserved | Reserved | + +**Table 7.3.1.1.2-61: Antenna port(s), transform precoder is disabled, *dmrs-Type*=2, *enhanced-dmrs-Type* is configured, *maxLength*=1, rank = 8** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +|-------|------------------------------------------|--------------| +| 0 | 2 | 0-3,12-15 | +| 1 | 3 | 0-3,12-15 | +| 2-31 | Reserved | Reserved | + +**Table 7.3.1.1.2-62: Antenna port(s), transform precoder is disabled, *dmrs-Type*=2, *enhanced-dmrs-Type* is configured, *maxLength*=2, rank = 1** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 1 | 0 | 1 | +| 1 | 1 | 1 | 1 | +| 2 | 2 | 0 | 1 | +| 3 | 2 | 1 | 1 | +| 4 | 2 | 2 | 1 | +| 5 | 2 | 3 | 1 | +| 6 | 3 | 0 | 1 | +| 7 | 3 | 1 | 1 | +| 8 | 3 | 2 | 1 | +| 9 | 3 | 3 | 1 | +| 10 | 3 | 4 | 1 | +| 11 | 3 | 5 | 1 | +| 12 | 3 | 0 | 2 | +| 13 | 3 | 1 | 2 | +| 14 | 3 | 2 | 2 | +| 15 | 3 | 3 | 2 | +| 16 | 3 | 4 | 2 | +| 17 | 3 | 5 | 2 | +| 18 | 3 | 6 | 2 | +| 19 | 3 | 7 | 2 | +| 20 | 3 | 8 | 2 | +| 21 | 3 | 9 | 2 | +| 22 | 3 | 10 | 2 | +| 23 | 3 | 11 | 2 | +| 24 | 1 | 0 | 2 | +| 25 | 1 | 1 | 2 | +| 26 | 1 | 6 | 2 | +| 27 | 1 | 7 | 2 | +| 28 | 1 | 12 | 1 | +| 29 | 1 | 13 | 1 | +| 30 | 2 | 12 | 1 | +| 31 | 2 | 13 | 1 | +| 32 | 2 | 14 | 1 | +| 33 | 2 | 15 | 1 | +| 34 | 3 | 12 | 1 | +| 35 | 3 | 13 | 1 | +| 36 | 3 | 14 | 1 | +| 37 | 3 | 15 | 1 | +| 38 | 3 | 16 | 1 | +| 39 | 3 | 17 | 1 | +| 40 | 3 | 12 | 2 | +| 41 | 3 | 13 | 2 | +| 42 | 3 | 14 | 2 | + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 43 | 3 | 15 | 2 | +| 44 | 3 | 16 | 2 | +| 45 | 3 | 17 | 2 | +| 46 | 3 | 18 | 2 | +| 47 | 3 | 19 | 2 | +| 48 | 3 | 20 | 2 | +| 49 | 3 | 21 | 2 | +| 50 | 3 | 22 | 2 | +| 51 | 3 | 23 | 2 | +| 52 | 1 | 12 | 2 | +| 53 | 1 | 13 | 2 | +| 54 | 1 | 18 | 2 | +| 55 | 1 | 19 | 2 | +| 56-63 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-63: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is configured, *maxLength=2*, *rank = 2*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 1 | 0,1 | 1 | +| 1 | 2 | 0,1 | 1 | +| 2 | 2 | 2,3 | 1 | +| 3 | 3 | 0,1 | 1 | +| 4 | 3 | 2,3 | 1 | +| 5 | 3 | 4,5 | 1 | +| 6 | 2 | 0,2 | 1 | +| 7 | 3 | 0,1 | 2 | +| 8 | 3 | 2,3 | 2 | +| 9 | 3 | 4,5 | 2 | +| 10 | 3 | 6,7 | 2 | +| 11 | 3 | 8,9 | 2 | +| 12 | 3 | 10,11 | 2 | +| 13 | 1 | 0,1 | 2 | +| 14 | 1 | 6,7 | 2 | +| 15 | 2 | 0,1 | 2 | +| 16 | 2 | 2,3 | 2 | +| 17 | 2 | 6,7 | 2 | +| 18 | 2 | 8,9 | 2 | +| 19 | 1 | 12,13 | 1 | +| 20 | 2 | 12,13 | 1 | +| 21 | 2 | 14,15 | 1 | +| 22 | 3 | 12,13 | 1 | +| 23 | 3 | 14,15 | 1 | +| 24 | 3 | 16,17 | 1 | +| 25 | 3 | 12,13 | 2 | +| 26 | 3 | 14,15 | 2 | +| 27 | 3 | 16,17 | 2 | +| 28 | 3 | 18,19 | 2 | +| 29 | 3 | 20,21 | 2 | +| 30 | 3 | 22,23 | 2 | +| 31 | 1 | 12,13 | 2 | +| 32 | 1 | 18,19 | 2 | +| 33 | 2 | 12,13 | 2 | +| 34 | 2 | 14,15 | 2 | +| 35 | 2 | 18,19 | 2 | +| 36 | 2 | 20,21 | 2 | +| 37 | 3 | 13,15 | 1 | +| 38 | 2 | 13,15 | 1 | +| 39-63 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-64: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *multipanelScheme* is not configured to *sdmScheme*, *enhanced-dmrs-Type* is configured, *maxLength=2*, *rank = 3*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 2 | 0-2 | 1 | +| 1 | 3 | 0-2 | 1 | +| 2 | 3 | 3-5 | 1 | +| 3 | 3 | 0,1,6 | 2 | +| 4 | 3 | 2,3,8 | 2 | +| 5 | 3 | 4,5,10 | 2 | +| 6 | 1 | 0,1,12 | 1 | +| 7 | 2 | 0,1,12 | 1 | +| 8 | 2 | 2,3,14 | 1 | +| 9 | 3 | 0,1,12 | 1 | +| 10 | 3 | 2,3,14 | 1 | +| 11 | 3 | 4,5,16 | 1 | +| 12 | 3 | 7,12,13 | 2 | +| 13 | 3 | 9,14,15 | 2 | +| 14 | 3 | 11,16,17 | 2 | +| 15 | 3 | 9,18,19 | 2 | +| 16 | 3 | 18,19,20 | 2 | +| 17 | 3 | 21,22,23 | 2 | +| 18 | 3 | 13,15,17 | 1 | +| 19-63 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-64A: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *multipanelScheme* is configured to *sdmScheme*, *enhanced-dmrs-Type* is configured, *maxLength=2*, *rank = 3*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 2 | 0-2 | 1 | +| 1 | 3 | 0-2 | 1 | +| 2 | 3 | 3-5 | 1 | +| 3 | 3 | 0,1,6 | 2 | +| 4 | 3 | 2,3,8 | 2 | +| 5 | 3 | 4,5,10 | 2 | +| 6 | 1 | 0,1,12 | 1 | +| 7 | 2 | 0,1,12 | 1 | +| 8 | 2 | 2,3,14 | 1 | +| 9 | 3 | 0,1,12 | 1 | +| 10 | 3 | 2,3,14 | 1 | +| 11 | 3 | 4,5,16 | 1 | +| 12 | 3 | 7,12,13 | 2 | +| 13 | 3 | 9,14,15 | 2 | +| 14 | 3 | 11,16,17 | 2 | +| 15 | 3 | 9,18,19 | 2 | +| 16 | 3 | 18,19,20 | 2 | +| 17 | 3 | 21,22,23 | 2 | +| 18 | 3 | 13,15,17 | 1 | +| 19 | 2 | 0,2,3 | 1 | +| 20-63 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-65: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is configured, *maxLength=2*, *rank = 4*** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 2 | 0-3 | 1 | +| 1 | 3 | 0-3 | 1 | +| 2 | 3 | 0,1,6,7 | 2 | +| 3 | 3 | 2,3,8,9 | 2 | +| 4 | 3 | 4,5,10,11 | 2 | +| 5 | 3 | 12,13,18,19 | 2 | +| 6 | 3 | 14,15,20,21 | 2 | + +| | | | | +|-------|----------|-------------|----------| +| 7 | 3 | 16,17,22,23 | 2 | +| 8 | 1 | 0,1,12,13 | 1 | +| 9 | 2 | 0,1,12,13 | 1 | +| 10 | 2 | 2,3,14,15 | 1 | +| 11 | 3 | 0,1,12,13 | 1 | +| 12 | 3 | 2,3,14,15 | 1 | +| 13 | 3 | 4,5,16,17 | 1 | +| 14-63 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-66: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is configured, *maxLength=2*, rank = 5** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|--------------|------------------------------| +| 0 | 3 | 0-4 | 1 | +| 1 | 2 | 0,1,2,3,6 | 2 | +| 2 | 2 | 0,1,2,3,12 | 1 | +| 3 | 3 | 0,1,2,3,12 | 1 | +| 4 | 1 | 0,1,6,7,12 | 2 | +| 5 | 2 | 0,1,6,7,12 | 2 | +| 6 | 3 | 0,1,6,7,12 | 2 | +| 7-63 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-67: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is configured, *maxLength=2*, rank = 6** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|---------------|------------------------------| +| 0 | 3 | 0-5 | 1 | +| 1 | 2 | 0,1,2,3,6,8 | 2 | +| 2 | 2 | 0-3,12,14 | 1 | +| 3 | 3 | 0-3,12,14 | 1 | +| 4 | 1 | 0,1,6,7,12,18 | 2 | +| 5 | 2 | 0,1,6,7,12,18 | 2 | +| 6 | 3 | 0,1,6,7,12,18 | 2 | +| 7-63 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-68: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is configured, *maxLength=2*, rank = 7** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|------------------|------------------------------| +| 0 | 2 | 0,1,2,3,6,7,8 | 2 | +| 1 | 2 | 0-3,12-14 | 1 | +| 2 | 3 | 0-3,12-14 | 1 | +| 3 | 1 | 0,1,6,7,12,13,18 | 2 | +| 4 | 2 | 0,1,6,7,12,13,18 | 2 | +| 5 | 3 | 0,1,6,7,12,13,18 | 2 | +| 6-63 | Reserved | Reserved | Reserved | + +**Table 7.3.1.1.2-69: Antenna port(s), transform precoder is disabled, *dmrs-Type=2*, *enhanced-dmrs-Type* is configured, *maxLength=2*, rank = 8** + +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +|-------|------------------------------------------|---------------------|------------------------------| +| 0 | 2 | 0,1,2,3,6,7,8,9 | 2 | +| 1 | 2 | 0-3,12-15 | 1 | +| 2 | 3 | 0-3,12-15 | 1 | +| 3 | 1 | 0,1,6,7,12,13,18,19 | 2 | +| 4 | 2 | 0,1,6,7,12,13,18,19 | 2 | +| 5 | 3 | 0,1,6,7,12,13,18,19 | 2 | +| 6-63 | Reserved | Reserved | Reserved | + +##### 7.3.1.1.3 Format 0\_2 + +DCI format 0\_2 is used for the scheduling of PUSCH in one cell. + +The following information is transmitted by means of the DCI format 0\_2 with CRC scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI: + +- Identifier for DCI formats - 1 bit + - The value of this bit field is always set to 0, indicating an UL DCI format +- Carrier indicator - 0, 1, 2 or 3 bits determined by higher layer parameter *carrierIndicatorSizeDCI-0-2*, as defined in Clause 10.1 of [5, TS38.213]. This field is reserved when this format is carried by PDCCH on the primary cell and the UE is configured for scheduling on the primary cell from an SCell, with the same number of bits as that in this format carried by PDCCH on the SCell for scheduling on the primary cell. +- UL/SUL indicator - 0 bit for UEs not configured with *supplementaryUplink* in *ServingCellConfig* in the cell or UEs configured with *supplementaryUplink* in *ServingCellConfig* in the cell but only one carrier in the cell is configured for PUSCH transmission; otherwise, 1 bit as defined in Table 7.3.1.1.1-1. +- Bandwidth part indicator - 0, 1 or 2 bits as determined by the number of UL BWPs configured by higher layers, excluding the initial UL bandwidth part. The bitwidth for this field is determined as bits, where + - if *BWP-Id*, in which case the bandwidth part indicator is equivalent to the ascending order of the higher layer parameter *BWP-Id*; + - otherwise, in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1; + If a UE does not support active BWP change via DCI, the UE ignores this bit field. +- Frequency domain resource assignment - number of bits determined by the following: + - bits if only resource allocation type 0 is configured, where *resourceAllocationDCI-0-2-r16* is defined in Clause 6.1.2.2.1 of [6, TS 38.214] + - bits if only resource allocation type 1 is configured, or bits if *resourceAllocationDCI-0-2-r16* is configured as 'dynamicSwitch', where *NBWPUL* is the size of the active UL bandwidth part, is defined as in clause 4.4.4.4 of [4, TS 38.211] and is given by higher layer parameter *resourceAllocationType1GranularityDCI-0-2*. If the higher layer parameter *resourceAllocationType1GranularityDCI-0-2* is not configured, *NBWPUL* is equal to 1. + - If *resourceAllocationDCI-0-2-r16* is configured as 'dynamicSwitch', the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit value of 1 indicates resource allocation type 1. + - For resource allocation type 0, the LSBs provide the resource allocation as defined in Clause 6.1.2.2.1 of [6, TS 38.214]. + - For resource allocation type 1, the LSBs provide the resource allocation as follows: + - For PUSCH hopping with resource allocation type 1: + - MSB bits are used to indicate the frequency offset according to Clause 6.3 of [6, TS 38.214], where if the higher layer parameter *frequencyHoppingOffsetListsDCI-0-2* contains two offset values and if the higher layer parameter *frequencyHoppingOffsetListsDCI-0-2* contains four offset values + - bits provide the frequency domain resource allocation according to Clause 6.1.2.2.2 of [6, TS 38.214] + - For non-PUSCH hopping with resource allocation type 1: + - bits provide the frequency domain resource allocation according to Clause 6.1.2.2.2 of [6, TS 38.214] + If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if *resourceAllocationDCI-0-2-r16* is configured as 'dynamicSwitch' for the indicated bandwidth part, the UE assumes resource allocation type 0 for the indicated bandwidth part if the bitwidth of the "Frequency domain resource assignment" field of the active bandwidth part is smaller than the bitwidth of the "Frequency domain resource assignment" field of the indicated bandwidth part. +- Time domain resource assignment - 0, 1, 2, 3, 4, 5 or 6 bits as defined in Clause 6.1.2.1 of [6, TS38.214]. The bitwidth for this field is determined as bits, where *I* is the number of entries in the higher layer parameter *pusch-TimeDomainAllocationListDCI-0-2* if the higher layer parameter is configured, or *I* is the number of entries in the higher layer parameter *PUSCH-TimeDomainResourceAllocationList* if the higher layer parameter *PUSCH-TimeDomainResourceAllocationList* is configured and the higher layer parameter *pusch-TimeDomainAllocationListDCI-0-2* is not configured; otherwise *I* is the number of entries in the default table. +- Frequency hopping flag - 0 or 1 bit: + - 0 bit if the higher layer parameter *frequencyHoppingDCI-0-2* is not configured; + - 1 bit according to Table 7.3.1.1.1-3 otherwise, only applicable to resource allocation type 1, as defined in Clause 6.3 of [6, TS 38.214]. +- Modulation and coding scheme -5 bits as defined in Clause 6.1.4.1 of [6, TS 38.214] + +- New data indicator - 1 bit +- Redundancy version - 0, 1 or 2 bits determined by higher layer parameter *numberOfBitsForRV-DCI-0-2* + - If 0 bit is configured, *rvid* to be applied is 0; + - 1 bit according to Table 7.3.1.2.3-1; + - 2 bits according to Table 7.3.1.1.1-2. +- Transform precoder indicator - 0 or 1 bit + - 1 bit if the higher layer parameter *dynamicTransformPrecoderIndicationDCI-0-2* is configured to 'enabled' and if the UE is configured to monitor DCI format 0\_2 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI, where the bit value of 0 indicates that transform precoder is enabled and the bit value of 1 indicates that transform precoder is disabled. For a DCI format 0\_2 with CRC scrambled by CS-RNTI and the value indicated by new data indicator field is 0, or for a DCI format 0\_2 with CRC scrambled by SP-CSI-RNTI, the bit is reserved. + - 0 bit otherwise. +- HARQ process number - number of bits determined by the following: + - 5 bits determined by higher layer parameter *harq-ProcessNumberSizeDCI-0-2-v1700* if configured; + - otherwise 0, 1, 2, 3 or 4 bits determined by higher layer parameter *harq-ProcessNumberSizeDCI-0-2* +- Downlink assignment index - 0, 1, 2 or 4 bits + - 0 bit if the higher layer parameter *downlinkAssignmentIndexDCI-0-2* is not configured; + - 1, 2, 3, 4, 5 or 6 bits otherwise, + - 1st downlink assignment index - 1 or 2 bits: + - 1 bit for semi-static HARQ-ACK codebook for unicast and multicast if *pdsch-HARQ-ACK-Codebook = semiStatic* is configured for both unicast and multicast and the higher layer parameter *fdmed-ReceptionMulticast* is not configured; otherwise for semi-static HARQ-ACK codebook for unicast; + - 2 bits for dynamic HARQ-ACK codebook for unicast. + - 2nd downlink assignment index - 0 or 2 bits + - 2 bits for dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks for unicast; + - 0 bit otherwise. + - 3rd downlink assignment index - 0, 1 or 2 bits + - 1 bit for semi-static HARQ-ACK codebook for multicast if the higher layer parameter *fdmed-ReceptionMulticast* is configured; + - 2 bits for the dynamic HARQ-ACK codebook for multicast; + - 0 bit otherwise. + +When two HARQ-ACK codebooks are configured by *pdsch-HARQ-ACK-CodebookList* for the same serving cell and if higher layer parameter *priorityIndicatorDCI-0-2* is configured, if the bit width of the 1st or 2nd Downlink assignment index in DCI format 0\_2 for one HARQ-ACK codebook is not equal to that of the 1st or 2nd Downlink assignment index in DCI format 0\_2 for the other HARQ-ACK codebook, a number of most significant bits with value set to '0' are inserted to smaller 1st or 2nd Downlink assignment index until the bit width of the 1st or 2nd Downlink assignment index in DCI format 0\_2 for the two HARQ-ACK codebooks are the same. + +When two HARQ-ACK codebooks are configured by *pdsch-HARQ-ACK-CodebookListMulticast* for the same serving cell and if higher layer parameter *priorityIndicatorDCI-0-2* is configured, if the bit width of the 3rd downlink assignment index in DCI format 0\_2 for one HARQ-ACK codebook is not equal to that of the 3rd downlink assignment index in DCI format 0\_2 for the other HARQ-ACK codebook, a number of most significant bits with value set to '0' are inserted to smaller 3rd downlink assignment index until the bit width of the 3rd downlink assignment index in DCI format 0\_2 for the two HARQ-ACK codebooks are the same. + +- TPC command for scheduled PUSCH - 2 bits as defined in Clause 7.1.1 of [5, TS38.213] +- Second TPC command for scheduled PUSCH - 2 bits as defined in Clause 7.1.1 of [5, TS38.213] if higher layer parameter *SecondTPCFieldDCI-0-2* is configured; 0 bit otherwise. +- SRS resource set indicator - 0 or 2 bits + - 2 bits according to Table 7.3.1.1.2-36 if + - *txConfig = nonCodeBook*, and there are two SRS resource sets configured by *srs-ResourceSetToAddModListDCI-0-2* and associated with the *usage* of value 'nonCodeBook', and is not configured with *coresetPoolIndex* or the value of *coresetPoolIndex* is the same for all CORESETs if *coresetPoolIndex* is provided, or + +- *txConfig=codebook*, and there are two SRS resource sets configured by *srs-ResourceSetToAddModListDCI-0-2* and associated with *usage* of value '*codebook*', and is not configured with *coresetPoolIndex* or the value of *coresetPoolIndex* is the same for all CORESETs if *coresetPoolIndex* is provided; +- 0 bit otherwise. +- SRS resource indicator - number of bits determined by the following: + - bits according to Tables 7.3.1.1.2-28/28A/29/29B/30/30B/31/31B if the higher layer parameter *txConfig = nonCodebook*, where + - is the number of configured SRS resources in the SRS resource set indicated by SRS resource set indicator field if present, + - is the number of configured SRS resources in the SRS resource set associated with the *coresetPoolIndex* value for the CORESET used for the PDCCH carrying the DCI format 0\_2, if the UE is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with value 0 for the first CORESETs, and is provided *coresetPoolIndex* with value 1 for the second CORESETs, and is provided *enableSTx2PofmDCI*, + - otherwise is the number of configured SRS resources in the SRS resource set configured by higher layer parameter *srs-ResourceSetToAddModListDCI-0-2* and associated with the higher layer parameter *usage* of value '*nonCodeBook*', where the SRS resource set is composed of the first SRS resources together with other configurations in the SRS resource set, or in the SRS resource set with lower *srs-ResourceSetId* of two SRS resources sets, configured by higher layer parameter *srs-ResourceSetToAddModList*, if any, and associated with the higher layer parameter *usage* of value '*nonCodeBook*', except for the higher layer parameters '*srs-ResourceSetId*' and '*srs-ResourceIdList*', + - and + - if UE supports operation with *maxMIMO-LayersDCI-0-2* and the higher layer parameter *maxMIMO-LayersDCI-0-2* of *PUSCH-ServingCellConfig* of the serving cell is configured, + - $L_{max}$ is given by $\max\{maxMIMO-LayersDCI-0-2, maxMIMO-LayersforSdmDCI-0-2\}$ if *maxMIMO-LayersforSdmDCI-0-2* is configured + - $L_{max}$ is given by $\max\{maxMIMO-LayersDCI-0-2, maxMIMO-LayersforSfnDCI-0-2\}$ if *maxMIMO-LayersforSfnDCI-0-2* is configured + - $L_{max}$ is given by *maxMIMO-LayersDCI-0-2* otherwise + - otherwise, $L_{max}$ is given by the maximum number of layers for PUSCH supported by the UE for the serving cell for non-codebook based operation. + - bits according to Tables 7.3.1.1.2-32 if the higher layer parameter *txConfig = codebook*, where + - is the number of configured SRS resources in the SRS resource set indicated by SRS resource set indicator field if present, + - is the number of configured SRS resources in the SRS resource set associated with the *coresetPoolIndex* value for the CORESET used for the PDCCH carrying the DCI format 0\_2, if the UE is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with value 0 for the first CORESETs, and is provided *coresetPoolIndex* with value 1 for the second CORESETs, and is provided *enableSTx2PofmDCI*, + - otherwise is the number of configured SRS resources in the SRS resource set configured by higher layer parameter *srs-ResourceSetToAddModListDCI-0-2* and associated with the higher layer parameter *usage* of value '*codeBook*', where the SRS resource set is composed of the first SRS resources together with other configurations in the SRS resource set configured by higher layer parameter *srs-ResourceSetToAddModList*, if any, and associated with the higher layer parameter *usage* of value '*codeBook*', except for the higher layer parameters '*srs-ResourceSetId*' and '*srs-ResourceIdList*'. + +When the UE is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with value 0 for the first CORESETs, and is provided *coresetPoolIndex* with value 1 for the second CORESETs, and is provided *enableSTx2PofmDCI*, and there are two SRS resource sets configured by *srs-ResourceSetToAddModListDCI-0-2* and associated with *usage* of value '*codebook*' or '*nonCodeBook*', the first SRS resource set is associated with *coresetPoolIndex* value 0 and the second SRS resource set is associated with *coresetPoolIndex* value 1, where the first and the second SRS resource sets are respectively the ones with lower and higher *srs-ResourceSetId* of the two SRS resources sets, and the first and second SRS resource sets are composed of the first SRS resources together with other configurations in the first and second SRS resource sets configured by higher layer parameter *srs-ResourceSetToAddModList*, if any, and associated with the higher layer parameter *usage* of value '*codebook*' or '*nonCodeBook*', respectively, except for the higher layer parameters '*srs-ResourceSetId*' and '*srs-ResourceIdList*'. + +- Second SRS resource indicator - number of bits determined by the following: + - bits according to Tables 7.3.1.1.2-28/29A/30A/31A with the same number of layers indicated by SRS resource indicator field if the higher layer parameter *txConfig = nonCodebook*, the higher layer parameter *maxMIMO-LayersforSdmDCI-0-2* is not configured, and SRS resource set indicator field is present, where is the number of configured SRS resources in the second SRS resource set, and + +- if UE supports operation with *maxMIMO-LayersDCI-0-2* and the higher layer parameter *maxMIMO-LayersDCI-0-2* of *PUSCH-ServingCellConfig* of the serving cell is configured, + - $L_{max}$ is given by *maxMIMO-LayersforSfnDCI-0-2* if *maxMIMO-LayersforSfnDCI-0-2* is configured + - $L_{max}$ is given by *maxMIMO-LayersDCI-0-2* otherwise +- otherwise, $L_{max}$ is given by the maximum number of layers for PUSCH supported by the UE for the serving cell for non-codebook based operation. +- bits according to Tables 7.3.1.1.2-28/29 if the higher layer parameter *txConfig* = *nonCodebook*, the higher layer parameter *maxMIMO-LayersforSdmDCI-0-2* is configured and SRS resource set indicator field is present, where $n_{SRS}$ is the number of configured SRS resources in the second SRS resource set, where the second SRS resource set is composed of the first $n_{SRS}$ SRS resources together with other configurations in the SRS resource set, or in the SRS resource set with higher *srs-ResourceSetId* of two SRS resources sets, configured by higher layer parameter *srs-ResourceSetToAddModList*, if any, and associated with the higher layer parameter *usage* of value '*nonCodeBook*', except for the higher layer parameters '*srs-ResourceSetId*' and '*srs-ResourceIdList*', and $L_{max}$ is given by *maxMIMO-LayersforSdmDCI-0-2*. +- bits according to Tables 7.3.1.1.2-32 if the higher layer parameter *txConfig* = *codebook* and SRS resource set indicator field is present, where $n_{SRS}$ is the number of configured SRS resources in the second SRS resource set. +- 0 bit otherwise. +- Precoding information and number of layers - number of bits determined by the following: + - 0 bits if the higher layer parameter *txConfig* = *nonCodeBook*; + - 0 bits for 1 antenna port and if the higher layer parameter *txConfig* = *codebook*; + - 4, 5, or 6 bits according to Table 7.3.1.1.2-2 for 4 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, transform precoder is disabled, and according to the values of higher layer parameters *maxRankDCI-0-2* if *multipanelScheme* is not configured or $\max\{\text{maxRankDCI-0-2, maxRankSfnDCI-0-2}\}$ if *multipanelScheme* = *sfnScheme* or $\max\{\text{maxRankDCI-0-2, maxRankSdmDCI-0-2}\}$ if *multipanelScheme* = *sdmScheme*, and *codebookSubsetDCI-0-2*; + - 4 or 5 bits according to Table 7.3.1.1.2-2A for 4 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, the values of higher layer parameters *maxRankDCI-0-2* = 2 if *multipanelScheme* is not configured or $\max\{\text{maxRankDCI-0-2, maxRankSfnDCI-0-2}\} = 2$ if *multipanelScheme* = *sfnScheme* or $\max\{\text{maxRankDCI-0-2k, maxRankSdmDCI-0-2}\} = 2$ if *multipanelScheme* = *sdmScheme*, transform precoder is disabled, and according to the value of higher layer parameter *codebookSubsetDCI-0-2*; + - 4 or 6 bits according to Table 7.3.1.1.2-2B for 4 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, the values of higher layer parameters *maxRankDCI-0-2* = 3 or 4, transform precoder is disabled, and according to the value of higher layer parameter *codebookSubsetDCI-0-2*; + - 2, 4, or 5 bits according to Table 7.3.1.1.2-3 for 4 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to whether transform precoder is enabled or disabled, and *maxRankDCI-0-2* = 1 if *multipanelScheme* is not configured or $\max\{\text{maxRankDCI-0-2, maxRankSfnDCI-0-2}\} = 1$ if *multipanelScheme* = *sfnScheme* or $\max\{\text{maxRankDCI-0-2, maxRankSdmDCI-0-2}\} = 1$ if *multipanelScheme* = *sdmScheme*, and *codebookSubsetDCI-0-2*; + - 3 or 4 bits according to Table 7.3.1.1.2-3A for 4 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, *maxRankDCI-0-2* = 1 if *multipanelScheme* is not configured or $\max\{\text{maxRankDCI-0-2, maxRankSfnDCI-0-2}\} = 1$ if *multipanelScheme* = *sfnScheme* or $\max\{\text{maxRankDCI-0-2, maxRankSdmDCI-0-2}\} = 1$ if *multipanelScheme* = *sdmScheme*, and according to whether transform precoder is enabled or disabled, and the value of higher layer parameter *codebookSubsetDCI-0-2*; + - 2 or 4 bits according to Table 7.3.1.1.2-4 for 2 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, transform precoder is disabled, and according to the values of higher layer parameters *maxRankDCI-0-2* if *multipanelScheme* is not configured or $\max\{\text{maxRankDCI-0-2, maxRankSfnDCI-0-2}\}$ if *multipanelScheme* = *sfnScheme* or $\max\{\text{maxRankDCI-0-2, maxRankSdmDCI-0-2}\}$ if *multipanelScheme* = *sdmScheme*, and *codebookSubsetDCI-0-2*; + - 2 bits according to Table 7.3.1.1.2-4A for 2 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, transform precoder is disabled, the *maxRankDCI-0-2* = 2 if *multipanelScheme* is not configured or $\max\{\text{maxRankDCI-0-2, maxRankSfnDCI-0-2}\} = 2$ if *multipanelScheme* = *sfnScheme* or $\max\{\text{maxRankDCI-0-2, maxRankSdmDCI-0-2}\} = 2$ if *multipanelScheme* = *sdmScheme*, and *codebookSubsetDCI-0-2* = *nonCoherent*; + - 1 or 3 bits according to Table 7.3.1.1.2-5 for 2 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and + +according to whether transform precoder is enabled or disabled, and $maxRankDCI-0-2=1$ if *multipanelScheme* is not configured or $\max\{maxRankDCI-0-2, maxRankSfnDCI-0-2\}=1$ if *multipanelScheme* = *sfnScheme* or $\max\{maxRankDCI-0-2, maxRankSdmDCI-0-2\}=1$ if *multipanelScheme* = *sdmScheme*, and *codebookSubsetDCI-0-2*; + +- 2 bits according to Table 7.3.1.1.2-5A for 2 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, $maxRankDCI-0-2=1$ if *multipanelScheme* is not configured or $\max\{maxRankDCI-0-2, maxRankSfnDCI-0-2\}=1$ if *multipanelScheme* = *sfnScheme* or $\max\{maxRankDCI-0-2, maxRankSdmDCI-0-2\}=1$ if *multipanelScheme* = *sdmScheme*, and according to whether transform precoder is enabled or disabled, and the value of higher layer parameter *codebookSubsetDCI-0-2*. +- 7 bits according to Table 7.3.1.1.2-5D for 8 antenna ports by replacing *maxRank* with *maxRankDCI-0-2*, if *CodebookType* = *Codebook1*, transform precoder is disabled, $maxRankDCI-0-2=4$ , and according to *maxRankDCI-0-2*; +- 4, 6 or 7 bits according to Table 7.3.1.1.2-5E for 8 antenna ports by replacing *maxRank* with *maxRankDCI-0-2*, if *CodebookType* = *Codebook1*, transform precoder is enabled or $maxRankDCI-0-2=1, 2$ or $3$ if transform precoder is disabled, and according to transform precoder and *maxRankDCI-0-2*; +- 6 or 7 or 8 bits according to Table 7.3.1.1.2-5G for 8 antenna ports by replacing *maxRank* with *maxRankDCI-0-2*, if *CodebookType* = *Codebook4*, transform precoder is disabled, $maxRankDCI-0-2=2, 3$ or $4$ , *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to *maxRankDCI-0-2*; +- 3 bits according to Table 7.3.1.1.2-5H for 8 antenna ports by replacing *maxRank* with *maxRankDCI-0-2*, if *CodebookType* = *Codebook4*, transform precoder is enabled or $maxRankDCI-0-2=1$ if transform precoder is disabled, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*. +- 5, 9 or 10 bits according to Table 7.3.1.1.2-5J for 8 antenna ports by replacing *maxRank* with *maxRankDCI-0-2*, if *CodebookType* = *Codebook2*, transform precoder is enabled or $maxRankDCI-0-2=1, 2, 3$ or $4$ if transform precoder is disabled, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to transform precoder and *maxRankDCI-0-2*; +- 4, 7, 9 or 10 bits according to Table 7.3.1.1.2-5L for 8 antenna ports by replacing *maxRank* with *maxRankDCI-0-2*, if *CodebookType* = *Codebook3*, transform precoder is enabled or $maxRankDCI-0-2=1, 2, 3$ or $4$ if transform precoder is disabled, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to transform precoder and *maxRankDCI-0-2*; +- 6 or 7 or 8 bits according to Table 7.3.1.1.2-5M for 8 antenna ports by replacing *maxRank* with *maxRankDCI-0-2*, if *CodebookType* = *Codebook4*, transform precoder is disabled, $maxRankDCI-0-2=2, 3$ or $4$ , *ul-FullPowerTransmission* is configured to *fullpowerMode1*, and according to *maxRankDCI-0-2*; +- 4 bits according to Table 7.3.1.1.2-5N for 8 antenna ports, if *CodebookType* = *Codebook4*, transform precoder is enabled or $maxRankDCI-0-2=1$ if transform precoder is disabled, *ul-FullPowerTransmission* is configured to *fullpowerMode1*. +- 6, 9 or 10 bits according to Table 7.3.1.1.2-5O for 8 antenna ports by replacing *maxRank* with *maxRankDCI-0-2*, if *CodebookType* = *Codebook2*, transform precoder is enabled or $maxRankDCI-0-2=1, 2, 3$ or $4$ if transform precoder is disabled, *ul-FullPowerTransmission* is configured to *fullpowerMode1*, and according to transform precoder and *maxRankDCI-0-2*; +- 5, 7, 9 or 10 bits according to Table 7.3.1.1.2-5P for 8 antenna ports by replacing *maxRank* with *maxRankDCI-0-2*, if *CodebookType* = *Codebook3*, transform precoder is enabled or $maxRankDCI-0-2=1, 2, 3$ or $4$ if transform precoder is disabled, *ul-FullPowerTransmission* is configured to *fullpowerMode1*, and according to transform precoder and *maxRankDCI-0-2*; + +For the higher layer parameter *txConfig* = *codebook*, if *ul-FullPowerTransmission* is configured to *fullpowerMode2*, the values of higher layer parameters *maxRankDCI-0-2* is configured to be larger than 2, and at least one SRS resource with 4 antenna ports is configured in the SRS resource set indicated by SRS resource set indicator field if present, otherwise in an SRS resource set with usage set to 'codebook', and an SRS resource with 2 antenna ports is indicated via SRI in the same SRS resource set, then Table 7.3.1.1.2-4 is used. + +For the higher layer parameter *txConfig* = *codebook*, if different SRS resources with different number of antenna ports are configured, the bitwidth is determined according to the maximum number of ports in an SRS resource among the configured SRS resources in all SRS resource set(s) with usage set to 'codebook'. If the number of ports for a configured SRS resource in the set is less than the maximum number of ports in an SRS resource among the configured SRS resources, a number of most significant bits with value set to '0' are inserted to the field. + +For the higher layer parameter *txConfig* = *codebook*, when the Transform precoder indicator field is present, if the bit width of the Precoding information and number of layers field for the case with transform precoder enabled is not equal to that for the case with transform precoder disabled, a number of most significant bits with + +value set to '0' are inserted to the Precoding information and number of layers field for the case with smaller bit width until the bit width of the Precoding information and number of layers field for the two cases are the same. + +When the UE is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with value 0 for the first CORESETs, and is provided *coresetPoolIndex* with value 1 for the second CORESETs, and is provided *enableSTx2PofmDCI*, and there are two SRS resource sets configured by *srs-ResourceSetToAddModListDCI-0-2* and associated with *usage* of value 'codebook' or 'nonCodeBook', the Precoding information and number of layers field is associated with the SRS resource set that is associated with the *coresetPoolIndex* value for the CORESET used for the PDCCH carrying the DCI format 0\_2. + +- Second Precoding information - number of bits determined by the following: + - 0 bits if SRS resource set indicator field is not present; + - 0 bits if the higher layer parameter *txConfig* = *nonCodeBook*; + - 0 bits for 1 antenna port and if the higher layer parameter *txConfig* = *codebook*; + - 3, 4, or 5 bits according to Table 7.3.1.1.2-2C with the same number of layers indicated by Precoding information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present, *txConfig* = *codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, transform precoder is disabled, and according to the values of higher layer parameters *maxRankDCI-0-2* if *multipanelScheme* is not configured or *maxRankSfnDCI-0-2* if *multipanelScheme* = *sfnScheme*, and *codebookSubsetDCI-0-2*; + - 3 or 4 bits according to Table 7.3.1.1.2-2D with the same number of layers indicated by Precoding information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present, *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, the values of higher layer parameters *maxRankDCI-0-2* = 2 if *multipanelScheme* is not configured or *maxRankSfnDCI-0-2* = 2 if *multipanelScheme* = *sfnScheme*, transform precoder is disabled, and according to the value of higher layer parameter *codebookSubsetDCI-0-2*; + - 3 or 4 bits according to Table 7.3.1.1.2-2E with the same number of layers indicated by Precoding information and number of layers field for 4 antenna ports, if SRS resource set indicator field is present, *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, *maxRankDCI-0-2* = 3 or 4, transform precoder is disabled, and according to the value of higher layer parameter *codebookSubsetDCI-0-2*; + - 2, 4, or 5 bits according to Table 7.3.1.1.2-3 with the same number of layers indicated by Precoding information and number of layers field for 4 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters *maxRankDCI-0-2* if *multipanelScheme* is not configured or *maxRankSfnDCI-0-2* if *multipanelScheme* = *sfnScheme* and *codebookSubsetDCI-0-2*; + - 3 or 4 bits according to Table 7.3.1.1.2-3A with the same number of layers indicated by Precoding information and number of layers field for 4 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, *maxRankDCI-0-2* = 1 if *multipanelScheme* is not configured or *maxRankSfnDCI-0-2* = 1 if *multipanelScheme* = *sfnScheme*, and according to whether transform precoder is enabled or disabled, and the value of higher layer parameter *codebookSubsetDCI-0-2*; + - 1 or 3 bits according to Table 7.3.1.1.2-4B with the same number of layers indicated by Precoding information and number of layers field for 2 antenna ports, if SRS resource set indicator field is present, *txConfig* = *codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, transform precoder is disabled, and according to the values of higher layer parameters *maxRankDCI-0-2* if *multipanelScheme* is not configured or *maxRankSfnDCI-0-2* if *multipanelScheme* = *sfnScheme*, and *codebookSubsetDCI-0-2*; + - 2 bits according to Table 7.3.1.1.2-4C with the same number of layers indicated by Precoding information and number of layers field for 2 antenna ports, if SRS resource set indicator field is present, *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, transform precoder is disabled, the *maxRankDCI-0-2* = 2 if *multipanelScheme* is not configured or *maxRankSfnDCI-0-2* = 2 if *multipanelScheme* = *sfnScheme*, and *codebookSubsetDCI-0-2* = *nonCoherent*; + - 1 or 3 bits according to Table 7.3.1.1.2-5 with the same number of layers indicated by Precoding information and number of layers field for 2 antenna ports, if SRS resource set indicator field is present, *txConfig* = *codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters *maxRankDCI-0-2* if *multipanelScheme* is not configured or *maxRankSfnDCI-0-2* if *multipanelScheme* = *sfnScheme*, and *codebookSubsetDCI-0-2*; + - 2 bits according to Table 7.3.1.1.2-5A with the same number of layers indicated by Precoding information and number of layers field for 2 antenna ports, if SRS resource set indicator field is present, *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, *maxRankDCI-0-2* = 1 if *multipanelScheme* is not + +configured or $maxRankSfnDCI-0-2=1$ if $multipanelScheme = sfnScheme$ , and according to whether transform precoder is enabled or disabled, and the value of higher layer parameter $codebookSubsetDCI-0-2$ . + +For the higher layer parameter $txConfig=codebook$ , if $ul-FullPowerTransmission$ is configured to $fullpowerMode2$ , the values of higher layer parameters $maxRankDCI-0-2$ is configured to be larger than 2, and at least one SRS resource with 4 antenna ports is configured in the SRS resource set indicated by SRS resource set indicator field, and an SRS resource with 2 antenna ports is indicated via Second SRS resource indicator field in the same SRS resource set, then Table 7.3.1.1.2-4B is used. + +For the higher layer parameter $txConfig = codebook$ , if different SRS resources with different number of antenna ports are configured, the bitwidth is determined according to the maximum number of ports in an SRS resource among the configured SRS resources in the second SRS resource set with usage set to 'codebook' as defined in Table 7.3.1.1.2-36. If the number of ports for a configured SRS resource in the set is less than the maximum number of ports in an SRS resource among the configured SRS resources, a number of most significant bits with value set to '0' are inserted to the field. + +For the higher layer parameter $txConfig = codebook$ , when the Transform precoder indicator field is present, if the bit width of the Second Precoding information field for the case with transform precoder enabled is not equal to that for the case with transform precoder disabled, a number of most significant bits with value set to '0' are inserted to the Second Precoding information field for the case with smaller bit width until the bit width of the Second Precoding information field for the two cases are the same. + +- Antenna ports - number of bits determined by the following: + - 0 bit if higher layer parameter $antennaPortsFieldPresenceDCI-0-2$ is not configured; + - 2, 3, 4, 5 or 6 bits otherwise, + - 2 bits as defined by Tables 7.3.1.1.2-6, if transform precoder is enabled, $dmrs-Type=1$ , and $maxLength=1$ , except that $dmrs-UplinkTransformPrecoding$ and $tp-pi2BPSK$ are both configured and $\pi/2$ BPSK modulation is used; + - 2 bits as defined by 7.3.1.1.2-6A, if transform precoder is enabled, and $dmrs-UplinkTransformPrecoding$ and $tp-pi2BPSK$ are both configured, $\pi/2$ BPSK modulation is used, $dmrs-Type=1$ , and $maxLength=1$ , where $n_{scid}$ is the scrambling identity for antenna ports defined in Clause 6.4.1.1.1.2, in [4, TS38.211]; + - 4 bits as defined by Tables 7.3.1.1.2-7, if transform precoder is enabled, $dmrs-Type=1$ , and $maxLength=2$ , except that $dmrs-UplinkTransformPrecoding$ and $tp-pi2BPSK$ are both configured and $\pi/2$ BPSK modulation is used; + - 4 bits as defined by Tables 7.3.1.1.2-7A, if transform precoder is enabled, and $dmrs-UplinkTransformPrecoding$ and $tp-pi2BPSK$ are both configured, $\pi/2$ BPSK modulation is used, $dmrs-Type=1$ , and $maxLength=2$ , where $n_{scid}$ is the scrambling identity for antenna ports defined in Clause 6.4.1.1.1.2, in [4, TS38.211]; + - 3 bits as defined by Tables 7.3.1.1.2-8/9/10/10A/11 according to the value of rank, if transform precoder is disabled, $dmrs-Type=1$ , $enhanced-dmrs-Type$ is not configured, and $maxLength=1$ ; + - 4 bits as defined by Tables 7.3.1.1.2-12/13/14/14A/15 according to the value of rank, if transform precoder is disabled, $dmrs-Type=1$ , $enhanced-dmrs-Type$ is not configured, and $maxLength=2$ ; + - 4 bits as defined by Tables 7.3.1.1.2-16/17/18/18A/19 according to the value of rank, if transform precoder is disabled, $dmrs-Type=2$ , $enhanced-dmrs-Type$ is not configured, and $maxLength=1$ ; + - 5 bits as defined by Tables 7.3.1.1.2-20/21/22/22A/23 according to the value of rank, if transform precoder is disabled, $dmrs-Type=2$ , $enhanced-dmrs-Type$ is not configured, and $maxLength=2$ . + - 4 bits as defined by Tables 7.3.1.1.2-38/39/40/40A/41, if transform precoder is disabled, $dmrs-Type=1$ , $enhanced-dmrs-Type$ is configured, and $maxLength=1$ ; + - 5 bits as defined by Tables 7.3.1.1.2-46/47/48/48A/49, if transform precoder is disabled, $dmrs-Type=1$ , $enhanced-dmrs-Type$ is configured, and $maxLength=2$ ; + - 5 bits as defined by Tables 7.3.1.1.2-54/55/56/56A/57, if transform precoder is disabled, $dmrs-Type=2$ , $enhanced-dmrs-Type$ is configured, and $maxLength=1$ ; + - 6 bits as defined by Tables 7.3.1.1.2-62/63/64/64A/65, if transform precoder is disabled, $dmrs-Type=2$ , $enhanced-dmrs-Type$ is configured, and $maxLength=2$ . + +where the number of CDM groups without data of values 1, 2, and 3 in Tables 7.3.1.1.2-6 to 7.3.1.1.2-23 refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively, and the value of rank is + +- the sum of the value determined according to the SRS resource indicator field and the value determined according to the second SRS resource indicator field, if $txConfig = nonCodebook$ and $multipanelScheme = sdmScheme$ and SRS resource set indicator field equals "10" +- the sum of the value determined according to the Precoding information and number of layers field and the value determined according to the Second Precoding information, if $txConfig = codebook$ and $multipanelScheme = sdmScheme$ and SRS resource set indicator field equals "10" + +- determined according to the SRS resource indicator field if the higher layer parameter *txConfig* = *nonCodebook* and *multipanelScheme* = *sdmScheme* is not configured, , or if the higher layer parameter *txConfig* = *nonCodebook*, *multipanelScheme* = *sdmScheme* and SRS resource set indicator field equals "00" or "01" +- determined according to the Precoding information and number of layers field if the higher layer parameter *txConfig* = *codebook* and *multipanelScheme* = *sdmScheme* is not configured, or if the higher layer parameter *txConfig* = *codebook*, *multipanelScheme* = *sdmScheme* and SRS resource set indicator field equals "00" or "01". + +If a UE is configured with both *dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2* and *dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2* and is configured with *antennaPortsFieldPresenceDCI-0-2*, the bitwidth of this field equals , where is the "Antenna ports" bitwidth derived according to *dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2* and is the "Antenna ports" bitwidth derived according to *dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2*. A number of zeros are padded in the MSB of this field, if the mapping type of the PUSCH corresponds to the smaller value of and . + +If a UE is not configured with higher layer parameter *antennaPortsFieldPresenceDCI-0-2*, antenna port(s) are defined assuming bit field index value 0 in Tables 7.3.1.1.2-6 to 7.3.1.1.2-23. + +When the Transform precoder indicator field is present, if the bit width of the Antenna ports field for the case with transform precoder enabled is not equal to that for the case with transform precoder disabled, a number of most significant bits with value set to '0' are inserted to the Antenna ports field for the case with smaller bit width until the bit width of the Antenna ports field for the two cases are the same. + +- SRS request - 0, 1, 2 or 3 bits + - 0 bit if the higher layer parameter *srs-RequestDCI-0-2* is not configured; + - 1 bit as defined by Table 7.3.1.1.3-1 if higher layer parameter *srs-RequestDCI-0-2* = 1 and for UEs not configured with *supplementaryUplink* in *ServingCellConfig* in the cell; + - 2 bits if higher layer parameter *srs-RequestDCI-0-2* = 1 and for UEs configured with *supplementaryUplink* in *ServingCellConfig* in the cell, where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-1 and the second bit is defined by Table 7.3.1.1.3-1; + - 2 bits as defined by Table 7.3.1.1.2-24 if higher layer parameter *srs-RequestDCI-0-2* = 2 and for UEs not configured with *supplementaryUplink* in *ServingCellConfig* in the cell; + - 3 bits if higher layer parameter *srs-RequestDCI-0-2* = 2 and for UEs configured with *supplementaryUplink* in *ServingCellConfig* in the cell, where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-1 and the second and third bits are defined by Table 7.3.1.1.2-24; +- SRS offset indicator - 0, 1 or 2 bits. + - 0 bit if higher layer parameter *AvailableSlotOffset* is not configured for any aperiodic SRS resource set in the scheduled cell, or if higher layer parameter *AvailableSlotOffset* is configured for at least one aperiodic SRS resource set in the scheduled cell and the maximum number of entries of *availableSlotOffsetList* configured for all aperiodic SRS resource set(s) is 1; + - otherwise, bits are used to indicate available slot offset according to Table 7.3.1.1.2-37 and Clause 6.2.1 of [6, TS 38.214], where K is the maximum number of entries of *availableSlotOffsetList* configured for all aperiodic SRS resource set(s) in the scheduled cell; +- CSI request - 0, 1, 2, 3, 4, 5, or 6 bits determined by higher layer parameter *reportTriggerSizeDCI-0-2*. +- PTRS-DMRS association - number of bits determined as follows + - 0 bit if *PTRS-UplinkConfig* is not configured in either *dmrs-UplinkForPUSCH-MappingTypeA* or *dmrs-UplinkForPUSCH-MappingTypeB* and transform precoder is disabled, or if transform precoder is enabled, or if *maxRankDCI-0-2*=1 and *multipanelScheme* is not configured, or if *maxRankDCI-0-2*=1 and *maxRankSfnDCI-0-2*=1, or if *maxRankDCI-0-2*=1 and *maxRankSdmDCI-0-2*=1 when two PTRS ports are configured by *maxNrofPortsforSdm*; + - 2 bits otherwise, where Table 7.3.1.1.2-25/7.3.1.1.2-25A/7.3.1.1.2-25B/7.3.1.1.2-26 are used to indicate the association between PTRS port(s) and DMRS port(s), and the DMRS ports are indicated by the Antenna ports field. + - When one PTRS port or two PTRS ports are configured by *maxNrofPorts* in *PTRS-UplinkConfig*, SRS resource set indicator field is absent or SRS resource set indicator field is present and equals "00" or "01" and *maxRankDCI-0-2*≤4, this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to SRS resource indicator field and/or Precoding information and number of layers field according to Table 7.3.1.1.2-25 and 7.3.1.1.2-26. + - When one PTRS port or two PTRS ports are configured by *maxNrofPorts* in *PTRS-UplinkConfig*, the SRS resource set indicator field is present and equals "10" or "11", *maxRankDCI-0-2*=3 or 4 and + +*multipanelScheme* is not configured, this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to SRS resource indicator field and/or Precoding information and number of layers field according to Table 7.3.1.1.2-25 and 7.3.1.1.2-26. + +- When one PTRS port is configured by *maxNrofPorts* in *PTRS-UplinkConfig*, the SRS resource set indicator field is present and equals "10" and "11" and *maxRankDCI-0-2*=2 and *multipanelScheme* is not configured, the MSB of this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to SRS resource indicator field and/or Precoding information and number of layers field, and the LSB of this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to Second SRS resource indicator field and/or Second Precoding information field, according to Table 7.3.1.1.2-25A. +- When two PTRS ports are configured by *maxNrofPorts* in *PTRS-UplinkConfig*, the SRS resource set indicator field is present and equals "10" and *multipanelScheme* is configured to *sdmScheme*, the MSB of this field indicates the association between PTRS port 0 and DMRS port(s) corresponding to SRS resource indicator field and/or Precoding information and number of layers field, and the LSB of this field indicates the association between PTRS port 1 and DMRS port(s) corresponding to Second SRS resource indicator field and/or Second Precoding information field, according to Table 7.3.1.1.2-25A. +- When one PTRS port is configured by *maxNrofPortsforSDM* in *PTRS-UplinkConfig*, SRS resource set indicator field is present and equals "10" and *multipanelScheme* is configured to *sdmScheme*, this field indicates the association between PTRS port and DMRS ports corresponding to SRS resource indicator field and Second SRS resource indicator field and/or Precoding information and number of layers field and Second Precoding information field according to Table 7.3.1.1.2-25. +- When one PTRS port or two PTRS ports are configured by *maxNrofPorts* in *PTRS-UplinkConfig*, SRS resource set indicator field is present and equals "10", *multipanelScheme* is configured to *sfnScheme*, this field indicates the association between PTRS port(s) and DMRS port(s) corresponding to SRS resource indicator field and/or Precoding information and number of layers field according to Table 7.3.1.1.2-25 and 7.3.1.1.2-26. + +If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and the "PTRS-DMRS association" field is present for the indicated bandwidth part but not present for the active bandwidth part, the UE assumes the "PTRS-DMRS association" field is not present for the indicated bandwidth part. + +When the Transform precoder indicator field is present, if the bit width of PTRS-DMRS association field for the case with transform precoder enabled is not equal to that for the case with transform precoder disabled, a number of most significant bits with value set to '0' are inserted to the PTRS-DMRS association field for the case with smaller bit width until the bit width of the PTRS-DMRS association field for the two cases are the same. + +- Second PTRS-DMRS association - 2 bits if PTRS-DMRS association field and SRS resource set indicator field are present and *maxRankDCI-0-2*>2 and *multipanelScheme* is not configured; 0 bit otherwise. Table 7.3.1.1.2-25 and 7.3.1.1.2-26 are used to indicate the association between PTRS port(s) and DMRS port(s) corresponding to Second SRS resource indicator field and/or Second precoding information field when one PT-RS port and two PT-RS ports are configured by *maxNrofPorts* in *PTRS-UplinkConfig* respectively, and the DMRS ports are indicated by the Antenna ports field. +- *beta\_offset* indicator - 0 bit if the higher layer parameter *betaOffsetsDCI-0-2* = *semiStaticDCI-0-2*; otherwise 1 bit if 2 offset indexes are configured by higher layer parameter *dynamicDCI-0-2* as defined by Table 9.3-3A in [5, TS 38.213], and 2 bits if 4 offset indexes are configured by higher layer parameter *dynamicDCI-0-2* as defined by Table 9.3-3 in [5, TS 38.213]. + +When two HARQ-ACK codebooks are configured by *pdsch-HARQ-ACK-CodebookList* or by *pdsch-HARQ-ACK-CodebookListMulticast* for the same serving cell and if higher layer parameter *priorityIndicatorDCI-0-2* is configured, if the bit width of the *beta\_offset* indicator in DCI format 0\_2 for one HARQ-ACK codebook is not equal to that of the *beta\_offset* indicator in DCI format 0\_2 for the other HARQ-ACK codebook, a number of most significant bits with value set to '0' are inserted to smaller *beta\_offset* indicator until the bit width of the *beta\_offset* indicator in DCI format 0\_2 for the two HARQ-ACK codebooks are the same. + +- DMRS sequence initialization - 0 or 1 bit + - 0 bit if the higher layer parameter *dmrs-SequencInitializationDCI-0-2* is not configured, or if transform precoder is enabled by higher layers and the Transform precoder indicator field is not present; + - 1 bit if transform precoder is disabled by higher layers and the higher layer parameter *dmrs-SequencInitializationDCI-0-2* is configured, or if the Transform precoder indicator field is present and the higher layer parameter *dmrs-SequencInitializationDCI-0-2* is configured. If the Transform precoder indicator field is present and set to '0', the bit is reserved. + +- UL-SCH indicator - 1 bit. A value of "1" indicates UL-SCH shall be transmitted on the PUSCH and a value of "0" indicates UL-SCH shall not be transmitted on the PUSCH. If a UE does not support triggering SRS only in DCI, except for DCI format 0\_2 with CRC scrambled by SP-CSI-RNTI, the UE is not expected to receive a DCI format 0\_2 with UL-SCH indicator of "0" and CSI request of all zero(s). If a UE supports triggering SRS only in DCI, except for DCI format 0\_2 with CRC scrambled by SP-CSI-RNTI, the UE is not expected to receive a DCI format 0\_2 with UL-SCH indicator of "0", CSI request of all zero(s) and SRS request of all zero(s). +- ChannelAccess-CPext-CAPC - 0, 1, 2, 3, 4, 5 or 6 bits. The bitwidth for this field is determined as $I$ bits, where $I$ is the number of entries in the higher layer parameter *ul-AccessConfigListDCI-0-2* or in Table 7.3.1.1.1-4A if *channelAccessMode-r16* = "semiStatic" is provided, for operation in a cell with shared spectrum channel access in frequency range 1, or the number of entries in the high layer parameter *ul-AccessConfigListDCI-0-1* for operation in frequency range 2-2 if *ChannelAccessMode2-r17* is provided; otherwise 0 bit. One or more entries from Table 7.3.1.1.2-35 are configured by the higher layer parameter *ul-AccessConfigListDCI-0-2* in frequency range 1. One or more entries from Table 7.3.1.1.2-35A are configured by the higher layer parameter *ul-AccessConfigListDCI-0-1* in frequency range 2-2. +- Open-loop power control parameter set indication - 0 or 1 or 2 bits. + - 0 bit if the higher layer parameter *p0-PUSCH-SetList* is not configured; + - 1 or 2 bits otherwise, + - 1 bit if SRS resource indicator is present in the DCI format 0\_2; + - 1 or 2 bits as determined by higher layer parameter *olpc-ParameterSetDCI-0-2* if SRS resource indicator is not present in the DCI format 0\_2; +- Priority indicator - 0 bit if higher layer parameter *priorityIndicatorDCI-0-2* is not configured; otherwise 1 bit as defined in Clause 9 in [5, TS 38.213]. +- Invalid symbol pattern indicator - 0 bit if higher layer parameter *invalidSymbolPatternIndicatorDCI-0-2* is not configured; otherwise 1 bit as defined in Clause 6.1.2.1 in [6, TS 38.214]. +- PDCCH monitoring adaptation indication - 0, 1 or 2 bits + - 1 or 2 bits, if *searchSpaceGroupIdList-r17* is not configured and if *pdcch-SkippingDurationList* is configured + - 1 bit if the UE is configured with only one duration by *pdcch-SkippingDurationList*; + - 2 bits if the UE is configured with more than one duration by *pdcch-SkippingDurationList*. + - 1 or 2 bits, if *pdcch-SkippingDurationList* is not configured and if *searchSpaceGroupIdList-r17* is configured + - 1 bit if the UE is configured by *searchSpaceGroupIdList-r17* with search space set(s) with group index 0 and search space set(s) with group index 1, and if the UE is not configured by *searchSpaceGroupIdList-r17* with any search space set with group index 2; + - 2 bits if the UE is configured by *searchSpaceGroupIdList-r17* with search space set(s) with group index 0, search space set(s) with group index 1 and search space set(s) with group index 2; + - 2 bits, if *pdcch-SkippingDurationList* is configured and if *searchSpaceGroupIdList-r17* is configured + - 0 bit, otherwise + +A UE does not expect that the bit width of a field in DCI format 0\_2 with CRC scrambled by CS-RNTI is larger than corresponding bit width of same field in DCI format 0\_2 with CRC scrambled by C-RNTI for the same serving cell. If the bit width of a field in the DCI format 0\_2 with CRC scrambled by CS-RNTI is not equal to that of the corresponding field in the DCI format 0\_2 with CRC scrambled by C-RNTI for the same serving cell, a number of most significant bits with value set to '0' are inserted to the field in DCI format 0\_2 with CRC scrambled by CS-RNTI until the bit width equals that of the corresponding field in the DCI format 0\_2 with CRC scrambled by C-RNTI for the same serving cell. + +For a UE configured with scheduling on the primary cell from an SCell, if prior to padding the number of information bits in DCI format 0\_2 carried by PDCCH on the primary cell is not equal to the number of information bits in DCI format 0\_2 carried by PDCCH on the SCell for scheduling on the primary cell, zeros shall be appended to the DCI format 0\_2 with smaller size until the payload size is the same. + +- If application of step 4B in clause 7.3.1.0 results in additional zero padding for DCI format 0\_2 for scheduling on the primary cell, corresponding zeros shall be appended to both DCI format 0\_2 monitored on the primary cell and DCI format 0\_2 monitored on the SCell for scheduling on the primary cell. +- If the SCell is deactivated and *firstActiveDownlinkBWP-Id* is not set to dormant BWP, the UE determines the number of information bits in DCI format 0\_2 carried by PDCCH on the primary cell based on a DL BWP provided by *firstActiveDownlinkBWP-Id* for the SCell. If the active DL BWP of the SCell is a dormant DL BWP, or if the SCell is deactivated and *firstActiveDownlinkBWP-Id* is set to dormant BWP, the UE determines the number of information bits in DCI format 0\_2 carried by PDCCH on the primary cell based on a DL BWP + +provided by *firstWithinActiveTimeBWP-Id* for the SCell if provided; otherwise, based on a DL BWP provided by *firstOutsideActiveTimeBWP-Id* for the SCell. + +**Table 7.3.1.1.3-1: 1 bit SRS request in DCI format 0\_2 and DCI format 1\_2** + +| Value of SRS request field | Triggered aperiodic SRS resource set(s) for DCI format 0_2 and 1_2 | +|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | No aperiodic SRS resource set triggered | +| 1 | SRS resource set(s) configured with higher layer parameter aperiodicSRS-ResourceTrigger set to 1 or an entry in aperiodicSRS-ResourceTriggerList set to 1 | + +##### 7.3.1.1.4 Format 0\_3 + +DCI format 0\_3 is used for the scheduling of one PUSCH in one cell, or multiple PUSCHs in multiple cells with one PUSCH per cell. + +The following information is transmitted by means of the DCI format 0\_3 with CRC scrambled by C-RNTI or MCS-C-RNTI: + +- Identifier for DCI formats - 1 bit + - The value of this bit field is always set to 0, indicating an UL DCI format +- Scheduled cell set indicator - bits, where $N$ is the number of cell sets which are configured by higher layer parameter *MC-DCI-SetofCellsToAddModList* to be respectively scheduled by DCI format 0\_3/1\_3 from the cell on which this format is carried by PDCCH. If present, this field is used to indicate the scheduled cell set according to Table 7.3.1.1.4-1; otherwise, the scheduled cell set is the cell set configured to be scheduled by DCI format 0\_3/1\_3 from the cell by higher layer parameter *MC-DCI-SetofCellsToAddModList*. +- Scheduled cells indicator - number of bits determined by the following: + - 0 bit if the higher layer parameter *ScheduledCellCombo-ListDCI-0-3* for the scheduled cell set is not configured; + - otherwise $N$ bits indicating the scheduled cells in the scheduled cell set according to Table 7.3.1.1.4-2, where $N$ is the number of entries in the higher layer parameter *ScheduledCellCombo-ListDCI-0-3*. If only one entry is configured in the higher layer parameter *ScheduledCellCombo-ListDCI-0-3*, the scheduled cells are the cells configured by higher layer parameter *ScheduledCellCombo-ListDCI-0-3*. +- Bandwidth part indicator - 0, 1 or 2 bits determined as $M$ , where + - if $M$ is the maximum number of UL BWPs configured by higher layers, excluding the initial UL bandwidth part, across all the cells configured by higher layer parameter *ScheduledCell-ListDCI-0-3* in the scheduled cell set, in which case the bandwidth part indicator is equivalent to the ascending order of the higher layer parameter *BWP-Id*; + - otherwise $M$ , in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1; +The field is only applicable to a scheduled cell with the number of configured UL BWPs larger than 1, including the initial UL bandwidth part, and is applied to the applicable scheduled cells in the scheduled cell set independently. If a UE does not support active BWP change via DCI, the UE ignores this bit field. If this field indicates a code point that does not correspond to a configured BWP of a scheduled cell, the UE ignores this bit field for the scheduled cell, and operates on the active BWP of the scheduled cell. +- Frequency domain resource assignment - number of bits determined by the following, where $N$ is the size of the active UL bandwidth part: + - block number 1, block number 2, ..., block number $N$ +If *ScheduledCellCombo-ListDCI-0-3* for the scheduled cell set is configured with more than one entry, $N$ is the number of scheduled cells indicated by Scheduled cells indicator field; if *ScheduledCellCombo-ListDCI-0-3* for the scheduled cell set is configured with only one entry, $N$ is the number of cells configured by higher layer parameter *ScheduledCellCombo-ListDCI-0-3*; otherwise, $N$ is the number of cells configured by higher layer parameter *ScheduledCell-ListDCI-0-3* in the scheduled cell set. Each block corresponds to the frequency domain resource assignment for a cell, and the blocks are placed according to an ascending order of a serving cell index, with block number 1 corresponding to the frequency domain resource assignment for the cell with the smallest serving cell index. Each block is defined by the following fields: + - If higher layer parameter *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated* is not configured + +- bits if only resource allocation type 0 is configured, where is defined in Clause 6.1.2.2.1 of [6, TS 38.214] +- bits if only resource allocation type 1 is configured, or bits if *resourceAllocationDCI-0-3* is configured as '*dynamicSwitch*', where is the size of the active UL bandwidth part, is defined as in clause 4.4.4.4 of [4, TS 38.211] and is given by higher layer parameter *resourceAllocationType1GranularityDCI-0-3*. If the higher layer parameter *resourceAllocationType1GranularityDCI-0-3* is not configured, is equal to 1. +- If *resourceAllocationDCI-0-3* is configured as '*dynamicSwitch*', the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit value of 1 indicates resource allocation type 1. +- For resource allocation type 0, the LSBs provide the resource allocation as defined in Clause 6.1.2.2.1 of [6, TS 38.214]. +- For resource allocation type 1, the LSBs provide the resource allocation as follows: + - For PUSCH hopping with resource allocation type 1: + - MSB bits are used to indicate the frequency offset according to Clause 6.3 of [6, TS 38.214], where if the higher layer parameter *frequencyHoppingOffsetLists* contains two offset values and if the higher layer parameter *frequencyHoppingOffsetLists* contains four offset values + - bits provide the frequency domain resource allocation according to Clause 6.1.2.2.2 of [6, TS 38.214] + - For non-PUSCH hopping with resource allocation type 1: + - bits provide the frequency domain resource allocation according to Clause 6.1.2.2.2 of [6, TS 38.214] + +If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if *resourceAllocationDCI-0-3* is configured as '*dynamicSwitch*' for the indicated bandwidth part, the UE assumes resource allocation type 0 for the indicated bandwidth part if the bitwidth of the "Frequency domain resource assignment" field of the active bandwidth part is smaller than the bitwidth of the "Frequency domain resource assignment" field of the indicated bandwidth part. + +- If the higher layer parameter *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated* is configured + - $5 + Y$ bits provide the frequency domain resource allocation according to Clause 6.1.2.2.3 of [6, TS 38.214] if the subcarrier spacing for the active UL bandwidth part is 30 kHz. The 5 MSBs provide the interlace allocation and the Y LSBs provide the RB set allocation. + - $6 + Y$ bits provide the frequency domain resource allocation according to Clause 6.1.2.2.3 of [6, TS 38.214] if the subcarrier spacing for the active UL bandwidth part is 15 kHz. The 6 MSBs provide the interlace allocation and the Y LSBs provide the RB set allocation. + +The value of Y is determined by where is the number of RB sets contained in the active UL BWP as defined in clause 7 of [6, TS38.214]. + +If the higher layer parameter *ScheduledCellCombo-ListDCI-0-3* for the scheduled cell set is not configured, each block is also used to indicate whether the corresponding cell is scheduled or not as follows: + +- if all bits of a block are set to 0 for resource allocation type 0, or set to 1 for resource allocation type 1, or set to 0 or 1 for dynamic switch resource allocation type, or set to 0 for resource allocation type 2 with $\mu=1$ , or set to 1 for resource allocation type 2 with $\mu=0$ , the cell corresponding to the block is not scheduled; +- otherwise, the cell corresponding to the block is scheduled. +- Time domain resource assignment - bits, where is the number of entries in the higher layer parameter *TDRA-FieldIndexListDCI-0-3*. This field is used to indicate an entry in the higher layer parameter *TDRA-FieldIndexListDCI-0-3* according to Table 7.3.1.1.4-3. Each entry in the higher layer parameter *TDRA-FieldIndexListDCI-0-3* contains the 'Time domain resource assignment' index for each BWP of each cell in the scheduled cell set, where the 'Time domain resource assignment' indexes for all the cells are placed according to an ascending order of a serving cell index, and the 'Time domain resource assignment' indexes for all the BWPs of a cell are placed according to an ascending order of the higher layer parameter *BWP-Id*. +- Frequency hopping flag - 0 or 1 bit + - 0 bit if the higher layer parameter *frequencyHopping* is not configured for any cell configured by higher layer parameter *ScheduledCell-ListDCI-0-3* in the scheduled cell set; + - 1 bit according to Table 7.3.1.1.1-3 otherwise, only applicable to resource allocation type 1, as defined in Clause 6.3 of [6, TS 38.214]. + +The field is only applicable to a scheduled cell configured with *frequencyHopping*, and is applied to the applicable scheduled cells independently. + +- Modulation and coding scheme - number of bits determined by the following: + +- block number 1, block number 2, ..., block number + +Each block corresponds to the modulation and coding scheme for a scheduled cell, and the blocks are placed according to an ascending order of a serving cell index, with block number 1 corresponding to the modulation and coding scheme for the cell with the smallest serving cell index. Each block is 5 bits as defined in Clause 6.1.4.1 of [6, TS 38.214]. + +- New data indicator - number of bits determined by the following: + +- block number 1, block number 2, ..., block number + +Each block corresponds to the new data indicator for a scheduled cell, and the blocks are placed according to an ascending order of a serving cell index, with block number 1 corresponding to the new data indicator for the cell with the smallest serving cell index. Each block is 1 bit. + +- Redundancy version - number of bits determined by the following: + +- block number 1, block number 2, ..., block number + +Each block corresponds to the redundancy version for a scheduled cell, and the blocks are placed according to an ascending order of a serving cell index, with block number 1 corresponding to the redundancy version for the cell with the smallest serving cell index. Each block is 0, 1 or 2 bits determined by higher layer parameter *numberOfBitsForRV-DCI-0-3* configured for the cell corresponding to the block, + +- If 0 bit is configured, *rvid* to be applied is 0; +- 1 bit according to Table 7.3.1.2.3-1; +- 2 bits according to Table 7.3.1.1.1-2. + +- HARQ process number - number of bits determined by the following: + +- block number 1, block number 2, ..., block number + +Each block corresponds to the HARQ process number for a scheduled cell, and the blocks are placed according to an ascending order of a serving cell index, with block number 1 corresponding to the HARQ process number for the cell with the smallest serving cell index. Each block is 0, 1, 2, 3, 4 or 5 bits determined by higher layer parameter *harq-ProcessNumberSizeDCI-0-3* configured for the cell corresponding to the block. + +- 1st downlink assignment index - 1 or 2 bits + +- 1 bit for semi-static HARQ-ACK codebook; +- 2 bits for dynamic HARQ-ACK codebook. + +When two HARQ-ACK codebooks are configured for the same serving cell and if higher layer parameter *priorityIndicatorDCI-0-3* is configured, if the bit width of the 1st downlink assignment index in DCI format 0\_3 for one HARQ-ACK codebook is not equal to that of the 1st downlink assignment index in DCI format 0\_3 for the other HARQ-ACK codebook, a number of most significant bits with value set to '0' are inserted to smaller 1st downlink assignment index until the bit width of the 1st downlink assignment index in DCI format 0\_3 for the two HARQ-ACK codebooks are the same. + +- 2nd downlink assignment index - 0 or 2 bits: + +- 2 bits for dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks; +- 0 bit otherwise. + +When two HARQ-ACK codebooks are configured for the same serving cell and if higher layer parameter *priorityIndicatorDCI-0-3* is configured, if the bit width of the 2nd downlink assignment index in DCI format 0\_3 for one HARQ-ACK codebook is not equal to that of the 2nd downlink assignment index in DCI format 0\_3 for the other HARQ-ACK codebook, a number of most significant bits with value set to '0' are inserted to smaller 2nd downlink assignment index until the bit width of the 2nd downlink assignment index in DCI format 0\_3 for the two HARQ-ACK codebooks are the same. + +- TPC command for scheduled PUSCH - number of bits determined by the following: + +- block number 1, block number 2, ..., block number + +Each block corresponds to the TPC command for the scheduled PUSCH for a scheduled cell, and the blocks are placed according to an ascending order of a serving cell index, with block number 1 corresponding to the TPC command for the scheduled PUSCH for the cell with the smallest serving cell index. Each block is 2 bits as defined in Clause 7.1.1 of [5, TS38.213]. + +- SRS resource indicator - number of bits determined by the following: + +- If *SRI-DCI0-3= type1a* is configured by higher layer, + +- bits applying to the scheduled cells with $\text{index}$ independently, where $\text{index}$ is the number of cells configured by higher layer parameter *ScheduledCell-ListDCI-0-3* in the scheduled cell set, $\text{index}$ is mapped to the cells according to an ascending order of a serving cell index with $\text{index}$ corresponding to the cell with the smallest serving cell index, and $\text{index}$ is defined below. +- If *SRI-DCI0-3* = *type2* is configured by higher layer, + - block number 1, block number 2, ..., block number $\text{index}$ + Each block corresponds to the SRS resource indicator for a scheduled cell, and the blocks are placed according to an ascending order of a serving cell index, with block number 1 corresponding to the SRS resource indicator for the cell with the smallest serving cell index. Each block is defined below. + +above for the case of *SRI-DCI0-3* = *type1a* or each block above for the case of *SRI-DCI0-3* = *type2* is defined by the following: + +- bits according to Tables 7.3.1.1.2-28/29/30/31 if the higher layer parameter *txConfig* = *nonCodebook*, where $\text{index}$ is the number of configured SRS resources in the first SRS resource set configured by higher layer parameter *srs-ResourceSetToAddModList*, and associated with the higher layer parameter *usage* of value 'nonCodeBook' and + - if UE supports operation with *maxMIMO-Layers* and the higher layer parameter *maxMIMO-Layers* of *PUSCH-ServingCellConfig* of the serving cell is configured, $L_{\max}$ is given by that parameter + - otherwise, $L_{\max}$ is given by the maximum number of layers for PUSCH supported by the UE for the serving cell for non-codebook based operation. +- bits according to Tables 7.3.1.1.2-32, 7.3.1.1.2-32A and 7.3.1.1.2-32B if the higher layer parameter *txConfig* = *codebook*, where $\text{index}$ is the number of configured SRS resources in the first SRS resource set configured by higher layer parameter *srs-ResourceSetToAddModList*, and associated with the higher layer parameter *usage* of value 'codeBook'. +- Precoding information and number of layers - number of bits determined by the following: + - If *TPMI-DCI0-3* = *type1a* is configured by higher layer, + - bits applying to the scheduled cells with $\text{index}$ independently, where $\text{index}$ is mapped to the cells according to an ascending order of a serving cell index with $\text{index}$ corresponding to the cell with the smallest serving cell index, and $\text{index}$ is defined below. + - If *TPMI-DCI0-3* = *type2* is configured by higher layer, + - block number 1, block number 2, ..., block number $\text{index}$ + Each block corresponds to the precoding information and number of layers for a scheduled cell, and the blocks are placed according to an ascending order of a serving cell index, with block number 1 corresponding to the precoding information and number of layers for the cell with the smallest serving cell index. Each block is defined below. + +above for the case of *TPMI-DCI0-3* = *type1a* or each block above for the case of *TPMI-DCI0-3* = *type2* is defined by the following: + +- 0 bits if the higher layer parameter *txConfig* = *nonCodeBook*; +- 0 bits for 1 antenna port and if the higher layer parameter *txConfig* = *codebook*; +- 4, 5, or 6 bits according to Table 7.3.1.1.2-2 for 4 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, transform precoder is disabled, and according to the values of higher layer parameters *maxRank*, and *codebookSubset*; +- 4 or 5 bits according to Table 7.3.1.1.2-2A for 4 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, *maxRank*=2, transform precoder is disabled, and according to the value of higher layer parameter *codebookSubset*; +- 4 or 6 bits according to Table 7.3.1.1.2-2B for 4 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, *maxRank*=3 or 4, transform precoder is disabled, and according to the value of higher layer parameter *codebookSubset*; +- 2, 4, or 5 bits according to Table 7.3.1.1.2-3 for 4 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters *maxRank* and *codebookSubset*; +- 3 or 4 bits according to Table 7.3.1.1.2-3A for 4 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, *maxRank*=1, and according to whether transform precoder is enabled or disabled, and the value of higher layer parameter *codebookSubset*; +- 2 or 4 bits according to Table 7.3.1.1.2-4 for 2 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, + +transform precoder is disabled, and according to the values of higher layer parameters *maxRank* and *codebookSubset*; + +- 2 bits according to Table 7.3.1.1.2-4A for 2 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, transform precoder is disabled, *maxRank*=2, and *codebookSubset*=*nonCoherent*; +- 1 or 3 bits according to Table 7.3.1.1.2-5 for 2 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* is not configured or configured to *fullpowerMode2* or configured to *fullpower*, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters *maxRank* and *codebookSubset*; +- 2 bits according to Table 7.3.1.1.2-5A for 2 antenna ports, if *txConfig* = *codebook*, *ul-FullPowerTransmission* = *fullpowerMode1*, *maxRank*=1, and according to whether transform precoder is enabled or disabled, and the value of higher layer parameter *codebookSubset*. + +For the higher layer parameter *txConfig*=*codebook*, if *ul-FullPowerTransmission* is configured to *fullpowerMode2*, *maxRank* is configured to be larger than 2, and at least one SRS resource with 4 antenna ports is configured in the SRS resource set indicated by SRS resource set indicator field if present, otherwise in an SRS resource set with usage set to 'codebook', and an SRS resource with 2 antenna ports is indicated via SRI in the same SRS resource set, then Table 7.3.1.1.2-4 is used. + +For the higher layer parameter *txConfig* = *codebook*, if different SRS resources with different number of antenna ports are configured, the bitwidth is determined according to the maximum number of ports in an SRS resource among the configured SRS resources in all SRS resource set(s) with usage set to 'codebook'. If the number of ports for a configured SRS resource in the set is less than the maximum number of ports in an SRS resource among the configured SRS resources, a number of most significant bits with value set to '0' are inserted to the field. + +- Antenna ports - number of bits determined by the following: + +- If *AntennaPortsDCI0-3*=*type1a* is configured by higher layer, + - bits applying to the scheduled cells independently, where *i* is mapped to the cells according to an ascending order of a serving cell index with *i* corresponding to the cell with the smallest serving cell index, and *i* is defined below. +- If *AntennaPortsDCI0-3*=*type2* is configured by higher layer, + - block number 1, block number 2, ..., block number *N* + Each block corresponds to the Antenna ports information for a scheduled cell, and the blocks are placed according to an ascending order of a serving cell index, with block number 1 corresponding to the Antenna ports information for the cell with the smallest serving cell index. Each block is defined below. + +above for the case of *AntennaPortsDCI0-3*=*type1a* or each block above for the case of *AntennaPortsDCI0-3*=*type2* is defined by the following: + +- 2 bits as defined by Tables 7.3.1.1.2-6, if transform precoder is enabled, *dmrs-Type*=1, and *maxLength*=1, except that *dmrs-UplinkTransformPrecoding* and *tp-pi2BPSK* are both configured and $\pi/2$ BPSK modulation is used; +- 2 bits as defined by Tables 7.3.1.1.2-6A, if transform precoder is enabled and *dmrs-UplinkTransformPrecoding* and *tp-pi2BPSK* are both configured, $\pi/2$ BPSK modulation is used, *dmrs-Type*=1, and *maxLength*=1, where *nSCID* is the scrambling identity for antenna ports defined in clause 6.4.1.1.1.2, TS38.211]; +- 4 bits as defined by Tables 7.3.1.1.2-7, if transform precoder is enabled, *dmrs-Type*=1, and *maxLength*=2, except that *dmrs-UplinkTransformPrecoding* and *tp-pi2BPSK* are both configured and $\pi/2$ BPSK modulation is used; +- 4 bits as defined by Tables 7.3.1.1.2-7A, if transform precoder is enabled and *dmrs-UplinkTransformPrecoding* and *tp-pi2BPSK* are both configured, $\pi/2$ BPSK modulation is used, *dmrs-Type*=1, and *maxLength*=2, where *nSCID* is the scrambling identity for antenna ports defined in clause 6.4.1.1.1.2, TS38.211]; +- 3 bits as defined by Tables 7.3.1.1.2-8/9/10/11, if transform precoder is disabled, *dmrs-Type*=1, and *maxLength*=1, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter *txConfig* = *nonCodebook* and according to the Precoding information and number of layers field if the higher layer parameter *txConfig* = *codebook*; +- 4 bits as defined by Tables 7.3.1.1.2-12/13/14/15, if transform precoder is disabled, *dmrs-Type*=1, and *maxLength*=2, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter *txConfig* = *nonCodebook* and according to the Precoding information and number of layers field if the higher layer parameter *txConfig* = *codebook*; + +- 4 bits as defined by Tables 7.3.1.1.2-16/17/18/19, if transform precoder is disabled, *dmrs-Type=2*, and *maxLength=1*, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter *txConfig = nonCodebook* and according to the Precoding information and number of layers field if the higher layer parameter *txConfig = codebook*; +- 5 bits as defined by Tables 7.3.1.1.2-20/21/22/23, if transform precoder is disabled, *dmrs-Type=2*, and *maxLength=2*, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter *txConfig = nonCodebook* and according to the Precoding information and number of layers field if the higher layer parameter *txConfig = codebook*. + +where the number of CDM groups without data of values 1, 2, and 3 in Tables 7.3.1.1.2-6 to 7.3.1.1.2-23 refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively. + +If a UE is configured with both *dmrs-UplinkForPUSCH-MappingTypeA* and *dmrs-UplinkForPUSCH-MappingTypeB*, the bitwidth of this field equals $\max(n_{AP}^A, n_{AP}^B)$ , where $n_{AP}^A$ is the "Antenna ports" bitwidth derived according to *dmrs-UplinkForPUSCH-MappingTypeA* and $n_{AP}^B$ is the "Antenna ports" bitwidth derived according to *dmrs-UplinkForPUSCH-MappingTypeB*. A number of zeros are padded in the MSB of this field, if the mapping type of the PUSCH corresponds to the smaller value of $n_{AP}^A$ and $n_{AP}^B$ . + +- SRS request -bits, where $n_{SRS}$ is the number of entries in the higher layer parameter *srs-RequestListDCI-0-3*. This field is used to indicate an entry in the higher layer parameter *srs-RequestListDCI-0-3* according to Table 7.3.1.1.4-4. Each entry in the higher layer parameter *srs-RequestListDCI-0-3* contains the 'SRS request' index for each cell in the scheduled cell set, where the 'SRS request' indexes for all the cells are placed according to an ascending order of a serving cell index. Each 'SRS request' index is defined by the following: + - 2 bits as defined by Table 7.3.1.1.2-24 for UEs not configured with *supplementaryUplink* in *ServingCellConfig* in the cell; 3 bits for UEs configured with *supplementaryUplink* in *ServingCellConfig* in the cell where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-1 and the second and third bits are defined by Table 7.3.1.1.2-24. This bit field may also indicate the associated CSI-RS according to Clause 6.1.1.2 of [6, TS 38.214]. +- SRS offset indicator -bits, where $n_{SRS}$ is the number of entries in the higher layer parameter *srs-OffsetListDCI-0-3*. This field is used to indicate an entry in the higher layer parameter *srs-OffsetListDCI-0-3* according to Table 7.3.1.1.4-5. Each entry in the higher layer parameter *srs-OffsetListDCI-0-3* contains the 'SRS offset indicator' index for each cell in the scheduled cell set, where the 'SRS offset indicator' indexes for all the cells are placed according to an ascending order of a serving cell index. Each 'SRS offset indicator' index is defined by the following: + - 0 bit if higher layer parameter *AvailableSlotOffset* is not configured for any aperiodic SRS resource set in the scheduled cell, or if higher layer parameter *AvailableSlotOffset* is configured for at least one aperiodic SRS resource set in the scheduled cell and the maximum number of entries of *availableSlotOffsetList* configured for all aperiodic SRS resource set(s) is 1; + - otherwise, bits are used to indicate available slot offset according to Table 7.3.1.1.2-37 and Clause 6.2.1 of [6, TS 38.214], where K is the maximum number of entries of *availableSlotOffsetList* configured for all aperiodic SRS resource set(s) in the scheduled cell; +- CSI request - 0, 1, 2, 3, 4, 5, or 6 bits determined by higher layer parameter *reportTriggerSize*. This field is applied to the cell with the smallest serving cell index among the scheduled cells indicated by Scheduled cells indicator field or Frequency domain resource assignment field. +- PTRS-DMRS association - number of bits determined by the following: + - $n_{block}$ block number 1, block number 2, ..., block number $n_{block}$ . Each block corresponds to the PTRS-DMRS association information for a scheduled cell, and the blocks are placed according to an ascending order of a serving cell index, with block number 1 corresponding to the PTRS-DMRS association information for the cell with the smallest serving cell index. Each block is defined by the following: + - 0 bit if *PTRS-UplinkConfig* is not configured in either *dmrs-UplinkForPUSCH-MappingTypeA* or *dmrs-UplinkForPUSCH-MappingTypeB* and transform precoder is disabled, or if transform precoder is enabled, or if *maxRankDCI=1*; + - 2 bits otherwise, where Table 7.3.1.1.2-25 and 7.3.1.1.2-26 are used to indicate the association between PTRS port(s) and DMRS port(s) when one PT-RS port and two PT-RS ports are configured by *maxNrofPorts* in *PTRS-UplinkConfig* respectively, and the DMRS ports are indicated by the Antenna ports field. + +If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and the "PTRS-DMRS association" field is present for the indicated bandwidth part but not present for the active + +bandwidth part, the UE assumes the "PTRS-DMRS association" field is not present for the indicated bandwidth part. + +- beta\_offset indicator - 0 or 2 bits + - 0 bit if *betaOffsets* = *semiStatic* is configured for all the cells configured by higher layer parameter *ScheduledCell-ListDCI-0-3* in the scheduled cell set; + - otherwise 2 bits as defined by Table 9.3-3 in [5, TS 38.213]. + +When two HARQ-ACK codebooks are configured for the same serving cell and if higher layer parameter *priorityIndicatorDCI-0-3* is configured, if the bit width of the beta\_offset indicator in DCI format 0\_3 for one HARQ-ACK codebook is not equal to that of the beta\_offset indicator in DCI format 0\_3 for the other HARQ-ACK codebook, a number of most significant bits with value set to '0' are inserted to smaller beta\_offset indicator until the bit width of the beta\_offset indicator in DCI format 0\_3 for the two HARQ-ACK codebooks are the same. + +The field is only applicable to a scheduled cell configured with *betaOffsets* = *dynamic*, and is applied to the applicable scheduled cells independently. + +- DMRS sequence initialization - 1 bit. This field is applied to all the scheduled cells indicated by Scheduled cells indicator field or Frequency domain resource assignment field independently. +- UL-SCH indicator - 1 bit. A value of "1" indicates UL-SCH shall be transmitted on the PUSCH and a value of "0" indicates UL-SCH shall not be transmitted on the PUSCH. A UE is not expected to receive a DCI format 0\_3 with UL-SCH indicator of "0" and CSI request of all zero(s). This field is applied to the cell with the smallest serving cell index among the scheduled cells indicated by Scheduled cells indicator field or Frequency domain resource assignment field. +- ChannelAccess-CPext-CAPC -bits applying to the scheduled cells with *I* independently, where *I* is the number of cells configured by higher layer parameter *ScheduledCell-ListDCI-0-3* in the scheduled cell set, *I* is mapped to the cells according to an ascending order of a serving cell index with *I* corresponding to the cell with the smallest serving cell index, and *I* is defined by the following: + - 0, 1, 2, 3, 4, 5 or 6 bits. The bitwidth for this field is determined as *I* bits, where *I* is the number of entries in the higher layer parameter *ul-AccessConfigListDCI-0-1* or in Table 7.3.1.1.1-4A if *channelAccessMode-r16* = "*semiStatic*" is provided, for operation in a cell with shared spectrum channel access in frequency range 1, or for operation in frequency range 2-2 if *ChannelAccessMode2-r17* is provided; otherwise 0 bit. One or more entries from Table 7.3.1.1.2-35 or Table 7.3.1.1.2-35A are configured by the higher layer parameter *ul-AccessConfigListDCI-0-1*. +- Open-loop power control parameter set indication - bits applying to the scheduled cells with *I* independently, where *I* is mapped to the cells according to an ascending order of a serving cell index with *I* corresponding to the cell with the smallest serving cell index, and *I* is defined by the following: + - 0 bit if the higher layer parameter *p0-PUSCH-SetList* is not configured; + - 1 or 2 bits otherwise, + - 1 bit if SRS resource indicator is present in the DCI format 0\_3; + - 1 or 2 bits as determined by higher layer parameter *olpc-ParameterSetDCI-0-1* if SRS resource indicator is not present in the DCI format 0\_3. +- Priority indicator - 0 bit if higher layer parameter *priorityIndicatorDCI-0-3* is not configured; otherwise 1 bit as defined in Clause 9 in [5, TS 38.213]. This field is applied to all the scheduled cells indicated by Scheduled cells indicator field or Frequency domain resource assignment field. +- Minimum applicable scheduling offset indicator - 0 or 1 bit + - 0 bit if higher layer parameter *minimumSchedulingOffsetK0DCI-0-3* is not configured; + - 1 bit otherwise. The 1 bit indication is used to determine the minimum applicable K2 for the active UL BWP and the minimum applicable K0 for the active DL BWP, if configured respectively, according to Table 7.3.1.1.2-33. If the minimum applicable K0 is indicated, the minimum applicable value of the aperiodic CSI-RS triggering offset for an active DL BWP for each scheduled cell shall be the same as the minimum applicable K0. +- SCell dormancy indication - 0 bit if higher layer parameter *dormancyDCI-0-3* or *dormancyGroupWithinActiveTime* is not configured; otherwise 1, 2, 3, 4, or 5 bits bitmap determined according to the number of different *DormancyGroupID(s)* provided by higher layer parameter *dormancyGroupWithinActiveTime*, where each bit corresponds to one of the SCell group(s) configured by higher layers parameter *dormancyGroupWithinActiveTime*, with MSB to LSB of the bitmap corresponding to the first to last configured SCell group in ascending order of *DormancyGroupID*. The field is only present when this format + +is carried by PDCCH on the primary cell within DRX Active Time and the UE is configured with at least two DL BWPs for an SCell. + +- PDCCH monitoring adaptation indication - 0, 1 or 2 bits + - 0 bit if higher layer parameter *pdcchMonAdaptDCI-0-3* is not enabled; + - otherwise, + - 1 or 2 bits, if *searchSpaceGroupIdList-r17* is not configured and if *pdcch-SkippingDurationList* is configured + - 1 bit if the UE is configured with only one duration by *pdcch-SkippingDurationList*; + - 2 bits if the UE is configured with more than one duration by *pdcch-SkippingDurationList*. + - 1 or 2 bits, if *pdcch-SkippingDurationList* is not configured and if *searchSpaceGroupIdList-r17* is configured + - 1 bit if the UE is configured by *searchSpaceGroupIdList-r17* with search space set(s) with group index 0 and search space set(s) with group index 1, and if the UE is not configured by *searchSpaceGroupIdList-r17* with any search space set with group index 2; + - 2 bits if the UE is configured by *searchSpaceGroupIdList-r17* with search space set(s) with group index 0, search space set(s) with group index 1 and search space set(s) with group index 2; + - 2 bits, if *pdcch-SkippingDurationList* is configured and if *searchSpaceGroupIdList-r17* is configured + +If *ScheduledCellCombo-ListDCI-0-3* for the cell set is configured, zeros shall be appended to DCI format 0\_3 if needed until the payload size equals the size of DCI format 0\_3 that is determined by the configuration of the corresponding active bandwidth part(s) of the scheduled cells in the entry which results in the largest size among the entries in the higher layer parameter *ScheduledCellCombo-ListDCI-0-3*. + +If an SCell within the scheduled cell set is deactivated, the UE determines the bitwidth of the fields in DCI format 0\_3 based on a UL BWP provided by *firstActiveUplinkBWP-Id* for the SCell. + +**Table 7.3.1.1.4-1: Scheduled cell set indicator in DCI format 0\_3** + +| Bit field mapped to index | Scheduled cell set | +|---------------------------|-------------------------------------------------------------------------------------------------------| +| 0 | The cell set configured by the 1 st entry in MC-DCI-SetofCellsToAddModList | +| 1 | The cell set configured by the 2 nd entry in MC-DCI-SetofCellsToAddModList | +| 2 | The cell set configured by the 3 rd entry in MC-DCI-SetofCellsToAddModList , if any | +| 3 | The cell set configured by the 4 th entry in MC-DCI-SetofCellsToAddModList , if any | + +**Table 7.3.1.1.4-2: Scheduled cells indicator in DCI format 0\_3** + +| Bit field mapped to index | Scheduled cells | +|---------------------------|------------------------------------------------------------------------------------------------------| +| 0 | The cells configured by the 1 st entry in ScheduledCellCombo-ListDCI-0-3 | +| 1 | The cells configured by the 2 nd entry in ScheduledCellCombo-ListDCI-0-3 | +| 2 | The cells configured by the 3 rd entry in ScheduledCellCombo-ListDCI-0-3 , if any | +| 3 | The cells configured by the 4 th entry in ScheduledCellCombo-ListDCI-0-3 , if any | +| 4 | The cells configured by the 5 th entry in ScheduledCellCombo-ListDCI-0-3 , if any | +| 5 | The cells configured by the 6 th entry in ScheduledCellCombo-ListDCI-0-3 , if any | +| 6 | The cells configured by the 7 th entry in ScheduledCellCombo-ListDCI-0-3 , if any | +| 7 | The cells configured by the 8 th entry in ScheduledCellCombo-ListDCI-0-3 , if any | +| 8 | The cells configured by the 9 th entry in ScheduledCellCombo-ListDCI-0-3 , if any | +| 9 | The cells configured by the 10 th entry in ScheduledCellCombo-ListDCI-0-3 , if any | +| 10 | The cells configured by the 11 th entry in ScheduledCellCombo-ListDCI-0-3 , if any | +| 11 | The cells configured by the 12 th entry in ScheduledCellCombo-ListDCI-0-3 , if any | +| 12 | The cells configured by the 13 th entry in ScheduledCellCombo-ListDCI-0-3 , if any | +| 13 | The cells configured by the 14 th entry in ScheduledCellCombo-ListDCI-0-3 , if any | +| 14 | The cells configured by the 15 th entry in ScheduledCellCombo-ListDCI-0-3 , if any | +| 15 | The cells configured by the 16 th entry in ScheduledCellCombo-ListDCI-0-3 , if any | + +**Table 7.3.1.1.4-3: Time domain resource assignment in DCI format 0\_3** + +| Bit field mapped to index | Indicated time domain resource allocation | +|---------------------------|-------------------------------------------------------------------------| +| 0 | The 1 st entry in TDRA-FieldIndexListDCI-0-3 | +| 1 | The 2 nd entry in TDRA-FieldIndexListDCI-0-3 | +| 2 | The 3 rd entry in TDRA-FieldIndexListDCI-0-3 , if any | +| ... | ... | +| | The entry in TDRA-FieldIndexListDCI-0-3 , if any | +| ... | ... | + +**Table 7.3.1.1.4-4: SRS request in DCI format 0\_3** + +| Bit field mapped to index | Triggered aperiodic SRS resource set(s) | +|---------------------------|----------------------------------------------------------------------| +| 0 | The 1 st entry in srs-RequestListDCI-0-3 | +| 1 | The 2 nd entry in srs-RequestListDCI-0-3 | +| 2 | The 3 rd entry in srs-RequestListDCI-0-3 , if any | +| ... | ... | +| 15 | The 16 th entry in srs-RequestListDCI-0-3 , if any | + +**Table 7.3.1.1.4-5: SRS offset indicator in DCI format 0\_3** + +| Bit field mapped to index | Available slot offset | +|---------------------------|--------------------------------------------------------------------| +| 0 | The 1 st entry in srs-OffsetListDCI-0-3 | +| 1 | The 2 nd entry in srs-OffsetListDCI-0-3 | +| 2 | The 3 rd entry in srs-OffsetListDCI-0-3 , if any | +| ... | ... | +| 7 | The 8 th entry in srs-OffsetListDCI-0-3 , if any | + +#### 7.3.1.2 DCI formats for scheduling of PDSCH + +##### 7.3.1.2.1 Format 1\_0 + +DCI format 1\_0 is used for the scheduling of PDSCH in one DL cell. + +The following information is transmitted by means of the DCI format 1\_0 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI: + +- Identifier for DCI formats - 1 bits + - The value of this bit field is always set to 1, indicating a DL DCI format +- Frequency domain resource assignment - bits where is given by Clause 7.3.1.0 + +If the CRC of the DCI format 1\_0 is scrambled by C-RNTI and the "Frequency domain resource assignment" field are of all ones, the DCI format 1\_0 is for random access procedure initiated by a PDCCH order, with all remaining fields set as follows: + +- Random Access Preamble index - 6 bits according to *ra-PreambleIndex* in Clause 5.1.2 of [8, TS38.321] +- UL/SUL indicator - 1 bit. If the value of the "Random Access Preamble index" is not all zeros and if the UE is configured with *supplementaryUplink* in *ServingCellConfig* in the cell, this field indicates which UL carrier in the cell to transmit the PRACH according to Table 7.3.1.1.1-1; otherwise, this field is reserved +- SS/PBCH index - 6 bits. If the value of the "Random Access Preamble index" is not all zeros, this field indicates the SS/PBCH that shall be used to determine the RACH occasion for the PRACH transmission; otherwise, this field is reserved. +- PRACH Mask index - 4 bits. If the value of the "Random Access Preamble index" is not all zeros, this field indicates the RACH occasion associated with the SS/PBCH indicated by "SS/PBCH index" for the PRACH transmission, according to Clause 5.1.1 of [8, TS38.321]; otherwise, this field is reserved +- Cell indicator - bits indicating the cell for the corresponding PRACH transmission if the UE is configured with higher layer parameter *EarlyUISyncConfig*, where *C* is the number of candidate cells configured with higher layer parameter *EarlyUISyncConfig*; 0 bit otherwise. The bit field index 0 of the cell indicator field is mapped to + +the serving cell, and other bit field indexes are mapped to the candidate cells configured with higher layer parameter *EarlyUlSyncConfig* according to an ascending order of a candidate identity configured by *ltm-CandidateId*, with the bit field index 1 mapped to the candidate cell with the smallest candidate identity. + +- PRACH association indicator - 0 or 1 bit + - 1bit if the UE is provided with *tag-Id2*, and the UE is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with value 0 for the first CORESETs, and is provided *coresetPoolIndex* with value 1 for the second CORESETs. + - This field indicates the PCI associated with the PRACH transmission if the UE is provided *SSB-MTC-AdditionalPCI*. The bit field index 0 of this field is mapped to the PCI of the serving cell, and the bit field index 1 of this field is mapped to the active additional PCI. + - This field indicates the PL-RS for the PRACH transmission if the UE is not provided *SSB-MTC-AdditionalPCI*. The bit field index 0 of this field is mapped to the DL RS that the DM-RS of the PDCCH order is quasi-collocated with, and the bit field index 1 of this field is mapped to the SS/PBCH indicated by the SS/PBCH index field in this DCI format. + - 0 bit otherwise. +- PRACH retransmission indicator - 0 or 1 bit + - 1bit if the UE is configured with higher layer parameter *EarlyUlSyncConfig*. This field indicates initial transmission or retransmission of PRACH according to Table 7.3.1.2.1-3 if the cell indicated by Cell indicator field is a candidate cell, and this field is reserved if the cell indicated by Cell indicator field is a serving cell but not a candidate cell. + - 0 bit otherwise. +- Reserved bits - a number of bits as determined by the following: + - 12 bits for operation in a cell with shared spectrum channel access in frequency range 1 or when the DCI format is monitored in common search space for operation in a cell in frequency range 2-2, and if the UE is not configured with higher layer parameter *EarlyUlSyncConfig*; + - 11- bits for operation in a cell with shared spectrum channel access in frequency range 1 or when the DCI format is monitored in common search space for operation in a cell in frequency range 2-2, and if the UE is configured with higher layer parameter *EarlyUlSyncConfig*; + - 9- bits for operation in a cell without shared spectrum channel access in frequency range 1 or for operation in a cell in frequency range 2-1 or when the DCI format is monitored in UE-specific search space for operation in a cell in frequency range 2-2, and if the UE is configured with higher layer parameter *EarlyUlSyncConfig*; + - 10 bits otherwise. + +Otherwise, all remaining fields are set as follows: + +- Time domain resource assignment - 4 bits as defined in Clause 5.1.2.1 of [6, TS 38.214] +- VRB-to-PRB mapping - 1 bit according to Table 7.3.1.2.2-5 +- Modulation and coding scheme - 5 bits as defined in Clause 5.1.3 of [6, TS 38.214] +- New data indicator - 1 bit +- Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2 +- HARQ process number - 4 bits +- Downlink assignment index - 2 bits as defined in Clause 9.1.3 of [5, TS 38.213], as counter DAI +- TPC command for scheduled PUCCH - 2 bits as defined in Clause 7.2.1 of [5, TS 38.213] +- PUCCH resource indicator - 3 bits as defined in Clause 9.2.3 of [5, TS 38.213] +- PDSCH-to-HARQ\_feedback timing indicator - 3 bits as defined in Clause 9.2.3 of [5, TS38.213] +- ChannelAccess-CPext - 2 bits indicating combinations of channel access type and CP extension as defined in Table 7.3.1.1.1-4, or Table 7.3.1.1.1-4A if *channelAccessMode-r16* = "semiStatic" is provided, for operation in a cell with shared spectrum channel access in frequency range 1; 2 bits indicating channel access type as defined in Table 7.3.1.1.1-4B if *ChannelAccessMode2-r17* is provided for operation in a cell in frequency range 2-2; 0 bits otherwise +- Reserved bits - 2 bits when the DCI format is monitored in common search space for operation in a cell in frequency range 2-2 and the number of bits for the field of 'ChannelAccess-CPext' is 0; 0 bits otherwise + +The following information is transmitted by means of the DCI format 1\_0 with CRC scrambled by P-RNTI: + +- Short Messages Indicator - 2 bits according to Table 7.3.1.2.1-1. +- Short Messages - 8 bits, according to Clause 6.5 of [9, TS38.331]. If only the scheduling information for Paging, and TRS availability indication if *trs-ResourceSetConfig* is configured, are carried, this bit field is reserved. +- Frequency domain resource assignment - bits. If only the short message, and TRS availability indication if *trs-ResourceSetConfig* is configured, are carried, this bit field is reserved. + - is the size of CORESET 0 +- Time domain resource assignment - 4 bits as defined in Clause 5.1.2.1 of [6, TS38.214]. If only the short message, and TRS availability indication if *trs-ResourceSetConfig* is configured, are carried, this bit field is reserved. +- VRB-to-PRB mapping - 1 bit according to Table 7.3.1.2.2-5. If only the short message, and TRS availability indication if *trs-ResourceSetConfig* is configured, are carried, this bit field is reserved. +- Modulation and coding scheme - 5 bits as defined in Clause 5.1.3 of [6, TS38.214], using Table 5.1.3.1-1. If only the short message, and TRS availability indication if *trs-ResourceSetConfig* is configured, are carried, this bit field is reserved. +- TB scaling - 2 bits as defined in Clause 5.1.3.2 of [6, TS38.214]. If only the short message, and TRS availability indication if *trs-ResourceSetConfig* is configured, are carried, this bit field is reserved. +- TRS availability indication - 1, 2, 3, 4, 5, or 6 bits, where the number of bits is equal to one plus the highest value of all the *indBitID*(s) provided by the *trs-ResourceSetConfig* if configured; 0 bits otherwise. +- Reserved bits - $(8 - M)$ bits for operation in a cell with shared spectrum channel access in frequency range 1 or for operation in a cell in frequency range 2-2; $(6 - M)$ bits for operation in a cell without shared spectrum channel access, where the value of $M$ is the number of bits for the field of 'TRS availability indication' as defined above. + +The following information is transmitted by means of the DCI format 1\_0 with CRC scrambled by SI-RNTI: + +- Frequency domain resource assignment - bits + - is the size of CORESET 0 +- Time domain resource assignment - 4 bits as defined in Clause 5.1.2.1 of [6, TS38.214] +- VRB-to-PRB mapping - 1 bit according to Table 7.3.1.2.2-5 +- Modulation and coding scheme - 5 bits as defined in Clause 5.1.3 of [6, TS38.214], using Table 5.1.3.1-1 +- Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2 +- System information indicator - 1 bit as defined in Table 7.3.1.2.1-2 +- Reserved bits - 17 bits for operation in a cell with shared spectrum channel access in frequency range 1 or for operation in a cell in frequency range 2-2; otherwise 15 bits + +The following information is transmitted by means of the DCI format 1\_0 with CRC scrambled by RA-RNTI or MsgB-RNTI: + +- Frequency domain resource assignment - bits + - is the size of CORESET 0 if CORESET 0 is configured for the cell and $N_{\text{RB}}^{\text{DL,BWP}}$ is the size of initial DL bandwidth part if CORESET 0 is not configured for the cell +- Time domain resource assignment - 4 bits as defined in Clause 5.1.2.1 of [6, TS38.214] +- VRB-to-PRB mapping - 1 bit according to Table 7.3.1.2.2-5 +- Modulation and coding scheme - 5 bits as defined in Clause 5.1.3 of [6, TS38.214], using Table 5.1.3.1-1 +- TB scaling - 2 bits as defined in Clause 5.1.3.2 of [6, TS38.214] +- LSBs of SFN - 2 bits for the DCI format 1\_0 with CRC scrambled by MsgB-RNTI as defined in Clause 8.2A of [5, TS 38.213] if *msgB-responseWindow* is configured to be larger than 10 ms; or 2 bits for the DCI format 1\_0 with CRC scrambled by RA-RNTI as defined in Clause 8.2 of [5, TS 38.213] for operation in a cell with shared spectrum channel access if *ra-ResponseWindow* or *ra-ResponseWindow-v1610* is configured to be larger than 10 ms; 0 bit otherwise + +- Reserved bits - (16 - *A*) bits for operation in a cell without shared spectrum access in frequency range 1 and frequency range 2-1, (18 - *A*) for operation in a cell with shared spectrum access in frequency range 1 or for operation in a cell in frequency range 2-2, where the value of *A* is the number of bits for the field of 'LSBs of SFN' as defined above + +The following information is transmitted by means of the DCI format 1\_0 with CRC scrambled by TC-RNTI: + +- Identifier for DCI formats - 1 bit + - The value of this bit field is always set to 1, indicating a DL DCI format +- Frequency domain resource assignment - bits + - *NRBUL* is the size of CORESET 0 +- Time domain resource assignment - 4 bits as defined in Clause 5.1.2.1 of [6, TS38.214] +- VRB-to-PRB mapping - 1 bit according to Table 7.3.1.2.2-5 +- Modulation and coding scheme - 5 bits as defined in Clause 5.1.3 of [6, TS38.214], using Table 5.1.3.1-1 +- New data indicator - 1 bit +- Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2 +- HARQ process number - 4 bits +- Downlink assignment index - 2 bits + - 2 bits indicating the number of repetitions for PUCCH as defined in clause 9.2.6 of [5, TS38.213] according to Table 7.3.1.2.1-4, if the higher layer parameter *numberOfPUCCHforMsg4HARQACK-RepetitionsList* is configured with at least two values and the UE has indicated capability of PUCCH repetition on common PUCCH resource [8, TS38.321]; + - otherwise, reserved. +- TPC command for scheduled PUCCH - 2 bits as defined in Clause 7.2.1 of [5, TS38.213] +- PUCCH resource indicator - 3 bits as defined in Clause 9.2.3 of [5, TS38.213] +- PDSCH-to-HARQ\_feedback timing indicator - 3 bits as defined in Clause 9.2.3 of [5, TS38.213] +- ChannelAccess-CPext - 2 bits indicating combinations of channel access type and CP extension as defined in Table 7.3.1.1.1-4, or Table 7.3.1.1.1-4A if *channelAccessMode-r16* = "semiStatic" is provided, for operation in a cell with shared spectrum channel access in frequency range 1; 2 bits indicating channel access type as defined in Table 7.3.1.1.1-4B if *ChannelAccessMode2-r17* is provided for operation in a cell in frequency range 2-2; otherwise 0 bit +- Reserved bits - 2 bits when the DCI format is monitored in common search space for operation in a cell in frequency range 2-2 and the number of bits for the field of 'ChannelAccess-CPext' is 0; 0 bits otherwise + +**Table 7.3.1.2.1-1: Short Message indicator** + +| Bit field | Short Message indicator | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 00 | Reserved | +| 01 | Only scheduling information for Paging, and TRS availability indication if trs-ResourceSetConfig is configured, are present in the DCI | +| 10 | Only short message, and TRS availability indication if trs-ResourceSetConfig is configured, are present in the DCI | +| 11 | Both scheduling information for Paging, TRS availability indication if trs-ResourceSetConfig is configured and short message are present in the DCI | + +**Table 7.3.1.2.1-2: System information indicator** + +| Bit field | System information indicator | +|-----------|----------------------------------------| +| 0 | SIB1 [9, TS38.331, Clause 5.2.1] | +| 1 | SI message [9, TS38.331, Clause 5.2.1] | + +**Table 7.3.1.2.1-3: PRACH retransmission indicator** + +| Bit field | PRACH retransmission indicator | +|-----------|--------------------------------| +| 0 | Initial transmission of PRACH | +| 1 | Retransmission of PRACH | + +**Table 7.3.1.2.1-4: Number of repetitions as a function of 2 bits of Downlink assignment index field** + +| Bit field | | +|-----------|----------------------------------------------------------------------------------------------------| +| 00 | First value of numberOfPUCCHforMsg4HARQACK-RepetitionsList | +| 01 | Second value of numberOfPUCCHforMsg4HARQACK-RepetitionsList | +| 10 | Third value of numberOfPUCCHforMsg4HARQACK-RepetitionsList if provided, otherwise reserved | +| 11 | Fourth value of numberOfPUCCHforMsg4HARQACK-RepetitionsList if provided, otherwise reserved | + +##### 7.3.1.2.2 Format 1\_1 + +DCI format 1\_1 is used for the scheduling of one or multiple PDSCH in one cell. + +The following information is transmitted by means of the DCI format 1\_1 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI: + +- Identifier for DCI formats - 1 bits + - The value of this bit field is always set to 1, indicating a DL DCI format +- Carrier indicator - 0 or 3 bits as defined in Clause 10.1 of [5, TS 38.213]. This field is reserved when this format is carried by PDCCH on the primary cell and the UE is configured for scheduling on the primary cell from an SCell, with the same number of bits as that in this format carried by PDCCH on the SCell for scheduling on the primary cell. +- Bandwidth part indicator - 0, 1 or 2 bits as determined by the number of DL BWPs $n_{\text{BWP,RRC}}$ configured by higher layers, excluding the initial DL bandwidth part. The bitwidth for this field is determined as bits, where + - if $n_{\text{BWP,RRC}} \leq 3$ , in which case the bandwidth part indicator is equivalent to the ascending order of the higher layer parameter *BWP-Id*; + - otherwise, in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1; + If a UE does not support active BWP change via DCI, the UE ignores this bit field. +- Frequency domain resource assignment - number of bits determined by the following, where $n$ is the size of the active DL bandwidth part: + - $n$ bits if only resource allocation type 0 is configured, where $n$ is defined in Clause 5.1.2.2.1 of [6, TS38.214], + - $n$ bits if only resource allocation type 1 is configured, or + - $n$ bits if *resourceAllocation* is configured as '*dynamicSwitch*'. + - If *resourceAllocation* is configured as '*dynamicSwitch*', the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit value of 1 indicates resource allocation type 1. + - For resource allocation type 0, the LSBs provide the resource allocation as defined in Clause 5.1.2.2.1 of [6, TS 38.214]. + - For resource allocation type 1, the LSBs provide the resource allocation as defined in Clause 5.1.2.2.2 of [6, TS 38.214] + If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if *resourceAllocation* is configured as '*dynamicSwitch*' for the indicated bandwidth part, the UE assumes resource allocation type 0 for the indicated bandwidth part if the bitwidth of the "Frequency domain resource assignment" field of the active bandwidth part is smaller than the bitwidth of the "Frequency domain resource assignment" field of the indicated bandwidth part. +- Time domain resource assignment - 0, 1, 2, 3, 4, 5 or 6 bits + +- If the higher layer parameter *pdsch-TimeDomainAllocationListForMultiPDSCH* is not configured and if the higher layer parameter *pdsch-TimeDomainAllocationList* is configured, 0, 1, 2, 3 or 4 bits as defined in Clause 5.1.2.1 of [6, TS 38.214]. The bitwidth for this field is determined as bits, where *I* is the number of entries in the higher layer parameter *pdsch-TimeDomainAllocationList* if the higher layer parameter is configured; +- if the higher layer parameter *pdsch-TimeDomainAllocationListForMultiPDSCH* is configured, 0, 1, 2, 3, 4, 5 or 6 bits as defined in Clause 5.1.2.1 of [6, TS 38.214]. The bitwidth for this field is determined as bits, where *I* is the number of entries in the higher layer parameter *pdsch-TimeDomainAllocationListForMultiPDSCH*; +- otherwise *I* is the number of entries in the default table. +- VRB-to-PRB mapping - 0 or 1 bit: + - 0 bit if only resource allocation type 0 is configured or if interleaved VRB-to-PRB mapping is not configured by high layers; + - 1 bit according to Table 7.3.1.2.2-5 otherwise, only applicable to resource allocation type 1, as defined in Clause 7.3.1.6 of [4, TS 38.211]. +- PRB bundling size indicator - 0 bit if the higher layer parameter *prb-BundlingType* is not configured or is set to 'staticBundling', or 1 bit if the higher layer parameter *prb-BundlingType* is set to 'dynamicBundling' according to Clause 5.1.2.3 of [6, TS 38.214]. +- Rate matching indicator - 0, 1, or 2 bits according to higher layer parameters *rateMatchPatternGroup1* and *rateMatchPatternGroup2*, where the MSB is used to indicate *rateMatchPatternGroup1* and the LSB is used to indicate *rateMatchPatternGroup2* when there are two groups. +- ZP CSI-RS trigger - 0, 1, or 2 bits as defined in Clause 5.1.4.2 of [6, TS 38.214]. The bitwidth for this field is determined as bits, where *I* is the number of aperiodic ZP CSI-RS resource sets configured by higher layer. + +For transport block 1: + +- Modulation and coding scheme - 5 bits as defined in Clause 5.1.3.1 of [6, TS 38.214] +- New data indicator - 1 bit if the number of scheduled PDSCH indicated by the Time domain resource assignment field is 1; otherwise 2, 3, 4, 5, 6, 7 or 8 bits determined based on the maximum number of schedulable PDSCH among all entries in the higher layer parameter *pdsch-TimeDomainAllocationListForMultiPDSCH*, where each bit corresponds to one scheduled PDSCH as defined in clause 5.1.3 in [6, TS 38.214]. +- Redundancy version - number of bits determined by the following: + - 2 bits as defined in Table 7.3.1.1.1-2 if the number of scheduled PDSCH indicated by the Time domain resource assignment field is 1; + - otherwise 2, 3, 4, 5, 6, 7 or 8 bits determined by the maximum number of schedulable PDSCHs among all entries in the higher layer parameter *pdsch-TimeDomainAllocationListForMultiPDSCH*, where each bit corresponds to one scheduled PDSCH as defined in clause 5.1.3 in [6, TS 38.214] and redundancy version is determined according to Table 7.3.1.1.2-34. + +For transport block 2 (only present if *maxNrofCodeWordsScheduledByDCI* equals 2): + +- Modulation and coding scheme - 5 bits as defined in Clause 5.1.3.1 of [6, TS 38.214] +- New data indicator - 1 bit if the number of scheduled PDSCH indicated by the Time domain resource assignment field is 1; otherwise 2, 3, 4, 5, 6, 7 or 8 bits determined based on the maximum number of schedulable PDSCH among all entries in the higher layer parameter *pdsch-TimeDomainAllocationListForMultiPDSCH*, where each bit corresponds to one scheduled PDSCH as defined in clause 5.1.3 in [6, TS 38.214]. +- Redundancy version - number of bits determined by the following: + - 2 bits as defined in Table 7.3.1.1.1-2 if the number of scheduled PDSCH indicated by the Time domain resource assignment field is 1; + - otherwise 2, 3, 4, 5, 6, 7 or 8 bits determined by the maximum number of schedulable PDSCHs among all entries in the higher layer parameter *pdsch-TimeDomainAllocationListForMultiPDSCH*, where each bit corresponds to one scheduled PDSCH as defined in clause 5.1.3 in [6, TS 38.214] and redundancy version is determined according to Table 7.3.1.1.2-34. + +If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and the value of *maxNrofCodeWordsScheduledByDCI* for the indicated bandwidth part equals 2 and the value of *maxNrofCodeWordsScheduledByDCI* for the active bandwidth part equals 1, the UE assumes zeros are padded when interpreting the "Modulation and coding scheme", "New data indicator", and "Redundancy version" fields of transport block 2 according to Clause 12 of [5, TS 38.213], and the UE ignores the "Modulation and coding scheme", "New data indicator", and "Redundancy version" fields of transport block 2 for the indicated bandwidth part. + +- HARQ process number - 5 bits if higher layer parameter *harq-ProcessNumberSizeDCI-1-1* is configured; otherwise 4 bits +- Downlink assignment index - number of bits as defined in the following + - 6 bits if more than one serving cell are configured in the DL and the higher layer parameter *nfi-TotalDAI-Included* is configured. The 4 MSB bits are the counter DAI and the total DAI for the scheduled PDSCH group, and the 2 LSB bits are the total DAI for the non-scheduled PDSCH group. + - 4 bits if only one serving cell is configured in the DL and the higher layer parameter *nfi-TotalDAI-Included* is configured. The 2 MSB bits are the counter DAI for the scheduled PDSCH group, and the 2 LSB bits are the total DAI for the non-scheduled PDSCH group; + - 4 bits if more than one serving cell are configured in the DL, the higher layer parameter *pdsch-HARQ-ACK-Codebook=dynamic* or *pdsch-HARQ-ACK-Codebook-r16=enhancedDynamic*, and *nfi-TotalDAI-Included* is not configured, where the 2 MSB bits are the counter DAI and the 2 LSB bits are the total DAI; + - 4 bits if one serving cell is configured in the DL, and the higher layer parameter *pdsch-HARQ-ACK-Codebook=dynamic*, and the UE is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with value 0 for one or more first CORESETs and is provided *coresetPoolIndex* with value 1 for one or more second CORESETs, and is provided *ackNackFeedbackMode = joint*, where the 2 MSB bits are the counter DAI and the 2 LSB bits are the total DAI; + - 2 bits if only one serving cell is configured in the DL, the higher layer parameter *pdsch-HARQ-ACK-Codebook=dynamic* or *pdsch-HARQ-ACK-Codebook-r16=enhancedDynamic*, and *nfi-TotalDAI-Included* is not configured, when the UE is not configured with *coresetPoolIndex* or the value of *coresetPoolIndex* is the same for all CORESETs if *coresetPoolIndex* is provided or the UE is not configured with *ackNackFeedbackMode = joint*, where the 2 bits are the counter DAI; + - 0 bits otherwise. + +If the UE is configured with a PUCCH-SCell, the number of serving cells is determined within a PUCCH group. + +If the UE is configured with a PUCCH-SCell, *pdsch-HARQ-ACK-Codebook* is replaced by *pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup-r16* if present for the secondary PUCCH group. + +If higher layer parameter *priorityIndicatorDCI-1-1* is configured, if the bit width of the Downlink assignment index in DCI format 1\_1 for one HARQ-ACK codebook is not equal to that of the Downlink assignment index in DCI format 1\_1 for the other HARQ-ACK codebook, a number of most significant bits with value set to '0' are inserted to smaller Downlink assignment index until the bit width of the Downlink assignment index in DCI format 1\_1 for the two HARQ-ACK codebooks are the same. + +- TPC command for scheduled PUCCH - 2 bits as defined in Clause 7.2.1 of [5, TS 38.213] +- Second TPC command for scheduled PUCCH - 2 bits as defined in Clause 7.2.1 of [5, TS 38.213] if higher layer parameter *SecondTPCFieldDCI-1-1* is configured; 0 bit otherwise. +- PUCCH resource indicator - 3 bits as defined in Clause 9.2.3 of [5, TS 38.213] +- PDSCH-to-HARQ\_feedback timing indicator - 0, 1, 2, or 3 bits as defined in Clause 9.2.3 of [5, TS 38.213]. The bitwidth for this field is determined as bits, where *I* is the number of entries in the higher layer parameter *dl-DataToUL-ACK*. + +If higher layer parameter *priorityIndicatorDCI-1-1* is configured, if the bit width of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 1\_1 for one HARQ-ACK codebook is not equal to that of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 1\_1 for the other HARQ-ACK codebook on the same cell for PUCCH transmission, a number of most significant bits with value set to '0' are inserted to smaller PDSCH-to-HARQ\_feedback timing indicator until the bit width of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 1\_1 for the two HARQ-ACK codebooks are the same. + +If higher layer parameter *pucch-sSCellDyn* is configured, if the bit width of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 1\_1 associated with one cell for PUCCH transmission is not equal to that of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 1\_1 associated with the other cell for PUCCH transmission, a number of most significant bits with value set to '0' are inserted to smaller PDSCH-to-HARQ\_feedback timing indicator until the bit width of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 1\_1 associated with the two cells are the same. + +If the UE is configured with a PUCCH-SCell, *pucch-sSCellDyn* is replaced by *pucch-sSCellDynSecondaryPUCCHgroup* for the secondary PUCCH group. + +- One-shot HARQ-ACK request - 0 or 1 bit. + +- 1 bit if higher layer parameter *pdsch-HARQ-ACK-OneShotFeedback-r16* or *pdsch-HARQ-ACK-EnhType3ToAddModList* is configured; +- 0 bit otherwise. + +If the UE is configured with a PUCCH-SCell, *pdsch-HARQ-ACK-EnhType3ToAddModList* is replaced by *pdsch-HARQ-ACK-EnhType3SecondaryToAddModList* for the secondary PUCCH group. + +- Enhanced Type 3 codebook indicator - 0, 1, 2, or 3 bits. + +- 0 bit if *pdsch-HARQ-ACK-EnhType3DCI-Field* is not configured; +- bits otherwise, where $x$ is the number of entries in the higher layer parameter *pdsch-HARQ-ACK-EnhType3ToAddModList*. + +If the UE is configured with a PUCCH-SCell, *pdsch-HARQ-ACK-EnhType3DCI-Field* is replaced by *pdsch-HARQ-ACK-EnhType3DCI-FieldSecondaryPUCCHgroup* for the secondary PUCCH group, and *pdsch-HARQ-ACK-EnhType3ToAddModList* is replaced by *pdsch-HARQ-ACK-EnhType3SecondaryList* for the secondary PUCCH group. + +- PDSCH group index - 0 or 1 bit. + +- 1 bit if the higher layer parameter *pdsch-HARQ-ACK-Codebook-r16= enhancedDynamic*; +- 0 bit otherwise. + +- New feedback indicator - 0, 1 or 2 bits. + +- 1 bit if the higher layer parameter *pdsch-HARQ-ACK-Codebook-r16= enhancedDynamic* and the higher layer parameter *nfi-TotalDAI-Included* is not configured; +- 2 bits if the higher layer parameter *pdsch-HARQ-ACK-Codebook-r16= enhancedDynamic* and the higher layer parameter *nfi-TotalDAI-Included=true*; the MSB corresponds to the scheduled PDSCH group, and the LSB corresponds to the non-scheduled PDSCH group, as defined in [TS38.213] clause 9.1.3.3 +- 0 bit otherwise. + +- Number of requested PDSCH group(s) - 0 or 1 bit. + +- 1 bit if the higher layer parameter *pdsch-HARQ-ACK-Codebook-r16= enhancedDynamic*; +- 0 bit otherwise. + +- HARQ-ACK retransmission indicator - 0 or 1 bit. + +- 1 bit if higher layer parameter *pdsch-HARQ-ACK-Retx* is configured. +- 0 bit otherwise. + +If the UE is configured with a PUCCH-SCell, *pdsch-HARQ-ACK-Retx* is replaced by *pdsch-HARQ-ACK-RetxSecondaryPUCCHgroup* for the secondary PUCCH group. + +- Antenna port(s) - 4, 5, 6, 7 or 8 bits as defined by Tables 7.3.1.2.2-1/2/3/4/7/8/9/10 and Tables 7.3.1.2.2-1A/2A/3A/4A/7A/8A/9A/10A, where the number of CDM groups without data of values 1, 2, and 3 refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively. The antenna ports shall be determined according to the ordering of DMRS port(s) given by Tables 7.3.1.2.2-1/2/3/4/7/8/9/10 or Tables 7.3.1.2.2-1A/2A/3A/4A/7A/8A/9A/10A. When a UE not configured with *dl-OrJointTCI-StateList* receives an activation command that maps at least one codepoint of DCI field 'Transmission Configuration Indication' to two TCI states, or when a UE configured with *dl-OrJointTCI-StateList* is having two indicated TCI states, the UE shall use Table 7.3.1.2.2-1A/2A/3A/4A/7A/8A/9A/10A; otherwise, it shall use Tables 7.3.1.2.2-1/2/3/4/7/8/9/10. The UE can receive an entry with DMRS ports equals to 1000, 1002, 1003 when two the UE is not configured with *dl-OrJointTCI-StateList* and TCI states are indicated in a codepoint of DCI field 'Transmission Configuration Indication', or when the UE configured with *dl-OrJointTCI-StateList* is having two indicated TCI states to be applied to PDSCH. + +If a UE is configured with both *dmrs-DownlinkForPDSCH-MappingTypeA* and *dmrs-DownlinkForPDSCH-MappingTypeB*, the bitwidth of this field equals $\max\{x_A, x_B\}$ , where $x_A$ is the "Antenna ports" bitwidth derived according to *dmrs-DownlinkForPDSCH-MappingTypeA* and $x_B$ is the "Antenna ports" bitwidth derived according to *dmrs-DownlinkForPDSCH-MappingTypeB*. A number of $|x_A - x_B|$ zeros are padded in the MSB of this field, if the mapping type of the PDSCH corresponds to the smaller value of $x_A$ and $x_B$ . + +- Transmission configuration indication - 0 bit if higher layer parameter *tci-PresentInDCI* is not enabled; otherwise 3 bits as defined in Clause 5.1.5 of [6, TS38.214]. + +If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part, + +- if the higher layer parameter *tci-PresentInDCI* is not enabled for the CORESET used for the PDCCH carrying the DCI format 1\_1, + - the UE assumes *tci-PresentInDCI* is not enabled for all CORESETs in the indicated bandwidth part; +- otherwise, + - the UE assumes *tci-PresentInDCI* is enabled for all CORESETs in the indicated bandwidth part. +- TCI selection - 0 bit if higher layer parameter *tciSelection-PresentInDCI* is not configured; otherwise 2 bits according to Table 7.3.1.2.2-11. +- SRS request - 2 bits as defined by Table 7.3.1.1.2-24 for UEs not configured with *supplementaryUplink* in *ServingCellConfig* in the cell; 3 bits for UEs configured with *supplementaryUplink* in *ServingCellConfig* in the cell where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-1 and the second and third bits are defined by Table 7.3.1.1.2-24. This bit field may also indicate the associated CSI-RS according to Clause 6.1.1.2 of [6, TS 38.214]. +- SRS offset indicator - 0, 1 or 2 bits. + - 0 bit if higher layer parameter *AvailableSlotOffset* is not configured for any aperiodic SRS resource set in the scheduled cell, or if higher layer parameter *AvailableSlotOffset* is configured for at least one aperiodic SRS resource set in the scheduled cell and the maximum number of entries of *availableSlotOffsetList* configured for all aperiodic SRS resource set(s) is 1; + - otherwise, bits are used to indicate available slot offset according to Table 7.3.1.1.2-37 and Clause 6.2.1 of [6, TS 38.214], where K is the maximum number of entries of *availableSlotOffsetList* configured for all aperiodic SRS resource set(s) in the scheduled cell; +- CBG transmission information (CBGTI) - 0 bit if higher layer parameter *PDSCH-CodeBlockGroupTransmission* for PDSCH is not configured, otherwise, 2, 4, 6, or 8 bits as defined in Clause 5.1.7 of [6, TS38.214], determined by the higher layer parameters *maxCodeBlockGroupsPerTransportBlock* and *maxNrofCodeWordsScheduledByDCI* for the PDSCH. + +If higher layer parameter *priorityIndicatorDCI-1-1* is configured, if the bit width of the CBG transmission information in DCI format 1\_1 for one HARQ-ACK codebook is not equal to that of the CBG transmission information in DCI format 1\_1 for the other HARQ-ACK codebook, a number of most significant bits with value set to '0' are inserted to smaller CBG transmission information until the bit width of the CBG transmission information in DCI format 1\_1 for the two HARQ-ACK codebooks are the same. + +- CBG flushing out information (CBGFI) - 1 bit if higher layer parameter *codeBlockGroupFlushIndicator* is configured as "TRUE", 0 bit otherwise. + +If higher layer parameter *priorityIndicatorDCI-1-1* is configured, if the bit width of the CBG flushing out information in DCI format 1\_1 for one HARQ-ACK codebook is not equal to that of the CBG flushing out information in DCI format 1\_1 for the other HARQ-ACK codebook, a number of most significant bits with value set to '0' are inserted to smaller CBG flushing out information until the bit width of the CBG flushing out information in DCI format 1\_1 for the two HARQ-ACK codebooks are the same. + +- DMRS sequence initialization - 1 bit. +- Priority indicator - 0 bit if higher layer parameter *priorityIndicatorDCI-1-1* is not configured; otherwise 1 bit as defined in Clause 9 in [5, TS 38.213]. +- ChannelAccess-CPext - 0, 1, 2, 3 or 4 bits. The bitwidth for this field is determined as bits, where *I* is the number of entries in the higher layer parameter *ul-AccessConfigListDCI-1-1* or in Table 7.3.1.1.1-4A if *channelAccessMode-r16* = "semiStatic" is provided, for operation in a cell with shared spectrum channel access in frequency range 1, or for operation in frequency range 2-2 if *ChannelAccessMode2-r17* is provided; otherwise 0 bit. One or more entries from Table 7.3.1.2.2-6 or Table 7.3.1.2.2-6A are configured by the higher layer parameter *ul-AccessConfigListDCI-1-1*. +- Minimum applicable scheduling offset indicator - 0 or 1 bit + - 0 bit if higher layer parameter *minimumSchedulingOffsetK0* is not configured; + - 1 bit if higher layer parameter *minimumSchedulingOffsetK0* is configured. The 1 bit indication is used to determine the minimum applicable K0 for the active DL BWP and the minimum applicable K2 value for the active UL BWP, if configured respectively, according to Table 7.3.1.1.2-33. If the minimum applicable K0 is indicated, the minimum applicable value of the aperiodic CSI-RS triggering offset for an active DL BWP shall be the same as the minimum applicable K0 value. +- SCell dormancy indication - 0 bit if higher layer parameter *dormancyGroupWithinActiveTime* is not configured; otherwise 1, 2, 3, 4 or 5 bits bitmap determined according to the number of different *DormancyGroupID(s)* provided by higher layer parameter *dormancyGroupWithinActiveTime*, where each bit corresponds to one of the + +SCell group(s) configured by higher layers parameter *dormancyGroupWithinActiveTime*, with MSB to LSB of the bitmap corresponding to the first to last configured SCell group in ascending order of *DormancyGroupID*. The field is only present when this format is carried by PDCCH on the primary cell within DRX Active Time and the UE is configured with at least two DL BWPs for an SCell. + +If one-shot HARQ-ACK request is not present or set to '0', and all bits of frequency domain resource assignment are set to 0 for resource allocation type 0 or set to 1 for resource allocation type 1 or set to 0 or 1 for dynamic switch resource allocation type, this field is reserved and the following fields among the fields above are used for SCell dormancy indication, where each bit corresponds to one of the configured SCell(s), with MSB to LSB of the following fields concatenated in the order below corresponding to the SCell with lowest to highest SCell index + +- Modulation and coding scheme of transport block 1 +- New data indicator of transport block 1 +- Redundancy version of transport block 1 +- HARQ process number +- Antenna port(s) +- DMRS sequence initialization +- PDCCH monitoring adaptation indication - 0, 1 or 2 bits + - 1 or 2 bits, if *searchSpaceGroupIdList-r17* is not configured and if *pdcch-SkippingDurationList* is configured + - 1 bit if the UE is configured with only one duration by *pdcch-SkippingDurationList*; + - 2 bits if the UE is configured with more than one duration by *pdcch-SkippingDurationList*. + - 1 or 2 bits, if *pdcch-SkippingDurationList* is not configured and if *searchSpaceGroupIdList-r17* is configured + - 1 bit if the UE is configured by *searchSpaceGroupIdList-r17* with search space set(s) with group index 0 and search space set(s) with group index 1, and if the UE is not configured by *searchSpaceGroupIdList-r17* with any search space set with group index 2; + - 2 bits if the UE is configured by *searchSpaceGroupIdList-r17* with search space set(s) with group index 0, search space set(s) with group index 1 and search space set(s) with group index 2; + - 2 bits, if *pdcch-SkippingDurationList* is configured and if *searchSpaceGroupIdList-r17* is configured + - 0 bit, otherwise +- PUCCH Cell indicator - 0 or 1 bit. + - 1 bit if higher layer parameter *pucch-sSCellDyn* is configured. + - 0 bit otherwise. + +If the UE is configured with a PUCCH-SCell, *pucch-sSCellDyn* is replaced by *pucch-sSCellDynSecondaryPUCCHgroup* for the secondary PUCCH group. + +- Co-scheduled UE information – 0 or 3 bits + - 3 bits as defined in Table 7.3.1.2.2-12 if higher layer parameter *XYZ* is configured. This field is reserved if two codewords are scheduled by this DCI format 1\_1. + - 0 bit otherwise. + +If DCI formats 1\_1 are monitored in multiple search spaces associated with multiple CORESETs in a BWP for scheduling the same serving cell, zeros shall be appended until the payload size of the DCI formats 1\_1 monitored in the multiple search spaces equal to the maximum payload size of the DCI format 1\_1 monitored in the multiple search spaces. + +If the number of information bits in DCI format 1\_1 scheduling a single PDSCH prior to padding is not equal to the number of information bits in DCI format 1\_1 scheduling multiple PDSCHs for the same serving cell, zeros shall be appended to the DCI format 1\_1 with smaller size until the payload size is the same for scheduling a single PDSCH and multiple PDSCHs. + +For a UE configured with scheduling on the primary cell from an SCell, if prior to padding the number of information bits in DCI format 1\_1 carried by PDCCH on the primary cell is not equal to the number of information bits in DCI format 1\_1 carried by PDCCH on the SCell for scheduling on the primary cell, zeros shall be appended to the DCI format 1\_1 with smaller size until the payload size is the same: + +- If application of step 4C in clause 7.3.1.0 results in additional zero padding for DCI format 1\_1 for scheduling on the primary cell, corresponding zeros shall be appended to both DCI format 1\_1 monitored on the primary cell and DCI format 1\_1 monitored on the SCell for scheduling on the primary cell. +- If the SCell is deactivated and *firstActiveDownlinkBWP-Id* is not set to dormant BWP, the UE determines the number of information bits in DCI format 1\_1 carried by PDCCH on the primary cell based on a DL BWP provided by *firstActiveDownlinkBWP-Id* for the SCell. If the active DL BWP of the SCell is a dormant DL + +BWP, or if the SCell is deactivated and *firstActiveDownlinkBWP-Id* is set to dormant BWP, the UE determines the number of information bits in DCI format 1\_1 carried by PDCCH on the primary cell based on a DL BWP provided by *firstWithinActiveTimeBWP-Id* for the SCell if provided; otherwise, based on a DL BWP provided by *firstOutsideActiveTimeBWP-Id* for the SCell. + +**Table 7.3.1.2.2-1: Antenna port(s) (1000 + DMRS port), *dmrs-Type=1*, *maxLength=1*** + +| One Codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | +|-------------------------------------------------------------|------------------------------------------|--------------| +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +| 0 | 1 | 0 | +| 1 | 1 | 1 | +| 2 | 1 | 0,1 | +| 3 | 2 | 0 | +| 4 | 2 | 1 | +| 5 | 2 | 2 | +| 6 | 2 | 3 | +| 7 | 2 | 0,1 | +| 8 | 2 | 2,3 | +| 9 | 2 | 0-2 | +| 10 | 2 | 0-3 | +| 11 | 2 | 0,2 | +| 12-15 | Reserved | Reserved | + +**Table 7.3.1.2.2-1A: Antenna port(s) (1000 + DMRS port), *dmrs-Type=1*, *maxLength=1*** + +| One Codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | +|-------------------------------------------------------------|------------------------------------------|--------------| +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +| 0 | 1 | 0 | +| 1 | 1 | 1 | +| 2 | 1 | 0,1 | +| 3 | 2 | 0 | +| 4 | 2 | 1 | +| 5 | 2 | 2 | +| 6 | 2 | 3 | +| 7 | 2 | 0,1 | +| 8 | 2 | 2,3 | +| 9 | 2 | 0-2 | +| 10 | 2 | 0-3 | +| 11 | 2 | 0,2 | +| 12 | 2 | 0,2,3 | +| 13-15 | Reserved | Reserved | + +**Table 7.3.1.2.2-2: Antenna port(s) (1000 + DMRS port), *dmrs-Type=1*, *maxLength=2*** + +| One Codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | | +|-------------------------------------------------------------|------------------------------------------|--------------|------------------------------|-------------------------------------------------------------|------------------------------------------|-----------------|------------------------------| +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +| 0 | 1 | 0 | 1 | 0 | 2 | 0-4 | 2 | +| 1 | 1 | 1 | 1 | 1 | 2 | 0,1,2,3,4,6 | 2 | +| 2 | 1 | 0,1 | 1 | 2 | 2 | 0,1,2,3,4,5,6 | 2 | +| 3 | 2 | 0 | 1 | 3 | 2 | 0,1,2,3,4,5,6,7 | 2 | +| 4 | 2 | 1 | 1 | 4-31 | reserved | reserved | reserved | +| 5 | 2 | 2 | 1 | | | | | +| 6 | 2 | 3 | 1 | | | | | +| 7 | 2 | 0,1 | 1 | | | | | +| 8 | 2 | 2,3 | 1 | | | | | +| 9 | 2 | 0-2 | 1 | | | | | +| 10 | 2 | 0-3 | 1 | | | | | +| 11 | 2 | 0,2 | 1 | | | | | +| 12 | 2 | 0 | 2 | | | | | +| 13 | 2 | 1 | 2 | | | | | +| 14 | 2 | 2 | 2 | | | | | +| 15 | 2 | 3 | 2 | | | | | +| 16 | 2 | 4 | 2 | | | | | +| 17 | 2 | 5 | 2 | | | | | +| 18 | 2 | 6 | 2 | | | | | +| 19 | 2 | 7 | 2 | | | | | +| 20 | 2 | 0,1 | 2 | | | | | +| 21 | 2 | 2,3 | 2 | | | | | +| 22 | 2 | 4,5 | 2 | | | | | +| 23 | 2 | 6,7 | 2 | | | | | +| 24 | 2 | 0,4 | 2 | | | | | +| 25 | 2 | 2,6 | 2 | | | | | +| 26 | 2 | 0,1,4 | 2 | | | | | +| 27 | 2 | 2,3,6 | 2 | | | | | +| 28 | 2 | 0,1,4,5 | 2 | | | | | +| 29 | 2 | 2,3,6,7 | 2 | | | | | +| 30 | 2 | 0,2,4,6 | 2 | | | | | +| 31 | Reserved | Reserved | Reserved | | | | | + +**Table 7.3.1.2.2-2A: Antenna port(s) (1000 + DMRS port), *dmrs-Type=1*, *maxLength=2*** + +| One Codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | | +|-------------------------------------------------------------|------------------------------------------|--------------|------------------------------|-------------------------------------------------------------|------------------------------------------|-----------------|------------------------------| +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +| 0 | 1 | 0 | 1 | 0 | 2 | 0-4 | 2 | +| 1 | 1 | 1 | 1 | 1 | 2 | 0,1,2,3,4,6 | 2 | +| 2 | 1 | 0,1 | 1 | 2 | 2 | 0,1,2,3,4,5,6 | 2 | +| 3 | 2 | 0 | 1 | 3 | 2 | 0,1,2,3,4,5,6,7 | 2 | +| 4 | 2 | 1 | 1 | 4-31 | reserved | reserved | reserved | +| 5 | 2 | 2 | 1 | | | | | +| 6 | 2 | 3 | 1 | | | | | +| 7 | 2 | 0,1 | 1 | | | | | +| 8 | 2 | 2,3 | 1 | | | | | +| 9 | 2 | 0-2 | 1 | | | | | +| 10 | 2 | 0-3 | 1 | | | | | +| 11 | 2 | 0,2 | 1 | | | | | +| 12 | 2 | 0 | 2 | | | | | +| 13 | 2 | 1 | 2 | | | | | +| 14 | 2 | 2 | 2 | | | | | +| 15 | 2 | 3 | 2 | | | | | +| 16 | 2 | 4 | 2 | | | | | +| 17 | 2 | 5 | 2 | | | | | +| 18 | 2 | 6 | 2 | | | | | +| 19 | 2 | 7 | 2 | | | | | +| 20 | 2 | 0,1 | 2 | | | | | +| 21 | 2 | 2,3 | 2 | | | | | +| 22 | 2 | 4,5 | 2 | | | | | +| 23 | 2 | 6,7 | 2 | | | | | +| 24 | 2 | 0,4 | 2 | | | | | +| 25 | 2 | 2,6 | 2 | | | | | +| 26 | 2 | 0,1,4 | 2 | | | | | +| 27 | 2 | 2,3,6 | 2 | | | | | +| 28 | 2 | 0,1,4,5 | 2 | | | | | +| 29 | 2 | 2,3,6,7 | 2 | | | | | +| 30 | 2 | 0,2,4,6 | 2 | | | | | +| 31 | 2 | 0,2,3 | 1 | | | | | + +**Table 7.3.1.2.2-3: Antenna port(s) (1000 + DMRS port), *dmrs-Type=2*, *maxLength=1*** + +| One codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | Two codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | +|-------------------------------------------------------------|---------------------------------------------------|-----------------|-------------------------------------------------------------|---------------------------------------------------|-----------------| +| Value | Number of
DMRS CDM
group(s)
without data | DMRS
port(s) | Value | Number of
DMRS CDM
group(s)
without data | DMRS
port(s) | +| 0 | 1 | 0 | 0 | 3 | 0-4 | +| 1 | 1 | 1 | 1 | 3 | 0-5 | +| 2 | 1 | 0,1 | 2-31 | reserved | reserved | +| 3 | 2 | 0 | | | | +| 4 | 2 | 1 | | | | +| 5 | 2 | 2 | | | | +| 6 | 2 | 3 | | | | +| 7 | 2 | 0,1 | | | | +| 8 | 2 | 2,3 | | | | +| 9 | 2 | 0-2 | | | | +| 10 | 2 | 0-3 | | | | +| 11 | 3 | 0 | | | | +| 12 | 3 | 1 | | | | +| 13 | 3 | 2 | | | | +| 14 | 3 | 3 | | | | +| 15 | 3 | 4 | | | | +| 16 | 3 | 5 | | | | +| 17 | 3 | 0,1 | | | | +| 18 | 3 | 2,3 | | | | +| 19 | 3 | 4,5 | | | | +| 20 | 3 | 0-2 | | | | +| 21 | 3 | 3-5 | | | | +| 22 | 3 | 0-3 | | | | +| 23 | 2 | 0,2 | | | | +| 24-31 | Reserved | Reserved | | | | + +**Table 7.3.1.2.2-3A: Antenna port(s) (1000 + DMRS port), *dmrs-Type=2*, *maxLength=1*** + +| One codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | Two codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | +|-------------------------------------------------------------|---------------------------------------------------|-----------------|-------------------------------------------------------------|---------------------------------------------------|-----------------| +| Value | Number of
DMRS CDM
group(s)
without data | DMRS
port(s) | Value | Number of
DMRS CDM
group(s)
without data | DMRS
port(s) | +| 0 | 1 | 0 | 0 | 3 | 0-4 | +| 1 | 1 | 1 | 1 | 3 | 0-5 | +| 2 | 1 | 0,1 | 2-31 | reserved | reserved | +| 3 | 2 | 0 | | | | +| 4 | 2 | 1 | | | | +| 5 | 2 | 2 | | | | +| 6 | 2 | 3 | | | | +| 7 | 2 | 0,1 | | | | +| 8 | 2 | 2,3 | | | | +| 9 | 2 | 0-2 | | | | +| 10 | 2 | 0-3 | | | | +| 11 | 3 | 0 | | | | +| 12 | 3 | 1 | | | | +| 13 | 3 | 2 | | | | +| 14 | 3 | 3 | | | | +| 15 | 3 | 4 | | | | +| 16 | 3 | 5 | | | | +| 17 | 3 | 0,1 | | | | +| 18 | 3 | 2,3 | | | | +| 19 | 3 | 4,5 | | | | +| 20 | 3 | 0-2 | | | | +| 21 | 3 | 3-5 | | | | +| 22 | 3 | 0-3 | | | | +| 23 | 2 | 0,2 | | | | +| 24 | 2 | 0,2,3 | | | | +| 25-31 | Reserved | Reserved | | | | + +**Table 7.3.1.2.2-4: Antenna port(s) (1000 + DMRS port), *dmrs-Type=2*, *maxLength=2*** + +| One codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | | +|-------------------------------------------------------------|---------------------------------------------------|-----------------|------------------------------------|-------------------------------------------------------------|------------------------------------------------------|-----------------|------------------------------------| +| Value | Number of
DMRS CDM
group(s)
without data | DMRS
port(s) | Number of
front-load
symbols | Value | Number of
DMRS CDM
group(s)
without
data | DMRS
port(s) | Number of
front-load
symbols | +| 0 | 1 | 0 | 1 | 0 | 3 | 0-4 | 1 | +| 1 | 1 | 1 | 1 | 1 | 3 | 0-5 | 1 | +| 2 | 1 | 0,1 | 1 | 2 | 2 | 0,1,2,3,6 | 2 | +| 3 | 2 | 0 | 1 | 3 | 2 | 0,1,2,3,6,8 | 2 | +| 4 | 2 | 1 | 1 | 4 | 2 | 0,1,2,3,6,7,8 | 2 | +| 5 | 2 | 2 | 1 | 5 | 2 | 0,1,2,3,6,7,8,9 | 2 | +| 6 | 2 | 3 | 1 | 6-63 | Reserved | Reserved | Reserved | +| 7 | 2 | 0,1 | 1 | | | | | +| 8 | 2 | 2,3 | 1 | | | | | +| 9 | 2 | 0-2 | 1 | | | | | +| 10 | 2 | 0-3 | 1 | | | | | +| 11 | 3 | 0 | 1 | | | | | +| 12 | 3 | 1 | 1 | | | | | +| 13 | 3 | 2 | 1 | | | | | +| 14 | 3 | 3 | 1 | | | | | +| 15 | 3 | 4 | 1 | | | | | +| 16 | 3 | 5 | 1 | | | | | +| 17 | 3 | 0,1 | 1 | | | | | +| 18 | 3 | 2,3 | 1 | | | | | + +| One codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | | +|-------------------------------------------------------------|------------------------------------------|--------------|------------------------------|-------------------------------------------------------------|------------------------------------------|--------------|------------------------------| +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +| 19 | 3 | 4,5 | 1 | | | | | +| 20 | 3 | 0-2 | 1 | | | | | +| 21 | 3 | 3-5 | 1 | | | | | +| 22 | 3 | 0-3 | 1 | | | | | +| 23 | 2 | 0,2 | 1 | | | | | +| 24 | 3 | 0 | 2 | | | | | +| 25 | 3 | 1 | 2 | | | | | +| 26 | 3 | 2 | 2 | | | | | +| 27 | 3 | 3 | 2 | | | | | +| 28 | 3 | 4 | 2 | | | | | +| 29 | 3 | 5 | 2 | | | | | +| 30 | 3 | 6 | 2 | | | | | +| 31 | 3 | 7 | 2 | | | | | +| 32 | 3 | 8 | 2 | | | | | +| 33 | 3 | 9 | 2 | | | | | +| 34 | 3 | 10 | 2 | | | | | +| 35 | 3 | 11 | 2 | | | | | +| 36 | 3 | 0,1 | 2 | | | | | +| 37 | 3 | 2,3 | 2 | | | | | +| 38 | 3 | 4,5 | 2 | | | | | +| 39 | 3 | 6,7 | 2 | | | | | +| 40 | 3 | 8,9 | 2 | | | | | +| 41 | 3 | 10,11 | 2 | | | | | +| 42 | 3 | 0,1,6 | 2 | | | | | +| 43 | 3 | 2,3,8 | 2 | | | | | +| 44 | 3 | 4,5,10 | 2 | | | | | +| 45 | 3 | 0,1,6,7 | 2 | | | | | +| 46 | 3 | 2,3,8,9 | 2 | | | | | +| 47 | 3 | 4,5,10,11 | 2 | | | | | +| 48 | 1 | 0 | 2 | | | | | +| 49 | 1 | 1 | 2 | | | | | +| 50 | 1 | 6 | 2 | | | | | +| 51 | 1 | 7 | 2 | | | | | +| 52 | 1 | 0,1 | 2 | | | | | +| 53 | 1 | 6,7 | 2 | | | | | +| 54 | 2 | 0,1 | 2 | | | | | +| 55 | 2 | 2,3 | 2 | | | | | +| 56 | 2 | 6,7 | 2 | | | | | +| 57 | 2 | 8,9 | 2 | | | | | +| 58-63 | Reserved | Reserved | Reserved | | | | | + +Table 7.3.1.2.2-4A: Antenna port(s) (1000 + DMRS port), *dmrs-Type=2*, *maxLength=2* + +| One codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | | +|-------------------------------------------------------------|------------------------------------------|--------------|------------------------------|-------------------------------------------------------------|------------------------------------------|-----------------|------------------------------| +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +| 0 | 1 | 0 | 1 | 0 | 3 | 0-4 | 1 | +| 1 | 1 | 1 | 1 | 1 | 3 | 0-5 | 1 | +| 2 | 1 | 0,1 | 1 | 2 | 2 | 0,1,2,3,6 | 2 | +| 3 | 2 | 0 | 1 | 3 | 2 | 0,1,2,3,6,8 | 2 | +| 4 | 2 | 1 | 1 | 4 | 2 | 0,1,2,3,6,7,8 | 2 | +| 5 | 2 | 2 | 1 | 5 | 2 | 0,1,2,3,6,7,8,9 | 2 | + +| One codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | | +|-------------------------------------------------------------|---------------------------------------------------|-----------------|------------------------------------|-------------------------------------------------------------|------------------------------------------------------|--------------|------------------------------------| +| Value | Number of
DMRS CDM
group(s)
without data | DMRS
port(s) | Number of
front-load
symbols | Value | Number of
DMRS CDM
group(s)
without
data | DMRS port(s) | Number of
front-load
symbols | +| 6 | 2 | 3 | 1 | 6-63 | Reserved | Reserved | Reserved | +| 7 | 2 | 0,1 | 1 | | | | | +| 8 | 2 | 2,3 | 1 | | | | | +| 9 | 2 | 0-2 | 1 | | | | | +| 10 | 2 | 0-3 | 1 | | | | | +| 11 | 3 | 0 | 1 | | | | | +| 12 | 3 | 1 | 1 | | | | | +| 13 | 3 | 2 | 1 | | | | | +| 14 | 3 | 3 | 1 | | | | | +| 15 | 3 | 4 | 1 | | | | | +| 16 | 3 | 5 | 1 | | | | | +| 17 | 3 | 0,1 | 1 | | | | | +| 18 | 3 | 2,3 | 1 | | | | | +| 19 | 3 | 4,5 | 1 | | | | | +| 20 | 3 | 0-2 | 1 | | | | | +| 21 | 3 | 3-5 | 1 | | | | | +| 22 | 3 | 0-3 | 1 | | | | | +| 23 | 2 | 0,2 | 1 | | | | | +| 24 | 3 | 0 | 2 | | | | | +| 25 | 3 | 1 | 2 | | | | | +| 26 | 3 | 2 | 2 | | | | | +| 27 | 3 | 3 | 2 | | | | | +| 28 | 3 | 4 | 2 | | | | | +| 29 | 3 | 5 | 2 | | | | | +| 30 | 3 | 6 | 2 | | | | | +| 31 | 3 | 7 | 2 | | | | | +| 32 | 3 | 8 | 2 | | | | | +| 33 | 3 | 9 | 2 | | | | | +| 34 | 3 | 10 | 2 | | | | | +| 35 | 3 | 11 | 2 | | | | | +| 36 | 3 | 0,1 | 2 | | | | | +| 37 | 3 | 2,3 | 2 | | | | | +| 38 | 3 | 4,5 | 2 | | | | | +| 39 | 3 | 6,7 | 2 | | | | | +| 40 | 3 | 8,9 | 2 | | | | | +| 41 | 3 | 10,11 | 2 | | | | | +| 42 | 3 | 0,1,6 | 2 | | | | | +| 43 | 3 | 2,3,8 | 2 | | | | | +| 44 | 3 | 4,5,10 | 2 | | | | | +| 45 | 3 | 0,1,6,7 | 2 | | | | | +| 46 | 3 | 2,3,8,9 | 2 | | | | | +| 47 | 3 | 4,5,10,11 | 2 | | | | | +| 48 | 1 | 0 | 2 | | | | | +| 49 | 1 | 1 | 2 | | | | | +| 50 | 1 | 6 | 2 | | | | | +| 51 | 1 | 7 | 2 | | | | | +| 52 | 1 | 0,1 | 2 | | | | | +| 53 | 1 | 6,7 | 2 | | | | | +| 54 | 2 | 0,1 | 2 | | | | | +| 55 | 2 | 2,3 | 2 | | | | | +| 56 | 2 | 6,7 | 2 | | | | | +| 57 | 2 | 8,9 | 2 | | | | | +| 58 | 2 | 0,2,3 | 1 | | | | | +| 59-63 | Reserved | Reserved | Reserved | | | | | + +**Table 7.3.1.2.2-5: VRB-to-PRB mapping** + +| Bit field mapped to index | VRB-to-PRB mapping | +|---------------------------|--------------------| +| 0 | Non-interleaved | +| 1 | Interleaved | + +**Table 7.3.1.2.2-6: Allowed entries for DCI format 1\_1 and DCI format 1\_2, configured by higher layer parameter *ul-AccessConfigListDCI-1-1* and *ul-AccessConfigListDCI-1-2*, respectively, in frequency range 1** + +| Entry index | Channel Access Type | The CP extension Text index defined in Clause 5.3.1 of [4, TS 38.211] | +|-------------|----------------------------------------------------------------------|-----------------------------------------------------------------------| +| 0 | Type2C-ULChannelAccess defined in clause 4.2.1.2.3 in TS 37.213 [14] | 0 | +| 1 | Type2C-ULChannelAccess defined in clause 4.2.1.2.3 in TS 37.213 [14] | 2 | +| 2 | Type2B-ULChannelAccess defined in clause 4.2.1.2.2 in TS 37.213 [14] | 0 | +| 3 | Type2B-ULChannelAccess defined in clause 4.2.1.2.2 in TS 37.213 [14] | 2 | +| 4 | Type2A-ULChannelAccess defined in clause 4.2.1.2.1 in TS 37.213 [14] | 0 | +| 5 | Type2A-ULChannelAccess defined in clause 4.2.1.2.1 in TS 37.213 [14] | 1 | +| 6 | Type2A-ULChannelAccess defined in clause 4.2.1.2.1 in TS 37.213 [14] | 3 | +| 7 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 0 | +| 8 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 1 | +| 9 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 2 | +| 10 | Type1-ULChannelAccess defined in clause 4.2.1.1 in TS 37.213 [14] | 3 | + +**Table 7.3.1.2.2-6A: Allowed entries for DCI format 1\_1 and DCI format 1\_2, configured by higher layer parameter *ul-AccessConfigListDCI-1-1* in frequency range 2-2** + +| Entry index | Channel Access Type | +|-------------|-----------------------------------------------------------------| +| 0 | Type 1 channel access defined in clause 4.4.1 of TS 37.213 [14] | +| 1 | Type 2 channel access defined in clause 4.4.2 of TS 37.213 [14] | +| 2 | Type 3 channel access defined in clause 4.4.3 of TS 37.213 [14] | + +**Table 7.3.1.2.2-7: Antenna port(s) (1000 + DMRS port), *dmrs-Type=1*, *enhanced-dmrs-Type* is configured, *maxLength=1*** + +| One Codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | +|-------------------------------------------------------------|------------------------------------------|--------------|-------------------------------------------------------------|------------------------------------------|-------------------| +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +| 0 | 1 | 0 | 0 | 2 | 0,1,2,3,8 | +| 1 | 1 | 1 | 1 | 2 | 0,1,2,3,8,10 | +| 2 | 1 | 0,1 | 2 | 2 | 0,1,2,3,8,9,10 | +| 3 | 2 | 0 | 3 | 2 | 0,1,2,3,8,9,10,11 | +| 4 | 2 | 1 | 4-31 | Reserved | Reserved | +| 5 | 2 | 2 | | | | +| 6 | 2 | 3 | | | | +| 7 | 2 | 0,1 | | | | +| 8 | 2 | 2,3 | | | | +| 9 | 2 | 0-2 | | | | +| 10 | 2 | 0-3 | | | | +| 11 | 2 | 0,2 | | | | +| 12 | 1 | 8 | | | | +| 13 | 1 | 9 | | | | +| 14 | 1 | 8,9 | | | | +| 15 | 2 | 8 | | | | +| 16 | 2 | 9 | | | | +| 17 | 2 | 10 | | | | +| 18 | 2 | 11 | | | | +| 19 | 2 | 8,9 | | | | +| 20 | 2 | 10,11 | | | | + +| One Codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | +|-------------------------------------------------------------|------------------------------------------|--------------|-------------------------------------------------------------|------------------------------------------|--------------| +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +| 21 | 1 | 0,1,8 | | | | +| 22 | 1 | 0,1,8,9 | | | | +| 23 | 2 | 0,1,8 | | | | +| 24 | 2 | 0,1,8,9 | | | | +| 25 | 2 | 2,3,10 | | | | +| 26 | 2 | 2,3,10,11 | | | | +| 27-31 | Reserved | Reserved | | | | + +Table 7.3.1.2.2-7A: Antenna port(s) (1000 + DMRS port), *dmrs-Type=1*, *enhanced-dmrs-Type* is configured, *maxLength=1* + +| One Codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | +|-------------------------------------------------------------|------------------------------------------|--------------|-------------------------------------------------------------|------------------------------------------|-------------------| +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +| 0 | 1 | 0 | 0 | 2 | 0,1,2,3,8 | +| 1 | 1 | 1 | 1 | 2 | 0,1,2,3,8,10 | +| 2 | 1 | 0,1 | 2 | 2 | 0,1,2,3,8,9,10 | +| 3 | 2 | 0 | 3 | 2 | 0,1,2,3,8,9,10,11 | +| 4 | 2 | 1 | 4-31 | Reserved | Reserved | +| 5 | 2 | 2 | | | | +| 6 | 2 | 3 | | | | +| 7 | 2 | 0,1 | | | | +| 8 | 2 | 2,3 | | | | +| 9 | 2 | 0-2 | | | | +| 10 | 2 | 0-3 | | | | +| 11 | 2 | 0,2 | | | | +| 12 | 1 | 8 | | | | +| 13 | 1 | 9 | | | | +| 14 | 1 | 8,9 | | | | +| 15 | 2 | 8 | | | | +| 16 | 2 | 9 | | | | +| 17 | 2 | 10 | | | | +| 18 | 2 | 11 | | | | +| 19 | 2 | 8,9 | | | | +| 20 | 2 | 10,11 | | | | +| 21 | 1 | 0,1,8 | | | | +| 22 | 1 | 0,1,8,9 | | | | +| 23 | 2 | 0,1,8 | | | | +| 24 | 2 | 0,1,8,9 | | | | +| 25 | 2 | 2,3,10 | | | | +| 26 | 2 | 2,3,10,11 | | | | +| 27 | 2 | 0,2,3 | | | | +| 28-31 | Reserved | Reserved | | | | + +Table 7.3.1.2.2-8: Antenna port(s) (1000 + DMRS port), *dmrs-Type=1*, *enhanced-dmrs-Type* is configured, *maxLength=2* + +| One Codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | | +|-------------------------------------------------------------|------------------------------------------|--------------|------------------------------|-------------------------------------------------------------|------------------------------------------|--------------|------------------------------| +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +| 0 | 1 | 0 | 1 | 0 | 2 | 0,1,2,3,8 | 1 | +| 1 | 1 | 1 | 1 | 1 | 2 | 0,1,2,3,8,10 | 1 | + +| One Codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | | +|----------------------------------------------------------------------|-----------------------------------------------------------------|-------------------------|---------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------|---------------------|---------------------------------------------| +| Value | Number of
DMRS CDM
group(s)
without
data | DMRS
port(s) | Number of
front-load
symbols | Value | Number of
DMRS CDM
group(s)
without
data | DMRS port(s) | Number of
front-load
symbols | +| 2 | 1 | 0,1 | 1 | 2 | 2 | 0,1,2,3,8,9,10 | 1 | +| 3 | 2 | 0 | 1 | 3 | 2 | 0,1,2,3,8,9,10,11 | 1 | +| 4 | 2 | 1 | 1 | 4 | 2 | 0-4 | 2 | +| 5 | 2 | 2 | 1 | 5 | 2 | 0,1,2,3,4,6 | 2 | +| 6 | 2 | 3 | 1 | 6 | 2 | 0,1,2,3,4,5,6 | 2 | +| 7 | 2 | 0,1 | 1 | 7 | 2 | 0,1,2,3,4,5,6,7 | 2 | +| 8 | 2 | 2,3 | 1 | 8 | 1 | 0,1,4,5,8 | 2 | +| 9 | 2 | 0-2 | 1 | 9 | 1 | 0,1,4,5,8,12 | 2 | +| 10 | 2 | 0-3 | 1 | 10 | 1 | 0,1,4,5,8,9,12 | 2 | +| 11 | 2 | 0,2 | 1 | 11 | 1 | 0,1,4,5,8,9,12,13 | 2 | +| 12 | 1 | 8 | 1 | 12 | 2 | 0,1,4,5,8 | 2 | +| 13 | 1 | 9 | 1 | 13 | 2 | 0,1,4,5,8,12 | 2 | +| 14 | 1 | 8,9 | 1 | 14 | 2 | 0,1,4,5,8,9,12 | 2 | +| 15 | 2 | 8 | 1 | 15 | 2 | 0,1,4,5,8,9,12,13 | 2 | +| 16 | 2 | 9 | 1 | 16~127 | Reserved | Reserved | Reserved | +| 17 | 2 | 10 | 1 | | | | | +| 18 | 2 | 11 | 1 | | | | | +| 19 | 2 | 8,9 | 1 | | | | | +| 20 | 2 | 10,11 | 1 | | | | | +| 21 | 1 | 0,1,8 | 1 | | | | | +| 22 | 1 | 0,1,8,9 | 1 | | | | | +| 23 | 2 | 0,1,8 | 1 | | | | | +| 24 | 2 | 0,1,8,9 | 1 | | | | | +| 25 | 2 | 2,3,10 | 1 | | | | | +| 26 | 2 | 2,3,10,11 | 1 | | | | | +| 27 | 2 | 0 | 2 | | | | | +| 28 | 2 | 1 | 2 | | | | | +| 29 | 2 | 2 | 2 | | | | | +| 30 | 2 | 3 | 2 | | | | | +| 31 | 2 | 4 | 2 | | | | | +| 32 | 2 | 5 | 2 | | | | | +| 33 | 2 | 6 | 2 | | | | | +| 34 | 2 | 7 | 2 | | | | | +| 35 | 2 | 0,1 | 2 | | | | | +| 36 | 2 | 2,3 | 2 | | | | | +| 37 | 2 | 4,5 | 2 | | | | | +| 38 | 2 | 6,7 | 2 | | | | | +| 39 | 2 | 0,4 | 2 | | | | | +| 40 | 2 | 2,6 | 2 | | | | | +| 41 | 2 | 0,1,4 | 2 | | | | | +| 42 | 2 | 2,3,6 | 2 | | | | | +| 43 | 2 | 0,1,4,5 | 2 | | | | | +| 44 | 2 | 2,3,6,7 | 2 | | | | | +| 45 | 2 | 0,2,4,6 | 2 | | | | | +| 46 | 2 | 8 | 2 | | | | | +| 47 | 2 | 9 | 2 | | | | | +| 48 | 2 | 10 | 2 | | | | | +| 49 | 2 | 11 | 2 | | | | | +| 50 | 2 | 12 | 2 | | | | | +| 51 | 2 | 13 | 2 | | | | | +| 52 | 2 | 14 | 2 | | | | | +| 53 | 2 | 15 | 2 | | | | | +| 54 | 2 | 8,9 | 2 | | | | | +| 55 | 2 | 10,11 | 2 | | | | | +| 56 | 2 | 12,13 | 2 | | | | | +| 57 | 2 | 14,15 | 2 | | | | | +| 58 | 2 | 0,1,8 | 2 | | | | | +| 59 | 2 | 0,1,8,9 | 2 | | | | | + +| One Codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | | +|-------------------------------------------------------------|------------------------------------------|--------------|------------------------------|-------------------------------------------------------------|------------------------------------------|--------------|------------------------------| +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +| 60 | 2 | 4,5,12 | 2 | | | | | +| 61 | 2 | 4,5,12,13 | 2 | | | | | +| 62 | 2 | 2,3,10 | 2 | | | | | +| 63 | 2 | 2,3,10,11 | 2 | | | | | +| 64 | 2 | 6,7,14 | 2 | | | | | +| 65 | 2 | 6,7,14,15 | 2 | | | | | +| 66-127 | Reserved | Reserved | Reserved | | | | | + +Table 7.3.1.2.2-8A: Antenna port(s) (1000 + DMRS port), *dmrs-Type=1*, *enhanced-dmrs-Type* is configured, *maxLength=2* + +| One Codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | | +|-------------------------------------------------------------|------------------------------------------|--------------|------------------------------|-------------------------------------------------------------|------------------------------------------|-------------------|------------------------------| +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +| 0 | 1 | 0 | 1 | 0 | 2 | 0,1,2,3,8 | 1 | +| 1 | 1 | 1 | 1 | 1 | 2 | 0,1,2,3,8,10 | 1 | +| 2 | 1 | 0,1 | 1 | 2 | 2 | 0,1,2,3,8,9,10 | 1 | +| 3 | 2 | 0 | 1 | 3 | 2 | 0,1,2,3,8,9,10,11 | 1 | +| 4 | 2 | 1 | 1 | 4 | 2 | 0-4 | 2 | +| 5 | 2 | 2 | 1 | 5 | 2 | 0,1,2,3,4,6 | 2 | +| 6 | 2 | 3 | 1 | 6 | 2 | 0,1,2,3,4,5,6 | 2 | +| 7 | 2 | 0,1 | 1 | 7 | 2 | 0,1,2,3,4,5,6,7 | 2 | +| 8 | 2 | 2,3 | 1 | 8 | 1 | 0,1,4,5,8 | 2 | +| 9 | 2 | 0-2 | 1 | 9 | 1 | 0,1,4,5,8,12 | 2 | +| 10 | 2 | 0-3 | 1 | 10 | 1 | 0,1,4,5,8,9,12 | 2 | +| 11 | 2 | 0,2 | 1 | 11 | 1 | 0,1,4,5,8,9,12,13 | 2 | +| 12 | 1 | 8 | 1 | 12 | 2 | 0,1,4,5,8 | 2 | +| 13 | 1 | 9 | 1 | 13 | 2 | 0,1,4,5,8,12 | 2 | +| 14 | 1 | 8,9 | 1 | 14 | 2 | 0,1,4,5,8,9,12 | 2 | +| 15 | 2 | 8 | 1 | 15 | 2 | 0,1,4,5,8,9,12,13 | 2 | +| 16 | 2 | 9 | 1 | 16~127 | Reserved | Reserved | Reserved | +| 17 | 2 | 10 | 1 | | | | | +| 18 | 2 | 11 | 1 | | | | | +| 19 | 2 | 8,9 | 1 | | | | | +| 20 | 2 | 10,11 | 1 | | | | | +| 21 | 1 | 0,1,8 | 1 | | | | | +| 22 | 1 | 0,1,8,9 | 1 | | | | | +| 23 | 2 | 0,1,8 | 1 | | | | | +| 24 | 2 | 0,1,8,9 | 1 | | | | | +| 25 | 2 | 2,3,10 | 1 | | | | | +| 26 | 2 | 2,3,10,11 | 1 | | | | | +| 27 | 2 | 0 | 2 | | | | | +| 28 | 2 | 1 | 2 | | | | | +| 29 | 2 | 2 | 2 | | | | | +| 30 | 2 | 3 | 2 | | | | | +| 31 | 2 | 4 | 2 | | | | | +| 32 | 2 | 5 | 2 | | | | | +| 33 | 2 | 6 | 2 | | | | | +| 34 | 2 | 7 | 2 | | | | | +| 35 | 2 | 0,1 | 2 | | | | | +| 36 | 2 | 2,3 | 2 | | | | | +| 37 | 2 | 4,5 | 2 | | | | | + +| One Codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | | +|-------------------------------------------------------------|------------------------------------------|--------------|------------------------------|-------------------------------------------------------------|------------------------------------------|--------------|------------------------------| +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +| 38 | 2 | 6,7 | 2 | | | | | +| 39 | 2 | 0,4 | 2 | | | | | +| 40 | 2 | 2,6 | 2 | | | | | +| 41 | 2 | 0,1,4 | 2 | | | | | +| 42 | 2 | 2,3,6 | 2 | | | | | +| 43 | 2 | 0,1,4,5 | 2 | | | | | +| 44 | 2 | 2,3,6,7 | 2 | | | | | +| 45 | 2 | 0,2,4,6 | 2 | | | | | +| 46 | 2 | 8 | 2 | | | | | +| 47 | 2 | 9 | 2 | | | | | +| 48 | 2 | 10 | 2 | | | | | +| 49 | 2 | 11 | 2 | | | | | +| 50 | 2 | 12 | 2 | | | | | +| 51 | 2 | 13 | 2 | | | | | +| 52 | 2 | 14 | 2 | | | | | +| 53 | 2 | 15 | 2 | | | | | +| 54 | 2 | 8,9 | 2 | | | | | +| 55 | 2 | 10,11 | 2 | | | | | +| 56 | 2 | 12,13 | 2 | | | | | +| 57 | 2 | 14,15 | 2 | | | | | +| 58 | 2 | 0,1,8 | 2 | | | | | +| 59 | 2 | 0,1,8,9 | 2 | | | | | +| 60 | 2 | 4,5,12 | 2 | | | | | +| 61 | 2 | 4,5,12,13 | 2 | | | | | +| 62 | 2 | 2,3,10 | 2 | | | | | +| 63 | 2 | 2,3,10,11 | 2 | | | | | +| 64 | 2 | 6,7,14 | 2 | | | | | +| 65 | 2 | 6,7,14,15 | 2 | | | | | +| 66 | 2 | 0,2,3 | 1 | | | | | +| 67-127 | Reserved | Reserved | Reserved | | | | | + +**Table 7.3.1.2.2-9: Antenna port(s) (1000 + DMRS port), *dmrs-Type=2*, *enhanced-dmrs-Type* is configured, *maxLength=1*** + +| One codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | Two codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | +|-------------------------------------------------------------|------------------------------------------|--------------|-------------------------------------------------------------|------------------------------------------|---------------| +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +| 0 | 1 | 0 | 0 | 3 | 0-4 | +| 1 | 1 | 1 | 1 | 3 | 0-5 | +| 2 | 1 | 0,1 | 2 | 2 | 0,1,2,3,12 | +| 3 | 2 | 0 | 3 | 2 | 0,1,2,3,12,14 | +| 4 | 2 | 1 | 4 | 2 | 0-3,12-14 | +| 5 | 2 | 2 | 5 | 2 | 0-3,12-15 | +| 6 | 2 | 3 | 6 | 3 | 0,1,2,3,12 | +| 7 | 2 | 0,1 | 7 | 3 | 0,1,2,3,12,14 | +| 8 | 2 | 2,3 | 8 | 3 | 0-3,12-14 | +| 9 | 2 | 0-2 | 9 | 3 | 0-3,12-15 | +| 10 | 2 | 0-3 | 10~63 | Reserved | Reserved | +| 11 | 3 | 0 | | | | +| 12 | 3 | 1 | | | | +| 13 | 3 | 2 | | | | +| 14 | 3 | 3 | | | | +| 15 | 3 | 4 | | | | +| 16 | 3 | 5 | | | | +| 17 | 3 | 0,1 | | | | + +| One codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | Two codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | +|----------------------------------------------------------------------|-----------------------------------------------------|-------------------------|----------------------------------------------------------------------|-----------------------------------------------------|---------------------| +| Value | Number of DMRS CDM
group(s) without data | DMRS
port(s) | Value | Number of DMRS CDM
group(s) without data | DMRS port(s) | +| 18 | 3 | 2,3 | | | | +| 19 | 3 | 4,5 | | | | +| 20 | 3 | 0-2 | | | | +| 21 | 3 | 3-5 | | | | +| 22 | 3 | 0-3 | | | | +| 23 | 2 | 0,2 | | | | +| 24 | 1 | 12 | | | | +| 25 | 1 | 13 | | | | +| 26 | 1 | 12,13 | | | | +| 27 | 2 | 12 | | | | +| 28 | 2 | 13 | | | | +| 29 | 2 | 14 | | | | +| 30 | 2 | 15 | | | | +| 31 | 2 | 12,13 | | | | +| 32 | 2 | 14,15 | | | | +| 33 | 3 | 12 | | | | +| 34 | 3 | 13 | | | | +| 35 | 3 | 14 | | | | +| 36 | 3 | 15 | | | | +| 37 | 3 | 16 | | | | +| 38 | 3 | 17 | | | | +| 39 | 3 | 12,13 | | | | +| 40 | 3 | 14,15 | | | | +| 41 | 3 | 16,17 | | | | +| 42 | 1 | 0,1,12 | | | | +| 43 | 1 | 0,1,12,13 | | | | +| 44 | 2 | 0,1,12 | | | | +| 45 | 2 | 0,1,12,13 | | | | +| 46 | 2 | 2,3,14 | | | | +| 47 | 2 | 2,3,14,15 | | | | +| 48 | 3 | 0,1,12 | | | | +| 49 | 3 | 0,1,12,13 | | | | +| 50 | 3 | 2,3,14 | | | | +| 51 | 3 | 2,3,14,15 | | | | +| 52 | 3 | 4,5,16 | | | | +| 53 | 3 | 4,5,16,17 | | | | +| 54-63 | Reserved | Reserved | | | | + +**Table 7.3.1.2.2-9A: Antenna port(s) (1000 + DMRS port), *dmrs-Type=2*, *enhanced-dmrs-Type* is configured, *maxLength=1*** + +| One codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | Two codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | +|-------------------------------------------------------------|------------------------------------------|--------------|-------------------------------------------------------------|------------------------------------------|---------------| +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Value | Number of DMRS CDM group(s) without data | DMRS port(s) | +| 0 | 1 | 0 | 0 | 3 | 0-4 | +| 1 | 1 | 1 | 1 | 3 | 0-5 | +| 2 | 1 | 0,1 | 2 | 2 | 0,1,2,3,12 | +| 3 | 2 | 0 | 3 | 2 | 0,1,2,3,12,14 | +| 4 | 2 | 1 | 4 | 2 | 0-3,12-14 | +| 5 | 2 | 2 | 5 | 2 | 0-3,12-15 | +| 6 | 2 | 3 | 6 | 3 | 0,1,2,3,12 | +| 7 | 2 | 0,1 | 7 | 3 | 0,1,2,3,12,14 | +| 8 | 2 | 2,3 | 8 | 3 | 0-3,12-14 | +| 9 | 2 | 0-2 | 9 | 3 | 0-3,12-15 | +| 10 | 2 | 0-3 | 10~63 | Reserved | Reserved | +| 11 | 3 | 0 | | | | +| 12 | 3 | 1 | | | | +| 13 | 3 | 2 | | | | +| 14 | 3 | 3 | | | | +| 15 | 3 | 4 | | | | +| 16 | 3 | 5 | | | | +| 17 | 3 | 0,1 | | | | +| 18 | 3 | 2,3 | | | | +| 19 | 3 | 4,5 | | | | +| 20 | 3 | 0-2 | | | | +| 21 | 3 | 3-5 | | | | +| 22 | 3 | 0-3 | | | | +| 23 | 2 | 0,2 | | | | +| 24 | 1 | 12 | | | | +| 25 | 1 | 13 | | | | +| 26 | 1 | 12,13 | | | | +| 27 | 2 | 12 | | | | +| 28 | 2 | 13 | | | | +| 29 | 2 | 14 | | | | +| 30 | 2 | 15 | | | | +| 31 | 2 | 12,13 | | | | +| 32 | 2 | 14,15 | | | | +| 33 | 3 | 12 | | | | +| 34 | 3 | 13 | | | | +| 35 | 3 | 14 | | | | +| 36 | 3 | 15 | | | | +| 37 | 3 | 16 | | | | +| 38 | 3 | 17 | | | | +| 39 | 3 | 12,13 | | | | +| 40 | 3 | 14,15 | | | | +| 41 | 3 | 16,17 | | | | +| 42 | 1 | 0,1,12 | | | | +| 43 | 1 | 0,1,12,13 | | | | +| 44 | 2 | 0,1,12 | | | | +| 45 | 2 | 0,1,12,13 | | | | +| 46 | 2 | 2,3,14 | | | | +| 47 | 2 | 2,3,14,15 | | | | +| 48 | 3 | 0,1,12 | | | | +| 49 | 3 | 0,1,12,13 | | | | +| 50 | 3 | 2,3,14 | | | | +| 51 | 3 | 2,3,14,15 | | | | +| 52 | 3 | 4,5,16 | | | | +| 53 | 3 | 4,5,16,17 | | | | +| 54 | 2 | 0,2,3 | | | | +| 55-63 | Reserved | Reserved | | | | + +**Table 7.3.1.2.2-10: Antenna port(s) (1000 + DMRS port), *dmrs-Type=2*, +*enhanced-dmrs-Type* is configured, *maxLength=2*** + +| One codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | | +|-------------------------------------------------------------|---------------------------------------------------|-----------------|------------------------------------|-------------------------------------------------------------|---------------------------------------------------|---------------------|----------------------------------------| +| Value | Number of
DMRS CDM
group(s)
without data | DMRS
port(s) | Number of
front-load
symbols | Value | Number of
DMRS CDM
group(s) without
data | DMRS port(s) | Number of
front-
load
symbols | +| 0 | 1 | 0 | 1 | 0 | 3 | 0-4 | 1 | +| 1 | 1 | 1 | 1 | 1 | 3 | 0-5 | 1 | +| 2 | 1 | 0,1 | 1 | 2 | 2 | 0,1,2,3,12 | 1 | +| 3 | 2 | 0 | 1 | 3 | 2 | 0-3,12,14 | 1 | +| 4 | 2 | 1 | 1 | 4 | 2 | 0-3,12-14 | 1 | +| 5 | 2 | 2 | 1 | 5 | 2 | 0-3,12-15 | 1 | +| 6 | 2 | 3 | 1 | 6 | 3 | 0,1,2,3,12 | 1 | +| 7 | 2 | 0,1 | 1 | 7 | 3 | 0-3,12,14 | 1 | +| 8 | 2 | 2,3 | 1 | 8 | 3 | 0-3,12-14 | 1 | +| 9 | 2 | 0-2 | 1 | 9 | 3 | 0-3,12-15 | 1 | +| 10 | 2 | 0-3 | 1 | 10 | 2 | 0,1,2,3,6 | 2 | +| 11 | 3 | 0 | 1 | 11 | 2 | 0,1,2,3,6,8 | 2 | +| 12 | 3 | 1 | 1 | 12 | 2 | 0,1,2,3,6,7,8 | 2 | +| 13 | 3 | 2 | 1 | 13 | 2 | 0,1,2,3,6,7,8,9 | 2 | +| 14 | 3 | 3 | 1 | 14 | 1 | 0,1,6,7,12 | 2 | +| 15 | 3 | 4 | 1 | 15 | 1 | 0,1,6,7,12,18 | 2 | +| 16 | 3 | 5 | 1 | 16 | 1 | 0,1,6,7,12,13,18 | 2 | +| 17 | 3 | 0,1 | 1 | 17 | 1 | 0,1,6,7,12,13,18,19 | 2 | +| 18 | 3 | 2,3 | 1 | 18 | 2 | 0,1,6,7,12 | 2 | +| 19 | 3 | 4,5 | 1 | 19 | 2 | 0,1,6,7,12,18 | 2 | +| 20 | 3 | 0-2 | 1 | 20 | 2 | 0,1,6,7,12,13,18 | 2 | +| 21 | 3 | 3-5 | 1 | 21 | 2 | 0,1,6,7,12,13,18,19 | 2 | +| 22 | 3 | 0-3 | 1 | 22 | 3 | 0,1,6,7,12 | 2 | +| 23 | 2 | 0,2 | 1 | 23 | 3 | 0,1,6,7,12,18 | 2 | +| 24 | 1 | 12 | 1 | 24 | 3 | 0,1,6,7,12,13,18 | 2 | +| 25 | 1 | 13 | 1 | 25 | 3 | 0,1,6,7,12,13,18,19 | 2 | +| 26 | 1 | 12,13 | 1 | 26~255 | Reserved | Reserved | Reserved | +| 27 | 2 | 12 | 1 | | | | | +| 28 | 2 | 13 | 1 | | | | | +| 29 | 2 | 14 | 1 | | | | | +| 30 | 2 | 15 | 1 | | | | | +| 31 | 2 | 12,13 | 1 | | | | | +| 32 | 2 | 14,15 | 1 | | | | | +| 33 | 3 | 12 | 1 | | | | | +| 34 | 3 | 13 | 1 | | | | | +| 35 | 3 | 14 | 1 | | | | | +| 36 | 3 | 15 | 1 | | | | | +| 37 | 3 | 16 | 1 | | | | | +| 38 | 3 | 17 | 1 | | | | | +| 39 | 3 | 12,13 | 1 | | | | | +| 40 | 3 | 14,15 | 1 | | | | | +| 41 | 3 | 16,17 | 1 | | | | | +| 42 | 1 | 0,1,12 | 1 | | | | | +| 43 | 1 | 0,1,12,13 | 1 | | | | | +| 44 | 2 | 0,1,12 | 1 | | | | | +| 45 | 2 | 0,1,12,13 | 1 | | | | | +| 46 | 2 | 2,3,14 | 1 | | | | | +| 47 | 2 | 2,3,14,15 | 1 | | | | | +| 48 | 3 | 0,1,12 | 1 | | | | | +| 49 | 3 | 0,1,12,13 | 1 | | | | | +| 50 | 3 | 2,3,14 | 1 | | | | | +| 51 | 3 | 2,3,14,15 | 1 | | | | | +| 52 | 3 | 4,5,16 | 1 | | | | | +| 53 | 3 | 4,5,16,17 | 1 | | | | | +| 54 | 3 | 0 | 2 | | | | | +| 55 | 3 | 1 | 2 | | | | | + +| One codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | | +|----------------------------------------------------------------------|-------------------------------------------------------------|-------------------------|---------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------|---------------------|--------------------------------------------------| +| Value | Number of
DMRS CDM
group(s)
without data | DMRS
port(s) | Number of
front-load
symbols | Value | Number of
DMRS CDM
group(s) without
data | DMRS port(s) | Number
of front-
load
symbols | +| 56 | 3 | 2 | 2 | | | | | +| 57 | 3 | 3 | 2 | | | | | +| 58 | 3 | 4 | 2 | | | | | +| 59 | 3 | 5 | 2 | | | | | +| 60 | 3 | 6 | 2 | | | | | +| 61 | 3 | 7 | 2 | | | | | +| 62 | 3 | 8 | 2 | | | | | +| 63 | 3 | 9 | 2 | | | | | +| 64 | 3 | 10 | 2 | | | | | +| 65 | 3 | 11 | 2 | | | | | +| 66 | 3 | 0,1 | 2 | | | | | +| 67 | 3 | 2,3 | 2 | | | | | +| 68 | 3 | 4,5 | 2 | | | | | +| 69 | 3 | 6,7 | 2 | | | | | +| 70 | 3 | 8,9 | 2 | | | | | +| 71 | 3 | 10,11 | 2 | | | | | +| 72 | 3 | 0,1,6 | 2 | | | | | +| 73 | 3 | 2,3,8 | 2 | | | | | +| 74 | 3 | 4,5,10 | 2 | | | | | +| 75 | 3 | 0,1,6,7 | 2 | | | | | +| 76 | 3 | 2,3,8,9 | 2 | | | | | +| 77 | 3 | 4,5,10,11 | 2 | | | | | +| 78 | 1 | 0 | 2 | | | | | +| 79 | 1 | 1 | 2 | | | | | +| 80 | 1 | 6 | 2 | | | | | +| 81 | 1 | 7 | 2 | | | | | +| 82 | 1 | 0,1 | 2 | | | | | +| 83 | 1 | 6,7 | 2 | | | | | +| 84 | 2 | 0,1 | 2 | | | | | +| 85 | 2 | 2,3 | 2 | | | | | +| 86 | 2 | 6,7 | 2 | | | | | +| 87 | 2 | 8,9 | 2 | | | | | +| 88 | 3 | 12 | 2 | | | | | +| 89 | 3 | 13 | 2 | | | | | +| 90 | 3 | 14 | 2 | | | | | +| 91 | 3 | 15 | 2 | | | | | +| 92 | 3 | 16 | 2 | | | | | +| 93 | 3 | 17 | 2 | | | | | +| 94 | 3 | 18 | 2 | | | | | +| 95 | 3 | 19 | 2 | | | | | +| 96 | 3 | 20 | 2 | | | | | +| 97 | 3 | 21 | 2 | | | | | +| 98 | 3 | 22 | 2 | | | | | +| 99 | 3 | 23 | 2 | | | | | +| 100 | 3 | 12,13 | 2 | | | | | +| 101 | 3 | 14,15 | 2 | | | | | +| 102 | 3 | 16,17 | 2 | | | | | +| 103 | 3 | 18,19 | 2 | | | | | +| 104 | 3 | 20,21 | 2 | | | | | +| 105 | 3 | 22,23 | 2 | | | | | +| 106 | 1 | 12 | 2 | | | | | +| 107 | 1 | 13 | 2 | | | | | +| 108 | 1 | 18 | 2 | | | | | +| 109 | 1 | 19 | 2 | | | | | +| 110 | 1 | 12,13 | 2 | | | | | +| 111 | 1 | 18,19 | 2 | | | | | +| 112 | 2 | 12,13 | 2 | | | | | +| 113 | 2 | 14,15 | 2 | | | | | +| 114 | 2 | 18,19 | 2 | | | | | + +| One codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | | +|-------------------------------------------------------------|------------------------------------------|--------------|------------------------------|-------------------------------------------------------------|------------------------------------------|--------------|------------------------------| +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +| 115 | 2 | 20,21 | 2 | | | | | +| 116 | 2 | 0,1,12 | 2 | | | | | +| 117 | 2 | 0,1,12,13 | 2 | | | | | +| 118 | 2 | 6,7,18 | 2 | | | | | +| 119 | 2 | 6,7,18,19 | 2 | | | | | +| 120 | 2 | 2,3,14 | 2 | | | | | +| 121 | 2 | 2,3,14,15 | 2 | | | | | +| 122 | 2 | 8,9,20 | 2 | | | | | +| 123 | 2 | 8,9,20,21 | 2 | | | | | +| 124 | 3 | 0,1,12 | 2 | | | | | +| 125 | 3 | 0,1,12,13 | 2 | | | | | +| 126 | 3 | 6,7,18 | 2 | | | | | +| 127 | 3 | 6,7,18,19 | 2 | | | | | +| 128 | 3 | 2,3,14 | 2 | | | | | +| 129 | 3 | 2,3,14,15 | 2 | | | | | +| 130 | 3 | 8,9,20 | 2 | | | | | +| 131 | 3 | 8,9,20,21 | 2 | | | | | +| 132 | 3 | 4,5,16 | 2 | | | | | +| 133 | 3 | 4,5,16,17 | 2 | | | | | +| 134 | 3 | 10,11,22 | 2 | | | | | +| 135 | 3 | 10,11,22,23 | 2 | | | | | +| 136-255 | Reserved | Reserved | Reserved | | | | | + +Table 7.3.1.2.2-10A: Antenna port(s) (1000 + DMRS port), *dmrs-Type=2*, *enhanced-dmrs-Type* is configured, *maxLength=2* + +| One codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | | +|-------------------------------------------------------------|------------------------------------------|--------------|------------------------------|-------------------------------------------------------------|------------------------------------------|---------------------|------------------------------| +| Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | Value | Number of DMRS CDM group(s) without data | DMRS port(s) | Number of front-load symbols | +| 0 | 1 | 0 | 1 | 0 | 3 | 0-4 | 1 | +| 1 | 1 | 1 | 1 | 1 | 3 | 0-5 | 1 | +| 2 | 1 | 0,1 | 1 | 2 | 2 | 0,1,2,3,12 | 1 | +| 3 | 2 | 0 | 1 | 3 | 2 | 0-3,12,14 | 1 | +| 4 | 2 | 1 | 1 | 4 | 2 | 0-3,12-14 | 1 | +| 5 | 2 | 2 | 1 | 5 | 2 | 0-3,12-15 | 1 | +| 6 | 2 | 3 | 1 | 6 | 3 | 0,1,2,3,12 | 1 | +| 7 | 2 | 0,1 | 1 | 7 | 3 | 0-3,12,14 | 1 | +| 8 | 2 | 2,3 | 1 | 8 | 3 | 0-3,12-14 | 1 | +| 9 | 2 | 0-2 | 1 | 9 | 3 | 0-3,12-15 | 1 | +| 10 | 2 | 0-3 | 1 | 10 | 2 | 0,1,2,3,6 | 2 | +| 11 | 3 | 0 | 1 | 11 | 2 | 0,1,2,3,6,8 | 2 | +| 12 | 3 | 1 | 1 | 12 | 2 | 0,1,2,3,6,7,8 | 2 | +| 13 | 3 | 2 | 1 | 13 | 2 | 0,1,2,3,6,7,8,9 | 2 | +| 14 | 3 | 3 | 1 | 14 | 1 | 0,1,6,7,12 | 2 | +| 15 | 3 | 4 | 1 | 15 | 1 | 0,1,6,7,12,18 | 2 | +| 16 | 3 | 5 | 1 | 16 | 1 | 0,1,6,7,12,13,18 | 2 | +| 17 | 3 | 0,1 | 1 | 17 | 1 | 0,1,6,7,12,13,18,19 | 2 | +| 18 | 3 | 2,3 | 1 | 18 | 2 | 0,1,6,7,12 | 2 | +| 19 | 3 | 4,5 | 1 | 19 | 2 | 0,1,6,7,12,18 | 2 | +| 20 | 3 | 0-2 | 1 | 20 | 2 | 0,1,6,7,12,13,18 | 2 | +| 21 | 3 | 3-5 | 1 | 21 | 2 | 0,1,6,7,12,13,18,19 | 2 | +| 22 | 3 | 0-3 | 1 | 22 | 3 | 0,1,6,7,12 | 2 | +| 23 | 2 | 0,2 | 1 | 23 | 3 | 0,1,6,7,12,18 | 2 | +| 24 | 1 | 12 | 1 | 24 | 3 | 0,1,6,7,12,13,18 | 2 | + +| One codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | | +|----------------------------------------------------------------------|-------------------------------------------------------------|-------------------------|---------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------|---------------------|--------------------------------------------------| +| Value | Number of
DMRS CDM
group(s)
without data | DMRS
port(s) | Number of
front-load
symbols | Value | Number of
DMRS CDM
group(s) without
data | DMRS port(s) | Number
of front-
load
symbols | +| 25 | 1 | 13 | 1 | 25 | 3 | 0,1,6,7,12,13,18,19 | 2 | +| 26 | 1 | 12,13 | 1 | 26~255 | Reserved | Reserved | Reserved | +| 27 | 2 | 12 | 1 | | | | | +| 28 | 2 | 13 | 1 | | | | | +| 29 | 2 | 14 | 1 | | | | | +| 30 | 2 | 15 | 1 | | | | | +| 31 | 2 | 12,13 | 1 | | | | | +| 32 | 2 | 14,15 | 1 | | | | | +| 33 | 3 | 12 | 1 | | | | | +| 34 | 3 | 13 | 1 | | | | | +| 35 | 3 | 14 | 1 | | | | | +| 36 | 3 | 15 | 1 | | | | | +| 37 | 3 | 16 | 1 | | | | | +| 38 | 3 | 17 | 1 | | | | | +| 39 | 3 | 12,13 | 1 | | | | | +| 40 | 3 | 14,15 | 1 | | | | | +| 41 | 3 | 16,17 | 1 | | | | | +| 42 | 1 | 0,1,12 | 1 | | | | | +| 43 | 1 | 0,1,12,13 | 1 | | | | | +| 44 | 2 | 0,1,12 | 1 | | | | | +| 45 | 2 | 0,1,12,13 | 1 | | | | | +| 46 | 2 | 2,3,14 | 1 | | | | | +| 47 | 2 | 2,3,14,15 | 1 | | | | | +| 48 | 3 | 0,1,12 | 1 | | | | | +| 49 | 3 | 0,1,12,13 | 1 | | | | | +| 50 | 3 | 2,3,14 | 1 | | | | | +| 51 | 3 | 2,3,14,15 | 1 | | | | | +| 52 | 3 | 4,5,16 | 1 | | | | | +| 53 | 3 | 4,5,16,17 | 1 | | | | | +| 54 | 3 | 0 | 2 | | | | | +| 55 | 3 | 1 | 2 | | | | | +| 56 | 3 | 2 | 2 | | | | | +| 57 | 3 | 3 | 2 | | | | | +| 58 | 3 | 4 | 2 | | | | | +| 59 | 3 | 5 | 2 | | | | | +| 60 | 3 | 6 | 2 | | | | | +| 61 | 3 | 7 | 2 | | | | | +| 62 | 3 | 8 | 2 | | | | | +| 63 | 3 | 9 | 2 | | | | | +| 64 | 3 | 10 | 2 | | | | | +| 65 | 3 | 11 | 2 | | | | | +| 66 | 3 | 0,1 | 2 | | | | | +| 67 | 3 | 2,3 | 2 | | | | | +| 68 | 3 | 4,5 | 2 | | | | | +| 69 | 3 | 6,7 | 2 | | | | | +| 70 | 3 | 8,9 | 2 | | | | | +| 71 | 3 | 10,11 | 2 | | | | | +| 72 | 3 | 0,1,6 | 2 | | | | | +| 73 | 3 | 2,3,8 | 2 | | | | | +| 74 | 3 | 4,5,10 | 2 | | | | | +| 75 | 3 | 0,1,6,7 | 2 | | | | | +| 76 | 3 | 2,3,8,9 | 2 | | | | | +| 77 | 3 | 4,5,10,11 | 2 | | | | | +| 78 | 1 | 0 | 2 | | | | | +| 79 | 1 | 1 | 2 | | | | | +| 80 | 1 | 6 | 2 | | | | | +| 81 | 1 | 7 | 2 | | | | | +| 82 | 1 | 0,1 | 2 | | | | | +| 83 | 1 | 6,7 | 2 | | | | | + +| One codeword:
Codeword 0 enabled,
Codeword 1 disabled | | | | Two Codewords:
Codeword 0 enabled,
Codeword 1 enabled | | | | +|----------------------------------------------------------------------|-------------------------------------------------------------|-------------------------|---------------------------------------------|----------------------------------------------------------------------|-------------------------------------------------------------|---------------------|--------------------------------------------------| +| Value | Number of
DMRS CDM
group(s)
without data | DMRS
port(s) | Number of
front-load
symbols | Value | Number of
DMRS CDM
group(s) without
data | DMRS port(s) | Number
of front-
load
symbols | +| 84 | 2 | 0,1 | 2 | | | | | +| 85 | 2 | 2,3 | 2 | | | | | +| 86 | 2 | 6,7 | 2 | | | | | +| 87 | 2 | 8,9 | 2 | | | | | +| 88 | 3 | 12 | 2 | | | | | +| 89 | 3 | 13 | 2 | | | | | +| 90 | 3 | 14 | 2 | | | | | +| 91 | 3 | 15 | 2 | | | | | +| 92 | 3 | 16 | 2 | | | | | +| 93 | 3 | 17 | 2 | | | | | +| 94 | 3 | 18 | 2 | | | | | +| 95 | 3 | 19 | 2 | | | | | +| 96 | 3 | 20 | 2 | | | | | +| 97 | 3 | 21 | 2 | | | | | +| 98 | 3 | 22 | 2 | | | | | +| 99 | 3 | 23 | 2 | | | | | +| 100 | 3 | 12,13 | 2 | | | | | +| 101 | 3 | 14,15 | 2 | | | | | +| 102 | 3 | 16,17 | 2 | | | | | +| 103 | 3 | 18,19 | 2 | | | | | +| 104 | 3 | 20,21 | 2 | | | | | +| 105 | 3 | 22,23 | 2 | | | | | +| 106 | 1 | 12 | 2 | | | | | +| 107 | 1 | 13 | 2 | | | | | +| 108 | 1 | 18 | 2 | | | | | +| 109 | 1 | 19 | 2 | | | | | +| 110 | 1 | 12,13 | 2 | | | | | +| 111 | 1 | 18,19 | 2 | | | | | +| 112 | 2 | 12,13 | 2 | | | | | +| 113 | 2 | 14,15 | 2 | | | | | +| 114 | 2 | 18,19 | 2 | | | | | +| 115 | 2 | 20,21 | 2 | | | | | +| 116 | 2 | 0,1,12 | 2 | | | | | +| 117 | 2 | 0,1,12,13 | 2 | | | | | +| 118 | 2 | 6,7,18 | 2 | | | | | +| 119 | 2 | 6,7,18,19 | 2 | | | | | +| 120 | 2 | 2,3,14 | 2 | | | | | +| 121 | 2 | 2,3,14,15 | 2 | | | | | +| 122 | 2 | 8,9,20 | 2 | | | | | +| 123 | 2 | 8,9,20,21 | 2 | | | | | +| 124 | 3 | 0,1,12 | 2 | | | | | +| 125 | 3 | 0,1,12,13 | 2 | | | | | +| 126 | 3 | 6,7,18 | 2 | | | | | +| 127 | 3 | 6,7,18,19 | 2 | | | | | +| 128 | 3 | 2,3,14 | 2 | | | | | +| 129 | 3 | 2,3,14,15 | 2 | | | | | +| 130 | 3 | 8,9,20 | 2 | | | | | +| 131 | 3 | 8,9,20,21 | 2 | | | | | +| 132 | 3 | 4,5,16 | 2 | | | | | +| 133 | 3 | 4,5,16,17 | 2 | | | | | +| 134 | 3 | 10,11,22 | 2 | | | | | +| 135 | 3 | 10,11,22,23 | 2 | | | | | +| 136 | 2 | 0,2,3 | 1 | | | | | +| 137-255 | Reserved | Reserved | Reserved | | | | | + +**Table 7.3.1.2.2-11: TCI selection** + +| Bit field mapped to index | TCI selection | +|---------------------------|---------------------------------------------------------------------------| +| 0 | The first indicated joint/DL TCI state is applied to the scheduled PDSCH | +| 1 | The second indicated joint/DL TCI state is applied to the scheduled PDSCH | +| 2 | Both indicated joint/DL TCI states are applied to the scheduled PDSCH | +| 3 | Reserved | + +**Table 7.3.1.2.2-12: Co-scheduled UE information** + +| Bit field mapped to index | Co-scheduled UE information | +|------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | In all the PRBs allocated to the UE, there is no co-scheduled UE or there is co-scheduled UE but with a different root DMRS sequence | +| 1 | In all the PRBs allocated to the UE, all the co-scheduled UE(s), if any, which have the same root DMRS sequence as the UE, are scheduled with modulation scheme QPSK | +| 2 | In all the PRBs allocated to the UE, all the co-scheduled UE(s), if any, which have the same root DMRS sequence as the UE, are scheduled with modulation scheme 16QAM | +| 3 | In all the PRBs allocated to the UE, all the co-scheduled UE(s), if any, which have the same root DMRS sequence as the UE, are scheduled with modulation scheme 64QAM | +| 4 | In all the PRBs allocated to the UE, all the co-scheduled UE(s), if any, which have the same root DMRS sequence as the UE, are scheduled with modulation scheme 256QAM | +| 5 | In all the PRBs allocated to the UE, all the co-scheduled UE(s), if any, which have the same root DMRS sequence as the UE, are scheduled with modulation scheme 1024QAM | +| 6 | In each individual PRB allocated to the UE, all the co-scheduled UE(s), which have the same root DMRS sequence as the UE, are scheduled with the same modulation scheme, except the cases corresponding to index 0~5 | +| 7 | All cases not covered above | +| Note: Root DMRS sequence is as defined in clause 7.4.1.1.1 of [4, TS 38.211] | | + +##### 7.3.1.2.3 Format 1\_2 + +DCI format 1\_2 is used for the scheduling of PDSCH in one cell. + +The following information is transmitted by means of the DCI format 1\_2 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI: + +- Identifier for DCI formats - 1 bits + - The value of this bit field is always set to 1, indicating a DL DCI format. +- Carrier indicator - 0, 1, 2 or 3 bits determined by higher layer parameter *carrierIndicatorSizeDCI-1-2*, as defined in Clause 10.1 of [5, TS38.213]. This field is reserved when this format is carried by PDCCH on the primary cell and the UE is configured for scheduling on the primary cell from an SCell, with the same number of bits as that in this format carried by PDCCH on the SCell for scheduling on the primary cell. +- Bandwidth part indicator - 0, 1 or 2 bits as determined by the number of DL BWPs configured by higher layers, excluding the initial DL bandwidth part. The bitwidth for this field is determined as bits, where + - if $\lceil \log_2(N_{BWP}^{DL}) \rceil = 1$ , in which case the bandwidth part indicator is equivalent to the ascending order of the higher layer parameter *BWP-Id*; + - otherwise, in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1; + If a UE does not support active BWP change via DCI, the UE ignores this bit field. +- Frequency domain resource assignment - number of bits determined by the following: + - $\lceil \log_2(N_{RB}^{DL} \cdot (N_{RB}^{DL} + 1) / 2) \rceil$ bits if only resource allocation type 0 is configured, where $N_{RB}^{DL}$ is defined in Clause 5.1.2.2.1 of [6, TS 38.214]; + - $\lceil \log_2(N_{RB}^{DL} \cdot (N_{RB}^{DL} + 1) / 2) \rceil$ bits if only resource allocation type 1 is configured, or $\lceil \log_2(N_{RB}^{DL} \cdot (N_{RB}^{DL} + 1) / 2) \rceil$ bits if *resourceAllocationDCI-1-2-r16* is configured as 'dynamicSwitch', where $N_{RB}^{DL}$ is the size of the active DL bandwidth part, is defined as in clause 4.4.4.4 of [4, TS 38.211] and is determined by higher layer parameter *resourceAllocationType1GranularityDCI-1-2*. If the higher layer parameter *resourceAllocationType1GranularityDCI-1-2* is not configured, $N_{RB}^{DL}$ is equal to 1. + - If *resourceAllocationDCI-1-2-r16* is configured as 'dynamicSwitch', the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit value of 1 indicates resource allocation type 1. + +- For resource allocation type 0, the LSBs provide the resource allocation as defined in Clause 5.1.2.2.1 of [6, TS 38.214]. +- For resource allocation type 1, the LSBs provide the resource allocation as defined in Clause 5.1.2.2.2 of [6, TS 38.214] + +If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if *resourceAllocationDCI-1-2-r16* is configured as '*dynamicSwitch*' for the indicated bandwidth part, the UE assumes resource allocation type 0 for the indicated bandwidth part if the bitwidth of the "Frequency domain resource assignment" field of the active bandwidth part is smaller than the bitwidth of the "Frequency domain resource assignment" field of the indicated bandwidth part. + +- Time domain resource assignment - 0, 1, 2, 3, or 4 bits as defined in Clause 5.1.2.1 of [6, TS 38.214]. The bitwidth for this field is determined as bits, where *I* is the number of entries in the higher layer parameter *pdsch-TimeDomainAllocationListDCI-1-2* if the higher layer parameter is configured, or *I* is the number of entries in the higher layer parameter *pdsch-TimeDomainAllocationList* if the higher layer parameter *pdsch-TimeDomainAllocationListDCI-1-2* is not configured; otherwise *I* is the number of entries in the default table. +- VRB-to-PRB mapping - 0 or 1 bit: + - 0 bit if the higher layer parameter *vrp-ToPRB-InterleaverDCI-1-2* is not configured; + - 1 bit according to Table 7.3.1.2.2-5 otherwise, only applicable to resource allocation type 1, as defined in Clause 7.3.1.6 of [4, TS 38.211]. +- PRB bundling size indicator - 0 bit if the higher layer parameter *prb-BundlingTypeDCI-1-2* is not configured or is set to 'static', or 1 bit if the higher layer parameter *prb-BundlingTypeDCI-1-2* is set to 'dynamic' according to Clause 5.1.2.3 of [6, TS 38.214]. +- Rate matching indicator - 0, 1, or 2 bits according to higher layer parameters *rateMatchPatternGroup1DCI-1-2* and *rateMatchPatternGroup2DCI-1-2*, where the MSB is used to indicate *rateMatchPatternGroup1DCI-1-2* and the LSB is used to indicate *rateMatchPatternGroup2DCI-1-2* when there are two groups. +- ZP CSI-RS trigger - 0, 1, or 2 bits as defined in Clause 5.1.4.2 of [6, TS 38.214]. The bitwidth for this field is determined as bits, where *N* is the number of aperiodic ZP CSI-RS resource sets configured by higher layer parameter *aperiodicZP-CSI-RS-ResourceSetsToAddModListDCI-1-2*. +- Modulation and coding scheme - 5 bits as defined in Clause 5.1.3.1 of [6, TS 38.214] +- New data indicator - 1 bit +- Redundancy version - 0, 1 or 2 bits determined by higher layer parameter *numberOfBitsForRV-DCI-1-2* + - If 0 bit is configured, *rvid* to be applied is 0; + - 1 bit according to Table 7.3.1.2.3-1; + - 2 bits according to Table 7.3.1.1.1-2. +- HARQ process number - number of bits determined by the following: + - 0, 1, 2, 3, 4 or 5 bits determined by higher layer parameter *harq-ProcessNumberSizeDCI-1-2-v1700* if configured; + - otherwise 0, 1, 2, 3 or 4 bits determined by higher layer parameter *harq-ProcessNumberSizeDCI-1-2* +- Downlink assignment index - 0, 1, 2 or 4 bits + - 0 bit if the higher layer parameter *downlinkAssignmentIndexDCI-1-2* is not configured; + - 1, 2 or 4 bits determined by higher layer parameter *downlinkAssignmentIndexDCI-1-2* otherwise, + - 4 bits if more than one serving cell are configured in the DL and the higher layer parameter *pdsch-HARQ-ACK-Codebook=dynamic*, where the 2 MSB bits are the counter DAI and the 2 LSB bits are the total DAI + - 4 bits if only one serving cell is configured in the DL and the higher layer parameter *pdsch-HARQ-ACK-Codebook=dynamic*, and the UE is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with value 0 for one or more first CORESETs and is provided *coresetPoolIndex* with value 1 for one or more second CORESETs, and is provided *ackNackFeedbackMode = joint*, where the 2 MSB bits are the counter DAI and the 2 LSB bits are the total DAI. + - 1 or 2 bits if only one serving cell is configured in the DL and the higher layer parameter *pdsch-HARQ-ACK-Codebook=dynamic*, when the UE is not configured with *coresetPoolIndex* or the value of *coresetPoolIndex* is the same for all CORESETs if *coresetPoolIndex* is provided or the UE is not configured with *ackNackFeedbackMode = joint*, where the 1 bit or 2 bits are the counter DAI. + +If the UE is configured with a PUCCH-SCell, the number of serving cells is determined within a PUCCH group. + +If the UE is configured with a PUCCH-SCell, *pdsch-HARQ-ACK-Codebook* is replaced by *pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup-r16* if present for the secondary PUCCH group. + +If higher layer parameter *priorityIndicatorDCI-1-2* is configured, if the bit width of the Downlink assignment index in DCI format 1\_2 for one HARQ-ACK codebook is not equal to that of the Downlink assignment index in DCI format 1\_2 for the other HARQ-ACK codebook, a number of most significant bits with value set to '0' are inserted to smaller Downlink assignment index until the bit width of the Downlink assignment index in DCI format 1\_2 for the two HARQ-ACK codebooks are the same. + +- TPC command for scheduled PUCCH - 2 bits as defined in Clause 7.2.1 of [5, TS 38.213] +- Second TPC command for scheduled PUCCH - 2 bits as defined in Clause 7.2.1 of [5, TS 38.213] if higher layer parameter *SecondTPCFieldDCI-1-2* is configured; 0 bit otherwise. +- PUCCH resource indicator - 0 or 1 or 2 or 3 bits determined by higher layer parameter *numberOfBitsForPUCCH-ResourceIndicatorDCI-1-2* + +If higher layer parameter *pucch-sCellPattern* or *pucch-sCellDynDCI-1-2* is configured, if the bit width of the PUCCH resource indicator in DCI format 1\_2 associated with one cell for PUCCH transmission is not equal to that of the PUCCH resource indicator in DCI format 1\_2 associated with the other cell for PUCCH transmission, a number of most significant bits with value set to '0' are inserted to smaller PUCCH resource indicator until the bit width of the PUCCH resource indicator in DCI format 1\_2 associated with the two cells for PUCCH transmissions are the same. + +If the UE is configured with a PUCCH-SCell, *pucch-sCellPattern* is replaced by *pucch-sCellPatternSecondaryPUCCHgroup* for the secondary PUCCH group. + +- PDSCH-to-HARQ\_feedback timing indicator - 0, 1, 2, or 3 bits as defined in Clause 9.2.3 of [5, TS 38.213]. The bitwidth for this field is determined as $\lceil \log_2 I \rceil$ bits, where $I$ is the number of entries in the higher layer parameter *DL-DataToUL-ACK-DCI-1-2*. + +If higher layer parameter *priorityIndicatorDCI-1-2* is configured, if the bit width of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 1\_2 for one HARQ-ACK codebook is not equal to that of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 1\_2 for the other HARQ-ACK codebook on the same cell for PUCCH transmission, a number of most significant bits with value set to '0' are inserted to smaller PDSCH-to-HARQ\_feedback timing indicator until the bit width of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 1\_2 for the two HARQ-ACK codebooks are the same. + +If higher layer parameter *pucch-sCellDynDCI-1-2* is configured, if the bit width of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 1\_2 associated with one cell for PUCCH transmission is not equal to that of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 1\_2 associated with the other cell for PUCCH transmission, a number of most significant bits with value set to '0' are inserted to smaller PDSCH-to-HARQ\_feedback timing indicator until the bit width of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 1\_2 associated with the two cells are the same. + +- One-shot HARQ-ACK request - 0 or 1 bit. + - 1 bit if higher layer parameter *pdsch-HARQ-ACK-OneShotFeedbackDCI-1-2* or *pdsch-HARQ-ACK-EnhType3DCI-1-2* is configured; + - 0 bit otherwise. +- Enhanced Type 3 codebook indicator - 0, 1, 2, or 3 bits. + - 0 bit if *pdsch-HARQ-ACK-EnhType3DCI-Field-1-2* is not configured; + - $\lceil \log_2 I \rceil$ bits otherwise, where $I$ is the number of entries in the higher layer parameter *pdsch-HARQ-ACK-EnhType3ToAddModList*. + +If the UE is configured with a PUCCH-SCell, *pdsch-HARQ-ACK-EnhType3ToAddModList* is replaced by *pdsch-HARQ-ACK-EnhType3SecondaryToAddModList* for the secondary PUCCH group. + +- HARQ-ACK retransmission indicator - 0 or 1 bit. + - 1 bit if higher layer parameter *pdsch-HARQ-ACK-retxDCI-1-2* is configured. + - 0 bit otherwise. +- Antenna port(s) - 0, 4, 5, 6, 7 or 8 bits + - 0 bit if higher layer parameter *antennaPortsFieldPresenceDCI-1-2* is not configured; + - Otherwise 4, 5, 6, 7 or 8 bits as defined by Tables 7.3.1.2.2-1/2/3/4/7/8/9/10 and Tables 7.3.1.2.2-1A/2A/3A/4A/7A/8A/9A/10A, where the number of CDM groups without data of values 1, 2, and 3 + +refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively. The antenna ports shall be determined according to the ordering of DMRS port(s) given by Tables 7.3.1.2.2-1/2/3/4/7/8/9/10 or Tables 7.3.1.2.2-1A/2A/3A/4A/7A/8A/9A/10A. When a UE not configured with *dl-OrJointTCI-StateList* receives an activation command that maps at least one codepoint of DCI field '*Transmission Configuration Indication*' to two TCI states, or when a UE configured with *dl-OrJointTCI-StateList* is having two indicated TCI states, the UE shall use Table 7.3.1.2.2-1A/2A/3A/4A/7A/8A/9A/10A; otherwise, it shall use Tables 7.3.1.2.2-1/2/3/4/7/8/9/10. + +- If a UE is configured with both *dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2* and *dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2* and is configured with higher layer parameter *antennaPortsFieldPresenceDCI-1-2*, the bitwidth of this field equals, where $\alpha$ is the "Antenna ports" bitwidth derived according to *dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2* and $\beta$ is the "Antenna ports" bitwidth derived according to *dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2*. A number of zeros are padded in the MSB of this field, if the mapping type of the PDSCH corresponds to the smaller value of $\alpha$ and $\beta$ . If a UE is not configured with higher layer parameter *antennaPortsFieldPresenceDCI-1-2*, antenna port(s) are defined assuming bit field index value 0 in Tables 7.3.1.2.2-1/2/3/4/7/8/9/10. +- Transmission configuration indication - 0 bit if higher layer parameter *tci-PresentDCI-1-2* is not configured; otherwise 1 or 2 or 3 bits determined by higher layer parameter *tci-PresentDCI-1-2* as defined in Clause 5.1.5 of [6, TS38.214]. + +If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part, + +- if the higher layer parameter *tci-PresentDCI-1-2* is not configured for the CORESET used for the PDCCH carrying the DCI format 1\_2, + - the UE assumes *tci-PresentDCI-1-2* is not configured for all CORESETs in the indicated bandwidth part; +- otherwise, + - the UE assumes *tci-PresentDCI-1-2* is configured for all CORESETs in the indicated bandwidth part with the same value configured for the CORESET used for the PDCCH carrying the DCI format 1\_2. +- TCI selection - 0 bit if higher layer parameter *tciSelection-PresentInDCI* is not configured; otherwise 2 bits according to Table 7.3.1.2.2-11. +- SRS request - 0, 1, 2 or 3 bits + - 0 bit if the higher layer parameter *srs-RequestDCI-1-2* is not configured; + - 1 bit as defined by Table 7.3.1.1.3-1 if the higher layer parameter *srs-RequestDCI-1-2* = 1 and for UEs not configured with *supplementaryUplink* in *ServingCellConfig* in the cell; + - 2 bits if the higher layer parameter *srs-RequestDCI-1-2* = 1 and for UEs configured with *supplementaryUplink* in *ServingCellConfig* in the cell, where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-1 and the second bit is defined by Table 7.3.1.1.3-1; + - 2 bits as defined by Table 7.3.1.1.2-24 if the higher layer parameter *srs-RequestDCI-1-2* = 2 and for UEs not configured with *supplementaryUplink* in *ServingCellConfig* in the cell; + - 3 bits if the higher layer parameter *srs-RequestDCI-1-2* = 2 and for UEs configured with *supplementaryUplink* in *ServingCellConfig* in the cell, where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-1 and the second and third bits are defined by Table 7.3.1.1.2-24; +- SRS offset indicator - 0, 1 or 2 bits. + - 0 bit if higher layer parameter *AvailableSlotOffset* is not configured for any aperiodic SRS resource set in the scheduled cell, or if higher layer parameter *AvailableSlotOffset* is configured for at least one aperiodic SRS resource set in the scheduled cell and the maximum number of entries of *availableSlotOffsetList* configured for all aperiodic SRS resource set(s) is 1; + - otherwise, bits are used to indicate available slot offset according to Table 7.3.1.1.2-37 and Clause 6.2.1 of [6, TS 38.214], where K is the maximum number of entries of *availableSlotOffsetList* configured for all aperiodic SRS resource set(s) in the scheduled cell; +- DMRS sequence initialization - 0 or 1 bit + - 0 bit if the higher layer parameter *dmrs-SequenceInitializationDCI-1-2* is not configured; + - 1 bit otherwise. +- Priority indicator - 0 bit if higher layer parameter *priorityIndicatorDCI-1-2* is not configured; otherwise 1 bit as defined in Clause 9 in [5, TS 38.213]. +- PDCCH monitoring adaptation indication - 0, 1 or 2 bits + - 1 or 2 bits, if *searchSpaceGroupIdList-r17* is not configured and if *pdch-SkippingDurationList* is configured + - 1 bit if the UE is configured with only one duration by *pdch-SkippingDurationList*; + +- 2 bits if the UE is configured with more than one duration by *pdcch-SkippingDurationList*. +- 1 or 2 bits, if *pdcch-SkippingDurationList* is not configured and if *searchSpaceGroupIdList-r17* is configured + - 1 bit if the UE is configured by *searchSpaceGroupIdList-r17* with search space set(s) with group index 0 and search space set(s) with group index 1, and if the UE is not configured by *searchSpaceGroupIdList-r17* with any search space set with group index 2; + - 2 bits if the UE is configured by *searchSpaceGroupIdList-r17* with search space set(s) with group index 0, search space set(s) with group index 1 and search space set(s) with group index 2; +- 2 bits, if *pdcch-SkippingDurationList* is configured and if *searchSpaceGroupIdList-r17* is configured +- 0 bit, otherwise +- ChannelAccess-CPext - 0, 1, 2, 3 or 4 bits. The bitwidth for this field is determined as *I* bits, where *I* is the number of entries in the higher layer parameter *ul-AccessConfigListDCI-1-2* or in Table 7.3.1.1.1-4A if *channelAccessMode-r16* = "semiStatic" is provided, for operation in a cell with shared spectrum channel access in frequency range 1, or the number of entries in the high layer parameter *ul-AccessConfigListDCI-1-1* for operation in frequency range 2-2 if *ChannelAccessMode2-r17* is provided; otherwise 0 bit. One or more entries from Table 7.3.1.2.2-6 are configured by the higher layer parameter *ul-AccessConfigListDCI-1-2* in frequency range 1. One or more entries from Table 7.3.1.1.2-6A are configured by the higher layer parameter *ul-AccessConfigListDCI-1-1* in frequency range 2-2. +- PUCCH Cell indicator - 0 or 1 bit. + - 1 bit if higher layer parameter *pucch-sSCellDynDCI-1-2* is configured. + - 0 bit otherwise. + +If DCI formats 1\_2 are monitored in multiple search spaces associated with multiple CORESETs in a BWP for scheduling the same serving cell, zeros shall be appended until the payload size of the DCI formats 1\_2 monitored in the multiple search spaces equal to the maximum payload size of the DCI format 1\_2 monitored in the multiple search spaces. + +For a UE configured with scheduling on the primary cell from an SCell, if prior to padding the number of information bits in DCI format 1\_2 carried by PDCCH on the primary cell is not equal to the number of information bits in DCI format 1\_2 carried by PDCCH on the SCell for scheduling on the primary cell, zeros shall be appended to the DCI format 1\_2 with smaller size until the payload size is the same. + +- If application of step 4B in clause 7.3.1.0 results in additional zero padding for DCI format 1\_2 for scheduling on the primary cell, corresponding zeros shall be appended to both DCI format 1\_2 monitored on the primary cell and DCI format 1\_2 monitored on the SCell for scheduling on the primary cell. +- If the SCell is deactivated and *firstActiveDownlinkBWP-Id* is not set to dormant BWP, the UE determines the number of information bits in DCI format 1\_2 carried by PDCCH on the primary cell based on a DL BWP provided by *firstActiveDownlinkBWP-Id* for the SCell. If the active DL BWP of the SCell is a dormant DL BWP, or if the SCell is deactivated and *firstActiveDownlinkBWP-Id* is set to dormant BWP, the UE determines the number of information bits in DCI format 1\_2 carried by PDCCH on the primary cell based on a DL BWP provided by *firstWithinActiveTimeBWP-Id* for the SCell if provided; otherwise, based on a DL BWP provided by *firstOutsideActiveTimeBWP-Id* for the SCell. + +**Table 7.3.1.2.3-1: Redundancy version** + +| Value of the Redundancy version field | Value of to be applied | +|---------------------------------------|------------------------| +| 0 | 0 | +| 1 | 3 | + +##### 7.3.1.2.4 Format 1\_3 + +DCI format 1\_3 is used for the scheduling of one PDSCH in one cell, or multiple PDSCHs in multiple cells with one PDSCH per cell. + +The following information is transmitted by means of the DCI format 1\_3 with CRC scrambled by C-RNTI or MCS-C-RNTI: + +- Identifier for DCI formats - 1 bits + - The value of this bit field is always set to 1, indicating a DL DCI format +- Scheduled cell set indicator - bits, where *I* is the number of cell sets which are configured by higher layer parameter *MC-DCI-SetofCellsToAddModList* to be respectively scheduled by DCI format 0\_3/1\_3 from the cell + +on which this format is carried by PDCCH. If present, this field is used to indicate the scheduled cell set according to Table 7.3.1.1.4-1; otherwise, the scheduled cell set is the cell set configured to be scheduled by DCI format 0\_3/1\_3 from the cell by higher layer parameter *MC-DCI-SetofCellsToAddModList*. + +- Scheduled cells indicator - number of bits determined by the following: + - 0 bit if the higher layer parameter *ScheduledCellCombo-ListDCI-1-3* for the scheduled cell set is not configured; + - otherwise bits indicating the scheduled cells in the scheduled cell set according to Table 7.3.1.2.4-1, where is the number of entries in the higher layer parameter *ScheduledCellCombo-ListDCI-1-3*. If only one entry is configured in the higher layer parameter *ScheduledCellCombo-ListDCI-1-3*, the scheduled cells are the cells configured by higher layer parameter *ScheduledCellCombo-ListDCI-1-3*. +- Bandwidth part indicator - 0, 1 or 2 bits determined as , where + - if , is the maximum number of DL BWPs configured by higher layers, excluding the initial DL bandwidth part, across all the cells configured by higher layer parameter *ScheduledCell-ListDCI-1-3* in the scheduled cell set, in which case the bandwidth part indicator is equivalent to the ascending order of the higher layer parameter *BWP-Id*; + - otherwise , in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1; + The field is only applicable to a scheduled cell with the number of configured DL BWPs larger than 1, including the initial DL bandwidth part, and is applied to the applicable scheduled cells in the scheduled cell set independently. If a UE does not support active BWP change via DCI, the UE ignores this bit field. If this field indicates a code point that does not correspond to a configured BWP of a scheduled cell, the UE ignores this bit field for the scheduled cell, and operates on the active BWP of the scheduled cell. +- Frequency domain resource assignment - number of bits determined by the following: + +- block number 1, block number 2, ..., block number + +If *ScheduledCellCombo-ListDCI-1-3* for the scheduled cell set is configured with more than one entry, is the number of scheduled cells indicated by Scheduled cells indicator field; if *ScheduledCellCombo-ListDCI-1-3* for the scheduled cell set is configured with only one entry, is the number of cells configured by higher layer parameter *ScheduledCellCombo-ListDCI-1-3*; otherwise, is the number of cells in the scheduled cell set configured by higher layer parameter *ScheduledCell-ListDCI-1-3*. Each block corresponds to the frequency domain resource assignment for a cell, and the blocks are placed according to an ascending order of a serving cell index, with block number 1 corresponding to the frequency domain resource assignment for the cell with the smallest serving cell index. Each block is defined by the following fields: + +- bits if only resource allocation type 0 is configured, where is defined in Clause 5.1.2.2.1 of [6, TS 38.214] +- bits if only resource allocation type 1 is configured, or bits if *resourceAllocationDCI-1-3* is configured as 'dynamicSwitch', where is the size of the active DL bandwidth part, is defined as in clause 4.4.4.4 of [4, TS 38.211] and is given by higher layer parameter *resourceAllocationType1GranularityDCI-1-3*. If the higher layer parameter *resourceAllocationType1GranularityDCI-1-3* is not configured, is equal to 1. +- If *resourceAllocationDCI-1-3* is configured as 'dynamicSwitch', the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit value of 1 indicates resource allocation type 1. +- For resource allocation type 0, the LSBs provide the resource allocation as defined in Clause 5.1.2.2.1 of [6, TS 38.214]. +- For resource allocation type 1, the LSBs provide the resource allocation as defined in Clause 5.1.2.2.2 of [6, TS 38.214]. + +If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if *resourceAllocationDCI-1-3* is configured as 'dynamicSwitch' for the indicated bandwidth part, the UE assumes resource allocation type 0 for the indicated bandwidth part if the bitwidth of the "Frequency domain resource assignment" field of the active bandwidth part is smaller than the bitwidth of the "Frequency domain resource assignment" field of the indicated bandwidth part. + +If the higher layer parameter *ScheduledCellCombo-ListDCI-1-3* for the scheduled cell set is not configured, each block is also used to indicate whether the corresponding cell is scheduled or not as follows: + +- if all bits of a block are set to 0 for resource allocation type 0 or set to 1 for resource allocation type 1 or set to 0 or 1 for dynamic switch resource allocation type, the cell corresponding to the block is not scheduled; + - otherwise, the cell corresponding to the block is scheduled. +- Time domain resource assignment - bits, where is the number of entries in the higher layer parameter *TDRA-FieldIndexListDCI-1-3*. This field is used to indicate an entry in the higher layer parameter *TDRA-* + +*FieldIndexListDCI-1-3* according to Table 7.3.1.2.4-2. Each entry in the higher layer parameter *TDRA-FieldIndexListDCI-1-3* contains the 'Time domain resource assignment' index for each BWP of each cell in the scheduled cell set, where the 'Time domain resource assignment' indexes for all the cells are placed according to an ascending order of a serving cell index, and the 'Time domain resource assignment' indexes for all the BWPs of a cell are placed according to an ascending order of the higher layer parameter *BWP-Id*. + +- VRB-to-PRB mapping - 0 or 1 bit + - 0 bit if the higher layer parameter *vrb-ToPRB-Interleaver* is not configured for any cell configured by higher layer parameter *ScheduledCell-ListDCI-1-3* in the scheduled cell set; + - 1 bit according to Table 7.3.1.2.2-5 otherwise, only applicable to resource allocation type 1, as defined in Clause 7.3.1.6 of [4, TS 38.211]. + +The field is only applicable to a scheduled cell configured with *vrb-ToPRB-Interleaver*, and is applied to the applicable scheduled cells independently. + +- PRB bundling size indicator - 0 or 1 bit + - 0 bit if the higher layer parameter *prb-BundlingType* is not configured or is set to 'staticBundling' for any cell configured by higher layer parameter *ScheduledCell-ListDCI-1-3* in the scheduled cell set; + - 1 bit according to Clause 5.1.2.3 of [6, TS 38.214] otherwise. +- The field is only applicable to a scheduled cell configured with *prb-BundlingType* set to 'dynamicBundling', and is applied to the applicable scheduled cells independently. + +- Rate matching indicator -bits, where *N* is the number of entries in the higher layer parameter *rateMatchListDCI-1-3*. This field is used to indicate an entry in the higher layer parameter *rateMatchListDCI-1-3* according to Table 7.3.1.2.4-3. Each entry in the higher layer parameter *rateMatchListDCI-1-3* contains the 'Rate matching indicator' index for each cell configured with *rateMatchPatternGroup1* or *rateMatchPatternGroup2* on at least one DL BWP in the scheduled cell set, where the 'Rate matching indicator' indexes for all the cells are placed according to an ascending order of a serving cell index. Each 'Rate matching indicator' index is defined by the following: + - 0, 1, or 2 bits according to higher layer parameters *rateMatchPatternGroup1* and *rateMatchPatternGroup2*, where the MSB is used to indicate *rateMatchPatternGroup1* and the LSB is used to indicate *rateMatchPatternGroup2* when there are two groups. +- ZP CSI-RS trigger -bits, where *N* is the number of entries in the higher layer parameter *zp-CSI-RSListDCI-1-3*. This field is used to indicate an entry in the higher layer parameter *zp-CSI-RSListDCI-1-3* according to Table 7.3.1.2.4-4. Each entry in the higher layer parameter *zp-CSI-RSListDCI-1-3* contains the 'ZP CSI-RS trigger' index for each cell configured with *aperiodicZP-CSI-RS-ResourceSetsToAddModList* on at least one DL BWP in the scheduled cell set, where the 'ZP CSI-RS trigger' indexes for all the cells are placed according to an ascending order of a serving cell index. Each 'ZP CSI-RS trigger' index is defined by the following: + - 0, 1, or 2 bits as defined in Clause 5.1.4.2 of [6, TS 38.214]. The bitwidth for this field is determined as *N* bits, where *N* is the number of aperiodic ZP CSI-RS resource sets configured by higher layer parameter *aperiodicZP-CSI-RS-ResourceSetsToAddModList*. + +For transport block 1: + +- Modulation and coding scheme - number of bits determined by the following: + - block number 1, block number 2, ..., block number *N* + +Each block corresponds to the modulation and coding scheme for a scheduled cell, and the blocks are placed according to an ascending order of a serving cell index, with block number 1 corresponding to the modulation and coding scheme for the cell with the smallest serving cell index. Each block is 5 bits as defined in Clause 6.1.4.1 of [6, TS 38.214]. +- New data indicator - number of bits determined by the following: + - block number 1, block number 2, ..., block number *N* + +Each block corresponds to the new data indicator for a scheduled cell, and the blocks are placed according to an ascending order of a serving cell index, with block number 1 corresponding to the new data indicator for the cell with the smallest serving cell index. Each block is 1 bit. +- Redundancy version - number of bits determined by the following: + - block number 1, block number 2, ..., block number *N* + +Each block corresponds to the redundancy version for a scheduled cell, and the blocks are placed according to an ascending order of a serving cell index, with block number 1 corresponding to the redundancy version + +for the cell with the smallest serving cell index. Each block is 0, 1 or 2 bits determined by higher layer parameter *numberOfBitsForRV-DCI-1-3* configured for the cell corresponding to the block, + +- If 0 bit is configured, *rvid* to be applied is 0; +- 1 bit according to Table 7.3.1.2.3-1; +- 2 bits according to Table 7.3.1.1.1-2. + +For transport block 2: + +- Modulation and coding scheme - number of bits determined by the following: + - block number 1, block number 2, ..., block number *N* + If *ScheduledCellCombo-ListDCI-1-3* for the scheduled cell set is configured, *N* is the number of scheduled cells indicated by Scheduled cells indicator field and configured with *maxNrofCodeWordsScheduledByDCI* = 2; otherwise, *N* is the number of cells configured by higher layer parameter *ScheduledCell-ListDCI-1-3* in the scheduled cell set and configured with *maxNrofCodeWordsScheduledByDCI* = 2. Each block corresponds to the modulation and coding scheme for a scheduled cell, and the blocks are placed according to an ascending order of a serving cell index, with block number 1 corresponding to the modulation and coding scheme for the cell with the smallest serving cell index. Each block is 5 bits as defined in Clause 6.1.4.1 of [6, TS 38.214]. + +- New data indicator - number of bits determined by the following: + - block number 1, block number 2, ..., block number *N* + Each block corresponds to the new data indicator for a scheduled cell, and the blocks are placed according to an ascending order of a serving cell index, with block number 1 corresponding to the new data indicator for the cell with the smallest serving cell index. Each block is 1 bit. + +- Redundancy version - number of bits determined by the following: + - block number 1, block number 2, ..., block number *N* + Each block corresponds to the redundancy version for a scheduled cell, and the blocks are placed according to an ascending order of a serving cell index, with block number 1 corresponding to the redundancy version for the cell with the smallest serving cell index. Each block is 0, 1 or 2 bits determined by higher layer parameter *numberOfBitsForRV-DCI-1-3* configured for the cell corresponding to the block, + - If 0 bit is configured, *rvid* to be applied is 0; + - 1 bit according to Table 7.3.1.2.3-1; + - 2 bits according to Table 7.3.1.1.1-2. + +If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and the value of *maxNrofCodeWordsScheduledByDCI* for the indicated bandwidth part equals 2 and the value of *maxNrofCodeWordsScheduledByDCI* for the active bandwidth part equals 1, the UE assumes zeros are padded when interpreting the "Modulation and coding scheme", "New data indicator", and "Redundancy version" fields of transport block 2 according to Clause 12 of [5, TS38.213], and the UE ignores the "Modulation and coding scheme", "New data indicator", and "Redundancy version" fields of transport block 2 for the indicated bandwidth part. + +- HARQ process number - number of bits determined by the following: + - block number 1, block number 2, ..., block number *N* + Each block corresponds to the HARQ process number for a scheduled cell, and the blocks are placed according to an ascending order of a serving cell index, with block number 1 corresponding to the HARQ process number for the cell with the smallest serving cell index. Each block is 0, 1, 2, 3, 4 or 5 bits determined by higher layer parameter *harq-ProcessNumberSizeDCI-1-3* configured for the cell corresponding to the block. + +- Downlink assignment index - number of bits as defined in the following + +- 4 bits if the higher layer parameter *pdsch-HARQ-ACK-Codebook=dynamic*, where the 2 MSB bits are the counter DAI and the 2 LSB bits are the total DAI; +- 0 bits otherwise. + +If the UE is configured with a PUCCH-SCell, *pdsch-HARQ-ACK-Codebook* is replaced by *pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup-r16* if present for the secondary PUCCH group. + +If higher layer parameter *priorityIndicatorDCI-1-3* is configured, if the bit width of the Downlink assignment index in DCI format 1\_3 for one HARQ-ACK codebook is not equal to that of the Downlink assignment index in DCI format 1\_3 for the other HARQ-ACK codebook, a number of most significant bits with value set to '0' are inserted to smaller Downlink assignment index until the bit width of the Downlink assignment index in DCI format 1\_3 for the two HARQ-ACK codebooks are the same. + +- TPC command for scheduled PUCCH - 2 bits as defined in Clause 7.2.1 of [5, TS 38.213] +- PUCCH resource indicator - 3 bits as defined in Clause 9.2.3 of [5, TS 38.213] +- PDSCH-to-HARQ\_feedback timing indicator - 0, 1, 2, or 3 bits as defined in Clause 9.2.3 of [5, TS 38.213]. The bitwidth for this field is determined as $\lceil \log_2 I \rceil$ bits, where $I$ is the number of entries in the higher layer parameter *dL-DataToUL-ACK*. + +If higher layer parameter *priorityIndicatorDCI-1-3* is configured, if the bit width of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 1\_3 for one HARQ-ACK codebook is not equal to that of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 1\_3 for the other HARQ-ACK codebook on the same cell for PUCCH transmission, a number of most significant bits with value set to '0' are inserted to smaller PDSCH-to-HARQ\_feedback timing indicator until the bit width of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 1\_3 for the two HARQ-ACK codebooks are the same. + +If higher layer parameter *pucch-sSCellDynDCI-1-3* is configured, if the bit width of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 1\_3 associated with one cell for PUCCH transmission is not equal to that of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 1\_3 associated with the other cell for PUCCH transmission, a number of most significant bits with value set to '0' are inserted to smaller PDSCH-to-HARQ\_feedback timing indicator until the bit width of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 1\_3 associated with the two cells are the same. + +- One-shot HARQ-ACK request - 0 or 1 bit. + - 1 bit if higher layer parameter *pdsch-HARQ-ACK-OneShotFeedbackDCI-1-3* or *pdsch-HARQ-ACK-enhType3DCI-1-3* is configured; + - 0 bit otherwise. +- Enhanced Type 3 codebook indicator - 0, 1, 2, or 3 bits. + - 0 bit if *pdsch-HARQ-ACK-enhType3DCIfieldDCI-1-3* is not configured; + - $\lceil \log_2 (N+1) \rceil$ bits otherwise, where $N$ is the number of entries in the higher layer parameter *pdsch-HARQ-ACK-EnhType3ToAddModList*. + +If the UE is configured with a PUCCH-SCell, *pdsch-HARQ-ACK-EnhType3ToAddModList* is replaced by *pdsch-HARQ-ACK-EnhType3SecondaryList* for the secondary PUCCH group. + +- HARQ-ACK retransmission indicator - 0 or 1 bit. + - 1 bit if higher layer parameter *pdsch-HARQ-ACK-retxDCI-1-3* is configured. + - 0 bit otherwise. +- Antenna ports - number of bits determined by the following: + - If *AntennaPortsDCI-1-3= type1a* is configured by higher layer, + - $\lceil \log_2 (N+1) \rceil$ bits applying to the scheduled cells independently, where $N$ is the number of cells configured by higher layer parameter *ScheduledCell-ListDCI-1-3* in the scheduled cell set, $N$ is mapped to the cells according to an ascending order of a serving cell index with $N$ corresponding to the cell with the smallest serving cell index, and $N$ is defined below. + - If *AntennaPortsDCI-1-3= type2* is configured by higher layer, + - $\lceil \log_2 (N+1) \rceil$ block number 1, block number 2, ..., block number $N$ + Each block corresponds to the Antenna ports information for a scheduled cell, and the blocks are placed according to an ascending order of a serving cell index, with block number 1 corresponding to the Antenna ports information for the cell with the smallest serving cell index. Each block is defined below. + +above for the case of *AntennaPortsDCI-1-3= type1a* or each block above for the case of *AntennaPortsDCI-1-3= type2* is defined by the following: + +- 4, 5, or 6 bits as defined by Tables 7.3.1.2.2-1/2/3/4 and Tables 7.3.1.2.2-1A/2A/3A/4A, where the number of CDM groups without data of values 1, 2, and 3 refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively. The antenna ports shall be determined according to the ordering of DMRS port(s) given by Tables 7.3.1.2.2-1/2/3/4 or Tables 7.3.1.2.2-1A/2A/3A/4A. + +If a UE is configured with both *dmrs-DownlinkForPDSCH-MappingTypeA* and *dmrs-DownlinkForPDSCH-MappingTypeB*, the bitwidth of this field equals $\max(\lceil \log_2 (N_A+1) \rceil, \lceil \log_2 (N_B+1) \rceil)$ , where $N_A$ is the "Antenna ports" bitwidth derived according to *dmrs-DownlinkForPDSCH-MappingTypeA* and $N_B$ is the "Antenna ports" bitwidth derived according to *dmrs-DownlinkForPDSCH-MappingTypeB*. A number of zeros are padded in the MSB of this field, if the mapping type of the PDSCH corresponds to the smaller value of $N_A$ and $N_B$ . + +- Transmission configuration indication - number of bits determined by the following: + - 0 bit if higher layer parameter *tci-PresentInDCI* is not enabled; + - otherwise bits, where $I$ is the number of entries in the higher layer parameter *tci-ListDCI-1-3*. This field is used to indicate an entry in the higher layer parameter *tci-ListDCI-1-3* according to Table 7.3.1.2.4-5. Each entry in the higher layer parameter *tci-ListDCI-1-3* contains the 'Transmission configuration indication' index for each cell in the scheduled cell set, where the 'Transmission configuration indication' indexes for all the cells are placed according to an ascending order of a serving cell index. Each 'Transmission configuration indication' index is 3 bits as defined in Clause 5.1.5 of [6, TS38.214]. +- If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part, +- if the higher layer parameter *tci-PresentInDCI* is not enabled for the CORESET used for the PDCCH carrying the DCI format 1\_3, + - the UE assumes *tci-PresentInDCI* is not enabled for all CORESETs in the indicated bandwidth part; + - otherwise, + - the UE assumes *tci-PresentInDCI* is enabled for all CORESETs in the indicated bandwidth part. +- SRS request -bits, where $I$ is the number of entries in the higher layer parameter *srs-RequestListDCI-1-3*. This field is used to indicate an entry in the higher layer parameter *srs-RequestListDCI-1-3* according to Table 7.3.1.2.4-6. Each entry in the higher layer parameter *srs-RequestListDCI-1-3* contains the 'SRS request' index for each cell in the scheduled cell set, where the 'SRS request' indexes for all the cells are placed according to an ascending order of a serving cell index. Each 'SRS request' index is defined by the following: + - 2 bits as defined by Table 7.3.1.1.2-24 for UEs not configured with *supplementaryUplink* in *ServingCellConfig* in the cell; 3 bits for UEs configured with *supplementaryUplink* in *ServingCellConfig* in the cell where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-1 and the second and third bits are defined by Table 7.3.1.1.2-24. This bit field may also indicate the associated CSI-RS according to Clause 6.1.1.2 of [6, TS 38.214]. + - SRS offset indicator -bits, where $I$ is the number of entries in the higher layer parameter *srs-OffsetListDCI-1-3*. This field is used to indicate an entry in the higher layer parameter *srs-OffsetListDCI-1-3* according to Table 7.3.1.2.4-7. Each entry in the higher layer parameter *srs-OffsetListDCI-1-3* contains the 'SRS offset indicator' index for each cell in the scheduled cell set, where the 'SRS offset indicator' indexes for all the cells are placed according to an ascending order of a serving cell index. Each 'SRS offset indicator' index is defined by the following: + - 0 bit if higher layer parameter *AvailableSlotOffset* is not configured for any aperiodic SRS resource set in the scheduled cell, or if higher layer parameter *AvailableSlotOffset* is configured for at least one aperiodic SRS resource set in the scheduled cell and the maximum number of entries of *availableSlotOffsetList* configured for all aperiodic SRS resource set(s) is 1; + - otherwise, bits are used to indicate available slot offset according to Table 7.3.1.1.2-37 and Clause 6.2.1 of [6, TS 38.214], where $K$ is the maximum number of entries of *availableSlotOffsetList* configured for all aperiodic SRS resource set(s) in the scheduled cell; + - DMRS sequence initialization - 1 bit. This field is applied to all the scheduled cells indicated by Scheduled cells indicator field or Frequency domain resource assignment field independently. + - Priority indicator - 0 bit if higher layer parameter *priorityIndicatorDCI-1-3* is not configured; otherwise 1 bit as defined in Clause 9 in [5, TS 38.213]. + - ChannelAccess-CPext - 0, 1, 2, 3 or 4 bits. The bitwidth for this field is determined as $I$ bits, where $I$ is the number of entries in the higher layer parameter *ul-AccessConfigListDCI-1-1* or in Table 7.3.1.1.1-4A if *channelAccessMode-r16* = "semiStatic" is provided, for operation in a cell with shared spectrum channel access in frequency range 1, or for operation in frequency range 2-2 if *ChannelAccessMode2-r17* is provided; otherwise 0 bit. One or more entries from Table 7.3.1.2.2-6 or Table 7.3.1.2.2-6A are configured by the higher layer parameter *ul-AccessConfigListDCI-1-1*. + - Minimum applicable scheduling offset indicator - 0 or 1 bit + - 0 bit if higher layer parameter *minimumSchedulingOffsetK0DCI-1-3* is not configured; + - 1 bit otherwise. The 1 bit indication is used to determine the minimum applicable $K_0$ for the active DL BWP and the minimum applicable $K_2$ for the active UL BWP, if configured respectively, according to Table 7.3.1.1.2-33. If the minimum applicable $K_0$ is indicated, the minimum applicable value of the aperiodic CSI-RS triggering offset for an active DL BWP for each scheduled cell shall be the same as the minimum applicable $K_0$ . + - SCell dormancy indication - 0 bit if higher layer parameter *dormancyDCI-1-3* or *dormancyGroupWithinActiveTime* is not configured; otherwise 1, 2, 3, 4, or 5 bits bitmap determined according + +to the number of different *DormancyGroupID(s)* provided by higher layer parameter *dormancyGroupWithinActiveTime*, where each bit corresponds to one of the SCell group(s) configured by higher layers parameter *dormancyGroupWithinActiveTime*, with MSB to LSB of the bitmap corresponding to the first to the last configured SCell group in ascending order of *DormancyGroupID*. The field is only present when this format is carried by PDCCH on the primary cell within DRX Active Time and the UE is configured with at least two DL BWPs for an SCell. + +If the “One-shot HARQ-ACK request” field is not present or set to '0', and if the “HARQ-ACK retransmission indicator” field is not present or set to '0', and if all bits of the corresponding block(s) of the frequency domain resource assignment field are set to 0 for resource allocation type 0 or set to 1 for resource allocation type 1 or set to 0 or 1 for dynamic switch resource allocation type for one or more cells in the scheduled cell set, this field is reserved and the following fields, corresponding to the cell with smallest serving cell index among the one or more cell(s), among the fields above are used for SCell dormancy indication, where each bit corresponds to one of the configured SCell(s), with MSB to LSB of the following fields concatenated in the order below corresponding to the SCell with lowest to highest SCell index + +- Modulation and coding scheme of transport block 1 +- New data indicator of transport block 1 +- Redundancy version of transport block 1 +- HARQ process number +- Antenna port(s) if *AntennaPortsDCI-3= type2* is configured by higher layer. +- PDCCH monitoring adaptation indication - 0, 1 or 2 bits + - 0 bit if higher layer parameter *pdccMonAdaptDCI-1-3* is not enabled; + - otherwise, + - 1 or 2 bits, if *searchSpaceGroupIdList-r17* is not configured and if *pdcc-SkippingDurationList* is configured + - 1 bit if the UE is configured with only one duration by *pdcc-SkippingDurationList*; + - 2 bits if the UE is configured with more than one duration by *pdcc-SkippingDurationList*. + - 1 or 2 bits, if *pdcc-SkippingDurationList* is not configured and if *searchSpaceGroupIdList-r17* is configured + - 1 bit if the UE is configured by *searchSpaceGroupIdList-r17* with search space set(s) with group index 0 and search space set(s) with group index 1, and if the UE is not configured by *searchSpaceGroupIdList-r17* with any search space set with group index 2; + - 2 bits if the UE is configured by *searchSpaceGroupIdList-r17* with search space set(s) with group index 0, search space set(s) with group index 1 and search space set(s) with group index 2; + - 2 bits, if *pdcc-SkippingDurationList* is configured and if *searchSpaceGroupIdList-r17* is configured +- PUCCH Cell indicator - 0 or 1 bit. + - 1 bit if higher layer parameter *pucch-sCellDynDCI-1-3* is configured. + - 0 bit otherwise. + +If *ScheduledCellCombo-ListDCI-1-3* for the cell set is configured, zeros shall be appended to DCI format 1\_3 if needed until the payload size equals the size of DCI format 1\_3 that is determined by the configuration of the corresponding active bandwidth part(s) of the scheduled cells in the entry which results in the largest size among the entries in the higher layer parameter *ScheduledCellCombo-ListDCI-1-3*. + +If an SCell within the scheduled cell set is deactivated and the *firstActiveDownlinkBWP-Id* corresponding to the SCell is not set to dormant BWP, the UE determines the bitwidth of the fields in DCI format 1\_3 based on a DL BWP provided by *firstActiveDownlinkBWP-Id* for the SCell. If the active DL BWP of an SCell within the scheduled cell set is a dormant DL BWP, or if an SCell within the scheduled cell set is deactivated and the *firstActiveDownlinkBWP-Id* corresponding to the SCell is set to dormant BWP, the UE determines the bitwidth of the fields in DCI format 1\_3 based on a DL BWP provided by *firstWithinActiveTimeBWP-Id* for the SCell if provided; otherwise, based on a DL BWP provided by *firstOutsideActiveTimeBWP-Id* for the SCell. + +**Table 7.3.1.2.4-1: Scheduled cells indicator in DCI format 1\_3** + +| Bit field mapped to index | Scheduled cells | +|---------------------------|------------------------------------------------------------------------------------------------------| +| 0 | The cells configured by the 1 st entry in ScheduledCellCombo-ListDCI-1-3 | +| 1 | The cells configured by the 2 nd entry in ScheduledCellCombo-ListDCI-1-3 | +| 2 | The cells configured by the 3 rd entry in ScheduledCellCombo-ListDCI-1-3 , if any | +| 3 | The cells configured by the 4 th entry in ScheduledCellCombo-ListDCI-1-3 , if any | +| 4 | The cells configured by the 5 th entry in ScheduledCellCombo-ListDCI-1-3 , if any | +| 5 | The cells configured by the 6 th entry in ScheduledCellCombo-ListDCI-1-3 , if any | +| 6 | The cells configured by the 7 th entry in ScheduledCellCombo-ListDCI-1-3 , if any | +| 7 | The cells configured by the 8 th entry in ScheduledCellCombo-ListDCI-1-3 , if any | +| 8 | The cells configured by the 9 th entry in ScheduledCellCombo-ListDCI-1-3 , if any | +| 9 | The cells configured by the 10 th entry in ScheduledCellCombo-ListDCI-1-3 , if any | +| 10 | The cells configured by the 11 th entry in ScheduledCellCombo-ListDCI-1-3 , if any | +| 11 | The cells configured by the 12 th entry in ScheduledCellCombo-ListDCI-1-3 if any | +| 12 | The cells configured by the 13 th entry in ScheduledCellCombo-ListDCI-1-3 , if any | +| 13 | The cells configured by the 14 th entry in ScheduledCellCombo-ListDCI-1-3 , if any | +| 14 | The cells configured by the 15 th entry in ScheduledCellCombo-ListDCI-1-3 , if any | +| 15 | The cells configured by the 16 th entry in ScheduledCellCombo-ListDCI-1-3 , if any | + +**Table 7.3.1.2.4-2: Time domain resource assignment in DCI format 1\_3** + +| Bit field mapped to index | Indicated time domain resource allocation | +|---------------------------|-------------------------------------------------------------------------| +| 0 | The 1 st entry in TDRA-FieldIndexListDCI-1-3 | +| 1 | The 2 nd entry in TDRA-FieldIndexListDCI-1-3 | +| 2 | The 3 rd entry in TDRA-FieldIndexListDCI-1-3 , if any | +| ... | ... | +| | The entry in TDRA-FieldIndexListDCI-1-3 , if any | +| ... | ... | + +**Table 7.3.1.2.4-3: Rate matching indicator** + +| Bit field mapped to index | Indicated rate matching pattern | +|---------------------------|--------------------------------------------------------------------| +| 0 | The 1 st entry in rateMatchListDCI-1-3 | +| 1 | The 2 nd entry in rateMatchListDCI-1-3 | +| 2 | The 3 rd entry in rateMatchListDCI-1-3 , if any | +| ... | ... | +| 15 | The 16 th entry in rateMatchListDCI-1-3 , if any | + +**Table 7.3.1.2.4-4: ZP CSI-RS trigger** + +| Bit field mapped to index | Triggered aperiodic ZP CSI-RS | +|---------------------------|-------------------------------------------------------------------| +| 0 | The 1 st entry in zp-CSI-RSListDCI-1-3 | +| 1 | The 2 nd entry in zp-CSI-RSListDCI-1-3 | +| 2 | The 3 rd entry in zp-CSI-RSListDCI-1-3 , if any | +| ... | ... | +| 7 | The 8 th entry in zp-CSI-RSListDCI-1-3 , if any | + +**Table 7.3.1.2.4-5: Transmission configuration indication** + +| Bit field mapped to index | Indicated transmission configuration indication | +|---------------------------|---------------------------------------------------------------| +| 0 | The 1 st entry in tci-ListDCI-1-3 | +| 1 | The 2 nd entry in tci-ListDCI-1-3 | +| 2 | The 3 rd entry in tci-ListDCI-1-3 , if any | +| ... | ... | +| 15 | The 16 th entry in tci-ListDCI-1-3 , if any | + +**Table 7.3.1.1.4-6: SRS request in DCI format 1\_3** + +| Bit field mapped to index | Triggered aperiodic SRS resource set(s) | +|---------------------------|----------------------------------------------------------------------| +| 0 | The 1 st entry in srs-RequestListDCI-1-3 | +| 1 | The 2 nd entry in srs-RequestListDCI-1-3 | +| 2 | The 3 rd entry in srs-RequestListDCI-1-3 , if any | +| ... | ... | +| 15 | The 16 th entry in srs-RequestListDCI-1-3 , if any | + +**Table 7.3.1.1.4-7: SRS offset indicator in DCI format 1\_3** + +| Bit field mapped to index | Available slot offset | +|---------------------------|--------------------------------------------------------------------| +| 0 | The 1 st entry in srs-OffsetListDCI-1-3 | +| 1 | The 2 nd entry in srs-OffsetListDCI-1-3 | +| 2 | The 3 rd entry in srs-OffsetListDCI-1-3 , if any | +| ... | ... | +| 7 | The 8 th entry in srs-OffsetListDCI-1-3 , if any | + +#### 7.3.1.3 DCI formats for other purposes + +##### 7.3.1.3.1 Format 2\_0 + +DCI format 2\_0 is used for notifying the slot format, COT duration, available RB set, and search space set group switching. + +The following information is transmitted by means of the DCI format 2\_0 with CRC scrambled by SFI-RNTI: + +- If the higher layer parameter *slotFormatCombToAddModList* is configured, + - Slot format indicator 1, Slot format indicator 2, ..., Slot format indicator *N*, +- If the higher layer parameter *availableRB-SetsToAddModList* is configured, + - Available RB set Indicator 1, Available RB set Indicator 2, ..., Available RB set Indicator *N1*, +- If the higher layer parameter *co-DurationsPerCellToAddModList* is configured + - COT duration indicator 1, COT duration indicator 2, ..., COT duration indicator *N2*. +- If the higher layer parameter *switchTriggerToAddModList* is configured + - Search space set group switching flag 1, Search space set group switching flag 2, ..., Search space set group switching flag *M*. + +The size of DCI format 2\_0 is configurable by higher layers up to 128 bits, according to Clause 11.1.1 of [5, TS 38.213]. + +##### 7.3.1.3.2 Format 2\_1 + +DCI format 2\_1 is used for notifying the PRB(s) and OFDM symbol(s) where UE may assume no transmission is intended for the UE. + +The following information is transmitted by means of the DCI format 2\_1 with CRC scrambled by INT-RNTI: + +- Pre-emption indication 1, Pre-emption indication 2, ..., Pre-emption indication *N*. + +The size of DCI format 2\_1 is configurable by higher layers up to 126 bits, according to Clause 11.2 of [5, TS 38.213]. Each pre-emption indication is 14 bits. + +##### 7.3.1.3.3 Format 2\_2 + +DCI format 2\_2 is used for the transmission of TPC commands for PUCCH and PUSCH. + +The following information is transmitted by means of the DCI format 2\_2 with CRC scrambled by TPC-PUSCH-RNTI or TPC-PUCCH-RNTI: + +- block number 1, block number 2, ..., block number *N* + +The parameter *tpc-PUSCH* or *tpc-PUCCH* provided by higher layers determines the index to the block number for an UL of a cell, with the following fields defined for each block: + +- Closed loop indicator - 0 or 1 bit. + - For DCI format 2\_2 with TPC-PUSCH-RNTI, 0 bit if the UE is not configured with high layer parameter *twoPUSCH-PC-AdjustmentStates*, in which case UE assumes each block in the DCI format 2\_2 is of 2 bits; 1 bit otherwise, in which case UE assumes each block in the DCI format 2\_2 is of 3 bits; + - For DCI format 2\_2 with TPC-PUCCH-RNTI, 0 bit if the UE is not configured with high layer parameter *twoPUCCH-PC-AdjustmentStates*, in which case UE assumes each block in the DCI format 2\_2 is of 2 bits; 1 bit otherwise, in which case UE assumes each block in the DCI format 2\_2 is of 3 bits; +- TPC command -2 bits + +The number of information bits in format 2\_2 shall be equal to or less than the payload size of format 1\_0 monitored in common search space in the same serving cell. If the number of information bits in format 2\_2 is less than the payload size of format 1\_0 monitored in common search space in the same serving cell, zeros shall be appended to format 2\_2 until the payload size equals that of format 1\_0 monitored in common search space in the same serving cell. + +##### 7.3.1.3.4 Format 2\_3 + +DCI format 2\_3 is used for the transmission of a group of TPC commands for SRS transmissions by one or more UEs. Along with a TPC command, a SRS request may also be transmitted. + +The following information is transmitted by means of the DCI format 2\_3 with CRC scrambled by TPC-SRS-RNTI: + +- block number 1, block number 2, ..., block number + +where the starting position of a block is determined by the parameter *startingBitOfFormat2-3* or *startingBitOfFormat2-3SUL-v1530* provided by higher layers for the UE configured with the block. + +If the UE is configured with higher layer parameter *srs-TPC-PDCCH-Group = typeA* for an UL without PUCCH and PUSCH or an UL on which the SRS power control is not tied with PUSCH power control, one block is configured for the UE by higher layers, with the following fields defined for the block: + +- SRS request - 0 or 2 bits. The presence of this field is according to the definition in Clause 11.4 of [5, TS38.213]. If present, this field is interpreted as defined by Table 7.3.1.1.2-24. +- TPC command number 1, TPC command number 2, ..., TPC command number *N*, where each TPC command applies to a respective UL carrier provided by higher layer parameter *cc-IndexInOneCC-Set* + +If the UE is configured with higher layer parameter *srs-TPC-PDCCH-Group = typeB* for an UL without PUCCH and PUSCH or an UL on which the SRS power control is not tied with PUSCH power control, one block or more blocks is configured for the UE by higher layers where each block applies to an UL carrier, with the following fields defined for each block: + +- SRS request - 0 or 2 bits. The presence of this field is according to the definition in Clause 11.4 of [5, TS38.213]. If present, this field is interpreted as defined by Table 7.3.1.1.2-24. +- TPC command -2 bits + +The number of information bits in format 2\_3 shall be equal to or less than the payload size of format 1\_0 monitored in common search space in the same serving cell. If the number of information bits in format 2\_3 is less than the payload size of format 1\_0 monitored in common search space in the same serving cell, zeros shall be appended to format 2\_3 until the payload size equals that of format 1\_0 monitored in common search space in the same serving cell. + +##### 7.3.1.3.5 Format 2\_4 + +DCI format 2\_4 is used for notifying the PRB(s) and OFDM symbol(s) where UE cancels the corresponding UL transmission from the UE according to Clause 11.2A of [5, TS 38.213]. + +The following information is transmitted by means of the DCI format 2\_4 with CRC scrambled by CI-RNTI: + +- Cancellation indication 1, Cancellation indication 2, ..., Cancellation indication *N*. + +The size of DCI format 2\_4 is configurable by higher layers parameter *dci-PayloadSizeForCI* up to 126 bits, according to Clause 11.2A of [5, TS 38.213]. The number of bits for each cancellation indication is configurable by higher layer parameter *ci-PayloadSize*. For a UE, there is at most one cancellation indication for an UL carrier. + +##### 7.3.1.3.6 Format 2\_5 + +DCI format 2\_5 is used for notifying the availability of soft resources as defined in Clause 9.3.1 of [10, TS 38.473] + +The following information is transmitted by means of the DCI format 2\_5 with CRC scrambled by AI-RNTI: + +- Availability indicator 1, Availability indicator 2, ..., Availability indicator *N*. + +The size of DCI format 2\_5 is configurable by higher layers up to 128 bits, according to Clause 14 of [5, TS 38.213]. + +##### 7.3.1.3.7 Format 2\_6 + +DCI format 2\_6 is used for notifying the power saving information outside DRX Active Time for one or more UEs. + +The following information is transmitted by means of the DCI format 2\_6 with CRC scrambled by PS-RNTI: + +- block number 1, block number 2, ..., block number *N* + +where the starting position of a block is determined by the parameter *ps-PositionDCI-2-6* provided by higher layers for the UE configured with the block. + +If the UE is configured with higher layer parameter *ps-RNTI* and *dci-Format2-6*, one block is configured for the UE by higher layers, with the following fields defined for the block: + +- Wake-up indication - 1 bit +- SCell dormancy indication - 0 bit if higher layer parameter *dormancyGroupOutsideActiveTime* is not configured; otherwise 1, 2, 3, 4 or 5 bits bitmap determined according to the number of different *DormancyGroupID(s)* provided by higher layer parameter *dormancyGroupOutsideActiveTime*, where each bit corresponds to one of the SCell group(s) configured by higher layers parameter *dormancyGroupOutsideActiveTime*, with MSB to LSB of the bitmap corresponding to the first to last configured SCell group in ascending order of *DormancyGroupID*. + +The size of DCI format 2\_6 is indicated by the higher layer parameter *sizeDCI-2-6*, according to Clause 10.3 of [5, TS 38.213]. + +##### 7.3.1.3.8 Format 2\_7 + +DCI format 2\_7 is used for notifying the paging early indication and TRS availability indication for one or more UEs. + +The following information is transmitted by means of the DCI format 2\_7 with CRC scrambled by PEI-RNTI: + +- Paging indication field - bit(s), where + - is the number of paging occasions configured by higher layer parameter *po-NumPerPEI* as defined in Clause 10.4A in [5, TS 38.213]; + - is the number of sub-groups of a paging occasion configured by higher layer parameter *subgroupsNumPerPO*. + - Each bit in the field indicates one UE subgroup of a paging occasion. +- TRS availability indication - 1, 2, 3, 4, 5, or 6 bits, where the number of bits is equal to one plus the highest value of all the *indBitID(s)* provided by the *trs-ResourceSetConfig* if configured; 0 bits otherwise. + +The size of DCI format 2\_7 is indicated by the higher layer parameter *payloadSizeDCI-2-7*, according to Clause 10.4A of [5, TS 38.213]. The number of information bits in format 2\_7 shall be equal to or less than the payload size of format 2\_7. If the number of information bits in format 2\_7 is less than the size of format 2\_7, the remaining bits are reserved. + +##### 7.3.1.3.9 Format 2\_8 + +DCI format 2\_8 is used for notifying the aperiodic beam indication and associated time resources + +The following information is transmitted by means of the DCI format 2\_8 with CRC scrambled by NCR-RNTI: + +- Beam index 1, Beam index 2, ..., Beam index N + +The bitwidth of each beam index field is determined by the higher layer parameter *aperiodicBeamFieldWidth*. + +- Time resource indication 1, Time resource indication 2, ..., Time resource indication N + +The bitwidth of each time resource indication field is determined by max, where $N$ is the number of time domain resources configured by *aperiodicFwdConfig*. The bit field indexes of a time resource indication field are mapped to the time domain resources configured by *aperiodicFwdConfig* according to an ascending order of a resource identity configured by *aperiodicFwdTimeRsrcId*, with the bit field index 0 mapped to the time resource with the smallest resource identity. + +The N beam indexes are sequentially associated with the N time resource indications with one to one mapping. N is configured by the higher layer parameter *numberOfFields*. The size of DCI format 2\_8 is up to 128 bits. + +##### 7.3.1.3.10 Format 2\_9 + +DCI format 2\_9 is used for activating or de-activating the cell DTX and/or DRX configuration of one or multiple serving cells for one or more UEs, and/or for providing NES-mode indication of the primary cell for one or more UEs. + +The following information is transmitted by means of the DCI format 2\_9 with CRC scrambled by cellDTRX-RNTI: + +- block number 1, block number 2, ..., block number N + +where the starting position of a block associated with a serving cell is determined by the parameter *positionInDCI-cellDTRX* provided by higher layers for the UE. + +If the UE is configured to monitor DCI 2\_9 with CRC scrambled by cellDTRX-RNTI, one or more blocks are configured for the UE by higher layers, with the following fields defined for each block: + +- Cell DTX/DRX indication - number of bits determined by the following: + - If higher layer parameter *cellDTXDRX-L1activation* is configured + - 2 bits as defined in Clause 11.5 of [5, TS38.213] if *cellDTXDRXconfigType* is configured to *dtxdrx* for the associated serving cell of the block, with the MSB corresponding to cell DTX configuration and the LSB corresponding to cell DRX configuration; + - 1 bit as defined in Clause 11.5 of [5, TS38.213] if *cellDTXDRXconfigType* is configured to either *dtx* or *drx* for the associated serving cell of the block; + - 0 bit otherwise. +- NES-mode indication – 1 bit indicating NES-specific CHO execution condition as defined in Clause 11.5 of [5, TS38.213], if the higher layer parameter *nesEvent* is configured and the associated serving cell of the block is primary cell; 0 bit otherwise. + +The size of DCI format 2\_9 is indicated by the higher layer parameter *sizeDCI-2-9*. + +#### 7.3.1.4 DCI formats for scheduling of sidelink + +##### 7.3.1.4.1 Format 3\_0 + +DCI format 3\_0 is used for scheduling of NR PSCCH and NR PSSCH in one cell, or scheduling of NR PSCCH, NR PSSCH and NR SL PRS for a shared SL PRS resource pool in one cell. + +The following information is transmitted by means of the DCI format 3\_0 with CRC scrambled by SL-RNTI or SL-CS-RNTI: + +- Resource pool index - bits, where $I$ is the total number of resource pools for transmission configured by the higher layer parameter *sl-TxPoolScheduling*, if configured, and *sl-DiscTxPoolScheduling*, if configured. +- Time gap - 3 bits determined by higher layer parameter *sl-DCI-ToSL-Trans*, as defined in clause 8.1.2.1 of [6, TS 38.214] +- HARQ process number - 4 bits. + +- New data indicator - 1 bit. +- Lowest index of the subchannel allocation to the initial transmission - bits as defined in Clause 8.1.2.2 of [6, TS 38.214]. +- Lowest index of the RB set allocation to the initial transmission - bits as defined in Clause 8.1.2.2 of [6, TS 38.214] if the higher layer parameter *transmissionStructureForPSCCHandPSSCH* in *SL-BWP-Config* is configured to 'interlaceRB'; 0 bit otherwise. +- SCI format 1-A fields according to clause 8.3.1.1: + - Frequency resource assignment. + - Time resource assignment. +- PSFCH-to-HARQ feedback timing indicator - bits, where $N$ is the number of entries in the higher layer parameter *sl-PSFCH-ToPUCCH*, as defined in clause 16.5 of [5, TS 38.213] +- PUCCH resource indicator - 3 bits as defined in clause 16.5 of [5, TS 38.213]. +- Configuration index - 0 bit if the UE is not configured to monitor DCI format 3\_0 with CRC scrambled by SL-CS-RNTI; otherwise 3 bits as defined in clause 8.1.2 of [6, TS 38.214]. If the UE is configured to monitor DCI format 3\_0 with CRC scrambled by SL-CS-RNTI, this field is reserved for DCI format 3\_0 with CRC scrambled by SL-RNTI. +- Counter sidelink assignment index - 2 bits + - 2 bits as defined in clause 16.5.2 of [5, TS 38.213] if the UE is configured with *pdsch-HARQ-ACK-Codebook = dynamic* + - 2 bits as defined in clause 16.5.1 of [5, TS 38.213] if the UE is configured with *pdsch-HARQ-ACK-Codebook = semi-static* +- Padding bits, if required + +If the total number of transmit resource pools provided in *sl-TxPoolScheduling*, if configured, and *sl-DiscTxPoolScheduling*, if configured, is larger than one, zeros shall be appended to the DCI format 3\_0 until the payload size is equal to the size of a DCI format 3\_0 given by a configuration of the transmit resource pool resulting in the largest number of information bits for DCI format 3\_0. + +If the UE is configured to monitor DCI format 3\_1 and/or DCI format 3\_2 and the number of information bits in DCI format 3\_0 is less than the larger payload size of DCI format 3\_1 if configured and DCI format 3\_2 if configured, zeros shall be appended to DCI format 3\_0 until the payload size equals the larger payload size of DCI format 3\_1 if configured and DCI format 3\_2 if configured. + +##### 7.3.1.4.2 Format 3\_1 + +DCI format 3\_1 is used for scheduling of LTE PSCCH and LTE PSSCH in one cell. + +The following information is transmitted by means of the DCI format 3\_1 with CRC scrambled by SL Semi-Persistent Scheduling V-RNTI: + +- Timing offset - 3 bits determined by higher layer parameter *sl-TimeOffsetEUTRA-List*, as defined in clause 16.6 of [5, TS 38.213] +- Carrier indicator - 3 bits as defined in 5.3.3.1.9A of [11, TS 36.212]. +- Lowest index of the subchannel allocation to the initial transmission - $\lceil \log_2(N_{\text{subchannel}}^{\text{SL}}) \rceil$ bits as defined in 5.3.3.1.9A of [11, TS 36.212]. +- Frequency resource location of initial transmission and retransmission, as defined in 5.3.3.1.9A of [11, TS 36.212] +- Time gap between initial transmission and retransmission, as defined in 5.3.3.1.9A of [11, TS 36.212] +- SL index - 2 bits as defined in 5.3.3.1.9A of [11, TS 36.212] +- SL SPS configuration index - 3 bits as defined in clause 5.3.3.1.9A of [11, TS 36.212]. +- Activation/release indication - 1 bit as defined in clause 5.3.3.1.9A of [11, TS 36.212]. + +If the UE is configured to monitor DCI format 3\_0 and/or DCI format 3\_2 and the number of information bits in DCI format 3\_1 is less than the larger payload size of DCI format 3\_0 if configured and DCI format 3\_2 if configured, zeros shall be appended to DCI format 3\_1 until the payload size equals the larger payload size of DCI format 3\_0 if configured and DCI format 3\_2 if configured. + +##### 7.3.1.4.3 Format 3\_2 + +DCI format 3\_2 is used for scheduling of NR SL PRS for a dedicated SL PRS resource pool in one cell. + +The following information is transmitted by means of the DCI format 3\_2 with CRC scrambled by SL-PRS-RNTI or SL-PRS-CS-RNTI: + +- Resource pool index - bits, where *I* is the total number of dedicated SL PRS resource pools for transmission configured by the higher layer parameter *sl-PRS-TxPoolScheduling*, if configured. +- Time gap - 3 bits determined by higher layer parameter *sl-DCI-ToSL-Trans*, as defined in clause 8.2.4.1.1 of [6, TS 38.214] +- First SL PRS indicator - bits indicating the SL PRS resource ID for the first SL PRS transmission, where the value is the total number of SL PRS resources within a slot in a dedicated SL PRS resource pool and provided by the higher layer parameter *sl-PrsResources-Dedicated-SL-PRS-RP*. +- SCI format 1-B fields according to clause 8.3.1.2: + - Time resource assignment + - Resource ID indication +- Configuration index – 0 bit if the UE is not configured to monitor DCI format 3\_2 with CRC scrambled by SL-PRS-CS-RNTI; otherwise 3 bits as defined in clause 8.2.4.1 of [6, TS 38.214]. If the UE is configured to monitor DCI format 3\_2 with CRC scrambled by SL-PRS-CS-RNTI, this field is reserved for DCI format 3\_2 with CRC scrambled by SL-PRS-RNTI. +- Activation/release indication – 0 bit if the UE is not configured to monitor DCI format 3\_2 with CRC scrambled with SL-PRS-CS-RNTI; otherwise 1 bit, where value 0 indicates release and value 1 indicates activation. If the UE is configured to monitor DCI format 3\_2 with CRC scrambled with SL-PRS-CS-RNTI, this field is reserved for DCI format 3\_2 with CRC scrambled by SL-PRS-RNTI. +- Padding bits, if required. + +If the total number of transmit resource pools provided in *sl-PRS-TxPoolScheduling*, if configured, is larger than one, zeros shall be appended to the DCI format 3\_2 until the payload size is equal to the size of a DCI format 3\_2 given by a configuration of the transmit resource pool resulting in the largest number of information bits for DCI format 3\_2. + +If the UE is configured to monitor DCI format 3\_0 and/or DCI format 3\_1 and the number of information bits in DCI format 3\_2 is less than the larger payload size of DCI format 3\_0 if configured and DCI format 3\_1 if configured, zeros shall be appended to DCI format 3\_2 until the payload size equals the larger payload size of DCI format 3\_0 if configured and DCI format 3\_1 if configured. + +#### 7.3.1.5 DCI formats for scheduling of MBS + +##### 7.3.1.5.1 Format 4\_0 + +DCI format 4\_0 is used for the scheduling of PDSCH for broadcast or for multicast in RRC\_INACTIVE state in DL cell. + +The following information is transmitted by means of the DCI format 4\_0 with CRC scrambled by MCCH-RNTI or G-RNTI for broadcast configured by *MBS-SessionInfo*, or by multicast-MCCH-RNTI for multicast configured by *MBS-SessionInfoMulticast*: + +- Frequency domain resource assignment - bits where equals to + - the size of CORESET 0 if CORESET 0 is configured for the cell; and + - the size of initial DL bandwidth part if CORESET 0 is not configured for the cell. +- Time domain resource assignment - 4 bits as defined in Clause 5.1.2.1 of [6, TS38.214] +- VRB-to-PRB mapping - 1 bit according to Table 7.3.1.2.2-5 + +- Modulation and coding scheme - 5 bits as defined in Clause 5.1.3 of [6, TS38.214] +- Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2 +- MCCH change notification - 2 bits as defined in Clause 5.9.1.3 and Clause 5.x.1.3 of [9, TS38.331] if the CRC of the DCI format 4\_0 is scrambled by MCCH-RNTI and multicast-MCCH-RNTI respectively. Otherwise, this bit field is reserved. +- Reserved bits - 14bits + +##### 7.3.1.5.2 Format 4\_1 + +DCI format 4\_1 is used for the scheduling of PDSCH for multicast in DL cell. + +The following information is transmitted by means of the DCI format 4\_1 with CRC scrambled by G-RNTI for multicast or G-CS-RNTI configured by *MBS-RNTI-SpecificConfig*, or by G-RNTI for multicast configured by *MBS-SessionInfoListMulticast*: + +- Frequency domain resource assignment - bits where $\text{bits} = \min(\text{CORESET\_size}, \text{initial\_DL\_BWP\_size})$ + - the size of CORESET 0 if CORESET 0 is configured for the cell; and + - the size of initial DL bandwidth part if CORESET 0 is not configured for the cell. +- Time domain resource assignment - 4 bits as defined in Clause 5.1.2.1 of [6, TS38.214] +- VRB-to-PRB mapping - 1 bit according to Table 7.3.1.2.2-5 +- Modulation and coding scheme - 5 bits as defined in Clause 5.1.3 of [6, TS38.214] +- New data indicator - 1 bit +- Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2 +- HARQ process number - 4 bits +- Downlink assignment index - 2 bits as defined in Clause 9.1.3 of [5, TS 38.213], as counter DAI +- PUCCH resource indicator - 3 bits as defined in Clause 9.2.3 of [5, TS38.213] +- PDSCH-to-HARQ\_feedback timing indicator - 3 bits as defined in Clause 9.2.3 of [5, TS38.213] +- Reserved bits - 3 bits + +##### 7.3.1.5.3 Format 4\_2 + +DCI format 4\_2 is used for the scheduling of PDSCH for multicast in DL cell. + +The following information is transmitted by means of the DCI format 4\_2 with CRC scrambled by G-RNTI for multicast or G-CS-RNTI configured by *MBS-RNTI-SpecificConfig*: + +- Frequency domain resource assignment - number of bits determined by the following, where $\text{bits} = \lceil \log_2(\text{common\_frequency\_resource\_size}) \rceil$ is the size of the common frequency resource as defined in Clause 18 of [5, TS38.213]. + - $\text{bits}$ if only resource allocation type 0 is configured, where $\text{bits}$ is defined in Clause 5.1.2.2.1 of [6, TS38.214], + - $\text{bits}$ if only resource allocation type 1 is configured, or + - $\text{bits}$ if *resourceAllocation* in *pdsch-ConfigMulticast* is configured as 'dynamicSwitch'. + - If *resourceAllocation* in *pdsch-ConfigMulticast* is configured as 'dynamicSwitch', the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit value of 1 indicates resource allocation type 1. + - For resource allocation type 0, the LSBs provide the resource allocation as defined in Clause 5.1.2.2.1 of [6, TS 38.214]. + - For resource allocation type 1, the LSBs provide the resource allocation as defined in Clause 5.1.2.2.2 of [6, TS 38.214] +- Time domain resource assignment - 0, 1, 2, 3, or 4 bits as defined in Clause 5.1.2.1 of [6, TS 38.214]. The bitwidth for this field is determined as $\text{bits}$ , where $I$ is the number of entries in the higher layer parameter *pdsch-TimeDomainAllocationList* if the higher layer parameter is configured; otherwise $I$ is the number of entries in the default table. +- VRB-to-PRB mapping - 0 or 1 bit: + +- 0 bit if only resource allocation type 0 is configured or if *vrb-ToPRB-Interleaver* in *pdsch-ConfigMulticast* is not configured; +- 1 bit according to Table 7.3.1.2.2-5 otherwise, only applicable to resource allocation type 1, as defined in Clause 7.3.1.6 of [4, TS 38.211]. +- PRB bundling size indicator - 0 bit if the higher layer parameter *prb-BundlingType* is not configured in *pdsch-ConfigMulticast* or is set to 'staticBundling', or 1 bit if the higher layer parameter *prb-BundlingType* in *pdsch-ConfigMulticast* is set to 'dynamicBundling' according to Clause 5.1.2.3 of [6, TS 38.214]. +- Rate matching indicator - 0, 1, or 2 bits according to higher layer parameters *rateMatchPatternGroup1* and *rateMatchPatternGroup2* in *pdsch-ConfigMulticast*, where the MSB is used to indicate *rateMatchPatternGroup1* and the LSB is used to indicate *rateMatchPatternGroup2* when there are two groups. +- ZP CSI-RS trigger - 0, 1, or 2 bits as defined in Clause 5.1.4.2 of [6, TS 38.214]. The bitwidth for this field is determined as $\lceil \log_2 N \rceil$ bits, where $N$ is the number of aperiodic ZP CSI-RS resource sets configured in *pdsch-ConfigMulticast*. + +For transport block 1: + +- Modulation and coding scheme - 5 bits as defined in Clause 5.1.3.1 of [6, TS 38.214] +- New data indicator - 1 bit +- Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2 + +For transport block 2 (only present if *maxNrofCodeWordsScheduledByDCI* configured in *pdsch-ConfigMulticast* equals 2): + +- Modulation and coding scheme - 5 bits as defined in Clause 5.1.3.1 of [6, TS 38.214] +- New data indicator - 1 bit +- Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2 +- HARQ process number - 4 bits +- Downlink assignment index - number of bits as defined in the following + - 2 bits if the higher layer parameter *pdsch-HARQ-ACK-Codebook = dynamic* is configured for multicast, where the 2 bits are the counter DAI; + - 0 bits otherwise. + +If higher layer parameter *priorityIndicatorDCI-4-2* is configured in *pdsch-ConfigMulticast*, if the bit width of the Downlink assignment index in DCI format 4\_2 for one HARQ-ACK codebook is not equal to that of the Downlink assignment index in DCI format 4\_2 for the other HARQ-ACK codebook, a number of most significant bits with value set to '0' are inserted to smaller Downlink assignment index until the bit width of the Downlink assignment index in DCI format 4\_2 for the two HARQ-ACK codebooks are the same. + +- PUCCH resource indicator - 3 bits as defined in Clause 9.2.3 of [5, TS 38.213] +- PDSCH-to-HARQ\_feedback timing indicator - 0, 1, 2, or 3 bits as defined in Clause 9.2.3 of [5, TS 38.213]. The bitwidth for this field is determined as $\lceil \log_2 I \rceil$ bits, where $I$ is the number of entries in the higher layer parameter *dl-DataToUL-ACK* in *pucch-ConfigMulticast1* if configured or *pucch-ConfigMulticast2* if configured; otherwise, $I$ is the number of entries in the higher layer parameter *dl-DataToUL-ACK* in *PUCCH-Config*. + +If higher layer parameter *priorityIndicatorDCI-4-2* is configured in *pdsch-ConfigMulticast*, if the bit width of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 4\_2 for one HARQ-ACK codebook is not equal to that of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 4\_2 for the other HARQ-ACK codebook, a number of most significant bits with value set to '0' are inserted to smaller PDSCH-to-HARQ\_feedback timing indicator until the bit width of the PDSCH-to-HARQ\_feedback timing indicator in DCI format 4\_2 for the two HARQ-ACK codebooks are the same. + +- Antenna port(s) - 4, 5, or 6 bits as defined by Tables 7.3.1.2.2-1/2/3/4, where the number of CDM groups without data of values 1, 2, and 3 refers to CDM groups $\{0\}$ , $\{0, 1\}$ , and $\{0, 1, 2\}$ respectively. The antenna ports shall be determined according to the ordering of DMRS port(s) given by Tables 7.3.1.2.2-1/2/3/4. + +If a UE is configured with both *dmrs-DownlinkForPDSCH-MappingTypeA* and *dmrs-DownlinkForPDSCH-MappingTypeB*, the bitwidth of this field equals $\max(\lceil \log_2 N_A \rceil, \lceil \log_2 N_B \rceil)$ , where $N_A$ is the "Antenna ports" bitwidth derived according to *dmrs-DownlinkForPDSCH-MappingTypeA* and $N_B$ is the "Antenna ports" bitwidth derived according to *dmrs-DownlinkForPDSCH-MappingTypeB*. A number of zeros are padded in the MSB of this field, if the mapping type of the PDSCH corresponds to the smaller value of $N_A$ and $N_B$ . + +- Transmission configuration indication - 0 bit if higher layer parameter *tci-PresentInDCI* in *pdcch-ConfigMulticast* is not enabled; otherwise 3 bits as defined in Clause 5.1.5 of [6, TS 38.214]. + +- DMRS sequence initialization - 1 bit. +- Priority indicator - 0 bit if higher layer parameter *priorityIndicatorDCI-4-2* is not configured in *pdsch-ConfigMulticast*; otherwise 1 bit as defined in Clause 9 in [5, TS 38.213]. +- Enabling/disabling HARQ-ACK feedback indication - 1 bit if higher layer parameter *harq-FeedbackEnablerMulticast* indicates *dci-enabler*, where value 1 indicates enabling HARQ-ACK feedback and value 0 indicates disabling HARQ-ACK feedback; 0 bit, otherwise. + +The size of DCI format 4\_2 is configurable by higher layer parameter *sizeDCI-4-2* from 20 bits and up to 140 bits. + +### 7.3.2 CRC attachment + +Error detection is provided on DCI transmissions through a Cyclic Redundancy Check (CRC). + +The entire payload is used to calculate the CRC parity bits. Denote the bits of the payload by $a$ , where $a$ is the payload size and $a$ is the number of parity bits. Let $a$ be a bit sequence such that $a_i$ for $i = 0, 1, \dots, a-1$ and $a_i$ for $i = a, a+1, \dots, a+a-1$ . The parity bits are computed with input bit sequence $a$ and attached according to Clause 5.1 by setting $a$ to 24 bits and using the generator polynomial $1 + x^3 + x^5 + x^7 + x^8 + x^9 + x^{10} + x^{11} + x^{12} + x^{13} + x^{14} + x^{15} + x^{16} + x^{17} + x^{18} + x^{19} + x^{20} + x^{21} + x^{22} + x^{23} + x^{24}$ . The output bit $b_0, b_1, b_2, b_3, \dots, b_{a-1}$ is + +for + +for , + +where . + +After attachment, the CRC parity bits are scrambled with the corresponding RNTI $r$ , where $r$ corresponds to the MSB of the RNTI, to form the sequence of bits $c$ . The relation between $c_k$ and $b_k$ is: + +for $k = 0, 1, 2, \dots,$ + +for $k = , \dots, .$ + +### 7.3.3 Channel coding + +Information bits are delivered to the channel coding block. They are denoted by $a$ , where $a$ is the number of bits, and they are encoded via Polar coding according to Clause 5.3.1, by setting $a$ , $a$ , and $a$ . + +After encoding the bits are denoted by $c$ , where $c$ is the number of coded bits. + +### 7.3.4 Rate matching + +The input bit sequence to rate matching is $c$ . + +Rate matching is performed according to Clause 5.4.1 by setting $a$ . + +The output bit sequence after rate matching is denoted as $c$ . + +# 8 Sidelink transport channels and control information + +## 8.1 Sidelink broadcast channel + +The processing for SL-BCH transport channel follows the BCH according to clause 7.1, with the following changes: + +- In Clause 7.1, 'maximum of one transport block every 80ms' is replaced with 'maximum of one transport block'. +- Clause 7.1.1 for PBCH payload generation is not performed. +- Clause 7.1.2 for scrambling is not performed. +- In clause 7.1.5, the rate matching output sequence length $E = 1386$ when higher layer parameter *cyclicPrefix* is configured, otherwise, $E = 1782$ . + +### 8.1.1 Void + +## 8.2 Sidelink shared channel + +The processing for SL-SCH transport channel follows the UL-SCH according to clause 6.2, with the following changes: + +- Rate matching of SL-SCH follows the rate matching according to clause 6.2.5 by setting +- Clause 6.2.7 is replaced by clause 8.2.1 + +### 8.2.1 Data and control multiplexing + +Denote the coded bits for SL-SCH as $c_{SL}$ . + +Denote the coded bits for the 2nd-stage SCI, as $c_{SCI}$ . + +Denote the multiplexed data and control coded bit sequence as $c$ , where $G$ is the total number of coded bits for transmission. + +Assuming that $L$ is the number of layers onto which the SL-SCH transport block is mapped, the multiplexed data and control coded bit sequence $c$ is obtained as follows: + +Denote $m$ is modulation order of the 2nd-stage SCI. + +``` + +if $L > 1$ , + for $l$ to $L-1$ + if $c_{SL}[l] \neq 0$ + end if + if $c_{SCI}[l] \neq 0$ + end if + end for +end if +if $L = 1$ , + let + set + for $l$ to $G-1$ + for $l$ to $G-1$ + for $l$ to $G-1$ + if $c_{SL}[l] \neq 0$ + else + // placeholder bit + end if + end for + end for + end for + for $l$ to $G-1$ + end for +end if + +``` + +## 8.3 Sidelink control information on PSCCH + +SCI carried on PSCCH is a 1st-stage SCI, which transports sidelink scheduling information. + +### 8.3.1 1st-stage SCI formats + +The fields defined in each of the 1st-stage SCI formats below are mapped to the information bits to as follows: + +Each field is mapped in the order in which it appears in the description, with the first field mapped to the lowest order information bit and each successive field mapped to higher order information bits. The most significant bit of each field is mapped to the lowest order information bit for that field, e.g. the most significant bit of the first field is mapped to . + +#### 8.3.1.1 SCI format 1-A + +SCI format 1-A is used for the scheduling of PSSCH and 2nd-stage-SCI on PSSCH + +The following information is transmitted by means of the SCI format 1-A: + +- Priority - 3 bits as specified in clause 5.4.3.3 of [12, TS 23.287] and clause 5.22.1.3.1 of [8, TS 38.321]. Value '000' of Priority field corresponds to priority value '1', value '001' of Priority field corresponds to priority value '2', and so on. +- Frequency resource assignment - number of bits determined by the following: + - If higher layer parameter *transmissionStructureForPSCCHandPSSCH* in *SL-BWP-Config* is not configured or configured to 'contiguousRB' + - bits when the value of the higher layer parameter *sl-MaxNumPerReserve* is configured to 2; otherwise bits when the value of the higher layer parameter *sl-MaxNumPerReserve* is configured to 3, as defined in clause 8.1.5 of [6, TS 38.214]. + - If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* in *SL-BWP-Config* is configured to 'interlaceRB' + - X + Y bits provide the frequency domain resource allocation according to Clause x.x of [6, TS 38.214], where the X MSBs provide the RB set allocation and the Y LSBs provide the sub-channel allocation, + - the value of X is determined by when the value of the higher layer parameter *sl-MaxNumPerReserve* is configured to 2, or determined by when the value of the higher layer parameter *sl-MaxNumPerReserve* is configured to 3, where is the number of RB sets in a resource pool + - the value of Y is determined by when the value of the higher layer parameter *sl-MaxNumPerReserve* is configured to 2, or determined by when the value of the higher layer parameter *sl-MaxNumPerReserve* is configured to 3, as defined in clause 8.1.5 of [6, TS 38.214]. +- Time resource assignment - 5 bits when the value of the higher layer parameter *sl-MaxNumPerReserve* is configured to 2; otherwise 9 bits when the value of the higher layer parameter *sl-MaxNumPerReserve* is configured to 3, as defined in clause 8.1.5 of [6, TS 38.214]. +- Resource reservation period - bits as defined in clause 16.4 of [5, TS 38.213], where is the number of entries in the higher layer parameter *sl-ResourceReservePeriodList*, if higher layer parameter *sl-MultiReserveResource* is configured; 0 bit otherwise. +- DMRS pattern - bits as defined in clause 8.4.1.1.2 of [4, TS 38.211], where is the number of DMRS patterns configured by higher layer parameter *sl-PSSCH-DMRS-TimePatternList*. +- 2nd-stage SCI format - 2 bits as defined in Table 8.3.1.1-1. +- Beta\_offset indicator - 2 bits as provided by higher layer parameter *sl-BetaOffsets2ndSCI* and Table 8.3.1.1-2. +- Number of DMRS port - 1 bit as defined in Table 8.3.1.1-3. +- Modulation and coding scheme - 5 bits as defined in clause 8.1.3 of [6, TS 38.214]. +- Additional MCS table indicator - as defined in clause 8.1.3.1 of [6, TS 38.214]: 1 bit if one MCS table is configured by higher layer parameter *sl-Additional-MCS-Table*; 2 bits if two MCS tables are configured by higher layer parameter *sl-Additional-MCS-Table*; 0 bit otherwise. +- PSFCH overhead indication - 1 bit as defined in clause 8.1.3.2 of [6, TS 38.214] if higher layer parameter *sl-PSFCH-Period* = 2 or 4; 0 bit otherwise. + +- Reserved - a number of bits as determined by the following: + - bits as configured by higher layer parameter *sl-NumReservedBits*, with value set to zero, if higher layer parameter *sl-IndicationUE-B* is not configured, or if higher layer parameter *sl-IndicationUE-B* is configured to 'disabled', and if higher layer parameter *transmissionStructureForPSCCHandPSSCH* in *SL-BWP-Config* is not configured; + - bits if higher layer parameter *sl-IndicationUE-B* is configured to 'enabled', and if higher layer parameter *transmissionStructureForPSCCHandPSSCH* in *SL-BWP-Config* is configured, with value set to zero. + - bits otherwise, with value set to zero. +- COT sharing flag – 0 or 1 bit +- 1 bit as defined in [14, TS 37.213] if the higher layer parameter *transmissionStructureForPSCCHandPSSCH* in *SL-BWP-Config* is configured; +- 0 bit otherwise.- Conflict information receiver flag - 0 or 1 bit +- 1 bit if higher layer parameter *sl-IndicationUE-B* is configured to 'enabled', where the bit value of 0 indicates that the UE cannot be a UE to receive conflict information and the bit value of 1 indicates that the UE can be a UE to receive conflict information as defined in Clause 16.3.0 of [5, TS 38.213]; +- 0 bit otherwise. + +**Table 8.3.1.1-1: 2nd-stage SCI formats** + +| Value of 2nd-stage SCI format field | 2nd-stage SCI format | +|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 00 | SCI format 2-A | +| 01 | SCI format 2-B; or
reserved if higher layer parameter
transmissionStructureForPSCCHandPSSCH in SL-BWP-Config is configured | +| 10 | SCI format 2-C; or
reserved if higher layer parameter
transmissionStructureForPSCCHandPSSCH in SL-BWP-Config is configured and the COT sharing flag field is set to '1' | +| 11 | SCI format 2-D; or
reserved if higher layer parameter
transmissionStructureForPSCCHandPSSCH in SL-BWP-Config is configured | + +**Table 8.3.1.1-2: Mapping of Beta\_offset indicator values to indexes in Table 9.3-2 of [5, TS38.213]** + +| Value of Beta_offset indicator | Beta_offset index in Table 9.3-2 of TS 38.213 [5] | +|--------------------------------|--------------------------------------------------------------------------------------| +| 00 | 1 st index provided by higher layer parameter sl-BetaOffsets2ndSCI | +| 01 | 2 nd index provided by higher layer parameter sl-BetaOffsets2ndSCI | +| 10 | 3 rd index provided by higher layer parameter sl-BetaOffsets2ndSCI | +| 11 | 4 th index provided by higher layer parameter sl-BetaOffsets2ndSCI | + +**Table 8.3.1.1-3: Number of DMRS port(s)** + +| Value of the Number of DMRS port field | Antenna ports | +|----------------------------------------|---------------| +| 0 | 1000 | +| 1 | 1000 and 1001 | + +#### 8.3.1.2 SCI format 1-B + +SCI format 1-B is used for the scheduling of SL PRS for a dedicated SL PRS resource pool. + +The following information is transmitted by means of the SCI format 1-B: + +- Priority - 3 bits as specified in clause x.x of [12, TS 23.586] and clause x.x of [8, TS 38.321]. Value '000' of Priority field corresponds to priority value '1', value '001' of Priority field corresponds to priority value '2', and so on. + +- Source ID – 12 or 24 bits determined by higher layer parameter *sl-SRC-ID-Len-Dedicated-SL-PRS-RP*, as defined in clause 16.4A of [5, TS 38.213]. +- Destination ID – 24 bits as defined in clause 16.4A of [5, TS 38.213]. +- Cast type indicator – 2 bits as defined in Table 8.3.1.2-1 and in clause 16.4A of [5, TS 38.213]. +- Resource reservation period – bits as defined in clause 16.4A of [5, TS 38.213], where is the number of entries in the higher layer parameter *reservationPeriodAllowed-Dedicated-SL-PRS-RP*, if higher layer parameter *reservationPeriodAllowed-Dedicated-SL-PRS-RP* is configured; 0 bit otherwise. +- Time resource assignment – 5 bits when the value of the higher layer parameter *sl-MaxNumPerReserve-Dedicated-SL-PRS-RP* is configured to 2; otherwise 9 bits when the value of the higher layer parameter *sl-MaxNumPerReserve-Dedicated-SL-PRS-RP* is configured to 3, as defined in clause 8.2.4.3 of [6, TS 38.214]. +- Resource ID indication –bits when the value of the higher layer parameter *sl-MaxNumPerReserve-Dedicated-SL-PRS-RP* is configured to 2; otherwise bits when the value of the higher layer parameter *sl-MaxNumPerReserve-Dedicated-SL-PRS-RP* is configured to 3. The value is the total number of SL PRS resources within a slot in a dedicated SL PRS resource pool and provided by the higher layer parameter *sl-PrsResources-Dedicated-SL-PRS-RP*. +- SL PRS request – 1 bit as defined in clause 8.4.4 of [6, TS 38.214] when the higher layer parameter *sl-SCI-based-SL-PRS-Tx-Trigger-SCI1-B* is provided; 0 bit otherwise. +- Reserved - bits as configured by higher layer parameter *sl-NumReservedBits-SCI1B-Dedicated-SL-PRS-RP*, with value set to zero. + +**Table 8.3.1.2-1: Cast type indicator** + +| Value of Cast type indicator | Cast type | +|------------------------------|-----------| +| 00 | Broadcast | +| 01 | Groupcast | +| 10 | Unicast | +| 11 | Reserved | + +### 8.3.2 CRC attachment + +CRC attachment is performed according to clause 7.3.2 except that scrambling is not performed. + +### 8.3.3 Channel coding + +Channel coding is performed according to clause 7.3.3. + +### 8.3.4 Rate Matching + +Rate matching is performed according to clause 7.3.4. + +## 8.4 Sidelink control information on PSSCH + +SCI carried on PSSCH is a 2nd-stage SCI, which transports sidelink scheduling information, and/or inter-UE coordination related information. + +### 8.4.1 2nd-stage SCI formats + +The fields defined in each of the 2nd-stage SCI formats below are mapped to the information bits to as follows: + +Each field is mapped in the order in which it appears in the description, with the first field mapped to the lowest order information bit and each successive field mapped to higher order information bits. The most significant bit of each field is mapped to the lowest order information bit for that field, e.g. the most significant bit of the first field is mapped to . + +#### 8.4.1.1 SCI format 2-A + +SCI format 2-A is used for the decoding of PSSCH, with HARQ operation when HARQ-ACK information includes ACK or NACK, when HARQ-ACK information includes only NACK, or when there is no feedback of HARQ-ACK information. + +The following information is transmitted by means of the SCI format 2-A: + +- HARQ process number - bits. +- New data indicator - 1 bit. +- Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2. +- Source ID - 8 bits as defined in clause 8.1 of [6, TS 38.214]. +- Destination ID - 16 bits as defined in clause 8.1 of [6, TS 38.214]. +- HARQ feedback enabled/disabled indicator - 1 bit as defined in clause 16.3 of [5, TS 38.213]. +- Cast type indicator - 2 bits as defined in Table 8.4.1.1-1 and in clause 8.1 of [6, TS 38.214]. +- CSI request - 1 bit as defined in clause 8.2.1 of [6, TS 38.214] and in clause 8.1 of [6, TS 38.214]. + +If the 'COT sharing flag' field in SCI format 1-A is present and set to '1', all the remaining fields are set as follows: + +- CAPC – 2 bits. Values '00', '01', '10' and '11' correspond to CAPC values '1', '2', '3' and '4' as defined in Table 4.5-1 of [14, TS 37.213], respectively. +- COT sharing cast type – 2 bits as defined in Table 8.4.1.1-1. +- COT sharing additional ID – 24 bits. The 16 LSBs provide layer 1 destination ID and the 8 MSBs provide layer 1 source ID, as defined in [6, TS 38.214]. The 8 MSBs are reserved when the COT sharing cast type field is set to '00' or '01'. +- Remaining COT duration – bits as defined in clause 4.5.3 of [14, TS 37.213], where is defined in Table 4.2-1 of Clause 4.2 of [4, TS 38.211]. + +**Table 8.4.1.1-1: Cast type indicator or COT sharing cast type** + +| Value of Cast type indicator or COT sharing cast type | Cast type | +|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 00 | Broadcast | +| 01 | Groupcast
when HARQ-ACK information includes ACK or NACK | +| 10 | Unicast | +| 11 | Groupcast
when HARQ-ACK information includes only NACK; or reserved, if higher layer parameter transmissionStructureForPSCCHandPSSCH in SL-BWP-Config is configured | + +#### 8.4.1.2 SCI format 2-B + +SCI format 2-B is used for the decoding of PSSCH, with HARQ operation when HARQ-ACK information includes only NACK, or when there is no feedback of HARQ-ACK information. + +The following information is transmitted by means of the SCI format 2-B: + +- HARQ process number - bits. +- New data indicator - 1 bit. +- Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2. +- Source ID - 8 bits as defined in clause 8.1 of [6, TS 38.214]. +- Destination ID - 16 bits as defined in clause 8.1 of [6, TS 38.214]. + +- HARQ feedback enabled/disabled indicator - 1 bit as defined in clause 16.3 of [5, TS 38.213]. +- Zone ID - 12 bits as defined in clause 5.8.11 of [9, TS 38.331]. +- Communication range requirement - 4 bits determined by higher layer parameter *sl-ZoneConfigMCR-Index*. + +#### 8.4.1.3 SCI format 2-C + +SCI format 2-C is used for the decoding of PSSCH, and providing inter-UE coordination information or requesting inter-UE coordination information. SCI format 2-C can be used only for unicast. + +The following information is transmitted by means of the SCI format 2-C: + +- HARQ process number - 4 bits +- New data indicator - 1 bit +- Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2 +- Source ID - 8 bits as defined in clause 8.1 of [6, TS 38.214] +- Destination ID - 16 bits as defined in clause 8.1 of [6, TS 38.214] +- HARQ feedback enabled/disabled indicator - 1 bit as defined in clause 16.3 of [5, TS 38.213] +- CSI request - 1 bit as defined in clause 8.2.1 of [6, TS 38.214] and in clause 8.1 of [6, TS 38.214] +- Providing/Requesting indicator - 1 bit, where value 0 indicates SCI format 2-C is used for providing inter-UE coordination information and value 1 indicates SCI format 2-C is used for requesting inter-UE coordination information + +If the 'Providing/Requesting indicator' field is set to 0, all the remaining fields are set as follows: + +- Resource combinations -number of bits determined by the following: + - If higher layer parameter *transmissionStructureForPSCCHandPSSCH* in *SL-BWP-Config* is not configured or configured to 'contiguousRB' + - bits as defined in Clause 8.1.5A of [6, TS 38.214]; + - If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* in *SL-BWP-Config* is configured to 'interlaceRB' + - bits as defined in Clause 8.1.5A of [6, TS 38.214]; +- where + - and is the number of entries in the higher layer parameter *sl-ResourceReservePeriodList*, if higher layer parameter *sl-MultiReserveResource* is configured; otherwise. + - is provided by the higher layer parameter *sl-NumSubchannel* as defined in Clause 8.1.5 of [6, TS 38.214]. + - is the number of RB sets in a resource pool. +- First resource location - 8 bits as defined in Clause 8.1.5A of [6, TS 38.214]. +- Reference slot location - ( bits as defined in Clause 8.1.5A of [6, TS 38.214], where is defined in Table 4.2-1 of Clause 4.2 of [4, TS 38.211]. +- Resource set type - 1 bit, where value 0 indicates preferred resource set and value 1 indicates non-preferred resource set. +- Lowest subChannel indices - bits as defined in Clause 8.1.5A of [6, TS 38.214]. +- Lowest RB set indices - bits as defined in Clause 8.1.5A of [6, TS 38.214] if the higher layer parameter *transmissionStructureForPSCCHandPSSCH* in *SL-BWP-Config* is configured to 'interlaceRB'; 0 bit otherwise. + +If the 'Providing/Requesting indicator' field is set to 1, all the remaining fields are set as follows: + +- Priority - 3 bits as specified in clause 5.4.3.3 of [12, TS 23.287] and clause 5.22.1.3.1 of [8, TS 38.321]. Value '000' of Priority field corresponds to priority value '1', value '001' of Priority field corresponds to priority value '2', and so on. +- Number of subchannels - bits as defined in Clause 8.1.4A of [6, TS 38.214]. + +- Number of RB sets - bits as defined in Clause 8.1.4A of [6, TS 38.214] if the higher layer parameter *transmissionStructureForPSCCHandPSSCH* in *SL-BWP-Config* is configured to 'interlaceRB'; 0 bit otherwise. +- Resource reservation period - bits as defined in Clause 8.1.4A of [6, TS 38.214], where *sl-ResourceReservePeriodList* is the number of entries in the higher layer parameter *sl-ResourceReservePeriodList*, if higher layer parameter *sl-MultiReserveResource* is configured; 0 bit otherwise. +- Resource selection window location - bits as defined in Clause 8.1.4A of [6, TS 38.214], where *sl-ResourceSelectionWindowLocation* is defined in Table 4.2-1 of Clause 4.2 of [4, TS 38.211]. +- Resource set type - 1 bit, where value 0 indicates a request for inter-UE coordination information providing preferred resource set and value 1 indicates a request for inter-UE coordination information providing non-preferred resource set, if higher layer parameter *sl-DetermineResourceType* is configured to 'ueb'; otherwise, 0 bit. +- Padding bits. + +For operation in a same resource pool, zeros shall be appended to SCI format 2-C of which 'Providing/Requesting indicator' field is set to 1 until the payload size equals that of SCI format 2-C of which 'Providing/Requesting indicator' field is set to 0. + +#### 8.4.1.4 SCI format 2-D + +SCI format 2-D is used for the decoding of PSSCH and the scheduling of SL PRS for a shared SL PRS resource pool. + +The following information is transmitted by means of the SCI format 2-D: + +- SL PRS resource ID -bits, where the value *sl-PRSResourceID* is the total number of SL PRS resource IDs within a slot in a shared SL PRS resource pool and provided by the higher layer parameter *sl-PrsResources-Shared-SL-PRS-RP*. +- SL PRS request – 1 bit as defined in clause 8.4.4 of [6, TS 38.214] when the higher layer parameter *sl-SCI-based-SL-PRS-Tx-Trigger-SCI2-D* is provided; 0 bit otherwise. +- Embedded SCI format - 2 bits. This field indicates the embedded SCI format as defined in Table 8.4.1.4-1. +- Embedded SCI format payload - number of bits determined according to Table 8.4.1.4-1. This field is set to the associated payload of the embedded SCI format indicated by the 'Embedded SCI format' field as defined in Table 8.4.1.4-1. + +**Table 8.4.1.4-1: Embedded SCI format and payload** + +| Value of the Embedded SCI format field | Embedded SCI format | Embedded SCI format payload | +|----------------------------------------|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 00 | SCI format 2-A | Set to all fields included in SCI format 2-A. Padding bits, if necessary, are appended to the 'Embedded SCI format payload' field untill the bitwidth equals the larger payload size of SCI format 2-A and SCI format 2-B. | +| 01 | SCI format 2-B | Set to all fields included in SCI format 2-B. Padding bits, if necessary, are appended to the 'Embedded SCI format payload' field untill the bitwidth equals the larger payload size of SCI format 2-A and SCI format 2-B. | +| 10 | Reserved | Reserved | +| 11 | Reserved | Reserved | + +### 8.4.2 CRC attachment + +CRC attachment is performed according to clause 7.3.2 except that scrambling is not performed. + +### 8.4.3 Channel coding + +Channel coding is performed according to clause 7.3.3. + +### 8.4.4 Rate Matching + +For 2nd-stage SCI transmission on PSSCH with SL-SCH, the number of coded modulation symbols generated for 2nd-stage SCI transmission prior to duplication for the 2nd layer if present, denoted as $N_{sc}^{2nd}$ , is determined as follows: + +where + +- $N_{sc}^{2nd}$ is the number of the 2nd-stage SCI bits +- $N_{CRC}$ is the number of CRC bits for the 2nd-stage SCI, which is 24 bits. +- $N_{info}$ is indicated in the corresponding 1st-stage SCI. +- $N_{RB}$ is the scheduled bandwidth of PSSCH transmission, expressed as a number of subcarriers. +- $N_{sc}$ is the number of subcarriers in OFDM symbol that carry PSCCH and PSCCH DMRS associated with the PSSCH transmission. +- $N_{RE}$ is the number of resource elements that can be used for transmission of the 2nd-stage SCI in OFDM symbol $s$ , for $s = 0, 1, \dots, N_{sc}-1$ , in PSSCH transmission, where $N_{RE} = sl\_lengthSymbols - 2$ , where $sl\_lengthSymbols$ is the number of sidelink symbols within the slot provided by higher layers as defined in [6, TS 38.214]. $N_{RE}$ is the number of symbols for SL PRS provided by the higher layer parameter *numSym-SL-PRS-2ndStageSCI* if the 2nd-stage SCI is SCI format 2-D, and $N_{RE} = 0$ otherwise. If *startingSymbolFirst* and *startingSymbolSecond* are provided for the SL-BWP, $N_{RE} = numRefSymbolLength - 2$ , where *numRefSymbolLength* is provided by higher layers. If higher layer parameter *sl-PSFCH-Period* = 2 or 4, $N_{RE} = 3$ if "PSFCH overhead indication" field of SCI format 1-A indicates "1", and $N_{RE} = 0$ otherwise. If higher layer parameter *sl-PSFCH-Period* = 0, $N_{RE} = 0$ . If higher layer parameter *sl-PSFCH-Period* is 1, $N_{RE} = 0$ . +- $N_{RE}^{vacant} = N_{RE} - N_{sc}^{2nd}$ +- $N_{RE}^{vacant}$ is the number of vacant resource elements in the resource block to which the last coded symbol of the 2nd-stage SCI belongs. +- $R$ is the coding rate as indicated by "Modulation and coding scheme" field in SCI format 1-A. +- $\alpha$ is configured by higher layer parameter *sl-Scaling*. + +The input bit sequence to rate matching is $b$ , where $b$ is the number of coded bits. + +Rate matching is performed according to Clause 5.4.1 by setting $b = b$ . + +The output bit sequence after rate matching is denoted as $b$ , where $b$ and $b$ is modulation order of the 2nd-stage SCI. A UE is not expected to have $b > b$ . + +### 8.4.5 Multiplexing of coded 2nd-stage SCI bits to PSSCH + +The coded 2nd-stage SCI bits are multiplexed onto PSSCH according to the procedures in Clause 8.2.1. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-----------|------------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-05 | RAN1#89 | R1-1707082 | | | | Draft skeleton | 0.0.0 | +| 2017-07 | AH_NR2 | R1-1712014 | | | | Inclusion of LDPC related agreements | 0.0.1 | +| 2017-08 | RAN1#90 | R1-1714564 | | | | Inclusion of Polar coding related agreements | 0.0.2 | +| 2017-08 | RAN1#90 | R1-1714659 | | | | Endorsed version by RAN1#90 as basis for further updates | 0.1.0 | +| 2017-09 | RAN1#90 | R1-1715322 | | | | Capturing additional agreements on LDPC and Polar code from RAN1 #90 | 0.1.1 | +| 2017-09 | RAN#77 | RP-171991 | | | | For information to plenary | 1.0.0 | +| 2017-09 | RAN1#90 b | R1-1716928 | | | | Capturing additional agreements on LDPC and Polar code from RAN1 NR AH#3 | 1.0.1 | +| 2017-10 | RAN1#90 b | R1-1719106 | | | | Endorsed as v1.1.0 | 1.1.0 | +| 2017-11 | RAN1#91 | R1-1719225 | | | | Capturing additional agreements on channel coding, etc. | 1.1.1 | +| 2017-11 | RAN1#91 | R1-1719245 | | | | Capturing additional agreements on DCI format, channel coding, etc. | 1.1.2 | +| 2017-11 | RAN1#91 | R1-1721049 | | | | Endorsed as v1.2.0 | 1.2.0 | +| 2017-12 | RAN1#91 | R1-1721342 | | | | Capturing additional agreements on UCI, DCI, channel coding, etc. | 1.2.1 | +| 2017-12 | RAN#78 | RP-172668 | | | | Endorsed version for approval by plenary. | 2.0.0 | +| 2017-12 | RAN#78 | | | | | Approved by plenary - Rel-15 spec under change control | 15.0.0 | +| 2018-03 | RAN#79 | RP-180200 | 0001 | - | F | CR capturing the Jan18 ad-hoc and RAN1#92 meeting agreements | 15.1.0 | +| 2018-04 | RAN#79 | | | | | MCC: correction of typo in DCI format 0_1 (time domain resource assignment) - higher layer parameter should be pusch-AllocationList | 15.1.1 | +| 2018-06 | RAN#80 | RP-181172 | 0002 | 1 | F | CR to 38.212 capturing the RAN1#92bis and RAN1#93 meeting agreements | 15.2.0 | +| 2018-06 | RAN#80 | RP-181257 | 0003 | - | B | CR to 38.212 capturing the RAN1#92bis and RAN1#93 meeting agreements related to URLLC | 15.2.0 | +| 2018-09 | RAN#81 | RP-181789 | 0004 | - | F | CR to 38.212 capturing the RAN1#94 meeting agreements | 15.3.0 | +| 2018-12 | RAN#82 | RP-182523 | 0005 | 3 | F | Combined CR of all essential corrections to 38.212 from RAN1#94bis and RAN1#95 | 15.4.0 | +| 2019-03 | RAN#83 | RP-190448 | 0006 | - | F | Correction of wrong implementation on frequency domain resource assignment bitwidth | 15.5.0 | +| 2019-03 | RAN#83 | RP-190448 | 0008 | - | F | Correction to UCI multiplexing | 15.5.0 | +| 2019-03 | RAN#83 | RP-190448 | 0009 | - | F | Correction on DCI format 2_3 for SUL cell in TS 38.212 | 15.5.0 | +| 2019-03 | RAN#83 | RP-190448 | 0010 | - | F | Corrections to TS38.212 | 15.5.0 | +| 2019-03 | RAN#83 | RP-190448 | 0011 | - | F | On bitwidth calculation for DCI fields using RRC parameter indicating maximum number of MIMO layers per serving cell | 15.5.0 | +| 2019-03 | RAN#83 | RP-190448 | 0012 | - | F | CR on zero-padding of DCI 1_1 in cross-carrier scheduling case | 15.5.0 | +| 2019-03 | RAN#83 | RP-190448 | 0013 | - | F | Clarification on UL SUL indicator field and SRS request field | 15.5.0 | +| 2019-06 | RAN#84 | RP-191282 | 0014 | - | F | CR on correction to bitwidth of NNZC indicator | 15.6.0 | +| 2019-06 | RAN#84 | RP-191282 | 0015 | - | F | Correction on DCI size alignment in TS 38.212 | 15.6.0 | +| 2019-06 | RAN#84 | RP-191282 | 0016 | - | F | Correction on UL/SUL indicator in DCI format 0_0 | 15.6.0 | +| 2019-06 | RAN#84 | RP-191282 | 0017 | - | F | Corrections to 38.212 including alignment of terminology across specifications | 15.6.0 | +| 2019-06 | RAN#84 | RP-191282 | 0018 | - | F | CR on maximum modulation order configured for serving cell | 15.6.0 | +| 2019-06 | RAN#84 | RP-191282 | 0019 | 1 | F | Corrections to 38.212 including alignment of terminology across specifications from RAN1#97 | 15.6.0 | +| 2019-09 | RAN#85 | RP-191941 | 0020 | - | F | Corrections to 38.212 including alignment of terminology across specifications in RAN1#98 | 15.7.0 | +| 2019-12 | RAN#86 | RP-192625 | 0021 | - | F | CR on UL/SUL indicator in DCI format 0_1 | 15.8.0 | +| 2019-12 | RAN#86 | RP-192625 | 0022 | - | F | Corrections to 38.212 including alignment of terminology across specifications in RAN1#98bis and RAN1#99 | 15.8.0 | +| 2019-12 | RAN#86 | RP-192636 | 0023 | - | B | Introduction of NR based access to unlicensed spectrum into 38.212 | 16.0.0 | +| 2019-12 | RAN#86 | RP-192637 | 0024 | - | B | Introduction of IAB into 38.212 | 16.0.0 | +| 2019-12 | RAN#86 | RP-192638 | 0025 | - | B | Introduction of 5G V2X sidelink features into TS 38.212 | 16.0.0 | + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2019-12 | RAN#86 | RP-192639 | 0026 | - | B | Introduction of Physical Layer Enhancements for NR URLLC | 16.0.0 | +| 2019-12 | RAN#86 | RP-192641 | 0027 | - | B | Introduction of Enhancements on NR MIMO | 16.0.0 | +| 2019-12 | RAN#86 | RP-192642 | 0028 | - | B | Introduction of power saving in 38.212 | 16.0.0 | +| 2019-12 | RAN#86 | RP-192645 | 0029 | - | B | Introduction of MR DC/CA | 16.0.0 | +| 2019-12 | RAN#86 | RP-192643 | 0030 | - | B | Introduction of NR positioning support | 16.0.0 | +| 2019-12 | RAN#86 | RP-192635 | 0031 | - | B | Introduction of two-step RACH | 16.0.0 | +| 2020-03 | RAN#87-e | RP-200185 | 0032 | - | F | Corrections for Rel-16 NR-U after RAN1#100-e | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200190 | 0033 | - | F | Corrections for NR MIMO after RAN1#100-e | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200188 | 0034 | - | F | Corrections for URLLC after RAN1#100-e | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200191 | 0035 | - | F | Corrections for power saving after RAN1#100-e | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200187 | 0036 | - | F | Corrections on 5G V2X sidelink features after RAN1#100-e | 16.1.0 | +| 2020-06 | RAN#88-e | RP-200683 | 0038 | - | A | CR on L1-RSRP report on PUSCH | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200693 | 0039 | 1 | F | Corrections for power saving | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200689 | 0040 | 1 | F | Corrections on 5G V2X sidelink features after RAN1#100bis-e and RAN1#101-e | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200694 | 0041 | 1 | F | Corrections in TS 38.212 for NR positioning | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200692 | 0042 | 1 | F | Corrections in TS 38.212 for NR MIMO | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200696 | 0043 | - | F | Corrections for Rel-16 MR-DC/CA after RAN1#100bis-e | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200690 | 0044 | 1 | F | Corrections on NR eURLLC | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200687 | 0045 | 1 | F | Corrections for Rel-16 NR-U | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200688 | 0046 | - | F | Corrections for NR IAB | 16.2.0 | +| 2020-09 | RAN#89-e | RP-201814 | 0047 | - | F | Correction on UCI bit sequence generation | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201803 | 0049 | - | A | CR on PTRS for TS 38.212 | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201810 | 0050 | - | F | Alignment of RRC parameter ps-RNTI | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201813 | 0051 | - | F | CR to 38.212 on RRC parameter alignment for SCell dormancy | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201807 | 0052 | - | F | Corrections on 5G V2X sidelink features | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201809 | 0053 | - | F | Corrections to MIMO enhancements | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201805 | 0054 | - | F | Corrections to MIMO enhancements | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201808 | 0055 | - | F | Corrections on NR eURLLC | 16.3.0 | +| 2020-12 | RAN#90-e | RP-202390 | 0056 | - | F | RRC IE name fix to dynamic frequency domain resource allocation type selection (Rel-15 origin) | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202384 | 0057 | - | F | Correction on Transmission configuration indication in DCI format 1_2 | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202398 | 0058 | - | F | Alignment CR for TS 38.212 | 16.4.0 | +| 2021-03 | RAN#91-e | RP-210052 | 0059 | - | F | CR on DMRS | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210049 | 0060 | - | F | Correction to description of FDRA field size in DCI 0_0 | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210049 | 0061 | - | F | Correction to description of FDRA field interpretation in DCI 0_1 | 16.5.0 | + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2021-03 | RAN#91-e | RP-210050 | 0062 | - | F | Correction on Sidelink Broadcast channel | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210049 | 0063 | - | F | Correction on LBT Type and CP Extension Indication for Semi-Static Channel Occupancy | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210059 | 0064 | - | F | Alignment CR for TS 38.212 | 16.5.0 | +| 2021-06 | RAN#92-e | RP-211252 | 0066 | - | F | 38.212 CR on DAI size determination for DCI format 1_1/1-2 in CA | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211236 | 0067 | - | F | Corrections on parameter of MCS table set to qam256 | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211234 | 0068 | - | D | Alignment CR for TS 38.212 (post RAN1#104bis-e) | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211234 | 0069 | - | F | Correction on HARQ-ACK codebook RRC parameter | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211236 | 0070 | - | F | Correction on SRS resource set configuration in TS 38.212 | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211243 | 0071 | - | F | Alignment CR for TS 38.212 (post RAN1#105-e) | 16.6.0 | +| 2021-09 | RAN#93-e | RP-211843 | 0072 | - | F | Correction on SRS resource set configuration for DCI format 0_2 in TS 38.212 | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211841 | 0074 | - | A | Rel-15 editorial corrections for TS 38.212 (mirrored to Rel-16) | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211850 | 0075 | - | F | Alignment CR for TS 38.212 | 16.7.0 | +| 2021-12 | RAN#94-e | RP-212959 | 0076 | - | F | Correction on mapping between priority field value and priority value in SCI format 1-A | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212961 | 0077 | - | F | Changes of channel access types tables in TS 38.212 | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212961 | 0078 | - | F | Corrections on CG-UCI multiplexing in TS38.212 | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212958 | 0080 | - | A | Clarify UCI bitwidth and UCI mapping order for non-PMI based CSI feedback | 16.8.0 | +| 2021-12 | RAN#94-e | RP-213238 | 0081 | - | F | Clarification on KNZ to codepoint mapping for eType II CSI | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212958 | 0083 | - | A | Rel-15 editorial corrections for TS 38.212 (mirrored to Rel-16) | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212964 | 0084 | - | F | Alignment CR for TS 38.212 | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212967 | 0085 | - | B | Introduction of features to extend current NR operation to 71 GHz | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212982 | 0086 | - | B | Introduction of NR DL 1024QAM for FR1 | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212973 | 0087 | - | B | Introduction of Coverage Enhancements | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212979 | 0088 | - | B | Introduction of NR Multicast and Broadcast Services | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212966 | 0089 | - | B | Introduction of Further enhancements on MIMO for NR | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212969 | 0090 | - | B | Introduction of NR non-terrestrial networks (NTN) | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212972 | 0091 | - | B | Introduction of Rel-17 UE power saving enhancements | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212968 | 0092 | - | B | Introduction of Rel-17 enhanced IloT and URLLC | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212980 | 0093 | - | B | Introduction of NR dynamic spectrum sharing enhancements | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212978 | 0094 | - | B | Introduction of NR sidelink enhancement | 17.0.0 | +| 2022-03 | RAN#95-e | RP-220269 | 0096 | - | A | Correction of NZC partitioning in eType II CSI | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220248 | 0098 | - | A | Correction on Rel-16 UE dormancy adaptation | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220252 | 0099 | - | F | Corrections on enhanced IloT and URLLC in 38.212 | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220262 | 0100 | - | F | Corrections on NR sidelink enhancement in 38.212 | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220257 | 0101 | - | F | Corrections on coverage enhancements in 38.212 | 17.1.0 | + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|---------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-03 | RAN#95-e | RP-220263 | 0102 | - | F | Corrections on NR Multicast and Broadcast Services in 38.212 | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220256 | 0103 | - | F | Corrections on UE power saving enhancements in 38.212 | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220251 | 0104 | - | F | Correction on extension of current NR operation to 71 GHz in 38.212 | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220264 | 0105 | - | F | Corrections on NR dynamic spectrum sharing enhancements in 38.212 | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220250 | 0106 | - | F | Corrections on Further enhancements on MIMO for NR in TS 38.212 | 17.1.0 | +| 2022-06 | RAN#96 | RP-221617 | 0108 | - | A | Clarification of TPMI indication for UL full power transmission | 17.2.0 | +| 2022-06 | RAN#96 | RP-221602 | 0109 | - | F | Corrections on enhanced IloT and URLLC in 38.212 | 17.2.0 | +| 2022-06 | RAN#96 | RP-221612 | 0110 | - | F | Corrections on NR Multicast and Broadcast Services in 38.212 | 17.2.0 | +| 2022-06 | RAN#96 | RP-221606 | 0111 | - | F | Corrections on UE power saving enhancements in 38.212 | 17.2.0 | +| 2022-06 | RAN#96 | RP-221601 | 0112 | - | F | Correction on extension of current NR operation to 71 GHz in 38.212 | 17.2.0 | +| 2022-06 | RAN#96 | RP-221600 | 0113 | - | F | Corrections on Further enhancements on MIMO for NR in TS 38.212 | 17.2.0 | +| 2022-06 | RAN#96 | RP-221599 | 0115 | - | A | Rel-16 editorial corrections for TS 38.212 (mirrored to Rel-17) | 17.2.0 | +| 2022-09 | RAN#97-e | RP-222403 | 0116 | 1 | F | CR on DCI size for Rel-17 NTN HARQ in 38.212 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222400 | 0117 | - | F | CR on the description of the SRS resource set indication for PUSCH repetition | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222401 | 0118 | - | F | CR on ChannelAccess-Cpext in Fallback DCI | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222413 | 0119 | - | F | CR on DCI size alignment for Cross-carrier scheduling from SCell to PCell | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222406 | 0120 | - | F | Corrections on UE Power Saving Enhancements for NR in TS 38.212 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222412 | 0121 | - | F | Corrections on NR Multicast and Broadcast Services in 38.212 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222411 | 0122 | - | F | Correction on NR sidelink enhancement | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222422 | 0123 | - | F | Rel-17 editorial corrections for TS 38.212 | 17.3.0 | +| 2022-12 | RAN#98-e | RP-222863 | 0124 | - | F | Corrections on resource pool index | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222853 | 0125 | - | F | CR on channel access type indication in non-fallback DCI | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222853 | 0126 | - | F | Correction to support up to 32 HARQ process numbers for FR2-2 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222853 | 0127 | - | F | Correction on TDRA for multiple PUSCH scheduling in TS 38.212 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222854 | 0128 | - | F | CR on priority of CG-UCI | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0129 | - | F | CR on number of HARQ-ACK codebooks configurable for multicast | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222865 | 0130 | - | F | CR on DCI size alignment for Cross-carrier scheduling from SCell to PCell | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222868 | 0131 | 1 | F | Rel-17 editorial corrections for TS 38.212 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222858 | 0132 | - | F | Correction on the short message indicator when TRS availability indication is present | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0133 | - | F | CR on format 4_0 DCI size alignment in SCell | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222870 | 0134 | - | F | CR on CSI reporting | 17.4.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-03 | RAN#99 | RP-230451 | 0135 | - | F | CR on aligning DCI sizes when configuring two HARQ-ACK codebooks for multicast | 17.5.0 | +| 2023-03 | RAN#99 | RP-230443 | 0136 | - | F | Corrections on intra-UE multiplexing and semi-static channel occupancy | 17.5.0 | +| 2023-03 | RAN#99 | RP-230442 | 0137 | - | F | CR on DCI field sizes for multiple PDSCHEs scheduled by single DCI | 17.5.0 | +| 2023-03 | RAN#99 | RP-230442 | 0138 | - | F | Corrections to ChanneAccess-CPext field in DCI formats x_2 in TS38.212 | 17.5.0 | +| 2023-03 | RAN#99 | RP-230440 | 0140 | - | A | Rel-16 editorial corrections for TS 38.212 (mirrored to Rel-17) | 17.5.0 | +| 2023-03 | RAN#99 | RP-230453 | 0141 | - | F | Rel-17 editorial corrections for TS 38.212 | 17.5.0 | +| 2023-09 | RAN#101 | RP-232445 | 0142 | - | F | Correction for the mapping of rank combination value for Rel-17 NCJT CSI | 17.6.0 | +| 2023-09 | RAN#101 | RP-232531 | 0143 | - | F | Rel-17 editorial corrections for TS 38.212 | 17.6.0 | +| 2023-09 | RAN#101 | RP-232471 | 0144 | - | B | Introduction of Rel-18 Multi-carrier enhancements | 18.0.0 | +| 2023-09 | RAN#101 | RP-232458 | 0145 | - | B | Introduction of Rel-18 MIMO Evolution for Downlink and Uplink | 18.0.0 | +| 2023-09 | RAN#101 | RP-232473 | 0146 | - | B | Introduction of Rel-18 Further NR mobility enhancements | 18.0.0 | +| 2023-09 | RAN#101 | RP-232474 | 0147 | - | B | Introduction of Rel-18 NR NTN enhancements | 18.0.0 | +| 2023-09 | RAN#101 | RP-232480 | 0148 | - | B | Introduction of NR positioning enhancement in Rel-18 | 18.0.0 | +| 2023-09 | RAN#101 | RP-232469 | 0149 | - | B | Introduction of Rel-18 NR sidelink evolution | 18.0.0 | +| 2023-09 | RAN#101 | RP-232479 | 0150 | - | B | Introduction of Rel-18 network controlled repeaters | 18.0.0 | +| 2023-09 | RAN#101 | RP-232481 | 0151 | - | B | Introduction of Rel-18 network energy saving for NR | 18.0.0 | +| 2023-09 | RAN#101 | RP-232472 | 0152 | - | B | Introduction of Rel-18 further NR Coverage enhancement | 18.0.0 | +| 2023-09 | RAN#101 | RP-232477 | 0154 | - | B | Introduction of Rel-18 NR support for dedicated spectrum less than 5MHz for FR1 | 18.0.0 | +| 2023-09 | RAN#101 | RP-232482 | 0155 | - | B | Introduction of Rel-18 XR enhancements for NR | 18.0.0 | +| 2023-12 | RAN#102 | RP-233703 | 0158 | 1 | A | Correction on the rate matching when HARQ-ACK multiplexed with CG-PUSCH | 18.1.0 | +| 2023-12 | RAN#102 | RP-233727 | 0160 | - | A | Correction on CSI reporting for 1 CSI-RS port | 18.1.0 | +| 2023-12 | RAN#102 | RP-233728 | 0162 | - | A | Rel-17 editorial corrections for TS 38.212 (mirrored to Rel-18) | 18.1.0 | +| 2023-12 | RAN#102 | RP-233719 | 0163 | - | F | Corrections on NR positioning enhancement in 38.212 | 18.1.0 | +| 2023-12 | RAN#102 | RP-233706 | 0164 | - | F | Corrections on Rel-18 NR sidelink evolution in 38.212 | 18.1.0 | +| 2023-12 | RAN#102 | RP-233709 | 0165 | - | F | Corrections on Rel-18 further NR Coverage enhancement in 38.212 | 18.1.0 | +| 2023-12 | RAN#102 | RP-233710 | 0166 | - | F | Corrections on Rel-18 Further NR mobility enhancements in 38.212 | 18.1.0 | +| 2023-12 | RAN#102 | RP-233705 | 0167 | - | F | Corrections on Rel-18 MIMO Evolution for Downlink and Uplink in 38.212 | 18.1.0 | +| 2023-12 | RAN#102 | RP-233708 | 0168 | - | F | Corrections on Rel-18 Multi-carrier enhancements in 38.212 | 18.1.0 | +| 2023-12 | RAN#102 | RP-233720 | 0169 | - | F | Corrections on Rel-18 network energy saving for NR in 38.212 | 18.1.0 | +| 2023-12 | RAN#102 | RP-233714 | 0170 | - | F | Corrections on Rel-18 NR NTN enhancements in 38.212 | 18.1.0 | +| 2023-12 | RAN#102 | RP-233721 | 0171 | - | F | Corrections on Rel-18 XR enhancements for NR in 38.212 | 18.1.0 | +| 2023-12 | RAN#102 | RP-233729 | 0172 | - | B | Introduction of Rel-18 NR demodulation performance evolution | 18.1.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|----------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-12 | RAN#102 | RP-233733 | 0173 | - | B | Introduction of Rel-18 enhancements of NR Multicast and Broadcast Services | 18.1.0 | +| 2023-12 | RAN#102 | RP-233718 | 0174 | - | F | Corrections on Rel-18 network controlled repeaters in 38.212 | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38213/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38213/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..417e8e4e8821810385005ea05425b8aec026d4c4 --- /dev/null +++ b/marked/Rel-18/38_series/38213/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79989817725afe1cb0b78e25c1e40dc0f80f5cba632809ff52bccd5d8dd468a9 +size 9459 diff --git a/marked/Rel-18/38_series/38213/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38213/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fad95fc5ba2b81903d9fb11786e46e8aab46029 --- /dev/null +++ b/marked/Rel-18/38_series/38213/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18fd2e4a577e1c9b6e5a6e49a801b5c7c4498a159384bbbc2201f924af9567dd +size 6206 diff --git a/marked/Rel-18/38_series/38213/raw.md b/marked/Rel-18/38_series/38213/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..645840e1b1d78546e97cfbedbec40aa8d2c7e589 --- /dev/null +++ b/marked/Rel-18/38_series/38213/raw.md @@ -0,0 +1,9031 @@ + + +# 3GPP TS 38.213 V18.1.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (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, New 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 + + +**3GPP** + +# Contents + +| | | +|-------------------------------------------------------------------|----| +| Foreword..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms, symbols and abbreviations..... | 8 | +| 3.1 Terms..... | 8 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations..... | 8 | +| 4 Synchronization procedures..... | 10 | +| 4.1 Cell search..... | 10 | +| 4.2 Transmission timing adjustments..... | 13 | +| 4.3 Timing for secondary cell activation / deactivation..... | 15 | +| 5 Radio link monitoring..... | 15 | +| 6 Link recovery procedures..... | 16 | +| 7 Uplink Power control..... | 22 | +| 7.1 Physical uplink shared channel..... | 23 | +| 7.1.1 UE behaviour..... | 24 | +| 7.2 Physical uplink control channel..... | 37 | +| 7.2.1 UE behaviour..... | 37 | +| 7.3 Sounding reference signals..... | 42 | +| 7.3.1 UE behaviour..... | 42 | +| 7.4 Physical random access channel..... | 46 | +| 7.5 Prioritizations for transmission power reductions..... | 47 | +| 7.6 Dual connectivity..... | 48 | +| 7.6.1 EN-DC..... | 48 | +| 7.6.1A NE-DC..... | 49 | +| 7.6.2 NR-DC..... | 50 | +| 7.7 Power headroom report..... | 51 | +| 7.7.1 Type 1 PH report..... | 52 | +| 7.7.2 Type 2 PH report..... | 55 | +| 7.7.3 Type 3 PH report..... | 55 | +| 8 Random access procedure..... | 55 | +| 8.1 Random access preamble..... | 56 | +| 8.1A PUSCH for Type-2 random access procedure..... | 60 | +| 8.2 Random access response - Type-1 random access procedure..... | 62 | +| 8.2A Random access response - Type-2 random access procedure..... | 64 | +| 8.3 PUSCH scheduled by RAR UL grant..... | 65 | +| 8.4 PDSCH with UE contention resolution identity..... | 67 | +| 9 UE procedure for reporting control information..... | 68 | +| 9.A PUCCH cell switching..... | 77 | + +# 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 + +| | | | +|---------|-------------------------------------------------------------------------------------------------------------------------|-----| +| 9.1 | HARQ-ACK codebook determination..... | 78 | +| 9.1.1 | CBG-based HARQ-ACK codebook determination..... | 79 | +| 9.1.2 | Type-1 HARQ-ACK codebook determination..... | 80 | +| 9.1.2.1 | Type-1 HARQ-ACK codebook in physical uplink control channel..... | 82 | +| 9.1.2.2 | Type-1 HARQ-ACK codebook in physical uplink shared channel..... | 94 | +| 9.1.3 | Type-2 HARQ-ACK codebook determination..... | 96 | +| 9.1.3.1 | Type-2 HARQ-ACK codebook in physical uplink control channel..... | 97 | +| 9.1.3.2 | Type-2 HARQ-ACK codebook in physical uplink shared channel..... | 111 | +| 9.1.3.3 | Type-2 HARQ-ACK codebook grouping and HARQ-ACK retransmission..... | 112 | +| 9.1.4 | Type-3 HARQ-ACK codebook determination..... | 115 | +| 9.1.5 | HARQ-ACK codebook retransmission..... | 119 | +| 9.2 | UCI reporting in physical uplink control channel..... | 121 | +| 9.2.1 | PUCCH Resource Sets..... | 121 | +| 9.2.2 | PUCCH Formats for UCI transmission..... | 125 | +| 9.2.3 | UE procedure for reporting HARQ-ACK..... | 127 | +| 9.2.4 | UE procedure for reporting SR..... | 130 | +| 9.2.5 | UE procedure for reporting multiple UCI types..... | 131 | +| 9.2.5.0 | UE procedure for prioritization between SL HARQ-ACK information in a PUCCH and DL HARQ-ACK or SR or CSI in a PUCCH..... | 136 | +| 9.2.5.1 | UE procedure for multiplexing HARQ-ACK or CSI and SR in a PUCCH..... | 137 | +| 9.2.5.2 | UE procedure for multiplexing HARQ-ACK/SR/CSI in a PUCCH..... | 138 | +| 9.2.5.3 | UE procedure for reporting UCI of different priorities..... | 142 | +| 9.2.5.4 | UE procedure for deferring HARQ-ACK for SPS PDSCH..... | 143 | +| 9.2.6 | PUCCH repetition procedure..... | 144 | +| 9.3 | UCI reporting in physical uplink shared channel..... | 147 | +| 9.3.1 | UE procedure for reporting UTO-UCI..... | 152 | +| 10 | UE procedure for receiving control information..... | 152 | +| 10.1 | UE procedure for determining physical downlink control channel assignment..... | 166 | +| 10.1.1 | Self-carrier and cross-carrier scheduling on the primary cell..... | 188 | +| 10.2 | PDCCH validation for DL SPS and UL grant Type 2..... | 189 | +| 10.2A | PDCCH validation for SL configured grant Type 2..... | 191 | +| 10.3 | PDCCH monitoring indication and dormancy/non-dormancy behaviour for SCells..... | 191 | +| 10.4 | Search space set group switching and skipping of PDCCH monitoring..... | 194 | +| 10.4A | PDCCH monitoring for early indication of paging..... | 199 | +| 10.4B | Indication of TRS resources..... | 200 | +| 10.5 | HARQ-ACK information for PUSCH transmissions..... | 200 | +| 11 | UE-group common signalling..... | 201 | +| 11.1 | Slot configuration..... | 201 | +| 11.1.1 | UE procedure for determining slot format..... | 206 | +| 11.2 | Interrupted transmission indication..... | 213 | +| 11.2A | Cancellation indication..... | 214 | +| 11.3 | Group TPC commands for PUCCH/PUSCH..... | 215 | +| 11.4 | SRS switching..... | 216 | +| 11.5 | Adaptation of cell operation..... | 216 | +| 12 | Bandwidth part operation..... | 217 | +| 13 | UE procedure for monitoring Type0-PDCCH CSS sets..... | 220 | +| 14 | Integrated access-backhaul operation..... | 234 | +| 15 | Dual active protocol stack based handover..... | 241 | +| 16 | UE procedures for sidelink..... | 242 | +| 16.1 | Synchronization procedures..... | 243 | +| 16.2 | Power control..... | 246 | +| 16.2.0 | S-SS/PSBCH blocks..... | 246 | +| 16.2.1 | PSSCH..... | 246 | +| 16.2.2 | PSCCH..... | 248 | +| 16.2.3 | PSFCH..... | 248 | +| 16.2.3A | SL PRS..... | 252 | +| 16.2.4 | Prioritization of transmissions/receptions..... | 253 | + +| | | | +|-----------------|----------------------------------------------------------------------------|------------| +| 16.2.4.1 | Simultaneous NR and E-UTRA transmission/reception..... | 253 | +| 16.2.4.2 | Simultaneous PSFCH transmission/reception..... | 254 | +| 16.2.4.3 | Simultaneous SL and UL transmissions/receptions..... | 254 | +| 16.2.4.3.1 | Prioritizations for sidelink and uplink transmissions/receptions..... | 255 | +| 16.2.5 | SL Carrier Aggregation..... | 256 | +| 16.3 | UE procedure for reporting and obtaining control information in PSFCH..... | 257 | +| 16.3.0 | UE procedure for transmitting PSFCH with control information..... | 257 | +| 16.3.1 | UE procedure for receiving PSFCH with control information..... | 261 | +| 16.4 | UE procedure for transmitting PSCCH..... | 263 | +| 16.4A | UE procedure for transmitting PSCCH in dedicated SL PRS resource pool..... | 264 | +| 16.5 | UE procedure for reporting HARQ-ACK on uplink..... | 265 | +| 16.5.1 | Type-1 HARQ-ACK codebook determination..... | 267 | +| 16.5.1.1 | Type-1 HARQ-ACK codebook in physical uplink control channel..... | 268 | +| 16.5.1.2 | Type-1 HARQ-ACK codebook in physical uplink shared channel..... | 269 | +| 16.5.2 | Type-2 HARQ-ACK codebook determination..... | 270 | +| 16.5.2.1 | Type-2 HARQ-ACK codebook in physical uplink control channel..... | 270 | +| 16.5.2.2 | Type-2 HARQ-ACK codebook in physical uplink shared channel..... | 272 | +| 16.6 | UE procedure for LTE sidelink transmission..... | 273 | +| 16.7 | Operation for in-device coexistence and for co-channel coexistence..... | 273 | +| 17 | UE with reduced capabilities..... | 273 | +| 17.1 | First procedures for RedCap UE..... | 273 | +| 17.1A | Second procedures for RedCap UE..... | 275 | +| 17.2 | Half-Duplex UE in paired spectrum..... | 276 | +| 18 | Multicast Broadcast Services..... | 277 | +| 19 | PUSCH transmission in RRC_INACTIVE state..... | 282 | +| 19.1 | Configured-grant based PUSCH transmission..... | 282 | +| 19.2 | Random-access based PUSCH transmission..... | 284 | +| 20 | Network controlled repeater..... | 284 | +| 21 | L1/L2-triggered mobility procedures..... | 286 | +| Annex A: | Change history..... | 288 | + +# --- 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 control operations in 5G-NR. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications" +- [2] 3GPP TS 38.201: "NR; Physical Layer – General Description" +- [3] 3GPP TS 38.202: "NR; Services provided by the physical layer" +- [4] 3GPP TS 38.211: "NR; Physical channels and modulation" +- [5] 3GPP TS 38.212: "NR; Multiplexing and channel coding" +- [6] 3GPP TS 38.214: "NR; Physical layer procedures for data" +- [7] 3GPP TS 38.215: "NR; Physical layer measurements" +- [8-1] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone" +- [8-2] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone" +- [8-3] 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" +- [8-4] 3GPP TS 38.101-4: "NR; User Equipment (UE) radio transmission and reception; Part 4: Performance requirements" +- [9] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception" +- [10] 3GPP TS 38.133: "NR; Requirements for support of radio resource management" +- [11] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification" +- [12] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification" +- [13] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures" +- [14] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification" +- [15] 3GPP TS 37.213: "Physical layer procedures for shared spectrum channel access" +- [16] 3GPP TS 38.473: "F1 application protocol (F1AP)" +- [17] 3GPP TS 38.304: "NR; User Equipment (UE) procedures in Idle mode and RRC Inactive state" +- [18] 3GPP TS 38.306: "NR; User Equipment (UE) radio access capabilities" +- [19] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description" +- [20] 3GPP TS 38.106: "NR; NR Repeater Radio Transmission and Reception" + +# 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms and definitions given in [1, TR 21.905] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in [1, TR 21.905]. A parameter referenced in *italics* is provided by higher layers. + +## 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 [1, TR 21.905]. + +| | | +|-----------|--------------------------------------------------------------------| +| BPRE | Bits Per Resource Element | +| BWP | Bandwidth Part | +| CB | Code Block | +| CBG | Code Block Group | +| CBR | Channel Busy Ratio | +| CCE | Control Channel Element | +| CORESET | Control Resource Set | +| CP | Cyclic Prefix | +| CRC | Cyclic Redundancy Check | +| C-RNTI | Cell RNTI | +| CS-RNTI | Configured Scheduling RNTI | +| CSI | Channel State Information | +| CSS | Common Search Space | +| DAI | Downlink Assignment Index | +| DAPS | Dual Active Protocol Stack | +| DC | Dual Connectivity | +| DCI | Downlink Control Information | +| DL | Downlink | +| DL-SCH | Downlink Shared Channel | +| EPRE | Energy Per Resource Element | +| EN-DC | E-UTRA NR Dual Connectivity with MCG using E-UTRA and SCG using NR | +| FR1 | Frequency Range 1 | +| FR2 | Frequency Range 2 | +| G-CS-RNTI | Group Configured Scheduling RNTI | +| G-RNTI | Group RNTI | +| GSCN | Global Synchronization Channel Number | +| HARQ-ACK | Hybrid Automatic Repeat reQuest Acknowledgement | +| MBS | Multicast Broadcast Services | +| MCG | Master Cell Group | +| MCS | Modulation and Coding Scheme | +| NCR | Network-controlled Repeater | +| NCR-Fwd | NCR Forwarding | +| NCR-MT | NCR Mobile Termination | +| NDI | New Data Indicator | +| NE-DC | NR E-UTRA Dual Connectivity with MCG using NR and SCG using E-UTRA | +| NR-DC | NR NR Dual Connectivity | +| PBCH | Physical Broadcast Channel | +| PCell | Primary Cell | +| PDCCH | Physical Downlink Control Channel | +| PDSCH | Physical Downlink Shared Channel | +| PO | Paging Occasion | +| PRACH | Physical Random Access Channel | + +| | | +|--------------|---------------------------------------| +| PRB | Physical Resource Block | +| PRG | Physical Resource block Group | +| PSCell | Primary Secondary Cell | +| PSBCH | Physical Sidelink Broadcast Channel | +| PSCCH | Physical Sidelink Control Channel | +| PSFCH | Physical Sidelink Feedback Channel | +| PSS | Primary Synchronization Signal | +| PSSCH | Physical Sidelink Shared Channel | +| PUCCH | Physical Uplink Control Channel | +| PUCCH-SCell | PUCCH SCell | +| PUCCH-sSCell | PUCCH switching SCell | +| PUSCH | Physical Uplink Shared Channel | +| QCL | Quasi Co-Location | +| RB | Resource Block | +| RE | Resource Element | +| RLM | Radio Link Monitoring | +| RRM | Radio Resource Management | +| RS | Reference Signal | +| RSRP | Reference Signal Received Power | +| SCG | Secondary Cell Group | +| SCI | Sidelink Control Information | +| SCS | Subcarrier Spacing | +| SFCI | Sidelink Feedback Control Information | +| SFN | System Frame Number | +| SL | Sidelink | +| SLIV | Start and Length Indicator Value | +| SL PRS | Sidelink Positioning Reference Signal | +| SPS | Semi-Persistent Scheduling | +| SR | Scheduling Request | +| SRI | SRS Resource Indicator | +| SRS | Sounding Reference Signal | +| SSS | Secondary Synchronization Signal | +| SSSG | Search Space Set Group | +| TA | Timing Advance | +| TAG | Timing Advance Group | +| TB | Transport Block | +| TBG | Transport Block Group | +| TCI | Transmission Configuration Indicator | +| TO | Transmission Occasion | +| UCI | Uplink Control Information | +| UE | User Equipment | +| UL | Uplink | +| UL-SCH | Uplink Shared Channel | +| USS | UE-specific Search Space | +| UTO-UCI | Unused Transmission Occasion - UCI | + +# 4 Synchronization procedures + +## 4.1 Cell search + +Cell search is the procedure for a UE to acquire time and frequency synchronization with a cell and to detect the physical layer Cell ID of the cell. + +A UE receives the following synchronization signals (SS) in order to perform cell search: the primary synchronization signal (PSS) and secondary synchronization signal (SSS) as defined in [4, TS 38.211]. + +A UE assumes that reception occasions of a physical broadcast channel (PBCH), PSS, and SSS are in consecutive symbols, as defined in [4, TS 38.211], and form a SS/PBCH block. The UE assumes that SSS, PBCH DM-RS, and PBCH data have same EPRE. The UE may assume that the ratio of PSS EPRE to SSS EPRE in a SS/PBCH block is either 0 dB or 3 dB. If the UE has not been provided dedicated higher layer parameters, the UE may assume that the ratio of PDCCH DMRS EPRE to SSS EPRE is within -8 dB and 8 dB when the UE monitors PDCCHs for a DCI format 1\_0 with CRC scrambled by SI-RNTI, P-RNTI, or RA-RNTI, or for a DCI format 2\_7, or for a DCI format 4\_0. + +For a half frame with SS/PBCH blocks, the first symbol indexes for candidate SS/PBCH blocks are determined according to the SCS of SS/PBCH blocks as follows, where index 0 corresponds to the first symbol of the first slot in a half-frame. + +- Case A - 15 kHz SCS: the first symbols of the candidate SS/PBCH blocks have indexes of . + - For operation without shared spectrum channel access: + - For carrier frequencies smaller than or equal to 3 GHz, . + - For carrier frequencies within FR1 larger than 3 GHz, . + - For operation with shared spectrum channel access, as described in [15, TS 37.213], . +- Case B - 30 kHz SCS: the first symbols of the candidate SS/PBCH blocks have indexes . For carrier frequencies smaller than or equal to 3 GHz, . For carrier frequencies within FR1 larger than 3 GHz, . +- Case C - 30 kHz SCS: the first symbols of the candidate SS/PBCH blocks have indexes . + - For operation without shared spectrum channel access + - For paired spectrum operation + - For carrier frequencies smaller than or equal to 3 GHz, . For carrier frequencies within FR1 larger than 3 GHz, . + - For unpaired spectrum operation + - For carrier frequencies smaller than 1.88 GHz, . For carrier frequencies within FR1 equal to or larger than 1.88 GHz, . + - For operation with shared spectrum channel access, . +- Case D - 120 kHz SCS: the first symbols of the candidate SS/PBCH blocks have indexes . For carrier frequencies within FR2, . +- Case E - 240 kHz SCS: the first symbols of the candidate SS/PBCH blocks have indexes . For carrier frequencies within FR2-1, . +- Case F - 480 kHz SCS: the first symbols of the candidate SS/PBCH blocks have indexes . For carrier frequencies within FR2-2, . +- Case G - 960 kHz SCS: the first symbols of the candidate SS/PBCH blocks have indexes . For carrier frequencies within FR2-2, . + +From the above cases, if the SCS of SS/PBCH blocks is not provided by *ssbSubcarrierSpacing*, the applicable cases for a cell depend on a respective frequency band, as provided in [8-1, TS 38.101-1] and [8-2, TS 38.101-2]. A same case applies for all SS/PBCH blocks on the cell. If a 30 kHz SS/PBCH block SCS is indicated by *ssbSubcarrierSpacing*, Case B applies for frequency bands with only 15 kHz SS/PBCH block SCS as specified in [8-1, TS 38.101-1], and the case specified for 30 kHz SS/PBCH block SCS in [8-1, TS 38.101-1] applies for frequency bands with 30 kHz SS/PBCH block SCS or both 15 kHz and 30 kHz SS/PBCH block SCS as specified in [8-1, TS 38.101-1]. For a UE configured to operate with carrier aggregation over a set of cells in a frequency band of FR2 or with frequency-contiguous carrier aggregation over a set of cells in a frequency band of FR1, if the UE is provided SCS values by *ssbSubcarrierSpacing* for receptions of SS/PBCH blocks on any cells from the set of cells, the UE expects the SCS values to be same. + +The candidate SS/PBCH blocks in a half frame are indexed in an ascending order in time from 0 to $L-1$ , where $L$ is determined according to SS/PBCH block patterns for Cases A through G. $L$ is a maximum number of SS/PBCH block indexes in a cell, and the maximum number of transmitted SS/PBCH blocks within a half frame is $L$ . + +- For operation without shared spectrum channel access in FR1 and FR2, and for operation with shared spectrum channel access in FR2-2, +- For operation with shared spectrum channel access in FR1, for 15 kHz SCS of SS/PBCH blocks and for 30 kHz SCS of SS/PBCH blocks + +For $L > 4$ , a UE determines the 2 LSB bits of a candidate SS/PBCH block index per half frame from a one-to-one mapping with an index of the DM-RS sequence transmitted in the PBCH as described in [4, TS 38.211]. + +For $L > 8$ , a UE determines the 3 LSB bits of a candidate SS/PBCH block index per half frame from a one-to-one mapping with an index of the DM-RS sequence transmitted in the PBCH as described in [4, TS 38.211] + +- for $L > 4$ , the UE determines the 1 MSB bit of the candidate SS/PBCH block index from PBCH payload bit $b_0$ as described in [5, TS 38.212] +- for $L > 8$ , the UE determines the 2 MSB bits of the candidate SS/PBCH block index from PBCH payload bits $b_0$ and $b_1$ as described in [5, TS 38.212] +- for $L > 16$ , the UE determines the 3 MSB bits of the candidate SS/PBCH block index from PBCH payload bits $b_0$ , $b_1$ and $b_2$ as described in [5, TS 38.212] + +A UE can be provided per serving cell by *ssb-periodicityServingCell* a periodicity of the half frames for reception of the SS/PBCH blocks for the serving cell. If the UE is not configured a periodicity of the half frames for receptions of the SS/PBCH blocks, the UE assumes a periodicity of a half frame. A UE assumes that the periodicity is same for all SS/PBCH blocks in the serving cell. + +For initial cell selection, a UE may assume that half frames with SS/PBCH blocks occur with a periodicity of 2 frames. + +For operation without shared spectrum channel access, an SS/PBCH block index is same as a candidate SS/PBCH block index. + +For operation with shared spectrum channel access, a UE assumes that transmission of SS/PBCH blocks in a half frame is within a discovery burst transmission window that starts from the first symbol of the first slot in a half-frame. The UE can be provided per serving cell by *discoveryBurstWindowLength* a duration of the discovery burst transmission window. If *discoveryBurstWindowLength* is not provided, the UE assumes that the duration of the discovery burst transmission window is a half frame. For a serving cell, the UE assumes that a periodicity of the discovery burst transmission window is same as a periodicity of half frames for receptions of SS/PBCH blocks in the serving cell. The UE assumes that one or more SS/PBCH blocks indicated by *ssb-PositionsInBurst* may be transmitted within the discovery burst transmission window and have candidate SS/PBCH blocks indexes corresponding to SS/PBCH block indexes provided by *ssb-PositionsInBurst*. If MSB $b_0$ of *ssb-PositionsInBurst* is set to 1, the UE assumes that SS/PBCH block(s) within the discovery burst transmission window with candidate SS/PBCH block index(es) corresponding to SS/PBCH block index equal to $i$ may be transmitted; if MSB $b_0$ is set to 0, the UE assumes that the SS/PBCH block(s) are not transmitted. If MSB $b_0$ of *inOneGroup* is set to 1, and MSB $b_0$ of *groupPresence* is set to 1, the UE assumes that SS/PBCH block(s) within the discovery burst transmission window with candidate SS/PBCH block index(es) corresponding to SS/PBCH block index determined by $i$ and $j$ may be transmitted; otherwise, the UE assumes that the SS/PBCH block(s) are not transmitted. + +For operation with shared spectrum channel access in FR1, a UE assumes that SS/PBCH blocks in a serving cell that are within a same discovery burst transmission window or across discovery burst transmission windows are quasi co-located with respect to average gain, quasi co-location 'typeA' and 'typeD' properties, when applicable [6, TS 38.214], if a value of $\Delta$ is same among the SS/PBCH blocks. $\Delta$ is an index of a DM-RS sequence transmitted in a PBCH of a corresponding SS/PBCH block, and $\Delta$ is either provided by *ssb-PositionQCL* or, if *ssb-PositionQCL* is not provided, obtained from a *MIB* provided by a SS/PBCH block according to Table 4.1-1 with $\Delta$ [4, TS 38.211]. The UE can determine an SS/PBCH block index according to $\Delta$ , or according to $\Delta$ where $\Delta$ is the candidate SS/PBCH block index. The UE assumes that within a discovery burst transmission window, a number of transmitted SS/PBCH blocks on a serving cell is not larger than $\Delta$ and a number of transmitted SS/PBCH blocks with a same SS/PBCH block index is not larger than one. + +**Table 4.1-1: Mapping between the combination of *subCarrierSpacingCommon* and LSB of *ssb-SubcarrierOffset* to $\Delta$ for operation with shared spectrum channel access in FR1** + +| subCarrierSpacingCommon | LSB of ssb-SubcarrierOffset | $\Delta$ | +|--------------------------------|------------------------------------|----------| +| scs15or60 | 0 | 1 | +| scs15or60 | 1 | 2 | +| scs30or120 | 0 | 4 | +| scs30or120 | 1 | 8 | + +For operation with shared spectrum channel access in FR2-2, a UE assumes that SS/PBCH blocks in a serving cell that are within a same discovery burst transmission window or across discovery burst transmission windows are quasi co-located with respect to average gain, quasi co-location 'typeA' and 'typeD' properties, when applicable, if a value of $\Delta$ is same among the SS/PBCH blocks, where $\Delta$ is the candidate SS/PBCH block index. $\Delta$ is either provided by *ssb-PositionQCL* or, if *ssb-PositionQCL* is not provided, obtained from a *MIB* provided by a SS/PBCH block according to Table 4.1-2. The UE can determine an SS/PBCH block index according to $\Delta$ . The UE assumes that within a discovery burst transmission window, a number of transmitted SS/PBCH blocks on a serving cell is not larger than $\Delta$ and a number of transmitted SS/PBCH blocks with a same SS/PBCH block index is not larger than one. + +**Table 4.1-2: Mapping between *subCarrierSpacingCommon* to $\Delta$ for operation with shared spectrum channel access in FR2-2** + +| subCarrierSpacingCommon | $\Delta$ | +|--------------------------------|----------| +| scs15or60 | 32 | +| scs30or120 | 64 | + +For operation without shared spectrum channel access in FR2-2, a UE expects a *MIB* in a SS/PBCH block to provide *subCarrierSpacingCommon* = 'scs30or120'. + +Upon detection of a SS/PBCH block, the UE determines from *MIB* that a CORESET for Type0-PDCCH CSS set, as described in clause 13, is present if $\Delta$ [4, TS 38.211] for FR1 or if $\Delta$ for FR2. The UE determines from *MIB* that a CORESET for Type0-PDCCH CSS set is not present if $\Delta$ for FR1 or if $\Delta$ for FR2; the CORESET for Type0-PDCCH CSS set may be provided by *PDCCH-ConfigCommon*. + +For a serving cell without transmission of SS/PBCH blocks, a UE acquires time and frequency synchronization with the serving cell based on receptions of SS/PBCH blocks on the PCell, or on the PSCell, or on an SCell if applicable as described in [10, TS 38.133], of the cell group for the serving cell. + +## 4.2 Transmission timing adjustments + +A UE can be provided a value of a timing advance offset for a serving cell by *n-TimingAdvanceOffset* for the serving cell. If for a serving cell the UE is provided two *coresetPoolIndex* values 0 and 1 for first and second CORESETs, or is not provided *coresetPoolIndex* value for first CORESETs and is provided *coresetPoolIndex* value of 1 for second CORESETs, the UE can be provided first and second values by *n-TimingAdvanceOffset* and *n-TimingAdvanceOffset2* for transmissions with first and second spatial filters associated with first and second TCI states for the first and second CORESETs, respectively. A UE can be provided a second value for transmissions with second spatial domain filters corresponding to second TCI states or to second SS/PBCH block receptions associated with *physCellId* different from *physCellId* for the serving cell in addition to a first value for transmissions with first spatial domain filters corresponding to first TCI states or to first SS/PBCH block receptions associated with *physCellId* for the serving cell. The first and second values correspond to first and second TAGs indicated in respective MAC RARs [11, TS 38.321] having an association indicated by *tag-Id-ptr* with first and second joint TCI states provided by *dl-OrJointTCI-StateList*. + +or first and second UL TCI states provided by *ul-TCI-State-List*. If the UE is not provided *n-TimingAdvanceOffset* for a serving cell, the UE determines a default value of the timing advance offset for the serving cell as described in [10, TS 38.133]. + +If a UE is configured with two UL carriers for a serving cell, a same timing advance offset value applies to both carriers for transmissions on the serving cell that are associated with a same TAG. The UE does not expect to apply two values for transmissions on the SUL carrier. + +Upon reception of a timing advance command for a TAG, the UE adjusts uplink timing for PUSCH/SRS/PUCCH transmission on all the serving cells in the TAG based on a value that the UE expects to be same for all the serving cells in the TAG and based on the received timing advance command where the uplink timing for PUSCH/SRS/PUCCH transmissions is the same for all the serving cells in the TAG. + +For a band with synchronous contiguous intra-band EN-DC in a band combination with non-applicable maximum transmit timing difference requirements as described in Note 1 of Table 7.5.3-1 of [10, TS 38.133], if the UE indicates *ul-TimingAlignmentEUTRA-NR* as 'required' and uplink transmission timing based on timing adjustment indication for a TAG from MCG and a TAG from SCG are determined to be different by the UE, the UE adjusts the transmission timing for PUSCH/SRS/PUCCH transmission on all serving cells part of the band with the synchronous contiguous intra-band EN-DC based on timing adjustment indication for a TAG from a serving cell in MCG in the band. The UE is not expected to transmit a PUSCH/SRS/PUCCH in one CG when the PUSCH/SRS/PUCCH is overlapping in time, even partially, with random access preamble transmitted in another CG. + +For a SCS of kHz, the timing advance command for a TAG indicates the change of the uplink timing relative to the current uplink timing for the TAG in multiples of . The start timing of the random access preamble is described in [4, TS 38.211]. + +A timing advance command [11, TS 38.321] in case of random access response or in an absolute timing advance command MAC CE or in a cell switch command, , for a TAG indicates values by index values of $= 0, 1, 2, \dots, 3846$ , where an amount of the time alignment for the TAG with SCS of kHz is . is defined in [4, TS 38.211] and is relative to the SCS of the first uplink transmission from the UE after the reception of the random access response or absolute timing advance command MAC CE or the cell switch command. + +In other cases, a timing advance command [11, TS 38.321], , for a TAG indicates adjustment of a current value, , to the new value, , by index values of $= 0, 1, 2, \dots, 63$ , where for a SCS of kHz, . + +If a UE has multiple active UL BWPs, as described in clause 12, in a same TAG, including UL BWPs in two UL carriers of a serving cell, the timing advance command value is relative to the largest SCS of the multiple active UL BWPs. The applicable value for an UL BWP with lower SCS may be rounded to align with the timing advance granularity for the UL BWP with the lower SCS while satisfying the timing advance accuracy requirements in [10, TS 38.133]. + +Adjustment of an value by a positive or a negative amount indicates advancing or delaying the uplink transmission timing for the TAG by a corresponding amount, respectively. + +For a timing advance command received on uplink slot and for a transmission other than a PUSCH scheduled by a RAR UL grant or a fallbackRAR UL grant as described in clause 8.2A or 8.3, or a PUCCH with HARQ-ACK information in response to a successRAR as described in clause 8.2A, the corresponding adjustment of the uplink transmission timing applies from the beginning of uplink slot where , is a time duration in msec of symbols corresponding to a PDSCH processing time for UE processing capability 1 when additional PDSCH DM-RS is configured, is a time duration in msec of symbols corresponding to a PUSCH preparation time for UE processing capability 1 [6, TS 38.214], is the maximum timing advance value in msec that can be provided by a TA command field of 12 bits, is the number of slots per subframe, is the subframe duration of 1 msec, and , where is provided by *cellSpecificKoffset* and is provided by a Differential Koffset MAC CE command [11, TS 38.321]; otherwise, if not respectively provided, or and are determined with respect to the minimum SCS among the SCSs of all configured UL BWPs for all uplink carriers in the TAG and of all configured DL BWPs for the corresponding downlink carriers. For , the UE assumes [6, TS 38.214]. Slot and are determined with respect to the minimum SCS among the SCSs of all configured UL BWPs for all uplink carriers in the TAG. is determined with respect to the minimum SCS among the SCSs of all configured UL BWPs for all uplink carriers in the TAG and for all configured initial UL BWPs provided by *initialUplinkBWP*. The uplink slot is the last slot among uplink slot(s) overlapping with the slot(s) of PDSCH reception assuming , where the PDSCH provides the timing advance command and is defined in [4, TS 38.211]. + +If a UE changes an active UL BWP between a time of a timing advance command reception and a time of applying a corresponding adjustment for the uplink transmission timing, the UE determines the timing advance command value based on the SCS of the new active UL BWP. If the UE changes an active UL BWP after applying an adjustment for + +the uplink transmission timing, the UE assumes a same absolute timing advance command value before and after the active UL BWP change. + +If the received downlink timing changes and is not compensated or is only partly compensated by the uplink timing adjustment without timing advance command as described in [10, TS 38.133], the UE changes accordingly. If a UE operates with two TAGs on an active UL BWP of a serving cell, the UE expects that a difference between a first downlink timing associated with a first TAG and a second downlink timing associated with a second TAG is not larger than the CP length for the active UL BWP unless the UE indicates *larger-thanCP-capability*. If a UE indicates *XYZ\_capability*, and transmits SRS based on a configuration by *SRS-PosResourceSet* in *SRS-PosRRC-InactiveConfig-ValidityArea* in RRC\_INACTIVE state, + +- if the UE is provided *SRS-autonomousTAupdate*, the UE may autonomously update at cell reselection as described in [10, TS 38.133] +- if the UE is not provided *SRS-autonomousTAupdate*, the UE maintains the of a last serving cell prior to the release of a dedicated RRC connection [11, TS 38.321]. + +For operation with single TAG on a serving cell, if two adjacent slots overlap due to a TA command or due to update of or , when applicable, the latter slot is reduced in duration relative to the former slot. The UE does not change during an actual transmission time window for a PUSCH or a PUCCH transmission [6, TS 38.214]. If the UE is not provided *enableSTx2PofMDCl* and operates with two TAGs on a serving cell, the UE does not expect transmissions associated with different TAGs to overlap unless the UE indicates *XYZ*; if the UE indicates *XYZ*, the UE reduces in duration a latter transmission using a first TAG to avoid overlapping with a former transmission using a second TAG. + +Using higher-layer ephemeris parameters for a serving satellite, if provided, a UE pre-compensates the two-way transmission delay on the service link based on that the UE determines using the serving satellite position and its own position. To pre-compensate the two-way transmission delay between the uplink time synchronization reference point and the serving satellite, the UE determines [4, TS 38.211] based on one-way propagation delay that the UE determines as: + +where , , and are respectively provided by *ta-Common*, *ta-CommonDrift*, and *ta-CommonDriftVariant* and is provided by *epochTime* which is the epoch time of *ta-Common*, *ta-CommonDrift*, and *ta-CommonDriftVariant* [12, TS 38.331]. provides a distance at time between the serving satellite and the uplink time synchronization reference point divided by the speed of light. The uplink time synchronization reference point is the point where DL and UL are frame aligned with an offset given by . + +## 4.3 Timing for secondary cell activation / deactivation + +With reference to slots for PUCCH transmissions, when a UE receives in a PDSCH an activation command [11, TS 38.321] for a secondary cell ending in slot $n$ , the UE applies the corresponding actions in [11, TS 38.321] no later than the minimum requirement defined in [10, TS 38.133] and no earlier than slot $n + k$ , except for the following: + +- the actions related to CSI reporting on a serving cell that is active in slot $n + k$ +- the actions related to the *sCellDeactivationTimer* associated with the secondary cell [11, TS 38.321] that the UE applies in slot $n + k$ +- the actions related to CSI reporting on a serving cell which is not active in slot $n + k$ that the UE applies in the earliest slot after $n + k$ in which the serving cell is active. + +The value of $k$ is where slot $n+m$ is a slot indicated for PUCCH transmission with HARQ-ACK information for the PDSCH reception as described in clause 9.2.3 and $N_{\text{slot}}^{\text{subframe}, \mu}$ is a number of slots per subframe for the SCS configuration $\mu$ of the PUCCH transmission as defined in [4, TS 38.211]. + +With reference to slots for PUCCH transmissions, if a UE receives a deactivation command [11, TS 38.321] for a secondary cell ending in slot $n$ , the UE applies the corresponding actions in [11, TS 38.321] no later than the minimum requirement defined in [10, TS 38.133], except for the actions related to CSI reporting on an activated serving cell which the UE applies in slot $n + k$ . + +If the *sCellDeactivationTimer* associated with the secondary cell expires in slot $n$ , the UE applies the corresponding actions in [11, TS 38.321] no later than the minimum requirement defined in [10, TS 38.133], except for the actions related to CSI reporting on an activated serving cell which the UE applies in the first slot that is after slot $n + 3 \cdot N_{\text{slot}}^{\text{subframe}, \mu}$ where $\mu$ is the SCS configuration for PDSCH reception on the secondary cell. + +# 5 Radio link monitoring + +The downlink radio link quality of the primary cell is monitored by a UE for the purpose of indicating out-of-sync/in-sync status to higher layers. The UE is not required to monitor the downlink radio link quality in DL BWPs other than the active DL BWP, as described in clause 12, on the primary cell unless the UE indicates a capability *rlm-BM-BFD-L3-IntraFreq-CD-SSB-MeasWithoutInterrupt-r18* or *rlm-BM-BFD-CD-SSB-MeasWithInterrupt-r18* [18, TS 38.306]. If the active DL BWP is the initial DL BWP and for SS/PBCH block and CORESET multiplexing pattern 2 or 3, as described in clause 13, the UE is expected to perform RLM using the associated SS/PBCH block when the associated SS/PBCH block index is provided by *RadioLinkMonitoringRS*. + +If the UE is configured with a SCG, as described in [12, TS 38.331], and the parameter *rlf-TimersAndConstants* is provided by higher layers and is not set to release, the downlink radio link quality of the PSCell of the SCG is monitored by the UE for the purpose of indicating out-of-sync/in-sync status to higher layers. The UE is not required to monitor the downlink radio link quality in DL BWPs other than the active DL BWP on the PSCell unless the UE indicates a capability *rlm-BM-BFD-L3-IntraFreq-CD-SSB-MeasWithoutInterrupt-r18* or *rlm-BM-BFD-CD-SSB-MeasWithInterrupt-r18* [18, TS 38.306]. + +A UE can be configured for each DL BWP of a SpCell [11, TS 38.321] with a set of resource indexes, through a corresponding set of *RadioLinkMonitoringRS*, for radio link monitoring by *failureDetectionResources*. The UE is provided either a CSI-RS resource configuration index, by *csi-RS-Index*, or a SS/PBCH block index, by *ssb-Index*. The UE can be configured with up to *RadioLinkMonitoringRS* for link recovery procedures, as described in clause 6, and for radio link monitoring. From the *RadioLinkMonitoringRS*, up to *RadioLinkMonitoringRS* can be used for radio link monitoring depending on as described in Table 5-1, wherein $\mu$ is as defined in clause 4.1, and up to two *RadioLinkMonitoringRS* can be used for link recovery procedures. + +For operation with shared spectrum channel access, when a UE is provided a SS/PBCH block index by *ssb-Index*, the UE is expected to perform radio link monitoring using SS/PBCH block(s) in the discovery burst transmission window as described in clause 4.1, where the SS/PBCH block(s) have candidate SS/PBCH block index(es) corresponding to SS/PBCH block index provided by *ssb-Index*. + +If the UE is not provided *RadioLinkMonitoringRS* and the UE is provided for PDCCH receptions TCI states that include one or more of a CSI-RS + +- the UE uses for radio link monitoring the RS provided for the active TCI state for PDCCH reception if the active TCI state for PDCCH reception includes only one RS +- if the active TCI state for PDCCH reception includes two RS, the UE expects that one RS is configured with *qcl-Type* set to 'typeD' [6, TS 38.214] and the UE uses the RS configured with *qcl-Type* set to 'typeD' for radio link monitoring; the UE does not expect both RS to be configured with *qcl-Type* set to 'typeD' +- the UE is not required to use for radio link monitoring an aperiodic or semi-persistent RS +- For $\mu$ , the UE selects the RS provided for active TCI states for PDCCH receptions in CORESETs associated with the search space sets in an order from the shortest monitoring periodicity. If more than one CORESETs are associated with search space sets having same monitoring periodicity, the UE determines the order of the CORESET from the highest CORESET index as described in clause 10.1. + +A UE does not expect to use more than *RadioLinkMonitoringRS* for radio link monitoring when the UE is not provided *RadioLinkMonitoringRS*. + +Values of $\mu$ and $\mu_{\text{max}}$ for different values of are given in Table 5-1. + +**Table 5-1:** $N_{LR-RLM}$ and as a function of maximum number of SS/PBCH blocks per half frame + +| 4 | 2 | 2 | +|----|---|---| +| 8 | 6 | 4 | +| 64 | 8 | 8 | + +For a CSI-RS resource configuration, *powerControlOffsetSS* is not applicable and a UE expects to be provided only 'noCDM' from *cdm-Type*, only 'one' and 'three' from *density*, and only '1 port' from *nrofPorts* [6, TS 38.214]. + +If a UE is configured with multiple DL BWPs for a serving cell, the UE performs RLM using the RS(s) corresponding to resource indexes provided by *RadioLinkMonitoringRS* for the active DL BWP or, if *RadioLinkMonitoringRS* is not provided for the active DL BWP, using the RS(s) provided for the active TCI state for PDCCH receptions in CORESETs on the active DL BWP. + +In non-DRX mode operation, the physical layer in the UE assesses once per indication period the radio link quality, evaluated over the previous time period defined in [10, TS 38.133] against thresholds ( $Q_{out}$ and $Q_{in}$ ) configured by *rlmInSyncOutOfSyncThreshold*. The UE determines the indication period as the maximum between the shortest periodicity for radio link monitoring resources and 10 msec. + +In DRX mode operation, the physical layer in the UE assesses once per indication period the radio link quality, evaluated over the previous time period defined in [10, TS 38.133], against thresholds ( $Q_{out}$ and $Q_{in}$ ) provided by *rlmInSyncOutOfSyncThreshold*. The UE determines the indication period as the maximum between the shortest periodicity for radio link monitoring resources and the DRX period. + +The physical layer in the UE indicates, in frames where the radio link quality is assessed, out-of-sync to higher layers when the radio link quality is worse than the threshold $Q_{out}$ for all resources in the set of resources for radio link monitoring. When the radio link quality is better than the threshold $Q_{in}$ for any resource in the set of resources for radio link monitoring, the physical layer in the UE indicates, in frames where the radio link quality is assessed, in-sync to higher layers. + +# 6 Link recovery procedures + +A UE can be provided, for each BWP of a serving cell, a set of periodic CSI-RS resource configuration indexes by *failureDetectionResourcesToAddModList* and a set of periodic CSI-RS resource configuration indexes and/or SS/PBCH block indexes by *candidateBeamRSList* or *candidateBeamRSListExt* or *candidateBeamRSSCellList* for radio link quality measurements on the BWP of the serving cell. Instead of the sets and , for each BWP of a serving cell, the UE can be provided respective two sets and of periodic CSI-RS resource configuration indexes by *failureDetectionSet1* and *failureDetectionSet2* that can be activated by a MAC CE [11 TS 38.321] and corresponding two sets and of periodic CSI-RS resource configuration indexes and/or SS/PBCH block indexes by *candidateBeamRS-List* and *candidateBeamRS-List2*, respectively, for radio link quality measurements on the BWP of the serving cell. The set is associated with the set and the set is associated with the set . + +If the UE is not provided by *failureDetectionResourcesToAddModList* for a BWP of the serving cell, the UE determines the set to include periodic CSI-RS resource configuration indexes with same values as the RS indexes in the RS sets indicated by *TCI-State* for respective CORESETs that the UE uses for monitoring PDCCH. If the UE is not provided and for a BWP of the serving cell, the UE determines the set and to include periodic CSI-RS resource configuration indexes with same values as the RS indexes in the RS sets indicated by *TCI-State* for first and second CORESETs that the UE uses for monitoring PDCCH, respectively, where the UE is provided two *coresetPoolIndex* values 0 and 1 for the first and second CORESETs, or is not provided *coresetPoolIndex* value for the first CORESETs and is provided *coresetPoolIndex* value of 1 for the second CORESETs, respectively. If there are two RS indexes in a TCI state, the set or , or includes RS indexes configured with *qcl-Type* set to 'typeD' for the corresponding TCI states. If a CORESET that the UE uses for monitoring PDCCH includes two TCI states and the UE is provided *sfnSchemePdcch* set to 'sfnSchemeA' or 'sfnSchemeB', the set includes RS indexes in the RS sets associated with the two TCI states. + +The UE expects the set to include up to two RS indexes. If the UE is provided or , the UE expects the set or the set to include up to a number of RS indexes indicated by *maxBFD-RS-resourcesPerSetPerBWP*. If the UE is not provided or , and if a number of active TCI states for PDCCH receptions in the first or second CORESETs is larger than , the UE + +determines the set or to include periodic CSI-RS resource configuration indexes with same values as the RS indexes in the RS sets associated with the active TCI states for PDCCH receptions in the first or second CORESETs corresponding to search space sets according to an ascending order for PDCCH monitoring periodicity. If more than one first or second CORESETs correspond to search space sets with same monitoring periodicity, the UE determines the order of the first or second CORESETs according to a descending order of a CORESET index. + +If a UE + +- is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with a value of 0 for first CORESETs on an active DL BWP of a serving cell, +- is provided *coresetPoolIndex* with a value of 1 for second CORESETs on the active DL BWP of the serving cells, and +- is provided *SSB-MTCAdditionalPCI* + +SS/PBCH block indexes associated with a physical cell identity other than the one provided by *physCellId* in *ServingCellConfigCommon* can be provided in set and the corresponding set is associated with the physical cell identity. + +The UE expects single port RS in the set , or , or . The UE expects single-port or two-port CSI-RS with frequency density equal to 1 or 3 REs per RB in the set , or , or . The thresholds $Q_{out,LR}$ and $Q_{in,LR}$ correspond to the default value of *rlnInSyncOutOfSyncThreshold*, as described in [10, TS 38.133] for $Q_{out}$ , and to the value provided by *rsrp-ThresholdSSB* or *rsrp-ThresholdBFR*, respectively. + +The physical layer in the UE assesses the radio link quality according to the set , or , of resource configurations against the threshold $Q_{out,LR}$ . For the set , the UE assesses the radio link quality only according to SS/PBCH blocks on the PCell or the PSCell or periodic CSI-RS resource configurations that are quasi co-located, as described in [6, TS 38.214], with the DM-RS of PDCCH receptions by the UE. The UE applies the $Q_{in,LR}$ threshold to the L1-RSRP measurement obtained from a SS/PBCH block. The UE applies the $Q_{in,LR}$ threshold to the L1-RSRP measurement obtained for a CSI-RS resource after scaling a respective CSI-RS reception power with a value provided by *powerControlOffsetSS*. + +In non-DRX mode operation, the physical layer in the UE provides an indication to higher layers when the radio link quality for all corresponding resource configurations in the set , or in the set or , that the UE uses to assess the radio link quality is worse than the threshold $Q_{out,LR}$ . The physical layer informs the higher layers when the radio link quality is worse than the threshold $Q_{out,LR}$ with a periodicity determined by the maximum between the shortest periodicity among the SS/PBCH blocks on the PCell or the PSCell and/or the periodic CSI-RS configurations in the set , or that the UE uses to assess the radio link quality and 2 msec. In DRX mode operation, the physical layer provides an indication to higher layers when the radio link quality is worse than the threshold $Q_{out,LR}$ with a periodicity determined as described in [10, TS 38.133]. + +For the PCell or the PSCell, upon request from higher layers, the UE provides to higher layers the periodic CSI-RS configuration indexes and/or SS/PBCH block indexes from the set , or , or and the corresponding L1-RSRP measurements that are larger than or equal to the $Q_{in,LR}$ threshold. + +For the SCell, upon request from higher layers, the UE indicates to higher layers whether there is at least one periodic CSI-RS configuration index or SS/PBCH block index from the set , or , or with corresponding L1-RSRP measurements that is larger than or equal to the $Q_{in,LR}$ threshold, and provides the periodic CSI-RS configuration indexes and/or SS/PBCH block indexes from the set , or , or and the corresponding L1-RSRP measurements that are larger than or equal to the $Q_{in,LR}$ threshold, if any. + +For the PCell or the PSCell, a UE can be provided a CORESET through a link to a search space set provided by *recoverySearchSpaceId*, as described in clause 10.1, for monitoring PDCCH in the CORESET. If the UE is provided *recoverySearchSpaceId*, the UE does not expect to be provided another search space set for monitoring PDCCH in the CORESET associated with the search space set provided by *recoverySearchSpaceId*. + +For the PCell or the PSCell, the UE can be provided, by *PRACH-ResourceDedicatedBFR*, a configuration for PRACH transmission as described in clause 8.1. For PRACH transmission in slot and according to antenna port quasi co-location parameters associated with periodic CSI-RS resource configuration or with SS/PBCH block associated with index provided by higher layers [11, TS 38.321], the UE monitors PDCCH in a search space set provided by *recoverySearchSpaceId* for detection of a DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI starting from slot , where is the SCS configuration for the PRACH transmission and is a number of slots provided by *kmac* [12, TS 38.331] or if *kmac* is not provided, within a window configured by *BeamFailureRecoveryConfig*. For PDCCH monitoring in a search space set provided by *recoverySearchSpaceId* and for corresponding PDSCH receptions, the UE + +assumes the same antenna port quasi-collocation parameters as the ones associated with index $\kappa$ until the UE receives by higher layers an activation for a TCI state or any of the parameters *tci-StatesPDCCH-ToAddList* and/or *tci-StatesPDCCH-ToReleaseList*. After the UE detects a DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI in the search space set provided by *recoverySearchSpaceId*, the UE continues to monitor PDCCH candidates in the search space set provided by *recoverySearchSpaceId* until the UE receives a MAC CE activation command for a TCI state or *tci-StatesPDCCH-ToAddList* and/or *tci-StatesPDCCH-ToReleaseList*. + +For the PCell or the PSCell, after 28 symbols from a last symbol of a first PDCCH reception in a search space set provided by *recoverySearchSpaceId* for which the UE detects a DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI and until the UE receives an activation command for *PUCCH-SpatialRelationInfo* [11, TS 38.321] or is provided *PUCCH-SpatialRelationInfo* for PUCCH resource(s), the UE transmits a PUCCH on a same cell as the PRACH transmission using + +- a same spatial filter as for the last PRACH transmission +- a power determined as described in clause 7.2.1 with $\kappa$ , $\delta$ , and $\beta$ + +For the PCell or the PSCell and for sets $\kappa$ and $\delta$ , after 28 symbols from a last symbol of a first PDCCH reception in a search space set provided by *recoverySearchSpaceId* where a UE detects a DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI, the UE assumes same antenna port quasi-collocation parameters as the ones associated with index $\kappa$ for PDCCH monitoring in a CORESET with index 0. + +If a UE is provided *dl-OrJointTCI-StateList* or *ul-TCI-StateList* and is indicated one or two TCI state(s) for the PCell or the PSCell [6, TS 38.214] associated with $\kappa$ and $\delta$ , after 28 symbols from a last symbol of a first PDCCH reception in a search space set provided by *recoverySearchSpaceId* where the UE detects a DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI, the UE + +- if *SSB-MTC-AdditionalPCI* is not provided, monitors PDCCH in all CORESETs, and receives PDSCH and aperiodic CSI-RS resource in a CSI-RS resource set with same indicated TCI state as for the PDCCH and PDSCH, using the same antenna port quasi co-location parameters as the ones associated with the corresponding index $\kappa$ , if any +- transmits PUSCH, PUCCH and SRS that uses a same spatial domain filter with same indicated TCI state as for the PUSCH and the PUCCH, using a same spatial domain filter as for the last PRACH transmission using the following parameters for determination of a corresponding power as described in clauses 7.1.1, 7.2.1, and 7.3.1 + - the RS index for obtaining the downlink pathloss estimate + - the values of $\kappa$ , $\delta$ , and the PUSCH power control adjustment state provided by *p0AlphaSetforPUSCH* associated with the smallest value of *ul-powercontrolId* for the PCell or the PSCell + - the value of $\kappa$ and the PUCCH power control adjustment state provided by *p0AlphaSetforPUCCH* associated with the smallest value of *ul-powercontrolId* for the PCell or the PSCell + - the values of $\kappa$ , $\delta$ , and the SRS power control adjustment state provided by *p0AlphaSetforSRS* associated with the smallest value of *ul-powercontrolId* for the PCell or the PSCell + +For the remaining of this clause, if a PDCCH reception includes two PDCCH candidates from two linked search space sets based on *searchSpaceLinkingId*, as described in clause 10.1, the last symbol of the PDCCH reception is the last symbol of the PDCCH candidate that ends later. The PDCCH reception includes the two PDCCH candidates also when the UE is not required to monitor one of the two PDCCH candidates as described in clauses 10 (except clause 10.4), 11.1, 11.1.1 and 17.2. + +For the PCell or the PSCell, if BFR MAC CE [11, TS 38.321] is provided in Msg3 or MsgA of contention based random access procedure, and if a PUCCH resource is provided with *PUCCH-SpatialRelationInfo*, after 28 symbols from the last symbol of the PDCCH reception that determines the completion of the contention based random access procedure as described in clause 5.1.4a or in clause 5.1.5 of [11, TS 38.321], the UE transmits the PUCCH on a same cell as the PRACH transmission using + +- a same spatial filter as for the last PRACH transmission +- a power determined as described in clause 7.2.1 with $\kappa$ , $\delta$ , and $\beta$ , where $\kappa$ is the SS/PBCH block index selected for the last PRACH transmission. + +If a UE is provided *dl-OrJointTCI-StateList* or *ul-TCI-StateList* and is indicated one or two TCI state(s) for the PCell or the PSCell associated with $\alpha$ and $\beta$ , and the UE provides BFR MAC CE in Msg3 or MsgA of contention based random access procedure, after 28 symbols from the last symbol of the PDCCH reception that determines the completion of the contention based random access procedure as described in [11, TS 38.321], the UE + +- if *SSB-MTC-AdditionalPCI* is not provided, monitors PDCCH in all CORESETs, and receives PDSCH and aperiodic CSI-RS resource in a CSI-RS resource set with same indicated TCI state as for the PDCCH and PDSCH using the same antenna port quasi co-location parameters as the ones associated with the corresponding index $\alpha$ , if any +- transmits PUSCH, PUCCH and SRS that uses a same spatial domain filter with same indicated TCI state as for the PUSCH and PUCCH, using a same spatial domain filter as for the last PRACH transmission using the following parameters for determination of a corresponding power as described in clauses 7.1.1, 7.2.1, and 7.3.1 + - the RS index for obtaining the downlink pathloss estimate + - the values of $\alpha$ , $\beta$ , and the PUSCH power control adjustment state provided by *p0AlphaSetforPUSCH* associated with the smallest value of *ul-powercontrolId* for the PCell or the PSCell + - the value of $\alpha$ and the PUCCH power control adjustment state provided by *p0AlphaSetforPUCCH* associated with the smallest value of *ul-powercontrolId* for the PCell or the PSCell + - the values of $\alpha$ , $\beta$ , and the SRS power control adjustment state provided by *p0AlphaSetforSRS* associated with the smallest value of *ul-powercontrolId* for the PCell or the PSCell + +A UE can be provided, by *schedulingRequestID-BFR-SCell*, a configuration for PUCCH transmission with a link recovery request (LRR) as described in clause 9.2.4 for the UE to transmit PUCCH [11, TS 38.321]. If the PCell or the PSCell is associated with sets $\alpha$ and $\beta$ , and with sets $\alpha$ and $\beta$ , the UE can be provided by *schedulingRequestID-BFR* a first configuration for PUCCH transmission with a LRR and, if the UE provides *twoLRRcapability*, the UE can be provided by *schedulingRequestID-BFR2* a second configuration for PUCCH transmission with a LRR. If the UE is provided only the first configuration, the UE transmits a PUCCH with LRR for either set $\alpha$ or $\beta$ . If the UE is provided both the first and second configurations, the UE uses the first configuration to transmit a PUCCH with LRR associated with set $\alpha$ and the second configuration to transmit a PUCCH with LRR associated with set $\beta$ [11, TS 38.321]. + +The UE can provide in a first PUSCH MAC CE index(es) for at least corresponding SCell(s) with radio link quality worse than $Q_{out,LR}$ , indication(s) of presence of $\alpha$ for corresponding SCell(s), and index(es) for a periodic CSI-RS configuration or for a SS/PBCH block provided by higher layers, as described in [11, TS 38.321], if any, for corresponding SCell(s). After 28 symbols from a last symbol of a PDCCH reception with a DCI format scheduling a PUSCH transmission with a same HARQ process number as for the transmission of the first PUSCH and having a toggled NDI field value, the UE + +- monitors PDCCH in all CORESETs on the SCell(s) indicated by the MAC CE using the same antenna port quasi co-location parameters as the ones associated with the corresponding index(es), if any +- transmits PUCCH on a PUCCH-SCell using a same spatial domain filter as the one corresponding to $\alpha$ , if any, for periodic CSI-RS or SS/PBCH block reception, as described in clause 9.2.2, and using a power determined as described in clause 7.2.1 with $\alpha$ , $\beta$ , and $\gamma$ , if + - the UE is provided *PUCCH-SpatialRelationInfo* for the PUCCH, + - a PUCCH with the LRR was either not transmitted or was transmitted on the PCell or the PSCell, and + - the PUCCH-SCell is included in the SCell(s) indicated by the MAC-CE + +where the SCS configuration for the 28 symbols is the smallest of the SCS configurations of the active DL BWP for the PDCCH reception and of the active DL BWP(s) of the at least one SCell. + +For serving cells associated with $\alpha$ and $\beta$ , if a UE is provided *dl-OrJointTCI-StateList* or *ul-TCI-StateList* and is indicated one or two TCI state(s), after 28 symbols from a last symbol of a PDCCH reception with a DCI format scheduling a PUSCH transmission with a same HARQ process number as for the transmission of the first PUSCH and having a toggled NDI field value, the UE + +- if *SSB-MTC-AdditionalPCI* is not provided, monitors PDCCH in all CORESETs, on the SCell(s) indicated by the MAC CE, and receives PDSCH and aperiodic CSI-RS resource in a CSI-RS resource set using the same antenna port quasi co-location parameters as the ones associated with the corresponding index $\alpha$ , if any + +- transmits PUSCH, PUCCH and SRS that uses a same spatial domain filter with same indicated TCI state as for the PUSCH and PUCCH, using a same spatial domain filter as the one corresponding to , if any, and using the following parameters for determination of a corresponding power as described in clauses 7.1.1, 7.2.1, and 7.3.1 +- the RS index for obtaining the downlink pathloss estimate +- the values of , , and the PUSCH power control adjustment state provided by *p0AlphaSetforPUSCH* associated with the smallest value of *ul-powercontrolId* for the corresponding SCell +- the value of and the PUCCH power control adjustment state provided by *p0AlphaSetforPUCCH* associated with the smallest value of *ul-powercontrolId* for the corresponding SCell +- the values of , , and the SRS power control adjustment state provided by *p0AlphaSetforSRS* associated with the smallest value of *ul-powercontrolId* for the corresponding SCell + +If there is at least one serving cell associated with sets and , and with sets and , the UE can provide in a second PUSCH MAC CE index(es) for cell(s) with and/or with at least one of and having radio link quality worse than $Q_{out,LR}$ , the index(es) of those and/or , and indication(s) of presence of and of index(es) , if any, from and/or corresponding sets and/or for the serving cells. + +For serving cells associated with sets and , and with sets and , and having radio link quality worse than $Q_{out,LR}$ , after 28 symbols from a last symbol of a first PDCCH reception with a DCI format scheduling a PUSCH transmission with a same HARQ process number as for transmission of the second PUSCH and having a toggled NDI field value, the UE assumes antenna port quasi-collocation parameters + +- corresponding to from , if any, for the first CORESETs, +- corresponding to from , if any, for the second CORESETs + +where the SCS configuration for the 28 symbols is the smallest of the SCS configurations of the active DL BWP for the PDCCH reception and of the active DL BWP(s) of the serving cells. + +For a serving cell associated with sets and , and with sets and , and having radio link quality worse than $Q_{out,LR}$ , and if a UE is provided *dl-OrJointTCI-StateList* or *TCI-UL-State* and is indicated a first *TCI-State* or *TCI-UL-State* and a second *TCI-State* or *TCI-UL-State*, after 28 symbols from a last symbol of a first PDCCH reception with a DCI format scheduling a PUSCH transmission with a same HARQ process number as for the transmission of the second PUSCH and having a toggled NDI field value, the UE + +- monitors PDCCH that applies the first *TCI-State* state, and receives PDSCH and aperiodic CSI-RS resource that apply the first *TCI-State*, using same antenna port quasi co-location parameters as the ones associated with a corresponding index from , if any, on the serving cell +- monitors PDCCH that applies the second *TCI-State*, and receives PDSCH and aperiodic CSI-RS resource that apply the second *TCI-State*, on the serving cell using same antenna port quasi co-location parameters as the ones associated with a corresponding index from , if any, on the serving cell +- transmits PUSCH, PUCCH, and SRS that apply the first *TCI-State* or *TCI-UL-State* using a same spatial domain filter as the one corresponding to from , if any, on the serving cell and using the following parameters for determination of a corresponding power as described in clauses 7.1.1, 7.2.1, and 7.3.1 + - the RS index from , if any, for obtaining a corresponding downlink pathloss estimate for the serving cell + - the values of , , and the PUSCH power control adjustment state provided by *p0AlphaSetforPUSCH* associated with the smallest value of *ul-powercontrolId* for the serving cell + - the value of and the PUCCH power control adjustment state provided by *p0AlphaSetforPUCCH* associated with the smallest value of *ul-powercontrolId* for the serving cell + - the values of , , and the SRS power control adjustment state provided by *p0AlphaSetforSRS* associated with the smallest value of *ul-powercontrolId* for the serving cell +- transmits PUSCH, PUCCH, and SRS that apply the second *TCI-State* or *TCI-UL-State* using a same spatial domain filter as the one corresponding to from , if any, on the serving cell and using the following parameters for determination of a corresponding power as described in clauses 7.1.1, 7.2.1, and 7.3.1 + - the RS index from , if any, for obtaining a corresponding downlink pathloss estimate for the serving cell + +- the values of $\beta$ , $\delta$ , and the PUSCH power control adjustment state provided by *p0AlphaSetforPUSCH* associated with the smallest value of *ul-powercontrolId* for the serving cell +- the value of $\beta$ and the PUCCH power control adjustment state provided by *p0AlphaSetforPUCCH* associated with the smallest value of *ul-powercontrolId* for the serving cell +- the values of $\beta$ , $\delta$ , and the SRS power control adjustment state provided by *p0AlphaSetforSRS* associated with the smallest value of *ul-powercontrolId* for the serving cell + +where the SCS configuration for the 28 symbols is the smallest of the SCS configurations of the active DL BWP for the PDCCH reception and of the active DL BWP(s) of the serving cells. + +For a serving cell associated with sets $\mathcal{C}_1$ and $\mathcal{C}_2$ , and with sets $\mathcal{C}_1$ and $\mathcal{C}_2$ , and having radio link quality worse than $Q_{out,LR}$ , and if a UE is provided two *coresetPoolIndex* values 0 and 1 for the first and second CORESETs, or is not provided *coresetPoolIndex* value for the first CORESETs and is provided *coresetPoolIndex* value of 1 for the second CORESETs, respectively, and the UE is provided *dl-OrJointTCI-StateList* or *TCI-UL-State*, after 28 symbols from a last symbol of a first PDCCH reception with a DCI format scheduling a PUSCH transmission with a same HARQ process number as for the transmission of the second PUSCH and having a toggled NDI field value, the UE + +- monitors PDCCH in the first CORESETs, and receives PDSCH scheduled/activated by PDCCH in the first CORESETs, and aperiodic CSI-RS resource that apply a *TCI-State* specific to the first CORESETs, using same antenna port quasi co-location parameters as the ones associated with a corresponding index $\kappa$ from $\mathcal{C}_1$ , if any, for the serving cell +- monitors PDCCH in the second CORESETs, and receives PDSCH scheduled/activated by PDCCH in the second CORESETs, and aperiodic CSI-RS resource that apply a *TCI-State* specific to the second CORESETs, using the same antenna port quasi co-location parameters as the ones associated with the corresponding index $\kappa$ from $\mathcal{C}_2$ , if any, for the serving cell +- transmits PUSCH, PUCCH, and SRS that apply *TCI-State* or *TCI-UL-State* specific to the first CORESETs using a same spatial domain filter as the one corresponding to $\kappa$ from $\mathcal{C}_1$ , if any, for the serving cell and using the following parameters for determination of a corresponding power as described in clauses 7.1.1, 7.2.1, and 7.3.1 + - the RS index $\kappa$ from $\mathcal{C}_1$ , if any, for obtaining a corresponding downlink pathloss estimate for the serving cell + - the values of $\beta$ , $\delta$ , and the PUSCH power control adjustment state provided by *p0AlphaSetforPUSCH* associated with the smallest value of *ul-powercontrolId* for the serving cell + - the value of $\beta$ and the PUCCH power control adjustment state provided by *p0AlphaSetforPUCCH* associated with the smallest value of *ul-powercontrolId* for the serving cell + - the values of $\beta$ , $\delta$ , and the SRS power control adjustment state provided by *p0AlphaSetforSRS* associated with the smallest value of *ul-powercontrolId* for the serving cell +- transmits PUSCH, PUCCH, and SRS that apply *TCI-State* or *TCI-UL-State* specific to the second CORESETs using a same spatial domain filter as the one corresponding to $\kappa$ from $\mathcal{C}_2$ , if any, for the serving cell and using the following parameters for determination of a corresponding power as described in clauses 7.1.1, 7.2.1, and 7.3.1 + - the RS index $\kappa$ from $\mathcal{C}_2$ , if any, for obtaining a corresponding downlink pathloss estimate for the serving cell + - the values of $\beta$ , $\delta$ , and the PUSCH power control adjustment state provided by *p0AlphaSetforPUSCH* associated with the smallest value of *ul-powercontrolId* for the serving cell + - the value of $\beta$ and the PUCCH power control adjustment state provided by *p0AlphaSetforPUCCH* associated with the smallest value of *ul-powercontrolId* for the serving cell + - the values of $\beta$ , $\delta$ , and the SRS power control adjustment state provided by *p0AlphaSetforSRS* associated with the smallest value of *ul-powercontrolId* for the serving cell + +where the SCS configuration for the 28 symbols is the smallest of the SCS configurations of the active DL BWP for the PDCCH reception and of the active DL BWP(s) of the serving cells. + +# 7 Uplink Power control + +Uplink power control determines a power for PUSCH, PUCCH, SRS, and PRACH transmissions. + +A UE does not expect to simultaneously maintain more than four pathloss estimates per serving cell for all PUSCH/PUCCH/SRS transmissions as described in clauses 7.1.1, 7.2.1, and 7.3.1, except for SRS transmissions configured by *SRS-PosResourceSet* as described in clause 7.3.1. If the UE is provided a number of RS resources for pathloss estimation for PUSCH/PUCCH/SRS transmissions that is larger than 4, the UE maintains for pathloss estimation RS resources corresponding to RS resource indexes as described in clauses 7.1.1, 7.2.1, and 7.3.1. If an RS resource updated by MAC CE, as described in clauses 7.1.1, 7.2.1 and 7.3.1, is one from the RS resources the UE maintains for pathloss estimation for PUSCH/PUCCH/SRS transmissions, the UE applies the pathloss estimation based on the RS resources starting from the first slot that is after slot *l* where *l* is the slot where the UE would transmit a PUCCH or PUSCH with HARQ-ACK information for the PDSCH providing the MAC CE, *l* is the SCS configuration for the PUCCH or PUSCH, respectively, that is determined in the slot when the MAC CE command is applied and *l* is a number of slots for SCS configuration provided by *kmac* or if *kmac* is not provided. + +A PUSCH/PUCCH/SRS/PRACH transmission occasion is defined by a slot index within a frame with system frame number *n*, a first symbol within the slot, and a number of consecutive symbols *l*. For a PUSCH transmission with repetition Type B, a PUSCH transmission occasion is a nominal repetition [6, TS 38.214]. + +In the remaining of this clause, if a UE is provided *TCI-State* in *dl-OrJointTCI-StateList* or *TCI-UL-State*, and for each indicated one or two *TCI-State* or *TCI-UL-State* of a PUSCH, PUCCH, or SRS transmission occasion as described in [6, TS 38.214] + +- in clauses 7.1.1, 7.2.1, and 7.3.1, the RS index for obtaining the downlink pathloss estimate for PUSCH, PUCCH, and SRS transmission is provided by *pathlossReferenceRS-Id-r17* associated with or included in the indicated *TCI-State* or *TCI-UL-State* except for SRS transmission that is not provided *followUnifiedTCI-StateSRS* +- in clause 7.1.1, if *p0AlphaSetforPUSCH* is provided, the values of $\alpha$ , $P_0$ , and the PUSCH power control adjustment state are provided by *p0AlphaSetforPUSCH* associated with the indicated *TCI-State* or *TCI-UL-State* +- in clause 7.2.1, if *p0AlphaSetforPUCCH* is provided, the values of $\alpha$ and the PUCCH power control adjustment state are provided by *p0AlphaSetforPUCCH* associated with the indicated *TCI-State* or *TCI-UL-State* +- in clause 7.3.1, if *p0AlphaSetforSRS* is provided, + - if *followUnifiedTCI-StateSRS* is provided for a SRS resource set, the values of $\alpha$ , $P_0$ , and SRS power control adjustment state are provided by *p0AlphaSetforSRS* associated with the indicated *TCI-State* or *TCI-UL-State* + - else, if *followUnifiedTCI-StateSRS* is not provided for a SRS resource set and for a SRS resource from the SRS resource set, the values of $\alpha$ , $P_0$ , and SRS power control adjustment state are provided by *p0AlphaSetforSRS* associated with *TCI-State* or *TCI-UL-State* of an SRS resource with lowest *SRS-ResourceId* in the SRS resource set and a RS index for obtaining a pathloss estimate for the SRS transmission is provided by *pathlossReferenceRS-Id-r17* associated with or included in the *TCI-State* or *TCI-UL-State* of an SRS resource with lowest *SRS-ResourceId* in the SRS resource set + +$\alpha$ is the sum of the component $\alpha_i$ and a component $p_0$ provided by *SRS-ResourceSet* corresponding to the SRS resource set. + +In the remaining of this clause, if a PDCCH reception by a UE includes two PDCCH candidates from corresponding search space sets, as described in clause 10.1 + +- a PDCCH monitoring occasion is the union of the PDCCH monitoring occasions for the two PDCCH candidates +- the end of the PDCCH reception is the end of the PDCCH candidate that ends later + +The PDCCH reception includes the two PDCCH candidates also when the UE is not required to monitor one of the two PDCCH candidates as described in clauses 10 (except clause 10.4), 11.1, 11.1.1 and 17.2. + +## 7.1 Physical uplink shared channel + +For a PUSCH transmission on active UL BWP, as described in clause 12, of carrier of serving cell, a UE first calculates a linear value of the transmit power, with parameters as defined in clause 7.1.1. For a PUSCH transmission scheduled by a DCI format other than DCI format 0\_0, or configured by *ConfiguredGrantConfig* or *semiPersistentOnPUSCH*, if *txConfig* in *PUSCH-Config* is set to 'codebook', + +- if *ul-FullPowerTransmission* in *PUSCH-Config* is provided, the UE scales by where: + - if *ul-FullPowerTransmission* in *PUSCH-Config* is set to *fullpowerModel*, and each SRS resource in the *SRS-ResourceSet* with *usage* set to 'codebook' has more than one SRS port, is the ratio of a number of antenna ports with non-zero PUSCH transmission power over the maximum number of SRS ports supported by the UE in one SRS resource + - if *ul-FullPowerTransmission* in *PUSCH-Config* is set to *fullpowerMode2*, + - for full power TPMIs reported by the UE [18, TS 38.306], and is the ratio of a number of antenna ports with non-zero PUSCH transmission power over a number of SRS ports for remaining TPMIs, where the number of SRS ports is associated with an SRS resource indicated by an SRI field in a DCI format scheduling the PUSCH transmission if more than one SRS resource is configured in the *SRS-ResourceSet* with *usage* set to 'codebook', or indicated by Type 1 configured grant, or the number of SRS ports is associated with the SRS resource if only one SRS resource is configured in the *SRS-ResourceSet* with *usage* set to 'codebook', + - , if an SRS resource with a single port is indicated by an SRI field in a DCI format scheduling the PUSCH transmission when more than one SRS resource is provided in the *SRS-ResourceSet* with *usage* set to 'codebook', or indicated by Type 1 configured grant, or if only one SRS resource with a single port is provided in the *SRS-ResourceSet* with *usage* set to 'codebook', and + - if *ul-FullPowerTransmission* in *PUSCH-Config* is set to *fullpower*, + - else, if each SRS resource in the *SRS-ResourceSet* with *usage* set to 'codebook' has more than one SRS port, the UE scales the linear value by the ratio of the number of antenna ports with a non-zero PUSCH transmission power to the maximum number of SRS ports supported by the UE in one SRS resource. + +The UE splits the power equally across the antenna ports on which the UE transmits the PUSCH with non-zero power. + +### 7.1.1 UE behaviour + +If a UE transmits a PUSCH on active UL BWP of carrier of serving cell using parameter set configuration with index and PUSCH power control adjustment state with index, the UE determines the PUSCH transmission power in PUSCH transmission occasion as + +$$P_{\text{PUSCH},b,f,c}(i,j,q_d,l) = \min \left\{ \begin{array}{l} P_{\text{CMAX},f,c}(i), \\ P_{\text{O\_PUSCH},b,f,c}(j) + 10 \log_{10} (2^{\mu} \cdot M_{\text{RB},b,f,c}^{\text{PUSCH}}(i)) + \alpha_{b,f,c}(j) \cdot PL_{b,f,c}(q_d) + \Delta_{\text{TF},b,f,c}(i) + f_{b,f,c}(i,l) \end{array} \right\} \text{ [dBm]}$$ + +where, + +- is the UE configured maximum output power defined in [8-1, TS 38.101-1], [8-2, TS 38.101-2] and [8-3, TS 38.101-3] for carrier of serving cell in PUSCH transmission occasion. +- is a parameter composed of the sum of a component and a component where. +- If a UE established dedicated RRC connection using a Type-1 random access procedure, as described in clause 8, and is not provided *P0-PUSCH-AlphaSet* or for a PUSCH (re)transmission corresponding to a RAR UL grant as described in clause 8.3, + +, , and , + +where is provided by *preambleReceivedTargetPower* [11, TS 38.321] and is provided by *msg3-DeltaPreamble* or *deltaPreamble*, or dB if *msg3-DeltaPreamble* and *deltaPreamble* are not provided, for carrier of serving cell + +- If a UE established dedicated RRC connection using a Type-2 random access procedure, as described in clause 8, and is not provided *P0-PUSCH-AlphaSet*, or for a PUSCH transmission for Type-2 random access procedure as described in clause 8.1A, + +, , and , + +where *msgA-preambleReceivedTargetPower*, or by *preambleReceivedTargetPower* if *msgA-preambleReceivedTargetPower* is not provided and *msgA-DeltaPreamble* or *deltaPreamble*, or dB if *msgA-DeltaPreamble* and *deltaPreamble* are not provided, for carrier of serving cell + +- For a PUSCH (re)transmission configured by *ConfiguredGrantConfig*, *p0-NominalWithoutGrant*, or if *p0-NominalWithoutGrant* is not provided. +- If the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook' and is provided *p0-PUSCH-Alpha2*, for a retransmission of a configured grant Type 1 PUSCH, or for activation or retransmission of a configured grant Type 2 PUSCH, scheduled by a DCI format that includes a SRS resource set indicator field, and for active UL BWP of carrier of serving cell + - If the SRS resource set indicator value is 00, first value is provided by the value of *p0-PUSCH-Alpha* in *ConfiguredGrantConfig*. + - If the SRS resource set indicator value is 01, second value is provided by the value of *p0-PUSCH-Alpha2* in *ConfiguredGrantConfig*. + - If the SRS resource set indicator value is 10 or 11, first and second values that are respectively associated with the first and second SRS resource set are respectively provided by the values of *p0-PUSCH-Alpha* and by *p0-PUSCH-Alpha2* in *ConfiguredGrantConfig*. +- else if the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook' and is provided *p0-PUSCH-Alpha2*, for a transmission of a configured grant Type 1 PUSCH and for active UL BWP of carrier of serving cell + - a first value is provided by the value of *p0-PUSCH-Alpha* in *ConfiguredGrantConfig* that is associated with the first *srs-ResourceIndicator* in *rrc-ConfiguredUplinkGrant* + - a second value is provided by the value of *p0-PUSCH-Alpha2* in *ConfiguredGrantConfig* that is associated with the second *srs-ResourceIndicator* in *rrc-ConfiguredUplinkGrant* +- else if the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook' and is provided *p0-PUSCH-Alpha2*, for a retransmission of a configured grant Type 1 PUSCH, or for activation or retransmission of a configured grant Type 2 PUSCH, scheduled by a DCI format 0\_0, and for active UL BWP of carrier of serving cell + - a first value is provided by the value of *p0-PUSCH-Alpha* in *ConfiguredGrantConfig* +- else, *p0* obtained from *p0-PUSCH-Alpha* in *ConfiguredGrantConfig* that provides an index *P0-PUSCH-AlphaSetId* to a set of *P0-PUSCH-AlphaSet*, or by *sdt-P0-PUSCH* for a PUSCH (re)transmission as described in clause 19.1, for active UL BWP of carrier of serving cell +- For *p0*, a value, applicable for all *carrier*, is provided by *p0-NominalWithGrant*, or if *p0-NominalWithGrant* is not provided, for each carrier of serving cell and a set of values are provided by a set of *p0* in *P0-PUSCH-AlphaSet* indicated by a respective set of *p0-PUSCH-AlphaSetId* for active UL BWP of carrier of serving cell +- If the UE is provided by *SRI-PUSCH-PowerControl* more than one values of *p0-PUSCH-AlphaSetId* and if a DCI format scheduling the PUSCH transmission includes an SRI field, the UE obtains a mapping from *sri-PUSCH-PowerControlId* in *SRI-PUSCH-PowerControl* between a set of values for the SRI field in the DCI format [5, TS 38.212] and a set of indexes provided by *p0-PUSCH-AlphaSetId* that map to a set of *P0-PUSCH-AlphaSet* values and determines the value of *p0* from the *p0-PUSCH-AlphaSetId* value that is mapped to the SRI field value. If the UE is provided by *SRI-PUSCH-PowerControl* more than one values of *p0-PUSCH-AlphaSetId* + +- if the DCI format scheduling the PUSCH transmission includes two SRI fields and the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook', the UE obtains a mapping from *sri-PUSCH-PowerControlId* in *SRI-PUSCH-PowerControl* between a set of values for the two SRI fields and a set of indexes provided by *p0-PUSCH-AlphaSetId* that map to a set of *P0-PUSCH-AlphaSet* values, and determines first and second values of from the *p0-PUSCH-AlphaSetId* values that are mapped to the values of the first and second SRI fields, respectively. +- if the DCI format scheduling the PUSCH transmission includes two SRI fields and the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'nonCodebook', the UE obtains a mapping from *sri-PUSCH-PowerControlId* in *SRI-PUSCH-PowerControl* between + - a set of values for the first SRI field value and a set of indexes provided by *p0-PUSCH-AlphaSetId* that map to a set of *P0-PUSCH-AlphaSet* values, and determines the first value of from the *p0-PUSCH-AlphaSetId* value that is mapped to the first SRI field value, and + - a set of values associated with the second SRI field value for a same number of layers as indicated by the first SRI field [5, TS 38.212], and a set of indexes provided by *p0-PUSCH-AlphaSetId* that map to a set of *P0-PUSCH-AlphaSet* values, and determines the second value of from the *p0-PUSCH-AlphaSetId* value that is mapped to the second SRI field value corresponding to Tables 7.3.1.1.2-28/29/30/31 of [5, TS 38.212]. +- If the DCI format also includes an open-loop power control parameter set indication field and a value of the open-loop power control parameter set indication field is '1' and if the DCI format scheduling the PUSCH transmission includes an SRI field, the UE determines a value of from a first value in *P0-PUSCH-Set* with a *p0-PUSCH-SetId* value mapped to the SRI field value. +- If the UE is provided by *SRI-PUSCH-PowerControl* more than one values of *p0-PUSCH-AlphaSetId* + - if a DCI format scheduling the PUSCH transmission includes two SRI fields and an open-loop power control parameter set indication field and the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' + - if a value of the open-loop power control parameter set indication field is '0', the UE determines two values of from the *p0-PUSCH-AlphaSetId* values in *SRI-PUSCH-PowerControl* that are mapped to the two SRI values corresponding to each SRS resource set with *usage* set to 'codebook'. + - if a value of the open-loop power control parameter set indication field is '1', the UE determines two values of from first values in *P0-PUSCH-Set* in *P0-PUSCH-SetList* and *P0-PUSCH-Set* in *P0-PUSCH-SetList2* with *p0-PUSCH-SetId* values mapped to the two SRI values corresponding to each SRS resource set with *usage* set to 'codebook', respectively. + - if a DCI format scheduling the PUSCH transmission includes two SRI fields and an open-loop power control parameter set indication field and the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'nonCodebook', + - if a value of the open-loop power control parameter set indication field is '0', the UE determines two values of from the *p0-PUSCH-AlphaSetId* values in *SRI-PUSCH-PowerControl* that are mapped to the first SRI field value corresponding to the first SRS resource set with *usage* set to 'nonCodebook' and to a second value, that is associated with the second SRI field value corresponding to Tables 7.3.1.1.2-28/29/30/31 of [5, TS 38.212] for a same number of layers as indicated by the first SRI field value, corresponding to the second SRS resource set with *usage* set to 'nonCodebook'. + - if a value of the open-loop power control parameter set indication field is '1', the UE determines two values of from first values in *P0-PUSCH-Set* in *P0-PUSCH-SetList* and *P0-PUSCH-Set* in *P0-PUSCH-SetList2* with *p0-PUSCH-SetId* values mapped to the first SRI field value corresponding to the first SRS resource set with *usage* set to 'nonCodebook', and a second value, that is associated with the second SRI field value corresponding to Tables 7.3.1.1.2-28/29/30/31 of [5, TS 38.212] for a same number of layers as indicated by the first SRI field value, corresponding to the second SRS resource set with *usage* set to 'nonCodebook', respectively. + +- if the UE is not provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook' and if the PUSCH transmission, except for the PUSCH retransmission corresponding to a RAR UL grant, is scheduled by a DCI format that does not include an SRI field, or if *SRI-PUSCH-PowerControl* is not provided to the UE, + - if *P0-PUSCH-Set* is provided to the UE and the DCI format includes an open-loop power control parameter set indication field, the UE determines a value of *f* from + - a first *P0-PUSCH-AlphaSet* in *p0-AlphaSets* if a value of the open-loop power control parameter set indication field is '0' or '00' + - a first value in *P0-PUSCH-Set* with the lowest *p0-PUSCH-SetID* value if a value of the open-loop power control parameter set indication field is '1' or '01' + - a second value in *P0-PUSCH-Set* with the lowest *p0-PUSCH-SetID* value if a value of the open-loop power control parameter set indication field is '10' + - else, the UE determines *f* from the value of the first *P0-PUSCH-AlphaSet* in *p0-AlphaSets* +- if the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook' and the PUSCH transmission is scheduled by a DCI format that does not include an SRI field and includes an SRS resource set indicator field with value 10 or 11 + - if *P0-PUSCH-Set* is provided to the UE and the DCI format includes an open-loop power control parameter set indication field, the UE determines first and second values of *f* respectively associated with the first and second SRS resource set as + - first and second *P0-PUSCH-AlphaSet* in *p0-AlphaSets* if the open-loop power control parameter set indication value is '0' or '00' + - first value in *P0-PUSCH-Set* with the lowest *p0-PUSCH-SetID* value in *p0-PUSCH-SetList* and first value in *P0-PUSCH-Set* with the lowest *p0-PUSCH-SetID* value in *p0-PUSCH-SetList2*, respectively, if the open-loop power control parameter set indication value is '1' or '01' + - second value in *P0-PUSCH-Set* with the lowest *p0-PUSCH-SetID* value in *p0-PUSCH-SetList* and second value in *P0-PUSCH-Set* with the lowest *p0-PUSCH-SetID* in *p0-PUSCH-SetList2*, respectively, if the open-loop power control parameter set indication value is '10' or '11' + - else, the UE determines first and second values *f* respectively associated with the first and second SRS resource set from the values of the first and second *P0-PUSCH-AlphaSet* in *p0-AlphaSets*, respectively +- if the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook', and the PUSCH transmission is scheduled by a DCI format that does not include an SRI field and includes an SRS resource set indicator field with value '00' + - if the UE is provided *P0-PUSCH-Set* and the DCI format includes an open-loop power control parameter set indication field, the UE determines a value of *f* as + - first *P0-PUSCH-AlphaSet* in *p0-AlphaSets* if the open-loop power control parameter set indication value is '0' or '00' + - first value in *P0-PUSCH-Set* with the lowest *p0-PUSCH-SetID* value in *p0-PUSCH-SetList*, if the open-loop power control parameter set indication value is '1' or '01' + - second value in *P0-PUSCH-Set* with the lowest *p0-PUSCH-SetID* value in *p0-PUSCH-SetList*, if the open-loop power control parameter set indication value is '10' or '11' + - else, the UE determines a value of *f* from the value of the first *P0-PUSCH-AlphaSet* in *p0-AlphaSets* +- if the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook', and the PUSCH + +transmission is scheduled by a DCI format that does not include an SRI field and includes an SRS resource set indicator field with value '01' + +- if *P0-PUSCH-Set* is provided to the UE and the DCI format includes an open-loop power control parameter set indication field, the UE determines a value of $\alpha$ as + - second *P0-PUSCH-AlphaSet* in *p0-AlphaSets* if the open-loop power control parameter set indication value is '0' or '00' + - first value in *P0-PUSCH-Set* with the lowest *p0-PUSCH-SetID* value in *p0-PUSCH-SetList2*, if the open-loop power control parameter set indication value is '1' or '01' + - second value in *P0-PUSCH-Set* with the lowest *p0-PUSCH-SetID* in *p0-PUSCH-SetList2*, if the open-loop power control parameter set indication value is '10' or '11' +- else, the UE determines a value of $\alpha$ from the value of the second *P0-PUSCH-AlphaSet* in *p0-AlphaSets* +- For $\alpha$ + - For $\alpha$ , + - if $\alpha$ and *msgA-Alpha* is provided, $\alpha$ is the value of *msgA-Alpha* + - elseif $\alpha$ or *msgA-Alpha* is not provided, and *msg3-Alpha* is provided, $\alpha$ is the value of *msg3-Alpha* + - else, $\alpha$ + - For $\alpha$ , + - if the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook' and is provided *p0-PUSCH-Alpha2*, for a retransmission of a configured grant Type 1 PUSCH, or for activation or retransmission of a configured grant Type 2 PUSCH, scheduled by a DCI format that includes an SRS resource set indicator field, and for active UL BWP of carrier of serving cell + - if the SRS resource set indicator value is '00', first $\alpha$ value is provided by *p0-PUSCH-Alpha* in *ConfiguredGrantConfig* + - if the SRS resource set indicator value is '01', first $\alpha$ value is provided by *p0-PUSCH-Alpha2* in *ConfiguredGrantConfig* + - if the SRS resource set indicator value is '10' or '11', first and second $\alpha$ values associated with the first and second SRS resource set are respectively provided by *p0-PUSCH-Alpha* and *p0-PUSCH-Alpha2* in *ConfiguredGrantConfig* + - else if the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook' and is provided *p0-PUSCH-Alpha2*, for a transmission of a configured grant Type 1 PUSCH and for active UL BWP of carrier of serving cell + - a first $\alpha$ value is provided by the value of *p0-PUSCH-Alpha* in *ConfiguredGrantConfig* that is associated with the first *srs-ResourceIndicator* in *rrc-ConfiguredUplinkGrant*. + - a second $\alpha$ value is provided by the value of *p0-PUSCH-Alpha2* in *ConfiguredGrantConfig* that is associated with the second *srs-ResourceIndicator* in *rrc-ConfiguredUplinkGrant*. + - else if the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook' and is provided *p0-PUSCH-Alpha2*, for a retransmission of a configured grant Type 1 PUSCH, or for activation or retransmission of a configured grant Type 2 PUSCH, scheduled by a DCI format 0\_0 and for active UL BWP of carrier of serving cell + - a first $\alpha$ value is provided by the value of *p0-PUSCH-Alpha* in *ConfiguredGrantConfig*. + +- else is provided by *alpha* obtained from *p0-PUSCH-Alpha* in *ConfiguredGrantConfig* providing an index *P0-PUSCH-AlphaSetId* to a set of *P0-PUSCH-AlphaSet*, or by *sdt-Alpha* for a PUSCH (re)transmission as described in clause 19.1, for active UL BWP of carrier of serving cell +- For , a set of values are provided by a set of *alpha* in *P0-PUSCH-AlphaSet* indicated by a respective set of *p0-PUSCH-AlphaSetId* for active UL BWP of carrier of serving cell +- If the UE is provided *SRI-PUSCH-PowerControl* and more than one values of *p0-PUSCH-AlphaSetId* in *p0-AlphaSets*, + - if a DCI format scheduling the PUSCH transmission includes two SRI fields and the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook', the UE obtains a mapping from *sri-PUSCH-PowerControlId* in *SRI-PUSCH-PowerControl* between a set of values for + - the two SRI fields and a set of indexes provided by *P0-PUSCH-AlphaSetId* that map to *P0-PUSCH-AlphaSet* values, and determines first and second values of from the *P0-PUSCH-AlphaSetID* values that are mapped to the values of the first and second SRI field values, respectively. + - if a DCI format scheduling the PUSCH transmission includes two SRI fields and the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'nonCodebook', the UE obtains a mapping from *sri-PUSCH-PowerControlId* in *SRI-PUSCH-PowerControl* between a set of values for + - the first SRI field and a set of indexes provided by *P0-PUSCH-AlphaSetId* that map to *P0-PUSCH-AlphaSet* values, and determines first value of from the *P0-PUSCH-AlphaSetID* value that is mapped to the first SRI field value, and + - the second value, associated with the second SRI field value corresponding to Tables 7.3.1.1.2-28/29/30/31 of [5, TS 38.212] for a same number of layers as indicated by the first SRI field value, and a set of indexes provided by *p0-PUSCH-AlphaSetId* that map to a set of *P0-PUSCH-AlphaSet* values, and determines the second value of from the *p0-PUSCH-AlphaSetId* value that is mapped to the second SRI field value + - if a DCI format scheduling the PUSCH transmission includes one SRI field, the UE obtains a mapping from *sri-PUSCH-PowerControlId* in *SRI-PUSCH-PowerControl* between a set of values for the SRI field in the DCI format [5, TS 38.212] and a set of indexes provided by *p0-PUSCH-AlphaSetId* that map to a set of *P0-PUSCH-AlphaSet* values and determines the values of from the *p0-PUSCH-AlphaSetId* value that is mapped to the SRI field value +- If the UE is not provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook' and if the PUSCH transmission except for the PUSCH retransmission corresponding to a RAR UL grant is scheduled by a DCI format that does not include an SRI field, or if *SRI-PUSCH-PowerControl* is not provided to the UE, , and the UE determines from the value of the first *P0-PUSCH-AlphaSet* in *p0-AlphaSets* +- If the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook' and the PUSCH transmission is scheduled by a DCI format that does not include an SRI field and includes an SRS resource set indicator field with value '10' or '11', the UE determines respectively associated with the first and second SRS resource set from first and second *P0-PUSCH-AlphaSet* in *p0-AlphaSets* +- If the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook', and the PUSCH transmission is scheduled by a DCI format that does not include an SRI field and includes an SRS resource set indicator field with value '00' or '01', the UE determines from first *P0-PUSCH-AlphaSet* or second *P0-PUSCH-AlphaSet* in *p0-AlphaSets*, respectively. +- is the bandwidth of the PUSCH resource assignment expressed in number of resource blocks for PUSCH transmission occasion on active UL BWP of carrier of serving cell and is a SCS configuration defined in [4, TS 38.211] + +- is a downlink pathloss estimate in dB calculated by the UE using reference signal (RS) index for the active DL BWP, as described in clause 12, of carrier of serving cell +- If the UE is not provided *PUSCH-PathlossReferenceRS* and *enableDefaultBeamPL-ForSRS*, or before the UE is provided dedicated higher layer parameters, the UE calculates + - using a RS resource from an SS/PBCH block with same SS/PBCH block index as the one the UE uses to obtain *MIB*, or using the SS/PBCH block the UE acquired the time and frequency synchronization for a secondary cell. + - if the UE is provided *ntn-RACH-LessHO* in *ReconfigurationWithSync* [12. TS 38.331], using a RS resource from an SS/PBCH block with same SS/PBCH block index as the one with same quasi co-location properties as for PDCCH receptions for scheduling an initial PUSCH transmission, as described in Clause 10.1, in *controlResourceSetZero* provided in *ServingCellConfigCommon* of *ReconfigurationWithSync* +- If the UE is configured with a number of RS resource indexes, up to the value of *maxNrofPUSCH-PathlossReferenceRSs*, and a respective set of RS configurations for the number of RS resource indexes by *PUSCH-PathlossReferenceRS*, the set of RS resource indexes can include one or both of a set of SS/PBCH block indexes, each provided by *ssb-Index* when a value of a corresponding *pusch-PathlossReferenceRS-Id* maps to a SS/PBCH block index, and a set of CSI-RS resource indexes, each provided by *csi-RS-Index* when a value of a corresponding *pusch-PathlossReferenceRS-Id* maps to a CSI-RS resource index. The UE identifies a RS resource index in the set of RS resource indexes to correspond either to a SS/PBCH block index or to a CSI-RS resource index as provided by *pusch-PathlossReferenceRS-Id* in *PUSCH-PathlossReferenceRS* +- If the PUSCH transmission is scheduled by a RAR UL grant as described in clause 8.3, or for a PUSCH transmission for Type-2 random access procedure as described in clause 8.1A, the UE uses the same RS resource index as for a corresponding PRACH transmission +- If the UE is provided *SRI-PUSCH-PowerControl* and more than one values of *PUSCH-PathlossReferenceRS-Id*, the UE obtains a mapping from *sri-PUSCH-PowerControlId* in *SRI-PUSCH-PowerControl* between a set of values for the SRI field, or for first and second SRI fields if the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook', or values for a first SRI field and values associated with a second SRI field value corresponding to Tables 7.3.1.1.2-28/29/30/31 of [5, TS 38.212] for a same number of layers as indicated by the first SRI field value if the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'nonCodebook', in a DCI format scheduling the PUSCH transmission and a set of *PUSCH-PathlossReferenceRS-Id* values and determines the RS resource index, or respective first and second RS resource indexes, from the value of *PUSCH-PathlossReferenceRS-Id* that is mapped to the SRI field value, or from the values of *PUSCH-PathlossReferenceRS-Id* that are mapped to respective first and second SRI field values if the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook', or from the values of *PUSCH-PathlossReferenceRS-Id* that are mapped to respective first SRI field value and a value associated with the second SRI field value corresponding to Tables 7.3.1.1.2-28/29/30/31 of [5, TS 38.212] for a same number of layers as indicated by the first SRI field value if the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'nonCodebook', + +where the RS resource is either on serving cell or, if provided, on a serving cell indicated by a value of *pathlossReferenceLinking* + +- If the PUSCH transmission is scheduled by DCI format 0\_0, and + - if two spatial settings from *PUCCH-SpatialRelationInfo* are activated for a PUCCH resource with a lowest index for active UL BWP of each carrier and serving cell, the UE uses the same RS resource index as for a PUCCH transmission with a spatial setting from the two spatial settings with lowest index in the PUCCH resource with the lowest index for active UL BWP of each carrier and serving cell + - else, if the UE is provided a spatial setting by *PUCCH-SpatialRelationInfo* for a PUCCH resource with a lowest index for active UL BWP of each carrier and serving cell, as described in clause 9.2.2, the UE uses the same RS resource index as for a PUCCH transmission in the PUCCH resource with the lowest index + +- If the PUSCH transmission is not scheduled by DCI format 0\_0, and if the UE is provided *enableDefaultBeamPL-ForSRS* and is not provided *PUSCH-PathlossReferenceRS* and *PUSCH-PathlossReferenceRS-r16*, the UE uses the same RS resource index as for an SRS resource set with an SRS resource associated with the PUSCH transmission +- If + - the UE is not provided *enableDefaultBeamPL-ForPUSCH0-0* and the PUSCH transmission is scheduled by DCI format 0\_0 and the UE is not provided a spatial setting for a PUCCH transmission, or + - the PUSCH transmission is scheduled by DCI format 0\_1 or DCI format 0\_2 that does not include an SRI field, or + - *SRI-PUSCH-PowerControl* is not provided to the UE, + +the UE determines a RS resource index with a respective *PUSCH-PathlossReferenceRS-Id* value being equal to zero where the RS resource is either on serving cell or, if provided, on a serving cell indicated by a value of *pathlossReferenceLinking* + +- If + - the PUSCH transmission is scheduled by DCI format 0\_0 on serving cell , + - the UE is not provided PUCCH resources for the active UL BWP of serving cell , and + - the UE is provided *enableDefaultBeamPL-ForPUSCH0-0* + +the UE determines a RS resource index providing a periodic RS resource configured with *qcl-Type* set to 'typeD' in the TCI state or the QCL assumption of a CORESET with the lowest index in the active DL BWP of the serving cell . If the CORESET has two activated TCI states, as described in clause 10.1, the UE determines the RS resource index based on the first TCI state. + +- If + - the PUSCH transmission is scheduled by DCI format 0\_0 on serving cell , + - the UE is not provided a spatial setting for PUCCH resources on the active UL BWP of the primary cell [11, TS 38.321], and + - the UE is provided *enableDefaultBeamPL-ForPUSCH0-0* + +the UE determines a RS resource index providing a periodic RS resource configured with *qcl-Type* set to 'typeD' in the TCI state or the QCL assumption of a CORESET with the lowest index in the active DL BWP of the serving cell . If the CORESET has two activated TCI states, as described in clause 10.1, the UE determines the RS resource index based on the first TCI state. + +- For a PUSCH transmission configured by *ConfiguredGrantConfig*, if *rrc-ConfiguredUplinkGrant* is included in *ConfiguredGrantConfig*, + - if the UE is provided *enablePL-RS-UpdateForType1CG-PUSCH*, the UE determines a RS resource index from the value of *PUSCH-PathlossReferenceRS-Id* that is mapped to the *sri-PUSCH-PowerControlId* indicated by the *srs-ResourceIndicator* value included in *rrc-ConfiguredUplinkGrant* + - if the UE is not provided *enablePL-RS-UpdateForType1CG-PUSCH*, a RS resource index is provided by a value of *pathlossReferenceIndex* included in *rrc-ConfiguredUplinkGrant* where the RS resource is either on serving cell or, if provided, on a serving cell indicated by a value of *pathlossReferenceLinking*. If the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook' and for configured grant Type 1 PUSCH, first and second RS resource indexes that are respectively associated with the first and second *srs-ResourceIndicator* in *rrc-ConfiguredUplinkGrant* are provided by respective values of *pathlossReferenceIndex* and *pathlossReferenceIndex2* in *rrc-ConfiguredUplinkGrant*. +- For a PUSCH transmission configured by *ConfiguredGrantConfig* that does not include *rrc-ConfiguredUplinkGrant*, the UE determines a RS resource index from a value of *PUSCH-PathlossReferenceRS-Id* that is mapped to a SRI field value in a DCI format activating the PUSCH transmission. + +- If the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' and the DCI format activating the PUSCH transmission includes two SRI fields, the UE determines first and second RS resource indexes from respective first and second values of *PUSCH-PathlossReferenceRS-Id* that are mapped to the first and second SRI values corresponding to each SRS resource set with *usage* set to 'codebook', respectively. +- If the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'nonCodebook' and the DCI format activating the PUSCH transmission includes two SRI fields, the UE determines first and second RS resource indexes from respective first and second values of *PUSCH-PathlossReferenceRS-Id* that are mapped to the first SRI value corresponding to the first SRS resource set with *usage* set to 'nonCodebook', and the value, associated with the second SRI field value corresponding to Tables 7.3.1.1.2-28/29/30/31 of [5, TS 38.212] for a same number of layers as indicated by the first SRI field value, corresponding to the second SRS resource set with *usage* set to 'nonCodebook'. +- If the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook' and the DCI format activating the PUSCH transmission does not include an SRI field, the UE determines first and second RS resource indexes respectively associated with the first and second SRS resource set with respective first and second *PUSCH-PathlossReferenceRS-Id* value being equal to zero and one. +- If the DCI format activating the PUSCH transmission does not include an SRI field, the UE determines a RS resource index with a respective *PUSCH-PathlossReferenceRS-Id* value being equal to zero + +where the RS resources are either on serving cell or, if provided, on a serving cell indicated by a value of *pathlossReferenceLinking* + +- If the UE is provided *enablePL-RS-UpdateForPUSCH-SRS*, a mapping between *sri-PUSCH-PowerControlId* and *PUSCH-PathlossReferenceRS-Id* values can be updated by a MAC CE as described in [11, TS 38.321] +- For a PUSCH transmission scheduled by a DCI format that does not include an SRI field, or for a PUSCH transmission configured by *ConfiguredGrantConfig* and activated, as described in clause 10.2, by a DCI format that does not include an SRI field, the UE determines a RS resource index from the *PUSCH-PathlossReferenceRS-Id* mapped to *sri-PUSCH-PowerControlId* = 0. If the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook', the UE determines first and second RS resource indexes from respective *PUSCH-PathlossReferenceRS-Id* mapped to *sri-PUSCH-PowerControlId* = 0 of *sri-PUSCH-MappingToAddModList* and *sri-PUSCH-PowerControlId* = 0 of *sri-PUSCH-MappingToAddModList2*, respectively. +- If the UE is not provided *enablePL-RS-UpdateForPUSCH-SRS* + - For a PUSCH transmission scheduled by a DCI format that does not include an SRI field, if the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook', the UE determines first and second RS resource indexes respectively associated with the first and second SRS resource set with respective first and second *PUSCH-PathlossReferenceRS-Id* values being equal to 0 and 1. + += *referenceSignalPower* – higher layer filtered RSRP, where *referenceSignalPower* is provided by higher layers and RSRP is defined in [7, TS 38.215] for the reference serving cell and the higher layer filter configuration provided by *QuantityConfig* is defined in [12, TS 38.331] for the reference serving cell + +If the UE is not configured periodic CSI-RS reception, *referenceSignalPower* is provided by *ss-PBCH-BlockPower*. If the UE is configured periodic CSI-RS reception, *referenceSignalPower* is provided either by *ss-PBCH-BlockPower* or by *powerControlOffsetSS* providing an offset of the CSI-RS transmission power relative to the SS/PBCH block transmission power [6, TS 38.214]. If *powerControlOffsetSS* is not provided to the UE, the UE assumes an offset of 0 dB. + +- for and for where is provided by *deltaMCS* for each UL BWP of each carrier and serving cell. If the PUSCH transmission is over more than one layer [6, TS 38.214], . and , for active UL BWP of each carrier and each serving cell, are computed as below + - for PUSCH with UL-SCH data and for CSI transmission in a PUSCH without UL-SCH data, where + +- $\beta$ is a number of transmitted code blocks, $\beta$ is a size for code block, and $\beta$ is a number of resource elements determined as $\beta$ , where $\beta$ is provided by *numberOfSlotsTBoMS* as described in [6, TS 38.214] and if *numberOfSlotsTBoMS* is not provided, $\beta$ is a number of symbols for PUSCH transmission occasion on active UL BWP of carrier of serving cell, $\beta$ is a number of subcarriers excluding DM-RS subcarriers and phase-tracking RS samples [4, TS 38.211] in PUSCH symbol and assuming no segmentation for a nominal repetition in case the PUSCH transmission is with repetition Type B, $\beta$ , and $\beta$ , are defined in [5, TS 38.212] +- when the PUSCH includes UL-SCH data and $\beta$ , as described in clause 9.3, when the PUSCH includes CSI and does not include UL-SCH data +- $\beta$ is the modulation order and $\beta$ is the target code rate, as described in [6, TS 38.214], provided by the DCI format scheduling the PUSCH transmission that includes CSI and does not include UL-SCH data +- For the PUSCH power control adjustment state for active UL BWP of carrier of serving cell in PUSCH transmission occasion +- $\beta$ is a TPC command value included in a DCI format that schedules the PUSCH transmission occasion on active UL BWP of carrier of serving cell or jointly coded with other TPC commands in a DCI format 2\_2 with CRC scrambled by TPC-PUSCH-RNTI, as described in clause 11.3 +- if the UE is configured with *twoPUSCH-PC-AdjustmentStates* and if the UE is not configured with *twoPUSCH-PC-AdjustmentStates* or if the PUSCH transmission is scheduled by a RAR UL grant as described in clause 8.3 + - if the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook', and is provided *p0-PUSCH-Alpha2*, for a retransmission of a configured grant Type 1 PUSCH, or for activation or retransmission of a configured grant Type 2 PUSCH, scheduled by a DCI format that includes a SRS resource set indicator field, and for active UL BWP of carrier of serving cell + - if the SRS resource set indicator value is 00, $\beta$ is equal to the value of *powerControlLoopToUse* in *ConfiguredGrantConfig* + - if the SRS resource set indicator value is 01, $\beta$ is equal to the value of *powerControlLoopToUse2* in *ConfiguredGrantConfig* + - if the SRS resource set indicator value is 10 or 11, a first $\beta$ and a second $\beta$ respectively associated with the first and second SRS resource set are respectively equal to *powerControlLoopToUse* and *powerControlLoopToUse2* in *ConfiguredGrantConfig* + - else if the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook' and is provided *p0-PUSCH-Alpha2*, for a transmission of a configured grant Type 1 PUSCH and for active UL BWP of carrier of serving cell + - a first $\beta$ is equal to the value of *powerControlLoopToUse* in *ConfiguredGrantConfig* that is associated with the first *srs-ResourceIndicator* in *rrc-ConfiguredUplinkGrant* + - a second $\beta$ is equal to the value of *powerControlLoopToUse2* in *ConfiguredGrantConfig* that is associated with the second *srs-ResourceIndicator* in *rrc-ConfiguredUplinkGrant* + - else if the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook' and is provided *p0-PUSCH-Alpha2*, for a retransmission of a configured grant Type 1 PUSCH, or for activation or retransmission of a configured grant Type 2 PUSCH, scheduled by a DCI format 0\_0 and for active UL BWP of carrier of serving cell + - $\beta$ is equal to the value of *powerControlLoopToUse* in *ConfiguredGrantConfig* + - else, for a PUSCH (re)transmission configured by *ConfiguredGrantConfig*, the value of $\beta$ is provided to the UE by *powerControlLoopToUse* in *ConfiguredGrantConfig*. + - If the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook', is provided *SRI-PUSCH-* + +*PowerControl*, and a DCI format scheduling the PUSCH transmission includes two SRI fields, the UE obtains a mapping from *sri-PUSCH-PowerControlId* in *SRI-PUSCH-PowerControl* between a set of values for the first and second SRI fields and the values provided by *sri-PUSCH-ClosedLoopIndex*, and determines the values mapped to the values of the first and second SRI fields corresponding to each SRS resource set with *usage* set to 'codebook', respectively + +- If the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'nonCodebook', is provided *SRI-PUSCH-PowerControl*, and a DCI format scheduling the PUSCH transmission includes two SRI fields, the UE obtains a mapping from *sri-PUSCH-PowerControlId* in *SRI-PUSCH-PowerControl* between a set of values for + - the first SRI field value and the values provided by *sri-PUSCH-ClosedLoopIndex*, and determines the value that is mapped to the first SRI field value corresponding to the first SRS resource set with *usage* set to 'nonCodebook', and + - the value, associated with the second SRI field value corresponding to Tables 7.3.1.1.2-28/29/30/31 of [5, TS 38.212] for a same number of layers as indicated by the first SRI field value, and the value(s) provided by *sri-PUSCH-ClosedLoopIndex*, and determines the value that is mapped to the value corresponding to the second SRS resource set with *usage* set to 'nonCodebook' +- If the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook', is provided *SRI-PUSCH-PowerControl*, and a DCI format scheduling the PUSCH transmission does not include an SRI field + - If the UE is provided two *PUSCH-PC-AdjustmentStates* + - the UE determines for the PUSCH transmission corresponding to the first SRS resource set with *usage* set to 'codebook' or 'nonCodebook', and for the PUSCH transmission corresponding to the second SRS resource set with *usage* set to 'codebook' or 'nonCodebook' + - else + - the UE determines for the PUSCH transmission +- If the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook', and is provided two *PUSCH-PC-AdjustmentStates* + - If the DCI format includes two TPC command values and the PUSCH transmissions are associated with *id* and *id*, the UE applies the first TPC command value for *id* and applies the second TPC command value for *id* + - If the DCI format includes two TPC command values and the PUSCH transmissions are associated with *id*, the UE applies the first TPC command value for *id* and ignores the second TPC command value + - If the DCI format includes two TPC command values and the PUSCH transmissions are associated with *id*, the UE applies the second TPC command value for *id* and ignores the first TPC command value + - If the DCI format includes one TPC command value, the UE applies the TPC command value for all associated with the PUSCH transmission +- If the UE is provided *SRI-PUSCH-PowerControl*, the UE obtains a mapping between a set of values for the SRI field in a DCI format scheduling the PUSCH transmission and the value(s) provided by *sri-PUSCH-ClosedLoopIndex* and determines the value that is mapped to the SRI field value +- If the PUSCH transmission is scheduled by a DCI format that does not include an SRI field, or if an *SRI-PUSCH-PowerControl* is not provided to the UE, +- If the UE obtains one TPC command from a DCI format 2\_2 with CRC scrambled by a TPC-PUSCH-RNTI, the value is provided by the closed loop indicator field in DCI format 2\_2 + +- is the PUSCH power control adjustment state for active UL BWP of carrier of serving cell and PUSCH transmission occasion $i$ if the UE is not provided *tpc-Accumulation*, where + - The values are given in Table 7.1.1-1 + - is a sum of TPC command values in a set of TPC command values with cardinality $N$ that the UE receives between symbols before PUSCH transmission occasion $i$ and symbols before PUSCH transmission occasion $i$ on active UL BWP of carrier of serving cell for PUSCH power control adjustment state $i$ , where $N$ is the smallest integer for which symbols before PUSCH transmission occasion $i$ is earlier than symbols before PUSCH transmission occasion $i$ + - If a PUSCH transmission is scheduled by a DCI format, $N$ is a number of symbols for active UL BWP of carrier of serving cell after a last symbol of a corresponding PDCCH reception and before a first symbol of the PUSCH transmission + - If a PUSCH transmission is configured by *ConfiguredGrantConfig*, $N$ is a number of symbols equal to the product of a number of symbols per slot, $k$ , and the minimum of the values provided by $k2$ in *PUSCH-ConfigCommon* for active UL BWP of carrier of serving cell + - If the first symbol of the PUSCH transmission occasion occurs within $T_{prep}$ after a last symbol of a PDCCH reception where the UE detects the DCI format providing the TPC command, the UE may postpone the application of the TPC command until the above condition is not valid. $T_{prep}$ is the PUSCH preparation time for the corresponding UE processing capability [6, TS 38.214] assuming $\mu$ , and corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH carrying the DCI format and the SCS configuration of the PUSCH. + - If the UE has reached maximum power for active UL BWP of carrier of serving cell at PUSCH transmission occasion $i$ and $\mu$ , then + - If UE has reached minimum power for active UL BWP of carrier of serving cell at PUSCH transmission occasion $i$ and $\mu$ , then + - A UE resets accumulation of a PUSCH power control adjustment state for active UL BWP of carrier of serving cell to + - If a configuration for a corresponding $\alpha$ value is provided by higher layers + - If a configuration for a corresponding $\alpha$ value is provided by higher layers +- where $\alpha$ is determined from the value of $\alpha$ as +- If $\alpha$ and the UE is provided higher *SRI-PUSCH-PowerControl*, $\alpha$ is the *sri-PUSCH-ClosedLoopIndex* value(s) configured in any *SRI-PUSCH-PowerControl* with the *sri-P0-PUSCH-AlphaSetId* value corresponding to + - If $\alpha$ and the UE is not provided *SRI-PUSCH-PowerControl* or $\alpha$ , if $\alpha$ and $\mu$ are provided by the second $\alpha$ ; otherwise, + - If $\alpha$ , + - $\alpha$ is provided by the value of *powerControlLoopToUse* if $\alpha$ and $\mu$ are provided by *p0-PUSCH-Alpha* in *ConfiguredGrantConfig* + - $\alpha$ is provided by the value of *powerControlLoopToUse2* if $\alpha$ and $\mu$ are provided by *p0-PUSCH-Alpha2* in *ConfiguredGrantConfig* +- is the PUSCH power control adjustment state for active UL BWP of carrier of serving cell and PUSCH transmission occasion $i$ if the UE is provided *tpc-Accumulation*, where +- absolute values are given in Table 7.1.1-1 + +If the UE transmits a PUSCH associated with the first RS resource index $\alpha$ , the UE applies the first $\alpha$ value, the first $\alpha$ value, and $\mu$ for determining $\alpha$ . If the UE transmits a PUSCH associated with the second RS resource index $\alpha$ , the UE applies the second $\alpha$ value, the second $\alpha$ value, and $\mu$ or if *twoPUSCH-PC-AdjustmentStates* is provided or not provided, respectively, for determining $\alpha$ . + +- If the UE receives a random access response message in response to a PRACH transmission or a MsgA transmission on active UL BWP of carrier of serving cell as described in clause 8 +- , where and +- is a TPC command value indicated in a random access response grant of the random access response message corresponding to a PRACH transmission according to Type-1 random access procedure, or in a random access response grant of the random access response message corresponding to a MsgA transmission according to Type-2 random access procedure with RAR message(s) for fallbackRAR, on active UL BWP of carrier of serving cell , and + +$$\Delta P_{rampup,b,f,c} = \min \left\{ \max \left( 0, P_{CMAX,f,c} - \left( \begin{array}{c} 10 \log_{10}(2^{\mu} \cdot M_{RB,b,f,c}^{PUSCH}(0)) \\ + P_{O\_PUSCH,b,f,c}(0) + \alpha_{b,f,c}(0) \cdot PL_c \\ + \Delta_{TF,b,f,c}(0) + \delta_{msg2,b,f,c} \end{array} \right) \right) \right\}, \quad \Delta P_{rampuprequested,b,f,c}$$ + +and is provided by higher layers and corresponds to the total power ramp-up requested by higher layers from the first to the last random access preamble for carrier in the serving cell , is the bandwidth of the PUSCH resource assignment expressed in number of resource blocks for the first PUSCH transmission on active UL BWP of carrier of serving cell , and is the power adjustment of first PUSCH transmission on active UL BWP of carrier of serving cell . + +- If the UE transmits the PUSCH in PUSCH transmission occasion on active UL BWP of carrier of serving cell as described in clause 8.1A, , where + +- , and + +$$\Delta P_{rampup,b,f,c} = \min \left\{ \max \left( 0, P_{CMAX,f,c} - \left( \begin{array}{c} 10 \log_{10}(2^{\mu} \cdot M_{RB,b,f,c}^{PUSCH}(i)) \\ + P_{O\_PUSCH,b,f,c}(0) + \alpha_{b,f,c}(0) \cdot PL_c(i) \\ + \Delta_{TF,b,f,c}(i) \end{array} \right) \right) \right\}, \quad \Delta P_{rampuprequested,b,f,c}$$ + +and is provided by higher layers and corresponds to the total power ramp-up requested by higher layers, is the bandwidth of the PUSCH resource assignment expressed in number of resource blocks, and is the power adjustment of the PUSCH transmission in PUSCH transmission occasion . + +**Table 7.1.1-1: Mapping of TPC Command Field in a DCI format scheduling a PUSCH transmission, or in DCI format 2\_2 with CRC scrambled by TPC-PUSCH-RNTI, or in DCI format 2\_3, to absolute and accumulated values or values** + +| TPC Command Field | Accumulated or [dB] | Absolute or [dB] | +|-------------------|---------------------|------------------| +| 0 | -1 | -4 | +| 1 | 0 | -1 | +| 2 | 1 | 1 | +| 3 | 3 | 4 | + +## 7.2 Physical uplink control channel + +If the UE is configured with a SCG, the UE shall apply the procedures described in this clause for both MCG and SCG. + +- When the procedures are applied for MCG, the term 'serving cell' in this clause refers to serving cell belonging to the MCG. +- When the procedures are applied for SCG, the term 'serving cell' in this clause refers to serving cell belonging to the SCG. The term 'primary cell' in this clause refers to the PSCell of the SCG. + +If the UE is configured with a PUCCH-SCell, the UE shall apply the procedures described in this clause for both primary PUCCH group and secondary PUCCH group. + +- When the procedures are applied for the primary PUCCH group, the term 'serving cell' in this clause refers to serving cell belonging to the primary PUCCH group. +- When the procedures are applied for the secondary PUCCH group, the term 'serving cell' in this clause refers to serving cell belonging to the secondary PUCCH group. The term 'primary cell' in this clause refers to the + +PUCCH-SCell of the secondary PUCCH group. If *pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup-r16* is provided, *pdsch-HARQ-ACK-Codebook* is replaced by *pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup-r16*. + +For unpaired spectrum operation, if the UE is provided a PUCCH-sSCell by *pucch-sSCell* as described in clause 9.A, the UE shall apply the procedures described in this clause for both the primary cell and the PUCCH-sSCell. + +### 7.2.1 UE behaviour + +If a UE transmits a PUCCH on active UL BWP of carrier in the primary cell using PUCCH power control adjustment state with index $i$ , the UE determines the PUCCH transmission power in PUCCH transmission occasion $l$ as + +$$P_{\text{PUCCH},b,f,c}(i, q_u, q_d, l) = \min \left\{ \begin{array}{l} P_{\text{CMAX},f,c}(i), \\ P_{0\_ \text{PUCCH},b,f,c}(q_u) + 10 \log_{10}(2^{\mu} \cdot M_{\text{RB},b,f,c}^{\text{PUCCH}}(i)) + PL_{b,f,c}(q_d) + \Delta_{F\_ \text{PUCCH}}(F) + \Delta_{\text{TF},b,f,c}(i) + g_{b,f,c}(i, l) \end{array} \right\} \text{ [dBm]}$$ + +where + +- is the UE configured maximum output power defined in [8-1, TS 38.101-1], [8-2, TS 38.101-2] and [8-3, TS 38.101-3] for carrier of primary cell in PUCCH transmission occasion +- is a parameter composed of the sum of a component $P_{0\_ \text{nominal}}$ , provided by *p0-nominal*, or dBm if *p0-nominal* is not provided, for carrier of primary cell and, if provided, a component provided by *p0-PUCCH-Value* in *P0-PUCCH* for active UL BWP of carrier of primary cell, where $\mu$ is a size for a set of values provided by *maxNrofPUCCH-P0-PerSet*. The set of values is provided by *p0-Set*. If *p0-Set* is not provided to the UE, , +- If the UE is provided *PUCCH-SpatialRelationInfo*, the UE obtains a mapping, by an index provided by *p0-PUCCH-Id*, between a set of *pucch-SpatialRelationInfoId* values and a set of *p0-PUCCH-Value* values. If the UE is provided more than one values for *pucch-SpatialRelationInfoId* and the UE receives an activation command [11, TS 38.321] indicating a value of *pucch-SpatialRelationInfoId*, the UE determines the *p0-PUCCH-Value* value through the link to a corresponding *p0-PUCCH-Id* index. The UE applies the activation command in the first slot that is after slot $l$ where $l$ is the slot where the UE would transmit a PUCCH with HARQ-ACK information for the PDSCH providing the activation command and $\mu$ is the SCS configuration for the PUCCH +- If the UE is provided more than one sets of power control parameters for operation in FR1, and the UE receives an activation command [11, TS 38.321] indicating one or two of the more than one sets of power control parameters, the UE determines *p0-PUCCH-Value* value according to the corresponding one or two sets of power control parameters. The UE applies the activation command in the first slot that is after slot $l$ where $l$ is the slot where the UE would transmit a PUCCH with HARQ-ACK information for the PDSCH providing the activation command and $\mu$ is the SCS configuration for the PUCCH. +- If the UE is not provided *PUCCH-SpatialRelationInfo* and is not provided more than one sets of power control parameters for operation in FR1, the UE obtains the *p0-PUCCH-Value* value from the *P0-PUCCH* with *p0-PUCCH-Id* value equal to the minimum *p0-PUCCH-Id* value in *p0-Set* +- is a bandwidth of the PUCCH resource assignment expressed in number of resource blocks for PUCCH transmission occasion on active UL BWP of carrier of primary cell and is a SCS configuration defined in [4, TS 38.211] +- is a downlink pathloss estimate in dB calculated by the UE using RS resource index $\alpha$ as described in clause 7.1.1 for the active DL BWP of carrier of the primary cell as described in clause 12 +- If the UE is not provided *pathlossReferenceRSs* and *enableDefaultBeamPL-ForPUCCH*, or before the UE is provided dedicated higher layer parameters, the UE calculates $\alpha$ using a RS resource obtained from an SS/PBCH block with same SS/PBCH block index as the one the UE uses to obtain *MIB*, or using the SS/PBCH block the UE acquired the time and frequency synchronization for a secondary cell. +- If the UE is provided a number of RS resource indexes, the UE calculates $\alpha$ using RS resource with index $\alpha$ , where $\mu$ is a size for a set of RS resources provided by *maxNrofPUCCH-PathlossReferenceRSs*. The set of RS resources is provided by *pathlossReferenceRSs*. The set of RS resources can include one or both of a set of SS/PBCH block indexes, each provided by *ssb-Index* in *PUCCH-PathlossReferenceRS* when a value of a corresponding *pucch-PathlossReferenceRS-Id* maps to a SS/PBCH block index, and a set of CSI-RS resource + +indexes, each provided by *csi-RS-Index* when a value of a corresponding *pucch-PathlossReferenceRS-Id* maps to a CSI-RS resource index. The UE identifies a RS resource in the set of RS resources to correspond either to a SS/PBCH block index or to a CSI-RS resource index as provided by *pucch-PathlossReferenceRS-Id* in *PUCCH-PathlossReferenceRS* + +- If the UE is provided *pathlossReferenceRSs* and *PUCCH-SpatialRelationInfo*, the UE obtains a mapping, by indexes provided by corresponding values of *pucch-PathlossReferenceRS-Id*, between a set of *pucch-SpatialRelationInfoId* values and a set of *referenceSignal* values provided by *PUCCH-PathlossReferenceRS*. If the UE is provided more than one values for *pucch-SpatialRelationInfoId* and the UE receives an activation command [11, TS 38.321] indicating a value of *pucch-SpatialRelationInfoId*, the UE determines the *referenceSignal* value in *PUCCH-PathlossReferenceRS* through the link to a corresponding *pucch-PathlossReferenceRS-Id* index. The UE applies the activation command in the first slot that is after slot where is the slot where the UE would transmit a PUCCH with HARQ-ACK information for the PDSCH providing the activation command and is the SCS configuration for the PUCCH +- If *PUCCH-SpatialRelationInfo* includes *servingCellId* indicating a serving cell, the UE receives the RS for resource index on the active DL BWP of the serving cell +- If the UE is provided *pathlossReferenceRSs* and more than one sets of power control parameters for operation in FR1, and the UE receives an activation command [11, TS 38.321] indicating one or two of the more than one sets of power control parameters, the UE determines the *referenceSignal* values in *PUCCH-PathlossReferenceRS* that are indicated in the one or two sets of power control parameter +- If the UE is provided *pathlossReferenceRSs* and is not provided *PUCCH-SpatialRelationInfo* and is not provided more than one sets of power control parameters for operation in FR1, the UE obtains the *referenceSignal* value in *PUCCH-PathlossReferenceRS* from the *pucch-PathlossReferenceRS-Id* with index 0 in *PUCCH-PathlossReferenceRS* where the RS resource is either on the primary cell or, if provided, on a serving cell indicated by a value of *pathlossReferenceLinking* +- If the UE + - is not provided *pathlossReferenceRSs*, and + - is not provided *PUCCH-SpatialRelationInfo*, and + - is provided *enableDefaultBeamPL-ForPUCCH*, and + - is not provided *coresetPoolIndex* value of 1 for any CORESET, or is provided *coresetPoolIndex* value of 1 for all CORESETs, in *ControlResourceSet* and no codepoint of a TCI field, if any, in a DCI format of any search space set maps to two TCI states [5, TS 38.212] + +the UE determines a RS resource index providing a periodic RS resource configured with *qcl-Type* set to 'typeD' in the TCI state or the QCL assumption of a CORESET with the lowest index in the active DL BWP of the primary cell. If the CORESET has two activated TCI states, as described in clause 10.1, the UE determines the RS resource index based on the first activated TCI state. For a PUCCH transmission over multiple slots, a same applies to the PUCCH transmission in each of the multiple slots. + +- The parameter is a value of *deltaF-PUCCH-f0* for PUCCH format 0, *deltaF-PUCCH-f1* for PUCCH format 1, *deltaF-PUCCH-f2* for PUCCH format 2, *deltaF-PUCCH-f3* for PUCCH format 3, and *deltaF-PUCCH-f4* for PUCCH format 4, if provided; otherwise . +- is a PUCCH transmission power adjustment component on active UL BWP of carrier of primary cell +- For a PUCCH transmission using PUCCH format 0 or PUCCH format 1, where + - is a number of PUCCH format 0 symbols or PUCCH format 1 symbols for the PUCCH transmission as described in clause 9.2. + - for PUCCH format 0 + - for PUCCH format 1 + - For PUCCH format 0, + - For PUCCH format 1 + +- if the PUCCH transmission provides multicast HARQ-ACK information according to the second HARQ-ACK reporting mode as described in clause 18, +- otherwise, , where is a number of UCI bits in PUCCH transmission occasion +- For a PUCCH transmission using PUCCH format 2 or PUCCH format 3 or PUCCH format 4 and for a number of UCI bits smaller than or equal to 11, , where + - + - is a number of HARQ-ACK information bits that the UE determines as described in clause 9.1.2.1 or 16.5.1.1 for Type-1 HARQ-ACK codebook and as described in clause 9.1.3.1 or 9.1.3.3 or 16.5.2.1 for Type-2 HARQ-ACK codebook, or as described in clause 9.1.5 for HARQ-ACK codebook retransmission, or as described in clause 9.2.5.4 for deferring HARQ-ACK for SPS PDSCH. is the same as as described in clause 9.1.4 for Type-3 HARQ-ACK codebook. If the UE is not provided any of *pdsch-HARQ-ACK-Codebook*, *pdsch-HARQ-ACK-Codebook-r16*, or *pdsch-HARQ-ACK-OneShotFeedback*, if the UE includes a HARQ-ACK information bit in the PUCCH transmission; otherwise, + - is a number of SR information bits that the UE determines as described in clause 9.2.5.1 + - is a number of CSI information bits that the UE determines as described in clause 9.2.5.2 + - is a number of resource elements determined as , where is a number of subcarriers per resource block excluding subcarriers used for DM-RS transmission, and is a number of symbols excluding symbols used for DM-RS transmission, as defined in clause 9.2.5.2, for PUCCH transmission occasion on active UL BWP of carrier of primary cell +- For a PUCCH transmission using PUCCH format 2 or PUCCH format 3 or PUCCH format 4 and for a number of UCI bits larger than 11, , where + - + - + - is a number of HARQ-ACK information bits that the UE determines as described in clause 9.1.2.1 or 16.5.1.1 for Type-1 HARQ-ACK codebook and as described in clause 9.1.3.1 or 9.1.3.3 or 16.5.2.1 for Type-2 HARQ-ACK codebook, or as described in clause 9.1.4 for Type-3 HARQ-ACK codebook, or as described in clause 9.1.5 for HARQ-ACK codebook retransmission, or as described in clause 9.2.5.4 for deferring HARQ-ACK for SPS PDSCH. If the UE is not provided any of *pdsch-HARQ-ACK-Codebook*, *pdsch-HARQ-ACK-Codebook-r16*, or *pdsch-HARQ-ACK-OneShotFeedback*, if the UE includes a HARQ-ACK information bit in the PUCCH transmission; otherwise, + - is a number of SR information bits that the UE determines as described in clause 9.2.5.1 + - is a number of CSI information bits that the UE determines as described in clause 9.2.5.2 + - is a number of CRC bits that the UE determines as described in clause 9.2 + - is a number of resource elements that the UE determines as , where is a number of subcarriers per resource block excluding subcarriers used for DM-RS transmission, and is a number of symbols excluding symbols used for DM-RS transmission, as defined in clause 9.2.5.2, for PUCCH transmission occasion on active UL BWP of carrier of primary cell . +- For the PUCCH power control adjustment state for active UL BWP of carrier of primary cell and PUCCH transmission occasion + - is a TPC command value included in a DCI format associated with the PUCCH transmission for active UL BWP of carrier of the primary cell that the UE detects for PUCCH transmission occasion , or is jointly coded with other TPC commands in a DCI format 2\_2 with CRC scrambled by TPC-PUCCH-RNTI [5, TS 38.212], as described in clause 11.3 + - if the UE is provided *twoPUCCH-PC-AdjustmentStates* and *PUCCH-SpatialRelationInfo*, or more than one sets of power control parameters for operation in FR1, if the UE is not provided *twoPUCCH-PC-AdjustmentStates* or *PUCCH-SpatialRelationInfo* and more than one sets of power control parameters, and if the PUCCH transmission provides only multicast HARQ-ACK information + +- If the UE obtains a TPC command value from a DCI format associated with the PUCCH transmission and if the UE is provided *PUCCH-SpatialRelationInfo*, the UE obtains a mapping, by an index provided by *p0-PUCCH-Id*, between a set of *pucch-SpatialRelationInfoId* values and a set of values for *closedLoopIndex* that provide the value(s). If the UE receives an activation command indicating a value of *pucch-SpatialRelationInfoId*, the UE determines the value *closedLoopIndex* that provides the value of through the link to a corresponding *p0-PUCCH-Id* index +- If the UE obtains a TPC command value from a DCI format associated with the PUCCH transmission, and if the UE is provided more than one sets of power control parameters for operation in FR1, and if the UE receives an activation command [11, TS 38.321] indicating one or two sets of the more than one sets of power control parameters, the UE determines the value of based on the *closedLoopIndex* value in the one or two sets of power control parameters +- If the UE obtains a TPC command from a DCI format 2\_2 with CRC scrambled by a TPC-PUCCH-RNTI, the value is provided by the closed loop indicator field in DCI format 2\_2 +- If the UE transmits the PUCCH with repetitions, as described in clause 9.2.6, and the UE is provided *twoPUCCH-PC-AdjustmentStates* by *pucch-PowerControl* + - If the DCI format includes two TPC command values and the PUCCH resource of the PUCCH transmission is associated with and , the UE applies the first TPC command value for and applies the second TPC command value for + - If the DCI format includes two TPC command values and the PUCCH resource of the PUCCH transmission is associated with , the UE applies the first TPC command value for and ignores the second TPC command value + - If the DCI format includes two TPC command values and the PUCCH resource of the PUCCH transmission is associated with , the UE applies the second TPC command value for and ignores the first TPC command value + - If the DCI format includes one TPC command value, the UE applies the TPC command value for all associated with the PUCCH resource of the PUCCH transmission +- is the current PUCCH power control adjustment state for active UL BWP of carrier of primary cell and PUCCH transmission occasion , where +- The values are given in Table 7.1.2-1 +- is a sum of TPC command values in a set of TPC command values with cardinality that the UE receives between symbols before PUCCH transmission occasion and $K_{PUCCH}(i)$ symbols before PUCCH transmission occasion on active UL BWP of carrier of primary cell for PUCCH power control adjustment state, where is the smallest integer for which symbols before PUCCH transmission occasion is earlier than symbols before PUCCH transmission occasion +- If the PUCCH transmission is in response to a detection by the UE of a DCI format, is a number of symbols for active UL BWP of carrier of primary cell after a last symbol of a corresponding PDCCH reception and before a first symbol of the PUCCH transmission +- If the PUCCH transmission is not in response to a detection by the UE of a DCI format, is a number of symbols equal to the product of a number of symbols per slot, , and the minimum of the values provided by *k2* in *PUSCH-ConfigCommon* for active UL BWP of carrier of primary cell + - If the first symbol of the PUCCH transmission occasion occurs within after a last symbol of a PDCCH reception where the UE detects the DCI format providing the TPC command, the UE may postpone the application of the TPC command until the above condition is not valid. is the PUSCH preparation time for the corresponding UE processing capability [6, TS 38.214] assuming , and corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH carrying the DCI format and the SCS configuration of the PUCCH. +- If the UE has reached maximum power for active UL BWP of carrier of primary cell at PUCCH transmission occasion and , then + +- If UE has reached minimum power for active UL BWP of carrier of primary cell at PUCCH transmission occasion and , then + - If a configuration of a value for a corresponding PUCCH power control adjustment state for active UL BWP of carrier of primary cell is provided by higher layers, + - + - if the UE is provided *PUCCH-SpatialRelationInfo*, the UE determines the value of from the value of based on a *pucch-SpatialRelationInfoId* value associated with the *p0-PUCCH-Id* value corresponding to and with the *closedLoopIndex* value corresponding to ; + - else, if the UE is provided more than one sets of power control parameters for operation in FR1, and if the UE receives an activation command for a PUCCH resource that indicates one or two sets of the more than one sets of power control parameters, the UE determines the value of based on the *closedLoopIndex* value in the one or two sets of power control parameters; + - else, + - Else, + - , where , and is + - the TPC command value indicated in a random access response grant corresponding to a PRACH transmission according to Type-1 random access procedure, or in a random access response grant corresponding to MsgA transmissions according to Type-2 random access procedure with RAR message(s) for fallbackRAR, or + - the TPC command value indicated in a successRAR corresponding to MsgA transmissions for Type-2 random access procedure, or + - the TPC command value in a DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI that the UE detects in a first PDCCH reception in a search space set provided by *recoverySearchSpaceId* if the PUCCH transmission is a first PUCCH transmission after 28 symbols from a last symbol of the first PDCCH reception, +- and, if the UE transmits PUCCH on active UL BWP of carrier of primary cell , +- ; +- otherwise, +- where is provided by higher layers and corresponds to the total power ramp-up requested by higher layers from the first to the last preamble for active UL BWP of carrier of primary cell , and corresponds to PUCCH format 0 or PUCCH format 1 + +**Table 7.2.1-1: Mapping of TPC Command Field in a DCI format to accumulated values** + +| TPC Command Field | Accumulated [dB] | +|-------------------|------------------| +| 0 | -1 | +| 1 | 0 | +| 2 | 1 | +| 3 | 3 | + +## 7.3 Sounding reference signals + +For SRS, + +- if a UE is provided *tdm* for an SRS resource with 8 ports in an SRS resource set with usage 'codebook' or 'antennaSwitching', the UE splits a linear value of the transmit power on active UL BWP of carrier of serving cell equally across the configured antenna ports on each symbol for SRS transmission. +- else, a UE splits a linear value of the transmit power on active UL BWP of carrier of serving cell equally across the configured antenna ports for SRS. + +### 7.3.1 UE behaviour + +If a UE transmits SRS based on a configuration by *SRS-ResourceSet* on active UL BWP of carrier of serving cell using SRS power control adjustment state with index $l$ , the UE determines the SRS transmission power in SRS transmission occasion as + +$$P_{\text{SRS},b,f,c}(i, q_s, l) = \min \left\{ \begin{aligned} & P_{\text{CMAX},f,c}(i), \\ & P_{\text{O\_SRS},b,f,c}(q_s) + 10 \log_{10}(2^{\mu} \cdot M_{\text{SRS},b,f,c}(i)) + \alpha_{\text{SRS},b,f,c}(q_s) \cdot PL_{b,f,c}(q_d) + h_{b,f,c}(i, l) \end{aligned} \right\} \text{ [dBm]}$$ + +where, + +- $P_{\text{CMAX},f,c}(i)$ is the UE configured maximum output power defined in [8, TS 38.101-1], [8-2, TS 38.101-2] and [TS 38.101-3] for carrier of serving cell in SRS transmission occasion +- $P_{\text{O\_SRS},b,f,c}(q_s)$ is provided by $p0$ for active UL BWP of carrier of serving cell and SRS resource set provided by *SRS-ResourceSet* and *SRS-ResourceSetId* +- $M_{\text{SRS},b,f,c}(i)$ is a SRS bandwidth expressed in number of resource blocks for SRS transmission occasion on active UL BWP of carrier of serving cell and is a SCS configuration defined in [4, TS 38.211] +- $\alpha_{\text{SRS},b,f,c}(q_s)$ is provided by *alpha* for active UL BWP of carrier of serving cell and SRS resource set +- $PL_{b,f,c}(q_d)$ is a downlink pathloss estimate in dB calculated by the UE using RS resource index as described in clause 7.1.1 for the active DL BWP of serving cell and SRS resource set [6, TS 38.214]. The RS resource index is provided by *pathlossReferenceRS* associated with the SRS resource set and is either an *ssb-Index* providing a SS/PBCH block index or a *csi-RS-Index* providing a CSI-RS resource index. If the UE is provided *enablePL-RS-UpdateForPUSCH-SRS*, a MAC CE [11, TS 38.321] can provide by *SRS-PathlossReferenceRS-Id* a corresponding RS resource index for aperiodic or semi-persistent SRS resource set +- If the UE is not provided *pathlossReferenceRS* or *SRS-PathlossReferenceRS-Id* and if the UE is not provided *enableDefaultBeamPL-ForSRS*, or before the UE is provided dedicated higher layer parameters, the UE calculates using a RS resource obtained from an SS/PBCH block with same SS/PBCH block index as the one the UE uses to obtain *MIB*, or using the SS/PBCH block the UE acquired the time and frequency synchronization for a secondary cell. +- If the UE is provided *pathlossReferenceLinking*, the RS resource is on a serving cell indicated by a value of *pathlossReferenceLinking* +- If the UE + - is not provided *pathlossReferenceRS* or *SRS-PathlossReferenceRS-Id*, + - is not provided *spatialRelationInfo*, and + - is provided *enableDefaultBeamPL-ForSRS*, and + - is not provided *coresetPoolIndex* value of 1 for any CORESET, or is provided *coresetPoolIndex* value of 1 for all CORESETs, in *ControlResourceSet* and no codepoint of a TCI field, if any, in a DCI format of any search space set maps to two TCI states [5, TS 38.212] + +the UE determines a RS resource index providing a periodic RS resource configured with *qcl-Type* set to 'typeD' in + +- the TCI state or the QCL assumption of a CORESET with the lowest index in the active DL BWP, if CORESETs are provided in the active DL BWP of serving cell. If the CORESET has two activated TCI states, as described in clause 10.1, the UE determines the RS resource index based on the first TCI state. +- the active PDSCH TCI state with lowest ID [6, TS 38.214] in the active DL BWP, if CORESETs are not provided in the active DL BWP of serving cell +- For the SRS power control adjustment state for active UL BWP of carrier of serving cell and SRS transmission occasion + +- , where is the current PUSCH power control adjustment state as described in clause 7.1.1, if *srs-PowerControlAdjustmentStates* indicates a same power control adjustment state for SRS transmissions and PUSCH transmissions; or + +$$h_{b,f,c}(i) = h_{b,f,c}(i - i_0) + \sum_{m=0}^{C(S_c)-1} \delta_{SRS,b,f,c}(m)$$ + +- if the UE is not configured for PUSCH transmissions on active UL BWP of carrier of serving cell , or if *srs-PowerControlAdjustmentStates* indicates separate power control adjustment states between SRS transmissions and PUSCH transmissions, and if *tpc-Accumulation* is not provided, where + +- The values are given in Table 7.1.1-1 +- is jointly coded with other TPC commands in a PDCCH with DCI format 2\_3, as described in clause 11.4 +- is a sum of TPC command values in a set of TPC command values with cardinality that the UE receives between symbols before SRS transmission occasion and symbols before SRS transmission occasion on active UL BWP of carrier of serving cell for SRS power control adjustment state, where is the smallest integer for which symbols before SRS transmission occasion is earlier than symbols before SRS transmission occasion +- if the SRS transmission is aperiodic, is a number of symbols for active UL BWP of carrier of serving cell after a last symbol of a corresponding PDCCH triggering the SRS transmission and before a first symbol of the SRS transmission +- if the SRS transmission is semi-persistent or periodic, is a number of symbols equal to the product of a number of symbols per slot, , and the minimum of the values provided by *k2* in *PUSCH-ConfigCommon* for active UL BWP of carrier of serving cell + - If the first symbol of the SRS transmission occasion occurs within after a last symbol of a PDCCH reception where the UE detects the DCI format providing the TPC command, the UE may postpone the application of the TPC until the above condition is not valid. is the PUSCH preparation time for the corresponding UE processing capability [6, TS 38.214] assuming , and corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH carrying the DCI format and the SCS configuration of the SRS. +- If the UE has reached maximum power for active UL BWP of carrier of serving cell at SRS transmission occasion and , then +- If UE has reached minimum power for active UL BWP of carrier of serving cell at SRS transmission occasion and , then +- If a configuration for a value or for a value for a corresponding SRS power control adjustment state for active UL BWP of carrier of serving cell is provided by higher layers + - +- else + - + +where + +is + +- the TPC command value indicated in the random access response grant corresponding to a PRACH transmission according to Type-1 random access procedure, or in a random access response grant corresponding to MsgA transmissions according to Type-2 random access procedure with RAR message(s) for fallbackRAR, or +- the TPC command value indicated in a successRAR corresponding to MsgA transmissions for Type-2 random access procedure, + +and + +; + +where $\Delta$ is provided by higher layers and corresponds to the total power ramp-up requested by higher layers from the first to the last preamble for active UL BWP of carrier of serving cell. + +- if the UE is not configured for PUSCH transmissions on active UL BWP of carrier of serving cell, or if *srs-PowerControlAdjustmentStates* indicates separate power control adjustment states between SRS transmissions and PUSCH transmissions, and *tpc-Accumulation* is provided, and the UE detects a DCI format 2\_3 symbols before a first symbol of SRS transmission occasion, where absolute values of $\delta_{SRS}$ are provided in Table 7.1.1-1 +- if *srs-PowerControlAdjustmentStates* indicates a same power control adjustment state for SRS transmissions and PUSCH transmissions, the update of the power control adjustment state for SRS transmission occasion occurs at the beginning of each SRS resource in the SRS resource set; otherwise, the update of the power control adjustment state SRS transmission occasion occurs at the beginning of the first transmitted SRS resource in the SRS resource set. + +If a UE transmits SRS based on a configuration by *SRS-PosResourceSet* on active UL BWP of carrier of serving cell, the UE determines the SRS transmission power in SRS transmission occasion as + +$$P_{SRS,b,f,c}(i, q_s) = \min \left\{ \begin{array}{l} P_{CMAX,f,c}(i), \\ P_{O,SRS,b,f,c}(q_s) + 10 \log_{10}(2^u \cdot M_{SRS,b,f,c}(i)) + \alpha_{SRS,b,f,c}(q_s) \cdot PL_{b,f,c}(q_d) \end{array} \right\} \text{ [dBm]}$$ + +where, + +- $P_{O,SRS,b,f,c}$ and $\alpha_{SRS,b,f,c}$ are provided by *p0-r16* and *alpha-r16* respectively, for active UL BWP of carrier of serving cell, and SRS resource set is indicated by *SRS-PosResourceSetId* from *SRS-PosResourceSet*, and +- $PL_{b,f,c}$ is a downlink pathloss estimate in dB calculated by the UE, as described in clause 7.1.1 in case of an active DL BWP of a serving cell, using RS resource indexed $\bar{i}$ in a serving or non-serving cell for SRS resource set [6, TS 38.214]. A configuration for RS resource index associated with SRS resource set is provided by *pathlossReferenceRS-Pos* + - if a *ssb-IndexServing* is provided, *referenceSignalPower* is provided by *ss-PBCH-BlockPower* + - if a *ssb-Ncell* is provided, *referenceSignalPower* is provided by *ss-PBCH-BlockPower-r16* + - if a *dl-PRS* is provided, *referenceSignalPower* is provided by *dl-PRS-ResourcePower* + +If the UE is in the RRC\_CONNECTED state and determines that the UE is not able to accurately measure $\bar{i}$ , or the UE is not provided with *pathlossReferenceRS-Pos*, the UE calculates $\bar{i}$ using a RS resource obtained from the SS/PBCH block of the serving cell that the UE uses to obtain *MIB*. If the UE is in the RRC\_INACTIVE state, is not provided *SRS-PosRRC-InactiveConfig-ValidityArea*, and determines that the UE is not able to accurately measure $\bar{i}$ , the UE does not transmit SRS for the SRS resource set. + +The UE may indicate a capability for a number of pathloss estimates that the UE can simultaneously maintain for all SRS resource sets provided by *SRS-PosResourceSet* in addition to the up to four pathloss estimates that the UE maintains per serving cell for PUSCH/PUCCH transmissions and for SRS transmissions configured by *SRS-Resource*. + +If a UE transmits SRS based on a configuration by *SRS-PosResourceSet* outside initial UL BWP of carrier $f$ of serving cell $c$ in RRC\_INACTIVE state, the active UL BWP $b$ refers to the BWP configuration provided by *bwp-NUL* or *bwp-SUL* in *SRS-PosRRC-InactiveConfig* for the corresponding carrier. + +If a UE transmits SRS on multiple SRS resources for positioning bandwidth aggregation according to *linkage* [6, TS 38.214], the UE calculates $\bar{i}$ , $P_{O,SRS,b,f,c}$ , and $\alpha_{SRS,b,f,c}$ for each of the multiple SRS resources. + +If a UE transmits SRS based on a configuration by *SRS-PosResourceSet* in *SRS-PosRRC-InactiveConfig-ValidityArea* in RRC\_INACTIVE state [12, TS 38.331], the active UL BWP $b$ refers to the BWP provided by *bwp* in *SRS-PosRRC-InactiveConfig-ValidityArea*. If the UE is not provided *pathlossReferenceRS-Pos* in *SRS-PosResourceSet*, or if the UE is provided *pathlossReferenceRS-Pos* in *SRS-PosResourceSet* and the UE cannot accurately measure a pathloss, the UE calculates $\bar{i}$ using an RS resource from an SS/PBCH block with same index as the one the UE used to obtain *MIB*; otherwise, the UE uses the RS indicated by *pathlossReferenceRS-Pos* to calculate $\bar{i}$ . + +If a RedCap UE transmits SRS with frequency hopping outside the active UL BWP of carrier of serving cell in RRC\_CONNECTED state based on an indication by *SRS-PosResourceSet* in *XYZ*, the active UL BWP refers to the BWP provided by *bwp* in *XYZ*. + +If a RedCap UE transmits SRS with frequency hopping outside the initial UL BWP of carrier of serving cell in RRC\_INACTIVE state based on an indication by *SRS-PosResourceSet* in *XYZ*, the active UL BWP refers to the BWP provided by *bwp* in *XYZ*. + +## 7.4 Physical random access channel + +A UE determines a transmission power for a physical random access channel (PRACH), , on active UL BWP of carrier of cell based on DL RS for cell in transmission occasion as + +[dBm], + +where + +- is the UE configured maximum output power defined in [8-1, TS 38.101-1], [8-2, TS 38.101-2] and [8-3, TS 38.101-3] for carrier of cell within transmission occasion , +- is the PRACH target reception power *PREAMBLE\_RECEIVED\_TARGET\_POWER* provided by higher layers [11, TS 38.321] for the active UL BWP of carrier of cell , and +- is a pathloss for the active UL BWP of carrier based on the DL RS associated with the PRACH transmission on the active DL BWP of cell and calculated by the UE in dB as *referenceSignalPower* – higher layer filtered RSRP in dBm, where RSRP is defined in [7, TS 38.215] and the higher layer filter configuration is defined in [12, TS 38.331]. If the active DL BWP is the initial DL BWP and for SS/PBCH block and CORESET multiplexing pattern 2 or 3 as described in clause 13, or for a non-serving cell, the UE determines based on the SS/PBCH block associated with the PRACH transmission. + +If a PRACH transmission from a UE is not in response to a detection of a PDCCH order by the UE, or is in response to a detection of a PDCCH order by the UE that triggers a contention based random access procedure, or is associated with a link recovery procedure where a corresponding index is associated with a SS/PBCH block, as described in clause 6, *referenceSignalPower* is provided by *ss-PBCH-BlockPower*. + +If a PRACH transmission from a UE is in response to a detection of a PDCCH order by the UE that triggers a contention-free random access procedure and depending on the DL RS that the DM-RS of the PDCCH order is quasi-collocated with as described in clause 10.1 + +- when the PRACH association indicator is not present in the PDCCH order, or +- when the cell indicator field in the PDCCH order is not present or has value 0, or +- when a value of a PRACH association indicator field in the PDCCH order is 0 if the UE is not provided *SSB-MTC-AdditionalPCI*, or +- when the PRACH association indicator field in the PDCCH order indicates a *physCellId* associated with the cell of the PDCCH order reception, + +or depending on an indicated SS/PBCH block + +- when the PRACH transmission is on a non-serving cell indicated by the cell indicator field in the PDCCH order, or +- when a value of a PRACH association indicator field in the PDCCH order is 1 if the UE is not provided *SSB-MTC-AdditionalPCI*, or +- when the PRACH association indicator field in the PDCCH order indicates a *physCellId* that is different that the *physCellId* associated with the cell of the PDCCH order reception, + +*referenceSignalPower* is provided by a corresponding *ss-PBCH-BlockPower*. + +When a value of a PRACH association indicator field in the PDCCH order is 1 if the UE is not provided *SSB-MTC-AdditionalPCI*, or when the PRACH association indicator field in the PDCCH order indicates a *physCellId* that is + +different that the *physCellId* associated with the cell of the PDCCH order reception, the UE expects that the indicated SS/PBCH block in the PDCCH order is configured as *pathlossReferenceRS-Id* of an active TCI state. + +If the UE is configured resources for a periodic CSI-RS reception or the PRACH transmission is associated with a link recovery procedure where a corresponding index is associated with a periodic CSI-RS configuration as described in clause 6, *referenceSignalPower* is obtained by *ss-PBCH-BlockPower* and *powerControlOffsetSS* where *powerControlOffsetSS* provides an offset of CSI-RS transmission power relative to SS/PBCH block transmission power [6, TS 38.214]. If *powerControlOffsetSS* is not provided to the UE, the UE assumes an offset of 0 dB. If the active TCI state for the PDCCH that provides the PDCCH order includes two RS, the UE expects that one RS is configured with *qcl-Type* set to 'typeD' and the UE uses the one RS when applying a value provided by *powerControlOffsetSS*. + +If within a random access response window, as described in clause 8.2, the UE does not receive a random access response that contains a preamble identifier corresponding to the preamble sequence transmitted by the UE, or when a random access response does not exist, the UE determines a transmission power for a subsequent PRACH transmission, if any, as described in [11, TS 38.321]. + +If prior to a PRACH retransmission, a UE changes the spatial domain transmission filter, Layer 1 notifies higher layers to suspend the power ramping counter as described in [11, TS 38.321]. + +If due to power allocation to PUSCH/PUCCH/PRACH/SRS transmissions as described in clause 7.5, or due to power allocation in EN-DC or NE-DC or NR-DC operation, or due to slot format determination as described in clause 11.1, or due to the PUSCH/PUCCH/PRACH/SRS transmission occasions are in the same slot or the gap between a PRACH transmission and PUSCH/PUCCH/SRS transmission is small as described in clause 8.1, or due to DAPS operation as described in clause 15, or due to HD-UE operation in paired spectrum as described in clause 17.2, the UE does not transmit a PRACH in a transmission occasion, Layer 1 notifies higher layers to suspend the corresponding power ramping counter. If due to power allocation to PUSCH/PUCCH/PRACH/SRS transmissions as described in clause 7.5, or due to power allocation in EN-DC or NE-DC or NR-DC operation, the UE transmits a PRACH with reduced power in a transmission occasion, Layer 1 may notify higher layers to suspend the corresponding power ramping counter. + +## 7.5 Prioritizations for transmission power reductions + +For single cell operation with two uplink carriers or for operation with carrier aggregation, if a total UE transmit power for PUSCH or PUCCH or PRACH or SRS transmissions on serving cells in a frequency range in a respective transmission occasion would exceed $P_{CMAX}$ , where $P_{CMAX}$ is the linear value of $P_{CMAX}$ in transmission occasion as defined in [8-1, TS 38.101-1] for FR1 and [8-2, TS 38.101-2] for FR2, the UE allocates power to PUSCH/PUCCH/PRACH/SRS transmissions according to the following priority order (in descending order) so that the total UE transmit power for transmissions on serving cells in the frequency range is smaller than or equal to $P_{CMAX}$ for that frequency range in every symbol of transmission occasion. If the UE transmits SRS on multiple SRS resources according the *XYZ* [6, TS 38.214], the UE allocates power so that all REs of the SRS transmission have same power. + +For the purpose of power allocation in this clause, if a UE is provided *uci-MuxWithDiffPrio* and the UE multiplexes HARQ-ACK information in a PUSCH, a priority index of the PUSCH is the larger of (a) the priority index of the PUSCH according to clause 9 and (b) the larger priority index of the HARQ-ACK information. When determining a total transmit power for serving cells in a frequency range in a symbol of transmission occasion, the UE does not include power for transmissions starting after the symbol of transmission occasion. The total UE transmit power in a symbol of a slot is defined as the sum of the linear values of UE transmit powers for PUSCH, PUCCH, PRACH, and SRS in the symbol of the slot. + +- PRACH transmission on a candidate cell, if any, as described in Clause 21 +- PRACH transmission on the PCell +- PUCCH or PUSCH transmissions with larger priority index +- For PUCCH or PUSCH transmissions with same priority index + - PUCCH transmission with HARQ-ACK information, and/or SR, and/or LRR, or PUSCH transmission with HARQ-ACK information of the priority index + - PUCCH transmission with CSI or PUSCH transmission with CSI + - PUSCH transmission without HARQ-ACK information of the priority index or CSI and, for Type-2 random access procedure, PUSCH transmission on the PCell + +- If the UE is configured with *prioSCellPRACH-OverSP-PeriodicSRS-r17* + - Aperiodic SRS transmission or PRACH transmission on a serving cell other than the PCell + - Semi-persistent and/or periodic SRS transmission +- otherwise, + - SRS transmission, with aperiodic SRS having higher priority than semi-persistent and/or periodic SRS, or PRACH transmission on a serving cell other than the PCell + +In case of same priority order and for operation with carrier aggregation, the UE prioritizes power allocation for transmissions on the primary cell of the MCG or the SCG over transmissions on a secondary cell. In case of same priority order and for operation with two UL carriers, the UE prioritizes power allocation for transmissions on the carrier where the UE is configured to transmit PUCCH. If PUCCH is not configured for any of the two UL carriers, the UE prioritizes power allocation for transmissions on the non-supplementary UL carrier. + +## 7.6 Dual connectivity + +### 7.6.1 EN-DC + +If a UE is configured with a MCG using E-UTRA radio access and with a SCG using NR radio access, the UE is configured a maximum power $P_{\text{LTE}}$ for transmissions on the MCG by *p-MaxEUTRA* and a maximum power $P_{\text{NR}}$ for transmissions in FR1 on the SCG by *p-NR-FR1*. + +The UE determines a transmission power for the MCG as described in [13, TS 36.213] using $P_{\text{LTE}}$ as the maximum transmission power. The UE determines transmission power for the SCG in FR1 as described in clauses 7.1 through 7.5 using $P_{\text{NR}}$ as the maximum transmission power. The UE determines transmission power for the SCG in FR2 as described in clauses 7.1 through 7.5. + +A UE does not expect to be configured for operation with shortened TTI and/or processing time [13, TS 36.213] on a cell that is included in an EN-DC configuration. + +If a UE is configured with $\hat{P}_{\text{LTE}} + \hat{P}_{\text{NR}} > \hat{P}_{\text{Total}}^{\text{EN-DC}}$ , where $\hat{P}_{\text{LTE}}$ is the linear value of $P_{\text{LTE}}$ , $\hat{P}_{\text{NR}}$ is the linear value of $P_{\text{NR}}$ , and $\hat{P}_{\text{Total}}^{\text{EN-DC}}$ is the linear value of a configured maximum transmission power for EN-DC operation as defined in [8-3, TS 38.101-3] for FR1, the UE determines a transmission power for the SCG as follows. + +- If the UE is configured with reference TDD configuration for E-UTRA (by *tdm-PatternConfig* or by *tdm-PatternConfig2* in [13, TS 36.213]) + - If the UE does not indicate a capability for dynamic power sharing between E-UTRA and NR for EN-DC, the UE does not transmit in a slot on the SCG in FR1 when a corresponding subframe on the MCG is an UL subframe in the reference TDD configuration. + - If the UE indicates a capability for dynamic power sharing between E-UTRA and NR for EN-DC, and does not indicate a capability *tdm-restrictionDualTX-FDD-endc-r16* in [18, TS 38.306], and is configured with *tdm-PatternConfig2*, the UE does not transmit on the SCG in FR1 when the UE has overlapped transmission on a subframe on the MCG. +- If the UE indicates a capability for dynamic power sharing between E-UTRA and NR for EN-DC and + - if UE transmission(s) in subframe $i_1$ of the MCG overlap in time with UE transmission(s) in slot $i_2$ of the SCG in FR1, and + - if $\hat{P}_{\text{MCG}}(i_1) + \hat{P}_{\text{SCG}}(i_2) > \hat{P}_{\text{Total}}^{\text{EN-DC}}$ in any portion of slot $i_2$ of the SCG, + +the UE reduces transmission power in any portion of slot $i_2$ of the SCG so that $\hat{P}_{\text{MCG}}(i_1) + \hat{P}_{\text{SCG}}(i_2) \leq \hat{P}_{\text{Total}}^{\text{EN-DC}}$ in any portion of slot $i_2$ , where $\hat{P}_{\text{MCG}}(i_1)$ and $\hat{P}_{\text{SCG}}(i_2)$ are the linear values of the total UE transmission powers in subframe $i_1$ of the MCG and in slot $i_2$ of the SCG in FR1, respectively. The UE is not required to transmit in any portion of slot $i_2$ of the SCG if $\hat{P}_{\text{SCG}}(i_2)$ would need to be reduced by more than the value provided by + +$X_{SCALE}$ in order for $\hat{P}_{MCG}(i_1) + \hat{P}_{SCG}(i_2) \leq \hat{P}_{Total}^{EN-DC}$ in any portion of slot $i_2$ of the SCG. The UE is required to transmit in slot $i_2$ of the SCG if $\hat{P}_{SCG}(i_2)$ would not need to be reduced by more than the value provided by $X_{SCALE}$ in order for $\hat{P}_{MCG}(i_1) + \hat{P}_{SCG}(i_2) \leq \hat{P}_{Total}^{EN-DC}$ in all portions of slot $i_2$ . + +- If the UE does not indicate a capability for dynamic power sharing between E-UTRA and NR for EN-DC, the UE expects to be configured with reference TDD configuration for E-UTRA by *tdm-PatternConfig* in [13, TS 36.213]. + +### 7.6.1A NE-DC + +If a UE is configured with an MCG using NR radio access and with a SCG using E-UTRA radio access, the UE is configured a maximum power $P_{NR}$ for transmissions in FR1 on the MCG by *p-NR-FR1* and a maximum power $P_{LTE}$ for transmissions on the SCG by *p-MaxEUTRA*. + +The UE determines transmission power for the MCG in FR1 as described in clauses 7.1 through 7.5 using $P_{NR}$ as the maximum transmission power for $P_{CMAX} \leq P_{NR}$ . The UE determines transmission power for the MCG in FR2 as described in clauses 7.1 through 7.5. + +If the UE is not provided *tdd-UL-DL-ConfigurationCommon* for the MCG, the UE determines a transmission power for the SCG as described in [13, TS 36.213] using $P_{LTE}$ as the maximum transmission power. + +If at least one symbol of slot $i_1$ of the MCG that is indicated as uplink or flexible by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* overlaps with subframe $i_2$ of the SCG + +- for subframe $i_2$ , the UE determines a transmission power for the SCG as described in [13, TS 36.213] using $P_{LTE}$ as the maximum transmission power + +otherwise + +- the UE determines a transmission power for the SCG as described in [13, TS 36.213] without considering $P_{LTE}$ as the maximum transmission power + +If a UE is configured with $\hat{P}_{LTE} + \hat{P}_{NR} > \hat{P}_{Total}^{NE-DC}$ , where $\hat{P}_{LTE}$ is the linear value of $P_{LTE}$ , $\hat{P}_{NR}$ is the linear value of $P_{NR}$ , and $\hat{P}_{Total}^{NE-DC}$ is the linear value of a configured maximum transmission power for NE-DC operation as defined in [8-3, TS 38.101-3] for FR1, the UE determines a transmission power for the MCG as follows + +- If the UE is configured with reference TDD configuration for E-UTRA (by *tdm-PatternConfigNE-DC-r15* in [13, TS 36.213]) + - If the UE does not indicate a capability for dynamic power sharing between E-UTRA and NR for NE-DC, the UE does not expect to transmit in a slot on the MCG in FR1 when a corresponding subframe on the SCG is an UL subframe in the reference TDD configuration. +- If the UE indicates a capability for dynamic power sharing between E-UTRA and NR for NE-DC and + - if the UE transmission(s) in slot $i_1$ of the MCG in FR1 overlap in time with UE transmission(s) in subframe $i_2$ of the SCG, and + - if $\hat{P}_{MCG}(i_1) + \hat{P}_{SCG}(i_2) > \hat{P}_{Total}^{NE-DC}$ in any portion of slot $i_1$ of the MCG, + +the UE reduces transmission power in any portion of slot $i_1$ of the MCG so that $\hat{P}_{MCG}(i_1) + \hat{P}_{SCG}(i_2) \leq \hat{P}_{Total}^{NE-DC}$ in all portions of slot $i_1$ , where $\hat{P}_{MCG}(i_1)$ and $\hat{P}_{SCG}(i_2)$ are the linear values of the total UE transmission powers in slot $i_1$ of the MCG in FR1 and in subframe $i_2$ of the SCG, respectively. + +- If the UE does not indicate a capability for dynamic power sharing between E-UTRA and NR for NE-DC, the UE expects to be configured with reference TDD configuration for E-UTRA (by *tdm-PatternConfigNE-DC-r15* in [13, TS 36.213]). + +### 7.6.2 NR-DC + +The UE procedures described in this clause are not applicable if the UE is provided *scg-State* [12, TS 38.331]. + +If a UE is configured with an MCG using NR radio access in FR1 or in FR2 and with a SCG using NR radio access in FR2 or in FR1, respectively, the UE performs transmission power control independently per cell group as described in clauses 7.1 through 7.5. + +If a UE is configured with an MCG and a SCG using NR radio access in FR1 and/or in FR2, the UE is configured a maximum power for transmissions on the MCG by *p-NR-FR1* and/or by *p-NR-FR2* and a maximum power for transmissions on the SCG by *p-NR-FR1* and/or by *p-NR-FR2* and with an inter-CG power sharing mode by *nrdc-PCmode-FR1* for FR1 and/or by *nrdc-PCmode-FR2* for FR2. The UE determines a transmission power on the MCG and a transmission power on the SCG per frequency range. + +If a UE is provided *semi-static-mode1* for *nrdc-PCmode-FR1* or for *nrdc-PCmode-FR2*, or *semi-static-mode2* for *nrdc-PCmode-FR1* or for *nrdc-PCmode-FR2*, the UE does not expect and to be configured such that , where is the linear value of , is the linear value of , and is the linear value of a configured maximum transmission power for NR-DC operation in FR1 or FR2 as defined in [8-3, TS 38.101-3]. + +If a UE is provided *semi-static-mode1* for *nrdc-PCmode-FR1* or for *nrdc-PCmode-FR2*, the UE determines a transmission power for the MCG or for the SCG as described in clauses 7.1 through 7.5 using or as the maximum transmission power, respectively. + +If a UE is provided *semi-static-mode2* for *nrdc-PCmode-FR1* or for *nrdc-PCmode-FR2* + +- if the UE is not provided *tdd-UL-DL-ConfigurationCommon* for the MCG or SCG, the UE determines a transmission power for the MCG or for the SCG as described in clauses 7.1 through 7.5 using or as the maximum transmission power, respectively +- if at least one symbol of slot of the MCG or of the SCG that is indicated as uplink or flexible to a UE by *tdd-UL-DL-ConfigurationCommon* and *tdd-UL-DL-ConfigurationDedicated*, if provided, overlaps with a symbol for any ongoing transmission overlapping with slot of the SCG or of the MCG, respectively, the UE determines a power for the transmission on the SCG or the MCG overlapping with slot as described in clauses 7.1 through 7.5 using or , respectively, as the maximum transmission power +- otherwise, the UE determines a power for the transmission on SCG or the MCG overlapping with slot , as described in [8-3, TS 38.101-3] and in clauses 7.1 through 7.5 without considering or respectively + +The UE expects to be provided *semi-static-mode2* for *nrdc-PCmode-FR1* or for *nrdc-PCmode-FR2* only for synchronous NR-DC operation [10, TS 38.133]. + +If a UE + +- is provided *dynamic* for *nrdc-PCmode-FR1* or for *nrdc-PCmode-FR2*, and +- indicates a capability to support dynamic power sharing for intra-FR NR DC, + +the UE determines a maximum transmission power on the SCG at a first symbol of a transmission occasion on the SCG by determining transmissions on the MCG that + +- are scheduled by DCI formats in PDCCH receptions with a last symbol that is earlier by at least from the first symbol of the transmission occasion on the SCG, or are configured by higher layers, and +- overlap with the transmission occasion on the SCG + +the maximum transmission power on the SCG is determined as + +- , if the UE determines transmissions on the MCG with a total power +- , if the UE does not determine any transmissions on the MCG + +where + +- , +- and is the maximum of , , , and based on the configurations on the MCG and the SCG, respectively, when the UE indicates the value of 'long' for the capability, +- and is the maximum of , , based on the configurations on the MCG and the SCG, respectively, when the UE indicates the value of 'short' for the capability, and +- is the total power for the transmissions on the MCG that overlap with the transmission occasion on the SCG where is determined based on transmissions configured by higher layers and on transmissions scheduled by DCI formats in PDCCH receptions with a last symbol that is at least before the first symbol of the transmission occasion on the SCG. + +The UE does not expect to have PUSCH, PUCCH, PRACH, or SRS transmissions on the MCG that + +- are scheduled/triggered by DCI formats in PDCCH receptions with a last symbol that is earlier by less than from the first symbol of the transmission occasion on the SCG, and +- overlap with the transmission occasion on the SCG + +The UE does not expect to receive a positive TPC command value in a DCI format 2\_2 or a DCI format 2\_3 in a PDCCH reception with a last symbol that is less than before the first symbol of the transmission occasion on the SCG, if the transmission on the MCG overlaps with the transmission occasion on the SCG. + +The UE is not required to apply a TPC command the UE receives in a DCI format 2\_2 or a DCI format 2\_3 in a PDCCH reception with a last symbol that is less than before the first symbol of the transmission occasion on the SCG, if the transmission on the MCG overlaps with the transmission occasion on the SCG. + +## 7.7 Power headroom report + +The types of UE power headroom reports are the following. A Type 1 UE power headroom $PH$ that is valid for PUSCH transmission occasion $i$ on active UL BWP $b$ of carrier $f$ of serving cell $c$ . A Type 3 UE power headroom $PH$ that is valid for SRS transmission occasion $i$ on active UL BWP $b$ of carrier $f$ of serving cell $c$ . + +A UE determines whether a power headroom report for an activated serving cell [11, TS 38.321] is based on an actual transmission or a reference format based on the higher layer signalling of configured grant and periodic/semi-persistent sounding reference signal transmissions and downlink control information the UE received until and including the PDCCH monitoring occasion where the UE detects the first DCI format scheduling an initial transmission of a transport block since a power headroom report was triggered if the power headroom report is reported on a PUSCH triggered by the first DCI format. Otherwise, a UE determines whether a power headroom report is based on an actual transmission or a reference format based on the higher layer signalling of configured grant and periodic/semi-persistent sounding reference signal transmissions and downlink control information the UE received until the first uplink symbol of a configured PUSCH transmission minus $T'_{proc,2} = T_{proc,2}$ where $T_{proc,2}$ is determined according to [6, TS 38.214] assuming $d_{2,1} = 1$ , $d_{2,2} = 0$ , and with $\mu_{DL}$ corresponding to the subcarrier spacing of the active downlink BWP of the scheduling cell for a configured grant if the power headroom report is reported on the PUSCH using the configured grant. + +If a UE + +- is configured with two UL carriers for a serving cell, and +- determines a Type 1 power headroom report and a Type 3 power headroom report for the serving cell + +the UE + +- provides the Type 1 power headroom report if both the Type 1 and Type 3 power headroom reports are based on respective actual transmissions or on respective reference transmissions +- provides the power headroom report that is based on a respective actual transmission if either the Type 1 report or the Type 3 report is based on a respective reference transmission + +If a UE is configured with a SCG and if $phr-ModeOtherCG$ for a CG indicates 'virtual' then, for power headroom reports transmitted on the CG, the UE computes $PH$ assuming that the UE does not transmit PUSCH/PUCCH on any serving cell of the other CG. For NR-DC when both the MCG and the SCG operate either in FR1 or in FR2 and for a + +power headroom report transmitted on the MCG or the SCG, the UE computes *PH* assuming that the UE does not transmit PUSCH/PUCCH on any serving cell of the SCG or the MCG, respectively. + +If the UE is configured with a SCG, + +- For computing power headroom for cells belonging to MCG, the term 'serving cell' in this clause refers to serving cell belonging to the MCG. +- For computing power headroom for cells belonging to SCG, the term 'serving cell' in this clause refers to serving cell belonging to the SCG. The term 'primary cell' in this clause refers to the PSCell of the SCG. + +If the UE is configured with a PUCCH-SCell, + +- For computing power headroom for cells belonging to primary PUCCH group, the term 'serving cell' in this clause refers to serving cell belonging to the primary PUCCH group. +- For computing power headroom for cells belonging to secondary PUCCH group, the term 'serving cell' in this clause refers to serving cell belonging to the secondary PUCCH group. The term 'primary cell' in this clause refers to the PUCCH-SCell of the secondary PUCCH group. + +For a UE configured with EN-DC/NE-DC and capable of dynamic power sharing, if E-UTRA Dual Connectivity PHR [14, TS 36.321] is triggered and, + +- if the duration of NR slot on active UL BWP is different from that of E-UTRA subframe carrying the Dual Connectivity PHR, the UE provides power headroom of the first NR slot that fully overlaps with the E-UTRA subframe; +- if the duration of NR slot on active UL BWP is the same as that of E-UTRA subframe carrying the Dual Connectivity PHR for asynchronous EN-DC/NE-DC [10, TS 38.133], the UE provides power headroom of the first NR slot that overlaps with the E-UTRA subframe. + +### 7.7.1 Type 1 PH report + +If a UE determines that a Type 1 power headroom report for an activated serving cell is based on an actual PUSCH transmission then, for PUSCH transmission occasion on active UL BWP of carrier of serving cell, the UE computes the Type 1 power headroom report as + +$$[dB]$$ + +where $\dots$ , and $\dots$ are defined in clause 7.1.1. + +If a UE is configured with multiple cells for PUSCH transmissions, where a SCS configuration on active UL BWP of carrier of serving cell is smaller than a SCS configuration on active UL BWP of carrier of serving cell, and if the UE provides a Type 1 power headroom report in a PUSCH transmission in a slot on active UL BWP that overlaps with multiple slots on active UL BWP, the UE provides a Type 1 power headroom report for the first PUSCH, if any, on the first slot of the multiple slots on active UL BWP that fully overlaps with the slot on active UL BWP. If a UE is configured with multiple cells for PUSCH transmissions, where a same SCS configuration on active UL BWP of carrier of serving cell and active UL BWP of carrier of serving cell, and if the UE provides a Type 1 power headroom report in a PUSCH transmission in a slot on active UL BWP, the UE provides a Type 1 power headroom report for the first PUSCH, if any, on the slot on active UL BWP that overlaps with the slot on active UL BWP. + +If a UE is configured with multiple cells for PUSCH transmissions and provides a Type 1 power headroom report in a PUSCH transmission with PUSCH repetition Type B having a nominal repetition that spans multiple slots on active UL BWP and overlaps with one or more slots on active UL BWP, the UE provides a Type 1 power headroom report for the first PUSCH, if any, on the first slot of the one or more slots on active UL BWP that overlaps with the multiple slots of the nominal repetition on active UL BWP. + +For a UE configured with EN-DC/NE-DC and capable of dynamic power sharing, if E-UTRA Dual Connectivity PHR [14, TS 36.321] is triggered, the UE provides power headroom of the first PUSCH, if any, on the determined NR slot as described in clause 7.7. + +If a UE is configured with multiple cells for PUSCH transmissions, the UE does not consider for computation of a Type 1 power headroom report in a first PUSCH transmission that includes an initial transmission of transport block on active UL BWP of carrier of serving cell, a second PUSCH transmission on active UL BWP of carrier of serving cell that overlaps with the first PUSCH transmission if + +- the second PUSCH transmission is scheduled by a DCI format in a PDCCH received in a second PDCCH monitoring occasion, and +- the second PDCCH monitoring occasion is after a first PDCCH monitoring occasion where the UE detects the earliest DCI format scheduling an initial transmission of a transport block after a power headroom report was triggered + +or + +- the second PUSCH transmission is after the first uplink symbol of the first PUSCH transmission minus $\Delta$ where $\Delta$ is determined according to [6, TS 38.214] assuming $\mu$ , and with $\Delta$ corresponding to the subcarrier spacing of the active downlink BWP of the scheduling cell for a configured grant if the first PUSCH transmission is on a configured grant after a power headroom report was triggered. + +If the UE determines that a Type 1 power headroom report for an activated serving cell is based on a reference PUSCH transmission then, for PUSCH transmission occasion on active UL BWP of carrier of serving cell, the UE computes the Type 1 power headroom report as + +$$[dB]$$ + +where $\Delta$ is computed assuming MPR=0 dB, A-MPR=0 dB, P-MPR=0 dB. $\Delta T_C = 0$ dB. MPR, A-MPR, P-MPR and $\Delta T_C$ are defined in [8-1, TS 38.101-1], [8-2, TS 38.101-2] and [8-3, TS 38.101-3]. The remaining parameters are defined in clause 7.1.1 and, if *ul-powerControl* is not provided, $P_{0-NP}$ and $\alpha$ are obtained using $p0-PUSCH-AlphaSetId = 0$ , $\alpha$ is obtained using *pusch-PathlossReferenceRS-Id* = 0, and $P_{0-NP}$ . If *ul-powerControl* is provided, $P_{0-NP}$ and $\alpha$ are obtained by *p0AlphaSetforPUSCH* associated with the indicated *TCI-State* or *TCI-UL-State*, $\alpha$ is obtained by PL-RS associated with the indicated *TCI-State* or *TCI-UL-State*. + +If a UE is configured with two UL carriers for a serving cell and the UE determines a Type 1 power headroom report for the serving cell based on a reference PUSCH transmission, the UE computes a Type 1 power headroom report for the serving cell assuming a reference PUSCH transmission on the UL carrier provided by *pusch-Config*. If the UE is provided *pusch-Config* for both UL carriers, the UE computes a Type 1 power headroom report for the serving cell assuming a reference PUSCH transmission on the UL carrier provided by *pucch-Config*. If *pucch-Config* is not provided to the UE for any of the two UL carriers, the UE computes a Type 1 power headroom report for the serving cell assuming a reference PUSCH transmission on the non-supplementary UL carrier. + +If a UE is not provided *twoPHRMode*, and is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook' on active UL BWP of carrier of serving cell, the UE provides one Type 1 power headroom report in a slot. If the Type 1 power headroom report is for an actual PUSCH repetition, the Type 1 power headroom report is for the first PUSCH repetition associated with the first SRS resource set or the second SRS resource set that overlaps with slot. + +If a UE is provided *twoPHRMode*, and is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook' on active UL BWP of carrier of serving cell, the UE provides two Type 1 power headroom reports in a slot, where + +- if the UE provides a first Type 1 power headroom report for an actual PUSCH repetition of a PUSCH transmission starting earliest in slot that is associated with one SRS resource set, +- if the UE transmits PUSCH repetitions associated with the other SRS resource set in slot, the UE provides a second Type 1 power headroom report for a first actual PUSCH repetition associated with the other SRS resource set that overlaps with slot +- else, the UE provides a second Type 1 power headroom report for a reference PUSCH transmission associated with the other SRS resource set, where + - if the other SRS resource set is the first SRS resource set, $P_{0-NP}$ and $\alpha$ are obtained using $p0-PUSCH-AlphaSetId = 0$ , $\alpha$ is obtained using *pusch-PathlossReferenceRS-Id* = 0 if the UE is not provided *enablePL-RS-UpdateForPUSCH-SRS* or is obtained from *PUSCH-PathlossReferenceRS-Id* mapped to *sri-PUSCH-PowerControlId* = 0 of *sri-PUSCH-MappingToAddModList* if the UE is provided *enablePL-RS-UpdateForPUSCH-SRS*, and $P_{0-NP}$ . If the UE is provided *dl-OrJointTCI-StateList* or *TCI-UL-State* that indicate a first *TCI-State* or *TCI-UL-State* and a second *TCI-State* or *TCI-UL-State*, the UE provides the second Type 1 power headroom report using the *p0AlphaSetforPUSCH* and *pathlossReferenceRS-Id-r17* values associated with the first *TCI-State* or *TCI-UL-State*. + +- else, and are obtained using and $p0\text{-PUSCH-AlphaSetId} = 1$ , is obtained using *pusch-PathlossReferenceRS-Id* = 1 if the UE is not provided *enablePL-RS-UpdateForPUSCH-SRS* or is obtained from *PUSCH-PathlossReferenceRS-Id* mapped to *sri-PUSCH-PowerControlId* = 0 of *sri-PUSCH-MappingToAddModList2* if the UE is provided *enablePL-RS-UpdateForPUSCH-SRS*, and if the UE is provided *twoPUSCH-PC-AdjustmentStates*, or if the UE is not provided *twoPUSCH-PC-AdjustmentStates*. If the UE is provided *dl-OrJointTCI-StateList* or *TCI-UL-State* that indicate a first *TCI-State* or *TCI-UL-State* and a second *TCI-State* or *TCI-UL-State*, the UE provides the second Type 1 power headroom report using the *p0AlphaSetforPUSCH* and *pathlossReferenceRS-Id-r17* values associated with the second *TCI-State* or *TCI-UL-State*. +- else, if the UE provides a Type 1 power headroom report for a reference PUSCH transmission associated with the first SRS resource set, the UE provides a Type 1 power headroom report for a reference PUSCH transmission associated with the second SRS resource set, where + - for the first Type 1 power headroom report, and are obtained using and $p0\text{-PUSCH-AlphaSetId} = 0$ , is obtained using *pusch-PathlossReferenceRS-Id* = 0 if the UE is not provided *enablePL-RS-UpdateForPUSCH-SRS*, or is obtained from the *PUSCH-PathlossReferenceRS-Id* mapped to *sri-PUSCH-PowerControlId* = 0 of *sri-PUSCH-MappingToAddModList* if the UE is provided *enablePL-RS-UpdateForPUSCH-SRS*, and . + - for the second Type 1 power headroom report, and are obtained using and $p0\text{-PUSCH-AlphaSetId} = 1$ , is obtained using *pusch-PathlossReferenceRS-Id* = 1 if the UE is not provided *enablePL-RS-UpdateForPUSCH-SRS*, or is obtained from the *PUSCH-PathlossReferenceRS-Id* mapped to *sri-PUSCH-PowerControlId* = 0 of *sri-PUSCH-MappingToAddModList2* if the UE is provided *enablePL-RS-UpdateForPUSCH-SRS*, and if the UE is provided *twoPUSCH-PC-AdjustmentStates* or if the UE is not provided *twoPUSCH-PC-AdjustmentStates* + - if a UE is provided *dl-OrJointTCI-StateList* or *TCI-UL-State* and is indicated a first *TCI-State* or *TCI-UL-State* and a second *TCI-State* or *TCI-UL-State*, the UE provides the first or the second Type 1 power headroom reports using the *p0AlphaSetforPUSCH* and *pathlossReferenceRS-Id-r17* values associated with the first *TCI-State* or *TCI-UL-State* or with the second *TCI-State* or *TCI-UL-State*, respectively, if the reference PUSCH transmission is associated with the first *TCI-State* or *TCI-UL-State* or with the second *TCI-State* or *TCI-UL-State*, respectively + +If a UE is provided, for active UL BWP of carrier of serving cell , + +- *twoPHRMode*, +- two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with usage set to 'codebook' or 'nonCodebook', +- *dl-OrJointTCI-StateList* or *TCI-UL-State* and is indicated a first *TCI-State* or *TCI-UL-State* and a second *TCI-State* or *TCI-UL-State*, and +- *multipanelScheme* + +the UE provides + +- a Type 1 power headroom report and a configured maximum output power associated with the first *TCI-State* or *TCI-UL-State* for an actual PUSCH transmission using a spatial domain filter corresponding only to the first *TCI-State* or *TCI-UL-State*, +- a Type 1 power headroom report and a configured maximum output power associated with the second *TCI-State* or *TCI-UL-State* for an actual PUSCH transmission using a spatial domain filter corresponding only to the second *TCI-State* or *TCI-UL-State*, +- a first Type 1 power headroom report and a first configured maximum output power associated with the first *TCI-State* or *TCI-UL-State*, and a second Type 1 power headroom report and a second configured maximum output power associated with the second *TCI-State* or *TCI-UL-State*, for an actual PUSCH transmission using a spatial domain filter corresponding to the first *TCI-State* or *TCI-UL-State* and using a spatial domain filter corresponding to the second *TCI-State* or *TCI-UL-State*. + +### 7.7.2 Type 2 PH report + +This clause is reserved. + +### 7.7.3 Type 3 PH report + +If a UE determines that a Type 3 power headroom report for an activated serving cell is based on an actual SRS transmission then, for SRS transmission occasion $i$ on active UL BWP $b$ of carrier $f$ of serving cell and if the UE is not configured for PUSCH transmissions on carrier $f$ of serving cell and the resource for the SRS transmission is provided by *SRS-Resource*, the UE computes a Type 3 power headroom report as + +$$PH_{\text{type3},b,f,c}(i,q_s) = P_{\text{CMAX},f,c}(i) - \left\{ P_{\text{O\_SRS},b,f,c}(q_s) + 10 \log_{10}(2^{\mu} \cdot M_{\text{SRS},b,f,c}(i)) + \alpha_{\text{SRS},b,f,c}(q_s) \cdot PL_{b,f,c}(q_d) + h_{b,f,c}(i) \right\} \text{ [dB]}$$ + +where $P_{\text{CMAX},f,c}(i)$ , $P_{\text{O\_SRS},b,f,c}(q_s)$ , $M_{\text{SRS},b,f,c}(i)$ , $\alpha_{\text{SRS},b,f,c}(q_s)$ , $PL_{b,f,c}(q_d)$ and $h_{b,f,c}(i)$ are defined in clause 7.3.1 with corresponding values provided by *SRS-ResourceSet*. + +If the UE determines that a Type 3 power headroom report for an activated serving cell is based on a reference SRS transmission then, for SRS transmission occasion $i$ on UL BWP $b$ of carrier $f$ of serving cell, and if the UE is not configured for PUSCH transmissions on UL BWP $b$ of carrier $f$ of serving cell and a resource for the reference SRS transmission is provided by *SRS-Resource*, the UE computes a Type 3 power headroom report as + +$$PH_{\text{type3},b,f,c}(i,q_s) = \tilde{P}_{\text{CMAX},f,c}(i) - \left\{ P_{\text{O\_SRS},b,f,c}(q_s) + \alpha_{\text{SRS},b,f,c}(q_s) \cdot PL_{b,f,c}(q_d) + h_{b,f,c}(i) \right\} \text{ [dB]}$$ + +where $q_s$ is an SRS resource set corresponding to *SRS-ResourceSetId* = 0 for UL BWP $b$ and $P_{\text{O\_SRS},b,f,c}(q_s)$ , $\alpha_{\text{SRS},f,c}(q_s)$ , $PL_{b,f,c}(q_d)$ and $h_{b,f,c}(i)$ are defined in clause 7.3.1 with corresponding values obtained from *SRS-ResourceSetId* = 0 for UL BWP $b$ . $\tilde{P}_{\text{CMAX},f,c}(i)$ is computed assuming MPR=0 dB, A-MPR=0 dB, P-MPR=0 dB and $\Delta T_c$ =0 dB. MPR, A-MPR, P-MPR and $\Delta T_c$ are defined in [8-1, TS 38.101-1], [8-2, TS 38.101-2] and [8-3, TS 38.101-3]. + +If a UE is configured with two UL carriers for a serving cell and the UE determines a Type 3 power headroom report for the serving cell based on a reference SRS transmission and a resource for the reference SRS is provided by *SRS-Resource*, the UE computes a Type 3 power headroom report for the serving cell assuming a reference SRS transmission on the UL carrier provided by *pucch-Config*. If *pucch-Config* is not provided to the UE for any of the two UL carriers, the UE computes a Type 3 power headroom report for the serving cell assuming a reference SRS transmission on the non-supplementary UL carrier. + +# --- 8 Random access procedure + +Prior to initiation of the physical random access procedure, Layer 1 receives from higher layers a set of SS/PBCH block indexes and provides to higher layers a corresponding set of RSRP measurements. + +Prior to initiation of the physical random access procedure, Layer 1 may receive from higher layers an indication to perform a Type-1 random access procedure, as described in clauses 8.1 through 8.4, or a Type-2 random access procedure as described in clauses 8.1 through 8.2A. + +Prior to initiation of the physical random access procedure, Layer 1 receives the following information from the higher layers: + +- Configuration of physical random access channel (PRACH) transmission parameters (PRACH preamble format, time resources, and frequency resources for PRACH transmission). +- Parameters for determining the root sequences and their cyclic shifts in the PRACH preamble sequence set (index to logical root sequence table, cyclic shift ( $N^{\text{CS}}$ ), and set type (unrestricted, restricted set A, or restricted set B)). + +From the physical layer perspective, the Type-1 L1 random access procedure includes the transmission of random access preamble (Msg1) in a PRACH, random access response (RAR) message with a PDCCH/PDSCH (Msg2), and when applicable, the transmission of a PUSCH scheduled by a RAR UL grant, and PDSCH for contention resolution. + +From the physical layer perspective, the Type-2 L1 random access procedure includes the transmission of random access preamble in a PRACH and of a PUSCH (MsgA) and the reception of a RAR message with a PDCCH/PDSCH (MsgB), and when applicable, the transmission of a PUSCH scheduled by a fallback RAR UL grant, and PDSCH for contention resolution. + +If a random access procedure is initiated by a PDCCH order to the UE, a PRACH transmission is with a same SCS as a PRACH transmission initiated by higher layers. + +If a UE is configured with two UL carriers for a serving cell and the UE detects a PDCCH order, the UE uses the UL/SUL indicator field value from the detected PDCCH order to determine the UL carrier for the corresponding PRACH transmission. + +## 8.1 Random access preamble + +Physical random access procedure for a UE is triggered upon request of a PRACH transmission by higher layers or by a PDCCH order for a cell. A configuration by higher layers for a PRACH transmission includes the following: + +- A configuration for PRACH transmission on the cell [4, TS 38.211]. +- A preamble index, a preamble SCS, , a corresponding RA-RNTI when applicable [11, TS 38.321], and a PRACH resource for the cell. +- A number of preamble repetitions for the PRACH transmission if the UE would transmit the PRACH with repetitions. + +A UE transmits a PRACH on a cell using the selected PRACH format with transmission power , as described in clause 7.4, on the indicated PRACH resource or on a determined set of resources using a same spatial filter in case of preamble repetitions. + +For Type-1 random access procedure, a UE is provided a number of SS/PBCH block indexes associated with one PRACH occasion and a number of contention based preambles per SS/PBCH block index per valid PRACH occasion by *ssb-perRACH-OccasionAndCB-PreamblesPerSSB*. + +For Type-2 random access procedure with common configuration of PRACH occasions with Type-1 random access procedure, a UE is provided a number of SS/PBCH block indexes associated with one PRACH occasion by *ssb-perRACH-OccasionAndCB-PreamblesPerSSB* and a number of contention based preambles per SS/PBCH block index per valid PRACH occasion by *msgA-CB-PreamblesPerSSB-PerSharedRO*. The PRACH transmission can be on a subset of PRACH occasions associated with a same SS/PBCH block index within an SSB-RO mapping cycle for a UE provided with a PRACH mask index by *msgA-SSB-SharedRO-MaskIndex* according to [11, TS 38.321]. + +For Type-2 random access procedure with separate configuration of PRACH occasions with Type-1 random access procedure, a UE is provided a number of SS/PBCH block indexes associated with one PRACH occasion and a number of contention based preambles per SS/PBCH block index per valid PRACH occasion by *msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB* when provided; otherwise, by *ssb-perRACH-OccasionAndCB-PreamblesPerSSB*. + +For a random access procedure associated with a feature combination indicated by *FeatureCombinationPreambles*, a UE is provided a number of SS/PBCH block indexes associated with one PRACH occasion by *ssb-perRACH-OccasionAndCB-PreamblesPerSSB* or *msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB* when provided and a number of contention based preambles per SS/PBCH block index per valid PRACH occasion by *startPreambleForThisPartition* and *numberOfPreamblesPerSSB-ForThisPartition*. The PRACH transmission can be on a subset of PRACH occasions associated with a same SS/PBCH block index within an SSB-RO mapping cycle for a UE provided with a PRACH mask index by *ssb-SharedRO-MaskIndex* according to [11, TS 38.321]. + +For Type-1 random access procedure, or for Type-2 random access procedure with separate configuration of PRACH occasions from Type 1 random access procedure, if , one SS/PBCH block index is mapped to consecutive valid PRACH occasions and contention based preambles with consecutive indexes associated with the SS/PBCH block index per valid PRACH occasion start from preamble index 0. If , contention based preambles with consecutive indexes associated with SS/PBCH block index , per valid PRACH occasion start from preamble index where is provided by *totalNumberOfRA-Preambles* for Type-1 random access procedure, or by *msgA-TotalNumberOfRA-Preambles* for + +Type-2 random access procedure with separate configuration of PRACH occasions from a Type 1 random access procedure, and is an integer multiple of . + +For Type-2 random access procedure with common configuration of PRACH occasions with Type-1 random access procedure, if , one SS/PBCH block index is mapped to consecutive valid PRACH occasions and contention based preambles with consecutive indexes associated with the SS/PBCH block index per valid PRACH occasion start from preamble index . If , contention based preambles with consecutive indexes associated with SS/PBCH block index , , per valid PRACH occasion start from preamble index , where is provided by *totalNumberOfRA-Preambles* for Type-1 random access procedure. + +For link recovery, a UE is provided SS/PBCH block indexes associated with one PRACH occasion by *ssb-perRACH-Occasion* in *BeamFailureRecoveryConfig*. For a dedicated RACH configuration provided by *RACH-ConfigDedicated*, if *cfra* is provided, a UE is provided SS/PBCH block indexes associated with one PRACH occasion by *ssb-perRACH-Occasion* in *occasions*. If , one SS/PBCH block index is mapped to consecutive valid PRACH occasions. If , all consecutive SS/PBCH block indexes are associated with one PRACH occasion. + +SS/PBCH block indexes provided by *ssb-PositionsInBurst* in *SIB1* or in *ServingCellConfigCommon* are mapped to valid PRACH occasions in the following order where the parameters are described in [4, TS 38.211]. + +- First, in increasing order of preamble indexes within a single PRACH occasion +- Second, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions +- Third, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot +- Fourth, in increasing order of indexes for PRACH slots + +An association period, starting from frame 0, for mapping SS/PBCH block indexes to PRACH occasions is the smallest integer number in the set determined by the PRACH configuration period according Table 8.1-1 such that SS/PBCH block indexes are mapped at least once to the PRACH occasions within the association period, where a UE obtains from the value of *ssb-PositionsInBurst* in *SIB1* or in *ServingCellConfigCommon*. If after an integer number of SS/PBCH block indexes to PRACH occasions mapping cycles within the association period there is a set of PRACH occasions or PRACH preambles that are not mapped to SS/PBCH block indexes, no SS/PBCH block indexes are mapped to the set of PRACH occasions or PRACH preambles. An association pattern period includes one or more association periods and is determined so that a pattern between PRACH occasions and SS/PBCH block indexes repeats at most every 160 msec. PRACH occasions not associated with SS/PBCH block indexes after an integer number of association periods, if any, are not used for PRACH transmissions. + +For a PRACH transmission by a UE triggered by a PDCCH order, the PRACH mask index field, if the value of the random access preamble index field is not zero, indicates the PRACH occasion for the PRACH transmission where the PRACH occasions are associated with the SS/PBCH block index indicated by the SS/PBCH block index field of the PDCCH order and, if any, a cell indicator field indicates a cell for the PRACH transmission [5, TS 38.212]. If the UE is provided by *cellSpecificKoffset*, the PRACH occasion is after slot where is the slot of the UL BWP for the PRACH transmission that overlaps with the end of the PDCCH order reception assuming , and is the SCS configuration for the PRACH transmission. If the PDCCH reception for the PDCCH order includes two PDCCH candidates from two linked search space sets based on *searchSpaceLinkingId*, as described in clause 10.1, the last symbol of the PDCCH reception is the last symbol of the PDCCH candidate that ends later. The PDCCH reception includes the two PDCCH candidates also when the UE is not required to monitor one of the two PDCCH candidates as described in clauses 10 (except clause 10.4), 11.1, 11.1.1 and 17.2. + +For a PRACH transmission triggered by higher layers, if *ssb-ResourceList* is provided, the PRACH mask index is indicated by *ra-ssb-OccasionMaskIndex* which indicates the PRACH occasions for the PRACH transmission where the PRACH occasions are associated with the selected SS/PBCH block index. + +The PRACH occasions are mapped consecutively per corresponding SS/PBCH block index. The indexing of the PRACH occasion indicated by the mask index value is reset per mapping cycle of consecutive PRACH occasions per SS/PBCH block index. The UE selects for a PRACH transmission the PRACH occasion indicated by PRACH mask index value for the indicated SS/PBCH block index in the first available mapping cycle. + +For the indicated preamble index, the ordering of the PRACH occasions is + +- First, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions + +- Second, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot +- Third, in increasing order of indexes for PRACH slots + +For a PRACH transmission with preamble repetitions, a set consists of valid PRACH occasions that are consecutive in time, use same frequency resources, and are associated with same one or more SS/PBCH block index(es), and each SS/PBCH block index is associated with same preamble indexes in all valid PRACH occasions within the set. + +For a PRACH transmission with preamble repetitions, a time period, starting from frame 0, is the smallest integer number of association pattern periods such that at least one set of valid PRACH occasions for each of the SS/PBCH block indexes can be determined within the time period for all configured number of preamble repetitions. The set(s) of valid PRACH occasions for each configured number of preamble repetitions repeats every time period. + +Within a time period, for set(s) of valid PRACH occasions for a PRACH transmission with preamble repetitions + +- the first valid PRACH occasion of the first set is the first valid PRACH occasion +- the first valid PRACH occasion of subsequent sets, if any, is determined according to an ordering of valid PRACH occasions + - first, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions + - second, in increasing order of time resource indexes for time multiplexed PRACH occasions + +where, for each frequency resource index for frequency multiplexed PRACH occasions + +- the first valid PRACH occasion of the first set is the first valid PRACH occasion +- the first valid PRACH occasion of subsequent sets, if any, + - is after *TimeOffsetBetweenStartingRO* consecutive valid PRACH occasions in time from the first valid PRACH occasion of the previous set, where each PRACH occasion is associated with same SS/PBCH block index(es) and each SS/PBCH block index is associated with same preambles, if *TimeOffsetBetweenStartingRO* is provided + - is after the PRACH occasions for the previous set, if *TimeOffsetBetweenStartingRO* is not provided + +For a PRACH transmission triggered upon request by higher layers, a value of *ra-OccasionList* [12, TS 38.331], if *csirs-ResourceList* is provided, indicates a list of PRACH occasions for the PRACH transmission where the PRACH occasions are associated with the selected CSI-RS index indicated by *csi-RS*. The indexing of the PRACH occasions indicated by *ra-OccasionList* is reset per association pattern period. + +**Table 8.1-1: Mapping between PRACH configuration period and SS/PBCH block to PRACH occasion association period** + +| PRACH configuration period (msec) | Association period (number of PRACH configuration periods) | +|-----------------------------------|------------------------------------------------------------| +| 10 | {1, 2, 4, 8, 16} | +| 20 | {1, 2, 4, 8} | +| 40 | {1, 2, 4} | +| 80 | {1, 2} | +| 160 | {1} | + +For paired spectrum or supplementary uplink band all PRACH occasions are valid. + +For unpaired spectrum, + +- if a UE is not provided *tdd-UL-DL-ConfigurationCommon*, a PRACH occasion in a PRACH slot is valid if it does not precede a SS/PBCH block in the PRACH slot and starts at least symbols after a last SS/PBCH block reception symbol, where is provided in Table 8.1-2 and, if *channelAccessMode* = "semiStatic" is provided, does not overlap with a set of consecutive symbols before the start of a next channel occupancy time where the UE does not transmit [15, TS 37.213]. + +- the candidate SS/PBCH block index of the SS/PBCH block corresponds to the SS/PBCH block index provided by *ssb-PositionsInBurst* in *SIB1* or in *ServingCellConfigCommon*, as described in clause 4.1 +- If a UE is provided *tdd-UL-DL-ConfigurationCommon*, a PRACH occasion in a PRACH slot is valid if + - it is within UL symbols, or + - it does not precede a SS/PBCH block in the PRACH slot and starts at least $\Delta$ symbols after a last downlink symbol and at least $\Delta$ symbols after a last SS/PBCH block symbol, where $\Delta$ is provided in Table 8.1-2, and if *channelAccessMode* = "semiStatic" is provided, does not overlap with a set of consecutive symbols before the start of a next channel occupancy time where there shall not be any transmissions, as described in [15, TS 37.213] + - the candidate SS/PBCH block index of the SS/PBCH block corresponds to the SS/PBCH block index provided by *ssb-PositionsInBurst* in *SIB1* or in *ServingCellConfigCommon*, as described in clause 4.1. + +For preamble format B4 [4, TS 38.211], . + +**Table 8.1-2: values for different preamble SCS** + +| Preamble SCS | | +|---------------------------------------|----| +| 1.25 kHz or 5 kHz | 0 | +| 15 kHz or 30 kHz or 60 kHz or 120 kHz | 2 | +| 480 kHz | 8 | +| 960 kHz | 16 | + +If a random access procedure is initiated by a PDCCH order, the UE, if requested by higher layers, transmits a PRACH in the selected PRACH occasion, as described in [11, TS 38.321], for which a time between the last symbol of the PDCCH order reception and the first symbol of the PRACH transmission is larger than or equal to $\Delta$ msec, where + +- $\Delta$ is a time duration of $\Delta$ symbols corresponding to a PUSCH preparation time for UE processing capability 1 [6, TS 38.214] assuming $\Delta$ corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH order and the SCS configuration of the corresponding PRACH transmission +- if the active UL BWP does not change, or if a cell indicator field in the PDCCH order indicates a non-serving cell [5, TS 38.212], and $\Delta$ is defined in [10, TS 38.133] otherwise +- $\Delta$ msec for FR1 and $\Delta$ msec for FR2 +- $\Delta$ is a switching gap duration as defined in [6, TS 38.214] +- if a cell indicator field in the PDCCH order indicates a serving cell or if cell indicator field is not present, and $\Delta$ is defined in [10, TS 38.133] otherwise +- if a cell indicator field in the PDCCH order indicates a serving cell or if cell indicator field is not present, and $\Delta$ is defined in [10, TS 38.133] otherwise + +For a PRACH transmission using 1.25 kHz or 5 kHz SCS, the UE determines $\Delta$ assuming SCS configuration . + +For single cell operation or for operation with contiguous carrier aggregation in a same frequency band or for operation with non-contiguous carrier aggregation in a same frequency band if the UE is not provided with *intraBandNC-PRACH-simulTx-r17*, a UE + +- does not transmit PRACH and PUSCH/PUCCH/SRS in a same slot with respect to the smallest SCS configuration between the SCS configuration for the UL BWP with the PRACH and the SCS configuration for the UL BWP with the PUSCH/PUCCH/SRS transmissions, +- does not transmit PRACH and PUSCH/PUCCH/SRS when a first or last symbol of a PRACH transmission in a first slot is separated by less than $\Delta$ symbols from the last or first symbol, respectively, of a PUSCH/PUCCH/SRS transmission in a second slot +- for a PRACH transmission with $\Delta$ preamble repetitions, if the UE does not indicate *capability-XYZ*, the UE does not transmit a first repetition of the PRACH and a second repetition of the PRACH when a first or last symbol of the first repetition of the PRACH in a first slot is separated by less than $\Delta$ symbols from the last or first symbol, respectively, of the second repetition of the PRACH in a second slot; otherwise, the UE transmits the first repetition of the PRACH and the second repetition of the PRACH + +where $\mu_{PRACH}$ for 1, $\mu_{PUSCH}$ for 0, $\mu_{PUCCH}$ for 1, $\mu_{SRS}$ for 2, and $\mu$ is the smallest SCS configuration between the SCS configuration for the UL BWP with the PRACH and the SCS configuration for the UL BWP with the PUSCH/PUCCH/SRS transmissions. For a PUSCH transmission with repetition Type B, this applies to each actual repetition for PUSCH transmission [6, TS 38.214]. + +## 8.1A PUSCH for Type-2 random access procedure + +For a Type-2 random access procedure, a UE transmits a PUSCH, when applicable, after transmitting a PRACH. The UE encodes a transport block provided for the PUSCH transmission using redundancy version number 0. The PUSCH transmission is after the PRACH transmission by at least $\Delta t_{PUSCH}$ symbols where $\mu_{PRACH}$ for 0, $\mu_{PUSCH}$ for 1, $\mu_{PUCCH}$ for 2, $\mu_{SRS}$ for 3, and $\mu$ is the SCS configuration for the active UL BWP. + +A UE does not transmit a PUSCH in a PUSCH occasion if the PUSCH occasion associated with a DMRS resource is not mapped to a preamble of valid PRACH occasions or if the associated PRACH preamble is not transmitted as described in clause 7.5 or clause 11.1 or clause 15 or clause 17.2. A UE can transmit a PRACH preamble in a valid PRACH occasion if the PRACH preamble is not mapped to a valid PUSCH occasion. + +A mapping between one or multiple PRACH preambles and a PUSCH occasion associated with a DMRS resource is per PUSCH configuration provided by *MsgA-PUSCH-Resource*. + +A UE determines time resources and frequency resources for PUSCH occasions in an active UL BWP from *msgA-PUSCH-Config* or *separateMsgA-PUSCH-Config* for the active UL BWP. If the active UL BWP is not the initial UL BWP and *msgA-PUSCH-Config* or *separateMsgA-PUSCH-Config* is not provided for the active UL BWP, the UE uses the *msgA-PUSCH-Config* or *separateMsgA-PUSCH-Config* provided for the initial UL BWP. + +A UE determines a first interlace or first RB for a first PUSCH occasion in an active UL BWP respectively from *interlaceIndexFirstPO-MsgA-PUSCH* or from *frequencyStartMsgA-PUSCH* that provides an offset, in number of RBs in the active UL BWP, from a first RB of the active UL BWP. A PUSCH occasion includes a number of interlaces or a number of RBs provided by *nrofInterlacesPerMsgA-PO* or by *nrofPRBs-perMsgA-PO*, respectively. Consecutive PUSCH occasions in the frequency domain of an UL BWP are separated by a number of RBs provided by *guardBandMsgA-PUSCH*. A number of PUSCH occasions in the frequency domain of an UL BWP is provided by *nrofMsgA-PO-FDM*. + +For operation with shared spectrum channel access, if the PUSCH occasion is provided by higher layer parameters *frequencyStartMsgA-PUSCH* and *nrofPRBs-perMsgA-PO*, the UE expects a PUSCH occasion to be confined within the same RB set as the corresponding PRACH transmission. + +For operation with shared spectrum channel access, if the PUSCH occasion is provided by higher layer parameters *interlaceIndexFirstPO-MsgA-PUSCH* and *nrofInterlacesPerMsgA-PO*, the RB set for the PUSCH occasion in the active UL BWP is the same RB set as the corresponding PRACH transmission. The UE assumes that the RB set is defined as when the UE is not provided *intraCellGuardBandsPerSCS* for an UL carrier as described in clause 7 of [6, TS 38.214]. + +If a UE does not have dedicated RRC configuration, or has an initial UL BWP as an active UL BWP, or is not provided *startSymbolAndLengthMsgA-PO*, *msgA-PUSCH-timeDomainAllocation* provides a SLIV and a PUSCH mapping type for a PUSCH transmission by indicating + +- one of the first *maxNrofUL-Allocations* values from *PUSCH-TimeDomainResourceAllocationList*, if *PUSCH-TimeDomainResourceAllocationList* is provided in *PUSCH-ConfigCommon* +- one of the entries from table 6.1.2.1.1-2 or table 6.1.2.1.1-3 in [6, TS 38.214], if *PUSCH-TimeDomainResourceAllocationList* is not provided in *PUSCH-ConfigCommon* + +else, the UE is provided a SLIV by *startSymbolAndLengthMsgA-PO*, and a PUSCH mapping type by *mappingTypeMsgA-PUSCH* for a PUSCH transmission. + +For mapping one or multiple preambles of a PRACH slot to a PUSCH occasion associated with a DMRS resource, a UE determines a first slot for a first PUSCH occasion in an active UL BWP from *msgA-PUSCH-TimeDomainOffset* that provides an offset, in number of slots in the active UL BWP, relative to the start of a PUSCH slot including the start of each PRACH slot. The UE does not expect to have a PRACH preamble transmission and a PUSCH transmission with a *msgA* in a PRACH slot or in a PUSCH slot, or to have overlapping *msgA* PUSCH occasions for a *MsgA* PUSCH configuration. The UE expects that a first PUSCH occasion in each slot has a same SLIV for a PUSCH transmission that is provided by *startSymbolAndLengthMsgA-PO* or *msgA-PUSCH-timeDomainAllocation* [6, TS 38.214]. + +Consecutive PUSCH occasions within each slot are separated by *guardPeriodMsgA-PUSCH* symbols and have same duration. A number of time domain PUSCH occasions in each slot is provided by *nrofMsgA-PO-perSlot* and a number of consecutive slots that include PUSCH occasions is provided by *nrofSlotsMsgA-PUSCH*. + +A UE is provided a DMRS configuration for a PUSCH transmission in a PUSCH occasion in an active UL BWP by *msgA-DMRS-Config*. + +A UE is provided an MCS for data information in a PUSCH transmission for a PUSCH occasion by *msgA-MCS*. + +For a PUSCH transmission with frequency hopping in a slot, when indicated by *msgA-intraSlotFrequencyHopping* for the active UL BWP, the frequency offset for the second hop [6, TS 38.214] is determined as described in clause 8.3, Table 8.3-1 using *msgA-HoppingBits* instead of *deltaFreq*. If *guardPeriodMsgA-PUSCH* is provided, a first symbol of the second hop is separated by *guardPeriodMsgA-PUSCH* symbols from the end of a last symbol of the first hop; otherwise, there is no time separation of the PUSCH transmission before and after frequency hopping. If a UE is provided with *useInterlacePUCCH-PUSCH* in *BWP-UplinkCommon*, the UE shall transmit PUSCH without frequency hopping. A PUSCH transmission uses a same spatial filter as an associated PRACH transmission. + +A UE determines whether or not to apply transform precoding for a PUSCH transmission as described in [6, TS 38.214]. + +A PUSCH occasion for PUSCH transmission is defined by a frequency resource and a time resource, and is associated with a DMRS resource. The DMRS resources are provided by *msgA-DMRS-Config*. + +Each consecutive number of preamble indexes from valid PRACH occasions in a PRACH slot + +- first, in increasing order of preamble indexes within a single PRACH occasion +- second, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions +- third, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot + +are mapped to a valid PUSCH occasion and the associated DMRS resource + +- first, in increasing order of frequency resource indexes for frequency multiplexed PUSCH occasions +- second, in increasing order of DMRS resource indexes within a PUSCH occasion, where a DMRS resource index is determined first in an ascending order of a DMRS port index and second in an ascending order of a DMRS sequence index [4, TS 38.211] +- third, in increasing order of time resource indexes for time multiplexed PUSCH occasions within a PUSCH slot +- fourth, in increasing order of indexes for PUSCH slots + +where $N_{PRACH}$ is a total number of valid PRACH occasions per association pattern period multiplied by the number of preambles per valid PRACH occasion provided by *rach-ConfigCommonTwoStepRA*, and $N_{PUSCH}$ is a total number of valid PUSCH occasions per PUSCH configuration per association pattern period multiplied by the number of DMRS resource indexes per valid PUSCH occasion provided by *msgA-DMRS-Config*. + +A PUSCH occasion is valid if it does not overlap in time and frequency with any valid PRACH occasion associated with either a Type-1 random access procedure or a Type-2 random access procedure. Additionally, for unpaired spectrum and for SS/PBCH blocks with indexes provided by *ssb-PositionsInBurst* in *SIB1* or by *ServingCellConfigCommon* + +- if a UE is not provided *tdd-UL-DL-ConfigurationCommon*, a PUSCH occasion is valid if the PUSCH occasion + - does not precede a SS/PBCH block in the PUSCH slot, and + - starts at least $O_{PUSCH}$ symbols after a last SS/PBCH block symbol, where $O_{PUSCH}$ is provided in Table 8.1-2 and, if *channelAccessMode* = "semiStatic" is provided, does not overlap with a set of consecutive symbols before the start of a next channel occupancy time where the UE does not transmit [15, TS 37.213]. +- if a UE is provided *tdd-UL-DL-ConfigurationCommon*, a PUSCH occasion is valid if the PUSCH occasion + - is within UL symbols, or + +- does not precede a SS/PBCH block in the PUSCH slot, and +- starts at least $\Delta$ symbols after a last downlink symbol and at least $\Delta$ symbols after a last SS/PBCH block symbol, where $\Delta$ is provided in Table 8.1-2 and, if *channelAccessMode* = "semiStatic" is provided, does not overlap with a set of consecutive symbols before the start of a next channel occupancy time where the UE does not transmit [15, TS 37.213]. + +## 8.2 Random access response - Type-1 random access procedure + +In response to a PRACH transmission, a UE attempts to detect a DCI format 1\_0 with CRC scrambled by a corresponding RA-RNTI during a window controlled by higher layers [11, TS 38.321] if the PRACH transmission is not triggered by a PDCCH order that includes a Cell Indicator field with non-zero value; otherwise, the UE does not attempt to detect the DCI format 1\_0. The window starts at the first symbol of the earliest CORESET the UE is configured to receive PDCCH for Type1-PDCCH CSS set, as defined in clause 10.1, that is at least one symbol, after the last symbol of the last PRACH occasion corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for Type1-PDCCH CSS set as defined in clause 10.1. If $\Delta$ or $\Delta_{msec}$ , as defined in [4, TS 38.211], is not zero, the window starts after an additional $\Delta_{msec}$ where $\Delta$ is defined in [4, TS 38.211] and is provided by *kmac* or if *kmac* is not provided. The length of the window in number of slots, based on the SCS for Type1-PDCCH CSS set, is provided by *ra-ResponseWindow*. + +If the UE detects the DCI format 1\_0 with CRC scrambled by the corresponding RA-RNTI and LSBs of a SFN field in the DCI format 1\_0, if included and applicable, are same as corresponding LSBs of the SFN where the UE transmitted PRACH, and the UE receives a transport block in a corresponding PDSCH within the window, the UE passes the transport block to higher layers. The higher layers parse the transport block for a random access preamble identity (RAPID) associated with the PRACH transmission. If the higher layers identify the RAPID in RAR message(s) of the transport block, the higher layers indicate an uplink grant to the physical layer. This is referred to as random access response (RAR) UL grant in the physical layer. + +If the UE does not detect the DCI format 1\_0 with CRC scrambled by the corresponding RA-RNTI within the window, or if the UE detects the DCI format 1\_0 with CRC scrambled by the corresponding RA-RNTI within the window and LSBs of a SFN field in the DCI format 1\_0, if included and applicable, are not same as corresponding LSBs of the SFN where the UE transmitted PRACH, or if the UE does not correctly receive the transport block in the corresponding PDSCH within the window, or if the higher layers do not identify the RAPID associated with the PRACH transmission from the UE, the higher layers can indicate to the physical layer to transmit a PRACH. If requested by higher layers, the UE shall be ready to transmit a PRACH no later than $\Delta$ msec after the last symbol of the window, or the last symbol of the PDSCH reception, where $\Delta$ is a time duration of $\Delta$ symbols corresponding to a PDSCH processing time for UE processing capability 1 assuming $\Delta$ corresponds to the smallest SCS configuration among the SCS configurations for the PDCCH carrying the DCI format 1\_0, the corresponding PDSCH when additional PDSCH DM-RS is configured, and the corresponding PRACH. For $\Delta$ , the UE assumes $\Delta$ [6, TS 38.214]. For a PRACH transmission using 1.25 kHz or 5 kHz SCS, the UE determines $\Delta$ assuming SCS configuration . + +If the UE detects a DCI format 1\_0 with CRC scrambled by the corresponding RA-RNTI and LSBs of a SFN field in the DCI format 1\_0, if included and applicable, are same as corresponding LSBs of the SFN where the UE transmitted the PRACH, and the UE receives a transport block in a corresponding PDSCH, the UE may assume same DM-RS antenna port quasi co-location properties, as described in [6, TS 38.214], as for a SS/PBCH block or a CSI-RS resource the UE used for PRACH association, as described in clause 8.1, regardless of whether or not the UE is provided *TCI-State* for the CORESET where the UE receives the PDCCH with the DCI format 1\_0. + +If the UE attempts to detect the DCI format 1\_0 with CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order that triggers a contention-free random access procedure for the SpCell [11, TS 38.321], the UE may assume that the PDCCH that includes the DCI format 1\_0 and the PDCCH order have same DM-RS antenna port quasi co-location properties. If the UE attempts to detect the DCI format 1\_0 with CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order that triggers a contention-free random access procedure for a secondary cell or if the PDCCH order is from a cell other than the serving cell, the UE may assume the DM-RS antenna port quasi co-location properties of the CORESET associated with the Type1-PDCCH CSS set for receiving the PDCCH that includes the DCI format 1\_0 and the PDSCH scheduled by the DCI format 1\_0. + +A RAR UL grant schedules a PUSCH transmission from the UE. The contents of the RAR UL grant, starting with the MSB and ending with the LSB, are given in Table 8.2-1. + +If the value of the frequency hopping flag is 0, the UE transmits the PUSCH without frequency hopping; otherwise, the UE transmits the PUSCH with frequency hopping. + +The UE determines the MCS of the PUSCH transmission from the first sixteen indexes of the applicable MCS index table for PUSCH as described in [6, TS 38.214]. + +The TPC command value is used for setting the power of the PUSCH transmission, as described in clause 7.1.1, and is interpreted according to Table 8.2-2. + +The CSI request field is reserved. + +The ChannelAccess-CPext field indicates a channel access type and CP extension for operation with shared spectrum channel access [15, TS 37.213] in FR1 as defined in Table 7.3.1.1.1-4 in [5, TS 38.212] or Table 7.3.1.1.1-4A in [5, TS 38.212] if *channelAccessMode* = "semiStatic" is provided. The ChannelAccess-CPext field indicates a channel access type for operation with shared spectrum channel access [15, TS 37.213] in FR2-2 as defined in Table 7.3.1.1.1-4B in [5, TS 38.212] if *ChannelAccessMode2-r17* is provided. + +**Table 8.2-1: Random Access Response Grant Content field size** + +| RAR grant field | Number of bits | +|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| Frequency hopping flag | 1 | +| PUSCH frequency resource allocation | 12, for operation with shared spectrum channel access in FR1 or for FR2-2 when ChannelAccessMode2-r17 is provided
14, otherwise | +| PUSCH time resource allocation | 4 | +| MCS | 4 | +| TPC command for PUSCH | 3 | +| CSI request | 1 | +| ChannelAccess-CPext | 2, for operation with shared spectrum channel access in FR1 or for FR2-2 when ChannelAccessMode2-r17 is provided
0, otherwise | + +**Table 8.2-2: TPC Command for PUSCH** + +| TPC Command | Value (in dB) | +|-------------|---------------| +| 0 | -6 | +| 1 | -4 | +| 2 | -2 | +| 3 | 0 | +| 4 | 2 | +| 5 | 4 | +| 6 | 6 | +| 7 | 8 | + +Unless the UE is configured a SCS, the UE receives subsequent PDSCH using same SCS as for the PDSCH reception providing the RAR message. + +If the UE does not detect the DCI format 1\_0 with CRC scrambled by the corresponding RA-RNTI within the window, or if the UE detects the DCI format 1\_0 with CRC scrambled by the corresponding RA-RNTI within the window and the LSBs of a SFN field in the DCI format 1\_0, if included and applicable, are not same as corresponding LSBs of the SFN where the UE transmitted the PRACH, or the UE does not correctly receive a corresponding transport block within the window, the UE procedure is as described in [11, TS 38.321]. + +## 8.2A Random access response - Type-2 random access procedure + +In response to a transmission of a PRACH and a PUSCH, or to a transmission of only a PRACH if the PRACH preamble is mapped to a valid PUSCH occasion, a UE attempts to detect a DCI format 1\_0 with CRC scrambled by a corresponding MsgB-RNTI during a window controlled by higher layers [11, TS 38.321]. The window starts at the first symbol of the earliest CORESET the UE is configured to receive PDCCH for Type1-PDCCH CSS set, as defined in clause 10.1, that is at least one symbol, after the last symbol of the PUSCH occasion corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for Type1-PDCCH CSS set. If $k_{mac}$ or $k_{mac}$ is not zero, the window starts after an additional msec where $k_{mac}$ is defined in [4, TS 38.211] and is provided by *kmac* or if *kmac* is not provided. The length of the window in number of slots, based on the SCS for Type1-PDCCH CSS set, is provided by *msgB-ResponseWindow*. + +In response to a transmission of a PRACH, if the PRACH preamble is not mapped to a valid PUSCH occasion, a UE attempts to detect a DCI format 1\_0 with CRC scrambled by a corresponding MsgB-RNTI during a window controlled by higher layers [11, TS 38.321]. The window starts at the first symbol of the earliest CORESET the UE is configured to receive PDCCH for Type1-PDCCH CSS set, as defined in clause 10.1, that is at least one symbol, after the last symbol of the PRACH occasion corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for Type1-PDCCH CSS set. The length of the window in number of slots, based on the SCS for Type1-PDCCH CSS set, is provided by *msgB-ResponseWindow*. + +If the UE detects the DCI format 1\_0, with CRC scrambled by the corresponding MsgB-RNTI and LSBs of a SFN field in the DCI format 1\_0, if applicable, are same as corresponding LSBs of the SFN where the UE transmitted PRACH, and the UE receives a transport block in a corresponding PDSCH within the window, the UE passes the transport block to higher layers. The higher layers indicate to the physical layer + +- an uplink grant if the RAR message(s) is for fallbackRAR and a random access preamble identity (RAPID) associated with the PRACH transmission is identified, and the UE procedure continues as described in clauses 8.2, 8.3, and 8.4 when the UE detects a RAR UL grant, or +- transmission of a PUCCH with HARQ-ACK information having ACK value if the RAR message(s) is for successRAR, where + - a PUCCH resource for the transmission of the PUCCH is indicated by PUCCH resource indicator field of 4 bits in the successRAR from a PUCCH resource set that is provided by *pucch-ResourceCommon* + - a slot for the PUCCH transmission is indicated by a HARQ Feedback Timing Indicator field of 3 bits in the successRAR having a value from {1, 2, 3, 4, 5, 6, 7, 8} for $\mu = 0$ , from {7, 8, 12, 16, 20, 24, 28, 32} for $\mu = 1$ , and from {13, 16, 24, 32, 40, 48, 56, 64} for $\mu = 2$ , and, with reference to slots for PUCCH transmission having duration $\geq 2$ , the slot is determined as $n$ , where $n$ is the last slot that overlaps with the DL slot for the PDSCH reception, $n$ is as defined for PUSCH transmission in Table 6.1.2.1.1-5 of [6, TS 38.214], $\mu$ is the SCS configuration of the active UL BWP, and $n$ is provided by *cellSpecificKoffset*, otherwise, if not provided, + - the UE does not expect the first symbol of the PUCCH transmission to be after the last symbol of the PDSCH reception by a time smaller than $msec$ where $msec$ is the PDSCH processing time for UE processing capability 1 [6, TS 38.214] + - for operation with shared spectrum channel access in FR1, a channel access type and CP extension [15, TS 37.213] for a PUCCH transmission is indicated by a ChannelAccess-CPext field in the successRAR as defined in Table 7.3.1.1.1-4 in [5, TS 38.212] or Table 7.3.1.1.1-4A in [5, TS 38.212] if *channelAccessMode* = "semiStatic" is provided + - for operation with shared spectrum channel access in FR2-2, a channel access type [15, TS 37.213] for a PUCCH transmission is indicated by a ChannelAccess-CPext field in the successRAR as defined in Table 7.3.1.1.1-4B in [5, TS 38.212] if *ChannelAccessMode2-r17* is provided + - the PUCCH transmission is with a same spatial domain transmission filter and in a same active UL BWP as a last PUSCH transmission + +If the UE detects the DCI format 1\_0 with CRC scrambled by a C-RNTI and a transport block in a corresponding PDSCH within the window, the UE transmits a PUCCH with HARQ-ACK information having ACK value if the UE correctly detects the transport block or NACK value if the UE incorrectly detects the transport block and the time alignment timer is running [11, TS 38.321]. + +If the UE detects a DCI format 1\_0 with CRC scrambled by the corresponding MsgB-RNTI and receives a transport block within the window in a corresponding PDSCH, the UE may assume same DM-RS antenna port quasi co-location properties, as described in [6, TS 38.214], as for a SS/PBCH block the UE used for PRACH association, as described in clause 8.1, regardless of whether or not the UE is provided *TCI-State* for the CORESET where the UE receives the PDCCH with the DCI format 1\_0. + +The UE does not expect to be indicated to transmit the PUCCH with the HARQ-ACK information at a time that is prior to a time when the UE applies a TA command that is provided by the transport block. If the UE does not detect the DCI format 1\_0 with CRC scrambled by the corresponding MsgB-RNTI within the window, or if the UE detects the DCI format 1\_0 with CRC scrambled by the corresponding MsgB-RNTI within the window and LSBs of a SFN field in the DCI format 1\_0, if applicable, are not same as corresponding LSBs of the SFN where the UE transmitted the PRACH, or if the UE does not correctly receive the transport block in the corresponding PDSCH within the window, or if the + +higher layers do not identify the RAPID associated with the PRACH transmission from the UE, the higher layers can indicate to the physical layer to transmit only PRACH according to Type-1 random access procedure or to transmit both PRACH and PUSCH according to Type-2 random access procedure [11, TS 38.321]. If requested by higher layers, the UE shall be ready to transmit a PRACH no later than msec after the last symbol of the window, or the last symbol of the PDSCH reception, where is a time duration of symbols corresponding to a PDSCH processing time for UE processing capability 1 when additional PDSCH DM-RS is configured. For , the UE assumes [6, TS 38.214]. + +Unless the UE is configured a SCS, the UE receives subsequent PDSCH using same SCS as for the PDSCH reception providing the RAR message. + +If the UE does not detect the DCI format 1\_0 with CRC scrambled by the corresponding MsgB-RNTI within the window, or if the UE detects the 1\_0 with CRC scrambled by the corresponding MsgB-RNTI within the window and LSBs of a SFN field in the DCI format 1\_0, if applicable, are not same as corresponding LSBs of the SFN where the UE transmitted the PRACH, or the UE does not correctly receive a corresponding transport block within the window, the UE procedure is as described in [11, TS 38.321]. + +## 8.3 PUSCH scheduled by RAR UL grant + +An active UL BWP with SCS configuration , as described in clause 12 and in [4, TS 38.211], for a PUSCH transmission scheduled by a RAR UL grant is indicated by higher layers. + +If *useInterlacePUCCH-PUSCH* is not provided by *BWP-UplinkCommon* and *BWP-UplinkDedicated*, for determining the frequency domain resource allocation for the PUSCH transmission within the active UL BWP + +- if the active UL BWP and the initial UL BWP have same SCS and same CP length and the active UL BWP includes all RBs of the initial UL BWP, or the active UL BWP is the initial UL BWP, the initial UL BWP is used +- else, the RB numbering starts from the first RB of the active UL BWP and the maximum number of RBs for frequency domain resource allocation equals the number of RBs in the initial UL BWP + +The frequency domain resource allocation is by uplink resource allocation type 1 [6, TS 38.214]. For an initial UL BWP size of RBs, a UE processes the frequency domain resource assignment field as follows + +- if, or for operation with shared spectrum channel access in FR1 or for FR2-2 when *ChannelAccessMode2-r17* is provided if + - truncate the frequency domain resource assignment field to its least significant bits and interpret the truncated frequency resource assignment field as for the frequency resource assignment field in DCI format 0\_0 as described in [5, TS 38.212] +- else + - insert + - most significant bits, for operation with shared spectrum channel access in FR1 or for FR2-2 when *ChannelAccessMode2-r17* is provided; + - most significant bits, otherwise; + with value set to '0' after the bits to the frequency domain resource assignment field, where if the frequency hopping flag is set to '0' and is provided in Table 8.3-1 if the hopping flag bit is set to '1', and interpret the expanded frequency resource assignment field as for the frequency resource assignment field in DCI format 0\_0 as described in [5, TS 38.212] +- end if + +If *useInterlacePUCCH-PUSCH* is provided by *BWP-UplinkCommon* or *BWP-UplinkDedicated*, the frequency domain resource allocation is by uplink resource allocation type 2 [6, TS 38.214]. A UE processes the frequency domain resource assignment field as follows + +- truncate the frequency domain resource assignment field to the LSBs if , or to the LSBs if + +- for interlace allocation of a PUSCH transmission, interpret the MSBs of the truncated frequency domain resource assignment field for the active UL BWP as for the MSBs of the frequency domain resource assignment field in DCI format 0\_0 [6, TS 38.214] +- for RB set allocation of a PUSCH transmission, the RB set of the active UL BWP is the RB set of the PRACH transmission associated with the RAR UL grant. The UE assumes that the RB set is defined as when the UE is not provided *intraCellGuardBandsUL-List* [6, TS 38.214]. + +A UE determines whether or not to apply transform precoding as described in [6, TS 38.214]. + +For a PUSCH transmission with frequency hopping scheduled by RAR UL grant or for a Msg3 PUSCH retransmission, the frequency offset for the second hop [6, TS 38.214] is given in Table 8.3-1. + +**Table 8.3-1: Frequency offset for second hop of PUSCH transmission with frequency hopping scheduled by RAR UL grant or of Msg3 PUSCH retransmission** + +| Number of PRBs in initial UL BWP | Value of Hopping Bits | Frequency offset for 2 nd hop | +|----------------------------------|-----------------------|------------------------------------------| +| | 0 | | +| | 1 | | +| | 00 | | +| | 01 | | +| | 10 | | +| | 11 | Reserved | + +A SCS for the PUSCH transmission is provided by *subcarrierSpacing* in *BWP-UplinkCommon*. A UE transmits PRACH and the PUSCH on a same uplink carrier of a same serving cell. + +A UE transmits a transport block in a PUSCH scheduled by a RAR UL grant in a corresponding RAR message using redundancy version number 0, if the PUSCH transmission is without repetitions. If a TC-RNTI is provided by higher layers, the scrambling initialization of the PUSCH corresponding to the RAR UL grant in clause 8.2 is by TC-RNTI. Otherwise, the scrambling initialization of the PUSCH corresponding to the RAR UL grant in clause 8.2 is by C-RNTI. + +Msg3 PUSCH retransmissions, if any, of the transport block, are scheduled by a DCI format 0\_0 with CRC scrambled by a TC-RNTI provided in the corresponding RAR message [11, TS 38.321]. + +With reference to slots for a PUSCH transmission scheduled by a RAR UL grant, if a UE receives a PDSCH with a RAR message ending in slot for a corresponding PRACH transmission from the UE, the UE transmits the PUSCH in slot , where and are provided in [6, TS 38.214] and is provided by *cellSpecificKoffset*; otherwise, if not provided, . + +A UE can be provided in *BWP-UplinkCommon* a set of numbers of repetitions for a PUSCH transmission with PUSCH repetition Type A that is scheduled by a RAR UL grant or by a DCI format 0\_0 with CRC scrambled by a TC-RNTI. If the UE requests repetitions for the PUSCH transmission [11, TS 38.321], the UE transmits the PUSCH over slots, where is indicated by the 2 MSBs of the MCS field in the RAR UL grant or in the DCI format 0\_0 from a set of four values provided by *numberOfMsg3-RepetitionsList* or from {1, 2, 3, 4} if *numberOfMsg3-RepetitionsList* is not provided. The UE determines an MCS for the PUSCH transmission by the 2 LSBs of the MCS field in the RAR UL grant or by the 3 LSBs of the MCS field in the DCI format 0\_0, and determines a redundancy version and RBs for each repetition as described in [6, TS 38.214]. For unpaired spectrum operation, the UE determines the slots as the first slots starting from slot where a repetition of the PUSCH transmission does not include a symbol indicated as downlink by *tdd-UL-DL-ConfigurationCommon* or indicated as a symbol of an SS/PBCH block with index provided by *ssb-PositionsInBurst*. + +The UE may assume a minimum time between the last symbol of a PDSCH reception conveying a RAR message with a RAR UL grant and the first symbol of a corresponding PUSCH transmission scheduled by the RAR UL grant is equal to msec, where is a time duration of symbols corresponding to a PDSCH processing time for UE processing capability 1 when additional PDSCH DM-RS is configured, is a time duration of symbols corresponding to a PUSCH preparation time for UE processing capability 1 [6, TS 38.214] and, for determining the minimum time, the UE considers that and correspond to the smaller of the SCS configurations for the PDSCH and the PUSCH. For , the UE assumes [6, TS 38.214]. + +## 8.4 PDSCH with UE contention resolution identity + +In response to a PUSCH transmission scheduled by a RAR UL grant when a UE has not been provided a C-RNTI, the UE attempts to detect a DCI format 1\_0 with CRC scrambled by a corresponding TC-RNTI scheduling a PDSCH that includes a UE contention resolution identity [11, TS 38.321]. In response to the PDSCH reception with the UE contention resolution identity, the UE transmits HARQ-ACK information in a PUCCH. The PUCCH transmission is within a same active UL BWP as the PUSCH transmission. A minimum time between the last symbol of the PDSCH reception and the first symbol of the corresponding PUCCH transmission with the HARQ-ACK information is equal to msec. is a time duration of symbols corresponding to a PDSCH processing time for UE processing capability 1 when additional PDSCH DM-RS is configured. For , the UE assumes [6, TS 38.214]. + +When detecting a DCI format in response to a PUSCH transmission scheduled by a RAR UL grant, as described in [11, TS 38.321], or corresponding PUSCH retransmission scheduled by a DCI format 0\_0 with CRC scrambled by a TC-RNTI provided in the corresponding RAR message [11, TS 38.321], the UE may assume the PDCCH carrying the DCI format has the same DM-RS antenna port quasi co-location properties, as described in [6, TS 38.214], as for a SS/PBCH block the UE used for PRACH association, as described in clause 8.1, regardless of whether or not the UE is provided TCI-State for the CORESET where the UE receives the PDCCH with the DCI format. + +# 9 UE procedure for reporting control information + +If a UE is configured with a SCG, the UE shall apply the procedures described in this clause for both MCG and SCG. + +- When the procedures are applied for MCG, the terms 'secondary cell', 'secondary cells', 'serving cell', 'serving cells' in this clause refer to secondary cell, secondary cells, serving cell, serving cells belonging to the MCG respectively. +- When the procedures are applied for SCG, the terms 'secondary cell', 'secondary cells', 'serving cell', 'serving cells' in this clause refer to secondary cell, secondary cells (not including PSCell), serving cell, serving cells belonging to the SCG respectively. The term 'primary cell' in this clause refers to the PSCell of the SCG. + +If a UE is configured with a PUCCH-SCell, the UE shall apply the procedures described in this clause for both primary PUCCH group and secondary PUCCH group + +- When the procedures are applied for the primary PUCCH group, the terms 'secondary cell', 'secondary cells', 'serving cell', 'serving cells' in this clause refer to secondary cell, secondary cells, serving cell, serving cells belonging to the primary PUCCH group respectively. +- When the procedures are applied for secondary PUCCH group, the terms 'secondary cell', 'secondary cells', 'serving cell', 'serving cells' in this clause refer to secondary cell, secondary cells (not including the PUCCH-SCell), serving cell, serving cells belonging to the secondary PUCCH group respectively. The term 'primary cell' in this clause refers to the PUCCH-SCell of the secondary PUCCH group. If *pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup-r16* is provided, *pdsch-HARQ-ACK-Codebook* is replaced by *pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup-r16*. If *harq-ACK-SpatialBundlingPUCCH-secondaryPUCCHgroup* is provided, *harq-ACK-SpatialBundlingPUCCH* is replaced by *harq-ACK-SpatialBundlingPUCCH-secondaryPUCCHgroup*. If *harq-ACK-SpatialBundlingPUSCH-secondaryPUCCHgroup* is provided, *harq-ACK-SpatialBundlingPUSCH* is replaced by *harq-ACK-SpatialBundlingPUSCH-secondaryPUCCHgroup*. If *uci-MuxWithDiffPrioSecondaryPUCCHgroup* is provided, *uci-MuxWithDiffPrio* is replaced by *uci-MuxWithDiffPrioSecondaryPUCCHgroup*. If *simultaneousPUCCH-PUSCH-secondaryPUCCHgroup* is provided, *simultaneousPUCCH-PUSCH* is replaced by *simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup*. If *simultaneousPUCCH-PUSCH-SamePriority-secondaryPUCCHgroup* is provided, *simultaneousPUCCH-PUSCH-SamePriority* is replaced by *simultaneousPUCCH-PUSCH-SamePriority-SecondaryPUCCHgroup*. If *pucch-sSCellSecondaryPUCCHgroup* is provided, *pucch-sSCell* is replaced by *pucch-sSCellSecondaryPUCCHgroup*. If *pucch-sSCellPatternSecondaryPUCCHgroup* is provided, *pucch-sSCellPattern* is replaced by *pucch-sSCellPatternSecondaryPUCCHgroup*. If *pucch-sSCellDynSecondaryPUCCHgroup* is provided, *pucch-sSCellDyn* is replaced by *pucch-sSCellDynSecondaryPUCCHgroup*. If *pdsch-HARQ-ACK-EnhType3SecondaryToAddModList* is provided, *pdsch-HARQ-ACK-EnhType3ToAddModList* is replaced by *pdsch-HARQ-ACK-EnhType3SecondaryToAddModList*. If *pdsch-HARQ-ACK-RetxSecondaryPUCCHgroup* is provided, *pdsch-HARQ-ACK-Retx* is replaced by *pdsch-HARQ-ACK-RetxSecondaryPUCCHgroup*. + +If a UE is provided *MC-DCI-SetofCells* for scheduling by a DCI format PDSCH receptions or PUSCH transmissions on serving cells from a set of more than one serving cells, the UE expects the more than one serving cells to be in a same + +PUCCH group. The UE provides HARQ-ACK information in a same HARQ-ACK codebook for sets of serving cells that are associated with a same PUCCH group. The UE does not expect to be configured to receive multicast PDSCH on serving cells of the same PUCCH group as serving cells from the sets of serving cells. + +For unpaired spectrum operation, if a UE is provided a PUCCH-sSCell as described in clause 9.A, the UE shall apply the procedures described in this clause for both the primary cell and the PUCCH-sSCell. + +If a UE is provided *pdsch-HARQ-ACK-CodebookList-r16*, *pdsch-HARQ-ACK-Codebook* is replaced by the relevant entry in *pdsch-HARQ-ACK-CodebookList-r16*. + +In the remaining of this clause, when a PDCCH reception by a UE includes two PDCCH candidates from corresponding search space sets, as described in clause 10.1 + +- a PDCCH monitoring occasion is the union of the PDCCH monitoring occasions for the two PDCCH candidates +- the start of the PDCCH reception is the start of the earlier PDCCH candidate +- the end of the PDCCH reception is the end of the PDCCH candidate that ends later + +The PDCCH reception includes the two PDCCH candidates also when the UE is not required to monitor one of the two PDCCH candidates as described in clauses 10 (except clause 10.4), 11.1, 11.1.1 and 17.2. + +In the remaining of this clause, a last DCI format is from a set of detected DCI formats for which the UE would provide HARQ-ACK information in a PUCCH in a same slot. Detected DCI formats are first indexed in ascending order across indexes of respective scheduled cells for a same PDCCH monitoring occasion, and are then indexed in ascending order across indexes of PDCCH monitoring occasions. For indexing a detected DCI format associated with two or more scheduled cells, a respective scheduled cell is the one with the smallest index among the two or more scheduled cells. For a PDCCH monitoring occasion and a scheduled cell, if a UE is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with value 0 for one or more first CORESETs and is provided *coresetPoolIndex* with value 1 for one or more second CORESETs on an active DL BWP of a serving cell, and is provided *ackNackFeedbackMode = joint* for the active UL BWP, detected DCI formats from PDCCH receptions in the first CORESETs are indexed prior to detected DCI formats from PDCCH receptions in the second CORESETs. + +For the purpose of determining timeline conditions in this clause, + +- if a UE would transmit a PUCCH with HARQ-ACK information in response to a first SPS PDSCH reception after an activation of SPS PDSCH receptions, the PUCCH is considered as a PUCCH transmission in response to a DCI format detection; +- if a UE would transmit a configured grant Type 2 PUSCH in the first transmission occasion after an activation of configured grant Type 2 PUSCH transmissions, the PUSCH is considered as a PUSCH transmission in response to a DCI format detection. + +If a UE + +- is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with a value of 0 for first CORESETs on active DL BWPs of serving cells, and +- is provided *coresetPoolIndex* with a value of 1 for second CORESETs on active DL BWPs of the serving cells, and +- is provided *ackNackFeedbackMode = separate* + +the UE shall separately apply the procedures described in clauses 9.1 and 9.2.3 for reporting HARQ-ACK information associated with the first CORESETs on active DL BWP of the serving cells and for reporting HARQ-ACK information associated with the second CORESETs on active DL BWP of the serving cells, and the UE does not expect to be provided with *subslotLengthForPUCCH* or to be indicated by *pdsch-HARQ-ACK-CodebookList* to generate two HARQ-ACK codebooks on active DL BWP of the serving cells. HARQ-ACK information reporting is associated with a CORESET through a reception of a PDCCH with a DCI format triggering the reporting of the HARQ-ACK information by the UE. + +For NR-DC when both the MCG and the SCG operate either in FR1 or in FR2 and for a power headroom report transmitted on the MCG or the SCG, the UE computes *PH* assuming that the UE does not transmit PUSCH/PUCCH on any serving cell of the SCG or the MCG, respectively. + +If a UE is configured for NR-DC operation, the UE does not expect to be configured with a PUCCH-SCell. + +A PUSCH or a PUCCH transmission other than PUCCH transmissions with SL HARQ-ACK reports, including repetitions if any, can be of priority index 0 or of priority index 1. For a configured grant PUSCH transmission, a UE determines a priority index from *phy-PriorityIndex*, if provided. For a PUCCH transmission with HARQ-ACK information corresponding to a SPS PDSCH reception or a SPS PDSCH release, a UE determines a priority index from *harq-CodebookID*, if provided. For a PUCCH transmission with SR, a UE determines the corresponding priority as described in clause 9.2.4. For a PUSCH transmission with semi-persistent CSI report, a UE determines a priority index from a priority indicator field, if provided, in a DCI format that activates the semi-persistent CSI report. If a priority index is not provided to a UE for a PUSCH or a PUCCH transmission other than PUCCH transmissions with SL HARQ-ACK reports, the priority index is 0. + +If a UE is provided one *PUCCH-Config* + +- if the UE is provided *subslotLengthForPUCCH* in the *PUCCH-Config*, the PUCCH resource for any SR configuration with priority index 0 or any CSI report configuration in the *PUCCH-Config* is within the *subslotLengthForPUCCH* symbols in the *PUCCH-Config* + +If a UE is provided two *PUCCH-Config* + +- if the UE is provided *subslotLengthForPUCCH* in the first *PUCCH-Config*, the PUCCH resource for any SR configuration with priority index 0 or any CSI report configuration in any *PUCCH-Config* is within the *subslotLengthForPUCCH* symbols in the first *PUCCH-Config* +- if the UE is provided *subslotLengthForPUCCH* in the second *PUCCH-Config*, the PUCCH resource for any SR configuration with priority index 1 in any *PUCCH-Config* is within the *subslotLengthForPUCCH* symbols in the second *PUCCH-Config* + +If a UE is provided *subslotLengthForPUCCH* in a *PUCCH-Config* of a given priority index, in a slot of symbols [4, TS 38.211] with HARQ-ACK, the UE does not expect that HARQ-ACK information in response to SPS PDSCH reception(s) only (if any) or SR (if any) of the given priority index in a slot of *subslotLengthForPUCCH* symbols is moved to a different slot of *subslotLengthForPUCCH* symbols after multiplexing overlapping PUCCHs. + +If in an active DL BWP a UE monitors PDCCH for detection of DCI format that includes a priority indicator field, a priority index can be provided by the priority indicator field. If a UE indicates a capability to monitor, in an active DL BWP, PDCCH for detection of DCI format that includes a priority indicator field, the DCI format can schedule PUSCH transmissions of any priority, or PDSCH receptions and/or trigger a PUCCH transmission with corresponding HARQ-ACK information of any priority, and DCI format 1\_1 or DCI format 1\_2 with a Transmission Configuration Indication field can indicate a TCI state update and trigger a PUCCH transmission with corresponding HARQ-ACK information of any priority. + +A DCI format indicating a SPS PDSCH release, or SCell dormancy without scheduling a PDSCH reception, or indicating a TCI state update without scheduling PDSCH reception, is referred to as a DCI format having associated HARQ-ACK information without scheduling a PDSCH reception. + +For the remaining of this clause, when a UE + +- is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with a value of 0 for first CORESETs, and is provided *coresetPoolIndex* with a value of 1 for second CORESETs, on active DL BWPs of serving cells, and +- is provided *enableSTx2PofmDCI* + +the UE separately determines and resolves time overlapping among first PUSCH transmissions that use respective first spatial domain filters corresponding to first *TCI-State* or *TCI-UL-State* associated with the first CORESETs, and among second PUSCH transmissions that use respective second spatial domain filters corresponding to second *TCI-State* or *TCI-UL-State* associated with the second CORESETs. + +When a UE determines overlapping for PUCCH transmissions with SL HARQ-ACK reports and PUCCH of larger and/or smaller priority index, the UE resolves the overlapping for PUCCH transmissions with SL HARQ-ACK reports and PUCCH of each priority index as described in clause 9.2.5 and 9.2.6 before resolving the overlapping for PUCCH transmissions without SL HARQ-ACK or the overlapping for PUCCH transmissions and PUSCH transmissions. + +When a UE determines overlapping for PUCCH and/or PUSCH transmissions of the same priority index other than PUCCH transmissions with SL HARQ-ACK reports before considering limitations for UE + +transmission due to cell DRX operation [11, TS 38.321] or as described in clauses 11.1, 11.1.1, 11.2A, 15 and 17.2 including repetitions if any, + +- first, the UE resolves the overlapping for PUCCHs with repetitions as described in clause 9.2.6, if any +- second, the UE resolves the overlapping for PUCCHs without repetitions as described in clauses 9.2.5 +- third, the UE resolves the overlapping for PUSCHs and PUCCHs with repetitions as described in clause 9.2.6 +- fourth, the UE resolves the overlapping for PUSCHs and PUCCHs without repetitions as is subsequently described in this clause. + +If a UE + +- is provided *simultaneousPUCCH-PUSCH* and would transmit a PUCCH with a first priority index and PUSCHs with a second priority index that is different than the first priority index, where the PUCCH and the PUSCHs overlap in time on different respective cells +- can simultaneously transmit the PUCCH and the PUSCHs with different priority indexes [18, TS 38.306], + +the UE excludes the PUSCHs for resolving the time overlapping between the PUCCH and PUSCHs with different priority indexes, where the timeline conditions for resolving the overlapping PUCCH and PUSCHs are not required for the excluded PUSCHs. + +If a UE + +- is provided *simultaneousPUCCH-PUSCH-SamePriority* and would transmit a PUCCH and PUSCHs with same priority index, where the PUCCH and the PUSCHs overlap in time on different respective cells, +- can simultaneously transmit the PUCCH and the PUSCHs with same priority index [18, TS 38.306], + +the UE excludes the PUSCHs for resolving the time overlapping between the PUCCH and PUSCHs with same priority index, where the timeline conditions for resolving the overlapping PUCCH and PUSCHs are not required for the excluded PUSCHs. + +When a UE determines overlapping for PUCCH and/or PUSCH transmissions of different priority indexes, other than PUCCH transmissions with SL HARQ-ACK reports, before considering limitations for transmission due to cell DRX operation or as described in clauses 11.1, 11.1.1, 11.2A, 15 and 17.2 including repetitions if any, if the UE is provided *uci-MuxWithDiffPrio* and the timeline conditions in clause 9.2.5 for multiplexing UCI in a PUCCH or a PUSCH are satisfied + +- first, the UE resolves overlapping for PUCCH and/or PUSCH transmissions of a same priority index as described in clauses 9.2.5 and 9.2.6 +- second, the UE resolves the overlapping for PUCCH transmissions of different priority indexes, and + - if the UE is provided *subslotLengthForPUCCH* in the second *PUCCH-Config*, a PUCCH transmission of smaller priority index is associated with the first overlapping slot with *subslotLengthForPUCCH* symbols of larger priority index; otherwise, the PUCCH transmission of smaller priority index is associated with the overlapping slot with symbols [4, TS 38.211] of larger priority index. + - the UE first resolves the overlapping for PUCCH transmissions, where at least one of the PUCCH transmissions is with repetitions, within a slot of larger priority index as is subsequently described in this clause, if any, and then the UE resolves the overlapping for PUCCH transmissions without repetitions within the slot using the pseudo-code in clause 9.2.5 + - if the UE determines that a first PUCCH transmission of the smaller priority index is not dropped and the UCI of the first PUCCH transmission is not multiplexed in a second PUCCH transmission of larger priority index in an overlapping slot with *subslotLengthForPUCCH* symbols, the first PUCCH transmission is associated with the next overlapping slot with *subslotLengthForPUCCH* symbols for PUCCH transmissions with the larger priority index + - the UE does not expect a PUCCH transmission that includes UCI of different priority indexes to overlap with a PUCCH transmission with repetitions after resolving the overlapping for PUCCH transmissions without repetitions within a slot + +- the UE does not expect a PUCCH transmission with UCI of first and second priority indexes to overlap with a PUCCH transmission with HARQ-ACK information of the first priority index, or with a PUCCH transmission or with a PUSCH transmission of the second priority index when the second priority index is larger than the first priority index +- the UE does not expect a PUCCH transmission with HARQ-ACK information of larger priority index to overlap with more than one PUCCH transmissions with HARQ-ACK information of smaller priority index +- third, the UE resolves the overlapping for PUCCH and PUSCH transmissions of different priority indexes + - the UE drops PUSCH transmissions of smaller priority index that overlap with a PUCCH transmission with positive SR of larger priority index prior to multiplexing UCI in a PUSCH transmission of smaller priority index, if any + - the UE drops PUSCH transmissions of smaller priority index that overlap with a PUCCH transmission with repetitions of larger priority index prior to multiplexing UCI in a PUSCH transmission of smaller priority index, if any + - the UE multiplexes HARQ-ACK information in a PUSCH transmission, as is subsequently described in this clause for multiplexing HARQ-ACK information from a PUCCH transmission in a PUSCH transmission of a same priority index, if a PUCCH transmission with HARQ-ACK information of a first priority index overlaps with one or more PUSCH transmissions of a second priority index that is different than the first priority index +- if // this is for cases the UE supports multiplexing information of different priorities in a PUCCH/PUSCH transmission + - a PUCCH transmission with HARQ-ACK information, without repetitions, with smaller priority index overlaps with a PUCCH transmission only with HARQ-ACK information, without repetitions, with larger priority index, or + - a PUCCH transmission without repetitions that includes HARQ-ACK information of smaller priority index overlaps with a PUCCH transmission without repetitions using a PUCCH resource with PUCCH format 2/3/4 with HARQ-ACK information and SR of larger priority index, or + - a PUCCH transmission with HARQ-ACK information, without repetitions, with smaller or larger priority index overlaps, respectively, with a PUSCH transmission with larger or smaller priority index + +the UE + +- multiplexes HARQ-ACK information of different priority indexes and SR information of larger priority index, if any, in a same PUCCH transmission of larger priority index, or multiplexes HARQ-ACK information the UE would provide in a PUCCH transmission of smaller or larger priority index in a PUSCH transmission of larger or smaller priority index, respectively, and applies the procedures in clause 9.2.5.3 or 9.3, respectively, and +- drops CSI and/or SR carried in the PUCCH transmission of smaller priority index, if any +- drops negative SR carried in the PUCCH transmission of larger priority index, if any, if the UE would multiplex the HARQ-ACK information of larger priority index in a PUSCH transmission of smaller priority index +- drops HARQ-ACK information of smaller priority index if the UE would multiplex the HARQ-ACK information of smaller priority index in a PUSCH transmission where the UE multiplexes Part 1 CSI reports and Part 2 CSI reports of larger priority index +- drops Part 2 CSI reports of smaller priority index if the UE would multiplex the HARQ-ACK information of smaller and larger priority indexes in a PUSCH transmission where the UE multiplexes Part 1 CSI reports and Part 2 CSI reports of smaller priority index +- drops HARQ-ACK information of smaller priority index if the UE would multiplex the HARQ-ACK information of smaller priority index in a PUCCH transmission of larger priority index using a PUCCH resource provided by $n_{PUCCH-AN}$ + +- drops Part 2 CSI reports of smaller priority index if the UE would multiplex the HARQ-ACK information of larger priority index in a PUSCH transmission where the UE multiplexes CG-UCI, or UTO-UCI, Part 1 CSI reports and Part 2 CSI reports of smaller priority index +- else + - if the UE would transmit the following channels that would overlap in time where, if a channel transmission is with repetitions, the following are applicable per repetition + - a first PUCCH transmission of larger priority index and a second PUCCH transmission of smaller priority index + - a first PUCCH transmission of larger priority index and a second PUSCH transmission of smaller priority index when the UE cannot simultaneously transmit the first PUCCH and second PUSCH + - a first PUCCH transmission of smaller priority index and a second PUSCH transmission of larger priority index when the UE cannot simultaneously transmit the first PUCCH and second PUSCH + - the UE + - transmits the PUCCH or the PUSCH of the larger priority index subject to the limitations for UE transmissions described in clauses 11.1, 11.1.1, 11.2A, and 15 and + - does not transmit a PUCCH or a PUSCH of smaller priority index + +When a UE determines overlapping for PUCCH and/or PUSCH transmissions of different priority indexes, other than PUCCH transmissions with SL HARQ-ACK reports, before considering limitations for transmissions including with repetitions, if any, due to cell DRX operation or as described in clauses 11.1, 11.1.1, 11.2A, 15 and 17.2, if the UE is not provided *uci-MuxWithDiffPrio*, the UE first resolves overlapping for PUCCH and/or PUSCH transmissions of smaller priority index as described in clauses 9.2.5 and 9.2.6. Then, + +- if a transmission of a first PUCCH of larger priority index scheduled by a DCI format in a PDCCH reception would overlap in time with a repetition of a transmission of a second PUSCH or a second PUCCH of smaller priority index, the UE cancels the repetition of a transmission of the second PUSCH or the second PUCCH before the first symbol that would overlap with the first PUCCH transmission +- if a transmission of a first PUSCH of larger priority index scheduled by a DCI format in a PDCCH reception would overlap in time with a repetition of the transmission of a second PUCCH of smaller priority index, the UE cancels the repetition of the transmission of the second PUCCH before the first symbol that would overlap with the first PUSCH transmission + +where + +- the overlapping is applicable before or after resolving overlapping among channels of larger priority index, if any, as described in clauses 9.2.5 and 9.2.6 +- any remaining PUCCH and/or PUSCH transmission after overlapping resolution is subjected to the limitations for UE transmission due to cell DRX operation or as described in clauses 11.1, 11.1.1, 11.2A, 15 and 17.2 +- the UE expects that the transmission of the first PUCCH or the first PUSCH, respectively, would not start before after a last symbol of the corresponding PDCCH reception +- is the PUSCH preparation time for a corresponding UE processing capability assuming [6, TS 38.214], based on and as subsequently defined in this clause, and is determined by a reported UE capability + +If a UE is scheduled by a DCI format in a first PDCCH reception to transmit a first PUCCH or a first PUSCH of larger priority index that overlaps with a second PUCCH or a second PUSCH transmission of smaller priority index that, if any, is scheduled by a DCI format in a second PDCCH + +- is based on a value of corresponding to the smallest SCS configuration of the first PDCCH, the second PDCCHs, the first PUCCH or the first PUSCH, and the second PUCCHs or the second PUSCHs +- if the overlapping group includes the first PUCCH + - if *processingType2Enabled* of *PDSCH-ServingCellConfig* is set to *enable* for the serving cell where the UE receives the first PDCCH and for all serving cells where the UE receives the PDSCHs + +corresponding to the second PUCCHs, and if *processingType2Enabled* of *PUSCH-ServingCellConfig* is set to *enable* for the serving cells with the second PUSCHs, is 5 for , 5.5 for and 11 for + +- else, is 10 for , 12 for , 23 for , 36 for , 144 for , and 288 for ; +- if the overlapping group includes the first PUSCH + - if *processingType2Enabled* of *PUSCH-ServingCellConfig* is set to *enable* for the serving cells with the first PUSCH and the second PUSCHs and if *processingType2Enabled* of *PDSCH-ServingCellConfig* is set to *enable* for all serving cells where the UE receives the PDSCHs corresponding to the second PUCCHs, is 5 for , 5.5 for and 11 for + - else, is 10 for , 12 for , 23 for , 36 for , 144 for , and 288 for ; + +If a PUSCH of larger priority index scheduled by a DCI format overlaps in time with a PUSCH of smaller priority index with SP-CSI report(s) without a corresponding PDCCH in one or more symbols on the same carrier, and if the earliest symbol of these PUSCH channels starts no earlier than $N_2+d_{2,1}$ symbols after the last symbol of the DCI scheduling the PUSCH of larger priority index where $d_{2,1}$ is the maximum of the $d_{2,1}$ associated with PUSCH of larger priority index scheduled by a DCI format and the PUSCH of smaller priority index with SP-CSI report(s) without a corresponding PDCCH, the PUSCH of smaller priority index with SP-CSI report(s) shall not be transmitted by the UE. Otherwise, if the timeline requirement is not satisfied this is an error case. + +If a UE would transmit the following channels, including repetitions if any, that would overlap in time + +- a first PUCCH of larger priority index with SR and a second PUCCH or PUSCH of smaller priority index, or +- a configured grant PUSCH of larger priority index and a PUCCH of smaller priority index, or +- a first PUCCH of larger priority index with HARQ-ACK information only in response to PDSCH(s) reception without corresponding PDCCH(s) and a second PUCCH of smaller priority index with HARQ-ACK information only in response to PDSCH(s) reception without corresponding PDCCH(s), or a second PUCCH of smaller priority index with SR and/or CSI, or a configured grant PUSCH with smaller priority index, or a PUSCH of smaller priority index with SP-CSI report(s) without a corresponding PDCCH, or +- a PUSCH of larger priority index with SP-CSI report(s) without a corresponding PDCCH and a PUCCH of smaller priority index with SR, or CSI, or HARQ-ACK information only in response to PDSCH(s) reception without corresponding PDCCH(s), or +- a configured grant PUSCH of larger priority index and a configured grant PUSCH of smaller priority index or a PUSCH of smaller priority index with SP-CSI report(s) without a corresponding PDCCH on a same serving cell +- a PUSCH of larger priority index with SP-CSI report(s) without a corresponding PDCCH and a configured grant PUSCH of smaller priority index or a PUSCH of smaller priority index with SP-CSI report(s) without a corresponding PDCCH on a same serving cell +- a PUSCH of smaller priority index scheduled by a DCI format and a configured grant PUSCH of larger priority index on a same serving cell if the UE is provided *prioLowDG-HighCG* +- a PUSCH of larger priority index scheduled by a DCI format and a configured grant PUSCH of smaller priority index on a same serving cell if the UE is provided *prioHighDG-LowCG* + +the UE is expected to cancel a repetition of the PUCCH/PUSCH transmissions of smaller priority index before the first symbol overlapping with the PUCCH/PUSCH transmission of larger priority index if the repetition of the PUCCH/PUSCH transmissions of smaller priority index overlaps in time with the PUCCH/PUSCH transmissions of larger priority index. In case of a PUSCH of larger priority index scheduled by a DCI format in a PDCCH reception and a configured grant PUSCH of smaller priority index on a same serving cell and the UE is provided *prioHighDG-LowCG* + +- the UE expects that the transmission of the PUSCH of larger priority index would not start before after a last symbol of the corresponding PDCCH reception +- is the PUSCH preparation time for a corresponding UE processing capability assuming [6, TS 38.214], based on and as subsequently defined in this clause, and and are determined by a reported UE capability + +When a UE determines overlapping for PUCCH transmissions with SL HARQ-ACK reports and PUSCH of smaller priority index, including repetitions if any, after resolving the overlapping PUCCH other than PUCCH transmissions with SL HARQ-ACK reports and/or PUSCH transmissions, if the PUSCH includes no UCI, the UE resolves the overlapping for PUCCH transmissions with SL HARQ-ACK reports and PUSCH of smaller priority index as described in clauses 9.2.5 and 9.2.6. + +When a UE determines overlapping for PUCCH transmissions with SL HARQ-ACK reports and PUSCH of larger priority index only, including repetitions if any, after resolving the overlapping PUCCH other than PUCCH transmissions with SL HARQ-ACK reports and/or PUSCH transmissions, the UE does not transmit the PUCCH with SL HARQ-ACK reports + +where + +- the UE expects that the transmission of the PUSCH would not start before after a last symbol of the corresponding PDCCH reception; +- is the PUSCH preparation time for a corresponding UE processing capability assuming [6, TS 38.214], based on and as subsequently defined in this clause, and is determined by a reported UE capability. + +The UE expects the PUCCH and PUSCH transmissions to fulfill the conditions in clause 9 and clause 9.2.5 for UCI multiplexing replacing the reference time of "end of PDSCH" with "end of the last symbol of a last PSFCH reception occasion" as described in 16.5 and $T_{proc,1}$ with $T_{prep}$ . + +A UE does not expect that a PUCCH carrying SL HARQ-ACK reports overlaps with PUSCH with aperiodic or semi-persistent CSI reports. + +A UE does not expect to be scheduled to transmit a PUCCH or a PUSCH with smaller priority index that would overlap in time with a PUCCH of larger priority index with HARQ-ACK information only in response to a PDSCH reception without a corresponding PDCCH unless the UE is provided *uci-MuxWithDiffPrio*. A UE does not expect to be scheduled to transmit a PUCCH of smaller priority index that would overlap in time with a PUSCH of larger priority index with SP-CSI report(s) without a corresponding PDCCH unless the UE is provided *uci-MuxWithDiffPrio*. + +In the remaining of this clause, a UE multiplexes UCIs with same priority index in a PUCCH or a PUSCH before considering limitations for UE transmission due to cell DRX operation or as described in clauses 11.1, 11.1.1, 11.2A, 15 and 17.2. A PUCCH or a PUSCH is assumed to have a same priority index as a priority index of UCIs a UE multiplexes in the PUCCH or the PUSCH. + +In the remaining of this clause, the multiplexing or prioritization for overlapping channels are for overlapping channels with same priority index or for overlapping channels with a PUCCH carrying SL HARQ-ACK information unless stated otherwise. + +In the remaining of this clause, if a UE is provided *subslotLengthForPUCCH* for a cell for PUCCH transmission, a slot for an associated PUCCH resource of a PUCCH transmission with HARQ-ACK information on the cell includes a number of symbols indicated by *subslotLengthForPUCCH*, unless stated otherwise. + +If a UE would transmit on a serving cell a PUSCH without UL-SCH that overlaps with a PUCCH transmission on a serving cell that includes positive SR information, the UE does not transmit the PUSCH. + +If a UE would transmit CSI reports on overlapping physical channels, the UE applies the priority rules described in [6, TS 38.214] for the multiplexing of CSI reports. + +If a UE + +- would multiplex UCI in a PUCCH transmission that overlaps with a PUSCH transmission, and +- the PUSCH and PUCCH transmissions fulfil the conditions in clause 9.2.5 for UCI multiplexing, + +the UE + +- multiplexes only HARQ-ACK information, if any, from the UCI in the PUSCH transmission and does not transmit the PUCCH if the UE multiplexes aperiodic or semi-persistent CSI reports in the PUSCH; + +- multiplexes only HARQ-ACK information and CSI reports, if any, from the UCI in the PUSCH transmission and does not transmit the PUCCH if the UE does not multiplex aperiodic or semi-persistent CSI reports in the PUSCH. + +A UE does not expect to multiplex in a PUSCH transmission in one slot with SCS configuration UCI of same type that the UE would transmit in PUCCHs in different slots with SCS configuration if . + +A UE does not expect to multiplex in a PUSCH transmission or in a PUCCH transmission HARQ-ACK information that the UE would transmit in different PUCCHs of a same priority index. + +A UE does not expect a PUCCH resource that results from multiplexing overlapped PUCCH resources, if applicable, to overlap with more than one PUSCHs if each of the more than one PUSCHs includes aperiodic CSI reports. + +A UE does not expect to detect a DCI format scheduling a PDSCH reception or having associated HARQ-ACK information report without scheduling a PDSCH reception, and indicating a resource for a PUCCH transmission with corresponding HARQ-ACK information in a slot if the UE previously detects a DCI format scheduling a PUSCH transmission in the slot and if the UE multiplexes HARQ-ACK information in the PUSCH transmission. + +If a UE multiplexes aperiodic CSI in a PUSCH and the UE would multiplex UCI that includes HARQ-ACK information in a PUCCH that overlaps with the PUSCH and the timing conditions for overlapping PUCCHs and PUSCHs in clause 9.2.5 are fulfilled, the UE multiplexes only the HARQ-ACK information in the PUSCH and does not transmit the PUCCH. + +When a UE transmits multiple PUSCHs on respective serving cells in a slot with reference to slots for PUCCH transmissions and the multiple PUSCHs overlap with a PUCCH carrying UCI in the slot, the UE selects all the PUSCHs overlapping with the PUCCH as the candidate PUSCHs for UCI multiplexing within the slot. + +If a UE would transmit a single PUSCH scheduled by a DCI format that includes a DAI field on a serving cell in a slot with reference to slots for PUCCH transmissions without any other PUSCH that would be transmitted on any serving cell in the slot and the UE does not determine any PUCCH carrying HARQ-ACK information in the slot, or if the UE indicates the corresponding capability *mux-HARQ-ACK-withoutPUCCH-onPUSCH* and the UE transmits multiple PUSCHs on respective serving cells in a slot with reference to slots for PUCCH transmissions and the UE does not determine any PUCCH carrying HARQ-ACK information in the slot and at least one of the multiple PUSCHs is scheduled by a DCI format that includes a DAI field, the UE selects the single PUSCH or all the multiple PUSCHs in the slot as the candidate PUSCHs for HARQ-ACK multiplexing within the slot except for any PUSCH among the multiple PUSCHs that is scheduled by a DCI format that includes a DAI field that is equal to 4 in case the UE is configured with *pdsch-HARQ-ACK-Codebook = dynamic* or with *pdsch-HARQ-ACK-Codebook-r16*, or is equal to 0 in case the UE is configured with *pdsch-HARQ-ACK-Codebook = semi-static*. + +The UE determines the PUSCH for UCI multiplexing by applying the following procedure on the candidate PUSCHs as described in this clause: + +- If the UE is provided *enableSTx2PofmDCI*, is provided *ackNackFeedbackMode = separate*, and would multiplex UCI that includes HARQ-ACK information in a PUSCH, candidate PUSCHs for the UCI multiplexing are the ones associated with same *coresetPoolIndex* value as for a PUCCH transmission with the HARQ-ACK information. +- If the candidate PUSCHs that include first PUSCHs that are scheduled by DCI formats and second PUSCHs configured by respective *ConfiguredGrantConfig* or *semiPersistentOnPUSCH*, and the UE would multiplex UCI in one of the candidate PUSCHs, and the candidate PUSCHs fulfil the conditions in clause 9.2.5 for UCI multiplexing, the UE multiplexes the UCI in a PUSCH from the first PUSCHs. +- If the UE would multiplex UCI in one of the candidate PUSCHs and the UE does not multiplex aperiodic CSI in any of the candidate PUSCHs, the UE multiplexes the UCI in a PUSCH of the serving cell with the smallest *ServCellIndex* subject to the conditions in clause 9.2.5 for UCI multiplexing being fulfilled. If the UE transmits more than one PUSCHs in the slot on the serving cell with the smallest *ServCellIndex* that fulfil the conditions in clause 9.2.5 for UCI multiplexing, the UE multiplexes the UCI in the earliest PUSCH that the UE transmits in the slot. If the UE is provided *enableSTx2PofmDCI*, is provided *ackNackFeedbackMode = joint* or the UCI does not include HARQ-ACK information, and the UE would transmit two PUSCHs in the slot that start at a same symbol on the serving cell with smallest *ServCellIndex* and fulfil the conditions in clause 9.2.5 for UCI multiplexing, the UE multiplexes the UCI in the PUSCH from the two PUSCHs associated with CORESETs that the UE is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with a value of 0. + +If a UE transmits a PUSCH over one or more slots or multiple PUSCHs over one or more slots that are scheduled by a DCI format, and the UE would transmit a PUCCH with HARQ-ACK and/or CSI information over a single slot that overlaps with the PUSCH transmission in the one or more slots, and the PUSCH transmission in the one or more slots fulfills the conditions in clause 9.2.5 for multiplexing the HARQ-ACK and/or CSI information, the UE multiplexes the HARQ-ACK and/or CSI information in the PUSCH transmission in the one or more slots. The UE does not multiplex HARQ-ACK and/or CSI information in the PUSCH transmission in a slot from the one or more slots if the UE would not transmit a single-slot PUCCH with HARQ-ACK and/or CSI information in the slot in case the PUSCH transmission was absent. + +If a UE transmits a PUSCH with repetition Type B and the UE would transmit a PUCCH with HARQ-ACK and/or CSI information over a single slot that overlaps with the PUSCH transmission in one or more slots, the UE expects all actual repetitions of the PUSCH transmission [6, TS 38.214] that would overlap with the PUCCH transmission to fulfill the conditions in clause 9.2.5 for multiplexing the HARQ-ACK and/or CSI information, and the UE multiplexes the HARQ-ACK and/or CSI information in the earliest actual PUSCH repetition of the PUSCH transmission that would overlap with the PUCCH transmission and includes more than one symbol. The UE does not expect that all actual repetitions that would overlap with the PUCCH transmission do not include more than one symbol. + +If the PUSCH transmission over the one or more slots is scheduled by a DCI format that includes a DAI field, or if the multiple PUSCH transmissions over the one or more slots are scheduled by a DCI format that includes a DAI field, the value of the DAI field is applicable for multiplexing HARQ-ACK information in any PUSCH transmission in any slot from the one or more slots where the UE multiplexes HARQ-ACK information. + +When a UE would multiplex HARQ-ACK information in a PUSCH transmission that is configured by a *ConfiguredGrantConfig*, and includes CG-UCI [5, TS 38.212], the UE multiplexes the HARQ-ACK information in the PUSCH transmission if the UE is provided *cgi-UCI-Multiplexing*; otherwise, if the HARQ-ACK information and the PUSCH have same priority index, the UE does not transmit the PUSCH and multiplexes the HARQ-ACK information in a PUCCH transmission or in another PUSCH transmission; if the HARQ-ACK information and the PUSCH have different priority indexes, the UE does not transmit the channel with the smaller priority index. + +In the following, DCI formats with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI are also referred to as unicast DCI formats and DCI formats with CRC scrambled by multicast-MCCH-RNTI, G-RNTI for multicast or G-CS-RNTI are also referred to as multicast DCI formats. Corresponding unicast DCI formats are DCI formats 0\_0/0\_1/0\_2/1\_0/1\_1/1\_2 and multicast DCI formats are DCI formats 4\_0/4\_1/4\_2 [4, TS 38.212]. PDSCH receptions scheduled by unicast or multicast DCI formats are referred as unicast or multicast PDSCH receptions. HARQ-ACK information associated with unicast or multicast DCI formats for PDCCH receptions in RRC\_CONNECTED state are also respectively referred as unicast or multicast HARQ-ACK information. + +For the remaining of this clause, if a UE is provided by *cellSpecificKoffset* or by a MAC CE command, reference to a slot for a PUCCH transmission or PUSCH transmission corresponds to a slot for the PUSCH or the PUCCH transmission, and reference to a slot corresponds to slot $\kappa$ , where $\kappa$ is the SCS configuration for the PUCCH transmission or PUSCH transmission, is defined in clause 4.2, and in FR1. If *cellSpecificKoffset* or if the MAC CE command is not provided, $\kappa$ , respectively. If the PUCCH or PUSCH transmission is scheduled by a DCI format, or if SRS transmission is triggered by a DCI format, the value of $\kappa$ is the one that is applicable at the slot overlapping with the last symbol of the PDCCH reception providing the DCI format. If the PUCCH transmission or the PUSCH transmission is scheduled by a DCI format with CRC scrambled by TC-RNTI, $\kappa$ . If the UE is provided a value by a MAC CE command, the UE applies the MAC CE command in the first slot that is after slot $\kappa$ where $\kappa$ is the slot where the UE would transmit a PUCCH with HARQ-ACK information for the PDSCH providing the MAC CE command, $\kappa$ is the SCS configuration for the PUCCH transmission that is determined in the slot when the MAC CE command is applied. + +## 9.A PUCCH cell switching + +This clause is applicable when a UE is provided a PUCCH-sSCell by *pucch-sSCell* and the PUCCH-sSCell is activated and does not have a dormant UL/DL active BWP. This clause is not applicable for slots with symbols [4, TS 38.211] of a reference SCS configuration provided by *tdd-UL-DL-ConfigurationCommon* for the PCell where the UE would transmit a PUCCH with repetitions of any priority, starting from the slot following the slot indicated to the UE as described in clause 9.2.3 for HARQ-ACK reporting, or following the slot determined as described in clause 9.2.4 for SR reporting, or in clause 5.2.1.4 of [6, TS 38.214] for CSI reporting, until the slot of the last repetition of the PUCCH transmission, as described in clause 9.2.6 if the UE is provided *PUCCH-sSCellPattern*. + +A UE can be provided a periodic cell switching pattern for PUCCH transmissions by *pucch-sSCellPattern*. Each bit of the pattern corresponds to a slot with symbols [4, TS 38.211] for a reference SCS configuration provided by *tdd-UL-DL-ConfigurationCommon* for the PCell with a value of '0' or a value of '1' indicating, respectively, the PCell or the + +PUCCH-sSCell as the cell for PUCCH transmissions during the slot with symbols of the reference SCS configuration. The UE does not transmit a PUCCH in a slot on a cell if the pattern indicates a different cell for PUCCH transmission during the slot. A slot on the active UL BWP of the PUCCH-sSCell does not overlap with more than one slot on the active UL BWP of the PCell. If a slot for the active UL BWP of the PCell overlaps with more than one slot on the active BWP of the PUCCH-sSCell and the UE would transmit a PUCCH on the PUCCH-sSCell, the UE considers the first of the overlapping slots for the PUCCH transmission on the PUCCH-sSCell. + +If a UE is provided *pucch-sSCellDyn* or *pucch-sSCellDynDCI-1-2* or *pucch-sSCellDynDCI-1-3*, a corresponding DCI format associated with generation of HARQ-ACK information by the UE can include a PUCCH cell indicator field [5, TS 38.212] with a value of '0' or a value of '1' indicating, respectively, whether a PUCCH transmission with the HARQ-ACK information by the UE is on the PCell or on the PUCCH-sSCell. When the UE transmits a PUCCH with HARQ-ACK information that is associated only with SPS PDSCH receptions, the UE transmits the PUCCH on the PCell. The UE does not expect the PUCCH cell indicator field to indicate the PUCCH-sSCell for a PUCCH transmission in a slot that overlaps with a slot on the PCell where the UE would transmit another PUCCH of same or different priority index. + +A UE transmits a PUCCH on a PUCCH-sSCell with a power that the UE determines as described in clause 7.2.1, where the UE applies + +- a *p0-PUCCH-Value* from *pucch-PowerControl* in *PUCCH-Config* for the PUCCH-sSCell for the determination of +- a *pucch-PathlossReferenceRS-Id* from *pucch-PowerControl* in *PUCCH-Config* for the PUCCH-sSCell for the determination of +- a PUCCH power control adjustment state for active UL BWP of the UL carrier of PUCCH-sSCell and PUCCH transmission occasion where is a TPC command value included in a DCI format associated with generation of HARQ-ACK information for multiplexing in a PUCCH transmission on the PUCCH-sSCell as indicated either by a *pucch-sSCellPattern* or by a PUCCH cell indicator field in the DCI format, or provided by DCI format 2\_2 with CRC scrambled by TPC-PUCCH-RNTI for the PUCCH-sSCell as described in clause 11.3 + +## 9.1 HARQ-ACK codebook determination + +If a UE is provided *pdsch-HARQ-ACK-CodebookList*, the UE can be indicated by *pdsch-HARQ-ACK-CodebookList* to generate one or two HARQ-ACK codebooks. If the UE is indicated to generate one HARQ-ACK codebook, the HARQ-ACK codebook is associated with a PUCCH of priority index 0. If a UE is provided *pdsch-HARQ-ACK-CodebookList*, the UE multiplexes in a same HARQ-ACK codebook only HARQ-ACK information associated with a same priority index. If the UE is indicated to generate two HARQ-ACK codebooks + +- a first HARQ-ACK codebook is associated with a PUCCH of priority index 0 and a second HARQ-ACK codebook is associated with a PUCCH of priority index 1 +- the UE is provided first and second for each of $\{PUCCH-Config, UCI-OnPUSCH, PDSCH-CodeBlockGroupTransmission\}$ by $\{PUCCH-ConfigurationList, UCI-OnPUSCH-ListDCI-0-1, PDSCH-CodeBlockGroupTransmissionList\}$ or $\{PUCCH-ConfigurationList, UCI-OnPUSCH-ListDCI-0-2, PDSCH-CodeBlockGroupTransmissionList\}$ , respectively, for use with the first and second HARQ-ACK codebooks, respectively + +If a UE receives a PDSCH without receiving a corresponding PDCCH, or if the UE receives a PDCCH indicating a SPS PDSCH release, the UE generates one corresponding HARQ-ACK information bit. If the UE generates two HARQ-ACK codebooks, the UE is indicated by *harq-CodebookID*, per SPS PDSCH configuration, a HARQ-ACK codebook index for multiplexing the corresponding HARQ-ACK information bit. + +If a UE is provided *pdsch-HARQ-ACK-OneShotFeedback* and the UE detects a DCI format in any PDCCH monitoring occasion that includes a One-shot HARQ-ACK request field with value 1 + +- the UE includes the HARQ-ACK information in a Type-3 HARQ-ACK codebook, as described in clause 9.1.4 +- the UE does not expect that the PDSCH-to-HARQ\_feedback timing indicator field of the DCI format provides an inapplicable value from *dl-DataToUL-ACK-r16* or *dl-DataToUL-ACK-r17* + +In the remaining of this clause, reference is to one HARQ-ACK codebook and to DCI formats that schedule PDSCH reception, or have associated HARQ-ACK information without scheduling a PDSCH reception and are associated with the HARQ-ACK codebook. + +If a UE is required to receive SPS PDSCHs in a slot according to Clause 5.1 of [6] and Clause 11.1 for SPS configurations that are indicated to be released by a DCI format, the UE is not expected to receive the DCI format in the slot if the end of the last symbol of the PDCCH reception is after the end of a last symbol of any of the SPS PDSCH receptions. For a SPS configuration subject to *pdsch-AggregationFactor* or *pdsch-AggregationFactor-r16*, the UE is not expected to receive the DCI format in a slot containing a SPS PDSCH transmission occasion other than the first transmission occasion required to be received by the UE for a TB. + +If a UE is configured to receive SPS PDSCHs in a slot for SPS configurations that are indicated to be released by a DCI format, and if the UE receives the PDCCH providing the DCI format in the slot, and if HARQ-ACK information for the SPS PDSCH release and the SPS PDSCH receptions would be multiplexed in a same PUCCH, the UE does not expect to receive the SPS PDSCHs, does not generate HARQ-ACK information for the SPS PDSCH receptions, and generates a HARQ-ACK information bit for the SPS PDSCH release. + +If a UE is configured to receive SPS PDSCH(s) in a slot for SPS configuration(s), the UE does not expect to receive a PDCCH providing a DCI format in the slot to indicate SPS PDSCH release of these SPS configuration(s), if HARQ-ACK information for the SPS PDSCH release and the SPS PDSCH reception(s) would map to different PUCCHs. + +If a UE detects a DCI format 1\_1 or a DCI format 1\_3 indicating + +- SCell dormancy without scheduling a PDSCH reception, as described in clause 10.3, and +- is provided *pdsch-HARQ-ACK-Codebook = dynamic* or *pdsch-HARQ-ACK-Codebook-r16* + +the UE generates a HARQ-ACK information bit as described in clause 9.1.3 for a DCI format 1\_1 or a DCI format 1\_3 indicating SCell dormancy without scheduling a PDSCH reception and the HARQ-ACK information bit value is ACK. + +If a UE is not provided *PDSCH-CodeBlockGroupTransmission*, the UE generates one HARQ-ACK information bit per transport block. + +For a HARQ-ACK information bit, a UE generates a positive acknowledgement (ACK) if the UE detects a DCI format that provides a SPS PDSCH release or detects a DCI format that does not schedule PDSCH reception and indicates a TCI state update or correctly decodes a transport block, and generates a negative acknowledgement (NACK) if the UE does not correctly decode the transport block. A HARQ-ACK information bit value of 0 represents a NACK while a HARQ-ACK information bit value of 1 represents an ACK. + +In the following, the CRC for a DCI format is scrambled with a C-RNTI, an MCS-C-RNTI, or a CS-RNTI, or a G-RNTI for multicast, or a G-CS-RNTI. + +In the following, if the value of *maxNrofCodeWordsScheduledByDCI* is not provided, the value of *maxNrofCodeWordsScheduledByDCI* equals one. + +### 9.1.1 CBG-based HARQ-ACK codebook determination + +If a UE is provided *PDSCH-CodeBlockGroupTransmission* for a serving cell, the UE receives a PDSCH scheduled by DCI format 1\_1, that includes code block groups (CBGs) of a transport block. The UE is also provided *maxCodeBlockGroupsPerTransportBlock* indicating a maximum number of CBGs for generating respective HARQ-ACK information bits for a transport block reception for the serving cell. + +For a number of code blocks (CBs) in a transport block, the UE determines a number of CBGs according to clause 5.1.7.1 of [6, TS 38.214] and determines a number of HARQ-ACK bits for the transport block as . + +The UE generates an ACK for the HARQ-ACK information bit of a CBG if the UE correctly received all code blocks of the CBG and generates a NACK for the HARQ-ACK information bit of a CBG if the UE incorrectly received at least one code block of the CBG. If the UE receives two transport blocks, the UE concatenates the HARQ-ACK information bits for CBGs of the second transport block after the HARQ-ACK information bits for CBGs of the first transport block. + +The HARQ-ACK codebook includes the HARQ-ACK information bits in ascending order of CBG index and, if for a transport block, the UE generates a NACK value for the last HARQ-ACK information bits for the transport block in the HARQ-ACK codebook. + +If the UE generates a HARQ-ACK codebook in response to a retransmission of a transport block, corresponding to a same HARQ process as a previous transmission of the transport block, the UE generates an ACK for each CBG that the UE correctly decoded in a previous transmission of the transport block. + +If a UE correctly detects each of the CBGs and does not correctly detect the transport block for the CBGs, the UE generates a NACK value for each of the CBGs. + +### 9.1.2 Type-1 HARQ-ACK codebook determination + +This clause applies if the UE is configured with *pdsch-HARQ-ACK-Codebook = semi-static*. In clauses 9.1.2, 9.1.2.1, and 9.1.2.2, if the UE is configured with *pdsch-HARQ-ACK-Codebook = semi-static* for only one of unicast or multicast HARQ-ACK codebook, the Type-1 HARQ-ACK codebook is generated considering only one of respective unicast or multicast configurations for PDSCH receptions or for PDCCH monitoring for detection of DCI formats. + +A UE does not provide a Type-1 HARQ-ACK codebook if the Type-1 HARQ-ACK codebook would include only HARQ-ACK information for transport blocks associated with HARQ processes with disabled HARQ-ACK information. + +If a UE is provided *downlinkHARQ-FeedbackDisabled* indicating disabled HARQ-ACK information for a HARQ process associated with a transport block in PDSCH reception occasion on serving cell, the UE reports a NACK value for a HARQ-ACK information bit corresponding to the transport block in a Type-1 HARQ-ACK codebook and does not consider the transport block as received in the determination of in clause 9.1.2.1. If the UE is also provided *PDSCH-CodeBlockGroupTransmission*, the UE reports NACK values for HARQ-ACK information bits corresponding to CBGs of the transport block in the Type-1 HARQ-ACK codebook and does not consider the CBGs as received in the determination of in clause 9.1.2.1. If the UE is also provided *harq-feedbackEnablingforSPSactive = 'enabled'*, the UE considers a HARQ process associated with a transport block in a first SPS PDSCH reception, after an activation of SPS PDSCH receptions, to have enabled HARQ-ACK information and the UE provides a HARQ-ACK information bit according to a decoding outcome for the transport block in the first SPS PDSCH reception. + +If a UE reports HARQ-ACK information associated with a G-RNTI for multicast or a G-CS-RNTI with disabled HARQ-ACK information, as described in clause 18, a value of the HARQ-ACK information is a UE implementation choice. + +A UE reports HARQ-ACK information for a corresponding PDSCH reception or SPS PDSCH release or TCI state update only in a HARQ-ACK codebook that the UE transmits in a slot indicated by a value of a PDSCH-to-HARQ\_feedback timing indicator field in a corresponding DCI format or provided by *dl-DataToUL-ACK* or *dl-DataToUL-ACK-r16* or *dl-DataToUL-ACK-DCI-1-2* or *dl-DataToUL-ACK-r17* or *dl-DataToUL-ACK-DCI-1-2-r17* if the PDSCH-to-HARQ\_feedback timing indicator field is not present in the DCI format as described in clause 9.2.3. The UE reports NACK value(s) for HARQ-ACK information bit(s) in a HARQ-ACK codebook that the UE transmits in a slot not indicated by a value of a PDSCH-to-HARQ\_feedback timing indicator field in a corresponding DCI format. + +If a UE is not provided *pdsch-HARQ-ACK-OneShotFeedback*, the UE does not expect to receive a PDSCH scheduled by a DCI format that the UE detects in any PDCCH monitoring occasion and includes a PDSCH-to-HARQ\_feedback timing indicator field providing an inapplicable value from *dl-DataToUL-ACK-r16* or *dl-DataToUL-ACK-r17*. + +If the UE is provided *pdsch-AggregationFactor-r16* in *SPS-Config*, or *pdsch-AggregationFactor* in *PDSCH-Config* and no entry in *pdsch-TimeDomainAllocationList* and *pdsch-TimeDomainAllocationListDCI-1-2* includes *repetitionNumber* in *PDSCH-TimeDomainResourceAllocation-r16*, is a maximum value of *pdsch-AggregationFactor-r16* in *SPS-Config*, or *pdsch-AggregationFactor* in *PDSCH-Config*; otherwise. The UE reports HARQ-ACK information for a PDSCH reception + +- from DL slot to DL slot, if is provided by *pdsch-AggregationFactor* or *pdsch-AggregationFactor-r16* [6, TS 38.214], or +- from DL slot to DL slot, if the time domain resource assignment field in the DCI format scheduling the PDSCH reception indicates an entry containing *repetitionNumber*, or +- in DL slot, otherwise + +only in a HARQ-ACK codebook that the UE includes in a PUCCH or PUSCH transmission in slot, where is + +- an UL slot overlapping with the end of the PDSCH reception in DL slot if the UE is provided *subslotLengthForPUCCH* for the HARQ-ACK codebook +- the UL slot is on the primary cell if the UE is provided *pucch-sSCellPattern*; otherwise, the UL slot is on the serving cell of the PUCCH transmission + +- the last UL slot for PUCCH transmission overlapping with DL slot if the UE is not provided *subslotLengthForPUCCH* for the HARQ-ACK codebook +- the last UL slot is on the primary cell if the UE is provided *pucch-sSCellPattern*; otherwise, the last UL slot is on the serving cell of the PUCCH transmission + +and is a number of slots indicated by the PDSCH-to-HARQ\_feedback timing indicator field in a corresponding DCI format, or provided by *dl-DataToUL-ACK* or *dl-DataToUL-ACK-r16* or *dl-DataToUL-ACK-DCI-1-2* or *dl-DataToUL-ACK-r17* or *dl-DataToUL-ACK-DCI-1-2-r17* if the PDSCH-to-HARQ\_feedback timing indicator field is not present in the DCI format. If the UE reports HARQ-ACK information for the PDSCH reception in a slot other than slot , the UE sets a value for each corresponding HARQ-ACK information bit to NACK. + +If a UE reports HARQ-ACK information in a PUCCH only for + +- a SPS PDSCH release indicated by DCI format 1\_0 or by DCI format 4\_1, with counter DAI field value of 1, or +- a PDSCH reception providing a transport block with enabled HARQ-ACK information scheduled by DCI format 1\_0 or by DCI format 4\_1 having enabled associated HARQ-ACK information report as described in clause 18, with counter DAI field value of 1 on the PCell, or +- SPS PDSCH receptions associated with a CS-RNTI or with G-CS-RNTIs having enabled associated HARQ-ACK information reports as described in clause 18 + +within the occasions for candidate PDSCH receptions as determined in clause 9.1.2.1, the UE determines a HARQ-ACK codebook only for the SPS PDSCH release, or only for the PDSCH reception, or only for SPS PDSCH receptions according to corresponding occasions on respective serving cells, where the value of counter DAI in DCI format 1\_0 or in DCI format 4\_1 is according to Table 9.1.3-1 and HARQ-ACK information bits in response to more than one SPS PDSCH receptions that the UE is configured to receive are ordered according to the following pseudo-code; otherwise, the procedures in clause 9.1.2.1 and clause 9.1.2.2 for a HARQ-ACK codebook determination apply. + +In the following pseudo-code, SPS PDSCH receptions associated with a SPS PDSCH configuration are activated by a DCI format with CRC scrambled by a CS-RNTI or by a DCI format with CRC scrambled by a G-CS-RNTI. + +Set to the number of serving cells configured to the UE + +Set to the number of SPS PDSCH configurations configured to the UE for serving cell + +Set to the number of DL slots for SPS PDSCH receptions on serving cell with HARQ-ACK information multiplexed on the PUCCH + +Set – HARQ-ACK information bit index + +Set – serving cell index: lower indexes correspond to lower RRC indexes of corresponding cell + +while + +Set – SPS PDSCH configuration index: lower indexes correspond to lower RRC indexes of corresponding SPS configurations + +while + +Set – slot index + +while + +if { + +a UE is configured to receive SPS PDSCHs from slot to slot for SPS PDSCH configuration on serving cell , excluding SPS PDSCHs that are not required to be received in any slot among overlapping SPS PDSCHs, if any according to [6, TS 38.214], or based on a UE capability for a number of PDSCH receptions in a slot according to [6, TS 38.214], or due to overlapping with a set of symbols + +- indicated as uplink by *tdd-UL-DL-ConfigurationCommon* or by *tdd-UL-DL-ConfigurationDedicated*, and/or + +- determined as non-active period of cell DTX [11, TS 38.321] + +where, for unicast SPS PDSCHs, is provided by *pdsch-AggregationFactor-r16* in *SPS-Config* or, if *pdsch-AggregationFactor-r16* is not included in *SPS-Config*, by *pdsch-AggregationFactor* in *PDSCH-config* and, for multicast SPS PDSCHs, is provided by if contained in an entry indicated by the time domain resource assignment field in the DCI format scheduling the PDSCH repetition, or provided by *pdsch-AggregationFactor-r16* if included in *SPS-Config* or, otherwise, , and + +HARQ-ACK information for the SPS PDSCH is associated with the PUCCH + +} + += HARQ-ACK information bit for this SPS PDSCH reception + +; + +end if + +; + +end while + +; + +end while + +; + +end while + +#### 9.1.2.1 Type-1 HARQ-ACK codebook in physical uplink control channel + +For a serving cell , an active DL BWP, and an active UL BWP, as described in clause 12, the UE determines a set of occasions for candidate PDSCH receptions for which the UE can transmit corresponding HARQ-ACK information in a PUCCH in slot . If serving cell is deactivated, the UE uses as the active DL BWP for determining the set of occasions for candidate PDSCH receptions a DL BWP provided by *firstActiveDownlinkBWP-Id*. The determination is based: + +- on a set of slot timing values associated with the active UL BWP on the primary cell or, if the PUCCH transmission is indicated by a DCI format to be on the PUCCH-sSCell as described in clause 9A, on a set of slot timing values associated with the active UL BWP on the PUCCH-sSCell + - If the UE is configured to monitor PDCCH for DCI format 1\_0 and is not configured to monitor PDCCH for either DCI format 1\_1 or DCI format 1\_2 for serving cell , or the active DL BWP for serving cell is dormant BWP, is provided by the slot timing values {1, 2, 3, 4, 5, 6, 7, 8} for SCS configuration of PUCCH transmission , {7, 8, 12, 16, 20, 24, 28, 32} for , and {13, 16, 24, 32, 40, 48, 56, 64} for + - If the UE is configured to monitor PDCCH for DCI format 1\_1 and is not configured to monitor PDCCH for DCI format 1\_2 for serving cell , is provided by *dl-DataToUL-ACK* or *dl-DataToUL-ACK-r16* or *dl-DataToUL-ACK-r17* + - If the UE is configured to monitor PDCCH for DCI format 1\_2 and is not configured to monitor PDCCH for DCI format 1\_1 for serving cell , is provided by *dl-DataToUL-ACK-DCI-1-2* or *dl-DataToUL-ACK-DCI-1-2-r17* + - If the UE is configured to monitor PDCCH for DCI format 1\_1 and DCI format 1\_2 for serving cell , is provided by the union of *dl-DataToUL-ACK* or *dl-DataToUL-ACK-r16* or *dl-DataToUL-ACK-r17* and *dl-DataToUL-ACK-DCI-1-2* or *dl-DataToUL-ACK-DCI-1-2-r17* + - If an inapplicable value in *dl-DataToUL-ACK-r16* or *dl-DataToUL-ACK-r17* is provided, the value is excluded from + - If the UE is configured to monitor PDCCH for multicast DCI formats for serving cell + - if the UE is provided *fdmed-ReceptionMulticast* or if the UE is not provided *type1CodebookGenerationMode* = 'mode1' + +- if the UE is configured to monitor PDCCH for DCI format 4\_2, *dl-DataToUL-ACK* or *DL-DataToUL-ACK-v1700* is provided by *pucch-ConfigMulticast1/pucch-ConfigurationListMulticast1* if provided; otherwise, by *pucch-Config/pucch-ConfigurationList* + - if UE is configured to monitor PDCCH for DCI format 4\_1, for multicast, is provided by the union of *dl-DataToUL-ACK* or *DL-DataToUL-ACK-v1700* and *dl-DataToUL-ACK-MulticastDCI-Format4-1*, if provided; otherwise, by the union of *dl-DataToUL-ACK* or *DL-DataToUL-ACK-v1700* and the slot timing values {1, 2, 3, 4, 5, 6, 7, 8} for SCS configuration of PUCCH transmission + - otherwise, is provided by *dl-DataToUL-ACK* or *DL-DataToUL-ACK-v1700* + - otherwise, is provided by *dl-DataToUL-ACK-ForDCIFormat4-1* if provided; otherwise, by the slot timing values {1, 2, 3, 4, 5, 6, 7, 8} for SCS configuration of PUCCH transmission + - else, if the UE is provided *typeICodebookGenerationMode* = 'mode1', the UE + - determines a first set as , a second set as , and a third set as + - if the UE is configured to monitor PDCCH for DCI format 4\_2, *dl-DataToUL-ACK* or *DL-DataToUL-ACK-v1700* is provided by *pucch-ConfigMulticast1/pucch-ConfigurationListMulticast1* if provided; otherwise, by *pucch-Config/pucch-ConfigurationList* + - if UE is configured to monitor PDCCH for DCI format 4\_1, is provided by the union of *dl-DataToUL-ACK* or *DL-DataToUL-ACK-v1700* and *dl-DataToUL-ACK-MulticastDCI-Format4-1*, if provided; otherwise, by the union of *dl-DataToUL-ACK* or *DL-DataToUL-ACK-v1700* and the slot timing values {1, 2, 3, 4, 5, 6, 7, 8} for SCS configuration of PUCCH transmission + - otherwise, is provided by *dl-DataToUL-ACK* or *DL-DataToUL-ACK-v1700* + - otherwise, is provided by *dl-DataToUL-ACK-ForDCIFormat4-1* if provided; otherwise, by the slot timing values {1, 2, 3, 4, 5, 6, 7, 8} for SCS configuration of PUCCH transmission +- b) on a set of row indexes of a table that is associated with the active DL BWP and defining respective sets of slot offsets , start and length indicators *SLIV*, and PDSCH mapping types for PDSCH reception as described in [6, TS 38.214], where the row indexes of the table are provided by +- the union of row indexes of time domain resource allocation tables for DCI formats the UE is configured to monitor PDCCH for serving cell if the UE is not configured to monitor PDCCH for multicast DCI formats for serving cell , or is not provided *typeICodebookGenerationMode* = 'mode1' and is not provided *fdmed-ReceptionMulticast*, or, if any, for the first set + - the union of row indexes of time domain resource allocation tables for DCI format 1\_0 and/or DCI format 1\_1 and/or DCI format 1\_2 for serving cell if UE is provided *fdmed-ReceptionMulticast*, or for the second set, if any + - the union of row indexes of time domain resource allocation tables for multicast DCI formats the UE is configured to monitor PDCCH for serving cell if UE is provided *fdmed-ReceptionMulticast*, or for the third set, if any + - if the UE is provided *referenceOfSLIVDCI-1-2*, for each row index with slot offset and PDSCH mapping Type B in a set of row indexes of a table for DCI format 1\_2 [6, TS 38.214], for any PDCCH monitoring occasion in any slot where the UE monitors PDCCH for DCI format 1\_2 and with starting symbol , if for normal cyclic prefix and for extended cyclic prefix, add a new row index in the set of row indexes of the table by replacing the starting symbol of the row index by +- c) on the ratio between the downlink SCS configuration and the uplink SCS configuration provided by *subcarrierSpacing* in *BWP-Downlink* and *BWP-Uplink* for the active DL BWP and the active UL BWP, respectively +- d) if provided, on *tdd-UL-DL-ConfigurationCommon* and *tdd-UL-DL-ConfigurationDedicated* as described in clause 11.1 +- e) if *ca-SlotOffset* is provided, on and provided by *ca-SlotOffset* for serving cell , or on and provided by *ca-SlotOffset* for the primary cell, as described in [4, TS 38.211]. + +If a UE + +- is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with a value of 0 for first CORESETs on active DL BWPs of serving cells, and +- is provided *coresetPoolIndex* with a value of 1 for second CORESETs on active DL BWPs of the serving cells, and +- is provided *ackNackFeedbackMode* = *joint* + +where + +- a serving cell is placed in a first set of serving cells if the serving cell includes a first CORESET, and +- a serving cell is placed in a second set of serving cells if the serving cell includes a second CORESET, and +- serving cells are placed in a set according to an ascending order of a serving cell index + +the UE generates a Type-1 HARQ-ACK codebook for the set and the set of serving cells separately by setting and in the following pseudo-code. The UE concatenates the HARQ-ACK codebook generated for the set followed by the HARQ-ACK codebook generated for the set to obtain a total number of HARQ-ACK information bits. + +If a UE is provided *fdmed-ReceptionMulticast* and the UE is configured to monitor PDCCH for detection of unicast DCI formats and to monitor PDCCH for detection of multicast DCI formats + +- a serving cell is placed in a first set of serving cells if the UE is configured to monitor PDCCH for DCI formats 1\_0/1\_1/1\_2 for scheduling on serving cell , and +- a serving cell is placed in a second set of serving cells if the UE is configured to monitor PDCCH for detection of DCI format 4\_1/4\_2 for scheduling on serving cell , and +- serving cells are placed in a set according to an ascending order of a serving cell index + +the UE generates a Type-1 HARQ-ACK codebook for the set and the set of serving cells separately by setting and using the *maxNrofCodeWordsScheduledByDCI* provided in *PDSCH-config* for the set and setting , *maxCodeBlockGroupsPerTransportBlock* to 1, and using the *maxNrofCodeWordsScheduledByDCI* provided in *PDSCH-configMulticast* for the set in the following pseudo-code. The UE concatenates the HARQ-ACK codebook generated for the set followed by the HARQ-ACK codebook generated for the set to obtain a total number of HARQ-ACK information bits. + +If the UE is configured to monitor PDCCH for DCI formats with CRC scrambled by G-RNTI for multicast or G-CS-RNTI and is provided *type1-Codebook-Generation-Mode* = 'mode1', the UE separately applies the following pseudo-code for each of the first set, the second set, and third set as the set of slot timing values , and for the corresponding sets of row indexes as to obtain first, second, and third Type-1 HARQ-ACK sub-codebooks, and concatenates the first, second, and third, Type-1 HARQ-ACK sub-codebooks to obtain the Type-1 HARQ-ACK codebook. The UE sets *maxCodeBlockGroupsPerTransportBlock* to 1 for determining the third Type-1 HARQ-ACK sub-codebook. + +If the UE is configured to monitor PDCCH for DCI formats with CRC scrambled by G-RNTI for multicast or G-CS-RNTI and is not provided *fdmed-ReceptionMulticast*, the UE generates a Type-1 HARQ-ACK codebook using the maximum value of *maxNrofCodeWordsScheduledByDCI* in *PDSCH-config* and *PDSCH-configMulticast* in the following pseudo-code. + +If *timeDomainHARQ-BundlingType1* is provided + +- set +- set to the set of row indexes that include the last SLIV of each row of set + +If the set of rows includes a row with more than one SLIV entry as described in [6, TS 38.214] and *timeDomainHARQ-BundlingType1* is not provided, the set of rows and the set of slot timing values are updated in this clause according to the following pseudo-code. + +set to the set of rows + +set to the cardinality of + +set – index of row in set + +set + +set + +while + +set to the set of entries for row + +set to the set of values of entries for row + +set + +set to the cardinality of + +set to the cardinality of + +set – index of element in set – index of element in + +while + +; + +; + +end while + +while + +; + +; + +end while + +; + +end while + +; + +For the set of slot timing values , the UE determines a set of occasions for candidate PDSCH receptions or SPS PDSCH releases or TCI state update according to the following pseudo-code. A location in the Type-1 HARQ-ACK codebook for HARQ-ACK information corresponding to a single SPS PDSCH release is same as for a corresponding SPS PDSCH reception. A location in the Type-1 HARQ-ACK codebook for HARQ-ACK information corresponding to multiple SPS PDSCH releases by a single DCI format is same as for a corresponding SPS PDSCH reception with the lowest SPS configuration index among the multiple SPS PDSCH releases. If a UE provides HARQ-ACK information corresponding to detection of a DCI format that provides TCI state update without scheduling PDSCH reception, as described in [6, TS 38.214], a location in the Type-1 HARQ-ACK codebook for the HARQ-ACK information is same as when the DCI format schedules a PDSCH reception with CBGs or with transport blocks that are correctly decoded. + +In the following pseudo-code, the *subslotLengthForPUCCH* is for the primary cell if the UE is provided *pucch-sCellPattern*; otherwise, *subslotLengthForPUCCH* is for the serving cell of the PUCCH transmission. + +Set - index of occasion for candidate PDSCH reception or SPS PDSCH release or TCI state update + +Set + +Set + +Set to the cardinality of set + +Set – index of slot timing values , in descending order of the slot timing values, in set for serving cell + +If a UE is not provided *ca-SlotOffset* for any serving cell of PDSCH receptions and for the serving cell of corresponding PUCCH transmission with HARQ-ACK information + +while + +if *subslotLengthForPUCCH* is provided for the HARQ-ACK codebook + +Set – index of a DL slot overlapping with an UL slot + +Set to a number of DL slots overlapping with UL slot if *subslotLengthForPUCCH* is provided for the HARQ-ACK codebook; otherwise, + +while + +if *pdsch-TimeDomainAllocationListForMultiPDSCH* and *timeDomainHARQ-BundlingType1* are provided for serving cell + +; + +; + +elseif *pdsch-TimeDomainAllocationListForMultiPDSCH* is provided and *timeDomainHARQ-BundlingType1* is not provided for serving cell + +; + +else + +Set to the set of rows + +end if + +Set to the cardinality of + +Set – index of row in set + +if slot starts at a same time as or after a slot for an active DL BWP change on serving cell or an active UL BWP change on the serving cell of PUCCH transmission if the UE is provided *pucch-sSCellDyn* or *pucch-sSCellDynDCI-1-2* or *pucch-sSCellDynDCI-1-3*, or an active UL BWP change on the PCell if the UE is not provided *pucch-sSCellDyn* and *pucch-sSCellDynDCI-1-2* and *pucch-sSCellDynDCI-1-3*, and slot is before the slot for the active DL BWP change on serving cell or the active UL BWP change on the serving cell of PUCCH transmission, or *subslotLengthForPUCCH* is provided for the HARQ-ACK codebook and slot overlaps with UL slot, , where is a DL slot with a smallest index among DL slots overlapping with UL slot , + +; + +else + +while + +if the UE is not provided *timeDomainHARQ-BundlingType1* and is provided *tdd-UL-DL-ConfigurationCommon*, or *tdd-UL-DL-ConfigurationDedicated* and, for each slot from slot to slot, at least one symbol of the PDSCH time resource derived by row is configured as UL by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* where is the *k*-th slot timing value in set, where is a DL slot with a smallest index among DL slots overlapping with UL slot, or *subslotLengthForPUCCH* is provided for the HARQ-ACK codebook and the end of the PDSCH time resource for row is not within any UL slot, or if *pdsch-TimeDomainAllocationListForMultiPDSCH* is provided and HARQ-ACK information for PDSCH time resource derived by row in slot cannot be provided in slot + +; + +elseif the UE is provided *timeDomainHARQ-BundlingType1* and *tdd-UL-DL-ConfigurationCommon*, or *tdd-UL-DL-ConfigurationDedicated* and, for each slot, at least one symbol of each PDSCH time resource derived by row of set is configured as UL by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated*, and for each slot from to slot at least one symbol of the PDSCH time resource derived by row of set *R* is configured as UL by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* if the row of set *R* belongs to time domain resource allocation table configured for DCI format 1\_2, where *k* = 0, 1, ..., , and is the cardinality of . + +``` + + ; + ; + ; +else + ; +end if +end while + +if the UE is not provided with multiPDSCH-perSlotType1-CB and the UE does not indicate a capability to +receive more than one unicast PDSCH or multicast PDSCH per slot and , or if the UE is provided with +multiPDSCH-perSlotType1-CB = 'disabled' and , + ; + ; +else + Set to the cardinality of + Set to the smallest last OFDM symbol index, as determined by the SLIV, among all rows of + while + Set + while + if for start OFDM symbol index for row + ; - index of occasion for candidate PDSCH reception, or SPS PDSCH release, or TCI state + update associated with row + ; + ; + else + ; + end if + end while + ; + Set to the smallest last OFDM symbol index among all rows of ; + end while +end if +; +end if +end while +end if +; + +``` + +end while + +else + +while + +if *subslotLengthForPUCCH* is provided for the HARQ-ACK codebook + +Set – index of a DL slot overlapping with an UL slot + +Set to a number of DL slots overlapping with UL slot if *subslotLengthForPUCCH* is provided for the HARQ-ACK codebook; otherwise, + +while + +if *pdsch-TimeDomainAllocationListForMultiPDSCH* and *timeDomainHARQ-BundlingType1* are provided for serving cell + +; + +; + +elseif *pdsch-TimeDomainAllocationListForMultiPDSCH* is provided and *timeDomainHARQ-BundlingType1* is not provided for serving cell + +; + +else + +Set to the set of rows + +end if + +Set to the cardinality of + +Set – index of row in set + +if slot starts at a same time as or after a slot for an active DL BWP change on serving cell or an active UL BWP change on the serving cell of PUCCH transmission if the UE is provided *pucch-sSCellDyn* or *pucch-sSCellDynDCI-1-2* or *pucch-sSCellDynDCI-1-3*, or an active UL BWP change on the PCell if the UE is not provided *pucch-sSCellDyn* and *pucch-sSCellDynDCI-1-2* or *pucch-sSCellDynDCI-1-3*, and slot is before the slot for the active DL BWP change on serving cell or the active UL BWP change on the serving cell of PUCCH transmission where is a DL slot with a smallest index among DL slots overlapping with UL slot , or *subslotLengthForPUCCH* is provided for the HARQ-ACK codebook and slot overlaps with UL slot , , + +; + +else + +while + +if the UE is not provided *timeDomainHARQ-BundlingType1* and is provided *tdd-UL-DL-ConfigurationCommon*, or *tdd-UL-DL-ConfigurationDedicated* and, for each slot from slot to slot , at least one symbol of the PDSCH time resource derived by row is configured as UL by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* where is the *k*-th slot timing value in set , where is a DL slot with a smallest index among DL slots overlapping with UL slot , or *subslotLengthForPUCCH* is provided for the HARQ-ACK codebook and the end of the PDSCH time resource for row is not within any UL slot , or if *pdsch-TimeDomainAllocationListForMultiPDSCH* is provided and HARQ-ACK information for PDSCH time resource derived by row in slot cannot be provided in slot + +; + +elseif the UE is provided *timeDomainHARQ-BundlingType1* and *tdd-UL-DL-ConfigurationCommon*, or *tdd-UL-DL-ConfigurationDedicated* and, for each slot , at least one symbol of each PDSCH time resource derived by row of set is configured as UL by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-* + +*DL-ConfigurationDedicated*, and for each slot from to slot at least one symbol of the PDSCH time resource derived by row of set *R* is configured as UL by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* if the row of set *R* belongs to time domain resource allocation table configured for DCI format 1\_2, where $= 0, 1, \dots$ , + +; + +; + +else + +; + +end if + +end while + +if the UE is not provided with *multiPDSCH-perSlotType1-CB* and the UE does not indicate a capability to receive more than one unicast PDSCH or multicast PDSCH per slot and , or if the UE is provided with *multiPDSCH-perSlotType1-CB* = 'disabled' and , + +; + +; + +else + +Set to the cardinality of + +Set to the smallest last OFDM symbol index, as determined by the *SLIV*, among all rows of + +while + +Set + +while + +if for start OFDM symbol index for row + +; - index of occasion for candidate PDSCH reception, or SPS PDSCH release, or TCI state update associated with row + +; + +; + +else + +; + +end if + +end while + +; + +; + +Set to the smallest last OFDM symbol index among all rows of ; + +end while + +end if + +; + +end if + +end while + +end if + +; + +end while + +end if + +If the UE indicates a capability to receive more than one PDSCH per slot, for occasions of candidate PDSCH receptions corresponding to rows of $\text{coresetPoolIndex}$ associated with a same value of $\text{coresetPoolIndex}$ , where $\text{coresetPoolIndex}$ , the UE does not expect to receive more than one PDSCH in a same DL slot associated with a same $\text{coresetPoolIndex}$ value if provided, or if $\text{coresetPoolIndex}$ is not provided. + +If a UE receives a SPS PDSCH, or a SPS PDSCH release, or TCI state update, or a PDSCH that is scheduled by a DCI format that does not support CBG-based PDSCH receptions and if + +- the UE is configured with one serving cell, and +- $\text{PDSCH-CodeBlockGroupTransmission}$ is provided to the UE + +the UE generates HARQ-ACK information only for the transport block in the PDSCH, or only for the SPS PDSCH release, or only for the TCI state update. + +If a UE receives a SPS PDSCH, or a SPS PDSCH release, or TCI state update, or a PDSCH that is scheduled by a DCI format that does not support CBG-based PDSCH receptions and if + +- the UE is configured with more than one serving cells, or +- $\text{PDSCH-CodeBlockGroupTransmission}$ is provided to the UE + +the UE repeats times the HARQ-ACK information for the transport block in the PDSCH, or for the SPS PDSCH release, or for the TCI state update. + +A UE does not expect to detect a DCI format switching a DL BWP within symbols prior to a first symbol of a PUCCH transmission where the UE multiplexes HARQ-ACK information, where $\text{PUCCH-SymbolDuration}$ is defined in clause 9.2.3. + +If a UE is provided $\text{dl-DataToUL-ACK}$ or $\text{dl-DataToUL-ACK-r16}$ or $\text{dl-DataToUL-ACK-DCI-1-2}$ or $\text{dl-DataToUL-ACK-r17}$ or $\text{dl-DataToUL-ACK-DCI-1-2-r17}$ , the UE does not expect to be indicated by DCI format 1\_0 a slot timing value for transmission of HARQ-ACK information that does not belong to the intersection of the set of slot timing values $\{1, 2, 3, 4, 5, 6, 7, 8\}$ for SCS configuration of PUCCH transmission, $\{7, 8, 12, 16, 20, 24, 28, 32\}$ for $\mu = 0$ , and $\{13, 16, 24, 32, 40, 48, 56, 64\}$ for $\mu = 1$ , and the set of slot timing values provided by $\text{PUCCH-SlotTiming}$ for the active DL BWP of a corresponding serving cell for unicast. + +If $\text{maxNrofCodeWordsScheduledByDCI}$ indicates reception of two transport blocks, when the UE receives a PDSCH with one transport block or a SPS PDSCH release or a TCI state update, the HARQ-ACK information is associated with the first transport block and the UE generates a NACK for the second transport block if $\text{harq-ACK-SpatialBundlingPUCCH}$ is not provided and generates HARQ-ACK information with value of ACK for the second transport block if $\text{harq-ACK-SpatialBundlingPUCCH}$ is provided. + +A UE determines HARQ-ACK information bits, for a total number of HARQ-ACK information bits, of a HARQ-ACK codebook for transmission in a PUCCH according to the following pseudo-code. In the following pseudo-code, if the UE does not receive a transport block or a CBG, due to the UE not detecting a corresponding DCI format, the UE generates a NACK value for the transport block or the CBG. The cardinality of the set $\text{Set}$ defines a total number of occasions for PDSCH reception or SPS PDSCH release or TCI state update for serving cell $\text{Set}$ corresponding to the HARQ-ACK information bits. + +Set – serving cell index: lower indexes correspond to lower RRC indexes of corresponding cells including, when applicable, cells in the set $\text{Set}$ and the set + +Set - HARQ-ACK information bit index + +Set to the number of serving cells configured by higher layers for the UE + +while + +Set – index of occasion for candidate PDSCH reception, or SPS PDSCH release, or TCI state update + +while + +if *timeDomainHARQ-BundlingType1* is provided for serving cell and a PDSCH associated with occasion is scheduled by a DCI format indicating a TDRA row that includes more than one SLIV entry + +if *harq-ACK-SpatialBundlingPUCCH* is not provided and the UE is configured by *maxNrofCodeWordsScheduledByDCI* with reception of two transport blocks for the active DL BWP of serving cell + +if the PDSCH is associated with the last SLIV in the TDRA row + += binary AND operation of the HARQ-ACK information bits corresponding to first transport blocks in PDSCH receptions, that do not overlap with an uplink symbol indicated by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated*, scheduled by the DCI format on serving cell ; + +; + += binary AND operation of the HARQ-ACK information bits corresponding to second transport blocks in PDSCH receptions, that do not overlap with an uplink symbol indicated by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated*, scheduled by the DCI format on serving cell ; + +else + +NACK; + +; + +NACK; + +end if + +; + +elseif *harq-ACK-SpatialBundlingPUCCH* is provided and the UE is configured by *maxNrofCodeWordsScheduledByDCI* with reception of two transport blocks for the active DL BWP of serving cell + +if the PDSCH is associated with the last SLIV in the TDRA row; + += binary AND operation of the HARQ-ACK information bits corresponding to all transport blocks in PDSCHs, that do not overlap with an uplink symbol indicated by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated*, scheduled by the DCI format of serving cell + +if the UE receives one transport block, the UE assumes ACK for the second transport block; + +else + += NACK; + +end if + +; + +else + +if the PDSCH is associated with the last SLIV in the TDRA row; + +``` + + =binary AND operation of the HARQ-ACK information bits corresponding to all transport blocks + in PDSCHs, that do not overlap with an uplink symbol indicated by tdd-UL-DL- + ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, scheduled by the DCI format of + serving cell + + else + = NACK; + end if + ; +end if +else + if harq-ACK-SpatialBundlingPUCCH is not provided, PDSCH-CodeBlockGroupTransmission is not + provided, and the UE is configured by maxNrofCodeWordsScheduledByDCI with reception of two + transport blocks for the active DL BWP of serving cell , + = HARQ-ACK information bit corresponding to a first transport block of this cell; + ; + = HARQ-ACK information bit corresponding to a second transport block of this cell; + ; + elseif harq-ACK-SpatialBundlingPUCCH is provided, and the UE is configured by + maxNrofCodeWordsScheduledByDCI with reception of two transport blocks for the active DL BWP of + serving cell , + = binary AND operation of the HARQ-ACK information bits corresponding to first and second + transport blocks of this cell + if the UE receives one transport block, the UE assumes ACK for the second transport block; + ; + elseif PDSCH-CodeBlockGroupTransmission is provided, and CBGs are indicated by + maxCodeBlockGroupsPerTransportBlock for serving cell , + Set - CBG index + while + = HARQ-ACK information bit corresponding to CBG of the first transport block; + if the UE is configured by maxNrofCodeWordsScheduledByDCI with reception of two transport + blocks for the active DL BWP of serving cell + = HARQ-ACK information bit corresponding to CBG of the second transport block; + end if + ; + end while + , where is the value of maxNrofCodeWordsScheduledByDCI for the active DL BWP of serving cell ; + else + = HARQ-ACK information bit of serving cell ; + ; + +``` + +end if + +end if + +; + +end while + +; + +end while + +If , the UE determines a number of HARQ-ACK information bits for obtaining a transmission power for a PUCCH, as described in clause 7.2.1, as where + +- are all DL cells where the UE is configured to receive unicast or multicast PDSCHs +- is the cardinality for the union of all sets of occasions for unicast or multicast PDSCH receptions or SPS PDSCH releases for serving cell +- is the number of transport blocks the UE receives in PDSCH reception occasion for serving cell if *harq-ACK-SpatialBundlingPUCCH* and *PDSCH-CodeBlockGroupTransmission* are not provided, or the number of transport blocks the UE receives in PDSCH reception occasion for serving cell if *PDSCH-CodeBlockGroupTransmission* is provided and the PDSCH reception is scheduled by a DCI format that does not support CBG-based PDSCH receptions, or the number of PDSCH receptions if *harq-ACK-SpatialBundlingPUCCH* is provided or SPS PDSCH release or TCI state update in PDSCH reception occasion for serving cell and the UE reports corresponding HARQ-ACK information in the PUCCH. +- If *timeDomainHARQ-BundlingType1* is provided for serving cell and for a DCI format indicating a TDRA row that includes more than one SLIV entry on the serving cell , the UE considers as received only a PDSCH associated with the last SLIV. +- is the number of CBGs the UE receives in a PDSCH reception occasion for serving cell if *PDSCH-CodeBlockGroupTransmission* is provided and the PDSCH reception is scheduled by a DCI format that supports CBG-based PDSCH receptions and the UE reports corresponding HARQ-ACK information in the PUCCH. + +#### 9.1.2.2 Type-1 HARQ-ACK codebook in physical uplink shared channel + +If a UE is not provided *pdsch-HARQ-ACK-Codebook* = 'semi-static' for unicast or multicast HARQ-ACK information, the UE does not multiplex the unicast or multicast HARQ-ACK information in the PUSCH transmission, respectively. + +If a UE is provided *pdsch-HARQ-ACK-Codebook* = 'semi-static' for unicast and/or multicast HARQ-ACK information, and would multiplex HARQ-ACK information in a PUSCH transmission that is not scheduled by a DCI format or is scheduled by a DCI format that does not include a DAI field, then + +- if the UE has not received any PDSCH providing a transport block having enabled HARQ-ACK information report or SPS PDSCH release or TCI state update that the UE multiplexes corresponding HARQ-ACK information in the PUSCH, based on a value of a respective PDSCH-to-HARQ feedback timing indicator field in a DCI format scheduling the PDSCH reception or the SPS PDSCH release or the TCI state update, or on the value of *dl-DataToUL-ACK* or *dl-DataToUL-ACK-r16* or *dl-DataToUL-ACK-r17* if the PDSCH-to-HARQ feedback timing indicator field is not present in DCI format 1\_1 or DCI format 1\_3, or on the value of *dl-DataToUL-ACK-DCI-1-2* or *dl-DataToUL-ACK-DCI-1-2-r17* if the PDSCH-to-HARQ feedback timing indicator field is not present in DCI format 1\_2, or on the value of *dl-DataToUL-ACK* if the PDSCH-to-HARQ feedback timing indicator field is not present in DCI format 4\_2, in any of the occasions for candidate PDSCH receptions by a DCI format or SPS PDSCH on any serving cell , as described in clause 9.1.2.1, the UE does not multiplex HARQ-ACK information in the PUSCH transmission +- else the UE generates the HARQ-ACK codebook as described in clause 9.1.2.1, except that *harq-ACK-SpatialBundlingPUCCH* is replaced by *harq-ACK-SpatialBundlingPUSCH*, unless the UE receives only one of + - a SPS PDSCH release indicated by DCI format 1\_0 or by DCI format 4\_1, with counter DAI field value of 1, or + - SPS PDSCH(s) with transport blocks having enabled HARQ-ACK information report, or + +- a PDSCH providing a transport block having enabled HARQ-ACK information report and scheduled by a DCI format 1\_0 or by DCI format 4\_1 with a counter DAI field value of 1, on the PCell + +in the occasions for candidate PDSCH receptions in which case the UE generates HARQ-ACK information only for the SPS PDSCH release or only for the PDSCH reception as described in clause 9.1.2. + +A UE sets to NACK value in the HARQ-ACK codebook any HARQ-ACK information corresponding to PDSCH reception or SPS PDSCH release or TCI state update that the UE detects in a PDCCH monitoring occasion that starts after a PDCCH monitoring occasion where the UE detects a DCI format scheduling the PUSCH transmission. + +A UE does not expect to detect a DCI format switching a DL BWP within symbols prior to a first symbol of a PUSCH transmission where the UE multiplexes HARQ-ACK information, where is defined in [6, TS 38.214]. + +If a UE multiplexes HARQ-ACK information in a PUSCH transmission that is scheduled by DCI format that includes a DAI field, and + +- is not provided *fdmed-ReceptionMulticast* and is provided *pdsch-HARQ-ACK-Codebook* = 'semi-static' for both unicast and multicast HARQ-ACK information, or +- is provided *pdsch-HARQ-ACK-Codebook* = 'semi-static' only for one of unicast and multicast HARQ-ACK information + +the UE generates the HARQ-ACK codebook as described in clause 9.1.2.1 when a value of the DAI field is except that *harq-ACK-SpatialBundlingPUCCH* is replaced by *harq-ACK-SpatialBundlingPUSCH*. The UE does not generate a HARQ-ACK codebook for multiplexing in the PUSCH transmission when unless the UE receives only one of + +- a SPS PDSCH release indicated by DCI format 1\_0 or by DCI format 4\_1, with counter DAI field value of 1, or +- SPS PDSCH(s) with transport blocks having enabled associated HARQ-ACK information reports, +- a PDSCH providing a transport block having enabled HARQ-ACK information report and scheduled by a DCI format 1\_0 or by DCI format 4\_1, or only a TCI state update, with counter DAI field value of 1 on the PCell, + +in the occasions for candidate PDSCH receptions in which case the UE generates HARQ-ACK information only for the SPS PDSCH release or only for the PDSCH reception as described in clause 9.1.2. + +if the PUSCH is scheduled by a DCI format that includes a DAI field and the DAI field is set to '0'; otherwise, . + +If a UE is provided *fdmed-ReceptionMulticast* and is provided *pdsch-HARQ-ACK-Codebook* = 'semi-static' for both unicast and multicast HARQ-ACK information, the UE generates the HARQ-ACK codebook as described in clause 9.1.2.1, except that *harq-ACK-SpatialBundlingPUCCH* is replaced by *harq-ACK-SpatialBundlingPUSCH* + +- for the first set of serving cells if a value of the DAI field associated with unicast HARQ-ACK information is [5, TS 38.212] +- for the second set of serving cells if a value of the DAI field associated with multicast HARQ-ACK information is [5, TS 38.212] + +The UE does not generate unicast or multicast HARQ-ACK information for multiplexing in the PUSCH transmission when and , unless the UE receives only one of + +- either a unicast SPS PDSCH release indicated by DCI format 1\_0, or a multicast SPS PDSCH release indicated by DCI format 4\_1, with counter DAI field value of 1, or +- unicast SPS PDSCH(s) or multicast SPS PDSCH(s) having enabled associated HARQ-ACK information reports, or +- either a PDSCH providing a transport block having enabled HARQ-ACK information report and scheduled by either a DCI format 1\_0 or a DCI format 4\_1 with counter DAI field value of 1, on the PCell, + +in the occasions for candidate PDSCH receptions in which case the UE generates only the corresponding unicast or multicast HARQ-ACK information only for the SPS PDSCH release or only for the PDSCH reception as described in clause 9.1.2. + +if the corresponding value of the DAI field is set to '0'; otherwise, . if the corresponding value of the DAI field is set to '0'; otherwise, [5, TS 38.212]. + +### 9.1.3 Type-2 HARQ-ACK codebook determination + +This clause applies if the UE is configured with *pdsch-HARQ-ACK-Codebook = dynamic* or with *pdsch-HARQ-ACK-Codebook-r16*. Unless stated otherwise, a PDSCH-to-HARQ\_feedback timing indicator field provides an applicable value. In clauses 9.1.3, 9.1.3.1, 9.1.3.2 and 9.1.3.3, if the UE is provided for only one of *pdsch-HARQ-ACK-Codebook = dynamic* or *pdsch-HARQ-ACK-Codebook-r16* for unicast HARQ-ACK-ACK codebook, or *pdsch-HARQ-ACK-Codebook = dynamic* for multicast HARQ-ACK codebook, the Type-2 HARQ-ACK codebook is generated considering only one of respective unicast or multicast configurations for PDSCH receptions or for PDCCH monitoring for detection of DCI formats. + +A UE does not expect to multiplex in a Type-2 HARQ-ACK codebook HARQ-ACK information that is in response to a detection of a DCI format that does not include a counter DAI field. + +If a UE is provided *downlinkHARQ-FeedbackDisabled* indicating disabled HARQ-ACK information for a HARQ process associated with a transport block for PDCCH monitoring occasion or for SPS PDSCH receptions on serving cell, the UE does not multiplex a HARQ-ACK information bit corresponding to the transport block in a Type-2 HARQ-ACK codebook and does not consider the transport block as received in the determination of or in clause 9.1.3.1. If the UE is also provided *PDSCH-CodeBlockGroupTransmission*, the UE does not multiplex HARQ-ACK information bits corresponding to CBGs of the transport block in the Type-2 HARQ-ACK codebook and does not consider the CBGs as received in the determination of in clause 9.1.3.1. If the UE is also provided *harq-feedbackEnablingforSPSactive = 'enabled'*, the UE considers a HARQ process associated with a transport block in a first SPS PDSCH reception, after an activation of SPS PDSCH receptions, to have enabled HARQ-ACK information and the UE provides a HARQ-ACK information bit according to a decoding outcome for the transport block in the first SPS PDSCH reception. + +If a UE is indicated to not provide multicast HARQ-ACK information, as described in clause 18, associated with PDCCH monitoring occasion or for SPS PDSCH receptions on serving cell, the UE does not multiplex corresponding HARQ-ACK information bits in a Type-2 HARQ-ACK codebook and does not consider any transport blocks as received in the determination of or of in clause 9.1.3.1. + +If a UE receives a first DCI format that the UE detects in a first PDCCH monitoring occasion and includes a PDSCH-to-HARQ\_feedback timing indicator field providing an inapplicable value from *dl-DataToUL-ACK-r16* or *dl-DataToUL-ACK-r17*, + +- if the UE detects a second DCI format, the UE multiplexes the corresponding HARQ-ACK information in a PUCCH or PUSCH transmission in a slot that is indicated by a value of a PDSCH-to-HARQ\_feedback timing indicator field in the second DCI format, where +- if the UE is not provided *pdsch-HARQ-ACK-Codebook-r16*, the UE detects the second DCI format in any PDCCH monitoring occasion after the first one, and where the slot indicated by the value of the PDSCH-to-HARQ\_feedback timing indicator field in the second DCI format is no later than a slot for HARQ-ACK information in response to a SPS PDSCH reception, if any, received after the PDSCHs scheduled by the first DCI format. +- if the UE is provided *pdsch-HARQ-ACK-Codebook-r16*, the UE detects the second DCI format in any PDCCH monitoring occasion after the first one, and the second DCI format indicates a HARQ-ACK information report for a same PDSCH group index as indicated by the first DCI format as described in clause 9.1.3.3, and where the slot indicated by the value of the PDSCH-to-HARQ\_feedback timing indicator field in the second DCI format is no later than a slot for HARQ-ACK information in response to a SPS PDSCH reception, if any, received after the PDSCHs scheduled by the first DCI format. +- if the UE is provided *pdsch-HARQ-ACK-Codebook-r16*, the UE receives the second DCI format later than the slot for HARQ-ACK information in response to a SPS PDSCH reception received after the PDSCHs scheduled by the first DCI format, and the second DCI format indicates a HARQ-ACK information report for a same PDSCH group index as indicated by the first DCI format as described in clause 9.1.3.3. +- if the UE is provided *pdsch-HARQ-ACK-OneShotFeedback*, the first DCI format does not have associated HARQ-ACK information without scheduling a PDSCH reception or TCI state update, the UE detects the second DCI format in any PDCCH monitoring occasion after the first one, and the second DCI format includes a One-shot HARQ-ACK request field with value 1, the UE includes the HARQ-ACK information in a Type-3 HARQ-ACK codebook, as described in clause 9.1.4, and where the slot indicated by the value of the PDSCH-to-HARQ\_feedback timing indicator field in the second DCI format is no later than a slot for + +HARQ-ACK information in response to a SPS PDSCH reception, if any, received after the PDSCHs scheduled by the first DCI format. + +- if the UE is provided *pdsch-HARQ-ACK-OneShotFeedback-r16*, the first DCI format does not have associated HARQ-ACK information without scheduling a PDSCH reception or TCI state update, and the UE receives the second DCI format later than the slot for HARQ-ACK information in response to a SPS PDSCH reception received after the PDSCHs scheduled by the first DCI format, and the second DCI format includes a One-shot HARQ-ACK request field with value 1, the UE includes the HARQ-ACK information in a Type-3 HARQ-ACK codebook, as described in clause 9.1.4. +- otherwise, the UE does not multiplex the corresponding HARQ-ACK information in a PUCCH or PUSCH transmission. + +#### 9.1.3.1 Type-2 HARQ-ACK codebook in physical uplink control channel + +If a UE is configured to monitor PDCCH for multicast DCI formats with CRC scrambled by one or more G-RNTIs for multicast or G-CS-RNTIs that the UE generates a Type-2 HARQ-ACK codebook, the UE separately applies the procedures in this clause per G-RNTI for multicast or per G-CS-RNTI using *maxNrofCodeWordsScheduledByDCI* in *pdsch-ConfigMulticast* except the procedures for SPS PDSCHs and applies the procedures in this clause using *maxNrofCodeWordsScheduledByDCI* provided in *pdsch-Config* for unicast DCI formats excluding the unicast DCI format activating SPS PDSCH receptions, and determines the Type-2 HARQ-ACK codebook by concatenating the Type-2 HARQ-ACK codebook for unicast DCI formats excluding the unicast DCI format activating SPS PDSCH receptions, followed by the HARQ-ACK codebooks for the multicast DCI formats in ascending order of the corresponding G-RNTI values, followed by the HARQ-ACK codebooks for the multicast DCI formats in ascending order of the corresponding G-CS-RNTI values excluding the multicast DCI format activating SPS PDSCH receptions, followed by the HARQ-ACK codebooks for unicast and multicast SPS PDSCH receptions. + +A UE determines monitoring occasions for PDCCH with DCI format scheduling PDSCH receptions, or having associated HARQ-ACK information without scheduling PDSCH reception, on an active DL BWP of a serving cell, as described in clause 10.1, and for which the UE transmits HARQ-ACK information in a same PUCCH in slot based on + +- PDSCH-to-HARQ feedback timing indicator field values, or a *dl-DataToUL-ACK*, *dl-DataToUL-ACK-r16* or *dl-DataToUL-ACK-DCI-1-2* or *dl-DataToUL-ACK-r17* or *dl-DataToUL-ACK-DCI-1-2-r17* value if the PDSCH-to-HARQ feedback timing indicator field is not present in a DCI format, for PUCCH transmission with HARQ-ACK information in slot, as described in clause 9.2.3, in response to PDSCH receptions, or in response to a DCI format having associated HARQ-ACK information without scheduling PDSCH reception +- slot offsets [6, TS 38.214] provided by time domain resource assignment field in a DCI format scheduling PDSCH receptions and by *pdsch-AggregationFactor*, or *pdsch-AggregationFactor-r16*, or *repetitionNumber*, when provided. + +The set of PDCCH monitoring occasions for DCI formats scheduling PDSCH receptions, or having associated HARQ-ACK information without scheduling PDSCH reception, is defined as the union of PDCCH monitoring occasions across active DL BWPs of configured serving cells. PDCCH monitoring occasions are indexed in an ascending order of their start times. The cardinality of the set of PDCCH monitoring occasions defines a total number of PDCCH monitoring occasions. PDCCH monitoring occasions are separately counted for a DCI format scheduling a PDSCH reception on a single serving cell and for a DCI format scheduling PDSCH receptions on more than one serving cells and corresponding values of can be different. + +A value of the counter downlink assignment indicator (DAI) field in DCI formats, each scheduling PDSCH receptions on respective single serving cells with associated HARQ-ACK information, or having associated HARQ-ACK information without scheduling a PDSCH reception, in a same HARQ-ACK codebook denotes the accumulative number of {serving cell, PDCCH monitoring occasion}-pairs in which PDSCH receptions that provide transport blocks with enabled HARQ-ACK information report, or HARQ-ACK information bits that are not in response for PDSCH receptions, associated with the DCI formats, excluding the SPS activation DCI, is present up to the current serving cell and current PDCCH monitoring occasion, + +- first, if the UE indicates by *type2-HARQ-ACK-Codebook* support for more than one PDSCH reception on a serving cell that are scheduled from a same PDCCH monitoring occasion, in increasing order of the PDSCH reception starting time for the same {serving cell, PDCCH monitoring occasion} pair, +- second in ascending order of serving cell index, and +- third in ascending order of PDCCH monitoring occasion index, where . + +A value of the counter DAI field in DCI formats, each scheduling PDSCH receptions on respective more than one serving cells with associated HARQ-ACK information in a same HARQ-ACK codebook, denotes the accumulative number of {serving cell with smallest index from the more than one serving cells, PDCCH monitoring occasion}-pairs in which PDSCH receptions are present up to the current more than one serving cells and current PDCCH monitoring occasion, + +- first, if the UE indicates by *type2-HARQ-ACK-Codebook* support for more than one PDSCH receptions on a serving cell that are scheduled from a same PDCCH monitoring occasion, in increasing order of the PDSCH reception starting time for the same {serving cell with smallest index from the more than one serving cells, PDCCH monitoring occasion} pair, +- second in ascending order of the smallest serving cell index from the more than one serving cells, and +- third in ascending order of PDCCH monitoring occasion index , where . + +If, for an active DL BWP of a serving cell, the UE is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with value 0 for one or more first CORESETs and is provided *coresetPoolIndex* with value 1 for one or more second CORESETs, and is provided *ackNackFeedbackMode = joint*, the value of the counter DAI is in the order of the first CORESETs and then the second CORESETs for a same serving cell index and a same PDCCH monitoring occasion index. + +The value of the total DAI, when present [5, TS 38.212], in a DCI format denotes the total number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH reception(s) that provide transport blocks with enabled HARQ-ACK information report, or HARQ-ACK information that does not correspond to PDSCH receptions, associated with DCI formats, excluding the SPS activation DCI, is present, up to the current PDCCH monitoring occasion and is updated from PDCCH monitoring occasion to PDCCH monitoring occasion. If, for an active DL BWP of a serving cell, the UE is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with value 0 for one or more first CORESETs and is provided *coresetPoolIndex* with value 1 for one or more second CORESETs, and is provided *ackNackFeedbackMode = joint*, the total DAI value counts the {serving cell, PDCCH monitoring occasion}-pair(s) for both the first CORESETs and the second CORESETs. + +Denote by $n_{bit}$ the number of bits for the counter DAI and set $n_{bit} = 2$ . Denote by the value of the counter DAI in a DCI format scheduling PDSCH reception, or having associated HARQ-ACK information without scheduling PDSCH reception, on serving cell $c$ in PDCCH monitoring occasion $m$ according to Table 9.1.3-1 or Table 9.1.3-1A. Denote by $n_{DAI}$ the value of the total DAI in a DCI format in PDCCH monitoring occasion $m$ according to Table 9.1.3-1. The UE assumes a same value of total DAI in all DCI formats that include a total DAI field in PDCCH monitoring occasion $m$ . A UE does not expect to multiplex, in a same Type-2 HARQ-ACK codebook, HARQ-ACK information that is in response to detection of DCI formats with different number of bits for the counter DAI field. + +If the UE transmits HARQ-ACK information in a PUCCH in slot $n$ and for any PUCCH format, the UE determines the $n_{bit}$ , for a total number of HARQ-ACK information bits, according to the following pseudo-code: + +Set $n_{bit} = 2$ – PDCCH, with DCI format scheduling PDSCH reception, or having associated HARQ-ACK information without scheduling a PDSCH reception, monitoring occasion index: lower index corresponds to earlier PDCCH monitoring occasion + +Set $n_{cell} = 0$ + +Set $n_{DAI} = 0$ + +Set $n_{bit} = 2$ + +Set $n_{cell} = 0$ + +Set $n_{cell}$ to the number of serving cells configured by higher layers for the UE + +- if, for an active DL BWP of a serving cell, the UE is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with value 0 for one or more first CORESETs and is provided *coresetPoolIndex* with value 1 for one or more second CORESETs, and is provided *ackNackFeedbackMode = joint*, the serving cell is counted two times where the first time corresponds to the first CORESETs and the second time corresponds to the second CORESETs +- if the UE indicates *type2-HARQ-ACK-Codebook* and receives a number of PDSCHs on a serving cell $c$ that are scheduled by DCI formats in PDCCH receptions at a same PDCCH monitoring occasion $m$ , the serving cell $c$ is counted $n_{bit}$ times for PDCCH monitoring occasion $m$ in increasing order of the PDSCH reception starting time + +Set to the number of PDCCH monitoring occasion(s) + +while + +Set – serving cell index: lower indexes correspond to lower RRC indexes of corresponding cell + +while + +if PDCCH monitoring occasion is before an active DL BWP change on serving cell or an active UL BWP change on the serving cell of PUCCH transmission if the UE is provided *pucch-sSCellDyn* or *pucch-sSCellDynDCI-1-2*, or an active UL BWP change on the PCell if the UE is not provided *pucch-sSCellDyn* and *pucch-sSCellDynDCI-1-2*, and an active DL BWP change is not triggered in PDCCH monitoring occasion + +; + +else + +if there is a PDSCH providing a transport block for a HARQ process with enabled HARQ-ACK information on serving cell associated with PDCCH in PDCCH monitoring occasion, or there is a PDCCH providing a DCI format associated with HARQ-ACK information without scheduling PDSCH reception on serving cell + +if + +end if + +if + +else + +end if + +if *harq-ACK-SpatialBundlingPUCCH* is not provided and the UE is configured by *maxNrofCodeWordsScheduledByDCI* with reception of two transport blocks for at least one configured DL BWP of at least one serving cell, + += HARQ-ACK information bit corresponding to the first transport block of this cell + += HARQ-ACK information bit corresponding to the second transport block of this cell + +elseif *harq-ACK-SpatialBundlingPUCCH* is provided to the UE and is a monitoring occasion for PDCCH with a DCI format that supports PDSCH reception with two transport blocks and the UE is configured by *maxNrofCodeWordsScheduledByDCI* with reception of two transport blocks in at least one configured DL BWP of at least one serving cell, + += binary AND operation of the HARQ-ACK information bits corresponding to the first and second transport blocks of this cell + +else + += HARQ-ACK information bit of this cell + +end if + +end if + +end if + +end while + +end while + +if UE does not set and + +end if + +if + +end if + +if *harq-ACK-SpatialBundlingPUCCH* is not provided to the UE and the UE is configured by *maxNrofCodeWordsScheduledByDCI* with reception of two transport blocks for at least one configured DL BWP of a serving cell, + +else + +end if + +for any + +If a UE is configured to receive SPS PDSCH and the UE multiplexes HARQ-ACK information for one activated SPS PDSCH reception that provides transport block with enabled HARQ-ACK information report, including the ones associated with the corresponding activation DCI, in the PUCCH in slot , the UE generates one HARQ-ACK information bit associated with the SPS PDSCH reception and appends it to the HARQ-ACK information bits. + +If a UE is configured to receive SPS PDSCH and the UE multiplexes HARQ-ACK information for multiple activated SPS PDSCH receptions, including the ones associated with the corresponding activation DCI and excluding the ones that provide only transport blocks with disabled HARQ-ACK information report, in the PUCCH in slot , the UE generates the HARQ-ACK information as described in clause 9.1.2 and appends it to the HARQ-ACK information bits. + +The UE generates HARQ-ACK information with ACK value in response to a detection of a DCI format that does not trigger a Type-3 HARQ-ACK codebook report and has associated HARQ-ACK information without scheduling a PDSCH reception. + +For a PDCCH monitoring occasion with DCI format scheduling PDSCH reception, or having associated HARQ-ACK information without scheduling a PDSCH reception, in the active DL BWP of a serving cell, when a UE receives a PDSCH with one transport block, or detects a DCI format having associated HARQ-ACK information without scheduling PDSCH reception, and the value of *maxNrofCodeWordsScheduledByDCI* is 2 for at least one configured DL BWP of at least one serving cell, the HARQ-ACK information is associated with the first transport block and the UE generates a NACK for the second transport block if *harq-ACK-SpatialBundlingPUCCH* is not provided and generates HARQ-ACK information with value of ACK for the second transport block if *harq-ACK-SpatialBundlingPUCCH* is provided. + +If a UE is + +- not provided *PDSCH-CodeBlockGroupTransmission* for any serving cell, and +- not provided *pdsch-TimeDomainAllocationListForMultiPDSCH* for any serving cell, or provided *nrofHARQ-BundlingGroups* with value of 1 for any serving cell provided *pdsch-TimeDomainAllocationListForMultiPDSCH* + +or + +- for PDSCH receptions scheduled by a DCI format that does not support CBG-based PDSCH receptions and does not schedule more than one PDSCH reception, or +- for PDSCH receptions scheduled by a DCI format on a serving cell when the UE is provided *nrofHARQ-BundlingGroups* with value of 1, or +- for SPS PDSCH reception, or +- for a DCI format having associated HARQ-ACK information without scheduling PDSCH reception, and + +if , the UE determines a number of HARQ-ACK information bits for obtaining a transmission power for a PUCCH, as described in clause 7.2.1, as + +where + +- is a number of serving cells where the UE is configured to receive unicast PDSCHs +- is a number of serving cells where the UE is configured to receive multicast PDSCHs for a G-RNTI for multicast or a G-CS-RNTI +- is a total number of G-RNTIs for multicast or G-CS-RNTIs configured to the UE +- is the number of PDCCH monitoring occasions for unicast DCI formats +- is the number of PDCCH monitoring occasions for multicast DCI formats with CRC scrambled by G-RNTI for multicast or G-CS-RNTI +- where the number of bits for the counter DAI field in unicast DCI formats +- where the number of bits for the counter DAI field in multicast DCI formats with CRC scrambled by G-RNTI for multicast or G-CS-RNTI +- if , is the value of the counter DAI in the last DCI format scheduling PDSCH reception or having associated HARQ-ACK information without scheduling PDSCH reception, that the UE detects within the PDCCH monitoring occasions. +- if , is the value of the counter DAI in the last multicast DCI format with G-RNTI for multicast, or G-CS-RNTI , scheduling PDSCH reception or having associated HARQ-ACK information without scheduling a PDSCH reception, that the UE detects within the PDCCH monitoring occasions +- if or if + - if the UE does not detect any DCI format that includes a total DAI field in a last PDCCH monitoring occasion within the or PDCCH monitoring occasions where the UE detects at least one DCI format scheduling PDSCH reception, or having associated HARQ-ACK information without scheduling PDSCH reception, for any serving cell , or , respectively, is the value of the counter DAI in a last DCI format the UE detects in the last PDCCH monitoring occasion + - if the UE detects at least one DCI format that includes a total DAI field in a last PDCCH monitoring occasion within the or , for G-RNTI for multicast or G-CS-RNTI , PDCCH monitoring occasions where the UE detects at least one DCI format scheduling PDSCH reception, or having associated HARQ-ACK information without scheduling PDSCH reception, for any serving cell , or , respectively, is the value of the total DAI in the at least one DCI format that includes a total DAI field + +- or if the UE does not detect any DCI format scheduling PDSCH reception, or having associated HARQ-ACK information without scheduling PDSCH reception, for any serving cell in any of the or PDCCH monitoring occasions, respectively. +- or, for G-RNTI for multicast or G-CS-RNTI, is the total number of DCI formats scheduling PDSCH receptions providing transport blocks with enabled HARQ-ACK information, or having associated HARQ-ACK information without scheduling a PDSCH reception, that the UE detects within the or PDCCH monitoring occasions, respectively, for serving cell. or if the UE does not detect any DCI format scheduling PDSCH reception providing a transport block with enabled HARQ-ACK information, or having associated HARQ-ACK information without scheduling PDSCH reception, for serving cell in any of the or, respectively, PDCCH monitoring occasions. +- if the value of *maxNrofCodeWordsScheduledByDCI* is 2 for any serving cell and *harq-ACK-SpatialBundlingPUCCH* is not provided; otherwise, . +- if the value of *maxNrofCodeWordsScheduledByDCI* is 2 for any serving cell and *harq-ACK-SpatialBundlingPUCCH* is not provided for G-RNTI for multicast or G-CS-RNTI; otherwise, . +- or, for G-RNTI for multicast or G-CS-RNTI, is + - if *harq-ACK-SpatialBundlingPUCCH* is not provided, the number of transport blocks the UE receives in a PDSCH, or the number of transport block groups the UE receives in PDSCHs if *nrofHARQ-BundlingGroups* with is provided, scheduled by a DCI format that the UE detects in PDCCH monitoring occasion for serving cell, or + - if *harq-ACK-SpatialBundlingPUCCH* is provided, the number of PDSCHs, or the number of PDSCH groups if *nrofHARQ-BundlingGroups* with is provided, scheduled by a DCI format that the UE detects in PDCCH monitoring occasion for serving cell, or + - the number of DCI formats that the UE detects and have associated a HARQ-ACK information without scheduling PDSCH reception in PDCCH monitoring occasion for serving cell. +- or, for G-RNTI for multicast or G-CS-RNTI, is the number of SPS PDSCH receptions by the UE on serving cell for which the UE transmits corresponding HARQ-ACK information in the same PUCCH as for HARQ-ACK information corresponding to PDSCH receptions within the or PDCCH monitoring occasions, respectively. + +If a UE + +- is provided *PDSCH-CodeBlockGroupTransmission* for serving cells; and +- is not provided *PDSCH-CodeBlockGroupTransmission*, for serving cells where + +the UE determines the according to the previous pseudo-code with the following modifications + +- is used for the determination of a first HARQ-ACK sub-codebook for + - SPS PDSCH reception, + - a DCI format having associated HARQ-ACK information without scheduling PDSCH reception, + - TCI state update, and + - TB-based PDSCH receptions on the serving cells and on the serving cells, +- is replaced by for the determination of a second HARQ-ACK sub-codebook corresponding to the serving cells for CBG-based PDSCH receptions, and +- if, for an active DL BWP of a serving cell, the UE is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with value 0 for one or more first CORESETs and is provided *coresetPoolIndex* with value 1 for one or more second CORESETs, and is provided *ackNackFeedbackMode = joint*, the serving cell is counted as two times where the first time corresponds to the first CORESETs and the second time corresponds to the second CORESETs, and +- instead of generating one HARQ-ACK information bit per transport block for a serving cell from the serving cells, the UE generates HARQ-ACK information bits, where is the maximum value of across all serving + +cells and is the value of *maxNrofCodeWordsScheduledByDCI* for serving cell . If for a serving cell it is , the UE generates NACK for the last HARQ-ACK information bits for serving cell + +- the pseudo-code operation when *harq-ACK-SpatialBundlingPUCCH* is provided is not applicable +- The counter DAI value and the total DAI value apply separately for each HARQ-ACK sub-codebook +- The UE generates the HARQ-ACK codebook by appending the second HARQ-ACK sub-codebook to the first HARQ-ACK sub-codebook + +If , the UE also determines for obtaining a PUCCH transmission power, as described in clause 7.2.1, with + +where + +- if , is the value of the counter DAI in the last DCI format scheduling CBG-based PDSCH reception that the UE detects within the PDCCH monitoring occasions +- if , is the value of the total DAI in the last DCI format scheduling CBG-based PDSCH reception for any serving cell that the UE detects within the PDCCH monitoring occasions +- , if the UE does not detect any DCI format scheduling CBG-based PDSCH reception for any serving cell in any of the PDCCH monitoring occasions +- is the total number of DCI formats scheduling CBG-based PDSCH receptions that the UE detects within the PDCCH monitoring occasions for serving cell . if the UE does not detect any DCI format scheduling CBG-based PDSCH reception for serving cell in any of the PDCCH monitoring occasions +- is the number of CBGs the UE receives in a PDSCH scheduled by a DCI format that supports CBG-based PDSCH reception that the UE detects in PDCCH monitoring occasion for serving cell and the UE reports corresponding HARQ-ACK information in the PUCCH + +If a UE is provided *nrofHARQ-BundlingGroups* and is not provided *harq-ACK-SpatialBundlingPUCCH* for a serving cell , the UE generates HARQ-ACK information over transport block groups (TBGs) for PDSCH receptions where, for a maximum number of PDSCH receptions scheduled by a DCI format on the serving cell, a maximum number of TBGs is provided by *nrofHARQ-BundlingGroups*. If the UE detects a DCI format scheduling PDSCH receptions on the serving cell , the UE generates HARQ-ACK information bits for the first TBs and, if applicable, generates HARQ-ACK information bits for the second TBs as described in clause 9.1.1 by setting and . For a TBG associated with at least one PDSCH that does not overlap with an UL symbol indicated by *tdd-UL-DL-ConfigurationCommon*, or by *tdd-UL-DL-ConfigurationDedicated* if provided, the UE assumes that TB(s) provided by a PDSCH that overlaps with an UL symbol indicated by *tdd-UL-DL-ConfigurationCommon*, or by *tdd-UL-DL-ConfigurationDedicated* if provided, are correctly received. For a TBG associated only with PDSCHs that overlap with UL symbols indicated by *tdd-UL-DL-ConfigurationCommon*, or by *tdd-UL-DL-ConfigurationDedicated* if provided, the UE generates a NACK value for the TBG. + +If a UE is provided *nrofHARQ-BundlingGroups* and *harq-ACK-SpatialBundlingPUCCH* for a serving cell , the UE generates HARQ-ACK information over PDSCH reception groups for PDSCH receptions scheduled by a DCI format on the serving cell where a maximum number of PDSCH reception groups, is provided by *nrofHARQ-BundlingGroups*. If the UE detects a DCI format scheduling PDSCH receptions on the serving cell , the UE generates HARQ-ACK information bits for the PDSCH receptions as described in clause 9.1.1 by setting and , after binary AND operation of the HARQ-ACK information bits corresponding to the first and second transport blocks of each PDSCH reception. For a PDSCH reception group associated with at least one PDSCH that does not overlap with an UL symbol indicated by *tdd-UL-DL-ConfigurationCommon*, or by *tdd-UL-DL-ConfigurationDedicated* if provided, the UE assumes that TBs provided by a PDSCH that overlaps with an UL symbol indicated by *tdd-UL-DL-ConfigurationCommon*, or by *tdd-UL-DL-ConfigurationDedicated* if provided, are correctly received. For a PDSCH reception group associated only with PDSCHs that overlap with UL symbols indicated by *tdd-UL-DL-ConfigurationCommon*, or by *tdd-UL-DL-ConfigurationDedicated* if provided, the UE generates a NACK value for the PDSCH reception group. + +If a UE is provided *pdsch-TimeDomainAllocationListForMultiPDSCH* and neither provided *nrofHARQ-BundlingGroups* nor *harq-ACK-SpatialBundlingPUCCH* for a serving cell , the UE generates HARQ-ACK information over transport blocks for PDSCH receptions. If the UE detects a DCI format scheduling PDSCH receptions on the serving cell , the UE generates HARQ-ACK information bits for the first TBs in the ascending order of the starting of + +PDSCH receptions and, if applicable, generates HARQ-ACK information bits for the second TBs in the ascending order of the starting of PDSCH receptions. For a PDSCH reception that overlaps with an UL symbol indicated by *tdd-UL-DL-ConfigurationCommon*, or by *tdd-UL-DL-ConfigurationDedicated* if provided, the UE generates a NACK value for the first TB and, if applicable, generates a NACK value for the second TB in the PDSCH reception. If $<$ , the UE generates a NACK value for the last HARQ-ACK information bits where $\max NrofCodeWordsScheduledByDCI$ is the value of $\max NrofCodeWordsScheduledByDCI$ for serving cell $c$ and is determined by the maximum number of SLIVs amongst all rows of the TDRA table configured by *pdsch-TimeDomainAllocationListForMultiPDSCH*. + +If a UE is provided *pdsch-TimeDomainAllocationListForMultiPDSCH* and *harq-ACK-SpatialBundlingPUCCH* and not provided *nrofHARQ-BundlingGroups* for a serving cell $c$ , the UE generates HARQ-ACK information over PDSCH receptions for PDSCH receptions scheduled by a DCI format on the serving cell $c$ . If the UE detects a DCI format scheduling PDSCH receptions on the serving cell $c$ , the UE generates HARQ-ACK information bits for the PDSCH receptions in the ascending order of the starting of PDSCH receptions after binary AND operation of the HARQ-ACK information bits corresponding to the first and second transport blocks of each PDSCH reception. For a PDSCH reception that overlaps with an UL symbol indicated by *tdd-UL-DL-ConfigurationCommon*, or by *tdd-UL-DL-ConfigurationDedicated* if provided, the UE generates a NACK value for the PDSCH reception. If $<$ , the UE generates a NACK value for the last HARQ-ACK information bits. + +If a UE + +- is provided *pdsch-TimeDomainAllocationListForMultiPDSCH* and, if provided, *nrofHARQ-BundlingGroups* with value $\max NrofCodeWordsScheduledByDCI$ for serving cells; and +- is not provided *pdsch-TimeDomainAllocationListForMultiPDSCH* or is provided *nrofHARQ-BundlingGroups* with value $\max NrofCodeWordsScheduledByDCI$ , for serving cells where + +the UE determines the $\max NrofCodeWordsScheduledByDCI$ according to the previous pseudo-code with the following modifications + +- $\max NrofCodeWordsScheduledByDCI$ is used for the determination of a first HARQ-ACK sub-codebook for + - SPS PDSCH reception, + - any DCI format having associated HARQ-ACK information without scheduling PDSCH reception, and + - PDSCH reception scheduled by a DCI format scheduling one PDSCH + - PDSCH reception with $\max NrofCodeWordsScheduledByDCI$ for TBG-based HARQ-ACK information on the serving cells, +- $\max NrofCodeWordsScheduledByDCI$ is replaced by $\max NrofCodeWordsScheduledByDCI$ for the determination of a second HARQ-ACK sub-codebook corresponding to the serving cells for TBG-based HARQ-ACK information, or for TB-based HARQ-ACK information corresponding to multiple PDSCH receptions scheduled by a single DCI format, and +- if, for an active DL BWP of a serving cell, the UE is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with value 0 for one or more first CORESETs and is provided *coresetPoolIndex* with value 1 for one or more second CORESETs, and is provided *ackNackFeedbackMode = joint*, the serving cell is counted as two times where the first time corresponds to the first CORESETs and the second time corresponds to the second CORESETs, and +- instead of generating one or two HARQ-ACK information bits per PDSCH for a serving cell from the serving cells, the UE generates HARQ-ACK information bits for the PDSCH receptions scheduled by a DCI format, where $\max NrofCodeWordsScheduledByDCI$ is the maximum value between $\max NrofCodeWordsScheduledByDCI$ across all serving cells if the UE is provided *nrofHARQ-BundlingGroups*, and $\max NrofCodeWordsScheduledByDCI$ across all serving cells where the UE is not provided *nrofHARQ-BundlingGroups*, and $\max NrofCodeWordsScheduledByDCI$ is the value of $\max NrofCodeWordsScheduledByDCI$ for serving cell $c$ if *harq-ACK-SpatialBundlingPUCCH* is not provided; else, $\max NrofCodeWordsScheduledByDCI$ . If for a serving cell $c$ where the UE is provided *nrofHARQ-BundlingGroups*, it is $\max NrofCodeWordsScheduledByDCI$ , the UE generates NACK for the last HARQ-ACK information bits for serving cell $c$ . If for a serving cell $c$ where the UE is not provided *nrofHARQ-BundlingGroups*, it is $\max NrofCodeWordsScheduledByDCI$ , the UE generates NACK for the last HARQ-ACK information bits for serving cell $c$ . +- The pseudo-code operation when *PDSCH-CodeBlockGroupTransmission* is provided is not applicable. +- The counter DAI value and the total DAI value apply separately for each HARQ-ACK sub-codebook. +- The UE generates the HARQ-ACK codebook by appending the second HARQ-ACK sub-codebook to the first HARQ-ACK sub-codebook. + +If and , the UE also determines for obtaining a PUCCH transmission power, as described in clause 7.2.1, with + +where + +- if , is the value of the counter DAI in the last DCI format scheduling more than one PDSCH receptions for any serving cell from the serving cells with TBG-based HARQ-ACK information or with TB-based HARQ-ACK information that the UE detects within the PDCCH monitoring occasions +- if , is the value of the total DAI in the last DCI format scheduling more than one PDSCH receptions with TBG-based HARQ-ACK information or with TB-based HARQ-ACK information for any serving cell from the serving cells that the UE detects within the PDCCH monitoring occasions +- , if the UE does not detect any DCI format scheduling more than one PDSCH receptions with TBG-based HARQ-ACK information or with TB-based HARQ-ACK information for any serving cell from the serving cells in any of the PDCCH monitoring occasions +- is the total number of DCI formats scheduling more than one PDSCH receptions with TBG-based HARQ-ACK information or with TB-based HARQ-ACK information for any serving cell from the serving cells that the UE detects within the PDCCH monitoring occasions for serving cell . if the UE does not detect any DCI format scheduling more than one PDSCH receptions for serving cell in any of the PDCCH monitoring occasions +- if *harq-ACK-SpatialBundlingPUCCH* is provided, + - if *nrofHARQ-BundlingGroups* is provided, is the number of PDSCH groups that include at least one PDSCH not overlapping with a UL symbol indicated by *tdd-UL-DL-ConfigurationCommon*, or *tdd-UL-DL-ConfigurationDedicated* if provided, that the UE receives in serving cell from the serving cells in PDCCH monitoring occasion and the UE reports corresponding HARQ-ACK information in the PUCCH + - if *nrofHARQ-BundlingGroups* is not provided, is the number of PDSCHs that the UE receives in serving cell from the serving cells in PDCCH monitoring occasion and the UE reports corresponding HARQ-ACK information in the PUCCH +- if *harq-ACK-SpatialBundlingPUCCH* is not provided, + - if *nrofHARQ-BundlingGroups* is provided, is the number of TBGs including at least one PDSCH not overlapping with an UL symbol indicated by *tdd-UL-DL-ConfigurationCommon*, or by *tdd-UL-DL-ConfigurationDedicated* if provided, that the UE receives in serving cell from the serving cells in PDCCH monitoring occasion and the UE reports corresponding HARQ-ACK information in the PUCCH + - if *nrofHARQ-BundlingGroups* is not provided, is the number of transport blocks in PDSCHs that the UE receives in serving cell from the serving cells in PDCCH monitoring occasion and the UE reports corresponding HARQ-ACK information in the PUCCH. + +If a UE is provided by *MC-DCI-SetofCellsToAddModList* a number of sets of serving cells and is provided USS sets to monitor PDCCH for detection of DCI format 1\_3, the UE separately applies the following procedures for determining a corresponding second Type-2 HARQ-ACK sub-codebook for scheduling cells associated with DCI format 1\_3 that + +- schedules PDSCH receptions on more than one serving cells from a set of serving cells, and/or +- does not include a SCell dormancy indication field or the SCell dormancy indication field is reserved, indicates SCell dormancy, and schedules PDSCH reception on one or more serving cells from the set of serving cells +- in the following, and for the purpose of providing HARQ-ACK information corresponding to SCell dormancy indication, the UE assumes that the UE receives a PDSCH on the serving cell associated with fields in DCI format 1\_3 used for SCell dormancy indication, as described in Clause 10.3, and that the PDSCH provides one transport block that the UE correctly decodes + +from the procedures for determining a first Type-2 HARQ-ACK sub-codebook that is associated with unicast SPS PDSCH receptions or with any unicast DCI format scheduling a PDSCH reception on a single serving cell, or has associated HARQ-ACK information without scheduling a PDSCH reception as described in this clause. The UE appends the second Type-2 HARQ-ACK sub-codebook to the first Type-2 HARQ-ACK sub-codebook. + +Denote by $N_{DAI}^{1\_3}$ the number of bits for the counter DAI field in DCI format 1\_3 and set $N_{DAI}^{1\_3}$ . Denote by $DAI_{1\_3}$ the value of the counter DAI in a DCI format 1\_3 scheduling PDSCH receptions on more than one cells from the set of serving cells with index $c$ , in PDCCH monitoring occasion $o$ according to Table 9.1.3-1. Denote by $DAI_{total}^{1\_3}$ the value of the total DAI in DCI format 1\_3 scheduling PDSCH receptions on more than one cells in PDCCH monitoring occasion $o$ according to Table 9.1.3-1. The UE assumes a same value of total DAI in all DCI formats 1\_3 in PDCCH monitoring occasion $o$ that schedule more than one PDSCH receptions on respective more than one serving cells from a set of serving cells. + +The UE determines the $N_{ACK}$ , for a total number of HARQ-ACK information bits in the second Type-2 HARQ-ACK sub-codebook according to the following pseudo-code. + +Set $N_{cells}$ to the maximum number of serving cells in *ScheduledCell-ListDCI-1-3* of a set of serving cells provided by *MC-DCI-SetofCells*, across the number of sets of serving cells, that can be scheduled PDSCH receptions by DCI format 1\_3 + +Set $N_{TBs}$ to the maximum total number of TBs in PDSCH receptions that can be scheduled by a DCI format 1\_3 over more than one serving cells in a set of serving cells across the number of sets of serving cells + +Set $N_{sets}$ to the number of sets of serving cells *MC-DCI-SetofCells* in a PUCCH group + +Set $s$ to index of sets of serving cells, + +Set $c$ to the index of a serving cell, in a set of indexes of serving cells arranged in ascending order, from the set of serving cells, + +Set $o$ – PDCCH monitoring occasion index for detection of a DCI format 1\_3 scheduling PDSCH receptions on serving cells from a set of serving cells: lower index corresponds to earlier PDCCH monitoring occasion + +Set $N_{ACK} = 0$ + +Set $s = 0$ + +Set $c = 0$ + +Set $o = 0$ + +Set $N_{PDCCH}$ to the number of PDCCH monitoring occasions + +while $s < N_{sets}$ + +if *harq-ACK-SpatialBundlingPUCCH* is not provided, + +while $o < N_{PDCCH}$ + +if there are more than one PDSCHs on respective more than one serving cells from the set of serving cells associated with PDCCH in PDCCH monitoring occasion $o$ + +if $DAI_{total}^{1\_3} > 0$ + +; + +end if + +; + +if $DAI_{1\_3} > 0$ + +; + +else + +; + +end if + +; + +``` + +; +while + if the UE is scheduled PDSCH reception on serving cell , if any, of set + if maxNrofCodeWordsScheduledByDCI is 2 for serving cell , if any, of set + = HARQ-ACK information bit corresponding to the first transport block of this cell + = HARQ-ACK information bit corresponding to the second transport block of this cell + ; + else + = HARQ-ACK information bit corresponding to the transport block of this cell + ; + end if +end if +; +end while +while + = NACK; + ; +end while +; +end if +; +end while +else +while + if there are more than one PDSCHs providing a transport block for a HARQ process with enabled HARQ-ACK information on respective more than one serving cells from the set of serving cells associated with PDCCH in PDCCH monitoring occasion + if + ; + end if + ; + if + ; + else + ; + end if + +``` + +``` +; +; +while + if the UE is scheduled PDSCH reception for transport blocks with enabled HARQ-ACK + information on serving cell , if any, of set + if maxNrofCodeWordsScheduledByDCI is 2 for serving cell + if the PDSCH reception provides two transport blocks + = binary AND operation of the HARQ-ACK information bits corresponding to the first + and second transport blocks of this cell + else + = HARQ-ACK information bit corresponding to the first transport block of this cell + end if + else + = HARQ-ACK information bit of this cell + end if + ; +end if +; +end while +while + = NACK; + ; +end while +; +end if +; +end while +end if +; +end while +; +if UE does not set and +; +end if +; +if +``` + +``` + +; +end if +if harq-ACK-SpatialBundlingPUCCH is not provided, + +else + +end if +for any . + +``` + +If *and*, for obtaining a PUCCH transmission power as described in clause 7.2.1, the UE determines , where is the value of for the first Type-2 HARQ-ACK sub-codebook and is the value of for the second Type-2 HARQ-ACK sub-codebook that is determined as + +where + +- in the following + - a DCI format 1\_3 schedules more than one PDSCH receptions providing transport blocks with enabled HARQ-ACK information + - a dormancy indication is considered as a PDSCH reception providing a single transport block with enabled HARQ-ACK information +- is the value of the total DAI field in a last DCI format 1\_3 the UE detects in a last PDCCH monitoring occasion within the PDCCH monitoring occasions where the UE detects at least one DCI format 1\_3. if the UE does not detect any DCI format 1\_3 in any of the PDCCH monitoring occasions. +- is the total number of DCI format 1\_3 that the UE detects within the PDCCH monitoring occasions for the set of serving cells. if the UE does not detect any DCI format 1\_3 associated with scheduling on set of serving cells in any of the PDCCH monitoring occasions. +- if *harq-ACK-SpatialBundlingPUCCH* is not provided; otherwise, . +- is + - the number of transport blocks, in PDSCH receptions not overlapping with an UL symbol indicated by *tdd-UL-DL-ConfigurationCommon* or by *tdd-UL-DL-ConfigurationDedicated* if provided, associated with a DCI format 1\_3 that the UE detects in PDCCH monitoring occasion for set of serving cells, if *harq-ACK-SpatialBundlingPUCCH* is not provided + - the number of more than one PDSCHs, not overlapping with an UL symbol indicated by *tdd-UL-DL-ConfigurationCommon* or by *tdd-UL-DL-ConfigurationDedicated* if provided, scheduled by a DCI format 1\_3 that the UE detects in PDCCH monitoring occasion for set of serving cells, if *harq-ACK-SpatialBundlingPUCCH* is provided + +**Table 9.1.3-1: Value of counter DAI for and of total DAI** + +| DAI MSB, LSB | or | Number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH transmission(s) associated with PDCCH or PDCCH generating a HARQ-ACK information bit without scheduling a PDSCH reception or providing TCI state update is present, or number of PDCCH monitoring occasions associated with PDCCH for scheduling PDSCH receptions on more than one cells, denoted as and | +|--------------|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0,0 | 1 | | +| 0,1 | 2 | | +| 1,0 | 3 | | +| 1,1 | 4 | | + +**Table 9.1.3-1A: Value of counter DAI for** + +| DAI | | Number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH transmission(s) associated with PDCCH or PDCCH generating a HARQ-ACK information bit without scheduling a PDSCH reception or providing TCI state update is present, denoted as $n$ and | +|-----|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | 1 | | +| 1 | 2 | | + +#### 9.1.3.2 Type-2 HARQ-ACK codebook in physical uplink shared channel + +In this clause, a DAI field is either the one corresponding to unicast HARQ-ACK information and associated PDSCH receptions or DCI formats, or is the one corresponding to multicast HARQ-ACK information and associated PDSCH receptions or DCI formats, as described in [5, TS 38.212]. + +If a UE would multiplex HARQ-ACK information in a PUSCH transmission that is not scheduled by a DCI format or is scheduled by a DCI format that does not include a DAI field, then + +- if the UE has not received any PDCCH within the monitoring occasions for DCI formats scheduling PDSCH receptions, or providing a DCI format having associated HARQ-ACK information without scheduling a PDSCH reception, on any serving cell and the UE does not have HARQ-ACK information in response to a SPS PDSCH reception to multiplex in the PUSCH, as described in clause 9.1.3.1, the UE does not multiplex HARQ-ACK information in the PUSCH transmission; +- else, the UE generates the HARQ-ACK codebook as described in clause 9.1.3.1, except that *harq-ACK-SpatialBundlingPUCCH* is replaced by *harq-ACK-SpatialBundlingPUSCH*. + +If a UE multiplexes HARQ-ACK information in a PUSCH transmission that is scheduled by a DCI format that includes a DAI field, the UE generates the HARQ-ACK codebook as described in clause 9.1.3.1, with the following modifications: + +- For the pseudo-code for the HARQ-ACK codebook generation in clause 9.1.3.1, after the completion of the $n$ and loops, the UE sets $n$ where $n$ is the value of the DAI field according to Table 9.1.3-2 +- if the UE multiplexes HARQ-ACK information associated with more than one G-RNTIs for multicast or G-CS-RNTIs, the value of the DAI field is applicable to each of the more than one G-RNTIs for multicast or each of the G-CS-RNTIs. +- For the case of first and second HARQ-ACK sub-codebooks, the DCI format includes a first DAI field corresponding to the first HARQ-ACK sub-codebook and a second DAI field corresponding to the second HARQ-ACK sub-codebook +- *harq-ACK-SpatialBundlingPUCCH* is replaced by *harq-ACK-SpatialBundlingPUSCH*. + +If a UE is not provided *PDSCH-CodeBlockGroupTransmission* and the UE is scheduled for a PUSCH transmission by DCI format that includes a DAI field for unicast PDSCH receptions with value $n$ and the UE has not received any PDCCH within the monitoring occasions for a unicast DCI format scheduling PDSCH receptions providing transport blocks with enabled HARQ-ACK information or having associated HARQ-ACK information without scheduling PDSCH receptions on any serving cell, and the UE does not have HARQ-ACK information in response to a SPS PDSCH reception to multiplex in the PUSCH as described in clause 9.1.3.1, the UE does not multiplex HARQ-ACK information associated with unicast DCI format and HARQ-ACK information for SPS PDSCH reception in the PUSCH transmission. + +If a UE is provided *PDSCH-CodeBlockGroupTransmission* and the UE is scheduled for a PUSCH transmission by DCI format that includes a DAI field for unicast PDSCH receptions with first value $n$ or with second value $n$ and the UE has not received any PDCCH within the monitoring occasions for a unicast DCI format scheduling PDSCH reception providing a transport block with enabled HARQ-ACK information or having associated HARQ-ACK information without scheduling PDSCH reception on any serving cell, and the UE does not have HARQ-ACK information in response to a SPS PDSCH reception to multiplex in the PUSCH, as described in clause 9.1.3.1, the UE does not multiplex HARQ-ACK information associated with unicast DCI format and HARQ-ACK information for SPS PDSCH reception for the first sub-codebook or for the second sub-codebook, respectively, in the PUSCH transmission. + +If a UE is scheduled for a PUSCH transmission by DCI format that includes a DAI field for multicast PDSCH receptions with value $n$ and the UE has not received any PDCCH within the monitoring occasions for a multicast DCI + +format scheduling PDSCH reception providing a transport block with enabled HARQ-ACK information or having associated HARQ-ACK information without scheduling PDSCH receptions on any serving cell, to multiplex in the PUSCH as described in clause 9.1.3.1, the UE does not multiplex multicast HARQ-ACK information associated with a multicast DCI format in the PUSCH transmission. + +**Table 9.1.3-2: Value of DAI** + +| DAI
MSB, LSB | | Number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH transmission(s) associated with PDCCH or PDCCH indicating SPS PDSCH release or providing TCI state update or DCI format 1_1 or DCI format 1_3 indicating SCell dormancy without scheduling a PDSCH reception is present, or number of PDCCH monitoring occasions associated with PDCCH for scheduling PDSCH receptions on more than one cells, denoted as $n$ and | +|-----------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0,0 | 1 | | +| 0,1 | 2 | | +| 1,0 | 3 | | +| 1,1 | 4 | | + +#### 9.1.3.3 Type-2 HARQ-ACK codebook grouping and HARQ-ACK retransmission + +If a UE is provided *pdsch-HARQ-ACK-Codebook-r16*, the UE determines HARQ-ACK information for multiplexing in a PUCCH transmission occasion according to the following procedure. + +Set $n_{\text{feedback}}$ to the value of a PDSCH group index field in a last DCI format that provides a value of $n_{\text{feedback}}$ and indicates a PUCCH transmission occasion. + +Set $n_{\text{pucch}}$ to denote a PUCCH transmission occasion for multiplexing HARQ-ACK information + +Set $n_{\text{feedback\_timing}}$ to the value of a PDSCH-to-HARQ\_feedback timing field, if any, in a DCI format providing a value of + +- If the DCI format does not include a PDSCH-to-HARQ\_feedback timing field, set $n_{\text{feedback\_timing}}$ to the value provided by *dl-DataToUL-ACK* or *dl-DataToUL-ACK-r16* + +Set $n_{\text{new\_feedback\_indicator}}$ to the value of the New feedback indicator field in the last DCI format providing the value of $n_{\text{new\_feedback\_indicator}}$ if the New feedback indicator field includes 1 bit, or to the MSB of the New feedback indicator field in the last DCI format providing the value of $n_{\text{new\_feedback\_indicator}}$ if the New feedback indicator field includes 2 bits + +Set $n_{\text{new\_feedback\_indicator\_lsb}}$ to a value of the LSB of the New feedback indicator field in the last DCI format providing the value of $n_{\text{new\_feedback\_indicator\_lsb}}$ if the New feedback indicator field includes 2 bits, or to 0 otherwise + +Set $n_{\text{total\_dai}}$ to the value of a total DAI field for group $n_{\text{feedback}}$ in the last DCI format providing the value of + +- If $n_{\text{feedback}}$ and the UE detects a DCI format that does not include a PDSCH group index field in a PDCCH reception that is after the PDCCH reception for the last DCI format detection providing the value of $n_{\text{feedback}}$ and indicating a same slot for a PUCCH transmission occasion, set $n_{\text{total\_dai}}$ + +Set $n_{\text{g}}$ to the value of a number of requested PDSCH group(s) field in the last DCI format providing the value of $n_{\text{g}}$ + +A UE does not expect to detect DCI formats with respective + +- Number of requested PDSCH group(s) field values of 0, and +- PDSCH-to-HARQ\_feedback timing field values that indicate a same PUCCH transmission occasion, and +- PDSCH group index field values that are different + +Generate first HARQ-ACK information for PUCCH transmission occasion $n_{\text{pucch}}$ in a slot, as described in clause 9.1.3.1, where + +- the first HARQ-ACK information corresponds only to detections of DCI formats each providing a same value of $n_{\text{feedback}}$ , of $n_{\text{pucch}}$ , and to detections of DCI formats that do not provide a value of $n_{\text{feedback}}$ and $n_{\text{pucch}}$ and are associated with a same value of $n_{\text{feedback\_timing}}$ , and at least one of the DCI formats providing a value of $n_{\text{feedback}}$ indicating the slot +- at least one of the DCI formats provides a value + +- corresponds to a PDCCH monitoring occasion, where the UE detects a DCI format that provides a value of $n_{PUCCH}$ or is associated with a value of $n_{PUCCH}$ , that is the first PDCCH monitoring occasion after a PDCCH monitoring occasion where the UE detects another DCI format that provides a value different than $n_{PUCCH}$ + +The generation of the first HARQ-ACK information for PUCCH transmission occasion in a slot, as described in clause 9.1.3.1, excludes the generation of HARQ-ACK information for SPS PDSCH receptions. + +If $n_{PUCCH}$ , generate second HARQ-ACK information for PUCCH transmission occasion in a slot, as described in clause 9.1.3.1, where + +- the second HARQ-ACK information corresponds to detections of DCI formats each providing a same value of $n_{PUCCH}$ , of $n_{PUCCH}$ and to detections of DCI formats that do not provide a value of $n_{PUCCH}$ , of $n_{PUCCH}$ , but are associated with a same value of $n_{PUCCH}$ , of $n_{PUCCH}$ +- at least one of the DCI formats provides a $n_{PUCCH}$ value +- corresponds to a PDCCH monitoring occasion, where the UE detects a DCI format that provides a value of $n_{PUCCH}$ or that is associated with a value of $n_{PUCCH}$ , that is the first PDCCH monitoring occasion after a PDCCH monitoring occasion where the UE detects another DCI format that provides a value different than $n_{PUCCH}$ +- the PUCCH transmission occasion is a last one for multiplexing second HARQ-ACK information and it is not after PUCCH transmission occasion +- if, after the completion of the $n_{PUCCH}$ and $n_{PUCCH}$ loops for the pseudo-code for the second HARQ-ACK codebook generation in clause 9.1.3.1, set $n_{PUCCH}$ . If the UE is provided *PDSCH-CodeBlockGroupTransmission* for $n_{PUCCH}$ serving cells, set $n_{PUCCH}$ for both sub-codebooks before appending the second sub-codebook to the first sub-codebook. + +If $n_{PUCCH}$ and $n_{PUCCH}$ , generate second HARQ-ACK information as described in clause 9.1.3.1 by setting $n_{PUCCH}$ and, after the completion of the $n_{PUCCH}$ and $n_{PUCCH}$ loops for the pseudo-code for the second HARQ-ACK codebook generation in clause 9.1.3.1, setting $n_{PUCCH}$ . + +The generation of the second HARQ-ACK information for PUCCH transmission occasion in a slot, as described in clause 9.1.3.1, excludes the generation of HARQ-ACK information for SPS PDSCH receptions. + +If, the UE + +includes only the first HARQ-ACK information for multiplexing in PUCCH transmission occasion + +elseif + +if $g = 1$ + +appends the first HARQ-ACK information to the second HARQ-ACK information for multiplexing in PUCCH transmission occasion + +else + +append the second HARQ-ACK information to the first HARQ-ACK information for multiplexing in PUCCH transmission occasion + +end if + +end if + +The UE appends the HARQ-ACK information corresponding to SPS PDSCH receptions, if any, as described in clause 9.1.3.1, after the first and second, if any, HARQ-ACK information. + +If the HARQ-ACK information is multiplexed in a PUSCH transmission, the HARQ-ACK information is determined as + +- for multiplexing in PUCCH transmission occasion, if the PUSCH transmission is not scheduled by a DCI format or is scheduled by a DCI format that does not include a DCI field with value $n_{PUCCH}$ +- for multiplexing in PUCCH transmission occasion, if the PUSCH transmission is scheduled by a DCI format without *ul-TotalDAI-Included* configured except that for PDSCH group, the DCI field with value $n_{PUCCH}$ in the DCI format is used after the completion of the $n_{PUCCH}$ and $n_{PUCCH}$ loops for the pseudo-code for the HARQ-ACK codebook generation in clause 9.1.3.1, and when the HARQ-ACK information multiplexed in the PUCCH transmission occasion does not include HARQ-ACK information for PDSCH group + +- for multiplexing in PUCCH transmission occasion , if the PUSCH transmission is scheduled by a DCI format without *ul-TotalDAI-Included* configured except that for PDSCH group , the DCI field with value in the DCI format is used after the completion of the and loops for the pseudo-code for the HARQ-ACK codebook generation in clause 9.1.3.1, and when the HARQ-ACK information multiplexed in the PUCCH transmission occasion includes HARQ-ACK information for PDSCH groups and +- for multiplexing in PUCCH transmission occasion , if the PUSCH transmission is scheduled by a DCI format without *ul-TotalDAI-Included* configured except that for PDSCH group , the DCI field with value in the DCI format is used after the completion of the and loops for the pseudo-code for the HARQ-ACK codebook generation in clause 9.1.3.1, and when the UE has not detected any DCI format scheduling PDSCH receptions, and the UE has not detected any DCI format with a request for HARQ-ACK information for any PDSCH group +- for multiplexing in PUCCH transmission occasion , if the PUSCH transmission is scheduled by a DCI format with *ul-TotalDAI-Included* configured except that MSBs of the DCI field with value in the DCI format are used for PDSCH group , and LSBs of DCI field with value in the DCI format are used for PDSCH group , after the completion of the and loops for the pseudo-code for the HARQ-ACK codebook generation in clause 9.1.3.1. + +If a UE is scheduled a PUSCH transmission by DCI format 0\_1 having a DAI field value for a PDSCH group index, and the UE has not detected any DCI format scheduling PDSCH receptions for the PDSCH group index, and the UE has not detected any DCI format with a request for HARQ-ACK information for the PDSCH group index, the UE does not multiplex HARQ-ACK information in the PUSCH transmission for the PDSCH group index. + +If a UE detects DCI formats with respective PDSCH-to-HARQ\_feedback timing field values indicating a same PUCCH transmission occasion and none of the DCI formats that the UE detects after a last PUCCH transmission occasion for includes a New feedback indicator field for , and at least one of the DCI formats is DCI format 1\_0, the UE generates HARQ-ACK information only for PDSCH receptions scheduled by detections of DCI format 1\_0 and SPS PDSCH releases indicated by detections of DCI format 1\_0, as described in clause 9.1.3.1 or 9.1.3.2 for multiplexing in the PUCCH transmission occasion. + +If a DCI format indicating a slot for a PUCCH transmission occasion does not include a New feedback indicator field, a PDSCH reception scheduled by the DCI format or a SPS PDSCH release indicated by the DCI format is associated with PDSCH group 0 and a value of $h(g)$ associated with the DCI format is set only if $h(g)$ is provided by another DCI format that provides a value of $h(g)$ for PDSCH group 0 and indicates the slot for the PUCCH transmission occasion. + +For PUCCH transmission occasion , the UE determines a PUCCH or a PUSCH transmission to multiplex the HARQ-ACK information according to the procedures in clauses 9.2.3 and 9.2.5. + +If , the UE determines a number of HARQ-ACK information bits for group and a number of HARQ-ACK information bits for group as described in clause 9.1.3.1 where is included in and, if and , the UE determines by setting . For obtaining a PUCCH transmission power, if , ; else, . + +### 9.1.4 Type-3 HARQ-ACK codebook determination + +If a UE is provided *pdsch-HARQ-ACK-OneShotFeedback* or *pdsch-HARQ-ACK-EnhType3ToAddModList*, the UE determines HARQ-ACK information bits, for a total number of HARQ-ACK information bits, of a Type-3 HARQ-ACK codebook according to the following procedure. If the UE is provided *pdsch-HARQ-ACK-EnhType3ToAddModList* and a DCI format scheduling PDSCH reception and triggering the Type-3 HARQ-ACK codebook includes an enhanced Type 3 codebook indicator field that provides a value for *pdsch-HARQ-ACK-EnhType3Index*, the UE determines a size of a set of indicated serving cells and a size of a set of indicated HARQ process numbers for each indicated serving cell and each indicated HARQ process number from the entry in *pdsch-HARQ-ACK-EnhType3ToAddModList* corresponding to the *pdsch-HARQ-ACK-EnhType3Index* value. Each bit from MSB to LSB provided by *perCC* corresponds to a serving cell in ascending order of serving cell index, where value '1' or value '0' indicate HARQ-ACK for the corresponding serving cell is included or not included in the Type 3 HARQ-ACK codebook, respectively. Each bit string provided by *perHARQ* corresponds to a serving cell in ascending order of serving cell index, and each bit from MSB to LSB within a bit string corresponds to a HARQ process number on a corresponding serving cell in ascending order of HARQ process number, where value '1' or value '0' indicate HARQ-ACK for the corresponding HARQ process number on the corresponding serving cell is included or not included in the Type 3 HARQ-ACK codebook, respectively. If the DCI format does not include the enhanced Type 3 codebook indicator field, the *pdsch-HARQ-ACK-EnhType3Index* value is zero. + +Set to the number of configured serving cells or, when applicable, to . + +Set to the value of *nrofHARQ-ProcessesForPDSCH* or *nrofHARQ-ProcessesForPDSCH-v1700* for serving cell *c*, if provided; else, set to 0. When applicable, set to 0. + +Set to the maximum value of *maxNrofCodeWordsScheduledByDCI* in *PDSCH-config* and *PDSCH-configMulticast* for serving cell *c* if *harq-ACK-SpatialBundlingPUCCH* is provided and *c*, or if *harq-ACK-SpatialBundlingPUCCH* is not provided, or if *maxCodeBlockGroupsPerTransportBlock* is provided for serving cell *c*; else, set to 1. + +Set to the number of HARQ-ACK information bits per TB for PDSCH receptions on serving cell *c* as described in clause 9.1.1 if *maxCodeBlockGroupsPerTransportBlock* is provided for serving cell *c* and *pdsch-HARQ-ACK-OneShotFeedbackCBG* or *pdsch-HARQ-ACK-EnhType3CBG* corresponding to the *pdsch-HARQ-ACK-EnhType3Index* value is provided; else, set to 0. A UE provided with *pdsch-HARQ-ACK-OneShotFeedbackCBG* or *pdsch-HARQ-ACK-EnhType3CBG* does not expect to be provided with different values of *maxCodeBlockGroupsPerTransportBlock* for different priority indexes in *pdsch-CodeBlockGroupTransmissionList* for serving cell *c*. + +Set if *pdsch-HARQ-ACK-OneShotFeedbackNDI* or *pdsch-HARQ-ACK-EnhType3NDI* is provided; else set to 0. + +Set – serving cell index in the set of serving cells + +Set – HARQ process number index in the set of numbers of HARQ processes + +Set – TB index + +Set – CBG index + +Set + +while + +while + +if *downlinkHARQ-FeedbackDisabled* is not provided, or is provided and indicates enabled HARQ-ACK information for *c*, or *harq-feedbackEnablingforSPSactive* is provided and enabled and corresponds to a transport block in a first SPS PDSCH reception after an activation of SPS PDSCH receptions + +if + +if + +while + +while + += HARQ-ACK information bit for CBG of TB for HARQ process number index in the set of numbers of HARQ processes of serving cell *c*, if any; else, + +end while + += NDI value indicated in the DCI format corresponding to the HARQ-ACK information bit(s) for TB for HARQ process number index in the set of numbers of HARQ processes on serving cell *c*, if any; else, + +end while + +else + +while + += HARQ-ACK information bit for TB for HARQ process index in the set of numbers of HARQ processes of serving cell, if any; else, + += NDI value indicated in the DCI format corresponding to the HARQ-ACK information bit(s) for TB for HARQ process number index in the set of numbers of HARQ processes on serving cell, if any; else, + +end while + +end if + +else + +if + +while + +if UE has obtained HARQ-ACK information for TB for HARQ process number index in the set of numbers of HARQ processes on serving cell corresponding to a PDSCH reception and has not reported the HARQ-ACK information corresponding to the PDSCH reception + +while + += HARQ-ACK information bit for CBG of TB for HARQ process number index in the set of numbers of HARQ processes of serving cell + +end while + +else + +while + +end while + +end if + +end while + +else + +while + +if UE has obtained HARQ-ACK information for TB for HARQ process number index in the set of numbers of HARQ processes on serving cell corresponding to a PDSCH reception and has not reported the HARQ-ACK information corresponding to the PDSCH reception + +if *harq-ACK-SpatialBundlingPUCCH* is not provided + += HARQ-ACK information bit for TB for HARQ process number index in the set of numbers of HARQ processes of serving cell + +else + += binary AND operation of the HARQ-ACK information bits corresponding to first and second transport blocks for HARQ process number index in the set of numbers of HARQ processes of serving cell. If the UE receives one transport block, the UE assumes ACK for the second transport block + +end if + +else + +end if + +end while + +end if + +end if + +end if + +end while + +end while + +If, when a UE receives a PDSCH with one transport block, the HARQ-ACK information is associated with the first transport block. + +If a UE receives a SPS PDSCH, or a PDSCH that is scheduled by a DCI format that does not support CBG-based PDSCH receptions for a serving cell, and if *maxCodeBlockGroupsPerTransportBlock* is provided for serving cell, and *pdsch-HARQ-ACK-OneShotFeedbackCBG* or *pdsch-HARQ-ACK-EnhType3CBG* corresponding to the *pdsch-HARQ-ACK-EnhType3Index* value is provided, the UE repeats times the HARQ-ACK information for the transport block, if any, in the PDSCH. + +If a UE detects a DCI format that includes a One-shot HARQ-ACK request field with value 1, the UE determines a PUCCH or a PUSCH to multiplex a Type-3 HARQ-ACK codebook for transmission in a slot as described in clauses 9.2.3 and 9.2.5. If the UE is provided a periodic cell switching pattern for PUCCH transmissions by *pucch-sCellPattern*, the UE determines the slot and a corresponding cell based on the periodic cell switching pattern as described in clause 9.A. The UE multiplexes only the Type-3 HARQ-ACK codebook in the PUCCH or the PUSCH for transmission in the slot. If the UE is provided *pdsch-HARQ-ACK-EnhType3ToAddModList*, the UE expects that HARQ-ACK information in a Type-1 or Type-2 HARQ-ACK codebook in a slot is associated with HARQ process(es) of the Type-3 HARQ-ACK codebook in the slot. + +If + +- a UE detects a DCI format that includes a One-shot HARQ-ACK request field with value 1, and +- the CRC of the DCI is scrambled by a C-RNTI or an MCS-C-RNTI, and + +if for one or more serving cells + +- *resourceAllocation* = *resourceAllocationType0* and all bits of the frequency domain resource assignment field in the DCI format are equal to 0, or +- *resourceAllocation* = *resourceAllocationType1* and all bits of the frequency domain resource assignment field in the DCI format are equal to 1, or +- *resourceAllocation* = *dynamicSwitch* and all bits of the frequency domain resource assignment field in the DCI format are equal to 0 or 1 + +the DCI format provides a request for a Type-3 HARQ-ACK codebook report and does not schedule a PDSCH reception on the one or more serving cells. If the UE is provided *pdsch-HARQ-ACK-EnhType3ToAddModList* and the DCI format includes an enhanced Type 3 codebook indicator field that provides a value for *pdsch-HARQ-ACK-EnhType3Index*, the UE determines a size of a set of indicated serving cells and a size of a set of indicated HARQ process numbers for each indicated serving cell from the entry in *pdsch-HARQ-ACK-EnhType3ToAddModList* corresponding to the *pdsch-HARQ-ACK-EnhType3Index* value. If the DCI format does not include the enhanced Type 3 codebook indicator field, the *pdsch-HARQ-ACK-EnhType3Index* value is provided by the value of + +- the MCS field for transport block 1 if the DCI format is DCI format 1\_1, +- the MCS field if the DCI format is DCI format 1\_2, +- the MCS field for transport block 1 of a serving cell with smallest index among the one or more serving cells if the DCI format is DCI format 1\_3. + +The UE is expected to provide HARQ-ACK information in response to the request for the Type-3 HARQ-ACK codebook after symbols from the last symbol of a PDCCH providing the DCI format, where the value of is provided in clause 10.2 by replacing "SPS PDSCH release" with "DCI format". + +If a UE multiplexes HARQ-ACK information in a PUSCH transmission, the UE generates the HARQ-ACK codebook as described in this clause except that *harq-ACK-SpatialBundlingPUCCH* is replaced by *harq-ACK-SpatialBundlingPUSCH*. + +### 9.1.5 HARQ-ACK codebook retransmission + +With reference to slots of PUCCH transmissions on the primary cell and for Type-1 or Type-2 HARQ-ACK codebooks, a UE that transmitted or would transmit a PUCCH or a PUSCH with a first HARQ-ACK codebook in slot can be indicated by a DCI format with CRC scrambled by a C-RNTI or a MCS-C-RNTI that does not schedule a PDSCH reception [4, TS 38.212] and is received in a PDCCH ending in slot , to transmit a PUCCH with the first HARQ-ACK codebook in slot , where slot is after slot . The UE determines and a resource for the PUCCH transmission as described in clauses 9.2.3 and 9.2.5. If the UE is provided a periodic cell switching pattern for PUCCH transmissions by *pucch-sSCellPattern*, the UE further determines a corresponding cell based on the periodic cell switching pattern as described in clause 9.A. + +If the HARQ-ACK retransmission indicator field value in a DCI format is '1', the UE determines slot as where is determined by a one-to-one mapping in ascending order among the values from -7 to 24 and the values of + +- the MCS field for transport block 1 if the DCI format is DCI format 1\_1 +- the MCS field if the DCI format is DCI format 1\_2 +- the MCS field for transport block 1 for a serving cell if the DCI format is DCI format 1\_3, where the serving cell is the one with smallest index that has + - *resourceAllocation* = *resourceAllocationType0* and all bits of the corresponding block of the frequency domain resource assignment field equal to 0, or + - *resourceAllocation* = *resourceAllocationType1* and all bits of the corresponding block of the frequency domain resource assignment field equal to 1, or + +- *resourceAllocation* = *dynamicSwitch* and all bits of the corresponding block of the frequency domain resource assignment field equal to 0 or 1 + +If the DCI format includes a priority indicator field having a value, a priority value of first HARQ-ACK information in the first HARQ-ACK codebook is same as the value of the priority indicator field; otherwise, the priority value of the first HARQ-ACK information is zero. + +If a UE + +- is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with a value of 0 for first CORESETs on active DL BWPs of serving cells, and +- is provided *coresetPoolIndex* with a value of 1 for second CORESETs on active DL BWPs of the serving cells, and +- is provided *ackNackFeedbackMode* = *separate* + +the first HARQ-ACK codebook is associated with the first CORESETs or with the second CORESETs, as described in clause 9, when the UE receives the PDCCH providing the DCI format in a CORESET from the first CORESETs or from the second CORESETs, respectively. + +If the UE would also multiplex in the PUCCH transmission in slot *n* a second HARQ-ACK codebook with second HARQ-ACK information of same priority value as for the first HARQ-ACK information in the first HARQ-ACK codebook, the UE appends the first HARQ-ACK codebook to the second HARQ-ACK codebook. The UE determines to multiplex the second HARQ-ACK information in the PUCCH transmission in slot *n* as described in clause 9.2.3. *n* is the total number of the first HARQ-ACK information bits and the second HARQ-ACK information bits if any. + +If the UE performs a procedure for deferring third HARQ-ACK information for SPS PDSCH receptions to slot *n*, as described in clause 9.2.5.4, and the third HARQ-ACK information has same priority value as a priority value indicated by the DCI format triggering the PUCCH transmission in slot *n*, the UE multiplexes in the PUCCH transmission in slot *n* the first HARQ-ACK information with the priority value that results in slot *n* according to the procedure in this clause, by appending the third HARQ-ACK information to the first HARQ-ACK information. If the UE would also multiplex in the PUCCH transmission in slot *n* the second HARQ-ACK information with the priority value, the UE appends the first HARQ-ACK information followed by the third HARQ-ACK information to the second HARQ-ACK information. *n* is the total number of the first HARQ-ACK information bits, the second HARQ-ACK information bits if any and the third HARQ-ACK information bits if any. + +If in slot *n* the UE would transmit a first PUCCH with first HARQ-ACK information over more than one slot and a second PUCCH with second HARQ-ACK information over one or more slots, where the first and second HARQ-ACK information have same priority value, the UE multiplexes in the PUCCH transmission in slot *n* one of + +- the first HARQ-ACK information if the first PUCCH starts at an earlier slot than the second PUCCH, or +- the second HARQ-ACK information if the second PUCCH starts at an earlier slot than the first PUCCH. + +If, the UE determines a number of HARQ-ACK information bits for obtaining a transmission power for a PUCCH, as described in clause 7.2.1, as where + +- *nACK,1* is the number of HARQ-ACK information bits that the UE determines as described in clause 9.1.2.1 or 9.1.3.1 for the first HARQ-ACK information bits, +- *nACK,2* is the number of HARQ-ACK information bits, if any, that the UE determines as described in clause 9.1.2.1 or 9.1.3.1 for the second HARQ-ACK information bits, +- *nACK,3* is determined as described in clause 9.1.2.1 or 9.1.3.1 for the third HARQ-ACK information bits for SPS PDSCH receptions deferred to slot *n*, if any. + +## 9.2 UCI reporting in physical uplink control channel + +UCI types reported in a PUCCH include HARQ-ACK information, SR, LRR, and CSI. UCI bits include HARQ-ACK information bits, if any, SR information bits, if any, LRR information bit, if any, and CSI bits, if any. The HARQ-ACK information bits correspond to a HARQ-ACK codebook as described in clause 9.1. For the remaining of this clause, any reference to SR is applicable for SR and/or for LRR. + +A UE may transmit one or two PUCCHs on a serving cell in different symbols within a slot. When the UE transmits two PUCCHs in a slot and the UE is not provided *ackNackFeedbackMode = separate*, at least one of the two PUCCHs uses PUCCH format 0 or PUCCH format 2. + +If a UE is provided *ackNackFeedbackMode = separate*, the UE may transmit up to two PUCCHs with HARQ-ACK information in different symbols within a slot. + +In clauses 9.2.3, 9.2.5.1, 9.2.5.2 and 9.2.5.3, a UE assumes 11 CRC bits if a number of respective UCI bits is larger than or equal to 360; otherwise, the UE determines a number of CRC bits based on the number of respective UCI bits as described in [5, TS 38.212]. + +### 9.2.1 PUCCH Resource Sets + +If a UE does not have dedicated PUCCH resource configuration, provided by *PUCCH-ResourceSet* in *PUCCH-Config*, a PUCCH resource set is provided by *pucch-ResourceCommon* through an index to a row of Table 9.2.1-1 for transmission of HARQ-ACK information on PUCCH in an initial UL BWP of PRBs. For operation in FR2-2, *nrofPRBs* provided in *PUCCH-ConfigCommon* can also provide a number of RBs for the PUCCH resource set; otherwise . + +The PUCCH resource set includes sixteen resources, each corresponding to a PUCCH format, a first symbol, a duration, a PRB offset , and a cyclic shift index set for a PUCCH transmission. + +The UE transmits a PUCCH using frequency hopping if not provided *useInterlacePUCCH-PUSCH* in *BWP-UplinkCommon*; otherwise, the UE transmits a PUCCH without frequency hopping. + +An orthogonal cover code with index 0 is used for a PUCCH resource with PUCCH format 1 in Table 9.2.1-1 except when index 3, 7, or 11 is indicated by *pucch-ResourceCommon* and *useInterlacePUCCH-PUSCH* in *BWP-UplinkCommon* is provided. + +The UE transmits the PUCCH using the same spatial domain transmission filter as for a PUSCH transmission scheduled by a RAR UL grant as described in clause 8.3. + +If a UE is not provided any of *pdsch-HARQ-ACK-Codebook*, *pdsch-HARQ-ACK-Codebook-r16*, or *pdsch-HARQ-ACK-OneShotFeedback*, the UE generates at most one HARQ-ACK information bit. + +If the UE provides HARQ-ACK information in a PUCCH transmission in response to detecting a DCI format scheduling a PDSCH reception or having associated HARQ-ACK information without scheduling a PDSCH reception, the UE determines a PUCCH resource with index , , as , where is a number of CCEs in a CORESET of a PDCCH reception with the DCI format, as described in clause 10.1, is the index of a first CCE for the PDCCH reception, and is a value of the PUCCH resource indicator field in the DCI format. + +When the PDCCH reception by a UE includes first and second PDCCH candidates from respective first and second search space sets, as described in clause 10.1, the CORESET and are associated with the search space set having the smaller index. If + +- the first search space set has larger index than the second search space set and includes the first PDCCH candidate and a third PDCCH candidate that have same first CCE index and CCE aggregation levels 8 and 16, or 16 and 8, respectively, +- the second search space set includes the second PDCCH candidate that has same index and same CCE aggregation level as the first PDCCH candidate, and a fourth PDCCH candidate that has same index and same CCE aggregation level as the third PDCCH candidate, +- the CORESET associated with the first search space set has *cce-REG-MappingType = 'nonInterleaved'* and has duration of one symbol, and +- the second PDCCH candidate has different first CCE index than the fourth PDCCH candidate + +the UE determines from the PDCCH candidate with CCE aggregation level 16 among the second PDCCH candidate and the fourth PDCCH candidate. + +If and a UE is provided a PUCCH resource by *pucch-ResourceCommon* and is not provided *useInterlacePUCCH-PUSCH* in *BWP-UplinkCommon* + +- the UE determines the lowest PRB index of the PUCCH transmission in the first hop as $n_{PRB,0}$ and the lowest PRB index of the PUCCH transmission in the second hop as $n_{PRB,1}$ , where $n_{PRB,0}$ is the total number of initial cyclic shift indexes in the set of initial cyclic shift indexes +- the UE determines the initial cyclic shift index in the set of initial cyclic shift indexes as + +If $n_{PRB,0}$ and $n_{PRB,1}$ are provided by *pucch-ResourceCommon* and is not provided *useInterlacePUCCH-PUSCH* in *BWP-UplinkCommon* + +- the UE determines the lowest PRB index of the PUCCH transmission in the first hop as $n_{PRB,0}$ and the lowest PRB index of the PUCCH transmission in the second hop as $n_{PRB,1}$ +- the UE determines the initial cyclic shift index in the set of initial cyclic shift indexes as $(n_{PUCCH} - 8) \bmod N_{CS}$ + +If a UE is provided a PUCCH resource by *pucch-ResourceCommon* and is provided *useInterlacePUCCH-PUSCH* in *BWP-UplinkCommon* + +- the UE determines for the PUCCH resource an interlace index $n_{interlace}$ as where $n_{interlace}$ is a number of interlaces [4, TS 38.211] and $n_{interlace}$ is an interlace index offset and $n_{interlace}$ is as given in Table 9.2.1-1 +- the UE determines an initial cyclic shift index in a set of initial cyclic shift indexes as $n_{PUCCH}$ , where $n_{PUCCH}$ is the total number of initial cyclic shifts indexes in the set of initial cyclic shift indexes in Table 9.2.1-1 +- if *pucch-ResourceCommon* indicates + - index 0: the first symbol is 9 for a PUCCH resource with PUCCH format 0 if + - index 1 or 2: the first symbol is 9 for a PUCCH resource with PUCCH format 0 if + - index 3, 7, or 11: an orthogonal cover code with index 1 is used for a PUCCH resource with PUCCH format 1 if ; otherwise, an orthogonal cover code with index 0 is used for a PUCCH resource with PUCCH format 1 +- the UE does not expect *pucch-ResourceCommon* to indicate index 15 + +**Table 9.2.1-1: PUCCH resource sets before dedicated PUCCH resource configuration** + +| Index | PUCCH format | First symbol | Number of symbols | PRB offset | Set of initial CS indexes | +|-------|--------------|--------------|-------------------|------------|---------------------------| +| 0 | 0 | 12 | 2 | 0 | {0, 3} | +| 1 | 0 | 12 | 2 | 0 | {0, 4, 8} | +| 2 | 0 | 12 | 2 | 3 | {0, 4, 8} | +| 3 | 1 | 10 | 4 | 0 | {0, 6} | +| 4 | 1 | 10 | 4 | 0 | {0, 3, 6, 9} | +| 5 | 1 | 10 | 4 | 2 | {0, 3, 6, 9} | +| 6 | 1 | 10 | 4 | 4 | {0, 3, 6, 9} | +| 7 | 1 | 4 | 10 | 0 | {0, 6} | +| 8 | 1 | 4 | 10 | 0 | {0, 3, 6, 9} | +| 9 | 1 | 4 | 10 | 2 | {0, 3, 6, 9} | +| 10 | 1 | 4 | 10 | 4 | {0, 3, 6, 9} | +| 11 | 1 | 0 | 14 | 0 | {0, 6} | +| 12 | 1 | 0 | 14 | 0 | {0, 3, 6, 9} | +| 13 | 1 | 0 | 14 | 2 | {0, 3, 6, 9} | +| 14 | 1 | 0 | 14 | 4 | {0, 3, 6, 9} | +| 15 | 1 | 0 | 14 | | {0, 3, 6, 9} | + +If a UE has dedicated PUCCH resource configuration, the UE is provided by higher layers with one or more PUCCH resources. + +A PUCCH resource includes the following parameters: + +- a PUCCH resource index provided by *pucch-ResourceId* +- an index of the first PRB prior to frequency hopping or for no frequency hopping by *startingPRB*, if a UE is not provided *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated* + +- an index of the first PRB after frequency hopping by *secondHopPRB*, if a UE is not provided *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated* +- an indication for intra-slot frequency hopping by *intraSlotFrequencyHopping*, if a UE is not provided *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated* +- an index of a first interlace by *interlace0*, if a UE is provided *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated* +- if provided, an index of a second interlace by *interlace1*, if a UE is provided *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated* +- an index of an RB set by *rb-SetIndex*, if a UE is provided *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated* +- an indication for applying one or both of *TCI-State* or *TCI-UL-State* by *apply-IndicatedTCIState*, if provided +- a configuration for a PUCCH format provided by *format* + +For operation with shared spectrum channel access, the UE does not expect that two hops of a PUCCH transmission are in different RB sets. + +The UE expects that *useInterlacePUCCH-PUSCH* in *BWP-UplinkCommon* and *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated* are provided either in all UL BWPs or in none of the UL BWPs for a serving cell. + +If a UE is provided *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated*, the UE determines available RBs for PUCCH transmissions within the active UL BWP as the intersection of RBs corresponding to an interlace index provided by *interlace0* and, if provided, *interlace1*, and RBs of an RB set provided by *rb-SetIndex*. The intersection results in RBs in the first interlace and the UE expects that is either 10 or 11. If *interlace1* is provided, the intersection results in RBs in the second interlace and the UE expects that is either 10 or 11. + +If the *format* indicates *PUCCH-format0*, the PUCCH format configured for a PUCCH resource is PUCCH format 0, where the PUCCH resource also includes an index for an initial cyclic shift provided by *initialCyclicShift*, a number of symbols for a PUCCH transmission provided by *nrofSymbols*, a first symbol for the PUCCH transmission provided by *startingSymbolIndex*. For PUCCH transmission in FR2-2, the PUCCH resource can also include a number of PRBs provided by *nrofPRBs*; otherwise, . + +If the *format* indicates *PUCCH-format1*, the PUCCH format configured for a PUCCH resource is PUCCH format 1, where the PUCCH resource also includes an index for an initial cyclic shift provided by *initialCyclicShift*, a number of symbols for a PUCCH transmission provided by *nrofSymbols*, a first symbol for the PUCCH transmission provided by *startingSymbolIndex*, and an index for an orthogonal cover code by *timeDomainOCC*. For PUCCH transmission in FR2-2, the PUCCH resource can also include a number of PRBs provided by *nrofPRBs*; otherwise, . + +If the *format* indicates *PUCCH-format2* or *PUCCH-format3*, the PUCCH format configured for a PUCCH resource is PUCCH format 2 or PUCCH format 3, respectively, where the PUCCH resource also includes a number of PRBs provided by *nrofPRBs*, a number of symbols for a PUCCH transmission provided by *nrofSymbols*, and a first symbol for the PUCCH transmission provided by *startingSymbolIndex*. If a UE is provided by *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated*, and the *format* indicates *PUCCH-format2* or *PUCCH-format3* and *PUCCH-ResourceExt* is provided, the PUCCH resource also includes an index of a second interlace by *interlace1*, if provided; otherwise, if *interlace1* is not provided, the PUCCH resource also includes, if provided, an orthogonal cover code length by *occ-Length* and an orthogonal cover code index by *occ-Index*. If the *format* indicates *PUCCH-format3* and *PUCCH-ResourceExt* is provided, the UE assumes that the [4, TS 38.211] PRBs with the lowest indexes within the first, and if configured, second interlace are used for PUCCH transmission. + +If the *format* indicates *PUCCH-format4*, the PUCCH format configured for a PUCCH resource is PUCCH format 4, where the PUCCH resource also includes a number of symbols for a PUCCH transmission provided by *nrofSymbols*, an orthogonal cover code length by *occ-Length*, an orthogonal cover code index by *occ-Index*, and a first symbol for the PUCCH transmission provided by *startingSymbolIndex*. For PUCCH transmission in FR2-2, the PUCCH resource can also include a number of PRBs provided by *nrofPRBs*; otherwise, . + +If a UE is provided *subslotLengthForPUCCH* in a *PUCCH-Config*, the first symbol of a PUCCH resource provided by *PUCCH-ResourceSet* or *SPS-PUCCH-AN-List* in *PUCCH-Config* or by *n1PUCCH-AN* in *SPS-Config* for multiplexing HARQ-ACK in a PUCCH transmission is relative to the first symbol of the *subslotLengthForPUCCH* symbols [12, TS + +38.331]. For the remaining cases, the first symbol of a PUCCH resource is relative to the first symbol of a slot with symbols [4, TS 38.211]. + +A UE can be configured up to four sets of PUCCH resources in a *PUCCH-Config*. A PUCCH resource set is provided by *PUCCH-ResourceSet* and is associated with a PUCCH resource set index provided by *pucch-ResourceSetId*, with a set of PUCCH resource indexes provided by *resourceList* that provides a set of *pucch-ResourceId* used in the PUCCH resource set, and with a maximum number of UCI information bits the UE can transmit using a PUCCH resource in the PUCCH resource set provided by *maxPayloadSize*. For the first PUCCH resource set, the maximum number of UCI information bits is 2. A maximum number of PUCCH resource indexes for a set of PUCCH resources is provided by *maxNrofPUCCH-ResourcesPerSet*. The maximum number of PUCCH resources in the first PUCCH resource set is 32 and the maximum number of PUCCH resources in the other PUCCH resource sets is 8. + +If the UE transmits UCI information bits, that include HARQ-ACK information bits, the UE determines a PUCCH resource set to be + +- a first set of PUCCH resources with *pucch-ResourceSetId* = 0 if including 1 or 2 HARQ-ACK information bits and a positive or negative SR on one SR transmission occasion if transmission of HARQ-ACK information and SR occurs simultaneously, or +- a second set of PUCCH resources with *pucch-ResourceSetId* = 1, if provided by higher layers, if where is equal to *maxPayloadSize* if *maxPayloadSize* is provided for the PUCCH resource set with *pucch-ResourceSetId* = 1; otherwise is equal to 1706, or +- a third set of PUCCH resources with *pucch-ResourceSetId* = 2, if provided by higher layers, if where is equal to *maxPayloadSize* if *maxPayloadSize* is provided for the PUCCH resource set with *pucch-ResourceSetId* = 2; otherwise is equal to 1706, or +- a fourth set of PUCCH resources with *pucch-ResourceSetId* = 3, if provided by higher layers, if . + +If the UE is provided *SPS-PUCCH-AN-List* and transmits UCI information bits that include only HARQ-ACK information bits in response to one or more SPS PDSCH receptions and SR, if any, the UE determines a PUCCH resource to be + +- a PUCCH resource provided by *sps-PUCCH-AN-ResourceID* obtained from the first entry in *sps-PUCCH-AN-List* if including 1 or 2 HARQ-ACK information bits and a positive or negative SR on one SR transmission occasion if transmission of HARQ-ACK information and SR occurs simultaneously, or +- a PUCCH resource provided by *sps-PUCCH-AN-ResourceID* obtained from the second entry in *sps-PUCCH-AN-List*, if provided, if where is either provided by *maxPayloadSize* obtained from the second entry in *sps-PUCCH-AN-List* or is otherwise equal to 1706, or +- a PUCCH resource provided by *sps-PUCCH-AN-ResourceID* obtained from the third entry in *sps-PUCCH-AN-List*, if provided, if where is either provided by *maxPayloadSize* obtained from the third entry in *sps-PUCCH-AN-List* or is otherwise equal to 1706, or +- a PUCCH resource provided by *sps-PUCCH-AN-ResourceID* obtained from the fourth entry in *sps-PUCCH-AN-List*, if provided, if where is equal to 1706. + +### 9.2.2 PUCCH Formats for UCI transmission + +If a UE is not transmitting PUSCH, and the UE is transmitting UCI, the UE transmits UCI in a PUCCH using + +- PUCCH format 0 if + - the transmission is over 1 symbol or 2 symbols, + - the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK/SR bits) is 1 or 2 +- PUCCH format 1 if + - the transmission is over 4 or more symbols, + - the number of HARQ-ACK/SR bits is 1 or 2 +- PUCCH format 2 if + +- the transmission is over 1 symbol or 2 symbols, +- the number of UCI bits is more than 2 +- PUCCH format 3 if + - the transmission is over 4 or more symbols, + - the number of UCI bits is more than 2, + - the PUCCH resource does not include an orthogonal cover code, or the UE is provided *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated* +- PUCCH format 4 if + - the transmission is over 4 or more symbols, + - the number of UCI bits is more than 2, + - the PUCCH resource includes an orthogonal cover code and the UE is not provided *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated* + +A spatial setting for a PUCCH transmission by a UE is provided by + +- an indicated *TCI-State* or *TCI-UL-State*, if provided, as described in [6, TS 38.214]; +- *PUCCH-SpatialRelationInfo* if the UE is configured with a single value for *pucch-SpatialRelationInfoId*; +- as described in [11, TS 38.321], if the UE is provided multiple values for *PUCCH-SpatialRelationInfo*. The UE applies corresponding actions in [11, TS 38.321] and a corresponding setting for a spatial domain filter to transmit PUCCH in the first slot that is after slot *n* where *n* is the slot where the UE would transmit a PUCCH with HARQ-ACK information with ACK value corresponding to a PDSCH reception providing the *PUCCH-SpatialRelationInfo*, each slot consists of *numberOfSymbols* symbols as defined in [4, TS 38.211], and *scs* is the SCS configuration for the PUCCH + - If *PUCCH-SpatialRelationInfo* or the indicated *TCI-UL-State* provides *ssb-Index*, the UE transmits the PUCCH using a same spatial domain filter as for a reception of a SS/PBCH block with index provided by *ssb-Index* for a same serving cell or, if *servingCellId* is provided, for a serving cell indicated by *servingCellId* + - else if *PUCCH-SpatialRelationInfo* or the indicated *TCI-UL-State* provides *csi-RS-Index*, or the indicated *TCI-State* provides *csi-rs* configured with *qcl-Type* set to 'typeD', the UE transmits the PUCCH using a same spatial domain filter as for a reception of a CSI-RS with resource index provided by *csi-RS-Index* or *csi-rs* for a same serving cell or, if *servingCellId* or *cell* is provided, for a serving cell indicated by *servingCellId* or *cell* + - else *PUCCH-SpatialRelationInfo* or the indicated *TCI-UL-State* provides *srs*, the UE transmits the PUCCH using a same spatial domain filter as for a transmission of an SRS with resource index provided by *resource* for a same serving cell and/or active UL BWP or, if *servingCellId* and/or *uplinkBWP* are provided, for a serving cell indicated by *servingCellId* and/or for an UL BWP indicated by *uplinkBWP* +- an indicated *apply-IndicatedTCIState*, if provided + - if *apply-IndicatedTCIState* = 'first', the UE transmits a PUCCH using a spatial domain filter corresponding to a first *TCI-State* or *TCI-UL-State* + - if *apply-IndicatedTCIState* = 'second', the UE transmits a PUCCH using a spatial domain filter corresponding to second *TCI-State* or *TCI-UL-State* + - if *apply-IndicatedTCIState* = 'both', the UE transmits a PUCCH using respective first and second spatial domain filters corresponding to the first and the second *TCI-State* or *TCI-UL-State* + +If the UE + +- is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with a value of 0 for first CORESETs on an active DL BWP of a serving cell, and + +- is provided *coresetPoolIndex* with a value of 1 for second CORESETs on the active DL BWP of the serving cells, + +the first and second *TCI-State* or *TCI-UL-State* are specific to the first and second CORESETs, respectively. + +If a UE + +- is not provided *pathlossReferenceRSs* in *PUCCH-PowerControl*, +- is provided *enableDefaultBeamPL-ForPUCCH*, and +- is not provided *PUCCH-SpatialRelationInfo*, and +- is not provided *coresetPoolIndex* value of 1 for any CORESET, or is provided *coresetPoolIndex* value of 1 for all CORESETs, in *ControlResourceSet* and no codepoint of a TCI field, if any, in a DCI format of any search space set maps to two TCI states [5, TS 38.212] + +a spatial setting for a PUCCH transmission from the UE is same as a spatial setting for PDCCH receptions by the UE in the CORESET with the lowest ID on the active DL BWP of the PCell and, if the CORESET has two activated TCI states as described in clause 10.1, the UE determines the spatial setting for the PUCCH transmission based on the first TCI state. For a PUCCH transmission over multiple slots, a same spatial setting applies to the PUCCH transmission in each of the multiple slots. + +A number of DMRS symbols for a PUCCH transmission using PUCCH format 3 or 4 is provided by *additionalDMRS*. + +Use of $\pi/2$ -BPSK, instead of QPSK, for a PUCCH transmission using PUCCH format 3 or 4 is indicated by *pi2BPSK*. + +A UE that has indicated a capability *beamCorrespondenceWithoutUL-BeamSweeping* set to 'supported', as described in [18, TS 38.306], can determine a spatial domain filter to be used while performing the applicable channel access procedures described in [15, TS 37.213] prior to a PUCCH transmission as follows: + +- if UE is configured with a single value for *pucch-SpatialRelationInfoId* for the UL transmission, the UE may use a spatial domain filter that is same as the spatial domain filter associated with *referenceSignal* in the corresponding *pucch-SpatialRelationInfo*, +- if UE is configured with more than one value for *pucch-SpatialRelationInfoId* for the UL transmission, the UE may use a spatial domain filter that is same as the spatial domain filter associated with *referenceSignal* in the activated *pucch-SpatialRelationInfo*. + +### 9.2.3 UE procedure for reporting HARQ-ACK + +In this clause, for the purpose of determining a PUCCH resource for a PUCCH transmission in a slot using a PUCCH resource indicator field in a DCI format that schedules a PDSCH reception, and for the purpose of determining the slot for the PUCCH transmission + +- a UE is assumed to generate HARQ-ACK information regardless of whether or not the PDSCH reception provides a transport block for a HARQ process with disabled HARQ-ACK information as indicated by *downlinkHARQ-FeedbackDisabled*, if provided +- a UE is assumed to not generate HARQ-ACK information associated with a G-RNTI for multicast or a G-CS-RNTI with disabled HARQ-ACK information as described in clause 18. + +The UE determines a number of HARQ-ACK information bits as described in clauses 9.1 through 9.1.5 and a corresponding set of PUCCH resources as described in clause 9.2.1. If , the UE does not transmit a PUCCH that only includes HARQ-ACK information bits. + +A UE does not expect to transmit more than one PUCCH with HARQ-ACK information in a slot per priority index, if the UE is not provided *ackNackFeedbackMode = separate*. + +For DCI format 1\_0, the PDSCH-to-HARQ\_feedback timing indicator field values map to {1, 2, 3, 4, 5, 6, 7, 8} for SCS configuration of PUCCH transmission , to {7, 8, 12, 16, 20, 24, 28, 32} for , and to {13, 16, 24, 32, 40, 48, 56, 64} for . For a unicast DCI format, other than DCI format 1\_0, the PDSCH-to-HARQ\_feedback timing indicator field values, if present, map to values for a set of number of slots provided by *dl-DataToUL-ACK*, *dl-DataToUL-ACK-r16*, or *dl-DataToUL-ACK-DCI-1-2*, or *dl-DataToUL-ACK-r17*, or *dl-DataToUL-ACK-DCI-1-2-r17*, or *dl-DataToUL-ACK-v1700* as defined in Table 9.2.3-1. If the DCI format indicates a cell for the PUCCH transmission, as described in clause + +9.A, the PDSCH-to-HARQ\_feedback timing indicator field value maps to slots of the active UL BWP of the cell; otherwise, the PDSCH-to-HARQ\_feedback timing indicator field value maps to slots of the active UL BWP of the PCell. For DCI format 4\_1, the PDSCH-to-HARQ\_feedback timing indicator field values are provided by *dl-DataToUL-ACK-MulticastDCI-Format4-1* or, if *dl-DataToUL-ACK-MulticastDCI-Format4-1* is not provided, by {1, 2, 3, 4, 5, 6, 7, 8}. For DCI format 4\_2, the PDSCH-to-HARQ\_feedback timing indicator field values are provided by *dl-DataToUL-ACK* from *pucch-ConfigMulticast1/pucch-ConfigurationListMulticast1* or *pucch-ConfigMulticast2/pucch-ConfigurationListMulticast2* if provided; otherwise, from *pucch-Config/pucch-ConfigurationList*. + +The following apply to the PCell if the UE is provided *pucch-sSCellPattern*; otherwise, the following apply to the serving cell of the PUCCH transmission. If the UE is provided *subslotLengthForPUCCH*, is the last UL slot for PUCCH transmission that overlaps with a PDSCH reception or with a PDCCH reception providing a DCI format having associated HARQ-ACK information without scheduling a PDSCH reception; otherwise, is the last UL slot for PUCCH transmission that overlaps with the DL slot for the PDSCH reception or with the DL slot for the PDCCH reception in case of a DCI format that triggers a HARQ-ACK information report and does not schedule a PDSCH reception. + +For a SPS PDSCH reception ending in DL slot, the UE transmits the PUCCH in UL slot where is provided by the PDSCH-to-HARQ\_feedback timing indicator field, if present, in a DCI format activating the SPS PDSCH reception. + +If the UE detects a DCI format that does not include a PDSCH-to-HARQ\_feedback timing indicator field and schedules a PDSCH reception or activates a SPS PDSCH reception ending in DL slot, the UE provides corresponding HARQ-ACK information in a PUCCH transmission within UL slot where is provided by *dl-DataToUL-ACK*, or *dl-DataToUL-ACK-r16*, or *dl-DataToUL-ACK-DCI-1-2*, or *dl-DataToUL-ACK-r17*, or *dl-DataToUL-ACK-DCI-1-2-r17*, or *dl-DataToUL-ACK-v1700*. + +If the UE detects a DCI format scheduling a number of PDSCH receptions ending in DL slot or if the UE detects a DCI format generating a HARQ-ACK information bit and does not schedule a PDSCH reception through a PDCCH reception ending in DL slot, the UE provides corresponding HARQ-ACK information in a PUCCH transmission within UL slot, where is a number of slots and is indicated by the PDSCH-to-HARQ\_feedback timing indicator field in the DCI format, if present, or provided by *dl-DataToUL-ACK*, *dl-DataToUL-ACK-r16*, or *dl-DataToUL-ACK-DCI-1-2*, or *dl-DataToUL-ACK-r17*, or *dl-DataToUL-ACK-DCI-1-2-r17*, or *dl-DataToUL-ACK-v1700*. + +A PUCCH transmission with HARQ-ACK information is subject to the limitations for UE transmissions described in clause 11.1, clause 11.1.1 and clause 17.2. + +**Table 9.2.3-1: Mapping of PDSCH-to-HARQ\_feedback timing indicator field values to numbers of slots** + +| PDSCH-to-HARQ_feedback timing indicator | | | Number of slots | +|-----------------------------------------|--------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 bit | 2 bits | 3 bits | | +| '0' | '00' | '000' | 1 st value provided by dl-DataToUL-ACK , dl-DataToUL-ACK-r16 , dl-DataToUL-ACK-DCI-1-2 , dl-DataToUL-ACK-r17 , dl-DataToUL-ACK-DCI-1-2-r17 , dl-DataToUL-ACK-v1700 , or dl-DataToUL-ACK-MulticastDCI-Format4-1 | +| '1' | '01' | '001' | 2 nd value provided by dl-DataToUL-ACK , dl-DataToUL-ACK-r16 , dl-DataToUL-ACK-DCI-1-2 , dl-DataToUL-ACK-r17 , dl-DataToUL-ACK-DCI-1-2-r17 , dl-DataToUL-ACK-v1700 , or dl-DataToUL-ACK-MulticastDCI-Format4-1 | +| | '10' | '010' | 3 rd value provided by dl-DataToUL-ACK , dl-DataToUL-ACK-r16 , dl-DataToUL-ACK-DCI-1-2 , dl-DataToUL-ACK-r17 , dl-DataToUL-ACK-DCI-1-2-r17 , dl-DataToUL-ACK-v1700 , or dl-DataToUL-ACK-MulticastDCI-Format4-1 | +| | '11' | '011' | 4 th value provided by dl-DataToUL-ACK , dl-DataToUL-ACK-r16 , dl-DataToUL-ACK-DCI-1-2 , dl-DataToUL-ACK-r17 , dl-DataToUL-ACK-DCI-1-2-r17 , dl-DataToUL-ACK-v1700 , or dl-DataToUL-ACK-MulticastDCI-Format4-1 | +| | | '100' | 5 th value provided by dl-DataToUL-ACK , dl-DataToUL-ACK-r16 , dl-DataToUL-ACK-DCI-1-2 , dl-DataToUL-ACK-r17 , dl-DataToUL-ACK-DCI-1-2-r17 , dl-DataToUL-ACK-v1700 , or dl-DataToUL-ACK-MulticastDCI-Format4-1 | +| | | '101' | 6 th value provided by dl-DataToUL-ACK , dl-DataToUL-ACK-r16 , dl-DataToUL-ACK-DCI-1-2 , dl-DataToUL-ACK-r17 , dl-DataToUL-ACK-DCI-1-2-r17 , dl-DataToUL-ACK-v1700 , or dl-DataToUL-ACK-MulticastDCI-Format4-1 | +| | | '110' | 7 th value provided by dl-DataToUL-ACK , dl-DataToUL-ACK-r16 , dl-DataToUL-ACK-DCI-1-2 , dl-DataToUL-ACK-r17 , dl-DataToUL-ACK-DCI-1-2-r17 , dl-DataToUL-ACK-v1700 , or dl-DataToUL-ACK-MulticastDCI-Format4-1 | +| | | '111' | 8 th value provided by dl-DataToUL-ACK , dl-DataToUL-ACK-r16 , dl-DataToUL-ACK-DCI-1-2 , dl-DataToUL-ACK-r17 , dl-DataToUL-ACK-DCI-1-2-r17 , dl-DataToUL-ACK-v1700 , or dl-DataToUL-ACK-MulticastDCI-Format4-1 | + +For a PUCCH transmission with HARQ-ACK information, a UE determines a PUCCH resource on the cell of the PUCCH transmission, as described in clause 9.A, after determining a set of PUCCH resources for HARQ-ACK information bits, as described in clause 9.2.1. The PUCCH resource determination is based on a PUCCH resource indicator field [5, TS 38.212], if present, in a last DCI format, excluding the SPS activation DCI, among the DCI formats that have a value of a PDSCH-to-HARQ\_feedback timing indicator field, if present, or a value of *dl-DataToUL-ACK*, or *dl-DataToUL-ACK-r16*, or *dl-DataToUL-ACK-DCI-1-2*, or *dl-DataToUL-ACK-r17*, or *dl-DataToUL-ACK-DCI-1-2-r17*, or *dl-DataToUL-ACK-MulticastDCI-Format4-1*, or *dl-DataToUL-ACK-v1700*, indicating a same slot for the PUCCH transmission, that the UE detects and for which the UE transmits corresponding HARQ-ACK information in the PUCCH. + +The PUCCH resource indicator field values map to values of a set of PUCCH resource indexes, as defined in Table 9.2.3-2 for a PUCCH resource indicator field of 3 bits, provided by *resourceList* for PUCCH resources from a set of PUCCH resources provided by *PUCCH-ResourceSet* with a maximum of eight PUCCH resources. If the PUCCH resource indicator field includes 1 bit or 2 bits, the values map to the first two values or the first four values, respectively, of Table 9.2.3-2. If the last DCI format does not include a PUCCH resource indicator field, the first value of Table 9.2.3-2 is used. + +For the first set of PUCCH resources and when the size of *resourceList* is larger than eight, when a UE provides HARQ-ACK information in a PUCCH transmission in response to detecting a last DCI format in a PDCCH reception, excluding the SPS activation DCI, among DCI formats with a value of the PDSCH-to-HARQ\_feedback timing indicator field, if present, or a value of *dl-DataToUL-ACK*, or *dl-DataToUL-ACK-r16*, or *dl-DataToUL-ACK-DCI-1-2*, or *dl-DataToUL-ACK-r17*, or *dl-DataToUL-ACK-DCI-1-2-r17*, or *dl-DataToUL-ACK-MulticastDCI-Format4-1*, or *dl-DataToUL-ACK-v1700*, indicating a same slot for the PUCCH transmission, the UE determines a PUCCH resource with index , , as + +$$r_{\text{PUCCH}} = \left\{ \begin{aligned} & \left\lceil \frac{n_{\text{CCE},p} \cdot \lceil R_{\text{PUCCH}}/8 \rceil}{N_{\text{CCE},p}} \right\rceil + \Delta_{\text{PRI}} \cdot \left\lceil \frac{R_{\text{PUCCH}}}{8} \right\rceil & \text{if } \Delta_{\text{PRI}} < R_{\text{PUCCH}} \bmod 8 \\ & \left\lceil \frac{n_{\text{CCE},p} \cdot \lceil R_{\text{PUCCH}}/8 \rceil}{N_{\text{CCE},p}} \right\rceil + \Delta_{\text{PRI}} \cdot \left\lceil \frac{R_{\text{PUCCH}}}{8} \right\rceil + R_{\text{PUCCH}} \bmod 8 & \text{if } \Delta_{\text{PRI}} \geq R_{\text{PUCCH}} \bmod 8 \end{aligned} \right\}$$ + +where $n_{\text{CCE},p}$ is a number of CCEs in CORESET of the PDCCH reception for the DCI format as described in clause 10.1, $N_{\text{CCE},p}$ is the index of a first CCE for the PDCCH reception, and $R_{\text{PUCCH}}$ is a value of the PUCCH resource indicator field in the DCI format. When the PDCCH reception includes first and second PDCCH candidates from respective first and second search space sets, as described in clause 10.1, the CORESET is associated with the search space set having the smaller index. If + +- the first search space set has larger index than the second search space set and includes the first PDCCH candidate and a third PDCCH candidate that have same first CCE index and CCE aggregation levels 8 and 16, or 16 and 8, respectively, +- the second search space set includes the second PDCCH candidate that has same index and same CCE aggregation level as the first PDCCH candidate, and a fourth PDCCH candidate that has same index and same CCE aggregation level as the third PDCCH candidate, +- the CORESET associated with the first search space set has *cce-REG-MappingType* = 'nonInterleaved' and has duration of one symbol, and +- the second PDCCH candidate has different first CCE index than the fourth PDCCH candidate + +the UE determines from the PDCCH candidate with CCE aggregation level 16 among the second PDCCH candidate and the fourth PDCCH candidate. + +If the DCI format does not include a PUCCH resource indicator field, . + +**Table 9.2.3-2: Mapping of PUCCH resource indication field values to a PUCCH resource in a PUCCH resource set with maximum 8 PUCCH resources** + +| PUCCH resource indicator | | | PUCCH resource | +|--------------------------|--------|--------|-----------------------------------------------------------------------------------------------------------------------------------| +| 1 bit | 2 bits | 3 bits | | +| '0' | '00' | '000' | 1 st PUCCH resource provided by pucch-ResourceId obtained from the 1 st value of resourceList | +| '1' | '01' | '001' | 2 nd PUCCH resource provided by pucch-ResourceId obtained from the 2 nd value of resourceList | +| | '10' | '010' | 3 rd PUCCH resource provided by pucch-ResourceId obtained from the 3 rd value of resourceList | +| | '11' | '011' | 4 th PUCCH resource provided by pucch-ResourceId obtained from the 4 th value of resourceList | +| | | '100' | 5 th PUCCH resource provided by pucch-ResourceId obtained from the 5 th value of resourceList | +| | | '101' | 6 th PUCCH resource provided by pucch-ResourceId obtained from the 6 th value of resourceList | +| | | '110' | 7 th PUCCH resource provided by pucch-ResourceId obtained from the 7 th value of resourceList | +| | | '111' | 8 th PUCCH resource provided by pucch-ResourceId obtained from the 8 th value of resourceList | + +If a UE determines a first resource for a PUCCH transmission with HARQ-ACK information corresponding only to a PDSCH reception without a corresponding PDCCH or detects a first DCI format indicating a first resource for a PUCCH transmission with corresponding HARQ-ACK information in a slot and also detects at a later time a second DCI format indicating a second resource for a PUCCH transmission with corresponding HARQ-ACK information in the slot, the UE does not expect to multiplex HARQ-ACK information corresponding to the second DCI format in a PUCCH resource in the slot if the PDCCH reception that includes the second DCI format is not earlier than from the beginning of a first symbol of the first resource for PUCCH transmission in the slot where, and are defined in clause 4.1 of [4, TS 38.211] and corresponds to the smallest SCS configuration among the SCS configurations of the PDCCHs providing the DCI formats and the SCS configuration of the PUCCH. If *processingType2Enabled* of *PDSCH-* + +*ServingCellConfig* is set to *enable* for the serving cell with the second DCI format and for all serving cells with corresponding HARQ-ACK information multiplexed in the PUCCH transmission in the slot, for , for , for ; otherwise, for , for , for , for , for , and for . + +If a UE is not provided *SPS-PUCCH-AN-List* and transmits HARQ-ACK information corresponding only to a PDSCH reception without a corresponding PDCCH, which includes the first SPS PDSCH reception associated with the corresponding activation DCI, a PUCCH resource for corresponding PUCCH transmission with HARQ-ACK information is provided by *n1PUCCH-AN*. + +If a UE transmits a PUCCH with HARQ-ACK information using PUCCH format 0, the UE determines values and for computing a value of cyclic shift [4, TS 38.211] where is provided by *initialCyclicShift* of *PUCCH-format0* or, if *initialCyclicShift* is not provided, by the initial cyclic shift index as described in clause 9.2.1 and is determined from the value of one HARQ-ACK information bit or from the values of two HARQ-ACK information bits as in Table 9.2.3-3 and Table 9.2.3-4, respectively. + +**Table 9.2.3-3: Mapping of values for one HARQ-ACK information bit to sequences for PUCCH format 0** + +| HARQ-ACK Value | 0 | 1 | +|-----------------------|---|---| +| Sequence cyclic shift | | | + +**Table 9.2.3-4: Mapping of values for two HARQ-ACK information bits to sequences for PUCCH format 0** + +| HARQ-ACK Value | {0, 0} | {0, 1} | {1, 1} | {1, 0} | +|-----------------------|--------|--------|--------|--------| +| Sequence cyclic shift | | | | | + +If a UE transmits a PUCCH with HARQ-ACK information using PUCCH format 1, the UE is provided a value for $m_0$ by *initialCyclicShift* of *PUCCH-format1* or, if *initialCyclicShift* is not provided, by the initial cyclic shift index as described in clause 9.2.1. + +If a UE transmits a PUCCH with HARQ-ACK information bits and bits using PUCCH format 2 or PUCCH format 3 in a PUCCH resource that includes PRBs, the UE determines a number of PRBs for the PUCCH transmission to be the minimum number of PRBs, that is smaller than or equal to a number of PRBs provided respectively by *nrofPRBs* of *PUCCH-format2* or *nrofPRBs* of *PUCCH-format3* and start from the first PRB from the number of PRBs, that results to and, if , , where , , and are defined in clause 9.2.5.2. For PUCCH format 3, if is not equal according to [4, TS 38.211], is increased to the nearest allowed value of *nrofPRBs* [12, TS 38.331]. If , the UE transmits the PUCCH over PRBs. + +If a UE is provided a first interlace of PRBs by *interlace0* in *InterlaceAllocation* and transmits a PUCCH with HARQ-ACK information bits and bits using PUCCH format 2 or PUCCH format 3, the UE transmits the PUCCH over the first interlace if ; otherwise, if the UE is provided a second interlace by *interlace1* in *PUCCH-format2* or *PUCCH-format3*, the UE transmits the PUCCH over the first and second interlaces. + +### 9.2.4 UE procedure for reporting SR + +A UE can be provided by *SchedulingRequestResourceConfig* a set of configurations for SR in a PUCCH transmission using either PUCCH format 0 or PUCCH format 1. + +A UE can be provided by *schedulingRequestID-BFR-SCell* a configuration for LRR in a PUCCH transmission using either PUCCH format 0 or PUCCH format 1. + +A UE can be provided by *schedulingRequestID-BFR* a first configuration for LRR and, if the UE provides *twoLRRcapability*, the UE can be provided by *schedulingRequestID-BFR2* a second configuration for LRR in a PUCCH transmission using either PUCCH format 0 or PUCCH format 1. + +A UE can be provided by *schedulingRequestID-LBT-SCell* a configuration for consistent LBT failure recovery, as described in [11, TS 38.321], in a PUCCH transmission using either PUCCH format 0 or PUCCH format 1. The UE can be provided, by *phy-PriorityIndex* in *SchedulingRequestResourceConfig*, a priority index 0 or a priority index 1 for the SR. If the UE is not provided a priority index for SR, the priority index is 0. + +The UE is also provided a periodicity in symbols or slots and an offset in slots by *periodicityAndOffset* for a PUCCH transmission conveying SR. If *periodicityAndOffset* is larger than one slot, the UE determines a SR transmission occasion in a PUCCH to be in a slot with number $[4, \text{TS } 38.211]$ in a frame with number *frameNumber* if + +*periodicityAndOffset* is one slot, the UE expects that *frameNumber* and every slot is a SR transmission occasion in a PUCCH. + +If *periodicityAndOffset* is smaller than one slot, the UE determines a SR transmission occasion in a PUCCH to start in a symbol with index $[4, \text{TS } 38.211]$ if *startingSymbolIndex* is the value of *startingSymbolIndex*. + +If the UE determines that, for a SR transmission occasion in a PUCCH, the number of symbols available for the PUCCH transmission in a slot is smaller than the value provided by *nrofSymbols*, the UE does not transmit the PUCCH in the slot. + +SR transmission occasions in a PUCCH are subject to the limitations for UE transmissions described in clause 11.1, clause 11.1.1 and clause 17.2. + +The UE transmits a PUCCH in the PUCCH resource for the corresponding SR configuration only when the UE transmits a positive SR. For a positive SR transmission using PUCCH format 0, the UE transmits the PUCCH as described in [4, TS 38.211] by obtaining *ackNackFeedback* as described for HARQ-ACK information in clause 9.2.3 and by setting *positiveSR*. For a positive SR transmission using PUCCH format 1, the UE transmits the PUCCH as described in [4, TS 38.211] by setting *positiveSR*. + +### 9.2.5 UE procedure for reporting multiple UCI types + +This clause is applicable to the case that a UE has resources for PUCCH transmissions or for PUCCH and PUSCH transmissions that overlap in time and each PUCCH transmission is over a single slot without repetitions. Any case that a PUCCH transmission is with repetitions over multiple slots is described in clause 9.2.6. If a UE is configured with multiple PUCCH resources in a slot to transmit CSI reports + +- if the UE is not provided *multi-CSI-PUCCH-ResourceList* or if PUCCH resources for transmissions of CSI reports do not overlap in the slot, the UE determines a first resource corresponding to a CSI report with the highest priority [6, TS 38.214] + - if the first resource includes PUCCH format 2, and if there are remaining resources in the slot that do not overlap with the first resource, the UE determines a CSI report with the highest priority, among the CSI reports with corresponding resources from the remaining resources, and a corresponding second resource as an additional resource for CSI reporting + - if the first resource includes PUCCH format 3 or PUCCH format 4, and if there are remaining resources in the slot that include PUCCH format 2 and do not overlap with the first resource, the UE determines a CSI report with the highest priority, among the CSI reports with corresponding resources from the remaining resources, and a corresponding second resource as an additional resource for CSI reporting +- if the UE is provided *multi-CSI-PUCCH-ResourceList* and if any of the multiple PUCCH resources overlap, the UE multiplexes all CSI reports in a resource from the resources provided by *multi-CSI-PUCCH-ResourceList*, as described in clause 9.2.5.2. + +A UE multiplexes DL HARQ-ACK information, with or without SR, and CSI report(s) in a same PUCCH if the UE is provided *simultaneousHARQ-ACK-CSI*; otherwise, the UE drops the CSI report(s) and includes only DL HARQ-ACK information, with or without SR, in the PUCCH. If the UE would transmit multiple PUCCHs in a slot that include DL HARQ-ACK information and CSI report(s), the UE expects to be provided a same configuration for *simultaneousHARQ-ACK-CSI* each of PUCCH formats 2, 3, and 4. + +If a UE would multiplex CSI reports that include Part 2 CSI reports in a PUCCH resource, the UE determines the PUCCH resource and a number of PRBs for the PUCCH resource or a number of Part 2 CSI reports assuming that each of the CSI reports and, if any, each CSI sub-report included in a CSI report, indicates rank 1, or rank combination of $\{1, 1\}$ if applicable. If the higher layer parameter *csi-ReportMode* of CSI reports is set to 'Mode2', the UE determines the PUCCH resource and a number of PRBs for the PUCCH resource or a number of Part 2 CSI reports assuming that each CRI in the CSI report is associated with a resource pair. + +If a UE would transmit multiple overlapping PUCCHs in a slot or overlapping PUCCH(s) and PUSCH(s) in a slot and, when applicable as described in clauses 9.2.5.1, 9.2.5.2, 9.2.5.3 and 18, the UE is configured to multiplex different UCI types or UCI of different priority indexes in one PUCCH, and at least one of the multiple overlapping PUCCHs or PUSCHs is in response to a DCI format detection by the UE, the UE multiplexes all corresponding UCI types or UCI of + +different priority indexes if the following conditions are met. If one of the PUCCH transmissions or PUSCH transmissions is in response to a DCI format detection by the UE, the UE expects that the first symbol of the earliest PUCCH or PUSCH, among a group overlapping PUCCHs and PUSCHs in the slot, satisfies the following timeline conditions + +- is not before a symbol with CP starting after after a last symbol of any corresponding PDSCH, is given by maximum of where for the i-th PDSCH with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs and PUSCHs, , is selected for the i-th PDSCH following [6, TS 38.214], is selected based on the UE PDSCH processing capability of the i-th PDSCH and SCS configuration , where corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH scheduling the i-th PDSCH if any, the i-th PDSCH, the PUCCH with corresponding HARQ-ACK transmission for the i-th PDSCH, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs. +- is not before a symbol with CP starting after after a last symbol of a PDCCH reception providing a DCI format having associated HARQ-ACK information without scheduling a PDSCH reception. is given by maximum of where for the i-th PDCCH providing the DCI format with corresponding HARQ-ACK transmission on a PUCCH which is in the group of overlapping PUCCHs and PUSCHs, , as described in clause 10.2, where corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH, the PUCCH with corresponding HARQ-ACK information, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs. +- if there is no aperiodic CSI report multiplexed in a PUSCH in the group of overlapping PUCCHs and PUSCHs, is not before a symbol with CP starting after after a last symbol of + - any PDCCH with the DCI format scheduling an overlapping PUSCH, and + - any PDCCH providing a DCI format with corresponding HARQ-ACK information in an overlapping PUCCH in the slot + +If there is at least one PUSCH in the group of overlapping PUCCHs and PUSCHs, is given by maximum of where for the i-th PUSCH which is in the group of overlapping PUCCHs and PUSCHs, , and are selected for the i-th PUSCH following [6, TS 38.214], is selected based on the UE PUSCH processing capability of the i-th PUSCH and SCS configuration , where corresponds to the smallest SCS configuration among the SCS configurations used for the PDCCH scheduling the i-th PUSCH, the PDCCHs scheduling the PDSCHs, or providing the DCI formats without scheduling PDSCHs, with corresponding HARQ-ACK information on a PUCCH which is in the group of overlapping PUCCHs/PUSCHs, and all PUSCHs in the group of overlapping PUCCHs and PUSCHs. + +If there is no PUSCH in the group of overlapping PUCCHs and PUSCHs, is given by maximum of where for the i-th PDSCH, or the i-th PDCCH providing a DCI format without scheduling PDSCH, with corresponding HARQ-ACK information on a PUCCH which is in the group of overlapping PUCCHs, , is selected based on the UE PUSCH processing capability of the PUCCH serving cell if configured. is selected based on the UE PUSCH processing capability 1, if PUSCH processing capability is not configured for the PUCCH serving cell. is selected based on the smallest SCS configuration between the SCS configuration used for the PDCCH scheduling the i-th PDSCH, or providing the i-th DCI format without scheduling PDSCH, with corresponding HARQ-ACK information on a PUCCH which is in the group of overlapping PUCCHs, and the SCS configuration for the PUCCH serving cell. + +- if there is an aperiodic CSI report multiplexed in a PUSCH in the group of overlapping PUCCHs and PUSCHs, is not before a symbol with CP starting after after a last symbol of + - any PDCCH with the DCI format scheduling an overlapping PUSCH, and + - any PDCCH scheduling a PDSCH, or providing a DCI format , with corresponding HARQ-ACK information in an overlapping PUCCH in the slot + +where corresponds to the smallest SCS configuration among the SCS configuration of the PDCCHs, the smallest SCS configuration for the group of the overlapping PUSCHs, and the smallest SCS configuration of CSI-RS associated with the DCI format scheduling the PUSCH with the multiplexed aperiodic CSI report, and for , for , and for . is defined in [6, TS 38.214] and it is applied only if of Table 5.4-1 in [6, TS 38.214] is applied to the determination of . + +- , , , , and are defined in [6, TS 38.214] and and are defined in [4, TS 38.211]. + +If a UE would transmit multiple overlapping PUCCHs in a slot or overlapping PUCCH(s) and PUSCH(s) in a slot, one of the PUCCHs includes HARQ-ACK information in response to an SPS PDSCH reception, and any PUSCH is not in response to a DCI format detection, the UE expects that the first symbol of the earliest PUCCH or PUSCH satisfies the first of the previous timeline conditions with the exception that components associated to a SCS configuration for a PDCCH scheduling a PDSCH or a PUSCH are absent from the timeline conditions. + +A UE does not expect a PUCCH or a PUSCH that is in response to a DCI format detection to overlap with any other PUCCH or PUSCH that does not satisfy the above timing conditions. + +A UE that + +- is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with a value of 0 for first CORESETs on active DL BWPs of serving cells, and +- is provided *coresetPoolIndex* with a value of 1 for second CORESETs on active DL BWPs of the serving cells, and +- is provided *ackNackFeedbackMode = separate* + +does not expect a PUCCH or a PUSCH transmission triggered by a detection of a DCI format in a PDCCH received in a CORESET from the first CORESETs to overlap in time with a PUCCH or a PUSCH transmission triggered by a detection of a DCI format in a PDCCH received in a CORESET from the second CORESETs if the UE is not provided *enableSTx2PofmDCI*, else, if the UE is provided *enableSTx2PofmDCI*, the UE does not expect to transmit a PUCCH that includes HARQ-ACK information and is associated with either the first or the second CORESETs to overlap with a PUSCH transmission associated with either the second or the first CORESETs and not overlap with a PUSCH transmission associated with either the first or the second CORESETs, respectively. + +If there is one or more aperiodic CSI reports multiplexed on a PUSCH in the group of overlapping PUCCHs and PUSCHs and if symbol $l$ is before symbol $l'$ that is a next uplink symbol with CP starting after after the end of the last symbol of + +- the last symbol of aperiodic CSI-RS resource for channel measurements, and +- the last symbol of aperiodic CSI-IM used for interference measurements, and +- the last symbol of aperiodic NZP CSI-RS for interference measurements, when aperiodic CSI-RS is used for channel measurement for triggered CSI report + +the UE is not required to update the CSI report for the triggered CSI report. $\mu$ is defined in [6, TS 38.214] and corresponds to the smallest SCS configuration among the SCS configurations of the PDCCHs scheduling the PUSCHs, the smallest SCS configuration of aperiodic CSI-RSs associated with DCI formats provided by the PDCCHs triggering the aperiodic CSI reports, and the smallest SCS configuration of the overlapping PUCCHs and PUSCHs and for $\mu$ , for and for . + +If a UE would transmit multiple PUCCHs in a slot that include HARQ-ACK information, and/or SR, and/or CSI reports and any PUCCH with HARQ-ACK information in the slot satisfies the above timing conditions and does not overlap with any other PUCCH or PUSCH in the slot that does not satisfy the above timing conditions, the UE multiplexes the HARQ-ACK information, and/or SR, and/or CSI reports and determines corresponding PUCCH(s) for transmission in the slot according to the following pseudo-code. If the multiple PUCCHs do not include HARQ-ACK information and do not overlap with any PUSCH transmission by the UE in response to a DCI format detection by the UE, the timing conditions do not apply. + +If + +- a UE is not provided *multi-CSI-PUCCH-ResourceList*, and +- a resource for a PUCCH transmission with HARQ-ACK information in response to SPS PDSCH reception and/or a resource for a PUCCH associated with a SR occasion overlap in time with two resources for respective PUCCH transmissions with two CSI reports, and +- there is no resource for a PUCCH transmission with HARQ-ACK information in response to a DCI format detection that overlaps in time with any of the previous resources, and +- the following pseudo code results to the UE attempting to determine a single PUCCH resource from the HARQ-ACK and/or the SR resource and the two PUCCH resources with CSI reports + +the UE + +- multiplexes the HARQ-ACK information and/or the SR in the resource for the PUCCH transmission with the CSI report having the higher priority, and +- does not transmit the PUCCH with the CSI report having the lower priority + +Set to the set of resources for transmission of corresponding PUCCHs in a single slot without repetitions where + +- a resource with earlier first symbol is placed before a resource with later first symbol +- for two resources with same first symbol, the resource with longer duration is placed before the resource with shorter duration +- for two resources with same first symbol and same duration, the placement is arbitrary + - the above three steps for the set are according to a subsequent pseudo-code for a function +- a resource for negative SR transmission that does not overlap with a resource for HARQ-ACK or CSI transmission is excluded from set +- if the UE is not provided *simultaneousHARQ-ACK-CSI* and resources for transmission of HARQ-ACK information include PUCCH format 0 or PUCCH format 2, resources that include PUCCH format 2, or PUCCH format 3, or PUCCH format 4 for transmission of CSI reports are excluded from the set if they overlap with any resource from the resources for transmission of HARQ-ACK information +- if the UE is not provided *simultaneousHARQ-ACK-CSI* and at least one of the resources for transmission of HARQ-ACK information includes PUCCH format 1, PUCCH format 3, or PUCCH format 4 + - resources that include PUCCH format 3 or PUCCH format 4 for transmission of CSI reports are excluded from the set + - resources that include PUCCH format 2 for transmission of CSI reports are excluded from the set if they overlap with any resource from the resources for transmission of HARQ-ACK information + +Set to the cardinality of + +Set to be the first symbol of resource in the slot + +Set to be the number of symbols of resource in the slot + +Set - index of first resource in set + +Set - counter of overlapped resources + +while + +if + +and resource overlaps with resource and the resources in set are of same priority index, or + +and resource overlaps with resource, , the resources in set are of different priority indexes, and the UE is provided *uci-MuxWithDiffPrio* + +then + +; + +; + +else + +if + +determine a single resource for multiplexing UCI associated with resources as described in clauses 9, 9.2.5.0, 9.2.5.1, 9.2.5.2, 9.2.5.3, and 18 + +set the index of the single resource to + +``` + + % start from the beginning after reordering unmerged resources at next step + ; + % function that re-orders resources in current set + Set to the cardinality of + else + ; + end if +end if +end while + +``` + +The function performs the following pseudo-code + +``` + +{ + ; + while % the next two while loops are to re-order the unmerged resources + ; + while + if OR + ; + ; + ; + end if + ; + end while + ; +end while +} + +``` + +For each PUCCH resource in the set that satisfies the aforementioned timing conditions, when applicable, + +- the UE transmits a PUCCH using the PUCCH resource if the PUCCH resource does not overlap in time with a PUSCH transmission after multiplexing UCI following the procedures described in clauses 9, 9.2.5.1, 9.2.5.2, 9.2.5.3 and 18 +- the UE multiplexes HARQ-ACK information and/or CSI reports in a PUSCH if the PUCCH resource overlaps in time with a PUSCH transmission, as described in clause 9.3, and does not transmit SR. In case the PUCCH resource overlaps in time with multiple PUSCH transmissions, the PUSCH for multiplexing HARQ-ACK information and/or CSI is selected as described in clause 9. If the PUSCH transmission by the UE is not in response to a DCI format detection and the UE multiplexes only CSI reports, the timing conditions are not applicable +- the UE does not expect the resource to overlap with a second resource of a PUCCH transmission over multiple slots if the resource is obtained from a group of resources that do not overlap with the second resource + +clauses 9.2.5.0, 9.2.5.1, 9.2.5.2, 9.2.5.3 and 18 assume the following + +- resources for transmissions of UCI types, prior to multiplexing or dropping, overlap in a slot +- multiplexing conditions of corresponding UCI types in a single PUCCH are satisfied, and +- the UE does not transmit any PUSCH time-overlapping with PUCCH in the slot. + +#### 9.2.5.0 UE procedure for prioritization between SL HARQ-ACK information in a PUCCH and DL HARQ-ACK or SR or CSI in a PUCCH + +The priority value of a PUCCH transmission is as described in clause 16.2.4.3.1. + +For prioritization between SL HARQ-ACK information in a first PUCCH and DL HARQ-ACK or SR or CSI in a second PUCCH + +- if the second PUCCH has priority index 1, + - if *sl-PriorityThreshold-UL-URLLC* is provided + - the UE transmits the first PUCCH if a smallest priority value of the first PUCCH is smaller than *sl-PriorityThreshold-UL-URLLC*; otherwise, the UE transmits the second PUCCH + - else + - the UE transmits the second PUCCH +- else + - the UE transmits the first PUCCH if the smallest priority value of the first PUCCH is smaller than *sl-PriorityThreshold*; otherwise, the UE transmits the second PUCCH + +When the UE determines to transmit the second PUCCH, the UE determines a single resource for multiplexing UCI in the second PUCCH as described in clauses 9.2.5.1 and 9.2.5.2. + +#### 9.2.5.1 UE procedure for multiplexing HARQ-ACK or CSI and SR in a PUCCH + +In the following, a UE is configured to transmit PUCCHs for respective SRs in a slot, as determined by a set of *schedulingRequestResourceId*, a *schedulingRequestResourceId* associated with *schedulingRequestID-BFR-SCell*, a *schedulingRequestResourceId* associated with *schedulingRequestID-BFR*, a *schedulingRequestResourceId* associated with *schedulingRequestID-BFR2* if the UE provides *twoLRRcapability*, and a *schedulingRequestResourceId* associated with *schedulingRequestID-LBT-SCell*, with SR transmission occasions that would overlap with a transmission of a PUCCH with HARQ-ACK information from the UE in the slot or with a transmission of a PUCCH with CSI report(s) from the UE in the slot. + +If a UE would transmit a PUCCH with positive SR and at most two HARQ-ACK information bits in a resource using PUCCH format 0, the UE transmits the PUCCH in the resource using PUCCH format 0 in PRB(s) for HARQ-ACK information as described in clause 9.2.3. The UE determines a value of $n_{\text{SR}}$ and $n_{\text{ACK}}$ for computing a value of cyclic shift [4, TS 38.211] where $n_{\text{SR}}$ is provided by *initialCyclicShift* of *PUCCH-format0*, and $n_{\text{ACK}}$ is determined from the value of one HARQ-ACK information bit or from the values of two HARQ-ACK information bits as in Table 9.2.5-1 and Table 9.2.5-2, respectively. + +If the UE would transmit negative SR and a PUCCH with at most two HARQ-ACK information bits in a resource using PUCCH format 0, the UE transmits the PUCCH in the resource using PUCCH format 0 for HARQ-ACK information as described in clause 9.2.3. + +**Table 9.2.5-1: Mapping of values for one HARQ-ACK information bit and positive SR to sequences for PUCCH format 0** + +| HARQ-ACK Value | 0 | 1 | +|-----------------------|---|---| +| Sequence cyclic shift | | | + +**Table 9.2.5-2: Mapping of values for two HARQ-ACK information bits and positive SR to sequences for PUCCH format 0** + +| HARQ-ACK Value | {0, 0} | {0, 1} | {1, 1} | {1, 0} | +|-----------------------|--------|--------|--------|--------| +| Sequence cyclic shift | | | | | + +If a UE would transmit SR in a resource using PUCCH format 0 and HARQ-ACK information bits in a resource using PUCCH format 1 in a slot, the UE transmits only a PUCCH with the HARQ-ACK information bits in the resource using PUCCH format 1. + +If the UE would transmit positive SR in a first resource using PUCCH format 1 and at most two HARQ-ACK information bits in a second resource using PUCCH format 1 in a slot, the UE transmits a PUCCH with HARQ-ACK information bits in the first resource using PUCCH format 1 as described in clause 9.2.3. If a UE would not transmit a positive SR in a resource using PUCCH format 1 and would transmit at most two HARQ-ACK information bits in a resource using PUCCH format 1 in a slot, the UE transmits a PUCCH in the resource using PUCCH format 1 for HARQ-ACK information as described in clause 9.2.3. + +If a UE would transmit a PUCCH with HARQ-ACK information bits in a resource using PUCCH format 2 or PUCCH format 3 or PUCCH format 4 in a slot, as described in clauses 9.2.1 and 9.2.3, bits representing a negative or positive SR, in ascending order of the values of *schedulingRequestResourceId*, a *schedulingRequestResourceId* associated with *schedulingRequestID-BFR-SCell*, a *schedulingRequestResourceId* associated with *schedulingRequestID-BFR*, a *schedulingRequestResourceId* associated with *schedulingRequestID-BFR2* if the UE provides *twoLRRcapability*, and a *schedulingRequestResourceId* associated with *schedulingRequestID-LBT-SCell*, are appended to the HARQ-ACK information bits and the UE transmits the combined UCI bits in a PUCCH using a resource with PUCCH format 2 or PUCCH format 3 or PUCCH format 4 that the UE determines as described in clauses 9.2.1 and 9.2.3. If one of the SRs is a positive LRR, the value of the bits indicates the positive LRR. An all-zero value for the bits represents a negative SR value across all SRs. + +If a UE would transmit a PUCCH with $O_{CSI}$ CSI report bits in a resource using PUCCH format 2 or PUCCH format 3 or PUCCH format 4 in a slot, bits representing corresponding negative or positive SR, in ascending order of the values of *schedulingRequestResourceId*, a *schedulingRequestResourceId* associated with *schedulingRequestID-BFR-SCell*, a *schedulingRequestResourceId* associated with *schedulingRequestID-BFR*, a *schedulingRequestResourceId* associated with *schedulingRequestID-BFR2* if the UE provides *twoLRRcapability*, and a *schedulingRequestResourceId* associated with *schedulingRequestID-LBT-SCell*, are prepended to the CSI information bits as described in clause 9.2.5.2 and the UE transmits a PUCCH with the combined UCI bits in a resource using the PUCCH format 2 or PUCCH format 3 or PUCCH format 4 for CSI reporting. If one of the SRs is a positive LRR, the value of the bits indicates the positive LRR. An all-zero value for the bits represents a negative SR value across all SRs. + +If a UE transmits a PUCCH with HARQ-ACK information bits, SR bits, and CRC bits using PUCCH format 2 or PUCCH format 3 in a PUCCH resource that includes PRBs, the UE determines a number of PRBs for the PUCCH transmission to be the minimum number of PRBs, that is smaller than or equal to a number of PRBs provided by *nrofPRBs* in *PUCCH-format2* or *nrofPRBs* in *PUCCH-format3* and starts from the first PRB from the number of PRBs, that results to and, if , , where , , and are defined in clause 9.2.5.2. For PUCCH format 3, if is not equal according to [4, TS 38.211], is increased to the nearest allowed value of *nrofPRBs* [12, TS 38.331]. If, the UE transmits the PUCCH over the PRBs. + +If a UE is provided a first interlace of PRBs by *interlace0* in *InterlaceAllocation* and transmits a PUCCH with HARQ-ACK information bits, SR bits, and CRC bits using PUCCH format 2 or PUCCH format 3, the UE transmits the PUCCH over the first interlace if ; otherwise, if the UE is provided a second interlace by *interlace1* in *PUCCH-format2* or *PUCCH-format3*, the UE transmits the PUCCH over the first and second interlaces. + +#### 9.2.5.2 UE procedure for multiplexing HARQ-ACK/SR/CSI in a PUCCH + +For a transmission occasion of a single CSI report, a PUCCH resource is provided by *pucch-CSI-ResourceList*. For a transmission occasion of multiple CSI reports, corresponding PUCCH resources can be provided by *multi-CSI-PUCCH-ResourceList*. If a UE is provided first and second *PUCCH-Config*, *multi-CSI-PUCCH-ResourceList* is provided by the first *PUCCH-Config*, and *PUCCH-ResourceId* in *pucch-CSI-ResourceList* or *multi-CSI-PUCCH-ResourceList* indicates a corresponding PUCCH resource in *PUCCH-Resource* provided by the first *PUCCH-Config*. + +If a UE is provided only one PUCCH resource set for transmission of HARQ-ACK information in response to PDSCH reception scheduled by a DCI format or in response to a DCI format having associated HARQ-ACK information without scheduling PDSCH reception, the UE does not expect to be provided *simultaneousHARQ-ACK-CSI*. + +A UE is configured by *maxCodeRate* a code rate for multiplexing HARQ-ACK, SR, and CSI report(s) in a PUCCH transmission using PUCCH format 2, PUCCH format 3, or PUCCH format 4. + +If a UE transmits CSI reports using PUCCH format 2, the UE transmits only wideband CSI for each CSI report [6, TS 38.214]. In the following, a Part 1 CSI report refers either to a CSI report with only wideband CSI or to a Part 1 CSI report with wideband CSI and sub-band CSI. + +Denote as + +- $O_{ACK}$ a total number of HARQ-ACK information bits, if any +- $O_{SR}$ a total number of SR bits. $O_{SR} = 0$ if there is no scheduling request bit; otherwise, $O_{SR} = \lceil \log_2 (K + 1) \rceil$ as described in clause 9.2.5.1 +- $O_{CSI} = \sum_{n=1}^{N_{CSI}^{total}} (O_{CSI-part1,n} + O_{CSI-part2,n})$ , where $O_{CSI-part1,n}$ is a number of Part 1 CSI report bits for CSI report with priority value $n$ , $O_{CSI-part2,n}$ is a number of Part 2 CSI report bits, if any, for CSI report with priority value $n$ [6, TS 38.214], and $N_{CSI}^{total}$ is a number of CSI reports that include overlapping CSI reports +- $O_{CRC} = O_{CRC,CSI-part1} + O_{CRC,CSI-part2}$ , where $O_{CRC,CSI-part1}$ is a number of CRC bits, if any, for encoding HARQ-ACK, SR and Part 1 CSI report bits and $O_{CRC,CSI-part2}$ is a number of CRC bits, if any, for encoding Part 2 CSI report bits + +In the following + +- is a code rate given by *maxCodeRate* as in Table 9.2.5.2-1. +- $M_{RB}^{PUCCH}$ is a number of PRBs provided by *nrofPRBs*; otherwise, if *nrofPRBs* is not provided, $M_{RB}^{PUCCH} = 1$ +- $N_{sc,ctrl}^{RB} = N_{sc}^{RB} - 4$ for PUCCH format 2 or, if the PUCCH resource with PUCCH format 2 includes an orthogonal cover code with length $N_{SF}^{PUCCH,2}$ provided by *occ-Length*, $N_{sc,ctrl}^{RB} = (N_{sc}^{RB} - 4) / N_{SF}^{PUCCH,2}$ , $N_{sc,ctrl}^{RB} = N_{sc}^{RB}$ for PUCCH format 3 or, if the PUCCH resource with PUCCH format 3 includes an orthogonal cover code with length $N_{SF}^{PUCCH,3}$ provided by *occ-Length*, $N_{sc,ctrl}^{RB} = N_{sc}^{RB} / N_{SF}^{PUCCH,3}$ , and $N_{sc,ctrl}^{RB} = N_{sc}^{RB} / N_{SF}^{PUCCH,4}$ for PUCCH format 4, where $N_{sc}^{RB}$ is a number of subcarriers per resource block [4, TS 38.211] +- $N_{symb-UCI}^{PUCCH}$ is equal to a number of PUCCH symbols $N_{symb}^{PUCCH,2}$ for PUCCH format 2 provided by *nrofSymbols* in *PUCCH-format2*. For PUCCH format 3 or for PUCCH format 4, $N_{symb-UCI}^{PUCCH}$ is equal to a number of PUCCH symbols $N_{symb}^{PUCCH,3}$ for PUCCH format 3 or equal to a number of PUCCH symbols $N_{symb}^{PUCCH,4}$ for PUCCH format 4 provided by *nrofSymbols* in *PUCCH-format3* or *nrofSymbols* in *PUCCH-format4*, respectively, after excluding a number of symbols used for DM-RS transmission for PUCCH format 3 or for PUCCH format 4, respectively [4, TS 38.211] +- $Q_m = 1$ if pi/2-BPSK is the modulation scheme and $Q_m = 2$ if QPSK is the modulation scheme as indicated by *pi2BPSK* for PUCCH format 3 or PUCCH format 4. For PUCCH format 2, $Q_m = 2$ + +If a UE has one or more CSI reports and zero or more HARQ-ACK/SR information bits to transmit in a PUCCH where the HARQ-ACK, if any, is in response to a PDSCH reception without a corresponding PDCCH + +- if any of the CSI reports are overlapping and the UE is provided by *multi-CSI-PUCCH-ResourceList* with $J \leq 2$ PUCCH resources in a slot, for PUCCH format 2 and/or PUCCH format 3 and/or PUCCH format 4, as described in clause 9.2.1, where the resources are indexed according to an ascending order for the product of a number of corresponding REs, modulation order $Q_m$ , and configured code rate $r$ ; + +- if $(O_{ACK} + O_{SR} + O_{CSI} + O_{CRC}) \leq (M_{RB}^{PUCCH} \cdot N_{sc,ctrl}^{RB} \cdot N_{symb-UCI}^{PUCCH} \cdot Q_m \cdot r)_0$ , the UE uses PUCCH format 2 resource $O_0$ , or the PUCCH format 3 resource $O_0$ , or the PUCCH format 4 resource $O_0$ +- else if $(O_{ACK} + O_{SR} + O_{CSI} + O_{CRC}) > (M_{RB}^{PUCCH} \cdot N_{sc,ctrl}^{RB} \cdot N_{symb-UCI}^{PUCCH} \cdot Q_m \cdot r)_j$ and $(O_{ACK} + O_{SR} + O_{CSI} + O_{CRC}) \leq (M_{RB}^{PUCCH} \cdot N_{sc,ctrl}^{RB} \cdot N_{symb-UCI}^{PUCCH} \cdot Q_m \cdot r)_{j+1}$ , $0 \leq j < J - 1$ , the UE transmits a PUCCH conveying HARQ-ACK information, SR and CSI report(s) in a respective PUCCH where the UE uses the PUCCH format 2 resource $j + 1$ , or the PUCCH format 3 resource $j + 1$ , or the PUCCH format 4 resource $j + 1$ +- else the UE uses the PUCCH format 2 resource $J - 1$ , or the PUCCH format 3 resource $J - 1$ , or the PUCCH format 4 resource $J - 1$ and the UE selects $N_{CSI}^{reported}$ CSI report(s) for transmission together with HARQ-ACK information and SR, when any, in ascending priority value as described in [6, TS 38.214] +- else, the UE transmits the $O_{ACK} + O_{SR} + O_{CSI} + O_{CRC}$ bits in a PUCCH resource provided by *pucch-CSI-ResourceList* and determined as described in clause 9.2.5 + +If a UE has HARQ-ACK, SR and wideband or sub-band CSI reports to transmit and the UE determines a PUCCH resource with PUCCH format 2, or the UE has HARQ-ACK, SR and wideband CSI reports [6, TS 38.214] to transmit and the UE determines a PUCCH resource with PUCCH format 3 or PUCCH format 4, where + +- the UE determines the PUCCH resource using the PUCCH resource indicator field [5, TS 38.212] in a last of a number of DCI formats, excluding the SPS activation DCI, with a value of a PDSCH-to-HARQ\_feedback timing indicator field, if present, or a value of *dl-DataToUL-ACK*, or *dl-DataToUL-ACK-r16*, or *dl-DataToUL-ACK-DCI-1-2*, or *dl-DataToUL-ACK-r17*, or *dl-DataToUL-ACK-DCI-1-2-r17*, indicating a same slot for the PUCCH transmission, from a PUCCH resource set provided to the UE for HARQ-ACK transmission, and +- the UE determines the PUCCH resource set as described in clause 9.2.1 and clause 9.2.3 for UCI bits + +and + +- if $O_{ACK} + O_{SR} + O_{CSI} + O_{CRC} \leq N_{PRB}^{PUCCH} \cdot N_{sc,ctrl}^{RB} \cdot N_{symb-UCI}^{PUCCH} \cdot Q_m \cdot r$ , the UE transmits the HARQ-ACK, SR, and CSI reports bits by selecting the minimum number of the PRBs satisfying $O_{ACK} + O_{SR} + O_{CSI} + O_{CRC} \leq N_{PRB}^{PUCCH} \cdot N_{sc,ctrl}^{RB} \cdot N_{symb-UCI}^{PUCCH} \cdot Q_m \cdot r$ as described in clauses 9.2.3 and 9.2.5.1; +- else, the UE selects CSI report(s), from the CSI reports, for transmission together with HARQ-ACK and SR in ascending priority value [6, TS 38.214], where the value of $O_{CSI}$ satisfies $O_{ACK} + O_{SR} + O_{CSI} + O_{CRC} \leq N_{PRB}^{PUCCH} \cdot N_{sc,ctrl}^{RB} \cdot N_{symb-UCI}^{PUCCH} \cdot Q_m \cdot r$ , where $O_{CSI}$ is a number of CRC bits corresponding to UCI bits, and $O_{CRC}$ is a number of CRC bits corresponding to UCI bits. + +If a UE is provided a first interlace of PRBs by *interlace0* in *InterlaceAllocation*, the UE has HARQ-ACK, SR and wideband or sub-band CSI reports to transmit, and the UE determines a PUCCH resource with PUCCH format 2, or the UE has HARQ-ACK, SR and wideband CSI reports to transmit and the UE determines a PUCCH resource with PUCCH format 3, where + +- the UE determines the PUCCH resource using the PUCCH resource indicator field in a last of a number of DCI formats, excluding the SPS activation DCI, with a value of a PDSCH-to-HARQ\_feedback timing indicator field, or a value provided by *dl-DataToUL-ACK* or *dl-DataToUL-ACK-r16* or *dl-DataToUL-ACK-DCI-1-2* or *dl-DataToUL-ACK-r17* or *dl-DataToUL-ACK-DCI-1-2-r17* if the PDSCH-to-HARQ\_feedback timing indicator field is not present in a DCI format, indicating a same slot for the PUCCH transmission, from a PUCCH resource set provided to the UE for HARQ-ACK transmission, and +- the UE determines the PUCCH resource set as described in clauses 9.2.1 and 9.2.3 for UCI bits + +and + +- if $O_{ACK} + O_{SR} + O_{CSI} + O_{CRC} \leq N_{PRB}^{PUCCH} \cdot N_{sc,ctrl}^{RB} \cdot N_{symb-UCI}^{PUCCH} \cdot Q_m \cdot r$ , the UE transmits the HARQ-ACK, SR, and CSI reports bits in a PUCCH over the first interlace +- else, if the UE is provided a second interlace of PRBs by *interlace1* and if $O_{ACK} + O_{SR} + O_{CSI} + O_{CRC} \leq N_{PRB}^{PUCCH} \cdot N_{sc,ctrl}^{RB} \cdot N_{symb-UCI}^{PUCCH} \cdot Q_m \cdot r$ , the UE transmits the HARQ-ACK, SR, and CSI reports bits in a PUCCH over both the first and second interlaces + +- else, the procedure is same as the corresponding one when the UE is provided *PUCCH-ResourceSet* by replacing with , or, if the UE is provided *interlace1*, by . + +If a UE has HARQ-ACK, SR and sub-band CSI reports to transmit and the UE determines a PUCCH resource with PUCCH format 3 or PUCCH format 4, where + +- the UE determines the PUCCH resource using the PUCCH resource indicator field [5, TS 38.212] in a last of a number of DCI formats, excluding the SPS activation DCI, with a value of a PDSCH-to-HARQ\_feedback timing indicator field indicating a same slot for the PUCCH transmission, or by a value provided by *dl-DataToUL-ACK* or *dl-DataToUL-ACK-r16* or *dl-DataToUL-ACK-DCI-1-2* or *dl-DataToUL-ACK-r17* or *dl-DataToUL-ACK-DCI-1-2-r17* if the PDSCH-to-HARQ\_feedback timing indicator field is not present in the last DCI format, from a PUCCH resource set provided to the UE for HARQ-ACK transmission, and +- the UE determines the PUCCH resource set as described in clause 9.2.1 and clause 9.2.3 for UCI bits + +and + +- if $(O_{ACK} + O_{SR} + O_{CSI} + O_{CRC}) \leq M_{RB}^{PUCCH} \cdot N_{sc,ctrl}^{RB} \cdot N_{symb-UCI}^{PUCCH} \cdot Q_m \cdot r$ , the UE transmits the HARQ-ACK, SR and the $N_{CSI}^{total}$ CSI report bits by selecting the minimum number $M_{RB,min}^{PUCCH}$ of PRBs from the $M_{RB}^{PUCCH}$ PRBs satisfying $(O_{ACK} + O_{SR} + O_{CSI} + O_{CRC}) \leq M_{RB,min}^{PUCCH} \cdot N_{sc,ctrl}^{RB} \cdot N_{symb-UCI}^{PUCCH} \cdot Q_m \cdot r$ as described in clauses 9.2.3 and 9.2.5.1 + +- else, + +- if for $N_{CSI-part2}^{reported} > 0$ Part 2 CSI report priority value(s), it is + +$$\sum_{n=1}^{N_{CSI-part2}^{reported}} O_{CSI-part2,n} + O_{CRC,CSI-part2,N} \leq \left( M_{RB}^{PUCCH} \cdot N_{sc,ctrl}^{RB} \cdot N_{symb-UCI}^{PUCCH} - \left[ \left( O_{ACK} + O_{SR} + \sum_{n=1}^{N_{CSI}^{total}} O_{CSI-part1,n} + O_{CRC,CSI-part1} \right) / (Q_m \cdot r) \right] \right) \cdot Q_m \cdot r$$ + +and + +$$\sum_{n=1}^{N_{CSI-part2}^{reported} + 1} O_{CSI-part2,n} + O_{CRC,CSI-part2,N+1} > \left( M_{RB}^{PUCCH} \cdot N_{sc,ctrl}^{RB} \cdot N_{symb-UCI}^{PUCCH} - \left[ \left( O_{ACK} + O_{SR} + \sum_{n=1}^{N_{CSI}^{total}} O_{CSI-part1,n} + O_{CRC,CSI-part1} \right) / (Q_m \cdot r) \right] \right) \cdot Q_m \cdot r$$ + +, + +the UE selects the first $N_{CSI-part2}^{reported}$ Part 2 CSI reports, according to respective priority value(s) [6, TS 38.214], for transmission together with the HARQ-ACK, SR and $N_{CSI}^{total}$ Part 1 CSI reports , where $O_{CSI-part1,n}$ is the number of Part 1 CSI report bits for the $n_{th}$ CSI report and $O_{CSI-part2,n}$ is the number of Part 2 CSI report bits + +for the $n_{th}$ CSI report priority value, $O_{CRC,CSI-part2,N}$ is a number of CRC bits corresponding to $\sum_{n=1}^{N_{CSI-part2}^{reported}} O_{CSI-part2,n}$ , + +and $O_{CRC,CSI-part2,N+1}$ is a number of CRC bits corresponding to $\sum_{n=1}^{N_{CSI-part2}^{reported} + 1} O_{CSI-part2,n}$ + +- else, the UE drops all Part 2 CSI reports and selects $N_{CSI-part1}^{reported}$ Part 1 CSI report(s), from the $N_{CSI}^{total}$ CSI reports in ascending priority value [6, TS 38.214], for transmission together with the HARQ-ACK and SR + +information bits where the value of $N_{CSI-part1}^{reported}$ satisfies + +$$\left( O_{ACK} + O_{SR} + \sum_{n=1}^{N_{CSI-part1}^{reported}} O_{CSI-part1,n} + O_{CRC,CSI-part1,N} \right) \leq M_{RB}^{PUCCH} \cdot N_{sc,ctrl}^{RB} \cdot N_{symb-UCI}^{PUCCH} \cdot Q_m \cdot r$$ + +and + +$$\left( O_{ACK} + O_{SR} + \sum_{n=1}^{N_{CSI-part1}^{reported} + 1} O_{CSI-part1,n} + O_{CRC,CSI-part1,N+1} \right) > M_{RB}^{PUCCH} \cdot N_{sc,ctrl}^{RB} \cdot N_{symb-UCI}^{PUCCH} \cdot Q_m \cdot r$$ + +, where $O_{CRC,CSI-part1,N}$ is + +$$\begin{aligned} + &\text{a number of CRC bits corresponding to } O_{\text{ACK}} + O_{\text{SR}} + \sum_{n=1}^{N_{\text{CSI-part1}}^{\text{reported}}} O_{\text{CSI-part1},n} \text{ UCI bits, and } O_{\text{CRC, CSI-part1}, N+1} \text{ is a} \\ + &\text{number of CRC bits corresponding to } O_{\text{ACK}} + O_{\text{SR}} + \sum_{n=1}^{N_{\text{CSI-part1}}^{\text{reported}} + 1} O_{\text{CSI-part1},n} \text{ UCI bits.} + \end{aligned}$$ + +If a UE is provided a first interlace of PRBs by *interlace0* in *InterlaceAllocation*, the UE has HARQ-ACK, SR and sub-band CSI reports to transmit, and the UE determines a PUCCH resource with PUCCH format 3, where + +- the UE determines the PUCCH resource using the PUCCH resource indicator field in a last of a number of DCI formats, excluding the SPS activation DCI, that have a value of a PDSCH-to-HARQ\_feedback timing indicator field indicating a same slot for the PUCCH transmission, or a value provided by *dl-DataToUL-ACK* or *dl-DataToUL-ACK-r16* or *dl-DataToUL-ACK-DCI-1-2* or *dl-DataToUL-ACK-r17* or *dl-DataToUL-ACK-DCI-1-2-r17* if the PDSCH-to-HARQ\_feedback timing indicator field is not present in the last DCI format, from a PUCCH resource set provided to the UE for HARQ-ACK transmission, and + - the UE determines the PUCCH resource set as described in clauses 9.2.1 and 9.2.3 for UCI bits +- and +- if , the UE transmits the HARQ-ACK, SR and the CSI report bits in a PUCCH over the first interlace + - else if the UE is provided a second interlace of PRBs by *interlace1* and if , the UE transmits the HARQ-ACK, SR, and CSI reports bits in a PUCCH over both the first and second interlaces + - else, the procedure is same as the corresponding one when the UE is provided *PUCCH-ResourceSet* by replacing with , or, if the UE is provided *interlace1*, with . + +**Table 9.2.5.2-1: Code rate corresponding to value of *maxCodeRate*** + +| maxCodeRate
e | Code rate | +|--------------------------------|-----------| +| 0 | 0.08 | +| 1 | 0.15 | +| 2 | 0.25 | +| 3 | 0.35 | +| 4 | 0.45 | +| 5 | 0.60 | +| 6 | 0.80 | +| 7 | Reserved | + +#### 9.2.5.3 UE procedure for reporting UCI of different priorities + +If a UE + +- is provided *PUCCH-ConfigurationList* for PUCCH transmissions with priority 0 and 1, +- is provided *uci-MuxWithDiffPrio*, and +- would transmit overlapping PUCCHs that include a first PUCCH with HARQ-ACK information bits of priority 0 and a second PUCCH with HARQ-ACK information bits of priority 1 + - if the PUCCH resource for the second PUCCH includes PUCCH format 2, 3, or 4 and additionally includes SR bits of priority 1, is replaced by where is determined according to clause 9.2.5.1 + +the UE + +- determines + - a PUCCH resource set from the second *PUCCH-Config* using as described in clause 9.2.1, and a PUCCH resource from the PUCCH resource set as described in clause 9.2.3 where a DCI format, if any, triggers PUCCH transmission of priority 1, or + +- a PUCCH resource from the second *sps-PUCCH-AN-List* using as described in clause 9.2.1, and +- multiplexes the and HARQ-ACK information bits in a same PUCCH using the PUCCH resource. + +If the PUCCH resource includes PUCCH format 2 or PUCCH format 3 and PRBs, the UE determines a number of PRBs for the PUCCH transmission to be the minimum number of PRBs that starts from the first PRB from the PRBs and results to + +where or is a number of CRC bits, if any, for encoding the or the HARQ-ACK information bits, respectively, is provided by *maxCodeRateLP*, and the remaining parameters are as defined in clause 9.2.5.2 with . For PUCCH format 3, if is not equal to [4, TS 38.211], is increased to a nearest value that is equal to and does not exceed *nrofPRBs*. + +If , the UE transmits the PUCCH over the PRBs. + +If a UE transmits a PUCCH that includes HARQ-ACK information bits of priority 0 and 1 using a PUCCH resource that includes PUCCH format 2, 3 or 4, the UE determines a power for the PUCCH transmission as described in clause 7.2.1 assuming that the PUCCH includes only UCI bits of priority 1, where . If bits, replaces in the calculation in clause 7.2.1; otherwise, replaces in the calculation in clause 7.2.1. + +If a UE transmits a PUCCH that includes one HARQ-ACK information bit of priority 0 and one HARQ-ACK information bit of priority 1 + +- if the PUCCH transmission uses a resource that includes PUCCH format 0, the HARQ-ACK information bits of priority 1 and priority 0 are set as the first and second bits in Table 9.2.3-4, respectively, to derive the of the PUCCH transmission +- if the PUCCH transmission uses a resource that includes PUCCH format 1, the HARQ-ACK information bits of priority 1 and priority 0 are the first and second bits, respectively, of the QPSK modulated symbol for the PUCCH transmission + +If a UE transmits a PUCCH that includes HARQ-ACK information bits of priority 0 and 1 using PUCCH format 1, the UE determines a power for the PUCCH transmission as described in clause 7.2.1 assuming that all HARQ-ACK information bits have priority 1. + +If a UE is provided a first interlace of PRBs by *interlace0* in *InterlaceAllocation* + +- if the UE is provided a second interlace of PRBs by *interlace1* in *InterlaceAllocation* + - if , the UE transmits the PUCCH over the first interlace + - else, the UE transmits the PUCCH over both the first and second interlaces +- else the UE transmits the PUCCH over the first interlace + +If the UE transmits a PUCCH that includes HARQ-ACK information bits of priority 0 and 1 over interlaces, the UE determines a power for the PUCCH transmission as described in clause 7.2.1 assuming that the PUCCH includes only UCI bits of priority 1. + +#### 9.2.5.4 UE procedure for deferring HARQ-ACK for SPS PDSCH + +If a UE is provided *sps-HARQ-Deferral* and, after performing the procedures in clauses 9 and 9.2.5 to resolve overlapping among PUCCHs and PUSCHs in a first slot, if any, the UE determines a PUCCH resource for a PUCCH transmission with first HARQ-ACK information bits for SPS PDSCH receptions that the UE would report for a first time, and the PUCCH resource + +- is provided by *SPS-PUCCH-AN-List* as described in clause 9.2.1, or by *nIPUCCH-AN* if *SPS-PUCCH-AN-List* is not provided +- is not cancelled by an overlapping PUCCH or PUSCH transmission of larger priority index +- overlaps with a symbol indicated as downlink by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigDedicated*, or indicated for a SS/PBCH block by *ssb-PositionsInBurst*, or belonging to a CORESET associated with a Type0-PDCCH CSS set + +the UE + +- determines an earliest second slot and, after performing the procedures in clauses 9.2.1 and 9.2.3 to determine a PUCCH with third HARQ-ACK information bits including second HARQ-ACK information bits and then performing the procedures in clauses 9 and 9.2.5 to resolve overlapping among PUCCHs and PUSCHs, if any, a PUSCH or a PUCCH in the earliest second slot to multiplex the third HARQ-ACK information bits that include second HARQ-ACK information bits from the first HARQ-ACK information bits , where the second HARQ-ACK information bits correspond to SPS PDSCH configurations with *sps-HARQ-Deferral* values that are larger than or equal to a time difference, with reference to slots for PUCCH transmissions on the primary cell, between the second slot and the slot of the SPS PDSCH reception, if any +- if the UE detects a DCI format in a PDCCH reception that triggers a PUCCH transmission with a Type-3 HARQ-ACK codebook in a slot as described in clause 9.1.4, the UE stops the procedure to determine the earliest second slot in the slot +- if the UE is provided a periodic cell switching pattern for PUCCH transmissions by *pucch-sSCellPattern*, the UE determines the earliest second slot and a corresponding cell based on the periodic cell switching pattern as described in clause 9.A +- if the UE multiplexes the second HARQ-ACK information in a PUSCH, or in a PUCCH using a resource that is not from *SPS-PUCCH-AN-List*, or from *n1PUCCH-AN* if *SPS-PUCCH-AN-List* is not provided, the UE stops the procedure to determine the earliest second slot in the slot +- if the UE multiplexes the second HARQ-ACK information in a first PUCCH using a resource provided by *SPS-PUCCH-AN-List*, or by *n1PUCCH-AN* if *SPS-PUCCH-AN-List* is not provided, of smaller priority index and the UE drops the first PUCCH transmission due to an overlapping with a second PUSCH or PUCCH transmission of larger priority index, the UE stops the procedure to determine the earliest second slot in the slot +- if the UE multiplexes the second HARQ-ACK information in a first PUCCH using a resource provided by *SPS-PUCCH-AN-List*, or by *n1PUCCH-AN* if *SPS-PUCCH-AN-List* is not provided, and the PUCCH transmission is not dropped due to an overlapping with a PUSCH or PUCCH transmission of larger priority and does not have any symbol that overlaps with a symbol indicated as downlink by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigDedicated*, or indicated for a SS/PBCH block by *ssb-PositionsInBurst*, or belonging to a CORESET associated with a Type0-PDCCH CSS set, the UE stops the procedure to determine the earliest second slot in the slot +- the second HARQ-ACK information bits, generated as described in clause 9.1.2, are appended to fourth HARQ-ACK information bits the UE generates as described in clauses 9.1.2, 9.1.2.1, 9.1.3.1, or 9.1.5 +- if the UE would receive a PDSCH providing a TB for a same HARQ process as a HARQ-ACK information bit from the second HARQ-ACK information bits prior to transmitting the PUCCH or the PUSCH, the UE does not include the HARQ-ACK information bit in the second HARQ-ACK information bits. + +The UE does not expect to be provided both *sps-HARQ-Deferral* and *nrofSlots* or *pucch-RepetitionNrofSlots* for any PUCCH resource of same priority. + +is the number of the third HARQ-ACK information bits. + +If , the UE determines a number of HARQ-ACK information bits for obtaining a transmission power for a PUCCH transmission in the second slot, as described in clause 7.2.1, as where + +- is the number of HARQ-ACK information bits, if any, that the UE determines as described in clause 9.1.2.1, 9.1.3.1 or 9.1.5 for the fourth HARQ-ACK information bits, +- is determined as described in clause 9.1.2.1 or 9.1.3.1 for the second HARQ-ACK information bits. + +### 9.2.6 PUCCH repetition procedure + +A UE that does not have dedicated PUCCH resource configuration and indicates a capability to transmit with repetitions a PUCCH with HARQ-ACK information [11, TS 38.321], determines a number of slots for repetitions of a PUCCH transmission with HARQ-ACK information based on an indication by *numberOfPUCCHforMsg4HARQACK-RepetitionsList*. If *numberOfPUCCHforMsg4HARQACK-RepetitionsList* provides more than one values, the DAI field in a DCI format 1\_0 with CRC scrambled by a TC-RNTI scheduling a PDSCH reception that includes a UE contention + +resolution identity indicates from the more than one values. The UE transmits any PUCCH with repetitions over slots before dedicated PUCCH resource configuration is provided. The UE transmits each repetition of the PUCCH using frequency hopping as described in Clause 9.2.1. + +In the remaining of this clause, a UE without dedicated PUCCH resource configuration determines a value of a parameter, if applicable, according to Table 9.2.1-1 and/or as specified above in this clause for a PUCCH transmission with repetitions from the UE. + +A UE can be indicated to transmit a PUCCH over slots using a PUCCH resource, where + +- if the PUCCH resource is indicated by a DCI format and includes *pucch-RepetitionNrofSlots*, is provided by *pucch-RepetitionNrofSlots* +- otherwise, is provided by *nrofSlots* + +If the UE is provided *subslotLengthForPUCCH*, a slot for a PUCCH transmission with repetitions over slots includes a number of symbols indicated by *subslotLengthForPUCCH*. + +For , + +- the UE repeats the PUCCH transmission with the UCI over slots + - if the UE is provided *multipanelSfnScheme* and *apply-IndicatedTCIState* = 'both', a repetition of the PUCCH transmission uses first and second spatial domain filters corresponding to first and second *TCI-State* or *TCI-UL-State* +- a repetition of the PUCCH transmission in each of the slots has a same number of consecutive symbols, as provided by *nrofSymbols* +- a repetition of the PUCCH transmission in each of the slots has a same first symbol, as provided by *startingSymbolIndex* if *subslotLengthForPUCCH* is not provided; otherwise $\text{mod}(\text{startingSymbolIndex}, \text{subslotLengthForPUCCH})$ +- the UE is configured by *interslotFrequencyHopping* whether or not to perform frequency hopping for repetitions of the PUCCH transmission in different slots + - if the UE is configured to perform frequency hopping for repetitions of a PUCCH transmission across slots and the UE is not provided *pucch-DMRS-Bundling* = 'enabled' + - the UE performs frequency hopping per slot + - the UE transmits the PUCCH starting from a first PRB, provided by *startingPRB*, in slots with even number and starting from a second PRB, provided by *secondHopPRB*, in slots with odd number. The slot indicated to the UE for the first repetition of the PUCCH transmission has number 0 and each subsequent slot until the UE transmits the PUCCH in slots is counted regardless of whether or not the UE transmits the PUCCH in the slot + - the UE does not expect to be configured to perform frequency hopping for a repetition of the PUCCH transmission within a slot + - if the UE is configured to perform frequency hopping for repetitions of a PUCCH transmission across slots and the UE is provided *pucch-DMRS-Bundling* = 'enabled' + - the UE performs frequency hopping per interval of consecutive slots, that start from a slot indicated to the UE and where the UE would transmit a first repetition of the PUCCH, where is the value of *pucch-FrequencyHoppingInterval*, if provided; otherwise, is the value of *pucch-TimeDomainWindowLength* + - the UE transmits the PUCCH over intervals until the UE transmits the PUCCH in slots, where the first interval has number 0 and each subsequent interval is counted regardless of whether or not the UE transmits the PUCCH in a slot + - the UE transmits the PUCCH starting from a first PRB, provided by *startingPRB*, in intervals with even number and starting from a second PRB, provided by *secondHopPRB*, in intervals of frequency hopping intervals with odd number + +- the UE does not expect to be configured to perform frequency hopping for a repetition of the PUCCH transmission within a slot +- if the UE is not configured to perform frequency hopping for repetitions of a PUCCH transmission across slots and the UE is configured to perform frequency hopping for a repetition of the PUCCH transmission within a slot, the frequency hopping pattern between the first PRB and the second PRB is same within each slot + +If the UE determines that, for a repetition of a PUCCH transmission in a slot, the number of symbols available for the PUCCH transmission is smaller than the value provided by *nrofSymbols* for the corresponding PUCCH format, the UE does not transmit the PUCCH repetition in the slot. + +A SS/PBCH block symbol is a symbol of an SS/PBCH block with candidate SS/PBCH block index corresponding to the SS/PBCH block index indicated to a UE by *ssb-PositionsInBurst* in *SIB1* or *ssb-PositionsInBurst* in *ServingCellConfigCommon* or, if the UE is not provided *dl-OrJointTCI-StateList*, by *ssb-PositionsInBurst* in *SSB-MTCAdditionalPCI* associated to physical cell ID with active TCI states for PDCCH or PDSCH, or for a set of symbols of a slot corresponding to SS/PBCH blocks configured for L1 beam measurement/reporting. + +For unpaired spectrum, the UE determines the slots for a PUCCH transmission starting from a slot indicated to the UE as described in clause 9.2.3 for HARQ-ACK reporting, or a slot determined as described in clause 9.2.4 for SR reporting or in clause 5.2.1.4 of [6, TS 38.214] for CSI reporting and having + +- an UL symbol, as described in clause 11.1, or flexible symbol that is not SS/PBCH block symbol provided by *startingSymbolIndex* as a first symbol, and +- consecutive UL symbols, as described in clause 11.1, or flexible symbols that are not SS/PBCH block symbols, starting from the first symbol, equal to or larger than a number of symbols provided by *nrofSymbols* + +For paired spectrum or supplementary uplink band, the UE determines the slots for a PUCCH transmission as the consecutive slots starting from a slot indicated to the UE as described in clause 9.2.3 for HARQ-ACK reporting, or a slot determined as described in clause 9.2.4 for SR reporting or in clause 5.2.1.4 of [6, TS 38.214] for CSI reporting. + +If a UE would transmit a PUCCH over a first number of slots and the UE would transmit a PUSCH with repetition Type A or with TB processing over multiple slots over a second number of slots, and the PUCCH transmission would overlap with the PUSCH transmission in one or more slots, and the conditions in clause 9.2.5 for multiplexing the UCI in the PUSCH are satisfied in the overlapping slots, the UE transmits the PUCCH and does not transmit the PUSCH in the overlapping slots. + +If a UE would transmit a PUCCH over a first number of slots and the UE would transmit a PUSCH with repetition Type B over a second number of slots, and the PUCCH transmission would overlap with actual PUSCH repetitions in one or more slots, and the conditions in clause 9.2.5 for multiplexing the UCI in the PUSCH are satisfied for the overlapping actual PUSCH repetitions, the UE transmits the PUCCH and does not transmit the overlapping actual PUSCH repetitions. + +A UE does not multiplex different UCI types in a PUCCH transmission with repetitions over slots. If a UE would transmit a first PUCCH over more than one slot and at least a second PUCCH over one or more slots, and the transmissions of the first PUCCH and the second PUCCH would overlap in a number of slots then, for each slot of the number of slots and with UCI type priority of HARQ-ACK > SR > CSI with higher priority > CSI with lower priority, the UE determines an earliest first PUCCH in a slot with the order of earliest starting symbol followed by longest duration and the second PUCCHs overlapping with the earliest first PUCCH, and then performs the following + +- the UE does not expect more than one PUCCH from the first PUCCH and the second PUCCHs to start at a same slot and include a UCI type with same priority +- if more than one PUCCH from the first PUCCH and the second PUCCHs include a UCI type with the same highest priority, the UE transmits the PUCCH with the highest priority starting at an earliest slot and does not transmit the other PUCCHs, otherwise, +- the UE transmits the PUCCH that includes the UCI type with the highest priority and does not transmit the PUCCHs that include the UCI type with lower priority + +The UE repeats the above procedure until there is no PUCCH overlapping with any PUCCH with repetitions in the slot. + +When a PUCCH resource used for repetitions of a PUCCH transmission by a UE includes + +- first and second spatial settings, or first and second sets of power control parameters, as described in [11, TS 38.321] and in clauses 7 and 7.2.1, or +- if the UE is provided *multipanelSfnScheme* and *apply-IndicatedTCIState* = 'both', a repetition of the PUCCH transmission uses first and second spatial domain filters corresponding to first and second *TCI-State* or *TCI-UL-State* + +the UE + +- uses the first and second spatial settings or the first and second indicated *TCI-State* or *TCI-UL-State*, or the first and second sets of power control parameters, for first and second repetitions of the PUCCH transmission, respectively, when , +- alternates between the first and second spatial settings or between the first and second indicated *TCI-State* or *TCI-UL-State*, or between the first and second sets of power control parameters, respectively, per repetitions of the PUCCH transmission, where if *mappingPattern* = 'cyclicMapping'; else, . + +A UE does not expect a PUCCH that is in response to a DCI format detection to overlap with any other PUCCH that does not satisfy the corresponding timing conditions in clause 9.2.5. + +If a UE would transmit a PUCCH over slots and the UE does not transmit the PUCCH in a slot from the slots due to overlapping with another PUCCH transmission in the slot, the UE counts the slot in the number of slots. + +For DAPS operation, if a UE would transmit a PUCCH over slots on the source MCG and the UE does not transmit the PUCCH in a slot from the slots due to overlapping in time with UE transmission on the target MCG in the slot, the UE counts the slot in the number of slots. + +## 9.3 UCI reporting in physical uplink shared channel + +Offset values are defined for a UE to determine a number of resources for multiplexing HARQ-ACK information and for multiplexing CSI reports in a PUSCH. Offset values are also defined for multiplexing CG-UCI or UTO-UCI [5, TS 38.212] in a CG-PUSCH. The offset values are signalled to a UE either by a DCI format scheduling the PUSCH transmission or by higher layers. + +If a DCI format that does not include a *beta\_offset* indicator field schedules the PUSCH transmission from the UE and the UE is provided *betaOffsets* = 'semiStatic' or *betaOffsetsDCI-0-2* = 'semiStaticDCI-0-2', the UE applies the , , and values that are provided by *betaOffsets* = 'semiStatic' for DCI formats 0\_0/0\_1/0\_3 or by *betaOffsetsDCI-0-2* = 'semiStaticDCI-0-2' for DCI format 0\_2 for the corresponding HARQ-ACK information, Part 1 CSI reports and Part 2 CSI reports. If the PUSCH transmission has priority 0 or priority 1 and the UE is configured by *uci-MuxWithDiffPrio* to multiplex HARQ-ACK information of priority 1 or priority 0, respectively, and if the UE multiplexes HARQ-ACK information of priority 1 or priority 0, the UE applies corresponding or provided by *betaOffsetsCrossPri1* = 'semiStatic' for DCI formats 0\_0/0\_1/0\_3 and by *betaOffsetsCrossPri1DCI-0-2* = 'semiStatic' for DCI format 0\_2, or by *betaOffsetsCrossPri0* = 'semiStatic' for DCI format 0\_0/0\_1/0\_3 and by *betaOffsetsCrossPri0DCI-0-2* = 'semiStatic' for DCI format 0\_2, respectively. + +If the PUSCH transmission is with a configured grant and the UE is provided *CG-UCI-OnPUSCH* = 'semiStatic', the UE applies the , , and values that are provided by *CG-UCI-OnPUSCH* = 'semiStatic' for the corresponding HARQ-ACK information, Part 1 CSI reports and Part 2 CSI reports. If the PUSCH transmission has priority 0 or priority 1 and the UE is configured by *uci-MuxWithDiffPrio* to multiplex HARQ-ACK information of priority 1 or priority 0, respectively, and if the UE multiplexes HARQ-ACK information of priority 1 or priority 0, the UE applies corresponding or provided by *cg-betaOffsetsCrossPri1* = 'semiStatic' or *cg-betaOffsetsCrossPri0* = 'semiStatic', respectively. + +If the PUSCH transmission is scheduled by DCI format 0\_0 and the UE is provided *betaOffsets* = 'dynamic', the UE applies the , , and values that are determined from the first value of *betaOffsets* = 'dynamic'. If the UE is configured by *uci-MuxWithDiffPrio* to multiplex HARQ-ACK information of priority 1, the UE applies corresponding provided by the first value of *betaOffsetsCrossPri1* = 'dynamic'. + +If the PUSCH transmission is a configured grant Type 2 PUSCH and the UE is provided *CG-UCI-OnPUSCH* = 'dynamic', the UE applies the , , and values that are determined from the first value of *CG-UCI-OnPUSCH* = 'dynamic'. If the PUSCH transmission has priority 0 or priority 1 and the UE is configured by *uci-MuxWithDiffPrio* to multiplex HARQ-ACK information of priority 1 or priority 0, respectively, and if the UE multiplexes HARQ-ACK information of priority 1 or priority 0, the UE applies corresponding or provided by the first value of *cg-betaOffsetsCrossPri1* = 'dynamic' or *cg-betaOffsetsCrossPri0* = 'dynamic', respectively. + +HARQ-ACK information offsets are configured to values according to Table 9.3-1. The *betaOffsetACK-Index1*, *betaOffsetACK-Index2*, and *betaOffsetACK-Index3* respectively provide indexes , , and for the UE to use if the UE multiplexes up to 2 HARQ-ACK information bits, more than 2 and up to 11 HARQ-ACK information bits, and more than 11 bits in the PUSCH, respectively. + +Offsets for multiplexing HARQ-ACK information with priority 0 in a PUSCH transmission with priority 1 are configured to values according to Table 9.3-1. The first, second and third values provided by any of *betaOffsetsCrossPri0*, *betaOffsetsCrossPri0DCI-0-2*, or *cg-betaOffsetsCrossPri0* respectively provide indexes , , and for the UE to use if the UE multiplexes up to 2 bits, more than 2 and up to 11 bits, and more than 11 bits of HARQ-ACK information with priority 0 in the PUSCH transmission with priority 1, respectively. + +Offsets for multiplexing HARQ-ACK information with priority 1 in a PUSCH transmission with priority 0 are configured to values according to Table 9.3-1. The first, second and third values provided by any of *betaOffsetsCrossPri1*, *betaOffsetsCrossPri1DCI-0-2*, or *cg-betaOffsetsCrossPri1* respectively provide indexes , , and for the UE to use if the UE multiplexes up to 2 bits, more than 2 and up to 11 bits, and more than 11 bits of HARQ-ACK information with priority 1 in the PUSCH transmission with priority 0, respectively. + +Part 1 CSI report and Part 2 CSI report offsets and , respectively, are configured to values according to Table 9.3-2. The *betaOffsetCSI-Part1-Index1* and *betaOffsetCSI-Part2-Index1* respectively provide indexes and for the UE to use if the UE multiplexes up to 11 bits for Part 1 CSI reports or Part 2 CSI reports in the PUSCH. The *betaOffsetCSI-Part1-Index2* and *betaOffsetCSI-Part2-Index2* respectively provide indexes or for the UE to use if the UE multiplexes more than 11 bits for Part 1 CSI reports or Part 2 CSI reports in the PUSCH. + +If a DCI format that includes a *beta\_offset* indicator field with one bit or two bits, as configured by *UCI-OnPUSCH* for DCI format 0\_1 or *UCI-OnPUSCH-DCI-0-2* for DCI format 0\_2 or *UCI-OnPUSCH-DCI-0-3*, schedules the PUSCH transmission from the UE, the UE is provided by each of {*betaOffsetACK-Index1*, *betaOffsetACK-Index2*, *betaOffsetACK-Index3*}, the {first, second, third} values provided by *betaOffsetsCrossPri0*, or *betaOffsetsCrossPri0DCI-0-2*, and the {first, second, third} values provided by *betaOffsetsCrossPri1*, or *betaOffsetsCrossPri1DCI-0-2*, a set of two or four indexes from Table 9.3-1 for multiplexing HARQ-ACK information in the PUSCH transmission and by each of {*betaOffsetCSI-Part1-Index1*, *betaOffsetCSI-Part1-Index2*} a set of two or four indexes, and by each of {*betaOffsetCSI-Part2-Index1*, *betaOffsetCSI-Part2-Index2*} a set of two or four indexes from Table 9.3-2, respectively, for multiplexing Part 1 CSI reports and Part 2 CSI reports, respectively, in the PUSCH transmission. The *beta\_offset* indicator field indicates a value and/or a value, and/or a value, a value and a value from the respective sets of values, with the mapping defined in Table 9.3-3 and in Table 9.3-3A. If the PUSCH transmission has priority 0 or priority 1, and the UE is provided *uci-MuxWithDiffPrio*, and the UE multiplexes HARQ-ACK information of priority 1 or priority 0 in the PUSCH, the UE applies the {first, second, third} values provided by *betaOffsetsCrossPri1* = 'dynamic' for DCI format 0\_1/0\_3, *betaOffsetsCrossPri1DCI-0-2* = 'dynamic' for DCI format 0\_2, or applies the {first, second, third} values provided by *betaOffsetsCrossPri0* = 'dynamic' for DCI format 0\_1/0\_3, *betaOffsetsCrossPri0DCI-0-2* = 'dynamic' for DCI format 0\_2. + +For a PUSCH transmission that is configured by a *ConfiguredGrantConfig* and includes CG-UCI, the UE multiplexes the CG-UCI in the PUSCH transmission using a value provided by *betaOffsetCG-UCI* with the mapping defined in Table 9.3-1. The CG-UCI has same priority value as the PUSCH. If the UE is provided *cg-UCI-Multiplexing* and multiplexes HARQ-ACK information of same priority value as the CG-UCI in the PUSCH transmission, as described in clauses 9 and 9.2.5, the UE jointly encodes the HARQ-ACK information and the CG-UCI [5, TS 38.212] and determines a number of resources for multiplexing the combined information in a PUSCH using which provides indexes and for the UE to use if the UE multiplexes up to 11, and more than 11 combined information bits, respectively. + +For a PUSCH transmission that is configured by a *ConfiguredGrantConfig* and includes UTO-UCI, the UE multiplexes the UTO-UCI in the PUSCH transmission using a value provided by *betaOffsetUTO-UCI* with the mapping defined in Table 9.3-1. The UTO-UCI has same priority value as the PUSCH. If the UE multiplexes HARQ-ACK information of same priority value as the UTO-UCI in the PUSCH transmission, as described in clauses 9 and 9.2.5, the UE jointly encodes the HARQ-ACK information and the UTO-UCI and determines a number of resources for multiplexing the combined information in the PUSCH using which provides indexes and for the UE to use if the UE multiplexes up to 11, and more than 11 combined information bits, respectively. + +**Table 9.3-1: Mapping of beta\_offset values for HARQ-ACK information, CG-UCI, or UTO-UCI and the index signalled by higher layers** + +| or or or or or or or or or or | or or or or | +|-------------------------------|-------------| +| 0 | 1.000 | +| 1 | 2.000 | +| 2 | 2.500 | +| 3 | 3.125 | +| 4 | 4.000 | +| 5 | 5.000 | +| 6 | 6.250 | +| 7 | 8.000 | +| 8 | 10.000 | +| 9 | 12.625 | +| 10 | 15.875 | +| 11 | 20.000 | +| 12 | 31.000 | +| 13 | 50.000 | +| 14 | 80.000 | +| 15 | 126.000 | +| 16 | 0.6 | +| 17 | 0.4 | +| 18 | 0.2 | +| 19 | 0.1 | +| 20 | 0.05 | +| 21 | Reserved | +| 22 | Reserved | +| 23 | Reserved | +| 24 | Reserved | +| 25 | Reserved | +| 26 | Reserved | +| 27 | Reserved | +| 28 | Reserved | +| 29 | Reserved | +| 30 | Reserved | +| 31 | Reserved | + +**Table 9.3-2: Mapping of beta\_offset values for CSI and the index signalled by higher layers** + +| or
or | | +|----------|----------| +| 0 | 1.125 | +| 1 | 1.250 | +| 2 | 1.375 | +| 3 | 1.625 | +| 4 | 1.750 | +| 5 | 2.000 | +| 6 | 2.250 | +| 7 | 2.500 | +| 8 | 2.875 | +| 9 | 3.125 | +| 10 | 3.500 | +| 11 | 4.000 | +| 12 | 5.000 | +| 13 | 6.250 | +| 14 | 8.000 | +| 15 | 10.000 | +| 16 | 12.625 | +| 17 | 15.875 | +| 18 | 20.000 | +| 19 | Reserved | +| 20 | Reserved | +| 21 | Reserved | +| 22 | Reserved | +| 23 | Reserved | +| 24 | Reserved | +| 25 | Reserved | +| 26 | Reserved | +| 27 | Reserved | +| 28 | Reserved | +| 29 | Reserved | +| 30 | Reserved | +| 31 | Reserved | + +**Table 9.3-3: Mapping of four beta\_offset indicator values to offset indexes** + +| beta_offset indicator | ( or or ),
( or or ),
( or or ),
( or ), ( or ) | +|-----------------------|----------------------------------------------------------| +| '00' | 1 st offset index provided by higher layers | +| '01' | 2 nd offset index provided by higher layers | +| '10' | 3 rd offset index provided by higher layers | +| '11' | 4 th offset index provided by higher layers | + +**Table 9.3-3A: Mapping of two beta\_offset indicator values to offset indexes** + +| beta_offset indicator | ( or or ),
( or or ),
( or or ),
( or ), ( or ) | +|-----------------------|----------------------------------------------------------| +| '0' | 1 st offset index provided by higher layers | +| '1' | 2 nd offset index provided by higher layers | + +### 9.3.1 UE procedure for reporting UTO-UCI + +If the UE is provided *nrof\_UTO\_UCI* with value equal to *n* in *configuredGrantConfig* of a CG-PUSCH configuration, the UE multiplexes UTO-UCI represented by a bitmap of *n* bits in each CG-PUSCH transmission for the CG-PUSCH configuration. + +The bits of UTO-UCI, *bi*, have a one-to-one mapping to subsequent CG-PUSCH TOs in ascending order of start time. For unpaired spectrum operation, the subsequent CG-PUSCH TOs exclude invalid ones where a UE does not transmit a PUSCH due to collision of the PUSCH with DL symbol(s) indicated by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* if provided, or with symbol(s) of an SS/PBCH block with index provided by *ssb-PositionsInBurst*, based on the procedures in Clause 11.1. A bit value of '0' indicates that the UE may transmit CG-PUSCH, and a bit value of '1' indicates that the UE will not transmit CG-PUSCH, in a corresponding CG-PUSCH TO. When the UE indicates by UTO-UCI a value of '1' for a CG-PUSCH TO, the UE continues to indicate the value of '1' for the CG-PUSCH TO by UTO-UCI multiplexed in subsequent CG-PUSCH transmissions, and the UE does not transmit CG-PUSCH in the CG-PUSCH TO. + +# 10 UE procedure for receiving control information + +If the UE is configured with a SCG, the UE shall apply the procedures described in this clause for both MCG and SCG except for PDCCH monitoring in Type0/0A/0B/2/2A -PDCCH CSS sets where the UE is not required to apply the procedures in this clause for the SCG + +- When the procedures are applied for MCG, the terms 'secondary cell', 'secondary cells', 'serving cell', 'serving cells' in this clause refer to secondary cell, secondary cells, serving cell, serving cells belonging to the MCG respectively. +- When the procedures are applied for SCG, the terms 'secondary cell', 'secondary cells', 'serving cell', 'serving cells' in this clause refer to secondary cell, secondary cells (not including PSCell), serving cell, serving cells belonging to the SCG respectively. The term 'primary cell' in this clause refers to the PSCell of the SCG. + +A UE monitors a set of PDCCH candidates in one or more CORESETs on the active DL BWP on each activated serving cell configured with PDCCH monitoring according to corresponding search space sets where monitoring implies receiving each PDCCH candidate and decoding according to the monitored DCI formats. + +In the remaining of this clause, when a PDCCH reception by a UE includes two PDCCH candidates from corresponding search space sets, as described in clause 10.1 + +- a PDCCH monitoring occasion is the union of the PDCCH monitoring occasions for the two PDCCH candidates + +- the start of the PDCCH reception is the start of the earlier PDCCH candidate +- the end of the PDCCH reception is the end of the PDCCH candidate that ends later + +The PDCCH reception includes the two PDCCH candidates also when the UE is not required to monitor one of the two PDCCH candidates as described in clauses 10 (except clause 10.4), 11.1, 11.1.1 and 17.2. + +If a UE is provided *monitoringCapabilityConfig* for a serving cell, the UE obtains an indication to monitor PDCCH on the active DL BWP of the serving cell for a maximum number of PDCCH candidates and non-overlapping CCEs + +- per slot, as in Tables 10.1-2 and 10.1-3, if *monitoringCapabilityConfig* = *r15monitoringcapability*, or +- per span, as in Tables 10.1-2A and 10.1-3A, if *monitoringCapabilityConfig* = *r16monitoringcapability*, or +- per group of slots according to combination, as in Tables 10.1-2B and 10.1-3B, if *monitoringCapabilityConfig* = *r17monitoringcapability* + +The remaining of this clause, including clause 10.1, considers that a UE is provided *monitoringCapabilityConfig* for a serving cell. If the UE is not provided *monitoringCapabilityConfig* for the serving cell, corresponding statements that the UE is provided *monitoringCapabilityConfig* for the serving cell are substituted as follows + +- for SCS configuration, the UE monitors PDCCH on the active DL BWP of the serving cell for maximum numbers of PDCCH candidates and non-overlapping CCEs per slot as in Tables 10.1-2 and 10.1-3. +- for SCS configuration, the UE monitors PDCCH on the active DL BWP of the serving cell for maximum numbers of PDCCH candidates and non-overlapping CCEs per group of slots according to combination for and for as in Tables 10.1-2B and 10.1-3B. + +The UE does not expect to monitor PDCCH with SCS configuration before the UE is provided dedicated higher layer parameters. + +A UE can indicate a capability to monitor PDCCH according to one or more of the combinations = (2, 2), (4, 3), and (7, 3) per SCS configuration of and . A span is a number of consecutive symbols in a slot where the UE is configured to monitor PDCCH. Each PDCCH monitoring occasion is within one span. If a UE monitors PDCCH on a cell according to combination, the UE supports PDCCH monitoring occasions in any symbol of a slot with minimum time separation of symbols between the first symbol of two consecutive spans, including across slots. A span starts at a first symbol where a PDCCH monitoring occasion starts and ends at a last symbol where a PDCCH monitoring occasion ends, where the number of symbols of the span is up to . + +If a UE indicates a capability to monitor PDCCH according to multiple combinations and a configuration of search space sets to the UE for PDCCH monitoring on a cell results to a separation of every two consecutive PDCCH monitoring spans that is equal to or larger than the value of for more than one of the multiple combinations, the UE monitors PDCCH on the cell according to the combination, from the more than one combinations, that is associated with the largest maximum number of and defined in Table 10.1-2A and Table 10.1-3A. The UE expects to monitor PDCCH according to the same combination in every slot on the active DL BWP of a cell. + +For SCS configuration or, a UE can indicate a capability to monitor PDCCH according to one or more combinations, where and are numbers of consecutive slots. Groups of slots are consecutive and non-overlapping and the slots are within the slots. The first group of slots starts from the beginning of a subframe. The start of two consecutive groups of slots is separated by slots. + +If a UE monitors PDCCH on a cell according to combination, the UE can monitor PDCCH for Type1-PDCCH CSS set provided by dedicated higher layer signalling, Type3-PDCCH CSS sets, and USS sets in any slot of the slots, and the UE can monitor PDCCH for Type0/0A/2-PDCCH CSS set and Type1-PDCCH CSS set provided in *SIB1* in any slot of the slots. The UE determines the number of monitored PDCCH candidates and the number of non-overlapped CCEs for combination based on all search space sets within the slots, as applicable according to the search space set configurations, and maximum corresponding values are provided in Table 10.1-2B and Table 10.1-3B, respectively. + +For, if the UE indicates a capability to monitor PDCCH according to multiple combinations and a configuration of search space sets to the UE for PDCCH monitoring on a serving cell results to a separation of every two consecutive groups of slots that is not smaller than for more than one combinations, of the multiple combinations, the UE monitors PDCCH on the cell according to the combination, from the more than one combinations, that is associated with the largest maximum number of and defined in Table 10.1-2B and Table 10.1-3B. + +A UE capability for PDCCH monitoring per slot, or per group of slots according to combination, or per span on an active DL BWP of a serving cell is defined by a maximum number of PDCCH candidates and non-overlapped CCEs the UE can monitor per slot, or per group of slots according to combination, or per span, respectively, on the active DL BWP of the serving cell. + +For monitoring of a PDCCH candidate by a UE, if the UE + +- has received *ssb-PositionsInBurst* in *SIB1* and has not received *ssb-PositionsInBurst* in *ServingCellConfigCommon* for a serving cell, and +- does not monitor PDCCH candidates in a Type0-PDCCH CSS set, and +- at least one RE for a PDCCH candidate overlaps with at least one RE of a candidate SS/PBCH block corresponding to a SS/PBCH block index provided by *ssb-PositionsInBurst* in *SIB1*, + +the UE is not required to monitor the PDCCH candidate. + +For monitoring of a PDCCH candidate by a UE, if the UE + +- has received *ssb-PositionsInBurst* in *ServingCellConfigCommon* for a serving cell, and +- does not monitor PDCCH candidates in a Type0-PDCCH CSS set, and +- at least one RE for a PDCCH candidate overlaps with at least one RE of a candidate SS/PBCH block corresponding to a SS/PBCH block index provided by *ssb-PositionsInBurst* in *ServingCellConfigCommon*, + +the UE is not required to monitor the PDCCH candidate. + +For monitoring of a PDCCH candidate by a UE, if the UE + +- has received *ssb-PositionsInBurst* in *SSB-MTCAdditionalPCI* for a serving cell, and +- at least one RE for a PDCCH candidate overlaps with at least one RE of a candidate SS/PBCH block corresponding to a SS/PBCH block index provided by *ssb-PositionsInBurst* in *SSB-MTCAdditionalPCI* with same physical cell identity as the one associated with a RS having same quasi-collocation properties as a CORESET for the PDCCH candidate, + +the UE is not required to monitor the PDCCH candidate. + +A UE is not required to monitor PDCCH candidates for a Type0/0A/0B/1/1A /2/2A -PDCCH CSS set when the active TCI state for a corresponding CORESET is not associated with *physCellId* in *ServingCellConfigCommon*. + +If a UE monitors the PDCCH candidate for a Type0-PDCCH CSS set on the serving cell according to the procedure described in clause 13, the UE may assume that no SS/PBCH block is transmitted in REs used for monitoring the PDCCH candidate on the serving cell. + +If at least one RE of a PDCCH candidate for a UE on the serving cell overlaps with at least one RE of *lte-CRS-ToMatchAround* or of *LTE-CRS-PatternList*, the UE + +- is not required to monitor the PDCCH candidate if the UE is not provided *pdchCandidateReception-WithCRSOverlap*, +- monitors the PDCCH candidate if the UE is provided *pdchCandidateReception-WithCRSOverlap* and the UE indicates an associated capability corresponding to the configuration of *lte-CRS-ToMatchAround* or of *LTE-CRS-PatternList* [18, TS 38.306]. + +If a UE is provided *availableRB-SetsPerCell*, the UE is not required to monitor PDCCH candidates that overlap with any RB from RB sets that are indicated as unavailable for receptions by an available RB set indicator field in DCI format 2\_0 as described in clause 11.1.1. If the UE does not obtain the available RB set indicator for a symbol, the UE monitors PDCCH candidates on all RB sets in the symbol. + +If a UE can support + +- a first set of serving cells where the UE is either not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with a single value for all CORESETs on all DL BWPs of each scheduling cell from the first set of serving cells, and + +- a second set of serving cells where the UE is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with a value 0 for a first CORESET, and with a value 1 for a second CORESET on any DL BWP of each scheduling cell from the second set of serving cells + +the UE determines, for the purpose of reporting *pdcch-BlindDetectionCA*, *pdcch-BlindDetectionCA1*, and *pdcch-BlindDetectionCA3*, a number of serving cells as $N_{cells}$ where $N_{cells}$ is a value reported by the UE. + +If a UE indicates in *UE-NR-Capability* a carrier aggregation capability larger than 4 serving cells and the UE is not provided *monitoringCapabilityConfig* for any downlink cell or if the UE is provided *monitoringCapabilityConfig* = *r15monitoringcapability* for all downlink cells where the UE monitors PDCCH, the UE includes in *UE-NR-Capability* an indication for a maximum number of PDCCH candidates and for a maximum number of non-overlapped CCEs the UE can monitor per slot when the UE is configured for carrier aggregation operation over more than 4 cells. When a UE is not configured for NR-DC operation, the UE determines a capability to monitor a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs per slot that corresponds to $N_{cells}$ downlink cells, where + +- $N_{cells}$ is if the UE does not provide *pdcch-BlindDetectionCA* where $N_{cells}$ is the number of configured downlink serving cells +- otherwise, $N_{cells}$ is the value of *pdcch-BlindDetectionCA* + +When a UE is configured for NR-DC operation, the UE determines a capability to monitor a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs per slot that corresponds to $N_{cells}$ downlink cells for the MCG where $N_{cells}$ is provided by *pdcch-BlindDetection* for the MCG and determines a capability to monitor a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs per slot that corresponds to $N_{cells}$ downlink cells for the SCG where $N_{cells}$ is provided by *pdcch-BlindDetection* for the SCG. When the UE is configured for carrier aggregation operation over more than 4 cells, or for a cell group when the UE is configured for NR-DC operation, the UE does not expect to monitor per slot a number of PDCCH candidates or a number of non-overlapped CCEs that is larger than the maximum number as derived from the corresponding value of $N_{cells}$ . + +When a UE is configured for NR-DC operation with a total of $N_{cells}$ downlink cells on both the MCG and the SCG, the UE expects to be provided *pdcch-BlindDetection* for the MCG and *pdcch-BlindDetection* for the SCG with values that satisfy + +- *pdcch-BlindDetection* for the MCG + *pdcch-BlindDetection* for the SCG $\leq$ *pdcch-BlindDetectionCA*, if the UE reports *pdcch-BlindDetectionCA*, or +- *pdcch-BlindDetection* for the MCG + *pdcch-BlindDetection* for the SCG $\leq$ $N_{cells}$ , if the UE does not report *pdcch-BlindDetectionCA*. + +For NR-DC operation, the UE may indicate, through *pdcch-BlindDetectionMCG-UE* and *pdcch-BlindDetectionSCG-UE*, respective maximum values for *pdcch-BlindDetection* for the MCG and *pdcch-BlindDetection* for the SCG. + +If the UE reports *pdcch-BlindDetectionCA*, + +- the value range of *pdcch-BlindDetectionMCG-UE* or of *pdcch-BlindDetectionSCG-UE* is $[1, \dots, pdcch-BlindDetectionCA-1]$ , and +- *pdcch-BlindDetectionMCG-UE* + *pdcch-BlindDetectionSCG-UE* $\geq$ *pdcch-BlindDetectionCA*. + +Otherwise, $N_{cells}$ is a maximum total number of downlink cells that the UE can be configured on both the MCG and the SCG for NR-DC as indicated in *UE-NR-Capability*, + +- the value range of *pdcch-BlindDetectionMCG-UE* or of *pdcch-BlindDetectionSCG-UE* is $[1, 2, 3]$ , and +- *pdcch-BlindDetectionMCG-UE* + *pdcch-BlindDetectionSCG-UE* $\geq N_{cells}$ . + +If a UE indicates in *UE-NR-Capability* a carrier aggregation capability larger than two downlink cells, the UE includes in *UE-NR-Capability* an indication for a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs that the UE can monitor per span when the UE is configured for carrier aggregation operation over more than two downlink cells with *monitoringCapabilityConfig* = *r16monitoringcapability*. When a UE is not configured for NR-DC operation and the UE is provided *monitoringCapabilityConfig* = *r16monitoringcapability* for all downlink cells where the UE monitors PDCCH, the UE determines a capability to monitor a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs per span that corresponds to $N_{cells}$ downlink cells, where + +- is the number of configured downlink cells if the UE does not provide *pdcch-MonitoringCA* +- otherwise, is the value of *pdcch-MonitoringCA* + +When a UE is configured for NR-DC operation and the UE is provided *monitoringCapabilityConfig* = *r16monitoringcapability* for all downlink cells where the UE monitors PDCCH, the UE determines a capability to monitor a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs per span that corresponds to + +- downlink cells for the MCG where is provided by *pdcch-BlindDetection2* for the MCG, and +- downlink cells for the SCG where is provided by *pdcch-BlindDetection2* for the SCG + +When the UE is configured for carrier aggregation operation over more than 2 cells, or for a cell group when the UE is configured for NR-DC operation, the UE does not expect to monitor per span a number of PDCCH candidates or a number of non-overlapped CCEs that is larger than the maximum number as derived from the corresponding value of . + +When a UE is configured for NR-DC operation with a total of downlink cells on both the MCG and the SCG and the UE is provided *monitoringCapabilityConfig* = *r16monitoringcapability* for all downlink cells where the UE monitors PDCCH, the UE expects to be provided *pdcch-BlindDetection2* for the MCG and *pdcch-BlindDetection2* for the SCG with values that satisfy + +- *pdcch-BlindDetection2* for the MCG + *pdcch-BlindDetection2* for the SCG $\leq$ *pdcch-MonitoringCA*, if the UE reports *pdcch-MonitoringCA*, or +- *pdcch-BlindDetection2* for the MCG + *pdcch-BlindDetection2* for the SCG $\leq$ , if the UE does not report *pdcch-MonitoringCA* + +When a UE is configured for NR-DC operation and the UE is provided *monitoringCapabilityConfig* = *r16monitoringcapability* for all downlink cells where the UE monitors PDCCH, the UE may indicate, through *pdcch-BlindDetectionMCG-UE-r16* and *pdcch-BlindDetectionSCG-UE-r16*, respective maximum values for *pdcch-BlindDetection* for the MCG and *pdcch-BlindDetection* for the SCG. + +If the UE reports *pdcch-MonitoringCA*, + +- the value range of *pdcch-BlindDetectionMCG-UE-r16* or of *pdcch-BlindDetectionSCG-UE-r16* is [1, ..., *pdcch-MonitoringCA*-1], and +- *pdcch-BlindDetectionMCG-UE-r16* + *pdcch-BlindDetectionSCG-UE-r16* $\geq$ *pdcch-MonitoringCA*. + +Otherwise, if is a maximum total number of downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r16monitoringcapability* and the UE is configured on both the MCG and the SCG for NR-DC as indicated in *UE-NR-Capability* + +- the value of *pdcch-BlindDetectionMCG-UE-r16* or of *pdcch-BlindDetectionSCG-UE-r16* is 1, +- *pdcch-BlindDetectionMCG-UE-r16* + *pdcch-BlindDetectionSCG-UE-r16* $\geq$ . + +If a UE indicates in *UE-NR-Capability* a carrier aggregation capability larger than four downlink cells, the UE includes in *UE-NR-Capability* an indication for a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs that the UE can monitor per group of slots when the UE is configured for carrier aggregation operation over more than four downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r17monitoringcapability*. When a UE is not configured for NR-DC operation for all downlink cells where the UE monitors PDCCH, the UE determines a capability to monitor a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs per group of slots that corresponds to downlink cells, where + +- is if the UE does not provide *pdcch-MonitoringCA-r17* where is the number of configured downlink serving cells +- otherwise, is the value of *pdcch-MonitoringCA-r17* + +When the UE is configured for carrier aggregation operation over more than 4 cells, the UE does not expect to monitor per group of slots a number of PDCCH candidates or a number of non-overlapped CCEs that is larger than the maximum number as derived from the corresponding value of . + +When a UE is configured for NR-DC operation and the UE is provided *monitoringCapabilityConfig* = *r17monitoringcapability* for all downlink cells where the UE monitors PDCCH, the UE determines a capability to monitor a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs per group of slots that corresponds to + +- downlink cells for the MCG where is provided by *pdcch-BlindDetection4* for the MCG, and +- downlink cells for the SCG where is provided by *pdcch-BlindDetection4* for the SCG + +When a UE is configured for NR-DC operation with a total of downlink cells on both the MCG and the SCG and the UE is provided *monitoringCapabilityConfig* = *r17monitoringcapability* for all downlink cells where the UE monitors PDCCH, the UE expects to be provided *pdcch-BlindDetection4* for the MCG and *pdcch-BlindDetection4* for the SCG with values that satisfy + +- *pdcch-BlindDetection4* for the MCG + *pdcch-BlindDetection4* for the SCG $\leq$ *pdcch-MonitoringCA-r17*, if the UE reports *pdcch-MonitoringCA-r17*, or +- *pdcch-BlindDetection4* for the MCG + *pdcch-BlindDetection4* for the SCG $\leq$ , if the UE does not report *pdcch-MonitoringCA-r17* + +When a UE is configured for NR-DC operation and the UE is provided *monitoringCapabilityConfig* = *r17monitoringcapability* for all downlink cells where the UE monitors PDCCH, the UE may indicate, through *pdcch-BlindDetectionMCG-UE-r17* and *pdcch-BlindDetectionSCG-UE-r17*, respective maximum values for *pdcch-BlindDetection4* for the MCG and *pdcch-BlindDetection4* for the SCG. + +If the UE reports *pdcch-MonitoringCA-r17*, + +- the value range of *pdcch-BlindDetectionMCG-UE-r17* or of *pdcch-BlindDetectionSCG-UE-r17* is [1, ..., *pdcch-MonitoringCA-r17*-1], and +- *pdcch-BlindDetectionMCG-UE-r17* + *pdcch-BlindDetectionSCG-UE-r17* $\geq$ *pdcch-MonitoringCA-r17*. + +Otherwise, if is a maximum total number of downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r17monitoringcapability* and the UE is configured on both the MCG and the SCG for NR-DC as indicated in *UE-NR-Capability* + +- the value range of *pdcch-BlindDetectionMCG-UE-r17* or of *pdcch-BlindDetectionSCG-UE-r17* is [1, 2, 3], and +- *pdcch-BlindDetectionMCG-UE-r17* + *pdcch-BlindDetectionSCG-UE-r17* $\geq$ . + +If a UE indicates in *UE-NR-Capability* a carrier aggregation capability larger than one downlink cell with *monitoringCapabilityConfig* = *r15monitoringcapability* or larger than one downlink cell with *monitoringCapabilityConfig* = *r16monitoringcapability*, the UE includes in *UE-NR-Capability* an indication for a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs the UE can monitor for downlink cells with *monitoringCapabilityConfig* = *r15monitoringcapability* or for downlink cells with *monitoringCapabilityConfig* = *r16monitoringcapability* when the UE is configured for carrier aggregation operation over more than two downlink cells with at least one downlink cell with *monitoringCapabilityConfig* = *r15monitoringcapability* and at least one downlink cell with *monitoringCapabilityConfig* = *r16monitoringcapability*. When a UE is not configured for NR-DC operation, the UE determines a capability to monitor a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs per slot or per span that corresponds to downlink cells or to downlink cells, respectively, where + +- is the number of configured downlink cells if the UE does not provide *pdcch-BlindDetectionCA1* +- otherwise, + - if the UE reports only one combination of (*pdcch-BlindDetectionCA1*, *pdcch-BlindDetectionCA2*), is the value of *pdcch-BlindDetectionCA1* + - else, is the value of *pdcch-BlindDetectionCA1* from a combination of (*pdcch-BlindDetectionCA1*, *pdcch-BlindDetectionCA2*) that is provided by *pdcch-BlindDetectionCA-CombIndicator* + +and + +- is the number of configured downlink cells if the UE does not provide *pdcch-BlindDetectionCA2* + +- otherwise, + - if the UE reports only one combination of (*pdcch-BlindDetectionCA1*, *pdcch-BlindDetectionCA2*), is the value of *pdcch-BlindDetectionCA2* + - else, is the value of *pdcch-BlindDetectionCA2* from a combination of (*pdcch-BlindDetectionCA1*, *pdcch-BlindDetectionCA2*) that is provided by *pdcch-BlindDetectionCA-CombIndicator* + +If a UE indicates in *UE-NR-Capability* a carrier aggregation capability larger than one downlink cell with *monitoringCapabilityConfig = r15monitoringcapability* or larger than one downlink cell with *monitoringCapabilityConfig = r17monitoringcapability*, the UE includes in *UE-NR-Capability* an indication for a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs the UE can monitor for downlink cells with *monitoringCapabilityConfig = r15monitoringcapability* or for downlink cells with *monitoringCapabilityConfig = r17monitoringcapability* when the UE is configured for carrier aggregation operation over more than two downlink cells with at least one downlink cell with *monitoringCapabilityConfig = r15monitoringcapability* and at least one downlink cell with *monitoringCapabilityConfig = r17monitoringcapability*. When a UE is not configured for NR-DC operation, the UE determines a capability to monitor a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs per slot or per group of slots that corresponds to downlink cells or to downlink cells, respectively, where + +- is if the UE does not provide *pdcch-BlindDetectionCA1* in *pdcch-BlindDetectionMixedList1*, where is the number of configured downlink serving cells +- otherwise, + - if the UE reports only one combination of (*pdcch-BlindDetectionCA1*, *pdcch-BlindDetectionCA2*) in *pdcch-BlindDetectionMixedList1*, is the value of *pdcch-BlindDetectionCA1* + - else, is the value of *pdcch-BlindDetectionCA1* from a combination of (*pdcch-BlindDetectionCA1*, *pdcch-BlindDetectionCA3*) that is provided by *pdcch-BlindDetectionCA-CombIndicator-r17* + +and + +- is if the UE does not provide *pdcch-BlindDetectionCA2* in *pdcch-BlindDetectionMixedList1*, where is the number of configured downlink serving cells +- otherwise, + - if the UE reports only one combination of (*pdcch-BlindDetectionCA1*, *pdcch-BlindDetectionCA2*) in *pdcch-BlindDetectionMixedList1*, is the value of *pdcch-BlindDetectionCA2* + - else, is the value of *pdcch-BlindDetectionCA3* from a combination of (*pdcch-BlindDetectionCA1*, *pdcch-BlindDetectionCA3*) that is provided by *pdcch-BlindDetectionCA-CombIndicator-r17* + +If a UE indicates in *UE-NR-Capability* a carrier aggregation capability larger than one downlink cell with *monitoringCapabilityConfig = r16monitoringcapability* or larger than one downlink cell with *monitoringCapabilityConfig = r17monitoringcapability*, the UE includes in *UE-NR-Capability* an indication for a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs the UE can monitor for downlink cells with *monitoringCapabilityConfig = r16monitoringcapability* or for downlink cells with *monitoringCapabilityConfig = r17monitoringcapability* when the UE is configured for carrier aggregation operation over more than two downlink cells with at least one downlink cell with *monitoringCapabilityConfig = r16monitoringcapability* and with at least one downlink cell with *monitoringCapabilityConfig = r17monitoringcapability*. When a UE is not configured for NR-DC operation, the UE determines a capability to monitor a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs per span or per group of slots that corresponds to downlink cells or to downlink cells, respectively, where + +- is the number of configured downlink cells if the UE does not provide *pdcch-BlindDetectionCA1* in *pdcch-BlindDetectionMixedList2* +- otherwise, + - if the UE reports only one combination of (*pdcch-BlindDetectionCA1*, *pdcch-BlindDetectionCA2*) in *pdcch-BlindDetectionMixedList2*, is the value of *pdcch-BlindDetectionCA1* + +- else, is the value of *pdcch-BlindDetectionCA2* from a combination of (*pdcch-BlindDetectionCA2*, *pdcch-BlindDetectionCA3*) that is provided by *pdcch-BlindDetectionCA-CombIndicator-r17* + +and + +- is the number of configured downlink cells if the UE does not provide *pdcch-BlindDetectionCA2* in *pdcch-BlindDetectionMixedList2* +- otherwise, + - if the UE reports only one combination of (*pdcch-BlindDetectionCA1*, *pdcch-BlindDetectionCA2*) in *pdcch-BlindDetectionMixedList2*, is the value of *pdcch-BlindDetectionCA2* + - else, is the value of *pdcch-BlindDetectionCA3* from a combination of (*pdcch-BlindDetectionCA2*, *pdcch-BlindDetectionCA3*) that is provided by *pdcch-BlindDetectionCA-CombIndicator-r17* + +If a UE indicates in *UE-NR-Capability* a carrier aggregation capability larger than one downlink cell with *monitoringCapabilityConfig = r15monitoringcapability*, or larger than one downlink cell with *monitoringCapabilityConfig = r16monitoringcapability*, or larger than one downlink cell with *monitoringCapabilityConfig = r17monitoringcapability*, the UE includes in *UE-NR-Capability* an indication for a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs the UE can monitor for downlink cells with *monitoringCapabilityConfig = r15monitoringcapability*, or for downlink cells with *monitoringCapabilityConfig = r16monitoringcapability*, or for downlink cells with *monitoringCapabilityConfig = r17monitoringcapability* when the UE is configured for carrier aggregation operation over more than three downlink cells with at least one downlink cell with *monitoringCapabilityConfig = r15monitoringcapability*, at least one downlink cell with *monitoringCapabilityConfig = r16monitoringcapability* and at least one downlink cell with *monitoringCapabilityConfig = r17monitoringcapability*. When a UE is not configured for NR-DC operation, the UE determines a capability to monitor a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs per slot or per span or per group of slots that corresponds to downlink cells or to downlink cells or to downlink cells, respectively, where + +- is the number of configured downlink cells if the UE does not provide *pdcch-BlindDetectionCA1* in *pdcch-BlindDetectionMixedList3* +- otherwise, + - if the UE reports only one combination of (*pdcch-BlindDetectionCA1*, *pdcch-BlindDetectionCA2*, *pdcch-BlindDetectionCA3*) in *pdcch-BlindDetectionMixedList3*, is the value of *pdcch-BlindDetectionCA1* + - else, is the value of *pdcch-BlindDetectionCA1* from a combination of (*pdcch-BlindDetectionCA1*, *pdcch-BlindDetectionCA2*, *pdcch-BlindDetectionCA3*) that is provided by *pdcch-BlindDetectionCA-CombIndicator-r17* +- is the number of configured downlink cells if the UE does not provide *pdcch-BlindDetectionCA2* in *pdcch-BlindDetectionMixedList3* +- otherwise, + - if the UE reports only one combination of (*pdcch-BlindDetectionCA1*, *pdcch-BlindDetectionCA2*, *pdcch-BlindDetectionCA3*) in *pdcch-BlindDetectionMixedList3*, is the value of *pdcch-BlindDetectionCA2* + - else, is the value of *pdcch-BlindDetectionCA2* from a combination of (*pdcch-BlindDetectionCA1*, *pdcch-BlindDetectionCA2*, *pdcch-BlindDetectionCA3*) that is provided by *pdcch-BlindDetectionCA-CombIndicator-r17* + +and + +- is the number of configured downlink cells if the UE does not provide *pdcch-BlindDetectionCA3* in *pdcch-BlindDetectionMixedList3* +- otherwise, + - if the UE reports only one combination of (*pdcch-BlindDetectionCA1*, *pdcch-BlindDetectionCA2*, *pdcch-BlindDetectionCA3*) in *pdcch-BlindDetectionMixedList3*, is the value of *pdcch-BlindDetectionCA3* + +- else, is the value of *pdcch-BlindDetectionCA3* from a combination of (*pdcch-BlindDetectionCA1*, *pdcch-BlindDetectionCA2*, *pdcch-BlindDetectionCA3*) that is provided by *pdcch-BlindDetectionCA-CombIndicator-r17* + +When a UE is configured for NR-DC operation and is provided *monitoringCapabilityConfig = r15monitoringcapability* for at least one downlink cell and *monitoringCapabilityConfig = r16monitoringcapability* for at least one downlink cell where the UE monitors PDCCH, the UE determines a capability to monitor a maximum number of PDCCH candidates and a maximum number of non-overlapped CCEs that corresponds to + +- downlink cells for the MCG where is provided by *pdcch-BlindDetection3* for the MCG, +- downlink cells for the SCG where is provided by *pdcch-BlindDetection3* for the SCG, and +- downlink cells for the MCG where is provided by *pdcch-BlindDetection2* for the MCG, +- downlink cells for the SCG where is provided by *pdcch-BlindDetection2* for the SCG + +When a UE is configured for carrier aggregation operation over more than two downlink cells with at least one downlink cell with *monitoringCapabilityConfig = r15monitoringcapability*, at least one downlink cell with *monitoringCapabilityConfig = r16monitoringcapability*, and no downlink cell has SCS configuration , or for a cell group when the UE is configured for NR-DC operation, the UE does not expect to + +- monitor per slot a number of PDCCH candidates or a number of non-overlapped CCEs that is larger than the maximum number as derived from the corresponding value of , and +- monitor per span a number of PDCCH candidates or a number of non-overlapped CCEs that is larger than the maximum number as derived from the corresponding value of + +When the UE is configured for carrier aggregation operation over more than two downlink cells with at least one downlink cell with *monitoringCapabilityConfig = r15monitoringcapability*, at least one downlink cell with *monitoringCapabilityConfig = r17monitoringcapability*, and no downlink cell with *monitoringCapabilityConfig = r16monitoringcapability*, the UE does not expect to + +- monitor per slot a number of PDCCH candidates or a number of non-overlapped CCEs that is larger than the maximum number as derived from the corresponding value of , and +- monitor per group of slots a number of PDCCH candidates or a number of non-overlapped CCEs that is larger than the maximum number as derived from the corresponding value of + +When the UE is configured for carrier aggregation operation over more than two downlink cells with at least one downlink cell with *monitoringCapabilityConfig = r16monitoringcapability*, at least one downlink cell with *monitoringCapabilityConfig = r17monitoringcapability*, and no downlink cell with *monitoringCapabilityConfig = r15monitoringcapability*, the UE does not expect to + +- monitor per span a number of PDCCH candidates or a number of non-overlapped CCEs that is larger than the maximum number as derived from the corresponding value of , and +- monitor per group of slots a number of PDCCH candidates or a number of non-overlapped CCEs that is larger than the maximum number as derived from the corresponding value of + +When the UE is configured for carrier aggregation operation over more than three downlink cells with at least one downlink cell with *monitoringCapabilityConfig = r15monitoringcapability*, at least one downlink cell with *monitoringCapabilityConfig = r16monitoringcapability*, and at least one downlink cell with *monitoringCapabilityConfig = r17monitoringcapability*, the UE does not expect to + +- monitor per slot a number of PDCCH candidates or a number of non-overlapped CCEs that is larger than the maximum number as derived from the corresponding value of , and +- monitor per span a number of PDCCH candidates or a number of non-overlapped CCEs that is larger than the maximum number as derived from the corresponding value of , and +- monitor per group of slots a number of PDCCH candidates or a number of non-overlapped CCEs that is larger than the maximum number as derived from the corresponding value of + +When a UE is configured for NR-DC operation with a total of downlink cells on both the MCG and the SCG and the UE is provided *monitoringCapabilityConfig = r15monitoringcapability* for downlink cells and + +*monitoringCapabilityConfig = r16monitoringcapability* for downlink cells where the UE monitors PDCCH, the UE expects to be provided *pdccch-BlindDetection3* and *pdccch-BlindDetection2* for the MCG, and *pdccch-BlindDetection3* and *pdccch-BlindDetection2* for the SCG with values that satisfy + +- *pdccch-BlindDetection3* for the MCG + *pdccch-BlindDetection3* for the SCG $\leq$ *pdccch-BlindDetectionCA1*, if the UE reports *pdccch-BlindDetectionCA1*, or +- *pdccch-BlindDetection3* for the MCG + *pdccch-BlindDetection3* for the SCG $\leq$ , if the UE does not report *pdccch-BlindDetectionCA1* + +and + +- *pdccch-BlindDetection2* for the MCG + *pdccch-BlindDetection2* for the SCG $\leq$ *pdccch-BlindDetectionCA2*, if the UE reports *pdccch-BlindDetectionCA2*, or +- *pdccch-BlindDetection2* for the MCG + *pdccch-BlindDetection2* for the SCG $\leq$ , if the UE does not report *pdccch-BlindDetectionCA2* + +When a UE is configured for NR-DC operation and is provided *monitoringCapabilityConfig = r15monitoringcapability* for at least one downlink cell and *monitoringCapabilityConfig = r16monitoringcapability* for at least one downlink cell where the UE monitors PDCCH, the UE may indicate, through *pdccch-BlindDetectionMCG-UE1* and *pdccch-BlindDetectionSCG-UE1*, respective maximum values for *pdccch-BlindDetection3* for the MCG and *pdccch-BlindDetection3* for the SCG, and through *pdccch-BlindDetectionMCG-UE2* and *pdccch-BlindDetectionSCG-UE2* respective maximum values for *pdccch-BlindDetection2* for the MCG and *pdccch-BlindDetection2* for the SCG. + +If the UE reports *pdccch-BlindDetectionCA1*, + +- the value range of *pdccch-BlindDetectionMCG-UE1* or of *pdccch-BlindDetectionSCG-UE1* is $[0, 1, \dots, \text{pdccch-BlindDetectionCA1}]$ , and +- *pdccch-BlindDetectionMCG-UE1* + *pdccch-BlindDetectionSCG-UE1* $\geq$ *pdccch-BlindDetectionCA1*. + +Otherwise, if is a maximum total number of downlink cells for which the UE is provided *monitoringCapabilityConfig = r15monitoringcapability* and the UE is configured on both the MCG and the SCG for NR-DC as indicated in *UE-NR-Capability* + +- the value range of *pdccch-BlindDetectionMCG-UE1* or of *pdccch-BlindDetectionSCG-UE1* is $[0, 1, 2]$ , +- *pdccch-BlindDetectionMCG-UE1* + *pdccch-BlindDetectionSCG-UE1* $\geq$ . + +If the UE reports *pdccch-BlindDetectionCA2* + +- the value range of *pdccch-BlindDetectionMCG-UE2* or of *pdccch-BlindDetectionSCG-UE2* is $[0, 1, \dots, \text{pdccch-BlindDetectionCA2}]$ , and +- *pdccch-BlindDetectionMCG-UE2* + *pdccch-BlindDetectionSCG-UE2* $\geq$ *pdccch-BlindDetectionCA2*. + +Otherwise, if is a maximum total number of downlink cells for which the UE is provided *monitoringCapabilityConfig = r16monitoringcapability* and the UE is configured on both the MCG and the SCG for NR-DC as indicated in *UE-NR-Capability* + +- the value range of *pdccch-BlindDetectionMCG-UE2* or of *pdccch-BlindDetectionSCG-UE2* is $[0, 1]$ , +- *pdccch-BlindDetectionMCG-UE2* + *pdccch-BlindDetectionSCG-UE2* $\geq$ . + +When a UE is configured for NR-DC operation with a total of downlink cells on both the MCG and the SCG and the UE is provided *monitoringCapabilityConfig = r15monitoringcapability* for downlink cells and *monitoringCapabilityConfig = r17monitoringcapability* for downlink cells where the UE monitors PDCCH, the UE expects to be provided *pdccch-BlindDetection3* and *pdccch-BlindDetection4* for the MCG, and *pdccch-BlindDetection3* and *pdccch-BlindDetection4* for the SCG with values that satisfy + +- *pdccch-BlindDetection3* for the MCG + *pdccch-BlindDetection3* for the SCG $\leq$ *pdccch-BlindDetectionCA1*, if the UE reports *pdccch-BlindDetectionCA1* in *pdccch-BlindDetectionMixedList1*, or +- *pdccch-BlindDetection3* for the MCG + *pdccch-BlindDetection3* for the SCG $\leq$ , if the UE does not report *pdccch-BlindDetectionCA1* in *pdccch-BlindDetectionMixedList1* + +and + +- *pdcch-BlindDetection4* for the MCG + *pdcch-BlindDetection4* for the SCG $\leq$ *pdcch-BlindDetectionCA2*, if the UE reports *pdcch-BlindDetectionCA2* in *pdcch-BlindDetectionMixedList1*, or +- *pdcch-BlindDetection4* for the MCG + *pdcch-BlindDetection4* for the SCG $\leq$ , if the UE does not report *pdcch-BlindDetectionCA2* in *pdcch-BlindDetectionMixedList1* + +When a UE is configured for NR-DC operation and is provided *monitoringCapabilityConfig* = *r15monitoringcapability* for at least one downlink cell and *monitoringCapabilityConfig* = *r17monitoringcapability* for at least one downlink cell where the UE monitors PDCCH, the UE may indicate, through *pdcch-BlindDetectionCG-UE1* in *pdcch-BlindDetectionMCG-UE-Mixed* and *pdcch-BlindDetectionCG-UE1* in *pdcch-BlindDetectionSCG-UE-Mixed*, respective maximum values for *pdcch-BlindDetection3* for the MCG and *pdcch-BlindDetection3* for the SCG, and through *pdcch-BlindDetectionCG-UE2* in *pdcch-BlindDetectionMCG-UE-Mixed* and *pdcch-BlindDetectionCG-UE2* in *pdcch-BlindDetectionSCG-UE-Mixed*, respective maximum values for *pdcch-BlindDetection4* for the MCG and *pdcch-BlindDetection4* for the SCG. + +If the UE reports *pdcch-BlindDetectionCA1* in *pdcch-BlindDetectionMixedList1*, + +- the value range of *pdcch-BlindDetectionCG-UE1* for the MCG or of *pdcch-BlindDetectionCG-UE1* for the SCG is [0, 1, ..., *pdcch-BlindDetectionCA1*], and +- *pdcch-BlindDetectionCG-UE1* for the MCG + *pdcch-BlindDetectionCG-UE1* for the SCG $\geq$ *pdcch-BlindDetectionCA1*. + +Otherwise, if is a maximum total number of downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r15monitoringcapability* and the UE is configured on both the MCG and the SCG for NR-DC as indicated in *UE-NR-Capability* + +- the value range of *pdcch-BlindDetectionCG-UE1* for the MCG or of *pdcch-BlindDetectionCG-UE1* for the SCG is [0, 1, 2], +- *pdcch-BlindDetectionCG-UE1* for the MCG + *pdcch-BlindDetectionSCG-UE1* for the SCG $\geq$ . + +If the UE reports *pdcch-BlindDetectionCA2* in *pdcch-BlindDetectionMixedList1* + +- the value range of *pdcch-BlindDetectionCG-UE2* for the MCG or of *pdcch-BlindDetectionCG-UE2* for the SCG is [0, 1, ..., *pdcch-BlindDetectionCA3*], and +- *pdcch-BlindDetectionCG-UE2* for the MCG + *pdcch-BlindDetectionCG-UE2* for the SCG $\geq$ *pdcch-BlindDetectionCA2*. + +Otherwise, if is a maximum total number of downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r17monitoringcapability* and the UE is configured on both the MCG and the SCG for NR-DC as indicated in *UE-NR-Capability* + +- the value range of *pdcch-BlindDetectionCG-UE2* for the MCG or of *pdcch-BlindDetectionCG-UE2* for the SCG is [0, 1, 2], +- *pdcch-BlindDetectionCG-UE2* for the MCG + *pdcch-BlindDetectionCG-UE2* for the SCG $\geq$ . + +When a UE is configured for NR-DC operation with a total of downlink cells on both the MCG and the SCG and the UE is provided *monitoringCapabilityConfig* = *r16monitoringcapability* for downlink cells and *monitoringCapabilityConfig* = *r17monitoringcapability* for downlink cells where the UE monitors PDCCH, the UE expects to be provided *pdcch-BlindDetection2* and *pdcch-BlindDetection4* for the MCG, and *pdcch-BlindDetection2* and *pdcch-BlindDetection4* for the SCG with values that satisfy + +- *pdcch-BlindDetection2* for the MCG + *pdcch-BlindDetection2* for the SCG $\leq$ *pdcch-BlindDetectionCA1*, if the UE reports *pdcch-BlindDetectionCA1* in *pdcch-BlindDetectionMixedList2*, or +- *pdcch-BlindDetection2* for the MCG + *pdcch-BlindDetection2* for the SCG $\leq$ , if the UE does not report *pdcch-BlindDetectionCA1* in *pdcch-BlindDetectionMixedList2* + +and + +- *pdcch-BlindDetection4* for the MCG + *pdcch-BlindDetection4* for the SCG $\leq$ *pdcch-BlindDetectionCA2*, if the UE reports *pdcch-BlindDetectionCA2* in *pdcch-BlindDetectionMixedList2*, or +- *pdcch-BlindDetection4* for the MCG + *pdcch-BlindDetection4* for the SCG $\leq$ , if the UE does not report *pdcch-BlindDetectionCA2* in *pdcch-BlindDetectionMixedList2* + +When a UE is configured for NR-DC operation and is provided *monitoringCapabilityConfig* = *r16monitoringcapability* for at least one downlink cell and *monitoringCapabilityConfig* = *r17monitoringcapability* for at least one downlink cell where the UE monitors PDCCH, the UE may indicate, through *pdcch-BlindDetectionCG-UE1* in *pdcch-BlindDetectionMCG-UE-Mixed* and *pdcch-BlindDetectionCG-UE1* in *pdcch-BlindDetectionSCG-UE-Mixed*, respective maximum values for *pdcch-BlindDetection2* for the MCG and *pdcch-BlindDetection2* for the SCG, and through *pdcch-BlindDetectionCG-UE2* in *pdcch-BlindDetectionMCG-UE-Mixed* and *pdcch-BlindDetectionCG-UE2* in *pdcch-BlindDetectionSCG-UE-Mixed*, respective maximum values for *pdcch-BlindDetection4* for the MCG and *pdcch-BlindDetection4* for the SCG. + +If the UE reports *pdcch-BlindDetectionCA1* in *pdcch-BlindDetectionMixedList2*, + +- the value range of *pdcch-BlindDetectionCG-UE1* for the MCG or of *pdcch-BlindDetectionCG-UE1* for the SCG is [0, 1, ..., *pdcch-BlindDetectionCA1*], and +- *pdcch-BlindDetectionCG-UE1* for the MCG + *pdcch-BlindDetectionCG-UE1* for the SCG $\geq$ *pdcch-BlindDetectionCA1*. + +Otherwise, if is a maximum total number of downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r16monitoringcapability* and the UE is configured on both the MCG and the SCG for NR-DC as indicated in *UE-NR-Capability* + +- the value range of *pdcch-BlindDetectionCG-UE1* for the MCG or of *pdcch-BlindDetectionCG-UE1* for the SCG is [0, 1], +- *pdcch-BlindDetectionCG-UE1* for the MCG + *pdcch-BlindDetectionCG-UE1* for the SCG $\geq$ . + +If the UE reports *pdcch-BlindDetectionCA2* in *pdcch-BlindDetectionMixedList2* + +- the value range of *pdcch-BlindDetectionCG-UE2* for the MCG or of *pdcch-BlindDetectionCG-UE2* for the SCG is [0, 1, ..., *pdcch-BlindDetectionCA2*], and +- *pdcch-BlindDetectionCG-UE2* for the MCG + *pdcch-BlindDetectionCG-UE2* for the SCG $\geq$ *pdcch-BlindDetectionCA2*. + +Otherwise, if is a maximum total number of downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r17monitoringcapability* and the UE is configured on both the MCG and the SCG for NR-DC as indicated in *UE-NR-Capability* + +- the value range of *pdcch-BlindDetectionCG-UE2* for the MCG or of *pdcch-BlindDetectionCG-UE2* for the SCG is [0, 1, 2], +- *pdcch-BlindDetectionCG-UE2* for the MCG + *pdcch-BlindDetectionCG-UE2* for the SCG $\geq$ . + +When a UE is configured for NR-DC operation with a total of downlink cells on both the MCG and the SCG and the UE is provided *monitoringCapabilityConfig* = *r15monitoringcapability* for downlink cells, *monitoringCapabilityConfig* = *r16monitoringcapability* for downlink cells, and *monitoringCapabilityConfig* = *r17monitoringcapability* for downlink cells where the UE monitors PDCCH, the UE expects to be provided *pdcch-BlindDetection3*, *pdcch-BlindDetection2*, and *pdcch-BlindDetection4* for the MCG, and *pdcch-BlindDetection3*, *pdcch-BlindDetection2*, and *pdcch-BlindDetection4* for the SCG with values that satisfy + +- *pdcch-BlindDetection3* for the MCG + *pdcch-BlindDetection3* for the SCG $\leq$ *pdcch-BlindDetectionCA1*, if the UE reports *pdcch-BlindDetectionCA1* in *pdcch-BlindDetectionMixedList3*, or +- *pdcch-BlindDetection3* for the MCG + *pdcch-BlindDetection3* for the SCG $\leq$ , if the UE does not report *pdcch-BlindDetectionCA1* in *pdcch-BlindDetectionMixedList3* + +and + +- *pdcch-BlindDetection2* for the MCG + *pdcch-BlindDetection2* for the SCG $\leq$ *pdcch-BlindDetectionCA2*, if the UE reports *pdcch-BlindDetectionCA2* in *pdcch-BlindDetectionMixedList3*, or + +- *pdccch-BlindDetection2* for the MCG + *pdccch-BlindDetection2* for the SCG $\leq$ , if the UE does not report *pdccch-BlindDetectionCA2* in *pdccch-BlindDetectionMixedList3* + +and + +- *pdccch-BlindDetection4* for the MCG + *pdccch-BlindDetection4* for the SCG $\leq$ *pdccch-BlindDetectionCA3*, if the UE reports *pdccch-BlindDetectionCA3* in *pdccch-BlindDetectionMixedList3*, or +- *pdccch-BlindDetection4* for the MCG + *pdccch-BlindDetection4* for the SCG $\leq$ , if the UE does not report *pdccch-BlindDetectionCA3* in *pdccch-BlindDetectionMixedList3* + +When a UE is configured for NR-DC operation and is provided *monitoringCapabilityConfig* = *r15monitoringcapability* for at least one downlink cell, *monitoringCapabilityConfig* = *r16monitoringcapability* for at least one downlink cell, and *monitoringCapabilityConfig* = *r17monitoringcapability* for at least one downlink cell where the UE monitors PDCCH, the UE may indicate, through *pdccch-BlindDetectionCG-UE1* in *pdccch-BlindDetectionMCG-UE-Mixed1* and *pdccch-BlindDetectionCG-UE1* in *pdccch-BlindDetectionSCG-UE-Mixed1* respective maximum values for *pdccch-BlindDetection3* for the MCG and *pdccch-BlindDetection3* for the SCG, through *pdccch-BlindDetectionCG-UE2* in *pdccch-BlindDetectionMCG-UE-Mixed1* and *pdccch-BlindDetectionCG-UE2* in *pdccch-BlindDetectionSCG-UE-Mixed1* respective maximum values for *pdccch-BlindDetection2* for the MCG and *pdccch-BlindDetection2* for the SCG, and through *pdccch-BlindDetectionCG-UE3* in *pdccch-BlindDetectionMCG-UE-Mixed1* and *pdccch-BlindDetectionCG-UE3* in *pdccch-BlindDetectionSCG-UE-Mixed1* respective maximum values for *pdccch-BlindDetection4* for the MCG and *pdccch-BlindDetection4* for the SCG. + +If the UE reports *pdccch-BlindDetectionCA1* in *pdccch-BlindDetectionMixedList3*, + +- the value range of *pdccch-BlindDetectionCG-UE1* for the MCG or of *pdccch-BlindDetectionCG-UE1* for the SCG is [0, 1, ..., *pdccch-BlindDetectionCA1*], and +- *pdccch-BlindDetectionCG-UE1* for the MCG + *pdccch-BlindDetectionCG-UE1* for the SCG $\geq$ *pdccch-BlindDetectionCA1*. + +Otherwise, if is a maximum total number of downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r15monitoringcapability* and the UE is configured on both the MCG and the SCG for NR-DC as indicated in *UE-NR-Capability* + +- the value range of *pdccch-BlindDetectionCG-UE1* for the MCG or of *pdccch-BlindDetectionCG-UE1* for the SCG is [0, 1, 2], +- *pdccch-BlindDetectionCG-UE1* for the MCG + *pdccch-BlindDetectionCG-UE1* for the SCG $\geq$ . + +If the UE reports *pdccch-BlindDetectionCA2* in *pdccch-BlindDetectionMixedList3*, + +- the value range of *pdccch-BlindDetectionCG-UE2* for the MCG or of *pdccch-BlindDetectionCG-UE2* for the SCG is [0, 1, ..., *pdccch-BlindDetectionCA2*], and +- *pdccch-BlindDetectionCG-UE2* for the MCG + *pdccch-BlindDetectionCG-UE2* for the SCG $\geq$ *pdccch-BlindDetectionCA2*. + +Otherwise, if is a maximum total number of downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r16monitoringcapability* and the UE is configured on both the MCG and the SCG for NR-DC as indicated in *UE-NR-Capability* + +- the value range of *pdccch-BlindDetectionCG-UE2* for the MCG or of *pdccch-BlindDetectionCG-UE2* for the SCG is [0, 1], +- *pdccch-BlindDetectionCG-UE2* for the MCG + *pdccch-BlindDetectionCG-UE2* for the SCG $\geq$ . + +If the UE reports *pdccch-BlindDetectionCA3* in *pdccch-BlindDetectionMixedList3* + +- the value range of *pdccch-BlindDetectionCG-UE3* for the MCG or of *pdccch-BlindDetectionCG-UE3* for the SCG is [0, 1, ..., *pdccch-BlindDetectionCA3*], and +- *pdccch-BlindDetectionCG-UE3* for the MCG + *pdccch-BlindDetectionCG-UE3* for the SCG $\geq$ *pdccch-BlindDetectionCA3*. + +Otherwise, if $r17monitoringcapability$ is a maximum total number of downlink cells for which the UE is provided *monitoringCapabilityConfig* = $r17monitoringcapability$ and the UE is configured on both the MCG and the SCG for NR-DC as indicated in *UE-NR-Capability* + +- the value range of *pdch-BlindDetectionCG-UE3* for the MCG or of *pdch-BlindDetectionCG-UE3* for the SCG is [0, 1, 2], +- *pdch-BlindDetectionCG-UE3* for the MCG + *pdch-BlindDetectionCG-UE3* for the SCG $\geq$ . + +## 10.1 UE procedure for determining physical downlink control channel assignment + +A set of PDCCH candidates for a UE to monitor is defined in terms of PDCCH search space sets. A search space set can be a CSS set or a USS set. A UE monitors PDCCH candidates in one or more of the following search spaces sets + +- a Type0-PDCCH CSS set on the primary cell of the MCG configured by + - *pdch-ConfigSIB1* in MIB or by *searchSpaceSIB1* in *PDCCH-ConfigCommon* or by *searchSpaceZero* in *PDCCH-ConfigCommon* for a DCI format 1\_0 with CRC scrambled by a SI-RNTI, or + - *searchSpaceZero* by providing *searchSpaceID*=0 for *searchSpaceMCCH* or *searchSpaceMTCH* for a DCI format 4\_0 with CRC scrambled by a MCCH-RNTI or a G-RNTI for broadcast, or + - *searchSpaceZero* by providing *searchSpaceID*=0 for *searchspaceMulticastMCCH* for a DCI format 4\_0 with CRC scrambled by a multicast-MCCH-RNTI, or by *searchSpaceMulticastMTCH* for a DCI format 4\_1 with CRC scrambled by a G-RNTI for multicast in RRC\_INACTIVE state +- a Type0A-PDCCH CSS set configured by *searchSpaceOtherSystemInformation* in *PDCCH-ConfigCommon* for a DCI format 1\_0 with CRC scrambled by a SI-RNTI on the primary cell of the MCG +- a Type0B-PDCCH CSS set configured by + - *searchSpaceMCCH* and *searchSpaceMTCH* for a DCI format 4\_0 with CRC scrambled by a MCCH-RNTI or a G-RNTI for broadcast, on the primary cell of the MCG + - *searchspaceMulticastMCCH* for a DCI format 4\_0 with CRC scrambled by a multicast-MCCH-RNTI, or by *searchSpaceMulticastMTCH* for a DCI format 4\_1 with CRC scrambled by a G-RNTI for PDCCH receptions in RRC\_INACTIVE state +- a Type1-PDCCH CSS set configured by *ra-SearchSpace* in *PDCCH-ConfigCommon* for a DCI format with CRC scrambled by a RA-RNTI, a MsgB-RNTI, or a TC-RNTI on the primary cell +- a Type1A-PDCCH CSS set configured by *sdt-SearchSpace* in *PDCCH-ConfigCommon* for a DCI format with CRC scrambled by a C-RNTI or a CS-RNTI on the primary cell as described in clause 19.1 +- a Type2-PDCCH CSS set configured by *pagingSearchSpace* in *PDCCH-ConfigCommon* for a DCI format 1\_0 with CRC scrambled by a P-RNTI on the primary cell of the MCG +- a Type2A-PDCCH CSS set configured by *pei-SearchSpace* in *pei-ConfigBWP* for a DCI format 2\_7 with CRC scrambled by a PEI-RNTI on the primary cell of the MCG +- a Type3-PDCCH CSS set configured by + - *SearchSpace* in *PDCCH-Config* with *searchSpaceType* = *common* for DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, or NES-RNTI and, only for the primary cell, C-RNTI, MCS-C-RNTI, CS-RNTI(s), or PS-RNTI, or + - *SearchSpace* in *pdch-ConfigMulticast* for DCI formats with CRC scrambled by G-RNTI, or G-CS-RNTI, or + - *searchSpaceMCCH* and *searchSpaceMTCH* on a secondary cell for a DCI format 4\_0 with CRC scrambled by a MCCH-RNTI or a G-RNTI for broadcast, and +- a USS set configured by + +- *SearchSpace* in *PDCCH-Config* with *searchSpaceType* = *ue-Specific* for DCI formats with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI(s), SL-RNTI, SL-CS-RNTI, SL Semi-Persistent Scheduling V-RNTI, or NCR-RNTI + +In the following, DCI formats with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI are also referred to as unicast DCI formats, DCI formats with CRC scrambled by G-RNTI for multicast or G-CS-RNTI are also referred to as multicast DCI formats, and DCI formats with CRC scrambled by MCCH-RNTI or G-RNTI for broadcast scheduling PDSCH receptions are also referred to as broadcast DCI formats, and DCI formats with CRC scrambled by multicast-MCCH-RNTI or G-RNTI for multicast scheduling PDSCH receptions in RRC\_INACTIVE state are also referred as multicast DCI formats for RRC\_INACTIVE state. + +For a DL BWP, if a UE is not provided *searchSpaceSIB1* for Type0-PDCCH CSS set by *PDCCH-ConfigCommon*, the UE does not monitor PDCCH candidates for a Type0-PDCCH CSS set on the DL BWP. The Type0-PDCCH CSS set is defined by the CCE aggregation levels and the number of PDCCH candidates per CCE aggregation level given in Table 10.1-1. + +If the active DL BWP and the initial DL BWP for a UE have same SCS and same CP length and the active DL BWP includes all RBs of the CORESET with index 0, or the active DL BWP is the initial DL BWP, or the active DL BWP includes all RBs of an MBS frequency resource provided by *cfr-ConfigMCCH-MTCH* as described in clause 18, the CORESET configured for Type0-PDCCH CSS set has CORESET index 0 and the Type0-PDCCH CSS set has search space set index 0. + +If the active DL BWP and an MBS frequency resource provided by *cfr-ConfigMCCH-MTCH* or determined by CORESET with index 0 when *cfr-ConfigMCCH-MTCH* is not provided for a UE have same SCS and same CP length and the active DL BWP includes all RBs of the MBS frequency resource, and if the UE is provided *searchSpaceMCCH* or *searchSpaceMTCH* for Type0B-PDCCH CSS set on the primary cell or for Type3-PDCCH CSS set on a secondary cell, the UE monitors PDCCH for detection of broadcast DCI formats, as described in clause 18, on the active DL BWP. + +For a DL BWP, if a UE is not provided *searchSpaceOtherSystemInformation* for Type0A-PDCCH CSS set, the UE does not monitor PDCCH for Type0A-PDCCH CSS set on the DL BWP. The CCE aggregation levels and the number of PDCCH candidates per CCE aggregation level for Type0A-PDCCH CSS set are given in Table 10.1-1. + +For a DL BWP, if a UE is not provided *ra-SearchSpace* for Type1-PDCCH CSS set, the UE does not monitor PDCCH for Type1-PDCCH CSS set on the DL BWP. If the UE has not been provided a Type3-PDCCH CSS set, or a Type1A-PDCCH CSS set, or a USS set and the UE has received a C-RNTI and has been provided a Type1-PDCCH CSS set, the UE monitors PDCCH candidates for DCI format 0\_0 and DCI format 1\_0 with CRC scrambled by the C-RNTI in the Type1-PDCCH CSS set. + +If a UE is not provided *pagingSearchSpace* for Type2-PDCCH CSS set, the UE does not monitor PDCCH for Type2-PDCCH CSS set on the DL BWP. The CCE aggregation levels and the number of PDCCH candidates per CCE aggregation level for Type2-PDCCH CSS set are given in Table 10.1-1. + +If a UE is not provided *pei-SearchSpace* for Type2A-PDCCH CSS set, the UE does not monitor PDCCH for Type2A-PDCCH CSS set on the DL BWP. The CCE aggregation levels and the maximum number of PDCCH candidates per CCE aggregation level for Type2A-PDCCH CSS set are given in Table 10.1-1. If the UE is provided *pei-SearchSpace* with zero value for the Type2A-PDCCH CSS set index, and for the SS/PBCH block and CORESET multiplexing patterns 2 and 3, the UE determines PDCCH monitoring occasions as described in clause 13 and the CCE aggregation levels and the number of PDCCH candidates per CCE aggregation level for Type2A-PDCCH CSS set are given in Table 10.1-1. + +If a UE is provided a zero value for *searchSpaceID* in *PDCCH-ConfigCommon* for a Type0/0A/1A/2-PDCCH CSS set, the UE determines monitoring occasions for PDCCH candidates of the Type0/0A/1A/2-PDCCH CSS set as described in clause 13, and the UE is provided a C-RNTI, the UE monitors PDCCH candidates only at monitoring occasions associated with a SS/PBCH block, where the SS/PBCH block is determined by the most recent of + +- a MAC CE activation command indicating a TCI state of the active BWP that includes a CORESET with index 0, as described in [6, TS 38.214], where the TCI-state includes a CSI-RS which is quasi-co-located with the SS/PBCH block, or +- a random access procedure that is not initiated by a PDCCH order that triggers a contention-free random access procedure, or +- configured-grant based PUSCH transmission in RRC\_INACTIVE state as described in clause 19.1. + +If a UE monitors PDCCH candidates for DCI formats with CRC scrambled by a C-RNTI and the UE is provided a non-zero value for *searchSpaceID* in *PDCCH-ConfigCommon* for a Type0/0A/1A/2-PDCCH CSS set, or monitors PDCCH candidates for DCI formats with CRC scrambled by a MCCH-RNTI or a G-RNTI for broadcast and the UE is provided a non-zero value for *searchSpaceMCCH* and *searchSpaceMTCH* in *PDCCH-ConfigCommon* for a Type0B-PDCCH CSS set, or monitors PDCCH candidates for DCI formats with CRC scrambled by a multicast-MCCH-RNTI or a G-RNTI for multicast in RRC\_INACTIVE state and the UE is provided a non-zero value for *searchSpaceMulticastMCCH* and *searchSpaceMulticastMTCH* in *PDCCH-ConfigCommon* for a Type0B-PDCCH CSS set, the UE determines monitoring occasions for PDCCH candidates of the Type0/0A/1A/2-PDCCH CSS set, or of the Type0B-PDCCH CSS set, respectively, based on the search space set associated with the value of *searchSpaceID*. + +The UE may assume that the DM-RS antenna port associated with PDCCH receptions in the CORESET configured by *pdcch-ConfigSIB1* in *MIB*, the DM-RS antenna port associated with corresponding PDSCH receptions, and the corresponding SS/PBCH block are quasi co-located with respect to average gain, quasi co-location 'typeA' and 'typeD' properties, when applicable [6, TS 38.214], if the UE is not provided a TCI state indicating quasi co-location information of the DM-RS antenna port for PDCCH reception in the CORESET. The value for the DM-RS scrambling sequence initialization is the cell ID. For operation without shared spectrum channel access in FR1 and FR2-1, a SCS is provided by *subCarrierSpacingCommon* in *MIB*. For operation with shared spectrum channel access in FR1 and for operation in FR2-2, a SCS is same as the SCS of a corresponding SS/PBCH block. + +For single cell operation or for operation with carrier aggregation in a same frequency band, a UE does not expect to monitor a PDCCH in a Type0/0A/0B/2/3-PDCCH CSS set or in a USS set if a DM-RS for monitoring a PDCCH in a Type1-PDCCH CSS set is not configured with same *qcl-Type* set to 'typeD' properties [6, TS 38.214] with a DM-RS for monitoring the PDCCH in the Type0/0A/0B/2/3-PDCCH CSS set or in the USS set, and if the PDCCH or an associated PDSCH overlaps in at least one symbol with a PDCCH the UE monitors in a Type1-PDCCH CSS set or with an associated PDSCH. + +If a UE is provided + +- one or more search space sets by corresponding one or more of *searchSpaceZero*, *searchSpaceSIB1*, *searchSpaceOtherSystemInformation*, *pagingSearchSpace*, *ra-SearchSpace*, and +- a C-RNTI, an MCS-C-RNTI, or a CS-RNTI + +the UE monitors PDCCH candidates for DCI format 0\_0 and DCI format 1\_0 with CRC scrambled by the C-RNTI, the MCS-C-RNTI, or the CS-RNTI in the one or more search space sets in a slot where the UE monitors PDCCH candidates for at least a DCI format 0\_0 or a DCI format 1\_0 with CRC scrambled by SI-RNTI, RA-RNTI, MsgB-RNTI, or P-RNTI. + +If a UE is provided + +- one or more search space sets by corresponding one or more of *searchSpaceZero*, *searchSpaceSIB1*, *searchSpaceOtherSystemInformation*, *pagingSearchSpace*, *pei-SearchSpace*, *ra-SearchSpace*, or a CSS set by *PDCCH-Config*, and +- a SI-RNTI, a P-RNTI, a PEI-RNTI, a RA-RNTI, a MsgB-RNTI, a SFI-RNTI, an INT-RNTI, a TPC-PUSCH-RNTI, a TPC-PUCCH-RNTI, or a TPC-SRS-RNTI + +then, for a RNTI from any of these RNTIs, the UE does not expect to process information from more than one DCI format with CRC scrambled with the RNTI per slot. + +**Table 10.1-1: CCE aggregation levels and maximum number of PDCCH candidates per CCE aggregation level for CSS sets configured by *searchSpaceSIB1*** + +| CCE Aggregation Level | Number of Candidates | +|-----------------------|----------------------| +| 4 | 4 | +| 8 | 2 | +| 16 | 1 | + +For each DL BWP configured to a UE in a serving cell, the UE can be provided by higher layer signalling with + +- CORESETs if *coresetPoolIndex* is not provided, or if a value of *coresetPoolIndex* is same for all CORESETs if *coresetPoolIndex* is provided + +- CORESETs if *coresetPoolIndex* is not provided for a first CORESET, or is provided and has a value 0 for a first CORESET, and is provided and has a value 1 for a second CORESET + +For each CORESET, the UE is provided the following by *ControlResourceSet*: + +- a CORESET index , by *controlResourceSetId* or by *controlResourceSetId-v1610*, where + - if *coresetPoolIndex* is not provided, or if a value of *coresetPoolIndex* is same for all CORESETs if *coresetPoolIndex* is provided; + - if *coresetPoolIndex* is not provided for a first CORESET, or is provided and has a value 0 for a first CORESET, and is provided and has a value 1 for a second CORESET; +- a DM-RS scrambling sequence initialization value by *pdcch-DMRS-ScramblingID*; +- a precoder granularity for a number of REGs in the frequency domain where the UE can assume use of a same DM-RS precoder by *precoderGranularity*; +- a number of consecutive symbols provided by *duration*; +- a set of resource blocks provided by *frequencyDomainResources*; +- CCE-to-REG mapping parameters provided by *cce-REG-MappingType*; +- an antenna port quasi co-location, from a set of antenna port quasi co-locations provided by *TCI-State*, indicating quasi co-location information of the DM-RS antenna port for PDCCH reception; +- an indication for a presence or absence of a transmission configuration indication (TCI) field for a DCI format, other than DCI format 1\_0, that schedules PDSCH receptions or has associated HARQ-ACK information without scheduling PDSCH and is provided by a PDCCH in CORESET , by *tci-PresentInDCI* or *tci-PresentDCI-1-2*. + +When *precoderGranularity* = *allContiguousRBs*, a UE does not expect + +- to be configured a set of resource blocks of a CORESET that includes more than four sub-sets of resource blocks that are not contiguous in frequency +- any RE of a CORESET to overlap with any RE determined from + - *lte-CRS-ToMatchAround* or *LTE-CRS-PatternList*, if the UE is not provided *pdcchCandidateReception-WithCRSOverlap*, or + - a SS/PBCH block. + +If a UE is provided two TCI states indicating quasi co-location information of the DM-RS antenna port for PDCCH reception in a CORESET associated with a Type3-PDCCH CSS set, the UE may assume the quasi co-location information indicated in both of the two TCI states for the PDCCH reception in the CORESET. + +For each CORESET in a DL BWP of a serving cell, a respective *frequencyDomainResources* provides a bitmap + +- if a CORESET is not associated with any search space set configured with *freqMonitorLocations*, the bits of the bitmap have a one-to-one mapping with non-overlapping groups of 6 consecutive PRBs, in ascending order of the PRB index in the DL BWP bandwidth of PRBs with starting common RB position , where the first common RB of the first group of 6 PRBs has common RB index if *rb-Offset* is not provided, or the first common RB of the first group of 6 PRBs has common RB index where is provided by *rb-Offset*. +- if a CORESET is associated with at least one search space set configured with *freqMonitorLocations*, the first bits of the bitmap have a one-to-one mapping with non-overlapping groups of 6 consecutive PRBs, in ascending order of the PRB index in each RB set in the DL BWP bandwidth of PRBs with starting common RB position [6, TS 38.214], where the first common RB of the first group of 6 PRBs has common RB index and *k* is indicated by *freqMonitorLocations* if provided for a search space set; otherwise, *k* is a number of available PRBs in the RB set 0 for the DL BWP, and *k* is provided by *rb-Offset* or if *rb-Offset* is not provided. If a UE is provided RB sets in the DL BWP, the UE expects that the RBs of the CORESET are within the union of the PRBs in the RB sets of the DL BWP. + +For each CORESET provided by *cfr-ConfigMCCH-MTCH* or *cfr-ConfigMulticast* in a CFR of a serving cell, the quantities and in this clause are replaced by the size of CFR and starting common RB position of CFR, respectively. + +For a CORESET other than a CORESET with index 0, + +- if a UE has not been provided a configuration of TCI state(s) by *tci-StatesPDCCH-ToAddList* and *tci-StatesPDCCH-ToReleaseList* for the CORESET, or has been provided initial configuration of more than one TCI states for the CORESET by *tci-StatesPDCCH-ToAddList* and *tci-StatesPDCCH-ToReleaseList* and has not received a MAC CE activation command for one of the TCI states as described in [11, TS 38.321], the UE assumes that the DM-RS antenna port associated with PDCCH receptions is quasi co-located with the SS/PBCH block the UE identified during the initial access procedure, or for a most recent configured grant PUSCH transmission as described in clause 19 for a same HARQ process; +- if a UE has been provided a configuration of more than one TCI states by *tci-StatesPDCCH-ToAddList* and *tci-StatesPDCCH-ToReleaseList* for the CORESET as part of Reconfiguration with sync procedure as described in [12, TS 38.331] and has not received a MAC CE activation command for one of the TCI states as described in [11, TS 38.321], the UE assumes that the DM-RS antenna port associated with PDCCH receptions is quasi co-located with the SS/PBCH block or the CSI-RS resource the UE identified during the random access procedure initiated by the Reconfiguration with sync procedure as described in [12, TS 38.331]. + +For a CORESET with index 0, + +- if the UE is provided *TCI-State* and *followUnifiedTCI-State* for the CORESET, the UE assumes that a DM-RS antenna port for PDCCH receptions in the CORESET and a DM-RS antenna port for PDSCH receptions scheduled by DCI formats provided by PDCCH receptions in the CORESET are quasi co-located with the reference signals provided by the indicated *TCI-State* [6, TS 38.214] +- else if the UE is provided *dl-OrJointTCI-StateList* and is indicated a first *TCI-State* and a second *TCI-State*, and *apply-IndicatedTCIState* for the CORESET + - if *apply-IndicatedTCIState* = 'first', the UE assumes that a DM-RS antenna port for PDCCH receptions in the CORESET is quasi co-located with the reference signals provided by the first *TCI-State*, + - if *apply-IndicatedTCIState* = 'second', the UE assumes that a DM-RS antenna port for PDCCH receptions in the CORESET is quasi co-located with the reference signals provided by the second *TCI-State*, + - if *apply-IndicatedTCIState* = 'both', the UE assumes that a DM-RS antenna port for PDCCH receptions in the CORESET is quasi co-located with the reference signals provided by the first and the second *TCI-State*. +- else, the UE assumes that a DM-RS antenna port for PDCCH receptions in the CORESET is quasi co-located with + - the one or more DL RS configured by a TCI state, where the TCI state is indicated by a MAC CE activation command for the CORESET, if any, or + - a SS/PBCH block the UE identified during a most recent random access procedure not initiated by a PDCCH order that triggers a contention-free random access procedure, if no MAC CE activation command indicating a TCI state for the CORESET is received after the most recent random access procedure, or a SS/PBCH block the UE identified during a most recent configured grant PUSCH transmission as described in clause 19. + +For a CORESET other than a CORESET with index 0, if a UE is provided a single TCI state for a CORESET, or if the UE receives a MAC CE activation command for one or two of the provided TCI states for a CORESET, the UE assumes that the DM-RS antenna port associated with PDCCH receptions in the CORESET is quasi co-located with the one or more DL RS configured by the TCI states. For a CORESET with index 0, the UE expects that a CSI-RS configured with *qcl-Type* set to 'typeD' in a TCI state indicated by a MAC CE activation command for the CORESET is provided by a SS/PBCH block + +- if the UE receives a MAC CE activation command for one of the TCI states, the UE applies the activation command in the first slot that is after slot where is the slot where the UE would transmit a PUCCH with HARQ-ACK information for the PDSCH providing the activation command, is the SCS configuration for the PUCCH in the slot when the activation command is applied, and is a number of slots for SCS configuration provided by *kmac* or if *kmac* is not provided. + +If a UE is provided *TCI-State* in *dl-OrJointTCI-StateList*, a DM-RS antenna port for PDCCH receptions in a CORESET, other than a CORESET with index 0, associated only with USS sets and/or Type3-PDCCH CSS sets, and a + +DM-RS antenna port for PDSCH receptions scheduled by DCI formats provided by PDCCH receptions in the CORESET are quasi co-located with reference signals provided by the indicated *TCI-State* [6, TS 38.214]. + +If a UE is provided *followUnifiedTCI-State* for a CORESET, other than a CORESET with index 0, associated at least with CSS sets other than Type3-PDCCH CSS sets, a DM-RS antenna port for PDCCH receptions in the CORESET and a DM-RS antenna port for PDSCH receptions scheduled by DCI formats provided by PDCCH receptions in the CORESET are quasi co-located with reference signals provided by the indicated *TCI-State*. + +If a UE is provided *dl-OrJointTCI-StateList* and is indicated a first *TCI-State* and a second *TCI-State*, and is provided *apply-IndicatedTCIState* for a CORESET, other than a CORESET with index 0, + +- if the CORESET is associated only with USS sets and/or Type3-PDCCH CSS sets + - if *apply-IndicatedTCIState* = 'first', the UE assumes that a DM-RS antenna port for PDCCH receptions in the CORESET is quasi co-located with the reference signals provided by the first *TCI-State* + - if *apply-IndicatedTCIState* = 'second', the UE assumes that a DM-RS antenna port for PDCCH receptions in the CORESET is quasi co-located with the reference signals provided by the second *TCI-State* + - if *apply-IndicatedTCIState* = 'both', the UE assumes that a DM-RS antenna port for PDCCH receptions in the CORESET is quasi co-located with the reference signals provided by the first *TCI-State* and the second *TCI-State* +- if the CORESET is associated at least with CSS sets other than Type3-PDCCH CSS sets, + - if *apply-IndicatedTCIState* = 'first', the UE assumes that a DM-RS antenna port for PDCCH receptions in the CORESET is quasi co-located with the reference signals provided by the first *TCI-State* + - if *apply-IndicatedTCIState* = 'second', the UE assumes that a DM-RS antenna port for PDCCH receptions in the CORESET is quasi co-located with the reference signals provided by the second *TCI-State* + - if *apply-IndicatedTCIState* = 'both', the UE assumes that a DM-RS antenna port for PDCCH receptions in the CORESET is quasi co-located with the reference signals provided by the first *TCI-State* and the second *TCI-State* + - if *apply-IndicatedTCIState* = 'none', the UE assumes that a DM-RS antenna port for PDCCH receptions in the CORESET is quasi co-located with the one or more DL RS configured by a TCI state indicated by a MAC CE activation command for the CORESET + +If the UE is provided *dl-OrJointTCI-StateList* and + +- is not provided *coresetPoolIndex* or is provided *coresetPoolIndex* with a value of 0 for first CORESETs on an active DL BWP of a serving cell, +- is provided *coresetPoolIndex* with a value of 1 for second CORESETs on the active DL BWP of the serving cells, and +- is provided *followUnifiedTCI-State* for the first and second CORESETs, that do not include a CORESET with index 0 and are associated only with USS sets and/or Type3-PDCCH CSS sets, or with CSS sets other than Type3-PDCCH CSS sets, + +the UE + +- assumes that DM-RS antenna ports for PDCCH receptions in the first and second CORESETs, and DM-RS antenna ports for PDSCH receptions scheduled by DCI formats provided by PDCCH receptions in the first and second CORESETs, are quasi co-located with the reference signals provided by indicated *TCI-State* specific to the first and second CORESETs, respectively +- transmits PUSCH scheduled by DCI formats provided by PDCCH receptions in the first and second CORESETs using a spatial domain filter corresponding to *TCI-State* or *TCI-UL-State* specific to the first and second CORESETs, respectively. + +If a UE is provided two *coresetPoolIndex* values 0 and 1 for first and second CORESETs, or is not provided *coresetPoolIndex* value for first CORESETs and is provided *coresetPoolIndex* value of 1 for second CORESETs, respectively, a MAC CE command activating TCI states for the first or second CORESETs [11, TS 38.321] can include *coresetPoolIndex* value 0 or 1 + +- if the UE is provided *SSB\_MTC\_AdditionalPCI*, the activated TCI states for the first and/or the second CORESETs are for *physCellId* from *ServingCellConfigCommon* and the activated TCI states for either the first or the second CORESETs can be for *physCellId* from *additionalPCI*. + +If a UE is provided by *simultaneousTCI-UpdateList1* or *simultaneousTCI-UpdateList2* up to two lists of cells for simultaneous TCI state activation, the UE applies the antenna port quasi co-location provided by one or two *TCI-State* each with same activated *tci-StateID* value, to CORESETs with a same index in all configured DL BWPs of all configured cells in a list determined from a serving cell index, where one or two *tci-StateID*, the CORESET index, and the serving cell index are provided by a MAC CE command. + +For each DL BWP configured to a UE in a serving cell, the UE is provided by higher layers with search space sets where, for each search space set from the search space sets, the UE is provided the following by *SearchSpace*: + +- a search space set index , , by *searchSpaceId* +- an association between the search space set and a CORESET by *controlResourceSetId* or by *controlResourceSetId-v1610* +- a PDCCH monitoring periodicity of slots and a PDCCH monitoring offset of slots, by *monitoringSlotPeriodicityAndOffset* or by *monitoringSlotPeriodicityAndOffset-r17* +- a PDCCH monitoring pattern within a slot, indicating first symbol(s) of the CORESET for PDCCH monitoring within each slot where the UE monitors PDCCH, by *monitoringSymbolsWithinSlot* +- a duration of indicating a number of slots that the search space set exists by *duration*, or a number of slots in consecutive groups of slots where the search space set can exist by *duration-r17* +- a bitmap, by *monitoringSlotsWithinSlotGroup*, that applies per group of slots and provides a PDCCH monitoring pattern indicating slots in a group of slots for PDCCH monitoring + - a size of the group of slots is same as a size of *monitoringSlotsWithinSlotGroup* + - for a Type1-PDCCH CSS set provided by *ra-SearchSpace* in dedicated RRC signaling, or for a Type3-PDCCH CSS set, or for a USS set, the PDCCH monitoring pattern indicates only consecutive slots in the group of slots for PDCCH monitoring and, at least for one combination indicated by the UE as a capability, a number of the consecutive slots is not larger than + - for a Type1-PDCCH CSS set provided by *ra-SearchSpace* in *SIB1*, the PDCCH monitoring pattern indicates only up to 1 slot in the group of slots for PDCCH monitoring + - for a Type0-PDCCH CSS set or for a Type0A-PDCCH CSS set, or for a Type2-PDCCH CSS set, the PDCCH monitoring pattern indicates slots in the group of slots for PDCCH monitoring, and the slots are not restricted to be consecutive, and the number of those slots is not larger than the size of *monitoringSlotsWithinSlotGroup* +- a number of PDCCH candidates per CCE aggregation level by *aggregationLevel1*, *aggregationLevel2*, *aggregationLevel4*, *aggregationLevel8*, and *aggregationLevel16*, for CCE aggregation level 1, CCE aggregation level 2, CCE aggregation level 4, CCE aggregation level 8, and CCE aggregation level 16, respectively +- an indication that search space set is either a CSS set or a USS set by *searchSpaceType* +- if search space set is a CSS set + - an indication by *dci-Format0-0-AndFormat1-0* to monitor PDCCH candidates for DCI format 0\_0 and DCI format 1\_0 + - an indication by *dci-Format2-0* to monitor one or two PDCCH candidates, or to monitor one PDCCH candidate per RB set if the UE is provided *freqMonitorLocations* for the search space set, for DCI format 2\_0 and a corresponding CCE aggregation level + - an indication by *dci-Format2-1* to monitor PDCCH candidates for DCI format 2\_1 + - an indication by *dci-Format2-2* to monitor PDCCH candidates for DCI format 2\_2 + - an indication by *dci-Format2-3* to monitor PDCCH candidates for DCI format 2\_3 + +- an indication by *dci-Format2-4* to monitor PDCCH candidates for DCI format 2\_4 +- an indication by *dci-Format2-6* to monitor PDCCH candidates for DCI format 2\_6 +- an indication by *dci-Format2-9* to monitor PDCCH candidates for DCI format 2\_9 +- an indication by *dci-Format4-0* to monitor PDCCH candidates for DCI format 4\_0 +- an indication by *dci-Format4-1*, or *dci-Format4-2*, or *dci-Format4-1-AndFormat4-2* to monitor PDCCH candidates for DCI format 4\_1, or DCI format 4\_2, or for both DCI format 4\_1 and DCI format 4\_2, respectively +- an indication by *searchSpaceLinkingId* that search space set is linked to another search space set for which is provided a same value for *searchSpaceLinkingId* +- if search space set is a USS set, + - an indication by *dci-Formats* to monitor PDCCH candidates either for DCI format 0\_0 and DCI format 1\_0, or for DCI format 0\_1 and DCI format 1\_1, or + - an indication by *dci-FormatsExt* to monitor PDCCH candidates for DCI format 0\_2 and DCI format 1\_2, or for DCI format 0\_1, DCI format 1\_1, DCI format 0\_2, and DCI format 1\_2, or + - an indication by *dci-FormatsMC* to monitor PDCCH candidates for one or both of DCI format 0\_3 and DCI format 1\_3, or + - an indication by *dci-FormatsSL* to monitor PDCCH candidates for DCI format 0\_0 and DCI format 1\_0, or for DCI format 0\_1 and DCI format 1\_1, or for DCI format 3\_0, or for DCI format 3\_1, or for DCI format 3\_0 and DCI format 3\_1, on an indication by *dci-Format-NCR* to monitor PDCCH candidates for DCI format 2\_8 +- a bitmap by *freqMonitorLocations*, if provided, to indicate an index of one or more RB sets for the search space set, where the MSB in the bitmap corresponds to RB set in the DL BWP. For RB set indicated in the bitmap, the first PRB of the frequency domain monitoring location confined within the RB set is given by $\sum_{i=0}^{k-1} 2^i \cdot b_i$ , where $b_i$ is the index of first common RB of the RB set [6, TS 38.214], and is provided by *rb-Offset* or if *rb-Offset* is not provided. For each RB set with a corresponding value of 1 in the bitmap, the frequency domain resource allocation pattern for the monitoring location is determined based on the first bits in *frequencyDomainResources* provided by the associated CORESET configuration. + +If the *monitoringSymbolsWithinSlot* indicates to a UE to monitor PDCCH in a subset of up to three consecutive symbols that are same in every slot where the UE monitors PDCCH for all search space sets, the UE does not expect to be configured with a PDCCH SCS other than 15 kHz if the subset includes at least one symbol after the third symbol. + +A UE does not expect to be provided a first symbol and a number of consecutive symbols for a CORESET that results to a PDCCH candidate mapping to symbols of different slots. + +A UE does not expect any two PDCCH monitoring occasions on an active DL BWP, for a same search space set or for different search space sets, in a same CORESET to be separated by a non-zero number of symbols that is smaller than the CORESET duration. + +A UE determines a PDCCH monitoring occasion on an active DL BWP from the PDCCH monitoring periodicity, the PDCCH monitoring offset, and the PDCCH monitoring pattern within a slot. If *monitoringSlotsWithinSlotGroup* is not provided, the UE determines that PDCCH monitoring occasions exist in a slot with number $\lfloor n_f / P \rfloor \bmod P$ [4, TS 38.211] in a frame with number $n_f$ if $(+)$ . The UE monitors PDCCH candidates for search space set for consecutive slots, starting from slot $\lfloor n_f / P \rfloor \bmod P$ , and does not monitor PDCCH candidates for search space set for the next consecutive slots. If *monitoringSlotsWithinSlotGroup* is provided, for search space set, the UE determines that the slot with number $\lfloor n_f / P \rfloor \bmod P$ [4, TS 38.211] in a frame with number $n_f$ satisfying $(+)$ is the first slot in a first group of slots and that PDCCH monitoring occasions exist in consecutive groups of slots starting from the first group, where is the size of *monitoringSlotsWithinSlotGroup*. The UE monitors PDCCH candidates for search space set within consecutive groups of slots according to *monitoringSlotsWithinSlotGroup*, starting from slot $\lfloor n_f / P \rfloor \bmod P$ , and does not monitor PDCCH candidates for search space set for the next consecutive slots. + +A USS at CCE aggregation level is defined by a set of PDCCH candidates for CCE aggregation level. + +If a UE is configured with *CrossCarrierSchedulingConfig* for a serving cell, the carrier indicator field value corresponds to the value indicated by *cif-InSchedulingCell* in *CrossCarrierSchedulingConfig*. If a UE is configured with *MC-DCI-SetofCells* for a set of serving cells, the UE can be provided *nCI-Value* for the set of serving cells. + +For an active DL BWP of a serving cell on which a UE monitors PDCCH candidates in a USS, if the UE is not configured with a carrier indicator field, the UE monitors the PDCCH candidates without carrier indicator field. For an active DL BWP of a serving cell on which a UE monitors PDCCH candidates in a USS, if a UE is configured with a carrier indicator field, the UE monitors the PDCCH candidates with carrier indicator field. + +A UE does not expect to monitor PDCCH candidates on an active DL BWP of a secondary cell if the UE is configured to monitor PDCCH candidates for detection of DCI formats scheduling on that secondary cell in another serving cell. For a serving cell included in *MC-DCI-SetofCells*, if provided, the UE does not expect to monitor PDCCH candidates on more than one scheduling cell for detection of DCI formats scheduling on the serving cell. For the active DL BWP of a serving cell on which the UE monitors PDCCH candidates, the UE monitors PDCCH candidates at least for the same serving cell. + +For a search space set associated with CORESET, the CCE indexes for aggregation level corresponding to PDCCH candidate of the search space set in slot for an active DL BWP of a serving cell corresponding to carrier indicator field value, or corresponding to value of *nCI-Value* associated with a set of serving cells *MC-DCI-SetofCells*, are given by + +where + +for any CSS, ; + +for a USS, , , for , for , for , and ; + +; + +is the number of CCEs, numbered from 0 to , in CORESET and, if any, per RB set + +- for CORESET 0, the CCEs are obtained prior to puncturing, if any, of corresponding RBs [4, TS 38.211]; + +is + +- the carrier indicator field value, if provided by *cif-InSchedulingCell* in *CrossCarrierSchedulingConfig* for the serving cell on which PDCCH is monitored, except for scheduling of the serving cell from the same serving cell in which case ; +- the *nCI-Value*, if provided, for the set of serving cells *MC-DCI-SetofCells*; +- otherwise, including for any CSS, + +, where is the number of PDCCH candidates the UE is configured to monitor for aggregation level of a search space set for a serving cell corresponding to ; + +for any CSS, ; + +for a USS, is the maximum of over all configured values for a CCE aggregation level of search space set ; + +the RNTI value used for is the C-RNTI. + +For search space sets and that include *searchSpaceLinkingId* with same value, a UE monitors, in monitoring occasions with same index according to each of search space sets and in a slot, PDCCH candidates and, with, for detection of a DCI format with same information. The UE expects, , , and a same number of non-overlapping PDCCH monitoring occasions per slot based on corresponding *monitoringSymbolsWithinSlot*, for search space sets and. For CORESET associated with the search space set and for CORESET associated with the search space set, the UE is provided *tci-PresentInDCI* or *tci-PresentDCI-1-2* for either none or both of CORESETs and. For CORESET associated with the search space set and for CORESET associated with the search space set, the UE is either not provided *coresetPoolIndex* value of 1 for any of the two CORESETs, or is provided *coresetPoolIndex* value of 1 for both CORESETs. + +A UE can indicate by *numBD-twoPDCCH-r17* a capability for counting PDCCH candidates and either as 2 PDCCH candidates or as 3 PDCCH candidates. + +For search space sets $s$ and $s'$ that include *searchSpaceLinkingId* with same value, and for search space sets $s$ and $s'$ that include *searchSpaceLinkingId* with same value, a UE expects to simultaneously monitor PDCCH candidates $c$ , and $c'$ = only if a first CCE of $c$ or $c'$ has different index than a first CCE of $c$ or $c'$ in a CORESET configured with *cce-REG-MappingType* = 'nonInterleaved' and with duration of one symbol. + +If a UE + +- is provided *monitoringCapabilityConfig* = *r16monitoringcapability* for a downlink cell, +- is provided, by *searchSpaceLinkingId* a same value for search space sets $s$ and $s'$ on the downlink cell, and +- indicates *numBD-twoPDCCH-r17* with value of 3 + +the UE counts each PDCCH candidate for the one of the search space sets $s$ and $s'$ that the UE monitors PDCCH in the later span, as two PDCCH candidates. The UE does not expect a first PDCCH candidate from search space set $s$ or $s'$ and a second PDCCH candidate from a search space set $s$ that does not include *searchSpaceLinkingId* to use a same set of CCEs and same scrambling in a same CORESET, and provide respective first and second DCI formats with same size, in any span other than the first span in a slot. + +A UE does not expect to be provided *freqMonitorLocations* for a search space set $s$ in a serving cell if *intraCellGuardBandsDL-List* indicates that no intra-cell guard-bands are configured for the serving cell. + +A UE that + +- is configured for operation with carrier aggregation, and +- indicates support of search space sharing through *searchSpaceSharingCA-UL* or through *searchSpaceSharingCA-DL*, and +- has a PDCCH candidate with CCE aggregation level $L$ in CORESET $c$ associated with search space set $s$ of a scheduling cell for detection of a first DCI format, other than DCI format 0\_0 or DCI format 1\_0, having a first size and scheduling + - PUSCH transmission or configured grant Type 2 PUSCH release on serving cell $c$ , or + - PDSCH reception or having associated HARQ-ACK information without scheduling PDSCH reception on serving cell + +can receive a corresponding PDCCH through a PDCCH candidate with CCE aggregation level $L$ in CORESET $c$ associated with search space set $s$ of the scheduling cell for detection of a second DCI format having a second size and associated with scheduling on serving cell $c$ if the first size and the second size are same and if neither of search space sets $s$ and $s'$ includes *searchSpaceLinkingId*. + +A UE expects to monitor PDCCH candidates for up to 4 sizes of DCI formats that include up to 3 sizes of DCI formats with CRC scrambled by C-RNTI per serving cell. The UE counts a number of sizes for DCI formats per serving cell based on a number of configured PDCCH candidates in respective search space sets for the corresponding active DL BWP. If the UE monitors PDCCH candidates for detection of one or both of DCI format 0\_3 and DCI format 1\_3 for scheduling on serving cells from a set of serving cells, the serving cell for counting the size of one or both DCI format 0\_3 and DCI format 1\_3, respectively, is + +- the scheduling cell, if the scheduling cell is included in the set of serving cells and the UE is provided search space sets for the PDCCH candidates only on the scheduling cell +- a serving cell from the set of serving cells, if search space sets with same *searchSpaceId* for one or both of DCI format 0\_3 and DCI format 1\_3, respectively, are provided on the serving cell and on the scheduling cell. + +A UE does not expect to detect, in a same PDCCH monitoring occasion, a DCI format with CRC scrambled by a SI-RNTI, RA-RNTI, MsgB-RNTI, TC-RNTI, P-RNTI, C-RNTI, CS-RNTI, MCS-RNTI, MCCH-RNTI, G-RNTI, G-CS-RNTI, or multicast-MCCH-RNTI and a DCI format with CRC scrambled by a SL-RNTI or a SL-CS-RNTI for scheduling respective PDSCH reception and PSSCH transmission on a same serving cell. + +A PDCCH candidate with index $c$ for a search space set $s$ using a set of CCEs in a CORESET $c$ on the active DL BWP for serving cell $c$ , or for set of serving cells associated with *nCI-Value* having value $c$ , is not counted for monitoring if there is a PDCCH candidate with index $c$ for a search space set $s$ , or if there is a PDCCH candidate with index $c$ and $s$ , in the CORESET $c$ on the active DL BWP for serving cell $c$ , or for set of serving cells $c$ , respectively, using a same set of CCEs, + +the PDCCH candidates have identical scrambling, and the corresponding DCI formats for the PDCCH candidates have a same size; otherwise, the PDCCH candidate with index $i$ is counted for monitoring. + +For search space sets $s$ and $s'$ that include *searchSpaceLinkingId* with same value, and for search space set $s$ that does not include *searchSpaceLinkingId*, when a UE + +- monitors PDCCH candidates $i$ for detection of a first DCI format, +- monitors PDCCH candidate $i$ for detection of a second DCI format having a same size as the first DCI format, +- the PDCCH candidate $i$ , or the PDCCH candidate $i$ , and the PDCCH candidate $i$ have identical scrambling and use a same set of CCEs over same symbols in a CORESET, + +the PDCCH candidate $i$ is not counted for monitoring and the UE assumes that a detected DCI format is the first DCI format. A UE may monitor PDCCH candidate $i$ depending on a corresponding capability [18, TS 38.306]. + +For search space sets $s$ and $s'$ that include *searchSpaceLinkingId* with same value, and for search space set $s$ that does not include *searchSpaceLinkingId*, when a UE + +- monitors PDCCH candidates $i$ for detection of a first DCI format and monitors PDCCH candidate $i$ for detection of a second DCI format, or monitors PDCCH candidates $i$ for detection of the first DCI format and monitors PDCCH candidate $i$ for detection of the second DCI format, and +- one of the PDCCH candidates $i$ and $i$ , and the PDCCH candidate $i$ , or one of the PDCCH candidates $i$ and $i$ , and the PDCCH candidate $i$ , have a first CCE with same index and are simultaneously monitored in a CORESET with *cce-REG-MappingType* = 'nonInterleaved' and duration of one symbol, + +the UE assumes that a detected DCI format is the first DCI format. + +For search space sets $s$ and $s'$ , that include *searchSpaceLinkingId* with same value, and for search space sets $s$ and $s'$ that include *searchSpaceLinkingId* with same value, and for detection of DCI formats with same size, a UE expects different CCEs or different scrambling in a CORESET for any of first PDCCH candidates $i$ and $i$ , with $i$ , and any of second PDCCH candidates $i$ and $i$ , with $i$ that the UE would simultaneously monitor. + +Table 10.1-2 provides the maximum number of monitored PDCCH candidates, $N$ , per slot for a UE in a DL BWP with SCS configuration $\mu$ for operation with a single serving cell. + +**Table 10.1-2: Maximum number of monitored PDCCH candidates per slot for a DL BWP with SCS configuration for a single serving cell** + +| | Maximum number of monitored PDCCH candidates per slot and per serving cell | +|---|----------------------------------------------------------------------------| +| 0 | 44 | +| 1 | 36 | +| 2 | 22 | +| 3 | 20 | + +Table 10.1-2A provides the maximum number of monitored PDCCH candidates, $N$ , per span for a UE in a DL BWP with SCS configuration $\mu$ for operation with a single serving cell. + +**Table 10.1-2A: Maximum number of monitored PDCCH candidates in a span for combination for a DL BWP with SCS configuration for a single serving cell** + +| | Maximum number of monitored PDCCH candidates per span for combination and per serving cell | | | +|---|--------------------------------------------------------------------------------------------|--------|--------| +| | (2, 2) | (4, 3) | (7, 3) | +| 0 | 14 | 28 | 44 | +| 1 | 12 | 24 | 36 | + +Table 10.1-2B provides the maximum number of monitored PDCCH candidates, $N$ , per group of slots for combination for a UE in a DL BWP with SCS configuration $\mu$ for operation with a single serving cell. + +**Table 10.1-2B: Maximum number of monitored PDCCH candidates per group of slots for combination for a DL BWP with SCS configuration for a single serving cell** + +| | Maximum number of monitored PDCCH candidates in a group of slots per combination and per serving cell | | | | +|---|-------------------------------------------------------------------------------------------------------|--------|--------|--------| +| | (4, 1) | (4, 2) | (8, 1) | (8, 4) | +| 5 | 20 | 20 | - | - | +| 6 | 10 | 10 | 20 | 20 | + +Table 10.1-3 provides the maximum number of non-overlapped CCEs, , for a DL BWP with SCS configuration that a UE is expected to monitor corresponding PDCCH candidates per slot for operation with a single serving cell. + +CCEs for PDCCH candidates are non-overlapped if they correspond to + +- different CORESET indexes, or +- different first symbols for the reception of the respective PDCCH candidates. + +**Table 10.1-3: Maximum number of non-overlapped CCEs per slot for a DL BWP with SCS configuration for a single serving cell** + +| | Maximum number of non-overlapped CCEs per slot and per serving cell | +|---|---------------------------------------------------------------------| +| | | +| 0 | 56 | +| 1 | 56 | +| 2 | 48 | +| 3 | 32 | + +Table 10.1-3A provides the maximum number of non-overlapped CCEs, , for a DL BWP with SCS configuration that a UE is expected to monitor corresponding PDCCH candidates per span for operation with a single serving cell. + +**Table 10.1-3A: Maximum number of non-overlapped CCEs in a span for combination for a DL BWP with SCS configuration for a single serving cell** + +| | Maximum number of non-overlapped CCEs per span for combination and per serving cell | | | +|---|-------------------------------------------------------------------------------------|--------|--------| +| | (2, 2) | (4, 3) | (7, 3) | +| 0 | 18 | 36 | 56 | +| 1 | 18 | 36 | 56 | + +Table 10.1-3B provides the maximum number of non-overlapped CCEs, , for a DL BWP with SCS configuration that a UE is expected to monitor corresponding PDCCH candidates per group of slots for combination for operation with a single serving cell. + +**Table 10.1-3B: Maximum number of non-overlapped CCEs in a group of slots for any combination for a DL BWP with SCS configuration for a single serving cell** + +| | Maximum number of non-overlapped CCEs in a group of slots per combination and per serving cell | | | | +|---|------------------------------------------------------------------------------------------------|--------|--------|--------| +| | (4, 1) | (4, 2) | (8, 1) | (8, 4) | +| 5 | 32 | 32 | - | - | +| 6 | 16 | 16 | 32 | 32 | + +In the following, if a UE monitors PDCCH candidates on a scheduling cell for detection of DCI format 0\_3 or DCI format 1\_3 for scheduling on serving cells from a set of serving cells, the serving cell for counting the PDCCH candidates and a corresponding number of non-overlapping CCEs is + +- the scheduling cell, if the scheduling cell is included in the set of serving cells and the UE is provided search space sets for the PDCCH candidates only on the scheduling cell +- a serving cell from the set of serving cells, if search space sets with same *searchSpaceId* for one or both of DCI format 0\_3 and DCI format 1\_3, respectively, are provided on the serving cell and on the scheduling cell. + +For the following procedures in this clause, downlink cells are scheduled cells on which a UE is provided search space sets. + +If a UE + +- does not report *pdcch-BlindDetectionCA*, *pdcch-BlindDetectionCA1*, *pdcch-BlindDetectionCA2*, or *pdcch-BlindDetectionCA3*, or is not provided *BDFactorR*, +- reports *pdcch-BlindDetectionCA*, *pdcch-BlindDetectionCA1*, *pdcch-BlindDetectionCA2*, or *pdcch-BlindDetectionCA3*, the UE can be indicated by *BDFactorR* either or + +If a UE is configured with downlink cells for which the UE is not provided *monitoringCapabilityConfig*, or is provided *monitoringCapabilityConfig* = *r15monitoringcapability* and is not provided *CORESETPoolIndex*, with associated PDCCH candidates monitored in the active DL BWPs of the scheduling cells using SCS configuration where , the UE is not required to monitor, on the active DL BWPs of the scheduling cells, + +- more than PDCCH candidates or more than non-overlapped CCEs per slot for each scheduled cell when the scheduling cell is from the downlink cells, or +- more than PDCCH candidates or more than non-overlapped CCEs per slot for each scheduled cell when the scheduling cell is from the downlink cells +- more than PDCCH candidates or more than non-overlapped CCEs per slot for CORESETs with same *coresetPoolIndex* value for each scheduled cell when the scheduling cell is from the downlink cells + +is replaced by , if a UE is configured with downlink cells for which the UE is provided both *monitoringCapabilityConfig* = *r15monitoringcapability* and *monitoringCapabilityConfig* = *r16monitoringcapability*. is replaced by , if a UE is configured with downlink cells for which the UE is provided both *monitoringCapabilityConfig* = *r15monitoringcapability* and *monitoringCapabilityConfig* = *r17monitoringcapability*. is replaced by , if a UE is configured with downlink cells for which the UE is provided both *monitoringCapabilityConfig* = *r15monitoringcapability* and *monitoringCapabilityConfig* = *r16monitoringcapability* and *monitoringCapabilityConfig* = *r17monitoringcapability*. + +If a UE + +- is configured with downlink cells for which the UE is not provided *monitoringCapabilityConfig*, or is provided *monitoringCapabilityConfig* = *r15monitoringcapability* and is not provided *coresetPoolIndex*, +- with associated PDCCH candidates monitored in the active DL BWPs of the scheduling cell(s) using SCS configuration , where , and +- a DL BWP of an activated cell is the active DL BWP of the activated cell, and a DL BWP of a deactivated cell is the DL BWP with index provided by *firstActiveDownlinkBWP-Id* for the deactivated cell, + +the UE is not required to monitor more than PDCCH candidates or more than non-overlapped CCEs per slot on the active DL BWP(s) of scheduling cell(s) from the downlink cells. is replaced by if a UE is configured with downlink cells for which the UE is provided both *monitoringCapabilityConfig* = *r15monitoringcapability* and *monitoringCapabilityConfig* = *r16monitoringcapability*. is replaced by , if a UE is configured with downlink cells for which the UE is provided both *monitoringCapabilityConfig* = *r15monitoringcapability* and *monitoringCapabilityConfig* = *r17monitoringcapability*. is replaced by . If a UE is configured with downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r15monitoringcapability* and *monitoringCapabilityConfig* = *r16monitoringcapability* and *monitoringCapabilityConfig* = *r17monitoringcapability*. + +For each scheduled cell from the downlink cells, the UE is not required to monitor on the active DL BWP with SCS configuration of the scheduling cell more than PDCCH candidates or more than non-overlapped CCEs per slot. + +For each scheduled cell from the downlink cells, the UE is not required to monitor on the active DL BWP with SCS configuration of the scheduling cell + +- more than PDCCH candidates or more than non-overlapped CCEs per slot +- more than PDCCH candidates or more than non-overlapped CCEs per slot for CORESETs with same *coresetPoolIndex* value + +If a UE is configured with downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r16monitoringcapability* and with associated PDCCH candidates monitored in the active DL BWPs of the scheduling cells using SCS configuration, and with of the downlink cells using combination for PDCCH monitoring, where, the UE is not required to monitor, on the active DL BWP of the scheduling cell, more than PDCCH candidates or more than non-overlapped CCEs per span for each scheduled cell when the scheduling cell is from the downlink cells. If a UE is configured with downlink cells for which the UE is provided both *monitoringCapabilityConfig* = *r15monitoringcapability* and *monitoringCapabilityConfig* = *r16monitoringcapability*, is replaced by . If a UE is configured with downlink cells for which the UE is provided both *monitoringCapabilityConfig* = *r16monitoringcapability* and *monitoringCapabilityConfig* = *r17monitoringcapability*, is replaced by .If a UE is configured with downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r15monitoringcapability* and *monitoringCapabilityConfig* = *r16monitoringcapability* and *monitoringCapabilityConfig* = *r17monitoringcapability*, is replaced by . + +If a UE is configured only with downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r16monitoringcapability* and with associated PDCCH candidates monitored in the active DL BWPs of the scheduling cells using SCS configuration, and with of the downlink cells using combination for PDCCH monitoring, where, a DL BWP of an activated cell is the active DL BWP of the activated cell, and a DL BWP of a deactivated cell is the DL BWP with index provided by *firstActiveDownlinkBWP-Id* for the deactivated cell, the UE is not required to monitor more than PDCCH candidates or more than non-overlapped CCEs + +- per set of spans on the active DL BWP(s) of all scheduling cell(s) from the downlink cells within every symbols, if the union of PDCCH monitoring occasions on all scheduling cells from the downlink cells results to PDCCH monitoring according to the combination and any pair of spans in the set is within symbols, where first symbols start at a first symbol with a PDCCH monitoring occasion and next symbols start at a first symbol with a PDCCH monitoring occasion that is not included in the first symbols +- per set of spans across the active DL BWP(s) of all scheduling cells from the downlink cells, with at most one span per scheduling cell for each set of spans, otherwise + +where is a number of configured cells with associated PDCCH candidates monitored in the active DL BWPs of the scheduling cells using SCS configuration. If a UE is configured with downlink cells for which the UE is provided both *monitoringCapabilityConfig* = *r15monitoringcapability* and *monitoringCapabilityConfig* = *r16monitoringcapability*, is replaced by . If a UE is configured with downlink cells for which the UE is provided both *monitoringCapabilityConfig* = *r16monitoringcapability* and *monitoringCapabilityConfig* = *r17monitoringcapability*, is replaced by .If a UE is configured with downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r15monitoringcapability* and *monitoringCapabilityConfig* = *r16monitoringcapability* and *monitoringCapabilityConfig* = *r17monitoringcapability*, is replaced by . + +For each scheduled cell from the downlink cells using combination, the UE is not required to monitor on the active DL BWP with SCS configuration of the scheduling cell, more than PDCCH candidates or more than non-overlapped CCEs per span. + +A UE does not expect to be configured CSS sets, except for CSS sets provided by *searchSpaceMCCH*, *searchSpaceMTCH*, *searchSpaceMulticastMCCH*, *searchSpaceMulticastMTCH* or by *SearchSpace* in *pdcc-ConfigMulticast* for DCI formats with CRC scrambled by G-RNTI or G-CS-RNTI, that result to corresponding total, or per scheduled cell, numbers of monitored PDCCH candidates and non-overlapped CCEs per slot, per group of slots for a corresponding combination, or per span that exceed the corresponding maximum numbers per slot, or per group of slots for a corresponding combination, or per span, respectively. + +For same cell scheduling or for cross-carrier scheduling, a UE does not expect a number of PDCCH candidates, and a number of corresponding non-overlapped CCEs per slot, or per group of slots for a corresponding combination, or per span, on a secondary cell to be larger than the corresponding numbers that the UE is capable of monitoring on the secondary cell per slot, or per group of slots for a corresponding combination, or per span, respectively. If a UE is provided *monitoringCapabilityConfig* = *r16monitoringcapability* for the primary cell, except the first span of each slot, the UE does not expect a number of PDCCH candidates and a number of corresponding non-overlapped CCEs per span on the primary cell to be larger than the corresponding numbers that the UE is capable of monitoring on the primary cell per span. + +If a UE is configured with downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r17monitoringcapability* and with associated PDCCH candidates monitored in the active DL BWPs of the scheduling cells using SCS configuration, and with of the downlink cells using any combination for a group of slots for PDCCH monitoring, where, the UE is not required to monitor, on the active DL BWP of the scheduling cell, + +- more than PDCCH candidates or more than non-overlapped CCEs per group of slots for each scheduled cell when the scheduling cell is from the downlink cells, or +- more than PDCCH candidates or more than non-overlapped CCEs per group of slots for each scheduled cell when the scheduling cell is from the downlink cells, or +- more than PDCCH candidates or more than non-overlapped CCEs per group of slots for CORESETs with same *coresetPoolIndex* for each scheduled cell when the scheduling cell is from the downlink cells + +If the UE is configured with downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r15monitoringcapability* and downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r17monitoringcapability* for the active DL BWPs, is replaced by . If the UE is configured with downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r16monitoringcapability* and downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r17monitoringcapability* for the active DL BWPs, is replaced by . If the UE is configured with downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r15monitoringcapability* and downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r16monitoringcapability* and downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r17monitoringcapability* for the active DL BWPs, is replaced by . If, for one or more of the cells, the UE is provided with *monitoringCapabilityConfig* = *r16monitoringcapability*, . + +If a UE is configured downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r17monitoringcapability* and with associated PDCCH candidates monitored in the active DL BWPs of the scheduling cells using SCS configuration , and with of the downlink cells using any combination for a group of slots for PDCCH monitoring, where , a DL BWP of an activated cell is the active DL BWP of the activated cell, and a DL BWP of a deactivated cell is the DL BWP with index provided by *firstActiveDownlinkBWP-Id* for the deactivated cell, the UE is not required to monitor more than PDCCH candidates, or more than non-overlapped CCEs, per group of slots on the active DL BWP(s) of scheduling cell(s) from the downlink cells where is a number of configured cells with associated PDCCH candidates monitored in the active DL BWPs of the scheduling cells using SCS configuration . + +If the UE is configured with downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r15monitoringcapability* and downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r17monitoringcapability* for the active DL BWPs, is replaced by . If the UE is configured with downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r16monitoringcapability* and downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r17monitoringcapability* for the active DL BWPs, is replaced by . If the UE is configured with downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r15monitoringcapability* and downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r16monitoringcapability* and downlink cells for which the UE is provided *monitoringCapabilityConfig* = *r17monitoringcapability* for the active DL BWPs, is replaced by . If, for one or more of the cells, the UE is provided with *monitoringCapabilityConfig* = *r16monitoringcapability*, . + +For each scheduled cell from the downlink cells using any combination for a group of slots, the UE is not required to monitor on the active DL BWP with SCS configuration of the scheduling cell, more than PDCCH candidates or more than non-overlapped CCEs per group of slots. + +For each scheduled cell from the downlink cells using any combination for a group of slots, the UE is not required to monitor on the active DL BWP with SCS configuration of the scheduling cell, + +- more than PDCCH candidates or more than non-overlapped CCEs per group of slots +- more than PDCCH candidates or more than non-overlapped CCEs per group of slots for CORESETs with the same *coresetPoolIndex* value. + +For cross-carrier scheduling, the number of PDCCH candidates for monitoring and the number of non-overlapped CCEs per span or per slot or per group of slots are separately counted for each scheduled cell. + +The UE allocates PDCCH candidates for monitoring to USS sets for the primary cell having an active DL BWP with SCS configuration in a slot if the UE is not provided *monitoringCapabilityConfig* for the primary cell or if the UE is provided *monitoringCapabilityConfig* = *r15monitoringcapability* for the primary cell, or in the first span of each slot if the UE is provided *monitoringCapabilityConfig* = *r16monitoringcapability* for the primary cell, or in a group of slots for a corresponding combination if the UE is provided *monitoringCapabilityConfig* = *r17monitoringcapability* for the primary cell, according to the following pseudocode. + +If for the USS sets for scheduling on the primary cell the UE is not provided *coresetPoolIndex* for first CORESETs, or is provided *coresetPoolIndex* with value 0 for first CORESETs, and is provided *coresetPoolIndex* with value 1 for second CORESETs, and if or , the following pseudocode applies only to USS sets associated with the first CORESETs. A UE does not expect to monitor PDCCH in a USS set without allocated PDCCH candidates for monitoring. + +In the following pseudocode, if the UE is provided *monitoringCapabilityConfig = r16monitoringcapability* for the primary cell, and are replaced by and respectively, and and are replaced by and respectively. + +In the following pseudocode, if the UE is provided *monitoringCapabilityConfig = r17monitoringcapability* for the primary cell, and are replaced by and respectively, and and are replaced by and respectively. + +For all search space sets that a UE monitors PDCCH on the primary cell within a slot , or within a group of slots for a corresponding combination , or within a span in slot , denote by a set of CSS sets, except for CSS sets provided by *searchSpaceMCCH*, *searchSpaceMTCH*, *searchSpaceMulticastMCCH*, *searchSpaceMulticastMTCH* or by *SearchSpace* in *pdcch-ConfigMulticast* for DCI formats with CRC scrambled by G-RNTI or G-CS-RNTI, with cardinality of and by a set of USS sets and CSS sets provided by *searchSpaceMCCH*, *searchSpaceMTCH* or by *SearchSpace* in *pdcch-ConfigMulticast* for DCI formats with CRC scrambled by G-RNTI or G-CS-RNTI with cardinality of for scheduling on the primary cell. The location of search space sets , , in is according to an ascending order of the search space set index. + +Denote by , , the number of counted PDCCH candidates for monitoring for CSS set and by , , the number of counted PDCCH candidates for monitoring for search space set . If a UE indicates *numBD-twoPDCCH-r17* with value of 3 and is provided *searchSpaceLinkingId* with same value for search space sets and , with , set if and are CSS sets or set if and are USS sets. + +For the CSS sets in , a UE monitors PDCCH candidates requiring a total of non-overlapping CCEs in a slot, of in group of slots for a corresponding combination , or in a span. + +Denote by the set of non-overlapping CCEs for search space set and by ; the cardinality of where a UE determines the non-overlapping CCEs for search space set considering the allocated PDCCH candidates for monitoring for the CSS sets in and the allocated PDCCH candidates for monitoring for all search space sets , . + +Set + +Set + +Set + +while AND + +allocate PDCCH candidates for monitoring to search space set + +; + +; + +; + +end while + +If a UE + +- is configured for single cell operation or for operation with carrier aggregation in a same frequency band, and +- monitors PDCCH candidates in overlapping PDCCH monitoring occasions in multiple CORESETs that have been configured with same or different *qcl-Type* set to 'typeD' properties on active DL BWP(s) of one or more cells + +the UE monitors PDCCHs only in a CORESET, and in any other CORESET from the multiple CORESETs that have been configured with *qcl-Type* set to same 'typeD' properties as the CORESET, on the active DL BWP of a cell from the one or more cells + +- the CORESET corresponds to the CSS set with the lowest index in the cell with the lowest index containing CSS, if any; otherwise, to the USS set with the lowest index in the cell with lowest index + +- the lowest USS set index is determined over all USS sets with at least one PDCCH candidate in overlapping PDCCH monitoring occasions + +If a UE + +- is not provided *coresetPoolIndex* for first CORESETs, or is provided *coresetPoolIndex* with value 0 for first CORESETs, and +- is provided *coresetPoolIndex* with value 1 for second CORESETs, and +- is provided *twoQCLTypeDforMulti-DCI* + +the UE applies the procedures in the above paragraph independently across the first CORESETs and the second CORESETs. + +If a UE + +- is configured for single cell operation or for operation with carrier aggregation in a same frequency band, +- monitors PDCCH candidates in overlapping PDCCH monitoring occasions in multiple CORESETs that have been configured with same or different *qcl-Type* set to 'typeD' properties on active DL BWP(s) of one or more cells, and +- is provided *twoQCLTypeDforPDCCHRepetition* + +the UE monitors PDCCHs only in a first CORESET with *qcl-Type* set to first 'typeD' properties and, if any, in a second CORESET with *qcl-Type* set to second 'typeD' properties that are different than the first 'typeD' properties, and in any other CORESET from the multiple CORESETs with corresponding *qcl-Type* set to either the first 'typeD' properties or to the second 'typeD' properties + +- the first CORESET corresponds to the CSS set with the lowest index in the cell with the lowest index containing CSS sets, if any; otherwise, to the USS set with the lowest index in the cell with lowest index +- excluding CSS sets and USS sets associated with CORESETs with *qcl-Type* set to first 'typeD' properties, the second CORESET corresponds to the CSS set with the lowest index in the cell with the lowest index containing CSS sets, if any; otherwise, to the USS set with the lowest index in the cell with lowest index, where the CSS set or the USS set includes *searchSpaceLinkingId* with same value as any CSS set or any USS set associated with CORESETs with *qcl-Type* set to first 'typeD' properties +- the lowest USS set index is determined over all USS sets with at least one PDCCH candidate in overlapping PDCCH monitoring occasions + +If a UE + +- is configured for single cell operation or for operation with carrier aggregation in a same frequency band, +- monitors PDCCH candidates in overlapping PDCCH monitoring occasions in multiple CORESETs that have been configured with same or different *qcl-Type* set to 'typeD' properties on active DL BWP(s) of one or more cells, +- one or more CORESETs have two activated TCI states, and +- reports *sfn-QCL-TypeD-Collision-twoTCI* + +the UE monitors PDCCHs only in a CORESET with a first *qcl-Type* set to first 'typeD' properties and, if any, a second *qcl-Type* set to second 'typeD' properties that are different than the first 'typeD' properties, and in any other CORESET from the multiple CORESETs with corresponding *qcl-Type* set to the first 'typeD' properties and/or to the second 'typeD' properties + +- the CORESET corresponds to the CSS set with the lowest index in the cell with the lowest index containing CSS, if any; otherwise, to the USS set with the lowest index in the cell with lowest index +- the lowest USS set index is determined over all USS sets with at least one PDCCH candidate in overlapping PDCCH monitoring occasions + +For the purpose of determining the CORESET, a SS/PBCH block is considered to have different QCL 'typeD' properties than a CSI-RS. + +For the purpose of determining the CORESET, a first CSI-RS associated with a SS/PBCH block in a first cell and a second CSI-RS in a second cell that is also associated with the SS/PBCH block are assumed to have same QCL 'typeD' properties. + +The allocation of non-overlapping CCEs and of PDCCH candidates for PDCCH monitoring is according to all search space sets associated with the multiple CORESETs on the active DL BWP(s) of the one or more cells. + +The number of active TCI states is determined from the multiple CORESETs. + +If a UE + +- is configured for single cell operation or for operation with carrier aggregation in a same frequency band, and +- monitors PDCCH candidates in overlapping PDCCH monitoring occasions in multiple CORESETs where none of the CORESETs has TCI-states configured with *qcl-Type* set to 'typeD', + +the UE is required to monitor PDCCH candidates in overlapping PDCCH monitoring occasions for search space sets associated with different CORESETs. + +For a scheduled cell and at any time, if a UE is provided a C-RNTI, the UE expects to have received at most 16 PDCCHs for DCI formats with CRC scrambled by C-RNTI, CS-RNTI, MCS-C-RNTI, G-RNTI for multicast, or G-CS-RNTI scheduling 16 PDSCH receptions for which the UE has not received any corresponding PDSCH symbol and at most 16 PDCCHs for DCI formats with CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI scheduling 16 PUSCH transmissions for which the UE has not transmitted any corresponding PUSCH symbol. + +If a UE is not provided *monitoringCapabilityConfig = r16monitoringcapability* for any serving cell, and + +- is not configured for NR-DC operation and indicates through *pdch-BlindDetectionCA* a capability to monitor PDCCH candidates for downlink cells and the UE is configured with downlink cells or uplink cells, or +- is configured with NR-DC operation and for a cell group with downlink cells or uplink cells + +the UE expects to have respectively received at most PDCCHs for + +- DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI, or a G-RNTI for multicast, or a G-CS-RNTI scheduling PDSCH receptions for which the UE has not received any corresponding PDSCH symbol over all downlink cells +- DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI scheduling PUSCH transmissions for which the UE has not transmitted any corresponding PUSCH symbol over all uplink cells + +If a UE is provided *monitoringCapabilityConfig = r16monitoringcapability* for all serving cells, and + +- is not configured for NR-DC operation and indicates through *pdch-MonitoringCA* a capability to monitor PDCCH candidates for downlink cells and the UE is configured with downlink cells or uplink cells, or +- is configured with NR-DC operation and for a cell group with downlink cells or uplink cells + +the UE expects to have respectively received at most PDCCHs for + +- DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI, or a G-RNTI for multicast, or a G-CS-RNTI scheduling PDSCH receptions for which the UE has not received any corresponding PDSCH symbol over all downlink cells +- DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI scheduling PUSCH transmissions for which the UE has not transmitted any corresponding PUSCH symbol over all uplink cells. + +If a UE is provided *monitoringCapabilityConfig = r16monitoringcapability* for at least one serving cell and is not provided *monitoringCapabilityConfig = r16monitoringcapability* for at least one serving cell, and + +- is not configured for NR-DC operation, and indicates a capability to monitor PDCCH candidates for downlink cells and downlink cells, and the UE is configured with downlink cells or uplink cells, or + +- is configured with NR-DC operation and for a cell group with downlink cells or uplink cells + +the UE expects to have respectively received + +- at most PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI, or a G-RNTI for multicast, or a G-CS-RNTI scheduling PDSCH receptions for which the UE has not received any corresponding PDSCH symbol over all serving cells that are not provided *monitoringCapabilityConfig = r16monitoringcapability* +- at most PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI scheduling PUSCH transmissions for which the UE has not transmitted any corresponding PUSCH symbol over all serving cells that are not provided *monitoringCapabilityConfig = r16monitoringcapability* +- at most PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI, or a G-RNTI for multicast, or a G-CS-RNTI scheduling PDSCH receptions for which the UE has not received any corresponding PDSCH symbol over all serving cells that are provided *monitoringCapabilityConfig = r16monitoringcapability* +- at most PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI scheduling PUSCH transmissions for which the UE has not transmitted any corresponding PUSCH symbol over all serving cells that are provided *monitoringCapabilityConfig = r16monitoringcapability* + +If a UE is provided serving cells with SCS configuration for the active DL BWP, is not configured for NR-DC operation and indicates through *pdcch-MonitoringCA* a capability to monitor PDCCH candidates for downlink cells and the UE is configured with downlink cells or uplink cells, the UE expects to have respectively received at most PDCCHs for + +- DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI, or a G-RNTI for multicast, or a G-CS-RNTI scheduling PDSCH receptions for which the UE has not received any corresponding PDSCH symbol over all downlink cells +- DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI scheduling PUSCH transmissions for which the UE has not transmitted any corresponding PUSCH symbol over all uplink cells. + +If a UE is provided *monitoringCapabilityConfig = r17monitoringcapability* for at least one serving cell, is provided *monitoringCapabilityConfig = r15monitoringcapability* for at least one serving cell, is not provided *monitoringCapabilityConfig = r16monitoringcapability* for any serving cell, is not configured for NR-DC operation, indicates a capability to monitor PDCCH candidates for downlink cells and downlink cells, and UE is configured with downlink cell or uplink cells, the UE expects to have respectively received + +- at most PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI, or a G-RNTI for multicast, or a G-CS-RNTI scheduling PDSCH receptions for which the UE has not received any corresponding PDSCH symbol over all serving cells that are provided *monitoringCapabilityConfig = r15monitoringcapability* +- at most PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI scheduling PUSCH transmissions for which the UE has not transmitted any corresponding PUSCH symbol over all serving cells that are provided *monitoringCapabilityConfig = r15monitoringcapability* +- at most PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI, or a G-RNTI for multicast, or a G-CS-RNTI scheduling PDSCH receptions for which the UE has not received any corresponding PDSCH symbol over all serving cells with *monitoringCapabilityConfig = r17monitoringcapability* +- at most PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI scheduling PUSCH transmissions for which the UE has not transmitted any corresponding PUSCH symbol over all serving cells with *monitoringCapabilityConfig = r17monitoringcapability* + +If a UE is provided *monitoringCapabilityConfig = r17monitoringcapability* for at least one serving cell, is provided *monitoringCapabilityConfig = r16monitoringcapability* for at least one serving cell, is not provided *monitoringCapabilityConfig = r15monitoringcapability* for any serving cell, is not configured for NR-DC operation, indicates a capability to monitor PDCCH candidates for downlink cells and downlink cells, and the UE is configured with downlink cells or uplink cells + +the UE expects to have respectively received + +- at most PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI, or a G-RNTI for multicast, or a G-CS-RNTI scheduling PDSCH receptions for which the UE has not received any corresponding PDSCH symbol over all serving cells that are provided *monitoringCapabilityConfig = r16monitoringcapability* +- at most PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI scheduling PUSCH transmissions for which the UE has not transmitted any corresponding PUSCH symbol over all serving cells that are provided *monitoringCapabilityConfig = r16monitoringcapability* +- at most PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI, or a G-RNTI for multicast, or a G-CS-RNTI scheduling PDSCH receptions for which the UE has not received any corresponding PDSCH symbol over all serving cells with *monitoringCapabilityConfig = r17monitoringcapability* +- at most PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI scheduling PUSCH transmissions for which the UE has not transmitted any corresponding PUSCH symbol over all serving cells with *monitoringCapabilityConfig = r17monitoringcapability* + +If a UE is provided *monitoringCapabilityConfig = r17monitoringcapability* for at least one serving cell, is provided *monitoringCapabilityConfig = r16monitoringcapability* for at least one serving cell, and *monitoringCapabilityConfig = r15monitoringcapability* for at least one serving cell, is not configured for NR-DC operation, indicates a capability to monitor PDCCH candidates for downlink cells, , and downlink cells, and is configured with downlink cells or uplink cells + +the UE expects to have respectively received + +- at most PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI, or a G-RNTI for multicast, or a G-CS-RNTI scheduling PDSCH receptions for which the UE has not received any corresponding PDSCH symbol over all serving cells that are provided *monitoringCapabilityConfig = r15monitoringcapability* +- at most PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI scheduling PUSCH transmissions for which the UE has not transmitted any corresponding PUSCH symbol over all serving cells that are provided *monitoringCapabilityConfig = r15monitoringcapability* +- at most PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI, or a G-RNTI for multicast, or a G-CS-RNTI scheduling PDSCH receptions for which the UE has not received any corresponding PDSCH symbol over all serving cells that are provided *monitoringCapabilityConfig = r16monitoringcapability* +- at most PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI scheduling PUSCH transmissions for which the UE has not transmitted any corresponding PUSCH symbol over all serving cells that are provided *monitoringCapabilityConfig = r16monitoringcapability* +- at most PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI, or a G-RNTI for multicast, or a G-CS-RNTI scheduling PDSCH receptions for which the UE has not received any corresponding PDSCH symbol over all serving cells with *monitoringCapabilityConfig = r17monitoringcapability* +- at most PDCCHs for DCI formats with CRC scrambled by a C-RNTI, or a CS-RNTI, or a MCS-C-RNTI scheduling PUSCH transmissions for which the UE has not transmitted any corresponding PUSCH symbol over all serving cells with *monitoringCapabilityConfig = r17monitoringcapability* + +If a UE + +- is configured to monitor a first PDCCH candidate for a DCI format 0\_0 and a DCI format 1\_0 from a CSS set and a second PDCCH candidate for a DCI format 0\_0 and a DCI format 1\_0 from a USS set, where the CSS set and the USS set do not include *searchSpaceLinkingId*, in a CORESET with index zero on an active DL BWP, and +- the DCI formats 0\_0/1\_0 associated with the first PDCCH candidate and the DCI formats 0\_0/1\_0 associated with the second PDCCH candidate have same size, and +- the UE receives the first PDCCH candidate and the second PDCCH candidate over a same set of CCEs, and + +- the first PDCCH candidate and the second PDCCH candidate have identical scrambling, and +- the DCI formats 0\_0/1\_0 for the first PDCCH candidate and the DCI formats 0\_0/1\_0 for the second PDCCH candidate have CRC scrambled by either C-RNTI, or MCS-C-RNTI, or CS-RNTI + +the UE decodes only the DCI formats 0\_0/1\_0 associated with the first PDCCH candidate. + +If a UE detects a DCI format with inconsistent information, the UE discards all the information in the DCI format. + +A UE configured with a bandwidth part indicator in a DCI format determines, in case of an active DL BWP or of an active UL BWP change, that the information in the DCI format is applicable to the new active DL BWP or UL BWP, respectively, as described in clause 12. + +For unpaired spectrum operation, if a UE is not configured for PUSCH/PUCCH transmission on serving cell , the UE does not expect to monitor PDCCH on serving cell if the PDCCH overlaps in time with SRS transmission (including any interruption due to uplink or downlink RF retuning time [10, TS 38.133]) on serving cell and if the UE is not capable of simultaneous reception and transmission on serving cell and serving cell . + +If a UE is provided *resourceBlocks* and *symbolsInResourceBlock* in *RateMatchPattern*, or if the UE is additionally provided *periodicityAndPattern* in *RateMatchPattern*, the UE can determine a set of RBs in symbols of a slot that are not available for PDSCH reception scheduled by a DCI format as described in [6, TS 38.214]. If a PDCCH candidate that provides a DCI format is mapped to one or more REs that overlap with REs of any RB in the set of RBs in symbols of the slot, the UE does not expect to monitor the PDCCH candidate. + +A UE does not expect to be configured with *dci-FormatsSL* and *dci-FormatsExt* in a same USS. + +### 10.1.1 Self-carrier and cross-carrier scheduling on the primary cell + +A UE can be configured for scheduling on the primary cell from the primary cell and from a secondary cell [12, TS 38.331]. The UE is either not provided *monitoringCapabilityConfig* for the primary cell or for the secondary cell, or the UE is provided only *monitoringCapabilityConfig* = *r15monitoringcapability* for the primary cell and for the secondary cell. The UE is not provided *coresetPoolIndex* on the primary cell or on the secondary cell. + +The SCS configuration for the active DL BWP on the primary cell is smaller than or equal to the SCS configuration for the active DL BWP on the secondary cell. + +If a UE indicates capability *disablingScalingFactorDeactSCell* [18, TS 38.306] and the secondary cell is deactivated, or if the UE indicates capability *disablingScalingFactorDormantSCell* [18, TS 38.306] and the active DL BWP of the secondary cell is a dormant DL BWP for the UE, applies for the procedures described in the remaining of this clause. If , the UE determines and , and determines and , by including the primary cell only in the downlink cells in , as described in clause 10.1. If , the UE determines and by including the primary cell once in the downlink cells in , as described in clause 10.1. + +For scheduling on the primary cell from the primary cell, the UE is not required to monitor more than PDCCH candidates per slot or more than non-overlapping CCEs per slot on the active DL BWP of the primary cell, where is provided by *ccs-BlindDetectionSplit*. + +For scheduling on the primary cell from the secondary cell, the UE is not required to monitor on the active DL BWP of the secondary cell more than + +- PDCCH candidates per slot or more than non-overlapping CCEs per slot of the active DL BWP of the secondary cell +- PDCCH candidates per slot or more than non-overlapping CCEs per slot of the active DL BWP of the primary cell + +If , the UE does not count PDCCH candidates and non-overlapping CCEs that the UE monitors for scheduling on the primary cell from the secondary cell towards and , respectively. + +If , the UE counts PDCCH candidates and non-overlapping CCEs that the UE monitors for scheduling on the primary cell from the secondary cell towards and , respectively. + +For allocation of PDCCH candidates and non-overlapping CCEs to search space sets for scheduling on the primary cell from the primary cell, the UE applies the procedure in clause 10.1 using $\text{cs-RNTI}$ instead of $\text{g-cs-RNTI}$ , and using $\text{g-cs-RNTI}$ instead of $\text{cs-RNTI}$ for the primary cell. + +## 10.2 PDCCH validation for DL SPS and UL grant Type 2 + +A UE validates, for scheduling activation or scheduling release, a DL SPS assignment PDCCH or a configured UL grant Type 2 PDCCH if + +- the CRC of a corresponding DCI format is scrambled with a CS-RNTI provided by $\text{cs-RNTI}$ or a G-CS-RNTI provided by $\text{g-cs-RNTI}$ , and +- the new data indicator field in the DCI format for the enabled transport block is set to '0', and +- the DFI flag field, if present, in the DCI format is set to '0', and +- the time domain resource assignment field in the DCI format indicates a row with single SLIV, and +- if validation is for scheduling activation and if the PDSCH-to-HARQ\_feedback timing indicator field in the DCI format is present, the PDSCH-to-HARQ\_feedback timing indicator field does not provide an inapplicable value from $\text{dl-DataToUL-ACK-r16}$ or $\text{dl-DataToUL-ACK-r17}$ . + +If a UE is provided a single configuration for UL grant Type 2 PUSCH or for SPS PDSCH, validation of the DCI format is achieved if all fields for the DCI format are set according to Table 10.2-1 or Table 10.2-2. + +If a UE is provided more than one configuration for UL grant Type 2 PUSCH or for SPS PDSCH, a value of the HARQ process number field in a DCI format indicates an activation for a corresponding UL grant Type 2 PUSCH or for a SPS PDSCH configuration with a same value as provided by $\text{ConfiguredGrantConfigIndex}$ or by $\text{sps-ConfigIndex}$ , respectively. Validation of the DCI format is achieved if the RV field for the DCI format is set as in Table 10.2-3. + +If a UE is provided more than one configuration for UL grant Type 2 PUSCH or for SPS PDSCH + +- if the UE is provided $\text{ConfiguredGrantConfigType2DeactivationStateList}$ or $\text{sps-ConfigDeactivationStateList}$ , a value of the HARQ process number field in a DCI format indicates a corresponding entry for scheduling release of one or more UL grant Type 2 PUSCH or SPS PDSCH configurations +- if the UE is not provided $\text{ConfiguredGrantConfigType2DeactivationStateList}$ or $\text{sps-ConfigDeactivationStateList}$ , a value of the HARQ process number field in a DCI format indicates a release for a corresponding UL grant Type 2 PUSCH or for a SPS PDSCH configuration with a same value as provided by $\text{ConfiguredGrantConfigIndex}$ or by $\text{sps-ConfigIndex}$ , respectively + +The UE does not expect to receive a multicast DCI format that releases either a unicast SPS PDSCH configuration or more than one SPS PDSCH configurations. + +Validation of the DCI format is achieved if all fields for the DCI format are set according to Table 10.2-4. + +If validation is achieved, the UE considers the information in the DCI format as a valid activation or valid release of DL SPS or configured UL grant Type 2. If validation is not achieved, the UE discards all the information in the DCI format. + +**Table 10.2-1: Special fields for single DL SPS or single UL grant Type 2 scheduling activation PDCCH validation when a UE is provided a single SPS PDSCH or UL grant Type 2 configuration in the active DL/UL BWP of the scheduled cell** + +| | DCI format 0_0/0_2 | DCI format 0_1 | DCI format 1_0/1_2/4_1 | DCI format 1_1/4_2 | +|----------------------------------|--------------------|--------------------------------------------------|------------------------|--------------------------------------------------| +| HARQ process number (if present) | set to all '0's | set to all '0's | set to all '0's | set to all '0's | +| Redundancy version (if present) | set to all '0's | For the enabled transport block: set to all '0's | set to all '0's | For the enabled transport block: set to all '0's | + +**Table 10.2-2: Special fields for single DL SPS or single UL grant Type 2 scheduling release PDCCH validation when a UE is provided a single SPS PDSCH or UL grant Type 2 configuration in the active DL/UL BWP of the scheduled cell** + +| | DCI format 0_0/0_1/0_2 | DCI format 1_0/1_1/1_2/4_1/4_2 | +|--------------------------------------|------------------------------------------------------------------------|------------------------------------------------------------------------------------------------| +| HARQ process number (if present) | set to all '0's | set to all '0's | +| Redundancy version (if present) | set to all '0's | set to all '0's | +| Modulation and coding scheme | set to all '1's | set to all '1's | +| Frequency domain resource assignment | set to all '0's for FDRA Type 2 with

set to all '1's, otherwise | set to all '0's for FDRA Type 0 or for dynamicSwitch
set to all '1's for FDRA Type 1 | + +**Table 10.2-3: Special fields for a single DL SPS or single UL grant Type 2 scheduling activation PDCCH validation when a UE is provided multiple DL SPS or UL grant Type 2 configurations in the active DL/UL BWP of the scheduled cell** + +| | DCI format 0_0/0_2 | DCI format 0_1 | DCI format 1_0/1_2/4_1 | DCI format 1_1/4_2 | +|---------------------------------|--------------------|--------------------------------------------------|------------------------|--------------------------------------------------| +| Redundancy version (if present) | set to all '0's | For the enabled transport block: set to all '0's | set to all '0's | For the enabled transport block: set to all '0's | + +**Table 10.2-4: Special fields for a single or multiple DL SPS and UL grant Type 2 scheduling release PDCCH validation when a UE is provided multiple DL SPS or UL grant Type 2 configurations in the active DL/UL BWP of the scheduled cell** + +| | DCI format 0_0/0_1/0_2 | DCI format 1_0/1_1/1_2/4_1/4_2 | +|--------------------------------------|------------------------------------------------------------------------|------------------------------------------------------------------------------------------------| +| Redundancy version (if present) | set to all '0's | set to all '0's | +| Modulation and coding scheme | set to all '1's | set to all '1's | +| Frequency domain resource assignment | set to all '0's for FDRA Type 2 with

set to all '1's, otherwise | set to all '0's for FDRA Type 0 or for dynamicSwitch
set to all '1's for FDRA Type 1 | + +A UE is expected to provide HARQ-ACK information in response to a SPS PDSCH release after symbols from the last symbol of a PDCCH providing the SPS PDSCH release. If *processingType2Enabled* of *PDSCH-ServingCellConfig* is set to *enable* for the serving cell with the PDCCH providing the SPS PDSCH release, for $\mu = 0$ , for $\mu = 1$ , and for $\mu = 2$ , otherwise, for $\mu = 0$ , for $\mu = 1$ , for $\mu = 2$ , for $\mu = 3$ , for $\mu = 4$ , and for $\mu = 5$ , wherein $\mu$ corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH providing the SPS PDSCH release and the SCS configuration of a PUCCH carrying the HARQ-ACK information in response to a SPS PDSCH release. + +## 10.2A PDCCH validation for SL configured grant Type 2 + +A UE validates, for scheduling activation or scheduling release, a SL configured grant Type 2 PDCCH if + +- the CRC of a corresponding DCI format 3\_0 is scrambled with a SL-CS-RNTI provided by *sl-CS-RNTI*, and +- the new data indicator field in the DCI format 3\_0 for the enabled transport block is set to '0' + +Validation of the DCI format 3\_0 is achieved if all fields for the DCI format 3\_0 are set according to Table 10.2A-1 or Table 10.2A-2. + +If validation is achieved, the UE considers the information in the DCI format 3\_0 as a valid activation or valid release of SL configured grant Type 2. If validation is not achieved, the UE discards all the information in the DCI format 3\_0. + +**Table 10.2A-1: Special fields for SL configured grant Type 2 scheduling activation PDCCH validation** + +| | DCI format 3_0 | +|---------------------|-----------------| +| HARQ process number | set to all '0's | + +**Table 10.2A-2: Special fields for SL configured grant Type 2 scheduling release PDCCH validation** + +| | DCI format 3_0 | +|-----------------------------------------------|-----------------| +| HARQ process number | set to all '1's | +| Frequency resource assignment
(if present) | set to all '1's | + +A UE validates, for SL PRS activation or release, a SL configured grant Type 2 PDCCH if + +- the CRC of a corresponding DCI format 3\_2 is scrambled with a SL-PRS-CS-RNTI provided by *sl-PRS-CS-RNTI*, and +- the activation/release indication field in the DCI format 3\_2 is set to '1' for activation and to '0' for release. + +## 10.3 PDCCH monitoring indication and dormancy/non-dormancy behaviour for SCells + +A UE configured with DRX mode operation [11, TS 38.321] can be provided the following for detection of a DCI format 2\_6 in a PDCCH reception on the PCell or on the SpCell [12, TS 38.331] + +- a PS-RNTI for DCI format 2\_6 by *ps-RNTI* +- a number of search space sets, by *dci-Format2-6*, to monitor PDCCH for detection of DCI format 2\_6 on the active DL BWP of the PCell or of the SpCell according to a common search space as described in clause 10.1 +- a payload size for DCI format 2\_6 by *sizeDCI-2-6* +- a location in DCI format 2\_6 of a Wake-up indication bit by *ps-PositionDCI-2-6* + - a '0' value for the Wake-up indication bit, when reported to higher layers, indicates to not start the *drx-onDurationTimer* for the next long DRX cycle [11, TS 38.321] + - a '1' value for the Wake-up indication bit, when reported to higher layers, indicates to start the *drx-onDurationTimer* for the next long DRX cycle [11, TS 38.321] +- a bitmap, when the UE is provided a number of groups of configured SCells by *dormancyGroupOutsideActiveTime*, where + - the bitmap location is immediately after the Wake-up indication bit location + - the bitmap size is equal to the number of groups of configured SCells where each bit of the bitmap corresponds to a group of configured SCells from the number of groups of configured SCells + - a '0' value for a bit of the bitmap indicates an active DL BWP, provided by *dormantBWP-Id*, for the UE [11, TS 38.321] for each activated SCell in the corresponding group of configured SCells + - a '1' value for a bit of the bitmap indicates + - an active DL BWP, provided by *firstOutsideActiveTimeBWP-Id*, for the UE for each activated SCell in the corresponding group of configured SCells, if a current active DL BWP is the dormant DL BWP + - a current active DL BWP, for the UE for each activated SCell in the corresponding group of configured SCells, if the current active DL BWP is not the dormant DL BWP + - the UE sets the active DL BWP to the indicated active DL BWP + +- an offset by *ps-Offset* indicating a time, where the UE starts monitoring PDCCH for detection of DCI format 2\_6 according to the number of search space sets, prior to a slot where the *drx-onDurationTimer* would start on the PCell or on the SpCell [11, TS 38.321] +- for each search space set, the PDCCH monitoring occasions are the ones in the first slots indicated by *duration*, or slot if *duration* is not provided, starting from the first slot of the first slots and ending prior to the start of *drx-onDurationTimer*. + +On PDCCH monitoring occasions associated with a same long DRX Cycle, a UE does not expect to detect more than one DCI format 2\_6 with different values of the Wake-up indication bit for the UE or with different values of the bitmap for the UE. + +The UE does not monitor PDCCH for detecting DCI format 2\_6 during Active Time [11, TS 38.321]. + +If a UE reports for an active DL BWP a *MinTimeGap* or *MinTimeGapFR2-2* value that is X slots prior to the beginning of a slot where the UE would start the *drx-onDurationTimer*, the UE is not required to monitor PDCCH for detection of DCI format 2\_6 during the X slots, where X corresponds to the *MinTimeGap* or *MinTimeGapFR2-2* value of the SCS of the active DL BWP in Table 10.3-1. + +**Table 10.3-1 Minimum time gap value X** + +| SCS
(kHz) | Minimum Time Gap X (slots) | | +|--------------|----------------------------|---------| +| | Value 1 | Value 2 | +| 15 | 1 | 3 | +| 30 | 1 | 6 | +| 60 | 1 | 12 | +| 120 | 2 | 24 | +| 480 | 8 | 96 | +| 960 | 16 | 192 | + +If a UE is provided search space sets to monitor PDCCH for detection of DCI format 2\_6 in the active DL BWP of the PCell or of the SpCell and the UE detects DCI format 2\_6, the physical layer of a UE reports the value of the Wake-up indication bit for the UE to higher layers [11, TS 38.321] for the next long DRX cycle. + +If a UE is provided search space sets to monitor PDCCH for detection of DCI format 2\_6 in the active DL BWP of the PCell or of the SpCell and the UE does not detect DCI format 2\_6, the physical layer of the UE does not report a value of the Wake-up indication bit to higher layers for the next long DRX cycle. + +If a UE is provided search space sets to monitor PDCCH for detection of DCI format 2\_6 in the active DL BWP of the PCell or of the SpCell and the UE + +- is not required to monitor PDCCH for detection of DCI format 2\_6, as described in clauses 10, 11.1, 12, and in clause 5.7 of [11, TS 38.321] for all corresponding PDCCH monitoring occasions outside Active Time prior to a next long DRX cycle, or +- does not have any PDCCH monitoring occasions for detection of DCI format 2\_6 outside Active Time of a next long DRX cycle + +the physical layer of the UE reports a value of 1 for the Wake-up indication bit to higher layers for the next long DRX cycle. + +If a UE is provided search space sets to monitor PDCCH for detection of DCI format 0\_1/0\_3/1\_1/1\_3 and if any of DCI format 0\_1/0\_3/1\_1/1\_3 includes a SCell dormancy indication field, + +- the SCell dormancy indication field is a bitmap with size equal to a number of groups of configured SCells, provided by *dormancyGroupWithinActiveTime*, +- each bit of the bitmap corresponds to a group of configured SCells from the number of groups of configured SCells +- if the UE detects a DCI format 0\_1/1\_1 that does not include a carrier indicator field, or a DCI format 0\_1/1\_1 that includes a carrier indicator field with value equal to 0, and if the DCI format 0\_1 does not indicate UL grant Type 2 release nor deactivate semi-persistent CSI report(s) on PUSCH, or if the DCI format 1\_1 does not indicate SPS PDSCH release , or if the UE detects a DCI format 0\_3/1\_3 + +- a '0' value for a bit of the bitmap indicates an active DL BWP, provided by *dormantBWP-Id*, for the UE for each activated SCell in the corresponding group of configured SCells +- a '1' value for a bit of the bitmap indicates + - an active DL BWP, provided by *firstWithinActiveTimeBWP-Id*, for the UE for each activated SCell in the corresponding group of configured SCells, if a current active DL BWP is the dormant DL BWP + - a current active DL BWP, for the UE for each activated SCell in the corresponding group of configured SCells, if the current active DL BWP is not the dormant DL BWP +- the UE sets the active DL BWP to the indicated active DL BWP + +If a UE is provided search space sets to monitor PDCCH for detection of DCI format 1\_1, or of DCI format 1\_3, and if + +- the CRC of DCI format 1\_1 or of DCI format 1\_3 is scrambled by a C-RNTI or an MCS-C-RNTI, and if +- a one-shot HARQ-ACK request field is not present or has a '0' value, and if +- for DCI format 1\_3, a HARQ-ACK retransmission indicator field is not present or has a '0' value, and if +- the UE detects a DCI format 1\_1 on the primary cell that does not include a carrier indicator field, or detects a DCI format 1\_1 on the primary cell that includes a carrier indicator field with value equal to 0, or detects a DCI format 1\_3 on the primary cell, + +and if + +- *resourceAllocation* = *resourceAllocationType0* and all bits of the frequency domain resource assignment field in DCI format 1\_1, or for one or more blocks of the frequency domain resource assignment field in DCI format 1\_3, are equal to 0, or +- *resourceAllocation* = *resourceAllocationType1* and all bits of the frequency domain resource assignment field in DCI format 1\_1, or for one or more blocks of the frequency domain resource assignment field in DCI format 1\_3, are equal to 1, or +- *resourceAllocation* = *dynamicSwitch* and all bits of the frequency domain resource assignment field in DCI format 1\_1, or for one or more blocks of the frequency domain resource assignment field in DCI format 1\_3, are equal to 0 or 1 + +the UE considers the DCI format 1\_1 or the DCI format 1\_3 as indicating SCell dormancy, not scheduling a PDSCH reception on a serving cell, where for DCI format 1\_3 the serving cell is the one with the smallest index that is associated with a block from the one or more blocks of the frequency domain resource assignment field, and for transport block 1 interprets the sequence of fields of + +- modulation and coding scheme +- new data indicator +- redundancy version + +and of + +- HARQ process number +- antenna port(s) for DCI format 1\_1, or for DCI format 1\_3 if *AntennaPortsDCI1-3* is configured as 'type2' +- DMRS sequence initialization for DCI format 1\_1 + +as providing a bitmap to each configured SCell, in an ascending order of the SCell index, where + +- a '0' value for a bit of the bitmap indicates an active DL BWP, provided by *dormantBWP-Id*, for the UE for a corresponding activated SCell +- a '1' value for a bit of the bitmap indicates + - an active DL BWP, provided by *firstWithinActiveTimeBWP-Id*, for the UE for a corresponding activated SCell, if a current active DL BWP is the dormant DL BWP + +- a current active DL BWP, for the UE for a corresponding activated SCell, if the current active DL BWP is not the dormant DL BWP +- the UE sets the active DL BWP to the indicated active DL BWP + +If an active DL BWP provided by *dormantBWP-Id* for a UE on an activated SCell is not a default DL BWP for the UE on the activated SCell, as described in clause 12, the BWP inactivity timer is not used for transitioning from the active DL BWP provided by *dormantBWP-Id* to the default DL BWP on the activated SCell. + +A UE is expected to provide HARQ-ACK information in response to a detection of a DCI format 1\_1/1\_3 indicating SCell dormancy after symbols from the last symbol of a PDCCH providing the DCI format 1\_1/1\_3. If *processingType2Enabled* of *PDSCH-ServingCellConfig* is set to *enable* for the serving cell with the PDCCH providing the DCI format 1\_1/1\_3, for , for , and for ; otherwise, for , for , for , for , for , and for , where is the smallest SCS configuration between the SCS configuration of the PDCCH providing the DCI format 1\_1/1\_3 and the SCS configuration of a PUCCH with the HARQ-ACK information in response to the detection of the DCI format 1\_1/1\_3. + +## 10.4 Search space set group switching and skipping of PDCCH monitoring + +A UE can be provided + +- a group index for a respective Type3-PDCCH CSS set or USS set by *searchSpaceGroupIdList* for PDCCH monitoring on a serving cell, +- a group index for a respective Type3-PDCCH CSS set or USS set by *searchSpaceGroupIdList-r17* for PDCCH monitoring on an active DL BWP of a serving cell. + +If the UE is not provided *searchSpaceGroupIdList* or *searchSpaceGroupIdList-r17* for a search space set, the following procedures that are based on search space set group switching are not applicable for PDCCH monitoring according to the search space set. + +A UE can be provided a set of durations by *pdcch-SkippingDurationList* for Type3-PDCCH CSS set or USS set for PDCCH monitoring on an active DL BWP of a serving cell. If the UE is not provided *pdcch-SkippingDurationList*, the following procedures related to skipping of PDCCH monitoring are not applicable. + +If a UE is provided *cellGroupsForSwitchList*, indicating one or more groups of serving cells, the following procedures apply to all serving cells within each group; otherwise, the following procedures apply only to a serving cell for which the UE is provided *searchSpaceGroupIdList*. + +When a UE is provided *searchSpaceGroupIdList* or *searchSpaceGroupIdList-r17*, the UE resets PDCCH monitoring according to search space sets with group index 0, if provided by *searchSpaceGroupIdList* or *searchSpaceGroupIdList-r17*. + +A UE can be provided by *searchSpaceSwitchDelay* or *searchSpaceSwitchDelay-r17* a number of symbols where a minimum value of is provided in Table 10.4-1 for UE processing capability 1 and UE processing capability 2 and SCS configuration . UE processing capability 1 for SCS configuration applies unless the UE indicates support for UE processing capability 2. + +**Table 10.4-1: Minimum value of [symbols]** + +| | Minimum value for
UE processing capability 1 [symbols] | Minimum value for
UE processing capability 2 [symbols] | +|---|-----------------------------------------------------------|-----------------------------------------------------------| +| 0 | 25 | 10 | +| 1 | 25 | 12 | +| 2 | 25 | 22 | +| 3 | 40 | - | +| 5 | 160 | - | +| 6 | 320 | - | + +A UE can be provided, by *searchSpaceSwitchTimer*, a timer value for a serving cell that the UE is provided *searchSpaceGroupIdList* or, if provided, for a set of serving cells provided by *cellGroupsForSwitchList*. The UE decrements the timer value by one after each slot based on a reference SCS configuration that is the smallest SCS + +configuration among all configured DL BWPs in the serving cell, or in the set of serving cells. The UE maintains the reference SCS configuration during the timer decrement procedure. + +If a UE is provided by *SearchSpaceSwitchTrigger* a location of a search space set group switching flag field in a DCI format 2\_0, as described in clause 11.1.1, for a serving cell where the UE has active DL BWP with SCS configuration + +- if the UE detects a DCI format 2\_0 and a value of the search space set group switching flag field in the DCI format 2\_0 is 0, the UE starts monitoring PDCCH according to search space sets with group index 0, and stops monitoring PDCCH according to search space sets with group index 1, for the serving cell + - at the beginning of the first slot that is at least symbols after the last symbol of the PDCCH with the DCI format 2\_0 when + - at the beginning of the first slot, of a group of slots, that is at least symbols after the last symbol of the PDCCH with the DCI format 2\_0 when +- if the UE detects a DCI format 2\_0 and a value of the search space set group switching flag field in the DCI format 2\_0 is 1, the UE starts monitoring PDCCH according to search space sets with group index 1, and stops monitoring PDCCH according to search space sets with group index 0, for the serving cell + - at the beginning of the first slot that is at least symbols after the last symbol of the PDCCH with the DCI format 2\_0, when + - at the beginning of the first slot, of a group of slots, that is at least symbols after the last symbol of the PDCCH with the DCI format 2\_0 when + +and the UE sets the timer value to the value provided by *searchSpaceSwitchTimer* + +- if the UE monitors PDCCH for a serving cell according to search space sets with group index 1, the UE starts monitoring PDCCH for the serving cell according to search space sets with group index 0, and stops monitoring PDCCH according to search space sets with group index 1, for the serving cell + - at the beginning of the first slot that is at least symbols after a slot where the timer expires or after a last symbol of a remaining channel occupancy duration for the serving cell if indicated by DCI format 2\_0 when + - at the beginning of the first slot, of a group of slots, that is at least symbols after a slot where the timer expires or after a last symbol of a remaining channel occupancy duration for the serving cell if indicated by DCI format 2\_0 when + +If a UE is provided *searchSpaceGroupIdList* and is not provided *SearchSpaceSwitchTrigger* for a serving cell, + +- if the UE detects a DCI format by monitoring PDCCH according to a search space set with group index 0, the UE starts monitoring PDCCH according to search space sets with group index 1, and stops monitoring PDCCH according to search space sets with group index 0, for the serving cell + - at the beginning of the first slot that is at least symbols after the last symbol of the PDCCH with the DCI format when , + - at the beginning of the first slot, of a group of slots, that is at least symbols after the last symbol of the PDCCH with the DCI format when + +the UE sets the timer value to the value provided by *searchSpaceSwitchTimer* if the UE detects a DCI format by monitoring PDCCH in any search space set + +- if the UE monitors PDCCH for a serving cell according to search space sets with group index 1, the UE starts monitoring PDCCH for the serving cell according to search space sets with group index 0, and stops monitoring PDCCH according to search space sets with group index 1, for the serving cell + - at the beginning of the first slot that is at least symbols after a slot where the timer expires or, if the UE is provided a search space set to monitor PDCCH for detecting a DCI format 2\_0, after a last symbol of a remaining channel occupancy duration for the serving cell if indicated by DCI format 2\_0 when + - at the beginning of the first slot, of a group of slots, that is at least symbols after a slot where the timer expires or, if the UE is provided a search space set to monitor PDCCH for detecting a DCI format 2\_0, after a last symbol of a remaining channel occupancy duration for the serving cell if indicated by DCI format 2\_0 when + +A UE determines a slot and a symbol in the slot to start or stop PDCCH monitoring according to search space sets for a serving cell that the UE is provided *searchSpaceGroupIdList* or, if *cellGroupsForSwitchList* is provided, for a set of serving cells, based on the largest if the SCS configuration among all configured DL BWPs in the set of serving cells equals to 6, otherwise, based on the smallest SCS configuration among all configured DL BWPs in the serving cell or in the set of serving cells and, if any, in the serving cell where the UE receives a PDCCH and detects a corresponding DCI format 2\_0 triggering the start or stop of PDCCH monitoring according to search space sets. + +A UE can be provided a set of durations by *pdcch-SkippingDurationList* for PDCCH monitoring on an active DL BWP of a serving cell and, if the UE is not provided *searchSpaceGroupIdList-r17* on the active DL BWP of the serving cell, a DCI format 0\_1/0\_2/0\_3 that schedules PUSCH transmission, and a DCI format 1\_1/1\_2/1\_3 that schedules PDSCH reception, can include a PDCCH monitoring adaptation field of 1 bit or of 2 bits. + +If the field has 1 bit and for PDCCH monitoring by the UE according to Type3-PDCCH CSS sets or USS sets on the active DL BWP of the serving cell + +- a '0' value for the bit indicates no skipping in PDCCH monitoring +- a '1' value for the bit indicates skipping PDCCH monitoring for a duration provided by the first value in the set of durations + +If the field has 2 bits and for PDCCH monitoring by the UE according to Type3-PDCCH CSS sets or USS sets on the active DL BWP of the serving cell + +- a '00' value for the bits indicates no skipping in PDCCH monitoring +- a '01' value for the bits indicates skipping PDCCH monitoring for a duration provided by the first value in the set of durations +- a '10' value for the bits indicates skipping PDCCH monitoring for a duration provided by the second value in the set of durations +- a '11' value for the bits indicates skipping PDCCH monitoring for a duration provided by the third value in the set of durations, if any; otherwise, if the set of durations includes two values, a use of the '11' value is reserved + +A UE can be provided group indexes for a Type3-PDCCH CSS set or USS set by *searchSpaceGroupIdList-r17* for PDCCH monitoring on an active DL BWP of a serving cell and, if the UE is not provided *pdcch-SkippingDurationList* for the active DL BWP of the serving cell, a DCI format 0\_1/0\_2/0\_3 that schedules PUSCH transmission, and a DCI format 1\_1/1\_2/1\_3 that schedules PDSCH reception, can include a PDCCH monitoring adaptation field of 1 bit or of 2 bits for the serving cell. + +If the field has 1 bit and for PDCCH monitoring by the UE according to Type3-PDCCH CSS sets or USS sets on the active DL BWP of the serving cell + +- a '0' value for the bit indicates start of PDCCH monitoring according to search space sets with group index 0 and stop of PDCCH monitoring according to search space sets with other group indexes, if any +- a '1' value for the bit indicates start of PDCCH monitoring according to search space sets with group index 1 and stop of PDCCH monitoring according to search space sets with other group indexes, if any, and the UE sets the timer value to the one provided by *searchSpaceSwitchTimer-r17*, if provided + +If the field has 2 bits and for PDCCH monitoring by the UE according to Type3-PDCCH CSS sets or USS sets on the active DL BWP of the serving cell + +- a '00' value for the bit indicates start of PDCCH monitoring according to search space sets with group index 0 and stop of PDCCH monitoring according to search space sets with other group indexes, if any +- a '01' value for the bit indicates start of PDCCH monitoring according to search space sets with group index 1 and stop of PDCCH monitoring according to search space sets with other group indexes, if any, and the UE sets the timer value to the one provided by *searchSpaceSwitchTimer-r17*, if provided +- a '10' value for the bit indicates start of PDCCH monitoring according to search space sets with group index 2 and stop of PDCCH monitoring according to search space sets with other group indexes, if any, and the UE sets the timer value to the one provided by *searchSpaceSwitchTimer-r17*, if provided +- a '11' value is reserved + +A UE can be provided a set of durations by *pdcch-SkippingDurationList* and group indexes for a Type3-PDCCH CSS set or USS set by *searchSpaceGroupIdList-r17* for PDCCH monitoring on an active DL BWP of a serving cell and, a DCI format 0\_1/0\_2/0\_3 that schedules PUSCH transmission, and a DCI format 1\_1/1\_2/1\_3 that schedules PDSCH reception, can include a PDCCH monitoring adaptation field of 2 bits. + +If the set of durations includes one value and for PDCCH monitoring by the UE according to Type3-PDCCH CSS sets or USS sets on the active DL BWP of the serving cell + +- a '00' value for the bits indicates start of PDCCH monitoring according to search space sets with group index 0 and stop of PDCCH monitoring according to search space sets with group index 1, if any +- a '01' value for the bits indicates start of PDCCH monitoring according to search space sets with group index 1 and stop of PDCCH monitoring according to search space sets with group index 0, if any, and the UE sets the timer value to the one provided by *searchSpaceSwitchTimer-r17*, if provided +- a '10' value for the bits indicates skipping PDCCH monitoring for a duration provided by the value in the set of durations +- a '11' value is reserved + +If the set of durations includes two values and for PDCCH monitoring by the UE according to Type3-PDCCH CSS sets or USS sets on active DL BWP of the serving cell + +- a '00' value for the bits indicates start of PDCCH monitoring according to search space sets with group index 0 and stop of PDCCH monitoring according to search space sets with group index 1, if any +- a '01' value for the bits indicates start of PDCCH monitoring according to search space sets with group index 1 and stop of PDCCH monitoring according to search space sets with group index 0, if any, and the UE sets the timer value to the one provided by *searchSpaceSwitchTimer-r17*, if provided +- a '10' value for the bits indicates skipping PDCCH monitoring for a duration provided by the first value in the set of durations +- a '11' value for the bits indicates skipping PDCCH monitoring for a duration provided by the second value in the set of durations + +When the PDCCH monitoring adaptation field indicates to a UE to start PDCCH monitoring according to search space sets with a first group index and stop PDCCH monitoring according to search space sets with a second group index, the UE applies the indication + +- at the beginning of a first slot that is at least symbols after the last symbol of the PDCCH reception providing the DCI format with the PDCCH monitoring adaptation field when , +- at the beginning of a first slot, of a slot group of slots, that is at least symbols after the last symbol of the PDCCH reception providing the DCI format with the PDCCH monitoring adaptation field when + +When the PDCCH monitoring adaptation field indicates to a UE to skip PDCCH monitoring for a duration on the active DL BWP of a serving cell, the UE starts skipping of PDCCH monitoring at the beginning of a first slot that is after the last symbol of the PDCCH reception providing the DCI format with the PDCCH monitoring adaptation field. + +- If the UE transmits a PUCCH providing a positive SR before the UE detects a DCI format providing the PDCCH monitoring adaptation field indicating to the UE to skip PDCCH monitoring for the duration on the active DL BWP of the serving cell, the UE shall monitor PDCCH regardless of PDCCH skipping indication on all serving cells of the corresponding Cell Group when the SR is pending [11, TS 38.321]. +- If the UE transmits a PUCCH providing a positive SR after the UE detects a DCI format providing the PDCCH monitoring adaptation field indicating to the UE to skip PDCCH monitoring for the duration on the active DL BWP of the serving cell, the UE resumes PDCCH monitoring starting at the beginning of a first slot that is after a last symbol of the PUCCH transmission in all serving cells of the corresponding Cell Group. +- When the UE is provided *pdcchMornitoringResumptionAfterNack*, after the UE detects a DCI format providing the PDCCH monitoring adaptation field indicating to the UE to skip PDCCH monitoring for the duration on the active DL BWP of the serving cell, if the UE transmits a PUCCH or a PUSCH providing a NACK value associated with a PDSCH reception that is scheduled by a DCI format in a PDCCH reception on the serving cell, + +the UE terminates PDCCH skipping, starting from the beginning of a first slot that is after a last symbol of the PUCCH or PUSCH transmission on the serving cell. + +- During the time of *ra-ResponseWindow* or *msgB-ResponseWindow* or the duration where *ra-ContentionResolutionTimer* is running, the UE shall not skip PDCCH monitoring on SpCell. +- After the UE detects a DCI format providing the PDCCH monitoring adaptation field indicating to the UE to skip PDCCH monitoring for the duration on the active DL BWP of a SpCell, when contention resolution is successful [11, TS 38.321], the UE resumes PDCCH monitoring on the SpCell. +- After the UE detects a DCI format providing the PDCCH monitoring adaptation field indicating to the UE to skip PDCCH monitoring for the duration on the active DL BWP of a serving cell, when a pending SR is cancelled [11, TS 38.321], the UE resumes PDCCH monitoring in all serving cells of the corresponding Cell Group. +- If UE transmits a RACH due to positive SR, the UE shall not skip PDCCH monitoring on any serving cell of the corresponding Cell Group during the time of *ra-ResponseWindow* or *msgB-ResponseWindow* or the duration where *ra-ContentionResolutionTimer* is running. If DRX is configured and the DRX group of the serving cell enters outside Active Time, the UE terminates PDCCH skipping for the serving cell. + +If the UE changes to a new active DL BWP of the serving cell by the expiration of *bwp-InactivityTimer* or by RRC configuration, the UE + +- resumes PDCCH monitoring according to the search space sets on the new active BWP of the serving cell when UE is in a PDCCH skipping duration, if the UE is not provided *searchSpaceGroupIdList-r17* on the new active DL BWP +- monitors PDCCH according to search space sets with group index 0 on the new active BWP of the serving cell, if the UE is provided *searchSpaceGroupIdList-r17*. + +If a UE is provided group indexes for a Type3-PDCCH CSS set or a USS set by *searchSpaceGroupIdList-r17* and a timer value by *searchSpaceSwitchTimer-r17* for PDCCH monitoring an active DL BWP of on a serving cell and the timer is running, the UE + +- resets the timer after a slot of the active DL BWP of the serving cell if the UE detects a DCI format in a PDCCH reception in the slot for with CRC scrambled by C-RNTI/CS-RNTI/MCS-C-RNTI/G-RNTI for multicast/G-CS-RNTI +- otherwise, decrements the timer value by one after a slot of the active DL BWP of the serving cell + +When the timer expires in a first slot, the UE monitors PDCCH on the serving cell according to search space sets with group index 0 starting in a second slot that + +- is not earlier than symbols after the first slot when , +- is a first slot in a slot group of slots that is not earlier than symbols after the first slot when , +- is not earlier than a slot where a PDCCH skipping duration expires, if applicable + +When a UE receives + +- a first PDCCH in a first slot that provides a DCI format with a PDCCH monitoring adaptation field having a first value indicating skipping PDCCH monitoring, or indicating start of PDCCH monitoring according to a search space sets with a first group index and stop of PDCCH monitoring according to search space sets with a second group index, for an active DL BWP and +- a second PDCCH that provides a DCI format with a PDCCH monitoring adaptation field having a second value indicating skipping PDCCH monitoring, or indicating start of PDCCH monitoring according to search space sets with a first group index and stop of PDCCH monitoring according to search space sets with a second group index different than the first group index, for the active DL BWP where the second PDCCH is received + - in the first slot if the first value indicates skipping PDCCH monitoring + - before a slot that is at least symbols after the first slot if the first value indicates start of PDCCH monitoring according to search space sets with a first group index + +the UE does not expect the second value to be different than the first value. + +A UE does not expect to receive in a second slot a PDCCH on an active DL BWP that provides a DCI format indicating skipping PDCCH monitoring, or start of PDCCH monitoring according to search space sets with group index 1 or 2 for the active DL BWP, if the second slot is not at least symbols after a first slot where the timer expires. + +## 10.4A PDCCH monitoring for early indication of paging + +A UE can be provided the following for detection of a DCI format 2\_7 in RRC\_IDLE state or in RRC\_INACTIVE state [12, TS 38.331] + +- a search space set, by *pei-SearchSpace*, to monitor PDCCH for detection of DCI format 2\_7 according to a Type2A-PDCCH CSS set as described in clause 10.1 +- a number of frames, by *pei-FrameOffset*, from the start of a frame to the start of a first paging frame of paging frames associated with a number of PDCCH monitoring occasions for DCI format 2\_7 [17, TS 38.304] +- a number of symbols, by *firstPDCCH-MonitoringOccasionOfPEI-O*, from the start of the frame to the start of the first PDCCH monitoring occasion for DCI format 2\_7 +- a size, by *payloadSizeDCI-2-7* +- a number of subgroups per paging occasion, , by *subgroupsNumPerPO* +- a number of paging occasions associated with the number of PDCCH monitoring occasions for DCI format 2\_7, , by *po-NumPerPEI* + +A paging indication field of DCI format 2\_7 includes segments of bits, where . For a subgroup index , , a UE determines a value for the bit in the paging indication field, where is a paging occasion index, and , , , and are defined in [17, TS 38.304]. When the value is '1', the UE monitors a paging occasion determined according to [17, TS 38.304]; otherwise, the UE is not required to monitor the paging occasion. + +If , the number of symbols from the start of the frame to the start of the first PDCCH monitoring occasion for DCI format 2\_7 that is associated with paging occasion index is the -th value from the values provided by *firstPDCCH-MonitoringOccasionOfPEI-O*. + +## 10.4B Indication of TRS resources + +A UE in RRC\_IDLE state or RRC\_INACTIVE state can be provided by *trs-ResourceSetConfig* a set of TRS occasions [6, TS 38.214]. If *trs-ResourceSetConfig* is provided, a DCI format 2\_7, if *pei-SearchSpace* is provided, and a DCI format 1\_0 with CRC scrambled by P-RNTI includes a TRS availability indication field [4, TS 38.212] that provides a bitmap to groups of TRS resource sets where the configuration of each TRS resource set includes an association to a bit of the bitmap. The UE can be additionally provided a multiple, by *validityDuration*, for a number of frames provided by *defaultPagingCycle* for TRS resource sets with indicated presence; if *validityDuration* is not provided, the multiple is equal to 2. + +A value of '1' for a bit of the bitmap indicates presence of associated TRS resource sets for the multiple of the number of frames, starting from a SFN determined from [17, TS 38.304] that corresponds to the frame within the DRX cycle that includes the PDCCH providing the DCI format 2\_7, or the DCI format 1\_0 with CRC scrambled by P-RNTI, with the TRS availability indication field indicating the TRS resource sets, where is provided by *defaultPagingCycle*. A value of '0' for a bit of the bitmap indicates no change to a current assumption for the availability or unavailability of associated TRS resource sets. + +A UE can receive first and second PDCCHs that provide DCI format 2\_7 or DCI format 1\_0 with CRC scrambled by P-RNTI that indicate presence of TRS resource sets for the multiple of the number of frames, where the second PDCCH reception after the first PDCCH reception by a time that is smaller than the multiple of the number of frames. + +## 10.5 HARQ-ACK information for PUSCH transmissions + +A UE can be configured a number of search space sets to monitor PDCCH for detecting a DCI format 0\_1 with a DFI flag field and CRC scrambled with a CS-RNTI provided by *cs-RNTI*. The UE determines that the DCI format provides HARQ-ACK information for PUSCH transmissions based on when a DFI flag field value is set to '1', if a PUSCH transmission is configured by *ConfiguredGrantConfig*. + +The HARQ-ACK information corresponds to transport blocks in PUSCH transmissions for all HARQ processes for a serving cell of a PDCCH reception that provides DCI format 0\_1 or, if DCI format 0\_1 includes a carrier indicator field, for a serving cell indicated by a value of the carrier indicator field. + +For a PUSCH transmission configured by *ConfiguredGrantConfig*, HARQ-ACK information for a transport block of a corresponding HARQ process number is valid if a first symbol of the PDCCH reception is after a last symbol of the PUSCH transmission, or of any repetition of the PUSCH transmission, by a number of symbols provided by *cgr-minDFI-Delay*. + +For an initial transmission by a UE of a transport block in a PUSCH configured by *ConfiguredGrantConfig*, if the UE receives a CG-DFI that provides HARQ-ACK information for the transport block, the UE assumes that the transport block was correctly decoded if the HARQ-ACK information value is ACK; otherwise, the UE assumes that the transport block was not correctly decoded. + +For a PUSCH transmission scheduled by a DCI format, if the UE receives a CG-DFI that provides HARQ-ACK information for the transport block, the UE assumes that the transport block was correctly decoded if the HARQ-ACK information value is ACK; otherwise, the UE assumes that the transport block was not correctly decoded. + +For a PUSCH transmission scheduled by a DCI format, HARQ-ACK information for a transport block of a corresponding HARQ process number is valid if a first symbol of the PDCCH reception is after a last symbol of the PUSCH transmission by a number of symbols provided by *cgr-minDFI-Delay* or, if the PUSCH transmission is over multiple slots, + +- after a last symbol of the PUSCH transmission in a first slot from the multiple slots by a number of symbols provided by *cgr-minDFI-Delay*, if a value of the HARQ-ACK information is ACK. +- after a last symbol of the PUSCH transmission in a last slot from the multiple slots by a number of symbols provided by *cgr-minDFI-Delay*, if a value of the HARQ-ACK information is NACK. + +UE does not expect to be configured with different *cgr-minDFI-Delay* among multiple *ConfiguredGrantConfig* in one BWP. + +# 11 UE-group common signalling + +If the UE is configured with a SCG, the UE shall apply the procedures described in this clause for both MCG and SCG + +- When the procedures are applied for MCG, the terms 'secondary cell', 'secondary cells', 'serving cell', 'serving cells' in this clause refer to secondary cell, secondary cells, serving cell, serving cells belonging to the MCG respectively. +- When the procedures are applied for SCG, the terms 'secondary cell', 'secondary cells', 'serving cell', 'serving cells' in this clause refer to secondary cell, secondary cells (not including PSCell), serving cell, serving cells belonging to the SCG respectively. The term 'primary cell' in this clause refers to the PSCell of the SCG. + +In the remaining of this clause, unless stated otherwise, when a PDCCH reception by a UE includes two PDCCH candidates from corresponding search space sets, as described in clause 10.1 + +- a PDCCH monitoring occasion is the union of the PDCCH monitoring occasions for the two PDCCH candidates +- the start of the PDCCH reception is the start of the earlier PDCCH candidate +- the end of the PDCCH reception is the end of the PDCCH candidate that ends later + +The PDCCH reception includes the two PDCCH candidates also when the UE is not required to monitor one of the two PDCCH candidates as described in clauses 10 (except clause 10.4), 11.1, 11.1.1 and 17.2. + +## 11.1 Slot configuration + +A slot format includes downlink symbols, uplink symbols, and flexible symbols. + +The following are applicable for each serving cell. + +If a UE is provided *tdd-UL-DL-ConfigurationCommon*, the UE sets the slot format per slot over a number of slots as indicated by *tdd-UL-DL-ConfigurationCommon*. + +The *tdd-UL-DL-ConfigurationCommon* provides + +- a reference SCS configuration $\mu_{\text{ref}}$ by *referenceSubcarrierSpacing* +- a *pattern1*. + +The *pattern1* provides + +- a slot configuration period of $P$ msec by *dl-UL-TransmissionPeriodicity* +- a number of slots $d_{\text{slots}}$ with only downlink symbols by *nrofDownlinkSlots* +- a number of downlink symbols $d_{\text{sym}}$ by *nrofDownlinkSymbols* +- a number of slots $u_{\text{slots}}$ with only uplink symbols by *nrofUplinkSlots* +- a number of uplink symbols $u_{\text{sym}}$ by *nrofUplinkSymbols* + +A value $P=0.625$ msec is valid only for , . A value $P=1.25$ msec is valid only for , . A value $P=2.5$ msec is valid only for , . A value $P=10$ msec is valid only for , or . + +A slot configuration period of $P$ msec includes $S = P \cdot 2^{\mu_{\text{ref}}}$ slots with SCS configuration $\mu_{\text{ref}}$ . From the $S$ slots, a first $d_{\text{slots}}$ slots include only downlink symbols and a last $u_{\text{slots}}$ slots include only uplink symbols. The $d_{\text{sym}}$ symbols after the first $d_{\text{slots}}$ slots are downlink symbols. The $u_{\text{sym}}$ symbols before the last $u_{\text{slots}}$ slots are uplink symbols. The remaining $(S - d_{\text{slots}} - u_{\text{slots}}) \cdot N_{\text{symb}}^{\text{slot}} - d_{\text{sym}} - u_{\text{sym}}$ are flexible symbols. + +The first symbol every $20/P$ periods is a first symbol in an even frame. + +If *tdd-UL-DL-ConfigurationCommon* provides both *pattern1* and *pattern2*, the UE sets the slot format per slot over a first number of slots as indicated by *pattern1* and the UE sets the slot format per slot over a second number of slots as indicated by *pattern2*. + +The *pattern2* provides + +- a slot configuration period of $P_2$ msec by *dl-UL-TransmissionPeriodicity* +- a number of slots $d_{\text{slots},2}$ with only downlink symbols by *nrofDownlinkSlots* +- a number of downlink symbols $d_{\text{sym},2}$ by *nrofDownlinkSymbols* +- a number of slots $u_{\text{slots},2}$ with only uplink symbols by *nrofUplinkSlots* +- a number of uplink symbols $u_{\text{sym},2}$ by *nrofUplinkSymbols* + +The applicable values of $P_2$ are same as the applicable values for $P$ . + +A slot configuration period of $P + P_2$ msec includes first $S = P \cdot 2^{\mu_{\text{ref}}}$ slots and second $S_2 = P_2 \cdot 2^{\mu_{\text{ref}}}$ slots. + +From the $S_2$ slots, a first $d_{\text{slots},2}$ slots include only downlink symbols and a last $u_{\text{slots},2}$ include only uplink symbols. The $d_{\text{sym},2}$ symbols after the first $d_{\text{slots},2}$ slots are downlink symbols. The $u_{\text{sym},2}$ symbols before the last $u_{\text{slots},2}$ slots are uplink symbols. The remaining $(S_2 - d_{\text{slots},2} - u_{\text{slots},2}) \cdot N_{\text{symb}}^{\text{slot}} - d_{\text{sym},2} - u_{\text{sym},2}$ are flexible symbols. + +A UE expects that $P + P_2$ divides 20 msec. + +The first symbol every $20/(P + P_2)$ periods is a first symbol in an even frame. + +A UE expects that the reference SCS configuration $\mu_{\text{ref}}$ is smaller than or equal to a SCS configuration $\mu$ for any configured DL BWP or UL BWP. Each slot provided by *pattern1* or *pattern2* is applicable to $2^{(\mu - \mu_{\text{ref}})}$ consecutive slots in the active DL BWP or the active UL BWP where the first slot starts at a same time as a first slot for the reference SCS configuration $\mu_{\text{ref}}$ and each downlink or flexible or uplink symbol for the reference SCS configuration $\mu_{\text{ref}}$ corresponds to $2^{(\mu - \mu_{\text{ref}})}$ consecutive downlink or flexible or uplink symbols for the SCS configuration $\mu$ . + +If the UE is additionally provided *tdd-UL-DL-ConfigurationDedicated*, the parameter *tdd-UL-DL-ConfigurationDedicated* overrides only flexible symbols per slot over the number of slots as provided by *tdd-UL-DL-ConfigurationCommon*. + +The *tdd-UL-DL-ConfigurationDedicated* provides + +- a set of slot configurations by *slotSpecificConfigurationsToAddModList* +- for each slot configuration from the set of slot configurations + - a slot index for a slot provided by *slotIndex* + - a set of symbols for a slot by *symbols* where + - if *symbols* = *allDownlink*, all symbols in the slot are downlink + - if *symbols* = *allUplink*, all symbols in the slot are uplink + - if *symbols* = *explicit*, *nrofDownlinkSymbols* provides a number of downlink first symbols in the slot and *nrofUplinkSymbols* provides a number of uplink last symbols in the slot. If *nrofDownlinkSymbols* is not provided, there are no downlink first symbols in the slot and if *nrofUplinkSymbols* is not provided, there are no uplink last symbols in the slot. The remaining symbols in the slot are flexible + +For each slot having a corresponding index provided by *slotIndex*, the UE applies a format provided by a corresponding *symbols*. The UE does not expect *tdd-UL-DL-ConfigurationDedicated* to indicate as uplink or as downlink a symbol that *tdd-UL-DL-ConfigurationCommon* indicates as a downlink or as an uplink symbol, respectively. + +For each slot configuration provided by *tdd-UL-DL-ConfigurationDedicated*, a reference SCS configuration is the reference SCS configuration $\mu_{\text{ref}}$ provided by *tdd-UL-DL-ConfigurationCommon*. + +A slot configuration period and a number of downlink symbols, uplink symbols, and flexible symbols in each slot of the slot configuration period are determined from *tdd-UL-DL-ConfigurationCommon* and *tdd-UL-DL-ConfigurationDedicated* and are common to each configured BWP. + +A UE considers symbols in a slot indicated as downlink by *tdd-UL-DL-ConfigurationCommon*, or *tdd-UL-DL-ConfigurationDedicated* to be available for receptions and considers symbols in a slot indicated as uplink by *tdd-UL-DL-ConfigurationCommon*, or by *tdd-UL-DL-ConfigurationDedicated* to be available for transmissions. + +If a UE is not configured to monitor PDCCH for DCI format 2\_0, for a set of symbols of a slot that are indicated as flexible by *tdd-UL-DL-ConfigurationCommon* and *tdd-UL-DL-ConfigurationDedicated* if provided, or when *tdd-UL-DL-ConfigurationCommon* and *tdd-UL-DL-ConfigurationDedicated* are not provided to the UE + +- the UE receives PDSCH or CSI-RS in the set of symbols of the slot if the UE receives a corresponding indication by a DCI format +- the UE transmits PUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot if the UE receives a corresponding indication by a DCI format, a RAR UL grant, fallbackRAR UL grant, or successRAR + +For operation on a single carrier in unpaired spectrum, if a UE is configured by higher layers to receive a PDCCH, or a PDSCH, or a CSI-RS, or a DL PRS in a set of symbols of a slot, the UE receives the PDCCH, the PDSCH, the CSI-RS, or the DL PRS if the UE does not detect a DCI format that indicates to the UE to transmit a PUSCH, a PUCCH, a + +PRACH, or a SRS in at least one symbol of the set of symbols of the slot; otherwise, the UE does not receive the PDCCH, or the PDSCH, or the CSI-RS, or the DL PRS in the set of symbols of the slot. + +For a UE operation with shared spectrum channel access in FR1, or in FR2-2 when the UE is provided *ChannelAccessMode2* = 'enabled', if the UE is provided *csi-RS-ValidationWithDCI*, is not provided *CO-DurationsPerCell*, and is not provided *SlotFormatCombinationsPerCell*, and if the UE is configured by higher layers to receive a CSI-RS in a set of symbols of a slot, the UE cancels the CSI-RS reception in the set of symbols of the slot if the UE does not detect a DCI format indicating an aperiodic CSI-RS reception or scheduling a PDSCH reception in the set of symbols of the slot. + +If a UE is provided *channelAccessMode* = 'dynamic' and is provided *availableRB-SetsToAddModList* and *availableRB-SetsToReleaseList*, the UE expects to be provided *co-DurationsPerCellToAddModList* and *co-DurationsPerCellToReleaseList* and/or *slotFormatCombToAddModList* and *slotFormatCombToReleaseList*. + +For operation on a single carrier in unpaired spectrum, if a UE is configured by higher layers to transmit SRS, or PUCCH, or PUSCH, or PRACH in a set of symbols of a slot and the UE detects a DCI format indicating to the UE to receive CSI-RS or PDSCH in a subset of symbols from the set of symbols, then + +- If the UE does not indicate the capability of [partialCancellation], the UE does not expect to cancel the transmission of the PUCCH or PUSCH or PRACH in the set of symbols if the first symbol in the set occurs within *Tproc,2* relative to a last symbol of a PDCCH reception where the UE detects the DCI format; otherwise, the UE cancels the PUCCH, or the PUSCH, or an actual repetition of the PUSCH [6, TS 38.214], determined from clauses 9, 9.2.5 and 9.2.6 or clause 6.1 of [6, TS 38.214], or the PRACH transmission in the set of symbols. +- If the UE indicates the capability of [partialCancellation], the UE does not expect to cancel the transmission of the PUCCH or PUSCH or PRACH in symbols from the set of symbols that occur within *Tproc,2* relative to a last symbol of a PDCCH reception where the UE detects the DCI format. The UE cancels the PUCCH, or the PUSCH, or an actual repetition of the PUSCH [6, TS 38.214], determined from clauses 9, 9.2.5 and 9.2.6 or clause 6.1 of [6, TS 38.214], or the PRACH transmission in remaining symbols from the set of symbols. +- The UE does not expect to cancel the transmission of SRS in symbols from the subset of symbols that occur within *Tproc,2* relative to a last symbol of a PDCCH reception where the UE detects the DCI format. The UE cancels the SRS transmission in remaining symbols from the subset of symbols. + +*Tproc,2* is the PUSCH preparation time for the corresponding UE processing capability [6, TS 38.214] assuming *Tproc,1* and corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH carrying the DCI format and the SCS configuration of the SRS, PUCCH, PUSCH or , where *Tproc,1* corresponds to the SCS configuration of the PRACH if it is 15kHz or higher; otherwise . + +For a set of symbols of a slot that are indicated to a UE as uplink by *tdd-UL-DL-ConfigurationCommon*, or *tdd-UL-DL-ConfigurationDedicated*, the UE does not receive PDCCH, PDSCH, or CSI-RS when the PDCCH, PDSCH, or CSI-RS overlaps, even partially, with the set of symbols of the slot. + +For a set of symbols of a slot that are indicated to a UE as uplink by *tdd-UL-DL-ConfigurationCommon*, or *tdd-UL-DL-ConfigurationDedicated*, the UE does not receive DL PRS in the set of symbols of the slot, if the UE is not provided with a measurement gap. + +For a set of symbols of a slot that are indicated to a UE as downlink by *tdd-UL-DL-ConfigurationCommon*, or *tdd-UL-DL-ConfigurationDedicated*, the UE does not transmit PUSCH, PUCCH, PRACH, or SRS when the PUSCH, PUCCH, PRACH, or SRS overlaps, even partially, with the set of symbols of the slot. + +For a set of symbols of a slot that are indicated to a UE as flexible by *tdd-UL-DL-ConfigurationCommon*, and *tdd-UL-DL-ConfigurationDedicated* if provided, the UE does not expect to receive both dedicated higher layer parameters configuring transmission from the UE in the set of symbols of the slot and dedicated higher layer parameters configuring reception by the UE in the set of symbols of the slot. + +For operation on a single carrier in unpaired spectrum, for a set of symbols of a slot indicated to a UE for reception of SS/PBCH blocks by *ssb-PositionsInBurst* in *SIB1* or by *ssb-PositionsInBurst* in *ServingCellConfigCommon* or, if the UE is not provided *dl-OrJointTCI-StateList*, by *ssb-PositionsInBurst* in *SSB-MTCAdditionalPCI* associated to physical cell ID with active TCI states for PDCCH or PDSCH, or for a set of symbols of a slot corresponding to SS/PBCH blocks configured for L1 beam measurement/reporting, the UE does not transmit PUSCH, PUCCH, PRACH in the slot if a transmission would overlap with any symbol from the set of symbols and the UE does not transmit SRS in the set of symbols of the slot. The UE does not expect the set of symbols of the slot to be indicated as uplink by *tdd-UL-DL-ConfigurationCommon*, or *tdd-UL-DL-ConfigurationDedicated*, when provided to the UE. + +If a UE + +- is configured with multiple serving cells and is provided with *directionalCollisionHandling-r16* = 'enabled' for a set of serving cell(s) among the multiple serving cells, and +- indicates support of *half-DuplexTDD-CA-SameSCS-r16* capability, and +- is not configured to monitor PDCCH for detection of DCI format 2\_0 on any of the multiple serving cells, + +for a set of symbols of a slot that are indicated to the UE for reception of SS/PBCH blocks in a first cell of the multiple serving cells by *ssb-PositionsInBurst* in *SystemInformationBlockType1* or by *ssb-PositionsInBurst* in *ServingCellConfigCommon* or, if the UE is not provided *dl-OrJointTCI-StateList*, by *ssb-PositionsInBurst* in *SSB-MTCAdditionalPCI* associated to physical cell ID with active TCI states for PDCCH or PDSCH, or for a set of symbols of a slot corresponding to SS/PBCH blocks configured for L1 beam measurement/reporting, the UE does not transmit PUSCH, PUCCH, or PRACH in the slot if a transmission would overlap with any symbol from the set of symbols, and the UE does not transmit SRS in the set of symbols of the slot in + +- any of the multiple serving cells if the UE is not capable of simultaneous transmission and reception as indicated by *simultaneousRxBTxInterBandCA* among the multiple serving cells, and +- any one of the cells corresponding to the same band as the first cell, irrespective of any capability indicated by *simultaneousRxBTxInterBandCA*. + +For a set of symbols of a slot corresponding to a valid PRACH occasion and $N_{\text{gap}}$ symbols before the valid PRACH occasion, as described in clause 8.1, the UE does not receive PDCCH, PDSCH, or CSI-RS in the slot if a reception would overlap with any symbol from the set of symbols. The UE does not expect the set of symbols of the slot to be indicated as downlink by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated*. + +For a set of symbols of a slot indicated to a UE by *pdcch-ConfigSIB1* in *MIB* for a CORESET for Type0-PDCCH CSS set, the UE does not expect the set of symbols to be indicated as uplink by *tdd-UL-DL-ConfigurationCommon*, or *tdd-UL-DL-ConfigurationDedicated*. + +If a UE is scheduled by a DCI format to receive PDSCH over multiple slots, and if *tdd-UL-DL-ConfigurationCommon*, or *tdd-UL-DL-ConfigurationDedicated*, indicate that, for a slot from the multiple slots, at least one symbol from a set of symbols where the UE is scheduled PDSCH reception in the slot is an uplink symbol, the UE does not receive the PDSCH in the slot. + +If a UE is scheduled by a DCI format to transmit PUSCH over multiple slots, and if *tdd-UL-DL-ConfigurationCommon*, or *tdd-UL-DL-ConfigurationDedicated*, indicates that, for a slot from the multiple slots, at least one symbol from a set of symbols where the UE is scheduled PUSCH transmission in the slot is a downlink symbol, the UE does not transmit the PUSCH in the slot. + +If a UE + +- is configured with multiple serving cells and is provided with *directionalCollisionHandling-r16* = 'enabled' for a set of serving cell(s) among the configured multiple serving cells, and +- indicates support of *half-DuplexTDD-CA-SameSCS-r16* capability, and +- is not configured to monitor PDCCH for detection of DCI format 2\_0 on any of the multiple serving cells, + +the UE determines a reference cell for a symbol as an active cell with the smallest cell index among + +- the configured multiple serving cells if the UE is not capable of simultaneous transmission and reception as indicated by *simultaneousRxBTxInterBandCA* among the multiple serving cells, and +- the cells of each band respectively if the UE is capable of simultaneous transmission and reception by *simultaneousRxBTxInterBandCA* for the configured multiple serving cells, + +where the symbol is configured as + +- downlink, or uplink, as indicated by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* +- uplink, if the symbol is flexible and the UE is configured to transmit SRS, PUCCH, PUSCH, or PRACH on the symbol + +- downlink, if the symbol is flexible and the UE is configured to receive PDCCH, PDSCH or CSI-RS on the symbol. + +And if another cell among the cells configured with *directionalCollisionHandling-r16* operates in the same frequency band as the reference cell, the UE does not expect + +- a symbol to be indicated as downlink or uplink on the reference cell and as uplink or downlink on another cell, respectively, by *tdd-UL-DL-ConfigurationCommon* or by *tdd-UL-DL-ConfigurationDedicated*, +- *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* to indicate a symbol as downlink on the reference cell and to detect a DCI format scheduling a transmission on the symbol on another cell, and +- to be configured by higher layers to receive PDCCH, PDSCH, or CSI-RS on a flexible symbol on the reference cell and to detect a DCI format scheduling a transmission on the symbol on another cell, + +if the reference cell and another cell among the cells configured with *directionalCollisionHandling-r16* operate in different frequency bands, + +the UE + +- assumes symbol as flexible, is not required to receive higher layer configured PDCCH, PDSCH, or CSI-RS and not expected to transmit higher layer configured SRS, PUCCH, PUSCH, or PRACH, when *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* indicates symbol as downlink or uplink on another cell and as uplink or downlink for the reference cell, respectively, +- transmits a signal/channel scheduled by a DCI format on a symbol of another cell when the symbol is indicated as downlink by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* for the reference cell, +- is not required to receive a higher layer configured PDCCH, PDSCH, or CSI-RS on flexible symbols on the reference cell in a set of symbols, if the UE detects a DCI format scheduling a transmission on one or more symbols in the set of symbols on another cell, + +and regardless of whether the reference cell and another cell operate in same or different frequency bands, + +the UE + +- does not expect *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* for the reference cell to indicate a symbol as uplink and to detect a DCI format scheduling a reception on the symbol on another cell +- does not expect to be configured by higher layers to transmit SRS, PUCCH, PUSCH, or PRACH on a flexible symbol on the reference cell and to detect a DCI format scheduling a reception on the symbol on another cell +- does not transmit a PUCCH, PUSCH or PRACH that is configured by higher layers on a set of symbols on another cell if at least one symbol from the set of symbols is indicated as downlink by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* or is a symbol corresponding to a PDCCH, PDSCH, or CSI-RS reception that is configured by higher layers on the reference cell +- does not transmit a SRS that is configured by higher layers on a set of symbols on another cell if the set of symbols is indicated as downlink by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* or corresponds to a PDCCH, PDSCH or CSI-RS reception that is configured by higher layers on the reference cell +- does not receive a PDCCH, PDSCH or CSI-RS that is configured by higher layers on a set of symbols on another cell if at least one symbol from the set of symbols is indicated as uplink by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* or is a symbol corresponding to a SRS, PUCCH, PUSCH, or PRACH transmission that is configured by higher layers on the reference cell +- assumes a symbol indicated as downlink or uplink by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* on another cell to be flexible, if the UE is respectively configured by higher layers to transmit SRS, PUCCH, PUSCH, or PRACH or to receive PDCCH, PDSCH, or CSI-RS on the reference cell +- does not expect to detect a first DCI format scheduling a transmission or reception on a symbol on a first cell and a second DCI format scheduling a reception or transmission on the symbol on a second cell, respectively. + +After the UE applies the procedures described above for directional collision handling within the set of cells that have been configured with *directionalCollisionHandling-r16*, the UE does not expect any directional collision among the serving cells that the UE is not capable of simultaneous transmission and reception. + +### 11.1.1 UE procedure for determining slot format + +This clause applies for a serving cell that is included in a set of serving cells configured to a UE by *slotFormatCombToAddModList* and *slotFormatCombToReleaseList*, *availableRB-SetsToAddModList* and *availableRB-SetsToReleaseList*, *switchTriggerToAddModList* and *switchTriggerToReleaseList*, or *co-DurationsPerCellToAddModList* and *co-DurationsPerCellToReleaseList*. + +If a UE is configured by higher layers with parameter *SlotFormatIndicator*, the UE is provided an SFI-RNTI by *sfi-RNTI* and with a payload size of DCI format 2\_0 by *dci-PayloadSize*. + +The UE is also provided in one or more serving cells with a configuration for a search space set *s* and a corresponding CORESET for monitoring PDCCH candidates for DCI format 2\_0 with a CCE aggregation level of CCEs as described in clause 10.1. The PDCCH candidates are the first PDCCH candidates for CCE aggregation level for search space set in CORESET. + +For each serving cell in the set of serving cells, the UE can be provided: + +- an identity of the serving cell by *servingCellId* +- a location of a SFI-index field in DCI format 2\_0 by *positionInDCI* +- a set of slot format combinations by *slotFormatCombinations*, where each slot format combination in the set of slot format combinations includes + - one or more slot formats indicated by a respective *slotFormats* for the slot format combination, and + - a mapping for the slot format combination provided by *slotFormats* to a corresponding SFI-index field value in DCI format 2\_0 provided by *slotFormatCombinationId* +- for unpaired spectrum operation, a reference SCS configuration by *subcarrierSpacing* and, when a supplementary UL carrier is configured for the serving cell, a reference SCS configuration by *subcarrierSpacing2* for the supplementary UL carrier +- for paired spectrum operation, a reference SCS configuration for a DL BWP by *subcarrierSpacing* and a reference SCS configuration for an UL BWP by *subcarrierSpacing2* +- a location of an available RB set indicator field in DCI format 2\_0, by *availableRB-SetsPerCell*, where the field is + - one bit, if *intraCellGuardBandsDL-List* for the serving cell indicates no intra-cell guard-bands are configured, where a value of '1' indicates that the serving cell is available for receptions, a value of '0' indicates that the serving cell is not available for receptions, and the serving cell remains available or unavailable for reception until the end of the remaining channel occupancy duration; or, + - a bitmap having a one-to-one mapping with the RB sets [6, TS 38.214] of the serving cell, if *intraCellGuardBandsDL-List* for the serving cell indicates intra-cell guard-bands are configured or if *intraCellGuardBandsDL-List* is not provided for the serving cell, where the bitmap includes bits and is the number of RB sets in the serving cell, a value of '1' indicates that an RB set is available for receptions, a value of '0' indicates that an RB set is not available for receptions, and a RB set remains available or unavailable for receptions until the end of the remaining channel occupancy duration +- a location of a channel occupancy duration field in DCI format 2\_0, by *CO-DurationsPerCell*, where the field indicates a remaining channel occupancy duration for the serving cell starting from a first symbol of a slot where the UE detects the DCI format 2\_0 by providing a value from *co-DurationList*. The channel occupancy duration field includes bits, where is the number of values provided by *co-DurationList*. If *CO-DurationsPerCell* is not provided, the remaining channel occupancy duration for the serving cell is a number of slots, starting from the slot where the UE detects the DCI format 2\_0, that the SFI-index field value provides corresponding slot formats +- a reference SCS configuration for *co-DurationList*, by *subcarrierSpacing* + +- a location of a search space set group switching flag field in DCI format 2\_0, by *SearchSpaceSwitchTrigger*, where the field indicates a group from two groups of search space sets for PDCCH monitoring for scheduling for the serving cell or the set of serving cells, provided by *CellGroupsForSwitching*, as described in clause 10.4. + +If neither *CO-DurationsPerCell* nor *SlotFormatCombinationsPerCell* are provided and if *channelAccessMode* = "semiStatic" is provided, the procedures in this clause apply with assuming a channel occupancy time defined in clause 4.3 of [15, TS 37.213] is the remaining channel occupancy duration if a DL transmission burst(s) is detected within the channel occupancy time. + +A SFI-index field value in a DCI format 2\_0 indicates to a UE a slot format for each slot in a number of slots for each DL BWP or each UL BWP starting from a slot where the UE detects the DCI format 2\_0. The number of slots is equal to or larger than a PDCCH monitoring periodicity for DCI format 2\_0. The SFI-index field includes + +$\max\{\lceil \log_2(\max\text{SFIindex} + 1) \rceil, 1\}$ bits where *maxSFIindex* is the maximum value of the values provided by corresponding *slotFormatCombinationId*. A slot format is identified by a corresponding format index as provided in Table 11.1.1-1 where 'D' denotes a downlink symbol, 'U' denotes an uplink symbol, and 'F' denotes a flexible symbol. + +If a PDCCH monitoring periodicity for DCI format 2\_0, provided to a UE for the search space set *S* by *monitoringSlotPeriodicityAndOffset*, is smaller than a duration of a slot format combination the UE obtains at a PDCCH monitoring occasion for DCI format 2\_0 by a corresponding SFI-index field value, and the UE detects more than one DCI formats 2\_0 indicating a slot format for a slot, the UE expects each of the more than one DCI formats 2\_0 to indicate a same format for the slot. + +A UE does not expect to be configured to monitor PDCCH for DCI format 2\_0 on a second serving cell that uses larger SCS than the serving cell. + +**Table 11.1.1-1: Slot formats for normal cyclic prefix** + +| Format | Symbol number in a slot | | | | | | | | | | | | | | +|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|---|---|----|----|----|----| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | +| 0 | D | D | D | D | D | D | D | D | D | D | D | D | D | D | +| 1 | U | U | U | U | U | U | U | U | U | U | U | U | U | U | +| 2 | F | F | F | F | F | F | F | F | F | F | F | F | F | F | +| 3 | D | D | D | D | D | D | D | D | D | D | D | D | D | F | +| 4 | D | D | D | D | D | D | D | D | D | D | D | D | F | F | +| 5 | D | D | D | D | D | D | D | D | D | D | D | F | F | F | +| 6 | D | D | D | D | D | D | D | D | D | D | F | F | F | F | +| 7 | D | D | D | D | D | D | D | D | D | F | F | F | F | F | +| 8 | F | F | F | F | F | F | F | F | F | F | F | F | F | U | +| 9 | F | F | F | F | F | F | F | F | F | F | F | F | U | U | +| 10 | F | U | U | U | U | U | U | U | U | U | U | U | U | U | +| 11 | F | F | U | U | U | U | U | U | U | U | U | U | U | U | +| 12 | F | F | F | U | U | U | U | U | U | U | U | U | U | U | +| 13 | F | F | F | F | U | U | U | U | U | U | U | U | U | U | +| 14 | F | F | F | F | F | U | U | U | U | U | U | U | U | U | +| 15 | F | F | F | F | F | F | U | U | U | U | U | U | U | U | +| 16 | D | F | F | F | F | F | F | F | F | F | F | F | F | F | +| 17 | D | D | F | F | F | F | F | F | F | F | F | F | F | F | +| 18 | D | D | D | F | F | F | F | F | F | F | F | F | F | F | +| 19 | D | F | F | F | F | F | F | F | F | F | F | F | F | U | +| 20 | D | D | F | F | F | F | F | F | F | F | F | F | F | U | +| 21 | D | D | D | F | F | F | F | F | F | F | F | F | F | U | +| 22 | D | F | F | F | F | F | F | F | F | F | F | F | U | U | +| 23 | D | D | F | F | F | F | F | F | F | F | F | F | U | U | +| 24 | D | D | D | F | F | F | F | F | F | F | F | F | U | U | +| 25 | D | F | F | F | F | F | F | F | F | F | F | U | U | U | +| 26 | D | D | F | F | F | F | F | F | F | F | F | U | U | U | +| 27 | D | D | D | F | F | F | F | F | F | F | F | U | U | U | +| 28 | D | D | D | D | D | D | D | D | D | D | D | D | F | U | +| 29 | D | D | D | D | D | D | D | D | D | D | D | F | F | U | +| 30 | D | D | D | D | D | D | D | D | D | D | F | F | F | U | +| 31 | D | D | D | D | D | D | D | D | D | D | D | F | U | U | +| 32 | D | D | D | D | D | D | D | D | D | D | F | F | U | U | +| 33 | D | D | D | D | D | D | D | D | D | F | F | F | U | U | +| 34 | D | F | U | U | U | U | U | U | U | U | U | U | U | U | +| 35 | D | D | F | U | U | U | U | U | U | U | U | U | U | U | +| 36 | D | D | D | F | U | U | U | U | U | U | U | U | U | U | +| 37 | D | F | F | U | U | U | U | U | U | U | U | U | U | U | +| 38 | D | D | F | F | U | U | U | U | U | U | U | U | U | U | +| 39 | D | D | D | F | F | U | U | U | U | U | U | U | U | U | +| 40 | D | F | F | F | U | U | U | U | U | U | U | U | U | U | +| 41 | D | D | F | F | F | U | U | U | U | U | U | U | U | U | +| 42 | D | D | D | F | F | F | U | U | U | U | U | U | U | U | +| 43 | D | D | D | D | D | D | D | D | D | F | F | F | F | U | +| 44 | D | D | D | D | D | D | F | F | F | F | F | F | U | U | +| 45 | D | D | D | D | D | D | F | F | U | U | U | U | U | U | +| 46 | D | D | D | D | D | F | U | D | D | D | D | D | F | U | +| 47 | D | D | F | U | U | U | U | D | D | F | U | U | U | U | +| 48 | D | F | U | U | U | U | U | D | F | U | U | U | U | U | +| 49 | D | D | D | D | F | F | U | D | D | D | D | F | F | U | +| 50 | D | D | F | F | U | U | U | D | D | F | F | U | U | U | +| 51 | D | F | F | U | U | U | U | D | F | F | U | U | U | U | +| 52 | D | F | F | F | F | F | U | D | F | F | F | F | F | U | +| 53 | D | D | F | F | F | F | U | D | D | F | F | F | F | U | +| 54 | F | F | F | F | F | F | F | D | D | D | D | D | D | D | +| 55 | D | D | F | F | F | U | U | U | D | D | D | D | D | D | +| 56 – 254 | Reserved | | | | | | | | | | | | | | +| 255 | UE determines the slot format for the slot based on tdd-UL-DL-ConfigurationCommon , or tdd-UL-DL-ConfigurationDedicated and, if any, on detected DCI formats | | | | | | | | | | | | | | + +For unpaired spectrum operation for a UE on a serving cell, the UE is provided by *subcarrierSpacing* a reference SCS configuration for each slot format in a combination of slot formats indicated by an SFI-index field value in DCI format 2\_0. The UE expects that for a reference SCS configuration and for an active DL BWP or an active UL BWP with SCS configuration, it is . Each slot format in the combination of slot formats indicated by the SFI-index field value in DCI format 2\_0 is applicable to consecutive slots in the active DL BWP or the active UL BWP where the first slot starts at a same time as a first slot for the reference SCS configuration and each downlink or flexible or uplink symbol for the reference SCS configuration corresponds to $2^{(\mu - \mu_{\text{SFI}})}$ consecutive downlink or flexible or uplink symbols for the SCS configuration. + +For paired spectrum operation for a UE on a serving cell, the SFI-index field in DCI format 2\_0 indicates a combination of slot formats that includes a combination of slot formats for a reference DL BWP and a combination of slot formats for a reference UL BWP of the serving cell. The UE is provided by *subcarrierSpacing* a reference SCS configuration for the combination of slot formats indicated by the SFI-index field value in DCI format 2\_0 for the reference DL BWP of the serving cell. The UE is provided by *subcarrierSpacing2* a reference SCS configuration for the combination of slot formats indicated by the SFI-index field value in DCI format 2\_0 for the reference UL BWP of the serving cell. If and for each values provided by a value of *slotFormats*, where the value of *slotFormats* is determined by a value of *slotFormatCombinationId* in *slotFormatCombination* and the value of *slotFormatCombinationId* is set by the value of the SFI-index field value in DCI format 2\_0, the first values for the combination of slot formats are applicable to the reference DL BWP and the next value is applicable to the reference UL BWP. If and for each values provided by *slotFormats*, the first value for the combination of slot formats is applicable to the reference DL BWP and the next values are applicable to the reference UL BWP. + +The UE is provided a reference SCS configuration so that for an active DL BWP with SCS configuration, it is . The UE is provided a reference SCS configuration so that for an active UL BWP with SCS configuration, it is . Each slot format for a combination of slot formats indicated by the SFI-index field value in DCI format 2\_0 for the reference DL BWP, by indicating a value for *slotFormatCombinationId* that is mapped to a value of *slotFormats* in *slotFormatCombination*, is applicable to consecutive slots for the active DL BWP where the first slot starts at a same time as a first slot in the reference DL BWP and each downlink or flexible symbol for the reference SCS configuration corresponds to consecutive downlink or flexible symbols for the SCS configuration. Each slot format for the combination of slot formats for the reference UL BWP is applicable to consecutive slots for the active UL BWP where the first slot starts at a same time as a first slot in the reference UL BWP and each uplink or flexible symbol for the reference SCS configuration corresponds to consecutive uplink or flexible symbols for the SCS configuration. + +For unpaired spectrum operation with a second UL carrier for a UE on a serving cell, the SFI-index field value in DCI format 2\_0 indicates a combination of slot formats that includes a combination of slot formats for a reference first UL carrier of the serving cell and a combination of slot formats for a reference second UL carrier of the serving cell. The UE is provided by *subcarrierSpacing* a reference SCS configuration for the combination of slot formats indicated by the SFI-index field in DCI format 2\_0 for the reference first UL carrier of the serving cell. The UE is provided by *subcarrierSpacing2* a reference SCS configuration for the combination of slot formats indicated by the SFI-index field value in DCI format 2\_0 for the reference second UL carrier of the serving cell. For each values of *slotFormats*, the first values for the combination of slot formats are applicable to the reference first UL carrier and the next value is applicable to the reference second UL carrier. + +The UE expects to be provided a reference SCS configuration so that for an active UL BWP in the second UL carrier with SCS configuration, it is . Each slot format for a combination of slot formats indicated by the SFI-index field in DCI format 2\_0 for the reference first UL carrier is applicable to consecutive slots for the active DL BWP and the active UL BWP in the first UL carrier where the first slot starts at a same time as a first slot in the reference first UL carrier. Each slot format for the combination of slot formats for the reference second UL carrier is applicable to consecutive slots for the active UL BWP in the second UL carrier where the first slot starts at a same time as a first slot in the reference second UL carrier. + +If a BWP in the serving cell is configured with and with extended CP, the UE expects, , or . A format for a slot with extended CP is determined from a format for a slot with normal CP. A UE determines an extended CP symbol to be a downlink/uplink/flexible symbol if the overlapping normal CP symbols that are downlink/uplink/flexible symbols, respectively. A UE determines an extended CP symbol to be a flexible symbol if one of the overlapping normal CP symbols is flexible. A UE determines an extended CP symbol to be a flexible symbol if the pair of the overlapping normal CP symbols includes a downlink and an uplink symbol. + +A reference SCS configuration, or, or, or is either 0, or 1, or 2 for FR1 and is either 2 or 3 for FR2. + +For a set of symbols of a slot, a UE does not expect to detect a DCI format 2\_0 with an SFI-index field value indicating the set of symbols of the slot as uplink and to detect a DCI format indicating to the UE to receive PDSCH or CSI-RS in the set of symbols of the slot. + +For a set of symbols of a slot, a UE does not expect to detect a DCI format 2\_0 with an SFI-index field value indicating the set of symbols in the slot as downlink and to detect a DCI format, a RAR UL grant, fallbackRAR UL grant, or successRAR indicating to the UE to transmit PUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot. + +For a set of symbols of a slot that are indicated by a DCI format 2\_0 as being within a remaining channel occupancy duration either by a channel occupancy duration field or by an SFI-index field, a UE does not expect to detect at a later time a DCI format 2\_0 indicating, either by a channel occupancy duration field or by an SFI-index field, that any symbol from the set of symbols is not within a remaining channel occupancy duration. + +For a set of symbols of a slot that are indicated as downlink/uplink by *tdd-UL-DL-ConfigurationCommon*, or *tdd-UL-DL-ConfigurationDedicated*, the UE does not expect to detect a DCI format 2\_0 with an SFI-index field value indicating the set of symbols of the slot as uplink/downlink, respectively, or as flexible. + +For a set of symbols of a slot corresponding to SS/PBCH blocks with candidate SS/PBCH block indices corresponding to the SS/PBCH block indexes indicated to a UE by *ssb-PositionsInBurst* in *SIB1*, or by *ssb-PositionsInBurst* in *ServingCellConfigCommon*, as described in clause 4.1, or by *NonCellDefiningSSB* or, if the UE is not provided *dl-OrJointTCI-StateList*, by *ssb-PositionsInBurst* in *SSB-MTCAdditionalPCI* associated to physical cell ID with active TCI states for PDCCH or PDSCH, or for a set of symbols of a slot corresponding to SS/PBCH blocks configured for L1 beam measurement/reporting, the UE does not expect to detect a DCI format 2\_0 with an SFI-index field value indicating the set of symbols of the slot as uplink. + +For a set of symbols of a slot corresponding to a valid PRACH occasion and symbols before the valid PRACH occasion, as described in clause 8.1, the UE does not expect to detect a DCI format 2\_0 with an SFI-index field value indicating the set of symbols of the slot as downlink. + +For a set of symbols of a slot indicated to a UE by *pdccch-ConfigSIB1* in *MIB* for a CORESET for Type0-PDCCH CSS set, the UE does not expect to detect a DCI format 2\_0 with an SFI-index field value indicating the set of symbols of the slot as uplink. + +For a set of symbols of a slot indicated to a UE as flexible by *tdd-UL-DL-ConfigurationCommon* and *tdd-UL-DL-ConfigurationDedicated* if provided, or when *tdd-UL-DL-ConfigurationCommon* and *tdd-UL-DL-ConfigurationDedicated* are not provided to the UE, and if the UE detects a DCI format 2\_0 providing a format for the slot using a slot format value other than 255 + +- if one or more symbols from the set of symbols are symbols in a CORESET configured to the UE for PDCCH monitoring, the UE receives PDCCH in the CORESET only if an SFI-index field value in DCI format 2\_0 indicates that the one or more symbols are downlink symbols +- if an SFI-index field value in DCI format 2\_0 indicates the set of symbols of the slot as flexible and the UE detects a DCI format indicating to the UE to receive PDSCH or CSI-RS in the set of symbols of the slot, the UE receives PDSCH or CSI-RS in the set of symbols of the slot +- if an SFI-index field value in DCI format 2\_0 indicates the set of symbols of the slot as flexible and the UE detects a DCI format, a RAR UL grant, fallbackRAR UL grant, or successRAR indicating to the UE to transmit PUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot the UE transmits the PUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot +- if an SFI-index field value in DCI format 2\_0 indicates the set of symbols of the slot as flexible, and the UE does not detect a DCI format indicating to the UE to receive PDSCH or CSI-RS, or the UE does not detect a DCI format, a RAR UL grant, fallbackRAR UL grant, or successRAR indicating to the UE to transmit PUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot, the UE does not transmit or receive in the set of symbols of the slot +- if the UE is configured by higher layers to receive PDSCH or CSI-RS in the set of symbols of the slot, the UE receives the PDSCH or the CSI-RS in the set of symbols of the slot only if an SFI-index field value in DCI format 2\_0 indicates the set of symbols of the slot as downlink and, if applicable, the set of symbols is within remaining channel occupancy duration + +- if the UE is configured by higher layers to receive DL PRS in the set of symbols of the slot, the UE receives the DL PRS in the set of symbols of the slot only if an SFI-index field value in DCI format 2\_0 indicates the set of symbols of the slot as downlink or flexible. +- if the UE is configured by higher layers to transmit PUCCH, or PUSCH, or PRACH in the set of symbols of the slot, the UE transmits the PUCCH, or the PUSCH, or the PRACH in the slot only if an SFI-index field value in DCI format 2\_0 indicates the set of symbols of the slot as uplink +- if the UE is configured by higher layers to transmit SRS in the set of symbols of the slot, the UE transmits the SRS only in a subset of symbols from the set of symbols of the slot indicated as uplink symbols by an SFI-index field value in DCI format 2\_0 +- a UE does not expect to detect an SFI-index field value in DCI format 2\_0 indicating the set of symbols of the slot as downlink and also detect a DCI format, a RAR UL grant, fallbackRAR UL grant, or successRAR indicating to the UE to transmit SRS, PUSCH, PUCCH, or PRACH, in one or more symbols from the set of symbols of the slot +- a UE does not expect to detect an SFI-index field value in DCI format 2\_0 indicating the set of symbols of the slot as downlink or flexible if the set of symbols of the slot includes symbols corresponding to any repetition of a PUSCH transmission activated by an UL Type 2 grant PDCCH as described in clause 10.2 +- a UE does not expect to detect an SFI-index field value in DCI format 2\_0 indicating the set of symbols of the slot as uplink and also detect a DCI format indicating to the UE to receive PDSCH or CSI-RS in one or more symbols from the set of symbols of the slot + +If a UE is configured by higher layers to receive a CSI-RS or a PDSCH in a set of symbols of a slot and the UE detects a DCI format 2\_0 with a slot format value other than 255 that indicates a slot format with a subset of symbols from the set of symbols as uplink or flexible, or the UE detects a DCI format indicating to the UE to transmit PUSCH, PUCCH, SRS, or PRACH in at least one symbol in the set of the symbols, the UE cancels the CSI-RS reception in the set of symbols of the slot or cancels the PDSCH reception in the slot. + +For a UE operation with shared spectrum channel access in FR1, or in FR2-2 when the UE is provided *ChannelAccessMode2 = 'enabled'*, if a UE is configured by higher layers to receive a CSI-RS and the UE is provided *CO-DurationsPerCell*, for a set of symbols of a slot that are indicated as downlink or flexible by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated*, or when *tdd-UL-DL-ConfigurationCommon* and *tdd-UL-DL-ConfigurationDedicated* are not provided, the UE cancels the CSI-RS reception in the set of symbols of the slot that are not within the remaining channel occupancy duration. + +If a UE is configured by higher layers to receive a DL PRS in a set of symbols of a slot and the UE detects a DCI format 2\_0 with a slot format value other than 255 that indicates a slot format with a subset of symbols from the set of symbols as uplink, or the UE detects a DCI format indicating to the UE to transmit PUSCH, PUCCH, SRS, or PRACH in at least one symbol in the set of the symbols, the UE cancels the DL PRS reception in the set of symbols of the slot. + +If a UE is configured by higher layers to transmit SRS, or PUCCH, or PUSCH, or PRACH in a set of symbols of a slot and the UE detects a DCI format 2\_0 with a slot format value other than 255 that indicates a slot format with a subset of symbols from the set of symbols as downlink or flexible, or the UE detects a DCI format indicating to the UE to receive CSI-RS or PDSCH in a subset of symbols from the set of symbols, then + +- If the UE does not indicate the capability of [partialCancellation], the UE does not expect to cancel the transmission of the PUCCH or PUSCH or PRACH in the set of symbols if the first symbol in the set occurs within relative to a last symbol of a PDCCH reception where the UE detects the DCI format; otherwise, the UE cancels the PUCCH, or the PUSCH, or an actual repetition of the PUSCH [6, TS 38.214], determined from clauses 9, 9.2.5 and 9.2.6 or clause 6.1 of [6, TS 38.214], or the PRACH transmission in the set of symbols. +- If the UE indicates the capability of [partialCancellation], the UE does not expect to cancel the transmission of the PUCCH or PUSCH or PRACH in symbols from the set of symbols that occur within relative to a last symbol of a PDCCH reception where the UE detects the DCI format. The UE cancels the PUCCH, or the PUSCH, or an actual repetition of the PUSCH [6, TS 38.214], determined from clauses 9, 9.2.5 and 9.2.6 or clause 6.1 of [6, TS 38.214], or the PRACH transmission in remaining symbols from the set of symbols. +- The UE does not expect to cancel the transmission of SRS in symbols from the subset of symbols that occur within relative to a last symbol of a PDCCH reception where the UE detects the DCI format. The UE cancels the SRS transmission in remaining symbols from the subset of symbols. + +is the PUSCH preparation time for the corresponding UE processing capability [6, TS 38.214] assuming and corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH carrying the DCI format and the SCS configuration of the SRS, PUCCH, PUSCH or , where corresponds to the SCS configuration of the PRACH if it is 15kHz or higher; otherwise . + +If a UE is configured by higher layers to receive a CSI-RS or detects a DCI format 0\_1 indicating to the UE to receive a CSI-RS in one or more RB sets and a set of symbols of a slot, and the UE detects a DCI format 2\_0 with bitmap indicating that any RB set from the one or more RB sets is not available for reception, the UE cancels the CSI-RS reception in the set of symbols of the slot. + +A UE assumes that flexible symbols in a CORESET configured to the UE for PDCCH monitoring are downlink symbols if the UE does not detect an SFI-index field value in DCI format 2\_0 indicating the set of symbols of the slot as flexible or uplink and the UE does not detect a DCI format indicating to the UE to transmit SRS, PUSCH, PUCCH, or PRACH in the set of symbols. + +For a set of symbols of a slot that are indicated as flexible by *tdd-UL-DL-ConfigurationCommon*, and *tdd-UL-DL-ConfigurationDedicated* if provided, or when *tdd-UL-DL-ConfigurationCommon*, and *tdd-UL-DL-ConfigurationDedicated* are not provided to the UE, and if the UE does not detect a DCI format 2\_0 providing a slot format for the slot + +- the UE receives PDSCH or CSI-RS in the set of symbols of the slot if the UE receives a corresponding indication by a DCI format +- the UE transmits PUSCH, PUCCH, PRACH, or SRS in the set of symbols of the slot if the UE receives a corresponding indication by a DCI format, a RAR UL grant, fallbackRAR UL grant, or successRAR +- the UE receives PDCCH as described in clause 10.1 +- if the UE is configured by higher layers to receive PDSCH in the set of symbols of the slot, the UE does not receive the PDSCH in the set of symbols of the slot +- if the UE is configured by higher layers to receive CSI-RS in the set of symbols of the slot, the UE does not receive the CSI-RS in the set of symbols of the slot, except when UE is provided *CO-DurationsPerCell* and the set of symbols of the slot are within the remaining channel occupancy duration. +- if the UE is configured by higher layers to receive DL PRS in the set of symbols of the slot, the UE receives the DL PRS +- if the UE is configured by higher layers to transmit SRS, or PUCCH, or PUSCH, or PRACH in the set of symbols of the slot and the UE is not provided *enableConfiguredUL*, then + - if the UE does not indicate the capability of [partialCancellation], the UE does not expect to cancel the transmission of the PUCCH, or the PUSCH, or an actual repetition of the PUSCH [6, TS 38.214], as determined in clauses 9, 9.2.5 and 9.2.6 or in clause 6.1 of [6, TS 38.214], or the PRACH in the slot if the first symbol of the PUCCH or the PUSCH or actual repetition of the PUSCH or the PRACH in the slot occurs within relative to a last symbol of a PDCCH reception where the UE is configured to monitor PDCCH for DCI format 2\_0; otherwise, the UE cancels the PUCCH, or the PUSCH, or an actual repetition of the PUSCH [6, TS 38.214], as determined in clauses 9, 9.2.5 and 9.2.6 or in clause 6.1 of [6, TS 38.214], or the PRACH in the slot; + - if the UE indicates the capability of [partialCancellation], the UE does not expect to cancel the transmission of the PUCCH, or the PUSCH, or an actual repetition of the PUSCH [6, TS 38.214], as determined in clauses 9, 9.2.5 and 9.2.6 or in clause 6.1 of [6, TS 38.214], or the PRACH in symbols from the set of symbols that occur within relative to a last symbol of a PDCCH reception where the UE is configured to monitor PDCCH for DCI format 2\_0. The UE cancels the PUCCH, or the PUSCH, or an actual repetition of the PUSCH [6, TS 38.214], as determined in clauses 9, 9.2.5 and 9.2.6 or in clause 6.1 of [6, TS 38.214], or the PRACH transmission in remaining symbols from the set of symbols; + - the UE does not expect to cancel the transmission of SRS in symbols from the set of symbols that occur within relative to a last symbol of a PDCCH reception where the UE is configured to monitor PDCCH for DCI format 2\_0. The UE cancels the SRS transmission in remaining symbols from the set of symbols; + - is the PUSCH preparation time for the corresponding UE processing capability [6, TS 38.214] assuming and corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH carrying the + +DCI format 2\_0 and the SCS configuration of the SRS, PUCCH, PUSCH or , where corresponds to the SCS configuration of the PRACH if it is 15kHz or higher; otherwise ; + +- if the UE is configured by higher layers to transmit SRS, or PUCCH, or PUSCH, or PRACH in the set of symbols of the slot and the UE is provided *enableConfiguredUL*, the UE can transmit the SRS, or PUCCH, or PUSCH, or PRACH, respectively. + +For unpaired spectrum operation for a UE on a cell in a frequency band of FR1, and when the scheduling restrictions due to RRM measurements [10, TS 38.133] are not applicable, if the UE detects a DCI format indicating to the UE to transmit in a set of symbols, the UE is not required to perform RRM measurements [10, TS 38.133] based on a SS/PBCH block or CSI-RS reception on a different cell in the frequency band if the SS/PBCH block or CSI-RS reception includes at least one symbol from the set of symbols. + +## 11.2 Interrupted transmission indication + +If a UE is provided *DownlinkPreemption*, the UE is configured with an INT-RNTI provided by *int-RNTI* for monitoring PDCCH conveying DCI format 2\_1 [5, TS 38.212]. The UE is additionally configured with + +- a set of serving cells by *int-ConfigurationPerServingCell* that includes a set of serving cell indexes provided by corresponding *servingCellId* and a corresponding set of locations for fields in DCI format 2\_1 by *positionInDCI* +- an information payload size for DCI format 2\_1 by *dci-PayloadSize* +- an indication granularity for time-frequency resources by *timeFrequencySet* + +If a UE detects a DCI format 2\_1 for a serving cell from the configured set of serving cells, the UE may assume that no transmission to the UE is present in PRBs and in symbols that are indicated by the DCI format 2\_1, from a set of PRBs and a set of symbols of the last monitoring period. The indication by the DCI format 2\_1 is not applicable to receptions of SS/PBCH blocks. + +The set of PRBs is equal to the active DL BWP as defined in clause 12 and includes $B_{\text{INT}}$ PRBs. + +If a UE detects a DCI format 2\_1 in a PDCCH reception in a slot, the set of symbols is the last $N_{\text{symb}}^{\text{slot}} \cdot T_{\text{INT}} \cdot 2^{\mu - \mu_{\text{INT}}}$ symbols prior to the first symbol of the PDCCH reception in the slot where $T_{\text{INT}}$ is the PDCCH monitoring periodicity provided by the value of *monitoringSlotPeriodicityAndOffset*, as described in clause 10.1, $N_{\text{symb}}^{\text{slot}}$ is the number of symbols per slot, $\mu$ is the SCS configuration for a serving cell with mapping to a respective field in the DCI format 2\_1, $\mu_{\text{INT}}$ is the SCS configuration of the DL BWP where the UE receives the PDCCH with the DCI format 2\_1. If the UE is provided *tdd-UL-DL-ConfigurationCommon*, symbols indicated as uplink by *tdd-UL-DL-ConfigurationCommon* are excluded from the last $N_{\text{symb}}^{\text{slot}} \cdot T_{\text{INT}} \cdot 2^{\mu - \mu_{\text{INT}}}$ symbols prior to the first symbol of the PDCCH reception in the slot. The resulting set of symbols includes a number of symbols that is denoted as $N_{\text{INT}}$ . + +The UE does not expect to be provided values of $\mu$ , $\mu_{\text{INT}}$ , and $T_{\text{INT}}$ resulting to a value of $N_{\text{symb}}^{\text{slot}} \cdot T_{\text{INT}} \cdot 2^{\mu - \mu_{\text{INT}}}$ that is not an integer. The UE does not expect to be configured by *monitoringSymbolsWithinSlot* with more than one PDCCH monitoring occasion for DCI format 2\_1 in a slot. + +A UE is provided the indication granularity for the set of PRBs and for the set of symbols by *timeFrequencySet*. + +If the value of *timeFrequencySet* is 'set0', 14 bits from MSB of a field in DCI format 2\_1 have a one-to-one mapping with 14 groups of consecutive symbols from the set of symbols where each of the first $N_{\text{INT}} - \lfloor N_{\text{INT}}/14 \rfloor \cdot 14$ symbol groups includes $\lfloor N_{\text{INT}}/14 \rfloor$ symbols, each of the last $14 - N_{\text{INT}} + \lfloor N_{\text{INT}}/14 \rfloor \cdot 14$ symbol groups includes $\lceil N_{\text{INT}}/14 \rceil$ symbols, a bit value of 0 indicates transmission to the UE in the corresponding symbol group and a bit value of 1 indicates no transmission to the UE in the corresponding symbol group. + +If the value of *timeFrequencySet* is 'set1', 7 pairs of bits from MSB of a field in the DCI format 2\_1 have a one-to-one mapping with 7 groups of consecutive symbols where each of the first $N_{\text{INT}} - \lfloor N_{\text{INT}}/7 \rfloor \cdot 7$ symbol groups includes $\lfloor N_{\text{INT}}/7 \rfloor$ symbols, each of the last $7 - N_{\text{INT}} + \lfloor N_{\text{INT}}/7 \rfloor \cdot 7$ symbol groups includes $\lceil N_{\text{INT}}/7 \rceil$ symbols, a first bit in a + +pair of bits for a symbol group is applicable to the subset of first $\lfloor B_{\text{INT}}/2 \rfloor$ PRBs from the set of $B_{\text{INT}}$ PRBs, a second bit in the pair of bits for the symbol group is applicable to the subset of last $\lfloor B_{\text{INT}}/2 \rfloor$ PRBs from the set of $B_{\text{INT}}$ PRBs, a bit value of 0 indicates transmission to the UE in the corresponding symbol group and subset of PRBs, and a bit value of 1 indicates no transmission to the UE in the corresponding symbol group and subset of PRBs. + +## 11.2A Cancellation indication + +If a UE is provided *UplinkCancellation*, the UE is provided, in one or more serving cells, search space sets for monitoring the first PDCCH candidate with a CCE aggregation level of CCEs of each search space set for detection of a DCI format 2\_4 [5, TS 38.212] with a CI-RNTI provided by *ci-RNTI* as described in clause 10.1. *UplinkCancellation* additionally provides to the UE + +- a set of serving cells, by *ci-ConfigurationPerServingCell*, that includes a set of serving cell indexes and a corresponding set of locations for fields in DCI format 2\_4 by *positionInDCI* +- a number of fields in DCI format 2\_4, by *positionInDCI-forSUL*, for each serving cell for a SUL carrier, if the serving cell is configured with a SUL carrier +- an information payload size for DCI format 2\_4 by *dci-PayloadSize-ForCI* +- an indication for time-frequency resources by *timeFrequencyRegion* + +For a serving cell having an associated field in a DCI format 2\_4, for the field denote by + +- a number of bits provided by *ci-PayloadSize* +- a number of PRBs provided by *frequencyRegionforCI* in *timeFrequencyRegion* +- a number of symbols, excluding symbols for reception of SS/PBCH blocks and DL symbols indicated by *tdd-UL-DL-ConfigurationCommon*, from a number of symbols that + - is provided by *timeDurationforCI* in *timeFrequencyRegion*, if the PDCCH monitoring periodicity for the search space set with the DCI format 2\_4 is one slot and there are more than one PDCCH monitoring occasions in a slot, or + - is equal to the PDCCH monitoring periodicity, otherwise. +- a number of partitions for the symbols provided by *timeGranularityforCI* in *timeFrequencyRegion* + +sets of bits from the MSB of the bits have a one-to-one mapping with groups of symbols where each of the first groups includes symbols and each of the remaining groups includes symbols. A UE determines a symbol duration with respect to a SCS configuration of an active DL BWP where the UE monitors PDCCH for DCI format 2\_4 detection. + +For a group of symbols, bits from MSB of each set of bits have a one-to-one mapping with groups of PRBs where each of the first groups includes PRBs and each of the remaining groups includes PRBs. A UE determines a first PRB index as and a number of contiguous RBs as from *frequencyRegionforCI* that indicates an offset and a length as RIV according to [6, TS 38.214], and from *offsetToCarrier* in *FrequencyInfoUL-SIB* or *FrequencyInfoUL* that indicates for a SCS configuration of an active DL BWP where the UE monitors PDCCH for DCI format 2\_4 detection. + +An indication by a DCI format 2\_4 for a serving cell is applicable to a PUSCH transmission or an SRS transmission on the serving cell. If the PUSCH transmission or the SRS transmission is scheduled by a DCI format, the indication by the DCI format 2\_4 is applicable to the PUSCH transmission or SRS transmission only if the last symbol of the PDCCH reception providing the DCI format is earlier than the first symbol of the PDCCH reception providing the DCI format 2\_4. + +For the serving cell, the UE determines the first symbol of the symbols to be the first symbol that is after from the end of a PDCCH reception where the UE detects the DCI format 2\_4, where is obtained from for PUSCH processing capability 2 [6, TS 38.214] assuming where is provided by *delta\_Offset*, being the smallest SCS configuration between the SCS configuration of the PDCCH and the smallest SCS configuration provided in *scs-SpecificCarrierList* of *FrequencyInfoUL* or *FrequencyInfoUL-SIB*. The UE does not expect to cancel the PUSCH transmission or the SRS transmission before a corresponding symbol that is assuming that after a last symbol of the PDCCH reception where the UE detects the DCI format 2\_4. + +A UE that detects a DCI format 2\_4 for a serving cell cancels a PUSCH transmission or an actual repetition of a PUSCH transmission [6, TS 38.214] if the PUSCH transmission is with repetition Type B, as determined in clauses 9 and 9.2.5 or in clause 6.1 of [6, TS 38.214], or an SRS transmission on the serving cell if, respectively, + +- the transmission is PUSCH with priority 0, if the UE is provided *uplinkCancellationPriority*, +- a group of symbols, from the symbols, has at least one bit value of '1' in the corresponding set of bits in the DCI format 2\_4 and includes a symbol of the (repetition of the) PUSCH transmission or of the SRS transmission, and +- a group of PRBs, from the PRBs, has a corresponding bit value of '1' in the set of bits corresponding to the group of symbols in the DCI format 2\_4 and includes a PRB of the (repetition of the) PUSCH transmission or of the SRS transmission, + +where + +- the cancellation of the (repetition of the) PUSCH transmission includes all symbols from the earliest symbol of the (repetition of the) PUSCH transmission that is in a group of symbols having corresponding bit values of '1' in the DCI format 2\_4; +- the cancellation of the SRS transmission includes only symbols that are in one or more groups of symbols having corresponding bit values of '1' in the DCI format 2\_4. + +If, based on an indication by a DCI format 2\_4, a UE cancels a PUSCH transmission or an SRS transmission, the UE does not expect to be scheduled by a second DCI format to transmit a PUSCH or an SRS over symbols that include symbols of the cancelled PUSCH transmission or SRS transmission, where the last symbol of the PDCCH reception providing the second DCI format is no earlier than the first symbol of the PDCCH reception providing the DCI format 2\_4. + +## 11.3 Group TPC commands for PUCCH/PUSCH + +For PUCCH transmission on a serving cell, a UE can be provided + +- a TPC-PUCCH-RNTI for a DCI format 2\_2 by *tpc-PUCCH-RNTI* + - a field in DCI format 2\_2 is a TPC command of 2 bits mapping to values as described in clause 7.2.1 +- an index for a location in DCI format 2\_2 of a first bit for a TPC command field for the PCell, or for a carrier of the PCell by *tpc-IndexPCell* +- an index for a location in DCI format 2\_2 of a first bit for a TPC command field for a PUCCH-sSCell in the primary PUCCH cell group, by *tpc-IndexPUCCH-sScell* +- an index for a location in DCI format 2\_2 of a first bit for a TPC command field for the PUCCH-SCell or for a carrier for the PUCCH-SCell by *tpc-IndexPUCCH-Scell* +- an index for a location in DCI format 2\_2 of a first bit for a TPC command field for a PUCCH-sSCell in the secondary PUCCH cell group, by *tpc-IndexPUCCH-sScellSecondaryPUCCHgroup* +- a mapping for the PUCCH power control adjustment state, by a corresponding {0, 1} value of a closed loop index field that is appended to the TPC command field in DCI format 2\_2 if the UE indicates a capability to support two PUCCH power control adjustment states by *twoDifferentTPC-Loop-PUCCH*, and if the UE is configured for two PUCCH power control adjustment states by *twoPUCCH-PC-AdjustmentStates* + +The UE is also provided on a serving cell with a configuration for a search space set and a corresponding CORESET for monitoring PDCCH candidates for DCI format 2\_2 with CRC scrambled by a TPC-PUCCH-RNTI as described in clause 10.1. + +For PUSCH transmission on a serving cell, a UE can be provided + +- a TPC-PUSCH-RNTI for a DCI format 2\_2 by *tpc-PUSCH-RNTI* + - a field in DCI format 2\_2 is a TPC command of 2 bits mapping to values as described in clause 7.1.1 +- an index for a location in DCI format 2\_2 of a first bit for a TPC command field for an uplink carrier of the serving cell by *tpc-Index* + +- an index for a location in DCI format 2\_2 of a first bit for a TPC command field for a supplementary uplink carrier of the serving cell by *tpc-IndexSUL* +- an index of the serving cell by *targetCell*. If *targetCell* is not provided, the serving cell is the cell of the PDCCH reception for DCI format 2\_2 +- a mapping for the PUSCH power control adjustment state, by a corresponding {0, 1} value of a closed loop index field that is appended to the TPC command field for the uplink carrier or for the supplementary uplink carrier of the serving cell in DCI format 2\_2 if the UE indicates a capability to support two PUSCH power control adjustment states, by *twoDifferentTPC-Loop-PUSCH*, and if the UE is configured for two PUSCH power control adjustment states by *twoPUSCH-PC-AdjustmentStates* + +The UE is also provided for the serving cell of the PDCCH reception for DCI format 2\_2 with a configuration for a search space set and a corresponding CORESET for monitoring PDCCH candidates for DCI format 2\_2 with CRC scrambled by a TPC-PUSCH-RNTI as described in clause 10.1. + +## 11.4 SRS switching + +DCI format 2\_3 is applicable for uplink carrier(s) of serving cells where a UE is not configured for PUSCH/PUCCH transmission or for uplink carrier(s) of a serving cell where *srs-PowerControlAdjustmentStates* indicates a separate power control adjustment state between SRS transmissions and PUSCH transmissions. + +A UE configured by higher layers with parameter *carrierSwitching* can be provided + +- a TPC-SRS-RNTI for a DCI format 2\_3 by *tpc-SRS-RNTI* +- an index of a serving cell where the UE interrupts transmission in order to transmit SRS on one or more other serving cells by *srs-SwitchFromServCellIndex* +- an indication of an uplink carrier where the UE interrupts transmission in order to transmit SRS on one or more other serving cells by *srs-SwitchFromCarrier* +- a DCI format 2\_3 field configuration type by *typeA* or *typeB* + - for *typeA*, an index for a set of serving cells is provided by *cc-SetIndex*, indexes of serving cells in the set of serving cells are provided by *cc-IndexInOneCC-Set*, and a DCI format 2\_3 field includes a TPC command for each serving cell from the set of serving cells and can also include a SRS request for SRS transmission on the set of serving cells + - for *typeB*, DCI format 2\_3 field includes a TPC command for a serving cell index and can also include a SRS request for SRS transmission on the serving cell +- an indication for a serving cell for whether or not a field in DCI format 2\_3 includes a SRS request by *fieldTypeFormat2-3* where a value of 0/1 indicates absence/presence of the SRS request – a mapping for a 2 bit SRS request to SRS resource sets is as provided in [6, TS 38.214] +- an index for a location in DCI format 2\_3 of a first bit for a field for a non-supplementary uplink carrier of the serving cell by *startingBitOfFormat2-3* +- an index for a location in DCI format 2\_3 of a first bit for a field for a supplementary uplink carrier of the serving cell by *startingBitOfFormat2-3SUL-v1530* + +## 11.5 Adaptation of cell operation + +A UE configured for operation on a serving cell according to one or both of a cell DTX operation and a cell DRX operation by *cellDTXDRX-Config* for the serving cell [11, TS 38.321], can be additionally provided by *dci-Format2-9* a Type3-PDCCH CSS set to monitor PDCCH for detection of DCI format 2\_9 as described in clause 10.1 during Active Time [11, TS 38.321], and a location in DCI format 2\_9 by *positionInDCI-cellDTX* of a cell DTX/DRX indication field for the serving cell and/or a NES-mode indication field for the PCell + +- if the UE is configured with both cell DTX operation and cell DRX operation for the serving cell and if *cellDTXDRX-L1activation* is provided, the cell DTX/DRX indication field includes two bits where the first bit indicates the cell DTX operation and the second bit indicates the cell DRX operation + +- if the UE is configured with only one of the cell DTX operation and cell DRX operation for the serving cell and if *cellDTXDRX-L1activation* is provided, the cell DTX/DRX indication field includes one bit indicating one of the cell DTX operation and cell DRX operation, respectively, for the serving cell +- a '0' value for a bit of the cell DTX/DRX indication field indicates deactivation of cell DTX or of cell DRX +- a '1' value for a bit of the cell DTX/DRX indication field indicates activation of cell DTX or of cell DRX +- if the serving cell is configured with a SUL carrier, the cell DTX/DRX indication field indication for activation or deactivation of cell DRX applies to both the UL carrier and the SUL carrier +- if *nesEvent* is configured, the NES-mode indication field includes one bit indicating NES-specific CHO execution condition, as described in [12, TS 38.331] + - a '0' value for the NES-mode indication field indicates NES-specific CHO execution condition is disabled + - a '1' value for the NES-mode indication field, indicates NES-specific CHO execution condition is enabled + +A UE does not expect to monitor PDCCH for detection of DCI format 2\_9 on more than one serving cells of one cell group. + +When a UE receives in slot on the active DL BWP of a first serving cell a PDCCH providing DCI format 2\_9 that indicates a change in activation or deactivation of a current cell DTX operation or cell DRX operation for a second serving cell, the UE operates on the second serving cell according to the indicated cell DTX operation or cell DRX operation starting from a slot on the active DL BWP or on the active UL BWP of the second serving cell, respectively, that is not before the beginning of the slot on the active DL BWP of the first serving cell where is a number of slots for the SCS of the active DL BWP of the first serving cell in Table 11.5-1. + +**Table 11.5-1: Minimum time gap value** + +| SCS (kHz) | Number of slots | +|-----------|-----------------| +| 15 | 3 | +| 30 | 6 | +| 60 | 12 | +| 120 | 24 | +| 480 | 96 | +| 960 | 192 | + +# 12 Bandwidth part operation + +If the UE is configured with a SCG, the UE shall apply the procedures described in this clause for both MCG and SCG + +- When the procedures are applied for MCG, the terms 'secondary cell', 'secondary cells', 'serving cell', 'serving cells' in this clause refer to secondary cell, secondary cells, serving cell, serving cells belonging to the MCG respectively. +- When the procedures are applied for SCG, the terms 'secondary cell', 'secondary cells', 'serving cell', 'serving cells' in this clause refer to secondary cell, secondary cells (not including PSCell), serving cell, serving cells belonging to the SCG respectively. The term 'primary cell' in this clause refers to the PSCell of the SCG. + +A UE configured for operation in bandwidth parts (BWPs) of a serving cell, is configured by higher layers for the serving cell a set of at most four bandwidth parts (BWPs) for receptions by the UE (DL BWP set) in a DL bandwidth by parameter *BWP-Downlink* or by parameter *initialDownlinkBWP* with a set of parameters configured by *BWP-DownlinkCommon* and *BWP-DownlinkDedicated*, and a set of at most four BWPs for transmissions by the UE (UL BWP set) in an UL bandwidth by parameter *BWP-Uplink* or by parameter *initialUplinkBWP* with a set of parameters configured by *BWP-UplinkCommon* and *BWP-UplinkDedicated*. + +For operation with shared spectrum channel access, a UE expects that the BWP configured by the parameter *initialUplinkBWP* provided in *UplinkConfigCommonSIB* is mapped to only a single RB set. + +If a UE is not provided *initialDownlinkBWP*, an initial DL BWP is defined by a location and number of contiguous PRBs, starting from a PRB with the lowest index and ending at a PRB with the highest index among PRBs of a + +CORESET for Type0-PDCCH CSS set, after puncturing if any [4, TS 38.211], and a SCS and a cyclic prefix for PDCCH reception in the CORESET for Type0-PDCCH CSS set; otherwise, the initial DL BWP is provided by *initialDownlinkBWP*. For operation on the primary cell or on a secondary cell, a UE is provided an initial UL BWP by *initialUplinkBWP*. If the UE is configured with a supplementary UL carrier, the UE can be provided an initial UL BWP on the supplementary UL carrier by *initialUplinkBWP*. + +If a UE has dedicated BWP configuration, the UE can be provided by *firstActiveDownlinkBWP-Id* a first active DL BWP for receptions and by *firstActiveUplinkBWP-Id* a first active UL BWP for transmissions on a carrier of the primary cell. + +For each DL BWP or UL BWP in a set of DL BWPs or UL BWPs, respectively, the UE is provided the following parameters for the serving cell as defined in [4, TS 38.211] or [6, TS 38.214]: + +- a SCS by *subcarrierSpacing* +- a cyclic prefix by *cyclicPrefix* +- a common RB and a number of contiguous RBs provided by *locationAndBandwidth* that indicates an offset and a length as RIV according to [6, TS 38.214], setting , and a value provided by *offsetToCarrier* for the *subcarrierSpacing* +- an index in the set of DL BWPs or UL BWPs by respective *BWP-Id* +- a set of BWP-common and a set of BWP-dedicated parameters by *BWP-DownlinkCommon* and *BWP-DownlinkDedicated* for the DL BWP, or *BWP-UplinkCommon* and *BWP-UplinkDedicated* for the UL BWP [12, TS 38.331] + +For unpaired spectrum operation, a DL BWP from the set of configured DL BWPs with index provided by *BWP-Id* is linked with an UL BWP from the set of configured UL BWPs with index provided by *BWP-Id* when the DL BWP index and the UL BWP index are same. For unpaired spectrum operation, a UE does not expect to receive a configuration where the center frequency for a DL BWP is different than the center frequency for an UL BWP when the *BWP-Id* of the DL BWP is same as the *BWP-Id* of the UL BWP. + +For each DL BWP in a set of DL BWPs of the PCell, a UE can be configured CORESETs for every type of CSS sets and for USS as described in clause 10.1. The UE does not expect to be configured without a CSS set on the PCell in the active DL BWP. + +If a UE is provided *controlResourceSetZero* and *searchSpaceZero* in *PDCCH-ConfigSIB1* or *PDCCH-ConfigCommon*, the UE determines a CORESET for a search space set from *controlResourceSetZero* as described in clause 13 and for Tables 13-0 through 13-10, and determines corresponding PDCCH monitoring occasions as described in clause 13 and for Tables 13-11 through 13-15. If the active DL BWP is not the initial DL BWP, the UE determines PDCCH monitoring occasions for the search space set only if the CORESET bandwidth is within the active DL BWP and the active DL BWP has same SCS configuration and same cyclic prefix as the initial DL BWP. + +For each UL BWP in a set of UL BWPs of the PCell, or of the PUCCH-SCell, or of the PUCCH-sSCell the UE is configured resource sets for PUCCH transmissions as described in clause 9.2.1. + +A UE receives PDCCH and PDSCH in a DL BWP according to a configured SCS and CP length for the DL BWP. A UE transmits PUCCH and PUSCH in an UL BWP according to a configured SCS and CP length for the UL BWP. + +If a bandwidth part indicator field is configured in a DCI format, the bandwidth part indicator field value indicates the active DL BWP, from the configured DL BWP set, for DL receptions as described in [5, TS 38.212]. If a bandwidth part indicator field is configured in a DCI format, the bandwidth part indicator field value indicates the active UL BWP, from the configured UL BWP set, for UL transmissions as described in [5, TS 38.212]. + +If a bandwidth part indicator field is provided by a DCI format 0\_3/1\_3, + +- the UE applies for a serving cell the value of the bandwidth part indicator field, if + - the UE is scheduled by the DCI format 0\_3/1\_3 to transmit PUSCH/receive PDSCH, respectively, on the serving cell, and + - the serving cell includes a configured UL/DL BWP with index corresponding to the value of the bandwidth part indicator field + +- otherwise, the UE does not apply for the serving cell the value of the bandwidth part indicator field. + +If a bandwidth part indicator field is configured in a DCI format and indicates an UL BWP or a DL BWP different from the active UL BWP or DL BWP, respectively, the UE shall + +- for each information field in the DCI format + - if the size of the information field is smaller than the one required for the DCI format interpretation for the UL BWP or DL BWP that is indicated by the bandwidth part indicator, the UE prepends zeros to the information field until its size is the one required for the interpretation of the information field for the UL BWP or DL BWP prior to interpreting the DCI format information fields, respectively + - if the size of the information field is larger than the one required for the DCI format interpretation for the UL BWP or DL BWP that is indicated by the bandwidth part indicator, the UE uses a number of least significant bits of the DCI format equal to the one required for the UL BWP or DL BWP indicated by bandwidth part indicator prior to interpreting the DCI format information fields, respectively + - for a DCI format 0\_3, or for a DCI format 1\_3, and for an information field that includes a number of blocks [5, TS 38.212], the above procedures apply separately for each block of the information field +- set the active UL BWP or DL BWP to the UL BWP or DL BWP indicated by the bandwidth part indicator in the DCI format + +If a bandwidth part indicator field is configured in a DCI format 0\_1/0\_3 and indicates an active UL BWP with different SCS configuration, or with different number of RB sets for a serving cell, than a current active UL BWP for the serving cell, the UE determines an uplink frequency domain resource allocation Type 2 for the serving cell based on bits and bits that are generated by independently truncating or padding the MSBs and the LSBs [6, TS 38.214] of the frequency domain resource assignment field of DCI format 0\_1, or the block of the frequency domain resource assignment field in DCI format 0\_3 corresponding to the serving cell, where truncation starts from the MSBs of the X bits or the Y bits, zero-padding prepends zeros to the X bits or the Y bits, and + +- if the indicated active UL BWP for the serving cell has SCS configuration and the current active BWP for the serving cell has SCS configuration, the MSBs are truncated to bits, or +- if the indicated active UL BWP for the serving cell has SCS configuration and the current active BWP for the serving cell has SCS configuration, the MSBs are zero-padded to bits +- otherwise, the MSBs are unchanged + +and + +- the LSBs are truncated or zero-padded to bits where is a number of RB sets configured for the indicated active UL BWP for the serving cell. + +A UE does not expect to detect a DCI format with a BWP indicator field that indicates an active DL BWP or an active UL BWP change with the corresponding time domain resource assignment field providing a slot offset value for a PDSCH reception or PUSCH transmission that is smaller than a delay required by the UE for an active DL BWP change or UL BWP change, respectively [10, TS 38.133]. + +If a UE detects a DCI format with a BWP indicator field that indicates an active DL BWP change for a cell, the UE is not required to receive or transmit in the cell during a time duration from the end of the third symbol of a slot where the UE receives the PDCCH that includes the DCI format in a scheduling cell until the beginning of a slot indicated by the slot offset value of the time domain resource assignment field in the DCI format. + +If a UE detects a DCI format with SCell dormancy indication that indicates an active DL BWP change for an SCell in slot $n$ of primary cell, the UE is not required to receive or transmit in the SCell during a time duration specified in [10, TS 38.133]. + +If a UE detects a DCI format indicating an active UL BWP change for a cell, the UE is not required to receive or transmit in the cell during a time duration from the end of the third symbol of a slot where the UE receives the PDCCH that includes the DCI format in the scheduling cell until the beginning of a slot indicated by the slot offset value of the time domain resource assignment field in the DCI format. + +A UE does not expect to detect a DCI format indicating an active DL BWP change or an active UL BWP change for a scheduled cell within FR1 (or FR2) in a slot other than the first slot of a set of slots for the DL SCS of the scheduling + +cell that overlaps with a time duration where the UE is not required to receive or transmit, respectively, for an active BWP change in a different cell from the scheduled cell within FR1 (or FR2). + +A UE expects to detect a DCI format with a BWP indicator field that indicates an active UL BWP change or an active DL BWP change only if a corresponding PDCCH is received within the first 3 symbols of a slot. If the UE detects the DCI format from two PDCCH receptions in search space sets and that include *searchSpaceLinkingId* with same value, as described in clause 10.1, the UE considers the PDCCH reception where the UE detects the DCI format to be the one from the two PDCCH receptions that ends later. + +For a serving cell, a UE can be provided by *defaultDownlinkBWP-Id* a default DL BWP among the configured DL BWPs. If a UE is not provided a default DL BWP by *defaultDownlinkBWP-Id*, the default DL BWP is the initial DL BWP. + +If a UE is provided by *bwp-InactivityTimer* a timer value for the serving cell [11, TS 38.321] and the timer is running, the UE decrements the timer at the end of a subframe for FR1 or at the end of a half subframe for FR2 if the restarting conditions in [11, TS 38.321] are not met during the interval of the subframe for FR1 or of the half subframe for FR2. + +For a cell where a UE changes an active DL BWP due to a BWP inactivity timer expiration and for accommodating a delay in the active DL BWP change or the active UL BWP change required by the UE [10, TS 38.133], the UE is not required to receive or transmit in the cell during a time duration from the beginning of a subframe for FR1, or of half of a subframe for FR2, that is immediately after the BWP inactivity timer expires until the beginning of a slot where the UE can receive or transmit. + +When a UE's BWP inactivity timer for a cell within FR1 (or FR2) expires within a time duration where the UE is not required to receive or transmit for an active UL/DL BWP change in the cell or in a different cell within FR1 (or FR2), the UE delays the active UL/DL BWP change triggered by the BWP inactivity timer expiration until a subframe for FR1 or half a subframe for FR2 that is immediately after the UE completes the active UL/DL BWP change in the cell or in the different cell within FR1 (or FR2). + +If a UE is provided by *firstActiveDownlinkBWP-Id* a first active DL BWP and by *firstActiveUplinkBWP-Id* a first active UL BWP on a carrier of a secondary cell, the UE uses the indicated DL BWP and the indicated UL BWP as the respective first active DL BWP on the secondary cell and first active UL BWP on the carrier of the secondary cell. + +If a UE is provided *NonCellDefiningSSB* in *BWP-DownlinkDedicated* for an active DL BWP, the UE assumes that the active DL BWP includes the SS/PBCH blocks provided by *NonCellDefiningSSB*. The SS/PBCH blocks provided by *NonCellDefiningSSB* and the SS/PBCH blocks that the UE used to obtain SIB1 have same QCL properties if they have a same index. Unless otherwise stated, handling of overlapping between downlink receptions or uplink transmissions and the SS/PBCH blocks provided by *NonCellDefiningSSB* is same as handling of overlapping between downlink receptions or uplink transmissions and the SS/PBCH blocks provided by *ssb-PositionsInBurst* in *SIB1* or in *ServingCellConfigCommon*. + +A UE does not expect to monitor PDCCH when the UE performs RRM measurements [10, TS 38.133] over a bandwidth that is not within the active DL BWP for the UE. + +# 13 UE procedure for monitoring Type0-PDCCH CSS sets + +If during cell search a UE determines from *MIB* that a CORESET for Type0-PDCCH CSS set is present, as described in clause 4.1, the UE determines a number of consecutive resource blocks and a number of consecutive symbols for the CORESET of the Type0-PDCCH CSS set from *controlResourceSetZero* in *pdcch-ConfigSIB1*, as described in Tables 13-0 through 13-10, for operation without shared spectrum channel access in FR1 and FR2-1, or as described in Tables 13-1A and 13-4A for operation with shared spectrum channel access in FR1, or as described in Table 13-10A for FR2-2, and determines PDCCH monitoring occasions from *searchSpaceZero* in *pdcch-ConfigSIB1*, included in *MIB*, as described in Tables 13-11 through 13-15A. *nsf* and *nslot* are the SFN and slot index within a frame of the CORESET based on SCS of the CORESET and *nsf* and *nslot* are the SFN and slot index based on SCS of the CORESET, respectively, where the SS/PBCH block with index *nssb* overlaps in time with system frame *nsf* and slot *nslot*. The symbols of the CORESET associated with *pdcch-ConfigSIB1* in *MIB* or with *searchSpaceSIB1* in *PDCCH-ConfigCommon* have normal cyclic prefix. In Table 13-0, configurations with index 0 to 9 are applicable when an associated SS/PBCH block is located according to Table 5.4.3.3-2 in [8-1, TS 38.101-1], configurations with index 10 to 11 are applicable when an associated SS/PBCH block is located according to NOTE 12 of Table 5.4.3.3-1 in [8-1, TS 38.101-1], and non-interleaved CCE-to-REG + +mapping applies for configurations with index 6 to 9. In Table 13-1, the associated SS/PBCH block is not located according to NOTE 12 of Table 5.4.3.3-1 in [8-1, TS 38.101-1]. + +For operation with shared spectrum channel access in FR2-2 and for operation without shared spectrum channel access, a UE assumes that the offset in Tables 13-0 through 13-10A is defined with respect to the SCS of the CORESET for Type0-PDCCH CSS set from the smallest RB index of the CORESET for Type0-PDCCH CSS set to the smallest RB index of the common RB overlapping with the first RB of the corresponding SS/PBCH block, after puncturing if any [4, TS 38.211]. The SCS of the CORESET for Type0-PDCCH CSS set is provided by *subCarrierSpacingCommon* for FR1 and FR2-1 and same as the SCS of the corresponding SS/PBCH block for FR2-2. In Tables 13-7, 13-8, and 13-10, is defined in [4, TS 38.211]. + +For operation with shared spectrum channel access in FR1, a UE determines an offset from a smallest RB index of the CORESET for Type0-PDCCH CSS set to a smallest RB index of the common RB overlapping with a first RB of the corresponding SS/PBCH block + +- according to the offset in Table 13-1A or Table 13-4A, if the frequency position of the SS/PBCH block corresponds to the GSCN of a synchronization raster entry as defined in [8-1, TS 38.101-1], and +- according to a sum of a first offset and a second offset if the frequency position of the SS/PBCH block is provided by *ssbFrequency* in a measurement configuration associated with a reporting configuration providing *reportCGI* and does not correspond to the GSCN of a synchronization raster entry as defined in [8-1, TS 38.101-1], where + - the first offset is provided in Table 13-1A or Table 13-4A, and + - the second offset is determined as the offset from a smallest RB index of the common RB overlapping with the first RB of the SS/PBCH block indicated in the measurement configuration to a smallest RB index of the common RB overlapping with the first RB of a SS/PBCH block hypothetically located at the GSCN of a synchronization raster entry, where the single synchronization raster entry is located in the same channel as the SS/PBCH block used for the shared spectrum channel access procedure, as described in [15, TS 37.213] + +where the offsets are defined with respect to the SCS of the CORESET for Type0-PDCCH CSS set that is same as the SCS of the corresponding SS/PBCH block. + +For operation without shared spectrum channel access and for the SS/PBCH block and CORESET multiplexing pattern 1, a UE monitors PDCCH in the Type0-PDCCH CSS set over two slots. For SS/PBCH block with index $i$ , the UE determines an index of slot $s$ that is in a frame with system frame number (SFN) satisfying $\text{if}_i$ , or in a frame with SFN satisfying $\text{if}_i$ where $\text{if}_i$ based on the SCS for PDCCH receptions in the CORESET [4, TS 38.211]. + +- For $i$ and for a SS/PBCH block index $i$ , the two slots including the associated Type0-PDCCH monitoring occasions are slots $s$ and $s+1$ , and the index of the first symbol of the CORESET in slots $s$ and $s+1$ are provided by Table 13-11 and Table 13-12. +- For $i$ and for a SS/PBCH block index $i$ , the two slots including the associated Type0-PDCCH monitoring occasions are slots $s$ and $s+1$ , and the index of the first symbol of the CORESET in slots $s$ and $s+1$ are provided by Table 13-12A, where $\text{if}_i$ . +- For $i$ and for a SS/PBCH block index $i$ , the two slots including the associated Type0-PDCCH monitoring occasions are slots $s$ and $s+1$ , and the index of the first symbol of the CORESET in slots $s$ and $s+1$ are provided by Table 13-12A, where $\text{if}_i$ . + +For operation with shared spectrum channel access and for the SS/PBCH block and CORESET multiplexing pattern 1, a UE monitors PDCCH in the Type0-PDCCH CSS set over slots that include Type0-PDCCH monitoring occasions associated with SS/PBCH blocks that are quasi co-located with the SS/PBCH block that provides a CORESET for Type0-PDCCH CSS set with respect to average gain, quasi co-location 'typeA' and 'typeD' properties, when applicable [6, TS 38.214]. For a candidate SS/PBCH block index $i$ , where $i$ , two slots include the associated Type0-PDCCH monitoring occasions. The UE determines an index of slot $s$ that is in a frame with system frame number (SFN) satisfying $\text{if}_i$ , or in a frame with SFN satisfying $\text{if}_i$ where $\text{if}_i$ based on the SCS for PDCCH receptions in the CORESET [4, TS 38.211]. + +- For $i$ and for a candidate SS/PBCH block index $i$ , the two slots including the associated Type0-PDCCH monitoring occasions are slots $s$ and $s+1$ , and the index of the first symbol of the CORESET in slots $s$ and $s+1$ are provided by Table 13-11. The UE does not expect to be configured with $\text{if}_i$ , or with $\text{if}_i$ , when $\text{if}_i$ . + +- For $\mu$ and for a candidate SS/PBCH block index $i$ , the two slots including the associated Type0-PDCCH monitoring occasions are slots $n$ and $n+1$ , and the index of the first symbol of the CORESET in slots $n$ and $n+1$ are provided by Table 13-12. +- For $\mu$ and for a candidate SS/PBCH block index $i$ , the two slots including the associated Type0-PDCCH monitoring occasions are slots $n$ and $n+1$ , and the index of the first symbol of the CORESET in slots $n$ and $n+1$ are provided by Table 13-12A, where $\mu = 2$ . +- For $\mu$ and for a candidate SS/PBCH block index $i$ , the two slots including the associated Type0-PDCCH monitoring occasions are slots $n$ and $n+1$ , and the index of the first symbol of the CORESET in slots $n$ and $n+1$ are provided by Table 13-12A, where $\mu = 3$ . + +For operation without shared spectrum channel access and for the SS/PBCH block and CORESET multiplexing patterns 2 and 3, a UE monitors PDCCH in the Type0-PDCCH CSS set over one slot with Type0-PDCCH CSS set periodicity equal to the periodicity of SS/PBCH block. For a SS/PBCH block with index $i$ , the UE determines the slot index $n$ and based on parameters provided by Tables 13-13 through 13-15A. + +For operation with shared spectrum channel access and for SS/PBCH block and CORESET multiplexing pattern 3, a UE monitors PDCCH in the Type0-PDCCH CSS set over slots that include Type0-PDCCH monitoring occasions associated with SS/PBCH blocks that are quasi co-located with the SS/PBCH block that provides a CORESET for Type0-PDCCH CSS set with respect to average gain, quasi co-location 'typeA' and 'typeD' properties, when applicable. For a candidate SS/PBCH block index $i$ , where $\mu$ , the periodicity of the slot including the associated Type0-PDCCH monitoring occasion is same as the periodicity of the candidate SS/PBCH block, and the UE determines the slot index $n$ and based on parameters provided by Tables 13-15 and 13-15A, where $\mu$ is replaced by $\mu$ for operation with shared spectrum channel access in FR2-2. + +For the SS/PBCH block and CORESET multiplexing patterns 2 and 3, if the active DL BWP is the initial DL BWP, the UE is expected to be able to perform radio link monitoring, as described in clause 5, and measurements for radio resource management [10, TS 38.133] using a SS/PBCH block that provides a CORESET for Type0-PDCCH CSS set. + +**Table 13-0: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when {SS/PBCH block, PDCCH} SCS is {15, 15} kHz for frequency bands with minimum channel bandwidth 3 MHz and channel bandwidth 3 MHz or 5 MHz.** + +| Index | SS/PBCH block and CORESET multiplexing pattern | Number of RBs | Number of Symbols | Offset (RBs) | +|-------|------------------------------------------------|---------------|-------------------|--------------| +| 0 | 1 | 12 | 2 | 0 | +| 1 | 1 | 12 | 3 | 0 | +| 2 | 1 | 24 | 2 | 0 | +| 3 | 1 | 24 | 2 | 2 | +| 4 | 1 | 24 | 3 | 0 | +| 5 | 1 | 24 | 3 | 2 | +| 6 | 1 | 24 | 2 | 0 | +| 7 | 1 | 24 | 2 | 2 | +| 8 | 1 | 24 | 3 | 0 | +| 9 | 1 | 24 | 3 | 2 | +| 10 | 1 | 24 | 2 | 0 | +| 11 | 1 | 24 | 3 | 0 | +| 12 | | Reserved | | | +| 13 | | Reserved | | | +| 14 | | Reserved | | | +| 15 | | Reserved | | | + +**Table 13-1: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when {SS/PBCH block, PDCCH} SCS is {15, 15} kHz for frequency bands with minimum channel bandwidth 5 MHz or 10 MHz or with minimum channel bandwidth 3 MHz and channel bandwidth larger than 3 MHz** + +| Index | SS/PBCH block and CORESET multiplexing pattern | Number of RBs | Number of Symbols | Offset (RBs) | +|-------|------------------------------------------------|---------------|-------------------|--------------| +| 0 | 1 | 24 | 2 | 0 | +| 1 | 1 | 24 | 2 | 2 | +| 2 | 1 | 24 | 2 | 4 | +| 3 | 1 | 24 | 3 | 0 | +| 4 | 1 | 24 | 3 | 2 | +| 5 | 1 | 24 | 3 | 4 | +| 6 | 1 | 48 | 1 | 12 | +| 7 | 1 | 48 | 1 | 16 | +| 8 | 1 | 48 | 2 | 12 | +| 9 | 1 | 48 | 2 | 16 | +| 10 | 1 | 48 | 3 | 12 | +| 11 | 1 | 48 | 3 | 16 | +| 12 | 1 | 96 | 1 | 38 | +| 13 | 1 | 96 | 2 | 38 | +| 14 | 1 | 96 | 3 | 38 | +| 15 | Reserved | | | | + +**Table 13-1A: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when {SS/PBCH block, PDCCH} SCS is {15, 15} kHz for frequency bands operated with shared spectrum channel access** + +| Index | SS/PBCH block and CORESET multiplexing pattern | Number of RBs | Number of Symbols | Offset (RBs) | +|-------|------------------------------------------------|---------------|-------------------|--------------| +| 0 | 1 | 96 | 1 | 10 | +| 1 | 1 | 96 | 1 | 12 | +| 2 | 1 | 96 | 1 | 14 | +| 3 | 1 | 96 | 1 | 16 | +| 4 | 1 | 96 | 2 | 10 | +| 5 | 1 | 96 | 2 | 12 | +| 6 | 1 | 96 | 2 | 14 | +| 7 | 1 | 96 | 2 | 16 | +| 8 | Reserved | | | | +| 9 | Reserved | | | | +| 10 | Reserved | | | | +| 11 | Reserved | | | | +| 12 | Reserved | | | | +| 13 | Reserved | | | | +| 14 | Reserved | | | | +| 15 | Reserved | | | | + +**Table 13-2: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when {SS/PBCH block, PDCCH} SCS is {15, 30} kHz for frequency bands with minimum channel bandwidth 5 MHz or 10 MHz** + +| Index | SS/PBCH block and CORESET multiplexing pattern | Number of RBs | Number of Symbols | Offset (RBs) | +|-------|------------------------------------------------|---------------|-------------------|--------------| +| 0 | 1 | 24 | 2 | 5 | +| 1 | 1 | 24 | 2 | 6 | +| 2 | 1 | 24 | 2 | 7 | +| 3 | 1 | 24 | 2 | 8 | +| 4 | 1 | 24 | 3 | 5 | +| 5 | 1 | 24 | 3 | 6 | +| 6 | 1 | 24 | 3 | 7 | +| 7 | 1 | 24 | 3 | 8 | +| 8 | 1 | 48 | 1 | 18 | +| 9 | 1 | 48 | 1 | 20 | +| 10 | 1 | 48 | 2 | 18 | +| 11 | 1 | 48 | 2 | 20 | +| 12 | 1 | 48 | 3 | 18 | +| 13 | 1 | 48 | 3 | 20 | +| 14 | | Reserved | | | +| 15 | | Reserved | | | + +**Table 13-3: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when {SS/PBCH block, PDCCH} SCS is {30, 15} kHz for frequency bands with minimum channel bandwidth 5 MHz or 10 MHz except for the frequency bands defined by note 17 of Table 5.2-1 in [8-1, TS 38.101-1]** + +| Index | SS/PBCH block and CORESET multiplexing pattern | Number of RBs | Number of Symbols | Offset (RBs) | +|-------|------------------------------------------------|---------------|-------------------|--------------| +| 0 | 1 | 48 | 1 | 2 | +| 1 | 1 | 48 | 1 | 6 | +| 2 | 1 | 48 | 2 | 2 | +| 3 | 1 | 48 | 2 | 6 | +| 4 | 1 | 48 | 3 | 2 | +| 5 | 1 | 48 | 3 | 6 | +| 6 | 1 | 96 | 1 | 28 | +| 7 | 1 | 96 | 2 | 28 | +| 8 | 1 | 96 | 3 | 28 | +| 9 | | Reserved | | | +| 10 | | Reserved | | | +| 11 | | Reserved | | | +| 12 | | Reserved | | | +| 13 | | Reserved | | | +| 14 | | Reserved | | | +| 15 | | Reserved | | | + +**Table 13-4: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when {SS/PBCH block, PDCCH} SCS is {30, 30} kHz for frequency bands with minimum channel bandwidth 5 MHz or 10 MHz except for the frequency bands defined by note 17 of Table 5.2-1 in [8-1, TS 38.101-1]** + +| Index | SS/PBCH block and CORESET multiplexing pattern | Number of RBs | Number of Symbols | Offset (RBs) | +|-------|------------------------------------------------|---------------|-------------------|--------------| +| 0 | 1 | 24 | 2 | 0 | +| 1 | 1 | 24 | 2 | 1 | +| 2 | 1 | 24 | 2 | 2 | +| 3 | 1 | 24 | 2 | 3 | +| 4 | 1 | 24 | 2 | 4 | +| 5 | 1 | 24 | 3 | 0 | +| 6 | 1 | 24 | 3 | 1 | +| 7 | 1 | 24 | 3 | 2 | +| 8 | 1 | 24 | 3 | 3 | +| 9 | 1 | 24 | 3 | 4 | +| 10 | 1 | 48 | 1 | 12 | +| 11 | 1 | 48 | 1 | 14 | +| 12 | 1 | 48 | 1 | 16 | +| 13 | 1 | 48 | 2 | 12 | +| 14 | 1 | 48 | 2 | 14 | +| 15 | 1 | 48 | 2 | 16 | + +**Table 13-4A: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when {SS/PBCH block, PDCCH} SCS is {30, 30} kHz for frequency bands operated with shared spectrum channel access** + +| Index | SS/PBCH block and CORESET multiplexing pattern | Number of RBs | Number of Symbols | Offset (RBs) | +|-------|------------------------------------------------|---------------|-------------------|--------------| +| 0 | 1 | 48 | 1 | 0 | +| 1 | 1 | 48 | 1 | 1 | +| 2 | 1 | 48 | 1 | 2 | +| 3 | 1 | 48 | 1 | 3 | +| 4 | 1 | 48 | 2 | 0 | +| 5 | 1 | 48 | 2 | 1 | +| 6 | 1 | 48 | 2 | 2 | +| 7 | 1 | 48 | 2 | 3 | +| 8 | | Reserved | | | +| 9 | | Reserved | | | +| 10 | | Reserved | | | +| 11 | | Reserved | | | +| 12 | | Reserved | | | +| 13 | | Reserved | | | +| 14 | | Reserved | | | +| 15 | | Reserved | | | + +**Table 13-5: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when {SS/PBCH block, PDCCH} SCS is {30, 15} kHz for frequency bands with minimum channel bandwidth 40MHz or for the frequency bands defined by note 17 of Table 5.2-1 in [8-1, TS 38.101-1]** + +| Index | SS/PBCH block and CORESET multiplexing pattern | Number of RBs | Number of Symbols | Offset (RBs) | +|-------|------------------------------------------------|---------------|-------------------|--------------| +| 0 | 1 | 48 | 1 | 4 | +| 1 | 1 | 48 | 2 | 4 | +| 2 | 1 | 48 | 3 | 4 | +| 3 | 1 | 96 | 1 | 0 | +| 4 | 1 | 96 | 1 | 56 | +| 5 | 1 | 96 | 2 | 0 | +| 6 | 1 | 96 | 2 | 56 | +| 7 | 1 | 96 | 3 | 0 | +| 8 | 1 | 96 | 3 | 56 | +| 9 | | Reserved | | | +| 10 | | Reserved | | | +| 11 | | Reserved | | | +| 12 | | Reserved | | | +| 13 | | Reserved | | | +| 14 | | Reserved | | | +| 15 | | Reserved | | | + +**Table 13-6: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when {SS/PBCH block, PDCCH} SCS is {30, 30} kHz for frequency bands with minimum channel bandwidth 40MHz or for the frequency bands defined by note 17 of Table 5.2-1 in [8-1, TS 38.101-1]** + +| Index | SS/PBCH block and CORESET multiplexing pattern | Number of RBs | Number of Symbols | Offset (RBs) | +|-------|------------------------------------------------|---------------|-------------------|--------------| +| 0 | 1 | 24 | 2 | 0 | +| 1 | 1 | 24 | 2 | 4 | +| 2 | 1 | 24 | 3 | 0 | +| 3 | 1 | 24 | 3 | 4 | +| 4 | 1 | 48 | 1 | 0 | +| 5 | 1 | 48 | 1 | 28 | +| 6 | 1 | 48 | 2 | 0 | +| 7 | 1 | 48 | 2 | 28 | +| 8 | 1 | 48 | 3 | 0 | +| 9 | 1 | 48 | 3 | 28 | +| 10 | | Reserved | | | +| 11 | | Reserved | | | +| 12 | | Reserved | | | +| 13 | | Reserved | | | +| 14 | | Reserved | | | +| 15 | | Reserved | | | + +**Table 13-7: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when {SS/PBCH block, PDCCH} SCS is {120, 60} kHz** + +| Index | SS/PBCH block and CORESET multiplexing pattern | Number of RBs | Number of Symbols | Offset (RBs) | +|-------|------------------------------------------------|---------------|-------------------|------------------| +| 0 | 1 | 48 | 1 | 0 | +| 1 | 1 | 48 | 1 | 8 | +| 2 | 1 | 48 | 2 | 0 | +| 3 | 1 | 48 | 2 | 8 | +| 4 | 1 | 48 | 3 | 0 | +| 5 | 1 | 48 | 3 | 8 | +| 6 | 1 | 96 | 1 | 28 | +| 7 | 1 | 96 | 2 | 28 | +| 8 | 2 | 48 | 1 | -41 if
-42 if | +| 9 | 2 | 48 | 1 | 49 | +| 10 | 2 | 96 | 1 | -41 if
-42 if | +| 11 | 2 | 96 | 1 | 97 | +| 12 | | Reserved | | | +| 13 | | Reserved | | | +| 14 | | Reserved | | | +| 15 | | Reserved | | | + +**Table 13-8: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when {SS/PBCH block, PDCCH} SCS is {120, 120} kHz for FR2-1** + +| Index | SS/PBCH block and CORESET multiplexing pattern | Number of RBs | Number of Symbols | Offset (RBs) | +|-------|------------------------------------------------|---------------|-------------------|------------------| +| 0 | 1 | 24 | 2 | 0 | +| 1 | 1 | 24 | 2 | 4 | +| 2 | 1 | 48 | 1 | 14 | +| 3 | 1 | 48 | 2 | 14 | +| 4 | 3 | 24 | 2 | -20 if
-21 if | +| 5 | 3 | 24 | 2 | 24 | +| 6 | 3 | 48 | 2 | -20 if
-21 if | +| 7 | 3 | 48 | 2 | 48 | +| 8 | | Reserved | | | +| 9 | | Reserved | | | +| 10 | | Reserved | | | +| 11 | | Reserved | | | +| 12 | | Reserved | | | +| 13 | | Reserved | | | +| 14 | | Reserved | | | +| 15 | | Reserved | | | + +**Table 13-9: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when {SS/PBCH block, PDCCH} SCS is {240, 60} kHz** + +| Index | SS/PBCH block and CORESET multiplexing pattern | Number of RBs | Number of Symbols | Offset (RBs) | +|-------|------------------------------------------------|---------------|-------------------|--------------| +| 0 | 1 | 96 | 1 | 0 | +| 1 | 1 | 96 | 1 | 16 | +| 2 | 1 | 96 | 2 | 0 | +| 3 | 1 | 96 | 2 | 16 | +| 4 | | Reserved | | | +| 5 | | Reserved | | | +| 6 | | Reserved | | | +| 7 | | Reserved | | | +| 8 | | Reserved | | | +| 9 | | Reserved | | | +| 10 | | Reserved | | | +| 11 | | Reserved | | | +| 12 | | Reserved | | | +| 13 | | Reserved | | | +| 14 | | Reserved | | | +| 15 | | Reserved | | | + +**Table 13-10: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when {SS/PBCH block, PDCCH} SCS is {240, 120} kHz** + +| Index | SS/PBCH block and CORESET multiplexing pattern | Number of RBs | Number of Symbols | Offset (RBs) | +|-------|------------------------------------------------|---------------|-------------------|------------------| +| 0 | 1 | 48 | 1 | 0 | +| 1 | 1 | 48 | 1 | 8 | +| 2 | 1 | 48 | 2 | 0 | +| 3 | 1 | 48 | 2 | 8 | +| 4 | 2 | 24 | 1 | -41 if
-42 if | +| 5 | 2 | 24 | 1 | 25 | +| 6 | 2 | 48 | 1 | -41 if
-42 if | +| 7 | 2 | 48 | 1 | 49 | +| 8 | | Reserved | | | +| 9 | | Reserved | | | +| 10 | | Reserved | | | +| 11 | | Reserved | | | +| 12 | | Reserved | | | +| 13 | | Reserved | | | +| 14 | | Reserved | | | +| 15 | | Reserved | | | + +**Table 13-10A: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when {SS/PBCH block, PDCCH} SCS is {120, 120} kHz, {480, 480} kHz, or {960, 960} kHz for FR2-2** + +| Index | SS/PBCH block and CORESET multiplexing pattern | Number of RBs | Number of Symbols | Offset (RBs) | +|-------|------------------------------------------------|---------------|-------------------|------------------| +| 0 | 1 | 24 | 2 | 0 | +| 1 | 1 | 24 | 2 | 4 | +| 2 | 1 | 48 | 1 | 0 | +| 3 | 1 | 48 | 1 | 14 | +| 4 | 1 | 48 | 1 | 28 | +| 5 | 1 | 48 | 2 | 0 | +| 6 | 1 | 48 | 2 | 14 | +| 7 | 1 | 48 | 2 | 28 | +| 8 | 1 | 96 | 1 | 0 | +| 9 | 1 | 96 | 1 | 76 | +| 10 | 1 | 96 | 2 | 0 | +| 11 | 1 | 96 | 2 | 76 | +| 12 | 3 | 24 | 2 | -20 if
-21 if | +| 13 | 3 | 24 | 2 | 24 | +| 14 | 3 | 48 | 2 | -20 if
-21 if | +| 15 | 3 | 48 | 2 | 48 | + +**Table 13-11: Parameters for PDCCH monitoring occasions for Type0-PDCCH CSS set - SS/PBCH block and CORESET multiplexing pattern 1 and FR1** + +| Index | | Number of search space sets per slot | | First symbol index | +|-------|---|--------------------------------------|-----|--------------------------------| +| 0 | 0 | 1 | 1 | 0 | +| 1 | 0 | 2 | 1/2 | {0, if is even}, {, if is odd} | +| 2 | 2 | 1 | 1 | 0 | +| 3 | 2 | 2 | 1/2 | {0, if is even}, {, if is odd} | +| 4 | 5 | 1 | 1 | 0 | +| 5 | 5 | 2 | 1/2 | {0, if is even}, {, if is odd} | +| 6 | 7 | 1 | 1 | 0 | +| 7 | 7 | 2 | 1/2 | {0, if is even}, {, if is odd} | +| 8 | 0 | 1 | 2 | 0 | +| 9 | 5 | 1 | 2 | 0 | +| 10 | 0 | 1 | 1 | 1 | +| 11 | 0 | 1 | 1 | 2 | +| 12 | 2 | 1 | 1 | 1 | +| 13 | 2 | 1 | 1 | 2 | +| 14 | 5 | 1 | 1 | 1 | +| 15 | 5 | 1 | 1 | 2 | + +**Table 13-12: Parameters for PDCCH monitoring occasions for Type0-PDCCH CSS set - SS/PBCH block and CORESET multiplexing pattern 1 and FR2-1, or SS/PBCH block and CORESET multiplexing pattern 1 and {SS/PBCH block, PDCCH} SCS {120, 120} kHz in FR2-2** + +| Index | | Number of search space sets per slot | | First symbol index | +|-------|----------|--------------------------------------|-----|---------------------------------| +| 0 | 0 | 1 | 1 | 0 | +| 1 | 0 | 2 | 1/2 | {0, if is even}, {7, if is odd} | +| 2 | 2.5 | 1 | 1 | 0 | +| 3 | 2.5 | 2 | 1/2 | {0, if is even}, {7, if is odd} | +| 4 | 5 | 1 | 1 | 0 | +| 5 | 5 | 2 | 1/2 | {0, if is even}, {7, if is odd} | +| 6 | 0 | 2 | 1/2 | {0, if is even}, {, if is odd} | +| 7 | 2.5 | 2 | 1/2 | {0, if is even}, {, if is odd} | +| 8 | 5 | 2 | 1/2 | {0, if is even}, {, if is odd} | +| 9 | 7.5 | 1 | 1 | 0 | +| 10 | 7.5 | 2 | 1/2 | {0, if is even}, {7, if is odd} | +| 11 | 7.5 | 2 | 1/2 | {0, if is even}, {, if is odd} | +| 12 | 0 | 1 | 2 | 0 | +| 13 | 5 | 1 | 2 | 0 | +| 14 | Reserved | | | | +| 15 | Reserved | | | | + +**Table 13-12A: Parameters for PDCCH monitoring occasions for Type0-PDCCH CSS set - SS/PBCH block and CORESET multiplexing pattern 1 and {SS/PBCH block, PDCCH} SCS {480, 480} kHz or {960, 960} kHz in FR2-2** + +| Index | | Number of search space sets per slot | | First symbol index | +|-------|----------|--------------------------------------|-----|---------------------------------| +| 0 | 0 | 1 | 1 | 0 | +| 1 | 0 | 2 | 1/2 | {0, if is even}, {7, if is odd} | +| 2 | X | 1 | 1 | 0 | +| 3 | X | 2 | 1/2 | {0, if is even}, {7, if is odd} | +| 4 | 5 | 1 | 1 | 0 | +| 5 | 5 | 2 | 1/2 | {0, if is even}, {7, if is odd} | +| 6 | 0 | 2 | 1/2 | {0, if is even}, {, if is odd} | +| 7 | X | 2 | 1/2 | {0, if is even}, {, if is odd} | +| 8 | 5 | 2 | 1/2 | {0, if is even}, {, if is odd} | +| 9 | 5+X | 1 | 1 | 0 | +| 10 | 5+X | 2 | 1/2 | {0, if is even}, {7, if is odd} | +| 11 | 5+X | 2 | 1/2 | {0, if is even}, {, if is odd} | +| 12 | 0 | 1 | 2 | 0 | +| 13 | 5 | 1 | 2 | 0 | +| 14 | Reserved | | | | +| 15 | Reserved | | | | + +**Table 13-13: PDCCH monitoring occasions for Type0-PDCCH CSS set - SS/PBCH block and CORESET multiplexing pattern 2 and {SS/PBCH block, PDCCH} SCS {120, 60} kHz** + +| Index | PDCCH monitoring occasions (SFN and slot number) | First symbol index
( $k = 0, 1, \dots, 15$ ) | +|-------|--------------------------------------------------|-------------------------------------------------| +| 0 | | 0, 1, 6, 7 for
, , , | +| 1 | Reserved | | +| 2 | Reserved | | +| 3 | Reserved | | +| 4 | Reserved | | +| 5 | Reserved | | +| 6 | Reserved | | +| 7 | Reserved | | +| 8 | Reserved | | +| 9 | Reserved | | +| 10 | Reserved | | +| 11 | Reserved | | +| 12 | Reserved | | +| 13 | Reserved | | +| 14 | Reserved | | +| 15 | Reserved | | + +**Table 13-14: PDCCH monitoring occasions for Type0-PDCCH CSS set - SS/PBCH block and CORESET multiplexing pattern 2 and {SS/PBCH block, PDCCH} SCS {240, 120} kHz** + +| Index | PDCCH monitoring occasions
(SFN and slot number) | First symbol index
( $k = 0, 1, \dots, 7$ ) | +|-------|-----------------------------------------------------|--------------------------------------------------| +| 0 | or | 0, 1, 2, 3, 0, 1 in , , , , ()
12, 13 in , () | +| 1 | Reserved | | +| 2 | Reserved | | +| 3 | Reserved | | +| 4 | Reserved | | +| 5 | Reserved | | +| 6 | Reserved | | +| 7 | Reserved | | +| 8 | Reserved | | +| 9 | Reserved | | +| 10 | Reserved | | +| 11 | Reserved | | +| 12 | Reserved | | +| 13 | Reserved | | +| 14 | Reserved | | +| 15 | Reserved | | + +**Table 13-15: PDCCH monitoring occasions for Type0-PDCCH CSS set - SS/PBCH block and CORESET multiplexing pattern 3 and {SS/PBCH block, PDCCH} SCS {120, 120} kHz** + +| Index | PDCCH monitoring occasions (SFN and slot number) | First symbol index
( $k = 0, 1, \dots, 15$ ) | +|-------|--------------------------------------------------|-------------------------------------------------| +| 0 | | 4, 8, 2, 6 in
, , , | +| 1 | Reserved | | +| 2 | Reserved | | +| 3 | Reserved | | +| 4 | Reserved | | +| 5 | Reserved | | +| 6 | Reserved | | +| 7 | Reserved | | +| 8 | Reserved | | +| 9 | Reserved | | +| 10 | Reserved | | +| 11 | Reserved | | +| 12 | Reserved | | +| 13 | Reserved | | +| 14 | Reserved | | +| 15 | Reserved | | + +**Table 13-15A: PDCCH monitoring occasions for Type0-PDCCH CSS set - SS/PBCH block and CORESET multiplexing pattern 3 and {SS/PBCH block, PDCCH} SCS {480, 480} kHz or {960, 960} kHz** + +| Index | PDCCH monitoring occasions (SFN and slot number) | First symbol index
( $k = 0, 1, \dots, 31$ ) | +|-------|--------------------------------------------------|-------------------------------------------------| +| 0 | | 2, 9 in
, | +| 1 | Reserved | | +| 2 | Reserved | | +| 3 | Reserved | | +| 4 | Reserved | | +| 5 | Reserved | | +| 6 | Reserved | | +| 7 | Reserved | | +| 8 | Reserved | | +| 9 | Reserved | | +| 10 | Reserved | | +| 11 | Reserved | | +| 12 | Reserved | | +| 13 | Reserved | | +| 14 | Reserved | | +| 15 | Reserved | | + +If a UE detects a first SS/PBCH block and determines that a CORESET for Type0-PDCCH CSS set is not present, and for FR1 or for FR2, the UE may determine the nearest (in the corresponding frequency direction) global synchronization channel number (GSCN) of a second SS/PBCH block having a CORESET for an associated Type0-PDCCH CSS set as $GSCN_{second} = GSCN_{first} + \Delta$ , where $GSCN_{first}$ is the GSCN of the first SS/PBCH block, $\Delta$ is 3 in FR2-1, 3 in FR2-2, and $\Delta$ is a GSCN offset provided by Table 13-16 for FR1 and Table 13-17 for FR2. If the UE detects the second SS/PBCH block and the second SS/PBCH block does not provide a CORESET for Type0-PDCCH CSS set, as described in clause 4.1, the UE may ignore the information related to GSCN of SS/PBCH block locations for performing cell search. + +If a UE detects a SS/PBCH block and determines that a CORESET for Type0-PDCCH CSS set is not present, and for FR1 or for FR2, the UE determines that there is no SS/PBCH block having an associated Type0-PDCCH CSS set within a GSCN range $[GSCN_{first} - \Delta, GSCN_{first} + \Delta]$ and $\Delta$ are respectively determined by *controlResourceSetZero* and *searchSpaceZero* in *pdcch-ConfigSIB1*. If the GSCN range is empty, the UE determines that there is no information for a second SS/PBCH block with a CORESET for an associated Type0-PDCCH CSS set on the detected SS/PBCH block. + +If a UE does not detect any SS/PBCH block providing a CORESET for Type0-PDCCH CSS set, as described in clause 4.1, within a time period determined by the UE, the UE may ignore the information related to GSCN of SS/PBCH locations in performing cell search. + +**Table 13-16: Mapping between the combination of *controlResourceSetZero* and *searchSpaceZero* in *pdcch-ConfigSIB1* to for FR1** + +| | $16 \times controlResourceSetZero + searchSpaceZero$ | | +|----|------------------------------------------------------|-----------------------------------| +| 24 | 0, 1, ..., 255 | 1, 2, ..., 256 | +| 25 | 0, 1, ..., 255 | 257, 258, ..., 512 | +| 26 | 0, 1, ..., 255 | 513, 514, ..., 768 | +| 27 | 0, 1, ..., 255 | -1, -2, ..., -256 | +| 28 | 0, 1, ..., 255 | -257, -258, ..., -512 | +| 29 | 0, 1, ..., 255 | -513, -514, ..., -768 | +| 30 | 0, 1, ..., 255 | Reserved, Reserved, ..., Reserved | + +**Table 13-17: Mapping between the combination of *controlResourceSetZero* and *searchSpaceZero* in *pdcch-ConfigSIB1* to for FR2** + +| | $16 \times controlResourceSetZero + searchSpaceZero$ | | +|----|------------------------------------------------------|-----------------------------------| +| 12 | 0, 1, ..., 255 | 1, 2, ..., 256 | +| 13 | 0, 1, ..., 255 | -1, -2, ..., -256 | +| 14 | 0, 1, ..., 255 | Reserved, Reserved, ..., Reserved | + +# 14 Integrated access-backhaul operation + +Throughout this specification, unless otherwise noted, statements using the term "UE" in clauses 4 through 13 are equally applicable to the IAB-MT of an IAB node. + +A procedure for an IAB-MT to perform cell search, system information acquisition, or random access procedure is same as a corresponding one for a UE except for the following. + +For initial cell selection, an IAB-MT may assume that half frames with SS/PBCH blocks occur with a periodicity of 16 frames. + +For PRACH transmission, an IAB-MT determines frames and subframes/slots within the frames containing PRACH occasions as described in [4, TS 38.211]. + +The IAB-MT determines an association period for mapping SS/PBCH blocks to PRACH occasions based on a PRACH configuration period as described in clause 8.1 and according to Table 14-1 instead of Table 8.1-1. An association pattern period includes one or more association periods and is determined so that a pattern between PRACH occasions and SS/PBCH blocks repeats at most every 640 msec. A PRACH occasion in a PRACH slot is valid according to the conditions in clause 8.1. + +**Table 14-1: Mapping between PRACH configuration period and SS/PBCH block to PRACH occasion association period for an IAB-MT** + +| PRACH configuration period (msec) | Association period (number of PRACH configuration periods) | +|-----------------------------------|------------------------------------------------------------| +| 10 | {1, 2, 4, 8, 16, 32, 64} | +| 20 | {1, 2, 4, 8, 16, 32} | +| 40 | {1, 2, 4, 8, 16} | +| 80 | {1, 2, 4, 8} | +| 160 | {1, 2, 4} | +| 320 | {1, 2} | +| 640 | {1} | + +If an IAB-node is provided an index in a Timing Delta MAC CE [11, TS 38.321] from a serving cell, the IAB-node may assume that is a time difference between a DU transmission of a signal from the serving cell and a reception of the signal by the IAB-MT when , where + +- is the difference between the IAB-MT reception time and the IAB-MT transmission time for IAB-MT transmission timing mode 'Case-6', and is defined in clause 4.3.1 of [4, TS 38.211] for IAB-MT transmission timing mode 'Case-1' and parent node reception mode 'Case-7' +- and are determined as + - and , if the serving cell providing the Timing Delta MAC CE operates in FR1 + - and , if the serving cell providing the Timing Delta MAC CE operates in FR2 + +The IAB node may assume that a same value of index is provided from a serving cell for the IAB-MT transmission timing modes 'Case-7' and 'Case-1' + +The IAB-node may use the time difference to determine a DU transmission time. + +For a serving cell of an IAB-MT, the IAB-MT can be provided by Timing Case Indication MAC CE [11, TS 38.321] an indication of the IAB-MT transmission timing mode in a slot. Upon reception of the Timing Case Indication for a serving cell in a TAG, the IAB-MT applies a same IAB-MT transmission timing mode in a slot on all serving cells in the TAG. + +If the indicated IAB-MT transmission timing mode in a slot is set to 'Case-1' or the IAB-MT transmission timing mode indication in a slot is not provided, the IAB-MT transmission time is determined as for a "UE" in clause 4.2. + +If the indicated IAB-MT transmission timing mode in a slot is set to 'Case-6', the IAB-node sets the IAB-MT transmission time to the transmission time of the IAB-DU. + +If the indicated IAB-MT transmission timing mode in a slot is set to 'Case-7', the IAB-MT is provided a timing advance offset value for a serving cell by Case-7 Timing advance offset MAC CE [11, TS 38.321]. The IAB-MT determines its uplink transmission timing as $T_{TA} + N_{TA,offset2} \cdot T_c$ where is defined in clause 4.3.1 of [4, TS 38.211] and where is provided by the Case-7 Timing advance offset MAC CE [11, TS 38.321]. + +A slot format for an IAB-DU or an IAB-MT includes downlink symbols, uplink symbols, and flexible symbols. + +For each cell of an IAB-DU, the IAB-DU can be provided an indication for a slot format over a number of slots by *gNB-DU Cell Resource Configuration* [16, TS 38.473]. + +For each serving cell, an IAB-MT can be provided an indication for a slot format over a number of slots by *tdd-UL-DL-ConfigurationDedicated-IAB-MT*. If the IAB-MT is provided *tdd-UL-DL-ConfigurationDedicated-IAB-MT*, the statements in clause 11.1 that include "*tdd-UL-DL-ConfigurationDedicated*" apply to the IAB-MT of an IAB node by replacing "*tdd-UL-DL-ConfigurationDedicated*" with "*tdd-UL-DL-ConfigurationDedicated-IAB-MT*" for the IAB-MT, except that the *tdd-UL-DL-ConfigurationDedicated-IAB-MT* provides + +- a set of slot configurations by *slotSpecificConfigurationsToAddModList-IAB-MT* +- for each slot configuration from the set of slot configurations + - a slot index for a slot provided by *slotIndex* + - a set of symbols for a slot by *symbols-IAB-MT* where + +- if *symbols-IAB-MT* = *allDownlink*, all symbols in the slot are downlink +- if *symbols-IAB-MT* = *allUplink*, all symbols in the slot are uplink +- if *symbols-IAB-MT* = *explicit*, *nrofDownlinkSymbols* provides a number of downlink first symbols in the slot and *nrofUplinkSymbols* provides a number of uplink last symbols in the slot. If *nrofDownlinkSymbols* is not provided, there are no downlink first symbols in the slot and if *nrofUplinkSymbols* is not provided, there are no uplink last symbols in the slot. The remaining symbols in the slot are flexible. +- if *symbols-IAB-MT* = *explicit-IAB-MT*, *nrofUplinkSymbols* provides a number of uplink first symbols in the slot and *nrofDownlinkSymbols* provides a number of downlink last symbols in the slot. If *nrofUplinkSymbols* is not provided, there are no uplink first symbols in the slot and if *nrofDownlinkSymbols* is not provided, there are no downlink last symbols in the slot. The remaining symbols in the slot are flexible. + +If an IAB-MT is configured with an MCG and an SCG, is not capable of simultaneous transmission and reception, and would simultaneously transmit and receive on the MCG and the SCG, + +- if flexible symbols are configured by both parent nodes for operation with inter-donor NR-DC, the IAB-MT operates according to the scheduling from the MCG +- otherwise, if the IAB-MT is configured with multiple serving cells, is provided *directionalCollisionHandling-r17* = 'enabled' for a set of serving cell(s) from the multiple serving cells, and indicates *half-DuplexTDD-CA-SameSCS* capability across MCG and SCG for NR-DC operation, the IAB-MT applies the procedures for resolving directional collisions as described in clause 11.1 for resolving directional collisions across serving cells. + +An IAB-MT can be provided, by *SlotFormatCombinationsPerCell*, a list of slot format combinations applicable for one serving cell and, by *SlotFormatIndicator*, a configuration for monitor a DCI format 2\_0 indicating a slot format combination, from the list of slot format combinations, over a number of slots as described in clause 11.1.1. In addition to the slot formats in Table 11.1.1-1, an SFI field for an IAB-MT in DCI format 2\_0 can indicate to the IAB-MT a slot format from the slot formats in Table 14-2. + +**Table 14-2: Slot formats for normal cyclic prefix** + +| Slot Format | Symbol number in a slot | | | | | | | | | | | | | | +|-------------|-------------------------|---|---|---|---|---|---|---|---|---|----|----|----|----| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | +| 56 | U | U | U | U | U | U | U | U | U | U | U | U | U | F | +| 57 | U | U | U | U | U | U | U | U | U | U | U | U | F | F | +| 58 | U | U | U | U | U | U | U | U | U | U | U | F | F | F | +| 59 | U | U | U | U | U | U | U | U | U | U | F | F | F | F | +| 60 | U | U | U | U | U | U | U | U | U | F | F | F | F | F | +| 61 | U | U | U | U | U | U | U | U | F | F | F | F | F | F | +| 62 | U | U | U | U | U | U | U | F | F | F | F | F | F | F | +| 63 | U | U | U | U | U | U | F | F | F | F | F | F | F | F | +| 64 | U | U | U | U | U | F | F | F | F | F | F | F | F | F | +| 65 | U | U | U | U | F | F | F | F | F | F | F | F | F | F | +| 66 | U | U | U | F | F | F | F | F | F | F | F | F | F | F | +| 67 | U | U | F | F | F | F | F | F | F | F | F | F | F | F | +| 68 | U | F | F | F | F | F | F | F | F | F | F | F | F | F | +| 69 | U | F | F | F | F | F | F | F | F | F | F | F | F | D | +| 70 | U | U | F | F | F | F | F | F | F | F | F | F | F | D | +| 71 | U | U | U | F | F | F | F | F | F | F | F | F | F | D | +| 72 | U | F | F | F | F | F | F | F | F | F | F | F | D | D | +| 73 | U | U | F | F | F | F | F | F | F | F | F | F | D | D | +| 74 | U | U | U | F | F | F | F | F | F | F | F | F | D | D | +| 75 | U | F | F | F | F | F | F | F | F | F | F | D | D | D | +| 76 | U | U | F | F | F | F | F | F | F | F | F | D | D | D | +| 77 | U | U | U | F | F | F | F | F | F | F | F | D | D | D | +| 78 | U | U | U | U | U | U | U | U | U | U | U | U | F | D | +| 79 | U | U | U | U | U | U | U | U | U | U | U | F | F | D | +| 80 | U | U | U | U | U | U | U | U | U | U | F | F | F | D | +| 81 | U | U | U | U | U | U | U | U | U | U | U | F | D | D | +| 82 | U | U | U | U | U | U | U | U | U | U | F | F | D | D | +| 83 | U | U | U | U | U | U | U | U | U | F | F | F | D | D | +| 84 | U | F | D | D | D | D | D | D | D | D | D | D | D | D | +| 85 | U | U | F | D | D | D | D | D | D | D | D | D | D | D | +| 86 | U | U | U | F | D | D | D | D | D | D | D | D | D | D | +| 87 | U | F | F | D | D | D | D | D | D | D | D | D | D | D | +| 88 | U | U | F | F | D | D | D | D | D | D | D | D | D | D | +| 89 | U | U | U | F | F | D | D | D | D | D | D | D | D | D | +| 90 | U | F | F | F | D | D | D | D | D | D | D | D | D | D | +| 91 | U | U | F | F | F | D | D | D | D | D | D | D | D | D | +| 92 | U | U | U | F | F | F | D | D | D | D | D | D | D | D | +| 93 | U | U | U | U | U | U | U | U | U | F | F | F | F | D | +| 94 | U | U | U | U | U | U | F | F | F | F | F | F | D | D | +| 95 | U | U | U | U | U | U | F | F | D | D | D | D | D | D | +| 96 | U | U | U | U | U | U | U | D | D | D | D | D | D | D | + +For a serving cell of an IAB-MT, the IAB-MT can be provided by Provided Guard Symbols MAC CE, for Case-1, Case-6 and Case-7 timing modes, respectively, a number of symbols that will not be used for the IAB-MT in slots where the IAB-node transitions between IAB-MT and IAB-node DU and a SCS configuration for the number of symbols [11, TS 38.321]. + +With reference to slots of an IAB-DU cell, a symbol in a slot of an IAB-DU cell can be configured to be of hard, soft, or unavailable type by *HSNA Slot Configuration List* in *gNB-DU Cell Resource Configuration* [16, TS 38.473]. + +When a downlink, uplink, or flexible symbol is configured as hard, the IAB-DU cell can respectively transmit, receive, or either transmit or receive in the symbol. A symbol of a slot is equivalent to being configured as hard if an IAB-DU would transmit a SS/PBCH block, PDCCH for Type0-PDCCH CSS sets configured by *pdccConfigSIB1*, or a periodic CSI-RS in the symbol of the slot, or would receive a PRACH or a SR in the symbol of the slot. + +When a downlink, uplink, or flexible symbol is configured as soft, the IAB-DU cell can respectively transmit, receive or either transmit or receive in the symbol only if + +- the IAB-MT does not transmit or receive during the symbol of the IAB-DU cell, or +- with respect to all serving cells, the IAB-MT would transmit or receive during the symbol of the IAB-DU cell, and the transmission or reception during the symbol of the IAB-DU cell is not changed due to a use of the symbol by the IAB-DU, or +- the IAB-MT detects a DCI format 2\_5 with an AI index field value indicating the soft symbol as available if the IAB-MT is not configured with an SCG, or +- the IAB-MT detects two DCI formats 2\_5 with an AI index field indicating the soft symbol as available from the MCG and SCG, respectively, or +- the IAB-MT detects a DCI format 2\_5 with an AI index field value indicating the soft symbol as available from one cell group and with respect to all serving cells of the other cell group + - the IAB-MT does not transmit or receive during the symbol of the IAB-DU cell, or + - the IAB-MT would transmit or receive during the symbol of the IAB-DU cell, and the transmission or reception during the symbol of the IAB-DU cell does not change due to a use of the symbol by the IAB-DU. + +When the IAB-MT receives a DCI format 2\_5 from a serving cell in a cell group, the IAB-MT applies the information of the DCI format 2\_5 to all serving cells of the cell group. + +When a symbol is configured as unavailable, the IAB-DU neither transmits nor receives in the symbol. + +With reference to slots of an IAB-DU cell, the IAB-DU can be provided an indication of hard, soft or unavailable type per RB set for symbols configured as downlink, uplink or flexible in a slot by *Frequency-Domain HSNA Configuration List* [16, TS 38.473]. The RB set size and the number of RB sets are configured by *RB Set Configuration* [16, TS 38.473]. The IAB-node can assume the RB set size for the IAB-DU cell is larger than or equal to the IAB-MT's smallest RBG size of the configured BWPs of the FDM required IAB-MT's serving cell(s) as indicated in *Multiplexing Info* [16, TS 38.473] of the DU cell. If an indication of hard, soft or unavailable type is not provided for an RB set of a symbol in a slot, the IAB-DU applies the configuration of hard, soft or unavailable type provided by *HSNA Slot Configuration List* in *gNB-DU Cell Resource Configuration* [16, TS 38.473] for the RB set of the symbol in the slot. If an indication of hard, soft, or unavailable type is provided for an RB set in a symbol of a slot, the IAB-DU applies the configuration of hard, soft, or unavailable type provided by *Frequency-Domain HSNA Configuration List* [16, TS 38.473] unless the symbol is configured as soft type in *HSNA Slot Configuration List* in *gNB-DU Cell Resource Configuration* [16, TS 38.473] and the IAB-DU cell can transmit or receive in the symbol. + +When an RB set of a downlink, uplink, or flexible symbol is configured as hard, the IAB-DU cell can respectively transmit, receive, or either transmit or receive on the RB set in the symbol. An RB set of a symbol is equivalent to being configured as hard if an IAB-DU would transmit a SS/PBCH block, PDCCH for Type0-PDCCH CSS sets configured by *pdchConfigSIB1*, or a periodic CSI-RS in the RB set of the symbol, or would receive a PRACH or a SR in the RB set of the symbol. + +When an RB set of a downlink, uplink, or flexible symbol is configured as soft, the IAB-DU cell can respectively transmit, receive or either transmit or receive on the RB set in the symbol only if + +- the IAB-MT does not transmit or receive on the RB set during the symbol of the IAB-DU cell, or +- with respect to all serving cells, the IAB-MT would transmit or receive on the RB set during the symbol of the IAB-DU cell, and the transmission or reception on the RB set or any RB set that is configured as unavailable or configured as soft and not indicated as available during the symbol of the IAB-DU cell is not changed due to a use of the RB set in the symbol by the IAB-DU, or +- the IAB-MT detects a DCI format 2\_5 with an AI index field value indicating the soft RB set as available if the IAB-MT is not configured with an SCG, or +- the IAB-MT detects two DCI formats 2\_5 with an AI index field value indicating the soft RB set as available from the MCG and SCG, respectively, or +- the IAB-MT detects a DCI format 2\_5 with an AI index field value indicating the soft RB set as available from one cell group and with respect to all serving cells of the other cell group, the IAB-MT would transmit or receive on the RB set during the symbol of the IAB-DU cell, and the transmission or reception on the RB set during the symbol of the IAB-DU cell does not change due to a use of the RB set in the symbol by the IAB-DU. + +When an RB set of a downlink, uplink, or flexible symbol is configured as unavailable, the IAB-DU neither transmits nor receives in the RB set in the symbol. + +If an IAB-node is provided an *AvailabilityIndicator*, the IAB-node is provided an AI-RNTI by *ai-RNTI* and a payload size of a DCI format 2\_5 by *dci-PayloadSizeAI*. The IAB-node is also provided a search space set configuration, by *SearchSpace*, for monitoring PDCCH. + +For each cell of an IAB-DU in a set of cells of the IAB-DU, the IAB-DU can be provided: + +- an identity of the IAB-DU cell by *iab-DU-CellIdentity* +- a location of an availability indicator (AI) index field in DCI format 2\_5 by *positionInDCI-AI-r16* and/or by *positionInDCI-AI-RBGroups-v1720* +- a set of availability combinations by *availabilityCombinations-r16* or by *availabilityCombinationsRB-Groups-r17*, where each availability combination in the set of availability combinations includes + - *resourceAvailability-r16* indicating availability of soft symbols in one or more slots for the IAB-DU cell, or one *resourceAvailability-r17* indicating availability of soft resources in all RB sets in one or more slots for the IAB-DU cell, or one or multiple RB set groups by *rb-SetGroups-r17* with each RB set groups by *RB-SetGroup-r17* indicating *resourceAvailability-r17* for soft resources in one or more slots for the associated *rb-Sets-r17*, and + - a mapping for the soft symbol, and/or for soft resources, availability combinations provided by *resourceAvailability-r16* or *resourceAvailability-r17* to a corresponding AI index field value in DCI format 2\_5 provided by *availabilityCombinationId-r16* or *availabilityCombinationId-r17*, respectively + +With reference to a slot of an IAB-DU cell, if the IAB-DU is not provided an indication of hard, soft or unavailable type per RB set by *Frequency-Domain HSNA Configuration List* [16, TS 38.473], the indication of availability for the slot is based solely on *availabilityCombinations-r16*. + +The IAB-DU can assume a same SCS configuration for *availabilityCombinations-r16* or *availabilityCombinationsRB-Groups-r17* for slots of a cell as an SCS configuration provided by *gNB-DU Cell Resource Configuration* for the cell. + +The IAB-DU can assume a same SCS configuration for *availabilityCombinationsRB-Groups-r17* for RB sets of a cell as a SCS configuration provided by *RB Set Configuration* for the cell. + +An AI index field value in a DCI format 2\_5 indicates to an IAB-DU a soft symbol and/or a soft RB set in an RB set group availability in each slot for a number of slots starting from the earliest slot of the IAB-DU which overlaps in time with the slot of the IAB-MT where the IAB-MT detects the DCI format 2\_5. The number of slots is equal to or larger than a PDCCH monitoring periodicity for DCI format 2\_5 as provided by *SearchSpace*. The AI index field includes bits where *maxAIindex* is the maximum of the values provided by corresponding *availabilityCombinationId*. An availability for a soft symbol or a soft RB set in an RB set group in a slot is identified by a corresponding value *resourceAvailability* as provided in Table 14-3. + +**Table 14-3: Mapping between values of *resourceAvailability* elements and types of soft symbol or soft RB set availability in a slot** + +| Value | Indication | +|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | No indication of availability for soft symbols or soft RB sets in an RB set group | +| 1 | DL soft symbols or soft RB sets in an RB set group are indicated available
No indication of availability for UL and Flexible soft symbols or soft RB sets in an RB set group | +| 2 | UL soft symbols or soft RB sets in an RB set group are indicated available
No indication of availability for DL and Flexible soft symbols or soft RB sets in an RB set group | +| 3 | DL and UL soft symbols or soft RB sets in an RB set group are indicated available
No indication of availability for Flexible soft symbols or soft RB sets in an RB set group | +| 4 | Flexible soft symbols or soft RB sets in an RB set group are indicated available
No indication of availability for DL and UL soft symbols or soft RB sets in an RB set group | +| 5 | DL and Flexible soft symbols or soft RB sets in an RB set group are indicated available
No indication of availability for UL soft symbols or soft RB sets in an RB set group | +| 6 | UL and Flexible soft symbols or soft RB sets in an RB set group are indicated available
No indication of availability for DL soft symbols or soft RB sets in an RB set group | +| 7 | DL, UL, and Flexible soft symbols or soft RB sets in an RB set group are indicated available | + +If a PDCCH monitoring periodicity for DCI format 2\_5 is smaller than a duration of an availability combination of soft symbols over a number of slots that the IAB-MT obtains at a PDCCH monitoring occasion for DCI format 2\_5 by a corresponding AI index field value, and the IAB-MT detects more than one DCI formats 2\_5 indicating an availability combination of soft symbols or of soft RB sets in RB set groups in a slot, the IAB-MT expects that each of the more than one DCI formats 2\_5 indicates a same value for the availability combination of the soft symbols or of soft RB sets in an RB set group in the slot. An IAB-MT monitors PDCCH candidates for a DCI format 2\_5 with CRC scrambled by AI-RNTI in one or both of the following search space sets: + +- a Type3-PDCCH CSS set configured by *SearchSpace* in *PDCCH-Config* with *searchSpaceType* = *common*; +- a USS set configured by *SearchSpace* in *PDCCH-Config* with *searchSpaceType* = *ue-Specific*. + +The IAB-node can be provided by the parent node a set of RS resource indexes that indicate quasi co-location properties of an IAB-DU cell where simultaneous transmission/reception from the IAB-MT and transmission from the IAB-DU cells is restricted by Child IAB-DU Restricted Beam Indication MAC CE as described in [11, TS 38.321]. The IAB-DU does not transmit on a cell if the IAB node is operating in a non-TDM multiplexing mode using an indicated RS resource index on a symbol or RB set configured as soft in an IAB-DU cell + +- when it is not indicated as available by *resourceAvailability* +- when the IAB-MT is operating on an associated carrier, if that indication is provided +- when the current IAB-DU transmission mode corresponds to an associated multiplexing mode, if that indication is provided +- when one of the associated TCI states, RS resource indexes, or SRI of the IAB-MT, if provided, is simultaneously used for reception or transmission of the IAB-MT +- when simultaneous transmission/reception by the IAB-MT and transmission from the IAB-DU cell occur in non-overlapping frequency resources, if such indication is provided, or when simultaneous transmission/reception by the IAB-MT and transmission from the IAB-DU cell occur in overlapping frequency resources +- in a given slot, if that indication is provided + +For a serving cell of an IAB-MT, the IAB-MT can be provided a set of TCI states or a set of RS resource indexes corresponding to a SS/PBCH block or to a CSI-RS resource index for a slot where a PDSCH EPRE adjustment is indicated by DL Tx Power Adjustment MAC CE as described in [11, TS 38.321]. The PDSCH EPRE can be derived from a downlink CSI-RS EPRE as described in [6, TS 38.214] and a power offset provided by the *DL Tx Power adjustment* field in *DL TX Power Adjustment* MAC CE as described in [11, TS 38.321]. The downlink CSI-RS EPRE refers to the CSI-RS indicated by Reference CSI-RS ID in *DL Tx Power Adjustment* MAC CE as described in [11, TS 38.321]. The *DL TX Power Adjustment* provides the offset between PDSCH EPRE and CSI-RS EPRE. For a downlink DM-RS and/or PT-RS associated with a PDSCH, the IAB-MT may assume that the ratio of PDSCH EPRE to DM-RS EPRE, and/or PT-RS EPRE to PDSCH EPRE, is obtained as for a "UE" in [6, TS 38.214]. If no TCI state or RS resource index is provided to the IAB-MT, the IAB-MT may assume that a same PDSCH EPRE adjustment applies to all TCI states or RS resource indexes configured for the IAB-MT. A PDSCH EPRE adjustment provided by DL Tx Power Adjustment MAC CE may be associated with + +- multiplexing mode of the IAB-node, if provided, and/or +- when simultaneous reception by the IAB-MT and transmission/reception by an IAB-DU cell occur in non-overlapping frequency resources, if provided, or when simultaneous reception by the IAB-MT and transmission/reception by an IAB-DU cell occur in overlapping frequency resources, if provided, and/or +- slots indicated by slot indexes, if provided. + +# 15 Dual active protocol stack based handover + +If a UE indicates a capability for dual active protocol stack based handover (DAPS HO), the UE can be provided with a source MCG and a target MCG. + +If a UE is configured with a target MCG using NR radio access in FR1 or in FR2 and with a source MCG using NR radio access in FR2 or in FR1, respectively, the UE performs transmission power control independently per cell group as described in clauses 7.1 through 7.5. + +When a PDCCH reception by a UE includes two PDCCH candidates from corresponding search space sets, as described in clause 10.1, the end of the PDCCH reception is the end of the PDCCH candidate that ends later. + +If a UE is configured with a target MCG using NR radio access in FR1 and a source MCG using NR radio access in FR1, the UE is configured a maximum power for transmissions on the target MCG by *p-DAPS-Target* and a maximum power for transmissions on the source MCG by *p-DAPS-Source* and with an inter-CG power sharing mode by *uplinkPowerSharingDAPS-Mode*. The UE determines a transmission power on the target MCG and a transmission power on the source MCG per frequency range. + +If the UE indicates support for semi-static power sharing model and is provided *uplinkPowerSharingDAPS-Mode = Semi-static-model*, the UE determines a transmission power for the target MCG or for the source MCG as described in clause 7.6.2 for *nrdc-PCmode-FR1 = Semi-static-model* by considering the target MCG as the MCG and the source MCG as the SCG. + +If the UE indicates support for semi-static power sharing mode2 and is provided *uplinkPowerSharingDAPS-Mode = Semi-static-mode2*, the UE determines a transmission power for the target MCG or for the source SCG as described in clause 7.6.2 for *nrdc-PCmode-FR1 = Semi-static-mode2* by considering the target MCG as the MCG and the source MCG as the SCG. The UE expects to be provided *uplinkPowerSharingDAPS-Mode = Semi-static-mode2* only for synchronous DAPS HO operation [10, TS 38.133]. + +If the UE indicates support for dynamic power sharing and is provided *uplinkPowerSharingDAPS-Mode = Dynamic*, the UE determines a transmission power for the target MCG or for the source MCG as described in clause 7.6.2 for *nrdc-PCmode-FR1 = Dynamic* by considering the target MCG as the MCG and the source MCG as the SCG. + +Intra-frequency DAPS handover is described in clause 6.1.3.2 of [10, TS 38.133]. + +For DAPS handover that is not intra-frequency, if + +- the UE does not indicate support of *interFreqUL-TransCancellationDAPS-r16*, and +- UE does not indicate a capability for power sharing between source and target MCG in DAPS handover or the UE is not provided with *uplinkPowerSharingDAPS-Mode*, + +the UE does not expect transmissions on the target and source cell in overlapping time resources. + +For DAPS handover that is not intra-frequency, if + +- the UE indicates support of *interFreqUL-TransCancellationDAPS-r16*, and +- UE does not indicate a capability for power sharing between source and target MCG in DAPS handover or the UE is not provided with *uplinkPowerSharingDAPS-Mode*, and +- UE transmissions on the target cell and the source cell are in overlapping time resources, + +the UE transmits only on the target cell, and cancels the transmission to source cell. + +For intra-frequency DAPS handover, if + +- UE transmissions on the target cell and the source cell are in overlapping time resources, + +the UE transmits only on the target cell and cancels the transmission on the source cell. + +The UE does not expect to cancel a transmission on the source cell if a first symbol of the transmission on the source cell is less than $T_{prep}$ after a last symbol of a PDCCH reception where the UE receives a PDCCH providing a DCI format scheduling a transmission on the target cell. $T_{prep}$ is the PUSCH preparation time for the corresponding PUSCH processing capability [6, TS 38.214] assuming $\mu$ is a time duration corresponding to 2 symbols for SCS configuration $\mu$ , and $\mu$ is the smallest SCS configuration between the SCS configuration of the PDCCH providing the DCI format and the SCS configuration for the transmission on the source cell. If the UE transmits PRACH using 1.25 kHz or 5 kHz SCS on the source cell, the UE determines $T_{prep}$ assuming SCS configuration $\mu$ . + +A UE does not expect to cancel a transmission on the source cell if the first symbol of the source cell transmission occurs, relative to a last symbol of a PDSCH reception conveying a RAR message with a RAR UL grant on the target cell, after a number of symbols that is smaller than $T_{prep}$ msec, where $T_{prep}$ is a time duration of symbols corresponding to a PDSCH processing time for UE processing capability 1 when additional PDSCH DM-RS is configured, $T_{prep}$ is a time duration of symbols corresponding to a PUSCH preparation time for UE processing capability 1 [6, TS 38.214] and the + +UE considers that $\mu$ and $\mu_{target}$ correspond to the smaller of the SCS configurations for the PDSCH on the target cell and the transmission on the source cell. For $\mu$ , the UE assumes [6, TS 38.214]. + +For intra-frequency DAPS handover operation, the UE expects that an active DL BWP and an active UL BWP on the target cell are within an active DL BWP and an active UL BWP on the source cell, respectively. + +If a UE is provided search space sets on both the target MCG and the source MCG, in any slot the UE does not expect to have USS sets on both the target MCG and the source MCG that result in the number of monitored PDCCH candidates and the total number of non-overlapped CCEs in both cells that each exceed the corresponding maximum numbers per slot defined in Table 10.1-2 and Table 10.1-3. + +For DAPS operation in a same frequency band, a UE does not transmit PUSCH/PUCCH/SRS to the source MCG in a slot overlapping in time with a PRACH transmission to the target MCG or when a gap between a first or last symbol of a PRACH transmission to the target MCG in a first slot would be separated by less than $\mu$ symbols from a last or first symbol, respectively, of the PUSCH/PUCCH/SRS transmission to the source MCG in a second slot. For DAPS operation in a same frequency band, a UE does not transmit PRACH on the source MCG in a slot overlapping in time with a PUSCH/PUCCH/SRS transmission on the target MCG or when a gap between the first or last symbol of a PUSCH/PUCCH/SRS transmission on the target MCG is separated by less than $\mu$ symbols from a last or a first symbol, respectively, of a PRACH transmission on the source MCG. $\mu$ for $\mu$ , $\mu$ for $\mu$ , and $\mu$ is the SCS configuration of the active UL BWP for the PUSCH/PUCCH/SRS transmission. The PUSCH processing capability is the processing capability of source cell. + +# 16 UE procedures for sidelink + +A UE is provided by *SL-BWP-Config* or *SL-BWP-ConfigCommon* a BWP for SL transmissions (SL BWP) with numerology and resource grid determined as described in [4, TS 38.211]. + +For a resource pool within the SL BWP, + +- for operation without shared spectrum channel access, or for operation with shared spectrum channel access and when *sl-transmissionStructureForPSCCHandPSSCH* = 'contiguousRB', the UE is provided by *sl-NumSubchannel* a number of sub-channels where each sub-channel includes a number of contiguous RBs provided by *sl-SubchannelSize*. The first RB of the first sub-channel in the SL BWP is indicated by *sl-StartRB-Subchannel* +- for operation with shared spectrum channel access and when *sl-transmissionStructureForPSCCHandPSSCH* = 'interlaceRB', the UE is provided by *sl-NumSubchannel* a number of sub-channels where each sub-channel includes a number of interlaces, provided by *sl-numInterlacePerSubchannel*, and the interlaces have contiguous interlace indexes + +Available slots for a resource pool are provided by *sl-TimeResource* and occur with a periodicity of 10240 ms. For an available slot without S-SS/PSBCH blocks, SL transmissions can start from a first symbol indicated by *sl-StartSymbol* or, for operation with shared spectrum channel access, can start from a first symbol indicated by *sl-StartingSymbolFirst* or from a second symbol indicated by *sl-StartingSymbolSecond* [6, TS 38.214], and be within a number of consecutive symbols indicated by *sl-LengthSymbols*. For an available slot with S-SS/PSBCH blocks, the first symbol and the number of consecutive symbols is predetermined. + +The UE expects to use a same numerology in the SL BWP and in an active UL BWP in a same carrier of a same cell. If the active UL BWP numerology is different than the SL BWP numerology, the SL BWP is deactivated. + +A priority of a PSSCH according to NR radio access or according to E-UTRA radio access is indicated by a priority field in a respective scheduling SCI format. A priority of a PSSS/SSSS/PSBCH according to E-UTRA radio access is provided by *sl-SSB-PriorityEUTRA* [13, TS 36.213]. A priority of an S-SS/PSBCH block is provided by *sl-SSB-PriorityNR*. A priority of a PSFCH is determined as described in clause 16.2.4.2. + +A UE does not expect to be provided search space sets associated with CORESETs on more than one cell to monitor PDCCH for detection of DCI format 3\_0 or DCI format 3\_1. + +## 16.1 Synchronization procedures + +A UE receives the following SL synchronization signals in order to perform synchronization procedures based on S-SS/PSBCH blocks: SL primary synchronization signals (S-PSS) and SL secondary synchronization signals (S-SSS) [4, TS 38.211]. + +A UE assumes that reception occasions of a physical sidelink broadcast channel (PSBCH), S-PSS, and S-SSS are in consecutive symbols [4, TS 38.211] and form a S-SS/PSBCH block. + +For reception of a S-SS/PSBCH block, + +- for operation without shared spectrum channel access, or for operation with shared spectrum channel access and when *sl-NumberRepeatedSSB* is not provided and for RB-set , a UE assumes a frequency location corresponding to the subcarrier with index 66 in the S-SS/PSBCH block [4, TS 38.211], is provided by + - *sl-AbsoluteFrequencySSB*, for operation without shared spectrum channel access or when RB-set is the anchor RB-set that is the RB set that includes the S-SS/PSBCH block + - a corresponding value in *sl-AbsoluteFrequencySSB-NonAnchorList* when RB-set is a non-anchor RB-set +- for operation with shared spectrum channel access when *sl-NumberRepeatedSSB* is provided and in RB-set , a UE assumes a frequency location corresponding to the subcarrier with index 66 in the S-SS/PSBCH block [4, TS 38.211] is provided by +, where + - is a frequency location of a lowest S-SS/PSBCH block in RB-set , where is provided by + - *sl-AbsoluteFrequencySSB* when RB-set *j* is the anchor RB-set, + - a corresponding value in *sl-AbsoluteFrequencySSB-NonAnchorList* when RB-set is a non-anchor RB-set + - is an index of an S-SS/PSBCH block from repeated S-SS/PSBCH blocks in the frequency domain and within the RB-set , where , and is provided by a value in *sl-NumberRepeatedSSB* corresponding to RB-set ; + - is a number of resource blocks, provided by *sl-GapRepeatedSSB*, for a gap between two adjacent repeated S-SS/PSBCH blocks; + - is a number of resource blocks for a S-SS/PSBCH block transmission with SCS configuration . + +For operation with shared spectrum channel access, a UE attempts to transmit at least S-SS/PSBCH blocks in the slots including S-SS/PSBCH blocks in the anchor RB set. The UE applies CP extension to the first symbol of an S-SS/PSBCH block and within the first one or two symbols before the first symbol of the S-SS/PSBCH block according to an index [4, TS 38.211] provided by *sl-CP-Extension-SSB*. The UE assumes PRB(s) in an intra-cell guard band [6, TS 38.214] are not used for transmission of S-SS/PSBCH blocks. + +The UE assumes that a S-PSS symbol, a S-SSS symbol, and a PSBCH symbol have a same transmission power. The UE assumes a same numerology of the S-SS/PSBCH as for a SL BWP of the S-SS/PSBCH block reception, and that a bandwidth of the S-SS/PSBCH is within a bandwidth of the SL BWP. The UE assumes the subcarrier with index 0 in the S-SS/PSBCH block is aligned with a subcarrier with index 0 in an RB of the SL BWP. + +A UE is provided, by *sl-NumSSB-WithinPeriod*, a number of S-SS/PSBCH blocks in a period of 16 frames. The UE assumes that a transmission of the S-SS/PSBCH blocks in the period is with a periodicity of 16 frames. The UE determines indexes of slots that include S-SS/PSBCH block as +, where + +- index 0 corresponds to a first slot in a frame with SFN of the serving cell satisfying or DFN satisfying $(DFN \bmod 16) = 0$ +- is a S-SS/PSBCH block index within the number of S-SS/PSBCH blocks in the period, with +- is a slot offset from a start of the period to the first slot including S-SS/PSBCH block, provided by *sl-TimeOffsetSSB* +- is a slot interval between S-SS/PSBCH blocks, provided by *sl-TimeInterval* + +For operation with shared spectrum channel access and for each slot that includes S-SS/PSBCH blocks, a UE is provided, by *sl-NumAdditionalOccasionPerSSB*, a number of additional candidate S-SS/PSBCH block transmission + +occasions. When the UE determines to transmit S-SS/PSBCH blocks on additional candidate S-SS/PSBCH block transmission occasions, the UE attempts to transmit S-SS/PSBCH blocks at least in the anchor RB set. When , for S-SS/PSBCH block with index , the UE determines indexes of slots that include the additional candidate S-SS/PSBCH block transmission occasions as $+ +$ , where + +- is a slot gap, provided by *sl-TimeGapAdditionalOccasion*, for determining the additional candidate S-SS/PSBCH block transmission occasions, and +- is an index of the additional candidate S-SS/PSBCH block transmission occasions, with . + +For paired spectrum, an S-SS/PSBCH block can be transmitted/received only in a slot of an UL carrier. For unpaired spectrum, an S-SS/PSBCH block can be transmitted/received only in a slot of which all OFDM symbols are configured as UL by *tdd-UL-DL-ConfigurationCommon* of the serving cell if provided or *sl-TDD-Configuration* if provided or *sl-TDD-Config* of the received PSBCH if provided. If *tdd-UL-DL-ConfigurationCommon* and *sl-TDD-Configuration* are not provided for a spectrum indicated with only PC5 interface in Table 5.2E.1-1 in [TS 38.101-1], an S-SS/PSBCH block can be transmitted/received in any slot of the spectrum. + +For transmission of an S-SS/PSBCH block, a UE includes a bit sequence in the PSBCH payload to indicate *sl-TDD-Config* and provide a slot format over a number of slots. + +For paired spectrum, or if *tdd-UL-DL-ConfigurationCommon* and *sl-TDD-Configuration* are not provided for a spectrum indicated with only PC5 interface in Table 5.2E.1-1 in [TS 38.101-1], + +- are set to '1'; + +else + +- if *pattern1* is provided by *sl-TDD-Configuration* or *tdd-UL-DL-ConfigurationCommon*; if both *pattern1* and *pattern2* are provided by *sl-TDD-Configuration* or *tdd-UL-DL-ConfigurationCommon* as described in clause 11.1 +- are determined based on + - in *pattern1* as described in Table 16.1-1 for + - in *pattern1* and in *pattern2* as described in Table 16.1-2 for + +where and are as described in clause 11.1 + +- are the 7th to 1st LSBs of , respectively + - for , + - for , + +where + +- is the number of symbols in a slot: if *cyclicPrefix* = "ECP"; else, +- is 1 if , else is 0 +- is 1 if , else is 0 +- is the sidelink starting symbol index provided by *sl-StartSymbol* +- is the granularity of slots indication as described in Table 16.1-2 +- , , , , are the parameters of *tdd-UL-DL-ConfigurationCommon* as described in clause 11.1, or the parameters of *sl-TDD-Configuration* as defined in [12, TS 38.331] +- corresponds to SL SCS as defined in [4, TS 38.211] + +**Table 16.1-1: Slot configuration period when one pattern is indicated** + +| | Slot configuration period of pattern1 (msec) | +|------------|-----------------------------------------------------| +| 0, 0, 0, 0 | 0.5 | +| 0, 0, 0, 1 | 0.625 | +| 0, 0, 1, 0 | 1 | +| 0, 0, 1, 1 | 1.25 | +| 0, 1, 0, 0 | 2 | +| 0, 1, 0, 1 | 2.5 | +| 0, 1, 1, 0 | 4 | +| 0, 1, 1, 1 | 5 | +| 1, 0, 0, 0 | 10 | +| Reserved | Reserved | + +**Table 16.1-2: Slot configuration period and granularity when two patterns are indicated** + +| | Slot configuration period of pattern1 (msec) | Slot configuration period of pattern2 (msec) | Granularity in slots with different SCS | | | | +|------------|-----------------------------------------------------|-----------------------------------------------------|-----------------------------------------|--------|--------|---------| +| | | | 15kHz | 30 kHz | 60 kHz | 120 kHz | +| 0, 0, 0, 0 | 0.5 | 0.5 | | | | | +| 0, 0, 0, 1 | 0.625 | 0.625 | | | | | +| 0, 0, 1, 0 | 1 | 1 | | | 1 | | +| 0, 0, 1, 1 | 0.5 | 2 | | | | | +| 0, 1, 0, 0 | 1.25 | 1.25 | | | | | +| 0, 1, 0, 1 | 2 | 0.5 | | | | | +| 0, 1, 1, 0 | 1 | 3 | | | | | +| 0, 1, 1, 1 | 2 | 2 | | | | | +| 1, 0, 0, 0 | 3 | 1 | | | | | +| 1, 0, 0, 1 | 1 | 4 | | | | | +| 1, 0, 1, 0 | 2 | 3 | | 1 | | 2 | +| 1, 0, 1, 1 | 2.5 | 2.5 | | | | | +| 1, 1, 0, 0 | 3 | 2 | | | | | +| 1, 1, 0, 1 | 4 | 1 | | | | | +| 1, 1, 1, 0 | 5 | 5 | 1 | | 2 | 4 | +| 1, 1, 1, 1 | 10 | 10 | 1 | 2 | 4 | 8 | + +If a UE would transmit or receive an S-SS/PSBCH block, and the transmission or reception would overlap in time with transmissions or receptions on the sidelink using E-UTRA radio access, the UE transmits or receives the signal/channel with the higher priority. + +If a UE would transmit or receive sidelink synchronization signals for E-UTRA radio access, and the transmission or reception would overlap in time with sidelink transmissions or receptions using NR radio access, the UE transmits or receives the signal/channel with the higher priority. + +## 16.2 Power control + +### 16.2.0 S-SS/PSBCH blocks + +A UE determines a power for an S-SS/PSBCH block transmission occasion in slot $n$ , in the anchor RB-set if applicable, on active SL BWP of carrier as + +[dBm] + +where + +- is defined in [8-1, TS 38.101-1] +- is a value of *dl-P0-PSBCH-r17* if using the parameter is supported by the UE and the parameter is provided; else *dl-P0-PSBCH-r16* if provided; otherwise, +- is a value of *dl-Alpha-PSBCH*, if provided; else, + +- when the active SL BWP is on a serving cell , as described in clause 7.1.1 except that + - the RS resource is the one the UE uses for determining a power of a PUSCH transmission scheduled by a DCI format 0\_0 in serving cell when the UE is configured to monitor PDCCH for detection of DCI format 0\_0 in serving cell + - the RS resource is the one corresponding to the SS/PBCH block the UE uses to obtain MIB when the UE is not configured to monitor PDCCH for detection of DCI format 0\_0 in serving cell +- is a number of resource blocks for a S-SS/PSBCH block transmission with SCS configuration +- is a value of *sl-PowerOffsetAnchor*, if provided; otherwise, . + +For operation with shared spectrum channel access, after allocating power for transmission of each S-SS/PSBCH block in the anchor RB-set, the UE equally allocates power remaining from , if any, for transmission of each S-SS/PSBCH block in all non-anchor RB-sets within the SL BWP + +- if *dl-P0-PSBCH* is not provided, a power for transmission of each S-SS/PSBCH block in a non-anchor RB-set is +- otherwise, a power for transmission of each S-SS/PSBCH block in a non-anchor RB-set is . + +### 16.2.1 PSSCH + +A UE determines a power for a PSSCH transmission on a resource pool in symbols where a corresponding PSCCH is not transmitted in PSCCH-PSSCH transmission occasion on active SL BWP of carrier as: + +[dBm] + +where + +- is defined in [8-1, TS 38.101-1] +- is determined by a value of *sl-MaxTxPower* based on a priority level of the PSSCH transmission and a CBR range that includes a CBR measured in slot [6, TS 38.214]; if *sl-MaxTxPower* is not provided, then ; +- if *dl-P0-PSSCH-PSCCH* is provided + - [dBm] +- else + - [dBm] + +where + +- is a value of *dl-P0-PSSCH-PSCCH-r17* if using the parameter is supported by the UE and the parameter is provided; else *dl-P0-PSSCH-PSCCH-r16* if provided +- is a value of *dl-Alpha-PSSCH-PSCCH*, if provided; else, +- when the active SL BWP is on a serving cell , as described in clause 7.1.1 except that + - the RS resource is the one the UE uses for determining a power of a PUSCH transmission scheduled by a DCI format 0\_0 in serving cell when the UE is configured to monitor PDCCH for detection of DCI format 0\_0 in serving cell + - the RS resource is the one corresponding to the SS/PBCH block the UE uses to obtain MIB when the UE is not configured to monitor PDCCH for detection of DCI format 0\_0 in serving cell +- is a number of resource blocks for the PSSCH transmission occasion and is a SCS configuration +- if *sl-P0-PSSCH-PSCCH* is provided and if a SCI format scheduling the PSSCH transmission includes a cast type indicator field indicating unicast or is SCI format 2-C + - [dBm] +- else + +- [dBm] + +where + +- is a value of *sl-P0-PSSCH-PSCCH-r17*, if using the parameter is supported by the UE and the parameter is provided; else *sl-P0-PSSCH-PSCCH-r16* if provided +- is a value of *sl-Alpha-PSSCH-PSCCH*, if provided; else, +- , where + - is obtained from a PSSCH transmit power per RE summed over the antenna ports of the UE, higher layer filtered across PSSCH transmission occasions using a filter configuration provided by *sl-FilterCoefficient*, and + - is a RSRP, as defined in [7, TS 38.215], that is reported to the UE from a UE receiving the PSCCH-PSSCH transmission and is obtained from a PSSCH DM-RS using a filter configuration provided by *sl-FilterCoefficient* + - is a number of resource blocks for PSCCH-PSSCH transmission occasion and is a SCS configuration + +The UE splits the power equally across the antenna ports on which the UE transmits the PSSCH with non-zero power. + +A UE determines a power for a PSSCH transmission on a resource pool in the symbols where a corresponding PSCCH is transmitted in PSCCH-PSSCH transmission occasion on active SL BWP of carrier as + +[dBm] + +where is a number of resource blocks for the corresponding PSCCH transmission in PSCCH-PSSCH transmission occasion. + +The UE splits the power equally across the antenna ports on which the UE transmits the PSSCH with non-zero power. + +### 16.2.2 PSCCH + +A UE determines a power for a PSCCH transmission on a resource pool in PSCCH-PSSCH transmission occasion as + +[dBm] + +where + +- is specified in clause 16.2.1 +- is a number of resource blocks for the PSCCH transmission in PSCCH-PSSCH transmission occasion +- is a number of resource blocks for PSCCH-PSSCH transmission occasion + +For a PSCCH transmission by a UE on a dedicated SL PRS resource pool, a power of the PSCCH transmission in a slot is same as a power of SL PRS transmission by the UE in the slot. The UE determines the power as described in Clause 16.2.3A. + +For sidelink co-channel coexistence between E-UTRA and NR, and for NR PSCCH/PSSCH transmissions with SCS configuration in slots that overlap with an E-UTRA subframe on the sidelink, the UE transmits NR PSCCH/PSSCH in the earlier overlapping slot with a power that is larger than or equal to the power in the later overlapping slot. + +### 16.2.3 PSFCH + +A UE with scheduled PSFCH transmissions for HARQ-ACK information and conflict information, and capable of transmitting a maximum of PSFCHs, determines a number of simultaneous PSFCH transmissions and a power for a PSFCH transmission, on all the resource pools in PSFCH transmission occasion on active SL BWP of carrier as + +- if *dl-P0-PSFCH* is provided, + +[dBm] + +Where + +- is applicable for + - the PRB of the PSFCH transmission for operation without shared spectrum channel access, + - each PRB in the interlace of the PSFCH transmission for operation with shared spectrum channel access and *sl-PSFCH-Type* = 'type1', + - each PRB in the subset of PRBs in the second interlace of the PSFCH transmission for operation with shared spectrum channel access and *sl-PSFCH-Type* = 'type2' +- is a value of *dl-P0-PSFCH-r17*, if using the parameter is supported by the UE and the parameter is provided; else *dl-P0-PSFCH-r16* if provided +- is a value of *dl-Alpha-PSFCH*, if provided; else, + - when the active SL BWP is on a serving cell , as described in clause 7.1.1 except that + - the RS resource is the one the UE uses for determining a power of a PUSCH transmission scheduled by a DCI format 0\_0 in serving cell when the UE is configured to monitor PDCCH for detection of DCI format 0\_0 in serving cell + - the RS resource is the one corresponding to the SS/PBCH block the UE uses to obtain MIB when the UE is not configured to monitor PDCCH for detection of DCI format 0\_0 in serving cell + - if + - if , where is determined for PSFCH transmissions according to [8-1, TS 38.101-1] and + - for operation without shared spectrum channel access + - and [dBm] + - for operation with shared spectrum channel access and *sl-PSFCH-Type* = 'type1', where is the number of PRBs in the interlace for PSFCH transmission + - and [dBm], where the power on one PRB in the interlace for PSFCH transmission is + - for operation with shared spectrum channel access and *sl-PSFCH-Type* = 'type2', where is provided by *sl-PSFCH-Type2-DedicatedPRB*, is provided by *sl-PSFCH-Type2-PowerOffset*, and is the number of PRBs in the first interlace for all PSFCH transmissions after excluding PRBs for PSFCH transmissions as described in Clause 16.3.0 + - and [dBm], where the power on one PRB in the first interlace for PSFCH transmission is and the power on one PRB in the subset of PRBs in the second interlace for PSFCH transmission is , where is provided by *sl-PSFCH-Type2-PowerOffset* + - else + - UE autonomously determines PSFCH transmissions first with ascending order of corresponding priority field values as described in clause 16.2.4.2 over the PSFCH transmissions with HARQ-ACK information, if any, and then with ascending order of priority value over the PSFCH transmissions with conflict information, if any, such that where , for , is a number of PSFCHs with priority value for PSFCH with HARQ-ACK information and , for , is a number of PSFCHs with priority value for PSFCH with conflict information and is defined as + - the largest value satisfying where is determined according to [8-1, TS 38.101-1] for transmission of all PSFCHs in , if any + - for operation without shared spectrum channel access + - for operation with shared spectrum channel access and *sl-PSFCH-Type* = 'type1' + - for operation with shared spectrum channel access and *sl-PSFCH-Type* = 'type2', where is the number of PRBs in the first interlace for the PSFCH transmissions after excluding PRBs for PSFCH transmissions as described in Clause 16.3.0 + +- zero, otherwise + +and + +- [dBm] for operation without shared spectrum channel access +- [dBm] for operation with shared spectrum channel access and *sl-PSFCH-Type* = 'type1', where the power on one PRB in the interlace for PSFCH transmission is +- [dBm] for operation with shared spectrum channel access and *sl-PSFCH-Type* = 'type2', where the power on one PRB in the first interlace for PSFCH transmission is and the power on one PRB in the subset of PRBs in the second interlace for PSFCH transmission is , where is provided by *sl-PSFCH-Type2-PowerOffset* + +where is defined in [8-1, TS 38.101-1] and is determined for the PSFCH transmissions + +- else + - the UE autonomously selects PSFCH transmissions with ascending order of corresponding priority field values as described in clause 16.2.4.2 + - if , where is determined for the PSFCH transmissions according to [8-1, TS 38.101-1] + - [dBm] for operation without shared spectrum channel access + - and [dBm] + - for operation with shared spectrum channel access and *sl-PSFCH-Type* = 'type1', where is the number of PRBs in the interlace for the PSFCH transmission + - and [dBm], where the power on one PRB in the interlace for PSFCH transmission is + - for operation with shared spectrum channel access and *sl-PSFCH-Type* = 'type2', where is provided by *sl-PSFCH-Type2-DedicatedPRB*, is provided by *sl-PSFCH-Type2-PowerOffset*, and is the number of PRBs in the first interlace for all PSFCH transmissions after excluding PRBs for PSFCH transmissions as described in Clause 16.3.0 + - and [dBm], where the power on one PRB in the first interlace for PSFCH transmission is and the power on one PRB in the subset of PRBs in the second interlace for PSFCH transmission is , where is provided by *sl-PSFCH-Type2-PowerOffset* + - else + - the UE autonomously selects PSFCH transmissions in ascending order of corresponding priority field values as described in clause 16.2.4.2 over the PSFCH transmissions with HARQ-ACK information, if any, and then with ascending order of priority value over the PSFCH transmissions with conflict information, if any, such that where , , is a number of PSFCHs with priority value for PSFCH with HARQ-ACK information and , is a number of PSFCHs with priority value for PSFCH with conflict information and is defined as + - the largest value satisfying where is determined according to [8-1, TS 38.101-1] for transmission of all PSFCHs in , if any + - for operation without shared spectrum channel access + - for operation with shared spectrum channel access and *sl-PSFCH-Type* = 'type1' + - for operation with shared spectrum channel access and *sl-PSFCH-Type* = 'type2', where is the number of PRBs in the first interlace for the PSFCH transmissions after excluding PRBs for PSFCH transmissions as described in Clause 16.3.0 + - zero, otherwise + +and + +- [dBm] for operation without shared spectrum channel access + +- [dBm] for operation with shared spectrum channel access and *sl-PSFCH-Type* = 'type1', where the power on one PRB in the interlace for PSFCH transmission is +- [dBm] for operation with shared spectrum channel access and *sl-PSFCH-Type* = 'type2', where the power on one PRB in the first interlace for PSFCH transmission is and the power on one PRB in the subset of PRBs in the second interlace for PSFCH transmission is , where is provided by *sl-PSFCH-Type2-PowerOffset* + +where is determined for the simultaneous PSFCH transmissions according to [8-1, TS 38.101-1] + +- else + - [dBm] for operation without shared spectrum channel access + - [dBm] for operation with shared spectrum channel access and *sl-PSFCH-Type* = 'type1', where the power on one PRB in the interlace for PSFCH transmission is + - [dBm] for operation with shared spectrum channel access and *sl-PSFCH-Type* = 'type2', where the power on one PRB in the first interlace for PSFCH transmission is and the power on one PRB in the subset of PRBs in the second interlace for PSFCH transmission is , where is provided by *sl-PSFCH-Type2-PowerOffset* + +where the UE autonomously determines PSFCH transmissions with ascending order of corresponding priority field values as described in clause 16.2.4.2 over the PSFCH transmissions with HARQ-ACK information, if any, and then with ascending order of priority value over the PSFCH transmissions with conflict information, if any, such that and where is determined for the PSFCH transmissions according to [8-1, TS 38.101-1]. + +For resource pools configured with PSFCH resources overlapping in time, the UE either expects not to be provided with *dl-P0-PSFCH* or *dl-Alpha-PSFCH* in any of the resource pools, or expects to be provided with the same values of *dl-P0-PSFCH* and the same values of *dl-Alpha-PSFCH* for all the resource pools. + +### 16.2.3A SL PRS + +A UE determines a power for a SL PRS transmission on a resource pool in SL PRS transmission occasion on active SL BWP of carrier as: + +where, + +- is defined in [8-1, TS 38.101-1] +- is determined by a value of *sl-MaxTxPower* based on a priority level and a CBR range for a CBR measured in slot , where is the congestion control processing time [6, TS 38.214] ]; if *sl-MaxTxPower* is not provided, then + - if the resource pool is a shared SL PRS resource pool, the priority level is same for PSSCH and SL PRS + - if the resource pool is a dedicated SL PRS resource pool, the priority level is for SL PRS +- if a value for is provided + - [dBm] +- else + - [dBm] + +where + +- if the resource pool is a shared SL PRS resource pool, is a value of *dl-P0-PSSCH-PSCCH* or *dl-P0-PSSCH-PSCCH-r17*; else, if the resource pool is a dedicated SL PRS resource pool, is a value of *dl-P0-SLPRS* +- if the resource pool is a shared SL PRS resource pool, is a value of *dl-Alpha-PSSCH-PSCCH*, if provided, and if *dl-Alpha-PSSCH-PSCCH* is not provided; else, if the resource pool is a dedicated SL PRS resource pool, is provided by *dl-Alpha-SLPRS*, if provided, and if *dl-Alpha-SLPRS* is not provided + +- when the active SL BWP is on a serving cell , as described in clause 7.1.1 except that + - the RS resource is the one the UE uses for determining a power of a PUSCH transmission scheduled by a DCI format 0\_0 in serving cell when the UE is configured to monitor PDCCH for detection of DCI format 0\_0 in serving cell + - the RS resource is the one corresponding to the SS/PBCH block the UE uses to obtain MIB when the UE is not configured to monitor PDCCH for detection of DCI format 0\_0 in serving cell +- is a number of resource blocks for the SL PRS transmission occasion and is a SCS configuration for the SL PRS transmission +- if a value for is provided + - [dBm] +- else + - [dBm] + +where + +- if the resource pool is a shared SL PRS resource pool, is a value of *sl-P0-PSSCH-PSCCH* or *sl-P0-PSSCH-PSCCH-r17*; else, if the resource pool is dedicated for SL PRS transmissions, is a value of *sl-P0-SLPRS* +- if the resource pool is a shared SL PRS resource pool, is a value of *sl-Alpha-PSSCH-PSCCH*, if provided and if *sl-Alpha-PSSCH-PSCCH* is not provided; else, if the resource pool is a dedicated SL PRS resource pool, is provided by *sl-Alpha-SLPRS* +- , where + - is obtained + - if the resource pool is a shared SL PRS resource pool, from a PSSCH transmit power per RE summed over the antenna ports of the UE and higher layer filtered across PSSCH transmission occasions using a filter configuration provided by *sl-FilterCoefficient*, + - else, if the resource pool is a dedicated SL PRS resource pool, from a SL PRS transmit power per RE and higher layer filtered across SL PRS transmission occasions using a filter configuration provided by *sl-FilterCoefficient* + - is a RSRP, as defined in [7, TS 38.215], that is reported to the UE from a UE receiving the SL PRS transmission and is obtained + - if the resource pool is a shared SL PRS resource pool, from a PSSCH DM-RS using a filter configuration provided by *sl-FilterCoefficient* + - else, if the resource pool is a dedicated SL PRS resource pool, from a SL PRS using a filter configuration provided by *sl-FilterCoefficient* + - is a number of resource blocks for the SL PRS transmission occasion and is a SCS configuration for the SL PRS transmission + +### 16.2.4 Prioritization of transmissions/receptions + +#### 16.2.4.1 Simultaneous NR and E-UTRA transmission/reception + +If a UE + +- would transmit a first channel/signal using E-UTRA radio access and second channels/signals using NR radio access, and +- a transmission of the first channel/signal would overlap in time with a transmission of the second channels/signals, and + +- the priorities of the channels/signals are known to both E-UTRA radio access and NR radio access at the UE msec prior to the start of the earliest of the two transmissions, where and is based on UE implementation, + +the UE transmits only the channels/signals of the radio access technology with the highest priority + +- as determined by the SCI formats scheduling the transmissions, or +- as indicated by higher layers in case of a S-SS/PSBCH block or a sidelink synchronization signal using E-UTRA radio access, or +- as determined in clause 16.2.4.2 in case of PSFCH transmissions. + +If a UE + +- would respectively transmit or receive a first channel/signal using E-UTRA radio access and receive a second channel/signal or transmit second channels/signals using NR radio access, and +- a transmission or reception of the first channel/signal would respectively overlap in time with a reception of the second channel/signal or transmission of the second channels/signals, and +- the priorities of the channels/signals are known to both E-UTRA radio access and NR radio access at the UE msec prior to the start of the earliest transmission or reception, where and is based on UE implementation, + +the UE transmits or receives the channels/signals of the radio access technology with the highest priority + +- as determined by the SCI formats scheduling the transmissions, or +- as indicated by higher layers in case of a S-SS/PSBCH block or a sidelink synchronization signal using E-UTRA radio access, or +- as determined in clause 16.2.4.2 among PSFCH transmissions/receptions. + +#### 16.2.4.2 Simultaneous PSFCH transmission/reception + +For a PSFCH transmission or reception with HARQ-ACK information, a priority value for the PSFCH is equal to the priority value indicated by an SCI format 1-A associated with the PSFCH. + +For PSFCH transmission with conflict information, a priority value for the PSFCH is equal to the smallest priority value determined by the corresponding SCI format(s) 1-A for the conflicting resource(s). + +For PSFCH reception with conflict information, a priority value for the PSFCH is equal to the priority value determined by the corresponding SCI format 1-A for the conflicting resource. + +If a UE + +- would transmit PSFCHs and receive PSFCHs, and +- transmissions of the PSFCHs would overlap in time with receptions of the PSFCHs + +the UE transmits or receives only a set of PSFCHs corresponding to the smallest priority field value, as determined by a first set of SCI format 1-A and/or a second set of SCI format 1-A [5, TS 38.212] that are respectively associated with PSFCHs with HARQ-ACK information from the PSFCHs and PSFCHs with HARQ-ACK information from the PSFCHs when one or more of the PSFCHs provide HARQ-ACK information. If none of the PSFCHs and none of the PSFCHs provide HARQ-ACK information, the UE transmits or receives only a set of PSFCHs corresponding to the smallest priority value of the first set of PSFCHs and the second set of PSFCHs that are respectively associated with the PSFCHs and the PSFCHs when the PSFCHs provide conflict information. + +If a UE would transmit PSFCHs in a PSFCH transmission occasion, the UE first transmits PSFCHs with HARQ-ACK information from PSFCHs corresponding to the smallest priority field values from the priority field values, if any. Subsequently, the UE transmits remaining PSFCHs with conflict information corresponding to the smallest remaining priority field values from the priority field values, if any. + +For operation with shared spectrum channel access, if a UE does not support PSFCH transmission in non-contiguous RB sets, the UE selects for PSFCH transmission any contiguous RB set(s) that include PSFCH with the smallest priority value. + +If a UE indicates a capability to receive PSFCHs in a PSFCH reception occasion [18, TS 38.306], the UE first receives PSFCHs with HARQ-ACK information, if any, and subsequently receives PSFCHs with conflict information, if any. + +#### 16.2.4.3 Simultaneous SL and UL transmissions/receptions + +If a UE + +- would simultaneously transmit on the UL and on the SL in a carrier or in two respective carriers, and +- the UE is not capable of simultaneous transmissions on the UL and on the SL in the carrier or in the two respective carriers + +the UE transmits only on the link, UL or SL, with the higher priority. + +If a UE + +- would simultaneously transmit on the UL and receive on the SL in a carrier, or +- would simultaneously transmit on the UL and receive on the SL in two respective carriers and the UE is not capable of simultaneous transmission on the UL and reception on the SL in the two respective carriers + +the UE transmits on UL or receives on SL, with the higher priority. + +If a UE + +- is capable of simultaneous transmissions on the UL and on the SL in two respective carriers, +- would transmit on the UL and on the SL in the two respective carriers, +- the transmission on the UL would overlap with the transmission on the SL over a time period, and +- the total UE transmission power over the time period would exceed + +the UE + +- reduces the power for the UL transmission prior to the start of the UL transmission, if the SL transmission has higher priority than the UL transmission as determined in clause 16.2.4.3.1, so that the total UE transmission power would not exceed +- reduces the power for the SL transmission prior to the start of the SL transmission, if the UL transmission has higher priority than the SL transmission as determined in clause 16.2.4.3.1, so that the total UE transmission power would not exceed + +##### 16.2.4.3.1 Prioritizations for sidelink and uplink transmissions/receptions + +A UE performs prioritization between SL transmissions/receptions and UL transmissions after performing the procedures described in clause 9, clause 9.2.5, and clause 9.2.6, and in clause 6.1 of [6, TS 38.214]. + +PSFCH transmissions in a slot, as determined in clause 16.2.4.2, have a same priority value as the smallest priority value among PSSCH receptions with corresponding HARQ-ACK information provided by the PSFCH transmissions in the slot, if any, and among PSFCH transmissions with conflict information in the slot, if any, where each priority value is equal to the smallest priority value determined by corresponding SCI formats 1-A as described in clause 16.3. + +PSFCH receptions in a slot, as determined in clause 16.2.4.2, have a same priority value as the smallest priority value among PSSCH transmissions with corresponding HARQ-ACK information provided by the PSFCH receptions in the slot, if any, and among PSFCH receptions with conflict information in the slot, if any, where each priority value is equal to the priority value determined by corresponding SCI format 1-A as described in clause 16.3. + +A priority of S-SS/PSBCH block transmission or reception is provided by *sl-SSB-PriorityNR*. + +For prioritization between SL transmission or PSFCH/S-SS/PSBCH block reception and UL transmission other than a PRACH, or a PUSCH scheduled by an UL grant in a RAR and its retransmission, or a PUSCH corresponding to Type-2 random access procedure and its retransmission, or a PUCCH with sidelink HARQ-ACK information report + +- if the UL transmission is for a PUSCH or for a PUCCH with priority index 1, +- if *sl-PriorityThreshold-UL-URLLC* is provided + +- the SL transmission or reception has higher priority than the UL transmission if the priority value of the SL transmission or reception is smaller than *sl-PriorityThreshold-UL-URLLC*; otherwise, the UL transmission has higher priority than the SL transmission or reception +- else + - the UL transmission has higher priority than the SL transmission or reception +- else + - the SL transmission or reception has higher priority than the UL transmission if the priority value of the SL transmission(s) or reception is smaller than *sl-PriorityThreshold*; otherwise, the UL transmission has higher priority than the SL transmission or reception + +A PRACH transmission, or a PUSCH scheduled by an UL grant in a RAR and its retransmission, or a PUSCH for Type-2 random access procedure and its retransmission, or a PUCCH with HARQ-ACK information in response to successRAR, or a PUCCH indicated by a DCI format 1\_0 with CRC scrambled by a corresponding TC-RNTI has higher priority than a SL transmission or reception. + +A PUCCH transmission with a sidelink HARQ-ACK information report has higher priority than a SL transmission if a priority value of the PUCCH is smaller than a priority value of the SL transmission. The priority value of the PUCCH transmission is as described in clause 16.5. If the priority value of the PUCCH transmission is larger than the priority value of the SL transmission, the SL transmission has higher priority. + +A PUCCH transmission with a sidelink HARQ-ACK information report has higher priority than a PSFCH/S-SS/PSBCH block reception if a priority value of the PUCCH is smaller than a priority value of the SL reception. If the priority value of the PUCCH transmission is larger than the priority value of the PSFCH/S-SS/PSBCH block reception, the SL reception has higher priority. + +When one or more SL transmissions from a UE overlap in time with multiple non-overlapping UL transmissions from the UE, the UE performs the SL transmissions if at least one SL transmission is prioritized over all UL transmissions subject to the UE processing timeline with respect to the first SL transmission and the first UL transmission. + +When one or more UL transmissions from a UE overlap in time with multiple non-overlapping SL transmissions, the UE performs the UL transmissions if at least one UL transmission is prioritized over all SL transmissions subject to the UE processing timeline with respect to the first SL transmission and the first UL transmission. + +When one SL transmission overlaps in time with one or more overlapping UL transmissions, the UE performs the SL transmission if the SL transmission is prioritized over all UL transmissions subject to both the UE multiplexing and processing timelines with respect to the first SL transmission and the first UL transmission, where the UE processing timeline with respect to the first SL transmission and the first UL transmission is same as when one or more SL transmissions overlap in time with multiple non-overlapping UL transmissions. + +When one SL transmission overlaps in time with one or more overlapping UL transmissions, the UE performs the UL transmission if at least one UL transmission is prioritized over the SL transmission subject to both the UE multiplexing and processing timelines with respect to the first SL transmission and the first UL transmission, where the UE processing timeline with respect to the first SL transmission and the first UL transmission is same as when one or more SL transmissions overlap in time with multiple non-overlapping UL transmissions. + +### 16.2.5 SL Carrier Aggregation + +If a UE is configured for sidelink operation on multiple carriers, the UE applies the synchronization procedures in Clause 16.1 on each of the multiple carriers [12, TS 38.331]. + +If a UE would transmit S-SS/PSBCH blocks on multiple carriers, the UE determines a power for each S-SS/PSBCH block transmission as described in Clause 16.2.0. If the UE would transmit S-SS/PSBCH blocks that would overlap in time on respective carriers and a total power for the transmissions of the S-SS/PSBCH blocks would exceed [8-1, TS 38.101-1], the UE autonomously reduces a power for one or more of the S-SS/PSBCH blocks transmissions so that a resulting total power would not exceed . + +If a UE would transmit PSCCH/PSSCHs on multiple carriers, the UE determines a power for each PSCCH/PSSCH transmission as described in Clauses 16.2.1 and 16.2.2, respectively. If the UE would transmit PSCCH/PSSCHs that would overlap in time on respective carriers and a total power for the PSCCH/PSSCH transmissions would exceed , the UE reduces a power for a PSCCH/PSSCH transmission that has the largest priority value as determined by SCI formats + +provided by the PSCCHs scheduling the respective PSSCHs. If more than one PSCCH/PSSCH transmission have the largest priority value, the UE autonomously selects one of the more than one PSCCH/PSSCH transmissions to reduce a respective power. If, after the reduction of the power of the PSCCH/PSSCH transmission with the largest priority value, a total power exceeds , the UE drops the PSCCH/PSSCH transmission with the largest priority value, respectively, and repeats the procedure over the remaining PSCCH/PSSCH transmissions. + +If a UE would simultaneously transmit PSFCHs and receive PSFCHs on multiple carriers, the UE performs the procedures in Clause 16.2.4.2 by considering all the PSFCHs for transmission and all the PSFCHs for reception in order to determine either PSFCHs to transmit or PSFCHs to receive. If a UE would simultaneously transmit PSFCHs on multiple carriers, the UE performs the procedures for single carrier in Clause 16.2.3 by considering all the PSFCHs for transmission using a corresponding and in order to determine PSFCHs to transmit and a corresponding power per PSFCH transmission. The UE expects to be provided a (pre)configuration such that the PSFCH transmissions on the multiple carriers are with time resource alignment and a same power. + +A UE expects that *sl-StartSymbol*, *sl-LengthSymbols*, *cyclicPrefix*, and *subcarrierSpacing* are (pre)configured to have same respective values on multiple carriers. + +## 16.3 UE procedure for reporting and obtaining control information in PSFCH + +Control information provided by a PSFCH transmission includes HARQ-ACK information or conflict information. + +### 16.3.0 UE procedure for transmitting PSFCH with control information + +A UE can be indicated by an SCI format scheduling a PSSCH reception to transmit a PSFCH with HARQ-ACK information in response to the PSSCH reception. The UE provides HARQ-ACK information that includes ACK or NACK, or only NACK. + +A UE can be provided, by *sl-PSFCH-Period*, a number of slots in a resource pool for a period of PSFCH transmission occasion resources. If the number is zero, PSFCH transmissions from the UE in the resource pool are disabled. + +A UE can be enabled, by *sl-InterUE-CoordinationScheme2*, to transmit a PSFCH with conflict information in a resource pool. The UE can determine, based on an indication by a SCI format 1-A, a set of resources that includes one or more slots and resource blocks that are reserved for PSSCH transmission. If the UE determines a conflict for a reserved resource for PSSCH transmission, the UE provides conflict information in a PSFCH. + +A UE expects that a slot ) has a PSFCH transmission occasion resource if , where is defined in [6, TS 38.214], is a number of slots that belong to the resource pool within 10240 msec according to [6, TS 38.214], and is provided by *sl-PSFCH-Period*. + +A UE may be indicated by higher layers to not transmit a PSFCH that includes HARQ-ACK information in response to a PSSCH reception [11, TS 38.321]. + +If a UE receives a PSSCH in a resource pool and the HARQ feedback enabled/disabled indicator field in an associated SCI format 2-A/2-B/2-C has value 1 [5, TS 38.212], the UE provides the HARQ-ACK information in a PSFCH transmission in the resource pool. For operation without shared spectrum channel access, the UE transmits the PSFCH in a first slot that includes PSFCH resources and is at least a number of slots, provided by *sl-MinTimeGapPSFCH*, of the resource pool after a last slot of the PSSCH reception. For operation with shared spectrum channel access, the UE can attempt to transmit the PSFCH over a number of first slots, provided by *sl-candidatePSFCH-Occasions* and indexed from 1 to in ascending order in time, that include PSFCH resources and are at least a number of slots, provided by *sl-MinTimeGapPSFCH*, of the resource pool after a last slot of the PSSCH reception. The UE attempts to transmit PSFCH in a slot only when the UE fails to transmit PSFCH associated with the PSSCH in all previous slots for PSFCH within the slots. + +For operation without shared spectrum channel access, a UE is provided by *sl-PSFCH-RB-Set* a set of PRBs in a resource pool for PSFCH transmission with HARQ-ACK information in a PRB of the resource pool. A UE can be provided by *sl-RB-SetPSFCH* a set of PRBs in a resource pool for PSFCH transmission with conflict information in a PRB of the resource pool. A UE expects that different PRBs are (pre)configured for conflict information and HARQ-ACK information. For a number of sub-channels for the resource pool, provided by *sl-NumSubchannel*, and a number of PSSCH slots associated with a PSFCH slot that is less than or equal to , the UE allocates the PRBs from the PRBs to slot among the PSSCH slots associated with the PSFCH slot and sub-channel , where , , and the allocation starts in an ascending order of and continues in an ascending order of . The UE expects that is a multiple of . + +For operation with shared spectrum channel access, when *sl-PSFCH-Type* is not provided and within RB-set *i*, for the *k*-th candidate PSFCH transmission occasion, a UE determines a set of PRBs in a resource pool based on the *k*-th indication provided by *sl-PSFCH-RB-SetList* or *sl-RB-SetPSFCHList* for PSFCH transmission with HARQ-ACK information or conflict information, respectively. The UE expects that different PRBs are (pre)configured for conflict information and HARQ-ACK information. For a number of sub-channels in RB-set *i* and a number of PSSCH slots associated with a PSFCH slot that is less than or equal to *N*, the UE allocates the PRBs from the PRBs to slot *l* among the PSSCH slots associated with the PSFCH slot and sub-channel *j*, where *l*, *j*, and *i*, and the allocation starts in an ascending order of *l* and continues in an ascending order of *j*. The UE expects that *N* is a multiple of *M*. + +For operation with shared spectrum channel access, when *sl-PSFCH-Type* = 'type1' and within RB-set *i*, a UE determines, based on *sl-PSFCH-RB-SetList*, all PRBs of an interlace for one PSFCH transmission with HARQ-ACK information in the resource pool. Within RB-set *i*, the UE determines, based on *sl-RB-SetPSFCHList*, all PRBs of an interlace for one PSFCH transmission with conflict information in the resource pool. For the *k*-th candidate PSFCH transmission occasion, the UE determines a set of interlaces that includes a number of interlaces based on the *k*-th indication provided by *sl-PSFCH-RB-SetList* or *sl-RB-SetPSFCHList* for HARQ-ACK information or conflict information, respectively. The UE expects that different interlaces are determined for conflict information and HARQ-ACK information. The set of interlaces are indexed in an ascending order of interlace indexes. For each interlace of the set of interlaces, all PRBs in the interlace are available for PSFCH transmission. For a number of sub-channels in RB-set *i* and a number of PSSCH slots that is not larger than *N* and is associated with a slot for PSFCH transmission, the UE allocates the interlaces from the interlaces to slot *l* and sub-channel *j*, where *l*, *j*, and *i*. The allocation starts in an ascending order of *l* and continues in an ascending order of *j*. The UE expects that *N* is a multiple of *M*. + +For operation with shared spectrum channel access, when *sl-PSFCH-Type* = 'type2' and within RB-set *i*, a UE determines a subset of PRBs in a first interlace and, based on *sl-PSFCH-RB-SetList*, a subset of PRBs in a second interlace for a PSFCH transmission with HARQ-ACK information in a resource pool, or based on *sl-RB-SetPSFCHList*, a subset of PRBs in a second interlace for a PSFCH transmission with conflict information in a resource pool. An index of the first interlace is provided by *sl-PSFCH-Type2-CommonInterlace*. The PRBs in the second interlace are provided by *sl-PSFCH-Type2-DedicatedPRB* where, for the *k*-th candidate PSFCH transmission occasion, and for each interlace *l*, the UE determines PRBs based on the *k*-th indication provided by *sl-PSFCH-RB-SetList* or *sl-RB-SetPSFCHList* for HARQ-ACK information or conflict information, respectively. The UE expects that different subsets of PRBs are determined for conflict information and HARQ-ACK information. The UE expects that *N* is a multiple of *M*. For interlace *l*, the UE determines a PRB subset with index *j* to include PRBs *j*. The UE determines the PRB subsets by ordering the PRB subsets first in an ascending order of PRB subset index within an interlace and second in ascending order of interlace index. For a number of sub-channels in RB-set *i* and a number of slots for PSSCH transmissions that is not larger than *N* and is associated with a slot for PSFCH transmission, the UE allocates the PRB subsets from the PRB subsets to slot *l* among the slots for PSSCH transmissions that are associated with the slot and sub-channel *j* for PSFCH transmissions, where *l* and *j*. The allocation starts in an ascending order of *l* and continues in an ascending order of *j*. The UE expects that *N* is a multiple of *M*. + +The second OFDM symbol of PSFCH transmission in a slot is defined as *l*. + +For operation without shared spectrum channel access, a UE determines a number of PSFCH resources available for multiplexing HARQ-ACK or conflict information in a PSFCH transmission as *N* where *N* is a number of cyclic shift pairs for the resource pool provided by *sl-NumMuxCS-Pair* and, based on an indication by *sl-PSFCH-CandidateResourceType*, + +- if *sl-PSFCH-CandidateResourceType* is configured as *startSubCH*, and the PRBs are associated with the starting sub-channel of the corresponding PSSCH +- if *sl-PSFCH-CandidateResourceType* is configured as *allocSubCH*, and the PRBs are associated with the sub-channels of the corresponding PSSCH +- for conflict information, the corresponding PSSCH is determined based on *sl-PSFCH-Occasion* + +The PSFCH resources are first indexed according to an ascending order of the PRB index, from the PRBs, and then according to an ascending order of the cyclic shift pair index from the cyclic shift pairs. + +For operation with shared spectrum channel access and for the *k*-th candidate PSFCH transmission occasion, a UE determines a number of PSFCH resources available for multiplexing HARQ-ACK or conflict information in a PSFCH transmission as *N* where *N* is a number of cyclic shift pairs for the resource pool provided by *sl-NumMuxCS-Pair* and, based on an indication by *sl-PSFCH-CandidateResourceType* + +- if *sl-PSFCH-CandidateResourceType* is indicated as *startSubCH*, and the interlaces or PRB subsets are associated with the lowest sub-channel index within the RB-set with smallest index of the corresponding PSSCH + +- if *sl-PSFCH-CandidateResourceType* is indicated as *allocSubCH*, and where the sum is over all RB-sets including resources for the corresponding PSSCH, and the combinations of interlaces and RB-sets or PRB subsets are associated with the sub-channels of the corresponding PSSCH +- for conflict information, the corresponding PSSCH is determined based on *sl-PSFCH-Occasion* + +The PSFCH resources are first indexed according to an ascending order of the interlace or PRB subset index, second according to an ascending order of the RB-set index, and then according to an ascending order of the cyclic shift pair index from the cyclic shift pairs. The UE applies CP extension to the first symbol of a PSFCH and within the first one or two symbols before the first symbol of the PSFCH according to an index [4, TS 38.211] provided by *sl-CP-Extension-PSFCH*. + +A UE determines an index of a PSFCH resource for a PSFCH transmission with HARQ-ACK information in response to a PSSCH reception or with conflict information corresponding to a reserved resource as where is a physical layer source ID provided by SCI format 2-A/2-B/2-C [5, TS 38.212] scheduling the PSSCH reception, or by SCI format 2-A/2-B/2-C with corresponding SCI format 1-A reserving the resource from another UE to be provided with the conflict information. For HARQ-ACK information, is the identity of the UE receiving the PSSCH as indicated by higher layers if the UE detects a SCI format 2-A with Cast type indicator field value of "01"; otherwise, is zero. For conflict information, is zero. + +For operation with shared spectrum channel access, when *sl-PSFCH-Type* = 'type2', a PRB in the first interlace is excluded from the resources for a PSFCH transmission, if for or for any PRB in the PRB subset when the PRB subset is selected for PSFCH transmission, and for or for , where PRB and PRB are the largest and smallest PRB indexes, respectively, in the resources for the PSFCH transmission assuming PRB is excluded. + +For a PSFCH transmission with HARQ-ACK information or conflict information, a UE determines a value, for computing a value of cyclic shift [4, TS 38.211], from a cyclic shift pair index corresponding to a PSFCH resource index and from using Table 16.3-1. + +**Table 16.3-1: Set of cyclic shift pairs** + +| | Cyclic Shift Pair Index | | | | | | +|---|-------------------------|---|---|---|---|---| +| | 0 | 1 | 2 | 3 | 4 | 5 | +| 1 | 0 | - | - | - | - | - | +| 2 | 0 | 3 | - | - | - | - | +| 3 | 0 | 2 | 4 | - | - | - | +| 6 | 0 | 1 | 2 | 3 | 4 | 5 | + +For a PSFCH transmission with HARQ-ACK information, a UE determines a value, for computing a value of cyclic shift [4, TS 38.211], as in Table 16.3-2 if the UE detects a SCI format 2-A with Cast type indicator field value of "01" or "10" or a SCI format 2-C, or as in Table 16.3-3 if the UE detects a SCI format 2-B or a SCI format 2-A with Cast type indicator field value of "11". For a PSFCH transmission with conflict information, a UE determines a value for computing a value of cyclic shift [4, TS 38.211] as in Table 16.3-4. The UE applies one cyclic shift from a cyclic shift pair to a sequence used for the PSFCH transmission [4, TS 38.211]. + +**Table 16.3-2: Mapping of HARQ-ACK information bit values to a cyclic shift, from a cyclic shift pair, of a sequence for a PSFCH transmission when HARQ-ACK information includes ACK or NACK** + +| HARQ-ACK Value | 0 (NACK) | 1 (ACK) | +|-----------------------|----------|---------| +| Sequence cyclic shift | 0 | 6 | + +**Table 16.3-3: Mapping of HARQ-ACK information bit values to a cyclic shift, from a cyclic shift pair, of a sequence for a PSFCH transmission when HARQ-ACK information includes only NACK** + +| HARQ-ACK Value | 0 (NACK) | 1 (ACK) | +|-----------------------|----------|---------| +| Sequence cyclic shift | 0 | N/A | + +**Table 16.3-4: Mapping of conflict information bit values to a cyclic shift, from a cyclic shift pair, of a sequence for a PSFCH transmission** + +| Conflict information | Conflict information for a next in time reserved resource indicated in SCI | +|-----------------------|----------------------------------------------------------------------------| +| Sequence cyclic shift | 0 | + +A first UE determines a second UE for providing the conflict information to in a PSFCH as follows + +- if the first UE is an intended receiver of the second UE for a reserved resource of a PSSCH transmission in a slot, +- does not expect to perform reception on the sidelink due to half-duplex operation in the slot, +- the PSFCH occasion for resource conflict information of the second UE is not passed, +- the conflict information receiver flag in SCI format 1-A from the second UE is set to 1, if *sl-IndicationUE-B* = 'enabled', and +- determines to transmit to the second UE the PSFCH with the conflict information. + +A first UE determines a UE for providing the conflict information to in a PSFCH as follows + +- if, for a resource pool, *sl-TypeUE-A* is not provided, the first UE has been indicated a first reserved resource and a second reserved resource as resources for PSSCH reception or, if for a resource pool *sl-TypeUE-A* is provided, has been indicated at least the first reserved resource or the second reserved resource for PSSCH reception, +- detects a first SCI format 1-A that includes a first priority value, , and the first reserved resource for PSSCH transmission from a second UE, +- detects a second SCI format 1-A that includes a second priority value, , and the second reserved resource for PSSCH transmission from a third UE, and +- determines that the first and second resources overlap in time and frequency +- the PSFCH occasions for resource conflict information of the second UE and the third UE are not passed +- the conflict information receiver flag in SCI Format 1-A from the second UE and the third UE is set to 1, if *sl-IndicationUE-B* = 'enabled' +- determines the first SCI format 1-A and the second SCI format 1-A are not received later than *sl-MinTimeGapPSFCH* before the PSFCH occasion for conflict information +- determines to transmit to the second UE the PSFCH with the conflict information +- determines to transmit to either the second UE or the third UE the PSFCH with the conflict information, if + +The first UE can be provided conditions by *sl-OptionForCondition2-A-1* to determine conflict of reserved resources in a resource pool + +- if *sl-OptionForCondition2-A-1* = '0', the first UE can be provided by, *sl-Thres-RSRP-List* , a list of RSRP thresholds for each priority combination [6, TS 38.214] + - if the first UE is an intended receiver for PSSCH in a reserved resource of the second UE, the first UE determines a resource conflict if the RSRP [6, TS 38.214] of the third UE is above a threshold + - if the first UE is an intended receiver for PSSCH in a reserved resource of the third UE, the first UE determines a resource conflict if the RSRP of the second UE is above a threshold +- if *sl-OptionForCondition2-A-1* = '1', the first UE can be provided a value by *sl-DeltaRSRP-Thresh* + - if the first UE is an intended receiver for PSSCH in a reserved resource of the second UE, the first UE determines a resource conflict if , where and are the RSRP measurements from the first UE for the second UE and the third UE, respectively + +- if the first UE is an intended receiver for PSSCH in a reserved resource of the third UE, the first UE determines a resource conflict if + +If a UE transmits a PSFCH with conflict information corresponding to a reserved resource indicated in an SCI format 1-A, the UE transmits the PSFCH in the resource pool in a slot determined based on *sl-PSFCH-Occasion* + +- If *sl-PSFCH-Occasion* = '0', + - for operation without shared spectrum channel access, the UE transmits the PSFCH in a first slot that includes PSFCH resources and is at least a number of slots, provided by *sl-MinTimeGapPSFCH*, of the resource pool after a slot of a PSCCH reception that provides the SCI format 1-A. The PSFCH resource is in a slot that is at least slots [6, TS 38.214] before the resource associated with the conflict information; otherwise, the UE does not transmit the PSFCH with conflict information. + - for operation with shared spectrum channel access, the UE can attempt to transmit the PSFCH over a number of first slots, provided by *sl-candidatePSFCH-Occasions* and indexed from 1 to in ascending order in time, that include PSFCH resources and are at least a number of slots, provided by *sl-MinTimeGapPSFCH*, of the resource pool after a last slot of a PSCCH reception that provides the SCI format 1-A. If the PSFCH resource is in a slot within the slots that is at least slots before the resource associated with conflict information, the UE can attempt to transmit the PSFCH with conflict information in the slot; otherwise, the UE does not transmit the PSFCH with conflict information in the slot. +- If *sl-PSFCH-Occasion* = '1', + - for operation without shared spectrum channel access, the UE transmits the PSFCH in a latest slot that includes PSFCH resources and is at least slots of the resource pool before a slot of the resource associated with conflict information. The PSFCH resource is in a slot that is at least *sl-MinTimeGapPSFCH* slots after a slot of a PSCCH reception that provides the SCI format 1-A; otherwise, the UE does not transmit the PSFCH with conflict information. + - for operation with shared spectrum channel access, the UE can attempt to transmit the PSFCH over a latest number of slots, provided by *sl-candidatePSFCH-Occasions* and indexed from 1 to in ascending order in time, that include PSFCH resources and are at least slots of the resource pool before a slot of the resource associated with conflict information. If the PSFCH resource is in a slot that is at least *sl-MinTimeGapPSFCH* slots after a slot of a PSCCH reception that provides the SCI format 1-A, the UE can attempt to transmit the PSFCH with conflict information in the slot; otherwise, the UE does not transmit the PSFCH with conflict information in the slot. + +### 16.3.1 UE procedure for receiving PSFCH with control information + +A UE that transmitted a PSSCH scheduled by a SCI format 2-A/2-B/2-C that indicates HARQ feedback enabled, attempts to receive associated PSFCHs with HARQ-ACK information according to PSFCH resources determined as described in clause 16.3.0. The UE determines an ACK or a NACK value for HARQ-ACK information provided in each PSFCH resource as described in [8-4, TS 38.101-4]. The UE does not determine both an ACK value and a NACK value at a same time for a PSFCH resource. + +For each PSFCH reception occasion, from a number of PSFCH reception occasions, the UE generates HARQ-ACK information to report to higher layers. For operation with shared spectrum channel access, the UE attempts to receive PSFCH on PSFCH occasion(s), as described in clause 16.3.0, until the UE detects one PSFCH from each UE expected to transmit a PSFCH, or the UE attempts to receive PSFCH on all the PSFCH occasion(s). For generating the HARQ-ACK information, the UE can be indicated by a SCI format to perform one of the following + +- if the UE receives a PSFCH associated with a SCI format 2-A with Cast type indicator field value of "10" or a SCI format 2-C + - report to higher layers HARQ-ACK information with same value as a value of HARQ-ACK information that the UE determines from the PSFCH reception for operation without shared spectrum channel access, or from the PSFCH reception(s) on PSFCH reception occasion(s), as described in clause 16.3.0, for operation with shared spectrum channel access +- if the UE receives a PSFCH associated with a SCI format 2-A with Cast type indicator field value of "01" + - report an ACK value to higher layers if the UE determines an ACK value from at least one PSFCH reception occasion from the number of PSFCH reception occasions in PSFCH resources corresponding to every + +identity of UEs that the UE expects to receive corresponding PSSCHs as described in clause 16.3; otherwise, report a NACK value to higher layers + +- if the PSFCH reception occasion is associated with a SCI format 2-B or a SCI format 2-A with Cast type indicator field value of "11" +- report to higher layers an ACK value if the UE determines absence of PSFCH reception for the PSFCH reception occasion; otherwise, report a NACK value to higher layers + +A UE that transmitted SCI format 1-A, indicating one or more reserved resources in a resource pool enabled by *sl-InterUE-CoordinationScheme2*, attempts to receive associated PSFCH with conflict information in the resource pool with PSFCH resources that the UE determines as described in clause 16.3.0. If the UE determines presence of a resource conflict based on conflict information in a PSFCH reception, the UE reports the resource conflict to higher layers + +- if *sl-SlotLevelResourceExclusion* is not provided, the UE reports resources overlapping with a next in time reserved resource indicated by the SCI format 1-A +- if *sl-SlotLevelResourceExclusion* is provided, the UE reports resources in a slot of a next in time reserved resource indicated by the SCI format 1-A + +If a UE receives a PSFCH with conflict information corresponding to a reserved resource indicated in an SCI format 1-A, the UE receives the PSFCH in the resource pool in a slot determined based on *sl-PSFCH-Occasion* + +- if *sl-PSFCH-Occasion* = '0', + - for operation without shared spectrum channel access, the UE receives the PSFCH in a first slot that includes PSFCH resources and is at least a number of slots, provided by *sl-MinTimeGapPSFCH*, of the resource pool after a slot of a PSCCH transmission that provides the SCI format 1-A. The PSFCH resource is in a slot that is at least slots [6, TS 38.214] before the resource associated with the conflict information; otherwise, the UE does not receive the PSFCH with conflict information + - for operation with shared spectrum channel access, the UE attempts to receive the PSFCH on a number of first slots, provided by *sl-candidatePSFCH-Occasions* and indexed from 1 to in ascending order in time, that include PSFCH resources and are at least a number of slots, provided by *sl-MinTimeGapPSFCH*, of the resource pool after a last slot of a PSCCH reception that provides the SCI format 1-A, until the UE detects one PSFCH from each UE expected to transmit a PSFCH, or the UE attempts to receive PSFCH on all PSFCH occasions. If the PSFCH resource is in a slot that is at least slots before the resource associated with the conflict information, the UE can attempt to receive the PSFCH with conflict information in the slot; otherwise, the UE does not receive the PSFCH with conflict information in the slot +- if *sl-PSFCH-Occasion* = '1', + - for operation without shared spectrum channel access, the UE receives the PSFCH in a latest slot that includes PSFCH resources and is at least slots of the resource pool before a slot of the resource associated with conflict information. The PSFCH resource is in a slot that is at least *sl-MinTimeGapPSFCH* slots after a slot of a PSCCH transmission that provides the SCI format 1-A; otherwise, the UE does not receive the PSFCH with conflict information + - for operation with shared spectrum channel access, the UE attempts to receive the PSFCH on a number of latest slots, provided by *sl-candidatePSFCH-Occasions* and indexed from 1 to in ascending order in time, that include PSFCH resources and are at least slots of the resource pool before a slot of the resource associated with conflict information, until the UE detects one PSFCH from each UE expected to transmit a PSFCH, or the UE attempts to receive PSFCH on all PSFCH occasions. If the PSFCH resource is in a slot that is at least *sl-MinTimeGapPSFCH* slots after a slot of a PSCCH transmission that provides the SCI format 1-A, the UE can attempt to receive the PSFCH with conflict information in the slot; otherwise, the UE does not receive the PSFCH with conflict information in the slot. + +## 16.4 UE procedure for transmitting PSCCH + +A UE can be provided a number of symbols in a resource pool, by *sl-TimeResourcePSCCH*, starting from a second symbol that is available for SL transmissions in a slot, and a number of PRBs in the resource pool, by *sl-FreqResourcePSCCH*, starting from the lowest PRB index of the lowest sub-channel index, in an RB-set with a lowest + +index if applicable, of the associated PSSCH for a PSCCH transmission with a SCI format 1-A. For operation with shared spectrum channel access, + +- if *sl-TransmissionStructureForPSCCHandPSSCH* = 'interlaceRB', the PRBs for PSCCH are within the sub-channel with the lowest index and within the RB-set with the lowest index among the RB-set(s) for the associated PSSCH transmission, +- if *sl-TransmissionStructureForPSCCHandPSSCH* = 'contiguousRB', the PRBs for PSCCH are within the sub-channel with the lowest index in the RB-set with the lowest index among the RB-set(s) for the associated PSSCH transmission, and all PRBs in the sub-channel overlapping with intra-cell guard band [6, TS 38.214] are not used for PSCCH. + +A UE that transmits a PSCCH with SCI format 1-A using sidelink resource allocation mode 2 [6, TS 38.214] sets + +- "Resource reservation period" as an index in *sl-ResourceReservePeriodList* corresponding to a reservation period provided by higher layers [11, TS 38.321], if the UE is provided *sl-MultiReserveResource* +- the values of the frequency resource assignment field and the time resource assignment field as described in [6, TS 38.214] to indicate resources from a set of resources selected by higher layers as described in [11, TS 38.321] with smallest slot indices for such that , where: + - , where is a number of resources in the set with slot indices , such that , and is provided by *sl-MaxNumPerReserve* + - each resource, from the set of resources, corresponds to contiguous sub-channels and a slot in a set of slots , where is the number of sub-channels available for PSSCH/PSCCH transmission in a slot + - is a set of slots in a sidelink resource pool [6, TS 38.214] + - is an index of a slot where the PSCCH with SCI format 1-A is transmitted. + +A UE that transmits a PSCCH with SCI format 1-A using sidelink resource allocation mode 1 [6, TS 38.214] sets + +- the values of the frequency resource assignment field and the time resource assignment field for the SCI format 1-A transmitted in the -th resource for PSCCH/PSSCH transmission provided by a dynamic grant or by a SL configured grant, where and M is the total number of resources for PSCCH/PSSCH transmission provided by a dynamic grant or the number of resources for PSCCH/PSSCH transmission in a period provided by a SL configured grant type 1 or SL configured grant type 2, as follows: + - the frequency resource assignment field and time resource assignment field indicate the -th to -th resources as described in [6, TS 38.214]. + +For decoding of a SCI format 1-A, a UE may assume that a number of bits provided by *sl-NumReservedBits* can have any value as described in [4, TS 38.212]. + +## 16.4A UE procedure for transmitting PSCCH in dedicated SL PRS resource pool + +For a dedicated SL PRS resource pool, a UE can be provided a number of symbols in the resource pool, by *sl-TimeResourcePSCCH*, starting from a second symbol that is available for SL transmissions in a slot, and a number of PRBs in the resource pool, by *sl-FreqResourcePSCCH*, starting from a PRB with lowest index for a sub-channel determined according to an index of an associated SL PRS resource, for a PSCCH transmission with a SCI format 1-B. + +A UE that transmits a PSCCH with SCI format 1-B using SL PRS resource allocation mode 2 [6, TS 38.214] sets + +- "Source ID" as indicated by higher layers +- "Destination ID" as indicated by high layers +- "Cast type indicator" as indicated by higher layers +- "Resource reservation period" as an index in *sl-ResourceReservePeriodList* corresponding to a reservation period provided by higher layers [11, TS 38.321], if the UE is provided *sl-MultiReserveResource* + +- the values of the time resource assignment field and of the resource ID indication field as described in [6, TS 38.214] to indicate resources from a set of resources selected by higher layers as described in [11, TS 38.321] with smallest slot indices for such that , where: + - , where is a number of resources in the set with slot indices , , such that , and is provided by *sl-MaxNumPerReserve* + - each resource, from the set of resources, corresponds to a SL PRS resource and the corresponding PSCCH, and a slot in a set of slots + - is a set of slots in a sidelink resource pool [6, TS 38.214] + - is an index of a slot where the PSCCH with SCI format 1-B is transmitted. +- "SL PRS request" as indicated by higher layers + +A UE that transmits a PSCCH with SCI format 1-B using SL PRS resource allocation mode 1 [6, TS 38.214] sets + +- "Source ID" as indicated by higher layers +- "Destination ID" as indicated by high layers +- "Cast type indicator" as indicated by higher layers +- the values of the resource ID indication field and the time resource assignment field for the SCI format 1-B transmitted in the -th resource for SL PRS and the corresponding PSCCH transmission provided by a dynamic grant or by a SL configured grant, where and M is the total number of resources for SL PRS and the corresponding PSCCH transmission provided by a dynamic grant or the number of resources for SL PRS transmission in a period provided by a SL configured grant type 1 or SL configured grant type 2, as follows: + - the resource ID indication field and time resource assignment field indicate the -th to -th resources as described in [6, TS 38.214]. +- "SL PRS request" as indicated by higher layers + +For decoding of a SCI format 1-B, a UE may assume that a number of bits provided by *sl-NumReservedBits* can have any value as described in [4, TS 38.212]. + +## 16.5 UE procedure for reporting HARQ-ACK on uplink + +A UE can be provided PUCCH resources or PUSCH resources [12, TS 38.331] to report HARQ-ACK information that the UE generates based on HARQ-ACK information that the UE obtains from PSFCH receptions, or from absence of PSFCH receptions. The UE reports HARQ-ACK information on the primary cell of the PUCCH group, as described in clause 9, of the cell where the UE monitors PDCCH for detection of DCI format 3\_0. + +For SL configured grant Type 1 or Type 2 PSSCH transmissions by a UE within a time period provided by *sl-PeriodCG*, the UE generates one HARQ-ACK information bit in response to the PSFCH receptions to multiplex in a PUCCH transmission occasion that is after a last time resource, in a set of time resources. + +For PSSCH transmissions scheduled by a DCI format 3\_0, a UE generates HARQ-ACK information in response to PSFCH receptions to multiplex in a PUCCH transmission occasion that is after a last time resource in a set of time resources provided by the DCI format 3\_0. + +From a number of PSFCH reception occasions, the UE generates HARQ-ACK information to report in a PUCCH or PUSCH transmission. The UE can be indicated by a SCI format to perform one of the following and the UE constructs a HARQ-ACK codeword with HARQ-ACK information, when applicable + +- for one or more PSFCH reception occasions associated with SCI format 2-A with Cast type indicator field value of "10" + - generate HARQ-ACK information with same value as a value of HARQ-ACK information the UE determines from the last PSFCH reception from the number of PSFCH reception occasions corresponding to PSSCH transmissions or, if the UE determines that a PSFCH is not received at the last PSFCH reception occasion and ACK is not received in any of previous PSFCH reception occasions, generate NACK + +- for one or more PSFCH reception occasions associated with SCI format 2-A with Cast type indicator field value of "01" +- generate ACK if the UE determines ACK from at least one PSFCH reception occasion, from the number of PSFCH reception occasions corresponding to PSSCH transmissions, in PSFCH resources corresponding to every identity of the UEs that the UE expects to receive the PSSCH, as described in clause 16.3; otherwise, generate NACK +- for one or more PSFCH reception occasions associated with SCI format 2-B or SCI format 2-A with Cast type indicator field value of "11" +- generate ACK when the UE determines absence of PSFCH reception for the last PSFCH reception occasion from the number of PSFCH reception occasions corresponding to PSSCH transmissions; otherwise, generate NACK + +After a UE transmits PSSCHs and receives PSFCHs in corresponding PSFCH resource occasions, the priority value of HARQ-ACK information is same as the priority value of the PSSCH transmissions that is associated with the PSFCH reception occasions providing the HARQ-ACK information. + +The UE generates a NACK when, due to prioritization, as described in clause 16.2.4, the UE does not receive PSFCH in any PSFCH reception occasion associated with a PSSCH transmission in a resource provided by a DCI format 3\_0 and the UE transmitted PSSCH in the resource or, for a configured grant, in a resource provided in a single period and for which the UE is provided a PUCCH resource to report HARQ-ACK information and the UE transmitted PSSCH in the resource. The priority value of the NACK is same as the priority value of the PSSCH transmission. + +The UE generates a NACK when, due to prioritization as described in clause 16.2.4, the UE does not transmit a PSSCH in any of the resources provided by a DCI format 3\_0 or, for a configured grant, in any of the resources provided in a single period and for which the UE is provided a PUCCH resource to report HARQ-ACK information. The priority value of the NACK is same as the priority value of the PSSCH that was not transmitted due to prioritization. + +For operation with shared spectrum channel access, the UE generates a NACK when, due to a failed channel access procedure [15, TS 37.213], the UE does not transmit a PSSCH with a single TB in any of the resources provided by a DCI format 3\_0 or, for a configured grant, in any of the resources provided in a single period and for which the UE is provided a PUCCH resource to report HARQ-ACK information. The priority value of the NACK is same as the priority value of the PSSCH that was not transmitted due to the failed channel access procedure. + +The UE generates an ACK if the UE does not transmit a PSCCH with a SCI format 1-A scheduling a PSSCH in any of the resources provided by a configured grant in a single period and for which the UE is provided a PUCCH resource to report HARQ-ACK information. The priority value of the ACK is same as the largest priority value among the possible priority values for the configured grant. + +The UE generates an ACK if the UE does not transmit a PSCCH with a SCI format 1-A scheduling a PSSCH in any of the resources provided by a DCI format 3\_0 and for which the UE is provided a PUCCH resource to report HARQ-ACK information. The priority value of the ACK is same as the largest priority value among the possible priority values for the dynamic grant. + +For reporting HARQ-ACK information on uplink corresponding to one or multiple PSSCH transmissions with a corresponding SCI format with the field 'HARQ feedback enabled/disabled indicator' set to disabled, the UE generates HARQ-ACK information with the contents instructed by higher layer. The priority value of the HARQ-ACK information is same as the priority value of the PSSCH transmission. + +A UE does not expect to be provided PUCCH resources or PUSCH resources to report HARQ-ACK information that start earlier than after the end of a last symbol of a last PSFCH reception occasion if *numPSFCHOccasions* is not (pre-)configured, or of a last candidate PSFCH reception occasion if *numPSFCHOccasions* is (pre-)configured, from a number of PSFCH reception occasions if *numPSFCHOccasions* is not (pre-)configured, or from a number of candidate PSFCH reception occasions if *numPSFCHOccasions* is (pre-)configured, that the UE generates HARQ-ACK information to report in a PUCCH or PUSCH transmission, where + +- and are defined in [4, TS 38.211] +- , where is the SCS configuration of the SL BWP and is the SCS configuration of the active UL BWP on the primary cell +- is determined from according to Table 16.5-1 + +**Table 16.5-1: Values of** + +| | | +|---|----| +| 0 | 14 | +| 1 | 18 | +| 2 | 28 | +| 3 | 32 | + +For DCI format 3\_0, if present, the PSFCH-to-HARQ feedback timing indicator field values map to values for a set of number of slots provided by *sl-PSFCH-ToPUCCH* as defined in Table 16.5-2. + +**Table 16.5-2: Mapping of PSFCH-to-HARQ feedback timing indicator field values to numbers of slots** + +| PSFCH-to-HARQ feedback timing indicator | | | Number of slots $k$ | +|-----------------------------------------|--------|--------|-----------------------------------------------------------| +| 1 bit | 2 bits | 3 bits | | +| '0' | '00' | '000' | 1 st value provided by sl-PSFCH-ToPUCCH | +| '1' | '01' | '001' | 2 nd value provided by sl-PSFCH-ToPUCCH | +| | '10' | '010' | 3 rd value provided by sl-PSFCH-ToPUCCH | +| | '11' | '011' | 4 th value provided by sl-PSFCH-ToPUCCH | +| | | '100' | 5 th value provided by sl-PSFCH-ToPUCCH | +| | | '101' | 6 th value provided by sl-PSFCH-ToPUCCH | +| | | '110' | 7 th value provided by sl-PSFCH-ToPUCCH | +| | | '111' | 8 th value provided by sl-PSFCH-ToPUCCH | + +With reference to slots for PUCCH transmissions and for a number of PSFCH reception occasions if *numPSFCHOccasions* is not (pre-)configured, or candidate PSFCH reception occasions if *numPSFCHOccasions* is (pre-)configured, ending in slot $n$ , the UE provides the generated HARQ-ACK information in a PUCCH transmission within slot $n$ , subject to the overlapping conditions in clause 9.2.5, where $n$ is a number of slots indicated by a PSFCH-to-HARQ feedback timing indicator field, if present, in a DCI format indicating a slot for PUCCH transmission to report the HARQ-ACK information, or is provided by *sl-PSFCH-ToPUCCH* for a transmission scheduled by a DCI format or for a SL configured grant type 2, or by *sl-PSFCH-ToPUCCH-CG-Type1* for a SL configured grant type 1. $n$ corresponds to a last slot for a PUCCH transmission that would overlap with the last PSFCH reception occasion if *numPSFCHOccasions* is not (pre-)configured, or the last candidate PSFCH reception occasion if *numPSFCHOccasions* is (pre-)configured, assuming that the start of the sidelink frame is same as the start of the downlink frame [4, TS 38.211]. + +For a PSSCH transmission by a UE that is scheduled by a DCI format, or for a SL configured grant Type 2 PSSCH transmission activated by a DCI format, the DCI format indicates to the UE that a PUCCH resource is not provided when a value of the PUCCH resource indicator field is zero and a value of PSFCH-to-HARQ feedback timing indicator field, if present, is zero. For a SL configured grant Type 2 PSSCH transmission without a corresponding PDCCH, the DCI format activating the SL configured grant Type 2 indicates to the UE that a PUCCH resource is not provided when a value of the PUCCH resource indicator field is zero and a value of PSFCH-to-HARQ feedback timing indicator field, if present, is zero. For a SL configured grant Type 1 PSSCH transmission, a PUCCH resource can be provided by *sl-NIPUCCH-AN* and *sl-PSFCH-ToPUCCH-CG-Type1*. For transmission of HARQ-ACK information corresponding only to a SL configured grant Type 2 PSSCH transmission, including the PSSCH transmission(s) associated with the corresponding activation DCI format 3\_0, a UE can be provided a PUCCH resource by *sl-NIPUCCH-AN-Type2*. If a PUCCH resource is not provided, the UE does not transmit a PUCCH with generated HARQ-ACK information from PSFCH reception occasions. + +For a PUCCH transmission with HARQ-ACK information, a UE determines a PUCCH resource after determining a set of PUCCH resources from up to four PUCCH resource sets provided by *sl-PUCCH-Config*, for HARQ-ACK information bits, as described in clause 9.2.1. The PUCCH resource determination is based on a PUCCH resource indicator field [5, TS 38.212] in a last DCI format 3\_0, excluding DCI format 3\_0 for the SL configured grant Type 2 activation, among the DCI formats 3\_0 that have a value of a PSFCH-to-HARQ feedback timing indicator field indicating a same slot for the PUCCH transmission, that the UE detects and for which the UE transmits corresponding HARQ-ACK information in the PUCCH where, for PUCCH resource determination, detected DCI formats are indexed in an ascending order across PDCCH monitoring occasion indexes. + +The PUCCH resource indicator field values map to values of a set of PUCCH resource indexes, as described in clause 9.2.3. + +A UE transmits a PUCCH with HARQ-ACK information using PUCCH format 0 or PUCCH format 1 or PUCCH format 2 or PUCCH format 3 or PUCCH format 4 as described in clause 9.2.3. + +A UE does not expect to multiplex HARQ-ACK information for more than one SL configured grants in a same PUCCH. + +A priority value of a PUCCH transmission with one or more sidelink HARQ-ACK information bits is the smallest priority value for the one or more HARQ-ACK information bits. + +In the following, the CRC for DCI format 3\_0 is scrambled with a SL-RNTI or a SL-CS-RNTI. + +### 16.5.1 Type-1 HARQ-ACK codebook determination + +This clause applies if the UE is configured with *pdsch-HARQ-ACK-Codebook = semi-static*. + +If a UE is configured a SL configured grant Type 1, and the UE is configured a SL configured grant Type 2 or to monitor PDCCH for detection of DCI format 3\_0 with CRC scrambled by SL-RNTI or SL-CS-RNTI, and the UE is provided a set of slot timing values associated with a SL BWP by *sl-PSFCH-ToPUCCH* and *sl-PSFCH-ToPUCCH-CG-Type1*, the *sl-PSFCH-ToPUCCH-CG-Type1* is one of *sl-PSFCH-ToPUCCH*. + +A UE reports HARQ-ACK information for PSSCH transmissions with corresponding PSFCH reception occasions in slot $n$ only in a HARQ-ACK codebook that the UE includes in a PUCCH or PUSCH transmission in slot $n$ , where $n$ is a number of slots indicated by the PSFCH-to-HARQ feedback timing indicator field in a DCI format 3\_0 scheduling the PSSCH transmissions, or by a value of PSFCH-to-HARQ feedback timing indicator field in a DCI format 3\_0 activating a SL configured grant Type-2 transmission, or by a value of *sl-PSFCH-ToPUCCH-CG-Type1* for a SL configured grant Type-1. If the UE reports HARQ-ACK information for the PSSCH transmissions with corresponding PSFCH reception occasions in a slot other than slot $n$ , the UE sets a value for each corresponding HARQ-ACK information bit to NACK. + +If a UE reports HARQ-ACK information in a PUCCH only for + +- PSFCH reception occasions associated with PSSCH transmissions scheduled by a DCI format 3\_0 with counter SAI field value of 1, or +- PSFCH reception occasions associated with PSSCH transmissions corresponding to a SL configured grant + +within a set of occasions for candidate PSSCH transmissions with corresponding PSFCH reception occasions as determined in clause 16.5.1.1, the UE determines a HARQ-ACK codebook only for the PSFCH reception occasion associated with PSSCH transmissions scheduled by DCI format 3\_0 or only for the PSFCH reception occasion associated with PSSCH transmissions corresponding to a SL configured grant according to corresponding set of occasions, where a value of a counter SAI in DCI format 3\_0 is according to Table 16.5.2.1-1. Otherwise, the procedures in clause 16.5.1.1 and in clause 16.5.1.2 for a HARQ-ACK codebook determination apply. + +#### 16.5.1.1 Type-1 HARQ-ACK codebook in physical uplink control channel + +For a SL BWP on a carrier, and an active UL BWP on the primary cell, as described in clause 12, a UE determines a set of occasions for candidate PSSCH transmissions with corresponding PSFCH reception occasions for which the UE can multiplex corresponding HARQ-ACK information in a PUCCH transmission in slot $n$ . The determination is based on: + +- a set of slot timing values associated with the SL BWP where $n$ is provided by *sl-PSFCH-ToPUCCH* for DCI format 3\_0 or by *sl-PSFCH-ToPUCCH-CG-Type1* +- the ratio between the sidelink SCS configuration and the uplink SCS configuration provided by *subcarrierSpacing* in *SL-BWP-Config* or *SL-BWP-ConfigCommon* and *BWP-Uplink* for the SL BWP and the active UL BWP, respectively +- a configured sidelink resource pool bitmap +- a value of a period of PSFCH transmission occasion resources for a sidelink resource pool provided by a respective *sl-PSFCH-Period* + +For the set of slot timing values, the UE determines a set of occasions for candidate PSSCH transmissions with corresponding PSFCH reception occasions according to the following pseudo-code. + +Set $n$ - index of occasion for candidate PSSCH transmissions with corresponding PSFCH reception occasions + +Set + +Set $C$ to the cardinality of set + +Set $\text{set}$ – index of slot timing values , in descending order of the slot timing values, in set + +Set to the value of the period of PSFCH transmission occasion resources for the sidelink resource pool + +while $C$ + +if + +Set $\text{set}$ – index of a SL slot within an UL slot + +while + +if slot starts at a same time as or after a slot for an active UL BWP change on the serving cell of PUCCH transmission and slot is before the slot for the active UL BWP change on the serving cell of PUCCH transmission + +; + +else + +if slot belongs to the sidelink resource pool and includes PSFCH resources as indicated by a sidelink resource pool bitmap and *sl-PSFCH-Period*, where is the $k$ -th slot timing value in set + +Set $\text{set}$ – index of a SL slot within an PSFCH period + +while + +; + +; + +; + +end while + +end if + +; + +end if + +end while + +end if + +; + +end while + +The cardinality of the set defines a total number of occasions for candidate PSSCH transmissions with corresponding PSFCH reception occasions corresponding to the HARQ-ACK information bits. A UE determines HARQ-ACK information bits, for a total number of HARQ-ACK information bits as $\text{set} = \text{HARQ-ACK information bit for candidate PSSCH transmission with index with corresponding PSFCH reception, for , as described in clause 16.5. If the UE does not transmit a PSSCH in an occasion for candidate PSSCH transmission with corresponding PSFCH reception occasion, due to the UE not detecting a corresponding DCI format 3_0, the UE generates a NACK value for the occasion for candidate PSSCH transmission with corresponding PSFCH reception occasion.}$ + +If, the UE determines a number of HARQ-ACK information bits for obtaining a transmission power for a PUCCH, as described in clause 7.2.1, as where is a number of HARQ-ACK information bits determined for corresponding PSSCH transmissions with corresponding PSFCH reception occasions in PSFCH reception occasion . + +#### 16.5.1.2 Type-1 HARQ-ACK codebook in physical uplink shared channel + +If a UE would multiplex HARQ-ACK information in a PUSCH transmission that is not scheduled by a DCI format or is scheduled by a DCI format without an SAI field, then + +- if the UE + - has not received any PDCCH with a DCI format 3\_0 scheduling PSSCH transmissions with corresponding PSFCH reception occasions that the UE transmits corresponding HARQ-ACK information in the PUSCH, based on a value of a respective PSFCH-to-HARQ feedback timing indicator field in a DCI format scheduling the PSSCH transmissions or on the value of PSFCH-to-HARQ feedback timing indicator field in a DCI format 3\_0 activating a SL configured grant Type 2 transmission, or + - has not been provided PSSCH resources with corresponding PSFCH reception occasions that the UE transmits corresponding HARQ-ACK information based on the value of *sl-PSFCH-ToPUCCH-CG-Type1* for a SL configured grant Type 1, + +then in any of the set of occasions for candidate PSSCH transmissions with corresponding PSFCH reception occasions, as described in clause 16.5.1.1, the UE does not multiplex HARQ-ACK information in the PUSCH transmission; + +- else the UE generates the HARQ-ACK codebook as described in clause 16.5.1.1, unless the UE generates HARQ-ACK information only for + - PSFCH reception occasions associated with PSSCH transmissions corresponding to a SL configured grant, or + - PSFCH reception occasions associated with PSSCH transmissions that are scheduled by DCI format 3\_0 with a counter SAI field value of 1 + +in the set of occasions for candidate PSSCH transmissions with corresponding PSFCH reception occasions, in which case the UE generates HARQ-ACK information only for the PSFCH reception occasions as described in clause 16.5.1. + +A UE sets to NACK value in the HARQ-ACK codebook any HARQ-ACK information corresponding to PSFCH reception occasions associated with PSSCH transmissions scheduled by a DCI format 3\_0 that the UE detects in a PDCCH monitoring occasion that starts after a PDCCH monitoring occasion where the UE detects a DCI format scheduling the PUSCH transmission. + +If a UE multiplexes HARQ-ACK information in a PUSCH transmission that is scheduled by a DCI format that includes a SAI field, the UE generates the HARQ-ACK codebook as described in clause 16.5.1.1 when a value of the SAI field in the DCI format is . The UE does not generate a HARQ-ACK codebook for multiplexing in the PUSCH transmission when unless the UE generates HARQ-ACK information only for + +- PSFCH reception occasions associated with PSSCH transmissions corresponding to a SL configured grant, or +- PSFCH reception occasions associated with PSSCH transmissions that are scheduled by a DCI format 3\_0 with a counter SAI field value of 1, + +in the set of occasions for candidate PSSCH transmissions with corresponding PSFCH reception occasions as described in clause 16.5.1. + +if the SAI field in the DCI format is set to '0'; otherwise, . + +### 16.5.2 Type-2 HARQ-ACK codebook determination + +This clause applies if the UE is configured with *pdsch-HARQ-ACK-Codebook = dynamic*. + +#### 16.5.2.1 Type-2 HARQ-ACK codebook in physical uplink control channel + +A UE determines monitoring occasions for PDCCH with DCI format 3\_0 for scheduling PSSCH transmissions with associated PSFCH reception occasions on an active DL BWP of a serving cell , as described in clause 10.1, and for which the UE transmits HARQ-ACK information in a same PUCCH in slot based on + +- PSFCH-to-HARQ feedback timing indicator field values, or a value provided by *sl-PSFCH-ToPUCCH-CG-Type1*, for PUCCH transmission with HARQ-ACK information in slot in response to PSFCH receptions; + +- time gap field in DCI format 3\_0 for scheduling PSSCH transmissions with associated PSFCH receptions; +- time resource assignment in DCI format 3\_0 for scheduling PSSCH transmissions with associated PSFCH receptions; +- a configured sidelink resource pool bitmap; +- a value of a period of PSFCH resources provided in *sl-PSFCH-Period*; +- a value of a minimum time gap provided in *sl-MinTimeGapPSFCH*. + +The set of PDCCH monitoring occasions for DCI format 3\_0 for scheduling PSSCH transmissions with associated PSFCH reception occasions is defined as the PDCCH monitoring occasions in the active DL BWP of the configured serving cell, indexed in ascending order of start time of the associated search space sets. The cardinality of the set of PDCCH monitoring occasions defines a total number of PDCCH monitoring occasions. A UE is not expected to receive a DCI format 3\_0 with CRC scrambled by SL-RNTI and a DCI format 3\_0 with CRC scrambled by SL-CS-RNTI for scheduling retransmission corresponding to a SL configured grant Type 1 or a sidelink configured grant Type 2 simultaneously in a same monitoring occasion. + +A value of a counter sidelink assignment indicator (SAI) field in DCI format 3\_0, excluding DCI format 3\_0 for the SL configured grant Type 2 activation, denotes an accumulative number of PDCCH monitoring occasions where PSSCH transmissions with associated PSFCH receptions are scheduled, up to a current PDCCH monitoring occasion, in ascending order of PDCCH monitoring occasion index , where . + +Denote by the value of the counter SAI in DCI format 3\_0 in PDCCH monitoring occasion according to Table 16.5.2.1-1. + +If the UE transmits HARQ-ACK information in a PUCCH in slot , the UE determines the , for a total number of HARQ-ACK information bits, according to the following pseudo-code: + +Set – PDCCH with DCI format 3\_0 monitoring occasion index: lower index corresponds to earlier PDCCH with DCI format 3\_0 monitoring occasion + +Set + +Set + +Set + +Set to the number of PDCCH monitoring occasions + +while + +if PDCCH monitoring occasion is before an active UL BWP change on the serving cell of PUCCH transmission + +; + +else + +if there is a PSFCH reception occasion associated with a PSSCH transmission scheduled by a DCI format in PDCCH monitoring occasion + +if + +; + +end if + += HARQ-ACK information bit + +end if + +end if + +; + +end while + +for any + +if a SL configured grant Type 1 is configured for a UE, or a SL configured grant Type 2 is configured and activated for a UE, and the SL configured grant provides a grant for PSSCH transmissions, including the PSSCH transmission(s) associated with the corresponding activation DCI format 3\_0, with PSFCH reception occasions in a slot, where is the value for the SL configured grant as described in clause 16.5 + +; + += HARQ-ACK information bit associated with the PSFCH reception occasions associated with the PSSCH transmissions scheduled by the SL configured grant + +end if + +If, the UE determines a number of HARQ-ACK information bits for obtaining a transmission power for a PUCCH, as described in clause 7.2.1, as + +where + +- is a value of a counter SAI field in a last DCI format 3\_0, excluding the DCI format 3\_0 activating a SL configured grant, scheduling PSSCH transmissions associated with PSFCH reception occasions that the UE detects within the PDCCH monitoring occasions +- if the UE does not detect any DCI format 3\_0, excluding the DCI format 3\_0 activating a SL configured grant, scheduling PSSCH transmissions associated with PSFCH reception occasions in any of the PDCCH monitoring occasions +- is a total number of DCI format 3\_0, excluding the DCI format 3\_0 activating a SL configured grant, scheduling PSSCH transmissions associated with PSFCH reception occasions, that the UE detects within the PDCCH monitoring occasions. if the UE does not detect any DCI format 3\_0, excluding the DCI format 3\_0 activating a SL configured grant, scheduling PSSCH transmissions with associated PSFCH reception occasions in any of the PDCCH monitoring occasions +- is a number of DCI format 3\_0, excluding the DCI format 3\_0 activating a SL configured grant, scheduling PSSCH transmissions with associated PSFCH reception occasions that the UE detects in PDCCH monitoring occasion +- is a number of SL configured grants for which the UE transmits corresponding HARQ-ACK information in a same PUCCH as for HARQ-ACK information corresponding to PSFCH reception occasions associated with PSSCH transmissions scheduled by a dynamic grant within the PDCCH monitoring occasions + +**Table 16.5.2.1-1: Value of counter SAI in DCI format 3\_0** + +| SAI
MSB, LSB | | Number of PDCCH monitoring occasions in which DCI format 3_0 scheduling PSSCH transmissions with corresponding PSFCH reception occasions is present, denoted as and | +|-----------------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0,0 | 1 | | +| 0,1 | 2 | | +| 1,0 | 3 | | +| 1,1 | 4 | | + +#### 16.5.2.2 Type-2 HARQ-ACK codebook in physical uplink shared channel + +If a UE would multiplex HARQ-ACK information in a PUSCH transmission that is not scheduled by a DCI format or is scheduled by a DCI format without an SAI field, then + +- if the UE + - has not received any PDCCH within the monitoring occasions for DCI format 3\_0 for scheduling PSSCH with corresponding PSFCH reception occasions on any serving cell, and + - does not have HARQ-ACK information in response to a PSSCH transmission with corresponding PSFCH reception occasions associated with a SL configured grant to multiplex in the PUSCH, as described in clause 16.5.2.1, + +the UE does not multiplex HARQ-ACK information in the PUSCH transmission; + +- else, the UE generates and multiplexes in the PUSCH transmission the HARQ-ACK codebook as described in clause 16.5.2.1. + +If a UE multiplexes HARQ-ACK information in a PUSCH transmission that is scheduled by a DCI format that includes a SAI field, the UE generates the HARQ-ACK codebook as described in clause 16.5.2.1, with the following modifications: + +- For the pseudo-code for the HARQ-ACK codebook generation in clause 16.5.2.1, after the completion of the loop, the UE sets $\text{SAI\_counter} = \text{SAI\_field}$ where $\text{SAI\_field}$ is the value of the SAI field in the DCI format according to Table 16.5.2.2-1. + +If a UE + +- is scheduled for a PUSCH transmission by a DCI format that includes a SAI field with value $\text{SAI\_field}$ , and +- has not received any PDCCH within the monitoring occasions for PDCCH with DCI format 3\_0 for scheduling PSSCH with corresponding PSFCH reception occasions on a serving cell, and +- does not have HARQ-ACK information in response to PSFCH reception occasions associated with a SL configured grant to multiplex in the PUSCH, as described in clause 16.5.2.1, + +the UE does not multiplex HARQ-ACK information in the PUSCH transmission. + +**Table 16.5.2.2-1: Value of SAI** + +| SAI MSB, LSB | | Number of PDCCH monitoring occasions in which DCI format 3_0 scheduling PSSCH transmissions with corresponding PSFCH reception occasions is present, denoted as $\text{SAI\_field}$ | +|--------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0,0 | 1 | | +| 0,1 | 2 | | +| 1,0 | 3 | | +| 1,1 | 4 | | + +## 16.6 UE procedure for LTE sidelink transmission + +If the UE detects a DCI format 3\_1 with CRC scrambled by SL Semi-Persistent Scheduling V-RNTI in slot $n$ , the DCI format 3\_1 activates or releases an LTE sidelink SPS configuration that is indicated by a SL SPS configuration index field [5, TS 38.212]. If the DCI format 3\_1 activates an SL SPS configuration, the UE procedure for transmitting a PSCCH and a PSSCH is as described in [13, TS 36.213] except that a transmission starts no earlier than $n + \text{K}_{\text{offset}}$ ms, where $n$ is a start time of slot $n$ , and $\text{K}_{\text{offset}}$ are defined in [4, TS 38.211], $\text{K}_{\text{offset}}$ is a value indicated by a Timing offset field in DCI format 3\_1, and $\text{K}_{\text{offset}}$ is a value indicated by SL index field in DCI format 3\_1 if the SL index field is present; otherwise, $\text{K}_{\text{offset}} = 0$ . + +## 16.7 Operation for in-device coexistence and for co-channel coexistence + +If a UE would transmit or receive a first channel/signal using E-UTRA radio access and a second channel/signal using NR radio access, when + +- the first channel/signal and the second channel/signal are time-division multiplexed, and +- the UE knows the frame indexes of the first channel/signal and the frame indexes of the second channel/signal, + +the UE transmits or receives each channel/signal so that the subframe boundary of the second channel/signal is aligned with the subframe boundary of the first channel/signal where the subframe boundary alignment is achieved by UE implementation means. + +# 17 UE with reduced capabilities + +A UE with reduced capabilities (RedCap UE) supports all Layer-1 UE features that are mandatory without capability signalling, unless stated otherwise. Procedures for a RedCap UE are same as described for a UE in all other clauses of this document unless stated otherwise. + +## 17.1 First procedures for RedCap UE + +In this clause, the term 'UE' refers to a RedCap UE that indicates *supportOfRedCap* or *supportOfRedCap-r18*. + +A UE expects the initial DL BWP and the active DL BWP after the UE (re)establishes dedicated RRC connection to be smaller than or equal to the maximum DL bandwidth that the UE supports. A UE can be provided a DL BWP by *initialDownlinkBWP-RedCap* in *DownlinkConfigCommonSIB*, and an UL BWP by *initialUplinkBWP-RedCap* in *UplinkConfigCommonSIB*. If *initialUplinkBWP* in *UplinkConfigCommonSIB* indicates an UL BWP that is larger than a maximum UL BWP that a UE supports, the UE expects to be provided an UL BWP by *initialUplinkBWP-RedCap* in *UplinkConfigCommonSIB* that is smaller than or equal to the maximum UL bandwidth that the UE supports. + +For unpaired spectrum operation, a RedCap UE does not expect to receive a configuration where the center frequency for an initial DL BWP in which the UE is configured to monitor Type1-PDCCH CSS set, or a CSS set provided by *sdt-SearchSpace* for random-access based PUSCH transmission as described in clause 19.2, is different than the center frequency for an initial UL BWP in which the RedCap UE may transmit Msg1/Msg3 or MsgA. + +A UE can be provided by *BWP-DownlinkDedicated* a DL BWP, other than the initial DL BWP. A UE can be provided by *BWP-UplinkDedicated* an UL BWP, other than the initial UL BWP, that is smaller than or equal to the maximum UL bandwidth that the UE supports. + +If a UE is provided an UL BWP by *initialUplinkBWP-RedCap* in *UplinkConfigCommonSIB* and is provided *rach-ConfigCommon* or *msgA-ConfigCommon* in *BWP-UplinkCommon* for the UL BWP, the UE uses corresponding parameters to perform the procedures in clauses 8.1, 8.1A, and 8.3; otherwise, the UE uses corresponding parameters from *rach-ConfigCommon* or *msgA-ConfigCommon* in *BWP-UplinkCommon* for the UL BWP provided by *initialUplinkBWP*. + +If a UE is provided *initialUplinkBWP-RedCap* in *UplinkConfigCommonSIB* and does not have dedicated PUCCH resource configuration, the UE transmits PUCCH with HARQ-ACK information as described in clause 9.2.1 using a PUCCH resource set provided by *pucch-ResourceCommonRedCap*, except that frequency hopping for the PUCCH transmission is disabled if *intra-SlotFH* is present in *PUCCH-ConfigCommon*. If frequency hopping of the PUCCH transmission is disabled then, for the PUCCH transmission, the UE determines the initial cyclic shift index in the set of initial cyclic shift indexes as and determines the PRB index as + +- , if *intra-SlotFH* = 'fromLowerEdge' +- , otherwise + +where is provided by *additionalPRBOffset*, if provided; otherwise, + +If a UE is not provided *initialUplinkBWP-RedCap* in *UplinkConfigCommonSIB* and does not have dedicated PUCCH resource configuration, the UE transmits PUCCH with HARQ-ACK information as described in clause 9.2.1 using a PUCCH resource set provided by *pucch-ResourceCommonRedCap* if *pucch-ResourceCommonRedCap* is present or by *pucch-ResourceCommon* if *pucch-ResourceCommonRedCap* is absent. For an initial DL BWP provided by *initialDownlinkBWP-RedCap* in *DownlinkConfigCommonSIB*, if a UE in RRC\_IDLE state or in RRC\_INACTIVE state monitors PDCCH according to Type1-PDCCH CSS set and does not monitor PDCCH according to Type2-PDCCH CSS set, the UE does not expect the initial DL BWP to include SS/PBCH blocks and the CORESET with index 0. + +For an active DL BWP not provided by *BWP-DownlinkDedicated*, if a UE does not indicate a capability to operate in the active DL BWP without receiving an SS/PBCH block, the UE in RRC\_CONNECTED state assumes that the active + +DL BWP includes the SS/PBCH blocks that the UE used to obtain SIB1 and, for SS/PBCH block and CORESET multiplexing pattern 1, the CORESET with index 0. + +For an active DL BWP provided by *BWP-DownlinkDedicated*, unless a UE indicates a capability to operate in the active DL BWP without receiving an SS/PBCH block, the UE in RRC\_CONNECTED state assumes that the active DL BWP includes the SS/PBCH blocks that the UE used to obtain SIB1 or the SS/PBCH blocks provided by *NonCellDefiningSSB*. If the active DL BWP includes the SS/PBCH blocks that the UE used to obtain SIB1, for SS/PBCH block and CORESET multiplexing pattern 1, the UE expects the active DL BWP to include the CORESET with index 0. + +For a RedCap UE indicating a capability to use an initial DL BWP that includes the SS/PBCH blocks provided by *NonCellDefiningSSB* for PUSCH transmission in RRC\_INACTIVE state, if the UE is provided *NonCellDefiningSSB* in *ncd-SSB-RedCapInitialBWP-SDT*, then during procedure of PUSCH transmission in RRC\_INACTIVE state (as described in clause 19) the UE uses the SS/PBCH blocks provided by *NonCellDefiningSSB* for the purposes for which the UE would otherwise have used the SS/PBCH blocks that the UE used to obtain SIB1. + +If the active DL BWP provided by *BWP-DownlinkDedicated*, or the initial DL BWP during procedure of PUSCH transmission in RRC\_INACTIVE state (as described in clause 19), includes the SS/PBCH blocks provided by *NonCellDefiningSSB*, these SS/PBCH blocks and the SS/PBCH blocks that the UE used to obtain SIB1 have the same QCL properties, if they have the same index. + +For a RedCap UE indicated presence of SS/PBCH blocks within an active DL BWP by *NonCellDefiningSSB*, collision handling between downlink receptions or uplink transmissions and the SS/PBCH blocks are same as described for a UE indicated presence of SS/PBCH blocks by *ssb-PositionsInBurst* in *SIB1* or in *ServingCellConfigCommon* described in all other clauses, unless otherwise stated. + +For monitoring of a PDCCH candidate by a UE configured with *NonCellDefiningSSB*, if the UE + +- does not monitor PDCCH candidates in a Type0-PDCCH CSS set, and +- at least one RE for a PDCCH candidate overlaps with at least one RE of a candidate SS/PBCH block corresponding to a SS/PBCH block index provided by *NonCellDefiningSSB*, + +the UE is not required to monitor the PDCCH candidate. + +The SS/PBCH blocks in clause 8.1 for determining valid PRACH occasions in unpaired spectrum correspond to the SS/PBCH blocks that the UE used to obtain SIB1. + +The SS/PBCH blocks in clause 8.1A for determining valid PUSCH occasions in unpaired spectrum correspond to the SS/PBCH blocks that the UE used to obtain SIB1. + +The SS/PBCH blocks in clause 6.1.2.1 in [6, TS 38.214] and clause 8.3 for determining the slots for a PUSCH transmission in unpaired spectrum correspond to the SS/PBCH blocks that the UE used to obtain SIB1. + +The SS/PBCH blocks in clause 19.1 for determining valid PUSCH occasions in unpaired spectrum correspond to the SS/PBCH blocks that the UE used to obtain SIB1. + +## 17.1A Second procedures for RedCap UE + +In this clause, the term 'UE' refers to a RedCap UE that indicates *supportOfRedCap-r18*. + +A UE that has not indicated FG 48-2 does not expect to transmit a PUSCH over a bandwidth that is larger than 25 PRBs for 15 kHz SCS, or larger than 12 PRBs for 30 kHz SCS, per hop in a slot. + +A UE that has not indicated FG 48-2 does not expect to process a PDSCH reception that is scheduled by a DCI format with CRC scrambled by a C-RNTI, CS-RNTI, MCS-C-RNTI, G-RNTI for multicast, or G-CS-RNTI over a number of PRBs that is larger than 25 PRBs for 15 kHz SCS, or larger than 12 PRBs for 30 kHz SCS, in a slot. + +A UE that has not indicated FG 48-2 is not required to process a PDSCH reception in slot that is scheduled by a DCI format with CRC scrambled by a G-RNTI for broadcast or a MCCH-RNTI over a number of PRBs that is larger than 25 PRBs for 15 kHz SCS, or larger than 12 PRBs for 30 kHz SCS, when the PDSCH reception is with repetitions or when the UE receives another PDSCH in slot. + +A UE is not required to process a PDSCH reception that is scheduled by a DCI format with CRC scrambled by a TC-RNTI over a number of PRBs that is larger than 25 PRBs for 15 kHz SCS, or larger than 12 PRBs for 30 kHz SCS, in a slot. + +A UE does not expect to transmit a PUSCH over a bandwidth that is larger than 25 PRBs for 15 kHz SCS, or larger than 12 PRBs for 30 kHz SCS, per hop in a slot, where the PUSCH is scheduled by RAR UL grant or by a DCI scrambled by a TC-RNTI, or is configured for a Type-2 random access procedure. + +When + +- a UE receives a PDSCH scheduled by a DCI format with CRC scrambled by a RA-RNTI or a MsgB-RNTI over a number of PRBs that is larger than 25 PRBs for 15 kHz SCS or larger than 12 PRBs for 30 kHz SCS, and +- the PDSCH includes a RAR message with an RAR UL grant scheduling a Msg3 PUSCH transmission from the UE, as described in Clauses 8.2 and 8.2A + +the UE transmits the Msg3 PUSCH if a time between the last symbol of a PDSCH reception conveying the RAR message and the first symbol of the Msg3 PUSCH transmission is not smaller than msec for 15 kHz SCS or msec for 30 kHz SCS where and are defined in clause 8.3; otherwise, the UE behaviour is based on UE implementation. + +When + +- a UE receives a PDSCH scheduled by a DCI format with CRC scrambled by a RA-RNTI or a MsgB-RNTI over a number of PRBs that is larger than 25 PRBs for 15 kHz SCS or larger than 12 PRBs for 30 kHz SCS, and +- the UE does not correctly receive the transport block provided by the PDSCH, or if the higher layers at the UE do not identify a RAPID associated with a corresponding PRACH transmission from the UE + +if requested by higher layers, the UE shall be ready to transmit a PRACH no later than msec for 15 kHz SCS, or no later than msec for 30 kHz SCS, after the last symbol of the PDSCH reception, or after the last symbol of the window as described in Clauses 8.2 and 8.2A. + +When + +- a UE receives a PDSCH scheduled by a DCI format with CRC scrambled by MsgB-RNTI over a number of PRBs that is larger than 25 PRBs for 15 kHz SCS or larger than 12 PRBs for 30 kHz SCS, and +- the PDSCH includes a RAR message that is for successRAR for the UE as described in Clause 8.2A + +the UE transmits a PUCCH with HARQ-ACK information if a time between the last symbol of the PDSCH reception conveying the RAR message and the first symbol of the PUCCH transmission is not smaller than msec for 15 kHz SCS or msec for 30 kHz SCS; otherwise, the UE behaviour is based on UE implementation. + +## 17.2 Half-Duplex UE in paired spectrum + +A half-duplex UE (HD-UE) in paired spectrum is not capable of simultaneous transmissions and receptions on a serving cell with paired spectrum. This clause is applicable for communication of a HD-UE on a serving cell with paired spectrum. Procedures for a HD-UE are same as described for a UE in all other clauses of this document unless stated otherwise. + +A HD-UE does not expect to detect a DCI format scheduling a reception in a set of symbols and detect a DCI format scheduling a transmission in any symbol from the set of symbols. + +When a PDCCH reception by a UE includes two PDCCH candidates from corresponding search space sets, as described in clause 10.1, the end of the PDCCH reception is the end of the PDCCH candidate that ends later. + +If a HD-UE is configured by higher layers to receive a PDCCH, or PDSCH, or CSI-RS, or DL PRS in a set of symbols, the HD-UE receives the PDCCH, or PDSCH, or CSI-RS, or DL PRS if the HD-UE does not detect a DCI format that indicates to the HD-UE to transmit a PUSCH, or PUCCH, or PRACH, or SRS in at least one symbol of the set of symbols; otherwise, the HD-UE does not receive the PDCCH, or PDSCH, or CSI-RS, or DL PRS in the set of symbols. + +If a HD-UE is configured by higher layers to transmit SRS, or PUCCH, or PUSCH in a set of symbols and the UE detects a DCI format indicating to the HD-UE to receive CSI-RS or PDSCH in a subset of symbols from the set of symbols, then + +- the HD-UE does not expect to cancel the transmission of the PUCCH or PUSCH in the set of symbols if the first symbol in the set occurs within $T_{prep}$ relative to a last symbol of a PDCCH reception where the HD-UE detects the DCI format; otherwise, the HD-UE cancels the PUCCH, or the PUSCH, or an actual repetition of the PUSCH [6, TS 38.214], determined from clauses 9 and 9.2.5 or clause 6.1 of [6, TS 38.214]. +- the HD-UE does not expect to cancel the transmission of SRS in symbols from the subset of symbols that occur within $T_{prep}$ relative to a last symbol of a PDCCH reception where the HD-UE detects the DCI format. The HD-UE cancels the SRS transmission in remaining symbols from the subset of symbols. + +is the PUSCH preparation time for UE processing capability 1 [6, TS 38.214] assuming $T_{prep}$ and corresponds to the smallest SCS configuration between the SCS configuration of the PDCCH carrying the DCI format and the SCS configuration of the SRS, PUCCH, PUSCH. + +A HD-UE does not expect to receive both dedicated higher layer parameters configuring transmission in a set of symbols and dedicated higher layer parameters configuring reception in the set of symbols. A HD-UE does not expect to receive both a Type-0/0A/0B/1/2-PDCCH CSS set configuration for PDCCH reception in a set of symbols and dedicated higher layer parameters configuring transmission in the set of symbols, except Type-2-PDCCH CSS set configuration for PDCCH reception in a set of symbols and configured-grant based PUSCH transmission as described in clause 19.1 in the set of symbols for which case the UE follows the procedure as in clause 5.1B.2.6 in [10, TS 38.133]. The UE expects to be configured with a Type-2-PDCCH CSS set configuration for PDCCH reception such that there is at least one paging occasion that does not overlap with configured-grant based PUSCH transmission as described in clause 19.1 per SI modification period. + +If a HD-UE would transmit a PUSCH, or PUCCH, or SRS based on a configuration by higher layers and the HD-UE is indicated presence of SS/PBCH blocks within the active DL BWP by *ssb-PositionsInBurst* in *SIB1* or in *ServingCellConfigCommon* or by *NonCellDefiningSSB*, the HD-UE does not transmit + +- PUSCH or PUCCH if a last symbol of the PUSCH or PUCCH transmission would not be at least $T_{prep}$ prior to a first symbol of the next earliest SS/PBCH block [4, TS 38.211] +- PUSCH or PUCCH if a first symbol of the PUSCH or PUCCH transmission would not be at least $T_{prep}$ after a last symbol of the previous latest SS/PBCH block [4, TS 38.211] +- SRS in symbols that would not be at least $T_{prep}$ prior to a first symbol of the next earliest SS/PBCH block +- SRS in symbols that would not be at least $T_{prep}$ after a last symbol of the previous latest SS/PBCH block + +If a HD-UE would transmit a PRACH based on a detected DCI format, or PUSCH, or PUCCH, or SRS and the HD-UE is indicated presence of SS/PBCH blocks within the active DL BWP by *ssb-PositionsInBurst* in *SIB1* or in *ServingCellConfigCommon* or by *NonCellDefiningSSB* in a set of symbols, the HD-UE does not transmit PUSCH or PUCCH or PRACH if a transmission would overlap with any symbol from the set of symbols and the HD-UE does not transmit SRS in the set of symbols. + +If a HD-UE would transmit a PRACH or MsgA PUSCH triggered by higher layers in a set of symbols and would receive a PDCCH, or a PDSCH, or a CSI-RS, or a DL PRS, or is indicated presence of SS/PBCH blocks within the active DL BWP by *ssb-PositionsInBurst* in *SIB1* or in *ServingCellConfigCommon* or by *NonCellDefiningSSB* in symbols that include any symbol from the set of symbols, the HD-UE can select based on its implementation whether to either transmit the PRACH or the MsgA PUSCH or receive the PDSCH, or the CSI-RS, or the DL PRS, or the PDCCH, or the SS/PBCH blocks. + +If a HD-UE would receive a PDCCH, or a PDSCH, or a CSI-RS, or a DL PRS based on a configuration by higher layers or is indicated presence of SS/PBCH blocks within the active DL BWP by *ssb-PositionsInBurst* in *SIB1* or in *ServingCellConfigCommon* or by *NonCellDefiningSSB* in a set of symbols, and the HD-UE would transmit PRACH or MsgA PUSCH triggered by higher layers starting or ending at a symbol that is earlier or later than $T_{prep}$ , respectively, from the last or first symbol in the set of symbols, the HD-UE can select based on its implementation whether to either transmit the PRACH or the MsgA PUSCH or receive the PDSCH, or the CSI-RS, or the DL PRS, or the PDCCH, or the SS/PBCH blocks. + +# 18 Multicast Broadcast Services + +This clause is applicable only for PDCCH receptions, PDSCH receptions, and PUCCH transmissions for MBS on a serving cell. DCI formats with CRC scrambled by multicast-MCCH-RNTI for multicast PDSCH receptions in RRC\_INACTIVE state, G-RNTI for multicast, or G-CS-RNTI scheduling PDSCH receptions are referred to as + +multicast DCI formats and the PDSCH receptions are referred to as multicast PDSCH receptions. DCI formats with CRC scrambled by MCCH-RNTI or G-RNTI for broadcast scheduling PDSCH receptions are referred to as broadcast DCI formats and the PDSCH receptions are referred to as broadcast PDSCH receptions. HARQ-ACK information associated with multicast DCI formats or multicast PDSCH receptions in RRC\_CONNECTED state is referred to as multicast HARQ-ACK information. + +A UE can be provided one or more G-RNTIs for multicast per serving cell for scrambling the CRC of multicast DCI formats for scheduling PDSCH receptions. The UE can be provided one or more G-CS-RNTI per serving cell for scrambling the CRC of multicast DCI formats providing activation/release/scheduling retransmission for SPS PDSCH receptions in RRC\_CONNECTED state. + +A UE can be configured by *cfr-ConfigMCCH-MTCH* an MBS frequency resource for PDCCH and PDSCH receptions providing broadcast MCCH and broadcast MTCH [12, TS 38.331]; otherwise, the MBS frequency resource is same as for the CORESET with index 0 that is associated with the Type0-PDCCH CSS set for PDCCH and PDSCH receptions providing broadcast MCCH and broadcast MTCH. The SCS and CP of MBS frequency resource for broadcast are same as the initial DL BWP. A UE monitors PDCCH for scheduling PDSCH receptions for broadcast MCCH or broadcast MTCH as described in clause 10.1. + +In clauses referring to a higher layer parameter value provided by *PDCCH-ConfigCommon* or *PDSCH-ConfigMCCH/PDSCH-ConfigMTCH* for broadcast, when applicable a corresponding higher layer parameter value for broadcast MCCH/broadcast MTCH PDCCH receptions or PDSCH receptions, respectively, is provided as described in [12, TS 38.331]. + +A UE can be configured by *cfr-ConfigMCCH-MTCH-r18* an MBS frequency resource for PDCCH and PDSCH receptions providing multicast MCCH and multicast MTCH in RRC\_INACTIVE state [12, TS 38.331]; otherwise, the MBS frequency resource is same as for the CORESET with index 0 that is associated with the Type0-PDCCH CSS set for PDCCH and PDSCH receptions providing multicast MCCH and multicast MTCH in RRC\_INACTIVE state. A UE monitors PDCCH for scheduling PDSCH receptions for multicast MCCH or multicast MTCH in RRC\_INACTIVE state as described in clause 10.1. + +In clauses referring to a higher layer parameter value provided by *PDCCH-ConfigCommon* or *PDSCH-ConfigMCCH/PDSCH-ConfigMTCH* for multicast in RRC\_INACTIVE state, when applicable a corresponding higher layer parameter value for multicast MCCH/multicast MTCH PDCCH receptions or PDSCH receptions in RRC\_INACTIVE state, respectively, is provided as described in [12, TS 38.331]. + +A UE can be configured, per DL BWP by *cfr-ConfigMulticast*, an MBS frequency resource within the DL BWP for PDCCH and PDSCH receptions [4, TS 38.211]. If *cfr-ConfigMulticast* does not include *locationAndBandwidthMulticast*, the MBS frequency resource is the DL BWP. The SCS and CP of MBS frequency resource provided by *CFR-ConfigMulticast* are same as the associated DL BWP. In clauses referring to a higher layer parameter value provided by *PDCCH-Config* or *PDSCH-Config* or *SPS-Config* for a DL BWP, when applicable a corresponding higher layer parameter value for multicast PDCCH, PDSCH, or SPS PDSCH receptions is provided as described in [12, TS 38.331]. + +In clauses referring to a higher layer parameter value provided by a first or second *PUCCH-Config*, when applicable a corresponding higher layer parameter value for PUCCH transmissions associated with multicast PDCCH or PDSCH receptions is provided as described in [12, TS 38.331]. In clauses referring to a higher layer parameter value provided by *n1-PUCCH-AN* or *SPS-PUCCH-AN-List*, when applicable a corresponding higher layer parameter value for PUCCH transmissions associated with multicast SPS PDSCH receptions is provided as described in [12, TS 38.331]. In clauses referring to a higher layer parameter value provided by *pdsch-HARQ-ACK-Codebook* or *pdsch-HARQ-ACK-CodebookList*, when applicable a corresponding higher layer parameter value for HARQ-ACK codebooks associated with multicast HARQ-ACK information is provided as described in [12, TS 38.331]. + +A UE monitors PDCCH for scheduling PDSCH receptions or for activation/release of SPS PDSCH receptions for a corresponding SPS PDSCH configuration as described in clause 10.1. + +A UE can be configured by *harq-FeedbackOptionMulticast*, for a G-RNTI for multicast or for a G-CS-RNTI, to provide HARQ-ACK information for a transport block reception associated with the G-RNTI for multicast or with the G-CS-RNTI, according to the first HARQ-ACK reporting mode if *harq-FeedbackOptionMulticast* is set to 'ack-nack' or according to the second HARQ-ACK reporting mode if *harq-FeedbackOptionMulticast* is set to 'nack-only'. The UE determines a priority for a PUCCH transmission with multicast HARQ-ACK information according to any HARQ-ACK reporting mode as described in clause 9 for a PUCCH transmission with unicast HARQ-ACK information. + +For the first HARQ-ACK reporting mode, the UE generates HARQ-ACK information with ACK value when a UE correctly decodes a transport block; otherwise, the UE generates HARQ-ACK information with NACK value, as + +described in clauses 9 and 9.1 through 9.3. The UE determines a PUCCH or a PUSCH to provide the HARQ-ACK information as described in clause 9.2. + +For the second HARQ-ACK reporting mode, the UE does not transmit a PUCCH that would include only HARQ-ACK information with ACK values. The second HARQ-ACK reporting mode is not applicable for the first SPS PDSCH reception after activation of SPS PDSCH receptions for a SPS configuration. + +For the second HARQ-ACK reporting mode, when a number of HARQ-ACK information bits is one, a UE transmits a PUCCH only when the HARQ-ACK information bit has NACK value. The UE determines a PUCCH to provide the HARQ-ACK information as described in clause 9.2.1 or 9.2.3 when UE is not provided *moreThanOneNackOnlyMode*, or as the first PUCCH in Table 18-1 when UE is provided *moreThanOneNackOnlyMode*. For a PUCCH resource associated with PUCCH format 0, the UE transmits the PUCCH as described in [4, TS 38.211] by obtaining as described for HARQ-ACK information in clause 9.2.3 and by setting . For a PUCCH resource associated with PUCCH format 1, the UE transmits the PUCCH as described in [4, TS 38.211] by setting . + +A UE that is indicated '*nack-only*' by *harq-FeedbackOptionMulticast*, and for the case when the UE reports more than one HARQ-ACK information bits, the UE can be indicated to provide the HARQ-ACK information bits in a PUCCH either according to the first HARQ-ACK reporting mode when the UE is not provided *moreThanOneNackOnlyMode* or, for only one G-RNTI or only one G-CS-RNTI, according to the second HARQ-ACK reporting mode by selecting a PUCCH resource from a set of PUCCH resources for the PUCCH transmission based on the values of the HARQ-ACK information bits as described in Table 18-1 when the UE is provided *moreThanOneNackOnlyMode*. The UE generates HARQ-ACK information bits for the second HARQ-ACK reporting mode according to a Type-2 HARQ-ACK codebook as described in clause 9.1.3.1. For a PUCCH resource associated with PUCCH format 0, the UE transmits the PUCCH as described in [4, TS 38.211] by obtaining as described for HARQ-ACK information in clause 9.2.3 and by setting . For a PUCCH resource associated with PUCCH format 1, the UE transmits the PUCCH as described in [4, TS 38.211] by setting . + +For a UE that is indicated the second HARQ-ACK reporting mode, the UE does not expect to be provided *pdsch-HARQ-ACK-Codebook = semi-static* for multicast HARQ-ACK information. + +For a UE that is indicated the second HARQ-ACK reporting mode and *moreThanOneNackOnlyMode*, all PUCCH resources associated with the second HARQ-ACK reporting mode have same starting symbol and same number of symbols and, when PUCCH resources in Table 18-1 are located in more than one PRBs, the more than one PRBs are adjacent and are associated with a same MPR value [8-1, TS 38.101-1]. + +**Table 18-1: Mapping of values of HARQ-ACK information bits to PUCCH resources for the second HARQ-ACK reporting mode** + +| Value of HARQ-ACK information bits | | | | PUCCH resource | +|------------------------------------|-------|---------|-----------|----------------------------------------------------------------------------------------------| +| {0} | {0,0} | {0,0,0} | {0,0,0,0} | 1 st PUCCH resource from resourceListn1PUCCH-AN/sps-PUCCH-AN-ListMulticast | +| | {1,0} | {1,0,0} | {1,0,0,0} | 2 nd PUCCH resource from resourceList/sps-PUCCH-AN-ListMulticast | +| | {0,1} | {0,1,0} | {0,1,0,0} | 3 rd PUCCH resource from resourceList/sps-PUCCH-AN-ListMulticast | +| | | {1,1,0} | {1,1,0,0} | 4 th PUCCH resource from resourceList | +| | | {0,0,1} | {0,0,1,0} | 5 th PUCCH resource from resourceList | +| | | {1,0,1} | {1,0,1,0} | 6 th PUCCH resource from resourceList | +| | | {0,1,1} | {0,1,1,0} | 7 th PUCCH resource from resourceList | +| | | | {1,1,1,0} | 8 th PUCCH resource from resourceList | +| | | | {0,0,0,1} | 9 th PUCCH resource from resourceList | +| | | | {1,0,0,1} | 10 th PUCCH resource from resourceList | +| | | | {0,1,0,1} | 11 th PUCCH resource from resourceList | +| | | | {1,1,0,1} | 12 th PUCCH resource from resourceList | +| | | | {0,0,1,1} | 13 th PUCCH resource from resourceList | +| | | | {1,0,1,1} | 14 th PUCCH resource from resourceList | +| | | | {0,1,1,1} | 15 th PUCCH resource from resourceList | + +If a UE is provided *pucch-ConfigurationListMulticast1* or *pucch-ConfigurationListMulticast2* for PUCCH transmissions with a priority value, the UE transmits a PUCCH with the priority value according to *pucch-ConfigurationListMulticast1* or *pucch-ConfigurationListMulticast2* for each G-RNTI for multicast or G-CS-RNTI that the UE provides associated HARQ-ACK information according to the first HARQ-ACK reporting mode or the second HARQ-ACK reporting mode, respectively. For HARQ-ACK information associated only with the second HARQ-ACK reporting mode and for more than one HARQ-ACK information bit, when the UE is not provided *moreThanOneNackOnlyMode* and the UE provides the HARQ-ACK information according to the first HARQ-ACK reporting mode, the UE determines a PUCCH resource from *pucch-ConfigMulticast1/pucch-ConfigurationListMulticast1*, if provided; otherwise, the UE determines a PUCCH resource from *pucch-Config/pucch-ConfigurationList* as described in clause 9.2.3. + +A PDSCH reception providing an initial transmission of a transport block is scheduled only by a multicast DCI format. For the first HARQ-ACK reporting mode, a PDSCH reception providing a retransmission of the transport block can be scheduled either by a multicast DCI format using a same G-RNTI for multicast as the G-RNTI for multicast of the initial transmission of the transport block, or by a unicast DCI format using a C-RNTI [6, TS 38.214]. + +An activation for SPS PDSCH receptions using a G-CS-RNTI for a corresponding SPS PDSCH configuration is provided only by a multicast DCI format as described in clause 10.2 by replacing CS-RNTI with the G-CS-RNTI. A release for SPS PDSCH receptions using a G-CS-RNTI for a corresponding SPS PDSCH configuration is provided by a multicast DCI format as described in clause 10.2 by replacing CS-RNTI with the G-CS-RNTI, or by a DCI format with CRC scrambled by CS-RNTI. For the first HARQ-ACK reporting mode and for a transport block that a UE received in a SPS PDSCH, a PDSCH reception providing a retransmission of the transport block can be scheduled either by a unicast DCI format using a CS-RNTI or by a multicast DCI format using a same G-CS-RNTI as the G-CS-RNTI of the initial transmission of the transport block [6, TS 38.214]. + +For a DCI format indicating SPS PDSCH release, the UE provides the associated HARQ-ACK information as described in clause 9.1. + +A UE can be configured per G-RNTI for multicast or per G-CS-RNTI, by *harq-FeedbackEnablerMulticast* with value set to 'enabled', to provide HARQ-ACK information for PDSCH receptions. When the UE is not provided *harq-FeedbackEnablerMulticast* for a G-RNTI for multicast or G-CS-RNTI and *pdsch-HARQ-ACK-Codebook* = *dynamic* for multicast HARQ-ACK information, the UE does not provide HARQ-ACK information for respective PDSCH receptions. If a UE is provided *harq-FeedbackEnablerMulticast* with value set to 'dci-enabler' for a G-RNTI for multicast or a G-CS-RNTI, the UE provides HARQ-ACK information for PDSCH receptions scheduled by multicast DCI format 4\_1 associated with the G-RNTI or the G-CS-RNTI, and determines whether or not to provide the HARQ-ACK information for PDSCH receptions scheduled or activated by multicast DCI format 4\_2 based on an indication by the multicast DCI format 4\_2 associated with the G-RNTI for multicast or the G-CS-RNTI [4, TS 38.212]. If a UE is provided *pdsch-HARQ-ACK-Codebook* = *semi-static* for multicast HARQ-ACK information, the UE does not expect to be provided *harq-FeedbackEnablerMulticast* with value set to 'dci-enabler' for a G-RNTI for multicast or a G-CS-RNTI. + +If a UE would multiplex second multicast HARQ-ACK information according to the second HARQ-ACK reporting mode with first multicast HARQ-ACK information according to the first HARQ-ACK reporting mode, or unicast HARQ-ACK information, or CSI reports in a first PUCCH or in a PUSCH, as described in clauses 9 and 9.2.5, the UE provides the second HARQ-ACK information according to the first HARQ-ACK reporting mode. If the UE would multiplex the second multicast HARQ-ACK information, for resolving an overlapping among a second PUCCH with the second HARQ-ACK information and other PUCCHs or PUSCHs prior to multiplexing the second HARQ-ACK information in a PUCCH or PUSCH, the UE considers that the UE would transmit the second PUCCH when all values of the HARQ-ACK information are 'ACK'. If the UE would multiplex the second multicast HARQ-ACK information, for resolving an overlapping among a second PUCCH with the second HARQ-ACK information and other PUCCHs or PUSCHs prior to multiplexing the second HARQ-ACK information in a PUCCH or PUSCH when the UE is provided *moreThanOneNackOnlyMode*, the UE considers that the UE would transmit the second PUCCH using any PUCCH resource from the PUCCH resources associated with the second HARQ-ACK reporting mode when all values of the second HARQ-ACK information are 'ACK'. + +If a UE would only transmit a first PUCCH with only positive SR and a second PUCCH with HARQ-ACK information according to the second HARQ-ACK reporting mode, where the first and second PUCCHs would overlap in time in a slot and have same priority index, it is up to UE implementation for the UE to transmit either the first PUCCH or the second PUCCH. + +If a UE is provided multiple G-RNTIs for multicast or G-CS-RNTIs, a configuration for a HARQ-ACK codebook type applies to all G-RNTIs for multicast or G-CS-RNTIs. + +If a UE is provided *pdsch-HARQ-ACK-Codebook* = *semi-static* for multicast HARQ-ACK information, the UE generates a Type-1 HARQ-ACK codebook as described in clauses 9.1.2, 9.1.2.1, and 9.1.2.2. + +If a UE is provided *pdsch-HARQ-ACK-Codebook* = *dynamic* for multicast HARQ-ACK information, the UE generates a Type-2 HARQ-ACK codebook as described in clauses 9.1.3.1 and 9.1.3.2. + +If a UE would report unicast HARQ-ACK information and multicast HARQ-ACK information with same priority index in a slot, the UE multiplexes the unicast HARQ-ACK information and the multicast HARQ-ACK information following the procedures in this clause and in clauses 9.1.2, 9.1.3, and 9.1.4. + +If, for unicast and multicast HARQ-ACK information of same priority value, a UE + +- is provided + - either *pdsch-HARQ-ACK-Codebook* = *dynamic* or *pdsch-HARQ-ACK-Codebook-r16* for unicast HARQ-ACK information and *pdsch-HARQ-ACK-Codebook* = *semi-static* for multicast HARQ-ACK information, + - or *pdsch-HARQ-ACK-Codebook* = *semi-static* or *pdsch-HARQ-ACK-Codebook-r16* for unicast HARQ-ACK information and *pdsch-HARQ-ACK-Codebook* = *dynamic* for multicast HARQ-ACK information, and +- would multiplex the unicast and multicast HARQ-ACK information in a same PUCCH or PUSCH + +the UE + +- appends the HARQ-ACK codebooks for the multicast HARQ-ACK information to the HARQ-ACK codebooks for the unicast HARQ-ACK information + +- if , the UE determines for obtaining a power of a PUCCH transmission with the HARQ-ACK information, as described in clause 7.2.1, as a sum of the value from clause 9.1.3.1 or clause 9.1.3.3 and the value from clause 9.1.2.1 or as a sum of the value from clause 9.1.2.1 or clause 9.1.3.3 and the value from clause 9.1.3.1. + +A UE determines a PUCCH resource for a PUCCH transmission with HARQ-ACK information as described in clauses 9.2 and 9.2.1 through 9.2.5. + +If a UE multiplexes in a PUCCH HARQ-ACK information of same priority associated with unicast DCI formats and with multicast DCI formats in a same PUCCH, the last DCI format that the UE uses to determine the PUCCH resource from *pucch-Config/pucch-ConfigurationList*, as described in clause 9.2.3, is a last unicast DCI format. + +If the UE multiplexes in a PUCCH only multicast HARQ-ACK information of same priority that is according to both the first and second HARQ-ACK reporting modes, the last DCI format that the UE uses to determine the PUCCH resource from *pucch-ConfigMulticast1/pucch-ConfigurationListMulticast1*, if provided; otherwise, from *pucch-Config/pucch-ConfigurationList*, as described in clause 9.2.3, is a last DCI format associated with multicast HARQ-ACK information that is according to the first HARQ-ACK reporting mode. + +If a UE multiplexes in a PUCCH only first HARQ-ACK information associated with multicast SPS PDSCH receptions and second HARQ-ACK information associated with multicast DCI formats and having same priority value as the first HARQ-ACK information, and both the first and second HARQ-ACK information are according to the first HARQ-ACK reporting mode, the UE determines the PUCCH resource based on the last multicast DCI format from *pucch-ConfigMulticast1/pucch-ConfigurationListMulticast1*, if provided; otherwise, from *pucch-Config/pucch-ConfigurationList*, as described in clause 9.2.3. + +If a UE multiplexes in a PUCCH only first HARQ-ACK information associated with multicast SPS PDSCH receptions and second HARQ-ACK information associated with multicast DCI formats and having same priority value as the first HARQ-ACK information, and the first and second HARQ-ACK information are indicated by *harq-FeedbackOptionMulticast* different HARQ-ACK reporting modes, the UE determines the PUCCH resource based on: + +- *sps-PUCCH-AN-ListMulticast*, or *sps-PUCCH-AN-List* if *sps-PUCCH-AN-ListMulticast* is not provided, if the first HARQ-ACK information is according to the first HARQ-ACK reporting mode or +- the last multicast DCI format, as described in clause 9.2.3, if the second HARQ-ACK information is according to the first HARQ-ACK reporting mode. + +If a UE multiplexes in a PUCCH first HARQ-ACK information associated with unicast SPS PDSCH receptions and second HARQ-ACK information associated with multicast DCI formats and having same priority value as the first HARQ-ACK information in a same PUCCH, the UE determines the PUCCH resource from + +- if provided, *SPS-PUCCH-AN-List* for unicast SPS PDSCH receptions as described in clause 9.2.1; +- else, if provided, *PUCCH-Config/PUCCH-ConfigurationList* for multicast PDSCH receptions; +- else, *PUCCH-Config/PUCCH-ConfigurationList* for unicast PDSCH receptions. + +If a UE multiplexes in a PUCCH first HARQ-ACK information associated with unicast SPS PDSCH receptions and second HARQ-ACK information associated with multicast SPS PDSCH receptions and having same priority value as the first HARQ-ACK information in a same PUCCH, the UE determines the PUCCH resource from *SPS-PUCCH-AN-List* for unicast SPS PDSCH receptions as described in clause 9.2.1. + +If a UE multiplexes in a PUCCH only HARQ-ACK information associated with multicast SPS PDSCHs receptions of same priority that is according to the first HARQ-ACK reporting mode and is not provided *sps-PUCCH-AN-ListMulticast*, the UE determines the PUCCH resource from the *sps-PUCCH-AN-List* provided for unicast SPS PDSCH reception as described in clause 9.2.1. + +If a UE multiplexes in a PUCCH multicast HARQ-ACK information only according to second HARQ-ACK reporting modes and CSI reports and, if any, SR, the UE determines a PUCCH resource as described in clause 9.2.5.2 for multiplexing CSI reports with HARQ-ACK information that is in response to PDSCH receptions without corresponding PDCCHs. + +A UE is not required to multiplex in a PUCCH multicast HARQ-ACK information of a priority and unicast UCI of the priority if the UE is provided *subslotLengthForPUCCH* for PUCCH transmissions with unicast UCI of the priority. + +# 19 PUSCH transmission in RRC\_INACTIVE state + +## 19.1 Configured-grant based PUSCH transmission + +A UE indicated to release a dedicated RRC connection can be provided one or more configurations by respective one or more *ConfiguredGrantConfig*, for configured grant Type 1 PUSCH transmissions on the initial UL BWP [12, TS 38.331]. For the remaining of this clause, PUSCH transmissions refer to configured grant Type-1 PUSCH transmissions for a configuration provided by *ConfiguredGrantConfig*. + +A UE can be provided by *sdt-SSB-Subset* a number of SS/PBCH block indexes to map to a number of valid PUSCH occasions for PUSCH transmissions over an association period. If the UE is not provided *sdt-SSB-Subset*, the UE determines from the value of *ssb-PositionsInBurst* in *SIB1*. A PUSCH occasion for a PUSCH transmission is defined by a time resource and a frequency resource and is associated with a DM-RS provided by *cg-DMRS-Configuration* for the configuration of PUSCH transmissions. A UE can be provided a number of repetitions for a PUSCH transmission by *repK* or *numberOfRepetitions*. If the number of repetitions is provided and larger than 1, all the PUSCH occasions of the repetitions for the PUSCH transmission are mapped to the same SS/PBCH block index(es). All the PUSCH occasions of the repetitions are not valid if any PUSCH occasion of the repetitions is not valid. + +An association period, starting from frame with SFN 0 and hyper frame with hyper SFN 0, for mapping SS/PBCH block indexes, from the number of SS/PBCH block indexes, to valid PUSCH occasions and associated DM-RS resources is the smallest value in the set determined by the PUSCH configuration period provided by *periodicity* in *ConfiguredGrantConfig* according to Table 19.1-1 such that SS/PBCH block indexes are mapped at least once to valid PUSCH occasions and associated DM-RS resources within the association period. A UE is provided a number of SS/PBCH block indexes associated with a PUSCH occasion and a DM-RS resource by *sdt-SSB-PerCG-PUSCH*. If after an integer number of SS/PBCH block indexes to PUSCH occasions and associated DMRS resources mapping cycles within the association period there is a set of PUSCH occasions and associated DMRS resources that are not mapped to SS/PBCH block indexes, no SS/PBCH block indexes are mapped to the set of PUSCH occasions and associated DMRS resources. An association pattern period, when PUSCH configuration period is no longer than 640 msec, includes one or more association periods and is determined so that a pattern between PUSCH occasions with associated DMRS resources and SS/PBCH block indexes repeats at most every 640 msec. PUSCH occasions and associated DMRS resources not associated with SS/PBCH block indexes after an integer number of association periods, if any, are not used for PUSCH transmissions. + +**Table 19.1-1: Mapping between PUSCH configuration period and SS/PBCH block to configured PUSCH resource association period** + +| PUSCH configuration period (msec) | Association period (number of PUSCH configuration periods) | +|-----------------------------------|------------------------------------------------------------| +| 5 | {1, 2, 4, 8, 16, 32, 64, 128} | +| 8 | {1, 2, 4, 5, 8, 10, 16, 20, 40, 80} | +| 10 | {1, 2, 4, 8, 16, 32, 64} | +| 16 | {1, 2, 4, 5, 8, 10, 20, 40} | +| 20 | {1, 2, 4, 8, 16, 32} | +| 32 | {1, 2, 4, 5, 10, 20} | +| 40 | {1, 2, 4, 8, 16} | +| 64 | {1, 2, 5, 10} | +| 80 | {1, 2, 4, 8} | +| 128 | {1, 5} | +| 160 | {1, 2, 4} | +| 320 | {1, 2} | +| 640 | {1} | +| 1280 | {1} | +| 2560 | {1} | +| 5120 | {1} | +| 10240 | {1} | +| 61440 | {1} | +| 122880 | {1} | +| 307200 | {1} | +| 604160 | {1} | +| 1208320 | {1} | +| 1802240 | {1} | +| 3604480 | {1} | + +SS/PBCH block indexes are mapped to valid PUSCH occasions and associated DMRS resources in the following order + +- first, in increasing order of DMRS resource indexes within a PUSCH occasion, where a DMRS resource index is determined first in an ascending order of a DMRS port index and second in an ascending order of a DMRS sequence index [4, TS 38.211] +- second, in increasing order of PUSCH configuration period indexes + +A PUSCH occasion is valid if it does not overlap with a valid PRACH occasion as described in clause 8.1. + +For unpaired spectrum and for SS/PBCH blocks with indexes provided by *ssb-PositionsInBurst* in *SIB1* + +- if a UE is not provided *tdd-UL-DL-ConfigurationCommon*, a PUSCH occasion is valid if the PUSCH occasion + - does not precede a SS/PBCH block in the PUSCH slot, and + - starts at least $\Delta$ symbols after a last SS/PBCH block symbol, where $\Delta$ is provided in Table 8.1-2 +- if a UE is provided *tdd-UL-DL-ConfigurationCommon*, a PUSCH occasion is valid if the PUSCH occasion + - is within UL symbols + - starts at least $\Delta$ symbols after a last downlink symbol, and at least $\Delta$ symbols after a last SS/PBCH block symbol, where $\Delta$ is provided in Table 8.1-2 + +A UE determines a power of a PUSCH transmission as described in clause 7.1.1, where the UE obtains $\Delta$ using a RS resource from an SS/PBCH block with index associated with the PUSCH transmission. + +A UE can be provided a USS set by *SearchSpace*, or a CSS set by *sdt-SearchSpace*, to monitor PDCCH for detection of DCI format 0\_0 with CRC scrambled by C-RNTI or CS-RNTI for scheduling PUSCH transmission or of DCI format 1\_0 with CRC scrambled by C-RNTI for scheduling PDSCH receptions [12, TS 38.331]. The UE may assume that the DM-RS antenna port associated with the PDCCH receptions, the DM-RS antenna port associated with the PDSCH receptions, and the SS/PBCH block associated with the PUSCH transmission are quasi co-located with respect to + +average gain and quasi co-location 'typeA' or 'typeD' properties. The UE transmits a PUCCH with HARQ-ACK information associated with the PDSCH receptions as described in clause 9.2.1 using a same spatial domain transmission filter as for the last PUSCH transmission. + +For initial transmission or autonomous retransmission of an initial transport block provided for the PUSCH transmission as described in clause 18.0 in [19, TS 38.300], the UE encodes the transport block using redundancy version number 0 if the UE is not provided *repK-RV*. + +## 19.2 Random-access based PUSCH transmission + +A UE indicated to release a dedicated RRC connection can be provided a configuration for a Type-1 and/or a Type-2 random access procedure on the initial UL BWP [12, TS 38.331]. PRACH occasions can have either a common configuration as, or a separate configuration from, PRACH occasions for Type-1 or Type-2 random access procedure as described in clause 8.1. The UE procedure is as described in clause 8, including clauses 8.1 through 8.4. The UE transmits a PRACH preamble with a power determined as described in clause 7.4. + +For a common configuration of PRACH occasions and a Type-1 or a Type-2 random access procedure, a UE can be provided a number of contention based preambles per SS/PBCH block index per valid PRACH occasion by *startPreambleForThisPartition* and *numberOfPreamblesPerSSB-ForThisPartition* when *smallData* is present in corresponding *FeatureCombination*. A PRACH transmission can be on a subset of PRACH occasions associated with a same SS/PBCH block index within an SSB-RO mapping cycle as determined by a PRACH mask index provided by *ssb-SharedRO-MaskIndex* according to [11, TS 38.321]. + +A UE can be provided by *sdt-SearchSpace* a CSS set to monitor, after contention resolution as described in clause 8.4, PDCCH for detection of a DCI format 0\_0 or DCI format 1\_0 with CRC scrambled by C-RNTI for scheduling respective PUSCH transmissions or PDSCH receptions; otherwise, if the UE is not provided *sdt-SearchSpace*, the UE monitors PDCCH according to a Type1-PDCCH CSS set as described in clause 10.1. The UE may assume that the DM-RS antenna port associated with the PDCCH receptions, the DM-RS antenna port associated with the PDSCH receptions, and the SS/PBCH block associated with the PRACH transmission are quasi co-located with respect to average gain and quasi co-location 'typeA' or 'typeD' properties. + +# --- 20 Network controlled repeater + +An NCR includes an NCR-MT entity and an NCR-Fwd entity [19, TS 38.300]. + +Throughout this specification, unless otherwise noted, statements using the term "UE" in Clauses 4 through 13 are equally applicable to the NCR-MT. + +A procedure for the NCR-MT to perform cell search, system information acquisition, random access procedure, UCI reporting, or PDCCH monitoring is same as a corresponding one for a UE. A procedure for the NCR-MT to perform PDSCH reception, CSI-RS measurements and CSI determination, PUSCH transmission, or SRS transmission is same as a corresponding one for a UE as described in [6, TS 38.214]. + +The NCR-Fwd transmits or receives only after the NCR-MT receives on the control link an indication for one or more beams [20, TS 38.106] for the NCR-Fwd to use for transmissions or receptions over corresponding one or more time resources on the access link. + +The timing for transmission and reception by the NCR-Fwd on the backhaul link follows the frame timing for transmission and reception, respectively, by the NCR-MT. + +When the NCR-MT performs a link recovery procedure as described in Clause 6, the NCR-Fwd does not transmit or receive until the link recovery procedure is complete [11, TS 38.321]. + +The NCR can be provided, through the NCR-MT, *tdd-UL-DL-ConfigurationCommon* and can be additionally provided *tdd-UL-DL-ConfigurationDedicated*. The NCR-Fwd receives on the backhaul link or transmits on the access link only in symbols indicated as downlink by *tdd-UL-DL-ConfigurationCommon* and, if provided, *tdd-UL-DL-ConfigurationDedicated*. The NCR-Fwd receives on the access link or transmits on the backhaul link only in symbols indicated as uplink by *tdd-UL-DL-ConfigurationCommon* and, if provided, *tdd-UL-DL-ConfigurationDedicated*. + +If the NCR does not support simultaneous transmissions on control link and the backhaul link, the NCR-Fwd does not transmit over a time resource if the NCR-MT transmits over the time resource. + +When the NCR simultaneously receives via both the control link and the backhaul link in a set of symbols, a TCI state for receptions on the backhaul link is same as a TCI state for receptions on the control link in the set of symbols. When the NCR simultaneously transmits via both the control link and the backhaul link in a set of symbols, a spatial filter for transmissions on the backhaul link is same as a spatial filter for transmissions on the control link in the set of symbols. + +When the NCR does not simultaneously receive on the control link and the backhaul link + +- if the NCR does not support determination of a TCI state for receptions on the backhaul link based on an indication of a TCI state by the serving cell, or if the NCR does not receive an indication of a TCI state, for receptions on the backhaul link [11, TS 38.321] +- if the NCR does not receive an indication of a unified TCI state for receptions by the NCR-MT, receptions on the backhaul link use same QCL parameters as the ones for PDCCH receptions in a CORESET with the lowest *controlResourceSetId* in the active DL BWP +- else, receptions on the backhaul link use the QCL parameters provided by an indicated unified TCI state for receptions by the NCR-MT +- else receptions on the backhaul link use QCL parameters provided by a TCI state in NCR Downlink Backhaul Link Beam Indication MAC CE [11, TS 38.321]. + +When the NCR does not simultaneously transmit on the control link and the backhaul link + +- if the NCR does not support determination of a spatial filter for transmissions on the backhaul link based on an indication of a unified TCI state or of an SRI by the serving cell, or if the NCR-MT does not receive an indication of a unified TCI state or of an SRI for determining a spatial filter, for transmissions on the backhaul link +- if the NCR does not receive an indication of a unified TCI state for transmissions by the NCR-MT, transmissions on the backhaul link use a same spatial filter as the one associated with the PUCCH resource with the smallest *pucch-ResourceId* in *PUCCH-ResourceSet* in the active UL BWP +- else, transmissions on the backhaul link use a spatial filter corresponding to the indicated unified TCI state for transmissions by the NCR-MT. +- else transmissions on the backhaul link use a spatial filter corresponding to a unified TCI state or an SRI provided in NCR Uplink Backhaul Link Beam Indication MAC CE [11, TS 38.321]. + +If the NCR receives an indication of a TCI state for receptions on the backhaul link in a MAC CE command, or an indication of a unified TCI state or of an SRI for determining a spatial filter for transmissions on the backhaul link in a MAC CE command, the NCR applies the MAC CE command from the first slot that is after slot $\lfloor \frac{n_{\text{slot}}}{K} \rfloor$ where $n_{\text{slot}}$ is the slot where the NCR-MT would transmit a PUCCH with HARQ-ACK information associated with the PDSCH providing the MAC CE command, $K$ is a number of slots per subframe for the SCS configuration of the PUCCH transmission. + +The NCR-Fwd uses a same beam for transmissions and receptions on the access link during respective time resources associated with a same beam index. + +The NCR can be provided by *periodicFwdRsrcSetToAddModList* a list of sets of resources for transmissions or receptions on the access link. A set of resources, from the list of sets of resources, is provided by *NCR-PeriodicFwdResourceSet* and occurs with a periodicity provided by *periodicityAndOffset-r18*. A resource from the set of resources is provided by *NCR-PeriodicFwdResource* and includes a pair of a time resource provided by *periodicTimeRsrc* and a beam [20, TS 38.106] with an index provided by *beamIndex*. The time resource starts at a slot that is offset by a number of slots provided by *periodicityAndOffset-r18* from the start of the period for the set of resources and at a symbol that is offset by *symbolOffset* from the start of the slot, and has a duration provided by *durationInSymbols* for a SCS provided by *referenceSCS* and the *cyclicPrefix* of the active DL BWP. + +The NCR can be provided by *semiPersistentFwdRsrcSetToAddModList* a list of sets of resources for transmissions or receptions on the access link and the NCR Access Link Beam Indication MAC CE command can indicate a set of resources for the NCR to use or to stop using based on a corresponding identity provided by *semiPersistentFwdRsrcSetId* [11, TS 38.321]. The NCR uses or stops using the set of resources starting from the first slot that is after slot $\lfloor \frac{n_{\text{slot}}}{K} \rfloor$ where $n_{\text{slot}}$ is the slot where the NCR-MT would transmit a PUCCH with HARQ-ACK information associated with the PDSCH providing the MAC CE command and $K$ is the SCS configuration for the PUCCH transmission. The set of resources is provided by *NCR-SemiPersistentFwdResourceSet* and occurs with a periodicity provided by *periodicityAndOffset-r18*. A resource from the set of resources is provided by *NCR-* + +*SemiPersistentFwdResource* and includes a pair of a time resource provided by *semiPersistentTimeRsrc* and a beam with an index provided by *beamIndex*, where *beamIndex* can be updated by the NCR Access Link Beam Indication MAC CE command. The time resource starts at a slot that is offset by a number of slots provided by *periodicityAndOffset-r18* from the start of the period for the set of resources and at a symbol that is offset by *symbolOffset* from the start of the slot, and has a duration provided by *durationInSymbols* for a SCS provided by *referenceSCS* and the *cyclicPrefix* of the active DL BWP. + +The NCR-MT can be configured to monitor PDCCH according to USS sets for detection of a DCI format 2\_8 with CRC scrambled by an NCR-RNTI. A time resource and a corresponding beam index for transmissions or receptions on the access link are indicated by corresponding fields in DCI format 2\_8 [4, TS 38.212]. When the NCR detects more than one DCI formats 2\_8 that indicate beam indexes for time resources overlapping in a set of symbols, the NCR uses for the set of symbols a beam index that is indicated by a DCI format 2\_8 that the NCR-MT detects in a most recent PDCCH monitoring occasion. The time resource starts at a slot that is offset by *slotOffsetAperiodic* slots from a reference slot and at a symbol that is offset by *symbolOffset* from the start of the slot, and has a duration provided by *durationInSymbols* for a SCS provided by *referenceSCS* and the *cyclicPrefix* of the active DL BWP. The reference slot is the first slot with the SCS provided by *referenceSCS* that starts no earlier than the start of a slot that is after a slot of a PDCCH reception that provides the DCI format 2\_8 by a number of slots indicated by *AperiodicBeamIndicationForAccessLink* [18, TS 38.306] with the SCS of PDCCH reception. + +If + +- a first time resource provided by *NCR-SemiPersistentFwdResourceSet* is indicated by the NCR Access Link Beam Indication MAC CE command and is associated with a first beam index, and +- a second time resource is provided by *NCR-PeriodicFwdResourceSet* and is associated with a second beam index, and +- the first time resource overlaps with the second time resource in a set of symbols, + +the NCR applies, for transmissions or receptions on the access link in the set of symbols, the second beam index if only *NCR-PeriodicFwdResourceSet* includes *priorityFlag*, and the first beam index otherwise. + +If + +- a first time resource is provided by *NCR-PeriodicFwdResourceSet*, or provided by *NCR-SemiPersistentFwdResourceSet* and indicated by the NCR Access Link Beam Indication MAC CE command, and is associated with a first beam index, and +- a second time resource is indicated by DCI format 2\_8 and is associated with a second beam index provided by the DCI format 2\_8, and +- the first time resource overlaps with the second time resource in a set of symbols, + +the NCR applies, for transmissions or receptions on the access link in the set of symbols, + +- the first beam index if *NCR-PeriodicFwdResourceSet* or *NCR-SemiPersistentFwdResourceSet* includes *priorityFlag*, and +- the second beam index if *NCR-PeriodicFwdResourceSet* or *NCR-SemiPersistentFwdResourceSet* does not include *priorityFlag*. + +The NCR does not expect overlapping time resources provided by either *NCR-PeriodicFwdResourceSet* or *NCR-SemiPersistentFwdResourceSet* to be associated with different beam indexes. + +# 21 L1/L2-triggered mobility procedures + +A UE can be indicated, by *LTM-Config*, candidate cells and SS/PBCH blocks per candidate cell for the UE to obtain synchronization and measure corresponding L1-RSRPs [10, TS 38.133]. A MAC CE command can activate TCI states, provided by *LTM-Candidate-TCI-State-r18* or/and *LTM-Candidate-TCI-UL-State-r18*, associated with SS/PBCH blocks or TRS of corresponding candidate cells. The UE is provided configurations by *LTM-CSI-ReportConfigToAddModList* for reporting L1-RSRP measurements [6, TS 38.214] that include a number of candidate cells and a number of SS/PBCH blocks per candidate cell from the number of candidate cells. + +If *Itm-UE-MeasuredTA-ID* of a candidate cell and *Itm-UE-MeasuredTA-ID* of the serving cell are provided to a UE and have same value, the UE estimates based on the UE implementation a timing advance to apply from a first transmission on the candidate cell that is after the reception of a cell switch command for the candidate cell [11, TS 38.321]. + +A UE can be provided configurations, by *EarlyUlSyncConfig*, for PRACH transmission parameters for each of the candidate cells. The UE can be triggered a PRACH transmission on a candidate cell by a PDCCH order that the UE receives on a serving cell and includes an indication of the candidate cell for the PRACH transmission [4, TS 38.212]. If the serving cell and the candidate cell operate in a same frequency range and the UE would have transmissions that overlap in time, or when a gap between a first or last symbol of a PRACH transmission to the candidate cell is less than *N* symbols from a last or first symbol, respectively, of an UL transmission to the serving cell, where *N* is defined in Clause 8.1, the UE + +- drops the transmissions on the serving cell when the UE does not support transmissions that overlap in time or are separated by less than the gap on the serving cell and the candidate cell +- prioritizes power allocation to the PRACH transmission on the candidate cell in clause 7.5 when the UE supports transmissions that overlap in time or are separated by less than the gap, and a total UE transmit power in the frequency range would exceed + +The UE transmits the PRACH on the candidate cell as described in Clause 8.1 with a power determined as described in Clause 7.4. + +A UE can be provided by a MAC CE in a PDSCH reception on the serving cell [11, TS 38.321] a *TCI-State* and/or *TCI-UL-State* in *LTM-dl-OrJointTCI-StateToAddModList* and/or *LTM-ul-TCI-ToAddModList* indicating a unified TCI state [6, TS 38.214] for applicable receptions or transmissions on a candidate cell from the number of candidate cells. The UE applies the *TCI-State* and/or *TCI-UL-State*, if indicated by the MAC CE, from a first slot that is after the last symbol of a PUCCH or PUSCH with HARQ-ACK information for the PDSCH providing the MAC CE, and is the SCS configuration for the TBD. If the MAC CE triggers a PRACH transmission [11, TS 38.321], the UE applies the *TCI-State* for receptions on the candidate cell, and applies a spatial domain filter corresponding to the *TCI-State* or the *TCI-UL-State* for transmissions on the candidate cell, that are after the completion of the random access procedure associated with the PRACH transmission on the candidate cell and before a new TCI state is indicated for the candidate cell. + +# Annex A: Change history + +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +|---------|------------|------------|------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------|-------------| +| 2017-04 | RAN1#89 | R1-1707925 | | | | Draft skeleton | 0.0.0 | +| 2017-07 | AH_NR2 | R1-1712015 | | | | Inclusion of agreements until RAN1-adhoc#2 | 0.0.1 | +| 2017-08 | RAN1#90 | R1-1714553 | | | | Inclusion of agreements on CA and first revisions | 0.0.2 | +| 2017-08 | RAN1#90 | R1-1714565 | | | | Second revisions | 0.0.3 | +| 2017-08 | RAN1#90 | R1-1714658 | | | | Endorsed by RAN1#90 | 0.1.0 | +| 2017-08 | RAN1#90 | R1-1715323 | | | | Inclusion of agreements from RAN1#90 | 0.1.1 | +| 2017-08 | RAN1#90 | R1-1715330 | | | | Updated editor's version | 0.1.2 | +| 2017-09 | RAN#77 | RP-171995 | | | | For information to plenary | 1.0.0 | +| 2017-09 | RAN1#90bis | R1-1716929 | | | | Inclusion of agreements until RAN1-adhoc#3 | 1.0.1 | +| 2017-10 | RAN1#90bis | R1-1719107 | | | | Endorsed by RAN1#90bis | 1.1.0 | +| 2017-11 | RAN1#90bis | R1-1719226 | | | | Inclusion of agreements from RAN1#90bis | 1.1.1 | +| 2017-11 | RAN1#90bis | R1-1719243 | | | | Updated editor's version | 1.1.2 | +| 2017-11 | RAN1#90bis | R1-1721050 | | | | Endorsed by RAN1#90bis | 1.2.0 | +| 2017-12 | RAN1#91 | R1-1721343 | | | | Inclusion of agreements from RAN1#91 | 1.3.0 | +| 2017-12 | RAN#78 | RP-172703 | | | | Endorsed version for approval by plenary | 2.0.0 | +| 2017-12 | RAN#78 | | | | | Approved by plenary – Rel-15 spec under change control | 15.0.0 | +| 2018-03 | RAN#79 | RP-180200 | 0001 | - | F | CR capturing the NR ad-hoc 1801 and RAN1#92 meeting agreements | 15.1.0 | +| 2018-06 | RAN#80 | RP-181172 | 0002 | 1 | F | CR to TS 38.213 capturing the RAN1#92bis and RAN1#93 meeting agreements and aligning higher layer parameters with TS 38.331 | 15.2.0 | +| 2018-09 | RAN#81 | RP-181789 | 0005 | - | F | CR to 38.213 capturing the RAN1#94 meeting agreements | 15.3.0 | +| 2018-09 | RAN#81 | RP-182071 | 0006 | - | C | Support maximum 8 SS/PBCH blocks for unpaired spectrum beyond 2.4GHz | 15.3.0 | +| 2018-12 | RAN#82 | RP-182523 | 0007 | 2 | F | Combined CR of all essential corrections to 38.213 from RAN1#94bis and RAN1#95. | 15.4.0 | +| 2019-03 | RAN#83 | RP-190449 | 0009 | - | F | Correction on search space sharing | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0010 | - | F | CR on timing adjustment indicator | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0011 | - | F | CR on SSB-RO association | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0012 | - | F | Removal of CSI request in RAR grant | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0014 | - | F | Correction to dynamic HARQ codebook in NR | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0015 | 1 | F | Corrections to TS 38.213 | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0016 | - | F | CR on simultaneous active BWP switching across carriers | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0017 | - | F | CR on using CORESET#0 in dedicated DL BWP | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0018 | - | F | PDCCH monitoring for overlapped CORESETs | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0019 | - | F | Correction to last PUCCH resource set configuration | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0020 | - | F | Correction on physical downlink control channel | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0021 | - | F | Correction to align RAN1 and RAN4 specifications for EN-DC power control | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0022 | - | F | (Late Drop) CR on PRACH Power Ramping Counter Suspension | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0023 | - | F | QCL properties of Msg4 in CONNECTED Mode | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0024 | - | F | CR on latency after gNB response for recovery | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0025 | - | F | Clarifying DL reception and UL transmission related restrictions | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0026 | - | F | CR on QCL assumption for receiving PDCCH for RAR | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0027 | - | F | CR on identifying transmission occasion after resetting a PC closed loop | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0028 | - | F | CR on overlapping of CSI and PUSCH with slot aggregation | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0029 | - | F | Correction on PHR timing for configured grant | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0030 | - | F | CR on QCL assumption for a CORESET other than 0 | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0031 | - | F | Correction on DCI format 2_3 for SUL cell in TS 38.213 | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0032 | - | F | Correction to support FR1 extension to 7.125 GHz | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0033 | - | F | CR on UE procedure for reporting multiple UCI types | 15.5.0 | +| 2019-03 | RAN#83 | RP-190449 | 0034 | - | F | Correction to transmission timing adjustments in TS 38.213 | 15.5.0 | +| 2019-06 | RAN#84 | RP-191283 | 0035 | - | F | CR on missing case for DCI format 1_1 with CS-RNTI | 15.6.0 | +| 2019-06 | RAN#84 | RP-191283 | 0036 | 1 | F | CR on the determination of the minimum number of PRBs for PUCCH transmission | 15.6.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------|--------| +| 2019-06 | RAN#84 | RP-191283 | 0037 | - | F | CR on PHR determination and transmission | 15.6.0 | +| 2019-06 | RAN#84 | RP-191283 | 0038 | 4 | F | Corrections to 38.213 including alignment of terminology across specifications | 15.6.0 | +| 2019-06 | RAN#84 | RP-191283 | 0039 | 1 | F | Correction on PUSCH power scaling | 15.6.0 | +| 2019-06 | RAN#84 | RP-191283 | 0040 | - | F | Correction on PDCCH monitoring | 15.6.0 | +| 2019-06 | RAN#84 | RP-191283 | 0041 | - | F | Correction on CRC assumption for multi-CSI resource selection and CSI report(s) selection | 15.6.0 | +| 2019-06 | RAN#84 | RP-191283 | 0042 | - | F | Clarification of reference to PDSCH processing capability 1 in TS 38.213 | 15.6.0 | +| 2019-06 | RAN#84 | RP-191283 | 0043 | - | F | Correction on the timeline condition of multiplexing two HARQ-ACK information in one slot | 15.6.0 | +| 2019-06 | RAN#84 | RP-191283 | 0044 | - | F | CR on Type-1 HARQ-ACK codebook determination | 15.6.0 | +| 2019-06 | RAN#84 | RP-191283 | 0045 | - | F | Correction on PHR in EN-DC | 15.6.0 | +| 2019-06 | RAN#84 | RP-191283 | 0046 | - | F | CR to 38.213 on deactivation timing for ScellDeactivationTimer | 15.6.0 | +| 2019-06 | RAN#84 | RP-191283 | 0047 | - | F | CR on single transmission timing for synchronous intra-band EN-DC | 15.6.0 | +| 2019-06 | RAN#84 | RP-191283 | 0048 | - | F | CR on PDCCH Monitoring for NR-DC | 15.6.0 | +| 2019-06 | RAN#84 | RP-191283 | 0049 | - | F | CR on Timing for MAC CE Applicability | 15.6.0 | +| 2019-09 | RAN#85 | RP-191942 | 0051 | - | F | Correction on RA procedure triggered by higher layers | 15.7.0 | +| 2019-09 | RAN#85 | RP-191942 | 0052 | 1 | F | CR on UE procedure for reporting multiple UCI types | 15.7.0 | +| 2019-09 | RAN#85 | RP-191942 | 0053 | - | F | CR to 38.213 fix to HARQ-ACK Type-1 codebook pseudo-code | 15.7.0 | +| 2019-09 | RAN#85 | RP-191942 | 0054 | - | F | CR to 38.213 on clarification of the RNTI used for scrambling a PUSCH transmission scheduled by RAR UL grant | 15.7.0 | +| 2019-09 | RAN#85 | RP-191942 | 0055 | 2 | F | Corrections to 38.213 including alignment of terminology across specifications in RAN1#98 | 15.7.0 | +| 2019-09 | RAN#85 | RP-191942 | 0056 | - | F | Correction on intra-band EN-DC with single TAG | 15.7.0 | +| 2019-09 | RAN#85 | RP-191942 | 0057 | - | F | Correction on PHR in EN-DC/NE-DC/NR-CA | 15.7.0 | +| 2019-09 | RAN#85 | RP-191942 | 0058 | - | F | Correction on the time gap definition | 15.7.0 | +| 2019-09 | RAN#85 | RP-191942 | 0059 | - | F | Correction on slot configuration | 15.7.0 | +| 2019-09 | RAN#85 | RP-191942 | 0060 | - | F | CR to 38.213 on PUCCH configuration for NR-DC | 15.7.0 | +| 2019-09 | RAN#85 | RP-191942 | 0061 | - | F | Correction on PUCCH power control | 15.7.0 | +| 2019-12 | RAN#86 | RP-192626 | 0062 | 1 | F | CR on beta_offset values for UCI reporting in PUSCH | 15.8.0 | +| 2019-12 | RAN#86 | RP-192626 | 0063 | - | F | Correction on RACH occasion | 15.8.0 | +| 2019-12 | RAN#86 | RP-192626 | 0064 | - | F | Correction on HARQ-ACK transmission with BWP change | 15.8.0 | +| 2019-12 | RAN#86 | RP-192626 | 0065 | - | F | CR on slot configuration regarding PUSCH scheduled by RAR | 15.8.0 | +| 2019-12 | RAN#86 | RP-192626 | 0066 | - | F | Correction on power control for NE-DC | 15.8.0 | +| 2019-12 | RAN#86 | RP-192626 | 0067 | - | F | Correction on time gap definition for HARQ-ACK transmission | 15.8.0 | +| 2019-12 | RAN#86 | RP-192626 | 0068 | - | F | Correction on time gap definition for random access procedure | 15.8.0 | +| 2019-12 | RAN#86 | RP-192626 | 0069 | 3 | F | Corrections to 38.213 including alignment of terminology across specifications in RAN1#98bis and RAN1#99 | 15.8.0 | +| 2019-12 | RAN#86 | RP-193121 | 0070 | 1 | B | Introduction of two-step RACH in NR | 16.0.0 | +| 2019-12 | RAN#86 | RP-193221 | 0071 | 2 | B | Introduction of shared spectrum channel access | 16.0.0 | +| 2019-12 | RAN#86 | RP-193123 | 0072 | 1 | B | Introduction of integrated access and backhaul in NR | 16.0.0 | +| 2019-12 | RAN#86 | RP-193222 | 0073 | 2 | B | Introduction of Industrial IoT | 16.0.0 | +| 2019-12 | RAN#86 | RP-193125 | 0074 | 1 | B | Introduction of Ultra Reliable Low Latency Communications Enhancements | 16.0.0 | +| 2019-12 | RAN#86 | RP-193127 | 0075 | 1 | B | Introduction of MIMO enhancements in NR | 16.0.0 | +| 2019-12 | RAN#86 | RP-193128 | 0076 | 1 | B | Introduction of UE power savings | 16.0.0 | +| 2019-12 | RAN#86 | RP-193131 | 0077 | 1 | B | Introduction of NR-DC in same Frequency Range and of Cross-carrier Scheduling with Different Numerologies | 16.0.0 | +| 2019-12 | RAN#86 | RP-193132 | 0078 | 1 | B | Introduction of multiple LTE CRS rate matching patterns | 16.0.0 | +| 2019-12 | RAN#86 | RP-193124 | 0079 | 1 | B | Introduction of V2X in NR | 16.0.0 | +| 2019-12 | RAN#86 | RP-193129 | 0080 | 1 | B | Introduction of positioning support in NR | 16.0.0 | +| 2019-12 | RAN#86 | RP-193223 | 0081 | 2 | B | Introduction of mobility enhancements in NR | 16.0.0 | +| 2020-03 | RAN#87-e | RP-200184 | 0085 | - | F | Corrections on two-step RACH | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200194 | 0086 | - | F | Corrections on NR-DC and on Cross-carrier Scheduling with Different Numerologies | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200186 | 0087 | - | F | Corrections on integrated access and backhaul | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200189 | 0088 | - | F | Corrections on Industrial IoT | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200190 | 0089 | - | F | Corrections on MIMO enhancements | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200193 | 0090 | - | F | Corrections on Mobility Enhancements | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200185 | 0091 | - | F | Corrections on shared spectrum channel access | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200192 | 0092 | - | F | Corrections on Positioning | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200187 | 0093 | - | F | Corrections on Sidelink | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200191 | 0094 | - | F | Corrections on UE power savings | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200188 | 0095 | - | F | Corrections on Ultra Reliable Low Latency Communications Enhancements | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200195 | 0097 | - | F | Introduction of half-duplex operation in CA with unpaired spectrum | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200447 | 0098 | - | A | Corrections to 38.213 including alignment of terminology across specifications in RAN1#100-e | 16.1.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------------|--------| +| 2020-06 | RAN#88-e | RP-200683 | 0102 | - | A | Correction on PDCCH Blind Detection for NR-DC | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200688 | 0103 | 1 | F | Corrections on integrated access and backhaul | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200690 | 0104 | 1 | F | Corrections on Ultra Reliable Low Latency Communications Enhancements | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200693 | 0105 | 1 | F | Corrections on UE power savings | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200689 | 0106 | 1 | F | Corrections on Sidelink | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200694 | 0107 | 1 | F | Corrections on Positioning | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200687 | 0108 | 1 | F | Corrections on shared spectrum channel access | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200692 | 0109 | 1 | F | Corrections on MIMO enhancements | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200691 | 0110 | 1 | F | Corrections on Industrial IoT | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200696 | 0111 | 1 | F | Corrections on NR-DC and on Cross-carrier Scheduling with Different Numerologies | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200686 | 0112 | 1 | F | Corrections on two-step RACH | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200697 | 0113 | 1 | F | Corrections on half-duplex operation in CA with unpaired spectrum | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200705 | 0114 | - | B | Introduction of UL transmission switching | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200695 | 0115 | - | F | Corrections on Mobility Enhancements | 16.2.0 | +| 2020-06 | RAN#88-e | RP-201349 | 0117 | 1 | A | Extending 8 SSB support to the newly introduced 30 kHz Case C SSB pattern on band n40 | 16.2.0 | +| 2020-09 | RAN#89-e | RP-201803 | 0119 | - | A | Correction on the definition for timeline condition | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201803 | 0120 | - | F | Correction for PUCCH repetition transmission | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201814 | 0121 | - | F | CR on determination of the number of RS for RLM | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201803 | 0123 | - | A | CR on determining P0 for a PUSCH retransmission corresponding to a RAR UL grant in TS 38.213 | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201803 | 0125 | - | F | PRACH power ramping suspension | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201806 | 0126 | - | F | Clarify starting slot within DCI 2_5 indication | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201804 | 0127 | - | F | CR on 2-step RACH for 38.213 | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201813 | 0128 | - | F | CR on Power Control for NR-DC | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201810 | 0129 | - | F | Type-3 CSS monitoring with PS-RNTI on primary cell | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201812 | 0131 | - | F | CR on correction on uplink power sharing for DAPS HO | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201812 | 0132 | - | F | CR on correction on PDCCH monitoring for DAPS HO | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201813 | 0133 | - | F | CR to 38.213 on RRC parameter alignment for SCell dormancy | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201813 | 0134 | - | F | CR to 38.213 on BWP triggering via SCell dormancy indication | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201813 | 0135 | - | F | CR to 38.213 on HARQ-ACK processing timeline for DCI format 1_1 with SCell dormancy indication without scheduling PD SCH | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201807 | 0136 | - | F | Corrections on Sidelink | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201809 | 0137 | - | F | Corrections on MIMO enhancements | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201805 | 0138 | - | F | Corrections on shared spectrum channel access | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201808 | 0139 | - | F | Corrections on Ultra Reliable Low Latency Communications Enhancements | 16.3.0 | +| 2020-09 | RAN#89-e | RP-202015 | 0141 | 1 | A | Extending 8 SSB support to the TDD bands with newly introduced 30 kHz Case C SSB pattern | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201847 | 0142 | - | A | Correction on supplementary uplink in Rel-16 TS 38.213 | 16.3.0 | +| 2020-12 | RAN#90-e | RP-202379 | 0144 | - | A | CR on HARQ-ACK Determination for SPS Release | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202383 | 0145 | - | F | Corrections related to sidelink physical layer procedures | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202382 | 0146 | - | F | Clarify DCI Format 2_5 search space sets | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202380 | 0147 | - | F | CR on 2-step RACH for 38.213 | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202385 | 0148 | - | F | Correction on UL power control | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202388 | 0149 | 1 | F | Correction on uplink transmission cancellation for DAPS handover | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202388 | 0150 | 1 | F | Correction on PUSCH processing capability for DAPS handover | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202388 | 0151 | 1 | F | Correction on intra-frequency DAPS handover | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202383 | 0152 | - | F | Corrections on the use of TDR and FDRA fields SCI for Mode 1 | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202383 | 0153 | - | F | Corrections for the prioritization between uplink transmission and sidelink transmission/reception | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202383 | 0154 | - | F | Corrections related to the sidelink slot index | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202383 | 0155 | - | F | Correction on sidelink pathloss calculation for S-SSB power control | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202383 | 0156 | 1 | F | Correction on sidelink TDD configuration for OoC UEs | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202379 | 0158 | - | A | Correction on HARQ-ACK generation for DL transmission with single TB when multi-TB is configured | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202381 | 0159 | - | F | Miscellaneous corrections on NR unlicensed configured grant | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202383 | 0160 | - | F | Introduction of the preparation time for SL retransmissions in Mode 1 | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202395 | 0161 | - | F | Correction on uplink Tx switching | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202381 | 0163 | - | F | Correction of NRU HARQ procedure in the presence of SPS PD SCH | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202381 | 0165 | - | F | CR to 38.213 on NR-U 2-step RACH PO configuration | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202389 | 0166 | - | F | 38.213 CR for NR-DC power control | 16.4.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2020-12 | RAN#90-e | RP-202389 | 0167 | - | F | 38.213 CR Correction on HARQ-ACK codebook for secondary PUCCH group | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202384 | 0168 | - | F | Correction on Type2 HARQ-ACK codebook construction | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202384 | 0169 | - | F | Correction on UL grant Type 2 PUSCH release for search space sharing | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202384 | 0170 | - | F | Correction on PDCCH monitoring on cell(s) configured with Rel-15 PDCCH monitoring capability | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202383 | 0171 | - | F | Correction on periodicity of resource pool bitmap | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202383 | 0172 | - | F | Correction on PSFCH and PSCCH mapping | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202385 | 0173 | - | F | CR on CBRA based BFR | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202381 | 0174 | - | F | CR to 38.213 to correct references to 38.212 for RACH procedure | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202381 | 0175 | - | F | Correction on remaining channel occupancy assumption | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202398 | 0176 | - | F | Alignment CR for TS 38.213 | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202389 | 0177 | - | F | Corrections for SCell dormancy indication | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202384 | 0178 | - | F | CR on handling overlapping PUCCH/PUSCH transmissions with repetitions and with different priorities | 16.4.0 | +| 2021-03 | RAN#91-e | RP-210055 | 0180 | - | F | Type-1 HARQ-ACK for PDSCH repetition with different SCSs in DL and UL | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210047 | 0182 | - | A | Correction on the search space configuration of PUCCH-SCell | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210055 | 0183 | - | F | Correction on UCI multiplexing with PUCCH overriding | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210048 | 0184 | - | F | CR on transmission timing adjustment procedure in 38.213 | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210055 | 0186 | - | F | Correction for cancellation due to PDSCH/CSI-RS/SFI | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210049 | 0187 | - | F | Correction of Type-3 HARQ-ACK codebook generation for a PDSCH with one transport block for a configuration with a maximum number of two TBs | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210049 | 0188 | - | F | Correction of UE reception of DL control when a DCI indicates a request for a Type-3 HARQ-ACK codebook report without scheduling PDSCH | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210049 | 0189 | - | D | Correction on PUCCH power control for enhanced Type-2 HARQ-ACK codebook and for Type-3 HARQ-ACK codebook | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210052 | 0190 | - | F | CR on HARQ-ACK | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210049 | 0191 | - | F | Correction on search space set group switching without channel occupancy duration field | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210052 | 0192 | - | F | Corrections on SCell BFR in Rel-16 | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210058 | 0193 | - | F | Correction on uplink Tx switching | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210050 | 0194 | - | F | Corrections related to prioritization between uplink and sidelink | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210050 | 0195 | - | F | Determination of indexes for slots for S-SS/PSBCH block transmission(s) | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210050 | 0196 | - | F | Restrictions of the slots for S-SSB transmission/reception | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210051 | 0197 | - | F | CR on Timing for secondary cell activation / deactivation with sub-slot PUCCH | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210051 | 0198 | - | F | CR on number of PUCCHs with HARQ-ACK in a slot | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210050 | 0199 | 1 | F | Correction of SL HARQ-ACK information reporting to the gNB in Mode 1 | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210049 | 0200 | - | F | Correction on LBT Type and CP Extension Indication for Semi-Static Channel Occupancy in RAR | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210054 | 0201 | - | F | CR to 38.213 on PRACH handling for NR-DC power control | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210054 | 0202 | - | F | CR to 38.213 on HARQ-ACK priority determination for SCell dormancy indication | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210055 | 0203 | - | F | 38.213 CR on DCI ordering in a search space set | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210051 | 0204 | - | F | Correction on dci-FormatsExt in clause 10.1 in TS 38.213 | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210051 | 0205 | - | F | Resolving collision with semi-static DL and SSB symbols | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210051 | 0206 | - | F | Correction on PUCCH resource determination in clause 9.2.1 in TS 38.213 | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210059 | 0207 | - | F | Editorial corrections for 38.213 | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210126 | 0208 | - | A | Resubmission of CR179r1 on Correction on supplementary uplink in 38.213 | 16.5.0 | +| 2021-06 | RAN#92-e | RP-211234 | 0209 | - | F | Correction on multiplexing timeline definition for Type-3 HARQ-ACK codebook | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211234 | 0210 | - | F | Correction on Type-3 HARQ-ACK codebook size ambiguity | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211250 | 0211 | - | F | CR to TS 38.213 on clarifying DAPS HO impact on PUCCH repetition counting | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211235 | 0212 | - | F | Corrections for the reference signal used for sidelink power control | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211237 | 0214 | - | F | Corrections for separate HARQ-ACK feedback of multi-TRP transmission | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211240 | 0215 | - | F | Correction on half-duplex operation in CA with unpaired spectrum | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211239 | 0216 | - | F | Correction on MR-DC Uplink Power Control in 38.213 | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211234 | 0217 | - | F | Correction on MsgA PUSCH validation for semistatic channel access | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211238 | 0218 | - | F | CR on the number of pathloss estimates maintained by the UE | 16.6.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------------------|--------| +| | | | | | | for SRS for positioning. | | +| 2021-06 | RAN#92-e | RP-211249 | 0219 | - | F | Conditions for IAB-DU soft resource availability | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211235 | 0220 | - | F | Correction of search space configuration for DCI formats 3_0 and 3_1 | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211234 | 0221 | - | F | Correction on SR reporting due to consistent LBT failure recovery | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211236 | 0222 | - | F | Correction on Prioritization Timeline | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211236 | 0223 | - | F | CR on the configuration for one PUCCH-Config with subslotLengthForPUCCH-r16 | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211236 | 0224 | - | F | CR on not supporting Type 1 HARQ-ACK codebook for sub-slot HARQ-ACK in R16 | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211236 | 0225 | - | F | CR on Number of PUCCH resource sets per PUCCH-config | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211236 | 0226 | - | F | Correction on UL cancellation due to dynamic SFI | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211233 | 0228 | 1 | A | Rel-15 editorial corrections for TS 38.213 (mirrored to Rel-16) | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211243 | 0229 | 1 | F | Rel-16 editorial corrections for TS 38.213 | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211236 | 0230 | - | F | Correction on UE procedure for determining physical downlink control channel assignment for Rel-16 PDCCH monitoring capability | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211235 | 0232 | - | F | Corrections for the multiplexing SL HARQ-ACK information on a PUSCH | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211237 | 0233 | - | F | Correction on simultaneous multi-CC TCI indication for CORESET | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211234 | 0234 | - | F | Correction on HARQ-ACK codebook RRC parameter | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211234 | 0235 | - | F | Initial UL BWP size restriction for NR-U | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211235 | 0236 | - | F | Correction of SL HARQ-ACK reporting when SL feedback is not used | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211235 | 0237 | - | F | Correction of SL HARQ-ACK reporting on UL for SL CG type 2 | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211240 | 0239 | - | F | Correction on UL cancellation due to DCI format 2_0 | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211240 | 0240 | - | F | Correction on half-duplex operation in CA with unpaired spectrum | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211236 | 0241 | - | F | Handling collision between PUCCH/PUSCH and semi-static DL symbols and SSBs | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211236 | 0242 | - | F | Correction on Type-1 HARQ-ACK codebook | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211252 | 0243 | - | F | Correction on value of 1-bit counter DAI | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211236 | 0244 | - | F | CR on correction for sub-slot based PUCCH | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211236 | 0245 | - | F | CR on clarification for reference point of sub-slot based PUCCH resource | 16.6.0 | +| 2021-09 | RAN#93-e | RP-211842 | 0246 | - | F | Clarification on SL power control and SL type-1 HARQ-ACK codebook in out of coverage case | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211842 | 0247 | - | F | Parameter name correction for PSSCH power control | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211844 | 0248 | - | F | CR on number of received PDSCHs for multi-TRP transmission | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211842 | 0249 | - | F | Correction on synchronization procedure for sidelink transmission | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211846 | 0250 | 1 | F | Corrections on SCell dormancy indication | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211843 | 0251 | 1 | F | Correction on overlapping between SPS HARQ-ACK with HP and SP HARQ-ACK with LP | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211842 | 0252 | - | F | CR on Simultaneous NR SL and LTE SL Operation | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211842 | 0253 | - | F | Clarification on PUCCH Power control | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211843 | 0254 | - | F | Corrections on Sub-slot Based HARQ-ACK Feedback for MAC CE Activation/deactivation | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211842 | 0255 | - | F | Correction of SL HARQ-ACK reporting on UL for skipped DG | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211842 | 0256 | - | F | Correction on HARQ reporting for multiple pools with PSFCH | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211843 | 0257 | - | F | CR for SPS Release and SPS PDSCH Receptions with Slot Aggregation | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211850 | 0258 | - | F | Editorial corrections for TS 38.213 | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211843 | 0259 | - | F | Correction on HARQ-ACK timing | 16.7.0 | +| 2021-12 | RAN#94-e | RP-212962 | 0260 | - | F | Correction on Case 1 dormancy operation with data scheduling | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212959 | 0261 | - | F | CR on SL HARQ-ACK feedback reporting to gNB | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212959 | 0262 | - | F | Clarification on UCI and SL HARQ-ACK | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212959 | 0263 | - | F | Correction on priority order in power control for PSFCH | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212960 | 0264 | - | F | Clarification on intra-UE prioritization/multiplexing on semi-static symbols | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212961 | 0265 | - | F | Correction on frequency hopping for PUCCH | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212960 | 0266 | - | F | PUCCH multiplexing with SPS HARQ-ACK or SR within a sub-slot | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212964 | 0267 | 1 | F | Editorial corrections for TS 38.213 | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212973 | 0268 | - | B | Introduction of coverage enhancements in NR | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212980 | 0269 | - | B | Introduction of dynamic spectrum sharing enhancements in NR | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212977 | 0270 | - | B | Introduction of enhanced IAB in NR | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212967 | 0271 | - | B | Introduction for extending NR operation to 71 GHz | 17.0.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------------|--------| +| 2021-12 | RAN#94-e | RP-212968 | 0272 | - | B | Introduction of IIoT/URLLC enhancements in NR | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212979 | 0273 | - | B | Introduction of multicast-broadcast services in NR | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212969 | 0274 | - | B | Introduction of non-terrestrial network operation in NR | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212971 | 0275 | - | B | Introduction of UEs with reduced capabilities in NR | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212972 | 0276 | - | B | Introduction of UE power savings enhancements in NR | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212966 | 0277 | - | B | Introduction of further enhancements on MIMO for NR | 17.0.0 | +| 2021-12 | RAN#94-e | RP-213524 | 0278 | - | B | Introduction of small data transmission in RRC_INACTIVE state for NR | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212978 | 0279 | - | B | Introduction of sidelink enhancements in NR | 17.0.0 | +| 2022-03 | RAN#95-e | RP-220245 | 0281 | - | A | CR on UE procedure for receiving HARQ-ACK on sidelink | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220247 | 0283 | - | A | Corrections on HARQ-ACK timing parameters for Rel-17 | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220272 | 0285 | - | A | CR on properties of tdd-UL-DL-ConfigurationDedicated and tdd-UL-DL-configurationDedicated-IAB-MT | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220246 | 0287 | - | A | Clarification of the SPS PDSCH activation and HARQ-ACK transmission for the 1st SPS PDSCH | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220249 | 0289 | - | A | Rel-16 editorial corrections for TS 38.213 (mirrored to Rel-17) | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220257 | 0290 | - | F | Corrections on coverage enhancements in NR | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220251 | 0291 | - | F | Corrections on extending NR operation to 71 GHz | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220252 | 0292 | - | F | Corrections on IIoT/URLLC enhancements in NR | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220263 | 0293 | - | F | Corrections on the introduction of multicast-broadcast services in NR | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220262 | 0294 | - | F | Corrections on sidelink enhancements in NR | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220256 | 0295 | - | F | Corrections on UE power savings enhancements in NR | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220261 | 0296 | - | F | Corrections on eIAB | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220250 | 0297 | - | F | Corrections on further enhancements on MIMO for NR | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220271 | 0298 | - | C | Introduction of carrier BW smaller than 40 MHz for n79 | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220264 | 0299 | - | F | Corrections on dynamic spectrum sharing enhancements in NR | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220253 | 0300 | - | F | Corrections on non-terrestrial network operation in NR | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220254 | 0301 | - | F | Corrections on positioning enhancements in NR | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220255 | 0302 | - | F | Corrections on the introduction of UEs with reduced capabilities in NR | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220270 | 0303 | - | F | Corrections on small data transmission in RRC_INACTIVE state for NR | 17.1.0 | +| 2022-06 | RAN#96 | RP-221619 | 0305 | - | A | Correction on Rel-16 SRS power control with 2-step RACH | 17.2.0 | +| 2022-06 | RAN#96 | RP-221597 | 0307 | - | A | CR on reporting sidelink HARQ-ACK on uplink for SL CG Type 2 PSSCH transmission | 17.2.0 | +| 2022-06 | RAN#96 | RP-221598 | 0309 | - | A | Correction on PDCCH reception with last symbol aligning with the first symbol of UL CI for Rel-17 | 17.2.0 | +| 2022-06 | RAN#96 | RP-221620 | 0312 | - | A | Timeline requirement for retransmitting MSG1/MSGA | 17.2.0 | +| 2022-06 | RAN#96 | RP-221597 | 0314 | - | A | Correction on SL HARQ-ACK reporting | 17.2.0 | +| 2022-06 | RAN#96 | RP-221620 | 0317 | - | A | Correction for HARQ-ACK multiplexing on PUSCH in the absence of PUCCH | 17.2.0 | +| 2022-06 | RAN#96 | RP-221599 | 0319 | - | A | Rel-16 editorial corrections for TS 38.213 (mirrored to Rel-17) | 17.2.0 | +| 2022-06 | RAN#96 | RP-221601 | 0320 | - | F | Corrections on extending NR operation to 71 GHz | 17.2.0 | +| 2022-06 | RAN#96 | RP-221602 | 0321 | - | F | Corrections on IIoT/URLLC enhancements in NR | 17.2.0 | +| 2022-06 | RAN#96 | RP-221612 | 0322 | - | F | Corrections on the introduction of multicast-broadcast services in NR | 17.2.0 | +| 2022-06 | RAN#96 | RP-221611 | 0323 | - | F | Corrections on sidelink enhancements in NR | 17.2.0 | +| 2022-06 | RAN#96 | RP-221606 | 0324 | - | F | Corrections on UE power savings enhancements in NR | 17.2.0 | +| 2022-06 | RAN#96 | RP-221610 | 0325 | - | F | Corrections on eIAB | 17.2.0 | +| 2022-06 | RAN#96 | RP-221600 | 0326 | - | F | Corrections on further enhancements on MIMO for NR | 17.2.0 | +| 2022-06 | RAN#96 | RP-221613 | 0327 | - | F | Corrections on dynamic spectrum sharing enhancements in NR | 17.2.0 | +| 2022-06 | RAN#96 | RP-221603 | 0328 | - | F | Corrections on non-terrestrial network operation in NR | 17.2.0 | +| 2022-06 | RAN#96 | RP-221605 | 0329 | - | F | Corrections on the introduction of UEs with reduced capabilities in NR | 17.2.0 | +| 2022-06 | RAN#96 | RP-221618 | 0330 | - | F | Corrections on small data transmission in RRC_INACTIVE state for NR | 17.2.0 | +| 2022-06 | RAN#96 | RP-221614 | 0331 | - | F | Corrections on further Multi-RAT Dual-Connectivity enhancements | 17.2.0 | +| 2022-09 | RAN#97-e | RP-222400 | 0332 | - | F | CR on PDCCH repetition with SSSG switching | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222397 | 0334 | 1 | A | Correction on DCI format 3_0 reception | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222401 | 0335 | - | F | Corrections on the value of slot configuration period in TS 38.213 for the features extending NR operation to 71 GHz | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222404 | 0336 | - | F | Correction of BWP for SRS | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222401 | 0337 | - | F | Correction on the tables for determining Type0 PDCCH monitoring occasions | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222418 | 0338 | - | F | Corrections of redundancy version for SDT | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222403 | 0339 | 1 | F | CR on the clarification of PUCCH resource determination in | 17.3.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| | | | | | | 38.213 | | +| 2022-09 | RAN#97-e | RP-222403 | 0340 | 1 | F | CR on the description about HARQ-feedbackEnablingforSPSactive in 38.213 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222401 | 0342 | - | F | Correction on multi-slot PDCCH monitoring in NR-DC and CA scenarios with mixed capability types | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222400 | 0343 | 1 | F | CR on inter-cell mTRP when SSBs of additional PCI overlap with UL | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222400 | 0344 | - | F | CR on default PUSCH power control parameters for mTRP PUSCH | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222400 | 0345 | - | F | CR for power control of mTRP PUSCH repetition | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222401 | 0346 | - | F | Corrections on PDCCH monitoring enhancement for 52-71GHz spectrum | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222402 | 0347 | - | F | Correction for HARQ-ACK codebook generation for PUCCH cell switching and UL BWP switching | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222401 | 0348 | - | F | Correction on a reference SCS configuration for co-DurationList in TS 38.213 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222401 | 0349 | - | F | Correction on Type-2 HARQ CB generation when both of spatial bundling and time bundling are configured | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222401 | 0350 | - | F | Correction on Type-2 HARQ CB generation when time bundling is configured but spatial bundling is not configured | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222421 | 0352 | - | A | CR on Rel-16 Type-1 HARQ-ACK codebook in PUCCH for SCell dormancy | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222400 | 0354 | - | F | Correction of CSI assumptions over multiplexing NCJT CSI reports in PUCCH | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222402 | 0355 | - | F | CR on HP DG PUSCH and LP CG PUSCH collision resolution | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222398 | 0357 | - | A | Correction for Intra-UE multiplexing/prioritization of the same priority | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222418 | 0358 | - | F | Corrections of random-access based small data transmission | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222401 | 0359 | - | F | Correction on CD-SSB frequency indication using NCD-SSB in TS38.213 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222405 | 0360 | - | F | Corrections and clarifications of RedCap UE procedures | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222398 | 0362 | - | A | Corrections on presence of redundancy version field and HARQ process number field of DCI formats 0_2/1_2 for validation of activation and release DCI format | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222417 | 0364 | - | A | Correction on PL RS determination for PUSCH scheduled by DCI format 0_0 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222406 | 0365 | - | F | Corrections on UE Power Saving Enhancements for NR in TS 38.213 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222412 | 0366 | - | F | Corrections on the introduction of multicast-broadcast services in NR | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222422 | 0367 | - | F | Rel-17 editorial corrections for TS 38.213 | 17.3.0 | +| 2022-12 | RAN#98-e | RP-222849 | 0369 | - | A | Correction on SL BWP in TS 38.213 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222853 | 0370 | - | F | CR for ChannelAccess-CPext in RAR UL grant in FR2-2 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222853 | 0371 | - | F | CR on spatial domain filter for sensing for PUCCH transmission in FR2-2 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222853 | 0372 | - | F | Correction for multi-slot PDCCH monitoring in FR2-2 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222853 | 0373 | - | F | Correction for BD/CCE budget of scheduling cell(s) in FR2-2 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222853 | 0374 | - | F | Correction for SSSG switching with multiple cells in FR2-2 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222855 | 0375 | - | F | CR on the Type-2 HARQ-ACK codebook | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222866 | 0376 | - | F | Correction on delpreamble of feature combination | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222871 | 0378 | - | A | Correction on HARQ-ACK multiplexing on multi-PUSCHs without PUCCH for Rel-16 NR-U | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222854 | 0379 | - | F | Correction on enhanced Type 3 HARQ-ACK codebook and HARQ-ACK re-transmission triggering | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222857 | 0380 | - | F | Corrections and clarifications of RedCap UE procedures | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222854 | 0381 | - | F | CR on multiplexing for SPS HARQ-ACK | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222853 | 0382 | - | F | Correction on BD/CCE decoding with release-specific number of serving cell(s) for NR operation in FR2-2 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0383 | - | F | CR on PDCCH monitoring when overlapping with the rate matching pattern to TS 38.213 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222858 | 0384 | - | F | Corrections on UE power saving enhancements for NR in TS 38.213 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222854 | 0385 | - | F | CR on power control for PUCCH | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222870 | 0386 | - | F | Correction on parallel transmission of PRACH and SRS/PUCCH/PUSCH | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0387 | - | F | CR on multiplexing NACK-only mode1 with others | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0388 | - | F | CR on codebook type for NACK-only HARQ-ACK feedback | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0389 | - | F | CR on HARQ-ACK feedback for PDSCH scheduled by DCI format 4_1 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0390 | 2 | F | CR on DAI counting for 'dci-enabler' in DCI indicating value 0 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222852 | 0391 | - | F | CR on PHR with unified TCI in TS 38.213 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222862 | 0392 | - | F | Correction on the formula of Case-7 UL Tx timing for eIAB in TS 38.213 | 17.4.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2022-12 | RAN#98-e | RP-222862 | 0393 | - | F | CR on guard symbols MAC CEs | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222862 | 0394 | - | F | Correction on timing case indication | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222862 | 0395 | - | F | Correction on coexistence of Rel-17 and Rel-16 HSNA configuration | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222870 | 0396 | - | F | Correction on ra-SearchSpace for DCI format 0_0 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222850 | 0398 | - | A | Correction on UL prioritization cases related to SP-CSI | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0399 | - | F | CR on SS0 availability for scheduling MBS to TS 38.213 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0400 | - | F | CR on PUCCH resource determination of SPS multicast HARQ-ACK | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0401 | - | F | CR on PUCCH resource determination for multiplexing dynamic multicast HARQ-ACK and SPS unicast HARQ-ACK | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0402 | 1 | F | CR on handling SR and NACK-only collision | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222863 | 0403 | - | F | Correction on conditions for UE to be UE-B for Condition 2-A-2 of Scheme 2 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222863 | 0404 | - | F | Correction on the determination of the priority value of PSFCH transmission with conflict information due to Condition 2-A-2 of Scheme 2 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222850 | 0406 | - | A | Correction on overlapping PUCCHs with repetitions of a same priority | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222854 | 0407 | - | F | CR on CSI on LP PUSCH with CG-UCI | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222854 | 0408 | - | F | Correction of PUCCH repetition for semi-static PUCCH cell switching | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0409 | - | F | CR on dci-enabler for Type1 HARQ-ACK CB for multicast | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222869 | 0411 | - | A | Correction on SCS configuration for parallel transmission of PRACH and SRS/PUCCH/PUSCH | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222868 | 0412 | 1 | F | Rel-17 editorial corrections for TS 38.213 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222852 | 0413 | - | F | CR on PDCCH monitoring for inter-cell beam management | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222852 | 0414 | - | F | Clarification on HARQ feedback for TCI state update indication | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0415 | 2 | F | CR on interpretation of moreThanOneNackOnlyMode | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0416 | - | F | CR on NACK-only mode 2 multicast feedback | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0417 | - | F | CR on alignment of moreThanOneNackOnlyMode | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222854 | 0419 | - | F | Correction on triggering of enhanced Type-3 codebook | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222854 | 0420 | - | F | Correction on PUCCH cell switching | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222854 | 0421 | - | F | Correction on HARQ-ACK reporting on PUSCH for Rel-17 Intra-UE multiplexing | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222869 | 0423 | - | A | Clarification on timelines for power control command | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222858 | 0424 | - | F | Correction on PDCCH monitoring adaptation and BWP switching | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222853 | 0425 | - | F | Correction of number of configured DL-CCs for BD/CCE budget for FR2-2 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222853 | 0426 | - | F | Correction on per-slot group monitoring within a duration for FR2-2 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222850 | 0428 | - | F | Correction on UL prioritization cases related to SP-CSI in TS 38.213 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0429 | - | F | CR on broadcast search space monitoring occasion determination | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222862 | 0430 | - | F | Correction on RB set size for Rel-17 IAB HSNA configuration | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222862 | 0431 | - | F | Correction on DL TX power adjustment for Rel-17 IAB | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0432 | - | F | CR on PUCCH resource determination of multicast HARQ-ACK | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0433 | - | F | CR on multiplexing HARQ-ACK for DG and SPS multicast and unicast | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0434 | - | F | CR on HARQ-ACK codebook generation for RRC disabled HARQ-ACK feedback | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0435 | - | F | CR on NACK-only mode 2 multicast feedback | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222870 | 0436 | - | F | Correction on SL open loop power control parameters | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222869 | 0438 | - | A | Rel-16 editorial corrections for TS 38.213 (mirrored to Rel-17) | 17.4.0 | +| 2023-03 | RAN#99 | RP-230447 | 0439 | - | F | Corrections on PDCCH Skipping | 17.5.0 | +| 2023-03 | RAN#99 | RP-230451 | 0440 | - | F | CR on HARQ-ACK timing for multicast | 17.5.0 | +| 2023-03 | RAN#99 | RP-230451 | 0441 | - | F | CR on multiplexing Type-2 HARQ-ACK codebook in a PUSCH | 17.5.0 | +| 2023-03 | RAN#99 | RP-230443 | 0442 | - | F | Miscellaneous corrections on Rel-17 URLLC / IIoT in 38.213 | 17.5.0 | +| 2023-03 | RAN#99 | RP-230445 | 0444 | - | A | CR on positioning SRS power control in 38.213 | 17.5.0 | +| 2023-03 | RAN#99 | RP-230441 | 0445 | - | F | CR on PHR for mTRP PUSCH repetitions | 17.5.0 | +| 2023-03 | RAN#99 | RP-230451 | 0446 | - | F | CR on broadcast PDCCH monitoring in active DL BWP | 17.5.0 | +| 2023-03 | RAN#99 | RP-230452 | 0447 | - | F | Correction on repetition for CG-SDT | 17.5.0 | +| 2023-03 | RAN#99 | RP-230442 | 0448 | - | F | Corrections to r17 PDCCH monitoring capability for CA and DC | 17.5.0 | +| 2023-03 | RAN#99 | RP-230450 | 0449 | - | F | Clarification on the timeline of transmitting/receiving PSFCH with control information | 17.5.0 | +| 2023-03 | RAN#99 | RP-230441 | 0450 | - | F | Corrections for Beam Failure Recovery related to unified TCI state framework | 17.5.0 | +| 2023-03 | RAN#99 | RP-230451 | 0452 | - | F | CR on PUCCH resource for UE configured with NACK-only mode2 for SPS | 17.5.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|---------------------------------------------------------------------------------------------|--------| +| 2023-03 | RAN#99 | RP-230451 | 0453 | - | F | CR on PUCCH resources for multiplexing multicast HARQ-ACK | 17.5.0 | +| 2023-03 | RAN#99 | RP-230446 | 0454 | - | F | Corrections on impact of HD-FDD operation for RedCap UE | 17.5.0 | +| 2023-03 | RAN#99 | RP-230449 | 0455 | - | F | Correction on availability indication for eIAB | 17.5.0 | +| 2023-03 | RAN#99 | RP-230449 | 0456 | - | F | CR editorial correction on RRC parameters | 17.5.0 | +| 2023-03 | RAN#99 | RP-230449 | 0457 | - | F | Correction on the availability of a soft RB set in an RB set group in TS38.213 | 17.5.0 | +| 2023-03 | RAN#99 | RP-230444 | 0458 | - | F | CR on the Type-1 HARQ-ACK codebook | 17.5.0 | +| 2023-03 | RAN#99 | RP-230439 | 0460 | - | A | Corrections on PSFCH power determination in TS 38.213 | 17.5.0 | +| 2023-03 | RAN#99 | RP-230440 | 0462 | - | A | Rel-16 editorial corrections for TS 38.213 (mirrored to Rel-17) | 17.5.0 | +| 2023-03 | RAN#99 | RP-230453 | 0463 | - | F | Rel-17 editorial corrections for TS 38.213 | 17.5.0 | +| 2023-06 | RAN#100 | RP-231230 | 0466 | - | A | Correction on the mapping of PDSCH-to-HARQ_feedback timing indicator field values in Rel-17 | 17.6.0 | +| 2023-06 | RAN#100 | RP-231220 | 0467 | - | F | CR on enhanced type-3 HARQ-ACK codebook | 17.6.0 | +| 2023-06 | RAN#100 | RP-231221 | 0468 | - | F | Corrections on Type-3 HARQ-ACK codebook | 17.6.0 | +| 2023-06 | RAN#100 | RP-231227 | 0470 | - | A | Clarification of HARQ-ACK transmission for the 1st SPS PDSCH | 17.6.0 | +| 2023-06 | RAN#100 | RP-231228 | 0472 | - | F | Correction on impact of DAPS handover in Rel-17 | 17.6.0 | +| 2023-06 | RAN#100 | RP-231225 | 0473 | - | F | Correction on redundancy version for CG-SDT in TS 38.213 | 17.6.0 | +| 2023-06 | RAN#100 | RP-231232 | 0474 | - | F | CR on Type1 HARQ-ACK CB issue with more than one PDSCH per slot | 17.6.0 | +| 2023-06 | RAN#100 | RP-231219 | 0475 | - | F | CR on value range mismatch of p0 for SRS in Rel-17 unified TCI framework | 17.6.0 | +| 2023-06 | RAN#100 | RP-231222 | 0476 | - | F | Correction on RRC parameters in eIAB | 17.6.0 | +| 2023-06 | RAN#100 | RP-231222 | 0477 | - | F | Correction on reference SCS for availability indication in eIAB | 17.6.0 | +| 2023-06 | RAN#100 | RP-231224 | 0478 | - | F | CR on condition for not providing Type-1 CB | 17.6.0 | +| 2023-06 | RAN#100 | RP-231224 | 0479 | - | F | CR on Type-1 HARQ-ACK codebook for multicast | 17.6.0 | +| 2023-06 | RAN#100 | RP-231224 | 0480 | - | F | CR on HARQ-ACK for SPS release | 17.6.0 | +| 2023-06 | RAN#100 | RP-231224 | 0481 | - | F | CR on SPS release via multicast DCI | 17.6.0 | +| 2023-06 | RAN#100 | RP-231225 | 0482 | - | F | Clarification of RA-SDT operation for RedCap UEs in TDD | 17.6.0 | +| 2023-06 | RAN#100 | RP-231226 | 0483 | - | F | Rel-17 editorial corrections for TS 38.213 | 17.6.0 | +| 2023-09 | RAN#101 | RP-232448 | 0484 | - | F | Correction on description of valid PSFCH occasion for scheme 2 in TS 38.213 | 17.7.0 | +| 2023-09 | RAN#101 | RP-232447 | 0485 | - | F | Miscellaneous corrections on Rel-17 enhanced URLLC & IIoT | 17.7.0 | +| 2023-09 | RAN#101 | RP-232446 | 0486 | - | F | Correction on HARQ-ACK timing for FR2-2 | 17.7.0 | +| 2023-09 | RAN#101 | RP-232457 | 0487 | - | F | Corrections on PDCCH Monitoring Adaptation | 17.7.0 | +| 2023-09 | RAN#101 | RP-232457 | 0488 | - | F | Alignment on SSSG Switching | 17.7.0 | +| 2023-09 | RAN#101 | RP-232455 | 0489 | - | F | Correction to CORESET0 selection for new BWs of bands n79 and n104 | 17.7.0 | +| 2023-09 | RAN#101 | RP-232449 | 0490 | - | F | CR on multiplexing NACK-only, CSI and SR in a PUCCH | 17.7.0 | +| 2023-09 | RAN#101 | RP-232453 | 0491 | - | F | Correction on Type-2 HARQ-ACK codebook | 17.7.0 | +| 2023-09 | RAN#101 | RP-232451 | 0493 | - | A | Correction on DCI 2_0 fields for operation with shared spectrum channel access | 17.7.0 | +| 2023-09 | RAN#101 | RP-232450 | 0495 | - | F | Clarification of TDD UL validation and SDT operation for RedCap UEs | 17.7.0 | +| 2023-09 | RAN#101 | RP-232449 | 0496 | - | F | CR on HARQ-ACK codebook for maxNrofCodeWords | 17.7.0 | +| 2023-09 | RAN#101 | RP-232449 | 0497 | - | F | CR on K1 timing for type 1 codebook | 17.7.0 | +| 2023-09 | RAN#101 | RP-232449 | 0498 | - | F | CR on HARQ-ACK codebook for multicast SPS | 17.7.0 | +| 2023-09 | RAN#101 | RP-232531 | 0499 | - | F | Rel-17 editorial corrections for TS 38.213 | 17.7.0 | +| 2023-09 | RAN#101 | RP-232696 | 0512 | 1 | F | Correction to SCell PRACH power scaling for UL CA | 17.7.0 | +| 2023-09 | RAN#101 | RP-232470 | 0500 | - | B | Introduction of dynamic spectrum sharing (DSS) | 18.0.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|----------------------------------------------------------------------------|--------| +| | | | | | | enhancements | | +| 2023-09 | RAN#101 | RP-232478 | 0501 | - | B | Introduction of support for enhanced reduced capability NR devices | 18.0.0 | +| 2023-09 | RAN#101 | RP-232477 | 0502 | - | B | Introduction of NR support for dedicated spectrum less than 5MHz for FR1 | 18.0.0 | +| 2023-09 | RAN#101 | RP-232471 | 0503 | - | B | Introduction of multi-carrier enhancements for NR | 18.0.0 | +| 2023-09 | RAN#101 | RP-232458 | 0504 | - | B | Introduction of MIMO Evolution for Downlink and Uplink | 18.0.0 | +| 2023-09 | RAN#101 | RP-232473 | 0505 | - | B | Introduction of further mobility enhancements | 18.0.0 | +| 2023-09 | RAN#101 | RP-232479 | 0506 | - | B | Introduction of Network Controlled Repeaters | 18.0.0 | +| 2023-09 | RAN#101 | RP-232474 | 0507 | - | B | Introduction of NR NTN enhancements | 18.0.0 | +| 2023-09 | RAN#101 | RP-232480 | 0508 | - | B | Introduction of expanded and improved NR positioning | 18.0.0 | +| 2023-09 | RAN#101 | RP-232469 | 0509 | - | B | Introduction of NR sidelink evolution | 18.0.0 | +| 2023-09 | RAN#101 | RP-232483 | 0510 | - | B | Introduction of BWP operation without restriction | 18.0.0 | +| 2023-09 | RAN#101 | RP-232472 | 0513 | - | B | Introduction of further NR coverage enhancements | 18.0.0 | +| 2023-09 | RAN#101 | RP-232481 | 0514 | - | B | Introduction of network energy savings for NR | 18.0.0 | +| 2023-09 | RAN#101 | RP-232482 | 0515 | - | B | Introduction of XR Enhancements for NR | 18.0.0 | +| 2023-12 | RAN#102 | RP-233698 | 0518 | - | A | Correction on minimum time gap for DCI format 2_6 | 18.1.0 | +| 2023-12 | RAN#102 | RP-233702 | 0520 | - | A | Correction on Type1A search space for SDT | 18.1.0 | +| 2023-12 | RAN#102 | RP-233698 | 0522 | 1 | A | Correction on Type-2 HARQ-ACK codebook for multi-slot scheduling | 18.1.0 | +| 2023-12 | RAN#102 | RP-233698 | 0524 | - | A | Correction on PUCCH power determination for Type-2 HARQ-ACK codebook | 18.1.0 | +| 2023-12 | RAN#102 | RP-233701 | 0526 | - | A | CR on Type-2 HARQ-ACK codebook on PUSCH | 18.1.0 | +| 2023-12 | RAN#102 | RP-233701 | 0528 | - | A | CR on PUCCH resources for multicast HARQ-ACK | 18.1.0 | +| 2023-12 | RAN#102 | RP-233723 | 0531 | - | A | CR on SL NACK report to gNB in mode 1 (Rel-18) | 18.1.0 | +| 2023-12 | RAN#102 | RP-233727 | 0533 | - | A | Correction on multiple DCIs per MO per CC for the Type-2 HARQ-ACK codebook | 18.1.0 | +| 2023-12 | RAN#102 | RP-233727 | 0535 | - | A | Path Loss reference RS for SCell UL PC when PL RS is not configured | 18.1.0 | +| 2023-12 | RAN#102 | RP-233727 | 0537 | - | A | Clarification of HARQ-ACK for MsgB PDSCH | 18.1.0 | +| 2023-12 | RAN#102 | RP-233699 | 0539 | - | A | Correction on PUCCH power control parameter determination | 18.1.0 | +| 2023-12 | RAN#102 | RP-233697 | 0541 | - | A | Correction on HARQ feedback for TCI state update indication | 18.1.0 | +| 2023-12 | RAN#102 | RP-233734 | 0543 | - | A | CR on transmission timing adjustments for Rel-17 NR-NTN | 18.1.0 | +| 2023-12 | RAN#102 | RP-233698 | 0545 | - | A | Correction on CSI related timeline for 480/960 kHz | 18.1.0 | +| 2023-12 | RAN#102 | RP-233730 | 0548 | - | A | CR on default pathloss reference signal for SRS and PUCCH | 18.1.0 | +| 2023-12 | RAN#102 | RP-233704 | 0551 | - | A | Correction of PDCCH monitoring adaptation behaviour for DRX groups | 18.1.0 | +| 2023-12 | RAN#102 | RP-233701 | 0553 | - | A | CR on Type-1 HARQ-ACK codebook on PUSCH | 18.1.0 | +| 2023-12 | RAN#102 | RP-233701 | 0555 | - | A | CR on PDCCH monitoring in Type0B CSS for HD-FDD RedCap UEs | 18.1.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------|--------| +| 2023-12 | RAN#102 | RP-233727 | 0557 | - | A | CR on Simultaneous PUCCH and PUSCH transmission with same priority in UL CA | 18.1.0 | +| 2023-12 | RAN#102 | RP-233727 | 0559 | - | A | Clarification on the first SPS PDSCH and Type2 CG PUSCH | 18.1.0 | +| 2023-12 | RAN#102 | RP-233701 | 0561 | - | A | CR on HARQ-ACK for SPS PDSCH | 18.1.0 | +| 2023-12 | RAN#102 | RP-233722 | 0562 | - | B | Introduction of extended CG-SDT periodicities [CG-SDT-Enh] | 18.1.0 | +| 2023-12 | RAN#102 | RP-233736 | 0564 | - | A | Correction of monitoring of paging occasions for CG-SDT with HD-FDD RedCap UEs | 18.1.0 | +| 2023-12 | RAN#102 | RP-233736 | 0566 | 1 | A | Correction of PUCCH repetition for RedCap UE with NCD-SSB in TDD | 18.1.0 | +| 2023-12 | RAN#102 | RP-233722 | 0567 | - | B | Introduction of RS for pathloss determination of Type 1 CG PUSCH [PL RS Type 1 CG] | 18.1.0 | +| 2023-12 | RAN#102 | RP-233722 | 0569 | - | B | Introduction of QCL-TypeD priorities for overlapping CORESETs in M-DCI/M-TRP operation [QCL-TypeD CORESET priority for M-TRP] | 18.1.0 | +| 2023-12 | RAN#102 | RP-233728 | 0571 | - | A | Rel-17 editorial corrections for TS 38.213 (mirrored to Rel-18) | 18.1.0 | +| 2023-12 | RAN#102 | RP-233709 | 0572 | - | F | Maintenance of further NR coverage enhancements | 18.1.0 | +| 2023-12 | RAN#102 | RP-233710 | 0573 | - | F | Maintenance of further mobility enhancements | 18.1.0 | +| 2023-12 | RAN#102 | RP-233707 | 0574 | - | F | Maintenance of dynamic spectrum sharing (DSS) enhancements | 18.1.0 | +| 2023-12 | RAN#102 | RP-233708 | 0575 | - | F | Maintenance of multi-carrier enhancements for NR | 18.1.0 | +| 2023-12 | RAN#102 | RP-233705 | 0576 | - | F | Maintenance of MIMO Evolution for Downlink and Uplink | 18.1.0 | +| 2023-12 | RAN#102 | RP-233718 | 0577 | - | F | Maintenance of Network Controlled Repeaters | 18.1.0 | +| 2023-12 | RAN#102 | RP-233720 | 0578 | - | F | Maintenance of network energy savings for NR | 18.1.0 | +| 2023-12 | RAN#102 | RP-233719 | 0579 | - | F | Maintenance of expanded and improved NR positioning | 18.1.0 | +| 2023-12 | RAN#102 | RP-233717 | 0580 | - | F | Maintenance of support for enhanced reduced capability NR devices | 18.1.0 | +| 2023-12 | RAN#102 | RP-233706 | 0581 | - | F | Maintenance of NR sidelink evolution | 18.1.0 | +| 2023-12 | RAN#102 | RP-233721 | 0582 | - | F | Maintenance of XR enhancements for NR | 18.1.0 | +| 2023-12 | RAN#102 | RP-233716 | 0583 | - | F | Maintenance of support for dedicated spectrum less than 5MHz for FR1 | 18.1.0 | +| 2023-12 | RAN#102 | RP-233733 | 0584 | - | B | Introduction of Rel-18 enhancements of NR Multicast and Broadcast Services | 18.1.0 | +| 2023-12 | RAN#102 | RP-233714 | 0585 | - | F | Maintenance of support for NR NTN enhancements | 18.1.0 | +| 2023-12 | RAN#102 | RP-233737 | 0586 | - | F | Maintenance of BWP operation without restriction | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38214/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38214/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..000e7c770a43a250b20ee71eda136f0927575b61 --- /dev/null +++ b/marked/Rel-18/38_series/38214/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43e5f9410dbb9f9ebd57da0a8f289647523d9d6848147865f5f9e1f03de0e9d8 +size 9704 diff --git a/marked/Rel-18/38_series/38214/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38214/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b8077bc949f5a0000b56eafb8aea3e82aebc90d --- /dev/null +++ b/marked/Rel-18/38_series/38214/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4e9dd8e609e1ab14894cce25532a9e6bd72a622b6f8b79fc4ac241fb530fcfc +size 6208 diff --git a/marked/Rel-18/38_series/38214/raw.md b/marked/Rel-18/38_series/38214/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..bf495fbb5afd6d30793b3ff98b19192fbfd76140 --- /dev/null +++ b/marked/Rel-18/38_series/38214/raw.md @@ -0,0 +1,8311 @@ + + +# 3GPP TS 38.214 V18.1.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data (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 capital 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, New 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 + + +**3GPP** + +# Contents + +| | | +|----------------------------------------------------------------------------------------------------------|----| +| Foreword..... | 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 Power control..... | 10 | +| 4.1 Power allocation for downlink..... | 10 | +| 5 Physical downlink shared channel related procedures..... | 11 | +| 5.1 UE procedure for receiving the physical downlink shared channel..... | 11 | +| 5.1.1 Transmission schemes..... | 17 | +| 5.1.1.1 Transmission scheme 1..... | 17 | +| 5.1.2 Resource allocation..... | 17 | +| 5.1.2.1 Resource allocation in time domain..... | 17 | +| 5.1.2.1.1 Determination of the resource allocation table to be used for PDSCH..... | 22 | +| 5.1.2.2 Resource allocation in frequency domain..... | 26 | +| 5.1.2.2.1 Downlink resource allocation type 0..... | 26 | +| 5.1.2.2.2 Downlink resource allocation type 1..... | 27 | +| 5.1.2.2.3 Downlink resource allocation type 1 for multicast/broadcast..... | 28 | +| 5.1.2.3 Physical resource block (PRB) bundling..... | 29 | +| 5.1.3 Modulation order, target code rate, redundancy version and transport block size determination..... | 30 | +| 5.1.3.1 Modulation order and target code rate determination..... | 32 | +| 5.1.3.2 Transport block size determination..... | 38 | +| 5.1.4 PDSCH resource mapping..... | 42 | +| 5.1.4.1 PDSCH resource mapping with RB symbol level granularity..... | 42 | +| 5.1.4.2 PDSCH resource mapping with RE level granularity..... | 43 | +| 5.1.5 Antenna ports quasi co-location..... | 46 | +| 5.1.6 UE procedure for receiving reference signals..... | 54 | +| 5.1.6.1 CSI-RS reception procedure..... | 54 | +| 5.1.6.1.1 CSI-RS for tracking..... | 55 | +| 5.1.6.1.2 CSI-RS for L1-RSRP and L1-SINR computation..... | 57 | +| 5.1.6.1.3 CSI-RS for mobility..... | 58 | +| 5.1.6.2 DM-RS reception procedure..... | 58 | +| 5.1.6.3 PT-RS reception procedure..... | 62 | +| 5.1.6.4 SRS reception procedure for CLI..... | 64 | +| 5.1.6.5 PRS reception procedure..... | 64 | +| 5.1.6.5.1 PRS receiver frequency hopping..... | 71 | +| 5.1.6.5.2 PRS for carrier phase positioning..... | 72 | +| 5.1.6.5.3 PRS bandwidth aggregation for positioning measurements..... | 72 | +| 5.1.7 Code block group based PDSCH transmission..... | 73 | +| 5.1.7.1 UE procedure for grouping of code blocks to code block groups..... | 73 | + +###### 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 + +| | | | +|------------|-------------------------------------------------------------------------------------------------------------------------------|-----| +| 5.1.7.2 | UE procedure for receiving code block group based transmissions..... | 73 | +| 5.2 | UE procedure for reporting channel state information (CSI)..... | 74 | +| 5.2.1 | Channel state information framework..... | 74 | +| 5.2.1.1 | Reporting settings..... | 74 | +| 5.2.1.2 | Resource settings..... | 75 | +| 5.2.1.3 | (void)..... | 76 | +| 5.2.1.4 | Reporting configurations..... | 76 | +| 5.2.1.4.1 | Resource Setting configuration..... | 79 | +| 5.2.1.4.2 | Report quantity configurations..... | 81 | +| 5.2.1.4.3 | L1-RSRP Reporting..... | 88 | +| 5.2.1.4.4 | L1-SINR Reporting..... | 88 | +| 5.2.1.4.5 | TDCP Reporting..... | 89 | +| 5.2.1.5 | Triggering/activation of CSI Reports and CSI-RS..... | 90 | +| 5.2.1.5.1 | Aperiodic CSI Reporting/Aperiodic CSI-RS when the triggering PDCCH and the CSI-RS have the same numerology..... | 90 | +| 5.2.1.5.1a | Aperiodic CSI Reporting/Aperiodic CSI-RS when the triggering PDCCH and the CSI-RS have different numerologies..... | 95 | +| 5.2.1.5.2 | Semi-persistent CSI/Semi-persistent CSI-RS..... | 97 | +| 5.2.1.5.3 | Aperiodic CSI-RS for tracking for fast SCell activation..... | 99 | +| 5.2.1.6 | CSI processing criteria..... | 99 | +| 5.2.2 | Channel state information..... | 101 | +| 5.2.2.1 | Channel quality indicator (CQI)..... | 101 | +| 5.2.2.1.1 | (void)..... | 104 | +| 5.2.2.2 | Precoding matrix indicator (PMI)..... | 104 | +| 5.2.2.2.1 | Type I Single-Panel Codebook..... | 104 | +| 5.2.2.2.2 | Type I Multi-Panel Codebook..... | 110 | +| 5.2.2.2.3 | Type II Codebook..... | 114 | +| 5.2.2.2.4 | Type II Port Selection Codebook..... | 120 | +| 5.2.2.2.5 | Enhanced Type II Codebook..... | 123 | +| 5.2.2.2.6 | Enhanced Type II Port Selection Codebook..... | 130 | +| 5.2.2.2.7 | Further enhanced Type II port selection codebook..... | 131 | +| 5.2.2.2.8 | Enhanced Type II codebook for CJT..... | 136 | +| 5.2.2.2.9 | Further enhanced Type II port selection codebook for CJT..... | 142 | +| 5.2.2.2.10 | Enhanced Type II codebook for predicted PMI..... | 148 | +| 5.2.2.2.11 | Further enhanced Type II port selection codebook for predicted PMI..... | 152 | +| 5.2.2.3 | Reference signal (CSI-RS)..... | 153 | +| 5.2.2.3.1 | NZP CSI-RS..... | 153 | +| 5.2.2.4 | Channel State Information – Interference Measurement (CSI-IM)..... | 154 | +| 5.2.2.5 | CSI reference resource definition..... | 154 | +| 5.2.2.5.1 | UE assumptions for CQI/PMI/RI calculation..... | 156 | +| 5.2.2.5.1a | UE assumptions for CQI/PMI/RI calculation for NCJT..... | 158 | +| 5.2.2.5.1b | UE assumptions for CQI/PMI/RI calculation for CJT..... | 158 | +| 5.2.2.5.1c | UE assumptions for CQI/PMI/RI calculation for predicted CSI..... | 159 | +| 5.2.3 | CSI reporting using PUSCH..... | 159 | +| 5.2.4 | CSI reporting using PUCCH..... | 165 | +| 5.2.5 | Priority rules for CSI reports..... | 166 | +| 5.3 | UE PDSCH processing procedure time..... | 167 | +| 5.3.1 | Application delay of the minimum scheduling offset restriction..... | 169 | +| 5.4 | UE CSI computation time..... | 170 | +| 5.5 | UE PDSCH reception preparation time with cross carrier scheduling with different subcarrier spacings for PDCCH and PDSCH..... | 172 | +| 6 | Physical uplink shared channel related procedure..... | 172 | +| 6.1 | UE procedure for transmitting the physical uplink shared channel..... | 172 | +| 6.1.1 | Transmission schemes..... | 176 | +| 6.1.1.1 | Codebook based UL transmission..... | 176 | +| 6.1.1.2 | Non-Codebook based UL transmission..... | 180 | +| 6.1.2 | Resource allocation..... | 182 | +| 6.1.2.1 | Resource allocation in time domain..... | 182 | +| 6.1.2.1.1 | Determination of the resource allocation table to be used for PUSCH..... | 193 | +| 6.1.2.2 | Resource allocation in frequency domain..... | 196 | +| 6.1.2.2.1 | Uplink resource allocation type 0..... | 196 | + +| | | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 6.1.2.2.2 | Uplink resource allocation type 1..... | 197 | +| 6.1.2.2.3 | Uplink resource allocation type 2..... | 198 | +| 6.1.2.3 | Resource allocation for uplink transmission with configured grant..... | 199 | +| 6.1.2.3.1 | Transport Block repetition for uplink transmissions of PUSCH repetition Type A with a configured grant..... | 202 | +| 6.1.2.3.2 | Transport Block repetition for uplink transmissions of PUSCH repetition Type B with a configured grant..... | 203 | +| 6.1.2.3.3 | Transport Block repetition for uplink transmissions of TB processing over multiple slots with a configured grant..... | 204 | +| 6.1.3 | UE procedure for applying transform precoding on PUSCH..... | 205 | +| 6.1.4 | Modulation order, redundancy version and transport block size determination..... | 206 | +| 6.1.4.1 | Modulation order and target code rate determination..... | 207 | +| 6.1.4.2 | Transport block size determination..... | 212 | +| 6.1.5 | Code block group based PUSCH transmission..... | 213 | +| 6.1.5.1 | UE procedure for grouping of code blocks to code block groups..... | 214 | +| 6.1.5.2 | UE procedure for transmitting code block group based transmissions..... | 214 | +| 6.1.6 | Uplink switching..... | 214 | +| 6.1.6.1 | Uplink switching for EN-DC..... | 215 | +| 6.1.6.2 | Uplink switching for carrier aggregation..... | 216 | +| 6.1.6.2.0 | Uplink switching with two uplink bands..... | 216 | +| 6.1.6.2.1 | void..... | 216 | +| 6.1.6.2.2 | Uplink switching with 3 or 4 uplink bands..... | 216 | +| 6.1.6.3 | Uplink switching with two uplink bands for supplementary uplink..... | 217 | +| 6.1.7 | UE procedure for determining time domain windows for bundling DM-RS..... | 218 | +| 6.2 | UE reference signal (RS) procedure..... | 221 | +| 6.2.1 | UE sounding procedure..... | 221 | +| 6.2.1.1 | UE SRS frequency hopping procedure..... | 229 | +| 6.2.1.2 | UE sounding procedure for DL CSI acquisition..... | 229 | +| 6.2.1.3 | UE sounding procedure between component carriers..... | 234 | +| 6.2.1.4 | UE sounding procedure for positioning purposes..... | 236 | +| 6.2.1.4.1 | SRS frequency hopping for positioning..... | 238 | +| 6.2.1.4.2 | SRS bandwidth aggregation for positioning measurements..... | 239 | +| 6.2.2 | UE DM-RS transmission procedure..... | 239 | +| 6.2.3 | UE PT-RS transmission procedure..... | 241 | +| 6.2.3.1 | UE PT-RS transmission procedure when transform precoding is not enabled..... | 241 | +| 6.2.3.2 | UE PT-RS transmission procedure when transform precoding is enabled..... | 245 | +| 6.3 | UE PUSCH frequency hopping procedure..... | 246 | +| 6.3.1 | Frequency hopping for PUSCH repetition Type A and for TB processing over multiple slots..... | 246 | +| 6.3.2 | Frequency hopping for PUSCH repetition Type B..... | 247 | +| 6.4 | UE PUSCH preparation procedure time..... | 248 | +| 7 | UE procedures for transmitting and receiving on a carrier with intra-cell guard bands..... | 249 | +| 8 | Physical sidelink shared channel related procedures..... | 250 | +| 8.1 | UE procedure for transmitting the physical sidelink shared channel..... | 251 | +| 8.1.1 | Transmission schemes..... | 253 | +| 8.1.2 | Resource allocation..... | 253 | +| 8.1.2.1 | Resource allocation in time domain..... | 254 | +| 8.1.2.2 | Resource allocation in frequency domain..... | 255 | +| 8.1.3 | Modulation order, target code rate, redundancy version and transport block size determination..... | 255 | +| 8.1.3.1 | Modulation order and target code rate determination..... | 255 | +| 8.1.3.2 | Transport block size determination..... | 256 | +| 8.1.4 | UE procedure for determining the subset of resources to be reported to higher layers in PSSCH resource selection in sidelink resource allocation mode 2..... | 257 | +| 8.1.4A | UE procedure for determining a set of preferred or non-preferred resources for another UE's transmission..... | 265 | +| 8.1.4B | Void..... | 266 | +| 8.1.4C | UE procedure for using a received non-preferred resource set..... | 266 | +| 8.1.5 | UE procedure for determining slots and resource blocks for PSSCH transmission associated with an SCI format 1-A..... | 266 | +| 8.1.5A | UE procedure for determining slots and resource blocks indicated by a preferred or non-preferred resource set..... | 268 | + +| | | | +|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| 8.1.6 | Sidelink congestion control in sidelink resource allocation mode 2..... | 269 | +| 8.1.7 | UE procedure for determining the number of logical slots for a reservation period..... | 269 | +| 8.2 | UE procedure for transmitting sidelink reference signals..... | 269 | +| 8.2.1 | CSI-RS transmission procedure..... | 269 | +| 8.2.2 | PSSCH DM-RS transmission procedure..... | 270 | +| 8.2.3 | PT-RS transmission procedure..... | 270 | +| 8.2.4 | SL PRS transmission procedure..... | 270 | +| 8.2.4.1 | Resource allocation..... | 271 | +| 8.2.4.1.1 | Resource allocation in time domain..... | 271 | +| 8.2.4.1.2 | Resource allocation in frequency domain..... | 272 | +| 8.2.4.2 | UE procedure for determining the subset of resources to be reported to higher layers in SL PRS resource selection in a dedicated SL PRS resource pool in sidelink resource allocation mode 2..... | 272 | +| 8.2.4.2A | UE procedure for determining slots and SL PRS resource(s) associated with an SCI format 1-B in a dedicated SL PRS resource pool..... | 273 | +| 8.2.4.3 | Sidelink congestion control in a dedicated SL PRS resource pool in sidelink resource allocation mode 2..... | 274 | +| 8.3 | UE procedure for receiving the physical sidelink shared channel..... | 274 | +| 8.4 | UE procedure for receiving reference signals..... | 274 | +| 8.4.1 | CSI-RS reception procedure..... | 274 | +| 8.4.2 | DM-RS reception procedure for RSRP computation..... | 274 | +| 8.4.3 | PT-RS reception procedure..... | 274 | +| 8.4.4 | SL PRS reception procedure..... | 275 | +| 8.5 | UE procedure for reporting channel state information (CSI)..... | 275 | +| 8.5.1 | Channel state information framework..... | 275 | +| 8.5.1.1 | Reporting configurations..... | 275 | +| 8.5.1.2 | Triggering of sidelink CSI reports..... | 276 | +| 8.5.2 | Channel state information..... | 276 | +| 8.5.2.1 | CSI reporting quantities..... | 276 | +| 8.5.2.1.1 | Channel quality indicator (CQI)..... | 276 | +| 8.5.2.2 | Reference signal (CSI-RS)..... | 276 | +| 8.5.2.3 | CSI reference resource definition..... | 277 | +| 8.5.3 | CSI reporting..... | 277 | +| 8.6 | UE PSSCH preparation procedure time..... | 277 | +| 9 | UE procedures for transmitting and receiving for RTT-based propagation delay compensation..... | 278 | +| 9.1 | PRS reception procedure for RTT-based propagation delay compensation..... | 279 | +| Annex <A> (informative): | Change history..... | 281 | + +# --- 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 physicals layer procedures of data channels for 5G-NR. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications" +- [2] 3GPP TS 38.201: " NR; Physical Layer – General Description" +- [3] 3GPP TS 38.202: "NR; Services provided by the physical layer" +- [4] 3GPP TS 38.211: "NR; Physical channels and modulation" +- [5] 3GPP TS 38.212: "NR; Multiplexing and channel coding" +- [6] 3GPP TS 38.213: "NR; Physical layer procedures for control" +- [7] 3GPP TS 38.215: "NR; Physical layer measurements" +- [8] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone" +- [9] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception" +- [10] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification" +- [11] 3GPP TS 38.133: "NR; Requirements for support of radio resource management" +- [12] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification" +- [13] 3GPP TS 38.306: "NR; User Equipment (UE) radio access capabilities" +- [14] 3GPP TS 38.423: "NG-RAN; Xn Application Protocol (XnAP)" +- [15] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation" +- [16] 3GPP TS 37.213: "Physical layer procedures for shared spectrum channel access" +- [17] 3GPP TS 37.355: "LTE Positioning Protocol (LPP)" +- [18] 3GPP TS 38.822: "NR; User Equipment (UE) feature list" +- [19] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures" +- [20] 3GPP TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN" + +# 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] 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: + +## 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]. + +| | | +|----------|-----------------------------------------------------| +| ARP | Antenna Reference Point | +| BWP | Bandwidth Part | +| CBG | Code Block Group | +| CJT | Coherent Joint Transmission | +| CLI | Cross Link Interference | +| CP | Cyclic Prefix | +| CQI | Channel Quality Indicator | +| CPU | CSI Processing Unit | +| CRB | Common Resource Block | +| CRC | Cyclic Redundancy Check | +| CRI | CSI-RS Resource Indicator | +| CSI | Channel State Information | +| CSI-RS | Channel State Information Reference Signal | +| CSI-RSRP | CSI Reference Signal Received Power | +| CSI-RSRQ | CSI Reference Signal Received Quality | +| CSI-SINR | CSI Signal-to-Interference-plus-Noise Ratio | +| CW | Codeword | +| DCI | Downlink Control Information | +| DL | Downlink | +| DM-RS | Demodulation Reference Signal | +| DRX | Discontinuous Reception | +| EPRE | Energy Per Resource Element | +| IAB-MT | Integrated Access and Backhaul – Mobile Termination | +| L1-RSRP | Layer 1 Reference Signal Received Power | +| LI | Layer Indicator | +| LoS | Line of Sight | +| MCS | Modulation and Coding Scheme | +| NCJT | Non-Coherent Joint Transmission | +| NCR | Network-controlled Repeater | +| NCR-MT | Network controlled repeater – Mobile Termination | +| NLoS | Non-Line of Sight | +| PDCCH | Physical Downlink Control Channel | +| PDSCH | Physical Downlink Shared Channel | +| PSS | Primary Synchronisation Signal | +| PUCCH | Physical Uplink Control Channel | +| QCL | Quasi Co-Location | +| PMI | Precoding Matrix Indicator | +| PRB | Physical Resource Block | +| PRG | Precoding Resource block Group | +| PRS | Positioning Reference Signal | +| PT-RS | Phase-Tracking Reference Signal | +| RB | Resource Block | +| RBG | Resource Block Group | + +| | | +|---------|--------------------------------------------| +| RI | Rank Indicator | +| RIV | Resource Indicator Value | +| RS | Reference Signal | +| SCI | Sidelink Control Information | +| SL PRS | Sidelink Positioning Reference Signal | +| SLIV | Start and Length Indicator Value | +| SR | Scheduling Request | +| SRS | Sounding Reference Signal | +| SS | Synchronisation Signal | +| SSS | Secondary Synchronisation Signal | +| SS-RSRP | SS Reference Signal Received Power | +| SS-RSRQ | SS Reference Signal Received Quality | +| SS-SINR | SS Signal-to-Interference-plus-Noise Ratio | +| TB | Transport Block | +| TCI | Transmission Configuration Indicator | +| TDCP | Time Domain Channel Properties | +| TDM | Time Division Multiplexing | +| UE | User Equipment | +| UL | Uplink | + +# 4 Power control + +Throughout this specification, unless otherwise noted, statements using the term "UE" in clauses 4, 5, or 6 are equally applicable to the IAB-MT part of an IAB node and to the NCR-MT part of an NCR node. + +## 4.1 Power allocation for downlink + +The gNB determines the downlink transmit EPRE. + +For the purpose of SS-RSRP, SS-RSRQ and SS-SINR measurements, the UE may assume downlink EPRE is constant across the bandwidth. For the purpose of SS-RSRP, SS-RSRQ and SS-SINR measurements, the UE may assume downlink EPRE is constant over SSS carried in different SS/PBCH blocks. For the purpose of SS-RSRP, SS-RSRQ and SS-SINR measurements, the UE may assume that the ratio of SSS EPRE to PBCH DM-RS EPRE is 0 dB. + +For the purpose of CSI-RSRP, CSI-RSRQ and CSI-SINR measurements, the UE may assume downlink EPRE of a port of CSI-RS resource configuration is constant across the configured downlink bandwidth and constant across all configured OFDM symbols. + +The downlink SS/PBCH SSS EPRE can be derived from the SS/PBCH downlink transmit power given by the parameter *ss-PBCH-BlockPower* provided by higher layers. The downlink SSS transmit power is defined as the linear average over the power contributions (in [W]) of all resource elements that carry the SSS within the operating system bandwidth. + +The downlink CSI-RS EPRE can be derived from the SS/PBCH block downlink transmit power given by the parameter *ss-PBCH-BlockPower* and CSI-RS power offset given by the parameter *powerControlOffsetSS* provided by higher layers if the SS/PBCH block is associated with serving cell PCI, or derived from *ss-PBCH-BlockPower-r17* in *SSB-MTC-AdditionalPCI-r17* and *powerControlOffsetSS* provided by higher layers if the SS/PBCH block is associated with additional PCI different from serving cell PCI, where the CSI-RS is QCled with the SS/PBCH block. The downlink reference-signal transmit power is defined as the linear average over the power contributions (in [W]) of the resource elements that carry the configured CSI-RS within the operating system bandwidth. + +For downlink DM-RS associated with PDSCH, the UE may assume the ratio of PDSCH EPRE to DM-RS EPRE ( [dB]) is given by Table 4.1-1 according to the number of DM-RS CDM groups without data as described in Clause 5.1.6.2. + +The DM-RS scaling factor $\beta_{PDSCH}^{DMRS}$ specified in Clause 7.4.1.1.2 of [4, TS 38.211] is given by $\beta_{PDSCH}^{DMRS} = 10^{-\frac{\beta_{DMRS}}{20}}$ . + +**Table 4.1-1: The ratio of PDSCH EPRE to DM-RS EPRE** + +| Number of DM-RS CDM groups without data | DM-RS configuration type 1 and enhanced type 1 | DM-RS configuration type 2 and enhanced type 2 | +|-----------------------------------------|------------------------------------------------|------------------------------------------------| +| 1 | 0 dB | 0 dB | +| 2 | -3 dB | -3 dB | +| 3 | - | -4.77 dB | + +When the UE is scheduled with one or two PT-RS ports associated with the PDSCH, + +- if the UE is configured with the higher layer parameter *epre-Ratio*, the ratio of PT-RS EPRE to PDSCH EPRE per layer per RE for each PT-RS port ( $\rho_{PTRS}$ ) is given by Table 4.1-2 or Table 4.1-2A according to the *epre-Ratio*, the PT-RS scaling factor $\beta_{PTRS}$ specified in clause 7.4.1.2.2 of [4, TS 38.211] is given by $\beta_{PTRS} = 10^{\frac{\rho_{PTRS}}{20}}$ . +- otherwise, the UE shall assume *epre-Ratio* is set to state '0' in Table 4.1-2 if not configured. + +**Table 4.1-2: PT-RS EPRE to PDSCH EPRE per layer per RE ( $\rho_{PTRS}$ ), if [enhanced-dmrs-Type\_r18] is not configured in DMRS-DownlinkConfig** + +| epre-Ratio | The number of PDSCH layers with DM-RS associated to the PT-RS port | | | | | | +|------------|--------------------------------------------------------------------|---|------|---|---|------| +| | 1 | 2 | 3 | 4 | 5 | 6 | +| 0 | 0 | 3 | 4.77 | 6 | 7 | 7.78 | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | reserved | | | | | | +| 3 | reserved | | | | | | + +**Table 4.1-2A: PT-RS EPRE to PDSCH EPRE per layer per RE ( $\rho_{PTRS}$ ), if [enhanced-dmrs-Type\_r18] is configured in DMRS-DownlinkConfig** + +| epre-Ratio | The number of PDSCH layers with DM-RS associated to the PT-RS port | | | | | | | | +|------------|--------------------------------------------------------------------|---|------|---|---|------|------|---| +| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| 0 | 0 | 3 | 4.77 | 6 | 7 | 7.78 | 8.45 | 9 | +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | reserved | | | | | | | | +| 3 | reserved | | | | | | | | + +For link recovery, as described in clause 6 of [6, TS 38.213] the ratio of the PDCCH EPRE to NZP CSI-RS EPRE is assumed as 0 dB. + +# 5 Physical downlink shared channel related procedures + +## 5.1 UE procedure for receiving the physical downlink shared channel + +For downlink, a maximum of 16 HARQ processes per cell are supported by the UE, or subject to UE capability, a maximum of 32 HARQ processes per cell as defined in [13, TS 38.306]. The number of processes the UE may assume will at most be used for the downlink is configured to the UE for each cell separately by higher layer parameter *nrofHARQ-ProcessesForPDSCH* or *nrofHARQ-ProcessesForPDSCH-v1700*, and when no configuration is provided the UE may assume a default number of 8 processes. + +A UE shall upon detection of a PDCCH with a configured DCI format 1\_0, 1\_1, 1\_2, 1\_3, 4\_0, 4\_1, or 4\_2 decode the corresponding PDSCHs as indicated by that DCI. When the UE is scheduled with multiple PDSCHs on a serving cell by a DCI, HARQ process ID indicated by this DCI applies to the first PDSCH not overlapping with a UL symbol indicated by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* if provided, HARQ process ID is then incremented by 1 for each subsequent PDSCH(s) in the scheduled order, with modulo operation of *nrofHARQ-ProcessesForPDSCH* applied if *nrofHARQ-ProcessesForPDSCH* is provided, or with modulo operation of *nrofHARQ-* + +*ProcessesForPDSCH-v1700* applied if or *nrofHARQ-ProcessesForPDSCH-v1700* is provided, or with modulo operation of 8 applied, otherwise. HARQ process ID is not incremented for PDSCH(s) not received if at least one of the symbols indicated by the indexed row of the used resource allocation table in the slot overlaps with a UL symbol indicated by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* if provided. When a UE is configured by the higher layer parameter *repetitionScheme* set to 'tdmSchemeA', the PDSCH includes two PDSCH transmission occasions. For each PDSCH, if either PDSCH occasion overlaps with a UL symbol indicated by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* if provided, the PDSCH is not received and HARQ process ID is not incremented for the PDSCH. For any HARQ process ID(s) in a given scheduled cell, the UE is not expected to receive a PDSCH that overlaps in time with another PDSCH if the UE is not capable of receiving FD Med unicast and multicast PDSCH per slot per carrier. When HARQ feedback for the HARQ process ID is not disabled, or for the HARQ process associated with the first SPS PDSCH when *HARQ-feedbackEnablingforSPSactive* is provided and enabled, the UE is not expected to receive another PDSCH for a given HARQ process until after the end of the expected transmission of HARQ-ACK for that HARQ process, where the timing is given by Clause 9.2.3 of [6, TS 38.213]. For HARQ-ACK subject to HARQ-ACK deferral described in Clause 9.2.5.4 of [6, TS 38.213], the expected transmission of HARQ-ACK corresponds to the expected transmission HARQ-ACK in a first slot. When HARQ feedback for the HARQ process ID is disabled, the UE is not expected to receive another PDCCH carrying a DCI scheduling a PDSCH or set of slot-aggregated PDSCH scheduled for the given HARQ process or to receive another PDSCH without corresponding PDCCH for the given HARQ process that starts until $T_{proc,1}$ after the end of the reception of the last PDSCH or slot-aggregated PDSCH for that HARQ process. Except for the case when a UE is configured by higher layer parameter *PDCCH-Config* that contains two different values of *coresetPoolIndex* in *ControlResourceSet* and PDCCHs that schedule two PDSCHs are associated to different *ControlResourceSets* having different values of *coresetPoolIndex*, in a given scheduled cell, the UE is not expected to receive a first PDSCH and a second PDSCH, starting later than the first PDSCH, with its corresponding HARQ-ACK assigned to be transmitted on a resource ending before the start of a different resource for the HARQ-ACK assigned to be transmitted for the first PDSCH, where the two resources are in different slots for the associated HARQ-ACK transmissions, each slot is composed of $N_{sym}^{slot}$ symbols [4] or a number of symbols indicated by *subslotLengthForPUCCH* if provided, and the HARQ-ACK for the two PDSCHs are associated with the HARQ-ACK codebook of the same priority. Except for the case when a UE is configured by higher layer parameter *PDCCH-Config* that contains two different values of *coresetPoolIndex* in *ControlResourceSet* and PDCCHs that schedule two PDSCHs are associated to different *ControlResourceSets* having different values of *coresetPoolIndex*, in a given scheduled cell, the UE is not expected to receive a first PDSCH, and a second PDSCH, starting later than the first PDSCH, with its corresponding HARQ-ACK assigned to be transmitted on a resource ending before the start of a different resource for the HARQ-ACK assigned to be transmitted for the first PDSCH if the HARQ-ACK for the two PDSCHs are associated with HARQ-ACK codebooks of different priorities. For any two HARQ process IDs in a given scheduled cell, if the UE is scheduled to start receiving a first PDSCH starting in symbol $j$ by a PDCCH ending in symbol $i$ on a scheduling cell, the UE is not expected to be scheduled to receive a PDSCH starting earlier than the end of the first PDSCH with a PDCCH that ends later than symbol $i$ of a scheduling cell. When the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], the PDCCH ending in symbol $i$ is determined based on the PDCCH candidate that ends later in time. In a given scheduled cell, for any PDSCH corresponding to SI-RNTI, the UE is not expected to decode a re-transmission of an earlier PDSCH with a starting symbol less than $N$ symbols after the last symbol of that PDSCH, where the value of $N$ depends on the PDSCH subcarrier spacing configuration $\mu$ , with $N=13$ for $\mu=0$ , $N=13$ for $\mu=1$ , $N=20$ for $\mu=2$ , $N=24$ for $\mu=3$ , $N=96$ for $\mu=5$ , and $N=192$ for $\mu=6$ . + +When receiving PDSCH scheduled with SI-RNTI, P-RNTI, G-RNTI for broadcast, MCCH-RNTI, G-RNTI for multicast in RRC\_INACTIVE state or multicast-MCCH-RNTI, the UE may assume that the DM-RS port of PDSCH is quasi co-located with the associated SS/PBCH block with respect to Doppler shift, Doppler spread, average delay, delay spread, spatial RX parameters when applicable. + +When receiving PDSCH scheduled with RA-RNTI, or MSGRNTI, the UE may assume that the DM-RS port of PDSCH is quasi co-located with the SS/PBCH block or the CSI-RS resource the UE used for RACH association as applicable, and transmission with respect to Doppler shift, Doppler spread, average delay, delay spread, spatial RX parameters when applicable. When receiving a PDSCH scheduled with RA-RNTI in response to a random access procedure triggered by a PDCCH order which triggers contention-free random access procedure for the SpCell [10, TS 38.321], the UE may assume that the DM-RS port of the received PDCCH order and the DM-RS ports of the corresponding PDSCH scheduled with RA-RNTI are quasi co-located with the same SS/PBCH block or CSI-RS with respect to Doppler shift, Doppler spread, average delay, delay spread, spatial RX parameters when applicable. If a UE is configured with *SSB-MTC-AdditionalPCI* and with *PDCCH-Config* that contains two different values of *coresetPoolIndex* in *ControlResourceSet*, and if the UE is configured with [*twoTAGs*] for the SpCell, if the UE attempts to detect the DCI format 1\_0 with CRC scrambled by the corresponding RA-RNTI or when receiving a PDSCH scheduled with RA-RNTI in response to a random access procedure triggered by a PDCCH order which triggers contention-free random access procedure for the SpCell [10, TS 38.321], and if the CORESET used for the PDCCH + +order transmission is not associated with the serving cell physical cell ID, the UE may assume that the DM-RS ports of the received PDSCH are quasi co-located with the DM-RS antenna port associated with PDCCH receptions in the CORESET for Type1-PDCCH CSS set with respect to Doppler shift, Doppler spread, average delay, delay spread, and spatial RX parameters when applicable. + +When receiving PDSCH in response to a PUSCH transmission scheduled by a RAR UL grant or corresponding PUSCH retransmission, or when receiving PDSCH in response to a PUSCH for Type-2 random access procedure, or a PUSCH scheduled by a fallbackRAR UL grant or corresponding PUSCH retransmission, the UE may assume that the DM-RS port of PDSCH is quasi co-located with the SS/PBCH block the UE selected for RACH association and transmission with respect to Doppler shift, Doppler spread, average delay, delay spread, spatial RX parameters when applicable. + +If the UE is not configured for PUSCH/PUCCH transmission for at least one serving cell configured with slot formats comprised of DL and UL symbols, and if the UE is not capable of simultaneous reception and transmission on serving cell $c_1$ and serving cell $c_2$ , the UE is not expected to receive PDSCH on serving cell $c_1$ if the PDSCH overlaps in time with SRS transmission (including any interruption due to uplink or downlink RF retuning time [10]) on serving cell $c_2$ not configured for PUSCH/PUCCH transmission. + +The UE is not expected to decode a PDSCH in a serving cell scheduled by a PDCCH with C-RNTI, CS-RNTI, MCS-C-RNTI, G-RNTI, G-CS-RNTI or MCCH-RNTI and one or multiple PDSCH(s) required to be received according to this Clause in the same serving cell without a corresponding PDCCH transmission if the PDSCHs partially or fully overlap in time except if the PDCCH scheduling the PDSCH ends at least 14 symbols before the earliest starting symbol of the PDSCH(s) without the corresponding PDCCH transmission, where $\mu$ and the symbol duration are based on the smallest numerology between the scheduling PDCCH and the PDSCH, in which case the UE shall decode the PDSCH scheduled by the PDCCH. When the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10 of [6, TS 38.213], for the purpose of determining the PDCCH with C-RNTI, CS-RNTI or MCS-C-RNTI scheduling the PDSCH ends at least 14 symbols before the earliest starting symbol of the PDSCH(s) without the corresponding PDCCH transmission, the PDCCH candidate that ends later in time is used. + +The UE is not expected to decode a PDSCH scheduled with C-RNTI, MCS-C-RNTI, G-RNTI for multicast or broadcast, MCCH-RNTI, multicast-MCCH-RNTI, G-CS-RNTI or CS-RNTI if another PDSCH in the same cell scheduled with RA-RNTI or MSGB-RNTI partially or fully overlap in time. + +Furthermore, a UE indicating *supportOfRedCap-r18* capability but not indicating FG 48-2 is not expected to decode a PDSCH scheduled with C-RNTI, MCS-C-RNTI, G-RNTI for multicast or broadcast, MCCH-RNTI, multicast-MCCH-RNTI, G-CS-RNTI or CS-RNTI in the same or next slot if another PDSCH in the same cell is scheduled with RA-RNTI or MSGB-RNTI, when the PDSCH scheduled with RA-RNTI or MSGB-RNTI is allocated more than 25 PRBs when configured with SCS $\mu = 0$ or more than 12 PRBs when configured with SCS $\mu = 1$ . + +The UE in RRC\_IDLE and RRC\_INACTIVE modes shall be able to decode two PDSCHs each scheduled with SI-RNTI, P-RNTI, RA-RNTI or TC-RNTI, where the PDSCH scheduled with TC-RNTI for a reduced capability UE that indicates *supportOfRedCap-r18* is allocated no more than 25 PRBs when configured with SCS $\mu = 0$ or no more than 12 PRBs when configured with SCS $\mu = 1$ , with the two PDSCHs partially or fully overlapping in time in non-overlapping PRBs. + +The UE: + +- is expected to decode PDSCH scheduled with MCCH-RNTI or multicast-MCCH-RNTI, and PBCH in PCell that partially or fully overlaps in time in non-overlapping PRBs in PCell. +- is not expected to decode PDSCH scheduled with G-RNTI for broadcast and PBCH in PCell that partially or fully overlaps in time in non-overlapping PRBs in PCell. +- is not expected to decode PDSCH scheduled with G-RNTI for multicast and PBCH in PCell that partially or fully overlaps in time in non-overlapping PRBs in PCell. + +On a frequency range 1 cell, the UE shall be able to decode a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI and, during a process of P-RNTI triggered SI acquisition, another PDSCH scheduled with SI-RNTI that partially or fully overlap in time in non-overlapping PRBs, unless the PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI requires Capability 2 processing time according to clause 5.3 in which case the UE may skip decoding of the scheduled PDSCH with C-RNTI, MCS-C-RNTI, or CS-RNTI. + +On a frequency range 2 cell, the UE is not expected to decode a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI if in the same cell, during a process of P-RNTI triggered SI acquisition, another PDSCH scheduled with SI-RNTI partially or fully overlap in time. + +A UE that indicates *supportOfRedCap-r18* capability but does not indicate FG 48-2, during a process of P-RNTI triggered SI acquisition, when the total number of PRBs for the PDSCH scheduled with SI-RNTI and the PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI scheduled in the slot is larger than 25 PRBs if configured with SCS $\mu = 0$ or larger than 12 PRBs if configured with SCS $\mu = 1$ , the UE may skip decoding of the scheduled PDSCH with C-RNTI, MCS-C-RNTI, or CS-RNTI. + +The UE is expected to decode a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI during a process of autonomous SI acquisition. + +The maximum number of PDSCHs scheduled per slot per component carrier with C-RNTI/CS-RNTI and G-RNTI/G-CS-RNTI/MCCH-RNTI/multicast-MCCH-RNTI that the UE shall be able to decode is the same as the indicated UE capability for the number of unicast PDSCHs per slot per component carrier. If the UE is capable of receiving FDMeD unicast and multicast PDSCH per slot per carrier, the UE shall be able to decode a PDSCH scheduled by a DCI format with C-RNTI or a PDSCH scheduled for a retransmission of a TB by a DCI format with CS-RNTI and a PDSCH scheduled by a DCI format with G-RNTI for multicast or a PDSCH scheduled for a retransmission of a TB by a DCI format with G-CS-RNTI or a PDSCH scheduled by a DCI format with multicast-MCCH-RNTI that partially or fully overlap in time in non-overlapping PRBs. If the UE is capable of receiving FDMeD unicast and broadcast PDSCH per slot per carrier, the UE shall be able to decode a PDSCH scheduled by a DCI format with C-RNTI or a PDSCH scheduled for a retransmission of a TB by a DCI format with CS-RNTI and a PDSCH scheduled with G-RNTI for broadcast/MCCH-RNTI that partially or fully overlap in time in non-overlapping PRBs. For a reduced capability UE that indicates *supportOfRedCap-r18* but not indicating FG 48-2, if the UE is capable of receiving FDMeD unicast and multicast/broadcast PDSCH per slot, the UE can decode the two PDSCHs, with the two PDSCHs partially or fully overlapping in time in non-overlapping PRBs, + +- if the total number of PRBs allocated is no more than 25 PRBs when configured with SCS $\mu = 0$ or no more than 12 PRBs when configured with SCS $\mu = 1$ , +- otherwise, the UE may skip decoding one of the two PDSCHs. + +If the UE is configured by higher layers to decode a PDCCH with its CRC scrambled by a CS-RNTI or G-CS-RNTI, the UE shall receive PDSCH transmissions without corresponding PDCCH transmissions using the higher-layer-provided PDSCH configuration for those PDSCHs. + +The UE is not expected to support reception of: + +- FDMeD broadcast MCCH PDSCH and broadcast MTCH PDSCH in PCell or SCell, or +- FDMeD multiple broadcast MTCH PDSCHs in PCell or SCell, or +- FDMeD broadcast MCCH/broadcast MTCH/multicast PDSCH and SIB PDSCH in PCell, or +- FDMeD multicast PDSCHs in PCell or SCell, or +- FDMeD multicast PDSCH and MCCH/broadcast MTCH PDSCH in PCell or SCell, or +- FDMeD broadcast MCCH/broadcast MTCH/multicast PDSCH and paging PDSCH. + +The UE in RRC\_INACTIVE state is not expected to support reception of: + +- FDMeD multicast MCCH PDSCH and multicast MTCH PDSCH in Pcell, or +- FDMeD multiple multicast MTCH PDSCHs in Pcell, or +- FDMeD broadcast MCCH/broadcast MTCH/multicast MCCH/multicast MTCH and SIB PDSCH in Pcell, or +- FDMeD multicast MCCH/multicast MTCH and broadcast MCCH/broadcast MTCH in Pcell, or +- FDMeD multicast MCCH/multicast MTCH and paging PDSCH in Pcell. + +If a UE is configured by higher layer parameter *PDCCH-Config* that contains two different values of *coresetPoolIndex* in *ControlResourceSet*, the UE may expect to receive multiple PDCCHs scheduling fully/partially/non-overlapped PDSCHs in time and frequency domain. The UE may expect the reception of full/partially-overlapped PDSCHs in time, only when PDCCHs that schedule two PDSCHs are associated to different *ControlResourceSets* having different values of *coresetPoolIndex*. For a *ControlResourceSet* without *coresetPoolIndex*, the UE may assume that the *ControlResourceSet* is assigned with *coresetPoolIndex* as 0. When the UE is configured with *SSB-MTC-AdditionalPCI*, + +*ControlResourceSets* corresponding to different *coresetPoolIndex* values may be associated with different physical cell IDs via activated TCI states of the *ControlResourceSets*, where *ControlResourceSets* corresponding to one *coresetPoolIndex* is associated with the serving cell physical cell ID and *ControlResourceSets* corresponding to another *coresetPoolIndex* can be associated with another physical cell ID. When the UE is scheduled with full/partially/non-overlapped PDSCHs in time and frequency domain, the full scheduling information for receiving a PDSCH is indicated and carried only by the corresponding PDCCH, the UE is expected to be scheduled with the same active BWP and the same SCS. When the UE is scheduled with full/partially-overlapped PDSCHs in time and frequency domain, the UE can be scheduled with at most two codewords simultaneously. When PDCCHs that schedule two PDSCHs are associated to different *ControlResourceSets* having different values of *coresetPoolIndex*, the following operations are allowed: + +- For any two HARQ process IDs in a given scheduled cell, if the UE is scheduled to start receiving a first PDSCH starting in symbol *j* by a PDCCH associated with a value of *coresetPoolIndex* ending in symbol *i*, the UE can be scheduled to receive a PDSCH starting earlier than the end of the first PDSCH with a PDCCH associated with a different value of *coresetPoolIndex* that ends later than symbol *i*. +- In a given scheduled cell, the UE can receive a first PDSCH in slot *i*, with the corresponding HARQ-ACK assigned to be transmitted in slot *j*, and a second PDSCH associated with a value of *coresetPoolIndex* different from that of the first PDSCH starting later than the first PDSCH with its corresponding HARQ-ACK assigned to be transmitted in a slot before slot *j*. + +If PDCCHs that schedule corresponding PDSCHs are associated to the same or different *ControlResourceSets* having the same value of *coresetPoolIndex*, the UE procedure for receiving the PDSCH upon detection of a PDCCH follows Clause 5.1. + +A UE does not expect to be configured with *repetitionScheme* if the UE is configured with higher layer parameter *repetitionNumber* for the same PDSCH. + +When a UE is configured by higher layer parameter *repetitionScheme* set to one of 'fdmSchemeA', 'fdmSchemeB', 'tdmSchemeA', if the UE not configured with *dl-OrJointTCI-StateList* is indicated with two TCI states in a codepoint of the DCI field '*Transmission Configuration Indication*' or if the UE configured with *dl-OrJointTCI-StateList* is having two indicated TCI States to be applied to PDSCH and the UE is indicated with DM-RS port(s) within one CDM group in the DCI field '*Antenna Port(s)*'. + +- When the UE is set to 'fdmSchemeA', the UE shall receive a single PDSCH transmission occasion of the TB with each TCI state associated to a non-overlapping frequency domain resource allocation as described in Clause 5.1.2.3. +- When the UE is set to 'fdmSchemeB', the UE shall receive two PDSCH transmission occasions of the same TB with each TCI state associated to a PDSCH transmission occasion which has non-overlapping frequency domain resource allocation with respect to the other PDSCH transmission occasion as described in Clause 5.1.2.3. +- When the UE is set to 'tdmSchemeA', the UE shall receive two PDSCH transmission occasions of the same TB with each TCI state associated to a PDSCH transmission occasion which has non-overlapping time domain resource allocation with respect to the other PDSCH transmission occasion and both PDSCH transmission occasions shall be received within a given slot as described in Clause 5.1.2.1. + +When a UE is configured by the higher layer parameter *repetitionNumber* in *PDSCH-TimeDomainResourceAllocation*, the UE not configured with *dl-OrJointTCI-StateList* may expect to be indicated with one or two TCI states in a codepoint of the DCI field '*Transmission Configuration Indication*' or when the UE configured with *dl-OrJointTCI-StateList* may expect to apply one or two indicated TCI states to the PDSCH, together with the DCI field '*Time domain resource assignment*' indicating an entry which contains *repetitionNumber* in *PDSCH-TimeDomainResourceAllocation* and DM-RS port(s) within one CDM group in the DCI field '*Antenna Port(s)*'. + +- When two TCI states are indicated in a DCI with '*Transmission Configuration Indication*' field for the UE not configured with *dl-OrJointTCI-StateList*, or when the UE configured with *dl-OrJointTCI-StateList* is having two indicated TCI States to be applied to PDSCH, the UE may expect to receive multiple slot level PDSCH transmission occasions of the same TB with two TCI states used across multiple PDSCH transmission occasions in the *repetitionNumber* consecutive slots as defined in Clause 5.1.2.1. +- When one TCI state is indicated in a DCI with '*Transmission Configuration Indication*' field for the UE not configured with *dl-OrJointTCI-StateList*, or when the UE configured with *dl-OrJointTCI-StateList* is having one indicated TCI states to be applied to PDSCH, the UE may expect to receive multiple slot level PDSCH + +transmission occasions of the same TB with one TCI state used across multiple PDSCH transmission occasions in the *repetitionNumber* consecutive slots as defined in Clause 5.1.2.1. + +When a UE is not indicated with a DCI that DCI field '*Time domain resource assignment*' indicating an entry which contains *repetitionNumber* in *PDSCH-TimeDomainResourceAllocation*, and it is indicated with two TCI states in a codepoint of the DCI field '*Transmission Configuration Indication*' for the UE not configured with *dl-OrJointTCI-StateList*, or when the UE configured with *dl-OrJointTCI-StateList* is having two indicated TCI States to be applied to PDSCH, and is indicated with DM-RS port(s) within two CDM groups in the DCI field '*Antenna Port(s)*' and it is not configured with higher layer parameter *sfnSchemePDSCH*, the UE may expect to receive a single PDSCH where the association between the DM-RS ports and the TCI states are as defined in Clause 5.1.6.2. + +When a UE is not indicated with a DCI that DCI field '*Time domain resource assignment*' indicating an entry which contains *repetitionNumber* in *PDSCH-TimeDomainResourceAllocation*, and it is not configured with *dl-OrJointTCI-StateList* and is indicated with one TCI states in a codepoint of the DCI field '*Transmission Configuration Indication*', or it is configured with *dl-OrJointTCI-StateList* and is expected to apply one indicated TCI states to PDSCH, the UE procedure for receiving the PDSCH upon detection of a PDCCH follows Clause 5.1. + +When a UE is configured with higher layer parameter *sfnSchemePDSCH* set to either 'sfnSchemeA' or 'sfnSchemeB' and + +- if the UE reports its capability of *sfnSchemeA-DynamicSwitching* or *sfnSchemeB-DynamicSwitching*, the UE not configured with *dl-OrJointTCI-StateList* is indicated with one or two TCI state(s) in a codepoint of the DCI field '*Transmission Configuration Indication*' in DCI format 1\_1/1\_2, or the UE configured with *dl-OrJointTCI-StateList* is having one or two indicated TCI States to be applied to PDSCH +- otherwise, the UE not configured with *dl-OrJointTCI-StateList* is not expected to be indicated with one TCI state per any of TCI codepoint by MAC CE, and the UE is indicated with two TCI states in a codepoint of the DCI field '*Transmission Configuration Indication*' in DCI format 1\_1/1\_2, or the UE configured with *dl-OrJointTCI-StateList* is having two indicated TCI States to be applied to PDSCH + +the UE procedure for receiving the PDSCH upon detection of a PDCCH follows clause 5.1 and the QCL assumption for the PDSCH as defined in clause 5.1.5. + +When a UE is configured with both *sfnSchemePDSCH* and *sfnSchemePDCCH*, the UE shall expect that *sfnSchemePDSCH* and *sfnSchemePDCCH* are set to the same scheme, either 'sfnSchemeA' or 'sfnSchemeB'. + +If a UE not configured with *dl-OrJointTCI-StateList* is configured with *sfnSchemePDCCH* set to 'sfnSchemeA' and activated with two TCI states by MAC CE, and the UE does not report its capability of *sfnSchemeA-PDCCH-only*, the UE is expected to be configured with *sfnSchemePDSCH* set to 'sfnSchemeA' and indicated with two TCI states in a codepoint of the DCI field '*Transmission Configuration Indication*', if the PDSCH is scheduled by DCI format 1\_1/1\_2. + +If a UE configured with *dl-OrJointTCI-StateList* and having two indicated TCI-States is configured with *sfnSchemePdcch* set to 'sfnSchemeA' for a DL BWP and signaled by the higher layer parameter [*applyIndicatedTCIState*] to apply both indicated TCI-States to a PDCCH on a CORESET, and the UE does not report its capability of *sfnSchemeA-PDCCH-only*, the UE is expected to be configured with *sfnSchemePdsch* set to 'sfnSchemeA' and both indicated TCI-States are applicable to PDSCH, if the PDSCH is scheduled by DCI format 1\_1/1\_2 on the PDCCH. + +If a UE not configured with *dl-OrJointTCI-StateList* is configured with *sfnSchemePDCCH* set to 'sfnSchemeB' and activated with two TCI states by MAC CE, the UE is expected to be configured with *sfnSchemePDSCH* set to 'sfnSchemeB' and indicated with two TCI states in a codepoint of the DCI field '*Transmission Configuration Indication*', if the PDSCH is scheduled by DCI format 1\_1/1\_2. + +If a UE configured with *dl-OrJointTCI-StateList* and having two indicated TCI-States is configured with *sfnSchemePdcch* set to 'sfnSchemeB' for a DL BWP, and signaled by the higher layer parameter [*applyIndicatedTCIState*] to apply both indicated TCI-States to a PDCCH on a CORESET, the UE is expected to be configured with *sfnSchemePdsch* set to 'sfnSchemeB' and both indicated TCI-States are applicable to PDSCH, if the PDSCH is scheduled by DCI format 1\_1/1\_2 on the PDCCH. + +When a UE is configured with *sfnSchemePDSCH* and/or *sfnSchemePDCCH*, the UE shall expect that the *sfnSchemePDSCH* and/or *sfnSchemePDCCH* configuration are the same within a CC, and the UE shall expect that the *sfnSchemePDSCH* and/or *sfnSchemePDCCH* configuration are the same in all CCs in a same frequency band if the UE is configured with CA, where the UE does not expect to be configured with *sfnSchemePDSCH* and/or *sfnSchemePDCCH* in initial BWP in each CC. + +If more than one PDSCH on a serving cell each without a corresponding PDCCH transmission are in a slot, after resolving overlapping with symbols in the slot indicated as uplink by *tdd-UL-DL-ConfigurationCommon*, or by *tdd-UL-DL-ConfigurationDedicated*, a UE receives one or more PDSCHs without corresponding PDCCH transmissions in the slot as specified below. + +- Step 0: set $j=0$ , where $j$ is the number of selected PDSCH(s) for decoding. $Q$ is the set of activated PDSCHs without corresponding PDCCH transmissions within the slot +- Step 1: A UE receives one PDSCH with the lowest configured *sps-ConfigIndex* within $Q$ , set $j=j+1$ . Designate the received PDSCH as survivor PDSCH. +- Step 2: The survivor PDSCH in step 1 and any other PDSCH(s) overlapping (even partially) with the survivor PDSCH in step 1 are excluded from $Q$ . +- Step 3: Repeat step 1 and 2 until $Q$ is empty or $j$ is equal to the number of unicast/multicast PDSCHs in a slot supported by the UE. + +For a cell detected in cell search procedure with synchronization raster defined in Table 5.4.3.1-2 or Table 5.4.3.1-3 of [8, TS 38.101-1], the size of CORESET 0 for the cell in this clause refers to the size of punctured CORESET 0 as defined in clause 7.3.2.2 of [4, TS 38.211] if any. + +### 5.1.1 Transmission schemes + +Only one transmission scheme is defined for the PDSCH, and is used for all PDSCH transmissions. + +#### 5.1.1.1 Transmission scheme 1 + +For transmission scheme 1 of the PDSCH, the UE may assume that a gNB transmission on the PDSCH would be performed with up to 8 transmission layers on antenna ports 1000-1023 as defined in Clause 7.3.1.4 of [4, TS 38.211], subject to the DM-RS reception procedures in Clause 5.1.6.2. + +### 5.1.2 Resource allocation + +#### 5.1.2.1 Resource allocation in time domain + +When the UE is scheduled to receive PDSCH by a DCI, the *Time domain resource assignment* field value $m$ for the scheduled PDSCH on the serving cell provides a row index $m + 1$ to a resource allocation table. The determination of the used resource allocation table is defined in Clause 5.1.2.1.1. The indexed row defines the slot offset $K_0$ , the start and length indicator *SLIV*, or directly the start symbol $S$ and the allocation length $L$ , and the PDSCH mapping type to be assumed in the PDSCH reception. + +Given the parameter values of the indexed row: + +- The slot allocated for the PDSCH is $K_s$ , where + +$$K_s = \left\lceil n \cdot \frac{2^{\mu_{\text{PDSCH}}}}{2^{\mu_{\text{PDCCH}}}} \right\rceil + K_0 + \left\lceil \left( \frac{N_{\text{slot,offset,PDCCH}}^{\text{CA}}}{2^{\mu_{\text{offset,PDCCH}}}} - \frac{N_{\text{slot,offset,PDSCH}}^{\text{CA}}}{2^{\mu_{\text{offset,PDSCH}}}} \right) \cdot 2^{\mu_{\text{PDSCH}}} \right\rceil, \text{ if UE is configured with } ca\text{-SlotOffset for at least one of the scheduled and scheduling cell, and } K_s = \left\lceil n \cdot \frac{2^{\mu_{\text{PDSCH}}}}{2^{\mu_{\text{PDCCH}}}} \right\rceil + K_0, \text{ otherwise, and}$$ + +where $n$ is the slot with the scheduling DCI, and $K_0$ is based on the numerology of PDSCH, and $\mu_{\text{PDSCH}}$ and $\mu_{\text{PDCCH}}$ are the subcarrier spacing configurations for PDSCH and PDCCH, respectively, and + +- and are the and the $\mu_{\text{offset}}$ , respectively, which are determined by higher-layer configured *ca-SlotOffset*, for the cell receiving the PDCCH respectively, and are the and the $\mu_{\text{offset}}$ , respectively, which are determined by higher-layer configured *ca-SlotOffset* for the cell receiving the PDSCH, as defined in clause 4.5 of [4, TS 38.211]. +- The reference point $S_0$ for starting symbol $S$ is defined as: + +- if configured with *referenceOfSLIVDCI-1-2*, and when receiving PDSCH scheduled by DCI format 1\_2 with CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI with $K_0=0$ , and PDSCH mapping Type B, the starting symbol $S$ is relative to the starting symbol $S_0$ of the PDCCH monitoring occasion where DCI format 1\_2 is detected; when the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], the PDCCH candidate that starts later in time is used for the purpose of determining the starting symbol $S_0$ ; +- otherwise, the starting symbol $S$ is relative to the start of the slot using $S_0=0$ . +- The number of consecutive symbols $L$ counting from the starting symbol $S$ allocated for the PDSCH are determined from the start and length indicator *SLIV*: + +if then + +else + +where $0 < L \leq 14 - S$ , and + +- the PDSCH mapping type is set to Type A or Type B as defined in Clause 7.4.1.1.2 of [4, TS 38.211]. + +The UE shall consider the $S$ and $L$ combinations defined in table 5.1.2.1-1 satisfying $S_0 + S + L \leq 14$ for normal cyclic prefix and $S_0 + S + L \leq 12$ for extended cyclic prefix as valid PDSCH allocations: + +**Table 5.1.2.1-1: Valid $S$ and $L$ combinations** + +| PDSCH mapping type | Normal cyclic prefix | | | Extended cyclic prefix | | | +|----------------------------------------------------------------------|-----------------------|------------|------------|------------------------|------------|------------| +| | $S$ | $L$ | $S+L$ | $S$ | $L$ | $S+L$ | +| Type A | {0,1,2,3}
(Note 1) | {3,...,14} | {3,...,14} | {0,1,2,3}
(Note 1) | {3,...,12} | {3,...,12} | +| Type B | {0,...,12} | {2,...,13} | {2,...,14} | {0,...,10} | {2,4,6} | {2,...,12} | +| Note 1: $S = 3$ is applicable only if dmrs-TypeA-Position = 3 | | | | | | | + +When configured with SCS $\mu = 5$ or $\mu = 6$ , the UE does not expect to be scheduled with more than one unicast PDSCH in a slot, by a single DCI scheduling multiple PDSCHs or by multiple DCIs, where multiple DCIs are not associated with CORESETs having different *coresetpoolIndex*. + +When receiving PDSCH scheduled by DCI format 1\_1, 1\_2 or 1\_3 in PDCCH with CRC scrambled by C-RNTI, MCS-C-RNTI, or scheduled by DCI format 1\_1 or 1\_2 in PDCCH with CRC scrambled by CS-RNTI with NDI=1, if the UE is configured with *pdsch-AggregationFactor* in *pdsch-config*, the same symbol allocation is applied across the *pdsch-AggregationFactor* consecutive slots. When receiving PDSCH scheduled by DCI format 1\_1 or 1\_2 in PDCCH with CRC scrambled by CS-RNTI with NDI=0, or PDSCH scheduled without corresponding PDCCH transmission using *sps-Config* and activated by DCI format 1\_1 or 1\_2, the same symbol allocation is applied across the *pdsch-AggregationFactor*, in *sps-Config* if configured, or across the *pdsch-AggregationFactor* in *pdsch-config* otherwise, consecutive slots. The UE may expect that the TB is repeated within each symbol allocation among each of the *pdsch-AggregationFactor* consecutive slots and the PDSCH is limited to a single transmission layer. For PDSCH scheduled by DCI format 1\_1 or 1\_2 in PDCCH with CRC scrambled by CS-RNTI with NDI=0, or PDSCH scheduled without corresponding PDCCH transmission using *sps-Config* and activated by DCI format 1\_1 or 1\_2, the UE is not expected to be configured with the time duration for the reception of *pdsch-AggregationFactor* repetitions, in *sps-Config* if configured, or across the *pdsch-AggregationFactor* in *pdsch-config* otherwise, larger than the time duration derived by the periodicity $P$ obtained from the corresponding *sps-Config*. The redundancy version to be applied on the $n^{\text{th}}$ transmission occasion of the TB, where $n = 0, 1, \dots, pdsch-AggregationFactor - 1$ , is determined according to table 5.1.2.1-2 and "*rv\_id* indicated by the DCI scheduling the PDSCH" in table 5.1.2.1-2 is assumed to be 0 for PDSCH scheduled without corresponding PDCCH transmission using *sps-Config* and activated by DCI format 1\_1 or 1\_2. + +When receiving PDSCH scheduled by DCI format 4\_1, or 4\_2 in PDCCH with CRC scrambled by G-RNTI for multicast, if the UE is configured with *pdsch-AggregationFactor* in the *MBS-RNTI-SpecificConfig* associated with the corresponding G-RNTI for multicast, the same symbol allocation is applied across the *pdsch-AggregationFactor* consecutive slots. When receiving PDSCH scheduled by DCI format 4\_1 or 4\_2 for multicast reception in PDCCH with + +CRC scrambled by G-CS-RNTI, or PDSCH without corresponding PDCCH transmission using associated *SPS-Config* and activated by the DCI format 4\_1 or 4\_2 in PDCCH with CRC scrambled by G-CS-RNTI, the same symbol allocation is applied across the *pdsch-AggregationFactor* in associated *SPS-Config* if configured, or across *repetitionNumber* in *PDSCH-TimeDomainResourceAllocation* in *pdsch-ConfigMulticast* if provided by an entry indicated by the 'Time domain resource assignment' field of the activating DCI, or 1 otherwise, consecutive slots. The redundancy version to be applied on the *n*th transmission occasion of the TB, where *n* = 0, 1, ... *pdsch-AggregationFactor* - 1, is determined according to table 5.1.2.1-2 and "rvid indicated by the DCI scheduling the PDSCH" in table 5.1.2.1-2 is assumed to be 0 for PDSCH scheduled without corresponding PDCCH transmission using *SPS-Config* and activated by DCI format 4\_1 or 4\_2. When receiving PDSCH scheduled by DCI format 4\_1 in PDCCH with CRC scrambled by G-RNTI for multicast in RRC\_INACTIVE state, if the UE is configured with *pdsch-AggregationFactor* in the *PDSCH-ConfigPTM-r18* for multicast in RRC\_INACTIVE state, the same symbol allocation is applied across the *pdsch-AggregationFactor* consecutive slots, and the redundancy version to be applied on the *n*th transmission occasion of the TB, where *n* = 0, 1, ... *pdsch-AggregationFactor* - 1, is determined according to table 5.1.2.1-2. When receiving PDSCH scheduled by DCI format 4\_0 in PDCCH with CRC scrambled by G-RNTI for broadcast, if the UE is configured with *pdsch-AggregationFactor* in the *PDSCH-ConfigPTM*, the same symbol allocation is applied across the *pdsch-AggregationFactor* consecutive slots, and the redundancy version to be applied on the *n*th transmission occasion of the TB, where *n* = 0, 1, ... *pdsch-AggregationFactor* - 1, is determined according to table 5.1.2.1-2. + +When receiving PDSCH scheduled by DCI in PDCCH with CRC scrambled by G-CS-RNTI for multicast reception or G-RNTI, if the DCI field 'Time domain resource assignment' indicates an entry which contains *repetitionNumber* in *PDSCH-TimeDomainResourceAllocation* in the *pdsch-ConfigMulticast*, or *pdsch-Config-MTCH*, or *PDSCH-Config-Broadcast*, the same SLIV is applied for all PDSCH transmission occasions across the *repetitionNumber* consecutive slots. When receiving PDSCH scheduled without corresponding PDCCH transmission using associated *SPS-Config* and activated by DCI in PDCCH with CRC scrambled by G-CS-RNTI for multicast reception, if the DCI field 'Time domain resource assignment' of the activating DCI indicates an entry which contains *repetitionNumber* in *PDSCH-TimeDomainResourceAllocation* in the *pdsch-ConfigMulticast*, the same SLIV is applied for all PDSCH transmission occasions across the *repetitionNumber* consecutive slots. The redundancy version to be applied on the *n*th transmission occasion of the TB, where *n* = 0, 1, ... *repetitionNumber* - 1, is determined according to table 5.1.2.1-2 and "rvid indicated by the DCI scheduling the PDSCH" in table 5.1.2.1-2 is assumed to be 0 for PDSCH scheduled without corresponding PDCCH transmission using *sps-Config* and activated by DCI format with CRC scrambled by G-CS-RNTI. + +If a UE is configured with higher layer parameter *repetitionNumber* or if the UE is configured by *repetitionScheme* set to one of 'fdmSchemeA', 'fdmSchemeB' and 'tdmSchemeA', the UE does not expect to be configured with *pdsch-AggregationFactor* for the same PDSCH. + +If a UE is configured with *pdsch-TimeDomainAllocationListForMultiPDSCH* in which one or more rows contain multiple SLIVs for PDSCH, the UE does not expect to be configured with higher layer parameter *repetitionNumber* in *pdsch-TimeDomainAllocationListForMultiPDSCH*. + +If a UE is configured with *pdsch-TimeDomainAllocationListForMultiPDSCH* in which one or more rows contain multiple SLIVs for PDSCH on a DL BWP of a serving cell, the UE does not apply *pdsch-AggregationFactor* in *PDSCH-config*, if configured, to DCI format 1\_1 on the DL BWP of the serving cell. + +If a UE is configured with *pdsch-TimeDomainAllocationListForMultiPDSCH* in which one or more rows contain multiple SLIVs for PDSCH on a DL BWP of a serving cell, when any two DL DCIs end in the same symbol and at least one of the DCIs schedules multiple PDSCHs, the UE does not expect that the scheduled PDSCH(s) by the two DCIs have overlapping spans, where the span associated with a DCI is defined from the beginning of the first scheduled PDSCH or up to the end of the last scheduled PDSCH. + +If a UE is configured with *pdsch-TimeDomainAllocationListForMultiPDSCH* in which one or more rows contain multiple SLIVs for PDSCH on a DL BWP of a serving cell within a PUCCH group, the UE does not expect to be configured with higher layer parameter *ScheduledCell-ListDCI-1-3* on any serving cell within the PUCCH group. + +**Table 5.1.2.1-2: Applied redundancy version when *pdsch-AggregationFactor* or *repetitionNumber* is present** + +| rvid indicated by the DCI scheduling the PDSCH | rvid to be applied to n th transmission occasion | | | | +|------------------------------------------------------------------|--------------------------------------------------------------------------------------|--------------------|--------------------|--------------------| +| | n mod 4 = 0 | n mod 4 = 1 | n mod 4 = 2 | n mod 4 = 3 | +| 0 | 0 | 2 | 3 | 1 | +| 2 | 2 | 3 | 1 | 0 | +| 3 | 3 | 1 | 0 | 2 | +| 1 | 1 | 0 | 2 | 3 | + +A PDSCH reception in a slot of a multi-slot PDSCH reception is omitted according to the conditions in clause 11.1 and clause 17.2 of [6, TS38.213]. + +The UE is not expected to receive a PDSCH with mapping type A in a slot, if the PDCCH scheduling the PDSCH was received in the same slot and was not contained within the first three symbols of the slot. When the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], if the two PDCCH candidates scheduling the PDSCH with mapping Type A were received in the same slot as the PDSCH, both PDCCH candidates are expected to be contained within the first three symbols of the slot. + +The UE is not expected to receive a PDSCH with mapping type B in a slot, if the first symbol of the PDCCH scheduling the PDSCH was received in a later symbol than the first symbol indicated in the PDSCH time domain resource allocation. When the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], the UE is not expected to receive a PDSCH with mapping type B in a slot, if the first symbol of the PDCCH candidate that starts later in time scheduling the PDSCH was received in a later symbol than the first symbol indicated in the PDSCH time domain resource allocation. + +When the UE is configured with *minimumSchedulingOffsetK0* in an active DL BWP it applies a minimum scheduling offset restriction indicated by the 'Minimum applicable scheduling offset indicator' field in DCI format 0\_1, 0\_3, 1\_1 or 1\_3, if the same field is available. When the UE is configured with *minimumSchedulingOffsetK0* in an active DL BWP and it has not received 'Minimum applicable scheduling offset indicator' field in DCI format 0\_1, 0\_3, 1\_1 or 1\_3, the UE shall apply a minimum scheduling offset restriction indicated based on 'Minimum applicable scheduling offset indicator' value '0'. When the minimum scheduling offset restriction is applied the UE is not expected to be scheduled with a DCI in slot *n* to receive a PDSCH scheduled with C-RNTI, CS-RNTI or MCS-C-RNTI with *K0* smaller than *K0min*, where *K0min* and *n* are the applied minimum scheduling offset restriction and the numerology of the active DL BWP of the scheduled cell when receiving the DCI in slot *n*, respectively, and *n* is the numerology of the new active DL BWP in case of active DL BWP change in the scheduled cell and is equal to *n*, otherwise. The minimum scheduling offset restriction is not applied when PDSCH transmission is scheduled with C-RNTI, CS-RNTI or MCS-C-RNTI in common search space associated with CORESET0 and default PDSCH time domain resource allocation is used, in the search space set provided by *recoverySearchSpaceId* when monitoring PDCCH as described in [6, TS 38.213] or when PDSCH transmission is scheduled with SI-RNTI, MSGB-RNTI or RA-RNTI. The application delay of the change of the minimum scheduling offset restriction is determined in Clause 5.3.1. + +The UE is not expected to be configured with *referenceOfSLIVDCI-1-2* for serving cells configured for cross-carrier scheduling with a scheduling cell of a different downlink SCS configuration. + +When a UE is configured by the higher layer parameter *repetitionScheme* set to 'tdmSchemeA' and indicated DM-RS port(s) within one CDM group in the DCI field 'Antenna Port(s)', the number of PDSCH transmission occasions is derived by the number of TCI states indicated by the DCI field 'Transmission Configuration Indication' of the scheduling DCI for the UE not configured with *dl-OrJointTCI-StateList*, or by the number of indicated TCI states when the UE configured with *dl-OrJointTCI-StateList*. + +- If two TCI states are indicated by the DCI field 'Transmission Configuration Indication' for a UE not configured with *dl-OrJointTCI-StateList*, or both indicated TCI states applicable to PDSCH for a UE configured with *dl-OrJointTCI-StateList*, the UE is expected to receive two PDSCH transmission occasions, where the first TCI state is applied to the first PDSCH transmission occasion and resource allocation in time domain for the first PDSCH transmission occasion follows Clause 5.1.2.1. The second TCI state is applied to the second PDSCH transmission occasion, and the second PDSCH transmission occasion shall have the same number of symbols as the first PDSCH transmission occasion. If the UE is configured by the higher layers with a value in *StartingSymbolOffsetK*, it shall determine that the first symbol of the second PDSCH transmission occasion starts after *StartingSymbolOffsetK* symbols from the last symbol of the first PDSCH transmission occasion. If the value is not configured via the higher layer parameter *StartingSymbolOffsetK*, *StartingSymbolOffsetK* = 0 shall be assumed by the UE. The UE is + +not expected to receive more than two PDSCH transmission layers for each PDSCH transmission occasion. For two PDSCH transmission occasions, the redundancy version to be applied is derived according to Table 5.1.2.1-2, where applied respectively to the first and second TCI state. The UE expects the PDSCH mapping type indicated by DCI field 'Time domain resource assignment' to be mapping type B, and the indicated PDSCH mapping type is applied to both PDSCH transmission occasions. + +- Otherwise, the UE is expected to receive a single PDSCH transmission occasion, and the resource allocation in the time domain follows Clause 5.1.2.1. + +When a UE configured by the higher layer parameter *PDSCH-config* that indicates at least one entry contains *repetitionNumber* in *PDSCH-TimeDomainResourceAllocation*, + +- If two TCI states are indicated by the DCI field 'Transmission Configuration Indication' for a UE not configured with *dl-OrJointTCI-StateList*, or both indicated TCI states applicable to PDSCH for a UE configured with *dl-OrJointTCI-StateList*, together with the DCI field 'Time domain resource assignment' indicating an entry which contains *repetitionNumber* in *PDSCH-TimeDomainResourceAllocation* and DM-RS port(s) within one CDM group in the DCI field 'Antenna Port(s)', the same SLIV is applied for all PDSCH transmission occasions across the *repetitionNumber* consecutive slots, the first TCI state is applied to the first PDSCH transmission occasion and resource allocation in time domain for the first PDSCH transmission occasion follows Clause 5.1.2.1. + +When the value indicated by *repetitionNumber* in *PDSCH-TimeDomainResourceAllocation* equals to two, the second TCI state is applied to the second PDSCH transmission occasion. When the value indicated by *repetitionNumber* in *PDSCH-TimeDomainResourceAllocation* is larger than two, the UE may be further configured to enable *cyclicMapping* or *sequentialMapping* in *tcMapping*. + +- When *cyclicMapping* is enabled, the first and second TCI states are applied to the first and second PDSCH transmission occasions, respectively, and the same TCI mapping pattern continues to the remaining PDSCH transmission occasions. +- When *sequentialMapping* is enabled, first TCI state is applied to the first and second PDSCH transmission occasions, and the second TCI state is applied to the third and fourth PDSCH transmission occasions, and the same TCI mapping pattern continues to the remaining PDSCH transmission occasions. + +The UE may expect that each PDSCH transmission occasion is limited to two transmission layers. For all PDSCH transmission occasions associated with the first TCI state, the redundancy version to be applied is derived according to Table 5.1.2.1-2, where is counted only considering PDSCH transmission occasions associated with the first TCI state. The redundancy version for PDSCH transmission occasions associated with the second TCI state is derived according to Table 5.1.2.1-3, where additional shifting operation for each redundancy version is configured by higher layer parameter *sequenceOffsetforRV* and is counted only considering PDSCH transmission occasions associated with the second TCI state. + +**Table 5.1.2.1-3: Applied redundancy version for the second TCI state when *sequenceOffsetforRV* is present** + +| rvid indicated by the DCI scheduling the PDSCH | rvid to be applied to n th transmission occasion with second TCI state | | | | +|------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|--------------------|--------------------|--------------------| +| | n mod 4 = 0 | n mod 4 = 1 | n mod 4 = 2 | n mod 4 = 3 | +| | | | | | +| | | | | | +| | | | | | +| | | | | | + +- If one TCI state is indicated by the DCI field 'Transmission Configuration Indication' for a UE not configured with *dl-OrJointTCI-StateList*, or one indicated TCI states applicable to PDSCH for a UE configured with *dl-OrJointTCI-StateList*, together with the DCI field 'Time domain resource assignment' indicating an entry which contains *repetitionNumber* in *PDSCH-TimeDomainResourceAllocation* and DM-RS port(s) within one CDM group in the DCI field 'Antenna Port(s)', the same SLIV is applied for all PDSCH transmission occasions across the *repetitionNumber* consecutive slots, the first PDSCH transmission occasion follows Clause 5.1.2.1, the same TCI state is applied to all PDSCH transmission occasions. The UE may expect that each PDSCH transmission occasion is limited to two transmission layers. For all PDSCH transmission occasions, the redundancy version to be applied is derived according to Table 5.1.2.1-2, where is counted considering PDSCH transmission occasions. + +- Otherwise, the UE is expected to receive a single PDSCH transmission occasion, and the resource allocation in the time domain follows Clause 5.1.2.1. + +For *pdsch-TimeDomainAllocationListForMultiPDSCH* in *pdsch-Config* each PDSCH has a separate SLIV, mapping type and $K_0$ . The number of scheduled PDSCHs is signalled by the number of indicated SLIVs in the row of the *pdsch-TimeDomainAllocationListForMultiPDSCH* signalled in DCI format 1\_1. + +If a UE is configured with *pdsch-TimeDomainAllocationListForMultiPDSCH* in which one or more rows contain multiple *SLIV*s for PDSCH on a DL BWP of a serving cell, and the UE is indicated re-transmission of PDSCH corresponding to a DL SPS by DCI format 1\_1, the UE does not expect that the number of indicated *SLIV*s in the row of the *pdsch-TimeDomainAllocationListForMultiPDSCH* by the DCI is more than one. + +If a UE is configured with *pdsch-TimeDomainAllocationListForMultiPDSCH* in which one or more rows contain multiple *SLIV*s for PDSCH on a DL BWP of a serving cell, the UE does not expect to be scheduled with one or multiple PDSCH receptions by a single DCI format 1\_1, where each PDSCH reception overlaps with a UL symbol indicated by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* if provided. + +##### 5.1.2.1.1 Determination of the resource allocation table to be used for PDSCH + +Table 5.1.2.1.1-1 and Table 5.1.2.1.1-1A define which PDSCH time domain resource allocation configuration to apply. Either a default PDSCH time domain allocation A, B or C according to tables 5.1.2.1.1-2, 5.1.2.1.1-3, 5.1.2.1.1-4 and 5.1.2.1.1-5 is applied, or the higher layer configured *pdsch-TimeDomainAllocationList* or *pdsch-TimeDomainAllocationListForMultiPDSCH* or *pdsch-TimeDomainAllocationListDCI-1-2* is applied. For operation with shared spectrum channel access in frequency range 1, as described in [16, TS 37.213], UE reinterprets *S* and *L* in row 9 of Table 5.1.2.1.1-2 as *S*=6 and *L*=7. + +**Table 5.1.2.1.1-1: Applicable PDSCH time domain resource allocation for DCI formats 1\_0, 1\_1, 1\_3, 4\_0, 4\_1 and 4\_2** + +| RNTI | PDCCH search space | SS/PBCH block and CORESET | PDSCH-ConfigCommon | PDSCH-Config | pdsch-ConfigMTC H / pdsch-ConfigGMTCH | PDSC H- g includes pdsch- | PDSCH time domain resource allocation to apply | +|------|--------------------|---------------------------|--------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|------------------------------------------------| +| | | | | | -
Confi
gMTC
H /
pdsch
-
Confi
gMTCH
H
includ
es
pdsch
-
Time
Doma
inAllo
cation
List
Or
pdsch
-
Confi
gMulti
cast
includ
es
pdsch
-
Time
Doma
inAllo | PDSC
H-
g
includ
es
pdsch
-
Time
Doma
inAllo
cation
ListF
orMul
tiPDS
CH | | + +| | | | | | cation
List | | | +|----------------------------------|-------------------------------------------------------|---------|---------|-----|------------------------|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| SI-RNTI | Type0 common | 1 | - | - | - | - | Default A for normal CP | +| | | 2 | - | - | - | - | Default B | +| | | 3 | - | - | - | - | Default C | +| SI-RNTI | Type0A common | 1 | No | - | - | - | Default A | +| | | 2 | No | - | - | - | Default B | +| | | 3 | No | - | - | - | Default C | +| | | 1,2, 3 | Yes | - | - | - | Pdsch-TimeDomainAllocationList provided in PDSCH-ConfigCommon | +| RA-RNTI, MSGB-RNTI, TC-RNTI | Type1 common | 1,2, 3 | No | - | - | - | Default A | +| | | 1,2, 3 | Yes | - | - | - | Pdsch-TimeDomainAllocationList provided in PDSCH-ConfigCommon | +| P-RNTI | Type2 common | 1 | No | - | - | - | Default A | +| | | 2 | No | - | - | - | Default B | +| | | 3 | No | - | - | - | Default C | +| | | 1,2, 3 | Yes | - | - | - | Pdsch-TimeDomainAllocationList provided in PDSCH-ConfigCommon | +| MCCH-RNTI, multicast-MCCH-RNTI | Type 0/0B/3 common for broadcast or muticast | 1 | No | - | No | - | Default A | +| | | 2 | No | - | No | - | Default B | +| | | 3 | No | - | No | - | Default C | +| | | 1,2, 3 | Yes | - | No | - | pdsch-TimeDomainAllocationList provided in PDSCH-ConfigCommon | +| | | 1,2, 3 | No/ Yes | - | Yes | - | pdsch-TimeDomainAllocationList provided in pdsch-ConfigMCCH | +| G-RNTI for broadcast or muticast | Type 0/0B/3 common for broadcast or muticast | 1 | No | - | No | - | Default A | +| | | 2 | No | - | No | - | Default B | +| | | 3 | No | - | No | - | Default C | +| | | 1,2, 3 | Yes | - | No | - | pdsch-TimeDomainAllocationList provided in PDSCH-ConfigCommon | +| | | 1,2, 3 | No/ Yes | - | Yes | - | pdsch-TimeDomainAllocationList provided in pdsch-ConfigMTCH, if configured, otherwise pdsch-TimeDomainAllocationList provided in pdsch-ConfigMCCH | +| | | 1,2, 3 | No/ Yes | - | Yes | - | pdsch-TimeDomainAllocationList provided in pdsch-ConfigMCCH | +| C-RNTI, MCS-C-RNTI, CS-RNTI | Any common search space associated with CORESET 0 | 1, 2, 3 | No | - | - | - | Default A | +| | | 1, 2, 3 | Yes | - | - | - | pdsch-TimeDomainAllocationList provided in PDSCH-ConfigCommon | +| C-RNTI, MCS-C-RNTI, CS-RNTI | Any common search space not associated with CORESET 0 | 1,2, 3 | No | No | - | - | Default A | +| | | 1,2, 3 | Yes | No | - | - | pdsch-TimeDomainAllocationList provided in PDSCH-ConfigCommon | +| | | 1,2, 3 | No/ Yes | Yes | - | - | pdsch-TimeDomainAllocationList provided in PDSCH-Config | +| | UE specific search space | 1,2, 3 | No/ Yes | - | - | Yes | pdsch-TimeDomainAllocationListForMultiPDSC H provided in PDSCH-Config (Note 2) | +| G-RNTI for multicast, | Type 3 common | 1,2, 3 | No | - | No | - | Default A | + +| | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|--------|--------|---|-----|---|-----------------------------------------------------------------------------------------|--| +| G-CS-RNTI | search space for multicast | 1,2, 3 | Yes | - | No | - | pdsch-TimeDomainAllocationList provided in PDSCH-ConfigCommon (Note 1) | | +| | | 1,2, 3 | No/Yes | - | Yes | - | pdsch-TimeDomainAllocationList provided in pdsch-ConfigMulticast (Note 1) | | +| Note 1: For a UE that supports multicast, the same TDRA table applies to all G-RNTIs and G-CS-RNTIs (configured for multicast) if configured on a given serving cell. | | | | | | | | | +| Note 2: If pdsch-TimeDomainAllocationListForMultiPDSCH is provided, it is applicable to DCI format 1_1 only. | | | | | | | | | + +Table 5.1.2.1.1-1A: Applicable PDSCH time domain resource allocation for DCI format 1\_2 + +| PDSCH-ConfigCommon includes pdsch-TimeDomainAllocationList | PDSCH-Config includes pdsch-TimeDomainAllocationList | PDSCH-Config includes pdsch-TimeDomainAllocationListDCI-1-2 | PDSCH time domain resource allocation to apply | +|--------------------------------------------------------------------------|--------------------------------------------------------------------|---------------------------------------------------------------------------|------------------------------------------------------------------------------| +| No | No | No | Default A | +| Yes | No | No | pdsch-TimeDomainAllocationList provided in PDSCH-ConfigCommon | +| No/Yes | Yes | No | pdsch-TimeDomainAllocationList provided in PDSCH-Config | +| No/Yes | No/Yes | Yes | pdsch-TimeDomainAllocationListDCI-1-2 provided in PDSCH-Config | + +Table 5.1.2.1.1-2: Default PDSCH time domain resource allocation A for normal CP + +| Row index | dmrs-TypeA-Position | PDSCH mapping type | K0 | S | L | +|-----------|----------------------------|--------------------|----------------------|----------|----------| +| 1 | 2 | Type A | 0 | 2 | 12 | +| | 3 | Type A | 0 | 3 | 11 | +| 2 | 2 | Type A | 0 | 2 | 10 | +| | 3 | Type A | 0 | 3 | 9 | +| 3 | 2 | Type A | 0 | 2 | 9 | +| | 3 | Type A | 0 | 3 | 8 | +| 4 | 2 | Type A | 0 | 2 | 7 | +| | 3 | Type A | 0 | 3 | 6 | +| 5 | 2 | Type A | 0 | 2 | 5 | +| | 3 | Type A | 0 | 3 | 4 | +| 6 | 2 | Type B | 0 | 9 | 4 | +| | 3 | Type B | 0 | 10 | 4 | +| 7 | 2 | Type B | 0 | 4 | 4 | +| | 3 | Type B | 0 | 6 | 4 | +| 8 | 2,3 | Type B | 0 | 5 | 7 | +| 9 | 2,3 | Type B | 0 | 5 | 2 | +| 10 | 2,3 | Type B | 0 | 9 | 2 | +| 11 | 2,3 | Type B | 0 | 12 | 2 | +| 12 | 2,3 | Type A | 0 | 1 | 13 | +| 13 | 2,3 | Type A | 0 | 1 | 6 | +| 14 | 2,3 | Type A | 0 | 2 | 4 | +| 15 | 2,3 | Type B | 0 | 4 | 7 | +| 16 | 2,3 | Type B | 0 | 8 | 4 | + +**Table 5.1.2.1.1-3: Default PDSCH time domain resource allocation A for extended CP** + +| Row index | dmrs-TypeA-Position | PDSCH mapping type | K0 | S | L | +|-----------|----------------------------|--------------------|----------------------|----------|----------| +| 1 | 2 | Type A | 0 | 2 | 6 | +| | 3 | Type A | 0 | 3 | 5 | +| 2 | 2 | Type A | 0 | 2 | 10 | +| | 3 | Type A | 0 | 3 | 9 | +| 3 | 2 | Type A | 0 | 2 | 9 | +| | 3 | Type A | 0 | 3 | 8 | +| 4 | 2 | Type A | 0 | 2 | 7 | +| | 3 | Type A | 0 | 3 | 6 | +| 5 | 2 | Type A | 0 | 2 | 5 | +| | 3 | Type A | 0 | 3 | 4 | +| 6 | 2 | Type B | 0 | 6 | 4 | +| | 3 | Type B | 0 | 8 | 2 | +| 7 | 2 | Type B | 0 | 4 | 4 | +| | 3 | Type B | 0 | 6 | 4 | +| 8 | 2,3 | Type B | 0 | 5 | 6 | +| 9 | 2,3 | Type B | 0 | 5 | 2 | +| 10 | 2,3 | Type B | 0 | 9 | 2 | +| 11 | 2,3 | Type B | 0 | 10 | 2 | +| 12 | 2,3 | Type A | 0 | 1 | 11 | +| 13 | 2,3 | Type A | 0 | 1 | 6 | +| 14 | 2,3 | Type A | 0 | 2 | 4 | +| 15 | 2,3 | Type B | 0 | 4 | 6 | +| 16 | 2,3 | Type B | 0 | 8 | 4 | + +**Table 5.1.2.1.1-4: Default PDSCH time domain resource allocation B** + +| Row index | dmrs-TypeA-Position | PDSCH mapping type | K0 | S | L | +|-------------|----------------------------|--------------------|----------------------|----------|----------| +| 1 | 2,3 | Type B | 0 | 2 | 2 | +| 2 | 2,3 | Type B | 0 | 4 | 2 | +| 3 | 2,3 | Type B | 0 | 6 | 2 | +| 4 | 2,3 | Type B | 0 | 8 | 2 | +| 5 | 2,3 | Type B | 0 | 10 | 2 | +| 6 | 2,3 | Type B | 1 | 2 | 2 | +| 7 | 2,3 | Type B | 1 | 4 | 2 | +| 8 | 2,3 | Type B | 0 | 2 | 4 | +| 9 | 2,3 | Type B | 0 | 4 | 4 | +| 10 | 2,3 | Type B | 0 | 6 | 4 | +| 11 | 2,3 | Type B | 0 | 8 | 4 | +| 12 (Note 1) | 2,3 | Type B | 0 | 10 | 4 | +| 13 (Note 1) | 2,3 | Type B | 0 | 2 | 7 | +| 14 (Note 1) | 2 | Type A | 0 | 2 | 12 | +| | 3 | Type A | 0 | 3 | 11 | +| 15 | 2,3 | Type B | 1 | 2 | 4 | +| 16 | Reserved | | | | | + +Note 1: If the PDSCH was scheduled with SI-RNTI in PDCCH Type0 common search space, the UE may assume that this PDSCH resource allocation is not applied + +**Table 5.1.2.1.1-5: Default PDSCH time domain resource allocation C** + +| Row index | dmrs-TypeA-Position | PDSCH mapping type | K0 | S | L | +|-------------|----------------------------|--------------------|----------------------|----------|----------| +| 1 (Note 1) | 2,3 | Type B | 0 | 2 | 2 | +| 2 | 2,3 | Type B | 0 | 4 | 2 | +| 3 | 2,3 | Type B | 0 | 6 | 2 | +| 4 | 2,3 | Type B | 0 | 8 | 2 | +| 5 | 2,3 | Type B | 0 | 10 | 2 | +| 6 (Note 2) | 2,3 | Type B | 0 | 11 | 2 | +| 7 | Reserved | | | | | +| 8 | 2,3 | Type B | 0 | 2 | 4 | +| 9 | 2,3 | Type B | 0 | 4 | 4 | +| 10 | 2,3 | Type B | 0 | 6 | 4 | +| 11 | 2,3 | Type B | 0 | 8 | 4 | +| 12 | 2,3 | Type B | 0 | 10 | 4 | +| 13 (Note 1) | 2,3 | Type B | 0 | 2 | 7 | +| 14 (Note 1) | 2 | Type A | 0 | 2 | 12 | +| | 3 | Type A | 0 | 3 | 11 | +| 15 (Note 1) | 2,3 | Type A | 0 | 0 | 6 | +| 16 (Note 1) | 2,3 | Type A | 0 | 2 | 6 | + +Note 1: The UE may assume that this PDSCH resource allocation is not used, if the PDSCH was scheduled with SI-RNTI in PDCCH Type0 common search space + +Note 2: This applies for Case F and Case G candidate SS/PBCH block pattern described in clause 4 of [6, TS 38.213] + +#### 5.1.2.2 Resource allocation in frequency domain + +Two downlink resource allocation schemes, type 0 and type 1, are supported. The UE shall assume that when the scheduling grant is received with DCI format 1\_0, 4\_0 or 4\_1 then downlink resource allocation type 1 is used. + +If the scheduling DCI is configured to indicate the downlink resource allocation type as part of the '*Frequency domain resource assignment*' field by setting a higher layer parameter *resourceAllocation* in *PDSCH-Config* to 'dynamicSwitch', for DCI format 1\_1 or setting a higher layer parameter *resourceAllocationDCI-1-2* in *PDSCH-Config* to 'dynamicSwitch' for DCI format 1\_2 or setting a higher layer parameter *resourceAllocationDCI-1-3* in *PDSCH-Config* to 'dynamicSwitch' for DCI format 1\_3 or setting a higher layer parameter *resourceAllocation* in *pdsch-ConfigMulticast* to 'dynamicSwitch' for DCI format 4\_2, the UE shall use downlink resource allocation type 0 or type 1 as defined by this DCI field. Otherwise the UE shall use the downlink frequency resource allocation type as defined by the higher layer parameter *resourceAllocation* in *PDSCH-Config* for DCI format 1\_1 or by the higher layer parameter *resourceAllocationDCI-1-2* for DCI format 1\_2 or by the higher layer parameter *resourceAllocationDCI-1-3* for DCI format 1\_3 or by the higher layer parameter *resourceAllocation* in *pdsch-ConfigMulticast* for DCI format 4\_2. + +If a bandwidth part indicator field is not configured in the scheduling DCI or the UE does not support active BWP change via DCI, the RB indexing for downlink type 0 and type 1 resource allocation is determined within the UE's active bandwidth part. If a bandwidth part indicator field is configured in the scheduling DCI and the UE supports active BWP change via DCI, the RB indexing for downlink type 0 and type 1 resource allocation is determined within the UE's bandwidth part indicated by bandwidth part indicator field value in the DCI. The UE shall upon detection of PDCCH intended for the UE determine first the downlink bandwidth part and then the resource allocation within the bandwidth part. + +For a PDSCH scheduled with a DCI format 1\_0 in any type of PDCCH common search space, regardless of which bandwidth part is the active bandwidth part, RB numbering starts from the lowest RB of the CORESET in which the DCI was received; otherwise RB numbering starts from the lowest RB in the determined downlink bandwidth part. When the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], for the purpose of determining the downlink RB set of a PDSCH when scheduled by DCI format 1\_0, the CORESET with lower ID among two CORESETs associated with two PDCCH candidates is used. + +##### 5.1.2.2.1 Downlink resource allocation type 0 + +In downlink resource allocation of type 0, the resource block assignment information includes a bitmap indicating the Resource Block Groups (RBGs) that are allocated to the scheduled UE where a RBG is a set of consecutive virtual resource blocks defined by higher layer parameter *rbg-Size* configured by *PDSCH-Config* for DCI format 1\_1 or 1\_2 or + +by higher layer parameter *rbg-SizeDCI-1-3* configured by *PDSCH-Config* for DCI format 1\_3 and the size of the bandwidth part as defined in Table 5.1.2.2.1-1. + +**Table 5.1.2.2.1-1: Nominal RBG size $P$** + +| Bandwidth Part Size | Configuration 1 | Configuration 2 | Configuration 3 | +|---------------------|-----------------|-----------------|-----------------| +| 1 – 36 | 2 | 4 | 8 | +| 37 – 72 | 4 | 8 | 16 | +| 73 – 144 | 8 | 16 | 32 | +| 145 – 275 | 16 | 16 | 32 | + +The total number of RBGs ( $N_{RBG}$ ) for a downlink bandwidth part $i$ of size $PRBs$ is given by $\lceil PRBs/P \rceil$ , where + +- the size of the first RBG is $\lceil PRBs/P \rceil - \lfloor PRBs/P \rfloor$ , +- the size of last RBG is $\lfloor PRBs/P \rfloor$ if $PRBs \bmod P = 0$ and $P$ otherwise, +- the size of all other RBGs is $P$ . + +In downlink resource allocation of type 0 scheduled using a DCI with CRC scrambled by G-RNTI for multicast or G-CS-RNTI, the resource block assignment information bitmap is calculated based on the description above with the following changes: the parameter $CFR$ is the starting PRB of the CFR, $CFR$ is the size of the common frequency resource (CFR) and the value of the higher layer parameter *rbg-Size* is configured by *pdsch-ConfigMulticast*. + +The bitmap is of size $N_{RBG}$ bits with one bitmap bit per RBG such that each RBG is addressable. The RBGs shall be indexed in the order of increasing frequency and starting at the lowest frequency of the bandwidth part. The order of RBG bitmap is such that RBG 0 to RBG $N_{RBG}-1$ are mapped from MSB to LSB. The RBG is allocated to the UE if the corresponding bit value in the bitmap is 1, the RBG is not allocated to the UE otherwise. + +##### 5.1.2.2.2 Downlink resource allocation type 1 + +In downlink resource allocation of type 1, the resource block assignment information indicates to a scheduled UE a set of contiguously allocated non-interleaved or interleaved virtual resource blocks within the active bandwidth part of size $PRBs$ except for the case when DCI format 1\_0 is decoded in any common search space in which case the size of CORESET 0 shall be used if CORESET 0 is configured for the cell and the size of initial DL bandwidth part shall be used if CORESET 0 is not configured for the cell. + +A downlink type 1 resource allocation field consists of a resource indication value ( $RIV$ ) corresponding to a starting virtual resource block ( $RB_{start}$ ) and a length in terms of contiguously allocated resource blocks. The resource indication value is defined by + +if $L_{RBs} \leq \lfloor N_{BWP}^{initial} / 2 \rfloor$ then + +else + +where $L_{RBs} \geq 1$ and shall not exceed $N_{BWP}^{active}$ . + +When the DCI size for DCI format 1\_0 in USS is derived from the size of DCI format 1\_0 in CSS but applied to an active BWP with size of $N_{BWP}^{active}$ , a downlink type 1 resource block assignment field consists of a resource indication value ( $RIV$ ) corresponding to a starting resource block $RB_{start} = 0, K, 2 \cdot K, \dots, (N_{BWP}^{initial} - 1) \cdot K$ and a length in terms of virtually contiguously allocated resource blocks $L_{RBs} = K, 2 \cdot K, \dots, N_{BWP}^{initial} \cdot K$ , where $N_{BWP}^{initial}$ is given by + +- the size of CORESET 0 if CORESET 0 is configured for the cell; +- the size of initial DL bandwidth part if CORESET 0 is not configured for the cell. + +The resource indication value is defined by: + +if $(L_{RBs} - 1) \leq \lfloor N_{BWP}^{initial} / 2 \rfloor$ then + +$$RIV = N_{BWP}^{initial} (L'_{RBs} - 1) + RB'_{start}$$ + +else + +$$RIV = N_{BWP}^{initial} (N_{BWP}^{initial} - L'_{RBs} + 1) + (N_{BWP}^{initial} - 1 - RB'_{start})$$ + +where $L'_{RBs} = L_{RBs} / K$ , $RB'_{start} = RB_{start} / K$ and where $L'_{RBs}$ shall not exceed $N_{BWP}^{initial} - RB'_{start}$ . + +If $N_{BWP}^{active} > N_{BWP}^{initial}$ , $K$ is the maximum value from set $\{1, 2, 4, 8\}$ which satisfies $K \leq \left\lfloor N_{BWP}^{active} / N_{BWP}^{initial} \right\rfloor$ ; otherwise $K = 1$ . + +When the scheduling grant is received with DCI format 1\_2 or 1\_3, a downlink type 1 resource allocation field consists of a resource indication value ( $RIV$ ) corresponding to a starting resource block group $RBG_{start}=0, 1, \dots, N_{RBG}-1$ and a length in terms of virtually contiguously allocated resource block groups $L_{RBGs}=1, \dots, N_{RBG}$ , where the resource block groups are defined as in 5.1.2.2.1 with $P$ defined by *resourceAllocationType1GranularityDCI-1-2* for DCI format 1\_2 and *resourceAllocationType1GranularityDCI-1-3* for DCI format 1\_3 if the UE is configured with higher layer parameter *resourceAllocationType1GranularityDCI-1-2* or *resourceAllocationType1GranularityDCI-1-3*, and $P=1$ otherwise. The resource indication value is defined by + +if $(L_{RBGs} - 1) \leq \left\lfloor N_{RBG} / 2 \right\rfloor$ then + +$$RIV = N_{RBG} (L_{RBGs} - 1) + RBG_{start}$$ + +else + +$$RIV = N_{RBG} (N_{RBG} - L_{RBGs} + 1) + (N_{RBG} - 1 - RBG_{start})$$ + +where $L_{RBGs} \geq 1$ and shall not exceed $N_{RBG} - RBG_{start}$ . + +##### 5.1.2.2.3 Downlink resource allocation type 1 for multicast/broadcast + +In downlink resource allocation of type 1 scheduled using DCI format 4\_0 or DCI format 4\_1 with CRC scrambled by G-RNTI, G-CS-RNTI, MCCH-RNTI or multicast-MCCH-RNTI, the resource block assignment information indicates to a scheduled UE a set of contiguously allocated non-interleaved or interleaved virtual resource blocks. + +A downlink type 1 resource block assignment field in the DCI format 4\_0 or DCI format 4\_1 consists of a $RIV$ corresponding to a starting resource block in reference to the lowest RB of the CFR + +$RB_{start} = 0, K, 2 \cdot K, \dots, (N_{BWP}^{initial} - 1) \cdot K$ and a length in terms of virtually contiguously allocated resource blocks $L_{RBs}$ , + +where $N_{BWP}^{initial}$ is given by + +- the size of CORESET 0 if CORESET 0 is configured for the cell; +- the size of initial DL bandwidth part if CORESET 0 is not configured for the cell. + +The resource indication value is defined by: + +if $(L'_{RBs} - 1) \leq \left\lfloor N_{BWP}^{initial} / 2 \right\rfloor$ then + +$$RIV = N_{BWP}^{initial} (L'_{RBs} - 1) + RB'_{start}$$ + +else + +$$RIV = N_{BWP}^{initial} (N_{BWP}^{initial} - L'_{RBs} + 1) + (N_{BWP}^{initial} - 1 - RB'_{start})$$ + +where $L'_{RBs} = L_{RBs} / K$ , $RB'_{start} = RB_{start} / K$ and where $L'_{RBs}$ shall not exceed $N_{BWP}^{initial} - RB'_{start}$ . + +If, $K$ is the maximum value from set $\{1, 2, 4, 6, 8, 10, 12\}$ which satisfies ; otherwise $K = 1$ . + +In downlink resource allocation of type 1 scheduled using DCI format 4\_2 with CRC scrambled by G-RNTI for multicast or G-CS-RNTI, the description in clause 5.1.2.2.2 with the following changes: corresponds to a starting resource block in reference to the lowest RB of the CFR and is the size of the CFR. + +#### 5.1.2.3 Physical resource block (PRB) bundling + +The PRB bundling procedures for PDSCH scheduled by PDCCH with DCI format 1\_1 described in this clause equally apply to PDSCH scheduled by PDCCH with DCI format 1\_2, by applying the parameters of *prb-BundlingTypeDCI-1-2* instead of *prb-BundlingType* as well as *vrb-ToPRB-InterleaverDCI-1-2* instead of *vrb-ToPRB-Interleaver*. The PRB bundling procedures for PDSCH scheduled by PDCCH with DCI format 1\_1 described in this clause equally apply to PDSCH scheduled by PDCCH with DCI format 1\_3. The PRB bundling procedures for PDSCH scheduled by PDCCH with DCI format 1\_1 described in this clause equally apply to PDSCH scheduled by PDCCH with DCI format 4\_2, by applying the parameters of *prb-BundlingType* given by *pdsch-ConfigMulticast* as well as *vrb-ToPRB-Interleaver* given by *pdsch-ConfigMulticast*. + +A UE may assume that precoding granularity is $P'_{BWP,i}$ consecutive resource blocks in the frequency domain. $P'_{BWP,i}$ can be equal to one of the values among {2, 4, wideband}. + +If $P'_{BWP,i}$ is determined as "wideband", the UE is not expected to be scheduled with non-contiguous PRBs and the UE may assume that the same precoding is applied to the allocated resource associated with a same TCI state or a same QCL assumption. + +If $P'_{BWP,i}$ is determined as one of the values among {2, 4}, Precoding Resource Block Group (PRGs) partitions the bandwidth part *i* with $P'_{BWP,i}$ consecutive PRBs. Actual number of consecutive PRBs in each PRG could be one or more. + +The first PRG size is given by $P'_{BWP,i} - N_{BWP,i}^{start} \bmod P'_{BWP,i}$ and the last PRG size given by $N_{BWP,i}^{end} - N_{BWP,i}^{start} \bmod P'_{BWP,i}$ , and the last PRG size is if $N_{BWP,i}^{end} - N_{BWP,i}^{start} \bmod P'_{BWP,i} = 0$ . For PDSCH scheduled by PDCCH with DCI scrambled using G-RNTI or G-CS-RNTI, $N_{BWP,i}^{start}$ is the starting PRB of the CFR and $N_{BWP,i}^{end}$ is the CFR. + +The UE may assume the same precoding is applied for any downlink contiguous allocation of PRBs in a PRG. + +For PDSCH carrying SIB1 scheduled by PDCCH with CRC scrambled by SI-RNTI, a PRG is partitioned from the lowest numbered resource block of CORESET 0 if the corresponding PDCCH is associated with CORESET 0 and Type0-PDCCH common search space and is addressed to SI-RNTI; otherwise, a PRG is partitioned from common resource block 0. + +If a UE is scheduled a PDSCH with DCI format 1\_0 or 4\_0 for broadcast or 4\_1 for multicast, the UE shall assume that $P'_{BWP,i}$ is equal to 2 PRBs. + +When receiving PDSCH scheduled by PDCCH with DCI format 1\_1 with CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI, $P'_{BWP,i}$ for bandwidth part is equal to 2 PRBs unless configured by the higher layer parameter *prb-BundlingType* given by *PDSCH-Config*. + +When receiving PDSCH scheduled by PDCCH with DCI format 1\_1 with CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI, if the higher layer parameter *prb-BundlingType* is set to 'dynamicBundling', the higher layer parameters *bundleSizeSet1* and *bundleSizeSet2* configure two sets of $P'_{BWP,i}$ values, the first set can take one or two $P'_{BWP,i}$ values among {2, 4, wideband}, and the second set can take one $P'_{BWP,i}$ value among {2, 4, wideband}. + +If the PRB '*bundling size indicator*' signalled in DCI format 1\_1 as defined in Clause 7.3.1.2.2 of [5, TS 38.212] + +- is set to '0', the UE shall use the $P'_{BWP,i}$ value from the second set of $P'_{BWP,i}$ values when receiving PDSCH scheduled by the same DCI. +- is set to '1' and one value is configured for the first set of $P'_{BWP,i}$ values, the UE shall use this $P'_{BWP,i}$ value when receiving PDSCH scheduled by the same DCI +- is set to '1' and two values are configured for the first set of $P'_{BWP,i}$ values as 'n2-wideband' (corresponding to two $P'_{BWP,i}$ values 2 and wideband) or 'n4-wideband' (corresponding to two $P'_{BWP,i}$ values 4 and wideband), the UE shall use the value when receiving PDSCH scheduled by the same DCI as follows: + +- If the scheduled PRBs are contiguous and the size of the scheduled PRBs is larger than $P'_{BWP,i}$ is the same as the scheduled bandwidth, otherwise $P'_{BWP,i}$ is set to the remaining configured value of 2 or 4, respectively. + +When receiving PDSCH scheduled by PDCCH with DCI format 1\_1 with CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI, if the higher layer parameter *prb-BundlingType* is set to 'staticBundling', the $P'_{BWP,i}$ value is configured with the single value indicated by the higher layer parameter *bundleSize*. + +When a UE is configured with nominal RBG size for bandwidth part *i* according to Clause 5.1.2.2.1, or when a UE is configured with interleaving unit of 2 for VRB to PRB mapping provided by the higher layer parameter *vrp-ToPRB-Interleaver* given by *PDSCH-Config* for bandwidth part *i*, the UE is not expected to be configured with $P'_{BWP,i} = 4$ . + +For a UE configured by the higher layer parameter *repetitionScheme* set to 'fdmSchemeA' or 'fdmSchemeB', and when the UE not configured with *dl-OrJointTCI-StateList* is indicated with two TCI states in a codepoint of the DCI field '*Transmission Configuration Indication*', or when the UE configured with *dl-OrJointTCI-StateList* and having two indicated TCI States to be applied to PDSCH, and the UE is indicated with DM-RS port(s) within one CDM group in the DCI field '*Antenna Port(s)*', + +- If *repetitionScheme* is determined as "wideband", the first PRBs are assigned to the first TCI state and the remaining PRBs are assigned to the second TCI state, where *i* is the total number of allocated PRBs for the UE. +- If *repetitionScheme* is determined as one of the values among {2, 4}, even PRGs within the allocated frequency domain resources are assigned to the first TCI state and odd PRGs within the allocated frequency domain resources are assigned to the second TCI state, wherein the PRGs are numbered continuously in increasing order with the first PRG index equal to 0. +- The UE is not expected to receive more than two PDSCH transmission layers for each PDSCH transmission occasion. + +For a UE configured by the higher layer parameter *repetitionScheme* set to 'fdmSchemeB', and when the UE not configured with *dl-OrJointTCI-StateList* is indicated with two TCI states in a codepoint of the DCI field '*Transmission Configuration Indication*', or when the UE configured with *dl-OrJointTCI-StateList* and having two indicated TCI States to be applied to PDSCH, and the UE is indicated with DM-RS port(s) within one CDM group in the DCI field '*Antenna Port(s)*', each PDSCH transmission occasion shall follow the Clause 7.3.1 of [4, TS 38.211] with the mapping to resource elements determined by the assigned PRBs for corresponding TCI state of the PDSCH transmission occasion, and the UE shall only expect at most two code blocks per PDSCH transmission occasion when a single transmission layer is scheduled and a single code block per PDSCH transmission occasion when two transmission layers are scheduled. For two PDSCH transmission occasions, the redundancy version to be applied is derived according to Table 5.1.2.1-2, where *rv* are applied to the first and second TCI state, respectively. + +### 5.1.3 Modulation order, target code rate, redundancy version and transport block size determination + +To determine the modulation order, target code rate, and transport block size(s) in the physical downlink shared channel, the UE shall first + +- read the 5-bit modulation and coding scheme field ( $I_{MCS}$ ) in the DCI to determine the modulation order ( $Q_m$ ) and target code rate ( $R$ ) based on the procedure defined in Clause 5.1.3.1, and +- read '*redundancy version*' field (*rv*) in the DCI to determine the redundancy version. + +and second + +- the UE shall use the number of layers (*v*), the total number of allocated PRBs before rate matching ( $n_{PRB}$ ) to determine the transport block size based on the procedure defined in Clause 5.1.3.2. + +The UE may skip decoding a transport block in an initial transmission if the effective channel code rate is higher than 0.95, where the effective channel code rate is defined as the number of downlink information bits (including CRC bits) divided by the number of physical channel bits on PDSCH. + +When the UE is scheduled with multiple PDSCHs on a serving cell by a DCI, as described in clause 5.1.2.1, the bits of *rv* field and NDI field, respectively, in the DCI are one-to-one mapped to the scheduled PDSCH(s) indicated by the + +TDRA information field with the corresponding transport block(s) in the scheduled order, where the LSB bits of the *rv* field and NDI field, respectively, correspond to the last scheduled PDSCH indicated by the TDRA information field. + +The UE is not expected to handle any transport blocks (TBs) in a 14 consecutive-symbol duration for normal CP (or 12 for extended CP) ending at the last symbol of the latest PDSCH transmission within an active BWP on a serving cell whenever + +where, for the serving cell, + +- *S* is the set of TBs belonging to PDSCH(s) that are partially or fully contained in the consecutive-symbol duration +- for the *i*th TB + - $C'_i$ is the number of scheduled code blocks for as defined in [5, 38.212]. + - $L_i$ is the number of OFDM symbols assigned to the PDSCH + - $x_i$ is the number of OFDM symbols of the PDSCH contained in the consecutive-symbol duration + - based on the values defined in Clause 5.4.2.1 [5, TS 38.212] + - $r_{i,0}$ is the starting location of RV for the *i*th transmission + - $C'_i$ of the scheduled code blocks for the *i*th transmission + - $L_i$ is the circular buffer length + - $i$ is the current (re)transmission for the *i*th TB + - $\mu$ corresponds to the subcarrier spacing of the BWP (across all configured BWPs of a carrier) that has the largest configured number of PRBs + - in case there is more than one BWP corresponding to the largest configured number of PRBs, $\mu$ follows the BWP with the largest subcarrier spacing. + - $\mu_{active}$ corresponds to the subcarrier spacing of the active BWP + - $R_{LBRM} = 2/3$ as defined in Clause 5.4.2.1 [5, TS 38.212] + - $TBS_{LBRM}$ as defined based on the parameters for unicast in Clause 5.4.2.1 [5, TS 38.212] + - $X$ as defined for downlink max MIMO layer for unicast in Clause 5.4.2.1 [5, TS 38.212]. + +If the UE skips decoding, the physical layer indicates to higher layer that the transport block is not successfully decoded. + +Within a cell group, a UE is not required to handle PDSCH(s) transmissions including unicast and/or multicast/broadcast in slot $s_j$ in serving cell-*j*, and for $j = 0, 1, 2, \dots, J-1$ , slot $s_j$ overlapping with any given point in time, if the following condition is not satisfied at that point in time: + +where, + +- *J* is the number of configured serving cells belonging to a frequency range +- for the *j*-th serving cell, + - *M* is the number of TB(s) transmitted in slot $s_j$ . If there are two PDSCH transmission occasions of the same TB (in time domain or in frequency domain) in the slot $s_j$ , each transmission occasion is counted separately. + - $T_{slot}^{\mu(j)} = 10^{-3}/2^{\mu(j)}$ , where $\mu(j)$ is the numerology for PDSCH(s) in slot $s_j$ of the *j*-th serving cell. + - for the *m*-th TB, + +- $A$ is the number of bits in the transport block as defined in Clause 7.2.1 [5, TS 38.212] +- $C$ is the total number of code blocks for the transport block defined in Clause 5.2.2 [5, TS 38.212]. +- $N$ is the number of scheduled code blocks for the transport block as defined in Clause 5.4.2.1 [5, TS 38.212] +- $[Mbps]$ is computed as the maximum data rate summed over all the carriers in the frequency range for any signaled band combination and feature set consistent with the configured serving cells, where the data rate value is given by the formula in Clause 4.1.2 in [13, TS 38.306], including the scaling factor $f(i)$ . + +For a $j$ -th serving cell, if higher layer parameter *processingType2Enabled* of *PDSCH-ServingCellConfig* is configured for the serving cell and set to 'enable', or if at least one $I_{MCS} > W$ for a PDSCH for unicast or multicast, where $W = 28$ for MCS tables 5.1.3.1-1 and 5.1.3.1-3, and $W = 27$ for MCS table 5.1.3.1-2, and $W = 26$ for MCS table 5.1.3.1-4, or for a $j$ -th serving cell where UE supports FDM-ed unicast and MBS PDSCH, the UE is not required to handle PDSCH transmissions, if the following condition is not satisfied: + +where + +- $N_{symbols}$ is the number of symbols assigned to the PDSCH(s). For a PDSCH that consists of two PDSCH transmission occasions in time domain in one slot, $N_{symbols}$ is the number of symbols of one transmission occasion. For FDM-ed unicast and MBS PDSCHs in one slot, $N_{symbols}$ is the total number of symbols of the unicast and MBS PDSCHs with fully or partially-overlapped in time domain. +- $M$ is the number of TB(s) in the PDSCH(s) +- where $\mu$ is the numerology of the PDSCH(s) +- for the $m$ -th TB, + - $A$ is the number of bits in the transport block as defined in Clause 7.2.1 [5, TS 38.212] + - $C$ is the total number of code blocks for the transport block defined in Clause 5.2.2 [5, TS 38.212] + - $N$ is the number of scheduled code blocks for the transport block as defined in Clause 5.4.2.1 [5, TS 38.212] +- $[Mbps]$ is computed as the maximum data rate for a carrier in the frequency band of the serving cell for any signaled band combination and feature set consistent with the serving cell, where the data rate value is given by the formula in Clause 4.1.2 in [13, TS 38.306], including the scaling factor $f(i)$ . + +#### 5.1.3.1 Modulation order and target code rate determination + +For the PDSCH scheduled by a PDCCH with DCI format 1\_0, format 1\_1, format 1\_2, format 1\_3, format 4\_0, format 4\_1 or format 4\_2 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, SI-RNTI, RA-RNTI, MSGB-RNTI, G-RNTI, G-CS-RNTI, multicast-MCCH-RNTI, MCCH-RNTI or P-RNTI, or for the PDSCH scheduled without corresponding PDCCH transmissions using the higher-layer-provided PDSCH configuration *SPS-Config*, + +if the higher layer parameter *mcs-Table-r17* given by *PDSCH-Config* is set to 'qam1024', and the PDSCH is scheduled by a PDCCH with DCI format 1\_1 or 1\_3 with CRC scrambled by C-RNTI + +- the UE shall use $I_{MCS}$ and Table 5.1.3.1-4 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical downlink shared channel. + +elseif *mcs-TableDCI-1-2-r17* given by *PDSCH-Config* is set to 'qam1024', and the PDSCH is scheduled by a PDCCH with DCI format 1\_2 with CRC scrambled by C-RNTI + +- the UE shall use $I_{MCS}$ and Table 5.1.3.1-4 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical downlink shared channel. + +elseif the higher layer parameter *mcs-TableDCI-1-2* given by *PDSCH-Config* is set to 'qam256', and the PDSCH is scheduled by a PDCCH with DCI format 1\_2 with CRC scrambled by C-RNTI + +- the UE shall use $I_{MCS}$ and Table 5.1.3.1-2 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical downlink shared channel. + +elseif the UE is not configured with MCS-C-RNTI, the higher layer parameter *mcs-TableDCI-1-2* given by *PDSCH-Config* is set to 'qam64LowSE', and the PDSCH is scheduled by a PDCCH with DCI format 1\_2 scrambled by C-RNTI + +- the UE shall use *IMCS* and Table 5.1.3.1-3 to determine the modulation order (*Qm*) and Target code rate (*R*) used in the physical downlink shared channel. + +elseif the higher layer parameter *mcs-Table* given by *PDSCH-Config* is set to 'qam256', and the PDSCH is scheduled by a PDCCH with DCI format 1\_1 or 1\_3 with CRC scrambled by C-RNTI + +- the UE shall use *IMCS* and Table 5.1.3.1-2 to determine the modulation order (*Qm*) and Target code rate (*R*) used in the physical downlink shared channel. + +elseif the higher layer parameter *mcs-Table* given by *pdsch-ConfigMulticast* is set to 'qam256', and the PDSCH is scheduled by a PDCCH with DCI format 4\_1 or 4\_2 with CRC scrambled by G-RNTI for multicast + +- the UE shall use *IMCS* and Table 5.1.3.1-2 to determine the modulation order (*Qm*) and Target code rate (*R*) used in the physical downlink shared channel. + +elseif the higher layer parameter *mcs-Table* given by *pdsch-ConfigMCCH* and *pdsch-ConfigMTCH* for MBS broadcast is set to 'qam256', and the PDSCH is scheduled by a PDCCH with DCI format 4\_0 with CRC scrambled by MCCH-RNTI or G-RNTI for broadcast + +- the UE shall use *IMCS* and Table 5.1.3.1-2 to determine the modulation order (*Qm*) and Target code rate (*R*) used in the physical downlink shared channel. + +elseif the higher layer parameter *mcs-Table* given by *pdsch-ConfigMCCH* and *pdsch-ConfigMTCH* for MBS multicast is set to 'qam256', and the PDSCH is scheduled by a PDCCH with DCI format 4\_0 with CRC scrambled by multicast-MCCH-RNTI or by a PDCCH with DCI format 4\_1 with CRC scrambled by G-RNTI for multicast in RRC\_INACTIVE + +- the UE shall use *IMCS* and Table 5.1.3.1-2 to determine the modulation order (*Qm*) and Target code rate (*R*) used in the physical downlink shared channel. + +elseif the higher layer parameter *mcs-Table* given by *pdsch-ConfigMulticast* is set to 'qam64LowSE', and the PDSCH is scheduled by a PDCCH with DCI format 4\_1 or 4\_2 with CRC scrambled by G-RNTI for multicast + +- the UE shall use *IMCS* and Table 5.1.3.1-3 to determine the modulation order (*Qm*) and Target code rate (*R*) used in the physical downlink shared channel. + +elseif the UE is not configured with MCS-C-RNTI, the higher layer parameter *mcs-Table* given by *PDSCH-Config* is set to 'qam64LowSE', and the PDSCH is scheduled by a PDCCH with a DCI format other than DCI format 1\_2 in a UE-specific search space with CRC scrambled by C-RNTI + +- the UE shall use *IMCS* and Table 5.1.3.1-3 to determine the modulation order (*Qm*) and Target code rate (*R*) used in the physical downlink shared channel. + +elseif the UE is configured with MCS-C-RNTI, and the PDSCH is scheduled by a PDCCH with CRC scrambled by MCS-C-RNTI + +- the UE shall use *IMCS* and Table 5.1.3.1-3 to determine the modulation order (*Qm*) and Target code rate (*R*) used in the physical downlink shared channel. + +elseif the UE is not configured with the higher layer parameter *mcs-Table* given by *SPS-config*, and the higher layer parameter *mcs-Table-r17* given by *PDSCH-Config* is set to 'qam1024', + +- if the PDSCH is scheduled by a PDCCH with DCI format 1\_1 with CRC scrambled by CS-RNTI or +- if the PDSCH with SPS activated by DCI format 1\_1 is scheduled without corresponding PDCCH transmission using *SPS-Config*, +- the UE shall use *IMCS* and Table 5.1.3.1-4 to determine the modulation order (*Qm*) and Target code rate (*R*) used in the physical downlink shared channel. + +elseif the UE is not configured with the higher layer parameter *mcs-Table* given by *SPS-config*, and the higher layer parameter *mcs-TableDCI-1-2-r17* given by *PDSCH-Config* is set to 'qam1024', + +- if the PDSCH is scheduled by a PDCCH with DCI format 1\_2 with CRC scrambled by CS-RNTI or +- if the PDSCH with SPS activated by DCI format 1\_2 is scheduled without corresponding PDCCH transmission using *SPS-Config*, + - the UE shall use $I_{MCS}$ and Table 5.1.3.1-4 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical downlink shared channel. + +elseif the UE is not configured with the higher layer parameter *mcs-Table* given by *SPS-config*, and the higher layer parameter *mcs-TableDCI-1-2* given by *PDSCH-Config* is set to 'qam256', + +- if the PDSCH is scheduled by a PDCCH with DCI format 1\_2 with CRC scrambled by CS-RNTI or +- if the PDSCH with SPS activated by DCI format 1\_2 is scheduled without corresponding PDCCH transmission using *SPS-Config*, + - the UE shall use $I_{MCS}$ and Table 5.1.3.1-2 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical downlink shared channel. + +elseif the UE is not configured with the higher layer parameter *mcs-Table* given by *SPS-Config*, and the higher layer parameter *mcs-Table* given by *PDSCH-Config* is set to 'qam256', + +- if the PDSCH is scheduled by a PDCCH with DCI format 1\_1 with CRC scrambled by CS-RNTI or +- if the PDSCH with SPS activated by DCI format 1\_1 is scheduled without corresponding PDCCH transmission using *SPS-Config*, + - the UE shall use $I_{MCS}$ and Table 5.1.3.1-2 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical downlink shared channel. + +elseif the UE is configured with the higher layer parameter *mcs-Table* given by *SPS-Config* set to 'qam64LowSE' + +- if the PDSCH is scheduled by a PDCCH with CRC scrambled by CS-RNTI or +- if the PDSCH is scheduled without corresponding PDCCH transmission using *SPS-Config*, + - the UE shall use $I_{MCS}$ and Table 5.1.3.1-3 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical downlink shared channel. + +elseif the UE is configured with the higher layer parameter *mcs-Table* given by *SPS-Config* or *mcs-Table* of *pdsch-ConfigMulticast* in the same *CFR-ConfigMulticast* set to 'qam64LowSE' + +- if the GC-PDSCH is scheduled by a GC-PDCCH with CRC scrambled by G-CS-RNTI or +- if the GC-PDSCH is scheduled without corresponding GC-PDCCH transmission using *SPS-Config*, + - the UE shall use $I_{MCS}$ and Table 5.1.3.1-3 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical downlink shared channel. + +else + +- the UE shall use $I_{MCS}$ and Table 5.1.3.1-1 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical downlink shared channel. + +end + +The UE is not expected to decode a PDSCH scheduled with P-RNTI, RA-RNTI, SI-RNTI and $Q_m > 2$ + +For a UE configured with the higher layer parameter *repetitionScheme* set to 'fdmSchemeB', and when the UE not configured with *dl-OrJointTCI-StateList* is indicated with two TCI states in a codepoint of the DCI field '*Transmission Configuration Indication*', or when the UE configured with *dl-OrJointTCI-StateList* and having two indicated TCI States to be applied to PDSCH, and the UE is indicated with DM-RS port(s) within one CDM group in the DCI field '*Antenna Port(s)*', the determined modulation order of PDSCH transmission occasion associated with the first TCI state is applied to the PDSCH transmission occasion associated with the second TCI state. + +**Table 5.1.3.1-1: MCS index table 1 for PDSCH** + +| MCS Index
$I_{MCS}$ | Modulation Order
$Q_m$ | Target code Rate R \times [1024] | Spectral efficiency | +|-------------------------------|----------------------------------|------------------------------------------------------|----------------------------| +| 0 | 2 | 120 | 0.2344 | +| 1 | 2 | 157 | 0.3066 | +| 2 | 2 | 193 | 0.3770 | +| 3 | 2 | 251 | 0.4902 | +| 4 | 2 | 308 | 0.6016 | +| 5 | 2 | 379 | 0.7402 | +| 6 | 2 | 449 | 0.8770 | +| 7 | 2 | 526 | 1.0273 | +| 8 | 2 | 602 | 1.1758 | +| 9 | 2 | 679 | 1.3262 | +| 10 | 4 | 340 | 1.3281 | +| 11 | 4 | 378 | 1.4766 | +| 12 | 4 | 434 | 1.6953 | +| 13 | 4 | 490 | 1.9141 | +| 14 | 4 | 553 | 2.1602 | +| 15 | 4 | 616 | 2.4063 | +| 16 | 4 | 658 | 2.5703 | +| 17 | 6 | 438 | 2.5664 | +| 18 | 6 | 466 | 2.7305 | +| 19 | 6 | 517 | 3.0293 | +| 20 | 6 | 567 | 3.3223 | +| 21 | 6 | 616 | 3.6094 | +| 22 | 6 | 666 | 3.9023 | +| 23 | 6 | 719 | 4.2129 | +| 24 | 6 | 772 | 4.5234 | +| 25 | 6 | 822 | 4.8164 | +| 26 | 6 | 873 | 5.1152 | +| 27 | 6 | 910 | 5.3320 | +| 28 | 6 | 948 | 5.5547 | +| 29 | 2 | reserved | | +| 30 | 4 | reserved | | +| 31 | 6 | reserved | | + +**Table 5.1.3.1-2: MCS index table 2 for PDSCH** + +| MCS Index
$I_{MCS}$ | Modulation Order
$Q_m$ | Target code Rate R \times [1024] | Spectral efficiency | +|-------------------------------|----------------------------------|------------------------------------------------------|----------------------------| +| 0 | 2 | 120 | 0.2344 | +| 1 | 2 | 193 | 0.3770 | +| 2 | 2 | 308 | 0.6016 | +| 3 | 2 | 449 | 0.8770 | +| 4 | 2 | 602 | 1.1758 | +| 5 | 4 | 378 | 1.4766 | +| 6 | 4 | 434 | 1.6953 | +| 7 | 4 | 490 | 1.9141 | +| 8 | 4 | 553 | 2.1602 | +| 9 | 4 | 616 | 2.4063 | +| 10 | 4 | 658 | 2.5703 | +| 11 | 6 | 466 | 2.7305 | +| 12 | 6 | 517 | 3.0293 | +| 13 | 6 | 567 | 3.3223 | +| 14 | 6 | 616 | 3.6094 | +| 15 | 6 | 666 | 3.9023 | +| 16 | 6 | 719 | 4.2129 | +| 17 | 6 | 772 | 4.5234 | +| 18 | 6 | 822 | 4.8164 | +| 19 | 6 | 873 | 5.1152 | +| 20 | 8 | 682.5 | 5.3320 | +| 21 | 8 | 711 | 5.5547 | +| 22 | 8 | 754 | 5.8906 | +| 23 | 8 | 797 | 6.2266 | +| 24 | 8 | 841 | 6.5703 | +| 25 | 8 | 885 | 6.9141 | +| 26 | 8 | 916.5 | 7.1602 | +| 27 | 8 | 948 | 7.4063 | +| 28 | 2 | reserved | | +| 29 | 4 | reserved | | +| 30 | 6 | reserved | | +| 31 | 8 | reserved | | + +**Table 5.1.3.1-3: MCS index table 3 for PDSCH** + +| MCS Index
$I_{MCS}$ | Modulation Order
$Q_m$ | Target code Rate R \times [1024] | Spectral efficiency | +|-------------------------------|----------------------------------|------------------------------------------------------|----------------------------| +| 0 | 2 | 30 | 0.0586 | +| 1 | 2 | 40 | 0.0781 | +| 2 | 2 | 50 | 0.0977 | +| 3 | 2 | 64 | 0.1250 | +| 4 | 2 | 78 | 0.1523 | +| 5 | 2 | 99 | 0.1934 | +| 6 | 2 | 120 | 0.2344 | +| 7 | 2 | 157 | 0.3066 | +| 8 | 2 | 193 | 0.3770 | +| 9 | 2 | 251 | 0.4902 | +| 10 | 2 | 308 | 0.6016 | +| 11 | 2 | 379 | 0.7402 | +| 12 | 2 | 449 | 0.8770 | +| 13 | 2 | 526 | 1.0273 | +| 14 | 2 | 602 | 1.1758 | +| 15 | 4 | 340 | 1.3281 | +| 16 | 4 | 378 | 1.4766 | +| 17 | 4 | 434 | 1.6953 | +| 18 | 4 | 490 | 1.9141 | +| 19 | 4 | 553 | 2.1602 | +| 20 | 4 | 616 | 2.4063 | +| 21 | 6 | 438 | 2.5664 | +| 22 | 6 | 466 | 2.7305 | +| 23 | 6 | 517 | 3.0293 | +| 24 | 6 | 567 | 3.3223 | +| 25 | 6 | 616 | 3.6094 | +| 26 | 6 | 666 | 3.9023 | +| 27 | 6 | 719 | 4.2129 | +| 28 | 6 | 772 | 4.5234 | +| 29 | 2 | reserved | | +| 30 | 4 | reserved | | +| 31 | 6 | reserved | | + +**Table 5.1.3.1-4: MCS index table 4 for PDSCH** + +| MCS Index
$I_{MCS}$ | Modulation Order
$Q_m$ | Target code Rate R \times [1024] | Spectral efficiency | +|-------------------------------|----------------------------------|------------------------------------------------------|----------------------------| +| 0 | 2 | 120 | 0.2344 | +| 1 | 2 | 193 | 0.3770 | +| 2 | 2 | 449 | 0.8770 | +| 3 | 4 | 378 | 1.4766 | +| 4 | 4 | 490 | 1.9141 | +| 5 | 4 | 616 | 2.4063 | +| 6 | 6 | 466 | 2.7305 | +| 7 | 6 | 517 | 3.0293 | +| 8 | 6 | 567 | 3.3223 | +| 9 | 6 | 616 | 3.6094 | +| 10 | 6 | 666 | 3.9023 | +| 11 | 6 | 719 | 4.2129 | +| 12 | 6 | 772 | 4.5234 | +| 13 | 6 | 822 | 4.8164 | +| 14 | 6 | 873 | 5.1152 | +| 15 | 8 | 682.5 | 5.3320 | +| 16 | 8 | 711 | 5.5547 | +| 17 | 8 | 754 | 5.8906 | +| 18 | 8 | 797 | 6.2266 | +| 19 | 8 | 841 | 6.5703 | +| 20 | 8 | 885 | 6.9141 | +| 21 | 8 | 916.5 | 7.1602 | +| 22 | 8 | 948 | 7.4063 | +| 23 | 10 | 805.5 | 7.8662 | +| 24 | 10 | 853 | 8.3301 | +| 25 | 10 | 900.5 | 8.7939 | +| 26 | 10 | 948 | 9.2578 | +| 27 | 2 | reserved | | +| 28 | 4 | reserved | | +| 29 | 6 | reserved | | +| 30 | 8 | reserved | | +| 31 | 10 | reserved | | + +#### 5.1.3.2 Transport block size determination + +In case the higher layer parameter *maxNrofCodeWordsScheduledByDCI* in *PDSCH-config* indicates that two codeword transmission is enabled, then one of the two transport blocks is disabled by DCI format 1\_1 or 1\_3 if $I_{MCS} = 26$ and if $rv_{id} = 1$ for the corresponding transport block. In case the higher layer parameter *maxNrofCodeWordsScheduledByDCI* in *pdsch-ConfigMulticast* indicates that two codeword transmission is enabled, then one of the two transport blocks is disabled by DCI format 4\_2 if $I_{MCS} = 26$ and if $rv_{id} = 1$ for the corresponding transport block. When the UE is configured with higher layer parameter *pdsch-TimeDomainAllocationListForMultiPDSCH*, either the first or the second transport block of all scheduled PDSCHs is disabled by the DCI format 1\_1 if $I_{MCS} = 26$ and if $rv_{id} = 2$ for the corresponding transport block of all scheduled PDSCHs. If both transport blocks are enabled, transport block 1 and 2 are mapped to codeword 0 and 1 respectively. If only one transport block is enabled, then the enabled transport block is always mapped to the first codeword. + +For the PDSCH assigned by a PDCCH with DCI format 1\_0, 1\_1, 1\_2, 1\_3, 4\_0, 4\_1, or 4\_2 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, G-RNTI, G-CS-RNTI, MCCH-RNTI, multicast-MCCH-RNTI or SI-RNTI, if Table 5.1.3.1-2 is used and , else if Table 5.1.3.1-4 is used and or a table other than Table 5.1.3.1-2 and Table 5.1.3.1-4 is used and , the UE shall, except if the transport block is disabled in DCI format 1\_1 or 1\_3, first determine the TBS as specified below: + +1) The UE shall first determine the number of REs ( $N_{RE}$ ) within the slot. + +- A UE first determines the number of REs allocated for PDSCH within a PRB ( $n_{PRB}$ ) by , where $n_{PRB}$ is the number of subcarriers in a physical resource block, $n_{symbols}$ is the number of symbols of the PDSCH allocation within the slot, $n_{DMRS}$ is the number of REs for DM-RS per PRB in the scheduled duration including the overhead of the DM-RS CDM groups without data, as indicated by DCI format 1\_1, 1\_2 or 1\_3 or as described for format 1\_0 in Clause 5.1.6.2, and $x_{overhead}$ is the overhead configured by higher layer parameter *xOverhead* in *PDSCH-* + +*ServingCellConfig*. If the *xOverhead* in *PDSCH-ServingCellConfig* is not configured (a value from 6, 12, or 18), the is set to 0. If the PDSCH is scheduled by PDCCH with a CRC scrambled by SI-RNTI, RA-RNTI, MSGB-RNTI or P-RNTI, is assumed to be 0. If the PDSCH is scheduled by PDCCH with a CRC scrambled by G-RNTI for multicast or G-CS-RNTI or PDSCH without PDCCH is activated by PDCCH with a CRC scrambled by G-CS-RNTI, is the overhead configured by higher layer parameter *xOverhead-Multicast* in *pdsch-ConfigMulticast*. If the *xOverhead-Multicast* in *pdsch-ConfigMulticast* is not configured, the is set to 0. If the PDSCH is scheduled by PDCCH with a CRC scrambled by G-RNTI for broadcast or MCCH-RNTI, is the overhead configured by higher layer parameter *xOverhead* in *pdsch-ConfigBroadcast*. If the *xOverhead* in *pdsch-ConfigBroadcast* is not configured, the is set to 0. + +- A UE determines the total number of REs allocated for PDSCH () by $N_{RE} = \min(156, N_{RE}^i) \cdot n_{PRB}$ , where $n_{PRB}$ is the total number of allocated PRBs for the UE. + +2) Unquantized intermediate variable ( $N_{info}$ ) is obtained by . + +If + +Use step 3 as the next step of the TBS determination + +else + +Use step 4 as the next step of the TBS determination + +end if + +3) When , TBS is determined as follows + +- quantized intermediate number of information bits , where . +- use Table 5.1.3.2-1 find the closest TBS that is not less than . + +**Table 5.1.3.2-1: TBS for** + +| Index | TBS | Index | TBS | Index | TBS | Index | TBS | +|-------|-----|-------|------|-------|------|-------|------| +| 1 | 24 | 31 | 336 | 61 | 1288 | 91 | 3624 | +| 2 | 32 | 32 | 352 | 62 | 1320 | 92 | 3752 | +| 3 | 40 | 33 | 368 | 63 | 1352 | 93 | 3824 | +| 4 | 48 | 34 | 384 | 64 | 1416 | | | +| 5 | 56 | 35 | 408 | 65 | 1480 | | | +| 6 | 64 | 36 | 432 | 66 | 1544 | | | +| 7 | 72 | 37 | 456 | 67 | 1608 | | | +| 8 | 80 | 38 | 480 | 68 | 1672 | | | +| 9 | 88 | 39 | 504 | 69 | 1736 | | | +| 10 | 96 | 40 | 528 | 70 | 1800 | | | +| 11 | 104 | 41 | 552 | 71 | 1864 | | | +| 12 | 112 | 42 | 576 | 72 | 1928 | | | +| 13 | 120 | 43 | 608 | 73 | 2024 | | | +| 14 | 128 | 44 | 640 | 74 | 2088 | | | +| 15 | 136 | 45 | 672 | 75 | 2152 | | | +| 16 | 144 | 46 | 704 | 76 | 2216 | | | +| 17 | 152 | 47 | 736 | 77 | 2280 | | | +| 18 | 160 | 48 | 768 | 78 | 2408 | | | +| 19 | 168 | 49 | 808 | 79 | 2472 | | | +| 20 | 176 | 50 | 848 | 80 | 2536 | | | +| 21 | 184 | 51 | 888 | 81 | 2600 | | | +| 22 | 192 | 52 | 928 | 82 | 2664 | | | +| 23 | 208 | 53 | 984 | 83 | 2728 | | | +| 24 | 224 | 54 | 1032 | 84 | 2792 | | | +| 25 | 240 | 55 | 1064 | 85 | 2856 | | | +| 26 | 256 | 56 | 1128 | 86 | 2976 | | | +| 27 | 272 | 57 | 1160 | 87 | 3104 | | | +| 28 | 288 | 58 | 1192 | 88 | 3240 | | | +| 29 | 304 | 59 | 1224 | 89 | 3368 | | | +| 30 | 320 | 60 | 1256 | 90 | 3496 | | | + +4) When , TBS is determined as follows. + +- $$N'_{\text{info}} = \max \left( 3840, 2^n \times \text{round} \left( \frac{N_{\text{info}} - 24}{2^n} \right) \right)$$ +- quantized intermediate number of information bits and ties in the round function are broken towards the next largest integer. + - if + - , where + - else + - if + - , where + - else + - end if + - end if + - else if Table 5.1.3.1-2 is used and , + - the TBS is assumed to be as determined from the DCI transported in the latest PDCCH for the same transport block using . If there is no PDCCH for the same transport block using , and if the initial PDSCH for the same transport block is semi-persistently scheduled, the TBS shall be determined from the most recent semi-persistent scheduling assignment PDCCH. + - else if Table 5.1.3.1-4 is used and , + - the TBS is assumed to be as determined from the DCI transported in the latest PDCCH for the same transport block using . If there is no PDCCH for the same transport block using , and if the initial PDSCH for the same transport block is semi-persistently scheduled, the TBS shall be determined from the most recent semi-persistent scheduling assignment PDCCH. + - else + - the TBS is assumed to be as determined from the DCI transported in the latest PDCCH for the same transport block using . If there is no PDCCH for the same transport block using, and if the initial PDSCH for the same transport block is semi-persistently scheduled, the TBS shall be determined from the most recent semi-persistent scheduling assignment PDCCH. + +The UE is not expected to receive a PDSCH assigned by a PDCCH with CRC scrambled by SI-RNTI with a TBS exceeding 2976 bits. + +For a UE configured with the higher layer parameter *repetitionScheme* set to 'fdmSchemeB', and when the UE not configured with *dl-OrJointTCI-StateList* is indicated with two TCI states in a codepoint of the DCI field '*Transmission Configuration Indication*', or when the UE configured with *dl-OrJointTCI-StateList* and having two indicated TCI States to be applied to PDSCH, and the UE is indicated with DM-RS port(s) within one CDM group in the DCI field '*Antenna Port(s)*', the TBS determination follows the steps 1-4 with the following modification in step 1: a UE + +determines the total number of REs allocated for PDSCH () by $N_{RE} = \min(156, N'_{RE}) \cdot n_{PRB}$ , where $n_{PRB}$ is the total number of allocated PRBs corresponding to the first TCI state, and the determined TBS of PDSCH transmission occasion associated with the first TCI state is also applied to the PDSCH transmission occasion associated with the second TCI state. For a UE configured with the higher layer parameter *repetitionScheme* set to 'tdmSchemeA' and indicated with two TCI states in a codepoint of the DCI field '*Transmission Configuration Indication*' for the UE not configured with *dl-OrJointTCI-StateList* or for the UE configured with *dl-OrJointTCI-StateList* and having two indicated TCI States to be applied to PDSCH and indicated with DM-RS port(s) within one CDM group in the DCI field '*Antenna Port(s)*', the TBS determination follows the steps 1-4 with the following modification in step 1: a UE + +determines the number of REs allocated for PDSCH within a PRB $\nu$ by $\nu$ , where $\nu$ is the number of symbols of the PDSCH allocation within the slot corresponding to the first TCI state, and the determined TBS of PDSCH transmission occasion associated with the first TCI state is also applied to the PDSCH transmission occasion associated with the second TCI state. + +For the PDSCH assigned by a PDCCH with DCI format 1\_0 with CRC scrambled by P-RNTI, or RA-RNTI, MsgB-RNTI, TBS determination follows the steps 1-4 with the following modification in step 2: a scaling + +$N_{info} = S \cdot N_{RE} \cdot R \cdot Q_m \cdot \nu$ is applied in the calculation of $N_{info}$ , where the scaling factor is determined based on the *TB scaling* field in the DCI as in Table 5.1.3.2-2. + +**Table 5.1.3.2-2: Scaling factor of $N_{info}$ for P-RNTI, RA-RNTI and MSGB-RNTI** + +| TB scaling field | Scaling factor S | +|------------------|------------------| +| 00 | 1 | +| 01 | 0.5 | +| 10 | 0.25 | +| 11 | | + +The NDI and HARQ process ID, as signalled on PDCCH, and the TBS, as determined above, shall be reported to higher layers. + +### 5.1.4 PDSCH resource mapping + +When receiving the PDSCH scheduled with SI-RNTI and the system information indicator in DCI is set to 0, the UE shall assume that no SS/PBCH block is transmitted in REs used by the UE for a reception of the PDSCH. + +When receiving the PDSCH scheduled with SI-RNTI and the system information indicator in DCI is set to 1, RA-RNTI, MSGB-RNTI, P-RNTI or TC-RNTI, the UE assumes SS/PBCH block transmission according to *ssb-PositionsInBurst*, and if the PDSCH resource allocation overlaps with PRBs containing SS/PBCH block transmission resources the UE shall assume that the PRBs containing SS/PBCH block transmission resources are not available for PDSCH in the OFDM symbols where SS/PBCH block is transmitted. + +A UE expects a configuration provided by *ssb-PositionsInBurst* in *ServingCellConfigCommon* to be same as a configuration provided by *ssb-PositionsInBurst* in *SIB1*. + +When receiving PDSCH scheduled by PDCCH with CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI, G-RNTI, G-CS-RNTI, MCCH-RNTI, multicast-MCCH-RNTI or PDSCHs with SPS, the REs corresponding to the configured or dynamically indicated resources in Clauses 5.1.4.1, 5.1.4.2 are not available for PDSCH. Furthermore, the UE assumes SS/PBCH block transmission according to *ssb-PositionsInBurst* if the PDSCH resource allocation overlaps with PRBs containing SS/PBCH block transmission resources, and the UE shall assume that the PRBs containing SS/PBCH block transmission resources are not available for PDSCH in the OFDM symbols where SS/PBCH block associated with the same PCI is transmitted. + +A UE is not expected to handle the case where PDSCH DM-RS REs are overlapping, even partially, with any RE(s) not available for PDSCH. + +For operation with shared spectrum channel access, SS/PBCH block transmission according to *ssb-PositionsInBurst* represents all of the candidate SS/PBCH blocks corresponding to SS/PBCH block indices provided by *ssb-PositionsInBurst* as described in Clause 4.1 of [6, TS 38.213]. + +#### 5.1.4.1 PDSCH resource mapping with RB symbol level granularity + +The procedures for PDSCH scheduled by PDCCH with DCI format 1\_1 described in this clause equally apply to PDSCH scheduled by PDCCH with DCI format 1\_2, by applying only the parameters of *rateMatchPatternGroup1DCI-1-2*, *rateMatchPatternGroup2DCI-1-2* instead of *rateMatchPatternGroup1* and *rateMatchPatternGroup2*. The procedures for PDSCH scheduled by PDCCH with DCI format 1\_1 described in this clause equally apply to PDSCH scheduled by PDCCH with DCI format 1\_3. The procedures for PDSCH scheduled by PDCCH with DCI format 1\_0 described in this clause equally apply to PDSCH scheduled by PDCCH with DCI format 4\_0, by applying only the parameters of *rateMatchPatternToAddModList* configured in *pdsch-ConfigMCCH* or *pdsch-ConfigMTCH*. + +The procedures for PDSCH scheduled by PDCCH with DCI format 1\_0 described in this clause equally apply to PDSCH scheduled by PDCCH with DCI format 4\_1, and the procedures for PDSCH scheduled by DCI format 1\_1 + +described in this clause equally apply to PDSCH scheduled by PDCCH with DCI format 4\_2 by applying only the parameters of *rateMatchPatternToAddModList*, *rateMatchPatternGroup1* and *rateMatchPatternGroup2* configured in *pdsc-ConfigMulticast*. + +A UE may be configured with any of the following higher layer parameters indicating REs declared as not available for PDSCH: + +- *rateMatchPatternToAddModList* given by *PDSCH-Config*, by *pdsc-ConfigMulticast*, by *ServingCellConfig* or by *ServingCellConfigCommon*, or by *pdsc-ConfigMCCH* or *pdsc-ConfigMTCH* and configuring up to 4 *RateMatchPattern(s)* per BWP and up to 4 *RateMatchPattern(s)* per serving-cell. The *RateMatchPatterns* configured for MBS multicast are counted into the ones that are configured per BWP. The *RateMatchPattern(s)* configured for MBS broadcast or for MBS multicast in *RRC\_INACTIVE\_state* is counted into the ones that are configured per serving-cell. A *RateMatchPattern* may contain: + - within a BWP, when provided by *PDSCH-Config* or *pdsc-ConfigMulticast* or within a serving cell when provided by *ServingCellConfig* or *ServingCellConfigCommon*, or by *pdsc-ConfigMCCH* or *pdsc-ConfigMTCH*, a pair of reserved resources with numerology provided by higher layer parameter *subcarrierSpacing* given by *RateMatchPattern* when configured per serving cell or by numerology of associated BWP when configured per BWP. The pair of reserved resources are respectively indicated by an RB level bitmap (higher layer parameter *resourceBlocks* given by *RateMatchPattern*) with 1RB granularity and a symbol level bitmap spanning one or two slots (higher layer parameters *symbolsInResourceBlock* given by *RateMatchPattern*) for which the reserved RBs apply. A bit value equal to 1 in the RB and symbol level bitmaps indicates that the corresponding resource is not available for PDSCH. For each pair of RB and symbol level bitmaps, a UE may be configured with a time-domain pattern (higher layer parameter *periodicityAndPattern* given by *RateMatchPattern*), where each bit of *periodicityAndPattern* corresponds to a unit equal to a duration of the symbol level bitmap, and a bit value equal to 1 indicates that the pair is present in the unit. The *periodicityAndPattern* can be {1, 2, 4, 5, 8, 10, 20 or 40} units long, but maximum of 40 msec. The first symbol of *periodicityAndPattern* every 40 msec/P periods is a first symbol in frame mod 4 = 0, where P is the duration of *periodicityAndPattern* in units of msec. When *periodicityAndPattern* is not configured for a pair, for a symbol level bitmap spanning two slots, the bits of the first and second slots correspond respectively to even and odd slots of a radio frame, and for a symbol level bitmap spanning one slot, the bits of the slot correspond to every slot of a radio frame. The pair can be included in one or two groups of resource sets (higher layer parameters *rateMatchPatternGroup1* and *rateMatchPatternGroup2*). The *rateMatchPatternToAddModList* given by *ServingCellConfig* or *ServingCellConfigCommon* configuration in numerology $\mu$ applies only to PDSCH of the same numerology $\mu$ . + - within a BWP, a frequency domain resource of a CORESET configured by *ControlResourceSet* with *controlResourceSetId* or *ControlResourceSetZero* and time domain resource determined by the higher layer parameters *monitoringSlotPeriodicityAndOffset*, *duration* and *monitoringSymbolsWithinSlot* of all search-space-sets configured by *SearchSpace* and time domain resource of search-space-set zero configured by *searchSpaceZero* associated with the CORESET as well as CORESET duration configured by *ControlResourceSet* with *controlResourceSetId* or *ControlResourceSetZero*. This resource not available for PDSCH can be included in one or two groups of resource sets (higher layer parameters *rateMatchPatternGroup1* and *rateMatchPatternGroup2*). + +A configured group *rateMatchPatternGroup1* or *rateMatchPatternGroup2* contains a list of indices of *RateMatchPattern(s)* forming a union of resource-sets not available for a PDSCH dynamically if a corresponding bit of the 'Rate matching indicator' field of the DCI format 1\_1 scheduling the PDSCH is equal to 1. The REs corresponding to the union of resource-sets configured by *RateMatchPattern(s)* that are not included in either of the two groups are not available for a PDSCH scheduled by a DCI format 1\_0, a PDSCH scheduled by a DCI format 1\_1, and PDSCHs with SPS. When receiving a PDSCH scheduled by a DCI format 1\_0 or PDSCHs with SPS activated by a DCI format 1\_0, the REs corresponding to configured resources in *rateMatchPatternGroup1* or *rateMatchPatternGroup2* are not available for the scheduled PDSCH or the activated PDSCHs with SPS. When receiving PDSCHs with SPS activated by a DCI format 1\_1, the REs corresponding to configured resources in *rateMatchPatternGroup1* or *rateMatchPatternGroup2* are not available for the PDSCHs with SPS if a corresponding bit of the Rate matching indicator field of the DCI format 1\_1 activating the PDSCHs with SPS is equal to 1. + +For a bitmap pair included in one or two groups of resource sets, the dynamic indication of availability for PDSCH applies to a set of slot(s) where the *rateMatchPatternToAddModList* is present among the slots of scheduled PDSCH. + +If a UE monitors PDCCH candidates of aggregation levels 8 and 16 with the same starting CCE index in non-interleaved CORESET spanning one OFDM symbol: + +- and if a detected PDCCH scheduling the PDSCH has aggregation level 8, the resources corresponding to the aggregation level 16 PDCCH candidate are not available for the PDSCH; +- when at least one of the PDCCH candidates of aggregation levels 8 and 16 linked as indicated by higher layer parameter *searchSpaceLinkingId*, the PDCCH candidates of aggregation level 16 and any other PDCCH candidate(s) linked with any of the PDCCH candidates of aggregation level 8 and 16 are not available for the PDSCH reception at the UE, if a detected PDCCH scheduling the PDSCH is associated with the PDCCH candidates of aggregation level 8 or 16. + +If a PDSCH scheduled by a PDCCH would overlap with resources in the CORESET containing the PDCCH, the resources corresponding to a union of the detected PDCCH that scheduled the PDSCH and associated PDCCH DM-RS are not available for the PDSCH. When the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], the resources corresponding to a union of the two PDCCH candidates scheduling the PDSCH and the associated PDCCH DM-RS are not available for the PDSCH. When *precoderGranularity* configured in a CORESET where the PDCCH was detected is set to 'allContiguousRBs', the associated PDCCH DM-RS are DM-RS in all REGs of the CORESET. Otherwise, the associated DM-RS are the DM-RS in REGs of the PDCCH. + +#### 5.1.4.2 PDSCH resource mapping with RE level granularity + +The procedures for PDSCH scheduled by PDCCH with DCI format 1\_1 described in this clause equally apply to PDSCH scheduled by PDCCH with DCI format 1\_2, by applying the parameters of *aperiodicZP-CSI-RS-ResourceSetsToAddModListDCI-1-2* instead of *aperiodic-ZP-CSI-RS-ResourceSetsToAddModList*. The procedures for PDSCH scheduled by PDCCH with DCI format 1\_1 described in this clause equally apply to PDSCH scheduled by PDCCH with DCI format 1\_3. + +The procedures for PDSCH scheduled by PDCCH with DCI format 1\_0 described in this clause equally apply to PDSCH scheduled by PDCCH with DCI format 4\_1 and the procedures for PDSCH scheduled by PDCCH with DCI format 1\_1 described in this clause equally apply to PDSCH scheduled by PDCCH with DCI format 4\_2, by applying the parameters of *aperiodicZP-CSI-RS-ResourceSetsToAddModList in pdsch-ConfigMulticast* instead of *aperiodic-ZP-CSI-RS-ResourceSetsToAddModList in PDSCH-Config*. + +A UE may be configured with any of the following higher layer parameters: + +- REs indicated by the '*RateMatchPatternLTE-CRS*' in *lte-CRS-ToMatchAround* in *ServingCellConfig* or *ServingCellConfigCommon* configuring cell-specific RS, in 15 kHz subcarrier spacing applicable only to 15 kHz subcarrier spacing PDSCH, of one LTE carrier in a serving cell are declared as not available for PDSCH. +- REs indicated by '*RateMatchPatternLTE-CRS*' in *lte-CRS-PatternList1-r16* or *lte-CRS-PatternList3-r18* in *ServingCellConfig* configuring cell-specific RS, in 15 kHz subcarrier spacing applicable only to 15 kHz subcarrier spacing PDSCH, of one LTE carrier in a serving cell are declared as not available for PDSCH. +- For the UE for broadcast reception or multicast reception in RRC\_INACTIVE\_state, REs indicated by '*RateMatchPatternLTE-CRS*' in *pdsch-ConfigMCCH* or *pdsch-ConfigMTCH* configuring cell-specific RS, in 15 kHz subcarrier spacing applicable only to 15 kHz subcarrier spacing PDSCH, of one LTE carrier in a serving cell are declared as not available for broadcast PDSCH. The total number of *RateMatchPatternLTE-CRS* for broadcast reception or multicast reception in RRC\_INACTIVE\_state that a UE can be configured with is the same as for unicast in Rel-15. +- Each *RateMatchPatternLTE-CRS* configuration contains *v-Shift* consisting of LTE-CRS-vshift(s), *nrofCRS-Ports* consisting of LTE-CRS antenna ports 1, 2 or 4 ports, *carrierFreqDL* representing the offset in units of 15 kHz subcarriers from (reference) point A to the LTE carrier centre subcarrier location, *carrierBandwidthDL* representing the LTE carrier bandwidth, and may also configure *mbsfn-SubframeConfigList* representing MBSFN subframe configuration. A UE determines the CRS position within the slot according to Clause 6.10.1.2 in [15, TS 36.211], where slot corresponds to LTE subframe. +- If the UE is configured by higher layer parameter *PDCCH-Config* with two different values of *coresetPoolIndex* in *ControlResourceSet* and is also configured by the higher layer parameter *lte-CRS-PatternList1-r16* and *lte-CRS-PatternList2-r16* in *ServingCellConfig*, the following REs are declared as not available for PDSCH: + - if the UE is configured with *crs-RateMatch-PerCoresetPoolIndex*, REs indicated by the CRS pattern(s) in *lte-CRS-PatternList1-r16* if the PDSCH is associated with *coresetPoolIndex* set to '0', or the CRS pattern(s) in *lte-CRS-PatternList2-r16* if PDSCH is associated with *coresetPoolIndex* set to '1'; + +- otherwise, REs indicated by *lte-CRS-PatternList1-r16* and *lte-CRS-PatternList2-r16*, in *ServingCellConfig*. +- If the UE is not configured by higher layer parameter *PDCCH-Config* with two different values of *coresetPoolIndex* in *ControlResourceSet*, and if the UE is configured by higher layer parameter *lte-CRS-PatternList3-r18* and *lte-CRS-PatternList4-r18* in *ServingCellConfig*, REs indicated by *lte-CRS-PatternList3-r18* and *lte-CRS-PatternList4-r18* are declared as not available for PDSCH. +- If the UE is configured by higher layer parameter *PDCCH-Config* with two different values of *coresetPoolIndex* in *ControlResourceSet* and is also configured by the higher layer parameter *lte-CRS-PatternList3-r18* and *lte-CRS-PatternList4-r18* in *ServingCellConfig*, the following REs are declared as not available for PDSCH: + - if the UE is configured with *crs-RateMatch-PerCoresetPoolIndex*, REs indicated by the CRS pattern(s) in *lte-CRS-PatternList3-r18* if the PDSCH is associated with *coresetPoolIndex* set to '0', or the CRS pattern(s) in *lte-CRS-PatternList4-r18* if PDSCH is associated with *coresetPoolIndex* set to '1'; + - otherwise, REs indicated by *lte-CRS-PatternList3-r18* and *lte-CRS-PatternList4-r18*, in *ServingCellConfig*. +- Within a BWP, the UE can be configured with one or more ZP CSI-RS resource set configuration(s) for aperiodic, semi-persistent and periodic time-domain behaviours (higher layer parameters *aperiodic-ZP-CSI-RS-ResourceSetsToAddModList*, *sp-ZP-CSI-RS-ResourceSetsToAddModList* and *p-ZP-CSI-RS-ResourceSet* respectively comprised in *PDSCH-Config*), with each ZP CSI-RS resource set consisting of at most 16 ZP CSI-RS resources (higher layer parameter *ZP-CSI-RS-Resource*) in numerology of the BWP. The REs indicated by *p-ZP-CSI-RS-ResourceSet* are declared as not available for PDSCH. The REs indicated by *sp-ZP-CSI-RS-ResourceSetsToAddModList* and *aperiodic-ZP-CSI-RS-ResourceSetsToAddModList* are declared as not available for PDSCH when their triggering and activation are applied, respectively. The following parameters are configured via higher layer signaling for each ZP CSI-RS resource configuration: + - *zp-CSI-RS-ResourceId* in *ZP-CSI-RS-Resource* determines ZP CSI-RS resource configuration identity. + - *nrofPorts* in *CSI-RS-ResourceMapping* defines the number of CSI-RS ports, where the allowable values are given in Clause 7.4.1.5 of [4, TS 38.211]. + - *cdm-Type* in *CSI-RS-ResourceMapping* defines CDM values and pattern, where the allowable values are given in Clause 7.4.1.5 of [4, TS 38.211]. + - *resourceMapping* in *ZP-CSI-RS-Resource* defines the OFDM symbol and subcarrier occupancy of the ZP CSI-RS resource within a slot that are given in Clause 7.4.1.5 of [4, TS 38.211]. + - *periodicityAndOffset* in *ZP-CSI-RS-Resource* defines the ZP-CSI-RS periodicity and slot offset for periodic/semi-persistent ZP CSI-RS. +- For the UE in RRC\_CONNECTED mode for multicast reception, *p-ZP-CSI-RS-ResourceSet* can be configured in *pdsch-ConfigMulticast* for GC-PDSCH rate matching, subject to UE capability. The REs indicated by *p-ZP-CSI-RS-ResourceSet* are declared as not available for GC-PDSCH. The REs indicated by *p-ZP-CSI-RS-ResourceSet* configured in *PDSCH-Config* for unicast do not apply for GC-PDSCH and the REs indicated by *p-ZP-CSI-RS-ResourceSet* configured in *pdsch-ConfigMulticast* for multicast do not apply for unicast PDSCH. The total number of periodic ZP-CSI-RS-Resources that a UE can be configured with is the same as for unicast in Rel-16. If *p-ZP-CSI-RS-ResourceSet* is configured in both *PDSCH-Config* and *pdsch-ConfigMulticast*, it is subject to UE capability whether the *p-ZP-CSI-RS-ResourceSet* configured in *pdsch-ConfigMulticast* can be different from the *p-ZP-CSI-RS-ResourceSet* configured in *PDSCH-Config*. +- For the UE in RRC\_CONNECTED mode for multicast reception, *sp-ZP-CSI-RS-ResourceSet* can be configured in *pdsch-ConfigMulticast* for GC-PDSCH rate matching, subject to UE capability. The REs indicated by *sp-ZP-CSI-RS-ResourceSet* are declared as not available for GC-PDSCH when their triggering and activation delivered by unicast PDSCH are applied. The REs indicated by *sp-ZP-CSI-RS-ResourceSet* configured in *PDSCH-Config* for unicast do not apply for GC-PDSCH and the REs indicated by *sp-ZP-CSI-RS-ResourceSet* configured in *pdsch-ConfigMulticast* for multicast do not apply for unicast PDSCH. The total number of semi-persistent ZP-CSI-RS-Resources that a UE can be configured with is the same as for unicast. + +The UE may be configured with a DCI field for triggering the aperiodic ZP CSI-RS. A list of *ZP-CSI-RS-ResourceSet(s)*, provided by higher layer parameter *aperiodic-ZP-CSI-RS-ResourceSetsToAddModList* in *PDSCH-Config*, is configured for aperiodic triggering. The maximum number of aperiodic ZP-CSI-RS-ResourceSet(s) configured per BWP is 3. The bit-length of DCI field *ZP CSI-RS trigger* depends on the number of aperiodic ZP-CSI-RS-ResourceSet(s) configured (up to 2 bits). Each non-zero codepoint of 'ZP CSI-RS' trigger in DCI format 1\_1 triggers + +one aperiodic 'ZP-CSI-RS-ResourceSet' in the list *aperiodic-ZP-CSI-RS-ResourceSetsToAddModList* by indicating the aperiodic ZP CSI-RS resource set ID. The DCI codepoint '01' triggers the resource set with 'ZP-CSI-RS-ResourceSetId' set to '1', the DCI codepoint '10' triggers the resource set with 'ZP-CSI-RS-ResourceSetId' set to '2', and the DCI codepoint '11' triggers the resource set with 'ZP-CSI-RS-ResourceSetId' set to '3'. Codepoint '00' is reserved for not triggering aperiodic ZP CSI-RS. When receiving PDSCH scheduled by DCI format 1\_0 or PDSCHs with SPS activated by DCI format 1\_0, the REs corresponding to configured resources in *aperiodic-ZP-CSI-RS-ResourceSetsToAddModList* or in *aperiodicZP-CSI-RS-ResourceSetsToAddModListDCI-1-2* are available for PDSCH. + +When the UE is configured with multi-slot and single-slot PDSCH scheduling or *pdsch-TimeDomainAllocationListForMultiPDSCH*, the triggered aperiodic ZP CSI-RS is applied to all the slot(s) of the PDSCH(s) scheduled or the PDSCHs with SPS activated by the PDCCH containing the trigger. + +For a UE configured with a list of semi-persistent *ZP-CSI-RS-ResourceSet(s)* provided by higher layer parameter *sp-ZP-CSI-RS-ResourceSetsToAddModList*: + +- when the UE would transmit a PUCCH with HARQ-ACK information in slot $n$ corresponding to the PDSCH carrying the activation command, as described in clause 6.1.3.19 of [10, TS 38.321], for ZP CSI-RS resource(s), the corresponding action in [10, TS 38.321] and the UE assumption on the PDSCH RE mapping corresponding to the activated ZP CSI-RS resource(s) shall be applied starting from the first slot that is after slot $n$ where $\mu$ is the SCS configuration for the PUCCH and is the subcarrier spacing configuration for with a value of 0 for frequency range 1, and is provided by *K-Mac* or if *K-Mac* is not provided. +- when the UE would transmit a PUCCH with HARQ-ACK information in slot $n$ corresponding to the PDSCH carrying the deactivation command, as described in clause 6.1.3.19 of [10, TS 38.321], for activated ZP CSI-RS resource(s), the corresponding action in [10, TS 38.321] and the UE assumption on cessation of the PDSCH RE mapping corresponding to the de-activated ZP CSI-RS resource(s) shall be applied starting from the first slot that is after slot $n$ where $\mu$ is the SCS configuration for the PUCCH and is the subcarrier spacing configuration for with a value of 0 for frequency range 1, and is provided by *K-Mac* or if *K-Mac* is not provided. + +### 5.1.5 Antenna ports quasi co-location + +The UE can be configured with a list of up to $M$ *TCI-State* configurations within the higher layer parameter *PDSCH-Config* to decode PDSCH according to a detected PDCCH with DCI intended for the UE and the given serving cell, where $M$ depends on the UE capability *maxNumberConfiguredTCIStatesPerCC*. Each *TCI-State* contains parameters for configuring a quasi co-location relationship between one or two downlink reference signals and the DM-RS ports of the PDSCH, the DM-RS port of PDCCH or the CSI-RS port(s) of a CSI-RS resource. The quasi co-location relationship is configured by the higher layer parameter *qcl-Type1* for the first DL RS, and *qcl-Type2* for the second DL RS (if configured). For the case of two DL RSs, the QCL types shall not be the same, regardless of whether the references are to the same DL RS or different DL RSs. The quasi co-location types corresponding to each DL RS are given by the higher layer parameter *qcl-Type* in *QCL-Info* and may take one of the following values: + +- 'typeA': {Doppler shift, Doppler spread, average delay, delay spread} +- 'typeB': {Doppler shift, Doppler spread} +- 'typeC': {Doppler shift, average delay} +- 'typeD': {Spatial Rx parameter} + +The UE can be configured with a list of up to 128 *TCI-State* configurations, within the higher layer parameter *dl-OrJointTCI-StateList* in *PDSCH-Config* for providing a reference signal for the quasi co-location for DM-RS of PDSCH and DM-RS of PDCCH in a BWP/CC, for CSI-RS, and to provide a reference, if applicable, for determining UL TX spatial filter for dynamic-grant and configured-grant based PUSCH and PUCCH resource in a BWP/CC, and SRS. + +If the *TCI-State* or *TCI-UL-State* configurations are absent in a BWP of the CC, the UE can apply the *TCI-State* or *TCI-UL-State* configurations from a reference BWP of a reference CC configured by *unifiedTCI-StateRef*. The UE is not expected to be configured with *tci-StatesToAddModList*, *SpatialRelationInfo* or *PUCCH-SpatialRelationInfo*, except *SpatialRelationInfoPos* in a CC in a band, if the UE is configured with *dl-OrJointTCI-StateList* or *ul-TCI-StateList* in any CC in the same band. The UE can assume that when the UE is configured with *tci-StatesToAddModList* in any CC in the CC list configured by *simultaneousTCI-UpdateList1-r16*, *simultaneousTCI-UpdateList2-r16*, *simultaneousSpatial-UpdatedList1-r16*, or *simultaneousSpatial-UpdatedList2-r16*, the UE is not configured with *dl-OrJointTCI-StateList* or *ul-TCI-StateList* in any CC within the same band in the CC list. + +The UE receives an activation command, as described in clause 6.1.3.xx of [10, TS 38.321], 6.1.3.47 of [10, TS 38.321] or 6.1.4.xx of [10, TS 38.321], used to map up to 8 TCI states and/or pairs of TCI states, with one TCI state for DL channels/signals and/or one TCI state for UL channels/signals to the codepoints of the DCI field *'Transmission Configuration Indication'* for one or for a set of CCs/DL BWPs, [and/] or up to 8 sets of TCI states, where each set is comprised of up to two TCI state(s) for DL and UL signals/channels, or up to two TCI state(s) for DL channels/signals and up to two TCI state(s) for UL channels/signals to the codepoints of the DCI field *'Transmission Configuration Indication'* for one or for a set of CCs/DL BWPs, and if applicable, for one or for a set of CCs/UL BWPs. When a set of TCI state IDs are activated for a set of CCs/DL BWPs and if applicable, for a set of CCs/UL BWPs, where the applicable list of CCs is determined by the indicated CC in the activation command, the same set of TCI state IDs are applied for all DL and/or UL BWPs in the indicated CCs. If the activation command maps *TCI-State(s)* and/or *TCI-UL-State(s)* to only one TCI codepoint, the UE shall apply the indicated *TCI-State(s)* and/or *TCI-UL-State(s)* to one or to a set of CCs /DL BWPs, and if applicable, to one or to a set of CCs /UL BWPs once the indicated mapping for the one single TCI codepoint is applied as described in [11, TS 38.133]. + +When the *bwp-id* or *cell* for QCL-TypeA/D source RS in a QCL-Info of the TCI state is not configured, the UE assumes that QCL-TypeA/D source RS is configured in the CC/DL BWP where TCI state applies. + +When *tci-PresentInDCI* is set as 'enabled' or *tci-PresentDCI-1-2* is configured for the CORESET, a UE configured with *dl-OrJointTCI-StateList* with activated *TCI-State* or *ul-TCI-StateList* with activated *TCI-UL-State* receives DCI format 1\_1/1\_2/1\_3 providing indicated *TCI-State(s)* and/or *TCI-UL-State(s)* for a CC or all CCs in the same CC list configured by *simultaneousU-TCI-UpdateList1-r17*, *simultaneousU-TCI-UpdateList2-r17*, *simultaneousU-TCI-UpdateList3-r17*, *simultaneousU-TCI-UpdateList4-r17*. The DCI format 1\_1/1\_2 can be with or without, if applicable, DL assignment. If the DCI format 1\_1/1\_2/ is without DL assignment, the UE can assume the following: + +- CS-RNTI is used to scramble the CRC for the DCI +- The values of the following DCI fields are set as follows: + - RV = all '1's + - MCS = all '1's + - NDI = 0 + - Set to all '0's for FDRA Type 0, or all '1's for FDRA Type 1, or all '0's for dynamicSwitch (same as in Table 10.2-4 of [6, TS 38.213]). + +After a UE receives an initial higher layer configuration of *dl-OrJointTCI-StateList* with more than one *TCI-State* and before application of an indicated TCI state from the configured TCI states: + +- The UE assumes that DM-RS of PDSCH and DM-RS of PDCCH and the CSI-RS applying the indicated TCI state are quasi co-located with the SS/PBCH block the UE identified during the initial access procedure + +After a UE receives an initial higher layer configuration of *dl-OrJointTCI-StateList* with more than one *TCI-State* or *ul-TCI-StateList* with more than one *TCI-UL-State* and before application of an indicated TCI state from the configured TCI states: + +- The UE assumes that the UL TX spatial filter, if applicable, for dynamic-grant and configured-grant based PUSCH and PUCCH, and for SRS applying the indicated TCI state, is the same as that for a PUSCH transmission scheduled by a RAR UL grant or a MsgA PUSCH transmission during the initial access procedure + +After a UE receives a higher layer configuration of *dl-OrJointTCI-StateList* with more than one *TCI-State* as part of a Reconfiguration with sync procedure as described in [12, TS 38.331] and before applying an indicated TCI state from the configured TCI states: + +- The UE assumes that DM-RS of PDSCH and DM-RS of PDCCH, and the CSI-RS applying the indicated TCI state are quasi co-located with the SS/PBCH block or the CSI-RS resource the UE identified during the random access procedure initiated by the Reconfiguration with sync procedure as described in [12, TS 38.331]. + +After a UE receives a higher layer configuration of *dl-OrJointTCI-StateList* with more than one *TCI-State* or more than one *TCI-UL-State* as part of a Reconfiguration with sync procedure as described in [12, TS 38.331] and before applying an indicated TCI state from the configured TCI states: + +- The UE assumes that the UL TX spatial filter, if applicable, for dynamic-grant and configured-grant based PUSCH and PUCCH, and for SRS applying the indicated TCI state, is the same as that for a PUSCH + +transmission scheduled by a RAR UL grant or a MsgA PUSCH transmission during random access procedure initiated by the Reconfiguration with sync procedure as described in [12, TS 38.331]. + +If a UE receives a higher layer configuration of *dl-OrJointTCI-StateList* with a single *TCI-State*, that can be used as an indicated TCI state, the UE obtains the QCL assumptions from the configured TCI state for DM-RS of PDSCH and DM-RS of PDCCH, and the CSI -RS applying the indicated TCI state. + +If a UE receives a higher layer configuration of *dl-OrJointTCI-StateList* with a single *TCI-State* or *ul-TCI-StateList* with a single *TCI-UL-State*, that can be used as an indicated TCI state, the UE determines an UL TX spatial filter, if applicable, from the configured TCI state for dynamic-grant and configured-grant based PUSCH and PUCCH, and SRS applying the indicated TCI state. + +When a UE configured with *dl-OrJointTCI-StateList* would transmit a PUCCH with positive HARQ-ACK or a PUSCH with positive HARQ-ACK corresponding to the DCI carrying the TCI State indication and without DL assignment, or corresponding to the PDSCH scheduled by the DCI carrying the TCI State indication, and if the indicated TCI State(s) is/are different from the previously indicated one(s), the indicated *TCI-State(s)* and/or *TCI-UL-State(s)* should be applied starting from the first slot that is at least symbols after the last symbol of the PUCCH or the PUSCH, and if the UE receives more than one indicated TCI state for a CC/BWP to be applied starting from the first slot that is at least symbols after the last symbol of the PUCCH or the PUSCH, the indicated TCI state carried in the latest DCI in time corresponding to positive HARQ-ACK value is applied. The first slot and the symbols are both determined on the active BWP with the smallest SCS among the BWP(s) from the CCs applying the indicated *TCI-State(s)* or *TCI-UL-State(s)* that are active at the end of the PUCCH or the PUSCH carrying the positive HARQ-ACK. + +If a UE is configured with *pdsch-TimeDomainAllocationListForMultiPDSCH* in which one or more rows contain multiple *SLIVs* for PDSCH on a DL BWP of a serving cell, and the UE is receiving a DCI carrying the *TCI-State* indication and without DL assignment, the UE does not expect that the number of indicated *SLIVs* in the row of the *pdsch-TimeDomainAllocationListForMultiPDSCH* by the DCI is more than one. + +If the UE is configured with *SSB-MTC-AdditionalPCI* and with *PDCCH-Config* that contains two different values of *coresetPoolIndex* in *ControlResourceSet*, the UE receives an activation command for CORESET associated with each *coresetPoolIndex*, as described in clause 6.1.3.14 of [10, TS 38.321] or 6.1.3.xx of [10, TS 38.321], used to map up to 8 TCI states and/or pairs of TCI states, with one TCI state for DL channels/signals and/or one TCI state for UL channels/signals to the codepoints of the DCI field '*Transmission Configuration Indication*' in one CC/DL BWP. When a set of TCI state IDs are activated for a *coresetPoolIndex*, the activated TCI states corresponding to one *coresetPoolIndex* is associated with the serving cell physical cell ID and activated TCI states corresponding to another *coresetPoolIndex* can be associated with another physical cell ID. + +When a UE supports two TCI states in a codepoint of the DCI field '*Transmission Configuration Indication*' the UE may receive an activation command, as described in clause 6.1.3.24 of [10, TS 38.321], the activation command is used to map up to 8 combinations of one or two TCI states to the codepoints of the DCI field '*Transmission Configuration Indication*'. The UE is not expected to receive more than 8 TCI states in the activation command. + +When the DCI field '*Transmission Configuration Indication*' is present in DCI format 1\_2 and when the number of codepoints S in the DCI field '*Transmission Configuration Indication*' of DCI format 1\_2 is smaller than the number of TCI codepoints that are activated by the activation command, as described in clause 6.1.3.14, 6.1.3.24 and 6.1.3.47 of [10, TS38.321], only the first S activated codepoints are applied for DCI format 1\_2. + +When the UE would transmit a PUCCH with HARQ-ACK information in slot *n* corresponding to the PDSCH carrying the activation command, the indicated mapping between TCI states and codepoints of the DCI field '*Transmission Configuration Indication*' should be applied starting from the first slot that is after slot where $\mu$ is the SCS configuration for the PUCCH and is the subcarrier spacing configuration for with a value of 0 for frequency range 1, and is provided by *K-Mac* or if *K-Mac* is not provided. If *tci-PresentInDCI* is set to 'enabled' or *tci-PresentDCI-1-2* is configured for the CORESET scheduling the PDSCH, and the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than *timeDurationForQCL* if applicable, after a UE receives an initial higher layer configuration of TCI states and before reception of the activation command, the UE may assume that the DM-RS ports of PDSCH of a serving cell are quasi co-located with the SS/PBCH block determined in the initial access procedure with respect to *qcl-Type* set to 'typeA', and when applicable, also with respect to *qcl-Type* set to 'typeD'. + +If a UE is configured with the higher layer parameter *tci-PresentInDCI* that is set as 'enabled' for the CORESET scheduling a PDSCH, the UE assumes that the TCI field is present in the DCI format 1\_1 or format 1\_3 of the PDCCH transmitted on the CORESET. If a UE is configured with the higher layer parameter *tci-PresentDCI-1-2* for the CORESET scheduling the PDSCH, the UE assumes that the TCI field with a DCI field size indicated by *tci-PresentDCI-1-2* is present in the DCI format 1\_2 of the PDCCH transmitted on the CORESET. If a UE is configured + +with the higher layer parameter *tci-PresentInDCI* that is set as 'enabled' for the CORESET scheduling the multicast PDSCH, the UE assumes that the TCI field is present in the DCI format 4\_2 of the PDCCH transmitted on the CORESET. If the PDSCH is scheduled by a DCI format not having the TCI field present, and the time offset between the reception of the DL DCI and the corresponding PDSCH of a serving cell is equal to or greater than a threshold *timeDurationForQCL* if applicable, where the threshold is based on reported UE capability [13, TS 38.306], for determining PDSCH antenna port quasi co-location, the UE assumes that the TCI state or the QCL assumption for the PDSCH is identical to the TCI state or QCL assumption whichever is applied for the CORESET used for the PDCCH transmission within the active BWP of the serving cell. + +When a UE is configured with both *sfnSchemePDCCH* and *sfnSchemePDSCH* scheduled by DCI format 1\_0 or by DCI format 1\_1/1\_2, if the time offset between the reception of the DL DCI and the corresponding PDSCH of a serving cell is equal to or greater than a threshold *timeDurationForQCL* if applicable: + +- if the UE supports *sfn-DefaultDL-BeamSetup-r17* for DCI scheduling without TCI field, the UE assumes that the TCI state(s) or the QCL assumption(s) for the PDSCH is identical to the TCI state(s) or QCL assumption(s) whichever is applied for the CORESET used for the reception of the DL DCI within the active BWP of the serving cell regardless of the number of active TCI states of the CORESET. If the UE does not support *sfn-SchemeA-DynamicSwitching-r17* or *sfn-SchemeB-DynamicSwitching-r17*, the UE should be activated with the CORESET with two TCI states. +- else if the UE does not support *sfn-DefaultDL-BeamSetup-r17* for DCI scheduling without TCI field, the UE shall expect TCI field present when scheduled by DCI format 1\_1/1\_2. + +When a UE is configured with *sfnSchemePDSCH* and *sfnSchemePDCCH* is not configured, when scheduled by DCI format 1\_1/1\_2, if the time offset between the reception of the DL DCI and the corresponding PDSCH of a serving cell is equal to or greater than a threshold *timeDurationForQCL* if applicable, the UE shall expect TCI field present. + +For PDSCH scheduled by DCI format 1\_0, 1\_1, 1\_2, when a UE is configured with *sfnSchemePDCCH* set to 'sfnSchemeA' and *sfnSchemePDSCH* is not configured, and there is no TCI codepoint with two TCI states in the activation command, and if the time offset between the reception of the DL DCI and the corresponding PDSCH is equal or larger than the threshold *timeDurationForQCL* if applicable and the CORESET which schedules the PDSCH is indicated with two TCI states, the UE assumes that the TCI state or the QCL assumption for the PDSCH is identical to the first TCI state or QCL assumption which is applied for the CORESET used for the PDCCH transmission within the active BWP of the serving cell. + +If a PDSCH is scheduled by a DCI format having the TCI field present, the TCI field in DCI in the scheduling component carrier points to the activated TCI states in the scheduled component carrier or DL BWP, the UE shall use the *TCI-State* according to the value of the '*Transmission Configuration Indication*' field in the detected PDCCH with DCI for determining PDSCH antenna port quasi co-location. The UE may assume that the DM-RS ports of PDSCH of a serving cell are quasi co-located with the RS(s) in the TCI state with respect to the QCL type parameter(s) given by the indicated TCI state if the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than a threshold *timeDurationForQCL*, where the threshold is based on reported UE capability [13, TS 38.306]. For a single slot PDSCH, the indicated TCI state(s) should be based on the activated TCI states in the slot with the scheduled PDSCH. For a multi-slot PDSCH or the UE is configured with higher layer parameter *pdsch-TimeDomainAllocationListForMultiPDSCH*, the indicated TCI state(s) should be based on the activated TCI states in the first slot with the scheduled PDSCH(s), and UE shall expect the activated TCI states are the same across the slots with the scheduled PDSCH(s). When the UE is configured with CORESET associated with a search space set for cross-carrier scheduling and the UE is not configured with *enableDefaultBeamForCCS*, the UE expects *tci-PresentInDCI* is set as 'enabled' or *tci-PresentDCI-1-2* is configured for the CORESET, and if one or more of the TCI states configured for the serving cell scheduled by the search space set contains *qcl-Type* set to 'typeD', the UE expects the time offset between the reception of the detected PDCCH in the search space set and a corresponding PDSCH is larger than or equal to the threshold *timeDurationForQCL*. + +Independent of the configuration of *tci-PresentInDCI* and *tci-PresentDCI-1-2* in RRC connected mode, if the UE is not provided *dl-OrJointTCI-StateList-r17*, and if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold *timeDurationForQCL* and at least one configured TCI state for the serving cell of scheduled PDSCH contains *qcl-Type* set to 'typeD', + +- the UE may assume that the DM-RS ports of PDSCH(s) of a serving cell are quasi co-located with the RS(s) with respect to the QCL parameter(s) used for PDCCH quasi co-location indication of the CORESET associated with a monitored search space with the lowest *controlResourceSetId* in the latest slot in which one or more CORESETs within the active BWP of the serving cell are monitored by the UE. In this case, if the *qcl-Type* is set to 'typeD' of the PDSCH DM-RS is different from that of the PDCCH DM-RS with which they overlap in at + +least one symbol, the UE is expected to prioritize the reception of PDCCH associated with that CORESET. This also applies to the intra-band CA case (when PDSCH and the CORESET are in different component carriers). + +- If a UE is configured with *enableDefaultTCI-StatePerCoresetPoolIndex* and the UE is configured by higher layer parameter *PDCCH-Config* that contains two different values of *coresetPoolIndex* in different *ControlResourceSets*, + - the UE may assume that the DM-RS ports of PDSCH associated with a value of *coresetPoolIndex* of a serving cell are quasi co-located with the RS(s) with respect to the QCL parameter(s) used for PDCCH quasi co-location indication of the CORESET associated with a monitored search space with the lowest *controlResourceSetId* among CORESETs, which are configured with the same value of *coresetPoolIndex* as the PDCCH scheduling that PDSCH, in the latest slot in which one or more CORESETs associated with the same value of *coresetPoolIndex* as the PDCCH scheduling that PDSCH within the active BWP of the serving cell are monitored by the UE. In this case, if the 'QCL-TypeD' of the PDSCH DM-RS is different from that of the PDCCH DM-RS with which they overlap in at least one symbol and they are associated with same value of *coresetPoolIndex*, the UE is expected to prioritize the reception of PDCCH associated with that CORESET. This also applies to the intra-band CA case (when PDSCH and the CORESET are in different component carriers). +- If a UE is configured with *enableTwoDefaultTCI-States*, and at least one TCI codepoint indicates two TCI states, the UE may assume that the DM-RS ports of PDSCH or PDSCH transmission occasions of a serving cell are quasi co-located with the RS(s) with respect to the QCL parameter(s) associated with the TCI states corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states. When the UE is configured by higher layer parameter *repetitionScheme* set to 'tdmSchemeA' or is configured with higher layer parameter *repetitionNumber*, and the offset between the reception of the DL DCI and the first PDSCH transmission occasion is less than the threshold *timeDurationForQCL*, the mapping of the TCI states to PDSCH transmission occasions is determined according to clause 5.1.2.1 by replacing the indicated TCI states with the TCI states corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states based on the activated TCI states in the slot with the first PDSCH transmission occasion. In this case, if the 'QCL-TypeD' in both of the TCI states corresponding to the lowest codepoint among the TCI codepoints containing two different TCI states is different from that of the PDCCH DM-RS with which they overlap in at least one symbol, the UE is expected to prioritize the reception of PDCCH associated with that CORESET. This also applies to the intra-band CA case (when PDSCH and the CORESET are in different component carriers) +- If a UE is not configured with *sfnSchemePDSCH*, and the UE is configured with *sfnSchemePDCCH* set to 'sfnSchemeA' and there is no TCI codepoint with two TCI states in the activation command and the CORESET with the lowest ID in the latest slot is indicated with two TCI states, the UE may assume that the DM-RS ports of PDSCH of a serving cell are quasi co-located with the RS(s) with respect to the QCL parameter(s) associated with the first TCI state of two TCI states indicated for the CORESET. In this case, if the *qcl-Type* is set to 'typeD' of the PDSCH DM-RS is different from that of the PDCCH DM-RS with which they overlap in at least one symbol, the UE is expected to prioritize the reception of PDCCH associated with that CORESET with single active TCI state. This also applies to the intra-band CA case (when PDSCH and the CORESET are in different component carriers). +- In all cases above, if none of configured TCI states for the serving cell of scheduled PDSCH is configured with *qcl-Type* set to 'typeD', the UE shall obtain the other QCL assumptions from the indicated TCI state(s) for its scheduled PDSCH irrespective of the time offset between the reception of the DL DCI and the corresponding PDSCH. + +Independent of the configuration of *tci-PresentInDCI* and *tci-PresentDCI-1-2* in RRC connected mode, if the UE is provided *dl-OrJointTCI-StateList-r17*, and if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold *timeDurationForQCL* and at least one configured TCI state for the serving cell of scheduled PDSCH contains *qcl-Type* set to 'typeD', regardless of configuration of *followUnifiedTCI-State*, + +- if the indicated TCI state is associated with the PCI of the serving cell, the indicated TCI state is applied to PDSCH reception. +- if the indicated TCI state is associated with a PCI different from the serving cell, the UE may assume that the DM-RS ports of PDSCH(s) of a serving cell are quasi co-located with the RS(s) with respect to the QCL parameter(s) used for PDCCH quasi co-location indication of the CORESET associated with a monitored search space with the lowest *controlResourceSetId* in the latest slot in which one or more CORESETs within the active BWP of the serving cell are monitored by the UE. In the CA case, if the 'QCL-TypeD' of the PDSCH DM-RSs from respective CCs in a band are different in a slot, the QCL-TypeD assumption of the PDSCH DM-RS in the + +CC with lowest CC ID in the band is applied to all the PDSCH DM-RSs in the CCs in the band. In this case, if the *qcl-Type* is set to 'typeD' of the PDSCH DM-RS is different from that of the PDCCH DM-RS with which they overlap in at least one symbol, the UE is expected to prioritize the reception of PDCCH associated with that CORESET. This also applies to the intra-band CA case (when PDSCH and the CORESET are in different component carriers). + +If the PDCCH carrying the scheduling DCI is received on one component carrier, and a PDSCH scheduled by that DCI is on another component carrier: + +- The *timeDurationForQCL* is determined based on the subcarrier spacing of the scheduled PDSCH. If $\mu_{\text{PDCCH}} < \mu_{\text{PDSCH}}$ an additional timing delay *d* is added to the *timeDurationForQCL*, where *d* is defined in 5.2.1.5.1a-1, otherwise *d* is zero; +- When the UE is configured with *enableDefaultBeamForCCS*, if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold *timeDurationForQCL*, or if the DL DCI does not have the TCI field present, the UE obtains its QCL assumption for the scheduled PDSCH from the activated TCI state with the lowest ID applicable to PDSCH in the active BWP of the scheduled cell. + +A UE that has indicated a capability *beamCorrespondenceWithoutUL-BeamSweeping* set to 'supported', as described in [13, TS 38.306], can determine a spatial domain filter to be used while performing the applicable channel access procedures described in [16, TS 37.213] prior to a UL transmission on the channel as follows: + +- if UE is indicated with an SRI corresponding to the UL transmission, the UE may use a spatial domain filter that is same as the spatial domain transmission filter associated with the indicated SRI, +- if UE is configured with *SRS-spatialRelationInfo* for the UL transmission, the UE may use a spatial domain filter that is same as the spatial domain filter associated with *referenceSignal* in the corresponding *SRS-spatialRelationInfo*, +- if UE is configured with *TCI-State* in *dl-OrJointTCI-StateList* or *TCI-UL-State* in *ul-TCI-StateList*, the UE may use a spatial domain filter that is same as the spatial domain receive filter the UE may use to receive the DL reference signal associated with the indicated TCI state. + +When the PDCCH reception includes two PDCCH from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], for the purpose of determining the time offset between the reception of the DL DCI and the corresponding PDSCH, the PDCCH candidate that ends later in time is used. When the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], for the configuration of *tcipPresentInDCI* or *tcipPresentDCI-1-2*, the UE expects the same configuration in the first and second CORESETs associated with the two PDCCH candidates; and if the PDSCH is scheduled by a DCI format not having the TCI field present and if the scheduling offset is equal to or larger than *timeDurationForQCL*, if applicable, PDSCH QCL assumption is based on the CORESET with lower ID among the first and second CORESETs associated with the two PDCCH candidates. + +For a periodic CSI-RS resource in an *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info*, the UE shall expect that a TCI-State indicates one of the following quasi co-location type(s): + +- 'typeC' with an SS/PBCH block and, when applicable, 'typeD' with the same SS/PBCH block where SS/PBCH block may have a PCI different from the PCI of the serving cell. The UE can assume center frequency, SCS, SFN offset are the same for SS/PBCH block from the serving cell and SS/PBCH block having a PCI different from the serving cell, or +- 'typeC' with an SS/PBCH block and, when applicable, 'typeD' with a CSI-RS resource in an *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *repetition*, where SS/PBCH block may have a PCI different from the PCI of the serving cell. The UE can assume center frequency, SCS, SFN offset are the same for SS/PBCH block from the serving cell and SS/PBCH block having a PCI different from the serving cell. + +For periodic/semi-persistent CSI-RS, if the UE is configured with *dl-OrJointTCI-StateList*, the UE can assume that the indicated *TCI-State* is not applied. + +For an aperiodic CSI-RS resource in an *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info*, the UE shall expect that a *TCI-State* indicates *qcl-Type* set to 'typeA' with a periodic CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info* and, when applicable, *qcl-Type* set to 'typeD' with the same periodic CSI-RS resource. + +For a CSI-RS resource in an *NZP-CSI-RS-ResourceSet* configured without higher layer parameter *trs-Info* and without the higher layer parameter *repetition*, the UE shall expect that a TCI-State indicates one of the following quasi co-location type(s): + +- 'typeA' with a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info* and, when applicable, 'typeD' with the same CSI-RS resource, or +- 'typeA' with a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info* and, when applicable, 'typeD' with an SS/PBCH block, where SS/PBCH block may have a PCI different from the PCI of the serving cell. The UE can assume center frequency, SCS, SFN offset are the same for SS/PBCH block from the serving cell and SS/PBCH block having a PCI different from the serving cell, or +- 'typeA' with a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info* and, when applicable, 'typeD' with a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *repetition*, or +- 'typeB' with a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info* when 'typeD' is not applicable. + +For a CSI-RS resource in an *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *repetition*, the UE shall expect that a TCI-State indicates one of the following quasi co-location type(s): + +- 'typeA' with a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info* and, when applicable, 'typeD' with the same CSI-RS resource, or +- 'typeA' with a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info* and, when applicable, 'typeD' with a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *repetition*, or +- 'typeC' with an SS/PBCH block and, when applicable, 'typeD' with the same SS/PBCH block, the reference RS may additionally be an SS/PBCH block having a PCI different from the PCI of the serving cell. The UE can assume center frequency, SCS, SFN offset are the same for SS/PBCH block from the serving cell and SS/PBCH block having a PCI different from the serving cell. + +For the DM-RS of PDCCH, if the UE is not configured with *dl-OrJointTCI-StateList*, the UE shall expect that a *TCI-State* indicates one of the following quasi co-location type(s): + +- 'typeA' with a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info* and, when applicable, 'typeD' with the same CSI-RS resource, or +- 'typeA' with a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info* and, when applicable, 'typeD' with a CSI-RS resource in an *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *repetition*, or +- 'typeA' with a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured without higher layer parameter *trs-Info* and without higher layer parameter *repetition* and, when applicable, 'typeD' with the same CSI-RS resource. + +When a UE is configured with *sfnSchemePdcch* set to 'sfnSchemeA', and CORESET is activated with two TCI states, the UE shall assume that the DM-RS port(s) of the PDCCH in the CORESET is quasi co-located with the DL-RSs of the two TCI states. When a UE is configured with *sfnSchemePdcch* set to 'sfnSchemeB', and a CORESET is activated with two TCI states, the UE shall assume that the DM-RS port(s) of the PDCCH is quasi co-located with the DL-RSs of the two TCI states except for quasi co-location parameters {Doppler shift, Doppler spread} of the second indicated TCI state. + +When a UE is configured by higher layer parameter *cjtSchemePDSCH* and *dl-OrJointTCI-StateList* and is indicated with two TCI-States applied for PDSCH reception and reports [support for two joint TCI states for PDSCH-CJT]: + +- if the UE is configured with *cjtSchemeA*, the UE assumes that PDSCH DM-RS port(s) are QCLed with the DL RSs of both indicated TCI-States with respect to QCL-TypeA. +- if the UE is configured with *cjtSchemeB*, the UE assumes that PDSCH DM-RS port(s) are QCLed with the DL RSs of both indicated TCI-States with respect to QCL-TypeA except for QCL parameters {Doppler shift, Doppler spread} of the second indicated joint TCI state. + +For the DM-RS of PDSCH, if the UE is not configured with *dl-OrJointTCI-StateList*, the UE shall expect that a *TCI-State* indicates one of the following quasi co-location type(s): + +- 'typeA' with a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info* and, when applicable, 'typeD' with the same CSI-RS resource, or +- 'typeA' with a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info* and, when applicable, 'typeD' with a CSI-RS resource in an *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *repetition*, or +- 'typeA' with a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured without higher layer parameter *trs-Info* and without higher layer parameter *repetition* and, when applicable, 'typeD' with the same CSI-RS resource. + +For the DM-RS of PDCCH, if the UE is configured with *dl-OrJointTCI-StateList*, the UE shall expect that an indicated *TCI-State* indicates one of the following quasi co-location type(s): + +- 'typeA' with a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info* and, when applicable, 'typeD' with the same CSI-RS resource, or +- 'typeA' with a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info* and, when applicable, 'typeD' with a CSI-RS resource in an *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *repetition*. + +For the DM-RS of PDSCH, if the UE is configured with *dl-OrJointTCI-StateList*, the UE shall expect that an indicated *TCI-State* indicates one of the following quasi co-location type(s): + +- 'typeA' with a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info* and, when applicable, 'typeD' with the same CSI-RS resource, or +- 'typeA' with a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info* and, when applicable, 'typeD' with a CSI-RS resource in an *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *repetition*. + +When a UE is configured with *sfnSchemePDSCH* set to 'sfnSchemeA', and the UE is indicated with two TCI states in a codepoint of the DCI field 'Transmission Configuration Indication' in a DCI scheduling a PDSCH, the UE shall assume that the DM-RS port(s) of the PDSCH is quasi co-located with the DL-RSs of the two TCI states. When a UE is configured with *sfnSchemePDSCH* set to 'sfnSchemeB', and the UE is indicated with two TCI states in a codepoint of the DCI field 'Transmission Configuration Indication' in a DCI scheduling a PDSCH, the UE shall assume that the DM-RS port(s) of the PDSCH is quasi co-located with the DL-RSs of the two TCI states except for quasi co-location parameters {Doppler shift, Doppler spread} of the second indicated TCI state. + +When a UE is configured with *dl-OrJointTCI-StateList* or *TCI-UL-State* and is configured by higher layer parameter *PDCCH-Config* that contains two different values of *coresetPoolIndex* in *ControlResourceSet*, an indicated TCI state is specific to a *coresetPoolIndex* value, when it is indicated by the DCI field 'Transmission Configuration Indication' in DCI format 1\_0/1\_1/1\_2 associated with the *coresetPoolIndex* value. + +When a UE is configured with *dl-OrJointTCI-StateList* and is having two indicated TCI-states, if the UE does not report its capability of *[two default beams for S-DCI based MTRP]* in frequency range 2 and when the offset between the reception of the scheduling/activation DCI format 1\_0/1\_1/1\_2 and the scheduled or activated PDSCH reception is less than *[timeDurationForQCL]* in frequency range 2, the UE shall apply the first indicated TCI-State to the scheduled or activated PDSCH reception. + +When a UE is configured with *dl-OrJointTCI-StateList*, is configured by higher layer parameter *PDCCH-Config* that contains two different values of *coresetPoolIndex* in *ControlResourceSet*, if the UE does not report its capability of *[default beam per coresetPoolIndex for M-DCI based MTRP]* in frequency range 2 + +- when the offset between the reception of the scheduling/activation DCI format 1\_0/1\_1/1\_2 in a CORESET associated with *coresetPoolIndex* value 0 and the scheduled or activated PDSCH reception is less than *[timeDurationForQCL]* in frequency range 2, the UE shall apply the indicated joint/DL TCI state specific to *coresetPoolIndex* value 0 to the scheduled or activated PDSCH reception. +- the UE does not expect that the offset between reception of the scheduling/activation DCI format 1\_0/1\_1/1\_2 in a CORESET associated with *coresetPoolIndex* value 1 and scheduled or activated PDSCH reception is less than *[timeDurationForQCL]* in frequency range 2. + +When a UE is configured with *dl-OrJointTCI-StateList* and is having two indicated TCI-states: + +- Regardless of the offset between the reception of the scheduling DCI format 1\_0/1\_1/1\_2 and the scheduled/activated PDSCH reception, if the UE is in frequency range 1, or the UE reports its capability of *[two default beams for S-DCI based MTRP]* in frequency range 2, or +- If the UE does not report its capability of *[two default beams for S-DCI based MTRP]* in frequency range 2 and if the scheduling offset between the reception of the scheduling DCI format 1\_0/1\_1/1\_2 and the scheduled/activated PDSCH reception is equal to or larger than *[timeDurationForQCL]* + - The UE can be configured by higher layer parameter *applyIndicatedTCIState* to indicate whether the first, the second, or both of the indicated TCI-state(s) is/are applied to PDSCH reception scheduled or activated by DCI format 1\_0. The UE can be configured with *applyIndicatedTCIState* with value *both* only when the UE is configured with *cjtSchemePDSCH* and the UE reports *[support for two joint TCI states for PDSCH-CJT]* or the UE is configured with *sfnSchemePdsch*. In that case, the UE shall apply both indicated TCI-states to PDSCH reception scheduled or activated by DCI format 1\_0 on a search space other than Type0/0A/2 CSS on CORESET#0. +- If the UE is not configured with *applyIndicatedTCIState*, the first indicated TCI-state is applied to PDSCH reception scheduled or activated by DCI format 1\_0. +- When the UE is configured with *tciselection-PresentInDCI* jointly for both DCI formats 1\_1 and 1\_2 in the same DL BWP, and when the UE receives a DCI format 1\_1/1\_2 that schedules or activates PDSCH reception, the UE shall determine the indicated joint/DL TCI state(s) for the PDSCH reception according to the following: + - If the DCI format 1\_1/1\_2 indicates codepoint "00" for the [TCI selection field], the UE shall apply the first one of two indicated joint/DL TCI states to all PDSCH DM-RS port(s) of corresponding PDSCH transmission occasion(s) scheduled or activated by the DCI format 1\_1/1\_2. + - If the DCI format 1\_1/1\_2 indicates codepoint "01" for the [TCI selection field], the UE shall apply the second one of two indicated joint/DL TCI states to all PDSCH DM-RS port(s) of corresponding PDSCH transmission occasion(s) scheduled or activated by the DCI format 1\_1/1\_2. + - If the DCI format 1\_1/1\_2 indicates codepoint "10" for the [TCI selection field], the UE shall apply both indicated joint/DL TCI states to the PDSCH reception scheduled or activated by the DCI format 1\_1/1\_2. +- If the UE is not configured with *tciselection-PresentInDCI* and when the UE receives a DCI format 1\_1/1\_2 that schedules/activates PDSCH reception, the UE shall apply both indicated TCI-States to the scheduled or activated PDSCH reception + +### 5.1.6 UE procedure for receiving reference signals + +#### 5.1.6.1 CSI-RS reception procedure + +The CSI-RS defined in Clause 7.4.1.5 of [4, TS 38.211], may be used for time/frequency tracking, CSI computation, L1-RSRP computation, L1-SINR computation, mobility, and tracking during fast SCell activation. + +For a CSI-RS resource associated with a *NZP-CSI-RS-ResourceSet* with the higher layer parameter *repetition* set to 'on', the UE shall not expect to be configured with CSI-RS over the symbols during which the UE is also configured to monitor the CORESET, while for other *NZP-CSI-RS-ResourceSet* configurations, if the UE is configured with a CSI-RS resource and a search space set associated with a CORESET in the same OFDM symbol(s), the UE may assume that the CSI-RS and a PDCCH DM-RS transmitted in all the search space sets associated with CORESET are quasi co-located with 'typeD', if 'typeD' is applicable. If the CORESET is activated with two TCI states, UE may assume that the first TCI state of the CORESET as the default QCL assumption for the CSI-RS. This also applies to the case when CSI-RS and the CORESET are in different intra-band component carriers, if 'typeD' is applicable. Furthermore, the UE shall not expect to be configured with the CSI-RS in PRBs that overlap those of the CORESET in the OFDM symbols occupied by the search space set(s). + +The UE is not expected to receive CSI-RS and *SIB1* message in the overlapping PRBs in the OFDM symbols where *SIB1* is transmitted. + +If the UE is configured with DRX, + +- if the UE is configured to monitor DCI format 2\_6 and configured by higher layer parameter *ps-TransmitOtherPeriodicCSI* to report CSI with the higher layer parameter *reportConfigType* set to 'periodic' and *reportQuantity* set to quantities other than 'cri-RSRP' and 'ssb-Index-RSRP' when *drx-onDurationTimer* in *DRX-Config* is not started, the most recent CSI measurement occasion occurs in DRX active time or during the time duration indicated by *drx-onDurationTimer* in *DRX-Config* also outside DRX active time for CSI to be reported; +- if the UE is configured to monitor DCI format 2\_6 and configured by higher layer parameter *ps-TransmitPeriodicL1-RSRP* to report L1-RSRP with the higher layer parameter *reportConfigType* set to 'periodic' and *reportQuantity* set to cri-RSRP when *drx-onDurationTimer* in *DRX-Config* is not started, the most recent CSI measurement occasion occurs in DRX active time or during the time duration indicated by *drx-onDurationTimer* in *DRX-Config* also outside DRX active time for CSI to be reported; +- otherwise, the most recent CSI measurement occasion occurs in DRX active time for CSI to be reported. + +During non-active periods of cell DTX, the UE configured with cell DTX is not expected to receive the periodic CSI-RS and semi-persistent CSI-RS configured in CSI report configuration in *CSI-ReportConfig* associated with the higher layer parameter *reportQuantity* comprising at least 'RI'. If the cell DTX is activated for a serving cell [10, TS 38.321], the most recent CSI measurement occasion of semi-persistent CSI-RS resource or periodic CSI-RS resource occurs in active periods of cell DTX for CSI report configured by *CSI-ReportConfig* associated with the higher layer parameter *reportQuantity* comprising at least 'RI'. + +##### 5.1.6.1.1 CSI-RS for tracking + +A UE in RRC connected mode is expected to receive the higher layer UE specific configuration of a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info*. + +For a *NZP-CSI-RS-ResourceSet* configured with the higher layer parameter *trs-Info*, the UE shall assume the antenna port with the same port index of the configured NZP CSI-RS resources in the *NZP-CSI-RS-ResourceSet* is the same. + +- For frequency range 1, the UE may be configured with one or more NZP CSI-RS set(s), where a *NZP-CSI-RS-ResourceSet* consists of four periodic NZP CSI-RS resources in two consecutive slots with two periodic NZP CSI-RS resources in each slot. If no two consecutive slots are indicated as downlink slots by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigDedicated*, then the UE may be configured with one or more NZP CSI-RS set(s), where a *NZP-CSI-RS-ResourceSet* consists of two periodic NZP CSI-RS resources in one slot. +- For frequency range 2 the UE may be configured with one or more NZP CSI-RS set(s), where a *NZP-CSI-RS-ResourceSet* consists of two periodic CSI-RS resources in one slot or with a *NZP-CSI-RS-ResourceSet* of four periodic NZP CSI-RS resources in two consecutive slots with two periodic NZP CSI-RS resources in each slot. + +A UE configured with *NZP-CSI-RS-ResourceSet(s)* configured with higher layer parameter *trs-Info* may have the CSI-RS resources configured as: + +- Periodic, with the CSI-RS resources in the *NZP-CSI-RS-ResourceSet* configured with same periodicity, bandwidth and subcarrier location. +- Periodic CSI-RS resource in one set and aperiodic CSI-RS resources in a second set, with the aperiodic CSI-RS and periodic CSI-RS resource having the same bandwidth (with same RB location) and the aperiodic CSI-RS being configured with *qcl-Type* set to 'typeA' and 'typeD', where applicable, with the periodic CSI-RS resources. For frequency range 2, the UE does not expect that the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resources is smaller than *beamSwitchTiming* + *d* in CSI-RS symbols, where *beamSwitchTiming* is UE reported value defined in [13, TS 38.306], the reported value is one of the values of {14, 28, 48}, and the beam switching timing delay *d* is defined in Table 5.2.1.5.1a-1 if $\mu_{\text{PDCCH}} < \mu_{\text{CSIRS}}$ , else *d* is zero. The UE shall expect that the periodic CSI-RS resource set and aperiodic CSI-RS resource set are configured with the same number of CSI-RS resources and with the same number of CSI-RS resources in a slot. For the aperiodic CSI-RS resource set if triggered, and if the associated periodic CSI-RS resource set is configured with four periodic CSI-RS resources with two consecutive slots with two periodic CSI-RS resources in each slot, the higher layer parameter *aperiodicTriggeringOffset* indicates the triggering offset for the first slot for the first two CSI-RS resources in the set. + +A UE does not expect to be configured with a *CSI-ReportConfig* that is linked to a *CSI-ResourceConfig* containing an *NZP-CSI-RS-ResourceSet* configured with *trs-Info* and with the *CSI-ReportConfig* configured with the higher layer parameter *timeRestrictionForChannelMeasurements* set to 'configured'. + +A UE does not expect to be configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to other than 'tdcp' or 'none' for aperiodic NZP CSI-RS resource set configured with *trs-Info*. + +A UE does not expect to be configured with a *CSI-ReportConfig* for periodic NZP CSI-RS resource set configured with *trs-Info*, except for *reportQuantity* set to 'tdcp'. + +A UE does not expect to be configured with a *NZP-CSI-RS-ResourceSet* configured both with *trs-Info* and *repetition*. + +Each CSI-RS resource, defined in Clause 7.4.1.5.3 of [4, TS 38.211], is configured by the higher layer parameter *NZP-CSI-RS-Resource* with the following restrictions: + +- the time-domain locations of the two CSI-RS resources in a slot, or of the four CSI-RS resources in two consecutive slots (which are the same across two consecutive slots), as defined by higher layer parameter *CSI-RS-resourceMapping*, is given by one of + - , , , or for frequency range 1 and frequency range 2, + - , , , , , or for frequency range 2. +- a single port CSI-RS resource with density given by Table 7.4.1.5.3-1 from [4, TS 38.211] and higher layer parameter *density* configured by *CSI-RS-ResourceMapping*. +- if carrier , , and the carrier is configured in paired spectrum, the bandwidth of the CSI-RS resource, as given by the higher layer parameter *freqBand* configured by *CSI-RS-ResourceMapping*, is *X* resource blocks, where resource blocks if the UE indicates *trs-AddBW-Set1* for the *trs-AdditionalBandwidth* capability for CSI-RS for tracking or *addBW-Set1* for the *aperiodicCSI-RS-AdditionalBandwidth* capability for aperiodic CSI-RS for fast SCell activation and if the UE indicates *trs-AddBW-Set2* for the *AdditionalBandwidth* capability for CSI-RS for tracking or *addBW-Set2* for the *aperiodicCSI-RS-AdditionalBandwidth* capability for aperiodic CSI-RS for fast SCell activation; in these cases, if the UE is configured with CSI-RS comprising *X*<52 resource blocks, the UE does not expect that the total number of PRBs allocated for DL transmissions but not overlapped with the PRBs carrying CSI-RS for tracking is more than 4, where all CSI-RS resource configurations shall span the same set of resource blocks; otherwise, the bandwidth of the CSI-RS resource, as given by the higher layer parameter *freqBand* configured by *CSI-RS-ResourceMapping*, is the minimum of 52 and resource blocks, or is equal to resource blocks. For operation with shared spectrum channel access in FR1, *freqBand* configured by *CSI-RS-ResourceMapping*, is the minimum of 48 and resource blocks, or is equal to resource blocks. +- the UE is not expected to be configured with the periodicity of slots if the bandwidth of CSI-RS resource is larger than 52 resource blocks. +- the periodicity and slot offset for periodic NZP CSI-RS resources, as given by the higher layer parameter *periodicityAndOffset* configured by *NZP-CSI-RS-Resource*, is one of slots where 10, 20, 40, or 80 and where $\mu$ is defined in Clause 4.3 of [4, TS 38.211]. +- same *powerControlOffset* and *powerControlOffsetSS* given by *NZP-CSI-RS-Resource* value across all resources. + +A UE in RRC\_IDLE or RRC\_INACTIVE can receive a higher layer configuration of TRS occasions via a *trs-ResourceSetConfig*. + +- For frequency range 1, the UE may be configured with one or more TRS resource set(s), where each TRS resource set configured by a *TRS-ResourceSet* consists of four periodic NZP CSI-RS resources in two consecutive slots with two periodic NZP CSI-RS resources in each slot. If no two consecutive slots are indicated as downlink slots by *tdd-UL-DL-ConfigurationCommon*, then the UE may be configured with one or more TRS resource set(s), where a *TRS-ResourceSet* consists of two periodic NZP CSI-RS resources in one slot. +- For frequency range 2 the UE may be configured with one or more TRS resource set(s), where each TRS resource set configured by a *TRS-ResourceSet* consists of two periodic NZP CSI-RS resources in one slot or by a *TRS-ResourceSet* of four periodic NZP CSI-RS resources in two consecutive slots with two periodic NZP CSI-RS resources in each slot. + +Each NZP CSI-RS resource, defined in Clause 7.4.1.5.3 of [4, TS 38.211], is configured by the higher layer parameter *TRS-ResourceSet* with the following restrictions for a UE in RRC\_IDLE or RRC\_INACTIVE: + +- the number of periodic NZP CSI-RS resources configured by a *TRS-ResourceSet* is given by *nrofResources* + +- the time-domain locations of the two CSI-RS resources in a slot, or of the four CSI-RS resources in two consecutive slots (which are the same across two consecutive slots), is one of + - , , or for frequency range 1 and frequency range 2, + - , , , , or for frequency range 2. +- where the first symbol location in a slot is indicated by *firstOFDMSymbolInTimeDomain* in the *TRS-ResourceSet* and the second symbol location in a slot is *firstOFDMSymbolInTimeDomain* + 4 +- a single port CSI-RS resource with density given by Table 7.4.1.5.3-1 from [4, TS 38.211]. +- the bandwidth and the frequency location of the NZP CSI-RS resource, is given by the higher layer parameter *nrofRBs*, *startingRB* and *frequencyDomainAllocation* in a *TRS-ResourceSet* and applies to all resources in a *TRS-ResourceSet*. Bandwidth, *nrofRBs*, and the initial CRB index, *startingRB*, of the NZP CSI-RS resource configured by *TRS-ResourceSet* are not restricted by initial DL BWP. +- UE is not required to receive TRS occasions outside the initial DL BWP. +- the periodicity for periodic NZP CSI-RS resources, is given by the higher layer parameter *periodicityAndOffset* configured by a *TRS-ResourceSet*, is one of slots where 10, 20, 40, or 80 and where $\mu$ is defined in Clause 4.3 of [4, TS 38.211], applies to all resources in a *TRS-ResourceSet*. The slot offset given by the higher layer parameter *periodicityAndOffset* configured by a *TRS-ResourceSet* provides the location of the first slot containing the periodic NZP CSI-RS resources configured by a *TRS-ResourceSet*. +- the UE does not expect the *TRS-ResourceSet* to be configured with the periodicity of slots if the bandwidth of NZP CSI-RS resource is larger than 52 resource blocks. +- the UE may assume the sub-carrier spacing of the NZP CSI-RS resources configured by *TRS-ResourceSet* to be same as the sub-carrier spacing of the initial DL BWP. +- *powerControlOffsetSS* given by a *TRS-ResourceSet* applies to all resources in a *TRS-ResourceSet*. +- the QCL information for periodic NZP CSI-RS resources, is given by the higher layer parameter *ssb-Index* configured by a *TRS-ResourceSet*, is a SS/PBCH block, applies to all resources in a *TRS-ResourceSet*. +- One or more scrambling IDs according to *scramblingID-Info* where if a single *scramblingIDforCommon* is configured, it applies to all NZP-CSI-RS resources in the resource set, otherwise, each NZP-CSI-RS resource is provided with a scrambling IDs according to *scramblingIDperResourceListWith2* or *scramblingIDperResourceListWith4*. +- the UE may assume the following quasi co-location type(s): + - 'typeC' with an SS/PBCH block and, when applicable, 'typeD' with the same SS/PBCH block. + +For each *TRS-ResourceSet* the index of the associated bit in TRS availability indication field [5, TS 38.212], is given by the higher layer parameter *indBitID*. + +###### 5.1.6.1.1.1 Aperiodic CSI-RS for tracking for fast SCell activation + +A UE can be configured with aperiodic CSI-RS resources for tracking for an SCell for fast SCell activation using *NZP-CSI-RS-ResourceSet(s)* with the higher layer parameter *scellActivationRS-ConfigToAddModList*, with the QCL relation, provided by higher layer parameter *qcl-Info* given by *SCellActivationRS-Config* as with aperiodic CSI-RS for tracking in clause 5.1.6.1.1. + +Each CSI-RS resource, defined in clause 7.4.1.5.3 of [4, TS 38.211], for fast SCell activation is configured by the higher layer parameter *NZP-CSI-RS-Resource* with the same restrictions as defined for CSI-RS for tracking in clause 5.1.6.1.1. + +##### 5.1.6.1.2 CSI-RS for L1-RSRP and L1-SINR computation + +If a UE is configured with a *NZP-CSI-RS-ResourceSet* configured with the higher layer parameter *repetition* set to 'on', the UE may assume that the CSI-RS resources, described in Clause 5.2.2.3.1, within the *NZP-CSI-RS-ResourceSet* are transmitted with the same downlink spatial domain transmission filter, where the CSI-RS resources in the *NZP-CSI-RS-ResourceSet* are transmitted in different OFDM symbols. If *repetition* is set to 'off', the UE shall not assume that the + +CSI-RS resources within the *NZP-CSI-RS-ResourceSet* are transmitted with the same downlink spatial domain transmission filter. + +If the UE is configured with a *CSI-ReportConfig* with *reportQuantity* set to 'cri-RSRP', 'cri-SINR' or 'none' and if the *CSI-ResourceConfig* for channel measurement (higher layer parameter *resourcesForChannelMeasurement*) contains a *NZP-CSI-RS-ResourceSet* that is configured with the higher layer parameter *repetition* and without the higher layer parameter *trs-Info*, the UE can only be configured with the same number (1 or 2) of ports with the higher layer parameter *nrofPorts* for all CSI-RS resources within the set. If the UE is configured with the CSI-RS resource in the same OFDM symbol(s) as an SS/PBCH block, the UE may assume that the CSI-RS and the SS/PBCH block are quasi co-located with 'typeD' if 'typeD' is applicable. Furthermore, the UE shall not expect to be configured with the CSI-RS in PRBs that overlap with those of the SS/PBCH block, and the UE shall expect that the same subcarrier spacing is used for both the CSI-RS and the SS/PBCH block. + +##### 5.1.6.1.3 CSI-RS for mobility + +If a UE is configured with the higher layer parameter *CSI-RS-Resource-Mobility* and the higher layer parameter *associatedSSB* is not configured, the UE shall perform measurements based on *CSI-RS-Resource-Mobility* and the UE may base the timing of the CSI-RS resource on the timing of the serving cell. + +If a UE is configured with the higher layer parameters *CSI-RS-Resource-Mobility* and *associatedSSB*, the UE may base the timing of the CSI-RS resource on the timing of the cell given by the *cellId* of the CSI-RS resource configuration. Additionally, for a given CSI-RS resource, if the associated SS/PBCH block is configured but not detected by the UE, the UE is not required to monitor the corresponding CSI-RS resource. The higher layer parameter *isQuasiColocated* indicates whether the associated SS/PBCH block given by the *associatedSSB* and the CSI-RS resource(s) are quasi co-located with respect to 'typeD', when applicable. + +If a UE is configured with the higher layer parameter *CSI-RS-Resource-Mobility* and with periodicity greater than 10 msec in paired spectrum, the UE may assume the absolute value of the time difference between radio frame *i* between any two cells, listed in the configuration with the higher layer parameter *CSI-RS-CellMobility* and with same *refFreqCSI-RS*, is less than 153600 *Ts*. + +If the UE is configured with DRX, the UE is not required to perform measurement of CSI-RS resources other than during the active time for measurements based on *CSI-RS-Resource-Mobility*. When the UE is configured to monitor DCI format 2\_6, the UE is not required to perform measurements other than during the active time and during the timer duration indicated by *drx-onDurationTimer* in *DRX-Config* also outside active time based on *CSI-RS-Resource-Mobility*. + +If the UE is configured with DRX and DRX cycle in use is larger than 80 msec, the UE may not expect CSI-RS resources are available other than during the active time for measurements based on *CSI-RS-Resource-Mobility*. If the UE is configured with DRX and configured to monitor DCI format 2\_6 and DRX cycle in use is larger than 80 msec, the UE may not expect that the CSI-RS resources are available other than during the active time and during the time duration indicated by *drx-onDurationTimer* in *DRX-Config* also outside active time for measurements based on *CSI-RS-Resource-Mobility*. Otherwise, the UE may assume CSI-RS are available for measurements based on *CSI-RS-Resource-Mobility*. + +A UE configured with the higher layer parameters *CSI-RS-Resource-Mobility* may expect to be configured + +- with no more than 96 CSI-RS resources per higher layer parameter *MeasObjectNR* for UEs not supporting [*increasedNumberOfCSIRSPerMO-r16*] when all CSI-RS resources configured by the same higher layer parameter *MeasObjectNR* have been configured with *associatedSSB*, or, +- with no more than 192 CSI-RS resources per higher layer parameter *MeasObjectNR* for UEs supporting [*increasedNumberOfCSIRSPerMO-r16*] when all CSI-RS resources configured by the same higher layer parameter *MeasObjectNR* have been configured with *associatedSSB*, or, +- with no more than 64 CSI-RS resources per higher layer parameter *MeasObjectNR* when all CSI-RS resources have been configured without *associatedSSB* or when only some of the CSI-RS resources have been configured with *associatedSSB* by the same higher layer parameter *MeasObjectNR* +- For frequency range 1 the *associatedSSB* is optionally present for each CSI-RS resource. +- For frequency range 2 the *associatedSSB* is either present for all configured CSI-RS resources or not present for any configured CSI-RS resource per higher layer parameter *MeasObjectNR*. + +For any CSI-RS resource configuration, the UE shall assume that the value for parameter *cdm-Type* is 'noCDM', and there is only one antenna port. + +#### 5.1.6.2 DM-RS reception procedure + +The DM-RS reception procedures for PDSCH scheduled by PDCCH with DCI format 1\_1 described in this clause equally apply to PDSCH scheduled by PDCCH with DCI format 1\_2, by applying the parameters of *dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2* and *dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2* instead of *dmrs-DownlinkForPDSCH-MappingTypeA* and *dmrs-DownlinkForPDSCH-MappingTypeB*. The DM-RS reception procedures for PDSCH scheduled by PDCCH with DCI format 1\_1 described in this clause equally apply to PDSCH scheduled by PDCCH with DCI format 1\_3. + +The DM-RS reception procedures for PDSCH scheduled by PDCCH with DCI format 1\_1 described in this clause equally apply to PDSCH scheduled by PDCCH with DCI format 4\_2, by applying the parameters of *dmrs-DownlinkForPDSCH-MappingTypeA* and *dmrs-DownlinkForPDSCH-MappingTypeB* in *pdsch-ConfigMulticast* instead of *dmrs-DownlinkForPDSCH-MappingTypeA* and *dmrs-DownlinkForPDSCH-MappingTypeB* in *PDSCH-Config*. + +When receiving PDSCH scheduled by DCI format 1\_0, 4\_0, or 4\_1, or receiving PDSCH before dedicated higher layer configuration of any of the parameters *dmrs-AdditionalPosition*, *maxLength* and *dmrs-Type*, the UE shall assume that the PDSCH is not present in any symbol carrying DM-RS except for PDSCH with allocation duration of 2 symbols with PDSCH mapping type B (described in clause 7.4.1.1.2 of [4, TS 38.211]), and a single symbol front-loaded DM-RS of configuration type 1 on DM-RS port 1000 is transmitted, and that all the remaining orthogonal antenna ports are not associated with transmission of PDSCH to another UE and in addition + +- For PDSCH with mapping type A and type B, the UE shall assume *dmrs-AdditionalPosition*='pos2' and up to two additional single-symbol DM-RS present in a slot according to the PDSCH duration indicated in the DCI as defined in Clause 7.4.1.1 of [4, TS 38.211], and +- For PDSCH with allocation duration of 2 symbols with mapping type B, the UE shall assume that the PDSCH is present in the symbol carrying DM-RS. + +When receiving PDSCH scheduled by DCI format 1\_1 or 1\_3 by PDCCH with CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI or DCI format 4\_2 by PDCCH with CRC scrambled by G-RNTI for multicast or G-CS-RNTI, + +- the UE may be configured with the higher layer parameter *dmrs-Type* and/or *enhanced-dmrs-Type\_r18*, and the configured DM-RS configuration type is used for receiving PDSCH in as defined in Clause 7.4.1.1 of [4, TS 38.211]. +- the UE may be configured with the maximum number of front-loaded DM-RS symbols for PDSCH by higher layer parameter *maxLength* given by *DMRS-DownlinkConfig*. + - if *maxLength* is set to 'len1', single-symbol DM-RS can be scheduled for the UE by DCI, and the UE can be configured with a number of additional DM-RS for PDSCH by higher layer parameter *dmrs-AdditionalPosition*, which can be set to 'pos0', 'pos1', 'pos2' or 'pos3'. + - if *maxLength* is set to 'len2', both single-symbol DM-RS and double symbol DM-RS can be scheduled for the UE by DCI, and the UE can be configured with a number of additional DM-RS for PDSCH by higher layer parameter *dmrs-AdditionalPosition*, which can be set to 'pos0' or 'pos1'. +- and the UE shall assume to receive additional DM-RS as specified in Table 7.4.1.1.2-3 and Table 7.4.1.1.2-4 as described in Clause 7.4.1.1.2 of [4, TS 38.211]. + +For the UE-specific reference signals generation as defined in Clause 7.4.1.1 of [4, TS 38.211], a UE can be configured by higher layers with one or two scrambling identity(ies), *i* = 0, 1 which are the same for both PDSCH mapping Type A and Type B. + +A UE may be scheduled with a number of DM-RS ports by the antenna port index in DCI format 1\_1 as described in Clause 7.3.1.2 of [5, TS 38.212]. + +For DM-RS configuration type 1, + +- if a UE is scheduled with one codeword and assigned with the antenna port mapping with indices of {2, 9, 10, 11 or 30} in Table 7.3.1.2.2-1 and Table 7.3.1.2.2-2 of Clause 7.3.1.2 of [5, TS 38.212], or + +- if a UE is scheduled with one codeword and assigned with the antenna port mapping with indices of {2, 9, 10, 11 or 12} in Table 7.3.1.2.2-1A and {2, 9, 10, 11, 30 or 31} in Table 7.3.1.2.2-2A of Clause 7.3.1.2 of [5, TS 38.212], or +- if a UE is scheduled with two codewords, + +the UE may assume that all the remaining orthogonal antenna ports are not associated with transmission of PDSCH to another UE. + +For DM-RS configuration type 2, + +- if a UE is scheduled with one codeword and assigned with the antenna port mapping with indices of {2, 10 or 23} in Table 7.3.1.2.2-3 and Table 7.3.1.2.2-4 of Clause 7.3.1.2 of [5, TS 38.212], or +- if a UE is scheduled with one codeword and assigned with the antenna port mapping with indices of {2, 10, 23 or 24} in Table 7.3.1.2.2-3A and {2, 10, 23 or 58} in Table 7.3.1.2.2-4A of Clause 7.3.1.2 of [5, TS 38.212], or +- if a UE is scheduled with two codewords, + +the UE may assume that all the remaining orthogonal antenna ports are not associated with transmission of PDSCH to another UE. + +For DM-RS configuration enhanced type 1, + +- if a UE is scheduled with one codeword and assigned with the antenna port mapping with indices of {9, 10, 11 and 27 when applicable} in Table 7.3.1.2.2-7 and Table 7.3.1.2.2-7A of Clause 7.3.1.2 of [5, TS 38.212], or +- if a UE is scheduled with one codeword and assigned with the antenna port mapping with indices of {9, 10, 11, 39, 40, 41, 42, 43, 44, 45 and 66 when applicable} in Table 7.3.1.2.2-8 and Table 7.3.1.2.2-8A of Clause 7.3.1.2 of [5, TS 38.212], + +the UE may assume that all the remaining orthogonal antenna ports of the CDM groups, from which the antenna ports are indicated to the UE, are not associated with transmission of PDSCH to another UE, or + +- if a UE is scheduled with two codewords, the UE may assume that all the remaining orthogonal antenna ports are not associated with transmission of PDSCH to another UE. + +For DM-RS configuration enhanced type 2, + +- if a UE is scheduled with one codeword and assigned with the antenna port mapping with indices of {9, 10, 20, 21, 22, 23 and 54 when applicable} in Table 7.3.1.2.2-9 and Table 7.3.1.2.2-9A of Clause 7.3.1.2 of [5, TS 38.212], or +- if a UE is scheduled with one codeword and assigned with the antenna port mapping with indices of {9, 10, 20, 21, 22, 23, 72, 73, 74, 75, 76, 77 and 136 when applicable} in Table 7.3.1.2.2-10 and in Table 7.3.1.2.2-10A of Clause 7.3.1.2 of [5, TS 38.212], + +The UE may assume that all the remaining orthogonal antenna ports of CDM groups, from which the antenna ports are indicated to the UE, are not associated with transmission of PDSCH to another UE, or + +- if a UE is scheduled with two codewords, the UE may assume that all the remaining orthogonal antenna ports are not associated with transmission of PDSCH to another UE. + +For DM-RS configuration enhanced type 1, + +- if a UE is configured with the higher layer parameter *repetitionScheme* set to '*fdmSchemeA*' or '*fdmSchemeB*', and is indicated with two TCI states to be applied to the PDSCH, +- if a UE is not indicating UE capability of *[noSchedulingRestrictionForFDMSSchemes-r18]*, the UE shall assume that the number of consecutively scheduled PRBs for PDSCH for each TCI-state is even, and the offset of each set of consecutively scheduled PRB from common resource block 0 for PDSCH for each TCI-state is even number. +- otherwise, + +- if the UE is not indicating UE capability of *[noSchedulingRestriction-r18]*, the UE shall assume the number of consecutively scheduled PRBs for PDSCH is even, and the offset of each set of consecutively scheduled PRB for PDSCH from common resource block 0 is even number. + +If a UE receiving PDSCH scheduled by DCI format 1\_2 is configured with the higher layer parameter *phaseTrackingRS* in *dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2* or *dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2* or a UE receiving PDSCH scheduled by DCI format 1\_0, 1\_1 or 1\_3 is configured with the higher layer parameter *phaseTrackingRS* in *dmrs-DownlinkForPDSCH-MappingTypeA* or *dmrs-DownlinkForPDSCH-MappingTypeB*, the UE may assume that the following configurations are not occurring simultaneously for the received PDSCH: + +- any DM-RS ports among + - 1004-1007 or 1006-1011 for DM-RS configurations type 1 and type 2, respectively or, + - 1004-1007 or 1012-1015 for DM-RS configuration enhanced type 1 or, + - 1006-1011 or 1018-1023 for DM-RS configuration enhanced type 2, + are scheduled for the UE and the other UE(s) sharing the DM-RS REs on the same CDM group(s), and +- PT-RS is transmitted to the UE. + +The UE is not expected to simultaneously be configured with the maximum number of front-loaded DM-RS symbols for PDSCH by higher layer parameter *maxLength* being set equal to 'len2' and more than one additional DM-RS symbol as given by the higher layer parameter *dmrs-AdditionalPosition*. + +The UE is not expected to assume co-scheduled UE(s) with different DM-RS configuration with respect to the actual number of front-loaded DM-RS symbol(s), the actual number of additional DM-RS, the DM-RS symbol location as described in Clause 7.4.1.1 of [4, TS 38.211]. The UE configured with DM-RS configuration type 1 or enhanced type 1 is not expected to assume co-scheduled UE(s) with DM-RS configuration type 2 or enhanced type 2. The UE configured with DM-RS configuration type 2 or enhanced type 2 is not expected to assume co-scheduled UE(s) with DM-RS configuration type 1 or enhanced type 1. + +The UE does not expect the precoding of the potential co-scheduled UE(s) in other DM-RS ports of the same CDM group to be different in the PRG-level grid configured to this UE with PRG=2 or 4. + +When the UE is configured with the higher layer parameter *enhanced-dmrs-Type\_r18* and indicated with at least one DM-RS ports 1008-1015 for enhanced Type 1 DM-RS or DM-RS ports 1012-1023 for enhanced Type 2 DM-RS, the UE does not expect that any co-scheduled UE(s) in the same CDM group is not configured with the higher layer parameter *enhanced-dmrs-Type\_r18*. When the UE is not configured with the higher layer parameter *enhanced-dmrs-Type\_r18*, the UE does not expect that any co-scheduled UE(s) in the same CDM group(s) is configured with the higher layer parameter *enhanced-dmrs-Type\_r18* and indicated with at least one of DMRS ports 1008-1015 for enhanced Type 1 DMRS or DMRS ports 1012-1023 for enhanced Type 2 DMRS. + +The UE does not expect the resource allocation of the potential co-scheduled UE(s) in other DM-RS ports of the same CDM group to be misaligned in the PRG-level grid to this UE with PRG=2 or 4. + +When receiving PDSCH scheduled by DCI format 1\_1, the UE shall assume that the CDM groups indicated in the configured index from Tables 7.3.1.2.2-1, 7.3.1.2.2-1A, 7.3.1.2.2-7, 7.3.1.2.2-7A, 7.3.1.2.2-2, 7.3.1.2.2-2A, 7.3.1.2.2-8, 7.3.1.2.2-8A, 7.3.1.2.2-3, 7.3.1.2.2-3A, 7.3.1.2.2-9, 7.3.1.2.2-9A, 7.3.1.2.2-4, 7.3.1.2.2-4A, 7.3.1.2.2-10, 7.3.1.2.2-10A of [5, TS. 38.212] contain potential co-scheduled downlink DM-RS and are not used for data transmission, where "1", "2" and "3" for the number of DM-RS CDM group(s) in Tables 7.3.1.2.2-1, 7.3.1.2.2-1A, 7.3.1.2.2-7, 7.3.1.2.2-7A, 7.3.1.2.2-2, 7.3.1.2.2-2A, 7.3.1.2.2-8, 7.3.1.2.2-8A, 7.3.1.2.2-3, 7.3.1.2.2-3A, 7.3.1.2.2-9, 7.3.1.2.2-9A, 7.3.1.2.2-4, 7.3.1.2.2-4A, 7.3.1.2.2-10, 7.3.1.2.2-10A of [5, TS. 38.212] correspond to CDM group 0, {0,1}, {0,1,2}, respectively. + +When receiving PDSCH scheduled by DCI format 1\_0, 4\_0, or 4\_1, the UE shall assume the number of DM-RS CDM groups without data is 1 which corresponds to CDM group 0 for the case of PDSCH with allocation duration of 2 symbols, and the UE shall assume that the number of DM-RS CDM groups without data is 2 which corresponds to CDM group {0,1} for all other cases. + +The UE is not expected to receive PDSCH scheduling DCI which indicates CDM group(s) with potential DM-RS ports which overlap with any configured CSI-RS resource(s) for that UE. + +If the UE receives the DM-RS for PDSCH and an SS/PBCH block associated with the same PCI in the same OFDM symbol(s), then the UE may assume that the DM-RS and SS/PBCH block are quasi co-located with 'typeD', if 'typeD' is applicable. Furthermore, the UE shall not expect to receive DM-RS in resource elements that overlap with those of the SS/PBCH block associated with the same PCI as the DM-RS, and the UE can expect that the same or different subcarrier spacing is configured for the DM-RS and SS/PBCH block in a CC except for the case of 240 kHz where only different subcarrier spacing is supported. A DM-RS for PDSCH is said to be associated with an additional PCI if the indicated TCI state for the PDSCH is associated with the additional PCI, otherwise a DM-RS for PDSCH is associated with serving cell PCI. + +If at least one TCI codepoint indicates two TCI states for a UE not configured with *dl-OrJointTCI-StateList*, or if the UE configured with *dl-OrJointTCI-StateList* is having two indicated TCI states and the UE receives the DM-RS for PDSCH and an SS/PBCH block in the same OFDM symbol(s), then the UE may assume that at least one DM-RS port for the PDSCH and SS/PBCH block are quasi co-located with 'QCL-TypeD', if 'QCL-TypeD' is applicable. + +If the UE is configured by higher layer parameter *PDCCH-Config* that contains two different values of *CORESETPoolIndex* in different *ControlResourceSets*, and the UE receives the DM-RS for PDSCH(s) and an SS/PBCH block in the same OFDM symbol(s), then the UE may assume that at least one DM-RS port for the PDSCH(s) and SS/PBCH block are quasi co-located with 'QCL-TypeD', if 'QCL-TypeD' is applicable. + +If a UE is configured by the higher layer parameter *PDCCH-Config* that contains two different values of *coresetPoolIndex* in *ControlResourceSet*, the UE may be scheduled with fully or partially overlapping PDSCHs in the time and frequency domain by multiple PDCCHs with the following restrictions, + +- the UE is not expected to assume different DM-RS configuration with respect to the actual number of front-loaded DM-RS symbol(s), the actual number of additional DM-RS symbol(s), the actual DM-RS symbol location, and DM-RS configuration type. +- the UE is not expected to assume DM-RS ports in a CDM group indicated by two TCI states. + +When a UE is not indicated with a DCI that DCI field '*Time domain resource assignment*' indicating an entry which contains *repetitionNumber* in *PDSCH-TimeDomainResourceAllocation*, the UE is not configured with *sfnSchemePDSCH* and it is indicated with two TCI states to be applied to the PDSCH and indicated DM-RS port(s) within two CDM groups in the DCI field '*Antenna Port(s)*', + +- the first TCI state corresponds to the CDM group of the first antenna port indicated by the antenna port indication table, and the second TCI state corresponds to the other CDM group. + +If a UE is configured with higher layer parameter *dmrs-FD-OCC-DisabledForRank1-PDSCH* and the UE is scheduled with PDSCH with single DM-RS port, the UE may assume that set of orthogonal DM-RS antenna ports from the same CDM group using different set of $w_i(k')$ codes are not associated with the transmission of PDSCH to another UE. If a UE is configured with higher layer parameter *enhanced-dmrs-Type\_r18*, the UE does not expect to be configured with *dmrs-FD-OCC-DisabledForRank1-PDSCH*. + +#### 5.1.6.3 PT-RS reception procedure + +The procedures on PT-RS reception described in this clause apply to a UE receiving PDSCH scheduled by DCI format 1\_2 configured with the higher layer parameter *phaseTrackingRS* in *dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2* or *dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2* and to a UE receiving PDSCH scheduled by DCI format 1\_0, 1\_1 or 1\_3 configured with the higher layer parameter *phaseTrackingRS* in *dmrs-DownlinkForPDSCH-MappingTypeA* or *dmrs-DownlinkForPDSCH-MappingTypeB*. The procedures on PT-RS reception described in this clause apply to a UE receiving PDSCH scheduled by DCI format 4\_1 or 4\_2 configured with the higher layer parameter *phaseTrackingRS* in *dmrs-DownlinkForPDSCH-MappingTypeA* or *dmrs-DownlinkForPDSCH-MappingTypeB* in *pdsch-ConfigMulticast*. + +A UE shall report the preferred MCS and bandwidth thresholds based on the UE capability at a given carrier frequency, for each subcarrier spacing applicable to data channel at this carrier frequency, assuming the MCS table with the maximum Modulation Order as it reported to support. + +If a UE is configured with the higher layer parameter *phaseTrackingRS* in *DMRS-DownlinkConfig*, + +- the higher layer parameters *timeDensity* and *frequencyDensity* in *PTRS-DownlinkConfig* indicate the threshold values $ptrs-MCS_i$ , $i=1,2,3$ and $N_{RB,i}$ , $i=0,1$ , as shown in Table 5.1.6.3-1 and Table 5.1.6.3-2, respectively. + +- if either or both of the additional higher layer parameters *timeDensity* and *frequencyDensity* are configured, and the RNTI equals MCS-C-RNTI, C-RNTI or CS-RNTI, the UE shall assume the PT-RS antenna port' presence and pattern is a function of the corresponding scheduled MCS of the corresponding codeword and scheduled bandwidth in corresponding bandwidth part as shown in Table 5.1.6.3-1 and Table 5.1.6.3-2, +- if the higher layer parameter *timeDensity* given by *PTRS-DownlinkConfig* is not configured, the UE shall assume $L_{PT-RS} = 1$ . +- if the higher layer parameter *frequencyDensity* given by *PTRS-DownlinkConfig* is not configured, the UE shall assume $K_{PT-RS} = 2$ . +- otherwise, if neither of the additional higher layer parameters *timeDensity* and *frequencyDensity* are configured and the RNTI equals MCS-C-RNTI, C-RNTI or CS-RNTI, the UE shall assume the PT-RS is present with $L_{PT-RS} = 1$ , $K_{PT-RS} = 2$ , and the UE shall assume PT-RS is not present when + - the scheduled MCS from Table 5.1.3.1-1 is smaller than 10, or + - the scheduled MCS from Table 5.1.3.1-2 is smaller than 5, or + - the scheduled MCS from Table 5.1.3.1-3 is smaller than 15, or + - the scheduled MCS from Table 5.1.3.1-4 is smaller than 3, or + - the number of scheduled RBs is smaller than 3, or +- otherwise, if the RNTI equals RA-RNTI, [MSGB-RNTI], SI-RNTI, or P-RNTI, the UE shall assume PT-RS is not present + +**Table 5.1.6.3-1: Time density of PT-RS as a function of scheduled MCS** + +| Scheduled MCS | Time density ( $L$ ) | +|----------------------------------------|----------------------| +| $l_{MCS} < ptrs-MCS_1$ | PT-RS is not present | +| $ptrs-MCS_1 \leq l_{MCS} < ptrs-MCS_2$ | 4 | +| $ptrs-MCS_2 \leq l_{MCS} < ptrs-MCS_3$ | 2 | +| $ptrs-MCS_3 \leq l_{MCS} < ptrs-MCS_4$ | 1 | + +**Table 5.1.6.3-2: Frequency density of PT-RS as a function of scheduled bandwidth** + +| Scheduled bandwidth | Frequency density ( $K$ ) | +|---------------------------------|---------------------------| +| $N_{RB} < N_{RB0}$ | PT-RS is not present | +| $N_{RB0} \leq N_{RB} < N_{RB1}$ | 2 | +| $N_{RB1} \leq N_{RB}$ | 4 | + +If a UE is not configured with the higher layer parameter *phaseTrackingRS* in *DMRS-DownlinkConfig*, the UE assumes PT-RS is not present. + +The higher layer parameter *PTRS-DownlinkConfig* provides the parameters *ptrs-MCSi*, $i=1,2,3$ and with values in range 0-29 when MCS Table 5.1.3.1-1 or MCS Table 5.1.3.1-3 is used and 0-28 when MCS Table 5.1.3.1-2 is used, and 0-27 when MCS Table 5.1.3.1-4 is used, respectively. *ptrs-MCS4* is not explicitly configured by higher layers but assumed 29 when MCS Table 5.1.3.1-1 or MCS Table 5.1.3.1-3 is used and 28 when MCS Table 5.1.3.1-2 is used and 27 when MCS Table 5.1.3.1-4 is used, respectively. The higher layer parameter *frequencyDensity* in *PTRS-DownlinkConfig* provides the parameters $N_{RBi}$ $i=0,1$ with values in range 1-276. + +If the higher layer parameter *PTRS-DownlinkConfig* indicates that the time density thresholds $ptrs-MCS_i = ptrs-MCS_{i+1}$ , then the time density $L_{PT-RS}$ of the associated row where both these thresholds appear in Table 5.1.6.3-1 is disabled. If the higher layer parameter *PTRS-DownlinkConfig* indicates that the frequency density thresholds $N_{RBi} = N_{RBi+1}$ , then the frequency density $K_{PTRS}$ of the associated row where both these thresholds appear in Table 5.1.6.3-2 is disabled. + +If either or both of the parameters PT-RS time density ( $L_{PT-RS}$ ) and PT-RS frequency density ( $K_{PT-RS}$ ), shown in Table 5.1.6.3-1 and Table 5.1.6.3-2, indicates that 'PT-RS not present', the UE shall assume that PT-RS is not present. + +When the UE is receiving a PDSCH with allocation duration of 2 symbols as defined in Clause 7.4.1.1.2 of [4, TS 38.211] and if $L_{PT-RS}$ is set to 2 or 4, the UE shall assume PT-RS is not transmitted. + +When the UE is receiving a PDSCH with allocation duration of 4 symbols and if $L_{PT-RS}$ is set to 4, the UE shall assume PT-RS is not transmitted. + +When a UE is receiving PDSCH for retransmission, if the UE is scheduled with an MCS index greater than V, where V=28 for MCS Table 5.1.3.1-1 and Table 5.1.3.1-3, and V=27 for MCS Table 5.1.3.1-2, and V=26 for MCS Table 5.1.3.1-4 respectively, the MCS for the PT-RS time-density determination is obtained from the DCI received for the same transport block in the initial transmission, which is smaller than or equal to V. + +The DL DM-RS port(s) associated with a PT-RS port are assumed to be quasi co-located with respect to 'typeA' and 'typeD'. If a UE is scheduled with one codeword, the PT-RS antenna port is associated with the lowest indexed DM-RS antenna port among the DM-RS antenna ports assigned for the PDSCH. + +If a UE is scheduled with two codewords, the PT-RS antenna port is associated with the lowest indexed DM-RS antenna port among the DM-RS antenna ports assigned for the codeword with the higher MCS. If the MCS indices of the two codewords are the same, the PT-RS antenna port is associated with the lowest indexed DM-RS antenna port assigned for codeword 0. + +When a UE is not indicated with a DCI that DCI field '*Time domain resource assignment*' indicating an entry which contains *repetitionNumber* in *PDSCH-TimeDomainResourceAllocation*, and if the UE is configured with the higher layer parameter *maxNrofPorts* equal to *n2*, the UE is not configured with *sfnSchemePDSCH* and if the UE not configured with *dl-OrJointTCI-StateList* is indicated with two TCI states by the codepoints of the DCI field '*Transmission Configuration Indication*' or when the UE configured with *dl-OrJointTCI-StateList* and having two indicated TCI States to be applied to PDSCH, and indicated DM-RS port(s) within two CDM groups in the DCI field '*Antenna Port(s)*', the UE shall receive two PT-RS ports which are associated to the lowest indexed DM-RS port among the DM-RS ports corresponding to the first/second indicated TCI state, respectively. + +When a UE configured by the higher layer parameter *repetitionScheme* set to 'fdmSchemeA' or 'fdmSchemeB', and the UE not configured with *dl-OrJointTCI-StateList* is indicated with two TCI states in a codepoint of the DCI field '*Transmission Configuration Indication*' or when the UE configured with *dl-OrJointTCI-StateList* and having two indicated TCI States to be applied to PDSCH, and indicated DM-RS port(s) within one CDM group in the DCI field '*Antenna Port(s)*', the UE shall receive a single PT-RS port which is associated with the lowest indexed DM-RS antenna port among the DM-RS antenna ports assigned for the PDSCH, a PT-RS frequency density is determined by the number of PRBs associated to each TCI state, and a PT-RS resource element mapping is associated to the allocated PRBs for each TCI state. + +#### 5.1.6.4 SRS reception procedure for CLI + +The SRS resources defined in Clause 6.4.1.4 of [4, TS 38.211] may be configured for SRS-RSRP measurement for CLI, as defined in Clause 5.1.19 of [7, TS 38.215]. The UE is not expected to measure SRS-RSRP with a subcarrier spacing other than the one configured for the active BWP confining the SRS resource. The UE is not expected to measure SRS-RSRP using the SRS-RSRP measurement resource which is not fully confined within the DL active BWP. The UE is not expected to measure more than 32 SRS resources, and the UE is not expected to receive more than 8 SRS resources in a slot. + +#### 5.1.6.5 PRS reception procedure + +The UE can be configured with one or more DL PRS resource set configuration(s) as indicated by the higher layer parameters *NR-DL-PRS-ResourceSet* and *NR-DL-PRS-Resource* as defined by Clause 6.4.3 [17, TS 37.355]. Each DL PRS resource set consists of $K \geq 1$ DL PRS resource(s) where each has an associated spatial transmission filter. The UE can be configured with one or more DL PRS positioning frequency layer configuration(s) as indicated by the higher layer parameter *NR-DL-PRS-PositioningFrequencyLayer*. A DL PRS positioning frequency layer is defined as a collection of DL PRS resource sets which have common parameters configured by *NR-DL-PRS-PositioningFrequencyLayer*. + +The UE assumes that the following parameters for each DL PRS resource(s) are configured via higher layer parameters *NR-DL-PRS-PositioningFrequencyLayer*, *NR-DL-PRS-ResourceSet* and *NR-DL-PRS-Resource*. + +A DL PRS positioning frequency layer is configured by *NR-DL-PRS-PositioningFrequencyLayer*, consists of one or more DL PRS resource sets and it is defined by: + +- *dl-PRS-SubcarrierSpacing* defines the subcarrier spacing for the DL PRS resource. All DL PRS resources and DL PRS resource sets in the same DL PRS positioning frequency layer have the same value of *dl-PRS-SubcarrierSpacing*. The supported values of *dl-PRS-SubcarrierSpacing* are given in Table 4.2-1 of [4, TS38.211], excluding the values of 240kHz, 480 kHz, and 960 kHz. +- *dl-PRS-CyclicPrefix* defines the cyclic prefix for the DL PRS resource. All DL PRS Resources and DL PRS Resource sets in the same DL PRS positioning frequency layer have the same value of *dl-PRS-CyclicPrefix*. The supported values of *dl-PRS-CyclicPrefix* are given in Table 4.2-1 of [4, TS38.211]. +- *dl-PRS-PointA* defines the absolute frequency of the reference resource block. Its lowest subcarrier is also known as Point A. All DL PRS resources belonging to the same DL PRS resource set have common Point A and all DL PRS resources sets belonging to the same DL PRS positioning frequency layer have a common Point A. + +The UE expects that it will be configured with *dl-PRS-ID* each of which is defined such that it is associated with multiple DL PRS resource sets. The UE expects that one of these *dl-PRS-ID* along with a *nr-DL-PRS-ResourceSetID* and a *nr-DL-PRS-ResourceID-r16* can be used to uniquely identify a DL PRS resource. + +The UE may be configured by the network with *nr-PhysCellID*, *nr-CellGlobalID*, and *nr-ARFCN* [17, TS 37.355] associated with a *dl-PRS-ID*. + +- If *nr-PhysCellID* or *nr-CellGlobalID* is provided, and if *nr-PhysCellID*, *nr-CellGlobalID* and *nr-ARFCN* associated with the *dl-PRS-ID*, if provided, are the same as the corresponding information of a serving cell, the UE may assume that the DL PRS is transmitted from the serving cell; +- Otherwise, the UE may assume that the DL PRS is not transmitted from a serving cell. + +If the UE assumes that the DL PRS is transmitted from a serving cell, and if the serving cell is the same as the serving cell defined by the SS/PBCH block, the UE may assume that the DL PRS and the SS/PBCH block are transmitted from the same serving cell. + +If the UE assumes that the DL PRS is not transmitted from a serving cell, and if *nr-PhysCellID* is provided, and is the same as physical cell ID of the SS/PBCH block from a non-serving cell of the same band as the DL PRS, the UE may assume that the DL PRS and the SS/PBCH block are transmitted from the same non-serving cell. + +A DL PRS resource set is configured by *NR-DL-PRS-ResourceSet*, consists of one or more DL PRS resources and it is defined by: + +- *nr-DL-PRS-ResourceSetID* defines the identity of the DL PRS resource set configuration. +- *dl-PRS-Periodicity-and-ResourceSetSlotOffset* defines the DL PRS resource periodicity and takes values slots, where for *dl-PRS-SubcarrierSpacing*=15, 30, 60 and 120 kHz respectively and the slot offset for DL PRS resource set with respect to SFN0 slot 0. All the DL PRS resources within one DL PRS resource set are configured with the same DL PRS resource periodicity. The UE does not expect that the product of DL PRS resource periodicity, the higher layer parameter *dl-prs-MutingBitRepetitionFactor* and the size of the bitmap of *dl-PRS-MutingOption1* exceeds, where for *dl-PRS-SubcarrierSpacing*=15, 30, 60 and 120 kHz respectively. +- *dl-PRS-ResourceRepetitionFactor* defines how many times each DL-PRS resource is repeated for a single instance of the DL-PRS resource set and takes values. All the DL PRS resources within one resource set have the same resource repetition factor. +- *dl-PRS-ResourceTimeGap* defines the offset in number of slots between two repeated instances of a DL PRS resource with the same *nr-DL-PRS-ResourceID* within a single instance of the DL PRS resource set. The UE only expects to be configured with *dl-PRS-ResourceTimeGap* if *dl-PRS-ResourceRepetitionFactor* is configured with value greater than 1. The time duration spanned by one instance of a *nr-DL-PRS-ResourceSet* is not expected to exceed the configured value of DL PRS periodicity. All the DL PRS resources within one resource set have the same value of *dl-PRS-ResourceTimeGap*. +- *dl-PRS-MutingOption1* and *dl-PRS-MutingOption2* define the time locations where the DL PRS resource is expected to not be transmitted for a DL PRS resource set. If *dl-PRS-MutingOption1* is configured, each bit in the bitmap of *dl-PRS-MutingOption1* corresponds to a configurable number provided by higher layer parameter *dl-prs-MutingBitRepetitionFactor* of consecutive instances of a DL PRS resource set where all the DL PRS resources within the set are muted for the instance that is indicated to be muted. The length of the bitmap can be {2, 4, 6, 8, 16, 32} bits. If *dl-PRS-MutingOption2* is configured each bit in the bitmap of *dl-PRS-MutingOption2* corresponds to a single repetition index for each of the DL PRS resources within each instance of a *nr-DL-PRS-* + +*ResourceSet* and the length of the bitmap is equal to the values of *dl-PRS-ResourceRepetitionFactor*. Both *dl-PRS-MutingOption1* and *dl-PRS-MutingOption2* may be configured at the same time in which case the logical AND operation is applied to the bit maps as described in Clause 7.4.1.7.4 of [4, TS 38.211]. + +- *NR-DL-PRS-SFN0-Offset* defines the time offset of the SFN0 slot 0 for the DL PRS resource set with respect to SFN0 slot 0 of reference provided by *nr-DL-PRS-ReferenceInfo*. +- *dl-PRS-ResourceList* determines the DL PRS resources that are contained within one DL PRS resource set. +- *dl-PRS-CombSizeN* defines the comb size of a DL PRS resource where the allowable values are given in Clause 7.4.1.7.3 of [TS38.211]. All DL PRS resource sets belonging to the same DL PRS positioning frequency layer have the same value of *dl-PRS-CombSizeN*. +- *dl-PRS-ResourceBandwidth* defines the number of resource blocks configured for DL PRS transmission. The parameter has a granularity of 4 PRBs with a minimum of 24 PRBs and a maximum of 272 PRBs. All DL PRS resources sets within a DL PRS positioning frequency layer have the same value of *dl-PRS-ResourceBandwidth*. +- *dl-PRS-StartPRB* defines the starting PRB index of the DL PRS resource with respect to reference Point A, where reference Point A is given by the higher-layer parameter *dl-PRS-PointA*. The starting PRB index has a granularity of one PRB with a minimum value of 0 and a maximum value of 2176 PRBs. All DL PRS resource sets belonging to the same DL PRS positioning frequency layer have the same value of *dl-PRS-StartPRB*. +- *dl-PRS-NumSymbols* defines the number of symbols of the DL PRS resource within a slot where the allowable values are given in Clause 7.4.1.7.3 of [4, TS38.211]. + +A DL PRS resource is defined by: + +- *nr-DL-PRS-ResourceID* determines the DL PRS resource configuration identity. All DL PRS resource IDs are locally defined within a DL PRS resource set. +- *dl-PRS-SequenceID* is used to initialize $c_{init}$ value used in pseudo random generator as described in Clause 7.4.1.7.2 of [4, TS 38.211] for generation of DL PRS sequence for a given DL PRS resource. +- *dl-PRS-CombSizeN-AndReOffset* defines the starting RE offset of the first symbol within a DL PRS resource in frequency. The relative RE offsets of the remaining symbols within a DL PRS resource are defined based on the initial offset and the rule described in Clause 7.4.1.7.3 of [4, TS 38.211]. +- *dl-PRS-ResourceSlotOffset* determines the starting slot of the DL PRS resource with respect to corresponding DL PRS resource set slot offset. +- *dl-PRS-ResourceSymbolOffset* determines the starting symbol of a slot configured with the DL PRS resource. +- *dl-PRS-QCL-Info* defines any quasi co-location information of the DL PRS resource with other reference signals. The DL PRS may be configured with QCL 'typeD' with a DL PRS associated with the same *dl-PRS-ID*, or with *rs-Type* set to 'typeC', 'typeD', or 'typeC-plus-typeD' with a SS/PBCH Block from a serving or non-serving cell. +- *dl-PRS-ResourcePrioritySubset* defines a subset of DL-PRS resources for the DL PRS resource for the purpose of prioritization of measurement reporting as described in [17, TS 37.355]. + +The UE assumes constant EPRE is used for all REs of a given DL PRS resource. + +The UE may be indicated by the network that DL PRS resource(s) can be used as the reference for the DL RSTD, DL PRS-RSRP, DL PRS-RSRPP, and UE Rx-Tx time difference measurements in a higher layer parameter *nr-DL-PRS-ReferenceInfo*. The reference indicated by the network to the UE can also be used by the UE to determine how to apply higher layer parameters *nr-DL-PRS-ExpectedRSTD* and *nr-DL-PRS-ExpectedRSTD-Uncertainty*. The UE expects the reference to be indicated whenever it is expected to receive the DL PRS. This reference provided by *nr-DL-PRS-ReferenceInfo* may include a *dl-PRS-ID*, a DL PRS resource set ID, and optionally a single DL PRS resource ID or a list of DL PRS resource IDs [17, TS 37.355]. The UE may use different DL PRS resources or a different DL PRS resource set to determine the reference for the RSTD measurement as long as the condition that the DL PRS resources used belong to a single DL PRS resource set is met. If the UE chooses to use a different reference than indicated by the network, then it is expected to report the *dl-PRS-ID*, the DL PRS resource ID(s) or the DL PRS resource set ID used to determine the reference. + +The UE may be configured to report quality metrics *NR-TimingQuality* corresponding to the DL RSTD and UE Rx-Tx time difference measurements which include the following fields: + +- *timingQualityValue* which provides the best estimate of the uncertainty of the measurement +- *timingQualityResolution* which specifies the resolution levels used in the *timingQualityValue* field. + +The UE expects to be configured with higher layer parameter *nr-DL-PRS-ExpectedRSTD*, which defines the time difference with respect to the received DL subframe timing the UE is expected to receive DL PRS, and *nr-DL-PRS-ExpectedRSTD-Uncertainty*, which defines a search window around the *nr-DL-PRS-ExpectedRSTD*. + +For DL UE positioning measurement reporting in higher layer parameters *NR-DL-TDOA-SignalMeasurementInformation* or *NR-Multi-RTT-SignalMeasurementInformation* the UE can be configured to report the DL PRS resource ID(s) or the DL PRS resource set ID(s) associated with the DL PRS resource(s) or the DL PRS resource set(s) which are used in determining the UE measurements DL RSTD, or UE Rx-Tx time difference, respectively. + +For the DL RSTD, DL PRS-RSRP, DL PRS-RSRPP, and UE Rx-Tx time difference measurements the UE reports an associated higher layer parameter *nr-TimeStamp*. The *nr-TimeStamp* can include the *dl-PRS-ID*, the SFN and the slot number for a subcarrier spacing. These values correspond to the reference which is provided by *nr-DL-PRS-ReferenceInfo*. + +The UE is expected to measure the DL PRS resource outside the active DL BWP or with a numerology different from the numerology of the active DL BWP if the measurement is made during a configured measurement gap. When the UE is expected to measure the DL PRS resource, the UE may request a measurement gap via higher layer parameter *NR-PRS-MeasurementInfoList* [12, TS 38.331] or as specified in clause 6.1.3.40 of [10, TS 38.321]. The UE may be preconfigured with one or more measurement gaps each associated with a *measPosPreConfigGapId*. When the UE requests activation or deactivation of a measurement gap as specified in clause 6.1.3.40 of [10, TS 38.321] it can request one of the preconfigured measurement gaps by referring to the *measPosPreConfigGapId*. The UE may have one of the preconfigured measurement gap(s) activated or deactivated as specified in clause 6.1.3.41 of [10, TS 38.321]. + +The UE assumes that the DL PRS from the serving cell is not mapped to any symbol that contains SS/PBCH block from the serving cell. If the time frequency location of the SS/PBCH block transmissions from non-serving cells are provided to the UE then the UE also assumes that the DL PRS from a non-serving cell is not mapped to any symbol that contains the SS/PBCH block of the same non-serving cell. + +The UE may be configured to measure and report, subject to UE capability, up to 4 DL RSTD measurements per pair of *dl-PRS-ID* with each measurement between a different pair of DL PRS resources or DL PRS resource sets within the DL PRS configured for those *dl-PRS-ID*. If the UE is not configured to report with *multiMeasInSameReport-r17*, the up to 4 measurements being performed on the same pair of *dl-PRS-ID* and all DL RSTD measurements in the same report use a single reference timing. If the UE is configured to report with *multiMeasInSameReport-r17*, the up to 4 measurements being performed on the same pair of *dl-PRS-ID* and all DL RSTD measurements in the same measurement instance of the same report use a single reference timing. + +The UE may be configured to measure and report, subject to UE capability, up to 24 DL PRS-RSRP measurements on DL PRS resources associated with the same *dl-PRS-ID*. When the UE reports DL PRS-RSRP measurements from one DL PRS resource set, the UE may indicate which DL PRS-RSRP measurements associated with the same higher layer parameter *nr-DL-PRS-RxBeamIndex* [17, TS 37.355] have been performed using the same spatial domain filter for reception if for each *nr-DL-PRS-RxBeamIndex* reported there are at least 2 DL PRS-RSRP measurements associated with it within the DL PRS resource set. When the UE reports DL PRS-RSRP measurements for a DL PRS resource, the reported multiple DL PRS-RSRP measurements associated with the same or different higher layer parameter *nr-DL-PRS-RxBeamIndex* may have the same or different timestamps. + +The UE may be configured to measure and optionally report, subject to UE capability, up to 24 DL PRS-RSRPP for the first detected path on DL PRS resources associated with the same *dl-PRS-ID*. When the UE reports DL PRS-RSRPP measurements for a DL PRS resource, the reported multiple DL PRS-RSRPP measurements associated with the same or different higher layer parameter *nr-DL-PRS-RxBeamIndex* may have the same or different timestamps. When the UE reports DL PRS-RSRPP measurements from one DL PRS resource set, the UE may indicate which DL PRS-RSRPP measurements associated with the same higher layer parameter *nr-DL-PRS-RxBeamIndex* [17, TS 37.355] have been performed using the same spatial domain filter for reception if for each *nr-DL-PRS-RxBeamIndex* reported there are at least 2 DL PRS-RSRPP measurements associated with it within the DL PRS resource set. + +The UE may be configured to optionally report a differential DL PRS-RSRPP for a DL PRS resource with reference to *nr-DL-PRS-FirstPathRSRP-Result* and/or a differential DL PRS RSRP with reference to *nr-DL-PRS-RSRP-Result* via higher layer parameter *NR-DL-AoD-AdditionalMeasurementElement*. + +For each DL PRS resource, the UE may be configured, subject to UE capability, with *dl-PRS-ResourcePrioritySubset* that is associated with this DL PRS resource, where the subset of DL PRS resources associated with the DL PRS resource can be in the same or different DL PRS resource set than the DL PRS resource. The UE may include UE measurements for the subset of DL PRS resources in *NR-DL-AoD-AdditionalMeasurementElement* if the UE measurements of the associated PRS resource are reported, where the UE measurement can be DL PRS-RSRP and/or DL PRS-RSRPP. The UE may report DL PRS-RSRP and/or DL PRS-RSRPP measurements only for the subset of DL PRS resources. Subject to UE capability, the UE may be configured with boresight direction via higher layer parameter *DL-PRS-BeamInfoElement* for each DL PRS resource. + +The UE may be provided with beam/antenna information via higher layer parameter *NR-TRP-BeamAntennaInfo*. + +The UE may request to be provided with either expected DL-AoD/ZoD and uncertainty range(s) of expected DL-AoD/ZoD, or expected DL-AoA/ZoA and uncertainty range(s) of the expected DL-AoA/ZoA. The UE may be provided with expected DL-AoD/ZoD and uncertainty range(s) of the expected DL-AoD/ZoD. The UE may be provided with expected DL-AoA/ZoA and uncertainty range(s) of the expected DL-AoA/ZoA. The uncertainty range(s) of the expected DL-AoD/DL-AoA may be configured within [0, 60]. The uncertainty range(s) of expected DL-ZoD/DL-ZoA may be configured within [0, 30]. + +The UE may be configured to measure and report, subject to UE capability, up to 4 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 resource set which can be in different DL PRS positioning frequency layers. + +The UE may be configured to measure and report via higher layer parameter *additionalPaths* or *additionalPathsExt*, subject to UE capability, the timing and the quality metrics of up to 8 additional detected paths, that are associated with each RSTD or UE Rx – Tx time difference. The timing of each additional path is reported relative to the path timing used for determining *nr-RSTD* or *nr-UE-RxTxTimeDiff*. For UE positioning measurement reporting in higher layer parameters *NR-DL-TDOA-SignalMeasurementInformation* or *NR-Multi-RTT-SignalMeasurementInformation*, the UE may be configured to measure and report, subject to UE capability, the DL PRS-RSRPP of the first path and the up to 8 additional paths that are associated with each RSTD or UE Rx – Tx time difference. + +The UE may be requested, subject to UE capability, to measure and report one or more of the DL RSTD, DL PRS-RSRP, DL PRS-RSRPP, or UE Rx-Tx time difference measurements with either 1 or 2 samples, where 1 or 2 is as defined in [11, TS 38.133], via higher layer parameter *reducedDL-PRS-ProcessingSamples* [17, TS 37.355] which applies for all DL PRS positioning frequency layers. + +The UE may be requested, subject to UE capability, to report LoS/NLoS indicator(s) via higher layer parameter *nr-los-nlos-IndicatorRequest*. The UE can report LoS/NLoS indicator(s) via higher layer parameter *nr-los-nlos-Indicator* associated with each DL RSTD, DL PRS-RSRP, DL PRS-RSRPP, and UE Rx-Tx time difference measurements. The UE can report LoS/NLoS indicator(s) via higher layer parameter *nr-los-nlos-Indicator* associated with each *dl-PRS-ID* in a measurement report. For the LoS/NLoS indicator(s) associated with DL RSTD, the UE may report one indicator associated with the *dl-PRS-ID* indicated by higher layer parameter *dl-PRS-ReferenceInfo* and one indicator associated with the *dl-PRS-ID* of the DL RSTD measurement. A UE may be provided with LoS/NLoS indicator(s) via higher layer parameter *nr-los-nlos-Indicator*, and it may be associated with each DL PRS resource of each configured *dl-PRS-ID* or may be associated with each configured *dl-PRS-ID*. The values of the higher layer parameter *LOS-NLOS-Indicator* may be soft values (0, 0.1, ..., 0.9, 1) or hard values (0, 1) with the values corresponding to the likelihood of LoS, with a value of 1 corresponding to LoS and a value of 0 corresponding to NLoS. + +If the UE is configured with *DL-PRS-QCL-Info* and the QCL relation is between two DL PRS resources, then the UE assumes those DL PRS resources are associated with the same *dl-PRS-ID*. If *DL-PRS-QCL-Info* is configured to the UE with QCL set to 'type-D' with a source DL PRS resource then the *nr-DL-PRS-ResourceSetId* and the *nr-DL-PRS-ResourceId* of the source DL PRS resource are expected to be indicated to the UE. + +The UE is expected to measure the DL PRS outside the measurement gap, subject to UE capability, if the DL PRS is inside the active DL BWP and has the same numerology as the active DL BWP and is within the DL PRS processing window indicated by higher layer parameter *DL-PPW-PreConfig*. The UE is not expected to measure the DL PRS outside the measurement gap if the expected received timing difference between the DL PRS from the non-serving cell and that from the serving cell, determined by the higher layer parameters *nr-DL-PRS-ExpectedRSTD* and *nr-DL-PRS-ExpectedRSTD-Uncertainty*, is larger than maximum Rx timing difference provided by UE capability. For receiving the DL PRS outside the measurement gap and within the DL PRS processing window, the priority between DL PRS and SSB is defined in [11, TS 38.133] and the UE determines the DL PRS priority as indicated by higher layer parameter *priority* subject to UE capability or as implied by UE capability, except for SSB: + +- with value '*st1*' where the DL PRS is higher priority than all the DL signals and channels, or +- with value '*st2*' where the DL PRS is lower priority than PDCCH and the PDSCH scheduled by DCI formats 1\_1, 1\_2, 1\_3 or 4\_2 with the priority indicator field in the corresponding DCI format set to 1, and is higher priority than other DL signals and channels, or +- with value '*st3*' where the DL PRS is lower priority than all the DL signals and channels. + +Inside one *DL-PPW-PreConfig* the UE is only expected to measure a single DL PRS positioning frequency layer. + +When the UE is expected to measure the DL PRS outside the measurement gap in a configured DL PRS processing window with *type1A* and if the DL PRS is determined to be higher priority than the DL signals and channels inside the DL PRS processing window, those DL signals and channels are not expected to be measured by the UE. When the UE is expected to measure the DL PRS outside the measurement gap in a configured DL PRS processing window with *type1B* and if the DL PRS is determined to be higher priority than the DL signals and channels inside the DL PRS processing window, those DL signals and channels in the same band as the DL PRS are not expected to be measured by the UE. When the UE is expected to measure the DL PRS outside the measurement gap in a configured DL PRS processing window with *type2* if the DL PRS is determined to be higher priority than the DL signals and channels inside the DL PRS processing window, those DL signals and channels from the impacted serving cells are not expected to be measured by the UE on the overlapped symbols with the DL PRS, where impacted serving cells refer to the serving cell on which the *DL-PPW-PreConfig* is configured for a frequency range 1 band, and all the serving cells in the same band as the DL PRS for a frequency range 2 band. When the UE is expected to measure the DL PRS outside the measurement gap in a configured DL PRS processing window with *type1B* or *type2*, and if the DL PRS is determined to be higher priority than the DL signals and channels inside the DL PRS processing window, the UE behavior is described in [11, TS 38.133] for inter-band case for frequency range 2 for the DL signals/channels from a different frequency range 2 band than the frequency range 2 band of the DL PRS. + +When the UE has an activated DL PRS processing window with *type1A* or *type1B* and the UE determines the presence of other DL signals and channels, except SSB, of higher priority than the DL PRS in the DL PRS processing window no later than *N2* symbols, defined in clause 6.4 for the subcarrier spacing of the DL PRS, before the first symbol of the DL PRS processing window, the UE is expected to receive the other DL signals and channels and drop all PRS within the DL PRS processing window. When the UE has an activated DL PRS processing window with *type2* and the UE determines the presence of other DL signals and channels, except SSB, of higher priority than the DL PRS on a symbol configured with the DL PRS no later than *N2* symbols, defined in clause 6.4 for the subcarrier spacing of the DL PRS, before the DL PRS symbol, the UE is expected to receive the other DL signals and channels and drop the DL PRS symbol. + +When the UE has an activated DL PRS processing window with *type1A* or *type1B* and the UE determines the presence of other DL signals and channels, except SSB, of higher priority than the DL PRS in the DL PRS processing window later than *N2* symbols, defined in clause 6.4 for the subcarrier spacing of the DL PRS, before the first symbol of the DL PRS processing window, the UE is not required to receive the other DL signals and channels and may receive the DL PRS and consider the DL PRS as higher priority in the DL PRS processing window. When the UE has an activated DL PRS processing window with *type2* and the UE determines the presence of other DL signals and channels, except SSB, of higher priority than the DL PRS on a symbol configured with the DL PRS later than *N2* symbols, defined in clause 6.4 for the subcarrier spacing of the DL PRS, before the DL PRS symbols, the UE is not required to receive the other DL signals and channels and may receive the DL PRS symbol and consider the DL PRS as higher priority in that symbol. + +Within a positioning frequency layer, the DL PRS resources are sorted in the decreasing order of priority for measurement to be performed by the UE, with the reference indicated by *nr-DL-PRS-ReferenceInfo* being the highest priority for measurement, and the following priority is assumed: + +- Up to 64 *NR-SelectedDL-PRS-IndexPerTRP* of the DL PRS positioning frequency layer are sorted according to priority if *nr-SelectedDL-PRS-IndexListPerFreq* is provided, or up to 64 *NR-DL-PRS-AssistanceDataPerTRP* of the frequency layer are sorted according to priority otherwise; except when the UE is requested to perform aggregated measurement(s), in which case: + - A [*dl-PRS-ID* or *nr-SelectedTRP-Index*] associated with DL PRS bandwidth aggregation linkage has higher priority than a [*dl-PRS-ID* or *nr-SelectedTRP-Index*] not associated with DL PRS bandwidth aggregation linkage. If [multiple *dl-PRS-ID(s)* or *nr-SelectedTRP-Index(s)*] are associated with DL PRS bandwidth aggregation linkage, they are sorted according to priority. + +- Up to 2 *DL-SelectedPRS-ResourceSetIndex* per *dl-PRS-ID* of the DL PRS positioning frequency layer are sorted according to priority if *dl-SelectedPRS-ResourceSetIndexList* is provided, or up to 2 *NR-DL-PRS-ResourceSet* per *dl-PRS-ID* of the DL PRS positioning frequency layer are sorted according to priority otherwise. Except when the UE is requested to perform aggregated measurement(s), in which case: +- A DL PRS resource set linked for a DL PRS bandwidth aggregation has higher priority than a DL PRS resource set not linked for DL PRS bandwidth aggregation. If multiple DL PRS resource sets are linked for DL PRS bandwidth aggregation, then they are sorted according to priority. + +The UE DL PRS processing capability is defined in [TS 37.355]. For the purpose of DL PRS processing capability, the duration *K* msec of DL PRS symbols within *P* msec window, is calculated by + +- Type 1 duration calculation with UE symbol level buffering capability +- Type 2 duration calculation with UE slot level buffering capability +- *S* is the set of slots based on the numerology of the DL PRS of a serving cell within the *P* msec window in the positioning frequency layer that contains potential DL PRS resources considering the actual *nr-DL-PRS-ExpectedRSTD*, *nr-DL-PRS-ExpectedRSTD-Uncertainty* provided for each pair of DL PRS Resource Sets. +- For Type 1, is the smallest interval in msec within slot corresponding to an integer number of OFDM symbols based on the numerology of the DL PRS of a serving cell that covers the union of the potential DL PRS symbols and determines the DL PRS symbol occupancy within slot, where the interval considers the actual *nr-DL-PRS-ExpectedRSTD*, *nr-DL-PRS-ExpectedRSTD-Uncertainty* provided for each pair of DL PRS resource sets (target and reference). +- For Type 2, is the numerology of the DL PRS, and is the cardinality of the set. + +The UE may be configured to report one or more measurement instances, each with its own timestamp, on DL RSTD, DL PRS-RSRP, DL PRS-RSRPP, and/or UE Rx-Tx time difference measurements, in a single measurement report. + +Timing Error Group(s) (TEG(s)) at UE side are defined: + +- UE Rx TEG is associated with one or more DL measurements, which have the Rx timing error difference within a certain margin. +- UE RxTx TEG is associated with one or more UE Rx-Tx time difference measurements, which have the 'Rx timing errors+Tx timing errors' difference within a certain margin. + +The UE may be configured to report, subject to UE capability, via high layer parameter *nr-UE-RxTEG-Request*, the association information of DL RSTD measurement(s) with UE Rx TEG(s) via higher layer parameter *nr-UE-Rx-TEG-ID* when the UE reports the DL RSTD measurement(s). The UE may report up to 4 RSTD measurements associated with different DL PRS resources per UE Rx TEG per *dl-PRS-ID*. + +The UE may report a UE Rx TEG ID via higher layer parameter *nr-UE-Rx-TEG-ID* for a RSTD reference time *dl-PRS-ReferenceInfo* and a UE Rx TEG ID for each DL RSTD measurement, where the DL RSTD can be DL RSTD measurement in *NR-DL-TDOA-MeasElement* and/or *NR-DL-TDOA-AdditionalMeasurementElement*. + +If the UE reports a UE Rx TEG ID with a DL RSTD measurement, the UE may report a UE Rx TEG timing error margin value, via high layer parameter *nr-UE-RxTEG-TimingErrorMargin*, for all the UE Rx TEGs within one *NR-DL-TDOASignalMeasurementInformation*. + +The UE may be configured to measure and report, via high layer parameter *measureSameDL-PRS-ResourceWithDifferentRxTEGs* subject to UE capability, RSTD measurements on a DL PRS resource associated with a *dl-PRS-ID* using up to 8 different UE Rx TEGs with the same *dl-PRS-ReferenceInfo*. The higher layer parameter *measureSameDL-PRS-ResourceWithDifferentRxTEGs* applies to all DL PRS positioning frequency layers. + +The UE may be provided with association information of DL PRS resource(s) with TRP Tx TEGs via higher layer parameter *dl-prs-trp-Tx-TEG-ID* for a *dl-PRS-ID*. + +The UE may be configured to report, via high layer parameter *nr-UE-RxTxTEG-Request*, subject to UE capability, the association information of UE Rx-Tx time difference measurement(s) with UE RxTx TEG(s) via higher layer parameter + +*nr-UE-RxTx-TEG-ID*. The UE may report up to 4 UE Rx-Tx time difference measurements associated with different DL PRS resources per UE RxTx TEG per *dl-PRS-ID*. + +If the UE reports a UE RxTx TEG ID with a UE Rx-Tx time difference measurement, the UE may report a UE RxTx TEG timing error margin value, via high layer parameter *nr-UE-RxTxTEG-TimingErrorMargin*, for all the UE RxTx TEGs within one *NR-Multi-RTT-SignalMeasurementInformation*. + +The UE may be configured to report, via high layer parameter *nr-UE-RxTxTEG-Request*, subject to UE capability, the association information of UE Rx-Tx time difference measurement(s) with the UE Rx TEG(s) and UE Tx TEG(s) via the higher layer parameters of *nr-UE-Rx-TEG-ID*, and *nr-UE-Tx-TEG-Index*. The UE may report up to 4 UE Rx-Tx time difference measurements associated with different DL PRS resources per UE Rx TEG per *dl-PRS-ID*. + +If the UE reports a UE Rx TEG ID with a UE Rx-Tx time difference measurement, the UE may report a UE Rx TEG timing error margin value, via high layer parameter *nr-UE-RxTEG-TimingErrorMargin*, for all the UE Rx TEGs within one *NR-Multi-RTT-SignalMeasurementInformation*. + +The UE may be configured to measure and report, via high layer parameter *measureSameDL-PRS-ResourceWithDifferentRxTEGs* subject to UE capability, UE Rx-Tx time difference measurements on a PRS resource associated with a *dl-PRS-ID* using up to 8 different UE Rx TEGs. The high layer parameter *measureSameDL-PRS-ResourceWithDifferentRxTEGs* applies to all DL PRS positioning frequency layers. + +The UE may be configured to measure and report, via high layer parameter *measureSameDL-PRS-ResourceWithDifferentRxTxTEGs* subject to UE capability, UE Rx-Tx time difference measurements with the same UE Tx TEG using up to 8 different UE RxTx TEGs. The high layer parameter *measureSameDL-PRS-ResourceWithDifferentRxTxTEGs* applies to all DL PRS positioning frequency layers. + +The UE may be configured to measure and report, via higher layer parameter [undetermined NTN related parameter] subject to UE capability, UE Rx-Tx time difference measurements on a PRS resource associated with a *dl-PRS-ID*, and report the UE Rx-Tx time difference subframe offset and the DL timing drift as described in [7, TS 38.215]. + +The UE in RRC\_INACTIVE mode is expected to prioritize the reception of any other DL signals and DL channels than the reception of DL PRS. + +The UE in RRC\_INACTIVE mode, subject to UE capability, is expected to process DL PRS outside or inside of the initial DL BWP. For DL PRS processing outside of the initial DL BWP, the UE may be configured with the same or different subcarrier spacing and CP for DL PRS resources than those of the initial DL BWP. For DL PRS processing inside of the initial DL BWP, the UE is configured with the same subcarrier spacing and CP for DL PRS resources as those of the initial DL BWP. + +For a UE configured with preconfigured Measurement gap(s) for Positioning, when the UE receives an activation command, as described in clause 6.1.3.41 of [10, TS 38.321], for a preconfigured Measurement Gap for Positioning activation/deactivation, and when the UE would transmit a PUCCH with HARQ-ACK information in slot $n$ corresponding to the PDSCH carrying the command, the corresponding actions in [10, TS 38.321] and the UE assumptions shall be applied starting from the first slot that is after slot $n$ where $\mu$ is the SCS configuration for the PUCCH. + +For a UE configured with DL PRS Processing Window(s), when the UE receives an activation/deactivation command, as described in clause 6.1.3.42 of [10, TS 38.321], for a DL PRS processing window activation, and when the UE would transmit a PUCCH with HARQ-ACK information in slot $n$ corresponding to the PDSCH carrying the command, the corresponding actions in [10, TS 38.321] and the UE assumptions shall be applied starting from the first slot that is after slot $n$ where $\mu$ is the SCS configuration for the PUCCH. The UE is not expected to be indicated with more than 4 activated DL PRS processing windows across all active DL BWPs and is not expected to be indicated with the activated DL PRS processing windows that overlap in time. + +The UE, subject to UE capability, may be requested via [higher layer parameter] to perform DL RSCPD and/or DL RSCP measurements on indicated DL PRS resource sets occurring within one or more-two time window(s) indicated by [*nr-timeWindowConfig-DL-Measurements*]. Within each window indicated by [*nr-timeWindowConfig-DL-Measurements*], the UE expects that the indicated DL PRS resource sets across all *dl-PRS-IDs* are from one DL PRS positioning frequency layer, and that the number of indicated DL PRS resource sets associated with each *dl-PRS-ID* are the same. + +The UE, subject to UE capability, may be requested to perform DL RSTD, UE Rx – Tx time difference, DL PRS-RSRP, and DL PRS-RSRPP measurement on the indicated DL PRS resource sets only within the window(s) indicated by [*nr-timeWindowConfig-DL-Measurements*]. + +##### 5.1.6.5.1 PRS receiver frequency hopping + +The reduced capability UE may be configured to measure and report, subject to UE capability, via *[nr-Requested-DL-PRS-measurementBasedOnMultihopRx]* the DL RSTD, DL PRS-RSRP, DL PRS-RSRPP, or UE Rx-Tx time difference using receiver frequency hopping for a DL PRS resource, with a requested bandwidth of all hops that may be greater than the maximum reduced capability UE bandwidth. The reduced capability UE performing receiver frequency hopping may report via *[higher layer parameter]* one measurement associated with one received frequency hop or one measurement based on multiple hops of the DL PRS. The reduced capability UE may report whether the measurement is associated with one received frequency hop or multiple frequency hops of the DL PRS. In RRC\_CONNECTED mode, the reduced capability UE is expected to use a single instance of a configured measurement gap to receive all hops of the DL PRS using receiver frequency hopping. + +##### 5.1.6.5.2 PRS for carrier phase positioning + +For DL UE positioning measurement reporting in higher layer parameter *NR-DL-TDOA-SignalMeasurementInformation*, the UE may be configured to report the DL Reference Signal Carrier Phase Difference (RSCPD) [7, TS 38.215] measurement along with the DL RSTD. When the UE reports RSCPD measurements, the reference *nr-DL-PRS-ReferenceInfo* is the same as the one reported, for the RSTD measurements. For DL UE positioning measurement reporting in higher layer parameter *NR-Multi-RTT-SignalMeasurementInformation*, the UE may be configured to report the DL Reference Signal Carrier Phase (RSCP) measurement [7, TS 38.215] along with the UE Rx-Tx time difference measurement. When the UE reports DL RSCPD measurement(s) along with DL RSTD measurement(s) or DL RSCP measurement(s) along with UE Rx-Tx time difference measurement(s), the DL RSCPD and/or DL RSCP measurement(s) should be measured from a single DL PRS positioning frequency layer. + +The UE is expected to obtain each DL RSCP or DL RSCPD measurement with as defined in [11, TS 38.133]. If the UE reports a DL RSTD measurement with $\geq 2$ or 4 samples as defined in [11, TS 38.133], up to DL RSCPD measurements can be reported associated with the DL RSTD measurement. If the UE reports a UE Rx-Tx time difference measurement with $\geq 2$ or 4 samples as defined in [11, TS 38.133], up to DL RSCP measurements can be reported associated with the UE Rx-Tx time difference measurement. Each DL RSCP or DL RSCPD measurement has its own timestamp. + +When the UE reports a timestamp associated with a DL RSCP measurement or a DL RSCPD measurement, subject to UE capability, it may include a symbol index in the timestamp. + +If the UE reports LoS/NLoS indicator(s) via higher layer parameter *nr-los-nlos-Indicator* along with a measurement report containing DL RSCP or DL RSCPD the LoS/NLoS indicator(s) are assumed to also apply to the DL RSCP or DL RSCPD measurements. + +The UE may be provided with *[nr-PruInformation-Ue-based-DL-CPP]* which contains DL RSCP/RSCPD measurements together with DL RSTD, DL PRS-RSRP, and/or DL PRS-RSRPP measurement(s) associated with the RSCP/RSCPD measurements performed by a positioning reference unit (PRU) [20, TS 38.305] the timestamps associated with the measurements, and the location information of the PRU. + +The UE may be configured to report quality metrics *[nr-CarrierPhaseQualityInfo]* corresponding to the DL RSCP and RSCPD measurements which include the following fields [17, TS 37.355]: + +- *[phase quality index]* which provides the uncertainty of the measurement +- *[phase quality resolution]* which specifies the resolution levels used in the *[phase quality index]* field. + +The UE in RRC\_INACTIVE or RRC\_IDLE mode is expected to perform the DL carrier phase measurement from the bandwidth of a DL PRS resource including outside of the initial downlink bandwidth part. + +##### 5.1.6.5.3 PRS bandwidth aggregation for positioning measurements + +When the UE is expected to perform aggregated measurements for bandwidth aggregation across DL PRS positioning frequency layers, the UE expects to be configured with linkage information, via higher layer parameter *[nr-linked-DL-PRS-ResourceSetIDList-PrsAggregation]*, between DL PRS resource sets across DL PRS positioning frequency layers. For the linked DL PRS resource sets, the UE is expected to be configured with the same values of QCL, *dl-PRS-Periodicity-and-ResourceSetSlotOffset*, *dl-PRS-NumSymbols*, *dl-PRS-ResourceTimeGap*, *dl-PRS-ResourceRepetitionFactor*, *dl-PRS-ResourceSymbolOffset*, *dl-prs-MutingBitRepetitionFactor*, *dl-PRS-* + +*CyclicPrefix*, comb size, power per subcarrier, *NR-MutingPattern*, and *NR-DL-PRS-SFN0-Offset*, and the UE is expected to be configured with DL PRS resources that maintain uniformly spaced DL PRS RE pattern within a symbol across aggregated DL PRS positioning frequency layers. The UE assumes that DL PRS resources across the linked DL PRS resource sets which satisfy the above conditions are linked for bandwidth aggregation, and the UE may assume phase continuity on the DL PRS resources on same symbol(s); otherwise, the UE does not assume that PRS resources from the linked DL PRS resource sets are linked for bandwidth aggregation. + +The UE may be configured to measure and report, subject to UE capability, up to 4 aggregated DL RSTD measurement(s) per pair of *dl-PRS-ID*, from aggregated DL PRS resources across two or three DL PRS positioning frequency layers. + +The UE may be configured to measure and report, subject to UE capability, up to 4 aggregated UE Rx-Tx time difference measurement(s) from aggregated DL PRS resources across two or three DL PRS positioning frequency layers. + +The UE may be requested via higher layer parameter [*nr-linked-DL-FreqLayerIndexList-PrsAggregation*] to perform the aggregated DL RSTD measurement(s) or the aggregated UE Rx-Tx time difference measurement(s) across two or three DL PRS positioning frequency layers. + +The UE may report via higher layer parameter [*nr-RSTD-BasedOnAggregatedResources*] or *nr-UE-RxTxTimeDiff-BasedOnAggregatedResources* in a measurement report whether the aggregated DL RSTD measurement(s) or the aggregated UE Rx-Tx time difference measurement(s) is performed. If any aggregated measurement is performed, the two or three DL PRS positioning frequency layers to be used may also be reported by reporting PRS resource set IDs. + +If the UE reports a DL PRS-RSRP or a DL PRS-RSRPP with aggregated DL RSTD measurement(s) or aggregated UE Rx-Tx time difference measurement(s), the DL PRS-RSRP or the DL PRS-RSRPP correspond to the aggregated DL PRS resources across two or three DL PRS positioning frequency layers. + +### 5.1.7 Code block group based PDSCH transmission + +If a UE is configured to receive code block group (CBG) based transmissions by receiving the higher layer parameter *PDSCH-CodeBlockGroupTransmission* in *PDSCH-ServingCellConfig* on a serving cell in a PUCCH group, the UE does not expect to be configured with higher layer parameter *ScheduledCell-ListDCI-1-3* on any serving cell within the PUCCH group. + +#### 5.1.7.1 UE procedure for grouping of code blocks to code block groups + +If a UE is configured to receive code block group (CBG) based transmissions by receiving the higher layer parameter *PDSCH-CodeBlockGroupTransmission* for PDSCH, the UE shall determine the number of CBGs for a transport block reception as + +, + +where $N$ is the maximum number of CBGs per transport block as configured by *maxCodeBlockGroupsPerTransportBlock* for PDSCH, and $C$ is the number of code blocks in the transport block according to the procedure defined in Clause 7.2.3 of [5, TS 38.212]. + +Define , , and . + +If , CBG $m$ , consists of code blocks with indices . CBG $m$ , consists of code blocks with indices . + +#### 5.1.7.2 UE procedure for receiving code block group based transmissions + +If a UE is configured to receive code block group-based transmissions by receiving the higher layer parameter *PDSCH-CodeBlockGroupTransmission* for PDSCH, + +- The '*CBG transmission information*' (CBGTI) field of DCI format 1\_1 is of length bits, where is the value of the higher layer parameter *maxNrofCodeWordsScheduledByDCI*. If the CBGTI field bits are mapped such that the first set of bits starting from the MSB corresponds to the first TB while the second set of bits corresponds to a second TB, if scheduled. The first $M$ bits of each set of bits in the CBGTI field have an in-order one-to-one mapping with the $M$ CBGs of the TB, with the MSB mapped to CBG#0. + +- For initial transmission of a TB as indicated by the '*New Data Indicator*' field of the scheduling DCI, the UE may assume that all the code block groups of the TB are present. +- For a retransmission of a TB as indicated by the '*New Data Indicator*' field of the scheduling DCI, the UE may assume that + - The '*CBGTI*' field of the scheduling DCI indicates which CBGs of the TB are present in the transmission. A bit value of '0' in the *CBGTI* field indicates that the corresponding CBG is not transmitted and '1' indicates that it is transmitted. + - If the '*CBG flushing out information*' (*CBGFI*) field of the scheduling DCI is present, '*CBGFI*' set to '0' indicates that the earlier received instances of the same CBGs being transmitted may be corrupted, and '*CBGFI*' set to '1' indicates that the CBGs being retransmitted are combinable with the earlier received instances of the same CBGs. +- A CBG contains the same CBs as in the initial transmission of the TB. + +## 5.2 UE procedure for reporting channel state information (CSI) + +### 5.2.1 Channel state information framework + +The procedures on aperiodic CSI reporting described in this clause assume that the CSI reporting is triggered by DCI format 0\_1, but they equally apply to CSI reporting triggered by DCI format 0\_2, by applying the higher layer parameter *reportTriggerSizeDCI-0-2* instead of *reportTriggerSize*. The procedures on aperiodic CSI reporting described in this clause assume that the CSI reporting is triggered by DCI format 0\_1, but they equally apply to CSI reporting triggered by DCI format 0\_3. + +The time and frequency resources that can be used by the UE to report CSI are controlled by the gNB. CSI may consist of Channel Quality Indicator (CQI), precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), SS/PBCH Block Resource indicator (SSBRI), layer indicator (LI), rank indicator (RI), L1-RSRP, L1-SINR, CapabilityIndex or time-domain channel properties (TDCP). + +For CQI, PMI, CRI, SSBRI, LI, RI, L1-RSRP, L1-SINR, CapabilityIndex, TDCP a UE is configured by higher layers with $N \geq 1$ *CSI-ReportConfig* Reporting Settings and/or [ $X \geq 1$ *LTM-CSI-ReportConfig* Reporting Settings], $M \geq 1$ *CSI-ResourceConfig* Resource Settings and/or [ $Y \geq 1$ *LTM-CSI-ResourceConfig* Resource Settings], and one or two list(s) of trigger states (given by the higher layer parameters *CSI-AperiodicTriggerStateList* and *CSI-SemiPersistentOnPUSCH-TriggerStateList*). Each trigger state in *CSI-AperiodicTriggerStateList* contains a list of associated *CSI-ReportConfigs* or *LTM-CSI-ReportConfigs* indicating the Resource Set IDs for channel and optionally for interference where a Resource Set for interference can only be present for a Report Setting given by a *CSI-ReportConfig* and a trigger state additionally contains one or more [*csi-ReportSubConfigID*] if the associated *CSI-ReportConfig* configured with a list of sub-configurations, as described in Clause 5.2.1.1. Each trigger state in *CSI-SemiPersistentOnPUSCH-TriggerStateList* contains one associated *CSI-ReportConfig* [or *LTM-CSI-ReportConfig*], and a trigger state additionally contain one or more [*csi-ReportSubConfigID*] if the associated *CSI-ReportConfig* is configured with a list of sub-configurations, as described in Clause 5.2.1.1. + +#### 5.2.1.1 Reporting settings + +Each Reporting Setting *CSI-ReportConfig* is associated with a single downlink BWP (indicated by higher layer parameter *BWP-Id*) given in the associated *CSI-ResourceConfig* for channel measurement and contains the parameter(s) for one CSI reporting band: codebook configuration including codebook subset restriction, time-domain behavior, frequency granularity for CQI and PMI, measurement restriction configurations, and the CSI-related quantities to be reported by the UE such as the layer indicator (LI), L1-RSRP, L1-SINR, CRI, SSBRI (SSB Resource Indicator), CapabilityIndex and TDCP. + +Each Reporting Setting [*LTM-CSI-ReportConfig*] is associated with a [*LTM-CSI-ResourceConfig*] for channel measurement and contains the parameter(s) for time-domain behavior provided by [*ltm-ReportConfigType*], the number of cells and the number of reference signals per candidate cell provided by [*noOfReportedCells*], and [*noOfReportedRS-PerCell*], respectively, comprising L1 measurement results associated with current SpCell if *spCellInclusion* is configured. + +The time domain behavior of the *CSI-ReportConfig* is indicated by the higher layer parameter *reportConfigType* and can be set to 'aperiodic', 'semiPersistentOnPUCCH', 'semiPersistentOnPUSCH', or 'periodic'. For 'periodic' and 'semiPersistentOnPUCCH'/'semiPersistentOnPUSCH' CSI reporting, the configured periodicity and slot offset applies in + +the numerology of the UL BWP in which the CSI report is configured to be transmitted on. The higher layer parameter *reportQuantity* indicates the CSI-related, L1-RSRP-related, L1-SINR-related, CapabilityIndex-related or TDCP-related quantities to report. The *reportFreqConfiguration* indicates the reporting granularity in the frequency domain, including the CSI reporting band and if PMI/CQI reporting is wideband or sub-band. The *timeRestrictionForChannelMeasurements* parameter in *CSI-ReportConfig* can be configured to enable time domain restriction for channel measurements and *timeRestrictionForInterferenceMeasurements* can be configured to enable time domain restriction for interference measurements. The *CSI-ReportConfig* can also contain *CodebookConfig*, which contains configuration parameters for Type-I, Type II, Enhanced Type II CSI, Further Enhanced Type II Port Selection, Enhanced Type II for coherent joint transmission (CJT), Further Enhanced Type II Port Selection for CJT, Enhanced Type II for predicted PMI, or Further Enhanced Type II Port Selection for predicted PMI including codebook subset restriction when applicable, and configurations of group-based reporting. A UE is not expected to be configured with a CSI report setting associated with a dormant DL BWP if the *reportConfigType* is set to 'aperiodic'. A *CSI-ReportConfig* can contain a list of sub-configurations, provided by the higher layer parameter [*csi-ReportSubConfigList*], where each sub-configuration is identified by [*csi-ReportSubConfigID*] and corresponds to a list of one or more CSI-RS resources or corresponds to a CSI-RS antenna port subset, and/or corresponds to a power offset for PDSCH relative to CSI-RS additional to *powerControlOffset* of the CSI-RS resource(s). A UE is not expected to be configured with a *CSI-ReportConfig* that contains a mix of sub-configuration(s) each corresponding to a list of one or more CSI-RS resources and some other sub-configuration(s) each corresponding to CSI-RS antenna port subset. + +The time domain behavior of [*LTM-CSI-ReportConfig*] is indicated by the higher layer parameter [*ltm-ReportConfigType*] and can be set to 'aperiodic', 'semiPersistentOnPUCCH', 'semiPersistentOnPUSCH', or 'periodic'. For 'periodic' and 'semiPersistentOnPUCCH'/'semiPersistentOnPUSCH' CSI reporting, the configured periodicity and slot offset applies in the numerology of the UL BWP in which the CSI report is configured to be transmitted on. + +#### 5.2.1.2 Resource settings + +Each CSI Resource Setting *CSI-ResourceConfig* contains a configuration of a list of $S \geq 1$ CSI Resource Sets (given by higher layer parameter *csi-RS-ResourceSetList*), where the list is comprised of references to either or both of NZP CSI-RS resource set(s) and SS/PBCH block set(s) or the list is comprised of references to CSI-IM resource set(s). Each CSI Resource Setting is located in the DL BWP identified by the higher layer parameter *BWP-id*, and all CSI Resource Settings linked to a CSI Report Setting have the same DL BWP. + +The time domain behavior of the CSI-RS resources within a CSI Resource Setting are indicated by the higher layer parameter *resourceType* and can be set to aperiodic, periodic, or semi-persistent. For periodic and semi-persistent CSI Resource Settings, when the UE is configured with *groupBasedBeamReporting-r17* or *groupBasedBeamReporting-v18*, the number of CSI Resource Sets configured is $S=2$ , otherwise the number of CSI-RS Resource Sets configured is limited to $S=1$ , except for periodic CSI Resource Settings, when the UE is configured with TDCP reporting, for which the number of CSI-RS Resource Sets in the CSI Resource Setting for channel measurement is $S=1$ and all the CSI-RS Resource Sets are configured with the higher layer parameter *trs-Info*. For periodic and semi-persistent CSI Resource Settings, the configured periodicity and slot offset is given in the numerology of its associated DL BWP, as given by *BWP-id*. When a UE is configured with multiple *CSI-ResourceConfigs* consisting the same NZP CSI-RS resource ID, the same time domain behavior shall be configured for the *CSI-ResourceConfigs*. When a UE is configured with multiple *CSI-ResourceConfigs* consisting the same CSI-IM resource ID, the same time-domain behavior shall be configured for the *CSI-ResourceConfigs*. All CSI Resource Settings linked to a CSI Report Setting shall have the same time domain behavior. + +The following are configured via higher layer signaling for one or more CSI Resource Settings for channel and interference measurement: + +- CSI-IM resource for interference measurement as described in Clause 5.2.2.4. +- NZP CSI-RS resource for interference measurement as described in Clause 5.2.2.3.1. +- NZP CSI-RS resource for channel measurement as described in Clause 5.2.2.3.1. + +The UE may assume that the NZP CSI-RS resource(s) for channel measurement and the CSI-IM resource(s) for interference measurement configured for one CSI reporting are resource-wise QCLed with respect to 'typeD'. When NZP CSI-RS resource(s) is used for interference measurement, the UE may assume that the NZP CSI-RS resource for channel measurement and the CSI-IM resource or NZP CSI-RS resource(s) for interference measurement configured for one CSI reporting are QCLed with respect to 'typeD'. + +For TDCP measurement, one periodic CSI Resource Setting is configured, and the Resource Setting is for channel measurement on CSI-RS for tracking. + +For L1-SINR measurement: + +- When one Resource Setting is configured, the Resource Setting (given by higher layer parameter *resourcesForChannelMeasurement*) is for channel and interference measurement on NZP CSI-RS for L1-SINR computation. UE may assume that same 1 port NZP CSI-RS resource(s) with density 3 REs/RB is used for both channel and interference measurements. +- When two Resource Settings are configured, the first one Resource Setting (given by higher layer parameter *resourcesForChannelMeasurement*) is for channel measurement on SSB or NZP CSI-RS and the second one (given by either higher layer parameter *csi-IM-ResourcesForInterference* or higher layer parameter *nzp-CSI-RS-ResourcesForInterference*) is for interference measurement performed on CSI-IM or on 1 port NZP CSI-RS with density 3 REs/RB, where each SSB or NZP CSI-RS resource for channel measurement is associated with one CSI-IM resource or one NZP CSI-RS resource for interference measurement by the ordering of the SSB or NZP CSI-RS resource for channel measurement and CSI-IM resource or NZP CSI-RS resource for interference measurement in the corresponding resource sets. The number of SSB(s) or CSI-RS resources for channel measurement equals to the number of CSI-IM resources or the number of NZP CSI-RS resource for interference measurement. + - UE may apply the SSB, or 'typeD' RS configured with *qcl-Type* set to 'typeD' to the NZP CSI-RS resource for channel measurement, as the reference RS for determining 'typeD' assumption for the corresponding CSI-IM resource or the corresponding NZP CSI-RS resource for interference measurement configured for one CSI reporting. + - UE may expect that the NZP CSI-RS resource set for channel measurement and the NZP-CSI-RS resource set for interference measurement, if any, are configured with the higher layer parameter *repetition*. + +Each LTM CSI Resource Setting [*LTM-CSI-ResourceConfig*] contains configuration of a [*LTM-CSI-SSB-ResourceSet*] which comprises of a list of $Z \geq 1$ SS/PBCH blocks indices (given by [*ltm-CSI-SSB-ResourceList*]) and a list of $Z$ [*LTM-CandidateIds*] (given by [*ltm-CandidateIDList*]) referring to candidate cells associated with the SS/PBCH block indices. For each candidate cell, the UE determines the time domain behavior of a SS/PBCH block from *ssb-Periodicity* and *ssb-PositionsInBurst* and the frequency domain behavior of a SS/PBCH block is determined by the higher layer parameters *subCarrierSpacing*, *ssbFrequency*. + +#### 5.2.1.3 (void) + +#### 5.2.1.4 Reporting configurations + +The UE shall calculate CSI parameters (if reported) assuming the following dependencies between CSI parameters (if reported) + +- LI shall be calculated conditioned on the reported CQI, PMI, RI and CRI +- CQI shall be calculated conditioned on the reported PMI, RI and CRI +- PMI shall be calculated conditioned on the reported RI and CRI +- RI shall be calculated conditioned on the reported CRI. + +The Reporting configuration for CSI can be aperiodic (using PUSCH), periodic (using PUCCH) or semi-persistent (using PUCCH, and DCI activated PUSCH). The CSI-RS Resources can be periodic, semi-persistent, or aperiodic. Table 5.2.1.4-1 shows the supported combinations of CSI Reporting configurations and CSI-RS Resource configurations and how the CSI Reporting is triggered for each CSI-RS Resource configuration. Periodic CSI-RS is configured by higher layers. Semi-persistent CSI-RS is activated and deactivated as described in Clause 5.2.1.5.2. Aperiodic CSI-RS is configured and triggered/activated as described in Clause 5.2.1.5.1. + +**Table 5.2.1.4-1: Triggering/Activation of CSI Reporting for the possible CSI-RS Configurations.** + +| CSI-RS Configuration | Periodic CSI Reporting | Semi-Persistent CSI Reporting | Aperiodic CSI Reporting | +|------------------------|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| Periodic CSI-RS | No dynamic triggering/activation | For reporting on PUCCH, the UE receives an activation command, as described in clause 6.1.3.16 of [10, TS 38.321]; for reporting on PUSCH, the UE receives triggering on DCI | Triggered by DCI; additionally, subselection indication as described in clause 6.1.3.13 of [10, TS 38.321] possible as defined in Clause 5.2.1.5.1. | +| Semi-Persistent CSI-RS | Not Supported | For reporting on PUCCH, the UE receives an activation command, as described in clause 6.1.3.16 of [10, TS 38.321]; for reporting on PUSCH, the UE receives triggering on DCI | Triggered by DCI; additionally, subselection indication as described in clause 6.1.3.13 of [10, TS 38.321] possible as defined in Clause 5.2.1.5.1. | +| Aperiodic CSI-RS | Not Supported | Not Supported | Triggered by DCI; additionally, subselection indication as described in clause 6.1.3.13 of [10, TS 38.321] possible as defined in Clause 5.2.1.5.1. | + +When the UE is configured with higher layer parameter *NZP-CSI-RS-ResourceSet* and when the higher layer parameter *repetition* is set to 'off', the UE shall determine a CRI from the supported set of CRI values as defined in Clause 6.3.1.1.2 of [5, TS 38.212] and report the number in each CRI report. When the higher layer parameter *repetition* for a CSI-RS Resource Set for channel measurement is set to 'on', CRI for the CSI-RS Resource Set for channel measurement is not reported. CRI reporting is not supported when the higher layer parameter *codebookType* is set to 'typeII', 'typeII-PortSelection', 'typeII-r16', 'typeII-PortSelection-r16', 'typeII-PortSelection-r17', 'typeII-CJT-r18', 'typeII-CJT-PortSelection-r18', 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18'. + +For a periodic or semi-persistent CSI report on PUCCH, the periodicity (measured in slots) and the slot offset are configured by the higher layer parameter *reportSlotConfig*. Unless specified otherwise, the UE shall transmit the CSI report in frames with SFN and slot number within the frame satisfying + +where $\mu$ is the SCS configuration of the UL BWP the CSI report is transmitted on. + +For a semi-persistent CSI report on PUSCH, the periodicity (measured in slots) is configured by the higher layer parameter *reportSlotConfig*. Unless specified otherwise, the UE shall transmit the CSI report in frames with SFN and slot number within the frame satisfying + +where $n_{frame}$ and $n_{slot}$ are the SFN and slot number within the frame respectively of the initial semi-persistent PUSCH transmission according to the activating DCI. + +For a semi-persistent or aperiodic CSI report on PUSCH, the allowed slot offsets are configured by the following higher layer parameters: + +- if triggered/activated by DCI format 0\_2 and the higher layer parameter *reportSlotOffsetListDCI-0-2* or *reportSlotOffsetListDCI-0-2-r17* is configured, the allowed slot offsets are configured by *reportSlotOffsetListDCI-0-2* or *reportSlotOffsetListDCI-0-2-r17*, and +- if triggered/activated by DCI format 0\_1 or 0\_3 and the higher layer parameter *reportSlotOffsetListDCI-0-1* or *reportSlotOffsetListDCI-0-1-r17* is configured, the allowed slot offsets are configured by *reportSlotOffsetListDCI-0-1* or *reportSlotOffsetListDCI-0-1-r17*, and +- otherwise, the allowed slot offsets are configured by the higher layer parameter *reportSlotOffsetList* or *reportSlotOffsetList-r17*. + +The offset is selected in the activating/triggering DCI. + +For CSI reporting, a UE can be configured via higher layer signaling with one out of two possible subband sizes, where a subband is defined as $N_{\text{PRB}}^{\text{SB}}$ contiguous PRBs and depends on the total number of PRBs in the bandwidth part according to Table 5.2.1.4-2. + +**Table 5.2.1.4-2: Configurable subband sizes** + +| Bandwidth part (PRBs) | Subband size (PRBs) | +|-----------------------|---------------------| +| 24 – 72 | 4, 8 | +| 73 – 144 | 8, 16 | +| 145 – 275 | 16, 32 | + +The *reportFreqConfiguration* contained in a *CSI-ReportConfig* indicates the frequency granularity of the CSI Report. A CSI Reporting Setting configuration defines a CSI reporting band as a subset of subbands of the bandwidth part, where the *reportFreqConfiguration* indicates: + +- the *csi-ReportingBand* as a contiguous or non-contiguous subset of subbands in the bandwidth part for which CSI shall be reported. + - A UE is not expected to be configured with *csi-ReportingBand* which contains a subband where a CSI-RS resource linked to the CSI Report setting has the frequency density of each CSI-RS port per PRB in the subband less than the configured density of the CSI-RS resource. + - If a CSI-IM resource is linked to the CSI Report Setting, a UE is not expected to be configured with *csi-ReportingBand* which contains a subband where not all PRBs in the subband have the CSI-IM REs present. +- wideband CQI or subband CQI reporting, as configured by the higher layer parameter *cqi-FormatIndicator*. When wideband CQI reporting is configured, a wideband CQI is reported for each codeword for the entire CSI reporting band. When subband CQI reporting is configured, one CQI for each codeword is reported for each subband in the CSI reporting band. +- wideband PMI or subband PMI reporting as configured by the higher layer parameter *pmi-FormatIndicator*. When wideband PMI reporting is configured, a wideband PMI is reported for the entire CSI reporting band. When subband PMI reporting is configured, except with 2 antenna ports, a single wideband indication ( $i_1$ in Clause 5.2.2.2) is reported for the entire CSI reporting band and one subband indication ( $i_2$ in clause 5.2.2.2) is reported for each subband in the CSI reporting band. When subband PMIs are configured with 2 antenna ports, a PMI is reported for each subband in the CSI reporting band. +- a UE is not expected to be configured with *pmi-FormatIndicator* if *codebookType* is set to 'typeII-r16', 'typeII-PortSelection-r16', 'typeII-PortSelection-r17', 'typeII-CJT-r18', 'typeII-CJT-PortSelection-r18', 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18'. + +A CSI Reporting Setting is said to have a wideband frequency-granularity if + +- *reportQuantity* is set to 'cri-RI-PMI-CQI', or 'cri-RI-LI-PMI-CQI', *cqi-FormatIndicator* is set to 'widebandCQI' and *pmi-FormatIndicator* is set to 'widebandPMI', or +- *reportQuantity* is set to 'cri-RI-PMI-CQI', *codebookType* is set to 'typeII-PortSelection-r17', 'typeII-CJT-PortSelection-r18' or 'typeII-Doppler-PortSelection-r18' with and *cqi-FormatIndicator* is set to 'widebandCQI', or +- *reportQuantity* is set to 'cri-RI-i1' or +- *reportQuantity* is set to 'cri-RI-CQI' or 'cri-RI-i1-CQI' and *cqi-FormatIndicator* is set to 'widebandCQI', or +- *reportQuantity* is set to 'cri-RSRP' or 'ssb-Index-RSRP' or 'cri-SINR', or 'ssb-Index-SINR' or 'cri-RSRP-Index' or 'ssb-Index-RSRP-Index' or 'cri-SINR-Index', or 'ssb-Index-SINR-Index', or +- *reportQuantity* is set to 'tdcp' + +otherwise, the CSI Reporting Setting is said to have a subband frequency-granularity. + +A CSI Reporting Setting with *codebookType* set to 'typeI-SinglePanel' and the corresponding CSI-RS Resource Set for channel measurement configured with two Resource Groups and Resource Pairs, as described in clause 5.2.1.4.1, can be configured with wideband frequency-granularity only if *csi-ReportMode* is set to 'Mode1' and *numberOfSingleTRP-CSI-Mode1* is set to , as described in clause 5.2.1.4.2. + +If the UE is configured with a CSI Reporting Setting for a bandwidth part with fewer than 24 PRBs, the CSI reporting setting is expected to have a wideband frequency-granularity, and, if applicable, the higher layer parameter *codebookType* is set to 'typeI-SinglePanel'. + +The first subband size is given by $N_{PRB}^{SB} - \left( N_{BWP,i}^{start} \bmod N_{PRB}^{SB} \right)$ and the last subband size given by $\left( N_{BWP,i}^{start} + N_{BWP,i}^{size} \right) \bmod N_{PRB}^{SB}$ if $\left( N_{BWP,i}^{start} + N_{BWP,i}^{size} \right) \bmod N_{PRB}^{SB} \neq 0$ and if $\left( N_{BWP,i}^{start} + N_{BWP,i}^{size} \right) \bmod N_{PRB}^{SB} = 0$ + +If a UE is configured with semi-persistent CSI reporting, the UE shall report CSI when both CSI-IM and NZP CSI-RS resources are configured as periodic or semi-persistent. If a UE is configured with aperiodic CSI reporting, the UE shall report CSI when both CSI-IM and NZP CSI-RS resources are configured as periodic, semi-persistent or aperiodic. + +A UE configured with DCI format 0\_1, 0\_2 or 0\_3 does not expect to be triggered with multiple CSI reports with the same *CSI-ReportConfigId*. + +##### 5.2.1.4.1 Resource Setting configuration + +For aperiodic CSI, each trigger state configured using the higher layer parameter *CSI-AperiodicTriggerState* is associated with one or multiple *CSI-ReportConfig* where the *CSI-ReportConfig* not configured with *groupBasedBeamReporting-r17* or *groupBasedBeamReporting-v18* is linked to periodic, or semi-persistent, or aperiodic resource setting(s): + +- When one Resource Setting is configured, the Resource Setting (given by higher layer parameter *resourcesForChannelMeasurement*) is for channel measurement for L1-RSRP or for channel and interference measurement for L1-SINR computation. +- When two Resource Settings are configured, the first one Resource Setting (given by higher layer parameter *resourcesForChannelMeasurement*) is for channel measurement and the second one (given by either higher layer parameter *csi-IM-ResourcesForInterference* or higher layer parameter *nzp-CSI-RS-ResourcesForInterference*) is for interference measurement performed on CSI-IM or on NZP CSI-RS. +- When three Resource Settings are configured, the first Resource Setting (higher layer parameter *resourcesForChannelMeasurement*) is for channel measurement, the second one (given by higher layer parameter *csi-IM-ResourcesForInterference*) is for CSI-IM based interference measurement and the third one (given by higher layer parameter *nzp-CSI-RS-ResourcesForInterference*) is for NZP CSI-RS based interference measurement. + +For aperiodic CSI, and for periodic and semi-persistent CSI resource settings, each trigger state configured using the higher layer parameter *CSI-AperiodicTriggerState* is associated with one or multiple *CSI-ReportConfig* where the *CSI-ReportConfig* configured with *groupBasedBeamReporting-r17* or *groupBasedBeamReporting-v18* is linked to periodic or semi-persistent, setting(s): + +- When one Resource Setting is configured, the Resource setting is given by *resourcesForChannelMeasurement* for L1-RSRP measurement. In such a case, the number of configured CSI Resource Sets in the Resource Setting is $S=2$ + +For aperiodic CSI, and for aperiodic CSI resource settings, each trigger state configured using the higher layer parameter *CSI-AperiodicTriggerState* is associated with one or multiple *CSI-ReportConfig* where the *CSI-ReportConfig* configured with *groupBasedBeamReporting-r17* or *groupBasedBeamReporting-v18* is associated with *resourcesForChannel* and *resourcesForChannel2*, which correspond to first and second resource sets, respectively, for L1-RSRP measurement. + +For semi-persistent or periodic CSI, each *CSI-ReportConfig* is linked to periodic or semi-persistent Resource Setting(s): + +- When one Resource Setting (given by higher layer parameter *resourcesForChannelMeasurement*) is configured, the Resource Setting is for channel measurement for L1-RSRP or for channel and interference measurement for L1-SINR computation. +- When two Resource Settings are configured, the first Resource Setting (given by higher layer parameter *resourcesForChannelMeasurement*) is for channel measurement and the second Resource Setting (given by higher layer parameter *csi-IM-ResourcesForInterference*) is used for interference measurement performed on CSI-IM. For L1-SINR computation, the second Resource Setting (given by higher layer parameter *csi-IM-ResourcesForInterference* or higher layer parameter *nzp-CSI-RS-ResourceForInterference*) is used for interference measurement performed on CSI-IM or on NZP CSI-RS. + +For aperiodic CSI, a UE configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'tdcp' is expected to be configured with one CSI Resource Setting (given by higher layer parameter *resourcesForChannelMeasurement*). The CSI Resource Setting may be periodic, with CSI-RS Resource Sets configured with higher layer parameter *trs-Info*. The support of 3 is subject to UE capability indication. For a periodic *CSI-ResourceConfig*, the UE can assume that all the CSI-RS resources in the CSI-RS Resource Sets share the same QCL-TypeA/C and, if applicable, TypeD. The UE expects that all the CSI-RS resources in the CSI-RS Resource Set(s) are configured with the same bandwidth and subcarrier locations. A UE configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'tdcp' is not expected to be configured with interference measurement on CSI-IM and/or NZP-CSI-RS. + +For a UE configured with [*LTM-CSI-ReportConfig*], the aperiodic, semi-persistent or periodic CSI are associated with one Resource Setting given by [*ltm-ResourcesForChannelMeasurement*] for L1-RSRP measurement. + +A UE is not expected to be configured with more than one CSI-RS resource in resource set for channel measurement for a *CSI-ReportConfig* with the higher layer parameter *codebookType* set to 'typeII', 'typeII-PortSelection', 'typeII-r16', 'typeII-PortSelection-r16', or 'typeII-PortSelection-r17'. A UE is not expected to be configured with more than 64 NZP CSI-RS resources and/or SS/PBCH block resources in resource setting for channel measurement for a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'none', 'cri-RI-CQI', 'cri-RSRP', 'ssb-Index-RSRP', 'cri-SINR' or 'ssb-Index-SINR', 'cri-RSRP- Index', 'ssb-Index-RSRP- Index', 'cri-SINR- Index' or 'ssb-Index-SINR- Index'. If interference measurement is performed on CSI-IM, each CSI-RS resource for channel measurement is resource-wise associated with a CSI-IM resource by the ordering of the CSI-RS resource and CSI-IM resource in the corresponding resource sets. The number of CSI-RS resources for channel measurement equals to the number of CSI-IM resources. + +A UE configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'cri-RI-PMI-CQI' and *codebookType* set to 'typeII-CJT-r18' or 'typeII-CJT-PortSelection-r18' is expected to be configured with CSI-RS resources in a resource set for channel measurement. If interference measurement is performed on CSI-IM, only one resource is configured in the corresponding *csi-IM-ResourceSet*. If interference measurement is performed on NZP CSI-RS, only one resource is configured in the corresponding *NZP-CSI-RS-ResourceSet* for interference measurement. + +A UE configured with a *CSI-ReportConfig* with the higher layer parameter *N4* and *reportQuantity* set to 'cri-RI-PMI-CQI', is expected to be configured with aperiodic CSI-RS resources or with a single periodic or semi-persistent CSI-RS resource in the resource set for channel measurement. For an aperiodic CSI-RS resource set for channel measurement, the CSI-RS resources are triggered by the same triggering instance and the separation between two consecutive CSI-RS resources is slots, which is configured by higher layer parameter in the *NZP-CSI-RS-ResourceSet*. The *K* aperiodic CSI-RS resources are transmitted following the order of the CSI-RS resource IDs configured in the CSI-RS resource set. The UE shall assume that the antenna port with the same port index of the aperiodic CSI-RS resources is the same. If interference measurement is performed on CSI-IM, only one resource is configured in the corresponding *csi-IM-ResourceSet*. If interference measurement is performed on NZP CSI-RS, only one resource is configured in the corresponding *NZP-CSI-RS-ResourceSet* for interference measurement. + +An NZP CSI-RS Resource Set for channel measurement with resources can be configured with two Resource Groups, with resources in Group 1 and resources in Group 2, such that , and with Resource Pairs. Each Resource Pair consists of one resource from Group 1 and one resource from Group 2. The same resource can be associated with two Resource Pairs in frequency range 1 but not in frequency range 2. + +A subset of resources, where a subset contains one or more resources, of a NZP CSI-RS Resource Set for channel measurement corresponds to a sub-configuration contained in a *CSI-ReportConfig* if each of the sub-configuration(s) contains a list of one or more NZP CSI-RS resources, or all the resources of a NZP CSI-RS Resource Set for channel measurement correspond to each of the sub-configuration(s) contained in a *CSI-ReportConfig* if each of the sub-configurations does not contain a list of NZP CSI-RS resources, as described in Clause 5.2.1.4.2. + +Except for L1-SINR, *codebookType* set to 'typeII-CJT-r18', 'typeII-CJT-PortSelection-r18', 'typeII-Doppler-r18', or 'typeII-Doppler-PortSelection-r18', if interference measurement is performed on NZP CSI-RS, a UE does not expect to be configured with more than one NZP CSI-RS resource in the associated resource set within the resource setting for channel measurement. Except for L1-SINR, the UE configured with the higher layer parameter *nzp-CSI-RS-ResourcesForInterference* may expect no more than 18 NZP CSI-RS ports configured in a NZP CSI-RS resource set. + +For CSI measurement(s) other than L1-SINR, a UE assumes: + +- each NZP CSI-RS port configured for interference measurement corresponds to an interference transmission layer. +- all interference transmission layers on NZP CSI-RS ports for interference measurement take into account the associated EPRE ratios configured in 5.2.2.3.1; +- other interference signal on REs of NZP CSI-RS resource for channel measurement, NZP CSI-RS resource for interference measurement, or CSI-IM resource for interference measurement. + +For L1-SINR measurement with dedicated interference measurement resources, a UE assumes: + +- the total received power on dedicated NZP CSI-RS resource for interference measurement or dedicated CSI-IM resource for interference measurement corresponds to interference and noise. + +##### 5.2.1.4.2 Report quantity configurations + +A UE may be configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to either 'none', 'cri-RI-PMI-CQI', 'cri-RI-i1', 'cri-RI-i1-CQI', 'cri-RI-CQI', 'cri-RSRP', 'cri-SINR', 'ssb-Index-RSRP', 'ssb-Index-SINR', 'cri-RI-LI-PMI-CQI', 'cri-RSRP- Index', 'ssb-Index-RSRP- Index', 'cri-SINR- Index', 'ssb-Index-SINR- Index' or 'tdcp'. + +If the UE is configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'none', then the UE shall not report any quantity for the *CSI-ReportConfig*. + +If the UE is configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'cri-RI-PMI-CQI', or 'cri-RI-LI-PMI-CQI', the UE shall report a preferred precoder matrix for the entire reporting band, or a preferred precoder matrix per subband, according to Clause 5.2.2.2. + +If the UE is configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'cri-RI-i1', + +- the UE expects, for that *CSI-ReportConfig*, to be configured with higher layer parameter *codebookType* set to 'typeI-SinglePanel' and *pmi-FormatIndicator* set to 'widebandPMI' and, +- the UE shall report a PMI consisting of a single wideband indication ( $\hat{i}_1$ in Clause 5.2.2.2.1) for the entire CSI reporting band. + +If the UE is configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'cri-RI-i1-CQI', + +- the UE expects, for that *CSI-ReportConfig*, to be configured with higher layer parameter *codebookType* set to 'typeI-SinglePanel' and *pmi-FormatIndicator* set to 'widebandPMI' and, +- the UE shall report a PMI consisting of a single wideband indication ( $\hat{i}_1$ in Clause 5.2.2.2.1) for the entire CSI reporting band. The CQI is calculated conditioned on the reported assuming PDSCH transmission with $N_p \geq 1$ precoders (corresponding to the same but different in Clause 5.2.2.2.1), where the UE assumes that one precoder is randomly selected from the set of $N_p$ precoders for each PRG on PDSCH, where the PRG size for CQI calculation is configured by the higher layer parameter *pdsch-BundleSizeForCSI*. + +If the UE is configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'cri-RI-CQI', + +- if the UE is configured with higher layer parameter *non-PMI-PortIndication* contained in a *CSI-ReportConfig*, $r$ ports are indicated in the order of layer ordering for rank $r$ and each CSI-RS resource in the CSI resource setting is linked to the *CSI-ReportConfig* based on the order of the associated *NZP-CSI-RS-ResourceId* in the linked CSI resource setting for channel measurement given by higher layer parameter *resourcesForChannelMeasurement*. The configured higher layer parameter *non-PMI-PortIndication* contains a sequence of port indices, where are the CSI-RS port indices associated with rank $v$ and $R \in \{1, 2, \dots, P\}$ where is the number of ports in the CSI-RS resource. The UE shall only report RI corresponding to the configured fields of *PortIndexFor8Ranks*. If the UE + +is configured with a *CSI-ReportConfig* that contains a list of sub-configurations with *[port-subsetIndicator]* configured in each sub-configuration, and the higher layer parameter *non-PMI-PortIndication* is separately provided for a sub-configuration, then $P$ corresponds to the number of bits with value 1 in the bitmap *[port-subsetIndicator]* for the sub-configuration and the CSI-RS port indices are derived by mapping antenna ports corresponding to all bits with value of 1 in *[port-subsetIndicator]* as consecutive antenna ports starting at CSI-RS port index 0 in increasing order of the bit position in *[port-subsetIndicator]*. + +- if the UE is not configured with higher layer parameter *non-PMI-PortIndication*, the UE assumes, for each CSI-RS resource in the CSI resource setting linked to the *CSI-ReportConfig*, that the CSI-RS port indices $p_0^{(v)}, \dots, p_{v-1}^{(v)} = \{0, \dots, v-1\}$ are associated with ranks $v = 1, 2, \dots, P$ where $P$ is the number of ports in the CSI-RS resource. If the UE is configured with a *CSI-ReportConfig* that contains a list of sub-configurations with *[port-subsetIndicator]* configured in each sub-configuration and the higher layer parameter *non-PMI-PortIndication* is not provided for a sub-configuration, then $P$ corresponds to the number of bits with value 1 in the bitmap *[port-subsetIndicator]* for the sub-configuration and the CSI-RS port indices are derived by mapping antenna ports corresponding to all bits with value of 1 in *[port-subsetIndicator]* as consecutive antenna ports starting at CSI-RS port index 0 in increasing order of the bit position in *[port-subsetIndicator]*. +- When calculating the CQI for a rank, the UE shall use the ports indicated for that rank for the selected CSI-RS resource. The precoder for the indicated ports shall be assumed to be the identity matrix scaled by $\frac{1}{\sqrt{v}}$ . + +If the UE is configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'cri-RSRP', 'ssb-Index-RSRP', 'cri-RSRP- Index' or 'ssb-Index-RSRP- Index', + +- if the UE is configured with the higher layer parameter *groupBasedBeamReporting* set to 'disabled', the UE is not required to update measurements for more than 64 CSI-RS and/or SSB resources, and the UE shall report in a single report *nrofReportedRS* (higher layer configured) different CRI or SSBRI for each report setting. +- if the UE is configured with the higher layer parameter *groupBasedBeamReporting* set to 'enabled', the UE is not required to update measurements for more than 64 CSI-RS and/or SSB resources, and the UE shall report in a single reporting instance two different CRI or SSBRI for each report setting, where CSI-RS and/or SSB resources can be received simultaneously by the UE either with a single spatial domain receive filter, or with multiple simultaneous spatial domain receive filters. +- if the UE is configured with the higher layer parameter *groupBasedBeamReporting-r17*, the UE is not required to update measurements for more than 64 CSI-RS and/or SSB resources, and the UE shall report in a single reporting instance *nrofReportedGroups*, if configured, group(s) of two CRIs or SSBRI selecting one CSI-RS or SSB from each of the two CSI Resource Sets for the report setting, where CSI-RS and/or SSB resources of each group can be received simultaneously by the UE. +- if the UE is configured with the higher layer parameter *groupBasedBeamReporting-v18* set to *JointULandDL*, the UE is not required to update measurements for more than 64 CSI-RS and/or SSB resources, and the UE shall report in a single reporting instance *nrofReportedGroups-r18*, if configured, group(s) of two CRIs or SSBRI selecting one CSI-RS or SSB from each of the two CSI Resource Sets for the report setting, where CSI-RS and/or SSB resources of each group can be received simultaneously and applied for simultaneous transmission with spatial filters by the UE subject to UE capability. +- if the UE is configured with the higher layer parameter *groupBasedBeamReporting-v18* set to *ULOnly*, the UE is not required to update measurements for more than 64 CSI-RS and/or SSB resources, and the UE shall report in a single reporting instance *nrofReportedGroups-r18*, if configured, group(s) of two CRIs or SSBRI selecting one CSI-RS or SSB from each of the two CSI Resource Sets for the report setting, where CSI-RS and/or SSB resources of each group can be applied for simultaneous transmission with spatial filters by the UE subject to UE capability. + +If the UE is configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'cri-SINR', 'ssb-Index-SINR', 'cri-SINR- Index' or 'ssb-Index-SINR- Index', + +- if the UE is configured with the higher layer parameter *groupBasedBeamReporting* set to 'disabled', the UE shall report in a single report *nrofReportedRS* (higher layer configured) different CRI or SSBRI for each report setting. + +- if the UE is configured with the higher layer parameter *groupBasedBeamReporting* set to 'enabled', the UE shall report in a single reporting instance two different CRI or SSBRI for each report setting, where CSI-RS and/or SSB resources can be received simultaneously by the UE. + +If the UE is configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'tdcp' + +- the value of $\delta$ is configured by higher layer parameter $Y$ , and delay values, $\delta_0, \delta_1, \dots$ , are configured by higher layer parameter $D$ , such that the UE is expected to report the amplitude of TDCP measurement, as defined in Clause 5.1 of [7, TS 38.215], for each of the configured delays. Values of $\delta$ can be configured subject to UE capability. The configurable delay values are $\delta_0, \delta_1, \dots$ , where the value $\delta_i$ is restricted to subcarrier spacing configuration $\mu$ , the values other than $\delta_i$ are applicable to subcarrier spacing configurations $\mu$ , and where the values $\delta_i$ can be configured subject to UE capability, with $i \geq 0$ . +- For $\mu$ , if the higher layer parameter *phase* is configured, the UE is expected to report the amplitude and phase of TDCP measurement for each of the configured delays, if supported by UE capability. + +Except for a *CSI-ReportConfig* configured with *reportQuantity* set to 'cri-RI-PMI-CQI' and *codebookType* set to 'typeII-CJT-r18', 'typeII-CJT-PortSelection-r18', 'typeII-Doppler-r18', or 'typeII-Doppler-PortSelection-r18', if the UE is configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'cri-RSRP', 'cri-RI-PMI-CQI', 'cri-RI-i1', 'cri-RI-i1-CQI', 'cri-RI-CQI', 'cri-RI-LI-PMI-CQI', 'cri-SINR', or 'cri-SINR- Index ', and resources are configured in the corresponding resource set for channel measurement, then the UE shall derive the CSI parameters other than CRI conditioned on the reported CRI, where CRI $k$ ( $k \geq 0$ ) corresponds to the configured $(k+1)$ -th entry of associated *nzp-CSI-RS-Resources* in the corresponding *NZP-CSI-RS-ResourceSet* for channel measurement, and $(k+1)$ -th entry of associated *csi-IM-Resource* in the corresponding *csi-IM-ResourceSet* (if configured) or $(k+1)$ -th entry of associated *nzp-CSI-RS-Resources* in the corresponding *NZP-CSI-RS-ResourceSet* (if configured for *CSI-ReportConfig* with *reportQuantity* set to 'cri-SINR' or 'cri-SINR- Index ') for interference measurement. If CSI-RS resources are configured, each resource shall contain at most 16 CSI-RS ports. If CSI-RS resources are configured, each resource shall contain at most 8 CSI-RS ports. + +If the UE is configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'cri-RI-PMI-CQI', *codebookType* set to 'typeII-CJT-r18' or 'typeII-CJT-PortSelection-r18' and the corresponding *NZP-CSI-RS-ResourceSet* for channel measurement is configured with resources, each resource can contain, at most, 32 CSI-RS ports. + +Subject to UE capability, a UE configured with a *CSI-ReportConfig* with the higher layer parameter $N4$ and *reportQuantity* set to 'cri-RI-PMI-CQI' is assumed to support UE-side CSI prediction. The reported PMI indicates predicted precoder matrices associated with consecutive slot intervals, each with duration of $\delta$ slots, where the value of $\delta$ is configured by higher layer parameter $N4$ . If the UE is configured with an aperiodic CSI-RS resource set for channel measurement, the value, in number of slots, of the time unit is configured by higher layer parameter $d$ , where $d$ is defined in Clause 5.2.1.4.1. If the UE is configured with a periodic or semi-persistent CSI-RS resource set for channel measurement, the value of $\delta$ is equal to the periodicity of the CSI-RS resource. The earliest of the $\delta$ slot intervals starts at slot $\delta$ , where $\delta$ is the uplink slot in which the CSI is reported and the slot offset is configured by higher layer parameter *delta*, where defined in Clause 5.2.2.5 and the value can be configured subject to UE capability. + +- For $\mu$ , the UE is expected to report a predicted PMI for slot interval $\delta$ and the slot offset value can be configured only for $\mu$ . A UE can be configured with $\mu$ if the higher layer parameter *codebookType* is set to 'typeII-Doppler-r18', or 'typeII-Doppler-PortSelection-r18'. +- The reported CQI is associated with slot $\delta$ and the reported PMI. +- For $\mu$ , the UE is expected to report a PMI which indicates predicted precoder matrices associated with slot intervals $\delta$ , for $\mu$ . A UE can be configured with $\mu$ if the higher layer parameter *codebookType* is set to 'typeII-Doppler-r18'. +- The UE is configured by higher layer parameter *TDCQI* to report CQIs for each subband in the CSI reporting band, if *cqi-FormatIndicator* is set to 'subbandCQI', or CQIs for the entire CSI reporting band, if *cqi-FormatIndicator* is set to 'widebandCQI'. For $\mu$ , the second CQI includes a 4-bit wideband CQI index and, if subband CQI reporting is configured, a 2-bit subband CQI index, calculated independently from the first CQI, as described in Clause 5.2.2.1, and the two CQIs are reported in the same CSI report. +- If the higher layer parameter *TDCQI* is set to '1-1', and the CQI is associated with slot $\delta$ and the precoder matrices for slot interval $\delta$ . + +- If the higher layer parameter *TDCQI* is set to '1-2', and the CQI is associated with slot $n$ and the precoder matrices for slot interval $n$ and with slot $n+1$ and the precoder matrices for slot interval $n+1$ . +- If the higher layer parameter *TDCQI* is set to '2', . The first CQI is associated with slot $n$ and the precoder matrices for slot interval $n$ . The second CQI is associated with slot $n+1$ and the precoder matrices for slot interval $n+1$ . + +If the UE is configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'cri-RI-PMI-CQI', or 'cri-RI-LI-PMI-CQI' and the corresponding *NZP-CSI-RS-ResourceSet* for channel measurement is configured with resources, two Resource Groups with resources in Group 1, resources in Group 2, , and Resource Pairs: + +- each resource can contain, subject to UE capability, at most 32 CSI-RS ports. For two Resource Groups with resources ( $i=1,2$ ), if $N_i > 1$ , the resource in *NZP-CSI-RS-ResourceSet* shall contain at most 32 CSI-RS ports; if $N_i = 1$ , each resource in *NZP-CSI-RS-ResourceSet* shall contain at most 16 CSI-RS ports; if $N_i = 0$ , each resource in *NZP-CSI-RS-ResourceSet* shall contain at most 8 CSI-RS ports. +- each of the Resource Pairs is associated to a CRI value. +- The *CSI-ReportConfig* may be configured with higher layer parameter *sharedCMR*. $N_1$ and $N_2$ are the numbers of resources associated to a CRI value, other than the $N$ CRIs defined above, in Group 1 and Group 2, respectively, with $N_1, N_2 \geq 0$ , such that the total number of CRI values configured for the *CSI-ReportConfig* is $N + N_1 + N_2$ . +- If the higher layer parameter *csi-ReportMode* is set to 'Mode1' and the higher layer parameter *numberOfSingleTRP-CSI-Mode1* is set to $M$ , ; otherwise, +- if the higher layer parameter *csi-ReportMode* is set to 'Mode1' and the higher layer parameter *numberOfSingleTRP-CSI-Mode1* is set to $M$ , or if *csi-ReportMode* is set to 'Mode2', + - if *sharedCMR* is configured: $M_1$ and $M_2$ ; otherwise + - if *sharedCMR* is not configured, only the resources in Group 1 and Group 2 that are not referred to in any Resource Pair are associated to $M$ CRI values other than the $N$ CRIs defined above. +- If interference measurement is performed on CSI-IM, $N$ resources are configured in the corresponding *csi-IM-ResourceSet*. The $N$ resources for channel measurement defined above are resource-wise associated with the first $N$ CSI-IM resources by the ordering of the CSI-RS resources and CSI-IM resources in the corresponding Resource Set. The $N$ Resource Pairs for channel measurement are associated to the last $N$ CSI-IM resources by the ordering of the CSI-RS Resource Pairs and CSI-IM resources in the CSI-IM Resource Set. The UE may assume that the two CSI-RS resources for channel measurement in a Resource Pair and the associated CSI-IM resource for interference measurement are resource-wise QCLed with respect to 'typeD'. +- The UE is not expected to be configured with NZP CSI-RS for interference measurement other than the NZP CSI-RS resources for channel measurement configured in the Resource Pairs. +- The UE expects, for that *CSI-ReportConfig*, to be configured with higher layer parameter *codebookType* set to 'typeI-SinglePanel', and +- The UE shall derive the CSI parameters other than CRI(s) conditioned on the reported CRI(s), as follows: + - If the higher layer parameter *csi-ReportMode* is set to 'Mode1' and the higher layer parameter *numberOfSingleTRP-CSI-Mode1* is set to $M$ , CRI(s) are reported: + - one CRI $i$ corresponds to the configured $i$ -th entry of the associated Resource Pairs in the corresponding CSI-RS Resource Set for channel measurement, and $i$ -th entry of the corresponding CSI-IM Resource Set, if configured. The UE shall report two RIs, two PMIs, two LIs (if configured), associated to the resource in Group 1 and the resource in Group 2, respectively, of the $i$ -th Resource Pair, and one CQI; and + - if $N_1 > 0$ , one CRI $i$ ( $i > N$ ) corresponds to the configured $i$ -th entry of the associated resources in the corresponding CSI-RS Resource Set for channel measurement, and $i$ -th entry of the corresponding CSI-IM Resource Set, if configured. The UE shall report one RI, one PMI, one LI (if configured) and one or two CQIs conditioned on CRI $i$ ; or + - if $N_2 > 0$ , one CRI $i$ corresponds to the configured $i$ -th entry of the associated resources in Group 1 of the corresponding CSI-RS Resource Set for channel measurement, and $i$ -th entry of the associated resources in the corresponding CSI-IM Resource Set, if configured, and one CRI $i$ corresponds to the configured $i$ -th + +entry of the associated resources in Group 2 of the corresponding CSI-RS Resource Set for channel measurement, and -th entry of the corresponding CSI-IM Resource Set, if configured. The UE shall report one RI, one PMI, one LI (if configured) and one or two CQIs conditioned on CRI and one RI, one PMI, one LI (if configured) and one or two CQIs conditioned on CRI. + +- If the higher layer parameter *csi-ReportMode* is set to 'Mode2', one CRI is reported, which corresponds to the -th entry of the resources or Resource Pairs in the corresponding CSI-RS Resource Set for channel measurement, and -th entry of the associated resources in the corresponding CSI-IM Resource Set, if configured. The first codepoints of the CRI correspond to resources associated to Group 1 and Group 2. The last codepoints of the CRI correspond to the configured Resource Pairs. The UE shall report one RI, one PMI, one LI, if configured, and one or two CQIs conditioned on CRI if ; or two RIs, two PMIs, two LIs, if configured, associated to the resource in Group 1 and the resource in Group 2, respectively, of the -th Resource Pair, and one CQI, otherwise. +- For a reported CRI corresponding to an entry of the Resource Pairs configured in the corresponding CSI-RS Resource Set for channel measurement: + - the UE shall not report a total number of layers larger than four. + - the two RIs are reported with a joint RI index corresponding to one of the four rank combinations: . +- The *CodebookConfig* in *CSI-ReportConfig* can be configured with two RI restriction parameters *typeI-SinglePanel-ri-RestrictionSTRP* and *typeI-SinglePanel-ri-RestrictionSDM*. The parameter *typeI-SinglePanel-ri-RestrictionSTRP* applies to a reported RI when conditioned on a CRI corresponding to an entry of the CSI-RS resources defined above. The bitmap parameter *typeI-SinglePanel-ri-RestrictionSTRP* forms the bit sequence $r_7, \dots, r_1, r_0$ where $r_0$ is the LSB and $r_7$ is the MSB. When $r_i$ is zero, $i \in \{0, 1, \dots, 7\}$ , PMI and RI reporting are not allowed to correspond to any precoder associated with $\nu = i + 1$ layers. The parameter *typeI-SinglePanel-ri-RestrictionSDM* applies to a reported joint RI index when conditioned on a CRI corresponding to an entry of the Resource Pairs and indicates one or more of the four rank combinations that are allowed to correspond to the reported PMIs and RIs. The bitmap parameter *typeI-SinglePanel-ri-RestrictionSDM* forms the bit sequence $r_3, \dots, r_1, r_0$ where $r_0$ is the LSB and $r_3$ is the MSB. When $r_i$ is zero, $i \in \{0, 1, \dots, 3\}$ , PMI and RI reporting are not allowed to correspond to any precoder associated with the -th rank combination in the following order: $\{1, 1\}$ , $\{1, 2\}$ , $\{2, 1\}$ , $\{2, 2\}$ . +- The *CodebookConfig* in *CSI-ReportConfig* can be configured with two Codebook Subset Restrictions. The first restriction applies to a reported PMI associated to a CSI-RS resource in Group 1. The second restriction applies to a reported PMI associated to a CSI-RS resource in Group 2. + +If the UE is configured with a *CSI-ReportConfig* that contains a list of sub-configurations, provided by *[csi-ReportSubConfigList]*: + +- The UE expects to be configured with the higher layer parameter *codebookType* set to 'typeI-SinglePanel' or 'typeI-MultiPanel'. If the UE indicates a capability for supporting mixed codebook combination in a slot with [ABC], each sub-configuration can be configured with the higher layer parameter *codebookType* set to 'typeI-SinglePanel' or 'typeI-MultiPanel'. +- Each sub-configuration can be configured with an antenna port subset using the higher layer bitmap parameter *[port-subsetIndicator]* which contains the bit sequence , where is the MSB and is the LSB, bit corresponds to antenna port , and is the number of ports *nrofPorts* configured for the CSI-RS resources(s) within a *NZP-CSI-RS-ResourceSet* contained in the *CSI-ResourceConfig* for channel measurement that corresponds to the *CSI-ReportConfig*. A bit value 0 in *[port-subsetIndicator]* indicates that the corresponding antenna port is disabled for the sub-configuration, whereas bit value 1 indicates that the antenna port is enabled and belongs to the antenna port subset for the sub-configuration. For the derivation of PMI, antenna ports corresponding to all bits with value of 1 in *[port-subsetIndicator]* are mapped to consecutive antenna ports starting at CSI-RS antenna port 3000 in increasing order of the bit position in *[port-subsetIndicator]*. +- If a sub-configuration is configured with an antenna port subset, then the sub-configuration can be configured with a [RI restriction parameter] and, if the number of antenna ports of the subset greater than 2, with *[n1-n2 parameter]* if the higher layer parameter *codebookType* is set to 'typeI-SinglePanel' or with *[ng-n1-n2 parameter]* if the higher layer parameter *codebookType* is set to 'typeI-MultiPanel', and, if the corresponding number of antenna ports of the subset is 2, with *twoTX-CodebookSubsetRestriction*, where the parameters [RI restriction], *[n1-n2]*, *[ng-n1-n2]*, *twoTX-CodebookSubsetRestriction* are as described in Clauses 5.2.2.2.1 and 5.2.2.2.2. If a + +sub-configuration is configured with an antenna port subset, and if higher layer parameter *reportQuantity* is set to 'cri-RI-i1-CQI', and if the higher layer parameter *codebookType* is set to 'typeI-SinglePanel', then the sub-configuration can be configured with higher layer parameter *typeI-SinglePanel-codebookSubsetRestriction-i2*, where *typeI-SinglePanel-codebookSubsetRestriction-i2* is as described in Clause 5.2.2.2.1. + +- If a sub-configuration is configured with an antenna port subset, and if the *CSI-ReportConfig* that contains a mix of sub-configuration(s) each corresponding to 'typeI-SinglePanel' some other sub-configuration(s) each corresponding to 'typeI-MultiPanel', then the sub-configuration(s) can be configured with the higher layer parameter *codebookMode*. +- A sub-configuration can be configured with a power offset provided by *[powerOffset]*. +- A sub-configuration can be configured with a list of NZP CSI-RS resources, provided by *[nzp-CSI-RS-resourceList]*, which indicates one or more NZP CSI-RS resources, within a *NZP-CSI-RS-ResourceSet* contained in the *CSI-ResourceConfig* for channel measurement which corresponds to the *CSI-ReportConfig*. If there is no sub-configuration configured with a power offset provided by *[powerOffset]*, the list of NZP CSI-RS resources has no intersection with a list of NZP CSI-RS resources configured for any other sub-configuration(s) within the *CSI-ReportConfig*. +- If a sub-configuration is configured with a list of NZP CSI-RS resources with more than one resource, the UE shall derive the CSI parameters other than CRI conditioned on the reported CRI, where the CRI $k$ ( $k \geq 0$ ) for the sub-configuration corresponds to the configured $(k+1)$ -th entry of associated *NZP-CSI-RS-Resource* in the list of NZP CSI-RS resources. +- If a sub-configuration is not configured with *[nzp-CSI-RS-resourceList]* then the sub-configuration shall be associated with all the NZP CSI-RS resources within a *NZP-CSI-RS-ResourceSet* contained in the *CSI-ResourceConfig* for channel measurement which corresponds to the *CSI-ReportConfig*. +- the UE reports CSI(s) for one or more sub-configurations according to Clauses 5.2.1.5.1, 5.2.1.5.2, 5.2.3 and 5.2.4, and according to the higher layer parameter *reportQuantity* configured for that *CSI-ReportConfig*. +- The UE does not expect the higher layer parameter *reportQuantity* to be set to 'cri-RSRP', 'cri-SINR', 'cri-SINR-Index', 'cri-RSRP-Index', 'none', 'ssb-Index-RSRP', 'ssb-Index-SINR', 'ssb-Index-RSRP-Index', 'ssb-Index-SINR-Index', or 'tdcp'. + +If the UE is configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'ssb-Index-RSRP' or 'ssb-Index-RSRP-Index', the UE shall report SSBRI, where SSBRI $k$ ( $k \geq 0$ ) corresponds to the configured $(k+1)$ -th entry of the associated *csi-SSB-ResourceList* in the corresponding *CSI-SSB-ResourceSet*. + +If the UE is configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'ssb-Index-SINR' or 'ssb-Index-SINR-Index', the UE shall derive L1-SINR conditioned on the reported SSBRI, where SSBRI $k$ ( $k \geq 0$ ) corresponds to the configured $(k+1)$ -th entry of the associated *csi-SSB-ResourceList* in the corresponding *CSI-SSB-ResourceSet* for channel measurement, and $(k+1)$ -th entry of associated *csi-IM-Resource* in the corresponding *csi-IM-ResourceSet* (if configured) or $(k+1)$ -th entry of associated *nzp-CSI-RS-Resources* in the corresponding *NZP-CSI-RS-ResourceSet* (if configured) for interference measurement. + +If the UE is configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'cri-RI-PMI-CQI', 'cri-RI-i1', 'cri-RI-i1-CQI', 'cri-RI-CQI' or 'cri-RI-LI-PMI-CQI', then the UE is not expected to be configured with more than 8 CSI-RS resources in a CSI-RS resource set contained within a resource setting that is linked to the *CSI-ReportConfig*, except when the UE is configured with a *CSI-ReportConfig* with the higher layer parameter *N4*, *reportQuantity* set to 'cri-RI-PMI-CQI' and the corresponding CSI-RS resource set for channel measurement is aperiodic with resources. + +If the UE is configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'cri-RI-LI-PMI-CQI', UE does not expect the *CSI-ReportConfig* to be configured with higher layer parameter *codebookType* set to 'typeII-r16' or 'typeII-PortSelection-r16', 'typeII-PortSelection-r17', 'typeII-CJT-r18', 'typeII-CJT-PortSelection-r18', 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18'. + +If the UE is configured with a *CSI-ReportConfig* with higher layer parameter *reportQuantity* set to 'cri-RSRP', 'cri-SINR', 'none', 'cri-RSRP-Index' or 'cri-SINR-Index' and the *CSI-ReportConfig* is linked to a resource setting configured with the higher layer parameter *resourceType* set to 'aperiodic', then the UE is not expected to be configured with more than 16 CSI-RS resources in a CSI-RS resource set contained within the resource setting. + +The LI indicates which column of the precoder matrix of the reported PMI corresponds to the strongest layer of the codeword corresponding to the largest reported wideband CQI. If two wideband CQIs are reported and have equal value, the LI corresponds to strongest layer of the first codeword. If the UE is configured with a *CSI-ReportConfig* with *reportQuantity* set to 'cri-RI-LI-PMI-CQI' and the corresponding *NZP-CSI-RS-ResourceSet* for channel measurement is configured with two Resource Groups and Resource Pairs, and the UE reports a CRI associated to a Resource Pair, and a rank combination, the first LI indicates which column of the precoder matrix of the first reported PMI corresponds to the strongest of the first layers of the codeword and the second LI indicates which column of the precoder matrix of the second reported PMI corresponds to the strongest of the last layers of the codeword. + +For operation with shared spectrum channel access in FR1, or in FR2-2 when the UE is provided *ChannelAccessMode2-r17* = 'enabled', if the UE is configured with a *CSI-ReportConfig* with higher layer parameter *reportQuantity* set to 'cri-RI-PMI-CQI', 'cri-RI-i1', 'cri-RI-i1-CQI', 'cri-RI-CQI' or 'cri-RI-LI-PMI-CQI', the UE shall derive: + +- the CSI parameters without averaging two or more instances of any periodic or semi-persistent *nzp-CSI-RS-Resources* in the corresponding *NZP-CSI-RS-ResourceSet* for channel measurement or for interference measurement located in different DL transmissions, +- the instances of the *nzp-CSI-RS-Resources* are not in the same channel occupancy duration indicated by DCI format 2\_0, if the UE is provided at least one of *SlotFormatIndicator* or *co-DurationList*; or +- the instances of the *nzp-CSI-RS-Resources* occur within a set of consecutive symbols which are not all occupied by PDSCH(s) and/or aperiodic CSI-RS(s) indicated by DCI formats, if any, and the corresponding PDCCH(s), if the UE is neither provided with *CO-DurationsPerCell* nor *SlotFormatIndicator*, but is provided with *csi-RS-ValidationWithDCI* +- the interference measurements for computing CSI value based on periodic/semi-persistent CSI-IM measured only in OFDM symbol(s) that fulfill the same conditions under which the UE is expected to receive periodic/semi-persistent CSI-RS as described in Clause 11.1 and Clause 11.1.1 of [6, TS 38.213]. + +If the UE is configured with the higher layer parameter *SSB-MTC-AdditionalPCI*, the UE is allowed to report in a single reporting instance up to four SSBRI for each report setting, where SSB resources are associated with PCI indices referring to the PCI of the serving cell and PCI(s) different from the PCI of the serving cell within the set of PCIs configured. + +If a UE is configured with a *LTM-CSI-ReportConfig*, + +- if the UE is configured with *[spCellInclusion]*, the UE shall report in a single reporting instance *[noOfReportedRS-PerCell different SSBRI]* for the current SpCell and each of the *[nOfReportedCells] - 1* candidate cells. Otherwise, the UE shall report in a single reporting instance *[noOfReportedRS-PerCell]* different SSBRI for each of the *[noOfReportedCell]* candidate cells, +- where SSBRI $k$ ( $k \geq 0$ ) corresponds to the configured $(k+1)$ -th entry of the associated *[ltm-CSI-SSB-ResourceList]* in the corresponding *[LTM-CSI-SSB-ResourceSet]*, + - if *spCellInclusion* is configured, SSB resources in *[ltm-CSI-SSB-ResourceList]* associated with the current SpCell are the entries where PCI [given by *ltm-CandidatePCI*] and frequency information [given by *SSB frequency/ ARFCN-ValueNR*] of the associated candidate cell (given in *[ltm-CandidateIdList]*) is equal to the PCI and frequency information [given by *SSB frequency/ ARFCN-ValueNR*] of the current SpCell. + +If the UE is configured with a *CSI-ReportConfig* that contains a list of sub-configurations provided by *csi-ReportSubConfigList*, the UE can only be configured with NZP CSI-RS for interference measurement if each sub-configuration is configured with *[powerOffset]* and not configured with *[port-subsetIndicator]*. + +##### 5.2.1.4.3 L1-RSRP Reporting + +For L1-RSRP computation + +- the UE may be configured with CSI-RS resources, SS/PBCH Block resources or both CSI-RS and SS/PBCH block resources, when resource-wise quasi co-located with 'type C' and 'type D' when applicable. +- the UE may be configured with CSI-RS resource setting up to 16 CSI-RS resource sets having up to 64 resources within each set. The total number of different CSI-RS resources over all resource sets is no more than 128. + +For L1-RSRP reporting, if the higher layer parameter *nrofReportedRS* in *CSI-ReportConfig* is configured to be one, or if the higher layer parameters *noOfReportedCells* and *noOfReportedRS-PerCell* are both configured to be one, the reported L1-RSRP value is defined by a 7-bit value in the range [-140, -44] dBm with 1dB step size, if the higher layer parameter *nrofReportedRS* is configured to be larger than one, or if the higher layer parameter *groupBasedBeamReporting* is configured as 'enabled', or if the higher layer parameter *groupBasedBeamReporting-r17* is configured, or if any of the higher layer parameters *noOfReportedCells* and *noOfReportedRS-PerCell* is configured to be larger than one, the UE shall use differential L1-RSRP based reporting, where the largest measured value of L1-RSRP is quantized to a 7-bit value in the range [-140, -44] dBm with 1dB step size, and the differential L1-RSRP is quantized to a 4-bit value. The differential L1-RSRP value is computed with 2 dB step size with a reference to the largest measured L1-RSRP value which is part of the same L1-RSRP reporting instance. The mapping between the reported L1-RSRP value and the measured quantity is described in [11, TS 38.133]. + +When the higher layer parameter *groupBasedBeamReporting-r17* in *CSI-ReportConfig* is configured, the UE shall indicate the CSI Resource Set associated with the largest measured value of L1-RSRP, and for each group, CRI or SSBRI of the indicated CSI Resource Set is present first. + +If the higher layer parameter *timeRestrictionForChannelMeasurements* in *CSI-ReportConfig* is set to "notConfigured", the UE shall derive the channel measurements for computing L1-RSRP value reported in uplink slot *n* based on only the SS/PBCH or NZP CSI-RS, no later than the CSI reference resource, (defined in TS 38.211[4]) associated with the CSI resource setting. + +If the higher layer parameter *timeRestrictionForChannelMeasurements* in *CSI-ReportConfig* is set to "Configured", the UE shall derive the channel measurements for computing L1-RSRP reported in uplink slot *n* based on only the most recent, no later than the CSI reference resource, occasion of SS/PBCH or NZP CSI-RS (defined in [4, TS 38.211]) associated with the CSI resource setting. + +When the UE is configured with *SSB-MTC-AdditionalPCI*, a CSI-SSB-ResourceSet configured for L1-RSRP reporting includes one set of SSB indices and one set of PCI indices, where each SSB index is associated with a PCI index. + +When the UE is configured with a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'cri-RSRP-Index' or 'ssb-Index-RSRP- Index' an index of UE capability value set, indicating the maximum supported number of SRS antenna ports, is reported along with the pair of SSBRI/CRI and L1-RSRP. + +##### 5.2.1.4.4 L1-SINR Reporting + +For L1-SINR computation, for channel measurement the UE may be configured with NZP CSI-RS resources and/or SS/PBCH Block resources, for interference measurement the UE may be configured with NZP CSI-RS or CSI-IM resources. + +- for channel measurement, the UE may be configured with CSI-RS resource setting with up to 16 resource sets, with a total of up to 64 CSI-RS resources or up to 64 SS/PBCH Block resources. + +For L1-SINR reporting, if the higher layer parameter *nrofReportedRS* in *CSI-ReportConfig* is configured to be one, the reported L1-SINR value is defined by a 7-bit value in the range [-23, 40] dB with 0.5 dB step size, and if the higher layer parameter *nrofReportedRS* is configured to be larger than one, or if the higher layer parameter *groupBasedBeamReporting* is configured as 'enabled', the UE shall use differential L1-SINR based reporting, where the largest measured value of L1-SINR is quantized to a 7-bit value in the range [-23, 40] dB with 0.5 dB step size, and the differential L1-SINR is quantized to a 4-bit value. The differential L1-SINR is computed with 1 dB step size with a reference to the largest measured L1-SINR value which is part of the same L1-SINR reporting instance. When NZP CSI-RS is configured for channel measurement and/or interference measurement, the reported L1-SINR values should not be compensated by the power offset(s) given by higher layer parameter *powerControlOffsetSS* or *powerControlOffset*. + +When one or two resource settings are configured for L1-SINR measurement + +- If the higher layer parameter *timeRestrictionForChannelMeasurements* in *CSI-ReportConfig* is set to 'notConfigured', the UE shall derive the channel measurements for computing L1-SINR reported in uplink slot *n* based on only the SSB or NZP CSI-RS, no later than the CSI reference resource, (defined in TS 38.211[4]) associated with the CSI resource setting. +- If the higher layer parameter *timeRestrictionForChannelMeasurements* in *CSI-ReportConfig* is set to 'configured', the UE shall derive the channel measurements for computing L1-SINR reported in uplink slot *n* based on only the most recent, no later than the CSI reference resource, occasion of SSB or NZP CSI-RS (defined in [4, TS 38.211]) associated with the CSI resource setting. + +- If the higher layer parameter *timeRestrictionForInterferenceMeasurements* in *CSI-ReportConfig* is set to 'notConfigured', the UE shall derive the interference measurements for computing L1-SINR reported in uplink slot n based on only the CSI-IM or NZP CSI-RS for interference measurement (defined in [4, TS 38.211]) or NZP CSI-RS for channel and interference measurement no later than the CSI reference resource associated with the CSI resource setting. +- If the higher layer parameter *timeRestrictionForInterferenceMeasurements* in *CSI-ReportConfig* is set to 'configured', the UE shall derive the interference measurements for computing the L1-SINR reported in uplink slot n based on the most recent, no later than the CSI reference resource, occasion of CSI-IM or NZP CSI-RS for interference measurement (defined in [4, TS 38.211]) or NZP CSI-RS for channel and interference measurement associated with the CSI resource setting. + +When the UE is configured a *CSI-ReportConfig* with the higher layer parameter *reportQuantity* set to 'cri-SINR- Index' or 'ssb-Index-SINR- Index' an index of UE capability value, indicating the maximum supported number of SRS antenna ports, is reported along with the pair of SSBRI/CRI and L1-SINR. + +##### 5.2.1.4.5 TDCP Reporting + +For a *CSI-ReportConfig* with higher layer parameter *reportQuantity* set to 'tdcp' and higher layer parameters and , the reported TDCP amplitude(s) corresponding to the configured delays are indicated by + +and the corresponding amplitude values are obtained from: , for , where the mapping from to is given in Table 5.2.1.4.5-1. + +**Table 5.2.1.4.5-1: Mapping of elements of : to** + +| | | | | | | | | +|---|--|---|--|----|--|----|--| +| | | | | | | | | +| 0 | | 4 | | 8 | | 12 | | +| 1 | | 5 | | 9 | | 13 | | +| 2 | | 6 | | 10 | | 14 | | +| 3 | | 7 | | 11 | | 15 | | + +For , if the higher layer parameter *phase* is configured, the reported TDCP phases are indicated by + +and the corresponding phase values are given by: . + +#### 5.2.1.5 Triggering/activation of CSI Reports and CSI-RS + +##### 5.2.1.5.1 Aperiodic CSI Reporting/Aperiodic CSI-RS when the triggering PDCCH and the CSI-RS have the same numerology + +For CSI-RS resource sets associated with Resource Settings configured with the higher layer parameter *resourceType* set to 'aperiodic', 'periodic', or 'semi-persistent', trigger states for Reporting Setting(s) (configured with the higher layer parameter *reportConfigType* set to 'aperiodic') and/or Resource Setting for channel and/or interference measurement on + +one or more component carriers are configured using the higher layer parameter *CSI-AperiodicTriggerStateList*. For a reporting setting for which the *CSI-ReportConfig* contains a list of sub-configurations provided by the higher layer parameter [*csi-ReportSubConfigList*], one or more trigger states can be configured with each indicating one or more of the sub-configurations. For aperiodic CSI report triggering, a single set of CSI triggering states are higher layer configured, wherein the CSI triggering states can be associated with any candidate DL BWP. A UE is not expected to receive more than one DCI with non-zero *CSI request* field per slot per cell. A UE is not expected to receive DCI with non-zero *CSI request* field within a cell group in a slot overlapping with any slot receiving DCI with non-zero *CSI request* field in the same cell group. A UE is not expected to be configured with different *TCI-StateId*'s for the same aperiodic CSI-RS resource ID configured in multiple aperiodic CSI-RS resource sets with the same triggering offset in the same aperiodic trigger state. A UE is not expected to receive more than one aperiodic CSI report request for transmission in a given slot per cell. A UE is not expected to receive an aperiodic CSI report request for transmission in a slot overlapping with any slot having an aperiodic CSI report transmission in the same cell group. If a UE does not indicate its capability of *csi-TriggerStateNon-ActiveBWP* the UE is not expected to be triggered with a CSI report for a non-active DL BWP. Otherwise, when a UE is triggered with a CSI report for a DL BWP that is non-active when expecting to receive the most recent occasion, no later than the CSI reference resource, of the associated NZP CSI-RS, the UE is not expected to report the CSI for the non-active DL BWP and the CSI report associated with that BWP is omitted. When a UE is triggered with aperiodic NZP CSI-RS in a DL BWP that is non-active when expecting to receive the NZP CSI-RS, the UE is not expected to measure the aperiodic CSI-RS. In the carrier of the serving cell expecting to receive that associated NZP CSI-RS, if the active DL BWP when receiving the NZP CSI-RS is different from the active DL BWP when receiving the triggering DCI, + +- the last symbol of the PDCCH span of the DCI carrying the BWP switching shall be no later than the last symbol of the PDCCH span of the DCI carrying the CSI trigger, irrespective of whether they are in the same carrier of a serving cell or not and irrespective of whether they are in the same SCS or not; +- the UE is not expected to have any other BWP switching in that carrier after the last symbol of the PDCCH span covering the DCI carrying the CSI trigger and before the first symbol of the triggered NZP CSI-RS or CSI-IM. +- when the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], the span that involves the PDCCH candidate that ends later in time is used. + +A trigger state is initiated using the *CSI request* field in DCI. + +- When all the bits of *CSI request* field in DCI are set to zero, no CSI is requested. +- When the number of configured CSI triggering states in *CSI-AperiodicTriggerStateList* is greater than $2^{N_{TS}} - 1$ , where $N_{TS}$ is the number of bits in the DCI *CSI request* field, the UE receives a subselection indication, as described in clause 6.1.3.13 of [10, TS 38.321], used to map up to $2^{N_{TS}} - 1$ trigger states to the codepoints of the *CSI request* field in DCI. $N_{TS}$ is configured by the higher layer parameter *reportTriggerSize* where . When the UE would transmit a PUCCH with HARQ-ACK information in slot $n$ corresponding to the PDSCH carrying the subselection indication, the corresponding action in [10, TS 38.321] and UE assumption on the mapping of the selected CSI trigger state(s) to the codepoint(s) of DCI *CSI request* field shall be applied starting from the first slot that is after slot $n - \mu$ where $\mu$ is the SCS configuration for the PUCCH and is the subcarrier spacing configuration for with a value of 0 for frequency range 1, and is provided by *K-Mac* or if *K-Mac* is not provided.. +- When the number of CSI triggering states in *CSI-AperiodicTriggerStateList* is less than or equal to $2^{N_{TS}} - 1$ , the *CSI request* field in DCI directly indicates the triggering state. +- For each aperiodic CSI-RS resource in a CSI-RS resource set associated with each CSI triggering state, the UE is indicated the quasi co-location configuration of quasi co-location RS source(s) and quasi co-location type(s), as described in clause 5.1.5, through higher layer signaling of *qcl-info* which contains a list of references to *TCI-State's* for the aperiodic CSI-RS resources associated with the CSI triggering state. If a *State* referred to in the list is configured with a reference to an RS configured with *qcl-Type* set to 'typeD', that RS may be an SS/PBCH block located in the same or different CC/DL BWP or a CSI-RS resource configured as periodic or semi-persistent located in the same or different CC/DL BWP. +- If the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resources in a *NZP-CSI-RS-ResourceSet* configured without higher layer parameter *trs-Info* is smaller than the UE reported threshold *beamSwitchTiming*, as defined in [13, TS 38.306], when the reported value is one of the values of {14, 28, 48} and *enableBeamSwitchTiming* is not + +provided, or is smaller than 48 when the UE provides *beamSwitchTiming-r16*, *enableBeamSwitchTiming* is provided and the *NZP-CSI-RS-ResourceSet* is configured with the higher layer parameter *repetition* set to 'off' or configured without the higher layer parameter *repetition*, or is smaller than the UE reported threshold *beamSwitchTiming-r16*, when *enableBeamSwitchTiming* is provided and the *NZP-CSI-RS-ResourceSet* is configured with the higher layer parameter *repetition* set to 'on'. + +- If a UE is configured with *enableDefaultTCI-StatePerCoresetPoolIndex* and the UE is configured by higher layer parameter *PDCCH-Config* that contains two different values of *coresetPoolIndex* in *ControlResourceSet* + - if there is any other DL signal with an indicated TCI state in the same symbols as the CSI-RS, the UE applies the QCL assumption of the other DL signal also when receiving the aperiodic CSI-RS. The other DL signal refers to PDSCH scheduled by a PDCCH associated with the same *coresetPoolIndex* as the PDCCH triggering the aperiodic CSI-RS and scheduled with offset larger than or equal to the threshold *timeDurationForQCL*, as defined in [13, TS 38.306], aperiodic CSI-RS triggered by a PDCCH associated with the same *coresetPoolIndex* as the PDCCH triggering the aperiodic CSI-RS and scheduled with offset larger than or equal to the UE reported threshold *beamSwitchTiming* when the reported value is one of the values {14,28,48} and *enableBeamSwitchTiming* is not provided, aperiodic CSI-RS triggered by a PDCCH associated with the same *coresetPoolIndex* as the PDCCH triggering the aperiodic CSI-RS and scheduled with offset larger than or equal to 48 when the reported value of *beamSwitchTiming-r16* is one of the values {224, 336} and *enableBeamSwitchTiming* is provided, periodic CSI-RS, semi-persistent CSI-RS; + - else, the UE applies the QCL parameter(s) of the CORESET associated with a monitored search space with the lowest *controlResourceSetId* among CORESETs, which are configured with the same value of *coresetPoolIndex* as the PDCCH triggering that aperiodic CSI-RS, in the latest slot in which one or more CORESETs are associated with the same value of *coresetPoolIndex* as the PDCCH triggering that aperiodic CSI-RS +- else if a UE is configured with *enableTwoDefaultTCI-States* and at least one TCI codepoint is mapped to two TCI states + - if there is any other DL signal with an indicated TCI state in the same symbols as the CSI-RS, the UE applies the QCL assumption of the other DL signal also when receiving the aperiodic CSI-RS. The other DL signal refers to PDSCH scheduled with offset larger than or equal to the threshold *timeDurationForQCL*, as defined in [13, TS 38.306], aperiodic CSI-RS scheduled with offset larger than or equal to the UE reported threshold *beamSwitchTiming* when the reported value is one of the values {14,28,48} and *enableBeamSwitchTiming* is not provided, aperiodic CSI-RS scheduled with offset larger than or equal to 48 when the reported value of *beamSwitchTiming-r16* is one of the values {224, 336} and *enableBeamSwitchTiming* is provided, periodic CSI-RS, semi-persistent CSI-RS. If there is a PDSCH indicated with two TCI states in the same symbols as the CSI-RS, the UE applies the first TCI state of the two TCI states when receiving the aperiodic CSI-RS. + - else, the UE applies the first one of two TCI states corresponding to the lowest TCI codepoint among those mapped to two TCI states and applicable to the PDSCH within the active BWP of the cell in which the CSI-RS is to be received when receiving the aperiodic CSI-RS. +- else if a UE is configured with *sfnSchemePdcch* set to 'sfnSchemeA' or 'sfnSchemeB', it is not configured with *enableTwoDefaultTCI-States*, and the two TCI states are activated for the CORESET by the activation command as described in clause 6.1.3.44 of [10, TS 38.321] + - if there is any other DL signal with an indicated TCI state in the same symbols as the CSI-RS, the UE applies the QCL assumption of the other DL signal also when receiving the aperiodic CSI-RS. The other DL signal refers to PDSCH scheduled with an offset larger than or equal to the threshold *timeDurationForQCL*, as defined in [13, TS 38.306], periodic CSI-RS, semi-persistent CSI-RS, aperiodic CSI-RS in a *NZP-CSI-RS-ResourceSet* scheduled with offset larger than or equal to the UE reported threshold *beamSwitchTiming* when the reported value is one of the values {14,28,48} and when *enableBeamSwitchTiming* is not provided or the *NZP-CSI-RS-ResourceSet* is configured with the higher layer parameter *trs-Info*, aperiodic CSI-RS in a *NZP-CSI-RS-ResourceSet* configured with the higher layer parameter *repetition* set to 'off' or configured without the higher layer parameters *repetition* and *trs-Info* scheduled with offset larger than or equal to 48 when the UE provides *beamSwitchTiming-r16* and *enableBeamSwitchTiming* is provided, aperiodic CSI-RS in a *NZP-CSI-RS-ResourceSet* configured with the higher layer parameter *repetition* set to 'on' scheduled with offset + +larger than or equal to the UE reported threshold *beamSwitchTiming-r16* and *enableBeamSwitchTiming* is provided; + +- else, the UE applies the first one of TCI states indicated for the CORESET with the lowest CORESET ID in the latest slot within the active BWP of the cell in which the CSI-RS is to be received when receiving the aperiodic CSI-RS, if two TCI states are activated for the CORESET. Otherwise, the UE applies the single activated TCI state of the CORESET with the lowest CORESET ID in the latest slot within the active BWP of the cell in which the CSI-RS is to be received, when receiving the aperiodic CSI-RS +- else if there is any other DL signal with an indicated TCI state in the same symbols as the CSI-RS, the UE applies the QCL assumption of the other DL signal also when receiving the aperiodic CSI-RS. The other DL signal refers to PDSCH scheduled with offset larger than or equal to the threshold *timeDurationForQCL*, as defined in [13, TS 38.306], periodic CSI-RS, semi-persistent CSI-RS, aperiodic CSI-RS in a *NZP-CSI-RS-ResourceSet* scheduled with offset larger than or equal to the UE reported threshold *beamSwitchTiming* when the reported value is one of the values {14,28,48} and when *enableBeamSwitchTiming* is not provided or the *NZP-CSI-RS-ResourceSet* is configured with the higher layer parameter *trs-Info*, aperiodic CSI-RS in a *NZP-CSI-RS-ResourceSet* configured with the higher layer parameter *repetition* set to 'off' or configured without the higher layer parameters *repetition* and *trs-Info* scheduled with offset larger than or equal to 48 when the UE provides *beamSwitchTiming-r16* and *enableBeamSwitchTiming* is provided, aperiodic CSI-RS in a *NZP-CSI-RS-ResourceSet* configured with the higher layer parameter *repetition* set to 'on' scheduled with offset larger than or equal to the UE reported threshold *beamSwitchTiming-r16* and *enableBeamSwitchTiming* is provided; +- else if the UE is not provided *dl-OrJointTCI-StateList*, and if at least one CORESET is configured for the BWP in which the aperiodic CSI-RS is received, when receiving the aperiodic CSI-RS, the UE applies the QCL assumption used for the CORESET associated with a monitored search space with the lowest *controlResourceSetId* in the latest slot in which one or more CORESETs within the active BWP of the serving cell are monitored; +- else if the UE is provided *dl-OrJointTCI-StateList* and if the indicated TCI state is associated with a PCI different from the serving cell, regardless of configuration of *followUnifiedTCI-State*, and if at least one CORESET is configured for the BWP in which the aperiodic CSI-RS is received, when receiving the aperiodic CSI-RS, the UE applies the QCL assumption used for the CORESET associated with a monitored search space with the lowest *controlResourceSetId* in the latest slot in which one or more CORESETs within the active BWP of the serving cell are monitored. In the CA case, if the 'QCL-TypeD' of the aperiodic CSI-RSs from respective CCs in a band are different in a slot, the QCL-TypeD assumption of the CSI-RS in the CC with lowest CC ID in the band is applied to all the aperiodic CSI-RSs in the CCs in the band; +- else if the UE is provided *dl-OrJointTCI-StateList* and the indicated TCI state is associated with the PCI of the serving cell, regardless of configuration of *followUnifiedTCI-State*, the indicated TCI state is applied to the aperiodic CSI-RS; +- else if the UE is configured with *enableDefaultBeamForCCS* and when receiving the aperiodic CSI-RS, the UE applies the QCL assumption of the lowest-ID activated TCI state applicable to the PDSCH within the active BWP of the cell in which the CSI-RS is to be received. +- If the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resources in a *NZP-CSI-RS-ResourceSet* is equal to or greater than the UE reported threshold *beamSwitchTiming* when the reported value is one of the values {14,28,48} and *enableBeamSwitchTiming* is not provided and the *NZP-CSI-RS-ResourceSet* is not configured with higher layer parameter *trs-Info*, or is equal to or greater than the UE reported threshold *beamSwitchTiming* when the reported value is one of the values {14,28,48} and the *NZP-CSI-RS-ResourceSet* is configured with higher layer parameter *trs-Info*, or is equal to or greater than 48 when the UE provides *beamSwitchTiming-r16* and *enableBeamSwitchTiming* is provided and the *NZP-CSI-RS-ResourceSet* is configured with the higher layer parameter *repetition* set to 'off' or configured without the higher layer parameters *repetition* and *trs-Info*, or is equal to or greater than the UE reported threshold *beamSwitchTiming-r16*, when *enableBeamSwitchTiming* is provided and the *NZP-CSI-RS-ResourceSet* is configured with the higher layer parameter *repetition* set to 'on', the UE is expected to apply the QCL assumptions in the indicated TCI states for the aperiodic CSI-RS resources in the CSI triggering state indicated by the CSI trigger field in DCI. + +- The UE is not expected to receive aperiodic CSI-RS and PDSCH/aperiodic CSI-RS associated with different values of *coresetPoolIndex* in overlapped symbol(s). The UE is not expected to receive aperiodic CSI-RS and semi-persistent/periodic CSI-RS with different 'QCL-type D' in overlapped symbol(s). +- If configured, the UE may assume that a CSI-RS resource in an aperiodic CSI-RS resource set configured without *trs-Info* is quasi co-located with the RS(s) in the indicated TCI state. +- A non-zero codepoint of the CSI request field in the DCI is mapped to a CSI triggering state according to the order of the associated positions of the up to trigger states in *CSI-AperiodicTriggerStateList* with codepoint '1' mapped to the triggering state in the first position. + +For a UE configured with the higher layer parameter *CSI-AperiodicTriggerStateList*, if a Resource Setting linked to a *CSI-ReportConfig* has multiple aperiodic resource sets, only one of the aperiodic CSI-RS resource sets from the Resource Setting is associated with the trigger state, and the UE is higher layer configured per trigger state per Resource Setting to select the one CSI-IM/NZP CSI-RS resource set from the Resource Setting. + +When aperiodic CSI-RS is used with aperiodic reporting, the CSI-RS offset is configured per resource set by the higher layer parameter *aperiodicTriggeringOffset* or *aperiodicTriggeringOffset-r16* or *aperiodicTriggeringOffset-r17*. The CSI-RS triggering offset has the values of {0, 1, 2, 3, 4, 5, 6, ..., 15, 16, 24} slots for or {0, 4, 8, 12, ..., 60, 64, 96} slots for , where is the subcarrier spacing configurations for CSI-RS. If the UE is not configured with *minimumSchedulingOffsetK0* for any DL BWP and *minimumSchedulingOffsetK2* for any UL BWP and if all the associated trigger states do not have the higher layer parameter *qcl-Type* set to 'typeD' in the corresponding TCI states, the CSI-RS triggering offset is fixed to zero. The aperiodic triggering offset of the CSI-IM follows offset of the associated NZP CSI-RS for channel measurement. The aperiodic CSI-RS is transmitted in a slot $K_s$ , , if UE is configured with *ca-SlotOffset* for at least one of the triggered and triggering cell, and in slot $K_s = n + X$ , otherwise, and where + +- $n$ is the slot containing the triggering DCI, $X$ is the CSI-RS triggering offset according to the higher layer parameter *aperiodicTriggeringOffset* or *aperiodicTriggeringOffset-r16* or *aperiodicTriggeringOffset-r17*, +- and are the and the $\mu_{\text{offset}}$ which are determined by higher-layer configured *ca-SlotOffset* for the cell receiving the PDCCH, and are the and the $\mu_{\text{offset}}$ which are determined by higher-layer configured *ca-SlotOffset* for the cell transmitting the CSI-RS respectively, as defined in [4, TS 38.211] clause 4.5. + +The UE does not expect that aperiodic CSI-RS is transmitted before the OFDM symbol(s) carrying its triggering DCI. When the minimum scheduling offset restriction is applied, UE is not expected to be triggered by CSI triggering state indicated by the CSI request field in DCI in which CSI-RS triggering offset is smaller than the currently applicable minimum scheduling offset restriction $K_{\text{omin}}$ . + +If interference measurement is performed on aperiodic NZP CSI-RS, a UE is not expected to be configured with a different aperiodic triggering offset of the NZP CSI-RS for interference measurement from the associated NZP CSI-RS for channel measurement. + +If the UE is configured with a single carrier for uplink, the UE is not expected to transmit more than one aperiodic CSI report triggered by different DCIs on overlapping OFDM symbols. + +When the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], for the purpose of determining scheduling offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resources, the PDCCH candidate that ends later in time is used, and the UE does not expect that the aperiodic CSI-RS is transmitted before the first symbol of the PDCCH candidate that starts later in time. + +When a UE is configured with *dl-OrJointTCI-StateList* and is having two indicated TCI states, a higher layer configuration can be provided to an aperiodic CSI-RS resource set or a CSI-RS resource in an aperiodic CSI-RS resource set to inform that the UE shall apply the first or the second indicated TCI-State to the aperiodic CSI-RS resource set or to the CSI-RS resource in the aperiodic CSI-RS resource set, if the aperiodic CSI-RS resource set for CSI or BM is configured with *followUnifiedTCI-State* and if the offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resources in the aperiodic CSI-RS resource set is equal to or larger than a threshold. + +- If the UE is configured by higher layer parameter *PDCCH-Config* that contains two different values of *CORESETPoolIndex* in different *ControlResourceSets*, the first and the second indicated TCI-States correspond to the indicated TCI-States specific to *coresetPoolIndex* value 0 and value 1, respectively. + +When a UE is configured with *dl-OrJointTCI-StateList* and is having two indicated TCI states and if the offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resources in the aperiodic CSI-RS resource set is smaller than a threshold: + +- If there is no DL signal in the same symbols as the aperiodic CSI-RS + - if the UE is in frequency range 1, or the UE reports its capability of [two default beams for S-DCI based MTRP] in frequency range 2, the UE shall apply the first or the second indicated joint/DL TCI state to the aperiodic CSI-RS according to the higher layer configuration(s) provided to the aperiodic CSI-RS resource or to the aperiodic CSI-RS resource set + - otherwise, the UE shall apply the first indicated joint/DL TCI state to the aperiodic CSI-RS +- else if there is any other DL signal with an indicated TCI state in the same symbols as the CSI-RS, the UE applies the QCL assumption of the other DL signal also when receiving the aperiodic CSI-RS. The other DL signal refers to PDSCH scheduled with offset larger than or equal to the threshold *timeDurationForQCL*, as defined in [13, TS 38.306], periodic CSI-RS, semi-persistent CSI-RS, aperiodic CSI-RS in a *NZP-CSI-RS-ResourceSet* scheduled with offset larger than or equal to the UE reported threshold *beamSwitchTiming* when the reported value is one of the values $\{14, 28, 48\} \cdot 2^{\max(0, \mu_{\text{CSI-RS}}-3)}$ and when *enableBeamSwitchTiming* is not provided or the *NZP-CSI-RS-ResourceSet* is configured with the higher layer parameter *trs-Info*, aperiodic CSI-RS in a *NZP-CSI-RS-ResourceSet* configured with the higher layer parameter *repetition* set to 'off' or configured without the higher layer parameters *repetition* and *trs-Info* scheduled with offset larger than or equal to $48 \cdot 2^{\max(0, \mu_{\text{CSI-RS}}-3)}$ when the UE provides *beamSwitchTiming-r16* and *enableBeamSwitchTiming* is provided, aperiodic CSI-RS in a *NZP-CSI-RS-ResourceSet* configured with the higher layer parameter *repetition* set to 'on' scheduled with offset larger than or equal to the UE reported threshold *beamSwitchTiming-r16* and *enableBeamSwitchTiming* is provided. If there is a PDSCH applying two indicated joint/DL TCI states in the same symbols as the AP CSI-RS, the UE applies the first or the second indicated joint/DL TCI state to the AP CSI-RS according to the higher layer configuration(s) provided to the AP CSI-RS resource or to the aperiodic CSI-RS resource set. + +When a UE is configured with *dl-OrJointTCI-StateList*, is configured by higher layer parameter *PDCCH-Config* that contains two different values of *coresetPoolIndex* in different *ControlResourceSets*, is having two indicated TCI states and if the offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resources in the aperiodic CSI-RS resource set is smaller than a threshold: + +- If there is no DL signal in the same symbols as the aperiodic CSI-RS + - if the UE is in frequency range 1, or the UE reports its capability of [default beam per *coresetPoolIndex* for M-DCI based MTRP] in frequency range 2, the UE shall apply the first or the second indicated joint/DL TCI state to the aperiodic CSI-RS according to the higher layer configuration(s) provided to the aperiodic CSI-RS resource or aperiodic CSI-RS resource set + - otherwise, the UE shall apply the indicated joint/DL TCI state specific to *coresetPoolIndex* value 0 to the aperiodic CSI-RS resource set +- else if there is any other DL signal with an indicated TCI state in the same symbols as the CSI-RS, the UE applies the QCL assumption of the other DL signal also when receiving the aperiodic CSI-RS. The other DL signal refers to PDSCH scheduled with offset larger than or equal to the threshold *timeDurationForQCL*, as defined in [13, TS 38.306], periodic CSI-RS, semi-persistent CSI-RS, aperiodic CSI-RS in a *NZP-CSI-RS-ResourceSet* scheduled with offset larger than or equal to the UE reported threshold *beamSwitchTiming* when the reported value is one of the values $\{14, 28, 48\} \cdot 2^{\max(0, \mu_{\text{CSI-RS}}-3)}$ and when *enableBeamSwitchTiming* is not provided or the *NZP-CSI-RS-ResourceSet* is configured with the higher layer parameter *trs-Info*, aperiodic CSI-RS in a *NZP-CSI-RS-ResourceSet* configured with the higher layer parameter *repetition* set to 'off' or configured without the higher layer parameters *repetition* and *trs-Info* scheduled with offset larger than or equal to $48 \cdot 2^{\max(0, \mu_{\text{CSI-RS}}-3)}$ when the UE provides *beamSwitchTiming-r16* and *enableBeamSwitchTiming* is provided, aperiodic CSI-RS in a *NZP-CSI-RS-ResourceSet* configured with the higher layer parameter *repetition* set to 'on' scheduled with offset larger than or equal to the UE reported threshold *beamSwitchTiming-r16* and *enableBeamSwitchTiming* is provided. + +##### 5.2.1.5.1a Aperiodic CSI Reporting/Aperiodic CSI-RS when the triggering PDCCH and the CSI-RS have different numerologies + +When the triggering PDCCH and the triggered aperiodic CSI-RS are of different numerologies, the behavior defined in 5.2.1.5.1 for the case where the numerologies are the same applies with the following exceptions: + +Beam switch timing: + +- If the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resources in a *NZP-CSI-RS-ResourceSet* configured without higher layer parameter *trs-Info* is smaller than *beamSwitchTiming* + *d* in CSI-RS symbols, as defined in [13, TS 38.306], when the reported value is one of the values of {14, 28, 48} and *enableBeamSwitchTiming* is not provided, or is smaller than 48+ in CSI-RS symbols when the UE provides *beamSwitchTiming-r16* and *enableBeamSwitchTiming* is provided and the *NZP-CSI-RS-ResourceSet* is configured with the higher layer parameter *repetition* set to 'off' or configured without the higher layer parameter *repetition*, or is smaller than *beamSwitchTiming-r16* + *d* in CSI-RS symbols, when *enableBeamSwitchTiming* is provided and the *NZP-CSI-RS-ResourceSet* is configured with the higher layer parameter *repetition* set to 'on', where if the $\mu_{\text{PDCCH}} < \mu_{\text{CSI-RS}}$ , the beam switching timing delay *d* is defined in Table 5.2.1.5.1a-1, else *d* is zero +- if one of the associated trigger states has the higher layer parameter *qcl-Type* set to 'typeD', + - if there is any other DL signal with an indicated TCI state in the same symbols as the CSI-RS, the UE applies the QCL assumption of the other DL signal also when receiving the aperiodic CSI-RS. The other DL signal refers to PDSCH scheduled with offset larger than or equal to the threshold *timeDurationForQCL*, as defined in [13, TS 38.306], periodic CSI-RS, semi-persistent CSI-RS, aperiodic CSI-RS scheduled with offset larger than or equal to *beamSwitchTiming* + *d* in CSI-RS symbols when the reported value is one of the values {14,28,48} and when *enableBeamSwitchTiming* is not provided or the *NZP-CSI-RS-ResourceSet* is configured with the higher layer parameter *trs-Info*, aperiodic CSI-RS in a *NZP-CSI-RS-ResourceSet* configured with the higher layer parameter *repetition* set to 'off' or configured without the higher layer parameters *repetition* and *trs-Info* scheduled with offset larger than or equal to 48+ in CSI-RS symbols when the UE provides *beamSwitchTiming-r16* and *enableBeamSwitchTiming* is provided, aperiodic CSI-RS in a *NZP-CSI-RS-ResourceSet* configured with the higher layer parameter *repetition* set to 'on' and scheduled with offset larger than or equal to *beamSwitchTiming-r16* + *d* in CSI-RS symbols when *enableBeamSwitchTiming* is provided; + - else, + - if at least one CORESET is configured for the BWP in which the aperiodic CSI-RS is to be received, when receiving the aperiodic CSI-RS, the UE applies the QCL assumption used for the CORESET associated with a monitored search space with the lowest *controlResourceSetId* in the latest slot in which one or more CORESETs within the active BWP of the serving cell are monitored. + - else if the UE is configured with *enableDefaultBeamForCCS*, when receiving the aperiodic CSI-RS, the UE applies the QCL assumption of the lowest-ID activated TCI state applicable to the PDSCH within the active BWP of the cell in which the CSI-RS is to be received. +- If the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resources in a *NZP-CSI-RS-ResourceSet* is equal to or greater than *beamSwitchTiming* + *d* in CSI-RS symbols, when the reported value is one of the values of {14,28,48} and *enableBeamSwitchTiming* is not provided and the *NZP-CSI-RS-ResourceSet* is not configured with higher layer parameter *trs-Info*, or is equal to or greater than *beamSwitchTiming* + *d* in CSI-RS symbols when the reported value is one of the values of {14,28,48} and the *NZP-CSI-RS-ResourceSet* is configured with higher layer parameter *trs-Info*, or is equal to or greater than 48+ in CSI-RS symbols when the UE provides *beamSwitchTiming-r16* and *enableBeamSwitchTiming* is provided and the *NZP-CSI-RS-ResourceSet* is configured with the higher layer parameter *repetition* set to 'off' or configured without the higher layer parameters *repetition* and *trs-Info*, or is equal to or greater than *beamSwitchTiming-r16* + *d* in CSI-RS symbols when *enableBeamSwitchTiming* is provided and the *NZP-CSI-RS-ResourceSet* is configured with the higher layer parameter *repetition* set to 'on', where if the $\mu_{\text{PDCCH}} < \mu_{\text{CSI-RS}}$ , the beam switching timing delay *d* is defined in Table 5.2.1.5.1a-1, else *d* is zero, the UE is expected to apply the QCL assumptions in the indicated TCI states for the aperiodic CSI-RS resources in the CSI triggering state indicated by the CSI trigger field in DCI. For $\mu_{\text{PDCCH}} = 5$ , UE shall report one of values of {56, 112} for additional beam switching time delay *d*. + +**Table 5.2.1.5.1a-1: Additional beam switching timing delay $d$** + +| $\mu_{PDCCH}$ | $d$ [PDCCH symbols] | +|---------------|---------------------| +| 0 | 8 | +| 1 | 8 | +| 2 | 14 | +| 3 | 28 | +| 5 | {56, 112} | + +Aperiodic CSI-RS timing: + +- When the aperiodic CSI-RS is used with aperiodic CSI reporting, the CSI-RS triggering offset $X$ is configured per resource set by the higher layer parameter *aperiodicTriggeringOffset* or *aperiodicTriggeringOffset-r16* or *aperiodicTriggeringOffset-r17*, including the case that the UE is not configured with *minimumSchedulingOffsetK0* for any DL BWP or *minimumSchedulingOffsetK2* for any UL BWP and all the associated trigger states do not have the higher layer parameter *qcl-Type* set to 'typeD' in the corresponding TCI states. The CSI-RS triggering offset has the values of {0, 1, ..., 31} slots for $\mu_{PDCCH} < \mu_{CSIRS}$ and {0, 4, 8, ..., 124} slots for $\mu_{PDCCH} < \mu_{CSIRS}$ and {0, 1, 2, 3, 4, 5, 6, ..., 15, 16, 24} slots for $\mu_{PDCCH} < \mu_{CSIRS}$ and {0, 4, 8, 12, ..., 60, 64, 96} slots for $\mu_{PDCCH} > \mu_{CSIRS}$ . The aperiodic CSI-RS is transmitted in a slot + +$$\left\lceil n \cdot \frac{2^{\mu_{CSIRS}}}{2^{\mu_{PDCCH}}} \right\rceil + X + \left\lceil \left( \frac{N_{slot,offset,PDCCH}^{CA}}{2^{\mu_{offset,PDCCH}}} - \frac{N_{slot,offset,CSIRS}^{CA}}{2^{\mu_{offset,CSIRS}}} \right) \cdot 2^{\mu_{CSIRS}} \right\rceil, \text{ if UE is configured with } ca\text{-SlotOffset for at least one of the triggered and triggering cell, and } K_s = \left\lceil n \cdot \frac{2^{\mu_{CSIRS}}}{2^{\mu_{PDCCH}}} \right\rceil + X, \text{ otherwise, and where}$$ + +- $n$ is the slot containing the triggering DCI, $X$ is the CSI-RS triggering offset in the numerology of CSI-RS according to the higher layer parameter *aperiodicTriggeringOffset* or *aperiodicTriggeringOffset-r16* or *aperiodicTriggeringOffset-r17*, +- $\mu_{PDCCH}$ and $\mu_{CSIRS}$ are the subcarrier spacing configurations for PDCCH and CSI-RS, respectively, +- $\mu_{offset,PDCCH}$ and $\mu_{offset,CSIRS}$ are the and the $\mu_{offset}$ , respectively, which are determined by higher-layer configured *ca-SlotOffset* for the cell receiving the PDCCH respectively, and $\mu_{offset,PDCCH}$ and $\mu_{offset,CSIRS}$ are the and the $\mu_{offset}$ , respectively, which are determined by higher-layer configured *ca-SlotOffset* for the cell transmitting the CSI-RS respectively, as defined in [4, TS 38.211] clause 4.5 +- If the $\mu_{PDCCH} < \mu_{CSIRS}$ , the UE is expected to be able to measure the aperiodic CSI RS, if the CSI-RS starts no earlier than the first symbol of the CSI-RS carrier's slot that starts at least $N_{csirs}$ PDCCH symbols after the end of the PDCCH triggering the aperiodic CSI-RS. +- If the $\mu_{PDCCH} > \mu_{CSIRS}$ , the UE is expected to be able to measure the aperiodic CSI RS, if the CSI-RS starts no earlier than at least $N_{csirs}$ PDCCH symbols after the end of the PDCCH triggering the aperiodic CSI-RS. + +When the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], for the purpose of determining $N_{csirs}$ , the PDCCH candidate that ends later in time is used. + +**Table 5.2.1.5.1a: $N_{csirs}$ as a function of the subcarrier spacing of the triggering PDCCH** + +| $\mu_{PDCCH}$ | $N_{csirs}$ [symbols] | +|---------------|-----------------------| +| 0 | 4 | +| 1 | 5 | +| 2 | 10 | +| 3 | 14 | +| 5 | 56 | +| 6 | 112 | + +When the triggering PDCCH and the triggered aperiodic CSI-RS are of different numerologies, the CSI request constraint and CSI reporting constraint defined in 5.2.1.5.1 for the case where the numerologies are the same applies with the following additions: + +- CSI request constraints: + - A UE is not expected to receive more than one CSI request per reference slot length across all CCs in a cell group, where the SCS of the reference slot is the minimum of SCS of the PDCCH with which the DCI was transmitted, the SCS of the PUSCH with which the CSI report is to be transmitted, and the SCS of the minimum SCS of the CSI-RS associated to the CSI reports triggered by the DCI. The beginning of a slot length is defined according the PDCCH cell with which the DCI carrying the CSI request is transmitted. +- CSI reporting constraints: + - A UE is not expected to receive more than one CSI request for transmission in a given reference slot length across all CCs in a cell group, where the SCS of the reference slot is the minimum of SCS of the PDCCH with which the DCI was transmitted, the SCS of the PUSCH with which the CSI report is to be transmitted, and the SCS of the minimum SCS of the CSI-RS associated to the CSI reports triggered by the DCI. The beginning of a slot length is defined according the PUSCH cell with which the CSI report is transmitted. + +##### 5.2.1.5.2 Semi-persistent CSI/Semi-persistent CSI-RS + +For semi-persistent reporting on PUSCH, a set of trigger states are higher layer configured by *CSI-SemiPersistentOnPUSCH-TriggerStateList*, where the CSI request field in DCI scrambled with SP-CSI-RNTI activates one of the trigger states. For a reporting setting for which the *CSI-ReportConfig* contains a list of sub-configurations, provided by the higher layer parameter [*csi-ReportSubConfigList*], one or more trigger states can be configured with each indicating one or more of the sub-configurations. A UE is not expected to receive a DCI scrambled with SP-CSI-RNTI activating one semi-persistent CSI report with the same *CSI-ReportConfigId* as in a semi-persistent CSI report which is activated by a previously received DCI scrambled with SP-CSI-RNTI. + +For semi-persistent reporting on PUCCH, the PUCCH resource used for transmitting the CSI report are configured by *reportConfigType*. Semi-persistent reporting on PUCCH is activated by an activation command as described in clause 6.1.3.16 of [10, TS 38.321], which selects one of the semi-persistent Reporting Settings for use by the UE on the PUCCH. For a selected reporting setting for which the *CSI-ReportConfig* contains a list of sub-configurations provided by the higher layer parameter [*csi-ReportSubConfigList*], [an/the] activation command can [also] select one or more sub-configurations to use by the UE as described in clause 6.1.3.X of [10, TS 38.321]. When the UE would transmit a PUCCH with HARQ-ACK information in slot $n$ corresponding to the PDSCH carrying the activation command, the indicated semi-persistent Reporting Setting should be applied starting from the first slot that is after slot $n$ where $\mu$ is the SCS configuration for the PUCCH. + +For a UE configured with CSI resource setting(s) where the higher layer parameter *resourceType* set to 'semiPersistent'. + +- when a UE receives an activation command, as described in clause 6.1.3.12 of [10, TS 38.321], for CSI-RS resource set(s) for channel measurement and CSI-IM/NZP CSI-RS resource set(s) for interference measurement associated with configured CSI resource setting(s), and when the UE would transmit a PUCCH with HARQ-ACK information in slot $n$ corresponding to the PDSCH carrying the selection command, the corresponding actions in [10, TS 38.321] and the UE assumptions (including QCL assumptions provided by a list of reference to *TCI-State's*, one per activated resource) on CSI-RS/CSI-IM transmission corresponding to the configured CSI-RS/CSI-IM resource configuration(s) shall be applied starting from the first slot that is after slot $n$ where $\mu$ is the SCS configuration for the PUCCH and is the subcarrier spacing configuration for with a value of 0 for frequency range 1, and is provided by *K-Mac* or if *K-Mac* is not provided. If a *TCI-State* referred to in the list is configured with a reference to an RS configured with *qcl-Type* set to 'typeD', that RS can be an SS/PBCH block, periodic or semi-persistent CSI-RS located in same or different CC/DL BWP. +- when a UE receives a deactivation command, as described in clause 6.1.3.12 of [10, TS 38.321], for activated CSI-RS/CSI-IM resource set(s) associated with configured CSI resource setting(s), and when the UE would transmit a PUCCH with HARQ-ACK information in slot $n$ corresponding to the PDSCH carrying the deactivation command, the corresponding actions in [10, TS 38.321] and UE assumption on cessation of CSI-RS/CSI-IM transmission corresponding to the deactivated CSI-RS/CSI-IM resource set(s) shall apply starting from the first slot that is after slot $n$ where $\mu$ is the SCS configuration for the PUCCH and is the subcarrier spacing configuration for with a value of 0 for frequency range 1, and is provided by *K-Mac* or if *K-Mac* is not provided. + +A codepoint of the CSI request field in the DCI is mapped to a SP-CSI triggering state according to the order of the positions of the configured trigger states in *CSI-SemiPersistentOnPUSCH-TriggerStateList*, with codepoint '0' mapped to the triggering state in the first position. A UE validates, for semi-persistent CSI activation or release, a PDCCH on a DCI only if the following conditions are met: + +- the CRC parity bits of the DCI format are scrambled with a SP-CSI-RNTI provided by higher layer parameter *sp-CSI-RNTI* +- Special fields for the DCI format are set according to Table 5.2.1.5.2-1 or Table 5.2.1.5.2-2. + +If validation is achieved, the UE considers the information in the DCI format as a valid activation or valid release of semi-persistent CSI transmission on PUSCH, and the UE activates or deactivates a CSI Reporting Setting indicated by CSI request field in the DCI. If validation is not achieved, the UE considers the DCI format as having been detected with a non-matching CRC. + +**Table 5.2.1.5.2-1: Special fields for semi-persistent CSI activation PDCCH validation** + +| | DCI format 0_1/0_2 | +|-------------------------------------|--------------------| +| HARQ process number
(if present) | set to all '0's | +| Redundancy version
(if present) | set to all '0's | + +**Table 5.2.1.5.2-2: Special fields for semi-persistent CSI deactivation PDCCH validation** + +| | DCI format 0_1/0_2 | +|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HARQ process number
(if present) | set to all '0's | +| Modulation and coding scheme | set to all '1's | +| Resource block assignment | If higher layer configures RA type 0 only, set to all '0's;
If higher layer configures RA type 1 only, set to all '1's;
If higher layer configures dynamic switch between RA type 0 and 1, then if MSB is '0', set to all '0's; else, set to all '1's
For DCI 0_1, if higher layer configures RA type 2, set to all '1's if $\mu = 0$ ; set to all '0's if $\mu = 1$ | +| Redundancy version
(if present) | set to all '0's | + +If the UE has an active semi-persistent CSI-RS/CSI-IM resource configuration, or an active semi-persistent ZP CSI-RS resource set configuration, and has not received a deactivation command, the activated semi-persistent CSI-RS/CSI-IM resource set or the activated semi-persistent ZP CSI-RS resource set configurations are considered to be active when the corresponding DL BWP is active, otherwise they are considered suspended. + +If the UE is configured with carrier deactivation, the following configurations in the carrier in activated state would also be deactivated and need re-activation configuration(s): semi-persistent CSI-RS/CSI-IM resource, semi-persistent CSI reporting on PUCCH, semi-persistent SRS, semi-persistent ZP CSI-RS resource set. + +##### 5.2.1.5.3 Aperiodic CSI-RS for tracking for fast SCell activation + +When the UE receives an *Enhanced SCell Activation/Deactivation* MAC-CE that triggers one or two CSI-RS bursts for fast SCell activation for a (set of) deactivated SCell(s), + +- if the MAC-CE indicates that the first CSI-RS burst for SCell activation is present in an SCell, then the UE may assume that the first CSI-RS burst for SCell activation is present in that SCell. The first slot of the first CSI-RS burst starts at the $m_1^{\text{th}}$ SCell slot after the last SCell slot coinciding with the reference slot $n+k$ , as defined in clause 4.3 of [6, TS38.213]. +- if the MAC-CE indicates that the second CSI-RS burst for SCell activation is present in an SCell, then the UE may assume that the second CSI-RS burst for SCell activation is present in that SCell. The first slot of the second CSI-RS burst starts at the $m_2^{\text{th}}$ SCell slot after the end of the first CSI-RS burst. The CSI-RS of the second burst shall have the same antenna port index, OFDM symbol allocations in a slot, same PRB allocation location as the CSI-RS of the first burst. + +- where the CSI-RS burst is defined as four CSI-RS resources in two consecutive slots in clause 5.1.6.1.1.1, and $m_1$ and $m_2$ are provided by *aperiodicTriggeringOffsetL2* in *NZP-CSI-RS-ResourceSet* and *gapBetweenBursts*, respectively, associated with the CSI-RS burst(s) triggered by the MAC-CE. + +#### 5.2.1.6 CSI processing criteria + +The UE indicates the number of supported simultaneous CSI calculations with parameter *simultaneousCSI-ReportsPerCC* in a component carrier, and *simultaneousCSI-ReportsAllCC* across all component carriers. If a UE supports simultaneous CSI calculations it is said to have CSI processing units for processing CSI reports. If $L$ CPUs are occupied for calculation of CSI reports in a given OFDM symbol, the UE has unoccupied CPUs. If $N$ CSI reports start occupying their respective CPUs on the same OFDM symbol on which CPUs are unoccupied, where each CSI report corresponds to , the UE is not required to update the requested CSI reports with lowest priority (according to Clause 5.2.5), where is the largest value such that holds. + +A UE is not expected to be configured with an aperiodic CSI trigger state containing more than Reporting Settings. Processing of a CSI report occupies a number of CPUs for a number of symbols as follows: + +- for a CSI report with *CSI-ReportConfig* with higher layer parameter *reportQuantity* set to 'none' and *CSI-RS-ResourceSet* with higher layer parameter *trs-Info* configured +- for a CSI report with *LTM-CSI-ReportConfig* or a CSI report with *CSI-ReportConfig* with higher layer parameter *reportQuantity* set to 'cri-RSRP', 'ssb-Index-RSRP', 'cri-SINR', 'ssb-Index-SINR', 'cri-RSRP- Index', 'ssb-Index-RSRP- Index', 'cri-SINR- Index', 'ssb-Index-SINR- Index ' or 'none' (and *CSI-RS-ResourceSet* with higher layer parameter *trs-Info* not configured) +- , for a CSI report with *CSI-ReportConfig* with higher layer parameter *reportQuantity* set to 'tdcp' and with number of delays configured by higher layer parameter $Y$ , where the value of is reported by UE capability. +- for a CSI report with *CSI-ReportConfig* with higher layer parameter *reportQuantity* set to 'cri-RI-PMI-CQI', 'cri-RI-i1', 'cri-RI-i1-CQI', 'cri-RI-CQI', or 'cri-RI-LI-PMI-CQI', + - if $\max\{\mu_{PDCCCH}, \mu_{CSI-RS}, \mu_{UL}\} \leq 3$ , and if a CSI report is aperiodically triggered without transmitting a PUSCH with either transport block or HARQ-ACK or both when $L = 0$ CPUs are occupied, where the CSI corresponds to a single CSI with wideband frequency-granularity and to at most 4 CSI-RS ports in a single resource without CRI report and where *codebookType* is set to 'typeI-SinglePanel' or where *reportQuantity* is set to 'cri-RI-CQI', , + - if a *CSI-ReportConfig* is configured with *codebookType* set to 'typeI-SinglePanel' and the corresponding CSI-RS Resource Set for channel measurement is configured with two Resource Groups and Resource Pairs, , where is the number of CPUs occupied by a pair of CMRs subject to *mTRP-CSI-numCPU-r17* and is defined in clause 5.2.1.4.2, + - if a *CSI-ReportConfig* contains a list of $L$ sub-configurations provided by the higher layer parameter [*csi-ReportSubConfigList*], + - for periodic CSI reporting, where is the total number of CSI-RS resources corresponding to the $i$ -th sub-configuration. + - for aperiodic and semi-persistent CSI reporting, where is the total number of CSI-RS resources corresponding to the $i$ -th sub-configuration, and where the $i$ -th sub-configuration is from $N$ indicated sub-configurations out of $L$ sub-configurations contained in a *CSI-ReportConfig*, where and . + - if a *CSI-ReportConfig* is configured with the higher layer parameter *reportQuantity* set to 'cri-RI-PMI-CQI', *codebookType* set to 'typeII-CJT-r18' or 'typeII-CJT-PortSelection-r18' and the corresponding *NZP-CSI-RS-ResourceSet* for channel measurement is configured with resources, , where is reported by UE capability indication, + - if a *CSI-ReportConfig* is configured with the higher layer parameter *reportQuantity* set to 'cri-RI-PMI-CQI' and with *codebookType* set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18', + - if the corresponding CSI-RS Resource Set for channel measurement is aperiodic and configured with CSI-RS resources, for and for , where is reported by UE capability indication, + +- if the corresponding CSI-RS Resource Set for channel measurement is periodic or semi-persistent and configured with a single CSI-RS resource, for $N_1$ and $N_2$ , where the value of $N_1$ is configured by the higher layer parameter $N_4$ , and is reported by UE capability indication, +- otherwise, $N_2$ , where $N_2$ is the number of CSI-RS resources in the CSI-RS resource set for channel measurement. + +For a CSI report with *CSI-ReportConfig* with higher layer parameter *reportQuantity* not set to 'none', the CPU(s) are occupied for a number of OFDM symbols as follows: + +- A periodic or semi-persistent CSI report (excluding an initial semi-persistent CSI report on PUSCH after the PDCCH triggering the report and a semi-persistent CSI report on PUSCH configured with the higher layer parameter *codebookType* set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18') occupies CPU(s) from the first symbol of the earliest one of each CSI-RS/CSI-IM/SSB resource, or each CSI-RS/CSI-IM resource associated with all configured sub-configurations for periodic CSI report corresponding to a *CSI-ReportConfig* that contains a list of sub-configurations provided by *csi-ReportSubConfigList*, or each CSI-RS/CSI-IM resource associated with all triggered sub-configurations for semi-persistent CSI report corresponding to a *CSI-ReportConfig* that contains a list of sub-configurations provided by *csi-ReportSubConfigList*, for channel or interference measurement, respective latest CSI-RS/CSI-IM/SSB occasion no later than the corresponding CSI reference resource, until the last symbol of the configured PUSCH/PUCCH carrying the report. +- An aperiodic CSI report occupies CPU(s) from the first symbol after the PDCCH triggering the CSI report until the last symbol of the scheduled PUSCH carrying the report. When the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], for the purpose of determining the CPU occupation duration, the PDCCH candidate that ends later in time is used. +- An initial semi-persistent CSI report on PUSCH after the PDCCH trigger occupies CPU(s) from the first symbol after the PDCCH until the last symbol of the scheduled PUSCH carrying the report. When the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], for the purpose of determining the CPU occupation duration, the PDCCH candidate that ends later in time is used. +- A semi-persistent CSI report on PUSCH configured with the higher layer parameter *codebookType* set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18' occupies CPU(s) from the first symbol of $K_p$ -th latest consecutive periodic/semi-persistent CSI-RS occasions no later than CSI reference resource, until the last symbol of the PUSCH carrying the report, where the value of $K_p$ is indicated by UE capability. + +For a CSI report with *CSI-ReportConfig* with higher layer parameter *reportQuantity* set to 'none' and *CSI-RS-ResourceSet* with higher layer parameter *trs-Info* not configured, the CPU(s) are occupied for a number of OFDM symbols as follows: + +- A semi-persistent CSI report (excluding an initial semi-persistent CSI report on PUSCH after the PDCCH triggering the report) occupies CPU(s) from the first symbol of the earliest one of each transmission occasion of periodic or semi-persistent CSI-RS/SSB resource for channel measurement for L1-RSRP computation, until symbols after the last symbol of the latest one of the CSI-RS/SSB resource for channel measurement for L1-RSRP computation in each transmission occasion. +- An aperiodic CSI report occupies CPU(s) from the first symbol after the PDCCH triggering the CSI report until the last symbol between symbols after the first symbol after the PDCCH triggering the CSI report and symbols after the last symbol of the latest one of each CSI-RS/SSB resource for channel measurement for L1-RSRP computation. + +where $N_1$ and $N_2$ are defined in the table 5.4-2. + +In any slot, the UE is not expected to have more active CSI-RS ports or active CSI-RS resources in active BWPs than reported as capability. NZP CSI-RS resource is active in a duration of time defined as follows. For aperiodic CSI-RS, starting from the end of the PDCCH containing the request and ending at the end of the scheduled PUSCH containing the report associated with this aperiodic CSI-RS. When the PDCCH candidates are associated with a search space set configured with *searchSpaceLinkingId*, for the purpose of determining the NZP CSI-RS resource active duration, the PDCCH candidate that ends later in time among the two linked PDCCH candidates is used. For semi-persistent CSI-RS, starting from the end of when the activation command is applied, and ending at the end of when the deactivation command is applied. For periodic CSI-RS, starting when the periodic CSI-RS is configured by higher layer signalling, and ending when the periodic CSI-RS configuration is released. + +If a CSI-RS resource is referred $N$ times by one or more CSI Reporting Settings not configured with higher layer parameter *csi-ReportSubConfigList*, the CSI-RS resource and the CSI-RS ports within the CSI-RS resource are counted $N$ times. + +For a CSI-RS Resource Set for channel measurement configured with two Resource Groups and Resource Pairs, if a CSI-RS resource is referred times by one of the CSI-RS resources, where is defined in clause 5.2.1.4.2, and/or one or two Resource Pairs, the CSI-RS resource and the CSI-RS ports within the CSI-RS resource are counted times. + +For a *CSI-ReportConfig* containing a list of $L$ sub-configuration(s) provided by higher layer parameter *csi-ReportSubConfigList*, if a CSI-RS resource is referred by $M$ sub-configurations among $N$ triggered sub-configurations for CSI reporting for aperiodic CSI-RS resource, or $L$ configured sub-configurations for CSI reporting for periodic or semi-persistent CSI-RS resource, the CSI-RS resource is counted $M$ times and the CSI-RS ports within the CSI-RS resource are counted , where $P$ is the number of ports configured by *nrofPorts* and is the number of CSI-RS ports in sub-configuration $s$ derived from the corresponding antenna port subset indicator [*port-subsetIndicator*] according to clause 5.2.1.4.2 if configured, otherwise . + +For a periodic or semi-persistent CSI-RS resource in a CSI-RS resource set for channel measurement linked to a *CSI-ReportConfig* configured with the higher layer parameter *codebookType* set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18', the CSI-RS resource and the CSI-RS ports within the CSI-RS resource are counted times, where the value of is indicated by UE capability. + +### 5.2.2 Channel state information + +#### 5.2.2.1 Channel quality indicator (CQI) + +The CQI indices and their interpretations are given in Table 5.2.2.1-2 or Table 5.2.2.1-4 for reporting CQI based on QPSK, 16QAM and 64QAM. The CQI indices and their interpretations are given in Table 5.2.2.1-3 for reporting CQI based on QPSK, 16QAM, 64QAM and 256QAM. The CQI indices and their interpretations are given in Table 5.2.2.1-5 for reporting CQI based on QPSK, 16QAM, 64QAM, 256QAM and 1024 QAM. + +Based on an unrestricted observation interval in time unless specified otherwise in this Clause, and an unrestricted observation interval in frequency, the UE shall derive for each CQI value reported in uplink slot $n$ the highest CQI index which satisfies the following condition: + +- A single PDSCH transport block with a combination of modulation scheme, target code rate and transport block size corresponding to the CQI index, and occupying a group of downlink physical resource blocks termed the CSI reference resource, could be received with a transport block error probability not exceeding: + - 0.1, if the higher layer parameter *cqi-Table* in *CSI-ReportConfig* configures 'table1' (corresponding to Table 5.2.2.1-2), or 'table2' (corresponding to Table 5.2.2.1-3), or if the higher layer parameter *cqi-Table* in *CSI-ReportConfig* configures 'table4-r17' (corresponding to Table 5.2.2.1-5), or + - 0.00001, if the higher layer parameter *cqi-Table* in *CSI-ReportConfig* configures 'table3' (corresponding to Table 5.2.2.1-4). + +If the higher layer parameter *timeRestrictionForChannelMeasurements* is set to "notConfigured", the UE shall derive the channel measurements for computing CSI value reported in uplink slot $n$ based on only the NZP CSI-RS, no later than the CSI reference resource, (defined in TS 38.211[4]) associated with the CSI resource setting. + +If the higher layer parameter *timeRestrictionForChannelMeasurements* in *CSI-ReportConfig* is set to "Configured", the UE shall derive the channel measurements for computing CSI reported in uplink slot $n$ based on only the most recent, no later than the CSI reference resource, in cell DTX active time if cell DTX is activated, occasion of NZP CSI-RS (defined in [4, TS 38.211]) associated with the CSI resource setting. + +If the higher layer parameter *timeRestrictionForInterferenceMeasurements* is set to "notConfigured", the UE shall derive the interference measurements for computing CSI value reported in uplink slot $n$ based on only the CSI-IM and/or NZP CSI-RS for interference measurement no later than the CSI reference resource associated with the CSI resource setting. + +If the higher layer parameter *timeRestrictionForInterferenceMeasurements* in *CSI-ReportConfig* is set to "Configured", the UE shall derive the interference measurements for computing the CSI value reported in uplink slot $n$ based on the most recent, no later than the CSI reference resource, in cell DTX active time if cell DTX is activated, occasion of CSI- + +IM and/or NZP CSI-RS for interference measurement (defined in [4, TS 38.211]) associated with the CSI resource setting. + +If the higher layer parameter *cqi-BitsPerSubband* in *CSI-ReportConfig* is not configured, for each sub-band index *s*, a 2-bit sub-band differential CQI is defined as: + +- Sub-band Offset level (*s*) = sub-band CQI index (*s*) - wideband CQI index. + +The mapping from the 2-bit sub-band differential CQI values to the offset level is shown in Table 5.2.2.1-1 + +**Table 5.2.2.1-1: Mapping sub-band differential CQI value to offset level** + +| Sub-band differential CQI value | Offset level | +|---------------------------------|--------------| +| 0 | 0 | +| 1 | 1 | +| 2 | $\geq 2$ | +| 3 | $\leq -1$ | + +If the higher layer parameter *cqi-BitsPerSubband* in *CSI-ReportConfig* is configured, for each sub-band index *s*, a 4-bit sub-band CQI is reported. The 4-bit sub-band CQI for each sub-band *s* is a CQI index in Table 5.2.2.1-2, Table 5.2.2.1-3, or Table 5.2.2.1-4 as configured by the higher layer parameter *cqi-Table* in *CSI-ReportConfig*. + +A combination of modulation scheme and transport block size corresponds to a CQI index if: + +- the combination could be signaled for transmission on the PDSCH in the CSI reference resource according to the Transport Block Size determination described in Clause 5.1.3.2, and +- the modulation scheme is indicated by the CQI index, and +- the combination of transport block size and modulation scheme when applied to the reference resource results in the effective channel code rate which is the closest possible to the code rate indicated by the CQI index. If more than one combination of transport block size and modulation scheme results in an effective channel code rate equally close to the code rate indicated by the CQI index, only the combination with the smallest of such transport block sizes is relevant. + +**Table 5.2.2.1-2: 4-bit CQI Table** + +| CQI index | modulation | code rate x 1024 | efficiency | +|-----------|--------------|------------------|------------| +| 0 | out of range | | | +| 1 | QPSK | 78 | 0.1523 | +| 2 | QPSK | 120 | 0.2344 | +| 3 | QPSK | 193 | 0.3770 | +| 4 | QPSK | 308 | 0.6016 | +| 5 | QPSK | 449 | 0.8770 | +| 6 | QPSK | 602 | 1.1758 | +| 7 | 16QAM | 378 | 1.4766 | +| 8 | 16QAM | 490 | 1.9141 | +| 9 | 16QAM | 616 | 2.4063 | +| 10 | 64QAM | 466 | 2.7305 | +| 11 | 64QAM | 567 | 3.3223 | +| 12 | 64QAM | 666 | 3.9023 | +| 13 | 64QAM | 772 | 4.5234 | +| 14 | 64QAM | 873 | 5.1152 | +| 15 | 64QAM | 948 | 5.5547 | + +**Table 5.2.2.1-3: 4-bit CQI Table 2** + +| CQI index | modulation | code rate x 1024 | efficiency | +|-----------|--------------|------------------|------------| +| 0 | out of range | | | +| 1 | QPSK | 78 | 0.1523 | +| 2 | QPSK | 193 | 0.3770 | +| 3 | QPSK | 449 | 0.8770 | +| 4 | 16QAM | 378 | 1.4766 | +| 5 | 16QAM | 490 | 1.9141 | +| 6 | 16QAM | 616 | 2.4063 | +| 7 | 64QAM | 466 | 2.7305 | +| 8 | 64QAM | 567 | 3.3223 | +| 9 | 64QAM | 666 | 3.9023 | +| 10 | 64QAM | 772 | 4.5234 | +| 11 | 64QAM | 873 | 5.1152 | +| 12 | 256QAM | 711 | 5.5547 | +| 13 | 256QAM | 797 | 6.2266 | +| 14 | 256QAM | 885 | 6.9141 | +| 15 | 256QAM | 948 | 7.4063 | + +**Table 5.2.2.1-4: 4-bit CQI Table 3** + +| CQI index | modulation | code rate x 1024 | efficiency | +|-----------|--------------|------------------|------------| +| 0 | out of range | | | +| 1 | QPSK | 30 | 0.0586 | +| 2 | QPSK | 50 | 0.0977 | +| 3 | QPSK | 78 | 0.1523 | +| 4 | QPSK | 120 | 0.2344 | +| 5 | QPSK | 193 | 0.3770 | +| 6 | QPSK | 308 | 0.6016 | +| 7 | QPSK | 449 | 0.8770 | +| 8 | QPSK | 602 | 1.1758 | +| 9 | 16QAM | 378 | 1.4766 | +| 10 | 16QAM | 490 | 1.9141 | +| 11 | 16QAM | 616 | 2.4063 | +| 12 | 64QAM | 466 | 2.7305 | +| 13 | 64QAM | 567 | 3.3223 | +| 14 | 64QAM | 666 | 3.9023 | +| 15 | 64QAM | 772 | 4.5234 | + +**Table 5.2.2.1-5: 4-bit CQI Table 4** + +| CQI index | modulation | code rate x 1024 | efficiency | +|-----------|--------------|------------------|------------| +| 0 | out of range | | | +| 1 | QPSK | 78 | 0.1523 | +| 2 | QPSK | 193 | 0.377 | +| 3 | QPSK | 449 | 0.877 | +| 4 | 16QAM | 378 | 1.4766 | +| 5 | 16QAM | 616 | 2.4063 | +| 6 | 64QAM | 567 | 3.3223 | +| 7 | 64QAM | 666 | 3.9023 | +| 8 | 64QAM | 772 | 4.5234 | +| 9 | 64QAM | 873 | 5.1152 | +| 10 | 256QAM | 711 | 5.5547 | +| 11 | 256QAM | 797 | 6.2266 | +| 12 | 256QAM | 885 | 6.9141 | +| 13 | 256QAM | 948 | 7.4063 | +| 14 | 1024QAM | 853 | 8.3301 | +| 15 | 1024QAM | 948 | 9.2578 | + +##### 5.2.2.1.1 (void) + +#### 5.2.2.2 Precoding matrix indicator (PMI) + +##### 5.2.2.2.1 Type I Single-Panel Codebook + +For 2 antenna ports {3000, 3001} and the UE configured with higher layer parameter *codebookType* set to 'typeI-SinglePanel' each PMI value corresponds to a codebook index given in Table 5.2.2.2.1-1. The UE is configured with the higher layer parameter *twoTX-CodebookSubsetRestriction*. The bitmap parameter *twoTX-CodebookSubsetRestriction* forms the bit sequence $a_5, \dots, a_1, a_0$ where $a_0$ is the LSB and $a_5$ is the MSB and where a bit value of zero indicates that PMI reporting is not allowed to correspond to the precoder associated with the bit. Bits 0 to 3 are associated respectively with the codebook indices 0 to 3 for $v=1$ layer, and bits 4 and 5 are associated respectively with the codebook indices 0 and 1 for $v=2$ layers. + +**Table 5.2.2.2.1-1: Codebooks for 1-layer and 2-layer CSI reporting using antenna ports 3000 to 3001** + +| Codebook index | Number of layers $v$ | | +|----------------|------------------------------------------------------------|---| +| | 1 | 2 | +| 0 | | | +| 1 | $\frac{1}{\sqrt{2}} \begin{bmatrix} 1 \\ j \end{bmatrix}$ | | +| 2 | $\frac{1}{\sqrt{2}} \begin{bmatrix} 1 \\ -1 \end{bmatrix}$ | - | +| 3 | | - | + +For 4 antenna ports {3000, 3001, 3002, 3003}, 8 antenna ports {3000, 3001, ..., 3007}, 12 antenna ports {3000, 3001, ..., 3011}, 16 antenna ports {3000, 3001, ..., 3015}, 24 antenna ports {3000, 3001, ..., 3023}, and 32 antenna ports {3000, 3001, ..., 3031}, and the UE configured with higher layer parameter *codebookType* set to 'typeI-SinglePanel', except when the number of layers $v \in \{2, 3, 4\}$ (where $v$ is the associated RI value), each PMI value corresponds to three codebook indices $i_{1,1}, i_{1,2}, i_2$ . When the number of layers $v \in \{2, 3, 4\}$ , each PMI value corresponds to four codebook indices $i_{1,1}, i_{1,2}, i_{1,3}, i_2$ . The composite codebook index $i_1$ is defined by + +$$i_1 = \begin{cases} \begin{bmatrix} i_{1,1} & i_{1,2} \end{bmatrix} & v \notin \{2, 3, 4\} \\ \begin{bmatrix} i_{1,1} & i_{1,2} & i_{1,3} \end{bmatrix} & v \in \{2, 3, 4\} \end{cases}$$ + +The codebooks for 1-8 layers are given respectively in Tables 5.2.2.2.1-5, 5.2.2.2.1-6, 5.2.2.2.1-7, 5.2.2.2.1-8, 5.2.2.2.1-9, 5.2.2.2.1-10, 5.2.2.2.1-11, and 5.2.2.2.1-12. The mapping from $i_{1,3}$ to $k_1$ and $k_2$ for 2-layer reporting is given in Table 5.2.2.2.1-3. The mapping from $i_{1,3}$ to $k_1$ and $k_2$ for 3-layer and 4-layer reporting when $P_{\text{CSI-RS}} < 16$ is given in Table 5.2.2.2.1-4. The quantities $\varphi_n, \theta_p, u_m, \tilde{v}_{l,m}$ are given by + +$$\begin{aligned} + \varphi_n &= e^{j\pi n/2} \\ + \theta_p &= e^{j\pi p/4} \\ + u_m &= \begin{cases} \begin{bmatrix} 1 & e^{j\frac{2\pi m}{O_2 N_2}} & \dots & e^{j\frac{2\pi m(N_2-1)}{O_2 N_2}} \end{bmatrix} & N_2 > 1 \\ 1 & N_2 = 1 \end{cases} \\ + v_{l,m} &= \begin{bmatrix} u_m & e^{j\frac{2\pi l}{O_1 N_1}} u_m & \dots & e^{j\frac{2\pi l(N_1-1)}{O_1 N_1}} u_m \end{bmatrix}^T \\ + \tilde{v}_{l,m} &= \begin{bmatrix} u_m & e^{j\frac{4\pi l}{O_1 N_1}} u_m & \dots & e^{j\frac{4\pi l(N_1/2-1)}{O_1 N_1}} u_m \end{bmatrix}^T + \end{aligned}$$ + +- The values of $n1$ and $n2$ are configured with the higher layer parameter $n1-n2$ , respectively. The supported configurations of $n1$ and $n2$ for a given number of CSI-RS ports and the corresponding values of $(O_1, O_2)$ are given in Table 5.2.2.2.1-2. The number of CSI-RS ports, $P_{\text{CSI-RS}}$ , is. +- UE shall only use $n1$ and $n2$ and shall not report $n1$ if the value of $N_2$ is 1. + +The bitmap parameter $n1-n2$ forms the bit sequence $a_{A_c-1}, \dots, a_1, a_0$ where $a_0$ is the LSB and $a_{A_c-1}$ is the MSB and where a bit value of zero indicates that PMI reporting is not allowed to correspond to any precoder associated with the bit. The number of bits is given by $A_c = N_1 O_1 N_2 O_2$ . Except when the number of layers $v \in \{3, 4\}$ and the number of antenna ports is 16, 24, or 32, bit $a_{N_2 O_2 l + m}$ is associated with all precoders based on the quantity $v_{l,m}$ , $l = 0, \dots, N_1 O_1 - 1$ , $m = 0, \dots, N_2 O_2 - 1$ . When the number of layers $v \in \{3, 4\}$ and the number of antenna ports is 16, 24, or 32, + +- bits $a_{(N_2 O_2 (2l-1) + m) \bmod N_1 O_1 N_2 O_2}$ , $a_{N_2 O_2 (2l) + m}$ , and $a_{N_2 O_2 (2l+1) + m}$ are each associated with all precoders based on the quantity $\tilde{v}_{l,m}$ , $l = 0, \dots, N_1 O_1 / 2 - 1$ , $m = 0, \dots, N_2 O_2 - 1$ ; +- if one or more of the associated bits is zero, then PMI reporting is not allowed to correspond to any precoder based on $\tilde{v}_{l,m}$ . + +For UE configured with higher layer parameter *codebookType* set to 'typeI-SinglePanel', the bitmap parameter *typeI-SinglePanel-ri-Restriction* forms the bit sequence $r_7, \dots, r_1, r_0$ where $r_0$ is the LSB and $r_7$ is the MSB. When $r_i$ is zero, $i \in \{0, 1, \dots, 7\}$ , PMI and RI reporting are not allowed to correspond to any precoder associated with $v = i + 1$ layers. + +For UE configured with higher layer parameter *reportQuantity* set to 'cri-RI-i1-CQI', the bitmap parameter *typeI-SinglePanel-codebookSubsetRestriction-i2* forms the bit sequence $c_{A_c-1}, \dots, c_1, c_0$ , where $c_0$ is the LSB and $c_{A_c-1}$ is the MSB. The bit $c_i$ is associated with precoders corresponding to codebook index $i$ . When $c_i$ is zero, the randomly selected precoder for CQI calculation is not allowed to correspond to any precoder associated with the bit $c_i$ . + +**Table 5.2.2.2.1-2: Supported configurations of $n1$ and $n2$** + +| Number of CSI-RS antenna ports, $P_{\text{CSI-RS}}$ | $n1$ | $n2$ | +|-----------------------------------------------------|------|------| +| | | | + +| | | | +|----|--------|-------| +| 4 | (2,1) | (4,1) | +| | (2,2) | (4,4) | +| 8 | (4,1) | (4,1) | +| | (3,2) | (4,4) | +| 12 | (6,1) | (4,1) | +| | (4,2) | (4,4) | +| 16 | (8,1) | (4,1) | +| | (4,3) | (4,4) | +| 24 | (6,2) | (4,4) | +| | (12,1) | (4,1) | +| 32 | (4,4) | (4,4) | +| | (8,2) | (4,4) | +| | (16,1) | (4,1) | + +**Table 5.2.2.2.1-3: Mapping of $i_{1,3}$ to $k_1$ and $k_2$ for 2-layer CSI reporting** + +| $i_{1,3}$ | $N_1 > N_2 > 1$ | | $N_1 = N_2$ | | $N_1 = 2, N_2 = 1$ | | $N_1 > 2, N_2 = 1$ | | +|-----------|-----------------|-------|-------------|-------|--------------------|-------|--------------------|-------| +| | $k_1$ | $k_2$ | $k_1$ | $k_2$ | $k_1$ | $k_2$ | $k_1$ | $k_2$ | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | $O_1$ | 0 | $O_1$ | 0 | $O_1$ | 0 | $O_1$ | 0 | +| 2 | 0 | $O_2$ | 0 | $O_2$ | | | $2O_1$ | 0 | +| 3 | $2O_1$ | 0 | $O_1$ | $O_2$ | | | $3O_1$ | 0 | + +**Table 5.2.2.2.1-4: Mapping of $i_{1,3}$ to $k_1$ and $k_2$ for 3-layer and 4-layer CSI reporting when $P_{CSI-RS} < 16$** + +| $i_{1,3}$ | $N_1 = 2, N_2 = 1$ | | $N_1 = 4, N_2 = 1$ | | $N_1 = 6, N_2 = 1$ | | $N_1 = 2, N_2 = 2$ | | $N_1 = 3, N_2 = 2$ | | +|-----------|--------------------|-------|--------------------|-------|--------------------|-------|--------------------|-------|--------------------|-------| +| | $k_1$ | $k_2$ | $k_1$ | $k_2$ | $k_1$ | $k_2$ | $k_1$ | $k_2$ | $k_1$ | $k_2$ | +| 0 | $O_1$ | 0 | $O_1$ | 0 | $O_1$ | 0 | $O_1$ | 0 | $O_1$ | 0 | +| 1 | | | $2O_1$ | 0 | $2O_1$ | 0 | 0 | $O_2$ | 0 | $O_2$ | +| 2 | | | $3O_1$ | 0 | $3O_1$ | 0 | $O_1$ | $O_2$ | $O_1$ | $O_2$ | +| 3 | | | | | $4O_1$ | 0 | | | $2O_1$ | 0 | + +**Table 5.2.2.2.1-5: Codebook for 1-layer CSI reporting using antenna ports 3000 to 2999+ $P_{CSI-RS}$** + +| codebookMode = 1 | | | | +|-------------------------|------------------------------------------------------------------------------------------------------------|---------|-----------------------------------| +| | | $i_2$ | | +| $0, 1, …, N_1 O_1 - 1$ | $0, …, N_2 O_2 - 1$ | 0,1,2,3 | $W_{i_{1,1}, i_{1,2}, i_2}^{(1)}$ | +| where | $W_{l,m,n}^{(1)} = \frac{1}{\sqrt{P_{CSI-RS}}} \begin{bmatrix} v_{l,m} \\ \varphi_n v_{l,m} \end{bmatrix}$ | | | + +| codebookMode = 2, N_2 > 1 | | | | | | +|--------------------------------------------------|--|-------|---|----|----| +| | | $i_2$ | | | | +| | | 0 | 1 | 2 | 3 | +| | | $i_2$ | | | | +| | | 4 | 5 | 6 | 7 | +| | | $i_2$ | | | | +| | | 8 | 9 | 10 | 11 | +| | | $i_2$ | | | | +| | | | | | | + +| | | 12 | 13 | 14 | 15 | +|-----------------------------------------------|---|-------------------------------------------------------------------------------------------------------------------------|----------------------------|----------------------------|----------------------------| +| | | $W_{l,m,n}^{(1)} = \frac{1}{\sqrt{P_{\text{CSI-RS}}}} \begin{bmatrix} v_{l,m} \\ \varphi_n v_{l,m} \end{bmatrix}$ where | | | | +| codebookMode = 2, N_2 = 1 | | | | | | +| | | $i_2$ | | | | +| | | 0 | 1 | 2 | 3 | +| | 0 | $W_{2i_{l,1},0,0}^{(1)}$ | $W_{2i_{l,1},0,1}^{(1)}$ | $W_{2i_{l,1},0,2}^{(1)}$ | $W_{2i_{l,1},0,3}^{(1)}$ | +| | | $i_2$ | | | | +| | | 4 | 5 | 6 | 7 | +| | 0 | $W_{2i_{l,1}+1,0,0}^{(1)}$ | $W_{2i_{l,1}+1,0,1}^{(1)}$ | $W_{2i_{l,1}+1,0,2}^{(1)}$ | $W_{2i_{l,1}+1,0,3}^{(1)}$ | +| | | $i_2$ | | | | +| | | 8 | 9 | 10 | 11 | +| | 0 | $W_{2i_{l,1}+2,0,0}^{(1)}$ | $W_{2i_{l,1}+2,0,1}^{(1)}$ | $W_{2i_{l,1}+2,0,2}^{(1)}$ | $W_{2i_{l,1}+2,0,3}^{(1)}$ | +| | | $i_2$ | | | | +| | | 12 | 13 | 14 | 15 | +| | 0 | $W_{2i_{l,1}+3,0,0}^{(1)}$ | $W_{2i_{l,1}+3,0,1}^{(1)}$ | $W_{2i_{l,1}+3,0,2}^{(1)}$ | $W_{2i_{l,1}+3,0,3}^{(1)}$ | +| | | $W_{l,m,n}^{(1)} = \frac{1}{\sqrt{P_{\text{CSI-RS}}}} \begin{bmatrix} v_{l,m} \\ \varphi_n v_{l,m} \end{bmatrix}$ where | | | | + +**Table 5.2.2.2.1-6: Codebook for 2-layer CSI reporting using antenna ports 3000 to 2999+ $P_{\text{CSI-RS}}$** + +| codebookMode = 1 | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|-------------------------------------------------------------------|-------------------------------------------------------------------| +| | | $i_2$ | | +| $0, 1, \dots, N_1 O_1 - 1$ | $0, \dots, N_2 O_2 - 1$ | 0, 1 | $W_{i_{l,1}, i_{l,1}+k_1, i_{l,2}, i_{l,2}+k_2, i_2}^{(2)}$ | +| $W_{l,l',m,m',n}^{(2)} = \frac{1}{\sqrt{2P_{\text{CSI-RS}}}} \begin{bmatrix} v_{l,m} & v_{l',m'} \\ \varphi_n v_{l,m} & -\varphi_n v_{l',m'} \end{bmatrix}$ where and the mapping from $i_{l,3}$ to $k_1$ and $k_2$ is given in Table 5.2.2.2.1-3. | | | | +| codebookMode = 2, N_2 > 1 | | | | +| | | $i_2$ | | +| | $i_{l,2}$ | 0 | 1 | +| $0, \dots, \frac{N_1 O_1}{2} - 1$ | $0, \dots, \frac{N_2 O_2}{2} - 1$ | $W_{2i_{l,1}, 2i_{l,1}+k_1, 2i_{l,2}, 2i_{l,2}+k_2, 0}^{(2)}$ | $W_{2i_{l,1}, 2i_{l,1}+k_1, 2i_{l,2}, 2i_{l,2}+k_2, 1}^{(2)}$ | +| | | $i_2$ | | +| | $i_{l,2}$ | 2 | 3 | +| $0, \dots, \frac{N_1 O_1}{2} - 1$ | $0, \dots, \frac{N_2 O_2}{2} - 1$ | $W_{2i_{l,1}+1, 2i_{l,1}+1+k_1, 2i_{l,2}, 2i_{l,2}+k_2, 0}^{(2)}$ | $W_{2i_{l,1}+1, 2i_{l,1}+1+k_1, 2i_{l,2}, 2i_{l,2}+k_2, 1}^{(2)}$ | +| | | $i_2$ | | +| | $i_{l,2}$ | 4 | 5 | +| $0, \dots, \frac{N_1 O_1}{2} - 1$ | $0, \dots, \frac{N_2 O_2}{2} - 1$ | $W_{2i_{l,1}, 2i_{l,1}+k_1, 2i_{l,2}+1, 2i_{l,2}+1+k_2, 0}^{(2)}$ | $W_{2i_{l,1}, 2i_{l,1}+k_1, 2i_{l,2}+1, 2i_{l,2}+1+k_2, 1}^{(2)}$ | +| | | $i_2$ | | + +| | | 6 | | 7 | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-------------------------------------------------|-------------------------------------------------|-----------------------------------------------------------------------|-----------------------------------------------------------------------| +| $0, \dots, \frac{N_1 O_1}{2} - 1$ | | $0, \dots, \frac{N_2 O_2}{2} - 1$ | | $W_{2i_{1,1}+1, 2i_{1,1}+1+k_1, 2i_{1,2}+1, 2i_{1,2}+1+k_2, 0}^{(2)}$ | $W_{2i_{1,1}+1, 2i_{1,1}+1+k_1, 2i_{1,2}+1, 2i_{1,2}+1+k_2, 1}^{(2)}$ | +| $\text{where } W_{l, l', m, m', n}^{(2)} = \frac{1}{\sqrt{2P_{\text{CSI-RS}}}} \begin{bmatrix} v_{l,m} & v_{l',m'} \\ \varphi_n v_{l,m} & -\varphi_n v_{l',m'} \end{bmatrix}$ and the mapping from $i_{1,3}$ to $k_1$ and $k_2$ is given in Table 5.2.2.2.1-3. | | | | | | +| codebookMode = 2, N_2 = 1 | | | | | | +| | $i_{1,2}$ | $i_2$ | | | | +| | | 0 | 1 | 2 | 3 | +| $0, \dots, \frac{N_1 O_1}{2} - 1$ | 0 | $W_{2i_{1,1}, 2i_{1,1}+k_1, 0, 0, 0}^{(2)}$ | $W_{2i_{1,1}, 2i_{1,1}+k_1, 0, 0, 1}^{(2)}$ | $W_{2i_{1,1}+1, 2i_{1,1}+1+k_1, 0, 0, 0}^{(2)}$ | $W_{2i_{1,1}+1, 2i_{1,1}+1+k_1, 0, 0, 1}^{(2)}$ | +| | $i_{1,2}$ | $i_2$ | | | | +| | | 4 | 5 | 6 | 7 | +| $0, \dots, \frac{N_1 O_1}{2} - 1$ | 0 | $W_{2i_{1,1}+2, 2i_{1,1}+2+k_1, 0, 0, 0}^{(2)}$ | $W_{2i_{1,1}+2, 2i_{1,1}+2+k_1, 0, 0, 1}^{(2)}$ | $W_{2i_{1,1}+3, 2i_{1,1}+3+k_1, 0, 0, 0}^{(2)}$ | $W_{2i_{1,1}+3, 2i_{1,1}+3+k_1, 0, 0, 1}^{(2)}$ | +| $\text{where } W_{l, l', m, m', n}^{(2)} = \frac{1}{\sqrt{2P_{\text{CSI-RS}}}} \begin{bmatrix} v_{l,m} & v_{l',m'} \\ \varphi_n v_{l,m} & -\varphi_n v_{l',m'} \end{bmatrix}$ and the mapping from $i_{1,3}$ to $k_1$ is given in Table 5.2.2.2.1-3. | | | | | | + +**Table 5.2.2.2.1-7: Codebook for 3-layer CSI reporting using antenna ports 3000 to 2999+ $P_{\text{CSI-RS}}$** + +| codebookMode = 1-2, P_{\text{CSI-RS}} < 16 | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|------------|-------------------------------------------------------------|--------------------------------------------| +| | $i_{1,2}$ | $i_2$ | | | +| $0, \dots, N_1 O_1 - 1$ | $0, 1, \dots, N_2 O_2 - 1$ | 0, 1 | $W_{i_{1,1}, i_{1,1}+k_1, i_{1,2}, i_{1,2}+k_2, i_2}^{(3)}$ | | +| $\text{where } W_{l, l', m, m', n}^{(3)} = \frac{1}{\sqrt{3P_{\text{CSI-RS}}}} \begin{bmatrix} v_{l,m} & v_{l',m'} & v_{l,m} \\ \varphi_n v_{l,m} & -\varphi_n v_{l',m'} & -\varphi_n v_{l,m} \end{bmatrix}$ and the mapping from $i_{1,3}$ to $k_1$ and $k_2$ is given in Table 5.2.2.2.1-4. | | | | | +| codebookMode = 1-2, P_{\text{CSI-RS}} \geq 16 | | | | | +| | $i_{1,2}$ | $i_{1,3}$ | $i_2$ | | +| $0, \dots, \frac{N_1 O_1}{2} - 1$ | $0, \dots, N_2 O_2 - 1$ | 0, 1, 2, 3 | 0, 1 | $W_{i_{1,1}, i_{1,2}, i_{1,3}, i_2}^{(3)}$ | +| $\text{where } W_{l, m, p, n}^{(3)} = \frac{1}{\sqrt{3P_{\text{CSI-RS}}}} \begin{bmatrix} \tilde{v}_{l,m} & v_{l,m} & v_{l,m} \\ \theta_p \tilde{v}_{l,m} & -\theta_p v_{l,m} & \theta_p v_{l,m} \\ \varphi_n \tilde{v}_{l,m} & \varphi_n v_{l,m} & -\varphi_n v_{l,m} \\ \varphi_n \theta_p \tilde{v}_{l,m} & -\varphi_n \theta_p v_{l,m} & -\varphi_n \theta_p v_{l,m} \end{bmatrix}$ | | | | | + +**Table 5.2.2.2.1-8: Codebook for 4-layer CSI reporting using antenna ports 3000 to 2999+ $P_{\text{CSI-RS}}$** + +| codebookMode = 1-2, P_{\text{CSI-RS}} < 16 | | | | +|-------------------------------------------------------------------|----------------------------|-------|-------------------------------------------------------------| +| | $i_{1,2}$ | $i_2$ | | +| $0, \dots, N_1 O_1 - 1$ | $0, 1, \dots, N_2 O_2 - 1$ | 0, 1 | $W_{i_{1,1}, i_{1,1}+k_1, i_{1,2}, i_{1,2}+k_2, i_2}^{(4)}$ | + +$$\text{where } W_{l,l',m,m',n}^{(4)} = \frac{1}{\sqrt{4P_{\text{CSI-RS}}}} \begin{bmatrix} v_{l,m} & v_{l',m'} & v_{l,m} & v_{l',m'} \\ \varphi_n v_{l,m} & \varphi_n v_{l',m'} & -\varphi_n v_{l,m} & -\varphi_n v_{l',m'} \end{bmatrix}.$$ + +and the mapping from $i_{1,3}$ to $k_1$ and $k_2$ is given in Table 5.2.2.2.1-4. + +| codebookMode = 1-2, P_{\text{CSI-RS}} \geq 16 | | | | | +|-------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------|--------------------------------------------| +| | | $i_{1,2}$ | $i_{1,3}$ | $i_2$ | +| $0, \dots, \frac{N_1 O_1}{2} - 1$ | $0, \dots, N_2 O_2 - 1$ | $0, 1, 2, 3$ | $0, 1$ | $W_{i_{1,1}, i_{1,2}, i_{1,3}, i_2}^{(4)}$ | +| where | $W_{l,m,p,n}^{(4)} = \frac{1}{\sqrt{4P_{\text{CSI-RS}}}} \begin{bmatrix} \tilde{v}_{l,m} & v_{l,m} & v_{l,m} & v_{l,m} \\ \theta_p \tilde{v}_{l,m} & -\theta_p v_{l,m} & \theta_p v_{l,m} & -\theta_p v_{l,m} \\ \varphi_n \tilde{v}_{l,m} & \varphi_n v_{l,m} & -\varphi_n v_{l,m} & -\varphi_n v_{l,m} \\ \varphi_n \theta_p \tilde{v}_{l,m} & -\varphi_n \theta_p v_{l,m} & -\varphi_n \theta_p v_{l,m} & \varphi_n \theta_p v_{l,m} \end{bmatrix}.$ | | | | + +**Table 5.2.2.2.1-9: Codebook for 5-layer CSI reporting using antenna ports 3000 to 2999+ $P_{\text{CSI-RS}}$** + +| codebookMode = 1-2 | | | | | +|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------|-----------------------------------------------------------------------------------------| +| | | $i_{1,2}$ | $i_2$ | | +| $N_2 > 1$ | $0, \dots, N_1 O_1 - 1$ | $0, \dots, N_2 O_2 - 1$ | $0, 1$ | $W_{i_{1,1}, i_{1,1} + O_1, i_{1,1} + O_1, i_{1,2}, i_{1,2}, i_{1,2} + O_2, i_2}^{(5)}$ | +| $N_1 > 2, N_2 = 1$ | $0, \dots, N_1 O_1 - 1$ | 0 | $0, 1$ | $W_{i_{1,1}, i_{1,1} + O_1, i_{1,1} + 2O_1, 0, 0, 0, i_2}^{(5)}$ | +| where | $W_{l,l',l'',m,m',m'',n}^{(5)} = \frac{1}{\sqrt{5P_{\text{CSI-RS}}}} \begin{bmatrix} v_{l,m} & v_{l,m} & v_{l',m'} & v_{l',m'} & v_{l'',m''} \\ \varphi_n v_{l,m} & -\varphi_n v_{l,m} & v_{l',m'} & -v_{l',m'} & v_{l'',m''} \end{bmatrix}.$ | | | | + +**Table 5.2.2.2.1-10: Codebook for 6-layer CSI reporting using antenna ports 3000 to 2999+ $P_{\text{CSI-RS}}$** + +| codebookMode = 1-2 | | | | | +|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|--------|-----------------------------------------------------------------------------------------| +| | | $i_{1,2}$ | $i_2$ | | +| $N_2 > 1$ | $0, \dots, N_1 O_1 - 1$ | $0, \dots, N_2 O_2 - 1$ | $0, 1$ | $W_{i_{1,1}, i_{1,1} + O_1, i_{1,1} + O_1, i_{1,2}, i_{1,2}, i_{1,2} + O_2, i_2}^{(6)}$ | +| $N_1 > 2, N_2 = 1$ | $0, \dots, N_1 O_1 - 1$ | 0 | $0, 1$ | $W_{i_{1,1}, i_{1,1} + O_1, i_{1,1} + 2O_1, 0, 0, 0, i_2}^{(6)}$ | +| where | $W_{l,l',l'',m,m',m'',n}^{(6)} = \frac{1}{\sqrt{6P_{\text{CSI-RS}}}} \begin{bmatrix} v_{l,m} & v_{l,m} & v_{l',m'} & v_{l',m'} & v_{l'',m''} & v_{l'',m''} \\ \varphi_n v_{l,m} & -\varphi_n v_{l,m} & \varphi_n v_{l',m'} & -\varphi_n v_{l',m'} & v_{l'',m''} & -v_{l'',m''} \end{bmatrix}.$ | | | | + +**Table 5.2.2.2.1-11: Codebook for 7-layer CSI reporting using antenna ports 3000 to 2999+ $P_{\text{CSI-RS}}$** + +| codebookMode = 1-2 | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|-----------------------------------|-------|--------------------------------------------------------------------------------------------------------| +| | | $i_{1,2}$ | $i_2$ | | +| $N_1 = 4, N_2 = 1$ | $0, \dots, \frac{N_1 O_1}{2} - 1$ | 0 | 0,1 | $W_{i_1, i_1, i_1, i_1, i_1, i_1, i_1}^{(7)} + O_1 i_1 + 2O_1 i_1 + 3O_1 0, 0, 0, 0, i_2$ | +| $N_1 > 4, N_2 = 1$ | $0, \dots, N_1 O_1 - 1$ | 0 | 0,1 | $W_{i_1, i_1, i_1, i_1, i_1, i_1, i_1}^{(7)} + O_1 i_1 + 2O_1 i_1 + 3O_1 0, 0, 0, 0, i_2$ | +| $N_1 = 2, N_2 = 2$ | $0, \dots, N_1 O_1 - 1$ | $0, \dots, N_2 O_2 - 1$ | 0,1 | $W_{i_1, i_1, i_1, i_1, i_1, i_1, i_1}^{(7)} + O_1 i_1 + 2O_1 i_1 + 3O_1 i_2, i_2 + O_2 i_2 + O_2 i_2$ | +| $N_1 > 2, N_2 = 2$ | $0, \dots, N_1 O_1 - 1$ | $0, \dots, \frac{N_2 O_2}{2} - 1$ | 0,1 | $W_{i_1, i_1, i_1, i_1, i_1, i_1, i_1}^{(7)} + O_1 i_1 + 2O_1 i_1 + 3O_1 i_2, i_2 + O_2 i_2 + O_2 i_2$ | +| $N_1 > 2, N_2 > 2$ | $0, \dots, N_1 O_1 - 1$ | $0, \dots, N_2 O_2 - 1$ | 0,1 | $W_{i_1, i_1, i_1, i_1, i_1, i_1, i_1}^{(7)} + O_1 i_1 + 2O_1 i_1 + 3O_1 i_2, i_2 + O_2 i_2 + O_2 i_2$ | +| $\text{where } W_{l, l', l'', m, m', m'', n}^{(7)} = \frac{1}{\sqrt{7 P_{\text{CSI-RS}}}} \begin{bmatrix} v_{l,m} & v_{l,m} & v_{l',m'} & v_{l',m'} & v_{l'',m''} & v_{l'',m''} & v_{l'',m''} \\ \varphi_n v_{l,m} & -\varphi_n v_{l,m} & \varphi_n v_{l',m'} & -\varphi_n v_{l',m'} & \varphi_n v_{l'',m''} & -\varphi_n v_{l'',m''} & \varphi_n v_{l'',m''} \end{bmatrix}$ | | | | | + +**Table 5.2.2.2.1-12: Codebook for 8-layer CSI reporting using antenna ports 3000 to 2999+ $P_{\text{CSI-RS}}$** + +| codebookMode = 1-2 | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|-----------------------------------|-------|-------------------------------------------------------------------------------------------------------------| +| | | $i_{1,2}$ | $i_2$ | | +| $N_1 = 4, N_2 = 1$ | $0, \dots, \frac{N_1 O_1}{2} - 1$ | 0 | 0,1 | $W_{i_1, i_1, i_1, i_1, i_1, i_1, i_1, i_1}^{(8)} + O_1 i_1 + 2O_1 i_1 + 3O_1 0, 0, 0, 0, i_2$ | +| $N_1 > 4, N_2 = 1$ | $0, \dots, N_1 O_1 - 1$ | 0 | 0,1 | $W_{i_1, i_1, i_1, i_1, i_1, i_1, i_1, i_1}^{(8)} + O_1 i_1 + 2O_1 i_1 + 3O_1 0, 0, 0, 0, i_2$ | +| $N_1 = 2, N_2 = 2$ | $0, \dots, N_1 O_1 - 1$ | $0, \dots, N_2 O_2 - 1$ | 0,1 | $W_{i_1, i_1, i_1, i_1, i_1, i_1, i_1, i_1}^{(8)} + O_1 i_1 + 2O_1 i_1 + 3O_1 i_2, i_2 + O_2 i_2 + O_2 i_2$ | +| $N_1 > 2, N_2 = 2$ | $0, \dots, N_1 O_1 - 1$ | $0, \dots, \frac{N_2 O_2}{2} - 1$ | 0,1 | $W_{i_1, i_1, i_1, i_1, i_1, i_1, i_1, i_1}^{(8)} + O_1 i_1 + 2O_1 i_1 + 3O_1 i_2, i_2 + O_2 i_2 + O_2 i_2$ | +| $N_1 > 2, N_2 > 2$ | $0, \dots, N_1 O_1 - 1$ | $0, \dots, N_2 O_2 - 1$ | 0,1 | $W_{i_1, i_1, i_1, i_1, i_1, i_1, i_1, i_1}^{(8)} + O_1 i_1 + 2O_1 i_1 + 3O_1 i_2, i_2 + O_2 i_2 + O_2 i_2$ | +| $\text{where } W_{l, l', l'', m, m', m'', n}^{(8)} = \frac{1}{\sqrt{8 P_{\text{CSI-RS}}}} \begin{bmatrix} v_{l,m} & v_{l,m} & v_{l',m'} & v_{l',m'} & v_{l'',m''} & v_{l'',m''} & v_{l'',m''} & v_{l'',m''} \\ \varphi_n v_{l,m} & -\varphi_n v_{l,m} & \varphi_n v_{l',m'} & -\varphi_n v_{l',m'} & \varphi_n v_{l'',m''} & -\varphi_n v_{l'',m''} & \varphi_n v_{l'',m''} & -\varphi_n v_{l'',m''} \end{bmatrix}$ | | | | | + +##### **5.2.2.2.2 Type I Multi-Panel Codebook** + +For 8 antenna ports {3000, 3001, ..., 3007}, 16 antenna ports {3000, 3001, ..., 3015}, and 32 antenna ports {3000, 3001, ..., 3031}, and the UE configured with higher layer parameter *codebookType* set to 'typeI-MultiPanel', + +- The values of $N_g$ , and are configured with the higher layer parameters *ng-n1-n2*. The supported configurations of $(N_g, N_1, N_2)$ for a given number of CSI-RS ports and the corresponding values of $(O_1, O_2)$ are given in Table 5.2.2.2.2-1. The number of CSI-RS ports, $P_{\text{CSI-RS}}$ , is $2^{N_g} N_1 N_2$ . +- When $N_g = 2$ , *codebookMode* shall be set to either '1' or '2'. When $N_g = 4$ , *codebookMode* shall be set to '1'. + +The bitmap parameter *ng-n1-n2* forms the bit sequence $a_{A_c-1}, \dots, a_1, a_0$ where $a_0$ is the LSB and $a_{A_c-1}$ is the MSB and where a bit value of zero indicates that PMI reporting is not allowed to correspond to any precoder associated with the bit. The number of bits is given by $A_c = N_1 O_1 N_2 O_2$ . Bit $a_{N_2 O_2 + m}$ is associated with all precoders based on the quantity $v_{l,m}$ , $l = 0, \dots, N_1 O_1 - 1$ , $m = 0, \dots, N_2 O_2 - 1$ , as defined below. The bitmap parameter *ri-Restriction* forms the bit sequence $r_3, \dots, r_1, r_0$ where $r_0$ is the LSB and $r_3$ is the MSB. When $r_i$ is zero, $i \in \{0, 1, \dots, 3\}$ , PMI and RI reporting are not allowed to correspond to any precoder associated with $v = i + 1$ layers. + +**Table 5.2.2.2.2-1: Supported configurations of $(N_g, N_1, N_2)$ and** + +| Number of CSI-RS antenna ports, $P_{\text{CSI-RS}}$ | $(N_g, N_1, N_2)$ | | +|-----------------------------------------------------|-------------------|-------| +| 8 | (2,2,1) | (4,1) | +| 16 | (2,4,1) | (4,1) | +| | (4,2,1) | (4,1) | +| | (2,2,2) | (4,4) | +| 32 | (2,8,1) | (4,1) | +| | (4,4,1) | (4,1) | +| | (2,4,2) | (4,4) | +| | (4,2,2) | (4,4) | + +Each PMI value corresponds to the codebook indices $i_1$ and $i_2$ , where $i_1$ is the vector + +$$i_1 = \begin{cases} [i_{1,1} \ i_{1,2} \ i_{1,4}] & v=1 \\ [i_{1,1} \ i_{1,2} \ i_{1,3} \ i_{1,4}] & v \in \{2,3,4\} \end{cases}$$ + +and $v$ is the associated RI value. When *codebookMode* is set to '1', $i_{1,4}$ is + +$$i_{1,4} = \begin{cases} i_{1,4,1} & N_g = 2 \\ [i_{1,4,1} \ i_{1,4,2} \ i_{1,4,3}] & N_g = 4 \end{cases}$$ + +When *codebookMode* is set to '2', $i_{1,4}$ and $i_2$ are + +$$\begin{aligned} i_{1,4} &= [i_{1,4,1} \ i_{1,4,2}] \\ i_2 &= [i_{2,0} \ i_{2,1} \ i_{2,2}] \end{aligned}$$ + +The mapping from $i_{1,3}$ to $k_1$ and $k_2$ for 2-layer reporting is given in Table 5.2.2.2.1-3. The mapping from $i_{1,3}$ to $k_1$ and $k_2$ for 3-layer and 4-layer reporting is given in Table 5.2.2.2.2-2. + +- UE shall only use and shall not report if the value of $N_2$ is 1. + +**Table 5.2.2.2.2-2: Mapping of $i_{1,3}$ to $k_1$ and $k_2$ for 3-layer and 4-layer CSI reporting** + +| $i_{1,3}$ | $N_1 = 2, N_2 = 1$ | | $N_1 = 4, N_2 = 1$ | | $N_1 = 8, N_2 = 1$ | | $N_1 = 2, N_2 = 2$ | | $N_1 = 4, N_2 = 2$ | | +|-----------|--------------------|-------|--------------------|-------|--------------------|-------|--------------------|-------|--------------------|-------| +| | $k_1$ | $k_2$ | $k_1$ | $k_2$ | $k_1$ | $k_2$ | $k_1$ | $k_2$ | $k_1$ | $k_2$ | +| 0 | $O_1$ | 0 | $O_1$ | 0 | $O_1$ | 0 | $O_1$ | 0 | $O_1$ | 0 | +| 1 | | | $2O_1$ | 0 | $2O_1$ | 0 | 0 | $O_2$ | 0 | $O_2$ | +| 2 | | | $3O_1$ | 0 | $3O_1$ | 0 | $O_1$ | $O_2$ | $O_1$ | $O_2$ | +| 3 | | | | | $4O_1$ | 0 | | | $2O_1$ | 0 | + +Several quantities are used to define the codebook elements. The quantities $\varphi_n$ , $a_p$ , $b_n$ , $u_m$ , and are given by + +$$\begin{aligned} + \varphi_n &= e^{j\pi n/2} \\ + a_p &= e^{j\pi/4} e^{j\pi p/2} \\ + b_n &= e^{-j\pi/4} e^{j\pi n/2} \\ + u_m &= \begin{cases} \begin{bmatrix} 1 & e^{j\frac{2\pi m}{O_2 N_2}} & \dots & e^{j\frac{2\pi m(N_2-1)}{O_2 N_2}} \end{bmatrix} & N_2 > 1 \\ 1 & N_2 = 1 \end{cases} \\ + v_{l,m} &= \begin{bmatrix} u_m & e^{j\frac{2\pi l}{O_1 N_1}} u_m & \dots & e^{j\frac{2\pi l(N_1-1)}{O_1 N_1}} u_m \end{bmatrix}^T + \end{aligned}$$ + +Furthermore, the quantities $W_{l,m,p,n}^{1,N_g,1}$ and $W_{l,m,p,n}^{2,N_g,1}$ ( $N_g \in \{2,4\}$ ) are given by + +$$\begin{aligned} + W_{l,m,p,n}^{1,2,1} &= \frac{1}{\sqrt{P_{\text{CSI-RS}}}} \begin{bmatrix} v_{l,m} \\ \varphi_n v_{l,m} \\ \varphi_{p_1} v_{l,m} \\ \varphi_n \varphi_{p_1} v_{l,m} \end{bmatrix} & W_{l,m,p,n}^{2,2,1} &= \frac{1}{\sqrt{P_{\text{CSI-RS}}}} \begin{bmatrix} v_{l,m} \\ -\varphi_n v_{l,m} \\ \varphi_{p_1} v_{l,m} \\ -\varphi_n \varphi_{p_1} v_{l,m} \end{bmatrix} \\ + W_{l,m,p,n}^{1,4,1} &= \frac{1}{\sqrt{P_{\text{CSI-RS}}}} \begin{bmatrix} v_{l,m} \\ \varphi_n v_{l,m} \\ \varphi_{p_1} v_{l,m} \\ \varphi_n \varphi_{p_1} v_{l,m} \\ \varphi_{p_2} v_{l,m} \\ \varphi_n \varphi_{p_2} v_{l,m} \\ \varphi_{p_3} v_{l,m} \\ \varphi_n \varphi_{p_3} v_{l,m} \end{bmatrix} & W_{l,m,p,n}^{2,4,1} &= \frac{1}{\sqrt{P_{\text{CSI-RS}}}} \begin{bmatrix} v_{l,m} \\ -\varphi_n v_{l,m} \\ \varphi_{p_1} v_{l,m} \\ -\varphi_n \varphi_{p_1} v_{l,m} \\ \varphi_{p_2} v_{l,m} \\ -\varphi_n \varphi_{p_2} v_{l,m} \\ \varphi_{p_3} v_{l,m} \\ -\varphi_n \varphi_{p_3} v_{l,m} \end{bmatrix} + \end{aligned}$$ + +where + +$$p = \begin{cases} p_1 & N_g = 2 \\ [p_1 \ p_2 \ p_3] & N_g = 4 \end{cases}$$ + +and the quantities $W_{l,m,p,n}^{1,N_g,2}$ and $W_{l,m,p,n}^{2,N_g,2}$ ( $N_g = 2$ ) are given by + +$$\begin{aligned} + W_{l,m,p,n}^{1,2,2} &= \frac{1}{\sqrt{P_{\text{CSI-RS}}}} \begin{bmatrix} v_{l,m} \\ \varphi_{n_0} v_{l,m} \\ a_{p_1} b_{n_1} v_{l,m} \\ a_{p_2} b_{n_2} v_{l,m} \end{bmatrix} & W_{l,m,p,n}^{2,2,2} &= \frac{1}{\sqrt{P_{\text{CSI-RS}}}} \begin{bmatrix} v_{l,m} \\ -\varphi_{n_0} v_{l,m} \\ a_{p_1} b_{n_1} v_{l,m} \\ -a_{p_2} b_{n_2} v_{l,m} \end{bmatrix} + \end{aligned}$$ + +where + +$$\begin{aligned} + p &= [p_1 \ p_2] \\ + n &= [n_0 \ n_1 \ n_2] + \end{aligned}$$ + +The codebooks for 1-4 layers are given respectively in Tables 5.2.2.2.2-3, 5.2.2.2.2-4, 5.2.2.2.2-5, and 5.2.2.2.2-6. + +**Table 5.2.2.2.2-3: Codebook for 1-layer CSI reporting using antenna ports 3000 to 2999+ $P_{CSI-RS}$** + +| codebookMode = 1, $N_g \in \{2, 4\}$ | | | | | +|---------------------------------------------------|-------------------------|------------------------------------|---------|--------------------------------------------| +| | $i_{1,2}$ | $i_{1,4,q}, q = 1, \dots, N_g - 1$ | $i_2$ | | +| $0, \dots, N_1 O_1 - 1$ | $0, \dots, N_2 O_2 - 1$ | 0,1,2,3 | 0,1,2,3 | $W_{i_{1,1}, i_{1,2}, i_{1,4}, i_2}^{(1)}$ | +| where $W_{l,m,p,n}^{(1)} = W_{l,m,p,n}^{1,N_g,1}$ | | | | | + +| codebookMode = 2, $N_g = 2$ | | | | | | +|---------------------------------------------------|-------------------------|-----------------------|-----------|---------------------|--------------------------------------------| +| | $i_{1,2}$ | $i_{1,4,q}, q = 1, 2$ | $i_{2,0}$ | $i_{2,q}, q = 1, 2$ | | +| $0, \dots, N_1 O_1 - 1$ | $0, \dots, N_2 O_2 - 1$ | 0,1,2,3 | 0,1,2,3 | 0,1 | $W_{i_{1,1}, i_{1,2}, i_{1,4}, i_2}^{(1)}$ | +| where $W_{l,m,p,n}^{(1)} = W_{l,m,p,n}^{1,N_g,2}$ | | | | | | + +**Table 5.2.2.2.2-4: Codebook for 2-layer CSI reporting using antenna ports 3000 to 2999+ $P_{CSI-RS}$** + +| codebookMode = 1, $N_g \in \{2, 4\}$ | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------------|-------|--------------------------------------------| +| | $i_{1,2}$ | $i_{1,4,q}, q = 1, \dots, N_g - 1$ | $i_2$ | | +| $0, \dots, N_1 O_1 - 1$ | $0, \dots, N_2 O_2 - 1$ | 0,1,2,3 | 0,1 | $W_{i_{1,1}, i_{1,2}, i_{1,4}, i_2}^{(2)}$ | +| where $W_{l,l',m,m',p,n}^{(2)} = \frac{1}{\sqrt{2}} \begin{bmatrix} W_{l,m,p,n}^{1,N_g,1} & W_{l',m',p,n}^{2,N_g,1} \\ W_{l',m',p,n}^{2,N_g,1} & W_{l,m,p,n}^{1,N_g,1} \end{bmatrix}$
and the mapping from $i_{1,3}$ to $k_1$ and $k_2$ is given in Table 5.2.2.2.1-3. | | | | | + +| codebookMode = 2, $N_g = 2$ | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------|------------------------|--------------------------------------------| +| | $i_{1,2}$ | $i_{1,4,q}, q = 1, 2$ | $i_{2,q}, q = 0, 1, 2$ | | +| $0, \dots, N_1 O_1 - 1$ | $0, \dots, N_2 O_2 - 1$ | 0,1,2,3 | 0,1 | $W_{i_{1,1}, i_{1,2}, i_{1,4}, i_2}^{(2)}$ | +| where $W_{l,l',m,m',p,n}^{(2)} = \frac{1}{\sqrt{2}} \begin{bmatrix} W_{l,m,p,n}^{1,N_g,2} & W_{l',m',p,n}^{2,N_g,2} \\ W_{l',m',p,n}^{2,N_g,2} & W_{l,m,p,n}^{1,N_g,2} \end{bmatrix}$
and the mapping from $i_{1,3}$ to $k_1$ and $k_2$ is given in Table 5.2.2.2.1-3. | | | | | + +**Table 5.2.2.2.2-5: Codebook for 3-layer CSI reporting using antenna ports 3000 to 2999+ $P_{CSI-RS}$** + +| codebookMode = 1, $N_g \in \{2, 4\}$ | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------------|-------|--------------------------------------------| +| | $i_{1,2}$ | $i_{1,4,q}, q = 1, \dots, N_g - 1$ | $i_2$ | | +| $0, \dots, N_1 O_1 - 1$ | $0, \dots, N_2 O_2 - 1$ | 0,1,2,3 | 0,1 | $W_{i_{1,1}, i_{1,2}, i_{1,4}, i_2}^{(3)}$ | +| where $W_{l,l',m,m',p,n}^{(3)} = \frac{1}{\sqrt{3}} \begin{bmatrix} W_{l,m,p,n}^{1,N_g,1} & W_{l',m',p,n}^{1,N_g,1} & W_{l',m',p,n}^{2,N_g,1} \\ W_{l',m',p,n}^{1,N_g,1} & W_{l,m,p,n}^{1,N_g,1} & W_{l',m',p,n}^{2,N_g,1} \\ W_{l',m',p,n}^{2,N_g,1} & W_{l',m',p,n}^{2,N_g,1} & W_{l,m,p,n}^{1,N_g,1} \end{bmatrix}$
and the mapping from $i_{1,3}$ to $k_1$ and $k_2$ is given in Table 5.2.2.2.2-2. | | | | | + +| codebookMode = 2, N_g = 2 | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------|------------------------|-------------------------------------------------------------------| +| | $i_{1,2}$ | $i_{1,4,q}, q = 1, 2$ | $i_{2,q}, q = 0, 1, 2$ | | +| $0, \dots, N_1 O_1 - 1$ | $0, \dots, N_2 O_2 - 1$ | 0,1,2,3 | 0,1 | $W_{i_{1,1}, i_{1,3}}^{(3)} + k_1 i_{1,2} + k_2 i_{1,4, i_{2,q}}$ | +| $\text{where } W_{l, l', m, m', p, n}^{(3)} = \frac{1}{\sqrt{3}} \begin{bmatrix} W_{l, m, p, n}^{1, N_g, 2} & W_{l', m', p, n}^{1, N_g, 2} & W_{l, m, p, n}^{2, N_g, 2} \end{bmatrix}$

and the mapping from i_{1,3} to k_1 and k_2 is given in Table 5.2.2.2.2-2.

| | | | | + +**Table 5.2.2.2.2-6: Codebook for 4-layer CSI reporting using antenna ports 3000 to 2999+ $P_{CSI-RS}$** + +| codebookMode = 1, N_g \in \{2, 4\} | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------------|-------|-------------------------------------------------------------------| +| | $i_{1,2}$ | $i_{1,4,q}, q = 1, \dots, N_g - 1$ | $i_2$ | | +| $0, \dots, N_1 O_1 - 1$ | $0, \dots, N_2 O_2 - 1$ | 0,1,2,3 | 0,1 | $W_{i_{1,1}, i_{1,3}}^{(4)} + k_1 i_{1,2} + k_2 i_{1,4, i_{2,q}}$ | +| $\text{where } W_{l, l', m, m', p, n}^{(4)} = \frac{1}{\sqrt{4}} \begin{bmatrix} W_{l, m, p, n}^{1, N_g, 1} & W_{l', m', p, n}^{1, N_g, 1} & W_{l, m, p, n}^{2, N_g, 1} & W_{l', m', p, n}^{2, N_g, 1} \end{bmatrix}$

and the mapping from i_{1,3} to k_1 and k_2 is given in Table 5.2.2.2.2-2.

| | | | | + +| codebookMode = 2, N_g = 2 | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------|------------------------|-------------------------------------------------------------------| +| | $i_{1,2}$ | $i_{1,4,q}, q = 1, 2$ | $i_{2,q}, q = 0, 1, 2$ | | +| $0, \dots, N_1 O_1 - 1$ | $0, \dots, N_2 O_2 - 1$ | 0,1,2,3 | 0,1 | $W_{i_{1,1}, i_{1,3}}^{(4)} + k_1 i_{1,2} + k_2 i_{1,4, i_{2,q}}$ | +| $\text{where } W_{l, l', m, m', p, n}^{(4)} = \frac{1}{\sqrt{4}} \begin{bmatrix} W_{l, m, p, n}^{1, N_g, 2} & W_{l', m', p, n}^{1, N_g, 2} & W_{l, m, p, n}^{2, N_g, 2} & W_{l', m', p, n}^{2, N_g, 2} \end{bmatrix}$

and the mapping from i_{1,3} to k_1 and k_2 is given in Table 5.2.2.2.2-2.

| | | | | + +##### 5.2.2.2.3 Type II Codebook + +For 4 antenna ports {3000, 3001, ..., 3003}, 8 antenna ports {3000, 3001, ..., 3007}, 12 antenna ports {3000, 3001, ..., 3011}, 16 antenna ports {3000, 3001, ..., 3015}, 24 antenna ports {3000, 3001, ..., 3023}, and 32 antenna ports {3000, 3001, ..., 3031}, and the UE configured with higher layer parameter *codebookType* set to 'typeII' + +- The values of $O_1$ and $O_2$ are configured with the higher layer parameter *n1-n2-codebookSubsetRestriction*. The supported configurations of $O_1$ and $O_2$ for a given number of CSI-RS ports and the corresponding values of $(O_1, O_2)$ are given in Table 5.2.2.2.1-2. The number of CSI-RS ports, $P_{CSI-RS}$ , is $\nu$ . +- The value of $L$ is configured with the higher layer parameter *numberOfBeams*, where $L = 2$ when $P_{CSI-RS} = 4$ and $L \in \{2, 3, 4\}$ when $P_{CSI-RS} > 4$ . +- The value of $N_{PSK}$ is configured with the higher layer parameter *phaseAlphabetSize*, where $N_{PSK} \in \{4, 8\}$ . +- The UE is configured with the higher layer parameter *subbandAmplitude* set to 'true' or 'false'. +- The UE shall not report RI > 2. + +When $\nu$ is the associated RI value, each PMI value corresponds to the codebook indices $i_1$ and $i_2$ where + +$$i_1 = \begin{cases} [i_{1,1} \ i_{1,2} \ i_{1,3,1} \ i_{1,4,1}] & v=1 \\ [i_{1,1} \ i_{1,2} \ i_{1,3,1} \ i_{1,4,1} \ i_{1,3,2} \ i_{1,4,2}] & v=2 \end{cases}$$ + +$$i_2 = \begin{cases} [i_{2,1,1}] & \text{subbandAmplitude} = \text{'false'}, v=1 \\ [i_{2,1,1} \ i_{2,1,2}] & \text{subbandAmplitude} = \text{'false'}, v=2 \\ [i_{2,1,1} \ i_{2,2,1}] & \text{subbandAmplitude} = \text{'true'}, v=1 \\ [i_{2,1,1} \ i_{2,2,1} \ i_{2,1,2} \ i_{2,2,2}] & \text{subbandAmplitude} = \text{'true'}, v=2 \end{cases}$$ + +The $L$ vectors combined by the codebook are identified by the indices $i_{1,1}$ and $i_{1,2}$ , where + +$$i_{1,1} = [q_1 \ q_2]$$ + +$$q_1 \in \{0, 1, \dots, O_1 - 1\}$$ + +$$q_2 \in \{0, 1, \dots, O_2 - 1\}$$ + +Let + +$$n_1 = [n_1^{(0)}, \dots, n_1^{(L-1)}]$$ + +$$n_2 = [n_2^{(0)}, \dots, n_2^{(L-1)}]$$ + +$$n_1^{(i)} \in \{0, 1, \dots, N_1 - 1\}$$ + +$$n_2^{(i)} \in \{0, 1, \dots, N_2 - 1\}$$ + +and + +$$C(x, y) = \begin{cases} \begin{pmatrix} x \\ y \end{pmatrix} & x \geq y \\ 0 & x < y \end{cases}$$ + +where the values of $C(x, y)$ are given in Table 5.2.2.2.3-1. + +Then the elements of $n_1$ and $n_2$ are found from $i_{1,2}$ using the algorithm: + +$$s_{-1} = 0$$ + +$$\text{for } i = 0, \dots, L - 1$$ + +$$\text{Find the largest } x^* \in \{L - 1 - i, \dots, N_1 N_2 - 1 - i\} \text{ in Table 5.2.2.2.3-1 such that } i_{1,2} - s_{i-1} \geq C(x^*, L - i)$$ + +$$e_i = C(x^*, L - i)$$ + +$$s_i = s_{i-1} + e_i$$ + +$$n^{(i)} = N_1 N_2 - 1 - x^*$$ + +$$n_1^{(i)} = n^{(i)} \bmod N_1$$ + +$$n_2^{(i)} = \frac{(n^{(i)} - n_1^{(i)})}{N_1}$$ + +When $n_1$ and $n_2$ are known, $i_{1,2}$ is found using: + +$$n^{(i)} = N_1 n_2^{(i)} + n_1^{(i)} \text{ where the indices } i = 0, 1, \dots, L - 1 \text{ are assigned such that } n^{(i)} \text{ increases as } i \text{ increases}$$ + +$$i_{1,2} = \sum_{i=0}^{L-1} C(N_1 N_2 - 1 - n^{(i)}, L - i), \text{ where } C(x, y) \text{ is given in Table 5.2.2.2.3-1.}$$ + +- If $N_2 = 1$ , $q_2 = 0$ and $n_2^{(i)} = 0$ for $i = 0, 1, \dots, L-1$ , and $q_2$ is not reported. +- When $(N_1, N_2) = (2, 1)$ , $n_1 = [0, 1]$ and $n_2 = [0, 0]$ , and $i_{1,2}$ is not reported. +- When $(N_1, N_2) = (4, 1)$ and $L = 4$ , $n_1 = [0, 1, 2, 3]$ and $n_2 = [0, 0, 0, 0]$ , and $i_{1,2}$ is not reported. +- When $(N_1, N_2) = (2, 2)$ and $L = 4$ , $n_1 = [0, 1, 0, 1]$ and $n_2 = [0, 0, 1, 1]$ , and $i_{1,2}$ is not reported. + +**Table 5.2.2.2.3-1: Combinatorial coefficients $C(x, y)$** + +| $y$
$x$ | 1 | 2 | 3 | 4 | +|------------|----|-----|-----|------| +| 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | 0 | 0 | 0 | +| 2 | 2 | 1 | 0 | 0 | +| 3 | 3 | 3 | 1 | 0 | +| 4 | 4 | 6 | 4 | 1 | +| 5 | 5 | 10 | 10 | 5 | +| 6 | 6 | 15 | 20 | 15 | +| 7 | 7 | 21 | 35 | 35 | +| 8 | 8 | 28 | 56 | 70 | +| 9 | 9 | 36 | 84 | 126 | +| 10 | 10 | 45 | 120 | 210 | +| 11 | 11 | 55 | 165 | 330 | +| 12 | 12 | 66 | 220 | 495 | +| 13 | 13 | 78 | 286 | 715 | +| 14 | 14 | 91 | 364 | 1001 | +| 15 | 15 | 105 | 455 | 1365 | + +The strongest coefficient on layer $l, l = 1, \dots, \nu$ is identified by $i_{1,3,l} \in \{0, 1, \dots, 2L-1\}$ . + +The amplitude coefficient indicators $i_{1,4,l}$ and $i_{2,2,l}$ are + +$$i_{1,4,l} = [k_{l,0}^{(1)}, k_{l,1}^{(1)}, \dots, k_{l,2L-1}^{(1)}]$$ + +$$i_{2,2,l} = [k_{l,0}^{(2)}, k_{l,1}^{(2)}, \dots, k_{l,2L-1}^{(2)}]$$ + +$$k_{l,i}^{(1)} \in \{0, 1, \dots, 7\}$$ + +$$k_{l,i}^{(2)} \in \{0, 1\}$$ + +for $l = 1, \dots, \nu$ . The mapping from $k_{l,i}^{(1)}$ to the amplitude coefficient $p_{l,i}^{(1)}$ is given in Table 5.2.2.2.3-2 and the mapping from $k_{l,i}^{(2)}$ to the amplitude coefficient $p_{l,i}^{(2)}$ is given in Table 5.2.2.2.3-3. The amplitude coefficients are represented by + +$$p_l^{(1)} = [p_{l,0}^{(1)}, p_{l,1}^{(1)}, \dots, p_{l,2L-1}^{(1)}]$$ + +$$p_l^{(2)} = [p_{l,0}^{(2)}, p_{l,1}^{(2)}, \dots, p_{l,2L-1}^{(2)}]$$ + +for $l = 1, \dots, \nu$ . + +**Table 5.2.2.2.3-2: Mapping of elements of $i_{1,4,l}$ to $k_{l,i}^{(1)}$ to $p_{l,i}^{(1)}$** + +| $k_{l,i}^{(1)}$ | $p_{l,i}^{(1)}$ | +|-----------------|-----------------| +| 0 | 0 | +| 1 | $\sqrt{1/64}$ | +| 2 | $\sqrt{1/32}$ | +| 3 | $\sqrt{1/16}$ | +| 4 | $\sqrt{1/8}$ | +| 5 | $\sqrt{1/4}$ | +| 6 | $\sqrt{1/2}$ | +| 7 | 1 | + +**Table 5.2.2.2.3-3: Mapping of elements of $i_{2,2,l}$ to $k_{l,i}^{(2)}$ to $p_{l,i}^{(2)}$** + +| $k_{l,i}^{(2)}$ | $p_{l,i}^{(2)}$ | +|-----------------|-----------------| +| 0 | $\sqrt{1/2}$ | +| 1 | 1 | + +The phase coefficient indicators are + +$$i_{2,l} = [c_{l,0}, c_{l,1}, \dots, c_{l,2L-1}]$$ + +for $l = 1, \dots, v$ . + +The amplitude and phase coefficient indicators are reported as follows: + +- The indicators $k_{l,i_{1,3,l}}^{(1)} = 7$ , $k_{l,i_{1,3,l}}^{(2)} = 1$ , and $c_{l,i_{1,3,l}} = 0$ ( $l = 1, \dots, v$ ). $k_{l,i_{1,3,l}}^{(1)}$ , $k_{l,i_{1,3,l}}^{(2)}$ , and $c_{l,i_{1,3,l}}$ are not reported for $l = 1, \dots, v$ . +- The remaining $2L - 1$ elements of $i_{1,4,l}$ ( $l = 1, \dots, v$ ) are reported, where $k_{l,i}^{(1)} \in \{0, 1, \dots, 7\}$ . Let $M_l$ ( $l = 1, \dots, v$ ) be the number of elements of $i_{1,4,l}$ that satisfy $k_{l,i}^{(1)} > 0$ . +- The remaining $2L - 1$ elements of $i_{2,1,l}$ and $i_{2,2,l}$ ( $l = 1, \dots, v$ ) are reported as follows: + - When *subbandAmplitude* is set to 'false', + - $k_{l,i}^{(2)} = 1$ for $l = 1, \dots, v$ , and $i = 0, 1, \dots, 2L - 1$ . $i_{2,2,l}$ is not reported for $l = 1, \dots, v$ . + - For $l = 1, \dots, v$ , the elements of $i_{2,1,l}$ corresponding to the coefficients that satisfy $k_{l,i}^{(1)} > 0$ , $i \neq i_{1,3,l}$ , as determined by the reported elements of $i_{1,4,l}$ , are reported, where $c_{l,i} \in \{0, 1, \dots, N_{\text{PSK}} - 1\}$ and the remaining $2L - M_l$ elements of $i_{2,1,l}$ are not reported and are set to $c_{l,i} = 0$ . + +- When *subbandAmplitude* is set to 'true', + - For $l=1,\dots,v$ , the elements of $i_{2,2,l}$ and $i_{2,1,l}$ corresponding to the $\min(M_l, K^{(2)}) - 1$ strongest coefficients (excluding the strongest coefficient indicated by $i_{1,3,l}$ ), as determined by the corresponding reported elements of $i_{1,4,l}$ , are reported, where $k_{l,i}^{(2)} \in \{0,1\}$ and $c_{l,i} \in \{0,1,\dots,N_{\text{PSK}} - 1\}$ . The values of $K^{(2)}$ are given in Table 5.2.2.2.3-4. The remaining $2L - \min(M_l, K^{(2)})$ elements of $i_{2,2,l}$ are not reported and are set to $k_{l,i}^{(2)} = 1$ . The elements of $i_{2,1,l}$ corresponding to the $M_l - \min(M_l, K^{(2)})$ weakest non-zero coefficients are reported, where $c_{l,i} \in \{0,1,2,3\}$ . The remaining $2L - M_l$ elements of $i_{2,1,l}$ are not reported and are set to $c_{l,i} = 0$ . + - When two elements, $k_{l,x}^{(1)}$ and $k_{l,y}^{(1)}$ , of the reported elements of $i_{1,4,l}$ are identical ( $k_{l,x}^{(1)} = k_{l,y}^{(1)}$ ), then element $\min(x, y)$ is prioritized to be included in the set of the $\min(M_l, K^{(2)}) - 1$ strongest coefficients for $i_{2,1,l}$ and $i_{2,2,l}$ ( $l=1,\dots,v$ ) reporting. + +**Table 5.2.2.2.3-4: Full resolution subband coefficients when *subbandAmplitude* is set to 'true'** + +| $L$ | $K^{(2)}$ | +|-----|-----------| +| 2 | 4 | +| 3 | 4 | +| 4 | 6 | + +The codebooks for 1-2 layers are given in Table 5.2.2.2.3-5, where the indices $m_1^{(i)}$ and $m_2^{(i)}$ are given by + +$$m_1^{(i)} = O_1 n_1^{(i)} + q_1$$ + +$$m_2^{(i)} = O_2 n_2^{(i)} + q_2$$ + +for $i=0,1,\dots,L-1$ , and the quantities $\varphi_{l,i}$ , $u_m$ , and $v_{l,m}$ are given by + +$$\varphi_{l,i} = \begin{cases} e^{j2\pi c_{l,i}/N_{\text{PSK}}} & \text{subbandAmplitude = 'false'} \\ e^{j2\pi c_{l,i}/N_{\text{PSK}}} & \text{subbandAmplitude = 'true', } \min(M_l, K^{(2)}) \text{ strongest coefficients (including } i_{1,3,l} \text{) with } k_{l,i}^{(1)} > 0 \\ e^{j2\pi c_{l,i}/4} & \text{subbandAmplitude = 'true', } M_l - \min(M_l, K^{(2)}) \text{ weakest coefficients with } k_{l,i}^{(1)} > 0 \\ 1 & \text{subbandAmplitude = 'true', } 2L - M_l \text{ coefficients with } k_{l,i}^{(1)} = 0 \end{cases}$$ + +$$u_m = \begin{cases} \begin{bmatrix} 1 & e^{j\frac{2\pi m}{O_2 N_2}} & \dots & e^{j\frac{2\pi m(N_2-1)}{O_2 N_2}} \end{bmatrix} & N_2 > 1 \\ 1 & N_2 = 1 \end{cases}$$ + +$$v_{l,m} = \begin{bmatrix} u_m & e^{j\frac{2\pi l}{O_1 N_1}} u_m & \dots & e^{j\frac{2\pi l(N_1-1)}{O_1 N_1}} u_m \end{bmatrix}^T$$ + +**Table 5.2.2.2.3-5: Codebook for 1-layer and 2-layer CSI reporting using antenna ports 3000 to 2999+PCSI-RS** + +| Layers | | +|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $v = 1$ | $W_{q_1, q_2, n_1, n_2, p_1^{(1)}, p_1^{(2)}, i_{2,1,1}}^{(1)} = W_{q_1, q_2, n_1, n_2, p_1^{(1)}, p_1^{(2)}, i_{2,1,1}}^1$ | +| $v = 2$ | $W_{q_1, q_2, n_1, n_2, p_1^{(1)}, p_1^{(2)}, i_{2,1,1}, p_2^{(1)}, p_2^{(2)}, i_{2,1,2}}^{(2)} = \frac{1}{\sqrt{2}} \begin{bmatrix} W_{q_1, q_2, n_1, n_2, p_1^{(1)}, p_1^{(2)}, i_{2,1,1}}^1 & W_{q_1, q_2, n_1, n_2, p_2^{(1)}, p_2^{(2)}, i_{2,1,2}}^2 \end{bmatrix}$ | +| | $W_{q_1, q_2, n_1, n_2, p_1^{(1)}, p_1^{(2)}, c_l}^l = \frac{1}{\sqrt{N_1 N_2 \sum_{i=0}^{2L-1} (p_{l,i}^{(1)} p_{l,i}^{(2)})^2}} \begin{bmatrix} \sum_{i=0}^{L-1} v_{m_1^{(l)}, m_2^{(l)}} p_{l,i}^{(1)} p_{l,i}^{(2)} \varphi_{l,i} \\ \sum_{i=0}^{L-1} v_{m_1^{(l)}, m_2^{(l)}} p_{l,i+L}^{(1)} p_{l,i+L}^{(2)} \varphi_{l,i+L} \end{bmatrix}, \quad l = 1, 2$

where

and the mappings from i_1 to q_1, q_2, n_1, n_2, p_1^{(1)}, and , and from i_2 to i_{2,1,1}, i_{2,1,2}, p_1^{(2)} and p_2^{(2)} are as described above, including the ranges of the constituent indices of i_1 and i_2.

| + +When the UE is configured with higher layer parameter *codebookType* set to 'typeII', the bitmap parameter *typeII-RI-Restriction* forms the bit sequence $r_1, r_0$ where $r_0$ is the LSB and $r_1$ is the MSB. When $r_i$ is zero, $i \in \{0, 1\}$ , PMI and RI reporting are not allowed to correspond to any precoder associated with $v = i + 1$ layers. The bitmap parameter *n1-n2-codebookSubsetRestriction* forms the bit sequence $B = B_1 B_2$ where bit sequences $B_1$ , and $B_2$ are concatenated to form $B$ . To define $B_1$ and $B_2$ , first define the $O_1 O_2$ vector groups $G(r_1, r_2)$ as + +$$G(r_1, r_2) = \{ v_{N_1 r_1 + x_1, N_2 r_2 + x_2} : x_1 = 0, 1, \dots, N_1 - 1; x_2 = 0, 1, \dots, N_2 - 1 \}$$ + +for + +$$r_1 \in \{ 0, 1, \dots, O_1 - 1 \}$$ + +$$r_2 \in \{ 0, 1, \dots, O_2 - 1 \}$$ + +The UE shall be configured with restrictions for 4 vector groups indicated by $(r_1^{(k)}, r_2^{(k)})$ for $k = 0, 1, 2, 3$ and identified by the group indices + +$$g^{(k)} = O_1 r_2^{(k)} + r_1^{(k)}$$ + +for $k = 0, 1, \dots, 3$ , where the indices are assigned such that $g^{(k)}$ increases as $k$ increases. The remaining vector groups are not restricted. + +- If $N_2 = 1$ , $g^{(k)} = k$ for $k = 0, 1, \dots, 3$ , and $B_1$ is empty. +- If $N_2 > 1$ , $B_1 = b_1^{(10)} \dots b_1^{(0)}$ is the binary representation of the integer $\beta_1$ where $b_1^{(10)}$ is the MSB and $b_1^{(0)}$ is the LSB. $\beta_1$ is found using: + +$$\beta_1 = \sum_{k=0}^3 C(O_1 O_2 - 1 - g^{(k)}, 4 - k)$$ + +where $C(x, y)$ is defined in Table 5.2.2.2.3-1. The group indices $g^{(k)}$ and indicators $(r_1^{(k)}, r_2^{(k)})$ for $k = 0, 1, 2, 3$ may be found from $\beta_1$ using the algorithm: + +$$\begin{aligned} + s_{-1} &= 0 \\ + \text{for } k &= 0, \dots, 3 \\ + \text{Find the largest } x^* &\in \{3 - k, \dots, O_1 O_2 - 1 - k\} \text{ such that } \beta_1 - s_{k-1} \geq C(x^*, 4 - k) \\ + e_k &= C(x^*, 4 - k) \\ + s_k &= s_{k-1} + e_k \\ + g^{(k)} &= O_1 O_2 - 1 - x^* \\ + r_1^{(k)} &= g^{(k)} \bmod O_1 \\ + r_2^{(k)} &= \frac{(g^{(k)} - r_1^{(k)})}{O_1} + \end{aligned}$$ + +The bit sequence $B_2 = B_2^{(0)} B_2^{(1)} B_2^{(2)} B_2^{(3)}$ is the concatenation of the bit sequences $B_2^{(k)}$ for $k = 0, 1, \dots, 3$ , corresponding to the group indices $g^{(k)}$ . The bit sequence $B_2^{(k)}$ is defined as + +$$B_2^{(k)} = b_2^{(k, 2N_1 N_2 - 1)} \dots b_2^{(k, 0)}$$ + +Bits $b_2^{(k, 2(N_1 x_2 + x_1) + 1)} b_2^{(k, 2(N_1 x_2 + x_1))}$ indicate the maximum allowed amplitude coefficient $p_{l,i}^{(1)}$ for the vector in group $g^{(k)}$ indexed by $x_1, x_2$ , where the maximum amplitude coefficients are given in Table 5.2.2.2.3-6. A UE that does not report parameter *amplitudeSubsetRestriction* = 'supported' in its capability signaling is not expected to be configured with $b_2^{(k, 2(N_1 x_2 + x_1) + 1)} b_2^{(k, 2(N_1 x_2 + x_1))} = 01$ or 10. + +**Table 5.2.2.2.3-6: Maximum allowed amplitude coefficients for restricted vectors** + +| Bits
$b_2^{(k, 2(N_1 x_2 + x_1) + 1)} b_2^{(k, 2(N_1 x_2 + x_1))}$ | Maximum Amplitude Coefficient
$p_{l,i}^{(1)}$ | +|-----------------------------------------------------------------------|--------------------------------------------------| +| 00 | 0 | +| 01 | $\sqrt{1/4}$ | +| 10 | $\sqrt{1/2}$ | +| 11 | 1 | + +##### 5.2.2.2.4 Type II Port Selection Codebook + +For 4 antenna ports {3000, 3001, ..., 3003}, 8 antenna ports {3000, 3001, ..., 3007}, 12 antenna ports {3000, 3001, ..., 3011}, 16 antenna ports {3000, 3001, ..., 3015}, 24 antenna ports {3000, 3001, ..., 3023}, and 32 antenna ports {3000, 3001, ..., 3031}, and the UE configured with higher layer parameter *codebookType* set to 'typeII-PortSelection' + +- The number of CSI-RS ports is given by $P_{\text{CSI-RS}} \in \{4, 8, 12, 16, 24, 32\}$ as configured by higher layer parameter *nrofPorts*. +- The value of $L$ is configured with the higher layer parameter *numberOfBeams*, where $L = 2$ when $P_{\text{CSI-RS}} = 4$ and $L \in \{2, 3, 4\}$ when $P_{\text{CSI-RS}} > 4$ . + +- The value of $d$ is configured with the higher layer parameter *portSelectionSamplingSize*, where $d \in \{1, 2, 3, 4\}$ and $d \leq \min\left(\frac{P_{\text{CSI-RS}}}{2}, L\right)$ . +- The value of $N_{\text{PSK}}$ is configured with the higher layer parameter *phaseAlphabetSize*, where $N_{\text{PSK}} \in \{4, 8\}$ . +- The UE is configured with the higher layer parameter *subbandAmplitude* set to 'true' or 'false'. +- The UE shall not report RI $> 2$ . + +The UE is also configured with the higher layer parameter *typeII-PortSelectionRI-Restriction*. The bitmap parameter *typeII-PortSelectionRI-Restriction* forms the bit sequence $r_1, r_0$ where $r_0$ is the LSB and $r_1$ is the MSB. When $r_i$ is zero, $i \in \{0, 1\}$ , PMI and RI reporting are not allowed to correspond to any precoder associated with $v = i + 1$ layers. + +When $v$ is the associated RI value, each PMI value corresponds to the codebook indices $i_1$ and $i_2$ where + +$$i_1 = \begin{cases} [i_{1,1} \ i_{1,3,1} \ i_{1,4,1}] & v=1 \\ [i_{1,1} \ i_{1,3,1} \ i_{1,4,1} \ i_{1,3,2} \ i_{1,4,2}] & v=2 \end{cases}$$ + +$$i_2 = \begin{cases} [i_{2,1,1}] & \text{subbandAmplitude} = \text{'false'}, v=1 \\ [i_{2,1,1} \ i_{2,1,2}] & \text{subbandAmplitude} = \text{'false'}, v=2 \\ [i_{2,1,1} \ i_{2,2,1}] & \text{subbandAmplitude} = \text{'true'}, v=1 \\ [i_{2,1,1} \ i_{2,2,1} \ i_{2,1,2} \ i_{2,2,2}] & \text{subbandAmplitude} = \text{'true'}, v=2 \end{cases}$$ + +The $L$ antenna ports per polarization are selected by the index $i_{l,1}$ , where + +$$i_{l,1} \in \left\{0, 1, \dots, \left\lceil \frac{P_{\text{CSI-RS}}}{2d} \right\rceil - 1\right\}$$ + +The strongest coefficient on layer $l, l=1, \dots, v$ is identified by $i_{l,3,l} \in \{0, 1, \dots, 2L-1\}$ . + +The amplitude coefficient indicators $i_{l,4,l}$ and $i_{2,2,l}$ are + +$$\begin{aligned} i_{l,4,l} &= [k_{l,0}^{(1)}, k_{l,1}^{(1)}, \dots, k_{l,2L-1}^{(1)}] \\ i_{2,2,l} &= [k_{l,0}^{(2)}, k_{l,1}^{(2)}, \dots, k_{l,2L-1}^{(2)}] \\ k_{l,i}^{(1)} &\in \{0, 1, \dots, 7\} \\ k_{l,i}^{(2)} &\in \{0, 1\} \end{aligned}$$ + +for $l=1, \dots, v$ . The mapping from $k_{l,i}^{(1)}$ to the amplitude coefficient $p_{l,i}^{(1)}$ is given in Table 5.2.2.2.3-2 and the mapping from $k_{l,i}^{(2)}$ to the amplitude coefficient $p_{l,i}^{(2)}$ is given in Table 5.2.2.2.3-3. The amplitude coefficients are represented by + +$$\begin{aligned} p_l^{(1)} &= [p_{l,0}^{(1)}, p_{l,1}^{(1)}, \dots, p_{l,2L-1}^{(1)}] \\ p_l^{(2)} &= [p_{l,0}^{(2)}, p_{l,1}^{(2)}, \dots, p_{l,2L-1}^{(2)}] \end{aligned}$$ + +for $l=1, \dots, v$ . + +The phase coefficient indicators are + +$$i_{2,l} = [c_{l,0}, c_{l,1}, \dots, c_{l,2L-1}]$$ + +for $l = 1, \dots, v$ . + +The amplitude and phase coefficient indicators are reported as follows: + +- The indicators $k_{l,i_{3,l}}^{(1)} = 7$ , $k_{l,i_{3,l}}^{(2)} = 1$ , and $c_{l,i_{3,l}} = 0$ ( $l = 1, \dots, v$ ). $k_{l,i_{3,l}}^{(1)}$ , $k_{l,i_{3,l}}^{(2)}$ , and $c_{l,i_{3,l}}$ are not reported for $l = 1, \dots, v$ . +- The remaining $2L - 1$ elements of ( $l = 1, \dots, v$ ) are reported, where $k_{l,i}^{(1)} \in \{0, 1, \dots, 7\}$ . Let $M_l$ ( $l = 1, \dots, v$ ) be the number of elements of that satisfy $k_{l,i}^{(1)} > 0$ . +- The remaining $2L - 1$ elements of $i_{2,l}$ and $i_{2,l}$ ( $l = 1, \dots, v$ ) are reported as follows: + - When *subbandAmplitude* is set to 'false', + - $k_{l,i}^{(2)} = 1$ for $l = 1, \dots, v$ , and $i = 0, 1, \dots, 2L - 1$ . $i_{2,l}$ is not reported for $l = 1, \dots, v$ . + - For $l = 1, \dots, v$ , the $M_l - 1$ elements of $i_{2,l}$ corresponding to the coefficients that satisfy $k_{l,i}^{(1)} > 0$ , $i \neq i_{3,l}$ , as determined by the reported elements of $i_{1,l}$ , are reported, where $c_{l,i} \in \{0, 1, \dots, N_{\text{PSK}} - 1\}$ and the remaining $2L - M_l$ elements of $i_{2,l}$ are not reported and are set to $c_{l,i} = 0$ . + - When *subbandAmplitude* is set to 'true', + - For $l = 1, \dots, v$ , the elements of $i_{2,l}$ and $i_{2,l}$ corresponding to the $\min(M_l, K^{(2)}) - 1$ strongest coefficients (excluding the strongest coefficient indicated by $i_{1,l}$ ), as determined by the corresponding reported elements of $i_{1,l}$ , are reported, where $k_{l,i}^{(2)} \in \{0, 1\}$ and $c_{l,i} \in \{0, 1, \dots, N_{\text{PSK}} - 1\}$ . The values of $K^{(2)}$ are given in Table 5.2.2.2.3-4. The remaining $2L - \min(M_l, K^{(2)})$ elements of $i_{2,l}$ are not reported and are set to $k_{l,i}^{(2)} = 1$ . The elements of $i_{2,l}$ corresponding to the $M_l - \min(M_l, K^{(2)})$ weakest non-zero coefficients are reported, where $c_{l,i} \in \{0, 1, 2, 3\}$ . The remaining $2L - M_l$ elements of $i_{2,l}$ are not reported and are set to $c_{l,i} = 0$ . + - When two elements, $k_{l,x}^{(1)}$ and $k_{l,y}^{(1)}$ , of the reported elements of $i_{1,l}$ are identical ( $k_{l,x}^{(1)} = k_{l,y}^{(1)}$ ), then element $\min(x, y)$ is prioritized to be included in the set of the $\min(M_l, K^{(2)}) - 1$ strongest coefficients for $i_{2,l}$ and $i_{2,l}$ ( $l = 1, \dots, v$ ) reporting. + +The codebooks for 1-2 layers are given in Table 5.2.2.2.4-1, where the quantity $\varphi_{l,i}$ is given by + +$$\varphi_{l,i} = \begin{cases} e^{j2\pi c_{l,i}/N_{\text{PSK}}} & \text{subbandAmplitude = 'false'} \\ e^{j2\pi c_{l,i}/N_{\text{PSK}}} & \text{subbandAmplitude = 'true', } \min(M_l, K^{(2)}) \text{ strongest coefficients (including } i_{3,l} \text{) with } k_{l,i}^{(1)} > 0 \\ e^{j2\pi c_{l,i}/4} & \text{subbandAmplitude = 'true', } M_l - \min(M_l, K^{(2)}) \text{ weakest coefficients with } k_{l,i}^{(1)} > 0 \\ 1 & \text{subbandAmplitude = 'true', } 2L - M_l \text{ coefficients with } k_{l,i}^{(1)} = 0 \end{cases}$$ + +and $v_m$ is a $P_{CSI-RS}/2$ -element column vector containing a value of 1 in element $(m \bmod P_{CSI-RS}/2)$ and zeros elsewhere (where the first element is element 0). + +**Table 5.2.2.2.4-1: Codebook for 1-layer and 2-layer CSI reporting using antenna ports 3000 to 2999+ $P_{CSI-RS}$** + +| Layers | | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $v = 1$ | $W_{i_1, p_1^{(1)}, p_1^{(2)}, i_{2,1,1}}^{(1)} = W_{i_1, p_1^{(1)}, p_1^{(2)}, i_{2,1,1}}^1$ | +| $v = 2$ | $W_{i_1, p_1^{(1)}, p_1^{(2)}, i_{2,1,1}, p_2^{(1)}, p_2^{(2)}, i_{2,1,2}}^{(2)} = \frac{1}{\sqrt{2}} \begin{bmatrix} W_{i_1, p_1^{(1)}, p_1^{(2)}, i_{2,1,1}}^1 & W_{i_1, p_2^{(1)}, p_2^{(2)}, i_{2,1,2}}^2 \end{bmatrix}$ | +| | $W_{i_1, p_1^{(1)}, p_1^{(2)}, i_{2,1,1}}^l = \frac{1}{\sqrt{\sum_{i=0}^{2L-1} (p_{l,i}^{(1)} p_{l,i}^{(2)})^2}} \begin{bmatrix} \sum_{i=0}^{L-1} v_{i_1, d+i} p_{l,i}^{(1)} p_{l,i}^{(2)} \varphi_{l,i} \\ \sum_{i=0}^{L-1} v_{i_1, d+i} p_{l,i+L}^{(1)} p_{l,i+L}^{(2)} \varphi_{l,i+L} \end{bmatrix}, \quad l = 1, 2$

where

and the mappings from i_1 to i_{1,1}, p_1^{(1)}, and p_1^{(2)} and from i_2 to i_{2,1,1}, i_{2,1,2}, p_2^{(1)}, and p_2^{(2)} are as described above, including the ranges of the constituent indices of i_1 and i_2.

| + +##### 5.2.2.2.5 Enhanced Type II Codebook + +For 4 antenna ports {3000, 3001, ..., 3003}, 8 antenna ports {3000, 3001, ..., 3007}, 12 antenna ports {3000, 3001, ..., 3011}, 16 antenna ports {3000, 3001, ..., 3015}, 24 antenna ports {3000, 3001, ..., 3023}, and 32 antenna ports {3000, 3001, ..., 3031}, and UE configured with higher layer parameter *codebookType* set to 'typeII-r16' + +- The values of $\beta$ and $\delta$ are configured with the higher layer parameter *n1-n2-codebookSubsetRestriction-r16*. The supported configurations of $\beta$ for a given number of CSI-RS ports and the corresponding values of $\delta$ are given in Table 5.2.2.2.1-2. The number of CSI-RS ports, $N$ , is . +- The values of $\beta$ , and $\delta$ are determined by the higher layer parameter *paramCombination-r16*, where the mapping is given in Table 5.2.2.2.5-1. + - The UE is not expected to be configured with *paramCombination-r16* equal to + - 3, 4, 5, 6, 7, or 8 when $N = 4$ , + - 7 or 8 when $N = 8$ , + - 7 or 8 when higher layer parameter *typeII-RI-Restriction-r16* is configured with $\beta$ for any $N$ . + - 7 or 8 when $N = 12$ . +- The parameter $\beta$ is configured with the higher-layer parameter *numberOfPMI-SubbandsPerCQI-Subband*. This parameter controls the total number of precoding matrices indicated by the PMI as a function of the number of configured subbands in *csi-ReportingBand*, the subband size configured by the higher-level parameter *subbandSize* and of the total number of PRBs in the bandwidth part according to Table 5.2.1.4-2, as follows: + - When $\beta = 1$ : + - One precoding matrix is indicated by the PMI for each subband in *csi-ReportingBand*. + - When $\beta = 2$ : + - For each subband in *csi-ReportingBand* that is not the first or last subband of a BWP, two precoding matrices are indicated by the PMI: the first precoding matrix corresponds to the first PRBs of the subband and the second precoding matrix corresponds to the last PRBs of the subband. + - For each subband in *csi-ReportingBand* that is the first or last subband of a BWP + +- If , one precoding matrix is indicated by the PMI corresponding to the first subband. If , two precoding matrices are indicated by the PMI corresponding to the first subband: the first precoding matrix corresponds to the first PRBs of the first subband and the second precoding matrix corresponds to the last PRBs of the first subband. +- If , one precoding matrix is indicated by the PMI corresponding to the last subband. If , two precoding matrices are indicated by the PMI corresponding to the last subband: the first precoding matrix corresponds to the first PRBs of the last subband and the second precoding matrix corresponds to the last PRBs of the last subband. + +**Table 5.2.2.2.5-1: Codebook parameter configurations for $\beta$ and $\alpha$** + +| paramCombination-r16 | $\beta$ | $\alpha$ | | $\alpha$ | +|-----------------------------|---------|---------------|---------------|---------------| +| | | $\alpha_1$ | $\alpha_2$ | | +| 1 | 2 | $\frac{1}{4}$ | $\frac{1}{8}$ | $\frac{1}{4}$ | +| 2 | 2 | $\frac{1}{4}$ | $\frac{1}{8}$ | $\frac{1}{2}$ | +| 3 | 4 | $\frac{1}{4}$ | $\frac{1}{8}$ | $\frac{1}{4}$ | +| 4 | 4 | $\frac{1}{4}$ | $\frac{1}{8}$ | $\frac{1}{2}$ | +| 5 | 4 | $\frac{1}{4}$ | $\frac{1}{4}$ | $\frac{3}{4}$ | +| 6 | 4 | $\frac{1}{2}$ | $\frac{1}{4}$ | $\frac{1}{2}$ | +| 7 | 6 | $\frac{1}{4}$ | - | $\frac{1}{2}$ | +| 8 | 6 | $\frac{1}{4}$ | - | $\frac{3}{4}$ | + +- The UE shall report the RI value according to the configured higher layer parameter *typeII-RI-Restriction-r16*. The UE shall not report . + +The PMI value corresponds to the codebook indices of $i_1$ and $i_2$ where + +The precoding matrices indicated by the PMI are determined from vectors. + +vectors, , are identified by the indices , , indicated by , , obtained as in 5.2.2.2.3, where the values of are given in Table 5.2.2.2.5-4. + +vectors, , , are identified by (for ) and where + +which are indicated by means of the indices (for ) and , where + +The amplitude coefficient indicators and are + +for . + +The phase coefficient indicator is + +for + +Let . The bitmap whose nonzero bits identify which coefficients in and are reported, is indicated by + +for , such that is the number of nonzero coefficients for layer and is the total number of nonzero coefficients. + +The indices of , and are associated to the codebook indices in . + +The mapping from to the amplitude coefficient is given in Table 5.2.2.2.5-2 and the mapping from to the amplitude coefficient is given in Table 5.2.2.2.5-3. The amplitude coefficients are represented by + +for. + +Let be the index of and be the index of which identify the strongest coefficient of layer , i.e., the element of , for . The codebook indices of are remapped with respect to as , such that , after remapping. The index is remapped with respect to as , such that the index of the strongest coefficient is (), after remapping. The indices of , and indicate amplitude coefficients, phase coefficients and bitmap after remapping. + +The strongest coefficient of layer is identified by , which is obtained as follows + +for . + +**Table 5.2.2.2.5-2: Mapping of elements of : to** + +| | | | | | | | | +|---|----------|---|--|----|--|----|---| +| | | | | | | | | +| 0 | Reserved | 4 | | 8 | | 12 | | +| 1 | | 5 | | 9 | | 13 | | +| 2 | | 6 | | 10 | | 14 | | +| 3 | | 7 | | 11 | | 15 | 1 | + +The amplitude and phase coefficient indicators are reported as follows: + +- $\delta_{amp}$ , $\delta_{phase}$ , and $\delta_{amp\_phase}$ . The indicators $\delta_{amp}$ and $\delta_{phase}$ are not reported for $\delta_{amp\_phase}$ . +- The indicator $\delta_{amp\_phase}$ is reported for $\delta_{amp}$ . +- The indicators $\delta_{amp}$ for which $\delta_{amp\_phase}$ are reported. +- The indicators $\delta_{phase}$ for which $\delta_{amp\_phase}$ are reported. +- The remaining $\delta_{amp}$ indicators are not reported. +- The remaining $\delta_{phase}$ indicators are not reported. + +**Table 5.2.2.2.5-3: Mapping of elements of $\delta_{amp\_phase}$ to $\delta_{amp}$** + +| $\delta_{amp\_phase}$ | $\delta_{amp}$ | +|-----------------------|----------------| +| 0 | | +| 1 | | +| 2 | | +| 3 | | +| 4 | | +| 5 | | +| 6 | | +| 7 | 1 | + +The elements of $\delta_{amp}$ and $\delta_{phase}$ are found from using the algorithm described in 5.2.2.2.3, where the values of $\delta_{amp\_phase}$ are given in Table 5.2.2.2.5-4. + +For $\delta_{amp\_phase}$ , is identified by $\delta_{amp\_phase}$ . + +For all values of $\delta_{amp\_phase}$ , for $\delta_{amp}$ . If, the nonzero elements of $\delta_{amp}$ , identified by $\delta_{amp\_phase}$ are found from $\delta_{amp}$ , for $\delta_{amp\_phase}$ , and from $\delta_{phase}$ and $\delta_{amp\_phase}$ , for $\delta_{amp}$ , using as defined in Table 5.2.2.2.5-4 and the algorithm: + +for + +Find the largest $\delta_{amp\_phase}$ in Table 5.2.2.2.5-4 such that + +if + +else + +if + +else + +end if + +end if + +**Table 5.2.2.2.5-4: Combinatorial coefficients** + +| $\begin{matrix} y \\ x \end{matrix}$ | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | +|--------------------------------------|----|-----|-----|------|------|-------|-------|-------|-------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 2 | 2 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| 3 | 3 | 3 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | +| 4 | 4 | 6 | 4 | 1 | 0 | 0 | 0 | 0 | 0 | +| 5 | 5 | 10 | 10 | 5 | 1 | 0 | 0 | 0 | 0 | +| 6 | 6 | 15 | 20 | 15 | 6 | 1 | 0 | 0 | 0 | +| 7 | 7 | 21 | 35 | 35 | 21 | 7 | 1 | 0 | 0 | +| 8 | 8 | 28 | 56 | 70 | 56 | 28 | 8 | 1 | 0 | +| 9 | 9 | 36 | 84 | 126 | 126 | 84 | 36 | 9 | 1 | +| 10 | 10 | 45 | 120 | 210 | 252 | 210 | 120 | 45 | 10 | +| 11 | 11 | 55 | 165 | 330 | 462 | 462 | 330 | 165 | 55 | +| 12 | 12 | 66 | 220 | 495 | 792 | 924 | 792 | 495 | 220 | +| 13 | 13 | 78 | 286 | 715 | 1287 | 1716 | 1716 | 1287 | 715 | +| 14 | 14 | 91 | 364 | 1001 | 2002 | 3003 | 3432 | 3003 | 2002 | +| 15 | 15 | 105 | 455 | 1365 | 3003 | 5005 | 6435 | 6435 | 5005 | +| 16 | 16 | 120 | 560 | 1820 | 4368 | 8008 | 11440 | 12870 | 11440 | +| 17 | 17 | 136 | 680 | 2380 | 6188 | 12376 | 19448 | 24310 | 24310 | +| 18 | 18 | 153 | 816 | 3060 | 8568 | 18564 | 31824 | 43758 | 48620 | + +When $x$ and $y$ are known, $\binom{y}{x}$ are found as follows: + +- If $x > y$ , $\binom{y}{x}$ is not reported. If $x = y$ , for $x$ , $\binom{y}{x}$ is not reported. If $x < y$ , where $\binom{y}{x}$ is given in Table 5.2.2.2.5-4 and where the indices $x$ and $y$ are assigned such that $x$ increases as $y$ increases. +- If $x > y$ , is indicated by $x$ , which is reported and given by + +Only the nonzero indices $\binom{y}{x}$ , where $x < y$ , are reported, where the indices $x$ and $y$ are assigned such that $x$ increases as $y$ increases. Let + +then $\binom{y}{x}$ , where $\binom{y}{x}$ is given in Table 5.2.2.2.5-4. + +The codebooks for 1-4 layers are given in Table 5.2.2.2.5-5, where $\binom{y}{x}$ , for $x$ are obtained as in clause 5.2.2.2.3, and the quantities $\binom{y}{x}$ and are given by + +where $i$ is the index associated with the precoding matrix, $i$ and with + +for. + +**Table 5.2.2.5-5: Codebook for 1-layer, 2-layer, 3-layer and 4-layer CSI reporting using antenna ports 3000 to 2999+PCSI-RS** + +| Layers | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | +| | | +| | | +| | | +|

Where

and the mappings from i to i_1, i_2, i_3, i_4, and from i to i_1, i_2, and i and i are as described above, including the ranges of the constituent indices of i and i.

| | + +For coefficients with $i$ , amplitude and phase are set to zero, i.e., $i$ and $i$ . + +The bitmap parameter *typeII-RI-Restriction-r16* forms the bit sequence $i$ where $i$ is the LSB and $i$ is the MSB. When $i$ is zero, $i$ , PMI and RI reporting are not allowed to correspond to any precoder associated with $i$ layers. + +The bitmap parameter *n1-n2-codebookSubsetRestriction-r16* forms the bit sequence $i$ and configures the vector group indices $i$ as in clause 5.2.2.2.3. Bits $i$ indicate the maximum allowed average amplitude, $i$ ( $i$ ), with $i$ of the coefficients associated with the vector in group $i$ indexed by $i$ , where the maximum amplitudes are given in Table 5.2.2.5-6 and the average coefficient amplitude is restricted as follows + +for $i$ and $i$ . A UE that does not report the parameter *amplitudeSubsetRestriction-r16* = 'supported' in its capability signaling is not expected to be configured with $i$ or $i$ . + +**Table 5.2.2.5-6: Maximum allowed average coefficient amplitudes for restricted vectors** + +| Bit | Maximum Average Coefficient Amplitude | +|-----|---------------------------------------| +| 00 | 0 | +| 01 | | +| 10 | | +| 11 | 1 | + +##### 5.2.2.2.6 Enhanced Type II Port Selection Codebook + +For 4 antenna ports {3000, 3001, ..., 3003}, 8 antenna ports {3000, 3001, ..., 3007}, 12 antenna ports {3000, 3001, ..., 3011}, 16 antenna ports {3000, 3001, ..., 3015}, 24 antenna ports {3000, 3001, ..., 3023}, and 32 antenna ports {3000, 3001, ..., 3031}, and the UE configured with higher layer parameter *codebookType* set to 'typeII-PortSelection-r16' + +- The number of CSI-RS ports is configured as in Clause 5.2.2.2.4 +- The value of $\beta$ is configured with the higher layer parameter *portSelectionSamplingSize-r16*, where $\beta \in \{1/4, 1/8, 1/2\}$ . +- The values $\beta$ , $\alpha$ , and $\gamma$ are configured as in Clause 5.2.2.2.5, where the supported configurations are given in Table 5.2.2.6-1. + +**Table 5.2.2.6-1: Codebook parameter configurations for $\beta$ , $\alpha$ , and $\gamma$** + +| paramCombination-r16 | $\beta$ | $\alpha$ | | $\gamma$ | +|-----------------------------|---------|------------|------------|----------| +| | | $\alpha_1$ | $\alpha_2$ | | +| 1 | 2 | $1/4$ | $1/8$ | $1/4$ | +| 2 | 2 | $1/4$ | $1/8$ | $1/2$ | +| 3 | 4 | $1/4$ | $1/8$ | $1/4$ | +| 4 | 4 | $1/4$ | $1/8$ | $1/2$ | +| 5 | 4 | $1/4$ | $1/4$ | $3/4$ | +| 6 | 4 | $1/2$ | $1/4$ | $1/2$ | + +- The UE shall report the RI value according to the configured higher layer parameter *typeII-PortSelectionRI-Restriction-r16*. The UE shall not report $\gamma$ . +- The value of $\beta$ is configured as in Clause 5.2.2.2.5. + +The UE is also configured with the higher layer bitmap parameter *typeII-PortSelectionRI-Restriction-r16*, which forms the bit sequence $b$ , where $b_0$ is the LSB and $b_{L-1}$ is the MSB. When $b_0$ is zero, $\beta$ , PMI and RI reporting are not allowed to correspond to any precoder associated with $\beta$ layers. + +The PMI value corresponds to the codebook indices $i_1$ and $i_2$ where + +The antenna ports are selected by the index $i_1$ as in clause 5.2.2.2.4. + +Parameters $\beta$ , $\alpha$ (for $\alpha_1$ and $\alpha_2$ ) and $\gamma$ are defined as in clause 5.2.2.2.5. + +For layer $l$ , the strongest coefficient the amplitude coefficient indicators $a_{l,0}$ and $a_{l,1}$ , the phase coefficient indicator $\phi_l$ and the bitmap indicator $b_l$ are defined and indicated as in clause 5.2.2.2.5, where the mapping from $a_{l,0}$ to the amplitude coefficient is given in Table 5.2.2.2.5-2 and the mapping from $a_{l,1}$ to the amplitude coefficient is given in Table 5.2.2.2.5-3. + +The number of nonzero coefficients for layer $l$ , $N_l$ , and the total number of nonzero coefficients $N$ are defined as in Clause 5.2.2.2.5. + +The amplitude coefficients $a_{l,0}$ and $a_{l,1}$ are represented as in clause 5.2.2.2.5. + +The amplitude and phase coefficient indicators are reported as in clause 5.2.2.2.5. + +Codebook indicators $i_1$ and $i_2$ are found as in clause 5.2.2.2.5. + +The codebooks for 1-4 layers are given in Table 5.2.2.6-2, where $\mathbf{e}_i$ is a $N$ -element column vector containing a value of 1 in element $i$ and zeros elsewhere (where the first element is element 0), and the quantities $\beta$ and $\alpha$ are defined as in clause 5.2.2.2.5. + +**Table 5.2.2.2.6-2: Codebook for 1-layer, 2-layer, 3-layer and 4-layer CSI reporting using antenna ports 3000 to 2999+ $P_{CSI-RS}$** + +| Layers | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | +| | | +| | | +| | | +| | | +|

Where ,

and the mappings from to , , , , and from to , , , , , and , , , and are as described above, including the ranges of the constituent indices of and .

| | + +For coefficients with , amplitude and phase are set to zero, i.e., and . + +##### 5.2.2.2.7 Further enhanced Type II port selection codebook + +For 4 antenna ports {3000, 3001, ..., 3003}, 8 antenna ports {3000, 3001, ..., 3007}, 12 antenna ports {3000, 3001, ..., 3011}, 16 antenna ports {3000, 3001, ..., 3015}, 24 antenna ports {3000, 3001, ..., 3023}, and 32 antenna ports {3000, 3001, ..., 3031}, and the UE configured with higher layer parameter *codebookType* set to 'typeII-PortSelection-r17' + +- The number of CSI-RS ports, , is configured as in clause 5.2.2.2.4. +- The values , and are determined by the higher layer parameter *paramCombination-r17*, where the mapping is given in Table 5.2.2.2.7-1. + - The UE is not expected to be configured with *paramCombination-r17* equal to + - 1 or 6 when , + - 7 or 8 when , + - 5 when and higher layer parameter *typeII-PortSelectionRI-Restriction-r17* is configured with for any . + +**Table 5.2.2.2.7-1: Codebook parameter configurations for , and** + +| paramCombination-r17 | | | | +|-----------------------------|---|---------------|---------------| +| 1 | 1 | $\frac{3}{4}$ | $\frac{1}{2}$ | +| 2 | 1 | 1 | $\frac{1}{2}$ | +| 3 | 1 | 1 | $\frac{3}{4}$ | +| 4 | 1 | 1 | 1 | +| 5 | 2 | $\frac{1}{2}$ | $\frac{1}{2}$ | +| 6 | 2 | $\frac{3}{4}$ | $\frac{1}{2}$ | +| 7 | 2 | 1 | $\frac{1}{2}$ | +| 8 | 2 | 1 | $\frac{3}{4}$ | + +- The parameter $\text{valueOfN}$ is configured with the higher-layer parameter $\text{valueOfN}$ , when $\text{typeII-PortSelectionRI-Restriction-r17}$ is configured. +- The parameter $\text{numberOfPMI-SubbandsPerCQI-Subband-r17}$ is configured with the higher-layer parameter $\text{numberOfPMI-SubbandsPerCQI-Subband-r17}$ , when $\text{typeII-PortSelectionRI-Restriction-r17}$ is configured, and when $\text{typeII-PortSelectionRI-Restriction-r17}$ is defined as in clause 5.2.2.2.5. +- The UE shall report the RI value according to the configured higher layer parameter $\text{typeII-PortSelectionRI-Restriction-r17}$ . The UE shall not report $\text{typeII-PortSelectionRI-Restriction-r17}$ . The bitmap parameter $\text{typeII-PortSelectionRI-Restriction-r17}$ forms the bit sequence $b_0, b_1, \dots, b_{N-1}$ , where $b_0$ is the LSB and $b_{N-1}$ is the MSB. When $\text{typeII-PortSelectionRI-Restriction-r17}$ is zero, $\text{typeII-PortSelectionRI-Restriction-r17}$ , PMI and RI reporting are not allowed to correspond to any precoder associated with $\text{typeII-PortSelectionRI-Restriction-r17}$ layers. + +The PMI value corresponds to the codebook indices $i_1$ and $i_2$ where + +The precoding matrices indicated by the PMI are determined from vectors $\mathbf{a}_i$ , where $i$ and $j$ . + +ports are selected from $\text{typeII-PortSelectionRI-Restriction-r17}$ ports based on vectors $\mathbf{a}_i$ , which are identified by + +which are indicated by the index $i$ , where + +The elements of $\mathbf{a}_i$ are found from using $\text{typeII-PortSelectionRI-Restriction-r17}$ as defined in Tables 5.2.2.2.5-4 and 5.2.2.2.7-2 and the algorithm: + +for + +Find the largest $i$ in Table 5.2.2.2.5-4, if $\text{typeII-PortSelectionRI-Restriction-r17}$ , or in Table 5.2.2.2.7-2, if $\text{typeII-PortSelectionRI-Restriction-r17}$ , such that + +When $\text{typeII-PortSelectionRI-Restriction-r17}$ are known, $\mathbf{a}_i$ is found using $\text{typeII-PortSelectionRI-Restriction-r17}$ , where $\text{typeII-PortSelectionRI-Restriction-r17}$ is given in Tables 5.2.2.2.5-4 and 5.2.2.2.7-2, and where the indices $i$ are assigned such that $\mathbf{a}_i$ increases as $i$ increases. + +- If $\text{typeII-PortSelectionRI-Restriction-r17}$ , $\text{typeII-PortSelectionRI-Restriction-r17}$ , and $\text{typeII-PortSelectionRI-Restriction-r17}$ is not reported. + +**Table 5.2.2.2.7-2: Combinatorial coefficients** + +| | | | | +|--|----|----|----| +| | 10 | 11 | 12 | +|--|----|----|----| + +| | | | | +|-----------|------|------|-----| +| 0 | 0 | 0 | 0 | +| 1 | 0 | 0 | 0 | +| 2 | 0 | 0 | 0 | +| 3 | 0 | 0 | 0 | +| 4 | 0 | 0 | 0 | +| 5 | 0 | 0 | 0 | +| 6 | 0 | 0 | 0 | +| 7 | 0 | 0 | 0 | +| 8 | 0 | 0 | 0 | +| 9 | 0 | 0 | 0 | +| 10 | 1 | 0 | 0 | +| 11 | 11 | 1 | 0 | +| 12 | 66 | 12 | 1 | +| 13 | 286 | 78 | 13 | +| 14 | 1001 | 364 | 91 | +| 15 | 3003 | 1365 | 455 | + +vectors, , , are identified by , where is defined as in clause 5.2.2.2.5, and where + +with the indices assigned such that increases with . is indicated by the index , when and , where + +- If , or and , is not reported. +- If and , the nonzero offset between and is reported with assuming that (reference for the offset) is 0. The nonzero offset values are mapped to the index values of in increasing order with offset value 1 mapped to index value '0'. + +The amplitude coefficient indicators and , for , are + +The phase coefficient indicator , for , is + +Let . The bitmap whose nonzero bits identify which coefficients in and are reported, is indicated by , for + +such that $N_{\text{nz}}$ is the number of nonzero coefficients for layer $l$ and $N$ is the total number of nonzero coefficients. + +- If $N_{\text{nz}}$ and $N$ are not reported, for $l$ . + +The indices of $N_{\text{nz}}$ and $N$ are associated to the codebook indices in $l$ . + +The mapping from $N_{\text{nz}}$ to the amplitude coefficient is given in Table 5.2.2.2.5-2 and the mapping from $N$ to the amplitude coefficient is given in Table 5.2.2.2.5-3. The amplitude coefficients are represented by + +Let $l$ be the index of $l$ and $i$ be the index of $i$ which identify the strongest coefficient of layer $l$ , i.e., the element of $l$ , for $l$ . The strongest coefficient of layer $l$ is identified by the index + +which is found from + +The amplitude and phase coefficient indicators are reported as follows: + +- $l$ , $i$ , and $l$ . The elements $l$ , and $l$ are not reported for $l$ . +- The element $l$ is reported for $l$ . +- The elements for which $l$ , are reported. +- The elements for which $l$ , are reported. +- The remaining elements are not reported. +- The remaining elements are not reported. + +The codebooks for 1-4 layers are given in Table 5.2.2.2.7-3, where $\mathbf{e}_i$ is a $N$ -element column vector containing a value of 1 in the element of index $i$ and zeros elsewhere (where the first element is the element of index 0), the quantities are given by + +where $l$ , is the index associated with the precoding matrix and where + +for $l$ , and the quantities are given by + +**Table 5.2.2.2.7-3: Codebook for 1-layer, 2-layer, 3-layer and 4-layer CSI reporting using antenna ports 3000 to 2999+PCSI-RS** + +| | | +|---------------|--| +| Layers | | +|---------------|--| + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | +| | | +| | | +| | | +|

Where ,

and the mappings from to , and from to , , , , , , , , are as described above, including the ranges of the constituent indices of and .

| | + +For coefficients with , amplitude and phase are set to zero, i.e., and . + +##### 5.2.2.2.8 Enhanced Type II codebook for CJT + +For 4 antenna ports {3000, 3001, ..., 3003}, 8 antenna ports {3000, 3001, ..., 3007}, 12 antenna ports {3000, 3001, ..., 3011}, 16 antenna ports {3000, 3001, ..., 3015}, 24 antenna ports {3000, 3001, ..., 3023}, and 32 antenna ports {3000, 3001, ..., 3031} per CSI-RS resource, and the UE configured with CSI-RS resources in a resource set for channel measurement and with higher layer parameter *codebookType* set to 'typeII-CJT-r18' + +- the values of , and , are the same for all CSI-RS resources and configured with the higher layer parameter. The supported configurations of for a given number of CSI-RS ports and the corresponding values of are given in Table 5.2.2.2.1-2. The number of CSI-RS ports , is for each of the CSI-RS resources. + +A set of combinations of values of is configured by the higher layer parameter *paramCombination-CJT-L-r18*, where the value of is configured by the higher layer parameter *numberOfSDCombinations* and the mapping is given in Table 5.2.2.2.8-1, with the value of corresponding to CSI-RS resource , for . A single value of and is configured by the higher layer parameter *paramCombination-CJT-r18*, where the mapping is given in Table 5.2.2.2.8-2. The configurable combinations of and are marked with 'x' in Table 5.2.2.2.8-3. + +- The UE is not expected to be configured with *paramCombination-CJT-L-r18* equal to + - 2, 3 for 2, 3, 4 for ; 2, 3, 4, 5 for ; 2, 3 or 4 for ; when , + - 3 for when , + - 3 for when higher layer parameter *typeII-CJT-RI-Restriction-r18* is configured with for any . + - 3 for when . +- If , the UE is expected to select one of the configured combinations of and report the index of the selected combination, where the index value 0 corresponds to the first configured combination and the index value corresponds to the -th configured combination. If , a single combination of is configured and the selection is not reported. + +**Table 5.2.2.2.8-1: Codebook parameter configurations for** + +| | paramCombination-CJT-L-r18 | | +|---|-----------------------------------|-----| +| 1 | 1 | {2} | +| | 2 | {4} | + +| | | | +|---|---|-----------| +| | 3 | {6} | +| 2 | 1 | {2,2} | +| | 2 | {2,4} | +| | 3 | {4,2} | +| | 4 | {4,4} | +| | | | +| 3 | 1 | {2,2,2} | +| | 2 | {2,2,4} | +| | 3 | {2,4,2} | +| | 4 | {4,2,2} | +| | 5 | {4,4,4} | +| 4 | 1 | {2,2,2,2} | +| | 2 | {2,2,2,4} | +| | 3 | {2,2,4,4} | +| | 4 | {4,4,4,4} | + +Table 5.2.2.2.8-2: Codebook parameter configurations for + +| paramCombination-CJT-r18 | | | | +|---------------------------------|-----|------|-----| +| | | | | +| 1 | 1/8 | 1/16 | 1/4 | +| 2 | 1/8 | 1/16 | 1/2 | +| 3 | 1/4 | 1/8 | 1/4 | +| 4 | 1/4 | 1/8 | 1/2 | +| 5 | 1/4 | 1/4 | 3/4 | +| 6 | 1/2 | 1/4 | 1/2 | +| 7 | 1/2 | 1/2 | 1/2 | + +Table 5.2.2.2.8-3: Configurable combinations of and + +| | paramCombination-CJT-L-r18 | paramCombination-CJT-r18 | | | | | | | +|---|-----------------------------------|---------------------------------|---|---|---|---|---|---| +| | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| 1 | 1 | | | x | x | | | | +| | 2 | | | x | x | x | x | | +| | 3 | | | | x | x | | | +| 2 | 1 | x | | | | | | | +| | 2 | x | | | | | | | +| | 3 | x | | | | | | | +| | 4 | | x | | x | | | x | +| 3 | 1 | x | x | | | | | | +| | 2 | x | x | | | | | | +| | 3 | x | x | | | | | | +| | 4 | x | x | | | | | | +| | 5 | x | x | x | x | x | | x | +| 4 | 1 | x | | | | | | | + +| | | | | | | | | | +|--|---|---|---|--|---|---|--|--| +| | 2 | x | | | | | | | +| | 3 | | | | x | x | | | +| | 4 | | x | | x | x | | | + +- The value of $\text{numberOfPMI-SubbandsPerCQI-Subband-CJT-r18}$ , where $\text{numberOfPMI-SubbandsPerCQI-Subband-CJT-r18}$ and the corresponding value of $\text{typeII-CJT-RI-Restriction-r18}$ are defined as in clause 5.2.2.2.5. +- The UE shall report the RI value according to the configured higher layer parameter $\text{typeII-CJT-RI-Restriction-r18}$ . The UE shall not report $\text{typeII-CJT-RI-Restriction-r18}$ . The bitmap parameter $\text{typeII-CJT-RI-Restriction-r18}$ forms the bit sequence where $\text{typeII-CJT-RI-Restriction-r18}$ is the LSB and $\text{typeII-CJT-RI-Restriction-r18}$ is the MSB. When $\text{typeII-CJT-RI-Restriction-r18}$ is zero, $\text{typeII-CJT-RI-Restriction-r18}$ , PMI and RI reporting are not allowed to correspond to any precoder associated with layers. +- The UE may be configured with higher layer parameter $\text{restrictedCMR-Selection}$ . If $\text{restrictedCMR-Selection}$ is configured, the number of selected CSI-RS resources is $\text{restrictedCMR-Selection}$ . Otherwise, the UE is expected to select $\text{numberOfPMI-SubbandsPerCQI-Subband-CJT-r18}$ CSI-RS resources, with $\text{typeII-CJT-RI-Restriction-r18}$ , and the selection is reported with an $\text{numberOfPMI-SubbandsPerCQI-Subband-CJT-r18}$ -bit bitmap, $\text{typeII-CJT-RI-Restriction-r18}$ , where the CSI-RS resources are mapped from bit to bit by their ordering in the resource set and the first of the selected CSI-RS resources corresponds to the nonzero bit with lowest index. + +The PMI value for the selected CSI-RS resources corresponds to the codebook indices of $\text{typeII-CJT-PMI-CodebookIndex-r18}$ and $\text{typeII-CJT-PMI-CodebookIndex-r18}$ where + +The precoding matrices indicated by the PMI are determined from vectors, where $\text{typeII-CJT-PMI-CodebookIndex-r18}$ are the indices of the selected CSI-RS resources in increasing order, such that $\text{typeII-CJT-PMI-CodebookIndex-r18}$ , and $\text{typeII-CJT-PMI-CodebookIndex-r18}$ are the corresponding values from the selected combination of $\text{typeII-CJT-PMI-CodebookIndex-r18}$ . + +The vectors, $\text{typeII-CJT-PMI-CodebookIndex-r18}$ , corresponding to the $\text{typeII-CJT-PMI-CodebookIndex-r18}$ -th selected CSI-RS resource, for $\text{typeII-CJT-PMI-CodebookIndex-r18}$ , are indicated by $\text{typeII-CJT-PMI-CodebookIndex-r18}$ , where + +and + +Let + +and + +the index $\text{typeII-CJT-PMI-CodebookIndex-r18}$ , for the $\text{typeII-CJT-PMI-CodebookIndex-r18}$ -th selected CSI-RS resource, is obtained from the indices $\text{typeII-CJT-PMI-CodebookIndex-r18}$ , as described in Clause 5.2.2.2.3 for the indicator $\text{typeII-CJT-PMI-CodebookIndex-r18}$ , obtained from the indices $\text{typeII-CJT-PMI-CodebookIndex-r18}$ . Vector $\text{typeII-CJT-PMI-CodebookIndex-r18}$ is then derived from the indices $\text{typeII-CJT-PMI-CodebookIndex-r18}$ and $\text{typeII-CJT-PMI-CodebookIndex-r18}$ , as described in Clause 5.2.2.2.3 for vector $\text{typeII-CJT-PMI-CodebookIndex-r18}$ , derived from indices $\text{typeII-CJT-PMI-CodebookIndex-r18}$ . + +The vectors, $\mathbf{v}_{l,i}$ , for layer $l$ are common for all the selected CSI-RS resources and are indicated by $\mathbf{v}_{l,i}$ (for $i$ ) and $\mathbf{v}_{l,i}$ , which are obtained as described in Clause 5.2.2.2.5, where $\mathbf{v}_{l,i}$ is derived from the selected vectors identified by the indices $\mathbf{v}_{l,i}$ . The vectors' elements are given by + +for $i$ , and $l$ . + +If the higher layer parameter *codebookMode* is set to 'mode1', an offset $\mathbf{v}_{l,i}$ is reported for the $i$ -th selected CSI-RS resource, with $\mathbf{v}_{l,i}$ , relative to the first of the selected CSI-RS resources. The reported offsets are common for all layers and are indicated by $\mathbf{v}_{l,i}$ , given by + +where the value of $\mathbf{v}_{l,i}$ is configured by higher layer parameter *numberOfOf3*. The offsets are represented by + +If *codebookMode* is set to 'mode2', the offset indicator, $\mathbf{v}_{l,i}$ , is not reported and $\mathbf{v}_{l,i}$ for $i$ . + +The reference amplitude coefficient indicator, $\mathbf{v}_{l,i}$ , for layer $l$ , is given by + +The reference amplitude coefficients for layer $l$ are represented by + +and the mapping from $\mathbf{v}_{l,i}$ to $\mathbf{v}_{l,i}$ is given in Table 5.2.2.2.5-2. + +The amplitude coefficient indicator, $\mathbf{v}_{l,i}$ , for layer $l$ , is given by + +The amplitude coefficients for layer $l$ are represented by + +and the mapping from $\mathbf{v}_{l,i}$ to $\mathbf{v}_{l,i}$ is given in Table 5.2.2.2.5-3. + +The phase coefficient indicator, $\mathbf{v}_{l,i}$ , for $i$ , is given by + +The phase coefficients for layer $l$ are represented by + +and the mapping from $k^{(l)}$ to $i$ is given by + +Let $i \in \{0, 1, \dots, 2L-1\}$ . The bitmap whose nonzero bits identify which coefficients in $a_{l,i}$ and $\phi_{l,i}$ are reported for layer $l$ , is indicated by $i_{1,7,l}$ + +Let $K_{NZ}^{(l)}$ be the number of nonzero coefficients for layer $l$ , the total number of nonzero coefficients is reported and given by $K_{NZ}^{tot} = \sum_{l=1}^{\nu} K_{NZ}^{(l)}$ . + +The indices of $i_{1,1}$ , $i_{1,2}$ and $i_{1,5}$ are associated to the selected CSI-RS resources. + +Let $k_{1}^{(l)}$ and $k_{2}^{(l)}$ be the indices which identify the strongest coefficient of layer $l$ , for $i = i_{1,8,l}$ , i.e., the element of $p_{l,i}$ , where the indices $k_{1}^{(l)}, k_{2}^{(l)}$ are such that $p_{l,i} = 1$ . The codebook indices of $i_{1,5}$ are remapped with respect to $i_{1,8,l}$ as $i'_{1,5}$ , such that $i'_{1,5} = 0$ , after remapping. The index $i_{1,6}$ is remapped with respect to $i_{1,8,l}$ as $i'_{1,6}$ , such that the index of the strongest coefficient is $i'_{1,6} = 0$ , for each layer $l$ , after remapping. The indices of $i_{2,3,l}$ , $i_{2,4,l}$ and $i_{2,5,l}$ indicate amplitude coefficients, phase coefficients and bitmap after remapping. + +The strongest coefficient of layer $l$ is identified by $i_{1,8,l}$ + +and is obtained as follows, where, for $i = i_{1,8,l}$ , $a_{l,i} = 1$ , $\phi_{l,i} = 0$ and index $k^{(l)}$ is such that $c_{l,i} = 1$ + +The amplitude and phase coefficient indicators are reported as follows: + +- $i_{1,8,l}$ , $i_{2,3,l}$ , $i_{2,4,l}$ and $i_{2,5,l}$ , for $l = 1, \dots, \nu$ . The reference amplitude, $a_{l,i} = 1$ , amplitude coefficient, $c_{l,i} = 1$ and phase coefficient, $\phi_{l,i} = 0$ , are not reported for $i = i_{1,8,l}$ . +- The reference amplitude, $a_{l,i}$ , is reported for $i \neq i_{1,8,l}$ . +- The amplitude coefficients, $c_{l,i}$ , for which $i \neq i_{1,8,l}$ , $k^{(l)} \neq k_{strongest}^{(l)}$ , are reported. +- The phase coefficients, $\phi_{l,i}$ , for which $i \neq i_{1,8,l}$ , $k^{(l)} \neq k_{strongest}^{(l)}$ , are reported. +- The remaining amplitude coefficients, $c_{l,i}$ , are not reported. +- The remaining phase coefficients, $\phi_{l,i}$ , are not reported. + +The codebooks for 1-4 layers are given in Table 5.2.2.2.8-4, where $W_{l}$ , is the index associated with the precoding matrix, $l$ is the layer index, and where, for coefficients with $k^{(l)}$ , amplitude and phase are set to zero, i.e., $a_{l,i} = 0$ and $\phi_{l,i} = 0$ . + +**Table 5.2.2.2.8-4: Codebook for 1-layer, 2-layer, 3-layer and 4-layer CSI reporting using antenna ports 3000 to 2999+PCSI-RS of selected CSI-RS resources** + +| Layers | | +|---------------|--| +|---------------|--| + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------| +| | | +| | | +| | | +| | | +| | | +| Where | | +| | $W = W_1 \tilde{W}_2$ , $\tilde{W}_2 = W_2 C$ | +| and the mappings from $v$ to $p, L, M, N_1, N_2, q_1, q_2, n_1, n_2$ and from $v$ to $k_1, k_2, \Delta_1, \Delta_2, \phi_n, \theta_p, \gamma_{l,m,i}, g_{l,m,i}, \beta_{l,m,i}$ are as described above, including the ranges of the constituent indices of $W_1$ and $W_2$ . | | + +The bitmap parameter *n1-n2-codebookSubsetRestriction-CJT-r18* is configured per CSI-RS resource and for at least one of the CSI-RS resources, and it is configured as described in Clause 5.2.2.2.5, where only the bit values '00' or '11' of Table 5.2.2.2.5-6 are configurable. If parameter *n1-n2-codebookSubsetRestriction-CJT-r18* is not configured for a CSI-RS resource, no restriction is applied to the selection of vectors corresponding to that resource. + +##### 5.2.2.2.9 Further enhanced Type II port selection codebook for CJT + +For 4 antenna ports {3000, 3001, ..., 3003}, 8 antenna ports {3000, 3001, ..., 3007}, 12 antenna ports {3000, 3001, ..., 3011}, 16 antenna ports {3000, 3001, ..., 3015}, 24 antenna ports {3000, 3001, ..., 3023}, and 32 antenna ports {3000, 3001, ..., 3031} per CSI-RS resource, the UE configured with CSI-RS resources in a resource set for channel measurement and with higher layer parameter *codebookType* set to 'typeII-CJT-PortSelection-r18' + +- the number of CSI-RS ports for each CSI-RS resource, $P_{CSI-RS,r}$ , is configured as in clause 5.2.2.2.4. + +A set of combinations of values of $\alpha$ is configured by the higher layer parameter *paramCombination-CJT-PS-alpha-r18*, where the value of $M$ is configured by the higher layer parameter *numberOfSDCombinations-PS* and the mapping is given in Table 5.2.2.2.9-1, with the value of $\alpha_r$ corresponding to CSI-RS resource $r$ , for $r=1, \dots, R$ . A single value of $L$ and $\beta$ is configured by the higher layer parameter *paramCombination-CJT-PS-r18*, where the mapping is given in Table 5.2.2.2.9-2. The configurable combinations of $L$ and $\beta$ are marked with 'x' in Table 5.2.2.2.9-3. + +- The UE is not expected to be configured with *paramCombination-CJT-PS-alpha-r18* equal to + - 2 for $L=4$ for $v \in \{2, 3, 4\}$ for when $R=1$ , + - 3 for $L=5$ for $L=8$ for $v=4$ for when *paramCombination-CJT-PS-r18* is configured to 4 or 5 and $R=1$ , + - 1 for $L \in \{1, 2, 3\}$ for $M \in \{1, 2, 3, 4, 5, 6, 7\}$ for $v \in \{1, 2, 3\}$ for when $R=1$ and higher layer parameter *typeII-CJT-PS-RI-Restriction-r18* is configured with $r_i=0$ for any $i > v$ . +- If $R > 1$ , the UE is expected to select one of the configured combinations of $\alpha$ and report the index of the selected combination, where the index value 0 corresponds to the first configured combination and the index value $i$ corresponds to the $(i+1)$ -th configured combination. If $R=1$ , a single combination of $\alpha$ is configured and the selection is not reported. + +**Table 5.2.2.2.9-1: Codebook parameter configurations for $\alpha$** + +| $R$ | paramCombination-CJT-PS-alpha-r18 | $\alpha$ | +|-----|------------------------------------------|------------| +| 1 | 1 | {1/2} | +| | 2 | {3/4} | +| | 3 | {1} | +| 2 | 1 | {1/2, 1/2} | + +| | | | +|---|---|-------------------| +| | 2 | {1/2,1} | +| | 3 | {1,1/2} | +| | 4 | {3/4,3/4} | +| | 5 | {1,1} | +| 3 | 1 | {1/2,1/2,1/2} | +| | 2 | {1/2,1/2,3/4} | +| | 3 | {1/2,3/4,1/2} | +| | 4 | {3/4,1/2,1/2} | +| | 5 | {1/2,1/2,1} | +| | 6 | {1/2,1,1/2} | +| | 7 | {1,1/2,1/2} | +| | 8 | {1,1,1} | +| 4 | 1 | {1/2,1/2,1/2,1/2} | +| | 2 | {1/2,1/2,1/2,1} | +| | 3 | {1/2,1/2,1,1} | +| | 4 | {1,1,1,1} | + +Table 5.2.2.2.9-2: Codebook parameter configurations for + +| paramCombination-CJT-PS-r18 | | | +|------------------------------------|---|-------| +| 1 | 1 | $1/2$ | +| 2 | 1 | $3/4$ | +| 3 | 1 | 1 | +| 4 | 2 | $1/2$ | +| 5 | 2 | $3/4$ | + +Table 5.2.2.2.9-3: Configurable combinations of and + +| | paramCombination-CJT-PS-alpha-r18 | paramCombination-CJT-PS-r18 | | | | | +|---|------------------------------------------|------------------------------------|---|---|---|---| +| | | 1 | 2 | 3 | 4 | 5 | +| 1 | 1 | | | | x | | +| | 2 | x | | | x | | +| | 3 | x | x | x | x | x | +| 2 | 1 | x | | | x | | +| | 2 | x | | | | | +| | 3 | x | | | | | +| | 4 | | x | | | | +| | 5 | | x | | x | | +| 3 | 1 | x | | | x | | +| | 2 | x | | | | | +| | 3 | x | | | | | +| | 4 | x | | | | | +| | 5 | | x | | x | | + +| | | | | | | | +|---|---|---|---|---|---|---| +| 4 | 6 | | X | | X | | +| | 7 | | X | | X | | +| | 8 | | X | | | X | +| | 1 | X | | | | | +| | 2 | X | | | | | +| | 3 | | X | X | X | | +| | 4 | | | X | | | +| | | | | | | | + +- The value of $\text{valueOfN-CJT-r18}$ is configured with the higher-layer parameter $\text{valueOfN-CJT-r18}$ , when $\text{typeII-CJT-PS-RI-Restriction-r18}$ is configured. +- The value of $\text{numberOfPMI-SubbandsPerCQI-Subband-CJT-PS-r18}$ is configured with the higher-layer parameter $\text{numberOfPMI-SubbandsPerCQI-Subband-CJT-PS-r18}$ , when $\text{typeII-CJT-PS-RI-Restriction-r18}$ is configured, and $\text{typeII-CJT-PS-RI-Restriction-r18}$ is configured, where $\text{typeII-CJT-PS-RI-Restriction-r18}$ and the corresponding value of $\text{numberOfPMI-SubbandsPerCQI-Subband-CJT-PS-r18}$ are defined as in clause 5.2.2.2.5. +- The UE shall report the RI value according to the configured higher layer parameter $\text{typeII-CJT-PS-RI-Restriction-r18}$ . The UE shall not report $\text{typeII-CJT-PS-RI-Restriction-r18}$ . The bitmap parameter $\text{typeII-CJT-PS-RI-Restriction-r18}$ forms the bit sequence $\text{typeII-CJT-PS-RI-Restriction-r18}$ , where $\text{typeII-CJT-PS-RI-Restriction-r18}$ is the LSB and $\text{typeII-CJT-PS-RI-Restriction-r18}$ is the MSB. When $\text{typeII-CJT-PS-RI-Restriction-r18}$ is zero, $\text{typeII-CJT-PS-RI-Restriction-r18}$ , PMI and RI reporting are not allowed to correspond to any precoder associated with layers. +- The UE may be configured with higher layer parameter $\text{restrictedCMR-Selection}$ . If $\text{restrictedCMR-Selection}$ is configured, the number of selected CSI-RS resources is $\text{restrictedCMR-Selection}$ . Otherwise, the UE is expected to select $\text{typeII-CJT-PS-RI-Restriction-r18}$ CSI-RS resources, with $\text{typeII-CJT-PS-RI-Restriction-r18}$ , and the selection is reported with an $\text{typeII-CJT-PS-RI-Restriction-r18}$ -bit bitmap, $\text{typeII-CJT-PS-RI-Restriction-r18}$ , where the CSI-RS resources are mapped from bit to bit by their ordering in the resource set and the first of the selected CSI-RS resources corresponds to the nonzero bit with lowest index. + +The PMI value for the selected CSI-RS resources corresponds to the codebook indices of $\text{typeII-CJT-PS-RI-Restriction-r18}$ and $\text{typeII-CJT-PS-RI-Restriction-r18}$ where + +The precoding matrices indicated by the PMI are determined from vectors, where $\text{typeII-CJT-PS-RI-Restriction-r18}$ are the indices of the selected CSI-RS resources in increasing order, such that $\text{typeII-CJT-PS-RI-Restriction-r18}$ , and $\text{typeII-CJT-PS-RI-Restriction-r18}$ , where $\text{typeII-CJT-PS-RI-Restriction-r18}$ are the corresponding values from the selected combination of $\text{typeII-CJT-PS-RI-Restriction-r18}$ . + +$\text{typeII-CJT-PS-RI-Restriction-r18}$ ports are selected from the ports of the $\text{typeII-CJT-PS-RI-Restriction-r18}$ -th selected CSI-RS resource, for $\text{typeII-CJT-PS-RI-Restriction-r18}$ , based on vectors, $\text{typeII-CJT-PS-RI-Restriction-r18}$ , which are indicated by $\text{typeII-CJT-PS-RI-Restriction-r18}$ , where + +Let + +the index $\text{typeII-CJT-PS-RI-Restriction-r18}$ , for the $\text{typeII-CJT-PS-RI-Restriction-r18}$ -th selected CSI-RS resource, is obtained from the elements of $\text{typeII-CJT-PS-RI-Restriction-r18}$ , as described in Clause 5.2.2.2.7 for the indicator $\text{typeII-CJT-PS-RI-Restriction-r18}$ , obtained from the elements of $\text{typeII-CJT-PS-RI-Restriction-r18}$ . Vector $\text{typeII-CJT-PS-RI-Restriction-r18}$ is a $\text{typeII-CJT-PS-RI-Restriction-r18}$ -element column vector containing a value of 1 in the element of index $\text{typeII-CJT-PS-RI-Restriction-r18}$ and zeros elsewhere, and where the first element is the element of index 0. + +- If for the $\text{typeII-CJT-PS-RI-Restriction-r18}$ -th selected CSI-RS resource, $\text{typeII-CJT-PS-RI-Restriction-r18}$ , for $\text{typeII-CJT-PS-RI-Restriction-r18}$ , and $\text{typeII-CJT-PS-RI-Restriction-r18}$ is not reported. + +The vectors, $\text{typeII-CJT-PS-RI-Restriction-r18}$ , are common for all the selected CSI-RS resources and are identified by $\text{typeII-CJT-PS-RI-Restriction-r18}$ , where + +with the indices assigned such that $\text{typeII-CJT-PS-RI-Restriction-r18}$ increases with $\text{typeII-CJT-PS-RI-Restriction-r18}$ . $\text{typeII-CJT-PS-RI-Restriction-r18}$ is indicated by the index $\text{typeII-CJT-PS-RI-Restriction-r18}$ , when $\text{typeII-CJT-PS-RI-Restriction-r18}$ and $\text{typeII-CJT-PS-RI-Restriction-r18}$ , where + +- If $\delta_{CSI}$ , or $\delta_{CSI}^{ref}$ and $\delta_{CSI}^{ref}$ , is not reported. +- If $\delta_{CSI}$ and $\delta_{CSI}^{ref}$ , the nonzero offset between $\delta_{CSI}$ and $\delta_{CSI}^{ref}$ is reported with assuming that $\delta_{CSI}^{ref}$ (reference for the offset) is 0. The nonzero offset values are mapped to the index values of $\delta_{CSI}$ in increasing order with offset value 1 mapped to index value '0'. + +The vectors' elements are given by + +for $\delta_{CSI}$ , and $\delta_{CSI}^{ref}$ . + +If the higher layer parameter *codebookMode* is set to 'mode1', an offset $\delta_{CSI}$ is reported for the $\delta_{CSI}$ -th selected CSI-RS resource, with $\delta_{CSI}$ , relative to the first of the $\delta_{CSI}$ selected CSI-RS resources. The reported offsets are common for all layers and are indicated by $\delta_{CSI}$ , given by + +where the value of $\delta_{CSI}$ is configured by higher layer parameter *numberOfO3*. The offsets are represented by + +If *codebookMode* is set to 'mode2', the offset indicator, $\delta_{CSI}$ , is not reported and $\delta_{CSI}^{ref}$ for $\delta_{CSI}$ . + +The reference amplitude coefficient indicator, $\delta_{CSI}$ , for layer $\delta_{CSI}$ , is given by + +The reference amplitude coefficients for layer $\delta_{CSI}$ are represented by + +and the mapping from $\delta_{CSI}$ to $\delta_{CSI}$ is given in Table 5.2.2.2.5-2. + +The amplitude coefficient indicator, $\delta_{CSI}$ , for layer $\delta_{CSI}$ , is given by + +The amplitude coefficients for layer $\delta_{CSI}$ are represented by + +and the mapping from $\delta_{CSI}$ to $\delta_{CSI}$ is given in Table 5.2.2.2.5-3. + +The phase coefficient indicator, $\delta_{CSI}$ , for $\delta_{CSI}$ , is given by + +The phase coefficients for layer $l$ are represented by $\phi_{l,i,f}$ + +and the mapping from $i$ to $k$ is given by $k = f \cdot N_1 N_2 + i$ + +Let $K = N_1 N_2 N_3$ . The bitmap whose nonzero bits identify which coefficients in $\mathbf{a}_l$ and $\mathbf{\phi}_l$ are reported for layer $l$ , is indicated by $\mathbf{v}_l$ + +Let $K_{l,NZ}$ be the number of nonzero coefficients for layer $l$ , the total number of nonzero coefficients is reported and given by $K_{NZ} = \sum_{l=1}^{\nu} K_{l,NZ}$ . + +- If $N_3 = 1$ and $M = 1$ , $K_{l,NZ}$ is not reported, for $l=1, \dots, \nu$ . + +The indices of $i$ , $f$ and $k$ are associated to the selected CSI-RS resources. + +Let $i^*$ and $f^*$ be the indices which identify the strongest coefficient of layer $l$ , for $l=1, \dots, \nu$ , i.e., the element of $\mathbf{a}_l$ , where the indices $i, f$ are such that $a_{l,i,f} \le a_{l,i^*,f^*} = 1$ . The strongest coefficient of layer $l$ is identified by the index $k^*$ + +which is found from $k^* = f^* \cdot N_1 N_2 + i^*$ + +The amplitude and phase coefficient indicators are reported as follows: + +- $i=i^*$ , $f=f^*$ , and $k=k^*$ , for $l=1, \dots, \nu$ . The reference amplitude, $a_{l,i^*,f^*}$ , amplitude coefficient, and phase coefficient, $\phi_{l,i^*,f^*}$ , are not reported for $k=k^*$ . +- The reference amplitude, $a_{l,i^*,f^*}$ , is reported for $k=k^*$ . +- The amplitude coefficients, $a_{l,i,f}$ , for which $v_{l,k} = 1$ , $k \ne k^*$ , are reported. +- The phase coefficients, $\phi_{l,i,f}$ , for which $v_{l,k} = 1$ , $k \ne k^*$ , are reported. +- The remaining amplitude coefficients, $a_{l,i,f}$ , are not reported. +- The remaining phase coefficients, $\phi_{l,i,f}$ , are not reported. + +The codebooks for 1-4 layers are given in Table 5.2.2.9-4, where $W_{l,i,f}$ is the index associated with the precoding matrix, $l$ is the layer index, and where, for coefficients with $v_{l,k} = 0$ , amplitude and phase are set to zero, i.e., $a_{l,i,f} = 0$ and $\phi_{l,i,f} = 0$ . + +**Table 5.2.2.9-4: Codebook for 1-layer, 2-layer, 3-layer and 4-layer CSI reporting using antenna ports 3000 to 2999+PCSI-RS of selected CSI-RS resources** + +| Layers | | +|---------------|--| +|---------------|--| + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | +| | | +| | | +| | | +|

Where

and the mappings from to , and from to , , , , , , , , are as described above, including the ranges of the constituent indices of and .

| | + +##### 5.2.2.2.10 Enhanced Type II codebook for predicted PMI + +For 4 antenna ports {3000, 3001, ..., 3003}, 8 antenna ports {3000, 3001, ..., 3007}, 12 antenna ports {3000, 3001, ..., 3011}, 16 antenna ports {3000, 3001, ..., 3015}, 24 antenna ports {3000, 3001, ..., 3023}, and 32 antenna ports {3000, 3001, ..., 3031} per CSI-RS resource, the UE configured with aperiodic CSI-RS resources or with a single periodic or semi-persistent CSI-RS resource in the resource set for channel measurement and with *codebookType* set to 'typeII-Doppler-r18' + +- The values of $\hat{r}$ and $\hat{s}$ are configured with the higher layer parameter *n1-n2-codebookSubsetRestriction-Doppler-r18*. The supported configurations of $\hat{r}$ for a given number of CSI-RS ports and the corresponding values of $\hat{s}$ are given in Table 5.2.2.2.1-2. The number of CSI-RS ports, $\hat{r}$ , is . +- The values of $\hat{r}$ , and $\hat{s}$ are determined by the higher layer parameter *paramCombination-Doppler-r18*, where the mapping is given in Table 5.2.2.2.10-1. +- The UE is not expected to be configured with *paramCombination-Doppler-r18* equal to + - 4, 5, 6, 7, 8, or 9 when $\hat{r}$ , + - 8 or 9 when $\hat{s}$ + - 8 or 9 when higher layer parameter *typeII-Doppler-RI-Restriction-r18* is configured with $\hat{r}$ for any . + - 8 or 9 when . + +**Table 5.2.2.2.10-1: Codebook parameter configurations for $\hat{r}$ and $\hat{s}$** + +| paramCombination-Doppler-r18 | $\hat{r}$ | $\hat{s}$ | | $\hat{s}$ | +|-------------------------------------|-----------|-----------|-----------|-----------| +| | | $\hat{s}$ | $\hat{s}$ | | +| 1 | 2 | 1/8 | 1/16 | 1/4 | +| 2 | 2 | 1/4 | 1/8 | 1/2 | +| 3 | 4 | 1/4 | 1/8 | 1/4 | +| 4 | 4 | 1/4 | 1/4 | 1/4 | +| 5 | 4 | 1/4 | 1/4 | 1/2 | +| 6 | 4 | 1/4 | 1/4 | 3/4 | +| 7 | 4 | 1/2 | 1/4 | 1/2 | +| 8 | 6 | 1/4 | - | 1/2 | + +| | | | | | +|---|---|---------------|---|---------------| +| | | | | | +| 9 | 6 | $\frac{1}{4}$ | - | $\frac{3}{4}$ | + +- The value of $\text{numberOfPMI-SubbandsPerCQI-Subband-Doppler-r18}$ is configured with the higher-layer parameter *numberOfPMI-SubbandsPerCQI-Subband-Doppler-r18*, where $\text{numberOfPMI-SubbandsPerCQI-Subband-Doppler-r18}$ and the corresponding value of $\text{numberOfPMI-SubbandsPerCQI-Subband-Doppler-r18}$ are defined as in clause 5.2.2.2.5. +- The UE shall report the RI value according to the configured higher layer parameter *typeII-Doppler-RI-Restriction-r18*. The UE shall not report $\text{typeII-Doppler-RI-Restriction-r18}$ . The bitmap parameter *typeII-Doppler-RI-Restriction-r18* forms the bit sequence where $\text{typeII-Doppler-RI-Restriction-r18}$ is the LSB and $\text{typeII-Doppler-RI-Restriction-r18}$ is the MSB. When $\text{typeII-Doppler-RI-Restriction-r18}$ is zero, $\text{typeII-Doppler-RI-Restriction-r18}$ , PMI and RI reporting are not allowed to correspond to any precoder associated with layers. +- The value of $\text{N4}$ is configured by the higher layer parameter *N4*, such that the PMI indicates precoder matrices for each of the consecutive slot intervals of duration $\text{N4}$ slots, as defined in Clause 5.2.1.4.2. + +If $\text{typeII-Doppler-RI-Restriction-r18}$ is zero, the PMI value corresponds to the codebook indices of $\text{typeII-Doppler-RI-Restriction-r18}$ and $\text{typeII-Doppler-RI-Restriction-r18}$ as described in Clause 5.2.2.2.5 and the precoder matrices for 1-4 layers are obtained from the PMI codebook as in Table 5.2.2.2.5-5. + +If $\text{typeII-Doppler-RI-Restriction-r18}$ is not zero, the PMI value corresponds to the codebook indices of $\text{typeII-Doppler-RI-Restriction-r18}$ and $\text{typeII-Doppler-RI-Restriction-r18}$ , where + +The precoding matrices indicated by the PMI are determined from vectors, where $\text{typeII-Doppler-RI-Restriction-r18}$ . + +The vectors, $\text{typeII-Doppler-RI-Restriction-r18}$ , indicated by $\text{typeII-Doppler-RI-Restriction-r18}$ , and the vectors, $\text{typeII-Doppler-RI-Restriction-r18}$ , for layer $\text{typeII-Doppler-RI-Restriction-r18}$ , indicated by $\text{typeII-Doppler-RI-Restriction-r18}$ (for $\text{typeII-Doppler-RI-Restriction-r18}$ ) and $\text{typeII-Doppler-RI-Restriction-r18}$ , are obtained as in Clause 5.2.2.2.5. + +The vectors, $\text{typeII-Doppler-RI-Restriction-r18}$ , for layer $\text{typeII-Doppler-RI-Restriction-r18}$ are identified by $\text{typeII-Doppler-RI-Restriction-r18}$ , where + +with the indices assigned such that $\text{typeII-Doppler-RI-Restriction-r18}$ increases with $\text{typeII-Doppler-RI-Restriction-r18}$ . $\text{typeII-Doppler-RI-Restriction-r18}$ is indicated by the index $\text{typeII-Doppler-RI-Restriction-r18}$ , for layer $\text{typeII-Doppler-RI-Restriction-r18}$ , where + +- If $\text{typeII-Doppler-RI-Restriction-r18}$ , for layer $\text{typeII-Doppler-RI-Restriction-r18}$ are not reported. +- If $\text{typeII-Doppler-RI-Restriction-r18}$ , the nonzero offset between $\text{typeII-Doppler-RI-Restriction-r18}$ and $\text{typeII-Doppler-RI-Restriction-r18}$ is reported with $\text{typeII-Doppler-RI-Restriction-r18}$ assuming that (reference for the offset) is 0. The nonzero offset values are mapped to the index values of $\text{typeII-Doppler-RI-Restriction-r18}$ in increasing order with offset value 1 mapped to index value '0'. + +The vectors' elements are given by + +for $\text{typeII-Doppler-RI-Restriction-r18}$ , and $\text{typeII-Doppler-RI-Restriction-r18}$ . + +The reference amplitude coefficient indicator, for layer $\text{typeII-Doppler-RI-Restriction-r18}$ , is given by + +The reference amplitude coefficients for layer $\text{typeII-Doppler-RI-Restriction-r18}$ are represented by + +and the mapping from $\text{typeII-Doppler-RI-Restriction-r18}$ to $\text{typeII-Doppler-RI-Restriction-r18}$ is given in Table 5.2.2.2.5-2. + +The amplitude coefficient indicator, for layer $\text{typeII-Doppler-RI-Restriction-r18}$ , is given by + +The amplitude coefficients for layer are represented by + +and the mapping from to is given in Table 5.2.2.2.5-3. + +The phase coefficient indicator, for, is given by + +The phase coefficients for layer are represented by + +and the mapping from to is given by + +Let. The bitmap whose nonzero bits identify which coefficients in and are reported for layer, is indicated by + +Let be the number of nonzero coefficients for layer, the total number of nonzero coefficients is reported and given by. + +The indices of, and are associated to the codebook indices in. + +Let, and be the indices which identify the strongest coefficient of layer, for, i.e., the element of. The codebook indices of are remapped with respect to as, such that, after remapping. The index is remapped with respect to as, such that the index of the strongest coefficient is (), after remapping. The indices of, and indicate amplitude coefficients, phase coefficients and bitmap after remapping. + +The strongest coefficient of layer is identified by, which is obtained as follows, where, for, and index is such that + +The amplitude and phase coefficient indicators are reported as follows: + +- , , and , for. The reference amplitude, , amplitude coefficient, and phase coefficient, , are not reported for. +- The reference amplitude, , is reported for. +- The amplitude coefficients, , for which , , are reported. +- The phase coefficients, , for which , are reported. +- The remaining amplitude coefficients, , are not reported. + +- The remaining phase coefficients, $\phi_{l,i,j,k}$ , are not reported. + +The codebooks for 1-4 layers are given in Table 5.2.2.2.10-2, where $l$ are the indices associated with the precoding matrix, $l$ is the layer index, and where, for coefficients with $l > 4$ , amplitude and phase are set to zero, i.e., $a_{l,i,j,k} = 0$ and $\phi_{l,i,j,k} = 0$ . + +**Table 5.2.2.2.10-2: Codebook for 1-layer, 2-layer, 3-layer and 4-layer CSI reporting using antenna ports 3000 to 2999+ $P_{CSI-RS}$** + +| Layers | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | +| | | +| | | +| | | +|

Where

and the mappings from l to l', i to i', j to j', and from k to k', are as described above, including the ranges of the constituent indices of l and l'.

| | + +The bitmap parameter *n1-n2-codebookSubsetRestriction-Doppler-r18* is configured as described in Clause 5.2.2.2.5, where only the bit values '00' or '11' of Table 5.2.2.2.5-6 are configurable. + +##### 5.2.2.2.11 Further enhanced Type II port selection codebook for predicted PMI + +For 4 antenna ports {3000, 3001, ..., 3003}, 8 antenna ports {3000, 3001, ..., 3007}, 12 antenna ports {3000, 3001, ..., 3011}, 16 antenna ports {3000, 3001, ..., 3015}, 24 antenna ports {3000, 3001, ..., 3023}, and 32 antenna ports {3000, 3001, ..., 3031} per CSI-RS resource, the UE configured with aperiodic CSI-RS resources or with a single periodic or semi-persistent CSI-RS resource in the resource set for channel measurement and with *codebookType* set to 'typeII-Doppler-PortSelection-r18' + +- the number of CSI-RS ports, $P$ , is configured as in clause 5.2.2.2.4. +- The values $n_1$ and $n_2$ are determined by the higher layer parameter *paramCombination-Doppler-PS-r18*, where the mapping is given in Table 5.2.2.2.7-1 and the applicable configuration restrictions are described in Clause 5.2.2.2.7. +- The parameter $n_1$ is configured with the higher-layer parameter *valueOfN-Doppler-r18*, when $n_1 > 0$ . +- The parameter $n_2$ is configured with the higher-layer parameter *numberOfPMI-SubbandsPerCQI-Subband-Doppler-PS-r18*, when $n_2 > 0$ and when $n_1 > 0$ , where $n_1$ and the corresponding value of parameter $n_2$ are defined as in clause 5.2.2.2.5. +- The UE shall report the RI value according to the configured higher layer parameter *typeII-Doppler-PS-RI-Restriction-r18*. The UE shall not report RI when $n_1 = 0$ . The bitmap parameter *typeII-Doppler-RI-Restriction-r18* forms the bit sequence where $b_0$ is the LSB and $b_{n_1-1}$ is the MSB. When $n_1$ is zero, PMI and RI reporting are not allowed to correspond to any precoder associated with layers. + +- The value of $N_4$ is configured by the higher layer parameter $N_4$ , such that the PMI indicates precoder matrices for one slot interval of duration $N_4$ slots, as defined in Clause 5.2.1.4.2. + +The PMI value corresponds to the codebook indices of $N_4$ and $N_5$ as described in Clause 5.2.2.2.7 and the precoder matrices for 1-4 layers are obtained from the PMI codebook as in Table 5.2.2.2.7-3. + +#### 5.2.2.3 Reference signal (CSI-RS) + +##### 5.2.2.3.1 NZP CSI-RS + +The UE can be configured with one or more NZP CSI-RS resource set configuration(s) as indicated by the higher layer parameters *CSI-ResourceConfig*, and *NZP-CSI-RS-ResourceSet*. Each NZP CSI-RS resource set consists of $K \geq 1$ NZP CSI-RS resource(s). + +The following parameters for which the UE shall assume non-zero transmission power for CSI-RS resource are configured via the higher layer parameter *NZP-CSI-RS-Resource*, *CSI-ResourceConfig* and *NZP-CSI-RS-ResourceSet* for each CSI-RS resource configuration: + +- *nzp-CSI-RS-ResourceId* determines CSI-RS resource configuration identity. +- *periodicityAndOffset* defines the CSI-RS periodicity and slot offset for periodic/semi-persistent CSI-RS. All the CSI-RS resources within one set are configured with the same periodicity, while the slot offset can be same or different for different CSI-RS resources. +- *resourceMapping* defines the number of ports, CDM-type, and OFDM symbol and subcarrier occupancy of the CSI-RS resource within a slot that are given in Clause 7.4.1.5 of [4, TS 38.211]. +- *nrofPorts* in *resourceMapping* defines the number of CSI-RS ports, where the allowable values are given in Clause 7.4.1.5 of [4, TS 38.211]. +- *density* in *resourceMapping* defines CSI-RS frequency density of each CSI-RS port per PRB, and CSI-RS PRB offset in case of the density value of 1/2, where the allowable values are given in Clause 7.4.1.5 of [4, TS 38.211]. For density 1/2, the odd/even PRB allocation indicated in *density* is with respect to the common resource block grid. +- *cdm-Type* in *resourceMapping* defines CDM values and pattern, where the allowable values are given in Clause 7.4.1.5 of [4, TS 38.211]. +- *powerControlOffset*: which is the assumed ratio of PDSCH EPRE to NZP CSI-RS EPRE when UE derives CSI feedback and takes values in the range of [-8, 15] dB with 1 dB step size. For CQI calculation based on a pair of NZP CSI-RS resources, *powerControlOffset* of each NZP CSI-RS resource in the pair of NZP CSI-RS resources for channel measurement is the assumed ratio of EPRE when UE derives CSI feedback and takes values in the range of [-8, 15] dB with 1 dB step size. +- *powerControlOffsetSS*: which is the assumed ratio of NZP CSI-RS EPRE to SS/PBCH block EPRE. +- *scramblingID* defines scrambling ID of CSI-RS with length of 10 bits. +- *BWP-Id* in *CSI-ResourceConfig* defines which bandwidth part the configured CSI-RS is located in. +- *repetition* in *NZP-CSI-RS-ResourceSet* is associated with a CSI-RS resource set and defines whether UE can assume the CSI-RS resources within the NZP CSI-RS Resource Set are transmitted with the same downlink spatial domain transmission filter or not as described in Clause 5.1.6.1.2. and can be configured only when the higher layer parameter *reportQuantity* associated with all the reporting settings linked with the CSI-RS resource set is set to 'cri-RSRP', 'cri-SINR', 'cri-RSRP- Index', 'cri-SINR- Index' or 'none'. +- *qcl-InfoPeriodicCSI-RS* contains a reference to a *TCI-State* indicating QCL source RS(s) and QCL type(s). If the *TCI-State* is configured with a reference to an RS configured with *qcl-Type* set to 'typeD' association, that RS may be an SS/PBCH block located in the same or different CC/DL BWP or a CSI-RS resource configured as periodic located in the same or different CC/DL BWP. The reference RS may additionally be an SS/PBCH block associated with a PCI different from the PCI of the serving cell. +- *trs-Info* in *NZP-CSI-RS-ResourceSet* is associated with a CSI-RS resource set and for which the UE can assume that the antenna port with the same port index of the configured NZP CSI-RS resources in the *NZP-CSI-RS-ResourceSet* is the same as described in Clause 5.1.6.1.1 and can be configured when reporting setting is not + +configured or when the higher layer parameter *reportQuantity* associated with all the reporting settings linked with the CSI-RS resource set is set to 'tdcp' or 'none'. + +All CSI-RS resources within one set are configured with same *density* and same *nrofPorts*, except for the NZP CSI-RS resources used for interference measurement. + +The UE expects that all the CSI-RS resources of a resource set are configured with the same starting RB and number of RBs and the same *cdm-type*. + +For a CSI-RS Resource Set for channel measurement configured with two Resource Groups and Resource Pairs, the slot offsets of the two resources in a Resource Pair are configured within slots, without DL/UL switching in between the two resources, where implies that the two resources are configured in the same slot, and implies that the two resources are configured within two adjacent slots. + +For a *NZP-CSI-RS-ResourceSet* for channel measurement with resources and linked to a *CSI-ReportConfig* configured with *codebookType* set to 'typeII-CJT-r18' or 'typeII-CJT-PortSelection-r18', the slot offsets of the CSI-RS resources are configured within slots, without DL/UL switching in between the two resources, where implies that the resources are configured in the same slot, and implies that the resources are configured within two adjacent slots. + +The bandwidth and initial common resource block (CRB) index of a CSI-RS resource within a BWP, as defined in Clause 7.4.1.5 of [4, TS 38.211], are determined based on the higher layer parameters *nrofRBs* and *startingRB*, respectively, within the CSI-FrequencyOccupation IE configured by the higher layer parameter *freqBand* within the *CSI-RS-ResourceMapping* IE. Both *nrofRBs* and *startingRB* are configured as integer multiples of 4 RBs, and the reference point for *startingRB* is CRB 0 on the common resource block grid. If the UE shall assume that the initial CRB index of the CSI-RS resource is , otherwise . If , the UE shall assume that the bandwidth of the CSI-RS resource is , otherwise . In all cases, the UE shall expect that . + +#### 5.2.2.4 Channel State Information – Interference Measurement (CSI-IM) + +The UE can be configured with one or more CSI-IM resource set configuration(s) as indicated by the higher layer parameter *CSI-IM-ResourceSet*. Each CSI-IM resource set consists of $K \geq 1$ CSI-IM resource(s). + +The following parameters are configured via higher layer parameter *CSI-IM-Resource* for each CSI-IM resource configuration: + +- *csi-IM-ResourceId* determines CSI-IM resource configuration identity +- *subcarrierLocation-p0* or *subcarrierLocation-p1* defines subcarrier occupancy of the CSI-IM resource within a slot for *csi-IM-ResourceElementPattern* set to 'pattern0' or 'pattern1', respectively. +- *symbolLocation-p0* or *symbolLocation-p1* defines OFDM symbol location of the CSI-IM resource within a slot for *csi-IM-ResourceElementPattern* set to 'pattern0' or 'pattern1', respectively. +- *periodicityAndOffset* defines the CSI-IM periodicity and slot offset for periodic/semi-persistent CSI-IM. +- *freqBand* includes parameters to enable configuration of frequency-occupancy of CSI-IM + +In each of the PRBs configured by *freqBand*, the UE shall assume each CSI-IM resource is located in, + +- resource elements , , and , if *csi-IM-ResourceElementPattern* is set to 'pattern0', +- resource elements , , and if *csi-IM-ResourceElementPattern* is set to 'pattern1', + +where and are the configured frequency-domain location and time-domain location, respectively, given by the higher layer parameters in the above list. + +#### 5.2.2.5 CSI reference resource definition + +The CSI reference resource for a serving cell is defined as follows: + +- In the frequency domain, the CSI reference resource is defined by the group of downlink physical resource blocks corresponding to the band to which the derived CSI relates. +- In the time domain, the CSI reference resource for a CSI reporting in uplink slot $n'$ is defined by a single downlink slot , where is a parameter configured by higher layer as specified in clause 4.2 of [6 TS 38.213], and where is the subcarrier spacing configuration for with a value of 0 for frequency range 1, + +- $$n = \left\lceil n' \cdot \frac{2^{\mu_{DL}}}{2^{\mu_{UL}}} \right\rceil$$ +- where $\mu_{DL}$ and $\mu_{UL}$ are the subcarrier spacing configurations for DL and UL, respectively, and $\mu_{offset}$ are determined by higher-layer configured *ca-SlotOffset* for the cells transmitting the uplink and downlink, as defined in clause 4.5 of [4, TS 38.211] + - where for periodic and semi-persistent CSI reporting + - if a single CSI-RS/SSB resource is configured for channel measurement $n_{CSI\_ref}$ is the smallest value greater than or equal to $n'$ , such that it corresponds to a valid downlink slot, or + - if multiple CSI-RS/SSB resources are configured for channel measurement $n_{CSI\_ref}$ is the smallest value greater than or equal to $5 \cdot 2^{\mu_{DL}}$ , such that it corresponds to a valid downlink slot. + - where for aperiodic CSI reporting, if the UE is indicated by the DCI to report CSI in the same slot as the CSI request, $n_{CSI\_ref}$ is such that the reference resource is in the same valid downlink slot as the corresponding CSI request, otherwise $n_{CSI\_ref}$ is the smallest value greater than or equal to $n'$ , such that slot $n - n_{CSI\_ref}$ corresponds to a valid downlink slot, where $Z'$ corresponds to the delay requirement as defined in Clause 5.4. + - when periodic or semi-persistent CSI-RS/CSI-IM or SSB is used for channel/interference measurements, the UE is not expected to measure channel/interference on the CSI-RS/CSI-IM/SSB whose last OFDM symbol is received up to $Z'$ symbols before transmission time of the first OFDM symbol of the aperiodic CSI reporting. + +A slot in a serving cell shall be considered to be a valid downlink slot if: + +- it comprises at least one higher layer configured downlink or flexible symbol, and +- it does not fall within a configured measurement gap for that UE + +If there is no valid downlink slot for the CSI reference resource corresponding to a CSI Report Setting in a serving cell, CSI reporting is omitted for the serving cell in uplink slot $n'$ . + +After the CSI report (re)configuration, serving cell activation, BWP change, or activation of SP-CSI, the UE reports a CSI report only after receiving at least one CSI-RS transmission occasion for channel measurement and CSI-RS and/or CSI-IM occasion for interference measurement no later than CSI reference resource and drops the report otherwise. For a CSI report configuration containing a list of sub-configurations provided by *csi-ReportSubConfigList*, after the CSI report (re)configuration, serving cell activation, BWP change, or activation of SP-CSI, the UE reports a CSI report including one or more sub-reports only after receiving at least one CSI-RS transmission occasion for channel measurement and CSI-RS and/or CSI-IM occasion for interference measurement, per sub-configuration, no later than CSI reference resource and drops the report otherwise, where the sub-configuration is the activated/triggered one for SP-CSI reporting. + +For a *CSI-ReportConfig* configured with two Resource Groups and Resource Pairs for channel measurement in the corresponding CSI-RS Resource Set, as described in clause 5.2.1.4.1, after the CSI report (re)configuration, serving cell activation, BWP change, or activation of SP-CSI, the UE reports a CSI report only after receiving at least one CSI-RS transmission occasion for each of the CSI-RS resources in the corresponding CSI-RS Resource Set for channel measurement no later than the CSI reference resource and within the same DRX Active Time when DRX is configured, and drops the report otherwise. + +For a *CSI-ReportConfig* configured with *codebookType* set to 'typeII-CJT-r18' or 'typeII-CJT-PortSelection-r18', after the CSI report (re)configuration, serving cell activation, BWP change, or activation of SP-CSI, the UE reports a CSI report only after receiving at least one CSI-RS transmission occasion for each of the CSI-RS resources in the corresponding CSI-RS Resource Set for channel measurement and one CSI-RS and/or CSI-IM resource transmission occasion for the CSI-RS and/or CSI-IM resource in the corresponding Resource Set for interference measurement no later than the CSI reference resource and within the same DRX Active Time, when DRX is configured, and drops the report otherwise. + +For a *CSI-ReportConfig* configured with *codebookType* set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18', after the CSI report (re)configuration, serving cell activation, BWP change, or activation of SP-CSI, the UE reports a CSI report only if receiving at least one aperiodic or periodic or semipersistent consecutive CSI-RS transmission occasions for each CSI-RS resource in the corresponding CSI-RS Resource Set for channel measurement and one CSI-RS and/or CSI-IM resource transmission occasion for the CSI-RS and/or CSI-IM resource in the corresponding Resource Set for interference measurement no later than the CSI reference resource and within the same DRX Active + +Time, when DRX is configured, and drops the report otherwise. The value of is indicated by UE capability, as defined in clause 5.2.1.6. + +For a *CSI-ReportConfig* configured with the higher layer parameter *reportQuantity* set to 'tdcp', after the CSI report (re)configuration, serving cell activation, BWP change, the UE reports a CSI report only after receiving at least one CSI-RS transmission occasion for each CSI-RS resource in the CSI-RS Resource Sets of the CSI-RS Resource Setting for channel measurement no later than the CSI reference resource within the same DRX active time, when DRX is configured, and drop the report otherwise. + +When DRX is configured, the UE reports a CSI report only if receiving at least one CSI-RS transmission occasion for channel measurement and CSI-RS and/or CSI-IM occasion for interference measurement in DRX Active Time no later than CSI reference resource and drops the report otherwise. When the UE is configured to monitor DCI format 2\_6 and if the UE configured by higher layer parameter *ps-TransmitOtherPeriodicCSI* to report CSI with the higher layer parameter *reportConfigType* set to 'periodic' and *reportQuantity* set to quantities other than 'cri-RSRP', 'ssb-Index-RSRP', 'cri-RSRP- Index', and 'ssb-Index-RSRP- Index' when *drx-onDurationTimer* is not started, the UE shall report CSI during the time duration indicated by *drx-onDurationTimer* in *DRX-Config* also outside active time according to the procedure described in Clause 5.2.1.4 if receiving at least one CSI-RS transmission occasion for channel measurement and CSI-RS and/or CSI-IM occasion for interference measurement during the time duration indicated by *drx-onDurationTimer* in *DRX-Config* outside DRX active time or in DRX Active Time no later than CSI reference resource and drops the report otherwise. When the UE is configured to monitor DCI format 2\_6 and if the UE configured by higher layer parameter *ps-TransmitPeriodicL1-RSRP* to report L1-RSRP with the higher layer parameter *reportConfigType* set to 'periodic' and *reportQuantity* set to 'cri-RSRP', 'ssb-Index-RSRP', 'cri-RSRP- Index', or 'ssb-Index-RSRP- Index' when *drx-onDurationTimer* is not started, the UE shall report L1-RSRP during the time duration indicated by *drx-onDurationTimer* in *DRX-Config* also outside active time according to the procedure described in clause 5.2.1.4 and when *reportQuantity* set to 'cri-RSRP' or 'cri-RSRP- Index' if receiving at least one CSI-RS transmission occasion for channel measurement during the time duration indicated by *drx-onDurationTimer* in *DRX-Config* outside DRX active time or in DRX Active Time no later than CSI reference resource and drops the report otherwise. + +For the CSI report configuration in *CSI-ReportConfig* associated with the higher layer parameter *reportQuantity* comprising at least 'RI' on a serving cell with cell DTX activated [10, TS 38.321], the UE reports a CSI report only if receiving at least one CSI-RS transmission occasion of each periodic CSI-RS resource or semi-persistent CSI-RS resource for channel measurement and/or interference measurement in active periods of cell DTX no later than CSI reference resource, and the UE drops the CSI report otherwise. + +When deriving CSI feedback, the UE is not expected that a NZP CSI -RS resource for channel measurement overlaps with CSI-IM resource for interference measurement or NZP CSI -RS resource for interference measurement. + +##### 5.2.2.5.1 UE assumptions for CQI/PMI/RI calculation + +If configured to report CQI index, in the CSI reference resource, or in each of the slot(s) associated with a CQI in the predicted CSI, as defined in Clause 5.2.1.4.2, the UE shall assume the following for the purpose of deriving the CQI index, and if also configured, for deriving PMI and RI: + +- The first 2 OFDM symbols are occupied by control signaling. +- The number of PDSCH and DM-RS symbols is equal to 12. +- The same bandwidth part subcarrier spacing configured as for the PDSCH reception +- The bandwidth as configured for the corresponding CQI report. + - The IAB-MT shall only assume the frequency resources as indicated by the DL TX power adjustment MAC CE, if indicated for the slot of the CSI reference resource by DL Tx Power Adjustment MAC CE as described in [10, TS 38.321]. +- The reference resource uses the CP length and subcarrier spacing configured for PDSCH reception +- No resource elements used by primary or secondary synchronization signals or PBCH. +- Redundancy Version 0. +- The ratio of PDSCH EPRE to CSI-RS EPRE is as given in Clause 5.2.2.3.1. + +- In addition, the IAB-MT shall apply the provided DL TX power adjustment, if indicated for the slot of the CSI reference resource by DL Tx Power Adjustment MAC CE as described in [10, TS 38.321]. +- Assume no REs allocated for NZP CSI-RS and ZP CSI-RS. +- Assume the same number of front-loaded DM-RS symbols as the maximum front-loaded symbols configured by the higher layer parameter *maxLength* in *DMRS-DownlinkConfig*. +- Assume the same number of additional DM-RS symbols as the additional symbols configured by the higher layer parameter *dmrs-AdditionalPosition*. +- Assume the PDSCH symbols are not containing DM-RS. +- Assume PRB bundling size of 2 PRBs. +- The PDSCH transmission scheme where the UE may assume that PDSCH transmission would be performed with up to 8 transmission layers as defined in Clause 7.3.1.4 of [4, TS 38.211]. For CQI calculation, the UE should assume that PDSCH signals on antenna ports in the set $[1000, \dots, 1000+v-1]$ for $v$ layers would result in signals equivalent to corresponding symbols transmitted on antenna ports $[3000, \dots, 3000+P-1]$ , as given by + +where $W(i)$ is a vector of PDSCH symbols from the layer mapping defined in Clause 7.3.1.4 of [4, TS 38.211], $P$ is the number of CSI-RS ports. If only one CSI-RS port is configured, $W(i)$ is 1. If the higher layer parameter *reportQuantity* in *CSI-ReportConfig* for which the CQI is reported is set to either 'cri-RI-PMI-CQI' or 'cri-RI-LI-PMI-CQI', $W(i)$ is the precoding matrix corresponding to the reported PMI applicable to $x(i)$ . If the higher layer parameter *reportQuantity* in *CSI-ReportConfig* for which the CQI is reported is set to 'cri-RI-CQI', $W(i)$ is the precoding matrix corresponding to the procedure described in Clause 5.2.1.4.2. If the higher layer parameter *reportQuantity* in *CSI-ReportConfig* for which the CQI is reported is set to 'cri-RI-i1-CQI', $W(i)$ is the precoding matrix corresponding to the reported i1 according to the procedure described in Clause 5.2.1.4.2. The corresponding PDSCH signals transmitted on antenna ports $[3000, \dots, 3000+P-1]$ would have a ratio of EPRE to CSI-RS EPRE equal to the ratio given in Clause 5.2.2.3.1. + +- For a UE configured with a *CSI-ReportConfig* that contains a list of sub-configurations provided by *[csi-ReportSubConfigList]*, + - if a sub-configuration indicates a CSI-RS antenna port subset using the higher layer bitmap parameter *[port-subsetIndicator]*, as described in clause 5.2.1.4.2, for CQI calculation, antenna ports corresponding to all bits with value of 1 in *[port-subsetIndicator]* are mapped to consecutive antenna ports starting at CSI-RS antenna port 3000 in increasing order of the bit position in *[port-subsetIndicator]*. The UE should assume that PDSCH signals on antenna ports in the set $[1000, \dots, 1000+v-1]$ for $v$ layers would result in signals equivalent to corresponding symbols transmitted on antenna ports $[3000, \dots, 3000+P-1]^T$ , as given by + +where $P$ corresponds to the number of bits with value 1 in the bitmap *[port-subsetIndicator]* and $T$ , and are as previously described in this Clause, and the corresponding PDSCH EPRE to CSI-RS EPRE is as previously defined in this Clause if the sub-configuration does not indicate a power offset *[powerOffset]*. + +- if a sub-configuration indicates a list of NZP CSI-RS resources, provided by *[nzp-CSI-RS-resourceList]* and does not indicate a power offset *[powerOffset]*, for CQI calculation for the sub-configuration the UE follows the procedure previously described in this Clause. +- if a sub-configuration indicates a power offset *[powerOffset]*, for CQI calculation, the UE shall assume the corresponding PDSCH signals transmitted on the antenna ports of a CSI-RS resource would have a ratio of EPRE to CSI-RS EPRE equal to the difference between *powerControlOffset* of the CSI-RS resource, given in Clause 5.2.2.3.1, and *[powerOffset]*, where the difference is expected to take one of the values that can be configured for *powerControlOffset* of the CSI-RS resource, given in Clause 5.2.2.3.1, and is also expected to take a value that is no larger than the value of *powerControlOffset*. + +##### 5.2.2.5.1a UE assumptions for CQI/PMI/RI calculation for NCJT + +If the higher layer parameter *reportQuantity* in *CSI-ReportConfig* for which the CQI is reported is set to either 'cri-RI-PMI-CQI' or 'cri-RI-LI-PMI-CQI', the corresponding CSI-RS Resource Set for channel measurement is configured with two Resource Groups and Resource Pairs, as described in clause 5.2.1.4.1, the reported CRI corresponds to an entry of + +the Resource Pairs, and the reported rank combination is , as described in clause 5.2.1.4.2, for CQI calculation, the UE should assume that + +- PDSCH signals on antenna ports in the set for layers would result in signals equivalent to corresponding symbols transmitted on antenna ports of the Group 1 CSI-RS resource in the Resource Pair indicated by the CRI, and PDSCH signals on antenna ports in the set for layers would result in signals equivalent to corresponding symbols transmitted on antenna ports of the Group 2 CSI-RS resource in the Resource Pair indicated by the CRI, as given by + +where , are the two precoding matrices corresponding to the two reported PMIs applicable to , as described in clause 5.2.1.4.2; and the indices are associated to the two Resource Groups configured in the corresponding CSI-RS Resource Set for channel measurement; that the signals , , fully overlap in time and frequency, and that, for the calculation of RI, PMI and LI (if configured) of layers, , the interference from the other layers is derived from channel measurement and precoding matrix corresponding to the other layers. + +- The UE shall assume that the corresponding PDSCH signals for layers transmitted on the antenna ports of the CSI-RS resource in Group would have a ratio of EPRE to CSI-RS EPRE equal to the *powerControlOffset* of the respective CSI-RS resource, for . + +##### 5.2.2.5.1b UE assumptions for CQI/PMI/RI calculation for CJT + +If the higher layer parameter *reportQuantity* in *CSI-ReportConfig* for which the CQI is reported is set to 'cri-RI-PMI-CQI', the higher layer parameter *codebookType* is set to 'typeII-CJT-r18' or 'typeII-CJT-PortSelection-r18', and the corresponding CSI-RS Resource Set for channel measurement is configured with CSI-RS resources, for CQI calculation + +- a UE should assume PDSCH signals on antenna ports in the set for layers would result in signals equivalent to corresponding symbols transmitted on antenna ports of each of the selected CSI-RS resources, as given by + +where is the precoding matrix corresponding to the procedure described in Clause 5.2.2.2.8 and 5.2.2.2.9 for *codebookType* set to 'typeII-CJT-r18' and 'typeII-CJT-PortSelection-r18', respectively, and are the indices of the selected CSI-RS resources in increasing order, such that . A UE should assume that the signals , , fully overlap in time and frequency. + +- a UE can assume that the PDSCH signals for layers would have the same ratio of EPRE to CSI-RS EPRE for all CSI-RS resources , with , equal to the *powerControlOffset* of the respective CSI-RS resource. + +##### 5.2.2.5.1c UE assumptions for CQI/PMI/RI calculation for predicted CSI + +If the higher layer parameter *reportQuantity* in *CSI-ReportConfig* for which the CQI is reported is set to 'cri-RI-PMI-CQI', the higher layer parameter *codebookType* is set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18', and the corresponding CSI-RS Resource Set for channel measurement is aperiodic with CSI-RS resources, for CQI calculation, a UE can assume the same ratio of EPRE to CSI-RS EPRE for all configured CSI-RS resources. + +### 5.2.3 CSI reporting using PUSCH + +A UE shall perform aperiodic CSI reporting using PUSCH on serving cell c upon successful decoding of a DCI format 0\_1 or DCI format 0\_2 which triggers an aperiodic CSI trigger state. A UE shall perform aperiodic CSI reporting using PUSCH on the serving cell with the smallest serving cell index scheduled by DCI format 0\_3 which triggers an aperiodic CSI trigger state. + +When a DCI format 0\_1 schedules two PUSCH allocations, the aperiodic CSI report is carried on the second scheduled PUSCH. When a DCI format 0\_1 schedules more than two PUSCH allocations, the aperiodic CSI report is carried on the penultimate scheduled PUSCH. + +An aperiodic CSI report carried on the PUSCH supports wideband, and sub-band frequency granularities. An aperiodic CSI report carried on the PUSCH supports Type I, Type II, Enhanced Type II, Further Enhanced Type II Port Selection CSI, Enhanced Type II for CJT, Further Enhanced Type II Port Selection for CJT, Enhanced Type II for predicted PMI, Further Enhanced Type II Port Selection for predicted PMI and TDCP reporting. + +A UE shall perform semi-persistent CSI reporting on the PUSCH upon successful decoding of a DCI format 0\_1 or DCI format 0\_2 which activates a semi-persistent CSI trigger state. DCI format 0\_1 and DCI format 0\_2 contains a CSI request field which indicates the semi-persistent CSI trigger state to activate or deactivate. Semi-persistent CSI reporting on the PUSCH supports Type I, Type II with wideband, and sub-band frequency granularities, Enhanced Type II, Further Enhanced Type II Port Selection CSI, Enhanced Type II for CJT, Further Enhanced Type II Port Selection for CJT, Enhanced Type II for predicted PMI and Further Enhanced Type II Port Selection for predicted PMI. The PUSCH resources and MCS shall be allocated semi-persistently by an uplink DCI. + +CSI reporting on PUSCH can be multiplexed with uplink data on PUSCH except that semi-persistent CSI reporting on PUSCH activated by a DCI format is not expected to be multiplexed with uplink data on the PUSCH. CSI reporting on PUSCH can also be performed without any multiplexing with uplink data from the UE. + +Type I CSI feedback is supported for CSI Reporting on PUSCH. Type I wideband and sub-band CSI is supported for CSI Reporting on the PUSCH. Type II CSI is supported for CSI Reporting on the PUSCH. + +For Type I, Type II, Enhanced Type II, Further Enhanced Type II Port Selection CSI, Enhanced Type II for CJT, Further Enhanced Type II Port Selection for CJT, Enhanced Type II for predicted PMI and Further Enhanced Type II Port Selection for predicted PMI feedback on PUSCH, a CSI report comprises of two parts. Part 1 has a fixed payload size and is used to identify the number of information bits in Part 2. Part 1 shall be transmitted in its entirety before Part 2. + +- For Type I CSI feedback, Part 1 contains RI (if reported), CRI (if reported), CQI for the first codeword (if reported). Part 2 contains PMI (if reported), LI (if reported) and contains the CQI for the second codeword (if reported) when RI is larger than 4. For a *CSI-ReportConfig* configured with *codebookType* set to 'typeI-SinglePanel' and the corresponding CSI-RS Resource Set for channel measurement configured with two Resource Groups and Resource Pairs, Part 1 contains RI(s), CRI(s), CQI(s) for the first codeword and is zero padded to a fixed payload size (if needed). Part 2 contains the CQI(s) for the second codeword (if reported) when RI is larger than 4, LI(s) (if reported) and PMI(s). For a *CSI-ReportConfig* that contains a list of sub-configurations provided by [*csi-ReportSubConfigList*], for Type I CSI feedback for one or more of the sub-configurations, Part 1 for a sub-configuration contains corresponding RI (if reported), CRI (if reported), CQI for the first codeword (if reported) and is zero padded to a fixed payload size (if needed). Part 2 for a sub-configuration contains the corresponding CQI for the second codeword (if reported) when RI is larger than 4, LI (if reported) and PMI (if reported). +- For Type II CSI feedback, Part 1 contains RI (if reported), CQI, and an indication of the number of non-zero wideband amplitude coefficients per layer for the Type II CSI (see Clause 5.2.2.2.3). The fields of Part 1 – RI (if reported), CQI, and the indication of the number of non-zero wideband amplitude coefficients for each layer – are separately encoded. Part 2 contains the PMI and LI (if reported) of the Type II CSI. The elements of , (if reported) and (if reported) are reported in the increasing order of their indices, , where the element of the lowest index is mapped to the most significant bits and the element of the highest index is mapped to the least significant bits. Part 1 and 2 are separately encoded. +- For Enhanced Type II CSI feedback (see Clause 5.2.2.2.5), Further Enhanced Type II Port Selection CSI feedback (see Clause 5.2.2.2.7), Enhanced Type II for predicted PMI with (see Clause 5.2.2.2.10) and Further Enhanced Type II Port Selection for predicted PMI (see Clause 5.2.2.2.11), Part 1 contains RI (if reported), CQI, and the total number of reported non-zero amplitude coefficients across layers. The fields of Part 1 – RI (if reported), CQI, and the total number of reported non-zero amplitude coefficients across layers – are separately encoded. Part 2 contains the PMI of the Enhanced Type II, Further Enhanced Type II Port Selection CSI, Enhanced Type II for predicted PMI with or Further Enhanced Type II Port Selection for predicted PMI. Part 1 and 2 are separately encoded. +- For Enhanced Type II for CJT (see Clause 5.2.2.2.8) and Further Enhanced Type II Port Selection for CJT (see Clause 5.2.2.2.9), Part 1 contains RI (if reported), CQI, the total number of reported non-zero amplitude coefficients across layers, the bitmap selecting CSI-RS resources (if reported) and the selected combination of or (if reported). The fields of Part 1 – RI (if reported), CQI, the total number of reported non-zero amplitude coefficients across layers, the bitmap selecting CSI-RS resources (if reported) and the selected combination of or (if reported) – are separately encoded. Part 2 contains the PMI of the Enhanced Type II for CJT or Further Enhanced Type II Port Selection for CJT. Part 1 and 2 are separately encoded. +- For Enhanced Type II for predicted PMI with (see Clause 5.2.2.2.10), Part 1 contains RI (if reported), the CQI (if the higher layer parameter *TDCQI* is set to '1-1' or '1-2') or the first CQI (if the higher layer parameter *TDCQI* is set to '2') and the total number of reported non-zero amplitude coefficients across layers. The fields of Part 1 – RI (if reported), CQI, and the total number of reported non-zero amplitude coefficients across layers – are + +separately encoded. Part 2 contains the second CQI (if the higher layer parameter *TDCQI* is set to '2') and the PMI of the Enhanced Type II for predicted PMI with . Part 1 and 2 are separately encoded. + +A Type II CSI report that is carried on the PUSCH shall be computed independently from any Type II CSI report that is carried on the PUCCH formats 3 or 4 (see Clause 5.2.4 and 5.2.2). + +When the higher layer parameter *reportQuantity* is configured with one of the values 'cri-RSRP', 'ssb-Index-RSRP', 'cri-SINR' or 'ssb-Index-SINR', or 'cri-RSRP-Index', 'ssb-Index-RSRP-Index', 'cri-SINR-Index', 'ssb-Index-SINR-Index', 'tdcp', the CSI feedback consists of a single part. + +For both Type I and Type II reports configured for PUCCH but transmitted on PUSCH, the determination of the payload for CSI part 1 and CSI part 2 follows that of PUCCH as described in Clause 5.2.4. + +When CSI reporting on PUSCH comprises two parts, the UE may omit a portion of the Part 2 CSI. Omission of Part 2 CSI is according to the priority order shown in Table 5.2.3-1, where $N_{\text{Rep}}$ is the number of CSI reports configured to be carried on the PUSCH. Priority 0 is the highest priority and priority $2N_{\text{Rep}}$ is the lowest priority and the CSI report $n$ corresponds to the CSI report with the $n$ th smallest $\text{Pri}_{i,\text{csi}}(y,k,c,s)$ value among the $N_{\text{Rep}}$ CSI reports as defined in Clause 5.2.5. The subbands for a given CSI report $n$ indicated by the higher layer parameter *csi-ReportingBand* with value '1' are numbered continuously in increasing order with the lowest subband of *csi-ReportingBand* with value set to '1' as subband 0. When omitting Part 2 CSI information for a particular priority level, the UE shall omit all of the information at that priority level, except when the corresponding CSI report contains one or more CSI sub-reports with Part 2 each corresponding to a sub-configuration from a list of sub-configurations provided by *csi-ReportSubConfigList* contained in the *CSI-ReportConfig* as described in Clause 5.2.1.1. + +- For Enhanced Type II reports and Enhanced Type II for predicted PMI configured with higher layer parameter , for a given CSI report , each reported element of indices and , indexed by and , is associated with a priority value , with with , and , and where is defined in Clause 5.2.2.2.5. The element with the highest priority has the lowest associated value . Omission of Part 2 CSI is according to the priority order shown in Table 5.2.3-1, where + - Group 0 includes indices (if reported), (if reported) and (). + - Group 1 includes indices (if reported), (if reported), the highest priority elements of , , the highest priority elements of and the highest priority elements of (). + - Group 2 includes the lowest priority elements of , the lowest priority elements of and the lowest priority elements of (). +- For Further Enhanced Type II Port Selection reports and Further Enhanced Type II Port Selection for predicted PMI, for a given CSI report , each reported element of and , indexed by , and , is associated with a priority value , with , and . The element with the highest priority has the lowest associated value . Omission of Part 2 CSI is according to the priority order shown in Table 5.2.3-1, where: + - Group 0 includes (if reported), () and (if reported). + - Group 1 includes the highest priority elements of (if reported), , the highest priority elements of and the highest priority elements of (). + - Group 2 includes the lowest priority elements of (if reported), the lowest priority elements of and the lowest priority elements of (). +- For Enhanced Type II for CJT reports, for a given CSI report , each reported element of and , indexed by , and , is associated with a priority value , with , for , and , and where and are defined in Clause 5.2.2.2.8. The element with the highest priority has the lowest associated value . Omission of Part 2 CSI is according to the priority order shown in Table 5.2.3-1, where + - Group 0 includes indices (if reported), (if reported) and (). + - Group 1 includes indices (if reported), (if reported), the highest priority elements of , , the highest priority elements of , the highest priority elements of () and (if reported). + - Group 2 includes the lowest priority elements of , the lowest priority elements of and the lowest priority elements of (). + +- For Further Enhanced Type II Port Selection for CJT reports, for a given CSI report, each reported element of $\mathbf{h}_{p,c}$ and $\mathbf{h}_{p,c}$ , indexed by $p$ , $c$ , and $i$ , is associated with a priority value $P_{p,c,i}$ , for $p$ , $c$ , and $i$ , and where $P_{p,c,i}$ is defined in Clause 5.2.2.2.8. The element with the highest priority has the lowest associated value. Omission of Part 2 CSI is according to the priority order shown in Table 5.2.3-1, where: + - Group 0 includes $\mathbf{h}_{p,c}$ (if reported), $\mathbf{h}_{p,c}$ (if reported). + - Group 1 includes the highest priority elements of $\mathbf{h}_{p,c}$ (if reported), the highest priority elements of $\mathbf{h}_{p,c}$ , the highest priority elements of $\mathbf{h}_{p,c}$ (if reported) and $\mathbf{h}_{p,c}$ (if reported). + - Group 2 includes the lowest priority elements of $\mathbf{h}_{p,c}$ (if reported), the lowest priority elements of $\mathbf{h}_{p,c}$ and the lowest priority elements of $\mathbf{h}_{p,c}$ (if reported). +- For Enhanced Type II for predicted PMI configured with $\mathbf{h}_{p,c}$ , for a given CSI report, each reported element of $\mathbf{h}_{p,c}$ and $\mathbf{h}_{p,c}$ , indexed by $p$ , $c$ , and $i$ , is associated with a priority value $P_{p,c,i}$ , for $p$ , $c$ , and $i$ . The element with the highest priority has the lowest associated value. Omission of Part 2 CSI is according to the priority order shown in Table 5.2.3-1, where: + - Group 0 includes indices $\mathbf{h}_{p,c}$ (if reported), $\mathbf{h}_{p,c}$ (if reported), $\mathbf{h}_{p,c}$ (if reported) and the second wideband CQI (if reported). + - Group 1 includes indices $\mathbf{h}_{p,c}$ (if reported), $\mathbf{h}_{p,c}$ (if reported), the highest priority elements of $\mathbf{h}_{p,c}$ , the highest priority elements of $\mathbf{h}_{p,c}$ , the highest priority elements of $\mathbf{h}_{p,c}$ (if reported) and the second subband CQI of even subbands (if reported). + - Group 2 includes the lowest priority elements of $\mathbf{h}_{p,c}$ , the lowest priority elements of $\mathbf{h}_{p,c}$ , the lowest priority elements of $\mathbf{h}_{p,c}$ (if reported) and the second subband CQI of odd subbands (if reported). +- For a Reporting Setting for which the *CSI-ReportConfig* contains a list of sub-configurations provided by [*csi-ReportSubConfigList*], for a corresponding CSI report which contains one or more CSI sub-reports, omission of Part 2 CSI is done at a sub-configuration level within the same priority level defined by Table 5.2.3-1 where a sub-configuration with an index, provided by [*csi-ReportSubConfigID*], with lower value has higher priority. + +**Table 5.2.3-1: Priority reporting levels for Part 2 CSI** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Priority 0:

For CSI reports 1 to     , Group 0 CSI for CSI reports configured as 'typeII-r16', 'typeII-PortSelection-r16', 'typeII-PortSelection-r17', 'typeII-CJT-r18', 'typeII-CJT-PortSelection-r18', 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18'; Part 2 wideband CSI for CSI reports configured otherwise

| +|

Priority 1:

Group 1 CSI for CSI report 1, if configured as 'typeII-r16', 'typeII-PortSelection-r16', 'typeII-PortSelection-r17', 'typeII-CJT-r18', 'typeII-CJT-PortSelection-r18', 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18'; Part 2 subband CSI of even subbands for CSI report 1, if configured otherwise

| +|

Priority 2:

Group 2 CSI for CSI report 1, if configured as 'typeII-r16', 'typeII-PortSelection-r16', 'typeII-PortSelection-r17', 'typeII-CJT-r18', 'typeII-CJT-PortSelection-r18', 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18'; Part 2 subband CSI of odd subbands for CSI report 1, if configured otherwise

| +|

Priority 3:

Group 1 CSI for CSI report 2, if configured as 'typeII-r16', 'typeII-PortSelection-r16', 'typeII-PortSelection-r17', 'typeII-CJT-r18', 'typeII-CJT-PortSelection-r18', 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18'; Part 2 subband CSI of even subbands for CSI report 2, if configured otherwise

| +|

Priority 4:

Group 2 CSI for CSI report 2, if configured as 'typeII-r16', 'typeII-PortSelection-r16', 'typeII-PortSelection-r17', 'typeII-CJT-r18', 'typeII-CJT-PortSelection-r18', 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18'; Part 2 subband CSI of odd subbands for CSI report 2, if configured otherwise

| +| ⋮ | +|

Priority     :

Group 1 CSI for CSI report     , if configured as 'typeII-r16', 'typeII-PortSelection-r16', 'typeII-PortSelection-r17', 'typeII-CJT-r18', 'typeII-CJT-PortSelection-r18', 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18'; Part 2 subband CSI of even subbands for CSI report     , if configured otherwise

| +|

Priority     :

Group 2 CSI for CSI report     , if configured as 'typeII-r16', 'typeII-PortSelection-r16', 'typeII-PortSelection-r17', 'typeII-CJT-r18', 'typeII-CJT-PortSelection-r18', 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18'; Part 2 subband CSI of odd subbands for CSI report     , if configured otherwise

| + +When the UE is scheduled to transmit a transport block on PUSCH not using repetition type B multiplexed with a CSI report(s) and if *numberOfSlotsTBToMS* is not present in the resource allocation table, or if *numberOfSlotsTBToMS* is + +present in the resource allocation table and the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI is equal to 1, Part 2 CSI is omitted only when + +$$\left( (O_{CSI-2} + L_{CSI-2}) \cdot \beta_{offset}^{PUSCH} \cdot \sum_{l=0}^{N_{symb,all}^{PUSCH}-1} M_{sc}^{UCI}(l) / \sum_{r=0}^{C_{UL-SCH}-1} K_r \right) \text{ is larger than } \alpha \text{ or when the higher layer parameter } [nrof\_UTO\_UCI] \text{ is configured, where parameters } O_{CSI-2}, L_{CSI-2}, \beta_{offset}^{PUSCH}, N_{symb,all}^{PUSCH}, M_{sc}^{UCI}(l), C_{UL-SCH}, K_r, Q'_{CSI-1}, \text{ and } \alpha \text{ are defined in Clause 6.3.2.4 of [5, TS 38.212].}$$ + +Part 2 CSI is omitted level by level, beginning with the lowest priority level until the lowest priority level is reached + +$$\text{which causes the } \left( (O_{CSI-2} + L_{CSI-2}) \cdot \beta_{offset}^{PUSCH} \cdot \sum_{l=0}^{N_{symb,all}^{PUSCH}-1} M_{sc}^{UCI}(l) / \sum_{r=0}^{C_{UL-SCH}-1} K_r \right) \text{ to be less than or equal to } \alpha \text{ or when the higher layer parameter } [nrof\_UTO\_UCI] \text{ is configured.}$$ + +When the UE is scheduled to transmit a transport block on PUSCH not using repetition type B multiplexed with a CSI report(s) and if *numberOfSlotsTBoMS* is present in the resource allocation table and the value of *numberOfSlotsTBoMS* in the row indicated by the Time domain resource assignment field in DCI is larger than 1, Part 2 CSI is omitted only + +$$\text{when } \left( (O_{CSI-2} + L_{CSI-2}) \cdot \beta_{offset}^{PUSCH} \cdot \sum_{l=0}^{N_{symb,all}^{PUSCH}-1} M_{sc}^{UCI}(l) / \sum_{r=0}^{C_{UL-SCH}-1} K_r \right) \text{ is larger than } \alpha \text{ when the higher layer parameter } [nrof\_UTO\_UCI] \text{ is configured, where parameters } O_{CSI-2}, L_{CSI-2}, \beta_{offset}^{PUSCH}, N_{symb,all}^{PUSCH}, M_{sc}^{UCI}(l), C_{UL-SCH}, K_r, Q'_{CSI-1}, \text{ and } \alpha \text{ are defined in Clause 6.3.2.4 of [5, TS 38.212].}$$ + +Part 2 CSI is omitted level by level, beginning with the lowest priority level until the lowest priority level is reached which causes the $\left( (O_{CSI-2} + L_{CSI-2}) \cdot \beta_{offset}^{PUSCH} \cdot \sum_{l=0}^{N_{symb,all}^{PUSCH}-1} M_{sc}^{UCI}(l) / \sum_{r=0}^{C_{UL-SCH}-1} K_r \right)$ to be less than or equal to $\alpha$ or when the higher layer parameter $[nrof\_UTO\_UCI]$ is configured. + +When the UE is scheduled to transmit a transport block on PUSCH using repetition type B multiplexed with a CSI report(s), Part 2 CSI is omitted only when + +is larger than + +, +or + +$$\text{when the higher layer parameter } [nrof\_UTO\_UCI] \text{ is configured, where parameters } O_{CSI-2}, L_{CSI-2}, \beta_{offset}^{PUSCH}, C_{UL-SCH}, K_r, Q'_{CSI-1}, \text{ and } \alpha \text{ are defined in Clause 6.3.2.4 of [5, TS 38.212].}$$ + +Part 2 CSI is omitted level by level, beginning with the lowest priority level until the lowest priority level is reached which causes + +to be less than or equal to + +, +or + +when the higher layer parameter $[nrof\_UTO\_UCI]$ is configured. + +When part 2 CSI is transmitted on PUSCH with no transport block, lower priority bits are omitted until Part 2 CSI code rate, which is given by $c_T$ , are given in clause 6.3.2.4 of [5, 38.212] before HARQ-ACK puncturing part 2 CSI if any, is below a threshold code rate $c_T$ lower than one, where + +$$c_T = \frac{R}{\beta_{offset}^{CSI-part2}}$$ + +- is the CSI offset value from Table 9.3-2 of [6, TS 38.213] +- $R$ is signaled code rate in DCI + +If the UE is in an active semi-persistent CSI reporting configuration on PUSCH, the CSI reporting is deactivated when either the downlink BWP or the uplink BWP is changed. Another activation command is required to enable the semi-persistent CSI reporting. + +### 5.2.4 CSI reporting using PUCCH + +A UE is semi-statically configured by higher layers to perform periodic CSI Reporting on the PUCCH. A UE can be configured by higher layers for multiple periodic CSI Reports corresponding to multiple higher layer configured CSI Reporting Settings, where the associated CSI Resource Settings are higher layer configured. For a Reporting Setting for which the *CSI-ReportConfig* contains a list of sub-configurations provided by [*csi-ReportSubConfigList*], CSI reporting is provided for all the sub-configurations in each corresponding reporting instance. Periodic CSI reporting on PUCCH formats 2, 3, 4 supports Type I CSI with wideband granularity. + +A UE shall perform semi-persistent CSI reporting on the PUCCH applied starting from the first slot that is after slot when the UE would transmit a PUCCH with HARQ-ACK information in slot $n$ corresponding to the PDSCH carrying the activation command described in clause 6.1.3.16 of [10, TS 38.321] where $\mu$ is the SCS configuration for the PUCCH. The activation command will contain one or more Reporting Settings, with or without containing one or more sub-configurations for each Reporting Setting for which the *CSI-ReportConfig* contains a list of sub-configurations provided by [*csi-ReportSubConfigList*], where the associated CSI Resource Settings are configured. Semi-persistent CSI reporting on the PUCCH supports Type I CSI. Semi-persistent CSI reporting on the PUCCH format 2 supports Type I CSI with wideband frequency granularity. Semi-persistent CSI reporting on PUCCH formats 3 or 4 supports Type I CSI with wideband and sub-band frequency granularities and Type II CSI Part 1. + +When the PUCCH carry Type I CSI with wideband frequency granularity, the CSI payload carried by the PUCCH format 2 and PUCCH formats 3, or 4 are identical and the same irrespective of RI (if reported), CRI (if reported). A *CSI-ReportConfig* with *codebookType* set to 'typeI-SinglePanel' and the corresponding CSI-RS Resource Set for channel measurement configured with two Resource Groups and Resource Pairs can be configured with wideband frequency granularity only with *csi-ReportMode* set to 'Mode1' and *numberOfSingleTRP-CSI-Mode1* set to . For type I CSI sub-band reporting on PUCCH formats 3, or 4, the payload is split into two parts. The first part contains RI (if reported), CRI (if reported), CQI for the first codeword. The second part contains PMI (if reported), LI (if reported) and contains the CQI for the second codeword (if reported) when $RI > 4$ . For a *CSI-ReportConfig* configured with subband reporting, *codebookType* set to 'typeI-SinglePanel' and the corresponding CSI-RS Resource Set for channel measurement configured with two Resource Groups and Resource Pairs, Part 1 contains RI(s), CRI(s), CQI(s) for the first codeword and is zero padded to a fixed payload size (if needed). Part 2 contains the CQI(s) for the second codeword (if reported) when $RI$ is larger than 4, LIs (if reported) and PMI(s). For a *CSI-ReportConfig* containing a list of sub-configurations provided by [*csi-ReportSubConfigList*], and configured with subband reporting, for Type I CSI for one or more of the sub-configurations, Part 1 for a sub-configuration contains corresponding RI (if reported), CRI (if reported), CQI for the first codeword (if reported) and is zero padded to a fixed payload size (if needed). Part 2 for a sub-configuration contains the corresponding CQI for the second codeword (if reported) when $RI$ is larger than 4, LI (if reported) and PMI (if reported). + +A semi-persistent report carried on the PUCCH formats 3 or 4 supports Type II CSI feedback, but only Part 1 of Type II CSI feedback (See Clause 5.2.2 and 5.2.3). Supporting Type II CSI reporting on the PUCCH formats 3 or 4 is a UE capability *type2-SP-CSI-Feedback-LongPUCCH*. A Type II CSI report (Part 1 only) carried on PUCCH formats 3 or 4 shall be calculated independently of any Type II CSI reports carried on the PUSCH (see Clause 5.2.3). + +When the UE is configured with CSI Reporting on PUCCH formats 2, 3 or 4, each PUCCH resource is configured for each candidate UL BWP. + +If the UE is in an active semi-persistent CSI reporting configuration on PUCCH and has not received a deactivation command, the CSI reporting takes place when the BWP in which the reporting is configured to take place is the active BWP, otherwise the CSI reporting is suspended. + +A UE is not expected to report CSI with a total number of UCI bits and CRC bits larger than 115 bits when configured with PUCCH format 4. For CSI reports transmitted on a PUCCH, if all CSI reports consist of one part, the UE may omit a portion of CSI reports. Omission of CSI is according to the priority order determined from the $Pri_{i,csi}(y, k, c, s)$ value as defined in Clause 5.2.5. CSI report is omitted beginning with the lowest priority level until the CSI report code rate is less or equal to the one configured by the higher layer parameter *maxCodeRate*. + +If any of the CSI reports consist of two parts, the UE may omit a portion of Part 2 CSI. Omission of Part 2 CSI is according to the priority order shown in Table 5.2.3-1. For a Reporting Setting for which the *CSI-ReportConfig* contains a list of sub-configurations provided by *[csi-ReportSubConfigList]*, for a given CSI report which contains one or more CSI sub-reports, omission of Part 2 CSI is defined in Clause 5.2.3. Part 2 CSI is omitted beginning with the lowest priority level until the Part 2 CSI code rate is less or equal to the one configured by higher layer parameter *maxCodeRate*. + +### 5.2.5 Priority rules for CSI reports + +For two overlapping PUSCHs, the priority rules in this clause are applied for physical channels with same priority index according to clause 9 in [6, TS 38.213] if a UE is not configured with *enableSTx2PofmDCI* or a UE is configured by higher layer parameter *PDCCH-Config* that contains two different values of *coresetPoolIndex* in *ControlResourceSet* and the UE is configured with *enableSTx2PofmDCI* and the two overlapping PUSCHs are associated with same value of *coresetPoolIndex*. + +CSI reports are associated with a priority value where + +- for aperiodic CSI reports to be carried on PUSCH for semi-persistent CSI reports to be carried on PUSCH, for semi-persistent CSI reports to be carried on PUCCH and for periodic CSI reports to be carried on PUCCH; +- for CSI reports carrying L1-RSRP or L1-SINR and for CSI reports not carrying L1-RSRP or L1-SINR; +- *c* is the serving cell index and is the value of the higher layer parameter *maxNrofServingCells*; +- *s* is the *reportConfigID* and is the value of the higher layer parameter *maxNrofCSI-ReportConfigurations*. + +A first CSI report is said to have priority over second CSI report if the associated value is lower for the first report than for the second report. + +Two CSI reports are said to collide if the time occupancy of the physical channels scheduled to carry the CSI reports overlap in at least one OFDM symbol and are transmitted on the same carrier. When a UE is configured to transmit two colliding CSI reports, + +- if *y* values are different between the two CSI reports, the following rules apply except for the case when one of the *y* value is 2 and the other *y* value is 3 (for CSI reports transmitted on PUSCH, as described in Clause 5.2.3; for CSI reports transmitted on PUCCH, as described in Clause 5.2.4): + - The CSI report with higher value shall not be sent by the UE. +- otherwise, the two CSI reports are multiplexed or either is dropped based on the priority values, as described in Clause 9.2.5.2 in [6, TS 38.213]. + +A CSI report configured with *LTM-CSI-ReportConfig* has a higher priority in case of collision with CSI report(s) configured with *CSI-ReportConfig*. + +If a semi-persistent CSI report to be carried on PUSCH overlaps in time with PUSCH data transmission in one or more symbols on the same carrier, and if the earliest symbol of these PUSCH channels starts no earlier than $N_2 + d_{2,1}$ symbols after the last symbol of the DCI scheduling the PUSCH where $d_{2,1}$ is the maximum of the $d_{2,1}$ associated with the PUSCH carrying semi-persistent CSI report and the PUSCH with data transmission, the CSI report shall not be transmitted by the UE. Otherwise, if the timeline requirement is not satisfied this is an error case. + +If a UE would transmit a first PUSCH that includes semi-persistent CSI reports and a second PUSCH that includes an UL-SCH on the same carrier, and the first PUSCH transmission would overlap in time with the second PUSCH transmission, the UE does not transmit the first PUSCH and transmits the second PUSCH. The UE expects that the first and second PUSCH transmissions satisfy the above timing conditions for PUSCH transmissions that overlap in time when at least one of the first or second PUSCH transmissions is in response to a DCI format detection by the UE. + +## 5.3 UE PDSCH processing procedure time + +If the first uplink symbol of the PUCCH which carries the HARQ-ACK information, as defined by the assigned HARQ-ACK timing $K_1$ and $K_{offset}$ , if configured, and the PUCCH resource to be used and including the effect of the timing advance, starts no earlier than at symbol $L_1$ , where $L_1$ is defined as the next uplink symbol with its CP starting after after the end of the last symbol of the PDSCH carrying the TB being acknowledged, then the UE shall provide a valid HARQ-ACK message. + +- $N_l$ is based on $\mu$ of table 5.3-1 and table 5.3-2 for UE processing capability 1 and 2 respectively, where $\mu$ corresponds to the one of $(\mu_{PDCCH}, \mu_{PDSCH}, \mu_{UL})$ resulting with the largest $T_{proc,1}$ , where the $\mu_{PDCCH}$ corresponds to the subcarrier spacing of the PDCCH scheduling the PDSCH, the $\mu_{PDSCH}$ corresponds to the subcarrier spacing of the scheduled PDSCH, and $\mu_{UL}$ corresponds to the subcarrier spacing of the uplink channel with which the HARQ-ACK is assumed to be transmitted regardless of whether or not the PDSCH reception provides a transport block for a HARQ process with disabled HARQ-ACK information as indicated by *HARQ-feedbackEnabling-disablingperHARQprocess*, if provided, and $\kappa$ is defined in clause 4.1 of [4, TS 38.211]. +- For UE processing capability 2, + - if the UE is not indicating [*UE Capability name*], the UE is not expected to be simultaneously configured with higher layer parameter *processingType2Enabled* set to 'enable' and higher layer parameter *enhanced-dmrs-Type\_r18*, and the additional processing delay $d_3$ is 0. + - if the UE is indicating [*UE Capability name*], + - if the UE is configured with higher layer parameter *enhanced-dmrs-Type\_r18*, the additional processing delay $d_3$ is indicated by [*UE Capability name*], + - otherwise $d_3=0$ . +- For operation with shared spectrum channel access in FR1, $T_{ext}$ is calculated according to [4, TS 38.211], otherwise $T_{ext}=0$ . +- If the PDSCH DM-RS position for the additional DM-RS in Table 7.4.1.1.2-3 in clause 7.4.1.1.2 of [4, TS 38.211] is then $N_{l,0}=14$ in Table 5.3-1, otherwise $N_{l,0}=13$ . +- If the UE is configured with multiple active component carriers, the first uplink symbol which carries the HARQ-ACK information further includes the effect of timing difference between the component carriers as given in [11, TS 38.133]. +- For the PDSCH mapping type A as given in clause 7.4.1.1 of [4, TS 38.211]: if the last symbol of PDSCH is on the $i$ -th symbol of the slot where $i < 7$ , then $d_{l,l} = 7 - i$ , otherwise $d_{l,l} = 0$ +- If a PUCCH of a larger priority index would overlap with a PUCCH of a smaller priority index, or with a PUSCH of a smaller priority index and the PUCCH of a larger priority index and the PUSCH of a smaller priority index are not simultaneously transmitted and the UE is not provided *uci-MuxWithDiffPrio* for the primary PUCCH group or *uci-MuxWithDiffPrioSecondaryPUCCHgroup* for the secondary PUCCH group, $d_2$ for the PUCCH of a larger priority is set as reported by the UE; otherwise $d_2 = 0$ . +- For UE processing capability 1: If the PDSCH is mapping type B as given in clause 7.4.1.1 of [4, TS 38.211], and + - if the number of PDSCH symbols allocated is $L \geq 7$ , then $d_{l,l} = 0$ , + - if the number of PDSCH symbols allocated is $L \geq 4$ and $L \leq 6$ , then $d_{l,l} = 7 - L$ . + - if the number of PDSCH symbols allocated is $L = 3$ then $d_{l,l} = 3 + \min(d, l)$ , where $d$ is the number of overlapping symbols of the scheduling PDCCH and the scheduled PDSCH. + - if the number of PDSCH symbols allocated is 2, then $d_{l,l} = 3 + d$ , where $d$ is the number of overlapping symbols of the scheduling PDCCH and the scheduled PDSCH. +- For UE processing capability 2: If the PDSCH is mapping type B as given in clause 7.4.1.1 of [4, TS 38.211], + - if the number of PDSCH symbols allocated is $L \geq 7$ , then $d_{l,l} = 0$ , + - if the number of PDSCH symbols allocated is $L \geq 3$ and $L \leq 6$ , then $d_{l,l}$ is the number of overlapping symbols of the scheduling PDCCH and the scheduled PDSCH, + - if the number of PDSCH symbols allocated is 2, + +- if the scheduling PDCCH was in a 3-symbol CORESET and the CORESET and the PDSCH had the same starting symbol, then $d_{l,l} = 3$ , +- otherwise $d_{l,l}$ is the number of overlapping symbols of the scheduling PDCCH and the scheduled PDSCH. +- For UE processing capability 2 with scheduling limitation when $\mu_{PDSCH} = 1$ , if the scheduled RB allocation exceeds 136 RBs, the UE defaults to capability 1 processing time. The UE may skip decoding a number of PDSCHs with last symbol within 10 symbols before the start of a PDSCH that is scheduled to follow Capability 2, if any of those PDSCHs are scheduled with more than 136 RBs with 30kHz SCS and following Capability 1 processing time. +- For a UE that supports capability 2 on a given cell, the processing time according to UE processing capability 2 is applied if the high layer parameter *processingType2Enabled* in *PDSCH-ServingCellConfig* is configured for the cell and set to 'enable'. +- PDSCH processing capability 2 is not applied to PDSCH scheduled by PDCCH with DCI format 4\_0, 4\_1, or 4\_2. +- If this PUCCH resource is overlapping with another PUCCH or PUSCH resource, then HARQ-ACK is multiplexed following the procedure in clause 9.2.5 of [6, TS 38.213], otherwise the HARQ-ACK message is transmitted on PUCCH. +- UE is not expected to be scheduled to transmit PUCCH carrying the HARQ-ACK information for PDSCH scheduled by a PDCCH if uplink switching gap is triggered for the PUCCH as defined in clause 6.1.6 and the first uplink symbol of the PUCCH starts earlier than the duration of $\{ + \}$ from the last symbol of the PDCCH, where $\{ + \}$ equals to the switching gap duration. + +Otherwise the UE may not provide a valid HARQ-ACK corresponding to the scheduled PDSCH. The value of $T_{proc,l}$ is used both in the case of normal and extended cyclic prefix. + +For a PDSCH that consists of two PDSCH transmission occasions in time domain in one slot, $d_{l,l}$ is calculated based on the first PDSCH transmission occasion in the slot, and as described above. + +For PDSCH with mapping Type B, if PDSCH is scheduled by a PDCCH reception that includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], $d_{l,l}$ for PDSCH processing time is determined by considering the PDCCH candidate that results in larger $d_{l,l}$ value. + +**Table 5.3-1: PDSCH processing time for PDSCH processing capability 1** + +| | PDSCH decoding time $N_t$ [symbols] | | +|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | dmrs-AdditionalPosition = 'pos0' in DMRS-DownlinkConfig in dmrs-DownlinkForPDSCH-MappingTypeA and dmrs-DownlinkForPDSCH-MappingTypeB if either higher layer parameter is configured, and in dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 and dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 if either higher layer parameter is configured | dmrs-AdditionalPosition $\neq$ 'pos0' in DMRS-DownlinkConfig in any of dmrs-DownlinkForPDSCH-MappingTypeA , dmrs-DownlinkForPDSCH-MappingTypeB , dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 , dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 , or if none of the higher layer parameters is configured | +| 0 | 8 | $N_{t,0}$ | +| 1 | 10 | 13 | +| 2 | 17 | 20 | +| 3 | 20 | 24 | +| 5 | 80 | 96 | +| 6 | 160 | 192 | + +**Table 5.3-2: PDSCH processing time for PDSCH processing capability 2** + +| | PDSCH decoding time N_t [symbols] | +|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | dmrs-AdditionalPosition = 'pos0' in
DMRS-DownlinkConfig in
dmrs-DownlinkForPDSCH-MappingTypeA and dmrs-DownlinkForPDSCH-MappingTypeB if
either higher layer parameter is configured, and in dmrs-DownlinkForPDSCH-
MappingTypeA-DCI-1-2 and dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 if either
higher layer parameter is configured | +| 0 | 3 | +| 1 | 4.5 | +| 2 | 9 for frequency range 1 | + +### 5.3.1 Application delay of the minimum scheduling offset restriction + +When the UE is scheduled with DCI format 0\_1, 0\_3, 1\_1 or 1\_3 with a '*Minimum applicable scheduling offset indicator*' field in slot $n$ , it shall determine the $K_{0min}$ and $K_{2min}$ values, if configured respectively, to be applied, while the previously applied $K_{0min}$ and/or $K_{2min}$ values are applied until the new values take effect. If the DCI in slot $n$ also indicates an active DL (UL) BWP change for a serving cell, the indicated $K_{0min}$ ( $K_{2min}$ ) value in the new active DL (UL) BWP, if configured, is applied from the slot indicated by the slot offset value of the time domain resource assignment field in the DCI. Otherwise, change of applied minimum scheduling offset restriction indication carried by DCI in slot $n$ , shall be applied in slot $n+X$ of the scheduling cell. The UE does not expect to be scheduled with DCI format 0\_1, 0\_3, 1\_1 or 1\_3 with '*Minimum applicable scheduling offset indicator*' field indicating another change to $K_{0min}$ or $K_{2min}$ for the same active BWP of the scheduled cell before slot $n+X$ of the scheduling cell. + +When the DCI format 0\_1, 0\_3, 1\_1 or 1\_3 with '*Minimum applicable scheduling offset indicator*' field indicating a change to the applied $K_{0min}$ or $K_{2min}$ is contained within the first three symbols of slot $n$ , the value of application delay $X$ is determined by, where $K_{0minOld}$ is the currently applied $K_{0min}$ value of the active DL BWP in the scheduled cell and is zero, if *minimumSchedulingOffsetK0* is not configured for the active DL BWP in the scheduled cell, $Z_\mu$ is determined by the subcarrier spacing of the active DL BWP in the scheduling cell in slot $n$ , and given in Table 5.3.1-1, and $\mu_{PDCCH}$ and $\mu_{PDSCH}$ are the sub-carrier spacing configurations for PDCCH of the active DL BWP in the scheduling cell and PDSCH of the active DL BWP in the scheduled cell, respectively, in slot $n$ . After indication of a change to the applied $K_{0min}$ or $K_{2min}$ of the scheduled cell in slot $n$ of the scheduling cell, if there is an active DL BWP change in the scheduling cell before slot $n+X$ , the new $K_{0min}$ and/or $K_{2min}$ values are applied from the first slot no earlier than the start of slot $n+X$ based on the sub-carrier spacing configuration of the active DL BWP in the scheduling cell in slot $n$ . + +When the DCI format 0\_1, 0\_3, 1\_1 or 1\_3 with '*Minimum applicable scheduling offset indicator*' field is received outside the first three symbols of the slot, value of $Z_\mu$ from Table 5.3.1-1 is incremented by one before determining the application delay $X$ . When the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], for the purpose of determining '*Minimum applicable scheduling offset indicator*' field is received outside the first three symbols of the slot, the PDCCH candidate that ends later in time is used. + +**Table 5.3.1-1: Definition of $Z_\mu$** + +| \mu | Z_\mu | +|-------------------------|---------------------------| +| 0 | 1 | +| 1 | 1 | +| 2 | 2 | +| 3 | 2 | +| 5 | 8 | +| 6 | 16 | + +## 5.4 UE CSI computation time + +When the *CSI request* field on a DCI triggers a CSI report(s) on PUSCH, the UE shall provide a valid CSI report for the $n$ -th triggered report, + +- if the first uplink symbol to carry the corresponding CSI report(s) including the effect of the timing advance, starts no earlier than at symbol $Z_{ref}$ , and + +- if the first uplink symbol to carry the $n$ -th CSI report including the effect of the timing advance, starts no earlier than at symbol $Z'_{ref}(n)$ , + +where $Z_{ref}$ is defined as the next uplink symbol with its CP starting $T'_{proc,CSI} = (Z')(2048 + 144) \cdot \kappa 2^{-\mu} \cdot T_c + T_{switch}$ after the end of the last symbol of the PDCCH triggering the CSI report(s), and where $Z'_{ref}(n)$ , is defined as the next uplink symbol with its CP starting $T'_{proc,CSI} = (Z')(2048 + 144) \cdot \kappa 2^{-\mu} \cdot T_c$ after the end of the last symbol in time of the latest of: aperiodic CSI-RS resource for channel measurements, aperiodic CSI-IM used for interference measurements, and aperiodic NZP CSI-RS for interference measurement for a *CSI-ReportConfig*, or for all triggered sub-configurations if *CSI-ReportConfig* contains multiple sub-configurations, when aperiodic CSI-RS is used for channel measurement for the $n$ -th triggered CSI report, and where $T_{switch}$ is defined in clause 6.4 and is applied only if of table 5.4-1 is applied. + +If the PUSCH indicated by the DCI is overlapping with another PUCCH or PUSCH, then the CSI report(s) are multiplexed following the procedure in clause 9.2.5 of [6, TS 38.213] and clause 5.2.5 when applicable, otherwise the CSI report(s) are transmitted on the PUSCH indicated by the DCI. + +When the *CSI request* field on a DCI triggers a CSI report(s) on PUSCH, if the first uplink symbol to carry the corresponding CSI report(s) including the effect of the timing advance, starts earlier than at symbol $Z_{ref}$ , + +- the UE may ignore the scheduling DCI if no HARQ-ACK or transport block is multiplexed on the PUSCH. + +When the *CSI request* field on a DCI triggers a CSI report(s) on PUSCH, if the first uplink symbol to carry the $n$ -th CSI report including the effect of the timing advance, starts earlier than at symbol $Z'_{ref}(n)$ , + +- the UE may ignore the scheduling DCI if the number of triggered reports is one and no HARQ-ACK or transport block is multiplexed on the PUSCH +- Otherwise, the UE is not required to update the CSI for the $n$ -th triggered CSI report. + +When the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], for the purpose of determining the last symbol of the PDCCH triggering the CSI report(s), the PDCCH candidate that ends later in time is used. + +$Z$ , $Z'$ and $\mu$ are defined as: + +and , where $M$ is the number of updated CSI report(s) according to Clause 5.2.1.6, corresponds to the $m$ -th updated CSI report and is defined as + +- of the table 5.4-1 if $\max\{\mu_{PDCCH}, \mu_{CSI-RS}, \mu_{UL}\} \leq 3$ and if the CSI is triggered without a PUSCH with either transport block or HARQ-ACK or both when $L = 0$ CPUs are occupied (according to Clause 5.2.1.6) and the CSI to be transmitted is a single CSI and corresponds to wideband frequency-granularity where the CSI corresponds to at most 4 CSI-RS ports in a single resource without CRI report and where *CodebookType* is set to 'typeI-SinglePanel' or where *reportQuantity* is set to 'cri-RI-CQI', or +- of the table 5.4-2 if the CSI to be transmitted corresponds to wideband frequency-granularity where the CSI corresponds to at most 4 CSI-RS ports in a single resource without CRI report and where *CodebookType* is set to 'typeI-SinglePanel' or where *reportQuantity* is set to 'cri-RI-CQI', or +- of the table 5.4-2 if the CSI to be transmitted corresponds to wideband frequency-granularity where the *reportQuantity* is set to 'ssb-Index-SINR', 'cri-SINR', 'ssb-Index-SINR- Index ', or 'cri-SINR- Index ', or +- of the table 5.4-2 if *reportQuantity* is set to 'cri-RSRP', 'ssb-Index-RSRP', 'cri-RSRP- Index' or 'ssb-Index-RSRP- Index ', is according to UE reported capability *beamReportTiming* and $KB_i$ is according to UE reported capability *beamSwitchTiming* as defined in [13, TS 38.306], or +- or , according to UE reported capability, with of table 5.4-2, if *codebookType* is set to 'typeII-CJT-r18' or 'typeII-CJT-PortSelection-r18' and the corresponding *NZP-CSI-RS-ResourceSet* for channel measurement is configured with resources, or +- , with of table 5.4-2, if the CSI report is configured with , *codebookType* is set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18' and the corresponding *NZP-CSI-RS-ResourceSet* for channel measurement is aperiodic with CSI-RS resources, or + +- , with of table 5.4-2, if the CSI report is configured with , *codebookType* is set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18' and the corresponding *NZP-CSI-RS-ResourceSet* for channel measurement is periodic or semi-persistent with a single CSI-RS resource, or +- or , according to UE reported capability, with of table 5.4-2, if the CSI report is configured with , *codebookType* is set to 'typeII-Doppler-r18' and the corresponding *NZP-CSI-RS-ResourceSet* for channel measurement is aperiodic with CSI-RS resources, or +- or , according to UE reported capability, with of table 5.4-2, if the CSI report is configured with , *codebookType* is set to 'typeII-Doppler-r18' and the corresponding *NZP-CSI-RS-ResourceSet* for channel measurement is periodic or semi-persistent with a single CSI-RS resource, or +- of table 5.4-2 otherwise. +- $\mu$ of table 5.4-1 and table 5.4-2 corresponds to the $\min(\mu_{PDCCH}, \mu_{CSI-RS}, \mu_{UL})$ where the $\mu_{PDCCH}$ corresponds to the subcarrier spacing of the PDCCH with which the DCI was transmitted and $\mu_{UL}$ corresponds to the subcarrier spacing of the PUSCH with which the CSI report is to be transmitted and $\mu_{CSI-RS}$ corresponds to the minimum subcarrier spacing of the aperiodic CSI-RS triggered by the DCI + +**Table 5.4-1: CSI computation delay requirement 1** + +| $\mu$ | $Z_1$ [symbols] | | +|-------|-----------------|--------| +| | $Z_1$ | $Z'_1$ | +| 0 | 10 | 8 | +| 1 | 13 | 11 | +| 2 | 25 | 21 | +| 3 | 43 | 36 | + +**Table 5.4-2: CSI computation delay requirement 2** + +| $\mu$ | $Z_1$ [symbols] | | $Z_2$ [symbols] | | $Z_3$ [symbols] | | +|-------|-----------------|--------|-----------------|--------|-------------------------|--------| +| | $Z_1$ | $Z'_1$ | $Z_2$ | $Z'_2$ | $Z_3$ | $Z'_3$ | +| 0 | 22 | 16 | 40 | 37 | 22 | $X_0$ | +| 1 | 33 | 30 | 72 | 69 | 33 | $X_1$ | +| 2 | 44 | 42 | 141 | 140 | $\min(44, X_2 + KB_1)$ | $X_2$ | +| 3 | 97 | 85 | 152 | 140 | $\min(97, X_3 + KB_2)$ | $X_3$ | +| 5 | 388 | 340 | 608 | 560 | $\min(388, X_5 + KB_3)$ | $X_5$ | +| 6 | 776 | 680 | 1216 | 1120 | $\min(776, X_6 + KB_4)$ | $X_6$ | + +For a CSI report corresponding to a *CSI-ReportConfig* that contains a list of sub-configurations, provided by [*csi-ReportSubConfigList*], only of table 5.4-2 is applicable. + +## 5.5 UE PDSCH reception preparation time with cross carrier scheduling with different subcarrier spacings for PDCCH and PDSCH + +This clause applies only if the PDCCH carrying the scheduling DCI is received on one carrier with one OFDM subcarrier spacing ( $\mu_{PDCCH}$ ), and the PDSCH scheduled to be received by the DCI is on another carrier with another OFDM subcarrier spacing ( $\mu_{PDSCH}$ ). + +If the $\mu_{PDCCH} < \mu_{PDSCH}$ , the UE is expected to receive the scheduled PDSCH, if the first symbol in the PDSCH allocation, including the DM-RS, as defined by the slot offset $K_0$ and the start and length indicator *SLIV* of the scheduling DCI starts no earlier than the first symbol of the slot of the PDSCH reception starting at least $N_{pdsch}$ PDCCH symbols after the end of the PDCCH scheduling the PDSCH, not taking into account the effect of receive timing difference between the scheduling cell and the scheduled cell. + +If the $\mu_{PDCCH} > \mu_{PDSCH}$ , the UE is expected to receive the scheduled PDSCH, if the first symbol in the PDSCH allocation, including the DM-RS, as defined by the slot offset $K_0$ and the start and length indicator *SLIV* of the scheduling DCI starts no earlier than $N_{pdsch}$ PDCCH symbols after the end of the PDCCH scheduling the PDSCH, not taking into account the effect of receive timing difference between the scheduling cell and the scheduled cell. + +When the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], for the purpose of determining $N_{pdscb}$ , the PDCCH candidate that ends later in time is used. + +**Table 5.5-1: $N_{pdscb}$ as a function of the subcarrier spacing of the scheduling PDCCH** + +| $\mu_{PDCCH}$ | $N_{pdscb}$ [symbols] | +|---------------|-----------------------| +| 0 | 4 | +| 1 | 5 | +| 2 | 10 | +| 3 | 14 | +| 5 | 56 | +| 6 | 112 | + +# 6 Physical uplink shared channel related procedure + +## 6.1 UE procedure for transmitting the physical uplink shared channel + +PUSCH transmission(s) can be dynamically scheduled by an UL grant in a DCI, or the transmission can correspond to a configured grant Type 1 or Type 2. The configured grant Type 1 PUSCH transmission is semi-statically configured to operate upon the reception of higher layer parameter of *configuredGrantConfig* including *rrc-ConfiguredUplinkGrant* without the detection of an UL grant in a DCI. The configured grant Type 2 PUSCH transmission is semi-persistently scheduled by an UL grant in a valid activation DCI according to clause 10.2 of [6, TS 38.213] after the reception of higher layer parameter *configuredGrantConfig* not including *rrc-ConfiguredUplinkGrant*. If *configuredGrantConfigToAddModList* is configured, more than one configured grant configuration of configured grant Type 1 and/or configured grant Type 2 may be active at the same time on an active BWP of a serving cell. + +The UE can be configured with a list of up to 64 *TCI-UL-State* configurations within the higher layer parameter *BWP-UplinkDedicated*. Each *TCI-UL-State* configuration contains a parameter for configuring one reference signal, if applicable, for determining UL TX spatial filter for dynamic-grant and configured-grant based PUSCH and PUCCH resource in a CC, and SRS. + +If a UE is configured by higher layer parameter *PDCCH-Config* that contains *ControlResourceSets* with two different values of *coresetPoolIndex* for the active BWP of a serving cell, or if a UE is configured with *SSB-MTC-AdditionalPCI* and with *PDCCH-Config* that contains two different values of *coresetPoolIndex* in *ControlResourceSet*, and if the UE is configured with *[twoTAGs]* and is configured with *dl-OrJointTCI-StateList* or *TCI-UL-State* for a serving cell, each *TCI-State* or *TCI-UL-State* is associated with a *[TAG-ID]* for determining timing adjustment for a corresponding UL transmission as described in Clause 4.2 of [6, TS 38.213]. The UE does not expect that *TCI-states* or *TCI-UL-States* associated with one *coresetPoolIndex* to correspond to two TAGs. + +For the PUSCH transmission corresponding to a Type 1 configured grant or a Type 2 configured grant activated by DCI format 0\_0 or 0\_1, the parameters applied for the transmission are provided by *configuredGrantConfig* except for *dataScramblingIdentityPUSCH*, *txConfig*, *codebookSubset*, *maxRank*, *scaling* of *UCI-OnPUSCH*, which are provided by *pusch-Config*. A configured grant PUSCH can be transmitted with at most 4 layers. For the PUSCH transmission corresponding to a Type 2 configured grant activated by DCI format 0\_2, the parameters applied for the transmission are provided by *configuredGrantConfig* except for *dataScramblingIdentityPUSCH*, *txConfig*, *codebookSubsetDCI-0-2*, *maxRankDCI-0-2*, *scaling* of *UCI-OnPUSCH*, *resourceAllocationType1GranularityDCI-0-2* provided by *pusch-Config*. If the UE is provided with *transformPrecoder* in *configuredGrantConfig*, the UE applies the higher layer parameter *tp-pi2BPSK*, if provided in *pusch-Config*, according to the procedure described in clause 6.1.4 for the PUSCH transmission corresponding to a configured grant. + +When the UE is configured *dl-OrJointTCI-StateList* or *ul-TCI-StateList*, the UE shall perform PUSCH transmission corresponding to a Type 1 configured grant or a Type 2 configured grant or a dynamic grant according to the spatial relation, if applicable, with a reference to the RS for determining UL Tx spatial filter. The RS is determined based on an RS configured with *qcl-Type* set to 'typeD' of the indicated *TCI-State* or an RS in the indicated *TCI-UL-State*. The reference RS in the indicated *TCI-State* can be a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *repetition*, or a CSI-RS resource in an *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info*. The reference RS in the indicated *TCI-UL-State* can be a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *repetition*, a CSI-RS resource in an *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info*, an SRS resource in an SRS resource set with the higher layer parameter *usage* set to + +'beamManagement', or SS/PBCH block associated with the same or different PCI from the PCI of the serving cell. When *[nrofSlots\_InCGperiod]* is configured for Type 1 configured grant or Type 2 configured grant, HARQ process ID for the first configured PUSCH grant and each subsequent valid configured PUSCH grant within a *periodicity* of the configuration is determined as in clause 5.4.1 of [10, TS 38.321], where a valid configured PUSCH grant is the one not colliding with the DL symbol(s) indicated by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* if provided, and is not colliding with a symbol(s) of an SS/PBCH block with index provided by *ssb-PositionsInBurst* as described in clause 11.1 of [6, TS 38.213]. + +When a UE is configured with *dl-OrJointTCI-StateList* or *TCI-UL-State* and is having two indicated TCI-States or TCI-UL-States, + +- a UE having a PUSCH transmission scheduled or activated by DCI format 0\_0 should apply the first indicated TCI state to the PUSCH transmission, +- a UE configured with a PUSCH transmission corresponding to a Type 1 configured grant is expected to be configured with the higher layer parameter *applyIndicatedTCIState* indicating the *first*, the *second* or *both* of the indicated TCI states to be applied for the PUSCH transmission. If 'both' TCI states are indicated, the UE should apply the first indicated TCI state to the PUSCH transmission occasion(s) or the PUSCH antenna port(s) associated with the first SRS resource set for CB/NCB transmission, and the second indicated TCI state to the PUSCH transmission occasion(s) or the PUSCH antenna port(s) associated with the second SRS resource set for CB/NCB transmission; otherwise the UE should apply either the 'first' or 'second' indicated TCI state to all PUSCH transmission occasions. +- If the UE is configured by higher layer parameter *PDCCH-Config* that contains two different values of *coresetPoolIndex* in different *ControlResourceSets*, the first and the second indicated TCI states correspond to the indicated TCI-States or TCI-UL-States specific to coresetPoolIndex value 0 and value 1, respectively, and *applyIndicatedTCIState* does not indicate *both* of the indicated TCI states to be applied for the PUSCH transmission + +For the PUSCH retransmission scheduled by a PDCCH with CRC scrambled by CS-RNTI with NDI=1, the parameters in *pusch-Config* are applied for the PUSCH transmission except for *p0-NominalWithoutGrant*, *p0-PUSCH-Alpha*, *powerControlLoopToUse*, *pathlossReferenceIndex* described in clause 7.1 of [6, TS 38.213], *mcs-Table*, *mcs-TableTransformPrecoder* described in clause 6.1.4.1 and *transformPrecoder* described in clause 6.1.3. + +For a UE configured with two uplinks in a serving cell, PUSCH retransmission for a TB on the serving cell is not expected to be on a different uplink than the uplink used for the PUSCH initial transmission of that TB. + +A UE shall upon detection of a PDCCH with a configured DCI format 0\_0, 0\_1, 0\_2 or 0\_3 transmit the corresponding PUSCH as indicated by that DCI unless the UE does not generate a transport block as described in [10, TS38.321]. Upon detection of a DCI format 0\_1 or 0\_2 with '*UL-SCH indicator*' set to '0' and with a non-zero '*CSI request*' where the associated *reportQuantity* in *CSI-ReportConfig* set to '*none*' for all CSI report(s) triggered by '*CSI request*' in this DCI format 0\_1 or 0\_2, the UE ignores all fields in this DCI except the '*CSI request*' and the UE shall not transmit the corresponding PUSCH as indicated by this DCI format 0\_1 or 0\_2. Upon detection of a DCI format 0\_3 with '*UL-SCH indicator*' set to '0' and with a non-zero '*CSI request*' where the associated *reportQuantity* in *CSI-ReportConfig* set to '*none*' for all CSI report(s) triggered by '*CSI request*' in this DCI format 0\_3, the UE ignores all fields for the scheduled cell with the smallest serving cell index in this DCI except the '*CSI request*' and the UE shall not transmit the corresponding PUSCH on the serving cell with the smallest serving cell index as indicated by this DCI format 0\_3. + +When the UE is scheduled with multiple PUSCHs on a serving cell by a DCI, HARQ process ID indicated by this DCI applies to the first PUSCH not overlapping with a DL symbol indicated by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* if provided, or a symbol of an SS/PBCH block with index provided by *ssb-PositionsInBurst*, HARQ process ID is then incremented by 1 for each subsequent PUSCH(s) in the scheduled order, with modulo operation of *nrofHARQ-ProcessesForPUSCH* applied if *nrofHARQ-ProcessesForPUSCH* is provided, or with modulo operation of *nrofHARQ-ProcessesForPUSCH-r17* applied if *nrofHARQ-ProcessesForPUSCH-r17* is provided, or with modulo operation of 16 applied, otherwise. HARQ process ID is not incremented for PUSCH(s) not transmitted if at least one of the symbols indicated by the indexed row of the used resource allocation table in the slot overlaps with a DL symbol indicated by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* if provided, or a symbol of an SS/PBCH block with index provided by *ssb-PositionsInBurst*. For any HARQ process ID(s) in a given scheduled cell, the UE is not expected to transmit a PUSCH that overlaps in time with another PUSCH. Except for the case when a UE is configured by higher layer parameter *PDCCH-Config* that contains two different values of *coresetPoolIndex* in *ControlResourceSet* for the active BWP of a serving cell and PDCCHs that schedule two PUSCHs are associated to different *ControlResourceSets* having different values of *coresetPoolIndex*, for any two HARQ process IDs in a given scheduled cell, if the UE is scheduled to start a first PUSCH transmission starting in + +symbol $j$ by a PDCCH ending in symbol $i$ on a scheduling cell,, the UE is not expected to be scheduled to transmit a PUSCH starting earlier than the end of the first PUSCH by a PDCCH that ends later than symbol $i$ of the scheduling cell. When the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], for the purpose of determining the PDCCH ending in symbol $i$ , the PDCCH candidate that ends later in time is used. The UE is not expected to be scheduled to transmit another PUSCH by a DCI format 0\_0 with CRC scrambled by TC-RNTI, for a given HARQ process with the DCI received before the end of the expected transmission of the last PUSCH for that HARQ process if the latter is scheduled by a DCI format 0\_0 with CRC scrambled by TC-RNTI or by an UL grant in RA Response. The UE is not expected to be scheduled to transmit another PUSCH by DCI format 0\_0, 0\_1, 0\_2 or 0\_3 scrambled by C-RNTI, CS-RNTI or MCS-C-RNTI for a given HARQ process with the DCI received before the end of the expected transmission of the last PUSCH for that HARQ process if the latter is scheduled by a DCI with CRC scrambled by C-RNTI, CS-RNTI or MCS-C-RNTI. + +If a UE is configured by higher layer parameter *PDCCH-Config* that contains two different values of *coresetPoolIndex* in *ControlResourceSet* for the active BWP of a serving cell and PDCCHs that schedule two PUSCHs are associated to different *ControlResourceSets* having different values of *coresetPoolIndex*, for any two HARQ process IDs in a given scheduled cell, if the UE is scheduled to start a first PUSCH transmission starting in symbol $j$ by a PDCCH associated with a value of *coresetPoolIndex* ending in symbol $i$ , the UE can be scheduled to transmit a PUSCH starting earlier than the end of the first PUSCH by a PDCCH associated with a different value of *coresetPoolIndex* that ends later than symbol $i$ . + +When two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook' or 'nonCodebook' and higher layer parameter *enableSTx2PofmDCI* is configured and *PDCCH-Config* contains two different values of *coresetPoolIndex* in *ControlResourceSet* for the active BWP of a serving cell, + +- two PUSCHs that are fully/partially overlapping in time domain and are fully/partially/non-overlapping in frequency domain can be dynamically scheduled by UL grant(s) in DCI(s) and/or scheduled by configured grant(s) Type 1 or Type 2, +- if dynamically scheduled by UL grant(s) in DCI(s) or activated by DCI(s) for configured grant Type 2, the DCI field *SRS Resource Set Indicator* is not present in each of PDCCH +- two PUSCHs are associated to different values of *coresetPoolIndex* where for configured grant Type 1, the association is based on higher layer parameter *srs-ResourceSetId* in *rrc-ConfiguredUplinkGrant* that indicates either the first or the second SRS resource set with usage 'codebook' or 'nonCodeBook' in *srs-ResourceSetToAddModList* +- the UE is not expected to be configured with different number of SRS resources in the two SRS resource sets +- the UE expects *maxNrofPorts* in *PTRS-UplinkConfig* to be configured as one if UL PT-RS is configured. + +When a UE is configured with *dl-OrJointTCI-StateList* or *TCI-UL-State* and two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook' or 'noncodebook', and the higher layer parameter *multipanelScheme* is set to 'SDMscheme' or 'SFNscheme', and the higher layer parameter *rrc-ConfiguredUplinkGrant* does not contain *srs-ResourceIndicator2* or *precodingAndNumberOfLayers2*, the PUSCH transmission occasion(s) is associated with the first SRS resource set if the first indicated *TCI-States* or *TCI-UL-States* applies and is associated with the second SRS resource set if the second indicated *TCI-States* or *TCI-UL-States* applies. + +When a UE is configured with *dl-OrJointTCI-StateList* or *TCI-UL-State* is having two indicated TCI states, and only one SRS resource set is configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook' or 'noncodebook', the PUSCH transmission occasion(s) scheduled or activated by DCI format 0\_1 or 0\_2 is associated with the first indicated *TCI-States* or *TCI-UL-States* if applies or is associated with the second indicated *TCI-States* or *TCI-UL-States* if applies, as indicated by the higher layer parameter *applyIndicatedTCIState-r18* configured by *PUSCH-Config*. + +When a UE is configured with higher layer parameter *enableSTx2PofmDCI* and *PDCCH-Config* contains two different values of *coresetPoolIndex* in *ControlResourceSet* for the active BWP of a serving cell, + +- the UE is expected to be configured with two SRS resource sets with usage 'codebook' or 'nonCodeBook' in *srs-ResourceSetToAddModList* + +- if the UE is configured to monitor DCI format 0\_2 and there is only one SRS resource sets configured by *srs-ResourceSetToAddModListDCI-0-2* and associated with usage 'codebook' or 'nonCodebook', the UE monitors only *coresetPoolIndex* configured with value 0. + +A UE is not expected to be scheduled by a PDCCH ending in symbol to transmit a PUSCH on a given serving cell overlapping in time with a transmission occasion, where the UE is allowed to transmit a PUSCH with configured grant according to [10, TS38.321], starting in a symbol on the same serving cell if the end of symbol is not at least symbols before the beginning of symbol , if + +- the UE is not provided *prioLowDG-HighCG* or *prioHighDG-LowCG*, or the UE is provided *prioLowDG-HighCG* or *prioHighDG-LowCG* and the two PUSCHs have the same priority index as described in Clause 9 of [6, TS 38.213] and +- the UE is not provided *enableSTx2PofmDCI*, or is provided *enableSTx2PofmDCI* and the two PUSCHs are associated with the same *coresetPoolIndex* value. + +The value in symbols is determined according to the UE processing capability defined in Clause 6.4, and and the symbol duration are based on the minimum of the subcarrier spacing corresponding to the PUSCH with configured grant and the subcarrier spacing of the PDCCH scheduling the PUSCH. + +If a UE receives an ACK for a given HARQ process in CG-DFI in a PDCCH ending in symbol *i* to terminate a transport block repetition in a PUSCH transmission with a configured grant on a given serving cell with the same HARQ process after symbol *i*, the UE is expected to terminate the repetition of the transport block in a PUSCH transmission starting from a symbol *j* if the gap between the end of PDCCH of symbol *i* and the start of the PUSCH transmission in symbol *j* is equal to or more than *N2* symbols. The value *N2* in symbols is determined according to the UE processing capability defined in Clause 6.4, and *N2* and the symbol duration are based on the minimum of the subcarrier spacing corresponding to the PUSCH and the subcarrier spacing of the PDCCH indicating CG-DFI. A UE is not expected to be scheduled by a PDCCH ending in symbol to transmit a PUSCH on a given serving cell for a given HARQ process, if there is a transmission occasion where the UE is allowed to transmit a PUSCH with configured grant according to [10, TS38.321] with the same HARQ process on the same serving cell starting in a symbol after symbol , and if the gap between the end of PDCCH and the beginning of symbol is less than symbols. The value in symbols is determined according to the UE processing capability defined in clause 6.4, and and the symbol duration are based on the minimum of the subcarrier spacing corresponding to the PUSCH with configured grant and the subcarrier spacing of the PDCCH scheduling the PUSCH. + +For PUSCH scheduled by DCI format 0\_0 on a cell, the UE shall transmit PUSCH according to the spatial relation, if applicable, corresponding to the dedicated PUCCH resource with the lowest ID within the active UL BWP of the cell, as described in Clause 9.2.1 of [6, TS 38.213]. If the dedicated PUCCH resource with the lowest ID within the active UL BWP of the cell corresponds to two spatial relations, the UE shall transmit the PUSCH according to the spatial relation with the lower ID. + +For PUSCH scheduled by DCI format 0\_0 on a cell and if the higher layer parameter *enableDefaultBeamPL-ForPUSCH0-0* is set 'enabled', the UE is not configured with PUCCH resources on the active UL BWP and the UE is in RRC connected mode, the UE shall transmit PUSCH according to the spatial relation, if applicable, with a reference to the RS configured with *qcl-Type* set to 'typeD' corresponding to the QCL assumption of the CORESET with the lowest ID on the active DL BWP of the cell. If the CORESET is indicated with two TCI states, *sfnSchemePdcch* is configured and the UE supports *sfn-DefaultUL-BeamSetup-r17*, the UE shall use the first TCI state as the QCL assumption. + +For PUSCH scheduled by DCI format 0\_0 on a cell and if the higher layer parameter *enableDefaultBeamPL-ForPUSCH0-0* is set 'enabled', the UE is configured with PUCCH resources on the active UL BWP where all the PUCCH resource(s) are not configured with any spatial relation and the UE is in RRC connected mode, the UE shall transmit PUSCH according to the spatial relation, if applicable, with a reference to the RS configured with *qcl-Type* set to 'typeD' corresponding to the QCL assumption of the CORESET with the lowest ID on the active DL BWP of the cell in case CORESET(s) are configured on the cell. If the CORESET is indicated with two TCI states, *sfnSchemePdcch* is configured and the UE supports *sfn-DefaultUL-BeamSetup-r17*, the UE shall use the first TCI state as the QCL assumption. + +For uplink, 16 HARQ processes per cell are supported by the UE, or subject to UE capability, a maximum of 32 HARQ processes per cell as defined in [13, TS 38.306]. The number of processes the UE may assume will at most be used for the uplink is configured to the UE for each cell separately by higher layer parameter *nrofHARQ-ProcessesForPUSCH*, + +or *nrofHARQ-ProcessesForPUSCH-r17*, and when no configuration is provided the UE may assume a default number of 16 processes. + +### 6.1.1 Transmission schemes + +Two transmission schemes are supported for PUSCH: codebook based transmission and non-codebook based transmission. The UE is configured with codebook based transmission when the higher layer parameter *txConfig* in *pusch-Config* is set to 'codebook', the UE is configured non-codebook based transmission when the higher layer parameter *txConfig* is set to 'nonCodebook'. If the higher layer parameter *txConfig* is not configured, the UE is not expected to be scheduled by DCI format 0\_1, 0\_2 or 0\_3. If PUSCH is scheduled by DCI format 0\_0, the PUSCH transmission is based on a single antenna port. Except if the higher layer parameter *enableDefaultBeamPL-ForPUSCH0-0* is set 'enabled', the UE shall not expect PUSCH scheduled by DCI format 0\_0 in a BWP without configured PUCCH resource with *PUCCH-SpatialRelationInfo* in frequency range 2 in RRC connected mode. + +#### 6.1.1.1 Codebook based UL transmission + +For codebook based transmission, PUSCH can be scheduled by DCI format 0\_0, DCI format 0\_1, DCI format 0\_2, DCI format 0\_3 or semi-statically configured to operate according to Clause 6.1.2.3. If this PUSCH is scheduled by DCI format 0\_1, DCI format 0\_2, or semi-statically configured to operate according to Clause 6.1.2.3, the UE determines its PUSCH transmission precoder(s) based on SRI(s), TPMI(s) and the transmission rank, where the SRI(s), TPMI(s) and the transmission rank are given by DCI fields of one or two SRS resource indicators and one or two Precoding information and number of layers in clause 7.3.1.1.2 and 7.3.1.1.3 of [5, TS 38.212] for DCI format 0\_1 and 0\_2 or given by *srs-ResourceIndicator* and *precodingAndNumberOfLayers* according to clause 6.1.2.3 or given by *srs-ResourceIndicator*, *srs-ResourceIndicator2*, *precodingAndNumberOfLayers*, and *precodingAndNumberOfLayers2* according to clause 6.1.2.3. If this PUSCH is scheduled by DCI format 0\_3, the UE determines its PUSCH transmission precoder based on SRI, TPMI and the transmission rank, where the SRI, TPMI and the transmission rank are given by DCI fields of one SRS resource indicator and one Precoding information and number of layers in clause 7.3.1.1.4 of [5, TS 38.212] for DCI format 0\_3. The *SRS-ResourceSet(s)* applicable for PUSCH scheduled by DCI format 0\_1 and DCI format 0\_2 are defined by the entries of the higher layer parameter *srs-ResourceSetToAddModList* and *srs-ResourceSetToAddModListDCI-0-2* in *SRS-config*, respectively. Only one or two SRS resource sets can be configured in *srs-ResourceSetToAddModList* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook', and only one or two SRS resource sets can be configured in *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook'. + +When only one SRS resource set is configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook', SRI and TPMI are given by the DCI fields of one SRS resource indicator and one Precoding information and number of layers in clauses 7.3.1.1.2, 7.3.1.1.3 and 7.3.1.1.4 of [5, TS 38.212] for DCI format 0\_1, 0\_2 and 0\_3 or given by *srs-ResourceIndicator* and *precodingAndNumberOfLayers* according to clause 6.1.2.3. When two SRS resource sets are configured in *srs-ResourceSetToAddModList* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook', SRI and TPMI are given by the DCI fields of one SRS resource indicator and one Precoding information and number of layers in clause 7.3.1.1.4 of [5, TS 38.212] for DCI format 0\_3 and the UE applies the indicated SRI and TPMI to one or more PUSCH repetitions according to the first SRS resource set. The TPMI is used to indicate the precoder to be applied over the layers $\{0 \dots v-1\}$ and that corresponds to the SRS resource selected by the SRI when multiple SRS resources are configured, or if a single SRS resource is configured TPMI is used to indicate the precoder to be applied over the layers $\{0 \dots v-1\}$ and that corresponds to the SRS resource. The transmission precoder is selected from the uplink codebook that has a number of antenna ports equal to higher layer parameter *nrofSRS-Ports* in *SRS-Config*, as defined in Clause 6.3.1.5 of [4, TS 38.211]. When the UE is configured with the higher layer parameter *txConfig* set to 'codebook', the UE is configured with at least one SRS resource. The indicated SRI in slot *n* is associated with the most recent transmission of SRS resource identified by the SRI, where the SRS resource is prior to the PDCCH carrying the SRI. + +When two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook', one or two SRI(s), and one or two TPMI(s) are given by the DCI fields of two SRS resource indicator and two Precoding information and number of layers in clause 7.3.1.1.2 and 7.3.1.1.3 of [5, TS 38.212] for DCI format 0\_1 and 0\_2. The UE applies the indicated SRI(s) and TPMI(s) to one or more PUSCH repetitions according to the associated SRS resource set of a PUSCH repetition according to clause 6.1.2.1. Each TPMI, based on indicated codepoint of *SRS Resource Set indicator*, is used to indicate the precoder to be applied over the layers $\{0 \dots v-1\}$ and that corresponds to the SRS resource selected by the corresponding SRI when multiple SRS resources are configured for the applicable SRS resource set, or if a single SRS resource is configured for the applicable SRS resource set TPMI is used to indicate the precoder to be applied over the layers $\{0 \dots v-1\}$ and that corresponds to the SRS resource. For one or two TPMI(s), the transmission precoder is + +selected from the uplink codebook that has a number of antenna ports equal to the higher layer parameter *nrofSRS-Ports* in *SRS-Config* for the indicated SRI(s), as defined in Clause 6.3.1.5 of [4, TS 38.211]. When two SRIs are indicated, the UE shall expect the *nrofSRS-Ports* for the two indicated SRS resources to be the same. When the UE is configured with the higher layer parameter *txConfig* set to 'codebook', the UE is configured with at least one SRS resource. Each of the indicated one or two SRI(s) in slot *n* is associated with the most recent transmission of SRS resource of associated SRS resource set identified by the SRI, where the SRS resource is prior to the PDCCH carrying the SRI. When two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook', the UE is not expected to be configured with different number of SRS resources in the two SRS resource sets. + +When the higher layer parameter *multipanelScheme* is set to 'SDMScheme' and two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook', two SRI(s), and two TPMI(s) are given by the DCI fields of two SRS resource indicator and two Precoding information and number of layers in clause 7.3.1.1.2 and 7.3.1.1.3 of [5, TS 38.212] for DCI format 0\_1 and 0\_2: + +- When codepoint "10" of *SRS Resource Set indicator* is indicated, the first TPMI is used to indicate the precoder to be applied over layers $\{0 \dots v_1-1\}$ , where $v_1$ is the number of layers indicated by the first TPMI, that corresponds to the SRS resource selected by the corresponding SRI when multiple SRS resources are configured for the applicable SRS resource set or if single SRS resource is configured for the applicable SRS resource set, and the second TPMI is used to indicate the precoder to be applied over layers $\{v_1 \dots v_2+v_1-1\}$ , where $v_2$ is the number of layers indicated by the second TPMI, that corresponds to the SRS resource selected by the corresponding SRI when multiple SRS resources are configured for the applicable SRS resource set or if single SRS resource is configured for the applicable SRS resource set, $v_1 \leq \maxRankSdm$ and $v_2 \leq \maxRankSdm$ or $\maxRankSdmDCI-0-2$ and $\maxRankSdm$ or $\maxRankSdmDCI-0-2$ are defining the maximum number of layers applied over the first and the second SRS resource sets, separately. +- When codepoint "00" or "01" of *SRS Resource Set indicator* is indicated, the second SRI and second TPMI are reserved, the first TPMI is used to indicate the precoder to be applied over layers $\{0 \dots v-1\}$ , where $v \leq \maxRank$ , where $\maxRank$ is defining the maximum number of layers. +- Codepoint "11" of *SRS Resource Set indicator* is reserved. +- For one or two TPMI(s), the transmission precoder is selected from the uplink codebook that has a number of antenna ports equal to the higher layer parameter *nrofSRS-Ports* in *SRS-Config* for the indicated SRI(s), as defined in Clause 6.3.1.5 of [4, TS 38.211]. When two TPMIs are indicated, the UE shall expect that the precoder indicated by the first TPMI and the precoder indicated by the second TPMI are mapped to different PUSCH antenna ports. +- When two SRIs are indicated, the UE shall expect that the number of SRS antenna ports associated with two indicated SRIs would be the same. When the UE is configured with the higher layer parameter *txConfig* set to 'codebook', the UE is configured with at least one SRS resource. Each of the indicated one or two SRI(s) in slot *n* is associated with the most recent transmission of SRS resource of associated SRS resource set identified by the SRI, where the SRS resource is prior to the PDCCH carrying the SRI. When two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook', the UE is not expected to be configured with different number of SRS resources in the two SRS resource sets. + +When higher layer parameter *multipanelScheme* set to 'SFNScheme' and two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook', two SRI(s), and two TPMI(s) are given by the DCI fields of two SRS resource indicator and two Precoding information and number of layers in clause 7.3.1.1.2 and 7.3.1.1.3 of [5, TS 38.212] for DCI format 0\_1 and 0\_2. + +- When codepoint "10" of *SRS Resource Set indicator* is indicated, the first TPMI is used to indicate precoder to be applied over layers $\{0 \dots v-1\}$ and the second TPMI is used to indicate the precoder to be applied over layers $\{0 \dots v-1\}$ , where $v \leq \maxRankSfn$ or $\maxRankSfnDCI-0-2$ and $\maxRankSfn$ or $\maxRankSfnDCI-0-2$ defining the maximum number of layers applied over the first SRS resource set and over the second SRS resource set separately. +- When codepoint "00" or "01" of *SRS Resource Set indicator* is indicated, the second SRI and second TPMI are reserved, the first TPMI is used to indicate precoder to be applied over layers $\{0 \dots v-1\}$ , where $v \leq \maxRank$ and + +where *maxRank* is defining the maximum number of layers applied over the first SRS resource set or the second SRS resource. + +- Codepoint "11" of *SRS Resource Set indicator* is reserved. +- For one or two TPMI(s), the transmission precoder is selected from the uplink codebook that has a number of antenna ports equal to *nrofSRS-Ports* in *SRS-Config* for the indicated SRI(s), as defined in Clause 6.3.1.5 of [4, TS 38.211]. When two TPMIs are indicated, the UE shall expect that the precoder indicated by the first TPMI and the precoder indicated by the second TPMI are mapped to different PUSCH antenna ports. +- When two TPMIs are indicated, the UE shall expect that the number of SRS antenna ports associated with two indicated SRIs to be the same. When the UE is configured with the higher layer parameter *txConfig* set to 'codebook', the UE is configured with at least one SRS resource. Each of the indicated one or two SRI(s) in slot *n* is associated with the most recent transmission of SRS resource of associated SRS resource set identified by the SRI, where the SRS resource is prior to the PDCCH carrying the SRI. When two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook', the UE is not expected to be configured with different number of SRS resources in the two SRS resource sets. + +When the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], for the purpose of determining the most recent transmission of SRS resource identified by the SRI, the PDCCH candidate that starts earlier in time is used. + +For codebook based transmission with two or four antenna ports, the UE determines its codebook subsets based on TPMI(s) and upon the reception of higher layer parameter *codebookSubset* in *pusch-Config* for PUSCH associated with DCI format 0\_1 or 0\_3 and *codebookSubsetDCI-0-2* in *pusch-Config* for PUSCH associated with DCI format 0\_2 which may be configured with 'fullyAndPartialAndNonCoherent', or 'partialAndNonCoherent', or 'nonCoherent' depending on the UE capability for two or four antenna ports. + +For codebook based transmission with eight antenna ports, the UE determines its codebook based upon the reception of higher layer parameter[s] *CodebookType* and *ULcodebookFC-N1N2* if *CodebookType* is configured with *Ng=1* in *pusch-Config* for PUSCH associated with DCI format 0\_1 and 0\_2, depending on the UE capability. According to the configured *CodebookType*, coherent UL MIMO operation applies within antenna port groups as defined in Table 6.3.1.5-8 of [4, TS 38.211]. + +When higher layer parameter *ul-FullPowerTransmission* is set to 'fullpowerMode2' and the higher layer parameter *codebookSubset* or the higher layer parameter *codebookSubsetDCI-0-2* is set to 'partialAndNonCoherent', and when the *SRS-resourceSet* with *usage* set to "codebook" includes at least one SRS resource with 4 ports and one SRS resource with 2 ports, the *codebookSubset* associated with the 2-port SRS resource is 'nonCoherent'. + +When higher layer parameter *ul-FullPowerTransmission* is set to 'fullpowerMode2' and the higher layer parameter *codebookType* is set to 'Codebook2' or 'Codebook3', and the *SRS-resourceSet* with *usage* set to 'codebook' includes one SRS resource with 8 ports, and at least one SRS resource with 2 ports or 4 ports, subject to UE capability, + +- when *codebookType* is set to 'Codebook2', the *codebookSubset* associated with the 2-port SRS resource is 'nonCoherent'. +- when *codebookType* is set to 'Codebook2', the *codebookSubset* associated with the 4-port SRS resource can be configured as 'partialAndNonCoherent' or 'nonCoherent', subject to UE capability. +- when *codebookType* is set to 'Codebook3', the *codebookSubset* associated with 4 ports SRS resources is 'nonCoherent'. + +The maximum transmission rank may be configured by the higher layer parameter *maxRank* in *pusch-Config* for PUSCH scheduled with DCI format 0\_1 or 0\_3 and *maxRankDCI-0-2* for PUSCH scheduled with DCI format 0\_2. + +A UE reporting its UE capability of 'partialAndNonCoherent' transmission shall not expect to be configured by either *codebookSubset* or *codebookSubsetDCI-0-2* with 'fullyAndPartialAndNonCoherent' for two or four antenna ports. + +A UE reporting its UE capability of 'nonCoherent' transmission shall not expect to be configured by either *codebookSubset* or *codebookSubsetDCI-0-2* with 'fullyAndPartialAndNonCoherent' or with 'partialAndNonCoherent' for two or four antenna ports. + +A UE does not expect to be configured by *CodebookType* with a value of *CodebookType* that does not correspond to one of the values of *UL\_8TX\_Ng* reported in its capability. A UE can be configured by *ULcodebookFC-N1N2* subject to + +UE capability, when higher layer parameter *CodebookType* is set to 'Codebook1' corresponding to $N_g=1$ , where $N_g$ represents the number of antenna port-groups. + +A UE shall not expect to be configured with the higher layer parameter *codebookSubset* or the higher layer parameter *codebookSubsetDCI-0-2* set to 'partialAndNonCoherent' when higher layer parameter *nrofSRS-Ports* in an *SRS-ResourceSet* with *usage* set to 'codebook' indicates that the maximum number of the configured SRS antenna ports in the *SRS-ResourceSet* is two. + +For codebook based transmission, only one SRS resource can be indicated based on the SRI from within the SRS resource set. Except when higher layer parameter *ul-FullPowerTransmission* is set to 'fullpowerMode2', the maximum number of configured SRS resources for codebook based transmission is 2. If aperiodic SRS is configured for a UE, the SRS request field in DCI triggers the transmission of aperiodic SRS resources. + +A UE shall not expect to be configured with higher layer parameter *ul-FullPowerTransmission* set to 'fullpowerMode1' and *codebookSubset* or *codebookSubsetDCI-0-2* set to 'fullAndPartialAndNonCoherent' simultaneously. + +A UE shall not expect to be configured with higher layer parameter *ul-FullPowerTransmission* set to 'fullpowerMode1' and *CodebookType* set to 'Codebook1' simultaneously. + +The UE shall transmit PUSCH using the same antenna port(s) as the SRS port(s) in the SRS resource(s) indicated by the DCI format 0\_1, 0\_2 or 0\_3 or by *configuredGrantConfig* according to clause 6.1.2.3. + +The DM-RS antenna ports $\{\tilde{p}_0, \dots, \tilde{p}_{v-1}\}$ in Clause 6.4.1.1.3 of [4, TS38.211] are determined according to the ordering of DM-RS port(s) given by Tables 7.3.1.1.2-6 to 7.3.1.1.2-23 in Clause 7.3.1.1.2 of [5, TS 38.212]. + +Except when higher layer parameter *ul-FullPowerTransmission* is set to 'fullpowerMode2', when multiple SRS resources are configured by *SRS-ResourceSet* with *usage* set to 'codebook', the UE shall expect that higher layer parameters *nrofSRS-Ports* in *SRS-Resource* in *SRS-ResourceSet* shall be configured with the same value for all these SRS resources. + +When higher layer parameter *ul-FullPowerTransmission* is set to 'fullpowerMode2', + +- the UE can be configured with one SRS resource or multiple SRS resources with same or different number of SRS ports within an SRS resource set with *usage* set to 'codebook'. +- up to 2 different spatial relations can be configured for all SRS resources in the SRS resource set with *usage* set to 'codebook' when multiple SRS resources are configured in the SRS resource set. +- subject to UE capability, a maximum of 2 or 4 SRS resources are supported in an SRS resource set with *usage* set to 'codebook'. + +#### 6.1.1.2 Non-Codebook based UL transmission + +For non-codebook based transmission, PUSCH can be scheduled by DCI format 0\_0, DCI format 0\_1, DCI format 0\_2, DCI format 0\_3 or semi-statically configured to operate according to Clause 6.1.2.3. If this PUSCH is scheduled by DCI format 0\_1, DCI format 0\_2, DCI format 0\_3 or semi-statically configured to operate according to Clause 6.1.2.3, the UE can determine its PUSCH precoder(s) and transmission rank based on the SRI(s) when multiple SRS resources are configured, where the SRI(s) is given by one or two SRS resource indicator(s) in DCI according to clause 7.3.1.1.2 and 7.3.1.1.3 of [5, 38.212] for DCI format 0\_1 and DCI format 0\_2, or the SRI is given by one SRS resource indicator in DCI according to clause 7.3.1.1.4 of [5, 38.212] for DCI format 0\_3, or the SRI is given by *srs-ResourceIndicator* according to clause 6.1.2.3, or SRIs given by *srs-ResourceIndicator* and *srs-ResourceIndicator2* according to clause 6.1.2.3. The *SRS-ResourceSet(s)* applicable for PUSCH scheduled by DCI format 0\_1 and DCI format 0\_2 are defined by the entries of the higher layer parameter *srs-ResourceSetToAddModList* and *srs-ResourceSetToAddModListDCI-0-2* in *SRS-config*, respectively. The UE shall use one or multiple SRS resources for SRS transmission, where, in a SRS resource set, the maximum number of SRS resources which can be configured to the UE for simultaneous transmission in the same symbol and the maximum number of SRS resources are UE capabilities. The SRS resources transmitted simultaneously occupy the same RBs. Only one SRS port for each SRS resource is configured. Only one or two SRS resource sets can be configured in *srs-ResourceSetToAddModList* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'nonCodebook', and only one or two SRS resource sets can be configured in *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'nonCodebook'. When two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'nonCodebook', SRIs are given by the DCI fields of two SRS resource indicators in clauses 7.3.1.1.2 and 7.3.1.1.3 of [5, TS 38.212] for DCI format 0\_1 and 0\_2 and the UE applies + +the indicated SRI(s) to one or more PUSCH repetitions according to the associated SRS resource set of a PUSCH repetition according to clause 6.1.2.1. When two SRS resource sets are configured in *srs-ResourceSetToAddModList* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'nonCodebook', SRI is given by the DCI field of one SRS resource indicator in clause 7.3.1.1.4 of [5, TS 38.212] for DCI format 0\_3 and the UE applies the indicated SRI to one or more PUSCH repetitions according to the first SRS resource set. The maximum number of SRS resources per SRS resource set that can be configured for non-codebook based uplink transmission is 1, 2, 4 or 8 depending on UE capability. Each of the indicated SRIs in slot $n$ is associated with the most recent transmission of SRS resource(s) of associated SRS resource set identified by the SRI, where the SRS transmission is prior to the PDCCH carrying the SRI. When two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'nonCodebook', the UE is not expected to be configured with different number of SRS resources in the two SRS resource sets. + +When the higher layer parameter *multipanelScheme* is set to 'SDMScheme' and two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'nonCodebook', SRIs are given by the DCI fields of two SRS resource indicators in clause 7.3.1.1.2 and 7.3.1.1.3 of [5, TS 38.212] for DCI format 0\_1 and 0\_2. + +- When codepoint "10" of *SRS Resource Set indicator* is indicated, the first SRI is used to indicate resource(s) to be associated with layer(s) $\{0 \dots v_1-1\}$ , where $v_1$ being the number of layers indicated by the first SRI, and the second SRI is used to indicate resource(s) to be associated with layer(s) $\{v_1 \dots v_2+v_1-1\}$ , $v_1 \leq L_{max}$ and $v_2 \leq L_{max}$ where $L_{max}$ is defined in clauses 7.3.1.1.2 and 7.3.1.1.3 of [5, TS 38.212]. The UE shall expect that SRS resource(s) indicated by the first SRI and SRS resource(s) indicated by the second SRI are corresponding to different PUSCH antenna ports. +- When codepoint "00" or "01" of *SRS Resource Set indicator* is indicated, the second SRI is reserved, the first SRI is used to indicate resource(s) to be associated with layers $\{0 \dots v-1\}$ , $v \leq L_{max}$ . + +When the higher layer parameter *multipanelScheme* is set to 'SFNScheme' and two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'nonCodebook', two SRI(s) are given by the DCI fields of two SRS resource indicator and two Precoding information and number of layers in clause 7.3.1.1.2 and 7.3.1.1.3 of [5, TS 38.212] for DCI format 0\_1 and 0\_2. + +- When codepoint "10" of *SRS Resource Set indicator* is indicated, the first SRI is used to indicate resource(s) to be associated with layer(s) $\{0 \dots v-1\}$ and the second SRI is used to indicate resource(s) to be associated with layer(s) $\{0 \dots v-1\}$ , where $v \leq L_{max}$ and where $L_{max}$ is defined in clauses 7.3.1.1.2 and 7.3.1.1.3 of [5, TS 38.212]. The UE shall expect that SRS resource(s) indicated by the first SRI and SRS resource(s) indicated by the second SRI are corresponding to different PUSCH antenna ports. +- When codepoint "00" or "01" of *SRS Resource Set indicator* is indicated, the second SRI is reserved, the first SRI is used to indicate resources(s) to be associated with layers $\{0 \dots v-1\}$ , where $v \leq L_{max}$ . When two SRIs are indicated, the UE shall expect that the number of SRS antenna ports associated with two indicated SRIs to be the same. +- Codepoint "11" of *SRS Resource Set indicator* is reserved. + +When the UE is configured with the higher layer parameter *txConfig* set to 'Noncodebook', the UE is configured with at least one SRS resource. Each of the indicated one or two SRI(s) in slot $n$ is associated with the most recent transmission of SRS resource of associated SRS resource set identified by the SRI, where the SRS resource is prior to the PDCCH carrying the SRI. When two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'Noncodebook', the UE is not expected to be configured with different number of SRS resources in the two SRS resource sets. + +When the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], for the purpose of determining the most recent transmission of SRS resource(s) identified by the SRI, the PDCCH candidate that starts earlier in time is used. + +For non-codebook based transmission, the UE can calculate the precoder used for the transmission of SRS based on measurement of an associated NZP CSI-RS resource. A UE can be configured with only one NZP CSI-RS resource for each of the SRS resource set(s) with higher layer parameter *usage* in *SRS-ResourceSet* set to 'nonCodebook' if configured. + +- If aperiodic SRS resource set is configured, the associated NZP-CSI-RS is indicated via SRS request field in DCI format 0\_1 and 1\_1, DCI format 0\_2 (if SRS request field is present) and DCI format 1\_2 (if SRS request + +field is present), as well as DCI format 0\_3 and 1\_3, where *AperiodicSRS-ResourceTrigger* and *AperiodicSRS-ResourceTriggerList* (indicating the association between aperiodic SRS triggering state(s) and SRS resource sets), triggered SRS resource(s) *srs-ResourceSetId*, *csi-RS* (indicating the associated *NZP-CSI-RS-ResourceId*) are higher layer configured in *SRS-ResourceSet*. The *SRS-ResourceSet(s)* associated with the SRS request by DCI format 0\_1, 0\_3, 1\_1 and 1\_3 are defined by the entries of the higher layer parameter *srs-ResourceSetToAddModList* and the *SRS-ResourceSet(s)* associated with the SRS request by DCI format 0\_2 and 1\_2 are defined by the entries of the higher layer parameter *srs-ResourceSetToAddModListDCI-0-2*. A UE is not expected to update the SRS precoding information if the gap from the last symbol of the reception of the aperiodic NZP-CSI-RS resource and the first symbol of the aperiodic SRS transmission is less than 42 OFDM symbols, where the SCS configuration $\mu$ is the smallest SCS configuration between the NZP-CSI-RS resource and the SRS transmission. + +- If the UE configured with aperiodic SRS associated with aperiodic NZP CSI-RS resource, the presence of the associated CSI-RS is indicated by the SRS request field if the value of the SRS request field is not '00' as in Table 7.3.1.1.2-24 of [5, TS 38.212] and if the scheduling DCI is not used for cross carrier or cross bandwidth part scheduling. If UE is configured with *minimumSchedulingOffsetK0* in the active DL BWP and the currently applicable minimum scheduling offset restriction $K_{0,min}$ is larger than 0, the UE does not expected to receive the scheduling DCI with the SRS request field value other than '00'. The CSI-RS is located in the same slot as the SRS request field. If the UE configured with aperiodic SRS associated with aperiodic NZP CSI-RS resource, any of the TCI states configured in the scheduled CC shall not be configured with *qcl-Type* set to 'typeD'. +- If periodic or semi-persistent SRS resource set is configured, the *NZP-CSI-RS-ResourceId* for measurement is indicated via higher layer parameter *associatedCSI-RS* in *SRS-ResourceSet*. + +The UE shall perform one-to-one mapping from the indicated SRI(s) to the indicated DM-RS ports(s) and their corresponding PUSCH layers $\{0 \dots v-1\}$ given by DCI format 0\_1, 0\_2 or 0\_3 or by *configuredGrantConfig* according to clause 6.1.2.3 in increasing order. + +The UE shall transmit PUSCH using the same antenna ports as the SRS port(s) in the SRS resource(s) indicated by SRI(s) given by DCI format 0\_1 or 0\_2 or by *configuredGrantConfig* according to clause 6.1.2.3, where the SRS port in $(i+1)$ -th SRS resource in the SRS resource set is indexed as $p_i = 1000 + i$ . + +The DM-RS antenna ports $\{\tilde{p}_0, \dots, \tilde{p}_{v-1}\}$ in Clause 6.4.1.1.3 of [4, TS 38.211] are determined according to the ordering of DM-RS port(s) given by Tables 7.3.1.1.2-6 to 7.3.1.1.2-23 in Clause 7.3.1.1.2 of [5, TS 38.212]. + +For non-codebook based transmission, the UE does not expect to be configured with both *spatialRelationInfo* for SRS resource and *associatedCSI-RS* in *SRS-ResourceSet* for SRS resource set. + +For non-codebook based transmission, the UE can be scheduled with DCI format 0\_1 or 0\_2 when at least one SRS resource is configured in *SRS-ResourceSet* with *usage* set to 'nonCodebook'. + +### 6.1.2 Resource allocation + +#### 6.1.2.1 Resource allocation in time domain + +When the UE is scheduled to transmit a transport block and no CSI report by a DCI or by a RAR UL grant or fallbackRAR UL grant, or the UE is scheduled to transmit a transport block and a CSI report(s) on PUSCH by a DCI, the '*Time domain resource assignment*' field value $m$ for the scheduled PUSCH on the serving cell of the DCI or the *PUSCH time resource allocation* field value $m$ of the RAR UL grant or of the fallbackRAR UL grant provides a row index $m + 1$ to a resource allocation table. The determination of the used resource allocation table is defined in Clause 6.1.2.1.1. The indexed row defines the slot offset $K_2$ , the start and length indicator *SLIV*, or directly the start symbol $S$ and the allocation length $L$ , the PUSCH mapping type, the number of slots used for TBS determination (if *numberOfSlotsTBoMS* is present in the resource allocation table), and the number of repetitions (if *numberOfRepetitions* is present in the resource allocation table) to be applied in the PUSCH transmission. + +When the UE is scheduled to transmit a PUSCH with no transport block and with a CSI report(s) by a '*CSI request*' field on a DCI, the '*Time domain resource assignment*' field value $m$ of the DCI provides a row index $m + 1$ to the allocated table as defined in Clause 6.1.2.1.1. The indexed row defines the start and length indicator *SLIV*, or directly the start symbol $S$ and the allocation length $L$ , and the PUSCH mapping type to be applied in the PUSCH transmission and the + +$K_2$ value is determined as $\max_j Y_j(m+1)$ , where $Y_j$ are the corresponding list entries of the higher layer parameter + +- *reportSlotOffsetListDCI-0-2* or *reportSlotOffsetListDCI-0-2-r17*, if PUSCH is scheduled by DCI format 0\_2 and *reportSlotOffsetListDCI-0-2* or *reportSlotOffsetListDCI-0-2-r17* is configured; +- *reportSlotOffsetListDCI-0-1* or *reportSlotOffsetListDCI-0-1-r17*, if PUSCH is scheduled by DCI format 0\_1 or 0\_3 and *reportSlotOffsetListDCI-0-1* or *reportSlotOffsetListDCI-0-1-r17* is configured; +- *reportSlotOffsetList* or *reportSlotOffsetList-r17*, otherwise; + +in *CSI-ReportConfig* for the triggered CSI Reporting Settings and $Y_j(m+1)$ is the $(m+1)$ th entry of including the omitted CSI Reporting Settings triggered for non-active DL BWPs, where the UE does not expect that $(m+1)$ is larger than 16. + +- The slot $K_s$ , where the UE shall transmit the PUSCH is determined by $K_2$ as $K_s =$ + +$$\left\lceil n \cdot \frac{2^{\mu_{PUSCH}}}{2^{\mu_{PDCCH}}} \right\rceil + K_2 + \left\lceil \left( \frac{N_{slot,offset,PDCCH}^{CA}}{2^{\mu_{offset,PDCCH}}} - \frac{N_{slot,offset,PUSCH}^{CA}}{2^{\mu_{offset,PUSCH}}}} \right) \cdot 2^{\mu_{PUSCH}} \right\rceil$$ + +, if UE is configured with *ca-SlotOffset* for at least one of the scheduled and scheduling cell, , otherwise, where $\mu$ is a parameter configured by higher layer as specified in clause 4.2 of [6 TS 38.213], and where $\mu$ is the subcarrier spacing configuration for with a value of 0 for frequency range 1, $n$ is the slot with the scheduling DCI, $K_2$ is based on the numerology of + +PUSCH, $\mu_{PUSCH}$ and $\mu_{PDCCH}$ are the subcarrier spacing configurations for PUSCH and PDCCH, respectively, and the scheduling DCI is other than DCI format 0\_0 with CRC scrambled by TC-RNTI. + +- $\mu_{PDCCH}$ and are the $\mu_{offset}$ , respectively, which are determined by higher-layer configured *ca-SlotOffset* for the cell receiving the PDCCH, and are the $\mu_{PUSCH}$ and the $\mu_{offset}$ , respectively, which are determined by higher-layer configured *ca-SlotOffset* for the cell transmitting the PUSCH, as defined in clause 4.5 of [4, TS 38.211], and +- for PUSCH scheduled by DCI format 0\_1, if *pusch-RepTypeIndicatorDCI-0-1* is set to 'pusch-RepTypeB', the UE applies PUSCH repetition Type B procedure when determining the time domain resource allocation. For PUSCH scheduled by DCI format 0\_2, if *pusch-RepTypeIndicatorDCI-0-2* is set to 'pusch-RepTypeB', the UE applies PUSCH repetition Type B procedure when determining the time domain resource allocation. Otherwise, the UE applies PUSCH repetition Type A procedure when determining the time domain resource allocation for PUSCH scheduled by PDCCH, by RAR UL grant, or by fallbackRAR UL grant. +- for PUSCH scheduled by DCI format 0\_1 or DCI format 0\_2, if *numberOfSlotsTBoMS* is present and larger than 1, the UE applies TB processing over multiple slots procedure when determining the time domain resource allocation. +- For PUSCH repetition Type A and TB processing over multiple slots, the starting symbol $S$ relative to the start of the slot, and the number of consecutive symbols $L$ counting from the symbol $S$ allocated for the PUSCH are determined from the start and length indicator *SLIV* of the indexed row: + +if then + +else + +where, and + +- For PUSCH repetition Type B, the starting symbol $S$ relative to the start of the slot, and the number of consecutive symbols $L$ counting from the symbol $S$ allocated for the PUSCH are provided by *startSymbol* and *length* of the indexed row of the resource allocation table, respectively. +- For PUSCH repetition Type A and TB processing over multiple slots, the PUSCH mapping type is set to Type A or Type B as defined in Clause 6.4.1.1.3 of [4, TS 38.211] as given by the indexed row. +- For PUSCH repetition Type B, the PUSCH mapping type is set to Type B. + +The UE shall consider the $S$ and $L$ combinations defined in table 6.1.2.1-1 as valid PUSCH allocations + +**Table 6.1.2.1-1: Valid S and L combinations** + +| PUSCH mapping type | Normal cyclic prefix | | | Extended cyclic prefix | | | +|------------------------------------|----------------------|------------|-----------------------------------------------------------------------|------------------------|------------|-----------------------------------------------------------------------| +| | S | L | S+L | S | L | S+L | +| Type A
(repetition Type A only) | 0 | {4,...,14} | {4,...,14} | 0 | {4,...,12} | {4,...,12} | +| Type B | {0,...,13} | {1,...,14} | {1,...,14} for repetition Type A,
{1,...,27} for repetition Type B | {0,...,11} | {1,...,12} | {1,...,12} for repetition Type A,
{1,...,23} for repetition Type B | + +For TB processing over multiple slots, when transmitting PUSCH scheduled by DCI format 0\_1 or 0\_2 in PDCCH with CRC scrambled with C-RNTI, MCS-C-RNTI, or CS-RNTI with NDI=1, + +- the number of slots used for TBS determination $N$ is indicated by *numberOfSlotsTBToMS*. +- the number of repetitions $K$ of the number of slots $N$ used for TBS determination is determined as + - if *numberOfRepetitions* is present in the resource allocation table, the number of repetitions $K$ is equal to *numberOfRepetitions*; + - otherwise, $K=1$ . +- when the UE supports repetition of TB processing over multiple slots, the UE does not expect that $N$ is larger than 32. + +When configured with $\mu=5$ or 6 the UE does not expect to be scheduled with more than one PUSCH in a slot, by a single DCI or multiple DCIs, where multiple DCIs are not associated with CORESETs having different *coresetPoolIndex*. + +For PUSCH repetition Type A, when transmitting PUSCH scheduled by DCI format 0\_1, 0\_2 or 0\_3 in PDCCH with CRC scrambled with C-RNTI, MCS-C-RNTI, or scheduled by DCI format 0\_1 or 0\_2 in PDCCH with CRC scrambled CS-RNTI with NDI=1, the number of repetitions $K$ is determined as + +- if *numberOfRepetitions* is present in the resource allocation table, the number of repetitions $K$ is equal to *numberOfRepetitions*; +- elseif the UE is configured with *pusch-AggregationFactor*, the number of repetitions $K$ is equal to *pusch-AggregationFactor*; +- otherwise $K=1$ . +- the number of slots used for TBS determination $N$ is equal to 1. + +For PUSCH repetition type A, when transmitting PUSCH scheduled by RAR UL grant, the 2 MSBs of the MCS information field of the RAR UL grant provide a codepoint to determine the number of repetitions $K$ according to Table 6.1.2.1-1A, based on whether or not the higher layer parameter *numberOfMsg3-RepetitionsList* is configured. The number of slots used for TBS determination $N$ is equal to 1. + +For PUSCH repetition type A, when transmitting PUSCH scheduled by DCI format 0\_0 with CRC scrambled by TC-RNTI, the 2 MSBs of the MCS information field of the DCI format 0\_0 with CRC scrambled by TC-RNTI provide a codepoint to determine the number of repetitions $K$ according to Table 6.1.2.1-1A, based on whether or not the higher layer parameter *numberOfMsg3-RepetitionsList* is configured. The number of slots used for TBS determination $N$ is equal to 1. + +**Table 6.1.2.1-1A: Number of repetition $K$ as a function of 2 MSBs of MCS information field** + +| numberOfMsg3-RepetitionsList is configured | | numberOfMsg3-RepetitionsList is not configured | | +|---------------------------------------------------|-----------------------------------------------------|-------------------------------------------------------|----------| +| Codepoint | K | Codepoint | K | +| 00 | First value of numberOfMsg3-RepetitionsList | 00 | 1 | +| 01 | Second value of numberOfMsg3-RepetitionsList | 01 | 2 | +| 10 | Third value of numberOfMsg3-RepetitionsList | 10 | 3 | +| 11 | Fourth value of numberOfMsg3-RepetitionsList | 11 | 4 | + +If a UE is configured with higher layer parameter *pusch-TimeDomainAllocationListForMultiPUSCH*, the UE does not expect to be configured with *pusch-AggregationFactor*. + +If a UE is configured with *extendedK2* in *pusch-TimeDomainAllocationListForMultiPUSCH* in which one or more rows contain multiple SLIVs for PUSCH on a UL BWP of a serving cell, the UE does not apply *pusch-AggregationFactor*, if configured, to DCI format 0\_1 on the UL BWP of the serving cell and the UE does not expect to be configured with *numberOfRepetitions* in *pusch-TimeDomainAllocationListForMultiPUSCH*. + +If a UE is configured with *extendedK2* in *pusch-TimeDomainAllocationListForMultiPUSCH* in which one or more rows contain multiple SLIVs for PUSCH on a UL BWP of a serving cell, when any two UL DCIs end in the same symbol and at least one of the DCIs scheduling multiple PUSCHs, the UE does not expect that the any scheduled multiple PUSCHs have overlapping spans, where the span associated with a DCI is defined from the beginning of the first scheduled PUSCH till the end of the last scheduled PUSCH. + +For unpaired spectrum: + +- When *AvailableSlotCounting* is enabled, and in case $K > 1$ , the UE determines slots for a PUSCH transmission of a PUSCH repetition type A scheduled by DCI format 0\_1 or 0\_2, based on *tdd-UL-DL-ConfigurationCommon*, *tdd-UL-DL-ConfigurationDedicated* and *ssb-PositionsInBurst*, and the TDRA information field value in the DCI format 0\_1 or 0\_2. +- A slot is not counted in the number of slots for PUSCH transmission of a PUSCH repetition Type A scheduled by DCI format 0\_1 or 0\_2 if at least one of the symbols indicated by the indexed row of the used resource allocation table in the slot overlaps with a DL symbol indicated by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* if provided, or a symbol of an SS/PBCH block with index provided by *ssb-PositionsInBurst*. +- Otherwise, the UE determines consecutive slots for a PUSCH transmission of a PUSCH repetition type A scheduled by DCI format 0\_1 or 0\_2, based on the TDRA information field value in the DCI format 0\_1 or 0\_2. +- The UE determines slots for a PUSCH transmission of TB processing over multiple slots scheduled by DCI format 0\_1 or 0\_2, based on *tdd-UL-DL-ConfigurationCommon*, *tdd-UL-DL-ConfigurationDedicated* and *ssb-PositionsInBurst*, and the TDRA information field value in the DCI format 0\_1 or 0\_2. +- A slot is not counted in the number of slots for a PUSCH transmission of TB processing over multiple slots if at least one of the symbols indicated by the indexed row of the used resource allocation table in the slot overlaps with a DL symbol indicated by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* if provided, or a symbol of an SS/PBCH block with index provided by *ssb-PositionsInBurst*. +- The UE determines slots for a PUSCH transmission of a PUSCH repetition Type A scheduled by RAR UL grant, based on *tdd-UL-DL-ConfigurationCommon* and *ssb-PositionsInBurst*, and the TDRA information field value in the RAR UL grant. +- A slot is not counted in the number of slots for a PUSCH transmission of a PUSCH repetition Type A scheduled by RAR UL grant, if at least one of the symbols indicated by the indexed row of the used resource allocation table in the slot overlaps with a DL symbol indicated by *tdd-UL-DL-ConfigurationCommon* if provided, or a symbol of an SS/PBCH block with index provided by *ssb-PositionsInBurst*. + +- The UE determines slots for a PUSCH transmission of a PUSCH repetition Type A scheduled by DCI format 0\_0 with CRC scrambled by TC-RNTI, based on *tdd-UL-DL-ConfigurationCommon* and *ssb-PositionsInBurst* and the TDRA information field value in the DCI scheduling the PUSCH. +- A slot is not counted in the number of slots for a PUSCH transmission of a PUSCH repetition Type A scheduled by DCI format 0\_0 scrambled by TC-RNTI, if at least one of the symbols indicated by the indexed row of the used resource allocation table in the slot overlaps with a DL symbol indicated by *tdd-UL-DL-ConfigurationCommon* if provided, or a symbol of an SS/PBCH block with index provided by *ssb-PositionsInBurst*. + +For paired spectrum and SUL band: + +- The UE determines consecutive slots for a PUSCH transmission of a PUSCH repetition type A scheduled by DCI format 0\_1 or 0\_2, or 0\_3 for paired spectrum only, or for a PUSCH transmission of TB processing over multiple slots scheduled by DCI format 0\_1 or 0\_2, based on the TDRA information field value in the DCI format 0\_1, 0\_2 or 0\_3. +- For the case of a reduced capability half-duplex UE, the UE determines slots for a PUSCH transmission of a PUSCH repetition type A scheduled by DCI format 0\_1 or 0\_2 when *AvailableSlotCounting* is enabled and $K > 1$ , or for a PUSCH transmission of TB processing over multiple slots scheduled by DCI format 0\_1 or 0\_2, based on the TDRA information field value in the DCI format 0\_1 or 0\_2. A slot is not counted in the number of slots if at least one of the symbols indicated by the indexed row of the used resource allocation table in the slot does not start or end at least or , respectively, from the last or first symbol of an SS/PBCH block with index provided by *ssb-PositionsInBurst*. +- The UE determines consecutive slots for a PUSCH transmission of a PUSCH repetition Type A scheduled by RAR UL grant, based on the TDRA information field value in the RAR UL grant. +- The UE determines consecutive slots for a PUSCH transmission of a PUSCH repetition Type A scheduled by DCI format 0\_0 with CRC scrambled by TC-RNTI, based on the TDRA information field value in the DCI scheduling the PUSCH. + +If a UE would transmit a PUSCH of PUSCH repetition Type A when *AvailableSlotCounting* is enabled and $K > 1$ or a TB processing over multiple slots over slots, and the UE does not transmit the PUSCH of a TB processing over multiple slots or the PUSCH repetition Type A in a slot from the slots, according to Clause 9, Clause 11.1, Clause 11.2A, Clause 15 and Clause 17.2 of [6, TS 38.213], the UE counts the slots in the number of slots. + +For PUSCH repetition Type A, in case $K > 1$ , + +- If the PUSCH is scheduled by DCI format 0\_1 or 0\_2 + - if *AvailableSlotCounting* is enabled, the same symbol allocation is applied across the slots determined for the PUSCH transmission and the PUSCH is limited to a single transmission layer. The UE shall repeat the TB across the slots determined for the PUSCH transmission, applying the same symbol allocation in each slot. + - Otherwise, the same symbol allocation is applied across the consecutive slots and the PUSCH is limited to a single transmission layer. The UE shall repeat the TB across the consecutive slots applying the same symbol allocation in each slot. +- Else if the PUSCH is scheduled by RAR UL grant or by DCI format 0\_0 with CRC scrambled by TC-RNTI, the same symbol allocation is applied across the slots determined for the PUSCH transmission and the PUSCH is limited to a single transmission layer. The UE shall repeat the TB across the slots determined for the PUSCH transmission, applying the same symbol allocation in each slot. + +For PUSCH repetition Type B: + +- If *pusch-DMRS-Bundling* is enabled, the PUSCH is limited to a single transmission layer. + +For TB processing over multiple slots: + +- For unpaired spectrum, the same symbol allocation is applied across the slots determined for the PUSCH transmission and the PUSCH is limited to a single transmission layer. The UE shall transmit the TB across the slots determined for the PUSCH transmission, applying the same symbol allocation in each slot. + +- For paired spectrum or supplementary uplink band, the same symbol allocation is applied across the consecutive slots and the PUSCH is limited to a single transmission layer. The UE shall transmit the TB across the consecutive slots applying the same symbol allocation in each slot. +- For the case of reduced capability half-duplex UE, the same symbol allocation is applied across the slots determined for the PUSCH transmission and the PUSCH is limited to a single transmission layer. The UE shall transmit the TB across the slots determined for the PUSCH transmission, applying the same symbol allocation in each slot. + +For a PUSCH transmission scheduled by DCI format 0\_1, 0\_2 or 0\_3, or 0\_0 with CRC scrambled by TC-RNTI, the redundancy version to be applied on the *n*th transmission occasion of the TB, where *n* = 0, 1, ... -1, is determined according to table 6.1.2.1-2. + +For a PUSCH transmission of a PUSCH repetition Type A scheduled by RAR UL grant, the redundancy version to be applied on the *n*th transmission occasion of the TB, where *n* = 0, 1, ... -1, is determined according to the first row of Table 6.1.2.1-2. + +**Table 6.1.2.1-2: Redundancy version for PUSCH transmission** + +| rvid indicated by the DCI scheduling the PUSCH | rvid to be applied to n th transmission occasion (repetition Type A) or TB processing over multiple slots) or n th actual repetition (repetition Type B) | | | | +|------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|-----------------------------------|-----------------------------------| +| | $((n-(n \bmod N))/N) \bmod 4 = 0$ | $((n-(n \bmod N))/N) \bmod 4 = 1$ | $((n-(n \bmod N))/N) \bmod 4 = 2$ | $((n-(n \bmod N))/N) \bmod 4 = 3$ | +| 0 | 0 | 2 | 3 | 1 | +| 2 | 2 | 3 | 1 | 0 | +| 3 | 3 | 1 | 0 | 2 | +| 1 | 1 | 0 | 2 | 3 | + +When transmitting MsgA PUSCH on a non-initial UL BWP, if the UE is configured with *startSymbolAndLengthMsgA-PO*, the UE shall determine the *S* and *L* from *startSymbolAndLengthMsgA-PO*. + +When transmitting MsgA PUSCH, if the UE is not configured with *startSymbolAndLengthMsgA-PO*, and if the TDRA list *PUSCH-TimeDomainResourceAllocationList* is provided in *PUSCH-ConfigCommon*, the UE shall use *msgA-PUSCH-TimeDomainAllocation* to indicate which values are used in the list. If *PUSCH-TimeDomainResourceAllocationList* is not provided in *PUSCH-ConfigCommon*, the UE shall use parameters *S* and *L* from table 6.1.2.1.1-2 or table 6.1.2.1.1-3 where *msgA-PUSCH-TimeDomainAllocation* indicates which values are used in the list. The time offset for PUSCH transmission is described in [6, TS 38.213]. + +For PUSCH repetition Type A and TB processing over multiple slots, a PUSCH transmission in a slot of a multi-slot PUSCH transmission is omitted according to the conditions in Clause 9, Clause 11.1, Clause 11.2A, Clause 15 and Clause 17.2 of [6, TS 38.213]. + +For PUSCH repetition Type B, except for PUSCH transmitting CSI report(s) with no transport block, the number of nominal repetitions is given by *numberOfRepetitions*. For the *n*-th nominal repetition, *n* = 0, ..., *numberOfRepetitions* - 1, + +- The slot where the nominal repetition starts is given by $K_s + \left\lfloor \frac{S + n \cdot L}{N_{\text{symb}}^{\text{slot}}} \right\rfloor$ , and the starting symbol relative to the start of the slot is given by $\bmod(S + n \cdot L, N_{\text{symb}}^{\text{slot}})$ . +- The slot where the nominal repetition ends is given by $K_s + \left\lfloor \frac{S + (n+1) \cdot L - 1}{N_{\text{symb}}^{\text{slot}}} \right\rfloor$ , and the ending symbol relative to the start of the slot is given by $\bmod(S + (n+1) \cdot L - 1, N_{\text{symb}}^{\text{slot}})$ . + +Here *Ks* is the slot where the PUSCH transmission starts, and *Nsymbslot* is the number of symbols per slot as defined in Clause 4.3.2 of [4, TS38.211]. + +For PUSCH repetition Type B, the UE determines invalid symbol(s) for PUSCH repetition Type B transmission as follows: + +- A symbol that is indicated as downlink by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* is considered as an invalid symbol for PUSCH repetition Type B transmission. +- For operation in unpaired spectrum, symbols indicated by *ssb-PositionsInBurst* in SIB1 or *ssb-PositionsInBurst* in *ServingCellConfigCommon* for reception of SS/PBCH blocks are considered as invalid symbols for PUSCH repetition Type B transmission. +- For a reduced capability half-duplex UE in paired spectrum, symbols that do not start or end at least $r$ or $r$ , respectively, from the last or first symbol of an SS/PBCH block with index indicated by *ssb-PositionsInBurst* in SIB1 or by *ssb-PositionsInBurst* in *ServingCellConfigCommon* or by *NonCellDefiningSSB*, or by *ssb-PositionsInBurst* in *SSB-MTC-AdditionalPCI* associated to physical cell ID with active TCI states for PDCCH or PDSCH, or for a set of symbols of a slot corresponding to SS/PBCH blocks configured for L1 beam measurement/reporting for reception of SS/PBCH blocks are considered as invalid symbols for PUSCH repetition Type B transmission. +- For operation in unpaired spectrum, symbol(s) indicated by *pdcch-ConfigSIB1* in *MIB* for a CORESET for Type0-PDCCH CSS set are considered as invalid symbol(s) for PUSCH repetition Type B transmission. +- For operation in unpaired spectrum, if *numberOfInvalidSymbolsForDL-UL-Switching* is configured, *numberOfInvalidSymbolsForDL-UL-Switching* symbol(s) after the last symbol that is indicated as downlink in each consecutive set of all symbols that are indicated as downlink by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* are considered as invalid symbol(s) for PUSCH repetition Type B transmission. The symbol(s) given by *numberOfInvalidSymbolsForDL-UL-Switching* are defined using the reference SCS configuration *referenceSubcarrierSpacing* provided in *tdd-UL-DL-ConfigurationCommon*. +- For operation with shared spectrum channel access with semi-static channel occupancy, symbols in an idle duration associated with a periodic channel occupancy as described in Clause 4.3.1.1 of [16, 37.213], or in an idle duration in a period associated with an initiated channel occupancy as described in Clause 4.3.2. of [16, TS 37.213] are considered as invalid symbol(s) for PUSCH repetition Type B transmission. +- The UE may be configured with the higher layer parameter *invalidSymbolPattern*, which provides a symbol level bitmap spanning one or two slots (higher layer parameter *symbols* given by *invalidSymbolPattern*). A bit value equal to 1 in the symbol level bitmap *symbols* indicates that the corresponding symbol is an invalid symbol for PUSCH repetition Type B transmission. The UE may be additionally configured with a time-domain pattern (higher layer parameter *periodicityAndPattern* given by *invalidSymbolPattern*), where each bit of *periodicityAndPattern* corresponds to a unit equal to a duration of the symbol level bitmap *symbols*, and a bit value equal to 1 indicates that the symbol level bitmap *symbols* is present in the unit. The *periodicityAndPattern* can be {1, 2, 4, 5, 8, 10, 20 or 40} units long, but maximum of 40 msec. The first symbol of *periodicityAndPattern* every 40 msec/P periods is a first symbol in frame $n_f \bmod 4 = 0$ , where P is the duration of *periodicityAndPattern-r16* in units of msec. When *periodicityAndPattern* is not configured, for a symbol level bitmap spanning two slots, the bits of the first and second slots correspond respectively to even and odd slots of a radio frame, and for a symbol level bitmap spanning one slot, the bits of the slot correspond to every slot of a radio frame. If *invalidSymbolPattern* is configured, when the UE applies the invalid symbol pattern is determined as follows: + - if the PUSCH is scheduled by DCI format 0\_1, or corresponds to a Type 2 configured grant activated by DCI format 0\_1, and if *invalidSymbolPatternIndicatorDCI-0-1* is configured, + - if invalid symbol pattern indicator field is set 1, the UE applies the invalid symbol pattern; + - otherwise, the UE does not apply the invalid symbol pattern; + - if the PUSCH is scheduled by DCI format 0\_2, or corresponds to a Type 2 configured grant activated by DCI format 0\_2, and if *invalidSymbolPatternIndicatorDCI-0-2* is configured, + - if invalid symbol pattern indicator field is set 1, the UE applies the invalid symbol pattern; + - otherwise, the UE does not apply the invalid symbol pattern; + - otherwise, the UE applies the invalid symbol pattern. +- If the UE + +- is configured with multiple serving cells within a cell group and is provided with *directionalCollisionHandling-r16* = 'enabled' for a set of serving cell(s) among the multiple serving cells, and +- indicates support of *half-DuplexTDD-CA-SameSCS-r16* capability, and +- is not configured to monitor PDCCH for detection of DCI format 2-0 on any of the multiple serving cells, + - a symbol indicated to the UE for reception of SS/PBCH blocks in a first cell of the multiple serving cells by *ssb-PositionsInBurst* in *SIB1*, or by *ssb-PositionsInBurst* in *ServingCellConfigCommon*, or by *NonCellDefiningSSB*, or by *ssb-PositionsInBurst* in *SSB-MTC-AdditionalPCI* associated to physical cell ID with active TCI states for PDCCH or PDSCH, or for a set of symbols of a slot corresponding to SS/PBCH blocks configured for L1 beam measurement/reporting is considered as an invalid symbol for PUSCH repetition Type B transmission in + - any of the multiple serving cells if the UE is not capable of simultaneous transmission and reception as indicated by *simultaneousRxBTxInterBandCA* among the multiple serving cells, and + - any one of the cells corresponding to the same band as the first cell, irrespective of any capability indicated by *simultaneousRxBTxInterBandCA* + +and + +- a symbol is considered as an invalid symbol in another cell among the set of serving cell(s) provided with *directionalCollisionHandling-r16* for PUSCH repetition Type B transmission with Type 1 or Type 2 configured grant except for the first Type 2 PUSCH transmission (including all repetitions) after activation if the symbol is indicated as downlink by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* on the reference cell as defined in Clause 11.1 of [6, TS 38.213], or the UE is configured by higher layers to receive PDCCH, PDSCH, or CSI-RS on the reference cell in the symbol. + +For PUSCH repetition Type B, after determining the invalid symbol(s) for PUSCH repetition type B transmission for each of the *K* nominal repetitions, the remaining symbols are considered as potentially valid symbols for PUSCH repetition Type B transmission. If the number of potentially valid symbols for PUSCH repetition type B transmission is greater than zero for a nominal repetition, the nominal repetition consists of one or more actual repetitions, where each actual repetition consists of a consecutive set of all potentially valid symbols that can be used for PUSCH repetition Type B transmission within a slot. An actual repetition with a single symbol is omitted except for the case of *L*=1. An actual repetition is omitted according to the conditions in Clause 9, Clause 11.1, Clause 11.2A, Clause 15 and Clause 17.2 of [6, TS 38.213]. The UE shall repeat the TB across actual repetitions. The redundancy version to be applied on the *n*th actual repetition (with the counting including the actual repetitions that are omitted) is determined according to table 6.1.2.1-2, where *N*=1. + +For PUSCH repetition Type B, when a UE receives a DCI that schedules aperiodic CSI report(s) or activates semi-persistent CSI report(s) on PUSCH with no transport block by a 'CSI request' field on a DCI, the number of nominal repetitions is always assumed to be 1, regardless of the value of *numberOfRepetitions*. When the UE is scheduled to transmit a PUSCH repetition Type B with no transport block and with aperiodic or semi-persistent CSI report(s) by a 'CSI request' field on a DCI, the first nominal repetition is expected to be the same as the first actual repetition. For PUSCH repetition Type B carrying semi-persistent CSI report(s) without a corresponding PDCCH after being activated on PUSCH by a 'CSI request' field on a DCI, if the first nominal repetition is not the same as the first actual repetition, the first nominal repetition is omitted; otherwise, the first nominal repetition is omitted according to the conditions in Clause 9, Clause 11.1, Clause 11.2A, Clause 15 and Clause 17.2 of [6, TS 38.213]. + +For PUSCH repetition Type B, when a UE is scheduled to transmit a transport block and aperiodic CSI report(s) on PUSCH by a 'CSI request' field on a DCI, the CSI report(s) is multiplexed only on the first actual repetition. The UE does not expect that the first actual repetition has a single symbol duration. + +For *pusch-TimeDomainAllocationListForMultiPUSCH* in *pusch-Config*, if a row indicates resource allocation for two to eight contiguous PUSCHs and *extendedK2* is not configured, *K2* given by *k2-r16* indicates the slot where UE shall transmit the first PUSCH of the multiple PUSCHs. Each PUSCH has a separate SLIV and mapping type. The number of scheduled PUSCHs is signalled by the number of indicated valid SLIVs in the row of the *pusch-TimeDomainAllocationListForMultiPUSCH* signalled in DCI format 0\_1. + +For *pusch-TimeDomainAllocationListForMultiPUSCH* in *pusch-Config*, if a row indicates resource allocation of more than one PUSCH and *extendedK2* is configured, each PUSCH has a separate SLIV, mapping type and *K2* given by *extendedK2*. If a row indicates resource allocation of a single PUSCH, the PUSCH has a single SLIV, mapping type, + +and $K_2$ , where $K_2$ is given by *extendedK2*, if configured, otherwise $K_2$ is given by $k2-r16$ . The number of scheduled PUSCHs is signalled by the number of indicated SLIVs in the row of the *pusch-TimeDomainAllocationListForMultiPUSCH* signalled in DCI format 0\_1. + +If a UE is configured with *extendedK2* in *pusch-TimeDomainAllocationListForMultiPUSCH* in which one or more rows contain multiple SLIVs for PUSCH on a UL BWP of a serving cell, and the UE is indicated re-transmission of PUSCH by DCI format 0\_1, where the PUSCH is correspond to a configured grant Type 1 or Type 2, the UE does not expect that the number of indicated SLIVs in the row of the *pusch-TimeDomainAllocationListForMultiPUSCH* by the DCI is more than one. + +If a UE is configured with *pusch-TimeDomainAllocationListForMultiPUSCH* in which one or more rows contain multiple SLIVs for PUSCH on a UL BWP of a serving cell, the UE does not expect to be scheduled with one or multiple PUSCH transmissions by a single DCI format 0\_1, where each PUSCH transmission overlaps with a DL symbol indicated by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* if provided, or a symbol of an SS/PBCH block with index provided by *ssb-PositionsInBurst*. + +When the UE is configured with *minimumSchedulingOffsetK2* in an active UL BWP it applies a minimum scheduling offset restriction indicated by the 'Minimum applicable scheduling offset indicator' field in DCI format 0\_1, 0\_3, 1\_1 or 1\_3 if the same field is available. When the UE is configured with *minimumSchedulingOffsetK2* in an active UL BWP and it has not received 'Minimum applicable scheduling offset indicator' field in DCI format 0\_1, 0\_3, 1\_1 or 1\_3, the UE shall apply a minimum scheduling offset restriction indicated based on 'Minimum applicable scheduling offset indicator' value '0'. When the minimum scheduling offset restriction is applied the UE is not expected to be scheduled with a DCI in slot $n$ to transmit a PUSCH scheduled with C-RNTI, CS-RNTI, MCS-C-RNTI or SP-CSI-RNTI with $K_2$ smaller than $K_{2min}$ , where $K_{2min}$ and $\mu$ are the applied minimum scheduling offset restriction and the numerology of the active UL BWP of the scheduled cell when receiving the DCI in slot $n$ , respectively, and $\mu$ is the numerology of the new active UL BWP in case of active UL BWP change in the scheduled cell and is equal to $\mu$ , otherwise. The minimum scheduling offset restriction is not applied when PUSCH transmission is scheduled by RAR UL grant or fallbackRAR UL grant for RACH procedure, or when PUSCH is scheduled with TC-RNTI. The application delay of the change of the minimum scheduling offset restriction is determined in Clause 5.3.1. + +When two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook' or 'noncodebook', for PUSCH repetition Type A, in case $K > 1$ , the same symbol allocation is applied across the $K$ consecutive slots and the PUSCH is limited to a single transmission layer. The UE shall repeat the TB across the $K$ consecutive slots applying the same symbol allocation in each slot, and the association of the first and second SRS resource set in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* to each slot is determined as follows: + +- if a DCI format 0\_3 schedules the PUSCH, the first SRS resource set is associated with all $K$ consecutive slots, +- if a DCI format 0\_1 or DCI format 0\_2 indicates codepoint "00" for the *SRS resource set indicator*, the first SRS resource set is associated with all $K$ consecutive slots, +- if a DCI format 0\_1 or DCI format 0\_2 indicates codepoint "01" for the *SRS resource set indicator*, the second SRS resource set is associated with all $K$ consecutive slots, +- if a DCI format 0\_1 or DCI format 0\_2 indicates codepoint "10" for the *SRS resource set indicator*, the first and second SRS resource set association to $K$ consecutive slots is determined as follows: + - When $K = 2$ , the first and second SRS resource sets are applied to the first and second slot of 2 consecutive slots, respectively. + - When $K > 2$ and *cyclicMapping* in *PUSCH-Config* is enabled, the first and second SRS resource sets are applied to the first and second slot of $K$ consecutive slots, respectively, and the same SRS resource set mapping pattern continues to the remaining slots of $K$ consecutive slots. + - When $K > 2$ and *sequentialMapping* in *PUSCH-Config* is enabled, first SRS resource set is applied to the first and second slots of $K$ consecutive slots, and the second SRS resource set is applied to the third and fourth slot of $K$ consecutive slots, and the same SRS resource set mapping pattern continues to the remaining slots of $K$ consecutive slots. +- Otherwise, a DCI format 0\_1 or DCI format 0\_2 indicates codepoint "11" for the *SRS resource set indicator*, and the first and second SRS resource set association to $K$ consecutive slots is determined as follows, + +- When $K = 2$ , the second and first SRS resource set are applied to the first and second slot of 2 consecutive slots, respectively. +- When $K > 2$ and *cyclicMapping* in *PUSCH-Config* is enabled, the second and first SRS resource sets are applied to the first and second slot of $K$ consecutive slots, respectively, and the same SRS resource set mapping pattern continues to the remaining slots of the $K$ consecutive slots. +- When $K > 2$ and *sequentialMapping* in *PUSCH-Config* is enabled, the second SRS resource set is applied to the first and second slot of $K$ consecutive slots, and the first SRS resource set is applied to the third and fourth slot of $K$ consecutive slots, and the same SRS resource set mapping pattern continues to the remaining slots of the $K$ consecutive slots. + +For PUSCH repetition Type B, when two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook' or 'noncodebook', the SRS resource set association to nominal PUSCH repetitions follows the same method as SRS resource set association to slots in PUSCH Type A repetition by considering nominal repetitions instead of slots. + +When a UE is configured with *dl-OrJointTCI-StateList* or *TCI-UL-State* and is having two indicated TCI-States or TCI-UL-States, and two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook' or 'noncodebook', for PUSCH repetition Type A or Type B as described above, or for PUSCH transmission when the higher layer parameter *multipanelScheme* is set to 'SDMscheme' or 'SFNscheme', the association of the first and second indicated joint/UL TCI states to PUSCH transmission occasions or to corresponding PUSCH antenna ports is determined as follows: + +- if a DCI format 0\_1 or DCI format 0\_2 indicates codepoint "00" or "01" for the *SRS resource set indicator*, the first or second indicated joint/UL TCI state is applied to all PUSCH transmission occasions, respectively. +- if a DCI format 0\_1 or DCI format 0\_2 indicates codepoint "10" or "11" for the *SRS resource set indicator*, and the *multipanelScheme* is not configured, + - the first indicated joint/UL TCI state is applied to the PUSCH transmission occasion(s) associated with the first SRS resource set and the second indicated joint/UL TCI state is applied to the PUSCH transmission occasion(s) associated with the second SRS resource set, where the association of PUSCH transmission occasions to SRS resource sets is determined for $K = 2$ and $K > 2$ , and depending on whether *cyclicMapping* or *sequentialMapping* in *PUSCH-Config* is enabled, based on the above description in this Clause. +- if a DCI format 0\_1 or DCI format 0\_2 indicates codepoint "10" for the *SRS resource set indicator* and the higher layer parameters *multipanelScheme* is configured and set to 'SDMscheme' or 'SFNscheme', + - the first indicated TCI state is applied to the PUSCH antenna port(s), of corresponding PUSCH transmission occasion, associated with the first SRS resource set, and the second indicated TCI state is applied to the PUSCH antenna port(s), of corresponding PUSCH transmission occasion, associated with the second SRS resource set, where the association of PUSCH antenna ports to SRS resource sets is determined according to Clauses 6.1.1.1 and 6.1.1.2. + +For both PUSCH repetition Type A and PUSCH repetition Type B, when a DCI format 0\_1 or DCI format 0\_2 indicates codepoint "10" or "11" for the *SRS resource set indicator*, the redundancy version to be applied on the $n$ th transmission occasion (for PUSCH repetition Type A) of the TB, where $n = 0, 1, \dots, K-1$ , or $n$ th actual repetition (for PUSCH repetition Type B, with the counting including the actual repetitions that are omitted) is determined according to Table 6.1.2.1-2 and Table 6.1.2.1-3. For all PUSCH repetitions associated with the SRS resource set of the first transmission occasion or actual repetition, the redundancy version to be applied is derived according to Table 6.1.2.1-2, where $n$ is counted only considering PUSCH transmission occasions or actual repetitions associated with the same SRS resource set as the first transmission occasion or actual repetition. The redundancy version for PUSCH transmission occasions or actual repetitions that are associated with an SRS resource set other than the SRS resource set of the first transmission occasion or actual repetition is derived according to Table 6.1.2.1-3, where additional shifting operation for each redundancy version is configured by higher layer parameter *sequenceOffsetforRV* in *PUSCH-Config* and is counted only considering PUSCH transmission occasions or actual repetitions that are not associated with the SRS resource set of the first transmission occasion or actual repetition. + +**Table 6.1.2.1-3: Applied redundancy version for the other SRS resource set (SRS resource set not associated with the first transmission occasion or actual repetition) when *sequenceOffsetforRV* is present** + +| rvid indicated by the DCI scheduling the PUSCH | rvid to be applied to n th transmission occasion (repetition Type A) or n th actual repetition (repetition Type B) | | | | +|------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|--------------------|--------------------| +| | n mod 4 = 0 | n mod 4 = 1 | n mod 4 = 2 | n mod 4 = 3 | +| | | | | | +| | | | | | +| | | | | | +| | | | | | + +For PUSCH repetition Type A, when higher layer parameter *multipanelScheme* is not provided and a DCI format 0\_1 and DCI format 0\_2 indicate codepoint "10" or "11" for the *SRS resource set indicator* and schedule aperiodic CSI report(s) on PUSCH with transport block by a 'CSI request' field on a DCI, the CSI report(s) multiplexing is determined as follows + +- if higher layer parameter *ap-CSI-MultiplexingMode* in *CSI-AperiodicTriggerState* is enabled and UCI other than CSI report(s) are not multiplexed on PUSCH, the CSI report(s) is transmitted separately only on the first transmission occasion associated with the first SRS resource set and the first transmission occasion associated with the second SRS resource set. +- otherwise, the CSI report(s) is transmitted only on the first transmission occasion. + +For PUSCH transmissions of TB processing over multiple slots, when a DCI format 0\_1 and DCI format 0\_2 schedule aperiodic CSI report(s) on PUSCH with transport block by a 'CSI request' field on a DCI, the CSI report(s) is transmitted only on the first slot of the $N \cdot K$ slots determined for the PUSCH transmission. + +For PUSCH repetition Type B, when higher layer parameter *multipanelScheme* is not provided and a DCI format 0\_1 and DCI format 0\_2 indicate codepoint "10" or "11" for the *SRS resource set indicator* and schedule aperiodic CSI report(s) on PUSCH with transport block by a 'CSI request' field on a DCI, CSI report(s) multiplexing is determined as follows + +- if higher layer parameter *ap-CSI-MultiplexingMode* in *CSI-AperiodicTriggerState* is enabled and the first actual repetition associated with the first SRS resource set and the first actual repetition associated with the second SRS resource set have the same number of symbols and UCI other than CSI report(s) are not multiplexed on PUSCH, the CSI report(s) is multiplexed separately only on the first actual repetition associated with the first SRS resource set and first actual repetition associated with the second SRS resource set. +- otherwise, the CSI report(s) is multiplexed only on the first actual repetition. + +The UE does not expect a different number of actual PT-RS ports for the two actual repetitions when the CSI report(s) is transmitted separately on two actual repetitions. + +For PUSCH repetition Type A, when higher layer parameter *multipanelScheme* is not provided and a DCI format 0\_1 and DCI format 0\_2 indicate codepoint "10" or "11" for the *SRS resource set indicator* and schedule aperiodic CSI report(s) on PUSCH with no transport block by a 'CSI request' field on a DCI, the number of repetitions is assumed to be 2 regardless of the value of *numberOfRepetitions* or *pusch-AggregationFactor* (if *numberOfRepetitions* is not present in the time domain resource allocation table), and transmission of CSI report(s) is determined as follows + +- if higher layer parameter *ap-CSI-MultiplexingMode* in *CSI-AperiodicTriggerState* is enabled and UCI other than CSI report(s) are not multiplexed on PUSCH, the CSI report(s) is transmitted separately on the first transmission occasion and the second transmission occasion +- otherwise, the CSI report(s) is transmitted only on the first transmission occasion. + +For PUSCH repetition Type B, when higher layer parameter *multipanelScheme* is not provided and a DCI format 0\_1 and DCI format 0\_2 indicate codepoint "10" or "11" for the *SRS resource set indicator* and schedule aperiodic CSI report(s) or activates semi-persistent CSI report(s) on PUSCH with no transport block by a 'CSI request' field on a DCI, the number of nominal repetitions is always assumed to be 2 regardless of the value of *numberOfRepetitions*, and the first and second nominal repetitions are expected to be the same as the first and second actual repetitions, and transmission of CSI report(s) is determined as follows: + +- if higher layer parameter *ap-CSI-MultiplexingMode* in *CSI-AperiodicTriggerState* is enabled for aperiodic CSI report(s) or higher layer parameter *SP-CSI-MultiplexingMode* in *CSI-SemiPersistentOnPUSCH-TriggerState* is enabled for semi-persistent CSI report(s) and UCI other than CSI report(s) are not multiplexed on PUSCH, the CSI report(s) is transmitted separately on the first actual repetition and the second actual repetition +- otherwise, the CSI report(s) is transmitted only on the first actual repetition. + +The UE does not expect a different number of actual PT-RS ports for the two actual repetitions when the CSI report(s) is transmitted separately on two actual repetitions. + +For PUSCH repetition Type A, when higher layer parameter *multipanelScheme* is not provided and a DCI format 0\_1 and DCI format 0\_2 indicate codepoint "10" or "11" for the *SRS resource set indicator* and activate semi-persistent CSI report(s) on PUSCH with no transport block by a 'CSI request' field on a DCI, or indicate the PUSCH repetition Type A carrying semi-persistent CSI report(s) without a corresponding PDCCH after being activated on PUSCH by a 'CSI request' field on a DCI, the number of repetitions is always assumed to be 2 regardless of the value of *numberOfRepetitions* or *pusch-AggregationFactor* (if *numberOfRepetitions* is not present in the time domain resource allocation table), and transmission of CSI report(s) is determined as follows + +- if higher layer parameter *SP-CSI-MultiplexingMode* in *CSI-SemiPersistentOnPUSCH-TriggerState* is enabled and UCI other than CSI report(s) are not multiplexed on PUSCH, the CSI report(s) is transmitted separately on the first transmission occasion and the second transmission occasion +- otherwise, the CSI report(s) is transmitted only on the first transmission occasion. + +For PUSCH repetition Type B, when higher layer parameter *multipanelScheme* is not provided and a DCI format 0\_1 and DCI format 0\_2 indicate codepoint "10" or "11" for the *SRS resource set indicator* and the PUSCH repetition Type B carrying semi-persistent CSI report(s) without a corresponding PDCCH after being activated on PUSCH by a 'CSI request' field on a DCI, the number of nominal repetitions is always assumed to be 2 regardless of the value of *numberOfRepetitions*, and transmission of CSI report(s) is determined as follows + +- if higher layer parameter *SP-CSI-MultiplexingMode* in *CSI-SemiPersistentOnPUSCH-TriggerState* is enabled and one of the first or second nominal repetition is the same as corresponding first or second actual repetition, the nominal repetition that is not having same actual repetition is omitted and the CSI report(s) is transmitted on the actual repetition that is not omitted. +- if higher layer parameter *SP-CSI-MultiplexingMode* in *CSI-SemiPersistentOnPUSCH-TriggerState* is enabled and the first and second nominal repetitions are the same as the first and second actual repetitions and the UCI other than CSI report(s) are not multiplexed on PUSCH, the CSI report(s) is transmitted separately on the first actual repetition and the second actual repetition +- otherwise, the CSI report(s) is transmitted only on the first actual repetition. + +##### 6.1.2.1.1 Determination of the resource allocation table to be used for PUSCH + +Table 6.1.2.1.1-1, Table 6.1.2.1.1-1A, Table 6.1.2.1.1-1B and Table 6.1.2.1.1-1C define which PUSCH time domain resource allocation configuration to apply. + +Table 6.1.2.1.1-4 defines the subcarrier spacing specific values $j$ . $j$ is used in determination of $K_2$ in conjunction to table 6.1.2.1.1-2, for normal CP or table 6.1.2.1.1-3 for extended CP, where $j$ is the subcarrier spacing configurations for PUSCH. + +Table 6.1.2.1.1-5 defines the additional subcarrier spacing specific slot delay value for the first transmission of PUSCH scheduled by the RAR or by the fallbackRAR. When the UE transmits a PUSCH scheduled by RAR or by the fallbackRAR, the $\Delta$ value specific to the PUSCH subcarrier spacing $\mu_{PUSCH}$ is applied in addition to the $K_2$ value. + +**Table 6.1.2.1.1-1: Applicable PUSCH time domain resource allocation for common search space and DCI format 0\_0 in UE specific search space** + +| RNTI | PDCCH search space | pusch-ConfigCommon includes pusch-TimeDomainAllocationList | pusch-Config includes pusch-TimeDomainAllocationList | PUSCH time domain resource allocation to apply | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|--------------------------------------------------------------------|-----------------------------------------------------------------------------| +| PUSCH scheduled by MAC RAR as described in clause 8.2 of [6, TS 38.213] or MAC fallbackRAR as described in clause 8.2A of [6, 38.213] or for MsgA PUSCH transmission | | No | - | Default A | +| | | Yes | | pusch-TimeDomainAllocationList provided in pusch-ConfigCommon | +| C-RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI | Any common search space associated with CORESET 0 | No | - | Default A | +| | | Yes | | pusch-TimeDomainAllocationList provided in pusch-ConfigCommon | +| C-RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI | Any common search space not associated with CORESET 0, DCI format 0_0 in UE specific search space | No | No | Default A | +| | | Yes | No | pusch-TimeDomainAllocationList provided in pusch-ConfigCommon | +| | | No/Yes | Yes | pusch-TimeDomainAllocationList provided in pusch-Config | + +**Table 6.1.2.1.1-1A: Applicable PUSCH time domain resource allocation for DCI format 0\_1 in UE specific search space scrambled with C-RNTI, MCS-C-RNTI, CS-RNTI or SP-CSI-RNTI** + +| pusch-ConfigCommon includes pusch-TimeDomainAllocationList | pusch-Config includes pusch-TimeDomainAllocationList | pusch-Config includes pusch-TimeDomainAllocationListDCI-0-1 | pusch-Config includes pusch-TimeDomainAllocationListForMultiPUSCH | PUSCH time domain resource allocation to apply | +|--------------------------------------------------------------------------|--------------------------------------------------------------------|---------------------------------------------------------------------------|---------------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| No | No | No | No | Default A | +| Yes | No | No | No | pusch-TimeDomainAllocationList provided in pusch-ConfigCommon | +| No/Yes | Yes | No | No | pusch-TimeDomainAllocationList provided in pusch-Config | +| No/Yes | No | Yes | - | pusch-TimeDomainAllocationListDCI-0-1 provided in pusch-Config | +| No/Yes | No | - | Yes | pusch-TimeDomainAllocationListForMultiPUSCH provided in pusch-Config | + +**Table 6.1.2.1.1-1B: Applicable PUSCH time domain resource allocation for DCI format 0\_2 in UE specific search space scrambled with C-RNTI, MCS-C-RNTI, CS-RNTI or SP-CSI-RNTI** + +| pusch-ConfigCommon includes pusch-TimeDomainAllocationList | pusch-Config includes pusch-TimeDomainAllocationList | pusch-Config includes pusch-TimeDomainAllocationListDCI-0-2 | PUSCH time domain resource allocation to apply | +|-------------------------------------------------------------------|-------------------------------------------------------------|--------------------------------------------------------------------|------------------------------------------------------------------------------| +| No | No | No | Default A | +| Yes | No | No | pusch-TimeDomainAllocationList provided in pusch-ConfigCommon | +| No/Yes | Yes | No | pusch-TimeDomainAllocationList provided in pusch-Config | +| No/Yes | No | Yes | pusch-TimeDomainAllocationListDCI-0-2 provided in pusch-Config | + +**Table 6.1.2.1.1-1C: Applicable PUSCH time domain resource allocation for DCI format 0\_3 in UE specific search space scrambled with C-RNTI or MCS-C-RNTI** + +| pusch-ConfigCommon includes pusch-TimeDomainAllocationList | pusch-Config includes pusch-TimeDomainAllocationList | pusch-Config includes pusch-TimeDomainAllocationListDCI-0-1 | PUSCH time domain resource allocation to apply | +|-------------------------------------------------------------------|-------------------------------------------------------------|--------------------------------------------------------------------|------------------------------------------------------------------------------| +| No | No | No | Default A | +| Yes | No | No | pusch-TimeDomainAllocationList provided in pusch-ConfigCommon | +| No/Yes | Yes | No | pusch-TimeDomainAllocationList provided in pusch-Config | +| No/Yes | No | Yes | pusch-TimeDomainAllocationListDCI-0-1 provided in pusch-Config | + +**Table 6.1.2.1.1-2: Default PUSCH time domain resource allocation A for normal CP** + +| Row index | PUSCH mapping type | $K_2$ | S | L | +|-----------|--------------------|-------|---|----| +| 1 | Type A | $j$ | 0 | 14 | +| 2 | Type A | $j$ | 0 | 12 | +| 3 | Type A | $j$ | 0 | 10 | +| 4 | Type B | $j$ | 2 | 10 | +| 5 | Type B | $j$ | 4 | 10 | +| 6 | Type B | $j$ | 4 | 8 | +| 7 | Type B | $j$ | 4 | 6 | +| 8 | Type A | $j+1$ | 0 | 14 | +| 9 | Type A | $j+1$ | 0 | 12 | +| 10 | Type A | $j+1$ | 0 | 10 | +| 11 | Type A | $j+2$ | 0 | 14 | +| 12 | Type A | $j+2$ | 0 | 12 | +| 13 | Type A | $j+2$ | 0 | 10 | +| 14 | Type B | $j$ | 8 | 6 | +| 15 | Type A | $j+3$ | 0 | 14 | +| 16 | Type A | $j+3$ | 0 | 10 | + +**Table 6.1.2.1.1-3: Default PUSCH time domain resource allocation A for extended CP** + +| Row index | PUSCH mapping type | $K_2$ | S | L | +|-----------|--------------------|-------|---|----| +| 1 | Type A | $j$ | 0 | 8 | +| 2 | Type A | $j$ | 0 | 12 | +| 3 | Type A | $j$ | 0 | 10 | +| 4 | Type B | $j$ | 2 | 10 | +| 5 | Type B | $j$ | 4 | 4 | +| 6 | Type B | $j$ | 4 | 8 | +| 7 | Type B | $j$ | 4 | 6 | +| 8 | Type A | $j+1$ | 0 | 8 | +| 9 | Type A | $j+1$ | 0 | 12 | +| 10 | Type A | $j+1$ | 0 | 10 | +| 11 | Type A | $j+2$ | 0 | 6 | +| 12 | Type A | $j+2$ | 0 | 12 | +| 13 | Type A | $j+2$ | 0 | 10 | +| 14 | Type B | $j$ | 8 | 4 | +| 15 | Type A | $j+3$ | 0 | 8 | +| 16 | Type A | $j+3$ | 0 | 10 | + +**Table 6.1.2.1.1-4: Definition of value $j$** + +| $\mu_{PUSCH}$ | $j$ | +|---------------|-----| +| 0 | 1 | +| 1 | 1 | +| 2 | 2 | +| 3 | 3 | +| 5 | 11 | +| 6 | 21 | + +**Table 6.1.2.1.1-5: Definition of value $\Delta$** + +| $\mu_{PUSCH}$ | $\Delta$ | +|---------------|----------| +| 0 | 2 | +| 1 | 3 | +| 2 | 4 | +| 3 | 6 | +| 5 | 24 | +| 6 | 48 | + +#### 6.1.2.2 Resource allocation in frequency domain + +The UE shall determine the resource block assignment in frequency domain using the resource allocation field in the detected PDCCH DCI except for a PUSCH transmission scheduled by a RAR UL grant or fallbackRAR UL grant, in which case the frequency domain resource allocation is determined according to clause 8.3 of [6, 38.213] or a MsgA PUSCH transmission with frequency domain resource allocation determined according to clause 8.1A of [6, 38.213]. Three uplink resource allocation schemes type 0, type 1 and type 2 are supported. Uplink resource allocation scheme type 0 is supported for PUSCH only when transform precoding is disabled. Uplink resource allocation scheme type 1 and type 2 are supported for PUSCH for both cases when transform precoding is enabled or disabled. + +If the scheduling DCI is configured to indicate the uplink resource allocation type as part of the 'Frequency domain resource' assignment field by setting a higher layer parameter *resourceAllocation* in *pusch-Config* to 'dynamicSwitch', for DCI format 0\_1 or setting a higher layer parameter *resourceAllocationDCI-0-2* in *pusch-Config* to 'dynamicSwitch' for DCI format 0\_2 or setting a higher layer parameter *resourceAllocationDCI-0-3* in *pusch-Config* to 'dynamicSwitch' for DCI format 0\_3, the UE shall use uplink resource allocation type 0 or type 1 as defined by this DCI field. Otherwise the UE shall use the uplink frequency resource allocation type as defined by the higher layer parameter *resourceAllocation* for DCI format 0\_1 or the higher layer parameter *resourceAllocationDCI-0-2* for DCI format 0\_2. The UE shall assume that when the scheduling PDCCH is received with DCI format 0\_1 and *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated* is configured, uplink type 2 resource allocation is used. + +The UE shall assume that when the scheduling PDCCH is received with DCI format 0\_0, then uplink resource allocation type 1 is used, except when any of the higher layer parameters *useInterlacePUCCH-PUSCH* in *BWP-UplinkCommon* and *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated* is configured in which case uplink resource allocation type 2 is used. + +The UE expects that either none or both of *useInterlacePUCCH-PUSCH* in *BWP-UplinkCommon* and *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated* is configured. + +If a bandwidth part indicator field is not configured in the scheduling DCI or the UE does not support active bandwidth part change via DCI, the RB indexing for uplink type 0, type 1 and type 2 resource allocation is determined within the UE's active bandwidth part. If a bandwidth part indicator field is configured in the scheduling DCI and the UE supports active bandwidth part change via DCI, the RB indexing for uplink type 0, type 1, type 2 resource allocation is determined within the UE's bandwidth part indicated by bandwidth part indicator field value in the DCI. The UE shall upon detection of PDCCH intended for the UE determine first the uplink bandwidth part and then the resource allocation within the bandwidth part. RB numbering starts from the lowest RB in the determined uplink bandwidth part. + +##### 6.1.2.2.1.1 Uplink resource allocation type 0 + +In uplink resource allocation of type 0, the resource block assignment information includes a bitmap indicating the Resource Block Groups (RBGs) that are allocated to the scheduled UE where a RBG is a set of consecutive virtual resource blocks defined by higher layer parameter *rbg-Size* for DCI format 0\_1/0\_2 or *rbg-SizeDCI-0-3* for DCI format 0\_3 configured in *pusch-Config* and the size of the bandwidth part as defined in Table 6.1.2.2.1-1. + +**Table 6.1.2.2.1-1: Nominal RBG size $P$** + +| Bandwidth Part Size | Configuration 1 | Configuration 2 | Configuration 3 | +|---------------------|-----------------|-----------------|-----------------| +| 1 – 36 | 2 | 4 | 8 | +| 37 – 72 | 4 | 8 | 16 | +| 73 – 144 | 8 | 16 | 32 | +| 145 – 275 | 16 | 16 | 32 | + +The total number of RBGs ( $N_{RBG}$ ) for a uplink bandwidth part $i$ of size $PRBs$ is given by + +$$N_{RBG} = \left\lceil \left( N_{BWP,i}^{size} + (N_{BWP,i}^{start} \bmod P) \right) / P \right\rceil \text{ where}$$ + +- the size of the first RBG is $N_{BWP,i}^{start} \bmod P$ , +- the size of the last RBG is 1 if and $P$ otherwise. +- the size of all other RBG is $P$ . + +The bitmap is of size $N_{RBG}$ bits with one bitmap bit per RBG such that each RBG is addressable. The RBGs shall be indexed in the order of increasing frequency of the bandwidth part and starting at the lowest frequency. The order of RBG bitmap is such that RBG 0 to $N_{RBG}-1$ are mapped from MSB to LSB of the bitmap. The RBG is allocated to the UE if the corresponding bit value in the bitmap is 1, the RBG is not allocated to the UE otherwise. + +In frequency range 1, only 'almost contiguous allocation' defined in [8, TS 38.101-1] is allowed as non-contiguous allocation per component carrier for UL RB allocation for CP-OFDM. + +In frequency range 2, non-contiguous allocation per component carrier for UL RB allocation for CP-OFDM is not supported. + +##### 6.1.2.2.2 Uplink resource allocation type 1 + +In uplink resource allocation of type 1, the resource block assignment information indicates to a scheduled UE a set of contiguously allocated non-interleaved virtual resource blocks within the active bandwidth part of size $PRBs$ except for the case when DCI format 0\_0 is decoded in any common search space in which case the size of the initial UL + +bandwidth part $N_{BWP,0}^{size}$ shall be used. + +An uplink type 1 resource allocation field consists of a resource indication value ( $RIV$ ) corresponding to a starting virtual resource block ( $RB_{start}$ ) and a length in terms of contiguously allocated resource blocks. The resource indication value is defined by + +if then + +else + +where $\geq 1$ and shall not exceed. + +When the DCI size for DCI format 0\_0 in USS is derived from the initial UL BWP with size $N_{BWP}^{initial}$ but applied to another active BWP with size of $N_{BWP}^{active}$ , an uplink type 1 resource block assignment field consists of a resource indication value ( $RIV$ ) corresponding to a starting resource block $RB_{start} = 0, K, 2 \cdot K, \dots, (N_{BWP}^{initial} - 1) \cdot K$ and a length in terms of virtually contiguously allocated resource blocks $L_{RBs} = K, 2 \cdot K, \dots, N_{BWP}^{initial} \cdot K$ . + +The resource indication value is defined by + +$$\text{if } (L'_{RBs} - 1) \leq \left\lfloor N_{BWP}^{initial} / 2 \right\rfloor \text{ then}$$ + +$$RIV = N_{BWP}^{initial} (L'_{RBs} - 1) + RB'_{start}$$ + +else + +$$RIV = N_{BWP}^{initial} (N_{BWP}^{initial} - L'_{RBs} + 1) + (N_{BWP}^{initial} - 1 - RB'_{start})$$ + +where $L'_{RBs} = L_{RBs} / K$ , $RB'_{start} = RB_{start} / K$ and where $L'_{RBs}$ shall not exceed $N_{BWP}^{initial} - RB'_{start}$ . + +If $N_{BWP}^{active} > N_{BWP}^{initial}$ , $K$ is the maximum value from set $\{1, 2, 4, 8\}$ which satisfies $K \leq \left\lfloor N_{BWP}^{active} / N_{BWP}^{initial} \right\rfloor$ ; otherwise $K = 1$ . + +When the scheduling grant is received with DCI format 0\_2 or 0\_3, an uplink type 1 resource allocation field consists of a resource indication value ( $RIV$ ) corresponding to a starting resource block group $RBG_{start} = 0, 1, \dots, N_{RBG} - 1$ and a length in terms of virtually contiguously allocated resource block groups $L_{RBGs} = 1, \dots, N_{RBG}$ , where the resource block groups are defined as in 6.1.2.2.1 with $P$ defined by *resourceAllocationType1GranularityDCI-0-2* for DCI format 0\_2 and by *resourceAllocationType1GranularityDCI-0-3* for DCI format 0\_3 if the UE is configured with higher layer parameter *resourceAllocationType1GranularityDCI-0-2* or *resourceAllocationType1GranularityDCI-0-3*, and $P=1$ otherwise. The resource indication value is defined by + +$$\text{if } (L_{RBGs} - 1) \leq \left\lfloor N_{RBG} / 2 \right\rfloor \text{ then}$$ + +$$RIV = N_{RBG} (L_{RBGs} - 1) + RBG_{start}$$ + +else + +$$RIV = N_{RBG} (N_{RBG} - L_{RBGs} + 1) + (N_{RBG} - 1 - RBG_{start})$$ + +where $L_{RBGs} \geq 1$ and shall not exceed $N_{RBG} - RBG_{start}$ . + +##### 6.1.2.2.3 Uplink resource allocation type 2 + +In uplink resource allocation of type 2, the resource block assignment information defined in [5, TS 38.212] indicates to a UE a set of up to $M$ interlace indices, and for DCI format 0\_0 monitored in a UE-specific search space and DCI formats 0\_1 and 0\_3 a set of up to contiguous RB sets, where $M$ and interlace indexing are defined in Clause 4.4.4.6 in [4, TS 38.211]. Within the active UL BWP, the assigned physical resource block is mapped to virtual resource block. For DCI format 0\_0 monitored in a UE-specific search space and DCI formats 0\_1 and 0\_3, the UE shall determine the resource allocation in frequency domain as an intersection of the resource blocks of the indicated interlaces and the union of the indicated set of RB sets and intra-cell guard bands defined in Clause 7 between the indicated RB sets, if any. For DCI format 0\_0 monitored in a common search space, the UE shall determine the resource allocation in frequency domain as an intersection of the resource blocks of the indicated interlaces and a single uplink RB set of the active UL BWP. For DCI format 0\_0 monitored in a CSS with CRC scrambled by an RNTI other than TC-RNTI, the uplink RB set is the lowest indexed one amongst uplink RB set(s) that intersects the lowest-indexed CCE of the PDCCH in which the UE detects the DCI format 0\_0 in the active downlink BWP. When the PDCCH reception + +includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], for the purpose of determining the uplink RB set of a PUSCH when scheduled by DCI format 0\_0 monitored in a CSS with CRC scrambled by an RNTI other than TC-RNTI, the CORESET with lower ID among two CORESETs associated with two PDCCH candidates is used. If there is no intersection, the uplink RB set is RB set 0 in the active uplink BWP. For DCI format 0\_0 with CRC scrambled by TC-RNTI, the uplink RB set is the same one in which the UE transmits the PRACH associated with the RAR UL grant, in which case the UE assumes that the uplink RB set is defined as when the UE is not configured with *intraCellGuardBandsUL-List* (see Clause 7). + +For $\mu=0$ , the $X=6$ MSBs of the resource block assignment information indicates to a UE a set of allocated interlace indices $i$ , where the indication consists of a resource indication value ( $RIV$ ). For $i$ , the resource indication value corresponds to the starting interlace index $m_0$ and the number of contiguous interlace indices $L$ . The resource indication value is defined by: + +if then + +else + +For $i$ , the resource indication value corresponds to the starting interlace index $m_0$ and the set of values according to Table 6.1.2.2.3-1. + +**Table 6.1.2.2.3-1: $m_0$ and $L$ for $i$ .** + +| $i$ | $m_0$ | $L$ | +|-----|-------|--------------------------| +| 0 | 0 | {0, 5} | +| 1 | 0 | {0, 1, 5, 6} | +| 2 | 1 | {0, 5} | +| 3 | 1 | {0, 1, 2, 3, 5, 6, 7, 8} | +| 4 | 2 | {0, 5} | +| 5 | 2 | {0, 1, 2, 5, 6, 7} | +| 6 | 3 | {0, 5} | +| 7 | 4 | {0, 5} | + +For $\mu=1$ , the $X=5$ MSBs of the resource block assignment information comprise a bitmap indicating the interlaces that are allocated to the scheduled UE. The bitmap is of size $M$ bits with one bitmap bit per interlace such that each interlace is addressable, where $M$ and interlace indexing is defined in Clause 4.4.4.6 in [4, TS 38.211]. The order of interlace bitmap is such that interlace 0 to interlace $M-1$ are mapped from MSB to LSB of the bitmap. An interlace is allocated to the UE if the corresponding bit value in the bitmap is 1; otherwise the interlace is not allocated to the UE. + +For DCI format 0\_0 monitored in a UE-specific search space and DCI formats 0\_1 and 0\_3 for both $\mu=0$ and $\mu=1$ , the the resource block assignment information indicate to a UE a set of contiguously allocated RB sets for PUSCH scheduled by DCI format 0\_0 monitored in a UE-specific search space, DCI formats 0\_1 and 0\_3 and Type 1 and Type 2 configured grant. The resource allocation field consists of a resource indication value ( $RIV$ ). For $i$ , the resource indication value corresponds to the starting RB set index $m_0$ and the number of contiguous RB sets $L$ . The resource indication value is defined by: + +if then + +else + +where $i$ , $m_0$ and $L$ shall not exceed + +If transform precoding is enabled according to the procedure in Clause 6.1.3, then the UE transmits PUSCH on the lowest-indexed PRBs amongst the PRBs indicated by the frequency domain resource assignment information. $i$ is the largest integer not greater than the number of RBs indicated by the frequency domain resource assignment information that fulfils the conditions in Clause 6.3.1.4 of [4, TS 38.211]. + +#### 6.1.2.3 Resource allocation for uplink transmission with configured grant + +When PUSCH resource allocation is semi-statically configured by higher layer parameter *configuredGrantConfig* in *BWP-UplinkDedicated* information element, and the PUSCH transmission corresponding to a configured grant, the following higher layer parameters are applied in the transmission: + +- For Type 1 PUSCH transmissions with a configured grant, the following parameters are given in *configuredGrantConfig* unless mentioned otherwise: + - For the determination of the PUSCH repetition type, if the higher layer parameter *pusch-RepTypeIndicator* in *rrc-ConfiguredUplinkGrant* is configured and set to 'pusch-RepTypeB', PUSCH repetition type B is applied; otherwise, PUSCH repetition type A is applied; + - For PUSCH repetition type A, the selection of the time domain resource allocation table follows the rules for DCI format 0\_0 on UE specific search space, as defined in Clause 6.1.2.1.1. + - For PUSCH repetition type B, the selection of the time domain resource allocation table is as follows: + - If *pusch-RepTypeIndicatorDCI-0-1* in *pusch-Config* is configured and set to 'pusch-RepTypeB', *pusch-TimeDomainAllocationListDCI-0-1* in *pusch-Config* is used; + - Otherwise, *pusch-TimeDomainAllocationListDCI-0-2* in *pusch-Config* is used. + - It is not expected that *pusch-RepTypeIndicator* in *rrc-ConfiguredUplinkGrant* is configured with 'pusch-RepTypeB' when none of *pusch-RepTypeIndicatorDCI-0-1* and *pusch-RepTypeIndicatorDCI-0-2* in *pusch-Config* is set to 'pusch-RepTypeB'. + - The higher layer parameter *timeDomainAllocation* value *m* provides a row index *m+1* pointing to the determined time domain resource allocation table, where the start symbol and length are determined following the procedure defined in Clause 6.1.2.1; + - Frequency domain resource allocation is determined by the *N* LSB bits in the higher layer parameter *frequencyDomainAllocation*, forming a bit sequence, where *i* is the LSB, according to the procedure in Clause 6.1.2.2 and *N* is determined as the size of frequency domain resource assignment field in DCI format 0\_1 for a given resource allocation type indicated by *resourceAllocation*, except if *useInterlacePUCCH-PUSCH* in *BWP-UplinkDedicated* is configured, in which case uplink type 2 resource allocation is used wherein the UE interprets the LSB bits in the higher layer parameter *frequencyDomainAllocation* as for the frequency domain resource assignment field of DCI 0\_1 according to the procedure in Clause 6.1.2.2.3; + - The *IMCS* is provided by higher layer parameter *mcsAndTBS*; + - Number of DM-RS CDM groups, DM-RS ports, SRS resource indication and DM-RS sequence initialization are determined as in Clause 7.3.1.1.2 of [5, TS 38.212], and the antenna port value, the bit value for DM-RS sequence initialization, precoding information and number of layers, SRS resource indicator are provided by *antennaPort*, *dmrs-SeqInitialization*, *precodingAndNumberOfLayers*, and *srs-ResourceIndicator* respectively; When two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2*, precoding information and number of layers (applicable when higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook') associated with the first and second SRS resource set is provided by *precodingAndNumberOfLayers* and *precodingAndNumberOfLayers2*, respectively, and SRS resource indicators associated with the first and second SRS resource sets are provided by *srs-ResourceIndicator* and *srs-ResourceIndicator2*, respectively. When both *srs-ResourceSetToAddModList* and *srs-ResourceSetToAddModListDCI-0-2* are configured with two SRS resource sets, the two SRS resource sets configured by *srs-ResourceSetToAddModList* is used to determine the SRS resource indications by *srs-ResourceIndicator* and *srs-ResourceIndicator2*. + - If two SRS resource sets with usage set to 'codebook' or 'noncodebook' are configured in *srs-ResourceSetToAddModList*, the two SRS resource sets are used to determine the SRS resource indications by *srs-ResourceIndicator* and *srs-ResourceIndicator2*. + - otherwise, the two SRS resource sets with usage set to 'codebook' or 'noncodebook' configured in *srs-ResourceSetToAddModListDCI-0-2* are used to determine the SRS resource indications by *srs-ResourceIndicator* and *srs-ResourceIndicator2*. + +- When frequency hopping is enabled, the frequency offset between two frequency hops can be configured by higher layer parameter *frequencyHoppingOffset*. +- For Type 2 PUSCH transmissions with a configured grant: the resource allocation follows the higher layer configuration according to [10, TS 38.321], and UL grant received on the DCI. +- The PUSCH repetition type and the time domain resource allocation table are determined by the PUSCH repetition type and the time domain resource allocation table associated with the UL grant received on the DCI, respectively, as defined in Clause 6.1.2.1. The value of $K_{offset}$ , if configured, is applied when determining the first transmission opportunity. + +For PUSCH transmissions with a Type 1 or Type 2 configured grant, the number of (nominal) repetitions $K$ to be applied to the transmitted transport block is provided by the indexed row in the time domain resource allocation table if *numberOfRepetitions* is present in the table; otherwise $K$ is provided by the higher layer configured parameters *repK*. For a *configuredGrantConfig*, if a UE is configured with higher layer parameter [*nrofSlots\_InCGperiod*], the UE does not support repetition nor the TB processing over multiple slots for the *configuredGrantConfig*. + +For PUSCH transmissions with a Type 2 configured grant, when two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2*, the SRS resource set association to (nominal) repetitions follows *MappingPattern* in *ConfiguredGrantConfig* as defined in Clause 6.1.2.1 for PUSCH scheduled by DCI format 0\_1 and 0\_2. For PUSCH transmissions with a Type 1 configured grant, when two SRS resource sets with usage set to 'codebook' or 'noncodebook' are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2*, if *p0-PUSCH-Alpha2* is provided, the SRS resource set association to (nominal) repetitions is determined as follows. When $K = 2$ , the first and second SRS resource sets are applied to the first and second (nominal) repetitions, respectively. + +- When $K > 2$ and *cyclicMapping* in *ConfiguredGrantConfig* is enabled, the first and second SRS resource sets are applied to the first and second (nominal) repetitions, respectively, and the same SRS resource set mapping pattern continues to the remaining (nominal) repetitions. +- When $K > 2$ and *sequentialMapping* in *ConfiguredGrantConfig* is enabled, first SRS resource set is applied to the first and second (nominal) repetitions, and the second SRS resource set is applied to the third and fourth (nominal) repetitions, and the same SRS resource set mapping pattern continues to the remaining (nominal) repetitions. + +For PUSCH transmissions with a Type 1 configured grant, when two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2*, if *configuredGrantConfig* contains only one *pathlossReferenceIndex*, *p0-PUSCH-Alpha*, *powerControlLoopToUse*, *srs-ResourceIndicator* and *precodingAndNumberOfLayers* (applicable when higher layer parameter usage in *SRS-ResourceSet* set to 'codebook'), PUSCH repetitions are associated only with the first SRS resource set. + +If the UE is provided two SRS resource sets in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with *usage* set to 'codebook' or 'nonCodebook', and the UE is not provided *p0-PUSCH-Alpha2* and *powerControlLoopToUse2*, for a retransmission of a configured grant Type 1 PUSCH, or for activation or retransmission of a configured grant Type 2 PUSCH, scheduled by a DCI format that includes an SRS resource set indicator field, the UE expects the value of the SRS resource set indicator field to be set to '00', and PUSCH repetitions are associated only with the first SRS resource set. + +The UE shall not transmit anything on the resources configured by *configuredGrantConfig* if the higher layers did not deliver a transport block to transmit on the resources allocated for uplink transmission without grant. + +A set of allowed periodicities $P$ are defined in [12, TS 38.331]. The higher layer parameter *cg-nrofSlots*, provides the number of consecutive slots allocated within a configured grant period. The higher layer parameter *cg-nrofPUSCH-InSlot* provides the number of consecutive PUSCH allocations within a slot, where the first PUSCH allocation follows the higher layer parameter *timeDomainAllocation* for Type 1 PUSCH transmission or the higher layer configuration according to [10, TS 38.321], and UL grant received on the DCI for Type 2 PUSCH transmissions, and the remaining PUSCH allocations have the same length and PUSCH mapping type, and are appended following the previous allocations without any gaps. The higher layer parameter [*nrofSlots\_InCGperiod*] provides the number of consecutive slots allocated within a configured grant period. The same combination of start symbol and length and PUSCH mapping type repeats over the consecutively allocated slots if *cg-nrofSlots* or [*nrofSlots\_InCGperiod*] is configured. If [*nrofSlots\_InCGperiod*] is configured, the PUSCH allocation in each consecutive slot follows the higher layer parameter *timeDomainAllocation* for Type 1 PUSCH transmission or the higher layer configuration according to [10, TS 38.321], and UL grant received in the DCI for Type 2 PUSCH transmissions. If a UE is configured with higher layer + +parameter *nrofSlots\_InCGperiod* in a *configuredGrantConfig*, the UE does not expect to be configured with *cg-nrofSlots* and *cg-nrofPUSCH-InSlot* in the *configuredGrantConfig*. + +For operation with shared spectrum channel access, and when the higher layer parameter *semiStaticChannelAccessConfigUE* is not configured, where a UE is performing uplink transmission with configured grants in contiguous OFDM symbols on all resource blocks of an RB set, for the first such UL transmission the UE determines a duration of a cyclic prefix extension $T_{ext}$ to be applied for transmission according to [4, TS 38.211] where the index for [4, TS 38.211] is chosen randomly from a set of values configured by higher layers according to the following rule: + +- If the first such UL transmission is within a channel occupancy initiated by the gNB (defined in Clause 4 of [16, TS 37.213]), the set of values is determined by *cg-StartingFullBW-InsideCOT*; +- otherwise, the set of values is determined by *cg-StartingFullBW-OutsideCOT*. + +For operation with shared spectrum channel access, and when the higher layer parameter *semiStaticChannelAccessConfigUE* is not configured, where a UE is performing uplink transmission with configured grants in contiguous OFDM symbols on fewer than all resource blocks of an RB set, for the first such UL transmission the UE determines a duration of a cyclic prefix extension $T_{ext}$ to be applied for transmission according to [4, TS 38.211] according to the following rule: + +- If the first such UL transmission is within a channel occupancy initiated by the gNB (defined in Clause 4 of [16, TS 37.213]), the index for [4, TS 38.211] is equal to *cg-StartingPartialBW-InsideCOT*; +- otherwise, the index for [4, TS 38.211] is equal to *cg-StartingPartialBW-OutsideCOT*. + +##### 6.1.2.3.1 Transport Block repetition for uplink transmissions of PUSCH repetition Type A with a configured grant + +The procedures described in this clause apply to PUSCH transmissions of PUSCH repetition Type A with a Type 1 or Type 2 configured grant. + +The higher layer parameter *repK-RV* defines the redundancy version pattern to be applied to the repetitions. If *cg-RetransmissionTimer* is provided, the redundancy version for uplink transmission with a configured grant is determined by the UE. If the parameter *repK-RV* is not provided in the *configuredGrantConfig* and *cg-RetransmissionTimer* is not provided, the redundancy version for uplink transmissions with a configured grant shall be set to 0. If the parameter *repK-RV* is provided in the *configuredGrantConfig* and *cg-RetransmissionTimer* is not provided, for the $n$ th transmission occasion among $K$ repetitions, $n=1, 2, \dots, K$ , it is associated with $(\text{mod}((n-\text{mod}(n, N))/N-1, 4)+1)^{\text{th}}$ value in the configured RV sequence, where $N=1$ . If a configured grant configuration is configured with *startingFromRV0* set to 'off', the initial transmission of a transport block may only start at the first transmission occasion of the $K$ repetitions. Otherwise, the initial transmission of a transport block may start at + +- the first transmission occasion of the $K$ repetitions if the configured RV sequence is $\{0, 2, 3, 1\}$ , +- any of the transmission occasions of the $K$ repetitions that are associated with RV=0 if the configured RV sequence is $\{0, 3, 0, 3\}$ , +- any of the transmission occasions of the $K$ repetitions if the configured RV sequence is $\{0, 0, 0, 0\}$ , except the last transmission occasion when $K \geq 8$ . + +When the transmission occasions are associated with the first and second SRS resource sets, if the parameter *repK-RV* is provided in the *configuredGrantConfig*, for the $n$ th transmission occasion among all transmission occasions that are associated with the SRS resource set of the first transmission occasion, it is associated with $(\text{mod}(n-1, 4)+1)^{\text{th}}$ value in the configured RV sequence, and for the $n$ th transmission occasion among all transmission occasions that are not associated with the SRS resource set of the first transmission occasion, it is associated with $(\text{mod}(n-1, 4)+1)^{\text{th}}$ value in the adjusted RV sequence and the adjustment is based on additional shifting operation on the configured RV sequence, where the shifting operation is defined as where is the $i^{\text{th}}$ RV value ( $i=1, 2, 3, 4$ ) in the configured RV sequence and is configured by the higher layer parameter *sequenceOffsetforRV* in *configuredGrantConfig*. When the transmission occasions are associated with the first and second SRS resource sets, if a configured grant configuration is configured with *startingFromRV0* set to 'off', the initial transmission of a transport block may only start at the first transmission occasion of the $K$ repetitions. Otherwise, the initial transmission of a transport block may start at + +- the first transmission occasion associated with RV = 0 corresponding to the first or second SRS resource set of the $K$ repetitions if the configured RV sequence is $\{0, 2, 3, 1\}$ , + +- any of the transmission occasions of the $K$ repetitions that are associated with RV=0 if the configured RV sequence is {0,3,0,3}, +- any of the transmission occasions of the $K$ repetitions if the configured RV sequence is {0,0,0,0}, except the last transmission occasion when $K \geq 8$ . + +After the initial transmission of a transport block, later transmission occasions among the $K$ repetitions associated with any RV value and associated to any of the first or second SRS resource set can be used for transmitting the transport block. + +For any RV sequence, the repetitions shall be terminated after transmitting $K$ repetitions, or at the last transmission occasion among the $K$ repetitions within the period $P$ , or from the starting symbol of the repetition that overlaps with a PUSCH with the same HARQ process scheduled by DCI format 0\_0, 0\_1, 0\_2 or 0\_3, whichever is reached first. In addition, the UE shall terminate the repetition of a transport block in a PUSCH transmission if the UE receives a DCI format 0\_1 with DFI flag provided and set to '1', and if in this DCI the UE detects ACK for the HARQ process corresponding to that transport block. + +The UE is not expected to be configured with the time duration for the transmission of $K$ repetitions larger than the time duration derived by the periodicity $P$ . If the UE determines that, for a transmission occasion, the number of symbols available for the PUSCH transmission in a slot is smaller than transmission duration $L$ , the UE does not transmit the PUSCH in the transmission occasion. + +For both Type 1 and Type 2 PUSCH transmissions with a configured grant, when $K > 1$ , + +- For unpaired spectrum: + - If *AvailableSlotCounting* is enabled, the UE shall repeat the TB across the slots determined for the PUSCH transmission applying the same symbol allocation in each slot. + - A slot is not counted in the number of slots if at least one of the symbols indicated by the indexed row of the used resource allocation table in the slot overlaps with a DL symbol indicated by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* if provided, or a symbol of an SS/PBCH block with index provided by *ssb-PositionsInBurst*. + - Otherwise, the UE shall repeat the TB across the consecutive slots applying the same symbol allocation in each slot, except if the UE is provided with higher layer parameters *cg-nrofSlots* and *cg-nrofPUSCH-InSlot*, in which case the UE repeats the TB in the *repK* earliest consecutive transmission occasion candidates within the same configuration. +- For paired spectrum and SUL band: + - The UE shall repeat the TB across the consecutive slots applying the same symbol allocation in each slot, except if the UE is provided with higher layer parameters *cg-nrofSlots* and *cg-nrofPUSCH-InSlot*, in which case the UE repeats the TB in the *repK* earliest consecutive transmission occasion candidates within the same configuration. + - If *AvailableSlotCounting* is enabled, and in case of reduced capability half-duplex UE, the UE shall repeat the TB across the slots applying the same symbol allocation in each slot. A slot is not counted in the number of slots if at least one of the symbols indicated by the indexed row of the used resource allocation table in the slot does not start or end at least one or , respectively, from the last or first symbol of an SS/PBCH block with index provided by *ssb-PositionsInBurst*. + +A Type 1 or Type 2 PUSCH transmission with a configured grant in a slot is omitted according to the conditions in Clause 9, Clause 11.1, Clause 11.2A, Clause 15 and Clause 17.2 of [6, TS 38.213]. + +##### 6.1.2.3.2 Transport Block repetition for uplink transmissions of PUSCH repetition Type B with a configured grant + +The procedures described in this Clause apply to PUSCH transmissions of PUSCH repetition type B with a Type 1 or Type 2 configured grant. + +For PUSCH transmissions with a Type 1 or Type 2 configured grant, the nominal repetitions and the actual repetitions are determined according to the procedures for PUSCH repetition Type B defined in Clause 6.1.2.1. The higher layer configured parameters *repK-RV* defines the redundancy version pattern to be applied to the repetitions. If the parameter *repK-RV* is not provided in the *configuredGrantConfig*, the redundancy version for each actual repetition with a + +configured grant shall be set to 0. Otherwise, for the $n$ th transmission occasion among all the actual repetitions (including the actual repetitions that are omitted) of the $K$ nominal repetitions, it is associated with $(\text{mod}((n - \text{mod}(n, N))/N - 1, 4) + 1)^{\text{th}}$ value in the configured RV sequence, where $N = 1$ . If a configured grant configuration is configured with *startingFromRV0* set to 'off', the initial transmission of a transport block may only start at the first transmission occasion of the actual repetitions. Otherwise, the initial transmission of a transport block may start at + +- the first transmission occasion of the actual repetitions if the configured RV sequence is $\{0, 2, 3, 1\}$ , +- any of the transmission occasions of the actual repetitions that are associated with RV=0 if the configured RV sequence is $\{0, 3, 0, 3\}$ , +- any of the transmission occasions of the actual repetitions if the configured RV sequence is $\{0, 0, 0, 0\}$ , except the actual repetitions within the last nominal repetition when $K \geq 8$ . + +When the transmission occasions are associated with the first and second SRS resource sets, if the parameter *repK-RV* is provided in the *configuredGrantConfig*, for the $n$ th transmission occasion among all actual repetitions (including the actual repetitions that are omitted) that are associated with the SRS resource set of the first transmission occasion, it is associated with $(\text{mod}(n - 1, 4) + 1)^{\text{th}}$ value in the configured RV sequence, and for the $n$ th transmission occasion among all actual repetitions that are not associated with the SRS resource set of the first transmission occasion, it is associated with $(\text{mod}(n - 1, 4) + 1)^{\text{th}}$ value in the adjusted RV sequence and the adjustment is based on additional shifting operation on the configured RV sequence, where the shifting operation is defined as where is the $i^{\text{th}}$ RV value ( $i=1, 2, 3, 4$ ) in the configured RV sequence and is configured by the higher layer parameter *sequenceOffsetforRV* in *configuredGrantConfig*. When the transmission occasions are associated with the first and second SRS resource sets, if a configured grant configuration is configured with *startingFromRV0* set to 'off', the initial transmission of a transport block may only start at the first transmission occasion of the $K$ repetitions. Otherwise, the initial transmission of a transport block may start at + +- the first transmission occasion associated with RV = 0 corresponding to the first or second SRS resource set of the $K$ repetitions if the configured RV sequence is $\{0, 2, 3, 1\}$ , +- any of the transmission occasions of the $K$ repetitions that are associated with RV=0 if the configured RV sequence is $\{0, 3, 0, 3\}$ , +- any of the transmission occasions of the $K$ repetitions if the configured RV sequence is $\{0, 0, 0, 0\}$ , except the last transmission occasion when $K \geq 8$ . + +After the initial transmission of a transport block, later transmission occasions among the $K$ repetitions associated with any RV value and associated to any of the first or second SRS resource set can be used for transmitting the transport block. + +For any RV sequence, the repetitions shall be terminated after transmitting $K$ nominal repetitions, or at the last transmission occasion among the $K$ nominal repetitions within the period $P$ , or from the starting symbol of an actual repetition that overlaps with a PUSCH with the same HARQ process scheduled by DCI format 0\_0, 0\_1, 0\_2 or 0\_3, whichever is reached first. The UE is not expected to be configured with the time duration for the transmission of $K$ nominal repetitions larger than the time duration derived by the periodicity $P$ . + +##### 6.1.2.3.3 Transport Block repetition for uplink transmissions of TB processing over multiple slots with a configured grant + +The procedures described in this clause apply to PUSCH transmissions of TB processing over multiple slots with a Type 2 configured grant. + +The higher layer parameter *repK-RV* defines the redundancy version pattern to be applied to the repetitions. If the parameter *repK-RV* is not provided in the *configuredGrantConfig*, the redundancy version for uplink transmissions with a configured grant shall be set to 0. If the parameter *repK-RV* is provided in the *configuredGrantConfig*, the $n$ th transmission occasion among transmissions occasions, $n=0, 1, \dots, -1$ , is associated with $(\text{mod}((n - \text{mod}(n, N))/N, 4) + 1)^{\text{th}}$ value in the configured RV sequence. When $K=1$ , or when $K > 1$ and the configured grant configuration is configured with *startingFromRV0* set to 'off', the initial transmission of the transport block may only start at the first transmission occasion of the transmission occasions. Otherwise, the initial transmission of the transport block may start at + +- The first transmission occasion of the transmission occasions if the configured RV sequence is $\{0, 2, 3, 1\}$ . +- Any transmission occasion $n$ associated with RV=0, and for which $n \bmod N = 0$ , if the configured RV sequence is $\{0, 3, 0, 3\}$ or $\{0, 0, 0, 0\}$ . + +The UE is not expected to be configured with the time duration for transmissions larger than the time duration derived by the periodicity $P$ . If the UE determines that, for a transmission occasion, the number of symbols available in a slot for the PUSCH transmission of TB processing over multiple slots is smaller than transmission duration $L$ , the UE does not transmit the PUSCH in the transmission occasion. + +For unpaired spectrum: + +- The UE determines slots for a PUSCH transmission of TB processing over multiple slots with a Type 2 configured grant activated by DCI format 0\_1 or 0\_2, based on *tdd-UL-DL-ConfigurationCommon*, *tdd-UL-DL-ConfigurationDedicated* and *ssb-PositionsInBurst*, and the TDRA information field value in the DCI format 0\_1 or 0\_2. +- A slot is not counted in the number of slots for a PUSCH transmission of TB processing over multiple slots with a Type 2 configured grant activated by DCI format 0\_1 or 0\_2 if at least one of the symbols indicated by the indexed row of the used resource allocation table in the slot overlaps with a DL symbol indicated by *tdd-UL-DL-ConfigurationCommon* or *tdd-UL-DL-ConfigurationDedicated* if provided, or a symbol of an SS/PBCH block with index provided by *ssb-PositionsInBurst*. + +For paired spectrum and SUL band: + +- The UE determines consecutive slots for a PUSCH transmission of TB processing over multiple slots with a Type 2 configured grant activated by DCI format 0\_1 or 0\_2, based on the TDRA information field value in the DCI format 0\_1 or 0\_2. +- For the case of a reduced capability half-duplex UE, the UE determines slots for a PUSCH transmission of TB processing over multiple slots with a Type 2 configured grant activated by DCI format 0\_1 or 0\_2, based on the TDRA information field value in the DCI format 0\_1 or 0\_2. A slot is not counted in the number of slots if at least one of the symbols indicated by the indexed row of the used resource allocation table in the slot does not start or end at least $L$ or $L-1$ , respectively, from the last or first symbol of an SS/PBCH block with index provided by *ssb-PositionsInBurst*. + +For Type 2 PUSCH transmission with a configured grant of TB processing over multiple slots, the UE shall transmit the TB across the slots determined for the PUSCH transmission applying the same symbol allocation in each slot. A Type 2 PUSCH transmission with a configured grant of TB processing over multiple slots is omitted in a slot according to the conditions in Clause 9, Clause 11.1, Clause 11.2A, Clause 15 and Clause 17.2 of [6, TS 38.213]. + +### 6.1.3 UE procedure for applying transform precoding on PUSCH + +For a PUSCH scheduled by RAR UL grant, or for a PUSCH scheduled by fallbackRAR UL grant, or for a PUSCH scheduled by DCI format 0\_0 with CRC scrambled by TC-RNTI, the UE shall consider the transform precoding either 'enabled' or 'disabled' according to the higher layer configured parameter *msg3-transformPrecoder*. + +For a MsgA PUSCH, the UE shall consider the transform precoding either 'enabled' or 'disabled' according to the higher layer configured parameter *msgA-TransformPrecoder*. If higher layer parameter *msgA-TransformPrecoder* is not configured, the UE shall consider the transform precoding either 'enabled' or 'disabled' according to the higher layer configured parameter *msg3-transformPrecoder*. + +For PUSCH transmission scheduled by a PDCCH with CRC scrambled by CS-RNTI with NDI=1, C-RNTI, or MCS-C-RNTI or SP-CSI-RNTI: + +- If the DCI with the scheduling grant was received with DCI format 0\_0, the UE shall, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter *msg3-transformPrecoder*. +- If the DCI with the scheduling grant was not received with DCI format 0\_0 + - If the DCI with the scheduling grant was received with DCI format 0\_1 or 0\_2 with CRC scrambled by C-RNTI, MCS-RNTI, or CS-RNTI with NDI=1 and if the UE is configured with a higher layer parameter [*dynamicTransformPrecoderIndicationDCI-0-1*] in *pusch-Config* for DCI format 0\_1 or [*dynamicTransformPrecoderIndicationDCI-0-2*] in *pusch-Config* for DCI format 0\_2 and the higher layer parameter is set to 'enabled', + - the UE shall, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the Transform precoder indicator field in the DCI with the scheduling grant. + +- For *pusch-TimeDomainAllocationListForMultiPUSCH* in *pusch-Config*, the UE shall, for all PUSCH transmissions, consider the transform precoding either enabled or disabled according to Transform precoder indicator field in the DCI format 0\_1 with the scheduling grant. +- If *resourceAllocation* in *pusch-Config* for DCI format 0\_1 or *resourceAllocationDCI-0-2* in *pusch-Config* for DCI format 0\_2 is set to *resourceAllocationType0*, or if the resource allocation is set to resource allocation type 0 according to the DCI configuration as described in clauses 7.3.1.1.2 and 7.3.1.1.3 of [6, TS 38.212], or if *dmrs-Type* in *DMRS-UplinkConfig* is set to 'type 2' for this PUSCH transmission, the UE does not expect that the Transform precoder indicator field in the DCI with the scheduling grant indicates that transform precoding is enabled. +- If the UE is configured with the higher layer parameter *enhanced-dmrs-Type-r18* in *DMRS-UplinkConfig*, and if the scheduling grant indicates that transform precoding is enabled for the scheduled PUSCH transmission, the UE ignores the higher layer parameters *enhanced-dmrs-Type-r18* in *DMRS-UplinkConfig*, if configured, for the DM-RS transmission of the scheduled PUSCH transmission. +- Otherwise, + - If the UE is configured with the higher layer parameter *transformPrecoder* in *pusch-Config*, the UE shall, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. + - If the UE is not configured with the higher layer parameter *transformPrecoder* in *pusch-Config*, the UE shall, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter *msg3-transformPrecoder*. + +For PUSCH transmission with a configured grant + +- If the UE is configured with the higher layer parameter *transformPrecoder* in *configuredGrantConfig*, the UE shall, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. +- If the UE is not configured with the higher layer parameter *transformPrecoder* in *configuredGrantConfig*, the UE shall, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter *msg3-transformPrecoder*. + +### 6.1.4 Modulation order, redundancy version and transport block size determination + +To determine the modulation order, target code rate, redundancy version and transport block size for the physical uplink shared channel, the UE shall first + +- read the 5-bit modulation and coding scheme field in the DCI scheduling PUSCH or provided in a DCI activating a configured grant Type 2 PUSCH, or as provided by *mcsAndTBS* as described in Clause 6.1.2.3 for a configured grant Type 1 PUSCH to determine the modulation order and target code rate ( $R$ ) based on the procedure defined in Clause 6.1.4.1 +- read redundancy version field ( $rv$ ) in the DCI to determine the redundancy version for PUSCH scheduled by DCI, or determine the redundancy version according to Clause 6.1.2.3.1 for configured grant Type 1 and Type 2 PUSCH, + +and second + +- use the number of layers , the total number of allocated PRBs to determine the transport block size based on the procedure defined in Clause 6.1.4.2. + +When the UE is scheduled with multiple PUSCHs on a serving cell by a DCI, as described in clause 6.1.2.1, the bits of $rv$ field and NDI field, respectively, in the DCI are one to one mapped to the scheduled PUSCH(s) indicated by the TDRA information field with the corresponding transport block(s) in the scheduled order where the LSB bits of the $rv$ field and NDI field, respectively, correspond to the last scheduled PUSCH indicated by the TDRA information field. + +Within a cell group, a UE is not required to handle PUSCH(s) transmissions in slot $s_j$ in serving cell- $j$ , and for $j = 0, 1, 2, \dots, J-1$ , slot $s_j$ overlapping with any given point in time, if the following condition is not satisfied at that point in time: + +where + +- $J$ is the number of configured serving cells belong to a frequency range +- for the $j$ -th serving cell, + - $M$ is the number of TB(s) transmitted in slot $s_j$ . For PUSCH repetition Type B, each actual repetition is counted separately. + - $T_{slot}^{\mu(j)} = 10^{-3}/2^{\mu(j)}$ , where $\mu(j)$ is the numerology for PUSCH(s) in slot $s_j$ of the $j$ -th serving cell. + - for the $m$ -th TB, + - $A$ is the number of bits in the transport block as defined in Clause 6.2.1 [5, TS 38.212] + - $C$ is the total number of code blocks for the transport block defined in Clause 5.2.2 [5, TS 38.212]. + - $\hat{C}$ is the number of scheduled code blocks for the transport block as defined in Clause 5.4.2.1 [5, 38.212] +- [Mbps] is computed as the maximum data rate summed over all the carriers in the frequency range for any signaled band combination and feature set consistent with the configured serving cells, where the data rate value is given by the formula in Clause 4.1.2 in [13, TS 38.306], including the scaling factor $f(i)$ . + +For a $j$ -th serving cell, if higher layer parameter *processingType2Enabled* of *PUSCH-ServingCellConfig* is configured for the serving cell and set to 'enable', or if at least one $I_{MCS} > W$ for a PUSCH, where $W = 28$ for MCS tables 5.1.3.1-1 and 5.1.3.1-3, and $W = 27$ for MCS tables 5.1.3.1-2, 6.1.4.1-1, and 6.1.4.1-2, or if it is an actual repetition for PUSCH repetition Type B, the UE is not required to handle PUSCH transmissions, if the following condition is not satisfied: + +where + +- $N_{symbols}$ is the number of symbols assigned to the PUSCH +- $M$ is the number of TB in the PUSCH +- where $\mu$ is the numerology of the PUSCH +- for the $m$ -th TB, + - $A$ is the number of bits in the transport block as defined in Clause 6.2.1 [5, TS 38.212] + - $C$ is the total number of code blocks for the transport block defined in Clause 5.2.2 [5, TS 38.212] + - $\hat{C}$ is the number of scheduled code blocks for the transport block as defined in Clause 5.4.2.1 [5, TS 38.212] +- [Mbps] is computed as the maximum data rate for a carrier in the frequency band of the serving cell for any signaled band combination and feature set consistent with the serving cell, where the data rate value is given by the formula in Clause 4.1.2 in [13, TS 38.306], including the scaling factor $f(i)$ +- each actual repetition for PUSCH repetition type B is treated as one PUSCH. + +#### 6.1.4.1 Modulation order and target code rate determination + +For a PUSCH scheduled by RAR UL grant or + +for a PUSCH scheduled by a fallbackRAR UL grant or + +for a MsgA PUSCH transmission, or + +for a PUSCH scheduled by a DCI format 0\_0 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, or + +for a PUSCH scheduled by a DCI format 0\_1 or DCI format 0\_2 with CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI, SP-CSI-RNTI, or + +for a PUSCH scheduled by a DCI format 0\_3 with CRC scrambled by C-RNTI, MCS-C-RNTI, or + +for a PUSCH with configured grant using CS-RNTI, and + +if transform precoding is disabled for this PUSCH transmission according to Clause 6.1.3 + +- if *mcs-TableDCI-0-2* in *pusch-Config* is set to 'qam256', and PUSCH is scheduled by a PDCCH with DCI format 0\_2 with CRC scrambled by C-RNTI or SP-CSI-RNTI, + - the UE shall use $I_{MCS}$ and Table 5.1.3.1-2 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel; +- elseif the UE is not configured with MCS-C-RNTI, *mcs-TableDCI-0-2* in *pusch-Config* is set to 'qam64LowSE', and the PUSCH is scheduled by a PDCCH with DCI format 0\_2 with CRC scrambled by C-RNTI or SP-CSI-RNTI, + - the UE shall use $I_{MCS}$ and Table 5.1.3.1-3 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel. +- elseif *mcs-Table* in *pusch-Config* is set to 'qam256', and PUSCH is scheduled by a PDCCH with DCI format 0\_1 or 0\_3 with CRC scrambled by C-RNTI or SP-CSI-RNTI, + - the UE shall use $I_{MCS}$ and Table 5.1.3.1-2 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel. +- elseif the UE is not configured with MCS-C-RNTI, *mcs-Table* in *pusch-Config* is set to 'qam64LowSE', and the PUSCH is scheduled by a PDCCH with a DCI format other than DCI format 0\_2 in a UE-specific search space with CRC scrambled by C-RNTI or SP-CSI-RNTI, + - the UE shall use $I_{MCS}$ and Table 5.1.3.1-3 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel. +- elseif the UE is configured with MCS-C-RNTI, and the PUSCH is scheduled by a PDCCH with CRC scrambled by MCS-C-RNTI, + - the UE shall use $I_{MCS}$ and Table 5.1.3.1-3 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel. +- elseif *mcs-Table* in *configuredGrantConfig* is set to 'qam256', + - if PUSCH is scheduled by a PDCCH with CRC scrambled by CS-RNTI or + - if PUSCH is transmitted with configured grant + - the UE shall use $I_{MCS}$ and Table 5.1.3.1-2 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel. +- elseif *mcs-Table* in *configuredGrantConfig* is set to 'qam64LowSE', + - if PUSCH is scheduled by a PDCCH with CRC scrambled by CS-RNTI or + - if PUSCH is transmitted with configured grant, + - the UE shall use $I_{MCS}$ and Table 5.1.3.1-3 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel. +- elseif for a MsgA PUSCH transmission, + - the UE shall use higher layer parameter *msgA-MCS* for $I_{MCS}$ and Table 5.1.3.1-1 to determine the Target code rate ( $R$ ) used in the physical uplink shared channel. +- elseif the UE requests repetition of PUSCH scheduled by RAR UL grant [10, TS 38.321], when transmitting PUSCH scheduled by RAR UL grant, + - the 2 LSBs of the MCS information field of the RAR UL grant provide a codepoint to determine the MCS index $I_{MCS}$ according to Table 6.1.4.1-3, based on whether or not the higher layer parameter *mcs-Msg3-Repetitions* is configured. The UE shall use the determined $I_{MCS}$ and Table 5.1.3.1-1 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel. + +- elseif the UE requests repetition of PUSCH scheduled by RAR UL grant [10, TS 38.321], when transmitting PUSCH scheduled by DCI format 0\_0 with CRC scrambled by the TC-RNTI, + - the 3 LSBs of the MCS information field of the DCI format 0\_0 with CRC scrambled by the TC-RNTI provide a codepoint to determine the MCS index $I_{MCS}$ according to Table 6.1.4.1-4, based on whether or not the higher layer parameter *mcs-Msg3-Repetitions* is configured. The UE shall use the determined $I_{MCS}$ and Table 5.1.3.1-1 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel. + - else + - the UE shall use $I_{MCS}$ and Table 5.1.3.1-1 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel. +- else +- if *mcs-TableTransformPrecoderDCI-0-2* in *pusch-Config* is set to 'qam256', and PUSCH is scheduled by a PDCCH with DCI format 0\_2 with CRC scrambled by C-RNTI or SP-CSI-RNTI, + - the UE shall use $I_{MCS}$ and Table 5.1.3.1-2 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel. + - elseif the UE is not configured with MCS-C-RNTI, *mcs-TableTransformPrecoderDCI-0-2* in *pusch-Config* is set to 'qam64LowSE', and the PUSCH is scheduled by a PDCCH with DCI format 0\_2 with CRC scrambled by C-RNTI or SP-CSI-RNTI, + - the UE shall use $I_{MCS}$ and Table 6.1.4.1-2 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel. + - elseif *mcs-TableTransformPrecoder* in *pusch-Config* is set to 'qam256', and PUSCH is scheduled by a PDCCH with DCI format 0\_1 or 0\_3 with CRC scrambled by C-RNTI or SP-CSI-RNTI, + - the UE shall use $I_{MCS}$ and Table 5.1.3.1-2 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel. + - elseif the UE is not configured with MCS-C-RNTI, *mcs-TableTransformPrecoder* in *pusch-Config* is set to 'qam64LowSE', and the PUSCH is scheduled by a PDCCH with a DCI format other than DCI format 0\_2 in a UE-specific search space with CRC scrambled by C-RNTI or SP-CSI-RNTI, + - the UE shall use $I_{MCS}$ and Table 6.1.4.1-2 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel. + - elseif the UE is configured with MCS-C-RNTI, and the PUSCH is scheduled by a PDCCH with CRC scrambled by MCS-C-RNTI, + - the UE shall use $I_{MCS}$ and Table 6.1.4.1-2 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel. + - elseif *mcs-TableTransformPrecoder* in *configuredGrantConfig* is set to 'qam256', + - if PUSCH is scheduled by a PDCCH with CRC scrambled by CS-RNTI or + - if PUSCH is transmitted with configured grant, + - the UE shall use $I_{MCS}$ and Table 5.1.3.1-2 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel. + - elseif *mcs-TableTransformPrecoder* in *configuredGrantConfig* is set to 'qam64LowSE', + - if PUSCH is scheduled by a PDCCH with CRC scrambled by CS-RNTI or + - if PUSCH is transmitted with configured grant, + - the UE shall use $I_{MCS}$ and Table 6.1.4.1-2 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel. + +- elseif for a MsgA PUSCH transmission, + - the UE shall use higher layer parameter *MsgA-MCS* for $I_{MCS}$ and Table 6.1.4.1-1 to determine the Target code rate ( $R$ ) used in the physical uplink shared channel. + - the UE shall use $q=2$ for determining modulation order $Q_m$ in Table 6.1.4.1-1. +- elseif the UE requests repetition of PUSCH scheduled by RAR UL grant [10, TS 38.321], when transmitting PUSCH scheduled by RAR UL grant, + - the 2 LSBs of the MCS information field of the RAR UL grant provide a codepoint to determine the MCS index $I_{MCS}$ according to Table 6.1.4.1-3, based on whether or not the higher layer parameter *mcs-Msg3-Repetitions* is configured. The UE shall use the determined $I_{MCS}$ and Table 6.1.4.1-1 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel. +- elseif the UE requests repetition of PUSCH scheduled by RAR UL grant [10, TS 38.321], when transmitting PUSCH scheduled by DCI format 0\_0 with CRC scrambled by the TC-RNTI, + - the 3 LSBs of the MCS information field of the DCI format 0\_0 with CRC scrambled by the TC-RNTI provide a codepoint to determine the MCS index $I_{MCS}$ according to Table 6.1.4.1-4, based on whether or not the higher layer parameter *mcs-Msg3-Repetitions* is configured. The UE shall use the determined $I_{MCS}$ and Table 6.1.4.1-1 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel. +- else + - the UE shall use $I_{MCS}$ and Table 6.1.4.1-1 to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical uplink shared channel. + +end + +For Table 6.1.4.1-1 and Table 6.1.4.1-2, if higher layer parameter *tp-pi2BPSK* is configured, $q = 1$ otherwise $q=2$ . + +**Table 6.1.4.1-1: MCS index table for PUSCH with transform precoding and 64QAM** + +| MCS Index
I_{MCS} | Modulation Order
Q_m | Target code Rate R \times 1024 | Spectral efficiency | +|-------------------------------------------|----------------------------------------------|----------------------------------------------------|----------------------------| +| 0 | q | 240/ q | 0.2344 | +| 1 | q | 314/ q | 0.3066 | +| 2 | 2 | 193 | 0.3770 | +| 3 | 2 | 251 | 0.4902 | +| 4 | 2 | 308 | 0.6016 | +| 5 | 2 | 379 | 0.7402 | +| 6 | 2 | 449 | 0.8770 | +| 7 | 2 | 526 | 1.0273 | +| 8 | 2 | 602 | 1.1758 | +| 9 | 2 | 679 | 1.3262 | +| 10 | 4 | 340 | 1.3281 | +| 11 | 4 | 378 | 1.4766 | +| 12 | 4 | 434 | 1.6953 | +| 13 | 4 | 490 | 1.9141 | +| 14 | 4 | 553 | 2.1602 | +| 15 | 4 | 616 | 2.4063 | +| 16 | 4 | 658 | 2.5703 | +| 17 | 6 | 466 | 2.7305 | +| 18 | 6 | 517 | 3.0293 | +| 19 | 6 | 567 | 3.3223 | +| 20 | 6 | 616 | 3.6094 | +| 21 | 6 | 666 | 3.9023 | +| 22 | 6 | 719 | 4.2129 | +| 23 | 6 | 772 | 4.5234 | +| 24 | 6 | 822 | 4.8164 | +| 25 | 6 | 873 | 5.1152 | +| 26 | 6 | 910 | 5.3320 | +| 27 | 6 | 948 | 5.5547 | +| 28 | q | reserved | | +| 29 | 2 | reserved | | +| 30 | 4 | reserved | | +| 31 | 6 | reserved | | + +**Table 6.1.4.1-2: MCS index table 2 for PUSCH with transform precoding and 64QAM** + +| MCS Index
$I_{MCS}$ | Modulation Order
$Q_m$ | Target code Rate $R \times 1024$ | Spectral efficiency | +|------------------------|---------------------------|----------------------------------|---------------------| +| 0 | $q$ | $60/q$ | 0.0586 | +| 1 | $q$ | $80/q$ | 0.0781 | +| 2 | $q$ | $100/q$ | 0.0977 | +| 3 | $q$ | $128/q$ | 0.1250 | +| 4 | $q$ | $156/q$ | 0.1523 | +| 5 | $q$ | $198/q$ | 0.1934 | +| 6 | 2 | 120 | 0.2344 | +| 7 | 2 | 157 | 0.3066 | +| 8 | 2 | 193 | 0.3770 | +| 9 | 2 | 251 | 0.4902 | +| 10 | 2 | 308 | 0.6016 | +| 11 | 2 | 379 | 0.7402 | +| 12 | 2 | 449 | 0.8770 | +| 13 | 2 | 526 | 1.0273 | +| 14 | 2 | 602 | 1.1758 | +| 15 | 2 | 679 | 1.3262 | +| 16 | 4 | 378 | 1.4766 | +| 17 | 4 | 434 | 1.6953 | +| 18 | 4 | 490 | 1.9141 | +| 19 | 4 | 553 | 2.1602 | +| 20 | 4 | 616 | 2.4063 | +| 21 | 4 | 658 | 2.5703 | +| 22 | 4 | 699 | 2.7305 | +| 23 | 4 | 772 | 3.0156 | +| 24 | 6 | 567 | 3.3223 | +| 25 | 6 | 616 | 3.6094 | +| 26 | 6 | 666 | 3.9023 | +| 27 | 6 | 772 | 4.5234 | +| 28 | $q$ | | reserved | +| 29 | 2 | | reserved | +| 30 | 4 | | reserved | +| 31 | 6 | | reserved | + +**Table 6.1.4.1-3: MCS index $I_{MCS}$ as a function of 2 LSBs of MCS information field in RAR UL grant** + +| mcs-Msg3-Repetitions is configured | | mcs-Msg3-Repetitions is not configured | | +|-------------------------------------------|---------------------------------------------|-----------------------------------------------|-----------| +| Codepoint | $I_{MCS}$ | Codepoint | $I_{MCS}$ | +| 00 | First value of mcs-Msg3-Repetitions | 00 | 0 | +| 01 | Second value of mcs-Msg3-Repetitions | 01 | 1 | +| 10 | Third value of mcs-Msg3-Repetitions | 10 | 2 | +| 11 | Fourth value of mcs-Msg3-Repetitions | 11 | 3 | + +**Table 6.1.4.1-4: MCS index $I_{MCS}$ as a function of 3 LSBs of MCS information field in DCI format 0\_0 with CRC scrambled by the TC-RNTI** + +| mcs-Msg3-Repetitions is configured | | | mcs-Msg3-Repetitions is not configured | | +|--------------------------------------------------|----------------------------------------------|--|------------------------------------------------------|-----------------------------| +| Codepoint | I_{MCS} | | Codepoint | I_{MCS} | +| 000 | First value of mcs-Msg3-Repetitions | | 000 | 0 | +| 001 | Second value of mcs-Msg3-Repetitions | | 001 | 1 | +| 010 | Third value of mcs-Msg3-Repetitions | | 010 | 2 | +| 011 | Fourth value of mcs-Msg3-Repetitions | | 011 | 3 | +| 100 | Fifth value of mcs-Msg3-Repetitions | | 100 | 4 | +| 101 | Sixth value of mcs-Msg3-Repetitions | | 101 | 5 | +| 110 | Seventh value of mcs-Msg3-Repetitions | | 110 | 6 | +| 111 | Eighth value of mcs-Msg3-Repetitions | | 111 | 7 | + +#### 6.1.4.2 Transport block size determination + +For eight antenna ports PUSCH transmission, when the number of PUSCH transmission layers is greater than 4, two codewords are transmitted. + +If the higher layer parameter *maxRank* or *maxMIMO-Layers* in *PUSCH-config* is greater than 4, then one of the two transport blocks is disabled by DCI format 0\_1 if $I_{MCS} = 26$ and if $rv_{id} = 1$ for the corresponding transport block. If both transport blocks are enabled, transport block 1 and 2 are mapped to codeword 0 and 1 respectively. If only one transport block is enabled, then the enabled transport block is always mapped to the first codeword. + +For a PUSCH scheduled by RAR UL grant or + +for a PUSCH scheduled by fallbackRAR UL grant or + +for a PUSCH scheduled by a DCI format 0\_0 with CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, or + +for a PUSCH scheduled by a DCI format 0\_1 or DCI format 0\_2 with CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI, or + +for a PUSCH scheduled by a DCI format 0\_3 with CRC scrambled by C-RNTI, MCS-C-RNTI, or + +for a PUSCH transmission with configured grant, or + +for a MsgA PUSCH transmission, + +if + +- and transform precoding is disabled and Table 5.1.3.1-2 is used, or +- and transform precoding is disabled and a table other than Table 5.1.3.1-2 is used, or +- and transform precoding is enabled, the UE shall first determine the TBS as specified below: + +The UE shall first determine the number of REs ( $N_{RE}$ ) within the slot: + +- A UE first determines the number of REs allocated for PUSCH within a PRB by +- $N_{sc}^{RB}$ , where $N_{sc}^{RB}$ is the number of subcarriers in the frequency domain in a physical resource block, $L$ is the number of symbols of the PUSCH allocation according to Clause 6.1.2.1 for scheduled PUSCH or Clause 6.1.2.3 for configured PUSCH, $N_{DMRS}^{PRB}$ is the number of REs for DM-RS per PRB in the allocated duration including the overhead of the DM-RS CDM groups without data, as described for PUSCH with a configured grant in Clause 6.1.2.3 or as indicated by DCI format 0\_1, 0\_2 or 0\_3 or as described for DCI format 0\_0 in Clause + +6.2.2, and $\alpha$ is the overhead configured by higher layer parameter *xOverhead* in *PUSCH-ServingCellConfig*. If $\alpha$ is not configured (a value from 6, 12, or 18), the $\alpha$ is assumed to be 0. For Msg3 or MsgA PUSCH transmission the $\alpha$ is always set to 0. In case of PUSCH repetition Type B, $\alpha$ is determined assuming a nominal repetition with the duration of $L$ symbols without segmentation. + +- A UE determines the total number of REs allocated for PUSCH as follows + - For TB processing over multiple slots, where $N$ is the total number of allocated PRBs for the UE and $N$ is the number of slots used for TBS determination indicated by *numberOfSlotsTBToMS*. + - Otherwise, . +- Next, proceed with steps 2-4 as defined in Clause 5.1.3.2 +- For a PUSCH scheduled by fallbackRAR UL grant, UE assumes the TB size determined by the UL grant in the fallbackRAR shall be the same as the TB size used in the corresponding MsgA PUSCH transmission. + +else if + +- $\alpha$ and transform precoding is disabled and Table 5.1.3.1-2 is used, or +- $\alpha$ and transform precoding is enabled, +- the TBS is assumed to be as determined from the DCI transported in the latest PDCCH for the same transport block using $\alpha$ . If there is no PDCCH for the same transport block using $\alpha$ , and if the initial PUSCH for the same transport block is scheduled by a RAR UL grant, the TBS shall be determined from the RAR UL grant. If there is no PDCCH for the same transport block using $\alpha$ , and if the initial PUSCH for the same transport block is transmitted with configured grant, + - the TBS shall be determined from *configuredGrantConfig* for a configured grant Type 1 PUSCH. + - the TBS shall be determined from the most recent PDCCH scheduling a configured grant Type 2 PUSCH. + +else + +- the TBS is assumed to be as determined from the DCI transported in the latest PDCCH for the same transport block using $\alpha$ . If there is no PDCCH for the same transport block using $\alpha$ , and if the initial PUSCH for the same transport block is scheduled by a RAR UL grant, the TBS shall be determined from the RAR UL grant. If there is no PDCCH for the same transport block using $\alpha$ , and if the initial PUSCH for the same transport block is transmitted with configured grant, + - the TBS shall be determined from *configuredGrantConfig* for a configured grant Type 1 PUSCH. + - the TBS shall be determined from the most recent PDCCH scheduling a configured grant Type 2 PUSCH. + +### 6.1.5 Code block group based PUSCH transmission + +If a UE is configured to transmit code block group (CBG) based transmissions by receiving the higher layer parameter *codeBlockGroupTransmission* in *PUSCH-ServingCellConfig* on a serving cell in a PUCCH group, the UE does not expect to be configured with higher layer parameter *ScheduledCell-ListDCI-0-3* on any serving cell within the PUCCH group. + +#### 6.1.5.1 UE procedure for grouping of code blocks to code block groups + +If a UE is configured to transmit code block group (CBG) based transmissions by receiving the higher layer parameter *codeBlockGroupTransmission* in *PUSCH-ServingCellConfig*, the UE shall determine the number of CBGs for a transport block transmission as + +, + +where $N$ is the maximum number of CBGs per transport block as configured by *maxCodeBlockGroupsPerTransportBlock* in *PUSCH-ServingCellConfig*, and $C$ is the number of code blocks in the transport block according to the procedure defined in Clause 6.2.3 of [5, TS 38.212]. + +Define $\alpha$ , $\beta$ , and $\gamma$ . + +If , CBG *m* , consists of code blocks with indices . CBG *m* , consists of code blocks with indices . + +#### 6.1.5.2 UE procedure for transmitting code block group based transmissions + +If a UE is configured to transmit code block group-based transmissions by receiving the higher layer parameter *codeBlockGroupTransmission* in *PUSCH-ServingCellConfig*, + +- For an initial transmission of a TB as indicated by the '*New Data Indicator*' field of the scheduling DCI, the UE may expect that the *CBGTI* field indicates all the CBGs of the TB are to be transmitted, and the UE shall include all the code block groups of the TB. +- For a retransmission of a TB as indicated by the '*New Data Indicator*' field of the scheduling DCI, the UE shall include only the CBGs indicated by the *CBGTI* field of the scheduling DCI. + +A bit value of '0' in the *CBGTI* field indicates that the corresponding CBG is not to be transmitted and '1' indicates that it is to be transmitted. The order of *CBGTI* field bits is such that the CBGs are mapped in order from CBG#0 onwards starting from the MSB. + +### 6.1.6 Uplink switching + +The UE may omit uplink transmission during the uplink switching gap if the conditions defined in this clause are met and the UE is configured with *uplinkTxSwitching*. The switching gap is indicated by UE capability *uplinkTxSwitchingPeriod2T2T* if *uplinkTxSwitching-2T-Mode* is configured, and *uplinkTxSwitchingPeriod* otherwise in clauses 6.1.6.1, 6.1.6.2.0, 6.1.6.3, and is determined based on UE capability *uplinkTxSwitchingPeriodForBandPair* in clause 6.1.6.2.2 for uplink switching with 3 or 4 uplink bands: + +- If a UE indicated a capability for uplink switching with *BandCombination-UplinkTxSwitch* for a band combination, and if it is for that band combination + - Configured with a MCG using E-UTRA radio access and with a SCG using NR radio access (EN-DC), or + - Configured with uplink carrier aggregation, or + - Configured in a serving cell with two uplink carriers with higher layer parameter *supplementaryUplink*. + +The conditions under which the switching gap may be present are defined for each of the cases in clauses 6.1.6.1, 6.1.6.2, and 6.1.6.3 respectively. + +If an uplink switching is triggered for an uplink transmission starting at *T*0, after *T*0-*T*offset, the UE is not expected to cancel the uplink switching, or to trigger any other new uplink switching occurring before *T*0 for any other uplink transmission that is scheduled after *T*0-*T*offset, where *T*offset is the UE processing procedure time defined for the uplink transmission triggering the switch given in clause 5.3, clause 5.4, clause 6.2.1, clause 6.4 and in clause 9 of [6, TS 38.213]. + +The UE does not expect to perform more than one uplink switching in a slot with $\mu_{UL} = \max(\mu_{UL,1}, \mu_{UL,2})$ , where the $\mu_{UL,1}$ corresponds to the subcarrier spacing of the active UL BWP of one uplink carrier before the switching gap and the $\mu_{UL,2}$ corresponds to the subcarrier spacing of the active UL BWP of the other uplink carrier after the switching gap. + +For uplink switching configured with 3 or 4 uplink bands + +- If two contiguous intra-band uplink carriers are configured to a UE, the UE may assume that the active UL BWPs of the two carriers are configured with the same subcarrier spacing. +- The UE does not expect to perform more than one uplink switching in a reference slot with $\mu_{UL}$ , where the $\mu_{UL}$ corresponds to the maximum subcarrier spacing of the active UL BWPs of all the configured uplink carriers. +- If 500 µs is determined by the UE capability *uplinkTxSwitchingMinimumSeparationTime*, when within any two consecutive reference slots corresponding to numerology $\mu_{UL}$ , + - the UE first performs one uplink switch and later performs another uplink switch and + - at least three bands are involved in the transmissions before the first switch, between the first switch and the second switch, and after the second switch, + +the separation time between the start of all transmission(s) after the first switch and the start of all transmission(s) after the second switch is not expected to be less than 500 $\mu$ s. If other than 500 $\mu$ s is determined by the UE capability *uplinkTxSwitchingMinimumSeparationTime*, no additional restrictions apply. + +- If an uplink switching is triggered for uplink transmission(s) with a gap between the start of the first uplink transmission(s) and the end of the last preceding uplink transmission(s) that is smaller than the determined switching gap, the UE determines the band of the switching period location, defined in [8, TS 38.101-1] based on the priority of the bands configured by *uplinkTxSwitchingBandList*. Among the bands either in switch-from or switch-to bands but not both, the switch is located on either, + - the switch-from band(s) if the highest priority band is a switch-to band, or + - the switch-to band(s) if the highest priority band is a switch-from band. + +#### 6.1.6.1 Uplink switching for EN-DC + +For a UE indicating a capability for uplink switching with *BandCombination-UplinkTxSwitch* for a band combination, and if it is for that band combination configured with a MCG using E-UTRA radio access and with a SCG using NR radio access (EN-DC), if the UE is configured with uplink switching with parameter *uplinkTxSwitching*, + +- for the UE configured with *switchedUL* by the parameter *uplinkTxSwitchingOption*, when the UE is to transmit in the uplink based on DCI(s) received before or based on a higher layer configuration(s): + - when the UE is to transmit an NR uplink that takes place after an E-UTRA uplink on another uplink carrier then the UE is not expected to transmit for the duration of $\Delta$ on any of the two carriers. + - when the UE is to transmit an E-UTRA uplink that takes place after an NR uplink on another uplink carrier then the UE is not expected to transmit for the duration of $\Delta$ on any of the two carriers. + - the UE is not expected to transmit simultaneously on the NR uplink and the E-UTRA uplink. If the UE is scheduled or configured to transmit any NR uplink transmission overlapping with an E-UTRA uplink transmission, the NR uplink transmission is dropped, +- for the UE configured with *uplinkTxSwitchingOption* set to 'dualUL', when the UE is to transmit in the uplink based on DCI(s) received before or based on a higher layer configuration(s): + - when the UE is to transmit an NR two-port uplink that takes place after an E-UTRA uplink on another uplink carrier then the UE is not expected to transmit for the duration of $\Delta$ on any of the two carriers. + - when the UE is to transmit an E-UTRA uplink that takes place after an NR two-port uplink on another uplink carrier then the UE is not expected to transmit for the duration of $\Delta$ on any of the two carriers. + - the UE is not expected to transmit simultaneously a two-port transmission on the NR uplink and the E-UTRA uplink. +- in all other cases the UE is expected to transmit normally all uplink transmissions without interruptions. +- when the UE is configured with *tdm-PatternConfig* or by *tdm-PatternConfig2* + - for the E-UTRA subframes designated as uplink by the configuration, the UE assumes the operation state in which one-port E-UTRA uplink can be transmitted. + - for the E-UTRA subframes other than the ones designated as uplink by the configuration, the UE assumes the operation state in which two-port NR uplink can be transmitted. + +#### 6.1.6.2 Uplink switching for carrier aggregation + +##### 6.1.6.2.0 Uplink switching with two uplink bands + +For a UE indicating a capability for uplink switching with *BandCombination-UplinkTxSwitch* or *uplinkTxSwitchingPeriod2T2T* for a band combination, and if it is for that band combination configured with uplink carrier aggregation: + +- If the UE is configured with uplink switching with parameter *uplinkTxSwitching*, when the UE is to transmit in the uplink based on DCI(s) received before or based on a higher layer configuration(s): + +- When the UE is to transmit a 2-port transmission on one uplink carrier on one band and if the preceding uplink transmission is a 1-port transmission on another uplink carrier on another band, then the UE is not expected to transmit for the duration of $N_{Tx1-Tx2}$ on any of the carriers. +- When the UE is to transmit a 1-port transmission on one uplink carrier on one band and if the preceding uplink transmission is a 2-port transmission on another uplink carrier on another band, then the UE is not expected to transmit for the duration of $N_{Tx1-Tx2}$ on any of the carriers. +- For the UE configured with *uplinkTxSwitchingOption* set to 'switchedUL', when the UE is to transmit a 1-port transmission on one uplink carrier on one band and if the preceding uplink transmission was a 1-port transmission on another uplink carrier on another band, then the UE is not expected to transmit for the duration of $N_{Tx1-Tx2}$ on any of the carriers. +- For the UE configured with *uplinkTxSwitchingOption* set to 'dualUL', when the UE is to transmit a 2-port transmission on one uplink carrier on one band and if the preceding uplink transmission was a 1-port transmission on a carrier on the same band and the UE is under the operation state in which 2-port transmission cannot be supported in the same band, then the UE is not expected to transmit for the duration of $N_{Tx1-Tx2}$ on any of the carriers. +- For the UE configured with *uplinkTxSwitchingOption* set to 'dualUL', when the UE is to transmit a 1-port transmission on one uplink carrier on one band and if the preceding uplink transmission was a 1-port transmission on another uplink carrier on another band and the UE is under the operation state in which 2-port transmission can be supported in the same band, then the UE is not expected to transmit for the duration of $N_{Tx1-Tx2}$ on any of the carriers. +- For the UE configured with *uplinkTxSwitchingOption* set to 'dualUL', if the UE is configured with *uplinkTxSwitching-DualUL-TxState* set to 'oneT', when the UE is under the operation state in which 2-port transmission can be supported on one carrier on one band followed by no transmission on any carrier on the same band and 1-port transmission on the other carrier on another band the UE shall consider this as if 1-port transmission was transmitted on both uplinks, otherwise the UE shall consider this as if 2-port transmission took place on the transmitting carrier. +- If *uplinkTxSwitching-2T-Mode* is configured, when the UE is to transmit a 2-port transmission on one uplink carrier on one band and if the preceding uplink transmission is a 2-port transmission on another uplink carrier on another band, then the UE is not expected to transmit for the duration of $N_{Tx1-Tx2}$ on any of the carriers. +- The UE is not expected to be scheduled or configured with uplink transmissions that result in simultaneous transmission on two antenna ports on one uplink carrier on one band, and any transmission on another uplink carrier on another band. +- In all other cases the UE is expected to transmit normally all uplink transmissions without interruptions. + +##### 6.1.6.2.1 void + +##### 6.1.6.2.2 Uplink switching with 3 or 4 uplink bands + +For a UE indicating a capability for uplink switching with *BandCombination-UplinkTxSwitch* for a band combination, and if it is for that band combination configured with uplink carrier aggregation with 3 or 4 bands, the behaviour in subclause 6.1.6.2.0 applies when the two bands involved in the uplink switching belong to different uplink serving cells, and the behavior in subclause 6.1.6.3 applies when the two bands involved in the uplink switching belong to one uplink serving cell, with the following exceptions: + +- If more than two bands are involved in the determination of one uplink switching and if on any two of the bands the UE is configured with *switchingOptionConfigForBandPair* set to 'dualUL', +- When the UE is to transmit a 2-port transmission on one uplink carrier on the 1st band and if the preceding uplink transmission was a 1-port transmission on a carrier on the 2nd and/or 3rd band and the UE is under the operation state in which 1-port transmission can be supported in the 2nd and 3rd band, then the UE is not expected to transmit for the duration of $N_{Tx1-Tx2}$ on any of the carriers, where $N_{Tx1-Tx2}$ is the switching gap defined in [8, TS 38.101-1]. +- When the UE is to transmit a 1-port transmission on one uplink carrier on the 1st band and the 2nd band, and if the preceding uplink transmission was a 1-port or 2-port transmission on a carrier on the 3rd band and the UE is under the operation state in which 2-port transmission can be supported on the 3rd band, then the UE is not + +expected to transmit for the duration of $N_{Tx1-Tx2}$ on any of the carriers, where $N_{Tx1-Tx2}$ is the switching gap defined in [8, TS3 8.101-1]. + +- When the UE is to transmit a 1-port transmission on one uplink carrier on the 1st band and the 2nd band, and if the preceding uplink transmission was a 1-port transmission on a carrier on the 1st band and/or the 3rd band and the UE is under the operation state in which 1-port transmission can be supported in the 1st and 3rd band, if UE indicates *maintainedUL-Trans* for the 1st band for band pair {the 2nd band, the 3rd band} then the UE is not expected to transmit for the duration of $N_{Tx1-Tx2}$ on any of the carriers on the 2nd band and the 3rd band, otherwise then the UE is not expected to transmit for the duration of $N_{Tx1-Tx2}$ on any of the carriers , where $N_{Tx1-Tx2}$ is the switching gap defined in [8, TS 38.101-1]. +- When the UE is to transmit a 1-port transmission on one uplink carrier on the 1st band and the 2nd band, and if the preceding uplink transmission was a 1-port transmission on a carrier on the 3rd band and/or the 4th band and the UE is under the operation state in which 1-port transmission can be supported in the 3rd and 4th band, then the UE is not expected to transmit for the duration of $N_{Tx1-Tx2}$ on any of the carriers, where $N_{Tx1-Tx2}$ is the switching gap defined in [8, TS 38.101-1]. +- The UE is not expected to be scheduled or configured to transmit on more than two uplink bands at any given time. +- If the UE indicated a *uplinkTxSwitchingOptionForBandPair* set to 'DualUL', or 'Both' for a band pair in the band combination, the UE can be configured with *switchingOptionConfigForBandPair* set to 'dualUL' for that band pair. +- If the UE indicated a *uplinkTxSwitchingOptionForBandPair* set to 'SwitchedUL', or 'Both' for a band pair in the band combination, the UE can be configured with *switchingOptionConfigForBandPair* set to 'switchedUL' for that band pair. +- If the UE is configured with *uplinkTxSwitching-DualUL-TxState* set to 'oneT', when the UE is under the operation state in which 1-port transmission can be supported on one carrier on the 1st band and the 2nd band followed by no transmission on any carrier on these two bands and 1-port transmission on the other carrier on the 3rd band the UE shall consider this as if 1-port transmission was transmitted on the 3rd band and the band associated with the 3rd band as configured by *associatedBand*, otherwise the UE shall consider this as if 2-port transmission took place on the transmitting carrier. Even if all cells in a band are deactivated, that does not invalidate the associated band configuration that is indicating the band as associated band for the other band(s) for the definition in clause 6.1.6. +- If the UE is configured with *uplinkTxSwitching-DualUL-TxState* set to 'oneT', if a band in the band combination is not configured as dualUL for any band pair it belongs to, when the UE is to transmit a 1-port transmission on a carrier on the band the UE shall consider this as if 2-port transmission took place on the transmitting carrier. + +#### 6.1.6.3 Uplink switching with two uplink bands for supplementary uplink + +For a UE indicating a capability for uplink switching with *BandCombination-UplinkTxSwitch* for a band combination, and if it is for that band combination configured in a serving cell with two uplink carriers with higher layer parameter *supplementaryUplink*: + +- If the UE is configured with uplink switching with parameter *uplinkTxSwitching*, + - If the UE is to transmit any uplink channel or signal on a different uplink on a different band from the preceding transmission occasion based on DCI(s) received before or based on a higher layer configuration(s), then the UE assumes that an uplink switching is triggered in a duration of switching gap , where $T_{start}$ is the start time of the first symbol of the transmission occasion of the uplink channel or signal and $T_{end}$ is the preparation procedure time of the transmission occasion of the uplink channel or signal given in clause 5.3, clause 5.4, clause 6.2.1, clause 6.4 and in clause 9 of [6, TS 38.213], respectively. During the switching gap , the UE is not expected to transmit on any of the two uplinks. +- In all other cases the UE is expected to transmit normally all uplink transmissions without interruptions. + +### 6.1.7 UE procedure for determining time domain windows for bundling DM-RS + +For PUSCH transmissions of PUSCH repetition Type A scheduled by DCI format 0\_1 or 0\_2, PUSCH repetition Type A with a configured grant, PUSCH repetition Type B and TB processing over multiple slots, when *pusch-DMRS-Bundling* is enabled, and for PUCCH transmissions of PUCCH repetition, when *PUCCH-DMRS-Bundling* is enabled, the UE determines one or multiple nominal TDWs, as follows: + +- For PUSCH transmissions of repetition Type A, PUSCH repetition Type B and TB processing over multiple slots, the duration of each nominal TDW except the last nominal TDW, in number of consecutive slots, is: + - Given by *pusch-TimeDomainWindowLength*, if configured. + - Computed as $\min(\maxDurationDMRS-Bundling, M)$ , if *pusch-TimeDomainWindowLength* is not configured, where *maxDurationDMRS-Bundling* is maximum duration for a nominal TDW subject to UE capability [13, TS 38.306], *M* is the time duration in consecutive slots of PUSCH transmissions, and where: + - For PUSCH transmissions of PUSCH repetition Type A, *N*=1 and *K* is the number of repetitions, as defined in Clause 6.1.2.1 or in Clause 6.1.2.3. + - For PUSCH transmissions of PUSCH repetition Type B, *N*=1 and *K* is the number of nominal repetitions, as defined in Clause 6.1.2.1 or in Clause 6.1.2.3. + - For PUSCH transmissions of TB processing over multiple slots, *N* is the number of slots used for TBS determination and *K* is the number of repetitions of the number of slots *N* used for TBS determination, as defined in Clause 6.1.2.1 or in Clause 6.1.2.3. +- For PUCCH transmissions of PUCCH repetition, the duration of each nominal TDW except the last nominal TDW, in number of consecutive slots, is: + - Given by *pucch-TimeDomainWindowLength*, if configured. + - Computed as $\min(\maxDurationDMRS-Bundling, M)$ , if *pucch-TimeDomainWindowLength* is not configured, where *maxDurationDMRS-Bundling* is maximum duration for a nominal TDW subject to UE capability [13, TS 38.306], *M* is the time duration in consecutive slots from the first slot determined for PUCCH transmissions of PUCCH repetition to the last slot determined for PUCCH transmissions of PUCCH repetition according to clause 9.2.6 of [6, TS 38.213]. +- For PUSCH transmission of a PUSCH repetition Type A scheduled by DCI format 0\_1 or 0\_2 and PUSCH repetition Type A with a configured grant, when *AvailableSlotCounting* is enabled, and for TB processing over multiple slots: + - The start of the first nominal TDW is the first slot determined for the first PUSCH transmission. + - The end of the last nominal TDW is the last slot determined for the last PUSCH transmission. + - The start of any other nominal TDWs is the first slot determined for PUSCH transmission after the last slot determined for PUSCH transmission of a previous nominal TDW. +- For PUSCH transmissions of a PUSCH repetition type A scheduled by DCI format 0\_1 or 0\_2 and PUSCH repetition Type A with a configured grant, when the UE is not configured with *AvailableSlotCounting* or when *AvailableSlotCounting* is disabled, and for PUSCH repetition type B: + - The start of the first nominal TDW is the first slot for the first PUSCH transmission. + - The end of the last nominal TDW is the last slot for the last PUSCH transmission. + - The start of any other nominal TDWs is the first slot after the last slot of a previous nominal TDW. +- For PUCCH transmissions of a PUCCH repetition: + - The start of the first nominal TDW is the first slot determined for the first PUCCH transmission. + - The end of the last nominal TDW is the last slot determined for the last PUCCH transmission. + +- The start of any other nominal TDWs is the first slot determined for PUCCH transmission after the last slot determined for PUCCH transmission of a previous nominal TDW. + +For PUSCH transmissions of a PUSCH repetition Type A scheduled by DCI format 0\_1 or 0\_2, PUSCH repetition Type A with a configured grant, PUSCH repetition Type B and TB processing over multiple slots, a nominal TDW consists of one or multiple actual TDWs. The UE determines the actual TDWs as follows: + +- The start of the first actual TDW is the first symbol of the first PUSCH transmission in a slot for PUSCH transmission of PUSCH repetition type A scheduled by DCI format 0\_1 or 0\_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots within the nominal TDW. +- The end of an actual TDW is + - The last symbol of the last PUSCH transmission in a slot for PUSCH transmission of PUSCH repetition type A scheduled by DCI format 0\_1 or 0\_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots within the nominal TDW, if the actual TDW reaches the end of the last PUSCH transmission within the nominal TDW. + - The last symbol of a PUSCH transmission before the event, if an event occurs which causes power consistency and phase continuity not to be maintained across PUSCH transmissions of PUSCH repetition type A scheduled by DCI format 0\_1 or 0\_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots within the nominal TDW, and the PUSCH transmission is in a slot for PUSCH transmission of PUSCH repetition type A scheduled by DCI format 0\_1 or 0\_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots. +- When *pusch-WindowRestart* is enabled, the start of a new actual TDW is the first symbol of the PUSCH transmission after the event which causes power consistency and phase continuity not to be maintained across PUSCH transmissions of PUSCH repetition type A scheduled by DCI format 0\_1 or 0\_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots within the nominal TDW, and the PUSCH transmission is in a slot for PUSCH transmission of PUSCH repetition type A scheduled by DCI format 0\_1 or 0\_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots. + +For PUCCH transmissions of PUCCH repetition, a nominal TDW consists of one or multiple actual TDWs. The UE determines the actual TDWs as follows: + +- The start of the first actual TDW is the first symbol of the first PUCCH transmission in a slot determined for PUCCH transmission within the nominal TDW. +- The end of an actual TDW is + - The last symbol of the last PUCCH transmission in a slot determined for transmission of the PUCCH within the nominal TDW, if the actual TDW reaches the end of the last PUCCH transmission within the nominal TDW. + - The last symbol of a PUCCH transmission before the event, if an event occurs which causes power consistency and phase continuity not to be maintained across PUCCH transmissions of PUCCH repetition within the nominal TDW, and the PUCCH transmission is in a slot determined for transmission of the PUCCH. +- When *pucch-WindowRestart* is enabled, the start of a new actual TDW is the first symbol of the PUCCH transmission after the event which causes power consistency and phase continuity not to be maintained across PUCCH transmissions of PUCCH repetition within the nominal TDW, and the PUCCH transmission is in a slot determined for transmission of the PUCCH. + +Events which cause power consistency and phase continuity not to be maintained across PUSCH transmissions of PUSCH repetition type A scheduled by DCI format 0\_1 or 0\_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots, or PUCCH transmissions of PUCCH repetition, within the nominal TDW, are: + +- A downlink slot or downlink reception or downlink monitoring based on *tdd-UL-DL-ConfigurationCommon* and *tdd-UL-DL-ConfigurationDedicated* for unpaired spectrum. + +- The gap between any two consecutive PUSCH transmissions, or the gap between any two consecutive PUCCH transmissions, exceeds 13 symbols for normal cyclic prefix or exceeds 11 symbols for extended cyclic prefix. +- The gap between any two consecutive PUSCH transmissions, or the gap between any two consecutive PUCCH transmissions, does not exceed 13 symbols but other uplink transmissions are scheduled between the two consecutive PUSCH transmissions or the two consecutive PUCCH transmissions. +- For PUSCH transmissions of PUSCH repetition type A, or PUSCH repetition type B or TB processing over multiple slots, a dropping or cancellation of a PUSCH transmission according to clause 9, clause 11.1 and clause 11.2A of [6, TS 38.213]. +- For PUCCH transmissions of PUCCH repetition, a dropping or cancellation of a PUCCH transmission according to clause 9, clause 9.2.6 and clause 11.1 of [6, TS 38.213]. +- For any two consecutive PUSCH transmissions of PUSCH repetition type A, or PUSCH repetition type B, and when two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook' or 'noncodebook', a different SRS resource set association is used for the two PUSCH transmissions of PUSCH repetition type A, or PUSCH repetition type B, according to Clause 6.1.2.1. +- For any two consecutive PUCCH transmissions of PUCCH repetition, and when a PUCCH resource used for repetitions of a PUCCH transmission by a UE includes first and second spatial relations or first and second sets of power control parameters, as described in [10, TS 38.321] and in clause 7.2.1 of [6, TS 38.213], different spatial relations or different power control parameters are used for the two PUCCH transmissions of PUCCH repetition, according to Clause 9.2.6 of [6, TS 38.213]. +- Uplink timing adjustment in response to a timing advance command according to clause 4.2 of [6, TS 38.213]. +- Frequency hopping. +- For reduced capability half-duplex UEs, + - a dropping or cancellation of a PUSCH or PUCCH transmission according to clause 17.2 of [6, TS 38.213] or + - an overlapping of the gap between two consecutive PUSCH or two consecutive PUCCH transmissions and any symbol of downlink reception or downlink monitoring + +The UE shall maintain power consistency and phase continuity within an actual TDW, across PUSCH transmissions of PUSCH repetition Type A scheduled by DCI format 0\_1 or 0\_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots, or across PUCCH transmissions of PUCCH repetition, in case the actual TDW is created in response to frequency hopping, or in response to the use of a different SRS resource set association for the two PUSCH transmissions of PUSCH repetition type A, or PUSCH repetition type B, or in response to the use of different spatial relations or different power control parameters for the two PUCCH transmissions of PUCCH repetition, or in response to any event not triggered by DCI or MAC-CE. The UE maintains power consistency and phase continuity within an actual TDW, across PUSCH transmissions of PUSCH repetition Type A scheduled by DCI format 0\_1 or 0\_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots, or across PUCCH transmissions of PUCCH repetition, in case the actual TDW is created in response to an event triggered by DCI other than frequency hopping or the use of a different SRS resource set association for the two PUSCH transmissions of PUSCH repetition type A, or PUSCH repetition type B, or the use of different spatial relations or different power control parameters for the two PUCCH transmissions of PUCCH repetition, or in response to an event triggered by MAC-CE, subject to UE capability. of *dmrs-BundlingRestart* [13, TS 38.306] and when *pusch-WindowRestart* or *pucch-WindowRestart* is enabled. + +## 6.2 UE reference signal (RS) procedure + +### 6.2.1 UE sounding procedure + +The UE may be configured with one or more Sounding Reference Signal (SRS) resource sets as configured by the higher layer parameter *SRS-ResourceSet* or *SRS-PosResourceSet*. For each SRS resource set configured by *SRS-ResourceSet*, a UE may be configured with SRS resources (higher layer parameter *SRS-Resource*), where the maximum value of K is indicated by UE capability [13, 38.306]. When SRS resource set is configured with the higher layer parameter *SRS-PosResourceSet*, a UE may be configured with $K \geq 1$ SRS resources (higher layer parameter *SRS-PosResource*), where the maximum value of K is 16. The SRS resource set applicability is configured by the higher + +layer parameter *usage* in *SRS-ResourceSet*. When the higher layer parameter *usage* is set to 'beamManagement', only one SRS resource in each of multiple SRS resource sets may be transmitted at a given time instant, but the SRS resources in different SRS resource sets with the same time domain behaviour in the same BWP may be transmitted simultaneously. + +During non-active periods of cell DRX, the UE configured with cell DRX is not expected to transmit the periodic SRS, or semi-persistent SRS for channel acquisition. SRS for positioning is not impacted by cell DRX operation. + +For the SRS resource set(s) configured in *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* set to 'antennaSwitching' or 'beamManagement', the UE expects the same SRS resource set(s) with the same *usage* being configured in *srs-ResourceSetToAddModList*. + +When the UE is configured *dl-OrJointTCI-StateList* or *ul-TCI-StateList*, the UE can assume that SRS resource(s) in any SRS resource set, except SRS resource set for positioning and an SRS resource set configured with *followUnifiedTCI-StateSRS*, can be configured with *TCI-State* or *TCI-UL-State* or updated as described in clause 6.1.3.59 or 6.1.3.60 of [10, TS 38.321]. The reference RS in the *TCI-State* can be a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *repetition*, or a CSI-RS resource in an *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info*. The reference RS in the *TCI-UL-State(s)* can be a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *repetition*, a CSI-RS resource in an *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info*, an SRS resource with the higher layer parameter *usage* set to 'beamManagement', or SS/PBCH block associated with the same or different PCI from the PCI of the serving cell. + +If an SRS resource set, except an SRS resource set for positioning, is configured with *followUnifiedTCI-StateSRS*, the UE shall transmit the target SRS resource(s) within the SRS resource set according to the spatial relation, if applicable, with a reference to the RS used for determining UL TX spatial filter. The RS is determined based on an RS configured with *qcl-Type* set to 'typeD' in *QCL-Info* of the indicated *TCI-State* or an RS in the indicated *TCI-UL-State*. The reference RS in the indicated *TCI-State* can be a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *repetition*, or a CSI-RS resource in an *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info*. The reference RS in the indicated *TCI-UL-State* can be a CSI-RS resource in a *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *repetition*, a CSI-RS resource in an *NZP-CSI-RS-ResourceSet* configured with higher layer parameter *trs-Info*, an SRS resource with the higher layer parameter *usage* set to 'beamManagement', or SS/PBCH block associated with the same or different PCI from the PCI of the serving cell. + +When the UE is configured *dl-OrJointTCI-StateList* or *TCI-UL-State* and is having two indicated TCI-States or TCI-UL-States, and if the UE is configured with *[[followUnifiedTCI-StateSRS]]* to, a periodic, semi-persistent or aperiodic SRS resource set with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook', 'nonCodebook' or 'antennaSwitching' or to an aperiodic SRS resource set with higher layer parameter *usage* in *SRS-ResourceSet* set to 'beamManagement' + +- The UE may be configured by higher layer parameter *applyIndicatedTCIState* to the SRS resource set to indicate whether the UE shall apply the first or the second indicated *TCI-State* or *TCI-UL-State* to the SRS resource set. +- When a UE is configured by higher layer parameter *PDCCH-Config* that contains two different values of *coresetPoolIndex* in *ControlResourceSet*, the first and second indicated *TCI-States* or *TCI-UL-States* correspond to the indicated *TCI-States* or *TCI-UL-States* specific to *coresetPoolIndex* value 0 and value 1, respectively. +- When a UE is configured by higher layer parameter *PDCCH-Config* that contains two different values of *coresetPoolIndex* in *ControlResourceSet*, and the aperiodic SRS resource set which is not configured with higher layer parameter *applyIndicatedTCIState* and the aperiodic SRS resource set is triggered by PDCCH on a CORESET associated with a *coresetPoolIndex* value, the UE shall apply the indicated *TCI-State* or *TCI-UL-State* specific to the *coresetPoolIndex* value to the aperiodic SRS resource set. +- When two SRS resource sets with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook' or 'nonCodebook' are configured, the UE does not expect that the first indicated *TCI-State* or *TCI-UL-State* is applied to the second SRS resource set and that the second indicated *TCI-State* or *TCI-UL-State* is applied to the first SRS resource set. + +For aperiodic SRS at least one state of the DCI field is used to select at least one out of the configured SRS resource set(s). + +The following SRS parameters are semi-statically configurable by higher layer parameter *SRS-Resource* or *SRS-PosResource*. + +- *srs-ResourceId* or *SRS-PosResourceId* determines SRS resource configuration identity. +- Number of SRS ports, as defined by the higher layer parameter *nrofSRS-Ports* and described in clause 6.4.1.4 of [4, TS 38.211]. If not configured, *nrofSRS-Ports* is 1. +- Time domain behaviour of SRS resource configuration as indicated by the higher layer parameter *resourceType*, which may be periodic, semi-persistent, aperiodic SRS transmission as defined in clause 6.4.1.4 of [4, TS 38.211]. +- Slot level periodicity and slot level offset as defined by the higher layer parameters *periodicityAndOffset-p* or *periodicityAndOffset-sp* for an SRS resource of type periodic or semi-persistent. The UE is not expected to be configured with SRS resources in the same SRS resource set *SRS-ResourceSet* or *SRS-PosResourceSet* with different slot level periodicities. For an *SRS-ResourceSet* configured with higher layer parameter *resourceType* set to 'aperiodic', a slot level offset is defined by the higher layer parameter *slotOffset*. For an *SRS-ResourceSet* configured with higher layer parameter *resourceType* set to 'aperiodic', a list of up to four different available slot offset values from the reference slot $n + k$ to the slot where the aperiodic SRS resource set is transmitted where $n$ is the slot with triggering DCI and $k$ is *slotOffset*, can be configured by the higher layer parameter *availableSlotOffsetList*. The parameter *availableSlotOffsetList* can be configured up to 4 different values. For an *SRS-PosResourceSet* configured with higher layer parameter *resourceType* set to 'aperiodic', the slot level offset is defined by the higher layer parameter *slotOffset* for each SRS resource. +- Support of time division mapping subsets of ports of the SRS resource into $S$ symbols ( $S=2$ ), as defined by the higher layer parameter [*tdm*], where the SRS ports are evenly distributed in two consecutive symbols over the symbols in a slot for the SRS resource according to clause 6.4.1.4.2 in [4, TS 38.211]. This applies when the SRS resource set is configured with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook', or 'antennaSwitching', and *nrofSRS-Ports* is set to 'n8'. +- Comb offset hopping pattern with repetition, as defined by the higher layer parameter [*combOffsetHoppingWithRepetition*], where the parameter can be set to either '[per-symbol]' or '[per-R-repetition]' subject to UE capability. When the parameter is set to '[per-symbol]', the comb offset hopping pattern is determined by the symbol index, and the comb offset hopping pattern is determined by the symbol index of the first symbol of the repetition when the parameter is set to '[per-R-repetition]' according to clause 6.4.1.4.3 in [4, TS 38.211]. +- Number of OFDM symbols in the SRS resource, starting OFDM symbol of the SRS resource within a slot including repetition factor $R$ as defined by the higher layer parameter *resourceMapping* and described in clause 6.4.1.4 of [4, TS 38.211]. If $R$ is not configured for positioning SRS, then $R$ is equal to the number of OFDM symbols in the SRS resource. +- SRS bandwidth , as defined by the higher layer parameter *freqHopping* and described in clause 6.4.1.4 of [4, TS 38.211]. If not configured, then= 0. +- Frequency hopping bandwidth , as defined by the higher layer parameter *freqHopping* and described in clause 6.4.1.4 of [4, TS 38.211]. If not configured, then = 0. +- Defining partial frequency sounding factor and start RB index for partial frequency sounding as defined by the higher layer parameters *FreqScalingFactor* $P_F$ and *StartRBIndex* $k_F$ , respectively, and described in Clause 6.4.1.4 of [4, TS 38.211]. If not configured, then $P_F = 1$ and $k_F = 0$ . +- Defining start RB index hopping for partial frequency sounding in different SRS frequency hopping periods for aperiodic/periodic/semi-persistent SRS based on the hopping pattern $k_{hop}$ as described in clause 6.4.1.4.3 in [4, TS 38.211]. If not configured, then start RB hopping is not enabled and $k_{hop}$ is fixed to be 0 for all SRS symbols. +- Defining frequency domain position and configurable shift, as defined by the higher layer parameters *freqDomainPosition* and *freqDomainShift*, respectively, and described in clause 6.4.1.4 of [4, TS 38.211]. If *freqDomainPosition* is not configured, *freqDomainPosition* is zero. +- Cyclic shift, as defined by the higher layer parameter *cyclicShift-n2*, *cyclicShift-n4*, or *cyclicShift-n8* for transmission comb value 2, 4 or 8, and described in clause 6.4.1.4 of [4, TS 38.211]. When cyclic shift hopping is configured by the higher layer parameter [*cyclicShiftHopping*] for an SRS resource in an SRS resource set with the usage configured as 'antennaSwitching' or 'codebook', subject to UE capabilities, cyclic shift is updated at every symbol as described in [clause 6.4.1.4 of [4, TS 38.211]]. For the cyclic shift hopping, a UE can be configured with a subset of cyclic shifts by the higher layer parameter [*cyclicShiftHoppingSubset*], where the cyclic shift hopping is performed only across the cyclic shifts configured in the subset. For the cyclic shift + +hopping, a UE can be configured with finer hopping granularity by the higher layer parameter *[hoppingFinerGranularity]*. The UE is not expecting that *[hoppingFinerGranularity]* and *[cyclicShiftHoppingSubset]* are configured simultaneously for an SRS resource. The UE is not expecting that the cyclic shift hopping and the higher layer parameter *[tdm]* are configured simultaneously for an SRS resource. + +- Transmission comb value, as defined by the higher layer parameter *transmissionComb* described in clause 6.4.1.4 of [4, TS 38.211]. +- Transmission comb offset, as defined by the higher layer parameter *combOffset-n2*, *combOffset-n4*, and *combOffset-n8* for transmission comb value 2, 4, or 8, and described in clause 6.4.1.4 of [4, TS 38.211]. When comb offset hopping is configured by the higher layer parameter *[combOffsetHopping]* for an SRS resource in an SRS resource set with the usage configured as 'antennaSwitching' or 'codebook', subject to UE capabilities, transmission comb offset(s) are updated as described in [clause 6.4.1.4 of [4, TS 38.211]]. For the comb offset hopping, a UE can be configured with a subset of comb offsets by the higher layer parameter *[combOffsetHoppingSubset]*, where the comb offset hopping is performed only across the comb offsets configured in the subset. The UE is not expecting that the comb offset hopping and the higher layer parameter *[tdm]* are configured simultaneously. +- SRS sequence ID, as defined by the higher layer parameter *sequenceId* in clause 6.4.1.4 of [4, TS 38.211]. +- SRS cyclic shift and/or comb offset hopping ID, as defined by the higher layer parameter *[hoppingID]* +- The configuration of the spatial relation between a reference RS and the target SRS, where the higher layer parameter *spatialRelationInfo* or *spatialRelationInfoPos*, if configured, contains the ID of the reference RS. The reference RS may be an SS/PBCH block, CSI-RS configured on serving cell indicated by higher layer parameter *servingCellId* if present, same serving cell as the target SRS otherwise, or an SRS configured on uplink BWP indicated by the higher layer parameter *uplinkBWP*, and serving cell indicated by the higher layer parameter *servingCellId* if present, same serving cell as the target SRS otherwise. When the target SRS is configured by the higher layer parameter *SRS-PosResourceSet*, the reference RS may also be a DL PRS configured on a serving cell or a non-serving cell indicated by the higher layer parameter *dl-PRS*, or an SS/PBCH block of a non-serving cell indicated by the higher layer parameter *ssb-Ncell*. If the UE is configured with *dl-OrJointTCI-StateList* or *ul-TCI-StateList*, the reference RS may additionally be an SS/PBCH block associated with a PCI different from the PCI of the serving cell. + +The UE may be configured by the higher layer parameter *resourceMapping* in *SRS-Resource* with an SRS resource occupying $N_s \in \{1, 2, 4\}$ adjacent OFDM symbols within the last 6 symbols of the slot, or at any symbol location within the slot if *resourceMapping-r16* is provided subject to UE capability, where all antenna ports of the SRS resources are mapped to each symbol of the resource. When the SRS is configured with the higher layer parameter *SRS-PosResourceSet* the higher layer parameter *resourceMapping-r16* in *SRS-PosResource* indicates an SRS resource occupying adjacent symbols anywhere within the slot. When the SRS is configured with the higher layer parameter *SRS-ResourceSet*, the higher layer parameter *resourceMapping-r17* in *SRS-Resource* indicates an SRS resource occupying adjacent symbols anywhere within the slot. $S$ is divisible by $R$ , where $S = 2$ when *[tdm]* is configured and $S = 1$ otherwise, and $R$ is the repetition factor. + +If a PUSCH with a priority index 0 and SRS configured by *SRS-Resource* are transmitted in the same slot on a serving cell, the UE may only be configured to transmit SRS after the transmission of the PUSCH and the corresponding DM-RS. + +If a PUSCH transmission with a priority index 1 or a PUCCH transmission with a priority index 1 would overlap in time with an SRS transmission on a serving cell, the UE does not transmit the SRS in the overlapping symbol(s). + +For a UE configured with one or more SRS resource configuration(s), and when the higher layer parameter *resourceType* in *SRS-Resource* or *SRS-PosResource* is set to 'periodic': + +- if the UE is configured with the higher layer parameter *spatialRelationInfo*, *spatialRelationInfo-PDC* or *spatialRelationInfoPos* containing the ID of a reference 'ssb-Index', 'ssb-IndexServing', or 'ssb-IndexNcell', the UE shall transmit the target SRS resource with the same spatial domain transmission filter used for the reception of the reference SS/PBCH block, if the higher layer parameter *spatialRelationInfo*, *spatialRelationInfo-PDC* or *spatialRelationInfoPos* contains the ID of a reference 'csi-RS-Index' or 'csi-RS-IndexServing', the UE shall transmit the target SRS resource with the same spatial domain transmission filter used for the reception of the reference periodic CSI-RS or of the reference semi-persistent CSI-RS, if the higher layer parameter *spatialRelationInfo*, *spatialRelationInfo-PDC* or *spatialRelationInfoPos* containing the ID of a reference 'srs' or 'srs-spatialRelation', the UE shall transmit the target SRS resource with the same spatial domain transmission + +filter used for the transmission of the reference periodic SRS. When the SRS is configured by the higher layer parameter *SRS-PosResource* and if the higher layer parameter *spatialRelationInfoPos* contains the ID of a reference 'dl-PRS', the UE shall transmit the target SRS resource with the same spatial domain transmission filter used for the reception of the reference DL PRS. When the SRS is configured by the higher layer parameter *SRS-Resource* and if the higher layer parameter *spatialRelationInfo-PDC* contains the ID of a reference 'dl-PRS-PDC', the UE shall transmit the target SRS resource with the same spatial domain transmission filter used for the reception of the reference DL PRS for RTT-based propagation delay compensation according to clause 9. + +For a UE configured with one or more SRS resource configuration(s), and when the higher layer parameter *resourceType* in *SRS-Resource* or *SRS-PosResource* is set to 'semi-persistent': + +- when a UE receives an activation command, as described in clause 6.1.3.17 or 6.1.3.36 of [10, TS 38.321], for an SRS resource, and when the UE would transmit a PUCCH with HARQ-ACK information in slot $n$ corresponding to the PDSCH carrying the activation command, the corresponding actions in [10, TS 38.321] and the UE assumptions on SRS transmission corresponding to the configured SRS resource set shall be applied starting from the first slot that is after slot $n$ where $\mu$ is the SCS configuration for the PUCCH. The activation command also contains spatial relation assumptions provided by a list of references to reference signal IDs, one per element of the activated SRS resource set. When the SRS is configured with the higher layer parameter *SRS-ResourceSet*, each ID in the list refers to a reference SS/PBCH block, NZP CSI-RS resource configured on serving cell indicated by *Resource Serving Cell ID* field in the activation command if present, same serving cell as the SRS resource set otherwise, or SRS resource configured on serving cell and uplink bandwidth part indicated by *Resource Serving Cell ID* field and *Resource BWP ID* field in the activation command if present, same serving cell and bandwidth part as the SRS resource set otherwise. When the SRS is configured with the higher layer parameter *SRS-PosResourceSet*, each ID in the list of reference signal IDs may refer to a reference SS/PBCH block on a serving or non-serving cell indicated by *PCI* field in the activation command, NZP CSI-RS resource configured on serving cell indicated by *Resource Serving Cell ID* field in the activation command if present, same serving cell as the SRS resource set otherwise, SRS resource configured on serving cell and uplink bandwidth part indicated by *Resource Serving Cell ID* field and *Resource BWP ID* field in the activation command if present, same serving cell and bandwidth part as the SRS resource set otherwise, or DL PRS resource of a serving or non-serving cell associated with a *dl-PRS-ID* indicated by *DL-PRS ID* field in the activation command. +- if an SRS resource in the activated resource set is configured with the higher layer parameter *spatialRelationInfo* or *spatialRelationInfoPos*, the UE shall assume that the ID of the reference signal in the activation command overrides the one configured in *spatialRelationInfo* or *spatialRelationInfoPos*. +- when a UE receives a deactivation command [10, TS 38.321] for an activated SRS resource set, and when the UE would transmit a PUCCH with HARQ-ACK information in slot $n$ corresponding to the PDSCH carrying the deactivation command, the corresponding actions in [10, TS 38.321] and UE assumption on cessation of SRS transmission corresponding to the deactivated SRS resource set shall apply starting from the first slot that is after slot $n$ where $\mu$ is the SCS configuration for the PUCCH. +- if the UE is configured with the higher layer parameter *spatialRelationInfo* or *spatialRelationInfoPos* containing the ID of a reference 'ssb-Index', 'ssb-IndexServing', or 'ssb-IndexNcell' the UE shall transmit the target SRS resource with the same spatial domain transmission filter used for the reception of the reference SS/PBCH block, if the higher layer parameter *spatialRelationInfo* or *spatialRelationInfoPos* contains the ID of a reference 'csi-RS-Index' or 'csi-RS-IndexServing', the UE shall transmit the target SRS resource with the same spatial domain transmission filter used for the reception of the reference periodic CSI-RS or of the reference semi-persistent CSI-RS, if the higher layer parameter *spatialRelationInfo* or *spatialRelationInfoPos* contains the ID of a reference 'srs' or 'srs-SpatialRelation', the UE shall transmit the target SRS resource with the same spatial domain transmission filter used for the transmission of the reference periodic SRS or of the reference semi-persistent SRS. When the SRS is configured by the higher layer parameter *SRS-PosResourceSet* and if the higher layer parameter *spatialRelationInfoPos* contains the ID of a reference 'dl-PRS', the UE shall transmit the target SRS resource with the same spatial domain transmission filter used for the reception of the reference DL PRS. + +If the UE has an active semi-persistent SRS resource configuration and has not received a deactivation command, the semi-persistent SRS configuration is considered to be active in the UL BWP which is active, otherwise it is considered suspended. + +For a UE configured with one or more SRS resource configuration(s), and when the higher layer parameter *resourceType* in *SRS-Resource* or *SRS-PosResource* is set to 'aperiodic': + +- the UE receives a configuration of SRS resource sets, + +- the UE receives a downlink DCI, a group common DCI, or an uplink DCI based command where a codepoint of the DCI may trigger one or more SRS resource set(s). For SRS in a resource set with usage set to 'codebook' or 'antennaSwitching', the minimal time interval between the last symbol of the PDCCH triggering the aperiodic SRS transmission and the first symbol of SRS resource is $N_2$ symbols and an additional time duration $T_{switch}$ . Otherwise, the minimal time interval between the last symbol of the PDCCH triggering the aperiodic SRS transmission and the first symbol of SRS resource is $N_2 + 14$ symbols and an additional time duration $T_{switch}$ . The minimal time interval unit of OFDM symbol is counted based on the minimum subcarrier spacing given by $\min(\mu_{PDCCH}, \mu_{UL})$ where $\mu_{UL}$ is given by $\min(\mu_{UL,carrier1}, \mu_{UL,carrier2}, \mu_{SRS})$ when the UE is configured with the higher layer parameter *uplinkTxSwitchingOption* set to 'dualUL' for uplink carrier aggregation, and by $\mu_{SRS}$ otherwise. $\mu_{SRS}$ and $\mu_{PDCCH}$ are the subcarrier spacing configurations for triggered SRS and PDCCH carrying the triggering command respectively. +- $T_{switch}$ , $\mu_{UL,carrier1}$ and $\mu_{UL,carrier2}$ are defined in clause 6.4. +- A UE reporting its UE capability 'srs-TriggeringDCI' can be indicated with DCI 0\_1 and 0\_2 to trigger aperiodic SRS without data and without CSI as described in clause 7.3.1.1 of [5, TS 38.212]. Otherwise, except for DCI format 0\_1/0\_2 with CRC scrambled by SP-CSI-RNTI, a UE is not expected to receive a DCI format 0\_1/0\_2 with UL-SCH indicator of "0" and CSI request of all zero(s) as described in clause 7.3.1.1 of [5, TS 38.212]. +- If the UE receives the DCI triggering aperiodic SRS in slot $n$ and at least one resource set is configured with parameter *availableSlotOffset* across all configured BWPs in a component carrier except when SRS is configured with the higher layer parameter *SRS-PosResource*, + - If *ca-SlotOffset* is configured, the UE transmits aperiodic SRS in each of the triggered SRS resource set(s) in the $(t + 1)$ -th available slot counting from slot + +$$\left\lceil n \cdot \frac{2^{\mu_{SRS}}}{2^{\mu_{PDCCH}}} \right\rceil + k + \left\lceil \left( \frac{N_{slot,offset,PDCCH}^{CA}}{2^{\mu_{offset,PDCCH}}} - \frac{N_{slot,offset,SRS}^{CA}}{2^{\mu_{offset,SRS}}} \right) \cdot 2^{\mu_{SRS}} \right\rceil,$$ + - otherwise the UE transmits aperiodic SRS in each of the triggered SRS resource set(s) in the $(t + 1)$ -th available slot counting from slot $n$ , where +- $k$ is configured via higher layer parameter *slotOffset* for each triggered SRS resources set and is based on the subcarrier spacing of the triggered SRS transmission, $\mu_{SRS}$ and $\mu_{PDCCH}$ are the subcarrier spacing configurations for triggered SRS and PDCCH carrying the triggering command, respectively; +- $t$ and are the $\mu_{offset}$ , respectively, which are determined by higher-layer configured *ca-SlotOffset* for the cell receiving the PDCCH, and are the $\mu_{offset}$ , respectively, which are determined by higher-layer configured *ca-SlotOffset* for the cell transmitting the SRS, as defined in [4, TS 38.211] clause 4.5. +- An available slot is a slot satisfying there are UL or flexible symbol(s) for the time-domain location(s) for all the SRS resources in the resource set and it satisfies UE capability on the minimum timing requirement between triggering PDCCH and all the SRS resources in the resource set. From the first symbol carrying the SRS request DCI to the last symbol of the triggered SRS resource set, UE does not expect to receive SFI indication, UL cancellation indication or dynamic scheduling of DL channel/signal(s) on flexible symbol(s) that may change the determination of available slot. +- $t$ is configured via higher layer parameter *availableSlotOffsetList* with up to four different values of *AvailableSlotOffset* for each triggered SRS resources set and it is based on the subcarrier spacing of the triggered SRS transmission. When one or more SRS resource sets across all configured BWPs in a component carrier are configured, and at least one resource set is configured with *availableSlotOffsetList* parameter of more than one values, the indicated value of $t$ is indicated by SOI field in DCI scheduling PUSCH/PDSCH and DCI 0\_1/0\_2 without data and without CSI request described in [5, TS 38.212]. The UE shall apply indicated value $t$ specifically for those sets with configured *availableSlotOffsetList* parameter. When one or more SRS resource sets across all configured BWPs in a component carrier are configured and at least one resource set is configured with *availableSlotOffsetList* parameter, and the *availableSlotOffsetList* parameter for each SRS resource set has only one value, the UE shall apply the configured value specifically for those sets with configured *availableSlotOffsetList* parameter. For SRS resource set configured with *availableSlotOffsetList* parameter, each of resource set is configured with $K$ values of *AvailableSlotOffset*. For SRS resource set configured without *availableSlotOffsetList* parameter, $t = 0$ is applied for the resource set. + +- If the UE receives the DCI triggering aperiodic SRS in slot $n$ and none of the resource sets is configured with parameter *availableSlotOffsetList* across all configured BWPs in a component carrier except when SRS is configured with the higher layer parameter *SRS-PosResource* + +- if the UE is configured with *ca-SlotOffset* for at least one of the triggered and triggering cell, the UE transmits aperiodic SRS in each of the triggered SRS resource set(s) in slot + +$$\left\lceil n \cdot \frac{2^{\mu_{SRS}}}{2^{\mu_{PDCCH}}} \right\rceil + k + \left\lceil \left( \frac{N_{slot,offset,PDCCH}^{CA}}{2^{\mu_{offset,PDCCH}}} - \frac{N_{slot,offset,SRS}^{CA}}{2^{\mu_{offset,SRS}}}} \right) \cdot 2^{\mu_{SRS}} \right\rceil,$$ + +- otherwise, the UE transmits aperiodic SRS in each of the triggered resource set(s) in slot $n$ , where $n$ is a parameter configured by higher layer as specified in clause 4.2 of [6 TS 38.213], and where + +- $k$ is configured via higher layer parameter *slotOffset* for each triggered SRS resources set and is based on the subcarrier spacing of the triggered SRS transmission, $\mu_{SRS}$ and $\mu_{PDCCH}$ are the subcarrier spacing configurations for triggered SRS and PDCCH carrying the triggering command respectively; + +- $n$ is the subcarrier spacing configuration for $\mu_{PDCCH}$ with a value of 0 for frequency range 1. + +- $\mu_{PDCCH}$ and $\mu_{SRS}$ are the and the $\mu_{offset}$ , respectively, which are determined by higher-layer configured *ca-SlotOffset* for the cell receiving the PDCCH, and are the $N_{slot,offset}^{CA}$ and the $\mu_{offset}$ , respectively, which are determined by higher-layer configured *ca-SlotOffset* for the cell transmitting the SRS, as defined in [4, TS 38.211] clause 4.5. + +- If the UE receives the DCI triggering aperiodic SRS in slot $n$ and when SRS is configured with the higher layer parameter *SRS-PosResource*, the UE transmits every aperiodic SRS resource in each of the triggered SRS + +$$\left\lceil n \cdot \frac{2^{\mu_{SRS}}}{2^{\mu_{PDCCH}}} \right\rceil + k + \left\lceil \left( \frac{N_{slot,offset,PDCCH}^{CA}}{2^{\mu_{offset,PDCCH}}} - \frac{N_{slot,offset,SRS}^{CA}}{2^{\mu_{offset,SRS}}}} \right) \cdot 2^{\mu_{SRS}} \right\rceil,$$ + +resource set(s) in slot $n$ , if UE is configured with *ca-SlotOffset* for at least one of the triggered and triggering cell, , otherwise, where $n$ is a parameter configured by higher layer as specified in clause 4.2 of [6 TS 38.213], and where + +- $k$ is configured via higher layer parameter *slotOffset* for each aperiodic SRS resource in each triggered SRS resources set and is based on the subcarrier spacing of the triggered SRS transmission, $\mu_{SRS}$ and $\mu_{PDCCH}$ are the subcarrier spacing configurations for triggered SRS and PDCCH carrying the triggering command respectively; + +- $n$ is the subcarrier spacing configuration for $\mu_{PDCCH}$ with a value of 0 for frequency range 1. + +- $\mu_{PDCCH}$ and $\mu_{SRS}$ are the and the $\mu_{offset}$ , respectively, which are determined by higher-layer configured *ca-SlotOffset* for the cell receiving the PDCCH, and are the $N_{slot,offset}^{CA}$ and the $\mu_{offset}$ , respectively, which are determined by higher-layer configured *ca-SlotOffset* for the cell transmitting the SRS, as defined in [4, TS 38.211] clause 4.5. + +- if the UE is configured with the higher layer parameter *spatialRelationInfo* or *spatialRelationInfoPos* containing the ID of a reference 'ssb-Index', 'ssb-IndexServing' or 'ssb-IndexNcell', the UE shall transmit the target SRS resource with the same spatial domain transmission filter used for the reception of the reference SS/PBCH block, if the higher layer parameter *spatialRelationInfo* or *spatialRelationInfoPos* contains the ID of a reference 'csi-RS-Index' or 'csi-RS-IndexServing', the UE shall transmit the target SRS resource with the same spatial domain transmission filter used for the reception of the reference periodic CSI-RS or of the reference semi-persistent CSI-RS, or of the latest reference aperiodic CSI-RS. If the higher layer parameter *spatialRelationInfo* or *spatialRelationInfoPos* contains the ID of a reference 'srs' or 'srs-SpatialRelation', the UE shall transmit the target SRS resource with the same spatial domain transmission filter used for the transmission of the reference periodic SRS or of the reference semi-persistent SRS or of the reference aperiodic SRS. When the SRS is configured by the higher layer parameter *SRS-PosResourceSet* and if the higher layer parameter *spatialRelationInfoPos* contains the ID of a reference 'dl-PRS', the UE shall transmit the target SRS resource with the same spatial domain transmission filter used for the reception of the reference DL PRS. + +- when a UE receives an spatial relation update command, as described in clause 6.1.3.26 of [10, TS 38.321], for an SRS resource configured with the higher layer parameter *SRS-Resource*, and when the HARQ-ACK corresponding to the PDSCH carrying the update command is transmitted in slot $n$ , the corresponding actions in [10, TS 38.321] and the UE assumptions on updating spatial relation for the SRS resource shall be applied for SRS transmission starting from the first slot that is after slot $n$ where $\mu$ is the SCS configuration for the PUCCH. The update command contains spatial relation assumptions provided by a list of references to reference signal IDs, one per element of the updated SRS resource set. Each ID in the list refers to a reference SS/PBCH block, NZP CSI-RS resource configured on serving cell indicated by *Resource Serving Cell ID* field in the update command if present, same serving cell as the SRS resource set otherwise, or SRS resource configured on serving cell and uplink bandwidth part indicated by *Resource Serving Cell ID* field and *Resource BWP ID* field in the update command if present, same serving cell and bandwidth part as the SRS resource set otherwise. When the UE is configured with the higher layer parameter *usage* in *SRS-ResourceSet* set to 'antennaSwitching', the UE shall not expect to be configured with different spatial relations for SRS resources in the same SRS resource set. + +The UE is not expected to be configured with different time domain behavior for SRS resources in the same SRS resource set. The UE is also not expected to be configured with different time domain behavior between SRS resource and associated SRS resources set. + +For operation in the same carrier, the UE is not expected to be configured on overlapping symbols with a SRS resource configured by the higher layer parameter *SRS-PosResource* and a SRS resource configured by the higher layer parameter *SRS-Resource* with *resourceType* of both SRS resources as 'periodic'. + +For operation in the same carrier, the UE is not expected to be activated or triggered to transmit SRS on overlapping symbols with a SRS resource configured by the higher layer parameter *SRS-PosResource* and a SRS resource configured by the higher layer parameter *SRS-Resource* with *resourceType* of both SRS resources as 'semi-persistent' or 'aperiodic'. + +For operations in the same carrier, the UE is not expected to be configured on overlapping symbols with more than one SRS resources configured by the higher layer parameter *SRS-PosResource* with *resourceType* of the SRS resources as 'periodic'. + +For operations in the same carrier, the UE is not expected to be activated or triggered to transmit SRS on overlapping symbols with more than one SRS resources configured by the higher layer parameter *SRS-PosResource* with *resourceType* of the SRS resources as 'semi-persistent' or 'aperiodic'. + +For intra-band and inter-band CA operations, a UE can simultaneously transmit more than one SRS resource configured by *SRS-PosResource* on different CCs, subject to UE's capability + +For intra-band and inter-band CA operations, a UE can simultaneously transmit more than one SRS resource configured by *SRS-PosResource* and *SRS-Resource* on different CCs, subject to UE's capability. + +The SRS request field [5, TS38.212] in DCI format 0\_1, 1\_1, 0\_2 (if SRS request field is present), 1\_2 (if SRS request field is present), 0\_3, 1\_3 indicates the triggered SRS resource set given in Table 7.3.1.1.2-24 of [5, TS 38.212]. The 2-bit SRS request field in DCI format 2\_3 indicates the triggered SRS resource set given in clause 7.3 of [5, TS 38.212] and defined by the entries of the higher layer parameter *srs-ResourceSetToAddModList* if the UE is configured with higher layer parameter *srs-TPC-PDCCH-Group* set to 'typeB', or indicates the SRS transmission on a set of serving cells configured by higher layers if the UE is configured with higher layer parameter *srs-TPC-PDCCH-Group* set to 'typeA'. + +For PUCCH and SRS on the same carrier, a UE shall not transmit SRS when semi-persistent or periodic SRS is configured in the same symbol(s) with PUCCH carrying only CSI report(s), or only L1-RSRP report(s), or only L1-SINR report(s). A UE shall not transmit SRS when semi-persistent or periodic SRS is configured or aperiodic SRS is triggered to be transmitted in the same symbol(s) with PUCCH carrying HARQ-ACK, link recovery request (as defined in clause 9.2.4 of [6, 38.213]) and/or SR. In the case that SRS is not transmitted due to overlap with PUCCH, only the SRS symbol(s) that overlap with PUCCH symbol(s) are dropped. PUCCH shall not be transmitted when aperiodic SRS is triggered to be transmitted to overlap in the same symbol with PUCCH carrying semi-persistent/periodic CSI report(s) or semi-persistent/periodic L1-RSRP report(s) only, or only L1-SINR report(s). + +In case of intra-band contiguous carrier aggregation, or in inter-band or intra-band non-contiguous CA band combination if simultaneous SRS and PUCCH/PUSCH transmissions are not supported by UE, the UE is not expected to be indicated with a SRS transmission from a carrier and to be configured or scheduled with a PUSCH/UL DM-RS/UL PT-RS/PUCCH transmission from a different carrier in the same symbol. + +In case of intra-band contiguous carrier aggregation, or in inter-band CA band combination if simultaneous SRS and PRACH transmissions are not supported by UE, or in case of intra-band non-contiguous CA band combination if the UE is not configured with higher layer parameter *intraBandNC-PRACH-simulTx-r17*, the UE shall not transmit simultaneously SRS resource(s) from a carrier and PRACH from a different carrier. + +In case of intra-band contiguous carrier aggregation, or in inter-band CA band combination if simultaneous SRS and MsgA transmissions are not supported by UE, the UE shall not transmit simultaneously SRS resource(s) from a carrier and MsgA from a different carrier. + +In case a SRS resource with *resourceType* set as 'aperiodic' is triggered on the OFDM symbol(s) configured with periodic/semi-persistent SRS transmission, the UE shall transmit the aperiodic SRS resource and only the periodic/semi-persistent SRS symbol(s) overlapping within the symbol(s) are dropped, while the periodic/semi-persistent SRS symbol(s) that are not overlapped with the aperiodic SRS resource are transmitted. In case a SRS resource with *resourceType* set as 'semi-persistent' is triggered on the OFDM symbol(s) configured with periodic SRS transmission, the UE shall transmit the semi-persistent SRS resource and only the periodic SRS symbol(s) overlapping within the symbol(s) are dropped, while the periodic SRS symbol(s) that are not overlapped with the semi-persistent SRS resource are transmitted. + +When the UE is configured with the higher layer parameter *usage* in *SRS-ResourceSet* set to 'antennaSwitching', and a guard period of Y symbols is configured according to Clause 6.2.1.2, the UE shall use the same priority rules as defined above during the guard period as if SRS was configured. + +When a *spatialRelationInfo* is activated/updated for a semi-persistent or aperiodic SRS resource configured by the higher layer parameter *SRS-Resource* by a MAC CE for a set of CCs/BWPs, where the applicable list of CCs provided by higher layer parameter *simultaneousSpatial-UpdatedList1* or *simultaneousSpatial-UpdatedList2* is determined by the indicated CC in the MAC CE, the *spatialRelationInfo* is applied for the semi-persistent or aperiodic SRS resource(s) with the same SRS resource ID for all the BWPs in the determined CCs. + +When the higher layer parameter *enableDefaultBeamPL-ForSRS* is set 'enabled', and if the higher layer parameter *spatialRelationInfo* for the SRS resource, except for the SRS resource with the higher layer parameter *usage* in *SRS-ResourceSet* set to 'beamManagement' or for the SRS resource with the higher layer parameter *usage* in *SRS-ResourceSet* set to 'nonCodebook' with configuration of *associatedCSI-RS* or for the SRS resource configured by the higher layer parameter *SRS-PosResourceSet*, or *dl-OrJointTCI-StateList* or *ul-TCI-StateList* is not configured in frequency range 2 and if the UE is not configured with higher layer parameter(s) *pathlossReferenceRS*, and if the UE is not configured with different values of *coresetPoolIndex* in *ControlResourceSets*, and is not provided at least one TCI codepoint mapped with two TCI states, the UE shall transmit the target SRS resource in an active UL BWP of a CC, + +- according to the spatial relation, if applicable, with a reference to the RS configured with *qcl-Type* set to 'typeD' corresponding to the QCL assumption of the CORESET with the lowest *controlResourceSetId* in the active DL BWP in the CC. If the CORESET is activated with two TCI states, *sfnSchemePdcch* is configured and the UE supports *sfn-DefaultUL-BeamSetup-r17*, UE shall use the first TCI state as the QCL assumption. +- according to the spatial relation, if applicable, with a reference to the RS configured with *qcl-Type* set to 'typeD' in the activated TCI state with the lowest ID applicable to PDSCH in the active DL BWP of the CC if the UE is not configured with any CORESET in the active DL BWP of the CC. + +For a SRS resource, if the higher layer parameters *[tdm]* or *[combOffsetHopping]* are configured, the corresponding UE SRS frequency hopping procedure is specified in clause 6.4.1.4.3 of [4, TS 38.211]. If for a SRS resource the higher layer parameters *[tdm]* and *[combOffsetHopping]* are not configured, the UE SRS frequency hopping procedure is specified in clause 6.4.1.4.3 of [4, TS 38.211] and in clause 6.2.1.1. + +#### 6.2.1.1 UE SRS frequency hopping procedure + +For a given SRS resource, the UE is configured with repetition factor $R \in \{1, 2, 4\}$ or $R \in \{1, 2, 3, 4, 5, 6, 7, 8, 10, 12, 14\}$ by higher layer parameter *resourceMapping* in *SRS-Resource* where $R \leq N_s$ . When frequency hopping within an SRS resource in each slot is not configured ( $R = N_s$ ), each of the antenna ports of the SRS resource in each slot is mapped in all the symbols to the same set of subcarriers in the same set of PRBs. When frequency hopping within an SRS resource in each slot is configured without repetition ( $R = 1$ ), according to the SRS hopping parameters, and defined in clause 6.4.1.4 of [4, TS 38.211], each of the antenna ports of the SRS resource in each slot is mapped to different sets of subcarriers in each OFDM symbol, where the same transmission comb value is assumed for different sets of subcarriers. When both frequency hopping and repetition within an SRS resource in each slot are configured ( $N_s \geq 4$ , $R \geq 2$ ), each of the antenna ports of the SRS resource in each slot is mapped to the same set of subcarriers within each set of R adjacent + +OFDM symbols, and frequency hopping across the sets is according to the SRS hopping parameters $N_s$ and $R$ , where $N_s$ should be divisible by $R$ . + +For operation with shared spectrum channel access in FR1, the UE does not expect that multiple hops of an SRS resource transmission are in different RB sets. + +A UE may be configured adjacent symbol aperiodic SRS resource with intra-slot frequency hopping within a bandwidth part, where the full hopping bandwidth is sounded with an equal-size subband across symbols when frequency hopping is configured with $R=1$ . A UE may be configured $N_s \geq 4$ adjacent symbols aperiodic SRS resource with intra-slot frequency hopping within a bandwidth part, where the full hopping bandwidth is sounded with an equal-size subband across sets of $R$ adjacent OFDM symbols, when frequency hopping is configured with $R \geq 2$ , $N_s \geq R$ and $N_s$ should be divisible by $R$ . Each of the antenna ports of the SRS resource is mapped to the same set of subcarriers within each set of $R$ adjacent OFDM symbols of the resource. + +A UE may be configured symbol periodic or semi-persistent SRS resource with inter-slot hopping within a bandwidth part, where the SRS resource occupies the same symbol location in each slot. A UE may be configured symbol periodic or semi-persistent SRS resource with intra-slot and inter-slot hopping within a bandwidth part, where the SRS resource occupies the same symbol location(s) in each slot. For $N_s \geq 4$ , when frequency hopping is configured with $R \geq 2$ , intra-slot and inter-slot hopping is supported with each of the antenna ports of the SRS resource mapped to different sets of subcarriers across sets of $R$ adjacent OFDM symbol(s) of the resource in each slot, where $N_s$ should be divisible by $R$ . Each of the antenna ports of the SRS resource is mapped to the same set of subcarriers within each set of $R$ adjacent OFDM symbols of the resource in each slot. For $N_s = R$ , when frequency hopping is configured, inter-slot frequency hopping is supported with each of the antenna ports of the SRS resource mapped to the same set of subcarriers in $R$ adjacent OFDM symbol(s) of the resource in each slot. + +#### 6.2.1.2 UE sounding procedure for DL CSI acquisition + +When the UE is configured with the higher layer parameter *usage* in *SRS-ResourceSet* set as 'antennaSwitching', the UE may be configured with only one of the following configurations depending on the indicated UE capability *supportedSRS-TxPortSwitch* ('t1r2' for 1T2R, 't1r1-t1r2' for 1T=1R/1T2R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't1r1-t1r2-t1r4' for 1T=1R/1T2R/1T4R, 't1r4-t2r4' for 1T4R/2T4R, 't1r1-t1r2-t2r2-t2r4' for 1T=1R/1T2R/2T=2R/2T4R, 't1r1-t1r2-t2r2-t1r4-t2r4' for 1T=1R/1T2R/2T=2R/1T4R/2T4R, 't1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r1-t2r2' for 1T=1R/2T=2R, 't4r4' for 4T=4R, or 't1r1-t2r2-t4r4' for 1T=1R/2T=2R/4T=4R) or the UE may be configured with only one of the following configurations depending on the indicated UE capability *supportedSRS-TxPortSwitchBeyond4Rx* ('t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R) or the UE may be configured with the following configurations depending on the indicated UE capability [*newUECapabilitySupporting8T8R*]: + +- For 1T2R, if the UE is indicating *srs-AntennaSwitching2SP-1Periodic* and/or *srs-ExtensionAperiodicSRS*: + - when the UE is indicating *srs-AntennaSwitching2SP-1Periodic* only, then up to two SRS resource sets with *resourceType* in *SRS-ResourceSet* set to 'semi-persistent' and up to one SRS resource set with *resourceType* in *SRS-ResourceSet* set to 'periodic' can be configured, or up to two SRS resource sets configured with a different value for the higher layer parameter *resourceType* in *SRS-ResourceSet* can be configured, where the two SRS resource sets configured with 'semi-persistent' are not activated at the same time, each SRS resource set has two SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a single SRS port, and the SRS port of the second resource in the set is associated with a different UE antenna port than the SRS port of the first resource in the same set. + - when the UE is indicating *srs-ExtensionAperiodicSRS* only, then up to two SRS resource sets with *resourceType* in *SRS-ResourceSet* set to 'aperiodic' and up to one SRS resource set with *resourceType* in *SRS-ResourceSet* set to 'periodic' or 'semi-persistent' can be configured, or up to two SRS resource sets configured with a different value for the higher layer parameter *resourceType* in *SRS-ResourceSet* can be configured. In the case of two resource sets with *resourceType* in *SRS-ResourceSet* set to 'aperiodic', a total of two SRS resources are transmitted in different symbols of two different slots, the SRS port of each SRS resource in the given two sets is associated with a different UE antenna port and the two sets are each configured with one SRS resource. In the case of the one resource set with *resourceType* in *SRS-ResourceSet* set to 'aperiodic' is configured, a total of two SRS resources transmitted in different symbols of one slot and where the SRS port of the second resource in the given set is associated with a different UE antenna port than the SRS port of the first resource in the same set. Each SRS resource set with 'resourceType' in *SRS-ResourceSet* set to 'periodic' or 'semi-persistent' has two SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a single SRS port, and the SRS port of the second resource in the set is associated with a different UE antenna port than the SRS port of the first resource in the same set. + +- zero or one or two SRS resource sets configured with different value of *resourceType* in *SRS-ResourceSet* set to 'periodic' or 'semi-persistent' if the UE is not indicating *srs-AntennaSwitching2SP-1Periodic*, or up to two SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to 'semi-persistent' and up to one SRS resource set configured with *resourceType* in *SRS-ResourceSet* set to 'periodic' if the UE is indicating *srs-AntennaSwitching2SP-1Periodic*, where the two SRS resource sets configured with 'semi-persistent' are not activated at the same time. An SRS resource set has two SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a single SRS port, and the SRS port of the second resource in the set is associated with a different UE antenna port than the SRS port of the first resource in the same set, and +- zero or one SRS resource set with *resourceType* in *SRS-ResourceSet* set to 'aperiodic' if the UE is not indicating *srs-ExtensionAperiodicSRS*, or up to two SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to 'aperiodic' if the UE is indicating *srs-ExtensionAperiodicSRS*, where in the case of one resource set, a total of two SRS resources transmitted in different symbols of one slot and where the SRS port of the second resource in the given set is associated with a different UE antenna port than the SRS port of the first resource in the same set. In the case of two resource sets, a total of two SRS resources are transmitted in different symbols of two different slots, the SRS port of each SRS resource in the given two sets is associated with a different UE antenna port. The two sets are each configured with one SRS resource, or +- otherwise, for 1T2R, up to two SRS resource sets configured with a different value for the higher layer parameter *resourceType* in *SRS-ResourceSet* set, where each set has two SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a single SRS port, and the SRS port of the second resource in the set is associated with a different UE antenna port than the SRS port of the first resource in the same set, or +- For 2T4R, if the UE is indicating *srs-AntennaSwitching2SP-1Periodic* and/or *srs-ExtensionAperiodicSRS*: + - when the UE is indicating *srs-AntennaSwitching2SP-1Periodic* only, then up to two SRS resource sets with *resourceType* in *SRS-ResourceSet* set to 'semi-persistent' and up to one SRS resource set with *resourceType* in *SRS-ResourceSet* set to 'periodic' can be configured, or up to two SRS resource sets configured with a different value for the higher layer parameter *resourceType* in *SRS-ResourceSet* can be configured, where the two SRS resource sets configured with 'semi-persistent' are not activated at the same time, each SRS resource set has two SRS resources transmitted in different symbols, each SRS resource in a given set consisting of two SRS ports, and the SRS port pair of the second resource is associated with a different UE antenna port pair than the SRS port pair of the first resource. + - when the UE is indicating *srs-ExtensionAperiodicSRS* only, then up to two SRS resource sets with *resourceType* in *SRS-ResourceSet* set to 'aperiodic' and up to one SRS resource set with *resourceType* in *SRS-ResourceSet* set to 'periodic' or 'semi-persistent' can be configured, or up to two SRS resource sets configured with a different value for the higher layer parameter *resourceType* in *SRS-ResourceSet* can be configured. In the case of two resource sets with *resourceType* in *SRS-ResourceSet* set to 'aperiodic', a total of two SRS resources are transmitted in different symbols of two different slots, the SRS port pair of each SRS resource in the given two sets is associated with a different UE antenna port pair and the two sets are each configured with one SRS resource. In the case of one resource set with *resourceType* in *SRS-ResourceSet* set to 'aperiodic' is configured, a total of two SRS resources transmitted in different symbols in the same slot, each SRS resource in a given set consisting of two SRS ports, and the SRS port pair of the second resource is associated with a different UE antenna port pair than the SRS port pair of the first resource. Each SRS resource set with '*resourceType*' in *SRS-ResourceSet* set to 'periodic' or 'semi-persistent' has two SRS resources transmitted in different symbols, each SRS resource in a given set consisting of two SRS ports, and the SRS port pair of the second resource is associated with a different UE antenna port pair than the SRS port pair of the first resource. + - zero or one or two SRS resource sets configured with a different value for the higher layer parameter *resourceType* in *SRS-ResourceSet* set to 'periodic' or 'semi-persistent' if the UE is not indicating *srs-AntennaSwitching2SP-1Periodic*, or up to two SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to 'semi-persistent' and up to one SRS resource set configured with *resourceType* in *SRS-ResourceSet* set to 'periodic' if the UE is indicating *srs-AntennaSwitching2SP-1Periodic*, where the two SRS resource sets configured with 'semi-persistent' are not activated at the same time. Each SRS resource set has two SRS resources transmitted in different symbols, each SRS resource in a given set consisting of two SRS ports, and the SRS port pair of the second resource is associated with a different UE antenna port pair than the SRS port pair of the first resource, and, + +- zero or one SRS resource set configured with *resourceType* in *SRS-ResourceSet* set to 'aperiodic' if the UE is not indicating *srs-ExtensionAperiodicSRS*, or up to two SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to 'aperiodic' if the UE is indicating *srs-ExtensionAperiodicSRS*, where in the case of one resource set, a total of two SRS resources transmitted in different symbols in the same slot, each SRS resource in a given set consisting of two SRS ports, and the SRS port pair of the second resource is associated with a different UE antenna port pair than the SRS port pair of the first resource. In the case of two resource sets, a total of two SRS resources are transmitted in different symbols of two different slots, the SRS port pair of each SRS resource in the given two sets is associated with a different UE antenna port pair. The two sets are each configured with one SRS resource, or +- otherwise, for 2T4R, up to two SRS resource sets configured with a different value for the higher layer parameter *resourceType* in *SRS-ResourceSet*, where each SRS resource set has two SRS resources transmitted in different symbols, each SRS resource in a given set consisting of two SRS ports, and the SRS port pair of the second resource is associated with a different UE antenna port pair than the SRS port pair of the first resource, or +- For 1T4R, if the UE is indicating *srs-AntennaSwitching2SP-1Periodic* and/or *srs-ExtensionAperiodicSRS* and/or *srs-OneAP-SRS*, + - zero or one SRS resource set configured with *resourceType* in *SRS-ResourceSet* set to 'periodic' or 'semi-persistent' if the UE is not indicating *srs-AntennaSwitching2SP-1Periodic*, or up to two SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to 'semi-persistent' and up to one SRS resource set configured with *resourceType* in *SRS-ResourceSet* set to 'periodic' if the UE is indicating *srs-AntennaSwitching2SP-1Periodic*, where the two SRS resource sets configured with 'semi-persistent' are not activated at the same time. Each SRS resource set has four SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a single SRS port, and the SRS port of each resource is associated with a different UE antenna port, and + - zero or two SRS resource sets each configured with *resourceType* in *SRS-ResourceSet* set to 'aperiodic', if the UE is not indicating *srs-ExtensionAperiodicSRS* or *srs-OneAP-SRS*, or zero or one or two or four SRS resource sets each configured with *resourceType* in *SRS-ResourceSet* set to 'aperiodic' if the UE is indicating *srs-ExtensionAperiodicSRS* and *srs-OneAP-SRS*, or zero or two or four SRS resource sets each configured with *resourceType* in *SRS-ResourceSet* set to 'aperiodic' if the UE is indicating *srs-ExtensionAperiodicSRS* only, or zero or one or two SRS resource sets each configured with *resourceType* in *SRS-ResourceSet* set to 'aperiodic' if the UE is indicating *srs-OneAP-SRS* only. In the case of one resource set, a total of four SRS resources are transmitted in different symbols in the same slot, and the SRS port of each resource in the given set is associated with a different UE antenna port. In the case of two resource sets, a total of four SRS resources are transmitted in different symbols of two different slots, and the SRS port of each SRS resource in the given two sets is associated with a different UE antenna port. The two sets are each configured with two SRS resources, or one set is configured with one SRS resource and the other set is configured with three SRS resources. In the case of four resource sets, a total of four SRS resources are transmitted in different symbols of four different slots, and the SRS port of each SRS resource in the given four sets is associated with a different UE antenna port. The four sets are each configured with one SRS resource. The UE shall expect that the value of the higher layer parameter *aperiodicSRS-ResourceTrigger* or the value of an entry in *AperiodicSRS-ResourceTriggerList* in each *SRS-ResourceSet* is the same, and the value of the higher layer parameter *slotOffset* in each *SRS-ResourceSet* is different when none of the SRS resource sets is configured with parameter *availableSlotOffsetList* across all configured BWPs in a component carrier. Or, +- otherwise, for 1T4R, + - zero or one SRS resource set configured with higher layer parameter *resourceType* in *SRS-ResourceSet* set to 'periodic' or 'semi-persistent' with four SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a single SRS port, and the SRS port of each resource is associated with a different UE antenna port, and + - zero or two SRS resource sets each configured with higher layer parameter *resourceType* in *SRS-ResourceSet* set to 'aperiodic' and with a total of four SRS resources transmitted in different symbols of two different slots, and where the SRS port of each SRS resource in the given two sets is associated with a different UE antenna port. The two sets are each configured with two SRS resources, or one set is configured with one SRS resource and the other set is configured with three SRS resources. The UE shall expect that the value of the higher layer parameter *aperiodicSRS-ResourceTrigger* or the value of an entry in *AperiodicSRS-ResourceTriggerList* in each *SRS-ResourceSet* is the same, and the value of the higher layer parameter *slotOffset* in each *SRS-ResourceSet* is different when none of the SRS resource sets is configured with parameter *availableSlotOffsetList* across all configured BWPs in a component carrier. Or, + +- For 1T=1R, 2T=2R, 4T=4R or 8T=8R, up to two SRS resource sets each with one SRS resource can be configured, where the number of SRS ports for each resource is equal to 1, 2, 4 or 8 if the UE is not indicating *srs-AntennaSwitching2SP-1Periodic*. Up to two SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to '*semi-persistent*' and one SRS resource set configured with *resourceType* in *SRS-ResourceSet* set to '*periodic*' can be configured and the two SRS resource sets configured with '*semi-persistent*' are not activated at the same time, or up to two SRS resource sets can be configured, if the UE is indicating *srs-AntennaSwitching2SP-1Periodic* or [*srs-AntennaSwitching2SP-1Periodic8T8R*], where each SRS resource set has one SRS resource, the number of SRS ports for each resource is equal to 1, 2, 4, or 8 or +- For 1T6R, zero or one SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to '*periodic*', where in the case of one resource set has six SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a single SRS port, and the SRS port of the resource in the set is associated with a different UE antenna port, and +- For 1T6R, zero or one SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to '*semi-persistent*' if the UE is not indicating *srs-AntennaSwitching2SP-1Periodic*, or up to two SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to '*semi-persistent*' if the UE is indicating *srs-AntennaSwitching2SP-1Periodic*, where the two SRS resource sets configured with '*semi-persistent*' are not activated at the same time. Each SRS resource set has six SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a single SRS port, and the SRS port of the resource in the set is associated with a different UE antenna port, and +- For 1T6R, zero or one or two or three SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to '*aperiodic*', where in the case of one resource set a total of six SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a single SRS port, and the SRS port of each resource in the set is associated with a different UE antenna port. In the case of two resource sets a total of six SRS resources are transmitted in different symbols of two different slots, and the SRS port of each SRS resource in the given two sets is associated with a different UE antenna port. In the case of three resource sets, a total of six SRS resources are transmitted in different symbols of three different slots, and the SRS port of each SRS resource in the given three sets is associated with a different UE antenna port, or +- For 1T8R, zero or one SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to '*periodic*', where in the case of one resource set has eight SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a single SRS port, and the SRS port of the resource in the set is associated with a different UE antenna port, and +- For 1T8R, zero or one SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to '*semi-persistent*' if the UE is not indicating *srs-AntennaSwitching2SP-1Periodic*, or up to two SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to '*semi-persistent*' if the UE is indicating *srs-AntennaSwitching2SP-1Periodic*, where the two SRS resource sets configured with '*semi-persistent*' are not activated at the same time. Each SRS resource set has eight SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a single SRS port, and the SRS port of the resource in the set is associated with a different UE antenna port, and +- For 1T8R, zero or two or three or four SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to '*aperiodic*', where in the case of two resource sets a total of eight SRS resources transmitted in different symbols of two different slots, and where the SRS port of each SRS resource in the given two sets is associated with a different UE antenna port. In the case of three resource sets a total of eight SRS resources are transmitted in different symbols of three different slots, and the SRS port of each SRS resource in the given three sets is associated with a different UE antenna port. In the case of four resource sets a total of eight SRS resources are transmitted in different symbols of four different slots, and the SRS port of each SRS resource in the given four sets is associated with a different UE antenna port, or +- For 2T6R, zero or one SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to '*periodic*', where in the case of one resource set has three SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a two SRS ports, and the SRS port pair of the resource in the set is associated with a different UE antenna port pair, and +- For 2T6R, zero or one SRS resource sets configured *resourceType* in *SRS-ResourceSet* set to '*semi-persistent*' if the UE is not indicating *srs-AntennaSwitching2SP-1Periodic*, or up to two SRS resource sets configured with '*semi-persistent*' and up to one SRS resource set configured with '*periodic*' if the UE is indicating *srs-AntennaSwitching2SP-1Periodic*, where the two SRS resource sets configured with '*semi-persistent*' are not activated at the same time. Each SRS resource set has three SRS resources transmitted in different symbols, + +each SRS resource in a given set consisting of a two SRS ports, and the SRS port pair of the resource in the set is associated with a different UE antenna port pair, and + +- For 2T6R, zero or one or two or three SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to 'aperiodic', where in the case of one resource set has three SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a two SRS ports, and the SRS port pair of the resource in the set is associated with a different UE antenna port pair. In the case of two resource sets a total of three SRS resources are transmitted in different symbols of two different slots, and the SRS port pair of each SRS resource in the given two sets is associated with a different UE antenna port pair. One set is configured with two SRS resources and another set with one resource. In the case of three resource sets a total of three SRS resources are transmitted in different symbols of three different slots, and the SRS port pair of each SRS resource in the given three sets is associated with a different UE antenna port pair, or +- For 2T8R, zero or one SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to 'periodic', where in the case of one resource set has four SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a two SRS ports, and the SRS port pair of the resource in the set is associated with a different UE antenna port pair, and +- For 2T8R, zero or one SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to 'semi-persistent' if the UE is not indicating *srs-AntennaSwitching2SP-1Periodic*, or up to two SRS resource sets configured with 'semi-persistent' and up to one SRS resource set configured with 'periodic' if the UE is indicating *srs-AntennaSwitching2SP-1Periodic*, where the two SRS resource sets configured with 'semi-persistent' are not activated at the same time. Each SRS resource set has four SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a two SRS ports, and the SRS port pair of the resource in the set is associated with a different UE antenna port pair, and +- For 2T8R, zero or one or two or three or four SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to 'aperiodic', where in the case of one resource set has four SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a two SRS ports, and the SRS port pair of the resource in the set is associated with a different UE antenna port pair. In the case of two resource sets a total of four SRS resources transmitted in different symbols of two different slots, and where the SRS port pair of each SRS resource in the given two sets is associated with a different UE antenna port pair. In the case of three resource sets a total of four SRS resources transmitted in different symbols of three different slots, and where the SRS port pair of each SRS resource in the given three sets is associated with a different UE antenna port pair. Two sets are configured with one SRS resource in each set and one resource set is configured with two resources. In the case of four resource sets a total of four SRS resources transmitted in different symbols of four different slots, and where the SRS port pair of each SRS resource in the given four sets is associated with a different UE antenna port pair. Four sets are configured with one SRS resource in each set, or +- For 4T8R, zero or one or two SRS resource sets configured with a different value of *resourceType* in *SRS-ResourceSet* set to 'periodic' or 'semi-persistent' if the UE is not indicating *srs-AntennaSwitching2SP-1Periodic*, or up to two SRS resource sets configured with 'semi-persistent' and up to one SRS resource set configured with 'periodic' if the UE is indicating *srs-AntennaSwitching2SP-1Periodic*, where the two SRS resource sets configured with 'semi-persistent' are not activated at the same time. Each SRS resource set has two SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a four SRS ports, and the SRS ports of the resource in the set are associated with a different UE antenna ports, or +- For 4T8R, zero or one or two SRS resource sets configured with *resourceType* in *SRS-ResourceSet* set to 'aperiodic', where in the case of one resource set has two SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a four SRS ports, and the SRS ports of the resource in the set are associated with a different UE antenna ports. In the case of two resource sets a total of two SRS resources are transmitted in different symbols of two different slots, and where the SRS ports of each SRS resource in the given two sets are associated with a different UE antenna ports. + +The UE is configured with a guard period of *Y* symbols, in which the UE does not transmit any other signal, in the case the SRS resources of a set are transmitted in the same slot. The guard period is in-between the SRS resources of the set. For two SRS resource sets of an antenna switching located in two consecutive slots, if UE is capable of transmitting SRS in all symbols in one slot, a guard period of *Y* symbols exists between the last OFDM symbol occupied by the SRS resource set in the first slot and the first OFDM symbol occupied by the SRS resource set in the second slot. + +For the inter-set guard period, the UE does not transmit any other signal on any symbols of the interval if the interval between SRS resource sets is *Y* symbols. + +- When both the SRS resource on all of the corresponding symbols prior to the gap and the SRS resource on all of the corresponding symbols after the gap are dropped due to collision handling, the gap period is also dropped with same priority and can be used for UL transmission. + +The UE shall expect to be configured with the same number of SRS ports for all SRS resources in the SRS resource set(s) with higher layer parameter *usage* set as '*antennaSwitching*'. + +In the case that more than one SRS resource set configured with *resourceType* in *SRS-ResourceSet* set to 'aperiodic', the UE shall expect that the more than one set are configured with the same values of the higher layer parameters *alpha*, *p0*, *pathlossReferenceRS*, and *srs-PowerControlAdjustmentStates* in *SRS-ResourceSet*. + +For 1T2R, 1T4R, 2T4R, 1T6R, 1T8R, 2T6R, 2T8R, or 4T8R, the UE shall not expect to be configured or triggered with more than one SRS resource set with higher layer parameter *usage* set as '*antennaSwitching*' in the same slot. For 1T=1R, 2T=2R, 4T=4R, or 8T=8R, the UE shall not expect to be configured or triggered with more than one SRS resource set with higher layer parameter *usage* set as '*antennaSwitching*' in the same symbol. + +The value of *Y* is defined by Table 6.2.1.2-1. + +**Table 6.2.1.2-1: The minimum guard period between two SRS resources of an SRS resource set for antenna switching** + +| | | Y [symbol] | +|---|-----|-------------------| +| 0 | 15 | 1 | +| 1 | 30 | 1 | +| 2 | 60 | 1 | +| 3 | 120 | 2 | +| 5 | 480 | 7 | +| 6 | 960 | 14 | + +#### 6.2.1.3 UE sounding procedure between component carriers + +For a carrier of a serving cell *c1* with slot formats comprised of DL and UL symbols, not configured for PUSCH/PUCCH transmission, denote as the corresponding carrier of a serving cell whose UL transmissions are temporarily suspended as signalled by higher layer parameter *srs-SwitchFromServCellIndex* and *srs-SwitchFromCarrier*. Define the set as the set of carriers of serving cells that each carrier meets one of the following conditions: + +- is in the same band and same TAG as ; +- is a carrier of inter-band CA with and is indicated through the capability signalling *srs-SwitchingAffectedBandsListNR-r17* to be affected by the SRS switch from to ; + +where . + +A UE can be configured with SRS resource(s) on a carrier *c1* with slot formats comprised of DL and UL symbols and not configured for PUSCH/PUCCH transmission. For carrier *c1*, the UE is configured with higher layer parameter *srs-SwitchFromServCellIndex* and *srs-SwitchFromCarrier* the switching from carrier *c2* which is configured for PUSCH/PUCCH transmission. During SRS transmission on carrier *c1* (including any interruption due to uplink or downlink RF retuning time [11, TS 38.133] as defined by higher layer parameters *switchingTimeUL* and *switchingTimeDL* of *SRS-SwitchingTimeNR*), the UE temporarily suspends the uplink transmission on carriers in the set *S(c2)*. + +For an SRS transmission starting in symbol of carrier and a conflicting transmission in any carrier starting in symbol, the UE shall apply the prioritization / dropping rules in the remainder of this clause taking into account: + +- DCI(s) for which the time interval between the last symbol of PDCCH and is at least symbols and an additional time duration , and the time interval between the last symbol of PDCCH and is at least symbols; and +- semi-persistent CSI reports or SRS considered active at least symbols and an additional time duration before , and considered active at least symbols before . + +where , and the time interval unit of OFDM symbol is counted based on the smaller subcarrier spacing across any carrier within the set , and their corresponding scheduling cells. + +The following prioritization rules shall be applied in case of collision between a transmission of SRS over carrier and transmission of a physical signal/channel over a carrier of a serving cell in set + +- the UE shall not transmit SRS whenever SRS transmission (including any interruption due to uplink or downlink RF retuning time [11, TS 38.133] as defined by higher layer parameters *switchingTimeUL* and *switchingTimeDL* of *SRS-SwitchingTimeNR*) on the carrier of the serving cell and PUSCH/PUCCH transmission carrying HARQ-ACK/positive SR/RI/CRI/SSBRI and/or PRACH on a carrier of a serving cell in set happen to overlap in the same symbol +- the UE shall not transmit a periodic/semi-persistent SRS whenever periodic/semi-persistent SRS transmission (including any interruption due to uplink or downlink RF retuning time [11, TS 38.133] as defined by higher layer parameters *switchingTimeUL* and *switchingTimeDL* of *SRS-SwitchingTimeNR*) on the carrier of the serving cell and PUSCH transmission carrying aperiodic CSI on a carrier of a serving cell in set happen to overlap in the same symbol +- the UE shall drop PUCCH/PUSCH transmission carrying periodic/semi-persistent CSI comprising only CQI/PMI/L1-RSRP/L1-SINR, and/or SRS transmission on a carrier of a serving cell in set configured for PUSCH/PUCCH transmission whenever the transmission and SRS transmission (including any interruption due to uplink or downlink RF retuning time [11, TS 38.133] as defined by higher layer parameters *switchingTimeUL* and *switchingTimeDL* of *SRS-SwitchingTimeNR*) on the carrier of the serving cell happen to overlap in the same symbol +- the UE shall drop PUSCH transmission carrying aperiodic CSI comprising only CQI/PMI/L1-RSRP/L1-SINR on a carrier of a serving cell in set whenever the transmission and aperiodic SRS transmission (including any interruption due to uplink or downlink RF retuning time [11, TS 38.133]) as defined by higher layer parameters *switchingTimeUL* and *switchingTimeDL* of *SRS-SwitchingTimeNR*) on the carrier of the serving cell happen to overlap in the same symbol. + +For an aperiodic SRS triggered in DCI format 2\_3 and if the UE is configured with higher layer parameter *srs-TPC-PDCCH-Group* set to 'typeA', and given by *SRS-CarrierSwitching*, without PUSCH/PUCCH transmission, the UE in each serving cell transmits the configured one or two SRS resource set(s) from *srs-ResourceSetToAddModList* with higher layer parameter *usage* set to 'antennaSwitching' and higher layer parameter *resourceType* in *SRS-ResourceSet* set to 'aperiodic'. + +For an aperiodic SRS triggered in DCI format 2\_3 and if the UE is configured with higher layer parameter *srs-TPC-PDCCH-Group* set to 'typeB' without PUSCH/PUCCH transmission, the UE in each serving cell transmits the configured one or two SRS resource set(s) from *srs-ResourceSetToAddModList* with higher layer parameter *usage* set to 'antennaSwitching' and higher layer parameter *resourceType* in *SRS-ResourceSet* set to 'aperiodic'. + +For an aperiodic SRS triggered in DCI format 1\_1 or 1\_2, if the UE is configured by *SRS-CarrierSwitching*, it transmits SRS on one serving cell not configured for PUSCH/PUCCH transmission scheduled by the DCI and the UE in the serving cell transmits the configured one or two SRS resource set(s) with higher layer parameter *usage* set to 'antennaSwitching' and higher layer parameter *resourceType* in *SRS-ResourceSet* set to 'aperiodic'. + +If the UE is not configured for PUSCH/PUCCH transmission on carrier $c_1$ with slot formats comprised of DL and UL symbols, and if the UE is not capable of simultaneous reception and transmission on carrier $c_1$ and serving cell $c_2$ , the UE is not expected to be configured or indicated with SRS resource(s) such that SRS transmission on carrier $c_1$ (including any interruption due to uplink or downlink RF retuning time [11, TS 38.133] as defined by higher layer parameters *switchingTimeUL* and *switchingTimeDL* of *SRS-SwitchingTimeNR*) would collide with the REs corresponding to the SS/PBCH blocks configured for the UE or the slots belonging to a control resource set indicated by *MIB* or *SIB1* on serving cell $c_2$ . + +For $n$ -th ( $n \geq 1$ ) aperiodic SRS transmission on a cell $c$ , upon detection of a positive SRS request on a grant, the UE shall commence this SRS transmission on the configured symbol and slot provided + +- it is no earlier than the summation of + - the maximum time duration between the two durations spanned by N OFDM symbols of the numerology of cell $c$ and the cell carrying the grant respectively, and + - the UL or DL RF retuning time [11, TS 38.133] as defined by higher layer parameters *switchingTimeUL* and *switchingTimeDL* of *SRS-SwitchingTimeNR*, + +- it does not collide with any previous SRS transmissions, or interruption due to UL or DL RF retuning time, except if the previous SRS transmission is in the same cell $c$ and the UE reports *SRS-StayInTargetCC* for the corresponding band combination. + +otherwise, $n$ -th SRS transmission is dropped, where $N$ is the reported capability as the minimum time interval in unit of symbols, between the DCI triggering and aperiodic SRS transmission. + +In case of inter-band carrier aggregation, a UE can simultaneously transmit SRS and PUCCH/PUSCH across component carriers in different bands subject to the UE's capability. + +In case of inter-band carrier aggregation, a UE can simultaneously transmit PRACH and SRS across component carriers in different bands subject to UE's capability. + +If the UE is not configured for PUSCH/PUCCH transmission for at least one serving cell configured with slot formats comprised of DL and UL symbols, and if the UE is not capable of simultaneous reception and transmission on serving cell $c_1$ and serving cell $s(c_2)$ , and if a UE + +- is configured with multiple serving cells and is provided with *directionalCollisionHandling-r16* = 'enabled' for a set of serving cell(s) among the configured multiple serving cells including serving cell $c_1$ and $s(c_2)$ , and +- indicates support of *half-DuplexTDD-CA-SameSCS-r16* capability, and +- is not configured to monitor PDCCH for detection of DCI format 2\_0 on any of the multiple serving cells, + +the UE shall apply first the prioritization/dropping rules described above for sounding procedure between component carriers and then apply the procedures for directional collision handling in clause 11.1 of [6, TS 38.213]. + +#### 6.2.1.4 UE sounding procedure for positioning purposes + +When the SRS is configured by the higher layer parameter *SRS-PosResource* and if the higher layer parameter *spatialRelationInfoPos* is configured, it contains the ID of the configuration fields of a reference RS according to Clause 6.3.2 of [TS 38.331]. The reference RS can be an SRS configured by the higher layer parameter *SRS-Resource* or *SRS-PosResource*, CSI-RS, SS/PBCH block, or a DL PRS configured on a serving cell or a SS/PBCH block or a DL PRS configured on a non-serving cell. If the UE is configured for transmission of *SRS-PosResource* in RRC\_INACTIVE mode, the configured *spatialRelationInfoPos* is also applicable. + +The UE is not expected to transmit multiple SRS resources with different spatial relations in the same OFDM symbol. + +If the UE is not configured with the higher layer parameter *spatialRelationInfoPos* the UE may use a fixed spatial domain transmission filter for transmissions of the SRS configured by the higher layer parameter *SRS-PosResource* across multiple SRS resources or it may use a different spatial domain transmission filter across multiple SRS resources. + +In RRC\_CONNECTED mode, the UE is only expected to transmit an SRS configured by the higher layer parameter *SRS-PosResource* within the active UL BWP of the UE. + +When the configuration of SRS is done by the higher layer parameter *SRS-PosResource*, the UE can only be provided with a single RS source in *spatialRelationInfoPos* per SRS resource for positioning. + +For operation on the same carrier, if an SRS configured by the higher parameter *SRS-PosResource* collides with a scheduled PUSCH, the SRS is dropped in the symbols where the collision occurs. + +Unless specified otherwise, the UE does not expect to be configured with *SRS-PosResource* on a carrier of a serving cell with slot formats comprised of DL and UL symbols, not configured for PUSCH/PUCCH transmission. + +Timing Error Group (TEG) at UE side is defined: + +- UE Tx TEG is associated with the transmissions of one or more UL SRS resources for the positioning purpose, which have the Tx timing error difference within a certain margin. + +The UE may be configured to report, via high layer parameter *nr-UE-RxTxTEG-Request* or *ue-TxTEG-RequestUL-TDOA-Config*, subject to UE capability, association information of the already transmitted SRS resource(s) configured by the higher layer parameter *SRS-PosResource* with UE Tx TEG(s) via higher layer parameter *nr-SRS-TxTEG-Set* or *ue-TxTEG-AssociationList*. + +The UE may report, via high layer parameter *ue-TxTEG-TimingErrorMarginValue*, the UE Tx TEG timing error margin value of all the UE Tx TEGs within one *UEPositioningAssistanceInfo*. + +If the UE reports a UE Tx TEG ID with a UE Rx-Tx time difference measurement, as defined in clause 5.1.6.5, the UE shall report the association information of the already transmitted SRS resources configured by the higher layer parameter *SRS-PosResource* with the UE Tx TEG ID. + +If the UE is configured with SRS resources configured by the higher layer parameter *SRS-PosResource* in multiple CCs, the UE should report the *carrierFreq* or *servCellId* of the SRS resources when it reports the UE Tx TEG associations. + +If the UE reports a UE RxTx TEG ID with a UE Rx-Tx time difference measurement, the UE may report a UE Tx TEG ID. + +If the UE reports a UE Tx TEG ID with a UE Rx-Tx time difference measurement, the UE may report a UE Tx TEG timing error margin value, via high layer parameter *nr-UE-TxTEG-TimingErrorMargin*, for all the UE Tx TEGs within one *NR-Multi-RTT-SignalMeasurementInformation*. + +Subject to UE capability, the UE may be configured with an SRS resource for positioning associated with the initial UL BWP, and the SRS resource is transmitted inside the initial UL BWP during RRC\_INACTIVE mode with the same CP and subcarrier spacing as configured for the initial UL BWP. Subject to UE capability, the UE may be configured with an SRS resource for positioning outside the initial BWP including frequency location and bandwidth, subcarrier spacing, and CP length for transmission of the SRS in RRC\_INACTIVE mode. If the transmission of SRS for positioning outside the initial BWP in RRC\_INACTIVE mode along with the switching time, indicated in higher layer parameter *switchingTimeSRS-TX-OtherTX*, in unpaired spectrum, subject to UE capability, collides in time domain with other DL signals or channels or UL signals or channels, the SRS for positioning transmission is dropped in the symbol(s) where the collision occurs. If a SRS symbol for positioning outside the initial BWP in RRC\_INACTIVE mode including the switching time, indicated in higher layer parameter *switchingTimeSRS-TX-OtherTX*, in paired spectrum or SUL band, subject to UE capability, collides in time domain with UL signals or channels on the same carrier, the colliding SRS symbol for positioning is dropped. The SRS resource for positioning outside the initial BWP in RRC\_INACTIVE mode is configured in the same band and CC as the initial UL BWP. + +If the UE in RRC\_INACTIVE mode is not provided [*SRS-PosRRC-InactiveConfig-ValidityArea*] and determines that the UE is not able to accurately measure the configured DL RS in *SRS-SpatialRelationInfoPos* for a SRS resource for positioning where the DL RS is semi-persistent or periodic, the UE stops transmission of the SRS resource for positioning. + +The UE is not expected to simultaneously transmit SRS resources configured by the higher layer parameter *SRS-PosResource* on NUL and SUL band in RRC\_INACTIVE mode. + +The UE may be configured with SRS, via [*SRS-PosRRC-InactiveConfig-ValidityArea*], subject to UE capability, valid in multiple cells within a validity area for RRC\_INACTIVE mode. For the configured SRS via [*SRS-PosRRC-InactiveConfig-ValidityArea*], if the UE in RRC\_INACTIVE mode determines that the UE is not able to accurately measure the configured DL RS in [*SRS-SpatialRelationInfoPos*] for a SRS resource for positioning where the DL RS is semi-persistent or periodic, the UE would not perform SRS transmission of the SRS resource for positioning. If the UE determines that the configured DL RS in [*SRS-SpatialRelationInfoPos*] for a SRS resource for positioning is being accurately measured, the UE is expected to perform the SRS transmission. + +##### 6.2.1.4.1 SRS frequency hopping for positioning + +The reduced capability UE may be configured via [*higher layer parameter*], subject to UE capability, to perform transmit frequency hopping separate from the UL BWP configuration and outside of the UL BWP, where the UE may be configured with subcarrier spacing, CP and bandwidth that are different from the UL active BWP. The reduced capability UE transmit frequency hopping is configured within one SRS resource for positioning, that may be configured with a bandwidth larger than the maximum bandwidth of the reduced capability UE, in RRC\_CONNECTED or RRC\_INACTIVE mode. The reduced capability UE transmit frequency hopping, may be configured with overlapping or non-overlapping frequency hops in the frequency domain. When the reduced capability UE is configured to perform transmit frequency hopping: + +- it expects to be configured with the following parameters: + - starting PRB of the first hop in time domain in [*higher layer parameter*] + - starting slot offset and starting symbol for each hop in [*higher layer parameter*] + +- number of symbols in each hop in [higher layer parameter] +- hop bandwidth in [higher layer parameter] +- number of overlapping resource block(s) between hops, if present, in [higher layer parameter] +- number of hops in [higher layer parameter]. +- it does not expect to be configured with the sum of *[StartingSymbol]* and *[Length]* for a hop that exceeds a slot duration. +- it expects to be configured with the same periodicity of each hop of an SRS resource with the transmit frequency hopping. + +The reduced capability UE may be configured, via *[uplinkTimeWindow-Config]*, subject to UE capability, with an UL time window where the UE is not expected to transmit other signals/channels and is only expected to transmit the SRS for positioning using frequency hopping. The UE is not expected to be configured with one [cycle] of the transmit frequency hopping, including the switching time from/to active BWP required ahead of the first hop and after the last hop, that is partially overlapped with the time window. + +The reduced capability UE is expected to switch back to the active BWP if the time between two consecutive hops exceeds twice the switching time from/to the active BWP. + +For a transmission of a hop for an SRS resource for positioning with frequency hopping starting in symbol *x* and a colliding PUSCH or PUCCH transmission starting in symbol *y*, the UE shall apply the dropping rules taking into account: + +- DCI(s) for which the time interval between the last symbol of PDCCH and the SRS symbol is at least *x* symbols and additional time duration *y*, where *y* is the switching time to/from the active BWP. +- DCI(s) for which the time interval between the last symbol of PDCCH and the colliding PUSCH/PUCCH symbol is at least *x* symbols, where calculation of *y* is based on the smallest SCS between the SCS configured for positioning SRS with the frequency hopping, the SCS of the PUSCH, and the SCS of the PDCCH. + +If the SRS symbol(s), including the switching time to and from the active bandwidth part, of the transmit frequency hopping collides with PUSCH or PUCCH, and if the UE determines the SRS to be dropped, the colliding SRS symbol(s) are dropped. + +For operation in the same carrier, the reduced capability UE is not expected to be configured on overlapping symbols with an SRS resource of the transmit frequency hopping configured by the higher layer parameter *[to\_be\_defined]* including the switching time to or from the active bandwidth part and an SRS resource with *resourceType* of both SRS resources as 'periodic'. + +For operation in the same carrier, the reduced capability UE is not expected to be activated or triggered to transmit SRS on overlapping symbols with a SRS resource of the transmit frequency hopping configured by the higher layer parameter *[XX]* including the switching time to or from the active bandwidth part and a SRS resource with *resourceType* of both SRS resources as 'semi-persistent' or 'aperiodic'. + +##### 6.2.1.4.2 SRS bandwidth aggregation for positioning measurements + +The UE is expected to be configured with linkage information *[linked-SRSPosResourceSetIdList-SrsAggregation]* on SRS resource sets for positioning across two or three CCs which are linked for bandwidth aggregation. For the linked SRS resource sets, the UE is expected to be configured with the same values of *startPosition*, *nrofSymbols*, *periodicityAndOffset*, *slotOffset*, *alpha*, *p0*, subcarrier spacing, CP, and comb size, and the UE is expected to maintain phase continuity for the SRS transmission. The UE assumes that SRS resources across the linked SRS resource sets which satisfy the above conditions are linked for bandwidth aggregation, otherwise, the UE does not assume that SRS resources of the linked SRS resource sets are linked for bandwidth aggregation. For the linked SRS resource sets for bandwidth aggregation across CCs, if an SRS configured by the higher layer parameter *SRS-PosResource*, along with the *[switching period]* when applicable, collides with other signals or channels on a symbol and if the SRS in that symbol is dropped, SRS transmission of the linked SRS resource sets across all CCs is dropped on that symbol. + +If the UE is configured with *[srs-PosBWAggregationDCITriggering]*, and if the UE receives a DCI 0\_1, 0\_2, 1\_1, or 1\_2 triggering an aperiodic SRS resource set for positioning linked for bandwidth aggregation in a CC, subject to UE capability, UE transmits SRS of the linked SRS resource sets across all CCs. + +A UE in RRC\_INACTIVE mode is expected to be configured with [frequency information] on additional component carrier(s) with respective SRS configuration(s) for bandwidth aggregation. + +When an SRS resource configured in a CC without PUSCH or PUCCH is linked for bandwidth aggregation with an SRS resource configured in an active UL BWP of another [UL data transmission] CC, there is a [guard period] during which the UE is not expected to transmit or receive other signals or channels. + +If the UE receives an activation or deactivation command of semi-persistent SRS resource set(s) for positioning in up to three aggregated carriers or SRS resource set(s) for positioning in up to two aggregated carriers as specified in [10, TS 38.321] and when the UE would transmit a PUCCH with HARQ-ACK information in slot $n$ corresponding to the PDSCH carrying the activation or deactivation command, the corresponding actions in [10, TS 38.321] and the UE assumptions on SRS transmission or cessation corresponding to the SRS resource set(s) shall be applied starting from the first slot that is after slot $n$ where $\mu$ is the SCS configuration for the PUCCH. + +### 6.2.2 UE DM-RS transmission procedure + +The DM-RS transmission procedures for PUSCH scheduled by PDCCH with DCI format 0\_1 described in this clause equally apply to PUSCH scheduled by PDCCH with DCI format 0\_2, by applying the parameters of *dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2* and *dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2* instead of *dmrs-UplinkForPUSCH-MappingTypeA* and *dmrs-UplinkForPUSCH-MappingTypeB*. The DM-RS transmission procedures for PUSCH scheduled by PDCCH with DCI format 0\_1 described in this clause equally apply to PUSCH scheduled by PDCCH with DCI format 0\_3. + +When transmitted PUSCH is neither scheduled by DCI format 0\_1/0\_2 with CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI or MCS-C-RNTI, nor corresponding to a configured grant, nor being a PUSCH for Type-2 random access procedure, the UE shall use single symbol front-loaded DM-RS of configuration type 1 on DM-RS port 0 and the remaining REs not used for DM-RS in the symbols are not used for any PUSCH transmission except for PUSCH with allocation duration of 2 or less OFDM symbols with transform precoding disabled, additional DM-RS can be transmitted according to the scheduling type and the PUSCH duration as specified in Table 6.4.1.1.3-3 of [4, TS38.211] for frequency hopping disabled and as specified in Table 6.4.1.1.3-6 of [4, TS38.211] for frequency hopping enabled, and + +If frequency hopping is disabled: + +- The UE shall assume *dmrs-AdditionalPosition* equals to 'pos2' and up to two additional DM-RS can be transmitted according to PUSCH duration, or + +If frequency hopping is enabled: + +- The UE shall assume *dmrs-AdditionalPosition* equals to 'pos1' and up to one additional DM-RS can be transmitted according to PUSCH duration. + +When transmitted PUSCH is scheduled by activation DCI format 0\_0 with CRC scrambled by CS-RNTI, the UE shall use single symbol front-loaded DM-RS of configuration type provided by higher layer parameter *dmrs-Type* in *DMRS-UplinkConfig* on DM-RS port 0 and the remaining REs not used for DM-RS in the symbols are not used for any PUSCH transmission except for PUSCH with allocation duration of 2 or less OFDM symbols with transform precoding disabled, and additional DM-RS with *dmrs-AdditionalPosition* from *ConfiguredGrantConfig* can be transmitted according to the scheduling type and the PUSCH duration as specified in Table 6.4.1.1.3-3 of [4, TS38.211] for frequency hopping disabled and as specified in Table 6.4.1.1.3-6 of [4, TS38.211] for frequency hopping enabled. + +For the UE-specific reference signals generation as defined in Clause 6.4.1.1 of [4, TS 38.211], a UE can be configured by higher layers with one or two scrambling identity(ies), $i = 0, 1$ which are the same for both PUSCH mapping Type A and Type B. + +When transmitted PUSCH is scheduled by DCI format 0\_1 with CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI or MCS-C-RNTI, or corresponding to a configured grant, or being a PUSCH for Type-2 random access procedure, + +- for a configured-grant based PUSCH transmission in RRC\_INACTIVE state, the UE is provided with a set of DM-RS port(s) by *sdt-DMRS-Ports*. The DM-RS port for the PUSCH is determined by the mapping between SS/PBCH block(s) and a PUSCH occasion and the associated DM-RS resource as described in Clause 19.1 of [6, TS 38.213]. +- the UE may be configured with higher layer parameter *dmrs-Type* in *DMRS-UplinkConfig*, and the configured DM-RS configuration type is used for transmitting PUSCH in as defined in Clause 6.4.1.1 of [4, TS 38.211]. + +- the UE may be configured with the maximum number of front-loaded DM-RS symbols for PUSCH by higher layer parameter *maxLength* in *DMRS-UplinkConfig*, or by higher layer parameter *msgA-MaxLength* in *msgA-DMRS-Config*, +- if *maxLength* is not configured, single-symbol DM-RS can be scheduled for the UE by DCI or configured by the configured grant configuration, and the UE can be configured with a number of additional DM-RS for PUSCH by higher layer parameter *dmrs-AdditionalPosition*, which can be 'pos0', 'pos1', 'pos2', 'pos3'. +- if *maxLength* is configured, either single-symbol DM-RS or double symbol DM-RS can be scheduled for the UE by DCI or configured by the configured grant configuration, and the UE can be configured with a number of additional DM-RS for PUSCH by higher layer parameter *dmrs-AdditionalPosition*, which can be 'pos0' or 'pos1'. +- for MsgA PUSCH for Type-2 random access procedure the UE can be configured with a number of additional DM-RS for PUSCH by higher layer parameter *msgA-DMRS-AdditionalPosition*, which can be 'pos0', 'pos1', 'pos2', 'pos3' for single-symbol DM-RS or 'pos0', 'pos1' for double-symbol DM-RS. +- and, the UE shall transmit a number of additional DM-RS as specified in Table 6.4.1.1.3-3 and Table 6.4.1.1.3-4 in -Clause 6.4.1.1.3 of [4, TS 38.211]. + +If a UE transmitting PUSCH scheduled by DCI format 0\_2 is configured with the higher layer parameter *phaseTrackingRS* in *dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2* or *dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2*, or a UE transmitting PUSCH scheduled by DCI format 0\_0, 0\_1 or 0\_3 is configured with the higher layer parameter *phaseTrackingRS* in *dmrs-UplinkForPUSCH-MappingTypeA* or *dmrs-UplinkForPUSCH-MappingTypeB*, the UE may assume that the following configurations are not occurring simultaneously for the transmitted PUSCH + +- any DM-RS ports among + - 4-7 or 6-11 for DM-RS configurations type 1 and type 2, respectively, or + - 4-7 or 12-15 for DM-RS configuration enhanced type 1, or + - 6-11 or 18-23 for DM-RS configuration enhanced type 2, + +are scheduled for the UE and PT-RS is transmitted from the UE. + +For PUSCH scheduled by DCI format 0\_1, by activation DCI format 0\_1 with CRC scrambled by CS-RNTI, or configured by configured grant Type 1 configuration, the UE shall assume the DM-RS CDM groups indicated in Tables 7.3.1.1.2-6 to 7.3.1.1.2-23D and Tables 7.3.1.1.2-38 to 7.3.1.1.2-69 of Clause 7.3.1.1 of [5, TS38.212] are not used for data transmission, where "1", "2" and "3" for the number of DM-RS CDM group(s) correspond to CDM group 0, {0,1}, {0,1,2}, respectively. + +For PUSCH scheduled by DCI format 0\_0 or by activation DCI format 0\_0 with CRC scrambled by CS-RNTI, the UE shall assume the number of DM-RS CDM groups without data is 1 which corresponds to CDM group 0 for the case of PUSCH with allocation duration of 2 or less OFDM symbols with transform precoding disabled, the UE shall assume that the number of DM-RS CDM groups without data is 3 which corresponds to CDM group {0,1,2} for the case of PUSCH scheduled by activation DCI format 0\_0 and the *dmrs-Type* in *DMRS-UplinkConfig* equal to 'type2' and the PUSCH allocation duration being more than 2 OFDM symbols, and the UE shall assume that the number of DM-RS CDM groups without data is 2 which corresponds to CDM group {0,1} for all other cases. + +For MsgA PUSCH transmission, if the UE is not configured with *msgA-PUSCH-DMRS-CDM-group*, the UE shall assume that 2 DM-RS CDM groups are configured. Otherwise, *msgA-PUSCH-DMRS-CDM-group* indicates which DM-RS CDM group to use from the set of {0,1}. + +For MsgA PUSCH transmission, if the UE is not configured with *msgA-PUSCH-NrofPorts*, the UE shall assume that 4 ports are configured per DM-RS CDM group for double-symbol DM-RS. Otherwise, *msgA-PUSCH-NrofPorts* with value of 0 indicates the first port per DM-RS CDM group, while a value of 1 indicates the first two ports per DM-RS CDM group. + +For uplink DM-RS with PUSCH, the UE may assume the ratio of PUSCH EPRE to DM-RS EPRE ( [dB]) is given by + +Table 6.2.2-1 according to the number of DM-RS CDM groups without data. The DM-RS scaling factor $\beta_{PUSCH}^{DMRS}$ specified in clause 6.4.1.1.3 of [4, TS 38.211] is given by $\beta_{PUSCH}^{DMRS} = 10^{-\frac{\beta_{DMRS}}{20}}$ . + +**Table 6.2.2-1: The ratio of PUSCH EPRE to DM-RS EPRE** + +| Number of DM-RS CDM groups without data | DM-RS configuration type 1 and enhanced type 1 | DM-RS configuration type 2 and enhanced type 2 | +|-----------------------------------------|------------------------------------------------|------------------------------------------------| +| 1 | 0 dB | 0 dB | +| 2 | -3 dB | -3 dB | +| 3 | - | -4.77 dB | + +For PUSCH repetition Type B, the DM-RS transmission procedure is applied for each actual repetition separately based on the allocation duration of the actual repetition. A UE is not expected to be indicated with an antenna port configuration that is invalid for the allocated duration of any actual repetition. + +### 6.2.3 UE PT-RS transmission procedure + +The procedures on PT-RS transmission described in this clause as well as clauses 6.2.3.1 and 6.2.3.2 apply to a UE PUSCH transmission scheduled by DCI format 0\_2 if the higher layer parameter *phaseTrackingRS* in *dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2* or *dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2* is configured, to PUSCH transmissions scheduled by DCI format 0\_0, 0\_1 or 0\_3 if the higher layer parameter *phaseTrackingRS* in *dmrs-UplinkForPUSCH-MappingTypeA* or *dmrs-UplinkForPUSCH-MappingTypeB* is configured and PUSCH transmissions corresponding to a configured grant if the higher layer parameter *phaseTrackingRS* in *cgr-DMRS-Configuration* is configured. If a UE is not configured with the higher layer parameter *phaseTrackingRS* in the respective *DMRS-UplinkConfig*, the UE shall not transmit PT-RS. The PT-RS is only present on PUSCH scheduled by PDCCH with CRC scrambled by MCS-C-RNTI, C-RNTI, CS-RNTI, SP-CSI-RNTI and on PUSCH corresponding to a configured grant. For PUSCH repetition Type B, the PT-RS transmission procedure is applied for each actual repetition separately based on the allocation duration of the actual repetition. + +#### 6.2.3.1 UE PT-RS transmission procedure when transform precoding is not enabled + +When transform precoding is not enabled and if a UE is configured with the higher layer parameter *phaseTrackingRS* in *DMRS-UplinkConfig*, + +- the higher layer parameters *timeDensity* and *frequencyDensity* in *PTRS-UplinkConfig* indicate the threshold values *ptrs-MCSi*, *i*=1,2,3 and *NRB,i*, *i*=0,1, as shown in Table 6.2.3.1-1 and Table 6.2.3.1-2, respectively. +- if either or both higher layer parameters *timeDensity* and/or *frequencyDensity* in *PTRS-UplinkConfig* are configured, the UE shall assume the PT-RS antenna ports' presence and pattern are a function of the corresponding scheduled MCS of the codeword associated with the PT-RS and scheduled bandwidth in a corresponding bandwidth part as shown in Table 6.2.3.1-1 and Table 6.2.3.1-2, respectively, + - if the higher layer parameter *timeDensity* is not configured, the UE shall assume *LPT-RS* = 1. + - if the higher layer parameter *frequencyDensity* is not configured, the UE shall assume *KPT-RS* = 2. +- if none of the higher layer parameters *timeDensity* and *frequencyDensity* in *PTRS-UplinkConfig* are configured, the UE shall assume *LPT-RS* = 1 and *KPT-RS* = 2. + +**Table 6.2.3.1-1: Time density of PT-RS as a function of scheduled MCS** + +| Scheduled MCS | Time density() | +|------------------------------------------------------------------------------------|----------------------| +| IMCS < ptrs-MCS1 | PT-RS is not present | +| ptrs-MCS1 ≤ IMCS < ptrs-MCS2 | 4 | +| ptrs-MCS2 ≤ IMCS < ptrs-MCS3 | 2 | +| ptrs-MCS3 ≤ IMCS < ptrs-MCS4 | 1 | + +**Table 6.2.3.1-2: Frequency density of PT-RS as a function of scheduled bandwidth** + +| Scheduled bandwidth | Frequency density () | +|-------------------------------------------------------------------------|----------------------| +| NRB < NRB0 | PT-RS is not present | +| NRB0 ≤ NRB < NRB1 | 2 | +| NRB1 ≤ NRB | 4 | + +The higher layer parameter *PTRS-UplinkConfig* provides the parameters *ptrs-MCSi*, *i*=1,2,3 and with values in 0-29 when MCS Table 5.1.3.1-1 or Table 5.1.3.1-3 is used and 0-28 when MCS Table 5.1.3.1-2 is used, respectively. *ptrs-MCS4* is not explicitly configured by higher layers but assumed 29 when MCS Table 5.1.3.1-1 or Table 5.1.3.1-3 is used and 28 when MCS Table 5.1.3.1-2 is used. The higher layer parameter *PTRS-UplinkConfig* provides the parameters *NRB,i* *i*=0,1 with values in range 1-276. + +If the higher layer parameter *PTRS-UplinkConfig* indicates that the time density thresholds *ptrs-MCSi* = *ptrs-MCSi+1*, then the time density *LPT-RS* of the associated row where both these thresholds appear in Table 6.2.3.1-1 is disabled. If the higher layer parameter *frequencyDensity* in *PTRS-UplinkConfig* indicates that the frequency density thresholds *NRB,i* = *NRB,i+1*, then the frequency density *KPT-RS* of the associated row where both these thresholds appear in Table 6.2.3.1-2 is disabled. + +If either or both of the parameters PT-RS time density (*LPT-RS*) and PT-RS frequency density (*KPT-RS*), shown in Table 6.2.3.1-1 and Table 6.2.3.1-2, indicates that are configured as 'PT-RS not present', the UE shall assume that PT-RS is not present. + +When a UE is scheduled to transmit PUSCH with allocation duration of 2 symbols or less, and if *LPT-RS* is set to 2 or 4, the UE shall not transmit PT-RS. When a UE is scheduled to transmit PUSCH with allocation duration of 4 symbols or less, and if *LPT-RS* is set to 4, the UE shall not transmit PT-RS. + +When a UE is scheduled to transmit PUSCH for retransmission, if the UE is scheduled with *IMCS* > *V*, where *V* = 28 for MCS Table 5.1.3.1-1 and MCS Table 5.1.3.1-3 and *V* = 27 for MCS Table 5.1.3.1-2, respectively, the MCS for PT-RS time-density determination is obtained from the DCI for the same transport block in the initial transmission, which is smaller than or equal to *V*. + +If a UE is configured with the higher layer parameter *maxNrofPorts* in *PTRS-UplinkConfig* set to 'n2' and scheduled with two codewords, the PT-RS time-density for both PT-RS ports is determined based on the higher MCSs of two codewords associated with the initial transmission. + +The maximum number of configured PT-RS ports is given by the higher layer parameter *maxNrofPorts* in *PTRS-UplinkConfig*. The UE is not expected to be configured with a larger number of UL PT-RS ports than it has reported need for. + +If a UE has reported the capability of supporting full-coherent UL transmission, the UE shall expect *maxNrofPorts* in *PTRS-UplinkConfig* to be configured as one if ULPT-RS is configured. If a UE has reported the capability of supporting full-coherent UL transmission and when the higher layer parameter *multipanelScheme* is set to 'sdmscheme', subject to UE capability, the UE can be configured with *maxNrofPortsforSDM* in *PTRS-UplinkConfig* set to n2, where at most one PT-RS port is associated with each SRS resource set with higher layer parameter *usage* set to 'codebook'/'nonCodebook'. + +For codebook or non-codebook based UL transmission, the association between UL PT-RS port(s) and DM-RS port(s) is signalled by *PTRS-DMRS association* field(s) in DCI format 0\_1, 0\_2 and 0\_3. For a PUSCH corresponding to a configured grant Type 1 transmission, the UE may assume the association between UL PT-RS port(s) and DM-RS port(s) defined by value 0 in Table 7.3.1.1.2-25, or value "00" in Table 7.3.1.1.1.2-26 or value "00" in Table 7.3.1.1.1.2-25a described in Clause 7.3.1 of [5, TS38.212]. + +For PUSCH scheduled by DCI format 0\_0 or by activation DCI format 0\_0, the UL PT-RS port is associated to DM-RS port 0. + +For non-codebook based UL transmission, the actual number of UL PT-RS port(s) to transmit is determined based on SRI(s) in DCI format 0\_1, 0\_2 or 0\_3 or higher layer parameter *sri-ResourceIndicator* in *rrc-ConfiguredUplinkGrant*. When two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'noncodebook', the actual number of UL PT-RS port(s) to transmit corresponding to each SRS resource set is determined based on SRI(s) corresponding to the associated SRS resource set or higher layer parameter *sri-ResourceIndicator* or *sri-ResourceIndicator2* corresponding to the associated SRS resource set in *rrc-ConfiguredUplinkGrant*. A UE is configured with the PT-RS port index for each configured SRS resource by the higher layer parameter *ptrs-PortIndex* configured by *SRS-Config* if the UE is configured with the higher layer parameter *phaseTrackingRS* in *DMRS-UplinkConfig*. If the PT-RS port index associated with different SRIs are the same, the corresponding UL DM-RS ports are associated to the one UL PT-RS port. + +When the higher layer parameter *multipanelScheme* is set to 'sdmscheme' and two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook'/'nonCodebook' and higher layer parameter *maxNrofPortsforSDM* in *PTRS-UplinkConfig* set to n2, the actual number of UL PT-RS port(s) to transmit corresponding to SRS resource sets is 2. + +When the higher layer parameter *multipanelScheme* is set to 'SFNscheme' and two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook'/'nonCodebook' and the higher layer parameter *maxNrofPorts* in *PTRS-UplinkConfig* is set to *n2*, the actual number of UL PT-RS port(s) to transmit corresponding to each SRS resource set is determined based on 1st TPMI codepoint field for 'codebook' or 1st SRI(s) codepoint field for 'nonCodebook'. + +For partial-coherent and non-coherent codebook-based UL transmission, the actual number of UL PT-RS port(s) is determined based on TPMI(s) and/or number of layers which are indicated by '*Precoding information and number of layers*' field(s) in DCI format 0\_1, 0\_2 or 0\_3 or configured by higher layer parameter *precodingAndNumberOfLayers*: + +- if the UE is configured with the higher layer parameter *maxNrofPorts* in *PTRS-UplinkConfig* set to 'n2', the actual UL PT-RS port(s) and the associated transmission layer(s) are derived from indicated TPMI(s) as: +- for PUSCH transmission with 2 or 4 ports, PUSCH antenna port 1000 and 1002 in indicated TPMI(s) share PT-RS port 0, and PUSCH antenna port 1001 and 1003 in indicated TPMI(s) share PT-RS port 1. +- UL PT-RS port 0 is associated with the UL layer 'x' of layers which are transmitted with PUSCH antenna port 1000 and PUSCH antenna port 1002 in indicated TPMI(s), and UL PT-RS port 1 is associated with the UL layer 'y' of layers which are transmitted with PUSCH antenna port 1001 and PUSCH antenna port 1003 in indicated TPMI(s), where 'x' and/or 'y' are given by DCI parameter '*PTRS-DMRS association*' as shown in DCI format 0\_1, 0\_2 and 0\_3 described in Clause 7.3.1 of [5, TS38.212]. +- for PUSCH transmission with 8 ports, PUSCH antenna port 1000, 1001, 1004 and 1005 in indicated TPMI(s) share PT-RS port 0, and PUSCH antenna port 1002, 1003, 1006 and 1007 in indicated TPMI(s) share PT-RS port 1. +- UL PT-RS port 0 is associated with the UL layer 'x' of layers which are transmitted with one or more of PUSCH antenna port 1000, 1001, 1004 and 1005 in indicated TPMI(s), and UL PT-RS port 1 is associated with the UL layer 'y' of layers which are transmitted with one or more of PUSCH antenna port 1002, 1003, 1006 and 1007 in indicated TPMI(s), where 'x' and/or 'y' are given by DCI parameter '*PTRS-DMRS association*' as shown in DCI format 0\_1 and DCI format 0\_2 described in Clause 7.3.1 of [5, TS38.212]. + +If a UE is scheduled with two codewords, + +- if the UE is configured with the higher layer parameter *maxNrofPorts* in *PTRS-UplinkConfig* set to 'n1', the PT-RS port is associated with the one of DM-RS ports indicated by DCI field *PTRS-DMRS association* for the codeword with the higher MCS. If the MCS indices of the two codewords are the same, the PT-RS antenna port is associated with codeword 0. When a codeword is scheduled to transmit PUSCH for retransmission, the MCS for determining PT-RS association to codeword is obtained from the DCI for the same transport block in the initial transmission. + +When the UE is scheduled with $Q_p=\{1,2\}$ PT-RS port(s) in uplink and the number of scheduled layers is , + +- If the UE is configured with higher layer parameter *ptrs-Power*, the PUSCH to PT-RS power ratio per layer per RE is given by , where is shown in the Table 6.2.3.1-3, Table 6.2.3.1-3A and Table 6.2.3.1-3B according to the higher layer parameter *ptrs-Power*, the PT-RS scaling factor $\beta_{PTRS}$ specified in clause 6.4.1.2.2.1 of [4, TS + +$$38.211] \text{ is given by } \beta_{PTRS} = 10^{-\frac{P_{PTRS}}{20}} \text{ and also on the 'Precoding Information and Number of Layers' field in DCI.}$$ + +- The UE shall assume *ptrs-Power* in *PTRS-UplinkConfig* is set to state "00" in Table 6.2.3.1-3, Table 6.2.3.1-3A, and Table 6.2.3.1-3B if not configured or in case of non-codebook based PUSCH. +- For partial coherent codebook-based 8TX PUSCH transmission, $L_x$ is the number of PUSCH layers in the antenna group which are precoded coherently with the PUSCH layer/DM-RS port that PT-RS port x is associated with, and $Q_p$ is the number of PT-RS ports scheduled to the UE. +- When the higher layer parameter *multipanelScheme* is set to 'sdmscheme' and two SRS resource sets are configured in *srs-ResourceSetToAddModList* or *srs-ResourceSetToAddModListDCI-0-2* with higher layer parameter *usage* in *SRS-ResourceSet* set to 'codebook'/'nonCodebook', and codepoint "10" of *SRS Resource Set indicator* is indicated, for each PT-RS port is based on Table 6.2.3.1-3B, where $Q_p$ is the total number of PT-RS ports for the PUSCH. + +**Table 6.2.3.1-3: Factor related to PUSCH to PT-RS power ratio per layer per RE other than 8TX PUSCH transmission and other than SDM PUSCH** + +| UL-PTRS-power / | The number of PUSCH layers ( ) | | | | | | | | +|-----------------|--------------------------------|---------------|-------------------------------------------------|---------------|-------------------------------------------------|---------------|------------------|-------------------------------------| +| | 1 | 2 | | 3 | | 4 | | | +| | All cases | Full coherent | Partial and non-coherent and non-codebook based | Full coherent | Partial and non-coherent and non-codebook based | Full coherent | Partial coherent | Non-coherent and non-codebook based | +| 00 | 0 | 3 | $3Q_p-3$ | 4.77 | $3Q_p-3$ | 6 | $3Q_p$ | $3Q_p-3$ | +| 01 | 0 | 3 | 3 | 4.77 | 4.77 | 6 | 6 | 6 | +| 10 | Reserved | | | | | | | | +| 11 | Reserved | | | | | | | | + +**Table 6.2.3.1-3A: Factor related to PUSCH to PT-RS power ratio per layer per RE $\alpha_{PTRS}^{PUSCH}$ for 8TX PUSCH transmission** + +| UL-PTRS-power / | The number of PUSCH layers ( ) | | | +|-----------------|--------------------------------|------------------|-------------------------------------| +| | 1-8 | | | +| | Full coherent | Partial coherent | Non-coherent and non-codebook based | +| 00 | | | | +| 01 | | | | +| 10 | Reserved | | | +| 11 | Reserved | | | + +**Table 6.2.3.1-3B: Factor related to PUSCH to PT-RS power ratio per layer per RE for SDM PUSCH** + +| UL-PTRS-power / | The number of PUSCH layers associated with the same SRS resource set as the PT-RS port | | | +|-----------------|----------------------------------------------------------------------------------------|---------------|-------------------------------------------------| +| | 1 | 2 | | +| | All cases | Full coherent | Partial and non-coherent and non-codebook based | +| 00 | $3Q_p-3$ | $3Q_p$ | $3Q_p-3$ | +| 01 | $3Q_p-3$ | $3Q_p$ | $3Q_p$ | +| 10 | Reserved | | | +| 11 | Reserved | | | + +#### 6.2.3.2 UE PT-RS transmission procedure when transform precoding is enabled + +When transform precoding is enabled and if a UE is configured with the higher layer parameter *transformPrecoderEnabled* in *PTRS-UplinkConfig*, + +- the UE shall be configured with the higher layer parameters *sampleDensity* and the UE shall assume the PT-RS antenna ports' presence and PT-RS group pattern are a function of the corresponding scheduled bandwidth in a corresponding bandwidth part, as shown in Table 6.2.3.2-1. The UE shall assume no PT-RS is present when the number of scheduled RBs is less than $N_{RB0}$ if $N_{RB0} > 1$ or if the RNTI equals TC-RNTI. +- and the UE may be configured PT-RS time density $L_{PT-RS} = 2$ with the higher layer parameter *timeDensityTransformPrecoding*. Otherwise, the UE shall assume $L_{PT-RS} = 1$ . +- if the higher layer parameter *sampleDensity* indicates that the sample density thresholds $N_{RB,i} = N_{RB,i+1}$ , then the associated row where both these thresholds appear in Table 6.2.3.2-1 is disabled. + +**Table 6.2.3.2-1: PT-RS group pattern as a function of scheduled bandwidth** + +| Scheduled bandwidth | Number of PT-RS groups | Number of samples per PT-RS group | +|---------------------------------|------------------------|-----------------------------------| +| $N_{RB0} \leq N_{RB} < N_{RB1}$ | 2 | 2 | +| $N_{RB1} \leq N_{RB} < N_{RB2}$ | 2 | 4 | +| $N_{RB2} \leq N_{RB} < N_{RB3}$ | 4 | 2 | +| $N_{RB3} \leq N_{RB} < N_{RB4}$ | 4 | 4 | +| $N_{RB4} \leq N_{RB}$ | 8 | 4 | + +When transform precoding is enabled and if a UE is configured with the higher layer parameter *transformPrecoderEnabled* in *PTRS-UplinkConfig*, the PT-RS scaling factor $\beta^r$ specified in Clause 6.4.1.2.2.2 of [4, TS 38.211] is determined by the scheduled modulation order as shown in table 6.2.3.2-2. + +**Table 6.2.3.2-2: PT-RS scaling factor ( $\beta^r$ ) when transform precoding enabled.** + +| Scheduled modulation | PT-RS scaling factor ( $\beta^r$ ) | +|----------------------|------------------------------------| +| $\pi/2$ -BPSK | 1 | +| QPSK | 1 | +| 16QAM | | +| 64QAM | | +| 256QAM | | + +## 6.3 UE PUSCH frequency hopping procedure + +### 6.3.1 Frequency hopping for PUSCH repetition Type A and for TB processing over multiple slots + +For PUSCH repetition Type A other than the PUSCH scheduled by RAR UL grant or fallbackRAR UL grant or by DCI format 0\_0 with CRC scrambled by TC-RNTI and for TB processing over multiple slots (as determined according to procedures defined in Clause 6.1.2.1 for scheduled PUSCH, or Clause 6.1.2.3 for configured PUSCH), a UE is configured for frequency hopping by the higher layer parameter *frequencyHoppingDCI-0-2* in *pusch-Config* for PUSCH transmission scheduled by DCI format 0\_2, and by *frequencyHopping* provided in *pusch-Config* for PUSCH transmission scheduled by a DCI format other than 0\_2, and by *frequencyHopping* provided in *configuredGrantConfig* for configured PUSCH transmission. For PUSCH repetition Type A scheduled by RAR UL grant or by DCI format 0\_0 with CRC scrambled by TC-RNTI, a UE is configured for frequency hopping by the frequency hopping flag information field of the RAR UL grant, and by the frequency hopping flag information field of DCI format 0\_0 with CRC scrambled by TC-RNTI, respectively. One of two frequency hopping modes can be configured: + +- Intra-slot frequency hopping, applicable to single slot and multi-slot configured PUSCH transmission, multi-slot PUSCH transmission scheduled by DCI format 0\_1, 0\_2 or 0\_3, each of multiple PUSCH transmissions on a serving cell scheduled by a DCI if the higher layer parameter *pusch-TimeDomainAllocationListForMultiPUSCH* is configured and each of multiple configured grant PUSCH transmissions in a configuration where the higher layer parameters *cg-nrofSlots* and *cg-nrofPUSCH-InSlot* are provided. +- Inter-slot frequency hopping, applicable to multi-slot PUSCH transmission. + +For operation with shared spectrum channel access in FR1, the UE does not expect that two hops of a PUSCH transmission are in different RB sets. + +In case of resource allocation type 2, the UE transmits PUSCH without frequency hopping. + +In case of resource allocation type 1, whether or not transform precoding is enabled for PUSCH transmission, the UE may perform PUSCH frequency hopping, if the frequency hopping field in a corresponding detected DCI format or in a random access response UL grant is set to 1, or if for a Type 1 PUSCH transmission with a configured grant the higher layer parameter *frequencyHoppingOffset* is provided, otherwise no PUSCH frequency hopping is performed. When frequency hopping is enabled for PUSCH, the RE mapping is defined in clause 6.3.1.6 of [4, TS 38.211]. + +For a PUSCH scheduled by RAR UL grant, fallbackRAR UL grant, or by DCI format 0\_0 with CRC scrambled by TC-RNTI, frequency offsets are obtained as described in clause 8.3 of [6, TS 38.213]. Otherwise, for a PUSCH scheduled by DCI format 0\_0/0\_1/0\_3 or a PUSCH based on a Type2 configured UL grant activated by DCI format 0\_0/0\_1 and for resource allocation type 1, frequency offsets are configured by higher layer parameter *frequencyHoppingOffsetLists* + +in *pusch-Config*. For a PUSCH scheduled by DCI format 0\_2 or a PUSCH based on a Type2 configured UL grant activated by DCI format 0\_2 and for resource allocation type 1, frequency offsets are configured by higher layer parameter *frequencyHoppingOffsetListsDCI-0-2* in *pusch-Config*. + +- When the size of the active BWP is less than 50 PRBs, one of two higher layer configured offsets is indicated in the UL grant. +- When the size of the active BWP is equal to or greater than 50 PRBs, one of four higher layer configured offsets is indicated in the UL grant. + +For PUSCH based on a Type1 configured UL grant the frequency offset is provided by the higher layer parameter *frequencyHoppingOffset* in *rrc-ConfiguredUplinkGrant*. + +For a MsgA PUSCH the frequency offset is provided by the higher layer parameter as described in [6, TS 38.213]. + +In case of intra-slot frequency hopping, the starting RB in each hop is given by: + +$$RB_{start} = \begin{cases} RB_{start} & i = 0 \\ (RB_{start} + RB_{offset}) \bmod N_{BWP}^{size} & i = 1 \end{cases},$$ + +where $i=0$ and $i=1$ are the first hop and the second hop respectively, and $RB_{start}$ is the starting RB within the UL BWP, as calculated from the resource block assignment information of resource allocation type 1 (described in Clause 6.1.2.2.2) or as calculated from the resource assignment for MsgA PUSCH (described in [6, TS 38.213]) and $RB_{offset}$ is the frequency offset in RBs between the two frequency hops. The number of symbols in the first hop is given by $N_{start}$ , the number of symbols in the second hop is given by $N_{end}$ , where $N_{start}$ and $N_{end}$ is the length of the PUSCH transmission in OFDM symbols in one slot. + +In case of inter-slot frequency hopping and when *pusch-DMRS-Bundling* is not enabled, or for inter-slot frequency hopping for a PUSCH scheduled by RAR UL grant or DCI format 0\_0 with CRC scrambled by TC-RNTI, the starting RB during slot $n$ is given by: + +where $n$ is the current slot number within a system radio frame, where a multi-slot PUSCH transmission can take place, $RB_{start}$ is the starting RB within the UL BWP, as calculated from the resource block assignment information of resource allocation type 1 (described in Clause 6.1.2.2.2) and $RB_{offset}$ is the frequency offset in RBs between the two frequency hops. + +In case of inter-slot frequency hopping and when *pusch-DMRS-Bundling* is enabled, and when a PUSCH is not scheduled by RAR UL grant or DCI format 0\_0 with CRC scrambled by TC-RNTI, the starting RB during slot $n$ is given by: + +where $n$ is the current slot number within a system radio frame, $K$ is the value of the higher layer parameter *pusch-FrequencyHopping-Interval*, $RB_{start}$ is the starting RB within the UL BWP, as calculated from the resource block assignment information of resource allocation type 1 (described in Clause 6.1.2.2.2) and $RB_{offset}$ is the frequency offset in RBs between the two frequency hops. + +### 6.3.2 Frequency hopping for PUSCH repetition Type B + +For PUSCH repetition Type B (as determined according to procedures defined in Clause 6.1.2.1 for scheduled PUSCH, or Clause 6.1.2.3 for configured PUSCH), a UE is configured for frequency hopping by the higher layer parameter *frequencyHoppingDCI-0-2* in *pusch-Config* for PUSCH transmission scheduled by DCI format 0\_2, by *frequencyHoppingDCI-0-1* provided in *pusch-Config* for PUSCH transmission scheduled by DCI format 0\_1, and by *frequencyHoppingPUSCH-RepTypeB* provided in *rrc-ConfiguredUplinkGrant* for Type 1 configured PUSCH transmission. The frequency hopping mode for Type 2 configured PUSCH transmission follows the configuration of the activating DCI format. One of two frequency hopping modes can be configured: + +- Inter-repetition frequency hopping +- Inter-slot frequency hopping + +For operation with shared spectrum channel access in FR1, the UE does not expect that two hops of a PUSCH transmission are in different RB sets. + +In case of resource allocation type 1, whether or not transform precoding is enabled for PUSCH transmission, the UE may perform PUSCH frequency hopping, if the frequency hopping field in a corresponding detected DCI format is set to 1, or if for a Type 1 PUSCH transmission with a configured grant the higher layer parameter *frequencyHoppingPUSCH-RepTypeB* is provided, otherwise no PUSCH frequency hopping is performed. When frequency hopping is enabled for PUSCH, the RE mapping is defined in clause 6.3.1.6 of [4, TS 38.211]. + +For a PUSCH scheduled by DCI format 0\_1 or a PUSCH based on a Type 2 configured UL grant activated by DCI format 0\_1 and for resource allocation type 1, frequency offsets are configured by higher layer parameter *frequencyHoppingOffsetLists* in *pusch-Config*. For a PUSCH scheduled by DCI format 0\_2 or a PUSCH based on a Type 2 configured UL grant activated by DCI format 0\_2 and for resource allocation type 1, frequency offsets are configured by higher layer parameter *frequencyHoppingOffsetListsDCI-0-2* in *pusch-Config*. + +- When the size of the active BWP is less than 50 PRBs, one of two higher layer configured offsets is indicated in the UL grant. +- When the size of the active BWP is equal to or greater than 50 PRBs, one of four higher layer configured offsets is indicated in the UL grant. + +For PUSCH based on a Type 1 configured UL grant the frequency offset is provided by the higher layer parameter *frequencyHoppingOffset* in *rrc-ConfiguredUplinkGrant*. + +In case of inter-repetition frequency hopping, the starting RB for an actual repetition within the $n$ -th nominal repetition (as defined in Clause 6.1.2.1) is given by: + +$$RB_{start}(n) = \begin{cases} RB_{start} & n \bmod 2 = 0 \\ (RB_{start} + RB_{offset}) \bmod N_{BWP}^{size} & n \bmod 2 = 1 \end{cases},$$ + +where $RB_{start}$ is the starting RB within the UL BWP, as calculated from the resource block assignment information of resource allocation type 1 (described in Clause 6.1.2.2.2) and $RB_{offset}$ is the frequency offset in RBs between the two frequency hops. + +In case of inter-slot frequency hopping, the starting RB during slot $n$ follows that of inter-slot frequency hopping for PUSCH Repetition Type A in Clause 6.3.1. + +## 6.4 UE PUSCH preparation procedure time + +If the first uplink symbol in the PUSCH allocation for a transport block, including the DM-RS, as defined by the slot offset $K_2$ and $K_{offset}$ , if configured, and the start $S$ and length $L$ of the PUSCH allocation indicated by 'Time domain resource assignment' of the scheduling DCI and including the effect of the timing advance, is no earlier than at symbol $L_2$ , where $L_2$ is defined as the next uplink symbol with its CP starting + +$T_{proc,2} = \max((N_2 + d_{2,1} + d_{2,2})(2048 + 144) \cdot \kappa 2^{-\mu} \cdot T_c + T_{ext} + T_{switch}, d_{2,2})$ after the end of the reception of the last symbol of the PDCCH carrying the DCI scheduling the PUSCH, then the UE shall transmit the transport block. When the PDCCH reception includes two PDCCH candidates from two respective search space sets, as described in clause 10.1 of [6, TS 38.213], for the purpose of determining the last symbol of the PDCCH carrying the DCI scheduling the PUSCH, the PDCCH candidate that ends later in time is used. + +- $N_2$ is based on $\mu$ of Table 6.4-1 and Table 6.4-2 for UE processing capability 1 and 2 respectively, where $\mu$ corresponds to the one of $(\mu_{DL}, \mu_{UL})$ resulting with the largest $T_{proc,2}$ , where the $\mu_{DL}$ corresponds to the subcarrier spacing of the downlink with which the PDCCH carrying the DCI scheduling the PUSCH was transmitted and $\mu_{UL}$ corresponds to the subcarrier spacing of the uplink channel with which the PUSCH is to be transmitted, and $\kappa$ is defined in clause 4.1 of [4, TS 38.211]. +- For operation with shared spectrum channel access in FR1, $T_{ext}$ is calculated according to [4, TS 38.211], otherwise $T_{ext} = 0$ . +- If the first symbol of the PUSCH allocation consists of DM-RS only, then $d_{2,1} = 0$ , otherwise $d_{2,1} = 1$ . +- If the UE is configured with multiple active component carriers, the first uplink symbol in the PUSCH allocation further includes the effect of timing difference between component carriers as given in [11, TS 38.133]. + +- If the scheduling DCI triggered a switch of BWP, $d_{2,2}$ equals to the switching time as defined in [11, TS 38.133], otherwise $d_{2,2}=0$ . +- If a PUSCH of a larger priority index would overlap with a PUCCH of a smaller priority index and the PUCCH and PUSCH are not simultaneously transmitted, and the UE is not provided *uci-MuxWithDiffPrio* for the primary PUCCH group or *uci-MuxWithDiffPrioSecondaryPUCCHgroup* for the secondary PUCCH group, $d_2$ for the PUSCH of a larger priority is set as reported by the UE; otherwise $d_2 = 0$ . +- For a UE that supports capability 2 on a given cell, the processing time according to UE processing capability 2 is applied if the high layer parameter *processingType2Enabled* in *PUSCH-ServingCellConfig* is configured for the cell and set to 'enable', +- If the PUSCH indicated by the DCI is overlapping with one or more PUCCH channels, then the transport block is multiplexed following the procedure in clause 9.2.5 of [6, TS 38.213], otherwise the transport block is transmitted on the PUSCH indicated by the DCI. +- If uplink switching gap is triggered as defined in clause 6.1.6, $T_{switch}$ equals to the switching gap duration and for the UE configured with higher layer parameter *uplinkTxSwitchingOption* set to 'dualUL' for uplink carrier aggregation $\mu_{UL}=\min(\mu_{UL,carrier1}, \mu_{UL,carrier2})$ , otherwise $T_{switch} = 0$ . + +Otherwise the UE may ignore the scheduling DCI. + +The value of $d_2$ is used both in the case of normal and extended cyclic prefix. + +**Table 6.4-1: PUSCH preparation time for PUSCH timing capability 1** + +| | PUSCH preparation time N_2 [symbols] | +|---|----------------------------------------------------------| +| 0 | 10 | +| 1 | 12 | +| 2 | 23 | +| 3 | 36 | +| 5 | 144 | +| 6 | 288 | + +**Table 6.4-2: PUSCH preparation time for PUSCH timing capability 2** + +| | PUSCH preparation time N_2 [symbols] | +|---|----------------------------------------------------------| +| 0 | 5 | +| 1 | 5.5 | +| 2 | 11 for frequency range 1 | + +# 7 UE procedures for transmitting and receiving on a carrier with intra-cell guard bands + +For operation with shared spectrum channel access for FR1, when the UE is configured with any of *IntraCellGuardBandsPerSCS* for UL carrier and for DL carrier and *intraCellGuardBandsSL-List* for SL carrier with SCS configuration, the UE is provided with intra-cell guard bands on a carrier with $x$ , each defined by start CRB and size in number of CRBs, and $x$ , provided by higher layer parameters *startCRB* and *nrofCRBs*, respectively, where $x$ . The subscript $x$ is set to DL, UL, or SL for the downlink, uplink, or sidelink, respectively. Where there is no risk of confusion, the subscript $x$ can be dropped. The intra-cell guard bands separate RB sets, each defined by start and end CRB, and $x$ , respectively. The UE does not expect that *nrofCRBs* is configured with non-zero value smaller than the applicable intra-cell guard bands as specified in [8, TS 38.101-1] corresponding to $x$ and carrier size $x$ . The UE determines the start and end CRB indices for $x$ as + +and + +The RB set with index $i$ consists of $nrofCRBs_i$ resource blocks where $i$ is from 0 to $nrofRBsets-1$ . When the UE is not configured with *IntraCellGuardBandsPerSCS* for UL carrier and for DL carrier with SCS configuration $\mu$ , or is not configured with *intraCellGuardBandsSL-List* for SL carrier with SCS configuration $\mu$ , the UE determines the CRB indices for the intra-cell guard band(s), if any, and corresponding RB set(s) according to the nominal intra-cell guard band and RB set pattern as specified in [8, TS 38.101-1] corresponding to $\mu$ and carrier size $N_{RB}$ . For any one or more of DL, UL, SL, if the nominal intra-cell guard band and RB set pattern as specified in [8, TS 38.101-1] contains no intra-cell guard bands, the number of RB sets for the carrier is $nrofRBsets$ . + +For a carrier with $\mu$ , the UE expects $nrofRBsets$ and where for a BWP $i$ configured by *initialDownlinkBWP* or *BWP-Downlink* for the DL BWP, or *initialUplinkBWP* or *BWP-Uplink* for the UL BWP, or configured by *SL-BWP-Config* for the SL BWP. Within the BWP $i$ , RB sets are numbered in increasing order from 0 to $nrofRBsets_i-1$ where $nrofRBsets_i$ is the number of RB sets contained in the BWP $i$ and RB set 0 within the BWP $i$ corresponds to RB set 0 in the carrier and RB set $nrofRBsets_i-1$ within the BWP $i$ corresponds to RB set $nrofRBsets-1$ in the carrier. + +When a UE is provided with $nrofCRBs_i = 0$ for all intra-cell guard band(s) on a carrier with $\mu$ , the UE is indicated that no intra-cell guard-bands are configured for the carrier and expects $nrofRBsets$ . For $\mu = 2$ , the UE expects the number of RBs within a RB set is between 100 and 110. For $\mu = 3$ , the UE expects the number of RBs within a RB set is between 50 and 55 except for at most one RB set which may contain 56 RBs. + +# 8 Physical sidelink shared channel related procedures + +A UE can be configured by higher layers with one or more sidelink resource pools. A sidelink resource pool can be for transmission of PSSCH, as described in Clause 8.1, and/or SL PRS, as described in Clause 8.2.4, or for reception of PSSCH, as described in Clause 8.3, and/or SL PRS, as described in Clause 8.4.4, and can be associated with either sidelink resource allocation mode 1 or sidelink resource allocation mode 2. + +A sidelink resource pool which can be used for transmission of both SL PRS and PSSCH will be referred to as shared SL PRS resource pool. + +A sidelink resource pool which can be used for transmission of SL PRS and cannot be used for transmission of PSSCH will be referred to as dedicated SL PRS resource pool. + +In the frequency domain, + +- If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is not provided, or it is set to 'contiguousRB', a sidelink resource pool consists of *sl-NumSubchannel* contiguous sub-channels. A sub-channel consists of *sl-SubchannelSize* contiguous PRBs, where *sl-NumSubchannel* and *sl-SubchannelSize* are higher layer parameters. +- If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'interlaceRB', in the frequency domain, a sidelink resource pool consists of *sl-NumSubchannel* sub-channels, where each sub-channel consists of *numInterlacePerSubchannel* interlaces having contiguous interlace indices. + +For operation with shared spectrum channel access for frequency range 1, a sidelink resource pool can be (pre-)configured to include integer number of RB sets, and the lowest RB of the sidelink resource pool is aligned with the lowest RB of lowest RB set in the resource pool, and the highest RB of the sidelink resource pool is aligned with the highest RB of highest RB set in the resource pool. A UE can be configured with intra-cell guard bands according to the higher layer parameter *intraCellGuardBandsSL-List*. The configured intra-cell guard band PRBs between any two adjacent RB sets can be used only for PSSCH transmission, if and only if, the UE has successfully performed channel access procedure in both adjacent RB sets, and the UE uses both of these RB sets for PSSCH transmission. If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'contiguousRB', and if more than 1 sub-channel is used for PSSCH transmission, when the highest sub-channel of PSSCH overlaps with a single RB set and intra-cell guard band PRBs, the UE can transmit PSSCH on the PRBs belonging to the allocated sub-channel(s) except for the intra-cell guard band PRBs within the highest sub-channel. The set of slots that may belong to a sidelink resource pool is denoted by $\{s\}$ where + +- + +- the slot index is relative to slot#0 of the radio frame corresponding to SFN 0 of the serving cell or DFN 0, +- the set includes all the slots except the following slots, + - slots in which S-SS/PSBCH block (S-SSB) or additional transmission occasion for S-SSB is configured, + - slots in each of which at least one of $Y$ -th, $(Y+1)$ -th, ..., $(Y+X-1)$ -th OFDM symbols are not semi-statically configured as UL as per the higher layer parameter *tdd-UL-DL-ConfigurationCommon* of the serving cell if provided or *sl-TDD-Configuration* if provided or *sl-TDD-Config* of the received PSBCH if provided, where $Y$ and $X$ are set by the higher layer parameters *sl-StartSymbol* and *sl-LengthSymbols*, respectively. +- The reserved slots which are determined by the following steps. + - 1) the remaining slots excluding slots and slots from the set of all the slots are denoted by arranged in increasing order of slot index. + - 2) a slot belongs to the reserved slots if , here and where denotes the length of bitmap configured by higher layers. +- The slots in the set are arranged in increasing order of slot index. + +The UE determines the set of logical slots assigned to a sidelink resource pool as follows: + +- a bitmap associated with the resource pool is used where the length of the bitmap is configured by higher layers. +- a slot belongs to the set if where . +- The slots in the set are re-indexed such that the subscripts $i$ of the remaining slots are successive $\{0, 1, \dots\}$ , where is the number of the slots remaining in the set. + +The UE determines the set of resource blocks assigned to a sidelink resource pool as follows: + +- The resource block pool consists of PRBs. +- If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is not provided, or is set to 'contiguousRB', the sub-channel $m$ for consists of a set of contiguous resource blocks with the physical resource block number for , where , and *numSubchannel* are given by higher layer parameters *sl-StartRB-Subchannel*, *sl-SubchannelSize* and *sl-NumSubchannel*, respectively. +- If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'interlaceRB', the sub-channel $m$ for consists of a set of *numInterlacePerSubchannel* contiguous interlaces, where each interlace consists of at least 10 resource blocks as defined in clause 4.4.4.6 of [4, TS 38.211]. The sub-channel $m$ is indexed per RB set and is periodically indexed across multiple RB sets within the resource pool. The sub-channel with the same index is mapped to the set of *numInterlacePerSubchannel* interlace(s) with the same index(s) in different RB sets. The sub-channel#0 is mapped to interlaces 0 to *numInterlacePerSubchannel*-1, the subchannel #1 is mapped to interlaces *numInterlacePerSubchannel* to *numInterlacePerSubchannel*\*2-1, and so on. + +A UE is not expected to use the last PRBs in the resource pool, except when the resource pool is a dedicated SL PRS resource pool. + +In case of dynamic co-channel coexistence of LTE sidelink and NR sidelink, for NR sidelink transmissions in 30kHz SCS, the UE expects that the start of the first symbol of the earlier overlapping NR SL slot is aligned with the start of the first symbol of the overlapping LTE SL subframe. + +## 8.1 UE procedure for transmitting the physical sidelink shared channel + +Each PSSCH transmission is associated with an PSCCH transmission. + +That PSCCH transmission carries the 1st stage of the SCI associated with the PSSCH transmission; the 2nd stage of the associated SCI is carried within the resource of the PSSCH. + +If the UE transmits SCI format 1-A on PSCCH according to a PSCCH resource configuration in slot $n$ and PSCCH resource $m$ , then for the associated PSSCH transmission in the same slot + +- one transport block is transmitted with up to two layers; +- The number of layers ( $\nu$ ) is determined according to the '*Number of DMRS port*' field in the SCI; +- The set of consecutive symbols within the slot for transmission of the PSSCH is determined according to clause 8.1.2.1; +- The set of contiguous or interlaced resource blocks for transmission of the PSSCH is determined according to clause 8.1.2.2; + +Transform precoding is not supported for PSSCH transmission. + +Only wideband precoding is supported for PSSCH transmission. + +The DM-RS antenna ports $\{\tilde{p}_0, \dots, \tilde{p}_{\nu-1}\}$ in Clause 8.4.1.1.2 of [4, TS38.211] are determined according to the ordering of DM-RS port(s) given by Tables 8.3.1.1-3 in Clause 8.3.1.1 of [5, TS 38.212]. + +The UE shall set the contents of the SCI format 2-A as follows: + +- the UE shall set value of the '*HARQ process number*' field as indicated by higher layers. +- the UE shall set value of the '*NDI*' field as indicated by higher layers. +- the UE shall set value of the '*Redundancy version*' field as indicated by higher layers. +- the UE shall set value of the '*Source ID*' field as indicated by higher layers. +- the UE shall set value of the '*Destination ID*' field as indicated by higher layers. +- the UE shall set value of the '*HARQ feedback enabled/disabled indicator*' field as indicated by higher layers. +- the UE shall set value of the '*Cast type indicator*' field as indicated by higher layers. +- the UE shall set value of the '*CSI request*' field as indicated by higher layers. +- the UE shall set value of the '*CAPC*' field, if present, as indicated by higher layers. +- the UE shall set value of the '*COT sharing cast type*' field, if present, as indicated by higher layers. +- the UE shall set value of the '*COT sharing Additional ID*' field, if present, as indicated by higher layers. +- the UE shall set value of the '*Remaining COT duration*' field, if present, as indicated by higher layers. + +The UE shall set the contents of the SCI formats 2-B as follows: + +- the UE shall set value of the '*HARQ process number*' field as indicated by higher layers. +- the UE shall set value of the '*NDI*' field as indicated by higher layers. +- the UE shall set value of the '*Redundancy version*' field as indicated by higher layers. +- the UE shall set value of the '*Source ID*' field as indicated by higher layers. +- the UE shall set value of the '*Destination ID*' field as indicated by higher layers. +- the UE shall set value of the '*HARQ feedback enabled/disabled indicator*' field as indicated by higher layers. +- the UE shall set value of the '*Zone ID*' field as indicated by higher layers. +- the UE shall set the '*Communication range requirement*' field as indicated by higher layers. + +The UE shall set the contents of the SCI format 2-C as follows: + +- the UE shall set value of the '*HARQ process number*' field as indicated by higher layers. +- the UE shall set value of the '*NDI*' field as indicated by higher layers. +- the UE shall set value of the '*Redundancy version*' field as indicated by higher layers. + +- the UE shall set value of the '*Source ID*' field as indicated by higher layers. +- the UE shall set value of the '*Destination ID*' field as indicated by higher layers. +- the UE shall set value of the '*HARQ feedback enabled/disabled indicator*' field as indicated by higher layers. +- the UE shall set value of the '*CSI request*' field as indicated by higher layers. +- the UE shall set value of '*Providing/Requesting indicator*' field as indicated by higher layers. +- if '*Providing/Requesting indicator*' indicates SCI format 2-C is used to convey an explicit request for inter-UE coordination information: + - the UE shall set value of the '*Priority*' field as indicated by higher layers. + - the UE shall set value of the '*Number of subchannels*' field as indicated by higher layers. + - the UE shall set value of the '*Resource reservation period*' field as indicated by higher layers. + - the UE shall set value of the '*Resource selection window location*' field as indicated by higher layers. + - the UE shall set value of the '*Resource set type*' field as indicated by higher layers if higher layer parameter *sl-DetermineResourceType* is configured to 'UE-B's request'; otherwise this field is omitted. +- if '*Providing/Requesting indicator*' indicates SCI format 2-C is used to convey inter-UE coordination information: + - the UE shall set value of the '*Resource set type*' field as indicated by higher layers. + - the UE shall set value of the '*Resource combination(s)*' field (clause 8.1.5A) as indicated by higher layers. + - the UE shall set value of the '*Lowest subchannel indices*' as indicated by higher layers + - the UE shall set value of the '*First resource location*' as indicated by higher layers + - the UE shall set value of the '*Reference slot location*' as indicated by higher layers + +The UE shall set the contents of the SCI format 2-D as follows: + +- the UE shall set value of the '*[SL PRS resource ID]*' field as indicated by higher layers. +- the UE shall set value of the '*[SL PRS request]*' field as indicated by higher layers. +- the UE shall set value of the '*[Embedded SCI format]*' field as indicated by higher layers. +- if '*Embedded SCI format*' indicates that SCI format 2-A is embedded within this SCI format 2-D then the UE shall include in the '*[Embedded SCI format payload]*' field the fields of SCI format 2-A, set as specified above. +- if '*Embedded SCI format*' indicates that SCI format 2-B is embedded within this SCI format 2-D then the UE shall include in the '*[Embedded SCI format payload]*' field the fields of SCI format 2-B, set as specified above. + +### 8.1.1 Transmission schemes + +Only one transmission scheme is defined for the PSSCH and is used for all PSSCH transmissions. + +PSSCH transmission is performed with up to two antenna ports, with antenna ports 1000-1001 as defined in clause 8.2.4 of [4, TS 38.211]. + +### 8.1.2 Resource allocation + +In sidelink resource allocation mode 1: + +- for PSSCH and PSCCH transmission, dynamic grant, configured grant type 1 and configured grant type 2 are supported. The configured grant Type 2 sidelink transmission is semi-persistently scheduled by a SL grant in a valid activation DCI according to Clause 10.2A of [6, TS 38.213]. + +#### 8.1.2.1 Resource allocation in time domain + +The UE shall transmit the PSSCH in the same slot as the associated PSCCH. + +The minimum resource allocation unit in the time domain is a slot. + +The UE shall transmit the PSSCH in consecutive symbols within the slot, subject to the following restrictions: + +- The UE shall not transmit PSSCH in symbols which are not configured for sidelink. A symbol is configured for sidelink, according to higher layer parameters *sl-StartSymbol* and *sl-LengthSymbols*, where *sl-StartSymbol* is the symbol index of the first symbol of *sl-LengthSymbols* consecutive symbols configured for sidelink. +- Within the slot, PSSCH resource allocation starts at symbol *sl-StartSymbol+1*, except when *startingSymbolFirst* and *startingSymbolSecond* are provided for a SL-BWP. If *startingSymbolFirst* and *startingSymbolSecond* are provided for the SL-BWP, there are 2 candidate starting symbols, given by *startingSymbolFirst* and *startingSymbolSecond* respectively, for PSSCH transmission for slots without PSFCH symbols; and there is one starting symbol, given by *startingSymbolFirst*, for PSSCH transmission for slots with PSFCH symbols. PSSCH resource allocation starts at the next symbol after each candidate starting symbol. In a slot, the UE may use the second candidate starting symbol, provided by *startingSymbolSecond*, only if it fails to access the channel prior to the first candidate starting symbol provided by *startingSymbolFirst*. +- The UE shall not transmit PSSCH in symbols which are configured for use by PSFCH, if PSFCH is configured in this slot. +- The UE shall not transmit PSSCH in the last symbol configured for sidelink. +- The UE shall not transmit PSSCH in the symbol immediately preceding the symbols which are configured for use by PSFCH, if PSFCH is configured in this slot. +- For operation with shared spectrum channel access in frequency range 1, for the first SL transmission with PSSCH/PSCCH by a UE to initiate a channel occupancy for a slot, if no resource reservation is transmitted or detected for the slot and any one of the RB set(s) of the intended PSCCH/PSSCH transmission, and if UE is configured with multiple CPE starting positions provided by *CPStartingPositionsPSCCH-PSSCH-InitiateCOT*, the UE determines a duration of a cyclic prefix extension *Text*, to be applied according to [4, TS 38.211] where the index for [4, TS 38.211] is chosen randomly from a set of values configured per priority of the PSCCH/PSSCH by the higher layer parameter *CPStartingPositionsPSCCH-PSSCH-InitiateCOT*. Otherwise, the UE uses a configured default cyclic prefix extension *Text* indicated by *DefaultCPStartingPositionsPSCCH-PSSCH-InitiateCOT*. +- For operation with shared spectrum channel access in frequency range 1, for the first SL transmission with PSSCH/PSCCH by a UE within a channel occupancy, the UE transmitting in the channel occupancy determines the duration of a cyclic prefix extension *Text* according to higher layer parameter *DefaultCPStartingPositionsPSCCH-PSSCH-SharedCOT*, unless the UE is configured with multiple CPE starting positions for transmitting within a shared channel occupancy by *CPStartingPositionsPSCCH-PSSCH-SharedCOT*, in which case the UE determines the duration of a cyclic prefix extension *Text* to be applied according to [4, TS 38.211] where the index for [4, TS 38.211] is chosen randomly from a set of values configured per priority of the PSCCH/PSSCH by the higher layer parameter *CPStartingPositionsPSCCH-PSSCH-SharedCOT*, if no resource reservation is transmitted or detected for the slot and the RB set(s) of the intended PSCCH/PSSCH transmission, otherwise, the UE uses the configured default cyclic prefix extension *Text* indicated by *DefaultCPStartingPositionsPSCCH-PSSCH-SharedCOT*. +- For operation with shared spectrum channel access in frequency range 1, for a PSSCH/PSCCH transmission by a UE that follows another SL transmission by the same UE in a channel occupancy, the UE determines the duration of a cyclic prefix extension *Text* as follows: + - When gap between the PSSCH/PSCCH transmission and the previous SL transmission is 1 symbol, the index for is set to '1'. + - When gap between the PSSCH/PSCCH transmission and the previous SL transmission is 2 symbols, the index for is set to '3' for $\mu=1$ and to 2 for $\mu=2$ . + +In sidelink resource allocation mode 1: + +- For sidelink dynamic grant, the PSSCH transmission is scheduled by a DCI format 3\_0. +- For sidelink configured grant type 2, the configured grant is activated by a DCI format 3\_0. +- For sidelink dynamic grant and sidelink configured grant type 2: + - The "Time gap" field value $m$ of the DCI format 3\_0 provides an index $m + 1$ into a slot offset table. That table is given by higher layer parameter *sl-DCI-ToSL-Trans* and the table value at index $m + 1$ will be referred to as slot offset . + - The slot of the first sidelink transmission scheduled by the DCI is the first SL slot of the corresponding resource pool that starts not earlier than , where is the starting time of the downlink slot carrying the corresponding DCI, is the timing advance value corresponding to the TAG of the serving cell on which the DCI is received and is the slot offset between the slot of the DCI and the first sidelink transmission scheduled by DCI and is the SL slot duration. + - The "Configuration index" field of the DCI format 3\_0, if provided and not reserved, indicates the index of the sidelink configured type 2. +- For sidelink configured grant type 1: + - The slot of the first sidelink transmissions follows the higher layer configuration according to [10, TS 38.321]. + +For operation with shared spectrum channel access for frequency range 1, if the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'interlaceRB;,' + +- the lowest index of the RB set allocation to the initial PSSCH transmission is indicated via the field "Lowest index of the RB set allocation to the initial transmission" of the DCI format 3\_0. +- the starting RB set index of the initial PSSCH transmission of the sidelink configured grant Type 1 is indicated via the higher layer parameter *sl-StartRBsetCG-Type1*. + +## 8.1.2.2 Resource allocation in frequency domain + +The resource allocation unit in the frequency domain is the sub-channel. + +The sub-channel assignment for sidelink transmission is determined using the "Frequency resource assignment" field in the associated SCI. + +The lowest sub-channel for sidelink transmission is the sub-channel on which the lowest PRB of the associated PSCCH is transmitted. + +If a PSSCH scheduled by a PSCCH would overlap with resources containing the PSCCH, the resources corresponding to a union of the PSCCH that scheduled the PSSCH and associated PSCCH DM-RS are not available for the PSSCH. + +When PSSCH is transmitted on multiple RB sets, the corresponding PSCCH is located on the sub-channel with smallest index of the lowest RB set. + +### 8.1.3 Modulation order, target code rate, redundancy version and transport block size determination + +The redundancy version is given by the "Redundancy version" field in SCI format 2-A, 2-B, 2-C or 2-D. + +#### 8.1.3.1 Modulation order and target code rate determination + +$I_{MCS}$ is given by the '*Modulation and coding scheme*' field in SCI format 1-A. + +The MCS table is determined as follows: Table 5.1.3.1-1 is used if no additional MCS table is configured by higher layer parameter *sl-Additional-MCS-Table*; otherwise an MCS table is determined according to Table 8.1.3.1-1 or Table 8.1.3.1-2 and '*Additional MCS table indicator*' field in SCI format 1-A. + +**Table 8.1.3.1-1: Mapping of one bit of MCS table indicator to MCS table** + +| MCS table indicator | MCS table | +|---------------------|-----------------------------------------------------------------------------------------| +| '0' | Table 5.1.3.1-1 | +| '1' | 1 st table provided by higher layer parameter sl-Additional-MCS-Table | + +**Table 8.1.3.1-2: Mapping of two bits of MCS table indicator to MCS table** + +| MCS table indicator | MCS table | +|---------------------|-----------------------------------------------------------------------------------------| +| '00' | Table 5.1.3.1-1 | +| '01' | 1 st table provided by higher layer parameter sl-Additional-MCS-Table | +| '10' | 2 nd table provided by higher layer parameter sl-Additional-MCS-Table | +| '11' | reserved | + +The UE shall use $I_{MCS}$ and the MCS table determined according to the previous step to determine the modulation order ( $Q_m$ ) and Target code rate ( $R$ ) used in the physical sidelink shared channel. + +### 8.1.3.2 Transport block size determination + +For the PSSCH assigned by SCI, if Table 5.1.3.1-2 is used and , or a table other than Table 5.1.3.1-2 is used and , the UE shall first determine the TBS as specified below: + +The UE shall first determine the number of REs ( $N_{RE}$ ) within the slot. + +- A UE first determines the number of REs allocated for PSSCH within a PRB () by , where + - is the number of subcarriers in a physical resource block, + - $= sl\text{-}LengthSymbols - 2$ , where $sl\text{-}LengthSymbols$ is the number of sidelink symbols within the slot provided by higher layers. If $startingSymbolFirst$ and $startingSymbolSecond$ are provided for the SL-BWP, the number of sidelink symbols assumed in transport block size determination is determined by a reference number of symbols, $numRefSymbolLength$ , provided by higher layers, such that $numRefSymbolLength$ replaces $sl\text{-}LengthSymbols$ in calculation of . + - $= 3$ if '*PSFCH overhead indication*' field of SCI format 1-A indicates "1", and $= 0$ otherwise, if higher layer parameter *sl-PSFCH-Period* is 2 or 4. If higher layer parameter *sl-PSFCH-Period* is 0, . If higher layer parameter *sl-PSFCH-Period* is 1, . + - is the number of OFDM symbols used for SL PRS in the slot as indicated by the '*SL PRS resource ID*' in SCI format 2-D if the 2nd-stage SCI is SCI format 2-D, and , otherwise., + - is the overhead given by higher layer parameter *sl-X-Overhead*, + - is given by Table 8.1.3.2-1 according to higher layer parameter *sl-PSSCH-DMRS-TimePatternList*. + +**Table 8.1.3.2-1: according to higher layer parameter *sl-PSSCH-DMRS-TimePatternList*** + +| sl-PSSCH-DMRS-TimePatternList | | +|--------------------------------------|----| +| {2} | 12 | +| {3} | 18 | +| {4} | 24 | +| {2,3} | 15 | +| {2,4} | 18 | +| {3,4} | 21 | +| {2,3,4} | 18 | + +- A UE determines the total number of REs allocated for PSSCH () by , where + +- $n_{PRB}$ is the total number of allocated PRBs for the PSSCH. If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'interlaceRB', a reference number of PRBs ( $n_{ref}$ ) per interlace within 1 RB set, *numRefPRBOFInterlace*, is provided by higher layers for determination of total number of PRBs for PSSCH, that is $n_{PRB} = n_{ref} * n_{inter.subCH} * n_{subCH} * n_{RB-set}$ , where $n_{inter.subCH}$ is given by the higher layer parameter *numInterlacePerSubchannel*, $n_{subCH}$ is the number of occupied sub-channels within one RB set for the PSSCH, and $n_{RB-set}$ is the number of occupied RB sets for the PSSCH. If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'contiguousRB', $n_{PRB} = * n_{subCH}$ , where is provided by higher layer parameter *sl-SubchannelSize*, and $n_{subCH}$ is the number of occupied sub-channels for the PSSCH. +- is the total number of REs occupied by the PSCCH and PSCCH DM-RS. +- is the number of coded modulation symbols generated for 2nd-stage SCI transmission (prior to duplication for the 2nd layer, if present) according to Clause 8.4.4 of [5, TS 38.212], with the assumption of . + +The UE determines TBS according to Steps 2), 3), and 4) in clause 5.1.3.2. + +A UE is not expected to receive an SCI indicating if Table 5.1.3.1-2 is used, or otherwise. + +#### 8.1.4 UE procedure for determining the subset of resources to be reported to higher layers in PSSCH resource selection in sidelink resource allocation mode 2 + +In resource allocation mode 2, the higher layer can request the UE to determine a subset of resources from which the higher layer will select resources for PSSCH/PSCCH transmission for a carrier. To trigger this procedure, in slot $n$ for this carrier, the higher layer provides the following parameters for this PSSCH/PSCCH transmission: + +- the resource pool from which the resources are to be reported; +- L1 priority, ; +- the remaining packet delay budget; +- number of sub-channels, : If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is not provided, the number of sub-channels to be used for the PSSCH/PSCCH transmission in a slot is . If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'contiguousRB', corresponds to the number of sub-channels within all used RB sets to be used for the PSCCH/PSSCH transmission in a slot. If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'interlaceRB', corresponds to the number of sub-channels to be used for the PSSCH/PSCCH transmission in a slot in each RB set, +- If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'interlaceRB', the number of used RB sets for one PSCCH/PSSCH transmission, $L_{RBset}$ . +- optionally, the number of consecutive slots for Multi-consecutive slots transmission, . +- optionally, the resource reservation interval, , in units of msec. +- if the higher layer requests the UE to determine a subset of resources from which the higher layer will select resources for PSSCH/PSCCH transmission as part of re-evaluation or pre-emption procedure, the higher layer provides a set of resources which may be subject to re-evaluation and a set of resources which may be subject to pre-emption. + - it is up to UE implementation to determine the subset of resources as requested by higher layers before or after the slot - , where is the slot with the smallest slot index among and , and is equal to , where is defined in slots in Table 8.1.4-2 where is the SCS configuration of the SL BWP. +- Each of the resource(s) in and/or corresponds to consecutive slots if is provided with a value larger than 1. +- Optionally, the indication of resource selection mechanism. +- Optionally, *rbSetsWithConsecutiveLBTFailure*, which indicates the RB sets where consistent LBT failure has been indicated. + +The following higher layer parameters affect this procedure: + +- *sl-SelectionWindowList*: internal parameter is set to the corresponding value from higher layer parameter *sl-SelectionWindowList* for the given value of . +- *sl-Thres-RSRP-List*: this higher layer parameter provides an RSRP threshold for each combination , where is the value of the priority field in a received SCI format 1-A and is the priority of the transmission of the UE selecting resources; for a given invocation of this procedure, . +- *sl-RS-ForSensing* selects if the UE uses the PSSCH-RSRP or PSCCH-RSRP measurement, as defined in clause 8.4.2.1. +- *sl-ResourceReservePeriodList* +- *sl-SensingWindow*: internal parameter is defined as the number of slots corresponding to *sl-SensingWindow* msec +- *sl-TxPercentageList*: internal parameter for a given is defined as *sl-TxPercentageList* () converted from percentage to ratio +- *sl-PreemptionEnable*: if *sl-PreemptionEnable* is provided, and if it is not equal to 'enabled', internal parameter is set to the higher layer provided parameter *sl-PreemptionEnable*. +- Optionally, minimum number of Y slots as (*sl-MinNumCandidateSlotsPeriodic*), which indicates the minimum number of Y slots that are included in the candidate resources corresponding to periodic-based partial sensing and contiguous partial sensing for resource (re)selection triggered by periodic transmission (). +- Optionally, minimum number of slots as (*sl-MinNumCandidateSlotsAperiodic*), which indicates the minimum number of slots that are included in the candidate resources corresponding to periodic-based partial sensing and/or contiguous partial sensing results (if available) for resource (re)selection triggered by aperiodic transmission (). +- Optionally, sensing occasion as *sl-PBPS-OccasionReservePeriodList*, which indicates the subset of periodicity values from *sl-ResourceReservePeriodList* used to determine periodic sensing occasions in periodic-based partial sensing. If not configured, all periodicity values from *sl-ResourceReservePeriodList* are used to determine periodic sensing occasions in periodic-based partial sensing. +- Optionally, additional sensing occasions as *sl-Additional-PBPS-Occasion*, which indicates that UE additionally monitors periodic sensing occasions that correspond to a set of values. The possible values of the set at least includes the most recent sensing occasion before the first slot of the candidate slots subject to processing time restriction as specified below for a given reservation periodicity and the last periodic sensing occasion prior to the most recent one for the given reservation periodicity. If not (pre-)configured, the UE monitors the most recent sensing occasion before the first slot of the candidate slots subject to processing time restriction as specified below for the given periodicity used to determine periodic sensing occasions in periodic-based partial sensing. +- Optionally, indication of the size in logical slots of contiguous partial sensing window for periodic transmissions as defined by the parameter *sl-CPS-WindowPeriodic*. +Optionally, indication of the size in logical slots of contiguous partial sensing window for aperiodic transmissions as defined by the parameter *sl-CPS-WindowAperiodic*. +- Optionally, indication of whether UE is required to perform SL reception of PSCCH and RSRP measurement for partial sensing on slots in SL DRX inactive time as *sl-PartialSensingInactiveTime*. + +In case of dynamic co-channel coexistence of LTE sidelink and NR sidelink, that is coexistence over time and frequency resources that are shared between NR sidelink and LTE sidelink: + +- *sl-NRPSSCH-EUTRA-ThresRSRP-List*: this higher layer parameter provides an RSRP threshold for each combination , where is the value of the priority field in a received LTE SCI format 1, and is the priority of the transmission of the UE selecting resources; for a given invocation of this procedure, . +- *sl-NRPSFCH-EUTRA-ThresRSRP-List*: this higher layer parameter, if provided, provides an RSRP threshold for each combination , where is the value of the priority field in a received LTE SCI format 1, and is the priority of the transmission of the UE selecting resources; for a given invocation of this procedure, . + +The resource reservation interval, , if provided, is converted from units of msec to units of logical slots, resulting in according to clause 8.1.7. + +When the resource pool is (pre-)configured with *sl-AllowedResourceSelectionConfig* including full sensing, and full sensing is configured in the UE by higher layers, the UE performs full sensing. + +When periodic reservation for another TB (*sl-MultiReserveResource*) is enabled for the resource pool, the resource pool is (pre-)configured with *sl-AllowedResourceSelectionConfig* including partial sensing, and partial sensing is configured by higher layer, the UE performs periodic-based partial sensing, unless other conditions state otherwise in the specification. + +When a UE is triggered by higher layer to report resources for resource (re-)selection in a mode 2 Tx pool, the resource pool is (pre-)configured with *sl-AllowedResourceSelectionConfig* including partial sensing, and partial sensing is configured by higher layer, the UE performs contiguous partial sensing, unless stated otherwise in the specification. + +Notation: + +denotes the set of slots which belongs to the sidelink resource pool and is defined in Clause 8. + +For dynamic co-channel coexistence of LTE sidelink and NR sidelink, denotes the set of subframes that may belong to an LTE sidelink resource pool as defined in clause 14.1.5 of [19, TS36.213]. + +The following steps are used: + +- 1) If a number of consecutive slots is provided with a value larger than 1, the candidate multi-slot resource definition is applied. Otherwise, the candidate single-slot resource definition is applied. + +If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'contiguousRB', a candidate multi-slot resource is defined as a set of contiguous sub-channels starting from sub-channel in consecutive slots starting from slot , when the set of slots that are consecutive in physical slots. + +If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'interlaceRB', a candidate multi-slot resource is defined as a set of contiguous sub-channels starting from sub-channel in consecutive slots starting from slot in contiguous RB sets starting from RB set z, when the set of slots that are consecutive in physical slots. A candidate single-slot resource is defined as a set of contiguous sub-channels starting from sub-channel in slot in contiguous RB sets starting from RB set z. + +If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is not provided or if the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'contiguousRB', a candidate single-slot resource for transmission is defined as a set of contiguous sub-channels with sub-channel $x+j$ in slot where . The UE shall assume that any set of contiguous sub-channels or contiguous sub-channels in contiguous RB sets included in the corresponding resource pool within the time interval correspond to one candidate single-slot resource or the UE shall assume that any set of contiguous sub-channels or contiguous sub-channels in contiguous RB sets in consecutive slots included in the corresponding resource pool within the time interval correspond to one candidate multi-slot resource for UE performing full sensing. The UE shall assume that any set of contiguous sub-channels included in the corresponding resource pool in a set of $Y$ candidate slots within the time interval correspond to one candidate single-slot resource or one candidate multi-slot resource for UE performing periodic-based partial sensing together with contiguous partial sensing and resource (re)selection triggered by periodic transmission (), or in a set of $Y'$ candidate slots within the time interval correspond to one candidate single-slot resource or one candidate multi-slot resource for UE performing at least contiguous partial sensing and resource (re)selection triggered by aperiodic transmission (), where + +- selection of is up to UE implementation under , where is defined in slots in Table 8.1.4-2 where is the SCS configuration of the SL BWP; +- if is shorter than the remaining packet delay budget (in slots) then is up to UE implementation subject to remaining packet delay budget (in slots); otherwise is set to the remaining packet delay budget (in slots). +- is selected by UE where . +- is selected by UE where . When the UE performs at least contiguous partial sensing and if , the UE selects a set of candidate slots with corresponding PBPS and/or CPS results (if available). If the number of candidate slots is smaller than , it is up to UE implementation to include other candidate slots. + +If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'contiguousRB', the UE shall exclude candidate single-slot or candidate multi-slot resources with the sub-channel with the smallest index including resource blocks of the intra-cell guardband PRBs, configured by higher layer parameter, *intraCellGuardBandsSL-List*, or determined according to the nominal intra-cell guard band and RB set pattern as specified in [8, TS 38.101-1] when higher layer parameter, *intraCellGuardBandsSL-List*, is not configured. + +If *rbSetsWithConsecutiveLBTFailure* is provided, the UE shall exclude candidate single-slot resources or candidate multi-slot resources, whose associated one or more RB set(s) is included in the *rbSetsWithConsecutiveLBTFailure* parameter. + +The total number of remaining candidate single-slot resources or candidate multi-slot resources is denoted by $\tilde{Y}$ . + +- 2) The sensing window is defined by the range of slots $[n, n+W]$ , when the UE performs full sensing, where $n$ is defined above and $W$ is defined in slots in Table 8.1.4-1 where $\mu$ is the SCS configuration of the SL BWP. The UE shall monitor slots which belongs to a sidelink resource pool within the sensing window except for those in which its own transmissions occur. The UE shall perform the behaviour in the following steps based on PSCCH decoded and RSRP measured in these slots. + +When the UE performs periodic-based partial sensing, the UE shall monitor slots at $n$ , where $n$ is a slot of the selected candidate slots and $n$ is converted to units of logical slot according to clause 8.1.7. The UE shall perform the behaviour in the following steps based on PSCCH decoded and RSRP measured in these slots. + +The value of $Y$ corresponds to *sl-PBPS-OccasionReservePeriodList* if (pre-)configured, otherwise, the values correspond to all periodicity from *sl-ResourceReservePeriodList*. + +The UE monitors sensing occasion(s) determined by *sl-Additional-PBPS-Occasion*, as previously described, and not earlier than $n$ . For a given periodicity $\mu$ , the values of $k$ correspond to the most recent sensing occasion earlier than $n$ if *sl-Additional-PBPS-Occasion* is not (pre-)configured, and additionally includes the value of $k$ corresponding to the last periodic sensing occasion prior to the most recent one if *sl-Additional-PBPS-Occasion* is (pre-)configured. $n$ is the first slot of the selected $Y$ candidate slots of PBPS. + +When the UE performs periodic-based partial sensing and contiguous partial sensing with periodic reservation for another TB (*sl-MultiReserveResource*) enabled and $\mu$ , the contiguous partial sensing window is defined by the range of slots $[n+T_A, n+T_B]$ where $n+T_A$ is $M$ consecutive logical slots earlier than slot $n$ , and $n+T_B$ is slots earlier than $n$ , where $n$ is the first slot of the selected $Y$ candidate slots of PBPS, and $T_A$ and $T_B$ are in units of physical time/slots. The value of $M$ is (pre-)configured with the *sl-CPS-WindowPeriodic*. The UE shall perform the behaviour in the following steps based on PSCCH decoded and RSRP measured in these slots. If *sl-CPS-WindowPeriodic* is not (pre-)configured, $M$ equals to 31. + +When the UE performs at least contiguous partial sensing and if $\mu$ , the contiguous partial sensing window is defined by the range of slots $[n, n+W]$ . $n$ and $W$ are both selected such that the UE has sensing results starting at least $M$ consecutive logical slots before $n$ and ending at $n+W$ slots earlier than $n$ , where $n$ is the first slot of the selected candidate slots. The value of $M$ is (pre-)configured with the *sl-CPS-WindowAperiodic*. The UE shall perform the behaviour in the following steps based on PSCCH decoded and RSRP measured in these slots. If *sl-CPS-WindowAperiodic* is not (pre-)configured, $M$ equals to 31. When the minimum $M$ slots for CPS cannot be guaranteed and when $\mu$ , it is up to UE implementation to either continue with step 3) or perform random selection. + +Whether the UE is required to perform SL reception of PSCCH and RSRP measurement for partial sensing on slots in SL DRX inactive time is enabled/disabled by higher layer parameter *sl-PartialSensingInactiveTime*. When it is enabled, if UE performs periodic-based partial sensing on the slots in SL DRX inactive time for a given periodicity corresponding to $\mu$ , UE monitors only the default periodic sensing occasions (most recent sensing occasion) from the slots; if UE performs contiguous partial sensing on the slots in SL DRX inactive time, UE monitors a minimum of $M$ slots from the slots. + +- 2LTE1) In case of dynamic co-channel coexistence of LTE sidelink and NR sidelink: The UE uses information determined by the E-UTRA radio access within the range of LTE subframes $[n, n+W]$ , where $n$ is an LTE subframe no later than LTE subframe $n$ is the LTE subframe, $n$ is the LTE subframe which overlaps slot $n$ , $W$ is 1100 msec and $W$ is up to UE implementation under $\mu$ ; $W$ is $4+T$ msec, where $T \leq 4$ msec. The UE shall perform the procedures in 5LTE1, 5LTE3 and 6LTE based on the information for these LTE subframes which is known to the NR radio access at the latest $T$ msec prior to slot $n$ . + +2LTE2) In case of dynamic co-channel coexistence of LTE sidelink and NR sidelink: The UE shall perform the procedures in 5LTE2 based on the information determined by the E-UTRA radio access, which is known by the NR radio access at the latest $T$ msec prior to slot $n$ . + +3) The internal parameter is set to the corresponding value of RSRP threshold indicated by the $i$ -th field in *sl-Thres-RSRP-List*, where . + +3LTE) In case of dynamic co-channel coexistence of LTE sidelink and NR sidelink: + +- The internal parameter is set to the corresponding value of RSRP threshold indicated by the $i$ -th field in *sl-NRPSSCH-EUTRA-ThresRSRP-List*, where . +- The internal parameter is set to the corresponding value of RSRP threshold indicated by the $i$ -th field in *sl-NRPSFCH-EUTRA-ThresRSRP-List*, if provided, where . If *sl-NRPSFCH-EUTRA-ThresRSRP-List* is not provided then each element of is set to minus Infinity dBm. + +4) The set is initialized to the set of all the remaining candidate single-slot resources or candidate multi-slot resources identified in step 1. + +5) The UE shall exclude any candidate single-slot resource or , or candidate multi-slot resource or from the set if it meets all the following conditions: + +- the UE has not monitored slot in Step 2. +- for any periodicity value allowed by the higher layer parameter *sl-ResourceReservePeriodList* and a hypothetical SCI format 1-A received in slot with '*Resource reservation period*' field set to that periodicity value and indicating all subchannels of the resource pool in this slot, condition c in step 6 would be met. + +5LTE1) In case of dynamic co-channel coexistence of LTE sidelink and NR sidelink: The UE shall exclude any candidate single-slot resource from the set if all the following conditions are met: + +- the resource pool overlaps with an LTE sidelink resource pool; +- the UE has not monitored LTE subframe . +- for any periodicity value allowed by the LTE higher layer parameter *restrictResourceReservationPeriod* and a hypothetical LTE SCI format 1 received in LTE subframe with '*Resource reservation*' field set to that periodicity value and indicating all subchannels of the LTE sidelink resource pool in this LTE subframe, condition c in step 6LTE would be met. + +5LTE2) In case of dynamic co-channel coexistence of LTE sidelink and NR sidelink: The UE shall exclude any candidate single-slot resource from the set if all the following conditions are met: + +- the UE has a selected sidelink grant for LTE V2X sidelink according to [19, TS 36.321] . +- the selected sidelink grant for LTE V2X sidelink determines the set of LTE resource blocks and LTE subframes which overlaps in time with for $j=0, 1, \dots, ;$ +- the priority value associated with the selected sidelink grant for LTE V2X sidelink is lower than ; It is up to UE implementation whether or not to apply this exclusion step if the priority value associated with selected sidelink grant for LTE V2X sidelink is higher than or equal to . + +5LTE3) In case of dynamic co-channel coexistence of LTE sidelink and NR sidelink: The UE shall exclude any candidate single-slot resource from the set if all the following conditions are met: + +- a) the resource pool is configured with PSFCH resources; +- b) an LTE SCI format 1 is received in LTE subframe , and the '*Resource reservation*' field and '*Priority*' field in the received LTE SCI format 1 indicate the values and , respectively according to Clause 14.2.1 in [19, TS 36.213], where LTE subframes are indexed according to Clause 14.1.5 in [19, TS 36.213]; +- c) the LTE PSSCH-RSRP measurement according to the received LTE SCI format 1 is higher than +- d) the SCI format received in LTE subframe or the same SCI format which is assumed to be received in LTE subframe(s) determines according to clause 14.1.1.4C or clause 14.2.4 in [19, TS 36.213] the set of LTE + +subframes which overlaps with PSFCH slots associated with for $q=1, 2, \dots, Q$ and $j=0, 1, \dots$ , where the PSFCH association is according to [6, TS 38.213]. and $Q$ are determined as in condition c) of step 6LTE. + +- 5a) If the number of candidate single-slot resources or , or the number of candidate multi-slot resource or remaining in the set is smaller than , the set is initialized to the set of all the candidate single-slot resources or candidate multi-slot resources as in step 4. +- 6) The UE shall exclude any candidate single-slot resource or , or candidate multi-slot resource or from the set if it meets all the following conditions: +- the UE receives an SCI format 1-A in slot , and 'Resource reservation period' field, if present, and 'Priority' field in the received SCI format 1-A indicate the values and , respectively according to Clause 16.4 in [6, TS 38.213]; + - the RSRP measurement performed, according to clause 8.4.2.1 for the received SCI format 1-A, is higher than + - the SCI format received in slot or the same SCI format which, if and only if the 'Resource reservation period' field is present in the received SCI format 1-A, is assumed to be received in slot(s) determines according to clause 8.1.5 the set of resource blocks and slots which overlaps with or for $q=1, 2, \dots, Q$ and $j=0, 1, \dots$ . Here, is converted to units of logical slots according to clause 8.1.7, if and , where if the UE is configured with full sensing by its higher layer, if slot $n$ belongs to the set , otherwise slot is the first slot after slot $n$ belonging to the set ; If UE is configured with partial sensing by its higher layer, if slot belongs to the set , otherwise, slot is the first slot after slot belonging to the set . Otherwise . If the UE is configured with full sensing by its higher layer, is set to selection window size $T_2$ converted to units of msec. If UE is configured with partial sensing by its higher layer, shall be converted to milliseconds, where slot is the last slot of the or candidate slots. The slot is the first slot of the selected/remaining set of or candidate slots. +- 6LTE) In case of dynamic co-channel coexistence of LTE sidelink and NR sidelink: The UE shall exclude any candidate single-slot resource from the set if all the following conditions are met: +- an LTE SCI format 1 is received in LTE subframe , and the 'Resource reservation' field and 'Priority' field in the received LTE SCI format 1 indicate the values and , respectively according to Clause 14.2.1 in [19, TS 36.213], where LTE subframes are indexed according to Clause 14.1.5 in [19, TS 36.213]; + - the LTE PSSCH-RSRP measurement according to the received LTE SCI format 1 is higher than + - the SCI format received in LTE subframe or the same SCI format which is assumed to be received in LTE subframe(s) determines according to clause 14.1.1.4C or clause 14.2.4 in [19, TS 36.213] the set of LTE resource blocks and LTE subframes which overlaps with for $q=1, 2, \dots, Q$ and $j=0, 1, \dots$ . Here, is with determined according to Table 14.1.1-1 in [19, TS 36.213], if and , where if subframe belongs to the set , otherwise subframe is the first subframe after subframe belonging to the set ; Otherwise . is set to selection window size $T_2$ converted to units of msec. +- 6a) This step is executed only if the procedure in clause 8.1.4A is triggered. +- 6b) This step is executed only if the procedure in clause 8.1.4C is triggered. +- 7) If the number of candidate single-slot resources or candidate multi-slot resources remaining in the set is smaller than , then and , if set, is increased by 3 dB for each priority value and the procedure continues with step 4. +- 7a) If sidelink DRX active time of RX UE is provided by the higher layer and there is no candidate single-slot or multi-slot resource remained within the sidelink DRX active time in the set , the UE based on its implementation additionally selects and includes at least one candidate single-slot resource or at least one candidate multi-slot resource within the sidelink DRX active time in the set . + +The UE shall report set to higher layers. + +If a resource from the set is not a member of , then the UE shall report re-evaluation of the resource to higher layers. + +If a resource from the set meets the conditions below then the UE shall report pre-emption of the resource to higher layers. + +- is not a member of , and + +- meets the conditions for exclusion in step 6, with $\text{set}$ to the final threshold after executing steps 1)-7), i.e. including all necessary increments for reaching $\text{set}$ , or for exclusion in step 6 LTE, with $\text{set}$ to the final threshold after executing steps 1-7, i.e. including all necessary increments for reaching $\text{set}$ , or for exclusion in step 5 LTE3, and +- the associated priority satisfies one of the following conditions: + - *sl-PreemptionEnable* is provided and is equal to 'enabled' and + - *sl-PreemptionEnable* is provided and is not equal to 'enabled', and $\text{set}$ and + +**Table 8.1.4-1: depending on sub-carrier spacing** + +| | [slots] | +|---|---------| +| 0 | 1 | +| 1 | 1 | +| 2 | 2 | +| 3 | 4 | + +**Table 8.1.4-2: depending on sub-carrier spacing** + +| | [slots] | +|---|---------| +| 0 | 3 | +| 1 | 5 | +| 2 | 9 | +| 3 | 17 | + +When the UE performs periodic-based partial sensing and contiguous partial sensing, and when the UE is triggered to perform re-evaluation and/or pre-emption checking, and if , + +- During the $q^{\text{th}}$ reservation period ( $q=0,1,2,\dots, C_{\text{resel}}-1$ ), candidate resource set ( $S_A$ ) is initialized to the remaining $Y$ candidate slots starting from slot $n$ and ending at the last slot of the $Y$ candidate slots, where the slot indices of the remaining $Y$ candidate slots are equal to $\text{set}$ , where $\text{set}$ is a slot index of $Y$ candidate slots used in the initial resource (re)selection. + - $\text{set}$ is the first candidate slot starting from slot $n+T_3$ . +- The UE performs PBPS for the remaining $Y$ candidate slots according to $\text{set}$ except for those in which its own transmissions occur, where $\text{set}$ is a slot belonging to the remaining $Y$ candidate slots, and $k$ and $P_{\text{reserve}}$ are the same as resource (re)selection, where the values of $k$ correspond to the most recent sensing occasion earlier than $\text{set}$ if *sl-Additional-PBPS-Occasion* is not (pre-)configured, and additionally includes the value of $k$ corresponding to the last periodic sensing occasion prior to the most recent one if *sl-Additional-PBPS-Occasion* is (pre-)configured. +- The UE performs CPS starting from $M$ logical slots earlier than $\text{set}$ to $\text{set}$ slots earlier than $\text{set}$ except for those in which its own transmissions occur. + - By default, $M$ is 31 unless (pre-)configured with another value by *sl-CPS-WindowPeriodic*. + +When the UE is triggered to perform re-evaluation and/or pre-emption checking, performs at least contiguous partial sensing, and if , + +- Candidate resource set ( $S_A$ ) is initialized to the remaining $Y'$ candidate slots starting from slot $n$ and ending at the last slot of the $Y'$ candidate slots, where $n$ is the first candidate slot starting from slot $n+T_3$ . +- It is up to UE implementation that UE may perform PBPS for periodic sensing occasions after the resource (re)selection when higher layer parameter *sl-MultiReserveResource* is enabled. +- UE performs CPS starting from at least $M$ consecutive logical slots earlier than $n$ to slots earlier than $n$ except for those in which its own transmissions occur. +- For minimum size $M$ of the contiguous partial sensing window, by default, $M$ is 31 unless (pre-)configured with another value, by *sl-CPS-WindowAperiodic*. + +When the minimum $M$ slots for CPS cannot be guaranteed, UE senses in all available slots starting from the resource (re)selection trigger slot of the same TB to slots earlier than $n$ . The UE re-evaluation and pre-emption checking is based on all available sensing results after $n$ . + +### 8.1.4A UE procedure for determining a set of preferred or non-preferred resources for another UE's transmission + +When this procedure is triggered, the following parameters are provided by the higher layer: + +- the resource pool from which the preferred or non-preferred resources are to be determined; +- the resource selection window within which the preferred or non-preferred resources are to be determined; +- the resource set type (either preferred or non-preferred resource set); +- if the resource set type indicates preferred set, then the higher layer additionally provides the following parameters: + - L1 priority, ; + - the number of sub-channels to be used for the PSSCH/PSCCH transmission in a slot, ; + - the resource reservation period, , if present. + +The value of $n$ is determined by the UE according to clause 8.1.5. + +When this procedure is triggered by another UE's explicit request, the fields in the request are interpreted as follows: + +- The field 'Resource selection window location' is the concatenation of the starting time location and the ending time location of the resource selection window. The starting and ending time locations of the resource selection window are each encoded in the same way as the reference slot as described in clause 8.1.5A. +- The field 'Resource reservation period' is encoded in the same way as the field of the same name in SCI format 1-A. + +When determining a preferred resource set, the UE applies the procedure described in clause 8.1.4 with the above parameters and the following modifications: + +- Step 6a) The UE excludes candidate single-slot resource(s) belonging to slot(s) where the UE does not expect to perform SL reception of a TB due to half-duplex operation, if all the following conditions are met: + - the UE is a destination UE of the TB for whose transmission the preferred resource set is being determined; + - the higher layer parameter *sl-Condition1-A-2* is not set to 'Disabled'. + +When determining a non-preferred resource set, the UE considers any resource(s) within the resource selection window, if indicated by a received explicit request, and satisfying at least one of the following conditions as non-preferred resource(s): + +- resource(s) indicated by a received [SCI format 1-A], satisfying at least one of the following criteria: + +- the RSRP measurement performed, according to clause 8.4.2.1, for the received [SCI format 1-A], is higher than $\text{sl-ThresholdRSRP-Condition1-B-1-Option1List}$ where $\text{sl-ThresholdRSRP-Condition1-B-1-Option1List}$ is the value of the priority field in the received [SCI format 1-A]. The internal parameter is set to the corresponding value of RSRP threshold indicated by the $k$ -th field in $\text{sl-ThresholdRSRP-Condition1-B-1-Option1List}$ , where . +- the UE is a destination UE of a TB associated with the received [SCI format 1-A] and the RSRP measurement performed, according to clause 8.4.2.1 for the received [SCI format 1-A], is lower than $\text{sl-ThresholdRSRP-Condition1-B-1-Option2List}$ where $\text{sl-ThresholdRSRP-Condition1-B-1-Option2List}$ is the value of the priority field in the received [SCI format 1-A]. The internal parameter is set to the corresponding value of RSRP threshold indicated by the $k$ -th field in $\text{sl-ThresholdRSRP-Condition1-B-1-Option2List}$ , where . +- resources(s) in slot(s) in which the UE does not expect to perform SL reception due to half duplex operation, if the UE is a destination UE of a TB for whose transmission the non-preferred resource set is being determined. + +### 8.1.4B Void + +### 8.1.4C UE procedure for using a received non-preferred resource set + +A UE configured with the higher layer parameter $\text{sl-InterUE-CoordinationScheme1}$ uses a received non-preferred resource set as follows when performing resource (re-)selection: + +- the UE excludes in Step 6b) of clause 8.1.4 resource(s) overlapping with the non-preferred resource set. + +If it is not possible to meet the requirement that the number of candidate single-slot resources remaining in the set be at least after excluding resource(s) overlapping with the received non-preferred resource set, it is up to UE implementation whether or not to take into account the received non-preferred resource set to meet such requirement. + +The UE is not required to use any resource from the non-preferred resource set in its resource (re-)selection if that resource is earlier than $(++)$ after the resource of inter-UE coordination information transmission, where $(++)$ is equal to $(++)$ when only MAC CE is used for inter-UE coordination information transmission, or $(++)$ is equal to $(++)$ when MAC CE and SCI format 2-C are both used for inter-UE coordination information transmission. + +The case when $(++)$ is equal to $(++)$ is assuming that SCI format 2-C is received. + +### 8.1.5 UE procedure for determining slots and resource blocks for PSSCH transmission associated with an SCI format 1-A + +The set of slots and resource blocks for PSSCH transmission is determined by the resource used for the PSCCH transmission containing the associated SCI format 1-A, and fields '*Frequency resource assignment*', '*Time resource assignment*' of the associated SCI format 1-A as described below. + +'*Time resource assignment*' carries logical slot offset indication of $N = 1$ or 2 actual resources when $\text{sl-MaxNumPerReserve}$ is 2, and $N = 1$ or 2 or 3 actual resources when $\text{sl-MaxNumPerReserve}$ is 3, in a form of time RIV (TRIV) field which is determined as follows: + +``` + +if + +elseif + +else + if + + else + +end if + +``` + +end if + +where the first resource is in the slot where SCI format 1-A was received, and denotes $i$ -th resource time offset in logical slots of a resource pool with respect to the first resource where for $N = 2, ;$ and for $N = 3, , .$ + +The starting sub-channel of the first resource is determined according to clause 8.1.2.2. The number of contiguously allocated sub-channels for each of the $N$ resources and the starting sub-channel indexes of resources indicated by the received SCI format 1-A, except the resource in the slot where SCI format 1-A was received, are determined from "Frequency resource assignment" which is equal to a frequency RIV (FRIV) where. + +If *sl-MaxNumPerReserve* is 2 then + +If *sl-MaxNumPerReserve* is 3 then + +where + +- denotes the starting sub-channel index for the second resource +- denotes the starting sub-channel index for the third resource +- is the number of sub-channels in a resource pool, or if the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'interlaceRB', the number of sub-channels in each RB set, provided according to the higher layer parameter *sl-NumSubchannel* + +If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'interlaceRB', the applied interlace index(s) in different RB sets are the same. + +If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'interlaceRB', the starting RB set of the first resource is determined according to the clause 8.1.2.2. The number of contiguously allocated RB sets for each of the $N$ resources $L_{RBset} \geq 1$ and the starting RB set indexes of resources indicated by the received SCI format 1-A, except the resource in the slot where SCI format 1-A was received, are determined from "Frequency resource assignment" which is equal to a frequency RIV (FRIV) where. + +If *sl-MaxNumPerReserve* is 2 then + +If *sl-MaxNumPerReserve* is 3 then + +where + +- denotes the starting RB set index for the second resource, +- denotes the starting RB set index for the third resource, +- is the number of RB sets in a resource pool, +- is the number of RB sets for each of the indicated resources, +- for FRIV indication, within the resource pool, RB sets are numbered in increasing order from 0 to from lowest frequency location to highest frequency location. + +If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'interlaceRB', the resource is determined by an intersection of the interlaces corresponding to the indicated sub-channel(s) and the union of the indicated set of RB sets and intra-cell guard bands between the indicated RB sets, if any. + +If TRIV indicates $N < sl-MaxNumPerReserve$ , the starting sub-channel indexes corresponding to *sl-MaxNumPerReserve* minus $N$ last resources are not used. + +The number of slots in one set of the time and frequency resources for transmission opportunities of PSSCH is given by where $= 10 * SL\_RESOURCE\_RESELECTION\_COUNTER [10, TS 38.321]$ if configured else is set to 1. + +If a set of sub-channels in slot $j$ is determined as the time and frequency resource for PSSCH transmission corresponding to the selected sidelink grant (described in [10, TS 38.321]), the same set of sub-channels in slots $j+1, j+2, \dots, j+K$ , if provided, is converted from units of msec to units of logical slots, resulting in according to clause 8.1.7, and is determined by Clause 8. Here, $K$ is the resource reservation interval indicated by higher layers. + +### 8.1.5A UE procedure for determining slots and resource blocks indicated by a preferred or non-preferred resource set + +The set of slots and resource blocks indicated by a set of preferred or non-preferred resource(s) is determined as described below. + +If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is not provided, or it is set to 'contiguousRB', the set of preferred or non-preferred resources, is indicated by a reference slot and tuples, indicated by the 'resource combination' field, where for each tuple is indicated by the 9 MSBs, followed by and (if present). + +If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'interlaceRB', the set of preferred or non-preferred resources, is indicated by a reference slot and tuples, indicated by the 'resource combination' field, where for each tuple is indicated by the 9 MSBs, followed by , and (if present). + +The reference slot is indicated by the 'Reference slot location' field as a combination of DFN index and slot index [5, TS 38.212], with the 10 MSBs indicating the DFN index, and if any are interpreted according to clause 8.1.5, with the following modifications: + +- the value of *sl-MaxNumPerReserve* is fixed to 3. +- "slot where SCI format 1-A was received" is replaced by slot indicated as the first resource location of a . +- the first resource location of each for is indicated by a slot offset in logical slots with respect to the reference slot; the slot offset is indicated by the 'first resource location' field; the first resource location of is at slot offset 0 with respect to the reference slot. +- "the received SCI format 1-A, except the resource in the slot where SCI format 1-A was received" is replaced by "each tuple". +- the starting sub-channel of the first resource of each tuple is separately indicated. +- if the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'interlaceRB', the starting RB set of the first resource of each tuple is separately indicated. + +The starting sub-channel of the first resource of each tuple is indicated by the 'Lowest subChannel indices' field. The starting RB set of the first resource of each tuple, if any, is indicated by the 'Lowest RB set indices' field. The resource reservation period is encoded as in SCI format 1-A. + +If the set is indicated by an SCI format 2-C, the number of tuples is . + +If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is not provided, or it is set to 'contiguousRB', a UE forms the union of the subsets indicated by each tuple to obtain the set . + +If the higher layer parameter *transmissionStructureForPSCCHandPSSCH* is set to 'interlaceRB', a UE forms the union of the subsets indicated by each tuple to obtain the set . + +### 8.1.6 Sidelink congestion control in sidelink resource allocation mode 2 + +If a UE is configured with higher layer parameter *sl-CR-Limit* and transmits PSSCH in slot $n$ , the UE shall ensure the following limits for any priority value $k$ : + +where is the CR evaluated in slot $n-N$ for the PSSCH transmissions with 'Priority' field in the SCI set to $i$ , and corresponds to the high layer parameter *sl-CR-Limit* that is associated with the priority value $k$ and the CBR range which includes the CBR measured in slot $n-N$ , where $N$ is the congestion control processing time. + +The congestion control processing time $N$ is based on $\mu$ of Table 8.1.6-1 and Table 8.1.6-2 for UE processing capability 1 and 2 respectively, where $\mu$ corresponds to the subcarrier spacing of the sidelink channel with which the PSSCH is to be transmitted. A UE shall only apply a single processing time capability in sidelink congestion control. + +**Table 8.1.6-1: Congestion control processing time for processing timing capability 1** + +| $\mu$ | Congestion control processing time $N$ [slots] | +|-------|------------------------------------------------| +| 0 | 2 | +| 1 | 2 | +| 2 | 4 | +| 3 | 8 | + +**Table 8.1.6-2: Congestion control processing time for processing timing capability 2** + +| $\mu$ | Congestion control processing time $N$ [slots] | +|-------|------------------------------------------------| +| 0 | 2 | +| 1 | 4 | +| 2 | 8 | +| 3 | 16 | + +It is up to UE implementation how to meet the above limits, including dropping the transmissions in slot $n$ . + +## 8.1.7 UE procedure for determining the number of logical slots for a reservation period + +A given resource reservation period in milliseconds is converted to a period in logical slots as: + +where $N_{\text{slots}}$ is the number of slots that belong to a resource pool as defined in Clause 8. + +# 8.2 UE procedure for transmitting sidelink reference signals + +## 8.2.1 CSI-RS transmission procedure + +A UE transmits sidelink CSI-RS within a unicast PSSCH transmission if the following conditions hold: + +- CSI reporting is enabled by higher layer parameter *sl-CSI-Acquisition*; and +- the 'CSI request' field in the corresponding SCI format 2-A, 2-C or 2-D is set to 1. + +The following parameters for CSI-RS transmission are configured for each CSI-RS configuration: + +- *sl-CSI-RS-FirstSymbol* indicates the first OFDM symbol in a PRB used for SL CSI-RS +- *sl-CSI-RS-FreqAllocation* indicates the number of antenna ports and the frequency domain allocation for SL CSI-RS. + +When the UE is configured with $Q_p=\{1,2\}$ CSI-RS port(s) in sidelink and the number of scheduled layers is $L$ , + +- The CSI-RS scaling factor specified in clause 8.4.1.5.3 of [4, TS 38.211] is given by $\alpha$ where $\alpha$ is the scaling factor for the corresponding PSSCH specified in clause 8.3.1.5 of [4, TS 38.211]. + +## 8.2.2 PSSCH DM-RS transmission procedure + +The UE selects the DM-RS time domain pattern out of the patterns configured using the higher layer parameter *sl-PSSCH-DMRS-TimePatternList* for the resource pool on which the PSSCH is to be transmitted. If more than one DM-RS time domain pattern is configured, the selected pattern is indicated by the 'DMRS pattern' field in the SCI format 1-A associated with the PSSCH transmission. + +If PSSCH DM-RS and PSCCH are mapped to the same OFDM symbol, then this mapping within a single sub-channel is only supported if higher layer parameter *sl-SubchannelSize* $\geq 20$ , i.e. the sub-channel size is at least 20 PRBs. + +When a sub-channel size is less than 20 PRBs and the size of PSCCH is less than the sub-channel size, a UE is not expected to choose a PSSCH DM-RS pattern to be transmitted in the same OFDM symbol with PSCCH. + +### 8.2.3 PT-RS transmission procedure + +Transmission of PT-RS is only supported in frequency range 2. + +The UE PT-RS transmission procedure specified in clause 6.2.3.1 applies for derivation of the PT-RS parameters *LPT-RS* and *KPT-RS* and for determination of PT-RS presence, with the following changes: + +- *timeDensity* and *frequencyDensity* in *PTRS-UplinkConfig* are replaced by *sl-PTRS-TimeDensity* and *sl-PTRS-FreqDensity* in *SL-PTRS-Config* respectively, and *SL-PTRS-Config* is (pre)configured per resource pool; +- the number of antenna ports is the same as the number of PSSCH DM-RS antenna ports and the association between a PT-RS antenna port and a PSSCH DM-RS antenna port is fixed. +- In a shared SL PRS resource pool, transmission of PT-RS is cancelled in OFDM symbols with SL PRS. + +### 8.2.4 SL PRS transmission procedure + +The following parameters for SL PRS transmission are associated with each SL PRS resource: + +- *[SL PRS resource ID]* indicates an identity of a SL PRS resource. The SL PRS resource is identified by the SL PRS resource ID that is unique within a slot of a dedicated SL PRS resource pool. For a shared SL PRS resource pool, a SL PRS resource is uniquely identified by a combination of the SL PRS resource ID, SL PRS frequency domain allocation within a slot indicated by “frequency resource assignment” field in the associated SCI format 1-A, and a starting symbol within the slot as determined by clause 8.2.4.1.1. +- *[SL PRS comb offset and comb size]* indicates a comb offset and a comb size of the SL PRS resource +- *[Starting symbol and the number of SL PRS symbols]* indicates the starting symbol index and the number of symbols of the SL PRS resource within a slot in a dedicated SL PRS resource pool. *[number of SL PRS symbols]* indicates the number of symbols of the SL PRS resource within a slot in a shared SL PRS resource pool. + +For a dedicated SL PRS resource pool, SL PRS resources for a same combination of number of SL PRS symbols and comb size can be mapped to a set of consecutive symbols in a slot. SL PRS resources for different combinations shall be mapped to non-overlapping sets of consecutive symbols in a slot. Up to four non-overlapping sets of consecutive symbols within a slot can be used to map SL PRS resources for same or different combinations, where the case of four non-overlapping sets of consecutive symbols only applies when for all the combinations. + +Each SL PRS transmission is associated with an PSCCH transmission in the same slot. + +In the case of dedicated SL PRS resource pool, that PSCCH carries the SCI format 1-B associated with the SL PRS transmission. + +The UE may report the association information between the already transmitted SL PRSs of SL PRS resources and UE Tx ARP ID. The association information includes ARP ID(s), SL PRS transmission timestamp(s) *[sl-prs-time-stamp]*, and optional SL PRS resource ID(s). + +#### 8.2.4.1 Resource allocation + +In sidelink resource allocation mode 1: + +- for SL PRS transmission, dynamic grant, configured grant type 1, and configured grant type 2 are supported. +- for a dedicated SL PRS resource pool, the UE shall perform the procedure described in clause 8.6 (excluding the case of PSSCH for retransmission of a transport block), with the following modifications: + - "PSSCH for a transport block" is replaced by "SL PRS" + - "PSSCH" is replaced by "SL PRS". + +The total number of SL configured grants including type 1 and type 2 across all resource pools is not greater than 8. + +#### 8.2.4.1.1 Resource allocation in time domain + +The UE shall transmit the SL PRS in the same slot as the associated PSCCH. + +For a dedicated SL PRS resource pool, the minimum resource allocation unit in the time domain is a SL PRS resource in a slot. + +The UE shall transmit the SL PRS in consecutive symbols within the slot. + +A UE does not transmit multiple SL PRS resources in the same slot. + +For a shared SL PRS resource pool, the UE transmits the SL PRS in PSSCH symbols according to clause 8.1.2.1, with the following restrictions: + +- the number of contiguous symbols for SL PRS transmission, , shall correspond to one of the SL PRS resources in parameter *sl-PrsResources-Shared-SL-PRS-RP*. +- the UE shall not transmit SL PRS in symbols where associated PSCCH is transmitted. +- the UE shall not transmit SL PRS and PSSCH DMRS in the same symbol. +- the UE shall not transmit SL PRS and SL CSI-RS in the same symbol. +- the UE shall transmit SL PRS on contiguous symbols either in between or after symbols where PSSCH DMRS is transmitted. +- the UE shall transmit SL PRS only after the last symbol with second stage SCI. +- For a given value of , SL PRS resource is mapped to the last consecutive SL symbols in the slot that meet all the other restrictions + +For a dedicated SL PRS resource pool, the UE transmits SL PRS subject to the following restrictions: + +- the UE shall not transmit SL PRS and associated PSCCH in the same symbol; +- the number of contiguous symbols and the starting symbol for SL PRS transmission shall correspond to one of the SL PRS resources in parameter []. + +In sidelink resource allocation mode 1 for a shared SL PRS resource pool, the time domain behaviour for sidelink dynamic grants and sidelink configured grants for SL PRS follows the behaviour in clause 8.1.2.1. + +In sidelink resource allocation mode 1 for a dedicated SL PRS resource pool, the time domain behaviour for sidelink dynamic grants and sidelink configured grants for SL PRS follows the behaviour in clause 8.1.2.1, with the following modifications: + +- "DCI format 3\_0" is replaced by "DCI format 3\_2". +- "PSSCH" is replaced by "SL PRS". + +#### 8.2.4.1.2 Resource allocation in frequency domain + +For a shared SL PRS resource pool, the frequency domain resource assignment of a SL PRS resource is the same as PSSCH in the same slot. + +For a dedicated SL PRS resource pool, the frequency domain resource assignment of a SL PRS resource is same as frequency resources of a resource pool provided by the higher layer parameter *sl-RB-Number*. + +#### 8.2.4.2 UE procedure for determining the subset of resources to be reported to higher layers in SL PRS resource selection in a dedicated SL PRS resource pool in sidelink resource allocation mode 2 + +In resource allocation mode 2 in a dedicated SL PRS resource pool, the higher layer can request the UE to determine a subset of resources from which the higher layer will select resources for SL PRS/PSCCH transmission. To trigger this procedure, in slot *n*, the higher layer provides the following parameters for this SL PRS/PSCCH transmission: + +- the resource pool from which the resources are to be reported; +- L1 priority, ; +- the remaining [delay budget]; +- Set of SL-PRS resource ID(s); +- optionally, the resource reservation interval, , in units of msec. +- if the higher layer requests the UE to determine a subset of resources from which the higher layer will select resources for SL PRS[/PSCCH] transmission as part of re-evaluation or pre-emption procedure, the higher layer provides a set of resources which may be subject to re-evaluation and a set of resources which may be subject to pre-emption. + - it is up to UE implementation to determine the subset of resources as requested by higher layers before or after the slot - , where is the slot with the smallest slot index among and , and is equal to , where is defined in slots in Table 8.1.4-2 where is the SCS configuration of the SL BWP. + +The following higher layer parameters affect this procedure: + +- *[sl-SelectionWindowList]*: internal parameter is set to the corresponding value from higher layer parameter *sl-SelectionWindowList* for the given value of .] +- *[sl-Thres-RSRP-List]*: this higher layer parameter provides an RSRP threshold for each combination , where is the value of the priority field in a received SCI format 1-B and is the priority of the transmission of the UE selecting resources; for a given invocation of this procedure, . +- *[reservationPeriodAllowed-Dedicated-SL-PRS-RP]* +- *[sl-SensingWindow]*: internal parameter is defined as the number of slots corresponding to *sl-SensingWindow* msec +- *[sl-TxPercentageList]*: internal parameter for a given is defined as *sl-TxPercentageList* () converted from percentage to ratio +- *[sl-PreemptionEnable]*: if *sl-PreemptionEnable* is provided, and if it is not equal to 'enabled', internal parameter is set to the higher layer provided parameter *sl-PreemptionEnable*. + +The UE shall perform this procedure according to clause 8.1.4, with the following modifications: + +- "packet delay budget" is replaced by "SL PRS delay budget", +- partial sensing is not applicable in a dedicated SL PRS resource pool, +- "candidate single-slot resource" is replaced by "candidate SL PRS resource", +- a candidate single-slot resource for transmission is defined as the SL PRS resource with index within the Set of SL-PRS resource ID(s) provided by the higher layer and in slot , +- "SCI format 1-A" is replaced by "SCI format 1-B", +- in step 5, the second condition is modified as follows: for any periodicity value allowed by the higher layer parameter *reservationPeriodAllowed-Dedicated-SL-PRS-RP* and any SL PRS resource ID in the set of SL PRS resource ID(s) provided by the higher layer, and a hypothetical SCI format 1-B received in slot with '*Resource reservation period*' field set to that periodicity value and indicating that SL-PRS resource ID, condition c in step 6 would be met, +- In condition b of step 6, the RSRP measurement is the PSCCH-RSRP over the DM-RS resource elements of the PSSCH; +- In condition c of step 6 "determines according to clause 8.1.5 the set of resource blocks and slots" is replaced by "determines according to clause 8.2.4.2A the set of SL PRS resources and slots ". + +#### 8.2.4.2A UE procedure for determining slots and SL PRS resource(s) associated with an SCI format 1-B in a dedicated SL PRS resource pool + +The set of slots and SL PRS resources for SL PRS transmission is determined by the PSCCH containing the associated SCI format 1-B, and fields '[*SL-PRS resource ID (s)*]', '[*Time resource assignment*]' of the associated SCI format 1-B as described below. + +The set of slots is determined as in clause 8.1.5, with the following modifications: + +- "SCI format 1-A" is replaced by "SCI format 1-B", +- [potential parameter name changes]. + +The first SL PRS resource is determined according to the sub-channel used for the PSCCH transmission containing the associated SCI format 1-B, where the index of the sub-channel in the resource pool is identical to the index of the SL PRS resource provided by [higher layer parameter]. + +The second SL-PRS and third SL PRS resource, if reserved by SCI format 1-B, are determined from " Resource ID indication" which is equal to a PRS Resource ID value (PRIV) where, + +If [*sl-MaxNumPerReserve*] is 2 then + +If [*sl-MaxNumPerReserve*] is 3 then + +Where + +- denotes the SL PRS resource ID for the second resource +- denotes the SL PRS resource ID for the third resource +- is the number of SL-PRS resources (pre-)configured in a slot of a resource pool. + +If TRIV determined according to clause 8.1.5 indicates $N < sl\text{-}MaxNumPerReserve$ , the SL PRS resource indices corresponding to *sl-MaxNumPerReserve* minus N last resources are not used. + +The number of slots in one set of the time and frequency resources for transmission opportunities of SL PRS is given by where $= 10 * SL\_RESOURCE\_RESELECTION\_COUNTER$ [10, TS 38.321] if configured else is set to 1. + +If a SL PRS resource in slot is determined as the time and frequency resource for SL PRS transmission corresponding to the selected sidelink grant (described in [10, TS 38.321]), the same SL PRS resource in slots is also determined for SL PRS transmissions corresponding to the same sidelink grant where $j=1, 2, \dots$ , if provided, is converted from units of msec to units of logical slots, resulting in according to clause 8.1.7, and is determined by Clause 8. Here, is the resource reservation interval indicated by higher layers. + +#### 8.2.4.3 Sidelink congestion control in a dedicated SL PRS resource pool in sidelink resource allocation mode 2 + +When transmitting SL-PRS in a dedicated SL PRS resource pool the UE shall perform sidelink congestion control as specified in clause 8.1.6, with the following modification(s): + +- "PSSCH" is replaced by "SL PRS" +- [potential parameter name changes] +- [potential changes to processing times] + +## 8.3 UE procedure for receiving the physical sidelink shared channel + +For sidelink resource allocation mode 1, a UE upon detection of SCI format 1-A on PSCCH can decode PSSCH according to the detected SCI formats 2-A, 2-B, 2-C and 2-D, and associated PSSCH resource configuration configured by higher layers. The UE is not required to decode more than one PSCCH at each PSCCH resource candidate. + +For sidelink resource allocation mode 2, a UE upon detection of SCI format 1-A on PSCCH can decode PSSCH according to the detected SCI formats 2-A, 2-B, 2-C and 2-D, and associated PSSCH resource configuration configured by higher layers. The UE is not required to decode more than one PSCCH at each PSCCH resource candidate. + +A UE is required to decode neither the corresponding SCI formats 2-A, 2-B, 2-C nor the PSSCH associated with an SCI format 1-A if the SCI format 1-A indicates an MCS table that the UE does not support. + +## 8.4 UE procedure for receiving reference signals + +### 8.4.1 CSI-RS reception procedure + +The CSI-RS defined in Clause 8.4.1.5 of [4, TS 38.211] may be used for CSI computation. + +### 8.4.2 DM-RS reception procedure for RSRP computation + +#### 8.4.2.1 RSRP for resource selection in sidelink resource allocation mode 2 + +In sidelink resource allocation mode 2, the UE measures RSRP for resource selection as follows: + +- PSSCH-RSRP over the DM-RS resource elements for the PSSCH according to the received SCI format 1-A if higher layer parameter *sl-RS-ForSensing* is set to 'pssch', and +- PSCCH-RSRP over the DM-RS resource elements for the PSCCH carrying the received SCI format 1-A if higher layer parameter *sl-RS-ForSensing* is set to 'pscch'. + +### 8.4.3 PT-RS reception procedure + +Reception of PT-RS is only supported in frequency range 2. + +The UE PT-RS reception procedure specified in clause 5.1.6.3 applies for derivation of the PT-RS parameters $L_{PT-RS}$ and $K_{PT-RS}$ and for determination of PT-RS presence, with the following changes: + +- *timeDensity* and *frequencyDensity* in *PTRS-DownlinkConfig* are replaced by *sl-PTRS-TimeDensity* and *sl-PTRS-FreqDensity* in *SL-PTRS-Config* respectively, and *SL-PTRS-Config* is (pre)configured per resource pool; +- the number of antenna ports is the same as the number of PSSCH DM-RS antenna ports and the association between a PT-RS antenna port and a PSSCH DM-RS antenna port is fixed. + +### 8.4.4 SL PRS reception procedure + +The UE may be configured, via [*higher layer parameter(s)*], to measure and report one or more of the SL RSTD, SL Rx-Tx time difference, SL RTOA, SL PRS-RSRPP, for the first detected path and up to 8 additional detected paths, and SL PRS-RSRP measurements. The UE may be configured, via [*higher layer parameter(s)*], to measure and report one or more of the SL AoA, SL PRS-RSRPP for the first path and up to 2 additional detected paths, and SL PRS-RSRP measurement. + +The UE may report an ARP ID associated with the reported measurements. The UE may provide the ARP location information via [*higher layer parameter(s)*]. + +The UE uses the same ARP for both the transmission and reception of sidelink positioning reference signals while performing an SL Rx-Tx time difference measurement. + +The UE may include SL PRS resource ID(s) when it reports one or more of the SL RSTD, SL Rx-Tx time difference, SL RTOA, SL AoA, SL PRS-RSRP, and SL PRS-RSRPP measurements. + +For the SL RSTD, SL Rx-Tx time difference, SL RTOA, SL AoA, SL PRS-RSRP, and SL PRS-RSRPP measurements, the UE reports an associated SL PRS reception timestamp via higher layer parameter [*slTimestamps*]. For SL Rx-Tx time difference, the UE may report an associated SL PRS transmission timestamp via higher layer parameter [*tx-Time-Info*] and the UE may be configured to report a SL PRS transmission timestamp via [*higher\_layer\_parameter*]. The timestamp includes the SFN, slot number, and optionally *nr-PhysCellID*, *nr-ARFCN*, *nr-CellGlobalID*, or the timestamp includes DFN and slot number. The timestamp of DFN and slot number may include synchronization source indication of DFN. + +The UE may be configured to report up to N Rx-Tx time difference measurements for the same SL PRS transmission associated with N different SL PRS receptions for the same pair of UE(s). The UE may be configured to report up to N Rx-Tx time difference measurements for the same SL PRS reception associated with N different SL PRS transmissions for the same pair of UE(s). + +The UE may report, LoS/NLoS indicator(s) via [*nr-los-nlos-Indicator*] associated with each SL RSTD, SL Rx-Tx time difference, SL RTOA, SL AoA, SL PRS-RSRP, and SL PRS-RSRPP measurements. + +The UE may report synchronization source type via [*sync-Info-for-SL-TDOA-TOA*] and/or relative time difference with the associated quality metric, via [*higher layer parameter(s)*]. For the SL RSTD measurement, the UE may report a reference UE information. + +For SL RTOA measurement, SFN or DFN initialization time may be provided to the UE by a UE or the network. + +The UE may be provided with the location information of other UEs via [*higher layer parameter*]. The UE may report the location information of the UE to the network. + +The UE may be provided with expected SL AoA and uncertainty range of the expected SL AoA via [*higher layer parameter*]. + +The UE may report quality metric [*time quality*] corresponding to the SL RSTD, SL RTOA or SL Rx-Tx time difference measurements. The UE may report quality metric [*angle quality*] corresponding to the SL AoA measurement. + +If the '*/SL PRS request/*' field in the SCI associated with the received SL PRS is set to 1 then this request for SL PRS transmission is reported to higher layers. + +## 8.5 UE procedure for reporting channel state information (CSI) + +### 8.5.1 Channel state information framework + +CSI consists of Channel Quality Indicator (CQI) and Rank Indicator (RI). The CQI and RI are always reported together. + +#### 8.5.1.1 Reporting configurations + +The UE shall calculate CSI parameters (if reported) assuming the following dependencies between CSI parameters (if reported) + +- CQI shall be calculated conditioned on the reported RI + +The CSI reporting can be aperiodic (using [10, TS 38.321]). Table 8.5.1.1-1 shows the supported combinations of CSI reporting configurations and CSI-RS configurations and how the CSI reporting is triggered for CSI-RS configuration. Aperiodic CSI-RS is configured and triggered/activated as described in Clause 8.5.1.2. + +**Table 8.5.1.1-1 Triggering/Activation of CSI reporting for the possible CSI-RS Configurations.** + +| CSI-RS Configuration | Aperiodic CSI Reporting | +|----------------------|-------------------------| +| Aperiodic CSI-RS | Triggered by SCI. | + +For CSI reporting, supported. A wideband single codeword for the wideband CQI reporting is CQI is reported for a entire CSI reporting band. + +#### 8.5.1.2 Triggering of sidelink CSI reports + +The CSI-triggering UE is not allowed to trigger another aperiodic CSI report for the same UE before the last slot of the expected reception or completion of the ongoing aperiodic CSI report associated with the SCI format 2-A, 2-C or 2-D + +with the '*CSI request*' field set to 1, where the last slot of the expected reception of the ongoing aperiodic CSI report is given by [10, TS38.321]. + +An aperiodic CSI report is triggered by an SCI format 2-A, 2-C or 2-D with the '*CSI request*' field set to 1. + +A UE is not expected to transmit a sidelink CSI-RS and a sidelink PT-RS which overlap. + +## 8.5.2 Channel state information + +### 8.5.2.1 CSI reporting quantities + +#### 8.5.2.1.1 Channel quality indicator (CQI) + +The UE shall derive CQI as specified in clause 5.2.2.1, with the following changes + +- PDSCH replaced by PSSCH +- uplink slot replaced by sidelink slot +- downlink physical resource blocks replaced by sidelink physical resource blocks +- Transport Block Size determination according to Clause 8.1.3.2 +- CSI reference resource according to the Clause 8.5.2.3 +- interference measurements are not supported +- sub-band CQI is not supported +- cqi-Table is determined as follows + - cqi-Table = 'table1' if Table 5.1.3.1-1 is determined as the MCS table according to Clause 8.1.3.1 of [6, 38.214], + - cqi-Table = 'table2' if Table 5.1.3.1-2 is determined as the MCS table according to Clause 8.1.3.1 of [6, 38.214], + - cqi-Table = 'table3' if Table 5.1.3.1-3 is determined as the MCS table according to Clause 8.1.3.1 of [6, 38.214] + +#### 8.5.2.2 Reference signal (CSI-RS) + +The UE can be configured with one CSI-RS pattern as indicated by the higher layer parameters *sl-CSI-RS-FreqAllocation*, *sl-CSI-RS-FirstSymbol* in *SL-CSI-RS-Config*. + +Parameters for which the UE shall assume non-zero transmission power for CSI-RS are configured according to clause 8.2.1. + +A UE is not expected to be configured such that a CSI-RS and the corresponding PSCCH can be mapped to the same resource element. A UE is not expected to receive sidelink CSI-RS and PSSCH DM-RS, nor CSI-RS and 2nd-stage SCI, on the same symbol. + +Sidelink CSI-RS shall be transmitted according to [4, TS 38.211] in the resource blocks used for the PSSCH associated with the SCI format 2-A, 2-C or 2-D triggering a report. + +#### 8.5.2.3 CSI reference resource definition + +The CSI reference resource in sidelink is defined as follows: + +- In the frequency domain, the CSI reference resource is defined by the group of sidelink physical resource blocks containing the sidelink CSI-RS to which the derived CSI relates. +- In the time domain, the CSI reference resource for a CSI reporting in sidelink slot $n$ is defined by a single sidelink slot $n_{CSI\_ref}$ where $n_{CSI\_ref}$ is the same sidelink slot as the corresponding CSI request. + +If configured to report CQI index and RI index, in the CSI reference resource, the UE shall assume the following for the purpose of deriving the CQI index and RI index: + +- The reference resource uses the CP length and subcarrier spacing configured for the SL BWP. +- Redundancy Version 0. +- PSCCH occupies 2 OFDM symbols. +- The number of PSSCH and DM-RS symbols is equal to *sl-LengthSymbols-2*. +- Assume no REs allocated for sidelink CSI-RS. +- Assume no REs allocated for SCI format 2-A, SCI format 2-B, SCI format 2-C or SCI format 2-D. +- Assume the same number of DM-RS symbols as the smallest one configured by the higher layer parameter *sl-PSSCH-DMRS-TimePatternList*. +- Assume no REs allocated for sidelink PT-RS. +- Assume sidelink CSI-RS RE power is the same as PSSCH RE power. +- The PSSCH transmission scheme where the UE may assume that PSSCH transmission would be performed with up to 2 transmission layers as defined in Clause 8.3.1.4 of [4, TS 38.211]. For CQI calculation, the UE should assume that PSSCH signals on antenna ports in the set [1000, ..., 1000+v-1] for v layers would result in signals equivalent to corresponding symbols transmitted on antenna ports [3000, ..., 3000+P-1], as given by + +where $W(i)$ is a vector of PSSCH symbols from the layer mapping defined in Clause 8.3.1.4 of [4, TS 38.211], $i$ is the number of CSI-RS ports. If only one CSI-RS port is configured, $W(i)$ is 1. Otherwise, $W(i)$ is the identity matrix. + +### 8.5.3 CSI reporting + +The UE can be configured with one CSI reporting latency bound as indicated by the higher layer parameter *sl-LatencyBoundCSI-Report*. CSI reporting is aperiodic and is described in [10, TS 38.321]. + +## 8.6 UE PSSCH preparation procedure time + +For sidelink dynamic grant and for SL configured grant type 2 activation, if the first sidelink symbol in the sidelink allocation for a PSSCH for a transport block and the associated PSCCH, including the DM-RS and the duplicated symbol, as defined by the slot offset of the scheduling DCI for dynamic grant or the activating DCI for SL configured grant type 2, is no earlier than at symbol $L$ , where $L$ is defined as the next sidelink symbol with its CP starting after the end of the reception of the last symbol of the PDCCH carrying the DCI scheduling the sidelink transmissions for dynamic grant or activating the SL configured grant type 2, then the UE shall transmit the PSSCH and the associated PSCCH. + +- $N_2$ is based on $\mu$ of Table 8.6-1, where $\mu$ corresponds to the one of $(\mu_{DL}, \mu_{SL})$ resulting with the largest $T_{proc}$ , where the $\mu_{DL}$ corresponds to the subcarrier spacing of the downlink with which the PDCCH carrying the DCI scheduling the PSSCH for dynamic grant or activating the SL configured grant type 2 was transmitted and $\mu_{SL}$ corresponds to the subcarrier spacing of the sidelink channel with which the PSSCH and the associated PSCCH are to be transmitted, and $\kappa$ is defined in Clause 4.1 of [4, TS 38.211]. +- $d_{2,1} = 1$ . + +Otherwise the UE may ignore the scheduling DCI for dynamic grant or the activating DCI for SL configured grant type 2. + +The value of $\kappa$ is used both in the case of normal and extended cyclic prefix. + +**Table 8.6-1: PSSCH preparation time** + +| | PSSCH preparation time N_2 [symbols] | +|---|----------------------------------------------------------| +| 0 | 10 | +| 1 | 12 | +| 2 | 23 | +| 3 | 36 | + +For sidelink resource allocation mode 1, the UE does not expect that the first sidelink symbol in the sidelink allocation for a PSSCH for retransmission of a transport block and the associated PSCCH, including the DM-RS and the duplicated symbol as defined by the "Time resource assignment" field of the corresponding DCI for dynamic grant or for SL configured grant type 2, or by *sl-TimeResourceCG-Type1* for configured grant type 1 starts earlier than at symbol $\psi$ where $\psi$ is defined as the next sidelink symbol with its CP starting after the end of the last symbol of the PSFCH occasion corresponding to the most recent transmission of PSSCH for the same transport block, where $\psi$ is defined in Clause 16.5 of [6, TS 38.213] and $\psi$ . Otherwise the UE may skip the retransmission of the PSSCH and the transmission of the corresponding PSCCH. + +## 9 UE procedures for transmitting and receiving for RTT-based propagation delay compensation + +For operation with RTT-based propagation delay compensation, the UE may be configured with either: + +- one CSI-RS for tracking with higher layer parameter *pdc-Info* for Rx – Tx time difference estimation at UE side and one SRS resource set with *usage-PDC*, or +- one PRS configuration of higher layer parameter *nr-DL-PRS-PDC-ResourceSet* [12, TS 38.331] for Rx – Tx time difference estimation at UE side and one SRS resource set with *usage-PDC*. + +The related UE procedures for transmitting uplink reference signals and receiving downlink reference signals for RTT-based propagation delay compensation are defined as follows: + +- for reception of CSI-RS for tracking with higher layer parameter *pdc-Info*, the UE follows the procedures for reception of CSI-RS for tracking defined in Clause 5.1.6.1.1. +- for reception of the one PRS configuration provided by RRC [12, TS 38.331] for RTT-based propagation delay compensation, the UE follows the procedure for PRS reception for RTT-based propagation delay compensation defined in Clause 9.1. +- for transmission of an SRS resource set configured with *usage-PDC*, the UE follows the procedures for SRS transmission defined in Clause 6.2.1. + +### 9.1 PRS reception procedure for RTT-based propagation delay compensation + +The DL PRS resource set for RTT-based propagation delay compensation consists of $K \geq 1$ DL PRS resource(s) where each has an associated spatial transmission filter. Each DL PRS resource is configured via higher layer parameters *NR-DL-PRS-Resource* and is uniquely defined by *nr-DL-PRS-ResourceID*. The subcarrier spacing and the cyclic prefix of the DL PRS resources are defined by the subcarrier spacing and the cyclic prefix of the DL active bandwidth part of the serving cell. + +The DL PRS resource set for RTT-based propagation delay compensation is configured by *nr-DL-PRS-PDC-ResourceSet*, consists of one or more DL PRS resource(s) and it is defined by: + +- *periodicityAndOffset* defines the DL PRS resource periodicity and takes values slots, where for 15, 30, 60 and 120 kHz subcarrier spacing respectively and the slot offset for DL PRS resource set with respect to SFN0 slot 0. All the DL PRS resources are configured with the same DL PRS resource periodicity. +- *repetitionFactor* defines how many times each DL-PRS resource is repeated for a single instance of the DL-PRS resource set and takes values $1, 2, 4, 8, 16, 32, 64, 128, 256$ . All the DL PRS resources within the resource set have the same resource repetition factor. + +- *timeGap* defines the offset in number of slots between two repeated instances of a DL PRS resource with the same *nr-DL-PRS-ResourceID* within a single instance of the DL PRS resource set. The UE only expects to be configured with *timeGap* if *repetitionFactor* is configured with value greater than 1. The time duration spanned by one instance of a *nr-DL-PRS-ResourceSet* is not expected to exceed the configured value of DL PRS periodicity. All the DL PRS resources within the resource set have the same value of *timeGap*. +- *resourceList* determines the DL PRS resources that are contained within the DL PRS resource set. +- *dl-PRS-ResourceBandwidth* defines the number of resource blocks configured for DL PRS transmission. The parameter has a granularity of 4 PRBs with a minimum of 24 PRBs and a maximum of 272 PRBs. All the DL PRS resources within the resource set have the same value of *dl-PRS-ResourceBandwidth*. +- *dl-PRS-StartPRB* defines the starting PRB index of the DL PRS resource with respect to subcarrier 0 in common resource block 0. The starting PRB index has a granularity of one PRB with a minimum value of 0 and a maximum value of 2176 PRBs. All the DL PRS resources within the resource set have the same value of *dl-PRS-StartPRB*. +- *numSymbols* defines the number of symbols of the DL PRS resource within a slot where the allowable values are given in Clause 7.4.1.7.3 of [4, TS38.211]. All the DL PRS resources within the resource set have the same value of *numSymbols*. + +A DL PRS resource is defined by: + +- *nr-DL-PRS-ResourceID* determines the DL PRS resource configuration identity. All DL PRS resource IDs are locally defined within the DL PRS resource set. +- *dl-PRS-SequenceID* is used to initialize $c_{init}$ value used in pseudo random generator as described in Clause 7.4.1.7.2 of [4, TS 38.211] for generation of DL PRS sequence for a given DL PRS resource. +- *dl-PRS-CombSizeN-AndReOffset* defines the comb size of a DL PRS resource, where the allowable values are given in Clause 7.4.1.7.3 of [TS38.211], and the starting RE offset of the first symbol within a DL PRS resource in frequency. The UE may expect the same comb size to be configured for all DL PRS resources of the PRS resource set. The relative RE offsets of the remaining symbols within a DL PRS resource are defined based on the initial offset and the rule described in Clause 7.4.1.7.3 of [4, TS 38.211]. +- *dl-PRS-ResourceSlotOffset* determines the starting slot of the DL PRS resource with respect to corresponding DL PRS resource set slot offset. +- *dl-PRS-ResourceSymbolOffset* determines the starting symbol of a slot configured with the DL PRS resource. +- *dl-PRS-QCL-Info* defines any quasi co-location information of the DL PRS resource with other reference signals. The DL PRS may be configured with QCL 'typeD' with a DL PRS in the same PRS resource set, or with *rs-Type* set to 'typeC', 'typeD', or 'typeC-plus-typeD' with a SS/PBCH Block from the serving cell. + +The UE assumes constant EPRE is used for all REs of a given DL PRS resource. + +The UE assumes that the DL PRS from the serving cell is not mapped to any symbol that contains SS/PBCH block from the serving cell. + +The UE does not expect to be scheduled or configured for reception of any downlink channel or any other downlink signal(s) in the OFDM symbol(s) and PRBs of the DL PRS resource for RTT-based propagation delay compensation to be received. + +The UE is expected to receive the DL PRS for RTT-based propagation delay compensation only in RRC\_CONNECTED state and within the DL active bandwidth part of the serving cell. + +--- + +## Annex (informative): Change history + +| Change history | | | | | | | | +|----------------|-------------|------------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-05 | RAN1#89 | R1-1708892 | - | - | - | Draft skeleton | 0.0.0 | +| 2017-07 | AH_1706 | R1-1712016 | | | | Inclusion of agreements up to and including RAN1#AH2 | 0.0.1 | +| 2017-08 | AH_1706 | R1-1714234 | | | | Inclusion of agreements up to and including RAN1#AH2 | 0.0.2 | +| 2017-08 | RAN1#90 | R1-1714596 | | | | Updated editor's version | 0.0.3 | +| 2017-08 | RAN1#90 | R1-1714626 | | | | Updated editor's version | 0.0.4 | +| 2017-08 | RAN1#90 | R1-1715077 | | | | Endorsed version by RAN1#90 | 0.1.0 | +| 2017-08 | RAN1#90 | R1-1715324 | | | | Inclusion of agreements up to and including RAN1#90 | 0.1.1 | +| 2017-08 | RAN1#90 | R1-1715331 | | | | Updated editor's version | 0.1.2 | +| 2017-09 | RAN#77 | RP-172001 | | | | For information to plenary | 1.0.0 | +| 2017-09 | AH_1709 | R1-1716930 | | | | Inclusion of agreements up to and including RAN1#AH3 | 1.0.1 | +| 2017-10 | RAN1#90 bis | R1-1718808 | | | | Updated editor's version | 1.0.2 | +| 2017-10 | RAN1#90 bis | R1-1718819 | | | | Endorsed version by RAN1#90bis | 1.1.0 | +| 2017-10 | RAN1#90 bis | R1-1719227 | | | | Inclusion of agreements up to and including RAN1#90bis | 1.1.1 | +| 2017-11 | RAN1#90 bis | R1-1720113 | | | | Inclusion of agreements up to and including RAN1#90bis | 1.1.2 | +| 2017-11 | RAN1#90 bis | R1-1720114 | | | | Inclusion of agreements up to and including RAN1#90bis | 1.1.3 | +| 2017-11 | RAN1#90 bis | R1-1721051 | | | | Endorsed version | 1.2.0 | +| 2017-12 | RAN1#91 | R1-1721344 | | | | Inclusion of agreements up to and including RAN1#91 | 1.3.0 | +| 2017-12 | RAN#78 | RP-172416 | | | | Endorsed version for approval by plenary | 2.0.0 | +| 2017-12 | RAN#78 | | | | | Approved by plenary – Rel-15 spec under change control | 15.0.0 | +| 2018-03 | RAN#79 | RP-180200 | 0001 | | F | CR capturing the Jan18 ad-hoc and RAN1#92 meeting agreements | 15.1.0 | +| 2018-06 | RAN#80 | RP-181172 | 0002 | 1 | F | CR to 38.214 capturing the RAN1#92bis and RAN1#93 meeting agreements | 15.2.0 | +| 2018-06 | RAN#80 | RP-181257 | 0003 | - | B | CR to 38.214 capturing the RAN1#92bis and RAN1#93 meeting agreements related to URLLC | 15.2.0 | +| 2018-06 | RAN#80 | RP-181172 | 0004 | - | F | CR to 38.214: maintenance according to agreed Rel 15 features | 15.2.0 | +| 2018-09 | RAN#81 | RP-181789 | 0005 | - | F | CR to 38.214 capturing the RAN1#94 meeting agreements | 15.3.0 | +| 2018-12 | RAN#82 | RP-182523 | 0006 | 2 | F | Combined CR of all essential corrections to 38.214 from RAN1#94bis and RAN1#95 | 15.4.0 | +| 2019-03 | RAN#83 | RP-190632 | 0007 | 3 | F | Correction to aperiodic CSI-RS triggering with different numerology between PDCCH and CSI-RS | 15.5.0 | +| 2019-03 | RAN#83 | RP-190450 | 0009 | - | F | Correction on CSI-RS configuration in 38.214 | 15.5.0 | +| 2019-03 | RAN#83 | RP-190450 | 0010 | - | F | Correction on uplink resource allocation type 1 | 15.5.0 | +| 2019-03 | RAN#83 | RP-190450 | 0011 | - | F | Correction on determination of the resource allocation table for PUSCH with SP CSI | 15.5.0 | +| 2019-03 | RAN#83 | RP-190450 | 0012 | - | F | Correction on PUSCH resource allocation | 15.5.0 | +| 2019-03 | RAN#83 | RP-190450 | 0013 | - | F | Change Request for alignment of frequency domain resource allocation with 38.213 for a PUSCH transmission scheduled by a RAR UL grant | 15.5.0 | +| 2019-03 | RAN#83 | RP-190450 | 0014 | - | F | CR on sequential PDSCH and PUSCH scheduling | 15.5.0 | +| 2019-03 | RAN#83 | RP-190450 | 0015 | - | F | CR on out of HARQ order with multiple PDSCHs within one slot | 15.5.0 | +| 2019-03 | RAN#83 | RP-190450 | 0016 | - | F | Correction to LBRM restriction | 15.5.0 | +| 2019-03 | RAN#83 | RP-190450 | 0017 | - | F | CR on PDSCH beam indication | 15.5.0 | +| 2019-03 | RAN#83 | RP-190450 | 0018 | - | F | Correction on TCI indication for multi-slot PDSCH | 15.5.0 | +| 2019-03 | RAN#83 | RP-190450 | 0019 | - | F | Clarifications on CSI reporting on PUSCH | 15.5.0 | +| 2019-03 | RAN#83 | RP-190450 | 0020 | - | F | QCL properties of Msg4 in CONNECTED Mode | 15.5.0 | +| 2019-03 | RAN#83 | RP-190450 | 0022 | 1 | F | CR on dynamic grant overriding configured grant | 15.5.0 | +| 2019-03 | RAN#83 | RP-190450 | 0023 | - | F | Correction on PUSCH with configured grant | 15.5.0 | +| 2019-03 | RAN#83 | RP-190450 | 0024 | - | F | Corrections to 38.214 | 15.5.0 | +| 2019-03 | RAN#83 | RP-190425 | 0025 | 1 | F | CR on QCL assumption for receiving PDSCH for RAR | 15.5.0 | +| 2019-06 | RAN#84 | RP-191552 | 0035 | - | F | Removal of "Correction to aperiodic CSI-RS triggering with different numerology between PDCCH and CSI-RS" | 15.6.0 | +| 2019-06 | RAN#84 | RP-191284 | 0026 | - | F | Corrections on non-codebook based UL transmission to TS 38.214 | 15.6.0 | +| 2019-06 | RAN#84 | RP-191284 | 0027 | - | F | CR on UE procedure for PDSCH and PUSCH | 15.6.0 | +| 2019-06 | RAN#84 | RP-191284 | 0028 | - | F | Correction on configured scheduling PUSCH repetition with dynamic SFI | 15.6.0 | +| 2019-06 | RAN#84 | RP-191284 | 0029 | - | F | CR on rate matching for PDSCH scheduled by DCI format 1_0 | 15.6.0 | +| 2019-06 | RAN#84 | RP-191284 | 0030 | - | F | Clarification on CG transmission opportunities | 15.6.0 | +| 2019-06 | RAN#84 | RP-191284 | 0031 | 5 | F | Corrections to 38.214 including alignment of terminology across specifications | 15.6.0 | +| 2019-06 | RAN#84 | RP-191284 | 0032 | - | F | CR to 38.214 clarifying calculation of DataRate and DataRateCC | 15.6.0 | +| 2019-06 | RAN#84 | RP-191284 | 0033 | - | F | Correction on PUSCH retransmission for a serving cell configured with two uplinks | 15.6.0 | +| 2019-06 | RAN#84 | RP-191284 | 0034 | - | F | Corrections to 38.214 regarding the MAC CE activation/deactivation timing in mixed numerology scenario | 15.6.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------|--------| +| 2019-09 | RAN#85 | RP-191943 | 0037 | - | F | Correction on UE receiving PDSCH procedure in FR2 | 15.7.0 | +| 2019-09 | RAN#85 | RP-191943 | 0038 | - | F | Correction on slot aggregation | 15.7.0 | +| 2019-09 | RAN#85 | RP-191943 | 0039 | - | F | CR on grant-based PDSCH overlapping with SPS PDSCH | 15.7.0 | +| 2019-09 | RAN#85 | RP-191943 | 0040 | - | F | Correction on the resource mapping of PDSCH in TS 38.214 | 15.7.0 | +| 2019-09 | RAN#85 | RP-191943 | 0041 | 1 | F | Corrections to 38.214 including alignment of terminology across specifications in RAN1#98 | 15.7.0 | +| 2019-09 | RAN#85 | RP-191943 | 0042 | - | F | Clarification of PUSCH with SP-CSI overlapping with PUSCH with data | 15.7.0 | +| 2019-12 | RAN#86 | RP-192627 | 0045 | - | F | Correction on resource allocation for uplink transmission with configured grant Type 1 | 15.8.0 | +| 2019-12 | RAN#86 | RP-192627 | 0046 | - | F | Clarification to the dynamically scheduled PDSCH collision with SPS-PDSCH | 15.8.0 | +| 2019-12 | RAN#86 | RP-192627 | 0047 | - | F | Correction on rate-matching for LTE-CRS-toMatchAround | 15.8.0 | +| 2019-12 | RAN#86 | RP-192627 | 0048 | - | F | Correction on timing for MAC CE applicability in 38.214 | 15.8.0 | +| 2019-12 | RAN#86 | RP-192627 | 0049 | - | F | Corrections to 38.214 including alignment of terminology across specifications in RAN1#98bis and RAN1#99 | 15.8.0 | +| 2019-12 | RAN#86 | RP-192634 | 0043 | 1 | B | Introduction of UE behaviour for SRS measurements for CLI | 16.0.0 | +| 2019-12 | RAN#86 | RP-192635 | 0050 | - | B | Introduction of two-step RACH | 16.0.0 | +| 2019-12 | RAN#86 | RP-192636 | 0051 | - | B | Introduction of NR - U | 16.0.0 | +| 2019-12 | RAN#86 | RP-192637 | 0052 | - | B | Introduction of integrated access and backhaul for NR | 16.0.0 | +| 2019-12 | RAN#86 | RP-192638 | 0053 | - | B | Introduction of NR V2X | 16.0.0 | +| 2019-12 | RAN#86 | RP-192639 | 0054 | - | B | Introduction of NR URLLC support | 16.0.0 | +| 2019-12 | RAN#86 | RP-192641 | 0055 | - | B | Introduction of NR enhanced MIMO | 16.0.0 | +| 2019-12 | RAN#86 | RP-192642 | 0056 | - | B | Introduction of cross-slot scheduling restriction | 16.0.0 | +| 2019-12 | RAN#86 | RP-192643 | 0057 | - | B | Introduction of NR positioning support | 16.0.0 | +| 2019-12 | RAN#86 | RP-192645 | 0058 | - | B | Introduction of Cross-carrier Scheduling with Different Numerologies | 16.0.0 | +| 2019-12 | RAN#86 | RP-192646 | 0059 | - | B | Introduction of multiple LTE CRS rate matching patterns | 16.0.0 | +| 2019-12 | RAN#86 | RP-192646 | 0060 | - | B | Aperiodic CSI-RS Triggering for UE reporting beamSwitchTiming values of 224 and 336 | 16.0.0 | +| 2019-12 | RAN#86 | RP-192646 | 0061 | - | B | Behaviour for triggered with a CSI report for non-active BWP | 16.0.0 | +| 2019-12 | RAN#86 | RP-192646 | 0062 | - | B | Introduction of downgraded configurations for SRS antenna switching | 16.0.0 | +| 2019-12 | RAN#86 | RP-192646 | 0063 | - | B | Introduction of one-slot periodic TRS configuration for FR1 under a certain condition | 16.0.0 | +| 2019-12 | RAN#86 | RP-192640 | 0064 | - | B | Introduction of Industrial IoT | 16.0.0 | +| 2020-03 | RAN#87-e | RP-200185 | 0068 | - | F | Corrections on NR - U | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200187 | 0069 | - | F | Corrections on NR V2X | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200483 | 0070 | 1 | F | Corrections on Cross-carrier Scheduling with Different Numerologies | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200188 | 0071 | - | F | Corrections on NR URLLC support | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200190 | 0072 | - | F | Corrections on NR enhanced MIMO | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200189 | 0073 | - | F | Corrections on Industrial IoT | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200191 | 0074 | - | F | Corrections of cross-slot scheduling restriction and CSI/L1-RSRP measurement outside active time | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200184 | 0075 | - | F | Corrections on two-step RACH after RAN1#100-e | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200192 | 0076 | - | F | Corrections of NR positioning support | 16.1.0 | +| 2020-03 | RAN#87-e | RP-200448 | 0078 | - | A | CR on UL PTRS density selection | 16.1.0 | +| 2020-06 | RAN#88-e | RP-200683 | 0080 | - | A | CR on CSI reporting for BWP size < 24 PRBs | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200683 | 0082 | - | A | CR on 38.214 PDSCH resource mapping | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200683 | 0084 | - | A | CR to 38.214 clarification on resource and port occupation of duplicate CSI-RS resources | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200693 | 0085 | 1 | F | Corrections of cross-slot scheduling restriction | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200686 | 0086 | 1 | F | Correction of two-step RACH | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200690 | 0087 | 1 | F | Corrections on NR URLLC support | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200691 | 0088 | 1 | F | Corrections on Industrial IoT | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200694 | 0089 | 1 | F | Corrections of NR positioning support | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200687 | 0090 | 1 | F | Corrections on NR - U | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200689 | 0091 | 1 | F | Corrections on NR V2X | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200696 | 0092 | 1 | F | Corrections on Cross-carrier Scheduling with Different Numerologies | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200692 | 0093 | 1 | F | Corrections on NR enhanced MIMO | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200685 | 0094 | - | F | Correction on SRS-RSRP reception procedure for CLI | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200683 | 0097 | - | A | CR on SRS for 38.214 | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200683 | 0099 | - | A | CR on 38.214 rate-matching for PDSCH with SPS | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200683 | 0101 | - | A | Correction for SP-CSI reporting on PUSCH | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200683 | 0103 | - | A | CR on port and CSI-RS resource counting | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200705 | 0106 | - | B | Introduction of switched uplink operation | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200697 | 0107 | - | F | Correction on aperiodic CSI-RS triggering with beam switching timing of 224 and 336 and on CSI reporting | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200697 | 0108 | - | F | Correction to TBS determination when $3824 < N_{info} < 3825$ | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200697 | 0109 | - | D | Editorial corrections | 16.2.0 | +| 2020-09 | RAN#89-e | RP-201803 | 0111 | - | A | CR on Measurement Restriction for L1-RSRP | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201803 | 0113 | - | A | Correction on sounding procedure between component carriers | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201803 | 0115 | - | A | Clarification on which UE capability component indicates the number | 16.3.0 | + +| | | | | | | | | +|--|--|--|--|--|--|--------------------------------------------|--| +| | | | | | | of supported simultaneous CSI calculations | | +|--|--|--|--|--|--|--------------------------------------------|--| + +| | | | | | | | | +|---------|----------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2020-09 | RAN#89-e | RP-201814 | 0116 | - | F | Corrections to PDSCH PRB bundling notation (Rel-15 origin) | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201804 | 0117 | - | F | CR on 2-step RACH for 38.214 | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201813 | 0118 | - | F | Corrections on Cross-carrier Scheduling with Different Numerologies | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201809 | 0120 | - | F | Correction on SRS carrier switching | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201814 | 0121 | - | F | Correction on aperiodic CSI-RS triggering with beam switching timing of 224 and 336 | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201814 | 0122 | - | B | Introduction of flexible TRS bandwidth for BWP of 52 RBs | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201814 | 0123 | - | F | Correction on 38.214 for PUSCH with UL skipping (Note: CR was not implementable because "not based on the latest version of the specification") | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201810 | 0124 | - | F | RRM measurements when drx-onDurationTimer does not start | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201820 | 0125 | - | F | Correction on uplink Tx switching | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201807 | 0126 | 1 | F | Corrections on 5G V2X sidelink features | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201809 | 0127 | - | F | Corrections to MIMO enhancements | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201811 | 0128 | - | F | Corrections to NR positioning support | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201805 | 0129 | - | F | Corrections to NR-based access to unlicensed spectrum | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201808 | 0130 | - | F | Corrections on NR URLLC support | 16.3.0 | +| 2020-12 | RAN#90-e | RP-202385 | 0131 | - | F | Corrections for default TCI state of AP CSI-RS in multi-TRP | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202390 | 0132 | - | F | Correction on beam switch timing for aperiodic TRS | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202401 | 0133 | - | F | Correction on increased number of CSI-RS for mobility per MO | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202390 | 0134 | - | F | 38.214 CR (Rel-16, F, Rel-15 originating) to fix configurable xOverhead values for TBS determination | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202385 | 0135 | - | F | Corrections for the issue of PDCCH and PDSCH colliding in multi-TRP | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202385 | 0136 | - | F | Correction on TCI state codepoint mapping for DCI format 1_2 | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202384 | 0137 | - | F | Correction on data rate restriction in a slot for PUSCH repetition Type B | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202390 | 0138 | - | F | Correction to beam switch timing | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202385 | 0139 | - | F | CR on Interference Measurement Resource for L1-SINR | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202383 | 0140 | - | F | Corrections related to the sidelink slot index | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202383 | 0141 | - | F | Correction on sidelink resource pool determination based on PSBCH | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202383 | 0142 | - | F | Introduction of the preparation time for SL retransmissions in Mode 1 | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202386 | 0143 | - | F | Correction on L1-RSRP and Minimum scheduling offset | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202383 | 0145 | - | F | Correction on redundancy version for PSSCH | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202385 | 0146 | - | F | CR on Measurement Restriction for L1-SINR | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202387 | 0147 | - | F | Correction to DL PRS duration calculation for DL PRS processing | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202387 | 0148 | - | F | CR on DL PRS resource prioritization for UE measurements | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202387 | 0149 | - | F | CR on the configuration of spatial relation for the SRS for positioning | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202387 | 0150 | - | F | CR for replacement of cell terminology in PRS reception procedure | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202387 | 0152 | - | F | CR for parameter name alignment and reference corrections in PRS reception procedure | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202389 | 0153 | - | F | Corrections for A-CSI triggering with unaligned CA | 16.4.0 | +| 2020-12 | RAN#90-e | RP-202398 | 0154 | - | F | Alignment of RRC parameter names for 38.214 | 16.4.0 | +| 2021-03 | RAN#91-e | RP-210047 | 0156 | - | A | Correction on MCS values for PT-RS time density determination in TS 38.214 | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210048 | 0157 | - | F | CR on DMRS configuration for MsgA in 38.214 | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210049 | 0158 | - | F | Correction on joint configuration of semi-static repetitions and multi-pusch scheduling | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210055 | 0159 | - | F | Correction on UE sounding procedure | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210052 | 0160 | - | F | CR on Default TCI state of Scheme 3 and Scheme 4 | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210052 | 0161 | - | F | CR on multi-TRP | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210052 | 0162 | - | F | CR on PDSCH QCL | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210052 | 0163 | - | F | CR on L1-SINR based beam measurement | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210050 | 0164 | - | F | Corrections related to the sidelink resource reservation period | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210050 | 0165 | - | F | Correction to pre-emption condition for Mode-2 resource allocation | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210051 | 0166 | - | F | Correction on Part 2 CSI dropping for UCI multiplexing on PUSCH repetition Type B | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210058 | 0167 | - | F | Correction on uplink Tx switching | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210053 | 0168 | 1 | F | CR for the configuration of semi-persistent SRS | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210053 | 0169 | 1 | F | CR for the configuration of DL-PRS as the spatial relation of periodic and semi-persistent positioning SRS | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210053 | 0170 | 1 | F | CR for the configuration of SRS for positioning in SRS carrier switching | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210053 | 0171 | 1 | F | CR on DL PRS resource indication in activation command for semi-persistent SRS for positioning and amount of DL PRS resource sets per TRP | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210053 | 0172 | 1 | F | CR on timestamp reference in NR positioning measurement report | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210053 | 0173 | 1 | F | CR on measurement gap configuration for NR positioning | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210054 | 0175 | - | F | Additional timing delay for applying QCL relation on the PDSCH with cross-carrier scheduling with different SCS. | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210051 | 0176 | - | F | Correction on PDSCH resource mapping with RE symbol level granularity | 16.5.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2021-03 | RAN#91-e | RP-210051 | 0177 | - | F | Active time duration of NZP CSI-RS resource | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210059 | 0178 | - | F | Editorial corrections for 38.214 | 16.5.0 | +| 2021-03 | RAN#91-e | RP-210309 | 0123 | 2 | F | Correction on 38.214 for PUSCH with UL skipping in Rel-16 | 16.5.0 | +| 2021-06 | RAN#92-e | RP-211237 | 0179 | - | F | Correction on out-of-order HARQ operation in 38.214 | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211239 | 0180 | - | F | 38.214 CR on CSI request constraint per slot | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211240 | 0181 | - | F | Timelines for SRS carrier switching | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211238 | 0182 | 1 | F | Correction to the DL PRS reception procedure for PRS cell determination | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211235 | 0183 | 1 | F | Correction to sidelink resource identification procedure avoiding infinite loop issue | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211234 | 0184 | - | F | Correction on averaging CSI-RS for measuring CSI across DL bursts | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211233 | 0186 | 1 | A | Rel-15 editorial corrections for TS 38.214 (mirrored to Rel-16) | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211243 | 0187 | 1 | F | Rel-16 editorial corrections for TS 38.214 | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211236 | 0188 | - | F | Correction on DMRS reception and transmission procedure in TS 38.214 | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211237 | 0189 | - | F | Correction on simultaneous multi-CC spatial relation update for SRS | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211237 | 0190 | - | F | Correction on enabling configuration of time restriction over L1-SINR measurement | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211237 | 0191 | - | F | Corrections on RRC names and interpretation for Multi-TRP | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211251 | 0192 | - | F | Correction of UE Power Saving | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211233 | 0194 | - | A | Correction on enabling configuration of time restriction over L1-RSRP and CSI measurement | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211233 | 0196 | - | A | Clarification on back-to-back PUSCHs scheduling restriction | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211235 | 0197 | - | F | Corrections for transmitting sidelink reference signals in TS 38.214 | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211238 | 0198 | - | F | CR on DL PRS periodicity and muting repetition factor | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211238 | 0199 | - | F | CR on measurement gap request inside of the active DL BWP for DL PRS measurements | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211239 | 0200 | - | F | 38.214 CR on unaligned frame boundary CA with A-CSI-RS transmission and CSI reference resource definition | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211238 | 0201 | 1 | F | CR on SCS values for DL PRS | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211238 | 0202 | 1 | F | CR on correction to DL PRS processing priority order | 16.6.0 | +| 2021-06 | RAN#92-e | RP-211236 | 0203 | - | F | Correction on SRS resource set configuration in TS 38.214 | 16.6.0 | +| 2021-09 | RAN#93-e | RP-211847 | 0204 | - | F | Correction to PDSCH rate matching for SPS | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211844 | 0205 | - | F | CR on sum data rate for tdmSchemeA and fdmSchemeB | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211842 | 0206 | 1 | F | Correction on procedure for transmitting the physical sidelink shared channel | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211843 | 0207 | - | F | Correction on invalid symbol determination for PUSCH repetition Type B | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211846 | 0208 | - | F | Correction on cross-carrier scheduling and cross-carrier CSI-RS triggering | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211845 | 0209 | - | F | CR on terminology correction to cell for positioning | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211845 | 0210 | - | F | CR on alignment with RAN4 on DL PRS processing | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211841 | 0212 | - | A | CR to 38.214 clarification on coefficients packing order for Type II CSI | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211841 | 0214 | - | A | Clarification on back-to-back PUSCHs scheduling restriction | 16.7.0 | +| 2021-09 | RAN#93-e | RP-211850 | 0215 | - | F | Rel-16 editorial corrections for TS 38.214 | 16.7.0 | +| 2021-12 | RAN#94-e | RP-212958 | 0218 | - | A | Correction on semi-persistent CSI reporting on PUSCH | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212960 | 0219 | - | F | Corrections on UE PDSCH processing time for DCI format 1_2 | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212961 | 0220 | - | F | Correction on frequency hopping for PUSCH and SRS | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212958 | 0222 | - | A | Rel-15 editorial corrections for TS 38.214 | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212964 | 0223 | - | F | Rel-16 editorial corrections for TS 38.214 | 16.8.0 | +| 2021-12 | RAN#94-e | RP-212981 | 0224 | - | B | Introduction of NR further Multi-RAT Dual-Connectivity enhancements | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212973 | 0225 | - | B | Introduction of NR coverage enhancements | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212982 | 0226 | - | B | Introduction of DL 1024QAM for NR FR1 | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212967 | 0227 | - | B | Introduction of NR Extending current NR operation to 71GHz | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212966 | 0228 | - | B | Introduction of further enhancements on MIMO for NR | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212968 | 0229 | - | B | Introduction of enhanced Industrial Internet of Things (IoT) and ultra-reliable and low latency communication (URLLC) support for NR | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212979 | 0230 | - | B | Introduction of NR Multicast and Broadcast Services | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212969 | 0231 | - | B | Introduction of solutions for NR to support non-terrestrial networks (NTN) | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212970 | 0232 | - | B | Introduction of NR Positioning Enhancements | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212971 | 0233 | - | B | Introduction of NR reduced capability NR devices | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212983 | 0234 | - | B | Introduction of UL Tx Switching enhancements | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212978 | 0235 | - | B | Introduction of NR Sidelink enhancements | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212972 | 0236 | - | B | Introduction of NR UE Power Saving Enhancements | 17.0.0 | +| 2021-12 | RAN#94-e | RP-213524 | 0237 | - | B | Introduction of NR small data transmissions in INACTIVE state | 17.0.0 | +| 2022-03 | RAN#95-e | RP-220246 | 0239 | - | A | Correction on determination of SRS resource set triggered by DCI format 2_3 | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220244 | 0242 | - | A | Corrections on mapping between the Time domain resource allocation field value of the RAR UL grant and a row index of an allocated table | 17.1.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2022-03 | RAN#95-e | RP-220246 | 0244 | - | A | Corrections on time domain resource allocation procedure for a PUSCH scheduled by RAR UL grant or by fallbackRAR UL grant | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220247 | 0246 | - | A | Correction on frequency hopping for PUSCH with a configured grant | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220269 | 0248 | - | A | CR on correction of indicated TCI states for single-DCI based MTRP schemes | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220269 | 0250 | - | A | CR on PMI indexing correction in Type II and eType II CSI | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220269 | 0252 | - | A | Correction of NZC partitioning in eType II CSI | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220257 | 0253 | - | F | Corrections on NR coverage enhancements | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220251 | 0254 | - | F | Corrections on NR extensions of current NR operation to 71GHz | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220252 | 0255 | - | F | Corrections on enhanced Industrial Internet of Things (IoT) and ultra-reliable and low latency communication (URLLC) support for NR | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220263 | 0256 | - | F | Corrections on NR Multicast and Broadcast Services | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220949 | 0257 | 1 | B | Corrections on NR Sidelink enhancements | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220256 | 0258 | - | F | Corrections on NR UE Power Saving Enhancements | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220265 | 0259 | - | F | Corrections on further Multi-RAT Dual-Connectivity enhancements | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220266 | 0260 | - | F | Corrections on DL 1024QAM for NR FR1 | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220264 | 0261 | - | F | Corrections on NR Dynamic Spectrum Sharing enhancements | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220250 | 0262 | - | F | Correction on further enhancements on MIMO for NR | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220253 | 0263 | - | F | Corrections on solutions for NR to support non-terrestrial networks (NTN) | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220254 | 0264 | - | F | Correction on NR Positioning Enhancements | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220255 | 0265 | - | F | Corrections on NR reduced capability NR devices | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220267 | 0266 | - | F | Corrections on UL Tx Switching enhancements | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220270 | 0267 | - | F | Corrections on UL Tx Switching enhancements | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220249 | 0269 | - | A | Rel-16 editorial corrections for TS 38.214 (mirrored to Rel-17) | 17.1.0 | +| 2022-06 | RAN#96 | RP-221620 | 0273 | - | A | Clarification of PUSCH with SP-CSI overlapping with PUSCH with data | 17.2.0 | +| 2022-06 | RAN#96 | RP-221598 | 0275 | - | A | Correction on SRS resource set with 'antennaSwitching' and 'beamManagement' | 17.2.0 | +| 2022-06 | RAN#96 | RP-221620 | 0277 | - | A | Correction for parallel transmission of SRS and PUSCH/PUCCH | 17.2.0 | +| 2022-06 | RAN#96 | RP-221616 | 0278 | - | F | Corrections on SRS carrier switching | 17.2.0 | +| 2022-06 | RAN#96 | RP-221616 | 0279 | - | F | Simultaneous transmission of SRS and other channels for intra-band non-contiguous carrier aggregation | 17.2.0 | +| 2022-06 | RAN#96 | RP-221607 | 0280 | - | F | Corrections on NR coverage enhancements | 17.2.0 | +| 2022-06 | RAN#96 | RP-221601 | 0281 | - | F | Corrections on NR extensions of current NR operation to 71GHz | 17.2.0 | +| 2022-06 | RAN#96 | RP-221602 | 0282 | - | F | Corrections on enhanced Industrial Internet of Things (IoT) and ultra-reliable and low latency communication (URLLC) support for NR | 17.2.0 | +| 2022-06 | RAN#96 | RP-221612 | 0283 | - | F | Corrections on NR Multicast and Broadcast Services | 17.2.0 | +| 2022-06 | RAN#96 | RP-221611 | 0284 | - | F | Corrections on NR Sidelink enhancements | 17.2.0 | +| 2022-06 | RAN#96 | RP-221614 | 0285 | - | F | Corrections on further Multi-RAT Dual-Connectivity enhancements | 17.2.0 | +| 2022-06 | RAN#96 | RP-221610 | 0286 | - | F | Corrections on eIAB | 17.2.0 | +| 2022-06 | RAN#96 | RP-221600 | 0287 | - | F | Correction on further enhancements on MIMO for NR | 17.2.0 | +| 2022-06 | RAN#96 | RP-221604 | 0288 | - | F | Correction on NR Positioning Enhancements | 17.2.0 | +| 2022-06 | RAN#96 | RP-221615 | 0289 | - | F | Corrections on UL Tx Switching enhancements | 17.2.0 | +| 2022-06 | RAN#96 | RP-221599 | 0291 | - | A | Rel-16 editorial corrections for TS 38.214 (mirrored to Rel-17) | 17.2.0 | +| 2022-09 | RAN#97-e | RP-222404 | 0292 | 1 | F | Correction on PRS reception procedure | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222404 | 0293 | 1 | F | Correction on UE sounding procedure for positioning purpose | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222404 | 0294 | - | F | CR on DL-AOD positioning measurement for 38.214 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222404 | 0295 | - | F | CR on PRS RSRP reporting for 38.214 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222398 | 0297 | - | A | Correction for PUSCH TDRA Tables | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222401 | 0298 | - | F | Corrections on timeline of CSI request for 480kHz and 960kHz SCS in TS38.214 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222401 | 0299 | - | F | Correction on UE PDSCH processing procedure time for operation with shared spectrum channel access in FR2-2 in TS 38.214 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222401 | 0300 | - | F | Correction for aperiodic CSI triggering offset for FR2-2 in TS 38.214 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222404 | 0301 | - | F | CR on priority states within the PRS processing window | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222404 | 0302 | - | F | CR on PRS processing sample for 38.214 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222404 | 0303 | - | F | Corrections on M-sample measurement | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222404 | 0304 | - | F | CR on the positioning frequency layer within a PPW and UE capability for the PPW | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222404 | 0305 | - | F | CR on PRS reception and SRS transmission outside initial BWP | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222403 | 0307 | 1 | F | Corrections on HARQ for NR-NTN for 38.214 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222410 | 0308 | - | F | Correction on CQI derivation accounting for provided DL Tx power adjustment for IAB-MT | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222410 | 0309 | - | F | CR on eIAB CSI | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222400 | 0310 | 1 | F | CR on inter-cell multi-TRP operation | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222400 | 0311 | 1 | F | CR on inter-cell mTRP with PUSCH repetition TypeB | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222415 | 0312 | - | F | Correction on uplink suspension for CA-based SRS carrier switching | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222400 | 0313 | - | F | CR for CSI-RS power for inter-cell mTRP | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222400 | 0314 | - | F | CR on default QCL for unified TCI state for PDSCH and A-CSI-RS | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222400 | 0315 | - | F | CR on unified TCI in TS38.214 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222400 | 0316 | - | F | CR on BAT for CA case | 17.3.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2022-09 | RAN#97-e | RP-222419 | 0317 | - | A | Correction on parallel transmission of MsgA and other channels in TS 38.214 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222400 | 0318 | - | F | Correction on the number of CPUs for Multi-TRP CSI | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222400 | 0319 | - | F | Correction on CSI-RS port restriction for mTRP CSI | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222400 | 0320 | - | F | Correction on slot offsets of CSI-RS resource pairs for MTRP | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222414 | 0321 | - | F | Correction on aperiodic CSI-RS for tracking for fast SCell activation | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222402 | 0322 | - | F | CR on UE procedure for overlapping CG PUSCH and DG PUSCH | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222400 | 0323 | - | F | CR on the application of the configuration of group-based beam reporting | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222404 | 0324 | - | F | CR on completing the PPW processing timeline | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222404 | 0326 | - | F | Correction on PRS reception procedure | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222415 | 0327 | - | F | CR on SRS carrier switching | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222400 | 0328 | - | F | Correction on Rel-17 aperiodic SRS configuration for 1T4R | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222398 | 0330 | - | A | Corrections on presence of redundancy version field and HARQ process number field of DCI format 0_2 for semi-persistent CSI activation or deactivation PDCCH validation | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222417 | 0332 | - | A | Clarification of LI reporting for Enhanced Type II CSI feedback | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222412 | 0337 | - | F | Corrections on NR Multicast and Broadcast Services | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222411 | 0340 | - | F | Corrections on NR Sidelink enhancements | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222422 | 0341 | - | F | Rel-17 editorial corrections for TS 38.214 | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222399 | 0343 | - | A | Rel-16 editorial corrections for TS 38.214 (mirrored to Rel-17) | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222407 | 0344 | - | F | A-CSI multiplexing on TBoMS | 17.3.0 | +| 2022-09 | RAN#97-e | RP-222609 | 0345 | 1 | F | CR on PUSCH frequency hopping with DMRS bundling | 17.3.0 | +| 2022-12 | RAN#98-e | RP-222852 | 0346 | - | F | Correction on LI reporting for Further Enhanced Type II Port Selection CSI feedback | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222853 | 0347 | - | F | Correction on spatial domain filter for sensing for SRS transmission in FR2-2 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222863 | 0348 | - | F | Correction on the description for the minimum number of Y and Y' candidate slots in sidelink partial sensing | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222863 | 0349 | - | F | Correction on the selection of Y and Y' candidate slots in sidelink partial sensing | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222856 | 0350 | - | F | Correction on SRS for positioning switching time | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222853 | 0351 | - | F | Correction on frequency resource for CSI-RS for tracking in TS 38.214 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222853 | 0352 | - | F | Correction on UE PUSCH preparation procedure time for operation with shared spectrum channel access in FR2-2 in TS 38.214 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222856 | 0353 | - | F | Correction on DL PRS subcarrier spacings for FR2-2 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222853 | 0354 | - | F | Correction on ZP CSI-RS rate-matching for multi-PDSCH scheduling | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222853 | 0355 | - | F | Correction on TDRA for multiple PUSCH scheduling in TS 38.214 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222857 | 0356 | - | F | Correction on invalid symbol determination for PUSCH repetition type B for HD-FDD | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222857 | 0357 | - | F | Corrections on available slot determination for PUSCH repetition type A and TBoMS for HD-UE | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222856 | 0358 | - | F | Correction adding DL PRS-RSRPP to the applicable measurements | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222856 | 0359 | - | F | Correction to the Rx beam reporting condition for DL-AoD | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0360 | - | F | CR on the max data rate for FDMD MBS and unicast to TS 38.214 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222867 | 0362 | - | A | CR on aperiodic CSI report with dormant BWP | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222853 | 0363 | - | F | Correction on a minimum guard period between two SRS resources for antenna switching | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222863 | 0364 | - | F | Corrections on CPS operation in sidelink partial sensing | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222852 | 0365 | - | F | Correction on Type 1 configured grant PUSCH transmission associated with two SRS resource sets | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222856 | 0366 | - | F | CR on collision in Type 1B and Type 2 PPW for FR2 inter-band case | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222853 | 0367 | - | F | Correction on DL PDSCH validity for multi-PDSCH scheduling via single DCI mTRP in FR2-2 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0368 | - | F | CR on the MBS reception type combinations to TS 38.214 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222851 | 0371 | - | A | Rel-16 editorial corrections for TS 38.214 (mirrored to Rel-17) | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222868 | 0372 | 1 | F | Rel-17 editorial corrections for TS 38.214 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222856 | 0373 | - | F | CR on UE TEG margin value report | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222856 | 0374 | - | F | Correction on configuration of UE Tx TEG association information reporting | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222853 | 0375 | - | F | CR on frequency hopping for PUSCH and SRS in FR2-2 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222852 | 0376 | - | F | CR on beam application time for unified TCI in TS 38.214 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222852 | 0377 | - | F | Correction on SRI for mTRP PUSCH repetition | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222859 | 0378 | - | F | Correction of RV of CG PUSCH repetitions | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222856 | 0379 | - | F | Correction on DL PRS priority states in PPW | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222870 | 0383 | - | F | CR on UL Tx switching for PUCCH with HARQ-ACK | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222850 | 0385 | - | A | Correction on Priority rules for CSI reports in TS 38.214 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222859 | 0386 | - | F | Correction on events for restarting of DMRS bundling | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222859 | 0387 | - | F | Correction on DMRS bundling for reduced capability HD-UE | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222859 | 0388 | - | F | Correction on determination N-K for DMRS bundling of CG-PUSCH | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222864 | 0389 | - | F | CR on rate-matching pattern for MBS broadcast reception | 17.4.0 | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2022-12 | RAN#98-e | RP-222863 | 0390 | - | F | Correction on duplicated part on UE procedure for determining a resource conflict between TS 38.213 and TS 38.214 | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222863 | 0391 | - | F | Correction on the re-evaluation and pre-emption checking for periodic and aperiodic transmissions | 17.4.0 | +| 2022-12 | RAN#98-e | RP-222870 | 0392 | - | F | CR on CSI reporting | 17.4.0 | +| 2023-03 | RAN#99 | RP-230443 | 0394 | - | F | Correction on timeline requirements when configured with uci-MuxWithDiffPrio | 17.5.0 | +| 2023-03 | RAN#99 | RP-230441 | 0395 | - | F | CR on power control parameters for multiple aperiodic SRS resource sets | 17.5.0 | +| 2023-03 | RAN#99 | RP-230442 | 0396 | - | F | Corrections to aperiodic CSI-RS timing for mixed numerologies configuration in TS38.214 | 17.5.0 | +| 2023-03 | RAN#99 | RP-230441 | 0397 | - | F | CR on slot offset parameters for multiple aperiodic SRS resource sets | 17.5.0 | +| 2023-03 | RAN#99 | RP-230451 | 0398 | - | F | CR on SPS and dynamic scheduling PDSCH(s) collision for MBS | 17.5.0 | +| 2023-03 | RAN#99 | RP-230442 | 0399 | - | F | CR on K2 indication for multi-PUSCH scheduling DCI | 17.5.0 | +| 2023-03 | RAN#99 | RP-230442 | 0400 | - | F | Correction on channel measurement and interference measurement in FR2-2 in TS 38.214 | 17.5.0 | +| 2023-03 | RAN#99 | RP-230450 | 0401 | - | F | Clarification of a field in SCI format 2-C indicating the time offset of the first resource of each tuple with respect to the reference slot | 17.5.0 | +| 2023-03 | RAN#99 | RP-230450 | 0402 | - | F | Correction on the resource selection mechanism indicated by higher layer | 17.5.0 | +| 2023-03 | RAN#99 | RP-230454 | 0404 | - | A | Correction on PUSCH TDRA Tables in Rel-17 | 17.5.0 | +| 2023-03 | RAN#99 | RP-230450 | 0405 | - | F | Correction on reservation periodicity for re-evaluation and pre-emption checking | 17.5.0 | +| 2023-03 | RAN#99 | RP-230450 | 0406 | - | F | Correction on periodic-based partial sensing occasion index | 17.5.0 | +| 2023-03 | RAN#99 | RP-230450 | 0407 | - | F | Correction on resource selection based on decoded PSCCH and measured RSRP | 17.5.0 | +| 2023-03 | RAN#99 | RP-230450 | 0408 | - | F | Correction on the parameter description for Y' candidate slots | 17.5.0 | +| 2023-03 | RAN#99 | RP-230441 | 0409 | - | F | CR on HARQ-ACK for beam indication in unified TCI | 17.5.0 | +| 2023-03 | RAN#99 | RP-230451 | 0410 | - | F | CR on FDMed unicast PDSCH and group-common PDSCH | 17.5.0 | +| 2023-03 | RAN#99 | RP-230451 | 0411 | - | F | CR on rate matching pattern number for MBS broadcast reception | 17.5.0 | +| 2023-03 | RAN#99 | RP-230446 | 0412 | - | F | Corrections on invalid symbol determination for PUSCH repetition Type B transmission for RedCap UE | 17.5.0 | +| 2023-03 | RAN#99 | RP-230440 | 0414 | - | A | Rel-16 editorial corrections for TS 38.214 (mirrored to Rel-17) | 17.5.0 | +| 2023-03 | RAN#99 | RP-230453 | 0415 | - | F | Rel-17 editorial corrections for TS 38.214 | 17.5.0 | +| 2023-06 | RAN#100 | RP-231220 | 0416 | - | F | Corrections to timeline for CSI feedback in TS38.214 | 17.6.0 | +| 2023-06 | RAN#100 | RP-231219 | 0417 | - | F | CR on the antenna switching capability indication for more than 4 Rx antenna | 17.6.0 | +| 2023-06 | RAN#100 | RP-231229 | 0419 | - | A | Clarification to the switching gap location of the UL Tx Switching | 17.6.0 | +| 2023-06 | RAN#100 | RP-231220 | 0420 | - | F | Corrections to spatial domain filter determination for directional LBT in TS38.214 | 17.6.0 | +| 2023-06 | RAN#100 | RP-231231 | 0422 | - | A | CR on TBS determination of a PUSCH retransmission with initial PUSCH scheduled by RAR UL grant | 17.6.0 | +| 2023-06 | RAN#100 | RP-231223 | 0423 | - | F | Clarification for half-duplex consideration in partial sensing based re-evaluation/pre-emption checking | 17.6.0 | +| 2023-06 | RAN#100 | RP-231219 | 0424 | - | F | Correction on default beam and configuration for HST-SFN | 17.6.0 | +| 2023-06 | RAN#100 | RP-231219 | 0426 | - | F | Correction on SFN configuration for HST-SFN | 17.6.0 | +| 2023-06 | RAN#100 | RP-231226 | 0427 | - | F | Rel-17 editorial corrections for TS 38.214 | 17.6.0 | +| 2023-09 | RAN#101 | RP-232445 | 0428 | - | F | CR on RI restriction description for NCJT in TS38.214 | 17.7.0 | +| 2023-09 | RAN#101 | RP-232447 | 0429 | - | F | Correction on timeline requirements for simultaneous PUCCH and PUSCH transmission of different priorities | 17.7.0 | +| 2023-09 | RAN#101 | RP-232445 | 0430 | - | F | Correction on SP CSI multiplexing on PUSCH after DCI activation | 17.7.0 | +| 2023-09 | RAN#101 | RP-232445 | 0431 | - | F | Correction on SFN configuration for CSI-RS reception using default beam | 17.7.0 | +| 2023-09 | RAN#101 | RP-232456 | 0432 | - | F | Correction on PUSCH repetition type B with DMRS bundling | 17.7.0 | +| 2023-09 | RAN#101 | RP-232456 | 0433 | - | F | Correction on the calculation of the number of coded modulation symbols for UCI multiplexing on TBoMS | 17.7.0 | +| 2023-09 | RAN#101 | RP-232531 | 0436 | - | F | Rel-17 editorial corrections for TS 38.214 | 17.7.0 | +| 2023-09 | RAN#101 | RP-232458 | 0437 | - | B | Introduction of specification support for MIMO enhancements on CSI | 18.0.0 | +| 2023-09 | RAN#101 | RP-232458 | 0438 | - | B | Introduction of specification support for MIMO enhancements on uTCI STxMP_DMRS_SRS_8Tx_2TA | 18.0.0 | +| 2023-09 | RAN#101 | RP-232473 | 0439 | - | B | Introduction of specification support for mobility enhancements | 18.0.0 | +| 2023-09 | RAN#101 | RP-232480 | 0440 | - | B | Introduction of specification support for Expanded and Improved NR Positioning | 18.0.0 | +| 2023-09 | RAN#101 | RP-232469 | 0441 | - | B | Introduction of specification enhancements for NR sidelink evolution | 18.0.0 | +| 2023-09 | RAN#101 | RP-232471 | 0442 | - | B | Introduction of multi-cell PDSCH / PUSCH scheduling | 18.0.0 | +| 2023-09 | RAN#101 | RP-232470 | 0443 | - | B | Introduction of dynamic spectrum sharing enhancements | 18.0.0 | +| 2023-09 | RAN#101 | RP-232483 | 0444 | - | B | Introduction of specification support for BandWidth Part operation without restriction in NR | 18.0.0 | +| 2023-09 | RAN#101 | RP-232472 | 0445 | - | B | Introduction of further NR coverage enhancements | 18.0.0 | +| 2023-09 | RAN#101 | RP-232474 | 0446 | - | B | Introduction of specification support for NR NTN enhancements | 18.0.0 | +| 2023-09 | RAN#101 | RP-232481 | 0447 | - | B | Introduction of specification support for network energy saving | 18.0.0 | +| 2023-09 | RAN#101 | RP-232482 | 0448 | - | B | Introduction of specification for XR Enhancements for NR | 18.0.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------|--------| +| | | | | | | | | +| 2023-09 | RAN#101 | RP-232478 | 0449 | - | B | Introduction of enhanced reduced capability NR devices | 18.0.0 | +| 2023-12 | RAN#102 | RP-233700 | 0455 | - | A | Corrections on Partial Sensing Occasion | 18.1.0 | +| 2023-12 | RAN#102 | RP-233697 | 0457 | - | A | CR on one from more than one indicated TCI state applied for unified TCI framework in TS38.214 | 18.1.0 | +| 2023-12 | RAN#102 | RP-233727 | 0459 | - | A | Correction on the order of SRS transmissions on multiple uplinks triggered by DCI 2_3 for SRS carrier switching | 18.1.0 | +| 2023-12 | RAN#102 | RP-233698 | 0461 | - | A | CR on resource allocation in time domain for multi-PXSCH scheduling | 18.1.0 | +| 2023-12 | RAN#102 | RP-233726 | 0464 | - | A | CR on slot offset calculation for PUSCH carrying aperiodic CSI with no transport block | 18.1.0 | +| 2023-12 | RAN#102 | RP-233697 | 0466 | - | A | CR on UL beam after 2-step RACH | 18.1.0 | +| 2023-12 | RAN#102 | RP-233697 | 0468 | - | A | CR on default beam based on unified TCI framework | 18.1.0 | +| 2023-12 | RAN#102 | RP-233735 | 0470 | - | A | Correction to the SRS transmission collision | 18.1.0 | +| 2023-12 | RAN#102 | RP-233732 | 0473 | - | A | CR on Memory issue associated to slot offset determination for A-CSI without data | 18.1.0 | +| 2023-12 | RAN#102 | RP-233697 | 0475 | - | A | CR on clarification of CSI-RS transmission occasion for NCJT CSI | 18.1.0 | +| 2023-12 | RAN#102 | RP-233727 | 0477 | - | A | Correction for SRS carrier switching for DCI formats 1_1 and 1_2 | 18.1.0 | +| 2023-12 | RAN#102 | RP-233736 | 0479 | 1 | A | Correction of PUSCH repetition for RedCap UE with NCD-SSB in TDD | 18.1.0 | +| 2023-12 | RAN#102 | RP-233728 | 0481 | - | A | Rel-17 editorial corrections for TS 38.214 (mirrored to Rel-18) | 18.1.0 | +| 2023-12 | RAN#102 | RP-233720 | 0482 | - | F | Correction of specification support for network energy saving | 18.1.0 | +| 2023-12 | RAN#102 | RP-233705 | 0483 | - | F | Correction of specification support for MIMO enhancements on CSI | 18.1.0 | +| 2023-12 | RAN#102 | RP-233705 | 0484 | - | F | Correction of specification support for MIMO enhancements on uTCI_STxMP_DMRS_SRS_8Tx_2TA | 18.1.0 | +| 2023-12 | RAN#102 | RP-233710 | 0485 | - | F | Corrections of specification support for mobility enhancements | 18.1.0 | +| 2023-12 | RAN#102 | RP-233714 | 0486 | - | F | Correction of specification support for NR NTN enhancements | 18.1.0 | +| 2023-12 | RAN#102 | RP-233719 | 0487 | - | F | Corrections on the support for Expanded and Improved NR Positioning | 18.1.0 | +| 2023-12 | RAN#102 | RP-233706 | 0488 | - | F | Correction of enhancements for NR sidelink evolution | 18.1.0 | +| 2023-12 | RAN#102 | RP-233717 | 0489 | - | F | Correction of enhanced reduced capability NR devices | 18.1.0 | +| 2023-12 | RAN#102 | RP-233721 | 0490 | - | F | Corrections of XR Enhancements for NR | 18.1.0 | +| 2023-12 | RAN#102 | RP-233708 | 0491 | - | B | Introduction of UL Tx switching across up to 4 bands | 18.1.0 | +| 2023-12 | RAN#102 | RP-233709 | 0492 | - | F | Corrections on further NR coverage enhancements | 18.1.0 | +| 2023-12 | RAN#102 | RP-233708 | 0493 | - | F | Corrections on multi-cell PDSCH / PUSCH scheduling | 18.1.0 | +| 2023-12 | RAN#102 | RP-233716 | 0494 | - | B | Introduction of NR support for dedicated spectrum less than 5MHz for FR1 | 18.1.0 | +| 2023-12 | RAN#102 | RP-233733 | 0495 | - | B | Introduction of Rel-18 enhancements of NR Multicast and Broadcast Services | 18.1.0 | +| 2023-12 | RAN#102 | RP-233718 | 0496 | - | B | Introduction of Network Controlled Repeaters | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38215/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38215/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..980df83485fac65f5aff7313ec050a726d4306ee --- /dev/null +++ b/marked/Rel-18/38_series/38215/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:677cdf2c445266a435ad55b25804dc48e0ac51989aab8a879e2e6b097d199169 +size 9494 diff --git a/marked/Rel-18/38_series/38215/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38215/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88e82a0e475ee76f0810896893c588a6849ddfb4 --- /dev/null +++ b/marked/Rel-18/38_series/38215/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec8c567cb3358007a0cfe445c46a399632ea57597efa105b484ce648d3660273 +size 6986 diff --git a/marked/Rel-18/38_series/38215/raw.md b/marked/Rel-18/38_series/38215/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..15a71c29de4e057e3602dd9b19edf57b84ec4a15 --- /dev/null +++ b/marked/Rel-18/38_series/38215/raw.md @@ -0,0 +1,764 @@ + + +# 3GPP TS 38.215 V18.1.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer measurements (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** + +3GPP, New 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. + +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 of terms, symbols and abbreviations..... | 6 | +| 3.1 Terms..... | 6 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 Control of UE/NG-RAN measurements ..... | 7 | +| 5 Measurement capabilities for NR ..... | 8 | +| 5.1 UE measurement capabilities..... | 8 | +| 5.1.1 SS reference signal received power (SS-RSRP)..... | 9 | +| 5.1.2 CSI reference signal received power (CSI-RSRP)..... | 10 | +| 5.1.3 SS reference signal received quality (SS-RSRQ)..... | 11 | +| 5.1.4 CSI reference signal received quality (CSI-RSRQ)..... | 12 | +| 5.1.5 SS signal-to-noise and interference ratio (SS-SINR)..... | 12 | +| 5.1.6 CSI signal-to-noise and interference ratio (CSI-SINR)..... | 13 | +| 5.1.7 Void ..... | 13 | +| 5.1.8 Void ..... | 13 | +| 5.1.9 UE GNSS Timing of Cell Frames for UE positioning for E-UTRA..... | 13 | +| 5.1.10 UE GNSS code measurements ..... | 13 | +| 5.1.11 UE GNSS carrier phase measurements ..... | 14 | +| 5.1.12 IEEE 802.11 WLAN RSSI ..... | 14 | +| 5.1.13 Reference signal time difference (RSTD) for E-UTRA..... | 14 | +| 5.1.14 SFN and frame timing difference (SFTD)..... | 14 | +| 5.1.15 E-UTRA RSRP..... | 15 | +| 5.1.16 E-UTRA RSRQ..... | 15 | +| 5.1.17 E-UTRA RS-SINR ..... | 16 | +| 5.1.18 SS reference signal received power per branch (SS-RSRPB)..... | 16 | +| 5.1.19 SRS reference signal received power (SRS-RSRP)..... | 17 | +| 5.1.20 CLI Received signal strength indicator (CLI-RSSI) ..... | 17 | +| 5.1.21 Received Signal Strength Indicator (RSSI)..... | 17 | +| 5.1.22 PSBCH reference signal received power (PSBCH-RSRP)..... | 18 | +| 5.1.23 PSSCH reference signal received power (PSSCH-RSRP)..... | 18 | +| 5.1.24 PSCCH reference signal received power (PSCCH-RSRP)..... | 19 | +| 5.1.25 Sidelink received signal strength indicator (SL RSSI)..... | 19 | +| 5.1.26 Sidelink channel occupancy ratio (SL CR) ..... | 19 | +| 5.1.27 Sidelink channel busy ratio (SL CBR)..... | 20 | +| 5.1.28 DL PRS reference signal received power (DL PRS-RSRP)..... | 20 | +| 5.1.29 DL reference signal time difference (DL RSTD)..... | 20 | +| 5.1.30 UE Rx – Tx time difference ..... | 21 | +| 5.1.31 SS reference signal antenna relative phase (SS-RSARP)..... | 21 | +| 5.1.32 UTRA FDD CPICH RSCP..... | 22 | +| 5.1.33 UTRA FDD carrier RSSI ..... | 22 | +| 5.1.34 UTRA FDD CPICH Ec/No ..... | 22 | +| 5.1.35 DL PRS reference signal received path power (DL PRS-RSRPP) ..... | 22 | +| 5.1.36 Sidelink PRS reference signal received power (SL PRS-RSRP)..... | 23 | +| 5.1.37 Sidelink PRS reference signal received path power (SL PRS-RSRPP)..... | 23 | +| 5.1.38 Sidelink relative time of arrival (T SL-RTOA )..... | 23 | +| 5.1.39 Sidelink angle of arrival (SL AoA) ..... | 24 | +| 5.1.40 Sidelink Rx – Tx time difference ..... | 24 | +| 5.1.41 Sidelink reference signal time difference (SL RSTD)..... | 24 | +| 5.1.42 DL reference signal carrier phase (DL RSCP)..... | 25 | +| 5.1.43 DL reference signal carrier phase difference (DL RSCPD)..... | 25 | +| 5.1.44 Sidelink PRS received signal strength indicator (SL PRS-RSSI) ..... | 25 | +| 5.1.45 Time domain channel property (TDCP)..... | 26 | + +5.1.46 UE Rx – Tx time difference subframe offset ..... 26 +5.1.47 DL timing drift ..... 26 +5.1.48 Sidelink PRS channel occupancy ratio (SL PRS-CR)..... 26 +5.1.49 Sidelink PRS channel busy ratio (SL PRS-CBR)..... 27 +5.2 NG-RAN measurement abilities ..... 27 +5.2.1 SSS transmit power ..... 27 +5.2.2 UL Relative Time of Arrival (TUL-RTOA)..... 28 +5.2.3 gNB Rx – Tx time difference ..... 28 +5.2.4 UL Angle of Arrival (UL AoA) ..... 29 +5.2.5 UL SRS reference signal received power (UL SRS-RSRP)..... 29 +5.2.6 UL SRS reference signal received path power (UL SRS-RSRPP) ..... 29 +5.2.7 Timing advance (TADV)..... 30 +5.2.8 UL reference signal carrier phase (UL RSCP) ..... 30 +**Annex A: 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 physical layer measurements for NR. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications" +- [2] 3GPP TS 38.201: "NR; Physical Layer – General Description" +- [3] 3GPP TS 38.211: "NR; Physical channels and modulation" +- [4] 3GPP TS 38.212: "NR; Multiplexing and channel coding" +- [5] 3GPP TS 38.213: "NR; Physical layer procedures for control channels" +- [6] 3GPP TS 38.214: "NR; Physical layer procedures for data channels" +- [7] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification" +- [8] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification" +- [9] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception" +- [10] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification" +- [11] IEEE 802.11, Part 11: "Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications, IEEE Std." +- [12] 3GPP TS 38.133: "NR; Requirements for support of radio resource management" +- [13] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation" +- [14] 3GPP TS 38.509: "5GS; Special conformance testing functions for User Equipment (UE)" +- [15] 3GPP TS 38.901: "Study on channel model for frequencies from 0.5 to 100 GHz" +- [16] 3GPP TS 38.455: "NR Positioning Protocol A (NRPPa)" +- [17] 3GPP TS 37.213: "Physical layer procedures for shared spectrum channel access" +- [18] 3GPP TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN" + +# --- 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] 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: + +## 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]. + +| | | +|----------|----------------------------------------------------------| +| ARFCN | Absolute Radio-Frequency Channel Number | +| CLI | Cross Link Interference | +| CSI-RSRP | CSI Reference Signal Received Power | +| CSI-RSRQ | CSI Reference Signal Received Quality | +| E-UTRAN | Evolved UTRAN | +| GNSS | Global Navigation Satellite System | +| GSM | Global System for Mobile communication | +| LBT | Listen Before Talk | +| SRS | Sounding Reference Signal | +| SS-RSRP | Synchronization Signal Reference Signal Received Power | +| SS-RSRQ | Synchronization Signal Reference Signal Received Quality | +| UTRAN | Universal Terrestrial Radio Access Network | + +# --- 4 Control of UE/NG-RAN 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. + +With the measurement specifications L1 provides measurement capabilities for the UE and NG-RAN. These measurements can be classified in different reported measurement types: intra-frequency, inter-frequency, inter-system, traffic volume, quality and UE internal measurements. + +In the L1 measurement definitions, see clause 5, the measurements are categorised as measurements in the UE or measurements in the NG-RAN. + +# 5 Measurement capabilities for NR + +## 5.1 UE measurement capabilities + +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 state(s) it shall be possible to perform this measurement. The following terms are used in the tables:
RRC_IDLE;
RRC_INACTIVE;
RRC_CONNECTED;

Intra-frequency appended to the RRC state:
Shall be possible to perform in the corresponding RRC state on an intra-frequency cell;

Inter-frequency 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.

If sidelink: it shall be possible to perform this measurement on sidelink.

| + +### 5.1.1 SS reference signal received power (SS-RSRP) + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

SS reference signal received power (SS-RSRP) is defined as the linear average over the power contributions (in [W]) of the resource elements that carry secondary synchronization signals. The measurement time resource(s) for SS-RSRP are confined within SS/PBCH Block Measurement Time Configuration (SMTC) window duration. If SS-RSRP is used for L1-RSRP as configured by reporting configurations as defined in TS 38.214 [6], the measurement time resources(s) restriction by SMTC window duration is not applicable.

For SS-RSRP determination demodulation reference signals for physical broadcast channel (PBCH) and, if indicated by higher layers, CSI reference signals in addition to secondary synchronization signals may be used. SS-RSRP using demodulation reference signal for PBCH or CSI reference signal shall be measured by linear averaging over the power contributions of the resource elements that carry corresponding reference signals taking into account power scaling for the reference signals as defined in TS 38.213 [5]. If SS-RSRP is not used for L1-RSRP, the additional use of CSI reference signals for SS-RSRP determination is not applicable.

SS-RSRP shall be measured only among the reference signals corresponding to SS/PBCH blocks with the same SS/PBCH block index and the same physical-layer cell identity.

If SS-RSRP is not used for L1-RSRP and higher-layers indicate certain SS/PBCH blocks for performing SS-RSRP measurements, then SS-RSRP is measured only from the indicated set of SS/PBCH block(s).

For frequency range 1, the reference point for the SS-RSRP shall be the antenna connector of the UE. For frequency range 2, SS-RSRP shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch. For frequency range 1 and 2, if receiver diversity is in use by the UE, the reported SS-RSRP value shall not be lower than the corresponding SS-RSRP of any of the individual receiver branches.

| +| Applicable for |

If SS-RSRP is used for L1-RSRP,
RRC_CONNECTED intra-frequency.

Otherwise,
RRC_IDLE intra-frequency,
RRC_IDLE inter-frequency,
RRC_INACTIVE intra-frequency,
RRC_INACTIVE inter-frequency,
RRC_CONNECTED intra-frequency,
RRC_CONNECTED inter-frequency

| + +NOTE 1: The number of resource elements within the measurement period that are used by the UE to determine SS-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.2 CSI reference signal received power (CSI-RSRP) + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

CSI reference signal received power (CSI-RSRP), is defined as the linear average over the power contributions (in [W]) of the resource elements of the antenna port(s) that carry CSI reference signals configured for RSRP measurements within the considered measurement frequency bandwidth in the configured CSI-RS occasions.

For CSI-RSRP determination CSI reference signals transmitted on antenna port 3000 according to TS 38.211 [4] shall be used. If CSI-RSRP is used for L1-RSRP, CSI reference signals transmitted on antenna ports 3000, 3001 can be used for CSI-RSRP determination.

For intra-frequency CSI-RSRP measurements, if the measurement gap is not configured, UE is not expected to measure the CSI-RS resource(s) outside of the active downlink bandwidth part.

For frequency range 1, the reference point for the CSI-RSRP shall be the antenna connector of the UE. For frequency range 2, CSI-RSRP shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch. For frequency range 1 and 2, if receiver diversity is in use by the UE, the reported CSI-RSRP value shall not be lower than the corresponding CSI-RSRP of any of the individual receiver branches.

| +| Applicable for |

If CSI-RSRP is used for L1-RSRP,
RRC_CONNECTED intra-frequency.

Otherwise,
RRC_CONNECTED intra-frequency,
RRC_CONNECTED inter-frequency

| + +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 CSI-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.3 SS reference signal received quality (SS-RSRQ) + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Secondary synchronization signal reference signal received quality (SS-RSRQ) is defined as the ratio of N \times \text{SS-RSRP} / \text{NR carrier RSSI}, where N is the number of resource blocks in the NR carrier RSSI measurement bandwidth. The measurements in the numerator and denominator shall be made over the same set of resource blocks.

NR carrier Received Signal Strength Indicator (NR carrier RSSI), comprises the linear average of the total received power (in [W]) observed only in certain OFDM symbols of measurement time resource(s), in the measurement bandwidth, over N number of resource blocks from all sources, including co-channel serving and non-serving cells, adjacent channel interference, thermal noise etc. For cell selection, according to Clause 4.1 of TS 38.211 [12], the measurement time resource(s) for NR Carrier RSSI are not constrained. Otherwise, the measurement time resource(s) for NR Carrier RSSI are confined within SS/PBCH Block Measurement Time Configuration (SMTC) window duration.

If indicated by higher-layers, if measurement gap is not used, the NR Carrier RSSI is measured in slots within the SMTC window duration that are indicated by the higher layer parameter measurementSlots and in OFDM symbols given by Table 5.1.3-1 and, if measurement gap is used, the NR Carrier RSSI is measured in slots within the SMTC window duration that are indicated by the higher layer parameter measurementSlots and in OFDM symbols given by Table 5.1.3-1 that are overlapped with the measurement gap, which is defined in TS 38.133 [12].

  • - For intra-frequency measurements, NR Carrier RSSI is measured with timing reference corresponding to the serving cell in the frequency layer
  • - For inter-frequency measurements, NR Carrier RSSI is measured with timing reference corresponding to any cell in the target frequency layer

Otherwise not indicated by higher-layers, if measurement gap is not used, NR Carrier RSSI is measured from OFDM symbols within SMTC window duration and, if measurement gap is used, NR Carrier RSSI is measured from OFDM symbols corresponding to overlapped time span between SMTC window duration and the measurement gap.

If higher-layers indicate certain SS/PBCH blocks for performing SS-RSRQ measurements, then SS-RSRP is measured only from the indicated set of SS/PBCH block(s).

For frequency range 1, the reference point for the SS-RSRQ shall be the antenna connector of the UE. For frequency range 2, NR Carrier RSSI shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch, where the combining for NR Carrier RSSI shall be the same as the one used for SS-RSRP measurements. For frequency range 1 and 2, if receiver diversity is in use by the UE, the reported SS-RSRQ value shall not be lower than the corresponding SS-RSRQ of any of the individual receiver branches.

| +| Applicable for | RRC_IDLE intra-frequency,
RRC_IDLE inter-frequency,
RRC_INACTIVE intra-frequency,
RRC_INACTIVE inter-frequency,
RRC_CONNECTED intra-frequency,
RRC_CONNECTED inter-frequency | + +**Table 5.1.3-1: NR Carrier RSSI measurement symbols** + +| OFDM signal indication
endSymbol | Symbol indexes | +|--------------------------------------------|------------------------------------------------------------------------------| +| 0 | {0,1} | +| 1 | For 480 kHz and 960 kHz
{0,1,2,...,11,12}; otherwise
{0,1,2,...,10,11} | +| 2 | {0,1,2,..., 5} | +| 3 | {0,1,2,..., 7} | + +### 5.1.4 CSI reference signal received quality (CSI-RSRQ) + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

CSI reference signal received quality (CSI-RSRQ) is defined as the ratio of N \times \text{CSI-RSRP} to \text{CSI-RSSI}, where N is the number of resource blocks in the \text{CSI-RSSI} measurement bandwidth. The measurements in the numerator and denominator shall be made over the same set of resource blocks.

CSI Received Signal Strength Indicator (CSI-RSSI), comprises the linear average of the total received power (in [W]) observed only in OFDM symbols of measurement time resource(s), in the measurement bandwidth, over N number of resource blocks from all sources, including co-channel serving and non-serving cells, adjacent channel interference, thermal noise etc. The measurement time resource(s) for CSI-RSSI corresponds to OFDM symbols containing configured CSI-RS occasions.

For CSI-RSRQ determination CSI reference signals transmitted on antenna port 3000 according to TS 38.211 [4] shall be used.

For intra-frequency CSI-RSRQ measurements, if the measurement gap is not configured, UE is not expected to measure the CSI-RS resource(s) outside of the active downlink bandwidth part.

For frequency range 1, the reference point for the CSI-RSRQ shall be the antenna connector of the UE. For frequency range 2, CSI-RSSI shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch, where the combining for CSI-RSSI shall be the same as the one used for CSI-RSRP measurements. For frequency range 1 and 2, if receiver diversity is in use by the UE, the reported CSI-RSRQ value shall not be lower than the corresponding CSI-RSRQ of any of the individual receiver branches.

| +| Applicable for |

RRC_CONNECTED intra-frequency,
RRC_CONNECTED inter-frequency

| + +### 5.1.5 SS signal-to-noise and interference ratio (SS-SINR) + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

SS signal-to-noise and interference ratio (SS-SINR), is defined as the linear average over the power contribution (in [W]) of the resource elements carrying secondary synchronisation signals divided by the linear average of the noise and interference power contribution (in [W]). If SS-SINR is used for L1-SINR reporting with dedicated interference measurement resources, the interference and noise is measured over resource(s) indicated by higher layers as described in TS 38.214 [6]. Otherwise, the interference and noise are measured over the resource elements carrying secondary synchronisation signals within the same frequency bandwidth. The measurement time resource(s) for SS-SINR are confined within SS/PBCH Block Measurement Time Configuration (SMTC) window duration. If SS-SINR is used for L1-SINR as configured by reporting configurations defined in TS 38.214 [6], the measurement time resource(s) restriction by SMTC window duration is not applicable.

For SS-SINR determination demodulation reference signals for physical broadcast channel (PBCH) in addition to secondary synchronization signals may be used.

If SS-SINR is not used for L1-SINR and higher-layers indicate certain SS/PBCH blocks for performing SS-SINR measurements, then SS-SINR is measured only from the indicated set of SS/PBCH block(s).

For frequency range 1, the reference point for the SS-SINR shall be the antenna connector of the UE. For frequency range 2, SS-SINR shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch. For frequency range 1 and 2, if receiver diversity is in use by the UE, the reported SS-SINR value shall not be lower than the corresponding SS-SINR of any of the individual receiver branches.

| +| Applicable for |

If SS-SINR is used for L1-SINR,
RRC_CONNECTED intra-frequency.

Otherwise,
RRC_CONNECTED intra-frequency,
RRC_CONNECTED inter-frequency

| + +### 5.1.6 CSI signal-to-noise and interference ratio (CSI-SINR) + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

CSI signal-to-noise and interference ratio (CSI-SINR), is defined as the linear average over the power contribution (in [W]) of the resource elements carrying CSI reference signals divided by the linear average of the noise and interference power contribution (in [W]). If CSI-SINR is used for L1-SINR reporting with dedicated interference measurement resources, the interference and noise is measured over resource(s) indicated by higher layers as described in TS 38.214 [6]. Otherwise, the interference and noise are measured over the resource elements carrying CSI reference signals within the same frequency bandwidth.

For CSI-SINR determination CSI reference signals transmitted on antenna port 3000 according to TS 38.211 [4] shall be used. If CSI-SINR is used for L1-SINR, CSI reference signals transmitted on antenna ports 3000, 3001 can be used for CSI-SINR determination.

For intra-frequency CSI-SINR measurements not used for L1-SINR reporting, if the measurement gap is not configured, UE is not expected to measure the CSI-RS resource(s) outside of the active downlink bandwidth part.

For frequency range 1, the reference point for the CSI-SINR shall be the antenna connector of the UE. For frequency range 2, CSI-SINR shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch. For frequency range 1 and 2, if receiver diversity is in use by the UE, the reported CSI-SINR value shall not be lower than the corresponding CSI-SINR of any of the individual receiver branches.

| +| Applicable for |

If CSI-SINR is used for L1-SINR,
RRC_CONNECTED intra-frequency.

Otherwise,
RRC_CONNECTED intra-frequency,
RRC_CONNECTED inter-frequency

| + +5.1.7 Void + +5.1.8 Void + +### 5.1.9 UE GNSS Timing of Cell Frames for UE positioning for E-UTRA + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The timing between E-UTRA cell j and a GNSS-specific reference time for a given GNSS (e.g., GPS/Galileo/Glonass system time). T_{UE-GNSSj} is defined as the time of occurrence of a specified NG-RAN event according to GNSS time for a given GNSS Id. The specified NG-RAN event is the beginning of a particular frame (identified through its SFN) in the first detected path (in time) of the cell-specific reference signals of the cell j, where cell j is a cell chosen by the UE. The reference point for T_{UE-GNSSj} shall be the antenna connector of the UE.

| +| Applicable for | RRC_CONNECTED inter-RAT | + +### 5.1.10 UE GNSS code measurements + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The GNSS code phase (integer and fractional parts) of the spreading code of the i^{th} GNSS satellite signal. The reference point for the GNSS code phase shall be the antenna connector of the UE.

| +| Applicable for | Void (this measurement is not related to NG-RAN/E-UTRAN/UTRAN/GSM signals; its applicability is therefore independent of the UE RRC state) | + +### 5.1.11 UE GNSS carrier phase measurements + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The number of carrier-phase cycles (integer and fractional parts) of the $i^{\text{th}}$ GNSS satellite signal, measured since locking onto the signal. Also called Accumulated Delta Range (ADR). The reference point for the GNSS carrier phase shall be the antenna connector of the UE. | +| Applicable for | Void (this measurement is not related to NG-RAN/E-UTRAN/UTRAN/GSM signals; its applicability is therefore independent of the UE RRC state) | + +### 5.1.12 IEEE 802.11 WLAN RSSI + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The IEEE 802.11 WLAN RSSI as used in RRC specification [10] refers to RSSI as defined in IEEE 802.11 specification [11], measured from Beacon, DMG Beacon or FILS discovery frames (in passive scanning mode) or from probe response frames (in active scanning mode). | +| Applicable for | RRC_CONNECTED inter-RAT,
RRC_INACTIVE inter-RAT,
RRC_IDLE inter-RAT | + +### 5.1.13 Reference signal time difference (RSTD) for E-UTRA + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | The relative timing difference between the E-UTRA neighbour cell j and the E-UTRA reference cell i, defined as $T_{\text{SubframeRsj}} - T_{\text{SubframeRxi}}$ , where: $T_{\text{SubframeRsj}}$ is the time when the UE receives the start of one subframe from E-UTRA cell j $T_{\text{SubframeRxi}}$ is the time when the UE receives the corresponding start of one subframe from E-UTRA cell i that is closest in time to the subframe received from E-UTRA cell j. The reference point for the observed subframe time difference shall be the antenna connector of the UE. | +| Applicable for | RRC_CONNECTED inter-RAT | + +### 5.1.14 SFN and frame timing difference (SFTD) + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The observed SFN and frame timing difference (SFTD) between an E-UTRA PCell and an NR PSCell (for EN-DC), or an NR PCell and an E-UTRA PSCell (for NE-DC), or an NR PCell and an NR PSCell (for NR-DC), or an NR PCell and NR neighbour cell (for UEs with NR PCell but no E-UTRA/NR PSCell) is defined as comprising the following two components:

  • - SFN offset = (\text{SFN}_{\text{PCell}} - \text{SFN}_{\text{TRGCell}}) \bmod 1024, where \text{SFN}_{\text{PCell}} is the SFN of a PCell radio frame and \text{SFN}_{\text{TRGCell}} is the SFN of the target cell radio frame of which the UE receives the start closest in time to the time when it receives the start of the PCell radio frame.
  • - Frame boundary offset = \left\lfloor (T_{\text{FrameBoundaryPCell}} - T_{\text{FrameBoundaryTRGCell}}) / 5 \right\rfloor, where T_{\text{FrameBoundaryPCell}} is the time when the UE receives the start of a radio frame from the PCell, T_{\text{FrameBoundaryTRGCell}} is the time when the UE receives the start of the radio frame, from the target cell, that is closest in time to the radio frame received from the PCell. The unit of (T_{\text{FrameBoundaryPCell}} - T_{\text{FrameBoundaryTRGCell}}) is T_s.
| +| Applicable for | RRC_CONNECTED intra-frequency for EN-DC, NE-DC, NR-DC
RRC_CONNECTED inter-frequency for UEs with NR PCell but no E-UTRA/NR PSCell | + +### 5.1.15 E-UTRA RSRP + +| | | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

E-UTRA Reference signal received power (E-UTRA 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 E-UTRA RSRP determination the cell-specific reference signals R_0 according to TS 36.211 [3] 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 E-UTRA RSRP.

If higher layers indicate measurements based on discovery signals, the UE shall measure E-UTRA RSRP in the subframes in the configured discovery signal occasions. For frame structure 1 and 2, if the UE can reliably detect that cell-specific reference signals are present in other subframes, the UE may use those subframes in addition to determine E-UTRA RSRP.

The reference point for the E-UTRA 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 E-UTRA RSRP of any of the individual diversity branches.

| +| Applicable for | RRC_IDLE inter-RAT,
RRC_INACTIVE inter-RAT,
RRC_CONNECTED 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 E-UTRA 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.16 E-UTRA RSRQ + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

E-UTRA Reference Signal Received Quality (E-UTRA RSRQ) is defined as the ratio N \times \text{E-UTRA RSRP} / (\text{E-UTRA carrier RSSI}), where N is the number of RBs 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 (E-UTRA 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, E-UTRA 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 E-UTRA RSRQ measurements, then E-UTRA RSSI is measured from all OFDM symbols of the DL part of measurement subframes. If higher layers indicate certain subframes for performing E-UTRA RSRQ measurements, then E-UTRA RSSI is measured from all OFDM symbols of the DL part of the indicated subframes.

If higher layers indicate measurements based on discovery signals, E-UTRA RSSI is measured from all OFDM symbols of the DL part of the subframes in the configured discovery signal occasions.

The reference point for the E-UTRA 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 E-UTRA RSRQ of any of the individual diversity branches.

| +| Applicable for | RRC_IDLE inter-RAT,
RRC_INACTIVE inter-RAT,
RRC_CONNECTED inter-RAT | + +### 5.1.17 E-UTRA RS-SINR + +| | | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

E-UTRA reference signal-signal to noise and interference ratio (E-UTRA RS-SINR), is defined as the linear average over the power contribution (in [W]) of the resource elements carrying cell-specific reference signals divided by the linear average of the noise and interference power contribution (in [W]) over the resource elements carrying cell-specific reference signals within the same frequency bandwidth.

For E-UTRA RS-SINR determination, the E-UTRA cell-specific reference signals R_0 according TS 36.211 [13] shall be used.

The reference point for the E-UTRA RS-SINR 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 E-UTRA RS-SINR of any of the individual diversity branches.

If higher-layer signalling indicates certain subframes for performing E-UTRA RS-SINR measurements, then E-UTRA RS-SINR is measured in the indicated subframes.

| +| Applicable for | RRC_CONNECTED inter-RAT | + +### 5.1.18 SS reference signal received power per branch (SS-RSRPB) + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

SS reference signal received power per branch (SS-RSRPB) is defined as the linear average over the power contributions (in [W]) of the resource elements that carry secondary synchronization signals (SS). The measurement time resource(s) for SS-RSRPB are confined within SS/PBCH Block Measurement Time Configuration (SMTC) window duration.

For SS-RSRPB determination demodulation reference signals for physical broadcast channel (PBCH) in addition to secondary synchronization signals may be used. SS-RSRPB using demodulation reference signal for PBCH shall be measured by linear averaging over the power contributions of the resource elements that carry corresponding reference signals taking into account power scaling for the reference signals as defined in TS 38.213 [5].

SS-RSRPB shall be measured only among the reference signals corresponding to SS/PBCH blocks with the same SS/PBCH block index and the same physical-layer cell identity.

If higher-layers indicate certain SS/PBCH blocks for performing SS-RSRPB measurements, then SS-RSRPB is measured only from the indicated set of SS/PBCH block(s).

For frequency range 1, SS-RSRPB shall be measured from each antenna connector of the UE. For frequency range 2, SS-RSRPB shall be measured for each receiver branch based on the combined signal from antenna elements corresponding to the receiver branch.

| +| Applicable for | RRC_CONNECTED intra-frequency | + +NOTE 1: The number of resource elements within the measurement period that are used by the UE to determine SS-RSRPB 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. + +NOTE 3: This UE measurement is defined only for conformance test purposes. It is described along with test control entity signalling in [14]. + +### 5.1.19 SRS reference signal received power (SRS-RSRP) + +| | | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

SRS reference signal received power (SRS-RSRP) is defined as linear average of the power contributions (in [W]) of the resource elements carrying sounding reference signals (SRS). SRS-RSRP shall be measured over the configured resource elements within the considered measurement frequency bandwidth in the configured measurement time occasions.

For frequency range 1, the reference point for the SRS-RSRP shall be the antenna connector of the UE. For frequency range 2, SRS-RSRP shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch. For frequency range 1 and 2, if receiver diversity is in use by the UE, the reported SRS-RSRP value shall not be lower than the corresponding SRS-RSRP of any of the individual receiver branches.

| +| Applicable for | RRC_CONNECTED intra-frequency | + +### 5.1.20 CLI Received signal strength indicator (CLI-RSSI) + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

CLI Received Signal Strength Indicator (CLI-RSSI), is defined as linear average of the total received power (in [W]) observed only in the configured OFDM symbols of the configured measurement time resource(s), in the configured measurement bandwidth from all sources, including co-channel serving and non-serving cells, adjacent channel interference, thermal noise etc.

For frequency range 1, the reference point for the RSSI shall be the antenna connector of the UE. For frequency range 2, CLI-RSSI shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch. For frequency range 1 and 2, if receiver diversity is in use by the UE, the reported CLI-RSSI value shall not be lower than the corresponding CLI-RSSI of any of the individual receiver branches.

| +| Applicable for | RRC_CONNECTED intra-frequency | + +### 5.1.21 Received Signal Strength Indicator (RSSI) + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Received Signal Strength Indicator (RSSI), comprises the linear average of the total received power (in [W]) observed only per configured OFDM symbol and in the measurement bandwidth indicated by higher layers or corresponding to the channel bandwidth defined in Clause 4 of TS 37.213 [17], where the channel has the center frequency configured by ARFCN-valueNR, by the UE from all sources, including co-channel serving and non-serving cells, adjacent channel interference, thermal noise etc.

Higher layers configure the ARFCN-valueNR, the reference numerology and the measurement duration, i.e., which OFDM symbol(s) should be measured by the UE.

For frequency range 1, the reference point for the RSSI shall be the antenna connector of the UE. For frequency range 2, RSSI shall be measured for each receiver branch based on the combined signal from antenna elements corresponding to the receiver branch. For frequency range 1 and 2, if receiver diversity is in use by the UE, the reported RSSI value shall not be lower than the corresponding RSSI of any of the individual receiver branches.

| +| Applicable for | RRC_CONNECTED intra-frequency,
RRC_CONNECTED inter-frequency | + +### 5.1.22 PSBCH reference signal received power (PSBCH-RSRP) + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

PSBCH Reference Signal Received Power (PSBCH-RSRP) is defined as the linear average over the power contributions (in [W]) of the resource elements that carry demodulation reference signals associated with physical sidelink broadcast channel (PSBCH).

For PSBCH-RSRP sidelink secondary synchronization signals in addition to demodulation reference signals for PSBCH may be used. PSBCH-RSRP using sidelink secondary synchronization signals shall be measured by linear averaging over the power contributions of the resource elements that carry corresponding reference signals.

For frequency range 1, the reference point for the PSBCH RSRP shall be the antenna connector of the UE. For frequency range 2, PSBCH-RSRP shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch. For frequency range 1 and 2, if receiver diversity is in use by the UE, the reported PSBCH-RSRP value shall not be lower than the corresponding PSBCH-RSRP of any of the individual receiver branches.

| +| Applicable for | Sidelink | + +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 PSBCH-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. + +NOTE 3: It is up to UE implementation to use PSBCH DMRS only or both S-SSS and PSBCH DMRS for PSBCH-RSRP. + +### 5.1.23 PSSCH reference signal received power (PSSCH-RSRP) + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

PSSCH Reference Signal Received Power (PSSCH-RSRP) is defined as the linear average over the power contributions (in [W]) of the resource elements of the antenna port(s) that carry demodulation reference signals associated with physical sidelink shared channel (PSSCH), summed over the antenna ports.

Demodulation reference signals transmitted on antenna ports 1000 and 1001 shall be used for PSSCH-RSRP determination if two antenna ports are indicated.

For frequency range 1, the reference point for the PSSCH-RSRP shall be the antenna connector of the UE. For frequency range 2, PSSCH-RSRP shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch. For frequency range 1 and 2, if receiver diversity is in use by the UE, the reported PSSCH-RSRP value shall not be lower than the corresponding PSSCH-RSRP of any of the individual receiver branches.

| +| Applicable for | Sidelink | + +NOTE 1: The power per resource element is determined from the energy received during the useful part of the symbol, excluding the CP. + +### 5.1.24 PSCCH reference signal received power (PSCCH-RSRP) + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

PSCCH Reference Signal Received Power (PSCCH-RSRP) is defined as the linear average over the power contributions (in [W]) of the resource elements that carry demodulation reference signals associated with physical sidelink control channel (PSCCH).

For frequency range 1, the reference point for the PSCCH-RSRP shall be the antenna connector of the UE. For frequency range 2, PSCCH-RSRP shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch. For frequency range 1 and 2, if receiver diversity is in use by the UE, the reported PSCCH-RSRP value shall not be lower than the corresponding PSCCH-RSRP of any of the individual receiver branches.

| +| Applicable for | Sidelink | + +NOTE 1: The power per resource element is determined from the energy received during the useful part of the symbol, excluding the CP. + +### 5.1.25 Sidelink received signal strength indicator (SL RSSI) + +| | | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Sidelink Received Signal Strength Indicator (SL RSSI) is defined as the linear average of the total received power (in [W]) observed in the configured sub-channel in OFDM symbols of a slot configured for PSCCH and PSSCH, starting from the 2nd OFDM symbol.

For frequency range 1, the reference point for the SL RSSI shall be the antenna connector of the UE. For frequency range 2, SL RSSI shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch. For frequency range 1 and 2, if receiver diversity is in use by the UE, the reported SL RSSI value shall not be lower than the corresponding SL RSSI of any of the individual receiver branches.

| +| Applicable for | Sidelink | + +### 5.1.26 Sidelink channel occupancy ratio (SL CR) + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Sidelink Channel Occupancy Ratio (SL CR) evaluated at slot n is defined as the total number of sub-channels used for its transmissions in slots [n-a, n-1] and granted in slots [n, n+b] divided by the total number of configured sub-channels in the transmission pool over [n-a, n+b].

| +| Applicable for | Sidelink | + +NOTE 1: $a$ is a positive integer and $b$ is 0 or a positive integer; $a$ and $b$ are determined by UE implementation with $a+b+1 = 1000$ or $1000 \cdot 2^\mu$ slots, according to higher layer parameter *sl-TimeWindowSizeCR*, $b < (a+b+1)/2$ , and $n+b$ shall not exceed the last transmission opportunity of the grant for the current transmission. + +NOTE 2: SL CR is evaluated for each (re)transmission. + +NOTE 3: In evaluating SL CR, the UE shall assume the transmission parameter used at slot $n$ is reused according to the existing grant(s) in slot $[n+1, n+b]$ without packet dropping. + +NOTE 4: The slot index is based on physical slot index. + +NOTE 5: SL CR can be computed per priority level + +NOTE 6: A resource is considered granted if it is a member of a selected sidelink grant as defined in TS 38.321 [7]. + +### 5.1.27 Sidelink channel busy ratio (SL CBR) + +| | | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | SL Channel Busy Ratio (SL CBR) measured in slot $n$ is defined as the portion of sub-channels in the resource pool whose SL RSSI measured by the UE exceed a (pre-)configured threshold provided by the higher layer parameter sl-ThreshS-RSSI-CBR sensed over a CBR measurement window $[n-a, n-1]$ , wherein $a$ is equal to 100 or $100 \cdot 2^\mu$ slots, according to higher layer parameter sl-TimeWindowSizeCBR . When UE is configured to perform partial sensing by higher layers (including when SL DRX is configured), SL RSSI is measured in slots where the UE performs partial sensing and where the UE performs PSCCH/PSSCH reception within the CBR measurement window. The calculation of SL CBR is limited within the slots for which the SL RSSI is measured. If the number of SL RSSI measurement slots within the CBR measurement window is below a (pre-)configured threshold, a (pre-)configured SL CBR value is used. | +| Applicable for | Sidelink | + +NOTE 1: The slot index is based on physical slot index. + +### 5.1.28 DL PRS reference signal received power (DL PRS-RSRP) + +| | | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | DL PRS reference signal received power (DL PRS-RSRP), is defined as the linear average over the power contributions (in [W]) of the resource elements that carry DL PRS reference signals configured for RSRP measurements within the considered measurement frequency bandwidth.

For frequency range 1, the reference point for the DL PRS-RSRP shall be the antenna connector of the UE. For frequency range 2, DL PRS-RSRP shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch. For frequency range 1 and 2, if receiver diversity is in use by the UE, the reported DL PRS-RSRP value shall not be lower than the corresponding DL PRS-RSRP of any of the individual receiver branches. | +| Applicable for | RRC_CONNECTED,
RRC_INACTIVE,
RRC_IDLE | + +### 5.1.29 DL reference signal time difference (DL RSTD) + +| | | +|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | DL reference signal time difference (DL RSTD) is the DL relative timing difference between the Transmission Point (TP) $[18] j$ and the reference TP $i$ , defined as $T_{\text{SubframeRxi}} - T_{\text{SubframeRxj}}$ ,

Where:
$T_{\text{SubframeRxi}}$ is the time when the UE receives the start of one subframe from TP $i$ .
$T_{\text{SubframeRxj}}$ is the time when the UE receives the corresponding start of one subframe from TP $j$ that is closest in time to the subframe received from TP $i$ .

Multiple DL PRS resources can be used to determine the start of one subframe from a TP.

For frequency range 1, the reference point for the DL RSTD shall be the antenna connector of the UE. For frequency range 2, the reference point for the DL RSTD shall be the antenna of the UE. | +| Applicable for | RRC_CONNECTED,
RRC_INACTIVE,
RRC_IDLE | + +### 5.1.30 UE Rx – Tx time difference + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The UE Rx – Tx time difference is defined as T_{UE-RX} - T_{UE-TX}

Where:
T_{UE-RX} is the UE received timing of downlink subframe #i from a Transmission Point (TP) [18], defined by the first detected path in time.
T_{UE-TX} is the UE transmit timing of uplink subframe #j that is closest in time to the subframe #i received from the TP.

Multiple DL PRS or CSI-RS for tracking resources, as instructed by higher layers, can be used to determine the start of one subframe of the first arrival path of the TP.

For frequency range 1, the reference point for T_{UE-RX} measurement shall be the Rx antenna connector of the UE and the reference point for T_{UE-TX} measurement shall be the Tx antenna connector of the UE. For frequency range 2, the reference point for T_{UE-RX} measurement shall be the Rx antenna of the UE and the reference point for T_{UE-TX} measurement shall be the Tx antenna of the UE.

| +| Applicable for | RRC_CONNECTED,
RRC_INACTIVE | + +### 5.1.31 SS reference signal antenna relative phase (SS-RSARP) + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

SS reference signal antenna relative phase (SS-RSARP) is defined as the difference of the average phase of the receive signals on the resource elements that carry secondary synchronization signals (SS) received by the reference individual receiver branch (Rx0) and the average phase of the receive signals on the resource elements that carry secondary synchronization signals (SS) received by one other individual receiver branch (Rx1 ... Rxn). The measurement time resource(s) for SS-RSARP are confined within SS/PBCH Block Measurement Time Configuration (SMTC) window duration.

SS-RSARP shall be measured only among the reference signals corresponding to SS/PBCH blocks with the same SS/PBCH block index and the same physical-layer cell identity.

If higher-layers indicate certain SS/PBCH blocks for performing SS-RSARP measurements, then SS-RSARP is measured only from the indicated set of SS/PBCH block(s).

For frequency range 1, the reference point for the SS-RSARP shall be the antenna connector of the UE. For frequency range 2, SS-RSARP shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch.

| +| Applicable for | RRC_CONNECTED intra-frequency | + +NOTE 1: The number of resource elements within the measurement period that are used by the UE to determine SS-RSARP is left up to the UE implementation with the limitation that corresponding measurement accuracy requirements have to be fulfilled. + +NOTE 2: The phase per resource element is determined from the energy received during the useful part of the symbol, excluding the CP. + +NOTE 3: This UE measurement is defined only for conformance test purposes. It is described along with test control entity signalling in [14]. + +### 5.1.32 UTRA FDD 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 reported value shall not be lower than the corresponding CPICH RSCP of any of the individual receive antenna branches. | +| Applicable for | RRC_CONNECTED inter-RAT | + +### 5.1.33 UTRA FDD 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 reported value shall not be lower than the corresponding UTRA carrier RSSI of any of the individual receive antenna branches. | +| Applicable for | RRC_CONNECTED inter-RAT | + +NOTE: This definition does not correspond to a reported measurement. This definition is just an intermediate definition used in the definition of UTRA FDD CPICH Ec/No. + +### 5.1.34 UTRA FDD 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 i of receive antenna branch i . | +| Applicable for | RRC_CONNECTED inter-RAT | + +### 5.1.35 DL PRS reference signal received path power (DL PRS-RSRPP) + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | DL PRS reference signal received path power (DL PRS-RSRPP), is defined as the power of the linear average of the channel response at the i -th path delay of the resource elements that carry DL PRS signal configured for the measurement, where DL PRS-RSRPP for the 1st path delay is the power contribution corresponding to the first detected path in time.

For frequency range 1, the reference point for the DL PRS-RSRPP shall be the antenna connector of the UE. For frequency range 2, DL PRS-RSRPP shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch.

For frequency range 1 and 2, if receiver diversity is in use by the UE for DL PRS-RSRPP measurements, the reported DL PRS-RSRPP value included in the higher layer parameter NR-DL-AoD-MeasElement for the first and additional measurements shall be provided for the same receiver branch(es) as applied for DL PRS-RSRP measurements. | +| Applicable for | RRC_CONNECTED,
RRC_INACTIVE,
RRC_IDLE | + +### 5.1.36 Sidelink PRS reference signal received power (SL PRS-RSRP) + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Sidelink PRS reference signal received power (SL PRS-RSRP) is defined as the linear average over the power contributions (in W) of the resource elements that carry SL PRS reference signals configured for RSRP measurements within the considered measurement frequency bandwidth.

For frequency range 1, the reference point for the SL PRS-RSRP shall be the antenna connector of the UE. For frequency range 1, if receiver diversity is in use by the UE, the reported SL PRS-RSRP value shall not be lower than the corresponding SL PRS-RSRP of any of the individual receiver branches.

For frequency range 2, SL PRS-RSRP shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch. If receiver diversity is in use by the UE, the reported SL PRS-RSRP value shall not be lower than the corresponding SL PRS-RSRP of any of the individual receiver branches.

| +| Applicable for | Sidelink | + +### 5.1.37 Sidelink PRS reference signal received path power (SL PRS-RSRPP) + +| | | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Sidelink PRS reference signal received path power (SL PRS-RSRPP) is defined as the power of the linear average of the channel response at the i-th path delay of the resource elements that carry SL PRS configured for the measurement, where SL PRS-RSRPP for the 1st path delay is the power contribution corresponding to the first detected path in time.

For frequency range 1, the reference point for the SL PRS-RSRPP shall be the antenna connector of the UE.

For frequency range 2, SL PRS-RSRPP shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch.

| +| Applicable for | Sidelink | + +### 5.1.38 Sidelink relative time of arrival ( $T_{SL-RTOA}$ ) + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The SL relative time of arrival (T_{SL-RTOA}) is defined as the beginning time of SL subframe # i containing SL PRS received from a UE, relative to the relative time of arrival (RTOA) reference time. The SL RTOA reference time is defined as T_0 + t_{SL-PRS}, where

  • - T_0 is the nominal beginning time of SFN 0 or DFN 0, provided by SFN and DFN initialization time, respectively.
  • - t_{SL-PRS} = (10n_f + n_{sf}) \times 10^{-3}, where n_f and n_{sf} are the SFN or DFN and the subframe number of the SL PRS, respectively.

For frequency range 1, the reference point for T_{SL-RTOA} measurement shall be the Rx antenna connector of the UE. For frequency range 2, the reference point for T_{SL-RTOA} measurement shall be the Rx antenna of the UE.

| +| Applicable for | Sidelink | + +### 5.1.39 Sidelink angle of arrival (SL AoA) + +| | | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The SL angle of arrival (SL AoA) is defined as the estimated azimuth angle and vertical angle of a transmitting UE with respect to a reference direction, wherein the reference direction is defined:

  • - In the global coordinate system (GCS), wherein estimated azimuth angle is measured relative to geographical North and is positive in a counter-clockwise direction and estimated vertical angle is measured relative to zenith and positive to horizontal direction
  • - In the local coordinate system (LCS), wherein estimated azimuth angle is measured relative to x-axis of LCS and positive in a counter-clockwise direction and estimated vertical angle is measured relative to z-axis of LCS and positive to x-y plane direction. The bearing, downtilt and slant angles of LCS are defined according to TS 38.901 [15].

The SL-AoA is determined at the receiving UE's antenna(s) for a SL channel corresponding to the transmitting UE.

| +| Applicable for | Sidelink | + +### 5.1.40 Sidelink Rx – Tx time difference + +| | | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The SL Rx – Tx time difference at a UE is defined as T_{UE-RX} - T_{UE-TX}

Where:

  • - T_{UE-RX} is the UE received timing of sidelink subframe #i from a transmitting UE, defined by the first detected path in time.
  • - If the UE reports the transmission timestamp of a SL PRS, T_{UE-TX} is the transmit timing of the sidelink subframe #j of the SL PRS of the UE. Otherwise, T_{UE-TX} is the transmit timing of the UE of sidelink subframe #j that is closest in time to the subframe #i received from the transmitting UE.
  • - The same antenna reference point is used for receiver and transmitter for the Rx-Tx time difference measurement.

If the UE reports the transmission timestamp of a SL PRS, the SL Rx-Tx time difference is modulo wrapped around to result in values between -0.5 ms to +0.5 ms.

For frequency range 1, the reference point for T_{UE-RX} measurement shall be the Rx antenna connector of the UE and the reference point for T_{UE-TX} measurement shall be the Tx antenna connector of the UE. For frequency range 2, the reference point for T_{UE-RX} measurement shall be the Rx antenna of the UE and the reference point for T_{UE-TX} measurement shall be the Tx antenna of the UE.

| +| Applicable for | Sidelink | + +### 5.1.41 Sidelink reference signal time difference (SL RSTD) + +| | | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The SL reference signal time difference (SL RSTD) is the SL relative timing difference between the UE j and the reference UE i, defined as T_{SL-RXi} - T_{SL-RXj}, where:

  • - T_{SL-RXj} is the time when the UE receives the start of one subframe from UE j
  • - T_{SL-RXi} is the time when the UE receives the corresponding start of one subframe from UE i that is closest in time to the subframe received from UE j

For frequency range 1, the reference point for SL RSTD measurement shall be the Rx antenna connector of the UE. For frequency range 2, the reference point for SL RSTD measurement shall be the Rx antenna of the UE.

| +| Applicable for | Sidelink | + +### 5.1.42 DL reference signal carrier phase (DL RSCP) + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

DL reference signal carrier phase (RSCP) is defined as the phase of the channel response at the 1st path delay derived from the resource elements carrying DL PRS configured for the measurement.

DL RSCP is associated with the center frequency of the DL positioning frequency layer (PFL) configured for the measurement for RRC_CONNECTED, RRC_INACTIVE, and RRC_IDLE modes.

For frequency range 1, the reference point for the DL RSCP shall be the antenna connector of the UE. For frequency range 2, the reference point for the DL RSCP shall be the antenna of the UE.

| +| Applicable for | RRC_CONNECTED,
RRC_INACTIVE,
RRC_IDLE | + +### 5.1.43 DL reference signal carrier phase difference (DL RSCPD) + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

DL reference signal carrier phase difference (RSCPD) is defined as the difference of DL RSCPs measured from DL PRS transmitted in a DL PFL from the transmission point (TP) j and the reference TP i. If UE reports RSCPD measurements together with RSTD measurements in a measurement report element, the reference TP for RSCPD is the same as the reference TP reported for RSTD.

For frequency range 1, the reference point for the DL RSCPD shall be the antenna connector of the UE. For frequency range 2, the reference point for the DL RSCPD shall be the antenna of the UE.

| +| Applicable for | RRC_CONNECTED,
RRC_INACTIVE,
RRC_IDLE | + +### 5.1.44 Sidelink PRS received signal strength indicator (SL PRS-RSSI) + +| | | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Sidelink PRS Received Signal Strength Indicator (SL PRS-RSSI) is defined as the linear average of the total received power (in [W]) observed in the SL-PRS resource and the associated PSCCH in OFDM symbols of slots configured for PSCCH and in OFDM symbols of slots configured for SL-PRS.

For frequency range 1, the reference point for the SL PRS-RSSI shall be the antenna connector of the UE. For frequency range 2, SL PRS-RSSI shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch. For frequency range 1 and 2, if receiver diversity is in use by the UE, the reported SL PRS-RSSI value shall not be lower than the corresponding SL PRS-RSSI of any of the individual receiver branches.

| +| Applicable for | Sidelink | + +### 5.1.45 Time domain channel property (TDCP) + +| | | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Time domain channel property (TDCP) is defined as wideband normalized correlation between two CSI-RS transmission occasions, corresponding to CSI-RS resource(s) from NZP-CSI-RS-ResourceSet(s) configured with higher layer parameter trs-info, that are separated by D_n symbols or slots, depending on the configuration, where D_n is the n-th delay configured value among [placeHolderForRrcParameter-D] configured delay values \{D_1, \dots, D_Y\} and Y is number of configured delay values.

The wideband normalized correlation value in TDCP is quantized in amplitude and if configured by [placeHolderForRrcParameter-phaseQuanOn], in phase, as described in Clause 5.2.1.4.5 of [6, TS38.214].

For frequency range 1 and 2, if receiver diversity is in use by the UE, the reported TDCP amplitude value shall be no lower than the minimum and no higher than the maximum measured values across the receiver branches.

For frequency range 1, the reference point for the TDCP shall be the antenna connector of the UE. For frequency range 2, TDCP shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch.

| +| Applicable for | RRC_CONNECTED | + +### 5.1.46 UE Rx – Tx time difference subframe offset + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

UE Rx – Tx time difference subframe offset is the index difference which represents the number of subframes between the uplink subframe \#j and the uplink subframe \#i, where uplink subframe \#j is the closest in time to the DL subframe \#i received from a transmission point (TP) [18] as defined in Clause 5.1.30 and i is the index of the DL subframe used for the UE Rx – Tx time difference measurement as defined in Clause 5.1.30.

For frequency range 1, the reference point for UE Rx – Tx time difference subframe offset measurement shall be the same antenna connectors as defined in Clause 5.1.30 for the UE Rx – Tx time difference measurement. For frequency range 2, the reference point UE Rx – Tx time difference subframe offset measurement shall be the same antenna as defined in Section 5.1.30 for the UE Rx – Tx time difference measurement.

| +| Applicable for | RRC_CONNECTED | + +### 5.1.47 DL timing drift + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

DL timing drift is defined as the variation rate of the downlink delay in ppm due to the service link Doppler over the UE Rx-Tx time difference measurement period.

For frequency range 1, the reference point for the DL timing drift measurement shall be the Rx antenna connector of the UE. For frequency range 2, the reference point for the DL timing drift measurement shall be the Rx antenna of the UE.

| +| Applicable for | RRC_CONNECTED | + +### 5.1.48 Sidelink PRS channel occupancy ratio (SL PRS-CR) + +| | | +|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Sidelink PRS Channel Occupancy Ratio (SL PRS-CR) evaluated at slot n is defined as the total number of SL PRS resource in the dedicated SL PRS resource pool used for its transmissions in slots [n-a, n-1] and granted in slots [n, n+b] divided by the total number of configured SL PRS resources in the transmission pool over [n-a, n+b].

| +| Applicable for | sidelink | + +NOTE 1: $a$ is a positive integer and $b$ is 0 or a positive integer; $a$ and $b$ are determined by UE implementation with $a+b+l = 1000$ or $1000 \cdot 2^\mu$ slots, according to higher layer parameter [*sl-TimeWindowSize-PRS-CR*], $b < (a+b+1)/2$ , and $n+b$ shall not exceed the last transmission opportunity of the grant for the current transmission. + +NOTE 2: SL PRS-CR is evaluated for each (re)transmission. + +NOTE 3: In evaluating SL PRS-CR, the UE shall assume the transmission parameter used at slot $n$ is reused according to the existing grant(s) in slot $[n+l, n+b]$ without dropping. + +NOTE 4: The slot index is based on physical slot index. + +NOTE 5: SL PRS-CR can be computed per priority level + +NOTE 6: A resource is considered granted if it is a member of a selected sidelink grant as defined in TS 38.321 [7]. + +### 5.1.49 Sidelink PRS channel busy ratio (SL PRS-CBR) + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | SL PRS Channel Busy Ratio (SL PRS-CBR) measured in slot $n$ is defined as the number of SL PRS resources in the dedicated SL PRS resource pool whose SL PRS RSSI measured by the UE exceed a (pre-)configured threshold provided by the higher layer parameter [ sl-ThreshS-PRS-RSSI-CBR ] sensed over a SL PRS-CBR measurement window $[n-a, n-1]$ , wherein $a$ is equal to 100 or $100 \cdot 2^\mu$ slots, according to higher layer parameter [ sl-TimeWindowSize-PRS-CBR-positioning ] divided by the total number of the configured SL PRS resources in the transmission pool over $[n-a, n-1]$ .
The calculation of SL PRS-CBR is limited within the slots for which the SL PRS-RSSI is measured. If the number of SL PRS-RSSI measurement slots within the SL PRS-CBR measurement window is below a (pre-)configured threshold, a (pre-)configured SL PRS-CBR value is used. | +| Applicable for | sidelink | + +NOTE 1: The slot index is based on physical slot index. + +## 5.2 NG-RAN measurement abilities + +The structure of the table defining a NG-RAN measurement quantity is shown below. + +| | | +|---------------------|---------------------------------------------| +| Column field | Comment | +| Definition | Contains the definition of the measurement. | + +### 5.2.1 SSS transmit power + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition | SSS transmit power is determined as the linear average over the power contributions (in [W]) of the resource elements that carry secondary synchronization signals within the secondary synchronization signal (SSS) bandwidth.

For downlink reference signal transmit power determination the secondary synchronization signal according TS 38.211 [4] can be used.

For frequency range 1, the reference point for the downlink reference signal power measurement shall be the transmit antenna connector. | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.2 UL Relative Time of Arrival (TUL-RTOA) + +| | | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The UL Relative Time of Arrival (TUL-RTOA) is the beginning of subframe i containing SRS received in Reception Point (RP) [18] j, relative to the RTOA Reference Time [16].

The UL RTOA reference time is defined as T_0 + t_{\text{SRS}}, where

  • - T_0 is the nominal beginning time of SFN 0 provided by SFN Initialization Time [15, TS 38.455]
  • - t_{\text{SRS}} = (10n_f + n_{\text{sf}}) \times 10^{-3}, where n_f and n_{\text{sf}} are the system frame number and the subframe number of the SRS, respectively.

Multiple SRS resources can be used to determine the beginning of one subframe containing SRS received at a RP.

The reference point for TUL-RTOA shall be:

  • - for type 1-C base station TS 38.104 [9]: the Rx antenna connector,
  • - for type 1-O or 2-O base station TS 38.104 [9]: the Rx antenna (i.e. the centre location of the radiating region of the Rx antenna),
  • - for type 1-H base station TS 38.104 [9]: the Rx Transceiver Array Boundary connector.
| +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.3 gNB Rx – Tx time difference + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

The gNB Rx – Tx time difference is defined as T_{\text{gNB-RX}} - T_{\text{gNB-TX}}

Where:

TgNB-RX is the Transmission and Reception Point (TRP) [18] received timing of uplink subframe #i containing SRS associated with UE, defined by the first detected path in time.

TgNB-TX is the TRP transmit timing of downlink subframe #j that is closest in time to the subframe #i received from the UE.

Multiple SRS resources can be used to determine the start of one subframe containing SRS.

The reference point for TgNB-RX shall be:

  • - for type 1-C base station TS 38.104 [9]: the Rx antenna connector,
  • - for type 1-O or 2-O base station TS 38.104 [9]: the Rx antenna (i.e. the centre location of the radiating region of the Rx antenna),
  • - for type 1-H base station TS 38.104 [9]: the Rx Transceiver Array Boundary connector.

The reference point for TgNB-TX shall be:

  • - for type 1-C base station TS 38.104 [9]: the Tx antenna connector,
  • - for type 1-O or 2-O base station TS 38.104 [9]: the Tx antenna (i.e. the centre location of the radiating region of the Tx antenna),
  • - for type 1-H base station TS 38.104 [9]: the Tx Transceiver Array Boundary connector.

In NTN, the gNB Rx – Tx time difference at the uplink time synchronization reference point [5] is reported.

| +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.4 UL Angle of Arrival (UL AoA) + +| | | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

UL Angle of Arrival (UL AoA) is defined as the estimated azimuth angle (A-AoA) and vertical angle (Z-AoA) of a UE with respect to a reference direction, wherein the reference direction is defined:

  • - In the global coordinate system (GCS), wherein estimated azimuth angle is measured relative to geographical North and is positive in a counter-clockwise direction and estimated vertical angle is measured relative to zenith and positive to horizontal direction
  • - In the local coordinate system (LCS), wherein estimated azimuth angle is measured relative to x-axis of LCS and positive in a counter-clockwise direction and estimated vertical angle is measured relative to z-axis of LCS and positive to x-y plane direction.

The bearing, downtilt and slant angles of LCS are defined according to TS 38.901 [15].

The UL-AoA is determined at the gNB antenna for an UL channel corresponding to this UE.

| +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.5 UL SRS reference signal received power (UL SRS-RSRP) + +| | | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

UL SRS reference signal received power (UL SRS-RSRP) is defined as linear average of the power contributions (in [W]) of the resource elements carrying sounding reference signals (SRS). UL SRS-RSRP shall be measured over the configured resource elements within the considered measurement frequency bandwidth in the configured measurement time occasions.

The reference point for UL SRS-RSRP shall be:

  • - for type 1-C base station TS 38.104 [9]: the Rx antenna connector,
  • - for type 1-O or 2-O base station TS 38.104 [9]: based on the combined signal from antenna elements corresponding to a given receiver branch,
  • - for type 1-H base station TS 38.104 [9]: the Rx Transceiver Array Boundary connector.

For frequency range 1 and 2, if receiver diversity is in use by the gNB, the reported UL SRS-RSRP value shall not be lower than the corresponding UL SRS-RSRP of any of the individual receiver branches.

| +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.6 UL SRS reference signal received path power (UL SRS-RSRPP) + +| | | +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

UL SRS reference signal received path power (UL SRS-RSRPP) is defined as the power of the linear average of the channel response at the i-th path delay of the resource elements that carry the received UL SRS signal configured for the measurement, where UL SRS-RSRPP for 1st path delay is the power contribution corresponding to the first detected path in time

The reference point for UL SRS-RSRPP shall be:

  • - for type 1-C base station TS 38.104 [9]: the Rx antenna connector,
  • - for type 1-O or 2-O base station TS 38.104 [9]: based on the combined signal from antenna elements corresponding to a given receiver branch
  • - for type 1-H base station TS 38.104 [9]: the Rx Transceiver Array Boundary connector.

For frequency range 1 and 2, if receiver diversity is in use by the gNB for UL SRS-RSRP measurements:

  • - The reported UL SRS-RSRPP value for the first and additional paths shall be provided for the same receiver branch(es) as applied for UL SRS-RSRP measurements, or
  • - The reported UL SRS-RSRPP value for the first path shall not be lower than the corresponding UL SRS-RSRP for the first path of any of the individual receiver branches and the reported UL SRS-RSRPP for the additional paths shall be provided for the same receiver branch(es) as applied UL SRS-RSRP for the first path.
| +|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.7 Timing advance ( $T_{ADV}$ ) + +| | | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

Timing advance (T_{ADV}) is defined as the time difference T_{ADV} = (T_{gNB-RX} - T_{gNB-TX}),

Where:
T_{gNB-RX} is the Transmission and Reception Point (TRP) [18] received timing of uplink subframe \#i containing PRACH transmitted from UE, defined by the first detected path in time.
T_{gNB-TX} is the TRP transmit timing of downlink subframe \#j that is closest in time to the subframe \#i received from the UE.

The detected PRACH is used to determine the start of one subframe containing that PRACH.

The reference point for T_{gNB-RX} shall be:

  • - for type 1-C base station TS 38.104 [9]: the Rx antenna connector,
  • - for type 1-O or 2-O base station TS 38.104 [9]: the Rx antenna (i.e. the centre location of the radiating region of the Rx antenna),
  • - for type 1-H base station TS 38.104 [9]: the Rx Transceiver Array Boundary connector.

The reference point for T_{gNB-TX} shall be:

  • - for type 1-C base station TS 38.104 [9]: the Tx antenna connector,
  • - for type 1-O or 2-O base station TS 38.104 [9]: the Tx antenna (i.e. the centre location of the radiating region of the Tx antenna),
  • - for type 1-H base station TS 38.104 [9]: the Tx Transceiver Array Boundary connector.
| +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 5.2.8 UL reference signal carrier phase (UL RSCP) + +| | | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Definition |

UL reference signal carrier phase (RSCP) is defined as the phase of the channel response at the 1st path delay derived from the resource elements carrying sounding reference signals (SRS) configured for the measurement.

UL RSCP is associated with the center frequency of the transmission bandwidth of the SRS for positioning purposes configured for the measurement.

The reference point for UL RSCP shall be:

  • - for type 1-C base station TS 38.104 [9]: the Rx antenna connector,
  • - for type 1-O or 2-O base station TS 38.104 [9]: the Rx antenna (i.e., the centre location of the radiating region of the Rx antenna),
  • - for type 1-H base station TS 38.104 [9]: the Rx Transceiver Array Boundary connector.
| +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +# --- Annex A: Change history + +| Change history | | | | | | | | | +|----------------|------------|------------|------|-----|-----|--------------------------------------------------------------------------------|-------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 2017-05 | RAN1#89 | R1-1709124 | | | | Draft skeleton | 0.0.0 | | +| 2017-07 | AH_NR2 | R1-1712017 | | | | Inclusion of agreements up to and including RAN1 NR Ad-Hoc #2 | 0.0.1 | | +| 2017-08 | RAN1#90 | R1-1714100 | | | | Updates according to email discussion "[NRAH2-03-215] TS 38.215 | 0.0.2 | | +| 2017-08 | RAN1#90 | R1-1714660 | | | | Clean version | 0.1.0 | | +| 2017-08 | RAN1#90 | R1-1715325 | | | | Inclusion of agreements from RAN1#90 | 0.1.1 | | +| 2017-08 | RAN1#90 | R1-1715333 | | | | Updates according to email discussion "[90-23-215] TS 38.215" | 0.1.2 | | +| 2017-09 | RAN#77 | RP-171999 | | | | For information to plenary | 1.0.0 | | +| 2017-09 | AH_NR3 | R1-1716931 | | | | Inclusion of agreements up to and including RAN1 NR Ad-Hoc #3 | 1.0.1 | | +| 2017-09 | RAN1#90bis | R1-1719108 | | | | Clean version | 1.1.0 | | +| 2017-11 | RAN1#90bis | R1-1719228 | | | | Inclusion of agreements up to and including RAN1#90bis | 1.1.1 | | +| 2017-11 | RAN1#90bis | R1-1719244 | | | | Updates according to email discussion "[90b-NR-01-38.215] " | 1.1.2 | | +| 2017-11 | RAN1#91 | R1-1721052 | | | | Clean version | 1.2.0 | | +| 2017-12 | RAN1#91 | R1-1721345 | | | | Inclusion of agreements up to and including RAN1#91 | 1.3.0 | | +| 2017-12 | RAN#78 | RP-172296 | | | | Endorsed version for approval by plenary | 2.0.0 | | +| 2017-12 | RAN#78 | | | | | Approved by plenary – Rel-15 spec under change control | 15.0.0 | | +| 2018-03 | RAN#79 | RP-180200 | 0002 | - | F | CR capturing the Jan18 ad-hoc and RAN1#92 meeting agreements | 15.1.0 | | +| 2018-06 | RAN#80 | RP-181172 | 0003 | 1 | F | CR to 38.215 capturing the RAN1#92bis and RAN1#93 meeting agreements | 15.2.0 | | +| 2018-09 | RAN#81 | RP-181789 | 0004 | - | F | CR to 38.215 capturing the RAN1#94 meetings agreements | 15.3.0 | | +| 2018-12 | RAN#82 | RP-182523 | 0005 | 3 | F | Combined CR of all essential corrections to 38.215 from RAN1#94bis and RAN1#95 | 15.4.0 | | +| 2019-06 | RAN#84 | RP-191278 | 0006 | - | F | CR on SFTD measurements for NE-DC | 15.5.0 | | +| 2019-06 | RAN#84 | RP-191278 | 0007 | - | F | Correction on SFTD measurement for NR-DC (Late drop) | 15.5.0 | | +| 2019-12 | RAN#86 | RP-192628 | 0010 | - | F | Correction of RSTD measurement for E-UTRA | 15.6.0 | | +| 2019-12 | RAN#86 | RP-192628 | 0012 | - | F | Corrections to SFTD measurement | 15.6.0 | | +| 2019-12 | RAN#86 | RP-192634 | 0008 | 1 | B | Introduction of cross layer interference measurements | 16.0.0 | | +| 2019-12 | RAN#86 | RP-192636 | 0013 | - | B | Introduction of NR-based access to unlicensed spectrum | 16.0.0 | | +| 2019-12 | RAN#86 | RP-192638 | 0014 | - | B | Introduction of V2X support | 16.0.0 | | +| 2019-12 | RAN#86 | RP-192641 | 0015 | - | B | Introduction of MIMO enhancements | 16.0.0 | | +| 2019-12 | RAN#86 | RP-192643 | 0016 | - | B | Introduction of NR positioning support | 16.0.0 | | +| 2020-01 | | | | | | MCC clean-up fixing font issue in clauses 5.2.2/5.2.3 and 5.2.4. | 16.0.1 | | +| 2020-03 | RAN#87-e | RP-200190 | 0017 | | F | Corrections to L1-SINR definitions | 16.1.0 | | +| 2020-03 | RAN#87-e | RP-200192 | 0018 | | F | Corrections to NR positioning support | 16.1.0 | | +| 2020-03 | RAN#87-e | RP-200183 | 0019 | | F | Corrections to cross layer interference measurements | 16.1.0 | | +| 2020-03 | RAN#87-e | RP-200187 | 0020 | | F | Corrections to V2X measurement definitions | 16.1.0 | | + +| | | | | | | | | +|---------|----------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2020-06 | RAN#88-e | RP-200707 | 0021 | 1 | B | Introduction of NR ATF measurements | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200683 | 0023 | - | A | Correction on SS-RSRPB measurement | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200692 | 0024 | - | F | Corrections to CSI-SINR definition | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200694 | 0025 | 1 | F | Correction to UL Relative Time of Arrival definition | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200687 | 0026 | - | F | Corrections to RSSI definition for NR-U | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200706 | 0027 | - | B | Introduction of UE UTRAN FDD measurements for SRVCC from NR to UMTS | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200689 | 0028 | - | F | Corrections to V2X measurement definitions | 16.2.0 | +| 2020-06 | RAN#88-e | RP-200694 | 0029 | - | F | Corrections to intra/inter-frequency measurement for NR positioning | 16.2.0 | +| 2020-09 | RAN#89-e | RP-201824 | 0030 | 1 | F | Correction of SS-RSARP definition | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201807 | 0031 | - | F | Corrections to V2X measurement definitions | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201809 | 0032 | - | F | Corrections to CSI-SINR definition | 16.3.0 | +| 2020-09 | RAN#89-e | RP-201811 | 0033 | - | F | Corrections to NR positioning measurement definitions | 16.3.0 | +| 2020-12 | RAN#90-e | RP-202398 | 0034 | - | F | Alignment of RRC parameter names | 16.4.0 | +| 2021-12 | RAN#94-e | RP-212967 | 0036 | - | B | Introduction of NR extensions to 71 GHz | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212970 | 0037 | - | B | Introduction of NR positioning enhancements | 17.0.0 | +| 2021-12 | RAN#94-e | RP-212968 | 0039 | - | B | Introduction of enhanced Industrial Internet of Things (IoT) and ultra-reliable and low latency communication (URLLC) support for NR | 17.0.0 | +| 2022-03 | RAN#95-e | RP-220862 | 0038 | 2 | B | Introduction of Timing advance (TA) PRACH based solution for NR UL E-CID [NRTADV] | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220273 | 0041 | - | A | CR on reference point for UL SRS-RSRP | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220254 | 0042 | - | F | Corrections to DL PRS-RSRPP and UL SRS-RSRPP measurement definitions | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220251 | 0043 | - | F | Corrections to SS-RSRQ and RSSI measurement definitions | 17.1.0 | +| 2022-03 | RAN#95-e | RP-220262 | 0044 | - | F | Corrections to SL CBR measurement definition | 17.1.0 | +| 2022-09 | RAN#97-e | RP-222404 | 0045 | - | F | CR on PRS RSRPP reporting for 38.215 | 17.2.0 | +| 2023-03 | RAN#99 | RP-230445 | 0047 | - | A | Alignment CR for AOA positioning in 38.215 | 17.3.0 | +| 2023-09 | RAN#101 | RP-232458 | 0048 | - | B | Introduction of MIMO evolution for Rel-18 for TS38.215 | 18.0.0 | +| 2023-09 | RAN#101 | RP-232480 | 0049 | - | B | Introduction of Rel-18 Positioning Enhancements for TS38.215 | 18.0.0 | +| 2023-09 | RAN#101 | RP-232474 | 0050 | - | B | Introduction of Rel-18 NR NTN enhancements for TS38.215 | 18.0.0 | +| 2023-12 | RAN#102 | RP-233723 | 0053 | - | A | Correction on SL RSSI measurement threshold related parameter name | 18.1.0 | +| 2023-12 | RAN#102 | RP-233723 | 0056 | - | A | Corrections to Applicable RRC States for Sidelink Measurements | 18.1.0 | +| 2023-12 | RAN#102 | RP-233723 | 0059 | - | A | CR on applicability of sidelink measurements | 18.1.0 | +| 2023-12 | RAN#102 | RP-233705 | 0060 | - | F | Correction of Rel-18 MIMO evolution | 18.1.0 | +| 2023-12 | RAN#102 | RP-233714 | 0061 | - | F | Correction of Rel-18 NR NTN enhancements | 18.1.0 | +| 2023-12 | RAN#102 | RP-233719 | 0062 | - | F | Correction of Rel-18 Positioning Enhancements | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38305/025f85981c69ed3274f1aa6c4844266e_img.jpg b/marked/Rel-18/38_series/38305/025f85981c69ed3274f1aa6c4844266e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..621b10024eaa0b2fbc54037a02b122c21fe9ba1c --- /dev/null +++ b/marked/Rel-18/38_series/38305/025f85981c69ed3274f1aa6c4844266e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4635e9f35fee1e86ca56bf7ee75d9aaf556bc126e6d25ca7ade07b7761538833 +size 15002 diff --git a/marked/Rel-18/38_series/38305/071619a7be79904674fb6b1963aa3b67_img.jpg b/marked/Rel-18/38_series/38305/071619a7be79904674fb6b1963aa3b67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ff0f2332ede91685277607ba2d0313285dc2ad4 --- /dev/null +++ b/marked/Rel-18/38_series/38305/071619a7be79904674fb6b1963aa3b67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb8f8df482820bb339881575502b88dfda2941818ed9b47501fa439d4eacc570 +size 56211 diff --git a/marked/Rel-18/38_series/38305/0d9b44054c70dcda35129f11b97a912f_img.jpg b/marked/Rel-18/38_series/38305/0d9b44054c70dcda35129f11b97a912f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3edde2c40ee3fbe3c975003b6663f3ba86cdf1bf --- /dev/null +++ b/marked/Rel-18/38_series/38305/0d9b44054c70dcda35129f11b97a912f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd58d3ecfa266542be284e40ea8f782288828b5cdc1e73b62cdbe292d719ed08 +size 14110 diff --git a/marked/Rel-18/38_series/38305/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/marked/Rel-18/38_series/38305/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..708ba2d4495d52a02b0ab663cc1ca69972fcd99f --- /dev/null +++ b/marked/Rel-18/38_series/38305/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f8cfe228e95e9ecc2d93d5492c9eda67e1091550495f5f1c08aa8940f044c4f +size 11558 diff --git a/marked/Rel-18/38_series/38305/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg b/marked/Rel-18/38_series/38305/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6968401ce6f2e85e518b0044ffa21e5b79b83cbc --- /dev/null +++ b/marked/Rel-18/38_series/38305/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9dac083de134257147b1002d4b88eb1911acb03cfb8f56fb1e9ba3e74bc4969 +size 15418 diff --git a/marked/Rel-18/38_series/38305/1fd763be1b7a05b52e554f0583617642_img.jpg b/marked/Rel-18/38_series/38305/1fd763be1b7a05b52e554f0583617642_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4142d6969b17e551155c45f6ffc3709a6fa6b70d --- /dev/null +++ b/marked/Rel-18/38_series/38305/1fd763be1b7a05b52e554f0583617642_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74060c00025753374c9cd44a791e082f14534308c55216582e53b2b90b91889f +size 29693 diff --git a/marked/Rel-18/38_series/38305/22c951be5955437ff27274172250e483_img.jpg b/marked/Rel-18/38_series/38305/22c951be5955437ff27274172250e483_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2d9ae7d35ea36a019a6d2a879fd377ce42e0043 --- /dev/null +++ b/marked/Rel-18/38_series/38305/22c951be5955437ff27274172250e483_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02d2d58bd9657f823d75d3bd1109a7c274d280f04ebc0de53125d5bad53953d2 +size 1294 diff --git a/marked/Rel-18/38_series/38305/245166735676c675f98f535bc4c6f0a1_img.jpg b/marked/Rel-18/38_series/38305/245166735676c675f98f535bc4c6f0a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad680db25ab20bea6da3d7137f3f53d4b58c6b77 --- /dev/null +++ b/marked/Rel-18/38_series/38305/245166735676c675f98f535bc4c6f0a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23a4350bdb22c0621e10c817876151f3073592117f9e39ea00220b4ae1c661b4 +size 15711 diff --git a/marked/Rel-18/38_series/38305/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-18/38_series/38305/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1bcf3787cb553225ef241c26edccf97533195d8 --- /dev/null +++ b/marked/Rel-18/38_series/38305/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45273c84d399ccbe62e929f11a136160f4549e3782a591a02752b4925d0cc7d0 +size 49798 diff --git a/marked/Rel-18/38_series/38305/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-18/38_series/38305/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8349740db4b125106ab48bb807015fe49f1694a5 --- /dev/null +++ b/marked/Rel-18/38_series/38305/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65ab38af57352eaea42d64ba60c03f2070662ab8a76b0413efa5a0364447ac3f +size 39773 diff --git a/marked/Rel-18/38_series/38305/35361e547fa02f04752bf841677e42b1_img.jpg b/marked/Rel-18/38_series/38305/35361e547fa02f04752bf841677e42b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00d57f51a67c6ab85dd8a6437ebeec39421a3452 --- /dev/null +++ b/marked/Rel-18/38_series/38305/35361e547fa02f04752bf841677e42b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f171ad9d0708ea3072a2d1f211ebdd208c0f5b669c92ad76234b5d683069167 +size 13977 diff --git a/marked/Rel-18/38_series/38305/427095219f3706148e8c03f1013eaec8_img.jpg b/marked/Rel-18/38_series/38305/427095219f3706148e8c03f1013eaec8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8e4e33d64bc36adbba1194a2b8fddb358ee90bc --- /dev/null +++ b/marked/Rel-18/38_series/38305/427095219f3706148e8c03f1013eaec8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1f88f63ee10b7b5b42252eccbe86568cdb6a8617a67c33cdee5f5abcb1b1cde +size 11625 diff --git a/marked/Rel-18/38_series/38305/4f7470055bfc22c4aa6b007a4056940e_img.jpg b/marked/Rel-18/38_series/38305/4f7470055bfc22c4aa6b007a4056940e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7591c123e7bd449aa58e745467679e87f7831c0 --- /dev/null +++ b/marked/Rel-18/38_series/38305/4f7470055bfc22c4aa6b007a4056940e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9040114505273a8d7ad05c7e9aefa954e649d2665896bd9c56daf91f15d8d27a +size 29693 diff --git a/marked/Rel-18/38_series/38305/52ee58fb61d595173f91db2bcbd18557_img.jpg b/marked/Rel-18/38_series/38305/52ee58fb61d595173f91db2bcbd18557_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92aa0d2979b0b5fbc0f6a9b9a726a7402170c490 --- /dev/null +++ b/marked/Rel-18/38_series/38305/52ee58fb61d595173f91db2bcbd18557_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b6cbbd8ad00a6f409e891adba59204e98512f765538f5d0c2112951373f596e +size 29982 diff --git a/marked/Rel-18/38_series/38305/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38305/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf46dbc2466a407ddc367e830127721e91457194 --- /dev/null +++ b/marked/Rel-18/38_series/38305/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8cd023d135e31d498c99115da1315add2a98ce6b7e45da6b30e7ccfca6914ce1 +size 6909 diff --git a/marked/Rel-18/38_series/38305/6aec120931a00f0d600bdb4a99d00bcc_img.jpg b/marked/Rel-18/38_series/38305/6aec120931a00f0d600bdb4a99d00bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..144d91e7b5f6e65f7b52ba7e714886d213da67d9 --- /dev/null +++ b/marked/Rel-18/38_series/38305/6aec120931a00f0d600bdb4a99d00bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24c526349a341387f27f63786722f43d7035c50166361e798916fb4a6021c3b6 +size 29098 diff --git a/marked/Rel-18/38_series/38305/6d442ab678ed52045444b3ccd4c0ac9e_img.jpg b/marked/Rel-18/38_series/38305/6d442ab678ed52045444b3ccd4c0ac9e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c4d1a1c24bd7e493fe451a04ac1ded761d4a731 --- /dev/null +++ b/marked/Rel-18/38_series/38305/6d442ab678ed52045444b3ccd4c0ac9e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a046d46007670bb05e6a99a61bb3d03e656616d1c7a90bd015ce4fd335f1755b +size 14999 diff --git a/marked/Rel-18/38_series/38305/7c57192c514175021e4560a1a46126c1_img.jpg b/marked/Rel-18/38_series/38305/7c57192c514175021e4560a1a46126c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7ba85d8047fabd8993af04d575316c93ae5fcc9 --- /dev/null +++ b/marked/Rel-18/38_series/38305/7c57192c514175021e4560a1a46126c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:028a23b8dc8f05855fc3cf94c11408999dad537baf5586e1653bf4c1f5cb8d42 +size 19198 diff --git a/marked/Rel-18/38_series/38305/822e033872d5ab16e861571f47b81ba7_img.jpg b/marked/Rel-18/38_series/38305/822e033872d5ab16e861571f47b81ba7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd5c090b8b4efaba939a30ccfa4b63c538096e2a --- /dev/null +++ b/marked/Rel-18/38_series/38305/822e033872d5ab16e861571f47b81ba7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a639a427d624deafb5698bbbe6b849260c436e818a4e83232b259112b8d6abec +size 56212 diff --git a/marked/Rel-18/38_series/38305/84db9bf6e93779b67aa320d1dfd38d91_img.jpg b/marked/Rel-18/38_series/38305/84db9bf6e93779b67aa320d1dfd38d91_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3842b5ad40838f25973763d3fc26ecef1611b95b --- /dev/null +++ b/marked/Rel-18/38_series/38305/84db9bf6e93779b67aa320d1dfd38d91_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e76c262e5229162b242d72d3eedd13145299fc192e6063f815e2bda4e7375ca +size 2272 diff --git a/marked/Rel-18/38_series/38305/92724c769da9d46b730fde1a6dccb023_img.jpg b/marked/Rel-18/38_series/38305/92724c769da9d46b730fde1a6dccb023_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e58b403bc1cacbaa05f38c07b9b627fc49430f3 --- /dev/null +++ b/marked/Rel-18/38_series/38305/92724c769da9d46b730fde1a6dccb023_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a98627f03034d7096a6fe7c7a473b1c66ea97d521e26609eec19d8371a1ccc5 +size 184519 diff --git a/marked/Rel-18/38_series/38305/96c8d8b0159c47a7478ada46d781060b_img.jpg b/marked/Rel-18/38_series/38305/96c8d8b0159c47a7478ada46d781060b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ed7015c7b79bc9821bf09200fb73f95785dda06 --- /dev/null +++ b/marked/Rel-18/38_series/38305/96c8d8b0159c47a7478ada46d781060b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dcce162cd22c14df6b9cf67ef882a77c05afdcc3ad3f106fca8cc5b93b283a89 +size 12347 diff --git a/marked/Rel-18/38_series/38305/9ba75f891de20483c291538e38701d96_img.jpg b/marked/Rel-18/38_series/38305/9ba75f891de20483c291538e38701d96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c0414d4756dfc6da453a6120922405740705216 --- /dev/null +++ b/marked/Rel-18/38_series/38305/9ba75f891de20483c291538e38701d96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93b01b362f1a782b7308165be0a7388a2f7c600bc3815cc1a186802de4d0aa8b +size 10765 diff --git a/marked/Rel-18/38_series/38305/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-18/38_series/38305/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7488f434f524416cb7509bbaf16a1bdde5683ae2 --- /dev/null +++ b/marked/Rel-18/38_series/38305/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69ebf4061833f0e5f10d1fcfcee0c05498d390185c8cca133c0fe828eb7a39c7 +size 35075 diff --git a/marked/Rel-18/38_series/38305/a1b35c85c93d7a2e30d1feea2faac2e6_img.jpg b/marked/Rel-18/38_series/38305/a1b35c85c93d7a2e30d1feea2faac2e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8fbfc0008befa8bef472727723b9a3af3afaab7 --- /dev/null +++ b/marked/Rel-18/38_series/38305/a1b35c85c93d7a2e30d1feea2faac2e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89ea555a899d7ae29111da246e6a425b584a47d47cd9327e70f5bbaa88e7e737 +size 10401 diff --git a/marked/Rel-18/38_series/38305/a1d3229d6f5d31aceed45f2a88917e4c_img.jpg b/marked/Rel-18/38_series/38305/a1d3229d6f5d31aceed45f2a88917e4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f507f1d94d544eacd92e311bb46619d9628dc26c --- /dev/null +++ b/marked/Rel-18/38_series/38305/a1d3229d6f5d31aceed45f2a88917e4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba7daaa82eca364b6f452fbe2aa7491a474aacc42d20d8f3edf687e5625c46a9 +size 24724 diff --git a/marked/Rel-18/38_series/38305/a626c4e5f38f8e361cd07c9f73405cc8_img.jpg b/marked/Rel-18/38_series/38305/a626c4e5f38f8e361cd07c9f73405cc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e393dd62c63be27f64575820e816c24d9fd686a8 --- /dev/null +++ b/marked/Rel-18/38_series/38305/a626c4e5f38f8e361cd07c9f73405cc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:933f2fb35bc941264e9d53b61763990b5379f56d6e226260af7c33c1b7e7f0a3 +size 36226 diff --git a/marked/Rel-18/38_series/38305/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg b/marked/Rel-18/38_series/38305/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9d313c2f483f279c67e1a0fde4ed35c81d666ea --- /dev/null +++ b/marked/Rel-18/38_series/38305/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90c50db3972a2113d2a9c2e4b93831e55d52e1d033a51aaa3a604dde74a6daf0 +size 24904 diff --git a/marked/Rel-18/38_series/38305/ae56c99bae77ca28d053b978909e1936_img.jpg b/marked/Rel-18/38_series/38305/ae56c99bae77ca28d053b978909e1936_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9babb69d639e587f3188b68fa93c5e69d89a57a7 --- /dev/null +++ b/marked/Rel-18/38_series/38305/ae56c99bae77ca28d053b978909e1936_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ad2b54f0b0c3d1d61f1f28e712071bceaef03bda35bc025b8f0261eb3270d0a +size 148105 diff --git a/marked/Rel-18/38_series/38305/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-18/38_series/38305/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15a42f4815e8ad335910ea1f8809005db99da28a --- /dev/null +++ b/marked/Rel-18/38_series/38305/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:808b39ca4fae08a1c94803f50ae123b9875e45a889371216a838e516e03d0eb3 +size 166215 diff --git a/marked/Rel-18/38_series/38305/c6e0b9030f9fb81435eaf9cb71532614_img.jpg b/marked/Rel-18/38_series/38305/c6e0b9030f9fb81435eaf9cb71532614_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4435e0b00fa65712ea577036df2346fcc756923 --- /dev/null +++ b/marked/Rel-18/38_series/38305/c6e0b9030f9fb81435eaf9cb71532614_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff901b6585d6590e62f3c1e22338e7cc0c693658dbe7a9fe05c576323a113425 +size 15742 diff --git a/marked/Rel-18/38_series/38305/c701a84b904fedcdb0316835eafbd39f_img.jpg b/marked/Rel-18/38_series/38305/c701a84b904fedcdb0316835eafbd39f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a587c7dc251cc0a2b978ab21a38b6d2e3cd87bc2 --- /dev/null +++ b/marked/Rel-18/38_series/38305/c701a84b904fedcdb0316835eafbd39f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5de5bf849be0a70aec46fb4cb07c27018a1ddb4954edafa947477be768eb15dc +size 10268 diff --git a/marked/Rel-18/38_series/38305/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-18/38_series/38305/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..084b93ebb44a4fdfc572f33860e3946afdb9a136 --- /dev/null +++ b/marked/Rel-18/38_series/38305/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7cdeb5906944ff2282021a5fc815780f65a120394761ab6fccbcc462b86d2aba +size 11831 diff --git a/marked/Rel-18/38_series/38305/d78e519e9186d30807342196675fd440_img.jpg b/marked/Rel-18/38_series/38305/d78e519e9186d30807342196675fd440_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00906eac3673e0a9bbecfa3a77adc95a322ad645 --- /dev/null +++ b/marked/Rel-18/38_series/38305/d78e519e9186d30807342196675fd440_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7172d4e7a13704a16e734e487d2c1cb276dd308827e571522ba9941f591cb2c6 +size 21648 diff --git a/marked/Rel-18/38_series/38305/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-18/38_series/38305/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6043fda609c0b56e961e013bbb3c8cd39bc7a21 --- /dev/null +++ b/marked/Rel-18/38_series/38305/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21ef08cb2792d74dfedec1df6c18fe403a343511c8d549c760a200c424f5d56d +size 19952 diff --git a/marked/Rel-18/38_series/38305/e01c6273c4177746475715ee9c17a882_img.jpg b/marked/Rel-18/38_series/38305/e01c6273c4177746475715ee9c17a882_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b3c4dac1bd507632f05b9e79ea6f581225d9456 --- /dev/null +++ b/marked/Rel-18/38_series/38305/e01c6273c4177746475715ee9c17a882_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea42887ae6317a1fedf2bc2bd6a884e8014422ced1233e39a0a1db17df4d7c28 +size 22809 diff --git a/marked/Rel-18/38_series/38305/e1570156ae4b4ddeb6913fc793678c94_img.jpg b/marked/Rel-18/38_series/38305/e1570156ae4b4ddeb6913fc793678c94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4588dba01c71d77d6c6c5fa2d1a88e28ef73885d --- /dev/null +++ b/marked/Rel-18/38_series/38305/e1570156ae4b4ddeb6913fc793678c94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d90325fa51e8a63ad3413927b08916785077b6e95e54569cc59b53b8ac28e38 +size 35691 diff --git a/marked/Rel-18/38_series/38305/e7378ff7bbd173cc8bd53a621907dc1d_img.jpg b/marked/Rel-18/38_series/38305/e7378ff7bbd173cc8bd53a621907dc1d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92b36741dbaf8acf3071a3a0f597ace2f5da8cc1 --- /dev/null +++ b/marked/Rel-18/38_series/38305/e7378ff7bbd173cc8bd53a621907dc1d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76dff1734a6af249b81487704217a4e873081e9062d07cfbdbb933fe47b529df +size 15975 diff --git a/marked/Rel-18/38_series/38305/ef3cc411849a8effc80adb5a6ad57b36_img.jpg b/marked/Rel-18/38_series/38305/ef3cc411849a8effc80adb5a6ad57b36_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..faa1e092fa4088288f39abd57b21a6ef892b1815 --- /dev/null +++ b/marked/Rel-18/38_series/38305/ef3cc411849a8effc80adb5a6ad57b36_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4a437737428ee9f37b4ebc034df09907e35a49d3d55d748a5095af7b23610a4 +size 11944 diff --git a/marked/Rel-18/38_series/38305/fae02fa1dac97fc5f19a7b85d20df290_img.jpg b/marked/Rel-18/38_series/38305/fae02fa1dac97fc5f19a7b85d20df290_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55a00e4cbf107451049cc926903db4719ae53cfe --- /dev/null +++ b/marked/Rel-18/38_series/38305/fae02fa1dac97fc5f19a7b85d20df290_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef25f1c34e49e56ad2628590f86020b4cb886d88bfdd059f8fbcdbdd11dca3d1 +size 12698 diff --git a/marked/Rel-18/38_series/38305/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg b/marked/Rel-18/38_series/38305/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6fc29e1fd88f5f95411eca3b91890ef0022146a --- /dev/null +++ b/marked/Rel-18/38_series/38305/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3482970003ddbc63949a882f7f1bf40f41296a236e6e977825210a3b2d9f3cd +size 88254 diff --git a/marked/Rel-18/38_series/38305/fe4f9338148fd891afbd3e301f9bad33_img.jpg b/marked/Rel-18/38_series/38305/fe4f9338148fd891afbd3e301f9bad33_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81966eb655ac3d81cc6a3c2f819a9e9ce222b3b9 --- /dev/null +++ b/marked/Rel-18/38_series/38305/fe4f9338148fd891afbd3e301f9bad33_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:595fd63f3e6a33563d23d0b0d1759e6c3e1257b23c257e18751a54ddfd14581f +size 19640 diff --git a/marked/Rel-18/38_series/38351/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg b/marked/Rel-18/38_series/38351/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c919e84845a6fd4f305930711be80a138283451 --- /dev/null +++ b/marked/Rel-18/38_series/38351/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d619fef60701516bdf728f79fb0d17c58a448450538c435e1e03bbcedf309fd0 +size 24245 diff --git a/marked/Rel-18/38_series/38351/18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg b/marked/Rel-18/38_series/38351/18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..974c9dbfd036a580537a032a427eebac454a0f69 --- /dev/null +++ b/marked/Rel-18/38_series/38351/18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:930844a157d429340f5d59952db18c15dc1622805b73d3857cd7ff94bb8a04ca +size 49838 diff --git a/marked/Rel-18/38_series/38351/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/Rel-18/38_series/38351/367926125450c2bc3f4bdca9d59a62ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d027ea7075b273470f01afc91373484faab2c10 --- /dev/null +++ b/marked/Rel-18/38_series/38351/367926125450c2bc3f4bdca9d59a62ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef0b81b8f99828ca66491909575cd23939a46fbd165ade0b46b9c34553ed9d28 +size 98081 diff --git a/marked/Rel-18/38_series/38351/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-18/38_series/38351/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7809c293ed79e800280230e08599e89b0173e27a --- /dev/null +++ b/marked/Rel-18/38_series/38351/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a89da6a7d77f9ac3abf03a0209f38d46a9c1c9423cd762f98ee9d93f54e72ac9 +size 89973 diff --git a/marked/Rel-18/38_series/38351/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38351/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80fee86f49bc2bf7a3bd48240d06144caa631abf --- /dev/null +++ b/marked/Rel-18/38_series/38351/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6c9e88b27f16f8be17bf15448c164f5ada04977c509c2e4fd23ca64ee91ff86 +size 8179 diff --git a/marked/Rel-18/38_series/38351/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38351/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9e992b724b645ac246f0d2fe0c0d44b6bc9602c --- /dev/null +++ b/marked/Rel-18/38_series/38351/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85ca448865f074eb876158f5b594be8ec022b023da6f7243c257c6907bfda997 +size 5353 diff --git a/marked/Rel-18/38_series/38351/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-18/38_series/38351/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54371ebfa650d2babf3ed1c19018b7f74cbce432 --- /dev/null +++ b/marked/Rel-18/38_series/38351/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea9214c65caa1173b24a96665f2cdbc4dc0f7d85a7a88f442fddc950ac70b04c +size 17914 diff --git a/marked/Rel-18/38_series/38351/a734898ce18e972938949637c32a34f4_img.jpg b/marked/Rel-18/38_series/38351/a734898ce18e972938949637c32a34f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f5a896a4818588090b6e6d50449b64926b043dc --- /dev/null +++ b/marked/Rel-18/38_series/38351/a734898ce18e972938949637c32a34f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:719a742ff8af502294b99fbb0342c98c2b5e37c1d79b4f7b71b65aa1bd444a5c +size 8273 diff --git a/marked/Rel-18/38_series/38351/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-18/38_series/38351/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f3b254f5a5b63167b3691b7fa44c1b74e967473 --- /dev/null +++ b/marked/Rel-18/38_series/38351/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:096935f033ec306c1a68f22daee2bfa5f1800232ff16003caaf23550d2da4201 +size 99680 diff --git a/marked/Rel-18/38_series/38351/raw.md b/marked/Rel-18/38_series/38351/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1fdb9f888798a1b57464c55aaf39a815ff185b96 --- /dev/null +++ b/marked/Rel-18/38_series/38351/raw.md @@ -0,0 +1,723 @@ + + +# 3GPP TS 38.351 V18.0.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Sidelink Relay Adaptation Protocol (SRAP) Specification (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5G" text is a green graphic element consisting of three curved lines of increasing height, resembling a signal strength indicator or a stylized wave. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top by a horizontal line. Below the "P" is a red graphic element consisting of three curved lines of increasing height, 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 + +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 of terms, symbols and abbreviations..... | 7 | +| 3.1 Terms..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 4 General ..... | 8 | +| 4.1 Introduction ..... | 8 | +| 4.2 SRAP architecture ..... | 8 | +| 4.2.1 General ..... | 8 | +| 4.2.2 SRAP entities..... | 8 | +| 4.3 Services ..... | 11 | +| 4.3.1 Services provided to upper layers..... | 11 | +| 4.3.2 Services expected from lower layers..... | 11 | +| 4.4 Functions ..... | 12 | +| 4.5 Configurations ..... | 12 | +| 5 Procedures..... | 12 | +| 5.1 SRAP entity handling..... | 12 | +| 5.1.1 SRAP entity establishment ..... | 12 | +| 5.1.2 SRAP entity release ..... | 12 | +| 5.2 DL Data transfer..... | 13 | +| 5.2.1 Receiving operation of U2N Relay UE..... | 13 | +| 5.2.2 Transmitting operation of U2N Relay UE..... | 13 | +| 5.2.2.1 Egress link determination ..... | 13 | +| 5.2.2.2 Egress RLC channel determination ..... | 13 | +| 5.2.3 Receiving operation of U2N Remote UE..... | 14 | +| 5.3 UL Data transfer..... | 14 | +| 5.3.1 Transmitting operation of U2N Remote UE ..... | 14 | +| 5.3.1.1 UE ID field and BEARER ID field determination ..... | 14 | +| 5.3.1.2 Egress RLC channel determination ..... | 15 | +| 5.3.2 Receiving operation of U2N Relay UE..... | 15 | +| 5.3.3 Transmitting operation of U2N Relay UE..... | 15 | +| 5.3.3.1 UE ID field and BEARER ID field determination ..... | 15 | +| 5.3.3.2 Egress RLC channel determination ..... | 16 | +| 5.3a U2U SL Data transfer..... | 16 | +| 5.3a.1 Transmitting operation of U2U Remote UE ..... | 16 | +| 5.3a.1.1 General..... | 16 | +| 5.3a.1.2 UE ID fields and BEARER ID field determination..... | 16 | +| 5.3a.1.3 Egress RLC channel determination ..... | 16 | +| 5.3a.2 Receiving operation of U2U Relay UE..... | 17 | +| 5.3a.3 Transmitting operation of U2U Relay UE..... | 17 | +| 5.3a.3.1 General..... | 17 | +| 5.3a.3.2 Egress link determination ..... | 17 | +| 5.3a.3.3 Egress RLC channel determination ..... | 17 | +| 5.3a.4 Receiving operation of U2U Remote UE..... | 17 | +| 5.4 Handling of unknown, unforeseen, and erroneous protocol data..... | 18 | +| 6 Protocol data units, formats, and parameters ..... | 18 | +| 6.1 Protocol data units ..... | 18 | +| 6.1.1 Data PDU..... | 18 | +| 6.2 Formats..... | 18 | +| 6.2.1 General ..... | 18 | +| 6.2.2 Data PDU..... | 18 | +| 6.3 Parameters ..... | 19 | + +6.3.1 General ........................................................................................................................................................ 19 + +6.3.2 UE ID........................................................................................................................................................... 19 + +6.3.3 BEARER ID ................................................................................................................................................ 20 + +6.3.4 Data.............................................................................................................................................................. 20 + +6.3.5 R ................................................................................................................................................................. 20 + +6.3.6 D/C ............................................................................................................................................................. 20 + +**Annex A (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 provides description of the Sidelink Relay Adaptation Protocol (SRAP). + +# --- 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 38.322: "NR Radio Link Control (RLC) protocol specification". +- [5] 3GPP TS 38.323: "NR; Packet Data Convergence Protocol (PDCP) specification". + +# --- 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]. + +**Egress RLC channel:** a RLC channel on which a packet is transmitted by a U2N Relay UE, a U2N Remote UE, a U2U Remote UE, a U2U Relay UE or a network node. + +**Egress link:** a radio link on which a packet is transmitted by a U2N Relay UE, a U2N Remote UE, a U2U Remote UE, a U2U Relay UE or a network node. + +**Ingress RLC channel:** a RLC channel on which a packet is received from a U2N Relay UE, a U2N Remote UE, a U2U Remote UE, a U2U Relay UE or a network node. + +**Ingress link:** a radio link on which a packet is received from a U2N Relay UE, a U2N Remote UE, a U2U Remote UE, a U2U Relay UE or a network node. + +**U2N Relay UE:** a UE that provides functionality to support connectivity to the network for U2N Remote UE(s). + +**U2N Remote UE:** a UE that communicates with the network via a U2N Relay UE. + +**U2U Relay UE:** a UE that provides functionality to support connectivity between two U2U Remote UEs. + +**U2U Remote UE:** a UE that communicates with other UE(s) via a U2U Relay UE. + +## 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]. + +| | | +|------|------------------------------------| +| SRAP | Sidelink Relay Adaptation Protocol | +| U2N | UE-to-Network | +| U2U | UE-to-UE | + +# 4 General + +## 4.1 Introduction + +The objective is to describe the SRAP architecture and the SRAP entities from a functional point of view. + +## 4.2 SRAP architecture + +### 4.2.1 General + +This clause describes a model of the SRAP, i.e., it does not specify or restrict implementations. + +### 4.2.2 SRAP entities + +Figure 4.2.2-1 represents one possible structure for the SRAP sublayer. The figure is based on the radio interface protocol architecture defined in TS 38.300 [2]. + +![Figure 4.2.2-1: SRAP structure overview. The diagram shows the SRAP sublayer structure. At the top, a box labeled 'SRAP entity' is shown. Above it, 'U2N Relay UE / U2N Remote UE / U2U Remote UE / U2U Relay UE' are listed. To the left of the SRAP entity is a 'C-SAP' interface. To the right is the 'SRAP Sublayer' label. Below the SRAP entity, there are 'SRAP-PDU' and 'RLC-SDU' labels. Below these, 'RLC channels' are indicated with arrows pointing to 'RLC UM-SAP' and 'RLC AM-SAP' interfaces. The bottom part is labeled 'RLC Sublayer'.](18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg) + +Figure 4.2.2-1: SRAP structure overview. The diagram shows the SRAP sublayer structure. At the top, a box labeled 'SRAP entity' is shown. Above it, 'U2N Relay UE / U2N Remote UE / U2U Remote UE / U2U Relay UE' are listed. To the left of the SRAP entity is a 'C-SAP' interface. To the right is the 'SRAP Sublayer' label. Below the SRAP entity, there are 'SRAP-PDU' and 'RLC-SDU' labels. Below these, 'RLC channels' are indicated with arrows pointing to 'RLC UM-SAP' and 'RLC AM-SAP' interfaces. The bottom part is labeled 'RLC Sublayer'. + +Figure 4.2.2-1: SRAP structure overview + +On the U2N Relay UE, the SRAP sublayer contains one SRAP entity at Uu interface and a separate collocated SRAP entity at the PC5 interface. On the U2N Remote UE, the SRAP sublayer contains only one SRAP entity at the PC5 interface. On the U2U Relay UE and U2U Remote UE, the SRAP sublayer contains only one SRAP entity at the PC5 interface. + +Each SRAP entity has a transmitting part and a receiving part. Across the PC5 interface in the U2N case, the transmitting part of the SRAP entity at the U2N Remote UE has a corresponding receiving part of an SRAP entity at the U2N Relay UE, and vice versa. Across the Uu interface, the transmitting part of the SRAP entity at the U2N Relay UE has a corresponding receiving part of an SRAP entity at the gNB, and vice versa. + +Across the PC5 interface in the U2U case, the transmitting part of the SRAP entity at the U2U Remote UE has a corresponding receiving part of an SRAP entity at the U2U Relay UE, and vice versa. + +Figure 4.2.2-2 and Figure 4.2.2-3 represents the functional view of the SRAP entity in U2N Relay case for the SRAP sublayer at PC5 interface and at Uu interface respectively. Figure 4.2.2-4 represents the functional view of the SRAP entity in U2U Relay case for the SRAP sublayer at PC5 interface. + +![Functional view of SRAP sublayer at PC5 interface in U2N Relay case. The diagram shows two main parts: 'Relay UE or Remote UE Transmitting part of SRAP sublayer' on the left and 'Remote UE or Relay UE Receiving part of SRAP sublayer' on the right, connected by a 'Radio Interface (PC5)'. The transmitting part takes data from the 'receiving part of Relay UE SRAP entity at Uu interface' and 'upper layers on Remote UE', processes it through 'Determine egress link', 'Remove SRAP header' (for SRB0), 'Determine UE ID and BEARER ID', 'Add SRAP header' (except SRB0), and finally 'Mapping to egress RLC channel' to send it over the 'Egress RLC Channel (PC5)'. The receiving part takes data from the 'Ingress RLC Channel (PC5)', removes the 'SRAP header' (except for SRB0), and then sends it 'To upper layers on Remote UE' and 'To transmitting part of Relay UE SRAP entity at Uu interface'.](367926125450c2bc3f4bdca9d59a62ba_img.jpg) + +Detailed Diagram Description: The diagram is divided into two vertical halves by a central line. +Left side: 'Relay UE or Remote UE Transmitting part of SRAP sublayer'. It has two inputs from the top: 'From receiving part of Relay UE SRAP entity at Uu interface' and 'From upper layers on Remote UE'. The first input goes to 'Determine egress link'. From there, SRB0 traffic goes to 'Remove SRAP header' while 'Except SRB0' traffic bypasses it. The second input goes to 'Determine UE ID and BEARER ID'. SRB0 traffic from this block bypasses 'Add SRAP header', while 'Except SRB0' traffic goes through 'Add SRAP header'. All paths converge at 'Mapping to egress RLC channel', which outputs to 'Egress RLC Channel (PC5)'. +Right side: 'Remote UE or Relay UE Receiving part of SRAP sublayer'. It receives input from 'Ingress RLC Channel (PC5)'. The data splits: SRB0 traffic bypasses 'Remove SRAP header', while 'Except SRB0' traffic goes through 'Remove SRAP header'. The outputs go to 'To upper layers on Remote UE' and 'To transmitting part of Relay UE SRAP entity at Uu interface'. +Bottom: Both sides are connected via a horizontal bar labeled 'Radio Interface (PC5)'. + +Functional view of SRAP sublayer at PC5 interface in U2N Relay case. The diagram shows two main parts: 'Relay UE or Remote UE Transmitting part of SRAP sublayer' on the left and 'Remote UE or Relay UE Receiving part of SRAP sublayer' on the right, connected by a 'Radio Interface (PC5)'. The transmitting part takes data from the 'receiving part of Relay UE SRAP entity at Uu interface' and 'upper layers on Remote UE', processes it through 'Determine egress link', 'Remove SRAP header' (for SRB0), 'Determine UE ID and BEARER ID', 'Add SRAP header' (except SRB0), and finally 'Mapping to egress RLC channel' to send it over the 'Egress RLC Channel (PC5)'. The receiving part takes data from the 'Ingress RLC Channel (PC5)', removes the 'SRAP header' (except for SRB0), and then sends it 'To upper layers on Remote UE' and 'To transmitting part of Relay UE SRAP entity at Uu interface'. + +**Figure 4.2.2-2: Example of functional view of SRAP sublayer at PC5 interface in U2N Relay case** + +![Figure 4.2.2-3: Example of functional view of SRAP sublayer at Uu interface. The diagram shows two main parts: the Transmitting part and the Receiving part of the SRAP sublayer at the Uu interface, connected by a Radio Interface (Uu).](e6df2733626a85205c1db682e6259c46_img.jpg) + +The diagram illustrates the functional view of the SRAP sublayer at the Uu interface, divided into Transmitting and Receiving parts. + +**NG-RAN or Relay UE Transmitting part of SRAP sublayer:** + +- Inputs: From receiving part of Relay UE SRAP entity at PC5 interface (SRB0) and From upper layers on NG-RAN. +- Processing: + - SRB0 path: Determine UE ID and BEARER ID for SL-RLC0 → Add SRAP header for SL-RLC0 → Mapping to egress RLC channel. + - Other paths: Determine UE ID and BEARER ID → Add SRAP header. + - Note: Except SRB0, the paths merge before the Add SRAP header block. +- Output: Egress RLC Channel (Uu). + +**Radio Interface (Uu):** The central interface connecting the transmitting and receiving parts. + +**NG-RAN or Relay UE Receiving part of SRAP sublayer:** + +- Input: Ingress RLC Channel (Uu). +- Processing: Remove SRAP header. +- Outputs: To upper layers on NG-RAN and To transmitting part of Relay UE SRAP entity at PC5 interface. + +Figure 4.2.2-3: Example of functional view of SRAP sublayer at Uu interface. The diagram shows two main parts: the Transmitting part and the Receiving part of the SRAP sublayer at the Uu interface, connected by a Radio Interface (Uu). + +**Figure 4.2.2-3: Example of functional view of SRAP sublayer at Uu interface** + +In the example of Figure 4.2.2-2 and Figure 4.2.2-3, at relay UE: + +- For data packet not corresponding to SRB0, the receiving part on the SRAP entity of Uu interface delivers SRAP Data PDUs to the transmitting part on the collocated SRAP entity of PC5 interface, and the receiving part on the SRAP entity of PC5 interface delivers SRAP Data PDUs to the transmitting part on the collocated SRAP entity of Uu interface. As an alternative, the receiving part may deliver SRAP SDUs to the transmitting part on the collocated SRAP entity. When passing SRAP SDUs, the receiving part removes the SRAP header and the transmitting part of the relay UE adds the SRAP header with the same SRAP header content as carried on the SRAP Data PDU header prior to removal. Passing SRAP SDUs in this manner is therefore functionally equivalent to passing SRAP Data PDUs, in implementation. The following specification therefore refers to the passing of SRAP data packets. +- For UL data packet corresponding to SRB0, the receiving part on the SRAP entity of PC5 interface delivers SRAP SDUs to the transmitting part on the collocated SRAP entity of Uu interface, and the transmitting part on the SRAP entity of Uu interface adds the SRAP header in accordance with clause 5.3.3. +- For DL data packet corresponding to SRB0, the receiving part on the SRAP entity of Uu interface delivers SRAP Data PDUs to the transmitting part on the collocated SRAP entity of PC5 interface, and the transmitting part on the SRAP entity of PC5 interface removes the SRAP header in accordance with clause 5.2.2. As an alternative for handling DL data packet corresponding to SRB0 not shown in Figure 4.2.2-2 or Figure 4.2.2-3, the receiving part on the SRAP entity of Uu interface removes the SRAP header and delivers SRAP SDUs to the transmitting part on the collocated SRAP entity of PC5 interface. + +![Figure 4.2.2-4: Example of functional view of SRAP sublayer at PC5 interface in U2U Relay case. The diagram shows two main parts: the Transmitting part and the Receiving part of the SRAP sublayer, separated by a vertical line. The Transmitting part (left) receives data from the receiving part of the U2U Relay UE SRAP entity at the PC5 interface and from upper layers on the U2U Remote UE. It processes this data through 'Determine egress link', 'Determine UE ID and BEARER ID', 'Add SRAP header', and 'Mapping to egress RLC channel' before sending it to the Egress RLC Channel (PC5). The Receiving part (right) receives data from the Ingress RLC Channel (PC5), processes it through 'Remove SRAP header', and then sends it to the upper layers on the U2U Remote UE and to the transmitting part of the U2U Relay UE SRAP entity at the PC5 interface. Both parts are connected to a central 'Radio Interface (PC5)' block at the bottom.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +Figure 4.2.2-4: Example of functional view of SRAP sublayer at PC5 interface in U2U Relay case. The diagram shows two main parts: the Transmitting part and the Receiving part of the SRAP sublayer, separated by a vertical line. The Transmitting part (left) receives data from the receiving part of the U2U Relay UE SRAP entity at the PC5 interface and from upper layers on the U2U Remote UE. It processes this data through 'Determine egress link', 'Determine UE ID and BEARER ID', 'Add SRAP header', and 'Mapping to egress RLC channel' before sending it to the Egress RLC Channel (PC5). The Receiving part (right) receives data from the Ingress RLC Channel (PC5), processes it through 'Remove SRAP header', and then sends it to the upper layers on the U2U Remote UE and to the transmitting part of the U2U Relay UE SRAP entity at the PC5 interface. Both parts are connected to a central 'Radio Interface (PC5)' block at the bottom. + +**Figure 4.2.2-4: Example of functional view of SRAP sublayer at PC5 interface in U2U Relay case** + +In the example of Figure 4.2.2-4, at U2U relay UE: + +- For U2U data packet, the receiving part on the SRAP entity of PC5 interface between the U2U Relay UE and the U2U Remote UE delivers U2U SRAP Data PDUs to the transmitting part on the SRAP entity of PC5 interface between the U2U Relay UE and the peer U2U Remote UE. As an alternative, the receiving part may deliver SRAP SDUs to the transmitting part on the SRAP entity. When passing SRAP SDUs, the receiving part removes the SRAP header and the transmitting part of the relay UE adds the SRAP header with the same SRAP header content as carried on the U2U SRAP Data PDU header prior to removal. Passing SRAP SDUs in this manner is therefore functionally equivalent to passing U2U SRAP Data PDUs, in implementation. The following specification therefore refers to the passing of SRAP data packets. + +## 4.3 Services + +### 4.3.1 Services provided to upper layers + +The following services are provided by the SRAP sublayer to upper layers: + +- Data transfer. + +### 4.3.2 Services expected from lower layers + +An SRAP sublayer expects the following services from lower layers per RLC entity (for a detailed description see TS 38.322 [4]): + +- Acknowledged data transfer service; + +- Unacknowledged data transfer service. + +## 4.4 Functions + +The SRAP sublayer supports the following functions: + +- Data transfer; +- Determination of UE ID field and BEARER ID field for data packets; +- Determination of egress link; +- Determination of egress RLC channel. + +## 4.5 Configurations + +The configuration of the SRAP entity for U2N Remote UE includes: + +- Mapping from a radio bearer identified by BEARER ID field to egress PC5 Relay RLC channel via RRC; +- The local identity via RRC. + +The configuration of the SRAP entity for U2N Relay UE includes: + +- The local identity for each U2N Remote UE via RRC; +- Mapping from a radio bearer identified by UE ID field and BEARER ID field to egress Uu Relay RLC channel for each U2N Remote UE via RRC; +- Mapping from a radio bearer identified by UE ID field and BEARER ID field to egress PC5 Relay RLC channel for each U2N Remote UE via RRC. + +The configuration of the SRAP entity for U2U Remote UE includes: + +- Mapping from a sidelink radio bearer identified by BEARER ID field to egress PC5 Relay RLC channel for each U2U Remote UE pair; +- The local identities. + +The configuration of the SRAP entity for U2U Relay UE includes: + +- Mapping from a sidelink radio bearer identified by BEARER ID field to egress PC5 Relay RLC channel for each U2U Remote UE pair and each direction of data transfer. + +# --- 5 Procedures + +## 5.1 SRAP entity handling + +### 5.1.1 SRAP entity establishment + +When upper layers request establishment of an SRAP entity, UE shall: + +- establish an SRAP entity; +- follow the procedures in clause 5. + +### 5.1.2 SRAP entity release + +When upper layers request release of an SRAP entity, UE shall: + +- release the SRAP entity and the related SRAP configurations. + +## 5.2 DL Data transfer + +### 5.2.1 Receiving operation of U2N Relay UE + +Upon receiving an SRAP Data PDU from lower layer, the receiving part of the SRAP entity on the Uu interface of U2N Relay UE shall: + +- deliver the SRAP data packet to the transmitting part of the collocated SRAP entity on the PC5 interface. + +### 5.2.2 Transmitting operation of U2N Relay UE + +The transmitting part of the SRAP entity on the PC5 interface of U2N Relay UE receives SRAP data packets from the receiving part of the SRAP entity on the Uu interface of the same U2N Relay UE, and construct SRAP Data PDUs as needed (see clause 4.2.2). + +When the transmitting part of the SRAP entity on the PC5 interface has an SRAP Data PDU to transmit, the transmitting part of the SRAP entity on the PC5 interface shall: + +- Determine the egress link in accordance with clause 5.2.2.1; +- Determine the egress RLC channel in accordance with clause 5.2.2.2; +- if the SRAP Data PDU is for SRB0 (the BEARER ID field is 0, and the bearer is identified as SRB based on *sl-RemoteUE-RB-Identity* associated with the entry containing the *sl-EgressRLC-ChannelUu* which matches the LCID of the Uu Relay RLC Channel from which the SRAP Data PDU is received): + - Remove the SRAP header from the SRAP Data PDU; +- Submit this SRAP Data PDU to the determined egress RLC channel of the determined egress link. + +#### 5.2.2.1 Egress link determination + +For a SRAP Data PDU to be transmitted, SRAP entity shall: + +- if there is an entry in *sl-RemoteUE-ToAddModList*, whose *sl-LocalIdentity* included in *sl-SRAP-ConfigRelay* matches the UE ID field in SRAP Data PDU: + - Determine the egress link on PC5 interface corresponding to *sl-L2IdentityRemote* configured for the concerned *sl-LocalIdentity* as specified in TS 38.331 [3]. + +#### 5.2.2.2 Egress RLC channel determination + +For a SRAP Data PDU to be transmitted, the SRAP entity shall: + +- if the SRAP Data PDU is for SRB0 (the BEARER ID field is 0 and the bearer is identified as SRB based on *sl-RemoteUE-RB-Identity* associated with the entry containing the *sl-EgressRLC-ChannelUu* which matches the LCID of the Uu Relay RLC Channel from which the SRAP Data PDU is received): + - Determine the egress PC5 Relay RLC channel in the determined egress link corresponding to *logicalChannelIdentity* for SL-RLC0 as specified in TS 38.331 [3]. +- else if there is an entry in *sl-RemoteUE-ToAddModList*, whose *sl-LocalIdentity* included in *sl-SRAP-ConfigRelay* matches the UE ID field in SRAP Data PDU, which includes an *sl-RemoteUE-RB-Identity* that matches the SRB identity or DRB identity of the SRAP Data PDU determined by the BEARER ID field (For the BEARER ID shared by both SRB and DRB, SRB and DRB are differentiated based on *sl-RemoteUE-RB-Identity* associated with the entry containing the *sl-EgressRLC-ChannelUu* which matches the LCID of the Uu Relay RLC Channel from which the SRAP Data PDU is received, and for DRB, the DRB identity is BEARER ID plus 1): + - if the SRAP Data PDU is for SRB1 but the corresponding *sl-EgressRLC-ChannelPC5* is absent in *sl-SRAP-ConfigRelay*: + - Remove the SRAP header from the SRAP Data PDU; + +- Determine the egress PC5 Relay RLC channel in the determined egress link corresponding to *logicalChannelIdentity* for SL-RLC1 as specified in TS 38.331 [3]. +- else: + - Determine the egress PC5 Relay RLC channel in the determined egress link corresponding to *sl-EgressRLC-ChannelPC5* configured for the concerned *sl-LocalIdentity* and concerned *sl-RemoteUE-RB-Identity* as specified in TS 38.331 [3]. + +### 5.2.3 Receiving operation of U2N Remote UE + +Upon receiving an SRAP Data PDU from lower layer, the receiving part of the SRAP entity shall: + +- if the SRAP Data PDU is not for SRB0 (not received from SL-RLC0 as specified in TS 38.331 [3]): + - if the SRAP Data PDU is received from SL-RLC1 as specified in TS 38.331 [3]: + - remove the SRAP header of this SRAP Data PDU and deliver the SRAP SDU to PDCP entity of SRB1 by ignoring the UE ID field and BEARER ID field of this SRAP Data PDU; + - else: + - remove the SRAP header of this SRAP Data PDU and deliver the SRAP SDU to upper layer entity corresponding to the BEARER ID field of this SRAP Data PDU (For the BEARER ID shared by both SRB and DRB, SRB and DRB are differentiated based on *sl-RemoteUE-RB-Identity* associated with the entry containing the *sl-EgressRLC-ChannelPC5* which matches LCID of the PC5 Relay RLC Channel from which the SRAP Data PDU is received, and for DRB, the DRB identity is BEARER ID plus 1); +- else: + - deliver the SRAP SDU (i.e., same as SRAP PDU for SRB0) to upper layer, i.e., RRC layer entity (TS 38.331 [3]). + +## 5.3 UL Data transfer + +### 5.3.1 Transmitting operation of U2N Remote UE + +The transmitting part of the SRAP entity on the PC5 interface of U2N Remote UE can receive SRAP SDU from upper layer and constructs SRAP Data PDU. + +Upon receiving an SRAP SDU from upper layer, the transmitting part of the SRAP entity on the PC5 interface shall: + +- if the SRAP SDU is not for SRB0: + - Determine the UE ID field and BEARER ID field in accordance with clause 5.3.1.1; + - Construct an SRAP Data PDU with SRAP header, where the UE ID field and BEARER ID field are set to the determined values, in accordance with clause 6.2.2; +- else: + - Construct an SRAP Data PDU without SRAP header in accordance with clause 6.2.2. +- Determine the egress RLC channel in accordance with clause 5.3.1.2; +- Submit this SRAP Data PDU to the determined egress RLC channel. + +#### 5.3.1.1 UE ID field and BEARER ID field determination + +For an SRAP SDU received from upper layer, the SRAP entity shall: + +- Determine the UE ID field corresponding to *sl-LocalIdentity*, configured as specified in TS 38.331 [3]; + +- Determine the BEARER ID field corresponding to SRB identity for SRB (i.e., set the BEARER ID field to *srb-Identity*), or corresponding to DRB identity minus 1 for DRB (i.e., set the BEARER ID field to *drb-Identity* minus 1), from which the SRAP SDU is received, configured as specified in TS 38.331 [3]. + +#### 5.3.1.2 Egress RLC channel determination + +For a SRAP Data PDU to be transmitted, the SRAP entity shall: + +- if the SRAP Data PDU is for SRB0: + - Determine the egress PC5 Relay RLC channel in the link with U2N Relay UE corresponding to *logicalChannelIdentity* for SL-RLC0 as specified in TS 38.331 [3]. +- else if the SRAP Data PDU is for SRB1 and if there is not an entry in *sl-MappingToAddModList*, whose *sl-RemoteUE-RB-Identity* matches the SRB identity of the SRAP Data PDU, or if there is an entry in *sl-MappingToAddModList* without the corresponding *sl-EgressRLC-ChannelPC5*: + - Determine the egress PC5 Relay RLC channel in the link with U2N Relay UE corresponding to *logicalChannelIdentity* for SL-RLC1 as specified in TS 38.331 [3]. +- else if there is an entry in *sl-MappingToAddModList*, whose *sl-RemoteUE-RB-Identity* matches the SRB identity or DRB identity of the SRAP Data PDU: + - Determine the egress PC5 Relay RLC channel of the link with U2N Relay UE corresponding to *sl-EgressRLC-ChannelPC5* configured for the concerned *sl-RemoteUE-RB-Identity* as specified in TS 38.331 [3]. + +### 5.3.2 Receiving operation of U2N Relay UE + +Upon receiving an SRAP Data PDU from lower layer, the receiving part of the SRAP entity on the PC5 interface shall: + +- deliver the SRAP data packet to the transmitting part of the collocated SRAP entity on the Uu interface. + +### 5.3.3 Transmitting operation of U2N Relay UE + +The transmitting part of the SRAP entity on the Uu interface of U2N Relay UE can receive SRAP data packets from the receiving part of the SRAP entity on the PC5 interface of the same U2N Relay UE, and construct SRAP Data PDUs as needed (see clause 4.2.2). + +When the transmitting part of the SRAP entity on the Uu interface has an SRAP Data PDU to transmit, the transmitting part of the SRAP entity on the Uu interface shall: + +- if the SRAP Data PDU is received from SL-RLC0 as specified in TS 38.331 [3]: + - Determine the UE ID field and BEARER ID field in accordance with clause 5.3.3.1; + - Construct an SRAP Data PDU with SRAP header, where the UE ID field and BEARER ID field are set to the determined values, in accordance with clause 6.2.2; +- Determine the egress RLC channel in accordance with clause 5.3.3.2; +- Submit this SRAP Data PDU to the determined egress RLC channel. + +#### 5.3.3.1 UE ID field and BEARER ID field determination + +For an SRAP Data PDU received from SL-RLC0 as specified in TS 38.331 [3], the SRAP entity shall: + +- if there is an entry in *sl-RemoteUE-ToAddModList*, whose *sl-L2IdentityRemote* matches the Layer-2 ID of the remote UE from which the SRAP Data PDU is received: + - Determine the UE ID field corresponding to *sl-LocalIdentity* configured for the concerned *sl-L2IdentityRemote* as specified in TS 38.331 [3]; + - Determine the BEARER ID field as 0 (i.e., set BEARER ID field as 0). + +#### 5.3.3.2 Egress RLC channel determination + +For a SRAP Data PDU to be transmitted, the SRAP entity shall: + +- if there is an entry in *sl-RemoteUE-ToAddModList*, whose *sl-LocalIdentity* included in *sl-SRAP-ConfigRelay* matches the UE ID field in SRAP Data PDU: + - if the SRAP Data PDU is for SRB0: + - Determine the egress Uu Relay RLC channel corresponding to *sl-EgressRLC-ChannelUu* configured for SRB0 for the concerned *sl-LocalIdentity* as specified in TS 38.331 [3]. + - else if the SRAP Data PDU is received from SL-RLC1 as specified in TS 38.331 [3]: + - Determine the egress Uu Relay RLC channel corresponding to *sl-EgressRLC-ChannelUu* configured for SRB1 for the concerned *sl-LocalIdentity* as specified in TS 38.331 [3]. +- else if there is an entry in *sl-RemoteUE-ToAddModList* which includes an *sl-RemoteUE-RB-Identity* matches SRB identity or DRB identity of the SRAP Data PDU determined by the BEARER ID field (For the BEARER ID shared by both SRB and DRB, SRB and DRB are differentiated based on *sl-RemoteUE-RB-Identity* associated with the entry containing the *sl-EgressRLC-ChannelPC5* which matches LCID of the PC5 Relay RLC Channel from which the SRAP Data PDU is received, and for DRB, the DRB identity is BEARER ID plus 1): + - Determine the egress Uu Relay RLC channel corresponding to *sl-EgressRLC-ChannelUu* configured for the concerned *sl-LocalIdentity* and concerned *sl-RemoteUE-RB-Identity* as specified in TS 38.331 [3]. + +## 5.3a U2U SL Data transfer + +### 5.3a.1 Transmitting operation of U2U Remote UE + +#### 5.3a.1.1 General + +The transmitting part of the SRAP entity on the PC5 interface of U2U Remote UE can receive SRAP SDU from upper layer and constructs U2U SRAP Data PDU. + +Upon receiving an SRAP SDU from upper layer, the transmitting part of the SRAP entity on the PC5 interface shall: + +- Determine the UE ID fields and BEARER ID field in accordance with clause 5.3a.1.2; +- Construct an U2U SRAP Data PDU with SRAP header, where the UE ID fields and BEARER ID field are set to the determined values, in accordance with clause 6.2.2; +- Determine the egress RLC channel in accordance with clause 5.3a.1.3; +- Submit this U2U SRAP Data PDU to the determined egress PC5 Relay RLC channel. + +#### 5.3a.1.2 UE ID fields and BEARER ID field determination + +For an U2U SRAP SDU received from upper layer, the SRAP entity shall: + +- Determine the UE ID (for SRC) field corresponding to *sl-RemoteUE-LocalIdentity* and UE ID (for DST) field corresponding to *sl-PeerRemoteUE-LocalIdentity*, configured as specified in TS 38.331 [3]; +- Determine the BEARER ID field for SL-SRBs as the fixed value (i.e., set 0/1/2/3 for SL-SRB0/1/2/3 respectively) or for SL-DRBs as the 5 LSBs of *slrb-PC5-ConfigIndex* used in end-to-end SL DRB configuration procedure as specified in TS 38.331 [3]. + +#### 5.3a.1.3 Egress RLC channel determination + +For a U2U SRAP Data PDU to be transmitted, the SRAP entity shall: + +- If the U2U SRAP Data PDU is for SRB (i.e., the BEARER ID field is 0/1/2/3): + +- Determine the egress PC5 Relay RLC channel in the determined egress link corresponding to *logicalChannelIdentity* for SL-U2U-RLC as specified in TS 38.331 [3]. +- Else if the SRAP Data is for DRB: + - Determine the egress PC5 Relay RLC channel in the determined egress link corresponding to RLC channel ID configured for the concerned bearer as specified in TS 38.331 [3]. + +### 5.3a.2 Receiving operation of U2U Relay UE + +Upon receiving an U2U SRAP Data PDU from lower layer, the receiving part of the SRAP entity on the PC5 interface between the U2U Relay UE and the U2U Remote UE shall: + +- deliver the SRAP data packet to the transmitting part of the SRAP entity on the PC5 interface between the U2U Relay UE and the peer U2U Remote UE. + +### 5.3a.3 Transmitting operation of U2U Relay UE + +#### 5.3a.3.1 General + +The transmitting part of the SRAP entity of U2U Relay UE on the PC5 interface between the U2U Relay UE and the peer U2U Remote UE can receive SRAP data packets from the receiving part of the SRAP entity of the same U2U Relay UE on the PC5 interface between the U2U Relay UE and the U2U Remote UE, and constructs U2U SRAP Data PDUs as needed (see clause 4.2.2). + +When the transmitting part of the SRAP entity of the U2U Relay UE has an U2U SRAP Data PDU to transmit on the PC5 interface between U2U Relay UE and the peer U2U Remote UE, the transmitting part of the SRAP entity of U2U Relay UE shall: + +- Determine the egress link in accordance with clause 5.3a.3.2; +- Determine the egress RLC channel in accordance with clause 5.3a.3.3; +- Submit this U2U SRAP Data PDU to the determined egress RLC channel of the determined egress link. + +#### 5.3a.3.2 Egress link determination + +For a U2U SRAP Data PDU to be transmitted, SRAP entity shall: + +- Determine the egress link on PC5 interface towards the peer U2U remote UE based on the UE ID fields in the U2U SRAP Data PDU. + +#### 5.3a.3.3 Egress RLC channel determination + +For a U2U SRAP Data PDU to be transmitted, the SRAP entity shall: + +- If the U2U SRAP Data PDU is for SRB (i.e., the BEARER ID field is 0/1/2/3): + - Determine the egress PC5 Relay RLC channel in the determined egress link corresponding to *logicalChannelIdentity* for SL-U2U-RLC as specified in TS 38.331 [3]. +- Else if the U2U SRAP Data PDU is for DRB: + - Determine the egress PC5 Relay RLC channel in the determined egress link corresponding to RLC channel configured for the concerned bearer as specified in TS 38.331 [3]. + +### 5.3a.4 Receiving operation of U2U Remote UE + +Upon receiving an U2U SRAP Data PDU from lower layer, the receiving part of the SRAP entity shall: + +- Remove the SRAP header of this U2U SRAP Data PDU and deliver the U2U SRAP SDU to upper layer entity corresponding to the BEARER ID and UE ID fields of this U2U SRAP Data PDU. + +## 5.4 Handling of unknown, unforeseen, and erroneous protocol data + +For U2N Remote UE, if *sl-LocalIdentity* and *sl-RemoteUE-RB-Identity* are both configured, when a SRAP Data PDU with SRAP header that contains a UE ID field or BEARER ID field which does not match *sl-LocalIdentity* or *sl-RemoteUE-RB-Identity* included in *sl-SRAP-ConfigRemote* is received, the SRAP entity shall: + +- discard the received SRAP Data PDU. + +For U2N Relay UE, when a SRAP Data PDU with SRAP header that contains a UE ID field or BEARER ID field which does not match *sl-LocalIdentity* or *sl-RemoteUE-RB-Identity* included in *sl-SRAP-ConfigRelay* is received except in the case where the SRAP Data PDU from SL-RLC1 as specified in TS 38.331 [3] is the first SRAP Data PDU received from a U2N Remote UE, or when a SRAP Data PDU that contains a UE ID which does not match the concerned *sl-LocalIdentity* corresponding to *sl-L2IdentityRemote* of the ingress link is received by U2N Relay UE, the SRAP entity shall: + +- discard the received SRAP Data PDU. + +When any of the U2N Remote UE, the U2N Relay UE, the U2U Remote UE or the U2U Relay UE receives a SRAP PDU with invalid or reserved values, the SRAP entity shall: + +- discard the received SRAP PDU. + +# --- 6 Protocol data units, formats, and parameters + +## 6.1 Protocol data units + +### 6.1.1 Data PDU + +The SRAP Data PDU is used to convey the following with or without the PDU header: + +- upper layer data. + +## 6.2 Formats + +### 6.2.1 General + +An SRAP Data PDU is a bit string that is byte aligned (i.e. multiple of 8 bits) in length. The formats of SRAP Data PDUs are described in clause 6.2.2 and their parameters are described in clause 6.3. + +### 6.2.2 Data PDU + +Figure 6.2.2-1 shows the format of the U2N SRAP Data PDU with SRAP header being configured. This SRAP Data PDU format is applicable to U2N SRAP SDU except those for SRB0 delivered over PC5 interface. + +![Figure 6.2.2-1: U2N SRAP Data PDU format with SRAP header. The diagram shows a header structure with three octets (D/C, R, R) followed by a multi-octet BEARER ID field. Below the header are two more multi-octet fields: UE ID and Data. Ellipses indicate additional octets.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +| | | | | | +|-------|---|---|-----------|-------| +| D/C | R | R | BEARER ID | Oct 1 | +| UE ID | | | | Oct 2 | +| Data | | | | Oct 3 | +| ... | | | | | + +Figure 6.2.2-1: U2N SRAP Data PDU format with SRAP header. The diagram shows a header structure with three octets (D/C, R, R) followed by a multi-octet BEARER ID field. Below the header are two more multi-octet fields: UE ID and Data. Ellipses indicate additional octets. + +**Figure 6.2.2-1: U2N SRAP Data PDU format with SRAP header** + +Figure 6.2.2-2 shows the format of the U2N SRAP Data PDU consisting only of a data field without any SRAP header. This SRAP Data PDU format is applicable to U2N SRAP SDU for SRB0 delivered over PC5 interface. + +![Figure 6.2.2-2: U2N SRAP Data PDU format without SRAP header. The diagram shows a single multi-octet Data field. Ellipses indicate additional octets.](a734898ce18e972938949637c32a34f4_img.jpg) + +| | | +|------|-------| +| Data | Oct 1 | +| ... | | + +Figure 6.2.2-2: U2N SRAP Data PDU format without SRAP header. The diagram shows a single multi-octet Data field. Ellipses indicate additional octets. + +**Figure 6.2.2-2: U2N SRAP Data PDU format without SRAP header** + +Figure 6.2.2-3 shows the format of the U2U SRAP Data PDU. This SRAP Data PDU format is applicable to U2U SRAP SDU delivered over PC5 interface. + +![Figure 6.2.2-3: U2U SRAP Data PDU format with SRAP header. The diagram shows a header structure with three octets (D/C, R, R) followed by a multi-octet BEARER ID field. Below the header are three multi-octet fields: UE ID (for SRC), UE ID (for DST), and Data. Ellipses indicate additional octets.](04f51626e2e10a16e3eb2c4b33cb2742_img.jpg) + +| | | | | | +|-----------------|---|---|-----------|-------| +| D/C | R | R | BEARER ID | Oct 1 | +| UE ID (for SRC) | | | | Oct 2 | +| UE ID (for DST) | | | | Oct 3 | +| Data | | | | Oct 4 | +| ... | | | | | + +Figure 6.2.2-3: U2U SRAP Data PDU format with SRAP header. The diagram shows a header structure with three octets (D/C, R, R) followed by a multi-octet BEARER ID field. Below the header are three multi-octet fields: UE ID (for SRC), UE ID (for DST), and Data. Ellipses indicate additional octets. + +**Figure 6.2.2-3: U2U SRAP Data PDU format with SRAP header** + +## 6.3 Parameters + +### 6.3.1 General + +If not otherwise mentioned in the definition of each field the bits in the parameters shall be interpreted as follows: the left most bit is the first and most significant and the right most bit is the last and least significant bit. + +Unless otherwise mentioned, integers are encoded in standard binary encoding for unsigned integers. In all cases the bits appear ordered from MSB to LSB when read in the PDU. + +### 6.3.2 UE ID + +Length: 8 bits. + +In U2N Relay case, this field carries local identity of U2N Remote UE. In U2U Relay case, there are two UE ID fields: one for local identity of each U2U Remote UE. + +### 6.3.3 BEARER ID + +Length: 5 bits. + +In U2N Relay case, this field carries information to identify Uu radio bearer for U2N Remote UE. For SRBs, the value is set to SRB Identity (which is configured by RRC parameter *srb-Identity*). For DRBs, the value is set to DRB Identity (which is configured by RRC parameter *drb-Identity*) minus 1. + +In U2U Relay case, this field carries information to identify end-to-end PC5 radio bearer for U2U Remote UE. For SL-SRBs, the value is set to 0/1/2/3 for SL-SRB 0/1/2/3 respectively. For SL-DRBs, the value is set to the 5 LSBs of *slrb-PC5-ConfigIndex* used in end-to-end SL DRB configuration procedure as specified in TS 38.331 [3]. + +### 6.3.4 Data + +Length: Variable + +This field carries the SRAP SDU (i.e. PDCP PDU or RRC PDU). + +### 6.3.5 R + +Length: 1 bit + +Reserved. In this release, reserved bits shall be set to 0. Reserved bits shall be ignored by the receiver. + +### 6.3.6 D/C + +Length: 1 bit + +This field indicates whether the corresponding SRAP PDU is an SRAP Data PDU or an SRAP Control PDU (not used in this release). + +**Table 6.3.6-1: D/C field** + +| Bit | Description | +|-----|---------------------------------------------| +| 0 | SRAP Data PDU | +| 1 | SRAP Control PDU (not used in this release) | + +# Annex A (informative): Change history + +| Change history | | | | | | | | | +|----------------|-------------|------------|------|-----|-----|----------------------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 11/2021 | RAN2#116 | R2-2109400 | | | | Skeleton | | 0.0.0 | +| 11/2021 | RAN2#116 | R2-2111485 | | | | Skeleton update | | 0.0.1 | +| 11/2021 | RAN2#116 | R2-2111489 | | | | Capture the agreement till R2#116 | | 0.1.0 | +| 01/2022 | RAN2#116bis | R2-2200364 | | | | Capture the agreement till R2#116 that related to the 38.331 running CR | | 0.2.0 | +| 01/2022 | RAN2#116bis | R2-2201996 | | | | Capture the agreement during R2#116bis | | 0.3.0 | +| 02/2022 | RAN2#117 | R2-2202276 | | | | Capture the agreement till R2#116bis that related to the 38.331 running CR | | 0.4.0 | +| 02/2022 | RAN2#117 | R2-2203594 | | | | Capture the agreement during R2#117 | | 0.5.0 | +| 03/2022 | RAN#95 | RP-220794 | | | | Submit to RAN for approval | | 1.0.0 | +| 03/2022 | RP-95 | | | | | Upgraded to Rel-17 by MCC | | 17.0.0 | +| 06/2022 | RP-96 | RP-221732 | 0001 | 1 | F | Correction on SRAP for L2 UE-to-Network Relay | | 17.1.0 | +| 09/2022 | RP-97 | RP-222524 | 0009 | 2 | F | Correction on SRAP for L2 U2N Relay | | 17.2.0 | +| 12/2022 | RP-98 | RP-223412 | 0012 | 2 | F | Corrections for L2 U2N Relay | | 17.3.0 | +| 03/2023 | RP-99 | RP-230692 | 0015 | 1 | F | Corrections on SRAP for SL relay | | 17.4.0 | +| | RP-99 | RP-230692 | 0016 | 1 | F | Correction to error handling in SRAP | | 17.4.0 | +| | RP-99 | RP-230692 | 0017 | 2 | F | Correction on SRAP for L2 U2N Relay | | 17.4.0 | +| | RP-99 | RP-230692 | 0018 | - | F | 38.351 SRAP corrections | | 17.4.0 | +| 06/2023 | RP-100 | RP-231416 | 0020 | 3 | F | Corrections on SRAP for SL relay | | 17.5.0 | +| | RP-100 | RP-231416 | 0021 | 1 | F | Corrections on SRAP for SL relay | | 17.5.0 | +| | RP-100 | RP-231416 | 0022 | 1 | F | Clarification on the SRAP configuration used in SRAP | | 17.5.0 | +| 09/2023 | RP-101 | RP-232667 | 0023 | - | F | Correction of IE name sl-SRAP-ConfigRemote | | 17.6.0 | +| | RP-101 | RP-232667 | 0024 | 2 | F | Correction on SRAP for sidelink relay | | 17.6.0 | +| | RP-101 | RP-232667 | 0025 | 1 | F | Clarification on the BEARER ID in SRAP data PDU | | 17.6.0 | +| 12/2023 | RP-102 | RP-233904 | 0027 | 3 | B | Introduction of NR sidelink relay enhancements | | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38401/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/marked/Rel-18/38_series/38401/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88b2a634cc08f2dc98d50fecae58fe7231bc75da --- /dev/null +++ b/marked/Rel-18/38_series/38401/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5273ee0f06b5f5506667d7e4887fca965e9072aa87674a17ac1e4458f8d10d01 +size 151633 diff --git a/marked/Rel-18/38_series/38401/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg b/marked/Rel-18/38_series/38401/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3353d4b7fe281476b20214f12c14b9b9f79d73c8 --- /dev/null +++ b/marked/Rel-18/38_series/38401/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69931894c2843280aed72ea9ce98e34e1ca2662dcb330b460ed7412b42f5028b +size 64316 diff --git a/marked/Rel-18/38_series/38401/16e2337d7302fa71012e69303a459c35_img.jpg b/marked/Rel-18/38_series/38401/16e2337d7302fa71012e69303a459c35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc53b745f96661632b25522a8d7db37f48404995 --- /dev/null +++ b/marked/Rel-18/38_series/38401/16e2337d7302fa71012e69303a459c35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08f59db92ac7d376a0d8d12546d2b4dfc49738f78d6fd3cd674f20e48d321330 +size 41978 diff --git a/marked/Rel-18/38_series/38401/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg b/marked/Rel-18/38_series/38401/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d48f984f84a6a30aef46696212f32db1ac2c2b48 --- /dev/null +++ b/marked/Rel-18/38_series/38401/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27f3320552f58614b9b0025cba36114bffd9d9b9feca121910160ac6432837fb +size 163036 diff --git a/marked/Rel-18/38_series/38401/2de714cedbbdd36f901f71bafa78f75a_img.jpg b/marked/Rel-18/38_series/38401/2de714cedbbdd36f901f71bafa78f75a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ae975d3fe165fab5a1014dc63f71ceb34a14b81 --- /dev/null +++ b/marked/Rel-18/38_series/38401/2de714cedbbdd36f901f71bafa78f75a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c4a59cd191009ae35027def88a176c5dd0fb9e63fa59ed1bd29d6e65b3f6c66 +size 29256 diff --git a/marked/Rel-18/38_series/38401/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Rel-18/38_series/38401/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7947aa477e1173c0a2338d8afa192900d0a5a6da --- /dev/null +++ b/marked/Rel-18/38_series/38401/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be9bfe51c4119b88283935e54d776216548df926a577d0254d2fdf24f581f234 +size 80034 diff --git a/marked/Rel-18/38_series/38401/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-18/38_series/38401/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..827e31175485c163d2c2d32489992d8d1dde5e63 --- /dev/null +++ b/marked/Rel-18/38_series/38401/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b58c41e302728f24d9c979ae6d30064f9baccb9dc9e4356adb65c80f5220762 +size 153111 diff --git a/marked/Rel-18/38_series/38401/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-18/38_series/38401/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85b61538aa8f3007eec959a76219602f1020327c --- /dev/null +++ b/marked/Rel-18/38_series/38401/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c68f4754c87ed379cf7c69235b35be4523b95fc34aba88fdf6513b5525f97187 +size 155891 diff --git a/marked/Rel-18/38_series/38401/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/Rel-18/38_series/38401/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e490dd4c5ce4f6fe0a4e9f6915e811fe05590abc --- /dev/null +++ b/marked/Rel-18/38_series/38401/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43a889195b3ed5204ae60a1f925c9f7a54d2a9a8dd410d87f455f45ff0bc50b3 +size 155900 diff --git a/marked/Rel-18/38_series/38401/3750b0149a6380885998ab3ca6a8787c_img.jpg b/marked/Rel-18/38_series/38401/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9dd5b7d5cbdb54655a8f5063107fdda8531832a0 --- /dev/null +++ b/marked/Rel-18/38_series/38401/3750b0149a6380885998ab3ca6a8787c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c322b88edbfb400b560ce36e63134f7059b1c3bedd2386f0849f4ac75c085e18 +size 25165 diff --git a/marked/Rel-18/38_series/38401/38d82ffe820e339811b396206f40a201_img.jpg b/marked/Rel-18/38_series/38401/38d82ffe820e339811b396206f40a201_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..598c039db7eecbd49f73d00a56fc73b775638bd8 --- /dev/null +++ b/marked/Rel-18/38_series/38401/38d82ffe820e339811b396206f40a201_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:739112fd45ad4971002246593f3fd3eb8e485a6256a0ac6cd8659c3a527ae1ac +size 36030 diff --git a/marked/Rel-18/38_series/38401/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg b/marked/Rel-18/38_series/38401/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ac9c27bd8d9ec996cfc9d90fe8f535bb9a1fac2 --- /dev/null +++ b/marked/Rel-18/38_series/38401/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:220ac2229342c7fdbcea9c12f0816ea2fb0dd92692d2439a0b3d83f21eb78745 +size 59645 diff --git a/marked/Rel-18/38_series/38401/41af98c5f15e6022f8ddde55567cf56e_img.jpg b/marked/Rel-18/38_series/38401/41af98c5f15e6022f8ddde55567cf56e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e8c5774119af4b65d55c8eda391348f771e835e --- /dev/null +++ b/marked/Rel-18/38_series/38401/41af98c5f15e6022f8ddde55567cf56e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed9589f10a83f698816d2d65b0d381b9974e71d9a3a2ed135d0d807aa3076692 +size 125344 diff --git a/marked/Rel-18/38_series/38401/43837b056625d3d6ce615e4c02f163bb_img.jpg b/marked/Rel-18/38_series/38401/43837b056625d3d6ce615e4c02f163bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18c6320e62ca72b67ad814d36d587cf05c286f66 --- /dev/null +++ b/marked/Rel-18/38_series/38401/43837b056625d3d6ce615e4c02f163bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b59e54b60183f667d0a82fb6d6ea469ffdf4d6d81263b1c8ad6d5363b258255f +size 43389 diff --git a/marked/Rel-18/38_series/38401/4806f9f95fff13a30d6523bd6ffeac63_img.jpg b/marked/Rel-18/38_series/38401/4806f9f95fff13a30d6523bd6ffeac63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37b3aad146fca5f40b995a762e0d3656b013628b --- /dev/null +++ b/marked/Rel-18/38_series/38401/4806f9f95fff13a30d6523bd6ffeac63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6477a2d63872789d39d8090299229c8d0a8ab678b04e984757e43c717e0c440 +size 90238 diff --git a/marked/Rel-18/38_series/38401/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-18/38_series/38401/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ed027691cb42d32829e0f51348bf4b468c3c638 --- /dev/null +++ b/marked/Rel-18/38_series/38401/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6f71c62f3ada9558bddc0bf1965923d477efab219a1cbd4019b53b0a6f79d18 +size 65069 diff --git a/marked/Rel-18/38_series/38401/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-18/38_series/38401/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5379db57fe709a1e826aa566913cda7c07dc211 --- /dev/null +++ b/marked/Rel-18/38_series/38401/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf9f3e333305cf8ee361be17225efcd87ff5d2be6ca36b9778c675c5a034de51 +size 168988 diff --git a/marked/Rel-18/38_series/38401/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-18/38_series/38401/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..abd080037afa4b0150f34a5b1af44201eac2d5e6 --- /dev/null +++ b/marked/Rel-18/38_series/38401/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99fa135dbe86a5f99dcdd1747f102a07808af3cbbd88423ac30f934a62f534b0 +size 53537 diff --git a/marked/Rel-18/38_series/38401/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-18/38_series/38401/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f952f781684c7a1558d9c90d0a3152149effcf46 --- /dev/null +++ b/marked/Rel-18/38_series/38401/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cca7b84ab8ba42665dff4f733fd66bbae6fd3664e9d38db8cc5553aaef57d4ba +size 53116 diff --git a/marked/Rel-18/38_series/38401/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg b/marked/Rel-18/38_series/38401/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..870148847397e7213ac6817f2c69a176fd065de7 --- /dev/null +++ b/marked/Rel-18/38_series/38401/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3996d2347d932fa6c3db32e4d64452521b82eb7bee3a247ca3d4343aa0774be9 +size 95299 diff --git a/marked/Rel-18/38_series/38401/71b0a68b4dd64961465d2b0e790538de_img.jpg b/marked/Rel-18/38_series/38401/71b0a68b4dd64961465d2b0e790538de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08a308e7851fd481b41fb0808f06cc6b5a0d51e8 --- /dev/null +++ b/marked/Rel-18/38_series/38401/71b0a68b4dd64961465d2b0e790538de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98d2ea9807022f519a39362f475bd67c9b1446b70b24ceea927a921955f38782 +size 72257 diff --git a/marked/Rel-18/38_series/38401/72d448a65347c51989171748789c7d4b_img.jpg b/marked/Rel-18/38_series/38401/72d448a65347c51989171748789c7d4b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47ca3486bd4027710c99e7897248a6c248fb3b00 --- /dev/null +++ b/marked/Rel-18/38_series/38401/72d448a65347c51989171748789c7d4b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1399df679963f0972b376d8077456f81aeb1f739f2aa27ef13e1758742269919 +size 196767 diff --git a/marked/Rel-18/38_series/38401/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/marked/Rel-18/38_series/38401/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21cae779dc621aeaf450ee522278184e1cd2184e --- /dev/null +++ b/marked/Rel-18/38_series/38401/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7eccbace5dfa842b27a24967949e3f72efb5e6a664b561ffa428c6d53f28ecd +size 67390 diff --git a/marked/Rel-18/38_series/38401/7722d62e33dcc894cc8555e9474c5606_img.jpg b/marked/Rel-18/38_series/38401/7722d62e33dcc894cc8555e9474c5606_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a8f507d27d97329ced3618507e3225b7df662a7 --- /dev/null +++ b/marked/Rel-18/38_series/38401/7722d62e33dcc894cc8555e9474c5606_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:185b794b3065ffd149bb5e98d95c58d90397fb431d460ae14333d3d1a78505e4 +size 85481 diff --git a/marked/Rel-18/38_series/38401/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-18/38_series/38401/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ca4a3983cce2b1592bf9cbbae2b8590aba54184 --- /dev/null +++ b/marked/Rel-18/38_series/38401/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5fadb56aaf778412eeb56bb2834fd6575546c38d4edde14196ff4d318ea884e4 +size 87653 diff --git a/marked/Rel-18/38_series/38401/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-18/38_series/38401/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24aa5379781a3c85d77a732bca028b2a7f845fdf --- /dev/null +++ b/marked/Rel-18/38_series/38401/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af13368dfabb234c541de4a78607d3aed7f31d26fff35144b22f426453ce9f4f +size 182735 diff --git a/marked/Rel-18/38_series/38401/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-18/38_series/38401/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e630faa702c578e9e7528cf704e1b13c826ae79 --- /dev/null +++ b/marked/Rel-18/38_series/38401/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e59eaa57819134d1eec60c7301140d2fcaf333bc507381628bbb0dae0a26a034 +size 59872 diff --git a/marked/Rel-18/38_series/38401/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/Rel-18/38_series/38401/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05c77d5715e1256cf3555684cbab472e287531a4 --- /dev/null +++ b/marked/Rel-18/38_series/38401/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9e2b2ec2691a027fa0660af1fdee76df0672345525e95da010a8ae5a1eeca5b +size 39497 diff --git a/marked/Rel-18/38_series/38401/9e26cd5584f423e1b2155fb341db579f_img.jpg b/marked/Rel-18/38_series/38401/9e26cd5584f423e1b2155fb341db579f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fd1c2ac1d0407394eb8db4b3276ad7eb39eca6c --- /dev/null +++ b/marked/Rel-18/38_series/38401/9e26cd5584f423e1b2155fb341db579f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee80a70841b37fb3193a57e7e68cc37a7502fa3ea1e185955bd38c2a0100e4e8 +size 67571 diff --git a/marked/Rel-18/38_series/38401/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg b/marked/Rel-18/38_series/38401/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b72c11c91a8fc8db956ee2ba0351d8dcc5530585 --- /dev/null +++ b/marked/Rel-18/38_series/38401/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2204b0339635f4e012faf7f490e46248488fc53201fccd93e45f0e7266395ebe +size 90813 diff --git a/marked/Rel-18/38_series/38401/a734898ce18e972938949637c32a34f4_img.jpg b/marked/Rel-18/38_series/38401/a734898ce18e972938949637c32a34f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c483d8df518cf7bb28ee7c5f013f7e725d33458 --- /dev/null +++ b/marked/Rel-18/38_series/38401/a734898ce18e972938949637c32a34f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fff5f58fda452ee25a7bb627052d1a64ff54b91451ae190d615a075a94d40b2 +size 59812 diff --git a/marked/Rel-18/38_series/38401/a963ca41bde1669b18a4b783616f228b_img.jpg b/marked/Rel-18/38_series/38401/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e70d73eb1351741b163c6e7c24b5c5d2fa682836 --- /dev/null +++ b/marked/Rel-18/38_series/38401/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea3be89ed2241f3ca884a134293abc7ca785afb54c22dbecb538f46efb7ba82b +size 45954 diff --git a/marked/Rel-18/38_series/38401/ad4da36431850ac19ba59bb74ec29dc9_img.jpg b/marked/Rel-18/38_series/38401/ad4da36431850ac19ba59bb74ec29dc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03a152ac2db35875725c416784d060bd73fc741c --- /dev/null +++ b/marked/Rel-18/38_series/38401/ad4da36431850ac19ba59bb74ec29dc9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cb652f1adf4e76c3c7b3fa213d51538dd674b92cb0f58f218e27d2520005928 +size 69599 diff --git a/marked/Rel-18/38_series/38401/c036e2540a94b31357ceb0002f0cacab_img.jpg b/marked/Rel-18/38_series/38401/c036e2540a94b31357ceb0002f0cacab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43832369166c5d2e76cfaea46b43398d5958bee1 --- /dev/null +++ b/marked/Rel-18/38_series/38401/c036e2540a94b31357ceb0002f0cacab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d4196f40d61357579e0b4ac1fb1b3e8db1d589cde71727133e34eac0b31e1d2 +size 45301 diff --git a/marked/Rel-18/38_series/38401/ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg b/marked/Rel-18/38_series/38401/ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe637e21bc6df5664fecdc46dc05b972c79d5e87 --- /dev/null +++ b/marked/Rel-18/38_series/38401/ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b1da11bd9cdbada928b6825e443b7ff9ae4c5d0b4964c56e047c18289377454 +size 82097 diff --git a/marked/Rel-18/38_series/38401/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/marked/Rel-18/38_series/38401/d04c50badc78d5ba47bf4e352af4a754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2cd86d22d7e905da8609abae50e014791df7379 --- /dev/null +++ b/marked/Rel-18/38_series/38401/d04c50badc78d5ba47bf4e352af4a754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:141fbd83879fa471738ff97dbff4623f6c87c921d8fa53d78fcb06b07603e15d +size 121242 diff --git a/marked/Rel-18/38_series/38401/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg b/marked/Rel-18/38_series/38401/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d89ab90abc713bed71ed8657337de1e44844889 --- /dev/null +++ b/marked/Rel-18/38_series/38401/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3b8df3f031829cb9b95ab9518edb9e086cd11ae6b09bbaa9f4e3e5f73728db9 +size 93841 diff --git a/marked/Rel-18/38_series/38401/d2417b04116c354deccb25d98a84a0fb_img.jpg b/marked/Rel-18/38_series/38401/d2417b04116c354deccb25d98a84a0fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..336c32a32293e56dabb97af6d39a3110ffaaa4c3 --- /dev/null +++ b/marked/Rel-18/38_series/38401/d2417b04116c354deccb25d98a84a0fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be381332863fa3e34f96dbb2fbd9157b7f3c902faa6845b50ec569f301edefc9 +size 53964 diff --git a/marked/Rel-18/38_series/38401/d6c377ae3e619ff992bd3647dbf43593_img.jpg b/marked/Rel-18/38_series/38401/d6c377ae3e619ff992bd3647dbf43593_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..403489b3da2ae272088e4089840b26243ab1d0b5 --- /dev/null +++ b/marked/Rel-18/38_series/38401/d6c377ae3e619ff992bd3647dbf43593_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2897b826daa279f54535c787289f05430167f31138b2f5476355cec6c444d302 +size 62915 diff --git a/marked/Rel-18/38_series/38401/da85343976fdbb19f866d9ddbdad0eae_img.jpg b/marked/Rel-18/38_series/38401/da85343976fdbb19f866d9ddbdad0eae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0853fce5a2aa013bed39e027a42b103ffa17e8c0 --- /dev/null +++ b/marked/Rel-18/38_series/38401/da85343976fdbb19f866d9ddbdad0eae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b00856fb77a18c7b820ca76b49820dffa79b6cfc7a54372d02c20cc0cfff208d +size 168166 diff --git a/marked/Rel-18/38_series/38401/db7a693cf26f527ac6c0d4d41da20858_img.jpg b/marked/Rel-18/38_series/38401/db7a693cf26f527ac6c0d4d41da20858_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b641170977d5e75efcdae34176082a62241f5e1 --- /dev/null +++ b/marked/Rel-18/38_series/38401/db7a693cf26f527ac6c0d4d41da20858_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:899a650c02cbb3db76ee8954ab22c1dc70d57c4b321a38e880747c1fc224e2d0 +size 34343 diff --git a/marked/Rel-18/38_series/38401/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-18/38_series/38401/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7cbdee1bee1d2e42d4aec84b7cef330c22fbecd --- /dev/null +++ b/marked/Rel-18/38_series/38401/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cbca4e2a67ece14e6fe0d6fe752f25d5b1d92da8e609a27aabe8afd5e112f5c +size 93882 diff --git a/marked/Rel-18/38_series/38401/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-18/38_series/38401/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0310cbc1be7540bd1fdb21ad083b2039ede68830 --- /dev/null +++ b/marked/Rel-18/38_series/38401/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d292c93a442808890df1e5a72c18f79a3bc90f78c93ce114dd0ecd29aac4baa +size 90738 diff --git a/marked/Rel-18/38_series/38401/e60c2d24a97a2855d98671d27ea43d0f_img.jpg b/marked/Rel-18/38_series/38401/e60c2d24a97a2855d98671d27ea43d0f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a2099d24e39435a7e33b20b9c8a6fcd53fa0aff --- /dev/null +++ b/marked/Rel-18/38_series/38401/e60c2d24a97a2855d98671d27ea43d0f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14f4f7054d518dcd31e3bc2b22fb4d74be0375876af0732ba6274920d13b6867 +size 50948 diff --git a/marked/Rel-18/38_series/38401/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg b/marked/Rel-18/38_series/38401/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5ee4975534a1b38d35d30db864757a39e8487bf --- /dev/null +++ b/marked/Rel-18/38_series/38401/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db05d3feae4e5c8335cf4df6854b8ef51b31ae2dec3ee767e55c312d77409539 +size 71591 diff --git a/marked/Rel-18/38_series/38401/f5d2a88925807080157c7cfb1d41cf0b_img.jpg b/marked/Rel-18/38_series/38401/f5d2a88925807080157c7cfb1d41cf0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c271f72d64b1d0798fdb2d7686a319279c08458 --- /dev/null +++ b/marked/Rel-18/38_series/38401/f5d2a88925807080157c7cfb1d41cf0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8741d4a3d43764acda49befce24c02e647fac93ad6cd842daffce931f2082e22 +size 82102 diff --git a/marked/Rel-18/38_series/38401/f61d0925551545b5938b3a4d1bbf63c3_img.jpg b/marked/Rel-18/38_series/38401/f61d0925551545b5938b3a4d1bbf63c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ee656ba9302b797c32ff33db07f7230bac5def3 --- /dev/null +++ b/marked/Rel-18/38_series/38401/f61d0925551545b5938b3a4d1bbf63c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a058af6bb93e62e2cd14b4c9e168550baaacba06084a9ebcc4ff6dfd9b2e649e +size 50462 diff --git a/marked/Rel-18/38_series/38401/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-18/38_series/38401/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d97b53c8eab3d8b7038f1c1110afc34556f31049 --- /dev/null +++ b/marked/Rel-18/38_series/38401/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43cce81cd9a6b77df5d7a8a681818d13ddf057bc63f190ae9d62173b1c2c28e5 +size 100529 diff --git a/marked/Rel-18/38_series/38410/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/Rel-18/38_series/38410/21ad58fee90f2be50708ff541d225507_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59afa50f4a7fa6d69d2662da7789d8991e4482f8 --- /dev/null +++ b/marked/Rel-18/38_series/38410/21ad58fee90f2be50708ff541d225507_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a1c7f51df3edaae5d970b154525a779c61a6156ee955f36af5354388b3b6d9c +size 15786 diff --git a/marked/Rel-18/38_series/38410/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38410/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adf37a3ac12b21d23f8b0e33a122ce2b320e21ac --- /dev/null +++ b/marked/Rel-18/38_series/38410/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e26c04424e25e72decbc6c5085aabdfce97d16b5b5647f88e6562cec1b3a62a +size 9556 diff --git a/marked/Rel-18/38_series/38410/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38410/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a01ff4d6112cf92ca0c2db51a9e7462c330bc72 --- /dev/null +++ b/marked/Rel-18/38_series/38410/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3666f4de69dd6fe9aba3c36d89dc159f32534113de149997a7d7cb02422adb32 +size 6375 diff --git a/marked/Rel-18/38_series/38410/e518bff13dc73675afd211dbea636c29_img.jpg b/marked/Rel-18/38_series/38410/e518bff13dc73675afd211dbea636c29_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..333bf9170d658da6d56cbb233344eeb4f05972bc --- /dev/null +++ b/marked/Rel-18/38_series/38410/e518bff13dc73675afd211dbea636c29_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a04a38ec1ea421f1c4fff08d0b9d966b26e61bff23184e5c283253f8c1999d23 +size 11535 diff --git a/marked/Rel-18/38_series/38410/raw.md b/marked/Rel-18/38_series/38410/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9a877a5b7b8cf74aa6283e0216bae698152f0595 --- /dev/null +++ b/marked/Rel-18/38_series/38410/raw.md @@ -0,0 +1,747 @@ + + +# 3GPP TS 38.410 V18.0.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG 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 + +## **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..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 General aspects ..... | 6 | +| 4.1 NG Architecture ..... | 6 | +| 4.2 NG interface general principles..... | 7 | +| 4.3 NG interface specification objectives ..... | 7 | +| 4.4 NG interface capabilities..... | 7 | +| 5 Functions of the NG interface..... | 8 | +| 5.1 General ..... | 8 | +| 5.2 Paging function ..... | 8 | +| 5.3 UE Context Management function..... | 8 | +| 5.4 Mobility Management function..... | 8 | +| 5.5 PDU Session Management function ..... | 8 | +| 5.6 NAS Transport function..... | 8 | +| 5.7 NAS Node Selection function..... | 8 | +| 5.8 NG Interface Management function..... | 9 | +| 5.9 Warning Message Transmission function..... | 9 | +| 5.10 Configuration Transfer function..... | 9 | +| 5.11 Trace function ..... | 9 | +| 5.12 AMF Management function..... | 9 | +| 5.13 Multiple TNL Associations Support Function..... | 9 | +| 5.14 AMF Load Balancing function ..... | 9 | +| 5.15 Location Reporting function ..... | 9 | +| 5.16 AMF Re-allocation function ..... | 9 | +| 5.17 UE Radio Capability Management function ..... | 10 | +| 5.18 NRPPa Signaling Transport function..... | 10 | +| 5.19 Overload Control function ..... | 10 | +| 5.20 Report of Secondary RAT data volumes Function ..... | 10 | +| 5.21 RIM Information Transfer function ..... | 10 | +| 5.22 Retrieve UE Information function..... | 10 | +| 5.23 RAN CP Relocation Indication function..... | 10 | +| 5.24 Suspend-Resume function..... | 10 | +| 5.25 Connection Establishment Indication Function ..... | 10 | +| 5.26 AMF CP Relocation Indication Function..... | 10 | +| 5.27 NR MBS Session Management function ..... | 11 | +| 5.28 Multicast Group Paging Function ..... | 11 | +| 5.29 QMC support function ..... | 11 | +| 5.30 MT Communication Handling function..... | 11 | +| 5.31 Timing Synchronisation Status Reporting function ..... | 11 | +| 6 Signalling procedures of the NG interface..... | 11 | +| 6.1 PDU Session Management Procedures ..... | 11 | +| 6.2 UE Context Management Procedures ..... | 11 | +| 6.3 NAS transport procedures ..... | 12 | +| 6.4 UE Mobility Management Procedures..... | 12 | +| 6.5 Paging procedure..... | 12 | +| 6.6 AMF Management procedures..... | 12 | +| 6.7 NG Interface Management procedures ..... | 12 | +| 6.8 Warning message transmission procedures..... | 13 | +| 6.9 Location Reporting procedures ..... | 13 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------|-----------| +| 6.10 | UE Radio Capability Management procedures..... | 13 | +| 6.11 | UE Tracing procedures..... | 13 | +| 6.12 | NR Positioning Protocol A (NRPPa) procedures..... | 13 | +| 6.13 | Overload Control procedures ..... | 14 | +| 6.14 | Configuration Transfer procedures ..... | 14 | +| 6.15 | Secondary RAT Data Usage Report procedure..... | 14 | +| 6.16 | RIM Information Transfer procedures ..... | 14 | +| 6.17 | Retrieve UE Information procedures ..... | 14 | +| 6.18 | RAN CP Relocation Indication procedures ..... | 14 | +| 6.19 | UE Context Suspend procedure ..... | 14 | +| 6.20 | Connection Establishment Indication procedure..... | 15 | +| 6.21 | AMF CP Relocation Indication procedure..... | 15 | +| 6.22 | UE Context Resume procedure..... | 15 | +| 6.23 | NR MBS Session Management Procedures ..... | 15 | +| 6.24 | Multicast Group Paging Procedures..... | 15 | +| 6.25 | The procedures for supporting QMC ..... | 16 | +| 6.26 | MT Communication Handling procedures..... | 16 | +| 6.27 | Timing Synchronisation Status Reporting procedures..... | 16 | +| 7 | NG interface protocol structure..... | 16 | +| 7.1 | NG Control Plane ..... | 16 | +| 7.2 | NG User Plane..... | 17 | +| 8 | Other NG interface specifications..... | 17 | +| 8.1 | NG-RAN NG interface: NG layer 1 (TS 38.411) ..... | 17 | +| 8.2 | NG-RAN NG interface: NG signalling transport (TS 38.412) ..... | 17 | +| 8.3 | NG-RAN NG interface: NG application protocol (NGAP) (TS 38.413)..... | 17 | +| 8.4 | NG-RAN NG interface: NG data transport (TS 38.414) ..... | 17 | +| 8.5 | NG-RAN NG interface: NG PDU Session user plane protocol (TS 38.415) ..... | 17 | +| Annex A (informative): | Change history..... | 18 | + +# --- 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 38.41x series of technical specifications that define the NG interface for the interconnection of an NG-RAN node to the 5GC (5G Core Network). + +# --- 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.411: "NG-RAN; NG layer 1". +- [3] 3GPP TS 38.412: "NG-RAN; NG signalling transport". +- [4] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP) ". +- [5] 3GPP TS 38.414: "NG-RAN; NG data transport". +- [6] 3GPP TS 23.502: "Procedures for the 5G system". +- [7] 3GPP TS 38.300: "NR; Overall Description; Stage 2". +- [8] 3GPP TS 23.501: "System Architecture for the 5G system". +- [9] 3GPP TS 38.415: "PDU Session User Plane Protocol". + +- [10] 3GPP TS 38.455: "NR Positioning Protocol A (NRPPa)". +- [11] 3GPP TS 36.300: "E-UTRAN; Overall description; Stage 2". +- [12] 3GPP TS 23.247: "Architectural enhancements for 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 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]. + +**gNB:** as defined in TS 38.300 [7]. + +**NB-IoT:** as defined in TS36.300 [11]. + +**ng-eNB:** as defined in TS 38.300 [7]. + +**NG-RAN node:** as defined in TS 38.300 [7]. + +**UPF:** as defined in TS 23.501 [8]. + +## 3.2 Abbreviations + +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]. + +| | | +|--------|-----------------------------------------| +| 5GC | 5G Core Network | +| AMF | Access and Mobility Management Function | +| CIoT | Cellular IoT | +| DRX | Discontinuous Reception | +| MBS | Multicast/Broadcast Service | +| NB-IoT | Narrow Band Internet of Things | +| NG-U | NG User plane interface | +| PTP | Point to Point | +| PTM | Point to Multipoint | +| QMC | QoE Measurement Collection | +| QoE | Quality of Experience | +| RIM | Remote Interference Management | +| SMF | Session Management Function | +| UP | User Plane | +| UPF | User Plane Function | + +# --- 4 General aspects + +## 4.1 NG Architecture + +The NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture, i.e. the NG-RAN logical nodes and interfaces between them, are defined as part of the RNL. + +The NG-RAN architecture consists of a set of gNBs and ng-eNBs which are connected to the 5GC through the NG interface and is specified in TS 38.300 [7]. + +The NG-RAN may have several NG access points towards the 5GC. As a minimum, each NG access point (in NG-RAN or 5GC) shall independently fulfil the requirements of the relevant NG specifications (3GPP 38.41x series - see clause 7). + +NG is a logical interface. + +There may be multiple NG-C logical interfaces towards the 5GC from any one NG-RAN node. The selection of the NG-C interface is then determined by the NAS Node Selection function as described in clause 5. + +There may be multiple NG-U logical interfaces towards the 5GC from any one NG-RAN node. The selection of the NG-U interface is done within the 5GC and signalled to the NG-RAN node by the AMF. + +## 4.2 NG interface general principles + +The general principles for the specification of the NG interface are as follows: + +- the NG interface is open; +- the NG interface supports the exchange of signalling information between the NG-RAN and 5GC; +- from a logical standpoint, the NG is a point-to-point interface between an NG-RAN node and a 5GC node. A point-to-point logical interface is feasible even in the absence of a physical direct connection between the NG-RAN and 5GC; +- the NG interface supports control plane and user plane separation; +- the NG interface separates Radio Network Layer and Transport Network Layer; +- the NG interface is future proof to fulfil different new requirements and support of new services and new functions; +- the NG interface is decoupled with the possible NG-RAN deployment variants; +- the NG Application Protocol supports modular procedures design and uses a syntax allowing optimized encoding /decoding efficiency. + +## 4.3 NG interface specification objectives + +The NG interface specification facilitates the following: + +- inter-connection of NG-RAN nodes with AMFs supplied by different manufacturers; +- separation of NG interface Radio Network functionality and Transport Network functionality to facilitate introduction of future technology. + +## 4.4 NG interface capabilities + +The NG interface supports: + +- procedures to establish, maintain and release NG-RAN part of PDU sessions; +- procedures to perform intra-RAT handover and inter-RAT handover; +- the separation of each UE on the protocol level for user specific signalling management; +- the transfer of NAS signalling messages between UE and AMF; +- mechanisms for resource reservation for packet data streams; +- procedures to establish, maintain and release NG-RAN part of MBS sessions. + +# 5 Functions of the NG interface + +## 5.1 General + +The following clauses describe the functions supported over the NG interface. + +## 5.2 Paging function + +The paging function supports the sending of paging requests to the NG-RAN nodes involved in the paging area e.g. the NG-RAN nodes of the TA(s) the UE is registered. + +The function also supports CN controlled subgrouping paging for UE Power Saving. + +## 5.3 UE Context Management function + +The UE Context management function allows the AMF to establish, modify or release a UE Context in the AMF and the NG-RAN node e.g. to support user individual signalling on NG. + +The function also enables the AMF to manage RRC state notifications of a CM-CONNECTED UE. + +## 5.4 Mobility Management function + +The mobility function for UEs in CM-CONNECTED includes the intra-system handover function to support mobility within NG-RAN and inter-system handover function to support mobility from/to EPS system. It comprises the preparation, execution and completion of handover via the NG interface. + +## 5.5 PDU Session Management function + +The PDU Session function is responsible for establishing, modifying and releasing the involved PDU sessions NG-RAN resources for user data transport once a UE context is available in the NG-RAN node. + +NGAP supports transparent relaying of PDU Session related information by the AMF as described in TS 23.502 [6]. + +## 5.6 NAS Transport function + +The NAS Signalling Transport function provides means to transport or reroute a NAS message (e.g. for NAS mobility management), or report the non-delivery of a NAS message for a specific UE over the NG interface. + +## 5.7 NAS Node Selection function + +The interconnection of NG-RAN nodes to multiple AMFs is supported in the 5GS architecture. + +Therefore, a NAS node selection function is located in the NG-RAN node to determine the AMF association of the UE, based on the UE's temporary identifier, which was assigned to the UE by the AMF. When the UE's temporary identifier has not been yet assigned or is no longer valid the NG-RAN node may instead take into account other information (e.g. slicing information, onboarding indication) to determine the AMF. When the NG-RAN node is configured to ensure that the selected AMF serves the country where the UE is located, as described in TS 23.501 [8], the NG-RAN node takes into account UE location information, if available, when determining the AMF. + +This functionality is located in the NG-RAN node and enables proper routing via the NG interface. On NG, no specific procedure corresponds to the NAS Node Selection Function. + +## 5.8 NG Interface Management function + +The NG-interface management functions provide + +- means to ensure a defined start of NG-interface operation (reset); +- means to handle different versions of application part implementations and protocol errors (error indication). + +## 5.9 Warning Message Transmission function + +The warning message transmission function provides means to transfer warning messages via NG interface or cancel ongoing broadcast of warning messages. It also provides the capability for the NG-RAN to inform the AMF that ongoing PWS operation has failed for one or more areas, or that one or more areas may be reloaded by the CBC. + +## 5.10 Configuration Transfer function + +The Configuration Transfer function is a generic mechanism that allows the request and transfer of RAN configuration information (e.g. SON information) between two RAN nodes via the core network. + +## 5.11 Trace function + +The Trace function provides means to control trace sessions in the NG-RAN node. + +## 5.12 AMF Management function + +The AMF management function supports AMF planned removal and AMF auto-recovery as specified in TS 23.501 [8]. + +## 5.13 Multiple TNL Associations Support Function + +When there are multiple TNL associations between a NG-RAN node and an AMF, the NG-RAN node selects the TNL association for NGAP signalling based on the usage and the weight factor of each TNL association received from the AMF, and uses the TNL association as specified in TS 23.501 [8] and TS 23.502 [6]. If an AMF releases a TNL association or a TNL association has failed, the NG-RAN node selects a new one as specified in TS 23.501 [8] and TS 23.502 [6]. + +## 5.14 AMF Load Balancing function + +The NG interface supports the indication by the AMF of its relative capacity to the NG-RAN node in order to achieve load-balanced AMFs within the pool area. + +## 5.15 Location Reporting function + +This function enables the AMF to request the NG-RAN node to report the UE's current location, or the UE's last known location with timestamp, or the UE's presence in a configured area of interest. + +## 5.16 AMF Re-allocation function + +This function allows to redirect an initial connection request issued by an NG-RAN node from an initial AMF towards a target AMF selected by 5GC. In this case the NG-RAN node initiates an Initial UE Message procedure over one NG interface instance and receives the first downlink message to close the UE-associated logical connection over a different NG interface instance. + +## 5.17 UE Radio Capability Management function + +The UE Radio Capability Management function is related to the UE radio capability handling. + +## 5.18 NRPPa Signaling Transport function + +The NRPPa (NR Positioning Protocol A) Signalling Transport function provides means to transport an NRPPa (3GPP TS 38.455 [10]) message transparently over the NG interface. + +## 5.19 Overload Control function + +The overload function provides means to enable AMF controls the load that the NG-RAN node(s) are generating. + +## 5.20 Report of Secondary RAT data volumes Function + +The Report of Secondary RAT data volumes Function enables the NG-RAN node to report Secondary RAT usage data information in case of MR-DC, either with a dedicated procedure or by including Secondary RAT usage data information in other messages. + +## 5.21 RIM Information Transfer function + +The RIM Information Transfer function is a generic mechanism that allows the transfer of Remote Interference Management (RIM) information between two RAN nodes via the core network. + +## 5.22 Retrieve UE Information function + +The Retrieve UE Information function enables the NG-RAN node to request UE information (e.g. QoS differentiation information) from the AMF before the setup of the NG connection for NB-IoT UE(s) using Control Plane CIoT 5GS Optimization. + +## 5.23 RAN CP Relocation Indication function + +The RAN CP Relocation Indication function enables the initiation of the UE-associated logical NG-connection for a NB-IoT UE using Control Plane CIoT 5GS Optimisation following a re-establishment request. It allows to have the re-establishment request authenticated by the AMF. + +## 5.24 Suspend-Resume function + +This function enables to suspend the UE-associated logical NG-connection and release the NG-U tunnel while storing the UE context in the NG-RAN for a faster subsequent resume as specified for User Plane CIoT 5GS optimizations in TS 23.501 [8]. In this version of the specification, this function only applies for long eDRX cycles. + +## 5.25 Connection Establishment Indication Function + +The connection establishment indication function enables the AMF to complete the establishment of the UE-associated logical NG-connection. + +## 5.26 AMF CP Relocation Indication Function + +The AMF CP relocation indication function enables the AMF to inform the previously serving NG-RAN node that the UE's connection is to be relocated to a new NG-RAN node. + +## 5.27 NR MBS Session Management function + +The MBS Session Management function is responsible for establishing, modifying and releasing the involved NR MBS sessions NG-RAN resources for user data transport once an MBS context is available in the NG-RAN node. + +NGAP supports transparent relaying of MBS Session related information by the AMF as described in TS 23.247 [12]. + +## 5.28 Multicast Group Paging Function + +The Multicast group paging function supports the sending of multicast group paging requests to the NG-RAN nodes in order to group-page UEs that have joined the Multicast MBS Session + +## 5.29 QMC support function + +The QMC function provides means to manage the QMC sessions and support the mobility of QMC sessions over the NG interface. + +## 5.30 MT Communication Handling function + +The function enables to support MT data and signalling handling within the CN for UEs in RRC\_INACTIVE state with extended DRX beyond 10.24s as specified in TS 23.501[8]. + +## 5.31 Timing Synchronisation Status Reporting function + +The Timing Synchronisation Status Reporting function enables the AMF to request the NG-RAN node to report the RAN timing synchronisation status information, and for the NG-RAN node to provide the RAN timing synchronisation status information to the AMF. + +# --- 6 Signalling procedures of the NG interface + +## 6.1 PDU Session Management Procedures + +The following PDU Session management procedures are used to establish, release or modify PDU sessions. + +- PDU Session Resource Setup; +- PDU Session Resource Release; +- PDU Session Resource Modify; +- PDU Session Resource Notify; +- PDU Session Resource Modify Indication. + +## 6.2 UE Context Management Procedures + +The following UE Context management procedures are used to establish, release or modify the UE context. They may also be used to report RRC state transition from NG-RAN to 5GC. + +- Initial Context Setup; +- UE Context Release Request; +- UE Context Release; +- UE Context Modification; + +- RRC Inactive Transition Report. + +## 6.3 NAS transport procedures + +The NAS transport procedures enable transparent transfer of NAS signalling data between the AMF and the UE. The procedures providing this functionality are: + +- Initial UE Message (NG-RAN node initiated); +- Uplink NAS transport (NG-RAN node initiated); +- Downlink NAS transport (AMF initiated); +- NAS non delivery indication (NG-RAN node initiated); +- Reroute NAS Request (AMF initiated). + +## 6.4 UE Mobility Management Procedures + +The following UE Mobility management procedures are used to prepare, execute or cancel handovers: + +- Handover Preparation; +- Handover Resource Allocation; +- Handover Notification; +- Path Switch Request; +- Uplink RAN Status Transfer; +- Downlink RAN Status Transfer; +- Handover Cancellation ; +- Handover Success; +- Uplink RAN Early Status Transfer; +- Downlink RAN Early Status Transfer. + +## 6.5 Paging procedure + +The following paging procedure is used to send paging requests to the NG-RAN nodes involved in the paging area: + +- Paging. + +## 6.6 AMF Management procedures + +The following AMF management procedures are used by the AMF to inform the NG-RAN nodes about an AMF's status, and to release the UE TNLA binding for specific UE(s): + +- AMF Status Indication; +- UE TNLA binding release. + +## 6.7 NG Interface Management procedures + +The following procedures are used to manage the NG interface: + +- NG Setup; + +- RAN Configuration Update; +- AMF Configuration Update; +- NG Reset; +- Error Indication. + +## 6.8 Warning message transmission procedures + +The following procedures are used to manage the broadcasting of warning messages: + +- Write-Replace Warning; +- PWS Cancel; +- PWS Restart Indication; +- PWS Failure Indication. + +## 6.9 Location Reporting procedures + +The following procedures are used to report the location of the UE: + +- Location Reporting Control; +- Location Report; +- Location Reporting Failure Indication. + +## 6.10 UE Radio Capability Management procedures + +The following procedures are related to the UE radio capability handling: + +- UE Radio Capability Check; +- UE Radio Capability Info Indication; +- UE Radio Capability ID Mapping. + +## 6.11 UE Tracing procedures + +The following procedures are used to trace the UE: + +- Trace Start; +- Trace Failure Indication; +- Deactivate Trace; +- Cell Traffic Trace. + +## 6.12 NR Positioning Protocol A (NRPPa) procedures + +The following procedures are used for NRPPa signalling: + +- Downlink UE Associated NRPPa Transport; +- Uplink UE Associated NRPPa Transport; +- Downlink non-UE Associated NRPPa Transport; + +- Uplink non-UE Associated NRPPa Transport. + +## 6.13 Overload Control procedures + +The following procedures are used by the AMF to start or stop overload control: + +- Overload Start procedure; +- Overload Stop procedure. + +## 6.14 Configuration Transfer procedures + +The following procedures are used by the AMF to transfer the RAN configuration information: + +- Downlink RAN Configuration Transfer procedure; +- Uplink RAN Configuration Transfer procedure. + +## 6.15 Secondary RAT Data Usage Report procedure + +The following procedure is used to provide information on the used resources of the secondary RAT: + +- Secondary RAT Data Usage Report procedure. + +## 6.16 RIM Information Transfer procedures + +The following procedures are used by the AMF to transfer the Remote Interference Management (RIM) information: + +- Downlink RIM Information Transfer procedure; +- Uplink RIM Information Transfer procedure. + +## 6.17 Retrieve UE Information procedures + +The following procedures are used by the NG-RAN node to retrieve UE information from the AMF: + +- Retrieve UE Information Request procedure; +- UE Information Transfer procedure. + +## 6.18 RAN CP Relocation Indication procedures + +The following procedure is used by the NG-RAN node to initiate the UE-associated logical NG-connection for the RAN CP Relocation function: + +- RAN CP Relocation Indication procedure. + +## 6.19 UE Context Suspend procedure + +The following procedure is to suspend the UE-associated logical NG-connection and release the NG-U tunnel with the 5GC while keeping the UE context in NG-RAN. In this version of the specification, this procedure applies only if the NG-RAN node is an ng-eNB. + +- UE Context Suspend procedure. + +## 6.20 Connection Establishment Indication procedure + +The following procedure is used to enable the AMF to provide information to the NG-RAN node to complete the establishment of the UE-associated logical NG-connection, for UEs using CIoT 5GS Optimization: + +- Connection Establishment Indication. + +The UE Radio Capability may be provided from the AMF to the NG-RAN node in this procedure. If the UE Radio Capability is not included, this may trigger the NG-RAN node to request the UE Radio Capability from the UE and to provide it to the AMF in the UE RADIO CAPABILITY INFO INDICATION message. + +## 6.21 AMF CP Relocation Indication procedure + +The following procedure is used to inform the previously serving NG-RAN node that the UE's connection is to be relocated to a new NG-RAN node, for UEs using Control Plane CIoT 5GS optimizations: + +- AMF CP Relocation Indication. + +## 6.22 UE Context Resume procedure + +The following procedure is used to resume the UE context, resume the suspended logical NG-connection and re-establish the related NG-U tunnel in the 5GC for the involved UE. In this version of the specification, this procedure applies only if the NG-RAN node is an ng-eNB. + +- UE Context Resume procedure. + +## 6.23 NR MBS Session Management Procedures + +The following list of MBS Session management procedures are used to establish, release, or modify NG-RAN resources for a NR MBS session: + +- Broadcast Session Resource Setup; +- Broadcast Session Modification; +- Broadcast Session Resource Release; +- Broadcast Session Resource Release Required; +- Broadcast Session Transport; +- Multicast Session Activation; +- Multicast Session Deactivation; +- Multicast Session Update; +- Distribution Setup; +- Distribution Release; + +## 6.24 Multicast Group Paging Procedures + +The following Multicast Group Paging procedure is used to send multicast group paging requests to the NG-RAN nodes: + +- Multicast Group Paging. + +## 6.25 The procedures for supporting QMC + +The following procedures are used to control the QMC sessions in the UE and to transfer QMC session information to the target NG-RAN node during a UE's intra-system intra-RAT or intra-system inter-RAT mobility: + +- Initial Context Setup; +- UE Context Modification; +- Handover Preparation; +- Handover Resource Allocation. + +## 6.26 MT Communication Handling procedures + +The following procedures are used by the NG-RAN node to request the AMF to activate or deactivate the CN based MT communication handling for UEs in RRC\_INACTIVE state with long extended DRX beyond 10.24 seconds, and by the CN to indicate availability of downlink data or downlink signalling to the NG-RAN node. + +- MT Communication Handling procedure. +- RAN Paging Request procedure. + +## 6.27 Timing Synchronisation Status Reporting procedures + +The following procedures are used to report the RAN timing synchronisation status information: + +- Timing Synchronization Status; +- Timing Synchronization Status Report. + +# --- 7 NG interface protocol structure + +## 7.1 NG Control Plane + +The control plane protocol stack of the NG interface is shown on Figure 7.1-1. The transport network layer is built on IP transport. For the reliable transport of signalling messages, SCTP is added on top of IP. The application layer signalling protocol is referred to as NGAP (NG Application Protocol). + +![Diagram of the NG Interface Control Plane protocol stack. The stack consists of five layers: NGAP at the top, followed by SCTP, IP, Data link layer, and Physical layer at the bottom. A double-headed vertical arrow is shown between the NGAP and SCTP layers, indicating bidirectional communication.](e518bff13dc73675afd211dbea636c29_img.jpg) + +``` +graph TD; NGAP[NGAP] <--> SCTP[SCTP]; SCTP --- IP[IP]; IP --- DDL[Data link layer]; DDL --- PL[Physical layer]; +``` + +Diagram of the NG Interface Control Plane protocol stack. The stack consists of five layers: NGAP at the top, followed by SCTP, IP, Data link layer, and Physical layer at the bottom. A double-headed vertical arrow is shown between the NGAP and SCTP layers, indicating bidirectional communication. + +Figure 7.1-1: NG Interface Control Plane + +## 7.2 NG User Plane + +The NG user plane (NG-U) interface is defined between a NG-RAN node and a UPF. The NG-U interface provides non guaranteed delivery of PDU Session/MBS session user plane PDUs between the NG-RAN node and the UPF. + +The protocol stack for NG-U is shown in Figure 7.2-1. + +![Diagram of the NG-U protocol stack for PDU/MBS Session. The stack consists of five layers: PDU/MBS Session User plane PDUs (top), GTP-U, UDP, IP, Data link layer, and Physical layer (bottom). A double-headed arrow indicates bidirectional communication between the top layer and the GTP-U layer.](21ad58fee90f2be50708ff541d225507_img.jpg) + +| | +|------------------------------------| +| PDU/MBS Session
User plane PDUs | +| ↕ | +| GTP-U | +| UDP | +| IP | +| Data link layer | +| Physical layer | + +Diagram of the NG-U protocol stack for PDU/MBS Session. The stack consists of five layers: PDU/MBS Session User plane PDUs (top), GTP-U, UDP, IP, Data link layer, and Physical layer (bottom). A double-headed arrow indicates bidirectional communication between the top layer and the GTP-U layer. + +Figure 7.2-1: NG-U protocol structure for PDU/MBS Session + +# --- 8 Other NG interface specifications + +## 8.1 NG-RAN NG interface: NG layer 1 (TS 38.411) + +TS 38.411 [2] specifies the physical layer technologies that may be used to support the NG interface. + +## 8.2 NG-RAN NG interface: NG signalling transport (TS 38.412) + +TS 38.412 [3] specifies how the NGAP signalling messages are transported over NG. + +## 8.3 NG-RAN NG interface: NG application protocol (NGAP) (TS 38.413) + +TS 38.413 [4] specifies the radio network layer signalling procedures of the control plane between the NG-RAN node and the AMF. + +## 8.4 NG-RAN NG interface: NG data transport (TS 38.414) + +TS 38.414 [5] specifies the standards for user data transport protocols over the NG interface. + +## 8.5 NG-RAN NG interface: NG PDU Session user plane protocol (TS 38.415) + +TS 38.415 [9] specifies the PDU Session user plane protocol procedures, and the PDU Set Information user plane protocol procedures over the NG interface. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|---------------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-04 | R3#95b | R3-171127 | | | | TS skeleton | 0.0.0 | +| 2017-04 | R3#95b | R3-171397 | | | | Update including TP from R3-171375 with text reduction from rapporteur | 0.0.1 | +| 2017-05 | R3#96 | R3-171218 | | | | Update of title page and change history | 0.0.2 | +| 2017-05 | R3#96 | R3-171965 | | | | Addition of section 4 and 6. Deletion of the content of section 5 with detailed PDU session management procedure. Update of change history | 0.1.0 | +| 2017-05 | R3#96 | R3-172019 | | | | Integration of R3-171981 with NAS Transport procedures. Update of change history. | 0.2.0 | +| 2017-07 | R3 NR AH# 2 | R3-172632 | | | | Integration of R3-172597 and R3-172598 respectively adding of a list of functions in section 5 and adding references to other NG specifications in sections 2 and 8. | 0.3.0 | +| 2017-09 | R3#97 | R3-173448 | | | | Integration of R3-173319 and R3-173325 respectively adding a list of procedures and the AMF transparency for PDU session related information. Integration of R3-173318 for terminology alignment with NG-RAN node. | 0.4.0 | +| 2017-10 | R3#97bis | R3-174238 | | | | Integration of R3-174104 modifying the NG architecture section. Integration of 3784 adding a list of procedures. Integration of 4151 adding AMF management function and procedures. | 0.5.0 | +| 2017-12 | R3#98 | R3-175055 | | | | Integration of R3-174527. | 0.6.0 | +| 2018-01 | R3 NR AH#1801 | R3-180648 | | | | Integration of R3-180540 removing NG-RAN from the abbreviations. Integration of R3-180095 correcting the description style of some procedures. | 0.7.0 | +| 2018-03 | R3#99 | R3-181585 | | | | Integration of R3-181486 for stage 2 of PWS support. Integration of R3-181412 on NGAP support of multiple SCTP associations. | 0.8.0 | +| 2018-04 | R3#99bis | R3-182523 | | | | Integration of R3-181981 introducing TS 38.415. Integration of R3-182273 introducing explicit per UE TNLA binding release. | 0.9.0 | +| 2018-05 | R3#100 | R3-183590 | | | | Integration of R3-183343 with location reporting function and procedures. Integration of R3-183479 with AMF re-allocation function. Correction of some editorials according to drafting rules. | 0.10.0 | +| 2018-06 | RAN#80 | RP-180739 | | | | For approval | 1.0.0 | +| 2018-06 | RAN#80 | | | | | Specification approved at TSG-RAN and placed under change control | 15.0.0 | +| 2018-09 | RAN#81 | RP-181922 | 0001 | 4 | F | NR Corrections (38.410 Baseline CR covering RAN3#101 agreements) | 15.1.0 | +| 2018-12 | RAN#82 | RP-182446 | 0004 | 1 | F | Rapporteur's CR for TS38.410 | 15.2.0 | +| 2018-12 | RAN#82 | RP-182447 | 0005 | 1 | B | Introduction of Data Volume Reporting for MR-DC | 15.2.0 | +| 2019-12 | RP-86 | RP-192908 | 0017 | 2 | B | Remote Interference Management Message Transfer Support | 16.0.0 | +| 2020-03 | RP-87-e | RP-200429 | 0023 | - | F | Rapporteur Correction of TS 38.410 | 16.1.0 | +| 2020-07 | RP-88-e | RP-201088 | 0018 | 6 | B | Introduction of NB-IoT dedicated CP functions when connected to 5GC | 16.2.0 | +| 2020-07 | RP-88-e | RP-201086 | 0019 | 6 | B | Introduction of Suspend-Resume for 5GC | 16.2.0 | +| 2020-07 | RP-88-e | RP-201086 | 0020 | 7 | B | Introduction of CP CIoT 5GS Optimisation for NB-IoT and MTC connected to 5GC (Stage 2) | 16.2.0 | +| 2020-07 | RP-88-e | RP-201075 | 0024 | 2 | B | Baseline CR for introducing Rel-16 NR mobility enhancement | 16.2.0 | +| 2020-07 | RP-88-e | RP-201078 | 0025 | 2 | B | Introducing Radio Capability Optimisation (RACS) | 16.2.0 | +| 2020-09 | RP-89-e | RP-201951 | 0026 | 1 | F | Rapporteur Correction of TS 38.410 | 16.3.0 | +| 2021-09 | RP-93-e | RP-211882 | 0033 | 3 | F | Correction on NAS non delivery | 16.4.0 | +| 2022-03 | RP-95-e | RP-220225 | 0029 | 7 | C | Clarification of NAS Node Selection Function for NTN nodes providing access over multiple countries | 17.0.0 | +| 2022-03 | RP-95-e | RP-220224 | 0030 | 10 | B | MBS BL CR for TS 38.410 | 17.0.0 | +| 2022-03 | RP-95-e | RP-220220 | 0032 | 7 | B | Introduction of support for eNPN | 17.0.0 | +| 2022-03 | RP-95-e | RP-220229 | 0034 | 4 | B | BLCR to 38.410: Support of QoE Measurement Collection for NR | 17.0.0 | +| 2022-03 | RP-95-e | RP-220235 | 0037 | 1 | B | Support for UE Power Saving Enhancements | 17.0.0 | +| 2022-03 | RP-95-e | RP-220236 | 0038 | | D | Rapporteur Corrections of TS 38.410 | 17.0.0 | +| 2022-06 | RP-96 | RP-221134 | 0040 | 1 | F | Correction on NR MBS for 38410 | 17.1.0 | +| 2022-06 | RP-96 | RP-221143 | 0042 | 1 | F | QoE Rel-17 Corrections | 17.1.0 | +| 2023-12 | RAN#102 | RP-233816 | 0044 | 6 | B | Introduction of NR Redcap Enhancement | 18.0.0 | +| 2023-12 | RAN#102 | RP-233829 | 0045 | 3 | B | (CR to 38.410) Update of MBS RAN sharing solution | 18.0.0 | +| 2023-12 | RAN#102 | RP-233838 | 0046 | 3 | B | Introduction of 5G Timing Resiliency and URLLC enhancements | 18.0.0 | +| 2023-12 | RAN#102 | RP-233833 | 0047 | 0 | B | Introduction of R18 QoE measurement enhancements | 18.0.0 | +| 2023-12 | RAN#102 | RP-233831 | 0048 | 0 | B | Support for XR UP design using new container | 18.0.0 | + diff --git a/marked/Rel-18/38_series/38411/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38411/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36294e9bffcd9d5d73c89527784b9a18c0daeb1c --- /dev/null +++ b/marked/Rel-18/38_series/38411/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42eb76986f24be7cbec4b11807882a11364209bf570b3f5495b4d5f8a4260143 +size 7698 diff --git a/marked/Rel-18/38_series/38411/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38411/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a61b26f4d41275eedf3047dce1e9a82b5848cd93 --- /dev/null +++ b/marked/Rel-18/38_series/38411/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:410412a1f681d3a864ab56d6241a01597549a11ac17054680ad7381115d92d75 +size 5884 diff --git a/marked/Rel-18/38_series/38411/raw.md b/marked/Rel-18/38_series/38411/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..aedba1cd4ff6e88ff8f00e61d56586d9d0deeeb0 --- /dev/null +++ b/marked/Rel-18/38_series/38411/raw.md @@ -0,0 +1,143 @@ + + +# 3GPP TS 38.411 V18.0.0(2024-03) + +Technical Specification + +**3rd Generation Partnership Project; +Technical Specification Group Radio Access Network; +NG-RAN; +NG layer 1 +(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 'P' has a red signal wave icon at its base. + +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. + +© 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 Abbreviations..... 5 + +4 Introduction..... 5 + +5 Layer 1 specifications ..... 5 + +6 Interface to management plane ..... 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. + +# --- 1 Scope + +The present document specifies the standards allowed to implement layer 1 on the NG 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 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 [1]. + +# --- 4 Introduction + +The main functions of layer 1 are summarized in the following: + +- Interface to physical medium; +- Frame delineation; +- Line clock extraction capability; +- Layer 1 alarms extraction and generation; +- Transmission quality control. + +# --- 5 Layer 1 specifications + +The support of any suitable layer 1 technique - like point-to-point or point-to-multipoint techniques - shall not be prevented. + +# --- 6 Interface to management plane + +The description of the interface towards the management plane is out of scope of this document, but at least the following O&M functions should be foreseen: + +- Performance monitoring functions; +- Alarm status reporting functions; +- Synchronisation source management. \ No newline at end of file diff --git a/marked/Rel-18/38_series/38420/43837b056625d3d6ce615e4c02f163bb_img.jpg b/marked/Rel-18/38_series/38420/43837b056625d3d6ce615e4c02f163bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e1626f2c98aa45c5e19e17c3a0bdfe51503937e --- /dev/null +++ b/marked/Rel-18/38_series/38420/43837b056625d3d6ce615e4c02f163bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d98c65343ed1de585953c078e4f583299a41746ea184d8cc8be5a35dc365e7a4 +size 87453 diff --git a/marked/Rel-18/38_series/38420/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38420/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab7fcff6441d8a44e2461d7e7b06a5d97a35eb1f --- /dev/null +++ b/marked/Rel-18/38_series/38420/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1e413ad522e4fc144e00d9046712773ea7b365e815ed00ab132f35bc70e4ef8 +size 9565 diff --git a/marked/Rel-18/38_series/38420/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38420/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2600acb8e54e4385555360ab3abac474043dd4dc --- /dev/null +++ b/marked/Rel-18/38_series/38420/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f175de9300bba4035acef0580dffc303d46b1f625c6e0ff218a3895ed0b75d2 +size 7278 diff --git a/marked/Rel-18/38_series/38420/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-18/38_series/38420/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54bfdfdfc8db95b338c3c0e65a9b6ead4bd4b349 --- /dev/null +++ b/marked/Rel-18/38_series/38420/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f9dc073ebdaa36df34114ee6aadc399e3d7ecbd5e3a89097f0bea18defc891e +size 11021 diff --git a/marked/Rel-18/38_series/38420/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg b/marked/Rel-18/38_series/38420/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7b0225c980ca0f2db6a6b3085f07ef3a0abf3d0 --- /dev/null +++ b/marked/Rel-18/38_series/38420/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e92ecb4d113037e0d818f7490c943aeb2654bc7ed8fa1da72a5a40f0b8cf4a4e +size 13552 diff --git a/marked/Rel-18/38_series/38420/raw.md b/marked/Rel-18/38_series/38420/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..04d6b96dde7137846ec84ff2b5b5e00860c0366f --- /dev/null +++ b/marked/Rel-18/38_series/38420/raw.md @@ -0,0 +1,685 @@ + + +# 3GPP TS 38.420 V18.0.0 (2023-12) --- + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn 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 + +## **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..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 7 | +| 4 General aspects ..... | 7 | +| 4.1 Introduction ..... | 7 | +| 4.2 Xn interface general principles ..... | 7 | +| 4.3 Xn interface specification objectives ..... | 7 | +| 4.4 Xn interface capabilities..... | 8 | +| 5 Functions of the Xn interface..... | 8 | +| 5.1 General ..... | 8 | +| 5.2 Functions of Xn-C..... | 8 | +| 5.2.1 Xn-C interface management and error handling functions ..... | 8 | +| 5.2.1.1 General..... | 8 | +| 5.2.1.2 Xn Setup function ..... | 8 | +| 5.2.1.3 Error Indication function ..... | 8 | +| 5.2.1.4 Xn reset function..... | 8 | +| 5.2.1.5 Xn configuration data update function ..... | 8 | +| 5.2.1.6 Xn removal function ..... | 8 | +| 5.2.2 UE mobility management functions ..... | 8 | +| 5.2.2.1 Handover preparation function ..... | 8 | +| 5.2.2.2 Handover cancellation function..... | 9 | +| 5.2.2.3 Retrieve UE Context function..... | 9 | +| 5.2.2.4 RAN Paging function..... | 9 | +| 5.2.2.5 Data Forwarding control function..... | 9 | +| 5.2.2.6 Handover Success Indication Function..... | 9 | +| 5.2.2.7 Conditional Handover cancellation function ..... | 9 | +| 5.2.3 Dual connectivity function ..... | 9 | +| 5.2.4 Energy saving function..... | 9 | +| 5.2.5 Resource coordination function..... | 9 | +| 5.2.6 Secondary RAT Data Volume Report function..... | 9 | +| 5.2.7 Trace function..... | 9 | +| 5.2.8 Load management function ..... | 9 | +| 5.2.9 Data exchange for self-optimisation function ..... | 9 | +| 5.2.10 IAB support function..... | 10 | +| 5.2.10.1 F1-C Traffic Transfer function ..... | 10 | +| 5.2.10.2 IAB Transport Migration function..... | 10 | +| 5.2.10.3 IAB Resource Coordination function ..... | 10 | +| 5.2.11 Small data transmission function..... | 10 | +| 5.2.11.1 General..... | 10 | +| 5.2.11.2 Partial UE Context Transfer function ..... | 10 | +| 5.2.12 QMC support function..... | 10 | +| 5.2.13 MBS management support function..... | 10 | +| 5.2.14 AI/ML support function ..... | 10 | +| 5.3 Functions of Xn-U..... | 10 | +| 5.3.1 Data transfer function ..... | 10 | +| 5.3.2 Flow control function ..... | 11 | +| 5.3.3 Assistance information function..... | 11 | +| 5.3.4 Fast retransmission function..... | 11 | +| 6 Xn interface procedures ..... | 11 | +| 6.1 General ..... | 11 | + +| | | | +|-------------------------------|------------------------------------------------------------------------|-----------| +| 6.2 | Control plane protocol procedures ..... | 11 | +| 6.2.1 | Mobility management procedures ..... | 11 | +| 6.2.2 | Dual Connectivity procedures ..... | 11 | +| 6.2.3 | Global procedures ..... | 12 | +| 6.2.4 | Interface Management procedures ..... | 12 | +| 6.2.5 | Energy saving procedures ..... | 12 | +| 6.2.6 | Resource coordination procedures ..... | 12 | +| 6.2.7 | UE Tracing procedures ..... | 12 | +| 6.2.8 | Load management procedures ..... | 12 | +| 6.2.9 | Data exchange for self-optimisation procedures ..... | 13 | +| 6.2.10 | IAB procedures ..... | 13 | +| 6.2.11 | MBS Management procedures ..... | 13 | +| 6.2.12 | Small data transmission procedures ..... | 13 | +| 6.2.13 | QMC support procedures ..... | 14 | +| 6.2.14 | AI/ML support procedures ..... | 14 | +| 6.3 | User plane protocol procedures ..... | 14 | +| 7 | Xn interface protocol structure ..... | 14 | +| 7.1 | Xn Control Plane ..... | 14 | +| 7.2 | Xn User Plane ..... | 15 | +| 8 | Other Xn interface specifications ..... | 16 | +| 8.1 | NG-RAN Xn interface: Xn layer 1 (TS 38.421) ..... | 16 | +| 8.2 | NG-RAN Xn interface: Xn signalling transport (TS 38.422) ..... | 16 | +| 8.3 | NG-RAN Xn interface: Xn application protocol (XnAP) (TS 38.423) ..... | 16 | +| 8.4 | NG-RAN Xn interface: Xn data transport (TS 38.424) ..... | 16 | +| 8.5 | NG-RAN Xn interface: NR user plane protocol (TS 38.425) ..... | 16 | +| 8.6 | NG-RAN Xn interface: PDU Session User Plane Protocol (TS 38.415) ..... | 17 | +| 8.7 | Summary of NG-RAN Xn interface Technical Specifications ..... | 17 | +| Annex A (informative): | Change history ..... | 18 | + +# --- 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 TSG RAN TS 38.42x series of Technical Specifications that define the Xn interface. It is an interface for the interconnection of two NG-RAN nodes within the NG-RAN architecture (TS 38.401 [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 38.401: "NG-RAN; Architecture description". +- [3] 3GPP TS 38.421: "NG-RAN; Xn layer 1". +- [4] 3GPP TS 38.422: "NG-RAN; Xn signalling transport". +- [5] 3GPP TS 38.423: "NG-RAN; Xn Application Protocol (XnAP)". +- [6] 3GPP TS 38.424: "NG-RAN; Xn data transport". +- [7] 3GPP TS 38.425: "NG-RAN; NR user plane protocol". +- [8] 3GPP TS 38.300: "NR; Overall Description; Stage 2". +- [9] 3GPP TS 37.340: "NR; Multi-connectivity; Overall description; Stage-2". +- [10] 3GPP TS 38.415: "PDU Session User Plane protocol". +- [11] 3GPP TS 29.281: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)". + +# --- 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]. + +**AI:** as defined in TS 38.300 [8]. + +**Boundary IAB-node:** as defined in TS 38.401 [2]. + +**corresponding node:** as defined in TS 38.425 [7]. + +**F1-terminating IAB-donor:** as defined in TS 38.401 [2]. + +**IAB-DU:** as defined in TS 38.300 [8]. + +**IAB-MT:** as defined in TS 38.300 [8]. + +Mobile IAB-node: as defined in TS 38.300 [8]. + +**Non-F1-terminating IAB-donor:** as defined in TS 38.401 [2]. + +**ML:** as defined in TS 38.300 [8]. + +**NG-RAN node:** as defined in TS 38.300 [8]. + +RRC-terminating IAB-donor: as defined in TS 38.401 [2]. + +**secondary node:** as defined in TS 37.340 [9]. + +## 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]. + +| | | +|------|--------------------------------------| +| IAB | Integrated Access and Backhaul | +| MBS | Multicast Broadcast Service | +| QMC | QoE Measurement Collection | +| QoE | Quality of Experience | +| SCTP | Stream Control Transmission Protocol | +| Xn-C | Xn Control plane | +| Xn-U | Xn User plane | + +# --- 4 General aspects + +## 4.1 Introduction + +The interface allowing to interconnect NG-RAN nodes with each other is referred to as the Xn interface. + +## 4.2 Xn interface general principles + +The general principles for the specification of the Xn interface are as follows: + +- the Xn interface is open; +- the Xn interface supports the exchange of signalling information between two NG-RAN nodes, and the forwarding of PDUs to the respective tunnel endpoints; +- from a logical standpoint, the Xn is a point-to-point interface between two NG-RAN nodes. A point-to-point logical interface should be feasible even in the absence of a physical direct connection between the two NG-RAN nodes. + +## 4.3 Xn interface specification objectives + +The Xn interface specifications facilitate the following: + +- inter-connection of NG-RAN nodes supplied by different manufacturers; +- support of continuation between NG-RAN nodes of the NG-RAN services offered via the NG interface; +- separation of Xn interface Radio Network functionality and Transport Network functionality to facilitate introduction of future technology. + +## 4.4 Xn interface capabilities + +The Xn interface supports: + +- procedures to support intra-NG-RAN mobility; +- procedures to support dual connectivity between NG-RAN nodes. + +# --- 5 Functions of the Xn interface + +## 5.1 General + +The following clauses describe the functions supported in Xn interface. + +## 5.2 Functions of Xn-C + +### 5.2.1 Xn-C interface management and error handling functions + +#### 5.2.1.1 General + +These functions allow for managing of signalling associations between NG-RAN nodes, surveying the Xn interface and recovering from errors. + +#### 5.2.1.2 Xn Setup function + +This function allows for the initial setup of an Xn interface between two NG-RAN nodes, including exchange of application level data. + +#### 5.2.1.3 Error Indication function + +This function allows the reporting of general error situations on application level. + +#### 5.2.1.4 Xn reset function + +This function allows an NG-RAN node to inform a second NG-RAN node that it has recovered from an abnormal failure and that either all or some of the contexts (except the application level data) related to the first node and stored in the second shall be deleted, and the associated resources released. + +#### 5.2.1.5 Xn configuration data update function + +This function allows two NG-RAN nodes to update application level data at any time. + +#### 5.2.1.6 Xn removal function + +This function allows two NG-RAN nodes to remove the respective Xn interface. + +### 5.2.2 UE mobility management functions + +#### 5.2.2.1 Handover preparation function + +This function allows the exchange of information between source and target NG-RAN nodes in order to initiate the handover of a certain UE to the target. + +#### 5.2.2.2 Handover cancellation function + +This function allows informing an already prepared target NG-RAN node that a prepared handover will not take place. It allows releasing the resources allocated during a preparation. + +#### 5.2.2.3 Retrieve UE Context function + +The Retrieve UE context function is used for a NG-RAN node to retrieve UE context from another one. + +#### 5.2.2.4 RAN Paging function + +The RAN paging function allows a NG-RAN node to initiate the paging for a UE in the inactive state. + +#### 5.2.2.5 Data Forwarding control function + +The data forwarding control function allows establishing and releasing transport bearers between source and target NG-RAN nodes for data forwarding. + +#### 5.2.2.6 Handover Success Indication Function + +This function allows informing a source NG-RAN node that the UE has successfully accessed a target NG-RAN node. + +#### 5.2.2.7 Conditional Handover cancellation function + +This function allows informing a source NG-RAN node that resources reserved for candidate target cell(s) during a conditional handover preparation are about to be released by the target NG-RAN node. + +### 5.2.3 Dual connectivity function + +The dual connectivity function enables usage of additional resources in a secondary node in the NG-RAN. + +### 5.2.4 Energy saving function + +This function enables decreasing energy consumption by indication of cell activation/deactivation or SSB beam activation/deactivation over the Xn interface. + +### 5.2.5 Resource coordination function + +This function enables coordination of cell resource usage between two NG-RAN nodes. + +### 5.2.6 Secondary RAT Data Volume Report function + +This function enables the NG-RAN node to report Secondary RAT usage data information in case of MR-DC with 5GC, either with a dedicated procedure or by including Secondary RAT usage data information in other messages. + +### 5.2.7 Trace function + +The Trace function provides means to control trace sessions for a UE over Xn interface. + +### 5.2.8 Load management function + +This function allows exchanging resource status and traffic load information between NG-RAN nodes, such that the NG-RAN node can control the traffic load appropriately. + +### 5.2.9 Data exchange for self-optimisation function + +This function allows two NG-RAN nodes to exchange information in order to support self-optimization functionality. + +### 5.2.10 IAB support function + +#### 5.2.10.1 F1-C Traffic Transfer function + +This function is used to deliver F1-C traffic between the M-NG-RAN node and the S-NG-RAN node serving a dual-connected IAB-node, where the F1-C traffic is either received from the IAB-node or sent to the IAB-node. + +#### 5.2.10.2 IAB Transport Migration function + +This function allows the exchange of information between the F1-terminating IAB-donor and the non-F1-terminating IAB-donor of a boundary IAB-node, for the purpose of managing the migration of the boundary and descendant IAB-node traffic between the topologies managed by the two IAB-donors. This function also allows the exchange of information between the F1-terminating IAB-donor and the RRC-terminating IAB-donor of a mobile IAB-node, for the purpose of managing the migration of the mobile IAB-node traffic between the topologies managed by the two IAB-donors. + +#### 5.2.10.3 IAB Resource Coordination function + +This function is used to exchange information between the F1-terminating IAB-donor and the non-F1-terminating IAB-donor of a boundary IAB-node in order to support resource multiplexing between the IAB-MT and the IAB-DU of the boundary IAB-node. This function is also used to exchange resource multiplexing related information between the F1-terminating IAB-donor and the RRC-terminating IAB-donor of a mobile IAB-node in order to support resource multiplexing between the IAB-MT and the IAB-DU of the mobile IAB-node. + +### 5.2.11 Small data transmission function + +#### 5.2.11.1 General + +This function supports small data transmission sessions in RRC\_INACTIVE both with and without anchor relocation. + +#### 5.2.11.2 Partial UE Context Transfer function + +The Partial UE Context Transfer function is used for the last serving NG-RAN node to provide part of the UE Context to the receiving gNB. + +### 5.2.12 QMC support function + +The QMC function provides means to support the mobility of QMC sessions over the Xn interface and to support the coordination of QMC information in case of dual connectivity. + +### 5.2.13 MBS management support function + +This function is used to support the management of MBS Sessions, including the addition of MBS related information in interface management and mobility procedures, and the support of RAN Multicast paging. + +### 5.2.14 AI/ML support function + +This function is used to support AI/ML for NG-RAN, including initiation of data collection and reporting of collected data. + +## 5.3 Functions of Xn-U + +### 5.3.1 Data transfer function + +The data transfer function allows the transfer of data between NG-RAN nodes to support dual connectivity or mobility operation. + +### 5.3.2 Flow control function + +The flow control function enables a NG-RAN node receiving user plane data from a second NG-RAN node to provide feedback information associated with the data flow. + +### 5.3.3 Assistance information function + +The assistance information function enables a NG-RAN node receiving user plane data from a second NG-RAN node to provide assistance information to the second node (e.g. related to radio conditions). + +### 5.3.4 Fast retransmission function + +The fast retransmission function provides coordination between PDCP-hosting node and corresponding node in case of outage in one of the nodes, to enables the node in good RF conditions to handle data previously forwarded to the node in outage. + +# --- 6 Xn interface procedures + +## 6.1 General + +The Xn interface supports procedures over the control plane (Xn-C) and user plane (Xn-U). + +## 6.2 Control plane protocol procedures + +### 6.2.1 Mobility management procedures + +The mobility management procedures are used to manage the UE mobility in Connected or RRC\_Inactive modes: + +- Handover Preparation +- Handover Cancel +- SN Status Transfer +- Retrieve UE Context +- RAN Paging +- Xn-U Address Indication +- UE Context Release +- Handover Success Indication +- Conditional Handover Cancel +- Retrieve UE Context Confirm + +### 6.2.2 Dual Connectivity procedures + +The dual connectivity procedures are used to add, modify and releases resources for the operation of Dual Connectivity: + +- S-NG-RAN-node Addition Preparation +- S-NG-RAN-node Reconfiguration Completion +- M-NG-RAN-node initiated S-NG-RAN-node Modification Preparation + +- S-NG-RAN-node initiated S-NG-RAN-node Modification +- M-NG-RAN-node initiated S-NG-RAN-node Release +- S-NG-RAN-node initiated S-NG-RAN-node Release +- S-NG-RAN-node Counter Check +- RRC Transfer +- Notification Control Indication +- Activity Notification +- Secondary RAT Data Usage Report +- Conditional PSCell Change Cancel + +### 6.2.3 Global procedures + +The global procedures are used to exchange configuration level data between two NG-RAN nodes, or to remove Xn connectivity between two NG-RAN nodes in a controlled manner: + +- Xn Setup +- NG-RAN-node Configuration Update +- Xn Removal + +### 6.2.4 Interface Management procedures + +The interface management procedures are used to align resources between two NG-RAN nodes in the event of failures, and to report detected protocol errors: + +- Reset +- Error Indication + +### 6.2.5 Energy saving procedures + +- Cell Activation procedure: enables an NG-RAN node to request the activation of a previously deactivated cell or SSB beam hosted in another NG-RAN node. + +### 6.2.6 Resource coordination procedures + +- E-UTRA - NR Cell Resource Coordination procedure: enables an ng-eNB and a gNB to interact for resource coordination purposes. + +### 6.2.7 UE Tracing procedures + +The following procedures are used to trace the UE: + +- Trace Start procedure +- Deactivate Trace procedure +- Cell Traffic Trace + +### 6.2.8 Load management procedures + +The load management procedures are used by NG-RAN nodes to indicate resource status, overload and traffic load to each other. + +- Resource Status Reporting Initiation +- Resource Status Reporting + +### 6.2.9 Data exchange for self-optimisation procedures + +The data exchange for self-optimisation procedures are used to transfer failure, access and mobility related information among NG-RAN nodes to enable self-optimisation + +- Failure Indication +- Handover report +- Mobility Settings Change +- Access and Mobility Indication +- SCG Failure Information Report +- SCG Failure Transfer +- RACH Indication + +### 6.2.10 IAB procedures + +The IAB procedures are used to enable the transfer of F1/non-F1 traffic for IAB, to exchange information between the F1-terminating IAB-donor and the non-F1-terminating IAB-donor of a boundary IAB-node, to enable the delivery of F1-C traffic between the M-NG-RAN node and the S-NG-RAN node serving a dual-connected non-boundary IAB-node, to exchange resource multiplexing related information between the F1-terminating IAB-donor and the non-F1-terminating IAB-donor of a boundary IAB-node, to exchange information between the F1-terminating IAB-donor and the RRC-terminating IAB-donor of a mobile IAB-node, and to exchange resource multiplexing related information between the F1-terminating IAB-donor and the RRC-terminating IAB-donor of the mobile IAB-node: + +- F1-C Traffic Transfer +- IAB Transport Migration Management +- IAB Transport Migration Modification +- IAB Resource Coordination + +### 6.2.11 MBS Management procedures + +The MBS management procedures are used to manage the MBS Session: + +- RAN Multicast Group Paging procedure + +### 6.2.12 Small data transmission procedures + +- Partial UE Context Transfer: enables exchange of information between NG-RAN nodes for SDT transmission without anchor relocation + +Small data transmission is also supported by the following procedures: + +- RRC Transfer +- Retrieve UE Context Confirm +- RAN Paging + +### 6.2.13 QMC support procedures + +The following procedures are used to transfer QMC configuration and session information to the target NG-RAN node during a UE's intra-system intra-RAT mobility: + +- Handover Preparation +- Retrieve UE Context + +The following procedures are used to coordinate QMC configuration and reporting between the M-NG-RAN node and the S-NG-RAN node: + +- S-NG-RAN node Addition Preparation +- M-NG-RAN node initiated S-NG-RAN node Modification Preparation +- S-NG-RAN node initiated S-NG-RAN node Modification +- S-NG-RAN node initiated S-NG-RAN node Change +- RRC Transfer + +### 6.2.14 AI/ML support procedures + +The following procedures are used to initiate data collection and report collected data to support, e.g., AI/ML for NG-RAN: + +- Data Collection Reporting Initiation +- Data Collection Reporting + +## 6.3 User plane protocol procedures + +The user plane protocol procedures are used to exchange user plane information between Xn-U protocol peers: + +- Transfer of Downlink User Data procedure: enables the node hosting the NR PDCP entity to provide user plane information to the corresponding node. +- Downlink Data Delivery Status procedure: enables the corresponding node to provide feedback to the node hosting the NR PDCP entity. +- Transfer of Assistance Information: enables the corresponding node to provide assistance information to the node hosting the NR PDCP entity. +- Transfer of PDU Session Information procedure: enables an NG-RAN node to provide user plane information associated with the forwarding of data towards a peer NG-RAN node, when using PDU session tunnels. + +# --- 7 Xn interface protocol structure + +## 7.1 Xn Control Plane + +The control plane protocol stack of the Xn interface is shown on Figure 7.1-1. The transport network layer is built on IP transport. For the reliable transport of signalling messages, SCTP is added on top of IP. The application layer signalling protocol is referred to as XnAP (Xn Application Protocol). + +![Figure 7.1-1: Xn Interface Control Plane protocol stack diagram](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +The diagram illustrates the protocol stack for the Xn Interface Control Plane. It consists of five layers stacked vertically. At the top is the XnAP layer. Below it is the SCTP layer, followed by the IP layer, the Data link layer, and finally the Physical layer at the bottom. A double-headed vertical arrow is positioned between the XnAP layer and the SCTP layer, indicating bidirectional communication. + +Figure 7.1-1: Xn Interface Control Plane protocol stack diagram + +**Figure 7.1-1: Xn Interface Control Plane** + +## 7.2 Xn User Plane + +The Xn user plane (Xn-U) interface is defined between two NG-RAN nodes. The Xn-U interface provides non-guaranteed delivery of user plane PDUs between two NG-RAN nodes. + +The protocol stack for Xn-U is shown in Figure 7.2-1. + +![Figure 7.2-1: Xn-U protocol structure diagram](c67d21fb3d9042e88cdc669f071b4e7c_img.jpg) + +The diagram illustrates the protocol stack for the Xn User Plane. It consists of five layers stacked vertically. At the top is the User plane PDUs layer. Below it is the GTP-U layer, followed by the UDP layer, the IP layer, the Data link layer, and finally the Physical layer at the bottom. A double-headed vertical arrow is positioned between the User plane PDUs layer and the GTP-U layer, indicating bidirectional communication. + +Figure 7.2-1: Xn-U protocol structure diagram + +**Figure 7.2-1: Xn-U protocol structure** + +The user plane packets conveyed by GTP-U may be PDCP PDUs (e.g. in case of dual connectivity), PDCP SDUs (e.g. in case of DRB level data forwarding), or SDAP SDUs (e.g. in PDU Session level data forwarding). + +User plane protocol messages (as defined in TS 38.425 [7] and TS 38.415 [10]) are carried by container fields in the GTP-U extension header as specified in TS 29.281 [11]. A single GTP-U packet may carry a user plane packet and/or a user plane protocol message. The mapping between container fields and Xn user plane protocol procedures and functions is described in Table 7.2-1. + +**Table 7.2-1: Mapping between container fields and Xn user plane procedures / functions** + +| Xn-U Function | Container Type | Xn UP Protocol Procedure | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| +| Data transfer | NR RAN Container, as per TS 29.281 [11] (Note 1) | Transfer of Downlink User Data, TS 38.425 [7] | +| | PDU Session Container, as per TS 29.281 [11] (Note 2) | Transfer of DL PDU Session Information, TS 38.415 [10]
Transfer of UL PDU Session Information, TS 38.415 [10] | +| | No container (Note 3) | NA | +| Flow control | NR RAN Container as per TS 29.281 [11] (Note 4) | Downlink Data Delivery Status, TS 38.425 [7]
Transfer of Downlink User Data, TS 38.425 [7] | +| Fast retransmission | NR RAN Container as per TS 29.281 [11] (Note 4) | Downlink Data Delivery Status, TS 38.425 [7]
Transfer of Downlink User Data, TS 38.425 [7] | +| Assistance information | NR RAN Container as per TS 29.281 [11] (Note 4) | Transfer of Assistance Information, TS 38.425 [7] | +| Note 1: optionally used in Dual Connectivity DL data transfer.
Note 2: in case of PDU Session level forwarding only.
Note 3: all other cases of data transfer when no other Xn-U functionality is required
Note 4: optionally used in Dual Connectivity | | | + +# 8 Other Xn interface specifications + +## 8.1 NG-RAN Xn interface: Xn layer 1 (TS 38.421) + +TS 38.421 [3] specifies the physical layer technologies that may be used to support the Xn interface. + +## 8.2 NG-RAN Xn interface: Xn signalling transport (TS 38.422) + +TS 38.422 [4] specifies how the XnAP signalling messages are transported over Xn. + +## 8.3 NG-RAN Xn interface: Xn application protocol (XnAP) (TS 38.423) + +TS 38.423 [5] specifies the radio network layer signalling procedures of the control plane between NG-RAN nodes. + +## 8.4 NG-RAN Xn interface: Xn data transport (TS 38.424) + +TS 38.424 [6] specifies the standards for user data transport protocols over the NG-RAN Xn interface. + +## 8.5 NG-RAN Xn interface: NR user plane protocol (TS 38.425) + +TS 38.425 [7] specifies the user plane protocol procedures for dual connectivity over the NG-RAN Xn interface. + +## 8.6 NG-RAN Xn interface: PDU Session User Plane Protocol (TS 38.415) + +TS 38.415 [10] specifies the user plane protocol procedures for data forwarding using PDU Session tunnels over the NG-RAN Xn interface. + +TS 38.415 [10] specifies the PDU Set Information user plane protocol for sending PDU Set Information and indication of End of Data Burst over the NG-RAN Xn interface. + +## 8.7 Summary of NG-RAN Xn interface Technical Specifications + +The relationship between the technical specifications that define the NG-RAN Xn interface is shown in Figure 8.7-1. + +![Diagram showing the relationship between technical specifications for the NG-RAN Xn interface, categorized into Radio Network Control Plane and User Plane across Radio Network Layer and Transport Layer.](43837b056625d3d6ce615e4c02f163bb_img.jpg) + +The diagram illustrates the technical specifications for the NG-RAN Xn interface, organized into two main planes: Radio Network Control Plane and User Plane, across two layers: Radio Network Layer and Transport Layer. + +| | Radio Network Control Plane | User Plane | | | +|---------------------|--------------------------------------|--------------------------------|-------------------------------------|----------------------------------------------| +| Radio Network Layer | XnAP
TS 38.423 | (void) | NR User Plane protocol
TS 38.425 | PDU Session User Plane protocol
TS 38.415 | +| Transport Layer | Xn Signalling Transport
TS 38.422 | Xn Data Transport
TS 38.424 | | | +| | Xn Layer 1 TS 38.421 | | | | + +Diagram showing the relationship between technical specifications for the NG-RAN Xn interface, categorized into Radio Network Control Plane and User Plane across Radio Network Layer and Transport Layer. + +Figure 8.7-1: Xn Interface Technical Specifications + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|---------------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-04 | R3#95b | R3-171313 | | | | TS skeleton | 0.0.1 | +| 2017-05 | R3#96 | R3-171807 | | | | Change of structure of clause 5 | 0.0.2 | +| 2017-05 | R3#96 | R3-171967 | | | | Further skeleton change following agreements at R3#96
Initial text for clauses 4, 7 and 8 (R3-171966)
Functions from R3-171927
Add change history | 0.1.0 | +| 2017-07 | R3 NR AH | R3-172636 | | | | TP from R3-172596 | 0.2.0 | +| 2017-09 | R3#97 | R3-173453 | | | | TPs from R3-173320 and R3-173321 | 0.3.0 | +| 2017-10 | R3#97bis | R3-174241 | | | | TP from R3-173636 | 0.4.0 | +| 2017-12 | R3#98 | R3-175057 | | | | TPs from R3-174451 and R3-174764 | 0.5.0 | +| 2018-02 | R3 NR AH 1801 | R3-180653 | | | | TP from R3-180543 | 0.6.0 | +| 2018-03 | R3#99 | R3-181590 | | | | TP from R3-181388 | 0.7.0 | +| 2018-04 | R3#99bis | R3-182526 | | | | TP from R3-181866 | 0.8.0 | +| 2018-06 | R3#100 | R3-183595 | | | | TPs from R3-183098, R3-182719 and R3-183375 | 0.9.0 | +| 2018-06 | RP#80 | RP-180687 | | | | Presentation to RAN for one step approval | 1.0.0 | +| 2018-06 | RAN#80 | - | - | - | - | Specification approved at TSG-RAN and placed under change control | 15.0.0 | +| 2018-09 | RAN#81 | RP-181922 | 0001 | 2 | F | NR Corrections (38.420 Baseline CR covering RAN3-101 agreements) | 15.1.0 | +| 2018-12 | RAN#82 | RP-182446 | 0004 | 1 | F | Rapporteur's CR for TS 38.420 | 15.2.0 | +| 2018-12 | RAN#82 | RP-182447 | 0006 | - | B | Introduction of Data Volume Reporting for MR-DC | 15.2.0 | +| 2018-12 | RAN#82 | RP-182447 | 0007 | - | F | Rename the Data Forwarding Address Indication procedure | 15.2.0 | +| 2020-07 | RAN#88-e | RP-201075 | 0008 | 8 | B | Baseline CR for introducing Rel-16 NR mobility enhancement | 16.0.0 | +| 2020-07 | RAN#88-e | RP-201082 | 0018 | 3 | B | BLCR to 38.420: Addition of MDT feature | 16.0.0 | +| 2020-07 | RAN#88-e | RP-201082 | 0019 | 3 | B | BLCR to 38.420: Addition of SON feature | 16.0.0 | +| 2022-03 | RAN#95-e | RP-220222 | 0020 | 7 | B | CR on CP-UP separation for Rel-17 IAB | 17.0.0 | +| 2022-03 | RAN#95-e | RP-220224 | 0022 | 3 | B | BL CR to TS38.420 | 17.0.0 | +| 2022-03 | RAN#95-e | RP-220218 | 0023 | 2 | B | CPAC BL CR to TS 38.420 | 17.0.0 | +| 2022-03 | RAN#95-e | RP-220233 | 0024 | 2 | B | RA-SDT BLCR to TS 38.420 | 17.0.0 | +| 2022-03 | RAN#95-e | RP-220236 | 0025 | 1 | B | Addition of the Retrieve UE Context Confirm procedure [InterMNResume] | 17.0.0 | +| 2022-03 | RAN#95-e | RP-220229 | 0026 | - | B | BLCR to 38.420: Support of QoE Measurement Collection for NR | 17.0.0 | +| 2022-06 | RAN#96 | RP-221141 | 0027 | - | F | Alignment with rel-17 changes in XnAP | 17.1.0 | +| 2022-06 | RAN#96 | RP-221134 | 0028 | 1 | F | Alignment with rel-17 changes in XnAP | 17.1.0 | +| 2022-06 | RAN#96 | RP-221136 | 0029 | - | F | Alignment with rel-17 changes in XnAP | 17.1.0 | +| 2022-06 | RAN#96 | RP-221128 | 0030 | 1 | F | IAB Rel-17 Corrections | 17.1.0 | +| 2022-06 | RAN#96 | RP-221143 | 0031 | - | F | QoE Rel-17 Corrections | 17.1.0 | +| 2022-09 | RAN#97-e | RP-222183 | 0032 | 1 | F | Correction to 38.420 for IAB | 17.2.0 | +| 2023-12 | RAN#102 | RP-233819 | 0034 | 6 | B | Introduction on MT-SDT | 18.0.0 | +| 2023-12 | RAN#102 | RP-233832 | 0035 | 3 | B | SON Introduction of RACH Indication | 18.0.0 | +| 2023-12 | RAN#102 | RP-233837 | 0036 | 3 | B | Support of AIML for NG-RAN | 18.0.0 | +| 2023-12 | RAN#102 | RP-233835 | 0037 | 1 | B | Support of mobile IAB | 18.0.0 | +| 2023-12 | RAN#102 | RP-233833 | 0038 | 1 | B | QMC enhancements for NR-DC | 18.0.0 | +| 2023-12 | RAN#102 | RP-233817 | 0039 | 0 | B | Network energy saving enhancements | 18.0.0 | +| 2023-12 | RAN#102 | RP-233831 | 0040 | 0 | B | Support for XR PDU Set Handling | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38421/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38421/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a93c4d0bda174b0bd353ced9a4097e6ca326bdc6 --- /dev/null +++ b/marked/Rel-18/38_series/38421/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d26e9e9c68d911ea3ae8a17036e086dca6dc531854441b038d29d927e6239d37 +size 9460 diff --git a/marked/Rel-18/38_series/38421/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38421/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a8175c1c7833ee96bf7d7b4c4a8ecec1a8f4d90 --- /dev/null +++ b/marked/Rel-18/38_series/38421/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee2e15b74cc52291fd878d24714af88112512ba905cf6d13db670535bef110fc +size 6797 diff --git a/marked/Rel-18/38_series/38421/raw.md b/marked/Rel-18/38_series/38421/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6b33f53b905de98fb1b94f04ef55af19685df3e0 --- /dev/null +++ b/marked/Rel-18/38_series/38421/raw.md @@ -0,0 +1,114 @@ + + +# 3GPP TS 38.421 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn 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 +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 | +| 5 Void..... | 6 | +| 6 Void..... | 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. + +# --- 1 Scope + +The present document specifies the standards allowed to implement layer 1 on the Xn 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 Xn Layer 1 shall comply with the requirements of clauses 4 through 6 in TS 38.411 [1]. + +# --- 5 Void + +# --- 6 Void \ No newline at end of file diff --git a/marked/Rel-18/38_series/38455/00c1e69f3f99d3499b03d2463d6d2fd2_img.jpg b/marked/Rel-18/38_series/38455/00c1e69f3f99d3499b03d2463d6d2fd2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df2e5ee0c85e7524ad2d367af9bc93eaaecfad0e --- /dev/null +++ b/marked/Rel-18/38_series/38455/00c1e69f3f99d3499b03d2463d6d2fd2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a33c5012bd03ac3abcca0829a480a9f53d386facbef2f743c8d1e7b223b35c53 +size 22103 diff --git a/marked/Rel-18/38_series/38455/04cfca33e3fc26513abe649d7474f733_img.jpg b/marked/Rel-18/38_series/38455/04cfca33e3fc26513abe649d7474f733_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..722ccbf5c6e5770ac6b185bce45a2724b93a0913 --- /dev/null +++ b/marked/Rel-18/38_series/38455/04cfca33e3fc26513abe649d7474f733_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55d1fbf25c77f0bda75041d32ec9302100af70262c0e301fc746cd1c06a5162e +size 22505 diff --git a/marked/Rel-18/38_series/38455/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/Rel-18/38_series/38455/09955ff8214ffb6947951fc0f60eb6ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4708caeaba3a299dd983f83b2df24f8774981316 --- /dev/null +++ b/marked/Rel-18/38_series/38455/09955ff8214ffb6947951fc0f60eb6ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:500659e451174e1af27f4c695c1da0a2654793da0db396689d9a3715bb691ff9 +size 26634 diff --git a/marked/Rel-18/38_series/38455/0fa26005ab105a07af4fda20b2554987_img.jpg b/marked/Rel-18/38_series/38455/0fa26005ab105a07af4fda20b2554987_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c571291254e63bdc2a20dfae40389e9d815a1ca5 --- /dev/null +++ b/marked/Rel-18/38_series/38455/0fa26005ab105a07af4fda20b2554987_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c80e4e2434a637fb1d9aeaa3768953efdfdfeebf6ace3aed14db782d41db16c +size 25630 diff --git a/marked/Rel-18/38_series/38455/144e1d61e8738b22dcf4a683f869ac6f_img.jpg b/marked/Rel-18/38_series/38455/144e1d61e8738b22dcf4a683f869ac6f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3721fd10f65f5776962169f151eab647fdacf94 --- /dev/null +++ b/marked/Rel-18/38_series/38455/144e1d61e8738b22dcf4a683f869ac6f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7e51608e95bbb10e925af25c05c505723c09b181d50934ff3da60bb3321f9e9 +size 15663 diff --git a/marked/Rel-18/38_series/38455/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg b/marked/Rel-18/38_series/38455/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71b8d4c5530c1a237533d68ae28d45b5d80f1179 --- /dev/null +++ b/marked/Rel-18/38_series/38455/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb18222a8c5f550f27d552fedfd76509192fd3a8f0a7e8db4448001eaa1cd950 +size 27147 diff --git a/marked/Rel-18/38_series/38455/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg b/marked/Rel-18/38_series/38455/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5378bce0afbf2edab96622f2123c7c5af4b9f3c0 --- /dev/null +++ b/marked/Rel-18/38_series/38455/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3250a2c3ed56a4f99d85fe1a5e534bc6db0b18e6d40450524af820f3b9d4fa0 +size 17906 diff --git a/marked/Rel-18/38_series/38455/26e334e61dd059cff029338a2a604d8d_img.jpg b/marked/Rel-18/38_series/38455/26e334e61dd059cff029338a2a604d8d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c479585e1228052320d1c0e9a91a64e27f42fff --- /dev/null +++ b/marked/Rel-18/38_series/38455/26e334e61dd059cff029338a2a604d8d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f01313d0d314ce03fa999ae28e6a01e6e700113cb8fadebf7b7179156c62ba4 +size 15093 diff --git a/marked/Rel-18/38_series/38455/44c70af075e4d9bbc6fbe267a666b3b0_img.jpg b/marked/Rel-18/38_series/38455/44c70af075e4d9bbc6fbe267a666b3b0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23338053381e631139e7a0c4ae27e1e1e1bd6680 --- /dev/null +++ b/marked/Rel-18/38_series/38455/44c70af075e4d9bbc6fbe267a666b3b0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c241ee533859d3b8c7faa52fd9dcd890c2aa0808489d7ae116c668881cc9f28 +size 20583 diff --git a/marked/Rel-18/38_series/38455/4b87467ad9642943235f48f7d4b59449_img.jpg b/marked/Rel-18/38_series/38455/4b87467ad9642943235f48f7d4b59449_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..133b6ec7f32855143b3dcea647865263632e11d0 --- /dev/null +++ b/marked/Rel-18/38_series/38455/4b87467ad9642943235f48f7d4b59449_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43f47d096be3a5585daf70105f7083ea48e9d2339741c08e6724d97ff555a6c6 +size 18724 diff --git a/marked/Rel-18/38_series/38455/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg b/marked/Rel-18/38_series/38455/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..476344c11cc58277d9322f46b169c5679ee35aaf --- /dev/null +++ b/marked/Rel-18/38_series/38455/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9437e8c26bb83a67075d7cc3559f74bc8f3c5e6dae7913d1491e8d4f2b82bd01 +size 21600 diff --git a/marked/Rel-18/38_series/38455/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38455/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c9dba5f761c5e7afa1b610d728a591f794b121e --- /dev/null +++ b/marked/Rel-18/38_series/38455/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:443c72cfdbce9162c7757e658978b538f0e250aa601df1128d5e119e0abe2ce3 +size 9688 diff --git a/marked/Rel-18/38_series/38455/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38455/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd54f0518d6046d3b5ba60fbaffd74deac0806aa --- /dev/null +++ b/marked/Rel-18/38_series/38455/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a885fc6a7835254237d93f86667f9c687822ea4c10e67c0b1d93d13795e41566 +size 5803 diff --git a/marked/Rel-18/38_series/38455/718be1eb075833deb7a3b80729a06264_img.jpg b/marked/Rel-18/38_series/38455/718be1eb075833deb7a3b80729a06264_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57c637ff0728805b5e8338baf1527c055a87ba9b --- /dev/null +++ b/marked/Rel-18/38_series/38455/718be1eb075833deb7a3b80729a06264_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:467bee0b17cac46077d183bf17aeafbc4ad97f6b810c0b1756d29f13e9a2529b +size 16640 diff --git a/marked/Rel-18/38_series/38455/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/marked/Rel-18/38_series/38455/744acfe8d4e31bcf03f95714c2f6e567_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b465879fdfab1b6d91404e6b9be0989e99284d49 --- /dev/null +++ b/marked/Rel-18/38_series/38455/744acfe8d4e31bcf03f95714c2f6e567_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6d7c27e9aa14174dfdb97ef507c213dc813e40f74604822dab3d3ab9f6e885c +size 25302 diff --git a/marked/Rel-18/38_series/38455/75e4b78ee25f885d73120e3066a5253e_img.jpg b/marked/Rel-18/38_series/38455/75e4b78ee25f885d73120e3066a5253e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d999035d5f14defbf7260cf5cae40b84407d736d --- /dev/null +++ b/marked/Rel-18/38_series/38455/75e4b78ee25f885d73120e3066a5253e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0e1317ff9fd14fbe0482fde3cda43580f063d45d2f23be601385c1067f8dbc3 +size 25330 diff --git a/marked/Rel-18/38_series/38455/84e5b251aa38db522f76f5cc3afcb853_img.jpg b/marked/Rel-18/38_series/38455/84e5b251aa38db522f76f5cc3afcb853_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2172cd5cac9e3266440ea347d6e3b17388bb406 --- /dev/null +++ b/marked/Rel-18/38_series/38455/84e5b251aa38db522f76f5cc3afcb853_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06d551a29c3be3b5a6164ddb108f2732f07e77e642b02f1cd78e581f3ebc9ac9 +size 26172 diff --git a/marked/Rel-18/38_series/38455/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/Rel-18/38_series/38455/86b4670fc1a5a694821ee92b99c1209a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad6b33ac4d7046da1a80e1152b05ab13a1fa8b38 --- /dev/null +++ b/marked/Rel-18/38_series/38455/86b4670fc1a5a694821ee92b99c1209a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b593edc936573527ddbd40af39afda5521b7505d12a5dd42e9adc8c0442accd +size 16966 diff --git a/marked/Rel-18/38_series/38455/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg b/marked/Rel-18/38_series/38455/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..875e35fdf8dfe6a61e3061e9ac45deacfe299e78 --- /dev/null +++ b/marked/Rel-18/38_series/38455/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0909949e7eb9510cd169b6f3ae1289bd86f3c93216132c20248febfa317a8ff +size 17928 diff --git a/marked/Rel-18/38_series/38455/9870bf462aa0d916a16d14b5a100c60a_img.jpg b/marked/Rel-18/38_series/38455/9870bf462aa0d916a16d14b5a100c60a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca07f8a425e4d7601d19273249d9c9d5c0d8833d --- /dev/null +++ b/marked/Rel-18/38_series/38455/9870bf462aa0d916a16d14b5a100c60a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0b29c4d18d89a5c5430ff2d8dac91552b0ebdc34307964ca74dab7f82b27837 +size 17726 diff --git a/marked/Rel-18/38_series/38455/9b686adccf125267a013fa25721231a3_img.jpg b/marked/Rel-18/38_series/38455/9b686adccf125267a013fa25721231a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24a85999d4688a465839a56edf858c39314ef075 --- /dev/null +++ b/marked/Rel-18/38_series/38455/9b686adccf125267a013fa25721231a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2961e416b92ff624b22b9cf598fb25a39efdaf19d988d371c48e0edb12905ae7 +size 26004 diff --git a/marked/Rel-18/38_series/38455/9f862801bce82634d3b5a1e0a195a799_img.jpg b/marked/Rel-18/38_series/38455/9f862801bce82634d3b5a1e0a195a799_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..541329ca0fc017d38e581691ab3f5f65be6f8e8f --- /dev/null +++ b/marked/Rel-18/38_series/38455/9f862801bce82634d3b5a1e0a195a799_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:853b05783c38baee68f7aed1c53202e028e3af1f89185fd8c9cbb2a2a03fe439 +size 16229 diff --git a/marked/Rel-18/38_series/38455/a1890b9a9b85f13e67ed59bbad623659_img.jpg b/marked/Rel-18/38_series/38455/a1890b9a9b85f13e67ed59bbad623659_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b5267b756da033cb2d8ff87e0eb77939f4af4ec --- /dev/null +++ b/marked/Rel-18/38_series/38455/a1890b9a9b85f13e67ed59bbad623659_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:354607266e9ae497e62f3464a7311f6f5b56cd25fa2fcd4271a9c4fd57ea991b +size 10942 diff --git a/marked/Rel-18/38_series/38455/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/marked/Rel-18/38_series/38455/b51423b6c049f5b5fcde42e50b58f18b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f18fd0ddfeb42d885a6ec60b362001d71baa020c --- /dev/null +++ b/marked/Rel-18/38_series/38455/b51423b6c049f5b5fcde42e50b58f18b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd18fd34a37ec6a7e1238a5b98b3185f1799d1a42e1ed328319bdf0d36353e3e +size 11218 diff --git a/marked/Rel-18/38_series/38455/b576eed4f7d3f33c6853abd24100a0ac_img.jpg b/marked/Rel-18/38_series/38455/b576eed4f7d3f33c6853abd24100a0ac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ed372925ab930faf925e32506a537070ed90359 --- /dev/null +++ b/marked/Rel-18/38_series/38455/b576eed4f7d3f33c6853abd24100a0ac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:167891a0556c804ac7282b1a9b46b3e12275829934d885cbb22cd52cc4d744f8 +size 16475 diff --git a/marked/Rel-18/38_series/38455/b904ac2472cab80892d1e783e6230d6e_img.jpg b/marked/Rel-18/38_series/38455/b904ac2472cab80892d1e783e6230d6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0fd9fc17543fdf878bdbfd4111b930537d487aa4 --- /dev/null +++ b/marked/Rel-18/38_series/38455/b904ac2472cab80892d1e783e6230d6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc0863d4708a877cfd18bff075afa70b979a07d2dcb479c32955a6e80ee1a011 +size 16945 diff --git a/marked/Rel-18/38_series/38455/c8e5b3ef81948bb13d5c6c3c326799ea_img.jpg b/marked/Rel-18/38_series/38455/c8e5b3ef81948bb13d5c6c3c326799ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b01b19ba3fcc6bc6c6b465af35f49c43a048ea5d --- /dev/null +++ b/marked/Rel-18/38_series/38455/c8e5b3ef81948bb13d5c6c3c326799ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eddc2d8747dbcb45f94218a8a331cb6f2952f75b96068946f259e00a544e0d07 +size 27300 diff --git a/marked/Rel-18/38_series/38455/d5918cee231b536f20789a18d861fae3_img.jpg b/marked/Rel-18/38_series/38455/d5918cee231b536f20789a18d861fae3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10ba1f23f94fe0e54b7bce38961b66d48b147654 --- /dev/null +++ b/marked/Rel-18/38_series/38455/d5918cee231b536f20789a18d861fae3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5742b5ad6da8f72ca5f031cd30a51517a6a5d4358e2720b45ed5d176b0d597f1 +size 20527 diff --git a/marked/Rel-18/38_series/38455/e354b57563dae469c00b412b2abdf765_img.jpg b/marked/Rel-18/38_series/38455/e354b57563dae469c00b412b2abdf765_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bf1e54a108761e35d4c95d238835d1670590ab3 --- /dev/null +++ b/marked/Rel-18/38_series/38455/e354b57563dae469c00b412b2abdf765_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:610f8aaccfb3bc77b50197881ffba927279f0beb408dc17b0e6f88d17f2a980e +size 23690 diff --git a/marked/Rel-18/38_series/38455/e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg b/marked/Rel-18/38_series/38455/e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a527d40902bdfad53fca5d91c5a9e8a582db579 --- /dev/null +++ b/marked/Rel-18/38_series/38455/e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fdb2900338621a2e327743e4d1e5196e74d22e41f56bc167c9413befa9afa8c +size 25399 diff --git a/marked/Rel-18/38_series/38455/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/Rel-18/38_series/38455/e90987faabad6a6665cd8ed1151dc474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04eb7575c399be9f47567c78fbe5740fb6dcf5f4 --- /dev/null +++ b/marked/Rel-18/38_series/38455/e90987faabad6a6665cd8ed1151dc474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbb2181d7128d6c182e6212acc51c46b1aaa8360730880d8c4bcd8983accb6cf +size 18832 diff --git a/marked/Rel-18/38_series/38455/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg b/marked/Rel-18/38_series/38455/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42cbfc8f47f614c02609cf2e24be94656d9eb96a --- /dev/null +++ b/marked/Rel-18/38_series/38455/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5214d4d222da69fb66364e8cca43b9270371a8bf8877e64fc22a9c4f72bff13 +size 23484 diff --git a/marked/Rel-18/38_series/38455/raw.md b/marked/Rel-18/38_series/38455/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0b92e6f91de44060cee5fad49e1bf211143da91f --- /dev/null +++ b/marked/Rel-18/38_series/38455/raw.md @@ -0,0 +1,11219 @@ + + +# 3GPP TS 38.455 V18.0.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NR Positioning Protocol A (NRPPa) (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. Below the 'P' is a small 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 + + +# --- Contents + +| | | +|---------------------------------------------------|----| +| Foreword..... | 8 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions, symbols and abbreviations..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Symbols..... | 10 | +| 3.3 Abbreviations..... | 10 | +| 4 General..... | 11 | +| 4.1 Procedure specification principles..... | 11 | +| 4.2 Forwards and backwards compatibility..... | 11 | +| 4.3 Specification notations..... | 11 | +| 5 NRPPa services..... | 12 | +| 5.1 NRPPa procedure modules..... | 12 | +| 5.2 Parallel transactions..... | 12 | +| 6 Services expected from lower layer..... | 12 | +| 7 Functions of NRPPa..... | 12 | +| 8 NRPPa procedures..... | 13 | +| 8.1 Elementary procedures..... | 13 | +| 8.2 Location Information Transfer Procedures..... | 14 | + +# **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 | E-CID Measurement Initiation..... | 14 | +| 8.2.1.1 | General..... | 14 | +| 8.2.1.2 | Successful Operation..... | 15 | +| 8.2.1.3 | Unsuccessful Operation..... | 15 | +| 8.2.1.4 | Abnormal Conditions..... | 16 | +| 8.2.2 | E-CID Measurement Failure Indication..... | 16 | +| 8.2.2.1 | General..... | 16 | +| 8.2.2.2 | Successful Operation..... | 16 | +| 8.2.2.3 | Unsuccessful Operation..... | 16 | +| 8.2.2.4 | Abnormal Conditions..... | 16 | +| 8.2.3 | E-CID Measurement Report..... | 16 | +| 8.2.3.1 | General..... | 16 | +| 8.2.3.2 | Successful Operation..... | 16 | +| 8.2.3.3 | Unsuccessful Operation..... | 17 | +| 8.2.3.4 | Abnormal Conditions..... | 17 | +| 8.2.4 | E-CID Measurement Termination..... | 17 | +| 8.2.4.1 | General..... | 17 | +| 8.2.4.2 | Successful Operation..... | 17 | +| 8.2.4.3 | Unsuccessful Operation..... | 17 | +| 8.2.4.4 | Abnormal Conditions..... | 17 | +| 8.2.5 | OTDOA Information Exchange..... | 18 | +| 8.2.5.1 | General..... | 18 | +| 8.2.5.2 | Successful Operation..... | 18 | +| 8.2.5.3 | Unsuccessful Operation..... | 18 | +| 8.2.5.4 | Abnormal Conditions..... | 18 | +| 8.2.6 | Positioning Information Exchange..... | 18 | +| 8.2.6.1 | General..... | 18 | +| 8.2.6.2 | Successful Operation..... | 19 | +| 8.2.6.3 | Unsuccessful Operation..... | 19 | +| 8.2.6.4 | Abnormal Conditions..... | 20 | + +| | | | +|----------|-------------------------------------|----| +| 8.2.7 | Positioning Information Update..... | 20 | +| 8.2.7.1 | General..... | 20 | +| 8.2.7.2 | Successful Operation..... | 20 | +| 8.2.7.3 | Unsuccessful Operation..... | 20 | +| 8.2.7.4 | Abnormal Conditions..... | 20 | +| 8.2.8 | TRP Information Exchange..... | 21 | +| 8.2.8.1 | General..... | 21 | +| 8.2.8.2 | Successful Operation..... | 21 | +| 8.2.8.3 | Unsuccessful Operation..... | 22 | +| 8.2.8.4 | Abnormal Conditions..... | 22 | +| 8.2.9 | Positioning Activation..... | 22 | +| 8.2.9.1 | General..... | 22 | +| 8.2.9.2 | Successful Operation..... | 22 | +| 8.2.9.3 | Unsuccessful Operation..... | 23 | +| 8.2.9.4 | Abnormal Conditions..... | 23 | +| 8.2.10 | Positioning Deactivation..... | 23 | +| 8.2.10.1 | General..... | 23 | +| 8.2.10.2 | Successful Operation..... | 23 | +| 8.2.10.3 | Unsuccessful Operation..... | 23 | +| 8.2.10.4 | Abnormal Conditions..... | 24 | +| 8.2.11 | PRS Configuration Exchange..... | 24 | +| 8.2.11.1 | General..... | 24 | +| 8.2.11.2 | Successful Operation..... | 24 | +| 8.2.11.3 | Unsuccessful Operation..... | 24 | +| 8.2.11.4 | Abnormal Conditions..... | 24 | +| 8.2.12 | Measurement Preconfiguration..... | 25 | +| 8.2.12.1 | General..... | 25 | +| 8.2.12.2 | Successful Operation..... | 25 | +| 8.2.12.3 | Unsuccessful Operation..... | 25 | +| 8.2.12.4 | Abnormal Conditions..... | 25 | + +| | | | +|----------|-------------------------------------------------|----| +| 8.2.13 | Measurement Activation..... | 25 | +| 8.2.13.1 | General..... | 25 | +| 8.2.13.2 | Successful Operation..... | 26 | +| 8.2.13.3 | Unsuccessful Operation..... | 26 | +| 8.2.13.4 | Abnormal Conditions..... | 26 | +| 8.3 | Management Procedures..... | 26 | +| 8.3.1 | Error Indication..... | 26 | +| 8.3.1.1 | General..... | 26 | +| 8.3.1.2 | Successful Operation..... | 26 | +| 8.3.1.3 | Abnormal Conditions..... | 27 | +| 8.4 | Assistance Information Transfer Procedures..... | 27 | +| 8.4.1 | Assistance Information Control..... | 27 | +| 8.4.1.1 | General..... | 27 | +| 8.4.1.2 | Successful Operation..... | 27 | +| 8.4.1.3 | Abnormal Conditions..... | 28 | +| 8.4.2 | Assistance Information Feedback..... | 28 | +| 8.4.2.1 | General..... | 28 | +| 8.4.2.2 | Successful Operation..... | 28 | +| 8.4.2.3 | Abnormal Conditions..... | 28 | +| 8.5 | Measurement Information Transfer..... | 28 | +| 8.5.1 | Measurement..... | 28 | +| 8.5.1.1 | General..... | 28 | +| 8.5.1.2 | Successful Operation..... | 29 | +| 8.5.1.3 | Unsuccessful Operation..... | 30 | +| 8.5.1.4 | Abnormal Conditions..... | 30 | +| 8.5.2 | Measurement Report..... | 30 | +| 8.5.2.1 | General..... | 30 | +| 8.5.2.2 | Successful Operation..... | 30 | +| 8.5.2.3 | Abnormal Conditions..... | 31 | +| 8.5.3 | Measurement Update..... | 31 | + +| | | | +|----------|------------------------------------------------------------|----| +| 8.5.3.1 | General..... | 31 | +| 8.5.3.2 | Successful Operation..... | 31 | +| 8.5.3.3 | Unsuccessful Operation..... | 31 | +| 8.5.3.4 | Abnormal Conditions..... | 31 | +| 8.5.4 | Measurement Abort..... | 32 | +| 8.5.4.1 | General..... | 32 | +| 8.5.4.2 | Successful Operation..... | 32 | +| 8.5.4.3 | Unsuccessful Operation..... | 32 | +| 8.5.4.4 | Abnormal Conditions..... | 32 | +| 8.5.5 | Measurement Failure Indication..... | 32 | +| 8.5.5.1 | General..... | 32 | +| 8.5.5.2 | Successful Operation..... | 32 | +| 8.5.5.3 | Abnormal Conditions..... | 33 | +| 9 | Elements for NRPPa Communication..... | 33 | +| 9.0 | General..... | 33 | +| 9.1 | Message Functional Definition and Content..... | 33 | +| 9.1.1 | Messages for Location Information Transfer Procedures..... | 33 | +| 9.1.1.1 | E-CID MEASUREMENT INITIATION REQUEST..... | 33 | +| 9.1.1.2 | E-CID MEASUREMENT INITIATION RESPONSE..... | 34 | +| 9.1.1.3 | E-CID MEASUREMENT INITIATION FAILURE..... | 35 | +| 9.1.1.4 | E-CID MEASUREMENT FAILURE INDICATION..... | 35 | +| 9.1.1.5 | E-CID MEASUREMENT REPORT..... | 35 | +| 9.1.1.6 | E-CID MEASUREMENT TERMINATION COMMAND..... | 36 | +| 9.1.1.7 | OTDOA INFORMATION REQUEST..... | 36 | +| 9.1.1.8 | OTDOA INFORMATION RESPONSE..... | 37 | +| 9.1.1.9 | OTDOA INFORMATION FAILURE..... | 37 | +| 9.1.1.10 | POSITIONING INFORMATION REQUEST..... | 37 | +| 9.1.1.11 | POSITIONING INFORMATION RESPONSE..... | 38 | +| 9.1.1.12 | POSITIONING INFORMATION FAILURE..... | 38 | +| 9.1.1.13 | POSITIONING INFORMATION UPDATE..... | 39 | + +| | | | +|----------|---------------------------------------------------------------|----| +| 9.1.1.14 | TRP INFORMATION REQUEST..... | 39 | +| 9.1.1.15 | TRP INFORMATION RESPONSE..... | 40 | +| 9.1.1.16 | TRP INFORMATION FAILURE..... | 40 | +| 9.1.1.17 | POSITIONING ACTIVATION REQUEST..... | 40 | +| 9.1.1.18 | POSITIONING ACTIVATION RESPONSE..... | 41 | +| 9.1.1.19 | POSITIONING ACTIVATION FAILURE..... | 41 | +| 9.1.1.20 | POSITIONING DEACTIVATION..... | 41 | +| 9.1.1.21 | PRS CONFIGURATION REQUEST..... | 42 | +| 9.1.1.22 | PRS CONFIGURATION RESPONSE..... | 42 | +| 9.1.1.23 | PRS CONFIGURATION FAILURE..... | 43 | +| 9.1.1.24 | MEASUREMENT PRECONFIGURATION REQUIRED..... | 43 | +| 9.1.1.25 | MEASUREMENT PRECONFIGURATION CONFIRM..... | 43 | +| 9.1.1.26 | MEASUREMENT PRECONFIGURATION REFUSE..... | 44 | +| 9.1.1.27 | MEASUREMENT ACTIVATION..... | 44 | +| 9.1.2 | Messages for Management Procedures..... | 45 | +| 9.1.2.1 | ERROR INDICATION..... | 45 | +| 9.1.3 | Messages for Assistance Information Transfer Procedures..... | 45 | +| 9.1.3.1 | ASSISTANCE INFORMATION CONTROL..... | 45 | +| 9.1.3.2 | ASSISTANCE INFORMATION FEEDBACK..... | 45 | +| 9.1.4 | Messages for Measurement Information Transfer Procedures..... | 46 | +| 9.1.4.1 | MEASUREMENT REQUEST..... | 46 | +| 9.1.4.2 | MEASUREMENT RESPONSE..... | 48 | +| 9.1.4.3 | MEASUREMENT FAILURE..... | 48 | +| 9.1.4.4 | MEASUREMENT REPORT..... | 48 | +| 9.1.4.5 | MEASUREMENT UPDATE..... | 49 | +| 9.1.4.6 | MEASUREMENT ABORT..... | 50 | +| 9.1.4.7 | MEASUREMENT FAILURE INDICATION..... | 50 | +| 9.2 | Information Element definitions..... | 50 | +| 9.2.0 | General..... | 50 | +| 9.2.1 | Cause..... | 50 | + +| | | | +|--------|-------------------------------------------------|----| +| 9.2.2 | Criticality Diagnostics..... | 52 | +| 9.2.3 | Message Type..... | 52 | +| 9.2.4 | NRPPa Transaction ID..... | 53 | +| 9.2.5 | E-CID Measurement Result..... | 53 | +| 9.2.6 | NG-RAN CGI..... | 56 | +| 9.2.7 | CGI EUTRA..... | 56 | +| 9.2.8 | PLMN Identity..... | 57 | +| 9.2.9 | NR CGI..... | 57 | +| 9.2.10 | NG-RAN Access Point Position..... | 57 | +| 9.2.11 | TAC..... | 58 | +| 9.2.12 | Cell Portion ID..... | 58 | +| 9.2.13 | Other-RAT Measurement Result..... | 58 | +| 9.2.14 | WLAN Measurement Result..... | 60 | +| 9.2.15 | OTDOA Cell Information..... | 61 | +| 9.2.16 | PRS Muting Configuration EUTRA..... | 63 | +| 9.2.17 | PRS Frequency Hopping Configuration EUTRA..... | 63 | +| 9.2.18 | TDD Configuration EUTRA..... | 64 | +| 9.2.19 | Assistance Information..... | 64 | +| 9.2.20 | PosSIB Segments..... | 64 | +| 9.2.21 | Assistance Information Meta Data..... | 65 | +| 9.2.22 | Positioning SIB Type..... | 65 | +| 9.2.23 | Assistance Information Failure List..... | 66 | +| 9.2.24 | TRP ID..... | 66 | +| 9.2.25 | TRP Information..... | 66 | +| 9.2.26 | Search Window Information..... | 67 | +| 9.2.27 | Requested SRS Transmission Characteristics..... | 68 | +| 9.2.28 | SRS Configuration..... | 69 | +| 9.2.29 | SRS Resource..... | 71 | +| 9.2.30 | Positioning SRS Resource..... | 72 | +| 9.2.31 | SRS Resource Set..... | 73 | + +| | | | +|--------|----------------------------------------------------|----| +| 9.2.32 | Positioning SRS Resource Set..... | 74 | +| 9.2.33 | SRS Resource Set ID..... | 74 | +| 9.2.34 | Spatial Relation Information..... | 74 | +| 9.2.35 | SRS Resource Trigger..... | 75 | +| 9.2.36 | Relative Time 1900..... | 75 | +| 9.2.37 | TRP Measurement Result..... | 76 | +| 9.2.38 | UL Angle of Arrival..... | 76 | +| 9.2.39 | UL RTOA Measurement..... | 76 | +| 9.2.40 | gNB Rx-Tx Time Difference..... | 77 | +| 9.2.41 | Additional Path List..... | 77 | +| 9.2.42 | Time Stamp..... | 78 | +| 9.2.43 | Measurement Quality..... | 78 | +| 9.2.44 | PRS Configuration..... | 79 | +| 9.2.45 | Spatial Direction Information..... | 80 | +| 9.2.46 | Geographical Coordinates..... | 81 | +| 9.2.47 | DL-PRS Resource Coordinates..... | 81 | +| 9.2.48 | Relative Geodetic Location..... | 82 | +| 9.2.49 | NG-RAN High Accuracy Access Point Position..... | 82 | +| 9.2.50 | Relative Cartesian Location..... | 83 | +| 9.2.51 | Reference Point..... | 83 | +| 9.2.52 | Location Uncertainty..... | 84 | +| 9.2.53 | Pathloss Reference Information..... | 84 | +| 9.2.54 | SSB Information..... | 84 | +| 9.2.55 | SSB Time/Frequency Configuration..... | 85 | +| 9.2.56 | DL-PRS Muting Pattern..... | 85 | +| 9.2.57 | Measurement Beam Information..... | 85 | +| 9.2.58 | NR-PRS Beam Information..... | 86 | +| 9.2.59 | Positioning Broadcast Cells..... | 86 | +| 9.2.60 | Spatial Relation Information per SRS Resource..... | 87 | +| 9.2.61 | Requested DL PRS Transmission Characteristics..... | 87 | + +| | | | +|--------|-------------------------------------------------------------------|-----| +| 9.2.62 | Requested DL-PRS Resource List..... | 88 | +| 9.2.63 | Start Time and Duration..... | 88 | +| 9.2.64 | PRS Transmission Off Information..... | 89 | +| 9.2.65 | On-demand PRS TRP Information..... | 89 | +| 9.2.66 | UL-AoA assistance information..... | 91 | +| 9.2.67 | Z-AoA..... | 91 | +| 9.2.68 | Response Time..... | 92 | +| 9.2.69 | LCS to GCS Translation..... | 92 | +| 9.2.70 | UE Reporting Information..... | 92 | +| 9.2.71 | Multiple UL-AoA..... | 92 | +| 9.2.72 | UL SRS-RSRPP..... | 93 | +| 9.2.73 | SRS Resource type..... | 93 | +| 9.2.74 | Extended Additional Path List..... | 93 | +| 9.2.75 | ARP ID..... | 93 | +| 9.2.76 | ARP Location Information..... | 94 | +| 9.2.77 | LoS/NLoS Information..... | 94 | +| 9.2.78 | UE Tx TEG Association List..... | 94 | +| 9.2.79 | TRP Tx TEG Association..... | 95 | +| 9.2.80 | TRP TEG Information..... | 95 | +| 9.2.81 | Measurement Characteristics Request Indicator..... | 96 | +| 9.2.82 | TRP Beam Antenna Information..... | 96 | +| 9.2.83 | TRP Beam Antenna Angles..... | 97 | +| 9.2.84 | Timing Error Margin..... | 98 | +| 9.2.85 | TRP Rx TEG Information..... | 98 | +| 9.2.86 | TRP Tx TEG Information..... | 98 | +| 9.2.87 | TRP RxTx TEG Information..... | 99 | +| 9.2.88 | Mobile TRP Location Information..... | 99 | +| 9.3 | Message and Information Element Abstract Syntax (with ASN.1)..... | 100 | +| 9.3.1 | General..... | 100 | +| 9.3.2 | Usage of Private Message Mechanism for Non-standard Use..... | 100 | + +| | | | +|-------------------------------|------------------------------------------------------------------|------------| +| 9.3.3 | Elementary Procedure Definitions..... | 100 | +| 9.3.4 | PDU Definitions..... | 107 | +| 9.3.5 | Information Element definitions..... | 125 | +| 9.3.6 | Common definitions..... | 189 | +| 9.3.7 | Constant definitions..... | 190 | +| 9.3.8 | Container definitions..... | 195 | +| 9.4 | Message transfer syntax..... | 198 | +| 9.5 | Timers..... | 198 | +| 10 | Handling of unknown, unforeseen and erroneous protocol data..... | 198 | +| Annex A (informative): | Change history..... | 199 | + +# --- 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 control plane radio network layer signalling procedures between a NG-RAN node and the LMF. NRPPa supports the concerned functions by signalling procedures defined 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 38.413: "NG-RAN; NG Application Protocol (NGAP)". +- [3] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2". +- [4] Void. +- [5] 3GPP TR 25.921 (version 7.0.0): "Guidelines and principles for protocol description and error handling". +- [6] ITU-T Recommendation X.691 (2002-07): "Information technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER) ". +- [7] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Base Station (BS) radio transmission and reception". +- [8] 3GPP TS 23.032: "Technical Specification Group Services and System Aspects; Universal Geographical Area Description (GAD)". +- [9] 3GPP TS 36.133: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management". +- [10] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Physical Channels and Modulation". +- [11] IEEE Std 802.11™-2012, IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area network. +- [12] 3GPP TS 36.455: " Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Positioning Protocol A (LPPa)". +- [13] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification". +- [14] 3GPP TS 37.355: " Technical Specification Group Radio Access Network; LTE Positioning Protocol (LPP)". +- [15] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification". + +- [16] 3GPP TS 38.133: "NR; Requirements for support of radio resource management". +- [17] 3GPP TS 36.214: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer (PHY); Measurements". +- [18] 3GPP TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN". +- [19] 3GPP TS 38.215: "NR; Physical layer (PHY); Measurements". +- [20] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2". +- [21] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces". + +# --- 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]. + +**gNB:** as defined in TS 38.300 [3]. + +**NG-RAN node:** as defined in TS 38.300 [3]. + +**ng-eNB:** as defined in TS 38.300 [3]. + +**Mobile IAB-MT:** as defined in TS 38.300 [3]. + +## 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]. + +| | | +|---------|----------------------------------------------------------------------------------------------| +| ARP | Antenna Reference Point | +| BDS | BeiDou Navigation Satellite System | +| CG-SDT | Configured Grant Small Data Transmission | +| CID | Cell-ID (positioning method) | +| DL-PRS | Downlink Positioning Reference Signal | +| E-CID | Enhanced Cell-ID (positioning method) | +| EGNOS | European Geostationary Navigation Overlay Service | +| 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 | + +| | | +|-------------|------------------------------------------------| +| LMF | Location Management Function | +| LPP | LTE Positioning Protocol | +| MSAS | Multi-functional Satellite Augmentation System | +| NavIC | NAVigation with Indian Constellation | +| NRPPa | NR Positioning Protocol A | +| OTDOA | Observed Time Difference of Arrival | +| posSIB | Positioning SIB | +| PRS | Positioning Reference Signal (for E-UTRA) | +| QZSS | Quasi-Zenith Satellite System | +| RSRP | Reference Signal Received Power | +| RSSI | Received Signal Strength Indicator | +| RSTD | Reference Signal Time Difference | +| SBAS | Space Based Augmentation System | +| SRS | Sounding Reference Signal | +| TEG | Timing Error group | +| TRP | Transmission-Reception Point | +| UE | User Equipment | +| UL-AoA | Uplink Angle of Arrival | +| UL-RTOA | Uplink Relative Time of Arrival | +| UL-SRS | Uplink Sounding Reference Signal | +| UL SRS-RSRP | UL SRS reference signal received path power | +| WAAS | Wide Area Augmentation System | +| Z-AoA | Zenith Angles of Arrival | + +# 4 General + +## 4.1 Procedure specification principles + +The principle for specifying the procedure logic is to specify the functional behaviour of the terminating NG-RAN Node exactly and completely. Any rule that specifies the behaviour of the originating NG-RAN 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 initiating 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 section 10. + +## 4.2 Forwards and backwards compatibility + +The forwards and backwards compatibility of the protocol is assured by a 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. ERROR INDICATION 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. Cause 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 sub clause 9.2 enclosed by quotation marks, e.g. "Value". | + +# --- 5 NRPPa services + +The present clause describes the services an NG -RAN Node offers to the LMF. + +## 5.1 NRPPa procedure modules + +The procedures are divided into two modules as follows: + +1. NRPPa Location Information Transfer Procedures; +2. NRPPa Management Procedures; + +The NRPPa Location Information Transfer Procedures module contains procedures used to handle the transfer of positioning related information between NG-RAN Node and LMF. + +The Management Procedures module contains procedures that are not related specifically to positioning, i.e. error handling. + +## 5.2 Parallel transactions + +Unless explicitly indicated in the procedure specification, at any instance in time one protocol peer may have more than one ongoing NRPPa procedure. + +# --- 6 Services expected from lower layer + +Within 5G RAN, NRPPa protocol uses the services provided by the NGAP protocol. An NRPPa message is carried inside an NGAP message. + +NGAP signalling is described in TS 38.413 [2]. + +# --- 7 Functions of NRPPa + +The NRPPa protocol provides the following functions: + +- E-CID Location Information Transfer. This function allows the NG-RAN node to exchange location information with LMF for the purpose of E-CID positioning and NR E-CID positioning. +- OTDOA Information Transfer. This function allows the NG-RAN node to exchange information with the LMF for the purpose of OTDOA positioning. +- Reporting of General Error Situations. This function allows reporting of general error situations, for which function specific error messages have not been defined. +- Assistance Information Transfer. This function allows the LMF to exchange information with the NG-RAN node for the purpose of assistance information broadcasting. +- Positioning Information Transfer. This function allows the NG-RAN node to exchange positioning information with the LMF for the purpose of positioning. +- Measurement Information Transfer. This function allows the LMF to exchange measurement information with the NG-RAN node for the purpose of positioning. +- TRP Information Transfer. This function allows an LMF to obtain TRP related information from an NG-RAN node. +- PRS Information Transfer. This function allows the LMF to exchange PRS related information with the NG-RAN node. +- Measurement Preconfiguration Information Transfer. This function allows the LMF to request the NG-RAN node to preconfigure and activate measurement gap and/or PRS processing window. + +The mapping between the above functions and NRPPa EPs is shown in the table below. + +**Table 7-1: Mapping between NRPPa functions and NRPPa EPs** + +| Function | Elementary Procedure(s) | +|---------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| E-CID Location Information Transfer | a) E-CID Measurement Initiation
b) E-CID Measurement Failure Indication
c) E-CID Measurement Report
d) E-CID Measurement Termination | +| OTDOA Information Transfer | OTDOA Information Exchange | +| Assistance Information Transfer | a) Assistance Information Control
b) Assistance Information Feedback | +| Reporting of General Error Situations | Error Indication | +| Positioning Information Transfer | a) Positioning Information Exchange
b) Positioning Information Update
c) Positioning Activation
d) Positioning Deactivation | +| TRP Information Transfer | TRP Information Exchange | +| Measurement Information Transfer | a) Measurement
b) Measurement Update
c) Measurement Report
d) Measurement Abort
e) Measurement Failure Indication | +| PRS Information Transfer | PRS Configuration Exchange | +| Measurement Preconfiguration Information Transfer | Measurement Preconfiguration
Measurement Activation | + +# --- 8 NRPPa procedures + +## 8.1 Elementary procedures + +In the following tables, all EPs are divided into Class 1 and Class 2 EPs. + +**Table 8.1-1: Class 1 Elementary Procedures** + +| Elementary Procedure | Initiating Message | Successful Outcome | Unsuccessful Outcome | +|----------------------------------|---------------------------------------|---------------------------------------|--------------------------------------| +| | | Response message | Response message | +| E-CID Measurement Initiation | E-CID MEASUREMENT INITIATION REQUEST | E-CID MEASUREMENT INITIATION RESPONSE | E-CID MEASUREMENT INITIATION FAILURE | +| OTDOA Information Exchange | OTDOA INFORMATION REQUEST | OTDOA INFORMATION RESPONSE | OTDOA INFORMATION FAILURE | +| Positioning Information Exchange | POSITIONING INFORMATION REQUEST | POSITIONING INFORMATION RESPONSE | POSITIONING INFORMATION FAILURE | +| TRP Information Exchange | TRP INFORMATION REQUEST | TRP INFORMATION RESPONSE | TRP INFORMATION FAILURE | +| Measurement | MEASUREMENT REQUEST | MEASUREMENT RESPONSE | MEASUREMENT FAILURE | +| Positioning Activation | POSITIONING ACTIVATION REQUEST | POSITIONING ACTIVATION RESPONSE | POSITIONING ACTIVATION FAILURE | +| PRS Configuration Exchange | PRS CONFIGURATION REQUEST | PRS CONFIGURATION RESPONSE | PRS CONFIGURATION FAILURE | +| Measurement Preconfiguration | MEASUREMENT PRECONFIGURATION REQUIRED | MEASUREMENT PRECONFIGURATION CONFIRM | MEASUREMENT PRECONFIGURATION REFUSE | + +**Table 8.1-2: Class 2 Elementary Procedures** + +| Elementary Procedure | Initiating Message | +|--------------------------------------|---------------------------------------| +| E-CID Measurement Failure Indication | E-CID MEASUREMENT FAILURE INDICATION | +| E-CID Measurement Report | E-CID MEASUREMENT REPORT | +| E-CID Measurement Termination | E-CID MEASUREMENT TERMINATION COMMAND | +| Error Indication | ERROR INDICATION | +| Assistance Information Control | ASSISTANCE INFORMATION CONTROL | +| Assistance Information Feedback | ASSISTANCE INFORMATION FEEDBACK | +| Positioning Information Update | POSITIONING INFORMATION UPDATE | +| Measurement Report | MEASUREMENT REPORT | +| Measurement Update | MEASUREMENT UPDATE | +| Measurement Abort | MEASUREMENT ABORT | +| Measurement Failure Indication | MEASUREMENT FAILURE INDICATION | +| Positioning Deactivation | POSITIONING DEACTIVATION | +| Measurement Activation | MEASUREMENT ACTIVATION | + +## 8.2 Location Information Transfer Procedures + +### 8.2.1 E-CID Measurement Initiation + +#### 8.2.1.1 General + +The purpose of E-CID Measurement Initiation procedure is to allow the LMF to request the NG-RAN node to report E-CID measurements used by LMF to compute the location of the UE. + +#### 8.2.1.2 Successful Operation + +![Sequence diagram of E-CID Measurement Initiation procedure, successful operation](75e4b78ee25f885d73120e3066a5253e_img.jpg) + +``` +sequenceDiagram + participant NG-RAN Node + participant LMF + Note left of NG-RAN Node: + LMF->>NG-RAN Node: E-CID MEASUREMENT INITIATION REQUEST + NG-RAN Node-->>LMF: E-CID MEASUREMENT INITIATION RESPONSE + Note right of LMF: +``` + +The diagram illustrates the successful operation of the E-CID Measurement Initiation procedure. It shows two participants: NG-RAN Node and LMF. The LMF sends an E-CID MEASUREMENT INITIATION REQUEST message to the NG-RAN Node. The NG-RAN Node responds with an E-CID MEASUREMENT INITIATION RESPONSE message. The messages are represented by horizontal arrows between the two entities, with the request arrow pointing from LMF to NG-RAN Node and the response arrow pointing from NG-RAN Node to LMF. + +Sequence diagram of E-CID Measurement Initiation procedure, successful operation + +**Figure 8.2.1.2-1: E-CID Measurement Initiation procedure, successful operation** + +The LMF initiates the procedure by sending an E-CID MEASUREMENT INITIATION REQUEST message. If the NG-RAN node is able to initiate the requested E-CID measurements, it shall reply with the E-CID MEASUREMENT INITIATION RESPONSE message. + +The *Measured Results* IE shall be included in the *E-CID Measurement Result* IE of the E-CID MEASUREMENT INITIATION RESPONSE message when measurement results other than the "Cell-ID" have been requested. + +If the *Report Characteristics* IE is set to "OnDemand", the NG-RAN node shall return the result of the measurement in the E-CID MEASUREMENT INITIATION RESPONSE message including, if available, the *NG-RAN Access Point Position* IE or the *Geographical Coordinates* IE in the *E-CID Measurement Result* IE, and the LMF shall consider that the E-CID measurements for the UE has been terminated by the NG-RAN node. If available, the NG-RAN node shall include the *Cell Portion ID* IE in the E-CID MEASUREMENT INITIATION RESPONSE message. Upon reception of the *Cell Portion ID* IE, the LMF may use the value as the cell portion for the measurement. If the *Report Characteristics* IE is set to "OnDemand" and the *Inter-RAT Measurement Quantities* IE is included in the E-CID MEASUREMENT INITIATION REQUEST message, the NG-RAN node shall, if supported, provide the corresponding measurements, if available in the NG-RAN node, in the *Inter-RAT Measurement Result* IE in E-CID MEASUREMENT INITIATION RESPONSE message. If the *Report Characteristics* IE is set to "OnDemand" and the *WLAN Measurement Quantities* IE is included in the E-CID MEASUREMENT INITIATION REQUEST message, the NG-RAN node shall, if supported, provide the corresponding measurements, if available in the NG-RAN node, in the *WLAN Measurement Result* IE in E-CID MEASUREMENT INITIATION RESPONSE message. + +If the *Report Characteristics* IE is set to "Periodic", the NG-RAN node shall initiate the requested measurements and shall reply with the E-CID MEASUREMENT INITIATION RESPONSE message without including either the *E-CID Measurement Result* IE or the *Cell Portion ID* IE in this message. The NG-RAN node shall then periodically initiate the E-CID Measurement Report procedure for the measurements, with the requested reporting periodicity. + +#### 8.2.1.3 Unsuccessful Operation + +![Sequence diagram for E-CID Measurement Initiation procedure, unsuccessful operation](09955ff8214ffb6947951fc0f60eb6ab_img.jpg) + +``` +sequenceDiagram + participant LMF + participant NG-RAN Node + Note left of NG-RAN Node: + LMF->>NG-RAN Node: E-CID MEASUREMENT INITIATION REQUEST + Note right of NG-RAN Node: + NG-RAN Node-->>LMF: E-CID MEASUREMENT INITIATION FAILURE + Note right of LMF: +``` + +The diagram shows a sequence of messages between an LMF and an NG-RAN Node. The LMF sends an 'E-CID MEASUREMENT INITIATION REQUEST' to the NG-RAN Node. The NG-RAN Node responds with an 'E-CID MEASUREMENT INITIATION FAILURE' message. Both entities are represented by boxes with lifelines extending downwards, and the messages are shown as horizontal arrows between them. + +Sequence diagram for E-CID Measurement Initiation procedure, unsuccessful operation + +**Figure 8.2.1.3-1: E-CID Measurement Initiation procedure, unsuccessful operation** + +If the NG-RAN node is not able to initiate at least one of the requested E-CID measurements, the NG-RAN node shall respond with an E-CID MEASUREMENT INITIATION FAILURE message. + +#### 8.2.1.4 Abnormal Conditions + +Void. + +### 8.2.2 E-CID Measurement Failure Indication + +#### 8.2.2.1 General + +The purpose of the E-CID Measurement Failure Indication procedure is for the NG-RAN node to notify the LMF that the E-CID measurements previously requested with the E-CID Measurement Initiation procedure can no longer be reported. + +#### 8.2.2.2 Successful Operation + +![Sequence diagram for E-CID Measurement Failure Indication, successful operation](8ed7f57cc317f6574bec781d01ae6ad2_img.jpg) + +``` +sequenceDiagram + participant LMF + participant NG-RAN Node + Note left of NG-RAN Node: + NG-RAN Node->>LMF: E-CID MEASUREMENT FAILURE INDICATION + Note right of LMF: +``` + +The diagram shows a sequence of messages between an NG-RAN Node and an LMF. The NG-RAN Node sends an 'E-CID MEASUREMENT FAILURE INDICATION' message to the LMF. Both entities are represented by boxes with lifelines extending downwards, and the message is shown as a horizontal arrow from the NG-RAN Node to the LMF. + +Sequence diagram for E-CID Measurement Failure Indication, successful operation + +**Figure 8.2.2.2-1: E-CID Measurement Failure Indication, successful operation** + +Upon reception of the E-CID MEASUREMENT FAILURE INDICATION message, the LMF shall consider that the E-CID measurements for the UE have been terminated by the NG-RAN node. + +#### 8.2.2.3 Unsuccessful Operation + +Not applicable. + +#### 8.2.2.4 Abnormal Conditions + +Void. + +### 8.2.3 E-CID Measurement Report + +#### 8.2.3.1 General + +The purpose of E-CID Measurement Report procedure is for the NG-RAN node to provide the E-CID measurements for the UE to the LMF. + +#### 8.2.3.2 Successful Operation + +![Sequence diagram showing the E-CID MEASUREMENT REPORT procedure. An NG-RAN Node sends a message labeled 'E-CID MEASUREMENT REPORT' to an LMF. Both entities are represented by boxes with vertical lines extending downwards to horizontal bars representing lifelines.](86b4670fc1a5a694821ee92b99c1209a_img.jpg) + +``` +sequenceDiagram + participant NG-RAN Node + participant LMF + Note left of NG-RAN Node: + NG-RAN Node->>LMF: E-CID MEASUREMENT REPORT + Note right of LMF: +``` + +Sequence diagram showing the E-CID MEASUREMENT REPORT procedure. An NG-RAN Node sends a message labeled 'E-CID MEASUREMENT REPORT' to an LMF. Both entities are represented by boxes with vertical lines extending downwards to horizontal bars representing lifelines. + +**Figure 8.2.3.2-1: E-CID Measurement Report procedure, successful operation** + +The NG-RAN node initiates the procedure by sending an E-CID MEASUREMENT REPORT message. The E-CID MEASUREMENT REPORT message contains the E-CID measurement results according to the measurement configuration in the respective E-CID MEASUREMENT INITIATION REQUEST message. + +The *Measured Results* IE shall be included in the *E-CID Measurement Result* IE of the E-CID MEASUREMENT REPORT message when measurement results other than the "Cell-ID" have been requested. + +If available, the NG-RAN node shall include the *NG-RAN Access Point Position* IE or the *Geographical Coordinates* IE which is the configured estimated serving antenna position in the *E-CID Measurement Result* IE within the E-CID MEASUREMENT REPORT message. Upon reception of this *NG-RAN Access Point Position* IE, the LMF may use the value as the geographical position of the NG-RAN access point. + +If available, the NG-RAN node shall include the *Cell Portion ID* IE in the E-CID MEASUREMENT REPORT message. Upon reception of the *Cell Portion ID* IE, the LMF may use the value as the cell portion for the measurement. + +If available, the NG-RAN node shall include the *Mobile Access Point Location Information* IE in the E-CID MEASUREMENT REPORT message. Upon reception of the *Mobile Access Point Location Information* IE, the LMF may use the value as the location information of the mobile NG-RAN access point that is associated to the mobile TRP. + +#### 8.2.3.3 Unsuccessful Operation + +Not applicable. + +#### 8.2.3.4 Abnormal Conditions + +Void. + +### 8.2.4 E-CID Measurement Termination + +#### 8.2.4.1 General + +The purpose of E-CID Measurement Termination procedure is to terminate periodical E-CID measurements for the UE performed by the NG-RAN node. + +#### 8.2.4.2 Successful Operation + +![Sequence diagram for E-CID Measurement Termination procedure, successful operation](4b87467ad9642943235f48f7d4b59449_img.jpg) + +A sequence diagram showing the interaction between an NG-RAN Node and an LMF. The LMF sends an E-CID MEASUREMENT TERMINATION COMMAND message to the NG-RAN Node. The NG-RAN Node is represented by a box with a thick black bar at its base, and the LMF is represented by a box with a thick black bar at its base. The message is indicated by a horizontal arrow pointing from the LMF to the NG-RAN Node. + +Sequence diagram for E-CID Measurement Termination procedure, successful operation + +**Figure 8.2.4.2-1: E-CID Measurement Termination procedure, successful operation** + +The LMF initiates the procedure by generating an E-CID MEASUREMENT TERMINATION COMMAND message. + +#### 8.2.4.3 Unsuccessful Operation + +Not applicable. + +#### 8.2.4.4 Abnormal Conditions + +Void. + +### 8.2.5 OTDOA Information Exchange + +#### 8.2.5.1 General + +The purpose of the OTDOA Information Exchange procedure is to allow the LMF to request the NG-RAN node to transfer OTDOA information to the LMF. + +#### 8.2.5.2 Successful Operation + +![Sequence diagram for OTDOA Information Exchange procedure, successful operation](0fa26005ab105a07af4fda20b2554987_img.jpg) + +A sequence diagram showing the interaction between an NG-RAN node and an LMF. The LMF sends an OTDOA INFORMATION REQUEST message to the NG-RAN node, and the NG-RAN node responds with an OTDOA INFORMATION RESPONSE message. The NG-RAN node is represented by a box with a thick black bar at its base, and the LMF is represented by a box with a thick black bar at its base. The first message is indicated by a horizontal arrow pointing from the LMF to the NG-RAN node, and the second message is indicated by a horizontal arrow pointing from the NG-RAN node to the LMF. + +Sequence diagram for OTDOA Information Exchange procedure, successful operation + +**Figure 8.2.5.2-1: OTDOA Information Exchange procedure, successful operation** + +The LMF initiates the procedure by sending an OTDOA INFORMATION REQUEST message. The NG-RAN node responds with OTDOA INFORMATION RESPONSE message that contains the available OTDOA information applicable to the relevant cells/TPs. + +#### 8.2.5.3 Unsuccessful Operation + +![Sequence diagram for OTDOA Information Exchange procedure, unsuccessful operation](e354b57563dae469c00b412b2abdf765_img.jpg) + +``` +sequenceDiagram + participant LMF + participant NG-RAN_node as NG-RAN node + Note left of NG-RAN_node: + LMF->>NG-RAN_node: OTDOA INFORMATION REQUEST + Note right of NG-RAN_node: + NG-RAN_node-->>LMF: OTDOA INFORMATION FAILURE + Note right of LMF: +``` + +The diagram shows a sequence of messages between an LMF and an NG-RAN node. The LMF sends an 'OTDOA INFORMATION REQUEST' to the NG-RAN node. The NG-RAN node responds with an 'OTDOA INFORMATION FAILURE' message. Both entities are represented by boxes with a horizontal line at the bottom, indicating the timeline of the interaction. + +Sequence diagram for OTDOA Information Exchange procedure, unsuccessful operation + +**Figure 8.2.5.3-1: OTDOA Information Exchange procedure, unsuccessful operation** + +If the NG-RAN node does not have any OTDOA information to report, the NG-RAN node shall respond with an OTDOA INFORMATION FAILURE message. + +#### 8.2.5.4 Abnormal Conditions + +Void. + +### 8.2.6 Positioning Information Exchange + +#### 8.2.6.1 General + +The Positioning Information Exchange procedure is initiated by the LMF to request to the NG-RAN node positioning information for the UE. This procedure applies only if the NG-RAN node is a gNB. + +#### 8.2.6.2 Successful Operation + +![Sequence diagram for Positioning Information Exchange procedure, successful operation](c8e5b3ef81948bb13d5c6c3c326799ea_img.jpg) + +``` +sequenceDiagram + participant LMF + participant NG-RAN_node as NG-RAN node + Note left of NG-RAN_node: + LMF->>NG-RAN_node: POSITIONING INFORMATION REQUEST + Note right of NG-RAN_node: + NG-RAN_node-->>LMF: POSITIONING INFORMATION RESPONSE + Note right of LMF: +``` + +The diagram shows a sequence of messages between an LMF and an NG-RAN node. The LMF sends a 'POSITIONING INFORMATION REQUEST' to the NG-RAN node. The NG-RAN node responds with a 'POSITIONING INFORMATION RESPONSE' message. Both entities are represented by boxes with a horizontal line at the bottom, indicating the timeline of the interaction. + +Sequence diagram for Positioning Information Exchange procedure, successful operation + +**Figure 8.2.6.2-1: Positioning Information Exchange procedure, successful operation** + +The LMF initiates the procedure by sending a POSITIONING INFORMATION REQUEST message to the NG-RAN node. + +If the *Requested SRS Transmission Characteristics* IE is included in the POSITIONING INFORMATION REQUEST message, the NG-RAN node may take this information into account when configuring SRS transmissions for the UE, and it shall include the *SRS Configuration* IE and the *SFN Initialisation Time* IE in the POSITIONING INFORMATION RESPONSE message. + +If the *Spatial Relation Information per SRS Resource* IE and the *Periodicity List* IE are both included in the *Requested SRS Transmission Characteristics* IE, the NG-RAN node shall consider that the *Spatial Relation per SRS Resource Item* IE and the *Periodicity List Item* IE have one-to-one mapping relation. + +If the *UE Reporting Information* IE is included in the POSITIONING INFORMATION REQUEST message, the NG-RAN node may take this information into account for allocating proper CG-SDT resources when positioning a UE. + +If the *UE TEG Information Request* IE is included in the POSITIONING INFORMATION REQUEST message and set to "onDemand", the NG-RAN node shall, if supported, provide the UE Tx TEG association in the POSITIONING INFORMATION RESPONSE message. + +If the *UE TEG Information Request* IE is set to "periodic", the NG-RAN node shall, if supported, reply with the POSITIONING INFORMATION RESPONSE message without including any UE Tx TEG association in this message. The NG-RAN node shall then take the *UE TEG Reporting Periodicity* IE into account when configuring the UE's periodic UE Tx TEG association reporting and initiate the Positioning Information Update procedure for reporting the UE Tx TEG association received from the UE, if any. + +If the *New NR CGI* IE is included in the POSITIONING INFORMATION RESPONSE message, the LMF shall, if supported, consider it as the new cell identity where the UE has currently resumed and take it into account for subsequent positioning procedures. + +#### 8.2.6.3 Unsuccessful Operation + +![Sequence diagram showing an unsuccessful positioning information exchange between an NG-RAN node and an LMF. The LMF sends a POSITIONING INFORMATION REQUEST to the NG-RAN node, and the NG-RAN node responds with a POSITIONING INFORMATION FAILURE.](9b686adccf125267a013fa25721231a3_img.jpg) + +``` +sequenceDiagram + participant LMF + participant NG-RAN_node + Note left of NG-RAN_node: + LMF->>NG-RAN_node: POSITIONING INFORMATION REQUEST + NG-RAN_node-->>LMF: POSITIONING INFORMATION FAILURE + Note right of LMF: +``` + +Sequence diagram showing an unsuccessful positioning information exchange between an NG-RAN node and an LMF. The LMF sends a POSITIONING INFORMATION REQUEST to the NG-RAN node, and the NG-RAN node responds with a POSITIONING INFORMATION FAILURE. + +**Figure 8.2.6.3-1: Positioning Information Exchange procedure, unsuccessful operation** + +If the *Requested SRS Transmission Characteristics* IE is included in the POSITIONING INFORMATION REQUEST message and the NG-RAN node is unable to configure any SRS transmissions for the UE, it shall respond with a POSITIONING INFORMATION FAILURE message. If a handover of the target UE has been triggered, the NG-RAN node shall send a POSITIONING INFORMATION FAILURE message with an appropriate cause value. + +If the NG-RAN node is unable to provide any of the requested information, the NG-RAN node shall respond with a POSITIONING INFORMATION FAILURE message with an appropriate cause value. + +#### 8.2.6.4 Abnormal Conditions + +Void. + +### 8.2.7 Positioning Information Update + +#### 8.2.7.1 General + +The Positioning Information Update procedure is initiated by the NG-RAN node to indicate to the LMF that a change has occurred in the SRS configuration or in the UE Tx TEG association. This procedure applies only if the NG-RAN node is a gNB. + +#### 8.2.7.2 Successful Operation + +![Sequence diagram showing the successful operation of the Positioning Information Update procedure. An NG-RAN node sends a POSITIONING INFORMATION UPDATE message to an LMF.](e90987faabad6a6665cd8ed1151dc474_img.jpg) + +``` +sequenceDiagram + participant NG-RAN node + participant LMF + Note left of NG-RAN node: + NG-RAN node->>LMF: POSITIONING INFORMATION UPDATE + Note right of LMF: + Note right of LMF: +``` + +Sequence diagram showing the successful operation of the Positioning Information Update procedure. An NG-RAN node sends a POSITIONING INFORMATION UPDATE message to an LMF. + +**Figure 8.2.7.2-1: Positioning Information Update procedure, successful operation** + +The NG-RAN node initiates the procedure by sending a POSITIONING INFORMATION UPDATE message to the LMF. If the *SRS Configuration* IE is included in the POSITIONING INFORMATION UPDATE message, the LMF shall consider this information as the updated SRS Configuration for the UE. If the *SFN Initialisation Time* IE is included in the POSITIONING INFORMATION UPDATE message, the LMF shall consider this information as the SFN Initialisation Time associated to the SRS Configuration. + +If the *UE Tx TEG Association List* IE is included in the POSITIONING INFORMATION UPDATE message, the LMF shall consider it as the UE Tx TEG association for the SRS resources that have changed their TEG association during the latest reporting interval. + +If the *SRS Transmission Status* IE is included in the POSITIONING INFORMATION UPDATE message and set to "stopped", the LMF shall consider that the SRS transmission has stopped. + +#### 8.2.7.3 Unsuccessful Operation + +Not Applicable. + +#### 8.2.7.4 Abnormal Conditions + +Void. + +### 8.2.8 TRP Information Exchange + +#### 8.2.8.1 General + +The purpose of the TRP Information Exchange procedure is to allow the LMF to request the NG-RAN node to provide detailed information for TRPs hosted by the NG-RAN node. This procedure applies only if the NG-RAN node is a gNB. + +#### 8.2.8.2 Successful Operation + +![Sequence diagram for successful TRP Information Exchange procedure. The LMF sends a TRP INFORMATION REQUEST to the NG-RAN node, and the NG-RAN node responds with a TRP INFORMATION RESPONSE.](eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg) + +``` +sequenceDiagram + participant LMF + participant NG-RAN_node as NG-RAN node + Note left of NG-RAN_node: + LMF->>NG-RAN_node: TRP INFORMATION REQUEST + NG-RAN_node-->>LMF: TRP INFORMATION RESPONSE + Note right of LMF: +``` + +Sequence diagram for successful TRP Information Exchange procedure. The LMF sends a TRP INFORMATION REQUEST to the NG-RAN node, and the NG-RAN node responds with a TRP INFORMATION RESPONSE. + +Figure 8.2.8.2-1: TRP Information Exchange procedure, successful operation + +The LMF initiates the procedure by sending a TRP INFORMATION REQUEST message. The NG-RAN node responds with a TRP INFORMATION RESPONSE message that contains the requested TRP information. + +If the *TRP List* IE is included in the TRP INFORMATION REQUEST message, the NG-RAN node should include in the TRP INFORMATION RESPONSE message, the requested information for all TRPs included in the *TRP List* IE. + +If the *TRP List* IE is not included in the TRP INFORMATION REQUEST message, the NG-RAN node should include the requested information for all TRPs hosted by the NG-RAN node in the TRP INFORMATION RESPONSE message + +If the *PRS Muting* IE is included in the *PRS Configuration* IE in the TRP INFORMATION RESPONSE message, the LMF may take it into account as the muting information for the given PRS resource set. + +If the *QCL Info* IE is included in the *PRS Configuration* IE in the TRP INFORMATION RESPONSE message, the LMF may take it into account for the given PRS resource list. + +If the *DL-PRS Resource Coordinates* IE is included in the *Geographical Coordinates* IE in the *TRP Information* IE in the TRP INFORMATION RESPONSE message, the LMF may take it into account as the DL PRS Resource Coordinates relative to the TRP coordinate. + +If the *Mobile IAB-MT UE ID* IE is included in the *TRP Information* IE in the TRP INFORMATION RESPONSE message, the LMF shall, if supported, use this information to determine an updated location of the Mobile TRP as specified in TS 23.273 [Xx]. + +If the *TRP Information Type Item* IE is set to 'mobile trp location info', the NG-RAN node shall, if supported, derive the location of the Mobile TRP as specified in TS 23.273 [Xx] and include the *Mobile TRP Location Information* in the TRP INFORMATION RESPONSE message. + +#### 8.2.8.3 Unsuccessful Operation + +![Sequence diagram for unsuccessful TRP Information Exchange procedure. The LMF sends a TRP INFORMATION REQUEST to the NG-RAN node, and the NG-RAN node responds with a TRP INFORMATION FAILURE.](d5918cee231b536f20789a18d861fae3_img.jpg) + +``` +sequenceDiagram + participant LMF + participant NG-RAN_node as NG-RAN node + Note left of NG-RAN_node: + LMF->>NG-RAN_node: TRP INFORMATION REQUEST + NG-RAN_node-->>LMF: TRP INFORMATION FAILURE + Note right of LMF: +``` + +Sequence diagram for unsuccessful TRP Information Exchange procedure. The LMF sends a TRP INFORMATION REQUEST to the NG-RAN node, and the NG-RAN node responds with a TRP INFORMATION FAILURE. + +Figure 8.2.8.3-1: TRP Information Exchange procedure, unsuccessful operation + +If the NG-RAN node cannot provide any of the requested information for any TRP, the NG-RAN node shall respond with a TRP INFORMATION FAILURE message. + +#### 8.2.8.4 Abnormal Conditions + +Void. + +### 8.2.9 Positioning Activation + +#### 8.2.9.1 General + +The Positioning Activation procedure is initiated by the LMF to request the NG-RAN node to activate semi-persistent or trigger aperiodic UL SRS transmission by the UE. This procedure applies only if the NG-RAN node is a gNB. + +#### 8.2.9.2 Successful Operation + +![Sequence diagram of the Positioning Activation procedure, successful operation. The diagram shows two vertical lifelines: NG-RAN node (left) and LMF (right). The LMF sends a POSITIONING ACTIVATION REQUEST message to the NG-RAN node. The NG-RAN node responds with a POSITIONING ACTIVATION RESPONSE message to the LMF. Both lifelines end with a thick horizontal bar at the bottom.](84e5b251aa38db522f76f5cc3afcb853_img.jpg) + +``` +sequenceDiagram + participant LMF + participant NG-RAN node + Note left of NG-RAN node: + LMF->>NG-RAN node: POSITIONING ACTIVATION REQUEST + NG-RAN node-->>LMF: POSITIONING ACTIVATION RESPONSE + Note right of LMF: +``` + +Sequence diagram of the Positioning Activation procedure, successful operation. The diagram shows two vertical lifelines: NG-RAN node (left) and LMF (right). The LMF sends a POSITIONING ACTIVATION REQUEST message to the NG-RAN node. The NG-RAN node responds with a POSITIONING ACTIVATION RESPONSE message to the LMF. Both lifelines end with a thick horizontal bar at the bottom. + +**Figure 8.2.9.2-1: Positioning Activation procedure, successful operation** + +The LMF initiates the procedure by sending a POSITIONING ACTIVATION REQUEST message to the NG-RAN node. + +For semi-persistent UL SRS, the POSITIONING ACTIVATION REQUEST message includes an indication of the UL SRS resource set to be activated and may include the spatial relation for the semi-persistent UL SRS resource to be activated. For aperiodic UL SRS, if the *SRS Resource Trigger* IE is included in the POSITIONING ACTIVATION REQUEST message, the NG-RAN node shall take the value of this IE into account when triggering aperiodic SRS transmission by the UE. + +If the *Activation Time* IE is included in the POSITIONING ACTIVATION REQUEST message, the NG-RAN node shall take the indicated value as the LMF's requested time for activation of the UE's SRS transmission. + +Following successful activation of UL SRS transmission in the UE, the NG-RAN node shall respond with a POSITIONING ACTIVATION RESPONSE message. If the POSITIONING ACTIVATION RESPONSE message includes the *System Frame Number* and/or the *Slot Number* IEs, the LMF shall consider that the respective information indicates the activation time of SRS transmission by the UE. + +#### 8.2.9.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Operation of Positioning Activation procedure.](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) + +``` +sequenceDiagram + participant NG-RAN node + participant LMF + Note left of NG-RAN node: + LMF->>NG-RAN node: POSITIONING ACTIVATION REQUEST + NG-RAN node-->>LMF: POSITIONING ACTIVATION FAILURE + Note right of LMF: +``` + +The diagram shows a sequence of messages between an NG-RAN node and an LMF. The NG-RAN node is on the left and the LMF is on the right. A solid arrow labeled 'POSITIONING ACTIVATION REQUEST' points from the LMF to the NG-RAN node. A dashed arrow labeled 'POSITIONING ACTIVATION FAILURE' points from the NG-RAN node back to the LMF. Both entities have a thick horizontal bar at their lifeline base. + +Sequence diagram for Unsuccessful Operation of Positioning Activation procedure. + +**Figure 8.2.9.3-1: Positioning Activation procedure, unsuccessful operation** + +If the NG-RAN node is unable to activate UL SRS transmission in the UE, it shall respond with a POSITIONING ACTIVATION FAILURE message. + +If the NG-RAN node is unable to trigger the aperiodic SRS transmission with the indicated *SRS Resource Trigger* IE, it shall respond with a POSITIONING ACTIVATION FAILURE message with an appropriate cause value. + +#### 8.2.9.4 Abnormal Conditions + +Void. + +### 8.2.10 Positioning Deactivation + +#### 8.2.10.1 General + +The Positioning Deactivation procedure is initiated by the LMF to indicate to the NG-RAN node that UL SRS transmission should be deactivated in the UE. This procedure applies only if the NG-RAN node is a gNB. + +#### 8.2.10.2 Successful Operation + +![Sequence diagram for Successful Operation of Positioning Deactivation procedure.](718be1eb075833deb7a3b80729a06264_img.jpg) + +``` +sequenceDiagram + participant NG-RAN node + participant LMF + Note left of NG-RAN node: + LMF->>NG-RAN node: POSITIONING DEACTIVATION + Note right of LMF: +``` + +The diagram shows a sequence of messages between an NG-RAN node and an LMF. The NG-RAN node is on the left and the LMF is on the right. A solid arrow labeled 'POSITIONING DEACTIVATION' points from the LMF to the NG-RAN node. Both entities have a thick horizontal bar at their lifeline base. + +Sequence diagram for Successful Operation of Positioning Deactivation procedure. + +**Figure 8.2.10.2-1: Positioning Deactivation procedure, successful operation** + +The LMF initiates the procedure by sending a POSITIONING DEACTIVATION message to the NG-RAN node. This message shall include an indication of the UL SRS resource set to be deactivated or release all the related resources. + +#### 8.2.10.3 Unsuccessful Operation + +Not Applicable. + +#### 8.2.10.4 Abnormal Conditions + +Void. + +### 8.2.11 PRS Configuration Exchange + +#### 8.2.11.1 General + +The PRS Configuration Exchange procedure is initiated by the LMF to request the NG-RAN node to configure or update (i.e., turn off) PRS transmission. This procedure applies only if the NG-RAN node is a gNB. + +#### 8.2.11.2 Successful Operation + +![Sequence diagram for PRS Configuration Exchange procedure, successful operation. The LMF sends a PRS CONFIGURATION REQUEST to the NG-RAN Node, and the NG-RAN Node responds with a PRS CONFIGURATION RESPONSE.](5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg) + +``` +sequenceDiagram + participant LMF + participant NG-RAN Node + Note left of NG-RAN Node: + LMF->>NG-RAN Node: PRS CONFIGURATION REQUEST + NG-RAN Node-->>LMF: PRS CONFIGURATION RESPONSE + Note right of LMF: +``` + +Sequence diagram for PRS Configuration Exchange procedure, successful operation. The LMF sends a PRS CONFIGURATION REQUEST to the NG-RAN Node, and the NG-RAN Node responds with a PRS CONFIGURATION RESPONSE. + +Figure 8.2.11.2-1: PRS Configuration Exchange procedure, successful operation + +The LMF initiates the procedure by sending a PRS CONFIGURATION REQUEST message to the NG-RAN. + +If the *PRS Configuration Request Type* IE is set to “configure”, the NG-RAN node should use the information in the *Requested DL PRS Transmission Characteristics* IE to configure DL-PRS transmission by the indicated TRP(s). + +If the *PRS Configuration Request Type* IE is set to “off”, the NG-RAN node should, if supported, use the information in the *PRS Transmission Off Information* IE to turn off the DL-PRS transmission for the indicated TRP(s), PRS Resource Set(s), or PRS Resource(s). + +If DL-PRS transmission is successfully configured or updated for at least one of the TRPs, the NG-RAN node shall respond with a PRS CONFIGURATION RESPONSE message. + +#### 8.2.11.3 Unsuccessful Operation + +![Sequence diagram for PRS Configuration Exchange procedure, unsuccessful operation. The LMF sends a PRS CONFIGURATION REQUEST to the NG-RAN Node, and the NG-RAN Node responds with a PRS CONFIGURATION FAILURE.](00c1e69f3f99d3499b03d2463d6d2fd2_img.jpg) + +``` +sequenceDiagram + participant LMF + participant NG-RAN Node + Note left of NG-RAN Node: + LMF->>NG-RAN Node: PRS CONFIGURATION REQUEST + NG-RAN Node-->>LMF: PRS CONFIGURATION FAILURE + Note right of LMF: +``` + +Sequence diagram for PRS Configuration Exchange procedure, unsuccessful operation. The LMF sends a PRS CONFIGURATION REQUEST to the NG-RAN Node, and the NG-RAN Node responds with a PRS CONFIGURATION FAILURE. + +Figure 8.2.11.3-1: PRS Configuration Exchange procedure, unsuccessful operation + +If the NG-RAN node cannot configure or update DL-PRS transmission for any of the TRPs in the *PRS TRP List* IE of the PRS CONFIGURATION REQUEST message, it shall respond with a PRS CONFIGURATION FAILURE message with an appropriate cause value. + +#### 8.2.11.4 Abnormal Conditions + +Void. + +### 8.2.12 Measurement Preconfiguration + +#### 8.2.12.1 General + +The Measurement Preconfiguration procedure allows the LMF to provide necessary information to the serving gNB and request the gNB to preconfigure measurement gap and/or PRS processing window for the UE. This procedure applies only if the NG-RAN node is a gNB. + +#### 8.2.12.2 Successful Operation + +![Sequence diagram for successful measurement preconfiguration](1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg) + +``` +sequenceDiagram + participant LMF + participant NG-RAN node + Note left of NG-RAN node: + LMF->>NG-RAN node: MEASUREMENT PRECONFIGURATION REQUIRED + NG-RAN node-->>LMF: MEASUREMENT PRECONFIGURATION CONFIRM + Note right of LMF: +``` + +The diagram illustrates the successful operation of the measurement preconfiguration procedure. It shows two participants: NG-RAN node and LMF. The LMF sends a 'MEASUREMENT PRECONFIGURATION REQUIRED' message to the NG-RAN node. The NG-RAN node responds with a 'MEASUREMENT PRECONFIGURATION CONFIRM' message. Both messages are shown as horizontal arrows between the two entities, with the LMF on the right and the NG-RAN node on the left. Vertical lines extend downwards from each participant box to a horizontal bar at the bottom, representing the timeline of the procedure. + +Sequence diagram for successful measurement preconfiguration + +**Figure 8.2.12.2-1: Measurement Preconfiguration procedure, successful operation** + +The LMF initiates the procedure by sending a MEASUREMENT PRECONFIGURATION REQUIRED message. + +If the NG-RAN node is able to configure measurement gap or PRS processing window, it shall reply with the MEASUREMENT PRECONFIGURATION CONFIRM message. + +#### 8.2.12.3 Unsuccessful Operation + +![Sequence diagram for unsuccessful measurement preconfiguration](e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg) + +``` +sequenceDiagram + participant LMF + participant NG-RAN node + Note left of NG-RAN node: + LMF->>NG-RAN node: MEASUREMENT PRECONFIGURATION REQUIRED + NG-RAN node-->>LMF: MEASUREMENT PRECONFIGURATION REFUSE + Note right of LMF: +``` + +The diagram illustrates the unsuccessful operation of the measurement preconfiguration procedure. It shows the same two participants: NG-RAN node and LMF. The LMF sends a 'MEASUREMENT PRECONFIGURATION REQUIRED' message to the NG-RAN node. The NG-RAN node responds with a 'MEASUREMENT PRECONFIGURATION REFUSE' message. Both messages are shown as horizontal arrows between the two entities, with the LMF on the right and the NG-RAN node on the left. Vertical lines extend downwards from each participant box to a horizontal bar at the bottom, representing the timeline of the procedure. + +Sequence diagram for unsuccessful measurement preconfiguration + +**Figure 8.2.12.3-1: Measurement Preconfiguration procedure, unsuccessful operation** + +If the NG-RAN node cannot configure any of the measurement gap or PRS processing window, the NG-RAN node shall respond with a MEASUREMENT PRECONFIGURATION REFUSE message. Upon receiving the MEASUREMENT PRECONFIGURATION REFUSE message, the LMF shall release the reserved PPW resources. + +#### 8.2.12.4 Abnormal Conditions + +Void. + +### 8.2.13 Measurement Activation + +#### 8.2.13.1 General + +The Measurement Activation procedure is initiated by the LMF to request the NG-RAN node to activate or deactivate the preconfigured measurement gap or PRS processing window for the UE. This procedure applies only if the NG-RAN node is a gNB. + +#### 8.2.13.2 Successful Operation + +![Sequence diagram showing the successful operation of the Measurement Activation procedure. The LMF sends a MEASUREMENT ACTIVATION message to the NG-RAN node.](b904ac2472cab80892d1e783e6230d6e_img.jpg) + +``` +sequenceDiagram + participant LMF + participant NG-RAN node + Note left of NG-RAN node: + Note right of LMF: + LMF->>NG-RAN node: MEASUREMENT ACTIVATION +``` + +Sequence diagram showing the successful operation of the Measurement Activation procedure. The LMF sends a MEASUREMENT ACTIVATION message to the NG-RAN node. + +**Figure 8.2.13.2-1: Measurement Activation procedure, successful operation** + +The LMF initiates the procedure by sending a MEASUREMENT ACTIVATION message to the NG-RAN node. + +If the *PRS Measurement Info List* IE is included in the MEASUREMENT ACTIVATION message, the NG-RAN node may take it into account when activating pre-configured measurement gap in the UE. + +#### 8.2.13.3 Unsuccessful Operation + +Not Applicable. + +#### 8.2.13.4 Abnormal Conditions + +Void. + +## 8.3 Management Procedures + +### 8.3.1 Error Indication + +#### 8.3.1.1 General + +The Error Indication procedure is initiated by a node to report detected errors in one incoming message, provided they cannot be reported by an appropriate failure message. + +#### 8.3.1.2 Successful Operation + +![Sequence diagram showing the Error Indication procedure initiated by the LMF.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) + +A sequence diagram illustrating the Error Indication procedure initiated by the LMF. It features two vertical lifelines: 'NG-RAN Node' on the left and 'LMF' on the right. A horizontal arrow labeled 'ERROR INDICATION' points from the LMF lifeline to the NG-RAN Node lifeline. Both lifelines have a thick horizontal bar at their base, representing the start of the procedure. + +Sequence diagram showing the Error Indication procedure initiated by the LMF. + +Figure 8.3.1.2-1: Error Indication procedure, LMF originated, successful operation + +![Sequence diagram showing the Error Indication procedure initiated by the NG-RAN Node.](a1890b9a9b85f13e67ed59bbad623659_img.jpg) + +A sequence diagram illustrating the Error Indication procedure initiated by the NG-RAN Node. It features two vertical lifelines: 'NG-RAN Node' on the left and 'LMF' on the right. A horizontal arrow labeled 'ERROR INDICATION' points from the NG-RAN Node lifeline to the LMF lifeline. Both lifelines have a thick horizontal bar at their base, representing the start of the procedure. + +Sequence diagram showing the Error Indication procedure initiated by the NG-RAN Node. + +Figure 8.3.1.2-2: Error Indication procedure, NG-RAN node 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. + +#### 8.3.1.3 Abnormal Conditions + +Not applicable. + +## 8.4 Assistance Information Transfer Procedures + +### 8.4.1 Assistance Information Control + +#### 8.4.1.1 General + +The purpose of the Assistance Information Control procedure is to allow the LMF to signal positioning assistance information to the NG-RAN Node for assistance information broadcasting. This procedure applies only if the NG-RAN node is a gNB. + +#### 8.4.1.2 Successful Operation + +![Diagram of the Assistance Information Control procedure. It shows two entities: NG-RAN Node and LMF. A horizontal arrow labeled 'ASSISTANCE INFORMATION CONTROL' points from the LMF to the NG-RAN Node. Both entities are represented by a box above a thick horizontal line representing the ground or base.](9870bf462aa0d916a16d14b5a100c60a_img.jpg) + +``` +graph LR; LMF[LMF] -- "ASSISTANCE INFORMATION CONTROL" --> NG-RAN[NG-RAN Node]; +``` + +Diagram of the Assistance Information Control procedure. It shows two entities: NG-RAN Node and LMF. A horizontal arrow labeled 'ASSISTANCE INFORMATION CONTROL' points from the LMF to the NG-RAN Node. Both entities are represented by a box above a thick horizontal line representing the ground or base. + +**Figure 8.4.1.2-1: Assistance Information Control procedure** + +The LMF initiates the procedure by sending an ASSISTANCE INFORMATION CONTROL message. + +If the *Assistance Information* IE is included in the ASSISTANCE INFORMATION CONTROL message, the NG-RAN Node shall, if supported, replace any previously stored assistance information and use the received information to configure assistance information broadcasting. + +If the *Broadcast Priority* IE is included in the *Assistance Information* IE, the NG-RAN Node may take it into account when configuring broadcasting for the relevant information. Assistance information having the same Broadcast Priority value should receive the same treatment (i.e. broadcast by the NG-RAN Node or not broadcast). + +If the *Broadcast* IE is included in the ASSISTANCE INFORMATION CONTROL message and set to "start", the NG-RAN Node may start broadcasting the assistance information. If the *Broadcast* IE is included in the ASSISTANCE INFORMATION CONTROL message and set to "stop", the NG-RAN Node may stop broadcasting the assistance information. + +If the *Positioning Broadcast Cells* IE is included in the ASSISTANCE INFORMATION CONTROL message, the NG-RAN shall, if supported, consider that the received assistance information is applicable to the cells in this IE. + +#### 8.4.1.3 Abnormal Conditions + +If the *Broadcast* IE is included in the ASSISTANCE INFORMATION CONTROL message and set to "start", and no assistance information is available, the NG-RAN Node shall consider the procedure as failed. + +If neither the *Assistance Information* IE nor the *Broadcast* IE are included in the ASSISTANCE INFORMATION CONTROL message, the NG-RAN Node shall consider the procedure as failed. + +### 8.4.2 Assistance Information Feedback + +#### 8.4.2.1 General + +The purpose of the Assistance Information Feedback procedure is to allow the NG-RAN Node to give feedback to the LMF on assistance information broadcasting. This procedure applies only if the NG-RAN node is a gNB. + +#### 8.4.2.2 Successful Operation + +![Diagram of Assistance Information Feedback procedure](1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg) + +A sequence diagram showing the 'ASSISTANCE INFORMATION FEEDBACK' procedure. It features two vertical lifelines: 'NG-RAN Node' on the left and 'LMF' on the right. A single horizontal arrow points from the NG-RAN Node to the LMF, labeled 'ASSISTANCE INFORMATION FEEDBACK'. Both lifelines end with a thick horizontal bar at the bottom. + +Diagram of Assistance Information Feedback procedure + +**Figure 8.4.2.2-1: Assistance Information Feedback procedure** + +If the *Assistance Information Failure List* IE is included in the ASSISTANCE INFORMATION FEEDBACK message, the LMF shall consider that assistance information broadcasting could not be configured for the relevant information. + +If the *Positioning Broadcast Cells* IE is included in the ASSISTANCE INFORMATION FEEDBACK message, the LMF shall consider that the feedback provided is applicable to the cells in this IE. + +#### 8.4.2.3 Abnormal Conditions + +Void. + +## 8.5 Measurement Information Transfer + +### 8.5.1 Measurement + +#### 8.5.1.1 General + +The Measurement procedure allows the LMF to request one or more TRPs in the NG-RAN node to perform and report positioning measurements. This procedure applies only if the NG-RAN node is a gNB. + +#### 8.5.1.2 Successful Operation + +![Diagram of Measurement procedure. Successful operation.](44c70af075e4d9bbc6fbe267a666b3b0_img.jpg) + +A sequence diagram illustrating the 'Measurement procedure. Successful operation.' It shows two lifelines: 'NG-RAN node' on the left and 'LMF' on the right. The LMF sends a 'MEASUREMENT REQUEST' message to the NG-RAN node, represented by a horizontal arrow pointing left. The NG-RAN node responds with a 'MEASUREMENT RESPONSE' message, represented by a horizontal arrow pointing right to the LMF. Both lifelines terminate with thick horizontal bars at the bottom. + +Diagram of Measurement procedure. Successful operation. + +**Figure 8.5.1.2.1: Measurement procedure. Successful operation.** + +The LMF initiates the procedure by sending a MEASUREMENT REQUEST message to the NG-RAN node, indicating in the *TRP Measurement Request List* IE the TRP(s) from which measurements are requested. The NG-RAN node shall use the included information to configure positioning measurements by the indicated TRP(s). If at least one of the requested measurements has been successful for at least one of the TRPs, the NG-RAN node shall reply with a MEASUREMENT RESPONSE message including the *TRP Measurement Response List* IE. + +If the *Report Characteristics* IE is set to "OnDemand", the NG-RAN node shall return the corresponding measurement results in the MEASUREMENT RESPONSE message, and the LMF shall consider that this reporting has been terminated by the NG-RAN node. If the *Report Characteristics* IE is set to "Periodic", the NG-RAN node shall initiate the corresponding measurements, and it shall reply with the MEASUREMENT RESPONSE message without including any measurement results in the message. The NG-RAN node shall then periodically initiate the Measurement Report procedure for the corresponding measurements, with the requested reporting periodicity. + +If the *Measurement Beam Information Request* IE is included in the MEASUREMENT REQUEST message, the NG-RAN node shall include the *Measurement Beam Information* IE in the *TRP Measurement Result* IE of the MEASUREMENT RESPONSE message. + +If the *Measurement Quality* IE is included in the *TRP Measurement Result* IE in the MEASUREMENT RESPONSE message, the LMF may take it into account as the TRP estimate of the measurement quality. If the *Measurement Quality* IE includes the *Zenith Quality* IE, the LMF may take it into account within the angle measurement quality. + +If the *Timing Reporting Granularity Factor* IE is included in the *TRP Measurement Quantities* IE in the MEASUREMENT REQUEST message, the NG-RAN node may take it into account when configuring measurements including UL RTOA and gNB Rx-Tx Time Difference. + +If the *System Frame Number* IE and/or the *Slot Number* IE are included in the MEASUREMENT REQUEST message, the NG-RAN node shall, if supported, consider that the respective information indicates the activation time of SRS transmission. + +If the *Report Characteristics* IE is set to "OnDemand" and the *Response Time* IE is included in the MEASUREMENT REQUEST message, the NG-RAN node shall, if supported, return the corresponding measurement results in the MEASUREMENT RESPONSE message within the indicated time. + +If the *Measurement Characteristics Request Indicator* IE is included in the MEASUREMENT REQUEST message, the NG-RAN node shall, if supported, take the requested measurement characteristics into account when configuring measurements, and include the requested information, if available, in the MEASUREMENT RESPONSE message. + +If the *Number of TRP Rx TEGs* IE is included in the MEASUREMENT REQUEST message, the NG-RAN node shall, if supported, use it to measure the same SRS resource with different TRP Rx TEGs for the indicated TRP, and report the corresponding UL-RTOA and/or gNB Rx-Tx time difference measurements. + +If the *Number of TRP RxTx TEGs* IE is included in the MEASUREMENT REQUEST message, the NG-RAN node shall, if supported, use it to measure the same SRS resource with different TRP RxTx TEGs with the same TRP Tx TEG for the indicated TRP, and report the corresponding gNB Rx-Tx time difference measurements. + +If the *Measurement Time Occasion* IE is included in the MEASUREMENT REQUEST message, the NG-RAN node may take it into account as the number of SRS measurement time occasions for a measurement instance. + +##### **Interaction with the Measurement Report procedure:** + +If the *Report Characteristics* IE is set to "Periodic" and the *Measurement Amount* IE is included in the MEASUREMENT REQUEST message, the NG-RAN node shall, if supported, take it into account for sending the MEASUREMENT REPORT message. + +#### 8.5.1.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Operation](04cfca33e3fc26513abe649d7474f733_img.jpg) + +``` +sequenceDiagram + participant NG-RAN node + participant LMF + Note left of NG-RAN node: + LMF->>NG-RAN node: MEASUREMENT REQUEST + Note right of LMF: + NG-RAN node-->>LMF: MEASUREMENT FAILURE + Note right of NG-RAN node: +``` + +The diagram shows a sequence of messages between an NG-RAN node and an LMF. The NG-RAN node is on the left and the LMF is on the right. A solid arrow labeled "MEASUREMENT REQUEST" points from the LMF to the NG-RAN node. A dashed arrow labeled "MEASUREMENT FAILURE" points from the NG-RAN node back to the LMF. Both entities have a small horizontal bar at the bottom of their lifelines. + +Sequence diagram for Unsuccessful Operation + +**Figure 8.5.1.3.1: Measurement procedure. Unsuccessful operation.** + +If the NG-RAN node cannot configure any of the requested measurements for any of the TRPs in the *TRP Measurement Request List* IE of the MEASUREMENT REQUEST message, it shall respond with a MEASUREMENT FAILURE message with an appropriate cause value. + +#### 8.5.1.4 Abnormal Conditions + +If the *Report Characteristics* IE is set to "OnDemand" and the *Response Time* IE is included in the MEASUREMENT REQUEST message but the NG-RAN node is unable to provide the measurement results within the indicated time, the NG-RAN node shall, if supported, respond with a MEASUREMENT FAILURE message with an appropriate cause value. + +### 8.5.2 Measurement Report + +#### 8.5.2.1 General + +The Measurement Report procedure allows the NG-RAN node to report positioning measurements to the LMF. This procedure applies only if the NG-RAN node is a gNB. + +#### 8.5.2.2 Successful Operation + +![Sequence diagram for Successful Operation](144e1d61e8738b22dcf4a683f869ac6f_img.jpg) + +``` +sequenceDiagram + participant NG-RAN Node + participant LMF + Note left of NG-RAN Node: + NG-RAN Node->>LMF: MEASUREMENT REPORT + Note right of LMF: +``` + +The diagram shows a sequence of messages between an NG-RAN Node and an LMF. The NG-RAN Node is on the left and the LMF is on the right. A solid arrow labeled "MEASUREMENT REPORT" points from the NG-RAN Node to the LMF. Both entities have a small horizontal bar at the bottom of their lifelines. + +Sequence diagram for Successful Operation + +**Figure 8.5.2.2.1: Measurement Report procedure. Successful operation.** + +The NG-RAN node initiates the procedure by sending a MEASUREMENT REPORT message to the LMF. The MEASUREMENT REPORT message contains the measurement results according to the associated measurement configuration. + +#### 8.5.2.3 Abnormal Conditions + +Void. + +### 8.5.3 Measurement Update + +#### 8.5.3.1 General + +The Measurement Update Procedure allows the LMF to notify the NG-RAN node of a change in a previously configured measurement. This procedure applies only if the NG-RAN node is a gNB. + +#### 8.5.3.2 Successful Operation + +![Sequence diagram showing the successful operation of a Measurement Update. An NG-RAN Node and an LMF are shown. A horizontal arrow labeled 'MEASUREMENT UPDATE' points from the LMF to the NG-RAN Node. Both entities have vertical lines extending downwards to a horizontal bar at the bottom, representing a timeline or sequence of events.](9f862801bce82634d3b5a1e0a195a799_img.jpg) + +``` +sequenceDiagram + participant NG-RAN Node + participant LMF + Note left of NG-RAN Node: + Note right of LMF: + LMF->>NG-RAN Node: MEASUREMENT UPDATE + Note left of NG-RAN Node: + Note right of LMF: +``` + +Sequence diagram showing the successful operation of a Measurement Update. An NG-RAN Node and an LMF are shown. A horizontal arrow labeled 'MEASUREMENT UPDATE' points from the LMF to the NG-RAN Node. Both entities have vertical lines extending downwards to a horizontal bar at the bottom, representing a timeline or sequence of events. + +**Figure 8.5.3.2.1: Measurement Update: Successful Operation.** + +The LMF initiates the procedure by sending a MEASUREMENT UPDATE message. + +If the *SRS Configuration* IE is included in the MEASUREMENT UPDATE message, the NG-RAN node shall overwrite the previously stored SRS configuration. + +If the *AoA Search Window Information* IE is included in the *TRP Measurement Update List* IE in the MEASUREMENT UPDATE message, the NG-RAN node shall clear any previously stored AoA search window information and store the newly received information. + +If the *Number of TRP Rx TEGs* IE is included in the *TRP Measurement Update List* IE in the MEASUREMENT UPDATE message, the NG-RAN node shall clear any previously stored information and store the newly received information. + +If the *Number of TRP RxTx TEGs* IE is included in the *TRP Measurement Update List* IE in the MEASUREMENT UPDATE message, the NG-RAN node shall clear any previously stored information and store the newly received information. + +If the *Measurement Characteristics Request Indicator* IE is included in the MEASUREMENT UPDATE message, the NG-RAN node shall clear any previously stored information and store the newly received information. + +If the *Measurement Time Occasion* IE is included in the MEASUREMENT UPDATE message, the NG-RAN node shall clear any previously stored information and store the newly received information. + +#### 8.5.3.3 Unsuccessful Operation + +Not applicable. + +#### 8.5.3.4 Abnormal Conditions + +If the NG-RAN node cannot identify at least one of the previously requested measurement to be modified, it shall consider the procedure as failed and initiate local error handling. + +### 8.5.4 Measurement Abort + +#### 8.5.4.1 General + +The purpose of the Measurement Abort Procedure is to enable the LMF to abort an on-going measurement. This procedure applies only if the NG-RAN node is a gNB. + +#### 8.5.4.2 Successful Operation + +![Sequence diagram for Measurement Abort Procedure: Successful Operation. The LMF sends a MEASUREMENT ABORT message to the NG-RAN Node.](26e334e61dd059cff029338a2a604d8d_img.jpg) + +``` +sequenceDiagram + participant LMF + participant NG-RAN Node + Note left of NG-RAN Node: + LMF->>NG-RAN Node: MEASUREMENT ABORT + Note right of NG-RAN Node: + Note left of LMF: + Note right of LMF: +``` + +Sequence diagram for Measurement Abort Procedure: Successful Operation. The LMF sends a MEASUREMENT ABORT message to the NG-RAN Node. + +**Figure 8.5.4.2.1: Measurement Abort Procedure: Successful Operation.** + +The LMF initiates the procedure by sending a MEASUREMENT ABORT message. + +Upon receiving this message, the NG-RAN node shall terminate the on-going measurement identified by the *LMF Measurement ID* IE and may release any resources previously allocated for the same measurement. + +#### 8.5.4.3 Unsuccessful Operation + +Not applicable. + +#### 8.5.4.4 Abnormal Conditions + +If the NG-RAN node cannot identify the previously requested measurement to be aborted, it shall ignore the MEASUREMENT ABORT message. + +### 8.5.5 Measurement Failure Indication + +#### 8.5.5.1 General + +The Measurement Failure Indication procedure allows the NG-RAN node to notify the LMF that the measurements previously requested with the Measurement procedure can no longer be reported. This procedure applies only if the NG-RAN node is a gNB. + +#### 8.5.5.2 Successful Operation + +![Sequence diagram for Measurement Failure Indication: Successful operation. The NG-RAN Node sends a MEASUREMENT FAILURE INDICATION message to the LMF.](b576eed4f7d3f33c6853abd24100a0ac_img.jpg) + +``` +sequenceDiagram + participant NG-RAN Node + participant LMF + Note left of NG-RAN Node: + NG-RAN Node->>LMF: MEASUREMENT FAILURE INDICATION + Note right of LMF: + Note left of NG-RAN Node: + Note right of NG-RAN Node: +``` + +Sequence diagram for Measurement Failure Indication: Successful operation. The NG-RAN Node sends a MEASUREMENT FAILURE INDICATION message to the LMF. + +**Figure 8.5.5.2.1: Measurement Report procedure. Successful operation.** + +Upon reception of the MEASUREMENT FAILURE INDICATION message, the LMF shall consider that the indicated measurements have been terminated by the NG-RAN node. + +#### 8.5.5.3 Abnormal Conditions + +Void. + +# 9 Elements for NRPPa Communication + +## 9.0 General + +Sub clauses 9.1 and 9.2 describe the structure of the messages and information elements required for the NRPPa protocol in tabular format. Sub clause 9.3 provides the corresponding ASN.1 definition. + +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 [2]. + +NOTE: The messages have been defined in accordance to the guidelines specified in TR 25.921 [5]. + +## 9.1 Message Functional Definition and Content + +### 9.1.1 Messages for Location Information Transfer Procedures + +#### 9.1.1.1 E-CID MEASUREMENT INITIATION REQUEST + +This message is sent by LMF to initiate E-CID measurements. + +Direction: LMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|-----------------------------------------------|-------|----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| LMF UE Measurement ID | M | | INTEGER
(1..15 ,..., 16..256) | | YES | reject | +| Report Characteristics | M | | ENUMERATED
(OnDemand, Periodic,...) | | YES | reject | +| Measurement Periodicity | C-
ifReportCh
aracteristi
csPeriodic | | ENUMERATED
(120ms, 240ms, 480ms, 640ms, 1024ms, 2048ms, 5120ms, 10240ms, 1min, 6min, 12min, 30min, 60min,..., 20480ms, 40960ms, extended) |

The codepoint 60min applies only for ng-eNB.

The codepoint “extended” is not applicable.

This IE is not applicable to NR Angle of Arrival.

| YES | reject | +| Measurement | | 1 | | | EACH | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------|-------------------------------------------------------------|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------|----------------------| +| Quantities | | | | | | | +| >Measurement Quantities Item | | 1.. | | | - | | +| >>Measurement Quantities Value | M | | ENUMERATED (Cell-ID, Angle of Arrival, Timing Advance Type 1, Timing Advance Type 2, RSRP, RSRQ, ..., SS-RSRP, SS-RSRQ, CSI-RSRP, CSI-RSRQ, NR Angle of Arrival, NR Timing Advance) | | - | - | +| Other-RAT Measurement Quantities | | 0 | | | EACH | ignore | +| >Other-RAT Measurement Quantities Item | | 0 .. | | | - | | +| >>Other-RAT Measurement Quantities Value | M | | ENUMERATED (GERAN, UTRAN, ..., NR, EUTRA) | | - | | +| WLAN Measurement Quantities | | 0 | | | EACH | ignore | +| >WLAN Measurement Quantities Item | | 0 .. | | | - | | +| >>WLAN Measurement Quantities Value | M | | ENUMERATED (WLAN, ...) | | - | | +| Measurement Periodicity NR-AoA | C-
ifReportCharacteristicsPeriodicAndMeasQuantityItemAoA | | ENUMERATED (160ms, 320ms, 640ms, 1280ms, 2560ms, 5120ms, 10240ms, 20480ms, 40960ms, 81920ms, 163840ms, 327680ms, 655360ms, 1310720ms, 2621440ms, ...) | | YES | reject | + +| Range bound | Explanation | +|-------------|-------------------------------------------------------------------------------------------------------| +| maxnoMeas | Maximum no. of measured quantities that can be configured and reported with one message. Value is 64. | + +| Condition | Explanation | +|-------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ifReportCharacteristicsPeriodic | This IE shall be present if the Report Characteristics IE is set to the value "Periodic". | +| ifReportCharacteristicsPeriodicAndMeasQuantityItemAoA | This IE shall be present if the Report Characteristics IE is set to the value "Periodic" and the Measurement Quantities Item IE is set to the value "NR Angle of Arrival". | + +#### 9.1.1.2 E-CID MEASUREMENT INITIATION RESPONSE + +This message is sent by NG-RAN node to indicate that the requested E-CID measurement is successfully initiated. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------|----------|-------|-------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| LMF UE Measurement ID | M | | INTEGER (1..15, ..., 16..256) | | YES | reject | +| RAN UE Measurement ID | M | | INTEGER (1..15, ..., 16..256) | | YES | reject | +| E-CID Measurement Result | O | | 9.2.5 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.2 | | YES | ignore | +| Cell Portion ID | O | | 9.2.12 | | YES | ignore | +| Other-RAT Measurement Result | O | | 9.2.13 | | YES | ignore | +| WLAN Measurement Result | O | | 9.2.14 | | YES | ignore | + +#### 9.1.1.3 E-CID MEASUREMENT INITIATION FAILURE + +This message is sent by NG-RAN node to indicate that the requested E-CID measurement cannot be initiated. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| LMF UE Measurement ID | M | | INTEGER (1..15, ..., 16..256) | | YES | reject | +| Cause | M | | 9.2.1 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.2 | | YES | ignore | + +#### 9.1.1.4 E-CID MEASUREMENT FAILURE INDICATION + +This message is sent by NG-RAN node to indicate that the previously requested E-CID measurement can no longer be reported. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-------------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | ignore | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| LMF UE Measurement ID | M | | INTEGER
(1..15,....,
16..256) | | YES | reject | +| RAN UE Measurement ID | M | | INTEGER
(1..15,....,
16..256) | | YES | reject | +| Cause | M | | 9.2.1 | | YES | ignore | + +#### 9.1.1.5 E-CID MEASUREMENT REPORT + +This message is sent by NG-RAN node to report the results of the requested E-CID measurement. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------|----------|-------|-------------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | ignore | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| LMF UE Measurement ID | M | | INTEGER
(1..15,....,
16..256) | | YES | reject | +| RAN UE Measurement ID | M | | INTEGER
(1..15,....,
16..256) | | YES | reject | +| E-CID Measurement Result | M | | 9.2.5 | | YES | ignore | +| Cell Portion ID | O | | 9.2.12 | | YES | ignore | + +#### 9.1.1.6 E-CID MEASUREMENT TERMINATION COMMAND + +This message is sent by the LMF to terminate the requested E-CID measurement. + +Direction: LMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-------------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | ignore | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| LMF UE Measurement ID | M | | INTEGER
(1..15,....,
16..256) | | YES | reject | +| RAN UE Measurement ID | M | | INTEGER
(1..15,....,
16..256) | | YES | reject | + +#### 9.1.1.7 OTDOA INFORMATION REQUEST + +This message is sent by LMF to request OTDOA information. + +Direction: LMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| OTDOA Information Type | | 1 | | | EACH | reject | +| >OTDOA Information Type Item | | 1 .. | | | - | | +| >>OTDOA Information Item | M | | ENUMERATED (pci, cellid, tac, earfcn, prsBandwidth, prsConfigIndex, cpLength, noDIFrames, noAntennaPorts, sFNInitTime, nG-RANAccessPointPosition, prsmutingconfiguration, prsid, tpid, tpType, crsCPLength, dlBandwidth, multipleprsConfigurationsperCell, prsOccasionGroup, prsFrequencyHoppingConfiguration, ..., tddConfig) | | - | | + +| Range bound | Explanation | +|-----------------|----------------------------------------------------------------------------------------------------------| +| maxnoOTDOAtypes | Maximum no. of OTDOA information types that can be requested and reported with one message. Value is 63. | + +#### 9.1.1.8 OTDOA INFORMATION RESPONSE + +This message is sent by NG-RAN node to provide OTDOA information. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------------------------|-----------------------|-------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| OTDOA Cells | | 1 .. | | Served cells/TPs that broadcast PRS. May be used to signal multiple PRS | GLOBAL | ignore | + +| | | | | | | | +|-------------------------|---|--|--------|----------------------------------------------------------------------|-----|--------| +| | | | | configurations per cell/TPs (up to 3 are supported in this release). | | | +| >OTDOA Cell Information | M | | 9.2.15 | | - | | +| Criticality Diagnostics | O | | 9.2.2 | | YES | ignore | + +| Range bound | Explanation | +|------------------|---------------------------------------------------------------------| +| maxCellInRANnode | Maximum no. cells that can be served by a RAN Node. Value is 16384. | + +#### 9.1.1.9 OTDOA INFORMATION FAILURE + +This message is sent by NG-RAN node to indicate that the OTDOA information cannot be provided. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| Cause | M | | 9.2.1 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.2 | | YES | ignore | + +#### 9.1.1.10 POSITIONING INFORMATION REQUEST + +This message is sent by the LMF to request positioning information. + +Direction: LMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------|--------------------------|-------|--------------------------------------------------------------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| Requested SRS Transmission Characteristics | O | | 9.2.27 | | YES | ignore | +| UE Reporting Information | O | | 9.2.70 | | YES | ignore | +| UE TEG Information Request | O | | ENUMERATED (onDemand, periodic, stop, ...) | | YES | ignore | +| UE TEG Reporting Periodicity | C-ifUeTegInfoReqPeriodic | | ENUMERATED (160ms, 320ms, 1280ms, 2560ms, 61440ms, 81920ms, 368640ms, 737280ms, ...) | | YES | reject | + +| Condition | Explanation | +|-----------|-------------| +|-----------|-------------| + +| | | +|------------------------|------------------------------------------------------------------------------------------------------| +| ifUeTegInfoReqPeriodic | This IE shall be present if the UE TEG Information Request IE is set to the value "periodic". | +|------------------------|------------------------------------------------------------------------------------------------------| + +#### 9.1.1.11 POSITIONING INFORMATION RESPONSE + +This message is sent by the NG-RAN node to provide positioning information. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------|----------|-------|---------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| SRS Configuration | O | | 9.2.28 | | YES | ignore | +| SFN Initialisation Time | O | | Relative Time
1900
9.2.36 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.2 | | YES | ignore | +| UE Tx TEG Association List | O | | 9.2.78 | | YES | ignore | +| New NR CGI | O | | NR CGI
9.2.9 | | YES | ignore | + +#### 9.1.1.12 POSITIONING INFORMATION FAILURE + +This message is sent by the NG-RAN node to indicate that the positioning information cannot be provided. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| Cause | M | | 9.2.1 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.2 | | YES | ignore | + +#### 9.1.1.13 POSITIONING INFORMATION UPDATE + +This message is sent by the NG-RAN node to indicate that a change in the SRS configuration or UE Tx TEG association has occurred. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------|----------|-------|---------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | ignore | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| SRS Configuration | O | | 9.2.28 | | YES | ignore | +| SFN Initialisation Time | O | | Relative Time
1900
9.2.36 | | YES | ignore | +| UE Tx TEG Association List | O | | 9.2.78 | | YES | ignore | +| SRS Transmission Status | O | | ENUMERATED
(stopped, ...) | | YES | ignore | + +#### 9.1.1.14 TRP INFORMATION REQUEST + +This message is sent by an LMF to request information for TRPs hosted by an NG-RAN node. + +Direction: LMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------|----------|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| TRP List | | 0 ..1 | | | YES | ignore | +| >TRP Item | | 1 ..
| | | EACH | ignore | +| >>TRP ID | M | | 9.2.24 | | - | | +| TRP Information Type List | | 1 | | | | | +| >TRP Information Type Item | | 1 ..
| | | EACH | reject | +| >>TRP Information Type Item | M | | ENUMERATED
(nr pci, ng-ran
cgi, nr arfcn, prs
config, ssb
config, sfn init
time, spatial
direction info,
geo-
coordinates, ...,
trp type, on-
demand prs, trp
tx teg, beam
antenna info,
mobile trp
location info,
common ta) | | - | | + +| Range bound | Explanation | +|-------------------|-------------------------------------------------------------------------------------------------------| +| maxnoTRPs | Maximum no. of TRPs in a NG-RAN node. Value is 65535 | +| maxnoTRPInfoTypes | Maximum no of TRP information types that can be requested and reported with one message. Value is 64. | + +#### 9.1.1.15 TRP INFORMATION RESPONSE + +This message is sent by an NG-RAN node to convey TRP information to an LMF. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| TRP Information List | | 1 | | | YES | ignore | + +| | | | | | | | +|---------------------------------|---|------------------|--------|--|------|--------| +| >TRP Information Item | M | 1 .. | | | EACH | ignore | +| >>TRP Information | M | | 9.2.25 | | - | | +| Criticality Diagnostics | O | | 9.2.2 | | YES | ignore | + +| Range bound | Explanation | +|-------------|-------------------------------------------------------| +| maxnoTRPs | Maximum no. of TRPs in a NG-RAN node. Value is 65535. | + +#### 9.1.1.16 TRP INFORMATION FAILURE + +This message is sent by an NG-RAN node to indicate that the requested TRP information cannot be provided to an LMF. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| Cause | M | | 9.2.1 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.2 | | YES | ignore | + +#### 9.1.1.17 POSITIONING ACTIVATION REQUEST + +This message is sent by the LMF to cause the NG RAN node to activate/trigger UL SRS transmission by the UE. + +Direction: LMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|-------|-------------------------------------|-----------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| CHOICE SRS type | M | | | | YES | reject | +| >Semi-persistent | | | | | | | +| >>SRS Resource Set ID | M | | 9.2.33 | | - | | +| >>SRS Spatial Relation | O | | Spatial Relation Information 9.2.34 | This IE is ignored if the Spatial Relation Information per SRS Resource IE is present. | YES | ignore | +| >>Spatial Relation Information per SRS Resource | O | | 9.2.60 | | YES | ignore | +| >Aperiodic | | | | | | | +| >>Aperiodic | M | | ENUMERATED (true,...) | | - | | +| >>SRS Resource Trigger | O | | 9.2.35 | | - | | +| Activation Time | O | | Relative Time 1900 9.2.36 | Indicates the start time when the SRS activation is requested | YES | ignore | + +#### 9.1.1.18 POSITIONING ACTIVATION RESPONSE + +This message is sent by NG-RAN node to confirm successful UL SRS activation in the UE. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| Criticality Diagnostics | O | | 9.2.2 | | YES | ignore | +| System Frame Number | O | | INTEGER(0..1023) | | YES | ignore | +| Slot Number | O | | INTEGER(0..79) | | YES | ignore | + +#### 9.1.1.19 POSITIONING ACTIVATION FAILURE + +This message is sent by NG-RAN node to indicate that activation of UL SRS transmission in the UE was unsuccessful. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| Cause | M | | 9.2.1 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.2 | | YES | ignore | + +#### 9.1.1.20 POSITIONING DEACTIVATION + +This message is sent by the LMF to cause the NG RAN node to deactivate UL SRS transmission or release all the transmission by the UE. + +Direction: LMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | ignore | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| CHOICE Abort Transmission | M | | | | YES | ignore | +| > Deactivate SRS Resource Set | | | | | | | +| >>SRS Resource Set ID | M | | 9.2.33 | | - | | +| > Release ALL | | | NULL | the NG-RAN node configures UE to stop transmitting SRS for the positioning purpose | | | + +#### 9.1.1.21 PRS CONFIGURATION REQUEST + +This message is sent by the LMF to request the NG-RAN node to configure or update PRS transmission. + +Direction: LMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|------------------|----------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| PRS Configuration Request Type | M | | ENUMERATED (configure, off, ...) | | YES | reject | +| PRS TRP List | | 1 | | | YES | ignore | +| >PRS TRP Item | | 1 .. | | | EACH | ignore | +| >>TRP ID | M | | 9.2.24 | | - | | +| >>Requested DL PRS Transmission Characteristics | C-ifConf | | 9.2.61 | | - | | +| >>PRS Transmission Off Information | C-ifOff | | 9.2.64 | | - | | + +| Range bound | Explanation | +|-------------|------------------------------------------------------| +| maxnoTRPs | Maximum no. of TRPs in a NG-RAN node. Value is 65535 | + +| Condition | Explanation | +|-----------|-----------------------------------------------------------------------------------------------------------| +| ifConf | This IE shall be present if the PRS Configuration Request Type IE is set to the value "configure". | +| ifOff | This IE shall be present if the PRS Configuration Request Type IE is set to the value "off". | + +#### 9.1.1.22 PRS CONFIGURATION RESPONSE + +This message is sent by the NG-RAN node to acknowledge configuring or updating the PRS transmission. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------|----------|------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| PRS Transmission TRP List | | 0..1 | | | YES | ignore | +| >PRS Transmission TRP Item | | 1 .. | | | EACH | ignore | +| >>TRP ID | M | | 9.2.24 | | - | | +| >>PRS Configuration | M | | 9.2.44 | | - | | +| Criticality Diagnostics | O | | 9.2.2 | | YES | ignore | + +| Range bound | Explanation | +|-------------|------------------------------------------------------| +| maxnoTRPs | Maximum no. of TRPs in a NG-RAN node. Value is 65535 | + +#### 9.1.1.23 PRS CONFIGURATION FAILURE + +This message is sent by the NG-RAN node to indicate that it cannot configure any PRS transmission. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| Cause | M | | 9.2.1 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.2 | | YES | ignore | + +#### 9.1.1.24 MEASUREMENT PRECONFIGURATION REQUIRED + +This message is sent by the LMF to provide the PRS configuration information of multiple TRPs to the NG-RAN node and request to configure measurement gap or PRS processing window of the UE. + +Direction: LMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|----------|---------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| TRP PRS Information List | | 1 | | | YES | ignore | +| >TRP PRS Information Item | | 1 .. | | | EACH | ignore | +| >>TRP ID | M | | 9.2.24 | | - | | +| >>NR PCI | M | | INTEGER (0..1007) | | - | | +| >>NR CGI | O | | 9.2.9 | | - | | +| >>PRS Configuration | M | | 9.2.44 | | - | | + +| Range bound | Explanation | +|--------------|-----------------------------------------------------------------------| +| maxnoPRSTRPs | Maximum no. of TRPs for on-demand PRS in a NG-RAN node. Value is 256. | + +#### 9.1.1.25 MEASUREMENT PRECONFIGURATION CONFIRM + +This message is sent by the NG-RAN node to the LMF to confirm successful configuration of measurement gap or PRS processing window of the UE. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| Preconfiguration Result | M | | BIT STRING (SIZE(8)) | Indicates what has been preconfigured in the UE.
first bit: measurement gaps
second bit: PRS processing windows.

Other bits reserved for future use. Value '1' indicates 'has been preconfigured', Value '0' indicates 'not preconfigured'. | YES | ignore | +| Criticality Diagnostics | O | | 9.2.2 | | YES | ignore | + +#### 9.1.1.26 MEASUREMENT PRECONFIGURATION REFUSE + +This message is sent by the NG-RAN node to indicate that configuration of measurement gap or PRS processing window of the UE was unsuccessful. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| Cause | M | | 9.2.1 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.2 | | YES | ignore | + +#### 9.1.1.27 MEASUREMENT ACTIVATION + +This message is sent by the LMF to request the NG-RAN node to activate or deactivate the preconfigured measurement gap or PRS processing window for the UE. + +Direction: LMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------|----------|-------|----------------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | ignore | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| Request Type | M | | ENUMERATED (activate, deactivate, ...) | | YES | reject | +| PRS Measurement Info List | | 0..1 | | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-----------------------|-------------------------------------------------------------------|----------------------------------------------|-------------|----------------------| +| >PRS Measurement Info Item | | 1 .. < maxFreqLayers> | | | - | | +| >>Point A | M | | INTEGER (0..3279165) | | - | | +| >>MeasPRS Periodicity | M | | ENUMERATED (ms20, ms40, ms80, ms160, ...) | Measurement gap periodicity in units of ms | - | | +| >>MeasPRS Offset | M | | INTEGER (0..159, ...) | Measurement gap offset in units of subframes | - | | +| >>Measurement PRS Length | M | | ENUMERATED {ms1dot5, ms3, ms3dot5, ms4, ms5dot5, ms6, ms10, ms20} | | - | | + +| Range bound | Explanation | +|---------------|---------------------------------------------| +| maxFreqLayers | Maximum no. of frequency layers. Value is 4 | + +### 9.1.2 Messages for Management Procedures + +#### 9.1.2.1 ERROR INDICATION + +This message is used to indicate that some error has been detected in the NG-RAN node or in the LMF. + +Direction: LMF → NG-RAN node and NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | ignore | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| Cause | O | | 9.2.1 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.2 | | YES | ignore | + +### 9.1.3 Messages for Assistance Information Transfer Procedures + +#### 9.1.3.1 ASSISTANCE INFORMATION CONTROL + +This message is sent by the LMF to transfer assistance information. + +Direction: LMF → NG-RAN Node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------|----------|-------|-------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| Assistance Information | O | | 9.2.19 | | YES | reject | +| Broadcast | O | | ENUMERATED (start, stop, ...) | | YES | reject | + +| | | | | | | | +|-----------------------------|---|--|--------|----------------------------------------------------------------------------------------------------------|-----|--------| +| Positioning Broadcast Cells | O | | 9.2.59 | The cell(s) that are requested to broadcast posSIB(s) according to the Assistance Information IE. | YES | reject | +|-----------------------------|---|--|--------|----------------------------------------------------------------------------------------------------------|-----|--------| + +#### 9.1.3.2 ASSISTANCE INFORMATION FEEDBACK + +This message is sent by the NG-RAN Node to give feedback on assistance information broadcasting. + +Direction: NG-RAN Node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| Assistance Information Failure List | O | | 9.2.23 | | YES | reject | +| Positioning Broadcast Cells | O | | 9.2.59 | The cells associated to the feedback provided in the Assistance Information Failure List IE. | YES | reject | +| Criticality Diagnostics | O | | 9.2.2 | | YES | ignore | + +### 9.1.4 Messages for Measurement Information Transfer Procedures + +#### 9.1.4.1 MEASUREMENT REQUEST + +This message is sent by the LMF to request the NG-RAN node to configure a positioning measurement. + +Direction: LMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-----------------------|-------------------------------|------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| LMF Measurement ID | M | | INTEGER (1..65536, ...) | | YES | reject | +| TRP Measurement Request List | | 1 | | | YES | reject | +| >TRP Measurement Request Item | | 1.. | | | EACH | reject | +| >>TRP ID | M | | 9.2.24 | | - | | +| >>Search Window Information | O | | 9.2.26 | | - | | +| >>Cell ID | O | | NR CGI 9.2.9 | The Cell ID of the TRP identified by the TRP ID IE. | YES | ignore | +| >>AoA Search Window Information | O | | UL-AoA Assistance Information | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|-----------------------------------------------|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | 9.2.66 | | | | +| >>Number of TRP Rx TEGs | O | | ENUMERATED (2, 3, 4, 6, 8, ...) | | YES | ignore | +| >>Number of TRP RxTx TEGs | O | | ENUMERATED (2, 3, 4, 6, 8, ...) | | YES | ignore | +| Report Characteristics | M | | ENUMERATED (OnDemand, Periodic, ...) | | YES | reject | +| Measurement Periodicity | C-
ifReportCh
aracteristi
csPeriodic | | ENUMERATED (120ms, 240ms, 480ms, 640ms, 1024ms, 2048ms, 5120ms, 10240ms, 1min, 6min, 12min, 30min, 60min, ..., 20480ms, 40960ms, extended) | The codepoint 120ms, 240ms, 480ms, 1024ms, 2048ms, 1min, 6min, 12min, 30min, and 60min are not applicable | YES | reject | +| TRP Measurement Quantities | | 1 | | | YES | reject | +| >TRP Measurement Quantities Item | | 1 ..
osMeas> | | | EACH | reject | +| >>TRP Measurement Type | M | | ENUMERATED (gNB-RxTxTimeDiff, UL-SRS-RSRP, UL-AoA, UL-RTOA, ..., Multiple UL-AoA, UL SRS-RSRPP) | | - | | +| >>Timing Reporting Granularity Factor | O | | INTEGER (0..5) | Value (0..5) corresponds to (k0..k5) TS 38.133 [16] | - | | +| SFN initialisation Time | O | | Relative Time 1900 9.2.36 | If this IE is not present, the TRP may assume that the value is same as its own SFN initialisation time. | YES | ignore | +| SRS Configuration | O | | 9.2.28 | | YES | ignore | +| Measurement Beam Information Request | O | | ENUMERATED (true,...) | This IE is ignored when the Measurement Characteristics Request Indicator IE is included. | YES | ignore | +| System Frame Number | O | | INTEGER(0..1023) | | YES | ignore | +| Slot Number | O | | INTEGER(0..79) | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------|--------------------|-------|---------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Measurement Periodicity Extended | C-
ifMeasPerExt | | )
ENUMERATED
(160ms, 320ms, 1280ms, 2560ms, 61440ms, 81920ms, 368640ms, 737280ms, 1843200ms, ...) | | YES | reject | +| Response Time | O | | 9.2.68 | This IE is ignored when the Report Characteristics IE is set to "periodic". | YES | ignore | +| Measurement Characteristics Request Indicator | O | | 9.2.81 | | YES | ignore | +| Measurement Time Occasion | O | | ENUMERATED
(o1, o4, ...) | | YES | ignore | +| Measurement Amount | O | | ENUMERATED
(0, 1, 2, 4, 8, 16, 32, 64) | This IE is ignored if the Report Characteristics IE is set to 'OnDemand'. Value 0 represents an infinite number of periodic reporting. | YES | ignore | + +| Condition | Explanation | +|---------------------------------|---------------------------------------------------------------------------------------------------| +| ifReportCharacteristicsPeriodic | This IE shall be present if the Report Characteristics IE is set to the value "Periodic". | +| ifMeasPerExt | This IE shall be present if the Measurement Periodicity IE is set to the value "extended". | + +| Range bound | Explanation | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------| +| maxnoPosMeas | Maximum no. of measured quantities that can be configured and reported with one positioning measurement message. Value is 16384. | +| maxnoofMeasTRPs | Maximum no. of TRPs that can be included within one message. Value is 64. | + +#### 9.1.4.2 MEASUREMENT RESPONSE + +This message is sent by the NG-RAN node to report positioning measurements for the target UE. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| LMF Measurement ID | M | | INTEGER | | YES | reject | + +| | | | | | | | +|------------------------------------------|---|----------------------|----------------------------|-----------------------------------------------------|------|--------| +| | | | (1..65536, ...) | | | | +| RAN Measurement ID | M | | INTEGER
(1..65536, ...) | | YES | reject | +| TRP Measurement Response List | | 0..1 | | | YES | reject | +| >TRP Measurement Response Item | | 1.. | | | EACH | reject | +| >>TRP ID | M | | 9.2.24 | | - | | +| >>TRP Measurement Result | M | | 9.2.37 | | - | | +| >>Cell ID | O | | NR CGI
9.2.9 | The Cell ID of the TRP identified by the TRP ID IE. | YES | ignore | +| Criticality Diagnostics | O | | 9.2.2 | | YES | ignore | + +| Range bound | Explanation | +|-----------------|---------------------------------------------------------------------------| +| maxnoofMeasTRPs | Maximum no. of TRPs that can be included within one message. Value is 64. | + +#### 9.1.4.3 MEASUREMENT FAILURE + +This message is sent by the NG-RAN node to report measurement failure. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|----------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| LMF Measurement ID | M | | INTEGER
(1..65536, ...) | | YES | reject | +| Cause | M | | 9.2.1 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.2 | | YES | ignore | + +#### 9.1.4.4 MEASUREMENT REPORT + +This message is sent by the NG-RAN node to report positioning measurements for the target UE. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------|----------|----------------------|----------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| LMF Measurement ID | M | | INTEGER
(1..65536, ...) | | YES | reject | +| RAN Measurement ID | M | | INTEGER
(1..65536, ...) | | YES | reject | +| TRP Measurement Response List | | 1 | | | YES | reject | +| >TRP Measurement Response Item | | 1.. | | | EACH | reject | +| >>TRP ID | M | | 9.2.24 | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------|----------|-------|-----------------------|------------------------------------------------------------|-------------|----------------------| +| >>TRP Measurement Result | M | | 9.2.37 | | - | | +| >>Cell ID | O | | NR CGI 9.2.9 | The Cell ID of the TRP identified by the TRP ID IE. | YES | ignore | + +| Range bound | Explanation | +|-----------------|---------------------------------------------------------------------------| +| maxnoofMeasTRPs | Maximum no. of TRPs that can be included within one message. Value is 64. | + +#### 9.1.4.5 MEASUREMENT UPDATE + +This message is sent by the LMF to update a previously configured measurement. + +Direction: LMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------|----------|-----------------------|--------------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | ignore | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| LMF Measurement ID | M | | INTEGER (1..65536, ...) | | YES | reject | +| RAN Measurement ID | M | | INTEGER (1..65536, ...) | | YES | reject | +| SRS Configuration | O | | 9.2.28 | | YES | ignore | +| TRP Measurement Update List | | 0..1 | | | YES | reject | +| >TRP Measurement Update Item | | 1.. | | | EACH | reject | +| >>TRP ID | M | | 9.2.24 | | - | | +| >>AoA Search Window Information | O | | UL-AoA Assistance Information 9.2.66 | | YES | ignore | +| >>Number of TRP Rx TEGs | O | | ENUMERATED (2, 3, 4, 6, 8, ...) | | YES | ignore | +| >>Number of TRP RxTx TEGs | O | | ENUMERATED (2, 3, 4, 6, 8, ...) | | YES | ignore | +| Measurement Characteristics Request Indicator | O | | 9.2.81 | | YES | ignore | +| Measurement Time Occasion | O | | ENUMERATED (o1, o4, ...) | | YES | ignore | + +| Range bound | Explanation | +|-----------------|---------------------------------------------------------------------------| +| maxnoofMeasTRPs | Maximum no. of TRPs that can be included within one message. Value is 64. | + +#### 9.1.4.6 MEASUREMENT ABORT + +This message is sent by the LMF to request the NG-RAN node to abort a measurement. + +Direction: LMF → NG-RAN node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|----------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| LMF Measurement ID | M | | INTEGER
(1..65536, ...) | | YES | reject | +| RAN Measurement ID | M | | INTEGER
(1..65536, ...) | | YES | reject | + +#### 9.1.4.7 MEASUREMENT FAILURE INDICATION + +This message is sent by the NG-RAN node to indicate that the previously requested measurements can no longer be reported. + +Direction: NG-RAN node → LMF. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|----------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3 | | YES | reject | +| NRPPa Transaction ID | M | | 9.2.4 | | - | | +| LMF Measurement ID | M | | INTEGER
(1..65536, ...) | | YES | reject | +| RAN Measurement ID | M | | INTEGER
(1..65536, ...) | | YES | reject | +| Cause | M | | 9.2.1 | | YES | ignore | + +## 9.2 Information Element definitions + +### 9.2.0 General + +When specifying information elements which are to be represented by bit strings, 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 bit strings from other specifications, the first bit of the bit string contains the first bit of the concerned information. + +### 9.2.1 Cause + +The purpose of the cause information element is to indicate the reason for a particular event for the whole 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,
Requested Item not Supported,
Requested Item Temporarily not Available,
..., Serving NG-RAN node changed,
Requested Item not Supported on Time ) | | +| > 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,
Unspecified,
Abstract Syntax Error (Falsely Constructed Message),
...) | | +| > Misc | | | | | +| >>Miscellaneous Cause | M | | ENUMERATED
(Unspecified,
...) | | + +The meaning of the different cause values is described in the following table. In general, "not supported" cause values indicate that the concerned capability is missing. On the other hand, "not available" cause values indicate that the concerned capability is present, but insufficient resources were available to perform the requested action. + +| Radio Network Layer cause | Meaning | +|------------------------------------------|----------------------------------------------------------------------------------------------------------------------| +| Unspecified | Sent when none of the above cause values applies but still the cause is Radio Network Layer related | +| Requested Item not Supported | The NG-RAN node does not support the requested measurement object, or cannot provide the requested information item. | +| Requested Item Temporarily not Available | The NG-RAN node can temporarily not provide the requested measurement object or information item. | +| Serving NG-RAN node changed | The UE has moved to another serving NG-RAN node. | +| Requested Item not Supported on Time | The NG-RAN node is unable to provide the measurement results on time. | + +| Protocol cause | Meaning | +|--------------------------------|--------------------------------------------------------------------------| +| Abstract Syntax Error (Reject) | The received message included an abstract syntax error and the concerned | + +| Protocol cause | Meaning | +|-----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| | criticality indicated "reject" (see sub clause 10.3 of TS 38.413) | +| Abstract Syntax Error (Ignore and Notify) | The received message included an abstract syntax error and the concerned criticality indicated "ignore and notify" (see sub clause 10.3 of TS 38.413) | +| Abstract syntax error (falsely constructed message) | The received message contained IEs or IE groups in wrong order or with too many occurrences (see sub clause 10.3 of TS 38.413) | +| Message not Compatible with Receiver State | The received message was not compatible with the receiver state (see sub clause 10.4 of TS 38.413) | +| Semantic Error | The received message included a semantic error (see sub clause 10.4 of TS 38.413) | +| Transfer Syntax Error | The received message included a transfer syntax error (see sub clause 10.2 of TS 38.413) | +| Unspecified | Sent when none of the above cause values applies but still the cause is Protocol related | + +| Miscellaneous cause | Meaning | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Unspecified | 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 or Protocol. | + +### 9.2.2 Criticality Diagnostics + +The *Criticality Diagnostics* IE is sent by the NG-RAN node or LMF 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 *NRPPa Transaction ID* IE are described in 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, successful outcome, unsuccessful outcome) | The Triggering 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). | +| NRPPa Transaction ID | O | | 9.2.4 | | +| 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" shall not be used. | +| >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 | +|---------------|------------------------------------------------------------------------------------------------------------| +| maxNrOfErrors | Maximum no. of IE errors allowed to be reported with a single message. The value for maxNrOfErrors is 256. | + +### 9.2.3 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 | +|-----------------|----------|-------|----------------------------------------------------------------------------|-----------------------| +| Procedure Code | M | | INTEGER (0..255) | | +| Type of Message | M | | CHOICE (Initiating Message, Successful Outcome, Unsuccessful Outcome, ...) | | + +### 9.2.4 NRPPa Transaction ID + +The *NRPPa Transaction ID* IE is used to associate all the messages belonging to the same procedure. Messages belonging to the same procedure shall use the same NRPPa Transaction ID. + +The NRPPa Transaction ID is determined by the initiating peer of a procedure. + +The NRPPa Transaction ID shall uniquely identify a procedure among all ongoing parallel procedures using the same procedure code, and initiated by the same protocol peer. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|----------|-------|-----------------------|-----------------------| +| NRPPa Transaction ID | M | | INTEGER (0..32767) | | + +### 9.2.5 E-CID Measurement Result + +The purpose of the E-CID Measurement Result information element is to provide the E-CID measurement result. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------|----------|-------|-----------------------|-------------------------------|-------------|----------------------| +| Serving Cell ID | M | | NG-RAN CGI 9.2.6 | NG-RAN Cell Identifier of the | - | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------|----------|---------------------|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | serving cell | | | +| Serving Cell TAC | M | | TAC
9.2.11 | Tracking Area Code of the serving cell | - | | +| NG-RAN Access Point Position | O | | 9.2.10 | The configured estimated geographical position of the antenna of the cell.
If the Geographical Coordinates IE is used, the NG-RAN Access Point Position IE shall be ignored. | - | | +| Measured Results | | 0..1 | | Measurement results of the serving RAT. | - | | +| >CHOICE Measured Results Value | | 1 .. | | | - | | +| >>Value Angle of Arrival EUTRA | | | INTEGER (0..719) | According to mapping in TS 36.133 [9] | | | +| >>Value Timing Advance Type 1 EUTRA | | | INTEGER (0..7690) | As defined in TS 36.214 [17] | | | +| >>Value Timing Advance Type 2 EUTRA | | | INTEGER (0..7690) | As defined in TS 36.214 [17] | | | +| >>Result RSRP EUTRA | | | | | | | +| >>>Result RSRP EUTRA Item | | 1 .. | | | - | | +| >>>>PCI EUTRA | M | | INTEGER (0..503) | Physical Cell Identifier of the reported E-UTRA cell | - | | +| >>>>EARFCN | M | | INTEGER (0..262143, ...) | Corresponds to NDL for FDD and NDL/UL for TDD in ref. TS 36.104 [7] | - | | +| >>>>CGI EUTRA | O | | 9.2.7 | Cell Global Identifier of the reported E-UTRA cell | - | | +| >>>>Value RSRP EUTRA | M | | INTEGER (0..97, ...) | | - | | +| >>Result RSRQ EUTRA | | | | | | | +| >>>Result RSRQ EUTRA Item | | 1 .. | | | - | | +| >>>>PCI EUTRA | M | | INTEGER (0..503) | Physical Cell Identifier of the | - | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------|----------|-------------------------|--------------------------|---------------------------------------------------------------------|-------------|----------------------| +| | | | | reported E-UTRA cell | | | +| >>>>EARFCN | M | | INTEGER (0..262143, ...) | Corresponds to NDL for FDD and NDL/UL for TDD in ref. TS 36.104 [7] | - | | +| >>>>CGI EUTRA | O | | 9.2.7 | Cell Global Identifier of the reported E-UTRA cell | - | | +| >>>>Value RSRQ EUTRA | M | | INTEGER (0..34, ...) | | - | | +| >>Result SS-RSRP | | | | | YES | ignore | +| >>>Result SS-RSRP Item | | 1 .. | | | - | | +| >>>>NR PCI | M | | INTEGER (0..1007) | | - | | +| >>>>NR ARFCN | M | | INTEGER (0..3279165) | | - | | +| >>>>NR CGI | O | | 9.2.9 | | - | | +| >>>>Value SS-RSRP Cell | O | | INTEGER (0..127) | SS-RSRP measurement aggregated at cell level | - | | +| >>>>SS-RSRP per SSB Resource | | 0..1 | | | - | | +| >>>>>SS-RSRP per SSB Resource Item | | 1 .. | | | - | | +| >>>>>SSB Index | M | | INTEGER (0..63) | | - | | +| >>>>>Value SS-RSRP | M | | INTEGER (0..127) | SS-RSRP measurement per SSB resource | - | | +| >>Result SS-RSRQ | | | | | YES | ignore | +| >>>Result SS-RSRQ-Item | | 1 .. | | | - | | +| >>>>NR PCI | M | | INTEGER (0..1007) | | - | | +| >>>>NR ARFCN | M | | INTEGER (0..3279165) | | - | | +| >>>>NR CGI | O | | 9.2.9 | | - | | +| >>>>Value SS-RSRQ Cell | O | | INTEGER (0..127) | SS-RSRQ measurement aggregated at cell level | - | | +| >>>>SS-RSRQ per SSB Resource | | 0..1 | | | - | | +| >>>>>SS- | | 1 .. | | | - | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------|----------|-------------------------|-----------------------|-----------------------------------------------|-------------|----------------------| +| RSRQ PerSSB Resource Item | | | | | | | +| >>>>>>SSB Index | M | | INTEGER (0..63) | | - | | +| >>>>>>Value SS-RSRQ | M | | INTEGER (0..127) | SS-RSRQ measurement per SSB resource | - | | +| >>Result CSI-RSRP | | | | | YES | ignore | +| >>>Result CSI-RSRP Item | | 1 .. | | | - | | +| >>>>NR PCI | M | | INTEGER (0..1007) | | - | | +| >>>>NR ARFCN | M | | INTEGER (0..3279165) | | - | | +| >>>>NR CGI | O | | 9.2.9 | | - | | +| >>>>Value CSI-RSRP Cell | O | | INTEGER (0..127) | CSI-RSRP measurement aggregated at cell level | - | | +| >>>>CSI-RSRP per CSI-RS Resource | | 0..1 | | | - | | +| >>>>>CSI-RSRP per CSI-RS Resource Item | | 1.. | | | - | | +| >>>>>>CSI-RS Index | M | | INTEGER (0..95) | | - | | +| >>>>>>Value CSI-RSRP | M | | INTEGER (0..127) | CSI-RSRP measurement per CSI-RS resource | - | | +| >>Result CSI-RSRQ | | | | | YES | ignore | +| >>>Result CSI-RSRQ Item | | 1 .. | | | - | | +| >>>>NR PCI | M | | INTEGER (0..1007) | | - | | +| >>>>NR ARFCN | M | | INTEGER (0..3279165) | | - | | +| >>>>NR CGI | O | | 9.2.9 | | - | | +| >>>>Value CSI-RSRQ Cell | O | | INTEGER (0..127) | CSI-RSRQ measurement aggregated at cell level | - | | +| >>>>CSI-RSRQ per CSI-RS Resource | | 0..1 | | | - | | +| >>>>>CSI-RSRQ per CSI-RS Resource | | 1 .. | | | - | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------|----------|-------|----------------------------------------|-------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Item | | | | | | | +| >>>>>>CSI-RS Index | M | | INTEGER (0..95) | | - | | +| >>>>>>Value CSI-RSRQ | M | | INTEGER (0..127) | CSI-RSRQ measurement per CSI-RS resource | - | | +| >>Angle of Arrival NR | | | UL Angle of Arrival 9.2.38 | | YES | ignore | +| >>Value Timing Advance NR | | | INTEGER (0..7690) | As defined in TS 38.215 [19] | YES | ignore | +| Geographical Coordinates | O | | 9.2.46 | | YES | ignore | +| Mobile Access Point Location Information | O | | Mobile TRP Location Information 9.2.88 | The location information of the mobile access point of the cell that is associated to the mobile TRP. | YES | ignore | + +| Range bound | Explanation | +|------------------|-------------------------------------------------------------------------------------------------------| +| maxnoMeas | Maximum no. of measured quantities that can be configured and reported with one message. Value is 64. | +| maxCellReport | Maximum no. of cells that can be reported with one message. Value is 9. | +| maxCellReportNR | Maximum no. of NR cells that can be reported with one message. Value is 9. | +| maxIndexesReport | Maximum no. of beam level measurement results that can be reported with one message. Value is 64. | + +### 9.2.6 NG-RAN CGI + +The NG-RAN Cell Global Identifier (CGI) is used to globally identify a cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|-----------------------|-----------------------| +| PLMN identity | M | | 9.2.8 | | +| CHOICE NG-RAN Cell | M | | | | +| >NR Cell | | | | | +| >>NR Cell Identifier | M | | BIT STRING (36) | | +| >E-UTRAN Cell | | | | | +| >>E-UTRAN Cell Identifier | M | | BIT STRING (28) | | + +### 9.2.7 CGI EUTRA + +The Cell Global Identifier EUTRA is used to globally identify an E-UTRA cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-----------------------|-----------------------| +| PLMN identity | M | | 9.2.8 | | +| E-UTRA Cell Identifier | M | | BIT STRING (28) | | + +### 9.2.8 PLMN Identity + +This IE 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

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 3 digit MNC).
| + +### 9.2.9 NR CGI + +The Cell Global Identifier NR is used to globally identify an NR cell. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|-----------------------|-----------------------| +| PLMN Identity | M | | 9.2.8 | | +| NR Cell Identity | M | | BIT STRING (SIZE(36)) | | + +### 9.2.10 NG-RAN Access Point Position + +The *NG-RAN Access Point Position* IE is used to identify the geographical position of an NG-RAN Access Point. It is expressed as ellipsoid point with altitude and uncertainty ellipsoid according to TS 23.032 [8]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Latitude Sign | M | | ENUMERATED (North, South) | | +| Degrees Of Latitude | M | | INTEGER ( $0..2^{23}-1$ ) |

The IE value (N) is derived by this formula:

$N \leq 2^{23} \times X / 90 < N+1$

X being the latitude in degrees (0^\circ..90^\circ).

| +| Degrees Of Longitude | M | | INTEGER ( $-2^{23}..2^{23}-1$ ) |

The IE value (N) is derived by this formula:

$N \leq 2^{24} \times X / 360 < N+1$

X being the longitude in degrees (-180^\circ..+180^\circ).

| +| Direction of Altitude | M | | ENUMERATED (Height, Depth) | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Altitude | M | | INTEGER (0..2 15 -1) | The relation between the value (N) and the altitude (a) in meters it describes is $N \leq a < N+1$ , except for $N=2^{15}-1$ for which the range is extended to include all greater values of (a). | +| Uncertainty semi-major | M | | INTEGER (0..127) | The uncertainty "r" is derived from the "uncertainty code" k by $r = 10x(1.1^k-1)$ . | +| Uncertainty semi-minor | M | | INTEGER (0..127) | The uncertainty "r" is derived from the "uncertainty code" k by $r = 10x(1.1^k-1)$ . | +| Orientation of major axis | M | | INTEGER (0..179) | | +| Uncertainty Altitude | M | | INTEGER (0..127) | The uncertainty altitude "h" expressed in metres is derived from the "uncertainty code" k, by: $h=45x(1.025^k-1)$ . | +| Confidence | M | | INTEGER (0..100) | In percentage | + +### 9.2.11 TAC + +This information element is used to uniquely identify a Tracking Area Code. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-------------------------|-----------------------| +| TAC | M | | OCTET STRING (SIZE (3)) | | + +### 9.2.12 Cell Portion ID + +This parameter gives the current Cell Portion associated with the target UE. The Cell Portion ID is the unique identifier for a cell portion within a cell. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------|----------|-------|-----------------------|-----------------------| +| Cell Portion ID | M | | INTEGER (0..4095,...) | | + +### 9.2.13 Other-RAT Measurement Result + +The purpose of the Other-RAT Measurement Result information element is to provide the measurement results of RATs other than the serving RAT. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|--------------------|-----------------------|-----------------------|-------------|----------------------| +| Other-RAT Measured Results | | 1 | | | - | | +| >CHOICE Other-RAT Measured Results Value | | 1..
| | | - | | +| >>Result GERAN | | | | | | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------------------|----------|-----------------------|-------------------------|----------------------------------------------|-------------|----------------------| +| >>>Result GERAN Item | | 1.. | | | - | | +| >>>>ARFCN of BCCH | M | | INTEGER (0..1023, ...) | | - | | +| >>>>Physical CellId GERAN | M | | INTEGER (0..63, ...) | | - | | +| >>>>RSSI | M | | INTEGER (0..63, ...) | | - | | +| >>Result UTRAN | | | | | | | +| >>>Result UTRAN Item | | 1.. | | | - | | +| >>>>UARFCN | M | | INTEGER (0..16383, ...) | | - | | +| >>>>CHOICE Physical CellId UTRA | M | | | | - | | +| >>>>>Physical CellId UTRA FDD | | | INTEGER (0..511, ...) | | | | +| >>>>>Physical CellId UTRA TDD | | | INTEGER (0..127, ...) | | | | +| >>>>UTRA RSCP | O | | INTEGER (-5..91, ...) | | - | | +| >>>>UTRA EcNo | O | | INTEGER (0..49, ...) | This IE applies to FDD only. | - | | +| >>Result NR | | | | | YES | ignore | +| >>>Result NR Item | | 1.. | | | - | | +| >>>>NR PCI | M | | INTEGER (0..1007) | | - | | +| >>>>NR ARFCN | M | | INTEGER (0..3279165) | | - | | +| >>>>SS-RSRP Cell | O | | INTEGER (0..127) | SS-RSRP measurement aggregated at cell level | - | | +| >>>>SS-RSRQ Cell | O | | INTEGER (0..127) | SS-RSRQ measurement aggregated at cell level | - | | +| >>>>SS-RSRP per SSB Resource | | 0..1 | | | - | | +| >>>>>Result SS-RSRP Per SSB Item | | 1.. | | | - | | +| >>>>>>SSB Index | M | | INTEGER (0..63) | | - | | +| >>>>>>Value SS-RSRP | M | | INTEGER (0..127) | SS-RSRP measurement per SSB resource | - | | +| >>>>SS-RSRQ per SSB | | 0..1 | | | - | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------|----------|-------------------------------|------------------------|-------------------------------------------------------------|-------------|----------------------| +| Resource | | | | | | | +| >>>>>Result
SS-RSRQ Per
SSB Item | | 1..dexesRep
ort> | | | - | | +| >>>>>SSB
Index | M | | INTEGER
(0..63) | | - | | +| >>>>>Value
SS-RSRQ | M | | INTEGER
(0..127) | SS-RSRQ
measurement per
SSB resource | - | | +| >>>>CGI NR | O | | 9.2.9 | Cell Global
Identifier of the
reported NR cell | - | | +| >>Result EUTRA | | | | | YES | ignore | +| >>>Result
EUTRA Item | | 1..UTRAMea
s> | | | - | | +| >>>>PCI
EUTRA | M | | INTEGER
(0..503) | | - | | +| >>>>EARFCN | M | | INTEGER
(0..262143) | | - | | +| >>>>RSRP
EUTRA | O | | INTEGER
(0..97) | | - | | +| >>>>RSRQ
EUTRA | O | | INTEGER
(0..34) | | - | | +| >>>>CGI
EUTRA | O | | 9.2.7 | Cell Global
Identifier of the
reported E-UTRA
cell | - | | + +| Range bound | Explanation | +|------------------|-------------------------------------------------------------------------------------------------------| +| maxnoMeas | Maximum no. of measured quantities that can be configured and reported with one message. Value is 64. | +| maxGERANMeas | Maximum no. of GERAN cells that can be reported with one message. Value is 8. | +| maxUTRANMeas | Maximum no. of UTRAN cells that can be reported with one message. Value is 8. | +| maxNRMeas | Maximum no. of NR cells that can be reported with one message. Value is 8. | +| maxEUTRAMeas | Maximum no. of EUTRA cells that can be reported with one message. Value is 8. | +| maxIndexesReport | Maximum no. of beam level measurement results that can be reported with one message. Value is 64. | + +### 9.2.14 WLAN Measurement Result + +The WLAN Measurement Result information element provides the WLAN measurement results. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------|----------|--------------------|-----------------------|-----------------------| +| WLAN Measured Results | | 1 | | | +| >WLAN Measurement
Result Item | | 1..
| | | +| >>WLAN RSSI | M | | INTEGER | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-----------------------|-------------------------------------------------------|----------------------------------------------------------------------------------| +| | | | (0..141, ...) | | +| >>SSID | O | | OCTET STRING (SIZE(1..32)) | Includes the SSID field as defined in subclause 8.4.2.2 of IEEE 802.11™ [11]. | +| >>BSSID | M | | OCTET STRING (SIZE(6)) | Includes the BSSID field as defined in subclause 8.2.4.3.4 of IEEE 802.11™ [11]. | +| >>HESSID | O | | OCTET STRING (SIZE(6)) | Includes the HESSID field as defined in subclause 8.4.2.94 of IEEE 802.11™ [11]. | +| >>Operating Class | O | | INTEGER (0..255) | Indicates the WLAN Operating Class as defined in IEEE 802.11™ [11]. | +| >>Country Code | O | | ENUMERATED (unitedStates, europe, japan, global, ...) | Indicates the WLAN country code as defined in IEEE 802.11™ [11]. | +| >>WLAN Channel List | | 0..1 | | | +| >>>WLAN Channel List Item | | 1.. | | | +| >>>>WLAN Channel | M | | INTEGER (0..255) | Indicates the WLAN channel number as defined in IEEE 802.11™ [11]. | +| >>WLAN Band | O | | ENUMERATED (band2dot4, band5, ...) | Indicates the WLAN band as defined in IEEE 802.11™ [11]. | + +| Range bound | Explanation | +|-----------------|-------------------------------------------------------------------------------------------------------| +| maxnoMeas | Maximum no. of measured quantities that can be configured and reported with one message. Value is 63. | +| maxWLANchannels | Maximum no. of WLAN channels that can be reported within one list. Value is 16. | + +### 9.2.15 OTDOA Cell Information + +This IE contains OTDOA information of a cell/TP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned criticality | +|-------------------------------------------|----------|------------------------|--------------------------|-----------------------------------------------|-------------|----------------------| +| CHOICE OTDOA Cell Information item | | 1
| | | - | | +| >>PCI EUTRA | M | | INTEGER (0..503, ...) | Physical Cell ID of the reported E-UTRA cell. | - | | +| >>CGI EUTRA | M | | 9.2.7 | Cell Global Identifier of the E-UTRA cell. | - | | +| >>TAC | M | | 9.2.11 | Tracking Area Code | - | | +| >>EARFCN | M | | INTEGER (0..262143, ...) | Corresponds to NDL for FDD and | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned criticality | +|----------------------------------|----------|-------|------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | NDL/UL for TDD in ref. TS 36.104 [7]. | | | +| >>PRS Bandwidth EUTRA | M | | ENUMERATED (bw6, bw15, bw25, bw50, bw75, bw100, ...) | Transmission bandwidth of PRS | - | | +| >>PRS Configuration Index EUTRA | M | | INTEGER (0..4095, ...) | PRS Configuration Index, ref TS 36.211 [10] | - | | +| >>CP Length EUTRA | M | | ENUMERATED (Normal, Extended, ...) | Cyclic prefix length of the PRS | - | | +| >>Number of DL Frames EUTRA | M | | ENUMERATED (sf1, sf2, sf4, sf6, ...) | Number of consecutive downlink subframes NPRS with PRS, ref TS 36.211 [10] | - | | +| >>Number of Antenna Ports EUTRA | M | | ENUMERATED (n1-or-n2, n4, ...) | Number of used antenna ports, where n1-or-n2 corresponds to 1 or 2 ports, n4 corresponds to 4 ports | - | | +| >>SFN Initialisation Time EUTRA | M | | BIT STRING (64) | Time in seconds relative to 00:00:00 on 1 January 1900 (calculated as continuous time without leap seconds and traceable to a common time reference) where binary encoding of the integer part is in the first 32 bits and binary encoding of the fraction part in the last 32 bits. The fraction part is expressed with a granularity of $1/2^{32}$ second. | - | | +| >>NG-RAN Access Point Position | M | | 9.2.10 | The configured estimated geographical position of the antenna of the cell/TP. | - | | +| >>PRS Muting Configuration EUTRA | M | | 9.2.16 | The configuration of positioning reference signals | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned criticality | +|---------------------------------------------|----------|-------|----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | muting pattern. | | | +| >>PRS-ID EUTRA | M | | INTEGER (0..4095, ...) | PRS ID, ref TS 36.211 [10]. | - | | +| >>TP-ID EUTRA | M | | INTEGER (0..4095, ...) | Identity of the transmission point. This IE together with the PCI and/or PRS-ID may be used to identify the transmission point in case the same physical cell ID is shared by multiple transmission points. | - | | +| >>TP Type EUTRA | M | | ENUMERATED (prs-only-tp, ...) | A TP which transmits PRS only. | - | | +| >>Number of DL Frames-Extended EUTRA | M | | INTEGER (1..160, ...) | Number of consecutive downlink subframes NPRS with PRS, ref TS 36.211 [10]. | - | | +| >>CRS CP Length EUTRA | M | | ENUMERATED (Normal, Extended, ...) | Cyclic prefix length of the CRS. | - | | +| >>DL Bandwidth EUTRA | M | | ENUMERATED (bw6, bw15, bw25, bw50, bw75, bw100, ...) | DL transmission bandwidth expressed in units of resource blocks NRB, ref TS 36.104 [7]. | - | | +| >>PRS Occasion Group EUTRA | M | | ENUMERATED (og2, og4, og8, og16, og32, og64, og128, ...) | PRS occasion group in a PRS period, ref TS 36.211 [10]. | - | | +| >>PRS Frequency Hopping Configuration EUTRA | M | | 9.2.17 | PRS frequency hopping configuration. | - | | +| >>TDD Configuration EUTRA | M | | 9.2.18 | TDD specific physical channel configuration. | YES | ignore | +| >>NR CGI | M | | 9.2.9 | Cell Global Identifier of the NR cell. | YES | ignore | +| >>SFN Initialisation Time NR | M | | BIT STRING (64) | Time in seconds relative to 00:00:00 on 1 January 1900 (calculated as continuous time without leap seconds and | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned criticality | +|---------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | traceable to a common time reference) where binary encoding of the integer part is in the first 32 bits and binary encoding of the fraction part in the last 32 bits. The fraction part is expressed with a granularity of $1/2^{32}$ second. | | | + +| Range bound | Explanation | +|-----------------|----------------------------------------------------------------------------------------------------------| +| maxnoOTDOAtypes | Maximum no. of OTDOA information types that can be requested and reported with one message. Value is 63. | + +### 9.2.16 PRS Muting Configuration EUTRA + +The *PRS Muting Configuration EUTRA* IE is used to describe the configuration of PRS muting patterns for the concerned cell/TP, according to TS 36.211 [10] and TS 36.133 [9]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE PRS Muting Configuration | M | | | | +| >Two | | | BIT STRING (2) | If a bit is set to "0", it indicates that the PRS is muted in the corresponding PRS positioning occasion (numbering from any sub frame for which SFN=0) in a periodic cycle of length equal to the length of the bit string | +| >Four | | | BIT STRING (4) | Same as above | +| >Eight | | | BIT STRING (8) | Same as above | +| >Sixteen | | | BIT STRING (16) | Same as above | +| >thirty-two | | | BIT STRING (32) | Same as above | +| >sixty-four | | | BIT STRING (64) | Same as above | +| >one-hundred-and-twenty-eight | | | BIT STRING (128) | Same as above | +| >two-hundred-and-fifty-six | | | BIT STRING (256) | Same as above | +| >five-hundred-and-twelve | | | BIT STRING (512) | Same as above | +| >one-thousand-and-twenty-four | | | BIT STRING (1024) | Same as above | + +### 9.2.17 PRS Frequency Hopping Configuration EUTRA + +The *PRS Frequency Hopping Configuration EUTRA* IE is used to describe the configuration of PRS frequency hopping for the concerned cell/TP, according to TS 36.211 [10]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|--------------------------------------------|---------------------------------------|----------------------------------------| +| Number of Frequency Hopping Bands | M | | ENUMERATED (twobands, fourbands, ...) | Number of bands for frequency hopping. | +| Band Positions | | 1..
| | | +| >NarrowBand Index | M | | INTEGER (0..15, ...) | Narrowband Index | + +| Range bound | Explanation | +|-------------------------------|---------------------------------------------------------------| +| maxnoFreqHoppingBandsMinusOne | Maximum no. of frequency hopping bands minus one. Value is 7. | + +### 9.2.18 TDD Configuration EUTRA + +The *TDD Configuration EUTRA* IE is used to specify the TDD specific physical channel configuration. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------| +| Subframe Assignment | M | | ENUMERATED ( sa0, sa1, sa2, sa3, sa4, sa5, sa6, ... ) | sa0 points to Configuration 0, sa1 to Configuration 1 etc. as specified in TS 36.211 [6, table 4.2-2]. | + +### 9.2.19 Assistance Information + +This IE contains the assistance information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|--------------------------|---------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| Assistance Information | M | | | | +| > System Information | | 1.. | | Corresponds to the number of SI messages with posSIBs to be scheduled | +| >>Broadcast Periodicity | M | | ENUMERATED (ms80, ms160, ms320, ms640, ms1280, ms2560, ms5120, ...) | Corresponds to information provided in posSI-Periodicity contained in the PosSI-SchedulingInfo IE as defined in TS 38.331 [13] | +| >> Pos SIBs | | 1.. | | Number of posSIBs in the System Information. | +| >>>PosSIB-Type | M | | 9.2.22 | | +| >>>PosSIB Segments | M | | 9.2.20 | | +| >>>Assistance Information Meta Data | O | | 9.2.21 | | +| >>>Broadcast Priority | O | | INTEGER (1..16, ...) | The priority of the assistance Information where 1 represents the highest priority and 16 the lowest priority | + +| Range bound | Explanation | +|---------------------|------------------------------------------------------------| +| maxNrOfPosSImessage | Maximum number of positioning system information messages. | + +| | | +|----------------|-----------------------------------------------------------------------------------------------| +| | Value is 32. | +| maxNrOfPosSIBs | Maximum number of positioning system information blocks included in the message. Value is 32. | + +### 9.2.20 PosSIB Segments + +This IE provides one posSIB or two or more posSIB segments which must be scheduled in series in consecutive transmissions of the same SI message. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|----------------------|-----------------------|------------------------------------------------------------------------------| +| PosSIB Segments | | 1.. | | | +| >Assistance Data SIB Element | M | | OCTET STRING | Includes the assistanceDataSIBElement IE as defined in TS 37.355 [14] | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxNrOfSegments | Maximum number of positioning SIB segments (in case of Assistance Information Element contains segmented data according to TS 37.355 [14]). Value is 64. | + +### 9.2.21 Assistance Information Meta Data + +This parameter contains meta data for an assistance information element. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| Encrypted | O | | ENUMERATED (true, ...) | Corresponds to information provided in encrypted contained in the PosSI-SchedulingInfo IE as defined in TS 38.331 [13] | +| GNSS ID | O | | ENUMERATED (gps, sbas, qzss, galileo, glonass, bds, navic ...) | Corresponds to information provided in gnss-id contained in the PosSI-SchedulingInfo IE as defined in TS 38.331 [13] | +| SBAS ID | O | | ENUMERATED (waas, egnos, msas, gagan, ...) | Corresponds to information provided in sbas-id contained in the PosSI-SchedulingInfo IE as defined in TS 38.331 [13] | + +### 9.2.22 Positioning SIB Type + +This parameter defines a specific positioning SIB, as defined in TS 38.331 [13]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|-------|---------------------------------------------------------------|-----------------------| +| Positioning SIB Type | M | | ENUMERATED (posSibType1-1, posSibType1-2, posSibType1-3, ...) | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| | | | posSibType1-4,
posSibType1-5,
posSibType1-6,
posSibType1-7,
posSibType1-8,
posSibType2-1,
posSibType2-2,
posSibType2-3,
posSibType2-4,
posSibType2-5,
posSibType2-6,
posSibType2-7,
posSibType2-8,
posSibType2-9,
posSibType2-10,
posSibType2-11,
posSibType2-12,
posSibType2-13,
posSibType2-14,
posSibType2-15,
posSibType2-16,
posSibType2-17,
posSibType2-18,
posSibType2-19,
posSibType2-20,
posSibType2-21,
posSibType2-22,
posSibType2-23,
posSibType2-24,
posSibType2-25,
posSibType3-1,
posSibType4-1,
posSibType5-1,
posSibType6-1,
posSibType6-2,
posSibType6-3,
...,
posSibType1-9,
posSibType1-10,
posSibType6-4,
posSibType6-5,
posSibType6-6) | | + +### 9.2.23 Assistance Information Failure List + +This parameter identifies the assistance information for which the NG-RAN Node failed to configure broadcasting. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------|----------|--------------------------------------|-----------------------------|-----------------------| +| Assistance Information Failure List | | 1.. | | | +| >PosSIB-Type | M | | 9.2.22 | | +| >Outcome | M | | ENUMERATED
(failed, ...) | | + +| Range bound | Explanation | +|---------------------------------|--------------------------------------------------------------------------------------------------------------| +| maxnoAssistInfoFailureListItems | Maximum no. of assistance information failure list items that can be signaled with one message. Value is 32. | + +### 9.2.24 TRP ID + +The *TRP ID* IE is used to identify a TRP uniquely within an NG-RAN node. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|---------------------------|----------------------------------------| +| TRP Identifier | M | | INTEGER
(1..65535,...) | Identifies a TRP within an NG-RAN node | + +## 9.2.25 TRP Information + +The *TRP Information* IE contains information for one TRP within an NG-RAN node. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------|----------|-----------------------------|------------------------------------------------------------------------|-----------------------|-------------|----------------------| +| TRP ID | M | | 9.2.24 | | - | | +| TRP Information Type | | 1 ..
| | | - | | +| >CHOICE TRP Information Item | M | | | | - | | +| >>NR PCI | | | INTEGER
(0..1007) | NR Physical Cell ID | | | +| >>NR CGI | | | 9.2.9 | | | | +| >>NR ARFCN | | | INTEGER
(0..3279165) | | | | +| >>PRS Configuration | | | 9.2.44 | | | | +| >>SSB Information | | | 9.2.54 | | | | +| >>SFN Initialisation Time | | | Relative Time
1900
9.2.36 | | | | +| >>Spatial Direction Information | | | 9.2.45 | | | | +| >>Geographical Coordinates | | | 9.2.46 | | | | +| >>TRP type | | | ENUMERATED
(prs-only-tp, srs-only-rp, tp, rp, trp, ..., mobile trp) | TS 38.305 [18] | YES | reject | +| >>On-demand PRS TRP Information | | | 9.2.65 | | YES | reject | +| >>TRP Tx TEG Association | | | 9.2.79 | | YES | reject | +| >>TRP Beam Antenna Information | | | 9.2.82 | | YES | reject | +| >>Mobile TRP Location Information | M | | 9.2.88 | | YES | reject | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------|-------------------|-------|-----------------------|--------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Mobile IAB-MT UE ID | C-
ifMobileTRP | | OCTET
STRING | The UE ID of the IAB-MT associated with the mobile TRP. Includes the GPSI as defined in TS 29.571 [Yy] | YES | reject | +| >>Common TA Parameters | M | | 9.2.89 | | YES | reject | + +| Condition | Explanation | +|-------------|-------------------------------------------------------------------------------------| +| ifMobileTRP | This IE shall be present if the TRP type IE is set to the value 'mobile trp' | + +| Range bound | Explanation | +|-------------------|-------------------------------------------------------------------------------------------------------| +| maxnoTRPInfoTypes | Maximum no of TRP information types that can be requested and reported with one message. Value is 64. | + +## 9.2.26 Search Window Information + +This information element contains search window information for the TRP. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Expected Propagation Delay | M | | INTEGER
(-3841..3841,...) | Indicates when the SRS is expected to arrive in time at the TRP relative to the UL RTOA Reference Time.
The UL RTOA Reference Time for a target SRS is defined as , where
- is the SFN Initialisation Time
- , where and are the system frame number and the subframe number of the SRS, respectively.
Granularity 4Ts, where $T_s = 1/(15 \cdot 10^3 \cdot 2048)$ seconds.
Centre of the search window. | +| Delay Uncertainty | M | | INTEGER
(1..246,...) | Indicates the uncertainty of the expected SRS arrival time at the TRP
Granularity 4Ts, where $T_s = 1/(15 \cdot 10^3 \cdot 2048)$ seconds.
Single-sided search window. | + +## 9.2.27 Requested SRS Transmission Characteristics + +This IE contains the requested SRS configuration for the UE. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------|---------------------------|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Number Of Periodic Transmissions | C-ifResource TypePeriodic | | INTEGER (0..500,...) | The number of periodic SRS transmissions requested. The value of '0' represents an infinite number of periodic SRS transmissions. | - | | +| Resource Type | M | | ENUMERATED (periodic, semi-persistent, aperiodic, ...) | | - | | +| CHOICE Bandwidth | M | | | | - | | +| >FR1 | | | ENUMERATED (5mHz, 10mHz, 20mHz, 40mHz, 50mHz, 80mHz, 100mHz, ...) | | | | +| >FR2 | | | ENUMERATED (50mHz, 100mHz, 200mHz, 400mHz,...) | | | | +| SRS Resource Set List | | 0.. 1 | | | - | | +| >SRS Resource Set Item | | 1.. | | | - | | +| >>Number of SRS Resources Per Set | O | | INTEGER (1..16,...) | The number of SRS Resources per resource set for SRS transmission. | - | | +| >>Periodicity List | | 0.. 1 | | | - | | +| >>>Periodicity List Item | | 1.. | | | - | | +| >>>>PeriodicitySRS | M | | ENUMERATED (0.125, 0.25, 0.5, 0.625, 1, 1.25, 2, 2.5, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240, ...) | Milli-seconds | - | | +| >>Spatial Relation Information | O | | 9.2.34 | This IE is ignored if the Spatial Relation Information per SRS Resource IE is present. | - | | +| >>Pathloss | O | | 9.2.53 | | - | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------|-------------|----------------------| +| Reference Information | | | | | | | +| >>Spatial Relation Information per SRS Resource | O | | 9.2.60 | | - | | +| SSB Information | O | | 9.2.54 | | - | | +| SRS Frequency | O | | INTEGER(0..3279165) | NR ARFCN
The carrier frequency of SRS transmission bandwidth. | YES | ignore | + +| Condition | Explanation | +|------------------------|-----------------------------------------------------------------------------------------| +| ifResourceTypePeriodic | This IE shall be present if the Resource Type IE is set to the value "Periodic". | + +| Range bound | Explanation | +|-------------------------|------------------------------------------------------------------------------| +| maxnoSRS-ResourceSets | Maximum no of requested SRS Resource Sets for SRS transmission. Value is 16. | +| maxnoSRS-ResourcePerSet | Maximum no of SRS Resources per set. Value is 16. | + +## 9.2.28 SRS Configuration + +This information element contains the SRS configuration configured by the NG-RAN node for the UE. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|------------------------|---------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------| +| SRS Carrier List | | 1 | | | +| > SRS Carrier List Item | | 1.. | | | +| >>Point A | M | | INTEGER(0..3279165) | NR ARFCN | +| >>Uplink Channel BW-PerSCS-List | | 1 | | Corresponds to sCS-SpecificCarrierList in TS 38.331 [13] | +| >>> SCS Specific Carrier | | 1.. | | | +| >>>>Offset To Carrier | M | | INTEGER(0..2199, ...) | First usable RB to Point A in the number of PRBs | +| >>>>Subcarrier Spacing | M | | ENUMERATED(kHz 15, kHz30, kHz60, kHz120, ..., kHz480, kHz960) | | +| >>>>Carrier Bandwidth | M | | INTEGER(1..275, ...) | | +| >>Active UL BWP | | 1 | | Only the configuration in the active UL BWP is needed. | +| >>>Location And Bandwidth | M | | INTEGER(0..37949, ...) | Corresponds to information provided in locationAndBandwidth contained in BWP IE as defined in TS 38.331 [13] | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------|----------|-------------------------------|--------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| >>>Subcarrier Spacing | M | | ENUMERATED(kHz 15, kHz30, kHz60, kHz120,..., kHz480, kHz960) | | +| >>>Cyclic Prefix | M | | ENUMERATED(Normal, Extended) | | +| >>>Tx Direct Current Location | M | | INTEGER(0..3301, ...) | | +| >>>Shift7dot5kHz | O | | ENUMERATED(true, ...) | | +| >>>SRS Config | | 1 | | Corresponds to information provided in SRS-Config IE as defined in TS 38.331 [13] | +| >>>>SRS Resource List | | 0.. | | | +| >>>>>SRS Resource | M | | 9.2.29 | Corresponds to information provided in SRS-Resource contained in SRS-Config IE as defined in TS 38.331 [13] | +| >>>>Positioning SRS Resource List | | 0.. | | | +| >>>>>Positioning SRS Resource | M | | 9.2.30 | Corresponds to information provided in SRS-PosResource contained in SRS-Config IE as defined in TS 38.331 [13] | +| >>>>SRS Resource Set List | | 0.. | | | +| >>>>>SRS Resource Set | M | | 9.2.31 | Corresponds to information provided in SRS-ResourceSet contained in SRS-Config IE as defined in TS 38.331 [13] | +| >>>>Positioning SRS Resource Set List | | 0.. | | | +| >>>>>Positioning SRS Resource Set | M | | 9.2.32 | Corresponds to information provided in SRS-PosResourceSet contained in SRS-Config IE as defined in TS 38.331 [13] | +| >>NR PCI | O | | INTEGER (0..1007) | Physical Cell ID of the cell that contains the SRS carrier | + +| Range bound | Explanation | +|--------------------------|------------------------------------------------------------------| +| maxnoSRS-Carriers | Maximum no of carriers for SRS. Value is 32. | +| maxnoSCSs | Maximum no of SCS spacings for a carrier. Value is 5. | +| maxnoSRS-Resources | Maximum no of SRS resources per UL BWP. Value is 64. | +| maxnoSRS-PosResources | Maximum no of positioning SRS resources per UL BWP. Value is 64. | +| maxnoSRS-ResourceSets | Maximum no of SRS resource sets per UL BWP. Value is 16. | +| maxnoSRS-PosResourceSets | Maximum no of positioning SRS resource sets per UL BWP. Value | + +| | | +|--|--------| +| | is 16. | +|--|--------| + +## 9.2.29 SRS Resource + +This information element contains the SRS resource. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|------------------------------------------------------------------------|----------------------------------------------------------------------------|-------------|----------------------| +| SRS Resource ID | M | | INTEGER(0..63) | | - | | +| Number of Ports | M | | ENUMERATED (port1, ports2, ports4) | | - | | +| CHOICE Transmission Comb | M | | | | - | | +| >Comb Two | | | | | | | +| >>Comb Offset | M | | INTEGER(0..1) | | - | | +| >>Cyclic Shift | M | | INTEGER(0..7) | | - | | +| >Comb Four | | | | | | | +| >>Comb Offset | M | | INTEGER(0..3) | | - | | +| >>Cyclic Shift | M | | INTEGER(0..11) | | - | | +| >Comb Eight | M | | | | YES | reject | +| >>Comb Offset | M | | INTEGER(0..7) | | - | - | +| >>Cyclic Shift | M | | INTEGER(0..5) | | - | - | +| Start Position | M | | INTEGER(0..13) | | - | | +| Number of Symbols | M | | ENUMERATED (n1,n2,n4) | This IE is ignored if the Number of Symbols Extended IE is included | - | | +| Repetition Factor | M | | ENUMERATED (r1,r2,r4) | This IE is ignored if the Repetition Factor Extended IE is included | - | | +| Frequency Domain Position | M | | INTEGER(0..67) | | - | | +| Frequency Domain Shift | M | | INTEGER(0..268) | | - | | +| C-SRS | M | | INTEGER(0..63) | | - | | +| B-SRS | M | | INTEGER(0..3) | | - | | +| B-Hop | M | | INTEGER(0..3) | | - | | +| Group or Sequence Hopping | M | | ENUMERATED (neither, groupHopping, sequenceHopping) | | - | | +| CHOICE Resource Type | M | | | | - | | +| >Periodic | | | | | - | | +| >>Periodicity | M | | ENUMERATED (slot1, slot2, slot4, slot5, slot8, slot10, slot16, slot20) | | - | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------|----------------------| +| | | | slot32, slot40, slot64, slot80, slot160, slot320, slot640, slot1280, slot2560, ...) | | | | +| >>Offset | M | | INTEGER(0..2559, ...) | | - | | +| >Semi-persistent | | | | | | | +| >>Periodicity | M | | ENUMERATED (slot1, slot2, slot4, slot5, slot8, slot10, slot16, slot20, slot32, slot40, slot64, slot80, slot160, slot320, slot640, slot1280, slot2560, ...) | | - | | +| >>Offset | M | | INTEGER(0..2559, ...) | | - | | +| >Aperiodic | | | | | | | +| >>Aperiodic Resource Type | M | | ENUMERATED (true,...) | | - | | +| Sequence ID | M | | INTEGER(0..1023) | | - | | +| Number of Symbols Extended | O | | ENUMERATED (n8,n10,n12, n14, ...) | | YES | ignore | +| Repetition Factor Extended | O | | ENUMERATED (r3, r5, r6, r7, r8, r10, r12, r14, ...) | | YES | ignore | +| Start RB Hopping | O | | ENUMERATED (enable) | | YES | ignore | +| CHOICE Start RB Index | O | | | | YES | ignore | +| >FreqScalingFactor2 | | | INTEGER (0..1) | | | | +| >FreqScalingFactor4 | | | INTEGER (0..3) | | | | + +## 9.2.30 Positioning SRS Resource + +This information element contains the SRS resource for positioning. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|-----------------------|-----------------------| +| Positioning SRS Resource ID | M | | INTEGER(0..63) | | +| CHOICE Transmission Comb | M | | | | +| >Comb Two | | | | | +| >>Comb Offset | M | | INTEGER(0..1) | | +| >>Cyclic Shift | M | | INTEGER(0..7) | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------|----------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| >Comb Four | | | | | +| >>Comb Offset | M | | INTEGER(0..3) | | +| >>Cyclic Shift | M | | INTEGER(0..11) | | +| >Comb Eight | | | | | +| >>Comb Offset | M | | INTEGER(0..7) | | +| >>Cyclic Shift | M | | INTEGER(0..5) | | +| Start Position | M | | INTEGER(0..13) | | +| Number of Symbols | M | | ENUMERATED(n1, n2,n4, n8, n12) | | +| Frequency Domain Shift | M | | INTEGER(0..268) | | +| C-SRS | M | | INTEGER(0..63) | | +| Group or Sequence Hopping | M | | ENUMERATED(Neither, groupHopping, sequenceHopping) | | +| CHOICE Resource Type Positioning | M | | | | +| >periodic | | | | | +| >>Periodicity | M | | ENUMERATED(slot 1, slot2, slot4, slot5, slot8, slot10, slot16, slot20, slot32, slot40, slot64, slot80, slot160, slot320, slot640, slot1280, slot2560, slot5120, slot10240, slot40960, slot81920,..., slot128, slot256, slot512, slot20480) | | +| >>Offset | M | | INTEGER(0..81919, ...) | | +| >semi-persistent | | | | | +| >>Periodicity | M | | ENUMERATED(slot 1, slot 2, slot4, slot5, slot8, slot10, slot16, slot20, slot32, slot40, slot64, slot80, slot160, slot320, slot640, slot1280, slot2560, slot5120, slot10240, slot40960, slot81920,..., slot128, slot256, slot512, slot20480) | | +| >>Offset | M | | INTEGER(0..81919, ...) | | +| >aperiodic | | | | | +| >>slot offset | M | | INTEGER(0..32) | | +| Sequence ID | M | | INTEGER(0..65535) | | +| CHOICE Spatial Relation Positioning | O | | | | +| >SSB | | | | | +| >>NR PCI | M | | INTEGER (0..1007) | | +| >>SSB index | O | | INTEGER(0..63) | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|-----------------------|-----------------------| +| >PRS | | | | | +| >>PRS ID | M | | INTEGER(0..255) | | +| >>PRS Resource Set ID | M | | INTEGER(0..7) | | +| >>PRS Resource ID | O | | INTEGER(0..63) | | + +### 9.2.31 SRS Resource Set + +This information element indicates an SRS resource set in the UE for UL SRS transmission. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|------------------------------|-----------------------|---------------------------------------------------------------| +| SRS Resource Set ID | M | | INTEGER(0..15) | | +| SRS Resource ID List | | 1.. | | | +| >SRS Resource ID | M | | INTEGER(0..63) | | +| CHOICE Resource Set Type | M | | | | +| > periodic | | | | | +| >>periodicSet | M | | ENUMERATED(true,...) | | +| > semi-persistent | | | | | +| >>semi-persistentSet | M | | ENUMERATED(true,...) | | +| > aperiodic | | | | | +| >>SRS Resource Trigger | M | | INTEGER(1..3) | | +| >>Slot offset | M | | INTEGER(0..32) | Offset in number of slots, where value 0 indicates no offset. | + +| Range bound | Explanation | +|-------------------------|----------------------------------------------------------------| +| maxnoSRS-ResourcePerSet | Maximum no of SRS resources per SRS resource set. Value is 16. | + +### 9.2.32 Positioning SRS Resource Set + +This information element indicates a positioning SRS resource set in the UE for UL SRS transmission. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|---------------------------------|-----------------------|-----------------------| +| Positioning SRS Resource Set ID | M | | INTEGER(0..15) | | +| Positioning SRS Resource ID List | | 1.. | | | +| >Positioning SRS Resource ID | M | | INTEGER(0..63) | | +| CHOICE Resource Type | M | | | | +| > periodic | | | | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-----------------------|-----------------------| +| >>PosperiodicSet | M | | ENUMERATED(true ,...) | | +| >semi-persistent | | | | | +| >>Possemi-persistentSet | M | | ENUMERATED(true ,...) | | +| >aperiodic | | | | | +| >>SRS Resource Trigger | M | | INTEGER(1..3) | | + +| Range bound | Explanation | +|----------------------------|----------------------------------------------------------------------------------------| +| maxnoSRS-PosResourcePerSet | Maximum no of positioning SRS resources per positioning SRS resource set. Value is 16. | + +## 9.2.33 SRS Resource Set ID + +This information element indicates a resource set in the UE for UL SRS transmission. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------| +| SRS Resource Set ID | M | | INTEGER (0..15) | Corresponds to information provided in SRS-ResourceSetId contained in SRS-Config IE as defined in TS 38.331 [13] | + +## 9.2.34 Spatial Relation Information + +This information element indicates a spatial relation for transmission of UL SRS by a UE. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|----------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Spatial Relation for Resource ID | | 1.. | | According to TS 38.321 [15] and corresponds to information provided in SRS-SpatialRelationInfoPos contained in SRS-Config IE as defined in TS 38.331 [13] | +| >CHOICE Reference Signal | M | | | | +| >>NZP CSI-RS | | | | | +| >>>NZP CSI-RS Resource ID | M | | INTEGER (0..191) | | +| >>SSB | | | | | +| >>>NR PCI | M | | INTEGER (0..1007) | | +| >>>SSB Index | O | | INTEGER (0..63) | | +| >>SRS | | | | | +| >>>SRS Resource ID | M | | INTEGER (0..63) | | +| >>Positioning SRS | | | | | +| >>>Positioning SRS Resource ID | M | | INTEGER (0..63) | | +| >>DL-PRS | | | | | +| >>>DL-PRS ID | M | | INTEGER (0..255) | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|-----------------------|-----------------------| +| >>>DL-PRS Resource Set ID | M | | INTEGER (0..7) | | +| >>>DL-PRS Resource ID | O | | INTEGER (0..63) | | + +| Range bound | Explanation | +|-----------------------|-----------------------------------------------------------------------| +| maxnoSpatialRelations | Maximum no. of Spatial Relations that can be configured. Value is 64. | + +## 9.2.35 SRS Resource Trigger + +This information element indicates a DCI code point according to a SRS resource set configuration. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------|----------|-----------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| Aperiodic SRS Resource Trigger List | | 1.. | | Corresponds to information provided in aperiodicSRS-ResourceTriggerList contained in SRS-Config IE as defined in TS 38.331 [13] | +| >Aperiodic SRS Resource Trigger | | | INTEGER (1..3) | | + +| Range bound | Explanation | +|-----------------------|------------------------------------------------| +| maxnoSRSTriggerStates | Maximum no. of SRS trigger states. Value is 3. | + +## 9.2.36 Relative Time 1900 + +This information element indicates the initialisation time (e.g. SFN Initialisation Time for a cell, requested time for an action, etc). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Relative Time 1900 | M | | BIT STRING (SIZE(64)) | Time in seconds relative to 00:00:00 on 1 January 1900 (calculated as continuous time without leap seconds and traceable to a common time reference) where binary encoding of the integer part is in the first 32 bits and binary encoding of the fraction part in the last 32 bits. The fraction part is expressed with a granularity of $1/2^{32}$ second | + +## 9.2.37 TRP Measurement Result + +This information element contains the measurement result. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------|----------|------------------------|-----------------------|-----------------------|-------------|----------------------| +| Measured Result Item | | 1 ..
| | | - | | +| >CHOICE Measured Results Value | M | | | | - | | +| >>UL Angle of Arrival | | | 9.2.38 | | | | +| >>UL SRS-RSRP | | | INTEGER (0..126) | | | | +| >>UL RTOA | | | 9.2.39 | | | | +| >>gNB Rx-Tx Time Difference | | | 9.2.40 | | | | +| >>Z-AoA | | | 9.2.67 | | YES | reject | +| >>Multiple UL-AoA | | | 9.2.71 | | YES | reject | +| >>UL SRS-RSRP | | | 9.2.72 | | YES | reject | +| >Time Stamp | M | | 9.2.42 | | - | | +| >Measurement Quality | O | | 9.2.43 | | - | | +| >Measurement Beam Information | O | | 9.2.57 | | - | | +| >SRS Resource type | O | | 9.2.73 | | YES | ignore | +| >ARP ID | O | | 9.2.75 | | YES | ignore | +| >LoS/NLoS Information | O | | 9.2.77 | | YES | ignore | +| >Mobile TRP Location Information | O | | 9.2.88 | | YES | ignore | + +| Range bound | Explanation | +|--------------|----------------------------------------------------------------------------------------------------------------------------------| +| maxnoPosMeas | Maximum no. of measured quantities that can be configured and reported with one positioning measurement message. Value is 16384. | + +## 9.2.38 UL Angle of Arrival + +This information element contains the uplink Angle of Arrival measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|-----------------------|--------------------------------------------------------| +| Azimuth Angle of Arrival | M | | INTEGER(0..3599) | TS 38.133 [16] | +| Zenith Angle of Arrival | O | | INTEGER(0..1799) | TS 38.133 [16] | +| LCS to GCS Translation | O | | 9.2.69 | If absent, the azimuth and zenith are provided in GCS. | + +## 9.2.39 UL RTOA Measurement + +This information element contains the uplink RTOA measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| CHOICE UL RTOA | M | | | | - | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------|-------------|----------------------| +| Measurement | | | | | | | +| >k0 | | | INTEGER (0..1970049) | TS 38.133 [16] | | | +| >k1 | | | INTEGER (0..985025) | TS 38.133 [16] | | | +| >k2 | | | INTEGER (0..492513) | TS 38.133 [16] | | | +| >k3 | | | INTEGER (0..246257) | TS 38.133 [16] | | | +| >k4 | | | INTEGER (0..123129) | TS 38.133 [16] | | | +| >k5 | | | INTEGER (0..61565) | TS 38.133 [16] | | | +| Additional Path List | O | | 9.2.41 | This IE is ignored if the Extended Additional Path List IE is included | - | | +| Extended Additional Path List | O | | 9.2.74 | | YES | ignore | +| TRP Rx TEG Information | O | | 9.2.85 | | YES | ignore | + +## 9.2.40 gNB Rx-Tx Time Difference + +This information element contains the gNB Rx-Tx Time Difference measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE gNB Rx-Tx Time Difference Measurement | M | | | | - | | +| >k0 | | | INTEGER (0..1970049) | TS 38.133 [16] | | | +| >k1 | | | INTEGER (0..985025) | TS 38.133 [16] | | | +| >k2 | | | INTEGER (0..492513) | TS 38.133 [16] | | | +| >k3 | | | INTEGER (0..246257) | TS 38.133 [16] | | | +| >k4 | | | INTEGER (0..123129) | TS 38.133 [16] | | | +| >k5 | | | INTEGER (0..61565) | TS 38.133 [16] | | | +| Additional Path List | O | | 9.2.41 | This IE is ignored if the Extended Additional Path List IE is included | - | | +| Extended Additional Path List | O | | 9.2.74 | | YES | ignore | +| TRP TEG Information | O | | 9.2.80 | | YES | ignore | + +## 9.2.41 Additional Path List + +This information element contains the additional path results of time measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------|----------|-----------------|----------------------------|-----------------------|-------------|----------------------| +| Additional Path Item | | 1.. | | | - | | +| >CHOICE Relative Path Delay | M | | | | - | | +| >>k0 | | | INTEGER(0..16351) | | | | +| >>k1 | | | INTEGER(0..8176) | | | | +| >>k2 | | | INTEGER(0..4088) | | | | +| >>k3 | | | INTEGER(0..2044) | | | | +| >>k4 | | | INTEGER(0..1022) | | | | +| >>k5 | | | INTEGER(0..511) | | | | +| >Path Quality | O | | Measurement Quality 9.2.43 | | - | | +| >Multiple UL-AoA | O | | 9.2.71 | | YES | ignore | +| >Path Power | O | | UL SRS-RSRPP 9.2.72 | | YES | ignore | + +| Range bound | Explanation | +|-------------|---------------------------------------------------------| +| maxnopath | Maximum no. of additional path measurement. Value is 2. | + +## 9.2.42 Time Stamp + +This information element contains the time stamp. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|---------------------------|-----------------------| +| System Frame Number | M | | INTEGER(0..1023) | | +| CHOICE Slot Index | M | | | | +| >SCS-15 | | | INTEGER(0..9) | | +| >SCS-30 | | | INTEGER(0..19) | | +| >SCS-60 | | | INTEGER(0..39) | | +| >SCS-120 | | | INTEGER(0..79) | | +| Measurement time | O | | Relative Time 1900 9.2.36 | | + +## 9.2.43 Measurement Quality + +This information element contains the TRP's best estimate of the quality of the measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------| +| CHOICE Measurement Quality | M | | | | +| >Timing Measurement Quality | | | | Corresponds to information provided in NR-TimingQuality IE | + +| | | | | | +|----------------------------|---|--|--------------------------------------|------------------------------| +| | | | | as defined in TS 37.355 [14] | +| >>Measurement Quality | M | | INTEGER(0..31) | | +| >>Resolution | M | | ENUMERATED(0.1 m, 1m, 10m, 30m, ...) | | +| >Angle Measurement Quality | | | | | +| >>Azimuth Quality | M | | INTEGER(0..255) | | +| >>Zenith Quality | O | | INTEGER(0..255) | | +| >>Resolution | M | | ENUMERATED (0.1deg, ...) | | + +## 9.2.44 PRS Configuration + +This information element contains the DL PRS configuration for the TRP. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------|----------|------------------------------|--------------------------------------------------------------------------------------------------------------------|-------------------------|-------------|----------------------| +| PRS Resource Set List | | 1 | | | | | +| >PRS Resource Set Item | | 1.. | | | | | +| >>PRS Resource Set ID | M | | INTEGER(0..7) | | | | +| >>Subcarrier Spacing | M | | ENUMERATED( kHz15, kHz30, kHz60, kHz120, ...) | | | | +| >>PRS bandwidth | M | | INTEGER(1..63) | 24,28,...,272 PRBs | | | +| >>Start PRB | M | | INTEGER(0..21 76) | Starting PRB to Point A | | | +| >>Point A | M | | INTEGER (0..3279165) | NR ARFCN | | | +| >>Comb Size | M | | ENUMERATED( 2, 4, 6, 12, ...) | | | | +| >>CP Type | M | | ENUMERATED( normal, extended, ...) | | | | +| >>Resource Set Periodicity | M | | ENUMERATED( 4,5,8,10,16,20,3 2,40,64,80,160, 320,640,1280,2 560,5120,10240 ,20480,40960,8 1920,..., 128, 256, 512) | Slots | | | +| >>Resource Set Slot Offset | M | | INTEGER(0..81 919,...) | | | | +| >>Resource Repetition Factor | M | | ENUMERATED( rf1,rf2,rf4,rf6,rf8, rf16,rf32,...) | | | | +| >>Resource Time Gap | M | | ENUMERATED( tg1,tg2,tg4,tg8,t g16,tg32,...) | | | | +| >>Resource | M | | ENUMERATED( | | | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------|----------|---------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Number of Symbols | | | n2,n4,n6,n12,..., n1) | | | | +| >>PRS Muting | O | | | | | | +| >>>Option1 | O | | | | | | +| >>>>Muting Pattern | M | | DL-PRS Muting Pattern 9.2.56 | Muting pattern option 1 is used to mute the whole PRS resource set (within a period) | | | +| >>>>Muting Bit Repetition Factor | M | | ENUMERATED(1,2,4,8,...) | | | | +| >>>Option2 | O | | | | | | +| >>>>Muting Pattern | M | | DL-PRS Muting Pattern 9.2.56 | Muting pattern option 2 is used to mute the selected repetition of the resource set (within the period) | | | +| >>PRS Resource Transmit Power | M | | INTEGER(-60..50) | | | | +| >>PRS Resource List | | 1 | | Corresponds to information provided in NR-DL-PRS-Resource contained in NR-DL-PRS-Info IE as defined in TS 37.355 [14] | | | +| >>>PRS Resource Item | | 1.. | | | | | +| >>>>PRS Resource ID | M | | INTEGER(0..63) | | | | +| >>>>Sequence ID | M | | INTEGER(0..4095) | | | | +| >>>>RE Offset | M | | INTEGER(0..11, ...) | | | | +| >>>>Resource Slot Offset | M | | INTEGER(0..511) | | | | +| >>>>Resource Symbol Offset | M | | INTEGER(0..12) | This IE is ignored if the Extended Resource Symbol Offset IE is present. | | | +| >>>>CHOICE QCL Info | O | | | | | | +| >>>>>SSB | | | | | | | +| >>>>>NR PCI | M | | INTEGER(0..1007) | | | | +| >>>>>SSB Index | O | | INTEGER(0..63) | | | | +| >>>>>DL-PRS | | | | | | | +| >>>>>QCL Source PRS | M | | INTEGER(0..7) | | | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------|-------------|----------------------| +| Resource Set ID | | | | | | | +| >>>>>>QCL Source PRS Resource ID | O | | INTEGER(0..63) | If it is absent, the QCL source PRS resource ID is the same as the PRS resource ID | | | +| >>>>Extended Resource Symbol Offset | O | | INTEGER(0..13, ...) | | YES | ignore | + +| Range bound | Explanation | +|-----------------------|----------------------------------------------------------------| +| maxnoofPRSresourceSet | Maximum no of PRS resources set. Value is 8. | +| maxnoofPRSresource | Maximum no of PRS resources per PRS resource set. Value is 64. | + +## 9.2.45 Spatial Direction Information + +This information element contains the spatial direction information of the DL PRS resources for the TRP. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-----------------------|----------------------------------------------------| +| NR-PRS Beam Information | M | | 9.2.58 | The spatial directions of DL-PRS Resources for TRP | + +## 9.2.46 Geographical Coordinates + +This information element contains the geographical coordinates for the TRP and any associated ARP(s). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------------|----------|-------|---------------------------------------------------|----------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE TRP Position Definition Type | M | | | | - | | +| > Direct | | | | | | | +| >>CHOICE Accuracy | M | | | | - | | +| >>> normal accuracy | | | | | | | +| >>>>TRP Position | M | | NG-RAN Access Point Position 9.2.10 | The configured estimated geographical position of the antenna of the cell/TRP. | - | | +| >>> high accuracy | | | | | | | +| >>>>TRP High Accuracy Access Point Position | M | | NG-RAN High Accuracy Access Point Position 9.2.49 | The configured estimated geographical high accuracy position of the antenna of the cell/TRP. | - | | +| > Referenced | | | | | | | +| >>Reference Point | M | | 9.2.51 | The reference | - | | + +| | | | | | | | +|-------------------------------------|---|--|------------------------------------|---------------------------------------------------------------------------------------|-----|--------| +| | | | | point is used to derive the TRP position | | | +| >>CHOICE Type | M | | | | - | | +| >>> Geodetic | | | | | | | +| >>>>TRP Position Relative Geodetic | M | | Relative Geodetic Location 9.2.48 | The configured estimated relative geodetic coordinate of the antenna of the cell/TRP | - | | +| >>> Cartesian | | | | | | | +| >>>>TRP Position Relative Cartesian | M | | Relative Cartesian Location 9.2.50 | The configured estimated relative Cartesian coordinate of the antenna of the cell/TRP | - | | +| DL-PRS Resource Coordinates | O | | 9.2.47 | DL-PRS Resource Coordinates relative to the TRP coordinate | - | | +| ARP Location Information | O | | 9.2.76 | | YES | ignore | + +## 9.2.47 DL-PRS Resource Coordinates + +This information element contains the geographical coordinates of the antenna reference points (ARP) for the DL-PRS Resources of a TRP. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------|----------|-----------------------------|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| DL-PRS Resource Set ARP List | M | 1.. | | | +| >DL-PRS Resource Set ID | M | | INTEGER (0..7) | | +| >CHOICE DL-PRS Resource Set ARP Location | M | | | Relative to the geographical coordinates for the TRP. If this IE is absent, the Relative Location is zero for the indicated DL-PRS Resource Set ID. | +| >> Geodetic | | | | | +| >>>TRP Position Relative Geodetic | M | | Relative Geodetic Location 9.2.48 | | +| >> Cartesian | | | | | +| >>>TRP Position Relative Cartesian | M | | Relative Cartesian Location 9.2.50 | | +| >DL-PRS Resource ARP List | M | 1.. | | | +| >>DL-PRS Resource ID | M | | INTEGER (0..63) | | +| >>CHOICE DL-PRS Resource ARP Location | M | | | Relative to the DL-PRS Resource Set ARP Location. If this IE is absent, the Relative Location is zero for the indicated DL-PRS Resource ID. | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------|----------|-------|---------------------------------------|-----------------------| +| >>>Geodetic | | | | | +| >>>>TRP Position
Relative Geodetic | M | | Relative Geodetic
Location 9.2.48 | | +| >>>Cartesian | | | | | +| >>>>TRP Position
Relative Cartesian | M | | Relative Cartesian
Location 9.2.50 | | + +| Range bound | Explanation | +|------------------------|------------------------------------------------------------------------------------| +| maxPRS-ResourceSets | Maximum no of DL-PRS resource sets per TRP. Value is 2. | +| maxPRS-ResourcesPerSet | Maximum no of DL-PRS resources of the DL-PRS resource set of the TRP. Value is 64. | + +## 9.2.48 Relative Geodetic Location + +This information element provides a location relative to some known reference location in a relative geodetic coordinate system. Corresponds to information provided in *RelativeLocation* IE as defined in TS 37.355 [14]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-----------------------------------|----------------------------------------------------------------------------------------------------------| +| Milli-Arc-Second Units | M | | ENUMERATED
(0.03, 0.3, 3, ...) | Units and scale factor for the delta-latitude and delta-longitude fields. 0.03, 0.3, 3, milliarcseconds. | +| Height Units | M | | ENUMERATED
(mm, cm, m, ...) | Units and scale factor for the delta-height field.
10 -3 metre, 10 -2 metre. | +| Delta Latitude | M | | INTEGER
(-1024..1023) | Delta value in latitude in the unit provided in Milli-Arc-Second Units. | +| Delta Longitude | M | | INTEGER
(-1024..1023) | Delta value in longitude in the unit provided in Milli-Arc-Second Units. | +| Delta Height | M | | INTEGER
(-1024..1023) | Delta value in ellipsoidal height in the unit provided in Height Units. | +| Location uncertainty | M | | 9.2.52 | | + +## 9.2.49 NG-RAN High Accuracy Access Point Position + +The *NG-RAN High Accuracy Access Point Position* IE is used to identify the geographical position of an NG-RAN Access Point. It is expressed as High Accuracy Ellipsoid point with altitude and uncertainty ellipsoid according to TS 23.032 [8]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|----------|-------|----------------------------------|-----------------------| +| Degrees of Latitude | M | | INTEGER(-2147483648..2147483647) | | +| Degrees of Longitude | M | | INTEGER(-2147483648..2147483647) | | +| Altitude | M | | INTEGER(-64000..1280000) | | + +| | | | | | +|------------------------|---|--|------------------|--| +| Uncertainty Semi Major | M | | INTEGER (0..255) | | +| Uncertainty Semi Minor | M | | INTEGER (0..255) | | +| Orientation Major Axis | M | | INTEGER (0..179) | | +| Horizontal Confidence | M | | INTEGER (0..100) | | +| Uncertainty Altitude | M | | INTEGER (0..255) | | +| Vertical Confidence | M | | INTEGER (0..100) | | + +## 9.2.50 Relative Cartesian Location + +This information element provides a location relative to some known reference location in a relative Cartesian coordinate system. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|----------|-------|--------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| XYZ unit | M | | ENUMERATED (mm, cm, dm,...) | | +| X value | M | | INTEGER (-2 16 .. 2 16 -1) | Positive value represents easting from reference point, in units of XYZ Unit IE . | +| Y value | M | | INTEGER (-2 16 .. 2 16 -1) | Positive value represents northing from reference point in units of XYZ Unit IE . | +| Z value | M | | INTEGER (-2 15 .. 2 15 -1) | Height with respect to reference point in units of XYZ Unit IE , where the XY-plane is horizontal and the Z-axis points up. | +| Location uncertainty | M | | 9.2.52 | | + +## 9.2.51 Reference Point + +This information element provides a reference point information. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------|----------|-------|---------------------------------------------------|----------------------------------------------------------------------| +| CHOICE ReferencePoint | M | | | Reference point to which relative location information is related to | +| >Coordinate ID | | | | | +| >>Coordinate ID | M | | INTEGER(0.. 2 9 -1,...) | Referential ID mapped via OAM | +| >Reference Point Coordinates | | | | | +| >>Reference Point Position | M | | NG-RAN Access Point Position 9.2.10 | | +| >Reference Point Coordinates High Accuracy | | | | | +| >>Reference Point High Accuracy Access Position | M | | NG-RAN High Accuracy Access Point Position 9.2.49 | | + +## 9.2.52 Location Uncertainty + +This information element provides the location uncertainty information. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------| +| Horizontal Uncertainty | M | | INTEGER (0..255) | Horizontal uncertainty of the ARP latitude/longitude. Corresponds to the encoded high accuracy uncertainty as defined in TS 23.032 [8] | +| Horizontal Confidence | M | | INTEGER (0..100) | Corresponds to confidence as defined in TS 23.032 [8]. | +| Vertical Uncertainty | M | | INTEGER (0..255) | Vertical uncertainty of the ARP altitude. Corresponds to the encoded high accuracy uncertainty as defined in TS 23.032 [8] | +| Vertical Confidence | M | | INTEGER (0..100) | Corresponds to confidence as defined in TS 23.032 [8]. | + +## 9.2.53 Pathloss Reference Information + +This information element indicates a pathloss reference for transmission of UL SRS by a UE. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Pathloss Reference Signal | M | | | | +| >SSB | | | | | +| >>NR PCI | M | | INTEGER (0..1007) | | +| >>SSB Index | O | | INTEGER (0..63) | | +| >DL-PRS | | | | | +| >>DL-PRS ID | M | | INTEGER (0..255) | | +| >>DL-PRS Resource Set ID | M | | INTEGER (0..7) | | +| >>DL PRS Resource ID | O | | INTEGER (0..63) | | + +## 9.2.54 SSB Information + +This information element contains the SSB time/frequency information for the TRPs. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|---------------------|-----------------------------------------|-----------------------| +| SSB Info List | | 1 | | | +| >SSB Info Item | | 1...
| | | +| >>SSB Configuration | M | | SSB Time/Frequency Configuration 9.2.55 | | +| >>NR PCI | M | | INTEGER (0..1007) | | + +| Range bound | Explanation | +|-------------|-------------------------------------------------------------------------------| +| maxNoSSBs | Maximum no of SSBs for which the configuration can be provided. Value is 255. | + +## 9.2.55 SSB Time/Frequency Configuration + +This information element contains the time and frequency configuration of an SSB. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------|----------|-------|-----------------------------------------------------------------------|------------------------------------------------------------------------| +| SSB frequency | M | | INTEGER (0..3279165) | ARFCN | +| SSB subcarrier spacing | M | | ENUMERATED(15k Hz, 30kHz, 60kHz, 120kHz, 240kHz,... , kHz480, kHz960) | The value 60kHz is not supported in this version of the specification. | +| SSB Transmit power | M | | INTEGER (-60..50) | EPRE of SSS | +| SSB periodicity | M | | ENUMERATED(5ms, 10ms, 20ms, 40ms, 80ms, 160ms, ...) | | +| SSB half frame index | M | | INTEGER(0..1) | | +| SSB SFN offset | M | | INTEGER(0..15) | | +| CHOICE SSB Position in Burst | O | | | | +| >Short Bitmap | | | BIT STRING (SIZE(4)) | | +| >Medium Bitmap | | | BIT STRING (SIZE(8)) | | +| >Long Bitmap | | | BIT STRING (SIZE(64)) | | +| SFN initialisation time | O | | Relative Time 1900 9.2.36 | | + +## 9.2.56 DL-PRS Muting Pattern + +This information element contains the DL-PRS muting pattern. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE DL-PRS Muting Pattern | M | | | | +| >Two | | | BIT STRING (SIZE(2)) | | +| >Four | | | BIT STRING (SIZE(4)) | | +| >Six | | | BIT STRING (SIZE(6)) | | +| >Eight | | | BIT STRING (SIZE(8)) | | +| >Sixteen | | | BIT STRING (SIZE(16)) | | +| >Thirty-two | | | BIT STRING (SIZE(32)) | | + +## 9.2.57 Measurement Beam Information + +This information element contains the receiving beam information when measuring UL signals. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------|-----------------------| +| PRS Resource ID | O | | INTEGER(0..63) | | +| PRS Resource Set ID | O | | INTEGER(0..7) | | +| SSB Index | O | | INTEGER(0..63) | | + +## 9.2.58 NR-PRS Beam Information + +This IE contains spatial direction information of the DL-PRS Resources. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------|----------|--------------------------------|-----------------------|------------------------------------------------------------------------|-------------|----------------------| +| NR-PRS Beam Information | | 1 | | | - | | +| >NR-PRS Beam Information Item | | 1.. | | | - | | +| >>PRS Resource Set ID | M | | INTEGER (0..7) | The resource set in which the resources are associated with the angle. | - | | +| >>PRS Angle | | 1 | | | - | | +| >>>PRS Angle Item | | 1.. | | | - | | +| >>>>NR PRS Azimuth | M | | INTEGER (0..359) | | - | | +| >>>>NR PRS Azimuth fine | O | | INTEGER (0..9) | Fine angles | - | | +| >>>>NR PRS Elevation | O | | INTEGER (0..180) | | - | | +| >>>>NR PRS Elevation fine | O | | INTEGER (0..9) | Fine angles | - | | +| >>>>PRS Resource ID | O | | INTEGER(0..63 ) | | YES | ignore | +| LCS to GCS Translation List | | 0..1 | | If absent, the azimuth and elevation are provided in GCS. | - | | +| >LCS to GCS Translation Item | | 1.. | | | - | | +| >>Alpha | M | | INTEGER (0..359) | | - | | +| >>Alpha-fine | O | | INTEGER (0..9) | Fine angles | - | | +| >>Beta | M | | INTEGER (0..359) | | - | | +| >>Beta-fine | O | | INTEGER (0..9) | Fine angles | - | | +| >>Gamma | M | | INTEGER (0..359) | | - | | +| >>Gamma-fine | O | | INTEGER (0..9) | Fine angles | - | | + +| Range bound | Explanation | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxPRS-ResourceSets | Maximum no of DL-PRS resource sets per TRP. Value is 2. | +| maxPRS-ResourcesPerSet | Maximum no of DL-PRS resources of the DL-PRS resource set of the TRP. Value is 64. | +| maxnolcs-gcs-translation | Maximum no. of LCS-GS-Translation-Parameters that can be reported with one message. Value is 3. The current version of the specification supports 1. | + +## 9.2.59 Positioning Broadcast Cells + +This IE is used to indicate the cells that are requested to broadcast, or failed to broadcast, the associated posSIB(s). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------|----------|--------------------------|-----------------------|-----------------------| +| Positioning Broadcast Cells | | 1 ..
| | | +| >NG-RAN-CGI | M | | 9.2.6 | | + +| Range bound | Explanation | +|-----------------|------------------------------------------------------------------------------| +| maxnoBcastCells | Maximum no. of cells broadcasting a posSIB in a NG-RAN node. Value is 16384. | + +## 9.2.60 Spatial Relation Information per SRS Resource + +This information element indicates a spatial relation for transmission of each UL SRS resource recommended by LMF. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------------|----------|-------------------------------|-----------------------|-----------------------| +| Spatial Relation per SRS Resource List | | 1 | | | +| >Spatial Relation per SRS Resource Item | | 1.. | | | +| >CHOICE Reference Signal | M | | | | +| >NZP CSI-RS | | | | | +| >>NZP CSI-RS Resource ID | M | | INTEGER (0..191) | | +| >SSB | | | | | +| >>NR PCI | M | | INTEGER (0..1007) | | +| >>SSB Index | O | | INTEGER (0..63) | | +| >SRS | | | | | +| >>SRS Resource ID | M | | INTEGER (0..63) | | +| >Positioning SRS | | | | | +| >>Positioning SRS Resource ID | M | | INTEGER (0..63) | | +| >DL-PRS | | | | | +| >>DL-PRS ID | M | | INTEGER (0..255) | | +| >>DL-PRS Resource | M | | INTEGER (0..7) | | + +| | | | | | +|----------------------|---|--|-----------------|--| +| Set ID | | | | | +| >>DL-PRS Resource ID | O | | INTEGER (0..63) | | + +| Range bound | Explanation | +|-------------------------|----------------------------------------------------------------| +| maxnoSRS-ResourcePerSet | Maximum no of SRS resources per SRS resource set. Value is 16. | + +## 9.2.61 Requested DL PRS Transmission Characteristics + +This IE contains the requested PRS configuration for transmission by the LMF. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------|----------|----------------------------|-------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------| +| Requested DL-PRS Resource Set List | | 1 | | | +| >Requested DL-PRS Resource Set Item | | 1.. | | | +| >>PRS bandwidth | O | | INTEGER(1..63) | 24,28,...,272 PRBs | +| >>Comb Size | O | | ENUMERATED(2, 4, 6, 12, ...) | | +| >>Resource Set Periodicity | O | | ENUMERATED(4,5, 8,10,16,20,32,40,64, 80,160,320,640,128 0,2560,5120,10240, 20480,40960,81920, ..., 128, 256, 512) | Slots | +| >>Resource Repetition Factor | O | | ENUMERATED(rf1,rf2,rf4,rf6,rf8,rf16,rf32, ...) | | +| >>Resource Number of Symbols | O | | ENUMERATED(n2, n4,n6,n12,...,n1) | | +| >>Requested DL-PRS Resource List | O | | 9.2.62 | | +| >>Resource Set Start Time and Duration | O | | Start Time and Duration 9.2.63 | This IE is ignored if the Start Time and Duration IE is present | +| Number of Frequency Layers | O | | INTEGER(1..4) | | +| Start Time and Duration | O | | 9.2.63 | | + +| Range bound | Explanation | +|-----------------------|----------------------------------------------| +| maxnoofPRSresourceSet | Maximum no of PRS resources set. Value is 8. | + +## 9.2.62 Requested DL-PRS Resource List + +This IE contains the requested DL-PRS resource list. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------| +| Requested DL-PRS Resource List | | 1 | | Corresponds to information provided in NR-DL-PRS-Resource contained in NR-DL- | + +| | | | | | +|-------------------------------------------|---|--------------------------------------|------------------|-------------------------------------------------| +| | | | | PRS-Info IE as defined in TS 37.355 [14] | +| >Requested DL-PRS Resource Item | | 1..<maxnoofPRSresource> | | | +| >>CHOICE QCL Info | O | | | | +| >>>SSB | | | | | +| >>>>NR PCI | M | | INTEGER(0..1007) | | +| >>>>SSB Index | O | | INTEGER(0..63) | | +| >>>DL-PRS | | | | | +| >>>>QCL Source PRS Resource Set ID | M | | INTEGER(0..7) | | +| >>>>QCL Source PRS Resource ID | O | | INTEGER(0..63) | | + +| Range bound | Explanation | +|--------------------|----------------------------------------------------------------| +| maxnoofPRSresource | Maximum no of PRS resources per PRS resource set. Value is 64. | + +## 9.2.63 Start Time and Duration + +This IE contains the start time and/or duration for the on-demand DL-PRS. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|---------------------------|-----------------------| +| Start Time | O | | Relative Time 1900 9.2.36 | | +| Duration | O | | INTEGER (0..90060, ...) | Unit: seconds | + +## 9.2.64 PRS Transmission Off Information + +This IE contains the information to turn off particular PRS transmissions. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-----------------------------------------|-----------------------|-----------------------| +| CHOICE level | M | | | | +| >TRP level | | | NULL | | +| >PRS resource set level | | | | | +| >>PRS Resource Set List | | 1 | | | +| >>>PRS Resource Set Item | | 1..<maxnoofPRSresourceSet> | | | +| >>>>PRS Resource Set ID | M | | INTEGER(0..7) | | +| >PRS resource level | | | | | +| >>PRS Resource Set List | | 1 | | | +| >>>PRS Resource Set Item | | 1..<maxnoofPRSresourceSet> | | | +| >>>>PRS Resource Set ID | M | | INTEGER(0..7) | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------------------------|-----------------------|-----------------------| +| >>>>PRS Resource List | | 1 | | | +| >>>>>PRS Resource Item | | 1.. | | | +| >>>>>>PRS Resource ID | M | | INTEGER(0..63) | | + +| Range bound | Explanation | +|-----------------------|----------------------------------------------------------------| +| maxnoofPRSresourceSet | Maximum no of PRS resources set. Value is 8. | +| maxnoofPRSresource | Maximum no of PRS resources per PRS resource set. Value is 64. | + +## 9.2.65 On-demand PRS TRP Information + +This IE contains on-demand PRS information for the TRP. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| On-demand PRS Request Allowed | M | | BIT STRING (SIZE(16)) | Each position in the bitmap represents an on-demand PRS transmission parameter:
first bit: Resource Set Periodicity
second bit: PRS Bandwidth
third bit: Resource Repetition Factor
fourth bit: Resource Number of Symbols
fifth bit: Comb Size
sixth bit: Number of Frequency Layers
seventh bit: Start Time and Duration
eighth bit: Off Indication
ninth bit: QCL Information
Other bits reserved for future use. Value '1' indicates 'request allowed', Value '0' indicates 'request not allowed'. | +| Allowed Resource Set Periodicity Values | O | | BIT STRING (SIZE(24)) | This IE applies only if the first bit of the On-demand PRS Request Allowed IE is set to '1'.

Each position in the bitmap represents a value of the Resource Set Periodicity IE defined in subclause 9.2.61, first bit = 4 and so on. Bit 24 is reserved for future use. Value '1' indicates 'request allowed', Value '0' indicates 'request not allowed'. If this IE is absent, all Resource Set Periodicity values are allowed to be requested. | +| Allowed PRS Bandwidth Values | O | | BIT STRING (SIZE(64)) | This IE applies only if the second bit of the On-demand PRS | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | Request Allowed IE is set to '1'.

Each position in the bitmap represents a value of the PRS Bandwidth IE defined in subclause 9.2.61, first bit = 1 and so on. Bit 64 is reserved for future use. Value '1' indicates 'request allowed', Value '0' indicates 'request not allowed'. If this IE is absent, all PRS Bandwidth values are allowed to be requested. | +| Allowed Resource Repetition Factor Values | O | | BIT STRING (SIZE(8)) | This IE applies only if the third bit of the On-demand PRS Request Allowed IE is set to '1'.

Each position in the bitmap represents a value of the Resource Repetition Factor IE defined in subclause 9.2.61, first bit = rf1 and so on. Bit 8 is reserved for future use. Value '1' indicates 'request allowed', Value '0' indicates 'request not allowed'. If this IE is absent, all Resource Repetition Factor values are allowed to be requested. | +| Allowed Resource Number of Symbols Values | O | | BIT STRING (SIZE(8)) | This IE applies only if the fourth bit of the On-demand PRS Request Allowed IE is set to '1'.

Each position in the bitmap represents a value of the Resource Number of Symbols IE defined in subclause 9.2.61, first bit = n2 and so on. Bits 6-8 are reserved for future use. Value '1' indicates 'request allowed', Value '0' indicates 'request not allowed'. If this IE is absent, all Resource Number of Symbols values are allowed to be requested. | +| Allowed Comb Size Values | O | | BIT STRING (SIZE(8)) | This IE applies only if the fifth bit of the On-demand PRS Request Allowed IE is set to '1'.

Each position in the bitmap represents a value of the Comb Size IE defined in subclause 9.2.61, first bit = 2 and so on. Bits 5-8 are reserved for future use. Value '1' indicates 'request allowed', Value '0' indicates 'request not allowed'. If this IE is | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------------------------------------------| +| | | | | absent, all Comb Size values are allowed to be requested. | + +## 9.2.66 UL-AoA assistance information + +This information element contains the expected uplink Angle of Arrival and uncertainty range. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE
AngleMeasurement | M | | | | +| >Expected UL Angle of Arrival | | | | | +| >>Expected Azimuth AoA | | 1 | | Defined as $(\phi_{\text{AOA}} - \Delta\phi_{\text{AOA}}/2, \phi_{\text{AOA}} + \Delta\phi_{\text{AOA}}/2)$ | +| >>>Expected Azimuth AoA Value | M | | INTEGER(0..3599) | $\phi_{\text{AOA}}$ component of Expected Azimuth AoA | +| >>>Expected Azimuth AoA Uncertainty Range | M | | INTEGER(0..3599) | $\Delta\phi_{\text{AOA}}$ component of Expected Azimuth AoA | +| >>Expected Zenith AoA | | 0..1 | | Defined as $(\theta_{\text{ZOA}} - \Delta\theta_{\text{ZOA}}/2, \theta_{\text{ZOA}} + \Delta\theta_{\text{ZOA}}/2)$ | +| >>>Expected Zenith AoA Value | M | | INTEGER(0..1799) | $\theta_{\text{ZOA}}$ component of Expected Zenith AoA | +| >>>Expected Zenith AoA Uncertainty Range | M | | INTEGER(0..1799) | $\Delta\theta_{\text{ZOA}}$ component of Expected Zenith AoA | +| >Expected UL Angle of Arrival Zenith Only | | | | Defined as $(\theta_{\text{ZOA}} - \Delta\theta_{\text{ZOA}}/2, \theta_{\text{ZOA}} + \Delta\theta_{\text{ZOA}}/2)$ | +| >>Expected Zenith AoA Value | M | | INTEGER(0..1799) | $\theta_{\text{ZOA}}$ component of Expected Zenith AoA | +| >>Expected Zenith AoA Uncertainty Range | M | | INTEGER(0..1799) | $\Delta\theta_{\text{ZOA}}$ component of Expected Zenith AoA | +| LCS to GCS Translation | O | | 9.2.69 | If absent, the azimuth and zenith are provided in GCS. In case of zenith only, the z-axis of LCS is defined along the linear array axis. | + +## 9.2.67 Z-AoA + +This information element contains the Zenith Angle of Arrival information, which can correspond to linear array measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------| +| Zenith Angle of Arrival | M | | INTEGER(0..1799) | TS 38.133 [16] | +| LCS to GCS Translation | O | | 9.2.69 | If absent, the zenith is provided in GCS. the z-axis of LCS is defined along the linear array axis | + +## 9.2.68 Response Time + +This information element contains the response time of the measurement results reporting. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|---------------------------------------------------------|-----------------------| +| Time | M | | INTEGER(1..128,...) | | +| Time Unit | M | | ENUMERATED (second, ten-seconds, ten-milliseconds, ...) | | + +## 9.2.69 LCS to GCS Translation + +This information element contains the LCS to GCS Translation information. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| Alpha | M | | INTEGER (0..3599) | | +| Beta | M | | INTEGER (0..3599) | | +| Gamma | M | | INTEGER (0..3599) | | + +## 9.2.70 UE Reporting Information + +This IE contains the UE Reporting Information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|---------------------------------------------------|-------------------------------------------------------------| +| Reporting Amount | M | | ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64) | Value 0 represents an infinite number of periodic reporting | +| Reporting Interval | M | | ENUMERATED (none, 1, 2, 4, 8, 10, 16, 20, 32, 64) | Unit: seconds | + +## 9.2.71 Multiple UL-AoA + +This information element contains the list of the multiple UL-AOAs values. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------|----------|--------------------|-----------------------|-----------------------| +| UL AoA List | | 1 | | | +| >UL AoA item | | 1.. | | | +| >>CHOICE
AngleMeasurement | M | | | | +| >>> UL Angle of Arrival | | | | | +| >>>>UL Angle of Arrival | M | | 9.2.38 | | +| >>> UL Zenith Angle of Arrival | | | | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-------|-----------------------|-----------------------| +| >>>>UL Zenith Angle of Arrival | M | | Z-AoA
9.2.67 | | + +| Range bound | Explanation | +|---------------|------------------------------------------------------------------------------------------| +| maxnoofULAoAs | Maximum no of UL-AOAs values (pair of AOA & ZOA values) that can be reported. Value is 8 | + +## 9.2.72 UL SRS-RSRP + +This information element contains the UL SRS Reference Signal Received Path Power measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|-----------------------|-----------------------| +| First Path RSRP Power | M | | INTEGER (0..126) | | + +## 9.2.73 SRS Resource type + +This IE contains the SRS resource type. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------|----------|-------|--------------------------------------------------|-----------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE Reference Signal | M | | | | - | | +| >SRS | | | | | | | +| >>SRS Resource ID | M | | INTEGER(0..63 ) | | - | | +| >Positioning SRS | | | | | | | +| >>Positioning SRS Resource ID | M | | INTEGER(0..63 ) | | - | | +| SRS Port Index | O | | ENUMERATED (id1000, id1001, id1002, id1003, ...) | This IE may be present if the SRS Resource ID IE is present, and is ignored otherwise. | YES | ignore | + +## 9.2.74 Extended Additional Path List + +This IE contains the extended additional path results of time measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------|----------|------------------------|-----------------------|-----------------------| +| Additional Path Item | | 1.. | | | +| >CHOICE Relative Path Delay | M | | | | +| >>k0 | | | INTEGER(0..16351) | | +| >>k1 | | | INTEGER(0..8176) | | +| >>k2 | | | INTEGER(0..4088) | | +| >>k3 | | | INTEGER(0..2044) | | +| >>k4 | | | INTEGER(0..1022) | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------|----------|-------|-------------------------------|-----------------------| +| >>k5 | | | INTEGER(0..511) | | +| >Path Quality | O | | Measurement Quality
9.2.43 | | +| >Multiple UL-AoA | O | | 9.2.71 | | +| >Path Power | O | | UL SRS-RSRPP
9.2.72 | | + +| Range bound | Explanation | +|-------------------|---------------------------------------------------------| +| maxNoPathExtended | Maximum no. of additional path measurement. Value is 8. | + +## 9.2.75 ARP ID + +This IE is used to uniquely identify an ARP associated with a TRP. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|-----------------------|-----------------------| +| ARP Identifier | M | | INTEGER (1..16, ...) | | + +## 9.2.76 ARP Location Information + +This IE contains the relative position of ARP(s) to the TRP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|----------------|---------------------------------------|-----------------------| +| ARP Location Information | | 1 | | | +| >ARP Location Information Item | | 1.. | | | +| >>ARP ID | M | | 9.2.75 | | +| >>CHOICE ARP Location Type | M | | | | +| >>>geodetic | | | | | +| >>>>ARP Position Relative Geodetic | M | | Relative Geodetic Location
9.2.48 | | +| >>>cartesian | | | | | +| >>>>ARP Position Relative Cartesian | M | | Relative Cartesian Location
9.2.50 | | + +| Range bound | Explanation | +|-------------|---------------------------------------------------------| +| maxnoARPs | Maximum no. of ARPs associated with a TRP. Value is 16. | + +## 9.2.77 LoS/NLoS Information + +This IE contains the LoS/NLoS information for UL measurement. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------|----------|-------|-----------------------|-----------------------| +| CHOICE LoS/NLoS | M | | | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|-------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Indicator | | | | | +| >Soft Indicator | | | | | +| >>LoS/NLoS Indicator
Soft | M | | INTEGER (0..10) | Values provide the likelihood of a LOS propagation path in the range between 0 and 1 with 0.1 steps resolution. Value '0' indicates NLOS and value '1' indicates LOS. | +| >Hard Indicator | | | | | +| >>LoS/NLoS Indicator
Hard | M | | ENUMERATED (NLoS, LoS) | | + +## 9.2.78 UE Tx TEG Association List + +This information element contains the list of UE Tx TEG associations. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------|----------|-------------------------------------------|----------------------------|----------------------------------------------------------|-------------|----------------------| +| UE Tx TEG Association item | | 1.. <maxno UETEGs> | | | - | | +| >UE Tx TEG ID | M | | INTEGER (0..7) | | - | | +| >Positioning SRS Resource ID List | | 1 | | | - | | +| >>Positioning SRS Resource ID Item | | 1.. <maxno SRS-PosResources> | | | - | | +| >>>Positioning SRS Resource ID | M | | INTEGER(0..63) | | - | | +| >Time Stamp | M | | 9.2.42 | | - | | +| >Carrier Frequency | | 0..1 | | Indicates the frequency of the positioning SRS resources | - | | +| >>Point A | M | | INTEGER (0..3279165) | NR ARFCN | - | | +| >>Offset to Carrier | M | | INTEGER (0.2199, ...) | | - | | +| >UE Tx Timing Error Margin | O | | Timing Error Margin 9.2.84 | Timing error margin associated to the UE Tx TEG ID. | YES | ignore | + +| Range bound | Explanation | +|-----------------------|--------------------------------------------------------------| +| maxnoUETEGs | Maximum no of reported UE Tx TEG associations. Value is 256. | +| maxnoSRS-PosResources | Maximum no of positioning SRS resources. Value is 64. | + +## 9.2.79 TRP Tx TEG Association + +This information element contains the TRP Tx TEG information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------------------------------------------|-----------------------|-----------------------| +| TRP TEG item | | 1..<maxnoTRP TEGs> | | | +| >TRP Tx TEG Information | M | | 9.2.86 | | +| >DL-PRS Resource Set ID | M | | INTEGER (0..7) | | +| >DL-PRS Resource ID List | | 0..1 | | | +| >>DL-PRS Resource ID Item | | 1..<maxPRS-ResourcesPer Set> | | | +| >>>DL-PRS Resource ID | M | | INTEGER (0..63) | | + +| Range bound | Explanation | +|------------------------|------------------------------------------------------------------------------------| +| maxnoTRPTEGs | Maximum no of reported TRP Tx TEG association. Value is 8. | +| maxPRS-ResourcesPerSet | Maximum no of DL-PRS resources of the DL-PRS resource set of the TRP. Value is 64. | + +## 9.2.80 TRP TEG Information + +This information element contains the TRP TEG information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE TRP TEG | M | | | | +| > RxTx TEG | | | | | +| >>TRP RxTx TEG Information | M | | 9.2.87 | | +| >>TRP Tx TEG Information | O | | 9.2.86 | | +| > Rx TEG | | | | | +| >>TRP Rx TEG Information | M | | 9.2.85 | | +| >>TRP Tx TEG Information | M | | 9.2.86 | | + +## 9.2.81 Measurement Characteristics Request Indicator + +This IE contains the measurement characteristic information requested by LMF. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement characteristic request indicator | M | | BIT STRING (SIZE(16)) | Each position in the bitmap represents a requested measurement characteristic:

first bit: Measurement Beam Information

Second bit: Extended Additional Path List | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | |

Third bit: Additional Path Power

Fourth Bit: Multiple UL AoA of Additional Path

Fifth bit: LoS/NLoS Information

Sixth bit: TRP Rx TEG association for UL-TDOA

Seventh bit: TRP RxTxTEG-ID information for DL+UL positioning.

Eighth bit: SRS Resource Type

Ninth bit: Multiple Measurement Instances

Tenth bit: Mobile TRP location information

Other bits reserved for future use. Value '1' indicates 'requested measurement characteristic', Value '0' indicates 'not requested'.

| + +## 9.2.82 TRP Beam Antenna Information + +The IE provides the beam antenna information of the TRP. It includes either the explicit beam antenna information, or a reference to another TRP's signalled configuration, or the indication that no change has occurred with respect to previously signalled configuration. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE TRP Beam Antenna Info Item | M | | | | +| >Reference | | | | | +| >>Associated TRP ID | M | | TRP ID 9.2.24 | This IE specifies the TRP ID of the associated TRP from which the beam information parameters are adopted in Local Coordinate System (LCS). | +| >Explicit | | | | | +| >>TRP Beam Antenna Angles | M | | 9.2.83 | | +| >>LCS to GCS Translation | O | | 9.2.69 | Included if the azimuth and elevation are not provided in GCS. | +| >No Change | | | NULL | No change compared to the previously signalled configuration for this TRP. | + +## 9.2.83 TRP Beam Antenna Angles + +The IE provides the beam antenna information of the TRP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|--------------------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TRP Beam Antenna Angles Item | | 1..<
maxnoAzimuth
Angles> | | | +| >TRP Azimuth Angle | M | | INTEGER (0..359) | For GCS, the azimuth angle is measured counter-clockwise from geographical North. For LCS, the azimuth angle is measured counter-clockwise from the x-axis of the LCS. | +| >TRP Azimuth Angle fine | O | | INTEGER (0..9) | Fine angle | +| >TRP Elevation Angle List | | 1 | | | +| >>TRP Elevation Angle Item | | 1.. | | | +| >>>TRP Elevation Angle | M | | INTEGER (0..180) | For 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 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). | +| >>>TRP Elevation Angle fine | O | | INTEGER (0..9) | Fine angle | +| >>>TRP Beam Power List | | 1 | | Relative power between DL-PRS Resources for the given Azimuth and Elevation Angle. The first Relative Power element in this list provides the peak power for this Azimuth/Elevation angle and is defined as 0dB power. All the remaining Relative Power Element's in this list provide the relative DL-PRS Resource power relative to this first element in the list. | +| >>>>TRP Beam Power Item | | 2..<
maxNumResourcesPerAngle
> | | | +| >>>>>PRS Resource Set ID | O | | INTEGER (0..7) | DL-PRS Resource Set ID of the DL-PRS Resource for which the Relative Power is provided. If this field is absent, the DL-PRS Resource Set ID for this instance of the Beam Power List is the same as the DL-PRS Resource | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | Set ID of the previous instance in the Beam Power List. This field shall be included at least in the first instance of the Beam Power List. | +| >>>>>PRS Resource ID | M | | INTEGER (0..63) | DL-PRS Resource for which the Relative Power is provided. | +| >>>>>TRP Beam Relative Power | M | | INTEGER (0..30) | The power values span from -30 to 0dB | +| >>>>>TRP Beam Relative Power "fine" | O | | INTEGER (0..9) | Relative Power with 0.1dB resolution. The power spans from -0.9 to 0dB | + +| Range bound | Explanation | +|-------------------------|--------------------------------------------------------------------------| +| maxNumResourcesPerAngle | Maximum number of DL-PRS Resources per angle per TRP. Value is 24. | +| maxnoAzimuthAngles | Maximum number of azimuth angles per TRP. Value is 3600. | +| maxnoElevationAngles | Maximum number of elevation angles per azimuth angle/TRP. Value is 1801. | + +## 9.2.84 Timing Error Margin + +This information element contains the Timing error margin for the UE Tx TEG, TRP Rx TEG, or TRP Tx TEG. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|------------------------------------------------------------------------------------------------------------|-----------------------| +| Timing Error Margin | M | | ENUMERATED(Tc0, Tc2, Tc4, Tc6, Tc8, Tc12, Tc16, Tc20, Tc24, Tc32, Tc40, Tc48, Tc56, Tc64, Tc72, Tc80, ...) | | + +## 9.2.85 TRP Rx TEG Information + +This information element contains the TRP Rx TEG information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------|----------|-------|----------------------------|------------------------------------------------------| +| TRP Rx TEG ID | M | | INTEGER (0..31) | | +| TRP Rx Timing Error Margin | M | | Timing Error Margin 9.2.84 | Timing error margin associated to the TRP Rx TEG ID. | + +## 9.2.86 TRP Tx TEG Information + +This information element contains the TRP Tx TEG information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------|----------|-------|-----------------------|--------------------------------| +| TRP Tx TEG ID | M | | INTEGER (0..7) | | +| TRP Tx Timing Error Margin | M | | Timing Error Margin | Timing error margin associated | + +| | | | | | +|--------|--|--|--------|-----------------------| +| Margin | | | 9.2.84 | to the TRP Tx TEG ID. | +|--------|--|--|--------|-----------------------| + +## 9.2.87 TRP RxTx TEG Information + +This information element contains the TRP RxTx TEG information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|-------|---------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------| +| TRP RxTx TEG ID | M | | INTEGER (0..255) | | +| TRP RxTx Timing Error Margin | M | | ENUMERATED
(Tc0dot5, Tc1, Tc2, Tc4, Tc8, Tc12, Tc16, Tc20, Tc24, Tc32, Tc40, Tc48, Tc64, Tc80, Tc96, Tc128, ...) | Timing error margin associated to the TRP RxTx TEG ID. | + +## 9.2.88 Mobile TRP Location Information + +This IE contains location information for one mobile TRP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------| +| Location Information | O | | OCTET STRING | Location of the mobile TRP, Includes the locationEstimate IE as defined in TS 37.355 [14] | +| Velocity Information | O | | OCTET STRING | Velocity of the mobile TRP, Includes the velocityEstimate IE as defined in TS 37.355 [14] | +| Location Time stamp | O | | Time Stamp
9.2.42 | Indicates the time when the mobile TRP location information is generated. | + +## 9.2.89 Common TA Parameters + +This information element contains the Common TA parameters for an NG-RAN node. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|--------------------------------------------------------------| +| EpochTime | M | | OCTET STRING | Includes the EpochTime IE as defined in TS 38.331[13] | +| TA Info | M | | OCTET STRING | Includes the TA-Info IE as defined in TS 38.331[13] | + +## 9.3 Message and Information Element Abstract Syntax (with ASN.1) + +### 9.3.1 General + +Sub clause 9.3 presents the Abstract Syntax of the NRPPa protocol with ASN.1. In case there is contradiction between the ASN.1 definition in this sub clause and the tabular format in sub clause 9.1 and 9.2, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, in which the tabular format shall take precedence. + +The ASN.1 definition specifies the structure and content of NRPPa messages. NRPPa 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 NRPPa 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 needs 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 in which 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 an NRPPa 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.3.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 inter-operability. +- by vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation. + +The private message mechanism shall not be used for basic functionality. Such functionality shall be standardised. + +### 9.3.3 Elementary Procedure Definitions + +-- ASN1START + +``` +-- ***** +-- +-- Elementary Procedure definitions +-- +-- ***** +``` + +``` +NRPPA-PDU-Descriptions { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + ngran-access (22) modules (3) nrppa (4) version1 (1) nrppa-PDU-Descriptions (0) } +``` + +``` +DEFINITIONS AUTOMATIC TAGS ::= +``` + +``` +BEGIN +``` + +``` +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** +``` + +``` +IMPORTS +``` + +``` + Criticality, + ProcedureCode, +``` + +NRPPATransactionID + +FROM NRPPA-CommonDataTypes + +ErrorIndication, + +PrivateMessage, + +E-CIDMeasurementInitiationRequest, + +E-CIDMeasurementInitiationResponse, + +E-CIDMeasurementInitiationFailure, + +E-CIDMeasurementFailureIndication, + +E-CIDMeasurementReport, + +E-CIDMeasurementTerminationCommand, + +OTDOAInformationRequest, + +OTDOAInformationResponse, + +OTDOAInformationFailure, + +AssistanceInformationControl, + +AssistanceInformationFeedback, + +PositioningInformationRequest, + +PositioningInformationResponse, + +PositioningInformationFailure, + +PositioningInformationUpdate, + +MeasurementRequest, + +MeasurementResponse, +MeasurementFailure, +MeasurementReport, +MeasurementUpdate, +MeasurementAbort, +MeasurementFailureIndication, +TRPInformationRequest, +TRPInformationResponse, +TRPInformationFailure, +PositioningActivationRequest, +PositioningActivationResponse, +PositioningActivationFailure, +PositioningDeactivation, +PRSConfigurationRequest, +PRSConfigurationResponse, +PRSConfigurationFailure, +MeasurementPreconfigurationRequired, +MeasurementPreconfigurationConfirm, +MeasurementPreconfigurationRefuse, +MeasurementActivation + +FROM NRPPA-PDU-Contents + +id-errorIndication, +id-privateMessage, +id-e-CIDMeasurementInitiation, +id-e-CIDMeasurementFailureIndication, +id-e-CIDMeasurementReport, +id-e-CIDMeasurementTermination, +id-oTDOAInformationExchange, +id-assistanceInformationControl, +id-assistanceInformationFeedback, +id-positioningInformationExchange, +id-positioningInformationUpdate, +id-Measurement, +id-MeasurementReport, +id-MeasurementUpdate, +id-MeasurementAbort, +id-MeasurementFailureIndication, +id-tRPInformationExchange, +id-positioningActivation, +id-positioningDeactivation, +id-pRSConfigurationExchange, +id-measurementPreconfiguration, +id-measurementActivation + +``` +FROM NRPPA-Constants; +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- Interface Elementary Procedure Class +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +NRPPA-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 +-- +-- ***** + +NRPPA-PDU ::= CHOICE { + initiatingMessage InitiatingMessage, + successfulOutcome SuccessfulOutcome, + unsuccessfulOutcome UnsuccessfulOutcome, + ... +} + +InitiatingMessage ::= SEQUENCE { + procedureCode NRPPA-ELEMENTARY-PROCEDURE.&procedureCode ({NRPPA-ELEMENTARY-PROCEDURES}), + criticality NRPPA-ELEMENTARY-PROCEDURE.&criticality ({NRPPA-ELEMENTARY-PROCEDURES}{@procedureCode}), + nrppatransactionID NRPPATransactionID, + value NRPPA-ELEMENTARY-PROCEDURE.&InitiatingMessage ({NRPPA-ELEMENTARY-PROCEDURES}{@procedureCode}) +} +``` + +``` + +SuccessfulOutcome ::= SEQUENCE { + procedureCode NRPPA-ELEMENTARY-PROCEDURE.&procedureCode ({NRPPA-ELEMENTARY-PROCEDURES}), + criticality NRPPA-ELEMENTARY-PROCEDURE.&criticality ({NRPPA-ELEMENTARY-PROCEDURES}{@procedureCode}), + nrppatransactionID NRPPATransactionID, + value NRPPA-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({NRPPA-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +``` + +``` + +UnsuccessfulOutcome ::= SEQUENCE { + procedureCode NRPPA-ELEMENTARY-PROCEDURE.&procedureCode ({NRPPA-ELEMENTARY-PROCEDURES}), + criticality NRPPA-ELEMENTARY-PROCEDURE.&criticality ({NRPPA-ELEMENTARY-PROCEDURES}{@procedureCode}), + nrppatransactionID NRPPATransactionID, + value NRPPA-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({NRPPA-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +``` + +``` + +-- ***** +-- +-- Interface Elementary Procedure List +-- +-- ***** + +``` + +``` + +NRPPA-ELEMENTARY-PROCEDURES NRPPA-ELEMENTARY-PROCEDURE ::= { + NRPPA-ELEMENTARY-PROCEDURES-CLASS-1 +} + +``` + +``` +NRPPA-ELEMENTARY-PROCEDURES-CLASS-2 , + ... +} + +NRPPA-ELEMENTARY-PROCEDURES-CLASS-1 NRPPA-ELEMENTARY-PROCEDURE ::= { + e-CIDMeasurementInitiation | + oTDOAInformationExchange | + positioningInformationExchange | + measurement | + tRPInformationExchange | + positioningActivation | + pRSConfigurationExchange | + measurementPreconfiguration, + ... +} + +NRPPA-ELEMENTARY-PROCEDURES-CLASS-2 NRPPA-ELEMENTARY-PROCEDURE ::= { + e-CIDMeasurementFailureIndication | + e-CIDMeasurementReport | + e-CIDMeasurementTermination | + errorIndication | + privateMessage | +``` + +``` + + assistanceInformationControl | + assistanceInformationFeedback | + positioningInformationUpdate | + measurementReport | + measurementUpdate | + measurementAbort | + measurementFailureIndication | + positioningDeactivation | + measurementActivation, + ... + } + +-- ***** +-- +-- Interface Elementary Procedures +-- +-- ***** + +e-CIDMeasurementInitiation NRPPA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE E-CIDMeasurementInitiationRequest + SUCCESSFUL OUTCOME E-CIDMeasurementInitiationResponse + UNSUCCESSFUL OUTCOME E-CIDMeasurementInitiationFailure +} + +``` + +``` +PROCEDURE CODE id-e-CIDMeasurementInitiation +CRITICALITY reject +} + +e-CIDMeasurementFailureIndication NRPPA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE E-CIDMeasurementFailureIndication + PROCEDURE CODE id-e-CIDMeasurementFailureIndication + CRITICALITY ignore +} + +e-CIDMeasurementReport NRPPA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE E-CIDMeasurementReport + PROCEDURE CODE id-e-CIDMeasurementReport + CRITICALITY ignore +} + +e-CIDMeasurementTermination NRPPA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE E-CIDMeasurementTerminationCommand + PROCEDURE CODE id-e-CIDMeasurementTermination + CRITICALITY reject +} + +oTDOAInformationExchange NRPPA-ELEMENTARY-PROCEDURE ::= { +``` + +``` + INITIATING MESSAGE OTDOAInformationRequest + SUCCESSFUL OUTCOME OTDOAInformationResponse + UNSUCCESSFUL OUTCOME OTDOAInformationFailure + PROCEDURE CODE id-oTDOAInformationExchange + CRITICALITY reject +} + +assistanceInformationControl NRPPA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE AssistanceInformationControl + PROCEDURE CODE id-assistanceInformationControl + CRITICALITY reject +} + +assistanceInformationFeedback NRPPA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE AssistanceInformationFeedback + PROCEDURE CODE id-assistanceInformationFeedback + CRITICALITY reject +} + +errorIndication NRPPA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE ErrorIndication +``` + +``` + PROCEDURE CODE id-errorIndication + CRITICALITY ignore +} + +privateMessage NRPPA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PrivateMessage + PROCEDURE CODE id-privateMessage + CRITICALITY ignore +} + +positioningInformationExchange NRPPA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositioningInformationRequest + SUCCESSFUL OUTCOME PositioningInformationResponse + UNSUCCESSFUL OUTCOME PositioningInformationFailure + PROCEDURE CODE id-positioningInformationExchange + CRITICALITY reject +} + +positioningInformationUpdate NRPPA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositioningInformationUpdate + PROCEDURE CODE id-positioningInformationUpdate +} +``` + +``` + CRITICALITY ignore + + } + + measurement NRPPA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MeasurementRequest + SUCCESSFUL OUTCOME MeasurementResponse + UNSUCCESSFUL OUTCOME MeasurementFailure + PROCEDURE CODE id-Measurement + CRITICALITY reject + } + + measurementReport NRPPA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MeasurementReport + PROCEDURE CODE id-MeasurementReport + CRITICALITY ignore + } + + measurementUpdate NRPPA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MeasurementUpdate + PROCEDURE CODE id-MeasurementUpdate + CRITICALITY ignore + } +``` + +``` +measurementAbort NRPPA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MeasurementAbort + PROCEDURE CODE id-MeasurementAbort + CRITICALITY ignore +} + +measurementFailureIndication NRPPA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MeasurementFailureIndication + PROCEDURE CODE id-MeasurementFailureIndication + CRITICALITY ignore +} + +tRPInformationExchange NRPPA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE TRPInformationRequest + SUCCESSFUL OUTCOME TRPInformationResponse + UNSUCCESSFUL OUTCOME TRPInformationFailure + PROCEDURE CODE id-tRPInformationExchange + CRITICALITY reject +} + +positioningActivation NRPPA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositioningActivationRequest + SUCCESSFUL OUTCOME PositioningActivationResponse +``` + +``` + UNSUCCESSFUL OUTCOME PositioningActivationFailure + + PROCEDURE CODE id-positioningActivation + + CRITICALITY reject + +} + +positioningDeactivation NRPPA-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE PositioningDeactivation + + PROCEDURE CODE id-positioningDeactivation + + CRITICALITY ignore + +} + +pRSConfigurationExchange NRPPA-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE PRSConfigurationRequest + + SUCCESSFUL OUTCOME PRSConfigurationResponse + + UNSUCCESSFUL OUTCOME PRSConfigurationFailure + + PROCEDURE CODE id-pRSConfigurationExchange + + CRITICALITY reject + +} + +measurementPreconfiguration NRPPA-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE MeasurementPreconfigurationRequired + + SUCCESSFUL OUTCOME MeasurementPreconfigurationConfirm + + UNSUCCESSFUL OUTCOME MeasurementPreconfigurationRefuse +``` + +``` + + PROCEDURE CODE id-measurementPreconfiguration + + CRITICALITY reject + +} + +``` + +``` + +measurementActivation NRPPA-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE MeasurementActivation + + PROCEDURE CODE id-measurementActivation + + CRITICALITY ignore + +} + +``` + +END + +-- ASN1STOP + +### 9.3.4 PDU Definitions + +-- ASN1START + +-- \*\*\*\*\* + +-- + +-- PDU definitions for NRPPa + +-- + +-- \*\*\*\*\* + +NRPPA-PDU-Contents { + +``` +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +ngran-access (22) modules (3) nrppa (4) version1 (1) nrppa-PDU-Contents (1) } +``` + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +``` +-- ***** +-- +-- IE parameter types from other modules +-- +-- ***** +``` + +IMPORTS + +``` +Cause, +CriticalityDiagnostics, +E-CID-MeasurementResult, +OTDOACells, +OTDOA-Information-Item, +Measurement-ID, +UE-Measurement-ID, +MeasurementPeriodicity, +``` + +MeasurementQuantities, +ReportCharacteristics, +RequestedSRSTransmissionCharacteristics, +Cell-Portion-ID, +OtherRATMeasurementQuantities, +OtherRATMeasurementResult, +WLANMeasurementQuantities, +WLANMeasurementResult, +Assistance-Information, +Broadcast, +AssistanceInformationFailureList, +SRSConfiguration, +TRPMeasurementQuantities, +TrpMeasurementResult, +TRP-ID, +TRPInformationTypeListTRPReq, +TRPInformationListTRPResp, +TRP-MeasurementRequestList, +TRP-MeasurementResponseList, +TRP-MeasurementUpdateList, +MeasurementBeamInfoRequest, +PositioningBroadcastCells, +SRSResourceSetID, + +SpatialRelationInfo, +SRSResourceTrigger, +TRPList, +AbortTransmission, +SystemFrameNumber, +SlotNumber, +RelativeTime1900, +SpatialRelationPerSRSResource, +MeasurementPeriodicityExtended, +PRSTRPList, +PRSTransmissionTRPList, +ResponseTime, +UEReportingInformation, +UETxTEGAssociationList, +TRP-PRS-Information-List, +PRS-Measurements-Info-List, +UE-TEG-Info-Request, +MeasurementCharacteristicsRequestIndicator, +MeasurementTimeOccasion, +PRSConfigRequestType, +MeasurementAmount, +PreconfigurationResult, +RequestType, + +UE-TEG-ReportingPeriodicity, +MeasurementPeriodicityNR-AoA, +SRSTransmissionStatus, +CGI-NR + +FROM NRPPA-IEs + +PrivateIE-Container{}, +ProtocolExtensionContainer{}, +ProtocolIE-Container{}, +ProtocolIE-ContainerList{}, +ProtocolIE-Single-Container{}, +NRPPA-PRIVATE-IEs, +NRPPA-PROTOCOL-EXTENSION, +NRPPA-PROTOCOL-IEs + +FROM NRPPA-Containers + +maxnoOTDOAtypes, +id-Cause, +id-CriticalityDiagnostics, + +id-LMF-Measurement-ID, +id-LMF-UE-Measurement-ID, +id-OTDOACells, +id-OTDOA-Information-Type-Group, +id-OTDOA-Information-Type-Item, +id-ReportCharacteristics, +id-MeasurementPeriodicity, +id-MeasurementQuantities, +id-RAN-Measurement-ID, +id-RAN-UE-Measurement-ID, +id-E-CID-MeasurementResult, +id-RequestedSRSTransmissionCharacteristics, +id-Cell-Portion-ID, +id-OtherRATMeasurementQuantities, +id-OtherRATMeasurementResult, +id-WLANMeasurementQuantities, +id-WLANMeasurementResult, +id-Assistance-Information, +id-Broadcast, +id-AssistanceInformationFailureList, +id-SRSConfiguration, +id-TRPMeasurementQuantities, +id-MeasurementResult, + +id-TRP-ID, +id-TRPInformationTypeListTRPReq, +id-TRPInformationListTRPResp, +id-TRP-MeasurementRequestList, +id-TRP-MeasurementResponseList, +id-TRP-MeasurementReportList, +id-TRP-MeasurementUpdateList, +id-MeasurementBeamInfoRequest, +id-PositioningBroadcastCells, +id-SRSType, +id-ActivationTime, +id-SRSResourceSetID, +id-TRPList, +id-SRSSpatialRelation, +id-AbortTransmission, +id-SystemFrameNumber, +id-SlotNumber, +id-SRSResourceTrigger, +id-SFNInitialisationTime, +id-SRSSpatialRelationPerSRSResource, +id-MeasurementPeriodicityExtended, +id-PRSTRPList, +id-PRSTransmissionTRPList, + +``` + +id-ResponseTime, +id-UEReportingInformation, +id-UETxTEGAssociationList, +id-TRP-PRS-Information-List, +id-PRS-Measurements-Info-List, +id-UE-TEG-Info-Request, +id-MeasurementCharacteristicsRequestIndicator, +id-MeasurementTimeOccasion, +id-PRSConfigRequestType, +id-MeasurementAmount, +id-PreconfigurationResult, +id-RequestType, +id-UE-TEG-ReportingPeriodicity, +id-MeasurementPeriodicityNR-AoA, +id-SRSTransmissionStatus, +id-NewNRCGI + +``` + +FROM NRPPA-Constants; + +-- \*\*\*\*\* + +``` + +-- +-- E-CID MEASUREMENT INITIATION REQUEST +-- +-- ***** + +E-CIDMeasurementInitiationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {E-CIDMeasurementInitiationRequest-IEs}, + ... +} + +E-CIDMeasurementInitiationRequest-IEs NRPPA-PROTOCOL-IES ::= { + { ID id-LMF-UE-Measurement-ID CRITICALITY reject TYPE UE-Measurement-ID PRESENCE mandatory}| + { ID id-ReportCharacteristics CRITICALITY reject TYPE ReportCharacteristics PRESENCE mandatory}| + { ID id-MeasurementPeriodicity CRITICALITY reject TYPE MeasurementPeriodicity PRESENCE conditional}| +-- The IE shall be present if the Report Characteritics IE is set to "periodic" -- + { ID id-MeasurementQuantities CRITICALITY reject TYPE MeasurementQuantities PRESENCE mandatory}| + { ID id-OtherRATMeasurementQuantities CRITICALITY ignore TYPE OtherRATMeasurementQuantities PRESENCE optional}| + { ID id-WLANMeasurementQuantities CRITICALITY ignore TYPE WLANMeasurementQuantities PRESENCE optional}| + { ID id-MeasurementPeriodicityNR-AoA CRITICALITY reject TYPE MeasurementPeriodicityNR-AoA PRESENCE conditional}, +-- The IE shall be present if the Report Characteritics IE is set to "periodic" and the MeasurementQuantities-Item IE in the MeasurementQuantities +-- IE is set to the value "angleOfArrivalNR" -- + ... +} + +``` + +``` + +-- ***** +-- +-- E-CID MEASUREMENT INITIATION RESPONSE +-- +-- ***** + +``` + +``` + +E-CIDMeasurementInitiationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {E-CIDMeasurementInitiationResponse-IEs}, + ... +} + +``` + +``` + +E-CIDMeasurementInitiationResponse-IEs NRPPA-PROTOCOL-IES ::= { + { ID id-LMF-UE-Measurement-ID CRITICALITY reject TYPE UE-Measurement-ID PRESENCE mandatory}| + { ID id-RAN-UE-Measurement-ID CRITICALITY reject TYPE UE-Measurement-ID PRESENCE mandatory}| + { ID id-E-CID-MeasurementResult CRITICALITY ignore TYPE E-CID-MeasurementResult PRESENCE optional}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}| + { ID id-Cell-Portion-ID CRITICALITY ignore TYPE Cell-Portion-ID PRESENCE optional}| + { ID id-OtherRATMeasurementResult CRITICALITY ignore TYPE OtherRATMeasurementResult PRESENCE optional}| + { ID id-WLANMeasurementResult CRITICALITY ignore TYPE WLANMeasurementResult PRESENCE optional}, + ... +} + +``` + +``` + +-- ***** + +``` + +``` + +-- +-- E-CID MEASUREMENT INITIATION FAILURE +-- +-- ***** + +E-CIDMeasurementInitiationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{E-CIDMeasurementInitiationFailure-IEs}}, + ... +} + +E-CIDMeasurementInitiationFailure-IEs NRPPA-PROTOCOL-IES ::= { + { ID id-LMF-UE-Measurement-ID CRITICALITY reject TYPE UE-Measurement-ID PRESENCE mandatory}| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}, + ... +} + +-- ***** +-- +-- E-CID MEASUREMENT FAILURE INDICATION +-- +-- ***** + +``` + +``` + +E-CIDMeasurementFailureIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{E-CIDMeasurementFailureIndication-IEs}}, + ... +} + +``` + +``` + +E-CIDMeasurementFailureIndication-IEs NRPPA-PROTOCOL-IES ::= { + { ID id-LMF-UE-Measurement-ID CRITICALITY reject TYPE UE-Measurement-ID PRESENCE mandatory}| + { ID id-RAN-UE-Measurement-ID CRITICALITY reject TYPE UE-Measurement-ID PRESENCE mandatory}| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}, + ... +} + +``` + +``` + +-- ***** +-- +-- E-CID MEASUREMENT REPORT +-- +-- ***** + +``` + +``` + +E-CIDMeasurementReport ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{E-CIDMeasurementReport-IEs}}, + ... +} + +``` + +``` + +} + +E-CIDMeasurementReport-IEs NRPFA-PROTOCOL-IEs ::= { + { ID id-LMF-UE-Measurement-ID CRITICALITY reject TYPE UE-Measurement-ID PRESENCE mandatory}| + { ID id-RAN-UE-Measurement-ID CRITICALITY reject TYPE UE-Measurement-ID PRESENCE mandatory}| + { ID id-E-CID-MeasurementResult CRITICALITY ignore TYPE E-CID-MeasurementResult PRESENCE mandatory}| + { ID id-Cell-Portion-ID CRITICALITY ignore TYPE Cell-Portion-ID PRESENCE optional}, + ... +} + +``` + +``` + +-- ***** +-- +-- E-CID MEASUREMENT TERMINATION +-- +-- ***** + +``` + +``` + +E-CIDMeasurementTerminationCommand ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{E-CIDMeasurementTerminationCommand-IEs}}, + ... +} + +``` + +``` + +E-CIDMeasurementTerminationCommand-IEs NRPPA-PROTOCOL-IES ::= { + { ID id-LMF-UE-Measurement-ID CRITICALITY reject TYPE UE-Measurement-ID PRESENCE mandatory}| + { ID id-RAN-UE-Measurement-ID CRITICALITY reject TYPE UE-Measurement-ID PRESENCE mandatory}, + ... +} + +-- ***** +-- +-- OTDOA INFORMATION REQUEST +-- +-- ***** + +OTDOAInformationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{OTDOAInformationRequest-IEs}}, + ... +} + +OTDOAInformationRequest-IEs NRPPA-PROTOCOL-IES ::= { + { ID id-OTDOA-Information-Type-Group CRITICALITY reject TYPE OTDOA-Information-Type PRESENCE mandatory}, + ... +} + +OTDOA-Information-Type ::= SEQUENCE (SIZE(1..maxnoOTDOATypes)) OF ProtocolIE-Single-Container { { OTDOA-Information-Type-ItemIEs } } + +``` + +``` + +OTDOA-Information-Type-ItemIEs NRPPA-PROTOCOL-IES ::= { + { ID id-OTDOA-Information-Type-Item CRITICALITY reject TYPE OTDOA-Information-Type-Item PRESENCE mandatory}, + ... +} + +``` + +``` + +OTDOA-Information-Type-Item ::= SEQUENCE { + oTDOA-Information-Item OTDOA-Information-Item, + iE-Extensions ProtocolExtensionContainer { { OTDOA-Information-Type-ItemExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +OTDOA-Information-Type-ItemExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +-- ***** +-- +-- OTDOA INFORMATION RESPONSE +-- +-- ***** + +``` + +``` + +OTDOAInformationResponse ::= SEQUENCE { + +``` + +``` + +protocolIEs ProtocolIE-Container {{OTDOAInformationResponse-IEs}}, +... +} + +``` + +``` + +OTDOAInformationResponse-IEs NRPPA-PROTOCOL-IEs ::= { + { ID id-OTDOACells CRITICALITY ignore TYPE OTDOACells PRESENCE mandatory}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}, + ... +} + +``` + +``` + +-- ***** +-- +-- OTDOA INFORMATION FAILURE +-- +-- ***** + +``` + +``` + +OTDOAInformationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{OTDOAInformationFailure-IEs}}, + ... +} + +``` + +``` + +OTDOAInformationFailure-IEs NRPPA-PROTOCOL-IEs ::= { + +``` + +``` +{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}| +{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}, +... +} + +-- ***** +-- +-- ASSISTANCE INFORMATION CONTROL +-- +-- ***** + +AssistanceInformationControl ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{AssistanceInformationControl-IEs}}, + ... +} + +AssistanceInformationControl-IEs NRPPA-PROTOCOL-IES ::= { + { ID id-Assistance-Information CRITICALITY reject TYPE Assistance-Information PRESENCE optional}| + { ID id-Broadcast CRITICALITY reject TYPE Broadcast PRESENCE optional}| + { ID id-PositioningBroadcastCells CRITICALITY reject TYPE PositioningBroadcastCells PRESENCE optional}, + ... +} +``` + +``` + +-- ***** +-- +-- ASSISTANCE INFORMATION FEEDBACK +-- +-- ***** + +``` + +``` + +AssistanceInformationFeedback ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{AssistanceInformationFeedback-IEs}}, + ... +} + +``` + +``` + +AssistanceInformationFeedback-IEs NRPPA-PROTOCOL-IES ::= { + { ID id-AssistanceInformationFailureList CRITICALITY reject TYPE AssistanceInformationFailureList PRESENCE optional}| + { ID id-PositioningBroadcastCells CRITICALITY reject TYPE PositioningBroadcastCells PRESENCE optional}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}, + ... +} + +``` + +``` + +-- ***** +-- +-- ERROR INDICATION +-- + +``` + +-- \*\*\*\*\* + +ErrorIndication ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    {{ErrorIndication-IEs}}, + +    ... + +} + +ErrorIndication-IEs NRPPA-PROTOCOL-IES ::= { + +    { ID id-Cause                                    CRITICALITY ignore    TYPE Cause                                    PRESENCE optional}| + +    { ID id-CriticalityDiagnostics    CRITICALITY ignore    TYPE CriticalityDiagnostics PRESENCE optional}, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- PRIVATE MESSAGE + +-- + +-- \*\*\*\*\* + +PrivateMessage ::= SEQUENCE { + +    privateIEs    PrivateIE-Container    {{PrivateMessage-IEs}}, + +    ... + +``` + +} + +PrivateMessage-IEs NRPPA-PRIVATE-IEs ::= { + ... +} + +-- ***** +-- +-- POSITIONING INFORMATION REQUEST +-- +-- ***** + +PositioningInformationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{PositioningInformationRequest-IEs}}, + ... +} + +PositioningInformationRequest-IEs NRPPA-PROTOCOL-IEs ::= { + { ID id-RequestedSRSTransmissionCharacteristics CRITICALITY ignore TYPE RequestedSRSTransmissionCharacteristics PRESENCE optional }| + { ID id-UEReportingInformation CRITICALITY ignore TYPE UEReportingInformation PRESENCE optional }| + { ID id-UE-TEG-Info-Request CRITICALITY ignore TYPE UE-TEG-Info-Request PRESENCE optional }| + { ID id-UE-TEG-ReportingPeriodicity CRITICALITY reject TYPE UE-TEG-ReportingPeriodicity PRESENCE conditional }, +-- The IE shall be present if the UE TEG Info Request IE is set to "periodic" + +``` + +``` +... +} + +-- ***** +-- +-- POSITIONING INFORMATION RESPONSE +-- +-- ***** + +PositioningInformationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{PositioningInformationResponse-IEs}}, + ... +} + +PositioningInformationResponse-IEs NRPPA-PROTOCOL-IEs ::= { + { ID id-SRSConfiguration CRITICALITY ignore TYPE SRSConfiguration PRESENCE optional}| + { ID id-SFNInitialisationTime CRITICALITY ignore TYPE RelativeTime1900 PRESENCE optional}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}| + { ID id-UETxTEGAssociationList CRITICALITY ignore TYPE UETxTEGAssociationList PRESENCE optional}| + { ID id-NewNR CGI CRITICALITY ignore TYPE CGI-NR PRESENCE optional}, + ... +} +``` + +``` + +-- ***** +-- +-- POSITIONING INFORMATION FAILURE +-- +-- ***** + +``` + +``` + +PositioningInformationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{PositioningInformationFailure-IEs}}, + ... +} + +``` + +``` + +PositioningInformationFailure-IEs NRPPA-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}, + ... +} + +``` + +``` + +-- ***** +-- +-- POSITIONING INFORMATION UPDATE +-- +-- ***** + +``` + +PositioningInformationUpdate ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    {{PositioningInformationUpdate-IEs}}, + +    ... + +} + +PositioningInformationUpdate-IEs NRPPA-PROTOCOL-IES ::= { + +    { ID id-SRSConfiguration            CRITICALITY ignore    TYPE SRSConfiguration            PRESENCE optional}| + +    { ID id-SFNInitialisationTime        CRITICALITY ignore    TYPE RelativeTime1900            PRESENCE optional}| + +    { ID id-UETxTEGAssociationList    CRITICALITY ignore    TYPE UETxTEGAssociationList    PRESENCE optional}| + +    { ID id-SRSTransmissionStatus        CRITICALITY ignore    TYPE SRSTransmissionStatus    PRESENCE optional}, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- MEASUREMENT REQUEST + +-- + +-- \*\*\*\*\* + +MeasurementRequest ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    {{MeasurementRequest-IEs}}, + +    ... + +} + +``` + +MeasurementRequest-IEs NRPPA-PROTOCOL-IES ::= { + { ID id-LMF-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}| + { ID id-TRP-MeasurementRequestList CRITICALITY reject TYPE TRP-MeasurementRequestList PRESENCE mandatory}| + { ID id-ReportCharacteristics CRITICALITY reject TYPE ReportCharacteristics PRESENCE mandatory}| + { ID id-MeasurementPeriodicity CRITICALITY reject TYPE MeasurementPeriodicity PRESENCE conditional}| + + -- The IE shall be present if the Report Characteristics IE is set to "periodic" - + + { ID id-TRPMeasurementQuantities CRITICALITY reject TYPE TRPMeasurementQuantities PRESENCE mandatory}| + { ID id-SFNInitialisationTime CRITICALITY ignore TYPE RelativeTime1900 PRESENCE optional}| + { ID id-SRSConfiguration CRITICALITY ignore TYPE SRSConfiguration PRESENCE optional}| + { ID id-MeasurementBeamInfoRequest CRITICALITY ignore TYPE MeasurementBeamInfoRequest PRESENCE optional}| + { ID id-SystemFrameNumber CRITICALITY ignore TYPE SystemFrameNumber PRESENCE optional}| + { ID id-SlotNumber CRITICALITY ignore TYPE SlotNumber PRESENCE optional}| + { ID id-MeasurementPeriodicityExtended CRITICALITY reject TYPE MeasurementPeriodicityExtended PRESENCE conditional}| + + -- The IE shall be present the MeasurementPeriodicity IE is set to the value "extended" + + { ID id-ResponseTime CRITICALITY ignore TYPE ResponseTime PRESENCE optional}| + + { ID id-MeasurementCharacteristicsRequestIndicator CRITICALITY ignore TYPE MeasurementCharacteristicsRequestIndicator PRESENCE optional}| + + { ID id-MeasurementTimeOccasion CRITICALITY ignore TYPE MeasurementTimeOccasion PRESENCE optional}| + { ID id-MeasurementAmount CRITICALITY ignore TYPE MeasurementAmount PRESENCE optional}|, + ... +} + +``` + +-- \*\*\*\*\* + +``` + +-- +-- MEASUREMENT RESPONSE +-- +-- ***** + +``` + +``` + +MeasurementResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{MeasurementResponse-IEs}}, + ... +} + +``` + +``` + +MeasurementResponse-IEs NRPPA-PROTOCOL-IES ::= { + { ID id-LMF-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}| + { ID id-RAN-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}| + { ID id-TRP-MeasurementResponseList CRITICALITY reject TYPE TRP-MeasurementResponseList PRESENCE optional}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}, + ... +} + +``` + +``` + +-- ***** +-- +-- MEASUREMENT FAILURE +-- +-- ***** + +``` + +MeasurementFailure ::= SEQUENCE { + +    protocolIEs                    ProtocolIE-Container    {{MeasurementFailure-IEs}}, +    ... +} + +MeasurementFailure-IEs NRPPA-PROTOCOL-IES ::= { + +    { ID id-LMF-Measurement-ID    CRITICALITY reject    TYPE Measurement-ID            PRESENCE mandatory}| +    { ID id-Cause                    CRITICALITY ignore    TYPE Cause                    PRESENCE mandatory}| +    { ID id-CriticalityDiagnostics    CRITICALITY ignore    TYPE CriticalityDiagnostics    PRESENCE optional}, +    ... +} + +-- \*\*\*\*\* +-- +-- MEASUREMENT REPORT +-- +-- \*\*\*\*\* + +MeasurementReport ::= SEQUENCE { + +    protocolIEs            ProtocolIE-Container    {{MeasurementReport-IEs}}, +    ... +} + +``` +MeasurementReport-IEs NRPPA-PROTOCOL-IEs ::= { + { ID id-LMF-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}| + { ID id-RAN-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}| + { ID id-TRP-MeasurementReportList CRITICALITY reject TYPE TRP-MeasurementResponseList PRESENCE mandatory}, + ... +} +``` + +``` +-- ***** +-- +-- MEASUREMENT UPDATE +-- +-- ***** +``` + +``` +MeasurementUpdate ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{MeasurementUpdate-IEs}}, + ... +} +``` + +``` +MeasurementUpdate-IEs NRPPA-PROTOCOL-IEs ::= { + { ID id-LMF-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}| + { ID id-RAN-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}| +``` + +``` +{ ID id-SRSConfiguration CRITICALITY ignore TYPE SRSConfiguration PRESENCE optional}| +{ ID id-TRP-MeasurementUpdateList CRITICALITY reject TYPE TRP-MeasurementUpdateList PRESENCE optional}| +{ ID id-MeasurementCharacteristicsRequestIndicator CRITICALITY ignore TYPE MeasurementCharacteristicsRequestIndicator PRESENCE optional}| +{ ID id-MeasurementTimeOccasion CRITICALITY ignore TYPE MeasurementTimeOccasion PRESENCE optional}, +... +} +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- MEASUREMENT ABORT +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +MeasurementAbort ::= SEQUENCE { +``` + +``` + protocolIEs ProtocolIE-Container {{MeasurementAbort-IEs}}, +``` + +``` + ... +``` + +``` +} +``` + +``` +MeasurementAbort-IEs NRPPA-PROTOCOL-IES ::= { +``` + +``` +{ ID id-LMF-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}| +``` + +``` +{ ID id-RAN-Measurement-ID CRITICALITY reject TYPE Measurement-ID PRESENCE mandatory}, +``` + +``` + ... +``` + +} + +-- \*\*\*\*\* + +-- + +-- MEASUREMENT FAILURE INDICATION + +-- + +-- \*\*\*\*\* + +MeasurementFailureIndication ::= SEQUENCE { + +    protocolIEs                    ProtocolIE-Container    {{MeasurementFailureIndication-IEs}}, + +    ... + +} + +MeasurementFailureIndication-IEs NRPPA-PROTOCOL-IES ::= { + +    { ID id-LMF-Measurement-ID    CRITICALITY reject    TYPE Measurement-ID            PRESENCE mandatory}| + +    { ID id-RAN-Measurement-ID    CRITICALITY reject    TYPE Measurement-ID            PRESENCE mandatory}| + +    { ID id-Cause                CRITICALITY ignore    TYPE Cause                    PRESENCE mandatory}, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- TRP INFORMATION REQUEST + +``` + +-- +-- ***** + +TRPInformationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{TRPInformationRequest-IEs}}, + ... +} + +TRPInformationRequest-IEs NRPPA-PROTOCOL-IES ::= { + { ID id-TRPList CRITICALITY ignore TYPE TRPList PRESENCE optional}| + { ID id-TRPInformationTypeListTRPReq CRITICALITY reject TYPE TRPInformationTypeListTRPReq PRESENCE mandatory}, + ... +} + +-- ***** +-- +-- TRP INFORMATION RESPONSE +-- +-- ***** + +TRPInformationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{TRPInformationResponse-IEs}}, + ... +} + +``` + +``` + +} + +TRPInformationResponse-IEs NRPPA-PROTOCOL-IES ::= { + { ID id-TRPInformationListTRPResp CRITICALITY ignore TYPE TRPInformationListTRPResp PRESENCE mandatory}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}, + ... +} + +``` + +``` + +-- ***** +-- +-- TRP INFORMATION FAILURE +-- +-- ***** + +``` + +``` + +TRPInformationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{TRPInformationFailure-IEs}}, + ... +} + +``` + +``` + +TRPInformationFailure-IEs NRPPA-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}, + ... +} + +``` + +} + +-- \*\*\*\*\* + +-- + +-- POSITIONING ACTIVATION REQUEST + +-- + +-- \*\*\*\*\* + +PositioningActivationRequest ::= SEQUENCE { + +protocolIEs            ProtocolIE-Container      { { PositioningActivationRequestIEs } }, + +... + +} + +PositioningActivationRequestIEs NRPPA-PROTOCOL-IES ::= { + +{ ID id-SRSType                    CRITICALITY reject    TYPE SRSType                    PRESENCE mandatory } | + +{ ID id-ActivationTime            CRITICALITY ignore    TYPE RelativeTime1900                    PRESENCE optional }, + +... + +} + +SRSType ::= CHOICE { + +semipersistentSRS                    SemipersistentSRS, + +``` + aperiodicSRS AperiodicSRS, + choice-Extension ProtocolIE-Single-Container { { SRSType-ExtIEs} } +} + +SRSType-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +SemipersistentSRS ::= SEQUENCE { + sRSResourceSetID SRSResourceSetID, + iE-Extensions ProtocolExtensionContainer { {SemipersistentSRS-ExtIEs} } OPTIONAL, + ... +} + +SemipersistentSRS-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + { ID id-SRSSpatialRelation CRITICALITY ignore EXTENSION SpatialRelationInfo PRESENCE optional}| + { ID id-SRSSpatialRelationPerSRSResource CRITICALITY ignore EXTENSION SpatialRelationPerSRSResource PRESENCE optional}, + ... +} + +AperiodicSRS ::= SEQUENCE { + aperiodic ENUMERATED{true,...}, + sRSResourceTrigger SRSResourceTrigger OPTIONAL, +``` + +``` + + iE-Extensions ProtocolExtensionContainer { {AperiodicSRS-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +AperiodicSRS-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +-- ***** +-- +-- POSITIONING ACTIVATION RESPONSE +-- +-- ***** + +``` + +``` + +PositioningActivationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PositioningActivationResponseIEs} }, + ... +} + +``` + +``` + +PositioningActivationResponseIEs NRPPA-PROTOCOL-IEs ::= { + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + +``` + +``` +{ ID id-SystemFrameNumber CRITICALITY ignore TYPE SystemFrameNumber PRESENCE optional }| +{ ID id-SlotNumber CRITICALITY ignore TYPE SlotNumber PRESENCE optional }, +... +} +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- POSITIONING ACTIVATION FAILURE +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +PositioningActivationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PositioningActivationFailureIEs } }, + ... +} +``` + +``` +PositioningActivationFailureIEs NRPPA-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} +``` + +``` +-- ***** +-- +-- POSITIONING DEACTIVATION +-- +-- ***** +``` + +``` +PositioningDeactivation ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PositioningDeactivationIEs } }, + ... +} +``` + +``` +PositioningDeactivationIEs NRPPA-PROTOCOL-IES ::= { + { ID id-AbortTransmission CRITICALITY ignore TYPE AbortTransmission PRESENCE mandatory } , + ... +} +``` + +``` +-- ***** +-- +-- PRS CONFIGURATION REQUEST +-- +-- ***** +``` + +``` + +PRSConfigurationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{PRSConfigurationRequest-IEs}}, + ... +} + +PRSConfigurationRequest-IEs NRPPA-PROTOCOL-IES ::= { + { ID id-PRSConfigRequestType CRITICALITY reject TYPE PRSConfigRequestType PRESENCE mandatory}| + { ID id-PRSTRPList CRITICALITY ignore TYPE PRSTRPList PRESENCE mandatory}, + ... +} + +-- ***** +-- +-- PRS CONFIGURATION RESPONSE +-- +-- ***** + +PRSConfigurationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ PRSConfigurationResponse-IEs}}, + ... +} + +``` + +``` +PRSConfigurationResponse-IEs NRPPA-PROTOCOL-IEs ::= { + { ID id-PRSTransmissionTRPList CRITICALITY ignore TYPE PRSTransmissionTRPList + PRESENCE optional}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional}, + ... +} + +-- ***** +-- +-- PRS CONFIGURATION FAILURE +-- +-- ***** + +PRSConfigurationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ PRSConfigurationFailure-IEs}}, + ... +} + +PRSConfigurationFailure-IEs NRPPA-PROTOCOL-IEs ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause + PRESENCE mandatory}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional}, + ... +} +``` + +``` +-- ***** +-- +-- MEASUREMENT PRECONFIGURATION REQUIRED +-- +-- ***** +``` + +``` +MeasurementPreconfigurationRequired ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ MeasurementPreconfigurationRequired-IEs}}, + ... +} +``` + +``` +MeasurementPreconfigurationRequired-IEs NRPPA-PROTOCOL-IEs ::= { + { ID id-TRP-PRS-Information-List CRITICALITY ignore TYPE TRP-PRS-Information-List PRESENCE mandatory}, + ... +} +``` + +``` +-- ***** +-- +-- MEASUREMENT PRECONFIGURATION CONFIRM +-- +-- ***** +``` + +``` + +MeasurementPreconfigurationConfirm ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ MeasurementPreconfigurationConfirm-IEs}}, + ... +} + +``` + +``` + +MeasurementPreconfigurationConfirm-IEs NRPPA-PROTOCOL-IES ::= { + { ID id-PreconfigurationResult CRITICALITY ignore TYPE PreconfigurationResult PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- MEASUREMENT PRECONFIGURATION REFUSE +-- +-- ***** + +``` + +``` + +MeasurementPreconfigurationRefuse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ MeasurementPreconfigurationRefuse-IEs}}, + ... +} + +``` + +``` + +MeasurementPreconfigurationRefuse-IEs NRPPA-PROTOCOL-IES ::= { + +``` + +``` +{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}| +{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}, +... +} + +-- ***** +-- +-- MEASUREMENT ACTIVATION +-- +-- ***** + +MeasurementActivation ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { MeasurementActivation-IEs } }, + ... +} + +MeasurementActivation-IEs NRPPA-PROTOCOL-IES ::= { + { ID id-RequestType CRITICALITY reject TYPE RequestType PRESENCE mandatory}| + { ID id-PRS-Measurements-Info-List CRITICALITY ignore TYPE PRS-Measurements-Info-List PRESENCE optional}, + ... +} +``` + +END + +-- ASN1STOP + +### 9.3.5 Information Element definitions + +-- ASN1START + +-- \*\*\*\*\* + +-- + +-- Information Element Definitions + +-- + +-- \*\*\*\*\* + +NRPPA-IEs { + +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + +ngran-access (22) modules (3) nrppa (4) version1 (1) nrppa-IEs (2) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + +id-MeasurementQuantities-Item, + +id-CGI-NR, + +id-SFNInitialisationTime-NR, +id-GeographicalCoordinates, +id-ResultSS-RSRP, +id-ResultSS-RSRQ, +id-ResultCSI-RSRP, +id-ResultCSI-RSRQ, +id-AngleOfArrivalNR, +id-ResultNR, +id-ResultEUTRA, +maxCellinRANnode, +maxCellReport, +maxNrOfErrors, +maxNoMeas, +maxnoOTDOAtypes, +maxServCell, +id-OtherRATMeasurementQuantities-Item, +id-WLANMeasurementQuantities-Item, +maxGERANMeas, +maxUTRANMeas, +maxWLANchannels, +maxnoFreqHoppingBandsMinusOne, +id-TDD-Config-EUTRA-Item, +maxNrOfPosSImessage, + +maxnoAssistInfoFailureListItems, +maxNrOfSegments, +maxNrOfPosSIBs, +maxnoPosMeas, +maxnoTRPs, +maxnoTRPInfoTypes, +maxNoOfMeasTRPs, +maxNoPath, +maxnoofAngleInfo, +maxnolcs-gcs-translation, +maxnoBcastCell, +maxnoSRSTriggerStates, +maxnoSpatialRelations, +maxNRMeas, +maxEUTRA Meas, +maxIndexesReport, +maxCellReportNR, +maxnoSRS-Carriers, +maxnoSCSs, +maxnoSRS-Resources, +maxnoSRS-PosResources, +maxnoSRS-ResourceSets, +maxnoSRS-ResourcePerSet, + +maxnoSRS-PosResourceSets, +maxnoSRS-PosResourcePerSet, +maxPRS-ResourceSets, +maxPRS-ResourcesPerSet, +maxNoSSBs, +maxnoofPRSresourceSet, +maxnoofPRSresource, +maxnoofULAoAs, +maxNoPathExtended, +maxnoARPs, +maxnoTRPTEGs, +maxnoUETEGs, +maxFreqLayers, +maxnoPRSTRPs, +maxNumResourcesPerAngle, +maxnoAzimuthAngles, +maxnoElevationAngles, +id-Cell-ID, +id-TRPInformationTypeItem, +id-SrsFrequency, +id-TRPType, +id-SRSPatialRelationPerSRSResource, +id-PRS-Resource-ID, + +id-OnDemandPRS, +id-AoA-SearchWindow, +id-ZoA, +id-MultipleULAoA, +id-UL-SRS-RSRPP, +id-SRSResourcetype, +id-ExtendedAdditionalPathList, +id-ARPLocationInfo, +id-ARP-ID, +id-LoS-NLoSInformation, +id-NumberOfTRPRxTEG, +id-NumberOfTRPRxTxTEG, +id-TRPTxTEGAssociation, +id-TRPTEGInformation, +id-TRP-Rx-TEGInformation, +id-TRPBeamAntennaInformation, +id-NR-TADV, +id-pathPower, +id-SRSPortIndex, +id-UETxTimingErrorMargin, +id-nrofSymbolsExtended, +id-repetitionFactorExtended, +id-StartRBHopping, + +id-StartRBIndex, +id-transmissionCombn8, +id-ExtendedResourceSymbolOffset, +id-Mobile-TRP-LocationInformation, +id-Mobile-IAB-MT-UE-ID, +id-MobileAccessPointLocation, +id-CommonTAParameters + +FROM NRPPA-Constants + +Criticality, +NRPPATransactionID, +ProcedureCode, +ProtocolIE-ID, +TriggeringMessage + +FROM NRPPA-CommonDataTypes + +ProtocolExtensionContainer{}, +ProtocolIE-Single-Container{}, + +``` +NRPPA-PROTOCOL-EXTENSION, +NRPPA-PROTOCOL-IES + +FROM NRPPA-Containers; + +-- A + +AbortTransmission ::= CHOICE { + deactivateSRSResourceSetID SRSResourceSetID, + releaseALL NULL, + choice-extension ProtocolIE-Single-Container { { AbortTransmission-ExtIEs } } +} + +AbortTransmission-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +ActiveULBWP ::= SEQUENCE { + locationAndBandwidth INTEGER (0..37949,...), + subcarrierSpacing ENUMERATED {kHz15, kHz30, kHz60, kHz120,..., kHz480, kHz960}, + cyclicPrefix ENUMERATED {normal, extended}, + txDirectCurrentLocation INTEGER (0..3301,...), +} +``` + +``` + shift7dot5kHz ENUMERATED {true, ...} OPTIONAL, + sRSConfig SRSConfig, + iE-Extensions ProtocolExtensionContainer { { ActiveULBWP-ExtIEs} } OPTIONAL, + ... + } + +ActiveULBWP-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +AdditionalPathList ::= SEQUENCE (SIZE (1.. maxNoPath)) OF AdditionalPathListItem + +AdditionalPathListItem ::= SEQUENCE { + relativeTimeOfPath RelativePathDelay, + pathQuality TrpMeasurementQuality OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { AdditionalPathListItem-ExtIEs} } OPTIONAL, + ... +} + +AdditionalPathListItem-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + { ID id-MultipleULAoA CRITICALITY ignore EXTENSION MultipleULAoA PRESENCE optional}| +``` + +``` +{ ID id-pathPower CRITICALITY ignore EXTENSION UL-SRS-RSRPP PRESENCE optional}, +... +} + +ExtendedAdditionalPathList ::= SEQUENCE (SIZE (1.. maxNoPathExtended)) OF ExtendedAdditionalPathList-Item + +ExtendedAdditionalPathList-Item ::= SEQUENCE { + relativeTimeOfPath RelativePathDelay, + pathQuality TrpMeasurementQuality OPTIONAL, + multipleULAoA MultipleULAoA OPTIONAL, + pathPower UL-SRS-RSRPP OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { ExtendedAdditionalPathList-Item-ExtIEs} } OPTIONAL, + ... +} + +ExtendedAdditionalPathList-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +AoA-AssistanceInfo ::= SEQUENCE { + angleMeasurement AngleMeasurementType, + LCS-to-GCS-Translation LCS-to-GCS-Translation OPTIONAL, +``` + +``` +iE-Extensions ProtocolExtensionContainer { { AoA-AssistanceInfo-ExtIEs } } OPTIONAL, +... +} + +AoA-AssistanceInfo-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +... +} + +AperiodicSRSResourceTriggerList ::= SEQUENCE (SIZE(1..maxnoSRSTriggerStates)) OF AperiodicSRSResourceTrigger + +AperiodicSRSResourceTrigger ::= INTEGER (1..3) + +AngleMeasurementType ::= CHOICE { + expected-ULAoA Expected-UL-AoA, + expected-ZoA Expected-ZoA-only, + choice-extension ProtocolIE-Single-Container { { AngleMeasurementType-ExtIEs } } +} + +AngleMeasurementType-ExtIEs NRPPA-PROTOCOL-IES ::= { +... +} + +Expected-UL-AoA ::= SEQUENCE { +``` + +``` + expected-Azimuth-AoA Expected-Azimuth-AoA, + expected-Zenith-AoA Expected-Zenith-AoA OPTIONAL, + iE-extensions ProtocolExtensionContainer { { Expected-UL-AoA-ExtIEs } } OPTIONAL, + ... +} + +Expected-UL-AoA-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +Expected-ZoA-only ::= SEQUENCE { + expected-ZoA-only Expected-Zenith-AoA, + iE-extensions ProtocolExtensionContainer { { Expected-ZoA-only-ExtIEs } } OPTIONAL, + ... +} + +Expected-ZoA-only-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +Expected-Azimuth-AoA ::= SEQUENCE { + expected-Azimuth-AoA-value Expected-Value-AoA, + expected-Azimuth-AoA-uncertainty Uncertainty-range-AoA, +``` + +``` +iE-extensions ProtocolExtensionContainer { { Expected-Azimuth-AoA-ExtIEs } } OPTIONAL, +... +} + +Expected-Azimuth-AoA-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +... +} + +Expected-Zenith-AoA ::= SEQUENCE { + expected-Zenith-AoA-value Expected-Value-ZoA, + expected-Zenith-AoA-uncertainty Uncertainty-range-ZoA, + iE-extensions ProtocolExtensionContainer { { Expected-Zenith-AoA-ExtIEs } } OPTIONAL, + ... +} + +Expected-Zenith-AoA-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +... +} + +ARP-ID ::= INTEGER (1..16, ...) + +ARPLocationInformation ::= SEQUENCE (SIZE (1..maxnoARPs)) OF ARPLocationInformation-Item +``` + +``` +ARPLocationInformation-Item ::= SEQUENCE { + aRP-ID aRP-ID, + aRPLocationType aRPLocationType, + iE-Extensions ProtocolExtensionContainer { { aRPLocationInformation-ExtIEs } } OPTIONAL, + ... +} + +ARPLocationInformation-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +aRPLocationType ::= CHOICE { + aRPPositionRelativeGeodetic RelativeGeodeticLocation, + aRPPositionRelativeCartesian RelativeCartesianLocation, + choice-extension ProtocolIE-Single-Container { { aRPLocationType-ExtIEs } } +} + +aRPLocationType-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +Assistance-Information ::= SEQUENCE { + systemInformation SystemInformation, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { Assistance-Information-ExtIEs} } OPTIONAL, + ... +} + +Assistance-Information-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +AssistanceInformationFailureList ::= SEQUENCE (SIZE (1..maxnoAssistInfoFailureListItems)) OF SEQUENCE { + posSIB-Type PosSIB-Type, + outcome Outcome, + iE-Extensions ProtocolExtensionContainer { {AssistanceInformationFailureList-ExtIEs} } OPTIONAL, + ... +} + +AssistanceInformationFailureList-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +AssistanceInformationMetaData ::= SEQUENCE { + encrypted ENUMERATED {true, ...} OPTIONAL, + gNSSID ENUMERATED {gps, sbas, qzss, galileo, glonass, bds, navic, ...} OPTIONAL, + sBASID ENUMERATED {waas, egnos, msas, gagan, ...} OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { AssistanceInformationMetaData-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +AssistanceInformationMetaData-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +-- B + +``` +BandwidthSRS ::= CHOICE { + fR1 ENUMERATED {mHz5, mHz10, mHz20, mHz40, mHz50, mHz80, mHz100, ...}, + fR2 ENUMERATED {mHz50, mHz100, mHz200, mHz400, ...}, + choice-extension ProtocolIE-Single-Container { { BandwidthSRS-ExtIEs } } +} +``` + +``` +BandwidthSRS-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} +``` + +``` +BCCH ::= INTEGER (0..1023, ...) +``` + +``` +Broadcast ::= ENUMERATED { + start, + stop, + ... +} +``` + +``` +BroadcastPeriodicity ::= ENUMERATED { + ms80, + ms160, + ms320, + ms640, + ms1280, + ms2560, + ms5120, + ... +} +``` + +``` +PositioningBroadcastCells ::= SEQUENCE (SIZE (1..maxnoBcastCell)) OF NG-RAN-CGI +``` + +``` +BSSID ::= OCTET STRING (SIZE(6)) +``` + +``` +-- C +``` + +``` +CarrierFreq ::= SEQUENCE { + pointA INTEGER (0..3279165), + offsetToCarrier INTEGER (0..2199, ...), + iE-Extensions ProtocolExtensionContainer { {CarrierFreq-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +CarrierFreq-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +Cause ::= CHOICE { + radioNetwork CauseRadioNetwork, + protocol CauseProtocol, + misc CauseMisc, + choice-Extension ProtocolIE-Single-Container {{ Cause-ExtensionIE }} +} +``` + +``` +Cause-ExtensionIE NRPPA-PROTOCOL-IES ::= { + ... +} +``` + +``` +CauseMisc ::= ENUMERATED { + unspecified, + ... +} + +CauseProtocol ::= ENUMERATED { + transfer-syntax-error, + abstract-syntax-error-reject, + abstract-syntax-error-ignore-and-notify, + message-not-compatible-with-receiver-state, + semantic-error, + unspecified, + abstract-syntax-error-falsely-constructed-message, + ... +} + +CauseRadioNetwork ::= ENUMERATED { + unspecified, + requested-item-not-supported, + requested-item-temporarily-not-available, + ..., + serving-NG-RAN-node-changed, + requested-item-not-supported-on-time +``` + +} + +Cell-Portion-ID ::= INTEGER (0..4095,...) + +CGI-EUTRA ::= SEQUENCE { + +    pLMN-Identity              PLMN-Identity, + +    eUTRAcellIdentifier        EUTRAcellIdentifier, + +    iE-Extensions              ProtocolExtensionContainer { {CGI-EUTRA-ExtIEs} } OPTIONAL, + +    ... + +} + +CGI-EUTRA-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + +    ... + +} + +CGI-NR ::= SEQUENCE { + +    pLMN-Identity              PLMN-Identity, + +    nRcellIdentifier          NRcellIdentifier, + +    iE-Extensions              ProtocolExtensionContainer { {CGI-NR-ExtIEs} } OPTIONAL, + +    ... + +} + +``` +CGI-NR-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +CPLength-EUTRA ::= ENUMERATED { +``` + +``` + normal, +``` + +``` + extended, +``` + +``` + ... +``` + +``` +} +``` + +``` +CriticalityDiagnostics ::= SEQUENCE { +``` + +``` + procedureCode ProcedureCode OPTIONAL, +``` + +``` + triggeringMessage TriggeringMessage OPTIONAL, +``` + +``` + procedureCriticality Criticality OPTIONAL, +``` + +``` + nrppatransactionID NRPPATransactionID OPTIONAL, +``` + +``` + iEsCriticalityDiagnostics CriticalityDiagnostics-IE-List OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +CriticalityDiagnostics-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE (1..maxNrOfErrors)) OF +``` + +``` + SEQUENCE { +``` + +``` + iECriticality Criticality, +``` + +``` + iE-ID ProtocolIE-ID, +``` + +``` + typeOfError TypeOfError, +``` + +``` + iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-IE-List-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` + } +``` + +``` +CriticalityDiagnostics-IE-List-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +CommonTAParameters ::= SEQUENCE { +``` + +``` + epochTime OCTET STRING, +``` + +``` + taInfo OCTET STRING, +``` + +``` + iE-Extensions ProtocolExtensionContainer {{ CommonTAParameters-ExtIEs}} OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +CommonTAParameters-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +-- D +``` + +``` +DL-Bandwidth-EUTRA ::= ENUMERATED { +``` + +``` + bw6, +``` + +``` + bw15, +``` + +``` + bw25, +``` + +``` + bw50, +``` + +``` + bw75, +``` + +``` + bw100, +``` + +``` + ... +``` + +``` +} +``` + +``` +DL-PRS ::= SEQUENCE { +``` + +``` + prsid INTEGER (0..255), +``` + +``` + dl-PRSResourceSetID PRS-Resource-Set-ID, +``` + +``` + dl-PRSResourceID PRS-Resource-ID OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { {DL-PRS-ExtIEs} } OPTIONAL, +``` + +``` +... +} + +DL-PRS-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +DL-PRSMutingPattern ::= CHOICE { + two BIT STRING (SIZE(2)), + four BIT STRING (SIZE(4)), + six BIT STRING (SIZE(6)), + eight BIT STRING (SIZE(8)), + sixteen BIT STRING (SIZE(16)), + thirty-two BIT STRING (SIZE(32)), + choice-extension ProtocolIE-Single-Container { { DL-PRSMutingPattern-ExtIEs } } +} + +DL-PRSMutingPattern-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +DLPRSResourceCoordinates ::= SEQUENCE { + listOfDL-PRSResourceSetARP SEQUENCE (SIZE(1.. maxPRS-ResourceSets)) OF DLPRSResourceSetARP, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { DLPRSResourceCoordinates-ExtIEs } } OPTIONAL, + ... +} + +DLPRSResourceCoordinates-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +DLPRSResourceSetARP ::= SEQUENCE { + dl-PRSResourceSetID PRS-Resource-Set-ID, + dL-PRSResourceSetARPLocation DL-PRSResourceSetARPLocation, + listOfDL-PRSResourceARP SEQUENCE (SIZE(1.. maxPRS-ResourcesPerSet)) OF DLPRSResourceARP, + iE-Extensions ProtocolExtensionContainer { { DLPRSResourceSetARP-ExtIEs } } OPTIONAL, + ... +} + +DLPRSResourceSetARP-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +DL-PRSResourceSetARPLocation ::= CHOICE { + relativeGeodeticLocation RelativeGeodeticLocation, +``` + +``` + relativeCartesianLocation RelativeCartesianLocation, + choice-Extension ProtocolIE-Single-Container { { DL-PRSResourceSetARPLocation-ExtIEs } } +} + +DL-PRSResourceSetARPLocation-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +DLPRSResourceARP ::= SEQUENCE { + dl-PRSResourceID PRS-Resource-ID, + dL-PRSResourceARPLocation DL-PRSResourceARPLocation, + iE-Extensions ProtocolExtensionContainer { { DLPRSResourceARP-ExtIEs } } OPTIONAL, + ... +} + +DLPRSResourceARP-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +DL-PRSResourceARPLocation ::= CHOICE { + relativeGeodeticLocation RelativeGeodeticLocation, + relativeCartesianLocation RelativeCartesianLocation, +``` + +``` + choice-Extension ProtocolIE-Single-Container { { DL-PRSResourceARPLocation-ExtIEs } } +} + +DL-PRSResourceARPLocation-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +-- E + +E-CID-MeasurementResult ::= SEQUENCE { + servingCell-ID NG-RAN-CGI, + servingCellTAC TAC, + nG-RANAccessPointPosition NG-RANAccessPointPosition OPTIONAL, + measuredResults MeasuredResults OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { E-CID-MeasurementResult-ExtIEs } } OPTIONAL, + ... +} + +E-CID-MeasurementResult-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + { ID id-GeographicalCoordinates CRITICALITY ignore EXTENSION GeographicalCoordinates PRESENCE optional } | + { ID id-MobileAccessPointLocation CRITICALITY ignore EXTENSION Mobile-TRP-LocationInformation PRESENCE optional }, + ... +} +``` + +EUTRACellIdentifier ::= BIT STRING (SIZE (28)) + +EARFCN ::= INTEGER (0..262143, ...) + +Expected-Value-AoA ::= INTEGER (0..3599) + +Expected-Value-ZoA ::= INTEGER (0..1799) + +-- F + +-- G + +GeographicalCoordinates ::= SEQUENCE { +    tRPPositionDefinitionType    TRPPositionDefinitionType, +    dLPRSResourceCoordinates    DLPRSResourceCoordinates    OPTIONAL, +    iE-Extensions                ProtocolExtensionContainer { { GeographicalCoordinates-ExtIEs } } OPTIONAL, +    ... +} + +GeographicalCoordinates-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +    { ID id-ARPLocationInfo    CRITICALITY ignore EXTENSION ARPLocationInformation    PRESENCE optional}, + +``` + ... +} + +GNB-RxTxTimeDiff ::= SEQUENCE { + + rxTxTimeDiff GNBRxTxTimeDiffMeas, + additionalPathList AdditionalPathList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GNB-RxTxTimeDiff-ExtIEs} } OPTIONAL, + ... +} + +GNB-RxTxTimeDiff-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + + { ID id-ExtendedAdditionalPathList CRITICALITY ignore EXTENSION ExtendedAdditionalPathList PRESENCE optional}| + { ID id-TRPTEGInformation CRITICALITY ignore EXTENSION TRPTEGInformation PRESENCE optional }, + + ... +} + +GNBRxTxTimeDiffMeas ::= CHOICE { + + k0 INTEGER (0.. 1970049), + k1 INTEGER (0.. 985025), +} +``` + +``` +k2 INTEGER (0.. 492513), +k3 INTEGER (0.. 246257), +k4 INTEGER (0.. 123129), +k5 INTEGER (0.. 61565), +choice-extension ProtocolIE-Single-Container { { GNBRxTxTimeDiffMeas-ExtIEs } } +} + +GNBRxTxTimeDiffMeas-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +-- H + +HESSID ::= OCTET STRING (SIZE(6)) + +-- I + +-- J + +-- K + +-- L +``` + +``` +LCS-to-GCS-Translation ::= SEQUENCE { + alpha INTEGER (0..3599), + beta INTEGER (0..3599), + gamma INTEGER (0..3599), + iE-Extensions ProtocolExtensionContainer { { LCS-to-GCS-Translation-ExtIEs} } OPTIONAL, + ... +} + +LCS-to-GCS-Translation-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +LCS-to-GCS-TranslationItem ::= SEQUENCE { + alpha INTEGER (0..359), + alphaFine INTEGER (0..9) OPTIONAL, + beta INTEGER (0..359), + betaFine INTEGER (0..9) OPTIONAL, + gamma INTEGER (0..359), + gammaFine INTEGER (0..9) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { LCS-to-GCS-TranslationItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +LCS-to-GCS-TranslationItem-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +LocationUncertainty ::= SEQUENCE { +``` + +``` + horizontalUncertainty INTEGER (0..255), +``` + +``` + horizontalConfidence INTEGER (0..100), +``` + +``` + verticalUncertainty INTEGER (0..255), +``` + +``` + verticalConfidence INTEGER (0..100), +``` + +``` + iE-Extensions ProtocolExtensionContainer { { LocationUncertainty-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +LocationUncertainty-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +LoS-NLoSIndicatorHard ::= ENUMERATED {nlos, los} +``` + +``` +LoS-NLoSIndicatorSoft ::= INTEGER (0..10) +``` + +``` +LoS-NLoSInformation ::= CHOICE { +``` + +``` + loS-NLoSIndicatorSoft LoS-NLoSIndicatorSoft, +``` + +``` + loS-NLoSIndicatorHard LoS-NLoSIndicatorHard, + choice-Extension ProtocolIE-Single-Container {{ LoS-NLoSInformation-ExtIEs}} + +} + +LoS-NLoSInformation-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +-- M + +Measurement-ID ::= INTEGER (1.. 65536, ...) + +MeasurementAmount ::= ENUMERATED {ma0, ma1, ma2, ma4, ma8, ma16, ma32, ma64} + +MeasurementBeamInfoRequest ::= ENUMERATED {true, ...} + +MeasurementBeamInfo ::= SEQUENCE { + pRS-Resource-ID PRS-Resource-ID OPTIONAL, + pRS-Resource-Set-ID PRS-Resource-Set-ID OPTIONAL, + sSB-Index SSB-Index OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MeasurementBeamInfo-ExtIEs} } OPTIONAL, +``` + +``` + ... +} + +MeasurementBeamInfo-ExtIEs NRPFA-PROTOCOL-EXTENSION ::= { + ... +} + +MeasurementPeriodicity ::= ENUMERATED { + ms120, + ms240, + ms480, + ms640, + ms1024, + ms2048, + ms5120, + ms10240, + min1, + min6, + min12, + min30, + min60, + ... +} +``` + +``` + ms20480, + ms40960, + extended +} +``` + +``` +MeasurementPeriodicityExtended ::= ENUMERATED { + ms160, + ms320, + ms1280, + ms2560, + ms61440, + ms81920, + ms368640, + ms737280, + ms1843200, + ... +} +``` + +``` +MeasurementPeriodicityNR-AoA ::= ENUMERATED { + ms160, + ms320, + ms640, +``` + +``` + ms1280, + ms2560, + ms5120, + ms10240, + ms20480, + ms40960, + ms61440, + ms81920, + ms368640, + ms737280, + ms1843200, + ... + +} + +MeasurementQuantities ::= SEQUENCE (SIZE (1.. maxNoMeas)) OF ProtocolIE-Single-Container { {MeasurementQuantities-ItemIEs} } + +MeasurementQuantities-ItemIEs NRPPA-PROTOCOL-IES ::= { + { ID id-MeasurementQuantities-Item CRITICALITY reject TYPE MeasurementQuantities-Item PRESENCE mandatory} +} + +MeasurementQuantities-Item ::= SEQUENCE { + measurementQuantitiesValue + MeasurementQuantitiesValue, +``` + +``` +iE-Extensions ProtocolExtensionContainer { { MeasurementQuantitiesValue-ExtIEs} } OPTIONAL, +... +} + +MeasurementQuantitiesValue-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +... +} + +MeasurementQuantitiesValue ::= ENUMERATED { + cell-ID, + angleOfArrival, + timingAdvanceType1, + timingAdvanceType2, + rSRP, + rSRQ, + ... , + sS-RSRP, + sS-RSRQ, + cSI-RSRP, + cSI-RSRQ, + angleOfArrivalNR, + timingAdvanceNR +} +``` + +MeasurementTimeOccasion ::= ENUMERATED {o1, o4, ...} + +MeasurementCharacteristicsRequestIndicator ::= BIT STRING (SIZE (16)) + +MeasuredResults ::= SEQUENCE (SIZE (1.. maxNoMeas)) OF MeasuredResultsValue + +MeasuredResultsValue ::= CHOICE { + +    valueAngleOfArrival-EUTRA                  INTEGER (0..719), + +    valueTimingAdvanceType1-EUTRA              INTEGER (0..7690), + +    valueTimingAdvanceType2-EUTRA              INTEGER (0..7690), + +    resultRSRP-EUTRA                           ResultRSRP-EUTRA, + +    resultRSRQ-EUTRA                           ResultRSRQ-EUTRA, + +    choice-Extension                           ProtocolIE-Single-Container {{ MeasuredResultsValue-ExtensionIE }} + +} + +MeasuredResultsValue-ExtensionIE NRPPA-PROTOCOL-IES ::= { + +{ ID id-ResultSS-RSRP          CRITICALITY ignore  TYPE ResultSS-RSRP          PRESENCE mandatory }| + +{ ID id-ResultSS-RSRQ          CRITICALITY ignore  TYPE ResultSS-RSRQ          PRESENCE mandatory }| + +{ ID id-ResultCSI-RSRP         CRITICALITY ignore  TYPE ResultCSI-RSRP         PRESENCE mandatory }| + +{ ID id-ResultCSI-RSRQ         CRITICALITY ignore  TYPE ResultCSI-RSRQ         PRESENCE mandatory }| + +{ ID id-AngleOfArrivalNR       CRITICALITY ignore  TYPE UL-AoA                 PRESENCE mandatory }| + +{ ID id-NR-TADV                CRITICALITY ignore  TYPE NR-TADV                PRESENCE mandatory }, + +``` + ... +} + +Mobile-TRP-LocationInformation ::= SEQUENCE { + location-Information OCTET STRING OPTIONAL, + velocity-Information OCTET STRING OPTIONAL, + location-time-stamp TimeStamp OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Mobile-TRP-LocationInformation-ExtIEs} } OPTIONAL, + ... +} + +Mobile-TRP-LocationInformation-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +Mobile-IAB-MT-UE-ID ::= OCTET STRING + +MultipleULAoA ::= SEQUENCE { + multipleULAoA MultipleULAoA-List, + iE-Extensions ProtocolExtensionContainer { { MultipleULAoA-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +MultipleULAoA-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +MultipleULAoA-List ::= SEQUENCE (SIZE(1.. maxnoofULAoAs)) OF MultipleULAoA-Item +``` + +``` +MultipleULAoA-Item ::= CHOICE { +``` + +``` + uL-AoA UL-AoA, +``` + +``` + ul-ZoA ZoA, +``` + +``` + choice-extension ProtocolIE-Single-Container { { MultipleULAoA-Item-ExtIEs } } +``` + +``` +} +``` + +``` +MultipleULAoA-Item-ExtIEs NRPPA-PROTOCOL-IES ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +-- N +``` + +``` +NarrowBandIndex ::= INTEGER (0..15,...) +``` + +``` +NG-RANAccessPointPosition ::= SEQUENCE { +``` + +``` + latitudeSign ENUMERATED {north, south}, +``` + +``` + latitude INTEGER (0..8388607), + longitude INTEGER (-8388608..8388607), + directionOfAltitude ENUMERATED {height, depth}, + altitude INTEGER (0..32767), + uncertaintySemi-major INTEGER (0..127), + uncertaintySemi-minor INTEGER (0..127), + orientationOfMajorAxis INTEGER (0..179), + uncertaintyAltitude INTEGER (0..127), + confidence INTEGER (0..100), + iE-Extensions ProtocolExtensionContainer { { NG-RANAccessPointPosition-ExtIEs} } OPTIONAL, + ... +} + +NG-RANAccessPointPosition-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +NGRANHighAccuracyAccessPointPosition ::= SEQUENCE { + latitude INTEGER (-2147483648.. 2147483647), + longitude INTEGER (-2147483648.. 2147483647), + altitude INTEGER (-64000..1280000), + uncertaintySemi-major INTEGER (0..255), + uncertaintySemi-minor INTEGER (0..255), +``` + +``` + orientationOfMajorAxis INTEGER (0..179), + horizontalConfidence INTEGER (0..100), + uncertaintyAltitude INTEGER (0..255), + verticalConfidence INTEGER (0..100), + iE-Extensions ProtocolExtensionContainer { { NGRANHighAccuracyAccessPointPosition-ExtIEs} } OPTIONAL, + ... +} + +NGRANHighAccuracyAccessPointPosition-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +NG-RAN-CGI ::= SEQUENCE { + pLMN-Identity PLMN-Identity, + nG-RANCell NG-RANCell, + iE-Extensions ProtocolExtensionContainer { {NG-RAN-CGI-ExtIEs} } OPTIONAL, + ... +} + +NG-RAN-CGI-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +NG-RANCell ::= CHOICE { + eUTRA-CellID EUTRACellIdentifier, + nR-CellID NRCellIdentifier, + choice-Extension ProtocolIE-Single-Container {{ NG-RANCell-ExtensionIE }} +} + +NG-RANCell-ExtensionIE NRPPA-PROTOCOL-IES ::= { + ... +} + +NR-ARFCN ::= INTEGER (0..3279165) + +NRCellIdentifier ::= BIT STRING (SIZE (36)) + +NrofSymbolsExtended ::= ENUMERATED {n8, n10, n12, n14, ...} + +NR-PCI ::= INTEGER (0..1007) + +NR-PRS-Beam-Information ::= SEQUENCE { + nR-PRS-Beam-InformationList SEQUENCE (SIZE(1.. maxPRS-ResourceSets)) OF NR-PRS-Beam-InformationItem, + LCS-to-GCS-TranslationList SEQUENCE (SIZE(1..maxnolcs-gcs-translation)) OF LCS-to-GCS-TranslationItem OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { NR-PRS-Beam-Information-IEs} } OPTIONAL, + ... +} +``` + +} + +NR-PRS-Beam-Information-IEs NRPPA-PROTOCOL-EXTENSION ::= { + +... + +} + +NR-PRS-Beam-InformationItem ::= SEQUENCE { + +pRSresourceSetID PRS-Resource-Set-ID, + +pRSAngle SEQUENCE (SIZE(1..maxPRS-ResourcesPerSet)) OF PRSAngleItem, + +iE-Extensions ProtocolExtensionContainer { { NR-PRS-Beam-InformationItem-ExtIEs } } OPTIONAL, + +... + +} + +NR-PRS-Beam-InformationItem-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + +... + +} + +NR-TADV ::= INTEGER (0.. 7690) + +NumberOfAntennaPorts-EUTRA ::= ENUMERATED { + +n1-or-n2, + +n4, + +... + +} + +NumberOfDlFrames-EUTRA ::= ENUMERATED { + +sf1, + +sf2, + +sf4, + +sf6, + +... + +} + +NumberOfDlFrames-Extended-EUTRA ::= INTEGER (1..160,...) + +NumberOfFrequencyHoppingBands ::= ENUMERATED { + +twobands, + +fourbands, + +... + +} + +NumberOfTRPRxTEG ::= ENUMERATED {two, three, four, six, eight, ...} + +NumberOfTRPRxTxTEG ::= ENUMERATED {two, three, four, six, eight, ...} + +NZP-CSI-RS-ResourceID ::= INTEGER (0..191) + +-- O + +``` +OnDemandPRS-Info ::= SEQUENCE { + onDemandPRSRequestAllowed BIT STRING (SIZE (16)), + allowedResourceSetPeriodicityValues BIT STRING (SIZE (24)) OPTIONAL, + allowedPRSBandwidthValues BIT STRING (SIZE (64)) OPTIONAL, + allowedResourceRepetitionFactorValues BIT STRING (SIZE (8)) OPTIONAL, + allowedResourceNumberOfSymbolsValues BIT STRING (SIZE (8)) OPTIONAL, + allowedCombSizeValues BIT STRING (SIZE (8)) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { OnDemandPRS-Info-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +OnDemandPRS-Info-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +OTDOACells ::= SEQUENCE (SIZE (1.. maxCellInRANnode)) OF SEQUENCE { + oTDOACellInfo OTDOACell-Information, + iE-Extensions ProtocolExtensionContainer { {OTDOACells-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +OTDOACells-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +OTDOACell-Information ::= SEQUENCE (SIZE (1..maxnoOTDOAtypes)) OF OTDOACell-Information-Item +``` + +``` +OTDOACell-Information-Item ::= CHOICE { +``` + +| | | +|------------------------------|-------------------------------| +| pCI-EUTRA | PCI-EUTRA, | +| cGI-EUTRA | CGI-EUTRA, | +| tAC | TAC, | +| eARFCN | EARFCN, | +| pRS-Bandwidth-EUTRA | PRS-Bandwidth-EUTRA, | +| pRS-ConfigurationIndex-EUTRA | PRS-ConfigurationIndex-EUTRA, | +| cPLength-EUTRA | CPLength-EUTRA, | +| numberOfDlFrames-EUTRA | NumberOfDlFrames-EUTRA, | +| numberOfAntennaPorts-EUTRA | NumberOfAntennaPorts-EUTRA, | +| sFNInitialisationTime-EUTRA | SFNInitialisationTime-EUTRA, | +| nG-RANAccessPointPosition | NG-RANAccessPointPosition, | +| pRSMutingConfiguration-EUTRA | PRSMutingConfiguration-EUTRA, | +| prsid-EUTRA | PRS-ID-EUTRA, | +| tpid-EUTRA | TP-ID-EUTRA, | +| tpType-EUTRA | TP-Type-EUTRA, | + +``` + + numberOfDlFrames-Extended-EUTRA NumberOfDlFrames-Extended-EUTRA, + crsCpLength-EUTRA CpLength-EUTRA, + dL-Bandwidth-EUTRA DL-Bandwidth-EUTRA, + prSOccasionGroup-EUTRA PRSOccasionGroup-EUTRA, + prSFrequencyHoppingConfiguration-EUTRA PRSFrequencyHoppingConfiguration-EUTRA, + choice-Extension ProtocolIE-Single-Container {{ OTDOACell-Information-Item-ExtensionIE }} + } + + OTDOACell-Information-Item-ExtensionIE NRPPA-PROTOCOL-IES ::= { + { ID id-TDD-Config-EUTRA-Item CRITICALITY ignore TYPE TDD-Config-EUTRA-Item PRESENCE mandatory }| + { ID id-CGI-NR CRITICALITY ignore TYPE CGI-NR PRESENCE mandatory }| + { ID id-SFNInitialisationTime-NR CRITICALITY ignore TYPE SFNInitialisationTime-EUTRA PRESENCE mandatory }, + ... + } + + OTDOA-Information-Item ::= ENUMERATED { + pci, + cGI, + tac, + earfcN, + prsBandwidth, + prsConfigIndex, + cpLength, + } + +``` + +``` + noDlFrames, + noAntennaPorts, + sFInitTime, + nG-RANAccessPointPosition, + prsmutingconfiguration, + prsid, + tpid, + tpType, + crsCPlength, + dlBandwidth, + multipleprsConfigurationsperCell, + prsOccasionGroup, + prsFrequencyHoppingConfiguration, + ..., + tddConfig +} + +OtherRATMeasurementQuantities ::= SEQUENCE (SIZE (0.. maxNoMeas)) OF ProtocolIE-Single-Container { {OtherRATMeasurementQuantities-ItemIEs} } + +OtherRATMeasurementQuantities-ItemIEs NRPPA-PROTOCOL-IES ::= { + { ID id-OtherRATMeasurementQuantities-Item CRITICALITY reject TYPE OtherRATMeasurementQuantities-Item PRESENCE mandatory} + +OtherRATMeasurementQuantities-Item ::= SEQUENCE { +``` + +``` + otherRATMeasurementQuantitiesValue OtherRATMeasurementQuantitiesValue, + iE-Extensions ProtocolExtensionContainer { { OtherRATMeasurementQuantitiesValue-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +OtherRATMeasurementQuantitiesValue-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +OtherRATMeasurementQuantitiesValue ::= ENUMERATED { + geran, + utran, + ... , + nR, + eUTRA +} +``` + +``` +OtherRATMeasurementResult ::= SEQUENCE (SIZE (1.. maxNoMeas)) OF OtherRATMeasuredResultsValue +``` + +``` +OtherRATMeasuredResultsValue ::= CHOICE { + resultGERAN ResultGERAN, + resultUTRAN ResultUTRAN, + choice-Extension ProtocolIE-Single-Container {{ OtherRATMeasuredResultsValue-ExtensionIE }} } +``` + +``` +} + +OtherRATMeasuredResultsValue-ExtensionIE NRPPA-PROTOCOL-IES ::= { + { ID id-ResultNR CRITICALITY ignore TYPE ResultNR PRESENCE mandatory }| + { ID id-ResultEUTRA CRITICALITY ignore TYPE ResultEUTRA PRESENCE mandatory }, + ... +} + +Outcome ::= ENUMERATED { + failed, + ... +} + +-- P + +PathlossReferenceInformation ::= SEQUENCE { + pathlossReferenceSignal PathlossReferenceSignal, + iE-Extensions ProtocolExtensionContainer { { PathlossReferenceInformation-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +PathlossReferenceInformation-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +PathlossReferenceSignal ::= CHOICE { +``` + +``` + sSB-Reference SSB, +``` + +``` + dL-PRS-Reference DL-PRS, +``` + +``` + choice-Extension ProtocolIE-Single-Container {{ PathlossReferenceSignal-ExtensionIE }} +``` + +``` +} +``` + +``` +PathlossReferenceSignal-ExtensionIE NRPPA-PROTOCOL-IES ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +PCI-EUTRA ::= INTEGER (0..503, ...) +``` + +``` +PhysCellIDGERAN ::= INTEGER (0..63, ...) +``` + +``` +PhysCellIDUTRA-FDD ::= INTEGER (0..511, ...) +``` + +``` +PhysCellIDUTRA-TDD ::= INTEGER (0..127, ...) +``` + +PLMN-Identity ::= OCTET STRING (SIZE(3)) + +PeriodicityList ::= SEQUENCE (SIZE (1.. maxnoSRS-ResourcePerSet)) OF PeriodicityItem + +PeriodicityItem ::= ENUMERATED {ms0dot125, ms0dot25, ms0dot5, ms0dot625, ms1, ms1dot25, ms2, ms2dot5, ms4dot, ms5, ms8, ms10, ms16, ms20, ms32, ms40, ms64, ms80m, ms160, ms320, ms640m, ms1280, ms2560, ms5120, ms10240, ...} + +PossSIBs ::= SEQUENCE (SIZE (1.. maxNrOfPossSIBs)) OF SEQUENCE { +    posSIB-Type                    PosSIB-Type, +    posSIB-Segments                PosSIB-Segments, +    assistanceInformationMetaData  AssistanceInformationMetaData  OPTIONAL, +    broadcastPriority              INTEGER (1..16,...)                OPTIONAL, +    iE-Extensions                  ProtocolExtensionContainer { { PossSIBs-ExtIEs} }  OPTIONAL, +    ... +} + +PossSIBs-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +    ... +} + +PossSIB-Segments ::= SEQUENCE (SIZE (1.. maxNrOfSegments)) OF SEQUENCE { +    assistanceDataSIBelement          OCTET STRING, + +``` +iE-Extensions ProtocolExtensionContainer { { PosSIB-Segments-ExtIEs } } OPTIONAL, +... +} + +PosSIB-Segments-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +... +} + +PosSIB-Type ::= ENUMERATED { + posSibType1-1, + posSibType1-2, + posSibType1-3, + posSibType1-4, + posSibType1-5, + posSibType1-6, + posSibType1-7, + posSibType1-8, + posSibType2-1, + posSibType2-2, + posSibType2-3, + posSibType2-4, + posSibType2-5, + posSibType2-6, +``` + +posSibType2-7, +posSibType2-8, +posSibType2-9, +posSibType2-10, +posSibType2-11, +posSibType2-12, +posSibType2-13, +posSibType2-14, +posSibType2-15, +posSibType2-16, +posSibType2-17, +posSibType2-18, +posSibType2-19, +posSibType2-20, +posSibType2-21, +posSibType2-22, +posSibType2-23, +posSibType2-24, +posSibType2-25, +posSibType3-1, +posSibType4-1, +posSibType5-1, +posSibType6-1, + +``` +posSibType6-2, +posSibType6-3, +... +posSibType1-9, +posSibType1-10, +posSibType6-4, +posSibType6-5, +posSibType6-6 +} +``` + +``` +PosSRSResource-List ::= SEQUENCE (SIZE (1..maxnoSRS-PosResources)) OF PosSRSResource-Item +``` + +``` +PosSRSResource-Item ::= SEQUENCE { + srs-PosResourceId SRSPosResourceID, + transmissionCombPos TransmissionCombPos, + startPosition INTEGER (0..13), + nrofSymbols ENUMERATED {n1, n2, n4, n8, n12}, + freqDomainShift INTEGER (0..268), + c-SRS INTEGER (0..63), + groupOrSequenceHopping ENUMERATED { neither, groupHopping, sequenceHopping }, + resourceTypePos ResourceTypePos, + sequenceId INTEGER (0.. 65535), + spatialRelationPos SpatialRelationPos OPTIONAL, +``` + +``` +iE-Extensions ProtocolExtensionContainer { { PosSRSResource-Item-ExtIEs} } OPTIONAL, +... +} + +PosSRSResource-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +... +} + +PosSRSResourceID-List ::= SEQUENCE (SIZE (1..maxnoSRS-PosResources)) OF SRSPosResourceID + +PosSRSResourceSet-List ::= SEQUENCE (SIZE (1..maxnoSRS-PosResourceSets)) OF PosSRSResourceSet-Item + +PosSRSResourceIDPerSet-List ::= SEQUENCE (SIZE (1..maxnoSRS-PosResourcePerSet)) OF SRSPosResourceID + +PosSRSResourceSet-Item ::= SEQUENCE { + possrsResourceSetID INTEGER(0..15), + possRSResourceIDPerSet-List PosSRSResourceIDPerSet-List, + posresourceSetType PosResourceSetType, + iE-Extensions ProtocolExtensionContainer { { PosSRSResourceSet-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +PosSRSResourceSet-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +PosResourceSetType ::= CHOICE { + periodic PosResourceSetTypePeriodic, + semi-persistent PosResourceSetTypeSemi-persistent, + aperiodic PosResourceSetTypeAperiodic, + choice-extension ProtocolIE-Single-Container {{ PosResourceSetType-ExtIEs }} +} + +PosResourceSetType-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +PosResourceSetTypePeriodic ::= SEQUENCE { + posperiodicSet ENUMERATED{true, ...}, + iE-Extensions ProtocolExtensionContainer { { PosResourceSetTypePeriodic-ExtIEs } } OPTIONAL, + ... +} + +PosResourceSetTypePeriodic-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +PosResourceSetTypeSemi-persistent ::= SEQUENCE { + possemi-persistentSet ENUMERATED(true, ...), + iE-Extensions ProtocolExtensionContainer { { PosResourceSetTypeSemi-persistent-ExtIEs} } OPTIONAL, + ... +} + +PosResourceSetTypeSemi-persistent-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +PosResourceSetTypeAperiodic ::= SEQUENCE { + sRSResourceTrigger INTEGER(1..3), + iE-Extensions ProtocolExtensionContainer { { PosResourceSetTypeAperiodic-ExtIEs} } OPTIONAL, + ... +} + +PosResourceSetTypeAperiodic-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +PreconfigurationResult ::= BIT STRING (SIZE(8)) + +PRS-Bandwidth-EUTRA ::= ENUMERATED { + +bw6, +bw15, +bw25, +bw50, +bw75, +bw100, +... + +} + +PRSAngleItem ::= SEQUENCE { + +nRPRSAzimuth INTEGER (0..359), +nRPRSAzimuthFine INTEGER (0..9) OPTIONAL, +nRPRSElevation INTEGER (0..180) OPTIONAL, +nRPRSElevationFine INTEGER (0..9) OPTIONAL, +iE-Extensions ProtocolExtensionContainer { { PRSAngleItem-ExtIEs } } OPTIONAL, +... + +} + +PRSAngleItem-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + +``` +{ ID id-PRS-Resource-ID CRITICALITY ignore EXTENSION PRS-Resource-ID PRESENCE optional }, +... +} + +PRSInformationPos ::= SEQUENCE { + pRS-IDPos INTEGER(0..255), + pRS-Resource-Set-IDPos INTEGER(0..7), + pRS-Resource-IDPos INTEGER(0..63) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PRSInformationPos-ExtIEs } } OPTIONAL, + ... +} + +PRSInformationPos-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +PRSConfigRequestType ::= ENUMERATED {configure, off, ...} + +PRSConfiguration ::= SEQUENCE { + pRSResourceSet-List PRSResourceSet-List, + iE-Extensions ProtocolExtensionContainer { { PRSConfiguration-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +PRSConfiguration-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PRS-ConfigurationIndex-EUTRA ::= INTEGER (0..4095, ...) +``` + +``` +PRS-ID-EUTRA ::= INTEGER (0..4095, ...) +``` + +``` +PRSMutingConfiguration-EUTRA ::= CHOICE { + two BIT STRING (SIZE (2)), + four BIT STRING (SIZE (4)), + eight BIT STRING (SIZE (8)), + sixteen BIT STRING (SIZE (16)), + thirty-two BIT STRING (SIZE (32)), + sixty-four BIT STRING (SIZE (64)), + one-hundred-and-twenty-eight BIT STRING (SIZE (128)), + two-hundred-and-fifty-six BIT STRING (SIZE (256)), + five-hundred-and-twelve BIT STRING (SIZE (512)), + one-thousand-and-twenty-four BIT STRING (SIZE (1024)), + choice-Extension ProtocolIE-Single-Container {{ PRSMutingConfiguration-EUTRA-ExtensionIE }} +} +``` + +PRSMutingConfiguration-EUTRA-ExtensionIE NRPPA-PROTOCOL-IES ::= { + +... + +} + +PRSOccasionGroup-EUTRA ::= ENUMERATED { + +og2, + +og4, + +og8, + +og16, + +og32, + +og64, + +og128, + +... + +} + +PRSFrequencyHoppingConfiguration-EUTRA ::= SEQUENCE { + +noOfFreqHoppingBands      NumberOfFrequencyHoppingBands, + +bandPositions              SEQUENCE (SIZE (1..maxnoFreqHoppingBandsMinusOne)) OF NarrowBandIndex, + +iE-Extensions              ProtocolExtensionContainer { { PRSFrequencyHoppingConfiguration-EUTRA-Item-IEs } } OPTIONAL, + +... + +} + +``` +PRSFrequencyHoppingConfiguration-EUTRA-Item-IEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +PRS-Measurements-Info-List ::= SEQUENCE (SIZE(1..maxFreqLayers)) OF PRS-Measurements-Info-List-Item + +PRS-Measurements-Info-List-Item ::= SEQUENCE { + pointA INTEGER (0..3279165), + measPRSPeriodicity ENUMERATED {ms20, ms40, ms80, ms160, ...}, + measPRSOFFset INTEGER (0..159, ...), + measurementPRSLength ENUMERATED {ms1dot5, ms3, ms3dot5, ms4, ms5dot5, ms6, ms10, ms20}, + iE-Extensions ProtocolExtensionContainer { { PRS-Measurements-Info-List-Item-ExtIEs} } OPTIONAL, + ... +} + +PRS-Measurements-Info-List-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +PRSMuting ::= SEQUENCE { + pRSMutingOption1 PRSMutingOption1 OPTIONAL, + pRSMutingOption2 PRSMutingOption2 OPTIONAL, +``` + +``` +iE-Extensions ProtocolExtensionContainer { { PRSMuting-ExtIEs } } OPTIONAL, +... +} + +PRSMuting-ExtIEs NRPFA-PROTOCOL-EXTENSION ::= { + ... +} + +PRSMutingOption1 ::= SEQUENCE { + mutingPattern DL-PRSMutingPattern, + mutingBitRepetitionFactor ENUMERATED{n1,n2,n4,n8,...}, + iE-Extensions ProtocolExtensionContainer { { PRSMutingOption1-ExtIEs } } OPTIONAL, + ... +} + +PRSMutingOption1-ExtIEs NRPFA-PROTOCOL-EXTENSION ::= { + ... +} + +PRSMutingOption2 ::= SEQUENCE { + mutingPattern DL-PRSMutingPattern, + iE-Extensions ProtocolExtensionContainer { { PRSMutingOption2-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +PRSMutingOption2-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +PRSResource-List ::= SEQUENCE (SIZE (1..maxnoofPRSresource)) OF PRSResource-Item + +PRSResource-Item ::= SEQUENCE { + pRSResourceID PRS-Resource-ID, + sequenceID INTEGER(0..4095), + rEOffset INTEGER(0..11,...), + resourceSlotOffset INTEGER(0..511), + resourceSymbolOffset INTEGER(0..12), + qCLInfo PRSResource-QCLInfo OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PRSResource-Item-ExtIEs } } OPTIONAL, + ... +} + +PRSResource-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + { ID id-ExtendedResourceSymbolOffset CRITICALITY ignore EXTENSION ExtendedResourceSymbolOffset PRESENCE optional }, + ... +} + +ExtendedResourceSymbolOffset ::= INTEGER (0..13,...) +``` + +``` +PRSResource-QCLInfo ::= CHOICE { + qCLSourceSSB PRSResource-QCLSourceSSB, + qCLSourcePRS PRSResource-QCLSourcePRS, + choice-Extension ProtocolIE-Single-Container { { PRSResource-QCLInfo-ExtIEs } } +} + +PRSResource-QCLInfo-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +PRSResource-QCLSourceSSB ::= SEQUENCE { + pCI-NR INTEGER(0..1007), + sSB-Index SSB-Index OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PRSResource-QCLSourceSSB-ExtIEs } } OPTIONAL, + ... +} + +PRSResource-QCLSourceSSB-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +PRSResource-QCLSourcePRS ::= SEQUENCE { + qCLSourcePRSResourceSetID PRS-Resource-Set-ID, +``` + +``` + + qCLSourcePRSResourceID PRS-Resource-ID OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PRSResource-QCLSourcePRS-ExtIEs } } OPTIONAL, + ... +} + +PRSResource-QCLSourcePRS-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +PRSResourceSet-List ::= SEQUENCE (SIZE (1..maxnoofPRSresourceSet)) OF PRSResourceSet-Item + +PRSResourceSet-Item ::= SEQUENCE { + pRSResourceSetID PRS-Resource-Set-ID, + subcarrierSpacing ENUMERATED{kHz15, kHz30, kHz60, kHz120, ...}, + pRSbandwidth INTEGER(1..63), + startPRB INTEGER(0..2176), + pointA INTEGER (0..3279165), + combSize ENUMERATED{n2, n4, n6, n12, ...}, + cPType ENUMERATED{normal, extended, ...}, + resourceSetPeriodicity ENUMERATED{n4,n5,n8,n10,n16,n20,n32,n40,n64,n80,n160,n320,n640,n1280,n2560,n5120,n10240,n20480,n40960, +n81920,..., n128, n256, n512}, + resourceSetSlotOffset INTEGER(0..81919,...), + resourceRepetitionFactor ENUMERATED{rf1,rf2,rf4,rf6,rf8,rf16,rf32,...}, +} + +``` + +``` +resourceTimeGap ENUMERATED{tg1,tg2,tg4,tg8,tg16,tg32,...}, +resourceNumberOfSymbols ENUMERATED{n2,n4,n6,n12,...,n1}, +pRSMuting PRSMuting OPTIONAL, +pRSResourceTransmitPower INTEGER(-60..50), +pRSResource-List PRSResource-List, +iE-Extensions ProtocolExtensionContainer { { PRSResourceSet-Item-ExtIEs} } OPTIONAL, +... +} +``` + +``` +PRSResourceSet-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +... +} +``` + +``` +PRS-Resource-ID ::= INTEGER (0..63) +``` + +``` +PRS-Resource-Set-ID ::= INTEGER(0..7) +``` + +``` +PRS-ID ::= INTEGER(0..255) +``` + +``` +PRSTransmissionOffIndication ::= CHOICE { +pRSTransmissionOffPerTRP NULL, +pRSTransmissionOffPerResourceSet PRSTransmissionOffPerResourceSet, +pRSTransmissionOffPerResource PRSTransmissionOffPerResource, +``` + +``` +choice-Extension ProtocolIE-Single-Container {{ PRSTransmissionOffIndication-ExtIEs }} +} + +PRSTransmissionOffIndication-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +PRSTransmissionOffPerResource ::= SEQUENCE (SIZE (1..maxnoofPRSresourceSet)) OF PRSTransmissionOffPerResource-Item + +PRSTransmissionOffPerResource-Item ::= SEQUENCE { + pRSResourceSetID PRS-Resource-Set-ID, + PRSTransmissionOffIndicationPerResourceList SEQUENCE (SIZE(1.. maxnoofPRSresource)) OF PRSTransmissionOffIndicationPerResource-Item, + iE-Extensions ProtocolExtensionContainer { { PRSTransmissionOffPerResource-Item-ExtIEs} } OPTIONAL, + ... +} + +PRSTransmissionOffPerResource-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +PRSTransmissionOffIndicationPerResource-Item ::= SEQUENCE { + pRSResourceID PRS-Resource-ID, + iE-Extensions ProtocolExtensionContainer { { PRSTransmissionOffIndicationPerResource-Item-ExtIEs} } OPTIONAL, +``` + +``` +... +} + +PRSTransmissionOffIndicationPerResource-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +PRSTransmissionOffInformation ::= SEQUENCE { + pPRSTransmissionOffIndication PRSTransmissionOffIndication, + iE-Extensions ProtocolExtensionContainer { { PRSTransmissionOffInformation-ExtIEs} } OPTIONAL, + ... +} + +PRSTransmissionOffInformation-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +PRSTransmissionOffPerResourceSet ::= SEQUENCE (SIZE (1..maxnoofPRSresourceSet)) OF PRSTransmissionOffPerResourceSet-Item + +PRSTransmissionOffPerResourceSet-Item ::= SEQUENCE { + pPRSResourceSetID PRS-Resource-Set-ID, + iE-Extensions ProtocolExtensionContainer { { PRSTransmissionOffPerResourceSet-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +} + +PRSTransmissionOffPerResourceSet-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + +... + +} + +PRSTRPList ::= SEQUENCE (SIZE(1.. maxnoTRPs)) OF PRSTRPItem + +PRSTRPItem ::= SEQUENCE { + +tRP-ID TRP-ID, + +requestedDLPRSTransmissionCharacteristics RequestedDLPRSTransmissionCharacteristics OPTIONAL, + +-- The IE shall be present if the PRS Configuration Request Type IE is set to "configure" -- + +pRSTransmissionOffInformation PRSTransmissionOffInformation OPTIONAL, + +-- The IE shall be present if the PRS Configuration Request Type IE is set to "off" -- + +iE-Extensions ProtocolExtensionContainer { { PRSTRPItem-ExtIEs } } OPTIONAL, + +... + +} + +PRSTRPItem-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + +... + +} + +``` +PRSTransmissionTRPList ::= SEQUENCE (SIZE(1.. maxnoTRPs)) OF PRSTransmissionTRPItem +``` + +``` +PRSTransmissionTRPItem ::= SEQUENCE { + tRP-ID TRP-ID, + pRSConfiguration PRSConfiguration, + iE-Extensions ProtocolExtensionContainer { { PRSTransmissionTRPItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +PRSTransmissionTRPItem-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +-- Q + +-- R + +``` +ReferenceSignal ::= CHOICE { + nZP-CSI-RS NZP-CSI-RS-ResourceID, + sSB SSB, + sRS SRSResourceID, +``` + +``` +positioningSRS SRSPosResourceID, +dL-PRS DL-PRS, +choice-Extension ProtocolIE-Single-Container {{ReferenceSignal-ExtensionIE }} +} +``` + +``` +ReferenceSignal-ExtensionIE NRPPA-PROTOCOL-IES ::= { + ... +} +``` + +``` +ReferencePoint ::= CHOICE { + relativeCoordinateID CoordinateID, + referencePointCoordinate NG-RANAccessPointPosition, + referencePointCoordinateHA NGRANHighAccuracyAccessPointPosition, + choice-Extension ProtocolIE-Single-Container { { ReferencePoint-ExtIEs } } +} +``` + +``` +ReferencePoint-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} +``` + +``` +CoordinateID ::= INTEGER (0..511, ...) +``` + +``` +RelativeGeodeticLocation ::= SEQUENCE { + milli-Arc-SecondUnits ENUMERATED {zerodot03, zerodot3, three, ...}, + heightUnits ENUMERATED {mm, cm, m, ...}, +``` + +``` +deltaLatitude INTEGER (-1024.. 1023), +deltaLongitude INTEGER (-1024.. 1023), +deltaHeight INTEGER (-1024.. 1023), +locationUncertainty LocationUncertainty, +iE-extensions ProtocolExtensionContainer {{RelativeGeodeticLocation-ExtIEs }} OPTIONAL, +... +} +``` + +``` +RelativeGeodeticLocation-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +... +} +``` + +``` +RelativeCartesianLocation ::= SEQUENCE { +xYZunit ENUMERATED {mm, cm, dm, ...}, +xvalue INTEGER (-65536..65535), +yvalue INTEGER (-65536..65535), +zvalue INTEGER (-32768..32767), +locationUncertainty LocationUncertainty, +iE-Extensions ProtocolExtensionContainer { { RelativeCartesianLocation-ExtIEs } } OPTIONAL, +... +} +``` + +``` +RelativeCartesianLocation-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +RelativePathDelay ::= CHOICE { +``` + +``` + k0 INTEGER(0..16351), +``` + +``` + k1 INTEGER(0..8176), +``` + +``` + k2 INTEGER(0..4088), +``` + +``` + k3 INTEGER(0..2044), +``` + +``` + k4 INTEGER(0..1022), +``` + +``` + k5 INTEGER(0..511), +``` + +``` + choice-Extension ProtocolIE-Single-Container { { RelativePathDelay-ExtIEs} } +``` + +``` +} +``` + +``` +RelativePathDelay-ExtIEs NRPPA-PROTOCOL-IES ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +RepetitionFactorExtended ::= ENUMERATED {n3, n5, n6, n7, n8, n10, n12, n14, ...} +``` + +``` +ReportCharacteristics ::= ENUMERATED { +``` + +``` + onDemand, +``` + +``` + periodic, +``` + +``` + + ... +} + +RequestedDLPRSTransmissionCharacteristics ::= SEQUENCE { + requestedDLPRSResourceSet-List RequestedDLPRSResourceSet-List, + numberOfFrequencyLayers INTEGER(1..4) OPTIONAL, + startTimeAndDuration StartTimeAndDuration OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { RequestedDLPRSTransmissionCharacteristics-ExtIEs} } OPTIONAL, + ... +} + +RequestedDLPRSTransmissionCharacteristics-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +RequestedDLPRSResourceSet-List ::= SEQUENCE (SIZE (1..maxnoofPRSresourceSet)) OF RequestedDLPRSResourceSet-Item + +RequestedDLPRSResourceSet-Item ::= SEQUENCE { + pRSbandwidth INTEGER(1..63) OPTIONAL, + combSize ENUMERATED{n2, n4, n6, n12, ...} OPTIONAL, + resourceSetPeriodicity ENUMERATED{n4,n5,n8,n10,n16,n20,n32,n40,n64,n80,n160,n320,n640,n1280,n2560,n5120,n10240,n20480,n40960, +n81920,..., n128, n256 ,n512} OPTIONAL, + resourceRepetitionFactor ENUMERATED{rf1,rf2,rf4,rf6,rf8,rf16,rf32,...} OPTIONAL, + resourceNumberOfSymbols ENUMERATED{n2,n4,n6,n12,...,n1} OPTIONAL, +} + +``` + +``` + requestedDLPRSResource-List RequestedDLPRSResource-List OPTIONAL, + resourceSetStartTimeAndDuration StartTimeAndDuration OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { RequestedDLPRSResourceSet-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +RequestedDLPRSResourceSet-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +RequestedDLPRSResource-List ::= SEQUENCE (SIZE (1..maxnoofPRSresource)) OF RequestedDLPRSResource-Item +``` + +``` +RequestedDLPRSResource-Item ::= SEQUENCE { + qCLInfo PRSResource-QCLInfo OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { RequestedDLPRSResource-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +RequestedDLPRSResource-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +RequestedSRSTransmissionCharacteristics ::= SEQUENCE { + numberOfTransmissions INTEGER (0..500,...) OPTIONAL, + -- The IE shall be present if the Resource Type IE is set to "periodic" -- + resourceType ENUMERATED {periodic, semi-persistent, aperiodic, ...}, + bandwidth BandwidthSRS, + listOfSRSResourceSet SEQUENCE (SIZE (1.. maxnoSRS-ResourceSets)) OF SRSResourceSet-Item OPTIONAL, + sSBInformation SSBInfo OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { RequestedSRSTransmissionCharacteristics-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +RequestedSRSTransmissionCharacteristics-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + { ID id-SrsFrequency CRITICALITY ignore EXTENSION SrsFrequency PRESENCE optional }, + ... +} +``` + +``` +SRSResourceSet-Item ::= SEQUENCE { + numberOfSRSResourcePerSet INTEGER (1..16, ...) OPTIONAL, + periodicityList PeriodicityList OPTIONAL, + spatialRelationInformation SpatialRelationInfo OPTIONAL, + pathlossReferenceInformation PathlossReferenceInformation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SRSResourceSet-Item-ExtIEs} } OPTIONAL, +``` + +``` + ... +} + +SRSResourceSet-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ID id-SRSSpatialRelationPerSRSResource CRITICALITY ignore EXTENSION SpatialRelationPerSRSResource PRESENCE optional}, + ... +} + +RequestType ::= ENUMERATED {activate, deactivate, ...} + +ResourceSetType ::= CHOICE { + periodic ResourceSetTypePeriodic, + semi-persistent ResourceSetTypeSemi-persistent, + aperiodic ResourceSetTypeAperiodic, + choice-extension ProtocolIE-Single-Container {{ ResourceSetType-ExtIEs }} +} + +ResourceSetType-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +ResourceSetTypePeriodic ::= SEQUENCE { + periodicSet ENUMERATED{true, ...}, +``` + +``` +iE-Extensions ProtocolExtensionContainer { { ResourceSetTypePeriodic-ExtIEs} } OPTIONAL, +... +} + +ResourceSetTypePeriodic-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +... +} + +ResourceSetTypeSemi-persistent ::= SEQUENCE { +semi-persistentSet ENUMERATED{true, ...}, +iE-Extensions ProtocolExtensionContainer { { ResourceSetTypeSemi-persistent-ExtIEs} } OPTIONAL, +... +} + +ResourceSetTypeSemi-persistent-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +... +} + +ResourceSetTypeAperiodic ::= SEQUENCE { +sRSResourceTrigger INTEGER(1..3), +slotoffset INTEGER(0..32), +iE-Extensions ProtocolExtensionContainer { { ResourceSetTypeAperiodic-ExtIEs} } OPTIONAL, +... +``` + +``` +} + +ResourceSetTypeAperiodic-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +ResourceType ::= CHOICE { + periodic ResourceTypePeriodic, + semi-persistent ResourceTypeSemi-persistent, + aperiodic ResourceTypeAperiodic, + choice-extension ProtocolIE-Single-Container {{ ResourceType-ExtIEs }} +} + +ResourceType-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +ResourceTypePeriodic ::= SEQUENCE { + periodicity ENUMERATED{slot1, slot2, slot4, slot5, slot8, slot10, slot16, slot20, slot32, slot40, slot64, slot80, slot160, + slot320, slot640, slot1280, slot2560, ...}, + offset INTEGER(0..2559, ...), + iE-Extensions ProtocolExtensionContainer { { ResourceTypePeriodic-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +} + +ResourceTypePeriodic-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +ResourceTypeSemi-persistent ::= SEQUENCE { + periodicity ENUMERATED{slot1, slot2, slot4, slot5, slot8, slot10, slot16, slot20, slot32, slot40, slot64, slot80, slot160, slot320, +slot640, slot1280, slot2560, ...}, + offset INTEGER(0..2559, ...), + iE-Extensions ProtocolExtensionContainer { { ResourceTypeSemi-persistent-ExtIEs} } OPTIONAL, + ... +} + +ResourceTypeSemi-persistent-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +ResourceTypeAperiodic ::= SEQUENCE { + aperiodicResourceType ENUMERATED{true, ...}, + iE-Extensions ProtocolExtensionContainer { { ResourceTypeAperiodic-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +ResourceTypeAperiodic-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +ResourceTypePos ::= CHOICE { +``` + +``` + periodic ResourceTypePeriodicPos, +``` + +``` + semi-persistent ResourceTypeSemi-persistentPos, +``` + +``` + aperiodic ResourceTypeAperiodicPos, +``` + +``` + choice-extension ProtocolIE-Single-Container {{ ResourceTypePos-ExtIEs }} +``` + +``` +} +``` + +``` +ResourceTypePos-ExtIEs NRPPA-PROTOCOL-IES ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +ResourceTypePeriodicPos ::= SEQUENCE { +``` + +``` + periodicity ENUMERATED{slot1, slot2, slot4, slot5, slot8, slot10, slot16, slot20, slot32, slot40, slot64, slot80, slot160, slot320, slot640, slot1280, slot2560, slot5120, slot10240, slot40960, slot81920, ..., slot128, slot256, slot512, slot20480}, +``` + +``` + offset INTEGER(0..81919, ...), +``` + +``` + iE-Extensions ProtocolExtensionContainer {{ ResourceTypePeriodicPos-ExtIEs }} OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +ResourceTypePeriodicPos-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +ResourceTypeSemi-persistentPos ::= SEQUENCE { +``` + +``` + periodicity ENUMERATED{slot1, slot2, slot4, slot5, slot8, slot10, slot16, slot20, slot32, slot40, slot64, slot80, slot160, slot320, slot640, slot1280, slot2560, slot5120, slot10240, slot40960, slot81920, ..., slot128, slot256, slot512, slot20480}, +``` + +``` + offset INTEGER(0..81919, ...), +``` + +``` + iE-Extensions ProtocolExtensionContainer { { ResourceTypeSemi-persistentPos-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +ResourceTypeSemi-persistentPos-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +ResourceTypeAperiodicPos ::= SEQUENCE { +``` + +``` + slotOffset INTEGER (0..32), +``` + +``` + iE-Extensions ProtocolExtensionContainer { { ResourceTypeAperiodicPos-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +ResourceTypeAperiodicPos-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +} + +``` +ResponseTime ::= SEQUENCE { + time INTEGER (1..128,...), + timeUnit ENUMERATED {second, ten-seconds, ten-milliseconds,...}, + iE-Extensions ProtocolExtensionContainer { { ResponseTime-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +ResponseTime-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +ResultCSI-RSRP ::= SEQUENCE (SIZE (1.. maxCellReportNR)) OF ResultCSI-RSRP-Item +``` + +``` +ResultCSI-RSRP-Item ::= SEQUENCE { + nR-PCI NR-PCI, + nR-ARFCN NR-ARFCN, + cGI-NR CGI-NR OPTIONAL, + valueCSI-RSRP-Cell ValueRSRP-NR OPTIONAL, + cSI-RSRP-PerCSI-RS ResultCSI-RSRP-PerCSI-RS OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { ResultCSI-RSRP-Item-ExtIEs } } OPTIONAL, +``` + +``` + ... +} + +ResultCSI-RSRP-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +ResultCSI-RSRP-PerCSI-RS ::= SEQUENCE (SIZE (1.. maxIndexesReport)) OF ResultCSI-RSRP-PerCSI-RS-Item + +ResultCSI-RSRP-PerCSI-RS-Item ::= SEQUENCE { + cSI-RS-Index INTEGER (0..95), + valueCSI-RSRP ValueRSRP-NR, + iE-Extensions ProtocolExtensionContainer { { ResultCSI-RSRP-PerCSI-RS-Item-ExtIEs} } OPTIONAL, + ... +} + +ResultCSI-RSRP-PerCSI-RS-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +ResultCSI-RSRQ ::= SEQUENCE (SIZE (1.. maxCellReportNR)) OF ResultCSI-RSRQ-Item + +ResultCSI-RSRQ-Item ::= SEQUENCE { +``` + +``` + nR-PCI NR-PCI, + nR-ARFCN NR-ARFCN, + cGI-NR CGI-NR OPTIONAL, + valueCSI-RSQ-Cell ValueRSRQ-NR OPTIONAL, + cSI-RSQ-PerCSI-RS ResultCSI-RSQ-PerCSI-RS OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { ResultCSI-RSQ-Item-ExtIEs} } OPTIONAL, + ... +} + +ResultCSI-RSQ-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +ResultCSI-RSQ-PerCSI-RS ::= SEQUENCE (SIZE (1.. maxIndexesReport)) OF ResultCSI-RSQ-PerCSI-RS-Item + +ResultCSI-RSQ-PerCSI-RS-Item ::= SEQUENCE { + cSI-RS-Index INTEGER (0..95), + valueCSI-RSQ ValueRSRQ-NR, + iE-Extensions ProtocolExtensionContainer { { ResultCSI-RSQ-PerCSI-RS-Item-ExtIEs} } OPTIONAL, + ... +} + +ResultCSI-RSQ-PerCSI-RS-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +ResultEUTRA ::= SEQUENCE (SIZE (1.. maxEUTRAMeas)) OF ResultEUTRA-Item + +ResultEUTRA-Item ::= SEQUENCE { + pCI-EUTRA PCI-EUTRA, + eARFCN EARFCN, + valueRSRP-EUTRA ValueRSRP-EUTRA OPTIONAL, + valueRSRQ-EUTRA ValueRSRQ-EUTRA OPTIONAL, + cGI-EUTRA CGI-EUTRA OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { ResultEUTRA-Item-ExtIEs } } OPTIONAL, + ... +} + +ResultEUTRA-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +ResultRSRP-EUTRA ::= SEQUENCE (SIZE (1.. maxCellReport)) OF ResultRSRP-EUTRA-Item + +ResultRSRP-EUTRA-Item ::= SEQUENCE { +``` + +``` + pCI-EUTRA PCI-EUTRA, + eARFCN EARFCN, + cGI-EUTRA CGI-EUTRA OPTIONAL, + valueRSRP-EUTRA ValueRSRP-EUTRA, + iE-Extensions ProtocolExtensionContainer { { ResultRSRP-EUTRA-Item-ExtIEs } } OPTIONAL, + ... +} + +ResultRSRP-EUTRA-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +ResultRSRQ-EUTRA ::= SEQUENCE (SIZE (1.. maxCellReport)) OF ResultRSRQ-EUTRA-Item + +ResultRSRQ-EUTRA-Item ::= SEQUENCE { + pCI-EUTRA PCI-EUTRA, + eARFCN EARFCN, + cGI-UTRA CGI-EUTRA OPTIONAL, + valueRSRQ-EUTRA ValueRSRQ-EUTRA, + iE-Extensions ProtocolExtensionContainer { { ResultRSRQ-EUTRA-Item-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +ResultRSRQ-EUTRA-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +ResultSS-RSRP ::= SEQUENCE (SIZE (1.. maxCellReportNR)) OF ResultSS-RSRP-Item +``` + +``` +ResultSS-RSRP-Item ::= SEQUENCE { +``` + +``` + nR-PCI NR-PCI, +``` + +``` + nR-ARFCN NR-ARFCN, +``` + +``` + cGI-NR CGI-NR OPTIONAL, +``` + +``` + valueSS-RSRP-Cell ValueRSRP-NR OPTIONAL, +``` + +``` + sS-RSRP-PerSSB ResultSS-RSRP-PerSSB OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { ResultSS-RSRP-Item-ExtIEs } } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +ResultSS-RSRP-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +ResultSS-RSRP-PerSSB ::= SEQUENCE (SIZE (1.. maxIndexesReport)) OF ResultSS-RSRP-PerSSB-Item +``` + +``` +ResultSS-RSRP-PerSSB-Item ::= SEQUENCE { + sSB-Index SSB-Index, + valueSS-RSRP ValueRSRP-NR, + iE-Extensions ProtocolExtensionContainer { { ResultSS-RSRP-PerSSB-Item-ExtIEs} } OPTIONAL, + ... +} + +ResultSS-RSRP-PerSSB-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +ResultSS-RSRQ ::= SEQUENCE (SIZE (1.. maxCellReportNR)) OF ResultSS-RSRQ-Item + +ResultSS-RSRQ-Item ::= SEQUENCE { + nR-PCI NR-PCI, + nR-ARFCN NR-ARFCN, + cGI-NR CGI-NR OPTIONAL, + valueSS-RSRQ-Cell ValueRSRQ-NR OPTIONAL, + sS-RSRQ-PerSSB ResultSS-RSRQ-PerSSB OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { ResultSS-RSRQ-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +ResultSS-RSRQ-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +ResultSS-RSRQ-PerSSB ::= SEQUENCE (SIZE (1.. maxIndexesReport)) OF ResultSS-RSRQ-PerSSB-Item +``` + +``` +ResultSS-RSRQ-PerSSB-Item ::= SEQUENCE { +``` + +``` + sSB-Index SSB-Index, +``` + +``` + valueSS-RSRQ ValueRSRQ-NR, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { ResultSS-RSRQ-PerSSB-Item-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +ResultSS-RSRQ-PerSSB-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +ResultGERAN ::= SEQUENCE (SIZE (1.. maxGERANMeas)) OF ResultGERAN-Item +``` + +``` +ResultGERAN-Item ::= SEQUENCE { +``` + +``` + bCCH BCCH, +``` + +``` + physCellIDGERAN PhysCellIDGERAN, +``` + +``` + rSSI RSSI, + iE-Extensions ProtocolExtensionContainer { { ResultGERAN-Item-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +ResultGERAN-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +ResultNR ::= SEQUENCE (SIZE (1.. maxNRMeas)) OF ResultNR-Item +``` + +``` +ResultNR-Item ::= SEQUENCE { + nR-PCI NR-PCI, + nR-ARFCN NR-ARFCN, + valueSS-RSRP-Cell ValueRSRP-NR OPTIONAL, + valueSS-RSRQ-Cell ValueRSQ-NR OPTIONAL, + sS-RSRP-PerSSB ResultSS-RSRP-PerSSB OPTIONAL, + sS-RSRQ-PerSSB ResultSS-RSRQ-PerSSB OPTIONAL, + cGI-NR CGI-NR OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { ResultNR-Item-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +ResultNR-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +ResultUTRAN ::= SEQUENCE (SIZE (1.. maxUTRANMeas)) OF ResultUTRAN-Item +``` + +``` +ResultUTRAN-Item ::= SEQUENCE { + uARFCN UARFCN, + physCellIDUTRAN CHOICE { + physCellIDUTRA-FDD PhysCellIDUTRA-FDD, + physCellIDUTRA-TDD PhysCellIDUTRA-TDD + }, + uTRA-RSCP UTRA-RSCP OPTIONAL, + uTRA-EcN0 UTRA-EcN0 OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { ResultUTRAN-Item-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +ResultUTRAN-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +RSSI ::= INTEGER (0..63, ...) + +RxTxTimingErrorMargin ::= ENUMERATED {tc0dot5, tc1, tc2, tc4, tc8, tc12, tc16, tc20, tc24, tc32, tc40, tc48, tc64, tc80, tc96, tc128, ...} + +-- S + +SCS-SpecificCarrier ::= SEQUENCE { +    offsetToCarrier                  INTEGER (0..2199,...), +    subcarrierSpacing              ENUMERATED {kHz15, kHz30, kHz60, kHz120,..., kHz480, kHz960}, +    carrierBandwidth               INTEGER (1..275,...), +    iE-Extensions                ProtocolExtensionContainer { { SCS-SpecificCarrier-ExtIEs } } OPTIONAL, +    ... +} + +SCS-SpecificCarrier-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +    ... +} + +Search-window-information ::= SEQUENCE { +    expectedPropagationDelay      INTEGER (-3841..3841,...), +    delayUncertainty            INTEGER (1..246,...), +} + +``` +iE-Extensions ProtocolExtensionContainer { { Search-window-information-ExtIEs } } OPTIONAL, +... +} + +Search-window-information-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +... +} + +RelativeTime1900 ::= BIT STRING (SIZE (64)) + +SFNInitialisationTime-EUTRA ::= BIT STRING (SIZE (64)) + +SlotNumber ::= INTEGER (0..79) + +SpatialDirectionInformation ::= SEQUENCE { + nR-PRS-Beam-Information NR-PRS-Beam-Information, + iE-Extensions ProtocolExtensionContainer { { SpatialDirectionInformation-ExtIEs } } OPTIONAL, + ... +} + +SpatialDirectionInformation-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +SpatialRelationInfo ::= SEQUENCE { + spatialRelationforResourceID SpatialRelationforResourceID, + iE-Extensions ProtocolExtensionContainer { {SpatialRelationInfo-ExtIEs} } OPTIONAL, + ... +} + +SpatialRelationInfo-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +SpatialRelationforResourceID ::= SEQUENCE (SIZE(1..maxnoSpatialRelations)) OF SpatialRelationforResourceIDItem + +SpatialRelationforResourceIDItem ::= SEQUENCE { + referenceSignal ReferenceSignal, + iE-Extensions ProtocolExtensionContainer { {SpatialRelationforResourceIDItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +SpatialRelationforResourceIDItem-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +SpatialRelationPerSRSResource ::= SEQUENCE { +``` + +``` + spatialRelationPerSRSResource-List SpatialRelationPerSRSResource-List, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { SpatialRelationPerSRSResource-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +SpatialRelationPerSRSResource-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +SpatialRelationPerSRSResource-List ::= SEQUENCE (SIZE (1.. maxnoSRS-ResourcePerSet)) OF SpatialRelationPerSRSResourceItem +``` + +``` +SpatialRelationPerSRSResourceItem ::= SEQUENCE { +``` + +``` + referenceSignal ReferenceSignal, +``` + +``` + iE-Extensions ProtocolExtensionContainer { {SpatialRelationPerSRSResourceItem-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +SpatialRelationPerSRSResourceItem-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +SpatialRelationPos ::= CHOICE { +``` + +``` + sSBPos SSB, +``` + +``` + pRSInformationPos PRSInformationPos, +``` + +``` + choice-extension ProtocolIE-Single-Container {{ SpatialInformationPos-ExtIEs }} +``` + +``` +} +``` + +``` +SpatialInformationPos-ExtIEs NRPPA-PROTOCOL-IES ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +SRSConfig ::= SEQUENCE { +``` + +``` + sRSResource-List SRSResource-List OPTIONAL, +``` + +``` + posSRSResource-List PosSRSResource-List OPTIONAL, +``` + +``` + sRSResourceSet-List SRSResourceSet-List OPTIONAL, +``` + +``` + posSRSResourceSet-List PosSRSResourceSet-List OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { SRSConfig-ExtIEs } } OPTIONAL, +``` + +``` + ... +``` + +} + +SRSSConfig-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + +... + +} + +SRSCarrier-List ::= SEQUENCE (SIZE(1.. maxnoSRS-Carriers)) OF SRSCarrier-List-Item + +SRSCarrier-List-Item ::= SEQUENCE { + +pointA                                    INTEGER (0..3279165), +uplinkChannelBW-PerSCS-List          UplinkChannelBW-PerSCS-List, +activeULBWP                             ActiveULBWP, +pCI-NR                                    INTEGER (0..1007)          OPTIONAL, + +iE-Extensions                            ProtocolExtensionContainer { { SRSCarrier-List-Item-ExtIEs } } OPTIONAL, + +... + +} + +SRSCarrier-List-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + +... + +} + +SRSSConfiguration ::= SEQUENCE { + +``` + sRSCarrier-List SRSCarrier-List, + iE-Extensions ProtocolExtensionContainer { { SRSConfiguration-ExtIEs } } OPTIONAL, + ... +} + +SRSConfiguration-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +SrsFrequency ::= INTEGER (0..3279165) + +SRSPortIndex ::= ENUMERATED{id1000, id1001, id1002, id1003, ...} + +SRSPosResourceID ::= INTEGER (0..63) + +SRSResource ::= SEQUENCE { + sRSResourceID SRSSResourceID, + nrofSRS-Ports ENUMERATED {port1, ports2, ports4}, + transmissionComb TransmissionComb, + startPosition INTEGER (0..13), + nrofSymbols ENUMERATED {n1, n2, n4}, + repetitionFactor ENUMERATED {n1, n2, n4}, + freqDomainPosition INTEGER (0..67), +} +``` + +``` + +freqDomainShift INTEGER (0..268), +c-SRS INTEGER (0..63), +b-SRS INTEGER (0..3), +b-hop INTEGER (0..3), +groupOrSequenceHopping ENUMERATED { neither, groupHopping, sequenceHopping }, +resourceType ResourceType, +sequenceId INTEGER (0..1023), +iE-Extensions ProtocolExtensionContainer { { SRSResource-ExtIEs } } OPTIONAL, +... +} + +SRSResource-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + { ID id-nrofSymbolsExtended CRITICALITY ignore EXTENSION NrofSymbolsExtended PRESENCE optional}| + { ID id-repetitionFactorExtended CRITICALITY ignore EXTENSION RepetitionFactorExtended PRESENCE optional}| + { ID id-StartRBHopping CRITICALITY ignore EXTENSION StartRBHopping PRESENCE optional}| + { ID id-StartRBIndex CRITICALITY ignore EXTENSION StartRBIndex PRESENCE optional}, + ... +} + +SRSResourceID ::= INTEGER (0..63) + +SRSResource-List ::= SEQUENCE (SIZE (1..maxnoSRS-Resources)) OF SRSResource + +``` + +SRSResourceSet-List ::= SEQUENCE (SIZE (1..maxnoSRS-ResourceSets)) OF SRSResourceSet + +SRSResourceID-List ::= SEQUENCE (SIZE (1..maxnoSRS-ResourcePerSet)) OF SRSResourceID + +SRSResourceSet ::= SEQUENCE { +    sRSResourceSetID            INTEGER(0..15), +    sRSResourceID-List          SRSResourceID-List, +    resourceSetType             ResourceSetType, +    iE-Extensions              ProtocolExtensionContainer { { SRSResourceSet-ExtIEs } } OPTIONAL, +    ... +} + +SRSResourceSet-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +    ... +} + +SRSResourceSetID ::= INTEGER (0..15, ...) + +SRSResourceTrigger ::= SEQUENCE { +    aperiodicSRSResourceTriggerList         AperiodicSRSResourceTriggerList, +    iE-Extensions          ProtocolExtensionContainer { {SRSResourceTrigger-ExtIEs} } OPTIONAL, +    ... +} + +} + +SRSResourceTrigger-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + +... + +} + +SRSResourcetype ::= SEQUENCE { + +sRSResourceTypeChoice + +sRSResourceTypeChoice, + +iE-Extensions + +ProtocolExtensionContainer { { SRSResourcetype-ExtIEs} } OPTIONAL, + +... + +} + +SRSResourcetype-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + +{ ID id-SRSPortIndex CRITICALITY ignore EXTENSION SRSPortIndex PRESENCE optional}, + +... + +} + +SRSResourceTypeChoice ::= CHOICE { + +sRSResourceInfo + +SRSInfo, + +posSRSResourceInfo + +PosSRSInfo, + +... + +} + +``` +SRSInfo ::= SEQUENCE { + sRSResource SRSResourceID, + ... +} + +SRSTransmissionStatus ::= ENUMERATED {stopped, ...} + +PosSRSInfo ::= SEQUENCE { + posSRSResourceID SRSPosResourceID, + ... +} + +SSBInfo ::= SEQUENCE { + listOfSSBInfo SEQUENCE (SIZE (1..maxNoSSBs)) OF SSBInfoItem, + iE-Extensions ProtocolExtensionContainer { {SSBInfo-ExtIEs} } OPTIONAL, + ... +} + +SSBInfo-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SSBInfoItem ::= SEQUENCE { + sSB-Configuration TF-Configuration, + pCI-NR INTEGER (0..1007), + iE-Extensions ProtocolExtensionContainer { { SSBInfoItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +SSBInfoItem-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SSB ::= SEQUENCE { + pCI-NR INTEGER (0..1007), + ssb-index SSB-Index OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SSB-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +SSB-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +SSBBurstPosition ::= CHOICE { + shortBitmap BIT STRING (SIZE(4)), + mediumBitmap BIT STRING (SIZE(8)), + longBitmap BIT STRING (SIZE(64)), + choice-extension ProtocolIE-Single-Container { { SSBBurstPosition-ExtIEs } } +} + +SSBBurstPosition-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +SSB-Index ::= INTEGER(0..63) + +SSID ::= OCTET STRING (SIZE(1..32)) + +StartRBIndex ::= CHOICE{ + freqScalingFactor2 INTEGER(0..1), +} +``` + +``` + freqScalingFactor4 INTEGER(0..3), + choice-extension ProtocolIE-Single-Container { { StartRBIndex-ExtIEs} } +} + +StartRBIndex-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +StartRBHopping ::= ENUMERATED {enable} + +StartTimeAndDuration ::= SEQUENCE { + startTime RelativeTime1900 OPTIONAL, + duration INTEGER (0..90060, ...) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { StartTimeAndDuration-ExtIEs} } OPTIONAL, + ... +} + +StartTimeAndDuration-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +SystemFrameNumber ::= INTEGER (0..1023) +``` + +``` +SystemInformation ::= SEQUENCE (SIZE (1.. maxNrOfPosSimessage)) OF SEQUENCE { + broadcastPeriodicity BroadcastPeriodicity, + posSIBs PosSIBs, + iE-Extensions ProtocolExtensionContainer { { SystemInformation-ExtIEs} } OPTIONAL, + ... +} + +SystemInformation-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +-- T + +TAC ::= OCTET STRING (SIZE(3)) + +TDD-Config-EUTRA-Item ::= SEQUENCE { + subframeAssignment ENUMERATED { sa0, sa1, sa2, sa3, sa4, sa5, sa6, ... }, + iE-Extensions ProtocolExtensionContainer { { TDD-Config-EUTRA-Item-Item-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +TDD-Config-EUTRA-Item-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +TRPTEGInformation ::= CHOICE { + rxTx-TEG RxTxTEG, + rx-TEG RxTEG, + choice-extension ProtocolIE-Single-Container { { TRPTEGInformation-ExtIEs } } +} + +TRPTEGInformation-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +RxTxTEG ::= SEQUENCE { + tRP-RxTx-TEGInformation TRP-RxTx-TEGInformation, + tRP-Tx-TEGInformation TRP-Tx-TEGInformation OPTIONAL, + iE-extensions ProtocolExtensionContainer { { RxTxTEG-ExtIEs } } OPTIONAL, + ... +} + +RxTxTEG-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +} + +RxTEG ::= SEQUENCE { + tRP-Rx-TEGInformation TRP-Rx-TEGInformation, + tRP-Tx-TEGInformation TRP-Tx-TEGInformation, + iE-extensions ProtocolExtensionContainer { { RxTEG-ExtIEs } } OPTIONAL, + ... +} + +RxTEG-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +TimingErrorMargin ::= ENUMERATED {tc0, tc2, tc4, tc6, tc8, tc12, tc16, tc20, tc24, tc32, tc40, tc48, tc56, tc64, tc72, tc80, ...} + +TF-Configuration ::= SEQUENCE { + sSB-frequency INTEGER (0..3279165), + sSB-subcarrier-spacing ENUMERATED {kHz15, kHz30, kHz120, kHz240, ..., kHz60, kHz480, kHz960}, + -- The value kHz60 is not supported in this version of the specification. + sSB-Transmit-power INTEGER (-60..50), + sSB-periodicity ENUMERATED {ms5, ms10, ms20, ms40, ms80, ms160, ...}, + sSB-half-frame-offset INTEGER(0..1), + sSB-SFN-offset INTEGER(0..15), +} +``` + +``` + sSB-BurstPosition SSBBurstPosition OPTIONAL, + sFN-initialisation-time RelativeTime1900 OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { TF-Configuration-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +TF-Configuration-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +TimeStamp ::= SEQUENCE { + systemFrameNumber SystemFrameNumber, + slotIndex TimeStampSlotIndex, + measurementTime RelativeTime1900 OPTIONAL, + iE-Extension ProtocolExtensionContainer { { TimeStamp-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +TimeStamp-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +TimeStampSlotIndex ::= CHOICE { + sCS-15 INTEGER(0..9), + sCS-30 INTEGER(0..19), + sCS-60 INTEGER(0..39), + sCS-120 INTEGER(0..79), + choice-extension ProtocolIE-Single-Container { { TimeStampSlotIndex-ExtIEs } } +} +``` + +``` +TimeStampSlotIndex-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} +``` + +``` +TP-ID-EUTRA ::= INTEGER (0..4095, ...) +``` + +``` +TP-Type-EUTRA ::= ENUMERATED { prs-only-tp, ... } +``` + +``` +TransmissionComb ::= CHOICE { + n2 SEQUENCE { + combOffset-n2 INTEGER (0..1), + cyclicShift-n2 INTEGER (0..7) + }, +} +``` + +``` +n4 SEQUENCE { + combOffset-n4 INTEGER (0..3), + cyclicShift-n4 INTEGER (0..11) + }, + choice-extension ProtocolIE-Single-Container { { TransmissionComb-ExtIEs } } +} + +TransmissionComb-ExtIEs NRPPA-PROTOCOL-IES ::= { + { ID id-transmissionCombn8 CRITICALITY reject TYPE TransmissionCombn8 PRESENCE mandatory }, + ... +} + +TransmissionCombn8 ::= SEQUENCE { + combOffset-n8 INTEGER (0..7), + cyclicShift-n8 INTEGER (0..5), + iE-Extensions ProtocolExtensionContainer { { TransmissionCombn8-ExtIEs } } OPTIONAL +} + +TransmissionCombn8-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +TransmissionCombPos ::= CHOICE { +``` + +``` +n2 SEQUENCE { + combOffset-n2 INTEGER (0..1), + cyclicShift-n2 INTEGER (0..7) + }, +n4 SEQUENCE { + combOffset-n4 INTEGER (0..3), + cyclicShift-n4 INTEGER (0..11) + }, +n8 SEQUENCE { + combOffset-n8 INTEGER (0..7), + cyclicShift-n8 INTEGER (0..5) + }, + + choice-extension ProtocolIE-Single-Container { { TransmissionCombPos-ExtIEs } } +} + +TransmissionCombPos-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +TRPBeamAntennaInformation ::= SEQUENCE { + choice-TRP-Beam-Antenna-Info-Item Choice-TRP-Beam-Antenna-Info-Item, + iE-Extensions ProtocolExtensionContainer {{ TRPBeamAntennaInformation-ExtIEs}} OPTIONAL, + ... +} +``` + +``` +} + +TRPBeamAntennaInformation-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +Choice-TRP-Beam-Antenna-Info-Item ::= CHOICE { + reference TRP-ID, + explicit TRP-BeamAntennaExplicitInformation, + noChange NULL, + choice-extension ProtocolIE-Single-Container { { Choice-TRP-Beam-Info-Item-ExtIEs } } +} + +Choice-TRP-Beam-Info-Item-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +TRP-BeamAntennaExplicitInformation ::= SEQUENCE { + trp-BeamAntennaAngles TRP-BeamAntennaAngles, + lcs-to-gcs-translation LCS-to-GCS-Translation OPTIONAL, + iE-Extensions ProtocolExtensionContainer {{ TRP-BeamAntennaExplicitInformation-ExtIEs}} OPTIONAL, + ... +} +``` + +``` +TRP-BeamAntennaExplicitInformation-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +TRP-BeamAntennaAngles ::= SEQUENCE (SIZE (1.. maxnoAzimuthAngles)) OF TRP-BeamAntennaAnglesList-Item + +TRP-BeamAntennaAnglesList-Item ::= SEQUENCE { + trp-azimuth-angle INTEGER (0..359), + trp-azimuth-angle-fine INTEGER (0..9) OPTIONAL, + trp-elevation-angle-list SEQUENCE (SIZE (1.. maxnoElevationAngles)) OF TRP-ElevationAngleList-Item, + iE-Extensions ProtocolExtensionContainer {{ TRP-BeamAntennaAnglesList-Item-ExtIEs}} OPTIONAL, + ... +} + +TRP-BeamAntennaAnglesList-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +TRP-ElevationAngleList-Item ::= SEQUENCE { + trp-elevation-angle INTEGER (0..180), + trp-elevation-angle-fine INTEGER (0..9) OPTIONAL, + trp-beam-power-list SEQUENCE (SIZE (2..maxNumResourcesPerAngle)) OF TRP-Beam-Power-Item, +``` + +``` + iE-Extensions ProtocolExtensionContainer {{ TRP-ElevationAngleList-Item-ExtIEs}} OPTIONAL, + ... +} + +TRP-ElevationAngleList-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +TRP-Beam-Power-Item ::= SEQUENCE { + pRSResourceSetID PRS-Resource-Set-ID OPTIONAL, + pRSResourceID PRS-Resource-ID, + relativePower INTEGER (0..30), --negative value + relativePowerFine INTEGER (0..9) OPTIONAL, --negative value + iE-Extensions ProtocolExtensionContainer {{ TRP-Beam-Power-Item-ExtIEs}} OPTIONAL, + ... +} + +TRP-Beam-Power-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +TRPMeasurementQuantities ::= SEQUENCE (SIZE (1..maxnoPosMeas)) OF TRPMeasurementQuantitiesList-Item +``` + +``` +TRPMeasurementQuantitiesList-Item ::= SEQUENCE { + tRPMeasurementQuantities-Item TRPMeasurementQuantities-Item, + timingReportingGranularityFactor INTEGER (0..5) OPTIONAL, + iE-Extensions ProtocolExtensionContainer {{ TRPMeasurementQuantitiesList-Item-ExtIEs}} OPTIONAL, + ... +} + +TRPMeasurementQuantitiesList-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +TRPMeasurementQuantities-Item ::= ENUMERATED { + gNB-RxTxTimeDiff, + uL-SRS-RSRP, + uL-AoA, + uL-RTOA, + ..., + multiple-UL-AoA, + uL-SRS-RSRPP +} + +TrpMeasurementResult ::= SEQUENCE (SIZE (1.. maxnoPosMeas)) OF TrpMeasurementResultItem + +TrpMeasurementResultItem ::= SEQUENCE { +``` + +``` + measuredResultsValue TrpMeasuredResultsValue, + timeStamp Timestamp, + measurementQuality TrpMeasurementQuality OPTIONAL, + measurementBeamInfo MeasurementBeamInfo OPTIONAL, + iE-Extensions ProtocolExtensionContainer {{TrpMeasurementResultItem-ExtIEs}} OPTIONAL, + ... +} + +TrpMeasurementResultItem-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + { ID id-SRSResourcetype CRITICALITY ignore EXTENSION SRSResourcetype PRESENCE optional}| + { ID id-ARP-ID CRITICALITY ignore EXTENSION ARP-ID PRESENCE optional}| + { ID id-LoS-NLoSInformation CRITICALITY ignore EXTENSION LoS-NLoSInformation PRESENCE optional }| + { ID id-Mobile-TRP-LocationInformation CRITICALITY ignore EXTENSION Mobile-TRP-LocationInformation PRESENCE optional }, + ... +} + +TrpMeasuredResultsValue ::= CHOICE { + uL-AngleOfArrival UL-AoA, + uL-SRS-RSRP UL-SRS-RSRP, + uL-RTOA UL-RTOAMeasurement, + gNB-RxTxTimeDiff GNB-RxTxTimeDiff, + choice-extension ProtocolIE-Single-Container { { TrpMeasuredResultsValue-ExtIEs } } +} +``` + +``` +TrpMeasuredResultsValue-ExtIEs NRPPA-PROTOCOL-IES ::= { + { ID id-ZoA CRITICALITY reject TYPE ZoA PRESENCE mandatory}| + { ID id-MultipleULAoA CRITICALITY reject TYPE MultipleULAoA PRESENCE mandatory}| + { ID id-UL-SRS-RSRPP CRITICALITY reject TYPE UL-SRS-RSRPP PRESENCE mandatory}, + ... +} + +TrpMeasurementQuality ::= CHOICE { + timingMeasQuality TrpMeasurementTimingQuality, + angleMeasQuality TrpMeasurementAngleQuality, + choice-Extension ProtocolIE-Single-Container {{ TrpMeasurementQuality-ExtIEs}} +} + +TrpMeasurementQuality-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +TrpMeasurementTimingQuality ::= SEQUENCE { + measurementQuality INTEGER (0..31), + resolution ENUMERATED {m0dot1, m1, m10, m30, ...}, + iE-extensions ProtocolExtensionContainer { { TrpMeasurementTimingQuality-ExtIEs } } OPTIONAL, +``` + +``` +... +} + +TrpMeasurementTimingQuality-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +TrpMeasurementAngleQuality ::= SEQUENCE { + azimuthQuality INTEGER (0..255), + zenithQuality INTEGER (0..255) OPTIONAL, + resolution ENUMERATED {deg0dot1, ...}, + iE-extensions ProtocolExtensionContainer { { TrpMeasurementAngleQuality-ExtIEs } } OPTIONAL, + ... +} + +TrpMeasurementAngleQuality-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +TRP-MeasurementRequestList ::= SEQUENCE (SIZE (1..maxNoOfMeasTRPs)) OF TRP-MeasurementRequestItem + +TRP-MeasurementRequestItem ::= SEQUENCE { + tRP-ID TRP-ID, +``` + +``` + search-window-information Search-window-information OPTIONAL, + iE-extensions ProtocolExtensionContainer { { TRP-MeasurementRequestItem-ExtIEs } } OPTIONAL, + ... +} + +TRP-MeasurementRequestItem-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + { ID id-Cell-ID CRITICALITY ignore EXTENSION CGI-NR PRESENCE optional }| + { ID id-AoA-SearchWindow CRITICALITY ignore EXTENSION AoA-AssistanceInfo PRESENCE optional }| + { ID id-NumberOfTRPRxTEG CRITICALITY ignore EXTENSION NumberOfTRPRxTEG PRESENCE optional }| + { ID id-NumberOfTRPTxTEG CRITICALITY ignore EXTENSION NumberOfTRPTxTEG PRESENCE optional }, + ... +} + +TRP-MeasurementResponseList ::= SEQUENCE (SIZE (1..maxNoOfMeasTRPs)) OF TRP-MeasurementResponseItem + +TRP-MeasurementResponseItem ::= SEQUENCE { + tRP-ID TRP-ID, + measurementResult TrpMeasurementResult, + iE-extensions ProtocolExtensionContainer { { TRP-MeasurementResponseItem-ExtIEs } } OPTIONAL, + ... +} + +TRP-MeasurementResponseItem-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` +{ ID id-Cell-ID CRITICALITY ignore EXTENSION CGI-NR PRESENCE optional }, +... +} + +TRP-MeasurementUpdateList ::= SEQUENCE (SIZE (1..maxNoOfMeasTRPs)) OF TRP-MeasurementUpdateItem + +TRP-MeasurementUpdateItem ::= SEQUENCE { + tRP-ID TRP-ID, + aoA-window-information AoA-AssistanceInfo OPTIONAL, + iE-extensions ProtocolExtensionContainer { { TRP-MeasurementUpdateItem-ExtIEs } } OPTIONAL, + ... +} + +TRP-MeasurementUpdateItem-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + { ID id-NumberOfTRPRxTEG CRITICALITY ignore EXTENSION NumberOfTRPRxTEG PRESENCE optional } | + { ID id-NumberOfTRPRxTxTEG CRITICALITY ignore EXTENSION NumberOfTRPRxTxTEG PRESENCE optional }, + ... +} + +TRPInformationListTRPResp ::= SEQUENCE (SIZE (1.. maxnoTRPs)) OF SEQUENCE { + tRPInformation TRPInformation, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { TRPInformationTRPResp-ExtIEs } } OPTIONAL, + ... +} + +TRPInformationTRPResp-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +TRPInformation ::= SEQUENCE { + tRP-ID TRP-ID, + tRPInformationTypeResponseList TRPInformationTypeResponseList, + iE-Extensions ProtocolExtensionContainer { { TRPInformation-ExtIEs } } OPTIONAL, + ... +} + +TRPInformation-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + { ID id-Mobile-IAB-MT-UE-ID CRITICALITY reject EXTENSION Mobile-IAB-MT-UE-ID PRESENCE optional }, + --This IE shall be present if the TRP type IE is set to the value "mobile trp" + ... +} + +TRPInformationTypeResponseList ::= SEQUENCE (SIZE (1..maxnoTRPInfoTypes)) OF TRPInformationTypeResponseItem +``` + +``` +TRPInformationTypeResponseItem ::= CHOICE { + pCI-NR INTEGER (0..1007), + cGI-NR CGI-NR, + aRFCN INTEGER (0..3279165), + pRSConfiguration PRSConfiguration, + sSBInformation SSBInfo, + sFNInitialisationTime RelativeTime1900, + spatialDirectionInformation SpatialDirectionInformation, + geographicalCoordinates GeographicalCoordinates, + choice-extension ProtocolIE-Single-Container { { TRPInformationTypeResponseItem-ExtIEs } } +} +``` + +``` +TRPInformationTypeResponseItem-ExtIEs NRPPA-PROTOCOL-IES ::= { + { ID id-TRPTType CRITICALITY reject TYPE TRPTType PRESENCE mandatory }| + { ID id-OnDemandPRS CRITICALITY reject TYPE OnDemandPRS-Info PRESENCE mandatory}| + { ID id-TRPTxTEGAssociation CRITICALITY reject TYPE TRPTxTEGAssociation PRESENCE mandatory}| + { ID id-TRPBeamAntennaInformation CRITICALITY reject TYPE TRPBeamAntennaInformation PRESENCE mandatory }| + { ID id-Mobile-TRP-LocationInformation CRITICALITY reject TYPE Mobile-TRP-LocationInformation PRESENCE mandatory }| + { ID id-CommonTAParameters CRITICALITY reject TYPE CommonTAParameters PRESENCE mandatory }, + ... +} +``` + +``` +TRPInformationTypeListTRPReq ::= SEQUENCE (SIZE(1.. maxnoTRPInfoTypes)) OF ProtocolIE-Single-Container { {TRPInformationTypeItemTRPReq} } +``` + +``` +TRPInformationTypeItemTRPReq NRPPA-PROTOCOL-IES ::= { +``` + +``` + { ID id-TRPInformationTypeItem CRITICALITY reject TYPE TRPInformationTypeItem PRESENCE mandatory }, +``` + +``` + ... +``` + +``` +} +``` + +``` +TRPInformationTypeItem ::= ENUMERATED { +``` + +``` + nrPCI, +``` + +``` + nG-RAN-CGI, +``` + +``` + arfcn, +``` + +``` + pRSConfig, +``` + +``` + sSBInfo, +``` + +``` + sFNInitTime, +``` + +``` + spatialDirectInfo, +``` + +``` + geoCoord, +``` + +``` + ..., +``` + +``` + trp-type, +``` + +``` + ondemandPRSInfo, +``` + +``` + trpTxTeg, +``` + +``` + beam-antenna-info, +``` + +``` + mobile-trp-location-info, + commonTA +} + +TRPList ::= SEQUENCE (SIZE(1.. maxnoTRPs)) OF TRPItem + +TRPItem ::= SEQUENCE { + tRP-ID TRP-ID, + iE-Extensions ProtocolExtensionContainer { {TRPItem-ExtIEs} } OPTIONAL, + ... +} + +TRPItem-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +TRP-ID ::= INTEGER (1.. maxnoTRPs, ...) + +TRPPositionDefinitionType ::= CHOICE { + direct TRPPositionDirect, + referenced TRPPositionReferenced, + choice-extension ProtocolIE-Single-Container { { TRPPositionDefinitionType-ExtIEs } } +``` + +} + +TRPPositionDefinitionType-ExtIEs NRPPA-PROTOCOL-IES ::= { + +... + +} + +TRPPositionDirect ::= SEQUENCE { + +accuracy TRPPositionDirectAccuracy, + +iE-extensions ProtocolExtensionContainer { { TRPPositionDirect-ExtIEs } } OPTIONAL, + +... + +} + +TRPPositionDirect-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + +... + +} + +TRPPositionDirectAccuracy ::= CHOICE { + +tRPPosition NG-RANAccessPointPosition , + +tRPHAPosition NGRANHighAccuracyAccessPointPosition , + +choice-extension ProtocolIE-Single-Container { { TRPPositionDirectAccuracy-ExtIEs } } + +} + +TRPPositionDirectAccuracy-ExtIEs NRPPA-PROTOCOL-IES ::= { + +... + +} + +TRPPositionReferenced ::= SEQUENCE { + +referencePoint ReferencePoint, + +referencePointType TRPReferencePointType, + +iE-extensions ProtocolExtensionContainer { { TRPPositionReferenced-ExtIEs } } OPTIONAL, + +... + +} + +TRPPositionReferenced-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + +... + +} + +TRP-PRS-Information-List ::= SEQUENCE (SIZE(1.. maxnoPRSTRPs)) OF TRP-PRS-Information-List-Item + +TRP-PRS-Information-List-Item ::= SEQUENCE { + +tRP-ID TRP-ID, + +nR-PCI NR-PCI, + +cGI-NR CGI-NR OPTIONAL, + +pRSConfiguration PRSConfiguration, + +``` + iE-Extensions ProtocolExtensionContainer { { TRP-PRS-Information-List-Item-ExtIEs } } OPTIONAL, + ... +} + +TRP-PRS-Information-List-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +TRPReferencePointType ::= CHOICE { + tRPPositionRelativeGeodetic RelativeGeodeticLocation, + tRPPositionRelativeCartesian RelativeCartesianLocation, + choice-extension ProtocolIE-Single-Container { { TRPReferencePointType-ExtIEs } } +} + +TRPReferencePointType-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +TRP-Rx-TEGInformation ::= SEQUENCE { + tRP-Rx-TEGID INTEGER (0..31), + tRP-Rx-TimingErrorMargin TimingErrorMargin, + iE-Extensions ProtocolExtensionContainer { { TRP-Rx-TEGInformation-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +} +``` + +``` +TRP-Rx-TEGInformation-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +TRP-RxTx-TEGInformation ::= SEQUENCE { +``` + +``` + tRP-RxTx-TEGID INTEGER (0..255), +``` + +``` + tRP-RxTx-TimingErrorMargin RxTxTimingErrorMargin, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { TRP-RxTx-TEGInformation-ExtIEs } } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +TRP-RxTx-TEGInformation-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +TRP-Tx-TEGInformation ::= SEQUENCE { +``` + +``` + tRP-Tx-TEGID INTEGER (0..7), +``` + +``` + tRP-Tx-TimingErrorMargin TimingErrorMargin, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { TRP-Tx-TEGInformation-ExtIEs } } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +TRP-Tx-TEGInformation-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +TRPTxTEGAssociation ::= SEQUENCE (SIZE(1.. maxnoTRPTEGs)) OF TRPTEGItem + +TRPTEGItem ::= SEQUENCE { + tRP-Tx-TEGInformation TRP-Tx-TEGInformation, + dl-PRSResourceSetID PRS-Resource-Set-ID, + dl-PRSResourceID-List SEQUENCE (SIZE(1.. maxPRS-ResourcesPerSet)) OF DLPRSResourceID-Item OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { TRPTEGItem-ExtIEs } } OPTIONAL, + ... +} + +TRPTEGItem-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +DLPRSResourceID-Item ::= SEQUENCE { + dl-PRSResourceID PRS-Resource-ID, + iE-Extensions ProtocolExtensionContainer { { DLPRSResource-Item-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +} +``` + +``` +DLPRSResource-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +TRPType ::= ENUMERATED { +``` + +``` + prsOnlyTP, +``` + +``` + srsOnlyRP, +``` + +``` + tp, +``` + +``` + rp, +``` + +``` + trp, +``` + +``` + ... +``` + +``` + mobile-trp +``` + +``` +} +``` + +``` +TypeOfError ::= ENUMERATED { +``` + +``` + not-understood, +``` + +``` + missing, +``` + +``` + ... +``` + +``` +} +``` + +-- U + +UARFCN ::= INTEGER (0..16383, ...) + +UE-Measurement-ID ::= INTEGER (1..15, ..., 16..256) + +UEReportingInformation ::= SEQUENCE { + reportingAmount ENUMERATED {ma0, ma1, ma2, ma4, ma8, ma16, ma32, ma64}, + reportingInterval ENUMERATED {none, one, two, four, eight, ten, sixteen, twenty, thirty-two, sixty-four, ...}, + iE-extensions ProtocolExtensionContainer { { UEReportingInformation-ExtIEs } } OPTIONAL, + ... +} + +UEReportingInformation-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +UE-TEG-ReportingPeriodicity ::= ENUMERATED { + ms160, + ms320, + ms1280, + ms2560, + ms61440, +} + +``` + ms81920, + ms368640, + ms737280, + ... +} + +UETxTEGAssociationList ::= SEQUENCE (SIZE(1.. maxnoUETEGs)) OF UETxTEGAssociationItem + +UETxTEGAssociationItem ::= SEQUENCE { + uE-Tx-TEG-ID INTEGER (0..7), + posSRSResourceID-List PosSRSResourceID-List, + timeStamp Timestamp, + carrierFreq CarrierFreq OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UETxTEGAssociationItem-ExtIEs } } OPTIONAL, + ... +} + +UETxTEGAssociationItem-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + { ID id-UETxTimingErrorMargin CRITICALITY ignore EXTENSION TimingErrorMargin PRESENCE optional }, + ... +} + +SRSResourceID-Item ::= SEQUENCE { +``` + +``` + sRSResourceID SRSResourceID, + iE-Extensions ProtocolExtensionContainer { { SRSResourceID-Item-ExtIEs } } OPTIONAL, + ... + } + + SRSResourceID-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... + } + + UE-TEG-Info-Request ::= ENUMERATED {onDemand, periodic, stop, ...} + + UTRA-EcN0 ::= INTEGER (0..49, ...) + + UTRA-RSCP ::= INTEGER (-5..91, ...) + + UL-AoA ::= SEQUENCE { + azimuthAoA INTEGER (0..3599), + zenithAoA INTEGER (0..1799) OPTIONAL, + LCS-to-GCS-Translation LCS-to-GCS-Translation OPTIONAL, + iE-extensions ProtocolExtensionContainer { { UL-AoA-ExtIEs } } OPTIONAL, + ... + } +``` + +``` +UL-AoA-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +UL-RTOAMeasurement ::= SEQUENCE { +``` + +``` + uLRTOMEas ULRTOMEas, +``` + +``` + additionalPathList AdditionalPathList OPTIONAL, +``` + +``` + iE-extensions ProtocolExtensionContainer { { UL-RTOAMeasurement-ExtIEs } } OPTIONAL, ... +``` + +``` +} +``` + +``` +UL-RTOAMeasurement-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { +``` + +``` + { ID id-ExtendedAdditionalPathList CRITICALITY ignore EXTENSION ExtendedAdditionalPathList PRESENCE optional} | +``` + +``` + { ID id-TRP-Rx-TEGInformation CRITICALITY ignore EXTENSION TRP-Rx-TEGInformation PRESENCE optional}, +``` + +``` + ... +``` + +``` +} +``` + +``` +ULRTOMEas ::= CHOICE { +``` + +``` + k0 INTEGER (0.. 1970049), +``` + +``` + k1 INTEGER (0.. 985025), +``` + +``` + k2 INTEGER (0.. 492513), +``` + +``` + k3 INTEGER (0.. 246257), +``` + +``` +k4 INTEGER (0.. 123129), +k5 INTEGER (0.. 61565), +choice-extension ProtocolIE-Single-Container { { ULRTOAMeas-ExtIEs } } +} + +ULRTOAMeas-ExtIEs NRPPA-PROTOCOL-IES ::= { + ... +} + +UL-SRS-RSRP ::= INTEGER (0..126) + +UL-SRS-RSRPP ::= SEQUENCE { + firstPathRSRPP INTEGER (0..126), + iE-extensions ProtocolExtensionContainer { { UL-SRS-RSRPP-ExtIEs } } OPTIONAL, + ... +} + +UL-SRS-RSRPP-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +UplinkChannelBW-PerSCS-List ::= SEQUENCE (SIZE (1..maxnoSCSs)) OF SCS-SpecificCarrier +``` + +Uncertainty-range-AoA ::= INTEGER (0..3599) + +Uncertainty-range-ZoA ::= INTEGER (0..1799) + +-- V + +ValueRSRP-EUTRA ::= INTEGER (0..97, ...) + +ValueRSRQ-EUTRA ::= INTEGER (0..34, ...) + +ValueRSRP-NR ::= INTEGER (0..127) + +ValueRSRQ-NR ::= INTEGER (0..127) + +-- W + +WLANMeasurementQuantities ::= SEQUENCE (SIZE (0.. maxNoMeas)) OF ProtocolIE-Single-Container { {WLANMeasurementQuantities-ItemIEs} } + +WLANMeasurementQuantities-ItemIEs NRPPA-PROTOCOL-IES ::= { + +{ ID id-WLANMeasurementQuantities-Item CRITICALITY reject TYPE WLANMeasurementQuantities-Item PRESENCE mandatory}} + +``` +WLANMeasurementQuantities-Item ::= SEQUENCE { + wlanMeasurementQuantitiesValue WLANMeasurementQuantitiesValue, + iE-Extensions ProtocolExtensionContainer { { WLANMeasurementQuantitiesValue-ExtIEs} } OPTIONAL, + ... +} + +WLANMeasurementQuantitiesValue-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +WLANMeasurementQuantitiesValue ::= ENUMERATED { + wlan, + ... +} + +WLANMeasurementResult ::= SEQUENCE (SIZE (1..maxNoMeas)) OF WLANMeasurementResult-Item + +WLANMeasurementResult-Item ::= SEQUENCE { + wlan-RSSI WLAN-RSSI, + sSID SSID OPTIONAL, + bSSID BSSID OPTIONAL, + hESSID HESSID OPTIONAL, + operatingClass WLANOperatingClass OPTIONAL, +``` + +``` + countryCode WLANCountryCode OPTIONAL, + wLANChannelList WLANChannelList OPTIONAL, + wLANBand WLANBand OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { WLANMeasurementResult-Item-ExtIEs } } OPTIONAL, + ... +} + +WLANMeasurementResult-Item-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} + +WLAN-RSSI ::= INTEGER (0..141, ...) + +WLANBand ::= ENUMERATED {band2dot4, band5, ...} + +WLANChannelList ::= SEQUENCE (SIZE (1..maxWLANchannels)) OF WLANChannel + +WLANChannel ::= INTEGER (0..255) + +WLANCountryCode ::= ENUMERATED { + unitedStates, + europe, + japan, +``` + +``` +global, +... +} + +WLANOperatingClass ::= INTEGER (0..255) + +-- X + +-- Y + +-- Z + +ZoA ::= SEQUENCE { + zenithAoA INTEGER (0..1799), + LCS-to-GCS-Translation LCS-to-GCS-Translation OPTIONAL, + iE-extensions ProtocolExtensionContainer { { ZoA-ExtIEs } } OPTIONAL, + ... +} + +ZoA-ExtIEs NRPPA-PROTOCOL-EXTENSION ::= { + ... +} +``` + +END + +-- ASN1STOP + +### 9.3.6 Common definitions + +-- ASN1START + +-- \*\*\*\*\* + +-- + +-- Common definitions + +-- + +-- \*\*\*\*\* + +NRPPA-CommonDataTypes { + +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + +ngran-access (22) modules (3) nrppa (4) version1 (1) nrppa-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 } + +NRPPATransactionID ::= INTEGER (0..32767) + +Presence ::= ENUMERATED { optional, conditional, mandatory } + +PrivateIE-ID ::= CHOICE { + local INTEGER (0.. maxPrivateIEs), + global OBJECT IDENTIFIER +``` + +``` + +} + +ProcedureCode ::= INTEGER (0..255) + +ProtocolIE-ID ::= INTEGER (0..maxProtocolIEs) + +TriggeringMessage ::= ENUMERATED { initiating-message, successful-outcome, unsuccessful-outcome} + +END + +-- ASN1STOP + +``` + +### 9.3.7 Constant definitions + +``` + +-- ASN1START + +-- ***** + +-- + +-- Constant definitions + +-- + +-- ***** + +NRPPA-Constants { + + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + + ngran-access (22) modules (3) nrppa (4) version1 (1) nrppa-Constants (4) } + +``` + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + +ProcedureCode, + +ProtocolIE-ID + +FROM NRPPA-CommonDataTypes; + +-- \*\*\*\*\* + +-- + +-- Elementary Procedures + +-- + +-- \*\*\*\*\* + +| | | +|--------------------------------------|---------------------| +| id-errorIndication | ProcedureCode ::= 0 | +| id-privateMessage | ProcedureCode ::= 1 | +| id-e-CIDMeasurementInitiation | ProcedureCode ::= 2 | +| id-e-CIDMeasurementFailureIndication | ProcedureCode ::= 3 | +| id-e-CIDMeasurementReport | ProcedureCode ::= 4 | +| id-e-CIDMeasurementTermination | ProcedureCode ::= 5 | +| id-oTDOAInformationExchange | ProcedureCode ::= 6 | + +``` + +id-assistanceInformationControl ProcedureCode ::= 7 +id-assistanceInformationFeedback ProcedureCode ::= 8 +id-positioningInformationExchange ProcedureCode ::= 9 +id-positioningInformationUpdate ProcedureCode ::= 10 +id-Measurement ProcedureCode ::= 11 +id-MeasurementReport ProcedureCode ::= 12 +id-MeasurementUpdate ProcedureCode ::= 13 +id-MeasurementAbort ProcedureCode ::= 14 +id-MeasurementFailureIndication ProcedureCode ::= 15 +id-tRPInformationExchange ProcedureCode ::= 16 +id-positioningActivation ProcedureCode ::= 17 +id-positioningDeactivation ProcedureCode ::= 18 +id-pRSConfigurationExchange ProcedureCode ::= 19 +id-measurementPreconfiguration ProcedureCode ::= 20 +id-measurementActivation ProcedureCode ::= 21 + +``` + +``` + +-- ***** +-- +-- Lists +-- +-- ***** + +``` + +``` + +maxNrOfErrors INTEGER ::= 256 + +``` + +| | | +|---------------------------------|-------------------| +| maxCellinRANnode | INTEGER ::= 3840 | +| maxIndexesReport | INTEGER ::= 64 | +| maxNoMeas | INTEGER ::= 64 | +| maxCellReport | INTEGER ::= 9 | +| maxCellReportNR | INTEGER ::= 9 | +| maxnoOTDOAtypes | INTEGER ::= 63 | +| maxServCell | INTEGER ::= 5 | +| maxEUTRAmeas | INTEGER ::= 8 | +| maxGERANmeas | INTEGER ::= 8 | +| maxNRmeas | INTEGER ::= 8 | +| maxUTRANmeas | INTEGER ::= 8 | +| maxWLANchannels | INTEGER ::= 16 | +| maxnoFreqHoppingBandsMinusOne | INTEGER ::= 7 | +| maxNoPath | INTEGER ::= 2 | +| maxNrOfPosSImessage | INTEGER ::= 32 | +| maxnoAssistInfoFailureListItems | INTEGER ::= 32 | +| maxNrOfSegments | INTEGER ::= 64 | +| maxNrOfPosSIBs | INTEGER ::= 32 | +| maxNoOfMeasTRPs | INTEGER ::= 64 | +| maxnoTRPs | INTEGER ::= 65535 | +| maxnoTRPInfoTypes | INTEGER ::= 64 | +| maxnoofAngleInfo | INTEGER ::= 65535 | +| maxnolcs-gcs-translation | INTEGER ::= 3 | + +maxnoBcastCell INTEGER ::= 16384 +maxnoSRSTriggerStates INTEGER ::= 3 +maxnoSpatialRelations INTEGER ::= 64 +maxnoPosMeas INTEGER ::= 16384 +maxnoSRS-Carriers INTEGER ::= 32 +maxnoSCSs INTEGER ::= 5 +maxnoSRS-Resources INTEGER ::= 64 +maxnoSRS-PosResources INTEGER ::= 64 +maxnoSRS-ResourceSets INTEGER ::= 16 +maxnoSRS-ResourcePerSet INTEGER ::= 16 +maxnoSRS-PosResourceSets INTEGER ::= 16 +maxnoSRS-PosResourcePerSet INTEGER ::= 16 +maxPRS-ResourceSets INTEGER ::= 2 +maxPRS-ResourcesPerSet INTEGER ::= 64 +maxNoSSBs INTEGER ::= 255 +maxnoofPRSresourceSet INTEGER ::= 8 +maxnoofPRSresource INTEGER ::= 64 +maxnoofULAoAs INTEGER ::= 8 +maxNoPathExtended INTEGER ::= 8 +maxnoARPs INTEGER ::= 16 +maxnoUETEGs INTEGER ::= 256 +maxnoTRPTEGs INTEGER ::= 8 +maxFreqLayers INTEGER ::= 4 + +``` + +maxNumResourcesPerAngle INTEGER ::= 24 +maxnoAzimuthAngles INTEGER ::= 3600 +maxnoElevationAngles INTEGER ::= 1801 +maxnoPRSTRPs INTEGER ::= 256 + +``` + +``` + +-- ***** +-- +-- IEs +-- +-- ***** + +``` + +``` + +id-Cause ProtocolIE-ID ::= 0 +id-CriticalityDiagnostics ProtocolIE-ID ::= 1 +id-LMF-UE-Measurement-ID ProtocolIE-ID ::= 2 +id-ReportCharacteristics ProtocolIE-ID ::= 3 +id-MeasurementPeriodicity ProtocolIE-ID ::= 4 +id-MeasurementQuantities ProtocolIE-ID ::= 5 +id-RAN-UE-Measurement-ID ProtocolIE-ID ::= 6 +id-E-CID-MeasurementResult ProtocolIE-ID ::= 7 +id-OTDOACells ProtocolIE-ID ::= 8 +id-OTDOA-Information-Type-Group ProtocolIE-ID ::= 9 + +``` + +| | | +|--------------------------------------------|----------------------| +| id-OTDOA-Information-Type-Item | ProtocolIE-ID ::= 10 | +| id-MeasurementQuantities-Item | ProtocolIE-ID ::= 11 | +| id-RequestedSRSTransmissionCharacteristics | ProtocolIE-ID ::= 12 | +| id-Cell-Portion-ID | ProtocolIE-ID ::= 14 | +| id-OtherRATMeasurementQuantities | ProtocolIE-ID ::= 15 | +| id-OtherRATMeasurementQuantities-Item | ProtocolIE-ID ::= 16 | +| id-OtherRATMeasurementResult | ProtocolIE-ID ::= 17 | +| id-WLANMeasurementQuantities | ProtocolIE-ID ::= 19 | +| id-WLANMeasurementQuantities-Item | ProtocolIE-ID ::= 20 | +| id-WLANMeasurementResult | ProtocolIE-ID ::= 21 | +| id-TDD-Config-EUTRA-Item | ProtocolIE-ID ::= 22 | +| id-Assistance-Information | ProtocolIE-ID ::= 23 | +| id-Broadcast | ProtocolIE-ID ::= 24 | +| id-AssistanceInformationFailureList | ProtocolIE-ID ::= 25 | +| id-SRSConfiguration | ProtocolIE-ID ::= 26 | +| id-MeasurementResult | ProtocolIE-ID ::= 27 | +| id-TRP-ID | ProtocolIE-ID ::= 28 | +| id-TRPInformationTypeListTRPReq | ProtocolIE-ID ::= 29 | +| id-TRPInformationListTRPResp | ProtocolIE-ID ::= 30 | +| id-MeasurementBeamInfoRequest | ProtocolIE-ID ::= 31 | +| id-ResultSS-RSRP | ProtocolIE-ID ::= 32 | +| id-ResultSS-RSRQ | ProtocolIE-ID ::= 33 | +| id-ResultCSI-RSRP | ProtocolIE-ID ::= 34 | + +| | | +|--------------------------------|----------------------| +| id-ResultCSI-RSRQ | ProtocolIE-ID ::= 35 | +| id-AngleOfArrivalNR | ProtocolIE-ID ::= 36 | +| id-GeographicalCoordinates | ProtocolIE-ID ::= 37 | +| id-PositioningBroadcastCells | ProtocolIE-ID ::= 38 | +| id-LMF-Measurement-ID | ProtocolIE-ID ::= 39 | +| id-RAN-Measurement-ID | ProtocolIE-ID ::= 40 | +| id-TRP-MeasurementRequestList | ProtocolIE-ID ::= 41 | +| id-TRP-MeasurementResponseList | ProtocolIE-ID ::= 42 | +| id-TRP-MeasurementReportList | ProtocolIE-ID ::= 43 | +| id-SRSType | ProtocolIE-ID ::= 44 | +| id-ActivationTime | ProtocolIE-ID ::= 45 | +| id-SRSResourceSetID | ProtocolIE-ID ::= 46 | +| id-TRPList | ProtocolIE-ID ::= 47 | +| id-SRSSpatialRelation | ProtocolIE-ID ::= 48 | +| id-SystemFrameNumber | ProtocolIE-ID ::= 49 | +| id-SlotNumber | ProtocolIE-ID ::= 50 | +| id-SRSResourceTrigger | ProtocolIE-ID ::= 51 | +| id-TRPMeasurementQuantities | ProtocolIE-ID ::= 52 | +| id-AbortTransmission | ProtocolIE-ID ::= 53 | +| id-SFNInitialisationTime | ProtocolIE-ID ::= 54 | +| id-ResultNR | ProtocolIE-ID ::= 55 | +| id-ResultEUTRA | ProtocolIE-ID ::= 56 | +| id-TRPInformationTypeItem | ProtocolIE-ID ::= 57 | + +| | | +|-------------------------------------|----------------------| +| id-CGI-NR | ProtocolIE-ID ::= 58 | +| id-SFNInitialisationTime-NR | ProtocolIE-ID ::= 59 | +| id-Cell-ID | ProtocolIE-ID ::= 60 | +| id-SrsFrequency | ProtocolIE-ID ::= 61 | +| id-TRPType | ProtocolIE-ID ::= 62 | +| id-SRSSpatialRelationPerSRSResource | ProtocolIE-ID ::= 63 | +| id-MeasurementPeriodicityExtended | ProtocolIE-ID ::= 64 | +| id-PRS-Resource-ID | ProtocolIE-ID ::= 65 | +| id-PRSTRPList | ProtocolIE-ID ::= 66 | +| id-PRSTransmissionTRPList | ProtocolIE-ID ::= 67 | +| id-OnDemandPRS | ProtocolIE-ID ::= 68 | +| id-AoA-SearchWindow | ProtocolIE-ID ::= 69 | +| id-TRP-MeasurementUpdateList | ProtocolIE-ID ::= 70 | +| id-ZoA | ProtocolIE-ID ::= 71 | +| id-ResponseTime | ProtocolIE-ID ::= 72 | +| id-UEReportingInformation | ProtocolIE-ID ::= 73 | +| id-MultipleULAoA | ProtocolIE-ID ::= 74 | +| id-UL-SRS-RSRP | ProtocolIE-ID ::= 75 | +| id-SRSResourcetype | ProtocolIE-ID ::= 76 | +| id-ExtendedAdditionalPathList | ProtocolIE-ID ::= 77 | +| id-ARPLocationInfo | ProtocolIE-ID ::= 78 | +| id-ARP-ID | ProtocolIE-ID ::= 79 | +| id-LoS-NLoSInformation | ProtocolIE-ID ::= 80 | + +| | | +|-----------------------------------------------|-----------------------| +| id-UETxTEGAssociationList | ProtocolIE-ID ::= 81 | +| id-NumberOfTRPRxTEG | ProtocolIE-ID ::= 82 | +| id-NumberOfTRPRxTxTEG | ProtocolIE-ID ::= 83 | +| id-TRPTxTEGAssociation | ProtocolIE-ID ::= 84 | +| id-TRPTEGInformation | ProtocolIE-ID ::= 85 | +| id-TRP-Rx-TEGInformation | ProtocolIE-ID ::= 86 | +| id-TRP-PRS-Information-List | ProtocolIE-ID ::= 87 | +| id-PRS-Measurements-Info-List | ProtocolIE-ID ::= 88 | +| id-PRSConfigRequestType | ProtocolIE-ID ::= 89 | +| id-UE-TEG-Info-Request | ProtocolIE-ID ::= 90 | +| id-MeasurementTimeOccasion | ProtocolIE-ID ::= 91 | +| id-MeasurementCharacteristicsRequestIndicator | ProtocolIE-ID ::= 92 | +| id-TRPBeamAntennaInformation | ProtocolIE-ID ::= 93 | +| id-NR-TADV | ProtocolIE-ID ::= 94 | +| id-MeasurementAmount | ProtocolIE-ID ::= 95 | +| id-pathPower | ProtocolIE-ID ::= 96 | +| id-PreconfigurationResult | ProtocolIE-ID ::= 97 | +| id-RequestType | ProtocolIE-ID ::= 98 | +| id-UE-TEG-ReportingPeriodicity | ProtocolIE-ID ::= 99 | +| id-SRSPortIndex | ProtocolIE-ID ::= 100 | +| id-procedure-code-101-not-to-be-used | ProtocolIE-ID ::= 101 | +| id-procedure-code-102-not-to-be-used | ProtocolIE-ID ::= 102 | +| id-procedure-code-103-not-to-be-used | ProtocolIE-ID ::= 103 | + +| | | +|-----------------------------------|-----------------------| +| id-UETxTimingErrorMargin | ProtocolIE-ID ::= 104 | +| id-MeasurementPeriodicityNR-AoA | ProtocolIE-ID ::= 105 | +| id-SRSTransmissionStatus | ProtocolIE-ID ::= 106 | +| id-nrofSymbolsExtended | ProtocolIE-ID ::= 107 | +| id-repetitionFactorExtended | ProtocolIE-ID ::= 108 | +| id-StartRBHopping | ProtocolIE-ID ::= 109 | +| id-StartRBIndex | ProtocolIE-ID ::= 110 | +| id-transmissionCombn8 | ProtocolIE-ID ::= 111 | +| id-ExtendedResourceSymbolOffset | ProtocolIE-ID ::= 112 | +| id-NewNR CGI | ProtocolIE-ID ::= 113 | +| id-Mobile-TRP-LocationInformation | ProtocolIE-ID ::= 114 | +| id-Mobile-IAB-MT-UE-ID | ProtocolIE-ID ::= 115 | +| id-MobileAccessPointLocation | ProtocolIE-ID ::= 116 | +| id-CommonTAParameters | ProtocolIE-ID ::= 117 | + +END + +-- ASN1STOP + +## 9.3.8 Container definitions + +-- ASN1START + +``` +-- ***** +-- +-- Container definitions +-- +-- ***** +``` + +``` +NRPPA-Containers { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + ngran-access (22) modules (3) nrppa (4) version1 (1) nrppa-Containers (5)} +``` + +``` +DEFINITIONS AUTOMATIC TAGS ::= +``` + +``` +BEGIN +``` + +``` +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** +``` + +``` +IMPORTS +``` + +``` + maxPrivateIEs, + maxProtocolExtensions, +``` + +``` + +maxProtocolIEs, +Criticality, +Presence, +PrivateIE-ID, +ProtocolIE-ID +FROM NRPPA-CommonDataTypes; + +-- ***** +-- +-- Class Definition for Protocol IEs +-- +-- ***** + +NRPPA-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 +-- +-- ***** + +NRPPA-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 +-- +-- ***** + +NRPPA-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 { NRPPA-PROTOCOL-IES : IEsSetParam} ::= + SEQUENCE (SIZE (0..maxProtocolIEs)) OF + ProtocolIE-Field {{IEsSetParam}} + +``` + +``` + +ProtocolIE-Single-Container { NRPPA-PROTOCOL-IES : IEsSetParam} ::= + ProtocolIE-Field {{IEsSetParam}} + +``` + +``` + +ProtocolIE-Field { NRPPA-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE { + id NRPPA-PROTOCOL-IES.&id ({IEsSetParam}), + criticality NRPPA-PROTOCOL-IES.&criticality ({IEsSetParam}{@id}), + value NRPPA-PROTOCOL-IES.&Value ({IEsSetParam}{@id}) +} + +``` + +``` + +-- ***** +-- +-- Container Lists for Protocol IE Containers +-- +-- ***** + +``` + +``` + +ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, NRPPA-PROTOCOL-IES : IEsSetParam} ::= + SEQUENCE (SIZE (lowerBound..upperBound)) OF + ProtocolIE-Container {{IEsSetParam}} + +``` + +``` + +-- ***** +-- +-- Container for Protocol Extensions +-- +-- ***** + +``` + +``` + +ProtocolExtensionContainer { NRPPA-PROTOCOL-EXTENSION : ExtensionSetParam} ::= + SEQUENCE (SIZE (1..maxProtocolExtensions)) OF + ProtocolExtensionField {{ExtensionSetParam}} + +``` + +``` + +ProtocolExtensionField { NRPPA-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE { + id NRPPA-PROTOCOL-EXTENSION.&id {{ExtensionSetParam}}, + criticality NRPPA-PROTOCOL-EXTENSION.&criticality {{ExtensionSetParam}{@id}}, + extensionValue NRPPA-PROTOCOL-EXTENSION.&Extension {{ExtensionSetParam}{@id}} +} + +``` + +``` + +-- ***** +-- +-- Container for Private IEs +-- +-- ***** + +``` + +``` +PrivateIE-Container { NRPPA-PRIVATE-IES : IEsSetParam} ::= + SEQUENCE (SIZE (1..maxPrivateIEs)) OF + PrivateIE-Field {{IEsSetParam}} + +PrivateIE-Field { NRPPA-PRIVATE-IES : IEsSetParam} ::= SEQUENCE { + id NRPPA-PRIVATE-IES.&id {{IEsSetParam}}, + criticality NRPPA-PRIVATE-IES.&criticality {{IEsSetParam}{@id}}, + value NRPPA-PRIVATE-IES.&Value {{IEsSetParam}{@id}} +} + +END + +-- ASN1STOP +``` + +## 9.4 Message transfer syntax + +NRPPa 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 [6]. + +## 9.5 Timers + +Void. + +--- + +## 10 Handling of unknown, unforeseen and erroneous protocol data + +Section 10 of TS 38.413 [2] is applicable for the purposes of the present document, with the following additions: + +- In case of Abstract Syntax Error, when reporting the *Criticality Diagnostics* IE for not comprehended IE/IE groups or missing IE/IE groups, the *NRPPa Transaction ID* IE shall also be included; +- In case of Logical Error, when reporting the *Criticality Diagnostics* IE, the *NRPPa Transaction ID* IE shall also be included. + +## Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-----------------|-----------|------|-----|-----|----------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-08-23 | RAN3#97 | R3-173238 | | | | TS skeleton agreed | v0.0.0 | +| 2017-08-25 | RAN3#97 | R3-173374 | | | | TS 38.455 V0.1.0 | v0.1.0 | +| 2017-10-18 | RAN3#97bis | R3-173979 | | | | Implemented agreed pCR from R3#97bis | V0.2.0 | +| 2017-12-04 | RAN3#98 | R3-175064 | | | | Implemented agreed pCR from R3#98 | V0.3.0 | +| 2018-01-31 | RAN3 Adhoc 1801 | R3-180658 | | | | Implemented agreed pCR from R3 Adhoc_1801 | V0.5.0 | +| 2018-03-15 | RAN3#99 | R3-181595 | | | | Implemented agreed pCR's from R3#99 | V0.6.0 | +| 2018-05-29 | RAN3#100 | R3-183598 | | | | Implemented agreed pCR's from R3#100 | V0.7.0 | +| 2018-06 | RAN#80 | RP-181147 | | | | Submitted to RAN plenary for Approval | V1.0.0 | +| 2018-06 | RAN#80 | - | - | - | - | Specification approved at TSG-RAN and placed under change control | 15.0.0 | +| 2018-09 | RAN#81 | RP-181921 | 0002 | 1 | F | Rapporteur CR for TS 38.455 | 15.1.0 | +| 2018-12 | RAN#82 | RP-182446 | 0003 | 1 | F | Addition of TDD UL/DL configuration to OTDOA assistance data | 15.2.0 | +| 2019-01 | RAN#82 | | | | | Editorial Corrections:
- 1 editorial correction to ASN.1
- adding "ASN1START" and "ASN1STOP" TAGs to the ASN.1 | 15.2.1 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | +| 2020-09 | SA#89-e | RP-201849 | 0008 | 19 | B | Introduction of NR Positioning in NRPPa | 16.1.0 | +| 2020-12 | RAN#90-e | RP-202315 | 0014 | 2 | A | Support OTDOA assistance data for case of NR serving cell | 16.2.0 | +| 2020-12 | RAN#90-e | RP-202311 | 0015 | 2 | F | Corrections to tabular and asn.1 for NR positioning (NRPPa) | 16.2.0 | +| 2020-12 | RAN#90-e | RP-202311 | 0016 | - | F | Correction of NRPPa positioning procedures | 16.2.0 | +| 2020-12 | RAN#90-e | RP-202311 | 0021 | 1 | F | RRc alignment and various correction including ASN.1 | 16.2.0 | +| 2020-12 | RAN#90-e | RP-202311 | 0022 | 2 | F | Coupling TRP ID and Cell ID in Measurement procedures | 16.2.0 | +| 2021-03 | RAN#91-e | RP-210230 | 0024 | 1 | F | Including SRS frequency information in Positioning Information Request | 16.3.0 | +| 2021-03 | RAN#91-e | RP-210230 | 0025 | 1 | F | Corrections on NRPPa | 16.3.0 | +| 2021-03 | RAN#91-e | RP-210236 | 0026 | - | F | Correction of NRPPa section 10 | 16.3.0 | +| 2021-06 | RAN#92-e | RP-211333 | 0028 | - | A | Clarification of E-CID Measurement Result | 16.4.0 | +| 2021-06 | RAN#92-e | RP-211327 | 0029 | - | F | Correction of Spatial Relation Information | 16.4.0 | +| 2021-06 | RAN#92-e | RP-211327 | 0033 | 1 | F | Correction on SFN Initialisation Time | 16.4.0 | +| 2021-06 | RAN#92-e | RP-211327 | 0034 | - | F | Correction on relative cartesian coordinate | 16.4.0 | +| 2021-09 | RAN#93-e | RP-211883 | 0039 | 1 | F | Correction of the RAN and LMF UE measurement IDs extension | 16.5.0 | +| 2021-09 | RAN#93-e | RP-211883 | 0041 | 1 | F | Adding procedural text for System Frame Number and Slot Number | 16.5.0 | +| 2021-12 | RAN#94-e | RP-213173 | 0047 | 3 | F | Correction on PRS-only TP | 16.6.0 | +| 2021-12 | RAN#94-e | RP-212867 | 0049 | 1 | F | Support of providing spatial relation per SRS resource from LMF to gNB | 16.6.0 | +| 2022-03 | RAN#95-e | RP-220281 | 0052 | 1 | F | Correction on Measurement Periodicity | 16.7.0 | +| 2022-03 | RAN#95-e | RP-220281 | 0053 | 1 | F | Correction on PRS Beam Information | 16.7.0 | +| 2022-03 | RAN#95-e | RP-220228 | 0037 | 8 | B | Introduction of NR Positioning enhancements to NRPPa | 17.0.0 | +| 2022-03 | RAN#95-e | RP-220236 | 0042 | 2 | B | Addition of NR Timing Advance reporting for NR UL E-CID [NRTADV] | 17.0.0 | +| 2022-03 | RAN#95-e | RP-220236 | 0054 | - | D | NRPPa Rapporteur Corrections | 17.0.0 | +| 2022-06 | RAN#96 | RP-221131 | 0057 | 1 | F | NRPPa ASN.1 review for NR Positioning Enhancements | 17.1.0 | +| 2022-06 | RAN#96 | RP-221145 | 0058 | 4 | F | CR to 38.455 on Measurement Amount | 17.1.0 | +| 2022-06 | RAN#96 | RP-221145 | 0062 | 2 | D | Rapporteur Corrections to Rel-17 NRPPa | 17.1.0 | +| 2022-06 | RAN#96 | RP-221131 | 0063 | 4 | F | Positionng corrections for NRPPA | 17.1.0 | + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-06 | RAN#96 | RP-221131 | 0066 | 1 | F | Corrections to Measurement Pre-configuration Information Transfer | 17.1.0 | +| 2022-06 | RAN#96 | RP-221131 | 0067 | 1 | F | Support for Multiple Measurement Instances | 17.1.0 | +| 2022-06 | RAN#96 | RP-221152 | 0069 | 2 | A | Correction for PRS Muting | 17.1.0 | +| 2022-06 | RAN#96 | RP-221152 | 0074 | | A | Correction to SSB subcarrier spacing | 17.1.0 | +| 2022-06 | | | | | | editorial corrections to rename the following asn.1 names as choice extension names
- sRSType-extension -> choice-Extension
- cause-Extension -> choice-Extension
- measuredResultsValue-Extension -> choice-Extension
- nG-RANCell-Extension -> choice-Extension
- oTDOACell-Information-Item-Extension -> choice-Extension
- otherRATMeasuredResultsValue-Extension -> choice-Extension
- pRSMutingConfiguration-EUTRA-Extension -> choice-Extension | 17.1.1 | +| 2022-09 | RAN#97-e | RP-222186 | 0075 | 1 | F | Correction for UE Tx TEG Association | 17.2.0 | +| 2022-09 | RAN#97-e | RP-222186 | 0076 | - | F | Introduction of SRS port index | 17.2.0 | +| 2022-09 | RAN#97-e | RP-222186 | 0077 | 2 | F | Support of timing error margins for TEGs in NRPPa | 17.2.0 | +| 2022-09 | RAN#97-e | RP-222543 | 0079 | 3 | A | CR to 38.455 on E-CID measurement periodicity | 17.2.0 | +| 2022-09 | RAN#97-e | RP-222186 | 0080 | 1 | F | Correction on Measurement Time Occasion | 17.2.0 | +| 2022-12 | RAN#98-e | RP-222886 | 0086 | 2 | F | Correction of TRP TEG | 17.3.0 | +| 2022-12 | RAN#98-e | RP-222886 | 0087 | 1 | F | Correction of Timing Error Margin | 17.3.0 | +| 2022-12 | RAN#98-e | RP-222886 | 0088 | 1 | F | Correction of Positioning Information Transfer function | 17.3.0 | +| 2022-12 | RAN#98-e | RP-222886 | 0089 | 2 | F | Correction to the PRS Measurement configuration procedures | 17.3.0 | +| 2022-12 | RAN#98-e | RP-222887 | 0092 | 1 | A | CR to 38.455 on SRS periodicity | 17.3.0 | +| 2022-12 | RAN#98-e | RP-222886 | 0093 | - | F | Correction on presence of timing error margin for TRP TEGs | 17.3.0 | +| 2023-03 | RAN#99 | RP-230597 | 0099 | 1 | A | Correction for SRS Configuration status in Positioning Information Update | 17.4.0 | +| 2023-03 | RAN#99 | RP-230593 | 0100 | 1 | F | NRPPa corrections of references to RRC | 17.4.0 | +| 2023-06 | RAN#100 | RP-231077 | 0103 | 1 | F | SRS Resource correction on Comb 8, Number of Symbols and Repetition Factor | 17.5.0 | +| 2023-06 | RAN#100 | RP-231077 | 0105 | 1 | F | Subcarrier Spacing correction | 17.5.0 | +| 2023-12 | RAN#102 | RP-233850 | 0116 | - | A | Correction of NR E-CID for OnDemand measurements | 17.6.0 | +| 2023-12 | RAN#102 | RP-233850 | 0118 | - | F | Correction to NRPPa for the misalignment on DL PRS | 17.6.0 | +| 2023-12 | RAN#102 | RP-233834 | 0101 | 9 | B | Support for mobile TRP Location Information | 18.0.0 | +| 2023-12 | RAN#102 | RP-233845 | 0102 | 3 | B | Support 1-symbol PRS [1symbol_PRS] | 18.0.0 | +| 2023-12 | RAN#102 | RP-233845 | 0109 | 3 | B | Support of Inactive Positioning in SDT without UE context relocation case [POS_SDT] | 18.0.0 | +| 2023-12 | RAN#102 | RP-233827 | 0125 | 1 | B | Introduction of Common TA Parameters for NR NTN | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38463/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38463/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a93c4d0bda174b0bd353ced9a4097e6ca326bdc6 --- /dev/null +++ b/marked/Rel-18/38_series/38463/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d26e9e9c68d911ea3ae8a17036e086dca6dc531854441b038d29d927e6239d37 +size 9460 diff --git a/marked/Rel-18/38_series/38463/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38463/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb517812a76318922e54b4c357df11a1cdc1e547 --- /dev/null +++ b/marked/Rel-18/38_series/38463/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db65cd630f0421d5036a81ff427aa366a32d29fee1ef026510f0ff61e84a18ff +size 7229 diff --git a/marked/Rel-18/38_series/38463/raw.md b/marked/Rel-18/38_series/38463/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..99c4100922b1ff43897d6a6a09c3c934b2e41746 --- /dev/null +++ b/marked/Rel-18/38_series/38463/raw.md @@ -0,0 +1,228 @@ + + +# 3GPP TS 38.463 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; 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 '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 to 10 Void ..... 5 + +11 E1 Application Protocol (EIAP)..... 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 + +See TS 37.483 [40]. + +## --- 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] -[39] Void. + +[40] 3GPP TS 37.483: "E1 Application Protocol (E1AP)". + +### --- 3 to 10 Void + +## --- 11 E1 Application Protocol (E1AP) + +See TS 37.483 [40]. + +## --- Annex A (informative): Change History + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-02 | R3 #99 | R3-181309 | - | - | - | Endorsed skeleton | 0.0.0 | +| 2018-03 | R3 #99 | R3-181597 | - | - | - | New version capturing agreements from RAN3#99 | 0.1.0 | +| 2018-04 | R3 #99b | R3-182531 | - | - | - | New version capturing agreements from RAN3#99b | 0.2.0 | +| 2018-05 | R3 #100 | R3-183601 | - | - | - | New version capturing agreements from RAN3#100 | 0.3.0 | +| 2018-06 | RAN#80 | RP-181154 | | | | Submitted to RAN for approval. | 1.0.0 | +| 2018-06 | RAN#80 | - | - | - | - | Specification approved at TSG-RAN and placed under change control | 15.0.0 | +| 2018-09 | RAN#81 | RP-181925 | 0001 | 3 | F | BL CR for TS 38.463 covering agreements from RAN3-AH-1807 and R3-101
Note: CR not based on latest version of the spec. Changes to clause 8.3.2.2 in the CR were implemented in clause 8.3.2.3 in the spec. | 15.1.0 | +| 2018-12 | RAN#82 | RP-182451 | 0002 | 2 | F | NR Corrections (TS 38.463 Baseline CR covering RAN3-101Bis and RAN3-102 agreements) | 15.2.0 | +| 2019-03 | RAN#83 | RP-190560 | 0004 | 2 | F | Correction to Data Forwarding Information IE | 15.3.0 | +| 2019-03 | RAN#83 | RP-190555 | 0005 | 1 | F | Corrections related to Integrity Protection handling at the gNB-CU-UP | 15.3.0 | +| 2019-03 | RAN#83 | RP-190554 | 0007 | 2 | F | Corrections on gNB-CU-UP/gNB-DU-CP Configuration Update | 15.3.0 | +| 2019-03 | RAN#83 | RP-190556 | 0008 | 2 | F | Correction of QoS Flow Mapping Indication | 15.3.0 | +| 2019-03 | RAN#83 | RP-190560 | 0009 | 1 | F | Paging Failure | 15.3.0 | +| 2019-03 | RAN#83 | RP-190560 | 0011 | 1 | F | Release due to pre-emption | 15.3.0 | +| 2019-03 | RAN#83 | RP-190560 | 0013 | - | F | Transaction ID in Error Indication procedure | 15.3.0 | +| 2019-03 | RAN#83 | RP-190560 | 0017 | 1 | F | CR to TS 38.463 on inactivity timer over E1 | 15.3.0 | +| 2019-03 | RAN#83 | RP-190560 | 0020 | 1 | F | Data volume reporting for MR-DC with 5GC | 15.3.0 | +| 2019-03 | RAN#83 | RP-190560 | 0029 | 1 | F | TS 38.463 ASN.1 corrections | 15.3.0 | +| 2019-03 | RAN#83 | RP-190560 | 0030 | - | F | Rapporteur corrections for TS 38.463 | 15.3.0 | +| 2019-03 | RAN#83 | RP-190611 | 0035 | 3 | F | S-NSSAI update during EPS to 5GS handover | 15.3.0 | +| 2019-07 | RP#84 | RP-191399 | 0023 | 2 | F | Support of ongoing re-mapping on source side during SDAP mobility | 15.4.0 | +| 2019-07 | RP#84 | RP-191399 | 0028 | 1 | F | TS 38.463 Tabular clean up for Bearer Context messages | 15.4.0 | +| 2019-07 | RP-84 | RP-191399 | 0044 | 2 | F | Correction to DRB 5QI on E1 | 15.4.0 | +| 2019-07 | RP-84 | RP-191399 | 0049 | 2 | F | Multiple SCTP associations over E1 | 15.4.0 | +| 2019-07 | RP-84 | RP-191399 | 0050 | 2 | F | Rapporteur's editorial corrections for TS 38.463 | 15.4.0 | +| 2019-07 | RP-84 | RP-191399 | 0051 | - | F | E1AP failure messages correction | 15.4.0 | +| 2019-07 | RP-84 | RP-191399 | 0052 | 1 | F | New UL TNL Information clarification | 15.4.0 | +| 2019-07 | RP-84 | RP-191399 | 0053 | 4 | F | UE Identification over E1 | 15.4.0 | +| 2019-07 | RP-84 | RP-191399 | 0057 | 2 | F | CR to 38.463 on deconfiguring PDCP duplication | 15.4.0 | +| 2019-07 | RP-84 | RP-191399 | 0062 | 2 | F | Clarification on security indication in the modification procedure over E1 interface | 15.4.0 | +| 2019-07 | RP-84 | RP-191399 | 0064 | 2 | F | Clarification on counter check procedure | 15.4.0 | +| 2019-07 | RP-84 | RP-191397 | 0065 | | F | Correction of Network Instance | 15.4.0 | +| 2019-07 | RP-84 | RP-191399 | 0073 | 1 | F | Activity Notification Level in Bearer Context Modification Request E1AP | 15.4.0 | +| 2019-07 | RP-84 | RP-191394 | 0075 | 1 | F | PDCP SN length and RLC mode related clean-up over To Be Modified structure in Bearer Context Modification procedure | 15.4.0 | +| 2019-07 | RP-84 | RP-191399 | 0084 | - | F | Bearer Context Release Request Cause | 15.4.0 | +| 2019-07 | RP-84 | RP-191399 | 0085 | - | F | Clarification on Bearer Context Setup and Bearer Context Modification failures | 15.4.0 | +| 2019-07 | RP-84 | RP-191396 | 0086 | 1 | F | PDU session split for E1 | 15.4.0 | +| 2019-07 | RP-84 | RP-191399 | 0091 | - | F | Rapporteur's editorial corrections for TS 38.463 | 15.4.0 | +| 2019-07 | RP-84 | RP-191399 | 0092 | 1 | F | Rapporteur's ASN.1 corrections for TS 38.463 | 15.4.0 | +| 2019-07 | RP-84 | RP-191399 | 0095 | 1 | F | CR to 38.463 on adding Cause when remove DRB and PDU Session | 15.4.0 | +| 2019-07 | RP-84 | RP-191399 | 0097 | - | F | Rapporteur's ASN.1 corrections for TS 38.463 | 15.4.0 | +| 2019-09 | RP-85 | RP-192168 | 0094 | 2 | F | CR to 38.463 on Security Indication | 15.5.0 | +| 2019-09 | RP-85 | RP-192166 | 0098 | 1 | F | Correction of security indication | 15.5.0 | +| 2019-09 | RP-85 | RP-192166 | 0111 | 1 | F | Clarification for TNLA removal | 15.5.0 | +| 2019-09 | RP-85 | RP-192168 | 0122 | 2 | F | Correction of semantic descriptions in TS 38.463 (rapporteur) | 15.5.0 | +| 2019-12 | RP-86 | RP-192915 | 0158 | 1 | F | Correction of S-NSSAI coding | 15.6.0 | +| 2019-12 | RP-86 | RP-192915 | 0174 | 2 | F | UL Data Split Threshold correction | 15.6.0 | +| 2019-12 | RP-86 | RP-192915 | 0476 | 1 | F | Correction to DRB to Setup | 15.6.0 | +| 2019-12 | RP-86 | RP-192913 | 0033 | 7 | F | Trace function support for E1AP | 16.0.0 | +| 2019-12 | RP-86 | RP-192913 | 0089 | 4 | B | Introduction of Additional RRM Policy Index (ARPI) | 16.0.0 | +| 2019-12 | RP-86 | RP-192913 | 0096 | 3 | B | Retainability measurements for DRBs and QoS flows | 16.0.0 | +| 2019-12 | RP-86 | RP-192913 | 0163 | 1 | C | Extending the MDBV Range | 16.0.0 | +| 2019-12 | RP-86 | RP-193212 | 0473 | 4 | F | Support for setting up IPsec a priori in E1 | 16.0.0 | +| 2020-03 | RP-87-e | RP-200477 | 0481 | 4 | B | E2E delay measurement for Qos monitoring for URLLC | 16.1.0 | +| 2020-03 | RP-87-e | RP-200425 | 0487 | - | F | E1AP correction of F1 Support for IPsec Setup | 16.1.0 | +| 2020-03 | RP-87-e | RP-200425 | 0488 | - | F | Rapporteur's corrections for TS 38.463 | 16.1.0 | +| 2020-03 | RP-87-e | RP-200425 | 0489 | - | D | Rapporteur's editorial corrections for TS 38.463 | 16.1.0 | + +| | | | | | | | | +|---------|---------|-----------|------|----|---|----------------------------------------------------------------------------------------------------------|--------| +| 2020-04 | | | | | | Editorial correction to the ASN.1 | 16.1.1 | +| 2020-07 | RP-88-e | RP-201082 | 0142 | 12 | B | Addition of SON features | 16.2.0 | +| 2020-07 | RP-88-e | RP-201079 | 0154 | 11 | B | Introduction of NR_IOT support to TS 38.463 | 16.2.0 | +| 2020-07 | RP-88-e | RP-201077 | 0162 | 6 | B | BL CR to 38.463: Support for IAB | 16.2.0 | +| 2020-07 | RP-88-e | RP-201080 | 0468 | 7 | B | Introduction of Non-Public Networks for TS38.463 | 16.2.0 | +| 2020-07 | RP-88-e | RP-201082 | 0477 | 6 | B | Addition of MDT features | 16.2.0 | +| 2020-07 | RP-88-e | RP-201079 | 0478 | 4 | B | Support of Ethernet Header Compression | 16.2.0 | +| 2020-07 | RP-88-e | RP-201075 | 0490 | 5 | B | Baseline CR for introducing Rel-16 NR mobility enhancement | 16.2.0 | +| 2020-07 | RP-88-e | RP-201085 | 0498 | - | D | Rapporteur's editorial corrections for TS 38.463 | 16.2.0 | +| 2020-07 | RP-88-e | RP-201091 | 0500 | 2 | A | Correction of the Old QoS Flow List update during HO | 16.2.0 | +| 2020-07 | RP-88-e | RP-201092 | 0502 | 2 | A | PDCP Status Report indication in PDCP-Configuration | 16.2.0 | +| 2020-07 | RP-88-e | RP-201074 | 0511 | - | B | Introducing alternative QoS profiles to E1AP | 16.2.0 | +| 2020-07 | RP-88-e | RP-201090 | 0512 | 4 | F | Correction of S-NSSAI range | 16.2.0 | +| 2020-09 | RP-89-e | RP-201953 | 0514 | 3 | F | Correction for SN Terminated (option 3x) GBR bearer establishment | 16.3.0 | +| 2020-09 | RP-89-e | RP-201949 | 0521 | 2 | F | Correction for TS38.463 on Unsuccessful Operation and Abnormal Conditions of MLB | 16.3.0 | +| 2020-09 | RP-89-e | RP-201949 | 0522 | 1 | F | Correction on Industrial IOT Rel-16 DC+CA duplication for E1AP | 16.3.0 | +| 2020-09 | RP-89-e | RP-201953 | 0525 | 1 | A | Correction on reusing Source TEID at Handover | 16.3.0 | +| 2020-09 | RP-89-e | RP-201950 | 0526 | 3 | F | Need of D1 for Qos monitoring for URLLC | 16.3.0 | +| 2020-09 | RP-89-e | RP-201949 | 0532 | 1 | F | TS38.463 Extend the CHO Usage and Support Intra-SN/inter-UP CPC case | 16.3.0 | +| 2020-09 | RP-89-e | RP-201953 | 0536 | 1 | F | Rapporteur's corrections for TS 38.463 | 16.3.0 | +| 2020-09 | RP-89-e | RP-201953 | 0537 | - | D | Rapporteur's editorial corrections for TS 38.463 | 16.3.0 | +| 2020-09 | RP-89-e | RP-201947 | 0551 | 1 | F | CR on clarification of QoS Mapping Information over E1 for Rel-16 IAB | 16.3.0 | +| 2020-09 | RP-89-e | RP-201955 | 0554 | - | F | Corrections to 38.463 on node name type | 16.3.0 | +| 2020-12 | RP-90-e | RP-202312 | 0555 | 1 | F | Support of direct data forwarding for inter-system HO | 16.4.0 | +| 2020-12 | RP-90-e | RP-202310 | 0556 | 3 | F | Correction on DSCP Derivation in IAB-donor node | 16.4.0 | +| 2020-12 | RP-90-e | RP-202313 | 0562 | 1 | F | Introduction of reporting frequency for Qos monitoring for URLLC | 16.4.0 | +| 2020-12 | RP-90-e | RP-202311 | 0566 | - | F | Correction on Industrial IOT Rel-16 PDCP duplication for E1AP | 16.4.0 | +| 2021-03 | RP-91-e | RP-210240 | 0568 | 2 | F | Update on QoS monitoring control | 16.5.0 | +| 2021-03 | RP-91-e | RP-210231 | 0583 | 2 | D | CR to 38.463 Correction on IAB UP TNL Address Update | 16.5.0 | +| 2021-06 | RP-92-e | RP-211335 | 0577 | 2 | F | Inter-system indicator for Bearer Context Setup | 16.6.0 | +| 2021-06 | RP-92-e | RP-211337 | 0585 | - | F | Private Message Definition | 16.6.0 | +| 2021-06 | RP-92-e | RP-211338 | 0602 | 4 | C | Maximum number of NR-CGI over E1 [EXT_NRCGI_E1] | 16.6.0 | +| 2021-09 | RP-93-e | RP-211877 | 0589 | 2 | F | CR on E1AP handling for unmapped DL QoS flows | 16.7.0 | +| 2021-09 | RP-93-e | RP-211877 | 0612 | 1 | A | Correction of PDU Session level Data Forwarding Information and QoS Flow list | 16.7.0 | +| 2021-09 | RP-93-e | RP-211879 | 0614 | 2 | F | Restricting the number of DL EHC contexts | 16.7.0 | +| 2021-09 | RP-93-e | RP-211881 | 0622 | - | F | Correction for UL Data Notification over E1 | 16.7.0 | +| 2021-09 | RP-93-e | RP-211873 | 0632 | 1 | F | Data forwarding address allocation for handover | 16.7.0 | +| 2021-09 | RP-93-e | RP-211873 | 0636 | 1 | F | Support of direct data forwarding for inter-system HO from 4G to 5G | 16.7.0 | +| 2021-09 | RP-93-e | RP-211881 | 0638 | - | F | Issue for Intra gNB-CU-UP DAPS HO | 16.7.0 | +| 2021-12 | RP-94-e | RP-212866 | 0644 | 3 | F | DAPS Inconsistencies | 16.8.0 | +| 2021-12 | RP-94-e | RP-212870 | 0645 | 1 | F | Adding reference for coding of Common Network Instance | 16.8.0 | +| 2021-12 | RP-94-e | RP-212864 | 0653 | 1 | F | Direct data forwarding indication for intra-5GS handover | 16.8.0 | +| 2021-12 | RP-94-e | RP-213019 | 0656 | 1 | F | Correction of Qos Mapping Information IE in E1AP message for IAB (CR to TS38.463, R16) | 16.8.0 | +| 2021-12 | RP-94-e | RP-212866 | 0657 | 1 | F | E1 impact to support to stop CHO early data forwarding | 16.8.0 | +| 2021-12 | RP-94-e | RP-212870 | 0662 | 2 | F | Correction CR for 38.463 on lossless intra-system HO with QoS flow remapping in CP-UP separated scenario | 16.8.0 | +| 2022-03 | RP-95-e | RP-220279 | 0651 | 2 | F | Dynamic ACL over E1 CR 38.463 | 16.9.0 | +| 2022-03 | RP-95-e | RP-220278 | 0672 | 1 | F | Downlink unmapped QoS flows for E1 | 16.9.0 | +| 2022-03 | RP-95-e | RP-220276 | 0673 | 1 | F | Correction on support of Pre-shared key derivation for IAB-donor-CU-UP | 16.9.0 | +| 2022-03 | RP-95-e | RP-220279 | 0675 | 2 | A | Security indication in the modification procedure over E1 interface | 16.9.0 | +| 2022-03 | RP-95-e | RP-220277 | 0676 | - | F | CR for 38.463 on fixing DAPS HO handling inconsistency during Bearer Context Modification procedure | 16.9.0 | +| 2022-03 | RP-95-e | RP-220282 | 0682 | - | F | Offered GBR in NR-DC | 16.9.0 | +| 2022-03 | RP-95-e | RP-220217 | 0665 | 2 | F | E1AP specification transfer to TS 37.483 | 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/38_series/38472/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38472/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ddf70ea207804d0a55e55f78fa824a9ac2340beb --- /dev/null +++ b/marked/Rel-18/38_series/38472/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:929c12bbe0782711421556a82f6ec681dca92f72e3788da8ab9c640189970271 +size 9432 diff --git a/marked/Rel-18/38_series/38472/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38472/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf589efa47341a826b3fb6cb4e1f9a780f2036f6 --- /dev/null +++ b/marked/Rel-18/38_series/38472/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff079d3343fc6e2f1d12b2ceb9bbac5b5d6bac7ac87f07d9b9713db0e7abd265 +size 6190 diff --git a/marked/Rel-18/38_series/38472/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-18/38_series/38472/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..120e96edecf29e14331f547e7bdb1e9b5f927e56 --- /dev/null +++ b/marked/Rel-18/38_series/38472/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22ec36bf9445a04c1deb0370c566f82995c4a8c962b12aecd79afe7b53a824e3 +size 18637 diff --git a/marked/Rel-18/38_series/38472/raw.md b/marked/Rel-18/38_series/38472/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..531d225696b73c745463d53654ba367253534abc --- /dev/null +++ b/marked/Rel-18/38_series/38472/raw.md @@ -0,0 +1,241 @@ + + +# 3GPP TS 38.472 V18.1.0(2024-06) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 signalling transport (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green wave-like signal 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 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 ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.3 Abbreviations ..... | 6 | +| 4 F1-C 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 F1 interface. The F1 interface provides means for interconnecting a gNB-CU and a gNB-DU of a gNB within an NG-RAN, or for interconnecting a gNB-CU and a gNB-DU of an en-gNB within an E-UTRAN. The present document describes how the F1AP signalling messages are transported over F1. + +# --- 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". +- [7] 3GPP TS 38.401: "NG-RAN; Architecture description". +- [8] 3GPP TS 37.340: "NR; Multi-connectivity; Overall description; Stage-2". +- [9] IETF RFC 6083 (2011-01): "Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)". +- [10] IETF RFC 6335 (2011-08): " Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry". +- [11] IANA: "Stream Control Transmission Protocol (SCTP) Parameters", []. +- [12] 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]. + +**en-gNB:** as defined in TS 37.340 [8] + +**F1:** interface between a gNB-CU and a gNB-DU, providing an interconnection point between the gNB-CU and the gNB-DU. + +**F1-C:** Reference point for the control plane protocol between gNB-CU and gNB-DU. + +**gNB-CU:** as defined in TS 38.401 [7] + +**gNB-DU:** as defined in TS 38.401 [7] + +**gNB:** as defined in TS 38.300 [6] + +**SCTP endpoint:** as defined in IETF RFC 4960 (2007-09) [5] + +**SCTP association:** as defined in IETF RFC 4960 (2007-09) [5] + +## 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 F1-C signalling bearer + +## 4.1 Function and protocol stack + +The F1-C signalling bearer provides the following functions: + +- Provision of reliable transfer of F1AP messages over the F1-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 F1-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: F1-C signalling bearer protocol stack diagram. The diagram shows a vertical stack of protocol layers. At the top is the F1AP layer. Below it is a horizontal line with an oval in the center, representing a connection point. Below this is the SCTP layer. Below SCTP is the IP layer. Below IP is the Data link layer. At the bottom is the Physical layer. To the left of the stack, labels indicate the layers: 'Radio Network Layer' is positioned next to F1AP; 'Transport Network Layer' is positioned next to SCTP and IP; 'Data link layer' is positioned next to the Data link layer; and 'Physical layer' is positioned next to the Physical layer.](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +Figure 4.1-1: F1-C signalling bearer protocol stack diagram. The diagram shows a vertical stack of protocol layers. At the top is the F1AP layer. Below it is a horizontal line with an oval in the center, representing a connection point. Below this is the SCTP layer. Below SCTP is the IP layer. Below IP is the Data link layer. At the bottom is the Physical layer. To the left of the stack, labels indicate the layers: 'Radio Network Layer' is positioned next to F1AP; 'Transport Network Layer' is positioned next to SCTP and IP; 'Data link layer' is positioned next to the Data link layer; and 'Physical layer' is positioned next to the Physical layer. + +**Figure 4.1-1: F1-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 gNB-CU and gNB-DU shall support IPv6 (IETF RFC 8200 [2]) and/or IPv4 (IETF RFC 791 [3]). + +The IP layer of F1-C only supports point-to-point transmission for delivering F1AP message. + +The gNB-CU and gNB-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 F1-C signalling bearer. The Payload Protocol Identifier (ppid) to be used by SCTP for the application layer protocol F1AP and for DTLS over SCTP (IETF RFC 6083 [9]) is assigned by IANA in [11]. 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-DU and gNB-CU shall support a configuration with a single SCTP association per gNB-DU/gNB-CU pair. Configurations with multiple SCTP endpoints per gNB-DU/gNB-CU pair should be supported. When configurations with multiple SCTP associations are supported, the gNB-CU/gNB-DU may request to dynamically add/remove SCTP associations between the gNB-DU/gNB-CU pair. + +The gNB-DU shall establish the SCTP association. The SCTP Destination Port number value to be used by F1AP is assigned by IANA in [12]. When the gNB-CU requests to dynamically add additional SCTP associations between the gNB-DU/gNB-CU pair, the SCTP Destination Port number value may be the one assigned by IANA in [12], or any dynamic port value (IETF RFC 6335 [10]). + +Within the set of SCTP associations established between one gNB-CU and gNB-DU pair, a single SCTP association shall be employed for F1AP elementary procedures that utilize non-UE-associated signalling with the possibility of fail-over to a new association to enable robustness. Selection of the SCTP association by the gNB-DU and the gNB-CU is specified in TS 38.401 [7]. + +When the configuration with multiple SCTP endpoints per gNB-DU is supported and gNB-DU wants to add additional SCTP endpoints, the gNB-DU Configuration Update procedure shall be the first F1AP procedure triggered on an + +additional TNLA of an already setup F1-C interface instance after the TNL association has become operational, and the gNB-CU shall associate the TNLA to the F1-C interface instance using the included gNB-DU ID. + +Between one gNB-CU and gNB-DU pair: + +- A single pair of stream identifiers shall be reserved over an SCTP association for the sole use of F1AP 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 F1AP 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-DU 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 or gNB-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. + +For MBS-associated signalling, principles specified above for UE-associated signalling shall apply. + +# Annex A (informative): Change History + +| Change history | | | | | | | | | +|----------------|----------|-----------|------|-----|-----|------------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2017-06 | R3 NR#2 | R3-172121 | - | - | - | First version | | 0.1.0 | +| 2017-07 | R3 NR#2 | R3-172644 | - | - | - | Incorporated agreed TPs from R3 NR#2 Adhoc | | 0.2.0 | +| 2017-08 | R3#97 | R3-172715 | | | | Incorporated Rapporteur's cleanup | | 0.2.1 | +| 2017-08 | R3#97 | R3-173446 | - | - | - | Incorporated agreed TPs from R3#97 | | 0.3.0 | +| 2017-10 | R3#97b | R3-174246 | - | - | - | Incorporated agreed TPs from R3#97b | | 0.4.0 | +| 2017-12 | R3#98 | R3-175062 | - | - | - | Incorporated agreed TPs from R3#98 | | 0.5.0 | +| 2017-12 | RAN#78 | RP-172261 | | | | Submitted for approval to RAN | | 1.0.0 | +| 2017-12 | RAN#78 | | | | | TR approved by RAN plenary | | 15.0.0 | +| 2018-06 | RAN#80 | RP-181238 | 0002 | 1 | F | Clarifications on multiple TNL associations | | 15.1.0 | +| 2018-09 | RAN#81 | RP-181922 | 0006 | 5 | F | NR Corrections (38.472 Baseline CR covering RAN3-101 agreements) | | 15.2.0 | +| 2019-03 | RAN#83 | RP-190555 | 0009 | 4 | F | Multiple TNLA over F1 transport | | 15.3.0 | +| 2019-07 | RAN#84 | RP-191395 | 0013 | 1 | F | Removal of Multiple TNLA(s) | | 15.4.0 | +| 2019-09 | RAN#85 | RP-192166 | 0014 | 1 | F | Addition of PPID for DTLS over SCTP for 38.472 | | 15.5.0 | +| 2019-09 | RAN#85 | RP-192167 | 0016 | 1 | F | Use of SCTP ports for multiple TNLA | | 15.5.0 | +| 2019-12 | RAN#86 | RP-192915 | 0017 | - | F | Ambiguity with multiple SCTP associations in 38.472 | | 15.6.0 | +| 2020-03 | RAN#87-e | RP-200425 | 0018 | - | F | Rapporteur's Update for 38.472 | | 16.0.0 | +| 2020-09 | RAN#89-e | RP-201956 | 0020 | 2 | A | SCTP association change when current SCTP association is failed | | 16.1.0 | +| 2022-03 | SA#95-e | | | | | Promotion to Release 17 without technical change | | 17.0.0 | +| 2022-09 | RAN#97-e | RP-222188 | 0022 | - | F | Corrections for MBS-associated signalling | | 17.1.0 | +| 2023-06 | RAN#100 | RP-231075 | 0027 | 2 | A | Corrections on TNL association addition, update and removal (F1) | | 17.2.0 | +| 2024-03 | SA#103- | - | - | - | - | Update to Rel-18 version (MCC) | | 18.0.0 | +| 2024-06 | RAN#104 | RP-241113 | 0028 | 3 | D | Correction on F1AP PPID and Destination Port Number over SCTP | | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38473/001e51e5f51e142322032c14a06c9385_img.jpg b/marked/Rel-18/38_series/38473/001e51e5f51e142322032c14a06c9385_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86caf9106d994bd485d10946b267656f16043f8b --- /dev/null +++ b/marked/Rel-18/38_series/38473/001e51e5f51e142322032c14a06c9385_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddbbc99683df5f75ba3160aabd241a4f5cee7e5a7319a4194a983ee551ed78ba +size 16741 diff --git a/marked/Rel-18/38_series/38473/02e16c8e8e61c2706b5c0129674884a8_img.jpg b/marked/Rel-18/38_series/38473/02e16c8e8e61c2706b5c0129674884a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee58033d3bd204a6f9f5cc9c36f9f4b49a7d3cf7 --- /dev/null +++ b/marked/Rel-18/38_series/38473/02e16c8e8e61c2706b5c0129674884a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3dfcbe46744dd250709ee2ae379d594a76d6c199c75b56197257ce3f766ee21 +size 20713 diff --git a/marked/Rel-18/38_series/38473/09ec8c855800290ecbc282cfef399c32_img.jpg b/marked/Rel-18/38_series/38473/09ec8c855800290ecbc282cfef399c32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34ab747c20990b594724574446efd07b3482bcb1 --- /dev/null +++ b/marked/Rel-18/38_series/38473/09ec8c855800290ecbc282cfef399c32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff549717a99a288c76e6e1a687205673556b87715dfc6266629f44cb56cca964 +size 15721 diff --git a/marked/Rel-18/38_series/38473/0c1feadc9b1a8d6535ef5a0604c0004f_img.jpg b/marked/Rel-18/38_series/38473/0c1feadc9b1a8d6535ef5a0604c0004f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..494f54087fdc92c7a5bc5e3b65306e5525944655 --- /dev/null +++ b/marked/Rel-18/38_series/38473/0c1feadc9b1a8d6535ef5a0604c0004f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a9d06e363a94fd1489065bec628d74796e1b9881fb49a0a0bcaf0c03e6814a9 +size 12920 diff --git a/marked/Rel-18/38_series/38473/0c672a46a384f025be6e69e6e34bfe11_img.jpg b/marked/Rel-18/38_series/38473/0c672a46a384f025be6e69e6e34bfe11_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8a67a300fc4b5d58af4b6dc7084c9dc88dd1534 --- /dev/null +++ b/marked/Rel-18/38_series/38473/0c672a46a384f025be6e69e6e34bfe11_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7274e9101de174036c44b572f53cd6d228d2f4fce0f0ef230788c087ac63e73a +size 15912 diff --git a/marked/Rel-18/38_series/38473/0d9149a10167a487a93c349f5d848b7d_img.jpg b/marked/Rel-18/38_series/38473/0d9149a10167a487a93c349f5d848b7d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3980f0a67ca2303aba8ccb2bee0e67a4ba457332 --- /dev/null +++ b/marked/Rel-18/38_series/38473/0d9149a10167a487a93c349f5d848b7d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17c955e741c20de43b63b758172c7d1247db6d4885ead1c1d054d0cb03172962 +size 17304 diff --git a/marked/Rel-18/38_series/38473/10ffa7dc47da9e864cada0fb7fe6f4cb_img.jpg b/marked/Rel-18/38_series/38473/10ffa7dc47da9e864cada0fb7fe6f4cb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97c0726c90b9ece3f6e901168a905b6e2086a622 --- /dev/null +++ b/marked/Rel-18/38_series/38473/10ffa7dc47da9e864cada0fb7fe6f4cb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7bb20643a3e314a0686764990bdbcb85f1acdcfa996779d5130a6da0cb50f91f +size 27907 diff --git a/marked/Rel-18/38_series/38473/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg b/marked/Rel-18/38_series/38473/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8c4ed0ec55b490c948fe3ea26fbb3e94cd09a16 --- /dev/null +++ b/marked/Rel-18/38_series/38473/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce03334777e6d31dccda4641e4055295d291aadec4f805cdbb74e045b8520ab7 +size 15217 diff --git a/marked/Rel-18/38_series/38473/131668780aa094876183923cf648e438_img.jpg b/marked/Rel-18/38_series/38473/131668780aa094876183923cf648e438_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b38bf346945560cae7ee4a0772eccc09e033cb64 --- /dev/null +++ b/marked/Rel-18/38_series/38473/131668780aa094876183923cf648e438_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13e68ae28986c2bcb5d8eecc19683bc1278df9e4121343d44a5201fc11dc78b8 +size 23162 diff --git a/marked/Rel-18/38_series/38473/132ad076dd59b60fd549f7a612ed568b_img.jpg b/marked/Rel-18/38_series/38473/132ad076dd59b60fd549f7a612ed568b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6074098a5b2f31570096e8b14749630e12b23411 --- /dev/null +++ b/marked/Rel-18/38_series/38473/132ad076dd59b60fd549f7a612ed568b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef2f2de9b522d0c5d2c2fbce36d653b12d3d85bddc31161c14c737f062103e5f +size 27287 diff --git a/marked/Rel-18/38_series/38473/16766297a5918739f471ec2a3130cca9_img.jpg b/marked/Rel-18/38_series/38473/16766297a5918739f471ec2a3130cca9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65637d54a5b94044187d209f8f27b9074735380a --- /dev/null +++ b/marked/Rel-18/38_series/38473/16766297a5918739f471ec2a3130cca9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc1cc1b32c48f4d37fbd9e7535dd79d0c3b0f9a92335703dbfc313f889442923 +size 14924 diff --git a/marked/Rel-18/38_series/38473/184d3d9a856c77aae93652f4fe30f752_img.jpg b/marked/Rel-18/38_series/38473/184d3d9a856c77aae93652f4fe30f752_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da735ab7bcb04d2d406f64ae01692f096fd705e2 --- /dev/null +++ b/marked/Rel-18/38_series/38473/184d3d9a856c77aae93652f4fe30f752_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca846e69d8a8178d845e0c64732a31d8bbef8a66173adce3056f48b74c9957ec +size 25523 diff --git a/marked/Rel-18/38_series/38473/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-18/38_series/38473/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9e900dfdaf08ac3c0055e4124305cddfef58286 --- /dev/null +++ b/marked/Rel-18/38_series/38473/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f02c6e2b2e710d739bf23fc16bb804ba9ad53dce9c6d2625b1cf60891d893a4 +size 11765 diff --git a/marked/Rel-18/38_series/38473/18b87e4ce7ef441f5620b8d6539a2939_img.jpg b/marked/Rel-18/38_series/38473/18b87e4ce7ef441f5620b8d6539a2939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1778a7090e11c590c58c91ccd9ca7ff0d994cce --- /dev/null +++ b/marked/Rel-18/38_series/38473/18b87e4ce7ef441f5620b8d6539a2939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7953ce0a9fea4715b2f96f63bc45a6566f961584b51e43cc1a13d78925720771 +size 33361 diff --git a/marked/Rel-18/38_series/38473/19499072f755b22d0a231123f75fa477_img.jpg b/marked/Rel-18/38_series/38473/19499072f755b22d0a231123f75fa477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5c60236f8dcc853d8644eae8a69e1eebc69e25e --- /dev/null +++ b/marked/Rel-18/38_series/38473/19499072f755b22d0a231123f75fa477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57f868967159365489d2718c33ae375b445584b3625d7f748fb0f891b5256f2f +size 21316 diff --git a/marked/Rel-18/38_series/38473/1b39bec1cdf850bbcbbd693f5c36dbf4_img.jpg b/marked/Rel-18/38_series/38473/1b39bec1cdf850bbcbbd693f5c36dbf4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..936535c14ffcfe5acf96651eeab95065d8a83311 --- /dev/null +++ b/marked/Rel-18/38_series/38473/1b39bec1cdf850bbcbbd693f5c36dbf4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51f1c0cebabd61154b8d8e1f8899992c77a92e88373c8b2f81516c53941dfef9 +size 27094 diff --git a/marked/Rel-18/38_series/38473/1ec8205c17ab05d4670ab9d41b572ec7_img.jpg b/marked/Rel-18/38_series/38473/1ec8205c17ab05d4670ab9d41b572ec7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8aaf99126c937f7872ee4ac9105071fc361edead --- /dev/null +++ b/marked/Rel-18/38_series/38473/1ec8205c17ab05d4670ab9d41b572ec7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:704c3a561d5d85c5f28a516a86dff877fe44f5da5d90d43fedfc933ef62989f2 +size 17077 diff --git a/marked/Rel-18/38_series/38473/1f1614411edea7edfc86c839a608e1fc_img.jpg b/marked/Rel-18/38_series/38473/1f1614411edea7edfc86c839a608e1fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ecba167776b3b2a73b6e2febcccf6796c57b4d2 --- /dev/null +++ b/marked/Rel-18/38_series/38473/1f1614411edea7edfc86c839a608e1fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee4b89a12a1a76bb8d0e889d9e086bad2e093beded3c53f4f28761d620d5fd23 +size 20246 diff --git a/marked/Rel-18/38_series/38473/237b76118be454462fc9b4e96adaa6c7_img.jpg b/marked/Rel-18/38_series/38473/237b76118be454462fc9b4e96adaa6c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39c55fe40e1c78291992a2668f452b0bbd3eaa9b --- /dev/null +++ b/marked/Rel-18/38_series/38473/237b76118be454462fc9b4e96adaa6c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7bf4342745bc65d5d943ebbbfe77882e16931a7e8cccbb7dd9d7c1821c02d98 +size 23659 diff --git a/marked/Rel-18/38_series/38473/23cb65390082ab306c15bd3d8196135e_img.jpg b/marked/Rel-18/38_series/38473/23cb65390082ab306c15bd3d8196135e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ecf367c3eacfe1727591b1c9324f59980cd8f712 --- /dev/null +++ b/marked/Rel-18/38_series/38473/23cb65390082ab306c15bd3d8196135e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29a3f81cb6ee096b71ca89d4236bb6a6a7e3caab35fc009ea0f4de27aac99372 +size 17149 diff --git a/marked/Rel-18/38_series/38473/300130063df853c2bf2589510f69dbba_img.jpg b/marked/Rel-18/38_series/38473/300130063df853c2bf2589510f69dbba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd1e4934056d6610497b927e47c2d4648246e6d8 --- /dev/null +++ b/marked/Rel-18/38_series/38473/300130063df853c2bf2589510f69dbba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f594bc18f5a8a8ac982d2b318e14514ff4c2930c42e65f25cd5b019f3e7b441a +size 21380 diff --git a/marked/Rel-18/38_series/38473/327cb947c7270b695bdd1cab5e8d72c0_img.jpg b/marked/Rel-18/38_series/38473/327cb947c7270b695bdd1cab5e8d72c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6aee9feea99249d3b5d4793b714a1146498db80 --- /dev/null +++ b/marked/Rel-18/38_series/38473/327cb947c7270b695bdd1cab5e8d72c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:066b786dc1224fc0c68454bc4015855755e040617ce2a83c7b966859c84a2547 +size 17503 diff --git a/marked/Rel-18/38_series/38473/32d2783121efa86871886ed9d7678637_img.jpg b/marked/Rel-18/38_series/38473/32d2783121efa86871886ed9d7678637_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a84894000c21ff1c80dd2b951f7163a816c1b223 --- /dev/null +++ b/marked/Rel-18/38_series/38473/32d2783121efa86871886ed9d7678637_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f24bd66f6d601ad453b5c92b871a45170108df6d4ba39d5e7af83528601ad056 +size 25527 diff --git a/marked/Rel-18/38_series/38473/37104233d1b6d7728427e833816594dc_img.jpg b/marked/Rel-18/38_series/38473/37104233d1b6d7728427e833816594dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2c54536b38f8d04d652cddc3b25fb512f4e140a --- /dev/null +++ b/marked/Rel-18/38_series/38473/37104233d1b6d7728427e833816594dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9450bdcf7f8cf2630639ede55d91c1ab3feec702db38cb1fce158644f24e622 +size 18812 diff --git a/marked/Rel-18/38_series/38473/376f80eb8a41369e87da63a0210d173e_img.jpg b/marked/Rel-18/38_series/38473/376f80eb8a41369e87da63a0210d173e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1e7c1697a69b1ffce621c06bf8b71227c261531 --- /dev/null +++ b/marked/Rel-18/38_series/38473/376f80eb8a41369e87da63a0210d173e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b67ac5d81ced4ce5de5fcf6e67c674dcf2109c3c48be4b8f0b9024491a10b384 +size 15801 diff --git a/marked/Rel-18/38_series/38473/39f5c01e256787572d7b50ca763be6e2_img.jpg b/marked/Rel-18/38_series/38473/39f5c01e256787572d7b50ca763be6e2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a45737f93af35cf7d1961af035826dc42e4db704 --- /dev/null +++ b/marked/Rel-18/38_series/38473/39f5c01e256787572d7b50ca763be6e2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3307809e84eb09a21463fe032d311216a078319681edc2ccd12de3c9f73e3827 +size 20656 diff --git a/marked/Rel-18/38_series/38473/404924fde6a708196214ae2da3819428_img.jpg b/marked/Rel-18/38_series/38473/404924fde6a708196214ae2da3819428_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2a405f04a5e974bde8df581e55a21a877c9792f --- /dev/null +++ b/marked/Rel-18/38_series/38473/404924fde6a708196214ae2da3819428_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e165eb6a50ab5e5f140bd98b228bb97027d5bcbe6bc574f5ed69bcff3cedf6c +size 25741 diff --git a/marked/Rel-18/38_series/38473/40b80ef077f6151a9fbb593b8ad4864d_img.jpg b/marked/Rel-18/38_series/38473/40b80ef077f6151a9fbb593b8ad4864d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55442f74232cd02211b538e7b51c77db4e1dcd9c --- /dev/null +++ b/marked/Rel-18/38_series/38473/40b80ef077f6151a9fbb593b8ad4864d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bcf6be384fa207f8754caeb419a5f5a3f0ba8b2ca2e67b68fa1f381be63be37 +size 15291 diff --git a/marked/Rel-18/38_series/38473/418ac859afe534b37c6f4e96e15c0b25_img.jpg b/marked/Rel-18/38_series/38473/418ac859afe534b37c6f4e96e15c0b25_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2fcfa9c64022a07ec8d6aeee3c9d282d6fc3551 --- /dev/null +++ b/marked/Rel-18/38_series/38473/418ac859afe534b37c6f4e96e15c0b25_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebf1808f498e91bedf5cc3b1b18a062c85135b2baad1737a9cfa4df88d3238eb +size 27928 diff --git a/marked/Rel-18/38_series/38473/43437211ce989e9da795fecc0d499c05_img.jpg b/marked/Rel-18/38_series/38473/43437211ce989e9da795fecc0d499c05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..397e5ea61ca8f18bc5e8ffd3d5e54972d1277339 --- /dev/null +++ b/marked/Rel-18/38_series/38473/43437211ce989e9da795fecc0d499c05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85e436af23d1e3afabf7f110be0ce92ecc008210042fd2de84de3f1c33b14478 +size 13569 diff --git a/marked/Rel-18/38_series/38473/435cf83a9531da350ea543aafa0add62_img.jpg b/marked/Rel-18/38_series/38473/435cf83a9531da350ea543aafa0add62_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d5f567d8fa649eea6a1c53497804c8eda4e0ab4 --- /dev/null +++ b/marked/Rel-18/38_series/38473/435cf83a9531da350ea543aafa0add62_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93157eb6120394f0901ff09bca71794794b2f7cd3a3e68a018255c7901991ef6 +size 19472 diff --git a/marked/Rel-18/38_series/38473/437a88375397eec8390174b5426e99b0_img.jpg b/marked/Rel-18/38_series/38473/437a88375397eec8390174b5426e99b0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20a514591c02f84f4d268ae1e09ef1d6699997db --- /dev/null +++ b/marked/Rel-18/38_series/38473/437a88375397eec8390174b5426e99b0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5af61a23afa04b6fd68e65567cba53f1db39486f8714b753f85bd4f7a57a018b +size 26455 diff --git a/marked/Rel-18/38_series/38473/457a77ed21f00d697e7d1d0b54041ca2_img.jpg b/marked/Rel-18/38_series/38473/457a77ed21f00d697e7d1d0b54041ca2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39399d9df90c68d22f4389caff2d5d8617d55f5c --- /dev/null +++ b/marked/Rel-18/38_series/38473/457a77ed21f00d697e7d1d0b54041ca2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86b0b853cac6ed65d3204df3cba2b0367dfb435b4b6f599ab37991b01982090f +size 18860 diff --git a/marked/Rel-18/38_series/38473/461ef997feb933486effd3b0d3504016_img.jpg b/marked/Rel-18/38_series/38473/461ef997feb933486effd3b0d3504016_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..930942296fae52984c8453418da106a7c3aa5d98 --- /dev/null +++ b/marked/Rel-18/38_series/38473/461ef997feb933486effd3b0d3504016_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:295ed34c9f36dfb0f1965f9d6b0e7e2b3b64ba3d919515b8403103a1cf93b2ca +size 26577 diff --git a/marked/Rel-18/38_series/38473/48090d8f1db2e826aaa740035aa12ecb_img.jpg b/marked/Rel-18/38_series/38473/48090d8f1db2e826aaa740035aa12ecb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1fb06d1a508b13224e31bfc20f1a2ae7758261c --- /dev/null +++ b/marked/Rel-18/38_series/38473/48090d8f1db2e826aaa740035aa12ecb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ffdce9da2674c791e7b83ee7f39e30e751d0a127470eff45e7cfd18c9a5c89e +size 29243 diff --git a/marked/Rel-18/38_series/38473/493539f7472fd8510b2c6dcb59339ad5_img.jpg b/marked/Rel-18/38_series/38473/493539f7472fd8510b2c6dcb59339ad5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7021b00a5a3ad6565b75749f72363e836ced261 --- /dev/null +++ b/marked/Rel-18/38_series/38473/493539f7472fd8510b2c6dcb59339ad5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0392d9d288d4c123c919f51d68cb54042d209deb10f1914ee112ecb35ee1a12 +size 22867 diff --git a/marked/Rel-18/38_series/38473/497d7e14540664a2914557cad79f3791_img.jpg b/marked/Rel-18/38_series/38473/497d7e14540664a2914557cad79f3791_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fd4c1868cdc0ee9ea5b0863a84cc46963127164 --- /dev/null +++ b/marked/Rel-18/38_series/38473/497d7e14540664a2914557cad79f3791_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d664e79c09b6b3fcdd1b7f86973425565737c1cb392fab284e4a575c5fd0e110 +size 20561 diff --git a/marked/Rel-18/38_series/38473/4a9454b4354535e1b61423084da1424b_img.jpg b/marked/Rel-18/38_series/38473/4a9454b4354535e1b61423084da1424b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56d7f61984626237da724daf8ff4f1bdcba6dae7 --- /dev/null +++ b/marked/Rel-18/38_series/38473/4a9454b4354535e1b61423084da1424b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5fb19b18eda7a2e44229700d6cb28f477fa987d04dfb97d7ceef220efe1a558 +size 28235 diff --git a/marked/Rel-18/38_series/38473/4b2dd266b605b2f31a8759f802637301_img.jpg b/marked/Rel-18/38_series/38473/4b2dd266b605b2f31a8759f802637301_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fe8adab5abdc51131e96627315510572bfd69ee --- /dev/null +++ b/marked/Rel-18/38_series/38473/4b2dd266b605b2f31a8759f802637301_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af1933168c553fd668f6734cf3c94b3018053bf8d1fbe2c913ccc30f5dff3ac1 +size 13036 diff --git a/marked/Rel-18/38_series/38473/4bb56f4af58f9d5daab52d98c984d8d5_img.jpg b/marked/Rel-18/38_series/38473/4bb56f4af58f9d5daab52d98c984d8d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..947f0a3578b8b30298941a1ec4af8948a9d2c139 --- /dev/null +++ b/marked/Rel-18/38_series/38473/4bb56f4af58f9d5daab52d98c984d8d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03f144351eb99e488ddf091ffdeb1f0176a6f8f784183c82a45c46430a5c7166 +size 16335 diff --git a/marked/Rel-18/38_series/38473/4c4c756d9c3797fc23d861bc37d2d63d_img.jpg b/marked/Rel-18/38_series/38473/4c4c756d9c3797fc23d861bc37d2d63d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..381d39de246b5344c3f25b408c59180b675b379f --- /dev/null +++ b/marked/Rel-18/38_series/38473/4c4c756d9c3797fc23d861bc37d2d63d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b434ceb3f01cd516ae82748bc0ebf5d8017ca47a550dd57eb2c0e10ae451df9 +size 21366 diff --git a/marked/Rel-18/38_series/38473/4e3bce0b4a3062f7f237acd0b04e5c66_img.jpg b/marked/Rel-18/38_series/38473/4e3bce0b4a3062f7f237acd0b04e5c66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6cf30a34bbc24950227e6413d6d54e4edbf1f4f --- /dev/null +++ b/marked/Rel-18/38_series/38473/4e3bce0b4a3062f7f237acd0b04e5c66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56dd0f7d445f1de5e7689c17d4db4cea172d9b49dfa00a5681d59f48d1febeb9 +size 22907 diff --git a/marked/Rel-18/38_series/38473/50f72073c616cb3d3ca3af04a0c3a221_img.jpg b/marked/Rel-18/38_series/38473/50f72073c616cb3d3ca3af04a0c3a221_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f06cc3e7637ba426dfae5978c5c3d6ccd3fd686b --- /dev/null +++ b/marked/Rel-18/38_series/38473/50f72073c616cb3d3ca3af04a0c3a221_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:007a07b27caed8e8ded325a2a7ad450683adffa59cab14236fdac4b2c698766b +size 14893 diff --git a/marked/Rel-18/38_series/38473/51167ecef86d85cdc6dde05a3afb74b8_img.jpg b/marked/Rel-18/38_series/38473/51167ecef86d85cdc6dde05a3afb74b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4308f6aac4825b97f0cb1f5551668e160e8e4145 --- /dev/null +++ b/marked/Rel-18/38_series/38473/51167ecef86d85cdc6dde05a3afb74b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d978f27924db0f39caea78b5f9b8b043b38997a230a77ce3857312410dfc028 +size 25987 diff --git a/marked/Rel-18/38_series/38473/53001b5ae3f65139f78db410bb41ae30_img.jpg b/marked/Rel-18/38_series/38473/53001b5ae3f65139f78db410bb41ae30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5c5bea0aeb70b40b377066d11af114ba2c4f7b3 --- /dev/null +++ b/marked/Rel-18/38_series/38473/53001b5ae3f65139f78db410bb41ae30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dad3ef4574146294672d32779f41e81c025d3385c6bb3844186068e5dc6646d4 +size 21713 diff --git a/marked/Rel-18/38_series/38473/5593facb376cb360bd4b0960b2911b3e_img.jpg b/marked/Rel-18/38_series/38473/5593facb376cb360bd4b0960b2911b3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3779e41863c71cb8b5edb506234f602b79671557 --- /dev/null +++ b/marked/Rel-18/38_series/38473/5593facb376cb360bd4b0960b2911b3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d94f0959ca4b404895cd8f96c2207e0cf8a454f67b58d068e18d88b83de636b2 +size 28453 diff --git a/marked/Rel-18/38_series/38473/56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg b/marked/Rel-18/38_series/38473/56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..397b45f3308360512ce78805aa2649da99cad531 --- /dev/null +++ b/marked/Rel-18/38_series/38473/56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1ca3f31e22d2e5f902708c640f50c0007c63a7b044daa17732794f7dbf260a0 +size 12387 diff --git a/marked/Rel-18/38_series/38473/56f125e1bc127f7ac3d210407957413c_img.jpg b/marked/Rel-18/38_series/38473/56f125e1bc127f7ac3d210407957413c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0fac344c0339a5bd58af84cb1a546e974cf0dabc --- /dev/null +++ b/marked/Rel-18/38_series/38473/56f125e1bc127f7ac3d210407957413c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f2302bc8575cc9678d17d81ee56c97aa43461164ae2ebff6ea486e919b191f4 +size 18601 diff --git a/marked/Rel-18/38_series/38473/5cce7ed287fbd2f458757874de049f7d_img.jpg b/marked/Rel-18/38_series/38473/5cce7ed287fbd2f458757874de049f7d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90c90458fdd71afb7da5a62a0edfa8d0e1f850a0 --- /dev/null +++ b/marked/Rel-18/38_series/38473/5cce7ed287fbd2f458757874de049f7d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c1f2472bc4e7eed433e1ec88b6463e381e999f35331580cde1692748637a09f +size 30301 diff --git a/marked/Rel-18/38_series/38473/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg b/marked/Rel-18/38_series/38473/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d08ad84f91a0039c6815b02985768ab884c1f3ed --- /dev/null +++ b/marked/Rel-18/38_series/38473/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c510ae0ccce8a40bc602e5d61c227d12148ea7afb621cd4316feaf9793b9ef0f +size 23856 diff --git a/marked/Rel-18/38_series/38473/5e42741a4adfaf166be0b153e8089809_img.jpg b/marked/Rel-18/38_series/38473/5e42741a4adfaf166be0b153e8089809_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfe9129dff5873c6d18965a4c0572ea007619b83 --- /dev/null +++ b/marked/Rel-18/38_series/38473/5e42741a4adfaf166be0b153e8089809_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12a5625d4272067365d1fbd6e785a10f01b175316cf9c2e1cd5dc2933a92825e +size 29045 diff --git a/marked/Rel-18/38_series/38473/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38473/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ea466f9ef55e1ccd8f0345c22120ed1f551a91f --- /dev/null +++ b/marked/Rel-18/38_series/38473/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73a21513f15a5e84d575994c28109025cc404bca6ab6923e0866ae4b82903c62 +size 9454 diff --git a/marked/Rel-18/38_series/38473/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-18/38_series/38473/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca2c5ffb03a2d60714b912f883ba9f9a29cee7cc --- /dev/null +++ b/marked/Rel-18/38_series/38473/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0662b71f94212573a9a177eb568176ab12a92455a8a9102b126e763145e78316 +size 19203 diff --git a/marked/Rel-18/38_series/38473/6334c962f5e106e3331e59946e4d166e_img.jpg b/marked/Rel-18/38_series/38473/6334c962f5e106e3331e59946e4d166e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9132993fdfd3e9fd0bf5af1c82d78fc87b741a82 --- /dev/null +++ b/marked/Rel-18/38_series/38473/6334c962f5e106e3331e59946e4d166e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8801b0dc4a45265cd380e4aa2fe6398a20c568b369387137503234cf7580de05 +size 16359 diff --git a/marked/Rel-18/38_series/38473/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38473/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..610535584c2bf8a99ad133133adc2b1bff66c411 --- /dev/null +++ b/marked/Rel-18/38_series/38473/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:672ae38e72da8b45ce016ad58be76e537585e11016cd0d18764e26c283338c91 +size 8594 diff --git a/marked/Rel-18/38_series/38473/649f424fd35ea31f622163506a6148ed_img.jpg b/marked/Rel-18/38_series/38473/649f424fd35ea31f622163506a6148ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65b481e03e2270b2a6afb6cff965c97747830fda --- /dev/null +++ b/marked/Rel-18/38_series/38473/649f424fd35ea31f622163506a6148ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:141f51d3f1d9c303bf527162d91e266caa043fdd370fc8439f9c9aa3784d7ce2 +size 24246 diff --git a/marked/Rel-18/38_series/38473/66d5189a924662748cac6a9b22a272e9_img.jpg b/marked/Rel-18/38_series/38473/66d5189a924662748cac6a9b22a272e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..656ef80cf1a104b51b2ef0c7db164cff2850e2a3 --- /dev/null +++ b/marked/Rel-18/38_series/38473/66d5189a924662748cac6a9b22a272e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:459a2c2a34e00d53f30beeff297bbfebb6c5cff5ec3859aac199106b16f09eb3 +size 16284 diff --git a/marked/Rel-18/38_series/38473/678ac9faaa56bb929499cebeea83a110_img.jpg b/marked/Rel-18/38_series/38473/678ac9faaa56bb929499cebeea83a110_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6882408f91537541311e434a6e574418a8cbedf --- /dev/null +++ b/marked/Rel-18/38_series/38473/678ac9faaa56bb929499cebeea83a110_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d554605d12d5aa34fde47cf4f0085a032ea88c3a293970cef81ad4cd49c6b152 +size 15569 diff --git a/marked/Rel-18/38_series/38473/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg b/marked/Rel-18/38_series/38473/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb1cb07e4b43085d73ea22de0b81260a44a25648 --- /dev/null +++ b/marked/Rel-18/38_series/38473/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80a1c04b719d6e5b597a2fdfe69775be3247065baa03434e9dfe6368ab14f9e5 +size 19878 diff --git a/marked/Rel-18/38_series/38473/6e50e3275fbdccd63dc258477b94bef6_img.jpg b/marked/Rel-18/38_series/38473/6e50e3275fbdccd63dc258477b94bef6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7effc87492f583db7b3095bf3e48adb7a5eed288 --- /dev/null +++ b/marked/Rel-18/38_series/38473/6e50e3275fbdccd63dc258477b94bef6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d4df228b42306642dbe0bb5eb9f1da7c6cf646517e60034ab0e501a5e98b904 +size 24535 diff --git a/marked/Rel-18/38_series/38473/6ee202d340236de98def8045f273fa38_img.jpg b/marked/Rel-18/38_series/38473/6ee202d340236de98def8045f273fa38_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5148da8fd185089a4cc9ccc698e8596d547d339 --- /dev/null +++ b/marked/Rel-18/38_series/38473/6ee202d340236de98def8045f273fa38_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31e696e941f32f405c6cbd6a37c877bb44de7f003ed5fc8c065006f261c3f5e6 +size 19260 diff --git a/marked/Rel-18/38_series/38473/727f170860008f2b6de39e96e5a03ced_img.jpg b/marked/Rel-18/38_series/38473/727f170860008f2b6de39e96e5a03ced_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..107c3a08fd57a1179b0917f15a5e01b0d390f136 --- /dev/null +++ b/marked/Rel-18/38_series/38473/727f170860008f2b6de39e96e5a03ced_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87438ebc5809ea1e69c5cf4641e98920f13f5ce581844d7c9ccb5528e6b11681 +size 26225 diff --git a/marked/Rel-18/38_series/38473/77c78bfdbbee0e121808674b08fd7046_img.jpg b/marked/Rel-18/38_series/38473/77c78bfdbbee0e121808674b08fd7046_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d252102946e830848930d4eb7eb568b48d019984 --- /dev/null +++ b/marked/Rel-18/38_series/38473/77c78bfdbbee0e121808674b08fd7046_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd6edcd7efdcd239f02dc3e2cb59b3e9dc98cb9ebc3af65dc808798fce1531fe +size 18862 diff --git a/marked/Rel-18/38_series/38473/7913c315e0db8233cb1ac2455e4a0a81_img.jpg b/marked/Rel-18/38_series/38473/7913c315e0db8233cb1ac2455e4a0a81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19c3d2abb9abf75d38bdd6be2fa66aefeee97a97 --- /dev/null +++ b/marked/Rel-18/38_series/38473/7913c315e0db8233cb1ac2455e4a0a81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ca4e3c44b9e5f1d461a4acfa3e0ce34b05a46d3c082180d6242433664677952 +size 25418 diff --git a/marked/Rel-18/38_series/38473/7a55c91aeff72a180a89e462c5c9f591_img.jpg b/marked/Rel-18/38_series/38473/7a55c91aeff72a180a89e462c5c9f591_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..888eab6cf5318e0720c8fe1816acf6e398e24e99 --- /dev/null +++ b/marked/Rel-18/38_series/38473/7a55c91aeff72a180a89e462c5c9f591_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a15f347ec95cc32e8a0387e2cec2a152da591609caf5e4bda26ddb421f0fcdca +size 15585 diff --git a/marked/Rel-18/38_series/38473/7abc02f39b6084e0f27f07a8e8f9224f_img.jpg b/marked/Rel-18/38_series/38473/7abc02f39b6084e0f27f07a8e8f9224f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c964f3a8c805d14326ee7edf85e5806eff38187f --- /dev/null +++ b/marked/Rel-18/38_series/38473/7abc02f39b6084e0f27f07a8e8f9224f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5a157976946af08563ec511a43ff351fca838228fd28f6714ce27223577e01f +size 18280 diff --git a/marked/Rel-18/38_series/38473/7c239d0d8d8e5ee7edb275ae16c2269e_img.jpg b/marked/Rel-18/38_series/38473/7c239d0d8d8e5ee7edb275ae16c2269e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ffeaa3c9ec1abfa36c5d19b460ef524b22bf3df2 --- /dev/null +++ b/marked/Rel-18/38_series/38473/7c239d0d8d8e5ee7edb275ae16c2269e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90fe44e8c00242afc1b0fdb94f80c6bb52423ced107fca55d5966c0f4bec19fc +size 24943 diff --git a/marked/Rel-18/38_series/38473/7c326311d265966a26e1a116f94aeb9b_img.jpg b/marked/Rel-18/38_series/38473/7c326311d265966a26e1a116f94aeb9b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..207532051bf88d78200d23896fb27a388f121246 --- /dev/null +++ b/marked/Rel-18/38_series/38473/7c326311d265966a26e1a116f94aeb9b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df59b124feb2466d1955081723632717e18eca8a4bd8b9d8c6e0be4e3b0e5770 +size 14862 diff --git a/marked/Rel-18/38_series/38473/7d78469417c76901ecf6e36600a721cb_img.jpg b/marked/Rel-18/38_series/38473/7d78469417c76901ecf6e36600a721cb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc208482bc80f447d5bdbdcb051f2e19c4c19cad --- /dev/null +++ b/marked/Rel-18/38_series/38473/7d78469417c76901ecf6e36600a721cb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d0b7dd86d9715d493d24164b9abd8520c190924c8186402807e72948d0bd179 +size 24161 diff --git a/marked/Rel-18/38_series/38473/81fc56a4a4db1ceae7a1d9810cc03c64_img.jpg b/marked/Rel-18/38_series/38473/81fc56a4a4db1ceae7a1d9810cc03c64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66536900a0d33a0f777e0055c75aabb79c8f5bbc --- /dev/null +++ b/marked/Rel-18/38_series/38473/81fc56a4a4db1ceae7a1d9810cc03c64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bd5121b0fd2cd86edec5360cdc805a74b55768ebe01c0c0739aa7f2b0eb99e4 +size 31729 diff --git a/marked/Rel-18/38_series/38473/8825e92f1c325d7393a17cdcdf31a292_img.jpg b/marked/Rel-18/38_series/38473/8825e92f1c325d7393a17cdcdf31a292_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c24e6c18b341c355b61a67518652893753b30fb --- /dev/null +++ b/marked/Rel-18/38_series/38473/8825e92f1c325d7393a17cdcdf31a292_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9dd76553408e2521ba1b47eee63547a654c658821dc06c78f56363376faabc83 +size 10466 diff --git a/marked/Rel-18/38_series/38473/90321ffa3cade82e4a57d6250d046c88_img.jpg b/marked/Rel-18/38_series/38473/90321ffa3cade82e4a57d6250d046c88_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6271f6b287d83c27d21f507866316012454de329 --- /dev/null +++ b/marked/Rel-18/38_series/38473/90321ffa3cade82e4a57d6250d046c88_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7778e7d6bc056315e29018517ff9d581bca9cc9863f4b8e6ba8e8872c13cceb4 +size 26731 diff --git a/marked/Rel-18/38_series/38473/9400925a53bd0c7e071258c54cb15c15_img.jpg b/marked/Rel-18/38_series/38473/9400925a53bd0c7e071258c54cb15c15_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6dccf2050535727c94aba07c271254ba0c222bd5 --- /dev/null +++ b/marked/Rel-18/38_series/38473/9400925a53bd0c7e071258c54cb15c15_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:efd91af083a910134d5c4af8f231567f86c11b2c420b383b5e5825bc18e8b75f +size 14603 diff --git a/marked/Rel-18/38_series/38473/949b72d31d7a6d03bc78908260e36d58_img.jpg b/marked/Rel-18/38_series/38473/949b72d31d7a6d03bc78908260e36d58_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3705ba1d7f415a62bb001eef6a475b1fbc724f00 --- /dev/null +++ b/marked/Rel-18/38_series/38473/949b72d31d7a6d03bc78908260e36d58_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acbe37ec2049a004d33343b61bf66f0ac04ba55d4d7f0bc73c70b5c034bb108e +size 15972 diff --git a/marked/Rel-18/38_series/38473/991dd3ca8ff5bdb023220b1d44775e1d_img.jpg b/marked/Rel-18/38_series/38473/991dd3ca8ff5bdb023220b1d44775e1d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc2f949ee7fb00751e2f6d2e2907b818fcf7392f --- /dev/null +++ b/marked/Rel-18/38_series/38473/991dd3ca8ff5bdb023220b1d44775e1d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f575bfbbc4b1b49c64d0aa88302cebe9e09b484394e4a72f844d4b3daf68b36 +size 24441 diff --git a/marked/Rel-18/38_series/38473/9d47fe89bc71acebde670ea760ee6ffb_img.jpg b/marked/Rel-18/38_series/38473/9d47fe89bc71acebde670ea760ee6ffb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4317393bdbc233e0e656bc8adbc8452f298ad856 --- /dev/null +++ b/marked/Rel-18/38_series/38473/9d47fe89bc71acebde670ea760ee6ffb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a963b83fdfdd70a4c3fc1608291de42ca81e665b955b48145f633a54a3945618 +size 34843 diff --git a/marked/Rel-18/38_series/38473/9dee6d7157e1d03eb09a30a9aa81cc11_img.jpg b/marked/Rel-18/38_series/38473/9dee6d7157e1d03eb09a30a9aa81cc11_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..620e557854f8b4fae4bb09297c30ce872737bcc7 --- /dev/null +++ b/marked/Rel-18/38_series/38473/9dee6d7157e1d03eb09a30a9aa81cc11_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fda0c95c04bb45e807efde573071e4d5d57b6fdbc189014d605fac05f074484 +size 14707 diff --git a/marked/Rel-18/38_series/38473/9e26cd5584f423e1b2155fb341db579f_img.jpg b/marked/Rel-18/38_series/38473/9e26cd5584f423e1b2155fb341db579f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b002aa12a6a1ccf8fbf0a4df3d92d755fab7eb6c --- /dev/null +++ b/marked/Rel-18/38_series/38473/9e26cd5584f423e1b2155fb341db579f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5e36c66867533fc0507554738201887ab8509f6bca89ffb24dfffee4c8921d0 +size 20654 diff --git a/marked/Rel-18/38_series/38473/a471382fa73185ead4f9b83e3e64ee96_img.jpg b/marked/Rel-18/38_series/38473/a471382fa73185ead4f9b83e3e64ee96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58d424dac565fa89c9e5cffa89adf19b709feaaf --- /dev/null +++ b/marked/Rel-18/38_series/38473/a471382fa73185ead4f9b83e3e64ee96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e590c07aad99ca91d4ac38d95a9d37a7d0cae445f544f62d82397f3948ef0b0 +size 15030 diff --git a/marked/Rel-18/38_series/38473/a5b3b7c5ec2245f09354260ea8cfffc5_img.jpg b/marked/Rel-18/38_series/38473/a5b3b7c5ec2245f09354260ea8cfffc5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8888e177d444357748e1fbd251e7607dbf59dfb9 --- /dev/null +++ b/marked/Rel-18/38_series/38473/a5b3b7c5ec2245f09354260ea8cfffc5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64c671d364db4f2f0825c792487f3f846bbeaafdad8985d8160497e8d3b2f5e8 +size 11876 diff --git a/marked/Rel-18/38_series/38473/a9159a006d67a834a7b1a771c18191cc_img.jpg b/marked/Rel-18/38_series/38473/a9159a006d67a834a7b1a771c18191cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a0da08b6ad93ea7962c9a1460d0fa1f51da50bb --- /dev/null +++ b/marked/Rel-18/38_series/38473/a9159a006d67a834a7b1a771c18191cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce47ffda9097e4345c2e7899cb7b653c60c1727db300133b08279d030e991dde +size 16635 diff --git a/marked/Rel-18/38_series/38473/a9fa8656fd01e4e407bc91dba6ac0ad5_img.jpg b/marked/Rel-18/38_series/38473/a9fa8656fd01e4e407bc91dba6ac0ad5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27ff3c291e113d3fd1f8fe0ed323c21e2dfc7970 --- /dev/null +++ b/marked/Rel-18/38_series/38473/a9fa8656fd01e4e407bc91dba6ac0ad5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec53607b0a27f3a244cf5d970eab7b40706c98b48cc8701f9115d1da2d6457c2 +size 23470 diff --git a/marked/Rel-18/38_series/38473/b27f2a922eec7e6837444dbfb73293a4_img.jpg b/marked/Rel-18/38_series/38473/b27f2a922eec7e6837444dbfb73293a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa4eefd2da2a823dec38e372b64dd7a3b71ae963 --- /dev/null +++ b/marked/Rel-18/38_series/38473/b27f2a922eec7e6837444dbfb73293a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:beb80b458c926f4c28db16d0ddf1cc4e41cbd8a97b81d7fe7d53d10e48693f64 +size 30487 diff --git a/marked/Rel-18/38_series/38473/b2e5ca10383692a39c97d8b9929bcd6d_img.jpg b/marked/Rel-18/38_series/38473/b2e5ca10383692a39c97d8b9929bcd6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03e331e2712d4262c6d1b0fe3c3a5dc3c10745b3 --- /dev/null +++ b/marked/Rel-18/38_series/38473/b2e5ca10383692a39c97d8b9929bcd6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:511808118922694b90a2d116d073b8c65c984ae9a62d0476f5030a488f7253a0 +size 24765 diff --git a/marked/Rel-18/38_series/38473/b2fc8c097c64181ee31839d2703d396d_img.jpg b/marked/Rel-18/38_series/38473/b2fc8c097c64181ee31839d2703d396d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..795c6708f31704d6a00c60b0e37fb842eddad61b --- /dev/null +++ b/marked/Rel-18/38_series/38473/b2fc8c097c64181ee31839d2703d396d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d50d54243ec88b50822e8b746d0e6bd58b373a07bd6aee8240559057370e663 +size 29623 diff --git a/marked/Rel-18/38_series/38473/b30e390cb591b39482fe7ecd4c4cd84b_img.jpg b/marked/Rel-18/38_series/38473/b30e390cb591b39482fe7ecd4c4cd84b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3232aaebbfb9ad24edd9aeeeb3871bf3846bc614 --- /dev/null +++ b/marked/Rel-18/38_series/38473/b30e390cb591b39482fe7ecd4c4cd84b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da7458765f87bb601be47779c700416a6b0603a90951db77597769616ec9dc03 +size 24706 diff --git a/marked/Rel-18/38_series/38473/b550cb515008f6bab9f295adcb28b5f6_img.jpg b/marked/Rel-18/38_series/38473/b550cb515008f6bab9f295adcb28b5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a2ce13f4608dca53e7c6c54f0fa1f8d5e602dc9 --- /dev/null +++ b/marked/Rel-18/38_series/38473/b550cb515008f6bab9f295adcb28b5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f44c82d5f79783df854da09a7c5328039fa2fd296f50a33d7a1356609dd98843 +size 16231 diff --git a/marked/Rel-18/38_series/38473/b5b0749219d60ecf8f3402eb2cc86d1e_img.jpg b/marked/Rel-18/38_series/38473/b5b0749219d60ecf8f3402eb2cc86d1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19e5f5a0c52ab02ef69771f6f6bff1da7745caba --- /dev/null +++ b/marked/Rel-18/38_series/38473/b5b0749219d60ecf8f3402eb2cc86d1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e557ffc86bf4217254ec58b487bf528ae3a1cfc79b13abc860415ecb216afcc7 +size 15717 diff --git a/marked/Rel-18/38_series/38473/b6cee7c106abafe0c3160e285cd68389_img.jpg b/marked/Rel-18/38_series/38473/b6cee7c106abafe0c3160e285cd68389_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec5897d61c7262a64c5ab81ea7379d5ad8ba7d3f --- /dev/null +++ b/marked/Rel-18/38_series/38473/b6cee7c106abafe0c3160e285cd68389_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f6c5eb83d05e213e8d50d4007d870e045d06198d43ae0f91170f7777b918829 +size 18333 diff --git a/marked/Rel-18/38_series/38473/ba30b0daaa7f0e5a65b4cd8b19c2bbd7_img.jpg b/marked/Rel-18/38_series/38473/ba30b0daaa7f0e5a65b4cd8b19c2bbd7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d141f3cb165107cd097ed0f076db3a37ac333dd --- /dev/null +++ b/marked/Rel-18/38_series/38473/ba30b0daaa7f0e5a65b4cd8b19c2bbd7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce018ab1ec640b34ca00870c6bf376447387a7a6f4ffdd7b0077ab8a8ef2ae65 +size 17740 diff --git a/marked/Rel-18/38_series/38473/bdbdf9152f5224e9ced4fc6f402fbe45_img.jpg b/marked/Rel-18/38_series/38473/bdbdf9152f5224e9ced4fc6f402fbe45_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..134f8c469ba5fc7dd13f5f25ada6122a1173d1c0 --- /dev/null +++ b/marked/Rel-18/38_series/38473/bdbdf9152f5224e9ced4fc6f402fbe45_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:685c4ae345e92a927035dd194c49466dc570bbb6340c90e117258cd94b1726cb +size 18127 diff --git a/marked/Rel-18/38_series/38473/be4ddda9589307e95f8145ad3a4de7f6_img.jpg b/marked/Rel-18/38_series/38473/be4ddda9589307e95f8145ad3a4de7f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c128df7bf3c9b1941302cb058e2ea941f345785 --- /dev/null +++ b/marked/Rel-18/38_series/38473/be4ddda9589307e95f8145ad3a4de7f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:941fed0c8ef5e1738541c67ee7adc12c09eac5d265a2a58276441c3f1c266dd8 +size 18967 diff --git a/marked/Rel-18/38_series/38473/bf333cb2e46bdfbdd321c2227dd84155_img.jpg b/marked/Rel-18/38_series/38473/bf333cb2e46bdfbdd321c2227dd84155_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bcfb3b447cbe4bf72421e2a7496777d683ba040 --- /dev/null +++ b/marked/Rel-18/38_series/38473/bf333cb2e46bdfbdd321c2227dd84155_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2729a6f3cec2b431b206fed8de024b4dedb6de0635503d5abb4051afbce81b77 +size 30055 diff --git a/marked/Rel-18/38_series/38473/c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg b/marked/Rel-18/38_series/38473/c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99f5591f341357c9a841c8890686f787f03aca34 --- /dev/null +++ b/marked/Rel-18/38_series/38473/c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2dffac5294ec4296357fd021cca36635ef9ab23ce259be2083a2e0a4523406df +size 16903 diff --git a/marked/Rel-18/38_series/38473/c11773d09ceffdb3b486f2055afa7c3c_img.jpg b/marked/Rel-18/38_series/38473/c11773d09ceffdb3b486f2055afa7c3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da236c26737473bf120834497f87fa17167d1f40 --- /dev/null +++ b/marked/Rel-18/38_series/38473/c11773d09ceffdb3b486f2055afa7c3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad9718fe669d3da94ac844e0fa30fcaffd5a2685b2e5113680f2795236e03d2b +size 16662 diff --git a/marked/Rel-18/38_series/38473/c1bfc6f877096c926ff17698a7fb919c_img.jpg b/marked/Rel-18/38_series/38473/c1bfc6f877096c926ff17698a7fb919c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be2a7750347b259eae2023d3b0f0c68046c1d7c0 --- /dev/null +++ b/marked/Rel-18/38_series/38473/c1bfc6f877096c926ff17698a7fb919c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e6d4801aa2a988ac4652d292c722b935274ca035d3972f4270b29b18e6a9ded +size 17519 diff --git a/marked/Rel-18/38_series/38473/c30bb9931a85960eb2e2008db772955c_img.jpg b/marked/Rel-18/38_series/38473/c30bb9931a85960eb2e2008db772955c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ea491c75d88a323f0310a51b9fa1337e14d2825 --- /dev/null +++ b/marked/Rel-18/38_series/38473/c30bb9931a85960eb2e2008db772955c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e01702265f2ae655b5c16344ab28140cb853deb6518a1ed00c0ec8651da9ed7 +size 26393 diff --git a/marked/Rel-18/38_series/38473/c46d463fc2af2c2a6a6a3f9d0cea1c5e_img.jpg b/marked/Rel-18/38_series/38473/c46d463fc2af2c2a6a6a3f9d0cea1c5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..568140514af4873ecac0ea18b2c714f6743f49ce --- /dev/null +++ b/marked/Rel-18/38_series/38473/c46d463fc2af2c2a6a6a3f9d0cea1c5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f26ae725b76e857b3619a70c8eced8235fffb20b1e2e4ed0e2535a0681be98f +size 18910 diff --git a/marked/Rel-18/38_series/38473/c5424b117a719524c619938e97c4cb1f_img.jpg b/marked/Rel-18/38_series/38473/c5424b117a719524c619938e97c4cb1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc8160b9ea33621a61e92c8bc75d73f2d102db66 --- /dev/null +++ b/marked/Rel-18/38_series/38473/c5424b117a719524c619938e97c4cb1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:499bf55c61051a00759dd8d83a193d672d6804d3999d7edddd58fcb14b4954ea +size 28875 diff --git a/marked/Rel-18/38_series/38473/c686c005fef31702c109f5d9dd975413_img.jpg b/marked/Rel-18/38_series/38473/c686c005fef31702c109f5d9dd975413_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18635b633ba81b4b5e3c0f5e0bb71577d057aa36 --- /dev/null +++ b/marked/Rel-18/38_series/38473/c686c005fef31702c109f5d9dd975413_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ffa68fd6db9bad2f33b09fd6f753d4780f18a79fa8ccdc4741733b2c5c600004 +size 12155 diff --git a/marked/Rel-18/38_series/38473/c973a830a03be42682a331ad3215d6c6_img.jpg b/marked/Rel-18/38_series/38473/c973a830a03be42682a331ad3215d6c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6ee028fc7688b496f3d7c92ab6bfd8639b24846 --- /dev/null +++ b/marked/Rel-18/38_series/38473/c973a830a03be42682a331ad3215d6c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91e8676ed5340e5cb61e0eca3f769163be0f241afa753337bc9be91bcd2a6194 +size 25514 diff --git a/marked/Rel-18/38_series/38473/ca22c6236ae7c9a8e76d79c469c452a6_img.jpg b/marked/Rel-18/38_series/38473/ca22c6236ae7c9a8e76d79c469c452a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e71e6df275773127bd8a37ee7bd5c3d4ab08ba9 --- /dev/null +++ b/marked/Rel-18/38_series/38473/ca22c6236ae7c9a8e76d79c469c452a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2f54f660be61fe18a990a0aad47624d6d2d55060b378aa48fec5333b656b659 +size 17938 diff --git a/marked/Rel-18/38_series/38473/cc542843836eecb036b99cb270b54a1e_img.jpg b/marked/Rel-18/38_series/38473/cc542843836eecb036b99cb270b54a1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc9baf8515e778ee5cf8d69fff79b17dee8e4767 --- /dev/null +++ b/marked/Rel-18/38_series/38473/cc542843836eecb036b99cb270b54a1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd40747a90e047fdab6a8c914d4720f8554ab25a16a246a8a77af3676b3d2808 +size 19017 diff --git a/marked/Rel-18/38_series/38473/cef981f48160da6ca248560bbf31eb7f_img.jpg b/marked/Rel-18/38_series/38473/cef981f48160da6ca248560bbf31eb7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd2d6c8716e8d6727a4026f931812200764db3de --- /dev/null +++ b/marked/Rel-18/38_series/38473/cef981f48160da6ca248560bbf31eb7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b13f8317d1e84f34514c2c96ff8cdbf3a20492a93684d801061a8656b056164d +size 34047 diff --git a/marked/Rel-18/38_series/38473/d21ff621d2cff0d2b4b5a97009b23eb3_img.jpg b/marked/Rel-18/38_series/38473/d21ff621d2cff0d2b4b5a97009b23eb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53582f9f6210b0ac772a5adf1ad02e3f63089bcd --- /dev/null +++ b/marked/Rel-18/38_series/38473/d21ff621d2cff0d2b4b5a97009b23eb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bd265e9078146f1f59efccbc22c31a2ac1dbc0436dabcc6e243fbec4f3f748c +size 16599 diff --git a/marked/Rel-18/38_series/38473/d50bad97997c6e68494503b621da25b6_img.jpg b/marked/Rel-18/38_series/38473/d50bad97997c6e68494503b621da25b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e76bad3c69d296a8bfb1c9d8ad3038746c631f6a --- /dev/null +++ b/marked/Rel-18/38_series/38473/d50bad97997c6e68494503b621da25b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:424f63e105d33aa6bb72bf1e3436c2642ae868310dbca3497a332ef1be7ab405 +size 16223 diff --git a/marked/Rel-18/38_series/38473/d78e519e9186d30807342196675fd440_img.jpg b/marked/Rel-18/38_series/38473/d78e519e9186d30807342196675fd440_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5879a35a2a4df9841c507e4726f50b1ac726880c --- /dev/null +++ b/marked/Rel-18/38_series/38473/d78e519e9186d30807342196675fd440_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4cc239160ab5ff4f4ac5cd3a01da47cd265a892e561e8d5d76124d2c98e33b7 +size 20353 diff --git a/marked/Rel-18/38_series/38473/da0e559eb2a247b221a69ce5f49f3b49_img.jpg b/marked/Rel-18/38_series/38473/da0e559eb2a247b221a69ce5f49f3b49_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7b3bff6f919f205aa4ebc3a67c9a5cbc26fa917 --- /dev/null +++ b/marked/Rel-18/38_series/38473/da0e559eb2a247b221a69ce5f49f3b49_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5caf18b2cbbeb8c2fee0d628194001bdf2c68dd2999c590380746f8359bf8a6b +size 22966 diff --git a/marked/Rel-18/38_series/38473/da87c1b628b63a046d8a0d0fc2c058ea_img.jpg b/marked/Rel-18/38_series/38473/da87c1b628b63a046d8a0d0fc2c058ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d9e2d82f82711d68507676aa11acb85e109294a --- /dev/null +++ b/marked/Rel-18/38_series/38473/da87c1b628b63a046d8a0d0fc2c058ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef67d253d5780bd89cbb0998ac8dfe09a6f2e36eb5770c1817bee02f05250198 +size 28682 diff --git a/marked/Rel-18/38_series/38473/db5deafdae53dbc7d5972957f708c691_img.jpg b/marked/Rel-18/38_series/38473/db5deafdae53dbc7d5972957f708c691_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ffad681c04fabde2eed49258a3610018e781a08 --- /dev/null +++ b/marked/Rel-18/38_series/38473/db5deafdae53dbc7d5972957f708c691_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e695aca187097d480efa1bdbb81d33575517cf1baae276ddb5f792136eda1f8f +size 16892 diff --git a/marked/Rel-18/38_series/38473/dd8c4eb490876d1c18169c84d877ef32_img.jpg b/marked/Rel-18/38_series/38473/dd8c4eb490876d1c18169c84d877ef32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d348fa9f37daed0de8349644984a7791d3c35c36 --- /dev/null +++ b/marked/Rel-18/38_series/38473/dd8c4eb490876d1c18169c84d877ef32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4602d2c5d24fdb2f9e73b64981544913ab44c9807e8e7ee6b3454df943687e5c +size 18325 diff --git a/marked/Rel-18/38_series/38473/ddacb7cc501527d4723bdb4c21f9e023_img.jpg b/marked/Rel-18/38_series/38473/ddacb7cc501527d4723bdb4c21f9e023_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab9d981e045eb769604b4506bfa1ccc150c92ae8 --- /dev/null +++ b/marked/Rel-18/38_series/38473/ddacb7cc501527d4723bdb4c21f9e023_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:621dc07031b81d63a846b39ef941f38d21116ff37f6ec73d17cf14d7900665fb +size 33884 diff --git a/marked/Rel-18/38_series/38473/e174d8245c581ea582782d582408074f_img.jpg b/marked/Rel-18/38_series/38473/e174d8245c581ea582782d582408074f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4e4be023a3877298b3ff0c876e68fff463d82fb --- /dev/null +++ b/marked/Rel-18/38_series/38473/e174d8245c581ea582782d582408074f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6391055fa3d296d819149c2166575f34f150a843862ed72b752d3b3c2e1633ed +size 28378 diff --git a/marked/Rel-18/38_series/38473/e1db30df0b66cb06acb3a897e4b00999_img.jpg b/marked/Rel-18/38_series/38473/e1db30df0b66cb06acb3a897e4b00999_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d30357fc6bc69cd614b4d6d90730718fefe130ee --- /dev/null +++ b/marked/Rel-18/38_series/38473/e1db30df0b66cb06acb3a897e4b00999_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f35b2aac832563118488048b3bcabc2ad8efeb734f4c001c789d1a76ee1af8cb +size 31017 diff --git a/marked/Rel-18/38_series/38473/ea105825edba5fe5123a980361334798_img.jpg b/marked/Rel-18/38_series/38473/ea105825edba5fe5123a980361334798_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a89bef5e6d4b9b178727e466612732238ff6848e --- /dev/null +++ b/marked/Rel-18/38_series/38473/ea105825edba5fe5123a980361334798_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf22fcdb123500eaa896a8a99a71a5e4e9b091c07fd4285983be8b5ddf810cac +size 28049 diff --git a/marked/Rel-18/38_series/38473/ed3c94ac94daffb2c1aee0dd37579f50_img.jpg b/marked/Rel-18/38_series/38473/ed3c94ac94daffb2c1aee0dd37579f50_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a79a25ed44233b3682fc4c7d66ccfd63370918bf --- /dev/null +++ b/marked/Rel-18/38_series/38473/ed3c94ac94daffb2c1aee0dd37579f50_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd827f2a5545f6d32bf338b6a22932b35ef12e2c7a8cbbe0c38427a980700f85 +size 15652 diff --git a/marked/Rel-18/38_series/38473/f050e021720d7dbc135e918a25860117_img.jpg b/marked/Rel-18/38_series/38473/f050e021720d7dbc135e918a25860117_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c47fb3def2a8cebc4d863f15b05bb12f06eabfce --- /dev/null +++ b/marked/Rel-18/38_series/38473/f050e021720d7dbc135e918a25860117_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c67bd02a1948051f39f576490998827d32fd5720fe2145f5e465bf88b1a84ded +size 31566 diff --git a/marked/Rel-18/38_series/38473/f087d3f5d298b3b1634d13ff17879e41_img.jpg b/marked/Rel-18/38_series/38473/f087d3f5d298b3b1634d13ff17879e41_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6e9aae0985240dfd901dafa2ca6d62db56618ad --- /dev/null +++ b/marked/Rel-18/38_series/38473/f087d3f5d298b3b1634d13ff17879e41_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:489ca9d587409b1a35cacb48273a05af422bd62375c83685b642fa42559ad9d4 +size 13374 diff --git a/marked/Rel-18/38_series/38473/f0addfb9cb95476594c62d37d1208037_img.jpg b/marked/Rel-18/38_series/38473/f0addfb9cb95476594c62d37d1208037_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6475d01f2b4a1a6aa1dda15d806a44ba98f9ae89 --- /dev/null +++ b/marked/Rel-18/38_series/38473/f0addfb9cb95476594c62d37d1208037_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e0b03804f3cef2c3c7fd50461d4fd714fa6cc66d59bdffd1a43c095ebd145c0 +size 29047 diff --git a/marked/Rel-18/38_series/38473/f3c73e8e478b8b2d9f6a96a970040556_img.jpg b/marked/Rel-18/38_series/38473/f3c73e8e478b8b2d9f6a96a970040556_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d77cbfacddabac51c67bffac319cae197c458022 --- /dev/null +++ b/marked/Rel-18/38_series/38473/f3c73e8e478b8b2d9f6a96a970040556_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03113322833cc0df495168697c31eddb78e0aaa2c16e468a1723865704b9af5b +size 15499 diff --git a/marked/Rel-18/38_series/38473/fb4274c4b7882a4059103f1dbca9b111_img.jpg b/marked/Rel-18/38_series/38473/fb4274c4b7882a4059103f1dbca9b111_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71d6c79b8fcac827b3f49c131c12f3c177fde37b --- /dev/null +++ b/marked/Rel-18/38_series/38473/fb4274c4b7882a4059103f1dbca9b111_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee3cea604fa5b937df65d31257a8a50c7c5dc4d7a782b8f71b17e461da64c731 +size 18738 diff --git a/marked/Rel-18/38_series/38473/fe4312cdd9b42f21c0790c197a9f027c_img.jpg b/marked/Rel-18/38_series/38473/fe4312cdd9b42f21c0790c197a9f027c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c48ca80975394ba03bf5619a46369622a850b84 --- /dev/null +++ b/marked/Rel-18/38_series/38473/fe4312cdd9b42f21c0790c197a9f027c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad88c57064ab9b642bc85150a209141a03bc2df16245f26678f25915e3a86885 +size 14225 diff --git a/marked/Rel-18/38_series/38473/fe7304192caf64cda93b580c5e7e5c06_img.jpg b/marked/Rel-18/38_series/38473/fe7304192caf64cda93b580c5e7e5c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c615f88963a3d7e134426c0552992a0189397be --- /dev/null +++ b/marked/Rel-18/38_series/38473/fe7304192caf64cda93b580c5e7e5c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72f56428f356d361c0b93cb7c7b8ba4c57288fda866fc25a69e36e6570772fb3 +size 30185 diff --git a/marked/Rel-18/38_series/38473/ffe2d3e622dd30bea4caf15951c60e42_img.jpg b/marked/Rel-18/38_series/38473/ffe2d3e622dd30bea4caf15951c60e42_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32f377ad84d213890a611ec77eee83e904d7ec16 --- /dev/null +++ b/marked/Rel-18/38_series/38473/ffe2d3e622dd30bea4caf15951c60e42_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c0b0be6c239394feabc1a51fd25a68122fd55930448096fe0593226b9a77d13 +size 22266 diff --git a/marked/Rel-18/38_series/38473/raw.md b/marked/Rel-18/38_series/38473/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8570b15f29c56207e3561927b77ed4b243acbb59 --- /dev/null +++ b/marked/Rel-18/38_series/38473/raw.md @@ -0,0 +1,39814 @@ + + +# 3GPP TS 38.473 V18.0.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP) (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. + +Keywords +NG-RAN, Radio + +**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..... | 19 | +| 1 Scope..... | 20 | +| 2 References..... | 20 | +| 3 Definitions and abbreviations..... | 22 | +| 3.1 Definitions..... | 22 | +| 3.2 Abbreviations..... | 24 | +| 4 General..... | 25 | +| 4.1 Procedure specification principles..... | 25 | +| 4.2 Forwards and backwards compatibility..... | 25 | +| 4.3 Specification notations..... | 25 | +| 5 F1AP services..... | 26 | +| 6 Services expected from signalling transport..... | 26 | +| 7 Functions of F1AP..... | 26 | +| 8 F1AP procedures..... | 26 | +| 8.1 List of F1AP Elementary procedures..... | 26 | +| 8.2 Interface Management procedures..... | 30 | +| 8.2.1 Reset..... | 30 | +| 8.2.1.1 General..... | 30 | +| 8.2.1.2 Successful Operation..... | 30 | + +## **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..... | 30 | +| 8.2.1.2.2 | Reset Procedure Initiated from the gNB-DU..... | 31 | +| 8.2.1.3 | Abnormal Conditions..... | 32 | +| 8.2.2 | Error Indication..... | 32 | +| 8.2.2.1 | General..... | 32 | +| 8.2.2.2 | Successful Operation..... | 32 | +| 8.2.2.3 | Abnormal Conditions..... | 32 | +| 8.2.3 | F1 Setup..... | 33 | +| 8.2.3.1 | General..... | 33 | +| 8.2.3.2 | Successful Operation..... | 33 | +| 8.2.3.3 | Unsuccessful Operation..... | 35 | +| 8.2.3.4 | Abnormal Conditions..... | 35 | +| 8.2.4 | gNB-DU Configuration Update..... | 35 | +| 8.2.4.1 | General..... | 35 | +| 8.2.4.2 | Successful Operation..... | 36 | +| 8.2.4.3 | Unsuccessful Operation..... | 39 | +| 8.2.4.4 | Abnormal Conditions..... | 39 | +| 8.2.5 | gNB-CU Configuration Update..... | 39 | +| 8.2.5.1 | General..... | 39 | +| 8.2.5.2 | Successful Operation..... | 39 | +| 8.2.5.3 | Unsuccessful Operation..... | 42 | +| 8.2.5.4 | Abnormal Conditions..... | 42 | +| 8.2.6 | gNB-DU Resource Coordination..... | 42 | +| 8.2.6.1 | General..... | 42 | +| 8.2.6.2 | Successful Operation..... | 43 | +| 8.2.7 | gNB-DU Status Indication..... | 43 | +| 8.2.7.1 | General..... | 43 | +| 8.2.7.2 | Successful Operation..... | 43 | +| 8.2.7.3 | Abnormal Conditions..... | 44 | +| 8.2.8 | F1 Removal..... | 44 | + +| | | | +|----------|-------------------------------------------|----| +| 8.2.8.1 | General..... | 44 | +| 8.2.8.2 | Successful Operation..... | 44 | +| 8.2.8.3 | Unsuccessful Operation..... | 45 | +| 8.2.8.4 | Abnormal Conditions..... | 45 | +| 8.2.9 | Network Access Rate Reduction..... | 45 | +| 8.2.9.1 | General..... | 45 | +| 8.2.9.2 | Successful operation..... | 46 | +| 8.2.9.3 | Abnormal Conditions..... | 46 | +| 8.2.10 | Resource Status Reporting Initiation..... | 46 | +| 8.2.10.1 | General..... | 46 | +| 8.2.10.2 | Successful Operation..... | 46 | +| 8.2.10.3 | Unsuccessful Operation..... | 48 | +| 8.2.10.4 | Abnormal Conditions..... | 48 | +| 8.2.11 | Resource Status Reporting..... | 48 | +| 8.2.11.1 | General..... | 48 | +| 8.2.11.2 | Successful Operation..... | 48 | +| 8.2.11.3 | Unsuccessful Operation..... | 49 | +| 8.2.11.4 | Abnormal Conditions..... | 49 | +| 8.2.12 | DU-CU TA Information Transfer..... | 49 | +| 8.2.12.1 | General..... | 49 | +| 8.2.12.2 | Successful Operation..... | 49 | +| 8.2.12.3 | Unsuccessful Operation..... | 49 | +| 8.2.12.4 | Abnormal Conditions..... | 49 | +| 8.2.13 | CU-DU TA Information Transfer..... | 49 | +| 8.2.13.1 | General..... | 49 | +| 8.2.13.2 | Successful Operation..... | 50 | +| 8.2.13.3 | Unsuccessful Operation..... | 50 | +| 8.2.13.4 | Abnormal Conditions..... | 50 | +| 8.2.14 | RACH Indication..... | 50 | +| 8.2.14.1 | General..... | 50 | + +| | | | +|----------|----------------------------------------------------------|----| +| 8.2.14.2 | Successful Operation..... | 50 | +| 8.2.14.3 | Abnormal Conditions..... | 51 | +| 8.3 | UE Context Management procedures..... | 51 | +| 8.3.1 | UE Context Setup..... | 51 | +| 8.3.1.1 | General..... | 51 | +| 8.3.1.2 | Successful Operation..... | 51 | +| 8.3.1.3 | Unsuccessful Operation..... | 60 | +| 8.3.1.4 | Abnormal Conditions..... | 60 | +| 8.3.2 | UE Context Release Request (gNB-DU initiated)..... | 60 | +| 8.3.2.1 | General..... | 60 | +| 8.3.2.2 | Successful Operation..... | 61 | +| 8.3.2.3 | Abnormal Conditions..... | 61 | +| 8.3.3 | UE Context Release (gNB-CU initiated)..... | 61 | +| 8.3.3.1 | General..... | 61 | +| 8.3.3.2 | Successful Operation..... | 62 | +| 8.3.3.4 | Abnormal Conditions..... | 62 | +| 8.3.4 | UE Context Modification (gNB-CU initiated)..... | 63 | +| 8.3.4.1 | General..... | 63 | +| 8.3.4.2 | Successful Operation..... | 63 | +| 8.3.4.3 | Unsuccessful Operation..... | 75 | +| 8.3.4.4 | Abnormal Conditions..... | 76 | +| 8.3.5 | UE Context Modification Required (gNB-DU initiated)..... | 76 | +| 8.3.5.1 | General..... | 76 | +| 8.3.5.2 | Successful Operation..... | 77 | +| 8.3.5.2A | Unsuccessful Operation..... | 78 | +| 8.3.5.3 | Abnormal Conditions..... | 79 | +| 8.3.6 | UE Inactivity Notification..... | 79 | +| 8.3.6.1 | General..... | 79 | +| 8.3.6.2 | Successful Operation..... | 79 | +| 8.3.6.3 | Abnormal Conditions..... | 79 | + +| | | | +|-------------------------|--------------------------------------|----| +| 8.3.7 | Notify..... | 79 | +| 8.3.7.1 | General..... | 79 | +| 8.3.7.2 | Successful Operation..... | 80 | +| 8.3.7.3 | Abnormal Conditions..... | 80 | +| 8.3.8 | Access Success..... | 80 | +| 8.3.8.1 | General..... | 80 | +| 8.3.8.2 | Successful Operation..... | 80 | +| 8.3.8.3 | Abnormal Conditions..... | 81 | +| 8.3.9 | DU-CU Cell Switch Notification..... | 81 | +| 8.3.9.1 | General..... | 81 | +| 8.3.9.2 | Successful Operation..... | 81 | +| 8.3.9.3 | Unsuccessful Operation..... | 81 | +| 8.3.9.4 | Abnormal Conditions..... | 81 | +| Not applicable.8.3.10 | CU-DU Cell Switch Notification..... | 81 | +| 8.3.10.1 | General..... | 81 | +| 8.3.10.2 | Successful Operation..... | 82 | +| 8.3.10.3 | Unsuccessful Operation..... | 82 | +| Not applicable.8.3.10.4 | Abnormal Conditions..... | 82 | +| 8.4 | RRC Message Transfer procedures..... | 82 | +| 8.4.1 | Initial UL RRC Message Transfer..... | 82 | +| 8.4.1.1 | General..... | 82 | +| 8.4.1.2 | Successful operation..... | 82 | +| 8.4.1.3 | Abnormal Conditions..... | 83 | +| 8.4.2 | DL RRC Message Transfer..... | 83 | +| 8.4.2.1 | General..... | 83 | +| 8.4.2.2 | Successful operation..... | 83 | +| 8.4.2.3 | Abnormal Conditions..... | 84 | +| 8.4.3 | UL RRC Message Transfer..... | 84 | +| 8.4.3.1 | General..... | 84 | +| 8.4.3.2 | Successful operation..... | 84 | + +| | | | +|---------|----------------------------------------------|----| +| 8.4.3.3 | Abnormal Conditions..... | 85 | +| 8.4.4 | RRC Delivery Report..... | 85 | +| 8.4.4.1 | General..... | 85 | +| 8.4.4.2 | Successful operation..... | 85 | +| 8.4.4.3 | Abnormal Conditions..... | 85 | +| 8.5 | Warning Message Transmission Procedures..... | 85 | +| 8.5.1 | Write-Replace Warning..... | 85 | +| 8.5.1.1 | General..... | 85 | +| 8.5.1.2 | Successful Operation..... | 86 | +| 8.5.1.3 | Unsuccessful Operation..... | 86 | +| 8.5.1.4 | Abnormal Conditions..... | 86 | +| 8.5.2 | PWS Cancel..... | 87 | +| 8.5.2.1 | General..... | 87 | +| 8.5.2.2 | Successful Operation..... | 87 | +| 8.5.2.3 | Unsuccessful Operation..... | 87 | +| 8.5.2.4 | Abnormal Conditions..... | 87 | +| 8.5.3 | PWS Restart Indication..... | 88 | +| 8.5.3.1 | General..... | 88 | +| 8.5.3.2 | Successful Operation..... | 88 | +| 8.5.3.3 | Abnormal Conditions..... | 88 | +| 8.5.4 | PWS Failure Indication..... | 88 | +| 8.5.4.1 | General..... | 88 | +| 8.5.4.2 | Successful Operation..... | 88 | +| 8.5.4.3 | Abnormal Conditions..... | 88 | +| 8.6 | System Information Procedures..... | 89 | +| 8.6.1 | System Information Delivery..... | 89 | +| 8.6.1.1 | General..... | 89 | +| 8.6.1.2 | Successful Operation..... | 89 | +| 8.6.1.3 | Abnormal Conditions..... | 89 | +| 8.7 | Paging procedures..... | 89 | + +| | | | +|----------|--------------------------------------------|----| +| 8.7.1 | Paging..... | 89 | +| 8.7.1.1 | General..... | 89 | +| 8.7.1.2 | Successful Operation..... | 90 | +| 8.7.1.3 | Abnormal Conditions..... | 91 | +| 8.8 | Trace Procedures..... | 91 | +| 8.8.1 | Trace Start..... | 91 | +| 8.8.1.1 | General..... | 91 | +| 8.8.1.2 | Successful Operation..... | 91 | +| 8.8.1.3 | Abnormal Conditions..... | 91 | +| 8.8.2 | Deactivate Trace..... | 92 | +| 8.8.2.1 | General..... | 92 | +| 8.8.2.2 | Successful Operation..... | 92 | +| 8.8.2.3 | Abnormal Conditions..... | 92 | +| 8.8.3 | Cell Traffic Trace..... | 92 | +| 8.8.3.1 | General..... | 92 | +| 8.8.3.2 | Successful Operation..... | 92 | +| 8.8.3.3 | Abnormal Conditions..... | 92 | +| 8.9 | Radio Information Transfer procedures..... | 93 | +| 8.9.1 | DU-CU Radio Information Transfer..... | 93 | +| 8.9.1.1 | General..... | 93 | +| 8.9.1.2 | Successful operation..... | 93 | +| 8.9.1.3 | Abnormal Conditions..... | 93 | +| 8.9.2 | CU-DU Radio Information Transfer..... | 93 | +| 8.9.2.1 | General..... | 93 | +| 8.9.2.2 | Successful operation..... | 93 | +| 8.9.2.3 | Abnormal Conditions..... | 94 | +| 8.10 | IAB Procedures..... | 94 | +| 8.10.0 | General..... | 94 | +| 8.10.1 | BAP Mapping Configuration..... | 94 | +| 8.10.1.1 | General..... | 94 | + +| | | | +|----------|-----------------------------------------------|-----| +| 8.10.1.2 | Successful Operation..... | 94 | +| 8.10.1.A | Unsuccessful Operation..... | 95 | +| 8.10.1.3 | Abnormal Conditions..... | 95 | +| 8.10.2 | gNB-DU Resource Configuration..... | 95 | +| 8.10.2.1 | General..... | 95 | +| 8.10.2.2 | Successful Operation..... | 96 | +| 8.10.2.B | Unsuccessful Operation..... | 96 | +| 8.10.2.3 | Abnormal Conditions..... | 97 | +| 8.10.3 | IAB TNL Address Allocation..... | 97 | +| 8.10.3.1 | General..... | 97 | +| 8.10.3.2 | Successful Operation..... | 97 | +| 8.10.3.C | Unsuccessful Operation..... | 98 | +| 8.10.3.3 | Abnormal Conditions..... | 98 | +| 8.10.4 | IAB UP Configuration Update..... | 98 | +| 8.10.4.1 | General..... | 98 | +| 8.10.4.2 | Successful Operation..... | 98 | +| 8.10.4.3 | Unsuccessful Operation..... | 99 | +| 8.10.4.4 | Abnormal Conditions..... | 99 | +| 8.10.5 | Mobile IAB F1 Setup Triggering..... | 99 | +| 8.10.5.1 | General..... | 99 | +| 8.10.5.2 | Successful Operation..... | 100 | +| 8.10.5.3 | Abnormal Conditions..... | 100 | +| 8.10.6 | Mobile IAB F1 Setup Outcome Notification..... | 100 | +| 8.10.6.1 | General..... | 100 | +| 8.10.6.2 | Successful Operation..... | 100 | +| 8.10.6.3 | Abnormal Conditions..... | 101 | +| 8.11 | Self Optimisation Support procedures..... | 101 | +| 8.11.1 | Access and Mobility Indication..... | 101 | +| 8.11.1.1 | General..... | 101 | +| 8.11.1.2 | Successful Operation..... | 101 | + +| | | | +|----------|------------------------------------------------------|-----| +| 8.11.1.3 | Abnormal Conditions..... | 102 | +| 8.12 | Reference Time Information Reporting procedures..... | 102 | +| 8.12.1 | Reference Time Information Reporting Control..... | 102 | +| 8.12.1.1 | General..... | 102 | +| 8.12.1.2 | Successful Operation..... | 102 | +| 8.12.1.3 | Abnormal Conditions..... | 102 | +| 8.12.2 | Reference Time Information Report..... | 102 | +| 8.12.2.1 | General..... | 102 | +| 8.12.2.2 | Successful Operation..... | 103 | +| 8.12.2.3 | Abnormal Conditions..... | 103 | +| 8.13 | Positioning Procedures..... | 103 | +| 8.13.1 | Positioning Assistance Information Control..... | 103 | +| 8.13.1.1 | General..... | 103 | +| 8.13.1.2 | Successful Operation..... | 103 | +| 8.13.1.3 | Abnormal Conditions..... | 104 | +| 8.13.2 | Positioning Assistance Information Feedback..... | 104 | +| 8.13.2.1 | General..... | 104 | +| 8.13.2.2 | Successful Operation..... | 104 | +| 8.13.2.3 | Abnormal Conditions..... | 104 | +| 8.13.3 | Positioning Measurement..... | 105 | +| 8.13.3.1 | General..... | 105 | +| 8.13.3.2 | Successful Operation..... | 105 | +| 8.13.3.3 | Unsuccessful Operation..... | 106 | +| 8.13.3.4 | Abnormal Conditions..... | 106 | +| 8.13.4 | Positioning Measurement Report..... | 106 | +| 8.13.4.1 | General..... | 106 | +| 8.13.4.2 | Successful Operation..... | 106 | +| 8.13.4.3 | Unsuccessful Operation..... | 107 | +| 8.13.4.4 | Abnormal Conditions..... | 107 | +| 8.13.5 | Positioning Measurement Abort..... | 107 | + +| | | | +|-----------|-------------------------------------------------|-----| +| 8.13.5.1 | General..... | 107 | +| 8.13.5.2 | Successful Operation..... | 107 | +| 8.13.5.3 | Unsuccessful Operation..... | 107 | +| 8.13.5.4 | Abnormal Conditions..... | 107 | +| 8.13.6 | Positioning Measurement Failure Indication..... | 107 | +| 8.13.6.1 | General..... | 107 | +| 8.13.6.2 | Successful Operation..... | 108 | +| 8.13.6.3 | Unsuccessful Operation..... | 108 | +| 8.13.6.4 | Abnormal Conditions..... | 108 | +| 8.13.7 | Positioning Measurement Update..... | 108 | +| 8.13.7.1 | General..... | 108 | +| 8.13.7.2 | Successful Operation..... | 108 | +| 8.13.7.3 | Unsuccessful Operation..... | 109 | +| 8.13.7.4 | Abnormal Conditions..... | 109 | +| 8.13.8 | TRP Information Exchange..... | 109 | +| 8.13.8.1 | General..... | 109 | +| 8.13.8.2 | Successful Operation..... | 109 | +| 8.13.8.3 | Unsuccessful Operation..... | 110 | +| 8.13.9 | Positioning Information Exchange..... | 110 | +| 8.13.9.1 | General..... | 110 | +| 8.13.9.2 | Successful Operation..... | 110 | +| 8.13.9.3 | Unsuccessful Operation..... | 111 | +| 8.13.10 | Positioning Activation..... | 111 | +| 8.13.10.1 | General..... | 111 | +| 8.13.10.2 | Successful Operation..... | 111 | +| 8.13.10.3 | Unsuccessful Operation..... | 112 | +| 8.13.10.4 | Abnormal Conditions..... | 112 | +| 8.13.11 | Positioning Deactivation..... | 112 | +| 8.13.11.1 | General..... | 112 | +| 8.13.11.2 | Successful Operation..... | 113 | + +| | | | +|-----------|-------------------------------------------|-----| +| 8.13.11.3 | Unsuccessful Operation..... | 113 | +| 8.13.11.4 | Abnormal Conditions..... | 113 | +| 8.13.12 | E-CID Measurement Initiation..... | 113 | +| 8.13.12.1 | General..... | 113 | +| 8.13.12.2 | Successful Operation..... | 113 | +| 8.13.12.3 | Unsuccessful Operation..... | 114 | +| 8.13.13 | E-CID Measurement Failure Indication..... | 114 | +| 8.13.13.1 | General..... | 114 | +| 8.13.13.2 | Successful Operation..... | 114 | +| 8.13.13.3 | Unsuccessful Operation..... | 114 | +| 8.13.14 | E-CID Measurement Report..... | 115 | +| 8.13.14.1 | General..... | 115 | +| 8.13.14.2 | Successful Operation..... | 115 | +| 8.13.14.3 | Unsuccessful Operation..... | 115 | +| 8.13.15 | E-CID Measurement Termination..... | 115 | +| 8.13.15.1 | General..... | 115 | +| 8.13.15.2 | Successful Operation..... | 115 | +| 8.13.15.3 | Unsuccessful Operation..... | 116 | +| 8.13.16 | Positioning Information Update..... | 116 | +| 8.13.16.1 | General..... | 116 | +| 8.13.16.2 | Successful Operation..... | 116 | +| 8.13.16.3 | Unsuccessful Operation..... | 116 | +| 8.13.16.4 | Abnormal Conditions..... | 116 | +| 8.13.17 | PRS Configuration Exchange..... | 116 | +| 8.13.17.1 | General..... | 116 | +| 8.13.17.2 | Successful Operation..... | 117 | +| 8.13.17.3 | Unsuccessful Operation..... | 117 | +| 8.13.17.4 | Abnormal Conditions..... | 117 | +| 8.13.18 | Measurement Preconfiguration..... | 117 | +| 8.13.18.1 | General..... | 117 | + +| | | | +|-----------|----------------------------------------------|-----| +| 8.13.18.2 | Successful Operation..... | 118 | +| 8.13.18.3 | Unsuccessful Operation..... | 118 | +| 8.13.19 | Measurement Activation..... | 118 | +| 8.13.19.1 | General..... | 118 | +| 8.13.19.2 | Successful Operation..... | 119 | +| 8.13.19.3 | Unsuccessful Operation..... | 119 | +| 8.13.20 | Positioning System Information Delivery..... | 119 | +| 8.13.20.1 | General..... | 119 | +| 8.13.20.2 | Successful Operation..... | 119 | +| 8.13.20.3 | Abnormal Conditions..... | 120 | +| 8.14 | NR MBS Procedures..... | 120 | +| 8.14.1 | Broadcast Context Setup..... | 120 | +| 8.14.1.1 | General..... | 120 | +| 8.14.1.2 | Successful Operation..... | 120 | +| 8.14.1.3 | Unsuccessful Operation..... | 121 | +| 8.14.1.4 | Abnormal Conditions..... | 121 | +| 8.14.2 | Broadcast Context Release..... | 121 | +| 8.14.2.1 | General..... | 121 | +| 8.14.2.2 | Successful Operation..... | 121 | +| 8.14.2.3 | Unsuccessful Operation..... | 122 | +| 8.14.2.4 | Abnormal Conditions..... | 122 | +| 8.14.3 | Broadcast Context Release Request..... | 122 | +| 8.14.3.1 | General..... | 122 | +| 8.14.3.2 | Successful Operation..... | 122 | +| 8.14.3.3 | Unsuccessful Operation..... | 122 | +| 8.14.3.4 | Abnormal Conditions..... | 122 | +| 8.14.4 | Broadcast Context Modification..... | 123 | +| 8.14.4.1 | General..... | 123 | +| 8.14.4.2 | Successful Operation..... | 123 | +| 8.14.4.3 | Unsuccessful Operation..... | 124 | + +| | | | +|-----------|----------------------------------------|-----| +| 8.14.4.4 | Abnormal Conditions..... | 124 | +| 8.14.5 | Multicast Group Paging..... | 124 | +| 8.14.5.1 | General..... | 124 | +| 8.14.5.2 | Successful Operation..... | 125 | +| 8.14.5.3 | Abnormal Conditions..... | 125 | +| 8.14.6 | Multicast Context Setup..... | 125 | +| 8.14.6.1 | General..... | 125 | +| 8.14.6.2 | Successful Operation..... | 125 | +| 8.14.6.3 | Unsuccessful Operation..... | 126 | +| 8.14.6.4 | Abnormal Conditions..... | 126 | +| 8.14.7 | Multicast Context Release..... | 126 | +| 8.14.7.1 | General..... | 126 | +| 8.14.7.2 | Successful Operation..... | 127 | +| 8.14.7.3 | Unsuccessful Operation..... | 127 | +| 8.14.7.4 | Abnormal Conditions..... | 127 | +| 8.14.8 | Multicast Context Release Request..... | 127 | +| 8.14.8.1 | General..... | 127 | +| 8.14.8.2 | Successful Operation..... | 127 | +| 8.14.8.3 | Unsuccessful Operation..... | 128 | +| 8.14.8.4 | Abnormal Conditions..... | 128 | +| 8.14.9 | Multicast Context Modification..... | 128 | +| 8.14.9.1 | General..... | 128 | +| 8.14.9.2 | Successful Operation..... | 128 | +| 8.14.9.3 | Unsuccessful Operation..... | 129 | +| 8.14.9.4 | Abnormal Conditions..... | 129 | +| 8.14.10 | Multicast Distribution Setup..... | 129 | +| 8.14.10.1 | General..... | 129 | +| 8.14.10.2 | Successful Operation..... | 130 | +| 8.14.10.3 | Unsuccessful Operation..... | 130 | +| 8.14.10.4 | Abnormal Conditions..... | 130 | + +| | | | +|-----------|-------------------------------------------|-----| +| 8.14.11 | Multicast Distribution Release..... | 131 | +| 8.14.11.1 | General..... | 131 | +| 8.14.11.2 | Successful Operation..... | 131 | +| 8.14.11.3 | Unsuccessful Operation..... | 131 | +| 8.14.11.4 | Abnormal Conditions..... | 131 | +| 8.14.12 | Multicast Context Notification..... | 131 | +| 8.14.12.1 | General..... | 131 | +| 8.14.12.2 | Successful Operation..... | 132 | +| 8.14.12.3 | Unsuccessful Operation..... | 132 | +| 8.14.12.4 | Abnormal Conditions..... | 132 | +| 8.14.13 | Multicast Common Configuration..... | 132 | +| 8.14.13.1 | General..... | 132 | +| 8.14.13.2 | Successful Operation..... | 133 | +| 8.14.13.3 | Unsuccessful Operation..... | 133 | +| 8.14.13.4 | Abnormal Conditions..... | 133 | +| 8.14.14 | Broadcast Transport Resource Request..... | 133 | +| 8.14.14.1 | General..... | 133 | +| 8.14.14.2 | Successful Operation..... | 134 | +| 8.14.14.3 | Unsuccessful Operation..... | 134 | +| 8.14.14.4 | Abnormal Conditions..... | 134 | +| 8.15 | PDC Measurement Reporting procedures..... | 134 | +| 8.15.1 | PDC Measurement Initiation..... | 134 | +| 8.15.1.1 | General..... | 134 | +| 8.15.1.2 | Successful Operation..... | 134 | +| 8.15.1.3 | Unsuccessful Operation..... | 135 | +| 8.15.2 | PDC Measurement Report..... | 135 | +| 8.15.2.1 | General..... | 135 | +| 8.15.2.2 | Successful Operation..... | 135 | +| 8.15.2.3 | Unsuccessful Operation..... | 136 | +| 8.15.3 | PDC Measurement Termination..... | 136 | + +| | | | +|----------|---------------------------------------------------------|-----| +| 8.15.3.1 | General..... | 136 | +| 8.15.3.2 | Successful Operation..... | 136 | +| 8.15.3.3 | Unsuccessful Operation..... | 136 | +| 8.15.3.4 | Abnormal Conditions..... | 136 | +| 8.15.4 | PDC Measurement Failure Indication..... | 136 | +| 8.15.4.1 | General..... | 136 | +| 8.15.4.2 | Successful Operation..... | 136 | +| 8.15.4.3 | Unsuccessful Operation..... | 137 | +| 8.15.4.4 | Abnormal Conditions..... | 137 | +| 8.16 | QMC Procedures..... | 137 | +| 8.16.1 | QoE Information Transfer..... | 137 | +| 8.16.1.1 | General..... | 137 | +| 8.16.1.2 | Successful operation..... | 137 | +| 8.16.1.3 | Abnormal Conditions..... | 137 | +| 8.16.2 | QoE Information Transfer Control..... | 137 | +| 8.16.2.1 | General..... | 137 | +| 8.16.2.2 | Successful operation..... | 138 | +| 8.16.2.3 | Abnormal Conditions..... | 138 | +| 8.17 | Timing Synchronisation Status Reporting Procedures..... | 138 | +| 8.17.1 | Timing Synchronisation Status..... | 138 | +| 8.17.1.1 | General..... | 138 | +| 8.17.1.2 | Successful Operation..... | 138 | +| 8.17.1.3 | Unsuccessful Operation..... | 139 | +| 8.17.1.4 | Abnormal Conditions..... | 139 | +| 8.17.2 | Timing Synchronisation Status Report..... | 139 | +| 8.17.2.1 | General..... | 139 | +| 8.17.2.2 | Successful Operation..... | 139 | +| 8.17.2.3 | Abnormal Conditions..... | 139 | +| 9 | Elements for FIAP Communication..... | 140 | +| 9.1 | General..... | 140 | + +| | | | +|----------|------------------------------------------------|-----| +| 9.2 | Message Functional Definition and Content..... | 140 | +| 9.2.1 | Interface Management messages..... | 140 | +| 9.2.1.1 | RESET..... | 140 | +| 9.2.1.2 | RESET ACKNOWLEDGE..... | 141 | +| 9.2.1.3 | ERROR INDICATION..... | 141 | +| 9.2.1.4 | F1 SETUP REQUEST..... | 141 | +| 9.2.1.5 | F1 SETUP RESPONSE..... | 142 | +| 9.2.1.6 | F1 SETUP FAILURE..... | 144 | +| 9.2.1.7 | GNB-DU CONFIGURATION UPDATE..... | 144 | +| 9.2.1.8 | GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE..... | 145 | +| 9.2.1.9 | GNB-DU CONFIGURATION UPDATE FAILURE..... | 147 | +| 9.2.1.10 | GNB-CU CONFIGURATION UPDATE..... | 147 | +| 9.2.1.11 | GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE..... | 150 | +| 9.2.1.12 | GNB-CU CONFIGURATION UPDATE FAILURE..... | 152 | +| 9.2.1.13 | GNB-DU RESOURCE COORDINATION REQUEST..... | 152 | +| 9.2.1.14 | GNB-DU RESOURCE COORDINATION RESPONSE..... | 152 | +| 9.2.1.15 | GNB-DU STATUS INDICATION..... | 153 | +| 9.2.1.16 | F1 REMOVAL REQUEST..... | 153 | +| 9.2.1.17 | F1 REMOVAL RESPONSE..... | 153 | +| 9.2.1.18 | F1 REMOVAL FAILURE..... | 154 | +| 9.2.1.19 | NETWORK ACCESS RATE REDUCTION..... | 154 | +| 9.2.1.20 | RESOURCE STATUS REQUEST..... | 154 | +| 9.2.1.21 | RESOURCE STATUS RESPONSE..... | 156 | +| 9.2.1.22 | RESOURCE STATUS FAILURE..... | 156 | +| 9.2.1.23 | RESOURCE STATUS UPDATE..... | 156 | +| 9.2.1.24 | DU-CU TA INFORMATION TRANSFER..... | 158 | +| 9.2.1.25 | CU-DU TA INFORMATION TRANSFER..... | 159 | +| 9.2.1.26 | RACH INDICATION..... | 159 | +| 9.2.2 | UE Context Management messages..... | 159 | +| 9.2.2.1 | UE CONTEXT SETUP REQUEST..... | 159 | + +| | | | +|-----------|--------------------------------------------|-----| +| 9.2.2.2 | UE CONTEXT SETUP RESPONSE..... | 168 | +| 9.2.2.3 | UE CONTEXT SETUP FAILURE..... | 172 | +| 9.2.2.4 | UE CONTEXT RELEASE REQUEST..... | 173 | +| 9.2.2.5 | UE CONTEXT RELEASE COMMAND..... | 173 | +| 9.2.2.6 | UE CONTEXT RELEASE COMPLETE..... | 174 | +| 9.2.2.7 | UE CONTEXT MODIFICATION REQUEST..... | 175 | +| 9.2.2.8 | UE CONTEXT MODIFICATION RESPONSE..... | 189 | +| 9.2.2.9 | UE CONTEXT MODIFICATION FAILURE..... | 196 | +| 9.2.2.10 | UE CONTEXT MODIFICATION REQUIRED..... | 196 | +| 9.2.2.11 | UE CONTEXT MODIFICATION CONFIRM..... | 199 | +| 9.2.2.11A | UE CONTEXT MODIFICATION REFUSE..... | 201 | +| 9.2.2.12 | UE INACTIVITY NOTIFICATION..... | 201 | +| 9.2.2.13 | NOTIFY..... | 202 | +| 9.2.2.14 | ACCESS SUCCESS..... | 202 | +| 9.2.2.15 | DU-CU CELL SWITCH NOTIFICATION..... | 203 | +| 9.2.2.16 | CU-DU CELL SWITCH NOTIFICATION..... | 203 | +| 9.2.3 | RRC Message Transfer messages..... | 203 | +| 9.2.3.1 | INITIAL UL RRC MESSAGE TRANSFER..... | 203 | +| 9.2.3.2 | DL RRC MESSAGE TRANSFER..... | 204 | +| 9.2.3.3 | UL RRC MESSAGE TRANSFER..... | 205 | +| 9.2.3.4 | RRC DELIVERY REPORT..... | 206 | +| 9.2.4 | Warning Message Transmission Messages..... | 206 | +| 9.2.4.1 | WRITE-REPLACE WARNING REQUEST..... | 206 | +| 9.2.4.2 | WRITE-REPLACE WARNING RESPONSE..... | 207 | +| 9.2.4.3 | PWS CANCEL REQUEST..... | 207 | +| 9.2.4.4 | PWS CANCEL RESPONSE..... | 208 | +| 9.2.4.5 | PWS RESTART INDICATION..... | 209 | +| 9.2.4.6 | PWS FAILURE INDICATION..... | 209 | +| 9.2.5 | System Information messages..... | 209 | +| 9.2.5.1 | SYSTEM INFORMATION DELIVERY COMMAND..... | 209 | + +| | | | +|----------|----------------------------------------------------|-----| +| 9.2.6 | Paging messages..... | 210 | +| 9.2.6.1 | PAGING..... | 210 | +| 9.2.7 | Trace Messages..... | 211 | +| 9.2.7.1 | TRACE START..... | 211 | +| 9.2.7.2 | DEACTIVATE TRACE..... | 211 | +| 9.2.7.3 | CELL TRAFFIC TRACE..... | 211 | +| 9.2.8 | Radio Information Transfer messages..... | 212 | +| 9.2.8.1 | DU-CU RADIO INFORMATION TRANSFER..... | 212 | +| 9.2.8.2 | CU-DU RADIO INFORMATION TRANSFER..... | 212 | +| 9.2.9 | IAB messages..... | 213 | +| 9.2.9.1 | BAP MAPPING CONFIGURATION..... | 213 | +| 9.2.9.2 | BAP MAPPING CONFIGURATION ACKNOWLEDGE..... | 214 | +| 9.2.9.2A | BAP MAPPING CONFIGURATION FAILURE..... | 214 | +| 9.2.9.3 | GNB-DU RESOURCE CONFIGURATION..... | 215 | +| 9.2.9.4 | GNB-DU RESOURCE CONFIGURATION ACKNOWLEDGE..... | 219 | +| 9.2.9.4A | GNB-DU RESOURCE CONFIGURATION FAILURE..... | 219 | +| 9.2.9.5 | IAB TNL ADDRESS REQUEST..... | 220 | +| 9.2.9.6 | IAB TNL ADDRESS RESPONSE..... | 220 | +| 9.2.9.6A | IAB TNL ADDRESS FAILURE..... | 221 | +| 9.2.9.7 | IAB UP CONFIGURATION UPDATE REQUEST..... | 221 | +| 9.2.9.8 | IAB UP CONFIGURATION UPDATE RESPONSE..... | 222 | +| 9.2.9.9 | IAB UP CONFIGURATION UPDATE FAILURE..... | 222 | +| 9.2.9.10 | MIAB F1 SETUP TRIGGERING..... | 223 | +| 9.2.9.11 | MIAB F1 SETUP OUTCOME NOTIFICATION..... | 223 | +| 9.2.10 | Self Optimisation Support Messages..... | 224 | +| 9.2.10.1 | ACCESS AND MOBILITY INDICATION..... | 224 | +| 9.2.11 | Reference Time Information Reporting messages..... | 225 | +| 9.2.11.1 | REFERENCE TIME INFORMATION REPORTING CONTROL..... | 225 | +| 9.2.11.2 | REFERENCE TIME INFORMATION REPORT..... | 225 | +| 9.2.12 | Messages for Positioning Procedures..... | 225 | + +| | | | +|-----------|--------------------------------------------------|-----| +| 9.2.12.1 | POSITIONING ASSISTANCE INFORMATION CONTROL..... | 225 | +| 9.2.12.2 | POSITIONING ASSISTANCE INFORMATION FEEDBACK..... | 226 | +| 9.2.12.3 | POSITIONING MEASUREMENT REQUEST..... | 226 | +| 9.2.12.4 | POSITIONING MEASUREMENT RESPONSE..... | 228 | +| 9.2.12.5 | POSITIONING MEASUREMENT FAILURE..... | 229 | +| 9.2.12.6 | POSITIONING MEASUREMENT REPORT..... | 229 | +| 9.2.12.7 | POSITIONING MEASUREMENT ABORT..... | 230 | +| 9.2.12.8 | POSITIONING MEASUREMENT FAILURE INDICATION..... | 230 | +| 9.2.12.9 | POSITIONING MEASUREMENT UPDATE..... | 230 | +| 9.2.12.10 | TRP INFORMATION REQUEST..... | 231 | +| 9.2.12.11 | TRP INFORMATION RESPONSE..... | 232 | +| 9.2.12.12 | TRP INFORMATION FAILURE..... | 232 | +| 9.2.12.13 | POSITIONING INFORMATION REQUEST..... | 232 | +| 9.2.12.14 | POSITIONING INFORMATION RESPONSE..... | 233 | +| 9.2.12.15 | POSITIONING INFORMATION FAILURE..... | 233 | +| 9.2.12.16 | POSITIONING ACTIVATION REQUEST..... | 233 | +| 9.2.12.17 | POSITIONING ACTIVATION RESPONSE..... | 234 | +| 9.2.12.18 | POSITIONING ACTIVATION FAILURE..... | 234 | +| 9.2.12.19 | POSITIONING DEACTIVATION..... | 234 | +| 9.2.12.20 | E-CID MEASUREMENT INITIATION REQUEST..... | 235 | +| 9.2.12.21 | E-CID MEASUREMENT INITIATION RESPONSE..... | 236 | +| 9.2.12.22 | E-CID MEASUREMENT INITIATION FAILURE..... | 236 | +| 9.2.12.23 | E-CID MEASUREMENT FAILURE INDICATION..... | 236 | +| 9.2.12.24 | E-CID MEASUREMENT REPORT..... | 237 | +| 9.2.12.25 | E-CID MEASUREMENT TERMINATION COMMAND..... | 237 | +| 9.2.12.26 | POSITIONING INFORMATION UPDATE..... | 237 | +| 9.2.12.27 | PRS CONFIGURATION REQUEST..... | 237 | +| 9.2.12.28 | PRS CONFIGURATION RESPONSE..... | 238 | +| 9.2.12.29 | PRS CONFIGURATION FAILURE..... | 238 | +| 9.2.12.30 | MEASUREMENT PRECONFIGURATION REQUIRED..... | 239 | + +| | | | +|-----------|------------------------------------------------------|-----| +| 9.2.12.31 | MEASUREMENT PRECONFIGURATION CONFIRM..... | 239 | +| 9.2.12.32 | MEASUREMENT PRECONFIGURATION REFUSE..... | 239 | +| 9.2.12.33 | MEASUREMENT ACTIVATION..... | 240 | +| 9.2.12.34 | POSITIONING SYSTEM INFORMATION DELIVERY COMMAND..... | 240 | +| 9.2.13 | Broadcast Context Management messages..... | 241 | +| 9.2.13.1 | BROADCAST CONTEXT SETUP REQUEST..... | 241 | +| 9.2.13.2 | BROADCAST CONTEXT SETUP RESPONSE..... | 241 | +| 9.2.13.3 | BROADCAST CONTEXT SETUP FAILURE..... | 242 | +| 9.2.13.4 | BROADCAST CONTEXT RELEASE COMMAND..... | 242 | +| 9.2.13.5 | BROADCAST CONTEXT RELEASE COMPLETE..... | 243 | +| 9.2.13.5a | BROADCAST CONTEXT RELEASE REQUEST..... | 243 | +| 9.2.13.6 | BROADCAST CONTEXT MODIFICATION REQUEST..... | 243 | +| 9.2.13.7 | BROADCAST CONTEXT MODIFICATION RESPONSE..... | 245 | +| 9.2.13.8 | BROADCAST CONTEXT MODIFICATION FAILURE..... | 245 | +| 9.2.13.9 | BROADCAST TRANSPORT RESOURCE REQUEST..... | 246 | +| 9.2.14 | Multicast Context Management messages..... | 246 | +| 9.2.14.1 | MULTICAST GROUP PAGING..... | 246 | +| 9.2.14.2 | MULTICAST CONTEXT SETUP REQUEST..... | 247 | +| 9.2.14.3 | MULTICAST CONTEXT SETUP RESPONSE..... | 247 | +| 9.2.14.4 | MULTICAST CONTEXT SETUP FAILURE..... | 248 | +| 9.2.14.5 | MULTICAST CONTEXT RELEASE COMMAND..... | 248 | +| 9.2.14.6 | MULTICAST CONTEXT RELEASE COMPLETE..... | 248 | +| 9.2.14.6a | MULTICAST CONTEXT RELEASE REQUEST..... | 249 | +| 9.2.14.7 | MULTICAST CONTEXT MODIFICATION REQUEST..... | 249 | +| 9.2.14.8 | MULTICAST CONTEXT MODIFICATION RESPONSE..... | 250 | +| 9.2.14.9 | MULTICAST CONTEXT MODIFICATION FAILURE..... | 251 | +| 9.2.14.10 | MULTICAST DISTRIBUTION SETUP REQUEST..... | 251 | +| 9.2.14.11 | MULTICAST DISTRIBUTION SETUP RESPONSE..... | 252 | +| 9.2.14.12 | MULTICAST DISTRIBUTION SETUP FAILURE..... | 252 | +| 9.2.14.13 | MULTICAST DISTRIBUTION RELEASE COMMAND..... | 253 | + +| | | | +|-----------|-------------------------------------------------------|-----| +| 9.2.14.14 | MULTICAST DISTRIBUTION RELEASE COMPLETE..... | 253 | +| 9.2.14.15 | MULTICAST CONTEXT NOTIFICATION INDICATION..... | 253 | +| 9.2.14.16 | MULTICAST CONTEXT NOTIFICATION CONFIRM..... | 253 | +| 9.2.14.17 | MULTICAST CONTEXT NOTIFICATION REFUSE..... | 254 | +| 9.2.14.18 | MULTICAST COMMON CONFIGURATION REQUEST..... | 254 | +| 9.2.14.19 | MULTICAST COMMON CONFIGURATION CONFIRM..... | 254 | +| 9.2.14.20 | MULTICAST COMMON CONFIGURATION REFUSE..... | 254 | +| 9.2.15 | PDC Measurement Reporting messages..... | 254 | +| 9.2.15.1 | PDC MEASUREMENT INITIATION REQUEST..... | 255 | +| 9.2.15.2 | PDC MEASUREMENT INITIATION RESPONSE..... | 255 | +| 9.2.15.3 | PDC MEASUREMENT INITIATION FAILURE..... | 255 | +| 9.2.15.4 | PDC MEASUREMENT REPORT..... | 256 | +| 9.2.15.5 | PDC MEASUREMENT TERMINATION COMMAND..... | 256 | +| 9.2.15.6 | PDC MEASUREMENT FAILURE INDICATION..... | 256 | +| 9.2.16 | QMC messages..... | 257 | +| 9.2.16.1 | QOE INFORMATION TRANSFER..... | 257 | +| 9.2.16.2 | QOE INFORMATION TRANSFER CONTROL..... | 257 | +| 9.2.17 | Timing Synchronisation Status Reporting Messages..... | 258 | +| 9.2.17.1 | TIMING SYNCHRONISATION STATUS REQUEST..... | 258 | +| 9.2.17.2 | TIMING SYNCHRONISATION STATUS RESPONSE..... | 258 | +| 9.2.17.3 | TIMING SYNCHRONISATION STATUS FAILURE..... | 258 | +| 9.2.17.4 | TIMING SYNCHRONISATION STATUS REPORT..... | 258 | +| 9.3 | Information Element Definitions..... | 259 | +| 9.3.1 | Radio Network Layer Related IEs..... | 259 | +| 9.3.1.1 | Message Type..... | 259 | +| 9.3.1.2 | Cause..... | 259 | +| 9.3.1.3 | Criticality Diagnostics..... | 263 | +| 9.3.1.4 | gNB-CU UE FIAP ID..... | 264 | +| 9.3.1.5 | gNB-DU UE FIAP ID..... | 264 | +| 9.3.1.6 | RRC-Container..... | 264 | + +| | | | +|-----------|---------------------------------------------|-----| +| 9.3.1.7 | SRB ID..... | 264 | +| 9.3.1.8 | DRB ID..... | 264 | +| 9.3.1.9 | gNB-DU ID..... | 264 | +| 9.3.1.10 | Served Cell Information..... | 265 | +| 9.3.1.11 | Transmission Action Indicator..... | 270 | +| 9.3.1.12 | NR CGI..... | 270 | +| 9.3.1.13 | Time To wait..... | 270 | +| 9.3.1.14 | PLMN Identity..... | 270 | +| 9.3.1.15 | Transmission Bandwidth..... | 271 | +| 9.3.1.16 | Void..... | 271 | +| 9.3.1.17 | NR Frequency Info..... | 271 | +| 9.3.1.18 | gNB-DU System Information..... | 272 | +| 9.3.1.19 | E-UTRAN QoS..... | 273 | +| 9.3.1.20 | Allocation and Retention Priority..... | 274 | +| 9.3.1.21 | GBR QoS Information..... | 275 | +| 9.3.1.22 | Bit Rate..... | 275 | +| 9.3.1.23 | Transaction ID..... | 275 | +| 9.3.1.24 | DRX Cycle..... | 275 | +| 9.3.1.25 | CU to DU RRC Information..... | 276 | +| 9.3.1.26 | DU to CU RRC Information..... | 278 | +| 9.3.1.27 | RLC Mode..... | 282 | +| 9.3.1.28 | SUL Information..... | 283 | +| 9.3.1.29 | 5GS TAC..... | 283 | +| 9.3.1.29a | Configured EPS TAC..... | 283 | +| 9.3.1.30 | RRC Reconfiguration Complete Indicator..... | 284 | +| 9.3.1.31 | UL Configuration..... | 284 | +| 9.3.1.32 | C-RNTI..... | 284 | +| 9.3.1.33 | Cell UL Configured..... | 284 | +| 9.3.1.34 | RAT-Frequency Priority Information..... | 284 | +| 9.3.1.35 | LCID..... | 285 | + +| | | | +|----------|-----------------------------------------------|-----| +| 9.3.1.36 | Duplication activation..... | 285 | +| 9.3.1.37 | Slice Support List..... | 285 | +| 9.3.1.38 | S-NSSAI..... | 285 | +| 9.3.1.39 | UE Identity Index value..... | 285 | +| 9.3.1.40 | Paging DRX..... | 286 | +| 9.3.1.41 | Paging Priority..... | 286 | +| 9.3.1.42 | gNB-CU System Information..... | 286 | +| 9.3.1.43 | RAN UE Paging identity..... | 287 | +| 9.3.1.44 | CN UE Paging Identity..... | 287 | +| 9.3.1.45 | QoS Flow Level QoS Parameters..... | 287 | +| 9.3.1.46 | GBR QoS Flow Information..... | 288 | +| 9.3.1.47 | Dynamic 5QI Descriptor..... | 289 | +| 9.3.1.48 | NG-RAN Allocation and Retention Priority..... | 290 | +| 9.3.1.49 | Non Dynamic 5QI Descriptor..... | 291 | +| 9.3.1.50 | Maximum Packet Loss Rate..... | 292 | +| 9.3.1.51 | Packet Delay Budget..... | 292 | +| 9.3.1.52 | Packet Error Rate..... | 292 | +| 9.3.1.53 | Averaging Window..... | 293 | +| 9.3.1.54 | Maximum Data Burst Volume..... | 293 | +| 9.3.1.55 | Masked IMEISV..... | 293 | +| 9.3.1.56 | Notification Control..... | 293 | +| 9.3.1.57 | RAN Area Code..... | 293 | +| 9.3.1.58 | PWS System Information..... | 294 | +| 9.3.1.59 | Repetition Period..... | 294 | +| 9.3.1.60 | Number of Broadcasts Requested..... | 294 | +| 9.3.1.61 | Void..... | 294 | +| 9.3.1.62 | SIType List..... | 294 | +| 9.3.1.63 | QoS Flow Identifier..... | 295 | +| 9.3.1.64 | Served E-UTRA Cell Information..... | 295 | +| 9.3.1.65 | Available PLMN List..... | 295 | + +| | | | +|-----------|----------------------------------------------------|-----| +| 9.3.1.66 | RLC Failure Indication..... | 296 | +| 9.3.1.67 | Uplink TxDirectCurrentList Information..... | 296 | +| 9.3.1.68 | Service Status..... | 296 | +| 9.3.1.69 | RLC Status..... | 296 | +| 9.3.1.70 | RRC Version..... | 296 | +| 9.3.1.71 | RRC Delivery Status..... | 297 | +| 9.3.1.72 | QoS Flow Mapping Indication..... | 297 | +| 9.3.1.73 | Resource Coordination Transfer Information..... | 297 | +| 9.3.1.74 | E-UTRA PRACH Configuration..... | 297 | +| 9.3.1.75 | Resource Coordination E-UTRA Cell Information..... | 298 | +| 9.3.1.76 | Extended Available PLMN List..... | 299 | +| 9.3.1.77 | Associated SCell List..... | 299 | +| 9.3.1.78 | Cell Direction..... | 300 | +| 9.3.1.79 | Paging Origin..... | 300 | +| 9.3.1.80 | E-UTRA Transmission Bandwidth..... | 300 | +| 9.3.1.81 | Message Identifier..... | 300 | +| 9.3.1.82 | Serial Number..... | 300 | +| 9.3.1.83 | UAC Assistance Information..... | 300 | +| 9.3.1.84 | UAC Action..... | 301 | +| 9.3.1.85 | UAC reduction Indication..... | 302 | +| 9.3.1.86 | Additional SIB Message List..... | 302 | +| 9.3.1.87 | Cell Type..... | 302 | +| 9.3.1.87a | Configured TAC Indication..... | 302 | +| 9.3.1.88 | Trace Activation..... | 303 | +| 9.3.1.89 | Intended TDD DL-UL Configuration..... | 304 | +| 9.3.1.90 | Additional RRM Policy Index..... | 305 | +| 9.3.1.91 | DU-CU RIM Information..... | 305 | +| 9.3.1.92 | CU-DU RIM Information..... | 305 | +| 9.3.1.93 | gNB Set ID..... | 306 | +| 9.3.1.94 | Lower Layer Presence Status Change..... | 306 | + +| | | | +|-----------|--------------------------------------------------------|-----| +| 9.3.1.95 | Traffic Mapping Information..... | 306 | +| 9.3.1.96 | IP-to-layer-2 traffic mapping Information List..... | 306 | +| 9.3.1.97 | IP Header Information..... | 307 | +| 9.3.1.98 | BAP layer BH RLC channel mapping Information List..... | 307 | +| 9.3.1.99 | Mapping Information to Remove..... | 308 | +| 9.3.1.100 | Mapping Information Index..... | 308 | +| 9.3.1.101 | IAB TNL Addresses Requested..... | 308 | +| 9.3.1.102 | IAB TNL Address..... | 309 | +| 9.3.1.103 | Uplink BH Non-UP Traffic Mapping..... | 309 | +| 9.3.1.104 | Non-UP Traffic Type..... | 309 | +| 9.3.1.105 | IAB Info IAB-donor-CU..... | 310 | +| 9.3.1.106 | IAB Info IAB-DU..... | 310 | +| 9.3.1.107 | gNB-DU Cell Resource Configuration..... | 310 | +| 9.3.1.108 | Multiplexing Info..... | 313 | +| 9.3.1.109 | IAB STC Info..... | 314 | +| 9.3.1.110 | BAP Routing ID..... | 315 | +| 9.3.1.111 | BAP Address..... | 315 | +| 9.3.1.112 | BAP Path ID..... | 315 | +| 9.3.1.113 | BH RLC Channel ID..... | 316 | +| 9.3.1.114 | BH Information..... | 316 | +| 9.3.1.115 | Control Plane Traffic Type..... | 317 | +| 9.3.1.116 | NR V2X Services Authorized..... | 317 | +| 9.3.1.117 | LTE V2X Services Authorized..... | 317 | +| 9.3.1.118 | LTE UE Sidelink Aggregate Maximum Bit Rate..... | 317 | +| 9.3.1.119 | NR UE Sidelink Aggregate Maximum Bit Rate..... | 318 | +| 9.3.1.120 | SL DRB ID..... | 318 | +| 9.3.1.121 | PC5 QoS Flow Identifier..... | 318 | +| 9.3.1.122 | PC5 QoS Parameters..... | 318 | +| 9.3.1.123 | Alternative QoS Parameters Set Index..... | 319 | +| 9.3.1.124 | Alternative QoS Parameters Set Notify Index..... | 319 | + +| | | | +|-----------|------------------------------------------|-----| +| 9.3.1.125 | Alternative QoS Parameters Set List..... | 319 | +| 9.3.1.126 | Non Dynamic PQI Descriptor..... | 319 | +| 9.3.1.127 | Dynamic PQI Descriptor..... | 320 | +| 9.3.1.128 | TNL Capacity Indicator..... | 320 | +| 9.3.1.129 | Radio Resource Status..... | 321 | +| 9.3.1.130 | Composite Available Capacity Group..... | 323 | +| 9.3.1.131 | Composite Available Capacity..... | 323 | +| 9.3.1.132 | Cell Capacity Class Value..... | 323 | +| 9.3.1.133 | Capacity Value..... | 324 | +| 9.3.1.134 | Slice Available Capacity..... | 324 | +| 9.3.1.135 | Number of Active UEs..... | 325 | +| 9.3.1.136 | Hardware Load Indicator..... | 325 | +| 9.3.1.137 | NR Carrier List..... | 325 | +| 9.3.1.138 | SSB Positions In Burst..... | 326 | +| 9.3.1.139 | NR PRACH Configuration..... | 326 | +| 9.3.1.140 | NR PRACH Configuration List..... | 326 | +| 9.3.1.141 | TSC Traffic Characteristics..... | 328 | +| 9.3.1.142 | TSC Assistance Information..... | 329 | +| 9.3.1.143 | Periodicity..... | 329 | +| 9.3.1.144 | Burst Arrival Time..... | 329 | +| 9.3.1.145 | Extended Packet Delay Budget..... | 329 | +| 9.3.1.146 | RLC Duplication Information..... | 330 | +| 9.3.1.147 | Reporting Request Type..... | 330 | +| 9.3.1.148 | Time Reference Information..... | 330 | +| 9.3.1.149 | Reference Time..... | 331 | +| 9.3.1.150 | MDT Configuration..... | 331 | +| 9.3.1.151 | MDT PLMN List..... | 331 | +| 9.3.1.152 | M5 Configuration..... | 332 | +| 9.3.1.153 | M6 Configuration..... | 332 | +| 9.3.1.154 | M7 Configuration..... | 333 | + +| | | | +|-----------|-------------------------------------------------|-----| +| 9.3.1.155 | NID..... | 333 | +| 9.3.1.156 | NPN Support Information..... | 333 | +| 9.3.1.157 | NPN Broadcast Information..... | 333 | +| 9.3.1.158 | Broadcast SNPN ID List..... | 333 | +| 9.3.1.159 | Broadcast NID List..... | 334 | +| 9.3.1.160 | Broadcast CAG-Identifier List..... | 334 | +| 9.3.1.161 | CAG ID..... | 334 | +| 9.3.1.162 | Broadcast PNI-NPN ID Information..... | 334 | +| 9.3.1.163 | Available SNPN ID List..... | 335 | +| 9.3.1.164 | Void..... | 335 | +| 9.3.1.165 | Extended Slice Support List..... | 335 | +| 9.3.1.166 | Positioning Measurement Result..... | 335 | +| 9.3.1.167 | UL Angle of Arrival..... | 336 | +| 9.3.1.168 | UL RTOA Measurement..... | 336 | +| 9.3.1.169 | Additional Path List..... | 337 | +| 9.3.1.170 | gNB Rx-Tx Time Difference..... | 337 | +| 9.3.1.171 | Time Stamp..... | 338 | +| 9.3.1.172 | TRP Measurement Quality..... | 338 | +| 9.3.1.173 | Measurement Beam Information..... | 339 | +| 9.3.1.174 | NG-RAN Access Point Position..... | 339 | +| 9.3.1.175 | Requested SRS Transmission Characteristics..... | 340 | +| 9.3.1.176 | TRP Information..... | 341 | +| 9.3.1.177 | PRS Configuration..... | 342 | +| 9.3.1.178 | DL-PRS Muting Pattern..... | 344 | +| 9.3.1.179 | Spatial Direction Information..... | 344 | +| 9.3.1.180 | SRS Resource Set ID..... | 345 | +| 9.3.1.181 | Spatial Relation Information..... | 345 | +| 9.3.1.182 | SRS Resource Trigger..... | 345 | +| 9.3.1.183 | Relative Time 1900..... | 346 | +| 9.3.1.184 | Geographical Coordinates..... | 346 | + +| | | | +|-----------|----------------------------------------------------|-----| +| 9.3.1.185 | DL-PRS Resource Coordinates..... | 347 | +| 9.3.1.186 | Relative Geodetic Location..... | 347 | +| 9.3.1.187 | Relative Cartesian Location..... | 348 | +| 9.3.1.188 | Reference Point..... | 348 | +| 9.3.1.189 | Location Uncertainty..... | 349 | +| 9.3.1.190 | NG-RAN High Accuracy Access Point Position..... | 349 | +| 9.3.1.191 | Positioning Broadcast Cells..... | 349 | +| 9.3.1.192 | SRS Configuration..... | 350 | +| 9.3.1.193 | SRS Resource..... | 351 | +| 9.3.1.194 | Positioning SRS Resource..... | 352 | +| 9.3.1.195 | SRS Resource Set..... | 353 | +| 9.3.1.196 | Positioning SRS Resource Set..... | 354 | +| 9.3.1.197 | TRP ID..... | 354 | +| 9.3.1.198 | NR-PRS Beam Information..... | 354 | +| 9.3.1.199 | E-CID Measurement Result..... | 355 | +| 9.3.1.200 | Cell Portion ID..... | 356 | +| 9.3.1.201 | Pathloss Reference Information..... | 356 | +| 9.3.1.202 | SSB Information..... | 357 | +| 9.3.1.203 | SSB Time/Frequency Configuration..... | 357 | +| 9.3.1.204 | Search Window Information..... | 357 | +| 9.3.1.205 | Extended gNB-DU Name..... | 358 | +| 9.3.1.206 | Extended gNB-CU Name..... | 358 | +| 9.3.1.207 | F1-C Transfer Path..... | 358 | +| 9.3.1.208 | SFN Offset..... | 358 | +| 9.3.1.209 | Transmission Stop Indicator..... | 359 | +| 9.3.1.210 | Spatial Relation Information per SRS Resource..... | 359 | +| 9.3.1.211 | CCO Assistance Information..... | 359 | +| 9.3.1.212 | Affected Cells and Beams..... | 360 | +| 9.3.1.213 | Coverage Modification Notification..... | 360 | +| 9.3.1.214 | Cells for SON List..... | 361 | + +| | | | +|-----------|----------------------------------------------------|-----| +| 9.3.1.215 | Neighbour NR Cells for SON List..... | 361 | +| 9.3.1.216 | NR Mode Info Rel16..... | 362 | +| 9.3.1.217 | Frequency Info Rel16..... | 362 | +| 9.3.1.218 | MBS Session ID..... | 363 | +| 9.3.1.219 | gNB-CU MBS F1AP ID..... | 363 | +| 9.3.1.220 | gNB-DU MBS F1AP ID..... | 363 | +| 9.3.1.221 | MBS Area Session ID..... | 363 | +| 9.3.1.222 | MBS Service Area..... | 363 | +| 9.3.1.223 | MBS Service Area information..... | 364 | +| 9.3.1.224 | MRB ID..... | 364 | +| 9.3.1.225 | MBS CU to DU RRC Information..... | 364 | +| 9.3.1.226 | MBS Broadcast Neighbour Cell List..... | 365 | +| 9.3.1.227 | IAB Congestion Indication..... | 365 | +| 9.3.1.228 | F1-C Transfer Path NRDC..... | 365 | +| 9.3.1.229 | IAB TNL Address Exception..... | 365 | +| 9.3.1.230 | RB Set Configuration..... | 366 | +| 9.3.1.231 | Survival Time..... | 366 | +| 9.3.1.232 | PDC Measurement Result..... | 366 | +| 9.3.1.233 | SCG Activation Request..... | 367 | +| 9.3.1.234 | SCG Activation Status..... | 367 | +| 9.3.1.235 | Requested DL PRS Transmission Characteristics..... | 367 | +| 9.3.1.236 | Start Time and Duration..... | 368 | +| 9.3.1.237 | PRS Transmission Off Information..... | 368 | +| 9.3.1.238 | UL-AoA Assistance Information..... | 369 | +| 9.3.1.239 | Zenith Angle of Arrival Information..... | 369 | +| 9.3.1.240 | On-demand PRS TRP Information..... | 369 | +| 9.3.1.241 | LCS to GCS Translation..... | 371 | +| 9.3.1.242 | Response Time..... | 371 | +| 9.3.1.243 | ARP Location Information..... | 371 | +| 9.3.1.244 | ARP ID..... | 372 | + +| | | | +|-----------|----------------------------------------------------|-----| +| 9.3.1.245 | Multiple UL AoA..... | 372 | +| 9.3.1.246 | UL SRS-RSRP..... | 372 | +| 9.3.1.247 | SRS Resource type..... | 373 | +| 9.3.1.248 | Extended Additional Path List..... | 373 | +| 9.3.1.249 | LoS/NLoS Information..... | 373 | +| 9.3.1.250 | Requested DL-PRS Resource List..... | 374 | +| 9.3.1.251 | Void..... | 374 | +| 9.3.1.252 | TRP Tx TEG Association..... | 374 | +| 9.3.1.253 | TRP TEG Information..... | 375 | +| 9.3.1.254 | Measurement Characteristics Request Indicator..... | 375 | +| 9.3.1.255 | UE Reporting Information..... | 376 | +| 9.3.1.256 | TRP Beam Antenna Information..... | 376 | +| 9.3.1.257 | TRP Beam Antenna Angles..... | 376 | +| 9.3.1.258 | NR Paging eDRX Information..... | 378 | +| 9.3.1.259 | NR Paging eDRX Information for RRC INACTIVE..... | 378 | +| 9.3.1.260 | QoE Metrics..... | 378 | +| 9.3.1.261 | CG-SDT Session Info..... | 378 | +| 9.3.1.262 | SDT Information..... | 378 | +| 9.3.1.263 | Path Switch Configuration..... | 379 | +| 9.3.1.264 | Sidelink Relay Configuration..... | 379 | +| 9.3.1.265 | PC5 RLC Channel ID..... | 379 | +| 9.3.1.266 | Uu RLC Channel ID..... | 379 | +| 9.3.1.267 | Remote UE Local ID..... | 380 | +| 9.3.1.268 | 5G ProSe Authorized..... | 380 | +| 9.3.1.269 | PEIPS Assistance Information..... | 381 | +| 9.3.1.270 | UE Paging Capability..... | 381 | +| 9.3.1.271 | gNB-DU UE Slice Maximum Bit Rate List..... | 381 | +| 9.3.1.272 | Multicast MBS Session List..... | 381 | +| 9.3.1.273 | TAI NSAG Support List..... | 381 | +| 9.3.1.274 | MDT PLMN Modification List..... | 382 | + +| | | | +|-----------|--------------------------------------------------------|-----| +| 9.3.1.275 | MRB RLC Configuration..... | 382 | +| 9.3.1.276 | Timing Error Margin..... | 383 | +| 9.3.1.277 | SDT Bearer Configuration Info..... | 383 | +| 9.3.1.278 | PosSIType List..... | 383 | +| 9.3.1.279 | IAB-DU Cell Resource Configuration-Mode-Info..... | 384 | +| 9.3.1.280 | TRP Rx TEG Information..... | 385 | +| 9.3.1.281 | TRP Tx TEG Information..... | 385 | +| 9.3.1.282 | TRP RxTx TEG Information..... | 385 | +| 9.3.1.283 | Uplink TxDirectCurrentTwoCarrierList Information..... | 385 | +| 9.3.1.284 | Uplink TxDirectCurrentMoreCarrierList Information..... | 386 | +| 9.3.1.285 | Extended UE Identity Index Value..... | 386 | +| 9.3.1.286 | Hashed UE Identity Index Value..... | 386 | +| 9.3.1.287 | Broadcast Area Scope..... | 386 | +| 9.3.1.288 | Network Controlled Repeater Authorized..... | 387 | +| 9.3.1.289 | MT-SDT Information..... | 387 | +| 9.3.1.290 | Supported UE Type List..... | 387 | +| 9.3.1.291 | LTM Cells To Be Released List..... | 387 | +| 9.3.1.292 | Reference Configuration..... | 387 | +| 9.3.1.293 | TCI States Configurations List..... | 388 | +| 9.3.1.294 | LTM Configuration ID Mapping List..... | 388 | +| 9.3.1.295 | Radio Resource Status NR-U..... | 388 | +| 9.3.1.296 | Path Addition Information..... | 389 | +| 9.3.1.297 | Recommended SSBs for Paging List..... | 389 | +| 9.3.1.298 | RAN Timing Synchronisation Status Information..... | 389 | +| 9.3.1.299 | Clock Accuracy..... | 390 | +| 9.3.1.300 | Burst Arrival Time Window..... | 390 | +| 9.3.1.301 | Periodicity Range..... | 390 | +| 9.3.1.302 | TSC Traffic Characteristics Feedback..... | 391 | +| 9.3.1.303 | TSC Feedback Information..... | 391 | +| 9.3.1.304 | Mobile TRP Location Information..... | 391 | + +| | | | +|-----------|--------------------------------------------------------------|-----| +| 9.3.1.305 | Global gNB ID..... | 391 | +| 9.3.1.306 | RRC Terminating IAB-Donor Related Info..... | 392 | +| 9.3.1.307 | Mobile IAB-MT User Location Information..... | 392 | +| 9.3.1.308 | TAI..... | 392 | +| 9.3.1.309 | Associated Session ID..... | 392 | +| 9.3.1.310 | Multicast CU to DU RRC Information..... | 392 | +| 9.3.1.311 | Multicast DU to CU RRC Information..... | 393 | +| 9.3.1.312 | MBS Multicast Configuration Response Information..... | 393 | +| 9.3.1.313 | MBS Multicast Configuration Notification..... | 394 | +| 9.3.1.314 | Multicast CU to DU Common RRC Information..... | 394 | +| 9.3.1.315 | Update MBS Multicast Neighbour Cell List Information..... | 395 | +| 9.3.1.316 | Update ThresholdMBS-List Information..... | 395 | +| 9.3.1.317 | MBS Multicast Session Reception State..... | 396 | +| 9.3.1.318 | Multicast RRC_INACTIVE Reception Mode..... | 396 | +| 9.3.1.319 | PDU Set QoS Parameters..... | 396 | +| 9.3.1.320 | N6 Jitter Information..... | 397 | +| 9.3.1.321 | ECN Marking or Congestion Information Reporting Request..... | 397 | +| 9.3.1.322 | ECN Marking or Congestion Information Reporting Status..... | 397 | +| 9.3.1.323 | NR A2X Services Authorized..... | 397 | +| 9.3.1.324 | LTE A2X Services Authorized..... | 397 | +| 9.3.1.325 | NR Paging Long eDRX Information..... | 398 | +| 9.3.2 | Transport Network Layer Related IEs..... | 398 | +| 9.3.2.1 | UP Transport Layer Information..... | 398 | +| 9.3.2.2 | GTP-TEID..... | 398 | +| 9.3.2.3 | Transport Layer Address..... | 398 | +| 9.3.2.4 | CP Transport Layer Information..... | 399 | +| 9.3.2.5 | Transport Layer Address Info..... | 399 | +| 9.3.2.6 | URI..... | 400 | +| 9.3.2.7 | BC Bearer Context F1-U TNL Info..... | 400 | +| 9.3.2.8 | MBS Multicast F1-U Context Descriptor..... | 400 | + +| | | | +|-------------------------------|-------------------------------------------------------------------|------------| +| 9.3.2.9 | Void..... | 401 | +| 9.3.2.10 | MBS PTP Retransmission Tunnel Required..... | 401 | +| 9.3.2.11 | Multicast F1-U Context Reference F1..... | 401 | +| 9.3.2.12 | MRB Progress Information..... | 401 | +| 9.3.2.13 | Multicast F1-U Context Reference CU..... | 401 | +| 9.4 | Message and Information Element Abstract Syntax (with ASN.1)..... | 402 | +| 9.4.1 | General..... | 402 | +| 9.4.2 | Usage of private message mechanism for non-standard use..... | 402 | +| 9.4.3 | Elementary Procedure Definitions..... | 403 | +| 9.4.4 | PDU Definitions..... | 423 | +| 9.4.5 | Information Element Definitions..... | 533 | +| 9.4.6 | Common Definitions..... | 709 | +| 9.4.7 | Constant Definitions..... | 710 | +| 9.4.8 | Container Definitions..... | 729 | +| 9.5 | Message Transfer Syntax..... | 734 | +| 9.6 | Timers..... | 734 | +| 10 | Handling of unknown, unforeseen and erroneous protocol data..... | 734 | +| Annex A (informative): | Change History..... | 735 | + +--- + +## 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 F1 interface. The F1 interface provides means for interconnecting a gNB-CU and a gNB-DU of a gNB within an NG-RAN, or for interconnecting a gNB-CU and a gNB-DU of an en-gNB within an E-UTRAN. The F1 Application Protocol (F1AP) supports the functions of F1 interface by signalling procedures defined in the present document. F1AP is developed in accordance to the general principles stated in TS 38.401 [4] and TS 38.470 [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 38.470: "NG-RAN; F1 general aspects and principles". +- [3] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)". +- [4] 3GPP TS 38.401: "NG-RAN; Architecture Description". +- [5] ITU-T Recommendation X.691 (2002-07): "Information technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER)". +- [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 38.331: "NR; Radio Resource Control (RRC); Protocol specification". +- [9] 3GPP TS 36.423: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP)". +- [10] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [11] 3GPP TS 23.203: "Policy and charging control architecture". +- [12] ITU-T Recommendation X.680 (07/2002): "Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation". +- [13] ITU-T Recommendation X.681 (07/2002): "Information technology – Abstract Syntax Notation One (ASN.1): Information object specification". +- [14] 3GPP TR 25.921: (version.7.0.0): "Guidelines and principles for protocol description and error". +- [15] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)". + +- [16] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification". +- [17] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception". +- [18] 3GPP TS 29.281: "General Packet Radio System (GPRS); Tunnelling Protocol User Plane (GTPv1-U) ". +- [19] 3GPP TS 38.414: "NG-RAN; NG data transport". +- [20] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". +- [21] 3GPP TS 23.501: "System Architecture for the 5G System". +- [22] 3GPP TS 38.472: "NG-RAN; F1 signalling transport". +- [23] 3GPP TS 23.003: "Numbering, addressing and identification". +- [24] 3GPP TS 38.304: "NR; User Equipment (UE) procedures in Idle mode and RRC Inactive state ". +- [25] 3GPP TS 36.104: "Base Station (BS) radio transmission and reception". +- [26] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [27] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation". +- [28] 3GPP TS 38.423: "NG-RAN; Xn application protocol (XnAP)". +- [29] 3GPP TS 32.422: "Trace control and configuration management". +- [30] 3GPP TS 38.340: "NR; Backhaul Adaptation Protocol (BAP) specification". +- [31] 3GPP TS 38.213: "NR; Physical layer procedures for control". +- [32] 3GPP TS 38.314: " NR; Layer 2 measurements". +- [33] 3GPP TS 38.211: "NR; Physical channels and modulation". +- [34] 3GPP TS 38.214: "NR; Physical layer procedures for data". +- [35] 3GPP TS 37.320: "Radio measurement collection for Minimization of Drive Tests (MDT)". +- [36] 3GPP TS 23.032:"Technical Specification Group Services and System Aspects; Universal Geographical Area Description (GAD)". +- [37] 3GPP TS 38.455: "NG-RAN; NR Positioning protocol A (NRPPa)". +- [38] 3GPP TS 38.133: "NR; Requirements for support of radio resource management". +- [39] 3GPP TS 37.355: "LTE Positioning Protocol (LPP)". +- [40] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services". +- [41] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [42] 3GPP TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN". + +- [43] 3GPP TS 38.215: "NR; Physical layer (PHY); Measurements". +- [44] 3GPP TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)". +- [45] Void +- [46] 3GPP TS 37.213: "NR; Physical layer procedures for shared spectrum channel access". +- [47] 3GPP TS 37.483: "E1 Application Protocol (E1AP)". +- [48] IEEE Std 1588: "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems", Edition 2019. +- [49] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2". +- [50] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces". +- [51] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3". + +--- + +## 3 Definitions and abbreviations + +### 3.1 Definitions + +**elementary procedure:** F1AP consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between gNB-CU and gNB-DU. 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 F1AP EPs together is specified in stage 2 specifications (e.g., TS 38.470 [2]). + +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. + +**BH RLC channel:** as defined in TS 38.300 [6]. + +**Conditional handover:** as defined in TS 38.300 [6]. + +**Conditional PSCell Addition:** as defined in TS 37.340 [7]. + +**Conditional PSCell Change:** as defined in TS 37.340 [7]. + +**DAPS Handover:** as defined in TS 38.300 [6]. + +**EN-DC operation:** Used in this specification when the F1AP is applied for gNB-CU and gNB-DU in E-UTRAN. + +**gNB:** as defined in TS 38.300 [6]. + +**gNB-CU:** as defined in TS 38.401 [4]. + +**gNB-CU UE F1AP ID:** as defined in TS 38.401 [4]. + +**gNB-DU:** as defined in TS 38.401 [4]. + +**gNB-DU UE F1AP ID:** as defined in TS 38.401 [4]. + +**en-gNB:** as defined in TS 37.340 [7]. + +**IAB-MT:** as defined in TS 38.300 [6]. + +**IAB-DU:** as defined in TS 38.300 [6]. + +**IAB-node:** as defined in TS 38.300 [6]. + +**IAB-donor:** as defined in TS 38.300 [6]. + +**IAB-donor-CU:** as defined in TS 38.401 [4]. + +**IAB-donor-DU:** as defined in TS 38.401 [4]. + +**MBS session resource:** as defined in TS 38.401 [4]. + +**MBS-associated signalling:** When F1AP messages associated to one MBS session uses the MBS-associated logical F1-connection for association of the message to the MBS session in gNB-DU and gNB-CU. + +**MBS-associated logical F1-connection:** The MBS-associated logical F1-connection uses the identities *GNB-CU MBS F1AP ID* and *GNB-DU MBS F1AP ID* according to the definition in TS 38.401 [4]. For a received MBS-associated F1AP message the gNB-CU identifies the associated MBS session based on the *GNB-CU MBS F1AP ID* IE and the gNB-DU identifies the associated MBS session based on the *GNB-DU MBS F1AP ID* IE. + +**MBS Session context in a gNB-DU:** as defined in TS 38.401 [4]. + +**MP Relay UE:** as defined in TS 38.300 [6]. + +**MP Remote UE:** as defined in TS 38.300 [6]. + +**Multi-path:** as defined in TS 38.300 [6]. + +**Multicast F1-U Context:** as defined in TS 38.401 [4]. + +**Other SI:** as defined in TS 38.300 [6]. + +**Public network integrated NPN:** as defined in TS 23.501 [21]. + +**Stand-alone Non-Public Network:** as defined in TS 23.501 [21]. + +**UE-associated signalling:** When F1AP messages associated to one UE uses the UE-associated logical F1-connection for association of the message to the UE in gNB-DU and gNB-CU. + +**UE-associated logical F1-connection:** The UE-associated logical F1-connection uses the identities *GNB-CU UE F1AP ID* and *GNB-DU UE F1AP ID* according to the definition in TS 38.401 [4]. For a received UE associated F1AP message the gNB-CU identifies the associated UE based on the *GNB-CU UE F1AP ID* IE and the gNB-DU identifies the associated UE based on the *GNB-DU UE F1AP ID* IE. The UE-associated logical F1-connection may exist before the F1 UE context is setup in gNB-DU. + +**U2N Relay UE:** a UE that provides functionality to support connectivity to the network for U2N Remote UE(s). + +**U2N Remote UE:** a UE that communicates with the network via a U2N Relay UE. + +**Uu Relay RLC channel:** as defined in TS 38.300 [6]. + +**PC5 Relay RLC channel:** as defined in TS 38.300 [6]. + +**SRAP:** Sidelink relay adaptation protocol, as defined in TS 38.300 [6]. + +**Mobile IAB-node:** as defined in TS 38.300 [6]. + +**Mobile IAB-MT:** as defined in TS 38.300 [6]. + +**Mobile IAB-DU:** as defined in TS 38.300 [6]. + +**RRC-terminating IAB-donor:** as defined in TS 38.401 [4]. + +**F1-terminating IAB-donor:** as defined in TS 38.401 [4]. + +## 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 | +| A2X | Aircraft-to-Everything | +| AMF | Access and Mobility Management Function | +| ARP | Antenna Reference Point | +| ARPI | Additional RRM Policy Index | +| BH | Backhaul | +| CAG | Closed Access Group | +| CN | Core Network | +| CG | Cell Group | +| CG-SDT | Configured Grant-Small Data Transmission | +| CGI | Cell Global Identifier | +| CHO | Conditional Handover | +| CP | Control Plane | +| CPA | Conditional PSCell Addition | +| CPC | Conditional PSCell Change | +| DAPS | Dual Active Protocol Stack | +| DL | Downlink | +| DL-PRS | Downlink Positioning Reference Signal | +| EN-DC | E-UTRA-NR Dual Connectivity | +| EPC | Evolved Packet Core | +| eRedCap | Enhanced Reduced Capability | +| FSA ID | MBS Frequency Selection Area (FSA) ID | +| GPSI | Generic Public Subscription Identifier | + +| | | +|---------|-----------------------------------------------------------------------------| +| IAB | Integrated Access and Backhaul | +| IMEISV | International Mobile station Equipment Identity and Software Version number | +| LMF | Location Management Function | +| LTM | L1/L2 Triggered Mobility | +| MBS | Multicast/Broadcast Service | +| MP | Multi-path | +| MT-SDT | Mobile Terminated Small Data Transmission | +| N3C | Non-3GPP Connection | +| NID | Network Identifier | +| NPN | Non-Public Network | +| NSAG | Network Slice AS Group | +| NSSAI | Network Slice Selection Assistance Information | +| PDC | Propagation Delay Compensation | +| PEIPS | Paging Early Indication with Paging Subgrouping | +| posSIB | Positioning SIB | +| PNI-NPN | Public Network Integrated NPN | +| PTP | Point to Point | +| PTM | Point to Multipoint | +| QMC | QoE Measurement Collection | +| QoE | Quality of Experience | +| RANAC | RAN Area Code | +| RedCap | Reduced Capability | +| RIM | Remote Interference Management | +| RIM-RS | RIM Reference Signal | +| RRC | Radio Resource Control | +| RSRP | Reference Signal Received Power | +| SDT | Small Data Transmission | +| SNPN | Stand-alone Non-Public Network | +| S-NSSAI | Single Network Slice Selection Assistance Information | +| SUL | Supplementary Uplink | +| TAC | Tracking Area Code | +| TAI | Tracking Area Identity | +| TEG | Timing Error Group | +| TRP | Transmission-Reception Point | +| TSS | Timing Synchronisation Status | +| U2N | UE-to-Network | +| UL-AoA | Uplink Angle of Arrival | +| UL-RTOA | Uplink Relative Time of Arrival | +| UL-SRS | Uplink Sounding Reference Signal | +| V2X | Vehicle-to-Everything | +| Z-AoA | Zenith Angles of Arrival | + +--- + +## 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 F1AP services + +F1AP provides the signalling service between gNB-DU and the gNB-CU that is required to fulfil the F1AP functions described in clause 7. F1AP services are divided into two groups: + +| | | +|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Non UE-associated services: | They are related to the whole F1 interface instance between the gNB-DU and gNB-CU utilising a non UE-associated signalling connection. | +| UE-associated services: | They are related to one UE. F1AP 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 service. F1AP functions that provide these services are associated with a MBS-associated signalling connection that is maintained for the MBS service in question. + +Unless explicitly indicated in the procedure specification, at any instance in time one protocol endpoint shall have a maximum of one ongoing F1AP 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 F1AP procedure related to a certain MBS session. + +All considerations of gNB-DU in this specification also apply to the IAB-DU and IAB-donor-DU, unless stated otherwise. All considerations of gNB-CU in this specification apply to the IAB-donor-CU as well, unless stated otherwise. + +## 6 Services expected from signalling transport + +The signalling connection shall provide in sequence delivery of F1AP messages. F1AP shall be notified if the signalling connection breaks. + +## 7 Functions of F1AP + +The functions of F1AP are described in TS 38.470 [2]. + +## 8 F1AP procedures + +### 8.1 List of F1AP 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 | | +| F1 Setup | F1 SETUP REQUEST | F1 SETUP RESPONSE | F1 SETUP FAILURE | +| gNB-DU Configuration Update | GNB-DU CONFIGURATION UPDATE | GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE | GNB-DU CONFIGURATION UPDATE FAILURE | +| gNB-CU Configuration Update | GNB-CU CONFIGURATION UPDATE | GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE | GNB-CU CONFIGURATION UPDATE FAILURE | +| UE Context Setup | UE CONTEXT SETUP REQUEST | UE CONTEXT SETUP RESPONSE | UE CONTEXT SETUP FAILURE | +| UE Context Release (gNB-CU initiated) | UE CONTEXT RELEASE COMMAND | UE CONTEXT RELEASE COMPLETE | | + +| Elementary Procedure | Initiating Message | Successful Outcome | Unsuccessful Outcome | +|-----------------------------------------------------|----------------------------------------|-------------------------------------------|----------------------------------------| +| | | Response message | Response message | +| UE Context Modification (gNB-CU initiated) | UE CONTEXT MODIFICATION REQUEST | UE CONTEXT MODIFICATION RESPONSE | UE CONTEXT MODIFICATION FAILURE | +| UE Context Modification Required (gNB-DU initiated) | UE CONTEXT MODIFICATION REQUIRED | UE CONTEXT MODIFICATION CONFIRM | UE CONTEXT MODIFICATION REFUSE | +| Write-Replace Warning | WRITE-REPLACE WARNING REQUEST | WRITE-REPLACE WARNING RESPONSE | | +| PWS Cancel | PWS CANCEL REQUEST | PWS CANCEL RESPONSE | | +| gNB-DU Resource Coordination | GNB-DU RESOURCE COORDINATION REQUEST | GNB-DU RESOURCE COORDINATION RESPONSE | | +| F1 Removal | F1 REMOVAL REQUEST | F1 REMOVAL RESPONSE | F1 REMOVAL FAILURE | +| BAP Mapping Configuration | BAP MAPPING CONFIGURATION | BAP MAPPING CONFIGURATION ACKNOWLEDGE | BAP MAPPING CONFIGURATION FAILURE | +| GNB-DU Resource Configuration | GNB-DU RESOURCE CONFIGURATION | GNB-DU RESOURCE CONFIGURATION ACKNOWLEDGE | GNB-DU RESOURCE CONFIGURATION FAILURE | +| IAB TNL Address Allocation | IAB TNL ADDRESS REQUEST | IAB TNL ADDRESS RESPONSE | IAB TNL ADDRESS FAILURE | +| IAB UP Configuration Update | IAB UP CONFIGURATION UPDATE REQUEST | IAB UP CONFIGURATION UPDATE RESPONSE | IAB UP CONFIGURATION UPDATE FAILURE | +| Resource Status Reporting Initiation | RESOURCE STATUS REQUEST | RESOURCE STATUS RESPONSE | RESOURCE STATUS FAILURE | +| Positioning Measurement | POSITIONING MEASUREMENT REQUEST | POSITIONING MEASUREMENT RESPONSE | POSITIONING MEASUREMENT FAILURE | +| Positioning Information Exchange | POSITIONING INFORMATION REQUEST | POSITIONING INFORMATION RESPONSE | POSITIONING INFORMATION FAILURE | +| TRP Information Exchange | TRP INFORMATION REQUEST | TRP INFORMATION RESPONSE | TRP INFORMATION FAILURE | +| Positioning Activation | POSITIONING ACTIVATION REQUEST | POSITIONING ACTIVATION RESPONSE | POSITIONING ACTIVATION FAILURE | +| E-CID Measurement Initiation | E-CID MEASUREMENT INITIATION REQUEST | E-CID MEASUREMENT INITIATION RESPONSE | E-CID MEASUREMENT INITIATION FAILURE | +| Broadcast Context Setup | BROADCAST CONTEXT SETUP REQUEST | BROADCAST CONTEXT SETUP RESPONSE | BROADCAST CONTEXT SETUP FAILURE | +| Broadcast Context Release | BROADCAST CONTEXT RELEASE COMMAND | BROADCAST CONTEXT RELEASE COMPLETE | | +| Broadcast Context Modification | BROADCAST CONTEXT MODIFICATION REQUEST | BROADCAST CONTEXT MODIFICATION RESPONSE | BROADCAST CONTEXT MODIFICATION FAILURE | + +| Elementary Procedure | Initiating Message | Successful Outcome | Unsuccessful Outcome | +|--------------------------------|-------------------------------------------|-----------------------------------------|----------------------------------------| +| | | Response message | Response message | +| Multicast Context Setup | MULTICAST CONTEXT SETUP REQUEST | MULTICAST CONTEXT SETUP RESPONSE | MULTICAST CONTEXT SETUP FAILURE | +| Multicast Context Release | MULTICAST CONTEXT RELEASE COMMAND | MULTICAST CONTEXT RELEASE COMPLETE | | +| Multicast Context Modification | MULTICAST CONTEXT MODIFICATION REQUEST | MULTICAST CONTEXT MODIFICATION RESPONSE | MULTICAST CONTEXT MODIFICATION FAILURE | +| Multicast Distribution Setup | MULTICAST DISTRIBUTION SETUP REQUEST | MULTICAST DISTRIBUTION SETUP RESPONSE | MULTICAST DISTRIBUTION SETUP FAILURE | +| Multicast Distribution Release | MULTICAST DISTRIBUTION RELEASE COMMAND | MULTICAST DISTRIBUTION RELEASE COMPLETE | | +| PDC Measurement Initiation | PDC MEASUREMENT INITIATION REQUEST | PDC MEASUREMENT INITIATION RESPONSE | PDC MEASUREMENT INITIATION FAILURE | +| PRS Configuration Exchange | PRS CONFIGURATION REQUEST | PRS CONFIGURATION RESPONSE | PRS CONFIGURATION FAILURE | +| Measurement Preconfiguration | MEASUREMENT PRECONFIGURATION REQUIRED | MEASUREMENT PRECONFIGURATION CONFIRM | MEASUREMENT PRECONFIGURATION REFUSE | +| Timing Synchronisation Status | TIMING SYNCHRONISATION STATUS REQUEST | TIMING SYNCHRONISATION STATUS RESPONSE | TIMING SYNCHRONISATION STATUS FAILURE | +| Multicast Context Notification | MULTICAST CONTEXT NOTIFICATION INDICATION | MULTICAST CONTEXT NOTIFICATION CONFIRM | MULTICAST CONTEXT NOTIFICATION REFUSE | +| Multicast Common Configuration | MULTICAST COMMON CONFIGURATION REQUEST | MULTICAST COMMON CONFIGURATION RESPONSE | MULTICAST COMMON CONFIGURATION REFUSE | + +**Table 2: Class 2 procedures** + +| Elementary Procedure | Message | +|-----------------------------------------------|-------------------------------------| +| Error Indication | ERROR INDICATION | +| UE Context Release Request (gNB-DU initiated) | UE CONTEXT RELEASE REQUEST | +| Initial UL RRC Message Transfer | INITIAL UL RRC MESSAGE TRANSFER | +| DL RRC Message Transfer | DL RRC MESSAGE TRANSFER | +| UL RRC Message Transfer | UL RRC MESSAGE TRANSFER | +| UE Inactivity Notification | UE INACTIVITY NOTIFICATION | +| System Information Delivery | SYSTEM INFORMATION DELIVERY COMMAND | +| Paging | PAGING | +| Notify | NOTIFY | +| PWS Restart Indication | PWS RESTART INDICATION | +| PWS Failure Indication | PWS FAILURE INDICATION | +| gNB-DU Status Indication | GNB-DU STATUS INDICATION | +| RRC Delivery Report | RRC DELIVERY REPORT | +| Network Access Rate Reduction | NETWORK ACCESS RATE REDUCTION | +| Trace Start | TRACE START | +| Deactivate Trace | DEACTIVATE TRACE | + +| Elementary Procedure | Message | +|----------------------------------------------|-------------------------------------------------| +| DU-CU Radio Information Transfer | DU-CU RADIO INFORMATION TRANSFER | +| CU-DU Radio Information Transfer | CU-DU RADIO INFORMATION TRANSFER | +| Resource Status Reporting | RESOURCE STATUS UPDATE | +| Access And Mobility Indication | ACCESS AND MOBILITY INDICATION | +| Reference Time Information Reporting Control | REFERENCE TIME INFORMATION REPORTING CONTROL | +| Reference Time Information Report | REFERENCE TIME INFORMATION REPORT | +| Access Success | ACCESS SUCCESS | +| Cell Traffic Trace | CELL TRAFFIC TRACE | +| Positioning Assistance Information Control | POSITIONING ASSISTANCE INFORMATION CONTROL | +| Positioning Assistance Information Feedback | POSITIONING ASSISTANCE INFORMATION FEEDBACK | +| Positioning Measurement Report | POSITIONING MEASUREMENT REPORT | +| Positioning Measurement Abort | POSITIONING MEASUREMENT ABORT | +| Positioning Measurement Failure Indication | POSITIONING MEASUREMENT FAILURE INDICATION | +| Positioning Measurement Update | POSITIONING MEASUREMENT UPDATE | +| Positioning Deactivation | POSITIONING DEACTIVATION | +| E-CID Measurement Failure Indication | E-CID MEASUREMENT FAILURE INDICATION | +| E-CID Measurement Report | E-CID MEASUREMENT REPORT | +| E-CID Measurement Termination | E-CID MEASUREMENT TERMINATION COMMAND | +| Positioning Information Update | POSITIONING INFORMATION UPDATE | +| Multicast Group Paging | MULTICAST GROUP PAGING | +| Broadcast Context Release Request | BROADCAST CONTEXT RELEASE REQUEST | +| Multicast Context Release Request | MULTICAST CONTEXT RELEASE REQUEST | +| PDC Measurement Report | PDC MEASUREMENT REPORT | +| PDC Measurement Termination | PDC MEASUREMENT TERMINATION COMMAND | +| PDC Measurement Failure Indication | PDC MEASUREMENT FAILURE INDICATION | +| PDC Measurement Termination | PDC MEASUREMENT TERMINATION COMMAND | +| Measurement Activation | MEASUREMENT ACTIVATION | +| QoE Information Transfer | QOE INFORMATION TRANSFER | +| Positioning System Information Delivery | POSITIONING SYSTEM INFORMATION DELIVERY COMMAND | +| DU-CU Cell Switch Notification | DU-CU CELL SWITCH NOTIFICATION | +| CU-DU Cell Switch Notification | CU-DU CELL SWITCH NOTIFICATION | +| DU-CU TA Information Transfer | DU-CU TA INFORMATION | + +| Elementary Procedure | Message | +|------------------------------------------|--------------------------------------| +| | TRANSFER | +| CU-DU TA Information Transfer | CU-DU TA INFORMATION TRANSFER | +| QoE Information Transfer Control | QOE INFORMATION TRANSFER CONTROL | +| RACH Indication | RACH INDICATION | +| Timing Synchronisation Status Report | TIMING SYNCHRONISATION STATUS REPORT | +| Mobile IAB F1 Setup Triggering | MIAB F1 SETUP TRIGGERING | +| Mobile IAB F1 Setup Outcome Notification | MIAB F1 SETUP OUTCOME NOTIFICATION | +| Broadcast Transport Resource Request | BROADCAST TRANSPORT RESOURCE REQUEST | + +## 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 FIAP UE-related contexts, in the event of a failure in the gNB-CU or gNB-DU. This procedure does not affect the application level configuration data exchanged during, e.g., the F1 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 + +![Sequence diagram showing the Reset procedure initiated from the gNB-CU. The gNB-CU sends a RESET message to the gNB-DU, and the gNB-DU responds with a RESET ACKNOWLEDGE message.](678ac9faaa56bb929499cebeea83a110_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-CU: Initiate Reset + gNB-CU->>gNB-DU: RESET + gNB-DU-->>gNB-CU: RESET ACKNOWLEDGE + +``` + +Sequence diagram showing the Reset procedure initiated from the gNB-CU. The gNB-CU sends a RESET message to the gNB-DU, and the gNB-DU responds with a RESET ACKNOWLEDGE message. + +**Figure 8.2.1.2.1-1: Reset procedure initiated from the gNB-CU. Successful operation** + +In the event of a failure at the gNB-CU, which has resulted in the loss of some or all transaction reference information, a RESET message shall be sent to the gNB-DU. + +At reception of the RESET message the gNB-DU shall release all allocated resources on F1 and radio resources related to the UE association(s) indicated explicitly or implicitly in the RESET message and remove the indicated UE contexts including F1AP ID. + +After the gNB-DU has released all assigned F1 resources and the UE F1AP IDs for all indicated UE associations which can be used for new UE-associated logical F1-connections over the F1 interface, the gNB-DU shall respond with the RESET ACKNOWLEDGE message. The gNB-DU does not need to wait for the release of radio resources to be completed before returning the RESET ACKNOWLEDGE message. + +If the RESET message contains the *UE-associated logical F1-connection list* IE, then: + +- The gNB-DU shall use the *gNB-CU UE F1AP ID* IE and/or the *gNB-DU UE F1AP ID* IE to explicitly identify the UE association(s) to be reset. +- The gNB-DU shall include in the RESET ACKNOWLEDGE message, for each UE association to be reset, the *UE-associated logical F1-connection Item* IE in the *UE-associated logical F1-connection list* IE. The *UE-associated logical F1-connection Item* IEs shall be in the same order as received in the RESET message and shall include also unknown UE-associated logical F1-connections. Empty *UE-associated logical F1-connection Item* IEs, received in the RESET message, may be omitted in the RESET ACKNOWLEDGE message. +- If the *gNB-CU UE F1AP ID* IE is included in the *UE-associated logical F1-connection Item* IE for a UE association, the gNB-DU shall include the *gNB-CU UE F1AP ID* IE in the corresponding *UE-associated logical F1-connection Item* IE in the RESET ACKNOWLEDGE message. +- If the *gNB-DU UE F1AP ID* IE is included in the *UE-associated logical F1-connection Item* IE for a UE association, the gNB-DU shall include the *gNB-DU UE F1AP ID* IE in the corresponding *UE-associated logical F1-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 F1 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-DU + +![Sequence diagram showing the Reset procedure initiated from the gNB-DU. The gNB-DU sends a RESET message to the gNB-CU, and the gNB-CU responds with a RESET ACKNOWLEDGE message.](1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: [ ] + gNB-DU->>gNB-CU: RESET + Note right of gNB-CU: [ ] + gNB-CU-->>gNB-DU: RESET ACKNOWLEDGE +``` + +Sequence diagram showing the Reset procedure initiated from the gNB-DU. The gNB-DU sends a RESET message to the gNB-CU, and the gNB-CU responds with a RESET ACKNOWLEDGE message. + +**Figure 8.2.1.2.2-1: Reset procedure initiated from the gNB-DU. Successful operation** + +In the event of a failure at the gNB-DU, which has resulted in the loss of some or all transaction reference information, a RESET message shall be sent to the gNB-CU. + +At reception of the RESET message the gNB-CU shall release all allocated resources on F1 related to the UE association(s) indicated explicitly or implicitly in the RESET message and remove the F1AP ID for the indicated UE associations. + +After the gNB-CU has released all assigned F1 resources and the UE F1AP IDs for all indicated UE associations which can be used for new UE-associated logical F1-connections over the F1 interface, the gNB-CU shall respond with the RESET ACKNOWLEDGE message. + +If the RESET message contains the *UE-associated logical F1-connection list* IE, then: + +- The gNB-CU shall use the *gNB-CU UE F1AP ID* IE and/or the *gNB-DU UE F1AP ID* IE to explicitly identify the UE association(s) to be reset. +- The gNB-CU shall in the RESET ACKNOWLEDGE message include, for each UE association to be reset, the *UE-associated logical F1-connection Item* IE in the *UE-associated logical F1-connection list* IE. The *UE-associated logical F1-connection Item* IEs shall be in the same order as received in the RESET message and shall include also unknown UE-associated logical F1-connections. Empty *UE-associated logical F1-connection Item* IEs, received in the RESET message, may be omitted in the RESET ACKNOWLEDGE message. +- If the *gNB-CU UE F1AP ID* IE is included in the *UE-associated logical F1-connection Item* IE for a UE association, the gNB-CU shall include the *gNB-CU UE F1AP ID* IE in the corresponding *UE-associated logical F1-connection Item* IE in the RESET ACKNOWLEDGE message. +- If the *gNB-DU UE F1AP ID* IE is included in a *UE-associated logical F1-connection Item* IE for a UE association, the gNB-CU shall include the *gNB-DU UE F1AP ID* IE in the corresponding *UE-associated logical F1-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 F1 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. A gNB-CU sends an ERROR INDICATION message to a gNB-DU.](8825e92f1c325d7393a17cdcdf31a292_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + Note right of gNB-CU: + gNB-CU->>gNB-DU: ERROR INDICATION + Note left of gNB-DU: + Note right of gNB-CU: +``` + +The diagram illustrates the Error Indication procedure. It shows two entities, gNB-DU and gNB-CU, represented by boxes at the top. Below each box is a vertical line representing a lifeline, ending in a thick horizontal bar. A horizontal arrow labeled "ERROR INDICATION" points from the gNB-CU lifeline to the gNB-DU lifeline. + +Sequence diagram showing the Error Indication procedure. A gNB-CU sends an ERROR INDICATION message to a gNB-DU. + +Figure 8.2.2.2-1: Error Indication procedure, gNB-CU originated. Successful operation + +![Diagram showing the Error Indication procedure. A gNB-DU sends an ERROR INDICATION message to a gNB-CU. The diagram shows two boxes, gNB-DU and gNB-CU, with a horizontal arrow labeled 'ERROR INDICATION' pointing from the gNB-DU to the gNB-CU. Both boxes have a vertical line extending downwards to a thick horizontal bar representing the ground or a common reference level.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +Diagram showing the Error Indication procedure. A gNB-DU sends an ERROR INDICATION message to a gNB-CU. The diagram shows two boxes, gNB-DU and gNB-CU, with a horizontal arrow labeled 'ERROR INDICATION' pointing from the gNB-DU to the gNB-CU. Both boxes have a vertical line extending downwards to a thick horizontal bar representing the ground or a common reference level. + +**Figure 8.2.2.2-2: Error Indication procedure, gNB-DU 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 UE F1AP ID* IE and *gNB-DU UE F1AP ID* IE shall be included in the ERROR INDICATION message. If one or both of the *gNB-CU UE F1AP ID* IE and the *gNB-DU UE F1AP ID* IE are not correct, the cause shall be set to appropriate value, e.g., "Unknown or already allocated gNB-CU UE F1AP ID", "Unknown or already allocated gNB-DU UE F1AP ID" or "Unknown or inconsistent pair of UE F1AP ID". + +### 8.2.2.3 Abnormal Conditions + +Not applicable. + +## 8.2.3 F1 Setup + +### 8.2.3.1 General + +The purpose of the F1 Setup procedure is to exchange application level data needed for the gNB-DU and the gNB-CU to correctly interoperate on the F1 interface. This procedure shall be the first F1AP procedure triggered for the F1-C interface instance after a TNL association has become operational. + +NOTE: If F1-C signalling transport is shared among multiple F1-C interface instances, one F1 Setup procedure is issued per F1-C interface instance to be setup, i.e. several F1 Setup procedures may be issued via the same TNL association after that TNL association has become operational. + +NOTE: Exchange of application level configuration data also applies between the gNB-DU and the gNB-CU in case the DU does not broadcast system information other than for radio frame timing and SFN, as specified in the TS 37.340 [7]. How to use this information when this option is used is not explicitly specified. + +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 F1AP 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 F1 Setup procedure: Successful Operation. The diagram shows two vertical lifelines: gNB-DU on the left and gNB-CU on the right. A horizontal arrow labeled 'F1 SETUP REQUEST' points from the gNB-DU lifeline to the gNB-CU lifeline. A return horizontal arrow labeled 'F1 SETUP RESPONSE' points from the gNB-CU lifeline back to the gNB-DU lifeline. Both lifelines end with a thick horizontal bar at the bottom.](fb4274c4b7882a4059103f1dbca9b111_img.jpg) + +Sequence diagram of the F1 Setup procedure: Successful Operation. The diagram shows two vertical lifelines: gNB-DU on the left and gNB-CU on the right. A horizontal arrow labeled 'F1 SETUP REQUEST' points from the gNB-DU lifeline to the gNB-CU lifeline. A return horizontal arrow labeled 'F1 SETUP RESPONSE' points from the gNB-CU lifeline back to the gNB-DU lifeline. Both lifelines end with a thick horizontal bar at the bottom. + +**Figure 8.2.3.2-1: F1 Setup procedure: Successful Operation** + +The gNB-DU initiates the procedure by sending a F1 SETUP REQUEST message including the appropriate data to the gNB-CU. The gNB-CU responds with a F1 SETUP RESPONSE message including the appropriate data. + +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 F1 interface is operational and other F1 messages may be exchanged. + +If the F1 SETUP REQUEST message contains the *gNB-DU Name* IE, the gNB-CU may use this IE as a human readable name of the gNB-DU. If the F1 SETUP REQUEST message contains the *Extended gNB-DU Name* IE, the gNB-CU may use this IE as a human readable name of the gNB-DU and shall ignore the *gNB-DU Name* IE if included. + +If the F1 SETUP RESPONSE message contains the *gNB-CU Name* IE, the gNB-DU may use this IE as a human readable name of the gNB-CU. If the F1 SETUP RESPONSE message contains the *Extended gNB-CU Name* IE, the gNB-DU may use this IE as a human readable name of the gNB-CU and shall ignore the *gNB-CU Name* IE if included. + +If the F1 SETUP REQUEST message contains the *gNB-DU Served Cells List* IE, the gNB-CU shall take into account as specified in TS 38.401 [4]. + +For NG-RAN, the gNB-DU shall include the *gNB-DU System Information* IE and the *TAI Slice Support List* IE in the F1 SETUP REQUEST message. + +The gNB-CU may include the *Cells to be Activated List* IE in the F1 SETUP RESPONSE message. The *Cells to be Activated List* IE includes a list of cells that the gNB-CU requests the gNB-DU to activate. The gNB-DU shall activate the cells included in the *Cells to be Activated List* IE and reconfigure the physical cell identity for cells for which the *NR PCI* IE is included. + +If *Cells to be Activated List Item* IE is included in the F1 SETUP RESPONSE message, and the information for the cell indicated by the *NR CGI* IE includes the *IAB Info IAB-donor-CU* IE, the gNB-DU shall, if supported, apply the *IAB STC Info* IE therein to the indicated cell. + +For NG-RAN, the gNB-CU shall include the *gNB-CU System Information* IE in the F1 SETUP RESPONSE message. + +For NG-RAN, the gNB-DU may include the *RAN Area Code* IE in the F1 SETUP REQUEST message. The gNB-CU may use it according to TS 38.300 [6]. + +For NG-RAN, the gNB-DU may include *Supported MBS FSA ID List* IE in the *Served Cell Information* IE in the F1 SETUP REQUEST message. The gNB-CU may use it according to TS 38.300 [6]. + +For NG-RAN, the gNB-CU may include *Available PLMN List* IE, and optionally also *Extended Available PLMN List* IE in the F1 SETUP RESPONSE message, if the available PLMN(s) are different from what gNB-DU has provided in F1 SETUP REQUEST message, gNB-DU shall take this into account and only broadcast the PLMN(s) included in the received Available PLMN list(s). + +For NG-RAN, the gNB-CU may include *Available SNPN ID List* IE in the F1 SETUP RESPONSE message. If the available SNPN(s) are different from what gNB-DU has provided in F1 SETUP REQUEST message, gNB-DU shall take this into account and only broadcast the SNPN(s) included in the received Available SNPN ID list. + +The *Latest RRC Version Enhanced* IE shall be included in the F1 SETUP REQUEST message and in the F1 SETUP RESPONSE message. + +If in F1 SETUP REQUEST message, the *Cell Direction* IE is present, the gNB-CU should use it to understand whether the cell is for UL or DL only. If in F1 SETUP REQUEST message, the *Cell Direction* IE is omitted in the *Served Cell Information* IE it shall be interpreted as that the Cell Direction is Bi-directional. + +If the *Intended TDD DL-UL Configuration* IE is present in the F1 SETUP REQUEST message, the receiving gNB-CU shall use the received information for Cross Link Interference management and/or NR-DC power coordination. The gNB-CU may merge the Intended TDD DL-UL Configuration information received from two or more gNB-DUs. The gNB-CU shall consider the received *Intended TDD DL-UL Configuration* content valid until reception of an update of the IE for the same cell(s). + +If the *Aggressor gNB Set ID* IE is included in the *Served Cell Information* IE in the F1 SETUP REQUEST message, the gNB-CU shall, if supported, take it into account. + +If the *Victim gNB Set ID* IE is included in the *Served Cell Information* IE in the F1 SETUP REQUEST message, the gNB-CU shall, if supported, take it into account. + +If the F1 SETUP REQUEST message contains the Transport Layer Address Info IE, the gNB-CU shall, if supported, take into account for IPSec tunnel establishment. + +If the *SFN Offset* IE is contained in the *Served Cell Information* IE in the F1 SETUP REQUEST message, the gNB-CU shall, if supported, use this information to deduce the SFN0 offset of the reported cell. + +If the F1 SETUP RESPONSE message contains the *Transport Layer Address Info* IE, the gNB-DU shall, if supported, take into account for IPSec tunnel establishment. + +If the F1 SETUP RESPONSE message contains the *Uplink BH Non-UP Traffic Mapping* IE, the gNB-DU shall, if supported, consider the information therein for mapping of non-UP uplink traffic. + +If the *BAP Address* IE is included in the F1 SETUP REQUEST message, while the *RRC Terminating IAB-Donor gNB-ID* IE is not included in the message, the receiving gNB-CU shall, if supported, consider the information therein for discovering the collocation of an IAB-DU and an IAB-MT. + +If the F1 SETUP REQUEST message is received from an IAB-donor-DU, the gNB-CU shall, if supported, include the *BAP Address* IE in the F1 SETUP RESPONSE message. + +NOTE: How to identify the IAB-donor-DU is up to gNB-CU implementation. + +If the F1 SETUP RESPONSE message contains the *BAP Address* IE, the gNB-DU shall, if supported, store the received BAP address and use it as specified in TS 38.340 [30]. + +If the *NR PRACH Configuration List* IE is included in the *Served Cell Information* IE contained in the F1 SETUP REQUEST message, the gNB-CU may store the information, and forward it to other RAN nodes for RACH optimisation. If the *L139 Info* IE included in the *NR PRACH Configuration List* IE is present, it shall contain the *Root Sequence Index* IE. + +If the *RedCap Broadcast Information* IE is included in the *Served Cell Information* IE in the F1 SETUP REQUEST message, the gNB-CU may store and use this information to determine a suitable target in case of subsequent outgoing mobility involving RedCap UEs. + +If the *eRedCap Broadcast Information* IE is included in the *Served Cell Information* IE in the F1 SETUP REQUEST message, the gNB-CU may store and use this information to determine a suitable target in case of subsequent outgoing mobility involving eRedCap UEs. + +If the *TAI NSAG Support List* IE is included in the *Served Cell Information* IE in the F1 SETUP REQUEST message, the gNB-CU shall, if supported, use this information as specified in TS 23.501 [21]. + +If both the *RRC Terminating IAB-Donor gNB-ID* IE and the *BAP Address* IE are included in the F1 SETUP REQUEST message, the gNB-CU shall, if supported, consider the BAP address indicated by the *BAP address* IE is assigned by the gNB-CU of the RRC-terminating IAB-donor indicated by the *RRC Terminating IAB-Donor gNB-ID* IE, and use this BAP address and gNB-ID for the subsequent IAB Transport Migration Management procedure towards the RRC-terminating IAB-donor of the mobile IAB-node, as specified in TS 38.423 [28]. + +If the F1 SETUP REQUEST message contains the *Mobile IAB-MT User Location Information* IE, the gNB-CU shall, if supported, take into account when reporting UE location information to the AMF for a UE served by the mobile IAB-node. + +### 8.2.3.3 Unsuccessful Operation + +![Sequence diagram showing the F1 Setup procedure: Unsuccessful Operation. The gNB-DU sends an F1 SETUP REQUEST to the gNB-CU, and the gNB-CU responds with an F1 SETUP FAILURE.](db5deafdae53dbc7d5972957f708c691_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: F1 SETUP REQUEST + Note right of gNB-CU: + gNB-CU-->>gNB-DU: F1 SETUP FAILURE + Note left of gNB-DU: +``` + +Sequence diagram showing the F1 Setup procedure: Unsuccessful Operation. The gNB-DU sends an F1 SETUP REQUEST to the gNB-CU, and the gNB-CU responds with an F1 SETUP FAILURE. + +Figure 8.2.3.3-1: F1 Setup procedure: Unsuccessful Operation + +If the gNB-CU cannot accept the setup, it should respond with a F1 SETUP FAILURE and appropriate cause value. + +If the F1 SETUP FAILURE message includes the *Time To Wait* IE, the gNB-DU shall wait at least for the indicated time before reinitiating the F1 setup towards the same gNB-CU. + +### 8.2.3.4 Abnormal Conditions + +Not applicable. + +## 8.2.4 gNB-DU Configuration Update + +### 8.2.4.1 General + +The purpose of the gNB-DU Configuration Update procedure is to update application level configuration data needed for the gNB-DU and the gNB-CU to interoperate correctly on the F1 interface. This procedure does not affect existing UE-related contexts, if any. The procedure uses non-UE associated signalling. + +NOTE: Update of application level configuration data also applies between the gNB-DU and the gNB-CU in case the DU does not broadcast system information other than for radio frame timing and SFN, as specified in the TS 37.340 [7]. How to use this information when this option is used is not explicitly specified. + +## 8.2.4.2 Successful Operation + +![Sequence diagram illustrating the gNB-DU Configuration Update procedure for Successful Operation. The diagram shows two vertical lifelines: gNB-DU on the left and gNB-CU on the right. The gNB-DU sends a 'GNB-DU CONFIGURATION UPDATE' message to the gNB-CU. The gNB-CU responds with a 'GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE' message back to the gNB-DU. Both lifelines end with a solid black horizontal bar at the bottom.](fe7304192caf64cda93b580c5e7e5c06_img.jpg) + +``` + +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: GNB-DU CONFIGURATION UPDATE + Note right of gNB-CU: + gNB-CU-->>gNB-DU: GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE + Note left of gNB-DU: + Note right of gNB-CU: + +``` + +Sequence diagram illustrating the gNB-DU Configuration Update procedure for Successful Operation. The diagram shows two vertical lifelines: gNB-DU on the left and gNB-CU on the right. The gNB-DU sends a 'GNB-DU CONFIGURATION UPDATE' message to the gNB-CU. The gNB-CU responds with a 'GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE' message back to the gNB-DU. Both lifelines end with a solid black horizontal bar at the bottom. + +**Figure 8.2.4.2-1: gNB-DU Configuration Update procedure: Successful Operation** + +The gNB-DU initiates the procedure by sending a GNB-DU CONFIGURATION UPDATE message to the gNB-CU including an appropriate set of updated configuration data that it has just taken into operational use. The gNB-CU responds with GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. If an information element is not included in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall interpret that the corresponding configuration data is not changed and shall continue to operate the F1-C interface 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 *gNB-DU ID* IE is contained in the GNB-DU CONFIGURATION UPDATE message for a newly established SCTP association, the gNB-CU will associate this association with the related gNB-DU. + +If *Served Cells To Add Item* IE is contained in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall add cell information according to the information in the *Served Cell Information IE*. For NG-RAN, the gNB-DU shall include the *gNB-DU System Information IE*. + +If *Served Cells To Modify Item* IE is contained in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall modify information of cell indicated by *Old NR CGI IE* according to the information in the *Served Cell Information IE* and overwrite the served cell information for the affected served cell. Further, if the *gNB-DU System Information IE* is present the gNB-CU shall store and replace any previous information received. + +If *Served Cells To Delete Item* IE is contained in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall delete information of cell indicated by *Old NR CGI IE*. + +If *Cells Status Item IE* is contained in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall update the information about the cells, as described in TS 38.401 [4]. If if the *Switching Off Ongoing IE* is present in the *Cells Status Item IE*, contained in the GNB-DU CONFIGURATION UPDATE message, and the corresponding *Service State IE* is set to "Out-of-Service", the gNB-CU shall ignore the *Switching Off Ongoing IE*. + +If *Cells to be Activated List Item IE* is contained in the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB-DU shall activate the cell indicated by *NR CGI IE* and reconfigure the physical cell identity for cells for which the *NR PCI IE* is included. + +If *Cells to be Activated List Item IE* is contained in the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message and the indicated cells are already activated, the gNB-DU shall update the cell information received in *Cells to be Activated List Item IE*. + +If *Cells to be Activated List Item IE* is included in the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message, and the information for the cell indicated by the *NR CGI IE* includes the *IAB Info IAB-donor-CU IE*, the gNB-DU shall, if supported, apply the *IAB STC Info IE* therein to the indicated cell. + +If *Cells to be Deactivated List Item* IE is contained in the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB-DU shall deactivate all the cells with NR CGI listed in the IE. + +If *Dedicated SI Delivery Needed UE List* IE is contained in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU should take it into account when informing the UE of the updated system information via the dedicated RRC message. + +For NG-RAN, the gNB-CU shall include the *gNB-CU System Information* IE in the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message. The *SIB type to Be Updated List* IE shall contain the full list of SIBs to be broadcast. + +For NG-RAN, the gNB-DU may include the *RAN Area Code* IE in the GNB-DU CONFIGURATION UPDATE message. The gNB-CU shall store and replace any previously provided *RAN Area Code* IE by the received *RAN Area Code* IE. + +For NG-RAN, the gNB-DU may include the *Supported MBS FSA ID List* IE in the *Served Cell Information* IE in the GNB-DU CONFIGURATION UPDATE message. The gNB-CU shall store and replace any previously provided *MBS FSA ID list* IE by the received *MBS FSA ID list* IE. + +If *Available PLMN List* IE, and optionally also *Extended Available PLMN List* IE, is contained in GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB-DU shall overwrite the whole available PLMN list and update the corresponding system information. + +If *Available SNPN ID List* IE is contained in GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB-DU shall overwrite the whole available SNPN ID list and update the corresponding system information. + +If in GNB-DU CONFIGURATION UPDATE message, the *Cell Direction* IE is present, the gNB-CU should use it to understand whether the cell is for UL or DL only. If in GNB-DU CONFIGURATION UPDATE message, the *Cell Direction* IE is omitted in the *Served Cell Information* IE it shall be interpreted as that the Cell Direction is Bi-directional. + +If the GNB-DU CONFIGURATION UPDATE message includes *gNB-DU TNL Association To Remove List* IE, the gNB-CU shall, if supported, initiate removal of the TNL association(s) indicated by gNB-DU TNL endpoint(s) and gNB-CU TNL endpoint(s) if the *TNL Association Transport Layer Address gNB-CU* IE is present, or the TNL association(s) indicated by gNB-DU TNL endpoint(s) if the *TNL Association Transport Layer Address gNB-CU* IE is absent: + +- if the received *TNL Association Transport Layer Address* IE includes the *Port Number* IE, the gNB-DU TNL endpoint is identified by the *Endpoint IP Address* IE and the *Port Number* IE. Otherwise, the gNB-DU TNL endpoints correspond to all gNB-DU TNL endpoints identified by the *Endpoint IP Address* IE and any port number(s). +- if the received *TNL Association Transport Layer Address gNB-CU* IE includes the *Port Number* IE, the gNB-CU TNL endpoint is identified by the *Endpoint IP Address* IE and the *Port Number* IE. Otherwise, the gNB-CU TNL endpoints correspond to all gNB-CU TNL endpoints identified by the *Endpoint IP Address* IE and any port number(s). + +If the *Intended TDD DL-UL Configuration* IE is present in the GNB-DU CONFIGURATION UPDATE message, the receiving gNB-CU shall use the received information for Cross Link Interference management and/or NR-DC power coordination. The gNB-CU may merge the Intended TDD DL-UL Configuration information received from two or more gNB-DUs. The gNB-CU shall consider the received *Intended TDD DL-UL Configuration* IE content valid until reception of an update of the IE for the same cell(s). + +If the *Aggressor gNB Set ID* IE is included in the *Served Cell Information* IE in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall, if supported, take it into account. + +If the *Victim gNB Set ID* IE is included in the *Served Cell Information* IE in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall, if supported, take it into account. + +If the GNB-DU CONFIGURATION UPDATE message includes *Transport Layer Address Info* IE, the gNB-CU shall, if supported, take into account for IPSec tunnel establishment. + +If the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message includes *Transport Layer Address Info* IE, the gNB-DU shall, if supported, take into account for IPSec tunnel establishment. + +If the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message contains the *Uplink BH Non-UP Traffic Mapping* IE, the gNB-DU shall, if supported, consider the information therein for mapping of non-UP uplink traffic. + +If the *SFN Offset* IE is contained in the *Served Cell Information* IE in GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall, if supported, use this information to deduce the SFN0 offset of the reported cell. + +If the *NR PRACH Configuration List* IE is included in the *Served Cell Information* IE contained in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU may store the information, and forward it to other RAN nodes for RACH optimisation. If the *L139 Info* IE included in the *NR PRACH Configuration List* IE is present, it shall contain the *Root Sequence Index* IE. + +If the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message contains the *BAP Address* IE, the gNB-DU shall, if supported, store the received BAP address and use it as specified in TS 38.340 [30]. + +If the *Coverage Modification Notification* IE is contained in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall, if supported, take it into account for Coverage and Capacity Optimization and network energy saving. If the *Coverage Modification Cause* IE is set to the "network energy saving", gNB-CU may consider those deactivated SSB beams are due to network energy saving. + +If the *Cells for SON* IE is present in the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB-DU may store or update this information and behaves as follows: + +- For each served cell indicated by the *NR CGI* IE included within the *Cells for SON Item* IE, the gNB-DU may adjust the PRACH configuration of this served cell. +- If the *Neighbour NR Cells for SON List* IE is present in the *Cells for SON Item* IE, the gNB-DU may take the PRACH configuration of neighbour cells included in the *Neighbour NR Cells for SON List* IE into consideration when adjusting the PRACH configuration of the served cell. + +If the *RedCap Broadcast Information* IE is contained in the *Served Cell Information* IE in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU may store and use this information to determine a suitable target in case of subsequent outgoing mobility involving RedCap UEs. + +If the *eRedCap Broadcast Information* IE is contained in the *Served Cell Information* IE in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU may store and use this information to determine a suitable target in case of subsequent outgoing mobility involving eRedCap UEs. + +If the *TAI NSAG Support List* IE is included in the *Served Cell Information* IE in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall, if supported, use this information as specified in TS 23.501 [21]. + +If the *gNB-DU Name* IE is included in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU may store it or update this IE value if already stored, and use it as a human readable name of the gNB-DU. If the *Extended gNB-DU Name* IE is included in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU may store it or update this IE value if already stored, and use it as a human readable name of the gNB-DU and shall ignore the *gNB-DU Name* IE if also included. + +If the *RRC Terminating IAB-Donor Related Info* IE is included in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall, if supported, consider that the BAP address indicated by the *Mobile IAB-MT BAP Address* IE is assigned by the gNB-CU of the RRC-terminating IAB-donor indicated by the *RRC Terminating IAB-Donor gNB-ID* IE, and it shall use this BAP address and gNB ID for the subsequent IAB Transport Migration Management procedure towards the RRC-terminating IAB-donor of the mobile IAB-node, as specified in TS 38.423 [28]. + +If the GNB-DU CONFIGURATION UPDATE message contains the *Mobile IAB-MT User Location Information* IE, the gNB-CU shall, if supported, take it into account when reporting UE location information to the AMF for a UE served by the mobile IAB-node. + +If the *NCGI to be Updated List* IE is included in the F1 SETUP RESPONSE message, the gNB-DU shall, if supported, change the NCGI of the cell indicated by the *Old NCGI* IE to the NCGI indicated by the *New NCGI* IE. + +#### 8.2.4.3 Unsuccessful Operation + +![Sequence diagram for gNB-DU Configuration Update procedure: Unsuccessful Operation](237b76118be454462fc9b4e96adaa6c7_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: GNB-DU CONFIGURATION UPDATE + Note right of gNB-CU: + gNB-CU-->>gNB-DU: GNB-DU CONFIGURATION UPDATE FAILURE + Note left of gNB-DU: +``` + +The diagram shows a sequence of messages between a gNB-DU and a gNB-CU. The gNB-DU sends a 'GNB-DU CONFIGURATION UPDATE' message to the gNB-CU. The gNB-CU responds with a 'GNB-DU CONFIGURATION UPDATE FAILURE' message. Both entities are represented by boxes with lifelines extending downwards, and there are solid black bars at the bottom of each lifeline. + +Sequence diagram for gNB-DU Configuration Update procedure: Unsuccessful Operation + +Figure 8.2.4.3-1: gNB-DU Configuration Update procedure: Unsuccessful Operation + +If the gNB-CU cannot accept the update, it shall respond with a GNB-DU CONFIGURATION UPDATE FAILURE message and appropriate cause value. + +If the GNB-DU CONFIGURATION UPDATE FAILURE message includes the *Time To Wait* IE, the gNB-DU shall wait at least for the indicated time before reinitiating the GNB-DU CONFIGURATION UPDATE message towards the same gNB-CU. + +#### 8.2.4.4 Abnormal Conditions + +Not applicable. + +### 8.2.5 gNB-CU Configuration Update + +#### 8.2.5.1 General + +The purpose of the gNB-CU Configuration Update procedure is to update application level configuration data needed for the gNB-DU and gNB-CU to interoperate correctly on the F1 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 for gNB-CU Configuration Update procedure: Successful Operation](5593facb376cb360bd4b0960b2911b3e_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-CU->>gNB-DU: GNB-CU CONFIGURATION UPDATE + Note right of gNB-CU: + gNB-DU-->>gNB-CU: GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE + Note left of gNB-DU: +``` + +The diagram shows a sequence of messages between a gNB-DU and a gNB-CU. The gNB-CU sends a 'GNB-CU CONFIGURATION UPDATE' message to the gNB-DU. The gNB-DU responds with a 'GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE' message. Both entities are represented by boxes with lifelines extending downwards, and there are solid black bars at the bottom of each lifeline. + +Sequence diagram for gNB-CU Configuration Update procedure: Successful Operation + +Figure 8.2.5.2-1: gNB-CU Configuration Update procedure: Successful Operation + +The gNB-CU initiates the procedure by sending a GNB-CU CONFIGURATION UPDATE message including the appropriate updated configuration data to the gNB-DU. The gNB-DU responds with a GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. If an information element is not included in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall interpret that the corresponding configuration data is not changed and shall continue to operate the F1-C interface with the existing related configuration data. + +The updated configuration data shall be stored in the respective node and used as long as there is an operational TNL association or until any further update is performed. + +If *Cells to be Activated List Item* IE is contained in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall activate the cell indicated by *NR CGI* IE and reconfigure the physical cell identity for which the *NR PCI* IE is included. + +If the *SSBs within the cell to be Activated List* IE is included in the *Cells to be Activated List Item* IE within the gNB-CU CONFIGURATION UPDATE message, the gNB-DU shall, if supported, only activate those SSB beams indicated by the *SSB Index* IE. + +If at least one requested SSB beam in the *SSBs within the cell to be Activated List* IE is activated, the gNB-DU includes the *Cells with SSBs Activated List* IE in the GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message. The gNB-CU shall consider that the SSB beams indicated by the *SSBs activated List* IE as activated. + +If *Cells to be Deactivated List Item* IE is contained in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall deactivate the cell indicated by *NR CGI* IE. + +If *Cells to be Activated List Item* IE is contained in the GNB-CU CONFIGURATION UPDATE message and the indicated cells are already activated, the gNB-DU shall update the cell information received in *Cells to be Activated List Item* IE. + +If *Cells to be Activated List Item* IE is included in the GNB-CU CONFIGURATION UPDATE message, and the information for the cell indicated by the *NR CGI* IE includes the *IAB Info IAB-donor-CU* IE, the gNB-DU shall, if supported, apply the *IAB STC Info* IE therein to the indicated cell. + +If the *Cells Allowed to be Deactivated List* IE is contained in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall, if supported, consider that it is allowed to deactivate the SSB beams within the indicated cells for network energy saving purpose. + +If the *gNB-CU System Information* IE is contained in the gNB-CU CONFIGURATION UPDATE message, the gNB-DU shall include the *Dedicated SI Delivery Needed UE List* IE in the GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message for UEs that are unable to receive system information from broadcast. + +If *Dedicated SI Delivery Needed UE List* IE is contained in the GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB-CU should take it into account when informing the UE of the updated system information via the dedicated RRC message. + +If the *gNB-CU TNL Association To Add List* IE is contained in the gNB-CU CONFIGURATION UPDATE message, the gNB-DU shall, if supported, use it to establish the TNL association(s) with the gNB-CU. If the *gNB-CU TNL Association To Add List* is included in the GNB-CU CONFIGURATION UPDATE message, and if the *TNL Association Transport Layer Information* IE does not include the *Port Number* IE, the gNB-DU shall assume that port number value 38472 is used for the endpoint. The gNB-DU shall report to the gNB-CU, in the gNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message, the successful establishment of the TNL association(s) with the gNB-CU as follows: + +- A list of TNL address(es) with which the gNB-DU successfully established the TNL association shall be included in the *gNB-CU TNL Association Setup List* IE; +- A list of TNL address(es) with which the gNB-DU failed to establish the TNL association shall be included in the *gNB-CU TNL Association Failed To Setup List* IE. + +If the GNB-CU CONFIGURATION UPDATE message includes *gNB-CU TNL Association To Remove List* IE, the gNB-DU shall, if supported, initiate removal of the TNL association(s) indicated by gNB-CU TNL endpoint(s) and gNB-DU TNL endpoint(s) if the *TNL Association Transport Layer Address gNB-DU* IE is present, or the TNL association(s) indicated by gNB-CU TNL endpoint(s) if the *TNL Association Transport Layer Address gNB-DU* IE is absent: + +- if the received *TNL Association Transport Layer Address* IE includes the *Port Number* IE, the gNB-CU TNL endpoint is identified by the *Endpoint IP Address* IE and the *Port Number* IE. Otherwise, the gNB-CU TNL endpoints correspond to all gNB-CU TNL endpoints identified by the *Endpoint IP Address* IE and any port number(s). +- if the received *TNL Association Transport Layer Address gNB-DU* IE includes the *Port Number* IE, the gNB-DU TNL endpoint is identified by the *Endpoint IP Address* IE and the *Port Number* IE. Otherwise, the gNB-DU TNL endpoints correspond to all gNB-DU node TNL endpoints identified by the *Endpoint IP Address* IE and any port number(s). + +If the *gNB-CU TNL Association To Update List* IE is contained in the gNB-CU CONFIGURATION UPDATE message the gNB-DU shall, if supported, overwrite the previously stored information for the related TNL Association(s). + +- if the received *TNL Association Transport Layer Address* IE includes the *Port Number* IE, the gNB-CU TNL endpoint is identified by the *Endpoint IP Address* IE and the *Port Number* IE. Otherwise, the gNB-CU TNL endpoints correspond to all gNB-CU TNL endpoints identified by the *Endpoint IP Address* IE and any port number(s). + +If in the gNB-CU CONFIGURATION UPDATE message the *TNL Association usage* IE is included in the *gNB-CU TNL Association To Add List* IE or the *gNB-CU TNL Association To Update List* IE, the gNB-DU node shall, if supported, use it as described in TS 38.472 [22]. + +For NG-RAN, the gNB-CU shall include the *gNB-CU System Information* IE in the GNB-CU CONFIGURATION UPDATE message. The *SIB type to Be Updated List* IE shall contain the full list of SIBs to be broadcast. + +If *Protected E-UTRA Resources List* IE is contained in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall protect the corresponding resource of the cells indicated by *E-UTRA Cells List* IE for spectrum sharing between E-UTRA and NR. + +If the GNB-CU CONFIGURATION UPDATE message contains the *Protected E-UTRA Resource Indication* IE, the receiving gNB-DU should forward it to lower layers and use it for cell-level resource coordination. The gNB-DU shall consider the received *Protected E-UTRA Resource Indication* IE when expressing its desired resource allocation during gNB-DU Resource Coordination procedure. The gNB-DU shall consider the received *Protected E-UTRA Resource Indication* IE content valid until reception of a new update of the IE for the same gNB-DU. + +If *Available PLMN List* IE, and optionally also *Extended Available PLMN List* IE, is contained in GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall overwrite the whole available PLMN list and update the corresponding system information. + +If *Available SNPN ID List* IE is contained in GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall overwrite the whole available SNPN ID list and update the corresponding system information. + +If *Cells Failed to be Activated Item* IE is contained in the GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB-CU shall consider that the indicated cells are out-of-service as defined in TS 38.401 [4]. + +If the *Neighbour Cell Information List* IE is present in the GNB-CU CONFIGURATION UPDATE message, the receiving gNB-DU shall use the received information for Cross Link Interference management and/or NR-DC power coordination. The gNB-DU shall consider the received *Neighbour Cell Information List* IE content valid until reception of an update of the IE for the same cell(s). If the *Intended TDD DL-UL Configuration NR* IE is absent from the *Neighbour Cell Information List* IE, whereas the corresponding *NR CGI* IE is present, the receiving gNB-DU shall remove the previously stored *Neighbour Cell Information* IE corresponding to the NR CGI. + +If the GNB-CU CONFIGURATION UPDATE message includes *Transport Layer Address Info* IE, the gNB-DU shall, if supported, take into account for IPSec tunnel establishment. + +If the GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message includes *Transport Layer Address Info* IE, the gNB-CU shall, if supported, take into account for IPSec tunnel establishment. + +If the GNB-CU CONFIGURATION UPDATE message contains the *Uplink BH Non-UP Traffic Mapping* IE, the gNB-DU shall, if supported, consider the information therein for mapping of non-UP uplink traffic. + +If the *IAB Barred* IE is included in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall, if supported, consider it as an indication of whether the cell allows IAB-node access or not. + +If the *BAP Address* IE is included in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall, if supported, store the received BAP address and use it as specified in TS 38.340 [30]. + +If the *CCO Assistance Information* IE is contained in the GNB-CU CONFIGURATION UPDATE message, and the *NR CGI* IE contained in the *Affected Cells and Beams* IE is served by the gNB-DU, the gNB-DU may use it to determine a new cell and/or beam configuration. + +If the *CCO Assistance Information* IE is contained in the GNB-CU CONFIGURATION UPDATE message and the *NR CGI* IE contained in the *Affected Cells and Beams* IE is not served by the gNB-DU, the gNB-DU may use it to adjust coverage of its cells. If the *CCO issue detection* IE set to "network energy saving" is included in the *CCO Assistance Information* IE, the gNB-DU may consider the indicated SSB beams by the *Affected Cells and Beam* IE are deactivated due to network energy saving. + +If the *Cells for SON* IE is present in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU may store or update this information and it behaves as follows: + +- For each served cell indicated by the *NR CGI* IE included within the *Cells for SON Item* IE, the gNB-DU may adjust the PRACH configuration of this served cell. +- If the *Neighbour NR Cells for SON List* IE is present in the *Cells for SON Item* IE, the gNB-DU may take the PRACH configuration of neighbour cells included in the *Neighbour NR Cells for SON List* IE into consideration when adjusting the PRACH configuration of the served cell. + +If the *gNB-CU Name* IE is included in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU may store it or update this IE value if already stored, and use it as a human readable name of the gNB-CU. If the *Extended gNB-CU Name* IE is included in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU may store it or update this IE value if already stored, and use it as a human readable name of the gNB-CU and shall ignore the *gNB-CU Name* IE if also included. + +### 8.2.5.3 Unsuccessful Operation + +![Sequence diagram showing an unsuccessful GNB-CU Configuration Update operation between a gNB-DU and a gNB-CU.](a9fa8656fd01e4e407bc91dba6ac0ad5_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: GNB-CU CONFIGURATION UPDATE + Note right of gNB-CU: + gNB-DU-->>gNB-CU: GNB-CU CONFIGURATION UPDATE FAILURE + Note left of gNB-DU: + Note right of gNB-CU: +``` + +The diagram illustrates a sequence of messages between a gNB-CU and a gNB-DU. The gNB-CU sends a 'GNB-CU CONFIGURATION UPDATE' message to the gNB-DU. The gNB-DU responds with a 'GNB-CU CONFIGURATION UPDATE FAILURE' message. Both entities are represented by rectangular boxes with vertical lines extending downwards to horizontal bars, indicating their lifelines. + +Sequence diagram showing an unsuccessful GNB-CU Configuration Update operation between a gNB-DU and a gNB-CU. + +Figure 8.2.5.3-1: gNB-CU Configuration Update: Unsuccessful Operation + +If the gNB-DU cannot accept the update, it shall respond with a GNB-CU CONFIGURATION UPDATE FAILURE message and appropriate cause value. + +If the GNB-CU CONFIGURATION UPDATE FAILURE message includes the *Time To Wait* IE, the gNB-CU shall wait at least for the indicated time before reinitiating the GNB-CU CONFIGURATION UPDATE message towards the same gNB-DU. + +#### 8.2.5.4 Abnormal Conditions + +Not applicable. + +### 8.2.6 gNB-DU Resource Coordination + +#### 8.2.6.1 General + +The purpose of the gNB-DU Resource Coordination procedure is to enable coordination of radio resource allocation between a gNB-CU and a gNB-DU for the purpose of spectrum sharing between E-UTRA and NR. This procedure is to be used only for the purpose of spectrum sharing between E-UTRA and NR. + +The procedure uses non-UE-associated signalling. + +#### 8.2.6.2 Successful Operation + +![Sequence diagram showing the successful operation of gNB-DU Resource Coordination. The gNB-CU sends a GNB-DU RESOURCE COORDINATION REQUEST to the gNB-DU, and the gNB-DU responds with a GNB-DU RESOURCE COORDINATION RESPONSE.](7913c315e0db8233cb1ac2455e4a0a81_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-CU: + gNB-CU->>gNB-DU: GNB-DU RESOURCE COORDINATION REQUEST + Note right of gNB-DU: + gNB-DU-->>gNB-CU: GNB-DU RESOURCE COORDINATION RESPONSE + Note left of gNB-CU: +``` + +Sequence diagram showing the successful operation of gNB-DU Resource Coordination. The gNB-CU sends a GNB-DU RESOURCE COORDINATION REQUEST to the gNB-DU, and the gNB-DU responds with a GNB-DU RESOURCE COORDINATION RESPONSE. + +Figure 8.2.6.2-1: gNB-DU Resource Coordination, successful operation + +A gNB-CU initiates the procedure by sending the GNB-DU RESOURCE COORDINATION REQUEST message to a gNB-DU over the F1 interface. + +The gNB-DU extracts the *E-UTRA – NR Cell Resource Coordination Request Container* IE and it replies by sending the GNB-DU RESOURCE COORDINATION RESPONSE message. + +In case of NR-initiated gNB-DU Resource Coordination procedure, the *Ignore Coordination Request Container* IE shall be present and set to "yes" and the *E-UTRA – NR Cell Resource Coordination Request Container* IE in the GNB-DU RESOURCE COORDINATION REQUEST message shall be ignored. + +### 8.2.7 gNB-DU Status Indication + +#### 8.2.7.1 General + +The purpose of the gNB-DU Status Indication procedure is informing the gNB-CU that the gNB-DU is overloaded so that overload reduction actions can be applied. This procedure is also used to inform the IAB-donor-CU about a downlink congestion at an IAB-DU or an IAB-donor-DU. The procedure uses non-UE associated signalling. + +### 8.2.7.2 Successful Operation + +![Sequence diagram showing the gNB-DU Status Indication procedure. A gNB-DU sends a GNB-DU STATUS INDICATION message to a gNB-CU.](376f80eb8a41369e87da63a0210d173e_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: GNB-DU STATUS INDICATION + Note right of gNB-CU: + Note left of gNB-DU: + Note right of gNB-CU: +``` + +Sequence diagram showing the gNB-DU Status Indication procedure. A gNB-DU sends a GNB-DU STATUS INDICATION message to a gNB-CU. + +**Figure 8.2.7.2-1: gNB-DU Status Indication procedure** + +If the *gNB-DU Overload Information* IE in the GNB-DU STATUS INDICATION message indicates that the gNB-DU is overloaded, the gNB-CU shall apply overload reduction actions until informed, with a new GNB-DU STATUS INDICATION message, that the overload situation has ceased. + +The detailed overload reduction policy is up to gNB-CU implementation. + +If the gNB-DU is an IAB-DU or an IAB-donor-DU, and if the *IAB Congestion Indication* IE is present in the GNB-DU STATUS INDICATION message and only includes the *Child Node Identifier* IE, the gNB-CU shall, if supported, consider that the backhaul link between the gNB-DU and the node identified by the *Child Node Identifier* IE is congested. If the *IAB Congestion Indication* IE is present in the GNB-DU STATUS INDICATION message and includes both the *Child Node Identifier* IE and the *BH RLC CH ID* IE, the gNB-CU shall, if supported, consider that congestion occurs on the corresponding BH RLC channel(s) over the link towards the node identified by the *Child Node Identifier* IE. + +### 8.2.7.3 Abnormal Conditions + +Void. + +## 8.2.8 F1 Removal + +### 8.2.8.1 General + +The purpose of the F1 Removal procedure is to remove the interface instance and all related resources between the gNB-DU and the gNB-CU in a controlled manner. If successful, this procedure erases any existing application level configuration data in the two nodes. + +NOTE: In case the signalling transport is shared among several F1-C interface instances, and the TNL association is still used by one or several F1-C interface instances, the initiating node should not initiate the removal of the TNL association. + +The procedure uses non-UE-associated signaling. + +### 8.2.8.2 Successful Operation + +![Sequence diagram for Figure 8.2.8-1: F1 Removal, gNB-DU initiated, successful operation. The diagram shows two lifelines: gNB-DU and gNB-CU. The gNB-DU sends an F1 REMOVAL REQUEST message to the gNB-CU. The gNB-CU responds with an F1 REMOVAL RESPONSE message. Both lifelines end with a thick horizontal bar.](1f1614411edea7edfc86c839a608e1fc_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: F1 REMOVAL REQUEST + gNB-CU-->>gNB-DU: F1 REMOVAL RESPONSE + Note right of gNB-CU: +``` + +Sequence diagram for Figure 8.2.8-1: F1 Removal, gNB-DU initiated, successful operation. The diagram shows two lifelines: gNB-DU and gNB-CU. The gNB-DU sends an F1 REMOVAL REQUEST message to the gNB-CU. The gNB-CU responds with an F1 REMOVAL RESPONSE message. Both lifelines end with a thick horizontal bar. + +Figure 8.2.8-1: F1 Removal, gNB-DU initiated, successful operation + +![Sequence diagram for Figure 8.2.8-2: F1 Removal, gNB-CU initiated, successful operation. The diagram shows two lifelines: gNB-DU and gNB-CU. The gNB-CU sends an F1 REMOVAL REQUEST message to the gNB-DU. The gNB-DU responds with an F1 REMOVAL RESPONSE message. Both lifelines end with a thick horizontal bar.](cc542843836eecb036b99cb270b54a1e_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-CU->>gNB-DU: F1 REMOVAL REQUEST + gNB-DU-->>gNB-CU: F1 REMOVAL RESPONSE + Note right of gNB-CU: +``` + +Sequence diagram for Figure 8.2.8-2: F1 Removal, gNB-CU initiated, successful operation. The diagram shows two lifelines: gNB-DU and gNB-CU. The gNB-CU sends an F1 REMOVAL REQUEST message to the gNB-DU. The gNB-DU responds with an F1 REMOVAL RESPONSE message. Both lifelines end with a thick horizontal bar. + +Figure 8.2.8-2: F1 Removal, gNB-CU initiated, successful operation + +#### Successful F1 Removal, gNB-DU initiated + +The gNB-DU initiates the procedure by sending the F1 REMOVAL REQUEST message to the gNB-CU. Upon reception of the F1 REMOVAL REQUEST message the gNB-CU shall reply with the F1 REMOVAL RESPONSE message. After receiving the F1 REMOVAL RESPONSE message, the gNB-DU may initiate removal of the TNL association towards the gNB-CU, if applicable, and may remove all resources associated with that interface instance. The gNB-CU may then remove all resources associated with that interface instance. + +#### Successful F1 Removal, gNB-CU initiated + +The gNB-CU initiates the procedure by sending the F1 REMOVAL REQUEST message to the gNB-DU. Upon reception of the F1 REMOVAL REQUEST message the gNB-DU shall reply with the F1 REMOVAL RESPONSE message. After receiving the F1 REMOVAL RESPONSE message, the gNB-CU may initiate removal of the TNL association towards the gNB-DU, if applicable, and may remove all resources associated with that interface instance. The gNB-DU may then remove all resources associated with that interface instance. + +### 8.2.8.3 Unsuccessful Operation + +![Sequence diagram for Figure 8.2.8-3: F1 Removal, gNB-DU initiated, unsuccessful operation. The diagram shows two lifelines: gNB-DU and gNB-CU. The gNB-DU sends an F1 REMOVAL REQUEST message to the gNB-CU. The gNB-CU responds with an F1 REMOVAL FAILURE message. Both lifelines end with a thick horizontal bar.](be4ddda9589307e95f8145ad3a4de7f6_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: F1 REMOVAL REQUEST + gNB-CU-->>gNB-DU: F1 REMOVAL FAILURE + Note right of gNB-CU: +``` + +Sequence diagram for Figure 8.2.8-3: F1 Removal, gNB-DU initiated, unsuccessful operation. The diagram shows two lifelines: gNB-DU and gNB-CU. The gNB-DU sends an F1 REMOVAL REQUEST message to the gNB-CU. The gNB-CU responds with an F1 REMOVAL FAILURE message. Both lifelines end with a thick horizontal bar. + +Figure 8.2.8-3: F1 Removal, gNB-DU initiated, unsuccessful operation + +![Sequence diagram for F1 Removal, gNB-CU initiated, unsuccessful operation. The diagram shows two lifelines: gNB-DU and gNB-CU. The gNB-CU sends an F1 REMOVAL REQUEST to the gNB-DU. The gNB-DU responds with an F1 REMOVAL FAILURE message.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: F1 REMOVAL REQUEST + gNB-DU-->>gNB-CU: F1 REMOVAL FAILURE + Note right of gNB-CU: + +``` + +Sequence diagram for F1 Removal, gNB-CU initiated, unsuccessful operation. The diagram shows two lifelines: gNB-DU and gNB-CU. The gNB-CU sends an F1 REMOVAL REQUEST to the gNB-DU. The gNB-DU responds with an F1 REMOVAL FAILURE message. + +**Figure 8.2.8.3-2: F1 Removal, gNB-CU initiated, unsuccessful operation** + +#### Unsuccessful F1 Removal, gNB-DU initiated + +If the gNB-CU cannot accept to remove the interface instance with the gNB-DU it shall respond with an F1 REMOVAL FAILURE message with an appropriate cause value. + +#### Unsuccessful F1 Removal, gNB-CU initiated + +If the gNB-DU cannot accept to remove the interface instance with the gNB-CU it shall respond with an F1 REMOVAL FAILURE message with an appropriate cause value. + +### 8.2.8.4 Abnormal Conditions + +Not applicable. + +## 8.2.9 Network Access Rate Reduction + +### 8.2.9.1 General + +The purpose of the Network Access Rate Reduction procedure is to indicate to the gNB-DU that the rate at which UEs are accessing the network need to be reduced from its current level. + +The procedure uses non-UE associated signalling. + +NETWORK ACCESS RATE REDUCTION + +### 8.2.9.2 Successful operation + +![Sequence diagram for Network Access Rate Reduction, Successful operation. The diagram shows two lifelines: gNB-DU and gNB-CU. The gNB-CU sends a NETWORK ACCESS RATE REDUCTION message to the gNB-DU.](a5b3b7c5ec2245f09354260ea8cfffc5_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: NETWORK ACCESS RATE REDUCTION + Note right of gNB-CU: + +``` + +Sequence diagram for Network Access Rate Reduction, Successful operation. The diagram shows two lifelines: gNB-DU and gNB-CU. The gNB-CU sends a NETWORK ACCESS RATE REDUCTION message to the gNB-DU. + +**Figure 8.2.9.2-1: Network Access Rate Reduction, Successful operation** + +The gNB-CU initiates the procedure by sending a NETWORK ACCESS RATE REDUCTION message to the gNB-DU. When receiving the NETWORK ACCESS RATE REDUCTION message the gNB-DU should take into account the information contained in the *UAC assistance information* to set the parameters for Unified Access Barring. + +If the *NID* IE is contained in the NETWORK ACCESS RATE REDUCTION message, the gNB-DU should take it into account and combine the *NID* IE with the *PLMN Identity* IE to identify the SNPN. + +### 8.2.9.3 Abnormal Conditions + +Not applicable + +## 8.2.10 Resource Status Reporting Initiation + +### 8.2.10.1 General + +This procedure is used by an gNB-CU to request the reporting of load measurements to gNB-DU. + +The procedure uses non UE-associated signalling. + +### 8.2.10.2 Successful Operation + +![Sequence diagram showing the successful operation of Resource Status Reporting Initiation. The gNB-CU sends a RESOURCE STATUS REQUEST message to the gNB-DU, and the gNB-DU responds with a RESOURCE STATUS RESPONSE message.](d78e519e9186d30807342196675fd440_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-CU: + gNB-CU->>gNB-DU: RESOURCE STATUS REQUEST + Note right of gNB-DU: + gNB-DU-->>gNB-CU: RESOURCE STATUS RESPONSE + Note left of gNB-CU: + +``` + +Sequence diagram showing the successful operation of Resource Status Reporting Initiation. The gNB-CU sends a RESOURCE STATUS REQUEST message to the gNB-DU, and the gNB-DU responds with a RESOURCE STATUS RESPONSE message. + +**Figure 8.2.10.2-1: Resource Status Reporting Initiation, successful operation** + +gNB-CU initiates the procedure by sending the RESOURCE STATUS REQUEST message to gNB-DU to start a measurement, stop a measurement, or add cells to report for a measurement. Upon receipt, gNB-DU: + +- shall initiate the requested measurement according to the parameters given in the request in case the *Registration Request* IE set to "start"; or +- shall stop all cells measurements and terminate the reporting in case the *Registration Request* IE is set to "stop"; or +- shall add cells indicated in the *Cell To Report List* IE to the measurements initiated before for the given measurement IDs, in case the *Registration Request* IE is set to "add". If measurements are already initiated for a cell indicated in the *Cell To Report List* IE, this information shall be ignored. + +If the *Registration Request* IE is set to "start" in the RESOURCE STATUS REQUEST message and the *Report Characteristics* IE indicates cell specific measurements, the *Cell To Report List* IE shall be included. + +If *Registration Request* IE is set to "add" in the RESOURCE STATUS REQUEST message, the *Cell To Report List* IE shall be included. + +If gNB-DU is capable to provide all requested resource status information, it shall initiate the measurement as requested by gNB-CU, 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-DU shall perform measurements on. For each cell, gNB-DU shall include in the RESOURCE STATUS UPDATE message: + +- the *Radio Resource Status* IE, if the first bit, "PRB Periodic" of the *Report Characteristics* IE included in the RESOURCE STATUS REQUEST message is set to 1. If the cell for which *Radio Resource Status* IE is requested to be reported supports more than one SSB, the *Radio Resource Status* IE for such cell shall include the *SSB Area Radio Resource Status Item* IE for all SSB areas supported by the cell. If the *SSB To Report List* IE is included for a cell, the *Radio Resource* IE for such cell shall only include the *SSB Area Radio Resource Status List* IE; If the cell for which *Radio Resource Status* IE is requested to be reported supports more than one slice, and if the *Slice To Report List* IE is included for a cell, the *Radio Resource Status* IE for such cell shall, if supported, include the requested *Slice Radio Resource Status Item* IE if the cell for which *Radio Resource Status* IE is requested to be reported supports MIMO the *Radio Resource Status* IE for such cell shall include the *MIMO PRB usage Information* IE; +- the *TNL Capacity Indicator* IE, if the second bit, "TNL Capacity Ind Periodic" of the *Report Characteristics* IE included in the RESOURCE STATUS REQUEST message is set to 1; +- the *Composite Available Capacity Group* IE, if the third bit, "Composite Available Capacity Periodic" of the *Report Characteristics* IE included in the RESOURCE STATUS REQUEST message is set to 1. If *Cell Capacity Class Value* IE is included within the *Composite Available Capacity Group* IE, this IE is used to assign weights to the available capacity indicated in the *Capacity Value* IE. If the cell for which *Composite Available Capacity Group* IE is requested to be reported supports more than one SSB the *Composite Available Capacity Group* IE for such cell shall include the *SSB Area Capacity Value List* IE for all SSB areas supported by the cell, providing the SSB area capacity with respect to the *Cell Capacity Class Value* IE. If the *SSB To Report List* IE is included for a cell, the *Composite Available Capacity Group* IE for such cell shall include the requested *SSB Area Capacity Value List* IE providing the SSB area capacity with respect to the *Cell Capacity Class Value*. If the cell for which *Composite Available Capacity Group* IE is requested to be reported supports more than one slice, and if the *Slice To Report List* IE is included for a cell, the *Slice Available Capacity* IE for such cell shall include the requested *Slice Available Capacity Value Downlink* IE and *Slice Available Capacity Value Uplink* IE, providing the slice capacity with respect to the *Cell Capacity Class Value*. +- the *Hardware Load Indicator* IE, if the fourth bit, " HW LoadInd Periodic " of the *Report Characteristics* IE included in the RESOURCE STATUS REQUEST message is set to 1; +- the *Number of Active UEs* IE, if the fifth bit, "Number of Active UEs Periodic" of the *Report Characteristics* IE included in the RESOURCE STATUS REQUEST message is set to 1; +- the *NR-U Channel List* IE, if the sixth bit, " NR-U Channel List Periodic" of the *Report Characteristics* IE included in the RESOURCE STATUS REQUEST message is set to "1". + +If the Reporting Periodicity IE in the RESOURCE STATUS REQUEST is present, this indicates the periodicity for the reporting of periodic measurements. The gNB-DU shall report once, unless otherwise requested within the *Reporting Periodicity* IE. + +### 8.2.10.3 Unsuccessful Operation + +![Sequence diagram showing an unsuccessful resource status reporting initiation between gNB-CU and gNB-DU.](9e26cd5584f423e1b2155fb341db579f_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-CU: + gNB-CU->>gNB-DU: RESOURCE STATUS REQUEST + Note right of gNB-DU: + gNB-DU-->>gNB-CU: RESOURCE STATUS FAILURE + +``` + +The diagram illustrates a sequence of messages between a gNB-CU (Central Unit) and a gNB-DU (Distributed Unit). The gNB-CU sends a 'RESOURCE STATUS REQUEST' message to the gNB-DU. The gNB-DU responds with a 'RESOURCE STATUS FAILURE' message, indicating an unsuccessful operation. Both units are represented by rectangular boxes with a horizontal line at the base, and the messages are shown as arrows between them. + +Sequence diagram showing an unsuccessful resource status reporting initiation between gNB-CU and gNB-DU. + +**Figure 8.2.10.3-1: Resource Status Reporting Initiation, unsuccessful operation** + +If any of the requested measurements cannot be initiated, gNB-DU shall send the RESOURCE STATUS FAILURE message with an appropriate cause value. + +#### 8.2.10.4 Abnormal Conditions + +If the initiating gNB-CU does not receive either RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message, the gNB-CU may reinitiate the Resource Status Reporting Initiation procedure towards the same gNB-DU, 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-DU shall initiate a RESOURCE STATUS FAILURE message with an appropriate cause value. + +If the gNB-DU receives a RESOURCE STATUS REQUEST message which includes the *Registration Request* IE set to "start" and the *gNB-CU Measurement ID* IE corresponding to an existing on-going load measurement reporting, for which a different Transaction ID is used, then gNB-DU shall initiate a RESOURCE STATUS FAILURE message with an appropriate cause value. + +### 8.2.11 Resource Status Reporting + +#### 8.2.11.1 General + +This procedure is initiated by gNB-DU to report the result of measurements admitted by gNB-DU following a successful Resource Status Reporting Initiation procedure. + +The procedure uses non UE-associated signalling. + +#### 8.2.11.2 Successful Operation + +![Sequence diagram showing the successful operation of Resource Status Reporting. A gNB-DU sends a RESOURCE STATUS UPDATE message to a gNB-CU.](50f72073c616cb3d3ca3af04a0c3a221_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: RESOURCE STATUS UPDATE + Note right of gNB-CU: +``` + +The diagram illustrates a sequence of messages between a gNB-DU and a gNB-CU. The gNB-DU is on the right, and the gNB-CU is on the left. A horizontal arrow labeled "RESOURCE STATUS UPDATE" points from the gNB-DU to the gNB-CU. Both entities are represented by a rectangle with a vertical line extending downwards to a thick horizontal bar at the bottom, representing their lifelines. + +Sequence diagram showing the successful operation of Resource Status Reporting. A gNB-DU sends a RESOURCE STATUS UPDATE message to a gNB-CU. + +**Figure 8.2.11.2-1: Resource Status Reporting, successful operation** + +The gNB-DU 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. + +If some results of the admitted measurements in RESOURCE STATUS UPDATE message are missing, the gNB-CU shall consider that these results were not available at the gNB-DU. + +#### 8.2.11.3 Unsuccessful Operation + +Not applicable. + +#### 8.2.11.4 Abnormal Conditions + +Void. + +## 8.2.12 DU-CU TA Information Transfer + +### 8.2.12.1 General + +The purpose of the DU-CU TA Information Transfer procedure is to enable the gNB-DU to send the TA related information to the gNB-CU. The procedure uses non-UE-associated signalling. + +### 8.2.12.2 Successful Operation + +![Sequence diagram showing the successful operation of the DU-CU TA Information Transfer procedure. The gNB-DU sends a 'DU-CU TA INFORMATION TRANSFER' message to the gNB-CU.](23cb65390082ab306c15bd3d8196135e_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: DU-CU TA INFORMATION TRANSFER + Note right of gNB-CU: +``` + +Sequence diagram showing the successful operation of the DU-CU TA Information Transfer procedure. The gNB-DU sends a 'DU-CU TA INFORMATION TRANSFER' message to the gNB-CU. + +**Figure 8.2.12.2-1: DU-CU TA Information Transfer procedure. Successful operation.** + +The gNB-DU initiates the procedure by sending a DU-CU TA Information Transfer message. + +Upon reception of the DU-CU TA Information Transfer message, the gNB-CU shall, if supported, consider that the received information is the TA information from the candidate cell(s) that is indicated by the included *Candidate Cell ID* IE. + +### 8.2.12.3 Unsuccessful Operation + +Not applicable. + +### 8.2.12.4 Abnormal Conditions + +Not applicable. + +## 8.2.13 CU-DU TA Information Transfer + +### 8.2.13.1 General + +The purpose of the CU-DU TA Information Transfer procedure is to enable the gNB-CU to send the TA related information to the gNB-DU. The procedure uses non-UE-associated signalling. + +### 8.2.13.2 Successful Operation + +![Sequence diagram for CU-DU TA Information Transfer procedure. The gNB-CU sends a CU-DU TA INFORMATION TRANSFER message to the gNB-DU.](a9159a006d67a834a7b1a771c18191cc_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-CU: + gNB-CU->>gNB-DU: CU-DU TA INFORMATION TRANSFER + Note right of gNB-DU: + activate gNB-DU + deactivate gNB-DU +``` + +Sequence diagram for CU-DU TA Information Transfer procedure. The gNB-CU sends a CU-DU TA INFORMATION TRANSFER message to the gNB-DU. + +**Figure 8.2.13.2-1: CU-DU TA Information Transfer procedure. Successful operation.** + +The gNB-CU initiates the procedure by sending a CU-DU TA Information Transfer message. + +Upon reception of the CU-DU TA Information Transfer message, the gNB-DU shall, if supported, consider that the received information is the TA information from the candidate cell(s) that is indicated by the included *Candidate Cell ID* IE. + +### 8.2.13.3 Unsuccessful Operation + +Not applicable. + +### 8.2.13.4 Abnormal Conditions + +Not applicable. + +## 8.2.14 RACH Indication + +### 8.2.14.1 General + +This procedure is initiated by the gNB-DU to inform the gNB-CU about the occurrences of successful random access procedures in the gNB-DU. + +The procedure uses non-UE-associated signalling. + +### 8.2.14.2 Successful Operation + +![Sequence diagram for RACH Indication procedure. The gNB-DU sends a RACH INDICATION message to the gNB-CU.](7c326311d265966a26e1a116f94aeb9b_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: RACH INDICATION + Note right of gNB-CU: + activate gNB-CU + deactivate gNB-CU +``` + +Sequence diagram for RACH Indication procedure. The gNB-DU sends a RACH INDICATION message to the gNB-CU. + +**Figure 8.2.14.2-1: RACH Indication procedure.** + +The gNB-DU initiates the procedure by sending the RACH INDICATION message to the gNB-CU. + +The RACH INDICATION message contains information concerning one or more successful random access procedures occurring at the gNB-DU and not known to the gNB-CU as described in TS 38.401 [4]. + +Upon reception of the RACH INDICATION message, the gNB-CU may trigger retrieval of RACH Reports from the UE. + +### 8.2.14.3 Abnormal Conditions + +Not applicable. + +## 8.3 UE Context Management procedures + +### 8.3.1 UE Context Setup + +#### 8.3.1.1 General + +The purpose of the UE Context Setup procedure is to establish the UE Context including, among others, SRB, DRB, BH RLC channel, Uu Relay RLC channel, PC5 Relay RLC channel, and SL DRB configuration. The procedure uses UE-associated signalling. + +#### 8.3.1.2 Successful Operation + +![Sequence diagram showing the UE Context Setup Request procedure: Successful Operation. The gNB-CU sends a UE CONTEXT SETUP REQUEST message to the gNB-DU, and the gNB-DU responds with a UE CONTEXT SETUP RESPONSE message.](02e16c8e8e61c2706b5c0129674884a8_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: UE CONTEXT SETUP REQUEST + gNB-DU-->>gNB-CU: UE CONTEXT SETUP RESPONSE + Note right of gNB-CU: +``` + +Sequence diagram showing the UE Context Setup Request procedure: Successful Operation. The gNB-CU sends a UE CONTEXT SETUP REQUEST message to the gNB-DU, and the gNB-DU responds with a UE CONTEXT SETUP RESPONSE message. + +**Figure 8.3.1.2-1: UE Context Setup Request procedure: Successful Operation** + +The gNB-CU initiates the procedure by sending UE CONTEXT SETUP REQUEST message to the gNB-DU. If the gNB-DU succeeds to establish the UE context, it replies to the gNB-CU with UE CONTEXT SETUP RESPONSE. If no UE-associated logical F1-connection exists, the UE-associated logical F1-connection shall be established as part of the procedure. Except for RACH based SDT and UE configured with BWP specific ServingCellMO, the gNB-CU shall perform RRC Reconfiguration or RRC connection resume to send UE to the RRC\_CONNECTED state as described in TS 38.331 [8], and in this case, the *CellGroupConfig* IE shall transparently be signaled to the UE as specified in TS 38.331 [8]. In the cases of RACH based SDT procedure and UE configured with BWP specific ServingCellMO, the *CellGroupConfig* IE shall be ignored by the gNB-CU. + +If the *UE-CapabilityRAT-ContainerList* IE is included in the UE CONTEXT SETUP REQUEST, the gNB-DU shall take this information into account for UE specific configurations. + +If the *servingCellMO* IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall configure servingCellMO for the indicated SpCell accordingly. + +If the *servingCellMO List* IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, select servingCellMO after determining the list of BWPs for the UE and include the list of servingCellMOs that have been encoded in *CellGroupConfig* IE as *ServingCellMO-encoded-in-CGC List* IE in the UE CONTEXT SETUP RESPONSE message. + +If the *Configured BWP List* IE is included in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, take it into account when requesting the gNB-DU for generating preconfigured measurement GAP for the indicated BWPs. + +If the *SpCell UL Configured* IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall configure UL for the indicated SpCell accordingly. + +If the *SCell To Be Setup List* IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall consider it as a list of candidate SCells to be set up. If the *SCell UL Configured* IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall configure UL for the indicated SCell accordingly. If the *servingCellMO* IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall configure servingCellMO for the indicated SCell accordingly. + +If the *DRX Cycle* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall use the provided value from the gNB-CU. + +If the *UL Configuration* IE in *DRB to Be Setup Item* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall take it into account for UL scheduling. + +If the *SRB To Be Setup List* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall act as specified in TS 38.401 [4]. If *Duplication Indication* IE is contained in the *SRB To Be Setup List* IE, the gNB-DU shall, if supported, setup two RLC entities for the indicated SRB. If the *Additional Duplication Indication* IE is contained in the *SRB To Be Setup List* IE, the gNB-DU shall, if supported, setup the indicated RLC entities for the indicated SRB. If the *SDT RLC Bearer Configuration* IE is contained in the *SRB To Be Setup List* IE, the gNB-DU shall, if supported, use it for packet transmission belonging to the SDT SRB indicated by the *SRB ID* IE. If the *SRB Mapping Info* IE is contained in the *SRB To Be Setup List* IE, the gNB-DU shall, if supported, store the mapping information indicated in the *SRB Mapping Info* IE for the SRB identified by the *SRB ID* IE and the Uu Relay RLC channel identified by the *SRB Mapping Info* IE. The gNB-DU shall use the mapping information stored for the mapping of SRB data to Uu Relay RLC channel. + +If the *DRB To Be Setup List* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall act as specified in TS 38.401 [4]. If the *QoS Flow Mapping Indication* IE is included in the *DRB To Be Setup List* IE for a QoS flow, the gNB-DU may take it into account that only the uplink or downlink QoS flow is mapped to the indicated DRB. If the *SDT RLC Bearer Configuration* IE is contained in the *DRB To Be Setup List* IE, the gNB-DU shall, if supported, use it for packet transmission belonging to the SDT DRB indicated by the *DRB ID* IE. If the *DRB Mapping Info* IE is contained in the *DRB To Be Setup List* IE, the gNB-DU shall, if supported, store the mapping information indicated in the *DRB Mapping Info* IE for the DRB identified by the *DRB ID* IE and the Uu Relay RLC channel identified by the *DRB Mapping Info* IE. The gNB-DU shall use the mapping information stored for the mapping of DRB data to Uu Relay RLC channel. + +For each GBR DRB, if the *Alternative QoS Parameters Sets* IE is included in the *GBR QoS Flow Information* IE in the UE CONTEXT SETUP REQUEST message, gNB-DU shall, if supported, behave the same as the NG-RAN node in the PDU Session Resource Setup procedure, specified in TS 38.413 [3]. + +If the *BH Information* IE is included in the *UL UP TNL Information to be setup List* IE or the *Additional PDCP Duplication TNL List* IE for a DRB, the gNB-DU shall, if supported, use the indicated BAP Routing ID and BH RLC channel for transmission of the corresponding GTP-U packets to the IAB-donor, as specified in TS 38.340 [30]. + +If the *BH RLC Channel To Be Setup List* IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall act as specified in TS 38.401 [4]. If the *Traffic Mapping Information* IE is included in the *BH RLC Channel To Be Setup Item IEs* IE for a BH RLC Channel, the gNB-DU shall, if supported, process the *Traffic Mapping Information* IE as follows: + +- if the *IP to layer2 Traffic Mapping Info* IE is included, the gNB-DU shall store the mapping information contained in the *IP to layer2 Traffic Mapping Info To Add* IE, if present, for the egress BH RLC channel identified by the *BH RLC CH ID* IE, and shall remove the previously stored mapping information as indicated by + +the *IP to layer2 Mapping Traffic Info To Remove IE*, if present. The gNB-DU shall use the mapping information stored for the mapping of IP traffic to layer 2, as specified in TS 38.340 [30]. + +- if the *BAP layer BH RLC channel Mapping Info IE* is included, the gNB-DU shall store the mapping information contained in the *BAP layer BH RLC channel Mapping Info To Add IE*, if present, for the egress or ingress BH RLC channel identified by the *BH RLC CH ID IE*, and shall remove the previously stored mapping information as indicated by the *BAP layer BH RLC channel Mapping Info To Remove IE*, if present. The gNB-DU shall use the mapping information stored when forwarding traffic on BAP sublayer, as specified in TS 38.340 [30]. + +If two *UL UP TNL Information IEs* are included in UE CONTEXT SETUP REQUEST message for a DRB, gNB-DU shall include two *DL UP TNL Information IEs* in UE CONTEXT SETUP RESPONSE message and setup two RLC entities for the indicated DRB. gNB-CU and gNB-DU use the *UL UP TNL Information IEs* and *DL UP TNL Information IEs* to support packet duplication for intra-gNB-DU CA as defined in TS 38.470 [2]. The first *UP TNL Information IE* of the two *UP TNL Information IEs* is for the primary path. + +If one or two *Additional PDCP Duplication UP TNL Information IEs* are included in the UE CONTEXT SETUP REQUEST message for a DRB, the gNB-DU shall, if supported, include one or two *Additional PDCP Duplication UP TNL Information IEs* in the UE CONTEXT SETUP RESPONSE message and setup one or two additional RLC entities for the indicated DRB. The gNB-CU and the gNB-DU use the *Additional PDCP Duplication UP TNL Information IEs* to support packet duplication for intra-gNB-DU CA as defined in TS 38.470 [2]. + +If *Duplication Activation IE* is included in the UE CONTEXT SETUP REQUEST message for a DRB, gNB-DU should take it into account when activating/deactivating CA based PDCP duplication for the DRB. If the *RLC Duplication State List IE* is included in the *RLC Duplication Information IE* contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take it into account when activating/deactivating CA based PDCP duplication for the DRB with more than two RLC entities. + +If *DC Based Duplication Configured IE* is included in the UE CONTEXT SETUP REQUEST message for a DRB, gNB-DU shall regard that DC based PDCP duplication is configured for this DRB if the value is set to be "true" and it should take the responsibility of PDCP duplication activation/deactivation. If *DC Based Duplication Activation IE* is included in the UE CONTEXT SETUP REQUEST message for a DRB, gNB-DU should take it into account when activating/deactivating DC based PDCP duplication for this DRB. If the *RLC Duplication State List IE* is included in the *RLC Duplication Information IE* contained in the UE CONTEXT SETUP REQUEST message for a DRB, the gNB-DU shall, if supported, take it into account when activating/deactivating DC based PDCP duplication for the DRB with more than two RLC entities. If the *Primary Path Indication IE* is included in the *RLC Duplication Information IE*, the gNB-DU shall, if supported, take it into account when performing DC based PDCP duplication for the DRB with more than two RLC entities. + +If *UL PDCP SN length IE* is included in the UE CONTEXT SETUP REQUEST message for a DRB, gNB-DU shall, if supported, store this information and use it for lower layer configuration. + +For EN-DC operation, and if the *Subscriber Profile ID for RAT/Frequency priority IE* is received from an MeNB, the UE CONTEXT SETUP REQUEST message shall contain the *Subscriber Profile ID for RAT/Frequency priority IE*. If the *Additional RRM Policy Index IE* is received from an MeNB, the UE CONTEXT SETUP REQUEST message shall, if supported, contain the *Additional RRM Policy Index IE*. The gNB-DU shall store the received Subscriber Profile ID for RAT/Frequency priority in the UE context and use it as defined in TS 36.300 [20]. The gNB-DU shall, if supported, store the received Additional RRM Policy Index in the UE context and use it as defined in TS 36.300 [20]. + +If the *Index to RAT/Frequency Selection Priority IE* is available at the gNB-CU, the *Index to RAT/Frequency Selection Priority IE* shall be included in the UE CONTEXT SETUP REQUEST. The gNB-DU may use it for RRM purposes. + +The gNB-DU shall report to the gNB-CU, in the UE CONTEXT SETUP RESPONSE message, the result for all the requested DRBs, SRBs, BH RLC channels, Uu RLC channels, PC5 Relay RLC channels, and SL DRBs in the following way: + +- 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 to Setup List* IE; +- A list of SRBs which failed to be established shall be included in the *SRB Failed to Setup List* IE. +- A list of successfully established SRBs with logical channel identities for primary path shall be included in the *SRB Setup List* IE only if CA based PDCP duplication is initiated for the concerned SRBs. +- A list of BH RLC channels which are successfully established shall be included in the *BH RLC Channel Setup List* IE; +- A list of BH RLC channels which failed to be established shall be included in the *BH RLC Channel Failed to be Setup List* IE; +- A list of SL DRBs which are successfully established shall be included in the *SL DRB Setup List* IE; +- A list of SL DRBs which failed to be established shall be included in the *SL DRB Failed to Setup List* IE. +- A list of Uu Relay RLC channels which are successfully established shall be included in the *Uu RLC Channel Setup List* IE; +- A list of Uu Relay RLC channels which failed to be established shall be included in the *Uu RLC Channel Failed to be Setup List* IE; +- A list of PC5 Relay RLC channels which are successfully established shall be included in the *PC5 RLC Channel Setup List* IE; +- A list of PC5 Relay RLC channels which failed to be established shall be included in the *PC5 RLC Channel Failed to be Setup List* IE; + +If *Duplication Indication* IE in *SL DRB To Be Setup List* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, generate two PC5 RLC configurations for the indicated SL DRB. + +When the gNB-DU reports the unsuccessful establishment of a DRB or SRB or SL DRB or a BH RLC channel or a Uu RLC channel or a PC5 Relay RLC channel, the cause value should be precise enough to enable the gNB-CU to know the reason for the unsuccessful establishment. + +For EN-DC operation, the gNB-CU shall include in the UE CONTEXT SETUP REQUEST the *E-UTRAN QoS* IE. The allocation of resources according to the values of the *Allocation and Retention Priority* IE included in the *E-UTRAN QoS* IE shall follow the principles described for the E-RAB Setup procedure in TS 36.413 [15]. + +For NG-RAN operation, the gNB-CU shall include in the UE CONTEXT SETUP REQUEST the *DRB Information* IE. + +For DC operation, the *CG-ConfigInfo* IE shall be included in the *CU to DU RRC Information* IE at the gNB acting as secondary node. If the *CG-ConfigInfo* IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall regard it as a reconfiguration with sync as defined in TS 38.331 [8]. + +For sidelink operation, the *CG-ConfigInfo* IE shall be included in the *CU to DU RRC Information* IE if the gNB-CU receives sidelink related UE information from UE. If the *CG-ConfigInfo* IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall regard it as an indication of V2X sidelink information as defined in TS 38.331 [8]. + +If the *HandoverPreparationInformation* IE is included in the *CU to DU RRC Information* IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU of the gNB acting as master node shall regard it as a reconfiguration with sync as defined in TS 38.331 [8]. The gNB-CU shall only initiate the UE Context Setup procedure for handover or secondary node addition when at least one DRB is setup for the UE, or at least one BH RLC channel is set up for IAB-MT. If the *HandoverPreparationInformation* IE containing the sidelink related UE information is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall regard it as an indication of V2X sidelink information as defined in TS 38.331 [8]. + +If the received *CU to DU RRC Information* IE does not include source cell group configuration, the gNB-DU shall generate the cell group configuration using full configuration. Otherwise, delta configuration is allowed. + +If the gNB-CU includes the SMTC information of the measured frequency(ies) in the *MeasurementTimingConfiguration* IE of the *CU to DU RRC Information* IE that is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall generate the measurement gaps based on the received SMTC information. Then the gNB-DU shall send the measurement gaps information to the gNB-CU in the *MeasGapConfig* IE of the *DU to CU RRC Information* IE that is included in the UE CONTEXT SETUP RESPONSE message. + +If the *MeasConfig* IE is included in the *CU to DU RRC Information* IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall deduce that changes to the measurements configuration need to be applied. If the *measObjectToAddModList* IE is included in the *MeasConfig* IE, then the frequencies added in such IE are to be activated. Then the gNB-DU shall decide if measurement gaps are needed or not and, if needed, the gNB-DU shall send the measurement gaps information to the gNB-CU in the *MeasGapConfig* IE of the *DU to CU RRC Information* IE that is included in the UE CONTEXT SETUP RESPONSE message. If the *measObjectToRemoveList* IE is included in the *MeasConfig* IE, the gNB-DU shall ignore it. + +If the *NeedForGapsInfoNR* IE is included in the *CU to DU RRC Information* IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it as described in TS 38.331 [8]. If the *NeedForGapNCSG-InfoNR* IE is included in the *CU to DU RRC Information* IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it as described in TS 38.331 [8]. If the *NeedForGapNCSG-InfoEUTRA* IE is included in the *CU to DU RRC Information* IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it as described in TS 38.331 [8]. If the *NeedForInterruptionInfoNR* IE is included in the *CU to DU RRC Information* IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it as described in TS 38.331 [8]. + +For EN-DC operation, if the gNB-CU includes the *Resource Coordination Transfer Information* IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it for the purpose of resource coordination. If the *Ignore PRACH Configuration* IE is present and set to "true" the *E-UTRA PRACH Configuration* IE in the UE CONTEXT SETUP REQUEST message shall be ignored. If the gNB-CU received the MeNB Resource Coordination Information as defined in TS 36.423 [9], it shall transparently transfer it to the gNB-DU via the *Resource Coordination Transfer Container* IE in the UE CONTEXT SETUP REQUEST message. The gNB-DU shall use the information received in the *Resource Coordination Transfer Container* IE for reception of MeNB Resource Coordination Information at the gNB acting as secondary node as described in TS 36.423 [9]. If the *Resource Coordination E-UTRA Cell Information* IE is included in the *Resource Coordination Transfer Information* IE, the gNB-DU shall store the information replacing previously received information for the same E-UTRA cell, and use the stored information for the purpose of resource coordination. + +For NGEN-DC or NE-DC operation, if the gNB-CU includes the *Resource Coordination Transfer Information* IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it for the purpose of resource coordination. If the gNB-CU received the MR-DC Resource Coordination Information as defined in TS 38.423 [28], it shall transparently transfer it to the gNB-DU via the *Resource Coordination Transfer Container* IE in the UE CONTEXT SETUP REQUEST message. The gNB-DU shall use the information received in the *Resource Coordination Transfer Container* IE for reception of MR-DC Resource Coordination Information at the gNB as described in TS 38.423 [28]. + +The *UEAssistanceInformation* IE shall be included in *CU to DU RRC Information* IE in the UE CONTEXT SETUP REQUEST message if the gNB-CU received this IE from the UE; if the *UEAssistanceInformation* IE is included in the *CU to DU RRC Information* IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take it into account when configuring resources for the UE. + +The *UEAssistanceInformationEUTRA* IE shall be included in *CU to DU RRC Information* IE in the UE CONTEXT SETUP REQUEST message if the gNB-CU received this IE from the UE; if the *UEAssistanceInformationEUTRA* IE is included in the *CU to DU RRC Information* IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take it into account when configuring LTE sidelink resources for the UE. + +If the *Resource Coordination Transfer Container* IE is included in the UE CONTEXT SETUP RESPONSE, the gNB-CU shall transparently transfer this information for the purpose of resource coordination as described in TS 36.423 [9], TS 38.423 [28]. + +If the *Masked IMEISV* IE is contained in the UE CONTEXT SETUP REQUEST message the gNB-DU shall, if supported, use it to determine the characteristics of the UE for subsequent handling. + +If the *SCell Failed To Setup List* IE is contained in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall regard the corresponding SCell(s) failed to be set up with an appropriate cause value for each SCell failed to setup. + +If the *Inactivity Monitoring Request* IE is contained in the UE CONTEXT SETUP REQUEST message, gNB-DU may consider that the gNB-CU has requested the gNB-DU to perform UE inactivity monitoring. If the *Inactivity Monitoring Response* IE is contained in the UE CONTEXT SETUP RESPONSE message and set to "Not-supported", the gNB-CU shall consider that the gNB-DU does not support UE inactivity monitoring for the UE. + +If the *ServCellInfoList* IE is included in the *DU to CU RRC Information* IE contained in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall take it into account to generate the content of inter-node RRC message, i.e., *CG-Config* or *CG-ConfigInfo*, as described in TS 38.331 [8]. + +If the *Full Configuration* IE is contained in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall consider that the gNB-DU has generated the *CellGroupConfig* IE using full configuration. + +If the *C-RNTI* IE is included in the UE CONTEXT SETUP RESPONSE, the gNB-CU shall consider that the C-RNTI has been allocated by the gNB-DU for this UE context. + +The UE Context Setup Procedure is not used to configure SRB0. + +If the UE CONTEXT SETUP REQUEST message contains the *RRC-Container* IE, the gNB-DU shall send the corresponding RRC message to the UE via SRB1. + +If the *Notification Control* IE is included in the *DRB to Be Setup List* IE contained in the UE CONTEXT SETUP REQUEST message and it is set to active, the gNB-DU shall, if supported, monitor the QoS of the DRB and notify the gNB-CU if the QoS cannot be fulfilled any longer or if the QoS can be fulfilled again. The *Notification Control* IE can only be applied to GBR bearers. + +If the *UL PDU Session Aggregate Maximum Bit Rate* IE is included in the *QoS Flow Level QoS Parameters* IE contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall store the received UL PDU Session Aggregate Maximum Bit Rate and use it when enforcing uplink traffic policing for non-GBR Bearers for the concerned UE as specified in TS 23.501 [21]. + +The gNB-DU shall store the received gNB-DU UE Aggregate Maximum Bit Rate Uplink and use it for non-GBR Bearers for the concerned UE. + +If the UE CONTEXT SETUP REQUEST message contains the *QoS Flow Mapping Indication* IE, the gNB-DU may take it into account that only the uplink or downlink QoS flow is mapped to the DRB. + +If the UE CONTEXT SETUP REQUEST message contains the *New gNB-CU UE FIAP ID* IE, the gNB-DU shall, if supported, replace the value received in the *gNB-CU UE FIAP ID* IE by the value of the *New gNB-CU UE FIAP ID* and use it for further signalling. + +If the *RAN UE ID* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall store and replace any previous information received. + +If the *Trace Activation* IE is included in the UE CONTEXT SETUP REQUEST message the gNB-DU shall, if supported, initiate the requested trace function as described in TS 32.422 [29]. + +In particular, the gNB-DU shall, if supported: + +- if the *Trace Activation* IE includes the *MDT Activation* IE set to "Immediate MDT and Trace", initiate the requested trace session and MDT session as described in TS 32.422 [29]; +- if the *Trace Activation* IE includes the *MDT Activation* IE set to "Immediate MDT Only", initiate the requested MDT session as described in TS 32.422 [29] and the gNB-DU shall ignore *Interfaces To Trace* IE, and *Trace Depth* IE. If the *Management Based MDT PLMN List* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, store the received information in the UE context, and use this information to allow subsequent selection of the UE for management based MDT defined in TS 32.422 [29]. + +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 UE CONTEXT SETUP REQUEST message, the gNB-DU shall store this information, and, if supported, perform delay measurement and QoS monitoring, as specified in TS 23.501 [21]. + +If the UE CONTEXT SETUP REQUEST message contains the *Configured BAP Address* IE, the gNB-DU shall, if supported, store this BAP address configured for the corresponding child IAB-node and use it as specified in TS 38.340 [30]. + +If the *BAP Control PDU Channel* IE is included in the *BH RLC Channel to be Setup List* IE, the gNB-DU shall, if supported, consider that the configured BH RLC channel can be used to transmit BAP Control PDUs, and use this BH RLC channel as specified in TS 38.340 [30]. + +If the *FI-C Transfer Path* IE is included in UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take it into account. + +If the *NR V2X Services Authorized* IE is contained in the UE CONTEXT SETUP REQUEST message and it contains one or more IEs set to "authorized", the gNB-DU node shall, if supported, consider that the UE is authorized for the relevant service(s). + +If the *LTE V2X Services Authorized* IE is contained in the UE CONTEXT SETUP REQUEST message and it contains one or more IEs set to "authorized", the gNB-DU node shall, if supported, consider that the UE is authorized for the relevant service(s). + +If the *NR UE Sidelink Aggregate Maximum Bit Rate* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it for the concerned UE's sidelink communication in network scheduled mode for NR V2X services. + +If the *LTE UE Sidelink Aggregate Maximum Bit Rate* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it for the concerned UE's sidelink communication in network scheduled mode for LTE V2X services. + +If the *PC5 Link Aggregate Bit Rate* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it for the concerned UE's sidelink communication in network scheduled mode for NR V2X services as defined in TS 23.287 [40]. + +If the *NR A2X Services Authorized* IE is contained in the UE CONTEXT SETUP REQUEST message and it contains one or more IEs set to "authorized", the gNB-DU node shall, if supported, consider that the UE is authorized for the relevant service(s). + +If the *LTE A2X Services Authorized* IE is contained in the UE CONTEXT SETUP REQUEST message and it contains one or more IEs set to "authorized", the gNB-DU node shall, if supported, consider that the UE is authorized for the relevant service(s). + +If the *NR UE Sidelink Aggregate Maximum Bit Rate for A2X* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it for the concerned UE's sidelink communication in network scheduled mode for NR A2X services. + +If the *LTE UE Sidelink Aggregate Maximum Bit Rate for A2X* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it for the concerned UE's sidelink communication in network scheduled mode for LTE A2X services. + +If the *TSC Traffic Characteristics* IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take into account the corresponding information received in the *TSC Traffic Characteristics* IE. If the *RAN Feedback Type* IE is included in the *TSC Assistance Information Uplink* IE of the *TSC Traffic Characteristics* IE, the gNB-DU shall, if supported, take this information into account when determining the feedback to provide in the *TSC Traffic Characteristics Feedback* IE in the UE CONTEXT SETUP RESPONSE message. + +If the *Conditional Inter-DU Mobility Information* IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall consider that the request concerns a conditional handover or conditional PSCell addition or conditional PSCell change or subsequent CPAC for the included *SpCell ID* IE and shall include it as the *Requested Target Cell ID* IE in the UE CONTEXT SETUP RESPONSE message. The gNB-DU shall regard it as a reconfiguration with sync as defined in TS 38.331 [8]. + +If the *Target gNB-DU UE FIAP ID* IE is contained in the *Conditional Inter-DU Mobility Information* IE included in the UE CONTEXT SETUP REQUEST message, then the gNB-DU shall replace the existing prepared conditional handover or conditional PSCell addition or conditional PSCell change or subsequent CPAC identified by the *Target gNB-DU UE FIAP ID* IE and the *SpCell ID* IE. + +If the *Serving NID* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall combine the *Serving NID* IE with the *Serving PLMN* IE to identify the serving NPN, and may take it into account for UE context establishment. + +If the *Estimated Arrival Probability* IE is contained in the *Conditional Inter-DU Mobility Information* IE included in the UE CONTEXT SETUP REQUEST message, then the gNB-DU may use the information to allocate necessary resources for the UE. + +If for a given E-RAB for EN-DC operation the *ENB DL Transport Layer Address* IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed. + +If for a given Qos flow for NG-RAN operation the *PDCP Terminating Node DL Transport Layer Address* IE is included in the UE CONTEXT SETUP REQUEST message, then the gNB-DU shall, if supported, use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed. + +If the *FI-C Transfer Path NRDC* IE is included in UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take it into account. + +If the *MDT Polluted Measurement Indicator* IE is included in the UE CONTEXT SETUP REQUEST, the gNB-DU shall take this information into account as specified in TS 38.401 [4]. + +If the *SCG Activation Request* IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU may use it to configure SCG resources as specified in TS 37.340 [7], and if supported, shall include the *SCG Activation Status* IE in the UE CONTEXT SETUP RESPONSE message. If the *SCG Activation Request* IE in the UE CONTEXT SETUP REQUEST message is set to "Activate SCG", the gNB-DU shall activate the SCG resources and set the *SCG Activation Status* IE in the UE CONTEXT SETUP RESPONSE message to "SCG Activated". + +If the *Old CG-SDT Session Info* IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, retrieve the old CG-SDT resource configuration and old UE context based on the indicated gNB-CU FIAP UE ID and gNB-DU FIAP UE ID. + +If the *5G ProSe Authorized* IE is contained in the UE CONTEXT SETUP REQUEST message and it contains one or more IEs set to "authorized", the gNB-DU node shall, if supported, consider that the UE is authorized for the relevant service(s). + +If the *5G ProSe UE PC5 Aggregate Maximum Bit Rate* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it for the concerned UE's sidelink communication in network scheduled mode for 5G ProSe services. + +If the *5G ProSe PC5 Link Aggregate Bit Rate* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it for the concerned UE's sidelink communication in network scheduled mode for 5G ProSe services as defined in TS 23.304 [44]. + +If the *Uu RLC Channel To Be Setup List* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, act as specified in TS 38.401 [4]. gNB-DU generates the Uu Relay RLC channel configurations for a L2 U2N Relay UE or a L2 MP Relay UE using N3C. + +If the *PC5 RLC Channel To Be Setup List* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, act as specified in TS 38.401 [4]. gNB-DU generates the PC5 Relay RLC channel configurations for a L2 U2N Remote UE. + +If the *Path Switch Configuration* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it to configure the path switch from direct path to indirect path as specified in TS 38.401 [4]. + +If the *MUSIM-GapConfig* IE is contained in the *CU to DU RRC Information* IE included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, decide to use this IE for MUSIM gap configuration or select another one based on the received *UEAssistanceInformation* IE. If gNB-DU selects a different MUSIM gap configuration from received *UEAssistanceInformation* IE, then it shall include the selected MUSIM gap information to the gNB-CU in the *MUSIM-GapConfig* IE of the *DU to CU RRC Information* IE that is included in the UE CONTEXT SETUP RESPONSE message. + +If *MUSIM-GapConfig* IE is not contained in the *CU to DU RRC Information* IE, then gNB-DU shall, if supported, send the selected MUSIM gap configuration based on the received *UEAssistanceInformation* IE, to the gNB-CU in the *MUSIM-GapConfig* IE of the *DU to CU RRC Information* IE that is included in the UE CONTEXT SETUP RESPONSE message. When MUSIM-GapConfig IE is received, the gNB-CU should use this value. + +If the *gNB-DU UE Slice Maximum Bit Rate List* IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, store and use the information for the uplink traffic policing for each concerned slice as specified in TS 23.501 [21]. + +If the *Multicast MBS Session Setup List* IE is contained in the UE CONTEXT SETUP REQUEST message the gNB-DU shall, if supported, store and use the information for configuring MBS Session Resources, if applicable. + +If the *UE Multicast MRB To Be Setup List* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take it into account for configuring MBS Session Resources, if applicable. And if the *MBS PTP Retransmission Tunnel Required* IE is included in the *UE Multicast MRB to Be Setup Item IEs* IE, the gNB-DU shall, if supported trigger the establishment of the MBS PTP Retransmission F1-U tunnel. If the *MBS PTP Forwarding Tunnel Required Information* IE is included in the *UE Multicast MRB to Be Setup Item IEs* IE, the gNB-DU shall, if supported trigger the establishment of the MBS PTP Forwarding F1-U tunnel. If the *Source MRB ID* IE is included in the *UE Multicast MRB to Be Setup Item IEs* IE, the DU shall, if supported, use it to identify the MRB configuration as provided to the UE in the source cell and take it into account for configuring MBS Session Resources. + +If the *Dedicated SI Delivery Indication* IE is included in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, take it into account for the system information delivery to the UE as described in TS 38.331 [8]. + +If the *PDU Set QoS Parameters* IE is included in the *QoS Flow Level QoS Parameters* IE contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, store this information and use it as specified in TS 23.501 [21]. + +If the *InterFrequencyConfig-NoGap* IE is included in the *DU to CU RRC Information* IE contained in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, use it as described in TS 38.331 [8]. + +If the *ul-GapFR2-Config* IE is contained in the *DU to CU RRC Information* IE that is included in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, use it as described in TS 38.331 [8]. + +If the *TwoPHRModeMCG* IE or the *TwoPHRModeSCG* IE is contained in the *DU to CU RRC Information* IE that is included in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, use this value as described in TS 38.331 [8]. + +If the *MBSInterestIndication* IE is included in the *CU to DU RRC Information* IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take it into account when configuring resources for the UE. + +If the *ncd-SSB-RedCapInitialBWP-SDT* IE is contained in the *DU to CU RRC Information* IE that is included in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, use it as described in TS 38.331 [8]. + +If the *Network Controlled Repeater Authorized* IE is contained in the UE CONTEXT SETUP REQUEST message and it is set to "authorized", the gNB-DU node shall, if supported, consider that the UE is authorized as Network Controlled Repeater. + +If the *musim-CapabilityRestrictionIndication* IE is included in the *CU to DU RRC Information* IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it as described in TS 38.331 [8]. + +If the *LTM Indicator* IE set to "true" is contained in the *LTM Information Setup* IE included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, consider that the request concerns LTM for the included *SpCell ID* IE and shall include it as the *Requested Target Cell ID* IE in the UE CONTEXT SETUP RESPONSE message. If the gNB-DU accepts the request for LTM for that *SpCell*, the gNB-DU shall generate and include the *CellGroupConfig* IE for the accepted LTM candidate cell in the UE CONTEXT SETUP RESPONSE message. + +If the *Request for Lower Layer Configuration* IE set to "true" is contained within the *Reference Configuration* IE in the *LTM Information Setup* IE included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, provide the lower layer configuration in the *CellGroupConfig* IE in the UE CONTEXT SETUP RESPONSE message for the gNB-CU to generate the LTM reference configuration. + +If the *LTM Reference Configuration* IE is contained within the *Reference Configuration* IE in the *LTM Information Setup* IE included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take it into account for generating the LTM lower layer configuration. + +If the *CSI Resource Configuration* is contained in the *LTM Information Setup* IE included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it to generate the LTM CSI reporting configuration(s) in the *CellGroupConfig* for the requested LTM candidate cell. + +If the *LTM Configuration ID Mapping List* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, consider this as the mapping information for the LTM candidate cell(s). + +If the *Request for RACH Configuration* IE set to "true" is contained in the *Early Sync Information Request* IE included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, include the *RACH Configuration* IE for early TA acquisition (early UL synchronisation), in the UE CONTEXT SETUP RESPONSE message. If the *Source gNB-DU ID* is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use this information to identify the source gNB-DU. + +If the *Early Sync Information* IE included in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, consider it as the generated early sync information from the accepted candidate cell in the candidate gNB-DU. + +If the *LTM Complete Configuration Indicator* IE set to "complete" is contained in the *LTM Configuration* IE included in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, consider that the LTM candidate configuration is a complete configuration. + +If the *Indirect Path Addition* IE is contained in the *Path Addition Information* IE which is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, consider that the request concerns the + +indirect path addition for the MP Remote UE using PC5 link and use it as specified in TS 38.401 [4]. If the *N3C Indirect Path Addition* IE is contained in the *Path Addition Information* IE, the gNB-DU shall, if supported, consider that the request concerns the indirect path addition for the MP Remote UE using N3C and use it as specified in TS 38.401 [4]. + +#### Interaction with UE Inactivity Notification procedure + +If the *SDT Volume Threshold* IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use the information during an SDT transaction to inform the gNB-CU via the UE INACTIVITY NOTIFICATION message as specified in TS 38.401 [4]. + +### 8.3.1.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the UE Context Setup Request procedure. The gNB-CU sends a UE CONTEXT SETUP REQUEST message to the gNB-DU. The gNB-DU responds with a UE CONTEXT SETUP FAILURE message.](53001b5ae3f65139f78db410bb41ae30_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: UE CONTEXT SETUP REQUEST + gNB-DU-->>gNB-CU: UE CONTEXT SETUP FAILURE + Note right of gNB-CU: + +``` + +Sequence diagram showing the Unsuccessful Operation of the UE Context Setup Request procedure. The gNB-CU sends a UE CONTEXT SETUP REQUEST message to the gNB-DU. The gNB-DU responds with a UE CONTEXT SETUP FAILURE message. + +**Figure 8.3.1.3-1: UE Context Setup Request procedure: unsuccessful Operation** + +If the gNB-DU is not able to establish an F1 UE context, or cannot even establish one bearer it shall consider the procedure as failed and reply with the UE CONTEXT SETUP FAILURE message. If the *Conditional Inter-DU Mobility Information* IE or the *LTM Indicator* IE was included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall include the received *SpCell ID* IE as the *Requested Target Cell ID* IE in the UE CONTEXT SETUP FAILURE message. + +If the gNB-DU is not able to accept the *SpCell ID* IE in UE CONTEXT SETUP REQUEST message, it shall reply with the UE CONTEXT SETUP FAILURE message with an appropriate cause value. Further, if the *Candidate SpCell List* IE is included in the UE CONTEXT SETUP REQUEST message and the gNB-DU is not able to accept the *SpCell ID* IE, the gNB-DU shall, if supported, include the *Potential SpCell List* IE in the UE CONTEXT SETUP FAILURE message and the gNB-CU should take this into account for selection of an opportune SpCell. The gNB-DU shall include the cells in the *Potential SpCell List* IE in a priority order, where the first cell in the list is the one most desired and the last one is the one least desired (e.g., based on load conditions). If the *Potential SpCell List* IE is present but no *Potential SpCell Item* IE is present, the gNB-CU should assume that none of the cells in the *Candidate SpCell List* IE are acceptable for the gNB-DU. + +### 8.3.1.4 Abnormal Conditions + +If the gNB-DU receives a UE CONTEXT SETUP REQUEST message containing a *E-UTRAN QoS* IE for a GBR QoS DRB but where the *GBR QoS Information* IE is not present, the gNB-DU shall report the establishment of the corresponding DRB as failed in the *DRB Failed to Setup List* IE of the UE CONTEXT SETUP RESPONSE message with an appropriate cause value. If the gNB-DU receives a UE CONTEXT SETUP REQUEST message containing a *DRB QoS* IE for a GBR QoS DRB but where the *GBR QoS Flow Information* IE is not present, the gNB-DU shall report the establishment of the corresponding DRBs as failed in the *DRB Failed to Setup List* IE of the UE CONTEXT SETUP RESPONSE message with an appropriate cause value. + +If the *Delay Critical* IE is included in the *Dynamic 5QI Descriptor* IE within the *DRB QoS* IE in the UE CONTEXT SETUP REQUEST message and is set to the value "delay critical" but the *Maximum Data Burst Volume* IE is not present, the gNB-DU shall report the establishment of the corresponding DRB as failed in the *DRB Failed to Setup List* IE of the of the UE CONTEXT SETUP RESPONSE message with an appropriate cause value. + +In case of "CHO-replace" when the *Target gNB-DU UE FIAP ID* IE is included, if the candidate cell in the *SpCell ID* IE included in the UE CONTEXT SETUP REQUEST message was not prepared using the same UE-associated signaling connection, the gNB-DU shall ignore this candidate cell. + +## 8.3.2 UE Context Release Request (gNB-DU initiated) + +### 8.3.2.1 General + +The purpose of the UE Context Release Request procedure is to enable the gNB-DU to request the gNB-CU to release the UE-associated logical F1-connection or candidate cells in conditional handover or conditional PSCell addition or conditional PSCell change or LTM or subsequent CPAC. The procedure uses UE-associated signalling. + +### 8.3.2.2 Successful Operation + +![Sequence diagram showing the successful operation of the UE Context Release procedure. A gNB-DU sends a UE CONTEXT RELEASE REQUEST message to a gNB-CU.](6334c962f5e106e3331e59946e4d166e_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: UE CONTEXT RELEASE REQUEST + Note right of gNB-CU: + activate gNB-CU + deactivate gNB-CU +``` + +Sequence diagram showing the successful operation of the UE Context Release procedure. A gNB-DU sends a UE CONTEXT RELEASE REQUEST message to a gNB-CU. + +**Figure 8.3.2.2-1: UE Context Release (gNB-DU initiated) procedure. Successful operation** + +The gNB-DU controlling a UE-associated logical F1-connection initiates the procedure by generating a UE CONTEXT RELEASE REQUEST message towards the affected gNB-CU node. + +The UE CONTEXT RELEASE REQUEST message shall indicate the appropriate cause value. + +If the *Candidate Cells To Be Cancelled List* IE is included in the UE CONTEXT RELEASE REQUEST message, the gNB-CU shall consider that the only the resources reserved for the candidate cells identified by the included NR CGIs and associated to the UE-associated signaling identified by the *gNB-CU UE FIAP ID* IE and the *gNB-DU UE FIAP ID* IE are about to be released by the gNB-DU. + +If the *LTM Cells To Be Released List* IE is included in the UE CONTEXT RELEASE REQUEST message, the gNB-CU shall, if supported, consider that only the resources reserved for the LTM cells identified by the included NR CGIs and associated to the UE-associated signaling identified by the *gNB-CU UE FIAP ID* IE and the *gNB-DU UE FIAP ID* IE are about to be released by the gNB-DU. + +#### **Interactions with UE Context Release procedure:** + +The UE Context Release procedure may be initiated upon reception of a UE CONTEXT RELEASE REQUEST message. + +#### **Interactions with UE Context Setup procedure:** + +The UE Context Release Request procedure may be performed before the UE Context Setup procedure to request the release of an existing UE-associated logical F1-connection and related resources in the gNB-DU. + +### 8.3.2.3 Abnormal Conditions + +If one or more candidate cells in the *Candidate Cells To Be Cancelled List* IE included in the UE CONTEXT RELEASE REQUEST message were not prepared using the same UE-associated signaling connection, the gNB-CU shall ignore those non-associated candidate cells. + +If one or more LTM cells in the *LTM Cells To Be Released List* IE included in the UE CONTEXT RELEASE REQUEST message were not prepared using the same UE-associated signaling connection, the gNB-CU shall ignore those non-associated LTM cells. + +## 8.3.3 UE Context Release (gNB-CU initiated) + +### 8.3.3.1 General + +The purpose of the UE Context Release procedure is to enable the gNB-CU to order the release of the UE-associated logical connection or candidate cells in conditional handover or conditional PSCell addition or conditional PSCell change or LTM or subsequent CPAC. The procedure uses UE-associated signalling. + +### 8.3.3.2 Successful Operation + +![Sequence diagram showing the successful operation of the UE Context Release procedure initiated by the gNB-CU. The gNB-CU sends a UE CONTEXT RELEASE COMMAND to the gNB-DU, and the gNB-DU responds with a UE CONTEXT RELEASE COMPLETE message.](b2e5ca10383692a39c97d8b9929bcd6d_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: UE CONTEXT RELEASE COMMAND + gNB-DU-->>gNB-CU: UE CONTEXT RELEASE COMPLETE + Note right of gNB-CU: + +``` + +Sequence diagram showing the successful operation of the UE Context Release procedure initiated by the gNB-CU. The gNB-CU sends a UE CONTEXT RELEASE COMMAND to the gNB-DU, and the gNB-DU responds with a UE CONTEXT RELEASE COMPLETE message. + +**Figure 8.3.3.2-1: UE Context Release (gNB-CU initiated) procedure. Successful operation** + +The gNB-CU initiates the procedure by sending the UE CONTEXT RELEASE COMMAND message to the gNB-DU. + +Upon reception of the UE CONTEXT RELEASE COMMAND message, the gNB-DU shall release all related signalling and user data transport resources and reply with the UE CONTEXT RELEASE COMPLETE message. If the *CG-SDT Kept Indicator* IE is contained in the UE CONTEXT RELEASE COMMAND message and set to "true", the gNB-DU shall, if supported, consider that the UE is sent to RRC\_INACTIVE state with CG-SDT configuration and store the configured CG-SDT resources, C-RNTI, CS-RNTI, the CG-SDT related RLC configurations and F1-U connections associated with the SDT bearers while releasing the UE context. + +If the *old gNB-DU UE FIAP ID* IE is included in the UE CONTEXT RELEASE COMMAND message, the gNB-DU shall additionally release the UE context associated with the old gNB-DU UE FIAP ID. + +If the UE CONTEXT RELEASE COMMAND message contains the *RRC-Container* IE, the gNB-DU shall send the RRC container to the UE via the SRB indicated by the *SRB ID* IE. + +If the UE CONTEXT RELEASE COMMAND message includes the *Execute Duplication* IE, the gNB-DU shall perform CA based duplication, if configured, for the SRB for the included *RRC-Container* IE. + +If the *Candidate Cells To Be Cancelled List* IE is included in the UE CONTEXT RELEASE COMMAND message, the gNB-DU shall consider that the gNB-CU is cancelling only the conditional handover or conditional PSCell addition or conditional PSCell change or subsequent CPAC associated to the cells identified by the included NR CGIs and associated to the UE-associated signaling identified by the *gNB-CU UE FIAP ID* IE and the *gNB-DU UE FIAP ID* IE. + +If the *Positioning Context Reservation Indication* IE is included in the UE CONTEXT RELEASE COMMAND message, the gNB-DU shall not release the positioning context including the SRS configuration for the UE. + +If the *LTM Cells To Be Released List* IE is included in the UE CONTEXT RELEASE COMMAND message, the gNB-DU shall, if supported, consider that the gNB-CU is cancelling only the LTM cells identified by the included NR CGIs and associated to the UE-associated signaling identified by the *gNB-CU UE FIAP ID* IE and the *gNB-DU UE FIAP ID* IE. + +If the *Recommended SSBs for Paging List* IE is included in the UE CONTEXT RELEASE COMPLETE message, the gNB-CU shall, if supported, store it and may use it as assistance information for subsequent paging. + +#### Interactions with UE Context Setup procedure: + +The UE Context Release procedure may be performed before the UE Context Setup procedure to release an existing UE-associated logical F1-connection and related resources in the gNB-DU, e.g. when gNB-CU rejects UE access it shall trigger UE Context Release procedure with the cause value of UE rejection. + +### 8.3.3.4 Abnormal Conditions + +If one or more candidate cells in the *Candidate Cells To Be Cancelled List* IE included in the UE CONTEXT RELEASE COMMAND message were not prepared using the same UE-associated signalling connection, the gNB-DU shall ignore those non-associated candidate cells. + +If one or more LTM cells in the *LTM Cells To Be Released List* IE included in the UE CONTEXT RELEASE COMMAND message were not prepared using the same UE-associated signalling connection, the gNB-DU shall ignore those non-associated LTM cells. + +## 8.3.4 UE Context Modification (gNB-CU initiated) + +### 8.3.4.1 General + +The purpose of the UE Context Modification procedure is to modify the established UE Context, e.g., establishing, modifying and releasing radio resources or sidelink resources. This procedure is also used to command the gNB-DU to stop data transmission for the UE for mobility (see TS 38.401 [4]). The procedure uses UE-associated signalling. + +### 8.3.4.2 Successful Operation + +![Sequence diagram of the UE Context Modification procedure. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST to the gNB-DU, and the gNB-DU responds with a UE CONTEXT MODIFICATION RESPONSE.](c30bb9931a85960eb2e2008db772955c_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: UE CONTEXT MODIFICATION REQUEST + Note right of gNB-DU: + gNB-DU-->>gNB-CU: UE CONTEXT MODIFICATION RESPONSE + Note right of gNB-CU: +``` + +Sequence diagram of the UE Context Modification procedure. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST to the gNB-DU, and the gNB-DU responds with a UE CONTEXT MODIFICATION RESPONSE. + +Figure 8.3.4.2-1: UE Context Modification procedure. Successful operation + +The UE CONTEXT MODIFICATION REQUEST message is initiated by the gNB-CU. + +Upon reception of the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall perform the modifications, and if successful reports the update in the UE CONTEXT MODIFICATION RESPONSE message. + +If the *SpCell ID* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall replace any previously received value and regard it as a reconfiguration with sync as defined in TS 38.331 [8]. If the *ServCellIndex* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall take this into account for the indicated SpCell. If the *SpCell UL Configured* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall configure UL for the indicated SpCell accordingly. If the *servingCellMO* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall configure servingCellMO for the indicated SpCell accordingly. If the *servingCellMO List* IE is included in the UE CONTEXT SETUP MODIFICATION REQUEST message, the gNB-DU shall, if supported, configure servingCellMO after determining the list of BWPs for the UE and include the list of servingCellMOs that have been encoded in *CellGroupConfig* IE as *ServingCellMO-encoded-in-CGC List* IE in the UE CONTEXT MODIFICATION RESPONSE message. + +If the *Configured BWP List* IE is included in the UE CONTEXT MODIFICATION RESPONSE message the gNB-CU shall, if supported, take it into account when requesting the gNB-DU for generating preconfigured measurement GAP for the indicated BWPs. + +If the *Preconfigured Measurement GAP Request* IE is present in the *CU to DU RRC Information* IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, consider that the content of the previous *CellGroupConfig* IE was not sent to the UE and generate the pre-configured measurement GAP for the indicated BWPs in the *MeasConfig* IE. If the gNB-DU successfully generates pre-configured measurement GAP for the indicated BWPs, the gNB-DU shall update the *CellGroupConfig* IE with the content of the previous *CellGroupConfig* IE and the preconfigured measurement GAP configuration in the UE CONTEXT MODIFICATION RESPONSE message. + +If the *SCell To Be Setup List* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall consider it as a list of candidate SCells to be set up. If the *SCell To Be Setup List* IE is included in the UE CONTEXT MODIFICATION REQUEST message and the indicated SCell(s) are already setup, the gNB-DU shall replace any previously received value. If the *SCell UL Configured* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall configure UL for the indicated SCell accordingly. If the *servingCellMO* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall configure servingCellMO for the indicated SCell accordingly. + +If the *SCell To Be Removed List* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall consider it as a list of SCells to be removed. + +If the *DRX Cycle* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall use the provided value from the gNB-CU. If the *DRX configuration indicator* IE is contained in the UE CONTEXT MODIFICATION REQUEST message and set to "release", the gNB-DU shall release DRX configuration. + +If the *SL DRX Cycle list* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use the provided value from the gNB-CU for the indicated RX UE of this UE. If the *SL DRX configuration indicator* IE is contained in the UE CONTEXT MODIFICATION REQUEST message and set to "release", the gNB-DU shall, if supported, release SL DRX configuration for the indicated RX UE of this UE. + +If the *SRB To Be Setup List* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall act as specified in the TS 38.401 [4], and replace any previously received value. If *Duplication Indication* IE is contained in the *SRB To Be Setup List* IE, the gNB-DU shall, if supported, setup two RLC entities for the indicated SRB if the value is set to be "true", or delete the RLC entity of secondary path if the value is set to be "false". If the *Additional Duplication Indication* IE is contained in the *SRB To Be Setup List* IE, the gNB-DU shall, if supported, setup the indicated RLC entities for the indicated SRB. If the *SRB Mapping Info* IE is contained in the *SRB To Be Setup List* IE, the gNB-DU shall, if supported, store the mapping information indicated in the *SRB Mapping Info* IE for the SRB identified by the *SRB ID* IE and the Uu Relay RLC channel identified by the *SRB Mapping Info*. The gNB-DU shall use the mapping information stored for the mapping of SRB data to Uu Relay RLC channel. If the *Duplication Indication* IE and *SRB Mapping Info* IE are both contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, setup one RLC entity for the direct path if the value is set to be "true", and map the indicated SRB to the Uu Relay RLC channel based on the *SRB Mapping Info* IE. If the *Additional Duplication* + +*Indication IE* and *SRB Mapping Info IE* are both contained in the *SRB To Be Setup List IE*, the gNB-DU shall, if supported, setup the indicated RLC entities for the indicated SRB, and map the indicated SRB to the Uu Relay RLC channel or the logical channel based on the *SRB Mapping Info IE*. The number of RLC entities to be set up is the indicated value of *Additional Duplication Indication IE* minus 1. + +If the *DRB To Be Setup List IE* is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall act as specified in the TS 38.401 [4]. If the *DRB Mapping Info IE* is contained in the *DRB To Be Setup List IE*, the gNB-DU shall, if supported, store the mapping information indicated in the *DRB Mapping Info IE*, if present, for the DRB identified by the *DRB ID IE* and the Uu Relay RLC channel identified by the *DRB Mapping Info*. The gNB-DU shall use the mapping information stored for the mapping of DRB data to Uu Relay RLC channel. + +If the *BH Information IE* is included in the *UL UP TNL Information to be setup List IE* or the *Additional PDCP Duplication TNL List IE* for a DRB, the gNB-DU shall, if supported, use the indicated BAP Routing ID and BH RLC channel for transmission of the corresponding GTP-U packets to the IAB-donor, as specified in TS 38.340 [30]. + +If the *BH RLC Channel To Be Setup List IE* is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall act as specified in TS 38.401 [4]. If the *Traffic Mapping Information IE* is included in the *BH RLC Channel To Be Setup Item IEs IE* for a BH RLC Channel, the gNB-DU shall, if supported, process the *Traffic Mapping Information IE* following the behaviour described for the UE Context Setup procedure. + +If the *BH RLC Channel To Be Modified List IE* is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall act as specified in TS 38.401 [4]. If the *Traffic Mapping Information IE* is included in the *BH RLC Channel To Be Modified Item IEs IE* for a BH RLC Channel, the gNB-DU shall, if supported, process the *Traffic Mapping Information IE* following the behaviour described for the UE Context Setup procedure. + +If the *BH RLC Channel To Be Released List IE* is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall release the BH RLC channels in the list. + +If two *UL UP TNL Information IEs* are included and the *DRB Mapping Info IE* is not contained in UE CONTEXT MODIFICATION REQUEST message for a DRB, the gNB-DU shall include two *DL UP TNL Information IEs* in UE CONTEXT MODIFICATION RESPONSE message and setup two RLC entities for the indicated DRB. If the *UL UP TNL Information IE* with the *DRB Mapping Info IE* and the *UL UP TNL Information IE* without the *DRB Mapping Info IE* are both contained in the UE CONTEXT MODIFICATION REQUEST message for a DRB, the gNB-DU shall, if supported, include two *DL UP TNL Information IEs* in UE CONTEXT MODIFICATION RESPONSE message, setup one RLC entity for the *UL UP TNL Information IE* without the *DRB Mapping Info IE*, and map the indicated DRB to the Uu Relay RLC channel based on the *DRB Mapping Info IE*. gNB-CU and gNB-DU use the *UL UP TNL Information IEs* and *DL UP TNL Information IEs* to support packet duplication for intra-gNB-DU CA and multi-path relay as defined in TS 38.470 [2]. The first *UP TNL Information IE* of the two *UP TNL Information IEs* is for the primary path. + +If one or two *Additional PDCP Duplication UP TNL Information IEs* are included in the UE CONTEXT MODIFICATION REQUEST message for a DRB, the gNB-DU shall, if supported, include one or two *Additional PDCP Duplication UP TNL Information IEs* in the UE CONTEXT MODIFICATION RESPONSE message and setup one or two additional RLC entities for the indicated DRB. The gNB-CU and the gNB-DU use the *Additional PDCP Duplication UP TNL Information IEs* to support packet duplication for intra-gNB-DU CA as defined in TS 38.470 [2]. + +If *Duplication Activation IE* is included in the UE CONTEXT MODIFICATION REQUEST message for a DRB, the gNB-DU should take it into account when activating/deactivating CA based PDCP duplication or multi-path relay based PDCP duplication for the DRB. If the *RLC Duplication State List IE* is included in the *RLC Duplication Information IE* contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take it into account for the DRB with more than two RLC entities. + +If *DC Based Duplication Configured IE* is included in the UE CONTEXT MODIFICATION REQUEST message for a DRB, the gNB-DU shall regard that DC based PDCP duplication is configured for this DRB if the value is set to be "true" and it should take the responsibility of PDCP duplication activation/deactivation. Otherwise, the gNB-DU shall regard that DC based PDCP duplication is de-configured for this DRB if the value is set to be "false", and it should stop + +PDCP duplication activation/deactivation by MAC CE. If *DC Based Duplication Activation* IE is included in the UE CONTEXT MODIFICATION REQUEST message for a DRB, the gNB-DU should take it into account when activating/deactivating DC based PDCP duplication for this DRB. If the *RLC Duplication State List* IE is included in the *RLC Duplication Information* IE contained in the UE CONTEXT MODIFICATION REQUEST message for a DRB, the gNB-DU shall, if supported, take it into account when activating/deactivating DC based PDCP duplication for the DRB with more than two RLC entities. If the *Primary Path Indication* IE is included in the *RLC Duplication Information* IE, the gNB-DU shall, if supported, take it into account when performing DC based PDCP duplication for the DRB with more than two RLC entities. + +For a certain DRB which was allocated with two GTP-U tunnels, if such DRB is modified and given one GTP-U tunnel via the UE Context Modification procedure, the gNB-DU shall consider that the CA based PDCP duplication or multi-path relay based PDCP duplication for the concerned DRB is de-configured. If such UE Context Modification procedure occurs, the *Duplication Activation* IE shall not be included for the concerned DRB. + +If the *UL Configuration* IE in *DRB to Be Setup Item* IE or *DRB to Be Modified Item* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall take it into account for UL scheduling. + +If the *RRC Reconfiguration Complete Indicator* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall consider the ongoing reconfiguration procedure involving changes of the L1/L2 configuration at the gNB-DU signalled to the gNB-CU via the *CellGroupConfig* IE for MR-DC operation or standalone operation has been successfully performed when such IE is set to 'true'; otherwise (when such IE is set to 'failure'), the gNB-DU shall consider the ongoing reconfiguration procedure has been failed and it shall continue to use the old L1/L2 configuration. + +If *DL PDCP SN length* IE is included in the UE CONTEXT MODIFICATION REQUEST message for a DRB, gNB-DU shall, if supported, store this information and use it for lower layer configuration. + +If *UL PDCP SN length* IE is included in the UE CONTEXT MODIFICATION REQUEST message for a DRB, gNB-DU shall, if supported, store this information and use it for lower layer configuration. + +If the *RLC Failure Indication* IE is included in UE CONTEXT MODIFICATION REQUEST message, the gNB-DU should consider that the RLC entity indicated by such IE needs to be re-established when the CA-based packet duplication is active, and the gNB-DU may include the *Associated SCell List* IE in UE CONTEXT MODIFICATION RESPONSE by containing a list of SCell(s) associated with the RLC entity indicated by the *RLC Failure Indication* IE. + +If the UE CONTEXT MODIFICATION REQUEST message contains the *RRC-Container* IE, the gNB-DU shall send the corresponding RRC message to the UE. If the UE CONTEXT MODIFICATION REQUEST message includes the *Execute Duplication* IE, the gNB-DU shall perform CA based duplication, if configured, for the SRB for the included *RRC-Container* IE. + +If the UE CONTEXT MODIFICATION REQUEST message contains the *Transmission Action Indicator* IE, the gNB-DU shall stop or restart (if already stopped) data transmission for the UE, according to the value of this IE. It is up to gNB-DU implementation when to stop or restart the UE scheduling. + +For EN-DC operation, if the *DRB to Be Setup List* IE is present in the UE CONTEXT MODIFICATION REQUEST message the gNB-CU shall include the *E-UTRAN QoS* IE. The allocation of resources according to the values of the *Allocation and Retention Priority* IE included in the *E-UTRAN QoS* IE shall follow the principles described for the E-RAB Setup procedure in TS 36.413 [15]. For NG-RAN operation, the gNB-CU shall include the *DRB Information* IE in the UE CONTEXT MODIFICATION REQUEST message. + +If the gNB-CU includes the SMTC information of the measured frequency(ies) in the *MeasurementTimingConfiguration* IE of the *CU to DU RRC Information* IE that is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall generate the measurement gaps based on the received SMTC information. Then the gNB-DU shall send the measurement gaps information to the gNB-CU in the *MeasGapConfig* IE of the *DU to CU RRC Information* IE that is included in the UE CONTEXT MODIFICATION RESPONSE message. + +If the *MeasConfig* IE is included in the *CU to DU RRC Information* IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall deduce that changes to the measurements' configuration need to be applied. The gNB-DU shall take the received info, e.g. the *measObjectToAddModList* IE, and/or the *measObjectToRemoveList* IE into account, when generating measurement gap and when deciding if a measurement gap is needed or not. + +If the *NeedForGapsInfoNR* IE is included in the *CU to DU RRC Information* IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it as described in TS 38.331 [8]. If the *NeedForGapNCSG-InfoNR* IE is included in the *CU to DU RRC Information* IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it as described in TS 38.331 [8]. If the *NeedForGapNCSG-InfoEUTRA* IE is included in the *CU to DU RRC Information* IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it as described in TS 38.331 [8]. If the *NeedForInterruptionInfoNR* IE is included in the *CU to DU RRC Information* IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it as described in TS 38.331 [8]. + +For DC operation, if the gNB-CU includes the *CG-Config* IE in the *CU to DU RRC Information* IE that is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU may initiate low layer parameters coordination taking this information into account. + +For sidelink operation, the *CG-ConfigInfo* IE shall be included in the *CU to DU RRC Information* IE if the gNB-CU receives sidelink related UE information from UE. If the *CG-ConfigInfo* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall regard it as an indication of V2X sidelink information as defined in TS 38.331 [8]. + +For EN-DC operation, if the gNB-CU includes the *Resource Coordination Transfer Information* IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it for the purpose of resource coordination. If the gNB-CU received the MeNB Resource Coordination Information as defined in TS 36.423 [9], after completion of UE Context Setup procedures, the gNB-CU shall transparently transfer it to the gNB-DU via the *Resource Coordination Transfer Container* IE in the UE CONTEXT MODIFICATION REQUEST message. The gNB-DU shall use the information received in the *Resource Coordination Transfer Container* IE for reception of MeNB Resource Coordination Information at the gNB acting as secondary node as described in TS 36.423 [9]. If the *Resource Coordination E-UTRA Cell Information* IE is included in the *Resource Coordination Transfer Information* IE, the gNB-DU shall store the information replacing previously received information for the same E-UTRA cell, and use the stored information for the purpose of resource coordination. If the *Ignore PRACH Configuration* IE is present and set to "true" the *E-UTRA PRACH Configuration* IE in the UE CONTEXT MODIFICATION REQUEST message shall be ignored. + +For NGEN-DC or NE-DC operation, if the gNB-CU includes the *Resource Coordination Transfer Information* IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it for the purpose of resource coordination. If the gNB-CU received the MR-DC Resource Coordination Information as defined in TS 38.423 [28], after completion of UE Context Setup procedures, the gNB-CU shall transparently transfer it to the gNB-DU via the *Resource Coordination Transfer Container* IE in the UE CONTEXT MODIFICATION REQUEST message. The gNB-DU shall use the information received in the *Resource Coordination Transfer Container* IE for reception of MR-DC Resource Coordination Information at the gNB as described in TS 38.423 [28]. + +For EN-DC operation, and if the *Subscriber Profile ID for RAT/Frequency priority* IE is received from an MeNB, the UE CONTEXT MODIFICATION REQUEST message shall contain the *Subscriber Profile ID for RAT/Frequency priority* IE. If the *Additional RRM Policy Index* IE is received from an MeNB, the UE CONTEXT MODIFICATION REQUEST message shall, if supported, contain the *Additional RRM Policy Index* IE. The gNB-DU shall store the received Subscriber Profile ID for RAT/Frequency priority in the UE context and use it as defined in TS 36.300 [20]. The gNB-DU shall, if supported, store the received Additional RRM Policy Index in the UE context and use it as defined in TS 36.300 [20]. + +If the *Index to RAT/Frequency Selection Priority* IE is modified at the gNB-CU, the *Index to RAT/Frequency Selection Priority* IE shall be included in the UE CONTEXT MODIFICATION REQUEST. The gNB-DU may use it for RRM purposes. + +Only one of the following IEs shall be contained in the UE CONTEXT MODIFICATION REQUEST message: the *Uplink TxDirectCurrentList Information* IE or the *Uplink TxDirectCurrentTwoCarrierList Information* IE or the *Uplink TxDirectCurrentMoreCarrierList Information* IE. If the UE CONTEXT MODIFICATION REQUEST message contains one of the *Uplink TxDirectCurrentList Information* IE or the *Uplink TxDirectCurrentTwoCarrierList Information* IE or the *Uplink TxDirectCurrentMoreCarrierList Information* IE, the gNB-DU may take that into account when selecting L1 configuration. + +The *UEAssistanceInformation* IE shall be included in *CU to DU RRC Information* IE in the UE CONTEXT MODIFICATION REQUEST message if the gNB-CU received this IE from the UE; if the *UEAssistanceInformation* IE is included in the *CU to DU RRC Information* IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take it into account when configuring resources for the UE. + +The *UEAssistanceInformationEUTRA* IE shall be included in *CU to DU RRC Information* IE in the UE CONTEXT MODIFICATION REQUEST message if the gNB-CU received this IE from the UE; if the *UEAssistanceInformationEUTRA* IE is included in the *CU to DU RRC Information* IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take it into account when configuring LTE sidelink resources for the UE. + +The gNB-DU shall report to the gNB-CU, in the UE CONTEXT MODIFICATION RESPONSE message, the result for all the requested or modified DRBs, SRBs, BH RLC Channels, Uu Relay RLC channels, PC5 Relay RLC channels, and SL DRBs in the following way: + +- 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 to be Setup 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 be Modified List* IE; +- A list of SRBs which failed to be established shall be included in the *SRB Failed to be Setup List* IE. +- A list of successfully established SRBs with logical channel identities for primary path shall be included in the *SRB Setup List* IE only if CA based PDCP duplication is initiated for the concerned SRBs. +- A list of successfully modified SRBs with logical channel identities for primary path shall be included in the *SRB Modified List* IE only if CA based PDCP duplication is initiated for the concerned SRBs. +- A list of BH RLC channels which are successfully established shall be included in the *BH RLC Channel Setup List* IE; +- A list of BH RLC channels which failed to be established shall be included in the *BH RLC Channel Failed to be Setup List* IE; +- A list of BH RLC channels which are successfully modified shall be included in the *BH RLC Channel Modified List* IE; +- A list of BH RLC channels which failed to be modified shall be included in the *BH RLC Channel Failed to be Modified List* IE; +- A list of Uu Relay RLC channels which are successfully established shall be included in the *Uu RLC Channel Setup List* IE; +- A list of Uu Relay RLC channels which failed to be established shall be included in the *Uu RLC Channel Failed to be Setup List* IE; +- A list of Uu Relay RLC channels which are successfully modified shall be included in the *Uu RLC Channel Modified List* IE; + +- A list of Uu Relay RLC channels which are failed to be modified shall be included in the *Uu RLC Channel Failed to be Modified List IE*; +- A list of PC5 Relay RLC channels which are successfully established shall be included in the *PC5 RLC Channel Setup List IE*; +- A list of PC5 Relay RLC channels which failed to be established shall be included in the *PC5 RLC Channel Failed to be Setup List IE*; +- A list of PC5 Relay RLC channels which are successfully modified shall be included in the *PC5 RLC Channel Modified List IE*; +- A list of PC5 Relay RLC channels which failed to be modified shall be included in the *PC5 RLC Channel Failed to be Modified List IE*; +- A list of SL DRBs which are successfully established shall be included in the *SL DRB Setup List IE*; +- A list of SL DRBs which failed to be established shall be included in the *SL DRB Failed to be Setup List IE*; +- A list of SL DRBs which are successfully modified shall be included in the *SL DRB Modified List IE*; +- A list of SL DRBs which failed to be modified shall be included in the *SL DRB Failed to be Modified List IE*. + +If *Duplication Indication IE* in *SL DRB To Be Setup List IE* is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, generate two PC5 RLC configurations for the indicated SL DRB. + +If *Duplication Indication IE* is contained in the *SL DRB To Be Modified List IE*, the gNB-DU shall, if supported, generate two PC5 RLC configurations for the indicated SL DRB, if the value is set to be "true" and duplication is not already configured for the indicated SL DRB. + +If *Duplication Indication IE* is contained in the *SL DRB To Be Modified List IE*, the gNB-DU shall, if supported, release the additional PC5 RLC configuration for the indicated SL DRB, if the value is set to be "false". + +For each GBR DRB, if the *Alternative QoS Parameters Sets IE* is included in the *GBR QoS Flow Information IE* in the UE CONTEXT MODIFICATION REQUEST message, gNB-DU shall, if supported, behave the same as the NG-RAN node in the PDU Session Resource Setup procedure, specified in TS 38.413 [3]. + +If the *BAP Control PDU Channel IE* is included in the *BH RLC Channel to be Setup List IE*, the gNB-DU shall, if supported, consider that the configured BH RLC channel can be used to transmit BAP Control PDUs, and use this BH RLC channel as specified in TS 38.340 [30]. + +If the *BAP Control PDU Channel IE* is included in the *BH RLC Channel to be Modified List IE*, the gNB-DU shall, if supported, consider that the configured BH RLC channel can be used to transmit BAP Control PDUs, and use this BH RLC channel as specified in TS 38.340 [30]. Otherwise, if the *BAP Control PDU Channel IE* is not present for any BH RLC channel, any available BH RLC channel can be used to transmit BAP Control PDUs as specified in TS 38.340 [30]. + +If the *FI-C Transfer Path IE* is included in UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take it into account. + +When the gNB-DU reports the unsuccessful establishment of a DRB or SRB or SL DRB or a BH RLC channel or a Uu Relay RLC channel or a PC5 Relay RLC channel, the cause value should be precise enough to enable the gNB-CU to know the reason for the unsuccessful establishment. + +If the *Resource Coordination Transfer Container IE* is included in the UE CONTEXT MODIFICATION RESPONSE, the gNB-CU shall transparently transfer this information for the purpose of resource coordination as described in TS 36.423 [9], TS 38.423 [28]. + +If the *DU to CU RRC Information* IE is included in the UE CONTEXT MODIFICATION RESPONSE message, except for the CG-SDT procedure and UE configured with BWP specific ServingCellMO, the gNB-CU shall perform RRC Reconfiguration as described in TS 38.331 [8]. The *CellGroupConfig* IE shall transparently be signaled to the UE as specified in TS 38.331 [8]. In the cases of CG-SDT, and UE configured with BWP specific ServingCellMO, the *CellGroupConfig* IE shall be ignored by the gNB-CU. + +If the *ServCellInfoList* IE is included in the *DU to CU RRC Information* IE contained in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall take it into account to generate the content of inter-node message, i.e., *CG-Config* or *CG-ConfigInfo*, as described in TS 38.331 [8]. + +If the *UE-CapabilityRAT-ContainerList* IE is included in the UE CONTEXT SETUP MODIFICATION REQUEST, the gNB-DU shall take this information into account for UE specific configurations. + +If the *SCell Failed To Setup List* IE is contained in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall regard the corresponding SCell(s) failed to be set up with an appropriate cause value for each SCell failed to setup. + +If the *C-RNTI* IE is included in the UE CONTEXT MODIFICATION RESPONSE, the gNB-CU shall consider that the C-RNTI has been allocated by the gNB-DU for this UE context. + +If the *Inactivity Monitoring Request* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, gNB-DU may consider that the gNB-CU has requested the gNB-DU to perform UE inactivity monitoring. If the *Inactivity Monitoring Response* IE is contained in the UE CONTEXT MODIFICATION RESPONSE message and set to "Not-supported", the gNB-CU shall consider that the gNB-DU does not support UE inactivity monitoring for the UE. + +The UE Context Modify Procedure is not used to configure SRB0. + +If in the UE CONTEXT MODIFICATION REQUEST, the *Notification Control* IE is included in the *DRB to Be Setup List* IE or the *DRB to Be Modified List* IE and it is set to active, the gNB-DU shall, if supported, monitor the QoS of the DRB and notify the gNB-CU if the QoS cannot be fulfilled any longer or if the QoS can be fulfilled again. The *Notification Control* IE can only be applied to GBR bearers. + +If the *UL PDU Session Aggregate Maximum Bit Rate* IE is included in the *QoS Flow Level QoS Parameters* IE contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall replace the received UL PDU Session Aggregate Maximum Bit Rate and use it as specified in TS 23.501 [21]. + +If the *gNB-DU UE Aggregate Maximum Bit Rate Uplink* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall: + +- replace the previously provided gNB-DU UE Aggregate Maximum Bit Rate Uplink with the new received gNB-DU UE Aggregate Maximum Bit Rate Uplink; +- use the received gNB-DU UE Aggregate Maximum Bit Rate Uplink for non-GBR Bearers for the concerned UE. + +The *gNB-DU UE Aggregate Maximum Bit Rate Uplink* IE shall be sent in the UE CONTEXT MODIFICATION REQUEST if *DRB to Be Setup List* IE is included and the gNB-CU has not previously sent it. The gNB-DU shall store and use the received *gNB-DU UE Aggregate Maximum Bit Rate Uplink* IE. + +If the *RLC Status* IE is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall assume that RLC has been reestablished at the gNB-DU and may trigger PDCP data recovery. + +If the *GNB-DU Configuration Query* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, gNB-DU shall include the *DU To CU RRC Information* IE in the UE CONTEXT MODIFICATION RESPONSE message. + +If the *Bearer Type Change* IE is included in *DRB to Be Modified List* IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall either reset the lower layers or generate a new LCID for the affected bearer as specified in TS 37.340 [7]. + +For NE-DC operation, if *NeedforGap* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall generate measurement gap for the SeNB. + +If the *QoS Flow Mapping Indication* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU 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 *Lower Layer presence status change* IE set to "suspend lower layers" is included in the UE CONTEXT MODIFICATION REQUEST, the gNB-DU shall keep all lower layer configuration for UEs, and not transmit or receive data from UE. + +If the *Lower Layer presence status change* IE set to "resume lower layers" is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall use the previously stored lower layer configuration for the UE. + +If the *Full Configuration* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall generate a *CellGroupConfig* IE using full configuration and include it in the UE CONTEXT MODIFICATION RESPONSE. + +If the *Full Configuration* IE is contained in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall consider that the gNB-DU has generated the *CellGroupConfig* IE using full configuration. + +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 UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall store this information, and, if supported, perform delay measurement and QoS monitoring, as specified in TS 23.501 [21]. + +If the *NR V2X Services Authorized* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, update its V2X services authorization information for the UE accordingly. If the *NR V2X Services Authorized* IE includes one or more IEs set to "not authorized", the gNB-DU shall, if supported, initiate actions to ensure that the UE is no longer accessing the relevant service(s). + +If the *LTE V2X Services Authorized* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, update its V2X services authorization information for the UE accordingly. If the *LTE V2X Services Authorized* IE includes one or more IEs set to "not authorized", the gNB-DU shall, if supported, initiate actions to ensure that the UE is no longer accessing the relevant service(s). + +If the *LTE UE Sidelink Aggregate Maximum Bit Rate* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported: + +- replace the previously provided UE LTE Sidelink Aggregate Maximum Bit Rate, if available in the UE context, with the received value; +- use the received value for the concerned UE's sidelink communication in network scheduled mode for LTE V2X services. + +If the *NR UE Sidelink Aggregate Maximum Bit Rate* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported: + +- replace the previously provided UE NR Sidelink Aggregate Maximum Bit Rate, if available in the UE context, with the received value; +- use the received value for the concerned UE's sidelink communication in network scheduled mode for NR V2X services. + +If the *NR A2X Services Authorized* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, update its A2X services authorization information for the UE accordingly. If the *NR A2X* + +*Services Authorized* IE includes one or more IEs set to "not authorized", the gNB-DU shall, if supported, initiate actions to ensure that the UE is no longer accessing the relevant service(s). + +If the *LTE A2X Services Authorized* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, update its A2X services authorization information for the UE accordingly. If the *LTE A2X Services Authorized* IE includes one or more IEs set to "not authorized", the gNB-DU shall, if supported, initiate actions to ensure that the UE is no longer accessing the relevant service(s). + +If the *LTE UE Sidelink Aggregate Maximum Bit Rate for A2X* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported: + +- replace the previously provided UE LTE Sidelink Aggregate Maximum Bit Rate for A2X, if available in the UE context, with the received value; +- use the received value for the concerned UE's sidelink communication in network scheduled mode for LTE A2X services. + +If the *NR UE Sidelink Aggregate Maximum Bit Rate for A2X* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported: + +- replace the previously provided UE NR Sidelink Aggregate Maximum Bit Rate for A2X, if available in the UE context, with the received value; +- use the received value for the concerned UE's sidelink communication in network scheduled mode for NR A2X services. + +If the *PC5 Link Aggregate Maximum Bit Rate* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported: + +- replace the previously provided UE PC5 Link Aggregate Bit Rate, if available in the UE context, with the received value; +- use the received value for the concerned UE's sidelink communication in network scheduled mode for NR V2X services as defined in TS 23.287 [40]. + +If the *TSC Traffic Characteristics* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take into account the corresponding information received in the *TSC Traffic Characteristics* IE. If the *RAN Feedback Type* IE is included in the *TSC Assistance Information Uplink* IE of the *TSC Traffic Characteristics* IE, the gNB-DU shall, if supported, take this information into account when determining the feedback to provide in the *TSC Traffic Characteristics Feedback* IE in the UE CONTEXT MODIFICATION RESPONSE message. + +If the *CPAC MCG Information* IE is included in the UE CONTEXT MODIFICATION REQUEST message and the CPAC Trigger is set to "CPAC-preparation", the gNB-DU shall, if supported, consider that the request concerns a conditional PSCell addition or conditional PSCell change or subsequent CPAC. The gNB-DU takes the included *CG-Config* and/or *CG-ConfigInfo* IE into account, and may provide a corresponding *CellGroupConfig* IE for MCG configuration preparation in the UE CONTEXT MODIFICATION RESPONSE message. The UE CONTEXT MODIFICATION RESPONSE message also includes a *Requested Target Cell ID* IE corresponding to the *PSCell ID* IE in the UE CONTEXT MODIFICATION REQUEST message. + +If the *CPAC MCG Information* IE is included in the UE CONTEXT MODIFICATION REQUEST message and the CPAC Trigger is set to "CPAC-executed", the gNB-DU shall, if supported, consider that, for the included *PSCell ID* IE corresponding to the selected PSCell, the UE has successfully executed the CPAC preparation. The gNB-DU shall apply the corresponding *CellGroupConfig* IE for MCG configuration. + +If the *Conditional Intra-DU Mobility Information* IE is included in the UE CONTEXT MODIFICATION REQUEST message and the CHO Trigger is set to "CHO-initiation", the gNB-DU shall consider that the request concerns a conditional handover or conditional PSCell addition or conditional PSCell change or subsequent CPAC for the included + +*SpCell ID IE* and shall include it as the *Requested Target Cell ID IE* in the UE CONTEXT MODIFICATION RESPONSE message. The gNB-DU shall regard it as a reconfiguration with sync as defined in TS 38.331 [8]. + +If the *Conditional Intra-DU Mobility Information IE* is included in the UE CONTEXT MODIFICATION REQUEST message and the CHO Trigger is set to "CHO-replace", the gNB-DU shall replace the existing prepared conditional mobility identified by the *gNB-DU UE FIAP ID IE* and the *SpCell ID IE*. + +If the *Conditional Intra-DU Mobility Information IE* is included in the UE CONTEXT MODIFICATION REQUEST message and the CHO Trigger is set to "CHO-cancel", the gNB-DU shall consider that the gNB-CU is about to remove any reference to, and release any resources previously reserved for the candidate cells associated to the UE-associated signalling identified by the *gNB-CU UE FIAP ID IE* and the *gNB-DU UE FIAP ID IE*. If the *Candidate Cells To Be Cancelled List IE* is also included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall consider that only the resources reserved for the cells identified by the included NR CGIs are about to be released by the gNB-CU. + +If the *Transmission Stop Indicator IE* is included within the *DRB to Be Modified Item IE* in the UE CONTEXT MODIFICATION REQUEST message and set to "true", the gNB-DU shall, if supported, stop the data transmission for the DRB. It is up to gNB-DU implementation when to stop the UE scheduling for that DRB. + +If the *SCG Indicator IE* is contained in the UE CONTEXT MODIFICATION REQUEST message and it is set to "released", the gNB-DU shall, if supported, deduce that an SCG is removed. + +If the *Estimated Arrival Probability IE* is contained in the *Conditional Intra-DU Mobility Information IE* included in the UE CONTEXT MODIFICATION REQUEST message, then the gNB-DU may use the information to allocate necessary resources for the UE. + +If the *Location Measurement Information IE* is included in the *CU to DU RRC Information IE* in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take it into account when configuring measurement gaps for the UE. + +If the *F1-C Transfer Path NRDC IE* is included in UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take it into account. + +If for a given E-RAB for EN-DC operation the *ENB DL Transport Layer Address IE* is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed. + +If for a given Qos flow for NG-RAN operation the *PDCP Terminating Node DL Transport Layer Address IE* is included in the UE CONTEXT MODIFICATION REQUEST message, then the gNB-DU shall, if supported, use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed. + +If the gNB-DU is an IAB-DU, and if the *IAB Conditional RRC Message Delivery Indication IE* is included in the UE CONTEXT MODIFICATION REQUEST message together with the *RRC-Container IE*, and if its value is set to "true", and if the *RRC-Container IE* is for a child IAB-MT of the gNB-DU, the gNB-DU shall, if supported, withhold the RRC message until one of the following conditions is met: + +- If the gNB-DU belongs to a migrating IAB-node, whose co-located IAB-MT has successfully performed the random-access procedure to the target parent node, and if the migrating IAB-node has one or more routing entries for the target path. + +- The gNB-DU receives a subsequent F1AP message including an *RRC-Container IE* for the same child node. + +- If the gNB-DU belongs to a descendant node of the migrating IAB-node, whose co-located IAB-MT has received an *RRCReconfiguration* message including the intra-donor migration configurations, e.g., new TNL address(es) and the new default UL BAP routing ID. + +If the gNB-DU belongs to a migrating IAB-node, whose co-located IAB-MT has successfully performed RLF recovery after handover failure, and if the migrating IAB-node has one or more routing entries for the target path. + +If the *MDT Polluted Measurement Indicator* IE is included in the UE CONTEXT MODIFICATION REQUEST, the gNB-DU shall take this information into account as specified in TS 38.401 [4]. + +If the *SCG Activation Request* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU may use it to configure SCG resources as specified in TS 37.340 [7], and if supported, shall include the *SCG Activation Status* IE in the UE CONTEXT MODIFICATION RESPONSE message. + +If the *CG-SDT Query Indication* IE is included in the UE CONTEXT MODIFICATION REQUEST message and set to 'true', the gNB-DU shall, if supported, provide the CG-SDT related resource configuration for the bearers indicated as SDT bearers in the *SDT-MAC-PHY-CG-Config* IE within the *DU to CU RRC Information* IE contained in the UE CONTEXT MODIFICATION RESPONSE message to the gNB-CU. If the *SDT-MAC-PHY-CG-Config* IE is also included in the UE CONTEXT MODIFICATION REQUEST message within the *CU to DU RRC Information* IE, the gNB-DU may provide the delta signalling version of the *SDT-MAC-PHY-CG-Config* IE within the *DU to CU RRC Information* IE contained in the UE CONTEXT MODIFICATION RESPONSE message to the gNB-CU. + +If the *5G ProSe Authorized* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, update its 5G ProSe services authorization information for the UE accordingly. If the *5G ProSe Authorized* IE includes one or more IEs set to "not authorized", the gNB-DU shall, if supported, initiate actions to ensure that the UE is no longer accessing the relevant service(s). + +If the *SDT Bearer Configuration Query Indication* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, provide the RLC bearer configuration in the *SDT Bearer Configuration Info* IE in the UE CONTEXT MODIFICATION RESPONSE message for each bearer indicated as SDT bearer. + +If the *5G ProSe UE PC5 Aggregate Maximum Bit Rate* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported: + +- replace the previously provided 5G ProSe UE PC5 Aggregate Maximum Bit Rate, if available in the UE context, with the received value; +- use the received value for the concerned UE's sidelink communication in network scheduled mode for 5G ProSe services. + +If the *5G ProSe PC5 Link Aggregate Bit Rate* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported: + +- replace the previously provided 5G ProSe PC5 Link Aggregate Bit Rate, if available in the UE context, with the received value; +- use the received value for the concerned UE's sidelink communication in network scheduled mode for 5G ProSe services as defined in TS 23.304 [44]. + +If the *Updated Remote UE Local ID* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, replace the previously provided Remote UE Local ID, if available in the UE context, with the received value. + +If the *Uu RLC Channel To Be Setup List* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, act as specified in TS 38.401 [4]. + +If the *Uu RLC Channel To Be Modified List* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, act as specified in TS 38.401 [4]. + +If the *Uu RLC Channel To Be Release List* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, release the Uu Relay RLC channels in the list. + +If the *PC5 RLC Channel To Be Setup List* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, act as specified in TS 38.401 [4]. gNB-DU generates the PC5 Relay RLC channel configurations for a L2 U2N Remote UE or U2N Relay UE. If the F1AP-IDs are associated with a U2N Relay UE, the *PC5 RLC Channel to be Setup Item IEs* IE shall include the *Remote UE Local ID* and correspondingly, the *PC5 RLC Channel Setup Item IEs* IE and the *PC5 RLC Channel Failed to be Setup Item* IE in the UE CONTEXT MODIFICATION RESPONSE message shall include the *Remote UE Local ID* IE. + +If the *PC5 RLC Channel To Be Modified List* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, act as specified in TS 38.401 [4]. gNB-DU generates the PC5 Relay RLC channel configurations for a L2 U2N Remote UE or U2N Relay UE. If the F1AP-IDs are associated with a U2N Relay UE, the *PC5 RLC Channel to be Modified Item IEs* IE shall include the *Remote UE Local ID* IE and correspondingly, the *PC5 RLC Channel Modified Item IEs* IE and the *PC5 RLC Channel Failed to be Modified Item IEs* IE in the UE CONTEXT MODIFICATION RESPONSE message shall include the *Remote UE Local ID* IE. + +If the *PC5 RLC Channel To Be Release List* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, release the PC5 Relay RLC channels in the list. If the F1AP-IDs are associated with a U2N Relay UE, the *PC5 RLC Channel to be Released Item IEs* IE shall include the *Remote UE Local ID* IE. + +If the *Path Switch Configuration* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it to configure the path switch from direct path to indirect path as specified in TS 38.401 [4]. + +If the *MUSIM-GapConfig* IE is contained in the *CU to DU RRC Information* IE included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, decide to use this IE for MUSIM gap configuration or select another one based on the received *UEAssistanceInformation* IE. If gNB-DU selects a different MUSIM gap configuration from received *UEAssistanceInformation* IE, then it shall include the selected MUSIM gap information to the gNB-CU in the *MUSIM-GapConfig* IE of the *DU to CU RRC Information* IE that is included in the UE CONTEXT MODIFICATION RESPONSE message. + +If *MUSIM-GapConfig* IE is not contained in the *CU to DU RRC Information* IE, then gNB-DU shall, if supported, send the selected MUSIM gap configuration based on the received *UEAssistanceInformation* IE, to the gNB-CU in the *MUSIM-GapConfig* IE of the *DU to CU RRC Information* IE that is included in the UE CONTEXT MODIFICATION RESPONSE message. When MUSIM-GapConfig IE is received, the gNB-CU should use this value. + +If the *gNB-DU UE Slice Maximum Bit Rate List* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, + +- store and replace the previously provided gNB-DU UE Slice Maximum Bit Rate List, if any, with the new received *gNB-DU UE Slice Maximum Bit Rate List*; +- use the received *gNB-DU UE Slice Maximum Bit Rate List* for the uplink traffic policing for each concerned slice as specified in TS 23.501 [21]. + +If the *Multicast MBS Session Setup List* IE or the *Multicast MBS Session Remove List* IE or both IEs are contained in the UE CONTEXT MODIFICATION REQUEST message the gNB-DU shall, if supported, store and use the information for configuring MBS Session Resources, if applicable. + +If the *UE Multicast MRB To Be Setup at Modify List* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take it into account for configuring MBS Session Resources, if applicable, and shall include the *Multicast F1-U Context Reference CU* IE, if available, in the UE CONTEXT MODIFICATION RESPONSE message. And if the *MBS PTP Retransmission Tunnel Required* IE is included in the *UE Multicast MRB to Be Setup at Modify Item IEs* IE, the gNB-DU shall, if supported trigger the establishment of the MBS PTP Retransmission F1-U tunnel. + +If the *MBS PTP Forwarding Tunnel Required Information* IE is included in the *UE Multicast MRB to Be Setup at Modify Item IEs* IE, the gNB-DU shall, if supported trigger the establishment of the MBS PTP Forwarding F1-U tunnel. + +If the *Management Based MDT PLMN Modification List* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU 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 [29]. + +If the *Dedicated SI Delivery Indication* IE is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall, if supported, take it into account for the system information delivery to the UE as described in TS 38.331 [8]. + +If the *PDU Set QoS Parameters* IE is included in the *QoS Flow Level QoS Parameters* IE contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, store this information and use it as specified in TS 23.501 [21]. + +If the *InterFrequencyConfig-NoGap* IE is included in the *DU to CU RRC Information* IE contained in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall, if supported, use it as described in TS 38.331 [8]. + +If the *ul-GapFR2-Config* IE is contained in the *DU to CU RRC Information* IE that is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall, if supported, use it as described in TS 38.331 [8]. + +If the *TwoPHRModeMCG* IE or the *TwoPHRModeSCG* IE is contained in the *DU to CU RRC Information* IE that is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall, if supported, use this value as described in TS 38.331 [8]. + +If the *MBSInterestIndication* IE is included in the *CU to DU RRC Information* IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take it into account when configuring resources for the UE. + +If the *ncd-SSB-RedCapInitialBWP-SDT* IE is contained in the *DU to CU RRC Information* IE that is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall, if supported, use it as described in TS 38.331 [8]. + +If the *Network Controlled Repeater Authorized* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, update its authorization information for the UE accordingly. If the *Network Controlled Repeater Authorized* IE is set to "not authorized", the gNB-DU shall, if supported, initiate actions to ensure that the UE is no longer accessing as a Network Controlled Repeater. + +If the *LTM Indicator* IE set to "true" is contained in the *LTM Information Modify* IE included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, consider that the request concerns LTM for the included *SpCell ID* IE and shall include it as the *Requested Target Cell ID* IE in the UE CONTEXT MODIFICATION RESPONSE message. + +If the *Request for Lower Layer Configuration* IE set to "true" is contained within the *Reference Configuration* IE in the *LTM Information Modify* IE included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, include the *CellGroupConfig* IE in the UE CONTEXT MODIFICATION RESPONSE message to provide lower layer configuration for the gNB-CU to generate the LTM reference configuration. + +If the *LTM Reference Configuration* IE is contained within the *Reference Configuration* IE in the *LTM Information Modify* IE included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take it into account for generating the LTM lower layer configuration. + +If the *CSI Resource Configuration* IE is contained in the *LTM Information Modify* IE included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it to generate the LTM CSI reporting configuration(s) in the *CellGroupConfig* for the requested LTM candidate cell. + +If the *LTM Configuration ID Mapping List* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, consider this as the mapping information for the LTM candidate cell(s). + +If the *Request for RACH Configuration* IE set to "true" is contained in the *Early Sync Information Request* IE included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take it into account for early TA acquisition, and include the *RACH Configuration* IE in the UE CONTEXT MODIFICATION RESPONSE message. + +If the *Early Sync Information List* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it as specified in TS 38.401 [4]. + +If the *LTM Cells to be Released List* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, release the configured candidate cells in the list. + +If the *LTM Complete Configuration Indicator* IE set to "complete" is contained in the *LTM Configuration* IE included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall, if supported, consider that the LTM candidate configuration is a complete configuration. + +If the *Direct Path Addition* IE is contained in the *Path Addition Information* IE which is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, consider that the request concerns the direct path addition for the included *SpCell ID* IE as specified in TS 38.401 [4] and regard it as a reconfiguration with sync as defined in TS 38.331 [8]. If the *Indirect Path Addition* IE is contained in the *Path Addition Information* IE, the gNB-DU shall, if supported, consider that the request concerns the indirect path addition for the MP Remote UE using PC5 link and use it as specified in TS 38.401 [4]. If the *N3C Indirect Path Addition* IE is contained in the *Path Addition Information* IE, the gNB-DU shall, if supported, consider that the request concerns the indirect path addition for the MP Remote UE using N3C and use it as specified in TS 38.401 [4]. + +If the *S-NSSAI* IE is included within the *DRB to Be Modified Item* IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, store the corresponding information and replace any existing information. + +#### Interaction with UE Inactivity Notification procedure + +If the *SDT Volume Threshold* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use the information during an SDT transaction to inform the gNB-CU via the UE INACTIVITY NOTIFICATION message as specified in TS 38.401 [4]. + +### 8.3.4.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the UE Context Modification procedure. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST to the gNB-DU, and the gNB-DU responds with a UE CONTEXT MODIFICATION FAILURE.](404924fde6a708196214ae2da3819428_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: UE CONTEXT MODIFICATION REQUEST + Note right of gNB-DU: + gNB-DU-->>gNB-CU: UE CONTEXT MODIFICATION FAILURE + +``` + +Sequence diagram showing the Unsuccessful Operation of the UE Context Modification procedure. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST to the gNB-DU, and the gNB-DU responds with a UE CONTEXT MODIFICATION FAILURE. + +Figure 8.3.4.3-1: UE Context Modification procedure. Unsuccessful operation + +In case none of the requested modifications of the UE context can be successfully performed, the gNB-DU shall respond with the UE CONTEXT MODIFICATION FAILURE message with an appropriate cause value. If the *Conditional Intra-DU Mobility Information* IE was included in the UE CONTEXT MODIFICATION REQUEST message and set to "CHO-initiation", the gNB-DU shall include the received *SpCell ID* IE as the *Requested Target Cell ID* IE in the UE CONTEXT MODIFICATION FAILURE message. + +If the gNB-DU is not able to accept the *SpCell ID* IE in UE CONTEXT MODIFICATION REQUEST message, it shall reply with the UE CONTEXT MODIFICATION FAILURE message. + +If the *Conditional Intra-DU Mobility Information* IE was included and set to "CHO-initiation" or "CHO-replace" or if the *LTM Indicator* IE was included, but the *SpCell ID* IE was not included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall respond with the UE CONTEXT MODIFICATION FAILURE message with an appropriate cause value. + +If the gNB-DU is not able to accept the UE CONTEXT MODIFICATION REQUEST message for mobility because an LTM command has been triggered to the UE, it shall reply with the UE CONTEXT MODIFICATION FAILURE message with an appropriate cause value. + +#### 8.3.4.4 Abnormal Conditions + +If the gNB-DU receives a UE CONTEXT MODIFICATION REQUEST message containing a *E-UTRAN QoS* IE for a GBR QoS DRB but where the *GBR QoS Information* IE is not present, the gNB-DU shall report the establishment of the corresponding DRB as failed in the *DRB Failed to Setup List* IE of the UE CONTEXT MODIFICATION RESPONSE message with an appropriate cause value. + +If the gNB-DU receives a UE CONTEXT MODIFICATION REQUEST message containing a *DRB QoS* IE for a GBR QoS DRB but where the *GBR QoS Flow Information* IE is not present, the gNB-DU shall report the establishment of the corresponding DRBs as failed in the *DRB Failed to Setup List* IE of the UE CONTEXT MODIFICATION RESPONSE message with an appropriate cause value. + +If the *Delay Critical* IE is included in the *Dynamic 5QI Descriptor* IE within the *DRB QoS* IE in the UE CONTEXT MODIFICATION REQUEST message and is set to the value "delay critical" but the *Maximum Data Burst Volume* IE is not present, the gNB-DU shall report the establishment of the corresponding DRB as failed in the *DRB Failed to Setup List* IE of the of the UE CONTEXT MODIFICATION RESPONSE message with an appropriate cause value. + +If one or more candidate cells in the *Candidate Cells To Be Cancelled List* IE included in the UE CONTEXT MODIFICATION REQUEST message were not prepared using the same UE-associated signaling connection, the gNB-DU shall ignore those non-associated candidate cells. + +If more than one of the following IEs, i.e., the *Uplink TxDirectCurrentList Information* IE or the *Uplink TxDirectCurrentTwoCarrierList Information* IE or the *Uplink TxDirectCurrentMoreCarrierList Information* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall consider it as a logical error. + +If one or more LTM cells in the *LTM Cells To Be Released List* IE included in the UE CONTEXT MODIFICATION REQUEST message were not prepared using the same UE-associated signaling connection, the gNB-DU shall ignore those non-associated LTM cells. + +### 8.3.5 UE Context Modification Required (gNB-DU initiated) + +#### 8.3.5.1 General + +The purpose of the UE Context Modification Required procedure is to modify the established UE Context, e.g., modifying and releasing radio bearer resources, or sidelink radio bearer resources or candidate cells in conditional handover or conditional PSCell addition or conditional PSCell change or subsequent CPAC. The procedure uses UE-associated signalling. + +### 8.3.5.2 Successful Operation + +![Sequence diagram illustrating the UE Context Modification Required procedure. The gNB-DU sends a 'UE CONTEXT MODIFICATION REQUIRED' message to the gNB-CU, and the gNB-CU responds with a 'UE CONTEXT MODIFICATION CONFIRM' message.](184d3d9a856c77aae93652f4fe30f752_img.jpg) + +``` + +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: UE CONTEXT MODIFICATION REQUIRED + Note right of gNB-CU: + gNB-CU-->>gNB-DU: UE CONTEXT MODIFICATION CONFIRM + Note left of gNB-DU: + +``` + +Sequence diagram illustrating the UE Context Modification Required procedure. The gNB-DU sends a 'UE CONTEXT MODIFICATION REQUIRED' message to the gNB-CU, and the gNB-CU responds with a 'UE CONTEXT MODIFICATION CONFIRM' message. + +**Figure 8.3.5.2-1: UE Context Modification Required procedure. Successful operation** + +The FIAP UE CONTEXT MODIFICATION REQUIRED message is initiated by the gNB-DU. + +The gNB-CU reports the successful update of the UE context in the UE CONTEXT MODIFICATION CONFIRM message. + +For a given bearer for which PDCP CA duplication was already configured, if two *DL UP TNL Information* IEs are included in UE CONTEXT MODIFICATION REQUIRED message for a DRB, the gNB-CU shall include two *UL UP TNL Information* IEs in UE CONTEXT MODIFICATION CONFIRM message. The gNB-CU and gNB-DU use the *UL UP TNL Information* IEs and *DL UP TNL Information* IEs to support packet duplication for intra-gNB-DU CA as defined in TS 38.470 [2], and the first *UP TNL Information* IE is still for the primary path. + +For a given bearer for which PDCP CA duplication was already configured, if one or two *Additional PDCP Duplication UP TNL Information* IEs are included in the UE CONTEXT MODIFICATION REQUIRED message for a DRB, the gNB-CU shall, if supported, include one or two *Additional PDCP Duplication UP TNL Information* IEs in the UE CONTEXT MODIFICATION CONFIRM message. The gNB-CU and gNB-DU use the *Additional PDCP Duplication UP TNL Information* IEs to support packet duplication for intra-gNB-DU CA as defined in TS 38.470 [2]. + +If the *BH Information* IE is included in the *UL UP TNL Information to be setup List* IE or the *Additional PDCP Duplication TNL List* IE for a DRB, the gNB-DU shall, if supported, use the indicated BAP Routing ID and BH RLC channel for transmission of the corresponding GTP-U packets to the IAB-donor, as specified in TS 38.340 [30]. + +If the *Resource Coordination Transfer Container* IE is included in the UE CONTEXT MODIFICATION REQUIRED, the gNB-CU shall transparently transfer this information for the purpose of resource coordination as described in TS 36.423 [9], TS 38.423 [28]. + +For EN-DC operation, if the gNB-CU includes the *Resource Coordination Transfer Information* IE in the UE CONTEXT MODIFICATION CONFIRM message, the gNB-DU shall, if supported, use it for the purpose of resource coordination. If the gNB-CU received the MeNB Resource Coordination Information as defined in TS 36.423 [9], after completion of UE Context Modification Required procedures, the gNB-CU shall transparently transfer it to the gNB-DU via the *Resource Coordination Transfer Container* IE in the UE CONTEXT MODIFICATION CONFIRM message. The gNB-DU shall use the information received in the *Resource Coordination Transfer Container* IE for reception of MeNB Resource Coordination Information at the gNB acting as secondary node as described in TS 36.423 [9]. If the *Resource Coordination E-UTRA Cell Information* IE is included in the *Resource Coordination Transfer Information* IE, the gNB-DU shall store the information replacing previously received information for the same E-UTRA cell, and use the stored information for the purpose of resource coordination. If the *Ignore PRACH Configuration* IE is present and set to "true" the *E-UTRA PRACH Configuration* IE in the UE CONTEXT MODIFICATION CONFIRM message shall be ignored. + +For NGEN-DC or NE-DC operation, if the gNB-CU includes the *Resource Coordination Transfer Information* IE in the UE CONTEXT MODIFICATION CONFIRM message, the gNB-DU shall, if supported, use it for the purpose of resource coordination. If the gNB-CU received the MR-DC Resource Coordination Information as defined in TS 38.423 + +[28], after completion of UE Context Modification Required procedures, the gNB-CU shall transparently transfer it to the gNB-DU via the *Resource Coordination Transfer Container* IE in the UE CONTEXT MODIFICATION CONFIRM message. The gNB-DU shall use the information received in the *Resource Coordination Transfer Container* IE for reception of MR-DC Resource Coordination Information at the gNB as described in TS 38.423 [28]. + +If the *DU to CU RRC Information* IE is included in the UE CONTEXT MODIFICATION REQUIRED message, the gNB-CU shall perform RRC Reconfiguration as described in TS 38.331 [8]. The *CellGroupConfig* IE shall transparently be signaled to the UE as specified in TS 38.331 [8]. + +If the *ServCellInfoList* IE is included in the *DU to CU RRC Information* IE contained in the UE CONTEXT MODIFICATION REQUIRED message, the gNB-CU shall take it into account to generate the content of inter-node message, i.e., *CG-Config* or *CG-ConfigInfo*, as described in TS 38.331 [8]. + +If the UE CONTEXT MODIFICATION CONFIRM message includes the *Execute Duplication* IE, the gNB-DU shall perform CA based duplication, if configured, for the SRB for the included *RRC-Container* IE. + +If the UE CONTEXT MODIFICATION REQUIRED message contains the *RLC Status* IE, the gNB-CU shall assume that RLC has been reestablished at the gNB-DU and may trigger PDCP data recovery. + +If the *Candidate Cells To Be Cancelled List* IE is included in the UE CONTEXT MODIFICATION REQUIRED message, the gNB-CU shall consider that only the resources reserved for the candidate cells identified by the included NR CGIs and associated to the UE-associated signaling identified by the *gNB-CU UE FIAP ID* IE and the *gNB-CU UE FIAP ID* IE are about to be released by the gNB-DU. + +If the *PC5 RLC Channel Required to be Modified List* IE or the *PC5 RLC Channel Required to be Released List* IE is included in the UE CONTEXT MODIFICATION REQUIRED message and the FIAP-IDs is associated with a U2N Relay UE, the *PC5 RLC Channel Required to be Modified List* IE or the *PC5 RLC Channel Required to be Released List* shall include the *Remote UE Local ID* and correspondingly, the *PC5 RLC Channel Modified Item* IEs in the UE CONTEXT MODIFICATION CONFIRM message shall include the *Remote UE Local ID* IE. + +If the *UE Multicast MRB Required to Be Modified List* IE is included in the UE CONTEXT MODIFICATION REQUIRED message + +- containing for an MRB the *MRB type reconfiguration* IE set to "true" the gNB-CU shall take the *MRB Reconfigured RLC mode* IE into account to reconfigure the UE and to decide whether to request a PDCP status report as specified in TS 38.300 [6] and include the *MBS PTP Retransmission Tunnel Required* IE in the *UE Multicast MRB Confirmed to Be Modified Item* IEs IE. +- containing for an MRB the *Multicast F1-U Context Reference CU* IE the gNB-CU shall, if supported, replace previously provided information by the newly received and take it into account when retrieving MRB progress information. + +If the *LTM Cells To Be Released List* IE is included in the UE CONTEXT MODIFICATION REQUIRED message, the gNB-CU shall, if supported, consider that the configured candidate cells in the list are about to be released by the gNB-DU. + +#### **Interaction with the Multicast Distribution Setup procedure:** + +If the UE CONTEXT MODIFICATION CONFIRM message contains for an MRB the *MBS PTP Retransmission Tunnel Required* IE in the *UE Multicast MRB Confirmed to Be Modified Item* IEs IE the gNB-DU shall, if supported, trigger the Multicast Distribution Setup procedure to setup requested F1-U resources, if applicable. + +### 8.3.5.2A Unsuccessful Operation + +![Sequence diagram for UE Context Modification Required procedure. Unsuccessful operation. The diagram shows two vertical lifelines: gNB-DU on the left and gNB-CU on the right. A solid horizontal arrow points from gNB-DU to gNB-CU with the text 'UE CONTEXT MODIFICATION REQUIRED'. A solid horizontal arrow points from gNB-CU back to gNB-DU with the text 'UE CONTEXT MODIFICATION REFUSE'. Both lifelines end with a thick horizontal bar at the bottom.](51167ecef86d85cdc6dde05a3afb74b8_img.jpg) + +Sequence diagram for UE Context Modification Required procedure. Unsuccessful operation. The diagram shows two vertical lifelines: gNB-DU on the left and gNB-CU on the right. A solid horizontal arrow points from gNB-DU to gNB-CU with the text 'UE CONTEXT MODIFICATION REQUIRED'. A solid horizontal arrow points from gNB-CU back to gNB-DU with the text 'UE CONTEXT MODIFICATION REFUSE'. Both lifelines end with a thick horizontal bar at the bottom. + +**Figure 8.3.5.2A-1: UE Context Modification Required procedure. Unsuccessful operation.** + +In case none of the requested modifications of the UE context can be successfully performed, the gNB-CU shall respond with the UE CONTEXT MODIFICATION REFUSE message with an appropriate cause value. + +### 8.3.5.3 Abnormal Conditions + +If one or more candidate cells in the *Candidate Cells To Be Cancelled List* IE included in the UE CONTEXT MODIFICATION REQUIRED message were not prepared using the same UE-associated signaling connection, the gNB-CU shall ignore those non-associated candidate cells. + +If one or more LTM cells in the *LTM Cells To Be Released List* IE included in the UE CONTEXT MODIFICATION REQUIRED message were not prepared using the same UE-associated signaling connection, the gNB-CU shall ignore those non-associated LTM cells. + +## 8.3.6 UE Inactivity Notification + +### 8.3.6.1 General + +This procedure is initiated by the gNB-DU to indicate the UE activity event. + +The procedure is also used to request the termination of SDT session. + +The procedure uses UE-associated signalling. + +### 8.3.6.2 Successful Operation + +![Sequence diagram for UE Inactivity Notification procedure. The diagram shows two vertical lifelines: gNB-DU on the left and gNB-CU on the right. A solid horizontal arrow points from gNB-DU to gNB-CU with the text 'UE INACTIVITY NOTIFICATION'. Both lifelines end with a thick horizontal bar at the bottom.](fe4312cdd9b42f21c0790c197a9f027c_img.jpg) + +Sequence diagram for UE Inactivity Notification procedure. The diagram shows two vertical lifelines: gNB-DU on the left and gNB-CU on the right. A solid horizontal arrow points from gNB-DU to gNB-CU with the text 'UE INACTIVITY NOTIFICATION'. Both lifelines end with a thick horizontal bar at the bottom. + +**Figure 8.3.6.2-1: UE Inactivity Notification procedure.** + +The gNB-DU initiates the procedure by sending the UE INACTIVITY NOTIFICATION message to the gNB-CU. + +If the *DRB ID* IE is included in the *DRB Activity Item* IE in the UE INACTIVITY NOTIFICATION message, the *DRB Activity* IE shall also be included + +If the gNB-CU receives the *SDT Termination Request* IE in the UE INACTIVITY NOTIFICATION message, the gNB-CU shall, if supported, consider that the termination of the ongoing SDT transaction is requested from the gNB-DU for this UE and act as specified in TS 38.300 [6]. + +### 8.3.6.3 Abnormal Conditions + +Not applicable. + +## 8.3.7 Notify + +### 8.3.7.1 General + +The purpose of the Notify procedure is to enable the gNB-DU to inform the gNB-CU that the QoS of an already established GBR DRB cannot be fulfilled any longer or that it can be fulfilled again. The procedure uses UE-associated signalling. + +### 8.3.7.2 Successful Operation + +![Sequence diagram showing the successful operation of the Notify procedure. The gNB-DU sends a NOTIFY message to the gNB-CU.](f087d3f5d298b3b1634d13ff17879e41_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: NOTIFY + Note right of gNB-CU: +``` + +The diagram illustrates the successful operation of the Notify procedure. It features two vertical lifelines: gNB-DU on the left and gNB-CU on the right. Each lifeline has a solid black horizontal bar at its base. A horizontal arrow labeled 'NOTIFY' points from the gNB-DU lifeline to the gNB-CU lifeline. The gNB-DU lifeline extends above the top of its box, and the gNB-CU lifeline extends above the top of its box. + +Sequence diagram showing the successful operation of the Notify procedure. The gNB-DU sends a NOTIFY message to the gNB-CU. + +**Figure 8.3.7.2-1: Notify procedure. Successful operation.** + +The gNB-DU initiates the procedure by sending a NOTIFY message. + +The NOTIFY message shall contain the list of the GBR DRBs associated with notification control for which the QoS is not fulfilled anymore or for which the QoS is fulfilled again by the gNB-DU. The gNB-DU may also indicate an alternative QoS parameters set which it can currently fulfil in the *Current QoS Parameters Set Index* IE. The gNB-DU may also include the TSC feedback information in the *TSC Traffic Characteristics Feedback* IE. + +Upon reception of the NOTIFY message, the gNB-CU may identify which are the affected PDU sessions and QoS flows. The gNB-CU may inform the 5GC that the QoS for these PDU sessions or QoS flows is not fulfilled any longer or it is fulfilled again. + +### 8.3.7.3 Abnormal Conditions + +Not applicable. + +## 8.3.8 Access Success + +### 8.3.8.1 General + +The purpose of the Access Success procedure is to enable the gNB-DU to inform the gNB-CU of which cell the UE has successfully accessed during conditional handover or conditional PSCell addition or conditional PSCell change or LTM or subsequent CPAC. The procedure uses UE-associated signalling. + +### 8.3.8.2 Successful Operation + +![Sequence diagram showing the successful operation of the Access Success procedure. A gNB-DU sends an ACCESS SUCCESS message to a gNB-CU.](09ec8c855800290ecbc282cfef399c32_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: ACCESS SUCCESS + Note right of gNB-CU: +``` + +The diagram illustrates the successful operation of the Access Success procedure. It features two vertical lifelines: gNB-DU on the left and gNB-CU on the right. Each lifeline has a thick horizontal bar at the bottom. A horizontal arrow labeled 'ACCESS SUCCESS' points from the gNB-DU lifeline to the gNB-CU lifeline. + +Sequence diagram showing the successful operation of the Access Success procedure. A gNB-DU sends an ACCESS SUCCESS message to a gNB-CU. + +**Figure 8.3.8.2-1: Access Success procedure. Successful operation.** + +The gNB-DU initiates the procedure by sending a ACCESS SUCCESS message. + +Upon reception of the ACCESS SUCCESS message, the gNB-CU shall consider that the UE successfully accessed the cell indicated by the included *NR CGI* IE in this gNB-DU and consider all the other CHO preparations or conditional PSCell addition or conditional PSCell change or subsequent CPAC preparations accepted for this UE under the same UE-associated signaling connection in this gNB-DU as cancelled. + +#### **Interaction with other procedure:** + +The gNB-CU may initiate UE Context Release procedure toward the other signalling connections or other candidate gNB-DUs for this UE, if any. + +### 8.3.8.3 Abnormal Conditions + +If the ACCESS SUCCESS message refers to a context that does not exist, the gNB-CU shall ignore the message. + +## 8.3.9 DU-CU Cell Switch Notification + +### 8.3.9.1 General + +The purpose of the DU-CU Cell Switch Notification procedure is to enable the gNB-DU to inform the gNB-CU about the initiation of the cell switch command to the UE. This procedure is also used to transfer the selected TCI state from the gNB-DU to the gNB-CU. The procedure uses UE-associated signalling. + +### 8.3.9.2 Successful Operation + +![Sequence diagram for DU-CU Cell Switch Notification procedure. Successful operation.](c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: DU-CU CELL SWITCH NOTIFICATION + Note right of gNB-CU: +``` + +The diagram shows a sequence of two lifelines: gNB-DU and gNB-CU. Each lifeline is represented by a vertical line with a rectangular box at the top containing the name. Below each box is a thick horizontal bar representing the activation of the entity. A horizontal arrow points from the gNB-DU lifeline to the gNB-CU lifeline, with the text "DU-CU CELL SWITCH NOTIFICATION" centered above it. + +Sequence diagram for DU-CU Cell Switch Notification procedure. Successful operation. + +**Figure 8.3.9.2-1: DU-CU Cell Switch Notification procedure. Successful operation.** + +The gNB-DU initiates the procedure by sending a DU-CU CELL SWITCH NOTIFICATION message. + +Upon reception of the DU-CU CELL SWITCH NOTIFICATION message, the gNB-CU shall, if supported, consider that a cell switch command was sent to the UE where the target cell is indicated by the included *Cell ID* IE. + +### 8.3.9.3 Unsuccessful Operation + +Not applicable. + +### 8.3.9.4 Abnormal Conditions + +Not applicable. + +## 8.3.10 CU-DU Cell Switch Notification + +### 8.3.10.1 General + +The purpose of the CU-DU Cell Switch Notification procedure is to enable the gNB-CU to inform the gNB-DU about the initiation of the cell switch command to the UE. This procedure is also used to transfer the selected TCI state from the gNB-CU to the gNB-DU. The procedure uses UE-associated signalling. + +### 8.3.10.2 Successful Operation + +![Sequence diagram for CU-DU Cell Switch Notification procedure. Successful operation.](c1bfc6f877096c926ff17698a7fb919c_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-CU->>gNB-DU: CU-DU CELL SWITCH NOTIFICATION + Note right of gNB-DU: +``` + +The diagram shows a sequence of two lifelines: gNB-DU and gNB-CU. Each lifeline is represented by a vertical line with a rectangular box at the top containing the name. Below each box is a thick horizontal bar representing the activation of the entity. A horizontal arrow points from the gNB-CU lifeline to the gNB-DU lifeline, with the text "CU-DU CELL SWITCH NOTIFICATION" centered above it. + +Sequence diagram for CU-DU Cell Switch Notification procedure. Successful operation. + +**Figure 8.3.10.2-1: CU-DU Cell Switch Notification procedure. Successful operation.** + +The gNB-CU initiates the procedure by sending a CU-DU CELL SWITCH NOTIFICATION message. + +Upon reception of the CU-DU CELL SWITCH NOTIFICATION message, the gNB-DU shall, if supported, consider that the information indicated the selected TCI state. + +### 8.3.10.3 Unsuccessful Operation + +Not applicable.8.3.10.4 Abnormal Conditions + +Not applicable. + +## 8.4 RRC Message Transfer procedures + +### 8.4.1 Initial UL RRC Message Transfer + +#### 8.4.1.1 General + +The purpose of the Initial UL RRC Message Transfer procedure is to transfer the initial RRC message to the gNB-CU. The procedure uses non-UE-associated signaling. + +#### 8.4.1.2 Successful operation + +![Sequence diagram showing the Initial UL RRC Message Transfer procedure. A gNB-DU sends an INITIAL UL RRC MESSAGE TRANSFER message to a gNB-CU.](ed3c94ac94daffb2c1aee0dd37579f50_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: INITIAL UL RRC MESSAGE TRANSFER + Note right of gNB-CU: +``` + +Sequence diagram showing the Initial UL RRC Message Transfer procedure. A gNB-DU sends an INITIAL UL RRC MESSAGE TRANSFER message to a gNB-CU. + +**Figure 8.4.1.2-1: Initial UL RRC Message Transfer procedure.** + +The gNB-DU initiates the procedure by sending an INITIAL UL RRC MESSAGE TRANSFER. The establishment of the UE-associated logical F1-connection shall be initiated as part of the procedure. + +If neither the *DU to CU RRC Container* IE nor the *Sidelink Configuration Container* IE in the *Sidelink Relay Configuration* IE is included in the INITIAL UL RRC MESSAGE TRANSFER, the gNB-CU should reject the UE under the assumption that the gNB-DU is not able to serve such UE. If the gNB-DU is able to serve the UE, the gNB-DU shall include the *DU to CU RRC Container* IE or the *Sidelink Configuration Container* IE in the *Sidelink Relay Configuration* IE and the gNB-CU shall configure the UE as specified in TS 38.331 [8]. The gNB-DU shall not include the *ReconfigurationWithSync* field in the *CellGroupConfig* IE as defined in TS 38.331 [8] of the *DU to CU RRC Container* IE. + +If the *SUL Access Indication* IE is included in the INITIAL UL RRC MESSAGE TRANSFER, the gNB-CU shall consider that the UE has performed access on SUL carrier. + +If the *RRC-Container-RRCSetupComplete* IE is included in the INITIAL UL RRC MESSAGE TRANSFER, the gNB-CU shall take it into account as specified in TS 38.401 [4]. + +If the *NR RedCap UE Indication* IE is included in the INITIAL UL RRC MESSAGE TRANSFER message, the gNB-CU shall, if supported, consider that the accessing UE is a RedCap UE. + +If the *NR eRedCap UE Indication* IE is included in the INITIAL UL RRC MESSAGE TRANSFER message, the gNB-CU shall, if supported, consider that the accessing UE is an eRedCap UE. + +If the *SDT Information* IE is included in the INITIAL UL RRC MESSAGE TRANSFER, the gNB-CU shall, if supported, consider that the UE is accessing for SDT as defined in TS 38.300 [6], and may use the information contained in the *SDT Assistant Information* IE, if any, for context retrieval. + +If the *Sidelink Relay Configuration* IE is included in the INITIAL UL RRC MESSAGE TRANSFER, the gNB-CU shall, if supported, consider that the UE is a NR ProSe Layer-2 U2N Remote UE identified by the *Remote UE Local ID* IE, and it is connected to the U2N Relay UE indicated by the *gNB-DU UE FIAP ID of Relay UE* IE. + +#### 8.4.1.3 Abnormal Conditions + +Not applicable. + +### 8.4.2 DL RRC Message Transfer + +#### 8.4.2.1 General + +The purpose of the DL RRC Message Transfer procedure is to transfer an RRC message The procedure uses UE-associated signalling. + +#### 8.4.2.2 Successful operation + +![Sequence diagram showing the DL RRC Message Transfer procedure. A gNB-CU sends a DL RRC MESSAGE TRANSFER message to a gNB-DU. The gNB-DU is represented by a vertical line with a thick horizontal bar at the bottom, and the gNB-CU is represented by a vertical line with a thick horizontal bar at the bottom. The message is shown as a horizontal arrow pointing from the gNB-CU to the gNB-DU.](a471382fa73185ead4f9b83e3e64ee96_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + Note right of gNB-CU: + gNB-CU->>gNB-DU: DL RRC MESSAGE TRANSFER + +``` + +Sequence diagram showing the DL RRC Message Transfer procedure. A gNB-CU sends a DL RRC MESSAGE TRANSFER message to a gNB-DU. The gNB-DU is represented by a vertical line with a thick horizontal bar at the bottom, and the gNB-CU is represented by a vertical line with a thick horizontal bar at the bottom. The message is shown as a horizontal arrow pointing from the gNB-CU to the gNB-DU. + +**Figure 8.4.2.2-1: DL RRC Message Transfer procedure** + +The gNB-CU initiates the procedure by sending a DL RRC MESSAGE TRANSFER message. If a UE-associated logical F1-connection exists, the DL RRC MESSAGE TRANSFER message shall contain the *gNB-DU UE FIAP ID* IE, which should be used by gNB-DU to lookup the stored UE context. If no UE-associated logical F1-connection exists, the UE-associated logical F1-connection shall be established at reception of the DL RRC MESSAGE TRANSFER message. + +If the *Index to RAT/Frequency Selection Priority* IE is included in the DL RRC MESSAGE TRANSFER, the gNB-DU may use it for RRM purposes. If the *Additional RRM Policy Index* IE is included in the DL RRC MESSAGE TRANSFER, the gNB-DU may use it for RRM purposes. + +The DL RRC MESSAGE TRANSFER message shall include, if available, the *old gNB-DU UE FIAP ID* IE so that the gNB-DU can retrieve the existing UE context in RRC connection reestablishment procedure, as defined in TS 38.401 [4]. + +The DL RRC MESSAGE TRANSFER message shall include, if SRB duplication is activated, the *Execute Duplication* IE, so that the gNB-DU can perform CA based duplication for the SRB. + +If the gNB-DU identifies the UE-associated logical F1-connection by the *gNB-DU UE FIAP ID* IE in the DL RRC MESSAGE TRANSFER message and the *old gNB-DU UE FIAP ID* IE is included, it shall release the old gNB-DU UE FIAP ID and the related configurations associated with the old gNB-DU UE FIAP ID. + +If the *UE Context not retrievable* IE set to "true" is included in the DL RRC MESSAGE TRANSFER, the DL RRC MESSAGE TRANSFER may contain the *Redirected RRC message* IE and use it as specified in TS 38.401 [4]. + +If the *UE Context not retrievable* IE set to "true" is included in the DL RRC MESSAGE TRANSFER, the DL RRC MESSAGE TRANSFER may contain the *PLMN Assistance Info for Network Sharing* IE, if available at the gNB-CU and may use it as specified in TS 38.401 [4]. + +If the DL RRC MESSAGE TRANSFER message contains the *New gNB-CU UE FIAP ID* IE, the gNB-DU shall, if supported, replace the value received in the *gNB-CU UE FIAP ID* IE by the value of the *New gNB-CU UE FIAP ID* and use it for further signalling. + +If the DL RRC MESSAGE TRANSFER contains the *SRB Mapping Info* IE, the gNB-DU shall, if supported, use it for the Remote UE's SRB0 or SRB1 transfer. + +#### Interactions with UE Context Release Request procedure: + +If the *UE Context not retrievable* IE set to "true" is included in the DL RRC MESSAGE TRANSFER, the gNB-DU may trigger the UE Context Release Request procedure, as specified in TS 38.401 [4]. + +### 8.4.2.3 Abnormal Conditions + +Not applicable. + +## 8.4.3 UL RRC Message Transfer + +### 8.4.3.1 General + +The purpose of the UL RRC Message Transfer procedure is to transfer an RRC message as an UL PDCP-PDU to the gNB-CU. The procedure uses UE-associated signalling. + +### 8.4.3.2 Successful operation + +![Sequence diagram of UL RRC Message Transfer procedure](9400925a53bd0c7e071258c54cb15c15_img.jpg) + +A sequence diagram illustrating the UL RRC Message Transfer procedure. It features two vertical lifelines: gNB-DU on the left and gNB-CU on the right. Each lifeline starts with a rectangular box containing its name and ends with a thick horizontal bar. A single horizontal arrow points from the gNB-DU lifeline to the gNB-CU lifeline, with the text "UL RRC MESSAGE TRANSFER" centered above it. + +Sequence diagram of UL RRC Message Transfer procedure + +Figure 8.4.3.2-1: UL RRC Message Transfer procedure + +The gNB-DU initiates the procedure by sending a UL RRC MESSAGE TRANSFER message. When the gNB-DU has received from the radio interface an RRC message to which a UE-associated logical F1-connection for the UE exists, the gNB-DU shall send the UL RRC MESSAGE TRANSFER message to the gNB-CU including the RRC message as a *RRC-Container* IE. + +If the *Selected PLMN ID* IE is contained in the UL RRC MESSAGE TRANSFER message, the gNB-CU may use it as specified in TS 38.401 [4]. + +If the UL RRC MESSAGE TRANSFER message contains the *New gNB-DU UE FIAP ID* IE, the gNB-CU shall, if supported, replace the value received in the *gNB-DU UE FIAP ID* IE by the value of the *New gNB-DU UE FIAP ID* and use it for further signalling. + +### 8.4.3.3 Abnormal Conditions + +Not applicable. + +## 8.4.4 RRC Delivery Report + +### 8.4.4.1 General + +The purpose of the RRC Delivery Report procedure is to transfer to the gNB-CU information about successful delivery of DL PDCP-PDUs including RRC messages. The procedure uses UE-associated signalling. + +RRC DELIVERY REPORT + +### 8.4.4.2 Successful operation + +![Sequence diagram of the RRC Delivery Report procedure. It shows two vertical lifelines: gNB-DU on the left and gNB-CU on the right. Each lifeline has a rectangular box at the top and a thick horizontal bar at the bottom. A single horizontal arrow points from the gNB-DU lifeline to the gNB-CU lifeline, representing the RRC DELIVERY REPORT message.](c686c005fef31702c109f5d9dd975413_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: RRC DELIVERY REPORT + Note right of gNB-CU: + Note left of gNB-DU: + Note right of gNB-CU: +``` + +Sequence diagram of the RRC Delivery Report procedure. It shows two vertical lifelines: gNB-DU on the left and gNB-CU on the right. Each lifeline has a rectangular box at the top and a thick horizontal bar at the bottom. A single horizontal arrow points from the gNB-DU lifeline to the gNB-CU lifeline, representing the RRC DELIVERY REPORT message. + +**Figure 8.4.4.2-1: RRC Delivery Report procedure.** + +The gNB-DU initiates the procedure by sending an RRC DELIVERY REPORT message. When the gNB-DU has successfully delivered an RRC message to the UE for which the gNB-CU has requested a delivery report, the gNB-DU shall send the RRC DELIVERY REPORT message to the gNB-CU containing the *RRC Delivery Status* IE and the *SRB ID* IE. + +### 8.4.4.3 Abnormal Conditions + +Not applicable. + +## 8.5 Warning Message Transmission Procedures + +### 8.5.1 Write-Replace Warning + +#### 8.5.1.1 General + +The purpose of Write-Replace Warning procedure is to start or overwrite the broadcasting of warning messages. The procedure uses non UE-associated signalling. + +### 8.5.1.2 Successful Operation + +![Sequence diagram showing the successful operation of the Write-Replace Warning procedure between gNB-DU and gNB-CU.](b30e390cb591b39482fe7ecd4c4cd84b_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: WRITE-REPLACE WARNING REQUEST + Note right of gNB-CU: + gNB-DU-->>gNB-CU: WRITE-REPLACE WARNING RESPONSE + Note right of gNB-DU: + +``` + +The diagram illustrates a sequence of two messages between the gNB-CU and the gNB-DU. The gNB-CU sends a 'WRITE-REPLACE WARNING REQUEST' message to the gNB-DU. The gNB-DU then responds with a 'WRITE-REPLACE WARNING RESPONSE' message back to the gNB-CU. Both entities are represented by rectangular boxes with lifelines extending downwards, and the messages are shown as horizontal arrows between these lifelines. + +Sequence diagram showing the successful operation of the Write-Replace Warning procedure between gNB-DU and gNB-CU. + +**Figure 8.5.1.2-1: Write-Replace Warning procedure: successful operation** + +The gNB-CU initiates the procedure by sending a WRITE-REPLACE WARNING REQUEST message to the gNB-DU. + +Upon receipt of the WRITE-REPLACE WARNING REQUEST message, the gNB-DU shall prioritise its resources to process the warning message. + +The gNB-DU acknowledges the WRITE-REPLACE WARNING REQUEST message by sending a WRITE-REPLACE WARNING RESPONSE message to the gNB-CU. + +Upon receipt of the WRITE-REPLACE WARNING REQUEST message, the gNB-DU shall include the *Dedicated SI Delivery Needed UE List* IE in the WRITE-REPLACE WARNING RESPONSE message for UEs that are unable to receive system information from broadcast. + +If *Dedicated SI Delivery Needed UE List* IE is contained in the WRITE-REPLACE WARNING RESPONSE message, the gNB-CU should take it into account when informing the UE of the updated system information via the dedicated RRC message. + +Upon reception of the *Notification Information* IE in the *PWS System Information* IE in the WRITE-REPLACE WARNING REQUEST message, the gNB-DU shall use this information to avoid that duplications trigger new broadcast or replace existing broadcast. + +If the gNB-DU receives a WRITE-REPLACE WARNING REQUEST message with the *Notification Information* IE in the *PWS System Information* IE which are different from those of ongoing broadcast warning messages, and if the *SIB Type* IE is set to "8", the gNB-DU shall broadcast the received warning message concurrently with other ongoing messages. + +If the gNB-DU receives a WRITE-REPLACE WARNING REQUEST message with the *Notification Information* IE in the *PWS System Information* IE which are different from those of ongoing broadcast warning messages, and if the *SIB Type* IE is set to the value other than '8', the gNB-DU shall use the newly received one to replace the ongoing broadcast warning message with the same value of *SIB Type* IE. + +If the *SIB Type* IE in the *PWS System Information* IE in the WRITE-REPLACE WARNING REQUEST message is set to "8" and if a value "0" is received in the *Number of Broadcast Requested* IE and if the *Repetition Period* IE is different from "0", the gNB-DU shall broadcast the received warning message indefinitely. + +If *Additional SIB Message List* IE is included in *PWS System Information* IE, the gNB-DU shall store all SIB message(s) in *PWS System Information* IE, and consider that the first segment of public warning message is included in *SIB message* IE, and the remaining segments are listed in *Additional SIB Message List* IE in segmentation sequence order. + +### 8.5.1.3 Unsuccessful Operation + +Not applicable. + +#### 8.5.1.4 Abnormal Conditions + +If the gNB-DU receives a WRITE-REPLACE WARNING REQUEST message which does not include the *Notification Information* IE in the *PWS System Information* IE, the gNB-DU shall consider it as a logical error. + +### 8.5.2 PWS Cancel + +#### 8.5.2.1 General + +The purpose of the PWS Cancel procedure is to cancel an already ongoing broadcast of a warning message. The procedure uses non UE-associated signalling. + +#### 8.5.2.2 Successful Operation + +![Sequence diagram of the PWS Cancel procedure: successful operation. The diagram shows two vertical lifelines: gNB-DU on the left and gNB-CU on the right. A horizontal arrow labeled 'PWS CANCEL REQUEST' points from the gNB-CU to the gNB-DU. A horizontal arrow labeled 'PWS CANCEL RESPONSE' points from the gNB-DU to the gNB-CU. Both lifelines end with a thick horizontal bar at the bottom.](19499072f755b22d0a231123f75fa477_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: PWS CANCEL REQUEST + gNB-DU-->>gNB-CU: PWS CANCEL RESPONSE + Note right of gNB-CU: +``` + +Sequence diagram of the PWS Cancel procedure: successful operation. The diagram shows two vertical lifelines: gNB-DU on the left and gNB-CU on the right. A horizontal arrow labeled 'PWS CANCEL REQUEST' points from the gNB-CU to the gNB-DU. A horizontal arrow labeled 'PWS CANCEL RESPONSE' points from the gNB-DU to the gNB-CU. Both lifelines end with a thick horizontal bar at the bottom. + +**Figure 8.5.2.2-1: PWS Cancel procedure: successful operation** + +The gNB-CU initiates the procedure by sending a PWS CANCEL REQUEST message to the gNB-DU. + +The gNB-DU shall acknowledge the PWS CANCEL REQUEST message by sending the PWS CANCEL RESPONSE message. + +If the *Cancel-All Warning Messages Indicator* IE is present in the PWS CANCEL REQUEST message, then the gNB-DU shall stop broadcasting and discard all warning messages for the area as indicated in the *Cell Broadcast To Be Cancelled List* IE or in all the cells of the gNB-DU if the *Cell Broadcast To Be Cancelled List* IE is not included. The gNB-DU shall acknowledge the PWS CANCEL REQUEST message by sending the PWS CANCEL RESPONSE message, and shall, if there is area to report where an ongoing broadcast was stopped successfully, include the *Cell Broadcast Cancelled List* IE with the *Number of Broadcasts* IE set to 0. + +If the *Cell Broadcast To Be Cancelled List* IE is not included in the PWS CANCEL REQUEST message, the gNB-DU shall stop broadcasting and discard the warning message identified by the *Message Identifier* IE and the *Serial Number* IE in the *Notification Information* IE in all of the cells in the gNB-DU. + +If the *Notification Information* IE is included in the PWS CANCEL REQUEST, the gNB-DU shall cancel broadcast of the public warning message identified by the *Notification Information* IE. + +If an area included in the *Cell Broadcast To Be Cancelled List* IE in the PWS CANCEL REQUEST message does not appear in the *Cell Broadcast Cancelled List* IE in the PWS CANCEL RESPONSE, the gNB-CU shall consider that the gNB-DU had no ongoing broadcast to stop for the public warning message identified, if present, by the *Notification Information* IE in that area. + +If the *Cell Broadcast Cancelled List* IE is not included in the PWS CANCEL RESPONSE message, the gNB-CU shall consider that the gNB-DU had no ongoing broadcast to stop for the public warning message identified, if present, by the *Notification Information* IE. + +### 8.5.2.3 Unsuccessful Operation + +If the gNB-DU receives a PWS CANCEL REQUEST message which contains neither the *Cancel-all Warning Messages Indicator* IE nor the *Notification Information* IE, the gNB-DU shall consider it as a logical error. + +### 8.5.2.4 Abnormal Conditions + +Not applicable. + +## 8.5.3 PWS Restart Indication + +### 8.5.3.1 General + +The purpose of PWS Restart Indication procedure is to inform the gNB-CU that PWS information for some or all cells of the gNB-DU are available for reloading from the CBC if needed. The procedure uses non UE-associated signalling. + +### 8.5.3.2 Successful Operation + +![Sequence diagram showing the PWS restart indication procedure. A gNB-DU sends a PWS RESTART INDICATION message to a gNB-CU.](327cb947c7270b695bdd1cab5e8d72c0_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: PWS RESTART INDICATION + Note right of gNB-CU: +``` + +The diagram illustrates a sequence of two vertical lifelines. The left lifeline is labeled 'gNB-DU' and the right is labeled 'gNB-CU'. Both labels are in rectangular boxes. A horizontal arrow points from the gNB-DU lifeline to the gNB-CU lifeline, with the text 'PWS RESTART INDICATION' centered above the arrow. Each lifeline has a thick horizontal bar at its base. + +Sequence diagram showing the PWS restart indication procedure. A gNB-DU sends a PWS RESTART INDICATION message to a gNB-CU. + +**Figure 8.5.3.2-1: PWS restart indication** + +The gNB-DU initiates the procedure by sending a PWS RESTART INDICATION message to the gNB-CU. + +### 8.5.3.3 Abnormal Conditions + +Not applicable. + +## 8.5.4 PWS Failure Indication + +### 8.5.4.1 General + +The purpose of the PWS Failure Indication procedure is to inform the gNB-CU that ongoing PWS operation for one or more cells of the gNB-DU has failed. The procedure uses non UE-associated signalling. + +### 8.5.4.2 Successful Operation + +![Sequence diagram for PWS failure indication](b550cb515008f6bab9f295adcb28b5f6_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: PWS FAILURE INDICATION + Note right of gNB-CU: +``` + +A sequence diagram showing the interaction between gNB-DU and gNB-CU. The gNB-DU sends a 'PWS FAILURE INDICATION' message to the gNB-CU. Both entities are represented by boxes with lifelines extending downwards, ending in thick horizontal bars. + +Sequence diagram for PWS failure indication + +**Figure 8.5.4.2-1: PWS failure indication** + +The gNB-DU initiates the procedure by sending a PWS FAILURE INDICATION message to the gNB-CU. + +### 8.5.4.3 Abnormal Conditions + +Not applicable. + +## 8.6 System Information Procedures + +### 8.6.1 System Information Delivery + +#### 8.6.1.1 General + +The purpose of the System Information Delivery procedure is to command the gNB-DU to broadcast the requested one or several *SystemInformation* messages including the Other SI as requested by the gNB-CU. The procedure uses non-UE associated signalling. + +#### 8.6.1.2 Successful Operation + +![Sequence diagram for System Information Delivery procedure. Successful operation.](457a77ed21f00d697e7d1d0b54041ca2_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-CU->>gNB-DU: SYSTEM INFORMATION DELIVERY COMMAND + Note right of gNB-DU: +``` + +A sequence diagram showing the interaction between gNB-DU and gNB-CU. The gNB-CU sends a 'SYSTEM INFORMATION DELIVERY COMMAND' message to the gNB-DU. Both entities are represented by boxes with lifelines extending downwards, ending in thick horizontal bars. + +Sequence diagram for System Information Delivery procedure. Successful operation. + +**Figure 8.6.1.2-1: System Information Delivery procedure. Successful operation.** + +The gNB-CU initiates the procedure by sending a SYSTEM INFORMATION DELIVERY COMMAND message to the gNB-DU. + +Upon reception of the SYSTEM INFORMATION DELIVERY COMMAND message, the gNB-DU shall broadcast the requested one or several *SystemInformation* messages, including the Other SI, indicated by the *SIType List* IE, and if the UE corresponding to the *confirmed UE ID* IE is not in RRC connected state, delete the UE context, if any. + +**Interactions with gNB-DU Configuration Update procedure:** + +Upon reception of SYSTEM INFORMATION DELIVERY COMMAND message, the gNB-DU Configuration Update procedure may be performed , and as part of such procedure the gNB-DU shall include the *Dedicated SI Delivery Needed UE List* IE in GNB-DU CONFIGURATION UPDATE message for UEs that are unable to receive system information from broadcast. + +### 8.6.1.3 Abnormal Conditions + +Not applicable. + +## 8.7 Paging procedures + +### 8.7.1 Paging + +#### 8.7.1.1 General + +The purpose of the Paging procedure is used to provide the paging information to enable the gNB-DU to page a UE. The procedure uses non-UE associated signalling. + +#### 8.7.1.2 Successful Operation + +![Sequence diagram showing the successful operation of the paging procedure. A gNB-CU sends a PAGING message to a gNB-DU. The gNB-DU then performs paging of the UE in cells which belong to cells as indicated in the Paging Cell List IE.](43437211ce989e9da795fecc0d499c05_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: PAGING + Note right of gNB-DU: +``` + +Sequence diagram showing the successful operation of the paging procedure. A gNB-CU sends a PAGING message to a gNB-DU. The gNB-DU then performs paging of the UE in cells which belong to cells as indicated in the Paging Cell List IE. + +**Figure 8.7.1.2-1: Paging procedure. Successful operation.** + +The gNB-CU initiates the procedure by sending a PAGING message. + +The *Paging DRX* IE may be included in the PAGING message, and if present the gNB-DU may use it to determine the final paging cycle for the UE. + +The *Paging Priority* IE may be included in the PAGING message, and if present the gNB-DU may use it according to TS 23.501 [21]. + +At the reception of the PAGING message, the gNB-DU shall perform paging of the UE in cells which belong to cells as indicated in the *Paging Cell List* IE. + +The *Paging Origin* IE may be included in the PAGING message, and if present the gNB-DU shall transfer it to the UE. + +The *RAN UE Paging DRX* IE may be included in the PAGING message, and if present the gNB-DU may use it according to TS 38.304 [24]. + +The *CN UE Paging DRX* IE may be included in the PAGING message, and if present the gNB-DU may use it according to TS 38.304 [24]. + +The *NR Paging eDRX Information* IE may be included in the PAGING message, and if present the gNB-DU may use it according to TS 38.304 [24]. + +The *NR Paging eDRX Information for RRC INACTIVE* IE may be included in the PAGING message, and if present the gNB-DU shall, if supported, use it according to TS 38.304 [24]. + +The *Paging Cause* IE may be included in the PAGING message. If present the gNB-DU shall, if supported, send it to UE according to TS 38.331 [8]. + +The *PEIPS Assistance Information* IE may be included in the PAGING message, and if present the gNB-DU shall, if supported, use it for paging subgrouping of the UE, as specified in TS 38.300 [6]. + +The *UEID Subgrouping Support Indication* IE may be included in *UE Paging Capability* IE in the PAGING message, and if present the gNB-DU shall, if supported, use it for paging subgrouping of the UE, as specified in TS 38.300 [6]. + +The *RedCap Indication* IE may be included in the *UE Paging Capability* IE in the PAGING message, and if present the gNB-DU shall, if supported, use it for paging of RedCap UE or eRedCap UE. + +The *Last Used Cell Indication* IE may be included in the *Paging Cell Item IEs* IE of the PAGING message, and if present the gNB-DU shall, if supported, consider the cell identified by the *NR CGI* IE as the last used cell of the paged UE, and use it as specified in TS 38.331 [8]. + +The *Recommended SSBs List* IE may be included in the *Paging Cell Item IEs* IE of the PAGING message, and if present the gNB-DU shall, if supported, use it to send the paging message over the indicated SSB beams. + +The *PEI Subgrouping Support Indication* IE may be included in the *Paging Cell Item IEs* IE in the PAGING message, and if present the gNB-DU shall, if supported, consider that the cell identified by the *NR CGI* IE is supported by the UE to receive the paging early indication as described in TS 38.300 [6] and TS 38.304 [24]. + +The *UE Paging Capability* IE may be included in the PAGING message, and if present the gNB-DU shall, if supported, take it into account when paging the UE. + +The *Extended UE Identity Index Value* IE may be included in the PAGING message, and if present the gNB-DU shall, if supported, use it according to TS 38.304 [24]. + +The *Hashed UE Identity Index Value* IE may be included in the PAGING message, and if present the gNB-DU shall, if supported, use it according to TS 38.304 [24]. + +The *MT-SDT Information* IE may be included in the PAGING message. If present the gNB-DU shall, if supported, use it for MT-SDT paging as specified in TS 38.331 [8]. + +The *NR Paging Long eDRX Information for RRC INACTIVE* IE may be included in the PAGING message, and if present, the gNB-DU shall, if supported, use it according to TS 38.304 [24]. + +### 8.7.1.3 Abnormal Conditions + +Not applicable. + +## 8.8 Trace Procedures + +### 8.8.1 Trace Start + +#### 8.8.1.1 General + +The purpose of the Trace Start procedure is to allow the gNB-CU to request the gNB-DU to initiate a trace session for a UE. The procedure uses UE-associated signalling. + +### 8.8.1.2 Successful Operation + +![Sequence diagram for Trace start procedure: Successful Operation. The gNB-CU sends a TRACE START message to the gNB-DU.](40b80ef077f6151a9fbb593b8ad4864d_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: TRACE START + Note right of gNB-DU: + Note left of gNB-DU: +``` + +Sequence diagram for Trace start procedure: Successful Operation. The gNB-CU sends a TRACE START message to the gNB-DU. + +**Figure 8.8.1.2-1: Trace start procedure: Successful Operation.** + +The gNB-CU initiates the procedure by sending a TRACE START message. Upon reception of the TRACE START message, the gNB-DU shall initiate the requested trace session for the requested UE, as described in TS 32.422 [29]. In particular, the gNB-DU shall, if supported: + +- if the *Trace Activation* IE includes the *MDT Activation* IE set to "Immediate MDT and Trace" initiate the requested trace session and MDT session as described in TS 32.422 [29]; +- if the *Trace Activation* IE includes the *MDT Activation* IE set to "Immediate MDT Only" initiate the requested MDT session as described in TS 32.422 [29] and the gNB-DU shall ignore *Interfaces To Trace* IE, and *Trace Depth* IE; + +### 8.8.1.3 Abnormal Conditions + +Void. + +## 8.8.2 Deactivate Trace + +### 8.8.2.1 General + +The purpose of the Deactivate Trace procedure is to allow the gNB-CU to request the gNB-DU to stop the trace session for the indicated trace reference. The procedure uses UE-associated signalling. + +### 8.8.2.2 Successful Operation + +![Sequence diagram for Deactivate trace procedure: Successful Operation. The gNB-CU sends a DEACTIVATE TRACE message to the gNB-DU.](9dee6d7157e1d03eb09a30a9aa81cc11_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: DEACTIVATE TRACE + Note right of gNB-DU: + Note left of gNB-DU: +``` + +Sequence diagram for Deactivate trace procedure: Successful Operation. The gNB-CU sends a DEACTIVATE TRACE message to the gNB-DU. + +**Figure 8.8.2.2-1: Deactivate trace procedure: Successful Operation** + +The gNB-CU initiates the procedure by sending a DEACTIVATE TRACE message. Upon reception of the DEACTIVATE TRACE message, the gNB-DU shall stop the trace session for the indicated trace reference contained in the *Trace ID* IE, as described in TS 32.422 [29]. + +### 8.8.2.3 Abnormal Conditions + +Void. + +## 8.8.3 Cell Traffic Trace + +### 8.8.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. The procedure uses UE-associated signalling. + +### 8.8.3.2 Successful Operation + +![Sequence diagram showing the successful operation of the Cell Traffic Trace procedure. A gNB-DU sends a CELL TRAFFIC TRACE message to a gNB-CU.](56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: CELL TRAFFIC TRACE + Note right of gNB-CU: +``` + +Sequence diagram showing the successful operation of the Cell Traffic Trace procedure. A gNB-DU sends a CELL TRAFFIC TRACE message to a gNB-CU. + +**Figure 8.8.3.2-1: Cell Traffic Trace procedure. Successful operation.** + +The procedure is initiated with a CELL TRAFFIC TRACE message sent from the gNB-DU to the gNB-CU. + +If the *Privacy Indicator* IE is included in the message, the gNB-CU shall store the information so that it can be transferred towards the AMF. + +### 8.8.3.3 Abnormal Conditions + +Void. + +## 8.9 Radio Information Transfer procedures + +### 8.9.1 DU-CU Radio Information Transfer + +#### 8.9.1.1 General + +The purpose of the DU-CU Radio Information Transfer procedure is to transfer radio-related information from the gNB-DU to the gNB-CU. The procedure uses non-UE-associated signalling. + +### 8.9.1.2 Successful operation + +![Sequence diagram for DU-CU Radio Information Transfer procedure. A gNB-DU (left) sends a message to a gNB-CU (right).](4b2dd266b605b2f31a8759f802637301_img.jpg) + +A sequence diagram illustrating the DU-CU Radio Information Transfer procedure. It features two vertical lifelines: gNB-DU on the left and gNB-CU on the right. Each lifeline is represented by a black rectangle at the top and a horizontal bar at the bottom. A single horizontal arrow points from the gNB-DU lifeline to the gNB-CU lifeline, indicating the transfer of information. + +Sequence diagram for DU-CU Radio Information Transfer procedure. A gNB-DU (left) sends a message to a gNB-CU (right). + +**Figure 8.9.1.2-1: DU-CU Radio Information Transfer procedure.** + +The gNB-DU initiates the procedure by sending the DU-CU RADIO INFORMATION TRANSFER message to the gNB-CU. + +The gNB-CU considers that the *RIM-RS Detection Status* IE indicates the RIM-RS detection status of the cell identified by *Aggressor Cell ID* IE. + +### 8.9.1.3 Abnormal Conditions + +Not applicable. + +## 8.9.2 CU-DU Radio Information Transfer + +### 8.9.2.1 General + +The purpose of the CU-DU Radio Information Transfer procedure is to transfer radio-related information from the gNB-CU to the gNB-DU. The procedure uses non-UE-associated signalling. + +### 8.9.2.2 Successful operation + +![Sequence diagram for CU-DU Radio Information Transfer procedure. A gNB-CU (right) sends a message to a gNB-DU (left).](0c1feadc9b1a8d6535ef5a0604c0004f_img.jpg) + +A sequence diagram illustrating the CU-DU Radio Information Transfer procedure. It features two vertical lifelines: gNB-CU on the right and gNB-DU on the left. Each lifeline is represented by a black rectangle at the top and a horizontal bar at the bottom. A single horizontal arrow points from the gNB-CU lifeline to the gNB-DU lifeline, indicating the transfer of information. + +Sequence diagram for CU-DU Radio Information Transfer procedure. A gNB-CU (right) sends a message to a gNB-DU (left). + +**Figure 8.9.2.2-1: CU-DU Radio Information Transfer procedure.** + +The gNB-CU initiates the procedure by sending the CU-DU RADIO INFORMATION TRANSFER message to the gNB-DU. The gNB-DU considers that the *RIM-RS Detection Status* IE indicates the detection status of RIM-RS associated with *Victim gNB Set ID* IE. + +### 8.9.2.3 Abnormal Conditions + +Not applicable. + +## 8.10 IAB Procedures + +### 8.10.0 General + +In this version of the specification, the IAB procedures are used to configure IAB-donor-DU or IAB-DU. + +NOTE: The IAB procedures are applicable for IAB-nodes and IAB-donor-DU, where the term "gNB-DU" applies to IAB-DU and IAB-donor-DU, and the term "gNB-CU" applies to IAB-donor-CU, unless otherwise specified. + +### 8.10.1 BAP Mapping Configuration + +#### 8.10.1.1 General + +The BAP Mapping Configuration Procedure is initiated by the gNB-CU to configure the DL/UL routing information and/or traffic mapping information needed for the gNB-DU. The procedure uses non-UE associated signalling. + +NOTE: Implementation shall ensure the avoidance of potential race conditions, i.e. it shall ensure that conflicting traffic mapping configurations are not concurrently performed using the non-UE-associated BAP Mapping Configuration procedure and the UE-associated UE Context Management procedures. + +#### 8.10.1.2 Successful Operation + +![Sequence diagram showing the BAP Mapping Configuration procedure between gNB-DU and gNB-CU. The gNB-CU sends a BAP MAPPING CONFIGURATION message to the gNB-DU, and the gNB-DU responds with a BAP MAPPING CONFIGURATION ACKNOWLEDGE message.](461ef997feb933486effd3b0d3504016_img.jpg) + +``` + +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-CU->>gNB-DU: BAP MAPPING CONFIGURATION + gNB-DU-->>gNB-CU: BAP MAPPING CONFIGURATION ACKNOWLEDGE + Note right of gNB-CU: + +``` + +Sequence diagram showing the BAP Mapping Configuration procedure between gNB-DU and gNB-CU. The gNB-CU sends a BAP MAPPING CONFIGURATION message to the gNB-DU, and the gNB-DU responds with a BAP MAPPING CONFIGURATION ACKNOWLEDGE message. + +Figure 8.10.1.2-1: BAP Mapping Configuration procedure: Successful Operation + +The gNB-CU initiates the procedure by sending BAP MAPPING CONFIGURATION message to the gNB-DU. The gNB-DU replies to the gNB-CU with BAP MAPPING CONFIGURATION ACKNOWLEDGE. + +If *BH Routing Information Added List* IE is included in the BAP MAPPING CONFIGURATION message, the gNB-DU shall, if supported, store the BH routing information from this IE and use it for DL/UL traffic forwarding as specified in TS 38.340 [30]. If *BH Routing Information Added List* IE contains information for an existing BAP Routing ID, the gNB-DU shall, if supported, replace the previously stored routing information for this BAP Routing ID with the corresponding information in the *BH Routing Information Added List* IE. + +If *BH Routing Information Removed List* IE is included in the BAP MAPPING CONFIGURATION message, the gNB-DU shall, if supported, remove the BH routing information according to such IE. + +If the *Traffic Mapping Information* IE is included in the BAP MAPPING CONFIGURATION message, the gNB-DU shall, if supported, process the *Traffic Mapping Information* IE as follows: + +- if the *IP to layer2 Traffic Mapping Info* IE is included, the gNB-DU shall store the mapping information contained in the *IP to layer2 Traffic Mapping Info To Add* IE, if present, and remove the previously stored mapping information as indicated by the *IP to layer2 Traffic Mapping Info To Remove* IE, if present. The gNB- + +DU shall use the mapping information stored for the mapping of IP traffic to layer 2, as specified in TS 38.340 [30]. + +- if the *BAP layer BH RLC channel Mapping Info* IE is included, the gNB-DU shall store the mapping information contained in the *BAP layer BH RLC channel Mapping Info To Add* IE, if present, and remove the previously stored mapping information as indicated by the *BAP layer BH RLC channel Mapping Info To Remove* IE, if present. The gNB-DU shall use the mapping information stored when forwarding traffic on BAP sublayer, as specified in TS 38.340 [30]. + +If the *Buffer Size Threshold* IE is included in the BAP MAPPING CONFIGURATION message, the gNB-DU shall, if supported, use it to determine the DL congestion based on the flow control feedback from child IAB-nodes as specified in TS 38.340 [30]. + +If *BAP Header Rewriting Added List* IE is included in the BAP MAPPING CONFIGURATION message, the gNB-DU shall, if supported, store the BAP header rewriting configuration from this IE, and use it as specified in TS 38.340 [30]. If *BAP Header Rewriting Added List* IE contains information for an existing ingress BAP Routing ID, the gNB-DU shall, if supported, replace the previously stored BAP header rewriting configuration for this ingress BAP Routing ID with the corresponding information in the *BAP Header Rewriting Added List* IE. + +If *BAP Header Rewriting Removed List* IE is included in the BAP MAPPING CONFIGURATION message, the gNB-DU shall, if supported, remove the BAP header rewriting configuration according to such IE. + +If the *Re-routing Enable Indicator* IE is included in the BAP MAPPING CONFIGURATION message, and the value is set as “false”, the gNB-DU shall, if supported, disable the inter-donor-DU re-routing. If the *Re-routing Enable Indicator* IE is included in the BAP MAPPING CONFIGURATION message, and the value is set as “true”, the gNB-DU shall, if supported, enable the inter-donor-DU re-routing, as specified in TS 38.340 [30]. + +#### 8.10.1.A Unsuccessful Operation + +![Sequence diagram showing the BAP Mapping Configuration procedure: Unsuccessful Operation. The gNB-CU sends a BAP MAPPING CONFIGURATION message to the gNB-DU, and the gNB-DU responds with a BAP MAPPING CONFIGURATION FAILURE message.](32d2783121efa86871886ed9d7678637_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: BAP MAPPING CONFIGURATION + gNB-DU-->>gNB-CU: BAP MAPPING CONFIGURATION FAILURE + Note right of gNB-CU: +``` + +Sequence diagram showing the BAP Mapping Configuration procedure: Unsuccessful Operation. The gNB-CU sends a BAP MAPPING CONFIGURATION message to the gNB-DU, and the gNB-DU responds with a BAP MAPPING CONFIGURATION FAILURE message. + +**Figure 8.10.1.3-1: BAP Mapping Configuration procedure: Unsuccessful Operation** + +If the gNB-DU cannot accept the configuration, it shall respond with a BAP MAPPING CONFIGURATION FAILURE and appropriate cause value. + +If the BAP MAPPING CONFIGURATION FAILURE message includes the Time To Wait IE, the gNB-CU shall wait at least for the indicated time before reinitiating the BAP MAPPING CONFIGURATION message towards the same gNB-DU. + +#### 8.10.1.3 Abnormal Conditions + +Not applicable. + +## 8.10.2 gNB-DU Resource Configuration + +### 8.10.2.1 General + +The gNB-DU Resource Configuration procedure is initiated by the gNB-CU in order to configure the resource usage for a gNB-DU. The procedure uses non-UE associated signalling. + +In this version of the specification, this procedure is used to configure IAB resources. + +### 8.10.2.2 Successful Operation + +![Sequence diagram showing the successful operation of the gNB-DU Resource Configuration procedure. The gNB-CU sends a GNB-DU RESOURCE CONFIGURATION message to the gNB-DU, and the gNB-DU responds with a GNB-DU RESOURCE CONFIGURATION ACKNOWLEDGE message.](4a9454b4354535e1b61423084da1424b_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: GNB-DU RESOURCE CONFIGURATION + gNB-DU-->>gNB-CU: GNB-DU RESOURCE CONFIGURATION ACKNOWLEDGE + Note right of gNB-CU: +``` + +Sequence diagram showing the successful operation of the gNB-DU Resource Configuration procedure. The gNB-CU sends a GNB-DU RESOURCE CONFIGURATION message to the gNB-DU, and the gNB-DU responds with a GNB-DU RESOURCE CONFIGURATION ACKNOWLEDGE message. + +**Figure 8.10.2.2-1: gNB-DU Resource Configuration procedure: Successful Operation** + +The gNB-CU initiates the procedure by sending the GNB-DU RESOURCE CONFIGURATION message to gNB-DU. The gNB-DU replies to the gNB-CU with the GNB-DU RESOURCE CONFIGURATION ACKNOWLEDGE message. + +For each cell in the *Activated Cells to Be Updated List* IE of the GNB-DU RESOURCE CONFIGURATION message, the gNB-DU shall store the resource configuration contained in the *IAB-DU Cell Resource Configuration-Mode-Info* IE and use it when performing scheduling in compliance with TS 38.213 [31]. + +If the *Child-Node List* IE is included in the GNB-DU RESOURCE CONFIGURATION message, for each child-node indicated by the *gNB-CU UE FIAP ID* IE and *gNB-DU UE FIAP ID* IE, and for each cell served by this child node indicated by the *NR CGI* IE in the *Child-Node Cells List* IE, the gNB-DU shall store the received information and use this information for scheduling, in compliance with TS 38.213 [31], clause 14. + +If the *Neighbour-Node Cells List* IE is included in the GNB-DU RESOURCE CONFIGURATION message, for each neighbour-node cell indicated by the *NR CGI* IE in the *Neighbour-Node Cells List* IE, the gNB-DU shall store the received information and use this information for cross-link interference management and/or semi-static resource coordination. If the *Peer Parent-Node Indicator* IE is included in the GNB-DU RESOURCE CONFIGURATION message and the value is set as “true”, the gNB-DU shall, consider the cell indicated by the *NR CGI* IE is served by the peer parent node of the IAB-node indicated by the *gNB-CU UE FIAP ID* IE and the *gNB-DU UE FIAP ID* IE. + +If the *Serving Cells List* IE is included in the GNB-DU RESOURCE CONFIGURATION message, the gNB-DU shall store the received information and use this information for scheduling, in compliance with TS 38.213 [31], clause 14. + +### 8.10.2.B Unsuccessful Operation + +![Sequence diagram for gNB-DU Resource Configuration procedure: Unsuccessful Operation](c5424b117a719524c619938e97c4cb1f_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: GNB-DU RESOURCE CONFIGURATION + Note right of gNB-CU: + gNB-DU-->>gNB-CU: GNB-DU RESOURCE CONFIGURATION FAILURE + Note right of gNB-DU: +``` + +The diagram shows a sequence of messages between a gNB-CU and a gNB-DU. The gNB-CU sends a 'GNB-DU RESOURCE CONFIGURATION' message to the gNB-DU. The gNB-DU responds with a 'GNB-DU RESOURCE CONFIGURATION FAILURE' message. Both entities have a vertical lifeline with a small black rectangle at the bottom. + +Sequence diagram for gNB-DU Resource Configuration procedure: Unsuccessful Operation + +**Figure 8.10.2.3-1: gNB-DU Resource Configuration procedure: Unsuccessful Operation** + +If the gNB-DU cannot accept the configuration, it shall respond with a GNB-DU RESOURCE CONFIGURATION FAILURE and appropriate cause value. + +If the GNB-DU RESOURCE CONFIGURATION FAILURE message includes the Time To Wait IE, the gNB-CU shall wait at least for the indicated time before reinitiating the GNB-DU RESOURCE CONFIGURATION message towards the same gNB-DU. + +### 8.10.2.3 Abnormal Conditions + +Not applicable. + +## 8.10.3 IAB TNL Address Allocation + +### 8.10.3.1 General + +The purpose of the IAB TNL Address Allocation procedure is to allocate TNL addresses to be used by the IAB-node(s). This procedure uses non-UE associated signalling. + +NOTE: This procedure is applicable for IAB-donor-DU, where the term "gNB-DU" applies to IAB-donor-DU, and the term "gNB-CU" applies to IAB-donor-CU. + +### 8.10.3.2 Successful Operation + +![Sequence diagram for IAB TNL Address Allocation procedure: Successful Operation](39f5c01e256787572d7b50ca763be6e2_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: IAB TNL ADDRESS REQUEST + Note right of gNB-CU: + gNB-DU-->>gNB-CU: IAB TNL ADDRESS RESPONSE + Note right of gNB-DU: +``` + +The diagram shows a sequence of messages between a gNB-CU and a gNB-DU. The gNB-CU sends an 'IAB TNL ADDRESS REQUEST' message to the gNB-DU. The gNB-DU responds with an 'IAB TNL ADDRESS RESPONSE' message. Both entities have a vertical lifeline with a small black rectangle at the bottom. + +Sequence diagram for IAB TNL Address Allocation procedure: Successful Operation + +**Figure 8.10.3.2-1: IAB TNL Address Allocation procedure: Successful Operation** + +The gNB-CU initiates the procedure by sending the IAB TNL ADDRESS REQUEST message to the gNB-DU. + +If the IAB TNL ADDRESS REQUEST message contains the *IAB IPv4 Addresses Requested* IE, the gNB-DU shall allocate the individual TNL address(es) accordingly and include these IPv4 address(es) in the IAB TNL ADDRESS RESPONSE message. + +If the IAB TNL ADDRESS REQUEST message contains the *IAB IPv6 Request Type* IE, the gNB-DU shall allocate the individual IPv6 address(es) or IPv6 address prefix(es) accordingly and include these IPv6 address(es) or IPv6 address prefix(es) in the IAB TNL ADDRESS RESPONSE message. + +If the IAB TNL ADDRESS REQUEST message contains the *IAB TNL Addresses To Remove List* IE, the gNB-DU shall consider that the TNL address(es) and/or TNL address prefix(es) therein are no longer used by the IAB-node(s). In addition, if the IAB TNL ADDRESS REQUEST message only contains the *IAB TNL Addresses to Remove List* IE, the gNB-CU shall ignore the *IAB Allocated TNL Address List* IE in the IAB TNL ADDRESS RESPONSE message. + +If the IAB TNL ADDRESS RESPONSE message contains the *IAB TNL Address Usage* IE in the *IAB Allocated TNL Address Item* IE, the gNB-CU shall consider the indicated TNL address usage when allocating a TNL address to an IAB-node. Otherwise, the gNB-CU shall consider that the TNL address can be used for all traffic when allocating the TNL address to an IAB-node. + +If the *IAB TNL Address Exception* IE is included in the IAB TNL ADDRESS REQUEST message and the gNB-DU is an IAB-donor-DU, the gNB-DU shall, if supported, consider the IP address(es) therein as exempt from TNL address filtering, and forward the packets with the address(es) indicated by this IE, as specified in TS 38.401 [4]. + +### 8.10.3.C Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of IAB TNL Address Allocation. A GNB-CU sends an IAB TNL ADDRESS REQUEST to a GNB-DU, and the GNB-DU responds with an IAB TNL ADDRESS FAILURE.](497d7e14540664a2914557cad79f3791_img.jpg) + +``` +sequenceDiagram + participant GNB-DU + participant GNB-CU + Note left of GNB-DU: + GNB-CU->>GNB-DU: IAB TNL ADDRESS REQUEST + Note right of GNB-DU: + GNB-DU-->>GNB-CU: IAB TNL ADDRESS FAILURE + Note right of GNB-CU: +``` + +Sequence diagram showing the Unsuccessful Operation of IAB TNL Address Allocation. A GNB-CU sends an IAB TNL ADDRESS REQUEST to a GNB-DU, and the GNB-DU responds with an IAB TNL ADDRESS FAILURE. + +**Figure 8.10.3.3-1: IAB TNL Address Allocation procedure: Unsuccessful Operation** + +If the gNB-DU cannot accept the request, it shall respond with an IAB TNL ADDRESS FAILURE and appropriate cause value. + +If the IAB TNL ADDRESS FAILURE message includes the Time To Wait IE, the gNB-CU shall wait at least for the indicated time before reinitiating the IAB TNL ADDRESS REQUEST message towards the same gNB-DU. + +### 8.10.3.3 Abnormal Conditions + +Not applicable. + +## 8.10.4 IAB UP Configuration Update + +### 8.10.4.1 General + +The purpose of the IAB UP Configuration Update procedure is to update the UP parameters including UL mapping configuration and the UL/DL UP TNL information between IAB-donor-CU and IAB-node. This procedure uses non-UE associated signalling. + +NOTE: This procedure is applicable for IAB-nodes, where the term "gNB-DU" applies to IAB-DU, and the term "gNB-CU" applies to IAB-donor-CU. + +NOTE: Implementation shall ensure the avoidance of potential race conditions, i.e. it shall ensure that the update of UP configuration (e.g. the UL/DL UP TNL information, UL mapping information) is not concurrently performed using the non-UE-associated IAB UP Configuration Update procedure and the UE-associated procedures for UE Context Management. + +#### 8.10.4.2 Successful Operation + +![Sequence diagram for Successful Operation of IAB UP Configuration Update procedure. The gNB-CU sends an IAB UP CONFIGURATION UPDATE REQUEST to the gNB-DU, and the gNB-DU responds with an IAB UP CONFIGURATION UPDATE RESPONSE.](5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-CU->>gNB-DU: IAB UP CONFIGURATION UPDATE REQUEST + Note right of gNB-CU: + gNB-DU-->>gNB-CU: IAB UP CONFIGURATION UPDATE RESPONSE + Note right of gNB-DU: +``` + +Sequence diagram for Successful Operation of IAB UP Configuration Update procedure. The gNB-CU sends an IAB UP CONFIGURATION UPDATE REQUEST to the gNB-DU, and the gNB-DU responds with an IAB UP CONFIGURATION UPDATE RESPONSE. + +Figure 8.10.4.2-1: IAB UP Configuration Update procedure: Successful Operation + +The gNB-CU initiates the procedure by sending the IAB UP CONFIGURATION UPDATE REQUEST message to the gNB-DU. The gNB-DU replies to the gNB-CU with the IAB UP CONFIGURATION UPDATE RESPONSE message. + +If the *UL UP TNL Information to Update List* IE is included in the IAB UP CONFIGURATION UPDATE REQUEST message, the gNB-DU shall perform the mapping according to the new received *BH Information* IE for each F1-U GTP tunnel indicated by the *UL UP TNL Information* IE. If the *New UL UP TNL Information* IE is included in *UL UP TNL Information to Update List* IE, the gNB-DU shall use it to replace the information of UL F1-U GTP tunnel indicated by the *UL UP TNL Information* IE. + +If the *UL UP TNL Address to Update List* IE is included in the IAB UP CONFIGURATION UPDATE REQUEST message, the gNB-DU shall replace the old TNL address with the new TNL address for all the maintained UL F1-U GTP tunnels corresponding to the old TNL address. + +If the *DL UP TNL Address to Update List* IE is included in the IAB UP CONFIGURATION UPDATE RESPONSE message, the gNB-CU shall replace the old TNL address with the new TNL address for all the maintained DL F1-U GTP tunnels corresponding to the old TNL address. + +#### 8.10.4.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Operation of IAB UP Configuration Update procedure. The gNB-CU sends an IAB UP CONFIGURATION UPDATE REQUEST to the gNB-DU, and the gNB-DU responds with an IAB UP CONFIGURATION UPDATE FAILURE.](7d78469417c76901ecf6e36600a721cb_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-CU->>gNB-DU: IAB UP CONFIGURATION UPDATE REQUEST + Note right of gNB-CU: + gNB-DU-->>gNB-CU: IAB UP CONFIGURATION UPDATE FAILURE + Note right of gNB-DU: +``` + +Sequence diagram for Unsuccessful Operation of IAB UP Configuration Update procedure. The gNB-CU sends an IAB UP CONFIGURATION UPDATE REQUEST to the gNB-DU, and the gNB-DU responds with an IAB UP CONFIGURATION UPDATE FAILURE. + +Figure 8.10.4.3-1: IAB UP Configuration Update procedure: Unsuccessful Operation + +If the gNB-DU receives an IAB UP CONFIGURATION UPDATE REQUEST message and cannot perform any update accordingly, it shall consider the update procedure as failed and respond with an IAB UP CONFIGURATION UPDATE FAILURE message and an appropriate cause value. + +If the IAB UP CONFIGURATION UPDATE FAILURE message includes the *Time To Wait* IE, the gNB-CU shall wait at least for the indicated time before reinitiating the IAB UP CONFIGURATION UPDATE REQUEST message towards the same gNB-DU. + +#### 8.10.4.4 Abnormal Conditions + +Not applicable. + +### 8.10.5 Mobile IAB F1 Setup Triggering + +#### 8.10.5.1 General + +The purpose of the Mobile IAB F1 Setup Triggering procedure is to trigger F1 interface establishment between a target logical gNB-DU and a target F1-terminating IAB-donor-CU. The target logical gNB-DU is co-located with the gNB-DU that receives the triggering message. This procedure uses non-UE associated signalling. + +NOTE: This procedure is applicable for mobile IAB-nodes, where the term "gNB-DU" applies to a mobile IAB-DU, and the term "gNB-CU" applies to a source F1-terminating IAB-donor-CU during mobile IAB-DU migration. + +#### 8.10.5.2 Successful Operation + +![Sequence diagram showing the successful operation of Mobile IAB F1 Setup Triggering. A gNB-CU sends a MIAB F1 SETUP TRIGGERING message to a gNB-DU.](16766297a5918739f471ec2a3130cca9_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-CU: + gNB-CU->>gNB-DU: MIAB F1 SETUP TRIGGERING + Note right of gNB-DU: + activate gNB-DU + Note right of gNB-DU: + deactivate gNB-DU +``` + +The diagram illustrates the successful operation of Mobile IAB F1 Setup Triggering. It shows two entities: gNB-DU and gNB-CU. The gNB-CU sends a message labeled "MIAB F1 SETUP TRIGGERING" to the gNB-DU. Both entities are represented by rectangular boxes with a horizontal line extending downwards from the bottom, ending in a thick black bar. + +Sequence diagram showing the successful operation of Mobile IAB F1 Setup Triggering. A gNB-CU sends a MIAB F1 SETUP TRIGGERING message to a gNB-DU. + +**Figure 8.10.5.2-1: Mobile IAB F1 Setup Triggering: Successful Operation** + +The gNB-CU initiates the procedure by sending the MIAB F1 SETUP TRIGGERING message to the gNB-DU. + +Upon the reception of the MIAB F1 SETUP TRIGGERING message, the gNB-DU shall initiate the TNL connection establishment and F1 setup to a target F1-terminating IAB-donor-CU indicated by the *Target gNB ID* IE included in the MIAB F1 SETUP TRIGGERING message. + +If the MIAB F1 SETUP TRIGGERING message contains the *Target gNB IP address* IE, the gNB-DU shall store the IP address and use it for establishing the TNL connection towards a target F1-terminating IAB-donor-CU. + +If the MIAB F1 SETUP TRIGGERING message contains the *Target SeGW IP address* IE, the gNB-DU shall store the IP address and use it for establishing the security connection to protect the F1 interface towards the target F1-terminating IAB-donor-CU. + +#### 8.10.5.3 Abnormal Conditions + +Not applicable. + +## 8.10.6 Mobile IAB F1 Setup Outcome Notification + +### 8.10.6.1 General + +The purpose of the Mobile IAB F1 Setup Outcome Notification procedure is to report the outcome of the F1 interface setup between a target logical gNB-DU and a target F1-terminating IAB-donor-CU. The target logical gNB-DU is co-located with the gNB-DU that sends the notification message. This procedure uses non-UE associated signalling. + +NOTE: This procedure is applicable for mobile IAB-nodes, where the term "gNB-DU" applies to mobile IAB-DU, and the term "gNB-CU" applies to source F1-terminating IAB-donor-CU during mIAB-DU migration. + +### 8.10.6.2 Successful Operation + +![Sequence diagram showing the successful operation of Mobile IAB F1 Setup Outcome Notification. A gNB-DU sends a MIAB F1 SETUP OUTCOME NOTIFICATION message to a gNB-CU.](4bb56f4af58f9d5daab52d98c984d8d5_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: MIAB F1 SETUP OUTCOME NOTIFICATION + Note right of gNB-CU: +``` + +Sequence diagram showing the successful operation of Mobile IAB F1 Setup Outcome Notification. A gNB-DU sends a MIAB F1 SETUP OUTCOME NOTIFICATION message to a gNB-CU. + +**Figure 8.10.6.2-1: Mobile IAB F1 Setup Outcome Notification: Successful Operation** + +The gNB-DU initiates the procedure by sending the MIAB F1 SETUP OUTCOME NOTIFICATION message to the gNB-CU. + +Upon the reception of the MIAB F1 SETUP OUTCOME NOTIFICATION message, the gNB-CU shall, if supported, consider the F1 setup outcome of the target logical gNB-DU co-located with the gNB-DU, for further IAB-DU migration as specified in TS 38.401 [4]. + +If the *Activated Cells Mapping List* is included in the MIAB F1 SETUP OUTCOME NOTIFICATION message, the gNB-CU shall, if supported, take it into account when further performing handover of the connected UEs from this gNB-DU to its co-located target logical gNB-DU. + +If the *Target F1 Terminating IAB-Donor gNB ID* is included in the MIAB F1 SETUP OUTCOME NOTIFICATION message, the gNB-CU shall, if supported, take it into account when further performing handover of the connected UEs from this gNB-DU to its co-located target logical gNB-DU. + +### 8.10.6.3 Abnormal Conditions + +Not applicable. + +## 8.11 Self Optimisation Support procedures + +### 8.11.1 Access and Mobility Indication + +#### 8.11.1.1 General + +This procedure is initiated by gNB-CU to send the Access and Mobility related Information to gNB-DU. + +The procedure uses non-UE-associated signalling. + +#### 8.11.1.2 Successful Operation + +![Sequence diagram showing the Access and Mobility Indication procedure. A gNB-CU sends an ACCESS AND MOBILITY INDICATION message to a gNB-DU.](dd8c4eb490876d1c18169c84d877ef32_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-CU: + gNB-CU->>gNB-DU: ACCESS AND MOBILITY INDICATION + Note right of gNB-DU: + Note left of gNB-CU: + Note right of gNB-DU: +``` + +Sequence diagram showing the Access and Mobility Indication procedure. A gNB-CU sends an ACCESS AND MOBILITY INDICATION message to a gNB-DU. + +**Figure 8.11.1.2-1: Access and Mobility Indication procedure. Successful operation** + +The Access and Mobility Indication procedure is initiated by ACCESS AND MOBILITY INDICATION message sent from gNB-CU to gNB-DU. + +If the ACCESS AND MOBILITY INDICATION message contains the *RA Report List* IE the gNB-DU shall take it into account for optimisation of RACH access procedures. + +If the ACCESS AND MOBILITY INDICATION message contains the *RLF Report Information List* IE the gNB-DU shall take it into account for optimisation of mobility parameters. + +If the ACCESS AND MOBILITY INDICATION message contains the *Successful HO Report Information List* IE the gNB-DU may take it into account for optimisation of mobility parameters. + +If the ACCESS AND MOBILITY INDICATION message contains the *Successful PSCell Change Report Information List* IE, the gNB-DU may take it into account for optimisation of PSCell change/addition related parameters. + +#### 8.11.1.3 Abnormal Conditions + +Not applicable. + +### 8.12 Reference Time Information Reporting procedures + +#### 8.12.1 Reference Time Information Reporting Control + +##### 8.12.1.1 General + +The purpose of the Reference Time Information Reporting Control procedure is to command the gNB-DU to send the requested accurate reference time information to the gNB-CU. The procedure uses non-UE associated signalling. + +##### 8.12.1.2 Successful Operation + +![Sequence diagram for Reference Time Information Reporting Control](684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg) + +A sequence diagram showing the interaction between a gNB-DU and a gNB-CU. The gNB-DU is on the left and the gNB-CU is on the right. A horizontal arrow labeled "REFERENCE TIME INFORMATION REPORTING CONTROL" points from the gNB-CU to the gNB-DU. Both entities have a vertical lifeline extending downwards from their respective boxes. + +Sequence diagram for Reference Time Information Reporting Control + +**Figure 8.12.1.2-1: Reference Time Information Reporting Control** + +The gNB-CU initiates the procedure by sending REFERENCE TIME INFORMATION REPORTING CONTROL message to the gNB-DU. Upon reception of the REFERENCE TIME INFORMATION REPORTING CONTROL message, the gNB-DU shall, if supported, perform the requested reference time information reporting action. + +The *Report Type* IE indicates to the gNB-DU whether: + +- to report on demand; +- to report periodic, with a frequency as specified by the *Report Periodicity* IE; +- to stop periodic reporting. + +### 8.12.1.3 Abnormal Conditions + +Not applicable. + +## 8.12.2 Reference Time Information Report + +### 8.12.2.1 General + +The purpose of the Reference Time Information Report procedure is to report the accurate reference time information from the gNB-DU to the gNB-CU. The procedure uses non-UE associated signalling. + +### 8.12.2.2 Successful Operation + +![Sequence diagram for Reference Time Information Report](c11773d09ceffdb3b486f2055afa7c3c_img.jpg) + +A sequence diagram showing the interaction between a gNB-DU and a gNB-CU. The gNB-DU is on the left and the gNB-CU is on the right. A horizontal arrow labeled "REFERENCE TIME INFORMATION REPORT" points from the gNB-DU to the gNB-CU. Both entities have a vertical lifeline extending downwards from their respective boxes. + +Sequence diagram for Reference Time Information Report + +**Figure 8.12.2.2-1: Reference Time Information Report** + +The gNB-DU initiates the procedure by sending a REFERENCE TIME INFORMATION REPORT message to the gNB-CU. The REFERENCE TIME INFORMATION REPORT message may be used as a response to the REFERENCE TIME INFORMATION REPORTING CONTROL message. + +### 8.12.2.3 Abnormal Conditions + +Not applicable. + +## 8.13 Positioning Procedures + +### 8.13.1 Positioning Assistance Information Control + +#### 8.13.1.1 General + +The purpose of the Positioning Assistance Information Control procedure is to allow the gNB-CU to signal positioning assistance information to the gNB-DU for positioning assistance information broadcasting. The procedure uses non-UE-associated signalling. + +#### 8.13.1.2 Successful Operation + +![Sequence diagram showing the Positioning Assistance Information Control procedure. A gNB-CU sends a POSITIONING ASSISTANCE INFORMATION CONTROL message to a gNB-DU. The gNB-DU is represented by a box with a vertical line extending downwards to a thick horizontal bar. The gNB-CU is represented by a box with a vertical line extending downwards to a thick horizontal bar. The message is shown as a horizontal arrow pointing from the gNB-CU to the gNB-DU.](77c78bfdbbee0e121808674b08fd7046_img.jpg) + +``` + +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + Note right of gNB-CU: + gNB-CU->>gNB-DU: POSITIONING ASSISTANCE INFORMATION CONTROL + +``` + +Sequence diagram showing the Positioning Assistance Information Control procedure. A gNB-CU sends a POSITIONING ASSISTANCE INFORMATION CONTROL message to a gNB-DU. The gNB-DU is represented by a box with a vertical line extending downwards to a thick horizontal bar. The gNB-CU is represented by a box with a vertical line extending downwards to a thick horizontal bar. The message is shown as a horizontal arrow pointing from the gNB-CU to the gNB-DU. + +**Figure 8.13.1.2-1: Positioning Assistance Information Control procedure** + +The gNB-CU initiates the procedure by sending a POSITIONING ASSISTANCE INFORMATION CONTROL message. + +If the *Positioning Assistance Information* IE is included in the POSITIONING ASSISTANCE INFORMATION CONTROL message, the gNB-DU shall, if supported, replace any previously stored positioning assistance information and use the received information to configure positioning assistance information broadcasting as specified in TS 38.455 [37]. + +If the *Broadcast* IE is included in the POSITIONING ASSISTANCE INFORMATION CONTROL message and set to "start", the gNB-DU may start broadcasting the positioning assistance information. If the *Broadcast* IE is included in the POSITIONING ASSISTANCE INFORMATION CONTROL message and set to "stop", the gNB-DU may stop broadcasting the positioning assistance information. + +If the *Positioning Broadcast Cells* IE is included in the POSITIONING ASSISTANCE INFORMATION CONTROL message, the gNB-DU shall, if supported, consider that the received assistance information is applicable to the cells in this IE. + +#### **Interaction with the Positioning Assistance Information Feedback procedure:** + +If the *Routing ID* IE is included in the POSITIONING ASSISTANCE INFORMATION CONTROL message, the gNB-DU shall, if supported, store this information and include it in any future POSITIONING ASSISTANCE INFORMATION FEEDBACK messages associated to the requested positioning assistance information broadcasting. + +#### 8.13.1.3 Abnormal Conditions + +If the *Broadcast* IE is included in the POSITIONING ASSISTANCE INFORMATION CONTROL message and set to "start", and no positioning assistance information is available, the gNB-DU shall consider the procedure as failed. + +If neither the *Positioning Assistance Information* IE nor the *Broadcast* IE are included in the POSITIONING ASSISTANCE INFORMATION CONTROL message, the gNB-DU shall consider the procedure as failed. + +## 8.13.2 Positioning Assistance Information Feedback + +### 8.13.2.1 General + +The purpose of the Positioning Assistance Information Feedback procedure is to allow the gNB-DU to give feedback to the gNB-CU on positioning assistance information broadcasting. The procedure uses non-UE-associated signalling. + +### 8.13.2.2 Successful Operation + +![Sequence diagram showing the Positioning Assistance Information Feedback procedure. A gNB-DU sends a POSITIONING ASSISTANCE INFORMATION FEEDBACK message to a gNB-CU.](6ee202d340236de98def8045f273fa38_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: POSITIONING ASSISTANCE INFORMATION FEEDBACK + Note right of gNB-CU: +``` + +Sequence diagram showing the Positioning Assistance Information Feedback procedure. A gNB-DU sends a POSITIONING ASSISTANCE INFORMATION FEEDBACK message to a gNB-CU. + +**Figure 8.13.2.2-1: Positioning Assistance Information Feedback procedure** + +The gNB-DU initiates the procedure by sending a POSITIONING ASSISTANCE INFORMATION FEEDBACK message. If the *Positioning Assistance Information Failure List* IE is included in the POSITIONING ASSISTANCE INFORMATION FEEDBACK message, the gNB-CU shall consider that positioning assistance information broadcasting could not be configured for the relevant information. + +If the *Positioning Broadcast Cells* IE is included in the POSITIONING ASSISTANCE INFORMATION FEEDBACK message, the gNB-CU shall consider that the feedback provided is applicable to the cells in this IE. + +If the *Routing ID* IE is included in the POSITIONING ASSISTANCE INFORMATION FEEDBACK message, the gNB-CU may use this information to identify the positioning assistance information broadcasting for which feedback is provided. + +### 8.13.2.3 Abnormal Conditions + +Void. + +## 8.13.3 Positioning Measurement + +### 8.13.3.1 General + +The purpose of the Positioning Measurement procedure is to allow the gNB-CU to request one or more TRPs in the gNB-DU to perform and report positioning measurements. The procedure uses non-UE-associated signalling. + +### 8.13.3.2 Successful Operation + +![Sequence diagram showing the successful operation of the Positioning Measurement procedure. The gNB-CU sends a POSITIONING MEASUREMENT REQUEST to the gNB-DU, and the gNB-DU responds with a POSITIONING MEASUREMENT RESPONSE.](649f424fd35ea31f622163506a6148ed_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: POSITIONING MEASUREMENT REQUEST + gNB-DU-->>gNB-CU: POSITIONING MEASUREMENT RESPONSE + Note right of gNB-CU: + +``` + +Sequence diagram showing the successful operation of the Positioning Measurement procedure. The gNB-CU sends a POSITIONING MEASUREMENT REQUEST to the gNB-DU, and the gNB-DU responds with a POSITIONING MEASUREMENT RESPONSE. + +**Figure 8.13.3.2-1: Positioning Measurement procedure: successful operation** + +The gNB-CU initiates the procedure by sending a POSITIONING MEASUREMENT REQUEST message to the gNB-DU, indicating in the *TRP Measurement Request List* IE the TRP(s) from which measurements are requested. The gNB-DU node shall use the included information to configure positioning measurements by the indicated TRP(s). If at least one of the requested measurements has been successful for at least one of the TRPs, the gNB-DU shall reply with the POSITIONING MEASUREMENT RESPONSE message including the *Positioning Measurement Response List* IE. + +If the *Positioning Report Characteristics* IE is set to "OnDemand", the gNB-DU shall return the corresponding measurement results in the *Positioning Measurement Result List* IE in the POSITIONING MEASUREMENT RESPONSE message, and the gNB-CU shall consider that this reporting has been terminated by the gNB-DU. + +If the *Measurement Beam Information Request* IE is included in the POSITIONING MEASUREMENT REQUEST message, the gNB-DU node shall include the *Measurement Beam Information* IE in the *Positioning Measurement Result* IE of the POSITIONING MEASUREMENT RESPONSE message. + +If the *Measurement Quality* IE is included in the *Measurement Result* IE in the POSITIONING MEASUREMENT RESPONSE message, the gNB-CU may use it for further signalling. If the *Measurement Quality* IE includes the *Zenith Quality* IE, the gNB-CU may use it for further signalling. + +If the *System Frame Number* IE and/or the *Slot Number* IE are included in the POSITIONING MEASUREMENT REQUEST message, the gNB-DU node shall, if supported, consider that the respective information indicates the activation time of SRS transmission. + +If the *Measurement Characteristics Request Indicator* IE is included in the POSITIONING MEASUREMENT REQUEST message, the gNB-DU shall, if supported, take the requested measurement characteristics into account when configuring measurements, and include the requested information, if available, in the POSITIONING MEASUREMENT RESPONSE message. + +If the *Number of TRP Rx TEGs* IE is included in the POSITIONING MEASUREMENT REQUEST message, the gNB-DU shall, if supported, use it to measure the same SRS resource with different TRP Rx TEGs for the indicated TRP, and report the corresponding UL-RTOA and/or gNB Rx-Tx time difference measurements. + +If the *Number of TRP RxTx TEGs* IE is included in the POSITIONING MEASUREMENT REQUEST message, the gNB-DU shall, if supported, use it to measure the same SRS resource with different TRP RxTx TEGs with the same TRP Tx TEG for the indicated TRP, and report the corresponding gNB Rx-Tx time difference measurements. + +If the *Measurement Time Occasion* IE is included in the POSITIONING MEASUREMENT REQUEST message, the gNB-DU may take it into account as the number of SRS measurement time occasions for a measurement instance. + +#### Interaction with the Positioning Measurement Report procedure: + +If the *Positioning Report Characteristics* IE is set to "Periodic", the gNB-DU shall initiate the corresponding measurements, and it shall reply with the POSITIONING MEASUREMENT RESPONSE message without including + +any measurement results in the message. The gNB-DU shall then periodically initiate the Positioning Measurement Report procedure for the corresponding measurements, with the requested reporting periodicity. + +If the *Report Characteristics* IE is set to "OnDemand" and the *Response Time* IE is included in the POSITIONING MEASUREMENT REQUEST message, the gNB-DU shall, if supported, return the corresponding measurement results in the POSITIONING MEASUREMENT RESPONSE message within the indicated time. + +If the *Positioning Report Characteristics* IE is set to "Periodic" and the *Positioning Measurement Amount* IE is included in the POSITIONING MEASUREMENT REQUEST message, the gNB-DU shall, if supported, take it into account for sending the POSITIONING MEASUREMENT REPORT message. + +### 8.13.3.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Operation](493539f7472fd8510b2c6dcb59339ad5_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: POSITIONING MEASUREMENT REQUEST + Note right of gNB-DU: + gNB-DU-->>gNB-CU: POSITIONING MEASUREMENT FAILURE +``` + +The diagram shows a sequence of messages between a gNB-CU and a gNB-DU. The gNB-CU sends a 'POSITIONING MEASUREMENT REQUEST' message to the gNB-DU. The gNB-DU then responds with a 'POSITIONING MEASUREMENT FAILURE' message. Both entities are represented by boxes with vertical lines extending downwards to horizontal bars. + +Sequence diagram for Unsuccessful Operation + +Figure 8.13.3.3-1: Positioning Measurement procedure: unsuccessful operation + +If the gNB-DU is unable to configure any of the requested positioning measurements for any of the TRPs in the *TRP Measurement Request List* IE of the POSITIONING MEASUREMENT REQUEST message, it shall respond with a POSITIONING MEASUREMENT FAILURE message. + +### 8.13.3.4 Abnormal Conditions + +If the gNB-DU receives a POSITIONING MEASUREMENT REQUEST message containing an LMF Measurement ID corresponding to an ongoing positioning measurement, it shall consider the procedure as failed and initiate local error handling. + +## 8.13.4 Positioning Measurement Report + +### 8.13.4.1 General + +The purpose of the Positioning Measurement Report procedure is for the gNB-DU to report positioning measurements to the gNB-CU. The procedure uses non-UE-associated signalling. + +### 8.13.4.2 Successful Operation + +![Sequence diagram for Successful Operation](001e51e5f51e142322032c14a06c9385_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: POSITIONING MEASUREMENT REPORT + Note right of gNB-CU: +``` + +The diagram shows a sequence of messages between a gNB-DU and a gNB-CU. The gNB-DU sends a 'POSITIONING MEASUREMENT REPORT' message to the gNB-CU. Both entities are represented by boxes with vertical lines extending downwards to horizontal bars. + +Sequence diagram for Successful Operation + +Figure 8.13.4.2-1: Positioning Measurement Report procedure: successful operation + +The gNB-DU initiates the procedure by sending a POSITIONING MEASUREMENT REPORT message. The POSITIONING MEASUREMENT REPORT message contains the positioning measurement results according to the associated measurement configuration. + +#### 8.13.4.3 Unsuccessful Operation + +Not applicable. + +#### 8.13.4.4 Abnormal Conditions + +Not applicable. + +### 8.13.5 Positioning Measurement Abort + +#### 8.13.5.1 General + +The purpose of the Positioning Measurement Abort procedure is to enable the gNB-CU to abort an on-going measurement. The procedure uses non-UE-associated signalling. + +#### 8.13.5.2 Successful Operation + +![Sequence diagram showing the successful operation of the Positioning Measurement Abort procedure. The gNB-CU sends a POSITIONING MEASUREMENT ABORT message to the gNB-DU.](0c672a46a384f025be6e69e6e34bfe11_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-CU: + gNB-CU->>gNB-DU: POSITIONING MEASUREMENT ABORT + Note right of gNB-DU: + Note left of gNB-CU: + Note right of gNB-DU: +``` + +The diagram illustrates the successful operation of the Positioning Measurement Abort procedure. It shows two entities, gNB-DU and gNB-CU, represented by boxes. A horizontal arrow labeled 'POSITIONING MEASUREMENT ABORT' points from the gNB-CU to the gNB-DU. Below each box is a vertical line representing a lifeline, which ends in a thick horizontal bar. + +Sequence diagram showing the successful operation of the Positioning Measurement Abort procedure. The gNB-CU sends a POSITIONING MEASUREMENT ABORT message to the gNB-DU. + +**Figure 8.13.5.2-1: Positioning Measurement Abort procedure: successful operation** + +The gNB-CU initiates the procedure by generating a POSITIONING MEASUREMENT ABORT message. Upon receiving this message, the gNB-DU shall terminate the on-going measurement identified by the *RAN Measurement ID* IE and may release any resources previously allocated for the same measurement. + +#### 8.13.5.3 Unsuccessful Operation + +Not applicable. + +#### 8.13.5.4 Abnormal Conditions + +If the gNB-DU cannot identify the previously requested measurement to be aborted, it shall ignore the POSITIONING MEASUREMENT ABORT message. + +### 8.13.6 Positioning Measurement Failure Indication + +#### 8.13.6.1 General + +The purpose of the Positioning Measurement Failure Indication procedure is for the gNB-DU to notify the gNB-CU that the positioning measurements previously requested with the Positioning Measurement procedure can no longer be reported. The procedure uses non-UE-associated signalling. + +### 8.13.6.2 Successful Operation + +![Sequence diagram for Positioning Measurement Failure Indication procedure: successful operation. The gNB-DU sends a POSITIONING MEASUREMENT FAILURE INDICATION message to the gNB-CU.](37104233d1b6d7728427e833816594dc_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: POSITIONING MEASUREMENT FAILURE INDICATION + Note right of gNB-CU: +``` + +Sequence diagram for Positioning Measurement Failure Indication procedure: successful operation. The gNB-DU sends a POSITIONING MEASUREMENT FAILURE INDICATION message to the gNB-CU. + +**Figure 8.13.6.2-1: Positioning Measurement Failure Indication procedure: successful operation** + +The gNB-DU initiates the procedure by sending a POSITIONING MEASUREMENT FAILURE INDICATION message. Upon reception of the POSITIONING MEASUREMENT FAILURE INDICATION message, the gNB-CU shall consider that the indicated positioning measurements have been terminated by the gNB-DU. + +### 8.13.6.3 Unsuccessful Operation + +Not applicable. + +### 8.13.6.4 Abnormal Conditions + +Not applicable. + +## 8.13.7 Positioning Measurement Update + +### 8.13.7.1 General + +The purpose of the Positioning Measurement Update procedure is to modify one or more periodic positioning measurements performed by the gNB-DU. The procedure uses non-UE-associated signalling. + +### 8.13.7.2 Successful Operation + +![Sequence diagram for Positioning Measurement Update procedure: successful operation. The gNB-CU sends a POSITIONING MEASUREMENT UPDATE message to the gNB-DU.](949b72d31d7a6d03bc78908260e36d58_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note right of gNB-CU: + gNB-CU->>gNB-DU: POSITIONING MEASUREMENT UPDATE + Note left of gNB-DU: +``` + +Sequence diagram for Positioning Measurement Update procedure: successful operation. The gNB-CU sends a POSITIONING MEASUREMENT UPDATE message to the gNB-DU. + +**Figure 8.13.7.2-1: Positioning Measurement Update procedure: successful operation** + +The gNB-CU initiates the procedure by generating a POSITIONING MEASUREMENT UPDATE message. Upon receiving the message, the gNB-DU shall overwrite the previously received measurement configuration for the corresponding measurements. + +If the *Number of TRP Rx TEGs* IE is included in the *TRP Measurement Update List* IE in the POSITIONING MEASUREMENT UPDATE message, the gNB-DU shall clear any previously stored information and store the newly received information. + +If the *Number of TRP RxTx TEGs* IE is included in the *TRP Measurement Update List* IE in the POSITIONING MEASUREMENT UPDATE message, the gNB-DU shall clear any previously stored information and store the newly received information. + +If the *Measurement Characteristics Request Indicator* IE is included in the POSITIONING MEASUREMENT UPDATE message, the gNB-DU shall clear any previously stored information and store the newly received information. + +If the *Measurement Time Occasion* IE is included in the POSITIONING MEASUREMENT UPDATE message, the gNB-DU shall clear any previously stored information and store the newly received information. + +### 8.13.7.3 Unsuccessful Operation + +Not applicable. + +### 8.13.7.4 Abnormal Conditions + +If the gNB-DU cannot identify the given positioning measurements, it shall regard the procedure as failed and initiate local error handling. + +## 8.13.8 TRP Information Exchange + +### 8.13.8.1 General + +The purpose of the TRP Information Exchange procedure is to allow the gNB-CU to request the gNB-DU to provide detailed information for TRPs hosted by the gNB-DU. The procedure uses non-UE-associated signalling. + +### 8.13.8.2 Successful Operation + +![Sequence diagram of the TRP Information Exchange procedure showing a request from gNB-CU to gNB-DU and a response from gNB-DU to gNB-CU.](ba30b0daaa7f0e5a65b4cd8b19c2bbd7_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: TRP INFORMATION REQUEST + Note right of gNB-DU: + gNB-DU-->>gNB-CU: TRP INFORMATION RESPONSE +``` + +The diagram illustrates the successful operation of the TRP Information Exchange procedure. It features two vertical lifelines: gNB-DU on the left and gNB-CU on the right. The sequence begins with a message labeled 'TRP INFORMATION REQUEST' sent from the gNB-CU lifeline to the gNB-DU lifeline. Following this, a message labeled 'TRP INFORMATION RESPONSE' is sent from the gNB-DU lifeline back to the gNB-CU lifeline. Both lifelines have a thick horizontal bar at the bottom, indicating the end of the sequence or the activation of the entities. + +Sequence diagram of the TRP Information Exchange procedure showing a request from gNB-CU to gNB-DU and a response from gNB-DU to gNB-CU. + +**Figure 8.13.8.2-1: TRP Information Exchange procedure, successful operation** + +The gNB-CU initiates the procedure by sending a TRP INFORMATION REQUEST message. The gNB-DU responds with a TRP INFORMATION RESPONSE message that contains the requested TRP information. + +If the *TRP List* IE is included in the TRP INFORMATION REQUEST message, the gNB-DU should include in the TRP INFORMATION RESPONSE message, the requested information for all TRPs included in the *TRP List* IE. + +If the *TRP List* IE is not included in the TRP INFORMATION REQUEST message, the gNB-DU should include the requested information for all TRPs hosted by the gNB-DU in the TRP INFORMATION RESPONSE message. + +If the *PRS Muting* IE is included in the *PRS Configuration* IE in the TRP INFORMATION RESPONSE message, the gNB-CU may use it for further signaling. + +If the *QCL Info* IE is included in the *PRS Configuration* IE in the TRP INFORMATION RESPONSE message, the gNB-CU may use it for further signaling. + +If the *DL-PRS Resource Coordinates* IE is included in the *Geographical Coordinates* IE in the *TRP Information* IE in the TRP INFORMATION RESPONSE message, the gNB-CU may use it for further signaling. + +If the *Mobile IAB-MT UE ID* IE is included in the *TRP Information* IE in the TRP INFORMATION RESPONSE message, the gNB-CU may use it for further signaling. + +If the *TRP Information Type Item* IE is set to 'mobile TRP location info', the gNB-DU shall, if supported, derive the location of the Mobile TRP as specified in TS 23.273 [49] and include the *Mobile TRP Location Information* in the TRP INFORMATION RESPONSE message. + +### 8.13.8.3 Unsuccessful Operation + +![Sequence diagram showing the TRP Information Exchange procedure for an unsuccessful operation. The gNB-CU sends a TRP INFORMATION REQUEST to the gNB-DU, and the gNB-DU responds with a TRP INFORMATION FAILURE.](1ec8205c17ab05d4670ab9d41b572ec7_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-CU: + gNB-CU->>gNB-DU: TRP INFORMATION REQUEST + Note right of gNB-DU: + gNB-DU-->>gNB-CU: TRP INFORMATION FAILURE +``` + +Sequence diagram showing the TRP Information Exchange procedure for an unsuccessful operation. The gNB-CU sends a TRP INFORMATION REQUEST to the gNB-DU, and the gNB-DU responds with a TRP INFORMATION FAILURE. + +Figure 8.13.8.3-1: TRP Information Exchange procedure, unsuccessful operation + +If the gNB-DU cannot provide any of the requested information, the gNB-DU shall respond with a TRP INFORMATION FAILURE message. + +## 8.13.9 Positioning Information Exchange + +### 8.13.9.1 General + +The Positioning Information Exchange procedure is initiated by the gNB-CU to indicate to the gNB-DU the need to configure the UE to transmit SRS signals and to retrieve the SRS configuration from the gNB-DU. The procedure uses UE-associated signalling. + +### 8.13.9.2 Successful Operation + +![Sequence diagram for Successful Operation of Positioning Information Exchange. The gNB-CU sends a POSITIONING INFORMATION REQUEST to the gNB-DU, and the gNB-DU responds with a POSITIONING INFORMATION RESPONSE.](90321ffa3cade82e4a57d6250d046c88_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: POSITIONING INFORMATION REQUEST + gNB-DU-->>gNB-CU: POSITIONING INFORMATION RESPONSE + Note right of gNB-CU: +``` + +Sequence diagram for Successful Operation of Positioning Information Exchange. The gNB-CU sends a POSITIONING INFORMATION REQUEST to the gNB-DU, and the gNB-DU responds with a POSITIONING INFORMATION RESPONSE. + +**Figure 8.13.9.2-1: Positioning Information Exchange procedure, successful operation** + +The gNB-CU initiates the procedure by sending a POSITIONING INFORMATION REQUEST message to the gNB-DU. + +If the *Requested SRS Transmission Characteristics* IE is included in the POSITIONING INFORMATION REQUEST message, the gNB-DU may take this information into account when configuring SRS transmissions for the UE, and it shall include the *SRS Configuration* IE and the *SFN Initialisation Time* IE in the POSITIONING INFORMATION RESPONSE message. If the *SRS Positioning INACTIVE Query Indication* IE is also included in the POSITIONING INFORMATION REQUEST message and set to 'true', the gNB-DU shall, if supported, include the *SRS-PosRRC-InactiveConfig* IE in the POSITIONING INFORMATION RESPONSE message. + +If the *Spatial Relation Information per SRS Resource* IE and the *Periodicity List* IE are both included in the *Requested SRS Transmission Characteristics* IE, the gNB-DU shall consider that the *Spatial Relation per SRS Resource Item* IE and the *Periodicity List Item* IE have one-to-one mapping relation. + +If the *UE Reporting Information* IE is included in the POSITIONING INFORMATION REQUEST message, the gNB-DU may take this information into account for allocating proper CG-SDT resources when positioning a UE. + +#### **Interaction with the UE Context Modification Required (gNB-DU initiated) procedure:** + +The UE Context Modification Required (gNB-DU initiated) procedure may be performed before the POSITIONING INFORMATION RESPONSE message. + +### 8.13.9.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Operation of Positioning Information Exchange. The gNB-CU sends a POSITIONING INFORMATION REQUEST to the gNB-DU, and the gNB-DU responds with a POSITIONING INFORMATION FAILURE.](c973a830a03be42682a331ad3215d6c6_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: POSITIONING INFORMATION REQUEST + gNB-DU-->>gNB-CU: POSITIONING INFORMATION FAILURE + Note right of gNB-CU: +``` + +Sequence diagram for Unsuccessful Operation of Positioning Information Exchange. The gNB-CU sends a POSITIONING INFORMATION REQUEST to the gNB-DU, and the gNB-DU responds with a POSITIONING INFORMATION FAILURE. + +**Figure 8.13.9.3-1: Positioning Information Exchange procedure, unsuccessful operation** + +If the *Requested SRS Transmission Characteristics* IE is included in the POSITIONING INFORMATION REQUEST message and the gNB-DU is unable to configure any SRS transmissions for the UE, the gNB-DU shall respond with a POSITIONING INFORMATION FAILURE message with an appropriate cause value. + +If the gNB-DU is unable to provide any of the requested information, the gNB-DU shall respond with a POSITIONING INFORMATION FAILURE message with an appropriate cause value. + +## 8.13.10 Positioning Activation + +### 8.13.10.1 General + +The Positioning Activation procedure is initiated by the gNB-CU to request the gNB-DU to activate semi-persistent or trigger aperiodic UL SRS transmission by the UE. The procedure uses UE-associated signalling. + +### 8.13.10.2 Successful Operation + +![Sequence diagram for successful Positioning Activation procedure](6e50e3275fbdccd63dc258477b94bef6_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: POSITIONING ACTIVATION REQUEST + Note right of gNB-CU: + gNB-DU-->>gNB-CU: POSITIONING ACTIVATION RESPONSE + Note left of gNB-DU: +``` + +The diagram shows a sequence of messages between the gNB-CU and the gNB-DU. The gNB-CU sends a 'POSITIONING ACTIVATION REQUEST' message to the gNB-DU. The gNB-DU responds with a 'POSITIONING ACTIVATION RESPONSE' message. Both entities are represented by boxes with lifelines extending downwards, and there are horizontal bars at the bottom of each lifeline. + +Sequence diagram for successful Positioning Activation procedure + +Figure 8.13.10.2-1: Positioning Activation procedure, successful operation + +The gNB-CU initiates the procedure by sending a POSITIONING ACTIVATION REQUEST message to the gNB-DU. + +For semi-persistent UL SRS, the POSITIONING ACTIVATION REQUEST message includes an indication of the UL SRS resource set to be activated, and may include the spatial relation for the semi-persistent UL SRS resource to be activated. For aperiodic UL SRS, if the *SRS Resource Trigger* IE is included in the POSITIONING ACTIVATION REQUEST message, the gNB-DU shall take the value of this IE into account when triggering aperiodic SRS transmission by the UE. + +If the *Activation Time* IE is included in the POSITIONING ACTIVATION REQUEST message, the gNB-DU shall take the indicated value as the requested time for activation of the UE's SRS transmission. + +Following successful activation of UL SRS transmission in the UE, the gNB-DU shall respond with a POSITIONING ACTIVATION RESPONSE message. If the POSITIONING ACTIVATION RESPONSE message includes the *System Frame Number* and/or the *Slot Number* IEs, the gNB-CU shall consider that the respective information indicates the activation time of SRS transmission by the UE. + +### 8.13.10.3 Unsuccessful Operation + +![Sequence diagram for unsuccessful Positioning Activation procedure](da0e559eb2a247b221a69ce5f49f3b49_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: POSITIONING ACTIVATION REQUEST + Note right of gNB-CU: + gNB-DU-->>gNB-CU: POSITIONING ACTIVATION FAILURE + Note left of gNB-DU: +``` + +The diagram shows a sequence of messages between the gNB-CU and the gNB-DU. The gNB-CU sends a 'POSITIONING ACTIVATION REQUEST' message to the gNB-DU. The gNB-DU responds with a 'POSITIONING ACTIVATION FAILURE' message. Both entities are represented by boxes with lifelines extending downwards, and there are horizontal bars at the bottom of each lifeline. + +Sequence diagram for unsuccessful Positioning Activation procedure + +Figure 8.13.10.3-1: Positioning Activation procedure, unsuccessful operation + +If the gNB-DU is unable to activate UL SRS transmission in the UE, it shall respond with a POSITIONING ACTIVATION FAILURE message. + +If the gNB-DU is unable to trigger the aperiodic SRS transmission with the indicated *SRS Resource Trigger* IE, it shall respond with a POSITIONING ACTIVATION FAILURE message with an appropriate cause value + +#### 8.13.10.4 Abnormal Conditions + +Void. + +### 8.13.11 Positioning Deactivation + +#### 8.13.11.1 General + +The Positioning Deactivation procedure is initiated by the gNB-CU to indicate to the gNB-DU node that UL SRS transmission should be deactivated in the UE. The procedure uses UE-associated signalling. + +#### 8.13.11.2 Successful Operation + +![Sequence diagram showing the successful operation of the Positioning Deactivation procedure. A gNB-CU sends a POSITIONING DEACTIVATION message to a gNB-DU.](d21ff621d2cff0d2b4b5a97009b23eb3_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note right of gNB-CU: + gNB-CU->>gNB-DU: POSITIONING DEACTIVATION + Note left of gNB-DU: + activate gNB-DU + deactivate gNB-DU +``` + +The diagram illustrates the successful operation of the Positioning Deactivation procedure. It shows two entities: gNB-DU and gNB-CU. A horizontal arrow labeled "POSITIONING DEACTIVATION" points from the gNB-CU to the gNB-DU. Both entities are represented by boxes with vertical lines extending downwards to a horizontal bar, indicating the start of a sequence or activation. + +Sequence diagram showing the successful operation of the Positioning Deactivation procedure. A gNB-CU sends a POSITIONING DEACTIVATION message to a gNB-DU. + +Figure 8.13.11.2-1: Positioning Deactivation procedure, successful operation + +The gNB-CU initiates the procedure by sending a POSITIONING DEACTIVATION message to the gNB-DU, including an indication of the UL SRS resources to be deactivated. + +#### 8.13.11.3 Unsuccessful Operation + +Not Applicable. + +#### 8.13.11.4 Abnormal Conditions + +Void. + +### 8.13.12 E-CID Measurement Initiation + +#### 8.13.12.1 General + +The purpose of E-CID Measurement Initiation procedure is to allow the gNB-CU to request the gNB-DU to report E-CID measurements used by LMF to compute the location of the UE. The procedure uses UE-associated signalling. + +### 8.13.12.2 Successful Operation + +![Sequence diagram for successful E-CID measurement initiation. The gNB-CU sends an E-CID MEASUREMENT INITIATION REQUEST to the gNB-DU, and the gNB-DU responds with an E-CID MEASUREMENT INITIATION RESPONSE.](132ad076dd59b60fd549f7a612ed568b_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: E-CID MEASUREMENT INITIATION REQUEST + gNB-DU-->>gNB-CU: E-CID MEASUREMENT INITIATION RESPONSE + Note right of gNB-CU: +``` + +Sequence diagram for successful E-CID measurement initiation. The gNB-CU sends an E-CID MEASUREMENT INITIATION REQUEST to the gNB-DU, and the gNB-DU responds with an E-CID MEASUREMENT INITIATION RESPONSE. + +**Figure 8.13.12.2-1: E-CID Measurement Initiation procedure, successful operation** + +The gNB-CU initiates the procedure by sending an E-CID MEASUREMENT INITIATION REQUEST message. If the gNB-DU is able to initiate the requested E-CID measurements, it shall reply with the E-CID MEASUREMENT INITIATION RESPONSE message. + +If the *E-CID Report Characteristics* IE is set to "OnDemand", the gNB-DU shall return the result of the measurement in the E-CID MEASUREMENT INITIATION RESPONSE message including, if available, the *Geographical Coordinates* IE in the *E-CID Measurement Result* IE and the *Cell Portion ID* IE, and the gNB-CU shall consider that the E-CID measurements for the UE have been terminated by the gNB-DU. The *Measured Results List* IE shall be included in the *E-CID Measurement Result* IE of the E-CID MEASUREMENT INITIATION RESPONSE message when measurement quantities other than "Default" have been requested. + +#### Interaction with the E-CID Measurement Report procedure: + +If the *E-CID Report Characteristics* IE is set to "Periodic", the gNB-DU shall initiate the requested measurements and shall reply with the E-CID MEASUREMENT INITIATION RESPONSE message without including either the *E-CID Measurement Result* IE or the *Cell Portion ID* IE in this message. The gNB-DU shall then periodically initiate the E-CID Measurement Report procedure for the measurements, with the requested reporting periodicity. + +### 8.13.12.3 Unsuccessful Operation + +![Sequence diagram for unsuccessful E-CID measurement initiation. The gNB-CU sends an E-CID MEASUREMENT INITIATION REQUEST to the gNB-DU, and the gNB-DU responds with an E-CID MEASUREMENT INITIATION FAILURE.](727f170860008f2b6de39e96e5a03ced_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: E-CID MEASUREMENT INITIATION REQUEST + gNB-DU-->>gNB-CU: E-CID MEASUREMENT INITIATION FAILURE + Note right of gNB-CU: +``` + +Sequence diagram for unsuccessful E-CID measurement initiation. The gNB-CU sends an E-CID MEASUREMENT INITIATION REQUEST to the gNB-DU, and the gNB-DU responds with an E-CID MEASUREMENT INITIATION FAILURE. + +**Figure 8.13.12.3-1: E-CID Measurement Initiation procedure, unsuccessful operation** + +If the gNB-DU is not able to initiate at least one of the requested E-CID measurements, the gNB-DU shall respond with an E-CID MEASUREMENT INITIATION FAILURE message. + +## 8.13.13 E-CID Measurement Failure Indication + +### 8.13.13.1 General + +The purpose of the E-CID Measurement Failure Indication procedure is for the gNB-DU to notify the gNB-CU that the E-CID measurements previously requested with the E-CID Measurement Initiation procedure can no longer be reported. The procedure uses UE-associated signalling. + +### 8.13.13.2 Successful Operation + +![Sequence diagram showing the successful operation of the E-CID Measurement Failure Indication procedure. A gNB-DU sends an E-CID MEASUREMENT FAILURE INDICATION message to a gNB-CU.](bdbdf9152f5224e9ced4fc6f402fbe45_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: E-CID MEASUREMENT FAILURE INDICATION + Note right of gNB-CU: +``` + +Sequence diagram showing the successful operation of the E-CID Measurement Failure Indication procedure. A gNB-DU sends an E-CID MEASUREMENT FAILURE INDICATION message to a gNB-CU. + +**Figure 8.13.13.2-1: E-CID Measurement Failure Indication, successful operation** + +The gNB-DU initiates the procedure by sending an E-CID MEASUREMENT FAILURE INDICATION message. Upon reception of the E-CID MEASUREMENT FAILURE INDICATION message, the gNB-CU shall consider that the E-CID measurements for the UE have been terminated by the gNB-DU. + +### 8.13.13.3 Unsuccessful Operation + +Not applicable. + +## 8.13.14 E-CID Measurement Report + +### 8.13.14.1 General + +The purpose of E-CID Measurement Report procedure is for the gNB-DU to provide the E-CID measurements for the UE to the gNB-CU. The procedure uses UE-associated signalling. + +### 8.13.14.2 Successful Operation + +![Sequence diagram showing the successful operation of the E-CID Measurement Report procedure. A gNB-DU sends an E-CID MEASUREMENT REPORT message to a gNB-CU.](7a55c91aeff72a180a89e462c5c9f591_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: E-CID MEASUREMENT REPORT + Note right of gNB-CU: +``` + +Sequence diagram showing the successful operation of the E-CID Measurement Report procedure. A gNB-DU sends an E-CID MEASUREMENT REPORT message to a gNB-CU. + +**Figure 8.13.14.2-1: E-CID Measurement Report procedure, successful operation** + +The gNB-DU initiates the procedure by sending an E-CID MEASUREMENT REPORT message. The E-CID MEASUREMENT REPORT message contains the E-CID measurement results according to the measurement configuration in the respective E-CID MEASUREMENT INITIATION REQUEST message. + +The *Measured Results List* IE shall be included in the *E-CID Measurement Result* IE of the E-CID MEASUREMENT REPORT message when measurement quantities other than "Default" have been requested. + +If available, the gNB-DU shall include the *Geographical Coordinates* IE in the *E-CID Measurement Result* IE in the E-CID MEASUREMENT REPORT message. + +If available, the gNB-DU shall include the *Cell Portion ID* IE in the E-CID MEASUREMENT REPORT message. + +If available, the gNB-DU shall include the *Mobile Access Point Location Information* IE in the E-CID MEASUREMENT REPORT message. + +#### 8.13.14.3 Unsuccessful Operation + +Not applicable. + +### 8.13.15 E-CID Measurement Termination + +#### 8.13.15.1 General + +The purpose of E-CID Measurement Termination procedure is to terminate periodical E-CID measurements for the UE performed by the gNB-DU. The procedure uses UE-associated signalling. + +#### 8.13.15.2 Successful Operation + +![Sequence diagram showing the E-CID Measurement Termination procedure. A gNB-CU sends an E-CID MEASUREMENT TERMINATION COMMAND message to a gNB-DU.](b6cee7c106abafe0c3160e285cd68389_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + Note right of gNB-CU: + gNB-CU->>gNB-DU: E-CID MEASUREMENT TERMINATION COMMAND + Note left of gNB-DU: + Note right of gNB-CU: +``` + +Sequence diagram showing the E-CID Measurement Termination procedure. A gNB-CU sends an E-CID MEASUREMENT TERMINATION COMMAND message to a gNB-DU. + +Figure 8.13.15.2-1: E-CID Measurement Termination procedure, successful operation + +The gNB-CU initiates the procedure by generating an E-CID MEASUREMENT TERMINATION COMMAND message. + +#### 8.13.15.3 Unsuccessful Operation + +Not applicable. + +### 8.13.16 Positioning Information Update + +#### 8.13.16.1 General + +The Positioning Information Update procedure is initiated by the gNB-DU to indicate to the gNB-CU that a change has occurred in the SRS configuration. The procedure uses UE-associated signalling. + +### 8.13.16.2 Successful Operation + +![Sequence diagram for Positioning Information Update procedure, successful operation. It shows a gNB-DU sending a POSITIONING INFORMATION UPDATE message to a gNB-CU.](56f125e1bc127f7ac3d210407957413c_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: POSITIONING INFORMATION UPDATE + Note right of gNB-CU: +``` + +Sequence diagram for Positioning Information Update procedure, successful operation. It shows a gNB-DU sending a POSITIONING INFORMATION UPDATE message to a gNB-CU. + +**Figure 8.13.16.2-1: Positioning Information Update procedure, successful operation** + +The gNB-DU initiates the procedure by sending a POSITIONING INFORMATION UPDATE message to the gNB-CU. + +If the SRS Configuration IE is included in the POSITIONING INFORMATION UPDATE message, the gNB-CU shall consider this information as the updated SRS Configuration for the UE. If the *SFN Initialisation Time* IE is included in the POSITIONING INFORMATION UPDATE message, the gNB-CU shall consider this information as the SFN Initialisation Time associated to the SRS Configuration. + +### 8.13.16.3 Unsuccessful Operation + +Not Applicable. + +### 8.13.16.4 Abnormal Conditions + +Void. + +## 8.13.17 PRS Configuration Exchange + +### 8.13.17.1 General + +The PRS Configuration Exchange procedure is initiated by the gNB-CU to request the gNB-DU to configure or update (i.e., turn off) the PRS transmissions. + +The procedure uses non-UE-associated signalling. + +### 8.13.17.2 Successful Operation + +![Sequence diagram for PRS Configuration Exchange procedure, successful operation. It shows a gNB-CU sending a PRS CONFIGURATION REQUEST message to a gNB-DU, and the gNB-DU responding with a PRS CONFIGURATION RESPONSE message.](131668780aa094876183923cf648e438_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-CU->>gNB-DU: PRS CONFIGURATION REQUEST + gNB-DU-->>gNB-CU: PRS CONFIGURATION RESPONSE + Note right of gNB-CU: +``` + +Sequence diagram for PRS Configuration Exchange procedure, successful operation. It shows a gNB-CU sending a PRS CONFIGURATION REQUEST message to a gNB-DU, and the gNB-DU responding with a PRS CONFIGURATION RESPONSE message. + +**Figure 8.13.17.2-1: PRS Configuration Exchange procedure, successful operation** + +The gNB-CU initiates the procedure by sending a PRS CONFIGURATION REQUEST message to the gNB-DU. + +If the *PRS Configuration Request Type* IE is set to “configure”, the gNB-DU should use the information in the *Requested DL PRS Transmission Characteristics* IE to configure DL-PRS transmission by the indicated TRP(s). + +If the *PRS Configuration Request Type* IE is set to “off”, the gNB-DU should, if supported, use the information in the *PRS Transmission Off Information* IE to turn off the DL-PRS transmission for the indicated TRP(s), PRS Resource Set(s), or PRS Resource(s). + +If DL-PRS transmission is successfully configured or updated for at least one of the TRPs, the gNB-DU shall respond with the PRS CONFIGURATION RESPONSE message. + +### 8.13.17.3 Unsuccessful Operation + +![Sequence diagram for PRS Configuration Exchange procedure, unsuccessful operation](4e3bce0b4a3062f7f237acd0b04e5c66_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-CU->>gNB-DU: PRS CONFIGURATION REQUEST + Note right of gNB-CU: + gNB-DU-->>gNB-CU: PRS CONFIGURATION FAILURE + Note left of gNB-DU: +``` + +The diagram shows a sequence of messages between a gNB-DU and a gNB-CU. The gNB-CU sends a 'PRS CONFIGURATION REQUEST' message to the gNB-DU. The gNB-DU responds with a 'PRS CONFIGURATION FAILURE' message. Both entities are represented by boxes with lifelines extending downwards, and the messages are indicated by horizontal arrows. + +Sequence diagram for PRS Configuration Exchange procedure, unsuccessful operation + +Figure 8.13.17.3-1: PRS Configuration Exchange procedure, unsuccessful operation + +If the gNB-DU cannot configure or update DL-PRS transmission for any of the TRPs in the *PRS TRP List* IE of the PRS CONFIGURATION REQUEST message, it shall respond with a PRS CONFIGURATION FAILURE message with an appropriate cause value. + +### 8.13.17.4 Abnormal Conditions + +Void. + +## 8.13.18 Measurement Preconfiguration + +### 8.13.18.1 General + +The Measurement Preconfiguration procedure allows the gNB-CU to provide necessary information to the serving gNB-DU and request the gNB-DU to preconfigure measurement gap and/or PRS processing window of the UE. + +### 8.13.18.2 Successful Operation + +![Sequence diagram for Measurement Preconfiguration procedure, successful operation](ea105825edba5fe5123a980361334798_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-CU->>gNB-DU: MEASUREMENT PRECONFIGURATION REQUIRED + Note right of gNB-CU: + gNB-DU-->>gNB-CU: MEASUREMENT PRECONFIGURATION CONFIRM + Note left of gNB-DU: +``` + +The diagram shows a sequence of messages between a gNB-DU and a gNB-CU. The gNB-CU sends a 'MEASUREMENT PRECONFIGURATION REQUIRED' message to the gNB-DU. The gNB-DU responds with a 'MEASUREMENT PRECONFIGURATION CONFIRM' message. Both entities are represented by boxes with lifelines extending downwards, and the messages are indicated by horizontal arrows. + +Sequence diagram for Measurement Preconfiguration procedure, successful operation + +Figure 8.13.18.2-1: Measurement Preconfiguration procedure, successful operation + +The gNB-CU initiates the procedure by sending a MEASUREMENT PRECONFIGURATION REQUIRED message. + +If the gNB-DU is able to configure measurement gap or PRS processing window, it shall reply with the MEASUREMENT PRECONFIGURATION CONFIRM message. + +If the *PosMeasGapPreConfigList* IE is included in the MEASUREMENT PRECONFIGURATION CONFIRM message, the gNB-CU shall, if supported, take the preconfigured measurement gaps information into account. + +### 8.13.18.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Operation of Measurement Preconfiguration procedure.](f0addfb9cb95476594c62d37d1208037_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: MEASUREMENT PRECONFIGURATION REQUIRED + Note right of gNB-CU: + gNB-DU-->>gNB-CU: MEASUREMENT PRECONFIGURATION REFUSE + Note left of gNB-DU: +``` + +The diagram shows a sequence of messages between the gNB-CU and the gNB-DU. The gNB-CU sends a 'MEASUREMENT PRECONFIGURATION REQUIRED' message to the gNB-DU. The gNB-DU responds with a 'MEASUREMENT PRECONFIGURATION REFUSE' message. Both entities are represented by boxes with vertical lines extending downwards to horizontal bars, indicating their respective timelines. + +Sequence diagram for Unsuccessful Operation of Measurement Preconfiguration procedure. + +**Figure 8.13.18.3-1: Measurement Preconfiguration procedure, unsuccessful operation** + +If the gNB-DU cannot configure any of the measurement gap or PRS processing window, the gNB-DU shall respond with a MEASUREMENT PRECONFIGURATION REFUSE message. + +## 8.13.19 Measurement Activation + +### 8.13.19.1 General + +The Measurement Activation procedure is initiated by the gNB-CU to request the gNB-DU to activate or deactivate the preconfigured measurement gap or PRS processing window for the UE. + +### 8.13.19.2 Successful Operation + +![Sequence diagram for Successful Operation of Measurement Activation procedure.](66d5189a924662748cac6a9b22a272e9_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: MEASUREMENT ACTIVATION + Note right of gNB-CU: + gNB-DU-->>gNB-CU: + Note left of gNB-DU: +``` + +The diagram shows a sequence of messages between the gNB-CU and the gNB-DU. The gNB-CU sends a 'MEASUREMENT ACTIVATION' message to the gNB-DU. The gNB-DU responds with a return message, indicated by a dashed arrow. Both entities are represented by boxes with vertical lines extending downwards to horizontal bars, indicating their respective timelines. + +Sequence diagram for Successful Operation of Measurement Activation procedure. + +**Figure 8.13.19.2-1: Measurement Activation procedure, successful operation** + +The gNB-CU initiates the procedure by sending a MEASUREMENT ACTIVATION message. + +If the *PRS Measurement Info List* IE is included in the MEASUREMENT ACTIVATION message, the gNB-DU may take it into account when activating pre-configured measurement gap in the UE. + +### 8.13.19.3 Unsuccessful Operation + +Not Applicable. + +## 8.13.20 Positioning System Information Delivery + +### 8.13.20.1 General + +The purpose of the Positioning System Information Delivery procedure is to command the gNB-DU to broadcast the requested one or several Positioning SI messages indicated by the gNB-CU. The procedure uses non-UE associated signalling. + +### 8.13.20.2 Successful Operation + +![Sequence diagram showing the successful operation of the Positioning System Information Delivery procedure. A gNB-CU sends a POSITIONING SYSTEM INFORMATION DELIVERY COMMAND message to a gNB-DU.](435cf83a9531da350ea543aafa0add62_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-CU: + gNB-CU->>gNB-DU: POSITIONING SYSTEM INFORMATION DELIVERY COMMAND + Note right of gNB-DU: + activate gNB-DU + Note right of gNB-DU: Broadcast Positioning SI messages + deactivate gNB-DU +``` + +Sequence diagram showing the successful operation of the Positioning System Information Delivery procedure. A gNB-CU sends a POSITIONING SYSTEM INFORMATION DELIVERY COMMAND message to a gNB-DU. + +**Figure 8.13.20.2-1: Positioning System Information Delivery procedure. Successful operation.** + +The gNB-CU initiates the procedure by sending a POSITIONING SYSTEM INFORMATION DELIVERY COMMAND message to the gNB-DU. + +Upon reception of the POSITIONING SYSTEM INFORMATION DELIVERY COMMAND message, the gNB-DU shall broadcast the requested one or several Positioning SI messages, indicated by the *PosSITypeList* IE, and delete the UE context corresponding to the *Confirmed UE ID* IE, if any. + +#### **Interactions with gNB-DU Configuration Update procedure:** + +Upon reception of POSITIONING SYSTEM INFORMATION DELIVERY COMMAND message, the gNB-DU Configuration Update procedure may be performed, and as part of such procedure the gNB-DU shall include the *Dedicated SI Delivery Needed UE List* IE in GNB-DU CONFIGURATION UPDATE message for UEs that are unable to receive system information from broadcast. + +### 8.13.20.3 Abnormal Conditions + +Not applicable. + +## 8.14 NR MBS Procedures + +### 8.14.1 Broadcast Context Setup + +#### 8.14.1.1 General + +The purpose of the Broadcast Context Setup procedure is to establish an MBS Session context for a broadcast session in the gNB-DU. + +The procedure uses MBS-associated signalling. + +### 8.14.1.2 Successful Operation + +![Sequence diagram showing the Broadcast Context Setup procedure between gNB-DU and gNB-CU. The gNB-CU sends a BROADCAST CONTEXT SETUP REQUEST to the gNB-DU, and the gNB-DU responds with a BROADCAST CONTEXT SETUP RESPONSE.](48090d8f1db2e826aaa740035aa12ecb_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-CU: gNB-CU initiates procedure + gNB-CU->>gNB-DU: BROADCAST CONTEXT SETUP REQUEST + Note right of gNB-DU: gNB-DU succeeds + gNB-DU-->>gNB-CU: BROADCAST CONTEXT SETUP RESPONSE + +``` + +Sequence diagram showing the Broadcast Context Setup procedure between gNB-DU and gNB-CU. The gNB-CU sends a BROADCAST CONTEXT SETUP REQUEST to the gNB-DU, and the gNB-DU responds with a BROADCAST CONTEXT SETUP RESPONSE. + +**Figure 8.14.1.2-1: Broadcast Context Setup procedure: Successful Operation** + +The gNB-CU initiates the procedure by sending BROADCAST CONTEXT SETUP REQUEST message to the gNB-DU. If the gNB-DU succeeds to establish the broadcast MBS Session context, it replies to the gNB-CU with BROADCAST CONTEXT SETUP RESPONSE. + +If the *MBS Service Area* IE is included in the BROADCAST CONTEXT SETUP REQUEST message, the gNB-DU shall take this information into account for shared F1-U tunnel assignment. + +The gNB-DU shall report to the gNB-CU, in the BROADCAST CONTEXT SETUP RESPONSE message, the result of all the requested Broadcast MRBs in the following way: + +- A list of MRBs which have been successfully established shall be included in the *Broadcast MRB Setup List* IE; +- A list of MRBs which failed to be established shall be included in the *Broadcast MRB Failed To Be Setup List* IE; + +If the *Broadcast MRB Failed To Setup List* IE is contained in the BROADCAST CONTEXT SETUP RESPONSE message, the gNB-CU shall regard the Broadcast MRB(s) failed to be setup with an appropriate cause value for each Broadcast MRB failed to setup. + +If + +- either the *MBS Service Area* IE was included in the BROADCAST CONTEXT SETUP REQUEST message, +- or the the *MBS Service Area* IE was not included in the BROADCAST CONTEXT SETUP REQUEST message and the gNB-DU was not able to establish MBS Session Resources in all cells served by the gNB-DU, + +the *Broadcast Area Scope* IE shall be included in the BROADCAST CONTEXT SETUP RESPONSE message to indicate the cells where MBS Session resources have been successfully established in the gNB-DU. + +If the *Supported UE Type List* IE is included in the BROADCAST CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, store and use the information for configuring MBS session resources. + +If the *Associated Session ID* IE is contained in the BROADCAST CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take this information into account to determine whether MBS session resource sharing is possible, as specified in TS 38.401 [4]. If the gNB-DU decides to not establish F1-U tunnel towards the gNB-CU it shall include the *F1-U tunnel Not Established* IE set to "true" in the BROADCAST CONTEXT SETUP RESPONSE message. + +### 8.14.1.3 Unsuccessful Operation + +![Sequence diagram for Broadcast Context Setup procedure: unsuccessful Operation](da87c1b628b63a046d8a0d0fc2c058ea_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: BROADCAST CONTEXT SETUP REQUEST + Note right of gNB-CU: + gNB-DU-->>gNB-CU: BROADCAST CONTEXT SETUP FAILURE + Note right of gNB-DU: +``` + +The diagram shows a sequence of messages between a gNB-CU and a gNB-DU. The gNB-CU sends a 'BROADCAST CONTEXT SETUP REQUEST' to the gNB-DU. The gNB-DU responds with a 'BROADCAST CONTEXT SETUP FAILURE' message. Both entities are represented by boxes with lifelines extending downwards, and there are solid black bars at the bottom of each lifeline. + +Sequence diagram for Broadcast Context Setup procedure: unsuccessful Operation + +**Figure 8.14.1.3-1: Broadcast Context Setup procedure: unsuccessful Operation** + +If the gNB-DU is not able to establish the requested MBS session context for all the MRBs in any of its cells it shall consider the procedure as failed and reply with the BROADCAST CONTEXT SETUP FAILURE message. + +### 8.14.1.4 Abnormal Conditions + +Not applicable. + +## 8.14.2 Broadcast Context Release + +### 8.14.2.1 General + +The purpose of the Broadcast Context Release procedure is to enable the gNB-CU to order the release of an established MBS Session context for a broadcast session in the gNB-DU. + +The procedure uses MBS-associated signalling. + +### 8.14.2.2 Successful Operation + +![Sequence diagram for Broadcast Context Release procedure. Successful operation](5cce7ed287fbd2f458757874de049f7d_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-CU: + gNB-CU->>gNB-DU: BROADCAST CONTEXT RELEASE COMMAND + Note right of gNB-CU: + gNB-DU-->>gNB-CU: BROADCAST CONTEXT RELEASE COMPLETE + Note right of gNB-DU: +``` + +The diagram shows a sequence of messages between a gNB-CU and a gNB-DU. The gNB-CU sends a 'BROADCAST CONTEXT RELEASE COMMAND' to the gNB-DU. The gNB-DU responds with a 'BROADCAST CONTEXT RELEASE COMPLETE' message. Both entities are represented by boxes with lifelines extending downwards, and there are solid black bars at the bottom of each lifeline. + +Sequence diagram for Broadcast Context Release procedure. Successful operation + +**Figure 8.14.2.2-1: Broadcast Context Release procedure. Successful operation** + +The gNB-CU initiates the procedure by sending the BROADCAST CONTEXT RELEASE COMMAND message to the gNB-DU. + +Upon reception of the BROADCAST CONTEXT RELEASE COMMAND message, the gNB-DU shall release all signalling and user data transport resources associated with the context and reply with the BROADCAST CONTEXT RELEASE COMPLETE message. + +### 8.14.2.3 Unsuccessful Operation + +Not applicable. + +### 8.14.2.4 Abnormal Conditions + +Not applicable. + +## 8.14.3 Broadcast Context Release Request + +### 8.14.3.1 General + +The purpose of the Broadcast Context Release Request procedure is to request the gNB-CU to trigger the Broadcast Context Release procedure. + +The procedure uses MBS-associated signalling. + +### 8.14.3.2 Successful Operation + +![Sequence diagram showing the successful operation of the Broadcast Context Release Request procedure. The gNB-DU sends a BROADCAST CONTEXT RELEASE REQUEST message to the gNB-CU.](4c4c756d9c3797fc23d861bc37d2d63d_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: BROADCAST CONTEXT RELEASE REQUEST + Note right of gNB-CU: +``` + +The diagram illustrates a sequence of interactions between two network entities: gNB-DU and gNB-CU. The gNB-DU is shown on the left and the gNB-CU on the right. A horizontal arrow points from the gNB-DU to the gNB-CU, labeled "BROADCAST CONTEXT RELEASE REQUEST". Both entities are represented by a vertical line (lifeline) extending from a box at the top to a thick horizontal bar at the bottom. + +Sequence diagram showing the successful operation of the Broadcast Context Release Request procedure. The gNB-DU sends a BROADCAST CONTEXT RELEASE REQUEST message to the gNB-CU. + +**Figure 8.14.3.2-1: Broadcast Context Release Request procedure. Successful operation** + +The gNB-DU initiates the procedure by sending the BROADCAST CONTEXT RELEASE REQUEST message to the gNB-CU. + +#### **Interaction with the Broadcast Context Release procedure:** + +Upon reception of the BROADCAST CONTEXT RELEASE REQUEST message, the gNB-CU should trigger the Broadcast Context Release procedure. + +### 8.14.3.3 Unsuccessful Operation + +Not applicable. + +### 8.14.3.4 Abnormal Conditions + +Not applicable. + +## 8.14.4 Broadcast Context Modification + +### 8.14.4.1 General + +The purpose of the Broadcast Context Modification procedure is to modify an established MBS Session context for a broadcast session in the gNB-DU. + +The procedure uses MBS-associated signalling. + +#### 8.14.4.2 Successful Operation + +![Sequence diagram showing the Broadcast Context Modification procedure. The gNB-CU sends a BROADCAST CONTEXT MODIFICATION REQUEST to the gNB-DU, and the gNB-DU responds with a BROADCAST CONTEXT MODIFICATION RESPONSE.](9d47fe89bc71acebde670ea760ee6ffb_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: BROADCAST CONTEXT MODIFICATION REQUEST + gNB-DU-->>gNB-CU: BROADCAST CONTEXT MODIFICATION RESPONSE + Note right of gNB-CU: + +``` + +Sequence diagram showing the Broadcast Context Modification procedure. The gNB-CU sends a BROADCAST CONTEXT MODIFICATION REQUEST to the gNB-DU, and the gNB-DU responds with a BROADCAST CONTEXT MODIFICATION RESPONSE. + +**Figure 8.14.4.2-1: Broadcast Context Modification procedure. Successful operation** + +The BROADCAST CONTEXT MODIFICATION REQUEST message is initiated by the gNB-CU. + +Upon reception of the BROADCAST CONTEXT MODIFICATION REQUEST message, the gNB-DU shall perform the modifications, and, if successful, report the update in the BROADCAST CONTEXT MODIFICATION RESPONSE message. + +If the *Broadcast MRB To Be Setup List* IE is contained in the BROADCAST CONTEXT MODIFICATION REQUEST message, the gNB-DU shall setup the corresponding resources for the requested MRB(s), and report to the gNB-CU, in the BROADCAST CONTEXT MODIFICATION RESPONSE message, the result of all the requested Broadcast MRBs in the following way: + +- A list of MRBs which have been successfully established shall be included in the *Broadcast MRB Setup List* IE; +- A list of MRBs which failed to be established shall be included in the *Broadcast MRB Failed To Be Setup List* IE; + +If the *Broadcast MRB Failed To Be Setup List* IE is contained in the BROADCAST CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall regard the setup of the indicated MRB(s) as failed and indicate the reason for the failure with an appropriate cause value for each MRB failed to be setup. + +If the *Broadcast MRB To Be Modified List* IE is contained in the BROADCAST CONTEXT MODIFICATION REQUEST message, the gNB-DU shall update the corresponding context and resources for the requested MRB(s), and report to the gNB-CU, in the BROADCAST CONTEXT MODIFICATION RESPONSE message, the modification result of all the requested Broadcast MRBs in the following way: + +- A list of MRBs which have been successfully modified shall be included in the *Broadcast MRB Modified List* IE; +- A list of MRBs which failed to be modified shall be included in the *Broadcast MRB Failed To Be Modified List* IE; + +If the *Broadcast MRB Failed To Be Modified List* IE is contained in the BROADCAST CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall regard the Broadcast MRB(s) failed to be modified with an appropriate cause value for each Broadcast MRB failed to modify. + +If the *MBS Service Area* IE is included in the BROADCAST CONTEXT MODIFICATION REQUEST message, the gNB-DU shall + +- release MBS Session Resources within cells not contained in the *MBS Service Area* IE, if any; + +- establish MBS Session Resources within cells which have not been contained in MBS Service Area information previously received; +- replace MBS Service Area information previously received with information received in the *MBS Service Area* IE included in the BROADCAST CONTEXT MODIFICATION REQUEST message; +- include the *Broadcast Area Scope* IE in the BROADCAST CONTEXT MODIFICATION RESPONSE message to indicate the cells where MBS Session resources are currently established in the gNB-DU. + +If the *MBS Service Area* IE was not included in the BROADCAST CONTEXT MODIFICATION REQUEST message and the gNB-DU has released MBS Session Resources within at least one cell or has established MBS Session Resources within at least one cell the gNB-DU shall include the *Broadcast Area Scope* IE in the BROADCAST CONTEXT MODIFICATION RESPONSE message to indicate the cells where MBS Session resources are currently established in the gNB-DU. + +If the *Supported UE Type List* IE is included in the BROADCAST CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, store and use the information for configuring MBS session resources. + +#### 8.14.4.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the Broadcast Context Modification procedure. The gNB-CU sends a BROADCAST CONTEXT MODIFICATION REQUEST to the gNB-DU, and the gNB-DU responds with a BROADCAST CONTEXT MODIFICATION FAILURE.](cef981f48160da6ca248560bbf31eb7f_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: BROADCAST CONTEXT MODIFICATION REQUEST + Note right of gNB-DU: + gNB-DU-->>gNB-CU: BROADCAST CONTEXT MODIFICATION FAILURE + +``` + +Sequence diagram showing the Unsuccessful Operation of the Broadcast Context Modification procedure. The gNB-CU sends a BROADCAST CONTEXT MODIFICATION REQUEST to the gNB-DU, and the gNB-DU responds with a BROADCAST CONTEXT MODIFICATION FAILURE. + +**Figure 8.14.4.3-1: Broadcast Context Modification procedure. Unsuccessful operation** + +In case none of the requested modifications of the broadcast context can be successfully performed, the gNB-DU shall respond with the BROADCAST CONTEXT MODIFICATION FAILURE message with an appropriate cause value. + +#### 8.14.4.4 Abnormal Conditions + +Not applicable. + +### 8.14.5 Multicast Group Paging + +#### 8.14.5.1 General + +The purpose of the Multicast Group Paging procedure is used to provide the paging information to enable the gNB-DU to multicast group page UEs which have joined an MBS Session and notify them about its activation. The procedure uses non-UE associated signalling. + +## 8.14.5.2 Successful Operation + +![Sequence diagram for Multicast Group Paging](f3c73e8e478b8b2d9f6a96a970040556_img.jpg) + +A sequence diagram showing the interaction between a gNB-DU and a gNB-CU. The gNB-CU sends a message labeled 'MULTICAST GROUP PAGING' to the gNB-DU. Both entities are represented by boxes with vertical lines extending downwards to horizontal bars. + +Sequence diagram for Multicast Group Paging + +Figure 8.14.5.2-1: Multicast Group Paging + +The gNB-CU initiates the Multicast Group Paging procedure by sending the MULTICAST GROUP PAGING message to the gNB-DU. + +At the reception of the MULTICAST GROUP PAGING message, the gNB-DU shall perform paging of the MBS Session identified by the *MBS Session ID* IE. + +If the *Paging DRX* IE is included in the MULTICAST GROUP PAGING message gNB-DU shall use it according to TS 38.304 [24]. + +If the *UE Identity List for Paging* IE is included in the MULTICAST GROUP PAGING message, the gNB-DU shall, if supported, use it according to TS 38.304 [24]. If absent, the gNB-DU shall perform multicast group paging of the MBS session in all paging occasions within at least one default paging cycle, as specified in TS 38.304 [24]. + +## 8.14.5.3 Abnormal Conditions + +Void. + +## 8.14.6 Multicast Context Setup + +### 8.14.6.1 General + +The purpose of the Multicast Context Setup procedure is to establish an MBS Session context in the gNB-DU for a multicast session. + +The procedure uses MBS-associated signalling. + +### 8.14.6.2 Successful Operation + +![Sequence diagram for Multicast Context Setup procedure: Successful Operation](5e42741a4adfaf166be0b153e8089809_img.jpg) + +A sequence diagram showing the interaction between a gNB-DU and a gNB-CU. The gNB-CU sends a 'MULTICAST CONTEXT SETUP REQUEST' message to the gNB-DU. The gNB-DU then responds with a 'MULTICAST CONTEXT SETUP RESPONSE' message back to the gNB-CU. Both entities are represented by boxes with vertical lines extending downwards to horizontal bars. + +Sequence diagram for Multicast Context Setup procedure: Successful Operation + +Figure 8.14.6.2-1: Multicast Context Setup procedure: Successful Operation + +The gNB-CU initiates the procedure by sending MULTICAST CONTEXT SETUP REQUEST message to the gNB-DU. If the gNB-DU succeeds to establish the multicast MBS Session context, it replies to the gNB-CU with MULTICAST CONTEXT SETUP RESPONSE. + +If the *MBS Service Area* IE is included in the MULTICAST CONTEXT SETUP REQUEST message, the gNB-DU shall take this information into account for shared F1-U tunnel assignment. + +The gNB-DU shall report to the gNB-CU, in the MULTICAST CONTEXT SETUP RESPONSE message, the result of all the requested Multicast MRBs in the following way: + +- A list of MRBs which have been successfully established shall be included in the *Multicast MRB Setup List* IE; +- A list of MRBs which failed to be established shall be included in the *Multicast MRB Failed To Be Setup List* IE; + +If the *Multicast MRB Failed To Setup List* IE is contained in the MULTICAST CONTEXT SETUP RESPONSE message, the gNB-CU shall regard the Multicast MRB(s) failed to be setup with an appropriate cause value for each Multicast MRB failed to setup. + +If the MULTICAST CONTEXT SETUP REQUEST message contains the *MBS Multicast Configuration Request* IE in the *Multicast CU to DU RRC Information* IE set to "query" and + +- if the gNB-DU is able to provide information about the requested resources, the gNB-DU shall, if supported, include the *MBS Multicast Configuration* IE in the *MBS Multicast Configuration Response Information* IE in the *Multicast DU to CU RRC Information* IE, +- else if the gNB-DU is not able to provide information about the requested resources, the gNB-DU shall, if supported, include the *MBS Multicast Configuration not available* IE in the *MBS Multicast Configuration Response Information* IE in the *Multicast DU to CU RRC Information* IE set to "not available". + +#### Interaction with the Multicast Distribution Context Setup procedure: + +Upon reception of the MULTICAST CONTEXT SETUP REQUEST procedure, the gNB-DU shall trigger either per cell or per MBS Area Session ID or for the whole gNB-DU the Multicast Distribution Context Setup procedure to establish per cell or per MBS Area Session ID or the the whole gNB DU per accepted MRB a shared F1-U tunnel. + +#### 8.14.6.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the Multicast Context Setup procedure. The gNB-CU sends a MULTICAST CONTEXT SETUP REQUEST to the gNB-DU, and the gNB-DU responds with a MULTICAST CONTEXT SETUP FAILURE.](418ac859afe534b37c6f4e96e15c0b25_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-CU: + gNB-CU->>gNB-DU: MULTICAST CONTEXT SETUP REQUEST + Note right of gNB-DU: + gNB-DU-->>gNB-CU: MULTICAST CONTEXT SETUP FAILURE + +``` + +Sequence diagram showing the Unsuccessful Operation of the Multicast Context Setup procedure. The gNB-CU sends a MULTICAST CONTEXT SETUP REQUEST to the gNB-DU, and the gNB-DU responds with a MULTICAST CONTEXT SETUP FAILURE. + +Figure 8.14.6.3-1: Multicast Context Setup procedure: unsuccessful Operation + +If the gNB-DU is not able to establish the MBS session context it shall consider the procedure as failed and reply with the MULTICAST CONTEXT SETUP FAILURE message. + +#### 8.14.6.4 Abnormal Conditions + +Not applicable. + +## 8.14.7 Multicast Context Release + +### 8.14.7.1 General + +The purpose of the Multicast Context Release procedure is to enable the gNB-CU to order the release of an established MBS session context in the gNB-DU for a multicast session. + +The procedure uses MBS-associated signalling. + +### 8.14.7.2 Successful Operation + +![Sequence diagram of the Multicast Context Release procedure. The gNB-CU sends a MULTICAST CONTEXT RELEASE COMMAND to the gNB-DU, and the gNB-DU responds with a MULTICAST CONTEXT RELEASE COMPLETE.](e174d8245c581ea582782d582408074f_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: MULTICAST CONTEXT RELEASE COMMAND + Note right of gNB-CU: + gNB-DU-->>gNB-CU: MULTICAST CONTEXT RELEASE COMPLETE + Note right of gNB-DU: +``` + +Sequence diagram of the Multicast Context Release procedure. The gNB-CU sends a MULTICAST CONTEXT RELEASE COMMAND to the gNB-DU, and the gNB-DU responds with a MULTICAST CONTEXT RELEASE COMPLETE. + +**Figure 8.14.7.2-1: Multicast Context Release procedure. Successful operation** + +The gNB-CU initiates the procedure by sending the MULTICAST CONTEXT RELEASE COMMAND message to the gNB-DU. + +Upon reception of the MULTICAST CONTEXT RELEASE COMMAND message, the gNB-DU shall release all signalling and user data transport resources associated with the context and reply with the MULTICAST CONTEXT RELEASE COMPLETE message. + +### 8.14.7.3 Unsuccessful Operation + +Not applicable. + +### 8.14.7.4 Abnormal Conditions + +Not applicable. + +## 8.14.8 Multicast Context Release Request + +### 8.14.8.1 General + +The purpose of the Multicast Context Release Request procedure is to request the gNB-CU to trigger the Multicast Context Release procedure. + +The procedure uses MBS-associated signalling. + +### 8.14.8.2 Successful Operation + +![Sequence diagram for Multicast Context Release Request procedure. Successful operation](ffe2d3e622dd30bea4caf15951c60e42_img.jpg) + +A sequence diagram showing the interaction between a gNB-DU and a gNB-CU. The gNB-DU is on the left and the gNB-CU is on the right. A horizontal arrow labeled "MULTICAST CONTEXT RELEASE REQUEST" points from the gNB-DU to the gNB-CU. Both entities have a vertical lifeline with a small black rectangle at the bottom. + +Sequence diagram for Multicast Context Release Request procedure. Successful operation + +**Figure 8.14.8.2-1: Multicast Context Release Request procedure. Successful operation** + +The gNB-DU initiates the procedure by sending the MULTICAST CONTEXT RELEASE REQUEST message to the gNB-CU. + +#### **Interaction with the Multicast Context Release procedure:** + +Upon reception of the MULTICAST CONTEXT RELEASE REQUEST message, the gNB-CU should trigger the Multicast Context Release procedure. + +### 8.14.8.3 Unsuccessful Operation + +Not applicable. + +### 8.14.8.4 Abnormal Conditions + +Not applicable. + +## 8.14.9 Multicast Context Modification + +### 8.14.9.1 General + +The purpose of the Multicast Context Modification procedure is to modify an established MBS session context in the gNB-DU for a multicast session. + +The procedure uses MBS-associated signalling. + +### 8.14.9.2 Successful Operation + +![Sequence diagram for Multicast Context Modification procedure. Successful operation](b27f2a922eec7e6837444dbfb73293a4_img.jpg) + +A sequence diagram showing the interaction between a gNB-DU and a gNB-CU. The gNB-DU is on the left and the gNB-CU is on the right. A horizontal arrow labeled "MULTICAST CONTEXT MODIFICATION REQUEST" points from the gNB-CU to the gNB-DU. A second horizontal arrow labeled "MULTICAST CONTEXT MODIFICATION RESPONSE" points from the gNB-DU to the gNB-CU. Both entities have a vertical lifeline with a small black rectangle at the bottom. + +Sequence diagram for Multicast Context Modification procedure. Successful operation + +**Figure 8.14.9.2-1: Multicast Context Modification procedure. Successful operation** + +The MULTICAST CONTEXT MODIFICATION REQUEST message is initiated by the gNB-CU. + +Upon reception of the MULTICAST CONTEXT MODIFICATION REQUEST message, the gNB-DU shall perform the modifications, and, if successful, report the update in the MULTICAST CONTEXT MODIFICATION RESPONSE message. + +If the *Multicast MRB To Be Setup List* IE is contained in the MULTICAST CONTEXT MODIFICATION REQUEST message, the gNB-DU shall setup the corresponding resources for the requested MRB(s), and report to the gNB-CU, in the MULTICAST CONTEXT MODIFICATION RESPONSE message, the result of all the requested Multicast MRBs in the following way: + +- A list of MRBs which have been successfully established shall be included in the *Multicast MRB Setup List* IE; +- A list of MRBs which failed to be established shall be included in the *Multicast MRB Failed To Be Setup List* IE; + +If the *Multicast MRB Failed To Be Setup List* IE is contained in the MULTICAST CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall regard the setup of the indicated MRB(s) as failed and indicated the resource for the failure with an appropriate cause value for each MRB failed to be setup. + +If the *Multicast MRB To Be Modified List* IE is contained in the MULTICAST CONTEXT MODIFICATION REQUEST message, the gNB-DU shall update the corresponding context and resources for the requested MRB(s), and report to the gNB-CU, in the MULTICAST CONTEXT MODIFICATION RESPONSE message, the modification result of all the requested Multicast MRBs in the following way: + +- A list of MRBs which have been successfully modified shall be included in the *Multicast MRB Modified List* IE; +- A list of MRBs which failed to be modified shall be included in the *Multicast MRB Failed To Be Modified List* IE; + +If the *Multicast MRB Failed To Be Modified List* IE is contained in the MULTICAST CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall regard the Multicast MRB(s) failed to be modified with an appropriate cause value for each Multicast MRB failed to modify. + +If the MULTICAST CONTEXT MODIFICATION REQUEST message contains the *MBS Multicast Configuration Request* IE in the *Multicast CU to DU RRC Information* IE set to "query" and + +- if the gNB-DU is able to provide information about the requested resources, the gNB-DU shall, if supported, include the *MBS Multicast Configuration* IE in the *MBS Multicast Configuration Response Information* IE in the *Multicast DU to CU RRC Information* IE, +- else if the gNB-DU is not able to provide information about the requested resources, the gNB-DU shall, if supported, include the *MBS Multicast Configuration not available* IE in the *MBS Multicast Configuration Response Information* IE in the *Multicast DU to CU RRC Information* IE set to "not available". + +#### 8.14.9.3 Unsuccessful Operation + +![Sequence diagram showing the Unsuccessful Operation of the Multicast Context Modification procedure. The gNB-CU sends a MULTICAST CONTEXT MODIFICATION REQUEST to the gNB-DU, and the gNB-DU responds with a MULTICAST CONTEXT MODIFICATION FAILURE.](81fc56a4a4db1ceae7a1d9810cc03c64_img.jpg) + +``` + +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-CU: + gNB-CU->>gNB-DU: MULTICAST CONTEXT MODIFICATION REQUEST + Note right of gNB-DU: + gNB-DU-->>gNB-CU: MULTICAST CONTEXT MODIFICATION FAILURE + +``` + +Sequence diagram showing the Unsuccessful Operation of the Multicast Context Modification procedure. The gNB-CU sends a MULTICAST CONTEXT MODIFICATION REQUEST to the gNB-DU, and the gNB-DU responds with a MULTICAST CONTEXT MODIFICATION FAILURE. + +Figure 8.14.9.3-1: Multicast Context Modification procedure. Unsuccessful operation + +In case none of the requested modifications of the multicast context can be successfully performed, the gNB-DU shall respond with the MULTICAST CONTEXT MODIFICATION FAILURE message with an appropriate cause value. + +#### 8.14.9.4 Abnormal Conditions + +Not applicable. + +### 8.14.10 Multicast Distribution Setup + +#### 8.14.10.1 General + +The purpose of the Multicast Distribution Setup procedure is to establish F1-U bearers for the multicast MBS session. + +The procedure uses MBS-associated signalling. + +#### 8.14.10.2 Successful Operation + +![Sequence diagram of the Multicast Distribution Setup procedure showing a request from gNB-DU to gNB-CU and a response from gNB-CU to gNB-DU.](bf333cb2e46bdfbdd321c2227dd84155_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: MULTICAST DISTRIBUTION SETUP REQUEST + Note right of gNB-CU: + gNB-CU-->>gNB-DU: MULTICAST DISTRIBUTION SETUP RESPONSE +``` + +The diagram illustrates the interaction between the gNB-DU and the gNB-CU. The gNB-DU sends a 'MULTICAST DISTRIBUTION SETUP REQUEST' message to the gNB-CU. The gNB-CU then responds with a 'MULTICAST DISTRIBUTION SETUP RESPONSE' message. Both entities are represented by vertical lines with horizontal bars at the bottom. + +Sequence diagram of the Multicast Distribution Setup procedure showing a request from gNB-DU to gNB-CU and a response from gNB-CU to gNB-DU. + +**Figure 8.14.10.2-1: Multicast Distribution Setup procedure: Successful Operation** + +The gNB-DU initiates the procedure by sending MULTICAST DISTRIBUTION SETUP REQUEST message to the gNB-CU. If the gNB-CU succeeds to establish the multicast context, it replies to the gNB-DU with MULTICAST DISTRIBUTION SETUP RESPONSE. + +The MULTICAST DISTRIBUTION SETUP REQUEST message shall contain F1-U TNL information for the MRBs accepted for the MBS Session by the gNB-DU and indicate in the *MBS Multicast F1-U Context Descriptor* IE, if the shared F1-U tunnel(s) for the MRB(s) are established on a per NR CGI or per MBS Area Session ID basis or for a ptp MRB leg. + +Upon reception of the MULTICAST DISTRIBUTION SETUP REQUEST message the gNB-CU shall allocate F1-U resources and reply accordingly to the gNB-DU in the MULTICAST DISTRIBUTION SETUP RESPONSE message. + +If the *MC F1-U Context usage* IE in the *MBS Multicast F1-U Context Descriptor* IE is set to "ptp forwarding" the gNB-CU shall, if supported, use the *MRB Progress Information* IE to determine at which PDCP SN to start transmitting multicast data to the gNB-DU. + +### 8.14.10.3 Unsuccessful Operation + +![Sequence diagram for Multicast Distribution Setup procedure: unsuccessful Operation](f050e021720d7dbc135e918a25860117_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-CU: + gNB-DU->>gNB-CU: MULTICAST DISTRIBUTION SETUP REQUEST + Note right of gNB-DU: + gNB-CU-->>gNB-DU: MULTICAST DISTRIBUTION SETUP FAILURE + Note right of gNB-CU: +``` + +The diagram shows a sequence of messages between a gNB-DU and a gNB-CU. The gNB-DU sends a 'MULTICAST DISTRIBUTION SETUP REQUEST' to the gNB-CU. The gNB-CU responds with a 'MULTICAST DISTRIBUTION SETUP FAILURE' message. Both entities are represented by boxes with lifelines extending downwards, and there are solid black bars at the bottom of each lifeline. + +Sequence diagram for Multicast Distribution Setup procedure: unsuccessful Operation + +**Figure 8.14.10.3-1: Multicast Distribution Setup procedure: unsuccessful Operation** + +If the gNB-CU is not able to provide the requested resources it shall consider the procedure as failed and reply with the MULTICAST CONTEXT SETUP FAILURE message. + +### 8.14.10.4 Abnormal Conditions + +Not applicable. + +## 8.14.11 Multicast Distribution Release + +### 8.14.11.1 General + +The purpose of the Multicast Distribution Release procedure is to enable the gNB-DU to order the release of F1-U tunnels previously established using the Multicast Distribution Setup procedure. + +The procedure uses MBS-associated signalling. + +### 8.14.11.2 Successful Operation + +![Sequence diagram for Multicast Distribution Release procedure. Successful operation](e1db30df0b66cb06acb3a897e4b00999_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: MULTICAST DISTRIBUTION RELEASE COMMAND + Note right of gNB-DU: + gNB-CU-->>gNB-DU: MULTICAST DISTRIBUTION RELEASE COMPLETE + Note right of gNB-CU: +``` + +The diagram shows a sequence of messages between a gNB-DU and a gNB-CU. The gNB-DU sends a 'MULTICAST DISTRIBUTION RELEASE COMMAND' to the gNB-CU. The gNB-CU responds with a 'MULTICAST DISTRIBUTION RELEASE COMPLETE' message. Both entities are represented by boxes with lifelines extending downwards, and there are solid black bars at the bottom of each lifeline. + +Sequence diagram for Multicast Distribution Release procedure. Successful operation + +**Figure 8.14.11.2-1: Multicast Distribution Release procedure. Successful operation** + +The gNB-DU initiates the procedure by sending the MULTICAST DISTRIBUTION RELEASE COMMAND message to the gNB-CU. + +Upon reception of the MULTICAST DISTRIBUTION RELEASE COMMAND message, the gNB-CU shall release all signalling and user data transport resources associated with the context and reply with the MULTICAST DISTRIBUTION RELEASE COMPLETE message. + +### 8.14.11.3 Unsuccessful Operation + +Not applicable. + +### 8.14.11.4 Abnormal Conditions + +Not applicable. + +## 8.14.12 Multicast Context Notification + +### 8.14.12.1 General + +The purpose of the Multicast Context Notification is to inform the gNB-CU about changes in the multicast context configuration during an active multicast MBS session. + +The procedure uses MBS-associated signalling. + +### 8.14.12.2 Successful Operation + +![Sequence diagram showing the successful operation of Multicast Context Notification between gNB-CU and gNB-DU.](ddacb7cc501527d4723bdb4c21f9e023_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: MULTICAST CONTEXT NOTIFICATION INDICATION + Note right of gNB-CU: + gNB-CU->>gNB-DU: MULTICAST CONTEXT MODIFICATION CONFIRM +``` + +The diagram illustrates a sequence of messages between the gNB-CU and the gNB-DU. The gNB-DU sends a 'MULTICAST CONTEXT NOTIFICATION INDICATION' message to the gNB-CU. The gNB-CU responds with a 'MULTICAST CONTEXT MODIFICATION CONFIRM' message. The gNB-CU and gNB-DU are represented by boxes with lifelines extending downwards, and the messages are shown as horizontal arrows between these lifelines. + +Sequence diagram showing the successful operation of Multicast Context Notification between gNB-CU and gNB-DU. + +**Figure 8.14.12.2-1: Multicast Context Notification. Successful operation** + +The gNB-DU initiates the procedure by sending the MULTICAST CONTEXT NOTIFICATION INDICATION message to the gNB-CU. + +If the MULTICAST CONTEXT NOTIFICATION INDICATION message contains the *MBS Multicast Configuration Notification* IE within the *Multicast DU to CU RRC Information* IE, the gNB-CU shall replace, for the respective cell, the Multicast Configuration Information previously received with information received in the *MBS Multicast Configuration Notification* IE. + +If the gNB-CU is able to execute the requested functions, the gNB-CU shall respond with the MULTICAST CONTEXT NOTIFICATION CONFIRM message to the gNB-DU. + +### 8.14.12.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Operation of Multicast Context Notification](18b87e4ce7ef441f5620b8d6539a2939_img.jpg) + +A sequence diagram showing the interaction between gNB-CU and gNB-DU for an unsuccessful operation. The gNB-DU sends a 'MULTICAST CONTEXT NOTIFICATION INDICATION' message to the gNB-CU. The gNB-CU responds with a 'MULTICAST CONTEXT MODIFICATION REFUSE' message to the gNB-DU. Both entities are represented by vertical lifelines with a solid black bar at the bottom. + +Sequence diagram for Unsuccessful Operation of Multicast Context Notification + +**Figure 8.14.12.3-1: Multicast Context Notification. Unsuccessful operation** + +If the gNB-CU is not able to execute the requested functions, the gNB-CU shall respond with the MULTICAST CONTEXT NOTIFICATION REFUSE message to the gNB-DU. + +### 8.14.12.4 Abnormal Conditions + +Not applicable. + +## 8.14.13 Multicast Common Configuration + +### 8.14.13.1 General + +The purpose of the Multicast Common Configuration procedure is to allow the gNB-CU to control the configuration of items common to all multicast contexts in the gNB-DU. + +The procedure uses non UE-associated signalling. + +### 8.14.13.2 Successful Operation + +![Sequence diagram for Successful Operation of Multicast Common Configuration](7c239d0d8d8e5ee7edb275ae16c2269e_img.jpg) + +A sequence diagram showing the interaction between gNB-DU and gNB-CU for a successful operation. The gNB-CU sends a 'MULTICAST COMMON CONFIGURATION REQUEST' message to the gNB-DU. The gNB-DU responds with a 'MULTICAST COMMON CONFIGURATION RESPONSE' message to the gNB-CU. Both entities are represented by vertical lifelines with a solid black bar at the bottom. + +Sequence diagram for Successful Operation of Multicast Common Configuration + +**Figure 8.14.13.2-1: Multicast Common Configuration. Successful operation** + +The gNB-CU initiates the procedure by sending the MULTICAST COMMON CONFIGURATION REQUEST message to the gNB-DU. + +If the *Multicast CU to DU Common RRC Information* IE is included in the MULTICAST COMMON CONFIGURATION REQUEST message and contains the *Multicast Common CU2DU Cell List* IE, the gNB-DU shall, if supported, use it to configure MBS session resources accordingly. + +### 8.14.13.3 Unsuccessful Operation + +![Sequence diagram for Multicast Context Notification. Unsuccessful operation](991dd3ca8ff5bdb023220b1d44775e1d_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: MULTICAST COMMON CONFIGURATION REQUEST + Note right of gNB-DU: + gNB-DU-->>gNB-CU: MULTICAST COMMON CONFIGURATION REFUSE +``` + +The diagram shows a sequence of messages between a gNB-CU and a gNB-DU. The gNB-CU sends a 'MULTICAST COMMON CONFIGURATION REQUEST' message to the gNB-DU. The gNB-DU responds with a 'MULTICAST COMMON CONFIGURATION REFUSE' message. Both entities are represented by vertical lines with horizontal bars at the bottom. + +Sequence diagram for Multicast Context Notification. Unsuccessful operation + +**Figure 8.14.13.3-1: Multicast Context Notification. Unsuccessful operation** + +If the gNB-DU is not able to execute the requested functions, the gNB-DU shall respond with the MULTICAST COMMON CONFIGURATION REFUSE message to the gNB-CU. + +### 8.14.13.4 Abnormal Conditions + +void. + +## 8.14.14 Broadcast Transport Resource Request + +### 8.14.14.1 General + +The purpose of the Broadcast Transport Resource Request procedure is to request the gNB-CU to trigger the establishment of F1-U resources for the broadcast session. + +The procedure uses MBS-associated signalling. + +### 8.14.14.2 Successful Operation + +![Sequence diagram for Broadcast Context Release Request procedure. Successful operation](300130063df853c2bf2589510f69dbba_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-DU->>gNB-CU: BROADCAST TRANSPORT RESOURCE REQUEST + Note right of gNB-CU: + gNB-CU-->>gNB-DU: +``` + +The diagram shows a sequence of messages between a gNB-DU and a gNB-CU. The gNB-DU sends a 'BROADCAST TRANSPORT RESOURCE REQUEST' message to the gNB-CU. The gNB-CU responds with a message that is partially cut off in the image. Both entities are represented by vertical lines with horizontal bars at the bottom. + +Sequence diagram for Broadcast Context Release Request procedure. Successful operation + +**Figure 8.14.14.2-1: Broadcast Context Release Request procedure. Successful operation** + +The gNB-DU initiates the procedure by sending the BROADCAST TRANSPORT RESOURCE REQUEST message to the gNB-CU. + +#### **Interaction with the Broadcast Context Modification procedure:** + +Upon reception of the BROADCAST TRANSPORT RESOURCE REQUEST message, the gNB-CU should trigger the Broadcast Context Modification procedure to establish the F1-U resources for the broadcast session. + +### 8.14.14.3 Unsuccessful Operation + +Not applicable. + +### 8.14.14.4 Abnormal Conditions + +Not applicable. + +## 8.15 PDC Measurement Reporting procedures + +### 8.15.1 PDC Measurement Initiation + +#### 8.15.1.1 General + +The purpose of the PDC Measurement Initiation procedure is to enable the gNB-CU to request the gNB-DU to report measurements used for propagation delay compensation at the gNB-CU or UE. The procedure uses UE-associated signalling. + +#### 8.15.1.2 Successful Operation + +![Sequence diagram of PDC Measurement Initiation procedure, successful operation](1b39bec1cdf850bbcbbd693f5c36dbf4_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: PDC MEASUREMENT INITIATION REQUEST + gNB-DU-->>gNB-CU: PDC MEASUREMENT INITIATION RESPONSE + Note right of gNB-CU: +``` + +The diagram illustrates the successful operation of the PDC Measurement Initiation procedure. It shows two entities, gNB-DU and gNB-CU, represented by boxes with vertical lines extending downwards. A horizontal arrow labeled "PDC MEASUREMENT INITIATION REQUEST" points from the gNB-CU to the gNB-DU. A return horizontal arrow labeled "PDC MEASUREMENT INITIATION RESPONSE" points from the gNB-DU to the gNB-CU. Both entities have a thick horizontal bar at the bottom of their vertical lines, representing the timeline of the procedure. + +Sequence diagram of PDC Measurement Initiation procedure, successful operation + +**Figure 8.15.1.2-1: PDC Measurement Initiation procedure, successful operation** + +The gNB-CU initiates the procedure by sending a PDC MEASUREMENT INITIATION REQUEST message. If the gNB-DU is able to initiate the requested PDC measurements, it shall reply with the PDC MEASUREMENT INITIATION RESPONSE message. + +If the *PDC Report Type* IE is set to "OnDemand", the gNB-DU shall return the result of the measurement in the PDC MEASUREMENT INITIATION RESPONSE message including the *PDC Measurement Result* IE, and the gNB-CU shall consider that the PDC measurements for the UE have been terminated by the gNB-DU. + +#### **Interaction with the PDC Measurement Report procedure:** + +If the *PDC Report Type* IE is set to "Periodic", the gNB-DU shall initiate the requested measurements and shall reply with the PDC MEASUREMENT INITIATION RESPONSE message without including the *PDC Measurement Result* IE in this message. The gNB-DU shall then periodically initiate the PDC Measurement Report procedure for the measurements, with the requested reporting periodicity. + +### 8.15.1.3 Unsuccessful Operation + +![Sequence diagram for PDC Measurement Initiation procedure, unsuccessful operation](437a88375397eec8390174b5426e99b0_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-DU: + gNB-CU->>gNB-DU: PDC MEASUREMENT INITIATION REQUEST + Note right of gNB-DU: + gNB-DU-->>gNB-CU: PDC MEASUREMENT INITIATION FAILURE +``` + +The diagram shows a sequence of messages between a gNB-CU and a gNB-DU. The gNB-CU sends a 'PDC MEASUREMENT INITIATION REQUEST' to the gNB-DU. The gNB-DU responds with a 'PDC MEASUREMENT INITIATION FAILURE' message. Both entities are represented by boxes with lifelines extending downwards, ending in thick horizontal bars. + +Sequence diagram for PDC Measurement Initiation procedure, unsuccessful operation + +**Figure 8.15.1.3-1: PDC Measurement Initiation procedure, unsuccessful operation** + +If the gNB-DU is not able to initiate at least one of the requested PDC measurements, the gNB-DU shall respond with a PDC MEASUREMENT INITIATION FAILURE message. + +## 8.15.2 PDC Measurement Report + +### 8.15.2.1 General + +The purpose of the PDC Measurement Report procedure is for the gNB-DU to provide the PDC measurements for the UE to the gNB-CU. The procedure uses UE-associated signalling. + +### 8.15.2.2 Successful Operation + +![Sequence diagram for PDC Measurement Report procedure, successful operation](b5b0749219d60ecf8f3402eb2cc86d1e_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: PDC MEASUREMENT REPORT +``` + +The diagram shows a sequence of messages between a gNB-DU and a gNB-CU. The gNB-DU sends a 'PDC MEASUREMENT REPORT' to the gNB-CU. Both entities are represented by boxes with lifelines extending downwards, ending in thick horizontal bars. + +Sequence diagram for PDC Measurement Report procedure, successful operation + +**Figure 8.15.2.2-1: PDC Measurement Report procedure, successful operation** + +The gNB-DU initiates the procedure by sending a PDC MEASUREMENT REPORT message. The PDC MEASUREMENT REPORT message contains the PDC measurement results according to the measurement configuration in the respective PDC MEASUREMENT INITIATION REQUEST message. + +### 8.15.2.3 Unsuccessful Operation + +Not applicable. + +## 8.15.3 PDC Measurement Termination + +### 8.15.3.1 General + +The purpose of the PDC Measurement Termination procedure is to enable the gNB-CU to terminate an on-going periodical PDC measurement. The procedure uses UE-associated signalling. + +### 8.15.3.2 Successful Operation + +![Sequence diagram for PDC Measurement Termination procedure: successful operation](7abc02f39b6084e0f27f07a8e8f9224f_img.jpg) + +A sequence diagram showing the interaction between a gNB-DU and a gNB-CU. The gNB-CU sends a 'PDC MEASUREMENT TERMINATION COMMAND' message to the gNB-DU. Both entities are represented by rectangular boxes with a horizontal line at the bottom. + +Sequence diagram for PDC Measurement Termination procedure: successful operation + +**Figure 8.15.3.2-1: PDC Measurement Termination procedure: successful operation** + +The gNB-CU initiates the procedure by sending a PDC MEASUREMENT TERMINATION COMMAND message. Upon receiving this message, the gNB-DU shall terminate the ongoing PDC measurement and may release any resources previously allocated for the same measurement. + +### 8.15.3.3 Unsuccessful Operation + +Not applicable. + +### 8.15.3.4 Abnormal Conditions + +If the gNB-DU cannot identify the previously requested measurement to be terminated, it shall ignore the PDC MEASUREMENT TERMINATION COMMAND message. + +## 8.15.4 PDC Measurement Failure Indication + +### 8.15.4.1 General + +The purpose of the PDC Measurement Failure Indication procedure is for the gNB-DU to notify the gNB-CU that the PDC measurements previously requested with the PDC Measurement Initiation procedure can no longer be reported. The procedure uses UE-associated signalling. + +### 8.15.4.2 Successful Operation + +![Sequence diagram for PDC Measurement Failure Indication procedure: successful operation](d50bad97997c6e68494503b621da25b6_img.jpg) + +A sequence diagram showing the interaction between a gNB-DU and a gNB-CU. The gNB-DU sends a 'PDC MEASUREMENT FAILURE INDICATION' message to the gNB-CU. Both entities are represented by rectangular boxes with a horizontal line at the bottom. + +Sequence diagram for PDC Measurement Failure Indication procedure: successful operation + +**Figure 8.15.4.2-1: PDC Measurement Failure Indication procedure: successful operation** + +The gNB-DU initiates the procedure by sending a PDC MEASUREMENT FAILURE INDICATION message. Upon reception of the PDC MEASUREMENT FAILURE INDICATION message, the gNB-CU shall consider that the indicated PDC measurements have been terminated by the gNB-DU. + +### 8.15.4.3 Unsuccessful Operation + +Not applicable. + +#### 8.15.4.4 Abnormal Conditions + +Void. + +### 8.16 QMC Procedures + +#### 8.16.1 QoE Information Transfer + +##### 8.16.1.1 General + +The purpose of the QoE Information Transfer procedure is to transfer RAN visible QoE information from the gNB-CU to the gNB-DU. The procedure uses UE-associated signalling. + +##### 8.16.1.2 Successful operation + +![Sequence diagram showing the QoE Information Transfer procedure. A gNB-CU sends a QOE INFORMATION TRANSFER message to a gNB-DU.](ca22c6236ae7c9a8e76d79c469c452a6_img.jpg) + +``` +sequenceDiagram + participant gNB-CU + participant gNB-DU + Note left of gNB-CU: + gNB-CU->>gNB-DU: QOE INFORMATION TRANSFER + Note right of gNB-DU: +``` + +The diagram illustrates the successful operation of the QoE Information Transfer procedure. It features two vertical lifelines: gNB-DU on the left and gNB-CU on the right. A horizontal arrow labeled 'QOE INFORMATION TRANSFER' originates from the gNB-CU lifeline and points to the gNB-DU lifeline. Both lifelines terminate at a thick horizontal bar at the bottom, representing the end of the procedure. + +Sequence diagram showing the QoE Information Transfer procedure. A gNB-CU sends a QOE INFORMATION TRANSFER message to a gNB-DU. + +**Figure 8.16.1.2-1: QoE Information Transfer procedure** + +The gNB-CU initiates the procedure by sending the QOE INFORMATION TRANSFER message to the gNB-DU. + +If the *QoE Information List* IE is included in QOE INFORMATION TRANSFER message, the gNB-DU may take it into account according to TS 38.300 [6]. + +##### 8.16.1.3 Abnormal Conditions + +Not applicable. + +#### 8.16.2 QoE Information Transfer Control + +##### 8.16.2.1 General + +The purpose of the QoE Information Transfer Control procedure is to control the RAN visible QoE information transfer from the gNB-CU to the gNB-DU. The procedure uses non-UE associated signalling. + +## 8.16.2.2 Successful operation + +![Sequence diagram for QoE Information Transfer Control procedure. A gNB-DU sends a QOE INFORMATION TRANSFER CONTROL message to a gNB-CU.](0d9149a10167a487a93c349f5d848b7d_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: QOE INFORMATION TRANSFER CONTROL + Note right of gNB-CU: +``` + +Sequence diagram for QoE Information Transfer Control procedure. A gNB-DU sends a QOE INFORMATION TRANSFER CONTROL message to a gNB-CU. + +**Figure 8.16.2.2-1: QoE Information Transfer Control procedure.** + +The gNB-DU initiates the procedure by sending the QOE INFORMATION TRANSFER CONTROL message to the gNB-CU. + +If the *Deactivation Indication List* IE is present in the message, the gNB-CU shall, if supported, deactivate the QoE information transfer from gNB-CU to gNB-DU for the UEs indicated therein. + +## 8.16.2.3 Abnormal Conditions + +Not applicable. + +# 8.17 Timing Synchronisation Status Reporting Procedures + +## 8.17.1 Timing Synchronisation Status + +### 8.17.1.1 General + +The purpose of the Timing Synchronisation Status procedure is to enable the gNB-CU to request the gNB-DU to start or stop reporting of RAN timing synchronisation status information. + +The procedure uses non-UE associated signalling. + +### 8.17.1.2 Successful Operation + +![Sequence diagram for Timing synchronisation status procedure: successful operation. A gNB-CU sends a TIMING SYNCHRONISATION STATUS REQUEST message to a gNB-DU, and the gNB-DU responds with a TIMING SYNCHRONISATION STATUS RESPONSE.](b2fc8c097c64181ee31839d2703d396d_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-CU->>gNB-DU: TIMING SYNCHRONISATION STATUS REQUEST + gNB-DU-->>gNB-CU: TIMING SYNCHRONISATION STATUS RESPONSE + Note right of gNB-CU: +``` + +Sequence diagram for Timing synchronisation status procedure: successful operation. A gNB-CU sends a TIMING SYNCHRONISATION STATUS REQUEST message to a gNB-DU, and the gNB-DU responds with a TIMING SYNCHRONISATION STATUS RESPONSE. + +**Figure 8.17.1.2-1: Timing synchronisation status procedure: successful operation** + +The gNB-CU initiates the procedure by sending a TIMING SYNCHRONISATION STATUS REQUEST message to the gNB-DU. + +If the *RAN TSS Request Type* IE included in the TIMING SYNCHRONISATION STATUS REQUEST message is set to “start”, the gNB-DU shall start the reporting of RAN timing synchronization status information and reply with the + +TIMING SYNCHRONISATION STATUS RESPONSE message. If the *RAN TSS Request Type* IE is set to “stop”, the gNB-DU shall stop the reporting and reply with the TIMING SYNCHRONISATION STATUS RESPONSE message. + +#### 8.17.1.3 Unsuccessful Operation + +![Sequence diagram for Unsuccessful Operation of Timing Synchronisation Status procedure.](10ffa7dc47da9e864cada0fb7fe6f4cb_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-CU->>gNB-DU: TIMING SYNCHRONISATION STATUS REQUEST + Note right of gNB-CU: + gNB-DU-->>gNB-CU: TIMING SYNCHRONISATION STATUS FAILURE + Note left of gNB-DU: +``` + +The diagram shows a sequence of messages between a gNB-DU and a gNB-CU. The gNB-CU sends a 'TIMING SYNCHRONISATION STATUS REQUEST' to the gNB-DU. The gNB-DU responds with a 'TIMING SYNCHRONISATION STATUS FAILURE' message. Both entities have a vertical lifeline with a thick horizontal bar at the bottom. + +Sequence diagram for Unsuccessful Operation of Timing Synchronisation Status procedure. + +Figure 8.17.1.3-1: Timing synchronisation status procedure: unsuccessful operation + +If the gNB-DU is not able to report timing synchronisation status, it shall consider the procedure as failed and reply with the TIMING SYNCHRONISATION STATUS FAILURE message. + +#### 8.17.1.4 Abnormal Conditions + +Void. + +### 8.17.2 Timing Synchronisation Status Report + +#### 8.17.2.1 General + +The purpose of the Timing Synchronisation Status Report procedure is to enable the gNB-DU to provide RAN timing synchronisation status information to the gNB-CU. + +The procedure uses non-UE associated signalling. + +#### 8.17.2.2 Successful Operation + +![Sequence diagram for Successful Operation of Timing Synchronisation Status Report.](c46d463fc2af2c2a6a6a3f9d0cea1c5e_img.jpg) + +``` +sequenceDiagram + participant gNB-DU + participant gNB-CU + Note left of gNB-DU: + gNB-DU->>gNB-CU: TIMING SYNCHRONISATION STATUS REPORT + Note right of gNB-CU: + Note left of gNB-DU: +``` + +The diagram shows a sequence of messages between a gNB-DU and a gNB-CU. The gNB-DU sends a 'TIMING SYNCHRONISATION STATUS REPORT' to the gNB-CU. Both entities have a vertical lifeline with a thick horizontal bar at the bottom. + +Sequence diagram for Successful Operation of Timing Synchronisation Status Report. + +Figure 8.17.2.2-1: Timing synchronisation status report + +The gNB-DU initiates the procedure by sending a TIMING SYNCHRONISATION STATUS REPORT message to the gNB-CU. + +#### 8.17.2.3 Abnormal Conditions + +Void. + +## 9 Elements for F1AP Communication + +### 9.1 General + +Subclauses 9.2 and 9.3 present the F1AP 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 [14]. + +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 [3]. + +### 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 and the gNB-DU and is used to request that the F1 interface, or parts of the F1 interface, to be reset. + +Direction: gNB-CU → gNB-DU and gNB-DU → gNB-CU + +| 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 | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| CHOICE Reset Type | M | | | | YES | reject | +| >F1 interface | | | | | | | +| >>Reset All | M | | ENUMERATED
(Reset all,...) | | - | | +| >Part of F1 interface | | | | | | | +| >>UE-associated logical F1-connection list | | 1 | | | - | | +| >>>UE-associated logical F1-connection Item | | 1 ..
| | | EACH | reject | + +| | | | | | | | +|-----------------------|---|--|---------|--|---|--| +| >>>>gNB-CU UE F1AP ID | O | | 9.3.1.4 | | - | | +| >>>>gNB-DU UE F1AP ID | O | | 9.3.1.5 | | - | | + +| Range bound | Explanation | +|---------------------------------------|------------------------------------------------------------------------------------------------------| +| maxnoofIndividualF1ConnectionsToReset | Maximum no. of UE-associated logical F1-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 and the gNB-DU as a response to a RESET message. + +Direction: gNB-DU → gNB-CU and gNB-CU → gNB-DU. + +| 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 | +| UE-associated logical F1-connection list | | 0..1 | | | YES | ignore | +| >UE-associated logical F1-connection Item | | 1 .. | | | EACH | ignore | +| >>gNB-CU UE F1AP ID | O | | 9.3.1.4 | | - | | +| >>gNB-DU UE F1AP ID | O | | 9.3.1.5 | | - | | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +| Range bound | Explanation | +|---------------------------------------|------------------------------------------------------------------------------------------------------| +| maxnoofIndividualF1ConnectionsToReset | Maximum no. of UE-associated logical F1-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 and the gNB-DU and is used to indicate that some error has been detected in the node. + +Direction: gNB-CU → gNB-DU and gNB-DU → gNB-CU + +| 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.23 | This IE is ignored if received in UE associated signalling message. | YES | reject | +| gNB-CU UE F1AP ID | O | | 9.3.1.4 | | YES | ignore | +| gNB-DU UE F1AP 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 | + +### 9.2.1.4 F1 SETUP REQUEST + +This message is sent by the gNB-DU to transfer information associated to an F1-C interface instance. + +NOTE: If a TNL association is shared among several F1-C interface instances, several F1 Setup procedures are issued via the same TNL association after that TNL association has become operational. + +Direction: gNB-DU → gNB-CU + +| 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 | +| gNB-DU ID | M | | 9.3.1.9 | | YES | reject | +| gNB-DU Name | O | | PrintableString(
SIZE(1..150,...)) | | YES | ignore | +| gNB-DU Served Cells List | | 0.. 1 | | List of cells configured in the gNB-DU | YES | reject | +| >gNB-DU Served Cells Item | | 1..
ngNB-DU> | | | EACH | reject | +| >>Served Cell Information | M | | 9.3.1.10 | Information about the cells configured in the gNB-DU | - | | +| >>gNB-DU System Information | O | | 9.3.1.18 | RRc container with system information owned by gNB-DU | - | | +| gNB-DU RRC version | M | | RRc version
9.3.1.70 | | YES | reject | +| Transport Layer Address Info | O | | 9.3.2.5 | | YES | ignore | +| BAP Address | O | | 9.3.1.111 | Indicates a BAP address assigned to the IAB-node. | YES | ignore | +| Extended gNB-DU Name | O | | 9.3.1.205 | | YES | ignore | +| RRc Terminating IAB-Donor gNB-ID | O | | Global gNB ID
9.3.1.305 | The Global gNB ID of a mobile IAB-node's RRc-terminating IAB donor. This IE is only present if the mobile IAB-node's RRc terminating IAB-donor-CU is different from the gNB-CU receiving this message. | YES | ignore | +| Mobile IAB-MT User Location Information | O | | 9.3.1.307 | | YES | ignore | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------| +| maxCellingNBUDU | Maximum no. cells that can be served by a gNB-DU. Value is 512. | + +### 9.2.1.5 F1 SETUP RESPONSE + +This message is sent by the gNB-CU to transfer information associated to an F1-C interface instance. + +Direction: gNB-CU → gNB-DU + +| 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 | +| gNB-CU Name | O | | PrintableString(
SIZE(1..150,...)) | Human readable name of the gNB-CU. | YES | ignore | +| Cells to be Activated List | | 0.. 1 | | | YES | reject | +| > Cells to be Activated List Item | | 1..
| | List of cells to be activated | EACH | reject | +| >>NR CGI | M | | 9.3.1.12 | | - | | +| >>NR PCI | O | | INTEGER
(0..1007) | Physical Cell ID | - | | +| >>gNB-CU System Information | O | | 9.3.1.42 | RRP container with system information owned by gNB-CU | YES | reject | +| >>Available PLMN List | O | | 9.3.1.65 | | YES | ignore | +| >>Extended Available PLMN List | O | | 9.3.1.76 | This is included if Available PLMN List IE is included and if more than 6 Available PLMNs is to be signalled. | YES | ignore | +| >>IAB Info IAB-donor-CU | O | | 9.3.1.105 | IAB-related configuration sent by the IAB-donor-CU. | YES | ignore | +| >>Available SNPN ID List | O | | 9.3.1.163 | Indicates the available SNPN ID list.
If this IE is included, the content of the Available PLMN List IE and Extended Available PLMN List IE if present in the Cells to be Activated List Item IE is ignored. | YES | ignore | +| >>MBS Broadcast Neighbour Cell List | O | | 9.3.1.226 | | YES | ignore | +| gNB-CU RRC version | M | | RRP version
9.3.1.70 | | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------|----------|--------------------------|-----------------------|-------------------------------------------------------|-------------|----------------------| +| Transport Layer Address Info | O | | 9.3.2.5 | | YES | ignore | +| Uplink BH Non-UP Traffic Mapping | O | | 9.3.1.103 | | YES | reject | +| BAP Address | O | | 9.3.1.111 | Indicates a BAP address assigned to the IAB-donor-DU. | YES | ignore | +| Extended gNB-CU Name | O | | 9.3.1.206 | | YES | ignore | +| NCGI to be Updated List | | 0..1 | | | YES | ignore | +| >NCGI to be Updated List Item | | 1..
| | List of NCGIs to be updated. | EACH | ignore | +| >>Old NCGI | M | | NR CGI
9.3.1.12 | Old NCGI of a cell served by the mobile IAB-DU | - | | +| >>New NCGI | M | | NR CGI
9.3.1.12 | New NCGI of a cell served by the mobile IAB-DU | - | | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------| +| maxCellingNBUDU | Maximum no. cells that can be served by a gNB-DU. Value is 512. | + +### 9.2.1.6 F1 SETUP FAILURE + +This message is sent by the gNB-CU to indicate F1 Setup failure. + +Direction: gNB-CU → gNB-DU + +| 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 | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Time to wait | O | | 9.3.1.13 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.1.7 GNB-DU CONFIGURATION UPDATE + +This message is sent by the gNB-DU to transfer updated information associated to an F1-C interface instance. + +NOTE: If F1-C signalling transport is shared among several F1-C interface instances, this message may transfer updated information associated to several F1-C interface instances. + +Direction: gNB-DU → gNB-CU + +| 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 | +| Served Cells To Add | | 0..1 | | Complete list of | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------|----------|------------------------------|-----------------------|-----------------------------------------------------------------|-------------|----------------------| +| List | | | | added cells served by the gNB-DU | | | +| > Served Cells To Add Item | | 1 ..
ngNBDU> | | | EACH | reject | +| >>Served Cell Information | M | | 9.3.1.10 | Information about the cells configured in the gNB-DU | - | | +| >>gNB-DU System Information | O | | 9.3.1.18 | RRP container with system information owned by gNB-DU | - | | +| Served Cells To Modify List | | 0..1 | | Complete list of modified cells served by the gNB-DU | YES | reject | +| > Served Cells To Modify Item | | 1 ..
ngNBDU> | | | EACH | reject | +| >>Old NR CGI | M | | NR CGI
9.3.1.12 | | - | | +| >>Served Cell Information | M | | 9.3.1.10 | Information about the cells configured in the gNB-DU | - | | +| >>gNB-DU System Information | O | | 9.3.1.18 | RRP container with system information owned by gNB-DU | - | | +| Served Cells To Delete List | | 0..1 | | Complete list of deleted cells served by the gNB-DU | YES | reject | +| > Served Cells To Delete Item | | 1..
ngNBDU> | | | EACH | reject | +| >>Old NR CGI | M | | NR CGI
9.3.1.12 | | - | | +| Cells Status List | | 0..1 | | Complete list of active cells | YES | reject | +| > Cells Status Item | | 0 ..
ngNBDU> | | | EACH | reject | +| >>NR CGI | M | | 9.3.1.12 | | - | | +| >>Service Status | M | | 9.3.1.68 | | - | | +| Dedicated SI Delivery Needed UE List | | 0..1 | | List of UEs unable to receive system information from broadcast | YES | ignore | +| > Dedicated SI Delivery Needed UE Item | | 1 ..
UEIDs> | | | EACH | ignore | +| >>gNB-CU UE F1AP ID | M | | 9.3.1.4 | | - | | +| >>NR CGI | M | | 9.3.1.12 | | - | | +| gNB-DU ID | O | | 9.3.1.9 | | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------------|----------|----------------------------|------------------------------------|-------------------------------------------------------------------------------------|-------------|----------------------| +| gNB-DU TNL Association To Remove List | | 0..1 | | | YES | reject | +| >gNB-DU TNL Association To Remove Item IEs | | 1.. | | | EACH | reject | +| >>TNL Association Transport Layer Address | M | | CP Transport Layer Address 9.3.2.4 | Transport Layer Address of the gNB-DU. | - | - | +| >>TNL Association Transport Layer Address gNB-CU | O | | CP Transport Layer Address 9.3.2.4 | Transport Layer Address of the gNB-CU | - | - | +| Transport Layer Address Info | O | | 9.3.2.5 | | YES | ignore | +| Coverage Modification Notification | O | | 9.3.1.213 | | YES | ignore | +| gNB-DU Name | O | | PrintableString( SIZE(1..150,...)) | Human readable name of the gNB-DU. | YES | ignore | +| Extended gNB-DU Name | O | | 9.3.1.205 | | YES | ignore | +| RRC Terminating IAB-Donor Related Info | O | | 9.3.1.306 | Indicates the information related to a mobile IAB-node's RRC-terminating IAB-donor. | YES | ignore | +| Mobile IAB-MT User Location Information | O | | 9.3.1.307 | | YES | ignore | + +| Range bound | Explanation | +|------------------------|-------------------------------------------------------------------------------------| +| maxCellingNBDU | Maximum no. cells that can be served by a gNB-DU. Value is 512. | +| maxnoofUEIDs | Maximum no. of UEs that can be served by a gNB-DU. Value is 65536. | +| maxnoofTNLAssociations | Maximum numbers of TNL Associations between the gNB-CU and the gNB-DU. Value is 32. | + +## 9.2.1.8 GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE + +This message is sent by a gNB-CU to a gNB-DU to acknowledge update of information associated to an F1-C interface instance. + +NOTE: If F1-C signalling transport is shared among several F1-C interface instances, this message may transfer updated information associated to several F1-C interface instances. + +Direction: gNB-CU → gNB-DU + +| 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 | +| Cells to be Activated List | | 0.. 1 | | List of cells to be activated | YES | reject | +| >Cells to be Activated List Item | | 1.. | | | EACH | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|------------------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | ngNBDU> | | | | | +| >> NR CGI | M | | 9.3.1.12 | | - | | +| >> NR PCI | O | | INTEGER (0..1007) | Physical Cell ID | - | | +| >> gNB-CU System Information | O | | 9.3.1.42 | RRC container with system information owned by gNB-CU | YES | reject | +| >>Available PLMN List | O | | 9.3.1.65 | | YES | ignore | +| >>Extended Available PLMN List | O | | 9.3.1.76 | This is included if Available PLMN List IE is included and if more than 6 Available PLMNs is to be signalled. | YES | ignore | +| >>IAB Info IAB-donor-CU | O | | 9.3.1.105 | IAB-related configuration sent by the IAB-donor-CU. | YES | ignore | +| >>Available SNPN ID List | O | | 9.3.1.163 | Indicates the available SNPN ID list.
If this IE is included, the content of the Available PLMN List IE and Extended Available PLMN List IE if present in the Cells to be Activated List Item IE is ignored. | YES | ignore | +| >>MBS Broadcast Neighbour Cell List | O | | 9.3.1.226 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| Cells to be Deactivated List | | 0.. 1 | | List of cells to be deactivated | YES | reject | +| >Cells to be Deactivated List Item | | 1.. <maxCelli ngNBDU> | | | EACH | reject | +| >>NR CGI | M | | 9.3.1.12 | | - | - | +| Transport Layer Address Info | O | | 9.3.2.5 | | YES | ignore | +| Uplink BH Non-UP Traffic Mapping | O | | 9.3.1.103 | | YES | reject | +| BAP Address | O | | 9.3.1.111 | Indicates a BAP address assigned to the IAB-donor-DU. | YES | ignore | +| Cells for SON List | O | | 9.3.1.214 | | YES | ignore | + +| Range bound | Explanation | +|----------------|-----------------------------------------------------------------| +| maxCellingNBDU | Maximum no. cells that can be served by a gNB-DU. Value is 512. | + +### 9.2.1.9 GNB-DU CONFIGURATION UPDATE FAILURE + +This message is sent by the gNB-CU to indicate gNB-DU Configuration Update failure. + +Direction: gNB-CU → gNB-DU + +| 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 | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Time to wait | O | | 9.3.1.13 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.1.10 GNB-CU CONFIGURATION UPDATE + +This message is sent by the gNB-CU to transfer updated information associated to an F1-C interface instance. + +NOTE: If F1-C signalling transport is shared among several F1-C interface instances, this message may transfer updated information associated to several F1-C interface instances. + +Direction: gNB-CU → gNB-DU + +| 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 | +| Cells to be Activated List | | 0..1 | | List of cells to be activated or modified | YES | reject | +| > Cells to be Activated List Item | | 1..
ngNBIDU> | | | EACH | reject | +| >>NR CGI | M | | 9.3.1.12 | | - | | +| >>NR PCI | O | | INTEGER
(0..1007) | Physical Cell ID | - | | +| >>gNB-CU System Information | O | | 9.3.1.42 | RRC container with system information owned by gNB-CU | YES | reject | +| >>Available PLMN List | O | | 9.3.1.65 | | YES | ignore | +| >>Extended Available PLMN List | O | | 9.3.1.76 | This is included if Available PLMN List IE is included and if more than 6 Available PLMNs is to be signalled. | YES | ignore | +| >>IAB Info IAB-donor-CU | O | | 9.3.1.105 | IAB-related configuration sent by the IAB-donor-CU. | YES | ignore | +| >>Available SNPN ID List | O | | 9.3.1.163 | Indicates the available SNPN ID list.
If this IE is included, the content of the | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------------|----------|-----------------------------|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | Available PLMN List IE and Extended Available PLMN List IE if present in the Cells to be Activated List Item IE is ignored. | | | +| >>MBS Broadcast Neighbour Cell List | O | | 9.3.1.226 | | YES | ignore | +| >>SSBs within the cell to be Activated List | | 0..1 | | List of SSB beams within the cell requested to be activated. | YES | reject | +| >>>SSBs within the cell to be Activated List Item | | 0.. | | | - | | +| >>>>SSB Index | M | | INTEGER (0..63) | Identifier of SSB beam requested to be activated. | - | | +| Cells to be Deactivated List | | 0..1 | | List of cells to be deactivated | YES | reject | +| >Cells to be Deactivated List Item | | 1.. | | | EACH | reject | +| >>NR CGI | M | | 9.3.1.12 | | - | | +| gNB-CU TNL Association To Add List | | 0..1 | | | YES | ignore | +| >gNB-CU TNL Association To Add Item IEs | | 1.. | | | EACH | ignore | +| >>TNL Association Transport Layer Information | M | | CP Transport Layer Address 9.3.2.4 | Transport Layer Address of the gNB-CU. | - | | +| >>TNL Association Usage | M | | ENUMERATED (ue, non-ue, both, ...) | Indicates whether the TNL association is only used for UE-associated signalling, or non-UE-associated signalling, or both. For usage of this IE, refer to TS 38.472 [22]. | - | | +| gNB-CU TNL Association To Remove List | | 0..1 | | | YES | ignore | +| >gNB-CU TNL Association To Remove Item IEs | | 1.. | | | EACH | ignore | +| >>TNL Association Transport Layer Address | M | | CP Transport Layer Address 9.3.2.4 | Transport Layer Address of the gNB-CU. | - | | +| >>TNL Association Transport Layer | O | | CP Transport Layer Address | Transport Layer Address of the | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------------|----------|------------------------------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Address gNB-DU | | | 9.3.2.4 | gNB-DU. | | | +| gNB-CU TNL Association To Update List | | 0..1 | | | YES | ignore | +| >gNB-CU TNL Association To Update Item IEs | | 1.. | | | EACH | ignore | +| >>TNL Association Transport Layer Address | M | | CP Transport Layer Address 9.3.2.4 | Transport Layer Address of the gNB-CU. | - | | +| >>TNL Association Usage | O | | ENUMERATED (ue, non-ue, both, ...) | Indicates whether the TNL association is only used for UE-associated signalling, or non-UE-associated signalling, or both. For usage of this IE, refer to TS 38.472 [22]. | - | | +| Cells to be barred List | | 0..1 | | List of cells to be barred. | YES | ignore | +| >Cells to be barred List Item | | 1.. | | | EACH | ignore | +| >>NR CGI | M | | 9.3.1.12 | | - | | +| >>Cell Barred | M | | ENUMERATED (barred, not-barred, ...) | | - | | +| >>IAB Barred | O | | ENUMERATED (barred, not-barred, ...) | Corresponds to information provided in the iab-Support contained in the PLMN-IdentityInfo IE or contained in the NPN-IdentityInfo IE as defined in TS 38.331 [8]. The codepoint value "barred" indicates that the iab-Support is not sent in SIB1, and the codepoint value "not-barred" indicates that the iab-Support is sent in SIB1. | - | | +| Protected E-UTRA Resources List | | 0..1 | | List of Protected E-UTRA Resources. | YES | reject | +| >Protected E-UTRA Resources List Item | | 1..neNB> | | | | | +| >>Spectrum Sharing Group ID | M | | INTEGER (1..maxCellineNB) | Indicates the E-UTRA cells involved in resource coordination with the NR cells affiliated with the same Spectrum Sharing Group ID. | - | | +| >>E-UTRA Cells List | | 1 | | List of applicable E-UTRA cells. | - | | +| >>>E-UTRA Cells List Item | | 1 .. <maxCellineNB> | | | - | | +| >>>>EUTRA Cell ID | M | | BIT STRING (SIZE(28)) | Indicates the E-UTRAN Cell Identifier IE contained in the ECGI as defined in subclause 9.2.14 in TS 36.423 [9]. | - | | +| >>>>Served E-UTRA Cell Information | M | | 9.3.1.64 | | - | | +| Neighbour Cell Information List | | 0..1 | | | YES | ignore | +| >Neighbour Cell Information List Item | | 1 .. <maxCellineNB> | | | EACH | ignore | +| >>NR CGI | M | | 9.3.1.12 | | - | | +| >>Intended TDD DL-UL Configuration | O | | 9.3.1.89 | | - | | +| Transport Layer Address Info | O | | 9.3.2.5 | | YES | ignore | +| Uplink BH Non-UP Traffic Mapping | O | | 9.3.1.103 | | YES | reject | +| BAP Address | O | | 9.3.1.111 | Indicates a BAP address assigned to the IAB-donor-DU. | YES | ignore | +| CCO Assistance Information | O | | 9.3.1.211 | Indicates CCO Assistance Information for cells and beams served by the gNB-DU of the same NG-RAN node or for cells and beams not served by the gNB-DU. | YES | ignore | +| Cells for SON List | O | | 9.3.1.214 | | YES | ignore | +| gNB-CU Name | O | | PrintableString( SIZE(1..150,...) ) | Human readable name of the gNB-CU. | YES | ignore | +| Extended gNB-CU | O | | 9.3.1.206 | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------|----------|-----------------------------|-----------------------|-----------------------|-------------|----------------------| +| Name | | | | | | | +| Cells Allowed to be Deactivated List | | 0..1 | | | YES | ignore | +| > Cells Allowed to be Deactivated List Item | | 1..
ngNBDU> | | | EACH | ignore | +| >>NR CGI | M | | 9.3.1.12 | | - | | + +| Range bound | Explanation | +|------------------------|-------------------------------------------------------------------------------------| +| maxCellingNBDU | Maximum numbers of cells that can be served by a gNB-DU. Value is 512. | +| maxnoofTNLAssociations | Maximum numbers of TNL Associations between the gNB-CU and the gNB-DU. Value is 32. | +| maxCellineNB | Maximum no. cells that can be served by an eNB. Value is 256. | +| maxnoofSSBAreas | Maximum no. SSB Areas that can be served by a cell. Value is 64. | + +## 9.2.1.11 GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE + +This message is sent by a gNB-DU to a gNB-CU to acknowledge update of information associated to an F1-C interface instance. + +NOTE: If F1-C signalling transport is shared among several F1-C interface instance, this message may transfer updated information associated to several F1-C interface instances. + +Direction: gNB-DU → gNB-CU + +| 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 | +| Cells Failed to be Activated List | | 0..1 | | List of cells which are failed to be activated | YES | reject | +| > Cells Failed to be Activated Item | | 1..
ngNBDU> | | | EACH | reject | +| >>NR CGI | M | | 9.3.1.12 | | - | | +| >>Cause | M | | 9.3.1.2 | | - | | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| gNB-CU TNL Association Setup List | | 0..1 | | | YES | ignore | +| > gNB-CU TNL Association Setup Item IEs | | 1..ofTNLAss
ociations> | | | EACH | ignore | +| >>TNL Association Transport Layer Address | M | | CP Transport Layer Address 9.3.2.4 | Transport Layer Address of the gNB-CU | - | | +| gNB-CU TNL Association Failed to Setup List | | 0..1 | | | YES | ignore | +| > gNB-CU TNL Association Failed To Setup Item IEs | | 1..ofTNLAss
ociations> | | | EACH | ignore | +| >>TNL Association | M | | CP Transport | Transport Layer | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------|----------|-----------------------|-----------------------|-----------------------------------------------------------------|-------------|----------------------| +| Transport Layer Address | | | Layer Address 9.3.2.4 | Address of the gNB-CU | | | +| >>Cause | M | | 9.3.1.2 | | - | | +| Dedicated SI Delivery Needed UE List | | 0..1 | | List of UEs unable to receive system information from broadcast | YES | ignore | +| >Dedicated SI Delivery Needed UE List | | 1 .. | | | EACH | ignore | +| >>gNB-CU UE F1AP ID | M | | 9.3.1.4 | | - | - | +| >>NR CGI | M | | 9.3.1.12 | | - | - | +| Transport Layer Address Info | O | | 9.3.2.5 | | YES | ignore | +| Cells with SSBs Activated List | | 0..1 | | | YES | ignore | +| >Cells with SSBs Activated List | | 0.. | | | - | | +| >>NR CGI | M | | 9.3.1.12 | | - | | +| >>SSBs activated List | | 1 .. | | | - | | +| >>>SSB Index | M | | INTEGER (0..63) | Identifier of the SSB beam activated. | - | | + +| Range bound | Explanation | +|------------------------|---------------------------------------------------------------------------------| +| maxCellingNBDM | Maximum no. cells that can be served by a gNB-DU. Value is 512. | +| maxnoofTNLAssociations | Maximum no. of TNL Associations between the gNB-CU and the gNB-DU. Value is 32. | +| maxnoofUEIDs | Maximum no. of UEs that can be served by a gNB-DU. Value is 65536. | +| maxnoofSBAreas | Maximum no. SSB Areas that can be served by a cell. Value is 64. | + +## 9.2.1.12 GNB-CU CONFIGURATION UPDATE FAILURE + +This message is sent by the gNB-DU to indicate gNB-CU Configuration Update failure. + +Direction: gNB-DU → gNB-CU + +| 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 | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Time to wait | O | | 9.3.1.13 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.1.13 GNB-DU RESOURCE COORDINATION REQUEST + +This message is sent by a gNB-CU to a gNB-DU, to express the desired resource allocation for data traffic, for the sake of resource coordination. The message triggers gNB-DU resource coordination (for NR-initiated resource coordination), to indicate an initial resource offer by the E-UTRA node (for E-UTRA-initiated gNB-DU Resource Coordination), or to indicate the agreed resource allocation that is to be executed. + +Direction: gNB-CU → gNB-DU + +| 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 | +| Request type | M | | ENUMERATED
(offer,
execution, ...) | | YES | reject | +| E-UTRA – NR Cell
Resource Coordination
Request Container | M | | OCTET
STRING | In EN-DC case, includes the X2AP E-UTRA – NR CELL RESOURCE COORDINATION REQUEST message as defined in subclause 9.1.4.24 in TS 36.423 [9]. In NG-RAN cases, includes the XnAP E-UTRA – NR CELL RESOURCE COORDINATION REQUEST message as defined in subclause 9.1.2.23 in TS 38.423 [28]. | YES | reject | +| Ignore Coordination
Request Container | O | | ENUMERATED
(yes, ...) | | YES | reject | + +#### 9.2.1.14 GNB-DU RESOURCE COORDINATION RESPONSE + +This message is sent by a gNB-DU to a gNB-CU, to express the desired resource allocation for data traffic, as a response to the GNB-DU RESOURCE COORDINATION REQUEST. + +Direction: gNB-DU → gNB-CU + +| 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 | +| E-UTRA – NR Cell
Resource Coordination
Response Container | M | | OCTET
STRING | In EN-DC case, includes the X2AP E-UTRA – NR CELL RESOURCE COORDINATION RESPONSE message as | YES | reject | + +| | | | | | | | +|--|--|--|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| +| | | | | defined in subclause 9.1.4.25 in TS 36.423 [9].
In NG-RAN cases, includes the XnAP E-UTRA – NR CELL RESOURCE COORDINATION RESPONSE message as defined in subclause 9.1.2.24 in TS 38.423 [28]. | | | +|--|--|--|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| + +### 9.2.1.15 GNB-DU STATUS INDICATION + +This message is sent by the gNB-DU to indicate to the gNB-CU its status of overload. + +Direction: gNB-DU → gNB-CU + +| 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.23 | | YES | reject | +| gNB-DU Overload Information | M | | ENUMERATED (overloaded, not-overloaded) | | YES | reject | +| IAB Congestion Indication | O | | 9.3.1.227 | | YES | ignore | + +### 9.2.1.16 F1 REMOVAL REQUEST + +This message is sent by either the gNB-DU or the gNB-CU to initiate the removal of the interface instance and the related resources. + +Direction: gNB-DU → gNB-CU, gNB-CU → gNB-DU. + +| 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 | + +### 9.2.1.17 F1 REMOVAL RESPONSE + +This message is sent by either the gNB-DU or the gNB-CU to acknowledge the initiation of removal of the interface instance and the related resources. + +Direction: gNB-CU → gNB-DU, gNB-DU → gNB-CU. + +| 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 | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.1.18 F1 REMOVAL FAILURE + +This message is sent by either the gNB-DU or the gNB-CU to indicate that removing the interface instance and the related resources cannot be accepted. + +Direction: gNB-CU → gNB-DU, gNB-DU → gNB-CU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.3.1 | | YES | reject | +| Transaction ID | M | | 9.3.1.23 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.1.19 NETWORK ACCESS RATE REDUCTION + +This message is sent by the gNB-CU to indicate to the gNB-DU a need to reduce the rate at which UEs access the network. + +Direction: gNB-CU → gNB-DU + +| 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.23 | | YES | reject | +| UAC Assistance Information | M | | 9.3.1.83 | | YES | reject | + +### 9.2.1.20 RESOURCE STATUS REQUEST + +This message is sent by gNB-CU to gNB-DU to initiate the requested measurement according to the parameters given in the message. + +Direction: gNB-CU → gNB-DU. + +| 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 | +| gNB-CU Measurement ID | M | | INTEGER (1..4095,...) | Allocated by gNB-CU | YES | reject | +| gNB-DU Measurement ID | C-
ifRegistrationRequestStoporAdded | | INTEGER (1..4095,...) | Allocated by gNB-DU | YES | ignore | +| Registration Request | M | | ENUMERATED (start, stop, add, ...) | Type of request for which the resource status is required. | YES | ignore | +| Report Characteristics | C-
ifRegistrationRequest | | BIT STRING (SIZE(32)) | Each position in the bitmap indicates | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------|----------|---------------------------|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | tStart | | | measurement object the gNB-DU is requested to report.
First Bit = PRB Periodic,
Second Bit = TNL Capacity Ind Periodic,
Third Bit = Composite Available Capacity Periodic,
Fourth Bit = HW LoadInd Periodic,
Fifth Bit = Number of Active UEs Periodic,
Sixth Bit = NR-U Channel List Periodic.
Other bits shall be ignored by the gNB-DU. | | | +| Cell To Report List | | 0..1 | | Cell ID list to which the request applies. | YES | ignore | +| >Cell To Report Item | | 1 .. | | | - | | +| >>Cell ID | M | | NR CGI 9.3.1.12 | | - | | +| >>SSB To Report List | | 0..1 | | SSB list to which the request applies. | - | | +| >>>SSB To Report Item | | 1 .. | | | - | | +| >>>>SSB index | M | | INTEGER (0..63) | | - | | +| >>Slice To Report List | | 0..1 | | S-NSSAI list to which the request applies. | - | | +| >>>Slice To Report Item | | 1..< maxnoofB PLMNsN R> | | | - | | +| >>>>PLMN Identity | M | | 9.3.1.14 | Broadcast PLMN | - | | +| >>>>S-NSSAI List | | 1 | | | - | | +| >>>>>S-NSSAI Item | | 1 .. < maxnoofS licItems> | | | - | | +| >>>>>>S-NSSAI | M | | 9.3.1.38 | | - | | +| Reporting Periodicity | O | | ENUMERATED (500ms, 1000ms, | Periodicity that can be used for reporting of | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | 2000ms, 5000ms, 10000 ms, ...) | indicated measurements. Also used as the averaging window length for all measurement object if supported. This IE is ignored if the Registration Request IE is set to "add". | | | + +| Condition | Explanation | +|--------------------------------|-----------------------------------------------------------------------------------------------------| +| ifRegistrationRequestStoporAdd | This IE shall be present if the Registration Request IE is set to the value "stop" or "add". | +| ifRegistrationRequestStart | This IE shall be present if the Registration Request IE is set to the value "start". | + +| Range bound | Explanation | +|-------------------|---------------------------------------------------------------------------| +| maxCellingNBUDU | Maximum no. cells that can be served by a gNB-DU. Value is 512. | +| maxnoofSSBAreas | Maximum no. SSB Areas that can be served by a gNB node cell. Value is 64. | +| maxnoofSliceItems | Maximum no. of signalled slice support items. Value is 1024. | +| maxnoofBPLMNsNR | Maximum no. of PLMN Ids.broadcast in a cell. Value is 12. | + +### 9.2.1.21 RESOURCE STATUS RESPONSE + +This message is sent by gNB-DU to gNB-CU to indicate that the requested measurement is successfully initiated. + +Direction: gNB-DU → gNB-CU + +| 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 | +| gNB-CU Measurement ID | M | | INTEGER (1..4095,...) | Allocated by gNB-CU | YES | reject | +| gNB-DU Measurement ID | M | | INTEGER (1..4095,...) | Allocated by gNB-DU | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.1.22 RESOURCE STATUS FAILURE + +This message is sent by gNB-DU to gNB-CU to indicate that for any of the requested measurement objects the measurement cannot be initiated. + +Direction: gNB-DU → gNB-CU + +| 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 | +| gNB-CU Measurement ID | M | | INTEGER (1..4095,...) | Allocated by gNB-CU | YES | reject | +| gNB-DU Measurement ID | M | | INTEGER (1..4095,...) | Allocated by gNB-DU | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.1.23 RESOURCE STATUS UPDATE + +This message is sent by gNB-DU to gNB-CU to report the results of the requested measurements. + +Direction: gNB-DU → gNB-CU. + +| 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.23 | | YES | reject | +| gNB-CU Measurement ID | M | | INTEGER (1..4095,...) | Allocated by gNB-CU | YES | reject | +| gNB-DU Measurement ID | M | | INTEGER (1..4095,...) | Allocated by gNB-DU | YES | ignore | +| Hardware Load Indicator | O | | 9.3.1.136 | | YES | ignore | +| TNL Capacity Indicator | O | | 9.3.1.128 | | YES | ignore | +| Cell Measurement Result | | 0..1 | | | YES | ignore | +| >Cell Measurement Result Item | | 1 .. | | | - | | +| >>Cell ID | M | | NR CGI 9.3.1.12 | | - | | +| >>Radio Resource Status | O | | 9.3.1.129 | | - | | +| >>Composite Available Capacity Group | O | | 9.3.1.130 | | - | | +| >>Slice Available Capacity | O | | 9.3.1.134 | | - | | +| >>Number of Active UEs | O | | 9.3.1.135 | | - | | +| >>NR-U Channel List | | 0..1 | | | YES | ignore | +| >>>NR-U Channel Item | | 1.. | | | - | | +| >>>>NR-U Channel ID | M | | INTEGER (1..maxnoofNR-UChannelIDs, ...) | Identifies a portion of the NR-U Channel Bandwidth on which channel access procedure in shared spectrum has been performed in | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------|----------|-------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | the last reporting period. | | | +| >>>>Channel occupancy time percentage DL | M | | INTEGER (0..100) | The percentage of time for which the channel resources have been utilised for DL traffic served by the corresponding NR-U Channel of the serving cell. Value 100 indicates that the channel resources have been utilized for DL traffic served by the corresponding NR-U Channel of the serving cell for the whole duration between consecutive reporting. | - | | +| >>>>Energy Detection Threshold DL | M | | INTEGER (-100..-50,...) | Average ED Threshold used for DL channel sensing at the gNB. Value is in dBm. | - | | +| >>>>Channel Occupancy Time Percentage UL | O | | INTEGER (0..100) | The percentage of time for which the channel resources have been utilised for UL traffic served by the corresponding NR-U Channel of the serving cell for UEs that transmit to the serving cell. Value 100 indicates that the channel resources have been utilized for UL traffic served by the corresponding NR-U Channel of the serving cell for the whole duration between consecutive reporting. | YES | ignore | +| >>>>Radio Resource Status | O | | 9.3.1.295 | Indicates the radio resource status | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| NR-U | | | | per NR-U channel. | | | + +| Range bound | Explanation | +|-----------------------|-----------------------------------------------------------------| +| maxCellingNBUDU | Maximum no. cells that can be served by a gNB-DU. Value is 512. | +| maxnoofNR-UChannelIDs | Maximum no. NR-U Channel IDs in a cell. Value is 16. | + +### 9.2.1.24 DU-CU TA INFORMATION TRANSFER + +This message is sent by the gNB-DU to inform the gNB-CU about TA information. + +Direction: gNB-DU → gNB-CU + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------|----------|-----------------------|-------------------------|------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| TA Information List | | 0..1 | | | YES | ignore | +| > TA Information Item IEs | | 1 .. | | | EACH | ignore | +| >>Candidate Cell ID | M | | NR CGI 9.3.1.12 | | - | | +| >>TA Value | M | | INTEGER (0..4095) | Indicates the TA value as defined in TS 38.213 [31]. | - | | +| >>Preamble Index | M | | INTEGER (0..63) | | - | | +| >>RA-RNTI | M | | INTEGER (0..65535, ...) | RA-RNTI as defined in TS 38.321 [16]. | - | | +| >>Source gNB-DU ID | M | | gNB-DU ID 9.3.1.9 | | - | | + +| Range bound | Explanation | +|---------------|--------------------------------------------------------------| +| maxnoofTAList | Maximum no. of TA values to be sent, the maximum value is 8. | + +### 9.2.1.25 CU-DU TA INFORMATION TRANSFER + +This message is sent by the gNB-CU to inform the gNB-DU about TA information. + +Direction: gNB-CU → gNB-DU + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------|----------|-----------------------|-----------------------|--------------------------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| TA Information List | | 0..1 | | | YES | ignore | +| > TA Information Item IEs | | 1 .. | | | EACH | ignore | +| >>Candidate Cell ID | M | | NR CGI 9.3.1.12 | | - | | +| >>TA Value | M | | INTEGER (0..4095) | Indicates the TA value as defined in | - | | + +| | | | | | | | +|--------------------|---|--|----------------------------|---------------------------------------|---|--| +| | | | | TS 38.213 [31]. | | | +| >>Preamble Index | M | | INTEGER
(0..63) | | - | | +| >>RA-RNTI | M | | INTEGER
(0..65535, ...) | RA-RNTI as defined in TS 38.321 [16]. | - | | +| >>Source gNB-DU ID | M | | gNB-DU ID
9.3.1.9 | | - | | + +| Range bound | Explanation | +|---------------|--------------------------------------------------------------| +| maxnoofTAList | Maximum no. of TA values to be sent, the maximum value is 8. | + +## 9.2.1.26 RACH INDICATION + +This message is sent by the gNB-DU to inform the gNB-CU about one or more random access procedures performed at the gNB-DU. + +Direction: gNB-DU → gNB-CU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|----------|------------------------------------------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| RA Report Indication List | | 1 | | | YES | reject | +| >RA Report Indication List Item | | 1.. | | | - | - | +| >>gNB-CU UE F1AP ID | M | | 9.3.1.4 | | - | | + +| Range bound | Explanation | +|----------------------------------|------------------------------------------------------------------------------------------| +| maxnoofUEsforRAReportIndications | Maximum number of UEs from which gNB-DU is interested to collect RA report. Value is 64. | + +## 9.2.2 UE Context Management messages + +### 9.2.2.1 UE CONTEXT SETUP REQUEST + +This message is sent by the gNB-CU to request the setup of a UE context. + +Direction: gNB-CU → gNB-DU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | O | | 9.3.1.5 | | YES | ignore | +| SpCell ID | M | | NR CGI
9.3.1.12 | Special Cell as defined in TS 38.321 [16]. For handover case, | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------|----------|----------------------------------|-------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | this IE is considered as target cell. | | | +| ServCellIndex | M | | INTEGER (0..31,...) | | YES | reject | +| SpCell UL Configured | O | | Cell UL Configured 9.3.1.33 | | YES | ignore | +| CU to DU RRC Information | M | | 9.3.1.25 | | YES | reject | +| Candidate SpCell List | | 0..1 | | | YES | ignore | +| >Candidate SpCell Item IEs | | 1 .. | | | EACH | ignore | +| >>Candidate SpCell ID | M | | NR CGI 9.3.1.12 | Special Cell as defined in TS 38.321 [16] | - | | +| DRX Cycle | O | | DRX Cycle 9.3.1.24 | | YES | ignore | +| Resource Coordination Transfer Container | O | | OCTET STRING | Includes the MeNB Resource Coordination Information IE as defined in subclause 9.2.116 of TS 36.423 [9] for EN-DC case or MR-DC Resource Coordination Information IE as defined in TS 38.423 [28] for NGEN-DC and NE-DC cases. | YES | ignore | +| SCell To Be Setup List | | 0..1 | | | YES | ignore | +| >SCell to Be Setup Item IEs | | 1.. | | | EACH | ignore | +| >>SCell ID | M | | NR CGI 9.3.1.12 | SCell Identifier in gNB | - | | +| >>SCellIndex | M | | INTEGER (1..31) | | - | | +| >>SCell UL Configured | O | | Cell UL Configured 9.3.1.33 | | - | | +| >>servingCellMO | O | | INTEGER (1..64) | | YES | ignore | +| SRB to Be Setup List | | 0..1 | | | YES | reject | +| >SRB to Be Setup Item IEs | | 1 .. | | | EACH | reject | +| >>SRB ID | M | | 9.3.1.7 | | - | | +| >>Duplication Indication | O | | ENUMERATED (true, ..., false) | If included, it should be set to true.
This IE is ignored | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------------|----------|-------------------------|-------------------------------|-------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | if the Additional Duplication Indication IE is present. | | | +| >>Additional Duplication Indication | O | | ENUMERATED (three, four, ...) | | YES | ignore | +| >>SDT RLC Bearer Configuration | O | | OCTET STRING | Includes the RLC-BearerConfig IE defined in subclause 6.3.2 of TS 38.331 [8] | YES | ignore | +| >>SRB Mapping Info | O | | Uu RLC Channel ID 9.3.1.266 | This IE contains the mapped Uu Relay RLC CH ID for the SRB | YES | ignore | +| DRB to Be Setup List | | 0..1 | | | YES | reject | +| > DRB to Be Setup Item IEs | | 1 .. | | | EACH | reject | +| >>DRB ID | M | | 9.3.1.8 | | - | | +| >>CHOICE QoS Information | M | | | | - | | +| >>> E-UTRAN QoS | | | | | | | +| >>>>E-UTRAN QoS | M | | 9.3.1.19 | Shall be used for EN-DC case to convey E-RAB Level QoS Parameters | - | | +| >>> DRB Information | | | | | | | +| >>>> DRB Information | | 1 | | Shall be used for NG-RAN cases | YES | ignore | +| >>>>> DRB QoS | M | | 9.3.1.45 | | - | | +| >>>>> S-NSSAI | M | | 9.3.1.38 | | - | | +| >>>>> Notification Control | O | | 9.3.1.56 | | - | | +| >>>>> Flows Mapped to DRB Item | | 1 .. | | | - | | +| >>>>>> QoS Flow Identifier | M | | 9.3.1.63 | | - | | +| >>>>>> QoS Flow Level QoS Parameters | M | | 9.3.1.45 | | - | | +| >>>>>> QoS Flow Mapping Indication | O | | 9.3.1.72 | | YES | ignore | +| >>>>>> TSC Traffic Characteristics | O | | 9.3.1.141 | Traffic pattern information associated with the QFI. Details in TS 23.501 [21]. | YES | ignore | +| >>>> ECN Marking or Congestion Information | O | | 9.3.1.321 | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------|----------|--------------------------------------|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Reporting Request | | | | | | | +| >>UL UP TNL Information to be setup List | | 1 | | | - | | +| >>>UL UP TNL Information to Be Setup Item IEs | | 1 .. | | | - | | +| >>>>UL UP TNL Information | M | | UP Transport Layer Information 9.3.2.1 | gNB-CU endpoint of the F1 transport bearer. For delivery of UL PDUs. | - | | +| >>>>BH Information | O | | 9.3.1.114 | | YES | ignore | +| >>>>DRB Mapping Info | O | | Uu RLC Channel ID 9.3.1.266 | This IE contains the mapped Uu Relay RLC CH ID of the DL tunnel corresponding to such UL tunnel | YES | ignore | +| >>RLC Mode | M | | 9.3.1.27 | | - | | +| >>UL Configuration | O | | UL Configuration 9.3.1.31 | Information about UL usage in gNB-DU. | - | | +| >>Duplication Activation | O | | 9.3.1.36 | Information on the initial state of CA based UL PDCP duplication. This IE is ignored if the RLC Duplication Information IE is present. | - | | +| >>DC Based Duplication Configured | O | | ENUMERATED (true, ..., false) | Indication on whether DC based PDCP duplication is configured or not. If included, it should be set to true. | YES | reject | +| >>DC Based Duplication Activation | O | | Duplication Activation 9.3.1.36 | Information on the initial state of DC based UL PDCP duplication. This IE is ignored if the RLC Duplication Information IE is present. | YES | reject | +| >>DL PDCP SN length | M | | ENUMERATED (12bits, 18bits, ...) | | YES | ignore | +| >>UL PDCP SN length | O | | ENUMERATED (12bits, ...) | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------|------------------|----------------------------------------------|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | 18bits, ...) | | | | +| >>Additional PDCP Duplication TNL List | | 0..1 | | | YES | ignore | +| >>>Additional PDCP Duplication TNL Items | | 1 .. | | | EACH | ignore | +| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information 9.3.2.1 | gNB-CU endpoint of the F1 transport bearer. For delivery of UL PDUs. | - | | +| >>>>BH Information | O | | 9.3.1.114 | | YES | ignore | +| >>RLC Duplication Information | O | | 9.3.1.146 | | YES | ignore | +| >>SDT RLC Bearer Configuration | O | | OCTET STRING | RLC-BearerConfig IE defined in subclause 6.3.2 of TS 38.331 [8] | YES | ignore | +| Inactivity Monitoring Request | O | | ENUMERATED (true, ...) | | YES | reject | +| RAT-Frequency Priority Information | O | | 9.3.1.34 | | YES | reject | +| RRC-Container | O | | 9.3.1.6 | Includes the DL-DCCH-Message message as defined in subclause 6.2 of TS 38.331 [8], encapsulated in a PDCP PDU. | YES | ignore | +| Masked IMEISV | O | | 9.3.1.55 | | YES | ignore | +| Serving PLMN | O | | PLMN ID 9.3.1.14 | Indicates the PLMN serving the UE. | YES | ignore | +| gNB-DU UE Aggregate Maximum Bit Rate Uplink | C-
ifDRBSetup | | Bit Rate 9.3.1.22 | The gNB-DU UE Aggregate Maximum Bit Rate Uplink is to be enforced by the gNB-DU. | YES | ignore | +| RRC Delivery Status Request | O | | ENUMERATED (true, ...) | Indicates whether RRC DELIVERY REPORT procedure is requested for the RRC message. | YES | ignore | +| Resource Coordination Transfer Information | O | | 9.3.1.73 | | YES | ignore | +| servingCellMO | O | | INTEGER (1..64, ...) | | YES | ignore | +| New gNB-CU UE F1AP ID | O | | gNB-CU UE F1AP ID | | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|------------------------------|----------------------------------------|--------------------------------------------------------------------|-------------|----------------------| +| | | | 9.3.1.1.4 | | | | +| RAN UE ID | O | | OCTET STRING (SIZE (8)) | | YES | ignore | +| Trace Activation | O | | 9.3.1.88 | | YES | ignore | +| Additional RRM Policy Index | O | | 9.3.1.90 | | YES | ignore | +| BH RLC Channel to be Setup List | | 0..1 | | | YES | reject | +| >BH RLC Channel to be Setup Item IEs | | 1 .. | | | EACH | reject | +| >>BH RLC CH ID | M | | 9.3.1.113 | | - | | +| >>CHOICE BH QoS Information | M | | | | | | +| >>>BH RLC CH QoS | | | | | | | +| >>>>BH RLC CH QoS | M | | QoS Flow Level QoS Parameters 9.3.1.45 | Shall be used for SA case. | - | | +| >>>E-UTRAN BH RLC CH QoS | | | | | | | +| >>>>E-UTRAN BH RLC CH QoS | M | | E-UTRAN QoS 9.3.1.19 | Shall be used for EN-DC case. | - | | +| >>>Control Plane Traffic Type | | | | | | | +| >>>>Control Plane Traffic Type | M | | 9.3.1.115 | | - | | +| >>RLC Mode | M | | 9.3.1.27 | | - | | +| >>BAP Control PDU Channel | O | | ENUMERATED (true, ...) | | - | | +| >>Traffic Mapping Information | O | | 9.3.1.95 | | - | | +| Configured BAP Address | O | | 9.3.1.111 | The BAP address configured for the corresponding child IAB-node. | YES | reject | +| NR V2X Services Authorized | O | | 9.3.1.116 | | YES | ignore | +| LTE V2X Services Authorized | O | | 9.3.1.117 | | YES | ignore | +| NR UE Sidelink Aggregate Maximum Bit Rate | O | | 9.3.1.119 | This IE applies only if the UE is authorized for NR V2X services. | YES | ignore | +| LTE UE Sidelink Aggregate Maximum Bit Rate | O | | 9.3.1.118 | This IE applies only if the UE is authorized for LTE V2X services. | YES | ignore | +| PC5 Link Aggregate Bit Rate | O | | Bit Rate 9.3.1.22 | Only applies for non-GBR and unicast QoS Flows. | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------------|----------------|----------------------------------|--------------------------------------------------------|--------------------------------------------------------------------------------------|-------------|----------------------| +| SL DRB to Be Setup List | | 0..1 | | | YES | reject | +| >SL DRB to Be Setup Item IEs | | 1 ..
SLDRBs> | | | EACH | reject | +| >>SL DRB ID | M | | 9.3.1.120 | | - | | +| >>SL DRB Information | | 1 | | | YES | ignore | +| >>>SL DRB QoS | M | | PC5 QoS Parameters
9.3.1.122 | | - | | +| >>>Flows Mapped to SL DRB Item | | 1 ..
PC5QoSFlows> | | | - | | +| >>>>PC5 QoS Flow Identifier | | | 9.3.1.121 | | - | | +| >>RLC mode | M | | 9.3.1.27 | | - | | +| >>Duplication Indication | O | | ENUMERATED
(true, ..., false) | If included, it should be set to true. | - | | +| Conditional Inter-DU Mobility Information | O | | | | YES | reject | +| >CHO Trigger | M | | ENUMERATED
(CHO-initiation, CHO-replace, ...) | | - | - | +| >Target gNB-DU UE F1AP ID | C-
ifCHOMod | | 9.3.1.5 | Allocated at the target gNB-DU | - | - | +| >Estimated Arrival Probability | O | | INTEGER
(1..100) | | YES | ignore | +| Management Based MDT PLMN List | O | | MDT PLMN List
9.3.1.151 | | YES | ignore | +| Serving NID | O | | 9.3.1.155 | | YES | reject | +| F1-C Transfer Path | O | | 9.3.1.207 | | YES | reject | +| F1-C Transfer Path NRDC | O | | 9.3.1.228 | | YES | reject | +| MDT Polluted Measurement Indicator | O | | ENUMERATED
(IDC,no-IDC, ...) | Indication on whether MDT Measurement affect (e.g. IDC) is undertaken or not. | YES | ignore | +| SCG Activation Request | O | | 9.3.1.233 | | YES | ignore | +| Old CG-SDT Session Info | O | | CG-SDT Session Info
9.3.1.261 | | YES | ignore | +| 5G ProSe Authorized | O | | 9.3.1.268 | | YES | ignore | +| 5G ProSe UE PC5 Aggregate Maximum Bit Rate | O | | NR UE Sidelink Aggregate Maximum Bit Rate
9.3.1.119 | This IE applies only if the UE is authorized for 5G ProSe services. | YES | ignore | +| 5G ProSe PC5 Link Aggregate Bit Rate | O | | Bit Rate
9.3.1.22 | This IE applies only if the UE is authorized for 5G ProSe services, and only applies | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------|----------|-------------------------------|----------------------------------------|---------------------------------------------------------------------------|-------------|----------------------| +| | | | | for non-GBR and unicast QoS Flows. | | | +| Uu RLC Channel to Be Setup List | | 0..1 | | | YES | reject | +| >Uu RLC Channel to be Setup Item IEs | | 1 .. | | | - | | +| >>Uu RLC Channel ID | M | | 9.3.1.266 | | - | | +| >>CHOICE Uu RLC Channel QoS Information | M | | | | - | | +| >>>Uu RLC Channel QoS | | | | | | | +| >>>>Uu RLC Channel QoS | M | | QoS Flow Level QoS Parameters 9.3.1.45 | | - | | +| >>>Uu Control Plane Traffic Type | | | | | | | +| >>>>Uu Control Plane Traffic Type | M | | ENUMERATED (SRB0, SRB1, SRB2, ...) | This IE indicates the type of SRB conveyed via the Uu Relay RLC Channel. | - | | +| >>RLC Mode | M | | 9.3.1.27 | | - | | +| PC5 RLC Channel to Be Setup List | | 0..1 | | | YES | reject | +| >PC5 RLC Channel to be Setup Item IEs | | 1 .. | | | - | | +| >>PC5 RLC Channel ID | M | | 9.3.1.265 | | - | | +| >>Remote UE Local ID | O | | 9.3.1.267 | This IE is not used in this version of the specification. | - | | +| >>CHOICE PC5 RLC Channel QoS Information | M | | | | - | | +| >>>PC5 RLC Channel QoS | | | | | | | +| >>>>PC5 RLC Channel QoS | M | | QoS Flow Level QoS Parameters 9.3.1.45 | | - | | +| >>>PC5 Control Plane Traffic Type | | | | | | | +| >>>>PC5 Control Plane Traffic Type | M | | ENUMERATED (SRB1, SRB2, ...) | This IE indicates the type of SRB conveyed via the PC5 Relay RLC Channel. | - | | +| >>RLC Mode | M | | 9.3.1.27 | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------------|----------|--------------------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Path Switch Configuration | O | | 9.3.1.263 | | YES | ignore | +| gNB-DU UE Slice Maximum Bit Rate List | O | | 9.3.1.271 | The Slice Maximum Bit Rate List is the maximum aggregate UL bit rate per slice, to be enforced by the gNB-DU, if feasible. This IE is ignored if the DRB to Be Setup List IE is not present. | YES | ignore | +| Multicast MBS Session Setup List | O | | Multicast MBS Session List 9.3.1.272 | The list of MBS Session ID that UE has joined. | YES | reject | +| UE Multicast MRB to Be Setup List | | 0..1 | | | YES | reject | +| >UE Multicast MRB to Be Setup Item IEs | | 1 .. | | | EACH | reject | +| >>MRB ID | M | | 9.3.1.224 | MRB ID for the UE. | - | | +| >>MBS PTP Retransmission Tunnel Required | O | | 9.3.2.10 | | - | | +| >>MBS PTP Forwarding Tunnel Required Information | O | | MRB Progress Information 9.3.2.12 | | - | | +| >>Source MRB ID | O | | 9.3.1.224 MRB ID | In case of inter-DU handover, indicates the MRB ID provided to the UE in the source cell. | - | ignore | +| ServingCellIMO List | | 0..1 | | For NCD-SSBs | YES | ignore | +| >ServingCellIMO Item IEs | | 1 .. | | | EACH | ignore | +| >>servingCellIMO | M | | INTEGER (1..64) | | - | | +| >>SSB frequency | M | | INTEGER (0..3279165) | ARFCN | - | | +| Network Controlled Repeater Authorized | O | | 9.3.1.288 | | YES | ignore | +| SDT Volume Threshold | O | | INTEGER(1..192000,...) | Unit: byte. | YES | ignore | +| LTM InformationSetup | | 0..1 | | | YES | reject | +| >LTM Indicator | M | | ENUMERATED (true, ...) | | - | | +| >LTM Configuration ID | M | | INTEGER (1..8) | Corresponds to the LTM-CandidateId IE, as defined in TS | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------|----------|-------|------------------------|-----------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | 38.331 [8]. | | | +| >Reference Configuration | O | | 9.3.1.292 | | - | | +| >CSI Resource Configuration | O | | OCTET STRING | Includes the Itm-CSI-ResourceConfigToAddModList IE as defined in TS 38.331 [8]. | - | | +| LTM Configuration ID Mapping List | O | | 9.3.1.294 | | YES | reject | +| Early Sync Information Request | | 0..1 | | | YES | ignore | +| >Request for RACH Configuration | O | | ENUMERATED (true, ...) | | - | | +| Source gNB-DU ID | O | | gNB-DU ID 9.3.1.9 | | YES | reject | +| Path Addition Information | O | | 9.3.1.296 | This IE contains either the Indirect Path Addition IE or the N3C Indirect Path Addition IE. | YES | ignore | +| NR A2X Services Authorized | O | | 9.3.1.323 | | YES | ignore | +| LTE A2X Services Authorized | O | | 9.3.1.324 | | YES | ignore | +| NR UE Sidelink Aggregate Maximum Bit Rate for A2X | O | | 9.3.1.119 | This IE applies only if the UE is authorized for NR A2X services. | YES | ignore | +| LTE UE Sidelink Aggregate Maximum Bit Rate for A2X | O | | 9.3.1.118 | This IE applies only if the UE is authorized for LTE A2X services. | YES | ignore | + +| Range bound | Explanation | +|----------------------------|-----------------------------------------------------------------------------------------------| +| maxnoofSCells | Maximum no. of SCells allowed towards one UE, the maximum value is 32. | +| maxnoofServingCellMOs | Maximum number of ServingCellMOs for NCD-SSB per cell. Maximum value is 16 | +| maxnoofSRBs | Maximum no. of SRB allowed towards one UE, the maximum value is 8. | +| maxnoofDRBs | Maximum no. of DRB allowed towards one UE, the maximum value is 64. | +| maxnoofULUP TNLInformation | Maximum no. of ULUP TNL Information allowed towards one DRB, the maximum value is 2. | +| maxnoofCandidateSpCells | Maximum no. of SpCells allowed towards one UE, the maximum value is 64. | +| maxnoofQoSFlows | Maximum no. of flows allowed to be mapped to one DRB, the maximum value is 64. | +| maxnoofBHRLCChannels | Maximum no. of BH RLC channels allowed towards one IAB-node, the maximum value is 65536. | +| maxnoofSLDRBs | Maximum no. of SL DRB allowed for NR sidelink communication per UE, the maximum value is 512. | +| maxnoofPC5QoSFlows | Maximum no. of PC5 QoS flow allowed towards one UE for NR | + +| Range bound | Explanation | +|-------------------------------------|------------------------------------------------------------------------------------------------------------------------| +| | sidelink communication, the maximum value is 2048. | +| maxnoofAdditionalPDCPDuplicationTNL | Maximum no. of additional UP TNL Information allowed towards one DRB, the maximum value is 2. | +| maxnoofUuRLCChannels | Maximum no. of Uu Relay RLC channels for L2 U2N relaying or L2 N3C relaying per Relay UE, the maximum value is 32. | +| maxnoofPC5RLCChannels | Maximum no. of PC5 Relay RLC channels allowed for L2 U2N relaying per Remote UE or Relay UE, the maximum value is 512. | +| maxnoofMRBsforUE | Maximum no. of multicast MRB allowed towards one UE, the maximum value is 64. | + +| Condition | Explanation | +|------------|--------------------------------------------------------------------------------------------| +| ifDRBSetup | This IE shall be present only if the DRB to Be Setup List IE is present. | +| ifCHOmod | This IE shall be present if the CHO Trigger IE is present and set to "CHO-replace". | + +## 9.2.2.2 UE CONTEXT SETUP RESPONSE + +This message is sent by the gNB-DU to confirm the setup of a UE context. + +Direction: gNB-DU → gNB-CU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| DU To CU RRC Information | M | | 9.3.1.26 | | YES | reject | +| C-RNTI | O | | 9.3.1.32 | C-RNTI allocated at the gNB-DU | YES | ignore | +| Resource Coordination Transfer Container | O | | OCTET STRING | Includes the SgNB Resource Coordination Information IE as defined in subclause 9.2.117 of TS 36.423 [9] for EN-DC case or MR-DC Resource Coordination Information IE as defined in TS 38.423 [28] for NGEN-DC and NE-DC cases. | YES | ignore | +| Full Configuration | O | | ENUMERATED (full, ...) | | YES | reject | +| DRB Setup List | | 0..1 | | The List of DRBs which are successfully established. | YES | ignore | +| >DRB Setup Item list | | 1 .. | | | EACH | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------------|----------|---------------------------------------------------------------|--------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>DRB ID | M | | 9.3.1.1.8 | | - | | +| >>LCID | O | | 9.3.1.1.35 | LCID for the primary path or for the split secondary path for fallback to split bearer if PDCP duplication is applied. | - | | +| >>DL UP TNL Information to be setup List | | 1 | | | - | | +| >>>DL UP TNL Information to Be Setup Item IEs | | 1 ..
DLUPTNL
Information> | | | - | | +| >>>>DL UP TNL Information | M | | UP Transport Layer Information 9.3.2.1 | gNB-DU endpoint of the F1 transport bearer. For delivery of DL PDUs. | - | | +| >>Additional PDCP Duplication TNL List | | 0..1 | | | YES | ignore | +| >>>Additional PDCP Duplication TNL Items | | 1 ..
Additional
PDCPDup
licationTN
L> | | | EACH | ignore | +| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information 9.3.2.1 | gNB-DU endpoint of the F1 transport bearer. For delivery of DL PDUs. | - | | +| >>>>BH Information | O | | 9.3.1.1.114 | This IE is not used in this version of the specification. | YES | ignore | +| >>Current QoS Parameters Set Index | O | | Alternative QoS Parameters Set Index 9.3.1.1.123 | Index to the currently fulfilled alternative QoS parameters set. | YES | ignore | +| >>TSC Traffic Characteristics Feedback | O | | 9.3.1.1.302 | | YES | ignore | +| >>ECN Marking or Congestion Information Reporting Status | O | | 9.3.1.1.322 | | YES | ignore | +| SRB Failed to Setup List | | 0..1 | | | YES | ignore | +| >SRB Failed to Setup Item | | 1 ..
SRBs> | | | EACH | ignore | +| >>SRB ID | M | | 9.3.1.7 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| DRB Failed to Setup | | 0..1 | | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------|----------|---------------------------------|------------------------------------|-----------------------------------------------------------------|-------------|----------------------| +| List | | | | | | | +| >DRB Failed to Setup Item | | 1 ..
| | | EACH | ignore | +| >>DRB ID | M | | 9.3.1.8 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| SCell Failed To Setup List | | 0..1 | | | YES | ignore | +| >SCell Failed to Setup Item | | 1 ..
| | | EACH | ignore | +| >>SCell ID | M | | NR CGI
9.3.1.12 | SCell Identifier in gNB | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| Inactivity Monitoring Response | O | | ENUMERATED
(not-supported, ...) | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| SRB Setup List | | 0..1 | | | YES | ignore | +| >SRB Setup Item | | 1 ..
| | | EACH | ignore | +| >>SRB ID | M | | 9.3.1.7 | | - | | +| >>LCID | M | | 9.3.1.35 | LCID for the primary path if PDCP duplication is applied | - | | +| BH RLC Channel Setup List | | 0..1 | | The list of BH RLC channels which are successfully established. | YES | ignore | +| >BH RLC Channel Setup Item | | 1 ..
| | | EACH | ignore | +| >>BH RLC CH ID | M | | 9.3.1.113 | | - | | +| BH RLC Channel Failed to be Setup List | | 0..1 | | The list of BH RLC channels whose setup has failed. | YES | ignore | +| >BH RLC Channel Failed to be Setup Item | | 1 ..
| | | EACH | ignore | +| >>BH RLC CH ID | M | | 9.3.1.113 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| SL DRB Setup List | | 0..1 | | The List of SL DRBs which are successfully established. | YES | ignore | +| >SL DRB Setup Item IEs | | 1 ..
| | | EACH | ignore | +| >>SL DRB ID | M | | 9.3.1.120 | | - | | +| SL DRB Failed To Setup List | | 0..1 | | | EACH | ignore | +| >SL DRB Failed To | | 1 .. | | | EACH | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|-----------------------------------|-----------------------|-----------------------------------------------------------------|-------------|----------------------| +| Setup Item IE | | | | | | | +| >>SL DRB ID | M | | 9.3.1.120 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| Requested Target Cell ID | O | | NR CGI
9.3.1.12 | Special Cell indicated in the UE CONTEXT SETUP REQUEST message. | YES | reject | +| SCG Activation Status | O | | 9.3.1.234 | | YES | ignore | +| Uu RLC Channel Setup List | | 0..1 | | | YES | ignore | +| >Uu RLC Channel Setup Item IEs | | 1 ..
| | | - | | +| >>Uu RLC Channel ID | M | | 9.3.1.266 | | - | | +| Uu RLC Channel Failed to be Setup List | | 0..1 | | | YES | ignore | +| >Uu RLC Channel Failed to be Setup Item IEs | | 1 ..
| | | - | | +| >>Uu RLC Channel ID | M | | 9.3.1.266 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| PC5 RLC Channel Setup List | | 0..1 | | | YES | ignore | +| >PC5 RLC Channel Setup Item IEs | | 1 ..
| | | - | | +| >>PC5 RLC Channel ID | M | | 9.3.1.265 | | - | | +| >>Remote UE Local ID | O | | 9.3.1.267 | This IE is not used in this version of the specification. | | | +| PC5 RLC Channel Failed to be Setup List | | 0..1 | | | YES | ignore | +| >PC5 RLC Channel Failed to be Setup Item IEs | | 1 ..
| | | - | | +| >>PC5 RLC Channel ID | M | | 9.3.1.265 | | - | | +| >>Remote UE Local ID | O | | 9.3.1.267 | This IE is not used in this version of the specification. | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| ServingCellMO-encoded-in-CGC List | | 0..1 | | | YES | ignore | +| >ServingCellMO-encoded-in-CGC Item IEs | | 1 ..
| | The servingCellMO which has been encoded in CellGroupConfig | EACH | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|--------------------------------|----------------------------|---------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | IE. | | | +| >>servingCellMO | M | | INTEGER (1..64) | | - | | +| >>BWP ID | M | | INTEGER (0..4) | | YES | ignore | +| UE Multicast MRB Setup List | | 0..1 | | | YES | reject | +| >UE Multicast MRB Setup Item IEs | | 1 ..
MRBsforUE> | | | EACH | reject | +| >>MRB ID | M | | 9.3.1.224 | MRB ID for the UE. | - | | +| >>Multicast F1-U Context Reference CU | M | | 9.3.2.13 | | - | | +| Dedicated SI Delivery Indication | O | | ENUMERATED (true, ...) | | YES | ignore | +| Configured BWP List | | 0..1 | | This IE is present when the gNB-DU configures at least one BWP with NCD-SSB or without SSB. | YES | ignore | +| >Configured BWP Item IEs | | 1 ..
BWPs> | | | EACH | ignore | +| >>BWP-Id | M | | INTEGER (0..4) | The IE is used to refer to one BWP. | - | | +| >>BWP Location And Bandwidth | M | | INTEGER (0..37949) | The IE type range is the same as the locationAndBandwidth IE in BWP IE as specified in TS 38.331 [8]. | | | +| Early Sync Information | | 0..1 | | | YES | ignore | +| >TCI States Configurations List | M | | 9.3.1.293 | | - | | +| >RACH Configuration | O | | OCTET STRING | Includes the EarlyUL-SyncConfig IE, as defined in TS 38.331 [8]. | - | | +| LTM Configuration | | 0..1 | | | YES | ignore | +| >SSB Information Item | M | | | | - | | +| >>SSB Time/Frequency Configuration | M | | 9.3.1.203 | | - | | +| >>NR PCI | M | | INTEGER (0..1007) | | - | | +| >LTM Reference Configuration | O | | OCTET STRING | Includes the CellGroupConfig IE, as defined in TS 38.331 [8]. | - | | +| >LTM Complete Configuration Indicator | O | | ENUMERATED (complete, ...) | | - | | + +| Range bound | Explanation | +|-------------------------------------|------------------------------------------------------------------------------------------------------------------------| +| maxnoofSCells | Maximum no. of SCells allowed towards one UE, the maximum value is 32. | +| maxnoofSRBs | Maximum no. of SRB allowed towards one UE, the maximum value is 8. | +| maxnoofDRBs | Maximum no. of DRB allowed towards one UE, the maximum value is 64. | +| maxnoofDLUPTNLInformation | Maximum no. of DL UP TNL Information allowed towards one DRB, the maximum value is 2. | +| maxnoofBHRLCChannels | Maximum no. of BH RLC channels allowed towards one IAB-node, the maximum value is 65536. | +| maxnoofSLDRBs | Maximum no. of SL DRB allowed for NR sidelink communication per UE, the maximum value is 512. | +| maxnoofAdditionalPDCPDuplicationTNL | Maximum no. of additional UP TNL Information allowed towards one DRB, the maximum value is 2. | +| maxnoofUuRLCChannels | Maximum no. of Uu Relay RLC channels for L2 U2N relaying or L2 N3C relaying per Relay UE, the maximum value is 32. | +| maxnoofPC5RLCChannels | Maximum no. of PC5 Relay RLC channels allowed for L2 U2N relaying per Remote UE or Relay UE, the maximum value is 512. | +| maxNrofBWPs | Maximum number of BWPs per serving cell, the maximum value is 8. | +| maxnoofMRBsforUE | Maximum no. of multicast MRB allowed towards one UE, the maximum value is 64. | + +### 9.2.2.3 UE CONTEXT SETUP FAILURE + +This message is sent by the gNB-DU to indicate that the setup of the UE context was unsuccessful. + +Direction: gNB-DU → gNB-CU + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP 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 | +| Potential SpCell List | | 0..1 | | | YES | ignore | +| >Potential SpCell Item IEs | | 0..
PotentialS
pCells> | | | EACH | ignore | +| >>Potential SpCell ID | M | | NR CGI
9.3.1.12 | Special Cell as defined in TS 38.321 [16] | - | | +| Requested Target Cell ID | O | | NR CGI
9.3.1.12 | Special Cell indicated in the UE CONTEXT SETUP REQUEST message. | YES | reject | + +| Range bound | Explanation | +|-------------------------|-------------------------------------------------------------------------| +| maxnoofPotentialSpCells | Maximum no. of SpCells allowed towards one UE, the maximum value is 64. | + +### 9.2.2.4 UE CONTEXT RELEASE REQUEST + +This message is sent by the gNB-DU to request the gNB-CU to release the UE-associated logical F1 connection or candidate cells in conditional handover or conditional PSCell addition or conditional PSCell change or LTM or subsequent CPAC. + +Direction: gNB-DU → gNB-CU + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Candidate Cells To Be Cancelled List | | 0 ..
CellsinCH
O> | | | YES | reject | +| >Target Cell ID | M | | NR CGI
9.3.1.12 | | - | - | +| LTM Cells To Be Released List | O | | 9.3.1.291 | | YES | ignore | + +| Range bound | Explanation | +|-------------------|--------------------------------------------------------------------------------| +| maxnoofCellsinCHO | Maximum no. cells that can be prepared for a conditional mobility. Value is 8. | + +### 9.2.2.5 UE CONTEXT RELEASE COMMAND + +This message is sent by the gNB-CU to request the gNB-DU to release the UE-associated logical F1 connection or candidate cells in conditional handover or conditional PSCell addition or conditional PSCell change or LTM or subsequent CPAC. + +Direction: gNB-CU → gNB-DU + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| RRC-Container | O | | 9.3.1.6 | Includes the DL-DCCH-Message message as defined in subclause 6.2 of TS 38.331 [8] encapsulated in a PDCP PDU, or the DL-CCCH-Message message as defined in subclause 6.2 of TS 38.331 [8]. | YES | ignore | +| SRB ID | C-
ifRRCCont | | 9.3.1.7 | The gNB-DU sends the RRC | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------|----------|--------------------------|------------------------|-----------------------------------------------------------------------------------|-------------|----------------------| +| | ainer | | | message on the indicated SRB. | | | +| old gNB-DU UE F1AP ID | O | | 9.3.1.5 | Include it if RRCReestablishmentRequest is not accepted | YES | ignore | +| Execute Duplication | O | | ENUMERATED (true, ...) | This IE may be sent only if duplication has been configured for the UE. | YES | ignore | +| RRc Delivery Status Request | O | | ENUMERATED (true, ...) | Indicates whether RRC DELIVERY REPORT procedure is requested for the RRC message. | YES | ignore | +| Candidate Cells To Be Cancelled List | | 0 .. | | | YES | reject | +| >Target Cell ID | M | | NR CGI 9.3.1.12 | | - | - | +| Positioning Context Reservation Indication | O | | ENUMERATED (True,...) | | YES | ignore | +| CG-SDT Kept Indicator | O | | ENUMERATED (true, ...) | | YES | ignore | +| LTM Cells To Be Released List | O | | 9.3.1.291 | | YES | ignore | + +| Range bound | Explanation | +|-------------------|--------------------------------------------------------------------------------| +| maxnoofCellsinCHO | Maximum no. cells that can be prepared for a conditional mobility. Value is 8. | + +| Condition | Explanation | +|----------------|---------------------------------------------------------------------| +| ifRRcContainer | This IE shall be present if the RRc container IE is present. | + +## 9.2.2.6 UE CONTEXT RELEASE COMPLETE + +This message is sent by the gNB-DU to confirm the release of the UE-associated logical F1 connection or candidate cells in conditional handover or conditional PSCell addition or conditional PSCell change or subsequent CPAC. + +Direction: gNB-DU → gNB-CU + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| Recommended SSBs for Paging List | O | | 9.3.1.297 | | YES | ignore | + +### 9.2.2.7 UE CONTEXT MODIFICATION REQUEST + +This message is sent by the gNB-CU to provide UE Context information changes to the gNB-DU. + +Direction: gNB-CU → gNB-DU + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| SpCell ID | O | | NR CGI
9.3.1.12 | Special Cell as defined in TS 38.321 [16]. For handover case, this IE is considered as target cell. | YES | ignore | +| ServCellIndex | O | | INTEGER
(0..31, ...) | | YES | reject | +| SpCell UL Configured | O | | Cell UL Configured
9.3.1.33 | | YES | ignore | +| DRX Cycle | O | | DRX Cycle
9.3.1.24 | | YES | ignore | +| CU to DU RRC Information | O | | 9.3.1.25 | | YES | reject | +| Transmission Action Indicator | O | | 9.3.1.11 | | YES | ignore | +| Resource Coordination Transfer Container | O | | OCTET STRING | Includes the MeNB Resource Coordination Information IE as defined in subclause 9.2.116 of TS 36.423 [9] for EN-DC case or MR-DC Resource Coordination Information IE as defined in TS 38.423 [28] for NGEN-DC and NE-DC cases. | YES | ignore | +| RRc Reconfiguration Complete Indicator | O | | 9.3.1.30 | | YES | ignore | +| RRc-Container | O | | 9.3.1.6 | Includes the DL-DCCH-Message message as defined in subclause 6.2 of TS 38.331 [8], encapsulated in a PDCP PDU. | YES | reject | +| SCell To Be Setup List | | 0..1 | | | YES | ignore | +| >SCell to Be Setup Item IEs | | 1..
| | | EACH | ignore | +| >>SCell ID | M | | NR CGI | SCell Identifier in | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------------------------|-------------------------------|-----------------------------------------------------------------------------------|-------------|----------------------| +| | | | 9.3.1.12 | gNB | | | +| >>SCellIndex | M | | INTEGER (1..31) | | - | | +| >>SCell UL Configured | O | | Cell UL Configured 9.3.1.33 | | - | | +| >>servingCellMO | O | | INTEGER (1..64) | | YES | ignore | +| SCell To Be Removed List | | 0..1 | | | YES | ignore | +| >SCell to Be Removed Item IEs | | 1 .. | | | EACH | ignore | +| >>SCell ID | M | | NR CGI 9.3.1.12 | SCell Identifier in gNB | - | | +| SRB to Be Setup List | | 0..1 | | | YES | reject | +| >SRB to Be Setup Item IEs | | 1.. | | | EACH | reject | +| >>SRB ID | M | | 9.3.1.7 | | - | | +| >>Duplication Indication | O | | ENUMERATED (true, ..., false) | This IE is ignored if the Additional Duplication Indication IE is present. | - | | +| >>Additional Duplication Indication | O | | ENUMERATED (three, four, ...) | | YES | ignore | +| >>SRB Mapping Info | O | | Uu RLC Channel ID 9.3.1.266 | This IE contains the mapped Uu Relay RLC CH ID for the SRB | YES | ignore | +| >>SDT Indicator Setup | O | | ENUMERATED (true, ...) | Indicates SDT SRB. | YES | reject | +| DRB to Be Setup List | | 0..1 | | | YES | reject | +| >DRB to Be Setup Item IEs | | 1 .. | | | EACH | reject | +| >>DRB ID | M | | 9.3.1.8 | | - | | +| >>CHOICE QoS Information | M | | | | - | | +| >>>E-UTRAN QoS | | | | | | | +| >>>>E-UTRAN QoS | M | | 9.3.1.19 | Shall be used for EN-DC case to convey E-RAB Level QoS Parameters | | | +| >>>DRB Information | | | | | | | +| >>>>DRB Information | | 1 | | Shall be used for NG-RAN cases | YES | ignore | +| >>>>>DRB QoS | M | | 9.3.1.45 | | - | | +| >>>>>S-NSSAI | M | | 9.3.1.38 | | - | | +| >>>>>Notification Control | O | | 9.3.1.56 | | - | | +| >>>>>Flows Mapped to DRB Item | | 1 .. | | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------------------|----------|------------------------------------|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | > | | | | | +| >>>>>>QoS Flow Identifier | M | | 9.3.1.63 | | - | | +| >>>>>>QoS Flow Level QoS Parameters | M | | 9.3.1.45 | | - | | +| >>>>>>QoS Flow Mapping Indication | O | | 9.3.1.72 | | YES | ignore | +| >>>>>>TSC Traffic Characteristics | O | | 9.3.1.141 | Traffic pattern information associated with the QFI. Details in TS 23.501 [21]. | YES | ignore | +| >>>>ECN Marking or Congestion Information Reporting Request | O | | 9.3.1.321 | | YES | ignore | +| >>UL UP TNL Information to be setup List | | 1 | | | - | | +| >>>UL UP TNL Information to Be Setup Item IEs | | 1 .. | | | - | | +| >>>>UL UP TNL Information | M | | UP Transport Layer Information 9.3.2.1 | gNB-CU endpoint of the F1 transport bearer. For delivery of UL PDUs. | - | | +| >>>>BH Information | O | | 9.3.1.114 | | YES | ignore | +| >>>>DRB Mapping Info | O | | Uu RLC Channel ID 9.3.1.266 | This IE contains the mapped Uu Relay RLC CH ID of the DL tunnel corresponding to such UL tunnel | YES | ignore | +| >>RLC Mode | M | | 9.3.1.27 | | - | | +| >>UL Configuration | O | | UL Configuration 9.3.1.31 | Information about UL usage in gNB-DU. | - | | +| >>Duplication Activation | O | | 9.3.1.36 | Information on the initial state of CA based UL PDCP duplication. This IE is ignored if the RLC Duplication Information IE is present. | - | | +| >>DC Based Duplication Configured | O | | ENUMERATED (true, ..., false) | Indication on whether DC based PDCP duplication is configured or not. If included, it | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------|----------|--------------------------------------------|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | should be set to true. | | | +| >>DC Based Duplication Activation | O | | Duplication Activation 9.3.1.36 | Information on the initial state of DC based UL PDCP duplication. This IE is ignored if the RLC Duplication Information IE is present. | YES | reject | +| >>DL PDCP SN length | O | | ENUMERATED (12bits, 18bits, ...) | | YES | ignore | +| >>UL PDCP SN length | O | | ENUMERATED (12bits, 18bits, ...) | | YES | ignore | +| >>Additional PDCP Duplication TNL List | | 0..1 | | | YES | ignore | +| >>>Additional PDCP Duplication TNL Items | | 1 .. | | | EACH | ignore | +| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information 9.3.2.1 | gNB-CU endpoint of the F1 transport bearer. For delivery of UL PDUs. | - | | +| >>>>BH Information | O | | 9.3.1.114 | | YES | ignore | +| >>RLC Duplication Information | O | | 9.3.1.146 | | YES | ignore | +| >>SDT Indicator Setup | O | | ENUMERATED (true, ...) | Indicates SDT DRB. | YES | reject | +| DRB to Be Modified List | | 0..1 | | | YES | reject | +| >DRB to Be Modified Item IEs | | 1 .. | | | EACH | reject | +| >>DRB ID | M | | 9.3.1.8 | | - | | +| >>CHOICE QoS Information | O | | | | - | | +| >>>E-UTRAN QoS | | | | | | | +| >>>>E-UTRAN QoS | M | | 9.3.1.19 | Used for EN-DC case to convey E-RAB Level QoS Parameters | - | | +| >>>DRB Information | | | | | | | +| >>>>DRB Information | | 1 | | Used for NG-RAN cases | YES | ignore | +| >>>>>DRB QoS | M | | 9.3.1.45 | | - | | +| >>>>>S-NSSAI | M | | 9.3.1.38 | | - | | +| >>>>>Notification | O | | 9.3.1.56 | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------------------|----------|------------------------------------|----------------------------------------|--------------------------------------------------------------------------------------|-------------|----------------------| +| Control | | | | | | | +| >>>>>Flows Mapped to DRB Item | | 1 .. | | | - | | +| >>>>>QoS Flow Identifier | M | | 9.3.1.63 | | - | | +| >>>>>QoS Flow Level QoS Parameters | M | | 9.3.1.45 | | - | | +| >>>>>QoS Flow Mapping Indication | O | | 9.3.1.72 | | YES | ignore | +| >>>>>TSC Traffic Characteristics | O | | 9.3.1.141 | Traffic pattern information associated with the QFI. Details in TS 23.501 [21]. | YES | ignore | +| >>>>ECN Marking or Congestion Information Reporting Request | O | | 9.3.1.321 | | YES | ignore | +| >>UL UP TNL Information to be setup List | | 1 | | | - | | +| >>>UL UP TNL Information to Be Setup Item IEs | | 1 .. | | | - | | +| >>>>UL UP TNL Information | M | | UP Transport Layer Information 9.3.2.1 | gNB-CU endpoint of the F1 transport bearer. For delivery of UL PDUs. | - | | +| >>>>BH Information | O | | 9.3.1.114 | | YES | ignore | +| >>>>DRB Mapping Info | O | | Uu RLC Channel ID 9.3.1.266 | | YES | ignore | +| >>UL Configuration | O | | UL Configuration 9.3.1.31 | Information about UL usage in gNB-DU. | - | | +| >>DL PDCP SN length | O | | ENUMERATED (12bits, 18bits, ..) | | YES | ignore | +| >>UL PDCP SN length | O | | ENUMERATED (12bits, 18bits, ...) | | YES | ignore | +| >>Bearer Type Change | O | | ENUMERATED (true, ...) | | YES | ignore | +| >>RLC Mode | O | | 9.3.1.27 | | YES | ignore | +| >>Duplication Activation | O | | 9.3.1.36 | Information on the initial state of CA based UL PDCP duplication. This IE is ignored | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------|----------|----------------------------------------------|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | if the RLC Duplication Information IE is present. | | | +| >>DC Based Duplication Configured | O | | ENUMERATED (true, ..., false) | Indication on whether DC based PDCP duplication is configured or not. | YES | reject | +| >>DC Based Duplication Activation | O | | 9.3.1.36 | Information on the initial state of DC based UL PDCP duplication. This IE is ignored if the RLC Duplication Information IE is present. | YES | reject | +| >>Additional PDCP Duplication TNL List | | 0..1 | | | YES | ignore | +| >>>Additional PDCP Duplication TNL Items | | 1 .. | | | EACH | ignore | +| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information 9.3.2.1 | gNB-CU endpoint of the F1 transport bearer. For delivery of UL PDUs. | - | | +| >>>>BH Information | O | | 9.3.1.114 | | YES | ignore | +| >>RLC Duplication Information | O | | 9.3.1.146 | | YES | ignore | +| >>Transmission Stop Indicator | O | | 9.3.1.209 | | YES | ignore | +| >>SDT Indicator Modify | O | | ENUMERATED (true, false, ...) | Indicates SDT DRB or not. | YES | reject | +| SRB To Be Released List | | 0..1 | | | YES | reject | +| >SRB To Be Released Item IEs | | 1.. | | | EACH | reject | +| >>SRB ID | M | | 9.3.1.7 | | | | +| DRB to Be Released List | | 0..1 | | | YES | reject | +| >DRB to Be Released Item IEs | | 1 .. | | | EACH | reject | +| >>DRB ID | M | | 9.3.1.8 | | - | | +| Inactivity Monitoring Request | O | | ENUMERATED (true, ...) | | YES | reject | +| RAT-Frequency Priority Information | O | | 9.3.1.34 | | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|------------------------------|-------------------------------|-----------------------------------------------------------------------------------------------|-------------|----------------------| +| DRX configuration indicator | O | | ENUMERATED (release,...) | | YES | ignore | +| RLC Failure Indication | O | | 9.3.1.66 | | YES | ignore | +| Uplink TxDirectCurrentList Information | O | | 9.3.1.67 | | YES | ignore | +| gNB-DU Configuration Query | O | | ENUMERATED (true, ...) | Used to request the gNB-DU to provide its configuration. | YES | reject | +| gNB-DU UE Aggregate Maximum Bit Rate Uplink | O | | Bit Rate 9.3.1.22 | The gNB-DU UE Aggregate Maximum Bit Rate Uplink is to be enforced by the gNB-DU. | YES | ignore | +| Execute Duplication | O | | ENUMERATED (true, ...) | This IE may be sent only if duplication has been configured for the UE. | YES | ignore | +| RRC Delivery Status Request | O | | ENUMERATED (true, ...) | Indicates whether RRC DELIVERY REPORT procedure is requested for the RRC message. | YES | ignore | +| Resource Coordination Transfer Information | O | | 9.3.1.73 | | YES | ignore | +| servingCellMO | O | | INTEGER (1..64, ...) | | YES | ignore | +| Need for Gap | O | | ENUMERATED (true, ...) | Indicate gap for SeNB configured measurement is requested. It only applied to NE DC scenario. | Yes | ignore | +| Full Configuration | O | | ENUMERATED (full, ...) | | YES | reject | +| Additional RRM Policy Index | O | | 9.3.1.90 | | YES | ignore | +| Lower Layer Presence Status Change | O | | 9.3.1.94 | | Yes | ignore | +| BH RLC Channel to be Setup List | | 0..1 | | | YES | reject | +| >BH RLC Channel to be Setup Item IEs | | 1 .. | | | EACH | reject | +| >>BH RLC CH ID | M | | 9.3.1.113 | | - | | +| >>CHOICE BH QoS information | M | | | | | | +| >>>BH RLC CH QoS | | | | | | | +| >>>>BH RLC CH QoS | M | | QoS Flow Level QoS Parameters | Shall be used for SA case. | | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|-------------------------------|----------------------------------------|-----------------------------------------------------|-------------|----------------------| +| | | | 9.3.1.145 | | | | +| >>>E-UTRAN BH RLC CH QoS | | | | | | | +| >>>>E-UTRAN BH RLC CH QoS | M | | E-UTRAN QoS 9.3.1.19 | Shall be used for EN-DC case. | | | +| >>>Control Plane Traffic Type | | | | | | | +| >>>>Control Plane Traffic Type | M | | 9.3.1.115 | | | | +| >>RLC Mode | M | | 9.3.1.27 | | - | | +| >>BAP Control PDU Channel | O | | ENUMERATED (true, ...) | | - | | +| >>Traffic Mapping Information | O | | 9.3.1.95 | | - | | +| BH RLC Channel to be Modified List | | 0..1 | | | YES | reject | +| > BH RLC Channel to be Modified Item IEs | | 1 .. | | | EACH | reject | +| >>BH RLC CH ID | M | | 9.3.1.113 | | - | | +| >>CHOICE BH QoS information | O | | | | | | +| >>>BH RLC CH QoS | | | | | | | +| >>>>BH RLC CH QoS | M | | QoS Flow Level QoS Parameters 9.3.1.45 | Shall be used for SA case. | - | | +| >>>E-UTRAN BH RLC CH QoS | | | | | | | +| >>>>E-UTRAN BH RLC CH QoS | M | | E-UTRAN QoS 9.3.1.19 | Shall be used for EN-DC case. | - | | +| >>>Control Plane Traffic Type | | | | | | | +| >>>>Control Plane Traffic Type | M | | 9.3.1.115 | | - | | +| >>RLC Mode | O | | 9.3.1.27 | | - | | +| >>BAP Control PDU Channel | O | | ENUMERATED (true, ...) | | - | | +| >>Traffic Mapping Information | O | | 9.3.1.95 | | - | | +| BH RLC Channel to be Released List | | 0..1 | | | YES | reject | +| > BH RLC Channel to be Released Item IEs | | 1 .. | | | EACH | reject | +| >>BH RLC CH ID | M | | 9.3.1.113 | | - | | +| NR V2X Services Authorized | O | | 9.3.1.116 | | YES | ignore | +| LTE V2X Services Authorized | O | | 9.3.1.117 | | YES | ignore | +| NR UE Sidelink Aggregate Maximum Bit Rate | O | | 9.3.1.119 | This IE applies only if the UE is authorized for NR | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------|----------|----------------------------|-------------------------------|--------------------------------------------------------------------|-------------|----------------------| +| | | | | V2X services. | | | +| LTE UE Sidelink Aggregate Maximum Bit Rate | O | | 9.3.1.118 | This IE applies only if the UE is authorized for LTE V2X services. | YES | ignore | +| PC5 Link Aggregate Bit Rate | O | | Bit Rate 9.3.1.22 | Only applies for non-GBR and unicast QoS Flows. | YES | ignore | +| SL DRB to Be Setup List | | 0..1 | | | YES | reject | +| > SL DRB to Be Setup Item IEs | | 1 .. | | | EACH | reject | +| >>SL DRB ID | M | | 9.3.1.120 | | - | | +| >> SL DRB Information | | 1 | | | YES | ignore | +| >>>SL DRB QoS | M | | PC5 QoS Parameters 9.3.1.122 | | - | | +| >>> Flows Mapped to SL DRB Item | | 1 .. | | | - | | +| >>>>PC5 QoS Flow Identifier | M | | 9.3.1.121 | | - | | +| >>RLC mode | O | | 9.3.1.27 | | - | | +| >>Duplication Indication | O | | ENUMERATED (true, ..., false) | If included, it should be set to true. | - | | +| SL DRB to Be Modified List | | 0..1 | | | YES | reject | +| > SL DRB to Be Modified Item IEs | | 1 .. | | | EACH | reject | +| >>SL DRB ID | M | | 9.3.1.120 | | - | | +| >> SL DRB Information | | 1 | | | YES | ignore | +| >>>SL DRB QoS | M | | PC5 QoS Parameters 9.3.1.122 | | - | | +| >>> Flows Mapped to SL DRB Item | | 1 .. | | | - | | +| >>>>PC5 QoS Flow Identifier | M | | 9.3.1.121 | | - | | +| >>RLC mode | O | | 9.3.1.27 | | - | | +| >>Duplication Indication | O | | ENUMERATED (true, ..., false) | | - | | +| SL DRB to Be Released List | | 0..1 | | | YES | reject | +| > SL DRB to Be Released Item IEs | | 1 .. | | | EACH | reject | +| >>SL DRB ID | M | | 9.3.1.120 | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------------|-------------------|-------------------------------------|-----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Conditional Intra-DU Mobility Information | O | | | | YES | reject | +| >CHO Trigger | M | | ENUMERATED (CHO-initiation, CHO-replace, CHO-cancel, ...) | | - | - | +| >Candidate Cells To Be Cancelled List | C-
ifCHOCancel | 0 ..
CellsinCH
O> | | | - | - | +| >>Target Cell ID | M | | NR CGI
9.3.1.12 | | - | - | +| >Estimated Arrival Probability | O | | INTEGER (1..100) | | YES | ignore | +| F1-C Transfer Path | O | | 9.3.1.207 | | YES | reject | +| SCG Indicator | O | | ENUMERATED (released,...) | This IE is used at the MN in NR-DC and NE-DC and it indicates the release of an SCG | YES | ignore | +| Uplink TxDirectCurrentTwoCarrierList Information | O | | 9.3.1.283 | | YES | ignore | +| IAB Conditional RRC Message Delivery Indication | O | | ENUMERATED (true, ...) | Indicates whether the RRC message within should be withheld. This IE is only applicable if the UE is an IAB-MT, and the gNB-DU is an IAB-DU. | YES | reject | +| F1-C Transfer Path NRDC | O | | 9.3.1.228 | This IE is only applicable if the UE is an IAB-MT. | YES | reject | +| MDT Polluted Measurement Indicator | O | | ENUMERATED (IDC,no-IDC, ...) | Indication on whether MDT Measurement affect (e.g. IDC) is undertaken or not. | YES | ignore | +| SCG Activation Request | O | | 9.3.1.233 | | YES | ignore | +| CG-SDT Query Indication | O | | ENUMERATED (true, ...) | | YES | ignore | +| 5G ProSe Authorized | O | | 9.3.1.268 | | YES | ignore | +| 5G ProSe UE PC5 Aggregate Maximum Bit Rate | O | | NR UE Sidelink Aggregate Maximum Bit Rate
9.3.1.119 | This IE applies only if the UE is authorized for 5G ProSe services. | YES | ignore | +| 5G ProSe PC5 Link Aggregate Bit Rate | O | | Bit Rate
9.3.1.22 | This IE applies only if the UE is authorized for 5G ProSe services, and only applies for non-GBR and unicast QoS Flows. | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------------|----------|------------------------------|----------------------------------------|-----------------------------------------------------------------------------------------------------|-------------|----------------------| +| Updated Remote UE Local ID | O | | Remote UE Local ID 9.3.1.267 | This IE indicates the updated Remote UE Local ID for the U2N Remote UE associated with the F1AP-IDs | YES | ignore | +| Uu RLC Channel to Be Setup List | | 0..1 | | | YES | reject | +| >Uu RLC Channel to be Setup Item IEs | | 1 .. | | | - | | +| >>Uu RLC Channel ID | M | | 9.3.1.266 | | - | | +| >>CHOICE Uu RLC Channel QoS Information | M | | | | - | | +| >>> Uu RLC Channel QoS | | | | | | | +| >>>>Uu RLC Channel QoS | M | | QoS Flow Level QoS Parameters 9.3.1.45 | | - | | +| >>> Uu Control Plane Traffic Type | | | | | | | +| >>>>Uu Control Plane Traffic Type | M | | ENUMERATED (SRB0, SRB1, SRB2, ...) | This IE indicates the type of SRB conveyed via the Uu Relay RLC Channel. | - | | +| >>RLC Mode | M | | 9.3.1.27 | | - | | +| Uu RLC Channel to Be Modified List | | 0..1 | | | YES | reject | +| >Uu RLC Channel to be Modified Item IEs | | 1 .. | | | - | | +| >>Uu RLC Channel ID | M | | 9.3.1.266 | | - | | +| >>CHOICE Uu RLC Channel QoS Information | O | | | | - | | +| >>> Uu RLC Channel QoS | | | | | | | +| >>>>Uu RLC Channel QoS | M | | QoS Flow Level QoS Parameters 9.3.1.45 | | - | | +| >>> Uu Control Plane Traffic Type | | | | | | | +| >>>>Uu Control Plane Traffic Type | M | | ENUMERATED (SRB0, SRB1, SRB2, ...) | This IE indicates the type of SRB conveyed via the Uu Relay RLC Channel. | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------|----------|-----------------------------------------|-------------------------------------------------|---------------------------------------------------------------------------|-------------|----------------------| +| >>RLC Mode | O | | 9.3.1.27 | | - | | +| Uu RLC Channel to Be Released List | | 0..1 | | | YES | reject | +| >Uu RLC Channel to Be Released Item IEs | | 1 ..
UuRLCCh
annels> | | | - | | +| >>Uu RLC channel ID | M | | 9.3.1.266 | | - | | +| PC5 RLC Channel to Be Setup List | | 0..1 | | | YES | reject | +| >PC5 RLC Channel to be Setup Item IEs | | 1 ..
PC5RLCC
hannels> | | | - | | +| >>PC5 RLC Channel ID | M | | 9.3.1.265 | | - | | +| >>Remote UE Local ID | O | | 9.3.1.267 | | - | | +| >>CHOICE PC5 RLC Channel QoS Information | M | | | | - | | +| >>>PC5 RLC Channel QoS | | | | | | | +| >>>>PC5 RLC Channel QoS | M | | QoS Flow Level
QoS
Parameters
9.3.1.45 | | - | | +| >>>PC5 Control Plane Traffic Type | | | | | | | +| >>>>PC5 Control Plane Traffic Type | M | | ENUMERATED
(SRB1, SRB2,
...) | This IE indicates the type of SRB conveyed via the PC5 Relay RLC Channel. | - | | +| >>RLC Mode | M | | 9.3.1.27 | | - | | +| PC5 RLC Channel to Be Modified List | | 0..1 | | | YES | reject | +| >PC5 RLC Channel to be Modified Item IEs | | 1 ..
PC5RLCC
hannels> | | | - | | +| >>PC5 RLC Channel ID | M | | 9.3.1.265 | | - | | +| >>Remote UE Local ID | O | | 9.3.1.267 | | - | | +| >>CHOICE PC5 RLC Channel QoS Information | O | | | | - | | +| >>>PC5 RLC Channel QoS | | | | | | | +| >>>>PC5 RLC Channel QoS | M | | QoS Flow Level
QoS
Parameters
9.3.1.45 | | - | | +| >>>PC5 Control Plane Traffic Type | | | | | | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------|----------|--------------------------------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>>>PC5 Control Plane Traffic Type | M | | ENUMERATED (SRB1, SRB2, ...) | This IE indicate the type of SRB conveyed via the PC5 Relay RLC Channel. | - | | +| >>RLC Mode | O | | 9.3.1.27 | | - | | +| PC5 RLC Channel to Be Released List | | 0..1 | | | YES | reject | +| >PC5 RLC Channel to be Released Item IEs | | 1 .. | | | - | | +| >>PC5 RLC Channel ID | M | | 9.3.1.265 | | - | | +| >>Remote UE Local ID | O | | 9.3.1.267 | | - | | +| Path Switch Configuration | O | | 9.3.1.263 | | YES | ignore | +| gNB-DU UE Slice Maximum Bit Rate List | O | | 9.3.1.271 | The Slice Maximum Bit Rate List is the maximum aggregate UL bit rate per slice, to be enforced by the gNB-DU, if feasible. | YES | ignore | +| Multicast MBS Session Setup List | O | | Multicast MBS Session List 9.3.1.272 | The list of MBS Session ID that UE has joined. | YES | reject | +| Multicast MBS Session Remove List | O | | Multicast MBS Session List 9.3.1.272 | The list of MBS Session ID that UE has left. | YES | reject | +| UE Multicast MRB to Be Setup at Modify List | | 0..1 | | | YES | reject | +| >UE Multicast MRB to Be Setup at Modify Item IEs | | 1 .. | | | EACH | reject | +| >>MRB ID | M | | 9.3.1.224 | MRB ID for the UE. | - | | +| >>MBS PTP Retransmission Tunnel Required | O | | 9.3.2.10 | | - | | +| >>MBS PTP Forwarding Tunnel Required Information | O | | MRB Progress Information 9.3.2.12 | | - | | +| UE Multicast MRB to Be Released List | | 0..1 | | | YES | reject | +| >UE Multicast MRB to Be Released Item IEs | | 1 .. | | | EACH | reject | +| >>MRB ID | M | | 9.3.1.224 | MRB ID for the UE. | - | | +| SL DRX Cycle List | | 0..1 | | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------------|----------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|-------------|----------------------| +| >SL DRX Cycle Item IEs | | 1 ..
SLdestinations > | | | EACH | ignore | +| >>RX UE ID | M | | BIT STRING
(SIZE(24)) | Indicates the destination L2 ID of RX UE associated to this UE. | - | | +| >>CHOICE SL DRX Information | M | | | | - | | +| >>>SL DRX Cycle | | | | | | | +| >>>>SL DRX Cycle Length | M | | ENUMERATED
(ms10, ms20, ms32, ms40, ms60, ms64, ms70, ms80, ms128, ms160, ms256, ms320, ms512, ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240, ...) | Indicates the desired SL DRX cycle for RX UE associated to this UE. | - | | +| >>>No SL DRX | | | | | - | | +| >>>>SL DRX configuration indicator | M | | ENUMERATED
(release,...) | | - | | +| Management Based MDT PLMN Modification List | O | | MDT PLMN Modification List
9.3.1.274 | | YES | ignore | +| SDT Bearer Configuration Query Indication | O | | ENUMERATED
(true, ...) | | YES | ignore | +| DAPS HO status | O | | ENUMERATED
(initiation, ...) | This IE is used if DAPS HO is initiated. | YES | ignore | +| ServingCellMO List | | 0..1 | | For NCD-SSBs | YES | ignore | +| >ServingCellMO Item IEs | | 1 ..
ServingCellMOs> | | | EACH | ignore | +| >>servingCellMO | M | | INTEGER
(1..64) | | - | | +| >>SSB frequency | M | | INTEGER
(0..3279165) | ARFCN | - | | +| Uplink TxDirectCurrentMoreCarrierList Information | O | | 9.3.1.284 | | YES | ignore | +| CPAC MCG Information | | 0..1 | | This IE is used at the MN for MCG configuration as specified in TS 37.340 [7] for CPAC. | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------|----------|-------------------------|---------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >CPAC Trigger | M | | ENUMERATED (CPAC-preparation, CPAC-executed, ...) | | - | - | +| >PSCell ID | M | | NR CGI 9.3.1.12 | The PSCell corresponding to the included CG-Config IE at CPAC-preparation or the selected PSCell by the UE at CPAC-executed. | - | - | +| Network Controlled Repeater Authorized | O | | 9.3.1.288 | | YES | ignore | +| SDT Volume Threshold | O | | INTEGER(1..192000,...) | Unit: byte. | YES | ignore | +| LTM Information Modify | | 0..1 | | | YES | reject | +| >LTM Indicator | M | | ENUMERATED (true, ...) | | - | | +| >LTM Configuration ID | M | | INTEGER (1..8) | Corresponds to the LTM-CandidateId IE, as defined in TS 38.331 [8]. | - | | +| >Reference Configuration | O | | 9.3.1.292 | | - | | +| >CSI Resource Configuration | O | | OCTET STRING | Includes the Itm-CSI-ResourceConfigToAddModList IE as defined in TS 38.331 [8]. | - | | +| LTM Configuration ID Mapping List | O | | 9.3.1.294 | | YES | reject | +| Early Sync Information Request | | 0..1 | | | YES | ignore | +| >Request for RACH Configuration | O | | ENUMERATED (true, ...) | | - | | +| Early Sync Information List | | 0..1 | | | YES | ignore | +| >Early Sync Information Item IEs | | 1 .. | | | EACH | ignore | +| >>Cell ID | M | | NR CGI 9.3.1.12 | | - | | +| >>RACH Configuration | O | | OCTET STRING | Includes the EarlyUL-SyncConfig IE, as defined in TS 38.331 [8]. | | | +| >>TCI States Configurations List | O | | 9.3.1.293 | | | | +| LTM Cells To Be | O | | 9.3.1.291 | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------|-------------|----------------------| +| Released List | | | | | | | +| Path Addition Information | O | | 9.3.1.296 | | YES | ignore | +| NR A2X Services Authorized | O | | 9.3.1.323 | | YES | ignore | +| LTE A2X Services Authorized | O | | 9.3.1.324 | | YES | ignore | +| NR UE Sidelink Aggregate Maximum Bit Rate for A2X | O | | 9.3.1.119 | This IE applies only if the UE is authorized for NR A2X services. | YES | ignore | +| LTE UE Sidelink Aggregate Maximum Bit Rate for A2X | O | | 9.3.1.118 | This IE applies only if the UE is authorized for LTE A2X services. | YES | ignore | + +| Range bound | Explanation | +|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------| +| maxnoofSCells | Maximum no. of SCells allowed towards one UE, the maximum value is 32. | +| maxnoofServingCellMOs | Maximum number of ServingCellMOs for NCD-SSB per cell. Maximum value is 16 | +| maxnoofSRBs | Maximum no. of SRB allowed towards one UE, the maximum value is 8. | +| maxnoofDRBs | Maximum no. of DRB allowed towards one UE, the maximum value is 64. | +| maxnoofULUPTNLInformation | Maximum no. of UL UP TNL Information allowed towards one DRB, the maximum value is 2. | +| maxnoofQoSFlows | Maximum no. of flows allowed to be mapped to one DRB, the maximum value is 64. | +| maxnoofBHRLCChannels | Maximum no. of BH RLC channels allowed towards one IAB-node, the maximum value is 65536. | +| maxnoofSLDRBs | Maximum no. of SL DRB allowed for NR sidelink communication per UE, the maximum value is 512. | +| maxnoofPC5QoSFlows | Maximum no. of PC5 QoS flow allowed towards one UE for NR sidelink communication, the maximum value is 2048. | +| maxnoofAdditionalPDCPDuplicationTNL | Maximum no. of additional UP TNL Information allowed towards one DRB, the maximum value is 2. | +| maxnoofCellsinCHO | Maximum no. cells that can be prepared for a conditional mobility. Value is 8. | +| maxnoofUuRLCChannels | Maximum no. of Uu Relay RLC channels for L2 U2N relaying or L2 N3C relaying per Relay UE, the maximum value is 32. | +| maxnoofPC5RLCChannels | Maximum no. of PC5 Relay RLC channel allowed for L2 U2N relaying per Remote UE or Relay UE, the maximum value is 512. | +| maxnoofMRBsforUE | Maximum no. of multicast MRB allowed towards one UE, the maximum value is 64. | +| maxnoofSLdestinations | Maximum number of destination for NR sidelink communication, the maximum value is 32 | +| maxnoofLTMCells | Maximum no. of Cells configured for LTM allowed towards one UE, the maximum value is 8. | + +| Condition | Explanation | +|-------------|----------------------------------------------------------------------------------| +| ifCHOCancel | This IE may be present if the CHO Trigger IE is present and set to "CHO-cancel". | + +## 9.2.2.8 UE CONTEXT MODIFICATION RESPONSE + +This message is sent by the gNB-DU to confirm the modification of a UE context. + +Direction: gNB-DU → gNB-CU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| Resource Coordination Transfer Container | O | | OCTET STRING | Includes the SgNB Resource Coordination Information IE as defined in subclause 9.2.117 of TS 36.423 [9] for EN-DC case or MR-DC Resource Coordination Information IE as defined in TS 38.423 [28] for NGEN-DC and NE-DC cases. | YES | ignore | +| DU To CU RRC Information | O | | 9.3.1.26 | | YES | reject | +| DRB Setup List | | 0..1 | | The List of DRBs which are successfully established. | YES | ignore | +| >DRB Setup Item IEs | | 1 .. | | | EACH | ignore | +| >>DRB ID | M | | 9.3.1.8 | | - | | +| >>LCID | O | | 9.3.1.35 | LCID for the primary path or for the split secondary path for fallback to split bearer if PDCP duplication is applied. | - | | +| >>DL UP TNL Information to be setup List | | 1 | | | - | | +| >>>DL UP TNL Information to Be Setup Item IEs | | 1 .. | | | - | | +| >>>>DL UP TNL Information | M | | UP Transport Layer Information 9.3.2.1 | gNB-DU endpoint of the F1 transport bearer. For delivery of DL PDUs. | - | | +| >>Additional PDCP Duplication TNL List | | 0..1 | | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------------|----------|--------------------------------------------|------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>>Additional PDCP Duplication TNL Items | | 1 .. | | | EACH | ignore | +| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information 9.3.2.1 | gNB-DU endpoint of the F1 transport bearer. For delivery of DL PDUs. | - | | +| >>>>BH Information | O | | 9.3.1.114 | This IE is not used in this version of the specification. | YES | ignore | +| >>Current QoS Parameters Set Index | O | | Alternative QoS Parameters Set Index 9.3.1.123 | Index to the currently fulfilled alternative QoS parameters set. | YES | ignore | +| >>TSC Traffic Characteristics Feedback | O | | 9.3.1.302 | | YES | ignore | +| >>ECN Marking or Congestion Information Reporting Status | O | | 9.3.1.322 | | YES | ignore | +| DRB Modified List | | 0..1 | | The List of DRBs which are successfully modified. | YES | ignore | +| >DRB Modified Item IEs | | 1 .. | | | EACH | ignore | +| >>DRB ID | M | | 9.3.1.8 | | - | | +| >>LCID | O | | 9.3.1.35 | LCID for the primary path or for the split secondary path for fallback to split bearer if PDCP duplication is applied. | - | | +| >>DL UP TNL Information to be setup List | | 1 | | | - | | +| >>>DL UP TNL Information to Be Setup Item IEs | | 1 .. | | | - | | +| >>>>DL UP TNL Information | M | | UP Transport Layer Information 9.3.2.1 | gNB-DU endpoint of the F1 transport bearer. For delivery of DL PDUs. | - | | +| >>RLC Status | O | | 9.3.1.69 | Indicates the RLC has been re-established at the gNB-DU. | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------------|----------|--------------------------------------------|------------------------------------------------|----------------------------------------------------------------------|-------------|----------------------| +| >>Additional PDCP Duplication TNL List | | 0..1 | | | YES | ignore | +| >>>Additional PDCP Duplication TNL Items | | 1 .. | | | EACH | ignore | +| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information 9.3.2.1 | gNB-DU endpoint of the F1 transport bearer. For delivery of DL PDUs. | - | | +| >>>>BH Information | O | | 9.3.1.114 | This IE is not used in this version of the specification. | YES | ignore | +| >>Current QoS Parameters Set Index | O | | Alternative QoS Parameters Set Index 9.3.1.123 | Index to the currently fulfilled alternative QoS parameters set. | YES | ignore | +| >>TSC Traffic Characteristics Feedback | O | | 9.3.1.302 | | YES | ignore | +| >>ECN Marking or Congestion Information Reporting Status | O | | 9.3.1.322 | | YES | ignore | +| SRB Failed to be Setup List | | 0..1 | | The List of SRBs which are failed to be established. | YES | ignore | +| >SRB Failed to be Setup Item IEs | | 1 .. | | | EACH | ignore | +| >>SRB ID | M | | 9.3.1.7 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| DRB Failed to be Setup List | | 0..1 | | The List of DRBs which are failed to be setup. | YES | ignore | +| >DRB Failed to be Setup Item IEs | | 1 .. | | | EACH | ignore | +| >>DRB ID | M | | 9.3.1.8 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| SCell Failed To Setup List | | 0..1 | | | YES | ignore | +| >SCell Failed to Setup Item | | 1 .. | | | EACH | ignore | +| >>SCell ID | M | | NR CGI 9.3.1.12 | SCell Identifier in gNB | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| DRB Failed to be Modified List | | 0..1 | | The List of DRBs which are failed to be modified. | YES | ignore | +| >DRB Failed to be Modified Item IEs | | 1 .. | | | EACH | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------|----------|--------------------------------------------|---------------------------------|-----------------------------------------------------------------|-------------|----------------------| +| | | DRBs> | | | | | +| >>DRB ID | M | | 9.3.1.8 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| Inactivity Monitoring Response | O | | ENUMERATED (Not-supported, ...) | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| C-RNTI | O | | 9.3.1.32 | C-RNTI allocated at the gNB-DU | YES | ignore | +| Associated SCell List | O | | 9.3.1.77 | | YES | ignore | +| SRB Setup List | | 0..1 | | | YES | ignore | +| >SRB Setup Item | | 1 .. <maxnoof SRBs> | | | EACH | ignore | +| >>SRB ID | M | | 9.3.1.7 | | - | | +| >>LCID | M | | 9.3.1.35 | LCID for the primary path if PDCP duplication is applied | - | | +| SRB Modified List | | 0..1 | | | YES | ignore | +| >SRB Modified Item | | 1 .. <maxnoof SRBs> | | | EACH | ignore | +| >>SRB ID | M | | 9.3.1.7 | | - | | +| >>LCID | M | | 9.3.1.35 | LCID for the primary path if PDCP duplication is applied | - | | +| Full Configuration | O | | ENUMERATED (full, ...) | | YES | reject | +| BH RLC Channel Setup List | | 0..1 | | The list of BH RLC channels which are successfully established. | YES | ignore | +| >BH RLC Channel Setup Item | | 1 .. <maxnoof BHRLCCh annels> | | | EACH | ignore | +| >>BH RLC CH ID | M | | 9.3.1.113 | | - | | +| BH RLC Channel Failed to be Setup List | | 0..1 | | The list of BH RLC channels whose setup has failed. | YES | ignore | +| >BH RLC Channel Failed to be Setup Item | | 1 .. <maxnoof BHRLCCh annels> | | | EACH | ignore | +| >>BH RLC CH ID | M | | 9.3.1.113 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| BH RLC Channel Modified List | | 0..1 | | The list of BH RLC channels which are successfully modified. | YES | ignore | +| >BH RLC Channel Modified Item | | 1 .. <maxnoof BHRLCCh annels> | | | EACH | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------------|----------|----------------------------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>BH RLC CH ID | M | | 9.3.1.113 | | - | | +| BH RLC Channel Failed to be Modified List | | 0..1 | | The list of BH RLC channels whose modification has failed. | YES | ignore | +| >BH RLC Channel Failed to be Modified Item | | 1 ..
BHRLCCh
annels> | | | EACH | ignore | +| >>BH RLC CH ID | M | | 9.3.1.113 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| SL DRB Setup List | | 0..1 | | The List of SL DRBs which are successfully established. | YES | ignore | +| >SL DRB Setup Item IEs | | 1 ..
SLDRBs> | | | EACH | ignore | +| >>SL DRB ID | M | | 9.3.1.120 | | - | | +| SL DRB Modified List | | 0..1 | | The List of SL DRBs which are successfully modified. | YES | ignore | +| >SL DRB Modified Item IEs | | 1 ..
SLDRBs> | | | EACH | ignore | +| >>SL DRB ID | M | | 9.3.1.120 | | - | | +| SL DRB Failed To Setup List | | 0..1 | | The List of SL DRBs which are failed to be setup. | YES | ignore | +| >SL DRB Failed To Setup Item | | 1 ..
SLDRBs> | | | EACH | ignore | +| >>SL DRB ID | M | | 9.3.1.120 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| SL DRB Failed To be Modified List | | 0..1 | | The List of SL DRBs which are failed to be modified. | YES | ignore | +| >SL DRB Failed To be Modified Item | | 1 ..
SLDRBs> | | | EACH | ignore | +| >>SL DRB ID | M | | 9.3.1.120 | | - | | +| >>cause | O | | 9.3.1.2 | | - | | +| Requested Target Cell ID | O | | NR CGI
9.3.1.12 | Special Cell or PSCell ID in the CPAC MCG Information IE indicated in the UE CONTEXT MODIFICATION REQUEST message. | YES | reject | +| SCG Activation Status | O | | 9.3.1.234 | | YES | ignore | +| Uu RLC Channel Setup List | | 0..1 | | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------------|----------|----------------------------------|-----------------------|-----------------------|-------------|----------------------| +| >Uu RLC Channel Setup Item IEs | | 1 ..
| | | - | | +| >>Uu RLC Channel ID | M | | 9.3.1.266 | | | | +| Uu RLC Channel Failed to be Setup List | | 0..1 | | | YES | ignore | +| >Uu RLC Channel Failed to be Setup Item IEs | | 1 ..
| | | - | | +| >>Uu RLC Channel ID | M | | 9.3.1.266 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| Uu RLC Channel Modified List | | 0..1 | | | YES | ignore | +| >Uu RLC Channel Modified Item IEs | | 1 ..
| | | - | | +| >>Uu RLC Channel ID | M | | 9.3.1.266 | | - | | +| Uu RLC Channel Failed to be Modified List | | 0..1 | | | YES | ignore | +| >Uu RLC Channel Failed to be Modified Item IEs | | 1 ..
| | | - | | +| >>Uu RLC Channel ID | M | | 9.3.1.266 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| PC5 RLC Channel Setup List | | 0..1 | | | YES | ignore | +| >PC5 RLC Channel Setup Item IEs | | 1 ..
| | | - | | +| >>PC5 RLC Channel ID | M | | 9.3.1.265 | | - | | +| >>Remote UE Local ID | O | | 9.3.1.267 | | - | | +| PC5 RLC Channel Failed to be Setup List | | 0..1 | | | YES | ignore | +| >PC5 RLC Channel Failed to be Setup Item IEs | | 1 ..
| | | - | | +| >>PC5 RLC Channel ID | M | | 9.3.1.265 | | - | | +| >>Remote UE Local ID | O | | 9.3.1.267 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| PC5 RLC Channel Modified List | | 0..1 | | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------------------|----------|-----------------------------------|------------------------|---------------------------------------------------------------------------------------------|-------------|----------------------| +| >PC5 RLC Channel Modified Item IEs | | 1 ..
| | | - | | +| >>PC5 RLC Channel ID | M | | 9.3.1.265 | | - | | +| >>Remote UE Local ID | O | | 9.3.1.267 | | - | | +| PC5 RLC Channel Failed to be Modified List | | 0..1 | | | YES | ignore | +| >PC5 RLC Channel Failed to be Modified Item IEs | | 1 ..
| | | - | | +| >>PC5 RLC Channel ID | M | | 9.3.1.265 | | - | | +| >>Remote UE Local ID | O | | 9.3.1.267 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| SDT Bearer Configuration Info | O | | 9.3.1.277 | | YES | ignore | +| UE Multicast MRB Setup List | | 0..1 | | | YES | reject | +| >UE Multicast MRB Setup Item IEs | | 1 ..
| | | EACH | reject | +| >>MRB ID | M | | 9.3.1.224 | MRB ID for the UE. | - | | +| >>Multicast F1-U Context Reference CU | M | | 9.3.2.13 | | - | | +| ServingCellMO-encoded-in-CGC List | | 0..1 | | | YES | ignore | +| >ServingCellMO-encoded-in-CGC Item IEs | | 1 ..
| | The servingCellMO which has been encoded in CellGroupConfig IE. | - | | +| >>servingCellMO | M | | INTEGER (1..64) | | - | | +| >>BWP ID | M | | INTEGER (0..4) | | YES | ignore | +| Dedicated SI Delivery Indication | O | | ENUMERATED (true, ...) | | YES | ignore | +| Configured BWP List | | 0..1 | | This IE is present when the gNB-DU configures at least one BWP with NCD-SSB or without SSB. | YES | ignore | +| >Configured BWP Item IEs | | 1 ..
| | | EACH | ignore | +| >>BWP-Id | M | | INTEGER (0..4) | The IE is used to refer to one BWP. | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-------|----------------------------|---------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>BWP Location And Bandwidth | M | | INTEGER (0..37949) | The IE type range is the same as the locationAndBandwidth IE in BWP IE as specified in TS 38.331 [8]. | | | +| Early Sync Information | | 0..1 | | | YES | ignore | +| >TCI States Configurations List | M | | 9.3.1.293 | | - | | +| >RACH Configuration | O | | OCTET STRING | Includes the EarlyUL-SyncConfig IE, as defined in TS 38.331 [8]. | - | | +| LTM Configuration | | 0..1 | | | YES | ignore | +| >SSB Information Item | M | | | | - | | +| >>SSB Time/Frequency Configuration | M | | 9.3.1.203 | | - | | +| >>NR PCI | M | | INTEGER (0..1007) | | - | | +| >LTM Reference Configuration | O | | OCTET STRING | Includes the CellGroupConfig IE, as defined in TS 38.331 [8]. | - | | +| >LTM Complete Configuration Indicator | O | | ENUMERATED (complete, ...) | | - | | + +| Range bound | Explanation | +|-------------------------------------|------------------------------------------------------------------------------------------------------------------------| +| maxnoofSRBs | Maximum no. of SRB allowed towards one UE, the maximum value is 8. | +| maxnoofDRBs | Maximum no. of DRB allowed towards one UE, the maximum value is 64. | +| maxnoofDLUPTNLInformation | Maximum no. of DL UP TNL Information allowed towards one DRB, the maximum value is 2. | +| maxnoofSCells | Maximum no. of SCells allowed towards one UE, the maximum value is 32. | +| maxnoofBHRLCChannels | Maximum no. of BH RLC channels allowed towards one IAB-node, the maximum value is 65536. | +| maxnoofSLDRBs | Maximum no. of SL DRB allowed for NR sidelink communication per UE, the maximum value is 512. | +| maxnoofAdditionalPDCPDuplicationTNL | Maximum no. of additional UP TNL Information allowed towards one DRB, the maximum value is 2. | +| maxnoofUuRLCChannels | Maximum no. of Uu Relay RLC channels for L2 U2N relaying or L2 N3C relaying per Relay UE, the maximum value is 32. | +| maxnoofPC5RLCChannels | Maximum no. of PC5 Relay RLC channels allowed for L2 U2N relaying per Remote UE or Relay UE, the maximum value is 512. | +| maxNrofBWPs | Maximum number of BWPs per serving cell, the maximum value is 8. | +| maxnoofMRBsforUE | Maximum no. of multicast MRB allowed towards one UE, the maximum value is 32. | + +### 9.2.2.9 UE CONTEXT MODIFICATION FAILURE + +This message is sent by the gNB-DU to indicate a context modification failure. + +Direction: gNB-DU → gNB-CU + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP 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 | +| Requested Target Cell ID | O | | NR CGI
9.3.1.12 | Special Cell indicated in the UE CONTEXT MODIFICATION REQUEST message. | YES | reject | + +### 9.2.2.10 UE CONTEXT MODIFICATION REQUIRED + +This message is sent by the gNB-DU to request the modification of a UE context. + +Direction: gNB-DU → gNB-CU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| Resource Coordination Transfer Container | O | | OCTET STRING | Includes the SgNB Resource Coordination Information IE as defined in subclause 9.2.117 of TS 36.423 [9] for EN-DC case or MR-DC Resource Coordination Information IE as defined in TS 38.423 [28] for NGEN-DC and NE-DC cases. | YES | ignore | +| DU To CU RRC Information | O | | 9.3.1.26 | | YES | reject | +| DRB Required to Be Modified List | | 0..1 | | | YES | reject | +| >DRB Required to Be Modified Item IEs | | 1 .. | | | EACH | reject | +| >>DRB ID | M | | 9.3.1.8 | | - | | +| >>DL UP TNL Information to be setup List | | 0..1 | | | - | | +| >>>DL UP TNL | | 1 .. | | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------|----------|---------------------------------------------------------------|----------------------------------------|----------------------------------------------------------------------|-------------|----------------------| +| Information to Be Setup Item IEs | | DLUPTNL
Information> | | | | | +| >>>>DL UP TNL Information | M | | UP Transport Layer Information 9.3.2.1 | gNB-DU endpoint of the F1 transport bearer. For delivery of DL PDUs. | - | | +| >>RLC Status | O | | 9.3.1.69 | Indicates the RLC has been re-established at the gNB-DU. | YES | ignore | +| >>Additional PDCP Duplication TNL List | | 0..1 | | | YES | ignore | +| >>>Additional PDCP Duplication TNL Items | | 1 ..
Additional
PDCPDup
licationTN
L> | | | EACH | ignore | +| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information 9.3.2.1 | gNB-CU endpoint of the F1 transport bearer. For delivery of DL PDUs. | - | | +| >>>>BH Information | O | | 9.3.1.114 | This IE is not used in this version of the specification. | YES | ignore | +| SRB Required to be Released List | | 0..1 | | | YES | reject | +| >SRB Required to be Released List Item IEs | | 1 ..
SRBs> | | | EACH | reject | +| >>SRB ID | M | | 9.3.1.7 | | - | | +| DRB Required to be Released List | | 0..1 | | | YES | reject | +| >DRB Required to be Released List Item IEs | | 1 ..
DRBs> | | | EACH | reject | +| >>DRB ID | M | | 9.3.1.8 | | - | | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| BH RLC Channel Required to be Released List | | 0..1 | | | YES | reject | +| >BH RLC Channel Required to be Released Item IEs | | 1 ..
BHRLCCh
annels> | | | EACH | reject | +| >>BH RLC CH ID | M | | 9.3.1.113 | | - | | +| SL DRB Required to Be Modified List | | 0..1 | | | YES | reject | +| >SL DRB Required to Be Modified Item IEs | | 1 ..
SLDRBs> | | | EACH | reject | +| >>SL DRB ID | M | | 9.3.1.120 | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------------|----------|-----------------------------------------|-----------------------|-----------------------|-------------|----------------------| +| SL DRB Required to be Released List | | 0..1 | | | YES | reject | +| >SL DRB Required to be Release Item IEs | | 1 ..
SLDRBs> | | | EACH | reject | +| >>SL DRB ID | M | | 9.3.1.120 | | - | | +| Candidate Cells To Be Cancelled List | | 0 ..
CellsInCH
O> | | | YES | reject | +| >Target Cell ID | M | | NR CGI
9.3.1.12 | | - | - | +| Uu RLC Channel Required to be Modified List | | 0..1 | | | YES | reject | +| >Uu RLC Channel Required to be Modified Item IEs | | 1 ..
UuRLCCh
annels> | | | - | | +| >>Uu RLC Channel ID | M | | 9.3.1.266 | | - | | +| Uu RLC Channel Required to be Released List | | 0..1 | | | YES | reject | +| >Uu RLC Channel Required to be Released Item IEs | | 1 ..
UuRLCCh
annels> | | | - | | +| >>Uu RLC Channel ID | M | | 9.3.1.266 | | - | | +| PC5 RLC Channel Required to be Modified List | | 0..1 | | | YES | reject | +| >PC5 RLC Channel Required to be Modified Item IEs | | 1 ..
PC5RLCC
hannels> | | | - | | +| >>PC5 RLC Channel ID | M | | 9.3.1.265 | | - | | +| >>Remote UE Local ID | O | | 9.3.1.267 | | - | | +| PC5 RLC Channel Required to be Released List | | 0..1 | | | YES | reject | +| >PC5 RLC Channel Required to be Released Item IEs | | 1 ..
PC5RLCC
hannels> | | | - | | +| >>PC5 RLC Channel ID | M | | 9.3.1.265 | | - | | +| >>Remote UE Local ID | O | | 9.3.1.267 | | - | | +| UE Multicast MRB Required to Be Modified List | | 0..1 | | | YES | reject | +| >UE Multicast MRB Required to Be Modified Item IEs | | 1 ..
MRBsforU
E> | | | EACH | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------------------------|---------------------------|-----------------------------------|------------------------------------|-----------------------|-------------|----------------------| +| >>MRB ID | M | | 9.3.1.224 | MRB ID for the UE. | - | | +| >>MRB type reconfiguration | O | | ENUMERATED (true, ...) | | - | | +| >>MRB Reconfigured RLC mode | C-
ifMRBTyp
eReconf | | MRB RLC Configuration
9.3.1.275 | | - | | +| >>Multicast F1-U Context Reference CU | O | | 9.3.2.13 | | YES | reject | +| UE Multicast MRB Required to Be Released List | | 0..1 | | | YES | reject | +| >UE Multicast MRB Required to Be Released Item IEs | | 1..
MRBsforU
E> | | | EACH | reject | +| >>MRB ID | M | | 9.3.1.224 | MRB ID for the UE. | - | | +| LTM Cells To Be Released List | O | | 9.3.1.291 | | YES | ignore | + +| Range bound | Explanation | +|-------------------------------------|------------------------------------------------------------------------------------------------------------------------| +| maxnoofSRBs | Maximum no. of SRB allowed towards one UE, the maximum value is 8. | +| maxnoofDRBs | Maximum no. of DRB allowed towards one UE, the maximum value is 64. | +| maxnoofDLUPTNLInformation | Maximum no. of DL UP TNL Information allowed towards one DRB, the maximum value is 2. | +| maxnoofBHRLCChannels | Maximum no. of BH RLC channels allowed towards one IAB-node, the maximum value is 65536. | +| maxnoofSLDRBs | Maximum no. of SL DRB allowed for NR sidelink communication per UE, the maximum value is 512. | +| maxnoofAdditionalPDCPDuplicationTNL | Maximum no. of additional UP TNL Information allowed towards one DRB, the maximum value is 2. | +| maxnoofCellsInCHO | Maximum no. cells that can be prepared for a conditional mobility. Value is 8. | +| maxnoofUuRLCChannels | Maximum no. of Uu Relay RLC channels for L2 U2N relaying or L2 N3C relaying per Relay UE, the maximum value is 32. | +| maxnoofPC5RLCChannels | Maximum no. of PC5 Relay RLC channels allowed for L2 U2N relaying per Remote UE or Relay UE, the maximum value is 512. | +| maxnoofMRBsforUE | Maximum no. of multicast MRB allowed towards one UE, the maximum value is 32. | + +| Condition | Explanation | +|-----------------|-------------------------------------------------------------------------| +| ifMRBTypeReconf | This IE shall be present if the MRB Type Reconfiguration IE is present. | + +## 9.2.2.11 UE CONTEXT MODIFICATION CONFIRM + +This message is sent by the gNB-CU to inform the gNB-DU the successful modification. + +Direction: gNB-CU → gNB-DU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| Resource Coordination Transfer Container | O | | OCTET STRING | Includes the MeNB Resource Coordination Information IE as defined in subclause 9.2.116 of TS 36.423 [9] for EN-DC case or MR-DC Resource Coordination Information IE as defined in TS 38.423 [28] for NGEN-DC and NE-DC cases. | YES | ignore | +| DRB Modified List | | 0..1 | | The List of DRBs which are successfully modified. | YES | ignore | +| >DRB Modified Item IEs | | 1 .. | | | EACH | ignore | +| >>DRB ID | M | | 9.3.1.8 | | - | | +| >>UL UP TNL Information to be setup List | | 1 | | | - | | +| >>>UL UP TNL Information to Be Setup Item IEs | | 1 .. | | | - | | +| >>>>UL UP TNL Information | M | | UP Transport Layer Information 9.3.2.1 | gNB-CU endpoint of the F1 transport bearer. For delivery of UL PDUs. | - | | +| >>>>BH Information | O | | 9.3.1.114 | | YES | ignore | +| >>>>DRB Mapping Info | O | | Uu RLC Channel ID 9.3.1.266 | This IE is not used in this version of the specification. | YES | ignore | +| >>Additional PDCP Duplication TNL List | | 0..1 | | | YES | ignore | +| >>>Additional PDCP Duplication TNL Items | | 1 .. | | | EACH | ignore | +| >>>>Additional PDCP Duplication UP TNL Information | M | | UP Transport Layer Information 9.3.2.1 | gNB-DU endpoint of the F1 transport bearer. For delivery of UL | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------------|----------|-------------------------------|------------------------|-----------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | PDUs. | | | +| >>>>BH Information | O | | 9.3.1.114 | | YES | ignore | +| RRC-Container | O | | 9.3.1.6 | Includes the DL-DCCH-Message message as defined in subclause 6.2 of TS 38.331 [8], encapsulated in a PDCP PDU. | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| Execute Duplication | O | | ENUMERATED (true, ...) | This IE may be sent only if duplication has been configured for the UE. | YES | ignore | +| Resource Coordination Transfer Information | O | | 9.3.1.73 | | YES | ignore | +| SL DRB Modified List | | 0..1 | | | YES | reject | +| >SL DRB Modified Item IEs | | 1 .. | | | EACH | reject | +| >>SL DRB ID | M | | 9.3.1.120 | | - | | +| Uu RLC Channel Modified List | | 0..1 | | | YES | reject | +| >Uu RLC Channel Modified Item IEs | | 1 .. | | | - | | +| >>Uu RLC Channel ID | M | | 9.3.1.266 | | - | | +| PC5 RLC Channel Modified List | | 0..1 | | | YES | reject | +| >PC5 RLC Channel Modified Item IEs | | 1 .. | | | - | - | +| >>PC5 RLC Channel ID | M | | 9.3.1.265 | | - | | +| >>Remote UE Local ID | O | | 9.3.1.267 | | - | | +| UE Multicast MRB Confirmed to Be Modified List | | 0..1 | | | YES | reject | +| >UE Multicast MRB Confirmed to Be Modified Item IEs | | 1 .. | | | EACH | reject | +| >>MRB ID | M | | 9.3.1.224 | MRB ID for the UE. | - | | +| >>MBS PTP Retransmission Tunnel Required | O | | 9.3.2.10 | | - | | + +| Range bound | Explanation | +|-------------|-------------| +|-------------|-------------| + +| | | +|-------------------------------------|------------------------------------------------------------------------------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRB allowed towards one UE, the maximum value is 64. | +| maxnoofULUPTNLInformation | Maximum no. of UL UP TNL Information allowed towards one DRB, the maximum value is 2. | +| maxnoofSLDRBs | Maximum no. of SL DRB allowed for NR sidelink communication per UE, the maximum value is 512. | +| maxnoofAdditionalPDCPDuplicationTNL | Maximum no. of additional UP TNL Information allowed towards one DRB, the maximum value is 2. | +| maxnoofUuRLCChannels | Maximum no. of Uu Relay RLC channels for L2 U2N relaying or L2 N3C relaying per Relay UE, the maximum value is 32. | +| maxnoofPC5RLCChannels | Maximum no. of PC5 Relay RLC channels allowed for L2 U2N relaying per Remote UE or Relay UE, the maximum value is 512. | + +### 9.2.2.11A UE CONTEXT MODIFICATION REFUSE + +This message is sent by the gNB-CU to indicate the UE context modification was unsuccessful. + +Direction: gNB-CU → gNB-DU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP 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.12 UE INACTIVITY NOTIFICATION + +This message is sent by the gNB-DU to provide information about the UE activity to the gNB-CU. + +Direction: gNB-DU → gNB-CU + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| DRB Activity List | | 1 | | | YES | reject | +| >DRB Activity Item | | 1 .. | | | EACH | reject | +| >>DRB ID | M | | 9.3.1.8 | | - | | +| >>DRB Activity | O | | ENUMERATED (Active, Not active) | | - | | +| SDT Termination Request | O | | ENUMERATED (radio link problem, normal, ..., SDT Volume Threshold Crossed) | Indicate the reason of request for termination of the ongoing SDT. | YES | ignore | + +| Range bound | Explanation | +|-------------|-------------| +|-------------|-------------| + +| | | +|-------------|---------------------------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRB allowed towards one UE, the maximum value is 64. | +|-------------|---------------------------------------------------------------------| + +### 9.2.2.13 NOTIFY + +This message is sent by the gNB-DU to notify the gNB-CU that the QoS for already established DRBs associated with notification control is not fulfilled any longer or it is fulfilled again. + +Direction: gNB-DU → gNB-CU + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| DRB Notify List | | 1 | | | YES | reject | +| >DRB Notify Item IEs | | <1 .. maxnoofDRBs> | | | EACH | reject | +| >>DRB ID | M | | 9.3.1.8 | | - | | +| >>Notification Cause | M | | ENUMERATED (Fulfilled, Not-Fulfilled, ...) | | - | | +| >>Current QoS Parameters Set Index | O | | Alternative QoS Parameters set Notify Index 9.3.1.124 | Index to the currently fulfilled alternative QoS parameters set. Value 0 indicates that NG-RAN cannot even fulfil the lowest alternative parameter set. | YES | ignore | +| >>TSC Traffic Characteristics Feedback | O | | 9.3.1.302 | | YES | ignore | + +| Range bound | Explanation | +|-------------|---------------------------------------------------------------------| +| maxnoofDRBs | Maximum no. of DRB allowed towards one UE, the maximum value is 64. | + +### 9.2.2.14 ACCESS SUCCESS + +This message is sent by the gNB-DU to inform the gNB-CU of which cell the UE has successfully accessed during conditional handover or conditional PSCell addition or conditional PSCell change or LTM or subsequent CPAC. + +Direction: gNB-DU → gNB-CU + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| NR CGI | M | | 9.3.1.12 | | YES | reject | + +### 9.2.2.15 DU-CU CELL SWITCH NOTIFICATION + +This message is sent by the gNB-DU to inform the gNB-CU about the initiation of the cell switch command to the UE. + +Direction: gNB-DU → gNB-CU + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| Cell ID | M | | NR CGI
9.3.1.12 | | YES | reject | +| LTM Cell Switch Information | | 0..1 | | | YES | ignore | +| >TCI State ID | M | | INTEGER
(0..127) | Corresponds to the CandidateTCI-StatesId IE as defined in TS 38.331 [8]. | - | | + +### 9.2.2.16 CU-DU CELL SWITCH NOTIFICATION + +This message is sent by the gNB-CU to inform the gNB-DU about the initiation of the cell switch command to the UE. + +Direction: gNB-CU → gNB-DU + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| Cell ID | M | | NR CGI
9.3.1.12 | | YES | reject | +| LTM Cell Switch Information | | 0..1 | | | YES | ignore | +| >TCI State ID | M | | INTEGER
(0..127) | Corresponds to the CandidateTCI-StatesId IE as defined in TS 38.331 [8]. | - | | + +## 9.2.3 RRC Message Transfer messages + +### 9.2.3.1 INITIAL UL RRC MESSAGE TRANSFER + +This message is sent by the gNB-DU to transfer the initial layer 3 message to the gNB-CU over the F1 interface. + +Direction: gNB-DU → gNB-CU + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| NR CGI | M | | 9.3.1.12 | NG-RAN Cell | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | Global Identifier (NR CGI) | | | +| C-RNTI | M | | 9.3.1.32 | C-RNTI allocated at the gNB-DU | YES | reject | +| RRC-Container | M | | 9.3.1.6 | Includes the UL-CCCH-Message message or UL-CCCH1-Message message as defined in subclause 6.2 of TS 38.331 [8]. | YES | reject | +| DU to CU RRC Container | O | | OCTET STRING | Includes the CellGroupConfig IE as defined in subclause 6.3.2 in TS 38.331 [8]. Required at least to carry SRB1 configuration. The ReconfigurationWithSync field is not included in the CellGroupConfig IE. | YES | reject | +| SUL Access Indication | O | | ENUMERATED (true, ...) | | YES | ignore | +| Transaction ID | M | | 9.3.1.23 | | YES | ignore | +| RAN UE ID | O | | OCTET STRING (SIZE (8)) | | YES | ignore | +| RRC-Container-RRCSsetupComplete | O | | 9.3.1.6 | Includes the UL-DCCH-Message message including the RRCSsetupComplete message, as defined in subclause 6.2 of TS 38.331 [8]. | YES | ignore | +| NR RedCap UE Indication | O | | ENUMERATED (true, ...) | | YES | ignore | +| SDT Information | O | | 9.3.1.262 | | YES | ignore | +| Sidelink Relay Configuration | O | | 9.3.1.264 | | YES | ignore | +| NR eRedCap UE Indication | O | | ENUMERATED (true, ...) | | YES | ignore | + +### 9.2.3.2 DL RRC MESSAGE TRANSFER + +This message is sent by the gNB-CU to transfer the layer 3 message to the gNB-DU over the F1 interface. + +Direction: gNB-CU →gNB-DU + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| old gNB-DU UE F1AP ID | O | | 9.3.1.5 | | YES | reject | +| SRB ID | M | | 9.3.1.7 | | YES | reject | +| Execute Duplication | O | | ENUMERATED (true, ...) | | YES | ignore | +| RRC-Container | M | | 9.3.1.6 | Includes the DL-DCCH-Message message as defined in subclause 6.2 of TS 38.331 [8] encapsulated in a PDCP PDU, or the DL-CCCH-Message message as defined in subclause 6.2 of TS 38.331 [8]. | YES | reject | +| RAT-Frequency Priority Information | O | | 9.3.1.34 | | YES | reject | +| RRC Delivery Status Request | O | | ENUMERATED (true, ...) | Indicates whether RRC DELIVERY REPORT procedure is requested for the RRC message. | YES | ignore | +| UE Context not retrievable | O | | ENUMERATED (true, ...) | | YES | reject | +| Redirected RRC message | O | | RRC Container 9.3.1.6 | Includes the UL-CCCH-Message message as defined in subclause 6.2 of TS 38.331 [8]. | YES | reject | +| PLMN Assistance Info for Network Sharing | O | | PLMN Identity 9.3.1.14 | | YES | ignore | +| New gNB-CU UE F1AP ID | O | | gNB-CU UE F1AP ID 9.3.1.4 | | YES | reject | +| Additional RRM Policy Index | O | | 9.3.1.90 | | YES | ignore | +| SRB Mapping Info | O | | Uu RLC Channel ID 9.3.1.266 | This IE contains the mapped Uu Relay RLC CH ID for the Remote UE's SRB0 or SRB1. | YES | ignore | + +### 9.2.3.3 UL RRC MESSAGE TRANSFER + +This message is sent by the gNB-DU to transfer the layer 3 message to the gNB-CU over the F1 interface. + +Direction: gNB-DU → gNB-CU + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| SRB ID | M | | 9.3.1.7 | | YES | reject | +| RRC-Container | M | | 9.3.1.6 | Includes the UL-DCCH-Message message as defined in subclause 6.2 of TS 38.331 [8], encapsulated in a PDCP PDU. In case of CG-SDT, may include the UL-CCCH-Message message or UL-CCCH1-Message message as defined in subclause 6.2 of TS 38.331 [8]. | YES | reject | +| Selected PLMN ID | O | | PLMN Identity 9.3.1.14 | | YES | reject | +| New gNB-DU UE F1AP ID | O | | gNB-DU UE F1AP ID 9.3.1.5 | | YES | reject | + +### 9.2.3.4 RRC DELIVERY REPORT + +This message is sent by the gNB-DU to inform the gNB-CU about the delivery status of DL RRC messages. + +Direction: gNB-DU → gNB-CU + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| RRC Delivery Status | M | | 9.3.1.71 | | YES | ignore | +| SRB ID | M | | 9.3.1.7 | | YES | ignore | + +## 9.2.4 Warning Message Transmission Messages + +### 9.2.4.1 WRITE-REPLACE WARNING REQUEST + +This message is sent by the gNB-CU to request the start or overwrite of the broadcast of a warning message. + +Direction: gNB-CU → gNB-DU + +| 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.23 | | YES | reject | +| PWS System Information | M | | 9.3.1.58 | This IE includes the system information for public warning, as defined in TS 38.331 [8]. | YES | reject | +| Repetition Period | M | | 9.3.1.59 | | YES | reject | +| Number of Broadcasts Requested | M | | 9.3.1.60 | | YES | reject | +| Cell To Be Broadcast List | | 0..1 | | | YES | reject | +| >Cell to Be Broadcast Item IEs | | 1..
ngNBDU> | | | EACH | reject | +| >>NR CGI | M | | 9.3.1.12 | | - | | + +| Range bound | Explanation | +|----------------|-----------------------------------------------------------------| +| maxCellingNBDU | Maximum no. cells that can be served by a gNB-DU. Value is 512. | + +## 9.2.4.2 WRITE-REPLACE WARNING RESPONSE + +This message is sent by the gNB-DU to acknowledge the gNB-CU on the start or overwrite request of a warning message. + +Direction: gNB-DU → gNB-CU + +| 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 | +| Cell Broadcast Completed List | | 0..1 | | | YES | reject | +| >Cell Broadcast Completed Item IEs | | 1..
ngNBDU> | | | EACH | reject | +| >>NR CGI | M | | 9.3.1.12 | | - | | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| Dedicated SI Delivery Needed UE List | | 0..1 | | List of UEs unable to receive system information from broadcast | YES | ignore | +| >Dedicated SI Delivery Needed UE Item | | 1..
UEIDs> | | | EACH | ignore | +| >>gNB-CU UE F1AP | M | | 9.3.1.4 | | - | | + +| | | | | | | | +|----------|---|--|----------|--|---|--| +| ID | | | | | | | +| >>NR CGI | M | | 9.3.1.12 | | - | | + +| Range bound | Explanation | +|----------------|--------------------------------------------------------------------| +| maxCellingNBDU | Maximum no. cells that can be served by a gNB-DU. Value is 512. | +| maxnoofUEIDs | Maximum no. of UEs that can be served by a gNB-DU. Value is 65536. | + +### 9.2.4.3 PWS CANCEL REQUEST + +This message is forwarded by the gNB-CU to gNB-DU to cancel an already ongoing broadcast of a warning message + +Direction: gNB-CU → gNB-DU + +| 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 | +| Number of Broadcasts Requested | M | | 9.3.1.60 | This IE is not used in this version of the specification | YES | reject | +| Cell Broadcast To Be Cancelled List | | 0..1 | | | YES | reject | +| >Cell Broadcast to Be Cancelled Item IEs | | 1..
| | | EACH | reject | +| >>NR CGI | M | | 9.3.1.12 | | - | | +| Cancel-all Warning Messages Indicator | O | | | ENUMERATED (true, ...) | YES | reject | +| Notification Information | O | | | This IE is ignored If the Cancel-all Warning Messages Indicator IE is included. | YES | reject | +| >Message Identifier | M | | 9.3.1.81 | | - | | +| >Serial Number | M | | 9.3.1.82 | | - | | + +| Range bound | Explanation | +|----------------|-----------------------------------------------------------------| +| maxCellingNBDU | Maximum no. cells that can be served by a gNB-DU. Value is 512. | + +### 9.2.4.4 PWS CANCEL RESPONSE + +This message is sent by the gNB-DU to indicate the list of warning areas where cancellation of the broadcast of the identified message was successful and unsuccessful. + +Direction: gNB-DU → gNB-CU + +| 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 | +| Cell Broadcast
Cancelled List | | 0..1 | | | YES | reject | +| > Cell Broadcast
Cancelled Item IEs | | 1..
ngNBDU> | | | EACH | reject | +| >>NR CGI | M | | 9.3.1.12 | | - | | +| >>Number of
Broadcasts | M | | INTEGER
(0..65535) | This IE is set to '0' if valid results are not known or not available. It is set to 65535 if the counter results have overflowed. | - | | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +| Range bound | Explanation | +|----------------|--------------------------------------------------------------------| +| maxCellingNBDU | Maximum no. of cells that can be served by a gNB-DU. Value is 512. | + +#### 9.2.4.5 PWS RESTART INDICATION + +This message is sent by the gNB-DU to inform the gNB-CU that PWS information for some or all cells of the gNB-DU are available if needed. + +Direction: gNB-DU → gNB-CU + +| 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.23 | | YES | reject | +| NR CGI List for
Restart List | | 1 | | | YES | reject | +| > NR CGI List for
Restart Item IEs | | 1..
ellingNBD
U> | | | EACH | reject | +| >>NR CGI | M | | 9.3.1.12 | | - | | + +| Range bound | Explanation | +|----------------|--------------------------------------------------------------------| +| maxCellingNBDU | Maximum no. of cells that can be served by a gNB-DU. Value is 512. | + +#### 9.2.4.6 PWS FAILURE INDICATION + +This message is sent by the gNB-DU to inform the gNB-CU that ongoing PWS operation for one or more cells of the gNB-DU has failed. + +Direction: gNB-DU → gNB-CU + +| 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.23 | | YES | reject | +| PWS failed NR CGI List | | 0..1 | | | YES | reject | +| >PWS failed NR CGI Item IEs | | 1.. | | | EACH | reject | +| >>NR CGI | M | | 9.3.1.12 | | - | | +| >>Number of Broadcasts | M | | INTEGER (0..65535) | This IE is not used in the specification and is ignored. | - | | + +| Range bound | Explanation | +|----------------|--------------------------------------------------------------------| +| maxCellingNBDU | Maximum no. of cells that can be served by a gNB-DU. Value is 512. | + +## 9.2.5 System Information messages + +### 9.2.5.1 SYSTEM INFORMATION DELIVERY COMMAND + +This message is sent by the gNB-CU and is used to request the gNB-DU to broadcast the requested *SystemInformation* messages including the Other SI. + +Direction: gNB-CU → gNB-DU + +| 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.23 | | YES | reject | +| NR CGI | M | | 9.3.1.12 | NR cell identifier | YES | reject | +| SIType List | M | | 9.3.1.62 | | YES | reject | +| Confirmed UE ID | M | | gNB-DU UE F1AP ID 9.3.1.5 | | YES | reject | + +## 9.2.6 Paging messages + +### 9.2.6.1 PAGING + +This message is sent by the gNB-CU and is used to request the gNB-DU to page UEs. + +Direction: gNB-CU → gNB-DU + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| UE Identity Index value | M | | 9.3.1.39 | | YES | reject | +| CHOICE Paging Identity | M | | | | YES | reject | +| >RAN UE Paging identity | | | | | | | +| >>RAN UE Paging | M | | 9.3.1.43 | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------|----------|------------------------------|-------------------------|---------------------------------------------------------------------------------|-------------|----------------------| +| identity | | | | | | | +| >CN UE paging identity | | | | | | | +| >>CN UE paging identity | M | | 9.3.1.44 | | - | | +| Paging DRX | O | | 9.3.1.40 | It is defined as the minimum between the RAN UE Paging DRX and CN UE Paging DRX | YES | ignore | +| Paging Priority | O | | 9.3.1.41 | | YES | ignore | +| Paging Cell List | | 1 | | | YES | ignore | +| >Paging Cell Item IEs | | 1 .. | | | EACH | ignore | +| >>NR CGI | M | | 9.3.1.12 | | - | | +| >>Last Used Cell Indication | O | | ENUMERATED (true, ...) | | YES | ignore | +| >>PEI Subgrouping Support Indication | O | | ENUMERATED (true, ...) | | YES | ignore | +| >>Recommended SSBs List | | 0 .. | | | YES | ignore | +| >>>SSB Index | M | | INTEGER (0..63) | Identifier of the recommended SSB beam for paging. | - | | +| Paging Origin | O | | 9.3.1.79 | | YES | ignore | +| RAN UE Paging DRX | O | | Paging DRX 9.3.1.40 | This IE indicates the RAN paging cycle as defined in TS 38.304 [24]. | YES | ignore | +| CN UE Paging DRX | O | | Paging DRX 9.3.1.40 | This IE indicates the UE specific paging cycle as defined in TS 38.304 [24]. | YES | ignore | +| NR Paging eDRX Information | O | | 9.3.1.258 | | YES | ignore | +| NR Paging eDRX Information for RRC INACTIVE | O | | 9.3.1.259 | | YES | ignore | +| Paging Cause | O | | ENUMERATED (voice, ...) | This IE indicates the paging cause is IMS voice, refer to TS 23.501[21]. | YES | ignore | +| PEIPS Assistance Information | O | | 9.3.1.269 | | YES | ignore | +| UE Paging Capability | O | | 9.3.1.270 | | YES | ignore | +| Extended UE Identity Index Value | O | | 9.3.1.285 | | YES | ignore | +| Hashed UE Identity Index Value | O | | 9.3.1.286 | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| MT-SDT Information | O | | 9.3.1.289 | | YES | ignore | +| NR Paging Long eDRX Information for RRC INACTIVE | O | | 9.3.1.325 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|------------------------------------------------------------------| +| maxnoofPagingCells | Maximum no. of paging cells, the maximum value is 512. | +| maxnoofSSBAreas | Maximum no. SSB Areas that can be served by a cell. Value is 64. | + +## 9.2.7 Trace Messages + +### 9.2.7.1 TRACE START + +This message is sent by the gNB-CU to initiate a trace session for a UE. + +Direction: gNB-CU → gNB-DU + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| Trace Activation | M | | 9.3.1.88 | | YES | ignore | + +### 9.2.7.2 DEACTIVATE TRACE + +This message is sent by the gNB-CU to deactivate a trace session. + +Direction: gNB-CU → gNB-DU + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP 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.7.3 CELL TRAFFIC TRACE + +This message is sent by the gNB-DU to transfer trace specific information. + +Direction: gNB-DU → gNB-CU + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| Trace ID | M | | OCTET | This IE is | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------|----------|-------|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | STRING (SIZE(8)) | composed of the following:
Trace Reference defined in TS 32.422 [29] (leftmost 6 octets, with PLMN information encoded as in 9.3.1.14), and Trace Recording Session Reference defined in TS 32.422 [29] (last 2 octets). | | | +| Trace Collection Entity IP Address | M | | Transport Layer Address 9.3.2.3 | For File based Reporting. Defined in TS 32.422 [29]. Should be ignored if URI is present | YES | ignore | +| Privacy Indicator | O | | ENUMERATED (Immediate MDT, Logged MDT, ...) | | YES | ignore | +| Trace Collection Entity URI | O | | URI 9.3.2.6 | For Streaming based Reporting. Defined in TS 32.422 [29]. Replaces Trace Collection Entity IP Address if present | YES | ignore | + +## 9.2.8 Radio Information Transfer messages + +### 9.2.8.1 DU-CU RADIO INFORMATION TRANSFER + +This message is sent by a gNB-DU to a gNB-CU, to convey radio-related information. + +Direction: gNB-DU → gNB-CU. + +| 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.23 | | YES | reject | +| CHOICE DU-CU Radio Information Type | M | | | | YES | ignore | +| >RIM | | | | | | | +| >>DU-CU RIM Information | M | | 9.3.1.91 | | - | - | + +### 9.2.8.2 CU-DU RADIO INFORMATION TRANSFER + +This message is sent by a gNB-CU to a gNB-DU, to convey radio-related information. + +Direction: gNB-CU → gNB-DU. + +| 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.23 | | YES | reject | +| CHOICE CU-DU Radio Information Type | M | | | | YES | ignore | +| > RIM | | | | | | | +| >> CU-DU RIM Information | M | | 9.3.1.92 | | - | - | + +## 9.2.9 IAB messages + +### 9.2.9.1 BAP MAPPING CONFIGURATION + +This message is sent by the gNB-CU to provide the backhaul routing information and/or traffic mapping information to the gNB-DU. + +Direction: gNB-CU → gNB-DU + +| 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 | +| BH Routing Information Added List | | 0...1 | | | YES | ignore | +| > BH Routing Information Added List Item | | 1..
RoutingEn
tries> | | | EACH | ignore | +| >>BAP Routing ID | M | | 9.3.1.110 | | - | | +| >>Next-Hop BAP Address | M | | 9.3.1.111 | Indicates the BAP address of the next hop IAB-node or IAB-donor-DU. | - | | +| >>Non-F1-Terminating IAB-donor Topology Indicator | O | | ENUMERATED
(true, ...) | If present, indicates that the routing entry applies to the non-F1-terminating IAB-donor topology of the boundary IAB-node. | YES | ignore | +| BH Routing Information Removed List | | 0...1 | | | YES | ignore | +| > BH Routing Information Removed List Item | | 1..
RoutingEn
tries> | | | EACH | ignore | +| >>BAP Routing ID | M | | 9.3.1.110 | | - | | +| Traffic Mapping | O | | 9.3.1.95 | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------------|----------|--------------------------------|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Information | | | | | | | +| Buffer Size Threshold | O | | INTEGER (0..2 24 -1) | The buffer size threshold (in kilobytes) for DL local rerouting, triggered by hop-by-hop flow control feedback. | YES | ignore | +| BAP Header Rewriting Added List | | 0..1 | | | YES | ignore | +| > BAP Header Rewriting Added List Item | | 1..
| | | EACH | ignore | +| >>Ingress BAP Routing ID | M | | 9.3.1.110 | | - | | +| >>Egress BAP Routing ID | M | | 9.3.1.110 | | - | | +| >>Non-F1-terminating IAB-donor Topology Indicator | O | | ENUMERATED (true, ...) | If present, indicates that the egress BAP Routing ID in the present BAP header rewriting entry pertains to the non-F1-terminating IAB-donor topology of the boundary IAB-node. | - | | +| Re-routing Enable Indicator | O | | ENUMERATED (true, false, ...) | | YES | ignore | +| BAP Header Rewriting Removed List | | 0..1 | | | YES | ignore | +| > BAP Header Rewriting Removed List Item | | 1..
| | | EACH | ignore | +| >>Ingress BAP Routing ID | M | | 9.3.1.110 | | | | + +| Range bound | Explanation | +|-----------------------|------------------------------------------------------------| +| maxnoofRoutingEntries | Maximum no. of routing entries, the maximum value is 1024. | + +## 9.2.9.2 BAP MAPPING CONFIGURATION ACKNOWLEDGE + +This message is sent by the gNB-DU as a response to a BAP MAPPING CONFIGURATION message. + +Direction: gNB-DU → gNB-CU + +| 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 | + +| 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.9.2A BAP MAPPING CONFIGURATION FAILURE + +This message is sent by the gNB-DU to indicate a BAP Mapping Configuration Update failure. + +Direction: gNB-DU → gNB-CU + +| 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 | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Time to wait | O | | 9.3.1.13 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.9.3 GNB-DU RESOURCE CONFIGURATION + +This message is sent by the gNB-CU to provide the resource configuration for an gNB-DU. + +Direction: gNB-CU → gNB-DU + +| 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 | +| Activated Cells to Be Updated List | | 0..1 | | List of activated cells served by the IAB-DU or the IAB-donor-DU whose resource configuration is updated | YES | reject | +| >Activated Cells To Be Updated List Item | | 1 .. | | | EACH | reject | +| >>NR CGI | M | | 9.3.1.12 | | - | | +| >>IAB-DU Cell Resource Configuration-Mode-Info | M | | 9.3.1.279 | In the current version of this specification, for FDD, this IE only contains the gNB-DU Cell Resource Configuration-FDD-UL IE and the gNB-DU Cell Resource Configuration-FDD-DL IE, for TDD, this IE only contains the gNB-DU Cell Resource | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------------|----------|--------------------------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | Configuration-TDD IE | | | +| Child-Nodes List | | 0..1 | | List of child IAB-nodes served by the IAB-DU or IAB-donor-DU. | YES | reject | +| >Child-Nodes List Item | | 1 ..
ChildIABNodes> | | | EACH | reject | +| >>gNB-CU UE F1AP ID | M | | 9.3.1.4 | Identifier of a descendant node IAB-MT at the IAB-donor-CU. | YES | reject | +| >>gNB-DU UE F1AP ID | M | | 9.3.1.5 | Identifier of a child-node IAB-MT at an IAB-DU or IAB-donor-DU. | YES | reject | +| >>Child-Node Cells List | | 0..1 | | List of cells served by the child-node IAB-DU whose resource configuration is updated. | YES | reject | +| >>>Child-Node Cells List Item | | 1 ..
ServedCellsIAB > | | | EACH | reject | +| >>>>NR CGI | M | | 9.3.1.12 | | - | | +| >>>>IAB-DU Cell Resource Configuration-Mode-Info | O | | 9.3.1.279 | | - | | +| >>>>IAB STC Info | O | | 9.3.1.109 | STC configuration of child-node IAB-DU's cell. | - | | +| >>>>RACH Config Common | O | | OCTET STRING | Includes the rach-ConfigCommon contained in the BWP-UplinkCommon IE as defined in subclause 6.3.2 of TS 38.331 [8]. | - | | +| >>>>RACH Config Common IAB | O | | OCTET STRING | Includes the IAB-specific rach-ConfigCommonIAB contained in the BWP-UplinkCommon IE as defined in subclause 6.3.2 of TS 38.331 [8]. | - | | +| >>>>CSI-RS Configuration | O | | OCTET STRING | Includes the NZP-CSI-RS-Resource IE as defined in subclause 6.3.2 of | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|----------------------------------------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | TS 38.331 [8]. | | | +| >>>>SR Configuration | O | | OCTET STRING | Includes the SchedulingRequestResourceConfig IE as defined in subclause 6.3.2 of TS 38.331 [8]. | - | | +| >>>>PDCCH Configuration SIB1 | O | | OCTET STRING | Includes the PDCCH-ConfigSIB1 IE as defined in subclause 6.3.2 of TS 38.331 [8]. | - | | +| >>>>SCS Common | O | | OCTET STRING | Includes the subCarrierSpacingCommon contained in the MIB message as defined in subclause 6.2.2 of TS 38.331 [8]. | - | | +| >>>>Multiplexing Info | O | | 9.3.1.108 | Contains information on multiplexing with cells configured for co-located IAB-MT. | - | | +| Neighbour-Node Cells List | | 0..1 | | List of neighbor node cells. | YES | reject | +| >Neighbour-Node Cells List Item | | 1 .. < maxnoofNeighbourNodeCellsIAB > | | | EACH | reject | +| >>NR CGI | M | | 9.3.1.12 | | - | | +| >>gNB-CU UE F1AP ID | O | | 9.3.1.4 | Identifier of a child-node IAB-MT at an IAB-donor-CU. | - | | +| >>gNB-DU UE F1AP ID | O | | 9.3.1.5 | Identifier of a child-node IAB-MT at an IAB-DU or IAB-donor-DU. | - | | +| >>Peer Parent-Node Indicator | O | | ENUMERATED (true, ...) | Indicates if the cell belongs to the peer parent IAB-node of the dual connected IAB-node. | - | | +| >>IAB-DU Cell Resource Configuration-Mode-Info | O | | 9.3.1.279 | | - | | +| >>IAB STC Info | O | | 9.3.1.109 | STC configuration of peer parent-node IAB-DU's cell. | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>RACH Config Common | O | | OCTET STRING | Common RACH Configuration of peer parent node IAB-DU's cell. Includes the rach-ConfigCommon contained in the BWP-UplinkCommon IE as defined in subclause 6.3.2 of TS 38.331 [8]. | - | | +| >>RACH Config Common IAB | O | | OCTET STRING | IAB specific common RACH Configuration of peer parent node IAB-DU's cell. Includes the IAB-specific rach-ConfigCommonIAB contained in the BWP-UplinkCommon IE as defined in subclause 6.3.2 of TS 38.331 [8]. | - | | +| >>CSI-RS Configuration | O | | OCTET STRING | CSI-RS configuration of peer parent node IAB-DU's cell. Includes the NZP-CSI-RS-Resource as defined in subclause 6.3.2 of TS 38.331 [8]. | - | | +| >>SR Configuration | O | | OCTET STRING | SR configuration of peer parent node IAB-DU's cell. Includes the SchedulingRequestResourceConfig IE as defined in subclause 6.3.2 of TS 38.331 [8]. | - | | +| >>PDCCH Configuration SIB1 | O | | OCTET STRING | PDCCH configuration SIB1 of peer parent node IAB-DU's cell. Includes the PDCCH-ConfigSIB1 IE as defined in subclause 6.3.2 of TS 38.331 [8]. | - | | +| >>SCS Common | O | | OCTET STRING | SCS Common of peer parent node | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------------|----------|--------------------------------|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | IAB-DU's cell. Includes the subCarrierSpacing Common contained in the MIB message as defined in subclause 6.2.2 of TS 38.331 [8]. | | | +| Serving Cells List | | 0..1 | | List of serving cells of the co-located IAB-MT. | YES | reject | +| >Serving Cells List Item | | 1 .. < maxnoofS ervingCell s > | | | EACH | reject | +| >>NR CGI | M | | 9.3.1.12 | | - | | +| >>CHOICE IAB-MT Cell NA Resource Configuration-Mode-Info | O | | | | - | | +| >>>FDD | | | | | | | +| >>>>FDD Info | | 1 | | | - | | +| >>>>>gNB-DU Cell NA Resource Configuration-FDD-UL | M | | gNB-DU Cell Resource Configuration 9.3.1.107 | Contains FDD UL NA resource configuration of parent IAB-node's cell for the co-located IAB-MT. | - | | +| >>>>>gNB-DU Cell NA Resource Configuration-FDD-DL | M | | gNB-DU Cell Resource Configuration 9.3.1.107 | Contains FDD DL NA resource configuration of parent IAB-node's cell for the co-located IAB-MT. | - | | +| >>>>>UL Frequency Info | O | | NR Frequency Info 9.3.1.17 | | - | | +| >>>>>UL Transmission Bandwidth | O | | Transmission Bandwidth 9.3.1.15 | | - | | +| >>>>>UL Carrier List | O | | NR Carrier List 9.3.1.137 | If included, the UL Transmission Bandwidth IE shall be ignored. | - | | +| >>>>>DL Frequency Info | O | | NR Frequency Info 9.3.1.17 | | - | | +| >>>>>DL Transmission Bandwidth | O | | Transmission Bandwidth 9.3.1.15 | | - | | +| >>>>>DL Carrier List | O | | NR Carrier List 9.3.1.137 | If included, the UL Transmission Bandwidth IE shall be ignored. | - | | +| >>>TDD | | | | | - | | +| >>>>TDD Info | | 1 | | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|-------|----------------------------------------------|---------------------------------------------------------------------------------------------|-------------|----------------------| +| >>>>>gNB-DU Cell NA Resource Configuration-TDD | M | | gNB-DU Cell Resource Configuration 9.3.1.107 | Contains TDD NA resource configuration of parent IAB-node's cell for the co-located IAB-MT. | - | | +| >>>>>NR Frequency Info | O | | NR Frequency Info 9.3.1.17 | | - | | +| >>>>>Transmission Bandwidth | O | | Transmission Bandwidth 9.3.1.15 | | - | | +| >>>>>Carrier List | O | | NR Carrier List 9.3.1.137 | If included, the Transmission Bandwidth IE shall be ignored. | - | | + +| Range bound | Explanation | +|------------------------------|-----------------------------------------------------------------------------------| +| maxnoofChildIABNodes | Maximum number of child nodes served by an IAB-DU or IAB-donor-DU. Value is 1024. | +| maxnoofServedCellsIAB | Maximum number of cells served by an IAB-DU or IAB-donor-DU. Value is 512. | +| maxnoofNeighbourNodeCellsIAB | Maximum no. of neighbour cells. Value is 1024. | +| MaxnoofServingCells | Maximum no. of serving cells for IAB-MT. Value is 32 | + +#### 9.2.9.4 GNB-DU RESOURCE CONFIGURATION ACKNOWLEDGE + +This message is sent by the gNB-DU to acknowledge the reception of an GNB-DU RESOURCE CONFIGURATION message. + +Direction: gNB-DU → gNB-CU + +| 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 | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +#### 9.2.9.4A GNB-DU RESOURCE CONFIGURATION FAILURE + +This message is sent by the gNB-DU to indicate a gNB-DU Resource Configuration Update failure. + +Direction: gNB-DU → gNB-CU + +| 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 | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Time to wait | O | | 9.3.1.13 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.9.5 IAB TNL ADDRESS REQUEST + +This message is sent by the gNB-CU to request the allocation of IP addresses for IAB-node(s). + +Direction: gNB-CU → gNB-DU. + +| 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 IPv4 Addresses Requested | O | | IAB TNL Addresses Requested 9.3.1.101 | | YES | reject | +| CHOICE IAB IPv6 Request Type | O | | | | YES | reject | +| >IPv6 Address | | | | | - | | +| >>IAB IPv6 Addresses Requested | M | | IAB TNL Addresses Requested 9.3.1.101 | | - | | +| >IPv6 Prefix | | | | | - | | +| >>IAB IPv6 Address Prefixes Requested | M | | IAB TNL Addresses Requested 9.3.1.101 | | - | | +| IAB TNL Addresses To Remove List | | 0..1 | | | YES | reject | +| >IAB TNL Addresses To Remove Item | | 1.. | | | EACH | reject | +| >>IAB TNL Address | M | | 9.3.1.102 | | - | | +| IAB TNL Address Exception | O | | 9.3.1.229 | | YES | reject | + +| Range bound | Explanation | +|----------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| maxnoofTLAsIAB | Maximum no. of individual IPv4/IPv6 addresses or IPv6 address prefixes that can be allocated in one procedure execution. The value is 1024. | + +### 9.2.9.6 IAB TNL ADDRESS RESPONSE + +This message is sent by the gNB-DU to indicate the TNL addresses allocated to IAB-node(s). + +Direction: gNB-DU → gNB-CU. + +| 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 Allocated TNL Address List | | 1 | | | YES | reject | +| >IAB Allocated TNL Address Item | | 1.. | | | EACH | reject | +| >>IAB TNL Address | M | | 9.3.1.102 | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|--------------------------------------|-------------------------------------------------------------------------|-------------|----------------------| +| >>IAB TNL Address Usage | O | | ENUMERATED (F1-C, F1-U, Non-F1, ...) | The usage of the allocated IPv4 or IPv6 address or IPv6 address prefix. | - | | + +| Range bound | Explanation | +|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxnoofTLAsIAB | Maximum no. of IPv6 addresses or IPv6 address prefixes and/or individual IPv4 addresses that can be allocated in one procedure execution. The value is 1024. | + +### 9.2.9.6A IAB TNL ADDRESS FAILURE + +This message is sent by the gNB-DU to indicate an IAB TNL Address Allocation failure. + +Direction: gNB-DU → gNB-CU + +| 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 | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Time to wait | O | | 9.3.1.13 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.9.7 IAB UP CONFIGURATION UPDATE REQUEST + +This message is sent by the gNB-CU to provide the updated UL BH Information or the updated UL UP TNL Information/Address to the gNB-DU. + +Direction: gNB-CU → gNB-DU + +| 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 | +| UL UP TNL Information to Update List | | 0..1 | | | YES | ignore | +| >UL UP TNL Information to Update List Item IEs | | 1.. < maxnoofULUPTNLInformationf orIAB> | | | EACH | ignore | +| >>UL UP TNL Information | M | | UP Transport Layer Information 9.3.2.1 | This field indicates the UL UP TNL Information used before configuration update. | - | | +| >>New UL UP TNL Information | O | | UP Transport Layer Information | If present, this field indicates the new UL UP TNL | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------------|----------|-----------------------------|---------------------------------|--------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | 9.3.2.1 | Information used after configuration update. | | | +| >>BH Information | M | | 9.3.1.114 | | - | | +| UL UP TNL Address to Update List | | 0..1 | | | YES | ignore | +| >UL UP TNL Address to Update List Item IEs | | 1.. | | | EACH | ignore | +| >>Old TNL Address | M | | Transport Layer Address 9.3.2.3 | The old UL UP Transport Layer Address of gNB-CU used for UL F1-U GTP Tunnel before the configuration update. | - | | +| >>New TNL Address | M | | Transport Layer Address 9.3.2.3 | The corresponding new UL UP Transport Layer Address that replaces the old one. | - | | + +| Range bound | Explanation | +|---------------------------------|------------------------------------------------------------------------------------------------| +| maxnoofULUPTNLInformationforIAB | Maximum no. of UL UP TNL Information allowed towards one IAB node, the maximum value is 32768. | +| maxnoofUPTNLAddresses | Maximum no. of TNL addresses for F1-U. Value is 8. | + +## 9.2.9.8 IAB UP CONFIGURATION UPDATE RESPONSE + +This message is sent by the gNB-DU to provide the updated TNL address(es) of the DL F1-U GTP tunnels to the gNB-CU. + +Direction: gNB-DU → gNB-CU + +| 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 | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| DL UP TNL Address to Update List | | 0..1 | | | YES | ignore | +| >DL UP TNL Address to Update List Item IEs | | 1.. | | | EACH | ignore | +| >>Old TNL Address | M | | Transport Layer Address 9.3.2.3 | The old DL UP Transport Layer Address of gNB-DU used for DL F1-U GTP tunnel before the | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------|----------|-------|---------------------------------|----------------------------------------------------------------------------|-------------|----------------------| +| | | | | configuration update. | | | +| >>New TNL Address | M | | Transport Layer Address 9.3.2.3 | The corresponding new Transport Layer Address used to replace the old one. | - | | + +| Range bound | Explanation | +|-----------------------|----------------------------------------------------| +| maxnoofUPTNLAddresses | Maximum no. of TNL addresses for F1-U. Value is 8. | + +### 9.2.9.9 IAB UP CONFIGURATION UPDATE FAILURE + +This message is sent by the gNB-DU to indicate an IAB UP Configuration Update failure. + +Direction: gNB-DU → gNB-CU + +| 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 | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Time to wait | O | | 9.3.1.13 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.9.10 MIAB F1 SETUP TRIGGERING + +This message is sent by the gNB-CU to trigger F1 interface setup from the gNB-DU's co-located target logical gNB-DU to the target F1-terminating IAB-donor-CU. + +Direction: gNB-CU → gNB-DU + +| 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 | +| Target gNB ID | M | | Global gNB ID 9.3.1.305 | | YES | reject | +| Target gNB IP Address | O | | Transport Layer Address 9.3.2.3 | | YES | ignore | +| Target SeGW IP Address | O | | Transport Layer Address 9.3.2.3 | | YES | ignore | + +### 9.2.9.11 MIAB F1 SETUP OUTCOME NOTIFICATION + +This message is sent by the gNB-DU to notify the gNB-CU about the outcome of F1 interface setup between the gNB-DU's co-located target logical gNB-DU and a target F1-terminating IAB-donor-CU. + +Direction: gNB-DU → gNB-CU + +| 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 | +| F1 Setup Outcome | M | | ENUMERATED (success, failure, ...) | | YES | reject | +| Activated Cells Mapping List | | 0..1 | | | YES | ignore | +| > Activated Cells List Mapping Item IEs | | 1..
| | List of activated cells. | EACH | ignore | +| >>NR CGI for Target Logical gNB-DU | O | | NR CGI 9.3.1.12 | The identity of an activated cell belonging to the target logical gNB-DU of the mobile IAB-node | - | | +| >>NR CGI for Source Logical gNB-DU | O | | NR CGI 9.3.1.12 | The identity of an activated cell belonging to the source logical gNB-DU of the mobile IAB-node | - | | +| Target F1 Terminating IAB-Donor gNB ID | O | | Global gNB ID 9.3.1.305 | The Global gNB ID of an IAB donor terminates F1 connection towards the target logical gNB-DU of the mobile IAB-node. This IE is present if the mobile IAB-DU migration is triggered by OAM. | YES | reject | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------| +| maxCellingNB DU | Maximum no. cells that can be served by a gNB-DU. Value is 512. | + +## 9.2.10 Self Optimisation Support Messages + +### 9.2.10.1 ACCESS AND MOBILITY INDICATION + +This message is sent by gNB-CU to gNB-DU to provide access and mobility information to the gNB-DU. + +Direction: gNB-CU → gNB-DU. + +| 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.23 | | YES | reject | +| RA Report List | | 0..1 | | | YES | ignore | +| > RA Report Item | | 1 .. | | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------------------|----------|---------------------------------------------------|---------------------------|--------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | RAReports> | | | | | +| >>RA Report Container | M | | OCTET STRING | Includes the RA-ReportList-r16 IE as defined in subclause 6.2.2 in TS 38.331 [8]. | - | | +| >>UE Assistant Identifier | O | | gNB-DU UE F1AP ID 9.3.1.5 | | - | | +| RLF Report Information List | | 0..1 | | | YES | ignore | +| >RLF Report Information Item | | 1 ..
RLFReports> | | | - | | +| >>NR UE RLF Report Container | M | | OCTET STRING | Includes the nr-RLF-Report-r16 IE contained in the UEInformationResponse message defined in TS 38.331 [8]. | - | | +| >>UE Assistant Identifier | O | | gNB-DU UE F1AP ID 9.3.1.5 | | - | | +| Successful HO Report Information List | | 0..1 | | | YES | ignore | +| >Successful HO Report Information Item | | 1 ..
SuccessfulHOReports> | | | - | | +| >>Successful HO Report Container | M | | OCTET STRING | Includes the SuccessHO-Report IE as defined in subclause 6.2.2 in TS 38.331 [8]. | - | | +| Successful PSCell Change Report Information List | | 0..1 | | | YES | ignore | +| >Successful PSCell Change Report information Item | | 1..SuccessfulPSCell
ChangeReports> | | | - | | +| >>Successful PSCell Change Report Container | M | | OCTET STRING | Includes the SuccessPSCell-Report IE as defined in TS 38.331 [8]. | - | | + +| Range bound | Explanation | +|--------------------------------------|----------------------------------------------------------------| +| maxnoofRAReports | Maximum no. of RA Reports, the maximum value is 64. | +| maxnoofRLFReports | Maximum no. of RLF Reports, the maximum value is 64. | +| maxnoofSuccessfulHOReports | Maximum no. of Successful HO Reports, the maximum value is 64. | +| maxnoofSuccessfulPSCellChangeReports | Maximum no. of Successful PSCell Change Reports. Value is 64. | + +## 9.2.11 Reference Time Information Reporting messages + +### 9.2.11.1 REFERENCE TIME INFORMATION REPORTING CONTROL + +This message is sent by the gNB-CU and is used to request the gNB-DU to deliver the accurate reference time information. + +Direction: gNB-CU → gNB-DU + +| 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.23 | | YES | reject | +| Reporting Request Type | M | | 9.3.1.147 | | YES | reject | + +### 9.2.11.2 REFERENCE TIME INFORMATION REPORT + +This message is sent by the gNB-DU and is used to report the accurate reference time information to the gNB-CU. + +Direction: gNB-DU → gNB-CU + +| 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.23 | | YES | ignore | +| Time Reference Information | M | | 9.3.1.148 | | YES | ignore | + +## 9.2.12 Messages for Positioning Procedures + +### 9.2.12.1 POSITIONING ASSISTANCE INFORMATION CONTROL + +This message is sent by the gNB-CU to transfer positioning assistance information. + +Direction: gNB-CU → gNB-DU. + +| 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.23 | | YES | reject | +| Positioning Assistance Information | O | | OCTET STRING | Contains the Assistance Information IE as defined in TS 38.455 [37]. | YES | reject | +| Broadcast | O | | ENUMERATED | | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | (start, stop, ...) | | | | +| Positioning Broadcast Cells | O | | 9.3.1.191 | The cell(s) that are requested to broadcast posSIB(s) according to the Positioning Assistance Information IE . | YES | reject | +| Routing ID | O | | OCTET STRING | | YES | reject | + +### 9.2.12.2 POSITIONING ASSISTANCE INFORMATION FEEDBACK + +This message is sent by the gNB-DU to give feedback on positioning assistance information broadcasting. + +Direction: gNB-DU → gNB-CU. + +| 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.23 | | YES | reject | +| Positioning Assistance Information Failure List | O | | OCTET STRING | Contains the Assistance Information IE as defined in TS 38.455 [37]. | YES | reject | +| Positioning Broadcast Cells | O | | 9.3.1.191 | The cells associated to the feedback provided in the Positioning Assistance Information Failure List IE . | YES | reject | +| Routing ID | O | | OCTET STRING | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.12.3 POSITIONING MEASUREMENT REQUEST + +This message is sent by the gNB-CU to request the gNB-DU to configure a positioning measurement. + +Direction: gNB-CU → gNB-DU. + +| 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 | +| LMF Measurement ID | M | | INTEGER (1..65536, ...) | | YES | reject | +| RAN Measurement ID | M | | INTEGER (1..65536, ...) | | YES | reject | +| TRP Measurement Request List | | 1 | | | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------|------------------------------------|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >TRP Measurement Request Item | | 1.. | | | - | | +| >>TRP ID | M | | 9.3.1.197 | | - | | +| >>Search Window Information | O | | 9.3.1.204 | | - | | +| >>NR CGI | O | | 9.3.1.12 | The Cell ID of the TRP identified by the TRP ID IE. | YES | ignore | +| >>AoA Search Window Information | O | | UL-AoA Assistance Information 9.3.1.238 | | YES | ignore | +| >>Number of TRP Rx TEGs | O | | ENUMERATED (2, 3, 4, 6, 8, ...) | | YES | ignore | +| >>Number of TRP RxTx TEGs | O | | ENUMERATED (2, 3, 4, 6, 8, ...) | | YES | ignore | +| Positioning Report Characteristics | M | | ENUMERATED (OnDemand, Periodic, ...) | | YES | reject | +| Positioning Measurement Periodicity | C- ifReportCharacteristicsPeriodic | | ENUMERATED (120ms, 240ms, 480ms, 640ms, 1024ms, 2048ms, 5120ms, 10240ms, 1min, 6min, 12min, 30min, ..., 20480ms, 40960ms, extended) | The codepoint 120ms, 240ms, 480ms, 1024ms, 2048ms, 1min, 6min, 12min, and 30min are not applicable. | YES | reject | +| Positioning Measurement Quantities | | 1 | | | YES | reject | +| >Positioning Measurement Quantities Item | | 1.. | | | EACH | | +| >>Positioning Measurement Type | M | | ENUMERATED (gNB RX-TX, UL-SRS-RSRP, UL AoA, UL RTOA, ..., Multiple UL AoA, UL SRS-RSRPP) | | - | - | +| >>Timing Reporting Granularity Factor | O | | INTEGER (0..5) | TS 38.133 [38] | - | | +| SFN Initialisation Time | O | | Relative Time 1900 9.3.1.183 | If this IE is not present, the TRP may assume that the value is same as its own SFN initialisation time. | YES | ignore | +| SRS Configuration | O | | 9.3.1.192 | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------|--------------------|-------|-------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Measurement Beam Information Request | O | | ENUMERATED (true, ...) | This IE is ignored when the Measurement characteristics Request Indicator IE is included. | YES | ignore | +| System Frame Number | O | | INTEGER(0..1023) | | YES | ignore | +| Slot Number | O | | INTEGER(0..79) | | YES | ignore | +| Measurement Periodicity Extended | C-
ifMeasPerExt | | ENUMERATED (160ms, 320ms, 1280ms, 2560ms, 61440ms, 81920ms, 368640ms, 737280ms, 1843200ms, ...) | | YES | reject | +| Response Time | O | | 9.3.1.242 | This IE is ignored when the Positioning Report Characteristics IE is set to "Periodic". | YES | ignore | +| Measurement Characteristics Request Indicator | O | | 9.3.1.254 | | YES | ignore | +| Measurement Time Occasion | O | | ENUMERATED (o1, o4,...) | | YES | ignore | +| Positioning Measurement Amount | O | | ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64) | This IE is ignored if the Positioning Report Characteristics IE is set to 'OnDemand'. Value 0 represents an infinite number of periodic reporting. | YES | ignore | + +| Range bound | Explanation | +|-----------------|----------------------------------------------------------------------------------------------------------| +| maxnoofPosMeas | Maximum no. of measured quantities that can be configured and reported with one message. Value is 16384. | +| maxnoofMeasTRPs | Maximum no. of TRPs that can be included within one measurement message. Value is 64. | + +| Condition | Explanation | +|---------------------------------|---------------------------------------------------------------------------------------------------------------| +| ifReportCharacteristicsPeriodic | This IE shall be present if the Positioning Report Characteristics IE is set to the value "Periodic". | +| ifMeasPerExt | This IE shall be present if the Positioning Measurement Periodicity IE is set to the value "extended". | + +## 9.2.12.4 POSITIONING MEASUREMENT RESPONSE + +This message is sent by the gNB-DU to report positioning measurements for the target UE. + +Direction: gNB-DU → gNB-CU. + +| 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 | +| LMF Measurement ID | M | | INTEGER
(1..65536, ...) | | YES | reject | +| RAN Measurement ID | M | | INTEGER
(1..65536, ...) | | YES | reject | +| Positioning Measurement Result List | | 0..1 | | | YES | reject | +| >Positioning Measurement Result List Item | | 1.. | | | - | | +| >>Positioning Measurement Result | M | | 9.3.1.166 | | - | - | +| >>TRP ID | M | | 9.3.1.197 | | - | | +| >>NR CGI | O | | 9.3.1.12 | The Cell ID of the TRP identified by the TRP ID IE. | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +| Range bound | Explanation | +|-----------------|---------------------------------------------------------------------------------------| +| maxnoofMeasTRPs | Maximum no. of TRP measurements that can be included within one message. Value is 64. | + +## 9.2.12.5 POSITIONING MEASUREMENT FAILURE + +This message is sent by the gNB-DU to report measurement failure. + +Direction: gNB-DU → gNB-CU. + +| 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 | +| LMF Measurement ID | M | | INTEGER
(1..65536, ...) | | YES | reject | +| RAN Measurement ID | M | | INTEGER
(1..65536, ...) | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.12.6 POSITIONING MEASUREMENT REPORT + +This message is sent by the gNB-DU to report positioning measurements for the target UE. + +Direction: gNB-DU → gNB-CU. + +| 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.23 | | YES | reject | +| LMF Measurement ID | M | | INTEGER (1..65536, ...) | | YES | reject | +| RAN Measurement ID | M | | INTEGER (1..65536, ...) | | YES | reject | +| Positioning Measurement Result List | | 1 | | | YES | reject | +| > Positioning Measurement Result List Item | | 1.. | | | EACH | | +| >>Positioning Measurement Result | M | | 9.3.1.166 | | - | - | +| >>TRP ID | M | | 9.3.1.197 | | - | - | +| >>NR CGI | O | | 9.3.1.12 | The Cell ID of the TRP identified by the TRP ID IE. | YES | ignore | + +| Range bound | Explanation | +|-----------------|---------------------------------------------------------------------------------------| +| maxnoofMeasTRPs | Maximum no. of TRP measurements that can be included within one message. Value is 64. | + +## 9.2.12.7 POSITIONING MEASUREMENT ABORT + +This message is sent by the gNB-CU to request the gNB-DU to abort a positioning measurement. + +Direction: gNB-CU → gNB-DU. + +| 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.23 | | YES | reject | +| LMF Measurement ID | M | | INTEGER (1..65536,...) | | YES | reject | +| RAN Measurement ID | M | | INTEGER (1..65536,...) | | YES | reject | + +## 9.2.12.8 POSITIONING MEASUREMENT FAILURE INDICATION + +This message is sent by the gNB-DU to indicate that the previously requested positioning measurements can no longer be reported. + +Direction: gNB-DU → gNB-CU. + +| 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.23 | | YES | reject | +| LMF Measurement ID | M | | INTEGER (1..65536,...) | | YES | reject | +| RAN Measurement ID | M | | INTEGER (1..65536,...) | | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Cause | M | | 9.3.1.2 | | YES | ignore | + +## 9.2.12.9 POSITIONING MEASUREMENT UPDATE + +This message is sent by the gNB-CU to update a previously configured measurement. + +Direction: gNB-CU → gNB-DU. + +| 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.23 | | YES | reject | +| LMF Measurement ID | M | | INTEGER
(1..65536,...) | | YES | reject | +| RAN Measurement ID | M | | INTEGER
(1..65536,...) | | YES | reject | +| SRS Configuration | O | | 9.3.1.192 | | YES | ignore | +| TRP Measurement Update List | | 0..1 | | | YES | reject | +| >TRP Measurement Update Item | | 1.. | | | EACH | reject | +| >>TRP ID | M | | 9.3.1.197 | | - | | +| >>AoA Search Window Information | O | | UL-AoA Assistance Information
9.3.1.238 | | - | | +| >>Number of TRP Rx TEGs | O | | ENUMERATED
(2, 3, 4, 6, 8, ...) | | YES | ignore | +| >>Number of TRP RxTx TEGs | O | | ENUMERATED
(2, 3, 4, 6, 8, ...) | | YES | ignore | +| Measurement Characteristics Request Indicator | O | | 9.3.1.254 | | YES | ignore | +| Measurement Time Occasion | O | | ENUMERATED
(o1, o4, ...) | | YES | ignore | + +| Range bound | Explanation | +|-----------------|---------------------------------------------------------------------------| +| maxnoofMeasTRPs | Maximum no. of TRPs that can be included within one message. Value is 64. | + +## 9.2.12.10 TRP INFORMATION REQUEST + +This message is sent by a gNB-CU to request information for TRPs hosted by a gNB-DU. + +Direction: gNB-CU → gNB-DU. + +| 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 | + +| | | | | | | | +|------------------------------------|---|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|------|--------| +| TRP list | | 0..1 | | | YES | ignore | +| > TRP list Item | | 1.. | | | EACH | ignore | +| >>TRP ID | M | | 9.3.1.197 | | - | | +| TRP Information Type List | | 1 | | | YES | reject | +| > TRP Information Type Item | | 1 .. | | | EACH | reject | +| >>TRP Information Type Item | M | | ENUMERATED (nr pci, ng-ran cgi, nr arfcn, prs config, ssb config, sfn init time, spatial direction info, geo-coordinates, ..., trp type, on-demand prs, trp Tx teg, beam antenna info, mobile TRP location info) | | - | | + +| Range bound | Explanation | +|---------------------|-------------------------------------------------------------------------------------------------------| +| maxnoofTRPInfoTypes | Maximum no of TRP information types that can be requested and reported with one message. Value is 64. | +| maxnoofTRPs | Maximum no. of TRPs in a gNB. Value is 65535. | + +## 9.2.12.11 TRP INFORMATION RESPONSE + +This message is sent by a gNB-DU to convey TRP information to a gNB-CU. + +Direction: gNB-DU → gNB-CU. + +| 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 | +| TRP Information List | | 1 | | | YES | ignore | +| > TRP Information Item | | 1 .. | | | EACH | ignore | +| >>TRP Information | M | | 9.3.1.176 | | - | | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +| Range bound | Explanation | +|-------------|--------------------------------------------------| +| maxnoofTRPs | Maximum no. of TRPs in a gNB-DU. Value is 65535. | + +## 9.2.12.12 TRP INFORMATION FAILURE + +This message is sent by a gNB-DU node to indicate that the requested TRP information cannot be provided to a gNB-CU. + +Direction: gNB-DU → gNB-CU. + +| 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 | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.12.13 POSITIONING INFORMATION REQUEST + +This message is sent by the gNB-CU to indicate to the gNB-DU the need to configure the UE to transmit SRS signals for uplink positioning measurement and also to retrieve the SRS configuration from the gNB-DU. + +Direction: gNB-CU → gNB-DU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| Requested SRS Transmission Characteristics | O | | 9.3.1.175 | | YES | ignore | +| UE Reporting Information | O | | 9.3.1.255 | | YES | ignore | +| SRS Positioning INACTIVE Query Indication | O | | ENUMERATED (true, ...) | Applicable only if the Requested SRS Transmission Characteristics IE is present | YES | ignore | + +## 9.2.12.14 POSITIONING INFORMATION RESPONSE + +This message is sent by the gNB-DU to provide the configured SRS information to the gNB-CU. + +Direction: gNB-DU → gNB-CU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| SRS Configuration | O | | 9.3.1.192 | | YES | ignore | +| SFN Initialisation Time | O | | Relative Time 1900
9.3.1.183 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| SRS-PosRRC-InactiveConfig | O | | OCTET STRING | Includes the SRS-PosRRC-InactiveConfig IE as defined in TS 38.331 [8] | YES | ignore | + +## 9.2.12.15 POSITIONING INFORMATION FAILURE + +This message is sent by the gNB-DU to indicate that no SRS transmissions could be configured for the UE for uplink positioning measurement. + +Direction: gNB-DU → gNB-CU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP 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.12.16 POSITIONING ACTIVATION REQUEST + +This message is sent by the gNB-CU to cause the gNB-DU to activate/trigger UL SRS transmission by the UE. + +Direction: gNB-CU → gNB-DU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| CHOICE SRS type | M | | | | YES | reject | +| >Semi-persistent | | | | | | | +| >>SRS Resource Set ID | M | | 9.3.1.180 | | - | - | +| >>SRS Spatial Relation | O | | Spatial Relation Information 9.3.1.181 | This IE is ignored if the Spatial Relation Information per SRS Resource IE is present. | - | - | +| >>Spatial Relation Information per SRS Resource | O | | 9.3.1.210 | | YES | ignore | +| >Aperiodic | | | | | | | +| >>Aperiodic | M | | ENUMERATED (true, ...) | | - | - | +| >>SRS Resource Trigger | O | | 9.3.1.182 | | - | - | +| Activation Time | O | | Relative Time 1900 9.3.1.183 | Indicates the start time when the SRS activation is requested | YES | ignore | + +## 9.2.12.17 POSITIONING ACTIVATION RESPONSE + +This message is sent by the gNB-DU to confirm successful UL SRS activation in the UE. + +Direction: gNB-DU → gNB-CU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| System Frame Number | O | | INTEGER(0..1023) | | YES | ignore | +| Slot Number | O | | INTEGER(0..79) | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.12.18 POSITIONING ACTIVATION FAILURE + +This message is sent by the gNB-DU to indicate that activation of UL SRS transmission in the UE was unsuccessful. + +Direction: gNB-DU → gNB-CU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP 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.12.19 POSITIONING DEACTIVATION + +This message is sent by the gNB-CU to cause the NG RAN node to deactivate UL SRS transmission or release all the transmission by the UE. + +Direction: gNB-CU → gNB-DU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| CHOICE Abort Transmission | M | | | | YES | ignore | +| > SRS Resource Set ID deactivation | | | | | | | +| >>SRS Resource Set ID | M | | 9.3.1.180 | | - | | +| > Release ALL | | | NULL | | | | + +## 9.2.12.20 E-CID MEASUREMENT INITIATION REQUEST + +This message is sent by gNB-CU to initiate E-CID measurements. + +Direction: gNB-CU → gNB-DU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------|---------------------------------------------------------------------------------|------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| LMF UE Measurement ID | M | | INTEGER (1..256, ...) | | YES | reject | +| RAN UE Measurement ID | M | | INTEGER (1..256, ...) | | YES | reject | +| E-CID Report Characteristics | M | | ENUMERATED (OnDemand, Periodic, ...) | | YES | reject | +| E-CID Measurement Periodicity | C-
ifReportCh
aracteristi
csPeriodic | | ENUMERATED (120ms, 240ms, 480ms, 640ms, 1024ms, 2048ms, 5120ms, 10240ms, 1min, 6min, 12min, 30min, ..., 20480ms, 40960ms, extended) | The codepoint "extended" is not applicable.

This IE is not applicable to NR Angle of Arrival. | YES | reject | +| E-CID Measurement Quantities | | 1 ..
MeasE-
CID> | | | EACH | reject | +| >E-CID Measurement Quantities Item | M | | ENUMERATED (Default, NR Angle of Arrival, ..., NR Timing Advance) | If "Default" is the only requested measurement quantity, it indicates that the Measured Results List IE need not be included in response or reporting messages. | - | | +| Measurement Periodicity NR-AoA | C-
ifReportCh
aracteristi
csPeriodic
AndMeas
QuantityIt
emAoA | | ENUMERATED (160ms, 320ms, 640ms, 1280ms, 2560ms, 5120ms, 10240ms, 20480ms, 40960ms, 61440ms, 81920ms, 368640ms, 737280ms, 1843200ms, ...) | | YES | reject | + +| Range bound | Explanation | +|------------------|-------------------------------------------------------------------------------------------------------------| +| maxnoofMeasE-CID | Maximum no. of E-CID measured quantities that can be configured and reported with one message. Value is 64. | + +| Condition | Explanation | +|-------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ifReportCharacteristicsPeriodic | This IE shall be present if the E-CID Report Characteristics IE is set to the value "Periodic". | +| ifReportCharacteristicsPeriodicAndMeasQuantityItemAoA | This IE shall be present if the E-CID Report Characteristics IE is set to the value "Periodic" and the E-CID Measurement Quantities Item IE is set to the value "NR Angle of Arrival". | + +## 9.2.12.21 E-CID MEASUREMENT INITIATION RESPONSE + +This message is sent by gNB-DU to indicate that the requested E-CID measurement is successfully initiated. + +Direction: gNB-DU → gNB-CU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| LMF UE Measurement ID | M | | INTEGER (1..256, ...) | | YES | reject | +| RAN UE Measurement ID | M | | INTEGER (1..256, ...) | | YES | reject | +| E-CID Measurement Result | O | | 9.3.1.199 | | YES | ignore | +| Cell Portion ID | O | | 9.3.1.200 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.12.22 E-CID MEASUREMENT INITIATION FAILURE + +This message is sent by gNB-DU to indicate that the requested E-CID measurement cannot be initiated. + +Direction: gNB-DU → gNB-CU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| LMF UE Measurement ID | M | | INTEGER (1..256, ...) | | YES | reject | +| RAN UE Measurement ID | M | | INTEGER (1..256, ...) | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.12.23 E-CID MEASUREMENT FAILURE INDICATION + +This message is sent by gNB-DU to indicate that the previously requested E-CID measurement can no longer be reported. + +Direction: gNB-DU → gNB-CU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| LMF UE Measurement ID | M | | INTEGER (1..256, ...) | | YES | reject | +| RAN UE Measurement ID | M | | INTEGER (1..256, ...) | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +## 9.2.12.24 E-CID MEASUREMENT REPORT + +This message is sent by gNB-DU to report the results of the requested E-CID measurement. + +Direction: gNB-DU → gNB-CU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| LMF UE Measurement ID | M | | INTEGER (1..256, ...) | | YES | reject | +| RAN UE Measurement ID | M | | INTEGER (1..256, ...) | | YES | reject | +| E-CID Measurement Result | M | | 9.3.1.199 | | YES | ignore | +| Cell Portion ID | O | | 9.3.1.200 | | YES | ignore | + +## 9.2.12.25 E-CID MEASUREMENT TERMINATION COMMAND + +This message is sent by the gNB-CU to terminate the requested E-CID measurement. + +Direction: gNB-CU → gNB-DU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| LMF UE Measurement ID | M | | INTEGER (1..256, ...) | | YES | reject | +| RAN UE Measurement ID | M | | INTEGER (1..256, ...) | | YES | reject | + +## 9.2.12.26 POSITIONING INFORMATION UPDATE + +This message is sent by the gNB-DU to indicate that a change in the SRS configuration has occurred. + +Direction: gNB-DU → gNB-CU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| SRS configuration | O | | 9.3.1.192 | | YES | ignore | + +| | | | | | | | +|-------------------------|---|--|------------------------------------|--|-----|--------| +| SFN Initialisation Time | O | | Relative Time
1900
9.3.1.183 | | YES | ignore | +|-------------------------|---|--|------------------------------------|--|-----|--------| + +## 9.2.12.27 PRS CONFIGURATION REQUEST + +This message is sent by a gNB-CU to request a gNB-DU to configure or update PRS transmissions. + +Direction: gNB-CU → gNB-DU. + +| 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 | +| PRS Configuration Request Type | M | | ENUMERATED
(configure, off, ...) | | YES | reject | +| PRS TRP List | | 1 | | | YES | ignore | +| >PRS TRP Item | | 1 ..
| | | EACH | ignore | +| >>TRP ID | M | | 9.3.1.197 | | - | | +| >>Requested DL PRS Transmission Characteristics | C-ifConf | | 9.3.1.235 | | - | | +| >>PRS Transmission Off Information | C-ifOff | | 9.3.1.237 | | - | | + +| Range bound | Explanation | +|-------------|------------------------------------------------| +| maxnoofTRPs | Maximum no. of TRPs in a gNB-DU Value is 65535 | + +| Condition | Explanation | +|-----------|-----------------------------------------------------------------------------------------------------------| +| ifConf | This IE shall be present if the PRS Configuration Request Type IE is set to the value "configure". | +| ifOff | This IE shall be present if the PRS Configuration Request Type IE is set to the value "off". | + +## 9.2.12.28 PRS CONFIGURATION RESPONSE + +This message is sent by a gNB-DU to acknowledge configuring or updating the PRS transmissions. + +Direction: gNB-DU → gNB-CU. + +| 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 | +| PRS Transmission TRP List | | 0..1 | | | YES | ignore | +| >PRS Transmission TRP Item | | 1 ..
| | | EACH | ignore | +| >>TRP ID | M | | 9.3.1.197 | | - | | +| >>PRS Configuration | M | | 9.3.1.117 | | - | | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +| Range bound | Explanation | +|-------------|-------------------------------------------------| +| maxnoofTRPs | Maximum no. of TRPs in a gNB-DU Value is 65535. | + +### 9.2.12.29 PRS CONFIGURATION FAILURE + +This message is sent by the gNB-DU to indicate that it cannot configure any PRS transmission. + +Direction: gNB-DU → gNB-CU. + +| 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 | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.12.30 MEASUREMENT PRECONFIGURATION REQUIRED + +This message is sent by a gNB-CU to provide the PRS configuration information of multiple TRPs to a gNB-DU and request to configure measurement gap or PRS processing window of the UE. + +Direction: gNB-CU → gNB-DU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| TRP PRS Information List | | 1 | | | YES | ignore | +| >TRP PRS Information Item | | 1 .. | | | EACH | ignore | +| >>TRP ID | M | | 9.3.1.197 | | - | | +| >>NR PCI | M | | INTEGER (0..1007) | | - | | +| >>NR CGI | O | | 9.3.1.12 | | - | | +| >>PRS Configuration | M | | 9.3.1.177 | | - | | + +| Range bound | Explanation | +|-------------|----------------------------------------------------------------| +| maxnoofTRPs | Maximum no. of TRPs for on-demand PRS in a gNB-DU Value is 256 | + +### 9.2.12.31 MEASUREMENT PRECONFIGURATION CONFIRM + +This message is sent by an gNB-DU to gNB-CU to confirm successful configuration of measurement gap or PRS processing window of the UE. + +Direction: gNB-DU → gNB-CU. + +| IE/Group Name | Presence | Range | IE type and | Semantics | Criticality | Assigned | +|---------------|----------|-------|-------------|-----------|-------------|----------| +|---------------|----------|-------|-------------|-----------|-------------|----------| + +| | | | reference | description | | Criticality | +|-----------------------------------|---|------|--------------|-------------------------------------------------------------------------------------|-----|-------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| gNB-CU UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| PosMeasGapPreConfigList | | 0..1 | | | YES | ignore | +| >PosMeasGapPreConfigToAddModList | O | | OCTET STRING | Includes the PosMeasGapPreConfigToAddModList IE as defined in TS 38.331 [8] | YES | Ignore | +| >PosMeasGapPreConfigToReleaseList | O | | OCTET STRING | Includes the PosMeasGapPreConfigToReleaseList IE as defined in TS 38.331 [8] | YES | Ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.12.32 MEASUREMENT PRECONFIGURATION REFUSE + +This message is sent by gNB-DU to indicate configuration of measurement gap or PRS processing window of the UE was unsuccessful. + +Direction: gNB-DU → gNB-CU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP 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.12.33 MEASUREMENT ACTIVATION + +This message is sent by the gNB-CU to request the gNB-DU to activate or deactivate the preconfigured measurement gap or PRS processing window for the UE. + +Direction: gNB-CU → gNB-DU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| Request Type | M | | ENUMERATED (activate, deactivate, ...) | | YES | reject | +| PRS Measurement Info List | | 0..1 | | | YES | ignore | +| >PRS Measurement Info Item | | 1 .. | | | - | | +| >>Point A | M | | INTEGER (0..3279165) | | - | | +| >>MeasPRS | M | | ENUMERATED | Measurement gap | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------|----------|-------|-------------------------------------------------------------------|----------------------------------------------|-------------|----------------------| +| Periodicity | | | (ms20, ms40, ms80, ms160, ...) | periodicity in units of ms | | | +| >>MeasPRS Offset | M | | INTEGER (0..159, ...) | Measurement gap offset in units of subframes | - | | +| >>Measurement PRS Length | M | | ENUMERATED {ms1dot5, ms3, ms3dot5, ms4, ms5dot5, ms6, ms10, ms20} | | - | | + +| Range bound | Explanation | +|---------------|---------------------------------------------| +| maxFreqLayers | Maximum no. of frequency layers. Value is 4 | + +## 9.2.12.34 POSITIONING SYSTEM INFORMATION DELIVERY COMMAND + +This message is sent by the gNB-CU and is used to request the gNB-DU to broadcast the indicated positioning SI message. + +Direction: gNB-CU → gNB-DU + +| 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.23 | | YES | reject | +| NR CGI | M | | 9.3.1.12 | NR cell identifier | YES | reject | +| PosSIType List | M | | 9.3.1.278 | | YES | reject | +| Confirmed UE ID | M | | gNB-DU UE F1AP ID 9.3.1.5 | | YES | reject | + +## 9.2.13 Broadcast Context Management messages + +### 9.2.13.1 BROADCAST CONTEXT SETUP REQUEST + +This message is sent by the gNB-CU to request the setup of an MBS session context for a broadcast session, and establish an MBS-associated logical F1-connection. + +Direction: gNB-CU → gNB-DU. + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| MBS Session ID | M | | 9.3.1.218 | | YES | reject | +| MBS Service Area | O | | 9.3.1.222 | | YES | reject | +| MBS CU to DU RRC Information | M | | 9.3.1.225 | | YES | reject | +| S-NSSAI | M | | 9.3.1.38 | | YES | reject | +| Broadcast MRB To Be Setup List | | 1 | | | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|-----------------------------|-----------------------------------------|------------------------------------------------------------------------------------|-------------|----------------------| +| >Broadcast MRB to Be Setup Item IEs | | 1 .. | | | EACH | reject | +| >>MRB ID | M | | MRB ID 9.3.1.224 | | - | | +| >>MRB QoS Information | M | | QoS Flow Level QoS Parameters 9.3.1.45 | | - | | +| >>MBS QoS Flows Mapped to MRB Item | | 1 .. | | | - | | +| >>>MBS QoS Flow Identifier | M | | QoS Flow Identifier 9.3.1.63 | | - | | +| >>>MBS QoS Flow Level QoS Parameters | M | | QoS Flow Level QoS Parameters 9.3.1.45 | | - | | +| >>BC Bearer Context F1-U TNL Info at CU | M | | BC Bearer Context F1-U TNL Info 9.3.2.7 | gNB-CU endpoint(s) of the F1 transport bearer(s). For delivery of F1-U PDU Type 1. | - | | +| Supported UE Type List | O | | 9.3.1.290 | | YES | ignore | +| Associated Session ID | O | | 9.3.1.309 | | YES | ignore | + +| Range bound | Explanation | +|---------------------------|--------------------------------------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRB allowed to be setup for one MBS Session, the maximum value is 32. | +| maxnoofMBSQoSFlows | Maximum no. of flows allowed to be mapped to one MRB, the maximum value is 64. | + +## 9.2.13.2 BROADCAST CONTEXT SETUP RESPONSE + +This message is sent by the gNB-DU to confirm the setup of a broadcast context. + +Direction: gNB-DU → gNB-CU. + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.220 | | YES | reject | +| Broadcast MRB Setup List | | 1 | | | YES | reject | +| >Broadcast MRB Setup Item IEs | | 1 .. | | | EACH | reject | +| >>MRB ID | M | | MRB ID 9.3.1.224 | | - | | +| >>BC Bearer Context | M | | BC Bearer | gNB-DU | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------------|----------|---------------------|-------------------------------|-----------------------------------------------------------------------|-------------|----------------------| +| F1-U TNL Info at DU | | | Context F1-U TNL Info 9.3.2.7 | endpoint(s) of the F1-U transport bearer(s). For delivery of DL PDUs. | | | +| Broadcast MRB Failed To Be Setup List | | 0..1 | | | YES | ignore | +| >Broadcast MRB Failed To Be Setup Item IEs | | 1 .. | | | EACH | ignore | +| >>MRB ID | M | | MRB ID 9.3.1.224 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| Broadcast Area Scope | O | | 9.3.1.287 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| F1-U Tunnel Not Established | O | | ENUMERATED (true, ...) | | YES | ignore | + +| Range bound | Explanation | +|--------------------|--------------------------------------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRB allowed to be setup for one MBS Session, the maximum value is 32. | + +### 9.2.13.3 BROADCAST CONTEXT SETUP FAILURE + +This message is sent by the gNB-DU to indicate that the setup of the broadcast context was unsuccessful. + +Direction: gNB-DU → gNB-CU + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | O | | 9.3.1.220 | | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.13.4 BROADCAST CONTEXT RELEASE COMMAND + +This message is sent by the gNB-CU to request the gNB-DU to release the broadcast context for a given broadcast service. + +Direction: gNB-CU → gNB-DU + +| 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 MBS F1AP ID | M | | gNB-CU MBS F1AP ID 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | gNB-DU MBS F1AP ID | | YES | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| | | | 9.3.1.220 | | | | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +### 9.2.13.5 BROADCAST CONTEXT RELEASE COMPLETE + +This message is sent by the gNB-DU to confirm the release of the broadcast context for a given broadcast service. + +Direction: gNB-DU → gNB-CU + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.220 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.13.5a BROADCAST CONTEXT RELEASE REQUEST + +This message is sent by the gNB-DU to request the gNB-CU to trigger the Broadcast Context Release procedure. + +Direction: gNB-DU → gNB-CU + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.220 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +### 9.2.13.6 BROADCAST CONTEXT MODIFICATION REQUEST + +This message is sent by the gNB-CU to request the gNB-DU to modify broadcast context information. + +Direction: gNB-CU → gNB-DU + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.220 | | YES | reject | +| MBS Service Area | O | | 9.3.1.222 | Overwrites any previously received MBS Service Area information | YES | reject | +| MBS CU to DU RRC Information | M | | 9.3.1.225 | | YES | reject | +| Broadcast MRB To Be Setup List | | 0..1 | | | YES | reject | +| >Broadcast MRB to Be Setup Item IEs | | 1 .. | | | EACH | reject | +| >>MRB ID | M | | MRB ID | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------|----------|-----------------------------|-----------------------------------------|--------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | 9.3.1.224 | | | | +| >>MRB QoS Information | M | | QoS Flow Level QoS Parameters 9.3.1.45 | | - | | +| >>MBS QoS Flows Mapped to MRB Item | | 1 .. | | | - | | +| >>>MBS QoS Flow Identifier | M | | QoS Flow Identifier 9.3.1.63 | | - | | +| >>>MBS QoS Flow Level QoS Parameters | M | | QoS Flow Level QoS Parameters 9.3.1.45 | | - | | +| >>BC Bearer Context F1-U TNL Info at CU | M | | BC Bearer Context F1-U TNL Info 9.3.2.7 | gNB-CU endpoint(s) of the F1 transport bearer(s). For delivery of F1-U PDU Type 1. | - | | +| Broadcast MRB To Be Modified List | | 0..1 | | | YES | reject | +| >Broadcast MRB to Be Modified Item IEs | | 1 .. | | | EACH | reject | +| >>MRB ID | M | | MRB ID 9.3.1.224 | | - | | +| >>MRB QoS Information | O | | QoS Flow Level QoS Parameters 9.3.1.45 | | - | | +| >>MBS QoS Flows Mapped to MRB Item | | 0 .. | | | - | | +| >>>MBS QoS Flow Identifier | M | | QoS Flow Identifier 9.3.1.63 | | - | | +| >>>MBS QoS Flow Level QoS Parameters | M | | QoS Flow Level QoS Parameters 9.3.1.45 | | - | | +| >>BC Bearer Context F1-U TNL Info at CU | O | | BC Bearer Context F1-U TNL Info 9.3.2.7 | Updated gNB-CU endpoint(s) of the F1 transport bearer(s). For delivery of F1-U PDU Type 1. | - | | +| Broadcast MRB To Be Released List | | 0..1 | | | YES | reject | +| >Broadcast MRB to Be Released Item IEs | | 1 .. | | | YES | reject | +| >>MRB ID | M | | MRB ID 9.3.1.224 | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Supported UE Type List | O | | 9.3.1.290 | | YES | ignore | + +| Range bound | Explanation | +|---------------------------|--------------------------------------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRB allowed to be setup for one MBS Session, the maximum value is 32. | +| maxnoofMBSQoSFlows | Maximum no. of flows allowed to be mapped to one MRB, the maximum value is 64. | + +## 9.2.13.7 BROADCAST CONTEXT MODIFICATION RESPONSE + +This message is sent by the gNB-DU to confirm the modification of a broadcast context. + +Direction: gNB-DU → gNB-CU. + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.220 | | YES | reject | +| Broadcast MRB Setup List | | 0..1 | | | YES | reject | +| > Broadcast MRB Setup Item IEs | | 1 ..
< maxnoof MRBs > | | | EACH | reject | +| >>MRB ID | M | | MRB ID
9.3.1.224 | | - | | +| >>BC Bearer Context F1-U TNL Info at DU | M | | BC Bearer Context F1-U TNL Info
9.3.2.7 | gNB-DU endpoint(s) of the F1-U transport bearer(s). For delivery of DL PDUs. | - | | +| Broadcast MRB Failed To Be Setup List | | 0..1 | | | YES | ignore | +| > Broadcast MRB Failed To Be Setup Item IEs | | 1 ..
< maxnoof MRBs > | | | EACH | ignore | +| >>MRB ID | M | | MRB ID
9.3.1.224 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| Broadcast MRB Modified List | | 0..1 | | | YES | reject | +| > Broadcast MRB Modified Item IEs | | 1 ..
< maxnoof MRBs > | | | EACH | reject | +| >>MRB ID | M | | MRB ID
9.3.1.224 | | - | | +| >>BC Bearer Context F1-U TNL Info at DU | O | | BC Bearer Context F1-U TNL Info
9.3.2.7 | Updated gNB-DU endpoint(s) of the F1-U transport bearer(s). For delivery of DL PDUs. | - | | +| Broadcast MRB Failed | | 0..1 | | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------|----------|---------------------|-----------------------|-----------------------|-------------|----------------------| +| To Be Modified List | | | | | | | +| >Broadcast MRB Failed To Be Modified Item IEs | | 1 .. | | | EACH | ignore | +| >>MRB ID | M | | MRB ID 9.3.1.224 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| Broadcast Area Scope | O | | 9.3.1.287 | | YES | ignore | + +| Range bound | Explanation | +|--------------------|--------------------------------------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRB allowed to be setup for one MBS Session, the maximum value is 32. | + +### 9.2.13.8 BROADCAST CONTEXT MODIFICATION FAILURE + +This message is sent by the gNB-DU to indicate a broadcast context modification failure. + +Direction: gNB-DU → gNB-CU + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.220 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.13.9 BROADCAST TRANSPORT RESOURCE REQUEST + +This message is sent by the gNB-DU to request the gNB-CU to establish the F1-U resources for the broadcast Session. + +Direction: gNB-DU → gNB-CU + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.220 | | YES | reject | + +## 9.2.14 Multicast Context Management messages + +### 9.2.14.1 MULTICAST GROUP PAGING + +This message is sent by the gNB-CU and is used to request the gNB-DU to multicast group page UEs. + +Direction: gNB-CU → gNB-DU + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|-----------------------------|------------------------|-------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| MBS Session ID | M | | 9.3.1.218 | | YES | reject | +| UE Identity List for Paging | | 0..1 | | | YES | ignore | +| >UE Identity for Paging Item | | 1.. | | | - | | +| >>UE Identity Index value | M | | 9.3.1.39 | | - | | +| >>Paging DRX | O | | 9.3.1.40 | | - | | +| MC Paging Cell List | | 0..1 | | | YES | ignore | +| >MC Paging Cell Item IEs | | 1 .. | | | EACH | ignore | +| >>NR CGI | M | | 9.3.1.12 | | - | | +| Indication for Multicast RRC_INACTIVE Reception | O | | ENUMERATED (true, ...) | Corresponds to information contained in the inactiveReception Allowed as specified in TS 38.331 [8]. | YES | ignore | + +| Range bound | Explanation | +|----------------------|-----------------------------------------------------------------| +| maxnoofUEIDforPaging | Maximum no. of UE ID for multicast group paging. Value is 4096. | +| maxnoofPagingCells | Maximum no. of paging cells, the maximum value is 512. | + +## 9.2.14.2 MULTICAST CONTEXT SETUP REQUEST + +This message is sent by the gNB-CU to request the setup of an MBS session context for a multicast session, and establish an MBS-associated logical F1-connection. + +Direction: gNB-CU → gNB-DU. + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| MBS Session ID | M | | 9.3.1.218 | | YES | reject | +| MBS Service Area | O | | 9.3.1.222 | | YES | reject | +| S-NSSAI | M | | 9.3.1.38 | | YES | reject | +| Multicast MRBs To Be Setup List | | 1 | | | YES | reject | +| >Multicast MRBs to Be Setup Item IEs | | 1 .. | | | EACH | reject | +| >>MRB ID | M | | MRB ID 9.3.1.224 | | - | | +| >>MRB QoS Information | M | | QoS Flow Level QoS Parameters 9.3.1.45 | | - | | +| >>MBS QoS Flows Mapped to MRB | | 1 .. Item | | MBSQoS Flows> | | | | | +| >>>MBS QoS Flow Identifier | M | | QoS Flow Identifier 9.3.1.63 | | - | | +| >>>MBS QoS Flow Level QoS Parameters | M | | QoS Flow Level QoS Parameters 9.3.1.45 | | - | | +| >>DL PDCP SN Length | M | | ENUMERATED (12bits, 18bits, ...) | | - | | +| Multicast CU to DU RRC Information | O | | 9.3.1.310 | | YES | reject | +| MBS Multicast Session Reception State | O | | 9.3.1.317 | | YES | reject | + +| Range bound | Explanation | +|---------------------------|--------------------------------------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRB allowed to be setup for one MBS Session, the maximum value is 32. | +| maxnoofMBSQoSFlows | Maximum no. of flows allowed to be mapped to one MRB, the maximum value is 64. | + +### 9.2.14.3 MULTICAST CONTEXT SETUP RESPONSE + +This message is sent by the gNB-DU to confirm the setup of a multicast context. + +Direction: gNB-DU → gNB-CU. + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.220 | | YES | reject | +| Multicast MRB Setup List | | 1 | | | YES | reject | +| > Multicast MRB Setup Item IEs | | 1 .. <maxnoof MRBs> | | | EACH | Reject | +| >>MRB ID | M | | MRB ID 9.3.1.224 | | - | | +| Multicast MRB Failed To Be Setup List | | 0..1 | | | YES | ignore | +| > Multicast MRB Failed To Be Setup Item IEs | | 1 .. <maxnoof MRBs> | | | EACH | ignore | +| >>MRB ID | M | | MRB ID 9.3.1.224 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| Multicast DU to CU RRC Information | O | | 9.3.1.311 | | YES | reject | + +| Range bound | Explanation | +|--------------------|--------------------------------------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRB allowed to be setup for one MBS Session, the maximum value is 32. | + +#### 9.2.14.4 MULTICAST CONTEXT SETUP FAILURE + +This message is sent by the gNB-DU to indicate that the setup of the multicast context was unsuccessful. + +Direction: gNB-DU → gNB-CU + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | O | | 9.3.1.220 | | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +#### 9.2.14.5 MULTICAST CONTEXT RELEASE COMMAND + +This message is sent by the gNB-CU to request the gNB-DU to release the multicast context for a given multicast service. + +Direction: gNB-CU → gNB-DU + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.220 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +#### 9.2.14.6 MULTICAST CONTEXT RELEASE COMPLETE + +This message is sent by the gNB-DU to confirm the release of the multicast context for a given multicast service. + +Direction: gNB-DU → gNB-CU + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.220 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +#### 9.2.14.6a MULTICAST CONTEXT RELEASE REQUEST + +This message is sent by the gNB-DU to request the gNB-CU to trigger the Multicast Context Release procedure. + +Direction: gNB-DU → gNB-CU + +| 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 MBS F1AP ID | M | | 9.3.1.2.19 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.2.20 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +## 9.2.14.7 MULTICAST CONTEXT MODIFICATION REQUEST + +This message is sent by the gNB-CU to request the gNB-DU to modify multicast context information. + +Direction: gNB-CU → gNB-DU + +| 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 MBS F1AP ID | M | | 9.3.1.2.19 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.2.20 | | YES | reject | +| MBS Service Area | O | | 9.3.1.2.22 | | YES | reject | +| Multicast MRB To Be Setup List | | 0..1 | | | YES | reject | +| > Multicast MRB to Be Setup Item IEs | | 1 ..
MRBs> | | | EACH | reject | +| >>MRB ID | M | | 9.3.1.2.24 | | - | | +| >>MRB QoS Information | M | | QoS Flow Level
QoS Parameters
9.3.1.4.5 | | - | | +| >>> MBS QoS Flows Mapped to MRB Item | | 1 ..
MBSQoS
Flows> | | | - | | +| >>>MBS QoS Flow Identifier | M | | QoS Flow Identifier
9.3.1.6.3 | | - | | +| >>>MBS QoS Flow Level QoS Parameters | M | | QoS Flow Level
QoS Parameters
9.3.1.4.5 | | - | | +| >>DL PDCP SN Length | M | | ENUMERATED
(12bits,
18bits, ...) | | - | | +| Multicast MRB To Be Modified List | | 0..1 | | | YES | reject | +| > Multicast MRB to Be Modified Item IEs | | 1 ..
MRBs> | | | EACH | reject | +| >>MRB ID | M | | 9.3.1.2.24 | | - | | +| >>MRB QoS Information | O | | QoS Flow Level
QoS Parameters
9.3.1.4.5 | | - | | +| >>> MBS QoS Flows Mapped to MRB Item | | 0 ..
MBSQoS
Flows> | | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|------------------------|----------------------------------------------|-----------------------|-------------|----------------------| +| >>>MBS QoS Flow Identifier | M | | QoS Flow Identifier
9.3.1.63 | | - | | +| >>>MBS QoS Flow Level QoS Parameters | M | | QoS Flow Level
QoS Parameters
9.3.1.45 | | - | | +| >>DL PDCP SN Length | O | | ENUMERATED
(12bits, 18bits, ...) | | - | | +| Multicast MRB To Be Released List | | 0..1 | | | YES | reject | +| > Multicast MRB to Be Released Item IEs | | 1 ..
| | | YES | reject | +| >>MRB ID | M | | 9.3.1.224 | | - | | +| Multicast CU to DU RRC Information | O | | 9.3.1.310 | | YES | reject | +| MBS Multicast Session Reception State | O | | 9.3.1.317 | | YES | reject | + +| Range bound | Explanation | +|---------------------------|--------------------------------------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRB allowed to be setup for one MBS Session, the maximum value is 32. | +| maxnoofMBSQoSFlows | Maximum no. of flows allowed to be mapped to one MRB, the maximum value is 64. | + +## 9.2.14.8 MULTICAST CONTEXT MODIFICATION RESPONSE + +This message is sent by the gNB-DU to confirm the modification of a multicast context. + +Direction: gNB-DU → gNB-CU. + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.220 | | YES | reject | +| Multicast MRB Setup List | | 0..1 | | | YES | reject | +| > Multicast MRB Setup Item IEs | | 1 ..
| | | EACH | reject | +| >>MRB ID | M | | 9.3.1.224 | | - | | +| Multicast MRB Failed To Be Setup List | | 0..1 | | | YES | ignore | +| > Multicast MRB Failed To Be Setup Item IEs | | 1 ..
| | | EACH | ignore | +| >>MRB ID | M | | 9.3.1.224 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| Multicast MRB Modified List | | 0..1 | | | YES | reject | +| > Multicast MRB | | 1 .. | | | EACH | reject | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|---------------------|-----------------------|-----------------------|-------------|----------------------| +| Modified Item IEs | | | | | | | +| >>MRB ID | M | | 9.3.1.224 | | - | | +| Multicast MRB Failed To Be Modified List | | 0..1 | | | YES | ignore | +| >Multicast MRB Failed To Be Modified Item IEs | | 1 .. | | | EACH | ignore | +| >>MRB ID | M | | 9.3.1.224 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| Multicast DU to CU RRC Information | O | | 9.3.1.311 | | YES | reject | + +| Range bound | Explanation | +|-------------|--------------------------------------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRB allowed to be setup for one MBS Session, the maximum value is 32. | + +## 9.2.14.9 MULTICAST CONTEXT MODIFICATION FAILURE + +This message is sent by the gNB-DU to indicate a multicast context modification failure. + +Direction: gNB-DU → gNB-CU + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.220 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.14.10 MULTICAST DISTRIBUTION SETUP REQUEST + +This message is sent by the gNB-DU to request the setup of a Multicast F1-U Context. + +Direction: gNB-DU → gNB-CU. + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.220 | | YES | reject | +| MBS Multicast F1-U Context Descriptor | M | | 9.3.2.8 | | YES | reject | +| Multicast F1-U Context To Be Setup List | | 1 | | | YES | reject | +| >Multicast F1-U Context To Be Setup Item | | 1 .. | | | EACH | reject | +| >>MRB ID | M | | 9.3.1.224 | | - | | +| >>MRB F1-U TNL | M | | UP Transport | gNB-DU endpoint | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------|-----------------------|-------|---------------------------|-------------------------------|-------------|----------------------| +| Info at DU | | | Layer Information 9.3.2.1 | of the F1-U transport bearer. | | | +| >>MRB Progress Information | C-
ifPTPForwarding | | 9.3.2.12 | | - | | + +| Range bound | Explanation | +|--------------------|--------------------------------------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRB allowed to be setup for one MBS Session, the maximum value is 32. | +| maxnoofMBSQoSFlows | Maximum no. of flows allowed to be mapped to one MRB, the maximum value is 64. | + +| Condition | Explanation | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| ifPTPForwarding | This IE shall be present if the MC F1-U Context usage IE in the MBS Multicast F1-U Context Descriptor IE is set to "ptp forwarding". | + +## 9.2.14.11 MULTICAST DISTRIBUTION SETUP RESPONSE + +This message is sent by the gNB-CU to confirm the setup of a Multicast F1-U Context. + +Direction: gNB-CU → gNB-DU. + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.220 | | YES | reject | +| MBS Multicast F1-U Context Descriptor | M | | 9.3.2.8 | | YES | reject | +| Multicast F1-U Context Setup List | | 1 | | | YES | reject | +| >Multicast F1-U Context Setup Item IEs | | 1 ..
| | | EACH | reject | +| >>MRB ID | M | | 9.3.1.224 | | - | | +| >>MRB F1-U TNL Info at CU | M | | UP Transport Layer Information 9.3.2.1 | gNB-CU endpoint of the F1-U transport bearer. | - | | +| Multicast F1-U Context Failed To Be Setup List | | 0..1 | | | YES | ignore | +| >Multicast F1-U Context Failed To Be Setup Item IEs | | 1 ..
| | | EACH | ignore | +| >>MRB ID | M | | 9.3.1.224 | | - | | +| >>Cause | O | | 9.3.1.2 | | - | | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | +| Multicast F1-U Context Reference CU | M | | 9.3.2.13 | | YES | reject | + +| Range bound | Explanation | +|--------------------|--------------------------------------------------------------------------------------| +| maxnoofMRBs | Maximum no. of MRB allowed to be setup for one MBS Session, the maximum value is 32. | + +#### 9.2.14.12 MULTICAST DISTRIBUTION SETUP FAILURE + +This message is sent by the gNB-DU to indicate that the setup of the Multicast F1-U Context was was unsuccessful. + +Direction: gNB-CU → gNB-DU + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | O | | 9.3.1.220 | | YES | ignore | +| MBS Multicast F1-U Context Descriptor | M | | 9.3.2.8 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +#### 9.2.14.13 MULTICAST DISTRIBUTION RELEASE COMMAND + +This message is sent by the gNB-DU to request the gNB-CU to release the Multicast F1-U Context for a given multicast MBS Session. + +Direction: gNB-DU → gNB-CU + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.220 | | YES | reject | +| MBS Multicast F1-U Context Descriptor | M | | 9.3.2.8 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +#### 9.2.14.14 MULTICAST DISTRIBUTION RELEASE COMPLETE + +This message is sent by the gNB-CU to confirm the release of the Multicast F1-U Context. + +Direction: gNB-CU → gNB-DU + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.220 | | YES | reject | +| MBS Multicast F1-U Context Descriptor | M | | 9.3.2.8 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +#### 9.2.14.15 MULTICAST CONTEXT NOTIFICATION INDICATION + +This message is sent by the gNB-DU to notify the gNB-CU about changes of the multicast context. + +Direction: gNB-DU → gNB-CU + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.220 | | YES | reject | +| Multicast DU to CU RRC Information | O | | 9.3.1.311 | | YES | reject | + +#### 9.2.14.16 MULTICAST CONTEXT NOTIFICATION CONFIRM + +This message is sent by the gNB-CU to notify the gNB-DU to confirm the execution of the requested functions. + +Direction: gNB-CU → gNB-DU + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.220 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +#### 9.2.14.17 MULTICAST CONTEXT NOTIFICATION REFUSE + +This message is sent by the gNB-CU to notify the gNB-DU that the execution of the requested functions was not successful. + +Direction: gNB-CU → gNB-DU + +| 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 MBS F1AP ID | M | | 9.3.1.219 | | YES | reject | +| gNB-DU MBS F1AP ID | M | | 9.3.1.220 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +#### 9.2.14.18 MULTICAST COMMON CONFIGURATION REQUEST + +This message is sent by the gNB-CU to request the gNB-DU to configure common items in the gNB-DU. + +Direction: gNB-CU → gNB-DU + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Multicast CU to DU Common RRC Information | O | | 9.3.1.314 | | YES | reject | + +#### 9.2.14.19 MULTICAST COMMON CONFIGURATION CONFIRM + +This message is sent by the gNB-DU to notify the gNB-CU to confirm the execution of the requested functions. + +Direction: gNB-DU → gNB-CU + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.14.20 MULTICAST COMMON CONFIGURATION REFUSE + +This message is sent by the gNB-DU to notify the gNB-CU that the execution of the requested functions was not successful. + +Direction: gNB-DU → gNB-CU + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.15 PDC Measurement Reporting messages + +### 9.2.15.1 PDC MEASUREMENT INITIATION REQUEST + +This message is sent by gNB-CU to initiate PDC measurements. + +Direction: gNB-CU → gNB-DU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| RAN UE PDC Measurement ID | M | | INTEGER (1..16, ...) | | YES | reject | +| PDC Report Type | M | | ENUMERATED (OnDemand, Periodic, ...) | | YES | reject | +| PDC Measurement Periodicity | C- ifReportTypePeriodic | | ENUMERATED (80ms, 120ms, 160ms, 240ms, 320ms, 480ms, 640ms, 1024ms, 1280ms, 2048ms, 2560ms, 5120ms, ...) | | YES | reject | +| PDC Measurement Quantities | | 1 .. | | | EACH | reject | +| >PDC Measurement Quantities Item | M | | ENUMERATED (NR PDC TADV, gNB RX- | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| | | | TX, ...) | | | | + +| Range bound | Explanation | +|--------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| maxnoMeasPDC | Maximum no. of PDC measured quantities that can be configured and reported with one message. Value is 16. Maximum is 1 in this release. | + +| Condition | Explanation | +|----------------------|------------------------------------------------------------------------------------| +| ifReportTypePeriodic | This IE shall be present if the PDC Report Type IE is set to the value "Periodic". | + +## 9.2.15.2 PDC MEASUREMENT INITIATION RESPONSE + +This message is sent by gNB-DU to indicate that the requested PDC measurement is successfully initiated. + +Direction: gNB-DU → gNB-CU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| RAN UE PDC Measurement ID | M | | INTEGER (1..16, ...) | | YES | reject | +| PDC Measurement Result | O | | 9.3.1.232 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.15.3 PDC MEASUREMENT INITIATION FAILURE + +This message is sent by gNB-DU to indicate that the requested PDC measurement cannot be initiated. + +Direction: gNB-DU → gNB-CU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| RAN UE PDC Measurement ID | M | | INTEGER (1..16, ...) | | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +## 9.2.15.4 PDC MEASUREMENT REPORT + +This message is sent by gNB-DU to report the results of the requested PDC measurement. + +Direction: gNB-DU → gNB-CU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| RAN UE PDC
Measurement ID | M | | INTEGER
(1..16, ...) | | YES | reject | +| PDC Measurement
Result | M | | 9.3.1.232 | | YES | ignore | + +### 9.2.15.5 PDC MEASUREMENT TERMINATION COMMAND + +This message is sent by the gNB-CU to request the gNB-DU to terminate an ongoing periodical PDC measurement. + +Direction: gNB-CU → gNB-DU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| RAN UE PDC
Measurement ID | M | | INTEGER
(1..16, ...) | | YES | ignore | + +### 9.2.15.6 PDC MEASUREMENT FAILURE INDICATION + +This message is sent by the gNB-DU to indicate that the previously requested PDC measurements can no longer be reported. + +Direction: gNB-DU → gNB-CU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| RAN UE PDC
Measurement ID | M | | INTEGER
(1..16, ...) | | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | + +## 9.2.16 QMC messages + +### 9.2.16.1 QOE INFORMATION TRANSFER + +This message is sent by a gNB-CU to a gNB-DU, to indicate information related to RAN visible QoE. + +Direction: gNB-CU → gNB-DU. + +| 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 UE F1AP ID | M | | 9.3.1.4 | | YES | reject | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | YES | reject | +| QoE Information List | | 0..1 | | | YES | ignore | +| >QoE Information
Item | | 1..ofQoEInfo | | | EACH | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------|----------|----------------------------------|-----------------------|--------------------------------------------------------|-------------|----------------------| +| | | rmation> | | | | | +| >>QoE Metrics | O | | 9.3.1.260 | | - | - | +| >>DRB List | | 0..1 | | | YES | ignore | +| >>>DRB List Item | | 1 .. <maxnoof DRBs> | | The List of DRBs corresponding to the QoE Information. | | | +| >>>>DRB ID | M | | 9.3.1.8 | | | | + +| Range bound | Explanation | +|-----------------------|---------------------------------------------------------------------| +| maxnoofQoEInformation | Maximum no. of QoE information for one UE, the maximum value is 16. | +| maxnoofDRBs | Maximum no. of DRB allowed towards one UE, the maximum value is 64. | + +## 9.2.16.2 QOE INFORMATION TRANSFER CONTROL + +This message is sent by a gNB-DU to the gNB-CU, to control the QoE information transfer. + +Direction: gNB-DU → gNB-CU + +| 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.23 | | YES | reject | +| CHOICE Deactivation Indication | O | | | | YES | ignore | +| > Per UE | | | | | | | +| >>Deactivation Indication List | | 1 | | | YES | ignore | +| >>>Deactivation Indication Item | | 1..<maxno ofUEsInQ MCTransf erControl Message> | | | - | | +| >>>> gNB-CU UE F1AP ID | M | | 9.3.1.4 | | - | | +| >>>>gNB-DU UE F1AP ID | M | | 9.3.1.5 | | - | | +| >Deactivate ALL | | | NULL | This choice indicates that RVQoE reporting pertaining to all the UEs served by the gNB-DU, should be deactivated. | | | + +| Range bound | Explanation | +|---------------------------------------|------------------------------------------------------------------------------------------------------| +| maxnoofUEsInQMCTransferControlMessage | Maximum no. of UEs for which QoE transfer control information is received, the maximum value is 512. | + +## 9.2.17 Timing Synchronisation Status Reporting Messages + +### 9.2.17.1 TIMING SYNCHRONISATION STATUS REQUEST + +This message is sent by the gNB-CU to request the gNB-DU to start or stop reporting of RAN timing synchronization status information. + +Direction: gNB-CU → gNB-DU + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|-------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | reject | +| RAN TSS Request Type | M | | ENUMERATED (start, stop, ...) | | YES | reject | + +### 9.2.17.2 TIMING SYNCHRONISATION STATUS RESPONSE + +This message is sent by the gNB-DU to confirm the request to start or stop reporting of RAN timing synchronization status information. + +Direction: gNB-DU → gNB-CU + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.17.3 TIMING SYNCHRONISATION STATUS FAILURE + +This message is sent by the gNB-DU to indicate that reporting of RAN timing synchronisation status information cannot be initiated. + +Direction: gNB-DU → gNB-CU + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| Cause | M | | 9.3.1.2 | | YES | ignore | +| Criticality Diagnostics | O | | 9.3.1.3 | | YES | ignore | + +### 9.2.17.4 TIMING SYNCHRONISATION STATUS REPORT + +This message is sent by the gNB-DU to report RAN timing synchronisation status information. + +Direction: gNB-DU → gNB-CU + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.3.1.1 | | YES | ignore | +| RAN Timing Synchronisation Status Information | M | | 9.3.1.298 | | 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 | | | | | +| >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 F1AP 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, RL failure-RLC,
Unknown or already allocated gNB-CU UE F1AP ID,
Unknown or already allocated gNB-DU UE F1AP ID,
Unknown or inconsistent pair of UE F1AP ID,
Interaction with other procedure,
Not supported QCI Value,
Action Desirable for Radio Reasons,
No Radio Resources Available,
Procedure cancelled, Normal Release, ..., Cell not available, RL failure-others, UE rejection,
Resources not available for the slice(s), AMF) | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| | | | initiated abnormal release, Release due to Pre-Emption, PLMN not served by the gNB-CU, Multiple DRB ID Instances, Unknown DRB ID, Multiple BH RLC CH ID Instances, Unknown BH RLC CH ID, CHO-CPC resources to be changed, NPN not supported, NPN access denied, gNB-CU Cell Capacity Exceeded, Report Characteristics Empty, Existing Measurement ID, Measurement Temporarily not Available, Measurement not Supported For The Object, Unknown BAP address, Unknown BAP routing ID, Insufficient UE Capabilities, SCG activation deactivation failure, SCG deactivation failure due to data transmission, Requested Item not Supported on Time, Unknown or already allocated gNB-CU MBS F1AP ID, Unknown or already allocated gNB-DU MBS F1AP ID, Unknown or inconsistent pair of MBS F1AP ID, Unknown or inconsistent MRB ID, TAT-SDT expiry, LTM command triggered, SSB not Available) | | +| >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, Unknown UP TNL information 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. | +| RL Failure-RLC | The action is due to an RL failure caused by exceeding the maximum number of ARQ retransmissions. | +| Unknown or already allocated gNB-CU UE F1AP ID | The action failed because the gNB-CU UE F1AP 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-DU UE F1AP ID | The action failed because the gNB-DU UE F1AP ID is either unknown, or (for a first message received at the gNB-DU) is known and already allocated to an existing context. | +| Unknown or inconsistent pair of UE F1AP ID | The action failed because both UE F1AP 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. | +| Not supported QCI Value | The action failed because the requested QCI is not supported. | + +| Radio Network Layer cause | Meaning | +|---------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Action Desirable for Radio Reasons | The reason for requesting the action is radio related. | +| No Radio Resources Available | The cell(s) in the requested node don't have sufficient radio resources available. | +| 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. | +| Cell Not Available | The action failed due to no cell available in the requested node. | +| RL Failure-others | The action is due to an RL failure caused by other radio link failures than exceeding the maximum number of ARQ retransmissions. | +| UE rejection | The action is due to gNB-CU's rejection of a UE access request. | +| Resources not available for the slice(s) | The requested resources are not available for the slice(s). | +| AMF initiated abnormal release | The release is triggered by an error in the AMF or in the NAS layer. | +| Release due to Pre-Emption | Release is initiated due to pre-emption. | +| PLMN not served by the gNB-CU | The PLMN indicated by the UE is not served by the gNB-CU. | +| 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. | +| Multiple BH RLC CH ID Instances | The action failed because multiple instances of the same BH RLC CH ID had been provided. This cause value is only applicable to IAB. | +| Unknown BH RLC CH ID | The action failed because the BH RLC CH ID is unknown. This cause value is only applicable to IAB. | +| CHO-CPC resources to be changed | The gNB-DU requires gNB-CU to replace, i.e. overwrite the configuration of indicated candidate target cell. | +| NPN not supported | The action fails because the indicated SNPN is not supported in the node. | +| NPN access denied | The action is due to rejection of a UE access request for NPN. | +| gNB-CU Cell Capacity Exceeded | The number of cells requested to be added was exceeding maximum cell capacity in the gNB-CU. | +| 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-DU 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. | +| Unknown BAP address | The action failed because the BAP address is unknown. This cause value is only applicable to IAB. | +| Unknown BAP routing ID | The action failed because the BAP routing ID is unknown. This cause value is only applicable to IAB. | +| Insufficient UE Capabilities | The setup can't proceed due to insufficient UE capabilities. | +| 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 failure due to ongoing or arriving data transmission. | +| Requested Item not Supported on Time | The gNB-DU is unable to provide the measurement results on time. | +| Unknown or already allocated gNB-CU MBS F1AP ID | The action failed because the gNB-CU MBS F1AP ID is either unknown, or (for a first message received at the gNB-CU) is known and already allocated to an existing context. | + +| Radio Network Layer cause | Meaning | +|-------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Unknown or already allocated gNB-DU MBS F1AP ID | The action failed because the gNB-DU MBS F1AP ID is either unknown, or (for a first message received at the gNB-DU) is known and already allocated to an existing context. | +| Unknown or inconsistent pair of MBS F1AP ID | The action failed because both MBS F1AP IDs are unknown, or are known but do not define a single MBS context. | +| Unknown or inconsistent MRB ID | The action failed because the MRB ID is unknown or inconsistent. | +| TAT-SDT expiry | The UE context release is requested from the gNB-DU due to the expiry of the Timing Alignment timer for CG-SDT. | +| LTM command triggered | The action failed because the LTM command has been triggered. | +| SSB not Available | The action failed due to no SSB available in the requested node. | + +| 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 only applicable to IAB. | +| Unknown UP TNL information for IAB | The action failed because the UP TNL information is unknown. This cause value is only applicable to IAB. | + +| 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 or Protocol. | + +### 9.3.1.3 Criticality Diagnostics + +The *Criticality Diagnostics* IE is sent by the gNB-DU or the gNB-CU when parts of a received message have not been comprehended or were missing, or if the message contained logical errors. When applicable, it contains information about which IEs were not comprehended or were missing. + +For further details on how to use the *Criticality Diagnostics* IE, (see clause 10). The conditions for inclusion of the *Transaction ID* IE are described in 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, successful outcome, unsuccessful outcome) | The Triggering 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). | +| Transaction ID | O | | 9.3.1.23 | | +| 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 UE F1AP ID + +The gNB-CU UE F1AP ID uniquely identifies the UE association over the F1 interface within the gNB-CU. + +NOTE: If F1-C signalling transport is shared among multiple interface instances, the value of the gNB-CU UE F1AP ID is allocated so that it can be associated with the corresponding F1-C interface instance. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------|----------|-------|-----------------------------------|-----------------------| +| gNB-CU UE F1AP ID | M | | INTEGER (0 .. 2 32 -1) | | + +### 9.3.1.5 gNB-DU UE F1AP ID + +The gNB-DU UE F1AP ID uniquely identifies the UE association over the F1 interface within the gNB-DU. + +NOTE: If F1-C signalling transport is shared among multiple interface instances, the value of the gNB-DU UE F1AP ID is allocated so that it can be associated with the corresponding F1-C interface instance. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------|----------|-------|-----------------------------------|-----------------------| +| gNB-DU UE F1AP ID | M | | INTEGER (0 .. 2 32 -1) | | + +### 9.3.1.6 RRC-Container + +This information element contains a gNB-CU→UE or a UE → gNB-CU message that is transferred without interpretation in the gNB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| RRC-Container | M | | OCTET STRING | | + +### 9.3.1.7 SRB ID + +This IE uniquely identifies a SRB for a UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------| +| SRB ID | M | | INTEGER (0..3, ...) | Corresponds to the identities of SRB as defined in TS 38.331 [8]. Value 0 indicates SRB0, value 1 indicates SRB1, etc. | + +### 9.3.1.8 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, ...) | Corresponds to the DRB-Identity defined in TS 38.331 [8]. | + +### 9.3.1.9 gNB-DU ID + +The gNB-DU ID uniquely identifies the 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.10 Served Cell Information + +This IE contains cell configuration information of a cell in the gNB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| NR CGI | M | | 9.3.1.12 | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------|----------|---------------------|---------------------------------------|-------------------------------------------------------------------------------|-------------|----------------------| +| NR PCI | M | | INTEGER (0..1007) | Physical Cell ID | - | | +| 5GS TAC | O | | 9.3.1.29 | 5GS Tracking Area Code | - | | +| Configured EPS TAC | O | | 9.3.1.29a | | - | | +| Served PLMNs | | 1.. | | Broadcast PLMNs in SIB 1 associated to the NR Cell Identity in the NR CG/IE | - | | +| >PLMN Identity | M | | 9.3.1.14 | | - | | +| >TAI Slice Support List | O | | Slice Support List 9.3.1.37 | Supported S-NSSAIs per PLMN or per SNPN. | YES | ignore | +| >NPN Support Information | O | | 9.3.1.156 | Supported NPNs per PLMN. | YES | reject | +| >Extended TAI Slice Support List | O | | Extended Slice Support List 9.3.1.165 | Additional Supported S-NSSAIs per PLMN or per SNPN. | YES | reject | +| >TAI NSAG Support List | O | | 9.3.1.273 | NSAG information associated with the slices per TAC, per PLMN or per SNPN. | YES | ignore | +| CHOICE NR-Mode-Info | M | | | | - | | +| >FDD | | | | | - | | +| >>FDD Info | | 1 | | | - | | +| >>>UL FreqInfo | M | | NR Frequency Info 9.3.1.17 | This IE is ignored if the Cell Direction IE is included and set to "dl-only". | - | | +| >>>DL FreqInfo | M | | NR Frequency Info 9.3.1.17 | This IE is ignored if the Cell Direction IE is included and set to "ul-only". | - | | +| >>>UL Transmission Bandwidth | M | | Transmission Bandwidth 9.3.1.15 | This IE is ignored if the Cell Direction IE is included and set to "dl-only". | - | | +| >>>DL Transmission Bandwidth | M | | Transmission Bandwidth 9.3.1.15 | This IE is ignored if the Cell Direction IE is included and set to "ul-only". | - | | +| >>>UL Carrier List | O | | NR Carrier List 9.3.1.137 | If included, the UL Transmission Bandwidth IE shall be ignored. | YES | ignore | +| >>>DL Carrier List | O | | NR Carrier List 9.3.1.137 | If included, the DL Transmission Bandwidth IE shall be ignored. | YES | ignore | +| >TDD | | | | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|----------------------------|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>TDD Info | | 1 | | | - | | +| >>>NR FreqInfo | M | | NR Frequency Info 9.3.1.17 | | - | | +| >>>Transmission Bandwidth | M | | Transmission Bandwidth 9.3.1.15 | | - | | +| >>>Intended TDD DL-UL Configuration | O | | 9.3.1.89 | | YES | ignore | +| >>>TDD UL-DL Configuration Common NR | O | | OCTET STRING | Includes the tdd-UL-DL-ConfigurationCommon contained in the ServingCellConfigCommon IE as defined in TS 38.331 [8] | YES | ignore | +| >>>Carrier List | O | | NR Carrier List 9.3.1.137 | If included, the Transmission Bandwidth IE shall be ignored. | YES | ignore | +| >NR-U | | | | | YES | ignore | +| >>NR-U Channel Info List | | 1.. | | | - | | +| >>>NR-U Channel Info Item | | | | | - | | +| >>>>NR-U Channel ID | M | | INTEGER (1..maxnoofNR-UChannelIDs, ...) |

Index to uniquely identify the part of the NR-U Channel Bandwidth consisting of a contiguous set of resource blocks (RBs) on which a channel access procedure is performed in shared spectrum.

Value 1 represents the first part of the NR-U Channel Bandwidth on which a channel access procedure is performed. Value 2 represents the second part of the NR-U Channel Bandwidth on which a channel access procedure is performed, and

| - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------|----------|----------------------------|-------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | so on. | | | +| >>>>NR-U ARFCN | M | | INTEGER (0..maxNRARFCN) | It represents the centre frequency of the NR-U Channel Bandwidth for NR bands restricted to operation with shared spectrum channel access, as defined in TS 37.213 [46]. Allowed values are specified in TS 38.101-1 [26] in Table 5.4.2.3-2, Table 5.4.2.3-3 and Table 5.4.2.3-4. | - | | +| >>>>NR-U Channel Bandwidth | M | | ENUMERATED (10MHz, 20MHz, 40MHz, 60 MHz, 80 MHz, ...) | | - | | +| Measurement Timing Configuration | M | | OCTET STRING | Includes the MeasurementTimingConfiguration inter-node message defined in TS 38.331 [8]. | - | | +| RANAC | O | | RAN Area Code 9.3.1.57 | | YES | ignore | +| Extended Served PLMNs List | | 0..1 | | This is included if more than 6 Served PLMNs is to be signalled. | YES | ignore | +| >Extended Served PLMNs Item | | 1.. | | | - | | +| >>PLMN Identity | M | | 9.3.1.14 | | - | | +| >>TAI Slice Support List | O | | Slice Support List 9.3.1.37 | Supported S-NSSAIs per PLMN or per SNPN. | - | | +| >>NPN Support Information | O | | 9.3.1.156 | Supported NPNs per PLMN. | YES | reject | +| >>Extended TAI Slice Support List | O | | Extended Slice Support List 9.3.1.165 | Additional Supported S-NSSAIs per PLMN or per SNPN. | YES | reject | +| >TAI NSAG Support List | O | | 9.3.1.273 | NSAG information associated with the slices per TAC, per PLMN or per SNPN. | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------|----------|-----------------------|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Cell Direction | O | | 9.3.1.78 | | YES | ignore | +| Broadcast PLMN Identity Info List | | 0.. | | This IE corresponds to the PLMN-IdentityInfoList IE and the NPN-IdentityInfoList IE (if available) in SIB1 as specified in TS 38.331 [8]. All PLMN Identities and associated information contained in the PLMN-IdentityInfoList IE and NPN identities and associated information contained in the NPN-IdentityInfoList IE (if available) are included and provided in the same order as broadcast in SIB1 . NOTE: In case of NPN-only cell, the PLMN Identities and associated information contained in the PLMN-IdentityInfoList IE are not included. | YES | ignore | +| Cell Type | O | | 9.3.1.87 | | YES | ignore | +| >PLMN Identity List | M | | Available PLMN List
9.3.1.65 | Broadcast PLMN IDs in SIB1 associated to the NR Cell Identity IE | - | | +| >Extended PLMN Identity List | O | | Extended Available PLMN List
9.3.1.76 | | - | | +| >5GS-TAC | O | | OCTET STRING (3) | | - | | +| >NR Cell Identity | M | | BIT STRING (36) | | - | | +| >RANAC | O | | RAN Area Code
9.3.1.57 | | - | | +| >Configured TAC Indication | O | | 9.3.1.87a | NOTE: This IE is associated with the 5GS TAC in the Broadcast PLMN Identity Info | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------|----------|-----------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | List IE | | | +| >NPN Broadcast Information | O | | 9.3.1.157 | If this IE is included the content of the PLMN Identity List IE and Extended PLMN Identity List IE if present in the Broadcast PLMN Identity Info List IE is ignored. | YES | reject | +| Configured TAC Indication | O | | 9.3.1.87a | NOTE: This IE is associated with the 5GS TAC on top-level of the Served Cell Information IE | YES | ignore | +| Aggressor gNB Set ID | O | | 9.3.1.93 | This IE indicates the associated aggressor gNB Set ID of the cell | YES | ignore | +| Victim gNB Set ID | O | | 9.3.1.93 | This IE indicates the associated Victim gNB Set ID of the cell | YES | ignore | +| IAB Info IAB-DU | O | | 9.3.1.106 | | YES | ignore | +| SSB Positions In Burst | O | | 9.3.1.138 | | YES | ignore | +| NR PRACH Configuration | O | | 9.3.1.139 | | YES | ignore | +| SFN Offset | O | | 9.3.1.208 | | YES | ignore | +| NPN Broadcast Information | O | | 9.3.1.157 | | YES | reject | +| Supported MBS FSA ID List | | 0.. | | Shall contain all MBS Frequency Selection Area Identities associated with the NR CGI. | YES | ignore | +| >MBS Frequency Selection Area Identity | M | | OCTET STRING(3) | | – | | +| RedCap Broadcast Information | O | | BIT STRING (SIZE(8)) | The presence of this IE indicates that the intraFreqReselectionRedCap IE is broadcast in SIB1 of the corresponding cell, see TS 38.331 [8]. Each position in the bitmap indicates which RedCap UEs are allowed access, according to the setting of RedCap barring indicators | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | in SIB1, see TS 38.331 [8].
First bit = 1Rx, second bit = 2Rx, third bit = halfDuplex, other bits reserved for future use. Value '1' indicates 'access allowed'. Value '0' indicates 'access not allowed'. | | | +| eRedCap Broadcast Information | O | | BIT STRING (SIZE(8)) | The presence of this IE indicates that the intraFreqReselection-eRedCap IE is broadcast in SIB1 of the corresponding cell, see TS 38.331 [8].
Each position in the bitmap indicates which eRedCap UEs are allowed access, according to the setting of the barring indicators in SIB1, see TS 38.331 [8].
First bit = 1Rx, second bit = 2Rx, third bit=half-duplex, other bits reserved for future use.
Value '1' indicates 'access allowed'.
Value '0' indicates 'access not allowed'. | YES | ignore | + +| Range bound | Explanation | +|-----------------------|---------------------------------------------------------------| +| maxnoofBPLMNs | Maximum no. of Broadcast PLMN Ids. Value is 6. | +| maxnoofExtendedBPLMNs | Maximum no. of Extended Broadcast PLMN Ids. Value is 6. | +| maxnoofBPLMNsNR | Maximum no. of PLMN Ids.broadcast in an NR cell. Value is 12. | +| maxnoofNR-UChannelIDs | Maximum no. NR-U Channel IDs in a cell. Value is 16. | +| maxnoofMBSFSA | Maximum no. of MBS FSAs by a cell. Value is 256. | + +### 9.3.1.11 Transmission Action Indicator + +This IE indicates actions for the gNB-DU for the data transmission to the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------|----------|-------|---------------------------------|-----------------------| +| Transmission Action Indicator | M | | ENUMERATED (stop, ..., restart) | | + +### 9.3.1.12 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.14 | | +| NR Cell Identity | M | | BIT STRING (SIZE(36)) | | + +### 9.3.1.13 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.14 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.15 Transmission Bandwidth + +The *Transmission Bandwidth* IE is used to indicate the UL or DL transmission bandwidth. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NR SCS | M | | ENUMERATED (scs15, scs30, scs60, scs120, ..., scs480, scs960) | The values scs15, scs30, scs60, scs120, scs480 and scs960 corresponds to the sub carrier spacing in TS 38.104 [17]. | +| NRB | M | | ENUMERATED (nrb11, nrb18, nrb24, nrb25, nrb31, nrb32, nrb38, nrb51, nrb52, nrb65, nrb66, nrb78, nrb79, nrb93, nrb106, nrb107, nrb121, nrb132, nrb133, nrb135, nrb160, nrb162, nrb189, nrb216, nrb217, nrb245, nrb264, nrb270, nrb273, ..., nrb33, nrb62, nrb124, nrb148, nrb248, nrb44, nrb58, nrb92, nrb119, nrb188, nrb242, nrb15) | This IE is used to indicate the UL or DL transmission bandwidth expressed in units of resource blocks "N RB " (TS 38.104 [17]). The values nrb11, nrb18, etc. correspond to the number of resource blocks "N RB " 11, 18, etc. | + +### 9.3.1.16 Void + +Reserved for future use. + +### 9.3.1.17 NR Frequency Info + +The NR Frequency Info defines the carrier frequency used in a cell for a given direction (UL or DL) in FDD or for both UL and DL directions in TDD or for an SUL carrier. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------|----------|-----------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| NR ARFCN | M | | INTEGER (0..maxNRARFCN) | RF Reference Frequency as defined in TS 38.104 [17] section 5.4.2.1. The frequency provided in this IE identifies the absolute frequency position of the reference resource block (Common RB 0) of the carrier. Its lowest subcarrier is also known as Point A. | – | | +| SUL Information | O | | 9.3.1.28 | | – | | +| Frequency Band List | | 1 | | | – | | +| >Frequency Band | | 1..Item | | ofNrCellBands> | | | | | +| >>NR Frequency Band | M | | INTEGER (1..1024, ...) | Operating Band as defined in TS 38.104 [17] section 5.4.2.3. The value 1 corresponds to NR operating band n1, value 2 corresponds to NR operating band n2, etc. | – | | +| >>Supported SUL band List | | 0..<maxno ofNrCellBands> | | | – | | +| >>>Supported SUL band Item | M | | INTEGER (1..1024, ...) | Supplementary NR Operating Band as defined in TS 38.104 [17] section 5.4.2.3 that can be used for SUL duplex mode as per TS 38.101-1 [26] table 5.2.-1. The value 80 corresponds to NR operating band n80, value 81 corresponds to NR operating band n81, etc. | – | | +| Frequency Shift 7p5khz | O | | ENUMERATED (false, true, ...) | Indicate whether the value of $\Delta_{\text{shift}}$ is 0kHz or 7.5kHz when calculating $F_{\text{REF,shift}}$ as defined in Section 5.4.2.1 of TS 38.104 [17]. | YES | ignore | + +| Range bound | Explanation | +|--------------------|----------------------------------------------------------------------| +| maxNRARFCN | Maximum value of NR ARFCNs. Value is 3279165. | +| maxnoofNrCellBands | Maximum no. of frequency bands supported for a NR cell. Value is 32. | + +### 9.3.1.18 gNB-DU System Information + +This IE contains the system information generated by the gNB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------------------------|-------------|----------------------| +| MIB message | M | | OCTET STRING | Includes the MIB message, as defined in | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|----------------------------------------------------------------------------|-------------|----------------------| +| | | | | subclause 6.2.2 in TS 38.331 [8]. | | | +| SIB1 message | M | | OCTET STRING | Includes the SIB1 message, as defined in subclause 6.2.2 in TS 38.331 [8]. | - | | +| SIB12 message | O | | OCTET STRING | Includes the SIB12 IE, as defined in subclause 6.3.1 in TS 38.331 [8]. | YES | ignore | +| SIB13 message | O | | OCTET STRING | Includes the SIB13 IE, as defined in subclause 6.3.1 in TS 38.331 [8]. | YES | ignore | +| SIB14 message | O | | OCTET STRING | Includes the SIB14 IE, as defined in subclause 6.3.1 in TS 38.331 [8]. | YES | ignore | +| SIB10 message | O | | OCTET STRING | Includes the SIB10 IE, as defined in subclause 6.3.1 in TS 38.331 [8]. | YES | ignore | +| SIB17 message | O | | OCTET STRING | Includes the SIB17 IE, as defined in subclause 6.3.1 in TS 38.331 [8]. | YES | ignore | +| SIB20 message | O | | OCTET STRING | Includes the SIB20 IE, as defined in subclause 6.3.1 in TS 38.331 [8]. | YES | ignore | +| SIB15 message | O | | OCTET STRING | Includes the SIB15 IE, as defined in subclause 6.3.1 in TS 38.331 [8]. | YES | ignore | +| SIBX message | O | | OCTET STRING | Includes the SIBX IE, as defined in subclause 6.3.1 in TS 38.331 [8]. | YES | ignore | + +### 9.3.1.19 E-UTRAN QoS + +This IE defines the QoS to be applied to a DRB or to a BH RLC channel for EN-DC case. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| QCI | M | | INTEGER | QoS Class | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------|----------|-------|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | (0..255) | Identifier defined in TS 23.401 [10]. Logical range and coding specified in TS 23.203 [11]. For a BH RLC channel, the Packet Delay Budget included in QCI defines the upper bound for the time that a packet may be delayed between the gNB-DU and its child IAB-MT. | | | +| Allocation and Retention Priority | M | | 9.3.1.20 | | - | | +| GBR QoS Information | O | | 9.3.1.21 | This IE shall be present for GBR bearers only and is ignored otherwise. | - | | +| ENB DL Transport Layer Address | O | | Transport Layer Address 9.3.2.3 | DL Transport Layer Address of node terminating PDCP. Included for MN-terminated SCG bearers. | YES | ignore | + +### 9.3.1.20 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 [10]).
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 (see TS 23.401 [10]).
Usage:
The E-RAB shall not pre-empt other E-RABs or, the E-RAB may | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | 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 (see TS 23.401 [10]).
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 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.21 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 | +|------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| E-RAB Maximum Bit Rate Downlink | M | | Bit Rate
9.3.1.22 | Maximum Bit Rate in DL (i.e. from EPC to E-UTRAN) for the bearer.
Details in TS 23.401 [10]. | +| E-RAB Maximum Bit Rate Uplink | M | | Bit Rate
9.3.1.22 | Maximum Bit Rate in UL (i.e. from E-UTRAN to EPC) for the bearer.
Details in TS 23.401 [10]. | +| E-RAB Guaranteed Bit Rate Downlink | M | | Bit Rate
9.3.1.22 | 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 [10]. | +| E-RAB Guaranteed Bit Rate Uplink | M | | Bit Rate
9.3.1.22 | 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 [10]. | + +### 9.3.1.22 Bit Rate + +This IE indicates the number of bits delivered by NG-RAN in UL or to NG-RAN 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 an aggregated maximum bit rate. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|--------------------------------------------|-----------------------| +| Bit Rate | M | | INTEGER (0..
4,000,000,000,000..
..) | The unit is: bit/s | + +### 9.3.1.23 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 use the same Transaction ID. The Transaction ID is determined by the initiating peer of a procedure. + +NOTE: If F1-C signalling transport is shared among multiple interface instances, the Transaction ID is allocated so that it can be associated with an F1-C interface instance. The Transaction ID may identify more than one interface instance. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|--------------------------|-----------------------| +| Transaction ID | M | | INTEGER
(0..255, ...) | | + +### 9.3.1.24 DRX Cycle + +The *DRX Cycle* IE is to indicate the desired DRX cycle. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| Long DRX Cycle Length | M | | ENUMERATED
(ms10, ms20, ms32,
ms40, ms60, ms64,
ms70, ms80,
ms128, ms160,
ms256, ms320,
ms512, ms640,
ms1024, ms1280,
ms2048, ms2560,
ms5120,
ms10240, ...) | Corresponds to the preferredDRX-LongCycle contained in the UEAssistanceInformation message defined in TS 38.331 [8] | +| Short DRX Cycle Length | O | | ENUMERATED
(ms2, ms3, ms4,
ms5, ms6, ms7,
ms8, ms10, ms14,
ms16, ms20, ms30,
ms32, ms35, ms40,
ms64, ms80,
ms128, ms160,
ms256, ms320,
ms512, ms640, ...) | Corresponds to the preferredDRX-ShortCycle contained in the UEAssistanceInformation message defined in TS 38.331 [8] | +| Short DRX Cycle Timer | O | | INTEGER (1..16) | Corresponds to the preferredDRX-ShortCycleTimer contained in the UEAssistanceInformation message defined in TS 38.331 | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| | | | | [8] | + +### 9.3.1.25 CU to DU RRC Information + +This IE contains the RRC Information that are sent from gNB-CU to gNB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CG-ConfigInfo | O | | OCTET STRING | Includes the CG-ConfigInfo message, as defined in TS 38.331 [8]. | - | | +| UE-CapabilityRAT-ContainerList | O | | OCTET STRING | This IE is used in the NG-RAN and it includes the UE-CapabilityRAT-ContainerList IE, as defined in TS 38.331 [8]. | - | | +| MeasConfig | O | | OCTET STRING | Includes the MeasConfig IE, as defined in TS 38.331 [8] (without the MeasGapConfig IE).
For EN-DC/NGEN-DC operation, includes the list of FR2 frequencies for which the gNB-CU requests the gNB-DU to generate gaps.
For NG-RAN, NE-DC and MN for NR-NR DC, includes the list of FR1 and/or FR2 frequencies, for which the gNB-CU requests the gNB-DU to generate gaps and the gap type (per-UE or per-FR). | - | | +| Handover Preparation Information | O | | OCTET STRING | Includes the HandoverPreparationInformation message, as defined in TS 38.331 [8]. | YES | ignore | +| CellGroupConfig | O | | OCTET STRING | Includes the CellGroupConfig | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | IE, as defined in TS 38.331 [8]. | | | +| Measurement Timing Configuration | O | | OCTET STRING | Contains the MeasurementTimingConfiguration inter-node message defined in TS 38.331 [8]. In EN-DC/NGEN-DC, it is included when the gaps for FR2 are requested to be configured by the MeNB. For MN in NR-NR DC, it is included when the gaps for FR2 and/or FR1 are requested by the SgNB | YES | ignore | +| UEAssistanceInformation | O | | OCTET STRING | Includes the UEAssistanceInformation message, as defined in TS 38.331 [8]. | YES | ignore | +| CG-Config | O | | OCTET STRING | Includes the CG-Config message, as defined in TS 38.331 [8]. | YES | ignore | +| UEAssistanceInformationEUTRA | O | | OCTET STRING | Includes the UEAssistanceInformation message, as defined in TS 36.331 [41]. | YES | ignore | +| Location Measurement Information | O | | OCTET STRING | Includes the LocationMeasurementInfo IE, as defined in TS 38.331[8] | YES | ignore | +| MUSIM-GapConfig | O | | OCTET STRING | Includes the MUSIM-GapConfig IE as defined in TS 38.331 [8]. | YES | reject | +| SDT-MAC-PHY-CG-Config | O | | OCTET STRING | Includes the SDT-MAC-PHY-CG-Config IE, as defined in TS 38.331 [8]. | YES | ignore | +| MBSInterestIndication | O | | OCTET STRING | Includes the MBSInterestIndication message as defined in TS 38.331 [8]. | YES | ignore | +| NeedForGapsInfoNR | O | | OCTET STRING | Includes the NeedForGapsInfoNR IE, as defined | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | in TS 38.331 [8]. | | | +| NeedForGapNCSG-InfoNR | O | | OCTET STRING | Includes the NeedForGapNCSG-InfoNR IE, as defined in TS 38.331 [8]. | YES | ignore | +| NeedForGapNCSG-InfoEUTRA | O | | OCTET STRING | Includes the NeedForGapNCSG-InfoEUTRA IE, as defined in TS 38.331 [8]. | YES | ignore | +| ConfigRestrictInfoDAPS | O | | OCTET STRING | Includes the ConfigRestrictInfoDAPS-r16 IE as defined in TS 38.331 [8]. This IE is used at the source node if DAPS HO is configured. | YES | ignore | +| Preconfigured measurement GAP Request | O | | ENUMERATED (true, ...) | | YES | ignore | +| NeedForInterruptionInfoNR | O | | OCTET STRING | Includes the NeedForInterruptionInfoNR IE, as defined in TS 38.331 [8]. | YES | ignore | +| musim-CapabilityRestrictionIndication | O | | ENUMERATED (true, ...) | Corresponds to the musim-CapabilityRestrictionIndication-r18 IE, as defined in TS 38.331 [8]. | YES | ignore | + +### 9.3.1.26 DU to CU RRC Information + +This IE contains the RRC Information that are sent from the gNB-DU to the gNB-CU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CellGroupConfig | M | | OCTET STRING | Includes the CellGroupConfig IE, as defined in TS 38.331 [8]. | - | | +| MeasGapConfig | O | | OCTET STRING | Includes the MeasGapConfig IE as defined in TS 38.331 [8]. For EN-DC/NGEN-DC operation, includes the gap for FR2, as requested by the gNB-CU via MeasConfig IE. | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | For NG-RAN, NE-DC and MN for NR-NR DC, includes the gap(s) for FR1 and/or FR2, as requested by the gNB-CU via MeasConfig IE.

For pre-configured measurement GAP scenario, it includes the gapToAddModList and/or gapToReleaseList as defined in TS 38.331 [8]. | | | +| Requested P-MaxFR1 | O | | OCTET STRING | Includes the requestedP-MaxFR1 contained in the CG-Config message, as defined in TS 38.331 [8].
For EN-DC, NGEN-DC and NR-DC operation, this IE should be included. | - | | +| DRX Long Cycle Start Offset | O | | INTEGER (0..10239) | Corresponds to the drx-LongCycleStartOffset IE contained in the DRX-Config IE as defined in TS 38.331 [8].
This field is not used in NR-DC. | - | | +| Selected BandCombinationIndex | O | | OCTET STRING | Includes the BandCombinationIndex IE, as defined in TS 38.331 [8].
For (NG)EN-DC and NR DC operation, this IE should be included so that gNB-CU is informed of the selected Band Combination; if this IE is included, the gNB-CU uses this information to | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | deduce the selected band. | | | +| Selected FeatureSetEntryIndex | O | | OCTET STRING | Includes the FeatureSetEntryIndex IE, as defined in TS 38.331 [8]. For (NG)EN-DC and NR DC operation, this IE should be included so that gNB-CU is informed of the selected FeatureSet. | YES | ignore | +| Ph-InfoSCG | O | | OCTET STRING | Includes the PH-TypeListSCG IE, as defined in TS 38.331 [8]. For MR-DC, this IE should be included so that gNB-CU is informed of the Power Headroom type for each serving cell in SN. | Yes | ignore | +| Requested BandCombinationIndex | O | | OCTET STRING | Includes the BandCombinationIndex IE, as defined in TS 38.331 [8]. This IE is used for the gNB-DU to request a new Band Combination. | YES | ignore | +| Requested FeatureSetEntryIndex | O | | OCTET STRING | Includes the FeatureSetEntryIndex IE, as defined in TS 38.331 [8]. This IE is used for the gNB-DU to request a new Feature Set. | YES | ignore | +| DRX Config | O | | OCTET STRING | Includes the DRX-Config IE, as defined in TS 38.331 [8]. This field is only used in NR-DC. | YES | ignore | +| PDCCH BlindDetectionSCG | O | | OCTET STRING | Includes the pdcch-BlindDetectionSCG contained in the CG-ConfigInfo message, as defined in TS 38.331 [8]. This IE | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | is used between the MgNB-DU and the MgNB-CU. | | | +| Requested PDCCH BlindDetectionSCG | O | | OCTET STRING | Includes the requestedPDCCH - BlindDetectionSCG contained in the CG-Config message, as defined in TS 38.331 [8]. This IE is used between the SgNB-DU and the SgNB-CU. | YES | ignore | +| Ph-InfoMCG | O | | OCTET STRING | Includes the PH-TypeListMCG IE, as defined in TS 38.331 [8]. For MR-DC, this IE should be included so that gNB-CU is informed of the Power Headroom type for each serving cell in MCG. | YES | ignore | +| MeasGapSharingConfig | O | | OCTET STRING | Includes the MeasGapSharingConfig IE as defined in TS 38.331 [8]. | YES | ignore | +| SL-PHY-MAC-RLC-Config | O | | OCTET STRING | Includes the SL-PHY-MAC-RLC-Config-r16 IE as defined in TS 38.331 [8]. | YES | ignore | +| SL-ConfigDedicatedEUTRA-Info | O | | OCTET STRING | Includes the SL-ConfigDedicatedEUTRA-Info IE as defined in TS 38.331 [8]. | YES | ignore | +| Requested P-MaxFR2 | O | | OCTET STRING | Includes the requestedP-MaxFR2 contained in the CG-Config message, as defined in TS 38.331 [8]. For NR-DC operation, this IE should be included. | YES | ignore | +| SDT-MAC-PHY-CG-Config | O | | OCTET STRING | Includes the SDT-MAC-PHY-CG-Config IE, as defined in TS | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------|----------|-------|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | 38.331 [8]. | | | +| MUSIM-GapConfig | O | | OCTET STRING | Includes the MUSIM-GapConfig IE as defined in TS 38.331 [8]. | YES | ignore | +| SL-RLC-ChannelToAddModList | O | | OCTET STRING | Includes the sl-RLC-ChannelToAddModList-r17 contained in the SL-ConfigDedicatedN R IE, as defined in TS 38.331 [8] | YES | ignore | +| InterFrequencyConfig-NoGap | O | | ENUMERATED (true, ...) | Corresponds to the interFrequencyConfig-NoGap-r16 contained in the MeasConfig IE, as defined in TS 38.331 [8]. | YES | ignore | +| ul-GapFR2-Config | O | | OCTET STRING | Includes the ul-GapFR2-Config contained in the RRCREconfiguration message, as specified in TS 38.331 [8]. | YES | ignore | +| TwoPHRModeMCG | O | | ENUMERATED (enabled, ...) | Corresponds to the twoPHRModeMCG contained in the CG-ConfigInfo message, as defined in TS 38.331 [8]. For NR-DC, this IE should be included so that gNB-CU is informed of the two PHR mode in the MN. | YES | ignore | +| TwoPHRModeSCG | O | | ENUMERATED (enabled, ...) | Corresponds to the twoPHRModeSCG contained in the CG-Config message, as defined in TS 38.331 [8]. For NR-DC, this IE should be included so that gNB-CU is informed of the two PHR mode in | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| ncd-SSB-RedCapInitialBWP-SDT | O | | OCTET STRING | the SN.
Includes the NonCellDefiningSSB contained in the RRCRelease message, as specified in TS 38.331 [8]. | YES | ignore | +| ServCellInfoList | O | | OCTET STRING | Includes the ServCellInfoListSCG-NR IE or the ServCellInfoListMCG-NR IE, as defined in TS 38.331 [8]. This IE is used for inter-node message for MN and SN in case of split gNB architecture. | YES | ignore | + +### 9.3.1.27 RLC Mode + +The *RLC Mode* IE indicates the RLC Mode used for a DRB or a BH RLC channel, or a Uu Relay RLC channel, or a PC5 Relay RLC channel. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------------------------------------------------------------------------------------|-----------------------| +| RLC Mode | M | | ENUMERATED ( RLC-AM, RLC-UM-Bidirectional, RLC-UM-Unidirectional-UL, RLC-UM-Unidirectional-DL, ...) | | + +### 9.3.1.28 SUL Information + +This IE provides information about the SUL carrier. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| SUL ARFCN | M | | INTEGER (0..maxNRARFCN) | RF Reference Frequency as defined in TS 38.104 [17] section 5.4.2.1. The frequency provided in this IE identifies the absolute frequency position of the reference resource block | – | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------|----------|-------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | (Common RB 0) of the SUL carrier. Its lowest subcarrier is also known as Point A. | | | +| SUL Transmission Bandwidth | M | | Transmission Bandwidth 9.3.1.15 | | – | | +| Carrier List | O | | NR Carrier List 9.3.1.137 | If included, the SUL Transmission Bandwidth IE shall be ignored. | YES | ignore | +| Frequency Shift 7p5khz | O | | ENUMERATED (false, true, ...) | Indicate whether the value of $\Delta_{\text{shift}}$ is 0kHz or 7.5kHz when calculating $F_{\text{REF,shift}}$ as defined in Section 5.4.2.1 of TS 38.104 [17]. | YES | ignore | + +| Range bound | Explanation | +|-------------|-----------------------------------------------| +| maxNRARFCN | Maximum value of NR ARFCNs. Value is 3279165. | + +### 9.3.1.29 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.3.1.29a Configured EPS TAC + +This information element is used to identify a configured EPS Tracking Area Code in order to enable application of Roaming and Access Restrictions for EN-DC as specified in TS 37.340 [7]. This IE is configured for the cell, but not broadcast. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|-------------------------|-----------------------| +| Configured EPS TAC | M | | OCTET STRING (SIZE (2)) | | + +### 9.3.1.30 RRC Reconfiguration Complete Indicator + +This IE indicates the result of the reconfiguration performed towards the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------|----------|-------|----------------------------------|-----------------------| +| RRC Reconfiguration Complete Indicator | M | | ENUMERATED (true, ... , failure) | | + +### 9.3.1.31 UL Configuration + +This IE indicates how the UL scheduling is configured at gNB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UL UE Configuration | M | | ENUMERATED (no-data, shared, only, ...) | Indicates how the UE uses the UL at gNB-DU, for which "no-data" indicates that the UL scheduling is not performed at gNB-DU, "shared" indicates that the UL scheduling is performed at both gNB-DU and another node, and "only" indicates that the UL scheduling is only performed at the gNB-DU. | + +### 9.3.1.32 C-RNTI + +This IE contains the C-RNTI information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-------------------------|-------------------------------------| +| C-RNTI | M | | INTEGER (0..65535, ...) | C-RNTI as defined in TS 38.331 [8]. | + +### 9.3.1.33 Cell UL Configured + +This IE indicates whether the gNB-CU requests the gNB-DU to configure the uplink as no UL, UL, SUL or UL+SUL for the indicated cell for the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|---------------------------------------------|----------------------------------------------| +| Cell UL Configured | M | | ENUMERATED (none, UL, SUL, UL and SUL, ...) | Further details are defined in TS 38.331 [8] | + +### 9.3.1.34 RAT-Frequency Priority Information + +The RAT-Frequency Priority Information contains either the *Subscriber Profile ID for RAT/Frequency priority* IE or the *Index to RAT/Frequency Selection Priority* IE. These parameters are used to define local configuration for RRM strategies. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE RAT-Frequency Priority Information | M | | | | +| >EN-DC | | | | | +| >>Subscriber Profile ID for RAT/Frequency priority | M | | INTEGER (1..256, ...) | | +| >NG-RAN | | | | | +| >>Index to RAT/Frequency Selection Priority | M | | INTEGER (1..256, ...) | | + +### 9.3.1.35 LCID + +This IE uniquely identifies a LCID for the associated SRB or DRB. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|----------------------------------------------------------------------------| +| LCID | M | | INTEGER (1..32, ...) | Corresponds to the LogicalChannelIdentity defined in TS 38.331 [8]. | + +### 9.3.1.36 Duplication activation + +The *Duplication Activation* IE indicates whether UL PDCP Duplication is activated or not. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|------------------------------------|-----------------------| +| Duplication Activation | M | | ENUMERATED (Active, Inactive, ...) | | + +### 9.3.1.37 Slice Support List + +This IE indicates the list of supported slices. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------|----------|------------------------------------|-----------------------|-----------------------| +| Slice Support Item IEs | | 1.. <maxnooSlicItems> | | | +| >S-NSSAI | M | | 9.3.1.38 | | + +| Range bound | Explanation | +|-----------------|--------------------------------------------------------------| +| maxnooSlicItems | Maximum no. of signalled slice support items. Value is 1024. | + +### 9.3.1.38 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.39 UE Identity Index value + +This IE is used by the gNB-DU to calculate the Paging Frame. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE UE Identity Index | M | | | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------|----------|-------|-----------------------|---------------------------------------| +| Value | | | | | +| >Length-10 | | | | | +| >>Index Length 10 | M | | BIT STRING (SIZE(10)) | Coded as specified in TS 38.304 [24]. | + +### 9.3.1.40 Paging DRX + +This IE indicates the Paging DRX as defined in TS 38.304 [24]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------------------|-----------------------| +| Paging DRX | M | | ENUMERATED(32, 64, 128, 256, ...) | Unit in radio frame. | + +### 9.3.1.41 Paging Priority + +This IE indicates the paging priority for paging a UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------|----------|-------|------------------------------------------------------------------------------------------------------------------|--------------------------------------------------| +| Paging Priority | M | | ENUMERATED (PrioLevel1, PrioLevel2, PrioLevel3, PrioLevel4, PrioLevel5, PrioLevel6, PrioLevel7, PrioLevel8, ...) | Lower value codepoint indicates higher priority. | + +### 9.3.1.42 gNB-CU System Information + +This IE contains the system information encoded by the gNB-CU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------|----------|-------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| SIB type to Be Updated List | | 1 | | | - | | +| >SIB type to Be Updated Item IEs | | 1... | | | - | | +| >>SIB type | M | | INTEGER (2..32, ...) | Indicates a certain SIB block, e.g. 2 means sibType2, 3 for sibType3, etc. Values for SIBs generated by the gNB-DU as defined subclause 5.2.2 in TS 38.470 [2], values 6, 7, 8 and values | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|------------------------|--------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | corresponding to not defined SIBs in TS 38.331 [8] are not applicable in this version of the specifications. | | | +| >>SIB message | M | | OCTET STRING | SIB as defined in subclause 6.3.1 in TS 38.331 [8]. | - | | +| >>Value Tag | M | | INTEGER (0..31, ...) | | - | | +| >>areaScope | O | | ENUMERATED (true, ...) | Indicates that a SIB is area specific. If the field is not present, the SIB is cell specific. | YES | ignore | +| SystemInformationAreaID | O | | BIT STRING (SIZE (24)) | Indicates the system information area that the cell belongs to, if any. | YES | ignore | + +| Range bound | Explanation | +|----------------|----------------------------------------------------| +| maxnooSIBTypes | Maximum no. of SIB types, the maximum value is 32. | + +### 9.3.1.43 RAN UE Paging identity + +This IE indicates the RAN UE Paging identity. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| I-RNTI | M | | BIT STRING (SIZE(40)) | | + +### 9.3.1.44 CN UE Paging Identity + +The 5G-S-TMSI is used as UE identifier for CN paging. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|-------|-----------------------|----------------------------------| +| CHOICE CN UE paging identity | M | | | | +| >5G-S-TMSI/ | | | | | +| >>5G-S-TMSI | M | | BIT STRING (SIZE(48)) | Details defined in TS 38.413 [3] | + +### 9.3.1.45 QoS Flow Level QoS Parameters + +This IE defines the QoS to be applied to a QoS flow, or to a DRB, or to a BH RLC channel, or to a Uu Relay RLC channel, or to a PC5 Relay RLC channel. + +NOTE: For a BH RLC channel, the listed mandatory IEs and the *GBR QoS Flow Information* IE are applicable, + +where *GBR QoS Flow Information* IE may be present if BH RLC channel conveys the traffic belonging to a GBR 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.49 | | - | | +| >Dynamic 5QI | | | | | - | | +| >>Dynamic 5QI Descriptor | M | | 9.3.1.47 | | - | | +| NG-RAN Allocation and Retention Priority | M | | 9.3.1.48 | | - | | +| GBR QoS Flow Information | O | | 9.3.1.46 | This IE shall be present for GBR QoS Flows only and is ignored otherwise. | - | | +| Reflective QoS Attribute | O | | ENUMERATED (subject to, ...) | Details in TS 23.501 [21]. This IE applies to non-GBR flows only and is ignored otherwise. | - | | +| PDU Session ID | O | | INTEGER (0 ..255) | As specified in TS 23.501 [21]. | YES | ignore | +| UL PDU Session Aggregate Maximum Bit Rate | O | | Bit Rate 9.3.1.22 | The PDU session Aggregate Maximum Bit Rate Uplink which is associated with the involved PDU session. | YES | ignore | +| QoS Monitoring Request | O | | ENUMERATED (UL, DL, Both, ..., stop) | Indicates to measure UL, or DL, or both UL/DL delays for the associated QoS flow or stop the corresponding QoS monitoring. | YES | ignore | +| PDCP Terminating Node DL Transport Layer Address | O | | Transport Layer Address 9.3.2.3 | DL Transport Layer Address of node terminating PDCP. Included for MN-terminated SCG bearers and SN-terminated MCG bearers. | YES | ignore | +| PDU Set QoS Parameters | O | | 9.3.1.319 | | YES | ignore | + +### 9.3.1.46 GBR QoS Flow Information + +This IE indicates QoS parameters for a GBR QoS flow or GBR bearer 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.22 | Maximum Bit Rate in DL. Details in TS 23.501 [21]. | - | | +| Maximum Flow Bit Rate Uplink | M | | Bit Rate
9.3.1.22 | Maximum Bit Rate in UL. Details in TS 23.501 [21]. | - | | +| Guaranteed Flow Bit Rate Downlink | M | | Bit Rate
9.3.1.22 | Guaranteed Bit Rate (provided there is data to deliver) in DL. Details in TS 23.501 [21]. | - | | +| Guaranteed Flow Bit Rate Uplink | M | | Bit Rate
9.3.1.22 | Guaranteed Bit Rate (provided there is data to deliver). Details in TS 23.501 [21]. | - | | +| Maximum Packet Loss Rate Downlink | O | | Maximum Packet Loss Rate
9.3.1.50 | Indicates the maximum rate for lost packets that can be tolerated in the downlink direction. Details in TS 23.501 [21]. | - | | +| Maximum Packet Loss Rate Uplink | O | | Maximum Packet Loss Rate
9.3.1.50 | Indicates the maximum rate for lost packets that can be tolerated in the uplink direction. Details in TS 23.501 [21]. | - | | +| Alternative QoS Parameters Set List | O | | 9.3.1.125 | Indicates alternative sets of QoS Parameters for the QoS flow. | YES | ignore | + +### 9.3.1.47 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 | +|---------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| QoS Priority Level | M | | INTEGER
(1..127) | For details see TS 23.501 [21]. | - | | +| Packet Delay Budget | M | | 9.3.1.51 | For details see TS 23.501 [21]. For IAB, the Packet Delay Budget defines the upper bound for the time that a packet may be delayed between the IAB-DU/IAB-donor-DU and its child IAB-MT, or between | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|-------------|-------|-------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | the IAB-DU and its served UE. For a PC5 Relay RLC channel, the Packet Delay Budget defines the upper bound for the time that a packet may be delayed between the L2 U2N relay UE and L2 U2N remote UE. For a Uu Relay RLC channel, the Packet Delay Budget defines the upper bound for the time that a packet may be delayed between the gNB-DU and L2 U2N relay UE. This IE is ignored if the Extended Packet Delay Budget IE is present. | | | +| Packet Error Rate | M | | 9.3.1.52 | For details see TS 23.501 [21]. | - | | +| 5QI | O | | INTEGER (0..255,...) | This IE contains the dynamically assigned 5QI as specified in TS 23.501 [21]. | - | | +| Delay Critical | C-ifGBRflow | | ENUMERATED (delay critical, non-delay critical) | For details see TS 23.501 [21]. | - | | +| Averaging Window | C-ifGBRflow | | 9.3.1.53 | For details see TS 23.501 [21]. | - | | +| Maximum Data Burst Volume | O | | 9.3.1.54 | For details see TS 23.501 [21]. This IE shall be included if the Delay Critical IE is set to "delay critical" and is ignored otherwise. | - | | +| Extended Packet Delay Budget | O | | 9.3.1.145 | Packet Delay Budget is specified in TS 23.501 [21]. | YES | ignore | +| CN Packet Delay Budget Downlink | O | | Extended Packet Delay Budget 9.3.1.145 | Core Network Packet Delay Budget is specified in TS 23.501 [21]. This IE may be | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | present in case of GBR QoS flows and is ignored otherwise. | | | +| CN Packet Delay Budget Uplink | O | | Extended Packet Delay Budget 9.3.1.145 | Core Network Packet Delay Budget is specified in TS 23.501 [21]. This IE may be present in case of GBR QoS flows and is ignored otherwise. | YES | ignore | + +| 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.48 NG-RAN Allocation and Retention Priority + +This IE specifies the relative importance of a QoS flow or a DRB compared to other QoS flows or DRBs 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 [21]).

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 [21].

| +| 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 (see TS 23.501 [21]).

Usage: The QoS flow shall not pre-empt other QoS flows or, the QoS flow may pre-empt other QoS flows.

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 gNB.

| +| 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 (see TS 23.501 [21]).

Usage: The QoS flow shall not be pre-empted by other QoS

| + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | flows or the QoS flow may be pre-empted by other QoS flows.
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 thegNB. | + +### 9.3.1.49 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 [21]. For a BH RLC channel, the Packet Delay Budget included in 5QI defines the upper bound for the time that a packet may be delayed between the gNB-DU and its child IAB-MT. | - | | +| Priority Level | O | | INTEGER (1..127) | For details see TS 23.501 [21]. When included overrides standardized or pre-configured value. | - | | +| Averaging Window | O | | 9.3.1.53 | For details see TS 23.501 [21]. When included overrides standardized or pre-configured value. | - | | +| Maximum Data Burst Volume | O | | 9.3.1.54 | For details see TS 23.501 [21]. When included overrides standardized or pre-configured value. | - | | +| CN Packet Delay Budget Downlink | O | | Extended Packet Delay Budget 9.3.1.145 | Core Network Packet Delay Budget is specified in TS 23.501 [21]. This IE may be | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | present in case of GBR QoS flows and is ignored otherwise. | | | +| CN Packet Delay Budget Uplink | O | | Extended Packet Delay Budget 9.3.1.145 | Core Network Packet Delay Budget is specified in TS 23.501 [21]. This IE may be present in case of GBR QoS flows and is ignored otherwise. | YES | ignore | + +### 9.3.1.50 Maximum Packet Loss Rate + +This IE indicates the Maximum Packet Loss Rate. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------| +| Maximum Packet Loss Rate | M | | INTEGER(0..1000) | Ratio of lost packets per number of packets sent, expressed in tenth of percent. | + +### 9.3.1.51 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.52 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.53 Averaging Window + +This IE indicates the Averaging Window for a QoS flow, and applies to GBR QoS Flows only. + +| 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.54 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.55 Masked IMEISV + +This information element contains the IMEISV value with a mask, to identify a terminal model without identifying an individual Mobile Equipment. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Masked IMEISV | M | | BIT STRING (SIZE
(64)) | Coded as the International Mobile station Equipment Identity and Software Version Number (IMEISV) defined in TS 23.003 [23] with the last 4 digits of the SNR masked by setting the corresponding bits to 1. The first to fourth bits correspond to the first digit of the IMEISV, the fifth to eighth bits correspond to the second digit of the IMEISV, and so on. | + +### 9.3.1.56 Notification Control + +The *Notification Control* IE indicates whether the notification control for a given DRB is active or not-active. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|----------|-------|-------------------------------------|-----------------------| +| Notification Control | M | | ENUMERATED(Active, Not-Active, ...) | | + +### 9.3.1.57 RAN Area Code + +This information element is used to uniquely identify a RAN Area Code. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| RANAC | M | | INTEGER (0..255) | RAN Area Code | + +### 9.3.1.58 PWS System Information + +This IE contains the system information used for public warning. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| SIB type | M | | INTEGER (6..8, ...) | Indicates a certain SIB block for public warning message, e.g. 6 means sibType6, 7 for sibType7, etc. | - | | +| SIB message | M | | OCTET STRING | SIB message for public warning, as defined in TS 38.331 [8]. | - | | +| Notification Information | O | | | | YES | ignore | +| >Message Identifier | M | | 9.3.1.81 | | - | | +| >Serial Number | M | | 9.3.1.82 | | - | | +| Additional SIB Message List | O | | 9.3.1.86 | Additional SIB messages containing different segments of a public warning message if segmentation is applied, as defined in TS 38.331 [8]. | YES | reject | + +### 9.3.1.59 Repetition Period + +This IE indicates the periodicity of the warning message to be broadcast. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------|----------|-------|---------------------------------|--------------------------------------------------------| +| Repetition Period | M | | INTEGER (0..2 17 -1) | The unit of value 1 to 2 17 -1 is [second]. | + +### 9.3.1.60 Number of Broadcasts Requested + +This IE indicates the number of times a message is to be broadcast. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|-------|-----------------------|-----------------------| +| Number of Broadcasts Requested | M | | INTEGER (0..65535) | | + +### 9.3.1.61 Void + +### 9.3.1.62 SIType List + +This IE is used by the gNB-CU to indicate to the gNB-DU to broadcast one or several *SystemInformation* messages including the Other SI. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SI type item IEs | | 1..
| | | +| >SI Type | M | | INTEGER (1..32, ...) | Value "1" corresponds to the SI message identified by the first SI message indicated in the SI-SchedulingInfo IE in the SIB1 message, value "2" to the SI message identified by the second SI message indicated in the SI-SchedulingInfo IE in the SIB1 message, and so on, as defined in TS 38.331 [8]. | + +| Range bound | Explanation | +|----------------|---------------------------------------------------| +| maxnoofSITypes | Maximum no. of SI types, the maximum value is 32. | + +### 9.3.1.63 QoS Flow Identifier + +This IE identifies a QoS Flow within a PDU Session. The definition and use of the QoS Flow Identifier is specified in TS 23.501 [21]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|-----------------------|-----------------------| +| QoS Flow Identifier | M | | INTEGER (0 ..63) | | + +### 9.3.1.64 Served E-UTRA Cell Information + +This IE contains served cell information of an E-UTRA cell for spectrum sharing between E-UTRA and NR. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------| +| CHOICE EUTRA-Mode-Info | M | | | | +| > FDD | | | | | +| >> FDD Info | | 1 | | | +| >>>UL Offset to Point A | M | | INTEGER (0..2199,...) | Indicates the offset to the center of the NR carrier for UL. | +| >>>DL Offset to Point A | M | | INTEGER (0..2199,...) | Indicates the offset to the center of the NR carrier for DL. | +| > TDD | | | | | +| >> TDD Info | | 1 | | | +| >>>Offset to Point A | M | | INTEGER (0..2199,...) | Indicates the offset to the center of the NR carrier. | +| Protected E-UTRA Resource Indication | O | | OCTET STRING | Indicates the Protected E-UTRA Resource Indication as defined in subclause 9.2.125 of TS 36.423 [9]. | + +### 9.3.1.65 Available PLMN List + +This IE indicates the list of available PLMN. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|-------------------------|-----------------------|-----------------------| +| Available PLMN Item IEs | | 1..<
maxnoofBPLMNs > | | | +| >PLMN Identity | M | | 9.3.1.14 | | + +| Range bound | Explanation | +|---------------|------------------------------------------------| +| maxnoofBPLMNs | Maximum no. of Broadcast PLMN Ids. Value is 6. | + +### 9.3.1.66 RLC Failure Indication + +This IE indicates the LCID associated with the RLC entity needing re-establishment. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------|----------|-------|-----------------------|-----------------------| +| Associated LCID | M | | LCID
9.3.1.35 | | + +### 9.3.1.67 Uplink TxDirectCurrentList Information + +This IE contains the Uplink TxDirectCurrentList information that is configured by the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------| +| Uplink TxDirectCurrentList Information | M | | OCTET STRING | Includes the UplinkTxDirectCurrentList IE as defined in TS 38.331 [8]. | + +### 9.3.1.68 Service Status + +This IE is used to indicate the service status of a cell by the gNB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| Service State | M | | ENUMERATED (In-Service, Out-Of-Service, ...) | Indicates the Service State of the cell. In-Service and Out-of-Service Service States are defined in TS 38.401 [4]. | +| Switching Off Ongoing | O | | ENUMERATED (True, ...) | This IE indicates that the gNB-DU will delete the cell after some time using a new gNB-DU Configuration Update procedure. | + +### 9.3.1.69 RLC Status + +This IE indicates about the RLC configuration change included in the container towards the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------|----------|-------|-----------------------|-----------------------------------| +| Reestablishment Indication | O | | ENUMERATED | Indicates that following a change | + +| | | | | | +|--|--|--|----------------------|-------------------------------------------------------| +| | | | (reestablished, ...) | in the radio status, the RLC has been re-established. | +|--|--|--|----------------------|-------------------------------------------------------| + +### 9.3.1.70 RRC Version + +This information element is used to identify RRC version corresponding to TS 38.331 [8]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------|----------|-------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Latest RRC Version | M | | BIT STRING (SIZE (3)) | This IE is not used in this release. | - | | +| Latest RRC Version Enhanced | O | | OCTET STRING (SIZE (3)) | Latest supported RRC version in the release corresponding to TS 38.331 [8]. For a 3GPP specification version x.y.z, x is encoded by the leftmost byte, y by the middle byte, and z by the rightmost byte. If the RRC protocol is not supported in the gNB-DU, this IE is set to all '0's. | YES | ignore | + +### 9.3.1.71 RRC Delivery Status + +This IE provides information about the delivery status of RRC messages to the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|---------------------------------|------------------------------------------------------------------| +| Delivery Status | M | | INTEGER (0..2 12 -1) | Highest NR PDCP SN successfully delivered in sequence to the UE. | +| Triggering Message | M | | INTEGER (0..2 12 -1) | NR PDCP SN for the RRC message that triggered the report. | + +### 9.3.1.72 QoS Flow Mapping Indication + +This IE is used to indicate only the uplink or downlink QoS flow is mapped to the DRB. + +| 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 | + +### 9.3.1.73 Resource Coordination Transfer Information + +This IE contains information for UE-associated E-UTRA – NR resource coordination. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------| +| MeNB Cell ID | M | | BIT STRING (SIZE(28)) | E-UTRAN Cell Identifier IE contained in the ECGI as defined in TS 36.423 [9] clause 9.2.14 | +| Resource Coordination E-UTRA Cell Information | O | | 9.3.1.75 | | + +### 9.3.1.74 E-UTRA PRACH Configuration + +This IE indicates the PRACH resources used in E-UTRA cell. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------| +| RootSequenceIndex | M | | INTEGER (0..837) | See section 5.7.2. in TS 36.211 [27] | +| ZeroCorrelationZoneConfig | M | | INTEGER (0..15) | See section 5.7.2. in TS 36.211 [27] | +| HighSpeedFlag | M | | BOOLEAN | TRUE corresponds to Restricted set and FALSE to Unrestricted set. See section 5.7.2 in TS 36.211 [27] | +| PRACH-FrequencyOffset | M | | INTEGER (0..94) | See section 5.7.1 of TS 36.211 [27] | +| PRACH-ConfigurationIndex | C-iftD | | INTEGER (0..63) | See section 5.7.1. in TS 36.211 [27] | + +| Condition | Explanation | +|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| iftD | This IE shall be present if the EUTRA-Mode-Info IE in the Resource Coordination E-UTRA Cell Information IE is set to the value "TDD". | + +### 9.3.1.75 Resource Coordination E-UTRA Cell Information + +This IE contains E-UTRA cell information for UE-associated E-UTRA – NR resource coordination. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|---------------------------------------|------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE EUTRA-Mode-Info | M | | | | - | | +| >FDD | | | | | - | | +| >>FDD Info | | 1 | | | - | | +| >>>UL EARFCN | O | | INTEGER (0 .. maxExtendedEARFCN, ...) | The relation between EARFCN and carrier frequency (in MHz) is defined in TS 36.104 [25]. | - | | +| >>>DL EARFCN | M | | INTEGER (0 .. maxExtendedEARFCN, ...) | The relation between EARFCN and carrier | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|-------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | frequency (in MHz) is defined in TS 36.104 [25]. | | | +| >>>UL Transmission Bandwidth | O | | E-UTRA Transmission Bandwidth 9.3.1.80 | Present if UL EARFCN IE is present. | - | | +| >>>DL Transmission Bandwidth | M | | E-UTRA Transmission Bandwidth 9.3.1.80 | | - | | +| >TDD | | | | | - | | +| >>TDD Info | | 1 | | | - | | +| >>>EARFCN | M | | INTEGER (0 .. maxExtendedEARFCN, ...) | The relation between EARFCN and carrier frequency (in MHz) is defined in TS 36.104 [25]. | - | | +| >>>Transmission Bandwidth | M | | E-UTRA Transmission Bandwidth 9.3.1.80 | | - | | +| >>>Subframe Assignment | M | | ENUMERATED (sa0, sa1, sa2, sa3, sa4, sa5, sa6,...) | Uplink-downlink subframe configuration information defined in TS 36.211 [27]. In NB-IOT, sa0 and sa6 are not applicable. | - | | +| >>>Special Subframe Info | | 1 | | Special subframe configuration information defined in TS 36.211 [27] | - | | +| >>>>Special Subframe Patterns | M | | ENUMERATED (ssp0, ssp1, ssp2, ssp3, ssp4, ssp5, ssp6, ssp7, ssp8, ssp9, ssp10, ...) | | - | | +| >>>>Cyclic Prefix DL | M | | ENUMERATED (Normal, Extended,...) | | - | | +| >>>>Cyclic Prefix UL | M | | ENUMERATED (Normal, Extended,...) | | - | | +| E-UTRA PRACH Configuration | M | | 9.3.1.74 | | - | | +| Ignore PRACH Configuration | O | | ENUMERATED (true,...) | | YES | reject | + +| Range bound | Explanation | +|-------------|-------------| +|-------------|-------------| + +| | | +|-------------------|----------------------------------------------------| +| maxExtendedEARFCN | Maximum value of extended EARFCN. Value is 262143. | +|-------------------|----------------------------------------------------| + +### 9.3.1.76 Extended Available PLMN List + +This IE indicates the list of available PLMN. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------|----------|---------------------------------|-----------------------|-----------------------| +| Extended Available PLMN Item IEs | | 1..<
maxnoofExtendedBPLMNs > | | | +| >PLMN Identity | M | | 9.3.1.14 | | + +| Range bound | Explanation | +|-----------------------|---------------------------------------------------------| +| maxnoofExtendedBPLMNs | Maximum no. of Extended Broadcast PLMN Ids. Value is 6. | + +### 9.3.1.77 Associated SCell List + +This IE indicates the list of SCells associated with the RLC entity indicated by the *RLC Failure Indication* IE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------|----------|-------------------------|-----------------------|-----------------------|-------------|----------------------| +| Associated SCell Item IEs | | 1..<
maxnoofSCells > | | | - | - | +| >SCell ID | M | | NR CGI
9.3.1.12 | | - | | + +| Range bound | Explanation | +|---------------|------------------------------------------------------------------------| +| maxnoofSCells | Maximum no. of SCells allowed towards one UE, the maximum value is 32. | + +### 9.3.1.78 Cell Direction + +This IE indicates if the cell is either bidirectional or only DL or only UL. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|----------------------------------|-----------------------| +| Cell Direction | M | | ENUMERATED
(dl-only, ul-only) | | + +### 9.3.1.79 Paging Origin + +This IE indicates whether Paging is originated due to the PDU sessions from the non-3GPP access. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-------------------------------|-----------------------| +| Paging Origin | M | | ENUMERATED
(non-3GPP, ...) | | + +### 9.3.1.80 E-UTRA Transmission Bandwidth + +This IE is used to indicate the E-UTRA UL or DL transmission bandwidth expressed in units of resource blocks " NRB " (TS 36.104 [25]). The values bw1, bw6, bw15, bw25, bw50, bw75, bw100 correspond to the number of resource blocks "NRB" 6, 15, 25, 50, 75, 100. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|---------------------------------------------------------|-----------------------| +| E-UTRA Transmission Bandwidth | M | | ENUMERATED
(bw6, bw15, bw25, bw50, bw75, bw100,... ) | | + +### 9.3.1.81 Message Identifier + +This IE identifies the warning message. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|--------------------------|-------------------------------------------------------------------| +| Message Identifier | M | | BIT STRING
(SIZE(16)) | This IE is set by the 5GC, transferred to the UE by the gNB node. | + +### 9.3.1.82 Serial Number + +This IE 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 reference | Semantics description | +|---------------|----------|-------|--------------------------|-----------------------| +| Serial Number | M | | BIT STRING
(SIZE(16)) | | + +### 9.3.1.83 UAC Assistance Information + +This information element contains assistance information helping the gNB-DU to set parameters for Unified Access Class barring. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------|----------|--------------------------|-----------------------|-----------------------|-------------|----------------------| +| UAC PLMN List | | 1 | | | - | | +| > UAC PLMN Item | | 1.. | | | - | | +| >>PLMN Identity | M | | 9.3.1.14 | | - | | +| >> UAC Type List | | 1 | | | - | | +| >>> UAC Type Item | | 1.. | | | - | | +| >>>>UAC Reduction Indication | M | | 9.3.1.85 | | - | | +| >>>>CHOICE UAC Category | M | | | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|--------------------------|----------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Type | | | | | | | +| >>>>>UAC
Standardized | | | | | - | | +| >>>>>UAC
Action | M | | 9.3.1.84 | | - | | +| >>>>>UAC
Operator Defined | | | | | - | | +| >>>>>Access
Category | M | | INTEGER
(32..63, ...) | Indicates the operator defined Access Category as defined in subclause 6.3.2 in TS 38.331 [8]. | - | | +| >>>>>Access
Identity | M | | BIT STRING
(SIZE(7)) | Indicates whether access attempt is allowed for each Access Identity as defined in subclause 6.3.2 in TS 38.331 [8]. | - | | +| >>NID | O | | 9.3.1.155 | | YES | ignore | + +| Range bound | Explanation | +|-------------------|------------------------------------------------------------| +| maxnoofUACPLMNs | Maximum no. of UAC PLMN Ids. Value is 12. | +| maxnoofUACperPLMN | Maximum no. of signalled categories per PLMN. Value is 64. | + +### 9.3.1.84 UAC Action + +This IE indicates which signalling traffic is expected to be reduced by the gNB-CU, as defined in clause 8.7.7 of TS 38.413 [3] + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| UAC Action | M | | ENUMERATED
(Reject RRC connection establishments for non-emergency MO DT, Reject RRC connection establishments for Signalling, Permit Emergency Sessions and mobile terminated services only, Permit High Priority Sessions and mobile terminated services only,...) | | + +### 9.3.1.85 UAC reduction Indication + +This IE indicates the percentage of signalling traffic expected to be reduced by the gNB-CU, relative to the instantaneous incoming rate from the gNB-DU + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| UAC reduction Indication | M | | INTEGER (0..100) | Value 0 indicates that no access rate reduction is desired. In this version of specification, value 99 indicates the highest desired rate reduction. | + +### 9.3.1.86 Additional SIB Message List + +This IE indicates the list of additional SIB messages containing all the remaining segments of a public warning message if segmentation is applied to such message. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------|----------|--------------------------------|-----------------------|----------------------------------------------------------------------------------------------| +| Additional SIB Message List Item IEs | | 1..
| | | +| >Additional SIB | M | | OCTET STRING | SIB message containing one segment of a public warning message, as defined in TS 38.331 [8]. | + +| Range bound | Explanation | +|-----------------------|------------------------------------------------------------------------------| +| maxnoofAdditionalSIBs | Maximum no. of additional segments of a public warning message. Value is 63. | + +### 9.3.1.87 Cell Type + +This IE provides the cell coverage area. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------------------------------------|-----------------------| +| Cell Size | M | | ENUMERATED
(verysmall, small, medium, large, ...) | | + +### 9.3.1.87a Configured TAC Indication + +This IE indicates that the TAC with which this IE is associated, is only configured for the cell, but not broadcast. + +NOTE: This IE is defined in accordance to the possibility foreseen in TS 38.331 [8] to not broadcast the TAC if the NR cell only supports PSCell/SCell functionality. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|---------------------------|-----------------------| +| Configured TAC Indication | M | | ENUMERATED
(true, ...) | | + +### 9.3.1.88 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 [29] (leftmost 6 octets, with PLMN information encoded as in 9.3.1.14), and
Trace Recording Session Reference defined in TS 32.422 [29] (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 [29]. | - | - | +| Trace Collection Entity IP Address | M | | Transport Layer Address 9.3.2.3 | For File based Reporting.
Defined in TS 32.422 [29].
Should be ignored if URI is present. | - | - | +| MDT Configuration | O | | 9.3.1.150 | | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Trace Collection Entity URI | O | | URI
9.3.2.6 | For Streaming based Reporting. Defined in TS 32.422 [29] Replaces Trace Collection Entity IP Address if present | YES | ignore | + +### 9.3.1.89 Intended TDD DL-UL Configuration + +This IE contains the subcarrier spacing, cyclic prefix and TDD DL-UL slot configuration of an NR cell that the receiving gNB needs to take into account for cross-link interference mitigation, and/or for NR-DC power coordination, when operating its own cells. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------|----------|------------------|---------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| NR SCS | M | | ENUMERATED
(scs15, scs30, scs60, scs120, ..., scs 480, scs960) | The values scs15, scs30, scs60, scs120, scs480 and scs960 corresponds to the sub carrier spacing in TS 38.104 [17]. | - | | +| NR Cyclic Prefix | M | | ENUMERATED
(Normal, Extended, ...) | The type of cyclic prefix, which determines the number of symbols in a slot. | - | | +| NR DL-UL Transmission Periodicity | M | | ENUMERATED
(ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms3, ms4, ms5, ms10, ms20, ms40, ms60, ms80, ms100, ms120, ms140, ms160, ...) | The periodicity is expressed in the format msXpYZ, and equals X.YZ milliseconds. | - | | +| Slot Configuration List | | 1 | | | - | | +| >Slot Configuration List Item | | 1.. | | | - | | +| >>Slot Index | M | | INTEGER
(0..5119) | | - | | +| >>CHOICE Symbol Allocation in Slot | M | | | | - | | +| >>>All DL | | | NULL | This choice implies that all symbols in the slot are DL symbols. | - | | +| >>>All UL | | | NULL | This choice implies that all symbols in the slot are UL symbols. | - | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------|----------|-------|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>>Both DL and UL | | | | | - | | +| >>>>Number of DL Symbols | M | | INTEGER (0..13) | Number of consecutive DL symbols in the slot identified by Slot Index IE. If extended cyclic prefix is used, the maximum value is 11. The Permutation IE indicates the location of DL symbols in the slot. | - | | +| >>>>Number of UL Symbols | M | | INTEGER (0..13) | Number of consecutive UL symbols in the slot identified by Slot Index IE. If extended cyclic prefix is used, the maximum value is 11. The Permutation IE indicates the location of UL symbols in the slot. | - | | +| >>>>Permutation | O | | ENUMERATED (DFU, UFD, ...) | If not present, the default value is DFU. | YES | ignore | + +| Range bound | Explanation | +|--------------|---------------------------------------------------------------------| +| maxnoofslots | Maximum length of number of slots in a 10-ms period. Value is 5120. | + +### 9.3.1.90 Additional RRM Policy Index + +The *Additional RRM Policy Index* IE is used to provide additional information independent from the Subscriber Profile ID for RAT/Frequency priority as specified in TS 36.300 [20]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------|----------|-------|-----------------------|-----------------------| +| Additional RRM Policy Index | M | | BIT STRING (32) | | + +### 9.3.1.91 DU-CU RIM Information + +This IE conveys the Remote Interference Management message from the gNB-DU to the gNB-CU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------|----------|------------------------------|-----------------------------------------|--------------------------------------------------------| +| Victim gNB Set ID | M | | 9.3.1.93 | | +| RIM-RS Detection Status | M | | ENUMERATED(RS detected, RS disappeared) | This IE indicates detection status of RIM-RS in gNB-DU | +| Aggressor Cell List | | 1 | | | +| >Aggressor Cell List Item | | 1..<
maxCellingNB
DU > | | | +| >>Aggressor Cell ID | M | | NR CGI 9.3.1.12 | | + +| Range bound | Explanation | +|-----------------|-----------------------------------------------------------------| +| maxCellingNB DU | Maximum no. cells that can be served by a gNB-DU. Value is 512. | + +### 9.3.1.92 CU-DU RIM Information + +This IE conveys the Remote Interference Management message from the gNB-CU to the gNB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|-----------------------------------------|----------------------------------------------------------------| +| Victim gNB Set ID | M | | 9.3.1.93 | | +| RIM-RS Detection Status | M | | ENUMERATED(RS detected, RS disappeared) | This IE indicates detection status of RIM-RS in remote gNB(s). | + +### 9.3.1.93 gNB Set ID + +The gNB Set ID IE is used to identify a group of gNBs which transmit the same RIM-RS. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|--------------------------|-----------------------| +| gNB Set ID | M | | BIT STRING
(SIZE(22)) | | + +### 9.3.1.94 Lower Layer Presence Status Change + +This IE indicates lower layer resources' presence status shall be changed. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------|----------|-------|---------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Lower Layer Presence Status Change | M | | ENUMERATED
(suspend lower layers, resume lower layers ...) | "suspend lower layers" will store CellGroupConfig. From the parameters received within the ReconfigurationWithSync, only the sPCellConfigCommon is stored. "resume lower layers" shall restore SCG and it is set only after "suspend lower layers" has been indicated. | + +### 9.3.1.95 Traffic Mapping Information + +This IE includes the information used by the gNB-DU to perform traffic mapping. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------------|----------|-------|---------------------------------------------------------------|--------------------------------------------------------------------------------------------------| +| CHOICE Traffic Mapping Information Type | M | | | | +| >IP to layer2 Traffic Mapping Info | | | | | +| >>IP to layer2 Traffic Mapping Info To Add | O | | IP-to-layer-2 traffic mapping Information List
9.3.1.96 | This IE indicates the mapping information for forwarding of IP traffic to layer-2 to be added. | +| >>IP to layer2 Traffic Mapping Info To Remove | O | | Mapping Information to Remove
9.3.1.99 | This IE indicates the mapping information for forwarding of IP traffic to layer 2 to be removed. | +| >BAP layer BH RLC channel Mapping Info | | | | | +| >>BAP layer BH RLC channel Mapping Info To Add | O | | BAP layer BH RLC channel mapping Information List
9.3.1.98 | This IE indicates the mapping information for forwarding of traffic on BAP layer to be added. | +| >>BAP layer BH RLC channel Mapping Info To Remove | O | | Mapping Information to Remove
9.3.1.99 | This IE indicates the mapping information for forwarding of traffic on BAP layer to be removed. | + +### 9.3.1.96 IP-to-layer-2 traffic mapping Information List + +This IE includes the information used by the IAB-donor-DU to perform the mapping from IP layer to layer-2. If this IE appears in the UE-associated F1AP signalling, the *BH Information* IE should only contain the *BAP Routing ID* IE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------|----------|--------------------------------|-----------------------|-----------------------| +| IP-to-layer-2 mapping information Item | | 1..
| | | +| >Mapping Information Index | M | | 9.3.1.100 | | +| >IP header information | M | | 9.3.1.97 | | +| >BH Information | M | | 9.3.1.114 | | + +| Range bound | Explanation | +|-----------------------|---------------------------------------------------------------------------------| +| maxnoofMappingEntries | Maximum no. of mapping entries, the maximum value is 67108864 (i.e. $2^{26}$ ). | + +### 9.3.1.97 IP Header Information + +This IE indicates the IP header information included in the *Traffic Mapping Information* IE for DL traffic. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------| +| Destination IAB TNL Address | M | | 9.3.1.102 | This IE indicates the destination IPv4 address, or IPv6 address or IPv6 prefix of a DL packet. | +| DS Information List | | 0.. | | | + +| | | | | | +|-----------------|---|-----------------|-----------------------|------------------------------------------------------| +| | | | | | +| >DSCP | M | | BIT STRING (SIZE(6)) | This IE indicates the DS information of DL traffic. | +| IPv6 Flow Label | O | | BIT STRING (SIZE(20)) | This IE indicates the IPv6 Flow Label of DL traffic. | + +| Range bound | Explanation | +|---------------|-----------------------------------------------------------------------------------------------------------------------------------| +| maxnoofDSInfo | Maximum no. of DSCP values related to a destination IP address that can be mapped to one BH RLC channel, the maximum value is 64. | + +### 9.3.1.98 BAP layer BH RLC channel mapping Information List + +This IE includes the information used by the IAB-DU to perform the BH RLC channel mapping when forwarding traffic on BAP sublayer. + +When this IE is included in the UE-associated F1AP signalling for setting up or modifying a BH RLC channel, it contains either the *Prior-Hop BAP Address* IE and the *Ingress BH RLC CH ID* IE to configure a mapping in downlink direction, or the *Next-Hop BAP address* IE and the *Egress BH RLC CH ID* IE to configure a mapping in uplink direction. This IE indicates the BH RLC channel served by the collocated IAB-MT. + +When this IE is included in the non-UE-associated F1AP signalling, it shall contain the *Prior-Hop BAP Address* IE, the *Ingress BH RLC CH ID* IE, the *Next-Hop BAP address* IE and the *Egress BH RLC CH ID* IE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------------------|----------|--------------------------------|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| BAP layer BH RLC channel mapping info Item | | 1..
| | | - | | +| >Mapping Information Index | M | | 9.3.1.100 | | - | | +| >Prior-Hop BAP Address | O | | 9.3.1.111 | | - | | +| >Ingress BH RLC CH ID | O | | BH RLC Channel ID
9.3.1.113 | | - | | +| >Next-Hop BAP Address | O | | 9.3.1.111 | | - | | +| >Egress BH RLC CH ID | O | | BH RLC Channel ID
9.3.1.113 | | - | | +| >Ingress Non-F1-terminating IAB-donor Topology Indicator | O | | ENUMERATED (true, ...) | If present, indicates that the ingress topology for this entry is the non-F1-terminating IAB-donor topology of the boundary IAB-node. | YES | ignore | +| >Egress Non-F1-terminating IAB-donor Topology Indicator | O | | ENUMERATED (true, ...) | If present, indicates that the egress topology for this entry is the | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------------------------------------------------|-------------|----------------------| +| | | | | non-F1-terminating IAB-donor topology of the boundary IAB-node. | | | + +| Range bound | Explanation | +|-----------------------|----------------------------------------------------------------------------------------| +| maxnoofMappingEntries | Maximum no. of mapping entries, the maximum value is 67108864 (i.e. 2 26 ). | + +### 9.3.1.99 Mapping Information to Remove + +This IE includes a list of mapping information indexes corresponding to the mapping configuration which is to be removed. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------------------|----------|--------------------------------|-----------------------|-----------------------| +| Mapping Information to Remove List Item | | 1..
| | | +| >Mapping Information Index | M | | 9.3.1.100 | | + +| Range bound | Explanation | +|-----------------------|----------------------------------------------------------------------------------------| +| maxnoofMappingEntries | Maximum no. of mapping entries, the maximum value is 67108864 (i.e. 2 26 ). | + +### 9.3.1.100 Mapping Information Index + +This IE includes an index of one mapping information entry at the IAB-donor-DU or an IAB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------|-----------------------| +| Mapping Information Index | M | | BIT STRING (SIZE(26)) | | + +### 9.3.1.101 IAB TNL Addresses Requested + +The *IAB TNL Addresses Requested* IE indicates the number of IPv4 or IPv6 addresses or IPv6 address prefixes requested for the indicated usage. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------| +| TNL Addresses or Prefixes Requested - All Traffic | O | | INTEGER (1..256) | The number of TNL addresses/IPv6 prefixes requested for all traffic. | +| TNL Addresses or Prefixes Requested - F1-C traffic | O | | INTEGER (1..256) | The number of TNL addresses/IPv6 prefixes requested for F1-C traffic. | +| TNL Addresses or Prefixes Requested - F1-U traffic | O | | INTEGER (1..256) | The number of TNL addresses/IPv6 prefixes requested for F1-U traffic. | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------| +| | | | | traffic. | +| TNL Addresses or Prefixes Requested - Non-F1 traffic | O | | INTEGER (1..256) | The number of TNL addresses/ IPv6 prefixes requested for non-F1 traffic. | + +### 9.3.1.102 IAB TNL Address + +The *IAB TNL Address* IE indicates an IPv4 or IPv6 address or an IPv6 address prefix assigned to an IAB-node. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------|----------|-------|------------------------|---------------------------------------------------| +| CHOICE IAB TNL Address | M | | | | +| >IPv4 Address | | | | | +| >>IPv4 Address | M | | BIT STRING (SIZE(32)) | The IPv4 address allocated to an IAB-node. | +| >IPv6 Address | | | | | +| >>IPv6 Address | M | | BIT STRING (SIZE(128)) | The IPv6 address allocated to an IAB-node. | +| >IPv6 Prefix | | | | | +| >>IPv6 Prefix | M | | BIT STRING (SIZE(64)) | The IPv6 address prefix allocated to an IAB-node. | + +### 9.3.1.103 Uplink BH Non-UP Traffic Mapping + +This IE indicates the mapping of uplink non-UP traffic to a BH RLC channel and BAP Routing ID. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------|----------|------------------------------------|-----------------------|-----------------------| +| Uplink Non-UP Traffic Mapping List | | 1 | | | +| >Uplink Non-UP Traffic Mapping List Item IEs | | 1 .. | | | +| >>Non-UP Traffic Type | M | | 9.3.1.104 | | +| >>BH Information | M | | 9.3.1.114 | | + +| Range bound | Explanation | +|-----------------------------|------------------------------------------------------| +| maxnoofNonUPTrafficMappings | Maximum no. of non-UP traffic mappings. Value is 32. | + +### 9.3.1.104 Non-UP Traffic Type + +This IE indicates the type of non-UP traffic. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|--------------------------------------------------------------------------------------|-----------------------| +| Non-UP Traffic Type | M | | ENUMERATED(UE-associated F1AP, non-UE-associated F1AP, non-F1, BAP control PDU, ...) | | + +### 9.3.1.105 IAB Info IAB-donor-CU + +This IE contains cell-specific IAB-related information sent by an IAB-donor-CU to an IAB-DU or IAB-donor-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-------------------------------------------------------| +| IAB STC Info | O | | 9.3.1.109 | Contains STC configuration of IAB-DU or IAB-donor-DU. | + +### 9.3.1.106 IAB Info IAB-DU + +This IE contains cell-specific IAB-related information sent by an IAB-DU or IAB-donor-DU to an IAB-donor-CU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------| +| Multiplexing Info | O | | 9.3.1.108 | Contains the information about multiplexing with cells configured for a collocated IAB-MT. Applicable for an IAB-DU. | +| IAB STC Info | O | | 9.3.1.109 | Contains the information about STC configuration of IAB-DU or IAB-donor-DU. | + +### 9.3.1.107 gNB-DU Cell Resource Configuration + +This IE contains the resource configuration of the cells served by a gNB-DU, i.e. the TDD/FDD resource parameters for each activated cell (TS 38.213 [31], clause 11.1.1). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------|----------|-----------------------|-------------------------------------------------------------------------------|--------------------------------------------------------------------------|-------------|----------------------| +| Subcarrier Spacing | M | | ENUMERATED (kHz15, kHz30, kHz60, kHz120, kHz240, spare3, spare2, spare1, ...) | Subcarrier spacing used as reference for the TDD/FDD slot configuration. | - | | +| DUF Transmission Periodicity | O | | ENUMERATED (ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10, ...) | | - | | +| DUF Slot Configuration List | | 0..1 | | | - | | +| >DUF Slot Configuration Item | | 1.. | | The maxNrofSlots in TS 38.331 [8]. | - | | +| >>CHOICE DUF Slot Configuration | M | | | | - | | +| >>>Explicit Format | | | | | | | +| >>>>Permutation | M | | ENUMERATED (DFU, UFD, ...) | | - | | +| >>>>Number of Downlink Symbols | O | | INTEGER (0..14) | | - | | +| >>>>Number of Uplink Symbols | O | | INTEGER (0..14) | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------------|----------|-----------------------------|-----------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>> Implicit Format | | | | | | | +| >>>>DUF Slot Format Index | M | | INTEGER (0..254) | Index into Table 11.1.1-1 and Table 14-2 in TS 38.213 [31], excluding the last row in Table 14-2. | - | | +| HSNA Transmission Periodicity | M | | ENUMERATED (ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10, ms20, ms40, ms80, ms160, ...) | | - | | +| HSNA Slot Configuration List | | 0..1 | | | - | | +| > HSNA Slot Configuration Item | | 1.. | | | - | | +| >>HSNA Downlink | O | | ENUMERATED (HARD, SOFT, NOTAVAILABLE) | HSNA value for downlink symbols in a slot. | - | | +| >>HSNA Uplink | O | | ENUMERATED (HARD, SOFT, NOTAVAILABLE) | HSNA value for uplink symbols in a slot. | - | | +| >>HSNA Flexible | O | | ENUMERATED (HARD, SOFT, NOTAVAILABLE) | HSNA value for flexible symbols in a slot. | - | | +| RB Set Configuration | O | | 9.3.1.230 | | YES | reject | +| Frequency-Domain HSNA Configuration List | | 0..1 | | | YES | reject | +| > Frequency-Domain HSNA Configuration Item | | 1.. | | | EACH | reject | +| >>RB Set Index | M | | INTEGER (0..maxnoofRBsets PerCell-1, ...) | Refers to an RB set defined by RB Set Configuration. The RB set indices are consecutive (and increasing) starting at 0. | - | | +| >>Frequency-Domain HSNA Slot Configuration List | | 1 | | | - | | +| >>>Frequency-Domain HSNA Slot Configuration Item | | 1.. | | | - | | +| >>>>Slot Index | O | | INTEGER (0..5119) | Indicates an index to a slot within the HSNA Transmission Periodicity. | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------|----------|------------------------------|---------------------------------------|-------------------------------------------------------------------------------------------|-------------|----------------------| +| >>>>HSNA Downlink | O | | ENUMERATED (HARD, SOFT, NOTAVAILABLE) | HSNA value for downlink symbols in a slot, for an RB set. | - | | +| >>>>HSNA Uplink | O | | ENUMERATED (HARD, SOFT, NOTAVAILABLE) | HSNA value for uplink symbols in a slot, for an RB set. | - | | +| >>>>HSNA Flexible | O | | ENUMERATED (HARD, SOFT, NOTAVAILABLE) | HSNA value for flexible symbols in a slot, for an RB set. | - | | +| Child IAB-Nodes NA Resource List | | 0..1 | | List of child IAB-nodes served by the IAB-DU or IAB-donor-DU. | YES | reject | +| >Child IAB-Nodes NA Resource List Item | | 1 .. | | | EACH | reject | +| >>gNB-CU UE F1AP ID | M | | 9.3.1.4 | Identifier of a child-node IAB-MT at the IAB-donor-CU. | - | | +| >>gNB-DU UE F1AP ID | M | | 9.3.1.5 | Identifier of a child-node IAB-MT at an IAB-DU or IAB-donor-DU. | - | | +| >>NA Resource Configuration List | | 0..1 | | List of not-available resources of this cell for this child IAB-node | - | | +| >>>NA Resource Configuration Item | | 1.. | | | - | | +| >>>>NA Downlink | O | | ENUMERATED (true, false, ...) | Indicates whether downlink symbols, in a slot, are available to serve the child IAB-node. | - | | +| >>>>NA Uplink | O | | ENUMERATED (true, false, ...) | Indicates whether uplink symbols, in a slot, are available to serve the child IAB-node. | - | | +| >>>>NA Flexible | O | | ENUMERATED (true, false, ...) | Indicates whether flexible symbols, in a slot, are available to serve the child IAB- | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------------------|----------|-----------------------|-------------------------------|---------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | node. | | | +| Parent IAB Nodes NA Resource Configuration List | | 0..1 | | List of unavailable resources of this cell for this IAB-node. | YES | reject | +| >Parent IAB Nodes NA Resource Configuration Item | | 1.. | | | EACH | reject | +| >>NA Downlink | O | | ENUMERATED (true, false, ...) | Indicates whether downlink symbols, in a slot, are unavailable to serve the IAB-node. | - | | +| >>NA Uplink | O | | ENUMERATED (true, false, ...) | Indicates whether uplink symbols, in a slot, are unavailable to serve the IAB-node. | - | | +| >>NA Flexible | O | | ENUMERATED (true, false, ...) | Indicates whether flexible symbols, in a slot, are unavailable to serve the IAB-node. | - | | + +| Range bound | Explanation | +|------------------------|--------------------------------------------------------------------------------------| +| maxnoofDUFSlots | Maximum no. of slots in 10ms. Value is 320. | +| maxnoofSymbols | Maximum no. of symbols in a slot. Value is 14. | +| maxnoofHSNASlots | Maximum no of "Hard", "Soft" or "Not available" slots in 160ms. Value is 5120. | +| maxnoofRBsetsPerCell | Maximum no. of RB sets per IAB-DU cell. Value is 8 | +| maxnoofRBsetsPerCell-1 | Maximum no. of RB sets per IAB-DU cell minus 1. Value is 7 | +| maxnoofChildIABNodes | Maximum number of child nodes served by an IAB-DU or an IAB-donor-DU. Value is 1024. | + +### 9.3.1.108 Multiplexing Info + +This IE contains information about the multiplexing capabilities between the gNB-DU's cell and the cells configured on the co-located IAB-MT. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------|----------|----------------------------|-----------------------|---------------------------------------------------------------------|-------------|----------------------| +| IAB-MT Cell List | | 1 | | | - | | +| >IAB-MT Cell Item | | 1 .. | | | - | | +| >>NR Cell Identity | M | | BIT STRING (SIZE(36)) | Cell identity of a serving cell configured for a co-located IAB-MT. | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|-------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>DU_RX/MT_RX | M | | ENUMERATED (supported, not supported) | An indication of whether the IAB-node supports simultaneous reception at its DU and MT side. | - | | +| >>DU_TX/MT_TX | M | | ENUMERATED (supported, not supported) | An indication of whether the IAB-node supports simultaneous transmission at its DU and MT side. | - | | +| >>DU_RX/MT_TX | M | | ENUMERATED (supported, not supported) | An indication of whether the IAB-node supports simultaneous reception at its DU and transmission at its MT side. | - | | +| >>DU_TX/MT_RX | M | | ENUMERATED (supported, not supported) | An indication of whether the IAB-node supports simultaneous transmission at its DU and reception at its MT side. | - | | +| >>DU_RX/MT_RX_extend | MO | | ENUMERATED (supported, not supported, supported and FDM required) | An indication of whether the IAB-node supports simultaneous reception at its DU and MT side. If present, the DU_RX/MT_RX IE shall be ignored. | YES | ignore | +| >>DU_TX/MT_TX_extend | O | | ENUMERATED (supported, not supported, supported and FDM required) | An indication of whether the IAB-node supports simultaneous transmission at its DU and MT side. If present, the DU_TX/MT_TX IE shall be ignored. | YES | ignore | +| >>DU_RX/MT_TX_extend | O | | ENUMERATED (supported, not supported, supported and FDM required) | An indication of whether the IAB-node supports simultaneous reception at its DU and transmission at its MT side. If present, the DU_RX/MT_TX IE shall be ignored. | YES | ignore | +| >>DU_TX/MT_RX_extend | O | | ENUMERATED (supported, not supported, supported and FDM required) | An indication of whether the IAB-node supports simultaneous transmission at its DU and reception at its MT side. If present, the DU_TX/MT_RX IE shall be ignored. | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------------|--------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | supported and FDM required) | simultaneous transmission at its DU and reception at its MT side. If present, the DU_TX/MT_RX IE shall be ignored. | | | + +| Range bound | Explanation | +|---------------------|----------------------------------------------------------------------------------------------------------------------| +| maxnoofServingCells | Maximum no. of serving cells for IAB-MT. Value is 32, as defined by the maxNrofServingCells in TS 38.331 [8]. | + +### 9.3.1.109 IAB STC Info + +This IE contains cell SSB Transmission Configuration (STC) information of an IAB-DU or IAB-donor-DU. The information is used by neighbour IAB-MTs for discovery and measurements of this IAB-DU or IAB-donor-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------|----------|-------------------------|------------------------------------------------------------------------|----------------------------------------------------------| +| IAB STC-Info List | | 1 | | | +| > IAB STC-Info Item | | 1 .. | | | +| >>SSB Frequency Info | M | | INTEGER (0..maxNRARFCN) | The SSB central frequency. | +| >>SSB Subcarrier Spacing | M | | ENUMERATED (kHz15, kHz30, kHz120, kHz240, spare3, spare2, spare1, ...) | The SSB subcarrier spacing. | +| >>SSB Transmission Periodicity | M | | ENUMERATED (sf5, sf10, sf20, sf40, sf80, sf160, sf320, sf640, ...) | | +| >>SSB Transmission Timing Offset | M | | INTEGER (0.. 127, ...) | SSB transmission timing offset in number of half-frames. | +| >>CHOICE SSB Transmission Bitmap | M | | | The SSB- ToMeasure IE defined in TS 38.331 [8]. | +| >>>Short Bitmap | | | | | +| >>>>Short Bitmap | M | | BIT STRING (SIZE (4)) | | +| >>>Medium Bitmap | | | | | +| >>>>Medium Bitmap | M | | BIT STRING (SIZE (8)) | | +| >>>Long Bitmap | | | | | +| >>>>Long Bitmap | M | | BIT STRING (SIZE (64)) | | + +| Range bound | Explanation | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------| +| maxnoofIABSTCInfo | Maximum no. of STC configurations. Value is 5. This includes 1 STC configuration for access and 4 STC configurations for backhaul. | +| maxNRARFCN | Maximum value of NR ARFCNs. Value is 3279165. | + +### 9.3.1.110 BAP Routing ID + +This IE indicates the BAP Routing ID. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|--------------------------|-----------------------| +| BAP Address | M | | 9.3.1.111 | | +| Path ID | M | | BAP Path ID
9.3.1.112 | | + +### 9.3.1.111 BAP Address + +This IE indicates the BAP address of an IAB-node or of an IAB-donor-DU, and it is part of the BAP Routing ID. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BAP Address | M | | BIT STRING
(SIZE(10)) | Corresponds to the bap-Address contained in the RRCReconfiguration message or contained in the BAP-RoutingID IE, or the iab-donor-DU-BAP-Address contained in the RRCReconfiguration message defined TS 38.331[8]. | + +### 9.3.1.112 BAP Path ID + +This IE indicates the BAP path ID, which is part of the BAP Routing ID. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|--------------------------|----------------------------------------------------------------------------------------------------------------------------| +| BAP Path ID | M | | BIT STRING
(SIZE(10)) | Corresponds to the bap-Pathid contained in the BAP-RoutingID IE defined in subclause 6.3.2 of TS 38.331 [8]. | + +### 9.3.1.113 BH RLC Channel ID + +This IE uniquely identifies a BH RLC channel in the link between IAB-MT of the IAB-node and IAB-DU of the parent IAB-node or IAB-donor-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|--------------------------|-----------------------| +| BH RLC CH ID | M | | BIT STRING
(SIZE(16)) | | + +### 9.3.1.114 BH Information + +This IE includes the backhaul information for UL or DL. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|------------------------------|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| BAP Routing ID | O | | 9.3.1.110 | This IE is not needed for the BAP control PDU. For UL F1-U traffic, the BAP address included in this IE also indicates the IAB-donor-DU via which the DL traffic is transmitted. | - | | +| Egress BH RLC CH List | | 0..1 | | | - | | +| >Egress BH RLC CH List Item | | 1..
| | | - | | +| >>Next-Hop BAP Address | M | | 9.3.1.111 | This IE identifies the next-hop node on the backhaul path to receive the packet. The value of this IE should be unique in the whole list. | - | | +| >>Egress BH RLC CH ID | M | | BH RLC Channel ID
9.3.1.113 | This IE identifies the BH RLC channel in the link between the IAB node/IAB-donor-DU and the node identified by the Next-Hop BAP Address IE. | - | | +| Non-F1-Terminating IAB-donor Topology Indicator | O | | ENUMERATED
(true, ...) | If present, indicates that the Next-Hop BAP Address and Egress BH RLC CH ID contained in this IE pertain to the non-F1-terminating IAB-donor topology of the boundary IAB-node. | YES | ignore | + +| Range bound | Explanation | +|--------------------|------------------------------------------| +| maxnoofEgressLinks | Maximum no. of egress links. Value is 2. | + +### 9.3.1.115 Control Plane Traffic Type + +This IE indicates the control plane traffic type carried over a BH RLC channel. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| Control Plane Traffic Type | M | | INTEGER (1..3, ...) | Control plane traffic types with different priorities are identified by the different codepoints in this IE, where 1 has the highest priority. | + +### 9.3.1.116 NR V2X Services Authorized + +This IE provides information on the authorization status of the UE to use the NR sidelink for V2X services. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|----------------------------------------------|----------------------------------------------------------| +| Vehicle UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized as Vehicle UE. | +| Pedestrian UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized as Pedestrian UE. | + +### 9.3.1.117 LTE V2X Services Authorized + +This IE provides information on the authorization status of the UE to use the LTE sidelink for V2X services. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|----------------------------------------------|----------------------------------------------------------| +| Vehicle UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized as Vehicle UE. | +| Pedestrian UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized as Pedestrian UE. | + +### 9.3.1.118 LTE UE Sidelink Aggregate Maximum Bit Rate + +This IE provides information on the Aggregate Maximum Bitrate of the UE's communication over LTE sidelink. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------| +| LTE UE Sidelink Aggregate Maximum Bit Rate | M | | Bit Rate 9.3.1.4 | Value 0 shall be considered as a logical error by the receiving gNB-DU. | + +### 9.3.1.119 NR UE Sidelink Aggregate Maximum Bit Rate + +This IE provides information on the Aggregate Maximum Bitrate of the UE's communication over NR sidelink. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------| +| NR UE Sidelink Aggregate Maximum Bit Rate | M | | Bit Rate
9.3.1.4 | Value 0 shall be considered as a logical error by the receiving gNB-DU. | + +### 9.3.1.120 SL DRB ID + +This IE uniquely identifies a SL DRB for a UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------|----------------------------------------------------------------------------| +| SL DRB ID | M | | INTEGER (1.. 512, ...) | Corresponds to the SLRB-Uu-ConfigIndex IE defined in TS 38.331 [8]. | + +### 9.3.1.121 PC5 QoS Flow Identifier + +This IE uniquely identifies one sidelink QoS flow between the UE and the network in the scope of UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------| +| PC5 QoS Flow Identifier | M | | INTEGER (1.. 2048) | Corresponds to the SL-QoS-FlowIdentity IE defined in TS 38.331 [8]. | + +### 9.3.1.122 PC5 QoS Parameters + +This IE defines the QoS to be applied to a SL DRB. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------|-------------|----------------------| +| CHOICE PC5 QoS Characteristics | M | | | | - | | +| > Non-dynamic PQI | | | | | - | | +| >>Non Dynamic PQI Descriptor | M | | 9.3.1.126 | | - | | +| > Dynamic PQI | | | | | - | | +| >>Dynamic PQI Descriptor | M | | 9.3.1.127 | | - | | +| PC5 QoS Flow Bit Rates | O | | | Only applies for GBR QoS Flows. | - | | +| >Guaranteed Flow Bit Rate | M | | Bit Rate
9.3.1.22 | Guaranteed Bit Rate for the PC5 QoS flow. Details in TS 23.287 [40]. | - | | +| >Maximum Flow Bit Rate | M | | Bit Rate
9.3.1.22 | Maximum Bit Rate for the PC5 QoS flow. Details in TS 23.287 [40]. | - | | + +| Range bound | Explanation | +|--------------------|---------------------------------------------------------------------------------------------------------------| +| maxnoofPC5QoSFlows | Maximum no. of PC5 QoS flows allowed towards one UE for NR sidelink communication, the maximum value is 2048. | + +### 9.3.1.123 Alternative QoS Parameters Set Index + +This IE indicates the QoS parameters set which can currently be fulfilled. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Alternative QoS Parameters Set Index | M | | INTEGER (1..8, ...) | Indicates the index of the item within the Alternative QoS Parameters Set List IE corresponding to the currently fulfilled alternative QoS parameters set. | + +### 9.3.1.124 Alternative QoS Parameters Set Notify Index + +This IE indicates the QoS parameters set which can currently be fulfilled. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Alternative QoS Parameters Set Notify Index | M | | INTEGER (0..8, ...) | Indicates the index of the item within the the Alternative QoS Parameters Set List IE corresponding to the currently fulfilled alternative QoS parameters set. Value 0 indicates that NG-RAN cannot even fulfil the lowest alternative parameter set. | + +### 9.3.1.125 Alternative QoS Parameters Set List + +This IE contains alternative sets of QoS parameters which the gNB 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 Set Item | | 1.. | | | +| >Alternative QoS Parameters Set Index | M | | 9.3.1.123 | | +| >Guaranteed Flow Bit Rate Downlink | O | | Bit Rate 9.3.1.22 | | +| >Guaranteed Flow Bit Rate Uplink | O | | Bit Rate 9.3.1.22 | | +| >Packet Delay Budget | O | | 9.3.1.51 | | +| >Packet Error Rate | O | | 9.3.1.52 | | + +| Range bound | Explanation | +|--------------------|--------------------------------------------------------------------------------------------| +| maxnoofQoSParaSets | Maximum no. of alternative sets of QoS Parameters allowed for the QoS profile. Value is 8. | + +### 9.3.1.126 Non Dynamic PQI Descriptor + +This IE indicates the QoS Characteristics for a standardized or pre-configured PQI for sidelink. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------| +| 5QI | M | | INTEGER (0..255,...) | This IE contains the standardized or pre-configured PQI as specified in TS 23.287 [40] | +| QoS Priority Level | O | | INTEGER (1..8,...) | For details see TS 23.501 [21]. When included overrides standardized or pre-configured value. | +| Averaging Window | O | | 9.3.1.53 | For details see TS 23.501 [21]. When included overrides standardized or pre-configured value. | +| Maximum Data Burst Volume | O | | 9.3.1.54 | For details see TS 23.501 [21]. When included overrides standardized or pre-configured value. | + +### 9.3.1.127 Dynamic PQI Descriptor + +This IE indicates the QoS Characteristics for a Non-standardised or not pre-configured PQI for sidelink. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|-------------|-------|----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| Resource Type | O | | ENUMERATED (GBR, non-GBR, delay critical GBR, ...) | | +| QoS Priority Level | M | | INTEGER (1..8, ...) | For details see TS 23.501 [21]. | +| Packet Delay Budget | M | | 9.3.1.51 | For details see TS 23.501 [21]. | +| Packet Error Rate | M | | 9.3.1.52 | For details see TS 23.501 [21]. | +| Averaging Window | C-ifGBRflow | | 9.3.1.53 | For details see TS 23.501 [21]. | +| Maximum Data Burst Volume | O | | 9.3.1.54 | For details see TS 23.501 [21]. This IE shall be included if the Delay Critical IE is set to "delay critical" and is ignored otherwise. | + +| Condition | Explanation | +|-----------|------------------------------------------------------------------------------------------------------------------| +| ifGBRflow | This IE shall be present if the PC5 QoS Flow Bit Rates IE is present in the PC5 QoS parameters IE. | + +### 9.3.1.128 TNL Capacity Indicator + +The *TNL Capacity Indicator* IE indicates the offered and available capacity of the Transport Network experienced by the gNB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------|----------|-------|-----------------------|-----------------------------| +| DL TNL Offered Capacity | M | | INTEGER (1.. | Maximum capacity offered by | + +| | | | | | +|---------------------------|---|--|---------------------------|-----------------------------------------------------------------------------------------------------------------------------| +| | | | 16777216,...) | the transport portion of the gNB-DU – gNB-CU in kbps | +| DL TNL Available Capacity | M | | INTEGER (0..100,...) | Available capacity over the transport portion serving the node in percentage. Value 100 corresponds to the offered capacity | +| UL TNL Offered Capacity | M | | INTEGER (1..16777216,...) | Maximum capacity offered by the transport portion of the gNB-DU – gNB-CU in kbps | +| UL TNL Available Capacity | M | | INTEGER (0..100,...) | Available capacity over the transport portion serving the node in percentage. Value 100 corresponds to the offered capacity | + +### 9.3.1.129 Radio Resource Status + +The *Radio Resource Status* IE indicates the usage of the PRBs per cell for MIMO, per SSB area and per slice for all traffic in Downlink and Uplink and the usage of PDCCH CCEs for Downlink and Uplink scheduling. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|-----------------------|-----------------------|-------------------------------------------------------------------------------|-------------|----------------------| +| SSB Area Radio Resource Status List | | 1 | | | - | | +| > SSB Area Radio Resource Status Item | | 1.. | | | - | | +| >>SSB Index | M | | INTEGER (0..63) | | - | | +| >>SSB Area DL GBR PRB usage | M | | INTEGER (0..100) | Per SSB area DL GBR PRB usage in percentage of the cell total PRB number. | - | | +| >>SSB Area UL GBR PRB usage | M | | INTEGER (0..100) | Per SSB area UL GBR PRB usage in percentage of the cell total PRB number. | - | | +| >>SSB Area DL non-GBR PRB usage | M | | INTEGER (0..100) | Per SSB area DL non-GBR PRB usage in percentage of the cell total PRB number. | - | | +| >>SSB Area UL non-GBR PRB usage | M | | INTEGER (0..100) | Per SSB area UL non-GBR PRB usage in percentage of the cell total PRB number. | - | | +| >>SSB Area DL Total PRB usage | M | | INTEGER (0..100) | Per SSB area DL Total PRB usage in percentage of the cell total PRB number. | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------|----------|------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>SSB Area UL Total PRB usage | M | | INTEGER (0..100) | Per SSB area UL Total PRB usage in percentage of the cell total PRB number. | - | | +| >>DL scheduling PDCCH CCE usage | O | | INTEGER (0..100) | | - | | +| >>UL scheduling PDCCH CCE usage | O | | INTEGER (0..100) | | - | | +| Slice Radio Resource List | | 0..1 | | | YES | ignore | +| >Slice Radio Resource Item | | 1.. | | | - | | +| >>PLMN Identity | M | | 9.3.1.14 | Broadcast PLMN | - | | +| >>>S-NSSAI Radio Resource Status List | | 1 | | | - | | +| >>>>S-NSSAI Radio Resource Status Item | | 1.. | | | - | | +| >>>>>S-NSSAI | M | | 9.3.1.38 | | - | | +| >>>>>S-NSSAI DL GBR PRB usage | M | | INTEGER (0..100) | Per slice DL GBR PRB usage in percentage of the cell total PRB number. | - | | +| >>>>>S-NSSAI UL GBR PRB usage | M | | INTEGER (0..100) | Per slice UL GBR PRB usage for this slice in percentage of the cell total PRB number. | - | | +| >>>>>S-NSSAI DL non-GBR PRB usage | M | | INTEGER (0..100) | Per slice DL non-GBR PRB usage for this slice in percentage of the cell total PRB number. | - | | +| >>>>>S-NSSAI UL non-GBR PRB usage | M | | INTEGER (0..100) | Per slice UL non-GBR PRB usage for this slice in percentage of the cell total PRB number. | - | | +| >>>>>Slice DL Total PRB allocation | M | | INTEGER (0..100) | Total amount of DL PRBs available per cell for this slice if all the resources the slice could access were usable. | - | | +| >>>>>Slice UL Total PRB allocation | M | | INTEGER (0..100) | Total amount of UL PRBs available per cell for this slice if all the resources the slice | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | could access were usable. | | | +| MIMO PRB usage Information | O | | | | YES | ignore | +| >DL GBR PRB usage for MIMO | M | | INTEGER (0..100) | Per cell DL GBR PRB usage for MIMO in percentage of the cell total PRB number as defined in TS 38.314 [32]. | - | | +| >UL GBR PRB usage for MIMO | M | | INTEGER (0..100) | Per cell UL GBR PRB usage for MIMO in percentage of the cell total PRB number as defined in TS 38.314 [32]. | - | | +| >DL non-GBR PRB usage for MIMO | M | | INTEGER (0..100) | Per cell DL non-GBR PRB usage for MIMO in percentage of the cell total PRB number as defined in TS 38.314 [32]. | - | | +| >UL non-GBR PRB usage for MIMO | M | | INTEGER (0..100) | Per cell UL non-GBR PRB usage for MIMO in percentage of the cell total PRB number as defined in TS 38.314 [32]. | - | | +| >DL Total PRB usage for MIMO | M | | INTEGER (0..100) | Per cell DL Total PRB usage for MIMO in percentage of the cell total PRB number as defined in TS 38.314 [32]. | - | | +| >UL Total PRB usage for MIMO | M | | INTEGER (0..100) | Per cell UL Total PRB usage for MIMO in percentage of the cell total PRB number as defined in TS 38.314 [32]. | - | | + +| Range bound | Explanation | +|-------------------|------------------------------------------------------------------| +| maxnoofSSBAreas | Maximum no. SSB Areas that can be served by a cell. Value is 64. | +| maxnoofSliceItems | Maximum no. of signalled slice support items. Value is 1024. | +| maxnoofBPLMNsNR | Maximum no. of PLMN Ids.broadcast in a cell. Value is 12. | + +### 9.3.1.130 Composite Available Capacity Group + +The *Composite Available Capacity Group* IE indicates the overall available resource level per cell and per SSB area in the cell in Downlink and Uplink. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------------------|----------|-------|----------------------------------------|-----------------------------------------------------------|-------------|----------------------| +| Composite Available Capacity Downlink | M | | Composite Available Capacity 9.3.1.131 | For the Downlink | - | | +| Composite Available Capacity Uplink | M | | Composite Available Capacity 9.3.1.131 | For the Uplink, including both NUL and SUL (if available) | - | | +| Composite Available Capacity Supplementary Uplink | O | | Composite Available Capacity 9.3.1.131 | For the SUL | YES | ignore | + +### 9.3.1.131 Composite Available Capacity + +The *Composite Available Capacity* IE indicates the overall available resource level in the cell in either Downlink or Uplink. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------|---------------------------------------------------------------------| +| Cell Capacity Class Value | O | | 9.3.1.132 | | +| Capacity Value | M | | 9.3.1.133 | '0' indicates no resource is available, Measured on a linear scale. | + +### 9.3.1.132 Cell Capacity Class Value + +The *Cell Capacity Class Value* IE indicates the value that classifies the cell capacity with regards to the other cells. The *Cell Capacity Class Value* IE only indicates resources that are configured for traffic purposes. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Capacity Class Value | M | | INTEGER (1..100,...) | Value 1 shall indicate the minimum cell capacity, and 100 shall indicate the maximum cell capacity. There should be a linear relation between cell capacity and Cell Capacity Class Value. | + +### 9.3.1.133 Capacity Value + +The *Capacity Value* IE indicates the amount of resources per cell and per SSB area that are available relative to the total gNB-DU resources. The capacity value should be measured and reported so that the minimum gNB-DU resource usage of existing services is reserved according to implementation. The *Capacity Value* IE can be weighted according to the ratio of cell capacity class values, if available. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +|---------------|----------|-------|-----------------------|-----------------------| + +| | | | | | +|-------------------------------------|---|---------------------|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Capacity Value | M | | INTEGER (0..100) | Value 0 shall indicate no available capacity, and 100 shall indicate maximum available capacity with respect to the whole cell. Capacity Value should be measured on a linear scale. | +| SSB Area Capacity Value List | | 0..1 | | | +| >SSB Area Capacity Value Item | | 1.. | | | +| >>SSB Index | M | | INTEGER (0..63) | | +| >>SSB Area Capacity Value | M | | INTEGER (0..100) | Value 0 shall indicate no available capacity, and 100 shall indicate maximum available capacity . SSB Area Capacity Value should be measured on a linear scale. | + +| Range bound | Explanation | +|-----------------|------------------------------------------------------------------| +| maxnoofSSBAreas | Maximum no. SSB Areas that can be served by a cell. Value is 64. | + +### 9.3.1.134 Slice Available Capacity + +The *Slice Available Capacity* IE indicates the amount of resources per network slice that are available per cell relative to the total gNB-DU resources per cell. The *Slice Available Capacity Value Downlink* IE and the *Slice Available Capacity Value Uplink* IE can be weighted according to the ratio of the corresponding cell capacity class values contained in the *Composite Available Capacity Group* IE, if available. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------|----------|--------------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Slice Available Capacity List | | 1 | | | +| >Slice Available Capacity Item | | 1.. | | | +| >>PLMN Identity | M | | 9.3.1.14 | Broadcast PLMN | +| >>S-NSSAI Available Capacity List | | 1 | | | +| >>>S-NSSAI Available Capacity Item | M | 1 .. | | | +| >>>>S-NSSAI | | | 9.3.1.38 | | +| >>>>Slice Available Capacity Value Downlink | O | | INTEGER (0..100) | Value 0 shall indicate no available capacity, and 100 shall indicate maximum available capacity . Slice Available Capacity Value Downlink should be measured on a linear scale. | +| >>>>Slice Available Capacity Value Uplink | O | | INTEGER (0..100) | Value 0 shall indicate no available capacity, and 100 shall indicate maximum available capacity . Slice Available Capacity Value Uplink should be measured on a linear scale. | + +| Range bound | Explanation | +|-----------------|--------------------------------------------------------------| +| maxnooSlicItems | Maximum no. of signalled slice support items. Value is 1024. | +| maxnoofBPLMNsNR | Maximum no. of PLMN Ids.broadcast in a cell. Value is 12. | + +### 9.3.1.135 Number of Active UEs + +The *Number of Active UEs* IE indicates the mean number of active UEs as defined in TS 38.314 [32]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Mean number of Active UEs | M | | INTEGER (0..16777215, ...) | As defined in TS 38.314 [32] and where value "1" is equivalent to 0.1 Active UEs, value "2" is equivalent to 0.2 Active UEs, value n is equivalent to n /10 Active UEs. | + +### 9.3.1.136 Hardware Load Indicator + +The *Hardware Load Indicator* IE indicates the status of the Hardware Load. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------|----------|-------|-----------------------|------------------------------------| +| DL Hardware Load Indicator | M | | INTEGER (0..100) | This indicates the load in percent | +| UL Hardware Load Indicator | M | | INTEGER (0..100) | This indicates the load in percent | + +### 9.3.1.137 NR Carrier List + +This IE indicates the SCS-specific carriers per TDD, per DL, per UL or per SUL of an NR cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|--------------------|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NR Carrier Item | | 1.. | | | +| >NR SCS | M | | ENUMERATED (scs15, scs30, scs60, scs120, ..., scs480, scs960) | SCS for the corresponding carrier. | +| >Offset to Carrier | M | | INTEGER (0.. 2199, ...) | Offset in frequency domain between Point A (lowest subcarrier of common RB 0) and the lowest usable subcarrier on this carrier in number of PRBs (using the NR SCS IE defined for this carrier). The maximum value corresponds to $275 \times 8 - 1$ . See TS 38.211 [33], clause 4.4.2. | +| >Carrier Bandwidth | M | | INTEGER (1..maxnoofPhysicalResourceBlocks, ...) | Width of this carrier in number of PRBs (using the NR SCS IE defined for this carrier). See TS 38.211 [33], clause 4.4.2. | + +| Range bound | Explanation | +|-------------------------------|----------------------------------------------------------------------------------------------------| +| maxnoofNRSCSs | Maximum no. of SCS-specific carriers per TDD, per DL, per UL or per SUL of an NR cell. Value is 5. | +| maxnoofPhysicalResourceBlocks | Maximum no. of Physical Resource Blocks. Value is 275. | + +### 9.3.1.138 SSB Positions In Burst + +Indicates the time domain positions of the transmitted SS-blocks in a half frame with SS/PBCH blocks as defined in TS 38.213 [31], clause 4.1. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE ssb-PositionsInBurst | M | | | 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. | +| >ShortBitmap | | | | | +| >>ShortBitmap | M | | BIT STRING (SIZE(4)) | | +| >MediumBitmap | | | | | +| >>MediumBitmap | M | | BIT STRING (SIZE(8)) | | +| >LongBitmap | | | | | +| >>LongBitmap | M | | BIT STRING (SIZE(64)) | | + +### 9.3.1.139 NR PRACH Configuration + +This IE indicates the PRACH resources by a NR cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|---------------------------------------|-----------------------| +| UL PRACH Configuration | M | | NR PRACH Configuration List 9.3.1.140 | | +| SUL PRACH Configuration | O | | NR PRACH Configuration List 9.3.1.140 | | + +### 9.3.1.140 NR PRACH Configuration List + +This IE indicates the PRACH resources used or reserved in the UL carrier(s) or SUL carrier(s) of the current NR cell. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------|----------|-----------------------|-----------------------|------------------------------------------|-------------|----------------------| +| NR PRACH Configuration Item | | 0..guration > | | Configuration Items for this UL or SUL. | | | +| >NR SCS | M | | ENUMERATED (scs15, scs30, scs60, scs120, ..., scs 480, scs960) | The SCS of the carrier to which this PRACH Configuration Item relates, i.e. in Section 5.3.2 in TS 38.211 [33]. The values scs15, scs30, scs60, scs120, scs 480, and scs960 corresponds to the sub carrier spacing in TS 38.104 [17]. NOTE: Its value may not be identical to the SCS of PRACH. | - | | +| >PRACH Frequency Start from Carrier | M | | INTEGER (0..maxNrofPhysicalResourceBlocks-1, ...) | Lowest number of resource blocks which can be used to deliver MSG1 or the preamble part of MSGA, counting from the start number of the corresponding carrier. Identical to in Section 5.1.2.2.2 in TS 38.214 [34] plus msg1-FrequencyStart or msgA-RO-FrequencyStart-r16 in TS 38.331 [8]. | - | | +| >PRACH-FDM | M | | ENUMERATED (one, two, four, eight, ...) | in Section 6.3.3.2 in TS 38.211 [33]. | - | | +| >PRACH Configuration Index | M | | INTEGER (0..255, ..., 256..262) | See Section 6.3.3.2 in TS 38.211 [33]. | - | | +| >SSB per RACH Occasion | M | | ENUMERATED (oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen, ...) | Number of SSBs per RACH occasion. Value oneEight corresponds to one SSB associated with 8 RACH occasions, value oneFourth corresponds to | - | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------|----------|-------|----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | one SSB associated with 4 RACH occasions, and so on. | | | +| >CHOICE
FreqDomainLength | M | | | For the case of PRACH resources reserved for BFR or MSG1-based SI Request, L139 is always used. | - | | +| >> L839 | | | | | | | +| >>> L839 Info | | 1 | | | - | | +| >>>>Root Sequence Index | M | | INTEGER (0..837) | See Section 6.3.3.1 in TS 38.211 [33]. | - | | +| >>>>Restricted Set Config | M | | ENUMERATED (unrestrictedSet , restrictedSetTypeA, restrictedSetTypeB, ...) | See Section 6.3.3.1 in TS 38.211 [33]. | - | | +| >> L139 | | | | | | | +| >>> L139 Info | | 1 | | | - | | +| >>>>PRACH SCS | M | | ENUMERATED (scs15, scs30, scs60, scs120, ..., scs480, scs960) | Subcarrier Spacing of PRACH, i.e. in Section 5.3.2 in TS 38.211 [33]. | - | | +| >>>>Root Sequence Index | O | | INTEGER (0..137) | See Section 6.3.3.1 in TS 38.211 [33]. | - | | +| >> L571 | | | | | YES | reject | +| >>> L571 Info | | 1 | | | - | | +| >>>>PRACH SCS for L571 | M | | ENUMERATED (scs30, scs120, ... , scs480) | Subcarrier Spacing of PRACH, i.e. in Section 5.3.2 in TS 38.211 [33]. | - | | +| >>>>Root Sequence Index | M | | INTEGER (0..569) | See Section 6.3.3.1 in TS 38.211 [33]. | - | | +| >> L1151 | | | | | YES | reject | +| >>> L1151 Info | | 1 | | | - | | +| >>>>PRACH SCS for L1151 | M | | ENUMERATED (scs15, scs120, ...) | Subcarrier Spacing of PRACH, i.e. in Section 5.3.2 in TS 38.211 [33]. | - | | +| >>>>Root Sequence Index | M | | INTEGER (0..1149) | See Section 6.3.3.1 in TS 38.211 [33]. | - | | +| >Zero Correlation Zone Config | M | | INTEGER (0..15) | See Section 6.3.3.1 in TS 38.211 [33]. | - | | + +| Range bound | Explanation | +|---------------------------------|----------------------------------------------------------------| +| maxnoofPhysicalResourceBlocks-1 | Maximum no. of Physical Resource Blocks minus 1. Value is 274. | +| maxnoofPrachConfiguration | Maximum no. of PRACH Configuration. Value is 16. | + +### 9.3.1.141 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.142 | | +| TSC Assistance Information Uplink | O | | TSC Assistance Information 9.3.1.142 | | + +### 9.3.1.142 TSC Assistance Information + +This IE provides the TSC assistance information for a TSC QoS flow in the uplink or downlink (see TS 23.501 [21]). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|------------------------|------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Periodicity | M | | 9.3.1.143 | Periodicity as specified in TS 23.501 [21]. | - | | +| Burst Arrival Time | O | | 9.3.1.144 | Burst Arrival Time as specified in TS 23.501 [21]. | - | | +| Survival Time | O | | 9.3.1.231 | | YES | ignore | +| CHOICE RAN Feedback Type | O | | | | YES | ignore | +| >proactive | | | | | | | +| >>Burst Arrival Time Window | M | | 9.3.1.300 | | - | | +| >>Periodicity Range | O | | 9.3.1.301 | | - | | +| >reactive | | | | | | | +| >>Capability for BAT Adaptation | M | | ENUMERATED (true, ...) | | - | | +| N6 Jitter Information | O | | 9.3.1.320 | Indicates the jitter information associated with the Periodicity in downlink, as defined in TS 23.501[21]. | YES | ignore | + +### 9.3.1.143 Periodicity + +This IE indicates the Periodicity as defined in TS 23.501 [21]. + +| IE/Group Name | Presence | Range | IE type and | Semantics description | +|---------------|----------|-------|-------------|-----------------------| +|---------------|----------|-------|-------------|-----------------------| + +| | | | reference | | +|-------------|---|--|-----------------------------|-----------------------------------------| +| Periodicity | M | | INTEGER
(0..640000, ...) | Periodicity expressed in units of 1 us. | + +### 9.3.1.144 Burst Arrival Time + +This IE indicates the Burst Arrival Time as defined in TS 23.501 [21]. + +| 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 [8]. The value is provided with 1 us accuracy. | + +### 9.3.1.145 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.146 RLC Duplication Information + +The IE contains the RLC duplication information in case that the indicated DRB is configured with more than two RLC entities as specified in TS 38.331 [8]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------|----------|--------------------------------------|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| RLC Duplication State List | | 1 | | | +| > RLC Duplication State Items | | 1 ..
| | Each position in the list represents a secondary RLC entity in ascending order by the logical channel ID in the order of MCG and SCG. | +| >>Duplication State | M | | ENUMERATED
(Active, Inactive, ...) | | +| Primary Path Indication | O | | ENUMERATED
(True, False,...) | Indicates whether the primary path is located at the gNB-DU for DC based PDCP duplication. | + +| Range bound | Explanation | +|----------------------------|---------------------------------------------------| +| maxnoofRLCDuplicationState | Maximum no of Secondary RLC entities. Value is 3. | + +### 9.3.1.147 Reporting Request Type + +This IE indicates the type of accurate reference time information reporting to be handled by the gNB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------|-------------------------------------|-------|---------------------------------------------|-----------------------------------------------------------------------------------------------| +| Event Type | M | | ENUMERATED (on demand, periodic, stop, ...) | | +| Report Periodicity Value | C-
ifEventTyp
eisPeriodi
c | | INTEGER (0..512, ...) | Indicates the periodicity of accurate reference time information report, Unit in radio frame. | + +| Condition | Explanation | +|-----------------------|----------------------------------------------------------------------------| +| ifEventTypeisPeriodic | This IE shall be present if the Event Type IE is set to "periodic". | + +### 9.3.1.148 Time Reference Information + +This IE contains the time reference information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| Reference Time | M | | 9.3.1.149 | | +| Reference SFN | M | | INTEGER (0..1023) | | +| Uncertainty | O | | INTEGER (0..32767, ...) | This field indicates the uncertainty of the reference time information provided in ReferenceTimeInfo IE, refer to 6.3.2 of TS 38.331 [8]. | +| Time Information Type | O | | ENUMERATED (localClock) | | + +### 9.3.1.149 Reference Time + +This IE provides the accurate Reference Time information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|-----------------------|----------------------------------------------------------------------------| +| Reference Time | M | | OCTET STRING | Includes the ReferenceTime IE as defined in 6.3.2 of TS 38.331 [8]. | + +### 9.3.1.150 MDT Configuration + +The IE defines the MDT configuration parameters. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------|----------|-------|----------------------------------------------------------------|----------------------------------------------------------------------------------------| +| MDT Activation | M | | ENUMERATED (Im mediate MDT only, Immediate MDT and Trace, ...) | | +| Measurements to Activate | M | | BITSTRING (SIZE(8)) | Each position in the bitmap indicates a MDT measurement, as defined in TS 37.320 [35]. | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | Second Bit = M2,
Fifth Bit = M5,
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 3, bit 4 and bit 6. | +| M2 Configuration | C-ifM2 | | ENUMERATED
(true, ...) | | +| M5 Configuration | C-ifM5 | | 9.3.1.152 | | +| M6 Configuration | C-ifM6 | | 9.3.1.153 | | +| M7 Configuration | C-ifM7 | | 9.3.1.154 | | + +| Condition | Explanation | +|-----------|----------------------------------------------------------------------------------------------------| +| ifM2 | This IE shall be present if the Measurements to Activate IE has the second bit set to "1". | +| ifM5 | This IE shall be present if the Measurements to Activate IE has the fifth bit set to "1". | +| ifM6 | This IE shall be present if the Measurements to Activate IE has the 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.151 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 | | PLMN ID
9.3.1.14 | | + +| Range bound | Explanation | +|-----------------|---------------------------------------------------------| +| maxnoofMDTPLMNs | Maximum no. of PLMNs in the MDT PLMN list. Value is 16. | + +### 9.3.1.152 M5 Configuration + +This IE defines the parameters for M5 measurement collection. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|----------|-------|-----------------------------------|-----------------------|-------------|----------------------| +| M5 Collection Period | M | | ENUMERATED
(ms1024,
ms2048, | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------|----------|-------|----------------------------------------------------------------------------|-----------------------|-------------|----------------------| +| | | | ms5120,
ms10240, min1,
...) | | | | +| M5 Links to log | M | | ENUMERATED
(uplink,
downlink, both-
uplink-and-
downlink, ...) | | - | | +| M5 Report Amount | O | | ENUMERATED
(1, 2, 4, 8, 16,
32, 64,
infinity...) | Number of
reports. | YES | ignore | + +### 9.3.1.153 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, ms640,
ms1024,
ms2048,
ms5120,
ms10240,
ms20480,
ms40960,
min1,min6,
min12,
min30,...,
ms480) | | - | | +| 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.154 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, ...) | Unit: minutes | - | | +| M7 Links to log | M | | ENUMERATED
(downlink, ...) | | - | | +| M7 Report Amount | O | | ENUMERATED
(1, 2, 4, 8, 16,
32, 64,
infinity...) | Number of
reports. | YES | ignore | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| | | | 32, 64, infinity...) | | | | + +### 9.3.1.155 NID + +This IE is used to identify (together with a PLMN identifier) a Stand-alone Non-Public Network. 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.156 NPN Support Information + +This IE contains NPN related information associated with Network Slicing information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE NPN Support Information | M | | | | +| > SNPN Information | | | | | +| >>NID | M | | 9.3.1.155 | | + +### 9.3.1.157 NPN Broadcast Information + +This IE contains NPN related broadcast information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE NPN Broadcast Information per PLMN | M | | | | +| > SNPN Information | | | | | +| >>Broadcast SNPN ID List | M | | 9.3.1.158 | | +| > PNI-NPN Information | | | | | +| >>Broadcast PNI-NPN ID List | M | | 9.3.1.162 | | + +### 9.3.1.158 Broadcast SNPN ID List + +This IE contains SNPN related broadcast information associated with a set of PLMNs. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------|----------|------------------|-----------------------|-----------------------| +| Broadcast SNPN ID List | | 1.. | | | +| >PLMN Identity | M | | 9.3.1.14 | | +| >Broadcast NID List | M | | 9.3.1.159 | | + +| Range bound | Explanation | +|-------------|-------------------------------------------------------| +| maxnoofNIDs | Maximum no. of NIDs broadcast in a cell. Value is 12. | + +### 9.3.1.159 Broadcast NID List + +This IE contains a list of NIDs. + +| IE/Group Name | Presence | RangeNIDsupported | IE type and reference | Semantics description | +|----------------------|----------|--------------------------|-----------------------|-----------------------| +| Broadcast NID | | 1.. | | | +| >NID | M | | 9.3.1.155 | | + +| Range bound | Explanation | +|---------------------|-------------------------------------------------------| +| maxnoofNIDsupported | Maximum no. of NIDs broadcast in a cell. Value is 12. | + +### 9.3.1.160 Broadcast CAG-Identifier List + +This IE contains a list of CAG-Identifiers. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------|----------|--------------------------|-----------------------|-----------------------| +| Broadcast CAG-Identifier List | | 1.. | | | +| >CAG ID | M | | 9.3.1.161 | | + +| Range bound | Explanation | +|---------------------|------------------------------------------------------------------| +| maxnoofCAGsupported | Maximum no. of CAG-Identifiers broadcast in a cell. Value is 12. | + +### 9.3.1.161 CAG ID + +This IE is used to identify (together with a PLMN identifier) a Public Network Integrated NPN, as defined in TS 23.003 [23]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------|------------------------------------| +| CAG ID | M | | BIT STRING (SIZE (32)) | Closed Access Group ID used in NR. | + +### 9.3.1.162 Broadcast PNI-NPN ID Information + +This IE contains a list of PNI-NPN IDs. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------|----------|--------------------|-----------------------|-----------------------| +| Broadcast PNI-NPN ID Information | | 1.. | | Broadcast PLMNs | +| >PLMN Identity | M | | 9.3.1.14 | | +| >Broadcast CAG-Identifier List | M | | 9.3.1.160 | | + +| Range bound | Explanation | +|---------------|--------------------------------------------------------| +| maxnoofBPLMNs | Maximum no. of broadcast PLMNs by a cell. Value is 12. | + +### 9.3.1.163 Available SNPN ID List + +This IE indicates the list of available SNPN ID. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------|----------|------------------|---------------------------------|-----------------------| +| Available SNPN ID List | | 1.. | | | +| >PLMN Identity | M | | 9.3.1.14 | | +| >Available NID List | M | | Broadcast NID List
9.3.1.159 | | + +| Range bound | Explanation | +|-------------|-------------------------------------------------------| +| maxnoofNIDs | Maximum no. of NIDs broadcast in a cell. Value is 12. | + +### 9.3.1.164 Void + +### 9.3.1.165 Extended Slice Support List + +This IE indicates a list of supported slices. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------|----------|---------------------------|-----------------------|-----------------------| +| Slice Support Item IEs | | 1.. | | | +| >S-NSSAI | M | | 9.3.1.38 | | + +| Range bound | Explanation | +|----------------------|---------------------------------------------------------------| +| maxnoofExtSliceItems | Maximum no. of signalled slice support items. Value is 65535. | + +### 9.3.1.166 Positioning Measurement Result + +The purpose of this information element is to provide the measurement result(s). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------|----------|-----------------------|-----------------------|-----------------------|-------------|----------------------| +| Positioning Measured Result Item | | 1 .. | | | - | | +| >CHOICE Measured Results Value | M | | | | - | | +| >>UL Angle of Arrival | | | | | | | +| >>>UL Angle of Arrival | M | | 9.3.1.167 | | - | | +| >>UL SRS-RSRP | | | | | | | +| >>>UL SRS-RSRP | M | | INTEGER | | - | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------|----------|-------|--------------------------------------|-----------------------|-------------|----------------------| +| | | | (0..126) | | | | +| >>UL RTOA | | | | | | | +| >>>UL RTOA | M | | UL RTOA Measurement
9.3.1.168 | | - | | +| >>gNB Rx-Tx Time Difference | | | | | | | +| >>>gNB Rx-Tx Time Difference | M | | 9.3.1.170 | | - | | +| >>Zenith Angle of Arrival Information | | | | | YES | reject | +| >>>Zenith Angle of Arrival Information | M | | 9.3.1.239 | | - | | +| >>Multiple UL AoA | | | | | YES | reject | +| >>>Multiple UL AoA | M | | 9.3.1.245 | | - | | +| >>UL SRS-RSRPP | | | | | YES | reject | +| >>>UL SRS-RSRPP | M | | 9.3.1.246 | | - | | +| >Time Stamp | M | | 9.3.1.171 | | - | | +| >Measurement Quality | O | | TRP Measurement Quality
9.3.1.172 | | - | | +| >Measurement Beam Information | O | | 9.3.1.173 | | - | | +| >ARP ID | O | | 9.3.1.244 | | YES | ignore | +| >SRS Resource type | O | | 9.3.1.247 | | YES | ignore | +| >LoS/NLoS Information | O | | 9.3.1.249 | | YES | ignore | +| >Mobile TRP Location Information | O | | 9.3.1.304 | | YES | ignore | + +| Range bound | Explanation | +|----------------|----------------------------------------------------------------------------------------------------------| +| maxnoofPosMeas | Maximum no. of measured quantities that can be configured and reported with one message. Value is 16384. | + +### 9.3.1.167 UL Angle of Arrival + +This information element contains the uplink Angle of Arrival measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|-----------------------|--------------------------------------------------------| +| Azimuth Angle of Arrival | M | | INTEGER(0..3599) | TS 38.133 [38] | +| Zenith Angle of Arrival | O | | INTEGER(0..1799) | TS 38.133 [38] | +| LCS to GCS Translation AoA | O | | 9.3.1.241 | If absent, the azimuth and zenith are provided in GCS. | + +### 9.3.1.168 UL RTOA Measurement + +This information element contains the uplink RTOA measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE UL RTOA Measurement | M | | | | - | | +| >k0 | | | | | | | +| >>k0 | M | | INTEGER (0..1970049) | TS 38.133 [38] | - | | +| >k1 | | | | | | | +| >>k1 | M | | INTEGER (0..985025) | TS 38.133 [38] | - | | +| >k2 | | | | | | | +| >>k2 | M | | INTEGER (0..492513) | TS 38.133 [38] | - | | +| >k3 | | | | | | | +| >>k3 | M | | INTEGER (0..246257) | TS 38.133 [38] | - | | +| >k4 | | | | | | | +| >>k4 | M | | INTEGER (0..123129) | TS 38.133 [38] | - | | +| >k5 | | | | | | | +| >>k5 | M | | INTEGER (0..61565) | TS 38.133 [38] | - | | +| Additional Path List | O | | 9.3.1.169 | This IE is ignored if the Extended Additional Path List IE is included | - | | +| Extended Additional Path List | O | | 9.3.1.248 | | YES | ignore | +| TRP Rx TEG Information | O | | 9.3.1.280 | | YES | ignore | + +### 9.3.1.169 Additional Path List + +This information element contains the additional path results of time measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------|----------|-------------------|-----------------------|-----------------------|-------------|----------------------| +| Additional Path Item | | 1.. | | | - | | +| >CHOICE Relative Path Delay | M | | | | - | | +| >>k0 | | | | | | | +| >>>k0 | M | | INTEGER(0..16351) | | - | | +| >>k1 | | | | | | | +| >>>k1 | M | | INTEGER(0..8176) | | - | | +| >>k2 | | | | | | | +| >>>k2 | M | | INTEGER(0..4088) | | - | | +| >>k3 | | | | | | | +| >>>k3 | M | | INTEGER(0..2044) | | - | | +| >>k4 | | | | | | | +| >>>k4 | M | | INTEGER(0..1022) | | - | | +| >>k5 | | | | | | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------|----------|-------|-----------------------------------|-----------------------|-------------|----------------------| +| >>>k5 | M | | INTEGER(0..511) | | - | | +| >Path Quality | O | | TRP Measurement Quality 9.3.1.172 | | - | | +| >Multiple UL AoA | O | | 9.3.1.245 | | YES | ignore | +| >Path Power | O | | UL SRS-RSRPP 9.3.1.246 | | YES | ignore | + +| Range bound | Explanation | +|-------------|----------------------------------------------------------| +| maxnoofPath | Maximum no. of additional path measurements. Value is 2. | + +### 9.3.1.170 gNB Rx-Tx Time Difference + +This information element contains the gNB Rx-Tx Time Difference measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| CHOICE gNB Rx-Tx Time Difference Measurement | M | | | | - | | +| >k0 | | | | | | | +| >>k0 | M | | INTEGER (0..1970049) | TS 38.133 [38] | - | | +| >k1 | | | | | | | +| >>k1 | M | | INTEGER (0..985025) | TS 38.133 [38] | - | | +| >k2 | | | | | | | +| >>k2 | M | | INTEGER (0..492513) | TS 38.133 [38] | - | | +| >k3 | | | | | | | +| >>k3 | M | | INTEGER (0..246257) | TS 38.133 [38] | - | | +| >k4 | | | | | | | +| >>k4 | M | | INTEGER (0..123129) | TS 38.133 [38] | - | | +| >k5 | | | | | | | +| >>k5 | M | | INTEGER (0..61565) | TS 38.133 [38] | - | | +| Additional Path List | O | | 9.3.1.169 | | - | | +| Extended Additional Path List | O | | 9.3.1.248 | | YES | ignore | +| TRP TEG Information | O | | 9.3.1.253 | | YES | ignore | + +### 9.3.1.171 Time Stamp + +This information element contains the time stamp associated with the measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| + +| | | | | | | | +|--------------------------|---|--|------------------------------------|--|-----|--------| +| System Frame Number | M | | INTEGER(0..1023) | | - | | +| CHOICE Slot Index | M | | | | - | | +| >SCS-15 | | | | | | | +| >>SCS-15 | M | | INTEGER(0..9) | | - | | +| >SCS-30 | | | | | | | +| >>SCS-30 | M | | INTEGER(0..19) | | - | | +| >SCS-60 | | | | | | | +| >>SCS-60 | M | | INTEGER(0..39) | | - | | +| >SCS-120 | | | | | | | +| >>SCS-120 | M | | INTEGER(0..79) | | - | | +| >SCS-480 | | | | | | | +| >>SCS-480 | M | | INTEGER(0..319) | | YES | reject | +| >SCS-960 | | | | | - | | +| >>SCS-960 | M | | INTEGER(0..639) | | YES | reject | +| Measurement Time | O | | Relative Time
1900
9.3.1.183 | | - | | + +### 9.3.1.172 TRP Measurement Quality + +This information element contains the TRP's best estimate of the quality of the measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------|----------|-------|--------------------------------------|-----------------------| +| CHOICE TRP Measurement Quality | M | | | | +| > Timing Measurement Quality | | | | | +| >>Measurement Quality | M | | INTEGER(0..31) | TS 37.355 [39] | +| >>Resolution | M | | ENUMERATED(0.1 m, 1m, 10m, 30m, ...) | TS 37.355 [39] | +| > Angle Measurement Quality | | | | | +| >>Azimuth Quality | M | | INTEGER(0..255) | | +| >>Zenith Quality | O | | INTEGER(0..255) | | +| >>Resolution | M | | ENUMERATED(0.1deg, ...) | | + +### 9.3.1.173 Measurement Beam Information + +This information element contains the receiving beam information when measuring UL signals. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------|-----------------------| +| PRS Resource ID | O | | INTEGER(0..63) | | +| PRS Resource Set ID | O | | INTEGER(0..7) | | +| SSB Index | O | | INTEGER(0..63) | | + +### 9.3.1.174 NG-RAN Access Point Position + +This IE is used to identify the geographical position of an NG-RAN Access Point / TRP / TRP Antenna Reference Points. It is expressed as ellipsoid point with altitude and uncertainty ellipsoid according to TS 23.032 [36]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|-------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Latitude Sign | M | | ENUMERATED (North, South) | | +| Degrees Of Latitude | M | | INTEGER (0..2 23 -1) | The IE value (N) is derived by this formula:
$N \leq 2^{23} \times X / 90 < N+1$
X being the latitude in degrees (0°.. 90°). | +| Degrees Of Longitude | M | | INTEGER (-2 23 ..2 23 -1) | The IE value (N) is derived by this formula:
$N \leq 2^{24} \times X / 360 < N+1$
X being the longitude in degrees (-180°..+180°). | +| Direction of Altitude | M | | ENUMERATED (Height, Depth) | | +| Altitude | M | | INTEGER (0..2 15 -1) | The relation between the value (N) and the altitude (a) in meters it describes is $N \leq a < N+1$ , except for $N=2^{15}-1$ for which the range is extended to include all greater values of (a). | +| Uncertainty semi-major | M | | INTEGER (0..127) | The uncertainty "r" is derived from the "uncertainty code" k by $r = 10x(1.1^k-1)$ . | +| Uncertainty semi-minor | M | | INTEGER (0..127) | The uncertainty "r" is derived from the "uncertainty code" k by $r = 10x(1.1^k-1)$ . | +| Orientation of major axis | M | | INTEGER (0..179) | | +| Uncertainty Altitude | M | | INTEGER (0..127) | The uncertainty altitude "h" expressed in metres is derived from the "uncertainty code" k, by: $h=45x(1.025^k-1)$ . | +| Confidence | M | | INTEGER (0..100) | In percentage | + +### 9.3.1.175 Requested SRS Transmission Characteristics + +This IE contains the requested SRS configuration for the UE for positioning purposes. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|----------------------------------|---------------------------------------|-------|-----------------------------|--------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Number Of Periodic Transmissions | C-
iffResource
TypePerio
dic | | INTEGER (0..500,...) | The number of periodic SRS transmissions requested. The value of '0' represents an infinite number of SRS transmissions. | - | | +| Resource Type | M | | ENUMERATED (periodic, semi- | | - | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------------|----------|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | persistent, aperiodic, ...) | | | | +| CHOICE Bandwidth SRS | M | | | | - | | +| >FR1 | | | | | | | +| >>FR1 Bandwidth | M | | ENUMERATED (5, 10, 20, 40, 50, 80, 100, ...) | | - | | +| >FR2 | | | | | | | +| >>FR2 Bandwidth | M | | ENUMERATED (50, 100, 200, 400, ..., 800, 1600, 2000) | | - | | +| SRS Resource Set List | | 0.. 1 | | | - | | +| >SRS Resource Set Item | | 1.. | | | - | | +| >>Number of SRS Resources Per Set | O | | INTEGER (1..16,...) | The number of SRS Resources per resource set for SRS transmission. | - | | +| >>Periodicity List | | 0.. 1 | | | - | | +| >>>Periodicity List Item | | 1.. | | | - | | +| >>>>PeriodicitySRS | M | | ENUMERATED (0.125, 0.25, 0.5, 0.625, 1, 1.25, 2, 2.5, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240, ...) | Milli-seconds | - | | +| >>Spatial Relation Information | O | | 9.3.1.181 | This IE is ignored if the Spatial Relation Information per SRS Resource IE is present. | - | | +| >>Pathloss Reference Information | O | | 9.3.1.201 | | - | | +| >>Spatial Relation Information per SRS Resource | O | | 9.3.1.210 | | YES | ignore | +| SSB Information | O | | 9.3.1.202 | | - | | +| SRS Frequency | O | | INTEGER(0..3279165) | NR ARFCN
The carrier frequency of SRS transmission bandwidth. | YES | ignore | + +| Condition | Explanation | +|------------------------|-----------------------------------------------------------------------------------------| +| ifResourceTypePeriodic | This IE shall be present if the Resource Type IE is set to the value "Periodic". | + +| Range bound | Explanation | +|-------------------------|------------------------------------------------------------------------------| +| maxnoSRS-ResourceSets | Maximum no of requested SRS Resource Sets for SRS transmission. Value is 16. | +| maxnoSRS-ResourcePerSet | Maximum no of SRS Resources per set. Value is 16. | + +### 9.3.1.176 TRP Information + +The *TRP Information* IE contains information for one TRP within a gNB-DU. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------------|----------|-----------------------------|---------------------------------|-----------------------|-------------|----------------------| +| TRP ID | M | | 9.3.1.197 | | - | | +| TRP Information Type Response List | | 1 | | | - | | +| >TRP Information Type Response Item | | 1 .. | | | - | | +| >>CHOICE TRP Information Type Response Item | M | | | | - | | +| >>>NR PCI | | | | | | | +| >>>>NR PCI | M | | INTEGER (0..1007) | NR Physical Cell ID | - | | +| >>>NR CGI | | | | | | | +| >>>>NR CGI | | | 9.3.1.12 | | - | | +| >>>NR ARFCN | | | | | | | +| >>>>NR ARFCN | M | | INTEGER (0..3279165) | | - | | +| >>>PRS Configuration | | | | | | | +| >>>>PRS Configuration | M | | 9.3.1.177 | | - | | +| >>>SSB Information | | | | | | | +| >>>>SSB Information | M | | 9.3.1.202 | | - | | +| >>>SFN Initialisation Time | | | | | | | +| >>>>SFN Initialisation Time | M | | Relative Time 1900
9.3.1.183 | | - | | +| >>>Spatial Direction Information | | | | | | | +| >>>>Spatial Direction Information | M | | 9.3.1.179 | | - | | +| >>>Geographical Coordinates | | | | | | | +| >>>>Geographical | M | | 9.3.1.184 | | - | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------|-----------------------|-------|--------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-------------|----------------------| +| Coordinates | | | | | | | +| >>>TRP Type | | | | | YES | reject | +| >>>>TRP Type | M | | ENUMERATED
(prs-only-tp,
srs-only-rp, tp,
rp, trp,...,
mobile-trp) | TS 38.305 [42] | - | | +| >>>On-demand
PRS TRP
Information | | | | | YES | reject | +| >>>>On-demand
PRS TRP
Information | M | | 9.3.1.240 | | - | | +| >>>TRP Tx TEG
Association | | | | | YES | reject | +| >>>>TRP Tx TEG
Association | M | | 9.3.1.252 | | - | | +| >>>TRP Beam
Antenna | | | | | YES | reject | +| >>>>TRP Beam
Antenna
Information | M | | 9.3.1.256 | | - | | +| >>>Mobile TRP
Location | | | | | | | +| >>>>Mobile TRP
Location
Information | M | | 9.3.1.304 | | YES | reject | +| Mobile IAB-MT UE ID | C-
ifMobileTR
P | | OCTET
STRING | The UE ID of the IAB-MT associated with the mobile TRP, includes GPSI as defined in TS 29.571 [50] | YES | reject | + +| Range bound | Explanation | +|---------------------|-------------------------------------------------------------------------------------------------------| +| maxnoofTRPInfoTypes | Maximum no of TRP information types that can be requested and reported with one message. Value is 64. | + +| Condition | Explanation | +|-------------|------------------------------------------------------------------------------| +| ifMobileTRP | This IE shall be present if the TRP type IE is set to the value 'mobile-trp' | + +### 9.3.1.177 PRS Configuration + +This information element contains the DL PRS configuration for the TRP. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------|----------|-----------------------------------------|-----------------------|-----------------------|-------------|----------------------| +| PRS Resource Set List | M | 1..oofPRSr
esourceS
ets> | | | | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------|----------|----------------------------|---------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >PRS Resource Set ID | M | | INTEGER(0..7) | | | | +| >Subcarrier Spacing | M | | ENUMERATED(kHz15, kHz30, kHz60, kHz120, ...) | | | | +| >PRS bandwidth | M | | INTEGER(1..63) | 24,28,...,272 PRBs | | | +| >Start PRB | M | | INTEGER(0..2176) | Starting PRB to Point A | | | +| >Point A | M | | INTEGER(0..3279165) | NR ARFCN | | | +| >Comb Size | M | | ENUMERATED(2, 4, 6, 12, ...) | | | | +| >CP Type | M | | ENUMERATED(normal, extended, ...) | | | | +| >Resource Set Periodicity | M | | ENUMERATED(4,5,8,10,16,20,32,40,64,80,160,320,640,1280,2560,5120,10240,20480,40960,81920, ..., 128, 256, 512) | Slots | | | +| >Resource Set Slot Offset | M | | INTEGER(0..81919,...) | | | | +| >Resource Repetition Factor | M | | ENUMERATED(rf1,rf2,rf4,rf6,rf8,rf16,rf32,...) | | | | +| >Resource Time Gap | M | | ENUMERATED(tg1,tg2,tg4,tg8,tg16,tg32,...) | | | | +| >Resource Number of Symbols | M | | ENUMERATED(n2,n4,n6,n12,...,n1) | | | | +| >PRS Muting | O | | | | | | +| >>Option1 | O | | | | | | +| >>>Muting Pattern | M | | DL-PRS Muting Pattern 9.3.1.178 | Muting pattern option 1 is used to mute the whole PRS resource set (within a period) | | | +| >>>Muting Bit Repetition Factor | M | | ENUMERATED(rf1,rf2,rf4,rf8,...) | | | | +| >>Option2 | O | | | | | | +| >>>Muting Pattern | M | | DL-PRS Muting Pattern 9.3.1.178 | Muting pattern option 2 is used to mute the selected repetition of the resource set (within the period) | | | +| >PRS Resource Transmit Power | M | | INTEGER(-60..50) | | | | +| >PRS Resource List | M | 1.. | | 37.355 [39] | | | +| >>PRS Resource ID | M | | INTEGER(0..63) | | | | +| >>Sequence ID | M | | INTEGER(0..4095) | | | | +| >>RE Offset | M | | INTEGER(0..11, ...) | | | | +| >>Resource Slot Offset | M | | INTEGER(0..511) | | | | +| >>Resource Symbol Offset | M | | INTEGER(0..12) | This IE is ignored if the Extended Resource Symbol Offset IE is present. | | | +| >>CHOICE QCL Info | O | | | | | | +| >>>SSB | | | | | | | +| >>>>PCI | M | | INTEGER(0..1007) | | | | +| >>>>SSB Index | O | | INTEGER(0..63) | | | | +| >>>DL-PRS | O | | | | | | +| >>>>QCL Source PRS Resource Set ID | M | | INTEGER(0..7) | | | | +| >>>>QCL Source PRS Resource ID | O | | INTEGER(0..63) | If absent, the QCL source PRS resource ID is the same as the PRS resource ID | | | +| >>Extended Resource Symbol Offset | O | | INTEGER(0..13, ...) | | Yes | ignore | + +| Range bound | Explanation | +|-------------------------|----------------------------------------------------------------| +| maxnoofPRSresourcesSets | Maximum no of PRS resource sets. Value is 8. | +| maxnoofPRSresources | Maximum no of PRS resources per PRS resource set. Value is 64. | + +### 9.3.1.178 DL-PRS Muting Pattern + +This information element contains the DL-PRS muting pattern. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE DL-PRS Muting Pattern | M | | | | +| >Two | | | | | +| >>Two | M | | BIT STRING (SIZE(2)) | | +| >Four | | | | | +| >>Four | M | | BIT STRING (SIZE(4)) | | +| >Six | | | | | +| >>Six | M | | BIT STRING (SIZE(6)) | | +| >Eight | | | | | +| >>Eight | M | | BIT STRING (SIZE(8)) | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| >Sixteen | | | | | +| >>Sixteen | M | | BIT STRING (SIZE(16)) | | +| >Thirty-two | | | | | +| >>Thirty-two | M | | BIT STRING (SIZE(32)) | | + +### 9.3.1.179 Spatial Direction Information + +This information element contains the spatial direction information of the DL PRS resources for the TRP. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-----------------------|----------------------------------------------------| +| NR-PRS Beam Information | M | | 9.3.1.198 | The spatial directions of DL-PRS Resources for TRP | + +### 9.3.1.180 SRS Resource Set ID + +This information element indicates a resource set in the UE for UL SRS transmission. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|-----------------------|----------------------------| +| SRS Resource Set ID | M | | INTEGER (0..15) | According to TS 38.331 [8] | + +### 9.3.1.181 Spatial Relation Information + +This information element indicates a spatial relation for transmission of UL SRS by a UE. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------|----------|----------------------------|-----------------------|---------------------------------------------------| +| Spatial Relation for Resource ID | | 1 | | According to TS 38.321 [16] and and TS 38.331 [8] | +| > Spatial Relation for Resource ID Item | | 1.. | | | +| >>CHOICE Reference Signal | M | | | | +| >>>NZP CSI-RS | | | | | +| >>>>NZP CSI-RS Resource ID | M | | INTEGER (0..191) | | +| >>>SSB | | | | | +| >>>>PCI | M | | INTEGER (0..1007) | | +| >>>>SSB Index | O | | INTEGER (0..63) | | +| >>>SRS | | | | | +| >>>>SRS Resource ID | M | | INTEGER (0..63) | | +| >>>Positioning SRS | | | | | +| >>>>Positioning SRS Resource ID | M | | INTEGER (0..63) | | +| >>>DL-PRS | | | | | +| >>>>DL-PRS ID | M | | INTEGER (0..255) | | +| >>>>DL-PRS Resource Set ID | M | | INTEGER (0..7) | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-----------------------|-----------------------| +| >>>>DL PRS Resource ID | O | | INTEGER (0..63) | | + +| Range bound | Explanation | +|-----------------------|-----------------------------------------------------------------------| +| maxnoSpatialRelations | Maximum no. of Spatial Relations that can be configured. Value is 64. | + +### 9.3.1.182 SRS Resource Trigger + +This information element indicates a DCI code point according to a SRS resource set configuration. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------|----------|------------------------------|-----------------------|----------------------------| +| Aperiodic SRS Resource Trigger List | | 1.. | | According to TS 38.331 [8] | +| >Aperiodic SRS Resource Trigger | | | INTEGER (1..3) | | + +| Range bound | Explanation | +|------------------------|------------------------------------------------| +| maxnoSRS-TriggerStates | Maximum no. of SRS trigger states. Value is 3. | + +### 9.3.1.183 Relative Time 1900 + +This information element indicates the initialisation time (e.g. SFN Initialisation Time for a cell, requested time for an action, etc). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Relative Time 1900 | M | | BIT STRING (SIZE(64)) | Time in seconds relative to 00:00:00 on 1 January 1900 (calculated as continuous time without leap seconds and traceable to a common time reference) where binary encoding of the integer part is in the first 32 bits and binary encoding of the fraction part in the last 32 bits. The fraction part is expressed with a granularity of $1/2^{32}$ second | + +### 9.3.1.184 Geographical Coordinates + +This information element contains the geographical coordinates for the TRP and any associated ARP(s). + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| CHOICE TRP Position Definition Type | M | | | | - | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-------|------------------------------------------------------|----------------------------------------------------------------------------------------------|-------------|----------------------| +| >Direct | | | | | | | +| >>CHOICE Accuracy | M | | | | - | | +| >>>normal accuracy | | | | | | | +| >>>>TRP Position | M | | NG-RAN Access Point Position 9.3.1.174 | The configured estimated geographical position of the antenna of the cell/TRP. | - | | +| >>>high accuracy | | | | | | | +| >>>>TRP High Accuracy Access Position | M | | NG-RAN High Accuracy Access Point Position 9.3.1.190 | The configured estimated geographical high accuracy position of the antenna of the cell/TRP. | - | | +| >Referenced | | | | | | | +| >>Reference Point | M | | 9.3.1.188 | The reference point is used to derive the TRP position | - | | +| >>CHOICE Type | M | | | | - | | +| >>>Geodetic | | | | | | | +| >>>>TRP Position Relative Geodetic | M | | Relative Geodetic Location 9.3.1.186 | The configured estimated relative geodetic coordinate of the antenna of the cell/TRP | - | | +| >>>Cartesian | | | | | | | +| >>>>TRP Position Relative Cartesian | M | | Relative Cartesian Location 9.3.1.187 | The configured estimated relative Cartesian coordinate of the antenna of the cell/TRP | - | | +| DL-PRS Resource Coordinates | O | | 9.3.1.185 | DL-PRS Resource Coordinates relative to the TRP coordinate | - | | +| ARP Location Information | O | | 9.3.1.243 | | YES | ignore | + +### 9.3.1.185 DL-PRS Resource Coordinates + +This information element contains the geographical coordinates of the antenna reference points (ARP) for the DL-PRS Resources of a TRP. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------|----------|---------------------------------|-----------------------|-----------------------| +| DL-PRS Resource Set ARP List | M | 1.. | | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------|----------|---------------------------------|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| >DL-PRS Resource Set ID | M | | INTEGER (0..7) | | +| >CHOICE DL-PRS Resource Set ARP Location | M | | | Relative to the geographical coordinates for the TRP. If this IE is absent, the Relative Location is zero for the indicated DL-PRS Resource Set ID. | +| >>Geodetic | | | | | +| >>>Relative Geodetic Location | M | | Relative Geodetic Location 9.3.1.186 | | +| >>Cartesian | | | | | +| >>>Relative Cartesian Location | M | | Relative Cartesian Location 9.3.1.187 | | +| >DL-PRS Resource ARP List | M | 1.. | | | +| >>DL-PRS Resource ID | M | | INTEGER (0..63) | | +| >>CHOICE DL-PRS Resource ARP Location | M | | | Relative to the DL-PRS Resource Set ARP Location. If this IE is absent, the Relative Location is zero for the indicated DL-PRS Resource ID. | +| >>Geodetic | | | | | +| >>>Relative Geodetic Location | O | | Relative Geodetic Location 9.3.1.186 | | +| >>Cartesian | | | | | +| >>>Relative Cartesian Location | O | | Relative Cartesian Location 9.3.1.187 | | + +| Range bound | Explanation | +|----------------------------|------------------------------------------------------------------------------------| +| maxnoofPRS-ResourceSets | Maximum no of DL-PRS resource sets per TRP. Value is 2. | +| maxnoofPRS-ResourcesPerSet | Maximum no of DL-PRS resources of the DL-PRS resource set of the TRP. Value is 64. | + +### 9.3.1.186 Relative Geodetic Location + +This information element provides a location relative to some known reference location in a relative geodetic coordinate system. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|--------------------------------|-------------------------------------------------------------------------------------------| +| Milli-Arc-Second Units | M | | ENUMERATED (0.03, 0.3, 3, ...) | Units and scale factor for the delta-latitude and delta-longitude fields, TS 37.355 [39]. | +| Height Units | M | | ENUMERATED (mm, cm, m, ...) | Units and scale factor for the delta-height field, TS 37.355 [39]. | +| Delta Latitude | M | | INTEGER (-1024..1023) | Delta value in latitude in the unit provided in Milli-Arc-Second Units, TS 37.355 [39]. | +| Delta Longitude | M | | INTEGER (-1024..1023) | Delta value in longitude in the unit provided in Milli-Arc-Second | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|----------|-------|--------------------------|-----------------------------------------------------------------------------------------| +| | | | | Units, TS 37.355 [39]. | +| Delta Height | M | | INTEGER
(-1024..1023) | Delta value in ellipsoidal height in the unit provided in Height Units, TS 37.355 [39]. | +| Location uncertainty | M | | 9.3.1.189 | | + +### 9.3.1.187 Relative Cartesian Location + +This information element provides a location relative to some known reference location in a relative Cartesian coordinate. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|----------|-------|----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| XYZ unit | M | | ENUMERATED
(mm, cm, dm,...) | | +| X value | M | | INTEGER
(-2 16 ..2 16 -1) | Positive value represents easting from reference point, in units of XYZ Unit IE. | +| Y value | M | | INTEGER
(-2 16 ..2 16 -1) | Positive value represents northing from reference point in units of XYZ Unit IE. | +| Z value | M | | INTEGER
(-2 15 ..2 15 -1) | Height with respect to reference point in units of XYZ Unit IE, where the XY-plane is horizontal and the Z-axis points up. | +| Location uncertainty | M | | 9.3.1.189 | | + +### 9.3.1.188 Reference Point + +This information element provides a reference point location information. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------------|----------|-------|---------------------------------------------------------|----------------------------------------------------------------------| +| CHOICE ReferencePoint | M | | | Reference point to which relative location information is related to | +| > Coordinate ID | | | | | +| >>Coordinate ID | M | | INTEGER(0..2 9 -1,...) | Referential ID mapped via OAM | +| > Reference Point Coordinates | | | | | +| >>Reference Point Position | M | | NG-RAN Access Point Position
9.3.1.174 | | +| > Reference Point Coordinates High Accuracy | | | | | +| >>Reference Point High Accuracy Access Position | M | | NG-RAN High Accuracy Access Point Position
9.3.1.190 | | + +### 9.3.1.189 Location Uncertainty + +This information element provides the location uncertainty information. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| Horizontal Uncertainty | M | | INTEGER (0..255) | Horizontal uncertainty of the ARP latitude/longitude. Corresponds to the encoded high accuracy uncertainty as defined in TS 23.032 [36] | +| Horizontal Confidence | M | | INTEGER (0..100) | Corresponds to confidence as defined in TS 23.032 [36]. | +| Vertical Uncertainty | M | | INTEGER (0..255) | Vertical uncertainty of the ARP altitude. Corresponds to the encoded high accuracy uncertainty as defined in TS 23.032 [36] | +| Vertical Confidence | M | | INTEGER (0..100) | Corresponds to confidence as defined in TS 23.032 [36]. | + +### 9.3.1.190 NG-RAN High Accuracy Access Point Position + +The *NG-RAN High Accuracy Access Point Position* IE is used to identify the geographical position of an NG-RAN Access Point. It is expressed as High Accuracy Ellipsoid point with altitude and uncertainty ellipsoid according to TS 23.032 [36]. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|----------------------------------|-----------------------| +| Degrees of Latitude | M | | INTEGER(-2147483648..2147483647) | | +| Degrees of Longitude | M | | INTEGER(-2147483648..2147483647) | | +| Altitude | M | | INTEGER(-64000..1280000) | | +| Uncertainty Semi Major | M | | INTEGER (0..255) | | +| Uncertainty Semi Minor | M | | INTEGER (0..255) | | +| Orientation Major Axis | M | | INTEGER (0..179) | | +| Horizontal Confidence | M | | INTEGER (0..100) | | +| Uncertainty Altitude | M | | INTEGER (0..255) | | +| Vertical Confidence | M | | INTEGER (0..100) | | + +### 9.3.1.191 Positioning Broadcast Cells + +This IE is used to indicate the cells that are requested to broadcast, or failed to broadcast, the associated posSIB(s). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------|----------|-----------------------|-----------------------|-----------------------| +| Positioning Broadcast Cells | | 1 .. | | | +| >NR CGI | M | | 9.3.1.12 | | + +| Range bound | Explanation | +|-----------------|------------------------------------------------------------------------| +| maxnoBcastCells | Maximum no. of cells broadcasting a posSIB in a NB-DU. Value is 16384. | + +### 9.3.1.192 SRS Configuration + +This information element contains the SRS configuration configured by the gNB-CU for the UE. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------------|----------|--------------------------------|---------------------------------------------------------------|------------------------------------------------------------| +| SRS Carrier List | | 1.. | | | +| >Point A | M | | INTEGER (0..3279165) | NR ARFCN | +| >Uplink Channel BW-PerSCS-List | | 1.. | | SCS-SpecificCarrier TS 38.331 [8] | +| >>Offset To Carrier | M | | INTEGER(0..2199, ...) | First usable RB to Point A in the number of PRBs | +| >>Subcarrier Spacing | M | | ENUMERATED(kHz 15, kHz30, kHz60, kHz120, ..., kHz480, kHz960) | | +| >>Carrier Bandwidth | M | | INTEGER(1..275, ...) | | +| >Active UL BWP | M | | | Only the configuration in the active UL BWP is needed. | +| >>Location And Bandwidth | M | | INTEGER(0..37949, ...) | BWP TS 38.331 [8] | +| >>Subcarrier Spacing | M | | ENUMERATED(kHz 15, kHz30, kHz60, kHz120, ..., kHz480, kHz960) | | +| >>Cyclic Prefix | M | | ENUMERATED(Normal, Extended) | | +| >>Tx Direct Current Location | M | | INTEGER(0..3301, ...) | | +| >>Shift7dot5kHz | O | | ENUMERATED(true, ...) | | +| >>SRS Config | M | | | SRS-Config as defined in TS 38.331 [8] | +| >>>SRS Resource List | | 0.. | | | +| >>>SRS Resource | M | | 9.3.1.193 | SRS-Resource as defined in TS 38.331 [8] | +| >>>Positioning SRS Resource List | | 0.. | | | +| >>>Positioning SRS Resource | M | | 9.3.1.194 | SRS-PosResource-r16 as defined in TS 38.331 [8] | +| >>>SRS Resource Set List | | 0.. | | | +| >>>SRS Resource Set | M | | 9.3.1.195 | SRS-ResourceSet as defined in TS 38.331 [8] | +| >>>Positioning SRS Resource Set List | | 0.. | | | +| >>>Positioning SRS Resource Set | M | | 9.3.1.196 | SRS-PosResourceSet-r16 as defined in TS 38.331 [8] | +| >PCI | O | | INTEGER (0..1007) | Physical Cell ID of the cell that contains the SRS carrier | + +| Range bound | Explanation | +|--------------------------|----------------------------------------------------------------------| +| maxnoSRS-Carriers | Maximum no of carriers for SRS. Value is 32. | +| maxnoSCSs | Maximum no of SCS spacings for a carrier. Value is 5. | +| maxnoSRS-Resources | Maximum no of SRS resources per UL BWP. Value is 64. | +| maxnoSRS-PosResources | Maximum no of positioning SRS resources per UL BWP. Value is 64. | +| maxnoSRS-ResourceSets | Maximum no of SRS resource sets. Value is 16. | +| maxnoSRS-PosResourceSets | Maximum no of positioning SRS resource sets per UL BWP. Value is 16. | + +### 9.3.1.193 SRS Resource + +This information element contains the SRS resource. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|-----------------------------------------|-----------------------------------------------------------------------------|-------------|----------------------| +| SRS Resource ID | M | | INTEGER (0..63, ...) | | - | | +| Number of Ports | M | | ENUMERATED (ports1, ports2, ports4) | | - | | +| CHOICE Transmission Comb | M | | | | - | | +| >Comb Two | | | | | | | +| >>Comb Offset | M | | INTEGER(0..1) | | - | | +| >>Cyclic Shift | M | | INTEGER(0..7) | | - | | +| >Comb Four | | | | | | | +| >>Comb Offset | M | | INTEGER(0..3) | | - | | +| >>Cyclic Shift | M | | INTEGER(0..11 ) | | - | | +| >Comb Eight | M | | | | YES | reject | +| >>Comb Offset | M | | INTEGER(0..7) | | - | - | +| >>Cyclic Shift | M | | INTEGER(0..5) | | - | - | +| Start Position | M | | INTEGER(0..13 ) | | - | | +| Number of Symbols | M | | ENUMERATED (1,2,4) | This IE is ignored if the Number of Symbols Extended IE is included. | - | | +| Repetition Factor | M | | ENUMERATED (1,2,4) | This IE is ignored if the Repetition Factor Extended IE is included. | - | | +| Frequency Domain Position | M | | INTEGER(0..67 ) | | - | | +| Frequency Domain Shift | M | | INTEGER(0..26 8) | | - | | +| C-SRS | M | | INTEGER(0..63 ) | | - | | +| B-SRS | M | | INTEGER(0..3) | | - | | +| B-Hop | M | | INTEGER(0..3) | | - | | +| Group or Sequence Hopping | M | | ENUMERATED (Neither, groupHopping, ...) | | - | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------|----------------------| +| | | | sequenceHopping) | | | | +| CHOICE Resource Type | M | | | | - | | +| > Periodic | | | | | | | +| >>Periodicity | M | | ENUMERATED (slot1, slot2, slot4, slot5, slot8, slot10, slot16, slot20, slot32, slot40, slot64, slot80, slot160, slot320, slot640, slot1280, slot2560, ...) | | - | | +| >>Offset | M | | INTEGER(0..2559, ...) | | - | | +| > Semi-persistent | | | | | | | +| >>Periodicity | M | | ENUMERATED (slot1, slot2, slot4, slot5, slot8, slot10, slot16, slot20, slot32, slot40, slot64, slot80, slot160, slot320, slot640, slot1280, slot2560, ...) | | - | | +| >>Offset | M | | INTEGER(0..2559, ...) | | - | | +| > Aperiodic | | | | | | | +| >>Aperiodic Resource Type | M | | ENUMERATED (true,...) | | - | | +| Sequence ID | M | | INTEGER(0..1023) | | - | | +| Number of Symbols Extended | O | | ENUMERATED (n8,n10,n12, n14, ...) | | YES | ignore | +| Repetition Factor Extended | O | | ENUMERATED (r3, r5, r6, r7, r8, r10, r12, r14, ...) | | YES | ignore | +| Start RB Hopping | O | | ENUMERATED (enable) | | YES | ignore | +| CHOICE Start RB Index | O | | | | YES | ignore | +| > FreqScalingFactor2 | | | INTEGER (0..1) | | - | - | +| > FreqScalingFactor4 | | | INTEGER (0..3) | | - | - | + +### 9.3.1.194 Positioning SRS Resource + +This information element contains the SRS resource for positioning. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------------|----------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Positioning SRS Resource ID | M | | INTEGER (0..63) | | +| CHOICE Transmission Comb Positioning | M | | | | +| >Comb Two | | | | | +| >>Comb Offset | M | | INTEGER(0..1) | | +| >>Cyclic Shift | M | | INTEGER(0..7) | | +| >Comb Four | | | | | +| >>Comb Offset | M | | INTEGER(0..3) | | +| >>Cyclic Shift | M | | INTEGER(0..11) | | +| >Comb Eight | | | | | +| >>Comb Offset | M | | INTEGER(0..7) | | +| >>Cyclic Shift | M | | INTEGER(0..5) | | +| Start Position | M | | INTEGER(0..13) | | +| Number of Symbols | M | | ENUMERATED(1,2, 4,8,12) | | +| Frequency Domain Shift | M | | INTEGER(0..268) | | +| C-SRS | M | | INTEGER(0..63) | | +| Group or Sequence Hopping | M | | ENUMERATED(Neither, groupHopping, sequenceHopping) | | +| CHOICE Resource Type Positioning | M | | | | +| >Periodic | | | | | +| >>Periodicity | M | | ENUMERATED(slot 1, slot2, slot4, slot5, slot8, slot10, slot16, slot20, slot32, slot40, slot64, slot80, slot160, slot320, slot640, slot1280, slot2560, slot5120, slot10240, slot40960, slot81920, ..., slot128, slot256, slot512, slot20480) | | +| >>Offset | M | | INTEGER(0..81919, ...) | | +| >Semi-persistent | | | | | +| >>Periodicity | M | | ENUMERATED(slot 1, slot2, slot4, slot5, slot8, slot10, slot16, slot20, slot32, slot40, slot64, slot80, slot160, slot320, slot640, slot1280, slot2560, slot5120, slot10240, slot20480, slot40960, slot81920, ..., slot128, slot256, slot512, slot20480) | | +| >>Offset | M | | INTEGER(0..81919, ...) | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------|----------|-------|-----------------------|-----------------------| +| > Aperiodic | | | | | +| >>Slot offset | M | | INTEGER(0..32) | | +| Sequence ID | M | | INTEGER(0..65535) | | +| CHOICE Spatial Relation Positioning | O | | | | +| >SSB | | | | | +| >>PCI | M | | INTEGER (0..1007) | | +| >>SSB index | O | | INTEGER(0..63) | | +| >PRS | | | | | +| >>PRS ID | M | | INTEGER(0..255) | | +| >>PRS Resource Set ID | M | | INTEGER(0..7) | | +| >>PRS Resource ID | O | | INTEGER(0..63) | | + +### 9.3.1.195 SRS Resource Set + +This information element indicates a SRS resource set in the UE for UL SRS transmission. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|---------------------------------------|-----------------------|-----------------------| +| SRS Resource Set ID | M | | INTEGER(0..15) | | +| SRS Resource ID List | | 1..< maxnoSRS-ResourcePerSet > | | | +| >SRS Resource ID | M | | INTEGER (0..63, ...) | | +| CHOICE Resource Set Type | M | | | | +| > Periodic | | | | | +| >>PeriodicSet | M | | ENUMERATED(true ....) | | +| > Semi-persistent | | | | | +| >>Semi-persistentSet | M | | ENUMERATED(true ....) | | +| > Aperiodic | | | | | +| >>SRS Resource Trigger List | M | | INTEGER(1..3) | | +| >>Slot offset | M | | INTEGER(0..32) | | + +| Range bound | Explanation | +|-------------------------|----------------------------------------------------------------| +| maxnoSRS-ResourcePerSet | Maximum no of SRS resources per SRS resource set. Value is 16. | + +### 9.3.1.196 Positioning SRS Resource Set + +This information element indicates a positioning SRS resource set in the UE for UL SRS transmission. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|------------------------------------------|-----------------------|-----------------------| +| Positioning SRS Resource Set ID | M | | INTEGER(0..15) | | +| Positioning SRS Resource ID List | | 1..< maxnoSRS-PosResourcePerSet > | | | + +| | | | | | +|------------------------------|---|--|-----------------------|--| +| >Positioning SRS Resource ID | M | | INTEGER (0..63, ...) | | +| CHOICE Resource Type | M | | | | +| > Periodic | | | | | +| >>PosperiodicSet | M | | ENUMERATED(true, ...) | | +| > Semi-persistent | | | | | +| >>Possemi-persistentSet | M | | ENUMERATED(true, ...) | | +| > Aperiodic | | | | | +| >>SRS Resource Trigger List | M | | INTEGER(1..3) | | + +| Range bound | Explanation | +|----------------------------|----------------------------------------------------------------------------------------| +| maxnoSRS-PosResourcePerSet | Maximum no of positioning SRS resources per positioning SRS resource set. Value is 16. | + +### 9.3.1.197 TRP ID + +The *TRP ID* IE is used to identify a TRP uniquely within a gNB-CU. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|------------------------|-----------------------------------| +| TRP Identifier | M | | INTEGER (1..65535,...) | Identifies a TRP within an gNB-CU | + +### 9.3.1.198 NR-PRS Beam Information + +This IE contains spatial direction information of the DL-PRS Resources. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------|----------|--------------------------------------|-----------------------|------------------------------------------------------------------------|-------------|----------------------| +| NR-PRS Beam Information List | | 1 | | | - | | +| > NR-PRS Beam Information Item | | 1 .. < maxnoofPRS-Resource Sets > | | | - | | +| >>PRS Resource Set ID | M | | INTEGER (0..7) | The resource set in which the resources are associated with the angle. | - | | +| >>PRS Angle List | | 1 | | | - | | +| >>>PRS Angle Item | | 1 .. < maxnoofPRS-Resource sPerSet > | | | - | | +| >>>>NR PRS Azimuth | M | | INTEGER (0..359) | | - | | +| >>>>NR PRS Azimuth fine | O | | INTEGER (0..9) | Fine angles | - | | +| >>>>NR PRS | O | | INTEGER | | - | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------|----------|-----------------------------------|-----------------------|-----------------------------------------------------------|-------------|----------------------| +| Elevation | | | (0..180) | | | | +| >>>>NR PRS Elevation fine | O | | INTEGER (0..9) | Fine angles | - | | +| >>>>PRS Resource ID | O | | INTEGER(0..63 ) | | YES | ignore | +| LCS to GCS Translation List | | 0..1 | | If absent, the azimuth and elevation are provided in GCS. | - | | +| > LCS to GCS Translation | | 1 .. | | | - | | +| >>Alpha | M | | INTEGER (0..359) | | - | | +| >>Alpha-fine | O | | INTEGER (0..9) | Fine angles | - | | +| >>Beta | M | | INTEGER (0..359) | | - | | +| >>Beta-fine | O | | INTEGER (0..9) | Fine angles | - | | +| >>Gamma | M | | INTEGER (0..359) | | - | | +| >>Gamma-fine | O | | INTEGER (0..9) | Fine angles | - | | + +| Range bound | Explanation | +|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| maxnoofPRS-ResourceSets | Maximum no of DL-PRS resource sets per TRP. Value is 2. | +| maxnoofPRS-ResourcesPerSet | Maximum no of DL-PRS resources of the DL-PRS resource set of the TRP. Value is 64. | +| maxnooflcs-gcs-translation | Maximum no. of LCS-GS-Translation-Parameters that can reported with one message. Value is 3. The current version of the specification supports 1. | + +### 9.3.1.199 E-CID Measurement Result + +The purpose of this IE is to provide the E-CID measurement result. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-----------------------|-----------------------|----------------------------------------------------------------------------|-------------|----------------------| +| Geographical Coordinates | O | | 9.3.1.184 | The configured estimated geographical position of the antenna of the cell. | - | | +| Measured Results List | | 0..1 | | | | | +| > E-CID Measured Results Item | | 1 .. | | | | | +| >>CHOICE Measured Results Value | M | | | | | | +| >>>Value Angle of Arrival NR | | | | | | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------|----------|-------|-------------------------------------------|-------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>>>Value Angle of Arrival NR | M | | UL Angle of Arrival 9.3.1.167 | | - | | +| >>>Value Timing Advance NR | | | | | | | +| >>>>Value Timing Advance NR | M | | INTEGER (0..7690) | As defined in TS 38.215 [43] | YES | ignore | +| Mobile Access Point Location Information | O | | Mobile TRP Location Information 9.3.1.304 | The location information of the mobile access point of the cell that is associated to the mobile TRP. | YES | ignore | + +| Range bound | Explanation | +|----------------|-------------------------------------------------------------------------------------------------------| +| maxnoMeasE-CID | Maximum no. of measured quantities that can be configured and reported with one message. Value is 64. | + +### 9.3.1.200 Cell Portion ID + +This IE gives the current Cell Portion associated with the target UE. The Cell Portion ID is the unique identifier for a cell portion within a cell. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------|----------|-------|------------------------|-----------------------| +| Cell Portion ID | M | | INTEGER (0..4095, ...) | | + +### 9.3.1.201 Pathloss Reference Information + +This information element indicates a pathloss reference for transmission of UL SRS by a UE. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Pathloss Reference Signal | M | | | | +| >SSB | | | | | +| >>PCI | M | | INTEGER (0..1007) | | +| >>SSB Index | O | | INTEGER (0..63) | | +| >DL-PRS | | | | | +| >>DL-PRS ID | M | | INTEGER (0..255) | | +| >>DL-PRS Resource Set ID | M | | INTEGER (0..7) | | +| >>DL PRS Resource ID | O | | INTEGER (0..63) | | + +### 9.3.1.202 SSB Information + +This information element contains the SSB time/frequency information for the TRPs. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|---------------------|-----------------------------------------------------|-----------------------| +| SSB Information List | | 1 | | | +| > SSB Information Item | | 1...
| | | +| >>SSB Configuration | M | | SSB
Time/Frequency
Configuration
9.3.1.203 | | +| >>PCI | M | | INTEGER (0..1007) | | + +| Range bound | Explanation | +|-------------|-------------------------------------------------------------------------------| +| maxNoSSBs | Maximum no of SSBs for which the configuration can be provided. Value is 255. | + +### 9.3.1.203 SSB Time/Frequency Configuration + +This information element contains the time and frequency configuration of an SSB. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------|----------|-------|-----------------------------------------------------------------------|------------------------------------------------------------------------| +| SSB frequency | M | | INTEGER (0..3279165) | ARFCN | +| SSB subcarrier spacing | M | | ENUMERATED(kHz 15, kHz30, kHz60, kHz120, kHz240,... , kHz480, kHz960) | The value 60kHz is not supported in this version of the specification. | +| SSB Transmit power | M | | INTEGER (-60..50) | EPRE of SSS | +| SSB periodicity | M | | ENUMERATED(ms 5, ms10, ms20, ms40, ms80, ms160, ...) | | +| SSB half frame index | M | | INTEGER(0..1) | | +| SSB SFN offset | M | | INTEGER(0..15) | | +| CHOICE SSB Position in Burst | O | | | | +| >Short | | | | | +| >>Short Bitmap | | | BIT STRING (SIZE(4)) | | +| >Medium | | | | | +| >>Medium Bitmap | | | BIT STRING (SIZE(8)) | | +| >Long | | | | | +| >>Long Bitmap | | | BIT STRING (SIZE(64)) | | +| SFN Initialisation Time | O | | Relative Time 1900
9.3.1.183 | | + +### 9.3.1.204 Search Window Information + +This information element contains search window information for the TRP. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Expected Propagation Delay | M | | INTEGER (-3841..3841,...) | Indicates when the SRS is expected to arrive in time at the TRP relative to the UL RTOA Reference Time.
The UL RTOA Reference Time for a target SRS is defined as , where
- is the SFN Initialisation Time
- , where and are the system frame number and the subframe number of the SRS, respectively.
Granularity 4Ts, where $T_s = 1/(15 \cdot 10^3 \cdot 2048)$ seconds.
Centre of the search window. | +| Delay Uncertainty | M | | INTEGER (1..246,...) | Indicates the uncertainty of the expected SRS arrival time at the TRP
Granularity 4Ts, where $T_s = 1/(15 \cdot 10^3 \cdot 2048)$ seconds.
Single-sided search window. | + +### 9.3.1.205 Extended gNB-DU Name + +This IE provides extended human readable name of the gNB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|-----------------------------------|-----------------------| +| gNB-DU Name Visible | O | | VisibleString (SIZE(1..150, ...)) | | +| gNB-DU Name UTF8 | O | | UTF8String (SIZE(1..150, ...)) | | + +### 9.3.1.206 Extended gNB-CU Name + +This IE provides extended human readable name of the gNB-CU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|-----------------------------------|-----------------------| +| gNB-CU Name Visible | O | | VisibleString (SIZE(1..150, ...)) | | +| gNB-CU Name UTF8 | O | | UTF8String (SIZE(1..150, ...)) | | + +### 9.3.1.207 F1-C Transfer Path + +This IE indicates the transmission path of the F1-C traffic. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|----------------------------|-----------------------------------------------------------------------| +| F1-C Path NSA | M | | ENUMERATED (lte, nr, both) | This IE indicates the transmission path of the F1-C traffic in EN-DC. | + +### 9.3.1.208 SFN Offset + +This IE contains the time offset between an absolute time reference and the SFN0 start. The IE is calculated assuming that the SFN transmission started at the absolute time reference. The absolute time reference chosen is the 1980-01-06 T00:00:19 International Atomic Time (TAI). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SFN Time Offset | M | | BIT STRING (SIZE(24)) | Time offset in microseconds between the absolute time reference "1980-01-06 T00:00:19 International Atomic Time (TAI)" and the SFN0 start. The maximum usable value is (1024*10 4 -1). Values higher than the maximum are discarded. | + +### 9.3.1.209 Transmission Stop Indicator + +This IE indicates to stop the data transmission at gNB-DU side for an DRB not subject to DAPS Handover. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------|----------|-------|------------------------|-----------------------| +| Transmission Stop Indicator | M | | ENUMERATED (true, ...) | | + +### 9.3.1.210 Spatial Relation Information per SRS Resource + +This information element indicates a spatial relation for transmission of each UL SRS resource recommended by LMF. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------------|----------|-------------------------------|-----------------------|-----------------------| +| Spatial Relation per SRS Resource List | | 1 | | | +| >Spatial Relation per SRS Resource Item | | 1.. | | | +| >CHOICE Reference Signal | M | | | | +| >>NZP CSI-RS | | | | | +| >>>NZP CSI-RS Resource ID | M | | INTEGER (0..191) | | +| >>SSB | | | | | +| >>>NR PCI | M | | INTEGER (0..1007) | | +| >>>SSB Index | O | | INTEGER (0..63) | | +| >>SRS | | | | | +| >>>SRS Resource ID | M | | INTEGER (0..63) | | +| >>Positioning SRS | | | | | +| >>>Positioning SRS Resource ID | M | | INTEGER (0..63) | | +| >>DL-PRS | | | | | +| >>>DL-PRS ID | M | | INTEGER (0..255) | | +| >>>DL-PRS Resource Set ID | M | | INTEGER (0..7) | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------|-----------------------|-----------------------| +| >>>DL-PRS Resource ID | O | | INTEGER (0..63) | | + +| Range bound | Explanation | +|-------------------------|----------------------------------------------------------------| +| maxnoSRS-ResourcePerSet | Maximum no of SRS resources per SRS resource set. Value is 16. | + +### 9.3.1.211 CCO Assistance Information + +This IE provides assistance information for the Capacity and Coverage (CCO) actions for specific CCO issues detected, and for network energy saving. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------|----------|-------|-----------------------------------------------------------------------|---------------------------------------------------------------------------| +| CCO issue detection | O | | ENUMERATED (coverage, cell edge capacity, ..., network energy saving) | Indicates the type of CCO issue detected, or network energy saving cause. | +| Affected Cells and Beams | O | | 9.3.1.212 | | + +### 9.3.1.212 Affected Cells and Beams + +This IE includes a list of cells and/or SS/PBCH block indexes affected by the detected CCO issue. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------------------------|-----------------------|-----------------------| +| Affected Cell List | | 1 .. | | | +| >NR CGI | M | | 9.3.1.12 | | +| >Affected SSB List | | 0.. | | | +| >>SSB Index | M | | INTEGER (0..63) | | + +| Range bound | Explanation | +|------------------|------------------------------------------------------------------------------| +| maxAffectedCells | Maximum numbers of cells affected by a CCO issue. Value is 32. | +| maxnoofSSBAreas | Maximum no. SSB Areas that can be served by a NG-RAN node cell. Value is 64. | + +### 9.3.1.213 Coverage Modification Notification + +This IE includes a list of cells and/or SS/PBCH block indexes with the corresponding coverage configuration selected by the gNB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------|----------|------------------------|-----------------------|-----------------------|-------------|----------------------| +| Coverage Modification List | | 1 | | | | | +| >Coverage Modification Item | | 1 .. | | | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------|----------|-----------------------|-----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>NR CGI | M | | 9.3.1.12 | | - | | +| >>Cell Coverage State | | | INTEGER (0..63, ...) | Value '0' indicates that the cell is inactive. Other values Indicates that the cell is active and also indicates the coverage configuration of the concerned cell. | - | | +| >>SSB Coverage Modification List | | 0..1 | | | - | | +| >>>SSB Coverage Modification Item | | 1.. | | | - | | +| >>>>SSB Index | M | | INTEGER (0..63) | | - | | +| >>>>SSB Coverage State | M | | INTEGER (0..15, ...) | Value '0' indicates that the SS/PBCH block is inactive. Other values Indicates that the SS/PBCH block is active and also indicates the coverage configuration of the concerned SS/PBCH block. | - | | +| >>Coverage Modification Cause | O | | ENUMERATE D(coverage, cell edge capacity, ..., network energy saving) | | YES | ignore | + +| Range bound | Explanation | +|-----------------|------------------------------------------------------------------------------| +| maxCellingNBUDU | Maximum numbers of cells that can be served by a gNB-DU. Value is 512. | +| maxnoofSSBAreas | Maximum no. SSB Areas that can be served by a NG-RAN node cell. Value is 64. | + +### 9.3.1.214 Cells for SON List + +This IE contains a list of served cells in potential PRACH conflict and it may contain neighbour cell PRACH configuration. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------------------|-----------------------|-----------------------| +| Cells for SON Item | | 1 .. | | | + +| | | | | | +|----------------------------------|---|----------------------|-----------|--| +| | | ellforSON> | | | +| >NR CGI | M | | 9.3.1.12 | | +| >Neighbour NR Cells for SON List | O | | 9.3.1.215 | | + +| Range bound | Explanation | +|---------------------|---------------------------------------------------------------------------------| +| maxServedCellforSON | Maximum numbers of served cells where PRACH conflict is possible. Value is 256. | + +### 9.3.1.215 Neighbour NR Cells for SON List + +This IE contains the configuration of NR neighbour cells which the gNB-DU may take into consideration for SON purposes. + +NOTE: If multiple served cells share a common neighbour cell and thus multiple copies of *Neighbour NR Cells for SON Item* IE for the neighbour cell are needed to be contained in an F1AP message, IEs other than the *NR CGI* IE may be omitted in the copies other than the first one present in the message. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------|----------|----------------------------------|-----------------------|-----------------------| +| Neighbour NR Cells for SON Item | | 1 ..
| | | +| >NR CGI | M | | 9.3.1.12 | | +| >NR Mode Info Rel16 | O | | 9.3.1.216 | | +| >SSB Positions In Burst | O | | 9.3.1.138 | | +| >NR Cell PRACH Configuration | O | | 9.3.1.139 | | + +| Range bound | Explanation | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| maxNeighbourCellforSON | Maximum numbers of neighbour cells which the gNB-DU may take into consideration for SON purposes on a given served cell. Value is 32. | + +### 9.3.1.216 NR Mode Info Rel16 + +This IE contains the information of a NR cell which needs to be encoded differently for FDD and TDD. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------|----------|-------|-----------------------------------|-----------------------| +| CHOICE NR-Mode-Info-Rel16 | M | | | | +| >FDD | | | | | +| >>FDD Info Rel16 | | 1 | | | +| >>>UL Frequency Info | O | | Frequency Info Rel16
9.3.1.217 | | +| >>>SUL Frequency Info | O | | Frequency Info Rel16
9.3.1.217 | | +| >TDD | | | | | +| >>TDD Info Rel16 | | 1 | | | +| >>>TDD Frequency | O | | Frequency Info | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------|----------|-------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| Info | | | Rel16
9.3.1.217 | | +| >>>SUL Frequency Info | O | | Frequency Info
Rel16
9.3.1.217 | | +| >>>TDD DL-UL
Configuration Common
NR | O | | OCTET STRING | Includes the tdd-UL-DL-ConfigurationCommon contained in the ServingCellConfigCommon IE as defined in TS 38.331 [8] | + +### 9.3.1.217 Frequency Info Rel16 + +This IE contains the information of a NR cell which should be encoded separately among FDD NDL, FDD NUL, TDD NDL+NUL and SUL. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------|----------|-------|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NR ARFCN | O | | INTEGER (0..
maxNRARFCN) | RF Reference Frequency as defined in TS 38.104 [17] section 5.4.2.1. The frequency provided in this IE identifies the absolute frequency position of the reference resource block (Common RB 0) of the carrier. Its lowest subcarrier is also known as Point A. | +| Frequency Shift 7p5khz | O | | ENUMERATED
(false, true, ...) | Indicate whether the value of $\Delta_{\text{shift}}$ is 0kHz or 7.5kHz when calculating $F_{\text{REF,shift}}$ as defined in Section 5.4.2.1 of TS 38.104 [17]. | +| Carrier List | O | | NR Carrier List
9.3.1.137 | | + +| Range bound | Explanation | +|-------------|-----------------------------------------------| +| maxNRARFCN | Maximum value of NR ARFCNs. Value is 3279165. | + +### 9.3.1.218 MBS Session ID + +This IE indicates the MBS Session ID uniquely identifies an MBS session. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|---------------------------|----------------------------------------------------------------------------| +| TMGI | M | | OCTET STRING
(SIZE(6)) | Coded as Temporary Mobile Group Identity (TMGI) defined in TS 23.003 [23]. | +| NID | O | | 9.3.1.155 | | + +### 9.3.1.219 gNB-CU MBS F1AP ID + +The gNB-CU MBS F1AP ID uniquely identifies the MBS association over the F1 interface within the gNB-CU. + +NOTE: If F1-C signalling transport is shared among multiple interface instances, the value of the gNB-CU MBS F1AP ID is allocated so that it can be associated with the corresponding F1-C interface instance. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|-----------------------------------|-----------------------| +| gNB-CU MBS F1AP ID | M | | INTEGER (0 .. 2 32 -1) | | + +### 9.3.1.220 gNB-DU MBS F1AP ID + +The gNB-DU MBS F1AP ID uniquely identifies the MBS association over the F1 interface within the gNB-DU. + +NOTE: If F1-C signalling transport is shared among multiple interface instances, the value of the gNB-DU MBS F1AP ID is allocated so that it can be associated with the corresponding F1-C interface instance. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|-----------------------------------|-----------------------| +| gNB-DU MBS F1AP ID | M | | INTEGER (0 .. 2 32 -1) | | + +### 9.3.1.221 MBS Area Session ID + +This IE indicates the Area Session ID for MBS Session with location dependent context. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|---------------------------|-----------------------| +| MBS Area Session ID | M | | INTEGER (0 .. 65535, ...) | | + +### 9.3.1.222 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 independent | | | | | +| >>MBS Service Area Information | M | | 9.3.1.223 | | +| > location dependent | | | | | +| >>MBS Service Area Information Location Dependent List | | 1..maxnoofMBSServiceAreaInformation | | | +| >>>MBS Area Session ID | M | | 9.3.1.221 | | +| >>>MBS Service Area Information | M | | 9.3.1.223 | | + +| 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.1.223 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.12 | | +| MBS Service Area TAI List | | 0..<maxnoofTAIforMBS> | | | +| >PLMN-Identity | M | | 9.3.1.14 | | +| >5GS TAC | M | | 9.3.1.29 | | + +| 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.1.224 MRB ID + +This IE indicates the MRB ID as specified in TS 38.401 [4]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| MRB ID | M | | INTEGER (1..512, ...) | | + +### 9.3.1.225 MBS CU to DU RRC Information + +This IE indicates the MBS CU to DU RRC Information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------|----------|------------------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------| +| MBS Broadcast Cell List | M | | | | +| > MBS Broadcast Cell Item | | 1 .. <maxCellingNBDU> | | | +| >>NR CGI | M | | NR CGI 9.3.1.12 | | +| >>mtch-neighbourCell | O | | OCTET STRING | Includes the mtch-NeighbourCell-r17 contained in the MBS-SessionInfoList IE, as defined in TS 38.331[8] | +| MBS Broadcast MRB List | | 1 | | | +| > MBS Broadcast MRB Item | | 1 .. <maxnoofMRBs> | | | +| >>MRB ID | M | | 9.3.1.224 | | +| >>MRB PDCP Config Broadcast | M | | OCTET STRING | Includes the MRB-PDCP-ConfigBroadcast IE, as defined in TS 38.331[8]. | + +| Range bound | Explanation | +|----------------|-----------------------------------------------------------------| +| maxCellingNBDU | Maximum no. cells that can be served by a gNB-DU. Value is 512. | +| maxnoofMRBs | Maximum no. MRBs allowed to be setup for one MBS session, the | + +| | | +|--|----------------------| +| | maximum value is 32. | +|--|----------------------| + +### 9.3.1.226 MBS Broadcast Neighbour Cell List + +This IE indicates a list of neighbour cells where ongoing MBS sessions provided via broadcast MRB in the current cells are also provided. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------| +| MBS Broadcast Neighbour Cell List | M | | OCTET STRING | Includes the MBS-NeighbourCellList IE, as defined in TS 38.331[8] | + +### 9.3.1.227 IAB Congestion Indication + +This IE contains the IAB downlink congestion indication. This IE is only applicable if the gNB-DU is an IAB-DU or IAB-donor-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------|----------|--------------------------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| IAB Congestion Indication List | | 1 | | | +| > IAB Congestion Indication Item | | 1..
| | | +| >>Child Node Identifier | M | | BAP Address
9.3.1.111 | This IE identifies the child node, the link to which is congested. | +| >> BH RLC CH List | | 0..1 | | | +| >>> BH RLC CH Item | | 1..
| | | +| >>>>BH RLC CH ID | M | | BH RLC Channel ID
9.3.1.113 | This IE identifies the congested BH RLC channel over the link towards the node identified by the Child Node Identifier IE. | + +| Range bound | Explanation | +|-----------------------|------------------------------------------------------------------------------------------| +| maxnoofIABCongInd | Maximum no. of congestion indications, the maximum value is 1024. | +| maxnoofBHR LCChannels | Maximum no. of BH RLC channels allowed towards one IAB-node, the maximum value is 65536. | + +### 9.3.1.228 F1-C Transfer Path NRDC + +This IE indicates the transmission path of the F1-C traffic in NR-DC. This IE is only applicable if the UE is an IAB-MT. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|--------------------------------|-----------------------------------------------------------------------| +| F1-C Path NRDC | M | | ENUMERATED
(mcg, scg, both) | This IE indicates the transmission path of the F1-C traffic in NR-DC. | + +### 9.3.1.229 IAB TNL Address Exception + +This IE indicates the list of TNL addresses, pertaining to the packets to be forwarded via the inter-IAB-donor-DU tunnel by the IAB-donor-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------|----------|-------------------------|-----------------------|-----------------------| +| IAB TNL Address List | | 1 | | | +| > IAB IAB TNL Address Item | | 1..
| | | +| >> IAB TNL Address | M | | 9.3.1.102 | | + +| Range bound | Explanation | +|----------------|-----------------------------------------------------------------------------------------------------------------------| +| maxnoofTLAsIAB | Maximum no. of individual IPv4/IPv6 addresses or IPv6 address prefixes in one procedure execution. The value is 1024. | + +### 9.3.1.230 RB Set Configuration + +This IE contains the RB Set Configuration. The IE is only applicable if the gNB-DU is an IAB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Subcarrier Spacing | M | | ENUMERATED
(kHz15, kHz30, kHz60, kHz120, kHz240, spare3, spare2, spare1, ...) | Subcarrier spacing used as reference for the RB set configuration. | +| RB Set Size | M | | ENUMERATED
(rb2, rb4, rb8, rb16, rb32, rb64) | Number of PRBs in each RB set. If the RB sets of IAB-DU H/S/NA resource configuration do not cover the entire carrier bandwidth, the remaining RBs not part of an RB set configuration are considered as included in the last RB set. | +| Number of RB Sets | M | | INTEGER(1..
maxnoofRBsetsPerCell ) | Number of configured RB sets. The RB sets are contiguous and non-overlapping. If NR Carrier List IE(9.3.1.137) is provided, the start RB index of the first RB set is the RB index of the lowest common RB with the SCS provided by RB Set Configuration IE, which overlaps with the lowest usable RB across all SCS-specific carriers provided by the NR Carrier List IE for the IAB-DU cell. Otherwise, the start RB of the first RB set is aligned with point A for the IAB-DU cell. | + +| Range bound | Explanation | +|----------------------|-----------------------------------------------------| +| maxnoofRBsetsPerCell | Maximum no. of RB sets per IAB-DU cell. Value is 8. | + +### 9.3.1.231 Survival Time + +This IE indicates the Survival Time of the TSC QoS flow as defined in TS 23.501 [21]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|---------------------------|-----------------------------| +| Survival Time | M | | INTEGER (0..1920000, ...) | Expressed in units of 1 us. | + +### 9.3.1.232 PDC Measurement Result + +The purpose of this IE is to provide the PDC measurement result. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------|----------|---------------------|-------------------------|-----------------------------------------------| +| PDC Measured Results List | | 1 | | | +| > PDC Measured Results Item | | 1 .. | | | +| >>CHOICE Measured Results Value | M | | | | +| >>> NR PDC Timing Advance | | | | | +| >>>>NR PDC Timing Advance | M | | INTEGER (0..62500, ...) | Value is expressed in unit of $[64 * T_c]$ ns | +| >>> PDC gNB Rx-Tx Time Difference | | | | | +| >>>>PDC gNB Rx-Tx Time Difference | M | | INTEGER (0..61565, ...) | Report mapping as defined in TS 38.133 [38] | + +| Range bound | Explanation | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------| +| maxnoMeasPDC | Maximum no. of measured quantities that can be configured and reported with one message. Value is 16. Maximum is 1 in this release. | + +### 9.3.1.233 SCG Activation Request + +This IE indicates whether the SCG resources are required to be activated or deactivated. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------|----------|-------|------------------------------------------------|-----------------------| +| SCG Activation Request | M | | ENUMERATED (activate SCG, deactivate SCG, ...) | | + +### 9.3.1.234 SCG Activation Status + +This 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.235 Requested DL PRS Transmission Characteristics + +This IE contains the requested PRS configuration for transmission by the gNB-CU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------|----------|-----------------------------|-------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------| +| Requested DL-PRS Resource Set List | | 1 | | | +| > Requested DL-PRS Resource Set Item | | 1.. | | | +| >>PRS bandwidth | O | | INTEGER(1..63) | 24,28,...,272 PRBs | +| >>Comb Size | O | | ENUMERATED(2, 4, 6, 12, ...) | | +| >>Resource Set Periodicity | O | | ENUMERATED(4,5, 8,10,16,20,32,40,64, 80,160,320,640,128 0,2560,5120,10240, 20480,40960,81920, ..., 128, 256, 512) | Slots | +| >>Resource Repetition Factor | O | | ENUMERATED(rf1,rf2,rf4,rf6,rf8,rf16,rf32, ...) | | +| >>Resource Number of Symbols | O | | ENUMERATED(n2, n4,n6,n12,...,n1) | | +| >>Requested DL-PRS Resource List | O | | 9.3.1.250 | | +| >>Resource Set Start Time and Duration | O | | Start Time and Duration 9.3.1.236 | This IE is ignored if the Start Time and Duration IE is present | +| Number of Frequency Layers | O | | INTEGER(1..4) | | +| Start Time and Duration | O | | 9.3.1.236 | | + +| Range bound | Explanation | +|------------------------|----------------------------------------------| +| maxnoofPRSresourceSets | Maximum no of PRS resources set. Value is 8. | + +### 9.3.1.236 Start Time and Duration + +This IE contains the start time and/or duration for the on-demand DL-PRS. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|------------------------------|-----------------------| +| Start Time | O | | Relative Time 1900 9.3.1.183 | | +| Duration | O | | INTEGER (0..90060, ...) | Unit: seconds | + +### 9.3.1.237 PRS Transmission Off Information + +This IE contains the information to turn off particular PRS transmissions. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|----------------------------|-----------------------|-----------------------| +| CHOICE level | M | | | | +| >TRP level | | | NULL | | +| >PRS resource set level | | | | | +| >>PRS Resource Set List | | 1 | | | +| >>>PRS Resource Set Item | | 1.. | | | +| >>>>PRS Resource Set ID | M | | INTEGER(0..7) | | +| >PRS resource level | | | | | +| >>PRS Resource Set List | | 1 | | | +| >>>PRS Resource Set Item | | 1.. | | | +| >>>>PRS Resource Set ID | M | | INTEGER(0..7) | | +| >>>>>PRS Resource List | | 1 | | | +| >>>>>PRS Resource Item | | 1.. | | | +| >>>>>>PRS Resource ID | M | | INTEGER(0..63) | | + +| Range bound | Explanation | +|-----------------------|----------------------------------------------------------------| +| maxnoofPRSresourceSet | Maximum no of PRS resources set. Value is 8. | +| maxnoofPRSresource | Maximum no of PRS resources per PRS resource set. Value is 64. | + +### 9.3.1.238 UL-AoA Assistance Information + +This information element contains the expected uplink Angle of Arrival and uncertainty range. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------| +| CHOICE AngleMeasurement | M | | | | +| >Expected UL Angle of Arrival | | | | | +| >>Expected Azimuth AoA | | 1 | | Defined as $(\phi_{\text{AoA}} - \Delta\phi_{\text{AoA}}/2, \phi_{\text{AoA}} + \Delta\phi_{\text{AoA}}/2)$ | +| >>Expected Azimuth AoA Value | M | | INTEGER(0..3599) | $\phi_{\text{AoA}}$ component of Expected Azimuth AoA | +| >>Expected Azimuth AoA Uncertainty Range | M | | INTEGER(0..3599) | $\Delta\phi_{\text{AoA}}$ component of Expected Azimuth AoA | +| >>Expected Zenith AoA | | 0..1 | | Defined as $(\theta_{\text{ZOA}} - \Delta\theta_{\text{ZOA}}/2, \theta_{\text{ZOA}} + \Delta\theta_{\text{ZOA}}/2)$ | +| >>Expected Zenith AoA Value | M | | INTEGER(0..1799) | $\theta_{\text{ZOA}}$ component of Expected Zenith AoA | +| >>Expected Zenith AoA Uncertainty Range | M | | INTEGER(0..1799) | $\Delta\theta_{\text{ZOA}}$ component of Expected Zenith AoA | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------| +| >Expected UL Angle of Arrival Zenith Only | | | | Defined as $(\theta_{ZOA} - \Delta\theta_{ZOA}/2, \theta_{ZOA} + \Delta\theta_{ZOA}/2)$ | +| >>Expected Zenith AoA Value | M | | INTEGER(0..1799) | $\theta_{ZOA}$ component of Expected Zenith AoA | +| >>Expected Zenith AoA Uncertainty Range | M | | INTEGER(0..1799) | $\Delta\theta_{ZOA}$ component of Expected Zenith AoA | +| LCS to GCS Translation | O | | 9.3.1.241 | If absent, the azimuth and zenith are provided in GCS. In case of zenith only, the z-axis of LCS is defined along the linear array axis. | + +### 9.3.1.239 Zenith Angle of Arrival Information + +This information element contains the Zenith Angle of Arrival, which can correspond to linear array measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------| +| Zenith Angle of Arrival | M | | INTEGER(0..1799) | TS 38.133 [38] | +| LCS to GCS Translation | O | | 9.3.1.241 | If absent, the zenith is provided in GCS. the z-axis of LCS is defined along the linear array axis | + +### 9.3.1.240 On-demand PRS TRP Information + +This IE contains on-demand PRS information for the TRP. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| On-demand PRS Request Allowed | M | | BIT STRING (SIZE(16)) | Each position in the bitmap represents an on-demand PRS transmission parameter:
first bit: Resource Set Periodicity
second bit: PRS Bandwidth
third bit: Resource Repetition Factor
fourth bit: Resource Number of Symbols
fifth bit: Comb Size
sixth bit: Number of Frequency Layers
seventh bit: Start Time and Duration
eighth bit: Off Indication
ninth bit: QCL Information
Other bits reserved for future use. Value '1' indicates 'request allowed', Value '0' indicates 'request not allowed'. | +| Allowed Resource Set Periodicity Values | O | | BIT STRING (SIZE(24)) | This IE applies only if the first bit of the On-demand PRS Request Allowed IE is set to '1'. | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | Each position in the bitmap represents a value of the Resource Set Periodicity IE defined in subclause 9.2.x1, first bit = 4 and so on. Bit 24 is reserved for future use. Value '1' indicates 'request allowed', Value '0' indicates 'request not allowed'. If this IE is absent, all Resource Set Periodicity values are allowed to be requested. | +| Allowed PRS Bandwidth Values | O | | BIT STRING (SIZE(64)) |

This IE applies only if the second bit of the On-demand PRS Request Allowed IE is set to '1'.

Each position in the bitmap represents a value of the PRS Bandwidth IE defined in subclause 9.2.x1, first bit = 1 and so on. Bit 64 is reserved for future use. Value '1' indicates 'request allowed', Value '0' indicates 'request not allowed'. If this IE is absent, all PRS Bandwidth values are allowed to be requested.

| +| Allowed Resource Repetition Factor Values | O | | BIT STRING (SIZE(8)) |

This IE applies only if the third bit of the On-demand PRS Request Allowed IE is set to '1'.

Each position in the bitmap represents a value of the Resource Repetition Factor IE defined in subclause 9.2.x1, first bit = rf1 and so on. Bit 8 is reserved for future use. Value '1' indicates 'request allowed', Value '0' indicates 'request not allowed'. If this IE is absent, all Resource Repetition Factor values are allowed to be requested.

| +| Allowed Resource Number of Symbols Values | O | | BIT STRING (SIZE(8)) |

This IE applies only if the fourth bit of the On-demand PRS Request Allowed IE is set to '1'.

Each position in the bitmap represents a value of the Resource Number of Symbols IE defined in subclause 9.2.x1, first bit = n2 and so on. Bits 6-8 are reserved for future use. Value '1' indicates 'request allowed', Value '0' indicates 'request not allowed'. If this IE is absent, all Resource Number of Symbols values are allowed to be requested.

| + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Allowed Comb Size Values | O | | BIT STRING (SIZE(8)) |

requested.

This IE applies only if the fifth bit of the On-demand PRS Request Allowed IE is set to '1'.

Each position in the bitmap represents a value of the Comb Size IE defined in subclause 9.2.x1, first bit = 2 and so on. Bits 5-8 are reserved for future use. Value '1' indicates 'request allowed', Value '0' indicates 'request not allowed'. If this IE is absent, all Comb Size values are allowed to be requested.

| + +### 9.3.1.241 LCS to GCS Translation + +This IE contains the LCS to GCS Translation information. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| Alpha | M | | INTEGER (0..3599) | | +| Beta | M | | INTEGER (0..3599) | | +| Gamma | M | | INTEGER (0..3599) | | + +### 9.3.1.242 Response Time + +This information element contains the response time of the measurement results reporting. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|---------------------------------------------------------|-----------------------| +| Time | M | | INTEGER(1..128, ...) | | +| Time Unit | M | | ENUMERATED(sec ond, ten-seconds, ten-milliseconds, ...) | | + +### 9.3.1.243 ARP Location Information + +This IE contains the relative position of ARP(s) to the TRP. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|----------------|-----------------------|-----------------------| +| ARP Location Information | | 1 | | | +| >ARP Location Information Item | | 1.. | | | +| >>ARP ID | M | | 9.3.1.244 | | +| >>CHOICE ARP Location Type | M | | | | +| >>>geodetic | | | | | +| >>>>ARP Position | M | | Relative Geodetic | | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------|----------|-------|---------------------------------------------|-----------------------| +| Relative Geodetic | | | Location
9.3.1.186 | | +| >>> cartesian | | | | | +| >>>>ARP Position
Relative Cartesian | M | | Relative Cartesian
Location
9.3.1.187 | | + +| Range bound | Explanation | +|-------------|---------------------------------------------------------| +| maxnoARPs | Maximum no. of ARPs associated with a TRP. Value is 16. | + +### 9.3.1.244 ARP ID + +This IE is used to uniquely identify an ARP associated with a TRP. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|-------------------------|-----------------------| +| ARP Identifier | M | | INTEGER (1..16,
...) | | + +### 9.3.1.245 Multiple UL AoA + +This information element contains the list of the multiple UL AOAs values. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|--------------------|-----------------------|-----------------------| +| UL AoA List | | 1 | | | +| > UL AoA item | | 1.. | | | +| >>CHOICE
AngleMeasurement | M | | | | +| >>> UL Angle of Arrival | | | | | +| >>>>UL Angle of Arrival | M | | 9.3.1.167 | | +| >>> UL Zenith Angle of Arrival | | | | | +| >>>>Zenith Angle of Arrival Information | M | | 9.3.1.239 | | + +| Range bound | Explanation | +|---------------|------------------------------------------------------------------------------------------| +| maxnoofULAoAs | Maximum no of UL-AOAs values (pair of AOA & ZOA values) that can be reported. Value is 8 | + +### 9.3.1.246 UL SRS-RSRP + +This information element contains the UL SRS RSRP measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +|---------------|----------|-------|-----------------------|-----------------------| + +| | | | Reference | | +|-----------------------|---|--|------------------|--| +| First Path RSRP Power | M | | INTEGER (0..126) | | + +### 9.3.1.247 SRS Resource type + +This IE contains the SRS resource type. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------|----------|-------|--------------------------------------------------|-----------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE Reference Signal | M | | | | - | | +| >SRS | | | | | | | +| >>SRS Resource ID | M | | INTEGER(0..63 ) | | - | | +| >Positioning SRS | | | | | | | +| >>Positioning SRS Resource ID | M | | INTEGER(0..63 ) | | - | | +| SRS Port Index | O | | ENUMERATED (id1000, id1001, id1002, id1003, ...) | This IE may be present if the SRS Resource ID IE is present, and is ignored otherwise. | YES | ignore | + +### 9.3.1.248 Extended Additional Path List + +This IE contains the extended additional path results of time measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------|----------|------------------------|-----------------------------------|-----------------------| +| Additional Path Item | | 1.. | | | +| >CHOICE Relative Path Delay | M | | | | +| >>k0 | | | | | +| >>>k0 | M | | INTEGER(0..16351) | | +| >>k1 | | | | | +| >>>k1 | M | | INTEGER(0..8176) | | +| >>k2 | | | | | +| >>>k2 | M | | INTEGER(0..4088) | | +| >>k3 | | | | | +| >>>k3 | M | | INTEGER(0..2044) | | +| >>k4 | | | | | +| >>>k4 | M | | INTEGER(0..1022) | | +| >>k5 | | | | | +| >>>k5 | M | | INTEGER(0..511) | | +| >Path Quality | O | | TRP Measurement Quality 9.3.1.172 | | +| >Path Power | O | | UL SRS-RSRP 9.3.1.246 | | +| >Multiple UL AoA | O | | 9.3.1.245 | | + +| Range bound | Explanation | +|-------------------|---------------------------------------------------------| +| maxNoPathExtended | Maximum no. of additional path measurement. Value is 8. | + +### 9.3.1.249 LoS/NLoS Information + +This IE contains the LoS/NLoS information for UL measurement. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------|----------|-------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE LoS/NLoS Indicator | M | | | | +| > Soft Indicator | | | | | +| >>LoS/NLoS Indicator Soft | M | | INTEGER (0..10) | Values provide the likelihood of a LOS propagation path in the range between 0 and 1 with 0.1 steps resolution. Value '0' indicates NLOS and value '1' indicates LOS. | +| > Hard Indicator | | | | | +| >>LoS/NLoS Indicator Hard | M | | ENUMERATED (NLoS, LoS) | | + +### 9.3.1.250 Requested DL-PRS Resource List + +This IE contains the requested DL-PRS resource list. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|-------------------------|-----------------------|------------------------------------------------------------| +| Requested DL-PRS Resource List | | 1 | | NR-DL-PRS-Resource-r16 as defined in TS 37.355 [39] | +| > Requested DL-PRS Resource Item | | 1.. | | | +| >>CHOICE QCL Info | O | | | | +| >>>SSB | | | | | +| >>>>NR PCI | M | | INTEGER(0..1007) | | +| >>>>SSB Index | O | | INTEGER(0..63) | | +| >>> DL-PRS | | | | | +| >>>>QCL Source PRS Resource Set ID | M | | INTEGER(0..7) | | +| >>>>QCL Source PRS Resource ID | O | | INTEGER(0..63) | | + +| Range bound | Explanation | +|--------------------|----------------------------------------------------------------| +| maxnoofPRSresource | Maximum no of PRS resources per PRS resource set. Value is 64. | + +### 9.3.1.251 Void + +### 9.3.1.252 TRP Tx TEG Association + +This information element contains the TRP Tx TEG information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|----------------------|-----------------------|-----------------------| +| TRP TEG item | | 1 .. | | | + +| | | | | | +|---------------------------|---|----------------------------------------------|-----------------|--| +| >TRP Tx TEG Information | M | | 9.3.1.281 | | +| >DL-PRS Resource Set ID | M | | INTEGER (0..7) | | +| >DL-PRS Resource ID List | | 0..1 | | | +| >>DL-PRS Resource ID Item | | 1..<
maxnoofPRS-
ResourcesPer
Set > | | | +| >>>DL-PRS Resource ID | M | | INTEGER (0..63) | | + +| Range bound | Explanation | +|----------------------------|------------------------------------------------------------------------------------| +| maxnoTRPTEGs | Maximum no of reported TRP Tx TEG association. Value is 8. | +| maxnoofPRS-ResourcesPerSet | Maximum no of DL-PRS resources of the DL-PRS resource set of the TRP. Value is 64. | + +### 9.3.1.253 TRP TEG Information + +This information element contains the TRP TEG information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE TRP TEG | M | | | | +| >RxTx TEG | | | | | +| >>TRP RxTx TEG Information | M | | 9.3.1.282 | | +| >>TRP Tx TEG Information | O | | 9.3.1.281 | | +| >Rx TEG | | | | | +| >>TRP Rx TEG Information | M | | 9.3.1.280 | | +| >>TRP Tx TEG Information | M | | 9.3.1.281 | | + +### 9.3.1.254 Measurement Characteristics Request Indicator + +This IE contains the measurement characteristic information requested by the gNB-CU. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement characteristic request indicator | M | | BIT STRING (SIZE(16)) | Each position in the bitmap represents a requested measurement characteristic:

first bit: Measurement Beam Information

Second bit: Extended Additional Path List

Third bit: Additional Path Power

Fourth Bit: Multiple UL AoA of | + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | |

Additional Path

Fifth bit: LoS/NLoS Information

Sixth bit: TRP Rx TEG association for UL-TDOA

Seventh bit: TRP RxTxTEG-ID information for DL+UL positioning.

Eighth bit: SRS Resource Type

Ninth bit: Multiple Measurement Instances

Tenth bit: Mobile TRP location information

Other bits reserved for future use. Value '1' indicates 'requested measurement characteristic', Value '0' indicates 'not requested'.

| + +### 9.3.1.255 UE Reporting Information + +This IE contains the UE Reporting Information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|---------------------------------------------------|-------------------------------------------------------------| +| Reporting Amount | M | | ENUMERATED (0, 1, 2, 4, 8, 16, 32, 64) | Value 0 represents an infinite number of periodic reporting | +| Reporting Interval | M | | ENUMERATED (none, 1, 2, 4, 8, 10, 16, 20, 32, 64) | Unit: seconds | + +### 9.3.1.256 TRP Beam Antenna Information + +The IE provides the beam antenna information of the TRP. It includes either the explicit beam antenna information, or a reference to another TRP's signalled configuration, or the indication that no change has occurred with respect to previously signalled configuration. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE TRP Beam Antenna Info Item | M | | | | +| >Reference | | | | | +| >>Associated TRP ID | M | | TRP ID
9.3.1.197 | This IE specifies the TRP ID of the associated TRP from which the beam information parameters are adopted in Local Coordinate System (LCS). | + +| | | | | | +|---------------------------|---|--|-----------|------------------------------------------------------------------------| +| >Explicit | | | | | +| >>TRP Beam Antenna Angles | M | | 9.3.1.257 | | +| >>LCS to GCS Translation | O | | 9.3.1.241 | Included if the azimuth and elevation are not provided in GCS. | +| >No Change | | | NULL | No change compared to previously signalled configuration for this TRP. | + +### 9.3.1.257 TRP Beam Antenna Angles + +The IE provides the beam antenna information of the TRP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|---------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TRP Beam Antenna Angles Item | | 1.. | | | +| >TRP Azimuth Angle | M | | INTEGER (0..3599) | For GCS, the azimuth angle is measured counter-clockwise from geographical North. For LCS, the azimuth angle is measured counter-clockwise from the x-axis of the LCS. | +| >TRP Azimuth Angle fine | O | | INTEGER (0..9) | Fine angle | +| >TRP Elevation Angle List | | 1 | | | +| >>TRP Elevation Angle Item | | 1.. | | | +| >>>TRP Elevation Angle | M | | INTEGER (0..1800) | For 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 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). | +| >>>TRP Elevation Angle fine | O | | INTEGER (0..9) | Fine angle | +| >>>TRP Beam Power List | | 1 | | Relative power between DL-PRS Resources for the given Azimuth and Elevation Angle. The first Relative Power element in this list provides the peak power for this Azimuth/Elevation angle and is defined as 0dB power. All the remaining Relative Power Element's in this list provide the relative DL-PRS Resource power relative to this first element in the list. | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|--------------------------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| >>>>>TRP Beam Power Item | | 2..<
maxNumResourcesPerAngle
> | | | +| >>>>>PRS Resource Set ID | O | | INTEGER (0..7) | DL-PRS Resource Set ID of the DL-PRS Resource for which the Relative Power is provided. If this field is absent, the DL-PRS Resource Set ID for this instance of the Beam Power List is the same as the DL-PRS Resource Set ID of the previous instance in the Beam Power List. This field shall be included at least in the first instance of the Beam Power List. | +| >>>>>PRS Resource ID | M | | INTEGER (0..63) | DL-PRS Resource for which the Relative Power is provided. | +| >>>>>TRP Beam Relative Power | M | | INTEGER (0..30) | The power values span from -30 to 0dB | +| >>>>>TRP Beam Relative Power "fine" | O | | INTEGER (0..9) | Relative Power with 0.1dB resolution. The power spans from -0.9 to 0dB | + +| Range bound | Explanation | +|-------------------------|--------------------------------------------------------------------------| +| maxNumResourcesPerAngle | Maximum number of DL-PRS Resources per angle per TRP. Value is 24. | +| maxnoAzimuthAngles | Maximum number of azimuth angles per TRP. Value is 3600. | +| maxnoElevationAngles | Maximum number of elevation angles per azimuth angle/TRP. Value is 1801. | + +### 9.3.1.258 NR Paging eDRX Information + +This IE indicates the NR Paging eDRX parameters for RRC\_IDLE as defined in TS 38.304 [24]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| NR Paging eDRX Cycle Idle | M | | ENUMERATED(hfq
uarter, hfhalf, hf1, hf2, hf4, hf8, hf16, hf32, hf64, hf128, hf256, hf512, hf1024, ...) | T eDRX,CN defined in TS 38.304 [24]. Unit: [number of hyperframes]. | +| NR Paging Time Window | O | | ENUMERATED(s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s11, s12, s13, s14, s15, s16, ..., s17, s18, s19, s20, s21, s22, s23, s24, s25, s26, s27, s28, s29, s30, s31, s32) | Unit: [1.28 second]. | + +### 9.3.1.259 NR Paging eDRX Information for RRC INACTIVE + +This IE indicates the NR Paging eDRX parameters for RRC\_INACTIVE as defined in TS 38.304 [24]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------|----------|-------|------------------------------------------|--------------------------------------------------------------------------| +| NR Paging eDRX Cycle Inactive | M | | ENUMERATED (hfquarter, hfhalf, hf1, ...) | $T_{eDRX,RAN}$ defined in TS 38.304 [24]. Unit: [number of hyperframes]. | + +### 9.3.1.260 QoE Metrics + +This IE provides the RAN visible QoE measurement report to gNB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|-------|-----------------------|------------------------------| +| Application Layer Buffer Level List | O | | OCTET STRING | As defined in TS 38.331 [8]. | +| Playout Delay for Media Startup | O | | OCTET STRING | As defined in TS 38.331 [8]. | + +### 9.3.1.261 CG-SDT Session Info + +This IE identifies an CG-SDT session for a UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------|----------|-------|-----------------------|-----------------------| +| gNB-CU UE F1AP ID | M | | 9.3.1.4 | | +| gNB-DU UE F1AP ID | M | | 9.3.1.5 | | + +### 9.3.1.262 SDT Information + +This IE is used to indicate an SDT transaction and to provide the assistant information from the UE. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|---------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| SDT Indicator | M | | ENUMERATED (true,...) | | +| SDT Assistant Information | O | | ENUMERATED (single packet, multiple packets, ...) | “single packet” indicates no subsequent SDT transmission is expected.
“multiple packets” indicates subsequent SDT transmission is expected. | + +### 9.3.1.263 Path Switch Configuration + +This IE provides information for switching to an indirect path from a direct path. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|-----------------------|-------------------------------------------------------------------| +| Target Relay UE ID | M | | BIT STRING (SIZE(24)) | Corresponds to the targetRelayUE-Identity contained in the | + +| | | | | | +|--------------------|---|--|------------------------------------------------------------------------|----------------------------------------------------------------------------------------------| +| | | | | CellGroupConfig IE, defined in TS 38.331 [8] | +| Remote UE Local ID | M | | 9.3.1.267 | | +| T420 | M | | ENUMERATED (ms50, ms100, ms150, ms200, ms500, ms1000, ms2000, ms10000) | Corresponds to the t420 contained in the CellGroupConfig IE, defined in TS 38.331 [8] | + +### 9.3.1.264 Sidelink Relay Configuration + +This IE provides information of a U2N Remote UE when accessing the network via a U2N Relay UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------|----------|-------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gNB-DU UE F1AP ID of Relay UE | M | | gNB-DU UE F1AP ID
9.3.1.5 | | +| Remote UE Local ID | M | | 9.3.1.267 | | +| Sidelink Configuration Container | O | | OCTET STRING | Includes the SL-ConfigDedicatedNR IE as defined in subclause 6.3.5 in TS 38.331 [8] to carry PC5 Relay RLC channel configuration for Remote UE's SRB1. | + +### 9.3.1.265 PC5 RLC Channel ID + +This IE uniquely identifies a PC5 Relay RLC channel for a L2 U2N Remote UE or a L2 U2N Relay UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|-----------------------|-----------------------| +| PC5 RLC Channel ID | M | | INTEGER (1..512, ...) | | + +### 9.3.1.266 Uu RLC Channel ID + +This IE uniquely identifies a Uu Relay RLC channel for a L2 U2N Relay UE or a L2 MP Relay UE using N3C. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------| +| Uu RLC Channel ID | M | | INTEGER (1..32) | Corresponds to information provided in the Uu-RelayRLC-ChannelID IE defined in 38.331 [8]. | + +### 9.3.1.267 Remote UE Local ID + +This IE uniquely identifies a L2 U2N Remote UE within the connected Relay UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------| +| Remote UE Local ID | M | | INTEGER (0..255, ...) | Corresponds to the s/LocalIdentity contained in the SL-SRAP-Config IE defined in TS 38.331 [8]. | + +### 9.3.1.268 5G ProSe Authorized + +This IE provides information on the authorization status of the UE for NR ProSe services. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|----------|-------|----------------------------------------------|------------------------------------------------------------------------------------------------------|-------------|----------------------| +| 5G ProSe Direct Discovery | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized for 5G ProSe Direct Discovery | - | | +| 5G ProSe Direct Communication | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized for 5G ProSe Direct Communication | - | | +| 5G ProSe Layer-2 UE-to-Network Relay | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized for 5G ProSe Layer-2 UE-to-Network Relay | - | | +| 5G ProSe Layer-3 UE-to-Network Relay | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized for 5G ProSe Layer-3 UE-to-Network Relay | - | | +| 5G ProSe Layer-2 Remote UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized for 5G ProSe Layer-2 Remote UE | - | | +| 5G ProSe Layer-2 Multi-path | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the 5G ProSe Layer-2 Remote UE is authorized for 5G ProSe multi-path transmission. | YES | ignore | +| 5G ProSe Layer-2 UE-to-UE Relay | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized for 5G ProSe Layer-2 UE-to-UE Relay UE | YES | ignore | +| 5G ProSe Layer-2 UE-to-UE Remote | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized for 5G ProSe Layer-2 UE-to-UE Remote UE. | YES | ignore | + +### 9.3.1.269 PEIPS Assistance Information + +This IE provides the information related to CN paging subgrouping for a particular UE, as specified in TS 38.304 [24]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------|----------|-------|-----------------------|-----------------------| +| CN Subgroup ID | M | | INTEGER (0..7, ...) | | + +### 9.3.1.270 UE Paging Capability + +This IE provides the UE Paging Capability information needed for paging. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| INACTIVE State PO-Determination | O | | ENUMERATED (supported,...) | Corresponds to the inactiveStatePO-Determination contained in the UERadioPagingInformation IE defined in TS 38.331 [8]. | - | - | +| RedCap Indication | O | | ENUMERATED (true,...) | Indicates that the paged UE is a Redcap UE or an eRedCap UE. | YES | Ignore | + +### 9.3.1.271 gNB-DU UE Slice Maximum Bit Rate List + +This IE contains the UE Slice Maximum Bit Rate List as specified in TS 23.501 [21]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|-----------------------|-----------------------|--------------------------------------------------------------------------------------------| +| UE Slice Maximum Bit Rate Item | | 1.. | | | +| >S-NSSAI | M | | 9.3.1.38 | | +| >UE Slice Maximum Bit Rate Uplink | M | | Bit Rate 9.3.1.22 | This IE indicates the UE-Slice-MBR as specified in TS 23.501 [21] in the uplink direction. | + +| Range bound | Explanation | +|------------------|--------------------------------------------------------------------| +| maxnoofSMBRVales | Maximum no. of SLICE MAXIMUM BIT RATE values for a UE. Value is 8. | + +### 9.3.1.272 Multicast MBS Session List + +This IE indicates the Multicast MBS Sessions the UE has joined. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------|----------|-----------------------------|-----------------------|-----------------------| +| Multicast MBS Session Item | | 1.. | | | +| >MBS Session ID | M | | 9.3.1.218 | | + +| Range bound | Explanation | +|-------------|-------------| +|-------------|-------------| + +| | | +|-------------------------------|-------------------------------------------------------------------| +| maxnoofMBSSessionsofUE | Maximum no. of MBS sessions allowed towards one UE. Value is 256. | +|-------------------------------|-------------------------------------------------------------------| + +### 9.3.1.273 TAI NSAG Support List + +This IE indicates the list of NSAGs configured at the gNB-DU and their associated S-NSSAIs as defined in TS 23.501 [21]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------|----------|-------------------|---------------------------------------|--------------------------------------------------------| +| NSAG Support Item | | 1.. | | | +| >NSAG ID | M | | INTEGER (0.. 255, ...) | | +| >NSAG Slice Support List | M | | Extended Slice Support List 9.3.1.165 | Indicates the list of slices which belong to the NSAG. | + +| Range bound | Explanation | +|--------------|-----------------------------------------------| +| maxnoofNSAGs | Maximum no. of signalled NSAGs. Value is 256. | + +### 9.3.1.274 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.14 | | + +| Range bound | Explanation | +|-----------------|---------------------------------------------------------| +| maxnoofMDTPLMNs | Maximum no. of PLMNs in the MDT PLMN list. Value is 16. | + +### 9.3.1.275 MRB RLC Configuration + +This ID provides MRB RLC Configuration Information and is provided by the gNB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MRB RLC Configuration | M | | ENUMERATED ( rlc-um-ptp, rlc-am-ptp, rlc-um-dl-ptm, two-rlc-um-dl-ptp-and-dl-ptm, three-rlc-um-dl-ptp-ul-ptp-dl-ptm, two-rlc-am-ptp-um-dl-ptm, ...) | The various codepoints correspond to MRB configurations specified in TS 38.300 [6] as follows:
"rlc-um-ptp " : Multicast MRB with DL only RLC-UM or bidirectional RLC-UM configuration for PTP transmission;
"rlc-am-ptp " : Multicast MRB with RLC-AM entity configuration for PTP transmission;
" rlc-um-dl-ptm " : Multicast MRB | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | with DL only RLC-UM entity for PTM transmission;
"two-rlc-um-dl-ptp-and-dl-ptm": Multicast MRB with two RLC-UM entities, one DL only RLC-UM entity for PTP transmission and the other DL only RLC-UM entity for PTM transmission;
"three-rlc-um-dl-ptp-ul-ptp-dl-ptm": Multicast MRB with three RLC-UM entities, one DL RLC-UM entity and one UL RLC-UM entity for PTP transmission and the other DL only RLC-UM entity for PTM transmission;
"two-rlc-am-ptp-um-dl-ptm": Multicast MRB with two RLC entities, one RLC-AM entity for PTP transmission and the other DL only RLC-UM entity for PTM transmission; | + +### 9.3.1.276 Timing Error Margin + +This information element contains the Timing error margin for the TRP Rx TEG, or TRP Tx TEG. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------|----------|-------|-----------------------------------------------------------------------------------------------------------|-----------------------| +| Timing Error Margin | M | | ENUMERATED(Tc0, Tc2, Tc4, Tc6, Tc8, Tc12, Tc16, Tc20, Tc24, Tc32, Tc40, Tc48, Tc56, Tc64, Tc72, Tc80,...) | | + +### 9.3.1.277 SDT Bearer Configuration Info + +This IE contains RLC bearer configuration of each SDT bearer. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|-----------------------------|-----------------------|-----------------------------------------------------------------------| +| SDT Bearer Config List | | 1 | | | +| >SDT Bearer Config Item IEs | | 1 ..
| | | +| >>CHOICE SDT Bearer Type | M | | | | +| >>>SRB | | | | | +| >>>>SRB ID | M | | 9.3.1.7 | | +| >>>DRB | | | | | +| >>>>DRB ID | M | | 9.3.1.8 | | +| >>SDT RLC Bearer Configuration | M | | OCTET STRING | Includes the RLC-BearerConfig IE defined in subclause 6.3.2 of | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| | | | | TS 38.331 [8] | + +| Range bound | Explanation | +|-------------------|---------------------------------------------------------------------------------------------------| +| maxnoofSDTBearers | Maximum no. of SDT bearers. Value is the summation of maximum numbers of DRBs and SRBs, i.e., 72. | + +### 9.3.1.278 PosSIType List + +This IE is used to indicate the list of positioning SI message to be broadcast. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------|----------|----------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PosSI type item IEs | | 1..
| | | +| >PosSI Type | M | | INTEGER (1..32, ...) | Value "1" corresponds to the positioning SI message identified by the first SI message indicated in the posSI-SchedulingInfo IE in the SIB1 message, value "2" to the positioning SI message identified by the second SI message indicated in the posSI-SchedulingInfo IE in the SIB1 message, and so on, as defined in TS 38.331 [8]. | + +| Range bound | Explanation | +|-------------------|---------------------------------------------------------------| +| maxnoofPosSITypes | Maximum no. of positioning SI types, the maximum value is 32. | + +### 9.3.1.279 IAB-DU Cell Resource Configuration-Mode-Info + +This IE contains the IAB-DU Cell Resource Configuration-Mode-Info. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------------------------|----------|-------|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE IAB-DU Cell Resource Configuration-Mode-Info | M | | | | - | | +| >FDD | | | | | | | +| >>FDD Info | | 1 | | | - | | +| >>>gNB-DU Cell Resource Configuration-FDD-UL | M | | gNB-DU Cell Resource Configuration 9.3.1.107 | Contains FDD UL resource configuration of the gNB-DU cell. Only applicable if the gNB-DU is an IAB-DU or an IAB-donor-DU. | - | | +| >>>gNB-DU Cell Resource | M | | gNB-DU Cell Resource | Contains FDD DL resource | - | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|-------|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Configuration-FDD-DL | | | Configuration 9.3.1.107 | configuration of the gNB-DU cell. Only applicable if the gNB-DU is an IAB-DU or an IAB-donor-DU. | | | +| >>>UL Frequency Info | O | | NR Frequency Info 9.3.1.17 | | YES | reject | +| >>>UL Transmission Bandwidth | O | | Transmission Bandwidth 9.3.1.15 | | YES | reject | +| >>>UL Carrier List | O | | NR Carrier List 9.3.1.137 | If included, the UL Transmission Bandwidth IE shall be ignored. | YES | reject | +| >>>DL Frequency Info | O | | NR Frequency Info 9.3.1.17 | | YES | reject | +| >>>DL Transmission Bandwidth | O | | Transmission Bandwidth 9.3.1.15 | | YES | reject | +| >>>DL Carrier List | O | | NR Carrier List 9.3.1.137 | If included, the UL Transmission Bandwidth IE shall be ignored. | YES | reject | +| >TDD | | | | | | | +| >>TDD Info | | 1 | | | - | | +| >>>gNB-DU Cell Resource Configuration-TDD | M | | gNB-DU Cell Resource Configuration 9.3.1.107 | Contains TDD resource configuration of the gNB-DU cell. Only applicable if the gNB-DU is an IAB-DU or an IAB-donor-DU. | - | | +| >>>NR Frequency Info | O | | NR Frequency Info 9.3.1.17 | | YES | reject | +| >>>Transmission Bandwidth | O | | Transmission Bandwidth 9.3.1.15 | | YES | reject | +| >>>Carrier List | O | | NR Carrier List 9.3.1.137 | If included, the Transmission Bandwidth IE shall be ignored. | YES | reject | + +### 9.3.1.280 TRP Rx TEG Information + +This information element contains the TRP Rx TEG information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| TRP Rx TEG ID | M | | INTEGER (0..31) | | + +| | | | | | +|----------------------------|---|--|-------------------------------|------------------------------------------------------| +| TRP Rx Timing Error Margin | M | | Timing Error Margin 9.3.1.276 | Timing error margin associated to the TRP Rx TEG ID. | +|----------------------------|---|--|-------------------------------|------------------------------------------------------| + +### 9.3.1.281 TRP Tx TEG Information + +This information element contains the TRP Tx TEG information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------|----------|-------|-------------------------------|------------------------------------------------------| +| TRP Tx TEG ID | M | | INTEGER (0..7) | | +| TRP Tx Timing Error Margin | M | | Timing Error Margin 9.3.1.276 | Timing error margin associated to the TRP Tx TEG ID. | + +### 9.3.1.282 TRP RxTx TEG Information + +This information element contains the TRP RxTx TEG information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|-------|------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------| +| TRP RxTx TEG ID | M | | INTEGER (0..255) | | +| TRP RxTx Timing Error Margin | M | | ENUMERATED(Tc0 dot5, Tc1, Tc2, Tc4, Tc8, Tc12, Tc16, Tc20, Tc24, Tc32, Tc40, Tc48, Tc64, Tc80, Tc96, Tc128, ...) | Timing error margin associated to the TRP RxTx TEG ID. | + +### 9.3.1.283 Uplink TxDirectCurrentTwoCarrierList Information + +This IE contains the Uplink TxDirectCurrentTwoCarrierList information that is configured by the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------| +| Uplink TxDirectCurrentTwoCarrierList Information | M | | OCTET STRING | Includes the UplinkTxDirectCurrentTwoCarrierList IE as defined in TS 38.331 [8]. | + +### 9.3.1.284 Uplink TxDirectCurrentMoreCarrierList Information + +This IE contains the Uplink TxDirectCurrentMoreCarrierList information that is configured by the UE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------| +| Uplink TxDirectCurrentMoreCarrierList Information | M | | OCTET STRING | Includes the UplinkTxDirectCurrentMoreCarrierList IE as defined in TS 38.331 [8]. | + +### 9.3.1.285 Extended UE Identity Index Value + +This IE is used by the gNB-DU to calculate the Paging Frame and Paging Occasion for eDRX, and the UE\_ID based subgroup ID as specified in TS 38.304 [24]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------|----------|-------|-----------------------|-----------------------| +| Extended UE Identity Index Value | M | | BIT STRING (SIZE(16)) | | + +### 9.3.1.286 Hashed UE Identity Index Value + +This IE is the 13 Most Significant Bits (MSBs) of the Hashed ID defined in TS 38.304 [24]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|----------|-------|----------------------------|-----------------------| +| Hashed UE Identity Index Value | M | | BIT STRING (SIZE(13, ...)) | | + +### 9.3.1.287 Broadcast Area Scope + +This IE contains the Broadcast Area where the broadcast session is delivered. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------|----------|------------------------------------|-----------------------|----------------------------------------------------------------------------| +| CHOICE
BroadcastAreaScope | M | | | | +| > CompleteSuccess | | | NULL | | +| > PartialSuccess | | | | | +| >> Broadcast Cell List | | 1 | | | +| >>> Broadcast Cell Item | | 1 ..
< maxcellingNB DU > | | | +| >>>>Cell ID | M | | NR CGI
9.3.1.12 | Identifier of the cells that establish the broadcast service successfully. | + +| Range bound | Explanation | +|------------------------|-------------------------------------------------------------------------------------------------| +| maxcellingNB DU | Maximum no. of cells which establish the MRBs successfully in one DU, the maximum value is 512. | + +### 9.3.1.288 Network Controlled Repeater Authorized + +This IE provides the authorization status of the Network Controlled Repeater. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------|----------|-------|----------------------------------------------|-----------------------| +| Network Controlled Repeater Authorized | M | | ENUMERATED (authorized, not authorized, ...) | | + +### 9.3.1.289 MT-SDT Information + +This IE indicates MT-SDT information. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------|----------|-------|---------------------------|-----------------------| +| MT-SDT Indicator | M | | ENUMERATED
(true, ...) | | + +### 9.3.1.290 Supported UE Type List + +This IE indicates the supported UE Type list for MBS session. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------|----------|--------------------------|--------------------------------------------------|-----------------------| +| Supported UE Type List Item IEs | | 1..<
maxnoofUETypes > | | | +| >Supported UE type | M | | ENUMERATED
(Non-RedCap-UE,
RedCap-UE, ...) | | + +| Range bound | Explanation | +|----------------|-------------------------------------------------| +| maxnoofUETypes | Maximum no. of associated UE types. Value is 8. | + +### 9.3.1.291 LTM Cells To Be Released List + +This IE indicates a list of LTM cells to be released. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------|----------|-----------------------------------|-----------------------|-----------------------|-------------|----------------------| +| LTM Cells To Be Released Item IEs | | 1 ..
LTMCells
> | | | EACH | ignore | +| >LTM Cell ID | M | | NR CGI
9.3.1.12 | | - | | + +| Condition | Explanation | +|-----------------|-----------------------------------------------------------------------------------------| +| maxnoofLTMCells | Maximum no. of Cells configured for LTM allowed towards one UE, the maximum value is 8. | + +### 9.3.1.292 Reference Configuration + +This IE contains the reference configuration used for LTM. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------|----------|-------|---------------------------|----------------------------------------------------------------------| +| CHOICE Reference Configuration | M | | | | +| >Request for Lower Layer Configuration | | | ENUMERATED
(true, ...) | | +| >LTM Reference Configuration | | | OCTET STRING | Includes the CellGroupConfig IE, as defined in TS 38.331 [8]. | + +### 9.3.1.293 TCI States Configurations List + +This IE indicates the list of TCI states configurations. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------------|----------|--------------------------------|-----------------------|----------------------------------------------------------------------------------| +| Joint or DL TCI States Configurations List | | 0..1 | | | +| >Joint or DL TCI States Configurations Item IEs | | 1.. | | | +| >>Joint or DL TCI State | M | | OCTET STRING | Includes the CandidateTCI-States as defined in 6.3.2 of TS 38.331 [8]. | +| UL TCI States Configurations List | | 0..1 | | | +| >UL TCI States Configurations Item IEs | | 1.. | | | +| >>UL TCI State | M | | OCTET STRING | Includes the CandidateTCI-UL-States as defined in 6.3.2 of TS 38.331 [8]. | + +| Range bound | Explanation | +|---------------------------|---------------------------------------------------------------------| +| maxnoofJointorDLTCIStates | Maximum no. of Joint or DL TCI States Configurations. Value is 128. | +| maxnoofULTCIStates | Maximum no. of UL TCI States Configurations. Value is 64. | + +### 9.3.1.294 LTM Configuration ID Mapping List + +This IE indicates the list of LTM cells associated with its configuration IDs. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------|----------|----------------------|-----------------------|----------------------------------------------------------------------------|-------------|----------------------| +| Configuration ID Mapping Item IEs | | 1.. | | | - | - | +| >LTM Cell ID | M | | NR CGI 9.3.1.12 | | - | | +| >LTM Configuration ID | O | | INTEGER (1..8) | Corresponds to the LTM-CandidateId IE, as defined in TS 38.331 [8]. | - | | + +| Range bound | Explanation | +|-----------------|-------------------------------------------------------------------------------------| +| maxnoofLTMCells | Maximum no. of Cells configured LTM allowed towards one UE, the maximum value is 8. | + +### 9.3.1.295 Radio Resource Status NR-U + +The *Radio Resource Status NR-U* IE indicates the usage of the PRBs per NR-U channel for all traffic in Downlink and Uplink. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------| +| DL Total PRB Usage | M | | INTEGER (0..100) | Per NR-U Channel DL Total PRB usage in percentage of the cell total PRB number. | +| UL Total PRB Usage | M | | INTEGER (0..100) | Per NR-U Channel UL Total PRB usage in percentage of the cell total PRB number. | + +### 9.3.1.296 Path Addition Information + +This IE provides information for path addition in case of MP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------|----------|-------|------------------------------|--------------------------------------------------------------------------------------------------| +| CHOICE Path Addition Information | M | | | | +| > Indirect Path Addition | | | | | +| >>Target Relay UE ID | M | | BIT STRING (SIZE(24)) | Corresponds to information provided in the SL-SourceIdentity IE, defined in TS 38.331 [8] | +| >>Remote UE Local ID | M | | 9.3.1.267 | | +| > Direct Path Addition | | | NULL | | +| > N3C Indirect Path Addition | | | | | +| >>Target Relay UE ID | M | | gNB-DU UE F1AP ID
9.3.1.5 | Corresponds to the gNB-DU UE F1AP ID IE of MP Relay UE using N3C. | + +### 9.3.1.297 Recommended SSBs for Paging List + +This IE indicates the recommended SSBs for paging list. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------|----------|----------------------------------------|-----------------------|---------------------------------------------------| +| Recommended SSBs for Paging List Item | | 0 .. < maxCellingNB DU > | | | +| >NR CGI | M | | 9.3.1.12 | | +| > SSBs for Paging List | | 1 .. < maxnoofSSBA reas > | | | +| >>SSB Index | M | | INTEGER (0..63) | Identifier of the recommended SSB beam for paging | + + + +| Range bound | Explanation | +|-----------------|------------------------------------------------------------------| +| maxCellingNB DU | Maximum no. cells that can be served by a gNB-DU. Value is 512. | +| maxnoofSSBAreas | Maximum no. SSB Areas that can be served by a cell. Value is 64. | + +### 9.3.1.298 RAN Timing Synchronisation Status Information + +This IE indicates the RAN timing synchronisation status information provided from the gNB-DU to the gNB-CU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------| +| Synchronisation State | O | | ENUMERATED
(locked, holdover, freeRun, ...) | | +| Traceable to UTC | O | | ENUMERATED
(true, false, ...) | | +| Traceable to GNSS | O | | ENUMERATED
(true, false, ...) | | +| Clock Frequency Stability | O | | BIT STRING (SIZE (16)) | Indicates the offsetScaledLogVariance as specified in TS 23.501 [21]. | +| Clock Accuracy | O | | 9.3.1.299 | | +| Parent Time Source | O | | ENUMERATED
(syncE, pTP, gNSS, atomicClock, terrestrialRadio, serialTimeCode, nTP, handSet, other, ...) | | + +### 9.3.1.299 Clock Accuracy + +This IE indicates the clock accuracy as defined in TS 23.501 [21]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------|----------|-------|----------------------------|-------------------------------------------------------------------------------------------------------------| +| CHOICE Clock Accuracy | M | | | | +| >Value | | | | | +| >>Clock Accuracy Value | M | | INTEGER (1..40000000, ...) | Indicates the absolute clock accuracy value expressed in units of 25 ns . | +| >Index | | | | | +| >>Clock Accuracy Index | M | | INTEGER (32..47, ...) | Indicates the clockAccuracy enumeration value specified in Table 5 of clause 7.6.2.6 of IEEE Std 1588 [48]. | + +### 9.3.1.300 Burst Arrival Time Window + +This IE indicates the Burst Arrival Time Window of the TSC QoS flow as defined in TS 23.501 [21]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------|----------|-------|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Earliest Burst Arrival Time | M | | INTEGER (0..640000, ...) | Start of the burst arrival time window calculated with reference to the Burst Arrival Time IE, expressed in units of 1 us. Integer values are negative. | +| Latest Burst Arrival Time | M | | INTEGER (0..640000, ...) | End of the burst arrival time window calculated with reference to the Burst Arrival Time IE, expressed in units of 1 us. Integer values are positive. | + +### 9.3.1.301 Periodicity Range + +This IE indicates the periodicity range for the TSC QoS flow as defined in TS 23.501 [21]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------|----------|---------------------------|--------------------------|-----------------------| +| CHOICE Periodicity Range | M | | | | +| > Periodicity Bound | | | | | +| >>Periodicity Lower Bound | M | | Periodicity
9.3.1.143 | | +| >>Periodicity Upper Bound | M | | Periodicity
9.3.1.143 | | +| > Periodicity List | | | | | +| >>Allowed Periodicity List | | 1.. | | | +| >>>Allowed Periodicity | M | | Periodicity
9.3.1.143 | | + +| Range bound | Explanation | +|-----------------------------|---------------------------------------------------| +| maxnoofPeriodicities | Maximum no. of allowed periodicities. Value is 8. | + +### 9.3.1.302 TSC Traffic Characteristics Feedback + +This IE provides the TSC traffic characteristics feedback of a TSC QoS flow (see TS 23.501 [21]). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------|----------|-------|---------------------------------------|-----------------------| +| TSC Feedback Information Downlink | O | | TSC Feedback Information
9.3.1.303 | | +| TSC Feedback Information Uplink | O | | TSC Feedback Information
9.3.1.303 | | + +### 9.3.1.303 TSC Feedback Information + +This IE provides the TSC feedback information for a TSC QoS flow in the uplink or downlink (see TS 23.501 [21]). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------------------|-------------------------------------------------------| +| Burst Arrival Time Offset | M | | INTEGER
(-640000..640000, ...) | Burst arrival time offset expressed in units of 1 us. | +| Adjusted Periodicity | O | | Periodicity
9.3.1.143 | Not applicable to reactive RAN feedback. | + +### 9.3.1.304 Mobile TRP Location Information + +This IE contains location information for a mobile TRP. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| | | | | | + +| | | | | | +|----------------------|---|--|--------------|--------------------------------------------------------------------------------------------------| +| Location Information | M | | OCTET STRING | Location of the mobile TRP, includes the locationEstimate IE as defined in TS 37.355 [39] | +| Velocity Information | O | | OCTET STRING | Velocity of the mobile TRP, includes the velocityEstimate IE as defined in TS 37.355 [39] | +| Location Time Stamp | O | | 9.3.1.171 | Time stamp, indicates the time when the mobile TRP location information is generated | + +### 9.3.1.305 Global gNB ID + +This IE is used to globally identify a gNB (see TS 38.300 [6]). + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|---------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| PLMN Identity | M | | 9.3.1.14 | | +| CHOICE gNB ID | M | | | | +| >gNB ID | | | | | +| >>gNB ID | M | | BIT STRING (SIZE(22..32)) | Equal to the leftmost bits of the NR Cell Identity IE contained in the NR CGI IE of each cell served by the gNB. | + +### 9.3.1.306 RRC Terminating IAB-Donor Related Info + +This IE contains the information related to a mobile IAB-node's RRC-terminating IAB-donor. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------|----------|-------|-------------------------|-----------------------------------------------------------------------------------| +| RRC Terminating IAB-Donor gNB-ID | M | | Global gNB ID 9.3.1.305 | The Global gNB ID of a mobile IAB-node's RRC-terminating IAB donor. | +| Mobile IAB-MT BAP Address | M | | 9.3.1.111 | The BAP address assigned to the mobile IAB-node by the RRC-terminating IAB-donor. | + +### 9.3.1.307 Mobile IAB-MT User Location Information + +This IE contains the user location information of mobile IAB-MT which is co-located with the mobile IAB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------| +| NR CGI | M | | 9.3.1.12 | The NR CGI of the serving cell of the mobile IAB-MT co-located with the mobile IAB-DU | +| TAI | O | | 9.3.1.308 | The TAI of the serving cell of the mobile IAB-MT co-located with the mobile IAB-DU | + +### 9.3.1.308 TAI + +This IE is used to uniquely identify a Tracking Area. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| PLMN Identity | M | | 9.3.1.14 | | +| 5GS TAC | M | | 9.3.1.29 | | + +### 9.3.1.309 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 [51].
The gNB-DU does not interpret the content of the Associated Session ID IE. | + +### 9.3.1.310 Multicast CU to DU RRC Information + +This IE indicates the multicast specific CU to DU RRC Information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------------|----------|--------------------------|-------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| MBS Multicast Cell List | | 0..1 | | | +| > MBS Multicast Cell Item | | 1 ..
| | | +| >>NR CGI | M | | NR CGI 9.3.1.12 | | +| >>RRC Multicast MTCH Neighbour Cell Information | O | | OCTET STRING | Includes the mtch-NeighbourCell in the MBS-SessionInfoListMulticast IE as specified in TS 38.331 [8]. | +| >>ThresholdIndex | O | | INTEGER
(0..maxnoofThresholdMBS) | Corresponds to the thresholdIndex as specified in TS 38.331 [8]. | +| >>MBS Multicast RRC_INACTIVE Reception Mode | O | | 9.3.1.318 | | +| >>MBS Multicast Configuration Request | O | | ENUMERATED
(query, ...) | | +| MBS Multicast MRB List | | 0..1 | | | +| > MBS Multicast MRB Item | | 1 ..
| | | +| >>MRB ID | M | | 9.3.1.224 | | +| >>MRB PDCP Config Broadcast | M | | OCTET STRING | Includes the MRB-PDCP-ConfigBroadcast IE, as defined in TS 38.331 [8]. | + +| Range bound | Explanation | +|----------------|------------------------------------------------------------------------------------| +| maxCellingNBDU | Maximum no. cells that can be served by a gNB-DU. Value is 512. | +| maxnoofMRBs | Maximum no. MRBs allowed to be setup for one MBS session, the maximum value is 32. | + +| | | +|---------------------|-----------------------------------------------------------| +| maxnoofThresholdMBS | Maximum no. thresholds configured in a cell. Value is 64. | +|---------------------|-----------------------------------------------------------| + +### 9.3.1.311 Multicast DU to CU RRC Information + +This IE indicates the multicast specific DU to CU RRC Information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------------|----------|------------------------------|-----------------------|-----------------------| +| MBS Multicast Cell List | | 0..1 | | | +| > MBS Multicast Cell Item | | 1 ..
BDU> | | | +| >>NR CGI | M | | NR CGI 9.3.1.12 | | +| >>MBS Multicast
Configuration Response
Information | O | | 9.3.1.312 | | +| >>MBS Multicast
Configuration Notification | O | | 9.3.1.313 | | + +| Range bound | Explanation | +|----------------|-----------------------------------------------------------------| +| maxCellingNBDU | Maximum no. cells that can be served by a gNB-DU. Value is 512. | + +### 9.3.1.312 MBS Multicast Configuration Response Information + +This IE contains information on the gNB-DU's response to the requested multicast configuration for reception RRC\_INACTIVE. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------------------------------------------|----------|-------|------------------------------------|---------------------------------------------------------------------------------------------| +| CHOICE MBS Multicast
Configuration Response
Information | O | | | | +| > MBS Multicast
Configuration available | | | | | +| >>MBS Multicast
Configuration | M | | OCTET STRING | Includes the
MBSMulticastConfiguration
message as defined in TS
38.331 [8]. | +| > MBS Multicast
Configuration not
available | | | | | +| >>MBS Multicast
Configuration not
available | M | | ENUMERATED (not
available, ...) | | + +### 9.3.1.313 MBS Multicast Configuration Notification + +This IE contains information on the gNB-DU's notification of MBS Multicast Configuration information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE MBS Multicast
Configuration Notification
Information | O | | | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------| +| >MBS Multicast Configuration changed | | | OCTET STRING | Includes the MBSMulticastConfiguration message as defined in TS 38.331 [8]. | +| >MBS Multicast Configuration removed | | | NULL | | + +### 9.3.1.314 Multicast CU to DU Common RRC Information + +This IE includes multicast specific CU to DU common RRC information. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------------------------------|----------|-----------------------|----------------------------------------------------------------|-----------------------| +| Multicast Common CU2DU Cell List | | 0..1 | | | +| >Multicast COMMON CU2DU Cell Item | | 1 .. | | | +| >>NR CGI | M | | NR CGI 9.3.1.12 | | +| >>CHOICE Multicast Common CU2DU Cell Information | M | | | | +| >>>Common CU2DU Cell Info Setup or Update | | | | | +| >>>>CHOICE MBS Multicast Neighbour Cell List Item | O | | | | +| >>>>>MBS Multicast Neighbour Cell List Information provided | | | Update MBS Multicast Neighbour Cell List Information 9.3.1.315 | | +| >>>>>No MBS Multicast Neighbour Cell List provided | | | NULL | | +| >>>>CHOICE ThresholdMBS-List Item | O | | | | +| >>>>>ThresholdMBS-List Information provided | | | Update ThresholdMBS-List Information 9.3.1.316 | | +| >>>>>No ThresholdMBS-List provided | | | NULL | | +| >>>No CU2DU Cell info Provided | | | NULL | | + +| Range bound | Explanation | +|----------------|-----------------------------------------------------------------| +| maxCellingNBDU | Maximum no. cells that can be served by a gNB-DU. Value is 512. | + +### 9.3.1.315 Update MBS Multicast Neighbour Cell List Information + +This IE includes MBS multicast neighbour cell related information provided in the multicast MCCH. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------------------|----------|-------------------------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------| +| MBS-NeighbourCellList | O | | OCTET STRING | Includes mbs-NeighbourCellList-r18 as defined in TS 38.331[8] | +| MTCH-NeighbourCell Session List | | 0..1 | | | +| >MTCH-NeighbourCell Session Item | | 1 ..
| | | +| >>MBS Session ID | M | | 9.3.1.218 | | +| >>CHOICE MTCH-NeighbourCell Information | M | | | | +| >>> MTCH-NeighbourCell provided | | | OCTET STRING | Includes the mtch-NeighbourCell-r18 in the MBS-SessionInfoListMulticast IE as specified in TS 38.331 [8]. | +| >>> MTCH-NeighbourCell not provided | | | NULL | Indicates that the the thresholdIndex as defined in TS 38.331 [8] is not provided for the respective multicast MBS session. | + +| Range bound | Explanation | +|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------| +| maxMBSSessionsinSessionInfoList | Maximum no. multicast MBS sessions contained in the MBS-SessionInfoListMulticast IE as specified in TS 38.331 [8]. Value is 1024. | + +### 9.3.1.316 Update ThresholdMBS-List Information + +This IE includes threshold MBS related list information provided in the multicast MCCH. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------|----------|-------------------------------------------|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| ThresholdMBS List | O | | OCTET STRING | Includes thresholdMBS-List as specified in TS 38.331[8] | +| ThresholdIndex Session List | | 0..1 | | | +| >ThresholdIndex Session Item | | 1 ..
| | | +| >>MBS Session ID | M | | 9.3.1.218 | | +| >>CHOICE ThresholdIndex Information | M | | | | +| >>> ThresholdIndex | | | INTEGER
(0..maxnoofThresholdMBS) | Corresponds to the thresholdIndex as specified in TS 38.331 [8]. | +| >>> ThresholdIndex not provided | | | NULL | Indicates that the the thresholdIndex as defined in TS 38.331 [8] is not provided for the respective multicast MBS session. | + +| Range bound | Explanation | +|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------| +| maxMBSSessionsinSessionInfoList | Maximum no. multicast MBS sessions contained in the MBS-SessionInfoListMulticast IE as specified in TS 38.331 [8]. Value is 1024. | +| maxnoofThresholdMBS | Maximum no. thresholds configured in a cell. Value is 64. | + +### 9.3.1.317 MBS Multicast Session Reception State + +This IE indicates the reception state of MBS Multicast Session. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|-------|----------------------------------------------------------------------|-----------------------| +| MBS Multicast Session Reception State | M | | ENUMERATED
(start monitoring G-RNTI, stop monitoring G-RNTI, ...) | | + +### 9.3.1.318 Multicast RRC\_INACTIVE Reception Mode + +This IE indicates the activation or deactivation of the multicast RRC\_INACTIVE reception mode for a multicast MBS session in a particular cell. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------|----------|-------|---------------------------------------------|-----------------------| +| Multicast RRC_INACTIVE Reception Mode | M | | ENUMERATED
(activated, deactivated, ...) | | + +### 9.3.1.319 PDU Set QoS Parameters + +This IE defines the 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.145 | PDU Set Delay Budget as defined in TS 23.501 [21]. | +| PDU Set Error Rate | O | | Packet Error Rate
9.3.1.52 | PDU Set Error Rate as defined in TS 23.501 [21]. | +| PDU Set Integrated Handling Information | O | | ENUMERATED(true, false, ...) | PDU Set Integrated Handling Information as defined in TS 23.501 [21]. | + +### 9.3.1.320 N6 Jitter Information + +This IE indicates the N6 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 | Indicates the lower bound of the | + +| | | | | | +|-----------------------|---|--|------------------------|-----------------------------------------------------------------| +| | | | (-127..127) | N6 jitter. The unit is: 0.5ms. | +| N6 Jitter Upper Bound | M | | INTEGER
(-127..127) | Indicates the upper bound of the N6 jitter. The unit is: 0.5ms. | + +### 9.3.1.321 ECN Marking or Congestion Information Reporting Request + +This IE indicates to the gNB-DU to report information for ECN marking or congestion for a DRB. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------------------------------------------|----------|-------|--------------------------------------|-----------------------| +| CHOICE ECN Marking or Congestion Information Request | M | | | | +| >ECN Marking | | | | | +| >>ECN Marking Request | M | | ENUMERATED (ul, dl, both, stop, ...) | | +| >Congestion Information | | | | | +| >>Congestion Information Request | M | | ENUMERATED (ul, dl, both, stop, ...) | | + +### 9.3.1.322 ECN Marking or Congestion Information Reporting Status + +This IE indicates the status of information reporting for ECN marking or congestion information reporting for a DRB. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------------------|----------|-------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------| +| ECN Marking or Congestion Information Reporting Status | O | | ENUMERATED (active, not active, ...) | Indicates whether information reporting for ECN marking or congestion information reporting is active or not active. | + +### 9.3.1.323 NR A2X Services Authorized + +This IE provides information on the authorization status of the UE to use the NR sidelink for A2X services. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|----------------------------------------------|----------------------------------------------------------| +| Aerial UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized as Aerial UE. | +| Controller UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized as Controller UE. | + +### 9.3.1.324 LTE A2X Services Authorized + +This IE provides information on the authorization status of the UE to use the LTE sidelink for A2X services. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|----------------------------------------------|------------------------------------------------------| +| Aerial UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized as Aerial UE. | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|----------------------------------------------|----------------------------------------------------------| +| Controller UE | O | | ENUMERATED (authorized, not authorized, ...) | Indicates whether the UE is authorized as Controller UE. | + +### 9.3.1.3.25 NR Paging Long eDRX Information + +This IE indicates the NR Paging long eDRX parameters for RRC INACTIVE as defined in TS 38.304 [24]. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------|----------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------| +| NR Paging Long eDRX Cycle for RRC INACTIVE | M | | ENUMERATED (hf2, hf4, hf8, hf16, hf32, hf64, hf128, hf256, hf512, hf1024, ...) | $T_{\text{long-eDRX,RAN}}$ defined in TS 38.304 [24]. Unit: [number of hyperframes]. | +| NR Paging Time Window for RRC INACTIVE | M | | ENUMERATED (s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s11, s12, s13, s14, s15, s16, s17, s18, s19, s20, s21, s22, s23, s24, s25, s26, s27, s28, s29, s30, s31, s32, ...) | Unit: [1.28 second]. | + +## 9.3.2 Transport Network Layer Related IEs + +### 9.3.2.1 UP Transport Layer Information + +The *UP Transport Layer Information* IE identifies an F1 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 F1 user plane transport. The GTP Tunnel Endpoint Identifier is to be used for the user plane transport between gNB-CU and gNB-DU. + +| 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.3 | | +| >>GTP-TEID | M | | 9.3.2.2 | | + +### 9.3.2.2 GTP-TEID + +The *GTP-TEID* IE is the GTP Tunnel Endpoint Identifier to be used for the user plane transport between the gNB-CU and gNB-DU. + +| 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 [18]. | + +### 9.3.2.3 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 [19]. | + +### 9.3.2.4 CP Transport Layer Information + +This IE is used to provide the F1 control plane transport layer information associated with a gNB-CU – gNB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-------|---------------------------------|-----------------------|-------------|----------------------| +| CHOICE CP Transport Layer Information | | | | | - | | +| >Endpoint-IP-address | | | | | | | +| >>Endpoint IP address | M | | Transport Layer Address 9.3.2.3 | | - | | +| >Endpoint-IP-address-and-port | | | | | | | +| >>Endpoint IP address | M | | Transport Layer Address 9.3.2.3 | | - | | +| >>Port Number | M | | BIT STRING (SIZE(16)) | | YES | reject | + +### 9.3.2.5 Transport Layer Address Info + +This IE is used for signalling TNL Configuration information for IPSec tunnel over which GTP traffic is transmitted. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------|----------|---------------------|---------------------------------|-------------------------------------------------| +| Transport UP Layer Address Info to Add List | | 0..1 | | | +| >Transport UP Layer Address Info to Add Item | | 1.. | | | +| >>IP-Sec Transport Layer Address | M | | Transport Layer Address 9.3.2.3 | Transport Layer Address for IP-Sec endpoint. | +| >>GTP Transport Layer Address To Add List | | 0..1 | | | +| >>>GTP Transport Layer Address To Add Item | | 1.. | | | +| >>>>GTP Transport Layer Address Info | M | | Transport Layer Address 9.3.2.3 | GTP Transport Layer Address for GTP end-points. | +| Transport UP Layer | | 0..1 | | | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------------------------------|----------|---------------------|------------------------------------|-------------------------------------------------| +| Address Info to Remove List | | | | | +| > Transport UP Layer Address Info to Remove Item | | 1.. | | | +| >>IP-Sec Transport Layer Address | M | | Transport Layer Address
9.3.2.3 | Transport Layer Address for IP-Sec endpoint. | +| >> GTP Transport Layer Address To Remove List | | 0..1 | | | +| >>> GTP Transport Layer Address To Remove Item | | 1.. | | | +| >>>>GTP Transport Layer Address Info | M | | Transport Layer Address
9.3.2.3 | GTP Transport Layer Address for GTP end-points. | + +| Range bound | Explanation | +|----------------|------------------------------------------------------------------------------------------------| +| maxnoofTLAs | Maximum no. of F1 Transport Layer Address in the message. Value is 16. | +| maxnoofGTPTLAs | Maximum no. of F1 GTP Transport Layer Address for a GTP end-point in the message. Value is 16. | + +### 9.3.2.6 URI + +This IE is an URI. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-------------------------------------------------------| +| URI | M | | VisibleString | String representing URI (Uniform Resource Identifier) | + +### 9.3.2.7 BC Bearer Context F1-U TNL Info + +This IE contains F1-U TNL information for an MBS Session. In case of location dependent MBS sessions, it also contains 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 | M | | UP Transport Layer Information
9.3.2.1 | | +| > location dependent | | | | | +| >> Location dependent MBS F1-U Information | | 1.. | | | +| >>>MBS Area Session ID | M | | 9.3.1.221 | | +| >>>MBS F1-U | M | | UP Transport Layer | | + +| | | | | | +|-------------|--|--|------------------------|--| +| Information | | | Information
9.3.2.1 | | +|-------------|--|--|------------------------|--| + +| Range bound | Explanation | +|--------------------------|----------------------------------------------------| +| maxnoofMBSAreaSessionIDs | Maximum no. of MBS Area Session IDs. Value is 256. | + +### 9.3.2.8 MBS Multicast F1-U Context Descriptor + +This IE contains a reference to a Multicast F1-U Context, information about the usage of the MBS Multicast F1-U Context and may contain an MBS Area Session ID. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-------------------------------------|----------|-------|----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Multicast F1-U Context Reference F1 | M | | 9.3.2.11 | | +| 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.221 | | + +### 9.3.2.9 Void + +Void + +### 9.3.2.10 MBS PTP Retransmission Tunnel Required + +This IE indicates the request to establishment of a PTP Retransmission F1-U Tunnel for retransmitting user data for a multicast MBS Session. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------|----------|-------|---------------------------|-----------------------| +| MBS PTP Retransmission Tunnel Required | M | | ENUMERATED
(true, ...) | | + +### 9.3.2.11 Multicast F1-U Context Reference F1 + +This IE contains a reference to a Multicast F1-U Context associated with an MBS Session context in a gNB-DU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------------------------|----------|-------|------------------------|----------------------------------------------------------------------------------------------------------------------| +| Multicast F1-U Bearer Context Reference | M | | OCTET STRING (SIZE(4)) | This value is allocated to uniquely denote an Multicast F1-U Context within an MBS-associated logical F1-connection. | + +### 9.3.2.12 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 | M | | | | +| >12bits | | | | | +| >>PDCP SN Length 12 | M | | INTEGER (0..4095) | | +| >18bits | | | | | +| >>PDCP SN Length 18 | M | | INTEGER (0..262143) | | + +### 9.3.2.13 Multicast F1-U Context Reference CU + +This IE contains a reference to a Multicast F1-U Context associated with MBS session resources allocated in the gNB-CU. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------------------|----------|-------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Multicast F1-U Bearer Context Reference CU | M | | OCTET STRING (SIZE(4)) | This value is allocated to uniquely denote a Multicast F1-U Context associated with multicast MBS session resources allocated in the gNB-CU.
NOTE: If E1 is deployed, the Multicast F1-U Bearer Context Reference CU IE refers to the Multicast F1-U Context ReferenceE1 IE as specified in TS 37.483 [47]. | + +## 9.4 Message and Information Element Abstract Syntax (with ASN.1) + +### 9.4.1 General + +FIAP ASN.1 definition conforms to ITU-T Recommendation X.691 [5], ITU-T Recommendation X.680 [12] and ITU-T Recommendation X.681 [13]. + +The ASN.1 definition specifies the structure and content of FIAP messages. FIAP 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 FIAP 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 FIAP 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 + +-- + +-- \*\*\*\*\* + +FlAP-PDU-Descriptions { + +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + +ngran-access (22) modules (3) flap (3) version1 (1) flap-PDU-Descriptions (0)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- \*\*\*\*\* + +-- + +-- IE parameter types from other modules. + +-- + +-- \*\*\*\*\* + +IMPORTS + +Criticality, + +ProcedureCode + +FROM F1AP-CommonDataTypes + +Reset, + +ResetAcknowledge, + +F1SetupRequest, + +F1SetupResponse, + +F1SetupFailure, + +GNBDUConfigurationUpdate, + +GNBDUConfigurationUpdateAcknowledge, + +GNBDUConfigurationUpdateFailure, + +GNBCUConfigurationUpdate, + +GNBCUConfigurationUpdateAcknowledge, + +GNBCUConfigurationUpdateFailure, + +UEContextSetupRequest, + +UEContextSetupResponse, + +UEContextSetupFailure, + +UEContextReleaseCommand, + +UEContextReleaseComplete, + +UEContextModificationRequest, + +UEContextModificationResponse, + +UEContextModificationFailure, + +UEContextModificationRequired, + +UEContextModificationConfirm, + +ErrorIndication, +UEContextReleaseRequest, +DLRRMessageTransfer, +ULRRMessageTransfer, +GNBDUResourceCoordinationRequest, +GNBDUResourceCoordinationResponse, +PrivateMessage, +UEInactivityNotification, +InitialULRRMessageTransfer, +SystemInformationDeliveryCommand, +Paging, +Notify, +WriteReplaceWarningRequest, +WriteReplaceWarningResponse, +PWSCancelRequest, +PWSCancelResponse, +PWSRestartIndication, +PWSFailureIndication, +GNBDUStatusIndication, +RRDeliveryReport, +UEContextModificationRefuse, +F1RemovalRequest, +F1RemovalResponse, +F1RemovalFailure, + +NetworkAccessRateReduction, +TraceStart, +DeactivateTrace, +DUCURadioInformationTransfer, +CUDURadioInformationTransfer, +BAPMappingConfiguration, +BAPMappingConfigurationAcknowledge, +BAPMappingConfigurationFailure, +GNBDUResourceConfiguration, +GNBDUResourceConfigurationAcknowledge, +GNBDUResourceConfigurationFailure, +IABTNLAddressRequest, +IABTNLAddressResponse, +IABTNLAddressFailure, +IABUPConfigurationUpdateRequest, +IABUPConfigurationUpdateResponse, +IABUPConfigurationUpdateFailure, +ResourceStatusRequest, +ResourceStatusResponse, +ResourceStatusFailure, +ResourceStatusUpdate, +AccessAndMobilityIndication, +ReferenceTimeInformationReportingControl, +ReferenceTimeInformationReport, + +AccessSuccess, +CellTrafficTrace, +PositioningMeasurementRequest, +PositioningMeasurementResponse, +PositioningMeasurementFailure, +PositioningAssistanceInformationControl, +PositioningAssistanceInformationFeedback, +PositioningMeasurementReport, +PositioningMeasurementAbort, +PositioningMeasurementFailureIndication, +PositioningMeasurementUpdate, +TRPInformationRequest, +TRPInformationResponse, +TRPInformationFailure, +PositioningInformationRequest, +PositioningInformationResponse, +PositioningInformationFailure, +PositioningActivationRequest, +PositioningActivationResponse, +PositioningActivationFailure, +PositioningDeactivation, +PositioningInformationUpdate, +E-CIDMeasurementInitiationRequest, +E-CIDMeasurementInitiationResponse, + +E-CIDMeasurementInitiationFailure, +E-CIDMeasurementFailureIndication, +E-CIDMeasurementReport, +E-CIDMeasurementTerminationCommand, +BroadcastContextSetupRequest, +BroadcastContextSetupResponse, +BroadcastContextSetupFailure, +BroadcastContextReleaseCommand, +BroadcastContextReleaseComplete, +BroadcastContextReleaseRequest, +BroadcastContextModificationRequest, +BroadcastContextModificationResponse, +BroadcastContextModificationFailure, +MulticastGroupPaging, +MulticastContextSetupRequest, +MulticastContextSetupResponse, +MulticastContextSetupFailure, +MulticastContextReleaseCommand, +MulticastContextReleaseComplete, +MulticastContextReleaseRequest, +MulticastContextModificationRequest, +MulticastContextModificationResponse, +MulticastContextModificationFailure, +MulticastDistributionSetupRequest, + +MulticastDistributionSetupResponse, +MulticastDistributionSetupFailure, +MulticastDistributionReleaseCommand, +MulticastDistributionReleaseComplete, +PDMeasurementInitiationRequest, +PDMeasurementInitiationResponse, +PDMeasurementInitiationFailure, +PDMeasurementReport, +PDMeasurementTerminationCommand, +PDMeasurementFailureIndication, +PRSConfigurationRequest, +PRSConfigurationResponse, +PRSConfigurationFailure, +MeasurementPreconfigurationRequired, +MeasurementPreconfigurationConfirm, +MeasurementPreconfigurationRefuse, +MeasurementActivation, +QoEInformationTransfer, +PosSystemInformationDeliveryCommand, +DUCUCellSwitchNotification, +CUDUCellSwitchNotification, +DUCUTAInformationTransfer, +CUDUTAInformationTransfer, +QoEInformationTransferControl, + +RachIndication, +TimingSynchronisationStatusRequest, +TimingSynchronisationStatusResponse, +TimingSynchronisationStatusFailure, +TimingSynchronisationStatusReport, +MIABF1SetupTriggering, +MIABF1SetupOutcomeNotification, +MulticastContextNotificationIndication, +MulticastContextNotificationConfirm, +MulticastContextNotificationRefuse, +MulticastCommonConfigurationRequest, +MulticastCommonConfigurationResponse, +MulticastCommonConfigurationRefuse, +BroadcastTransportResourceRequest + +FROM F1AP-PDU-Contents + +id-Reset, +id-F1Setup, +id-gNBDCConfigurationUpdate, +id-gNBCUConfigurationUpdate, + +id-UEContextSetup, +id-UEContextRelease, +id-UEContextModification, +id-UEContextModificationRequired, +id-ErrorIndication, +id-UEContextReleaseRequest, +id-DLRRCMessageTransfer, +id-ULRRCMessageTransfer, +id-GNBDUResourceCoordination, +id-privateMessage, +id-UEInactivityNotification, +id-InitialULRRCMessageTransfer, +id-SystemInformationDeliveryCommand, +id-Paging, +id-Notify, +id-WriteReplaceWarning, +id-PWSCancel, +id-PWSRestartIndication, +id-PWSFailureIndication, +id-GNBDUStatusIndication, +id-RRCDeliveryReport, +id-F1Removal, +id-NetworkAccessRateReduction, +id-TraceStart, + +id-DeactivateTrace, +id-DUCURadioInformationTransfer, +id-CUDURadioInformationTransfer, +id-BAPMappingConfiguration, +id-GNBDUResourceConfiguration, +id-IABTNLAddressAllocation, +id-IABUPConfigurationUpdate, +id-resourceStatusReportingInitiation, +id-resourceStatusReporting, +id-accessAndMobilityIndication, +id-ReferenceTimeInformationReportingControl, +id-ReferenceTimeInformationReport, +id-accessSuccess, +id-cellTrafficTrace, +id-PositioningMeasurementExchange, +id-PositioningAssistanceInformationControl, +id-PositioningAssistanceInformationFeedback, +id-PositioningMeasurementReport, +id-PositioningMeasurementAbort, +id-PositioningMeasurementFailureIndication, +id-PositioningMeasurementUpdate, +id-TRPInformationExchange, +id-PositioningInformationExchange, +id-PositioningActivation, + +id-PositioningDeactivation, +id-PositioningInformationUpdate, +id-E-CIDMeasurementInitiation, +id-E-CIDMeasurementFailureIndication, +id-E-CIDMeasurementReport, +id-E-CIDMeasurementTermination, +id-BroadcastContextSetup, +id-BroadcastContextRelease, +id-BroadcastContextReleaseRequest, +id-BroadcastContextModification, +id-MulticastGroupPaging, +id-MulticastContextSetup, +id-MulticastContextRelease, +id-MulticastContextReleaseRequest, +id-MulticastContextModification, +id-MulticastDistributionSetup, +id-MulticastDistributionRelease, +id-PDCMeasurementInitiation, +id-PDCMeasurementInitiationRequest, +id-PDCMeasurementInitiationResponse, +id-PDCMeasurementInitiationFailure, +id-PDCMeasurementTerminationCommand, +id-PDCMeasurementFailureIndication, +id-PDCMeasurementReport, + +id-pRSConfigurationExchange, +id-measurementPreconfiguration, +id-measurementActivation, +id-QoEInformationTransfer, +id-PosSystemInformationDeliveryCommand, +id-DUCUCellSwitchNotification, +id-CUDUCellSwitchNotification, +id-DUCUTAInformationTransfer, +id-CUDUTAInformationTransfer, +id-QoEInformationTransferControl, +id-RachIndication, +id-TimingSynchronisationStatus, +id-TimingSynchronisationStatusReport, +id-MIABF1SetupTriggering, +id-MIABF1SetupOutcomeNotification, +id-MulticastContextNotification, +id-MulticastCommonConfiguration, +id-BroadcastTransportResourceRequest + +FROM F1AP-Constants + +``` + +ProtocolIE-SingleContainer{}, +FLAP-PROTOCOL-IES + +FROM FLAP-Containers; + +-- ***** +-- +-- Interface Elementary Procedure Class +-- +-- ***** + +FLAP-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 +-- +-- ***** + +FlAP-PDU ::= CHOICE { + initiatingMessage InitiatingMessage, + successfulOutcome SuccessfulOutcome, + unsuccessfulOutcome UnsuccessfulOutcome, + choice-extension ProtocolIE-SingleContainer { { FlAP-PDU-ExtIEs } } +} + +FlAP-PDU-ExtIEs FlAP-PROTOCOL-IES ::= { -- this extension is not used + ... +} + +InitiatingMessage ::= SEQUENCE { + procedureCode FlAP-ELEMENTARY-PROCEDURE.&procedureCode ({FlAP-ELEMENTARY-PROCEDURES}), + criticality FlAP-ELEMENTARY-PROCEDURE.&criticality ({FlAP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value FlAP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({FlAP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} +``` + +``` + +} + +SuccessfulOutcome ::= SEQUENCE { + procedureCode FLAP-ELEMENTARY-PROCEDURE.&procedureCode ({FLAP-ELEMENTARY-PROCEDURES}), + criticality FLAP-ELEMENTARY-PROCEDURE.&criticality ({FLAP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value FLAP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({FLAP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +``` + +``` + +UnsuccessfulOutcome ::= SEQUENCE { + procedureCode FLAP-ELEMENTARY-PROCEDURE.&procedureCode ({FLAP-ELEMENTARY-PROCEDURES}), + criticality FLAP-ELEMENTARY-PROCEDURE.&criticality ({FLAP-ELEMENTARY-PROCEDURES}{@procedureCode}), + value FLAP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({FLAP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +``` + +``` + +-- ***** +-- +-- Interface Elementary Procedure List +-- +-- ***** + +``` + +``` + +FLAP-ELEMENTARY-PROCEDURES FLAP-ELEMENTARY-PROCEDURE ::= { + FLAP-ELEMENTARY-PROCEDURES-CLASS-1 | + FLAP-ELEMENTARY-PROCEDURES-CLASS-2, + ... +} + +``` + +} + +FLAP-ELEMENTARY-PROCEDURES-CLASS-1 FLAP-ELEMENTARY-PROCEDURE ::= { + +| | | +|-----------------------------------|--| +| reset | | +| flSetup | | +| gNBDCUConfigurationUpdate | | +| gNBCUConfigurationUpdate | | +| uEContextSetup | | +| uEContextRelease | | +| uEContextModification | | +| uEContextModificationRequired | | +| writeReplaceWarning | | +| pWSCancel | | +| gNBDCUResourceCoordination | | +| flRemoval | | +| bAPMappingConfiguration | | +| gNBDCUResourceConfiguration | | +| iABTNLAddressAllocation | | +| iABUPConfigurationUpdate | | +| resourceStatusReportingInitiation | | +| positioningMeasurementExchange | | +| tRPInformationExchange | | +| positioningInformationExchange | | + +``` + positioningActivation | + e-CIDMeasurementInitiation | + broadcastContextSetup | + broadcastContextRelease | + broadcastContextModification | + multicastContextSetup | + multicastContextRelease | + multicastContextModification | + multicastDistributionSetup | + multicastDistributionRelease | + pDCMeasurementInitiation | + pRSConfigurationExchange | + measurementPreconfiguration | + timingSynchronisationStatus | + multicastContextNotification | + multicastCommonConfiguration , + ... +} + +FIAP-ELEMENTARY-PROCEDURES-CLASS-2 FIAP-ELEMENTARY-PROCEDURE ::= { + errorIndication | + uEContextReleaseRequest | + dLRRCMessageTransfer | + uLRRCMessageTransfer | +``` + +| | | +|------------------------------------------|--| +| uEInactivityNotification | | +| privateMessage | | +| initialULRRCMessageTransfer | | +| systemInformationDelivery | | +| paging | | +| notify | | +| pWSRestartIndication | | +| pWSFailureIndication | | +| gNBDUStatusIndication | | +| rRCDeliveryReport | | +| networkAccessRateReduction | | +| traceStart | | +| deactivateTrace | | +| dUCURadioInformationTransfer | | +| cUDURadioInformationTransfer | | +| resourceStatusReporting | | +| accessAndMobilityIndication | | +| referenceTimeInformationReportingControl | | +| referenceTimeInformationReport | | +| accessSuccess | | +| cellTrafficTrace | | +| positioningAssistanceInformationControl | | +| positioningAssistanceInformationFeedback | | +| positioningMeasurementReport | | + +| | | | +|-----------------------------------------|--|--| +| positioningMeasurementAbort | | | +| positioningMeasurementFailureIndication | | | +| positioningMeasurementUpdate | | | +| positioningDeactivation | | | +| e-CIDMeasurementFailureIndication | | | +| e-CIDMeasurementReport | | | +| e-CIDMeasurementTermination | | | +| positioningInformationUpdate | | | +| multicastGroupPaging | | | +| broadcastContextReleaseRequest | | | +| multicastContextReleaseRequest | | | +| pDCMeasurementReport | | | +| pDCMeasurementTerminationCommand | | | +| pDCMeasurementFailureIndication | | | +| measurementActivation | | | +| qoEInformationTransfer | | | +| posSystemInformationDelivery | | | +| dUCUCellSwitchNotification | | | +| cUDUCellSwitchNotification | | | +| dUCUTAInformationTransfer | | | +| cUDUTAInformationTransfer | | | +| qoEInformationTransferControl | | | +| rachIndication | | | +| timingSynchronisationStatusReport | | | + +``` + mIABF1SetupTriggering | + mIABF1SetupOutcomeNotification | + broadcastTransportResourceRequest, + ... +} + +-- ***** +-- +-- Interface Elementary Procedures +-- +-- ***** + +reset FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Reset + SUCCESSFUL OUTCOME ResetAcknowledge + PROCEDURE CODE id-Reset + CRITICALITY reject +} + +f1Setup FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE F1SetupRequest + SUCCESSFUL OUTCOME F1SetupResponse + UNSUCCESSFUL OUTCOME F1SetupFailure + PROCEDURE CODE id-F1Setup + CRITICALITY reject +} +``` + +``` +} + +gNBDCUConfigurationUpdate FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE GNBDCUConfigurationUpdate + SUCCESSFUL OUTCOME GNBDCUConfigurationUpdateAcknowledge + UNSUCCESSFUL OUTCOME GNBDCUConfigurationUpdateFailure + PROCEDURE CODE id-gNBDCUConfigurationUpdate + CRITICALITY reject +} + +gNBCUConfigurationUpdate FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE GNBCUConfigurationUpdate + SUCCESSFUL OUTCOME GNBCUConfigurationUpdateAcknowledge + UNSUCCESSFUL OUTCOME GNBCUConfigurationUpdateFailure + PROCEDURE CODE id-gNBCUConfigurationUpdate + CRITICALITY reject +} + +uEContextSetup FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UEContextSetupRequest + SUCCESSFUL OUTCOME UEContextSetupResponse + UNSUCCESSFUL OUTCOME UEContextSetupFailure + PROCEDURE CODE id-UEContextSetup + CRITICALITY reject +} +``` + +``` +} + +uEContextRelease FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UEContextReleaseCommand + SUCCESSFUL OUTCOME UEContextReleaseComplete + PROCEDURE CODE id-UEContextRelease + CRITICALITY reject +} + +uEContextModification FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UEContextModificationRequest + SUCCESSFUL OUTCOME UEContextModificationResponse + UNSUCCESSFUL OUTCOME UEContextModificationFailure + PROCEDURE CODE id-UEContextModification + CRITICALITY reject +} + +uEContextModificationRequired FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UEContextModificationRequired + SUCCESSFUL OUTCOME UEContextModificationConfirm + UNSUCCESSFUL OUTCOME UEContextModificationRefuse + PROCEDURE CODE id-UEContextModificationRequired + CRITICALITY reject +} +``` + +``` +writeReplaceWarning FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE WriteReplaceWarningRequest + SUCCESSFUL OUTCOME WriteReplaceWarningResponse + PROCEDURE CODE id-WriteReplaceWarning + CRITICALITY reject +} + +pWSCancel FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PWSCancelRequest + SUCCESSFUL OUTCOME PWSCancelResponse + PROCEDURE CODE id-PWSCancel + CRITICALITY reject +} + +errorIndication FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE ErrorIndication + PROCEDURE CODE id-ErrorIndication + CRITICALITY ignore +} + +UEContextReleaseRequest FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UEContextReleaseRequest + PROCEDURE CODE id-UEContextReleaseRequest +``` + +``` + CRITICALITY ignore + } + + initialULRRCMessageTransfer FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE InitialULRRCMessageTransfer + PROCEDURE CODE id-InitialULRRCMessageTransfer + CRITICALITY ignore + } + + dLRRCMessageTransfer FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DLRRRCMessageTransfer + PROCEDURE CODE id-DLRRRCMessageTransfer + CRITICALITY ignore + } + + uLRRCMessageTransfer FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE ULRRRCMessageTransfer + PROCEDURE CODE id-ULRRRCMessageTransfer + CRITICALITY ignore + } + + uEInactivityNotification FLAP-ELEMENTARY-PROCEDURE ::= { +``` + +``` + INITIATING MESSAGE UEInactivityNotification + PROCEDURE CODE id-UEInactivityNotification + CRITICALITY ignore +} + +gNBDUResourceCoordination FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE GNBDUResourceCoordinationRequest + SUCCESSFUL OUTCOME GNBDUResourceCoordinationResponse + PROCEDURE CODE id-GNBDUResourceCoordination + CRITICALITY reject +} + +privateMessage FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PrivateMessage + PROCEDURE CODE id-privateMessage + CRITICALITY ignore +} + +systemInformationDelivery FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE SystemInformationDeliveryCommand + PROCEDURE CODE id-SystemInformationDeliveryCommand + CRITICALITY ignore +} +``` + +``` +paging FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Paging + PROCEDURE CODE id-Paging + CRITICALITY ignore +} + +notify FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Notify + PROCEDURE CODE id-Notify + CRITICALITY ignore +} + +networkAccessRateReduction FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE NetworkAccessRateReduction + PROCEDURE CODE id-NetworkAccessRateReduction + CRITICALITY ignore +} + +pWSRestartIndication FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PWSRestartIndication + PROCEDURE CODE id-PWSRestartIndication + CRITICALITY ignore +} +``` + +``` +} + +pWSFailureIndication FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PWSFailureIndication + PROCEDURE CODE id-PWSFailureIndication + CRITICALITY ignore +} + +gNBDUStatusIndication FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE GNBDSUStatusIndication + PROCEDURE CODE id-GNBDSUStatusIndication + CRITICALITY ignore +} + +rRCDeliveryReport FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RRCDeliveryReport + PROCEDURE CODE id-RRCDeliveryReport + CRITICALITY ignore +} + +f1Removal FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE F1RemovalRequest + SUCCESSFUL OUTCOME F1RemovalResponse +``` + +``` + UNSUCCESSFUL OUTCOME FlRemovalFailure + + PROCEDURE CODE id-FlRemoval + + CRITICALITY reject + +} + +traceStart FLAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE TraceStart + + PROCEDURE CODE id-TraceStart + + CRITICALITY ignore + +} + +deactivateTrace FLAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE DeactivateTrace + + PROCEDURE CODE id-DeactivateTrace + + CRITICALITY ignore + +} + +dUCURadioInformationTransfer FLAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE DUCURadioInformationTransfer + + PROCEDURE CODE id-DUCURadioInformationTransfer + + CRITICALITY ignore + +} + +cUDURadioInformationTransfer FLAP-ELEMENTARY-PROCEDURE ::= { +``` + +``` + INITIATING MESSAGE CUDURadioInformationTransfer + PROCEDURE CODE id-CUDURadioInformationTransfer + CRITICALITY ignore +} + +bAPMappingConfiguration FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE BAPMappingConfiguration + SUCCESSFUL OUTCOME BAPMappingConfigurationAcknowledge + UNSUCCESSFUL OUTCOME BAPMappingConfigurationFailure + PROCEDURE CODE id-BAPMappingConfiguration + CRITICALITY reject +} + +gNBDUResourceConfiguration FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE GNBDUResourceConfiguration + SUCCESSFUL OUTCOME GNBDUResourceConfigurationAcknowledge + UNSUCCESSFUL OUTCOME GNBDUResourceConfigurationFailure + PROCEDURE CODE id-GNBDUResourceConfiguration + CRITICALITY reject +} + +iABTNLAddressAllocation FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE IABTNLAddressRequest + SUCCESSFUL OUTCOME IABTNLAddressResponse +``` + +``` +UNSUCCESSFUL OUTCOME IABTNLAddressFailure + +PROCEDURE CODE id-IABTNLAddressAllocation + +CRITICALITY reject + +} + +iABUPConfigurationUpdate FLAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE IABUPConfigurationUpdateRequest + + SUCCESSFUL OUTCOME IABUPConfigurationUpdateResponse + + UNSUCCESSFUL OUTCOME IABUPConfigurationUpdateFailure + + PROCEDURE CODE id-IABUPConfigurationUpdate + + CRITICALITY reject + +} + +resourceStatusReportingInitiation FLAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE ResourceStatusRequest + + SUCCESSFUL OUTCOME ResourceStatusResponse + + UNSUCCESSFUL OUTCOME ResourceStatusFailure + + PROCEDURE CODE id-resourceStatusReportingInitiation + + CRITICALITY reject + +} + +resourceStatusReporting FLAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE ResourceStatusUpdate + + PROCEDURE CODE id-resourceStatusReporting +``` + +``` + CRITICALITY ignore +} + +accessAndMobilityIndication FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE AccessAndMobilityIndication + PROCEDURE CODE id-accessAndMobilityIndication + CRITICALITY ignore +} + +referenceTimeInformationReportingControl FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE ReferenceTimeInformationReportingControl + PROCEDURE CODE id-ReferenceTimeInformationReportingControl + CRITICALITY ignore +} + +referenceTimeInformationReport FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE ReferenceTimeInformationReport + PROCEDURE CODE id-ReferenceTimeInformationReport + CRITICALITY ignore +} + +accessSuccess FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE AccessSuccess + PROCEDURE CODE id-accessSuccess +``` + +``` + CRITICALITY ignore +} + +cellTrafficTrace FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CellTrafficTrace + PROCEDURE CODE id-cellTrafficTrace + CRITICALITY ignore +} + +positioningAssistanceInformationControl FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositioningAssistanceInformationControl + PROCEDURE CODE id-PositioningAssistanceInformationControl + CRITICALITY ignore +} + +positioningAssistanceInformationFeedback FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositioningAssistanceInformationFeedback + PROCEDURE CODE id-PositioningAssistanceInformationFeedback + CRITICALITY ignore +} + +positioningMeasurementExchange FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositioningMeasurementRequest + SUCCESSFUL OUTCOME PositioningMeasurementResponse +} +``` + +``` + UNSUCCESSFUL OUTCOME PositioningMeasurementFailure + PROCEDURE CODE id-PositioningMeasurementExchange + CRITICALITY reject +} + +positioningMeasurementReport FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositioningMeasurementReport + PROCEDURE CODE id-PositioningMeasurementReport + CRITICALITY ignore +} + +positioningMeasurementAbort FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositioningMeasurementAbort + PROCEDURE CODE id-PositioningMeasurementAbort + CRITICALITY ignore +} + +positioningMeasurementFailureIndication FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositioningMeasurementFailureIndication + PROCEDURE CODE id-PositioningMeasurementFailureIndication + CRITICALITY ignore +} + +positioningMeasurementUpdate FLAP-ELEMENTARY-PROCEDURE ::= { +``` + +``` + INITIATING MESSAGE PositioningMeasurementUpdate + PROCEDURE CODE id-PositioningMeasurementUpdate + CRITICALITY ignore +} +``` + +``` +trPInformationExchange FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE TRPInformationRequest + SUCCESSFUL OUTCOME TRPInformationResponse + UNSUCCESSFUL OUTCOME TRPInformationFailure + PROCEDURE CODE id-TRPInformationExchange + CRITICALITY reject +} +``` + +``` +positioningInformationExchange FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositioningInformationRequest + SUCCESSFUL OUTCOME PositioningInformationResponse + UNSUCCESSFUL OUTCOME PositioningInformationFailure + PROCEDURE CODE id-PositioningInformationExchange + CRITICALITY reject +} +``` + +``` +positioningActivation FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositioningActivationRequest +``` + +``` + SUCCESSFUL OUTCOME PositioningActivationResponse + UNSUCCESSFUL OUTCOME PositioningActivationFailure + PROCEDURE CODE id-PositioningActivation + CRITICALITY reject +} + +positioningDeactivation FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositioningDeactivation + PROCEDURE CODE id-PositioningDeactivation + CRITICALITY ignore +} + +e-CIDMeasurementInitiation FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE E-CIDMeasurementInitiationRequest + SUCCESSFUL OUTCOME E-CIDMeasurementInitiationResponse + UNSUCCESSFUL OUTCOME E-CIDMeasurementInitiationFailure + PROCEDURE CODE id-E-CIDMeasurementInitiation + CRITICALITY reject +} + +e-CIDMeasurementFailureIndication FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE E-CIDMeasurementFailureIndication + PROCEDURE CODE id-E-CIDMeasurementFailureIndication + CRITICALITY ignore +} +``` + +``` +} + +e-CIDMeasurementReport FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE E-CIDMeasurementReport + PROCEDURE CODE id-E-CIDMeasurementReport + CRITICALITY ignore +} + +e-CIDMeasurementTermination FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE E-CIDMeasurementTerminationCommand + PROCEDURE CODE id-E-CIDMeasurementTermination + CRITICALITY ignore +} + +positioningInformationUpdate FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositioningInformationUpdate + PROCEDURE CODE id-PositioningInformationUpdate + CRITICALITY ignore +} + +broadcastContextSetup FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE BroadcastContextSetupRequest + SUCCESSFUL OUTCOME BroadcastContextSetupResponse + UNSUCCESSFUL OUTCOME BroadcastContextSetupFailure +} +``` + +``` +PROCEDURE CODE id-BroadcastContextSetup +CRITICALITY reject +} + +broadcastContextRelease FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE BroadcastContextReleaseCommand + SUCCESSFUL OUTCOME BroadcastContextReleaseComplete + PROCEDURE CODE id-BroadcastContextRelease + CRITICALITY reject +} + +broadcastContextReleaseRequest FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE BroadcastContextReleaseRequest + PROCEDURE CODE id-BroadcastContextReleaseRequest + CRITICALITY reject +} + +broadcastContextModification FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE BroadcastContextModificationRequest + SUCCESSFUL OUTCOME BroadcastContextModificationResponse + UNSUCCESSFUL OUTCOME BroadcastContextModificationFailure + PROCEDURE CODE id-BroadcastContextModification + CRITICALITY reject +} +``` + +``` +multicastGroupPaging FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MulticastGroupPaging + PROCEDURE CODE id-MulticastGroupPaging + CRITICALITY ignore +} + +multicastContextSetup FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MulticastContextSetupRequest + SUCCESSFUL OUTCOME MulticastContextSetupResponse + UNSUCCESSFUL OUTCOME MulticastContextSetupFailure + PROCEDURE CODE id-MulticastContextSetup + CRITICALITY reject +} + +multicastContextRelease FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MulticastContextReleaseCommand + SUCCESSFUL OUTCOME MulticastContextReleaseComplete + PROCEDURE CODE id-MulticastContextRelease + CRITICALITY reject +} + +multicastContextReleaseRequest FLAP-ELEMENTARY-PROCEDURE ::= { +``` + +``` + INITIATING MESSAGE MulticastContextReleaseRequest + PROCEDURE CODE id-MulticastContextReleaseRequest + CRITICALITY reject +} + +multicastContextModification FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MulticastContextModificationRequest + SUCCESSFUL OUTCOME MulticastContextModificationResponse + UNSUCCESSFUL OUTCOME MulticastContextModificationFailure + PROCEDURE CODE id-MulticastContextModification + CRITICALITY reject +} + +multicastDistributionSetup FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MulticastDistributionSetupRequest + SUCCESSFUL OUTCOME MulticastDistributionSetupResponse + UNSUCCESSFUL OUTCOME MulticastDistributionSetupFailure + PROCEDURE CODE id-MulticastDistributionSetup + CRITICALITY reject +} + +multicastDistributionRelease FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MulticastDistributionReleaseCommand + SUCCESSFUL OUTCOME MulticastDistributionReleaseComplete +``` + +``` + PROCEDURE CODE id-MulticastDistributionRelease + + CRITICALITY reject + +} + +pDCMeasurementInitiation FLAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE PDCMeasurementInitiationRequest + + SUCCESSFUL OUTCOME PDCMeasurementInitiationResponse + + UNSUCCESSFUL OUTCOME PDCMeasurementInitiationFailure + + PROCEDURE CODE id-PDCMeasurementInitiation + + CRITICALITY reject + +} + +pDCMeasurementReport FLAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE PDCMeasurementReport + + PROCEDURE CODE id-PDCMeasurementReport + + CRITICALITY ignore + +} + +pDCMeasurementTerminationCommand FLAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE PDCMeasurementTerminationCommand + + PROCEDURE CODE id-PDCMeasurementTerminationCommand + + CRITICALITY ignore + +} +``` + +``` +pDCMeasurementFailureIndication FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PDCMeasurementFailureIndication + PROCEDURE CODE id-pDCMeasurementFailureIndication + CRITICALITY ignore +} +``` + +``` +pRSConfigurationExchange FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PRSConfigurationRequest + SUCCESSFUL OUTCOME PRSConfigurationResponse + UNSUCCESSFUL OUTCOME PRSConfigurationFailure + PROCEDURE CODE id-pRSConfigurationExchange + CRITICALITY reject +} +``` + +``` +measurementPreconfiguration FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MeasurementPreconfigurationRequired + SUCCESSFUL OUTCOME MeasurementPreconfigurationConfirm + UNSUCCESSFUL OUTCOME MeasurementPreconfigurationRefuse + PROCEDURE CODE id-measurementPreconfiguration + CRITICALITY reject +} +``` + +``` +measurementActivation FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MeasurementActivation + PROCEDURE CODE id-measurementActivation + CRITICALITY ignore +} + +qoEInformationTransfer FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE QoEInformationTransfer + PROCEDURE CODE id-QoEInformationTransfer + CRITICALITY ignore +} + +posSystemInformationDelivery FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PosSystemInformationDeliveryCommand + PROCEDURE CODE id-PosSystemInformationDeliveryCommand + CRITICALITY ignore +} + +dUCUCellSwitchNotification FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DUCUCellSwitchNotification + PROCEDURE CODE id-DUCUCellSwitchNotification + CRITICALITY ignore +} +``` + +``` +cUDUCellSwitchNotification FIAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CUDUCellSwitchNotification + PROCEDURE CODE id-CUDUCellSwitchNotification + CRITICALITY ignore +} + +dUCUTAInformationTransfer FIAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DUCUTAInformationTransfer + PROCEDURE CODE id-DUCUTAInformationTransfer + CRITICALITY ignore +} + +cUDUTAInformationTransfer FIAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE CUDUTAInformationTransfer + PROCEDURE CODE id-CUDUTAInformationTransfer + CRITICALITY ignore +} + +qoEInformationTransferControl FIAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE QoEInformationTransferControl + PROCEDURE CODE id-QoEInformationTransferControl + CRITICALITY ignore +} +``` + +``` +rachIndication FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE RachIndication + PROCEDURE CODE id-RachIndication + CRITICALITY ignore +} + +timingSynchronisationStatus FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE TimingSynchronisationStatusRequest + SUCCESSFUL OUTCOME TimingSynchronisationStatusResponse + UNSUCCESSFUL OUTCOME TimingSynchronisationStatusFailure + PROCEDURE CODE id-TimingSynchronisationStatus + CRITICALITY reject +} + +timingSynchronisationStatusReport FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE TimingSynchronisationStatusReport + PROCEDURE CODE id-TimingSynchronisationStatusReport + CRITICALITY ignore +} + +mIABF1SetupTriggering FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE MIABF1SetupTriggering + PROCEDURE CODE id-MIABF1SetupTriggering +} +``` + +``` + CRITICALITY ignore + +} + +mIABF1SetupOutcomeNotification FLAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE MIABF1SetupOutcomeNotification + + PROCEDURE CODE id-mIABF1SetupOutcomeNotification + + CRITICALITY ignore + +} + +multicastContextNotification FLAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE MulticastContextNotificationIndication + + SUCCESSFUL OUTCOME MulticastContextNotificationConfirm + + UNSUCCESSFUL OUTCOME MulticastContextNotificationRefuse + + PROCEDURE CODE id-MulticastContextNotification + + CRITICALITY reject + +} + +multicastCommonConfiguration FLAP-ELEMENTARY-PROCEDURE ::= { + + INITIATING MESSAGE MulticastCommonConfigurationRequest + + SUCCESSFUL OUTCOME MulticastCommonConfigurationResponse + + UNSUCCESSFUL OUTCOME MulticastCommonConfigurationRefuse + + PROCEDURE CODE id-MulticastCommonConfiguration + + CRITICALITY reject + +} +``` + +``` + +broadcastTransportResourceRequest FLAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE BroadcastTransportResourceRequest + PROCEDURE CODE id-BroadcastTransportResourceRequest + CRITICALITY reject +} + +``` + +END + +-- ASN1STOP + +### 9.4.4 PDU Definitions + +-- ASN1START + +-- \*\*\*\*\* + +-- + +-- PDU definitions for FLAP. + +-- + +-- \*\*\*\*\* + +FLAP-PDU-Contents { + +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + +ngran-access (22) modules (3) flap (3) version1 (1) flap-PDU-Contents (1) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- \*\*\*\*\* +-- +-- IE parameter types from other modules. +-- +-- \*\*\*\*\* + +IMPORTS + +AssociatedSessionID, +BroadcastMRBs-FailedToBeModified-Item, +BroadcastMRBs-FailedToBeSetup-Item, +BroadcastMRBs-FailedToBeSetupMod-Item, +BroadcastMRBs-Modified-Item, +BroadcastMRBs-Setup-Item, +BroadcastMRBs-SetupMod-Item, +BroadcastMRBs-ToBeModified-Item, +BroadcastMRBs-ToBeReleased-Item, +BroadcastMRBs-ToBeSetup-Item, +BroadcastMRBs-ToBeSetupMod-Item, +Candidate-SpCell-Item, + +Cause, +Cells-Allowed-to-be-Deactivated-List-Item, +Cells-Failed-to-be-Activated-List-Item, +Cells-Status-Item, +Cells-to-be-Activated-List-Item, +Cells-to-be-Deactivated-List-Item, +CellULConfigured, +CriticalityDiagnostics, +C-RNTI, +CUtoDURRCInformation, +DRB-Activity-Item, +DRBID, +DRBs-FailedToBeModified-Item, +DRBs-FailedToBeSetup-Item, +DRBs-FailedToBeSetupMod-Item, +DRB-Notify-Item, +DRBs-ModifiedConf-Item, +DRBs-Modified-Item, +DRBs-Required-ToBeModified-Item, +DRBs-Required-ToBeReleased-Item, +DRBs-Setup-Item, +DRBs-SetupMod-Item, +DRBs-ToBeModified-Item, +DRBs-ToBeReleased-Item, + +DRBs-ToBeSetup-Item, +DRBs-ToBeSetupMod-Item, +DRXCycle, +DRXConfigurationIndicator, +DUtoCURRCInformation, +EUTRANQoS, +ExecuteDuplication, +FullConfiguration, +GNB-CU-MBS-FlAP-ID, +GNB-CU-UE-FlAP-ID, +GNB-DU-MBS-FlAP-ID, +GNB-DU-UE-FlAP-ID, +GNB-DU-ID, +GNB-DU-Served-Cells-Item, +GNB-DU-System-Information, +GNB-CU-Name, +GNB-DU-Name, +InactivityMonitoringRequest, +InactivityMonitoringResponse, +LowerLayerPresenceStatusChange, +MBS-Area-Session-ID, +MBS-CUtoDURRCInformation, +MBSMulticastFlUContextDescriptor, +MBS-Session-ID, + +MBS-ServiceArea, +MulticastFlUContextReferenceCU, +MulticastFlUContext-ToBeSetup-Item, +MulticastFlUContext-Setup-Item, +MulticastFlUContext-FailedToBeSetup-Item, +MulticastMBSSessionList, +MulticastMRBs-ToBeSetup-Item, +MulticastMRBs-Setup-Item, +MulticastMRBs-FailedToBeSetup-Item, +MulticastMRBs-ToBeSetupMod-Item, +MulticastMRBs-ToBeModified-Item, +MulticastMRBs-ToBeReleased-Item, +MulticastMRBs-SetupMod-Item, +MulticastMRBs-FailedToBeSetupMod-Item, +MulticastMRBs-Modified-Item, +MulticastMRBs-FailedToBeModified-Item, +BroadcastAreaScope, +NetworkControlledRepeaterAuthorized, +NotificationControl, +NRCGI, +NRPCI, +UEContextNotRetrievable, +Potential-SpCell-Item, +RAT-FrequencyPriorityInformation, + +RequestedSRSTransmissionCharacteristics, +ResourceCoordinationTransferContainer, +RRCContainer, +RRCContainer-RRCSsetupComplete, +RRCReconfigurationCompleteIndicator, +SCellIndex, +SCell-ToBeRemoved-Item, +SCell-ToBeSetup-Item, +SCell-ToBeSetupMod-Item, +SCell-FailedtoSetup-Item, +SCell-FailedtoSetupMod-Item, +SDT-Volume-Threshold, +ServCellIndex, +Served-Cell-Information, +Served-Cells-To-Add-Item, +Served-Cells-To-Delete-Item, +Served-Cells-To-Modify-Item, +ServingCellMO, +SNSSAI, +SRBID, +SRBs-FailedToBeSetup-Item, +SRBs-FailedToBeSetupMod-Item, +SRBs-Required-ToBeReleased-Item, +SRBs-ToBeReleased-Item, + +SRBs-ToBeSetup-Item, +SRBs-ToBeSetupMod-Item, +SRBs-Modified-Item, +SRBs-Setup-Item, +SRBs-SetupMod-Item, +SupportedUETypeList, +TimeToWait, +TransactionID, +TransmissionActionIndicator, +UE-associatedLogicalF1-ConnectionItem, +UEIdentity-List-For-Paging-Item, +DUtoCURRCCContainer, +PagingCell-Item, +SItype-List, +UEIdentityIndexValue, +GNB-CU-TNL-Association-Setup-Item, +GNB-CU-TNL-Association-Failed-To-Setup-Item, +GNB-CU-TNL-Association-To-Add-Item, +GNB-CU-TNL-Association-To-Remove-Item, +GNB-CU-TNL-Association-To-Update-Item, +MaskedIMEISV, +PagingDRX, +PagingPriority, +PagingIdentity, + +Cells-to-be-Barred-Item, +PWSSystemInformation, +Broadcast-To-Be-Cancelled-Item, +Cells-Broadcast-Cancelled-Item, +NR-CGI-List-For-Restart-Item, +PWS-Failed-NR-CGI-Item, +RepetitionPeriod, +NumberofBroadcastRequest, +Cells-To-Be-Broadcast-Item, +Cells-Broadcast-Completed-Item, +Cancel-all-Warning-Messages-Indicator, +EUTRA-NR-CellResourceCoordinationReq-Container, +EUTRA-NR-CellResourceCoordinationReqAck-Container, +RequestType, +PLMN-Identity, +RLCFailureIndication, +UplinkTxDirectCurrentListInformation, +SULAccessIndication, +Protected-EUTRA-Resources-Item, +GNB-DUConfigurationQuery, +BitRate, +RRC-Version, +GNBDUOverloadInformation, +RRCDeliveryStatusRequest, + +NeedforGap, +RRCDeliveryStatus, +ResourceCoordinationTransferInformation, +Dedicated-SIDelivery-NeededUE-Item, +Associated-SCell-Item, +IgnoreResourceCoordinationContainer, +PagingOrigin, +UAC-Assistance-Info, +RANUEID, +GNB-DU-TNL-Association-To-Remove-Item, +NotificationInformation, +TraceActivation, +TraceID, +Neighbour-Cell-Information-Item, +SymbolAllocInSlot, +NumDLULSymbols, +AdditionalRRMPriorityIndex, +DUCURadioInformationType, +CUDURadioInformationType, +Transport-Layer-Address-Info, +BHChannels-ToBeSetup-Item, +BHChannels-Setup-Item, +BHChannels-FailedToBeSetup-Item, +BHChannels-ToBeModified-Item, + +BHChannels-ToBeReleased-Item, +BHChannels-ToBeSetupMod-Item, +BHChannels-FailedToBeModified-Item, +BHChannels-FailedToBeSetupMod-Item, +BHChannels-Modified-Item, +BHChannels-SetupMod-Item, +BHChannels-Required-ToBeReleased-Item, +BAPAddress, +BAPPathID, +BAPRoutingID, +BH-Routing-Information-Added-List-Item, +BH-Routing-Information-Removed-List-Item, +Child-Nodes-List, +Child-Nodes-List-Item, +Child-Node-Cells-List, +Child-Node-Cells-List-Item, +Activated-Cells-to-be-Updated-List, +Activated-Cells-to-be-Updated-List-Item, +UL-BH-Non-UP-Traffic-Mapping, +IABTNLAddressesRequested, +IABIPv6RequestType, +IAB-TNL-Addresses-To-Remove-Item, +IABTNLAddress, +IAB-Allocated-TNL-Address-Item, + +IABv4AddressesRequested, +TrafficMappingInfo, +UL-UP-TNL-Information-to-Update-List-Item, +UL-UP-TNL-Address-to-Update-List-Item, +DL-UP-TNL-Address-to-Update-List-Item, +NRV2XServicesAuthorized, +LTEV2XServicesAuthorized, +NRUESidelinkAggregateMaximumBitrate, +LTEUESidelinkAggregateMaximumBitrate, +SLDRBs-SetupMod-Item, +SLDRBs-ModifiedConf-Item, +SLDRBID, +SLDRBs-FailedToBeModified-Item, +SLDRBs-FailedToBeSetup-Item, +SLDRBs-FailedToBeSetupMod-Item, +SLDRBs-Modified-Item, +SLDRBs-Required-ToBeModified-Item, +SLDRBs-Required-ToBeReleased-Item, +SLDRBs-Setup-Item, +SLDRBs-ToBeModified-Item, +SLDRBs-ToBeReleased-Item, +SLDRBs-ToBeSetup-Item, +SLDRBs-ToBeSetupMod-Item, +GNBCUMeasurementID, + +GNBDUMeasurementID, +RegistrationRequest, +ReportCharacteristics, +CellToReportList, +HardwareLoadIndicator, +CellMeasurementResultList, +ReportingPeriodicity, +TNLCapacityIndicator, +RAReportList, +RLFReportInformationList, +ReportingRequestType, +TimeReferenceInformation, +ConditionalInterDUMobilityInformation, +ConditionalIntraDUMobilityInformation, +TargetCellList, +MDTPLMNList, +PrivacyIndicator, +TransportLayerAddress, +URI-address, +NID, +PosAssistance-Information, +PosBroadcast, +PositioningBroadcastCells, +RoutingID, + +PosAssistanceInformationFailureList, +PosMeasurementQuantities, +PosMeasurementResultList, +PosReportCharacteristics, +TRPInformationTypeItem, +TRPInformationItem, +LMF-MeasurementID, +RAN-MeasurementID, +SDT-Termination-Request, +SRSResourceSetID, +SpatialRelationInfo, +SRSResourceTrigger, +SRSConfiguration, +TRPList, +E-CID-MeasurementQuantities, +MeasurementPeriodicity, +E-CID-MeasurementResult, +Cell-Portion-ID, +LMF-UE-MeasurementID, +RAN-UE-MeasurementID, +RelativeTime1900, +SystemFrameNumber, +SlotNumber, +AbortTransmission, + +TRP-MeasurementRequestList, +MeasurementBeamInfoRequest, +E-CID-ReportCharacteristics, +Extended-GNB-CU-Name, +Extended-GNB-DU-Name, +FlCTransferPath, +SCGIndicator, +SpatialRelationPerSRSResource, +MeasurementPeriodicityExtended, +SuccessfulHOREportInformationList, +Coverage-Modification-Notification, +CCO-Assistance-Information, +CellsForSON-List, +IABCongestionIndication, +IABConditionalRRCMessagedeliveryIndication, +FlCTransferPathNRDC, +BufferSizeThresh, +IAB-TNL-Addresses-Exception, +BAP-Header-Rewriting-Added-List-Item, +Re-routingEnableIndicator, +NonFlterminatingTopologyIndicator, +EgressNonFlterminatingTopologyIndicator, +IngressNonFlterminatingTopologyIndicator, +Neighbour-Node-Cells-List, + +Neighbour-Node-Cells-List-Item, +NA-Resource-Configuration-List, +NA-Resource-Configuration-Item, +Serving-Cells-List, +Serving-Cells-List-Item, +RBSetConfiguration, +PDCMeasurementPeriodicity, +PDCMeasurementQuantities, +PDCMeasurementResult, +PDCReportType, +RAN-UE-PDC-MeasID, +SCGActivationRequest, +SCGActivationStatus, +TRP-MeasurementUpdateList, +PRSTRPList, +PRSTransmissionTRPList, +ResponseTime, +TRP-PRS-Info-List, +PRS-Measurement-Info-List, +PRSConfigRequestType, +MeasurementCharacteristicsRequestIndicator, +MeasurementTimeOccasion, +UEReportingInformation, +PosConextRevIndication, + +NRRedCapUEIndication, +NRPagingeDRXInformation, +NRPagingeDRXInformationforRRRCINACTIVE, +QoEInformation, +CG-SDTQueryIndication, +CG-SDTKeptIndicator, +CG-SDTSessionInfo, +SDTInformation, +FiveG-ProSeAuthorized, +UuRLCChannelToBeSetupList, +UuRLCChannelToBeModifiedList, +UuRLCChannelToBeReleasedList, +UuRLCChannelSetupList, +UuRLCChannelFailedToBeSetupList, +UuRLCChannelModifiedList, +UuRLCChannelFailedToBeModifiedList, +UuRLCChannelRequiredToBeModifiedList, +UuRLCChannelRequiredToBeReleasedList, +PC5RLCChannelToBeSetupList, +PC5RLCChannelToBeModifiedList, +PC5RLCChannelToBeReleasedList, +PC5RLCChannelSetupList, +PC5RLCChannelFailedToBeSetupList, +PC5RLCChannelFailedToBeModifiedList, + +PC5RLCChannelRequiredToBeModifiedList, +PC5RLCChannelRequiredToBeReleasedList, +PC5RLCChannelModifiedList, +RemoteUELocalID, +PathSwitchConfiguration, +SidelinkRelayConfiguration, +PagingCause, +PEIPSAssistanceInfo, +UEPagingCapability, +GNBDUUESliceMaximumBitRateList, +MDTPollutedMeasurementIndicator, +UE-MulticastMRBs-ConfirmedToBeModified-Item, +UE-MulticastMRBs-RequiredToBeModified-Item, +UE-MulticastMRBs-RequiredToBeReleased-Item, +UE-MulticastMRBs-Setup-Item, +UE-MulticastMRBs-Setupnew-Item, +UE-MulticastMRBs-ToBeReleased-Item, +UE-MulticastMRBs-ToBeSetup-Item, +UE-MulticastMRBs-ToBeSetup-atModify-Item, +PosMeasurementAmount, +BAP-Header-Rewriting-Removed-List-Item, +SLDRXCycleList, +MDTPLMNModificationList, +ActivationRequestType, + +PosMeasGapPreConfigList, +PosMeasurementPeriodicityNR-AoA, +SRSPosRRInactiveConfig, +SDTBearerConfigurationQueryIndication, +SDTBearerConfigurationInfo, +ServingCellMO-List-Item, +ServingCellMO-encoded-in-CGC-List, +PosSItypeList, +DAPS-HO-Status, +UuRLCChannelID, +UplinkTxDirectCurrentTwoCarrierListInfo, +SRSPosRRInactiveQueryIndication, +MC-PagingCell-Item, +UlTxDirectCurrentMoreCarrierInformation, +CPACMCGInformation, +ExtendedUEIdentityIndexValue, +HashedUEIdentityIndexValue, +DedicatedSIDeliveryIndication, +Configured-BWP-List, +MT-SDT-Information, +LTMInformation-Setup, +LTMConfigurationIDMappingList, LTMInformation-Modify, +LTMCells-ToBeReleased-List, LTMConfiguration, +EarlySyncInformation-Request, + +EarlySyncInformation, +EarlySyncInformation-List, +LTMLCellSwitchInformation, +TAInformation-List, +DeactivationIndication, +RAReportIndicationList, +SuccessfulPSCellChangeReportInformationList, +PathAdditionInformation, +RANTSSRequestType, +RANTimingSynchronisationStatusInfo, +GlobalGNB-ID, +Activated-Cells-Mapping-List-Item, +RRC-Terminating-IAB-Donor-Related-Info, +NCGI-to-be-Updated-List-Item, +Mobile-IAB-MTUserLocationInformation, +TAI, +IndicationMCInactiveReception, +MulticastCU2DURRCInfo, +MulticastDU2CURRCInfo, +MBSMulticastSessionReceptionState, +FlUTunnelNotEstablished, +MulticastCU2DUCommonRRCInfo, +NRA2XServicesAuthorized, +LTEA2XServicesAuthorized, + +NReRedCapUEIndication, +NRPaginglongeDRXInformationforRRRCINACTIVE, +Cells-With-SSBs-Activated-List, +Recommended-SSBs-for-Paging-List + +FROM FlAP-IEs + +PrivateIE-Container{}, +ProtocolExtensionContainer{}, +ProtocolIE-Container{}, +ProtocolIE-ContainerPair{}, +ProtocolIE-SingleContainer{}, +FlAP-PRIVATE-IEs, +FlAP-PROTOCOL-EXTENSION, +FlAP-PROTOCOL-IEs, +FlAP-PROTOCOL-IEs-PAIR + +FROM FlAP-Containers + +id-AssociatedSessionID, +id-BroadcastMRBs-FailedToBeModified-List, +id-BroadcastMRBs-FailedToBeModified-Item, +id-BroadcastMRBs-FailedToBeSetup-List, + +id-BroadcastMRBs-FailedToBeSetup-Item, +id-BroadcastMRBs-FailedToBeSetupMod-List, +id-BroadcastMRBs-FailedToBeSetupMod-Item, +id-BroadcastMRBs-Modified-List, +id-BroadcastMRBs-Modified-Item, +id-BroadcastMRBs-Setup-List, +id-BroadcastMRBs-Setup-Item, +id-BroadcastMRBs-SetupMod-List, +id-BroadcastMRBs-SetupMod-Item, +id-BroadcastMRBs-ToBeModified-List, +id-BroadcastMRBs-ToBeModified-Item, +id-BroadcastMRBs-ToBeReleased-List, +id-BroadcastMRBs-ToBeReleased-Item, +id-BroadcastMRBs-ToBeSetup-List, +id-BroadcastMRBs-ToBeSetup-Item, +id-BroadcastMRBs-ToBeSetupMod-List, +id-BroadcastMRBs-ToBeSetupMod-Item, +id-Candidate-SpCell-Item, +id-Candidate-SpCell-List, +id-Cause, +id-Cancel-all-Warning-Messages-Indicator, +id-Cells-Failed-to-be-Activated-List, +id-Cells-Failed-to-be-Activated-List-Item, +id-Cells-Status-Item, + +id-Cells-Status-List, +id-Cells-to-be-Activated-List, +id-Cells-to-be-Activated-List-Item, +id-Cells-to-be-Deactivated-List, +id-Cells-to-be-Deactivated-List-Item, +id-Cells-Allowed-to-be-Deactivated-List, +id-Cells-Allowed-to-be-Deactivated-List-Item, +id-Cells-With-SSBs-Activated-List, +id-Recommended-SSBs-for-Paging-List, +id-ConfirmedUEID, +id-CriticalityDiagnostics, +id-C-RNTI, +id-CUtoDURRCInformation, +id-DRB-Activity-Item, +id-DRB-Activity-List, +id-DRBs-FailedToBeModified-Item, +id-DRBs-FailedToBeModified-List, +id-DRBs-FailedToBeSetup-Item, +id-DRBs-FailedToBeSetup-List, +id-DRBs-FailedToBeSetupMod-Item, +id-DRBs-FailedToBeSetupMod-List, +id-DRBs-ModifiedConf-Item, +id-DRBs-ModifiedConf-List, +id-DRBs-Modified-Item, + +id-DRBs-Modified-List, +id-DRB-Notify-Item, +id-DRB-Notify-List, +id-DRBs-Required-ToBeModified-Item, +id-DRBs-Required-ToBeModified-List, +id-DRBs-Required-ToBeReleased-Item, +id-DRBs-Required-ToBeReleased-List, +id-DRBs-Setup-Item, +id-DRBs-Setup-List, +id-DRBs-SetupMod-Item, +id-DRBs-SetupMod-List, +id-DRBs-ToBeModified-Item, +id-DRBs-ToBeModified-List, +id-DRBs-ToBeReleased-Item, +id-DRBs-ToBeReleased-List, +id-DRBs-ToBeSetup-Item, +id-DRBs-ToBeSetup-List, +id-DRBs-ToBeSetupMod-Item, +id-DRBs-ToBeSetupMod-List, +id-DRXCycle, +id-DUtoCURRCInformation, +id-ExecuteDuplication, +id-FullConfiguration, +id-gNB-CU-MBS-FlAP-ID, + +id-gNB-CU-UE-FlAP-ID, +id-gNB-DU-MBS-FlAP-ID, +id-gNB-DU-UE-FlAP-ID, +id-gNB-DU-ID, +id-GNB-DU-Served-Cells-Item, +id-gNB-DU-Served-Cells-List, +id-gNB-CU-Name, +id-gNB-DU-Name, +id-Extended-GNB-CU-Name, +id-Extended-GNB-DU-Name, +id-InactivityMonitoringRequest, +id-InactivityMonitoringResponse, +id-MBS-Area-Session-ID, +id-MBS-CUtoDURRCInformation, +id-MBS-Session-ID, +id-MBS-ServiceArea, +id-MBSSMulticastFlUContextDescriptor, +id-MC-PagingCell-Item, +id-MC-PagingCell-List, +id-MulticastFlUContextReferenceCU, +id-MulticastMBSSessionSetupList, +id-MulticastMBSSessionRemoveList, +id-MulticastMRBs-FailedToBeModified-List, +id-MulticastMRBs-FailedToBeModified-Item, + +id-MulticastMRBs-FailedToBeSetup-List, +id-MulticastMRBs-FailedToBeSetup-Item, +id-MulticastMRBs-FailedToBeSetupMod-List, +id-MulticastMRBs-FailedToBeSetupMod-Item, +id-MulticastMRBs-Modified-List, +id-MulticastMRBs-Modified-Item, +id-MulticastMRBs-Setup-List, +id-MulticastMRBs-Setup-Item, +id-MulticastMRBs-SetupMod-List, +id-MulticastMRBs-SetupMod-Item, +id-MulticastMRBs-ToBeModified-List, +id-MulticastMRBs-ToBeModified-Item, +id-MulticastMRBs-ToBeReleased-List, +id-MulticastMRBs-ToBeReleased-Item, +id-MulticastMRBs-ToBeSetup-List, +id-MulticastMRBs-ToBeSetup-Item, +id-MulticastMRBs-ToBeSetupMod-List, +id-MulticastMRBs-ToBeSetupMod-Item, +id-MulticastF1UContext-ToBeSetup-List, +id-MulticastF1UContext-ToBeSetup-Item, +id-MulticastF1UContext-Setup-List, +id-MulticastF1UContext-Setup-Item, +id-MulticastF1UContext-FailedToBeSetup-List, +id-MulticastF1UContext-FailedToBeSetup-Item, + +id-BroadcastAreaScope, +id-new-gNB-CU-UE-F1AP-ID, +id-new-gNB-DU-UE-F1AP-ID, +id-oldgNB-DU-UE-F1AP-ID, +id-PLMNAssistanceInfoForNetShar, +id-Potential-SpCell-Item, +id-Potential-SpCell-List, +id-RAT-FrequencyPriorityInformation, +id-RedirectedRRmessage, +id-ResetType, +id-RequestedSRSTransmissionCharacteristics, +id-ResourceCoordinationTransferContainer, +id-RRContainer, +id-RRContainer-RRSetupComplete, +id-RRReconfigurationCompleteIndicator, +id-SCell-FailedtoSetup-List, +id-SCell-FailedtoSetup-Item, +id-SCell-FailedtoSetupMod-List, +id-SCell-FailedtoSetupMod-Item, +id-SCell-ToBeRemoved-Item, +id-SCell-ToBeRemoved-List, +id-SCell-ToBeSetup-Item, +id-SCell-ToBeSetup-List, +id-SCell-ToBeSetupMod-Item, + +id-SCell-ToBeSetupMod-List, +id-SDT-Termination-Request, +id-SDT-Volume-Threshold, +id-SelectedPLMNID, +id-Served-Cells-To-Add-Item, +id-Served-Cells-To-Add-List, +id-Served-Cells-To-Delete-Item, +id-Served-Cells-To-Delete-List, +id-Served-Cells-To-Modify-Item, +id-Served-Cells-To-Modify-List, +id-ServCellIndex, +id-ServingCellMO, +id-SNSSAI, +id-SpCell-ID, +id-SpCellULConfigured, +id-SRBID, +id-SRBs-FailedToBeSetup-Item, +id-SRBs-FailedToBeSetup-List, +id-SRBs-FailedToBeSetupMod-Item, +id-SRBs-FailedToBeSetupMod-List, +id-SRBs-Required-ToBeReleased-Item, +id-SRBs-Required-ToBeReleased-List, +id-SRBs-ToBeReleased-Item, +id-SRBs-ToBeReleased-List, + +id-SRBs-ToBeSetup-Item, +id-SRBs-ToBeSetup-List, +id-SRBs-ToBeSetupMod-Item, +id-SRBs-ToBeSetupMod-List, +id-SRBs-Modified-Item, +id-SRBs-Modified-List, +id-SRBs-Setup-Item, +id-SRBs-Setup-List, +id-SRBs-SetupMod-Item, +id-SRBs-SetupMod-List, +id-SupportedUETypeList, +id-TimeToWait, +id-TransactionID, +id-TransmissionActionIndicator, +id-UEContextNotRetrievable, +id-UE-associatedLogicalF1-ConnectionItem, +id-UE-associatedLogicalF1-ConnectionListResAck, +id-UEIdentity-List-For-Paging-List, +id-UEIdentity-List-For-Paging-Item, +id-UE-MulticastMRBs-ConfirmedToBeModified-List, +id-UE-MulticastMRBs-ConfirmedToBeModified-Item, +id-UE-MulticastMRBs-RequiredToBeModified-List, +id-UE-MulticastMRBs-RequiredToBeModified-Item, +id-UE-MulticastMRBs-RequiredToBeReleased-List, + +id-UE-MulticastMRBs-RequiredToBeReleased-Item, +id-UE-MulticastMRBs-Setup-List, +id-UE-MulticastMRBs-Setup-Item, +id-UE-MulticastMRBs-Setupnew-List, +id-UE-MulticastMRBs-Setupnew-Item, +id-UE-MulticastMRBs-ToBeReleased-List, +id-UE-MulticastMRBs-ToBeReleased-Item, +id-UE-MulticastMRBs-ToBeSetup-atModify-List, +id-UE-MulticastMRBs-ToBeSetup-atModify-Item, +id-UE-MulticastMRBs-ToBeSetup-List, +id-UE-MulticastMRBs-ToBeSetup-Item, +id-DUtoCURRCContainer, +id-NRCGI, +id-PagingCell-Item, +id-PagingCell-List, +id-PagingDRX, +id-PagingPriority, +id-SItype-List, +id-UEIdentityIndexValue, +id-GNB-CU-TNL-Association-Setup-List, +id-GNB-CU-TNL-Association-Setup-Item, +id-GNB-CU-TNL-Association-Failed-To-Setup-List, +id-GNB-CU-TNL-Association-Failed-To-Setup-Item, +id-GNB-CU-TNL-Association-To-Add-Item, + +id-GNB-CU-TNL-Association-To-Add-List, +id-GNB-CU-TNL-Association-To-Remove-Item, +id-GNB-CU-TNL-Association-To-Remove-List, +id-GNB-CU-TNL-Association-To-Update-Item, +id-GNB-CU-TNL-Association-To-Update-List, +id-MaskedIMEISV, +id-PagingIdentity, +id-Cells-to-be-Barred-List, +id-Cells-to-be-Barred-Item, +id-PWSSystemInformation, +id-RepetitionPeriod, +id-NumberOfBroadcastRequest, +id-Cells-To-Be-Broadcast-List, +id-Cells-To-Be-Broadcast-Item, +id-Cells-Broadcast-Completed-List, +id-Cells-Broadcast-Completed-Item, +id-Broadcast-To-Be-Cancelled-List, +id-Broadcast-To-Be-Cancelled-Item, +id-Cells-Broadcast-Cancelled-List, +id-Cells-Broadcast-Cancelled-Item, +id-NR-CGI-List-For-Restart-List, +id-NR-CGI-List-For-Restart-Item, +id-PWS-Failed-NR-CGI-List, +id-PWS-Failed-NR-CGI-Item, + +id-EUTRA-NR-CellResourceCoordinationReq-Container, +id-EUTRA-NR-CellResourceCoordinationReqAck-Container, +id-Protected-EUTRA-Resources-List, +id-RequestType, +id-ServingPLMN, +id-DRXConfigurationIndicator, +id-RLCFailureIndication, +id-UplinkTxDirectCurrentListInformation, +id-SULAccessIndication, +id-Protected-EUTRA-Resources-Item, +id-GNB-DUConfigurationQuery, +id-GNB-DU-UE-AMBR-UL, +id-GNB-CU-RRC-Version, +id-GNB-DU-RRC-Version, +id-GNBDUOverloadInformation, +id-NeedforGap, +id-RRCDeliveryStatusRequest, +id-RRCDeliveryStatus, +id-Dedicated-SIDelivery-NeededUE-List, +id-Dedicated-SIDelivery-NeededUE-Item, +id-ResourceCoordinationTransferInformation, +id-Associated-SCell-List, +id-Associated-SCell-Item, +id-IgnoreResourceCoordinationContainer, + +id-UAC-Assistance-Info, +id-RANUEID, +id-PagingOrigin, +id-GNB-DU-TNL-Association-To-Remove-Item, +id-GNB-DU-TNL-Association-To-Remove-List, +id-NotificationInformation, +id-TraceActivation, +id-TraceID, +id-Neighbour-Cell-Information-List, +id-Neighbour-Cell-Information-Item, +id-SymbolAllocInSlot, +id-NumDLULSymbols, +id-AdditionalRRMPriorityIndex, +id-DUCURadioInformationType, +id-CUDURadioInformationType, +id-LowerLayerPresenceStatusChange, +id-Transport-Layer-Address-Info, +id-BHChannels-ToBeSetup-List, +id-BHChannels-ToBeSetup-Item, +id-BHChannels-Setup-List, +id-BHChannels-Setup-Item, +id-BHChannels-ToBeModified-Item, +id-BHChannels-ToBeModified-List, +id-BHChannels-ToBeReleased-Item, + +id-BHChannels-ToBeReleased-List, +id-BHChannels-ToBeSetupMod-Item, +id-BHChannels-ToBeSetupMod-List, +id-BHChannels-FailedToBeSetup-Item, +id-BHChannels-FailedToBeSetup-List, +id-BHChannels-FailedToBeModified-Item, +id-BHChannels-FailedToBeModified-List, +id-BHChannels-FailedToBeSetupMod-Item, +id-BHChannels-FailedToBeSetupMod-List, +id-BHChannels-Modified-Item, +id-BHChannels-Modified-List, +id-BHChannels-SetupMod-Item, +id-BHChannels-SetupMod-List, +id-BHChannels-Required-ToBeReleased-Item, +id-BHChannels-Required-ToBeReleased-List, +id-BAPAddress, +id-ConfiguredBAPAddress, +id-BH-Routing-Information-Added-List, +id-BH-Routing-Information-Added-List-Item, +id-BH-Routing-Information-Removed-List, +id-BH-Routing-Information-Removed-List-Item, +id-UL-BH-Non-UP-Traffic-Mapping, +id-Child-Nodes-List, +id-Activated-Cells-to-be-Updated-List, + +id-IABIPv6RequestType, +id-IAB-TNL-Addresses-To-Remove-List, +id-IAB-TNL-Addresses-To-Remove-Item, +id-IAB-Allocated-TNL-Address-List, +id-IAB-Allocated-TNL-Address-Item, +id-IABv4AddressesRequested, +id-TrafficMappingInformation, +id-UL-UP-TNL-Information-to-Update-List, +id-UL-UP-TNL-Information-to-Update-List-Item, +id-UL-UP-TNL-Address-to-Update-List, +id-UL-UP-TNL-Address-to-Update-List-Item, +id-DL-UP-TNL-Address-to-Update-List, +id-DL-UP-TNL-Address-to-Update-List-Item, +id-NRV2XServicesAuthorized, +id-LTEV2XServicesAuthorized, +id-NRUESidelinkAggregateMaximumBitrate, +id-LTEUESidelinkAggregateMaximumBitrate, +id-PC5LinkAMBR, +id-SLDRBs-FailedToBeModified-Item, +id-SLDRBs-FailedToBeModified-List, +id-SLDRBs-FailedToBeSetup-Item, +id-SLDRBs-FailedToBeSetup-List, +id-SLDRBs-Modified-Item, +id-SLDRBs-Modified-List, + +id-SLDRBs-Required-ToBeModified-Item, +id-SLDRBs-Required-ToBeModified-List, +id-SLDRBs-Required-ToBeReleased-Item, +id-SLDRBs-Required-ToBeReleased-List, +id-SLDRBs-Setup-Item, +id-SLDRBs-Setup-List, +id-SLDRBs-ToBeModified-Item, +id-SLDRBs-ToBeModified-List, +id-SLDRBs-ToBeReleased-Item, +id-SLDRBs-ToBeReleased-List, +id-SLDRBs-ToBeSetup-Item, +id-SLDRBs-ToBeSetup-List, +id-SLDRBs-ToBeSetupMod-Item, +id-SLDRBs-ToBeSetupMod-List, +id-SLDRBs-SetupMod-List, +id-SLDRBs-FailedToBeSetupMod-List, +id-SLDRBs-SetupMod-Item, +id-SLDRBs-FailedToBeSetupMod-Item, +id-SLDRBs-ModifiedConf-List, +id-SLDRBs-ModifiedConf-Item, +id-gNBCUMeasurementID, +id-gNBDMUMeasurementID, +id-RegistrationRequest, +id-ReportCharacteristics, + +id-CellToReportList, +id-CellMeasurementResultList, +id-HardwareLoadIndicator, +id-ReportingPeriodicity, +id-TNLCapacityIndicator, +id-RAReportList, +id-RLFReportInformationList, +id-ReportingRequestType, +id-TimeReferenceInformation, +id-ConditionalInterDUMobilityInformation, +id-ConditionalIntraDUMobilityInformation, +id-targetCellsToCancel, +id-requestedTargetCellGlobalID, +id-TraceCollectionEntityIPAddress, +id-ManagementBasedMDTPLMNList, +id-PrivacyIndicator, +id-TraceCollectionEntityURI, +id-ServingNID, +id-PosAssistance-Information, +id-PosBroadcast, +id-PositioningBroadcastCells, +id-RoutingID, +id-PosAssistanceInformationFailureList, +id-PosMeasurementQuantities, + +id-PosMeasurementResultList, +id-PosMeasurementPeriodicity, +id-PosReportCharacteristics, +id-TRPInformationTypeListTRPReq, +id-TRPInformationTypeItem, +id-TRPInformationListTRPResp, +id-TRPInformationItem, +id-LMF-MeasurementID, +id-RAN-MeasurementID, +id-SRSType, +id-ActivationTime, +id-AbortTransmission, +id-SRSConfiguration, +id-TRPList, +id-E-CID-MeasurementQuantities, +id-E-CID-MeasurementPeriodicity, +id-E-CID-MeasurementResult, +id-Cell-Portion-ID, +id-LMF-UE-MeasurementID, +id-RAN-UE-MeasurementID, +id-SFNInitialisationTime, +id-SystemFrameNumber, +id-SlotNumber, +id-TRP-MeasurementRequestList, + +id-MeasurementBeamInfoRequest, +id-E-CID-ReportCharacteristics, +id-F1CTransferPath, +id-SCGIndicator, +id-SRSPatialRelationPerSRSResource, +id-PosMeasurementPeriodicityExtended, +id-SuccessfulHOReportInformationList, +id-Coverage-Modification-Notification, +id-CCO-Assistance-Information, +id-CellsForSON-List, +id-IABCongestionIndication, +id-IABConditionalRRCMessagedeliveryIndication, +id-F1CTransferPathNRDC, +id-BufferSizeThresh, +id-IAB-TNL-Addresses-Exception, +id-BAP-Header-Rewriting-Added-List, +id-BAP-Header-Rewriting-Added-List-Item, +id-Re-routingEnableIndicator, +id-NonFlterminatingTopologyIndicator, +id-EgressNonFlterminatingTopologyIndicator, +id-IngressNonFlterminatingTopologyIndicator, +id-Neighbour-Node-Cells-List, +id-Serving-Cells-List, +id-MDTPollutedMeasurementIndicator, + +id-PDCMeasurementPeriodicity, +id-PDCMeasurementQuantities, +id-PDCMeasurementResult, +id-PDCReportType, +id-RAN-UE-PDC-MeasID, +id-SCGActivationRequest, +id-SCGActivationStatus, +id-TRP-MeasurementUpdateList, +id-PRSTRPList, +id-PRSTransmissionTRPList, +id-ResponseTime, +id-TRP-PRS-Info-List, +id-PRS-Measurement-Info-List, +id-PRSConfigRequestType, +id-MeasurementCharacteristicsRequestIndicator, +id-MeasurementTimeOccasion, +id-UEReportingInformation, +id-PosConextRevIndication, +id-NRRedCapUEIndication, +id-RANUEPagingDRX, +id-CNUEPagingDRX, +id-NRPagingeDRXInformation, +id-NRPagingeDRXInformationforRRRCINACTIVE, +id-QoEInformation, + +id-CG-SDTQueryIndication, +id-CG-SDTKeptIndicator, +id-CG-SDTSessionInfoOld, +id-SDTInformation, +id-FiveG-ProSeAuthorized, +id-FiveG-ProSePC5LinkAMBR, +id-FiveG-ProSeUEPC5AggregateMaximumBitrate, +id-UuRLCChannelToBeSetupList, +id-UuRLCChannelToBeModifiedList, +id-UuRLCChannelToBeReleasedList, +id-UuRLCChannelSetupList, +id-UuRLCChannelFailedToBeSetupList, +id-UuRLCChannelModifiedList, +id-UuRLCChannelFailedToBeModifiedList, +id-UuRLCChannelRequiredToBeModifiedList, +id-UuRLCChannelRequiredToBeReleasedList, +id-PC5RLCChannelToBeSetupList, +id-PC5RLCChannelToBeModifiedList, +id-PC5RLCChannelToBeReleasedList, +id-PC5RLCChannelSetupList, +id-PC5RLCChannelFailedToBeSetupList, +id-PC5RLCChannelModifiedList, +id-PC5RLCChannelFailedToBeModifiedList, +id-PC5RLCChannelRequiredToBeModifiedList, + +id-PC5RLCChannelRequiredToBeReleasedList, +id-SidelinkRelayConfiguration, +id-UpdatedRemoteUELocalID, +id-PathSwitchConfiguration, +id-PagingCause, +id-PEIPSAssistanceInfo, +id-UEPagingCapability, +id-GNBDUUESliceMaximumBitRateList, +id-PosMeasurementAmount, +id-BAP-Header-Rewriting-Removed-List, +id-BAP-Header-Rewriting-Removed-List-Item, +id-SLDRXCycleList, +id-ManagementBasedMDTPLMNModificationList, +id-ActivationRequestType, +id-PosMeasGapPreConfigList, +id-PosMeasurementPeriodicityNR-AoA, +id-SRSPosRRCCInactiveConfig, +id-SDTBearerConfigurationQueryIndication, +id-SDTBearerConfigurationInfo, +id-ServingCellMO-List, +id-ServingCellMO-List-Item, +id-ServingCellMO-encoded-in-CGC-List, +id-PosSItypeList, +id-DAPS-HO-Status, + +id-SRBMappingInfo, +id-UplinkTxDirectCurrentTwoCarrierListInfo, +id-SRSPosRRCInactiveQueryIndication, +id-UlTxDirectCurrentMoreCarrierInformation, +id-CPACMCGInformation, +id-ExtendedUEIdentityIndexValue, +id-HashedUEIdentityIndexValue, +id-DedicatedSIDeliveryIndication, +id-Configured-BWP-List, +id-NetworkControlledRepeaterAuthorized, +id-MT-SDT-Information, +id-LTMInformation-Setup, id-LTMConfigurationIDMappingList, +id-LTMInformation-Modify, +id-LTMCells-ToBeReleased-List, +id-LTMConfiguration, +id-EarlySyncInformation-Request, +id-EarlySyncInformation, +id-EarlySyncInformation-List, +id-LTMCellSwitchInformation, +id-TAInformation-List, +id-Source-gNB-DU-ID, +id-DeactivationIndication, +id-RAReportIndicationList, +id-SuccessfulPSCellChangeReportInformationList, + +id-PathAdditionInformation, +id-RANTSSRequestType, +id-RANTimingSynchronisationStatusInfo, +id-Target-gNB-ID, +id-Target-gNB-IP-address, +id-Target-SeGW-IP-address, +id-Activated-Cells-Mapping-List, +id-Activated-Cells-Mapping-List-Item, +id-F1SetupOutcome, +id-RRC-Terminating-IAB-Donor-Related-Info, +id-RRC-Terminating-IAB-Donor-gNB-ID, +id-NCGI-to-be-Updated-List, +id-NCGI-to-be-Updated-List-Item, +id-Mobile-IAB-MTUserLocationInformation, +id-IndicationMCInactiveReception, +id-MulticastCU2DURRCInfo, +id-MulticastDU2CURRCInfo, +id-MBSMulticastSessionReceptionState, +id-F1UTunnelNotEstablished, +id-MulticastCU2DUCommonRRRCInfo, +id-NRA2XServicesAuthorized, +id-LTEA2XServicesAuthorized, +id-NRUESidelinkAggregateMaximumBitrateForA2X, +id-LTEUESidelinkAggregateMaximumBitrateForA2X, + +id-NReRedCapUEIndication, +id-NRPaginglongeDRXInformationforRRCINACTIVE, +maxCellingNBDU, +maxnoofCandidateSpCells, +maxnoofDRBs, +maxnoofErrors, +maxnoofIndividualF1ConnectionsToReset, +maxnoofPotentialSpCells, +maxnoofSCells, +maxnoofSRBs, +maxnoofPagingCells, +maxnoofTNLAssociations, +maxCellineNB, +maxnoofUEIDs, +maxnoofBHRLCChannels, +maxnoofRoutingEntries, +maxnoofChildIABNodes, +maxnoofServedCellsIAB, +maxnoofTLAsIAB, +maxnoofULUPTNLInformationforIAB, +maxnoofUPTNLAddresses, +maxnoofSLDRBs, +maxnoofTRPInfoTypes, +maxnoofTRPs, + +``` + +maxnoofMRBs, +maxnoofUEIDforPaging, +maxnoofNeighbourNodeCellsIAB, +maxnoofMRBsforUE, +maxnoofServingCellMOs, +maxnoofLTMCells + +``` + +``` + +FROM FlAP-Constants; + +``` + +``` + +-- ***** +-- +-- RESET ELEMENTARY PROCEDURE +-- +-- ***** +-- +-- ***** +-- +-- Reset +-- +-- ***** + +``` + +``` +Reset ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {ResetIEs} }, + ... +} + +ResetIEs FLAP-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 { + f1-Interface ResetAll, + partOfF1-Interface UE-associatedLogicalF1-ConnectionListRes, + choice-extension ProtocolIE-SingleContainer { { ResetType-ExtIEs } } +} + +ResetType-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} +``` + +ResetAll ::= ENUMERATED { + +    reset-all, + +    ... +} + +UE-associatedLogicalF1-ConnectionListRes ::= SEQUENCE (SIZE(1.. maxnoofIndividualF1ConnectionsToReset)) OF ProtocolIE-SingleContainer { { UE-associatedLogicalF1-ConnectionItemRes } } + +UE-associatedLogicalF1-ConnectionItemRes FLAP-PROTOCOL-IES ::= { + +    { ID id-UE-associatedLogicalF1-ConnectionItem CRITICALITY reject TYPE UE-associatedLogicalF1-ConnectionItem PRESENCE mandatory}, + +    ... +} + +-- \*\*\*\*\* + +-- + +-- Reset Acknowledge + +-- + +-- \*\*\*\*\* + +ResetAcknowledge ::= SEQUENCE { + +    protocolIEs           ProtocolIE-Container           { {ResetAcknowledgeIEs} }, + +    ... +} + +ResetAcknowledgeIEs FIAP-PROTOCOL-IES ::= { + +{ ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE + mandatory } | + +{ ID id-UE-associatedLogicalF1-ConnectionListResAck CRITICALITY ignore TYPE UE-associatedLogicalF1-ConnectionListResAck PRESENCE + optional } | + +{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + +... + +} + +UE-associatedLogicalF1-ConnectionListResAck ::= SEQUENCE (SIZE(1.. maxnoofIndividualF1ConnectionsToReset)) OF ProtocolIE-SingleContainer { { UE-associatedLogicalF1-ConnectionItemResAck } } + +UE-associatedLogicalF1-ConnectionItemResAck FIAP-PROTOCOL-IES ::= { + +{ ID id-UE-associatedLogicalF1-ConnectionItem CRITICALITY ignore TYPE UE-associatedLogicalF1-ConnectionItem PRESENCE mandatory }, + +... + +} + +-- \*\*\*\*\* + +-- + +-- ERROR INDICATION ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- Error Indication + +-- +-- \*\*\*\*\* + +ErrorIndication ::= SEQUENCE { +    protocolIEs          ProtocolIE-Container      {{ErrorIndicationIEs}}, +    ... +} + +ErrorIndicationIEs FLAP-PROTOCOL-IES ::= { +    { ID id-TransactionID          CRITICALITY reject  TYPE TransactionID          PRESENCE mandatory } | +    { ID id-gNB-CU-UE-FLAP-ID      CRITICALITY ignore  TYPE GNB-CU-UE-FLAP-ID          PRESENCE optional } | +    { ID id-gNB-DU-UE-FLAP-ID      CRITICALITY ignore  TYPE GNB-DU-UE-FLAP-ID          PRESENCE optional } | +    { ID id-Cause                  CRITICALITY ignore  TYPE Cause                  PRESENCE optional } | +    { ID id-CriticalityDiagnostics  CRITICALITY ignore  TYPE CriticalityDiagnostics  PRESENCE optional }, +    ... +} + +-- \*\*\*\*\* +-- + +-- F1 SETUP ELEMENTARY PROCEDURE + +-- +-- \*\*\*\*\* + +-- \*\*\*\*\* + +``` + +-- +-- F1 Setup Request +-- +-- ***** + +F1SetupRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {F1SetupRequestIEs} }, + ... +} + +F1SetupRequestIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-gNB-DU-ID CRITICALITY reject TYPE GNB-DU-ID PRESENCE mandatory }| + { ID id-gNB-DU-Name CRITICALITY ignore TYPE GNB-DU-Name PRESENCE optional }| + { ID id-gNB-DU-Served-Cells-List CRITICALITY reject TYPE GNB-DU-Served-Cells-List PRESENCE optional }| + { ID id-GNB-DU-RRC-Version CRITICALITY reject TYPE RRC-Version PRESENCE mandatory }| + { ID id-Transport-Layer-Address-Info CRITICALITY ignore TYPE Transport-Layer-Address-Info PRESENCE optional }| + { ID id-BAPAddress CRITICALITY ignore TYPE BAPAddress PRESENCE optional }| + { ID id-Extended-GNB-DU-Name CRITICALITY ignore TYPE Extended-GNB-DU-Name PRESENCE optional }| + { ID id-RRC-Terminating-IAB-Donor-gNB-ID CRITICALITY ignore TYPE GlobalGNB-ID PRESENCE optional }| + { ID id-Mobile-IAB-MTUserLocationInformation CRITICALITY ignore TYPE Mobile-IAB-MTUserLocationInformation PRESENCE optional }, + ... +} + +``` + +``` +GNB-DU-Served-Cells-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { GNB-DU-Served-Cells-ItemIEs } } +``` + +``` +GNB-DU-Served-Cells-ItemIEs FIAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-GNB-DU-Served-Cells-Item CRITICALITY reject TYPE GNB-DU-Served-Cells-Item PRESENCE mandatory }, +``` + +``` + ... +``` + +``` +} +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- F1 Setup Response +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +F1SetupResponse ::= SEQUENCE { +``` + +``` + protocolIEs ProtocolIE-Container { {F1SetupResponseIEs} }, +``` + +``` + ... +``` + +``` +} +``` + +``` +F1SetupResponseIEs FIAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| +``` + +``` + { ID id-gNB-CU-Name CRITICALITY ignore TYPE GNB-CU-Name PRESENCE optional }| +``` + +``` + + { ID id-Cells-to-be-Activated-List CRITICALITY reject TYPE Cells-to-be-Activated-List PRESENCE optional }| + { ID id-GNB-CU-RRC-Version CRITICALITY reject TYPE RRC-Version PRESENCE mandatory }| + { ID id-Transport-Layer-Address-Info CRITICALITY ignore TYPE Transport-Layer-Address-Info PRESENCE optional }| + { ID id-UL-BH-Non-UP-Traffic-Mapping CRITICALITY reject TYPE UL-BH-Non-UP-Traffic-Mapping PRESENCE optional }| + { ID id-BAPAddress CRITICALITY ignore TYPE BAPAddress PRESENCE optional }| + { ID id-Extended-GNB-CU-Name CRITICALITY ignore TYPE Extended-GNB-CU-Name PRESENCE optional }| + { ID id-NCGI-to-be-Updated-List CRITICALITY ignore TYPE NCGI-to-be-Updated-List PRESENCE optional }, + ... +} + +Cells-to-be-Activated-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { Cells-to-be-Activated-List-ItemIEs } } + +Cells-to-be-Activated-List-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-Cells-to-be-Activated-List-Item CRITICALITY reject TYPE Cells-to-be-Activated-List-Item PRESENCE mandatory}, + ... +} + +NCGI-to-be-Updated-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { NCGI-to-be-Updated-List-ItemIEs } } + +NCGI-to-be-Updated-List-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-NCGI-to-be-Updated-List-Item CRITICALITY reject TYPE NCGI-to-be-Updated-List-Item PRESENCE mandatory}, + ... +} + +``` + +``` + +} + +-- ***** +-- +-- F1 Setup Failure +-- +-- ***** + +F1SetupFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {F1SetupFailureIEs} }, + ... +} + +F1SetupFailureIEs FLAP-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-DU CONFIGURATION UPDATE ELEMENTARY PROCEDURE +-- +-- ***** +-- +-- ***** +-- +-- GNB-DU CONFIGURATION UPDATE +-- +-- ***** + +``` + +``` + +GNBDUConfigurationUpdate ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {GNBDUConfigurationUpdateIEs} }, + ... +} + +``` + +``` + +GNBDUConfigurationUpdateIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-Served-Cells-To-Add-List CRITICALITY reject TYPE Served-Cells-To-Add-List PRESENCE optional }| + { ID id-Served-Cells-To-Modify-List CRITICALITY reject TYPE Served-Cells-To-Modify-List PRESENCE optional }| + { ID id-Served-Cells-To-Delete-List CRITICALITY reject TYPE Served-Cells-To-Delete-List PRESENCE optional }| + { ID id-Cells-Status-List CRITICALITY reject TYPE Cells-Status-List PRESENCE optional }| + { ID id-Dedicated-SIDelivery-NeededUE-List CRITICALITY ignore TYPE Dedicated-SIDelivery-NeededUE-List PRESENCE optional }| + { ID id-gNB-DU-ID CRITICALITY reject TYPE GNB-DU-ID PRESENCE optional }| + +``` + +``` + + { ID id-GNB-DU-TNL-Association-To-Remove-List CRITICALITY reject TYPE GNB-DU-TNL-Association-To-Remove-List PRESENCE optional }| + { ID id-Transport-Layer-Address-Info CRITICALITY ignore TYPE Transport-Layer-Address-Info PRESENCE optional }| + { ID id-Coverage-Modification-Notification CRITICALITY ignore TYPE Coverage-Modification-Notification PRESENCE optional }| + { ID id-gNB-DU-Name CRITICALITY ignore TYPE GNB-DU-Name PRESENCE optional }| + { ID id-Extended-GNB-DU-Name CRITICALITY ignore TYPE Extended-GNB-DU-Name PRESENCE optional }| + { ID id-RRC-Terminating-IAB-Donor-Related-Info CRITICALITY ignore TYPE RRC-Terminating-IAB-Donor-Related-Info PRESENCE optional }| + { ID id-Mobile-IAB-MTUserLocationInformation CRITICALITY ignore TYPE Mobile-IAB-MTUserLocationInformation PRESENCE optional }, + ... +} + +Served-Cells-To-Add-List := SEQUENCE (SIZE(1.. maxCeilingNB DU)) OF ProtocolIE-SingleContainer { { Served-Cells-To-Add-ItemIEs } } +Served-Cells-To-Modify-List := SEQUENCE (SIZE(1.. maxCeilingNB DU)) OF ProtocolIE-SingleContainer { { Served-Cells-To-Modify-ItemIEs } } +Served-Cells-To-Delete-List := SEQUENCE (SIZE(1.. maxCeilingNB DU)) OF ProtocolIE-SingleContainer { { Served-Cells-To-Delete-ItemIEs } } +Cells-Status-List := SEQUENCE (SIZE(0.. maxCeilingNB DU)) OF ProtocolIE-SingleContainer { { Cells-Status-ItemIEs } } + +Dedicated-SIDelivery-NeededUE-List := SEQUENCE (SIZE(1.. maxnoofUEIDs)) OF ProtocolIE-SingleContainer { { Dedicated-SIDelivery-NeededUE-ItemIEs } } + +GNB-DU-TNL-Association-To-Remove-List := SEQUENCE (SIZE(1.. maxnoofTNLAssociations)) OF ProtocolIE-SingleContainer { { GNB-DU-TNL-Association-To-Remove-ItemIEs } } + +Served-Cells-To-Add-ItemIEs FIAP-PROTOCOL-IES := { + { ID id-Served-Cells-To-Add-Item CRITICALITY reject TYPE Served-Cells-To-Add-Item PRESENCE mandatory }, + ... +} + +``` + +``` +Served-Cells-To-Modify-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-Served-Cells-To-Modify-Item CRITICALITY reject TYPE Served-Cells-To-Modify-Item PRESENCE mandatory +}, + ... +} + +Served-Cells-To-Delete-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-Served-Cells-To-Delete-Item CRITICALITY reject TYPE Served-Cells-To-Delete-Item PRESENCE mandatory }, + ... +} + +Cells-Status-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-Cells-Status-Item CRITICALITY reject TYPE Cells-Status-Item PRESENCE mandatory }, + ... +} + +Dedicated-SIDelivery-NeededUE-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-Dedicated-SIDelivery-NeededUE-Item CRITICALITY ignore TYPE Dedicated-SIDelivery-NeededUE-Item PRESENCE mandatory }, + ... +} + +GNB-DU-TNL-Association-To-Remove-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-GNB-DU-TNL-Association-To-Remove-Item CRITICALITY reject TYPE GNB-DU-TNL-Association-To-Remove-Item PRESENCE +mandatory }, +``` + +``` + + ... + } + + -- ***** + -- + -- GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE + -- + -- ***** + +``` + +``` + +GNBDUConfigurationUpdateAcknowledge ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {GNBDUConfigurationUpdateAcknowledgeIEs} }, + ... +} + +``` + +``` + +GNBDUConfigurationUpdateAcknowledgeIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-Cells-to-be-Activated-List CRITICALITY reject TYPE Cells-to-be-Activated-List PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + { ID id-Cells-to-be-Deactivated-List CRITICALITY reject TYPE Cells-to-be-Deactivated-List PRESENCE optional }| + { ID id-Transport-Layer-Address-Info CRITICALITY ignore TYPE Transport-Layer-Address-Info PRESENCE optional }| + { ID id-UL-BH-Non-UP-Traffic-Mapping CRITICALITY reject TYPE UL-BH-Non-UP-Traffic-Mapping PRESENCE optional }| + { ID id-BAPAddress CRITICALITY ignore TYPE BAPAddress PRESENCE optional }| + +``` + +``` + + { ID id-CellsForSON-List CRITICALITY ignore TYPE CellsForSON-List PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- GNB-DU CONFIGURATION UPDATE FAILURE + +-- + +-- \*\*\*\*\* + +``` + +GNBDUConfigurationUpdateFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {GNBDUConfigurationUpdateFailureIEs} }, + ... +} + +``` + +``` + +GNBDUConfigurationUpdateFailureIEs FLAP-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 CONFIGURATION UPDATE ELEMENTARY PROCEDURE +-- +-- ***** +-- +-- ***** +-- +-- GNB-CU CONFIGURATION UPDATE +-- +-- ***** + +``` + +``` + +GNBCUConfigurationUpdate ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { GNBCUConfigurationUpdateIEs} }, + ... +} + +``` + +``` + +GNBCUConfigurationUpdateIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-Cells-to-be-Activated-List CRITICALITY reject TYPE Cells-to-be-Activated-List PRESENCE optional }| + { ID id-Cells-to-be-Deactivated-List CRITICALITY reject TYPE Cells-to-be-Deactivated-List PRESENCE optional }| + { ID id-GNB-CU-TNL-Association-To-Add-List CRITICALITY ignore TYPE GNB-CU-TNL-Association-To-Add-List PRESENCE optional }| + { ID id-GNB-CU-TNL-Association-To-Remove-List CRITICALITY ignore TYPE GNB-CU-TNL-Association-To-Remove-List PRESENCE optional }| + { ID id-GNB-CU-TNL-Association-To-Update-List CRITICALITY ignore TYPE GNB-CU-TNL-Association-To-Update-List PRESENCE optional }| + { ID id-Cells-to-be-Barred-List CRITICALITY ignore TYPE Cells-to-be-Barred-List PRESENCE optional }| +} + +``` + +``` + + { ID id-Protected-EUTRA-Resources-List CRITICALITY reject TYPE Protected-EUTRA-Resources-List PRESENCE optional }| + { ID id-Neighbour-Cell-Information-List CRITICALITY ignore TYPE Neighbour-Cell-Information-List PRESENCE optional }| + { ID id-Transport-Layer-Address-Info CRITICALITY ignore TYPE Transport-Layer-Address-Info PRESENCE optional }| + { ID id-UL-BH-Non-UP-Traffic-Mapping CRITICALITY reject TYPE UL-BH-Non-UP-Traffic-Mapping PRESENCE optional }| + { ID id-BAPAddress CRITICALITY ignore TYPE BAPAddress PRESENCE optional }| + { ID id-CCO-Assistance-Information CRITICALITY ignore TYPE CCO-Assistance-Information PRESENCE optional }| + { ID id-CellsForSON-List CRITICALITY ignore TYPE CellsForSON-List PRESENCE optional }| + { ID id-gNB-CU-Name CRITICALITY ignore TYPE GNB-CU-Name PRESENCE optional }| + { ID id-Extended-GNB-CU-Name CRITICALITY ignore TYPE Extended-GNB-CU-Name PRESENCE optional }| + { ID id-Cells-Allowed-to-be-Deactivated-List CRITICALITY ignore TYPE Cells-Allowed-to-be-Deactivated-List PRESENCE optional }, + ... +} + +``` + +``` +Cells-to-be-Deactivated-List ::= SEQUENCE (SIZE(1.. maxCeilingNBUDU)) OF ProtocolIE-SingleContainer { { Cells-to-be-Deactivated-List-ItemIEs } } +``` + +``` +GNB-CU-TNL-Association-To-Add-List ::= SEQUENCE (SIZE(1.. maxnoofTNLAssociations)) OF ProtocolIE-SingleContainer { { GNB-CU-TNL-Association-To-Add-ItemIEs } } +``` + +``` +GNB-CU-TNL-Association-To-Remove-List ::= SEQUENCE (SIZE(1.. maxnoofTNLAssociations)) OF ProtocolIE-SingleContainer { { GNB-CU-TNL-Association-To-Remove-ItemIEs } } +``` + +``` +GNB-CU-TNL-Association-To-Update-List ::= SEQUENCE (SIZE(1.. maxnoofTNLAssociations)) OF ProtocolIE-SingleContainer { { GNB-CU-TNL-Association-To-Update-ItemIEs } } +``` + +``` +Cells-to-be-Barred-List ::= SEQUENCE (SIZE(1.. maxCeilingNBUDU)) OF ProtocolIE-SingleContainer { { Cells-to-be-Barred-ItemIEs } } +``` + +``` +Cells-Allowed-to-be-Deactivated-List ::= SEQUENCE (SIZE(1.. maxCeilingNBUDU)) OF ProtocolIE-SingleContainer { { Cells-Allowed-to-be-Deactivated-List-ItemIEs } } +``` + +``` +Cells-Allowed-to-be-Deactivated-List-ItemIEs FIAP-PROTOCOL-IES ::= { +``` + +``` +{ ID id-Cells-Allowed-to-be-Deactivated-List-Item CRITICALITY ignore TYPE Cells-Allowed-to-be-Deactivated-List-Item PRESENCE optional), +... +} + +Cells-to-be-Deactivated-List-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-Cells-to-be-Deactivated-List-Item CRITICALITY reject TYPE Cells-to-be-Deactivated-List-Item + PRESENCE mandatory }, + ... +} + +GNB-CU-TNL-Association-To-Add-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-GNB-CU-TNL-Association-To-Add-Item CRITICALITY ignore TYPE GNB-CU-TNL-Association-To-Add-Item PRESENCE mandatory }, + ... +} + +GNB-CU-TNL-Association-To-Remove-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-GNB-CU-TNL-Association-To-Remove-Item CRITICALITY ignore TYPE GNB-CU-TNL-Association-To-Remove-Item PRESENCE + mandatory }, + ... +} + +GNB-CU-TNL-Association-To-Update-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-GNB-CU-TNL-Association-To-Update-Item CRITICALITY ignore TYPE GNB-CU-TNL-Association-To-Update-Item PRESENCE + mandatory }, +``` + +... +} + +Cells-to-be-Barred-ItemIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-Cells-to-be-Barred-Item CRITICALITY ignore TYPE Cells-to-be-Barred-Item PRESENCE mandatory }, + +... +} + +Protected-EUTRA-Resources-List ::= SEQUENCE (SIZE(1.. maxCellineNB)) OF ProtocolIE-SingleContainer { { Protected-EUTRA-Resources-ItemIEs } } + +Protected-EUTRA-Resources-ItemIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-Protected-EUTRA-Resources-Item CRITICALITY reject TYPE Protected-EUTRA-Resources-Item PRESENCE mandatory }, + +... +} + +Neighbour-Cell-Information-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { Neighbour-Cell-Information-ItemIEs } } + +Neighbour-Cell-Information-ItemIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-Neighbour-Cell-Information-Item CRITICALITY ignore TYPE Neighbour-Cell-Information-Item PRESENCE mandatory }, + +... +} + +-- \*\*\*\*\* + +-- + +-- GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE + +-- +-- \*\*\*\*\* + +``` +GNBCUConfigurationUpdateAcknowledge ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { GNBCUConfigurationUpdateAcknowledgeIEs } }, + ... +} +``` + +``` +GNBCUConfigurationUpdateAcknowledgeIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-Cells-Failed-to-be-Activated-List CRITICALITY reject TYPE Cells-Failed-to-be-Activated-List PRESENCE optional}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional +}| + { ID id-GNB-CU-TNL-Association-Setup-List CRITICALITY ignore TYPE GNB-CU-TNL-Association-Setup-List PRESENCE optional }| + { ID id-GNB-CU-TNL-Association-Failed-To-Setup-List CRITICALITY ignore TYPE GNB-CU-TNL-Association-Failed-To-Setup-List PRESENCE optional }| + { ID id-Dedicated-SIDelivery-NeededUE-List CRITICALITY ignore TYPE Dedicated-SIDelivery-NeededUE-List PRESENCE optional +}| + { ID id-Transport-Layer-Address-Info CRITICALITY ignore TYPE Transport-Layer-Address-Info PRESENCE optional }| + { ID id-Cells-With-SSBs-Activated-List CRITICALITY ignore TYPE Cells-With-SSBs-Activated-List PRESENCE optional }, + ... +} +``` + +``` +Cells-Failed-to-be-Activated-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { Cells-Failed-to-be-Activated-List-ItemIEs } } +``` + +``` +GNB-CU-TNL-Association-Setup-List ::= SEQUENCE (SIZE(1.. maxnoofTNLAssociations)) OF ProtocolIE-SingleContainer { { GNB-CU-TNL-Association-Setup-ItemIEs } } +``` + +``` +GNB-CU-TNL-Association-Failed-To-Setup-List ::= SEQUENCE (SIZE(1.. maxnoofTNLAssociations)) OF ProtocolIE-SingleContainer { { GNB-CU-TNL-Association-Failed-To-Setup-ItemIEs } } +``` + +``` +Cells-Failed-to-be-Activated-List-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-Cells-Failed-to-be-Activated-List-Item CRITICALITY reject TYPE Cells-Failed-to-be-Activated-List-Item PRESENCE mandatory }, + ... +} +``` + +``` +GNB-CU-TNL-Association-Setup-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-GNB-CU-TNL-Association-Setup-Item CRITICALITY ignore TYPE GNB-CU-TNL-Association-Setup-Item PRESENCE mandatory }, + ... +} +``` + +``` +GNB-CU-TNL-Association-Failed-To-Setup-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-GNB-CU-TNL-Association-Failed-To-Setup-Item CRITICALITY ignore TYPE GNB-CU-TNL-Association-Failed-To-Setup-Item PRESENCE mandatory }, + ... +} +``` + +``` +-- ***** +-- +``` + +-- GNB-CU CONFIGURATION UPDATE FAILURE + +-- + +-- \*\*\*\*\* + +GNBCUConfigurationUpdateFailure ::= SEQUENCE { + +    protocolIEs          ProtocolIE-Container    { { GNBCUConfigurationUpdateFailureIEs} }, + +    ... + +} + +GNBCUConfigurationUpdateFailureIEs FLAP-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-DU RESOURCE COORDINATION REQUEST + +-- + +-- \*\*\*\*\* + +``` + +GNBDUResourceCoordinationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{GNBDUResourceCoordinationRequest-IEs}}, + ... +} + +``` + +``` + +GNBDUResourceCoordinationRequest-IEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-RequestType CRITICALITY reject TYPE RequestType PRESENCE mandatory }| + { ID id-EUTRA-NR-CellResourceCoordinationReq-Container CRITICALITY reject TYPE EUTRA-NR-CellResourceCoordinationReq-Container PRESENCE mandatory}| + { ID id-IgnoreResourceCoordinationContainer CRITICALITY reject TYPE IgnoreResourceCoordinationContainer PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- GNB-DU RESOURCE COORDINATION RESPONSE +-- +-- ***** + +``` + +``` + +GNBDUResourceCoordinationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{GNBDUResourceCoordinationResponse-IEs}}, + ... +} + +``` + +``` + +GNBDUResourceCoordinationResponse-IEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-EUTRA-NR-CellResourceCoordinationReqAck-Container CRITICALITY reject TYPE EUTRA-NR-CellResourceCoordinationReqAck-Container + PRESENCE mandatory}, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- UE Context Setup ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- UE CONTEXT SETUP REQUEST + +-- + +-- \*\*\*\*\* + +``` + +UEContextSetupRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { UEContextSetupRequestIEs} }, + ... +} + +``` + +UEContextSetupRequestIEs FLAP-PROTOCOL-IES ::= { + +| | | | | +|-------------------------------------------------|--------------------|----------------------------------------------|------------------------| +| { ID id-gNB-CU-UE-FLAP-ID | CRITICALITY reject | TYPE GNB-CU-UE-FLAP-ID | PRESENCE mandatory } | +| { ID id-gNB-DU-UE-FLAP-ID | CRITICALITY ignore | TYPE GNB-DU-UE-FLAP-ID | PRESENCE optional } | +| { ID id-SpCell-ID | CRITICALITY reject | TYPE NRCGI | PRESENCE mandatory } | +| { ID id-ServCellIndex | CRITICALITY reject | TYPE ServCellIndex | PRESENCE mandatory } | +| { ID id-SpCellULConfigured | CRITICALITY ignore | TYPE CellULConfigured | PRESENCE optional } | +| { ID id-CUtoDURRCInformation | CRITICALITY reject | TYPE CUtoDURRCInformation | PRESENCE mandatory } | +| { ID id-Candidate-SpCell-List | CRITICALITY ignore | TYPE Candidate-SpCell-List | PRESENCE optional } | +| { ID id-DRXCycle | CRITICALITY ignore | TYPE DRXCycle | PRESENCE optional } | +| { ID id-ResourceCoordinationTransferContainer | CRITICALITY ignore | TYPE ResourceCoordinationTransferContainer | PRESENCE optional } | +| { ID id-SCell-ToBeSetup-List | CRITICALITY ignore | TYPE SCell-ToBeSetup-List | PRESENCE optional } | +| { ID id-SRBs-ToBeSetup-List | CRITICALITY reject | TYPE SRBs-ToBeSetup-List | PRESENCE optional } | +| { ID id-DRBs-ToBeSetup-List | CRITICALITY reject | TYPE DRBs-ToBeSetup-List | PRESENCE optional } | +| { ID id-InactivityMonitoringRequest | CRITICALITY reject | TYPE InactivityMonitoringRequest | PRESENCE optional } | +| { ID id-RAT-FrequencyPriorityInformation | CRITICALITY reject | TYPE RAT-FrequencyPriorityInformation | PRESENCE optional } | +| { ID id-RRCContainer | CRITICALITY ignore | TYPE RRCContainer | PRESENCE optional } | +| { ID id-MaskedIMEISV | CRITICALITY ignore | TYPE MaskedIMEISV | PRESENCE optional } | +| { ID id-ServingPLMN | CRITICALITY ignore | TYPE PLMN-Identity | PRESENCE optional } | +| { ID id-GNB-DU-UE-AMBR-UL | CRITICALITY ignore | TYPE BitRate | PRESENCE conditional } | +| { ID id-RRCDeliveryStatusRequest | CRITICALITY ignore | TYPE RRCDeliveryStatusRequest | PRESENCE optional } | +| { ID id-ResourceCoordinationTransferInformation | CRITICALITY ignore | TYPE ResourceCoordinationTransferInformation | PRESENCE optional } | +| { ID id-ServingCellMO | CRITICALITY ignore | TYPE ServingCellMO | PRESENCE optional } | +| { ID id-new-gNB-CU-UE-FLAP-ID | CRITICALITY reject | TYPE GNB-DU-UE-FLAP-ID | PRESENCE optional } | +| { ID id-RANUEID | CRITICALITY ignore | TYPE RANUEID | PRESENCE optional } | + +| | | | | +|-------------------------------------------------|--------------------|--------------------------------------------|---------------------| +| { ID id-TraceActivation | CRITICALITY ignore | TYPE TraceActivation | PRESENCE optional } | +| { ID id-AdditionalRRMPriorityIndex | CRITICALITY ignore | TYPE AdditionalRRMPriorityIndex | PRESENCE optional } | +| { ID id-BHChannels-ToBeSetup-List | CRITICALITY reject | TYPE BHChannels-ToBeSetup-List | PRESENCE optional } | +| { ID id-ConfiguredBAPAddress | CRITICALITY reject | TYPE BAPAddress | PRESENCE optional } | +| { ID id-NRV2XServicesAuthorized | CRITICALITY ignore | TYPE NRV2XServicesAuthorized | PRESENCE optional } | +| { ID id-LTEV2XServicesAuthorized | CRITICALITY ignore | TYPE LTEV2XServicesAuthorized | PRESENCE optional } | +| { ID id-NRUESidelinkAggregateMaximumBitrate | CRITICALITY ignore | TYPE NRUESidelinkAggregateMaximumBitrate | PRESENCE optional } | +| { ID id-LTEUESidelinkAggregateMaximumBitrate | CRITICALITY ignore | TYPE LTEUESidelinkAggregateMaximumBitrate | PRESENCE optional } | +| { ID id-PC5LinkAMBR | CRITICALITY ignore | TYPE BitRate | PRESENCE optional} | +| { ID id-SLDRBs-ToBeSetup-List | CRITICALITY reject | TYPE SLDRBs-ToBeSetup-List | PRESENCE optional } | +| { ID id-ConditionalInterDUMobilityInformation | CRITICALITY reject | TYPE ConditionalInterDUMobilityInformation | PRESENCE optional} | +| { ID id-ManagementBasedMDTPLMNList | CRITICALITY ignore | TYPE MDTPLMNList | PRESENCE optional } | +| { ID id-ServingNID | CRITICALITY reject | TYPE NID | PRESENCE optional } | +| { ID id-F1CTransferPath | CRITICALITY reject | TYPE F1CTransferPath | PRESENCE optional } | +| { ID id-F1CTransferPathNRDC | CRITICALITY reject | TYPE F1CTransferPathNRDC | PRESENCE optional } | +| { ID id-MDTPollutedMeasurementIndicator | CRITICALITY ignore | TYPE MDTPollutedMeasurementIndicator | PRESENCE optional } | +| { ID id-SCGActivationRequest | CRITICALITY ignore | TYPE SCGActivationRequest | PRESENCE optional } | +| { ID id-CG-SDTSessionInfoOld | CRITICALITY ignore | TYPE CG-SDTSessionInfo | PRESENCE optional } | +| { ID id-FiveG-ProSeAuthorized | CRITICALITY ignore | TYPE FiveG-ProSeAuthorized | PRESENCE optional } | +| { ID id-FiveG-ProSeUEPC5AggregateMaximumBitrate | CRITICALITY ignore | TYPE NRUESidelinkAggregateMaximumBitrate | PRESENCE optional } | +| { ID id-FiveG-ProSePC5LinkAMBR | CRITICALITY ignore | TYPE BitRate | PRESENCE optional} | +| { ID id-UuRLCChannelToBeSetupList | CRITICALITY reject | TYPE UuRLCChannelToBeSetupList | PRESENCE optional} | +| { ID id-PC5RLCChannelToBeSetupList | CRITICALITY reject | TYPE PC5RLCChannelToBeSetupList | PRESENCE optional} | +| { ID id-PathSwitchConfiguration | CRITICALITY ignore | TYPE PathSwitchConfiguration | PRESENCE optional } | + +``` + +{ ID id-GNBDUUESliceMaximumBitRateList CRITICALITY ignore TYPE GNBDUUESliceMaximumBitRateList PRESENCE optional }| +{ ID id-MulticastMBSSessionSetupList CRITICALITY reject TYPE MulticastMBSSessionList PRESENCE optional }| +{ ID id-UE-MulticastMRBs-ToBeSetup-List CRITICALITY reject TYPE UE-MulticastMRBs-ToBeSetup-List PRESENCE optional }| +{ ID id-ServingCellMO-List CRITICALITY ignore TYPE ServingCellMO-List PRESENCE optional }| +{ ID id-NetworkControlledRepeaterAuthorized CRITICALITY ignore TYPE NetworkControlledRepeaterAuthorized PRESENCE optional }| +{ ID id-SDT-Volume-Threshold CRITICALITY ignore TYPE SDT-Volume-Threshold PRESENCE optional }| +{ ID id-LTMInformation-Setup CRITICALITY reject TYPE LTMInformation-Setup PRESENCE optional }| +{ ID id-LTMConfigurationIDMappingList CRITICALITY reject TYPE LTMConfigurationIDMappingList PRESENCE optional }| +{ ID id-EarlySyncInformation-Request CRITICALITY ignore TYPE EarlySyncInformation-Request PRESENCE optional }| +{ ID id-Source-gNB-DU-ID CRITICALITY reject TYPE GNB-DU-ID PRESENCE optional }| +{ ID id-PathAdditionInformation CRITICALITY ignore TYPE PathAdditionInformation PRESENCE optional }| +{ ID id-NRA2XServicesAuthorized CRITICALITY ignore TYPE NRA2XServicesAuthorized PRESENCE optional }| +{ ID id-LTEA2XServicesAuthorized CRITICALITY ignore TYPE LTEA2XServicesAuthorized PRESENCE optional }| +{ ID id-NRUESidelinkAggregateMaximumBitrateForA2X CRITICALITY ignore TYPE NRUESidelinkAggregateMaximumBitrate PRESENCE optional }| +{ ID id-LTEUESidelinkAggregateMaximumBitrateForA2X CRITICALITY ignore TYPE LTEUESidelinkAggregateMaximumBitrate PRESENCE optional }, +... +} + +``` + +``` + +Candidate-SpCell-List ::= SEQUENCE (SIZE(1..maxnoofCandidateSpCells)) OF ProtocolIE-SingleContainer { { Candidate-SpCell-ItemIEs} } +SCell-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofSCells)) OF ProtocolIE-SingleContainer { { SCell-ToBeSetup-ItemIEs} } +SRBs-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofSRBs)) OF ProtocolIE-SingleContainer { { SRBs-ToBeSetup-ItemIEs} } +DRBs-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF ProtocolIE-SingleContainer { { DRBs-ToBeSetup-ItemIEs} } +BHChannels-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofBHRLCChannels)) OF ProtocolIE-SingleContainer { { BHChannels-ToBeSetup-ItemIEs} } +SLDRBs-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofSLDRBs)) OF ProtocolIE-SingleContainer { { SLDRBs-ToBeSetup-ItemIEs} } + +``` + +UE-MulticastMRBs-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofMRBsforUE)) OF ProtocolIE-SingleContainer { { UE-MulticastMRBs-ToBeSetup-ItemIEs} } + +ServingCellMO-List ::= SEQUENCE (SIZE(1..maxnoofServingCellMOs)) OF ProtocolIE-SingleContainer { { ServingCellMO-List-ItemIEs} } + +Candidate-SpCell-ItemIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-Candidate-SpCell-Item CRITICALITY ignore TYPE Candidate-SpCell-Item PRESENCE mandatory }, + +... + +} + +SCell-ToBeSetup-ItemIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-SCell-ToBeSetup-Item CRITICALITY ignore TYPE SCell-ToBeSetup-Item PRESENCE mandatory }, + +... + +} + +SRBs-ToBeSetup-ItemIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-SRBs-ToBeSetup-Item CRITICALITY reject TYPE SRBs-ToBeSetup-Item PRESENCE mandatory}, + +... + +} + +DRBs-ToBeSetup-ItemIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-DRBs-ToBeSetup-Item CRITICALITY reject TYPE DRBs-ToBeSetup-Item PRESENCE mandatory}, + +... + +} + +BHChannels-ToBeSetup-ItemIEs FLAP-PROTOCOL-IES ::= { + +``` + + { ID id-BHChannels-ToBeSetup-Item CRITICALITY reject TYPE BHChannels-ToBeSetup-Item PRESENCE mandatory}, + ... +} + +``` + +SLDRBs-ToBeSetup-ItemIEs FLAP-PROTOCOL-IES ::= { + +``` + + { ID id-SLDRBs-ToBeSetup-Item CRITICALITY reject TYPE SLDRBs-ToBeSetup-Item PRESENCE mandatory}, + ... +} + +``` + +UE-MulticastMRBs-ToBeSetup-ItemIEs FLAP-PROTOCOL-IES ::= { + +``` + + { ID id-UE-MulticastMRBs-ToBeSetup-Item CRITICALITY reject TYPE UE-MulticastMRBs-ToBeSetup-Item PRESENCE mandatory}, + ... +} + +``` + +ServingCellMO-List-ItemIEs FLAP-PROTOCOL-IES ::= { + +``` + + { ID id-ServingCellMO-List-Item CRITICALITY reject TYPE ServingCellMO-List-Item PRESENCE mandatory}, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- UE CONTEXT SETUP RESPONSE + +-- + +-- \*\*\*\*\* + +UEContextSetupResponse ::= SEQUENCE { + +    protocolIEs          ProtocolIE-Container    { { UEContextSetupResponseIEs } }, + +    ... + +} + +UEContextSetupResponseIEs FLAP-PROTOCOL-IES ::= { + +| | | | | +|-----------------------------------------------|--------------------|--------------------------------------------|----------------------| +| { ID id-gNB-CU-UE-FLAP-ID | CRITICALITY reject | TYPE GNB-CU-UE-FLAP-ID | PRESENCE mandatory } | +| { ID id-gNB-DU-UE-FLAP-ID | CRITICALITY reject | TYPE GNB-DU-UE-FLAP-ID | PRESENCE mandatory } | +| { ID id-DUtoCURRCInformation | CRITICALITY reject | TYPE DUtoCURRCInformation | PRESENCE mandatory } | +| { ID id-C-RNTI | CRITICALITY ignore | TYPE C-RNTI | PRESENCE optional } | +| { ID id-ResourceCoordinationTransferContainer | CRITICALITY ignore | TYPE ResourceCoordinationTransferContainer | PRESENCE optional } | +| { ID id-FullConfiguration | CRITICALITY reject | TYPE FullConfiguration | PRESENCE optional } | +| { ID id-DRBs-Setup-List | CRITICALITY ignore | TYPE DRBs-Setup-List | PRESENCE optional } | +| { ID id-SRBs-FailedToBeSetup-List | CRITICALITY ignore | TYPE SRBs-FailedToBeSetup-List | PRESENCE optional } | +| { ID id-DRBs-FailedToBeSetup-List | CRITICALITY ignore | TYPE DRBs-FailedToBeSetup-List | PRESENCE optional } | +| { ID id-SCell-FailedtoSetup-List | CRITICALITY ignore | TYPE SCell-FailedtoSetup-List | PRESENCE optional } | +| { ID id-InactivityMonitoringResponse | CRITICALITY reject | TYPE InactivityMonitoringResponse | PRESENCE optional } | +| { ID id-CriticalityDiagnostics | CRITICALITY ignore | TYPE CriticalityDiagnostics | PRESENCE optional } | +| { ID id-SRBs-Setup-List | CRITICALITY ignore | TYPE SRBs-Setup-List | PRESENCE optional } | +| { ID id-BHChannels-Setup-List | CRITICALITY ignore | TYPE BHChannels-Setup-List | PRESENCE optional } | +| { ID id-BHChannels-FailedToBeSetup-List | CRITICALITY ignore | TYPE BHChannels-FailedToBeSetup-List | PRESENCE optional } | +| { ID id-SLDRBs-Setup-List | CRITICALITY ignore | TYPE SLDRBs-Setup-List | PRESENCE optional } | + +``` + + { ID id-SLDRBs-FailedToBeSetup-List CRITICALITY ignore TYPE SLDRBs-FailedToBeSetup-List PRESENCE optional }| + { ID id-requestedTargetCellGlobalID CRITICALITY reject TYPE NRCGI PRESENCE optional}| + { ID id-SCGActivationStatus CRITICALITY ignore TYPE SCGActivationStatus PRESENCE optional }| + { ID id-UuRLCChannelSetupList CRITICALITY ignore TYPE UuRLCChannelSetupList PRESENCE optional}| + { ID id-UuRLCChannelFailedToBeSetupList CRITICALITY ignore TYPE UuRLCChannelFailedToBeSetupList PRESENCE optional}| + { ID id-PC5RLCChannelSetupList CRITICALITY ignore TYPE PC5RLCChannelSetupList PRESENCE optional}| + { ID id-PC5RLCChannelFailedToBeSetupList CRITICALITY ignore TYPE PC5RLCChannelFailedToBeSetupList PRESENCE optional}| + { ID id-ServingCellMO-encoded-in-CGC-List CRITICALITY ignore TYPE ServingCellMO-encoded-in-CGC-List PRESENCE optional}| + { ID id-UE-MulticastMRBs-Setupnew-List CRITICALITY reject TYPE UE-MulticastMRBs-Setupnew-List PRESENCE optional}| + { ID id-DedicatedSIDeliveryIndication CRITICALITY ignore TYPE DedicatedSIDeliveryIndication PRESENCE optional}| + { ID id-Configured-BWP-List CRITICALITY ignore TYPE Configured-BWP-List PRESENCE optional}| + { ID id-EarlySyncInformation CRITICALITY ignore TYPE EarlySyncInformation PRESENCE optional }| + { ID id-LTMConfiguration CRITICALITY ignore TYPE LTMConfiguration PRESENCE optional }, + ... +} + +``` + +``` + +DRBs-Setup-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF ProtocolIE-SingleContainer { { DRBs-Setup-ItemIEs} } + +``` + +``` + +SRBs-FailedToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofSRBs)) OF ProtocolIE-SingleContainer { { SRBs-FailedToBeSetup-ItemIEs} } + +``` + +``` + +DRBs-FailedToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF ProtocolIE-SingleContainer { { DRBs-FailedToBeSetup-ItemIEs} } + +``` + +``` + +SCell-FailedtoSetup-List ::= SEQUENCE (SIZE(1..maxnoofSCells)) OF ProtocolIE-SingleContainer { { SCell-FailedtoSetup-ItemIEs} } + +``` + +``` + +SRBs-Setup-List ::= SEQUENCE (SIZE(1..maxnoofSRBs)) OF ProtocolIE-SingleContainer { { SRBs-Setup-ItemIEs} } + +``` + +``` + +BHChannels-Setup-List ::= SEQUENCE (SIZE(1..maxnoofBHRLCChannels)) OF ProtocolIE-SingleContainer { { BHChannels-Setup-ItemIEs} } + +``` + +``` +BHChannels-FailedToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofBHRLCChannels)) OF ProtocolIE-SingleContainer { { BHChannels-FailedToBeSetup-ItemIEs } } +``` + +``` +DRBs-Setup-ItemIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-DRBs-Setup-Item CRITICALITY ignore TYPE DRBs-Setup-Item PRESENCE mandatory}, + ... +} +``` + +``` +SRBs-Setup-ItemIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-SRBs-Setup-Item CRITICALITY ignore TYPE SRBs-Setup-Item PRESENCE mandatory}, + ... +} +``` + +``` +SRBs-FailedToBeSetup-ItemIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-SRBs-FailedToBeSetup-Item CRITICALITY ignore TYPE SRBs-FailedToBeSetup-Item PRESENCE mandatory}, + ... +} +``` + +``` +DRBs-FailedToBeSetup-ItemIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-DRBs-FailedToBeSetup-Item CRITICALITY ignore TYPE DRBs-FailedToBeSetup-Item PRESENCE mandatory}, + ... +} +``` + +``` +SCell-FailedtoSetup-ItemIEs FLAP-PROTOCOL-IES ::= { +``` + +``` +{ ID id-SCell-FailedtoSetup-Item CRITICALITY ignore TYPE SCell-FailedtoSetup-Item PRESENCE mandatory}, +... +} + +BHChannels-Setup-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-BHChannels-Setup-Item CRITICALITY ignore TYPE BHChannels-Setup-Item PRESENCE mandatory}, + ... +} + +BHChannels-FailedToBeSetup-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-BHChannels-FailedToBeSetup-Item CRITICALITY ignore TYPE BHChannels-FailedToBeSetup-Item PRESENCE mandatory}, + ... +} + +SLDRBs-Setup-List ::= SEQUENCE (SIZE(1..maxnoofSLDRBs)) OF ProtocolIE-SingleContainer { { SLDRBs-Setup-ItemIEs} } + +SLDRBs-FailedToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofSLDRBs)) OF ProtocolIE-SingleContainer { { SLDRBs-FailedToBeSetup-ItemIEs} } + +SLDRBs-Setup-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-SLDRBs-Setup-Item CRITICALITY ignore TYPE SLDRBs-Setup-Item PRESENCE mandatory}, + ... +} + +SLDRBs-FailedToBeSetup-ItemIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + + { ID id-SLDRBs-FailedToBeSetup-Item CRITICALITY ignore TYPE SLDRBs-FailedToBeSetup-Item PRESENCE mandatory}, + ... +} + +UE-MulticastMRBs-Setupnew-List ::= SEQUENCE (SIZE(1..maxnoofMRBsforUE)) OF ProtocolIE-SingleContainer { { UE-MulticastMRBs-Setupnew-ItemIEs } } + +UE-MulticastMRBs-Setupnew-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-UE-MulticastMRBs-Setupnew-Item CRITICALITY reject TYPE UE-MulticastMRBs-Setupnew-Item PRESENCE mandatory}, + ... +} + +``` + +``` + +-- ***** +-- +-- UE CONTEXT SETUP FAILURE +-- +-- ***** + +``` + +``` + +UEContextSetupFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { UEContextSetupFailureIEs} }, + ... +} + +``` + +``` + +UEContextSetupFailureIEs FLAP-PROTOCOL-IES ::= { + +``` + +``` + + { ID id-gNB-CU-UE-F1AP-ID CRITICALITY reject TYPE GNB-CU-UE-F1AP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-F1AP-ID CRITICALITY ignore TYPE GNB-DU-UE-F1AP-ID PRESENCE optional }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + { ID id-Potential-SpCell-List CRITICALITY ignore TYPE Potential-SpCell-List PRESENCE optional }| + { ID id-requestedTargetCellGlobalID CRITICALITY reject TYPE NRCGI PRESENCE optional}, + ... +} + +``` + +``` +Potential-SpCell-List ::= SEQUENCE (SIZE(0..maxnoofPotentialSpCells)) OF ProtocolIE-SingleContainer { { Potential-SpCell-ItemIEs } } +``` + +``` + +Potential-SpCell-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-Potential-SpCell-Item CRITICALITY ignore TYPE Potential-SpCell-Item PRESENCE mandatory }, + ... +} + +``` + +``` +-- ***** +``` + +``` +-- +-- UE Context Release Request ELEMENTARY PROCEDURE +``` + +``` +-- +-- ***** +``` + +``` +-- +-- ***** +``` + +-- UE Context Release Request + +-- + +-- \*\*\*\*\* + +``` + +UEContextReleaseRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ UEContextReleaseRequestIEs}}, + ... +} + +``` + +``` + +UEContextReleaseRequestIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-targetCellsToCancel CRITICALITY reject TYPE TargetCellList PRESENCE optional }| + { ID id-LTMCells-ToBeReleased-List CRITICALITY ignore TYPE LTMCells-ToBeReleased-List PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- UE Context Release (gNB-CU initiated) ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +``` + +-- ***** +-- +-- UE CONTEXT RELEASE COMMAND +-- +-- ***** + +``` + +``` + +UEContextReleaseCommand ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { UEContextReleaseCommandIEs } }, + ... +} + +``` + +``` + +UEContextReleaseCommandIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-RRContainer CRITICALITY ignore TYPE RRContainer PRESENCE optional }| + { ID id-SRBID CRITICALITY ignore TYPE SRBID PRESENCE conditional }| + { ID id-oldgNB-DU-UE-FlAP-ID CRITICALITY ignore TYPE GNB-DU-UE-FlAP-ID PRESENCE optional }| + { ID id-ExecuteDuplication CRITICALITY ignore TYPE ExecuteDuplication PRESENCE optional }| + { ID id-RRDeliveryStatusRequest CRITICALITY ignore TYPE RRDeliveryStatusRequest PRESENCE optional }| + { ID id-targetCellsToCancel CRITICALITY reject TYPE TargetCellList PRESENCE optional }| + { ID id-PosConextRevIndication CRITICALITY reject TYPE PosConextRevIndication PRESENCE optional }| + { ID id-CG-SDTKeptIndicator CRITICALITY ignore TYPE CG-SDTKeptIndicator PRESENCE optional }| +} + +``` + +``` +{ ID id-LTMCells-ToBeReleased-List CRITICALITY ignore TYPE LTMCells-ToBeReleased-List PRESENCE optional }, +... +} + +-- ***** +-- +-- UE CONTEXT RELEASE COMPLETE +-- +-- ***** + +UEContextReleaseComplete ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { UEContextReleaseCompleteIEs } }, + ... +} + +UEContextReleaseCompleteIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory } | + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } | + { ID id-Recommended-SSBs-for-Paging-List CRITICALITY ignore TYPE Recommended-SSBs-for-Paging-List PRESENCE optional }, + ... +} +``` + +``` + +-- ***** +-- +-- UE Context Modification ELEMENTARY PROCEDURE +-- +-- ***** + +-- ***** +-- +-- UE CONTEXT MODIFICATION REQUEST +-- +-- ***** + +``` + +``` + +UEContextModificationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { UEContextModificationRequestIEs } }, + ... +} + +``` + +``` + +UEContextModificationRequestIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory } | + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory } | + { ID id-SpCell-ID CRITICALITY ignore TYPE NRCGI PRESENCE optional } | + { ID id-ServCellIndex CRITICALITY reject TYPE ServCellIndex PRESENCE optional } | + { ID id-SpCellULConfigured CRITICALITY ignore TYPE CellULConfigured PRESENCE optional } | + { ID id-DRXCycle CRITICALITY ignore TYPE DRXCycle PRESENCE optional } | +} + +``` + +| | | | | +|-------------------------------------------------|--------------------|----------------------------------------------|---------------------| +| { ID id-CUtoDURRCInformation | CRITICALITY reject | TYPE CUtoDURRCInformation | PRESENCE optional } | +| { ID id-TransmissionActionIndicator | CRITICALITY ignore | TYPE TransmissionActionIndicator | PRESENCE optional } | +| { ID id-ResourceCoordinationTransferContainer | CRITICALITY ignore | TYPE ResourceCoordinationTransferContainer | PRESENCE optional } | +| { ID id-RRCReconfigurationCompleteIndicator | CRITICALITY ignore | TYPE RRCReconfigurationCompleteIndicator | PRESENCE optional } | +| { ID id-RRCContainer | CRITICALITY reject | TYPE RRCContainer | PRESENCE optional } | +| { ID id-SCell-ToBeSetupMod-List | CRITICALITY ignore | TYPE SCell-ToBeSetupMod-List | PRESENCE optional } | +| { ID id-SCell-ToBeRemoved-List | CRITICALITY ignore | TYPE SCell-ToBeRemoved-List | PRESENCE optional } | +| { ID id-SRBs-ToBeSetupMod-List | CRITICALITY reject | TYPE SRBs-ToBeSetupMod-List | PRESENCE optional } | +| { ID id-DRBs-ToBeSetupMod-List | CRITICALITY reject | TYPE DRBs-ToBeSetupMod-List | PRESENCE optional } | +| { ID id-DRBs-ToBeModified-List | CRITICALITY reject | TYPE DRBs-ToBeModified-List | PRESENCE optional } | +| { ID id-SRBs-ToBeReleased-List | CRITICALITY reject | TYPE SRBs-ToBeReleased-List | PRESENCE optional } | +| { ID id-DRBs-ToBeReleased-List | CRITICALITY reject | TYPE DRBs-ToBeReleased-List | PRESENCE optional } | +| { ID id-InactivityMonitoringRequest | CRITICALITY reject | TYPE InactivityMonitoringRequest | PRESENCE optional } | +| { ID id-RAT-FrequencyPriorityInformation | CRITICALITY reject | TYPE RAT-FrequencyPriorityInformation | PRESENCE optional } | +| { ID id-DRXConfigurationIndicator | CRITICALITY ignore | TYPE DRXConfigurationIndicator | PRESENCE optional } | +| { ID id-RLCFailureIndication | CRITICALITY ignore | TYPE RLCFailureIndication | PRESENCE optional } | +| { ID id-UplinkTxDirectCurrentListInformation | CRITICALITY ignore | TYPE UplinkTxDirectCurrentListInformation | PRESENCE optional } | +| { ID id-GNB-DUConfigurationQuery | CRITICALITY reject | TYPE GNB-DUConfigurationQuery | PRESENCE optional } | +| { ID id-GNB-DU-UE-AMBR-UL | CRITICALITY ignore | TYPE BitRate | PRESENCE optional } | +| { ID id-ExecuteDuplication | CRITICALITY ignore | TYPE ExecuteDuplication | PRESENCE optional} | +| { ID id-RRCDeliveryStatusRequest | CRITICALITY ignore | TYPE RRCDeliveryStatusRequest | PRESENCE optional } | +| { ID id-ResourceCoordinationTransferInformation | CRITICALITY ignore | TYPE ResourceCoordinationTransferInformation | PRESENCE optional } | +| { ID id-ServingCellMO | CRITICALITY ignore | TYPE ServingCellMO | PRESENCE optional } | +| { ID id-NeedforGap | CRITICALITY ignore | TYPE NeedforGap | PRESENCE optional } | + +``` + +{ ID id-FullConfiguration CRITICALITY reject TYPE FullConfiguration PRESENCE optional }| +{ ID id-AdditionalRRMPriorityIndex CRITICALITY ignore TYPE AdditionalRRMPriorityIndex PRESENCE optional }| +{ ID id-LowerLayerPresenceStatusChange CRITICALITY ignore TYPE LowerLayerPresenceStatusChange PRESENCE optional }| +{ ID id-BHChannels-ToBeSetupMod-List CRITICALITY reject TYPE BHChannels-ToBeSetupMod-List PRESENCE optional }| +{ ID id-BHChannels-ToBeModified-List CRITICALITY reject TYPE BHChannels-ToBeModified-List PRESENCE optional }| +{ ID id-BHChannels-ToBeReleased-List CRITICALITY reject TYPE BHChannels-ToBeReleased-List PRESENCE optional }| +{ ID id-NRV2XServicesAuthorized CRITICALITY ignore TYPE NRV2XServicesAuthorized PRESENCE optional }| +{ ID id-LTEV2XServicesAuthorized CRITICALITY ignore TYPE LTEV2XServicesAuthorized PRESENCE optional }| +{ ID id-NRUESidelinkAggregateMaximumBitrate CRITICALITY ignore TYPE NRUESidelinkAggregateMaximumBitrate PRESENCE optional }| +{ ID id-LTEUESidelinkAggregateMaximumBitrate CRITICALITY ignore TYPE LTEUESidelinkAggregateMaximumBitrate PRESENCE optional }| +{ ID id-PC5LinkAMBR CRITICALITY ignore TYPE BitRate PRESENCE optional}| +{ ID id-SLDRBs-ToBeSetupMod-List CRITICALITY reject TYPE SLDRBs-ToBeSetupMod-List PRESENCE optional }| +{ ID id-SLDRBs-ToBeModified-List CRITICALITY reject TYPE SLDRBs-ToBeModified-List PRESENCE optional }| +{ ID id-SLDRBs-ToBeReleased-List CRITICALITY reject TYPE SLDRBs-ToBeReleased-List PRESENCE optional }| +{ ID id-ConditionalIntraDUMobilityInformation CRITICALITY reject TYPE ConditionalIntraDUMobilityInformation PRESENCE optional}| +{ ID id-F1CTransferPath CRITICALITY reject TYPE F1CTransferPath PRESENCE optional }| +{ ID id-SCGIndicator CRITICALITY ignore TYPE SCGIndicator PRESENCE optional }| + +{ ID id-UplinkTxDirectCurrentTwoCarrierListInfo CRITICALITY ignore TYPE UplinkTxDirectCurrentTwoCarrierListInfo PRESENCE optional }| + +{ ID id-IABConditionalRRCMessagedeliveryIndication CRITICALITY reject TYPE IABConditionalRRCMessagedeliveryIndication + PRESENCE optional }| + +{ ID id-F1CTransferPathNRDC CRITICALITY reject TYPE F1CTransferPathNRDC PRESENCE optional }| +{ ID id-MDTPollutedMeasurementIndicator CRITICALITY ignore TYPE MDTPollutedMeasurementIndicator PRESENCE optional }| +{ ID id-SCGActivationRequest CRITICALITY ignore TYPE SCGActivationRequest PRESENCE optional }| +{ ID id-CG-SDTQueryIndication CRITICALITY ignore TYPE CG-SDTQueryIndication PRESENCE optional }| +{ ID id-FiveG-ProSeAuthorized CRITICALITY ignore TYPE FiveG-ProSeAuthorized PRESENCE optional }| + +``` + +``` + +{ ID id-FiveG-ProSeUEPC5AggregateMaximumBitrate CRITICALITY ignore TYPE NRUESidelinkAggregateMaximumBitrate PRESENCE optional }| +{ ID id-FiveG-ProSePC5LinkAMBR CRITICALITY ignore TYPE BitRate PRESENCE optional }| +{ ID id-UpdatedRemoteUELocalID CRITICALITY ignore TYPE RemoteUELocalID PRESENCE optional }| +{ ID id-UuRLCChannelToBeSetupList CRITICALITY reject TYPE UuRLCChannelToBeSetupList PRESENCE optional }| +{ ID id-UuRLCChannelToBeModifiedList CRITICALITY reject TYPE UuRLCChannelToBeModifiedList PRESENCE optional }| +{ ID id-UuRLCChannelToBeReleasedList CRITICALITY reject TYPE UuRLCChannelToBeReleasedList PRESENCE optional }| +{ ID id-PC5RLCChannelToBeSetupList CRITICALITY reject TYPE PC5RLCChannelToBeSetupList PRESENCE optional }| +{ ID id-PC5RLCChannelToBeModifiedList CRITICALITY reject TYPE PC5RLCChannelToBeModifiedList PRESENCE optional }| +{ ID id-PC5RLCChannelToBeReleasedList CRITICALITY reject TYPE PC5RLCChannelToBeReleasedList PRESENCE optional }| +{ ID id-PathSwitchConfiguration CRITICALITY ignore TYPE PathSwitchConfiguration PRESENCE optional }| +{ ID id-GNBDUUESliceMaximumBitRateList CRITICALITY ignore TYPE GNBDUUESliceMaximumBitRateList PRESENCE optional }| +{ ID id-MulticastMBSSessionSetupList CRITICALITY reject TYPE MulticastMBSSessionList PRESENCE optional }| +{ ID id-MulticastMBSSessionRemoveList CRITICALITY reject TYPE MulticastMBSSessionList PRESENCE optional }| +{ ID id-UE-MulticastMRBs-ToBeSetup-atModify-List CRITICALITY reject TYPE UE-MulticastMRBs-ToBeSetup-atModify-List PRESENCE optional }| +{ ID id-UE-MulticastMRBs-ToBeReleased-List CRITICALITY reject TYPE UE-MulticastMRBs-ToBeReleased-List PRESENCE optional }| +{ ID id-SLDRXCycleList CRITICALITY ignore TYPE SLDRXCycleList PRESENCE optional }| +{ ID id-ManagementBasedMDTPLMNModificationList CRITICALITY ignore TYPE MDTPLMNModificationList PRESENCE optional }| +{ ID id-SDTBearerConfigurationQueryIndication CRITICALITY ignore TYPE SDTBearerConfigurationQueryIndication PRESENCE optional }| +{ ID id-DAPS-HO-Status CRITICALITY ignore TYPE DAPS-HO-Status PRESENCE optional }| +{ ID id-ServingCellMO-List CRITICALITY ignore TYPE ServingCellMO-List PRESENCE optional }| +{ ID id-ULTxDirectCurrentMoreCarrierInformation CRITICALITY ignore TYPE ULTxDirectCurrentMoreCarrierInformation PRESENCE optional }| +{ ID id-CPACMCGInformation CRITICALITY ignore TYPE CPACMCGInformation PRESENCE optional }| +{ ID id-NetworkControlledRepeaterAuthorized CRITICALITY ignore TYPE NetworkControlledRepeaterAuthorized PRESENCE optional }| +{ ID id-SDT-Volume-Threshold CRITICALITY ignore TYPE SDT-Volume-Threshold PRESENCE +optional }| + +``` + +``` + + { ID id-LTMInformation-Modify CRITICALITY reject TYPE LTMInformation-Modify PRESENCE optional }| + { ID id-LTMConfigurationIDMappingList CRITICALITY reject TYPE LTMConfigurationIDMappingList PRESENCE optional }| + { ID id-EarlySyncInformation-Request CRITICALITY ignore TYPE EarlySyncInformation-Request PRESENCE optional }| + { ID id-EarlySyncInformation-List CRITICALITY ignore TYPE EarlySyncInformation-List PRESENCE optional }| + { ID id-LTMCells-ToBeReleased-List CRITICALITY ignore TYPE LTMCells-ToBeReleased-List PRESENCE optional }| + { ID id-PathAdditionInformation CRITICALITY ignore TYPE PathAdditionInformation PRESENCE optional }| + { ID id-NRA2XServicesAuthorized CRITICALITY ignore TYPE NRA2XServicesAuthorized PRESENCE optional }| + { ID id-LTEA2XServicesAuthorized CRITICALITY ignore TYPE LTEA2XServicesAuthorized PRESENCE optional }| + { ID id-NRUESidelinkAggregateMaximumBitrateForA2X CRITICALITY ignore TYPE NRUESidelinkAggregateMaximumBitrate PRESENCE optional }| + { ID id-LTEUESidelinkAggregateMaximumBitrateForA2X CRITICALITY ignore TYPE LTEUESidelinkAggregateMaximumBitrate PRESENCE optional }, + ... +} + +``` + +``` + +SCell-ToBeSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofSCells)) OF ProtocolIE-SingleContainer { { SCell-ToBeSetupMod-ItemIEs} } +SCell-ToBeRemoved-List ::= SEQUENCE (SIZE(1..maxnoofSCells)) OF ProtocolIE-SingleContainer { { SCell-ToBeRemoved-ItemIEs} } +SRBs-ToBeSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofSRBs)) OF ProtocolIE-SingleContainer { { SRBs-ToBeSetupMod-ItemIEs} } +DRBs-ToBeSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF ProtocolIE-SingleContainer { { DRBs-ToBeSetupMod-ItemIEs} } +BHChannels-ToBeSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofBHRLCChannels)) OF ProtocolIE-SingleContainer { { BHChannels-ToBeSetupMod-ItemIEs} } + +DRBs-ToBeModified-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF ProtocolIE-SingleContainer { { DRBs-ToBeModified-ItemIEs} } +BHChannels-ToBeModified-List ::= SEQUENCE (SIZE(1..maxnoofBHRLCChannels)) OF ProtocolIE-SingleContainer { { BHChannels-ToBeModified-ItemIEs} } +SRBs-ToBeReleased-List ::= SEQUENCE (SIZE(1..maxnoofSRBs)) OF ProtocolIE-SingleContainer { { SRBs-ToBeReleased-ItemIEs} } +DRBs-ToBeReleased-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF ProtocolIE-SingleContainer { { DRBs-ToBeReleased-ItemIEs} } +BHChannels-ToBeReleased-List ::= SEQUENCE (SIZE(1..maxnoofBHRLCChannels)) OF ProtocolIE-SingleContainer { { BHChannels-ToBeReleased-ItemIEs} } + +``` + +``` +UE-MulticastMRBs-ToBeSetup-atModify-List ::= SEQUENCE (SIZE(1..maxnoofMRBsforUE)) OF + ProtocolIE-SingleContainer { { UE-MulticastMRBs-ToBeSetup-atModify-ItemIEs} } + +UE-MulticastMRBs-ToBeReleased-List ::= SEQUENCE (SIZE(1..maxnoofMRBsforUE)) OF ProtocolIE-SingleContainer { { UE-MulticastMRBs-ToBeReleased-ItemIEs} } + +SCell-ToBeSetupMod-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-SCell-ToBeSetupMod-Item CRITICALITY ignore TYPE SCell-ToBeSetupMod-Item PRESENCE mandatory }, + ... +} + +SCell-ToBeRemoved-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-SCell-ToBeRemoved-Item CRITICALITY ignore TYPE SCell-ToBeRemoved-Item PRESENCE mandatory }, + ... +} + +SRBs-ToBeSetupMod-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-SRBs-ToBeSetupMod-Item CRITICALITY reject TYPE SRBs-ToBeSetupMod-Item PRESENCE mandatory}, + ... +} + +DRBs-ToBeSetupMod-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-DRBs-ToBeSetupMod-Item CRITICALITY reject TYPE DRBs-ToBeSetupMod-Item PRESENCE mandatory}, +``` + +``` + ... +} + +DRBs-ToBeModified-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-DRBs-ToBeModified-Item CRITICALITY reject TYPE DRBs-ToBeModified-Item PRESENCE mandatory}, + ... +} + +SRBs-ToBeReleased-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-SRBs-ToBeReleased-Item CRITICALITY reject TYPE SRBs-ToBeReleased-Item PRESENCE mandatory}, + ... +} + +DRBs-ToBeReleased-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-DRBs-ToBeReleased-Item CRITICALITY reject TYPE DRBs-ToBeReleased-Item PRESENCE mandatory}, + ... +} + +BHChannels-ToBeSetupMod-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-BHChannels-ToBeSetupMod-Item CRITICALITY reject TYPE BHChannels-ToBeSetupMod-Item PRESENCE mandatory}, + ... +} +``` + +``` +BHChannels-ToBeModified-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-BHChannels-ToBeModified-Item CRITICALITY reject TYPE BHChannels-ToBeModified-Item PRESENCE mandatory}, + ... +} + +BHChannels-ToBeReleased-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-BHChannels-ToBeReleased-Item CRITICALITY reject TYPE BHChannels-ToBeReleased-Item PRESENCE mandatory}, + ... +} + +SLDRBs-ToBeSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofSLDRBs)) OF ProtocolIE-SingleContainer { { SLDRBs-ToBeSetupMod-ItemIEs } } +SLDRBs-ToBeModified-List ::= SEQUENCE (SIZE(1..maxnoofSLDRBs)) OF ProtocolIE-SingleContainer { { SLDRBs-ToBeModified-ItemIEs } } +SLDRBs-ToBeReleased-List ::= SEQUENCE (SIZE(1..maxnoofSLDRBs)) OF ProtocolIE-SingleContainer { { SLDRBs-ToBeReleased-ItemIEs } } + +SLDRBs-ToBeSetupMod-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-SLDRBs-ToBeSetupMod-Item CRITICALITY reject TYPE SLDRBs-ToBeSetupMod-Item PRESENCE mandatory}, + ... +} + +SLDRBs-ToBeModified-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-SLDRBs-ToBeModified-Item CRITICALITY reject TYPE SLDRBs-ToBeModified-Item PRESENCE mandatory}, + ... +} +``` + +SLDRBs-ToBeReleased-ItemIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-SLDRBs-ToBeReleased-Item CRITICALITY reject TYPE SLDRBs-ToBeReleased-Item PRESENCE mandatory}, + +... + +} + +UE-MulticastMRBs-ToBeSetup-atModify-ItemIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-UE-MulticastMRBs-ToBeSetup-atModify-Item CRITICALITY reject TYPE UE-MulticastMRBs-ToBeSetup-atModify-Item PRESENCE mandatory}, + +... + +} + +UE-MulticastMRBs-ToBeReleased-ItemIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-UE-MulticastMRBs-ToBeReleased-Item CRITICALITY reject TYPE UE-MulticastMRBs-ToBeReleased-Item PRESENCE mandatory}, + +... + +} + +-- \*\*\*\*\* + +-- + +-- UE CONTEXT MODIFICATION RESPONSE + +-- + +-- \*\*\*\*\* + +UEContextModificationResponse ::= SEQUENCE { + +protocolIEs ProtocolIE-Container { { UEContextModificationResponseIEs } }, + +... + } + +``` + +UEContextModificationResponseIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FLAP-ID CRITICALITY reject TYPE GNB-CU-UE-FLAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FLAP-ID CRITICALITY reject TYPE GNB-DU-UE-FLAP-ID PRESENCE mandatory }| + { ID id-ResourceCoordinationTransferContainer CRITICALITY ignore TYPE ResourceCoordinationTransferContainer PRESENCE optional }| + { ID id-DUtoCURRCInformation CRITICALITY reject TYPE DUtoCURRCInformation PRESENCE optional}| + { ID id-DRBs-SetupMod-List CRITICALITY ignore TYPE DRBs-SetupMod-List PRESENCE optional}| + { ID id-DRBs-Modified-List CRITICALITY ignore TYPE DRBs-Modified-List PRESENCE optional}| + { ID id-SRBs-FailedToBeSetupMod-List CRITICALITY ignore TYPE SRBs-FailedToBeSetupMod-List PRESENCE optional }| + { ID id-DRBs-FailedToBeSetupMod-List CRITICALITY ignore TYPE DRBs-FailedToBeSetupMod-List PRESENCE optional }| + { ID id-SCell-FailedtoSetupMod-List CRITICALITY ignore TYPE SCell-FailedtoSetupMod-List PRESENCE optional }| + { ID id-DRBs-FailedToBeModified-List CRITICALITY ignore TYPE DRBs-FailedToBeModified-List PRESENCE optional }| + { ID id-InactivityMonitoringResponse CRITICALITY reject TYPE InactivityMonitoringResponse PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + { ID id-C-RNTI CRITICALITY ignore TYPE C-RNTI PRESENCE optional }| + { ID id-Associated-SCell-List CRITICALITY ignore TYPE Associated-SCell-List PRESENCE optional }| + { ID id-SRBs-SetupMod-List CRITICALITY ignore TYPE SRBs-SetupMod-List PRESENCE optional }| + { ID id-SRBs-Modified-List CRITICALITY ignore TYPE SRBs-Modified-List PRESENCE optional }| + { ID id-FullConfiguration CRITICALITY reject TYPE FullConfiguration PRESENCE optional }| + { ID id-BHChannels-SetupMod-List CRITICALITY ignore TYPE BHChannels-SetupMod-List PRESENCE optional}| + { ID id-BHChannels-Modified-List CRITICALITY ignore TYPE BHChannels-Modified-List PRESENCE optional}| +} + +``` + +``` + +{ ID id-BHChannels-FailedToBeSetupMod-List CRITICALITY ignore TYPE BHChannels-FailedToBeSetupMod-List PRESENCE optional }| +{ ID id-BHChannels-FailedToBeModified-List CRITICALITY ignore TYPE BHChannels-FailedToBeModified-List PRESENCE optional }| +{ ID id-SLDRBs-SetupMod-List CRITICALITY ignore TYPE SLDRBs-SetupMod-List PRESENCE optional }| +{ ID id-SLDRBs-Modified-List CRITICALITY ignore TYPE SLDRBs-Modified-List PRESENCE optional }| +{ ID id-SLDRBs-FailedToBeSetupMod-List CRITICALITY ignore TYPE SLDRBs-FailedToBeSetupMod-List PRESENCE optional }| +{ ID id-SLDRBs-FailedToBeModified-List CRITICALITY ignore TYPE SLDRBs-FailedToBeModified-List PRESENCE optional }| +{ ID id-requestedTargetCellGlobalID CRITICALITY reject TYPE NRCGI PRESENCE optional}| +{ ID id-SCGActivationStatus CRITICALITY ignore TYPE SCGActivationStatus PRESENCE optional }| +{ ID id-UuRLCChannelSetupList CRITICALITY ignore TYPE UuRLCChannelSetupList PRESENCE optional}| +{ ID id-UuRLCChannelFailedToBeSetupList CRITICALITY ignore TYPE UuRLCChannelFailedToBeSetupList PRESENCE optional}| +{ ID id-UuRLCChannelModifiedList CRITICALITY ignore TYPE UuRLCChannelModifiedList PRESENCE optional}| +{ ID id-UuRLCChannelFailedToBeModifiedList CRITICALITY ignore TYPE UuRLCChannelFailedToBeModifiedList PRESENCE optional}| +{ ID id-PC5RLCChannelSetupList CRITICALITY ignore TYPE PC5RLCChannelSetupList PRESENCE optional}| +{ ID id-PC5RLCChannelFailedToBeSetupList CRITICALITY ignore TYPE PC5RLCChannelFailedToBeSetupList PRESENCE optional}| +{ ID id-PC5RLCChannelModifiedList CRITICALITY ignore TYPE PC5RLCChannelModifiedList PRESENCE optional}| +{ ID id-PC5RLCChannelFailedToBeModifiedList CRITICALITY ignore TYPE PC5RLCChannelFailedToBeModifiedList PRESENCE optional}| +{ ID id-SDTBearerConfigurationInfo CRITICALITY ignore TYPE SDTBearerConfigurationInfo PRESENCE optional}| +{ ID id-UE-MulticastMRBs-Setup-List CRITICALITY reject TYPE UE-MulticastMRBs-Setup-List PRESENCE optional}| +{ ID id-ServingCellMO-encoded-in-CGC-List CRITICALITY ignore TYPE ServingCellMO-encoded-in-CGC-List PRESENCE optional}| +{ ID id-DedicatedSIDeliveryIndication CRITICALITY ignore TYPE DedicatedSIDeliveryIndication PRESENCE optional}| +{ ID id-Configured-BWP-List CRITICALITY ignore TYPE Configured-BWP-List PRESENCE optional}| +{ ID id-EarlySyncInformation CRITICALITY ignore TYPE EarlySyncInformation PRESENCE optional}| +{ ID id-LTMConfiguration CRITICALITY ignore TYPE LTMConfiguration PRESENCE optional}, +... +} + +``` + +``` +DRBs-SetupMod-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF ProtocolIE-SingleContainer { { DRBs-SetupMod-ItemIEs } } +DRBs-Modified-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF ProtocolIE-SingleContainer { { DRBs-Modified-ItemIEs } } +SRBs-SetupMod-List ::= SEQUENCE (SIZE(1..maxnoofSRBs)) OF ProtocolIE-SingleContainer { { SRBs-SetupMod-ItemIEs } } +SRBs-Modified-List ::= SEQUENCE (SIZE(1..maxnoofSRBs)) OF ProtocolIE-SingleContainer { { SRBs-Modified-ItemIEs } } +DRBs-FailedToBeModified-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF ProtocolIE-SingleContainer { { DRBs-FailedToBeModified-ItemIEs } } +SRBs-FailedToBeSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofSRBs)) OF ProtocolIE-SingleContainer { { SRBs-FailedToBeSetupMod-ItemIEs } } +DRBs-FailedToBeSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF ProtocolIE-SingleContainer { { DRBs-FailedToBeSetupMod-ItemIEs } } +SCell-FailedtoSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofSCells)) OF ProtocolIE-SingleContainer { { SCell-FailedtoSetupMod-ItemIEs } } +BHChannels-SetupMod-List ::= SEQUENCE (SIZE(1..maxnoofBHRLCChannels)) OF ProtocolIE-SingleContainer { { BHChannels-SetupMod-ItemIEs } } +BHChannels-Modified-List ::= SEQUENCE (SIZE(1..maxnoofBHRLCChannels)) OF ProtocolIE-SingleContainer { { BHChannels-Modified-ItemIEs } } +BHChannels-FailedToBeModified-List ::= SEQUENCE (SIZE(1..maxnoofBHRLCChannels)) OF ProtocolIE-SingleContainer { { BHChannels-FailedToBeModified-ItemIEs } } +BHChannels-FailedToBeSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofBHRLCChannels)) OF ProtocolIE-SingleContainer { { BHChannels-FailedToBeSetupMod-ItemIEs } } + +Associated-SCell-List ::= SEQUENCE (SIZE(1..maxnoofSCells)) OF ProtocolIE-SingleContainer { { Associated-SCell-ItemIEs } } + +DRBs-SetupMod-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-DRBs-SetupMod-Item CRITICALITY ignore TYPE DRBs-SetupMod-Item PRESENCE mandatory }, + ... +} +``` + +``` +DRBs-Modified-ItemIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-DRBs-Modified-Item CRITICALITY ignore TYPE DRBs-Modified-Item PRESENCE mandatory}, +``` + +``` + ... +``` + +``` +} +``` + +``` +SRBs-SetupMod-ItemIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-SRBs-SetupMod-Item CRITICALITY ignore TYPE SRBs-SetupMod-Item PRESENCE mandatory}, +``` + +``` + ... +``` + +``` +} +``` + +``` +SRBs-Modified-ItemIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-SRBs-Modified-Item CRITICALITY ignore TYPE SRBs-Modified-Item PRESENCE mandatory}, +``` + +``` + ... +``` + +``` +} +``` + +``` +SRBs-FailedToBeSetupMod-ItemIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-SRBs-FailedToBeSetupMod-Item CRITICALITY ignore TYPE SRBs-FailedToBeSetupMod-Item PRESENCE mandatory}, +``` + +``` + ... +``` + +``` +} +``` + +``` +DRBs-FailedToBeSetupMod-ItemIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-DRBs-FailedToBeSetupMod-Item CRITICALITY ignore TYPE DRBs-FailedToBeSetupMod-Item PRESENCE mandatory}, +``` + +``` +... +} + +DRBs-FailedToBeModified-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-DRBs-FailedToBeModified-Item CRITICALITY ignore TYPE DRBs-FailedToBeModified-Item PRESENCE mandatory}, + ... +} + +SCell-FailedtoSetupMod-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-SCell-FailedtoSetupMod-Item CRITICALITY ignore TYPE SCell-FailedtoSetupMod-Item PRESENCE mandatory}, + ... +} + +Associated-SCell-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-Associated-SCell-Item CRITICALITY ignore TYPE Associated-SCell-Item PRESENCE mandatory}, + ... +} + +BHChannels-SetupMod-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-BHChannels-SetupMod-Item CRITICALITY ignore TYPE BHChannels-SetupMod-Item PRESENCE mandatory}, + ... +} +``` + +``` +BHChannels-Modified-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-BHChannels-Modified-Item CRITICALITY ignore TYPE BHChannels-Modified-Item PRESENCE mandatory}, + ... +} + +BHChannels-FailedToBeSetupMod-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-BHChannels-FailedToBeSetupMod-Item CRITICALITY ignore TYPE BHChannels-FailedToBeSetupMod-Item PRESENCE mandatory}, + ... +} + +BHChannels-FailedToBeModified-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-BHChannels-FailedToBeModified-Item CRITICALITY ignore TYPE BHChannels-FailedToBeModified-Item PRESENCE mandatory}, + ... +} + +SLDRBs-SetupMod-List ::= SEQUENCE (SIZE(1..maxnoofSLDRBs)) OF ProtocolIE-SingleContainer { { SLDRBs-SetupMod-ItemIEs } } +SLDRBs-Modified-List ::= SEQUENCE (SIZE(1..maxnoofSLDRBs)) OF ProtocolIE-SingleContainer { { SLDRBs-Modified-ItemIEs } } +SLDRBs-FailedToBeModified-List ::= SEQUENCE (SIZE(1..maxnoofSLDRBs)) OF ProtocolIE-SingleContainer { { SLDRBs-FailedToBeModified-ItemIEs } } +SLDRBs-FailedToBeSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofSLDRBs)) OF ProtocolIE-SingleContainer { { SLDRBs-FailedToBeSetupMod-ItemIEs } } + +SLDRBs-SetupMod-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-SLDRBs-SetupMod-Item CRITICALITY ignore TYPE SLDRBs-SetupMod-Item PRESENCE mandatory}, + ... +} +``` + +``` + +} + +SLDRBs-Modified-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-SLDRBs-Modified-Item CRITICALITY ignore TYPE SLDRBs-Modified-Item PRESENCE mandatory}, + ... +} + +SLDRBs-FailedToBeSetupMod-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-SLDRBs-FailedToBeSetupMod-Item CRITICALITY ignore TYPE SLDRBs-FailedToBeSetupMod-Item PRESENCE mandatory}, + ... +} + +SLDRBs-FailedToBeModified-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-SLDRBs-FailedToBeModified-Item CRITICALITY ignore TYPE SLDRBs-FailedToBeModified-Item PRESENCE mandatory}, + ... +} + +UE-MulticastMRBs-Setup-List ::= SEQUENCE (SIZE(1..maxnoofMRBsforUE)) OF ProtocolIE-SingleContainer { { UE-MulticastMRBs-Setup-ItemIEs } } + +UE-MulticastMRBs-Setup-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-UE-MulticastMRBs-Setup-Item CRITICALITY reject TYPE UE-MulticastMRBs-Setup-Item PRESENCE mandatory}, + ... +} + +``` + +``` + +-- ***** +-- +-- UE CONTEXT MODIFICATION FAILURE +-- +-- ***** + +``` + +``` + +UEContextModificationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { UEContextModificationFailureIEs } }, + ... +} + +``` + +``` + +UEContextModificationFailureIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + { ID id-requestedTargetCellGlobalID CRITICALITY reject TYPE NRCGI PRESENCE optional}, + ... +} + +``` + +``` + +-- ***** +-- + +``` + +-- UE Context Modification Required (gNB-DU initiated) ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- UE CONTEXT MODIFICATION REQUIRED + +-- + +-- \*\*\*\*\* + +UEContextModificationRequired ::= SEQUENCE { + +    protocolIEs          ProtocolIE-Container    { { UEContextModificationRequiredIEs} }, + +    ... + +} + +UEContextModificationRequiredIEs FLAP-PROTOCOL-IES ::= { + +| | | | | | +|-----------------------------------------------|--------------------|--------------------------------------------|--------------------|---| +| { ID id-gNB-CU-UE-FlAP-ID | CRITICALITY reject | TYPE GNB-CU-UE-FlAP-ID | PRESENCE mandatory | } | +| { ID id-gNB-DU-UE-FlAP-ID | CRITICALITY reject | TYPE GNB-DU-UE-FlAP-ID | PRESENCE mandatory | } | +| { ID id-ResourceCoordinationTransferContainer | CRITICALITY ignore | TYPE ResourceCoordinationTransferContainer | PRESENCE optional | } | +| { ID id-DUtoCURRCInformation | CRITICALITY reject | TYPE DUtoCURRCInformation | PRESENCE optional | } | +| { ID id-DRBs-Required-ToBeModified-List | CRITICALITY reject | TYPE DRBs-Required-ToBeModified-List | PRESENCE optional | } | +| { ID id-SRBs-Required-ToBeReleased-List | CRITICALITY reject | TYPE SRBs-Required-ToBeReleased-List | PRESENCE optional | } | +| { ID id-DRBs-Required-ToBeReleased-List | CRITICALITY reject | TYPE DRBs-Required-ToBeReleased-List | PRESENCE optional | } | +| { ID id-Cause | CRITICALITY ignore | TYPE Cause | PRESENCE mandatory | } | + +``` + + { ID id-BHChannels-Required-ToBeReleased-List CRITICALITY reject TYPE BHChannels-Required-ToBeReleased-List PRESENCE optional}| + { ID id-SLDRBs-Required-ToBeModified-List CRITICALITY reject TYPE SLDRBs-Required-ToBeModified-List PRESENCE optional}| + { ID id-SLDRBs-Required-ToBeReleased-List CRITICALITY reject TYPE SLDRBs-Required-ToBeReleased-List PRESENCE optional}| + { ID id-targetCellsToCancel CRITICALITY reject TYPE TargetCellList PRESENCE optional}| + { ID id-UuRLCChannelRequiredToBeModifiedList CRITICALITY reject TYPE UuRLCChannelRequiredToBeModifiedList PRESENCE optional}| + { ID id-UuRLCChannelRequiredToBeReleasedList CRITICALITY reject TYPE UuRLCChannelRequiredToBeReleasedList PRESENCE optional}| + { ID id-PC5RLCChannelRequiredToBeModifiedList CRITICALITY reject TYPE PC5RLCChannelRequiredToBeModifiedList PRESENCE optional}| + { ID id-PC5RLCChannelRequiredToBeReleasedList CRITICALITY reject TYPE PC5RLCChannelRequiredToBeReleasedList PRESENCE optional}| + { ID id-UE-MulticastMRBs-RequiredToBeModified-List CRITICALITY reject TYPE UE-MulticastMRBs-RequiredToBeModified-List PRESENCE optional }| + { ID id-UE-MulticastMRBs-RequiredToBeReleased-List CRITICALITY reject TYPE UE-MulticastMRBs-RequiredToBeReleased-List PRESENCE optional }| + { ID id-LTMCells-ToBeReleased-List CRITICALITY ignore TYPE LTMCells-ToBeReleased-List PRESENCE optional }, + ... +} + +``` + +``` + +DRBs-Required-ToBeModified-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF ProtocolIE-SingleContainer { { DRBs-Required-ToBeModified-ItemIEs } } + +``` + +``` + +DRBs-Required-ToBeReleased-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF ProtocolIE-SingleContainer { { DRBs-Required-ToBeReleased-ItemIEs } } + +``` + +``` + +SRBs-Required-ToBeReleased-List ::= SEQUENCE (SIZE(1..maxnoofSRBs)) OF ProtocolIE-SingleContainer { { SRBs-Required-ToBeReleased-ItemIEs } } + +``` + +``` + +BHChannels-Required-ToBeReleased-List ::= SEQUENCE (SIZE(1..maxnoofBHRLCChannels)) OF ProtocolIE-SingleContainer { { BHChannels-Required-ToBeReleased-ItemIEs } } + +``` + +``` + +DRBs-Required-ToBeModified-ItemIEs FLAP-PROTOCOL-IES ::= { + +``` + +``` + + { ID id-DRBs-Required-ToBeModified-Item CRITICALITY reject TYPE DRBs-Required-ToBeModified-Item PRESENCE mandatory}, + ... +} + +``` + +``` +} + +DRBs-Required-ToBeReleased-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-DRBs-Required-ToBeReleased-Item CRITICALITY reject TYPE DRBs-Required-ToBeReleased-Item PRESENCE mandatory}, + ... +} + +SRBs-Required-ToBeReleased-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-SRBs-Required-ToBeReleased-Item CRITICALITY reject TYPE SRBs-Required-ToBeReleased-Item PRESENCE mandatory}, + ... +} + +BHChannels-Required-ToBeReleased-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-BHChannels-Required-ToBeReleased-Item CRITICALITY reject TYPE BHChannels-Required-ToBeReleased-Item PRESENCE mandatory}, + ... +} + +SLDRBs-Required-ToBeModified-List ::= SEQUENCE (SIZE(1..maxnoofSLDRBs)) OF ProtocolIE-SingleContainer { { SLDRBs-Required-ToBeModified-ItemIEs } } +SLDRBs-Required-ToBeReleased-List ::= SEQUENCE (SIZE(1..maxnoofSLDRBs)) OF ProtocolIE-SingleContainer { { SLDRBs-Required-ToBeReleased-ItemIEs } } + +SLDRBs-Required-ToBeModified-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-SLDRBs-Required-ToBeModified-Item CRITICALITY reject TYPE SLDRBs-Required-ToBeModified-Item PRESENCE mandatory}, + ... +} +``` + +``` + +SLDRBs-Required-ToBeReleased-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-SLDRBs-Required-ToBeReleased-Item CRITICALITY reject TYPE SLDRBs-Required-ToBeReleased-Item PRESENCE mandatory}, + ... +} + +UE-MulticastMRBs-RequiredToBeModified-List ::= SEQUENCE (SIZE(1..maxnoofMRBsforUE)) OF + ProtocolIE-SingleContainer { { UE-MulticastMRBs-RequiredToBeModified-ItemIEs} } + +UE-MulticastMRBs-RequiredToBeModified-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-UE-MulticastMRBs-RequiredToBeModified-Item CRITICALITY reject TYPE UE-MulticastMRBs-RequiredToBeModified-Item PRESENCE mandatory}, + ... +} + +UE-MulticastMRBs-RequiredToBeReleased-List ::= SEQUENCE (SIZE(1..maxnoofMRBsforUE)) OF + ProtocolIE-SingleContainer { { UE-MulticastMRBs-RequiredToBeReleased-ItemIEs} } + +UE-MulticastMRBs-RequiredToBeReleased-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-UE-MulticastMRBs-RequiredToBeReleased-Item CRITICALITY reject TYPE UE-MulticastMRBs-RequiredToBeReleased-Item PRESENCE mandatory}, + ... +} + +``` + +-- \*\*\*\*\* + +``` + +-- +-- UE CONTEXT MODIFICATION CONFIRM +-- +-- ***** + +``` + +``` + +UEContextModificationConfirm ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { UEContextModificationConfirmIEs } }, + ... +} + +``` + +``` + +UEContextModificationConfirmIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FLAP-ID CRITICALITY reject TYPE GNB-CU-UE-FLAP-ID PRESENCE mandatory } | + { ID id-gNB-DU-UE-FLAP-ID CRITICALITY reject TYPE GNB-DU-UE-FLAP-ID PRESENCE mandatory } | + { ID id-ResourceCoordinationTransferContainer CRITICALITY ignore TYPE ResourceCoordinationTransferContainer PRESENCE optional } | + { ID id-DRBs-ModifiedConf-List CRITICALITY ignore TYPE DRBs-ModifiedConf-List PRESENCE optional } | + { ID id-RRCContainer CRITICALITY ignore TYPE RRCContainer PRESENCE optional } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } | + { ID id-ExecuteDuplication CRITICALITY ignore TYPE ExecuteDuplication PRESENCE optional } | + { ID id-ResourceCoordinationTransferInformation CRITICALITY ignore TYPE ResourceCoordinationTransferInformation PRESENCE optional } | + { ID id-SLDRBs-ModifiedConf-List CRITICALITY ignore TYPE SLDRBs-ModifiedConf-List PRESENCE optional } | + { ID id-UuRLCChannelModifiedList CRITICALITY reject TYPE UuRLCChannelModifiedList PRESENCE optional } | + { ID id-PC5RLCChannelModifiedList CRITICALITY reject TYPE PC5RLCChannelModifiedList PRESENCE optional } | + { ID id-UE-MulticastMRBs-ConfirmedToBeModified-List CRITICALITY reject TYPE UE-MulticastMRBs-ConfirmedToBeModified-List PRESENCE optional }, +} + +``` + +``` + ... +} + +DRBs-ModifiedConf-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF ProtocolIE-SingleContainer { { DRBs-ModifiedConf-ItemIEs } } + +DRBs-ModifiedConf-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-DRBs-ModifiedConf-Item CRITICALITY ignore TYPE DRBs-ModifiedConf-Item PRESENCE mandatory}, + ... +} + +SLDRBs-ModifiedConf-List ::= SEQUENCE (SIZE(1..maxnoofSLDRBs)) OF ProtocolIE-SingleContainer { { SLDRBs-ModifiedConf-ItemIEs } } + +SLDRBs-ModifiedConf-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-SLDRBs-ModifiedConf-Item CRITICALITY ignore TYPE SLDRBs-ModifiedConf-Item PRESENCE mandatory}, + ... +} + +UE-MulticastMRBs-ConfirmedToBeModified-List ::= SEQUENCE (SIZE(1..maxnoofMRBsforUE)) OF + ProtocolIE-SingleContainer { { UE-MulticastMRBs-ConfirmedToBeModified-ItemIEs } } + +UE-MulticastMRBs-ConfirmedToBeModified-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-UE-MulticastMRBs-ConfirmedToBeModified-Item CRITICALITY reject TYPE UE-MulticastMRBs-ConfirmedToBeModified-Item PRESENCE mandatory}, + ... +} +``` + +``` + +-- ***** +-- +-- UE CONTEXT MODIFICATION REFUSE +-- +-- ***** + +``` + +``` + +UEContextModificationRefuse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { UEContextModificationRefuseIEs} }, + ... +} + +``` + +``` + +UEContextModificationRefuseIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** + +``` + +``` + +-- +-- WRITE-REPLACE WARNING ELEMENTARY PROCEDURE +-- +-- ***** +-- +-- ***** +-- +-- Write-Replace Warning Request +-- +-- ***** + +``` + +``` + +WriteReplaceWarningRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {WriteReplaceWarningRequestIEs} }, + ... +} + +``` + +``` + +WriteReplaceWarningRequestIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-PWSSystemInformation CRITICALITY reject TYPE PWSSystemInformation PRESENCE mandatory }| + { ID id-RepetitionPeriod CRITICALITY reject TYPE RepetitionPeriod PRESENCE mandatory }| + { ID id-NumberOfBroadcastRequest CRITICALITY reject TYPE NumberOfBroadcastRequest PRESENCE mandatory }| + { ID id-Cells-To-Be-Broadcast-List CRITICALITY reject TYPE Cells-To-Be-Broadcast-List PRESENCE optional }, + ... +} + +``` + +``` +Cells-To-Be-Broadcast-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { Cells-To-Be-Broadcast-List-ItemIEs } } +``` + +``` +Cells-To-Be-Broadcast-List-ItemIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-Cells-To-Be-Broadcast-Item CRITICALITY reject TYPE Cells-To-Be-Broadcast-Item PRESENCE mandatory }, +``` + +``` + ... +``` + +``` +} +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- Write-Replace Warning Response +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +WriteReplaceWarningResponse ::= SEQUENCE { +``` + +``` + protocolIEs ProtocolIE-Container { {WriteReplaceWarningResponseIEs} }, +``` + +``` + ... +``` + +``` +} +``` + +``` +WriteReplaceWarningResponseIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory } | +``` + +``` + { ID id-Cells-Broadcast-Completed-List CRITICALITY reject TYPE Cells-Broadcast-Completed-List PRESENCE optional } | +``` + +``` + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } | +``` + +``` + { ID id-Dedicated-SIDelivery-NeededUE-List CRITICALITY ignore TYPE Dedicated-SIDelivery-NeededUE-List PRESENCE optional }, +``` + +``` + + ... +} + +Cells-Broadcast-Completed-List ::= SEQUENCE (SIZE(1.. maxCellingNBUDU)) OF ProtocolIE-SingleContainer { { Cells-Broadcast-Completed-List- +ItemIEs } } + +Cells-Broadcast-Completed-List-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-Cells-Broadcast-Completed-Item CRITICALITY reject TYPE Cells-Broadcast-Completed-Item PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- PWS CANCEL ELEMENTARY PROCEDURE +-- +-- ***** +-- +-- ***** +-- +-- PWS Cancel Request +-- +-- ***** + +``` + +``` + +PWSCancelRequest ::= SEQUENCE { + +``` + +``` + + protocolIEs ProtocolIE-Container { {PWSCancelRequestIEs} }, + ... +} + +``` + +``` + +PWSCancelRequestIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-NumberOfBroadcastRequest CRITICALITY reject TYPE NumberOfBroadcastRequest PRESENCE mandatory }| + { ID id-Broadcast-To-Be-Cancelled-List CRITICALITY reject TYPE Broadcast-To-Be-Cancelled-List PRESENCE optional }| + { ID id-Cancel-all-Warning-Messages-Indicator CRITICALITY reject TYPE Cancel-all-Warning-Messages-Indicator PRESENCE optional }| + { ID id-NotificationInformation CRITICALITY reject TYPE NotificationInformation PRESENCE optional}, + ... +} + +``` + +``` + +Broadcast-To-Be-Cancelled-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { Broadcast-To-Be-Cancelled-List-ItemIEs } } + +``` + +``` + +Broadcast-To-Be-Cancelled-List-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-Broadcast-To-Be-Cancelled-Item CRITICALITY reject TYPE Broadcast-To-Be-Cancelled-Item PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- PWS Cancel Response +-- + +``` + +``` +-- ***** +``` + +``` +PWSCancelResponse ::= SEQUENCE { +``` + +``` + protocolIEs ProtocolIE-Container { {PWSCancelResponseIEs} }, +``` + +``` + ... +``` + +``` +} +``` + +``` +PWSCancelResponseIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| +``` + +``` + { ID id-Cells-Broadcast-Cancelled-List CRITICALITY reject TYPE Cells-Broadcast-Cancelled-List PRESENCE optional }| +``` + +``` + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, +``` + +``` + ... +``` + +``` +} +``` + +``` +Cells-Broadcast-Cancelled-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { Cells-Broadcast-Cancelled-List-ItemIEs } } +``` + +``` +Cells-Broadcast-Cancelled-List-ItemIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-Cells-Broadcast-Cancelled-Item CRITICALITY reject TYPE Cells-Broadcast-Cancelled-Item PRESENCE mandatory }, +``` + +``` + ... +``` + +``` +} +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- UE Inactivity Notification ELEMENTARY PROCEDURE +``` + +``` + +-- +-- ***** +-- +-- ***** +-- +-- UE Inactivity Notification +-- +-- ***** + +UEInactivityNotification ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ UEInactivityNotificationIEs}}, + ... +} + +UEInactivityNotificationIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-DRB-Activity-List CRITICALITY reject TYPE DRB-Activity-List PRESENCE mandatory }| + { ID id-SDT-Termination-Request CRITICALITY ignore TYPE SDT-Termination-Request PRESENCE optional }, + ... +} + +DRB-Activity-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF ProtocolIE-SingleContainer { { DRB-Activity-ItemIEs } } +``` + +DRB-Activity-ItemIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-DRB-Activity-Item CRITICALITY reject TYPE DRB-Activity-Item PRESENCE mandatory}, + +... + +} + +-- \*\*\*\*\* + +-- + +-- Initial UL RRC Message Transfer ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- INITIAL UL RRC Message Transfer + +-- + +-- \*\*\*\*\* + +InitialULRRCMessageTransfer ::= SEQUENCE { + +protocolIEs ProtocolIE-Container {{ InitialULRRCMessageTransferIEs}}, + +... + +} + +InitialULRRCMessageTransferIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-gNB-DU-UE-FLAP-ID CRITICALITY reject TYPE GNB-DU-UE-FLAP-ID PRESENCE mandatory }| + +{ ID id-NRCGI CRITICALITY reject TYPE NRCGI PRESENCE mandatory }| + +``` + + { ID id-C-RNTI CRITICALITY reject TYPE C-RNTI PRESENCE mandatory }| + { ID id-RRContainer CRITICALITY reject TYPE RRContainer PRESENCE mandatory }| + { ID id-DUtoCURRContainer CRITICALITY reject TYPE DUtoCURRContainer PRESENCE optional }| + { ID id-SULAccessIndication CRITICALITY ignore TYPE SULAccessIndication PRESENCE optional }| + { ID id-TransactionID CRITICALITY ignore TYPE TransactionID PRESENCE mandatory }| + { ID id-RANUEID CRITICALITY ignore TYPE RANUEID PRESENCE optional }| + { ID id-RRContainer-RRSetupComplete CRITICALITY ignore TYPE RRContainer-RRSetupComplete PRESENCE optional }| + { ID id-NRRedCapUEIndication CRITICALITY ignore TYPE NRRedCapUEIndication PRESENCE optional }| + { ID id-SDTInformation CRITICALITY ignore TYPE SDTInformation PRESENCE optional }| + { ID id-SidelinkRelayConfiguration CRITICALITY ignore TYPE SidelinkRelayConfiguration PRESENCE optional }| + { ID id-NReRedCapUEIndication CRITICALITY ignore TYPE NReRedCapUEIndication PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- +-- DL RRC Message Transfer ELEMENTARY PROCEDURE + +-- +-- \*\*\*\*\* + +-- +-- \*\*\*\*\* + +-- DL RRC Message Transfer + +-- +-- \*\*\*\*\* + +DLRRMessageTransfer ::= SEQUENCE { +    protocolIEs          ProtocolIE-Container      {{ DLRRMessageTransferIEs }}, +    ... +} + +DLRRMessageTransferIEs FLAP-PROTOCOL-IES ::= { +    { ID id-gNB-CU-UE-FlAP-ID                  CRITICALITY reject  TYPE GNB-CU-UE-FlAP-ID          PRESENCE mandatory }| +    { ID id-gNB-DU-UE-FlAP-ID                  CRITICALITY reject  TYPE GNB-DU-UE-FlAP-ID          PRESENCE mandatory }| +    { ID id-oldgNB-DU-UE-FlAP-ID              CRITICALITY reject  TYPE GNB-DU-UE-FlAP-ID          PRESENCE optional }| +    { ID id-SRBID                              CRITICALITY reject  TYPE SRBID                      PRESENCE mandatory }| +    { ID id-ExecuteDuplication                CRITICALITY ignore  TYPE ExecuteDuplication          PRESENCE optional }| +    { ID id-RRContainer                        CRITICALITY reject  TYPE RRContainer              PRESENCE mandatory }| +    { ID id-RAT-FrequencyPriorityInformation  CRITICALITY reject  TYPE RAT-FrequencyPriorityInformation  PRESENCE optional }| +    { ID id-RRDeliveryStatusRequest          CRITICALITY ignore  TYPE RRDeliveryStatusRequest          PRESENCE optional }| +    { ID id-UEContextNotRetrievable          CRITICALITY reject  TYPE UEContextNotRetrievable          PRESENCE optional }| +    { ID id-RedirectedRRmessage              CRITICALITY reject  TYPE OCTET STRING                  PRESENCE optional }| +    { ID id-PLMNAssistanceInfoForNetShar      CRITICALITY ignore  TYPE PLMN-Identity                  PRESENCE optional }| +    { ID id-new-gNB-CU-UE-FlAP-ID            CRITICALITY reject  TYPE GNB-CU-UE-FlAP-ID          PRESENCE optional }| +    { ID id-AdditionalRRMPriorityIndex        CRITICALITY ignore  TYPE AdditionalRRMPriorityIndex          PRESENCE optional }| +    { ID id-SRBMappingInfo                    CRITICALITY ignore  TYPE UuRLCChannelID                  PRESENCE optional }, +    ... +} + +``` + +} + +-- ***** +-- +-- UL RRC Message Transfer ELEMENTARY PROCEDURE +-- +-- ***** + +-- ***** +-- +-- UL RRC Message Transfer +-- +-- ***** + +ULRRCMessageTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ ULRRCMessageTransferIEs }}, + ... +} + +ULRRCMessageTransferIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-SRBID CRITICALITY reject TYPE SRBID PRESENCE mandatory }| + { ID id-RRCContainer CRITICALITY reject TYPE RRCContainer PRESENCE mandatory }| + { ID id-SelectedPLMNID CRITICALITY reject TYPE PLMN-Identity PRESENCE optional }| +} + +``` + +``` + + { ID id-new-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- PRIVATE MESSAGE +-- +-- ***** + +``` + +``` + +PrivateMessage ::= SEQUENCE { + privateIEs PrivateIE-Container {{PrivateMessage-IEs}}, + ... +} + +``` + +``` + +PrivateMessage-IEs FlAP-PRIVATE-IES ::= { + ... +} + +``` + +``` + +-- ***** +-- +-- System Information ELEMENTARY PROCEDURE +-- +-- ***** + +``` + +``` + +-- ***** +-- +-- ***** +-- +-- System information Delivery Command +-- +-- ***** + +``` + +``` + +SystemInformationDeliveryCommand ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ SystemInformationDeliveryCommandIEs }}, + ... +} + +``` + +``` + +SystemInformationDeliveryCommandIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-NRCGI CRITICALITY reject TYPE NRCGI PRESENCE mandatory }| + { ID id-SItype-List CRITICALITY reject TYPE SItype-List PRESENCE mandatory }| + { ID id-ConfirmedUEID CRITICALITY reject TYPE GNB-DU-UE-FLAP-ID PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- + +``` + +``` + +-- Paging PROCEDURE + +-- +-- ***** + +-- ***** + +-- +-- Paging + +-- +-- ***** + +``` + +``` + +Paging ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ PagingIEs}}, + ... +} + +``` + +``` + +PagingIEs FLAP-PROTOCOL-IES ::= { + { ID id-UEIdentityIndexValue CRITICALITY reject TYPE UEIdentityIndexValue PRESENCE mandatory }| + { ID id-PagingIdentity CRITICALITY reject TYPE PagingIdentity PRESENCE mandatory }| + { ID id-PagingDRX CRITICALITY ignore TYPE PagingDRX PRESENCE optional }| + { ID id-PagingPriority CRITICALITY ignore TYPE PagingPriority PRESENCE optional }| + { ID id-PagingCell-List CRITICALITY ignore TYPE PagingCell-list PRESENCE mandatory }| + { ID id-PagingOrigin CRITICALITY ignore TYPE PagingOrigin PRESENCE optional }| + { ID id-RANUEPagingDRX CRITICALITY ignore TYPE PagingDRX PRESENCE optional }| + { ID id-CNUEPagingDRX CRITICALITY ignore TYPE PagingDRX PRESENCE optional }| +} + +``` + +``` + + { ID id-NRPagingDRXInformation CRITICALITY ignore TYPE NRPagingDRXInformation PRESENCE optional }| + { ID id-NRPagingDRXInformationforRRRCINACTIVE CRITICALITY ignore TYPE NRPagingDRXInformationforRRRCINACTIVE PRESENCE optional }| + { ID id-PagingCause CRITICALITY ignore TYPE PagingCause PRESENCE optional }| + { ID id-PEIPSAssistanceInfo CRITICALITY ignore TYPE PEIPSAssistanceInfo PRESENCE optional }| + { ID id-UEPagingCapability CRITICALITY ignore TYPE UEPagingCapability PRESENCE optional }| + { ID id-ExtendedUEIdentityIndexValue CRITICALITY ignore TYPE ExtendedUEIdentityIndexValue PRESENCE optional}| + { ID id-HashedUEIdentityIndexValue CRITICALITY ignore TYPE HashedUEIdentityIndexValue PRESENCE optional}| + { ID id-MT-SDT-Information CRITICALITY ignore TYPE MT-SDT-Information PRESENCE optional }| + { ID id-NRPaginglongeDRXInformationforRRRCINACTIVE CRITICALITY ignore TYPE NRPaginglongeDRXInformationforRRRCINACTIVE PRESENCE +optional }, + ... +} + +``` + +``` + +PagingCell-list ::= SEQUENCE (SIZE(1.. maxnoofPagingCells)) OF ProtocolIE-SingleContainer { { PagingCell-ItemIEs } } + +``` + +``` + +PagingCell-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-PagingCell-Item CRITICALITY ignore TYPE PagingCell-Item PRESENCE mandatory} , + ... +} + +``` + +``` + +-- ***** +-- +-- Notify + +``` + +``` + +-- +-- ***** + +Notify ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ NotifyIEs}}, + ... +} + +NotifyIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FLAP-ID CRITICALITY reject TYPE GNB-CU-UE-FLAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FLAP-ID CRITICALITY reject TYPE GNB-DU-UE-FLAP-ID PRESENCE mandatory }| + { ID id-DRB-Notify-List CRITICALITY reject TYPE DRB-Notify-List PRESENCE mandatory }, + ... +} + +DRB-Notify-List ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF ProtocolIE-SingleContainer { { DRB-Notify-ItemIEs } } + +DRB-Notify-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-DRB-Notify-Item CRITICALITY reject TYPE DRB-Notify-Item PRESENCE mandatory}, + ... +} + +-- ***** + +``` + +``` + +-- +-- NETWORK ACCESS RATE REDUCTION ELEMENTARY PROCEDURE +-- +-- ***** +-- +-- ***** +-- +-- Network Access Rate Reduction +-- +-- ***** + +``` + +``` + +NetworkAccessRateReduction ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ NetworkAccessRateReductionIEs }}, + ... +} + +``` + +``` + +NetworkAccessRateReductionIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-UAC-Assistance-Info CRITICALITY reject TYPE UAC-Assistance-Info PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- + +``` + +``` +-- PWS RESTART INDICATION ELEMENTARY PROCEDURE +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- PWS Restart Indication +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +PWSRestartIndication ::= SEQUENCE { +``` + +``` + protocolIEs ProtocolIE-Container { { PWSRestartIndicationIEs } }, +``` + +``` + ... +``` + +``` +} +``` + +``` +PWSRestartIndicationIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory } | +``` + +``` + { ID id-NR-CGI-List-For-Restart-List CRITICALITY reject TYPE NR-CGI-List-For-Restart-List PRESENCE mandatory }, +``` + +``` + ... +``` + +``` +} +``` + +``` +NR-CGI-List-For-Restart-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { NR-CGI-List-For-Restart-List-ItemIEs } } +``` + +``` +NR-CGI-List-For-Restart-List-ItemIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + + { ID id-NR-CGI-List-For-Restart-Item CRITICALITY reject TYPE NR-CGI-List-For-Restart-Item PRESENCE mandatory }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- PWS FAILURE INDICATION ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- PWS Failure Indication + +-- + +-- \*\*\*\*\* + +``` + +PWSFailureIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PWSFailureIndicationIEs } }, + ... +} + +``` + +``` + +PWSFailureIndicationIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-PWS-Failed-NR-CGI-List CRITICALITY reject TYPE PWS-Failed-NR-CGI-List PRESENCE optional }, + +``` + +``` + + ... +} + +PWS-Failed-NR-CGI-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { PWS-Failed-NR-CGI-List-ItemIEs } } + +PWS-Failed-NR-CGI-List-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-PWS-Failed-NR-CGI-Item CRITICALITY reject TYPE PWS-Failed-NR-CGI-Item PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- gNB-DU STATUS INDICATION ELEMENTARY PROCEDURE +-- +-- ***** +-- +-- ***** +-- +-- gNB-DU Status Indication +-- +-- ***** + +``` + +``` + +GNBDUStatusIndication ::= SEQUENCE { + +``` + +``` + +protocolIEs ProtocolIE-Container { {GNBDUStatusIndicationIEs} }, +... +} + +``` + +``` + +GNBDUStatusIndicationIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-GNBDUOverloadInformation CRITICALITY reject TYPE GNBDUOverloadInformation PRESENCE mandatory }| + { ID id-IABCongestionIndication CRITICALITY ignore TYPE IABCongestionIndication PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- RRC Delivery Report ELEMENTARY PROCEDURE +-- +-- ***** +-- +-- ***** +-- +-- RRC Delivery Report +-- +-- ***** + +``` + +``` + +RRCDeliveryReport ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ RRCDeliveryReportIEs}}, + ... +} + +RRCDeliveryReportIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-RRCDeliveryStatus CRITICALITY ignore TYPE RRCDeliveryStatus PRESENCE mandatory }| + { ID id-SRBID CRITICALITY ignore TYPE SRBID PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- F1 Removal ELEMENTARY PROCEDURE +-- +-- ***** + +-- ***** +-- +-- F1 Removal Request +-- + +``` + +-- \*\*\*\*\* + +``` + +FlRemovalRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ FlRemovalRequestIEs }}, + ... +} + +``` + +``` + +FlRemovalRequestIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- Fl Removal Response + +-- + +-- \*\*\*\*\* + +``` + +FlRemovalResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ FlRemovalResponseIEs }}, + ... +} + +``` + +``` + +FlRemovalResponseIEs FLAP-PROTOCOL-IES ::= { + +``` + +``` + + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- F1 Removal Failure + +-- + +-- \*\*\*\*\* + +``` + +F1RemovalFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ F1RemovalFailureIEs }}, + + ... +} + +``` + +``` + +F1RemovalFailureIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + + ... +} + +``` + +``` + +-- ***** +-- +-- TRACE ELEMENTARY PROCEDURES +-- +-- ***** + +-- ***** +-- +-- TRACE START +-- +-- ***** + +``` + +``` + +TraceStart ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {TraceStartIEs} }, + ... +} + +``` + +``` + +TraceStartIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-TraceActivation CRITICALITY ignore TYPE TraceActivation PRESENCE mandatory }, + ... +} + +``` + +``` + +} + +-- ***** +-- +-- DEACTIVATE TRACE +-- +-- ***** + +``` + +``` + +DeactivateTrace ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {DeactivateTraceIEs} }, + ... +} + +``` + +``` + +DeactivateTraceIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-TraceID CRITICALITY ignore TYPE TraceID PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- CELL TRAFFIC TRACE +-- +-- ***** + +``` + +-- \*\*\*\*\* + +``` + +CellTrafficTrace ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {CellTrafficTraceIEs} }, + ... +} + +``` + +``` + +CellTrafficTraceIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-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-TraceCollectionEntityURI CRITICALITY ignore TYPE URI-address PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- DU-CU Radio Information Transfer ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +``` + +-- +-- DU-CU Radio Information Transfer +-- +-- ***** + +``` + +``` + +DUCURadioInformationTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ DUCURadioInformationTransferIEs}}, + ... +} + +``` + +``` + +DUCURadioInformationTransferIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-DUCURadioInformationType CRITICALITY ignore TYPE DUCURadioInformationType PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- CU-DU Radio Information Transfer ELEMENTARY PROCEDURE +-- +-- ***** + +``` + +``` + +-- ***** +-- +-- CU-DU Radio Information Transfer +-- +-- ***** + +``` + +``` + +CUDURadioInformationTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ CUDURadioInformationTransferIEs}}, + ... +} + +``` + +``` + +CUDURadioInformationTransferIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-CUDURadioInformationType CRITICALITY ignore TYPE CUDURadioInformationType PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- IAB PROCEDURES +-- +-- ***** +-- ***** +-- + +``` + +-- BAP Mapping Configuration ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- BAP MAPPING CONFIGURATION + +-- + +-- \*\*\*\*\* + +BAPMappingConfiguration ::= SEQUENCE { + +    protocolIEs          ProtocolIE-Container { {BAPMappingConfiguration-IEs} }, + +    ... + +} + +BAPMappingConfiguration-IEs FLAP-PROTOCOL-IES ::= { + +| | | | | | +|---------------------------------------------|--------------------|------|-------------------------------------|---------------------| +| { ID id-TransactionID | CRITICALITY reject | TYPE | TransactionID | PRESENCE mandatory} | +| { ID id-BH-Routing-Information-Added-List | CRITICALITY ignore | TYPE | BH-Routing-Information-Added-List | PRESENCE optional} | +| { ID id-BH-Routing-Information-Removed-List | CRITICALITY ignore | TYPE | BH-Routing-Information-Removed-List | PRESENCE optional} | +| { ID id-TrafficMappingInformation | CRITICALITY ignore | TYPE | TrafficMappingInfo | PRESENCE optional} | +| { ID id-BufferSizeThresh | CRITICALITY ignore | TYPE | BufferSizeThresh | PRESENCE optional} | +| { ID id-BAP-Header-Rewriting-Added-List | CRITICALITY ignore | TYPE | BAP-Header-Rewriting-Added-List | PRESENCE optional} | +| { ID id-Re-routingEnableIndicator | CRITICALITY ignore | TYPE | Re-routingEnableIndicator | PRESENCE optional} | + +``` +{ ID id-BAP-Header-Rewriting-Removed-List CRITICALITY ignore TYPE BAP-Header-Rewriting-Removed-List PRESENCE optional}, +... +} + +BH-Routing-Information-Added-List ::= SEQUENCE (SIZE(1.. maxnoofRoutingEntries)) OF ProtocolIE-SingleContainer { { BH-Routing-Information-Added-List-ItemIEs } } + +BH-Routing-Information-Removed-List ::= SEQUENCE (SIZE(1.. maxnoofRoutingEntries)) OF ProtocolIE-SingleContainer { { BH-Routing-Information-Removed-List-ItemIEs } } + +BH-Routing-Information-Added-List-ItemIEs FLAP-PROTOCOL-IES ::= { + + { ID id-BH-Routing-Information-Added-List-Item CRITICALITY ignore TYPE BH-Routing-Information-Added-List-Item + PRESENCE optional}, + ... +} + +BH-Routing-Information-Removed-List-ItemIEs FLAP-PROTOCOL-IES ::= { + + { ID id-BH-Routing-Information-Removed-List-Item CRITICALITY ignore TYPE BH-Routing-Information-Removed-List-Item + PRESENCE optional}, + ... +} + +BAP-Header-Rewriting-Added-List ::= SEQUENCE (SIZE(1.. maxnoofRoutingEntries)) OF ProtocolIE-SingleContainer { { BAP-Header-Rewriting-Added-List-ItemIEs } } + +BAP-Header-Rewriting-Added-List-ItemIEs FLAP-PROTOCOL-IES ::= { + + { ID id-BAP-Header-Rewriting-Added-List-Item CRITICALITY ignore TYPE BAP-Header-Rewriting-Added-List-Item PRESENCE optional}, + ... +} +``` + +``` + +} + +BAP-Header-Rewriting-Removed-List ::= SEQUENCE (SIZE(1.. maxnoofRoutingEntries)) OF ProtocolIE-SingleContainer { { BAP-Header-Rewriting-Removed-List-ItemIEs } } + +BAP-Header-Rewriting-Removed-List-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-BAP-Header-Rewriting-Removed-List-Item CRITICALITY ignore TYPE BAP-Header-Rewriting-Removed-List-Item PRESENCE optional}, + ... +} + +-- ***** +-- +-- BAP MAPPING CONFIGURATION ACKNOWLEDGE +-- +-- ***** + +BAPMappingConfigurationAcknowledge ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {BAPMappingConfigurationAcknowledge-IEs} }, + ... +} + +BAPMappingConfigurationAcknowledge-IEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}, + ... +} + +``` + +``` + +} + +-- ***** +-- +-- BAP MAPPING CONFIGURATION FAILURE +-- +-- ***** + +BAPMappingConfigurationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BAPMappingConfigurationFailureIEs } }, + ... +} + +BAPMappingConfigurationFailureIEs FLAP-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-DU Configuration ELEMENTARY PROCEDURE +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- GNB-DU RESOURCE CONFIGURATION +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +GNBDUResourceConfiguration ::= SEQUENCE { +``` + +``` + protocolIEs ProtocolIE-Container {{ GNBDUResourceConfigurationIEs}}, +``` + +``` + ... +``` + +``` +} +``` + +``` +GNBDUResourceConfigurationIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| +``` + +``` + { ID id-Activated-Cells-to-be-Updated-List CRITICALITY reject TYPE Activated-Cells-to-be-Updated-List PRESENCE optional}| +``` + +``` + { ID id-Child-Nodes-List CRITICALITY reject TYPE Child-Nodes-List PRESENCE optional}| +``` + +``` + { ID id-Neighbour-Node-Cells-List CRITICALITY reject TYPE Neighbour-Node-Cells-List PRESENCE optional}| +``` + +``` + { ID id-Serving-Cells-List CRITICALITY reject TYPE Serving-Cells-List PRESENCE optional}, +``` + +``` + ... +``` + +} + +``` +-- ***** +-- +-- GNB-DU RESOURCE CONFIGURATION ACKNOWLEDGE +-- +-- ***** +``` + +``` +GNBDUResourceConfigurationAcknowledge ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { GNBDUResourceConfigurationAcknowledgeIEs } }, + ... +} +``` + +``` +GNBDUResourceConfigurationAcknowledgeIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} +``` + +``` +-- ***** +-- +-- GNB-DU RESOURCE CONFIGURATION FAILURE +-- +-- ***** +``` + +``` +GNBDUResourceConfigurationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { GNBDUResourceConfigurationFailureIEs} }, + ... +} +``` + +``` +GNBDUResourceConfigurationFailureIEs FLAP-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 }, + ... +} +``` + +``` +-- ***** +-- +-- IAB TNL Address Allocation ELEMENTARY PROCEDURE +-- +``` + +``` + +-- ***** +-- +-- ***** +-- +-- IAB TNL ADDRESS REQUEST +-- +-- ***** + +``` + +``` + +IABTNLAddressRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {IABTNLAddressRequestIEs} }, + ... +} + +``` + +``` + +IABTNLAddressRequestIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-IABv4AddressesRequested CRITICALITY reject TYPE IABv4AddressesRequested PRESENCE optional }| + { ID id-IABIPv6RequestType CRITICALITY reject TYPE IABIPv6RequestType PRESENCE optional }| + { ID id-IAB-TNL-Addresses-To-Remove-List CRITICALITY reject TYPE IAB-TNL-Addresses-To-Remove-List PRESENCE optional }| + { ID id-IAB-TNL-Addresses-Exception CRITICALITY reject TYPE IAB-TNL-Addresses-Exception PRESENCE optional }, + ... +} + +``` + +``` +IAB-TNL-Addresses-To-Remove-List := SEQUENCE (SIZE(1..maxnoofTLAsIAB)) OF ProtocolIE-SingleContainer { { IAB-TNL-Addresses-To-Remove-ItemIEs } } +``` + +``` +IAB-TNL-Addresses-To-Remove-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-IAB-TNL-Addresses-To-Remove-Item CRITICALITY reject TYPE IAB-TNL-Addresses-To-Remove-Item PRESENCE mandatory}, + ... +} +``` + +``` +-- ***** +-- +-- IAB TNL ADDRESS RESPONSE +-- +-- ***** +``` + +``` +IABTNLAddressResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {IABTNLAddressResponseIEs} }, + ... +} +``` + +``` +IABTNLAddressResponseIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory } | +``` + +``` + + { ID id-IAB-Allocated-TNL-Address-List CRITICALITY reject TYPE IAB-Allocated-TNL-Address-List PRESENCE mandatory }, + ... +} + +``` + +``` + +IAB-Allocated-TNL-Address-List ::= SEQUENCE (SIZE(1.. maxnoofTLAsIAB)) OF ProtocolIE-SingleContainer { { IAB-Allocated-TNL-Address-List-ItemIEs } } + +``` + +``` + +IAB-Allocated-TNL-Address-List-ItemIEs FIAP-PROTOCOL-IES ::= { + { ID id-IAB-Allocated-TNL-Address-Item CRITICALITY reject TYPE IAB-Allocated-TNL-Address-Item PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- IAB TNL ADDRESS FAILURE +-- +-- ***** + +``` + +``` + +IABTNLAddressFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { IABTNLAddressFailureIEs } }, + ... +} + +``` + +``` + +IABTNLAddressFailureIEs FLAP-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 }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- IAB UP Configuration Update ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- IAB UP Configuration Update Request + +-- + +-- \*\*\*\*\* + +``` + +IABUPConfigurationUpdateRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { IABUPConfigurationUpdateRequestIEs } }, + ... +} + +``` + +``` +IABUPConfigurationUpdateRequestIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-UL-UP-TNL-Information-to-Update-List CRITICALITY ignore TYPE UL-UP-TNL-Information-to-Update-List PRESENCE optional }| + { ID id-UL-UP-TNL-Address-to-Update-List CRITICALITY ignore TYPE UL-UP-TNL-Address-to-Update-List PRESENCE optional }, + ... +} + +UL-UP-TNL-Information-to-Update-List ::= SEQUENCE (SIZE(1.. maxnoofULUPTNLInformationforIAB)) OF ProtocolIE-SingleContainer { { UL-UP-TNL-Information-to-Update-List-ItemIEs } } + +UL-UP-TNL-Information-to-Update-List-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-UL-UP-TNL-Information-to-Update-List-Item CRITICALITY ignore TYPE UL-UP-TNL-Information-to-Update-List-Item PRESENCE mandatory }, + ... +} + +UL-UP-TNL-Address-to-Update-List ::= SEQUENCE (SIZE(1.. maxnoofUPTNLAddresses)) OF ProtocolIE-SingleContainer { { UL-UP-TNL-Address-to-Update-List-ItemIEs } } + +UL-UP-TNL-Address-to-Update-List-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-UL-UP-TNL-Address-to-Update-List-Item CRITICALITY ignore TYPE UL-UP-TNL-Address-to-Update-List-Item PRESENCE mandatory }, + ... +} +``` + +``` +-- ***** +-- +-- IAB UP Configuration Update Response +-- +-- ***** +``` + +``` +IABUPConfigurationUpdateResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { IABUPConfigurationUpdateResponseIEs } }, + ... +} +``` + +``` +IABUPConfigurationUpdateResponseIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + { ID id-DL-UP-TNL-Address-to-Update-List CRITICALITY reject TYPE DL-UP-TNL-Address-to-Update-List PRESENCE optional }, + ... +} +``` + +``` +DL-UP-TNL-Address-to-Update-List ::= SEQUENCE (SIZE(1.. maxnoofUPTNLAddresses)) OF ProtocolIE-SingleContainer { { DL-UP-TNL-Address-to-Update-List-ItemIEs } } +``` + +``` +DL-UP-TNL-Address-to-Update-List-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-DL-UP-TNL-Address-to-Update-List-Item CRITICALITY ignore TYPE DL-UP-TNL-Address-to-Update-List-Item PRESENCE mandatory }, + ... +} +``` + +``` + +-- ***** +-- +-- IAB UP Configuration Update Failure +-- +-- ***** + +``` + +``` + +IABUPConfigurationUpdateFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { IABUPConfigurationUpdateFailureIEs } }, + ... +} + +``` + +``` + +IABUPConfigurationUpdateFailureIEs FLAP-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 }, + ... +} + +``` + +``` + +-- MIAB F1 SETUP TRIGGERING PROCEDURE +-- +-- ***** + +``` + +``` +-- ***** +-- +-- MIAB F1 SETUP TRIGGERING +-- +-- ***** +``` + +``` +MIABF1SetupTriggering ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ MIABF1SetupTriggeringIEs}}, + ... +} +``` + +``` +MIABF1SetupTriggeringIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-Target-gNB-ID CRITICALITY reject TYPE GlobalGNB-ID PRESENCE mandatory }| + { ID id-Target-gNB-IP-address CRITICALITY ignore TYPE TransportLayerAddress PRESENCE optional }| + { ID id-Target-SeGW-IP-address CRITICALITY ignore TYPE TransportLayerAddress PRESENCE optional }, + ... +} +``` + +``` +-- MIAB F1 SETUP OUTCOME NOTIFICATION PROCEDURE +-- +-- ***** +``` + +``` + +-- ***** +-- +-- MIAB F1 SETUP OUTCOME NOTIFICATION +-- +-- ***** + +MIABF1SetupOutcomeNotification ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ MIABF1SetupOutcomeNotificationIEs}}, + ... +} + +MIABF1SetupOutcomeNotificationIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-F1SetupOutcome CRITICALITY reject TYPE F1SetupOutcome PRESENCE mandatory }| + { ID id-Activated-Cells-Mapping-List CRITICALITY ignore TYPE Activated-Cells-Mapping-List PRESENCE optional }| + { ID id-RRC-Terminating-IAB-Donor-gNB-ID CRITICALITY ignore TYPE GlobalGNB-ID PRESENCE optional }, + ... +} + +F1SetupOutcome ::= ENUMERATED {success, failure,...} + +Activated-Cells-Mapping-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { Activated-Cells-Mapping-List-ItemIEs } } + +``` + +``` + +Activated-Cells-Mapping-List-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-Activated-Cells-Mapping-List-Item CRITICALITY ignore TYPE Activated-Cells-Mapping-List-Item PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- Resource Status Reporting Initiation ELEMENTARY PROCEDURE +-- +-- ***** +-- +-- ***** +-- +-- Resource Status Request +-- +-- ***** + +``` + +``` + +ResourceStatusRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {ResourceStatusRequestIEs} }, + ... +} + +``` + +ResourceStatusRequestIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-TransactionID            CRITICALITY reject    TYPE TransactionID            PRESENCE mandatory }| + +{ ID id-gNBCUMeasurementID    CRITICALITY reject    TYPE GNBCUMeasurementID        PRESENCE mandatory }| + +{ ID id-gNBDUMeasurementID    CRITICALITY ignore    TYPE GNBUDUMeasurementID        PRESENCE conditional }| + +{ ID id-RegistrationRequest    CRITICALITY ignore    TYPE RegistrationRequest            PRESENCE mandatory }| + +{ ID id-ReportCharacteristics CRITICALITY ignore    TYPE ReportCharacteristics        PRESENCE conditional }| + +{ ID id-CellToReportList        CRITICALITY ignore    TYPE CellToReportList                PRESENCE optional }| + +{ ID id-ReportingPeriodicity   CRITICALITY ignore    TYPE ReportingPeriodicity            PRESENCE optional }, + +... + +} + +-- \*\*\*\*\* + +-- + +-- Resource Status Response + +-- + +-- \*\*\*\*\* + +ResourceStatusResponse ::= SEQUENCE { + +protocolIEs            ProtocolIE-Container        { { ResourceStatusResponseIEs } }, + +... + +} + +``` + +ResourceStatusResponseIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-gNBCUMeasurementID CRITICALITY reject TYPE GNBCUMeasurementID PRESENCE mandatory }| + { ID id-gNBDUMeasurementID CRITICALITY ignore TYPE GNBUDMeasurementID PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- Resource Status Failure +-- +-- ***** + +``` + +``` + +ResourceStatusFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { ResourceStatusFailureIEs } }, + ... +} + +``` + +``` + +ResourceStatusFailureIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-gNBCUMeasurementID CRITICALITY reject TYPE GNBCUMeasurementID PRESENCE mandatory }| + +``` + +``` + + { ID id-gNBDUMeasurementID CRITICALITY ignore TYPE GNBDMeasurementID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- Resource Status Reporting ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- Resource Status Update + +-- + +-- \*\*\*\*\* + +``` + +ResourceStatusUpdate ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ ResourceStatusUpdateIEs}}, + ... +} + +``` + +``` + +ResourceStatusUpdateIEs FLAP-PROTOCOL-IES ::= { + +``` + +``` + + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-gNBCUMeasurementID CRITICALITY reject TYPE GNBCUMeasurementID PRESENCE mandatory }| + { ID id-gNBDUMeasurementID CRITICALITY ignore TYPE GNBDUMeasurementID PRESENCE mandatory }| + { ID id-HardwareLoadIndicator CRITICALITY ignore TYPE HardwareLoadIndicator PRESENCE optional }| + { ID id-TNLCapacityIndicator CRITICALITY ignore TYPE TNLCapacityIndicator PRESENCE optional }| + { ID id-CellMeasurementResultList CRITICALITY ignore TYPE CellMeasurementResultList PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- Access And Mobility Indication ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- Access And Mobility Indication + +-- + +-- \*\*\*\*\* + +``` + +AccessAndMobilityIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { AccessAndMobilityIndicationIEs } }, + ... +} + +``` + +} + +AccessAndMobilityIndicationIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + +{ ID id-RAReportList CRITICALITY ignore TYPE RAReportList PRESENCE optional }| + +{ ID id-RLFReportInformationList CRITICALITY ignore TYPE RLFReportInformationList PRESENCE optional }| + +{ ID id-SuccessfulHOReportInformationList CRITICALITY ignore TYPE SuccessfulHOReportInformationList PRESENCE optional }| + +{ ID id-SuccessfulPSCellChangeReportInformationList CRITICALITY ignore TYPE SuccessfulPSCellChangeReportInformationList PRESENCE optional }, + +... + +} + +-- \*\*\*\*\* + +-- + +-- REFERENCE TIME INFORMATION REPORTING CONTROL + +-- + +-- \*\*\*\*\* + +ReferenceTimeInformationReportingControl ::= SEQUENCE { + +protocolIEs ProtocolIE-Container { { ReferenceTimeInformationReportingControlIEs } }, + +... + +} + +ReferenceTimeInformationReportingControlIEs FLAP-PROTOCOL-IES ::= { + +``` + + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-ReportingRequestType CRITICALITY reject TYPE ReportingRequestType PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- REFERENCE TIME INFORMATION REPORT +-- +-- ***** + +``` + +``` + +ReferenceTimeInformationReport ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { ReferenceTimeInformationReportIEs } }, + ... +} + +``` + +``` + +ReferenceTimeInformationReportIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY ignore TYPE TransactionID PRESENCE mandatory }| + { ID id-TimeReferenceInformation CRITICALITY ignore TYPE TimeReferenceInformation PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- Access Success +-- +-- ***** + +``` + +``` + +AccessSuccess ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ AccessSuccessIEs}}, + ... +} + +``` + +``` + +AccessSuccessIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FLAP-ID CRITICALITY reject TYPE GNB-CU-UE-FLAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FLAP-ID CRITICALITY reject TYPE GNB-DU-UE-FLAP-ID PRESENCE mandatory }| + { ID id-NRCGI CRITICALITY reject TYPE NRCGI PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- POSITIONING ASSISTANCE INFORMATION CONTROL ELEMENTARY PROCEDURE +-- +-- ***** + +``` + +``` + +-- ***** +-- +-- Positioning Assistance Information Control +-- +-- ***** + +``` + +``` + +PositioningAssistanceInformationControl ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PositioningAssistanceInformationControlIEs } }, + ... +} + +``` + +``` + +PositioningAssistanceInformationControlIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory } | + { ID id-PosAssistance-Information CRITICALITY reject TYPE PosAssistance-Information PRESENCE optional } | + { ID id-PosBroadcast CRITICALITY reject TYPE PosBroadcast PRESENCE optional } | + { ID id-PositioningBroadcastCells CRITICALITY reject TYPE PositioningBroadcastCells PRESENCE optional } | + { ID id-RoutingID CRITICALITY reject TYPE RoutingID PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- POSITIONING ASSISTANCE INFORMATION FEEDBACK ELEMENTARY PROCEDURE + +``` + +``` + +-- +-- ***** +-- +-- ***** +-- +-- Positioning Assistance Information Feedback +-- +-- ***** + +``` + +``` + +PositioningAssistanceInformationFeedback ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ PositioningAssistanceInformationFeedbackIEs}}, + ... +} + +``` + +``` + +PositioningAssistanceInformationFeedbackIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-PosAssistanceInformationFailureList CRITICALITY reject TYPE PosAssistanceInformationFailureList PRESENCE optional}| + { ID id-PositioningBroadcastCells CRITICALITY reject TYPE PositioningBroadcastCells PRESENCE optional}| + { ID id-RoutingID CRITICALITY reject TYPE RoutingID PRESENCE optional}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}| + ... +} + +``` + +``` + +-- ***** + +``` + +``` + +-- +-- POSITIONING MEASUREMENT EXCHANGE ELEMENTARY PROCEDURE +-- +-- ***** +-- +-- ***** +-- +-- Positioning Measurement Request +-- +-- ***** + +``` + +``` + +PositioningMeasurementRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PositioningMeasurementRequestIEs } }, + ... +} + +``` + +``` + +PositioningMeasurementRequestIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory}| + { ID id-LMF-MeasurementID CRITICALITY reject TYPE LMF-MeasurementID PRESENCE mandatory}| + { ID id-RAN-MeasurementID CRITICALITY reject TYPE RAN-MeasurementID PRESENCE mandatory}| + { ID id-TRP-MeasurementRequestList CRITICALITY reject TYPE TRP-MeasurementRequestList PRESENCE mandatory}| + { ID id-PosReportCharacteristics CRITICALITY reject TYPE PosReportCharacteristics PRESENCE mandatory}| + { ID id-PosMeasurementPeriodicity CRITICALITY reject TYPE MeasurementPeriodicity PRESENCE conditional }| + +``` + +-- The above IE shall be present if the PosReportCharacteristics IE is set to "periodic" -- + +``` + +{ ID id-PosMeasurementQuantities CRITICALITY reject TYPE PosMeasurementQuantities PRESENCE mandatory}| +{ ID id-SFNInitialisationTime CRITICALITY ignore TYPE RelativeTime1900 PRESENCE optional }| +{ ID id-SRSConfiguration CRITICALITY ignore TYPE SRSConfiguration PRESENCE optional}| +{ ID id-MeasurementBeamInfoRequest CRITICALITY ignore TYPE MeasurementBeamInfoRequest PRESENCE optional }| +{ ID id-SystemFrameNumber CRITICALITY ignore TYPE SystemFrameNumber PRESENCE optional}| +{ ID id-SlotNumber CRITICALITY ignore TYPE SlotNumber PRESENCE optional}| +{ ID id-PosMeasurementPeriodicityExtended CRITICALITY reject TYPE MeasurementPeriodicityExtended PRESENCE conditional }| +-- The IE shall be present the MeasurementPeriodicity IE is set to the value "extended" + +{ ID id-ResponseTime CRITICALITY ignore TYPE ResponseTime PRESENCE optional}| +{ ID id-MeasurementCharacteristicsRequestIndicator CRITICALITY ignore TYPE MeasurementCharacteristicsRequestIndicator PRESENCE optional}| +{ ID id-MeasurementTimeOccasion CRITICALITY ignore TYPE MeasurementTimeOccasion PRESENCE optional }| +{ ID id-PosMeasurementAmount CRITICALITY ignore TYPE PosMeasurementAmount PRESENCE optional }, +... +} + +-- ***** +-- +-- Positioning Measurement Response +-- +-- ***** + +``` + +``` + +PositioningMeasurementResponse ::= SEQUENCE { + +``` + +``` + +protocolIEs ProtocolIE-Container { { PositioningMeasurementResponseIEs } }, +... +} + +``` + +``` + +PositioningMeasurementResponseIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory}| + { ID id-LMF-MeasurementID CRITICALITY reject TYPE LMF-MeasurementID PRESENCE mandatory}| + { ID id-RAN-MeasurementID CRITICALITY reject TYPE RAN-MeasurementID PRESENCE mandatory}| + { ID id-PosMeasurementResultList CRITICALITY reject TYPE PosMeasurementResultList PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- Positioning Measurement Failure +-- +-- ***** + +``` + +``` + +PositioningMeasurementFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PositioningMeasurementFailureIEs } }, + ... +} + +``` + +``` + +} + +PositioningMeasurementFailureIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-LMF-MeasurementID CRITICALITY reject TYPE LMF-MeasurementID PRESENCE mandatory }| + { ID id-RAN-MeasurementID CRITICALITY reject TYPE RAN-MeasurementID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- POSITIONING MEASUREMENT REPORT ELEMENTARY PROCEDURE +-- +-- ***** + +-- ***** +-- +-- Positioning Measurement Report +-- +-- ***** + +``` + +``` + +PositioningMeasurementReport ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PositioningMeasurementReportIEs } }, + ... +} + +``` + +``` + +PositioningMeasurementReportIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-LMF-MeasurementID CRITICALITY reject TYPE LMF-MeasurementID PRESENCE mandatory }| + { ID id-RAN-MeasurementID CRITICALITY reject TYPE RAN-MeasurementID PRESENCE mandatory }| + { ID id-PosMeasurementResultList CRITICALITY reject TYPE PosMeasurementResultList PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- POSITIONING MEASUREMENT ABORT ELEMENTARY PROCEDURE +-- +-- ***** +-- +-- ***** +-- +-- Positioning Measurement Abort +-- +-- ***** + +``` + +``` + +PositioningMeasurementAbort ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PositioningMeasurementAbortIEs } }, + ... +} + +``` + +``` + +PositioningMeasurementAbortIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory } | + { ID id-LMF-MeasurementID CRITICALITY reject TYPE LMF-MeasurementID PRESENCE mandatory } | + { ID id-RAN-MeasurementID CRITICALITY reject TYPE RAN-MeasurementID PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- POSITIONING MEASUREMENT FAILURE INDICATION ELEMENTARY PROCEDURE +-- +-- ***** +-- +-- ***** +-- +-- Positioning Measurement Failure Indication +-- +-- ***** + +``` + +``` + +PositioningMeasurementFailureIndication := SEQUENCE { + protocolIEs ProtocolIE-Container { { PositioningMeasurementFailureIndicationIEs } }, + ... +} + +``` + +``` + +PositioningMeasurementFailureIndicationIEs FLAP-PROTOCOL-IES := { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-LMF-MeasurementID CRITICALITY reject TYPE LMF-MeasurementID PRESENCE mandatory }| + { ID id-RAN-MeasurementID CRITICALITY reject TYPE RAN-MeasurementID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- POSITIONING MEASUREMENT UPDATE ELEMENTARY PROCEDURE +-- +-- ***** + +-- ***** +-- +-- Positioning Measurement Update +-- + +``` + +-- \*\*\*\*\* + +``` + +PositioningMeasurementUpdate ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PositioningMeasurementUpdateIEs } }, + ... +} + +``` + +``` + +PositioningMeasurementUpdateIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-LMF-MeasurementID CRITICALITY reject TYPE LMF-MeasurementID PRESENCE mandatory }| + { ID id-RAN-MeasurementID CRITICALITY reject TYPE RAN-MeasurementID PRESENCE mandatory }| + { ID id-SRSConfiguration CRITICALITY ignore TYPE SRSConfiguration PRESENCE optional}| + { ID id-TRP-MeasurementUpdateList CRITICALITY reject TYPE TRP-MeasurementUpdateList PRESENCE optional}| + { ID id-MeasurementCharacteristicsRequestIndicator CRITICALITY ignore TYPE MeasurementCharacteristicsRequestIndicator PRESENCE optional}| + { ID id-MeasurementTimeOccasion CRITICALITY ignore TYPE MeasurementTimeOccasion PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- TRP INFORMATION EXCHANGE ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +``` + +-- ***** +-- +-- TRP Information Request +-- +-- ***** + +TRPInformationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { TRPInformationRequestIEs } }, + ... +} + +TRPInformationRequestIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-TRPList CRITICALITY ignore TYPE TRPList PRESENCE optional }| + { ID id-TRPInformationTypeListTRPReq CRITICALITY reject TYPE TRPInformationTypeListTRPReq PRESENCE mandatory }, + ... +} + +TRPInformationTypeListTRPReq ::= SEQUENCE (SIZE(1.. maxnoofTRPInfoTypes)) OF ProtocolIE-SingleContainer { { TRPInformationTypeItemTRPReq } } + +TRPInformationTypeItemTRPReq FLAP-PROTOCOL-IES ::= { + { ID id-TRPInformationTypeItem CRITICALITY reject TYPE TRPInformationTypeItem PRESENCE mandatory }, + ... +} + +``` + +``` + +} + +-- ***** +-- +-- TRP Information Response +-- +-- ***** + +TRPInformationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { TRPInformationResponseIEs } }, + ... +} + +TRPInformationResponseIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-TRPInformationListTRPResp CRITICALITY ignore TYPE TRPInformationListTRPResp PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +TRPInformationListTRPResp ::= SEQUENCE (SIZE(1.. maxnoofTRPs)) OF ProtocolIE-SingleContainer { { TRPInformationItemTRPResp } } + +TRPInformationItemTRPResp FLAP-PROTOCOL-IES ::= { + +``` + +``` +{ ID id-TRPInformationItem CRITICALITY ignore TYPE TRPInformationItem PRESENCE mandatory }, +... +} + +-- ***** +-- +-- TRP Information Failure +-- +-- ***** + +TRPInformationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { TRPInformationFailureIEs } }, + ... +} + +TRPInformationFailureIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} +``` + +``` + +-- ***** +-- +-- POSITIONING INFORMATION EXCHANGE ELEMENTARY PROCEDURE +-- +-- ***** + +-- ***** +-- +-- Positioning Information Request +-- +-- ***** + +``` + +``` + +PositioningInformationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PositioningInformationRequestIEs } }, + ... +} + +``` + +``` + +PositioningInformationRequestIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FLAP-ID CRITICALITY reject TYPE GNB-CU-UE-FLAP-ID PRESENCE mandatory } | + { ID id-gNB-DU-UE-FLAP-ID CRITICALITY reject TYPE GNB-DU-UE-FLAP-ID PRESENCE mandatory } | + { ID id-RequestedSRSTransmissionCharacteristics CRITICALITY ignore TYPE RequestedSRSTransmissionCharacteristics PRESENCE optional} | + { ID id-UEReportingInformation CRITICALITY ignore TYPE UEReportingInformation PRESENCE optional} | + { ID id-SRSPosRRcInactiveQueryIndication CRITICALITY ignore TYPE SRSPosRRcInactiveQueryIndication PRESENCE optional}, + ... +} + +``` + +``` + +} + +-- ***** +-- +-- Positioning Information Response +-- +-- ***** + +PositioningInformationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PositioningInformationResponseIEs } }, + ... +} + +PositioningInformationResponseIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FLAP-ID CRITICALITY reject TYPE GNB-CU-UE-FLAP-ID PRESENCE mandatory } | + { ID id-gNB-DU-UE-FLAP-ID CRITICALITY reject TYPE GNB-DU-UE-FLAP-ID PRESENCE mandatory } | + { ID id-SRSConfiguration CRITICALITY ignore TYPE SRSConfiguration PRESENCE optional } | + { ID id-SFNInitialisationTime CRITICALITY ignore TYPE RelativeTime1900 PRESENCE optional } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } | + { ID id-SRSPosRRCInactiveConfig CRITICALITY ignore TYPE SRSPosRRCInactiveConfig PRESENCE optional }, + ... +} + +``` + +``` +-- ***** +-- +-- Positioning Information Failure +-- +-- ***** +``` + +``` +PositioningInformationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PositioningInformationFailureIEs } }, + ... +} +``` + +``` +PositioningInformationFailureIEs FLAP-PROTOCOL-IES ::= { + + { ID id-gNB-CU-UE-FLAP-ID CRITICALITY reject TYPE GNB-CU-UE-FLAP-ID PRESENCE mandatory } | + { ID id-gNB-DU-UE-FLAP-ID CRITICALITY reject TYPE GNB-DU-UE-FLAP-ID PRESENCE mandatory } | + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} +``` + +``` +-- ***** +``` + +``` + +-- +-- POSITIONING ACTIVATION PROCEDURE +-- +-- ***** +-- +-- ***** +-- +-- Positioning Activation Request +-- +-- ***** + +``` + +``` + +PositioningActivationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PositioningActivationRequestIEs } }, + ... +} + +``` + +``` + +PositioningActivationRequestIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FLAP-ID CRITICALITY reject TYPE GNB-CU-UE-FLAP-ID PRESENCE mandatory } | + { ID id-gNB-DU-UE-FLAP-ID CRITICALITY reject TYPE GNB-DU-UE-FLAP-ID PRESENCE mandatory } | + { ID id-SRSType CRITICALITY reject TYPE SRSType PRESENCE mandatory } | + { ID id-ActivationTime CRITICALITY ignore TYPE RelativeTime1900 PRESENCE optional }, + ... +} + +``` + +``` +SRSType ::= CHOICE { + semipersistentSRS SemipersistentSRS, + aperiodicSRS AperiodicSRS, + choice-extension ProtocolIE-SingleContainer { { SRSType-ExtIEs } } +} + +SRSType-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +SemipersistentSRS ::= SEQUENCE { + sRSResourceSetID SRSResourceSetID, + sRSPatialRelation SpatialRelationInfo OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SemipersistentSRS-ExtIEs } } OPTIONAL, + ... +} + +SemipersistentSRS-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-SRSPatialRelationPerSRSResource CRITICALITY ignore EXTENSION SpatialRelationPerSRSResource PRESENCE optional }, + ... +} + +AperiodicSRS ::= SEQUENCE { + aperiodic ENUMERATED { true, ... }, +``` + +``` + + sRSResourceTrigger SRSResourceTrigger OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {AperiodicSRS-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +AperiodicSRS-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +-- ***** +-- +-- Positioning Activation Response +-- +-- ***** + +``` + +``` + +PositioningActivationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PositioningActivationResponseIEs} }, + ... +} + +``` + +``` + +PositioningActivationResponseIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory } | + +``` + +``` + + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-SystemFrameNumber CRITICALITY ignore TYPE SystemFrameNumber PRESENCE optional }| + { ID id-SlotNumber CRITICALITY ignore TYPE SlotNumber PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- Positioning Activation Failure +-- +-- ***** + +``` + +``` + +PositioningActivationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PositioningActivationFailureIEs } }, + ... +} + +``` + +``` + +PositioningActivationFailureIEs FlAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + +``` + +``` + + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- POSITIONING DEACTIVATION PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- Positioning Deactivation + +-- + +-- \*\*\*\*\* + +``` + +PositioningDeactivation ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PositioningDeactivationIEs } }, + ... +} + +``` + +``` + +PositioningDeactivationIEs FLAP-PROTOCOL-IES ::= { + +``` + +``` + + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-AbortTransmission CRITICALITY ignore TYPE AbortTransmission PRESENCE mandatory }, + ... +} + +``` + +-- \*\*\*\*\* + +-- +-- POSITIONING INFORMATION UPDATE PROCEDURE + +-- +-- \*\*\*\*\* + +-- +-- \*\*\*\*\* + +-- Positioning Information Update + +-- +-- \*\*\*\*\* + +``` + +PositioningInformationUpdate ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PositioningInformationUpdateIEs } }, + ... +} + +``` + +PositioningInformationUpdateIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-gNB-CU-UE-FlAP-ID      CRITICALITY reject    TYPE GNB-CU-UE-FlAP-ID      PRESENCE mandatory } | + { ID id-gNB-DU-UE-FlAP-ID      CRITICALITY reject    TYPE GNB-DU-UE-FlAP-ID      PRESENCE mandatory } | + { ID id-SRSConfiguration        CRITICALITY ignore    TYPE SRSConfiguration            PRESENCE optional } | + { ID id-SFNInitialisationTime    CRITICALITY ignore    TYPE RelativeTime1900            PRESENCE optional }, + ... + +} + +-- \*\*\*\*\* + +-- + +-- E-CID MEASUREMENT PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- E-CID Measurement Initiation Request + +-- + +-- \*\*\*\*\* + +E-CIDMeasurementInitiationRequest ::= SEQUENCE { + +protocolIEs      ProtocolIE-Container    {{E-CIDMeasurementInitiationRequest-IEs}}, + ... + +} + +``` + +E-CIDMeasurementInitiationRequest-IEs FLAP-PROTOCOL-IES ::= { + + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-LMF-UE-MeasurementID CRITICALITY reject TYPE LMF-UE-MeasurementID PRESENCE mandatory }| + { ID id-RAN-UE-MeasurementID CRITICALITY reject TYPE RAN-UE-MeasurementID PRESENCE mandatory }| + { ID id-E-CID-ReportCharacteristics CRITICALITY reject TYPE E-CID-ReportCharacteristics PRESENCE mandatory }| + { ID id-E-CID-MeasurementPeriodicity CRITICALITY reject TYPE MeasurementPeriodicity PRESENCE conditional }| + +-- The above IE shall be present if the E-CID-ReportCharacteristics IE is set to "periodic" -- + + { ID id-E-CID-MeasurementQuantities CRITICALITY reject TYPE E-CID-MeasurementQuantities PRESENCE mandatory}| + + { ID id-PosMeasurementPeriodicityNR-AoA CRITICALITY reject TYPE PosMeasurementPeriodicityNR-AoA PRESENCE conditional}, + +-- The IE shall be present if the E-CID-ReportCharacteristics IE is set to "periodic" and the E-CID-MeasurementQuantities-Item IE in the E-CID-MeasurementQuantities IE is set to the value "angleOfArrivalNR"-- + + ... + +} + +``` + +-- \*\*\*\*\* + +-- + +-- E-CID Measurement Initiation Response + +-- + +-- \*\*\*\*\* + +``` + +E-CIDMeasurementInitiationResponse ::= SEQUENCE { + + protocolIEs ProtocolIE-Container {{E-CIDMeasurementInitiationResponse-IEs}}, + + ... +} + +``` + +``` + +} + +E-CIDMeasurementInitiationResponse-IEs FLAP-PROTOCOL-IEs ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-LMF-UE-MeasurementID CRITICALITY reject TYPE LMF-UE-MeasurementID PRESENCE mandatory }| + { ID id-RAN-UE-MeasurementID CRITICALITY reject TYPE RAN-UE-MeasurementID PRESENCE mandatory }| + { ID id-E-CID-MeasurementResult CRITICALITY ignore TYPE E-CID-MeasurementResult PRESENCE optional}| + { ID id-Cell-Portion-ID CRITICALITY ignore TYPE Cell-Portion-ID PRESENCE optional}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}, + ... +} + +-- ***** +-- +-- E-CID Measurement Initiation Failure +-- +-- ***** + +E-CIDMeasurementInitiationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {E-CIDMeasurementInitiationFailure-IEs}, + ... +} + +``` + +``` + +E-CIDMeasurementInitiationFailure-IEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-LMF-UE-MeasurementID CRITICALITY reject TYPE LMF-UE-MeasurementID PRESENCE mandatory }| + { ID id-RAN-UE-MeasurementID CRITICALITY reject TYPE RAN-UE-MeasurementID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}, + ... +} + +``` + +``` + +-- ***** +-- +-- E-CID MEASUREMENT FAILURE INDICATION PROCEDURE +-- +-- ***** + +-- ***** +-- +-- E-CID Measurement Failure Indication +-- +-- ***** + +``` + +``` + +E-CIDMeasurementFailureIndication ::= SEQUENCE { + +``` + +``` + +protocolIEs ProtocolIE-Container {{E-CIDMeasurementFailureIndication-IEs}}, +... +} + +E-CIDMeasurementFailureIndication-IEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FLAP-ID CRITICALITY reject TYPE GNB-CU-UE-FLAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FLAP-ID CRITICALITY reject TYPE GNB-DU-UE-FLAP-ID PRESENCE mandatory }| + { ID id-LMF-UE-MeasurementID CRITICALITY reject TYPE LMF-UE-MeasurementID PRESENCE mandatory }| + { ID id-RAN-UE-MeasurementID CRITICALITY reject TYPE RAN-UE-MeasurementID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}, + ... +} + +``` + +``` + +-- ***** +-- +-- E-CID MEASUREMENT REPORT PROCEDURE +-- +-- ***** + +-- ***** +-- +-- E-CID Measurement Report +-- +-- + +``` + +-- \*\*\*\*\* + +E-CIDMeasurementReport ::= SEQUENCE { + +    protocolIEs                    ProtocolIE-Container          {{E-CIDMeasurementReport-IEs}}, +    ... +} + +E-CIDMeasurementReport-IEs FLAP-PROTOCOL-IES ::= { + +    { ID id-gNB-CU-UE-FlAP-ID          CRITICALITY reject  TYPE GNB-CU-UE-FlAP-ID          PRESENCE mandatory }| +    { ID id-gNB-DU-UE-FlAP-ID          CRITICALITY reject  TYPE GNB-DU-UE-FlAP-ID          PRESENCE mandatory }| +    { ID id-LMF-UE-MeasurementID      CRITICALITY reject  TYPE LMF-UE-MeasurementID          PRESENCE mandatory }| +    { ID id-RAN-UE-MeasurementID      CRITICALITY reject  TYPE RAN-UE-MeasurementID          PRESENCE mandatory }| +    { ID id-E-CID-MeasurementResult  CRITICALITY ignore  TYPE E-CID-MeasurementResult          PRESENCE mandatory }| +    { ID id-Cell-Portion-ID          CRITICALITY ignore  TYPE Cell-Portion-ID          PRESENCE optional}, +    ... +} + +-- \*\*\*\*\* + +-- +-- E-CID MEASUREMENT TERMINATION PROCEDURE +-- + +-- \*\*\*\*\* + +``` + +-- ***** +-- +-- E-CID Measurement Termination Command +-- +-- ***** + +``` + +``` + +E-CIDMeasurementTerminationCommand ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{E-CIDMeasurementTerminationCommand-IEs}}, + ... +} + +``` + +``` + +E-CIDMeasurementTerminationCommand-IEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-LMF-UE-MeasurementID CRITICALITY reject TYPE LMF-UE-MeasurementID PRESENCE mandatory }| + { ID id-RAN-UE-MeasurementID CRITICALITY reject TYPE RAN-UE-MeasurementID PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- + +``` + +-- BROADCAST CONTEXT SETUP ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- BROADCAST CONTEXT SETUP REQUEST + +-- + +-- \*\*\*\*\* + +BroadcastContextSetupRequest ::= SEQUENCE { + +    protocolIEs          ProtocolIE-Container    { { BroadcastContextSetupRequestIEs } }, + +    ... + +} + +BroadcastContextSetupRequestIEs FLAP-PROTOCOL-IES ::= { + +| | | | | | | +|--------------------------------------|--------------------|------|------------------------------|--------------------|--| +| { ID id-gNB-CU-MBS-FLAP-ID | CRITICALITY reject | TYPE | GNB-CU-MBS-FLAP-ID | PRESENCE mandatory | | +| { ID id-MBS-Session-ID | CRITICALITY reject | TYPE | MBS-Session-ID | PRESENCE mandatory | | +| { ID id-MBS-ServiceArea | CRITICALITY reject | TYPE | MBS-ServiceArea | PRESENCE optional | | +| { ID id-MBS-CUtoDURRCInformation | CRITICALITY reject | TYPE | MBS-CUtoDURRCInformation | PRESENCE mandatory | | +| { ID id-SNSSAI | CRITICALITY reject | TYPE | SNSSAI | PRESENCE mandatory | | +| { ID id-BroadcastMRBs-ToBeSetup-List | CRITICALITY reject | TYPE | BroadcastMRBs-ToBeSetup-List | PRESENCE mandatory | | +| { ID id-SupportedUETypeList | CRITICALITY ignore | TYPE | SupportedUETypeList | PRESENCE optional | | +| { ID id-AssociatedSessionID | CRITICALITY ignore | TYPE | AssociatedSessionID | PRESENCE optional | | + +``` + + ... +} + +BroadcastMRBs-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { BroadcastMRBs-ToBeSetup-ItemIEs} } + +BroadcastMRBs-ToBeSetup-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-BroadcastMRBs-ToBeSetup-Item CRITICALITY reject TYPE BroadcastMRBs-ToBeSetup-Item PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- BROADCAST CONTEXT SETUP RESPONSE +-- +-- ***** + +``` + +``` + +BroadcastContextSetupResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BroadcastContextSetupResponseIEs} }, + ... +} + +``` + +``` + +BroadcastContextSetupResponseIEs FLAP-PROTOCOL-IES ::= { + +``` + +``` + + { ID id-gNB-CU-MBS-FlAP-ID CRITICALITY reject TYPE GNB-CU-MBS-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-MBS-FlAP-ID CRITICALITY reject TYPE GNB-DU-MBS-FlAP-ID PRESENCE mandatory }| + { ID id-BroadcastMRBs-Setup-List CRITICALITY reject TYPE BroadcastMRBs-Setup-List PRESENCE mandatory }| + { ID id-BroadcastMRBs-FailedToBeSetup-List CRITICALITY ignore TYPE BroadcastMRBs-FailedToBeSetup-List PRESENCE optional }| + { ID id-BroadcastAreaScope CRITICALITY ignore TYPE BroadcastAreaScope PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + { ID id-FlUTunnelNotEstablished CRITICALITY ignore TYPE FlUTunnelNotEstablished PRESENCE optional}, + ... +} + +BroadcastMRBs-Setup-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { BroadcastMRBs-Setup-ItemIEs} } + +BroadcastMRBs-FailedToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { BroadcastMRBs-FailedToBeSetup-ItemIEs} } + +BroadcastMRBs-Setup-ItemIEs FlAP-PROTOCOL-IES ::= { + { ID id-BroadcastMRBs-Setup-Item CRITICALITY reject TYPE BroadcastMRBs-Setup-Item PRESENCE mandatory}, + ... +} + +BroadcastMRBs-FailedToBeSetup-ItemIEs FlAP-PROTOCOL-IES ::= { + { ID id-BroadcastMRBs-FailedToBeSetup-Item CRITICALITY ignore TYPE BroadcastMRBs-FailedToBeSetup-Item PRESENCE mandatory}, ... +} + +``` + +``` + +-- ***** +-- +-- BROADCAST CONTEXT SETUP FAILURE +-- +-- ***** + +``` + +``` + +BroadcastContextSetupFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BroadcastContextSetupFailureIEs } }, + ... +} + +``` + +``` + +BroadcastContextSetupFailureIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-MBS-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-MBS-FlAP-ID CRITICALITY ignore TYPE GNB-DU-UE-FlAP-ID PRESENCE optional }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- BROADCAST CONTEXT RELEASE ELEMENTARY PROCEDURE +-- +-- ***** + +``` + +``` + +-- ***** +-- +-- BROADCAST CONTEXT RELEASE COMMAND +-- +-- ***** + +``` + +``` + +BroadcastContextReleaseCommand ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BroadcastContextReleaseCommandIEs } }, + ... +} + +``` + +``` + +BroadcastContextReleaseCommandIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-MBS-FLAP-ID CRITICALITY reject TYPE GNB-CU-MBS-FLAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-MBS-FLAP-ID CRITICALITY reject TYPE GNB-DU-MBS-FLAP-ID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- BROADCAST CONTEXT RELEASE COMPLETE +-- +-- ***** + +``` + +``` + +BroadcastContextReleaseComplete ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BroadcastContextReleaseCompleteIEs } }, + ... +} + +``` + +``` + +BroadcastContextReleaseCompleteIEs F1AP-PROTOCOL-IES ::= { + { ID id-gNB-CU-MBS-F1AP-ID CRITICALITY reject TYPE GNB-CU-MBS-F1AP-ID PRESENCE mandatory } | + { ID id-gNB-DU-MBS-F1AP-ID CRITICALITY reject TYPE GNB-DU-MBS-F1AP-ID PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- BROADCAST CONTEXT RELEASE REQUEST ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- BROADCAST CONTEXT RELEASE REQUEST + +-- + +-- \*\*\*\*\* + +BroadcastContextReleaseRequest ::= SEQUENCE { + +    protocolIEs          ProtocolIE-Container      {{ BroadcastContextReleaseRequestIEs}}, + +    ... + +} + +BroadcastContextReleaseRequestIEs FLAP-PROTOCOL-IES ::= { + +    { ID id-gNB-CU-MBS-FlAP-ID                  CRITICALITY reject  TYPE GNB-CU-MBS-FlAP-ID          PRESENCE mandatory  }| + +    { ID id-gNB-DU-MBS-FlAP-ID                  CRITICALITY reject  TYPE GNB-DU-MBS-FlAP-ID          PRESENCE mandatory  }| + +    { ID id-Cause                                CRITICALITY ignore  TYPE Cause                      PRESENCE mandatory  }, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- BROADCAST CONTEXT MODIFICATION ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- BROADCAST CONTEXT MODIFICATION REQUEST + +-- + +-- \*\*\*\*\* + +BroadcastContextModificationRequest ::= SEQUENCE { + +    protocolIEs          ProtocolIE-Container    { { BroadcastContextModificationRequestIEs } }, + +    ... + +} + +BroadcastContextModificationRequestIEs FLAP-PROTOCOL-IES ::= { + +    { ID id-gNB-CU-MBS-FLAP-ID                  CRITICALITY reject  TYPE GNB-CU-MBS-FLAP-ID                  PRESENCE mandatory  }| + +    { ID id-gNB-DU-MBS-FLAP-ID                  CRITICALITY reject  TYPE GNB-DU-MBS-FLAP-ID                  PRESENCE mandatory  }| + +    { ID id-MBS-ServiceArea                    CRITICALITY reject  TYPE MBS-ServiceArea                    PRESENCE optional   }| + +    { ID id-MBS-CUtoDURRCInformation          CRITICALITY reject  TYPE MBS-CUtoDURRCInformation          PRESENCE mandatory  }| + +    { ID id-BroadcastMRBs-ToBeSetupMod-List    CRITICALITY reject  TYPE BroadcastMRBs-ToBeSetupMod-List    PRESENCE optional }| + +    { ID id-BroadcastMRBs-ToBeModified-List    CRITICALITY reject  TYPE BroadcastMRBs-ToBeModified-List    PRESENCE optional }| + +    { ID id-BroadcastMRBs-ToBeReleased-List    CRITICALITY reject  TYPE BroadcastMRBs-ToBeReleased-List    PRESENCE optional }| + +    { ID id-SupportedUETypeList                CRITICALITY ignore  TYPE SupportedUETypeList                PRESENCE optional }, + +    ... + +} + +BroadcastMRBs-ToBeSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { BroadcastMRBs-ToBeSetupMod-ItemIEs } } + +BroadcastMRBs-ToBeModified-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { BroadcastMRBs-ToBeModified-ItemIEs } } + +BroadcastMRBs-ToBeReleased-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { BroadcastMRBs-ToBeReleased-ItemIEs } } + +``` + +BroadcastMRBs-ToBeSetupMod-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-BroadcastMRBs-ToBeSetupMod-Item CRITICALITY reject TYPE BroadcastMRBs-ToBeSetupMod-Item PRESENCE mandatory}, + ... +} + +``` + +``` + +BroadcastMRBs-ToBeModified-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-BroadcastMRBs-ToBeModified-Item CRITICALITY reject TYPE BroadcastMRBs-ToBeModified-Item PRESENCE mandatory}, + ... +} + +``` + +``` + +BroadcastMRBs-ToBeReleased-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-BroadcastMRBs-ToBeReleased-Item CRITICALITY reject TYPE BroadcastMRBs-ToBeReleased-Item PRESENCE mandatory}, + ... +} + +``` + +``` + +-- ***** +-- +-- BROADCAST CONTEXT MODIFICATION RESPONSE +-- +-- ***** + +``` + +``` + +BroadcastContextModificationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BroadcastContextModificationResponseIEs } }, + +``` + +``` + + ... +} + +BroadcastContextModificationResponseIEs FLAP-PROTOCOL-IEs ::= { + { ID id-gNB-CU-MBS-FLAP-ID CRITICALITY reject TYPE GNB-CU-MBS-FLAP-ID PRESENCE mandatory}| + { ID id-gNB-DU-MBS-FLAP-ID CRITICALITY reject TYPE GNB-DU-MBS-FLAP-ID PRESENCE mandatory}| + + { ID id-BroadcastMRBs-SetupMod-List CRITICALITY reject TYPE BroadcastMRBs-SetupMod-List PRESENCE optional}| + { ID id-BroadcastMRBs-FailedToBeSetupMod-List CRITICALITY ignore TYPE BroadcastMRBs-FailedToBeSetupMod-List PRESENCE optional}| + { ID id-BroadcastMRBs-Modified-List CRITICALITY reject TYPE BroadcastMRBs-Modified-List PRESENCE optional}| + { ID id-BroadcastMRBs-FailedToBeModified-List CRITICALITY ignore TYPE BroadcastMRBs-FailedToBeModified-List PRESENCE optional}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}| + { ID id-BroadcastAreaScope CRITICALITY ignore TYPE BroadcastAreaScope PRESENCE optional}| + ... +} + +BroadcastMRBs-SetupMod-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { BroadcastMRBs-SetupMod-ItemIEs } } + +BroadcastMRBs-FailedToBeSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { BroadcastMRBs-FailedToBeSetupMod-ItemIEs } } + +BroadcastMRBs-Modified-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { BroadcastMRBs-Modified-ItemIEs } } + +``` + +``` + +BroadcastMRBs-FailedToBeModified-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { BroadcastMRBs-FailedToBeModified-ItemIEs } } + +``` + +``` + +BroadcastMRBs-SetupMod-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-BroadcastMRBs-SetupMod-Item CRITICALITY reject TYPE BroadcastMRBs-SetupMod-Item PRESENCE mandatory}, + ... +} + +``` + +``` + +BroadcastMRBs-FailedToBeSetupMod-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-BroadcastMRBs-FailedToBeSetupMod-Item CRITICALITY ignore TYPE BroadcastMRBs-FailedToBeSetupMod-Item PRESENCE mandatory}, + ... +} + +``` + +``` + +BroadcastMRBs-Modified-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-BroadcastMRBs-Modified-Item CRITICALITY reject TYPE BroadcastMRBs-Modified-Item PRESENCE mandatory}, + ... +} + +``` + +``` + +BroadcastMRBs-FailedToBeModified-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-BroadcastMRBs-FailedToBeModified-Item CRITICALITY ignore TYPE BroadcastMRBs-FailedToBeModified-Item PRESENCE mandatory}, + ... +} + +``` + +``` + +-- ***** + +``` + +``` + +-- +-- BROADCAST CONTEXT MODIFICATION FAILURE +-- +-- ***** + +``` + +``` + +BroadcastContextModificationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { BroadcastContextModificationFailureIEs } }, + ... +} + +``` + +``` + +BroadcastContextModificationFailureIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-MBS-FLAP-ID CRITICALITY reject TYPE GNB-CU-MBS-FLAP-ID PRESENCE mandatory } | + { ID id-gNB-DU-MBS-FLAP-ID CRITICALITY reject TYPE GNB-DU-MBS-FLAP-ID PRESENCE mandatory } | + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- BROADCAST TRANSPORT RESOURCE REQUEST ELEMENTARY PROCEDURE +-- +-- ***** + +``` + +``` +-- ***** +-- +-- BROADCAST TRANSPORT RESOURCE REQUEST +-- +-- ***** +``` + +``` +BroadcastTransportResourceRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ BroadcastTransportResourceRequestIEs }}, + ... +} +``` + +``` +BroadcastTransportResourceRequestIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-MBS-FlAP-ID CRITICALITY reject TYPE GNB-CU-MBS-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-MBS-FlAP-ID CRITICALITY reject TYPE GNB-DU-MBS-FlAP-ID PRESENCE mandatory }, + ... +} +``` + +``` +-- ***** +-- +-- Multicast Group Paging PROCEDURE +-- +-- ***** +``` + +``` +-- ***** +-- +-- Multicast Group Paging +-- +-- ***** +``` + +``` +MulticastGroupPaging ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ MulticastGroupPagingIEs}}, + ... +} +``` + +``` +MulticastGroupPagingIEs FLAP-PROTOCOL-IES ::= { + { ID id-MBS-Session-ID CRITICALITY reject TYPE MBS-Session-ID PRESENCE mandatory }| + { ID id-UEIdentity-List-For-Paging-List CRITICALITY ignore TYPE UEIdentity-List-For-Paging-List PRESENCE optional }| + { ID id-MC-PagingCell-List CRITICALITY ignore TYPE MC-PagingCell-list PRESENCE optional }| + { ID id-IndicationMCInactiveReception CRITICALITY ignore TYPE IndicationMCInactiveReception PRESENCE optional }, + ... +} +``` + +``` +UEIdentity-List-For-Paging-List ::= SEQUENCE (SIZE(1.. maxnoofUEIDforPaging)) OF ProtocolIE-SingleContainer { { UEIdentity-List-For-Paging-ItemIEs +} } +``` + +``` + +UEIdentity-List-For-Paging-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-UEIdentity-List-For-Paging-Item CRITICALITY ignore TYPE UEIdentity-List-For-Paging-Item PRESENCE optional } , + ... +} + +``` + +``` + +MC-PagingCell-list ::= SEQUENCE (SIZE(1.. maxnoofPagingCells)) OF ProtocolIE-SingleContainer { { MC-PagingCell-ItemIEs } } + +``` + +``` + +MC-PagingCell-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-MC-PagingCell-Item CRITICALITY ignore TYPE MC-PagingCell-Item PRESENCE mandatory} , + ... +} + +``` + +-- \*\*\*\*\* + +-- +-- MULTICAST CONTEXT SETUP ELEMENTARY PROCEDURE + +-- +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- +-- MULTICAST CONTEXT SETUP REQUEST + +-- +-- \*\*\*\*\* + +MulticastContextSetupRequest ::= SEQUENCE { +    protocolIEs          ProtocolIE-Container    {{ MulticastContextSetupRequestIEs }}, +    ... +} + +MulticastContextSetupRequestIEs FLAP-PROTOCOL-IES ::= { +    { ID id-gNB-CU-MBS-FLAP-ID                  CRITICALITY reject  TYPE    GNB-CU-MBS-FLAP-ID                  PRESENCE mandatory }| +    { ID id-MBS-Session-ID                      CRITICALITY reject  TYPE    MBS-Session-ID                      PRESENCE mandatory }| +    { ID id-MBS-ServiceArea                    CRITICALITY reject  TYPE    MBS-ServiceArea                    PRESENCE optional  }| +    { ID id-SNSSAI                              CRITICALITY reject  TYPE    SNSSAI                              PRESENCE mandatory }| +    { ID id-MulticastMRBs-ToBeSetup-List          CRITICALITY reject  TYPE    MulticastMRBs-ToBeSetup-List          PRESENCE mandatory }| +    { ID id-MulticastCU2DURRCCInfo              CRITICALITY reject  TYPE    MulticastCU2DURRCCInfo              PRESENCE optional  }| +    { ID id-MBSMulticastSessionReceptionState    CRITICALITY reject  TYPE    MBSMulticastSessionReceptionState    PRESENCE optional  }, +    ... +} + +MulticastMRBs-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { MulticastMRBs-ToBeSetup-ItemIEs } } + +MulticastMRBs-ToBeSetup-ItemIEs FLAP-PROTOCOL-IES ::= { +    { ID id-MulticastMRBs-ToBeSetup-Item  CRITICALITY reject  TYPE    MulticastMRBs-ToBeSetup-Item  PRESENCE mandatory  }, + +``` + + ... + } + + -- ***** + -- + -- MULTICAST CONTEXT SETUP RESPONSE + -- + -- ***** + +MulticastContextSetupResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ MulticastContextSetupResponseIEs }}, + ... +} + +MulticastContextSetupResponseIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-MBS-FlAP-ID CRITICALITY reject TYPE GNB-CU-MBS-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-MBS-FlAP-ID CRITICALITY reject TYPE GNB-DU-MBS-FlAP-ID PRESENCE mandatory }| + { ID id-MulticastMRBs-Setup-List CRITICALITY reject TYPE MulticastMRBs-Setup-List PRESENCE mandatory }| + { ID id-MulticastMRBs-FailedToBeSetup-List CRITICALITY ignore TYPE MulticastMRBs-FailedToBeSetup-List PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + { ID id-MulticastDU2CURRCInfo CRITICALITY reject TYPE MulticastDU2CURRCInfo PRESENCE optional }, + ... +} + +``` + +MulticastMRBs-Setup-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { MulticastMRBs-Setup-ItemIEs} } + +MulticastMRBs-FailedToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { MulticastMRBs-FailedToBeSetup-ItemIEs} } + +MulticastMRBs-Setup-ItemIEs FIAP-PROTOCOL-IES ::= { + +{ ID id-MulticastMRBs-Setup-Item CRITICALITY reject TYPE MulticastMRBs-Setup-Item PRESENCE mandatory}, + +... + +} + +MulticastMRBs-FailedToBeSetup-ItemIEs FIAP-PROTOCOL-IES ::= { + +{ ID id-MulticastMRBs-FailedToBeSetup-Item CRITICALITY ignore TYPE MulticastMRBs-FailedToBeSetup-Item PRESENCE mandatory}, + +... + +} + +-- \*\*\*\*\* + +-- + +-- MULTICAST CONTEXT SETUP FAILURE + +-- + +-- \*\*\*\*\* + +MulticastContextSetupFailure ::= SEQUENCE { + +protocolIEs ProtocolIE-Container {{ MulticastContextSetupFailureIEs}}, + +... +} + +MulticastContextSetupFailureIEs FLAP-PROTOCOL-IES ::= { + +| | | | | +|--------------------------------|--------------------|-----------------------------|----------------------| +| { ID id-gNB-CU-MBS-FlAP-ID | CRITICALITY reject | TYPE GNB-CU-MBS-FlAP-ID | PRESENCE mandatory } | +| { ID id-gNB-DU-MBS-FlAP-ID | CRITICALITY ignore | TYPE GNB-DU-MBS-FlAP-ID | PRESENCE optional } | +| { ID id-Cause | CRITICALITY ignore | TYPE Cause | PRESENCE mandatory } | +| { ID id-CriticalityDiagnostics | CRITICALITY ignore | TYPE CriticalityDiagnostics | PRESENCE optional }, | + +... + +} + +-- \*\*\*\*\* + +-- + +-- MULTICAST CONTEXT RELEASE ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- MULTICAST CONTEXT RELEASE COMMAND + +-- + +-- \*\*\*\*\* + +``` + +MulticastContextReleaseCommand ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ MulticastContextReleaseCommandIEs}}, + ... +} + +``` + +``` + +MulticastContextReleaseCommandIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-MBS-FlAP-ID CRITICALITY reject TYPE GNB-CU-MBS-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-MBS-FlAP-ID CRITICALITY reject TYPE GNB-DU-MBS-FlAP-ID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- MULTICAST CONTEXT RELEASE COMPLETE +-- +-- ***** + +``` + +``` + +MulticastContextReleaseComplete ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ MulticastContextReleaseCompleteIEs}}, + ... +} + +``` + +MulticastContextReleaseCompleteIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-gNB-CU-MBS-FlAP-ID                      CRITICALITY reject TYPE GNB-CU-MBS-FlAP-ID              PRESENCE mandatory }| + +{ ID id-gNB-DU-MBS-FlAP-ID                      CRITICALITY reject TYPE GNB-DU-MBS-FlAP-ID              PRESENCE mandatory }| + +{ ID id-CriticalityDiagnostics                    CRITICALITY ignore TYPE CriticalityDiagnostics            PRESENCE optional }, + +... + +} + +-- \*\*\*\*\* + +-- + +-- MULTICAST CONTEXT RELEASE REQUEST ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- MULTICAST CONTEXT RELEASE REQUEST + +-- + +-- \*\*\*\*\* + +MulticastContextReleaseRequest ::= SEQUENCE { + +protocolIEs                      ProtocolIE-Container              {{ MulticastContextReleaseRequestIEs }}, + +... +} + +MulticastContextReleaseRequestIEs FLAP-PROTOCOL-IES ::= { + +| | | | | +|----------------------------|--------------------|-------------------------|-----------------------| +| { ID id-gNB-CU-MBS-FlAP-ID | CRITICALITY reject | TYPE GNB-CU-MBS-FlAP-ID | PRESENCE mandatory } | +| { ID id-gNB-DU-MBS-FlAP-ID | CRITICALITY reject | TYPE GNB-DU-MBS-FlAP-ID | PRESENCE mandatory } | +| { ID id-Cause | CRITICALITY ignore | TYPE Cause | PRESENCE mandatory }, | + +... +} + +-- \*\*\*\*\* + +-- + +-- MULTICAST CONTEXT MODIFICATION ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- MULTICAST CONTEXT MODIFICATION REQUEST + +-- + +-- \*\*\*\*\* + +``` + +MulticastContextModificationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { MulticastContextModificationRequestIEs } }, + ... +} + +MulticastContextModificationRequestIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-MBS-FlAP-ID CRITICALITY reject TYPE GNB-CU-MBS-FlAP-ID PRESENCE mandatory } | + { ID id-gNB-DU-MBS-FlAP-ID CRITICALITY reject TYPE GNB-DU-MBS-FlAP-ID PRESENCE mandatory } | + { ID id-MBS-ServiceArea CRITICALITY reject TYPE MBS-ServiceArea PRESENCE optional } | + { ID id-MulticastMRBs-ToBeSetupMod-List CRITICALITY reject TYPE MulticastMRBs-ToBeSetupMod-List PRESENCE optional } | + { ID id-MulticastMRBs-ToBeModified-List CRITICALITY reject TYPE MulticastMRBs-ToBeModified-List PRESENCE optional } | + { ID id-MulticastMRBs-ToBeReleased-List CRITICALITY reject TYPE MulticastMRBs-ToBeReleased-List PRESENCE optional } | + { ID id-MulticastCU2DURRCInfo CRITICALITY reject TYPE MulticastCU2DURRCInfo PRESENCE optional } | + { ID id-MBSMulticastSessionReceptionState CRITICALITY reject TYPE MBSMulticastSessionReceptionState PRESENCE optional }, + ... +} + +MulticastMRBs-ToBeSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { MulticastMRBs-ToBeSetupMod-ItemIEs } } + +MulticastMRBs-ToBeSetupMod-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-MulticastMRBs-ToBeSetupMod-Item CRITICALITY reject TYPE MulticastMRBs-ToBeSetupMod-Item PRESENCE mandatory }, + ... +} + +MulticastMRBs-ToBeModified-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { MulticastMRBs-ToBeModified-ItemIEs } } + +``` + +``` + +MulticastMRBs-ToBeModified-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-MulticastMRBs-ToBeModified-Item CRITICALITY reject TYPE MulticastMRBs-ToBeModified-Item PRESENCE mandatory}, + ... +} + +MulticastMRBs-ToBeReleased-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { MulticastMRBs-ToBeReleased-ItemIEs} } + +MulticastMRBs-ToBeReleased-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-MulticastMRBs-ToBeReleased-Item CRITICALITY reject TYPE MulticastMRBs-ToBeReleased-Item PRESENCE mandatory}, + ... +} + +-- ***** +-- +-- MULTICAST CONTEXT MODIFICATION RESPONSE +-- +-- ***** + +MulticastContextModificationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ MulticastContextModificationResponseIEs}}, + ... +} + +``` + +``` + +MulticastContextModificationResponseIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-MBS-FLAP-ID CRITICALITY reject TYPE GNB-CU-MBS-FLAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-MBS-FLAP-ID CRITICALITY reject TYPE GNB-DU-MBS-FLAP-ID PRESENCE mandatory }| + { ID id-MulticastMRBs-SetupMod-List CRITICALITY reject TYPE MulticastMRBs-SetupMod-List PRESENCE optional }| + { ID id-MulticastMRBs-FailedToBeSetupMod-List CRITICALITY ignore TYPE MulticastMRBs-FailedToBeSetupMod-List PRESENCE optional }| + { ID id-MulticastMRBs-Modified-List CRITICALITY reject TYPE MulticastMRBs-Modified-List PRESENCE optional }| + { ID id-MulticastMRBs-FailedToBeModified-List CRITICALITY ignore TYPE MulticastMRBs-FailedToBeModified-List PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + { ID id-MulticastDU2CURRCInfo CRITICALITY reject TYPE MulticastDU2CURRCInfo PRESENCE optional }, + ... +} + +MulticastMRBs-SetupMod-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { MulticastMRBs-SetupMod-ItemIEs } } + +MulticastMRBs-SetupMod-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-MulticastMRBs-SetupMod-Item CRITICALITY reject TYPE MulticastMRBs-SetupMod-Item PRESENCE mandatory}, + ... +} + +MulticastMRBs-FailedToBeSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { MulticastMRBs-FailedToBeSetupMod-ItemIEs } } + +MulticastMRBs-FailedToBeSetupMod-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-MulticastMRBs-FailedToBeSetupMod-Item CRITICALITY ignore TYPE MulticastMRBs-FailedToBeSetupMod-Item PRESENCE mandatory}, + ... +} + +``` + +MulticastMRBs-Modified-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { MulticastMRBs-Modified-ItemIEs } } + +MulticastMRBs-Modified-ItemIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-MulticastMRBs-Modified-Item CRITICALITY reject TYPE MulticastMRBs-Modified-Item PRESENCE mandatory}, +... +} + +MulticastMRBs-FailedToBeModified-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { MulticastMRBs-FailedToBeModified-ItemIEs } } + +MulticastMRBs-FailedToBeModified-ItemIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-MulticastMRBs-FailedToBeModified-Item CRITICALITY ignore TYPE MulticastMRBs-FailedToBeModified-Item PRESENCE mandatory}, +... +} + +-- \*\*\*\*\* + +-- + +-- MULTICAST CONTEXT MODIFICATION FAILURE + +-- + +-- \*\*\*\*\* + +MulticastContextModificationFailure ::= SEQUENCE { + +protocolIEs ProtocolIE-Container {{ MulticastContextModificationFailureIEs}}, +... +} + +MulticastContextModificationFailureIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-gNB-CU-MBS-FLAP-ID                    CRITICALITY reject    TYPE GNB-CU-MBS-FLAP-ID            PRESENCE mandatory }| + +{ ID id-gNB-DU-MBS-FLAP-ID                    CRITICALITY reject    TYPE GNB-DU-MBS-FLAP-ID            PRESENCE mandatory }| + +{ ID id-Cause                                    CRITICALITY ignore    TYPE Cause                            PRESENCE mandatory }| + +{ ID id-CriticalityDiagnostics                CRITICALITY ignore    TYPE CriticalityDiagnostics        PRESENCE optional }, + +... + +} + +-- \*\*\*\*\* + +-- + +-- MULTICAST CONTEXT NOTIFICATION PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- MULTICAST CONTEXT NOTIFICATION INDICATION + +-- + +-- \*\*\*\*\* + +MulticastContextNotificationIndication ::= SEQUENCE { + +protocolIEs                    ProtocolIE-Container            {MulticastContextNotificationIndicationIEs}}, + +``` + + ... + } + + MulticastContextNotificationIndicationIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-MBS-FlAP-ID CRITICALITY reject TYPE GNB-CU-MBS-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-MBS-FlAP-ID CRITICALITY reject TYPE GNB-DU-MBS-FlAP-ID PRESENCE mandatory }| + { ID id-MulticastDU2CURRCInfo CRITICALITY reject TYPE MulticastDU2CURRCInfo PRESENCE optional }, + ... + } + +``` + +``` + +-- ***** +-- +-- MULTICAST CONTEXT NOTIFICATION CONFIRM +-- +-- ***** + +``` + +``` + +MulticastContextNotificationConfirm ::= SEQUENCE { + protocolIEs ProtocolIE-Container {MulticastContextNotificationConfirmIEs}, + ... +} + +``` + +``` + +MulticastContextNotificationConfirmIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-MBS-FlAP-ID CRITICALITY reject TYPE GNB-CU-MBS-FlAP-ID PRESENCE mandatory }| + +``` + +``` + + { ID id-gNB-DU-MBS-FlAP-ID CRITICALITY reject TYPE GNB-DU-MBS-FlAP-ID PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- MULTICAST CONTEXT NOTIFICATION REFUSE +-- +-- ***** + +``` + +``` + +MulticastContextNotificationRefuse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {MulticastContextNotificationRefuseIEs}, + ... +} + +``` + +``` + +MulticastContextNotificationRefuseIEs FlAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-MBS-FlAP-ID CRITICALITY reject TYPE GNB-CU-MBS-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-MBS-FlAP-ID CRITICALITY reject TYPE GNB-DU-MBS-FlAP-ID PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- MULTICAST COMMON CONFIGURATION PROCEDURE +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- MULTICAST COMMON CONFIGURATION REQUEST +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +MulticastCommonConfigurationRequest ::= SEQUENCE { +``` + +``` + protocolIEs ProtocolIE-Container {{MulticastCommonConfigurationRequestIEs}}, +``` + +``` + ... +``` + +``` +} +``` + +``` +MulticastCommonConfigurationRequestIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-MulticastCU2DUCommonRRcInfo CRITICALITY reject TYPE MulticastCU2DUCommonRRcInfo PRESENCE optional }, +``` + +``` + ... +``` + +``` +} +``` + +``` + +-- ***** +-- +-- MULTICAST COMMON CONFIGURATION RESPONSE +-- +-- ***** + +``` + +``` + +MulticastCommonConfigurationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{MulticastCommonConfigurationResponseIEs}}, + ... +} + +``` + +``` + +MulticastCommonConfigurationResponseIEs FLAP-PROTOCOL-IES ::= { + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- MULTICAST COMMON CONFIGURATION REFUSE +-- +-- ***** + +``` + +MulticastCommonConfigurationRefuse ::= SEQUENCE { + +    protocolIEs          ProtocolIE-Container    {{MulticastCommonConfigurationRefuseIEs}}, + +    ... + +} + +MulticastCommonConfigurationRefuseIEs FIAP-PROTOCOL-IES ::= { + +    { ID id-Cause                                  CRITICALITY ignore  TYPE Cause                          PRESENCE mandatory  }| + +    { ID id-CriticalityDiagnostics              CRITICALITY ignore  TYPE CriticalityDiagnostics                  PRESENCE optional  }, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- MULTICAST DISTRIBUTION SETUP ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- MULTICAST DISTRIBUTION SETUP REQUEST + +-- + +-- \*\*\*\*\* + +MulticastDistributionSetupRequest ::= SEQUENCE { + +    protocolIEs          ProtocolIE-Container      {{ MulticastDistributionSetupRequestIEs}}, + +    ... + +} + +MulticastDistributionSetupRequestIEs FLAP-PROTOCOL-IES ::= { + +    { ID id-gNB-CU-MBS-FlAP-ID                  CRITICALITY reject  TYPE GNB-CU-MBS-FlAP-ID                  PRESENCE mandatory  }| + +    { ID id-gNB-DU-MBS-FlAP-ID                  CRITICALITY reject  TYPE GNB-DU-MBS-FlAP-ID                  PRESENCE mandatory  }| + +    { ID id-MBSSMulticastFlUContextDescriptor  CRITICALITY reject  TYPE MBSSMulticastFlUContextDescriptor  PRESENCE mandatory  }| + +    { ID id-MulticastFlUContext-ToBeSetup-List  CRITICALITY reject  TYPE MulticastFlUContext-ToBeSetup-List  PRESENCE mandatory  }, + +    ... + +} + +MulticastFlUContext-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF + +                                                          ProtocolIE-SingleContainer { { MulticastFlUContext-ToBeSetup-ItemIEs} } + +MulticastFlUContext-ToBeSetup-ItemIEs FLAP-PROTOCOL-IES ::= { + +    { ID id-MulticastFlUContext-ToBeSetup-Item  CRITICALITY      reject  TYPE MulticastFlUContext-ToBeSetup-Item          PRESENCE +mandatory}, + +    ... + +} + +-- \*\*\*\*\* + +-- + +``` +-- MULTICAST DISTRIBUTION SETUP RESPONSE +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +MulticastDistributionSetupResponse ::= SEQUENCE { +``` + +``` + protocolIEs ProtocolIE-Container {{ MulticastDistributionSetupResponseIEs }}, +``` + +``` + ... +``` + +``` +} +``` + +``` +MulticastDistributionSetupResponseIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-gNB-CU-MBS-FLAP-ID CRITICALITY reject TYPE GNB-CU-MBS-FLAP-ID PRESENCE mandatory}| +``` + +``` + { ID id-gNB-DU-MBS-FLAP-ID CRITICALITY reject TYPE GNB-DU-MBS-FLAP-ID PRESENCE mandatory}| +``` + +``` + { ID id-MBSMulticastFlUContextDescriptor CRITICALITY reject TYPE MBSMulticastFlUContextDescriptor PRESENCE mandatory}| +``` + +``` + { ID id-MulticastFlUContext-Setup-List CRITICALITY reject TYPE MulticastFlUContext-Setup-List PRESENCE mandatory}| +``` + +``` + { ID id-MulticastFlUContext-FailedToBeSetup-List CRITICALITY ignore TYPE MulticastFlUContext-FailedToBeSetup-List PRESENCE optional}| +``` + +``` + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| +``` + +``` + { ID id-MulticastFlUContextReferenceCU CRITICALITY reject TYPE MulticastFlUContextReferenceCU PRESENCE mandatory}, +``` + +``` + ... +``` + +``` +} +``` + +``` +MulticastFlUContext-Setup-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF ProtocolIE-SingleContainer { { MulticastFlUContext-Setup-ItemIEs } } +``` + +``` +MulticastFlUContext-Setup-ItemIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-MulticastFlUContext-Setup-Item CRITICALITY reject TYPE MulticastFlUContext-Setup-Item PRESENCE mandatory}, +``` + +``` + ... +``` + +``` + +} + +MulticastFlUContext-FailedToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofMRBs)) OF + ProtocolIE-SingleContainer { { MulticastFlUContext-FailedToBeSetup-ItemIEs} } + +MulticastFlUContext-FailedToBeSetup-ItemIEs FLAP-PROTOCOL-IES ::= { + + { ID id-MulticastFlUContext-FailedToBeSetup-Item CRITICALITY ignore TYPE MulticastFlUContext-FailedToBeSetup-Item PRESENCE mandatory}, + + ... + +} + +-- ***** +-- +-- MULTICAST DISTRIBUTION SETUP FAILURE +-- +-- ***** + +MulticastDistributionSetupFailure ::= SEQUENCE { + + protocolIEs ProtocolIE-Container {{ MulticastDistributionSetupFailureIEs}}, + + ... + +} + +MulticastDistributionSetupFailureIEs FLAP-PROTOCOL-IES ::= { + + { ID id-gNB-CU-MBS-FlAP-ID CRITICALITY reject TYPE GNB-CU-MBS-FlAP-ID PRESENCE mandatory }| + + { ID id-gNB-DU-MBS-FlAP-ID CRITICALITY ignore TYPE GNB-DU-MBS-FlAP-ID PRESENCE optional }| + + { ID id-MBSMulticastFlUContextDescriptor CRITICALITY reject TYPE MBSMulticastFlUContextDescriptor PRESENCE mandatory }| + +``` + +``` + + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- MULTICAST DISTRIBUTION RELEASE ELEMENTARY PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- MULTICAST DISTRIBUTION RELEASE COMMAND + +-- + +-- \*\*\*\*\* + +``` + +MulticastDistributionReleaseCommand := SEQUENCE { + protocolIEs ProtocolIE-Container {{ MulticastDistributionReleaseCommandIEs }}, + ... +} + +``` + +MulticastDistributionReleaseCommandIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-gNB-CU-MBS-FlAP-ID                      CRITICALITY reject    TYPE GNB-CU-MBS-FlAP-ID                      PRESENCE mandatory    }| + +{ ID id-gNB-DU-MBS-FlAP-ID                      CRITICALITY reject    TYPE GNB-DU-MBS-FlAP-ID                      PRESENCE mandatory    }| + +{ ID id-MBSMulticastFlUContextDescriptor    CRITICALITY reject    TYPE MBSMulticastFlUContextDescriptor    PRESENCE mandatory    }| + +{ ID id-Cause                                            CRITICALITY ignore    TYPE Cause                                            PRESENCE mandatory    }, + +... + +} + +-- \*\*\*\*\* + +-- + +-- MULTICAST DISTRIBUTION RELEASE COMPLETE + +-- + +-- \*\*\*\*\* + +MulticastDistributionReleaseComplete ::= SEQUENCE { + +protocolIEs                      ProtocolIE-Container            {{ MulticastDistributionReleaseCompleteIEs}}, + +... + +} + +MulticastDistributionReleaseCompleteIEs FLAP-PROTOCOL-IES ::= { + +{ ID id-gNB-CU-MBS-FlAP-ID                      CRITICALITY reject    TYPE GNB-CU-MBS-FlAP-ID                      PRESENCE mandatory    }| + +{ ID id-gNB-DU-MBS-FlAP-ID                      CRITICALITY reject    TYPE GNB-DU-MBS-FlAP-ID                      PRESENCE mandatory    }| + +{ ID id-MBSMulticastFlUContextDescriptor    CRITICALITY reject    TYPE MBSMulticastFlUContextDescriptor    PRESENCE mandatory    }| + +``` + + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- PDC MEASUREMENT PROCEDURE +-- +-- ***** +-- +-- ***** +-- +-- PDC Measurement Initiation Request +-- +-- ***** + +``` + +``` + +PDCMeasurementInitiationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{PDCMeasurementInitiationRequest-IEs}}, + ... +} + +``` + +``` + +PDCMeasurementInitiationRequest-IEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory } | + +``` + +``` + + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-PDC-MeasID CRITICALITY reject TYPE RAN-UE-PDC-MeasID PRESENCE mandatory }| + { ID id-PDCReportType CRITICALITY reject TYPE PDCReportType PRESENCE mandatory }| + { ID id-PDCMeasurementPeriodicity CRITICALITY reject TYPE PDCMeasurementPeriodicity PRESENCE conditional }| + +``` + +-- The above IE shall be present if the PDCReportType IE is set to "periodic" -- + +``` + + { ID id-PDCMeasurementQuantities CRITICALITY reject TYPE PDCMeasurementQuantities PRESENCE mandatory }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- PDC Measurement Initiation Response + +-- + +-- \*\*\*\*\* + +``` + +PDCMeasurementInitiationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{PDCMeasurementInitiationResponse-IEs}}, + ... +} + +``` + +PDCMeasurementInitiationResponse-IEs FlAP-PROTOCOL-IEs ::= { + +``` + + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-PDC-MeasID CRITICALITY reject TYPE RAN-UE-PDC-MeasID PRESENCE mandatory }| + +``` + +``` + + { ID id-PDCMeasurementResult CRITICALITY ignore TYPE PDCMeasurementResult PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +-- ***** +-- +-- PDC Measurement Initiation Failure +-- +-- ***** + +PDCMeasurementInitiationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{PDCMeasurementInitiationFailure-IEs}}, + ... +} + +PDCMeasurementInitiationFailure-IEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-PDC-MeasID CRITICALITY ignore TYPE RAN-UE-PDC-MeasID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- PDC MEASUREMENT REPORT PROCEDURE +-- +-- ***** + +-- ***** +-- +-- PDC Measurement Report +-- +-- ***** + +``` + +``` + +PDCMeasurementReport ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{PDCMeasurementReport-IEs}}, + ... +} + +``` + +``` + +PDCMeasurementReport-IEs F1AP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-F1AP-ID CRITICALITY reject TYPE GNB-CU-UE-F1AP-ID PRESENCE mandatory } | + { ID id-gNB-DU-UE-F1AP-ID CRITICALITY reject TYPE GNB-DU-UE-F1AP-ID PRESENCE mandatory } | + { ID id-RAN-UE-PDC-MeasID CRITICALITY reject TYPE RAN-UE-PDC-MeasID PRESENCE mandatory } | + { ID id-PDCMeasurementResult CRITICALITY ignore TYPE PDCMeasurementResult PRESENCE mandatory }, + ... +} + +``` + +``` + +} + +-- ***** +-- +-- PDC MEASUREMENT TERMINATION PROCEDURE +-- +-- ***** + +-- ***** +-- +-- PDC Measurement Termination +-- +-- ***** + +PDCMeasurementTerminationCommand ::= SEQUENCE { + protocolIEs ProtocolIE-Container { { PDCMeasurementTerminationCommand-IEs } }, + ... +} + +PDCMeasurementTerminationCommand-IEs FLAP-PROTOCOL-IEs ::= { + { ID id-gNB-CU-UE-F1AP-ID CRITICALITY reject TYPE GNB-CU-UE-F1AP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-F1AP-ID CRITICALITY reject TYPE GNB-DU-UE-F1AP-ID PRESENCE mandatory }| + { ID id-RAN-UE-PDC-MeasID CRITICALITY ignore TYPE RAN-UE-PDC-MeasID PRESENCE mandatory }, + +``` + +``` +... +} + +-- ***** +-- +-- PDC MEASUREMENT FAILURE INDICATION PROCEDURE +-- +-- ***** + +-- ***** +-- +-- PDC Measurement Failure Indication +-- +-- ***** + +PDMeasurementFailureIndication := SEQUENCE { + protocolIEs ProtocolIE-Container { { PDMeasurementFailureIndication-IEs} }, + ... +} + +PDMeasurementFailureIndication-IEs FLAP-PROTOCOL-IEs ::= { + { ID id-gNB-CU-UE-FlAP-ID CRITICALITY reject TYPE GNB-CU-UE-FlAP-ID PRESENCE mandatory } | +``` + +``` + + { ID id-gNB-DU-UE-FlAP-ID CRITICALITY reject TYPE GNB-DU-UE-FlAP-ID PRESENCE mandatory }| + { ID id-RAN-UE-PDC-MeasID CRITICALITY ignore TYPE RAN-UE-PDC-MeasID PRESENCE mandatory }| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- PPS CONFIGURATION PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- PRS CONFIGURATION REQUEST + +-- + +-- \*\*\*\*\* + +``` + +PRSConfigurationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{PRSConfigurationRequest-IEs}}, + ... +} + +``` + +``` + +PRSConfigurationRequest-IEs FlAP-PROTOCOL-IEs ::= { + +``` + +``` + + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-PRSConfigRequestType CRITICALITY reject TYPE PRSConfigRequestType PRESENCE mandatory }| + { ID id-PRSTRPLList CRITICALITY ignore TYPE PRSTRPLList PRESENCE mandatory }, + ... +} + +``` + +-- \*\*\*\*\* + +-- + +-- PRS CONFIGURATION RESPONSE + +-- + +-- \*\*\*\*\* + +``` + +PRSConfigurationResponse := SEQUENCE { + protocolIEs ProtocolIE-Container {{ PRSConfigurationResponse-IEs}}, + ... +} + +``` + +``` + +PRSConfigurationResponse-IEs FLAP-PROTOCOL-IES := { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory}| + { ID id-PRSTransmissionTRPLList CRITICALITY ignore TYPE PRSTransmissionTRPLList PRESENCE optional}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}, + ... +} + +``` + +``` + +-- ***** +-- +-- PRS CONFIGURATION FAILURE +-- +-- ***** + +``` + +``` + +PRSConfigurationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ PRSConfigurationFailure-IEs}}, + ... +} + +``` + +``` + +PRSConfigurationFailure-IEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory}| + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional}, + ... +} + +``` + +``` + +-- ***** +-- +-- MEASUREMENT PRECONFIGURATION PROCEDURE +-- +-- ***** + +``` + +``` +-- ***** +-- +-- Positioning Preconfiguration Required +-- +-- ***** +``` + +``` +MeasurementPreconfigurationRequired ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ MeasurementPreconfigurationRequired-IEs}}, + ... +} +``` + +``` +MeasurementPreconfigurationRequired-IEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FLAP-ID CRITICALITY reject TYPE GNB-CU-UE-FLAP-ID PRESENCE mandatory}| + { ID id-gNB-DU-UE-FLAP-ID CRITICALITY reject TYPE GNB-DU-UE-FLAP-ID PRESENCE mandatory}| + { ID id-TRP-PRS-Info-List CRITICALITY ignore TYPE TRP-PRS-Info-List PRESENCE mandatory}, + ... +} +``` + +``` +-- ***** +-- +-- Positioning Preconfiguration Confirm +-- +``` + +-- \*\*\*\*\* + +MeasurementPreconfigurationConfirm ::= SEQUENCE { + +    protocolIEs          ProtocolIE-Container      { { MeasurementPreconfigurationConfirm-IEs } }, +    ... +} + +MeasurementPreconfigurationConfirm-IEs FLAP-PROTOCOL-IES ::= { + +    { ID id-gNB-CU-UE-FlAP-ID          CRITICALITY reject  TYPE GNB-CU-UE-FlAP-ID          PRESENCE mandatory }| +    { ID id-gNB-DU-UE-FlAP-ID          CRITICALITY reject  TYPE GNB-DU-UE-FlAP-ID          PRESENCE mandatory }| +    { ID id-PosMeasGapPreConfigList    CRITICALITY ignore  TYPE PosMeasGapPreConfigList    PRESENCE optional }| +    { ID id-CriticalityDiagnostics     CRITICALITY ignore  TYPE CriticalityDiagnostics      PRESENCE optional }, +    ... +} + +-- \*\*\*\*\* + +-- + +-- Positioning Preconfiguration Refuse + +-- + +-- \*\*\*\*\* + +MeasurementPreconfigurationRefuse ::= SEQUENCE { + +    protocolIEs          ProtocolIE-Container      { { MeasurementPreconfigurationRefuse-IEs } }, + +    ... + +} + +MeasurementPreconfigurationRefuse-IEs FLAP-PROTOCOL-IES ::= { + +    { ID id-gNB-CU-UE-FlAP-ID          CRITICALITY reject  TYPE GNB-CU-UE-FlAP-ID          PRESENCE mandatory  }| + +    { ID id-gNB-DU-UE-FlAP-ID          CRITICALITY reject  TYPE GNB-DU-UE-FlAP-ID          PRESENCE mandatory  }| + +    { ID id-Cause                        CRITICALITY ignore  TYPE Cause                    PRESENCE mandatory  }| + +    { ID id-CriticalityDiagnostics      CRITICALITY ignore  TYPE CriticalityDiagnostics    PRESENCE optional }, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- MEASUREMENT ACTIVATION PROCEDURE + +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* + +-- + +-- Measurement Activation + +-- +-- \*\*\*\*\* + +MeasurementActivation ::= SEQUENCE { +    protocolIEs          ProtocolIE-Container    { { MeasurementActivation-IEs } }, +    ... +} + +MeasurementActivation-IEs FLAP-PROTOCOL-IES ::= { +    { ID id-gNB-CU-UE-FlAP-ID          CRITICALITY reject  TYPE GNB-CU-UE-FlAP-ID          PRESENCE mandatory } | +    { ID id-gNB-DU-UE-FlAP-ID          CRITICALITY reject  TYPE GNB-DU-UE-FlAP-ID          PRESENCE mandatory } | +    { ID id-ActivationRequestType      CRITICALITY reject  TYPE ActivationRequestType          PRESENCE mandatory} | +    { ID id-PRS-Measurement-Info-List  CRITICALITY ignore  TYPE PRS-Measurement-Info-List      PRESENCE optional}, +    ... +} + +-- \*\*\*\*\* + +-- +-- QOE INFORMATION TRANSFER + +-- +-- \*\*\*\*\* + +-- +-- \*\*\*\*\* + +-- QoE Information Transfer + +-- + +-- \*\*\*\*\* + +QoEInformationTransfer ::= SEQUENCE { + +    protocolIEs                    ProtocolIE-Container    {{QoEInformationTransfer-IEs}}, + +    ... + +} + +QoEInformationTransfer-IEs FLAP-PROTOCOL-IES ::= { + +    { ID id-gNB-CU-UE-FlAP-ID            CRITICALITY reject  TYPE GNB-CU-UE-FlAP-ID            PRESENCE mandatory  }| + +    { ID id-gNB-DU-UE-FlAP-ID            CRITICALITY reject  TYPE GNB-DU-UE-FlAP-ID            PRESENCE mandatory  }| + +    { ID id-QoEInformation              CRITICALITY ignore  TYPE QoEInformation                PRESENCE optional }, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- Positioning System information Delivery Command + +-- + +-- \*\*\*\*\* + +``` + +PosSystemInformationDeliveryCommand ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ PosSystemInformationDeliveryCommandIEs}}, + ... +} + +``` + +``` + +PosSystemInformationDeliveryCommandIEs FLAP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-NRCGI CRITICALITY reject TYPE NRCGI PRESENCE mandatory }| + { ID id-PosSItypeList CRITICALITY reject TYPE PosSItypeList PRESENCE mandatory }| + { ID id-ConfirmedUEID CRITICALITY reject TYPE GNB-DU-UE-FLAP-ID PRESENCE mandatory }, + ... +} + +``` + +``` + +-- ***** +-- +-- DU-CU Cell Switch Notification +-- +-- ***** + +``` + +``` + +DUCUCellSwitchNotification ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ DUCUCellSwitchNotificationIEs}}, + ... +} + +``` + +``` + +DUCUCellSwitchNotificationIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FLAP-ID CRITICALITY reject TYPE GNB-CU-UE-FLAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FLAP-ID CRITICALITY reject TYPE GNB-DU-UE-FLAP-ID PRESENCE mandatory }| + { ID id-NRCGI CRITICALITY reject TYPE NRCGI PRESENCE mandatory }| + { ID id-LTMCellSwitchInformation CRITICALITY ignore TYPE LTMCellSwitchInformation PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- CU-DU Cell Switch Notification +-- +-- ***** + +``` + +``` + +CUDUCellSwitchNotification ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ CUDUCellSwitchNotificationIEs}}, + ... +} + +``` + +``` + +CUDUCellSwitchNotificationIEs FLAP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-FLAP-ID CRITICALITY reject TYPE GNB-CU-UE-FLAP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-FLAP-ID CRITICALITY reject TYPE GNB-DU-UE-FLAP-ID PRESENCE mandatory }| + { ID id-NRCGI CRITICALITY reject TYPE NRCGI PRESENCE mandatory }| + +``` + +``` + + { ID id-LTMCellSwitchInformation CRITICALITY ignore TYPE LTMCellSwitchInformation PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- DU-CU TA Information Transfer +-- +-- ***** + +``` + +``` + +DUCUTAInformationTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ DUCUTAInformationTransferIEs }}, + ... +} + +``` + +``` + +DUCUTAInformationTransferIEs FLAP-PROTOCOL-IES ::= { + { ID id-TAInformation-List CRITICALITY ignore TYPE TAInformation-List PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- CU-DU TA Information Transfer + +``` + +-- +-- \*\*\*\*\* + +CUDUTInformationTransfer ::= SEQUENCE { +    protocolIEs          ProtocolIE-Container      {{ CUDUTInformationTransferIEs }}, +    ... +} + +CUDUTInformationTransferIEs FLAP-PROTOCOL-IES ::= { +    { ID id-TAInformation-List          CRITICALITY ignore  TYPE TAInformation-List          PRESENCE optional }, +    ... +} + +-- \*\*\*\*\* +-- + +-- QOE INFORMATION TRANSFER CONTROL +-- + +-- \*\*\*\*\* + +-- \*\*\*\*\* +-- + +-- QoE Information Transfer Control +-- + +-- \*\*\*\*\* + +``` + +QoEInformationTransferControl ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{QoEInformationTransferControl-IEs}}, + ... +} + +``` + +``` + +QoEInformationTransferControl-IEs FLAP-PROTOCOL-IEs ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-DeactivationIndication CRITICALITY ignore TYPE DeactivationIndication PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- RACH Indication ELEMENTARY PROCEDURE +-- +-- ***** +-- +-- ***** +-- +-- RACH Indication + +``` + +``` + +-- +-- ***** + +RachIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ RachIndication-IEs}}, + ... +} + +RachIndication-IEs FLAP-PROTOCOL-IEs ::= { + { ID id-RAReportIndicationList CRITICALITY reject TYPE RAReportIndicationList PRESENCE mandatory }, + ... +} + +-- ***** +-- +-- Timing Synchronisation Status Elementary Procedure +-- +-- ***** + +-- ***** +-- +-- TIMING SYNCHRONISATION STATUS REQUEST + +``` + +-- + +-- \*\*\*\*\* + +TimingSynchronisationStatusRequest ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    {{TimingSynchronisationStatusRequest-IEs}}, + +    ... + +} + +TimingSynchronisationStatusRequest-IEs FLAP-PROTOCOL-IES ::= { + +    { ID id-RANTSSRequestType                    CRITICALITY reject  TYPE RANTSSRequestType                    PRESENCE mandatory }, + +    ... + +} + +-- \*\*\*\*\* + +-- + +-- TIMING SYNCHRONISATION STATUS RESPONSE + +-- + +-- \*\*\*\*\* + +TimingSynchronisationStatusResponse ::= SEQUENCE { + +    protocolIEs    ProtocolIE-Container    {{TimingSynchronisationStatusResponse-IEs}}, + +    ... + +} + +``` +TimingSynchronisationStatusResponse-IEs FLAP-PROTOCOL-IEs ::= { + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +-- ***** +-- +-- TIMING SYNCHRONISATION STATUS FAILURE +-- +-- ***** + +TimingSynchronisationStatusFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{TimingSynchronisationStatusFailure-IEs}}, + ... +} + +TimingSynchronisationStatusFailure-IEs FLAP-PROTOCOL-IEs ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +-- ***** +-- +-- Timing Synchronisation Status Reporting Elementary Procedure +``` + +``` + +-- +-- ***** +-- ***** +-- +-- TIMING SYNCHRONISATION STATUS REPORT +-- +-- ***** + +``` + +``` + +TimingSynchronisationStatusReport ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ TimingSynchronisationStatusReport-IEs }}, + ... +} + +``` + +``` + +TimingSynchronisationStatusReport-IEs FLAP-PROTOCOL-IEs ::= { + { ID id-RANTimingSynchronisationStatusInfo CRITICALITY ignore TYPE RANTimingSynchronisationStatusInfo PRESENCE +mandatory }, + ... +} + +``` + +END + +-- ASN1STOP + +## 9.4.5 Information Element Definitions + +``` +-- ASN1START +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- Information Element Definitions +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +Flap-IEs { +``` + +``` + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +``` + +``` + ngran-access (22) modules (3) flap (3) version1 (1) flap-IEs (2) } +``` + +``` +DEFINITIONS AUTOMATIC TAGS ::= +``` + +``` +BEGIN +``` + +``` +IMPORTS +``` + +``` + id-gNB-CUSystemInformation, +``` + +``` + id-HandoverPreparationInformation, +``` + +``` + id-TAISliceSupportList, +``` + +``` + id-RANAC, +``` + +``` + id-BearerTypeChange, +``` + +``` + id-Coverage-Modification-Cause, +``` + +``` + id-Cell-Direction, +``` + +id-Cell-Type, +id-CellGroupConfig, +id-AvailablePLMNList, +id-PDUSessionID, +id-ULPDUSessionAggregateMaximumBitRate, +id-DC-Based-Duplication-Configured, +id-DC-Based-Duplication-Activation, +id-Duplication-Activation, +id-DLPDCPSNLength, +id-ULPDCPSNLength, +id-RLC-Status, +id-MeasurementTimingConfiguration, +id-DRB-Information, +id-QoSFlowMappingIndication, +id-ServingCellMO, +id-RLCMode, +id-ExtendedServedPLMNs-List, +id-ExtendedAvailablePLMN-List, +id-DRX-LongCycleStartOffset, +id-SelectedBandCombinationIndex, +id-SelectedFeatureSetEntryIndex, +id-Ph-InfoSCG, +id-latest-RRC-Version-Enhanced, +id-RequestedBandCombinationIndex, + +id-RequestedFeatureSetEntryIndex, +id-DRX-Config, +id-UEAssistanceInformation, +id-PDCCH-BlindDetectionSCG, +id-Requested-PDCCH-BlindDetectionSCG, +id-BPLMN-ID-Info-List, +id-NotificationInformation, +id-TNLAssociationTransportLayerAddressgNBDU, +id-portNumber, +id-AdditionalSIBMessageList, +id-IgnorePRACHConfiguration, +id-CG-Config, +id-Ph-InfoMCG, +id-AggressorgNBSetID, +id-VictimgNBSetID, +id-MeasGapSharingConfig, +id-systemInformationAreaID, +id-areaScope, +id-IntendedTDD-DL-ULConfig, +id-QosMonitoringRequest, +id-BHInfo, +id-IAB-Info-IAB-DU, +id-IAB-Info-IAB-donor-CU, +id-IAB-Barred, + +id-SIB12-message, +id-SIB13-message, +id-SIB14-message, +id-UEAssistanceInformationEUTRA, +id-SL-PHY-MAC-RLC-Config, +id-SL-ConfigDedicatedEUTRA-Info, +id-AlternativeQoSParaSetList, +id-CurrentQoSParaSetIndex, +id-CarrierList, +id-ULCarrierList, +id-FrequencyShift7p5khz, +id-SSB-PositionsInBurst, +id-NRPRACHConfig, +id-TDD-UL-DLConfigCommonNR, +id-CNPacketDelayBudgetDownlink, +id-CNPacketDelayBudgetUplink, +id-ExtendedPacketDelayBudget, +id-TSCTrafficCharacteristics, +id-AdditionalPDCPDuplicationTNL-List, +id-RLCDuplicationInformation, +id-AdditionalDuplicationIndication, +id-mdtConfiguration, +id-TraceCollectionEntityURI, +id-NID, + +id-NPNSupportInfo, +id-NPNBroadcastInformation, +id-AvailableSNPN-ID-List, +id-SIB10-message, +id-RequestedP-MaxFR2, +id-DLCarrierList, +id-ExtendedTAISliceSupportList, +id-E-CID-MeasurementQuantities-Item, +id-ConfiguredTACIndication, +id-NRCGI, +id-SFN-Offset, +id-TransmissionStopIndicator, +id-SrsFrequency, +id-EstimatedArrivalProbability, +id-Supported-MBS-FSA-ID-List, +id-TRPType, +id-SRSSpatialRelationPerSRSResource, +id-MBS-Broadcast-NeighbourCellList, +id-PDCPTerminatingNodeDLTNLAddrInfo, +id-ENBDLTNLAddress, +id-PRS-Resource-ID, +id-LocationMeasurementInformation, +id-SliceRadioResourceStatus, +id-CompositeAvailableCapacity-SUL, + +id-NR-U, +id-NR-U-Channel-List, +id-MIMOPRBusageInformation, +id-IngressNonFlterminatingTopologyIndicator, +id-NonFlterminatingTopologyIndicator, +id-EgressNonFlterminatingTopologyIndicator, +id-rBSetConfiguration, +id-frequency-Domain-HSNA-Configuration-List, +id-child-IAB-Nodes-NA-Resource-List, +id-Parent-IAB-Nodes-NA-Resource-Configuration-List, +id-uL-FreqInfo, +id-uL-Transmission-Bandwidth, +id-dL-FreqInfo, +id-dL-Transmission-Bandwidth, +id-uL-NR-Carrier-List, +id-dL-NR-Carrier-List, +id-nRFreqInfo, +id-transmission-Bandwidth, +id-nR-Carrier-List, +id-permutation, +id-M5ReportAmount, +id-M6ReportAmount, +id-M7ReportAmount, +id-SurvivalTime, + +id-PDCMeasurementQuantities-Item, +id-OnDemandPRS, +id-AoA-SearchWindow, +id-ZoAInformation, +id-ARPLocationInfo, +id-ARP-ID, +id-MultipleULAoA, +id-UL-SRS-RSRPP, +id-SRSResourcetype, +id-ExtendedAdditionalPathList, +id-LoS-NLoSInformation, +id-NumberOfTRPRxTEG, +id-NumberOfTRPRxTxTEG, +id-TRPTxTEGAssociation, +id-TRPTEGInformation, +id-TRPRx-TEGInformation, +id-TRPBeamAntennaInformation, +id-Redcap-Bcast-Information, +id-NR-TADV, +id-SDT-MAC-PHY-CG-Config, +id-CG-SDTindicatorSetup, +id-CG-SDTindicatorMod, +id-SDTRLCBearerConfiguration, +id-SRBMappingInfo, + +id-DRBMappingInfo, +id-LastUsedCellIndication, +id-Recommended-SSBs-List, +id-SSBs-withinTheCell-toBe-Activated-List, +id-SIB17-message, +id-MUSIM-GapConfig, +id-SIB20-message, +id-pathPower, +id-DU-RX-MT-RX-Extend, +id-DU-TX-MT-TX-Extend, +id-DU-RX-MT-TX-Extend, +id-DU-TX-MT-RX-Extend, +id-TAINSAGSupportList, +id-SL-RLC-ChannelToAddModList, +id-SIB15-message, +id-InterFrequencyConfig-NoGap, +id-MBSInterestIndication, +id-L571Info, +id-L1151Info, +id-SCS-480, +id-SCS-960, +id-SRSPortIndex, +id-PEISubgroupingSupportIndication, +id-NeedForGapsInfoNR, + +id-NeedForGapNCSGInfoNR, +id-NeedForGapNCSGInfoEUTRA, +id-Source-MRB-ID, +id-RedCapIndication, +id-UL-GapFR2-Config, +id-ConfigRestrictInfoDAPS, +id-MulticastFlUContextReferenceCU, +id-TwoPHRModeMCG, +id-TwoPHRModeSCG, +id-ncd-SSB-RedCapInitialBWP-SDT, +id-nrofSymbolsExtended, +id-repetitionFactorExtended, +id-startRBHopping, +id-startRBIndex, +id-transmissionCombn8, +id-ServCellInfoList, +id-Preconfigured-measurement-GAP-Request, +id-BWP-Id, +id-ExtendedResourceSymbolOffset, +id-MusimCapabilityRestrictionIndication, +id-duplicationIndication, +id-dRB-List, +id-ChannelOccupancyTimePercentageUL, +id-RadioResourceStatusNR-U, + +id-FiveG-ProSeLayer2Multipath, +id-FiveG-ProSeLayer2UEtoUERelay, +id-FiveG-ProSeLayer2UEtoUERemote, +id-TSCTrafficCharacteristicsFeedback, +id-RANfeedbacktype, +id-Mobile-TRP-LocationInformation, +id-Mobile-IAB-MT-UE-ID, +id-MobileAccessPointLocation, +id-SIBX-message, +id-PDUSetQoSParameters, +id-N6JitterInformation, +id-ECNMarkingorCongestionInformationReportingRequest, +id-ECNMarkingorCongestionInformationReportingStatus, +id-ERedcap-Bcast-Information, +id-NeedForInterruptionInfoNR, +id-LTMCells-ToBeReleased-Item, +maxNRARFCN, +maxnoofErrors, +maxnoofBPLMNs, +maxnoofBPLMNsNR, +maxnoofDLUPTNLInformation, +maxnoofNrCellBands, +maxnoofULUPTNLInformation, +maxnoofQoSFlows, + +maxnoofSliceItems, +maxnoofSIBTypes, +maxnoofSITypes, +maxCellineNB, +maxnoofExtendedBPLMNs, +maxnoofAdditionalSIBs, +maxnoofUACPLMNs, +maxnoofUACperPLMN, +maxCeilingNBDU, +maxnoofTLAs, +maxnoofGTPTLAs, +maxnoofslots, +maxnoofNonUPTrafficMappings, +maxnoofServingCells, +maxnoofServedCellsIAB, +maxnoofChildIABNodes, +maxnoofIABSTCInfo, +maxnoofSymbols, +maxnoofDUFSlots, +maxnoofHSNASlots, +maxnoofEgressLinks, +maxnoofMappingEntries, +maxnoofDSInfo, +maxnoofQoSParaSets, + +maxnoofPC5QoSFlows, +maxnoofSSBAreas, +maxnoofNRSCSs, +maxnoofPhysicalResourceBlocks, +maxnoofPhysicalResourceBlocks-1, +maxnoofPRACHconfigs, +maxnoofRAReports, +maxnoofRLFReports, +maxnoofAdditionalPDCPDuplicationTNL, +maxnoofRLCDuplicationState, +maxnoofCHOcells, +maxnoofMDTPLMNs, +maxnoofCAGsupported, +maxnoofNIDsupported, +maxnoofExtSliceItems, +maxnoofPosMeas, +maxnoofTRPInfoTypes, +maxnoofSRSTriggerStates, +maxnoofSpatialRelations, +maxnoBcastCell, +maxnoofTRPs, +maxnoofAngleInfo, +maxnooflcs-gcs-translation, +maxnoofPath, + +maxnoofMeasE-CID, +maxnoofSSBs, +maxnoSRS-ResourceSets, +maxnoSRS-ResourcePerSet, +maxnoSRS-Carriers, +maxnoSCSs, +maxnoSRS-Resources, +maxnoSRS-PosResources, +maxnoSRS-PosResourceSets, +maxnoSRS-PosResourcePerSet, +maxnoofPRS-ResourceSets, +maxnoofPRS-ResourcesPerSet, +maxNoOfMeasTRPs, +maxnoofPRSresourceSets, +maxnoofPRSresources, +maxnoofSuccessfulHOReports, +maxnoofNR-UChannelIDs, +maxServedCellforSON, +maxNeighbourCellforSON, +maxAffectedCells, +maxnoofMBSQoSFlows, +maxnoofMBSFSAAs, +maxnoofMBSAreaSessionIDs, +maxnoofMBSServiceAreaInformation, + +maxnoofTAIforMBS, +maxnoofCellsforMBS, +maxnoofIABCongInd, +maxnoofBHRLCChannels, +maxnoofTLAsIAB, +maxnoofRBsetsPerCell, +maxnoofRBsetsPerCell-1, +maxnoofNeighbourNodeCellsIAB, +maxnoofMeasPDC, +maxnoARPs, +maxnoofULAOAs, +maxNoPathExtended, +maxnoTRPTEGs, +maxFreqLayers, +maxNumResourcesPerAngle, +maxnoAzimuthAngles, +maxnoElevationAngles, +maxnoofPRSTRPs, +maxnoofQoEInformation, +maxnoofUuRLCChannels, +maxnoofPC5RLCChannels, +maxnoofSMBRValues, +maxnoofMBSSessionsofUE, +maxnoofSLdestinations, + +maxnoofNSAGs, +maxnoofSDTBearers, +maxnoofPosSITypes, +maxnoofMRBs, +maxNrofBWP, +maxnoofUETypes, +maxnoofLTMCells, +maxnoofJointorDLTCIStates, +maxnoofULTCIStates, +maxnoofTAList, +maxnoofDRBs, +maxnoofUEsInQMCTransferControlMessage, +maxnoofUEsforRAReportIndications, +maxnoofSuccessfulPSCellChangeReports, +maxnoofPeriodicities, +maxnoofThresholdMBS, +maxMBSSessionsinSessionInfoList + +FROM FlAP-Constants + +Criticality, + +``` +ProcedureCode, +ProtocolIE-ID, +TriggeringMessage + +FROM FlAP-CommonDataTypes + +ProtocolExtensionContainer{}, +FlAP-PROTOCOL-EXTENSION, +ProtocolIE-SingleContainer{}, +FlAP-PROTOCOL-IES + +FROM FlAP-Containers; + +-- A + +AbortTransmission ::= CHOICE { + sRSResourceSetID SRSResourceSetID, + releaseALL NULL, + choice-extension ProtocolIE-SingleContainer { { AbortTransmission-ExtIEs } } +} + +AbortTransmission-ExtIEs FlAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +AccessPointPosition ::= SEQUENCE { + latitudeSign ENUMERATED {north, south}, + latitude INTEGER (0..8388607), + longitude INTEGER (-8388608..8388607), + directionOfAltitude ENUMERATED {height, depth}, + altitude INTEGER (0..32767), + uncertaintySemi-major INTEGER (0..127), + uncertaintySemi-minor INTEGER (0..127), + orientationOfMajorAxis INTEGER (0..179), + uncertaintyAltitude INTEGER (0..127), + confidence INTEGER (0..100), + iE-Extensions ProtocolExtensionContainer { { AccessPointPosition-ExtIEs} } OPTIONAL +} + +AccessPointPosition-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +Activated-Cells-Mapping-List-Item ::= SEQUENCE { + nRCGIforTargetLogicalDU NRCGI OPTIONAL, + nRCGIforSourceLogicalDU NRCGI OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Activated-Cells-Mapping-List-ItemExtIEs } } OPTIONAL, + ... +} +``` + +``` +} + +Activated-Cells-Mapping-List-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +Activated-Cells-to-be-Updated-List ::= SEQUENCE (SIZE(1..maxnoofServedCellsIAB)) OF Activated-Cells-to-be-Updated-List-Item + +Activated-Cells-to-be-Updated-List-Item ::= SEQUENCE{ + nRCGI NRCGI, + iAB-DU-Cell-Resource-Configuration-Mode-Info IAB-DU-Cell-Resource-Configuration-Mode-Info, + iE-Extensions ProtocolExtensionContainer { { Activated-Cells-to-be-Updated-List-Item-ExtIEs} } OPTIONAL +} + +Activated-Cells-to-be-Updated-List-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +ActivationRequestType ::= ENUMERATED {activate, deactivate, ...} + +ActiveULBWP ::= SEQUENCE { + locationAndBandwidth INTEGER (0..37949,...), + subcarrierSpacing ENUMERATED {kHz15, kHz30, kHz60, kHz120,..., kHz480, kHz960}, + cyclicPrefix ENUMERATED {normal, extended}, +} +``` + +``` + txDirectCurrentLocation INTEGER (0..3301,...), + shift7dot5kHz ENUMERATED {true, ...} OPTIONAL, + sRSConfig SRSConfig, + iE-Extensions ProtocolExtensionContainer { { ActiveULBWP-ExtIEs} } OPTIONAL +} + +ActiveULBWP-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +AdditionalDuplicationIndication ::= ENUMERATED { + three, + four, + ... +} + +AdditionalPath-List ::= SEQUENCE (SIZE(1..maxnoofPath)) OF AdditionalPath-Item + +AdditionalPath-Item ::= SEQUENCE { + relativePathDelay RelativePathDelay, + pathQuality TRPMeasurementQuality OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { AdditionalPath-Item-ExtIEs } } OPTIONAL +} +``` + +``` +AdditionalPath-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-MultipleULAoA CRITICALITY ignore EXTENSION MultipleULAoA PRESENCE optional}| + { ID id-pathPower CRITICALITY ignore EXTENSION UL-SRS-RSRPP PRESENCE optional}, + ... +} + +ExtendedAdditionalPathList ::= SEQUENCE (SIZE (1.. maxNoPathExtended)) OF ExtendedAdditionalPathList-Item + +ExtendedAdditionalPathList-Item ::= SEQUENCE { + relativeTimeOfPath RelativePathDelay, + pathQuality TRPMeasurementQuality OPTIONAL, + multipleULAoA MultipleULAoA OPTIONAL, + pathPower UL-SRS-RSRPP OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { ExtendedAdditionalPathList-Item-ExtIEs } } OPTIONAL, + ... +} + +ExtendedAdditionalPathList-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +AdditionalPDCPDuplicationTNL-List ::= SEQUENCE (SIZE(1..maxnoofAdditionalPDCPDuplicationTNL)) OF AdditionalPDCPDuplicationTNL-Item +``` + +``` +AdditionalPDCPDuplicationTNL-Item ::=SEQUENCE { + additionalPDCPDuplicationUPTNLInformation UPTransportLayerInformation, + iE-Extensions ProtocolExtensionContainer { { AdditionalPDCPDuplicationTNL-ItemExtIEs } } OPTIONAL, + ... +} + +AdditionalPDCPDuplicationTNL-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-BHInfo CRITICALITY ignore EXTENSION BHInfo PRESENCE optional }, + ... +} + +AdditionalSIBMessageList ::= SEQUENCE (SIZE(1..maxnoofAdditionalSIBs)) OF AdditionalSIBMessageList-Item + +AdditionalSIBMessageList-Item ::= SEQUENCE { + additionalSIB OCTET STRING, + iE-Extensions ProtocolExtensionContainer { { AdditionalSIBMessageList-Item-ExtIEs } } OPTIONAL +} + +AdditionalSIBMessageList-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +AdditionalRRMPriorityIndex ::= BIT STRING (SIZE(32)) +``` + +AffectedCellsAndBeams-List ::= SEQUENCE (SIZE (1.. maxAffectedCells)) OF AffectedCellsAndBeams-Item + +AffectedCellsAndBeams-Item ::= SEQUENCE { +    nRCGI                    NRCGI, +    affectedSSB-List      AffectedSSB-List OPTIONAL, +    iE-Extensions        ProtocolExtensionContainer { { AffectedCellsAndBeams-Item-ExtIEs } } OPTIONAL, +    ... +} + +AffectedCellsAndBeams-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +AffectedSSB-List ::= SEQUENCE (SIZE (1..maxnoofSSBAreas)) OF AffectedSSB-Item + +AffectedSSB-Item ::= SEQUENCE { +    sSB-Index    INTEGER(0..63), +    iE-Extensions    ProtocolExtensionContainer { { AffectedSSB-Item-ExtIEs } } OPTIONAL, +    ... +} + +AffectedSSB-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +``` +AggressorCellList ::= SEQUENCE (SIZE(1..maxCellingNBDU)) OF AggressorCellList-Item + +AggressorCellList-Item ::= SEQUENCE { + aggressorCell-ID NRCGI, + iE-Extensions ProtocolExtensionContainer { { AggressorCellList-Item-ExtIEs } } OPTIONAL +} + +AggressorCellList-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +AggressorgNBSetID ::= SEQUENCE { + aggressorgNBSetID GNBSetID, + iE-Extensions ProtocolExtensionContainer { { AggressorgNBSetID-ExtIEs } } OPTIONAL +} + +AggressorgNBSetID-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +AllocationAndRetentionPriority ::= SEQUENCE { + priorityLevel PriorityLevel, +``` + +``` + pre-emptionCapability Pre-emptionCapability, + pre-emptionVulnerability Pre-emptionVulnerability, + iE-Extensions ProtocolExtensionContainer { {AllocationAndRetentionPriority-ExtIEs} } OPTIONAL, + ... +} + +AllocationAndRetentionPriority-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +AlternativeQoSParaSetList ::= SEQUENCE (SIZE(1..maxnoofQoSParaSets)) OF AlternativeQoSParaSetItem + +AlternativeQoSParaSetItem ::= SEQUENCE { + alternativeQoSParaSetIndex QoSParaSetIndex, + guaranteedFlowBitRateDL BitRate OPTIONAL, + guaranteedFlowBitRateUL BitRate OPTIONAL, + packetDelayBudget PacketDelayBudget OPTIONAL, + packetErrorRate PacketErrorRate OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {AlternativeQoSParaSetItem-ExtIEs} } OPTIONAL, + ... +} + +AlternativeQoSParaSetItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +} + +``` +AngleMeasurementQuality ::= SEQUENCE { + azimuthQuality INTEGER(0..255), + zenithQuality INTEGER(0..255) OPTIONAL, + resolution ENUMERATED{deg0dot1,...}, + iE-Extensions ProtocolExtensionContainer { { AngleMeasurementQuality-ExtIEs } } OPTIONAL +} +``` + +``` +AngleMeasurementQuality-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +AperiodicSRSResourceTriggerList ::= SEQUENCE (SIZE(1..maxnoofSRSTriggerStates)) OF AperiodicSRSResourceTrigger +``` + +``` +AperiodicSRSResourceTrigger ::= INTEGER (1..3) +``` + +``` +Associated-SCell-Item ::= SEQUENCE { + sCell-ID NRCGI, + iE-Extensions ProtocolExtensionContainer { { Associated-SCell-ItemExtIEs } } OPTIONAL +} +``` + +``` +Associated-SCell-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +AssociatedSessionID ::= OCTET STRING +``` + +``` +AvailablePLMNList ::= SEQUENCE (SIZE(1..maxnoofBPLMNs)) OF AvailablePLMNList-Item +``` + +``` +AvailablePLMNList-Item ::= SEQUENCE { +``` + +``` + pLMNIdentity PLMN-Identity, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { AvailablePLMNList-Item-ExtIEs} } OPTIONAL +``` + +``` +} +``` + +``` +AvailablePLMNList-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +AvailableSNPN-ID-List ::= SEQUENCE (SIZE(1..maxnoofNIDsupported)) OF AvailableSNPN-ID-List-Item +``` + +``` +AvailableSNPN-ID-List-Item ::= SEQUENCE { +``` + +``` + pLMN-Identity PLMN-Identity, +``` + +``` + availableNIDList BroadcastNIDList, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { AvailableSNPN-ID-List-ItemExtIEs} } OPTIONAL, +``` + +``` + ... +} + +AvailableSNPN-ID-List-ItemExtIEs FIAP-PROTOCOL-EXTENSION ::= { + ... +} + +AveragingWindow ::= INTEGER (0..4095, ...) + +AreaScope ::= ENUMERATED {true, ...} + +AoA-AssistanceInfo ::= SEQUENCE { + angleMeasurement AngleMeasurementType, + LCS-to-GCS-Translation LCS-to-GCS-Translation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { AoA-AssistanceInfo-ExtIEs } } OPTIONAL, + ... +} + +AoA-AssistanceInfo-ExtIEs FIAP-PROTOCOL-EXTENSION ::= { + ... +} + +AngleMeasurementType ::= CHOICE { + expected-ULAoA Expected-UL-AoA, +``` + +``` + expected-ZoA Expected-ZoA-only, + choice-extension ProtocolIE-SingleContainer { { AngleMeasurementType-ExtIEs } } +} + +AngleMeasurementType-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +AppLayerBufferLevelList ::= OCTET STRING + +ARP-ID ::= INTEGER (1..16, ...) + +ARPLocationInformation ::= SEQUENCE (SIZE (1..maxnoARPs)) OF ARPLocationInformation-Item + +ARPLocationInformation-Item ::= SEQUENCE { + aRP-ID ARP-ID, + aRPLocationType ARPLocationType, + iE-Extensions ProtocolExtensionContainer { { ARPLocationInformation-ExtIEs} } OPTIONAL, + ... +} + +ARPLocationInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +ARPLocationType ::= CHOICE { + aRPPositionRelativeGeodetic RelativeGeodeticLocation, + aRPPositionRelativeCartesian RelativeCartesianLocation, + choice-extension ProtocolIE-SingleContainer { { ARPLocationType-ExtIEs } } +} +``` + +``` +ARPLocationType-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} +``` + +-- B + +``` +BAP-Header-Rewriting-Added-List-Item ::= SEQUENCE { + ingressBAPRoutingID BAPRoutingID, + egressBAPRoutingID BAPRoutingID, + nonFlterminatingTopologyIndicator NonFlterminatingTopologyIndicator OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { BAP-Header-Rewriting-Added-List-Item-ExtIEs} } OPTIONAL +} +``` + +``` +BAP-Header-Rewriting-Added-List-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +BAP-Header-Rewriting-Removed-List-Item ::= SEQUENCE { + ingressBAPRoutingID BAPRoutingID, + iE-Extensions ProtocolExtensionContainer { { BAP-Header-Rewriting-Removed-List-Item-ExtIEs} } OPTIONAL +} + +BAP-Header-Rewriting-Removed-List-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +BandwidthSRS ::= CHOICE { + fR1 FR1-Bandwidth, + fR2 FR2-Bandwidth, + choice-extension ProtocolIE-SingleContainer {{ BandwidthSRS-ExtIEs }} +} + +BandwidthSRS-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +BAPAddress ::= BIT STRING (SIZE(10)) +``` + +BAPCtrlPDUGChannel ::= ENUMERATED {true, ...} + +BAPLayerBHRLCchannelMappingInfo ::= SEQUENCE { +    bAPLayerBHRLCchannelMappingInfoToAdd            BAPLayerBHRLCchannelMappingInfoList            OPTIONAL, +    bAPLayerBHRLCchannelMappingInfoToRemove          MappingInformationtoRemove                    OPTIONAL, +    iE-Extensions                                        ProtocolExtensionContainer { { BAPLayerBHRLCchannelMappingInfo-ExtIEs} } OPTIONAL, +    ... +} + +BAPLayerBHRLCchannelMappingInfo-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +BAPLayerBHRLCchannelMappingInfoList ::= SEQUENCE (SIZE(1..maxnoofMappingEntries)) OF BAPLayerBHRLCchannelMappingInfo-Item + +BAPLayerBHRLCchannelMappingInfo-Item ::= SEQUENCE { +    mappingInformationIndex            MappingInformationIndex, +    priorHopBAPAddress                BAPAddress            OPTIONAL, +    ingressbHRLCChannelID            BHRLCChannelID            OPTIONAL, +    nextHopBAPAddress                BAPAddress            OPTIONAL, +    egressbHRLCChannelID            BHRLCChannelID            OPTIONAL, +    iE-Extensions                        ProtocolExtensionContainer { { BAPLayerBHRLCchannelMappingInfo-ItemExtIEs} } OPTIONAL, +    ... +} + +``` +BAPlayerBHRLCchannelMappingInfo-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-IngressNonFlterminatingTopologyIndicator CRITICALITY ignore EXTENSION IngressNonFlterminatingTopologyIndicator PRESENCE +optional}| + { ID id-EgressNonFlterminatingTopologyIndicator CRITICALITY ignore EXTENSION EgressNonFlterminatingTopologyIndicator PRESENCE optional}, + ... +} + +BAPPathID ::= BIT STRING (SIZE(10)) + +BAPRoutingID ::= SEQUENCE { + bAPAddress BAPAddress, + bAPPathID BAPPathID, + iE-Extensions ProtocolExtensionContainer { { BAPRoutingIDExtIEs } } OPTIONAL +} + +BAPRoutingIDExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +BCBearerContextFlU-TNLInfo ::= CHOICE { + locationindependent MBSFlUInformation, + locationdependent LocationDependentMBSFlUInformation, + choice-extension ProtocolIE-SingleContainer { {BCBearerContextFlU-TNLInfo-ExtIEs} } +} +``` + +``` +BCBearerContextFlU-TNLInfo-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +BitRate ::= INTEGER (0..40000000000000, ...) + +BearerTypeChange ::= ENUMERATED {true, ...} + +BHRLCChannelID ::= BIT STRING (SIZE(16)) + +BHChannels-FailedToBeModified-Item ::= SEQUENCE { + bHRLCChannelID BHRLCChannelID, + cause Cause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { BHChannels-FailedToBeModified-ItemExtIEs } } OPTIONAL +} + +BHChannels-FailedToBeModified-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +BHChannels-FailedToBeSetup-Item ::= SEQUENCE { + bHRLCChannelID BHRLCChannelID, + cause Cause OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { BHChannels-FailedToBeSetup-ItemExtIEs } } OPTIONAL +} +``` + +``` +BHChannels-FailedToBeSetup-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +BHChannels-FailedToBeSetupMod-Item ::= SEQUENCE { + bHRLCChannelID bHRLCChannelID, + cause Cause OPTIONAL , + iE-Extensions ProtocolExtensionContainer { { BHChannels-FailedToBeSetupMod-ItemExtIEs } } OPTIONAL +} +``` + +``` +BHChannels-FailedToBeSetupMod-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +BHChannels-Modified-Item ::= SEQUENCE { + bHRLCChannelID bHRLCChannelID, + iE-Extensions ProtocolExtensionContainer { { BHChannels-Modified-ItemExtIEs } } OPTIONAL +} +``` + +``` +BHChannels-Modified-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +} + +BHChannels-Required-ToBeReleased-Item ::= SEQUENCE { + +bHRLCChannelID            bHRLCChannelID, + +iE-Extensions    ProtocolExtensionContainer { { BHChannels-Required-ToBeReleased-ItemExtIEs } }    OPTIONAL + +} + +BHChannels-Required-ToBeReleased-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +BHChannels-Setup-Item ::= SEQUENCE { + +bHRLCChannelID            bHRLCChannelID, + +iE-Extensions    ProtocolExtensionContainer { { BHChannels-Setup-ItemExtIEs } }    OPTIONAL + +} + +BHChannels-Setup-ItemExtIEs    FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +BHChannels-SetupMod-Item ::= SEQUENCE { + +bHRLCChannelID            bHRLCChannelID, + +iE-Extensions    ProtocolExtensionContainer { { BHChannels-SetupMod-ItemExtIEs } }    OPTIONAL + +} + +``` +BHChannels-SetupMod-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +BHChannels-ToBeModified-Item ::= SEQUENCE { + bHRLCChannelID BHRLCChannelID, + bHQoSInformation BHQoSInformation, + rLCMode RLCMode OPTIONAL, + bAPCtrlPDUGChannel BAPCtrlPDUGChannel OPTIONAL, + trafficMappingInfo TrafficMappingInfo OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { BHChannels-ToBeModified-ItemExtIEs } } OPTIONAL +} + +BHChannels-ToBeModified-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +BHChannels-ToBeReleased-Item ::= SEQUENCE { + bHRLCChannelID BHRLCChannelID, + iE-Extensions ProtocolExtensionContainer { { BHChannels-ToBeReleased-ItemExtIEs } } OPTIONAL +} + +BHChannels-ToBeReleased-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +BHChannels-ToBeSetup-Item ::= SEQUENCE { + bHRLCChannelID bHRLCChannelID, + bHQoSInformation bHQoSInformation, + rLCMode RLCMode, + bAPCtrlPDUGChannel bAPCtrlPDUGChannel OPTIONAL, + trafficMappingInfo TrafficMappingInfo OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { BHChannels-ToBeSetup-ItemExtIEs } } OPTIONAL +} + +BHChannels-ToBeSetup-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +BHChannels-ToBeSetupMod-Item ::= SEQUENCE { + bHRLCChannelID bHRLCChannelID, + bHQoSInformation bHQoSInformation, + rLCMode RLCMode, + bAPCtrlPDUGChannel bAPCtrlPDUGChannel OPTIONAL, + trafficMappingInfo TrafficMappingInfo OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { BHChannels-ToBeSetupMod-ItemExtIEs } } OPTIONAL +} +``` + +``` +BHChannels-ToBeSetupMod-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +BHInfo ::= SEQUENCE { +``` + +``` + bAProutingID BAPRoutingID OPTIONAL, +``` + +``` + egressBHRLCCHList EgressBHRLCCHList OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { BHInfo-ExtIEs} } OPTIONAL +``` + +``` +} +``` + +``` +BHInfo-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + { ID id-NonFlterminatingTopologyIndicator CRITICALITY ignore EXTENSION NonFlterminatingTopologyIndicator PRESENCE optional }, +``` + +``` + ... +``` + +``` +} +``` + +``` +BHQoSInformation ::= CHOICE { +``` + +``` + bHRLCCHQoS QoSFlowLevelQoSParameters, +``` + +``` + eUTRANBHRLCCHQoS EUTRANQoS, +``` + +``` + cPTrafficType CPTrafficType, +``` + +``` + choice-extension ProtocolIE-SingleContainer { { BHQoSInformation-ExtIEs} } +``` + +``` +} +``` + +``` +BHQoSInformation-ExtIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + ... +} + +BHRLCCHList ::= SEQUENCE (SIZE(1..maxnoofBHRLCChannels)) OF BHRLCCHItem + +BHRLCCHItem ::= SEQUENCE { + bHRLCChannelID BHRLCChannelID, + iE-Extensions ProtocolExtensionContainer {{BHRLCCHItemExtIEs}} OPTIONAL +} + +BHRLCCHItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +BH-Routing-Information-Added-List-Item ::= SEQUENCE { + bAPRoutingID BAPRoutingID, + nextHopBAPAddress BAPAddress, + iE-Extensions ProtocolExtensionContainer { { BH-Routing-Information-Added-List-ItemExtIEs} } OPTIONAL +} + +BH-Routing-Information-Added-List-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + {ID id-NonFlterminatingTopologyIndicator CRITICALITY ignore EXTENSION NonFlterminatingTopologyIndicator PRESENCE optional}, + ... +} +``` + +``` +BH-Routing-Information-Removed-List-Item ::= SEQUENCE { + bAPRoutingID BAPRoutingID, + iE-Extensions ProtocolExtensionContainer { { BH-Routing-Information-Removed-List-ItemExtIEs} } OPTIONAL +} +``` + +``` +BH-Routing-Information-Removed-List-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +BPLMN-ID-Info-List ::= SEQUENCE (SIZE(1..maxnoofBPLMNsNR)) OF BPLMN-ID-Info-Item +``` + +``` +BPLMN-ID-Info-Item ::= SEQUENCE { + pLMN-Identity-List AvailablePLMNList, + extended-PLMN-Identity-List ExtendedAvailablePLMN-List OPTIONAL, + fiveGS-TAC FiveGS-TAC OPTIONAL, + nr-cell-ID NRCellIdentity, + ranac RANAC OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { BPLMN-ID-Info-ItemExtIEs} } OPTIONAL, + ... +} +``` + +``` +BPLMN-ID-Info-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-ConfiguredTACIndication CRITICALITY ignore EXTENSION ConfiguredTACIndication PRESENCE optional }| +``` + +``` +{ ID id-NPNBroadcastInformation CRITICALITY reject EXTENSION NPNBroadcastInformation PRESENCE optional}, +... +} +``` + +``` +ServedPLMNs-List ::= SEQUENCE (SIZE(1..maxnoofBPLMNs)) OF ServedPLMNs-Item +``` + +``` +ServedPLMNs-Item ::= SEQUENCE { + pLMN-Identity PLMN-Identity, + iE-Extensions ProtocolExtensionContainer { { ServedPLMNs-ItemExtIEs} } OPTIONAL, + ... +} +``` + +``` +ServedPLMNs-ItemExtIEs FIAP-PROTOCOL-EXTENSION ::= { + { ID id-TAISliceSupportList CRITICALITY ignore EXTENSION SliceSupportList PRESENCE optional }| + { ID id-NPNSupportInfo CRITICALITY reject EXTENSION NPNSupportInfo PRESENCE optional }| + { ID id-ExtendedTAISliceSupportList CRITICALITY reject EXTENSION ExtendedSliceSupportList PRESENCE optional }| + { ID id-TAINSAGSupportList CRITICALITY ignore EXTENSION NSAGSupportList PRESENCE optional}, + ... +} +``` + +``` +BroadcastCAGList ::= SEQUENCE (SIZE(1..maxnoofCAGsupported)) OF CAGID +``` + +``` +BroadcastMRBs-FailedToBeModified-Item ::= SEQUENCE { +``` + +``` + mRB-ID MRB-ID, + cause Cause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { BroadcastMRBs-FailedtoBeModified-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +BroadcastMRBs-FailedtoBeModified-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +BroadcastMRBs-FailedToBeSetup-Item ::= SEQUENCE { + mRB-ID MRB-ID, + cause Cause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { BroadcastMRBs-FailedToBeSetup-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +BroadcastMRBs-FailedToBeSetup-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +BroadcastMRBs-FailedToBeSetupMod-Item ::= SEQUENCE { + mRB-ID MRB-ID, + cause Cause OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { BroadcastMRBs-FailedToBeSetupMod-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +BroadcastMRBs-FailedToBeSetupMod-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +BroadcastMRBs-Modified-Item ::= SEQUENCE { + mRB-ID MRB-ID, + bcBearerCtxtFlU-TNLInfoatDU BCBearerContextFlU-TNLInfo OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { BroadcastMRBs-Modified-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +BroadcastMRBs-Modified-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +BroadcastMRBs-Setup-Item ::= SEQUENCE { + mRB-ID MRB-ID, + bcBearerCtxtFlU-TNLInfoatDU BCBearerContextFlU-TNLInfo, + iE-Extensions ProtocolExtensionContainer { { BroadcastMRBs-Setup-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +} + +BroadcastMRBs-Setup-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +BroadcastMRBs-SetupMod-Item ::= SEQUENCE { + mRB-ID MRB-ID, + bcBearerCtxtFlU-TNLInfoatDU BCBearerContextFlU-TNLInfo, + iE-Extensions ProtocolExtensionContainer { { BroadcastMRBs-SetupMod-Item-ExtIEs} } OPTIONAL, + ... +} + +BroadcastMRBs-SetupMod-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +BroadcastMRBs-ToBeModified-Item ::= SEQUENCE { + mRB-ID MRB-ID, + mRB-QoSInformation QoSFlowLevelQoSParameters OPTIONAL, + mBS-Flows-Mapped-To-MRB-List MBS-Flows-Mapped-To-MRB-List OPTIONAL, + bcBearerCtxtFlU-TNLInfoatCU BCBearerContextFlU-TNLInfo OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { BroadcastMRBs-ToBeModified-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +} + +BroadcastMRBs-ToBeModified-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +BroadcastMRBs-ToBeReleased-Item ::= SEQUENCE { + mRB-ID MRB-ID, + iE-Extensions ProtocolExtensionContainer { { BroadcastMRBs-ToBeReleased-ItemExtIEs } } OPTIONAL, + ... +} + +BroadcastMRBs-ToBeReleased-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +BroadcastMRBs-ToBeSetup-Item ::= SEQUENCE { + mRB-ID MRB-ID, + mRB-QoSInformation QoSFlowLevelQoSParameters, + mBS-Flows-Mapped-To-MRB-List MBS-Flows-Mapped-To-MRB-List, + bcBearerCtxtFlU-TNLInfoatCU BCBearerContextFlU-TNLInfo , + iE-Extensions ProtocolExtensionContainer { { BroadcastMRBs-ToBeSetup-Item-ExtIEs} }, + ... +} +``` + +``` +BroadcastMRBs-ToBeSetup-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +BroadcastMRBs-ToBeSetupMod-Item ::= SEQUENCE { + mRB-ID MRB-ID, + mRB-QoSInformation QoSFlowLevelQoSParameters, + mBS-Flows-Mapped-To-MRB-List MBS-Flows-Mapped-To-MRB-List, + bcBearerCtxtFlU-TNLInfoatCU BCBearerContextFlU-TNLInfo, + iE-Extensions ProtocolExtensionContainer { { BroadcastMRBs-ToBeSetupMod-Item-ExtIEs } }, + ... +} +``` + +``` +BroadcastMRBs-ToBeSetupMod-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +BroadcastNIDLList ::= SEQUENCE (SIZE(1..maxnoofNIDsupported)) OF NID +``` + +``` +BroadcastSNPN-ID-List ::= SEQUENCE (SIZE(1..maxnoofNIDsupported)) OF BroadcastSNPN-ID-List-Item +``` + +``` +BroadcastSNPN-ID-List-Item ::= SEQUENCE { +``` + +``` + pLMN-Identity PLMN-Identity, + broadcastNIDList BroadcastNIDList, + iE-Extensions ProtocolExtensionContainer { { BroadcastSNPN-ID-List-ItemExtIEs } } OPTIONAL, + ... +} +``` + +``` +BroadcastSNPN-ID-List-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +BroadcastPNI-NPN-ID-List ::= SEQUENCE (SIZE(1..maxnoofCAGsupported)) OF BroadcastPNI-NPN-ID-List-Item +``` + +``` +BroadcastPNI-NPN-ID-List-Item ::= SEQUENCE { + pLMN-Identity PLMN-Identity, + broadcastCAGList BroadcastCAGList, + iE-Extensions ProtocolExtensionContainer { { BroadcastPNI-NPN-ID-List-ItemExtIEs } } OPTIONAL, + ... +} +``` + +``` +BroadcastPNI-NPN-ID-List-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +BroadcastAreaScope ::= CHOICE { +``` + +``` + completeSuccess NULL, + partialSuccess PartialSuccessCell, + choice-extension ProtocolIE-SingleContainer { { BroadcastAreaScope-ExtIEs } } +} + +BroadcastAreaScope-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +BroadcastCellList ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF Broadcast-Cell-List-Item +Broadcast-Cell-List-Item ::= SEQUENCE { + cellID NRCGI, + iE-Extensions ProtocolExtensionContainer { { Broadcast-Cell-List-ItemExtIEs } } OPTIONAL, + ... +} + +Broadcast-Cell-List-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +BufferSizeThresh ::= INTEGER(0..16777215) + +BurstArrivalTime ::= OCTET STRING +``` + +BWP-Id ::= INTEGER (0..4) + +BurstArrivalTimeWindow ::= SEQUENCE { +    burstArrivalTimeWindowStart    INTEGER (0..640000, ...), +    burstArrivalTimeWindowEnd    INTEGER (0..640000, ...), +    iE-Extension    ProtocolExtensionContainer { {BurstArrivalTimeWindow-ExtIEs} } OPTIONAL, +    ... +} + +BurstArrivalTimeWindow-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +-- C + +CAGID ::= BIT STRING (SIZE(32)) + +Cancel-all-Warning-Messages-Indicator ::= ENUMERATED {true, ...} + +Candidate-SpCell-Item ::= SEQUENCE { +    candidate-SpCell-ID    NR CGI , +    iE-Extensions    ProtocolExtensionContainer { { Candidate-SpCell-ItemExtIEs } } OPTIONAL, +    ... +} + +} + +``` +Candidate-SpCell-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +CapacityValue ::= SEQUENCE { + capacityValue INTEGER (0..100), + sSBAreaCapacityValueList SSBAreaCapacityValueList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { CapacityValue-ExtIEs } } OPTIONAL +} +``` + +``` +CapacityValue-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +Cause ::= CHOICE { + radioNetwork CauseRadioNetwork, + transport CauseTransport, + protocol CauseProtocol, + misc CauseMisc, + choice-extension ProtocolIE-SingleContainer { { Cause-ExtIEs } } +} +``` + +``` +Cause-ExtIEs FLAP-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, + rl-failure-rlc, + unknown-or-already-allocated-gnb-cu-ue-flap-id, + unknown-or-already-allocated-gnb-du-ue-flap-id, + unknown-or-inconsistent-pair-of-ue-flap-id, + interaction-with-other-procedure, + not-supported-qci-Value, + action-desirable-for-radio-reasons, + no-radio-resources-available, + procedure-cancelled, + normal-release, + ... + cell-not-available, + rl-failure-others, + ue-rejection, + resources-not-available-for-the-slice, + amf-initiated-abnormal-release, + release-due-to-pre-emption, + plmn-not-served-by-the-gNB-CU, + multiple-drb-id-instances, + unknown-drb-id, + multiple-bh-rlc-ch-id-instances, + unknown-bh-rlc-ch-id, +} +``` + +``` +cho-cpc-resources-tobechanged, +nPN-not-supported, +nPN-access-denied, +gNB-CU-Cell-Capacity-Exceeded, +report-characteristics-empty, +existing-measurement-ID, +measurement-temporarily-not-available, +measurement-not-supported-for-the-object, +unknown-bh-address, +unknown-bap-routing-id, +insufficient-ue-capabilities, +scg-activation-deactivation-failure, +scg-deactivation-failure-due-to-data-transmission, +requested-item-not-supported-on-time, +unknown-or-already-allocated-gNB-CU-MBS-FlAP-ID, +unknown-or-already-allocated-gNB-DU-MBS-FlAP-ID, +unknown-or-inconsistent-pair-of-MBS-FlAP-ID, +unknown-or-inconsistent-MRB-ID, +tat-sdt-expiry, +ITM-command-triggered, +sSB-not-available + +} +``` + +``` +CauseTransport ::= ENUMERATED { + unspecified, + transport-resource-unavailable, + ..., + unknown-TNL-address-for-IAB, + unknown-UP-TNL-information-for-IAB +} + +CellGroupConfig ::= OCTET STRING + +CellCapacityClassValue ::= INTEGER (1..100,...) + +Cell-Direction ::= ENUMERATED {dl-only, ul-only} + +CellMeasurementResultList ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF CellMeasurementResultItem + +CellMeasurementResultItem ::= SEQUENCE { + cellID NRCGI, + radioResourceStatus RadioResourceStatus OPTIONAL, + compositeAvailableCapacityGroup CompositeAvailableCapacityGroup OPTIONAL, + sliceAvailableCapacity SliceAvailableCapacity OPTIONAL, + numberOfActiveUEs NumberOfActiveUEs OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { CellMeasurementResultItem-ExtIEs} } OPTIONAL +} +``` + +``` + +CellMeasurementResultItem-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + { ID id-NR-U-Channel-List CRITICALITY ignore EXTENSION NR-U-Channel-List PRESENCE optional }, + ... +} + +Cell-Portion-ID ::= INTEGER (0..4095,...) + +CellsForSON-List ::= SEQUENCE (SIZE(1.. maxServedCellforSON)) OF CellsForSON-Item + +CellsForSON-Item ::= SEQUENCE { + nRCGI NRCGI, + neighbourNR-CellsForSON-List NeighbourNR-CellsForSON-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { CellsForSON-Item-ExtIEs} } OPTIONAL, + ... +} + +CellsForSON-Item-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +Cells-Failed-to-be-Activated-List-Item ::= SEQUENCE { + nRCGI NRCGI, + cause Cause, + ... +} + +``` + +``` + iE-Extensions ProtocolExtensionContainer { { Cells-Failed-to-be-Activated-List-ItemExtIEs } } OPTIONAL, + ... +} + +Cells-Failed-to-be-Activated-List-ItemExtIEs FIAP-PROTOCOL-EXTENSION ::= { + ... +} + +Cells-Status-Item ::= SEQUENCE { + nRRCGI NRCGI, + service-status Service-Status, + iE-Extensions ProtocolExtensionContainer { { Cells-Status-ItemExtIEs } } OPTIONAL, + ... +} + +Cells-Status-ItemExtIEs FIAP-PROTOCOL-EXTENSION ::= { + ... +} + +Cells-To-Be-Broadcast-Item ::= SEQUENCE { + nRRCGI NRCGI, + iE-Extensions ProtocolExtensionContainer { { Cells-To-Be-Broadcast-ItemExtIEs } } OPTIONAL, + ... +} +``` + +``` +Cells-To-Be-Broadcast-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +Cells-Broadcast-Completed-Item ::= SEQUENCE { + nRCGI NRCGI, + iE-Extensions ProtocolExtensionContainer { { Cells-Broadcast-Completed-ItemExtIEs } } OPTIONAL, + ... +} + +Cells-Broadcast-Completed-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +Broadcast-To-Be-Cancelled-Item ::= SEQUENCE { + nRCGI NRCGI, + iE-Extensions ProtocolExtensionContainer { { Broadcast-To-Be-Cancelled-ItemExtIEs } } OPTIONAL, + ... +} + +Broadcast-To-Be-Cancelled-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +Cells-Broadcast-Cancelled-Item ::= SEQUENCE { + nRCGI NRCGI, + numberOfBroadcasts NumberOfBroadcasts, + iE-Extensions ProtocolExtensionContainer { { Cells-Broadcast-Cancelled-ItemExtIEs } } OPTIONAL, + ... +} + +Cells-Broadcast-Cancelled-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +Cells-to-be-Activated-List-Item ::= SEQUENCE { + nRCGI NRCGI, + nRPCI NRPCI OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Cells-to-be-Activated-List-ItemExtIEs } } OPTIONAL, + ... +} + +Cells-to-be-Activated-List-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-gNB-CUSystemInformation CRITICALITY reject EXTENSION GNB-CUSystemInformation PRESENCE optional }| + { ID id-AvailablePLMNList CRITICALITY ignore EXTENSION AvailablePLMNList PRESENCE optional }| + { ID id-ExtendedAvailablePLMN-List CRITICALITY ignore EXTENSION ExtendedAvailablePLMN-List PRESENCE optional }| +} +``` + +``` +{ ID id-IAB-Info-IAB-donor-CU CRITICALITY ignore EXTENSION IAB-Info-IAB-donor-CU PRESENCE optional }| +{ ID id-AvailableSNPN-ID-List CRITICALITY ignore EXTENSION AvailableSNPN-ID-List PRESENCE optional }| +{ ID id-MBS-Broadcast-NeighbourCellList CRITICALITY ignore EXTENSION MBS-Broadcast-NeighbourCellList PRESENCE optional }| +{ ID id-SSBs-withinTheCell-toBe-Activated-List CRITICALITY reject EXTENSION SSBs-toBeActivated-List PRESENCE optional }, +... +} + +Cells-With-SSBs-Activated-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF Cells-With-SSBs-Activated-List-Item + +Cells-With-SSBs-Activated-List-Item ::= SEQUENCE { + nGCGI NRCGI, + sSBs-activated-List SSBs-activated-List, + iE-Extensions ProtocolExtensionContainer { { Cells-With-SSBs-Activated-List-Item-ExtIEs} } OPTIONAL +} + +Cells-With-SSBs-Activated-List-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +Cells-Allowed-to-be-Deactivated-List-Item ::= SEQUENCE { + nRCGI NRCGI, + iE-Extensions ProtocolExtensionContainer { { Cells-Allowed-to-be-Deactivated-List-ItemExtIEs} } OPTIONAL, + ... +} +``` + +``` +Cells-Allowed-to-be-Deactivated-List-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +Cells-to-be-Deactivated-List-Item ::= SEQUENCE { + nRCGI NRCGI , + iE-Extensions ProtocolExtensionContainer { { Cells-to-be-Deactivated-List-ItemExtIEs } } OPTIONAL, + ... +} + +Cells-to-be-Deactivated-List-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +Cells-to-be-Barred-Item ::= SEQUENCE { + nRCGI NRCGI , + cellBarred CellBarred, + iE-Extensions ProtocolExtensionContainer { { Cells-to-be-Barred-Item-ExtIEs } } OPTIONAL +} + +Cells-to-be-Barred-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-IAB-Barred CRITICALITY ignore EXTENSION IAB-Barred PRESENCE optional }, +``` + +``` + ... +} + +CellBarred ::= ENUMERATED {barred, not-barred, ...} + +CellSize ::= ENUMERATED {verysmall, small, medium, large, ...} + +CellToReportList ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF CellToReportItem + +CellToReportItem ::= SEQUENCE { + cellID NRCGI, + ssbToReportList SSBToReportList OPTIONAL, + sliceToReportList SliceToReportList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { CellToReportItem-ExtIEs} } OPTIONAL +} + +CellToReportItem-ExtIEs FIAP-PROTOCOL-EXTENSION ::= { + ... +} + +CellType ::= SEQUENCE { + cellSize CellSize, + iE-Extensions ProtocolExtensionContainer { {CellType-ExtIEs} } OPTIONAL, +``` + +``` + ... +} + +CellType-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +CellULConfigured ::= ENUMERATED {none, ul, sul, ul-and-sul, ...} + +CG-SDTQueryIndication ::= ENUMERATED {true, ...} + +CG-SDTKeptIndicator ::= ENUMERATED {true, ...} + +CG-SDTIndicatorSetup ::= ENUMERATED {true, ...} + +CG-SDTIndicatorMod ::= ENUMERATED {true, false, ...} + +CG-SDTSessionInfo ::= SEQUENCE { + gNB-CU-UE-FlAP-ID GNB-CU-UE-FlAP-ID, + gNB-DU-UE-FlAP-ID GNB-DU-UE-FlAP-ID, + iE-Extensions ProtocolExtensionContainer {{CG-SDTSessionInfo-ExtIEs}} OPTIONAL, + ... +} +``` + +``` +CG-SDTSessionInfo-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +ChannelOccupancyTimePercentage ::= INTEGER (0..100,...) + +Child-IAB-Nodes-NA-Resource-List ::= SEQUENCE (SIZE(1..maxnoofChildIABNodes)) OF Child-IAB-Nodes-NA-Resource-List-Item + +Child-IAB-Nodes-NA-Resource-List-Item ::= SEQUENCE { + gNB-CU-UE-FlAP-ID GNB-CU-UE-FlAP-ID, + gNB-DU-UE-FlAP-ID GNB-DU-UE-FlAP-ID, + nA-Resource-Configuration-List NA-Resource-Configuration-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Child-IAB-Nodes-NA-Resource-List-Item-ExtIEs } } OPTIONAL +} + +Child-IAB-Nodes-NA-Resource-List-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +Child-Node-Cells-List ::= SEQUENCE (SIZE(1..maxnoofChildIABNodes)) OF Child-Node-Cells-List-Item + +Child-Node-Cells-List-Item ::= SEQUENCE{ +``` + +``` + +nRCGI NRCGI, + +iAB-DU-Cell-Resource-Configuration-Mode-Info iAB-DU-Cell-Resource-Configuration-Mode-Info OPTIONAL, + +iAB-STC-Info iAB-STC-Info OPTIONAL, + +rACH-Config-Common RACH-Config-Common OPTIONAL, + +rACH-Config-Common-IAB RACH-Config-Common-IAB OPTIONAL, + +cSI-RS-Configuration OCTET STRING OPTIONAL, + +sR-Configuration OCTET STRING OPTIONAL, + +pDCCH-ConfigSIB1 OCTET STRING OPTIONAL, + +sCS-Common OCTET STRING OPTIONAL, + +multiplexingInfo MultiplexingInfo OPTIONAL, + +iE-Extensions ProtocolExtensionContainer {{Child-Node-Cells-List-Item-ExtIEs}} OPTIONAL + +} + +Child-Node-Cells-List-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + + ... + +} + +Child-Nodes-List ::= SEQUENCE (SIZE(1..maxnoofChildIABNodes)) OF Child-Nodes-List-Item + +Child-Nodes-List-Item ::= SEQUENCE{ + + gNB-CU-UE-FlAP-ID GNB-CU-UE-FlAP-ID, + + gNB-DU-UE-FlAP-ID GNB-DU-UE-FlAP-ID, + + child-Node-Cells-List Child-Node-Cells-List OPTIONAL, + + iE-Extensions ProtocolExtensionContainer {{Child-Nodes-List-Item-ExtIEs}} OPTIONAL +} + +``` + +} + +Child-Nodes-List-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +CHOtrigger-InterDU ::= ENUMERATED { + +cho-initiation, + +cho-replace, + +... + +} + +CHOtrigger-IntraDU ::= ENUMERATED { + +cho-initiation, + +cho-replace, + +cho-cancel, + +... + +} + +CNSubgroupID ::= INTEGER (0..7, ...) + +CNUEPagingIdentity ::= CHOICE { + +fiveG-S-TMSI BIT STRING (SIZE(48)), + +choice-extension ProtocolIE-SingleContainer { { CNUEPagingIdentity-ExtIEs } } + +``` + } + + CNUEPagingIdentity-ExtIEs FLAP-PROTOCOL-IES ::= { + ... + } + + CompositeAvailableCapacityGroup ::= SEQUENCE { + compositeAvailableCapacityDownlink CompositeAvailableCapacity, + compositeAvailableCapacityUplink CompositeAvailableCapacity, + iE-Extensions ProtocolExtensionContainer { { CompositeAvailableCapacityGroup-ExtIEs} } OPTIONAL + } + + CompositeAvailableCapacityGroup-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-CompositeAvailableCapacity-SUL CRITICALITY ignore EXTENSION CompositeAvailableCapacity PRESENCE optional }, + ... + } + + CompositeAvailableCapacity ::= SEQUENCE { + cellCapacityClassValue CellCapacityClassValue OPTIONAL, + capacityValue CapacityValue, + iE-Extensions ProtocolExtensionContainer { { CompositeAvailableCapacity-ExtIEs} } OPTIONAL + } + + CompositeAvailableCapacity-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +CHO-Probability ::= INTEGER (1..100) + +ConditionalInterDUMobilityInformation ::= SEQUENCE { + cho-trigger CHOtrigger-InterDU, + targetgNB-DUUEFlAPID GNB-DU-UE-FlAP-ID OPTIONAL + -- This IE shall be present if the cho-trigger IE is present and set to "cho-replace" --, + iE-Extensions ProtocolExtensionContainer { { ConditionalInterDUMobilityInformation-ExtIEs } } OPTIONAL, + ... +} + +ConditionalInterDUMobilityInformation-ExtIEs FlAP-PROTOCOL-EXTENSION ::= { + { ID id-EstimatedArrivalProbability CRITICALITY ignore EXTENSION CHO-Probability PRESENCE optional }, + ... +} + +ConditionalIntraDUMobilityInformation ::= SEQUENCE { + cho-trigger CHOtrigger-IntraDU, + targetCellsToCancel TargetCellList OPTIONAL, + -- This IE may be present if the cho-trigger IE is present and set to "cho-cancel" + iE-Extensions ProtocolExtensionContainer { { ConditionalIntraDUMobilityInformation-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +} + +ConditionalIntraDUMobilityInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-EstimatedArrivalProbability CRITICALITY ignore EXTENSION CHO-Probability PRESENCE optional }, + ... +} + +ConfigRestrictInfoDAPS ::= OCTET STRING + +ConfiguredTACIndication ::= ENUMERATED { + true, + ... +} + +Configured-BWP-List ::= SEQUENCE (SIZE(1.. maxNrofBWPs)) OF Configured-BWP-Item + +Configured-BWP-Item ::= SEQUENCE { + bWP-Id bWP-Id, + bWP-Location-and-bandwidth INTEGER (0..37949), + iE-Extensions ProtocolExtensionContainer { { Configured-BWP-Item-ExtIEs } } OPTIONAL, + ... +} + +Configured-BWP-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +CoordinateID ::= INTEGER (0..511, ...) + +Coverage-Modification-Notification ::= SEQUENCE { + coverage-Modification-List Coverage-Modification-List, + iE-Extensions ProtocolExtensionContainer { { Coverage-Modification-Notification-ExtIEs} } OPTIONAL, + ... +} + +Coverage-Modification-Notification-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +Coverage-Modification-List ::= SEQUENCE (SIZE (1..maxCellingNBDU)) OF Coverage-Modification-Item + +Coverage-Modification-Item ::= SEQUENCE { + nRCGI NRCGI, + cellCoverageState CellCoverageState, + sSBCoverageModificationList SSBCoverageModification-List OPTIONAL, + iE-Extension ProtocolExtensionContainer { { Coverage-Modification-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +} + +Coverage-Modification-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +CellCoverageState ::= INTEGER (0..63, ...) + +CCO-Assistance-Information ::= SEQUENCE { + cCO-issue-detection cCO-issue-detection OPTIONAL, + affectedCellsAndBeams-List AffectedCellsAndBeams-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { CCO-Assistance-Information-ExtIEs} } OPTIONAL, + ... +} + +CCO-Assistance-Information-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +CCO-issue-detection ::= ENUMERATED { + coverage, + cell-edge-capacity, +``` + +``` + ... + network-energy-saving} + +CP-TransportLayerAddress ::= CHOICE { + endpoint-IP-address TransportLayerAddress, + endpoint-IP-address-and-port Endpoint-IP-address-and-port, + choice-extension ProtocolIE-SingleContainer { { CP-TransportLayerAddress-ExtIEs } } +} + +CP-TransportLayerAddress-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +CPACMCGInformation ::= SEQUENCE { + cpac-trigger CPAC-trigger, + pscellid NRCGI, + iE-Extensions ProtocolExtensionContainer { { CPACMCGInformation-ExtIEs} } OPTIONAL, + ... +} + +CPACMCGInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +CPAC-trigger ::= ENUMERATED { + +cpac-preparation, + +cpac-executed, + +... + +} + +CPTrafficType ::= INTEGER (1..3,...) + +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 FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE (1.. maxnoofErrors)) OF CriticalityDiagnostics-IE-Item + +``` +CriticalityDiagnostics-IE-Item ::= SEQUENCE { + iECriticality Criticality, + iE-ID ProtocolIE-ID, + typeOfError TypeOfError, + iE-Extensions ProtocolExtensionContainer {{CriticalityDiagnostics-IE-Item-ExtIEs}} OPTIONAL, + ... +} + +CriticalityDiagnostics-IE-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +C-RNTI ::= INTEGER (0..65535, ...) + +CUDURadioInformationType ::= CHOICE { + rIM CUDURIMInformation, + choice-extension ProtocolIE-SingleContainer { { CUDURadioInformationType-ExtIEs} } +} + +CUDURadioInformationType-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} +``` + +``` + +CUDURIMInformation ::= SEQUENCE { + victimgNBSetID GNBSetID, + rIMRSDetectionStatus RIMRSDetectionStatus, + iE-Extensions ProtocolExtensionContainer { { CUDURIMInformation-ExtIEs} } OPTIONAL +} + +``` + +``` + +CUDURIMInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +CUtoDURRCInformation ::= SEQUENCE { + cG-ConfigInfo CG-ConfigInfo OPTIONAL, + uE-CapabilityRAT-ContainerList UE-CapabilityRAT-ContainerList OPTIONAL, + measConfig MeasConfig OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { CUtoDURRCInformation-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +CUtoDURRCInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-HandoverPreparationInformation CRITICALITY ignore EXTENSION HandoverPreparationInformation PRESENCE optional }| + { ID id-CellGroupConfig CRITICALITY ignore EXTENSION CellGroupConfig PRESENCE optional }| + { ID id-MeasurementTimingConfiguration CRITICALITY ignore EXTENSION MeasurementTimingConfiguration PRESENCE optional }| + { ID id-UEAssistanceInformation CRITICALITY ignore EXTENSION UEAssistanceInformation PRESENCE optional }| + { ID id-CG-Config CRITICALITY ignore EXTENSION CG-Config PRESENCE optional }| +} + +``` + +``` + + { ID id-UEAssistanceInformationEUTRA CRITICALITY ignore EXTENSION UEAssistanceInformationEUTRA PRESENCE optional }| + { ID id-LocationMeasurementInformation CRITICALITY ignore EXTENSION LocationMeasurementInformation PRESENCE optional }| + { ID id-MUSIM-GapConfig CRITICALITY reject EXTENSION MUSIM-GapConfig PRESENCE optional }| + { ID id-SDT-MAC-PHY-CG-Config CRITICALITY ignore EXTENSION SDT-MAC-PHY-CG-Config PRESENCE optional }| + { ID id-MBSInterestIndication CRITICALITY ignore EXTENSION MBSInterestIndication PRESENCE optional }| + { ID id-NeedForGapsInfoNR CRITICALITY ignore EXTENSION NeedForGapsInfoNR PRESENCE optional }| + { ID id-NeedForGapNCSGInfoNR CRITICALITY ignore EXTENSION NeedForGapNCSGInfoNR PRESENCE optional }| + { ID id-NeedForGapNCSGInfoEUTRA CRITICALITY ignore EXTENSION NeedForGapNCSGInfoEUTRA PRESENCE optional }| + { ID id-ConfigRestrictInfoDAPS CRITICALITY ignore EXTENSION ConfigRestrictInfoDAPS PRESENCE optional }| + + { ID id-Preconfigured-measurement-GAP-Request CRITICALITY ignore EXTENSION Preconfigured-measurement-GAP-Request PRESENCE +optional }| + + { ID id-NeedForInterruptionInfoNR CRITICALITY ignore EXTENSION NeedForInterruptionInfoNR PRESENCE optional }| + + { ID id-MusimCapabilityRestrictionIndication CRITICALITY ignore EXTENSION MusimCapabilityRestrictionIndication PRESENCE +optional }, + + ... + +} + +``` + +CSIResourceConfiguration ::= OCTET STRING + +-- D + +DAPS-HO-Status ::= ENUMERATED{initiation,... } + +DCBasedDuplicationConfigured ::= ENUMERATED{true,..., false} + +``` +DeactivationIndication ::= CHOICE { + perUE DeactivationIndicationList, + deactivateAll NULL, + choice-extension ProtocolIE-SingleContainer { { DeactivationIndication-ExtIEs} } +} + +DeactivationIndication-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +DeactivationIndicationList ::= SEQUENCE (SIZE(1..maxnoofUEsInQMCTransferControlMessage)) OF DeactivationIndicationList-Item + +DeactivationIndicationList-Item ::= SEQUENCE { + gNB-CU-UE-FLAP-ID GNB-CU-UE-FLAP-ID, + gNB-DU-UE-FLAP-ID GNB-DU-UE-FLAP-ID, + iE-Extensions ProtocolExtensionContainer { { DeactivationIndicationList-Item-ExtIEs} } OPTIONAL, + ... +} + +DeactivationIndicationList-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +DedicatedSIDelivery-NeededUE-Item ::= SEQUENCE { + gNB-CU-UE-FlAP-ID GNB-CU-UE-FlAP-ID, + nRCGI NRCGI, + iE-Extensions ProtocolExtensionContainer { { DedicatedSIDeliveryNeededUE-Item-ExtIEs} } OPTIONAL, + ... +} + +DedicatedSIDeliveryNeededUE-Item-ExtIEs FlAP-PROTOCOL-EXTENSION ::= { + ... +} + +DedicatedSIDeliveryIndication ::= ENUMERATED{true, ...} + +DL-PRS ::= SEQUENCE { + prsid INTEGER (0..255), + dl-PRSResourceSetID PRS-Resource-Set-ID, + dl-PRSResourceID PRS-Resource-ID OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {DL-PRS-ExtIEs} } OPTIONAL +} + +DL-PRS-ExtIEs FlAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +DL-PRSMutingPattern ::= CHOICE { + two BIT STRING (SIZE(2)), + four BIT STRING (SIZE(4)), + six BIT STRING (SIZE(6)), + eight BIT STRING (SIZE(8)), + sixteen BIT STRING (SIZE(16)), + thirty-two BIT STRING (SIZE(32)), + choice-extension ProtocolIE-SingleContainer { { DL-PRSMutingPattern-ExtIEs } } +} + +DL-PRSMutingPattern-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +DLPRSResourceCoordinates ::= SEQUENCE { + listOfDL-PRSResourceSetARP SEQUENCE (SIZE(1.. maxnoofPRS-ResourceSets)) OF DLPRSResourceSetARP, + iE-Extensions ProtocolExtensionContainer { { DLPRSResourceCoordinates-ExtIEs } } OPTIONAL +} + +DLPRSResourceCoordinates-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +DLPRSResourceSetARP ::= SEQUENCE { +``` + +``` +dl-PRSResourceSetID PRS-Resource-Set-ID, +dl-PRSResourceSetARPLocation DL-PRSResourceSetARPLocation, +listofDL-PRSResourceARP SEQUENCE (SIZE(1.. maxnoofPRS-ResourcesPerSet)) OF DLPRSResourceARP, +iE-Extensions ProtocolExtensionContainer { { DLPRSResourceSetARP-ExtIEs } } OPTIONAL +} + +DLPRSResourceSetARP-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +DL-PRSResourceSetARPLocation ::= CHOICE { + relativeGeodeticLocation RelativeGeodeticLocation, + relativeCartesianLocation RelativeCartesianLocation, + choice-Extension ProtocolIE-SingleContainer { { DL-PRSResourceSetARPLocation-ExtIEs } } +} + +DL-PRSResourceSetARPLocation-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +DLPRSResourceARP ::= SEQUENCE { + dl-PRSResourceID PRS-Resource-ID, +``` + +``` + dL-PRSResourceARPLocation DL-PRSResourceARPLocation, + iE-Extensions ProtocolExtensionContainer { { DLPRSResourceARP-ExtIEs } } OPTIONAL +} + +DLPRSResourceARP-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +DL-PRSResourceARPLocation ::= CHOICE { + relativeGeodeticLocation RelativeGeodeticLocation, + relativeCartesianLocation RelativeCartesianLocation, + choice-Extension ProtocolIE-SingleContainer { { DL-PRSResourceARPLocation-ExtIEs } } +} + +DL-PRSResourceARPLocation-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +DL-UP-TNL-Address-to-Update-List-Item ::= SEQUENCE { + oldIPAddress TransportLayerAddress, + newIPAddress TransportLayerAddress, + iE-Extensions ProtocolExtensionContainer { { DL-UP-TNL-Address-to-Update-List-ItemExtIEs } } OPTIONAL, + ... +} +``` + +``` +DL-UP-TNL-Address-to-Update-List-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +DLUPTNLInformation-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofDLUPTNLInformation)) OF DLUPTNLInformation-ToBeSetup-Item + +DLUPTNLInformation-ToBeSetup-Item ::= SEQUENCE { + dLUPTNLInformation UPTransportLayerInformation , + iE-Extensions ProtocolExtensionContainer { { DLUPTNLInformation-ToBeSetup-ItemExtIEs } } OPTIONAL, + ... +} + +DLUPTNLInformation-ToBeSetup-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-Activity-Item ::= SEQUENCE { + dRBID DRBID, + dRB-Activity DRB-Activity OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRB-Activity-ItemExtIEs } } OPTIONAL, + ... +} +``` + +``` +DRB-Activity-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-Activity ::= ENUMERATED {active, not-active} + +DRBID ::= INTEGER (1..32, ...) + +DRBs-FailedToBeModified-Item ::= SEQUENCE { + dRBID DRBID , + cause Cause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRBs-FailedToBeModified-ItemExtIEs } } OPTIONAL, + ... +} + +DRBs-FailedToBeModified-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +DRBs-FailedToBeSetup-Item ::= SEQUENCE { + dRBID DRBID, + cause Cause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRBs-FailedToBeSetup-ItemExtIEs } } OPTIONAL, + ... +} +``` + +} + +DRBs-FailedToBeSetup-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +DRBs-FailedToBeSetupMod-Item ::= SEQUENCE { + +dRBID dRBID , + +cause Cause OPTIONAL , + +iE-Extensions ProtocolExtensionContainer { { DRBs-FailedToBeSetupMod-ItemExtIEs } } OPTIONAL, + +... + +} + +DRBs-FailedToBeSetupMod-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +DRB-Information ::= SEQUENCE { + +dRB-QoS QoSFlowLevelQoSParameters, + +sNSSAI SNSSAI, + +notificationControl NotificationControl OPTIONAL, + +flows-Mapped-To-DRB-List Flows-Mapped-To-DRB-List, + +iE-Extensions ProtocolExtensionContainer { { DRB-Information-ItemExtIEs } } OPTIONAL + +``` + +} + +DRB-Information-ItemExtIEs FIAP-PROTOCOL-EXTENSION ::= { + + { ID id-ECNMarkingorCongestionInformationReportingRequest CRITICALITY ignore EXTENSION ECNMarkingorCongestionInformationReportingRequest + PRESENCE optional }, + + ... + +} + +DRBs-Modified-Item ::= SEQUENCE { + + dRBID DRBID, + + lCID lCID OPTIONAL, + + dLUPTNLInformation-ToBeSetup-List dLUPTNLInformation-ToBeSetup-List, + + iE-Extensions ProtocolExtensionContainer { { DRBs-Modified-ItemExtIEs } } OPTIONAL, + + ... + +} + +DRBs-Modified-ItemExtIEs FIAP-PROTOCOL-EXTENSION ::= { + + { ID id-RLC-Status CRITICALITY ignore EXTENSION RLC-Status PRESENCE optional }| + + { ID id-AdditionalPDCPDuplicationTNL-List CRITICALITY ignore EXTENSION AdditionalPDCPDuplicationTNL-List PRESENCE optional }| + + { ID id-CurrentQoSParaSetIndex CRITICALITY ignore EXTENSION QoSParaSetIndex PRESENCE optional }| + + { ID id-TSCTrafficCharacteristicsFeedback CRITICALITY ignore EXTENSION TSCTrafficCharacteristicsFeedback PRESENCE optional }| + + { ID id-ECNMarkingorCongestionInformationReportingStatus CRITICALITY ignore EXTENSION ECNMarkingorCongestionInformationReportingStatus + PRESENCE optional }, + + ... + +} + +``` + +``` +DRBs-ModifiedConf-Item ::= SEQUENCE { + dRBID DRBID, + uLUPtNLInformation-ToBeSetup-List uLUPtNLInformation-ToBeSetup-List , + iE-Extensions ProtocolExtensionContainer { { DRBs-ModifiedConf-ItemExtIEs } } OPTIONAL, + ... +} + +DRBs-ModifiedConf-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-AdditionalPDCPDuplicationTNL-List CRITICALITY ignore EXTENSION AdditionalPDCPDuplicationTNL-List PRESENCE optional }, + ... +} + +DRB-Notify-Item ::= SEQUENCE { + dRBID DRBID, + notification-Cause Notification-Cause, + iE-Extensions ProtocolExtensionContainer { { DRB-Notify-ItemExtIEs } } OPTIONAL, + ... +} + +DRB-Notify-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-CurrentQoSParaSetIndex CRITICALITY ignore EXTENSION QoSParaSetNotifyIndex PRESENCE optional } | + { ID id-TSCTrafficCharacteristicsFeedback CRITICALITY ignore EXTENSION TSCTrafficCharacteristicsFeedback PRESENCE optional }, + ... +} +``` + +``` +} + +DRBs-Required-ToBeModified-Item ::= SEQUENCE { + dRBID dRBID, + dLUPTNLInformation-ToBeSetup-List dLUPTNLInformation-ToBeSetup-List , + iE-Extensions ProtocolExtensionContainer { { DRBs-Required-ToBeModified-ItemExtIEs } } OPTIONAL, + ... +} + +DRBs-Required-ToBeModified-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-RLC-Status CRITICALITY ignore EXTENSION RLC-Status PRESENCE optional }| + { ID id-AdditionalPDCPDuplicationTNL-List CRITICALITY ignore EXTENSION AdditionalPDCPDuplicationTNL-List PRESENCE optional }, + ... +} + +DRBs-Required-ToBeReleased-Item ::= SEQUENCE { + dRBID dRBID, + iE-Extensions ProtocolExtensionContainer { { DRBs-Required-ToBeReleased-ItemExtIEs } } OPTIONAL, + ... +} + +DRBs-Required-ToBeReleased-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` + +DRBs-Setup-Item ::= SEQUENCE { + dRBID DRBID, + lCID lCID OPTIONAL, + dLUPTNLInformation-ToBeSetup-List dLUPTNLInformation-ToBeSetup-List , + iE-Extensions ProtocolExtensionContainer { { DRBs-Setup-ItemExtIEs } } OPTIONAL, + ... +} + +DRBs-Setup-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-AdditionalPDCPDuplicationTNL-List CRITICALITY ignore EXTENSION AdditionalPDCPDuplicationTNL-List PRESENCE optional }| + { ID id-CurrentQoSParaSetIndex CRITICALITY ignore EXTENSION QoSParaSetIndex PRESENCE optional }| + { ID id-TSCTrafficCharacteristicsFeedback CRITICALITY ignore EXTENSION TSCTrafficCharacteristicsFeedback PRESENCE optional }| + { ID id-ECNMarkingorCongestionInformationReportingStatus CRITICALITY ignore EXTENSION ECNMarkingorCongestionInformationReportingStatus + PRESENCE optional }, + ... +} + +DRBs-SetupMod-Item ::= SEQUENCE { + dRBID DRBID, + lCID lCID OPTIONAL, + dLUPTNLInformation-ToBeSetup-List dLUPTNLInformation-ToBeSetup-List , + iE-Extensions ProtocolExtensionContainer { { DRBs-SetupMod-ItemExtIEs } } OPTIONAL, + ... +} + +``` + +``` + +DRBs-SetupMod-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + + { ID id-AdditionalPDCPDuplicationTNL-List CRITICALITY ignore EXTENSION AdditionalPDCPDuplicationTNL-List PRESENCE optional }| + + { ID id-CurrentQoSParaSetIndex CRITICALITY ignore EXTENSION QoSParaSetIndex PRESENCE optional }| + + { ID id-TSCTrafficCharacteristicsFeedback CRITICALITY ignore EXTENSION TSCTrafficCharacteristicsFeedback PRESENCE optional }| + + { ID id-ECNMarkingorCongestionInformationReportingStatus CRITICALITY ignore EXTENSION ECNMarkingorCongestionInformationReportingStatus + PRESENCE optional }, + + ... + +} + +``` + +``` + +DRBs-ToBeModified-Item ::= SEQUENCE { + + dRBID DRBID, + + qosInformation QoSInformation OPTIONAL, + + uLUPTNLInformation-ToBeSetup-List ULUPTNLInformation-ToBeSetup-List , + + uLConfiguration ULConfiguration OPTIONAL, + + iE-Extensions ProtocolExtensionContainer { { DRBs-ToBeModified-ItemExtIEs } } OPTIONAL, + + ... + +} + +``` + +``` + +DRBs-ToBeModified-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + + { ID id-DLPDCPSNLength CRITICALITY ignore EXTENSION PDCPSNLength PRESENCE optional }| + + { ID id-ULPDCPSNLength CRITICALITY ignore EXTENSION PDCPSNLength PRESENCE optional }| + + { ID id-BearerTypeChange CRITICALITY ignore EXTENSION BearerTypeChange PRESENCE optional }| + + { ID id-RLCMode CRITICALITY ignore EXTENSION RLCMode PRESENCE optional }| + +``` + +``` + + { ID id-Duplication-Activation CRITICALITY reject EXTENSION DuplicationActivation PRESENCE optional }| + { ID id-DC-Based-Duplication-Configured CRITICALITY reject EXTENSION DCBasedDuplicationConfigured PRESENCE optional }| + { ID id-DC-Based-Duplication-Activation CRITICALITY reject EXTENSION DuplicationActivation PRESENCE optional }| + { ID id-AdditionalPDCPDuplicationTNL-List CRITICALITY ignore EXTENSION AdditionalPDCPDuplicationTNL-List PRESENCE optional }| + { ID id-RLCDuplicationInformation CRITICALITY ignore EXTENSION RLCDuplicationInformation PRESENCE optional }| + { ID id-TransmissionStopIndicator CRITICALITY ignore EXTENSION TransmissionStopIndicator PRESENCE optional }| + { ID id-CG-SDTIndicatorMod CRITICALITY reject EXTENSION CG-SDTIndicatorMod PRESENCE optional }, + ... +} + +``` + +``` + +DRBs-ToBeReleased-Item ::= SEQUENCE { + dRBID DRBID, + iE-Extensions ProtocolExtensionContainer { { DRBs-ToBeReleased-ItemExtIEs } } OPTIONAL, + ... +} + +``` + +``` + +DRBs-ToBeReleased-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +DRBs-ToBeSetup-Item ::= SEQUENCE { + dRBID DRBID, + qosInformation QoSInformation, + uLUPTNLInformation-ToBeSetup-List ULUPTNLInformation-ToBeSetup-List , +} + +``` + +``` + + rLCMode RLCMode, + uLConfiguration ULConfiguration OPTIONAL, + duplicationActivation DuplicationActivation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRBs-ToBeSetup-ItemExtIEs } } OPTIONAL, + ... +} + +DRBs-ToBeSetup-ItemExtIEs FIAP-PROTOCOL-EXTENSION ::= { + { ID id-DC-Based-Duplication-Configured CRITICALITY reject EXTENSION DCBasedDuplicationConfigured PRESENCE optional }| + { ID id-DC-Based-Duplication-Activation CRITICALITY reject EXTENSION DuplicationActivation PRESENCE optional }| + { ID id-DLPDCPSNLength CRITICALITY ignore EXTENSION PDCPSNLength PRESENCE mandatory }| + { ID id-ULPDCPSNLength CRITICALITY ignore EXTENSION PDCPSNLength PRESENCE optional }| + { ID id-AdditionalPDCPDuplicationTNL-List CRITICALITY ignore EXTENSION AdditionalPDCPDuplicationTNL-List PRESENCE optional }| + { ID id-RLCDuplicationInformation CRITICALITY ignore EXTENSION RLCDuplicationInformation PRESENCE optional }| + { ID id-SDTRLCBearerConfiguration CRITICALITY ignore EXTENSION SDTRLCBearerConfiguration PRESENCE optional }, + ... +} + +DRBs-ToBeSetupMod-Item ::= SEQUENCE { + dRBID DRBID, + qosInformation QoSInformation, + uLUPTNLInformation-ToBeSetup-List ULUPTNLInformation-ToBeSetup-List, + rLCMode RLCMode, +} + +``` + +``` + +uLConfiguration ULConfiguration OPTIONAL, +duplicationActivation DuplicationActivation OPTIONAL, +iE-Extensions ProtocolExtensionContainer { { DRBs-ToBeSetupMod-ItemExtIEs } } OPTIONAL, +... +} + +DRBs-ToBeSetupMod-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-DC-Based-Duplication-Configured CRITICALITY reject EXTENSION DCBasedDuplicationConfigured PRESENCE optional }| + { ID id-DC-Based-Duplication-Activation CRITICALITY reject EXTENSION DuplicationActivation PRESENCE optional }| + { ID id-DLPDCPSNLength CRITICALITY ignore EXTENSION PDCPSNLength PRESENCE optional }| + { ID id-ULPDCPSNLength CRITICALITY ignore EXTENSION PDCPSNLength PRESENCE optional }| + { ID id-AdditionalPDCPDuplicationTNL-List CRITICALITY ignore EXTENSION AdditionalPDCPDuplicationTNL-List PRESENCE optional }| + { ID id-RLCDuplicationInformation CRITICALITY ignore EXTENSION RLCDuplicationInformation PRESENCE optional}| + { ID id-CG-SDTIndicatorSetup CRITICALITY reject EXTENSION CG-SDTIndicatorSetup PRESENCE optional }, + ... +} + +DRB-List ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-List-Item + +DRB-List-Item ::= SEQUENCE { + drbid DRBID, + iE-Extensions ProtocolExtensionContainer { { DRB-List-Item-ExtIEs } } OPTIONAL +} + +DRB-List-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +``` + +``` + ... +} + +DRXCycle ::= SEQUENCE { + longDRXCycleLength LongDRXCycleLength, + shortDRXCycleLength ShortDRXCycleLength OPTIONAL, + shortDRXCycleTimer ShortDRXCycleTimer OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRXCycle-ExtIEs } } OPTIONAL, + ... +} + +DRXCycle-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +DRX-Config ::= OCTET STRING + +DRXConfigurationIndicator ::= ENUMERATED{ release, ...} + +DRX-LongCycleStartOffset ::= INTEGER (0..10239) + +DSInformationList ::= SEQUENCE (SIZE(0..maxnoofDSInfo)) OF DSCP + +DSCP ::= BIT STRING (SIZE (6)) +``` + +DUtoCURRContainer ::= OCTET STRING + +DUCURadioInformationType ::= CHOICE { +    rIM                          DUCURIMInformation, +    choice-extension          ProtocolIE-SingleContainer { { DUCURadioInformationType-ExtIEs } } +} + +DUCURadioInformationType-ExtIEs FLAP-PROTOCOL-IES ::= { +    ... +} + +DUCURIMInformation ::= SEQUENCE { +    victimgNBSetID          GNBSetID, +    rIMRSDetectionStatus  RIMRSDetectionStatus, +    aggressorCellList     AggressorCellList, +    iE-Extensions         ProtocolExtensionContainer { { DUCURIMInformation-ExtIEs } }    OPTIONAL +} + +DUCURIMInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +DUF-Slot-Config-Item ::= CHOICE { +    explicitFormat         ExplicitFormat, +} + +``` + implicitFormat ImplicitFormat, + choice-extension ProtocolIE-SingleContainer { { DUF-Slot-Config-Item-ExtIEs} } +} + +DUF-Slot-Config-Item-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +DUF-Slot-Config-List ::= SEQUENCE (SIZE(1..maxnoofDUFSlots)) OF DUF-Slot-Config-Item + +DUFSlotformatIndex ::= INTEGER(0..254) + +DUFTTransmissionPeriodicity ::= ENUMERATED { ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10, ...} + +DU-RX-MT-RX ::= ENUMERATED {supported, not-supported } + +DU-TX-MT-TX ::= ENUMERATED {supported, not-supported } + +DU-RX-MT-TX ::= ENUMERATED {supported, not-supported } + +DU-TX-MT-RX ::= ENUMERATED {supported, not-supported } + +DU-RX-MT-RX-Extend ::= ENUMERATED {supported, not-supported, supported-and-FDM-required, ...} + +DU-TX-MT-TX-Extend ::= ENUMERATED {supported, not-supported, supported-and-FDM-required, ...} +``` + +DU-RX-MT-TX-Extend ::= ENUMERATED {supported, not-supported, supported-and-FDM-required, ...} + +DU-TX-MT-RX-Extend ::= ENUMERATED {supported, not-supported, supported-and-FDM-required, ...} + +DUtoCURRCInformation ::= SEQUENCE { + cellGroupConfig CellGroupConfig, + measGapConfig MeasGapConfig OPTIONAL, + requestedP-MaxFR1 OCTET STRING OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DUtoCURRCInformation-ExtIEs } } OPTIONAL, + ... +} + +DUtoCURRCInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-DRX-LongCycleStartOffset CRITICALITY ignore EXTENSION DRX-LongCycleStartOffset PRESENCE optional } | + { ID id-SelectedBandCombinationIndex CRITICALITY ignore EXTENSION SelectedBandCombinationIndex PRESENCE optional } | + { ID id-SelectedFeatureSetEntryIndex CRITICALITY ignore EXTENSION SelectedFeatureSetEntryIndex PRESENCE optional } | + { ID id-Ph-InfoSCG CRITICALITY ignore EXTENSION Ph-InfoSCG PRESENCE optional } | + { ID id-RequestedBandCombinationIndex CRITICALITY ignore EXTENSION RequestedBandCombinationIndex PRESENCE optional } | + { ID id-RequestedFeatureSetEntryIndex CRITICALITY ignore EXTENSION RequestedFeatureSetEntryIndex PRESENCE optional } | + { ID id-DRX-Config CRITICALITY ignore EXTENSION DRX-Config PRESENCE optional } | + { ID id-PDCCH-BlindDetectionSCG CRITICALITY ignore EXTENSION PDCCH-BlindDetectionSCG PRESENCE optional } | + { ID id-Requested-PDCCH-BlindDetectionSCG CRITICALITY ignore EXTENSION Requested-PDCCH-BlindDetectionSCG PRESENCE optional } | + { ID id-Ph-InfoMCG CRITICALITY ignore EXTENSION Ph-InfoMCG PRESENCE optional } | +} + +``` + + { ID id-MeasGapSharingConfig CRITICALITY ignore EXTENSION MeasGapSharingConfig PRESENCE optional }| + { ID id-SL-PHY-MAC-RLC-Config CRITICALITY ignore EXTENSION SL-PHY-MAC-RLC-Config PRESENCE optional }| + { ID id-SL-ConfigDedicatedEUTRA-Info CRITICALITY ignore EXTENSION SL-ConfigDedicatedEUTRA-Info PRESENCE optional }| + { ID id-RequestedP-MaxFR2 CRITICALITY ignore EXTENSION RequestedP-MaxFR2 PRESENCE optional }| + { ID id-SDT-MAC-PHY-CG-Config CRITICALITY ignore EXTENSION SDT-MAC-PHY-CG-Config PRESENCE optional }| + { ID id-MUSIM-GapConfig CRITICALITY ignore EXTENSION MUSIM-GapConfig PRESENCE optional }| + { ID id-SL-RLC-ChannelToAddModList CRITICALITY ignore EXTENSION SL-RLC-ChannelToAddModList PRESENCE optional }| + { ID id-InterFrequencyConfig-NoGap CRITICALITY ignore EXTENSION InterFrequencyConfig-NoGap PRESENCE optional }| + { ID id-UL-GapFR2-Config CRITICALITY ignore EXTENSION UL-GapFR2-Config PRESENCE optional }| + { ID id-TwoPHRModeMCG CRITICALITY ignore EXTENSION TwoPHRModeMCG PRESENCE optional }| + { ID id-TwoPHRModeSCG CRITICALITY ignore EXTENSION TwoPHRModeSCG PRESENCE optional }| + { ID id-ncd-SSB-RedCapInitialBWP-SDT CRITICALITY ignore EXTENSION Ncd-SSB-RedCapInitialBWP-SDT PRESENCE optional }| + { ID id-ServCellInfoList CRITICALITY ignore EXTENSION ServCellInfoList PRESENCE optional }, + ... +} + +``` + +``` +DuplicationActivation ::= ENUMERATED{active,inactive,... } +``` + +``` +DuplicationIndication ::= ENUMERATED {true, ... , false } +``` + +``` +DuplicationState ::= ENUMERATED { + active, + inactive, + ... +} +``` + +``` + +} + +Dynamic5QIDescriptor := SEQUENCE { + qosPriorityLevel INTEGER (1..127), + packetDelayBudget PacketDelayBudget, + packetErrorRate PacketErrorRate, + fiveQI INTEGER (0..255, ...) OPTIONAL, + delayCritical ENUMERATED {delay-critical, non-delay-critical} OPTIONAL, + -- C-ifGBRflow: This IE shall be present if the GBR QoS Flow Information IE is present in the QoS Flow Level QoS Parameters IE. + averagingWindow AveragingWindow OPTIONAL, + -- C-ifGBRflow: This IE shall be present if the GBR QoS Flow Information IE is present in the QoS Flow Level QoS Parameters IE. + maxDataBurstVolume MaxDataBurstVolume OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Dynamic5QIDescriptor-ExtIEs } } OPTIONAL +} + +``` + +``` + +Dynamic5QIDescriptor-ExtIEs FLAP-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 }, + ... +} + +``` + +``` + +DynamicPQIDescriptor := SEQUENCE { + resourceType ENUMERATED {gbr, non-gbr, delay-critical-grb, ...} OPTIONAL, + +``` + +``` + qosPriorityLevel INTEGER (1..8, ...), + packetDelayBudget PacketDelayBudget, + packetErrorRate PacketErrorRate, + averagingWindow AveragingWindow OPTIONAL, + -- C-ifGBRflow: This IE shall be present if the GBR QoS Flow Information IE is present in the QoS Flow Level QoS Parameters IE. + maxDataBurstVolume MaxDataBurstVolume OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DynamicPQIDescriptor-ExtIEs } } OPTIONAL +} +``` + +``` +DynamicPQIDescriptor-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +-- E + +``` +EarlySyncInformation-Request ::= SEQUENCE { + requestforRACHConfiguration RequestforRACHConfiguration OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { EarlySyncInformation-Request-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +EarlySyncInformation-Request-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +} + +EarlySyncInformation ::= SEQUENCE { + +tCIStatesConfigurationsList TCISTatesConfigurationsList, + +rACHConfiguration RACHConfiguration + +OPTIONAL, iE-Extensions + +ProtocolExtensionContainer { { EarlySyncInformation-ExtIEs } } OPTIONAL, + +... + +} + +EarlySyncInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +EarlySyncInformation-List ::= SEQUENCE (SIZE (1.. maxnoofLTMCells)) OF EarlySyncInformation-Item + +EarlySyncInformation-Item ::= SEQUENCE { + +nRCGI NRCGI, + +rACHConfiguration RACHConfiguration + +OPTIONAL, + +tCIStatesConfigurationsList + +TCISTatesConfigurationsList + +OPTIONAL, + +iE-Extensions ProtocolExtensionContainer { { EarlySyncInformation-Item-ExtIEs } } OPTIONAL, + +... + +} + +EarlySyncInformation-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +``` + ... +} + +E-CID-MeasurementQuantities ::= SEQUENCE (SIZE (1.. maxnoofMeasE-CID)) OF ProtocolIE-SingleContainer { {E-CID-MeasurementQuantities-ItemIEs} } + +E-CID-MeasurementQuantities-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-E-CID-MeasurementQuantities-Item CRITICALITY reject TYPE E-CID-MeasurementQuantities-Item PRESENCE mandatory} +} + +E-CID-MeasurementQuantities-Item ::= SEQUENCE { + e-CIDMeasurementQuantitiesValue E-CID-MeasurementQuantitiesValue, + iE-Extensions ProtocolExtensionContainer { { E-CID-MeasurementQuantitiesValue-ExtIEs} } OPTIONAL +} + +E-CID-MeasurementQuantitiesValue-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +E-CID-MeasurementQuantitiesValue ::= ENUMERATED { + default, + angleOfArrivalNR, + ... / + timingAdvanceNR +``` + +``` +} + +E-CID-MeasurementResult ::= SEQUENCE { + geographicalCoordinates GeographicalCoordinates OPTIONAL, + measuredResults-List E-CID-MeasuredResults-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { E-CID-MeasurementResult-ExtIEs} } OPTIONAL +} + +E-CID-MeasurementResult-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-MobileAccessPointLocation CRITICALITY ignore EXTENSION Mobile-TRP-LocationInformation PRESENCE optional }, + ... +} + +E-CID-MeasuredResults-List ::= SEQUENCE (SIZE(1..maxnoofMeasE-CID)) OF E-CID-MeasuredResults-Item + +E-CID-MeasuredResults-Item ::= SEQUENCE { + e-CID-MeasuredResults-Value E-CID-MeasuredResults-Value, + iE-Extensions ProtocolExtensionContainer {{ E-CID-MeasuredResults-Item-ExtIEs }} OPTIONAL +} + +E-CID-MeasuredResults-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +E-CID-MeasuredResults-Value ::= CHOICE { + valueAngleofArrivalNR UL-AoA, + choice-extension ProtocolIE-SingleContainer { { E-CID-MeasuredResults-Value-ExtIEs} } +} + +E-CID-MeasuredResults-Value-ExtIEs FIAP-PROTOCOL-IES ::= { + { ID id-NR-TADV CRITICALITY ignore TYPE NR-TADV PRESENCE mandatory }, + ... +} + +E-CID-ReportCharacteristics ::= ENUMERATED { + onDemand, + periodic, + ... +} + +EgressBHRLCCHList ::= SEQUENCE (SIZE(1..maxnoofEgressLinks)) OF EgressBHRLCCHItem + +EgressBHRLCCHItem ::= SEQUENCE { + nextHopBAPAddress BAPAddress, + bHRLCChannelID BHRLCChannelID, + iE-Extensions ProtocolExtensionContainer {{EgressBHRLCCHItemExtIEs }} OPTIONAL +} +``` + +``` +EgressBHRLCCHItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +EgressNonFlterminatingTopologyIndicator ::= ENUMERATED {true, ...} + +Endpoint-IP-address-and-port ::=SEQUENCE { + endpointIPAddress TransportLayerAddress, + iE-Extensions ProtocolExtensionContainer { { Endpoint-IP-address-and-port-ExtIEs} } OPTIONAL +} + +Endpoint-IP-address-and-port-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-portNumber CRITICALITY reject EXTENSION PortNumber PRESENCE optional}, + ... +} + +EnergyDetectionThreshold ::= INTEGER (-100..-50, ...) + +ExtendedAvailablePLMN-List ::= SEQUENCE (SIZE(1..maxnoofExtendedBPLMNs)) OF ExtendedAvailablePLMN-Item + +ExtendedAvailablePLMN-Item ::= SEQUENCE { + pLMNIdentity PLMN-Identity, + iE-Extensions ProtocolExtensionContainer { { ExtendedAvailablePLMN-Item-ExtIEs} } OPTIONAL +} +``` + +``` +ExplicitFormat ::= SEQUENCE { + permutation Permutation, + noofDownlinkSymbols NoofDownlinkSymbols OPTIONAL, + noofUplinkSymbols NoofUplinkSymbols OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { ExplicitFormat-ExtIEs } } OPTIONAL +} + +ExplicitFormat-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +ExtendedAvailablePLMN-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +ExtendedServedPLMNs-List ::= SEQUENCE (SIZE(1.. maxnoofExtendedBPLMNs)) OF ExtendedServedPLMNs-Item + +ExtendedServedPLMNs-Item ::= SEQUENCE { + pLMN-Identity PLMN-Identity, + tAISliceSupportList SliceSupportList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { ExtendedServedPLMNs-ItemExtIEs } } OPTIONAL, + ... +} +``` + +``` +ExtendedServedPLMNs-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-NPNSupportInfo CRITICALITY reject EXTENSION NPNSupportInfo PRESENCE optional }| + { ID id-ExtendedTAISliceSupportList CRITICALITY reject EXTENSION ExtendedSliceSupportList PRESENCE optional }| + { ID id-TAINSAGSupportList CRITICALITY ignore EXTENSION NSAGSupportList PRESENCE optional}, + ... +} + +ExtendedSliceSupportList ::= SEQUENCE (SIZE(1.. maxnoofExtSliceItems)) OF SliceSupportItem + +ExtendedUEIdentityIndexValue ::= BIT STRING (SIZE(16)) + +EUTRACells-List ::= SEQUENCE (SIZE (1.. maxCellineNB)) OF EUTRACells-List-item + +EUTRACells-List-item ::= SEQUENCE { + eUTRA-Cell-ID EUTRA-Cell-ID, + served-EUTRA-Cells-Information Served-EUTRA-Cells-Information, + iE-Extensions ProtocolExtensionContainer { { EUTRACells-List-itemExtIEs } } OPTIONAL +} + +EUTRACells-List-itemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +EUTRA-Cell-ID ::= BIT STRING (SIZE(28)) + +EUTRA-Coex-FDD-Info ::= SEQUENCE { +    uL-EARFCN                    ExtendedEARFCN                    OPTIONAL, +    dL-EARFCN                    ExtendedEARFCN, +    uL-Transmission-Bandwidth    EUTRA-Transmission-Bandwidth    OPTIONAL, +    dL-Transmission-Bandwidth    EUTRA-Transmission-Bandwidth, +    iE-Extensions                ProtocolExtensionContainer { {EUTRA-Coex-FDD-Info-ExtIEs} } OPTIONAL, +    ... +} + +EUTRA-Coex-FDD-Info-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +EUTRA-Coex-Mode-Info ::= CHOICE { +    fDD    EUTRA-Coex-FDD-Info, +    tDD    EUTRA-Coex-TDD-Info, +    ... +} + +EUTRA-Coex-TDD-Info ::= SEQUENCE { +    eARFCN                        ExtendedEARFCN, + +``` + transmission-Bandwidth EUTRA-Transmission-Bandwidth, + subframeAssignment EUTRA-SubframeAssignment, + specialSubframe-Info EUTRA-SpecialSubframe-Info, + iE-Extensions ProtocolExtensionContainer { {EUTRA-Coex-TDD-Info-ExtIEs} } OPTIONAL, + ... +} + +EUTRA-Coex-TDD-Info-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +EUTRA-CyclicPrefixDL ::= ENUMERATED { + normal, + extended, + ... +} + +EUTRA-CyclicPrefixUL ::= ENUMERATED { + normal, + extended, + ... +} + +EUTRA-PRACH-Configuration ::= SEQUENCE { + rootSequenceIndex INTEGER (0..837), + zeroCorrelationIndex INTEGER (0..15), +} +``` + +``` + highSpeedFlag BOOLEAN, + prach-FreqOffset INTEGER (0..94), + prach-ConfigIndex INTEGER (0..63) OPTIONAL, + -- C-iftDD: This IE shall be present if the EUTRA-Mode-Info IE in the Resource Coordination E-UTRA Cell Information IE is set to the value + "TDD" + iE-Extensions ProtocolExtensionContainer { {EUTRA-PRACH-Configuration-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +EUTRA-PRACH-Configuration-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +EUTRA-SpecialSubframe-Info ::= SEQUENCE { + specialSubframePatterns EUTRA-SpecialSubframePatterns, + cyclicPrefixDL EUTRA-CyclicPrefixDL, + cyclicPrefixUL EUTRA-CyclicPrefixUL, + iE-Extensions ProtocolExtensionContainer { { EUTRA-SpecialSubframe-Info-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +EUTRA-SpecialSubframe-Info-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +EUTRA-SpecialSubframePatterns ::= ENUMERATED { + ssp0, + ssp1, + ssp2, + ssp3, + ssp4, + ssp5, + ssp6, + ssp7, + ssp8, + ssp9, + ssp10, + ... +} +``` + +``` +EUTRA-SubframeAssignment ::= ENUMERATED { + sa0, + sa1, + sa2, + sa3, + sa4, + sa5, + sa6, +``` + +``` + ... +} + +EUTRA-Transmission-Bandwidth ::= ENUMERATED { + bw6, + bw15, + bw25, + bw50, + bw75, + bw100, + ... +} + +EUTRANQoS ::= SEQUENCE { + qCI QCI, + allocationAndRetentionPriority AllocationAndRetentionPriority, + gbrQosInformation GBR-QosInformation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { EUTRANQoS-ExtIEs} } OPTIONAL, + ... +} + +EUTRANQoS-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-ENBDLTLNAddress CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE optional }, + ... +} +``` + +} + +ExecuteDuplication ::= ENUMERATED{true,...} + +ExtendedEARFCN ::= INTEGER (0..262143) + +EUTRA-Mode-Info ::= CHOICE { +    eUTRAFDD          EUTRA-FDD-Info, +    eUTRATDD          EUTRA-TDD-Info, +    choice-extension  ProtocolIE-SingleContainer { { EUTRA-Mode-Info-ExtIEs } } +} + +EUTRA-Mode-Info-ExtIEs FIAP-PROTOCOL-IES ::= { +    ... +} + +EUTRA-NR-CellResourceCoordinationReq-Container ::= OCTET STRING + +EUTRA-NR-CellResourceCoordinationReqAck-Container ::= OCTET STRING + +EUTRA-FDD-Info ::= SEQUENCE { +    uL-offsetToPointA          OffsetToPointA, +    dL-offsetToPointA          OffsetToPointA, +    iE-Extensions            ProtocolExtensionContainer { { EUTRA-FDD-Info-ExtIEs } } OPTIONAL, + +``` + ... +} + +EUTRA-FDD-Info-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +EUTRA-TDD-Info ::= SEQUENCE { + offsetToPointA OffsetToPointA, + iE-Extensions ProtocolExtensionContainer { {EUTRA-TDD-Info-ExtIEs} } OPTIONAL, + ... +} + +EUTRA-TDD-Info-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +EventType ::= ENUMERATED { + on-demand, + periodic, + stop, + ... +} +``` + +ExtendedPacketDelayBudget ::= INTEGER (1..65535, ..., 65536..109999) + +Expected-UL-AoA ::= SEQUENCE { +    expected-Azimuth-AoA    Expected-Azimuth-AoA, +    expected-Zenith-AoA    Expected-Zenith-AoA    OPTIONAL, +    iE-extensions    ProtocolExtensionContainer { { Expected-UL-AoA-ExtIEs } } OPTIONAL, +    ... +} + +Expected-UL-AoA-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +Expected-ZoA-only ::= SEQUENCE { +    expected-ZoA-only    Expected-Zenith-AoA, +    iE-extensions    ProtocolExtensionContainer { { Expected-ZoA-only-ExtIEs } } OPTIONAL, +    ... +} + +Expected-ZoA-only-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +Expected-Azimuth-AoA ::= SEQUENCE { +    expected-Azimuth-AoA-value    Expected-Value-AoA, + +``` + expected-Azimuth-AoA-uncertainty Uncertainty-range-AoA, + iE-Extensions ProtocolExtensionContainer { { Expected-Azimuth-AoA-ExtIEs } } OPTIONAL, + ... +} + +Expected-Azimuth-AoA-ExtIEs FIAP-PROTOCOL-EXTENSION ::= { + ... +} + +Expected-Zenith-AoA ::= SEQUENCE { + expected-Zenith-AoA-value Expected-Value-ZoA, + expected-Zenith-AoA-uncertainty Uncertainty-range-ZoA, + iE-Extensions ProtocolExtensionContainer { { Expected-Zenith-AoA-ExtIEs } } OPTIONAL, + ... +} + +Expected-Zenith-AoA-ExtIEs FIAP-PROTOCOL-EXTENSION ::= { + ... +} + +Expected-Value-AoA ::= INTEGER (0..3599) + +Expected-Value-ZoA ::= INTEGER (0..1799) + +ECNMarkingorCongestionInformationReportingRequest ::= CHOICE { +``` + +``` + ecnMarking ECNmarkingRequest, + congestionInformation CongestionInformationRequest, + choice-extension ProtocolIE-SingleContainer { { ECNMarkingorCongestionInformationReportingRequest-ExtIEs } } +} + +ECNMarkingorCongestionInformationReportingRequest-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +ECNmarkingRequest ::= ENUMERATED { ul, dl, both, stop, ... } + +CongestionInformationRequest ::= ENUMERATED { ul, dl, both, stop, ... } + +ECNMarkingorCongestionInformationReportingStatus ::= ENUMERATED { active, not-active, ... } + +-- F + +F1CPathNSA ::= ENUMERATED { lte, nr, both } + +F1CTransferPath ::= SEQUENCE { + f1CPathNSA F1CPathNSA, + iE-Extensions ProtocolExtensionContainer { { F1CTransferPath-ExtIEs } } OPTIONAL, + ... +} + +F1CTransferPath-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +FlCPathNRDC ::= ENUMERATED {mcg, scg, both} + +FlCTransferPathNRDC ::= SEQUENCE { + flCPathNRDC FlCPathNRDC, + iE-Extensions ProtocolExtensionContainer { { FlCTransferPathNRDC-ExtIEs} } OPTIONAL, + ... +} + +FlCTransferPathNRDC-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +FlUTunnelNotEstablished ::= ENUMERATED { + true, + ... +} + +FDD-Info ::= SEQUENCE { + uL-NRFreqInfo NRFreqInfo, + dL-NRFreqInfo NRFreqInfo, + uL-Transmission-Bandwidth Transmission-Bandwidth, +``` + +``` +dL-Transmission-Bandwidth Transmission-Bandwidth, +iE-Extensions ProtocolExtensionContainer { {FDD-Info-ExtIEs} } OPTIONAL, +... +} + +FDD-Info-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-ULCarrierList CRITICALITY ignore EXTENSION NRCarrierList PRESENCE optional } | + { ID id-DLCarrierList CRITICALITY ignore EXTENSION NRCarrierList PRESENCE optional }, + ... +} + +FDD-InfoRel16 ::= SEQUENCE { + uL-FreqInfo FreqInfoRel16 OPTIONAL, + sUL-FreqInfo FreqInfoRel16 OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {FDD-InfoRel16-ExtIEs} } OPTIONAL, + ... +} + +FDD-InfoRel16-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +FiveG-ProSeAuthorized ::= SEQUENCE { + fiveG-proSeDirectDiscovery FiveG-ProSeDirectDiscovery OPTIONAL, +``` + +``` + + fiveG-ProSeDirectCommunication FiveG-ProSeDirectCommunication OPTIONAL, + fiveG-ProSeLayer2UEtoNetworkRelay FiveG-ProSeLayer2UEtoNetworkRelay OPTIONAL, + fiveG-ProSeLayer3UEtoNetworkRelay FiveG-ProSeLayer3UEtoNetworkRelay OPTIONAL, + fiveG-ProSeLayer2RemoteUE FiveG-ProSeLayer2RemoteUE OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {FiveG-ProSeAuthorized-ExtIEs} } OPTIONAL, + ... +} + +FiveG-ProSeAuthorized-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-FiveG-ProSeLayer2Multipath CRITICALITY ignore EXTENSION FiveG-ProSeLayer2Multipath PRESENCE optional }| + { ID id-FiveG-ProSeLayer2UEtoUERelay CRITICALITY ignore EXTENSION FiveG-ProSeLayer2UEtoUERelay PRESENCE optional }| + { ID id-FiveG-ProSeLayer2UEtoUERemote CRITICALITY ignore EXTENSION FiveG-ProSeLayer2UEtoUERemote PRESENCE optional }, + ... +} + +FiveG-ProSeDirectDiscovery ::= ENUMERATED { + authorized, + not-authorized, + ... +} + +FiveG-ProSeDirectCommunication ::= ENUMERATED { + authorized, + not-authorized, +} + +``` + +``` + ... +} + +FiveG-ProSeLayer2UEtoNetworkRelay ::= ENUMERATED { + authorized, + not-authorized, + ... +} + +FiveG-ProSeLayer3UEtoNetworkRelay ::= ENUMERATED { + authorized, + not-authorized, + ... +} + +FiveG-ProSeLayer2RemoteUE ::= ENUMERATED { + authorized, + not-authorized, + ... +} + +FiveG-ProSeLayer2Multipath ::= ENUMERATED { + authorized, + not-authorized, +``` + +``` + ... +} + +FiveG-ProSeLayer2UEtoUERelay ::= ENUMERATED { + authorized, + not-authorized, + ... +} + +FiveG-ProSeLayer2UEtoUERemote ::= ENUMERATED { + authorized, + not-authorized, + ... +} + +Flows-Mapped-To-DRB-List ::= SEQUENCE (SIZE(1.. maxnoofQoSFlows)) OF Flows-Mapped-To-DRB-Item + +Flows-Mapped-To-DRB-Item ::= SEQUENCE { + qosFlowIdentifier QoSFlowIdentifier, + qosFlowLevelQoSParameters QoSFlowLevelQoSParameters, + iE-Extensions ProtocolExtensionContainer { { Flows-Mapped-To-DRB-ItemExtIEs} } OPTIONAL +} +``` + +``` +Flows-Mapped-To-DRB-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + {ID id-QoSFlowMappingIndication CRITICALITY ignore EXTENSION QoSFlowMappingIndication PRESENCE optional}| + {ID id-TSCTrafficCharacteristics CRITICALITY ignore EXTENSION TSCTrafficCharacteristics PRESENCE optional}, + ... +} +``` + +``` +FR1-Bandwidth ::= ENUMERATED {bw5, bw10, bw20, bw40, bw50, bw80, bw100, ...} +``` + +``` +FR2-Bandwidth ::= ENUMERATED {bw50, bw100, bw200, bw400, ..., bw800, bw1600, bw2000} +``` + +``` +FreqBandNrItem ::= SEQUENCE { + freqBandIndicatorNr INTEGER (1..1024,...), + supportedSULBandList SEQUENCE (SIZE(0..maxnoofNrCellBands)) OF SupportedSULFreqBandItem, + iE-Extensions ProtocolExtensionContainer { {FreqBandNrItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +FreqBandNrItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +FreqDomainLength ::= CHOICE { + 1839 L839Info, + 1139 L139Info, +``` + +``` + + choice-extension ProtocolIE-SingleContainer { { FreqDomainLength-ExtIEs} } +} + +FreqDomainLength-ExtIEs FLAP-PROTOCOL-IES ::= { + { ID id-L571Info CRITICALITY reject TYPE L571Info PRESENCE mandatory}| + { ID id-L1151Info CRITICALITY reject TYPE L1151Info PRESENCE mandatory}, + ... +} + +FreqInfoRel16 ::= SEQUENCE { + nRARFCN INTEGER (0..maxNRARFCN) OPTIONAL, + frequencyShift7p5khz FrequencyShift7p5khz OPTIONAL, + carrierList NRCarrierList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { FreqInfoRel16-ExtIEs} } OPTIONAL, + ... +} + +FreqInfoRel16-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +FrequencyShift7p5khz ::= ENUMERATED {false, true, ...} + +Frequency-Domain-HSNA-Configuration-List ::= SEQUENCE (SIZE(1..maxnoofRBsetsPerCell)) OF Frequency-Domain-HSNA-Configuration-Item + +``` + +``` +Frequency-Domain-HSNA-Configuration-Item ::= SEQUENCE { + rBSetIndex INTEGER (0..maxnoofRBsetsPerCell-1, ...), + frequency-Domain-HSNA-Slot-Configuration-List Frequency-Domain-HSNA-Slot-Configuration-List, + iE-Extensions ProtocolExtensionContainer { { Frequency-Domain-HSNA-Configuration-Item-ExtIEs } } OPTIONAL +} + +Frequency-Domain-HSNA-Configuration-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +Frequency-Domain-HSNA-Slot-Configuration-List ::= SEQUENCE (SIZE(1..maxnoofHSNASlots)) OF Frequency-Domain-HSNA-Slot-Configuration-Item + +Frequency-Domain-HSNA-Slot-Configuration-Item ::= SEQUENCE { + slotIndex INTEGER (0..5119) OPTIONAL, + hSNADownlink HSNADownlink OPTIONAL, + hSNAUplink HSNAUplink OPTIONAL, + hSNAFlexible HSNAFlexible OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Frequency-Domain-HSNA-Slot-Configuration-Item-ExtIEs } } OPTIONAL +} + +Frequency-Domain-HSNA-Slot-Configuration-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +} + +FullConfiguration ::= ENUMERATED {full, ...} + +FlowsMappedToSLDRB-List ::= SEQUENCE (SIZE(1.. maxnoofPC5QoSFlows)) OF FlowsMappedToSLDRB-Item + +FlowsMappedToSLDRB-Item ::= SEQUENCE { +    pc5QoSFlowIdentifier            PC5QoSFlowIdentifier, +    iE-Extensions                    ProtocolExtensionContainer { {FlowsMappedToSLDRB-Item-ExtIEs} } OPTIONAL, +    ... +} + +FlowsMappedToSLDRB-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +-- G + +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 FLAP-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 FLAP-PROTOCOL-EXTENSION ::= { + { ID id-AlternativeQoSParaSetList CRITICALITY ignore EXTENSION AlternativeQoSParaSetList PRESENCE optional }, + ... +} +``` + +CG-Config ::= OCTET STRING + +GeographicalCoordinates ::= SEQUENCE { +    tRPPositionDefinitionType    TRPPositionDefinitionType, +    dLPRSResourceCoordinates    DLPRSResourceCoordinates    OPTIONAL, +    iE-Extensions                ProtocolExtensionContainer { { GeographicalCoordinates-ExtIEs } } OPTIONAL +} + +GeographicalCoordinates-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    { ID id-ARPLocationInfo    CRITICALITY ignore EXTENSION ARPLocationInformation PRESENCE optional}, +    ... +} + +GlobalGNB-ID ::= SEQUENCE { +    pLMNIdentity                PLMN-Identity, +    gNB-ID                        GNB-ID, +    iE-Extensions                ProtocolExtensionContainer { {GlobalGNB-ID-ExtIEs} } OPTIONAL, +    ... +} + +GlobalGNB-ID-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +GNB-ID ::= CHOICE { + +``` +gNB-ID BIT STRING (SIZE(22..32)), +choice-Extensions ProtocolIE-SingleContainer { {GNB-ID-ExtIEs} } +} + +GNB-ID-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +GNB-CU-MBS-FLAP-ID ::= INTEGER (0..4294967295) + +GNBCUMeasurementID ::= INTEGER (0.. 4095, ...) + +GNBDUMeasurementID ::= INTEGER (0.. 4095, ...) + +GNB-CUSystemInformation ::= SEQUENCE { + sibtypetobeupdatedlist SEQUENCE (SIZE(1.. maxnooSIBTypes)) OF SibtypetobeupdatedListItem, + iE-Extensions ProtocolExtensionContainer { { GNB-CUSystemInformation-ExtIEs} } OPTIONAL, + ... +} + +GNB-CUSystemInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + {ID id-systemInformationAreaID CRITICALITY ignore EXTENSION SystemInformationAreaID PRESENCE optional}, + ... +} +``` + +``` + } + + GNB-CU-TNL-Association-Setup-Item ::= SEQUENCE { + tNLAssociationTransportLayerAddress CP-TransportLayerAddress , + iE-Extensions ProtocolExtensionContainer { { GNB-CU-TNL-Association-Setup-Item-ExtIEs} } OPTIONAL + } + + GNB-CU-TNL-Association-Setup-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... + } + + GNB-CU-TNL-Association-Failed-To-Setup-Item ::= SEQUENCE { + tNLAssociationTransportLayerAddress CP-TransportLayerAddress , + cause Cause, + iE-Extensions ProtocolExtensionContainer { { GNB-CU-TNL-Association-Failed-To-Setup-Item-ExtIEs} } OPTIONAL + } + + GNB-CU-TNL-Association-Failed-To-Setup-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... + } + + GNB-CU-TNL-Association-To-Add-Item ::= SEQUENCE { + tNLAssociationTransportLayerAddress CP-TransportLayerAddress , +``` + +``` + tNLAssociationUsage TNLAssociationUsage, + iE-Extensions ProtocolExtensionContainer { { GNB-CU-TNL-Association-To-Add-Item-ExtIEs} } OPTIONAL + } + +GNB-CU-TNL-Association-To-Add-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +GNB-CU-TNL-Association-To-Remove-Item ::= SEQUENCE { + tNLAssociationTransportLayerAddress CP-TransportLayerAddress , + iE-Extensions ProtocolExtensionContainer { { GNB-CU-TNL-Association-To-Remove-Item-ExtIEs} } OPTIONAL +} + +GNB-CU-TNL-Association-To-Remove-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + {ID id-TNLAssociationTransportLayerAddressgNB DU CRITICALITY reject EXTENSION CP-TransportLayerAddress PRESENCE optional}, + ... +} + +GNB-CU-TNL-Association-To-Update-Item ::= SEQUENCE { + tNLAssociationTransportLayerAddress CP-TransportLayerAddress , + tNLAssociationUsage TNLAssociationUsage OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GNB-CU-TNL-Association-To-Update-Item-ExtIEs} } OPTIONAL +} +``` + +``` +GNB-CU-TNL-Association-To-Update-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +GNB-CU-UE-FlAP-ID ::= INTEGER (0..4294967295) + +GNB-DU-Cell-Resource-Configuration ::= SEQUENCE { + subcarrierSpacing SubcarrierSpacing, + dUFTTransmissionPeriodicity DUFTTransmissionPeriodicity OPTIONAL, + dUF-Slot-Config-List DUF-Slot-Config-List OPTIONAL, + hSNATransmissionPeriodicity HSNATransmissionPeriodicity, + hNSASlotConfigList HSNASlotConfigList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GNB-DU-Cell-Resource-Configuration-ExtIEs } } OPTIONAL +} + +GNB-DU-Cell-Resource-Configuration-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + {ID id-rBSetConfiguration CRITICALITY reject EXTENSION RBSetConfiguration PRESENCE optional}| + {ID id-frequency-Domain-HSNA-Configuration-List CRITICALITY reject EXTENSION Frequency-Domain-HSNA-Configuration-List PRESENCE optional}| + {ID id-child-IAB-Nodes-NA-Resource-List CRITICALITY reject EXTENSION Child-IAB-Nodes-NA-Resource-List PRESENCE optional}| + {ID id-Parent-IAB-Nodes-NA-Resource-Configuration-List CRITICALITY reject EXTENSION Parent-IAB-Nodes-NA-Resource-Configuration-List PRESENCE optional}, + ... +} +``` + +GNB-DU-MBS-FlAP-ID ::= INTEGER (0..4294967295) + +GNB-DU-UE-FlAP-ID ::= INTEGER (0..4294967295) + +GNB-DU-ID ::= INTEGER (0..68719476735) + +GNB-CU-Name ::= PrintableString(SIZE(1..150,...)) + +GNB-DU-Name ::= PrintableString(SIZE(1..150,...)) + +Extended-GNB-CU-Name ::= SEQUENCE { +    gNB-CU-NameVisibleString    GNB-CU-NameVisibleString    OPTIONAL, +    gNB-CU-NameUTF8String    GNB-CU-NameUTF8String    OPTIONAL, +    iE-Extensions    ProtocolExtensionContainer { { Extended-GNB-CU-Name-ExtIEs } } OPTIONAL, +    ... +} + +Extended-GNB-CU-Name-ExtIEs FlAP-PROTOCOL-EXTENSION ::= { +    ... +} + +GNB-CU-NameVisibleString ::= VisibleString(SIZE(1..150,...)) + +GNB-CU-NameUTF8String ::= UTF8String(SIZE(1..150,...)) + +Extended-GNB-DU-Name ::= SEQUENCE { +    gNB-DU-NameVisibleString    GNB-DU-NameVisibleString    OPTIONAL, +    gNB-DU-NameUTF8String    GNB-DU-NameUTF8String    OPTIONAL, +    iE-Extensions    ProtocolExtensionContainer { { Extended-GNB-DU-Name-ExtIEs } } OPTIONAL, +    ... +} + +Extended-GNB-DU-Name-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +GNB-DU-NameVisibleString ::= VisibleString(SIZE(1..150,...)) + +GNB-DU-NameUTF8String ::= UTF8String(SIZE(1..150,...)) + +GNB-DU-Served-Cells-Item ::= SEQUENCE { +    served-Cell-Information    Served-Cell-Information, +    gNB-DU-System-Information    GNB-DU-System-Information    OPTIONAL, +    iE-Extensions    ProtocolExtensionContainer { { GNB-DU-Served-Cells-ItemExtIEs } } OPTIONAL, +    ... +} + +``` +GNB-DU-Served-Cells-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +GNB-DU-System-Information ::= SEQUENCE { + mIB-message MIB-message, + sIB1-message SIB1-message, + iE-Extensions ProtocolExtensionContainer { { GNB-DU-System-Information-ExtIEs } } OPTIONAL, + ... +} + +GNB-DU-System-Information-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-SIB12-message CRITICALITY ignore EXTENSION SIB12-message PRESENCE optional}| + { ID id-SIB13-message CRITICALITY ignore EXTENSION SIB13-message PRESENCE optional}| + { ID id-SIB14-message CRITICALITY ignore EXTENSION SIB14-message PRESENCE optional}| + { ID id-SIB10-message CRITICALITY ignore EXTENSION SIB10-message PRESENCE optional}| + { ID id-SIB17-message CRITICALITY ignore EXTENSION SIB17-message PRESENCE optional}| + { ID id-SIB20-message CRITICALITY ignore EXTENSION SIB20-message PRESENCE optional}| + { ID id-SIB15-message CRITICALITY ignore EXTENSION SIB15-message PRESENCE optional}| + { ID id-SIBX-message CRITICALITY ignore EXTENSION SIBX-message PRESENCE optional}, + ... +} +``` + +GNB-DUConfigurationQuery ::= ENUMERATED {true, ...} + +GNBDUOverloadInformation ::= ENUMERATED {overloaded, not-overloaded} + +GNB-DU-TNL-Association-To-Remove-Item ::= SEQUENCE { +    tNLAssociationTransportLayerAddress           CP-TransportLayerAddress , +    tNLAssociationTransportLayerAddressgNBCU    CP-TransportLayerAddress       OPTIONAL, +    iE-Extensions                                   ProtocolExtensionContainer { { GNB-DU-TNL-Association-To-Remove-Item-ExtIEs} } OPTIONAL +} + +GNB-DU-TNL-Association-To-Remove-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +GNBDUUESliceMaximumBitRateList ::= SEQUENCE (SIZE(1.. maxnoofSMBRValues)) OF GNBDUUESliceMaximumBitRateItem + +GNBDUUESliceMaximumBitRateItem ::= SEQUENCE { +    sNSSAI                            SNSSAI, +    uESliceMaximumBitRateUL       BitRate, +    iE-Extensions                   ProtocolExtensionContainer { { GNBDUUESliceMaximumBitRateItem-ExtIEs} } OPTIONAL, +    ... +} + +GNBDUUESliceMaximumBitRateItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +``` + ... +} + +GNB-RxTxTimeDiff ::= SEQUENCE { + rxTxTimeDiff GNBRxTxTimeDiffMeas, + additionalPath-List AdditionalPath-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GNB-RxTxTimeDiff-ExtIEs } } OPTIONAL +} + +GNB-RxTxTimeDiff-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-ExtendedAdditionalPathList CRITICALITY ignore EXTENSION ExtendedAdditionalPathList PRESENCE optional } | + { ID id-TRPTEGInformation CRITICALITY ignore EXTENSION TRPTEGInformation PRESENCE optional }, + ... +} + +GNBRxTxTimeDiffMeas ::= CHOICE { + k0 INTEGER (0.. 1970049), + k1 INTEGER (0.. 985025), + k2 INTEGER (0.. 492513), + k3 INTEGER (0.. 246257), + k4 INTEGER (0.. 123129), + k5 INTEGER (0.. 61565), + choice-extension ProtocolIE-SingleContainer { { GNBRxTxTimeDiffMeas-ExtIEs } } +} +``` + +``` +GNBRxTxTimeDiffMeas-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +GNBSetID ::= BIT STRING (SIZE(22)) + +GTP-TEID ::= OCTET STRING (SIZE (4)) + +GTPTLAs ::= SEQUENCE (SIZE(1.. maxnoofGTPTLAs)) OF GTPTLA-Item + +GTPTLA-Item ::= SEQUENCE { + gTPTransportLayerAddress TransportLayerAddress, + iE-Extensions ProtocolExtensionContainer { { GTPTLA-Item-ExtIEs } } OPTIONAL +} + +GTPTLA-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +GTPTunnel ::= SEQUENCE { + transportLayerAddress TransportLayerAddress, + gTP-TEID GTP-TEID, +``` + +``` +iE-Extensions ProtocolExtensionContainer { { GTP Tunnel-ExtIEs } } OPTIONAL, +... +} + +GTP Tunnel-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- H + +HandoverPreparationInformation ::= OCTET STRING + +HardwareLoadIndicator ::= SEQUENCE { + dLHardwareLoadIndicator INTEGER (0..100, ...), + uLHardwareLoadIndicator INTEGER (0..100, ...), + iE-Extensions ProtocolExtensionContainer { { HardwareLoadIndicator-ExtIEs } } OPTIONAL, + ... +} + +HardwareLoadIndicator-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +HSNASlotConfigList ::= SEQUENCE (SIZE(1..maxnoofHSNASlots)) OF HSNASlotConfigItem +``` + +``` +HSNASlotConfigItem ::= SEQUENCE { + hSNADownlink HSNADownlink OPTIONAL, + hSNAUplink HSNAUplink OPTIONAL, + hSNAFlexible HSNAFlexible OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { HSNASlotConfigItem-ExtIEs } } OPTIONAL +} + +HSNASlotConfigItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +HSNADownlink ::= ENUMERATED { hard, soft, notavailable } + +hSNAFlexible ::= ENUMERATED { hard, soft, notavailable } + +hSNAUplink ::= ENUMERATED { hard, soft, notavailable } + +HSNATransmissionPeriodicity ::= ENUMERATED { ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10, ms20, ms40, ms80, ms160, ... } + +HashedUEIdentityIndexValue ::= BIT STRING (SIZE(13, ...)) + +-- I +``` + +IAB-Barred ::= ENUMERATED {barred, not-barred, ...} + +IABConditionalRRMessageDeliveryIndication ::= ENUMERATED {true, ...} + +IABCongestionIndication ::= SEQUENCE { +    iAB-Congestion-Indication-List            IAB-Congestion-Indication-List, +    iE-Extensions    ProtocolExtensionContainer { { IAB-Congestion-Indication-List-ExtIEs } } OPTIONAL +} + +IAB-Congestion-Indication-List-ExtIEs    FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +IAB-Congestion-Indication-List ::= SEQUENCE (SIZE(1..maxnoofIABCongInd)) OF IAB-Congestion-Indication-Item + +IAB-Congestion-Indication-Item ::= SEQUENCE { +    childNodeIdentifier            BAPAddress, +    bHRLCCHList                  BHRLCCHList    OPTIONAL, +    iE-Extensions                ProtocolExtensionContainer { { IAB-Congestion-Indication-ItemExtIEs } } OPTIONAL +} + +IAB-Congestion-Indication-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +``` +IAB-Info-IAB-donor-CU ::= SEQUENCE{ + iAB-STC-Info IAB-STC-Info OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { IAB-Info-IAB-donor-CU-ExtIEs } } OPTIONAL +} + +IAB-Info-IAB-donor-CU-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +IAB-Info-IAB-DU ::= SEQUENCE{ + multiplexingInfo MultiplexingInfo OPTIONAL, + iAB-STC-Info IAB-STC-Info OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { IAB-Info-IAB-DU-ExtIEs } } OPTIONAL +} + +IAB-Info-IAB-DU-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +IAB-MT-Cell-List ::= SEQUENCE (SIZE(1..maxnooServingCells)) OF IAB-MT-Cell-List-Item + +IAB-MT-Cell-List-Item ::= SEQUENCE { +``` + +``` + +nRCellIdentity NRCellIdentity, +dU-RX-MT-RX DU-RX-MT-RX, +dU-TX-MT-TX DU-TX-MT-TX, +dU-RX-MT-TX DU-RX-MT-TX, +dU-TX-MT-RX DU-TX-MT-RX, +iE-Extensions ProtocolExtensionContainer { { IAB-MT-Cell-List-Item-ExtIEs } } OPTIONAL +} + +IAB-MT-Cell-List-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-DU-RX-MT-RX-Extend CRITICALITY ignore EXTENSION DU-RX-MT-RX-Extend PRESENCE optional } | + { ID id-DU-TX-MT-TX-Extend CRITICALITY ignore EXTENSION DU-TX-MT-TX-Extend PRESENCE optional } | + { ID id-DU-RX-MT-TX-Extend CRITICALITY ignore EXTENSION DU-RX-MT-TX-Extend PRESENCE optional } | + { ID id-DU-TX-MT-RX-Extend CRITICALITY ignore EXTENSION DU-TX-MT-RX-Extend PRESENCE optional }, + ... +} + +IAB-MT-Cell-NA-Resource-Configuration-Mode-Info ::= CHOICE { + fDD IAB-MT-Cell-NA-Resource-Configuration-FDD-Info, + tDD IAB-MT-Cell-NA-Resource-Configuration-TDD-Info, + choice-extension ProtocolIE-SingleContainer { { IAB-MT-Cell-NA-Resource-Configuration-Mode-Info-ExtIEs } } +} + +``` + +``` +IAB-MT-Cell-NA-Resource-Configuration-Mode-Info-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +IAB-MT-Cell-NA-Resource-Configuration-FDD-Info ::= SEQUENCE { + gNB-DU-Cell-NA-Resource-Configuration-FDD-UL GNB-DU-Cell-Resource-Configuration, + gNB-DU-Cell-NA-Resource-Configuration-FDD-DL GNB-DU-Cell-Resource-Configuration, + uL-FreqInfo NRFreqInfo OPTIONAL, + uL-Transmission-Bandwidth Transmission-Bandwidth OPTIONAL, + uL-NR-Carrier-List NRCarrierList OPTIONAL, + dL-FreqInfo NRFreqInfo OPTIONAL, + dL-Transmission-Bandwidth Transmission-Bandwidth OPTIONAL, + dL-NR-Carrier-List NRCarrierList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {IAB-MT-Cell-NA-Resource-Configuration-FDD-Info-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +IAB-MT-Cell-NA-Resource-Configuration-FDD-Info-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +IAB-MT-Cell-NA-Resource-Configuration-TDD-Info ::= SEQUENCE { + gNB-DU-Cell-NA-Resourc-Configuration-TDD GNB-DU-Cell-Resource-Configuration, + nRFreqInfo NRFreqInfo OPTIONAL, +``` + +``` + transmission-Bandwidth Transmission-Bandwidth OPTIONAL, + nR-Carrier-List NRCarrierList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { IAB-MT-Cell-NA-Resource-Configuration-TDD-Info-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +IAB-MT-Cell-NA-Resource-Configuration-TDD-Info-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +IAB-STC-Info ::= SEQUENCE{ + iAB-STC-Info-List IAB-STC-Info-List, + iE-Extensions ProtocolExtensionContainer { { IAB-STC-Info-ExtIEs } } OPTIONAL +} +``` + +``` +IAB-STC-Info-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +IAB-STC-Info-List ::= SEQUENCE (SIZE(1..maxnoofIABSTCInfo)) OF IAB-STC-Info-Item +``` + +``` +IAB-STC-Info-Item ::= SEQUENCE { + sSB-freqInfo SSB-freqInfo, + sSB-subcarrierSpacing SSB-subcarrierSpacing, +``` + +``` + sSB-transmissionPeriodicity SSB-transmissionPeriodicity, + sSB-transmissionTimingOffset SSB-transmissionTimingOffset, + sSB-transmissionBitmap SSB-transmissionBitmap, + iE-Extensions ProtocolExtensionContainer { { IAB-STC-Info-Item-ExtIEs } } OPTIONAL +} + +IAB-STC-Info-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +IAB-Allocated-TNL-Address-Item ::= SEQUENCE { + iABTNLAddress IABTNLAddress, + iABTNLAddressUsage IABTNLAddressUsage OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { IAB-Allocated-TNL-Address-Item-ExtIEs } } OPTIONAL +} + +IAB-Allocated-TNL-Address-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +IAB-DU-Cell-Resource-Configuration-Mode-Info ::= CHOICE { + fDD IAB-DU-Cell-Resource-Configuration-FDD-Info, + tDD IAB-DU-Cell-Resource-Configuration-TDD-Info, + choice-extension ProtocolIE-SingleContainer { { IAB-DU-Cell-Resource-Configuration-Mode-Info-ExtIEs } } +``` + +``` + +} + +IAB-DU-Cell-Resource-Configuration-Mode-Info-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +IAB-DU-Cell-Resource-Configuration-FDD-Info ::= SEQUENCE { + gNB-DU-Cell-Resource-Configuration-FDD-UL GNB-DU-Cell-Resource-Configuration, + gNB-DU-Cell-Resource-Configuration-FDD-DL GNB-DU-Cell-Resource-Configuration, + iE-Extensions ProtocolExtensionContainer { { IAB-DU-Cell-Resource-Configuration-FDD-Info-ExtIEs } } OPTIONAL, + ... +} + +IAB-DU-Cell-Resource-Configuration-FDD-Info-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + {ID id-uL-FreqInfo CRITICALITY reject EXTENSION NRFreqInfo PRESENCE optional}| + {ID id-uL-Transmission-Bandwidth CRITICALITY reject EXTENSION Transmission-Bandwidth PRESENCE optional}| + {ID id-uL-NR-Carrier-List CRITICALITY reject EXTENSION NRCarrierList PRESENCE optional}| + {ID id-dL-FreqInfo CRITICALITY reject EXTENSION NRFreqInfo PRESENCE optional}| + {ID id-dL-Transmission-Bandwidth CRITICALITY reject EXTENSION Transmission-Bandwidth PRESENCE optional}| + {ID id-dL-NR-Carrier-List CRITICALITY reject EXTENSION NRCarrierList PRESENCE optional}, + ... +} + +IAB-DU-Cell-Resource-Configuration-TDD-Info ::= SEQUENCE { + +``` + +``` +gNB-DU-Cell-Resourc-Configuration-TDD GNB-DU-Cell-Resource-Configuration, +iE-Extensions ProtocolExtensionContainer { { IAB-DU-Cell-Resource-Configuration-TDD-Info-ExtIEs } } OPTIONAL, +... +} + +IAB-DU-Cell-Resource-Configuration-TDD-Info-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + {ID id-nRFreqInfo CRITICALITY reject EXTENSION NRFreqInfo PRESENCE optional}| + {ID id-transmission-Bandwidth CRITICALITY reject EXTENSION Transmission-Bandwidth PRESENCE optional}| + {ID id-nR-Carrier-List CRITICALITY reject EXTENSION NRCarrierList PRESENCE optional}, + ... +} + +IABIPv6RequestType ::= CHOICE { + iIPv6Address IABTNLAddressesRequested, + iIPv6Prefix IABTNLAddressesRequested, + choice-extension ProtocolIE-SingleContainer { { IABIPv6RequestType-ExtIEs } } +} + +IABIPv6RequestType-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +IABTNLAddress ::= CHOICE { + iIPv4Address BIT STRING (SIZE(32)), +``` + +``` + iIPv6Address BIT STRING (SIZE(128)), + iIPv6Prefix BIT STRING (SIZE(64)), + choice-extension ProtocolIE-SingleContainer { { IABTNLAddress-ExtIEs } } +} + +IABTNLAddress-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +IABTNLAddressesRequested ::= SEQUENCE { + tNLAddressesOrPrefixesRequestedAllTraffic INTEGER (1..256) OPTIONAL, + tNLAddressesOrPrefixesRequestedF1-C INTEGER (1..256) OPTIONAL, + tNLAddressesOrPrefixesRequestedF1-U INTEGER (1..256) OPTIONAL, + tNLAddressesOrPrefixesRequestedNoNF1 INTEGER (1..256) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { IABTNLAddressesRequested-ExtIEs } } OPTIONAL +} + +IABTNLAddressesRequested-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +IAB-TNL-Addresses-To-Remove-Item ::= SEQUENCE { + iABTNLAddress IABTNLAddress, + iE-Extensions ProtocolExtensionContainer { { IAB-TNL-Addresses-To-Remove-Item-ExtIEs } } OPTIONAL +} +``` + +} + +IAB-TNL-Addresses-To-Remove-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +IAB-TNL-Addresses-Exception ::= SEQUENCE { + +iABTNLAddressList IABTNLAddressList, + +iE-Extensions ProtocolExtensionContainer { { IAB-TNL-Addresses-Exception-ExtIEs } } OPTIONAL + +} + +IAB-TNL-Addresses-Exception-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +IABTNLAddressList ::= SEQUENCE (SIZE(1.. maxnoofTLAsIAB)) OF IABTNLAddress-Item + +IABTNLAddress-Item ::= SEQUENCE { + +iABTNLAddress IABTNLAddress , + +iE-Extensions ProtocolExtensionContainer { { IABTNLAddress-ItemExtIEs } } OPTIONAL + +} + +IABTNLAddress-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +``` +} + +IABTNLAddressUsage ::= ENUMERATED { + fl-c, + fl-u, + non-fl, + ... +} + +IABv4AddressesRequested ::= SEQUENCE { + iABv4AddressesRequested IABTNLAddressesRequested, + iE-Extensions ProtocolExtensionContainer { { IABv4AddressesRequested-ExtIEs} } OPTIONAL +} + +IABv4AddressesRequested-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +Mobile-IAB-MTUserLocationInformation ::= SEQUENCE { + nRCGI NRCGI, + tAI TAI OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Mobile-IAB-MTUserLocationInformation-ExtIEs} } OPTIONAL +} +``` + +``` +Mobile-IAB-MTUserLocationInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +ImplicitFormat ::= SEQUENCE { + dUFSlotformatIndex DUFSlotformatIndex, + iE-Extensions ProtocolExtensionContainer { { ImplicitFormat-ExtIEs } } OPTIONAL +} + +ImplicitFormat-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +IgnorePRACHConfiguration ::= ENUMERATED { true,... } + +IgnoreResourceCoordinationContainer ::= ENUMERATED { yes,... } + +InactivityMonitoringRequest ::= ENUMERATED { true,... } + +InactivityMonitoringResponse ::= ENUMERATED { not-supported,... } + +IndirectPathAddition ::= SEQUENCE { + targetRelayUEID BIT STRING(SIZE(24)), + remoteUELocalID RemoteUELocalID, +} +``` + +``` + iE-Extensions ProtocolExtensionContainer { { IndirectPathAddition-ExtIEs } } OPTIONAL, + ... +} + +IndirectPathAddition-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +InterfacesToTrace ::= BIT STRING (SIZE(8)) + +IntendedTDD-DL-ULConfig ::= SEQUENCE { + nRSCS ENUMERATED { scs15, scs30, scs60, scs120, ..., scs480, scs960 }, + nRCP ENUMERATED { normal, extended, ... }, + nRDLULTxPeriodicity ENUMERATED { ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms3, ms4, ms5, ms10, ms20, ms40, ms60, ms80, ms100, ms120, + ms140, ms160, ... }, + slot-Configuration-List Slot-Configuration-List, + iE-Extensions ProtocolExtensionContainer { { IntendedTDD-DL-ULConfig-ExtIEs } } OPTIONAL +} + +InterFrequencyConfig-NoGap ::= ENUMERATED { + true, + ... +} + +IngressNonFlterminatingTopologyIndicator ::= ENUMERATED { true, ... } +``` + +IntendedTDD-DL-ULConfig-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +IndicationMCInactiveReception ::= ENUMERATED {true, ...} + +IPHeaderInformation ::= SEQUENCE { + +destinationIABTNLAddress IABTNLAddress, + +dsInformationList DSInformationList OPTIONAL, + +iPv6FlowLabel BIT STRING (SIZE (20)) OPTIONAL, + +iE-Extensions ProtocolExtensionContainer { { IPHeaderInformation-ItemExtIEs} } OPTIONAL, + +... + +} + +IPHeaderInformation-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +IPtoLayer2TrafficMappingInfo ::= SEQUENCE { + +iPtoLayer2TrafficMappingInfoToAdd iPtoLayer2TrafficMappingInfoList OPTIONAL, + +iPtoLayer2TrafficMappingInfoToRemove MappingInformationToRemove OPTIONAL, + +iE-Extensions ProtocolExtensionContainer { { IPtoLayer2TrafficMappingInfo-ItemExtIEs} } OPTIONAL, + +... + +} + +IPtoLayer2TrafficMappingInfoList ::= SEQUENCE (SIZE(1..maxnoofMappingEntries)) OF IPtoLayer2TrafficMappingInfo-Item + +IPtoLayer2TrafficMappingInfo-Item ::= SEQUENCE { +    mappingInformationIndex    MappingInformationIndex, +    iPHeaderInformation        IPHeaderInformation, +    bHInfo                    BHInfo, iE-Extensions                ProtocolExtensionContainer { { IPtoLayer2TrafficMappingInfo-ItemExtIEs } } +OPTIONAL, +    ... +} + +IPtoLayer2TrafficMappingInfo-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +-- J + +JointorDLTCIStatesConfigurationsList ::= SEQUENCE (SIZE (1.. maxnoofJointorDLTCIStates)) OF JointorDLTCIStatesConfigurations-Item + +JointorDLTCIStatesConfigurations-Item ::= SEQUENCE { +    jointorDLTCIState          OCTET STRING, +    iE-Extensions            ProtocolExtensionContainer { { JointorDLTCIStatesConfigurations-Item-ExtIEs } } OPTIONAL +} + +JointorDLTCIStatesConfigurations-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +``` + ... +} + +ULTCIStatesConfigurationsList ::= SEQUENCE (SIZE (1.. maxnoofULTCIStates)) OF ULTCIStatesConfigurations-Item + +ULTCIStatesConfigurations-Item ::= SEQUENCE { + uLCIStatesConfigurations OCTET STRING, + iE-Extensions ProtocolExtensionContainer { { ULTCIStatesConfigurations-Item-ExtIEs} } OPTIONAL +} + +ULTCIStatesConfigurations-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- K + +-- L + +LTEA2XServicesAuthorized ::= SEQUENCE { + aerialUE AerialUE OPTIONAL, + controllerUE ControllerUE OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {LTEA2XServicesAuthorized-ExtIEs} } OPTIONAL +``` + +``` +} +``` + +``` +LTEA2XServicesAuthorized-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { +``` + +... + +``` +} +``` + +L139Info ::= SEQUENCE { + +    prachSCS                        ENUMERATED {scs15, scs30, scs60, scs120, ..., scs480, scs960}, + +    rootSequenceIndex               INTEGER (0..137)                                        OPTIONAL, + +    iE-Extension                    ProtocolExtensionContainer { {L139Info-ExtIEs} }                    OPTIONAL, + +... + +} + +``` +L139Info-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { +``` + +... + +} + +L839Info ::= SEQUENCE { + +    rootSequenceIndex               INTEGER (0..837), + +    restrictedSetConfig             ENUMERATED {unrestrictedSet, restrictedSetTypeA, +                                                restrictedSetTypeB, ...}, + +    iE-Extension                    ProtocolExtensionContainer { {L839Info-ExtIEs} }                    OPTIONAL, + +... + +} + +``` +L839Info-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +L571Info ::= SEQUENCE { + prachSCSForL571 ENUMERATED { scs30, scs120, ... , scs480}, + rootSequenceIndex INTEGER (0..569), + iE-Extension ProtocolExtensionContainer { {L571Info-ExtIEs} } OPTIONAL, + ... +} + +L571Info-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +L1151Info ::= SEQUENCE { + prachSCSForL1151 ENUMERATED { scs15, scs120,...}, + rootSequenceIndex INTEGER (0..1149), + iE-Extension ProtocolExtensionContainer { {L1151Info-ExtIEs} } OPTIONAL, + ... +} + +L1151Info-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +LastUsedCellIndication ::= ENUMERATED {true, ...} + +LCID ::= INTEGER (1..32, ...) + +LCS-to-GCS-Translation ::= SEQUENCE { + alpha INTEGER (0..3599), + beta INTEGER (0..3599), + gamma INTEGER (0..3599), + iE-Extensions ProtocolExtensionContainer { { LCS-to-GCS-Translation-ExtIEs } } OPTIONAL, + ... +} + +LCS-to-GCS-Translation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +LCStoGCSTranslationList ::= SEQUENCE (SIZE (1.. maxnooflcs-gcs-translation)) OF LCStoGCSTranslation + +LCStoGCSTranslation ::= SEQUENCE { +``` + +``` + alpha INTEGER (0..359), + alpha-fine INTEGER (0..9) OPTIONAL, + beta INTEGER (0..359), + beta-fine INTEGER (0..9) OPTIONAL, + gamma INTEGER (0..359), + gamma-fine INTEGER (0..9) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {LCStoGCSTranslation-ExtIEs} } OPTIONAL +} + +LCStoGCSTranslation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +LMF-MeasurementID ::= INTEGER (1.. 65536, ...) + +LMF-UE-MeasurementID ::= INTEGER (1.. 256, ...) + +LocationDependentMBSF1UIInformation ::= SEQUENCE (SIZE(1..maxnoofMBSAreaSessionIDs)) OF LocationDependentMBSF1UIInformation-Item +LocationDependentMBSF1UIInformation-Item ::= SEQUENCE { + mbsAreaSession-ID MBS-Area-Session-ID, + mbs-flu-info-at-CU UPTransportLayerInformation, + iE-Extensions ProtocolExtensionContainer { { LocationDependentMBSF1UIInformation-Item-ExtIEs } } OPTIONAL, + ... +} +``` + +LocationDependentMBSF1UInformation-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +LocationMeasurementInformation ::= OCTET STRING + +LocationUncertainty ::= SEQUENCE { + +horizontalUncertainty INTEGER (0..255), + +horizontalConfidence INTEGER (0..100), + +verticalUncertainty INTEGER (0..255), + +verticalConfidence INTEGER (0..100), + +iE-Extensions ProtocolExtensionContainer { { LocationUncertainty-ExtIEs } } OPTIONAL + +} + +LocationUncertainty-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +LongDRXCycleLength ::= ENUMERATED + +{ms10, ms20, ms32, ms40, ms60, ms64, ms70, ms80, ms128, ms160, ms256, ms320, ms512, ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240, ...} + +LowerLayerPresenceStatusChange ::= ENUMERATED { + +suspend-lower-layers, + +``` + resume-lower-layers, + ... +} + +LoS-NLoSIndicatorHard ::= ENUMERATED {nLoS, loS} + +LoS-NLoSIndicatorSoft ::= INTEGER (0..10) + +LoS-NLoSInformation ::= CHOICE { + loS-NLoSIndicatorSoft LoS-NLoSIndicatorSoft, + loS-NLoSIndicatorHard LoS-NLoSIndicatorHard, + choice-Extension ProtocolIE-SingleContainer {{ LoS-NLoSInformation-ExtIEs}} +} + +LoS-NLoSInformation-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +LTEUESidelinkAggregateMaximumBitrate ::= SEQUENCE { + uELTSidelinkAggregateMaximumBitrate BitRate, + iE-Extensions ProtocolExtensionContainer { {LTEUESidelinkAggregateMaximumBitrate-ExtIEs} } OPTIONAL +} +``` + +``` +LTEUESidelinkAggregateMaximumBitrate-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +LTEV2XServicesAuthorized ::= SEQUENCE { +``` + +``` + vehicleUE VehicleUE OPTIONAL, +``` + +``` + pedestrianUE PedestrianUE OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { {LTEV2XServicesAuthorized-ExtIEs} } OPTIONAL +``` + +``` +} +``` + +``` +LTEV2XServicesAuthorized-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +LTMCells-ToBeReleased-List ::= SEQUENCE (SIZE(1..maxnoofLTMCells)) OF ProtocolIE-SingleContainer { { LTMCells-ToBeReleased-ItemIEs} } +``` + +``` +LTMCells-ToBeReleased-ItemIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + { ID id-LTMCells-ToBeReleased-Item CRITICALITY reject TYPE LTMCells-ToBeReleased-Item PRESENCE mandatory}, +``` + +``` + ... +``` + +``` +} +``` + +``` +LTMCells-ToBeReleased-Item ::= SEQUENCE { +``` + +``` + +nRCGI NRCGI, + +iE-Extensions ProtocolExtensionContainer { { LTMCells-ToBeReleased-ItemExtIEs } } OPTIONAL, + +... + +} + +LTMCells-ToBeReleased-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +LTInformation-Setup ::= SEQUENCE { + + LTMIndicator LTMIndicator, + + LTMConfigurationID LTMConfigurationID, referenceConfiguration ReferenceConfiguration + OPTIONAL, + + CSIResourceConfiguration CSIResourceConfiguration OPTIONAL, + + iE-Extensions ProtocolExtensionContainer { { LTInformation-Setup-ExtIEs} } OPTIONAL, + + ... + +} + +LTInformation-Setup-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + + ... + +} + +LTMConfigurationIDMappingList ::= SEQUENCE (SIZE(1..maxnoofLTMCells)) OF LTMConfigurationIDMapping-Item + +LTMConfigurationIDMapping-Item ::= SEQUENCE{ + +``` + +``` + lTMCellID NRCGI, + lTMConfigurationID lTMConfigurationID OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { lTMConfigurationIDMapping-Item-ExtIEs} } OPTIONAL +} + +lTMConfigurationIDMapping-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +lTMInformation-Modify ::= SEQUENCE { + lTMIndicator lTMIndicator, + lTMConfigurationID lTMConfigurationID, referenceConfiguration ReferenceConfiguration + OPTIONAL, + cSIResourceConfiguration cSIResourceConfiguration OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { lTMInformation-Modify-ExtIEs} } OPTIONAL, + ... +} + +lTMInformation-Modify-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +lTMIndicator ::= ENUMERATED {true, ...} +``` + +LTMCompleteConfigurationIndicator ::= ENUMERATED {true, ...} + +LTMConfigurationID ::= INTEGER (1..8) + +LTMReferenceConfiguration ::= OCTET STRING + +LTMConfiguration ::= SEQUENCE { +    sSBInformationItem                            SSBInformationItem, +    LTMReferenceConfiguration                    LTMReferenceConfiguration            OPTIONAL, +    LTMCompleteConfigurationIndicator          LTMCompleteConfigurationIndicator  OPTIONAL, +    iE-Extensions                ProtocolExtensionContainer { { LTMConfiguration-ExtIEs } } OPTIONAL, +    ... +} + +LTMConfiguration-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +LTMCellSwitchInformation ::= SEQUENCE { +    tCIStateID                TCIStateID, +    iE-Extensions            ProtocolExtensionContainer { { LTMCellSwitchInformation-ExtIEs } } OPTIONAL, +    ... +} + +LTMCellSwitchInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +``` + ... +} + +-- M + +MappingInformationIndex ::= BIT STRING (SIZE (26)) + +MappingInformationToRemove ::= SEQUENCE (SIZE(1..maxnoofMappingEntries)) OF MappingInformationIndex + +MaskedIMEISV ::= BIT STRING (SIZE (64)) + +MaxDataBurstVolume ::= INTEGER (0..4095, ..., 4096.. 2000000) +MaxPacketLossRate ::= INTEGER (0..1000) + +MBS-Broadcast-NeighbourCellList ::= OCTET STRING + +MBS-Flows-Mapped-To-MRB-List ::= SEQUENCE (SIZE(1.. maxnoofMBSQoSFlows)) OF MBS-Flows-Mapped-To-MRB-Item + +MBS-Flows-Mapped-To-MRB-Item ::= SEQUENCE { + mBS-QoSFlowIdentifier QoSFlowIdentifier, + mbs-QoSFlowLevelQoSParameters QoSFlowLevelQoSParameters, + iE-Extensions ProtocolExtensionContainer { { MBS-Flows-Mapped-To-MRB-Item-ExtIEs} } OPTIONAL +} +``` + +``` +MBS-Flows-Mapped-To-MRB-Item-ExtIEs FIAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBSF1UInformation ::= SEQUENCE { + mbs-flu-info UPTransportLayerInformation, + iE-Extensions ProtocolExtensionContainer { { MBSF1UInformation-ExtIEs } } OPTIONAL, + ... +} + +MBSF1UInformation-ExtIEs FIAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBSInterestIndication ::= OCTET STRING + +MBS-Session-ID ::= SEQUENCE { + tMGI TMGI, + nID NID OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MBS-Session-ID-ExtIEs } } OPTIONAL, + ... +} +``` + +MBS-Session-ID-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +MBS-Area-Session-ID ::= INTEGER (0..65535, ...) + +MBS-CUtoDURRInformation ::= SEQUENCE { + +mBS-Broadcast-Cell-List MBS-Broadcast-Cell-List, + +mBS-Broadcast-MRB-List MBS-Broadcast-MRB-List, + +iE-Extensions ProtocolExtensionContainer { { MBS-CUtoDURRInformation-ExtIEs } } OPTIONAL, + +... + +} + +MBS-CUtoDURRInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +MBS-Broadcast-Cell-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF MBS-Broadcast-Cell-Item + +MBS-Broadcast-Cell-Item ::= SEQUENCE { + +nRCGI NRCGI, + +mtch-neighbourCell OCTET STRING OPTIONAL, + +iE-Extensions ProtocolExtensionContainer { { MBS-Broadcast-Cell-Item-ExtIEs } } OPTIONAL, + +``` + ... +} + +MBS-Broadcast-Cell-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBS-Broadcast-MRB-List ::= SEQUENCE (SIZE(1.. maxnoofMRBs)) OF MBS-Broadcast-MRB-Item + +MBS-Broadcast-MRB-Item ::= SEQUENCE { + mRB-ID MRB-ID, + mRB-PDCP-Config-Broadcast OCTET STRING, + iE-Extensions ProtocolExtensionContainer { { MBS-Broadcast-MRB-Item-ExtIEs} } OPTIONAL, + ... +} + +MBS-Broadcast-MRB-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBSMulticastFlUContextDescriptor ::= SEQUENCE { + multicastFlUContextReferenceFl MulticastFlUContextReferenceFl, + mc-FlUCtxtusage ENUMERATED {ptm, ptp, ptp-retransmission, ptp-forwarding, ...}, + mbsAreaSession MBS-Area-Session-ID OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { {MBSMulticastFlUContextDescriptor-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +MBSMulticastFlUContextDescriptor-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +MT-SDT-Information ::= SEQUENCE { + mt-SDT-Indicator MT-SDT-Indicator, + iE-Extensions ProtocolExtensionContainer { { MT-SDT-Information-ExtIEs } } OPTIONAL +} +``` + +``` +MT-SDT-Information-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +MT-SDT-Indicator ::= ENUMERATED {true, ...} +``` + +``` +MBSMulticastSessionReceptionState ::= ENUMERATED {start-monitoring-G-RNTI, stop-monitoring-G-RNTI, ...} +``` + +``` +MulticastCU2DURRCInfo ::= SEQUENCE { + mBS-Multicast-CU2DU-Cell-List MBS-Multicast-CU2DU-Cell-List OPTIONAL, + mBS-Multicast-MRB-List MBS-Multicast-MRB-List OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { MulticastCU2DURRCInfo-ExtIEs } } OPTIONAL, + ... +} + +MulticastCU2DURRCInfo-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBS-Multicast-CU2DU-Cell-List ::= SEQUENCE (SIZE(1.. maxCellingNBDDU)) OF MBS-Multicast-CU2DU-Cell-Item + +MBS-Multicast-CU2DU-Cell-Item ::= SEQUENCE { + nRCGI NRCGI, + multicast-mtch-neighbourCell OCTET STRING OPTIONAL, + thresholdIndex ThresholdIndex OPTIONAL, + mbsMulticastRRc-INACTIVEReceptionMode MBSMulticastRRcINACTIVEReceptionMode OPTIONAL, + mbsMulticastConfigurationRequest ENUMERATED {query, ...} OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MBS-Multicast-CU2DU-Cell-Item-ExtIEs } } OPTIONAL, + ... +} + +MBS-Multicast-CU2DU-Cell-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +MBSMulticastRRcInactiveReceptionMode ::= ENUMERATED {activated, deactivated, ...} + +MBS-Multicast-MRB-List ::= SEQUENCE (SIZE(1.. maxnoofMRBs)) OF MBS-Multicast-MRB-Item + +MBS-Multicast-MRB-Item ::= SEQUENCE { +    mRB-ID                    MRB-ID, +    mRB-PDCP-Config-Broadcast  OCTET STRING, +    iE-Extensions          ProtocolExtensionContainer { { MBS-Multicast-MRB-Item-ExtIEs} } OPTIONAL, +    ... +} + +MBS-Multicast-MRB-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +MulticastCU2DUCCommonRRcInfo ::= SEQUENCE { +    multicastCommonCU2DUCellList    MulticastCommonCU2DUCellList    OPTIONAL, +    iE-Extensions                  ProtocolExtensionContainer { {MulticastCU2DUCCommonRRcInfo-ExtIEs} } OPTIONAL, +    ... +} + +MulticastCU2DUCCommonRRcInfo-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +``` +MulticastCommonCU2DUCellList ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF MulticastCommonCU2DUCell-Item +``` + +``` +MulticastCommonCU2DUCell-Item ::= SEQUENCE { +``` + +``` + nRCGI NRCGI, +``` + +``` + multicastCommonCu2DUCellInformation MulticastCommonCu2DUCellInformation, +``` + +``` + iE-Extensions ProtocolExtensionContainer { {MulticastCommonCU2DUCell-Item-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +MulticastCommonCU2DUCell-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +MulticastCommonCu2DUCellInformation ::= SEQUENCE { +``` + +``` + mBSMulticastNeighbourCellListItem MBSMulticastNeighbourCellListItem OPTIONAL, +``` + +``` + thresholdMBS-ListItem ThresholdMBS-ListItem OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { {MulticastCommonCu2DUCellInformation-ExtIEs} } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +MulticastCommonCu2DUCellInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +MBSMulticastNeighbourCellListItem ::= CHOICE { + mbsMulticastNeighbourCellListInformationprovided UpdateMBSMulticastNeighbourCellListInformation, + nombsMulticastNeighbourCellListInformationprovided NULL, + choice-extension ProtocolIE-SingleContainer { {MBSMulticastNeighbourCellListItem-ExtIEs} } +} + +MBSMulticastNeighbourCellListItem-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +ThresholdMBS-ListItem ::= CHOICE { + thresholdMBS-ListInformationprovided UpdateThresholdMBS-ListInformation, + nothresholdMBSListInformationprovided NULL, + choice-extension ProtocolIE-SingleContainer { {ThresholdMBS-ListItem-ExtIEs} } +} + +ThresholdMBS-ListItem-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +UpdateMBSMulticastNeighbourCellListInformation ::= SEQUENCE { + mbs-NeighbourCellList OCTET STRING OPTIONAL, + mbs-MulticastSessionList MTCH-NeighbourCellSessionList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {UpdateMBSMulticastNeighbourCellListInformation-ExtIEs} } OPTIONAL, +``` + +``` + ... +} + +UpdateMBSMulticastNeighbourCellListInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +MTCH-NeighbourCellSessionList ::= SEQUENCE (SIZE(1..maxMBSSessionsinSessionInfoList)) OF MTCH-NeighbourCellSession-Item + +MTCH-NeighbourCellSession-Item ::= SEQUENCE { + mbsSessionID MBS-Session-ID, + mtch-NeighbourCellInformation CHOICE { + mtch-NeighbourCellprovided OCTET STRING, + mtch-NeighbourCellnotprovided NULL + }, + iE-Extensions ProtocolExtensionContainer { {MTCH-NeighbourCellSession-Item-ExtIEs} } OPTIONAL, + ... +} + +MTCH-NeighbourCellSession-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +UpdateThresholdMBS-ListInformation ::= SEQUENCE { +``` + +``` +thresholdMBSList OCTET STRING OPTIONAL, +thresholdIndexSessionList ThresholdIndexSessionList OPTIONAL, +iE-Extensions ProtocolExtensionContainer { {UpdateThresholdMBS-ListInformation-ExtIEs} } OPTIONAL, +... +} +``` + +``` +UpdateThresholdMBS-ListInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +... +} +``` + +``` +ThresholdIndexSessionList ::= SEQUENCE (SIZE(1..maxMBSSessionsinSessionInfoList)) OF ThresholdIndexSession-Item +``` + +``` +ThresholdIndexSession-Item ::= SEQUENCE { + mbsSessionID MBS-Session-ID, + thresholdIndexInformation CHOICE { + thresholdIndexprovided ThresholdIndex, + thresholdIndexnotprovided NULL + }, + iE-Extensions ProtocolExtensionContainer { {ThresholdIndexSession-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +ThresholdIndexSession-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +... +} +``` + +ThresholdIndex ::= INTEGER (0..maxnoofThresholdMBS) + +MulticastDU2CURRCInfo ::= SEQUENCE { +    mBS-Multicast-DU2CU-Cell-List          MBS-Multicast-DU2CU-Cell-List          OPTIONAL, +    iE-Extensions                          ProtocolExtensionContainer { { MulticastDU2CURRCInfo-ExtIEs } } OPTIONAL, +    ... +} + +MulticastDU2CURRCInfo-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +MBS-Multicast-DU2CU-Cell-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF MBS-Multicast-DU2CU-Cell-Item + +MBS-Multicast-DU2CU-Cell-Item ::= SEQUENCE { +    nRCGI                                  NRCGI, +    mbsMulticastConfigurationResponseInfo  MBSMulticastConfigurationResponseInfo          OPTIONAL, +    mbsMulticastConfigurationNotification  MBSMulticastConfigurationNotification                          OPTIONAL, +    iE-Extensions                          ProtocolExtensionContainer { { MBS-Multicast-DU2CU-Cell-Item-ExtIEs } } OPTIONAL, +    ... +} + +MBS-Multicast-DU2CU-Cell-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +``` +... +} + +MBSMulticastConfigurationResponseInfo ::= CHOICE { + mbsMulticastConfiguration-available OCTET STRING, + mbsMulticastConfiguration-notavailable ENUMERATED {not-available, ...}, + choice-extension ProtocolIE-SingleContainer { {MBSMulticastConfigurationResponseInfo-ExtIEs} } +} + +MBSMulticastConfigurationResponseInfo-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +MBSMulticastConfigurationNotification ::= SEQUENCE { + mbsMulticastConfigurationNotificationInfo MBSMulticastConfigurationNotificationInfo OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {MBSMulticastConfigurationNotification-ExtIEs} } OPTIONAL, + ... +} + +MBSMulticastConfigurationNotification-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +MBSMulticastConfigurationNotificationInfo ::= CHOICE { + mbsMulticastConfigurationChanged OCTET STRING, + mbsMulticastConfigurationRemoved NULL, + choice-extension ProtocolIE-SingleContainer { {MBSMulticastConfigurationNotificationInfo-ExtIEs} } +} + +MBSMulticastConfigurationNotificationInfo-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +MulticastFlUContext-ToBeSetup-Item ::= SEQUENCE { + mRB-ID MRB-ID, + mbs-flu-info-at-DU UPTransportLayerInformation, + mbsProgressInformation MRB-ProgressInformation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {MulticastFlUContext-ToBeSetup-Item-ExtIEs} } OPTIONAL, + ... +} + +MulticastFlUContext-ToBeSetup-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +MulticastFlUContext-Setup-Item ::= SEQUENCE { +``` + +``` +mRB-ID MRB-ID, +mbs-flu-info-at-CU UPTransportLayerInformation, +iE-Extensions ProtocolExtensionContainer { {MulticastFlUContext-Setup-Item-ExtIEs} } OPTIONAL, +... +} + +MulticastFlUContext-Setup-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +MulticastFlUContext-FailedToBeSetup-Item ::= SEQUENCE { + mRB-ID MRB-ID, + cause Cause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {MulticastFlUContext-FailedToBeSetup-Item-ExtIEs} } OPTIONAL, + ... +} + +MulticastFlUContext-FailedToBeSetup-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +MBSPTRetransmissionTunnelRequired ::= ENUMERATED {true, ...} +``` + +``` +MBS-ServiceArea ::= CHOICE { + locationindependent MBS-ServiceAreaInformation, + locationdependent MBS-ServiceAreaInformationList, + choice-Extensions ProtocolIE-SingleContainer { {MBSServiceArea-ExtIEs} } +} +``` + +``` +MBSServiceArea-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +MBS-ServiceAreaInformation ::= SEQUENCE { + mBS-ServiceAreaCellList MBS-ServiceAreaCellList OPTIONAL, + mBS-ServiceAreaTAIList MBS-ServiceAreaTAIList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {MBS-ServiceAreaInformation-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +MBS-ServiceAreaInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +MBS-ServiceAreaCellList ::= SEQUENCE (SIZE(1.. maxnoofCellsforMBS)) OF NRCGI + +MBS-ServiceAreaTAIList ::= SEQUENCE (SIZE(1.. maxnoofTAIforMBS)) OF MBS-ServiceAreaTAIList-Item + +MBS-ServiceAreaTAIList-Item ::= SEQUENCE { + plmn-ID PLMN-Identity, + five5-TAC FiveGS-TAC, + iE-Extensions ProtocolExtensionContainer { {MBS-ServiceAreaTAIList-Item-ExtIEs} } OPTIONAL, + ... +} + +MBS-ServiceAreaTAIList-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBS-ServiceAreaInformationList ::= SEQUENCE (SIZE(1..maxnoofMBSServiceAreaInformation)) OF MBS-ServiceAreaInformationItem + +MBS-ServiceAreaInformationItem ::= SEQUENCE { + mBS-AreaSessionID MBS-Area-Session-ID, + mBS-ServiceAreaInformation MBS-ServiceAreaInformation, + iE-Extensions ProtocolExtensionContainer { { MBS-ServiceAreaInformationItem-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +MBS-ServiceAreaInformationItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +MC-PagingCell-Item ::= SEQUENCE { + nRCGI NRCGI, + iE-Extensions ProtocolExtensionContainer { { MC-PagingCell-ItemExtIEs } } OPTIONAL +} + +MC-PagingCell-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +MIB-message ::= OCTET STRING + +MeasConfig ::= OCTET STRING + +MeasGapConfig ::= OCTET STRING + +MeasGapSharingConfig ::= OCTET STRING + +PosMeasurementAmount ::= ENUMERATED {ma0, ma1, ma2, ma4, ma8, ma16, ma32, ma64} +``` + +MeasurementBeamInfoRequest ::= ENUMERATED {true, ...} + +MeasurementBeamInfo ::= SEQUENCE { +    pRS-Resource-ID              PRS-Resource-ID    OPTIONAL, +    pRS-Resource-Set-ID        PRS-Resource-Set-ID OPTIONAL, +    SSB-Index                  SSB-Index          OPTIONAL, +    iE-Extensions              ProtocolExtensionContainer { { MeasurementBeamInfo-ExtIEs} } OPTIONAL +} + +MeasurementBeamInfo-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +MeasurementTimingConfiguration ::= OCTET STRING + +MessageIdentifier ::= BIT STRING (SIZE (16)) + +MeasurementTimeOccasion ::= ENUMERATED {o1, o4, ...} + +MeasurementCharacteristicsRequestIndicator ::= BIT STRING (SIZE (16)) + +MRB-ProgressInformation ::= CHOICE { + +``` + pdcp-SN12 INTEGER (0..4095), + pdcp-SN18 INTEGER (0..262143), + choice-extension ProtocolIE-SingleContainer { { MRB-ProgressInformation-ExtIEs} } +} + +MRB-ProgressInformation-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +MulticastFlUContextReferenceFl ::= OCTET STRING (SIZE(4)) + +MulticastFlUContextReferenceCU ::= OCTET STRING (SIZE(4)) + +MultipleULAoA ::= SEQUENCE { + multipleULAoA MultipleULAoA-List, + iE-Extensions ProtocolExtensionContainer { { MultipleULAoA-ExtIEs} } OPTIONAL, + ... +} + +MultipleULAoA-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +MultipleULAoA-List ::= SEQUENCE (SIZE(1.. maxnoofULAoAs)) OF MultipleULAoA-Item +``` + +``` +MultipleULAoA-Item ::= CHOICE { + uL-AoA UL-AoA, + ul-ZoA ZoAInformation, + choice-extension ProtocolIE-SingleContainer { { MultipleULAoA-Item-ExtIEs } } +} + +MultipleULAoA-Item-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +MDTPollutedMeasurementIndicator ::= ENUMERATED {iDC,no-IDC, ...} + +MRB-ID ::= INTEGER (1..512, ...) + +MulticastMBSSessionList ::= SEQUENCE (SIZE(1..maxnoofMBSSessionsofUE)) OF MulticastMBSSessionList-Item + +MulticastMBSSessionList-Item ::= SEQUENCE { + mbsSessionId MBS-Session-ID, + iE-Extensions ProtocolExtensionContainer { { MulticastMBSSessionList-Item-ExtIEs } } OPTIONAL, + ... +} + +MulticastMBSSessionList-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +} + +MulticastMRBs-FailedToBeModified-Item ::= SEQUENCE { + mRB-ID MRB-ID, + cause Cause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MulticastMRBs-FailedtoBeModified-Item-ExtIEs} } OPTIONAL, + ... +} + +MulticastMRBs-FailedtoBeModified-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +MulticastMRBs-FailedToBeSetup-Item ::= SEQUENCE { + mRB-ID MRB-ID, + cause Cause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MulticastMRBs-FailedToBeSetup-Item-ExtIEs} } OPTIONAL, + ... +} + +MulticastMRBs-FailedToBeSetup-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +MulticastMRBs-FailedToBeSetupMod-Item ::= SEQUENCE { + mRB-ID MRB-ID, + cause Cause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MulticastMRBs-FailedToBeSetupMod-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +MulticastMRBs-FailedToBeSetupMod-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +MulticastMRBs-Modified-Item ::= SEQUENCE { + mRB-ID MRB-ID, + iE-Extensions ProtocolExtensionContainer { { MulticastMRBs-Modified-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +MulticastMRBs-Modified-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +MulticastMRBs-Setup-Item ::= SEQUENCE { + mRB-ID MRB-ID, + iE-Extensions ProtocolExtensionContainer { { MulticastMRBs-Setup-Item-ExtIEs} } OPTIONAL, +``` + +``` + ... +} + +MulticastMRBs-Setup-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +MulticastMRBs-SetupMod-Item ::= SEQUENCE { + mRB-ID MRB-ID, + iE-Extensions ProtocolExtensionContainer { { MulticastMRBs-SetupMod-Item-ExtIEs} } OPTIONAL, + ... +} + +MulticastMRBs-SetupMod-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +MulticastMRBs-ToBeModified-Item ::= SEQUENCE { + mRB-ID MRB-ID, + mRB-QoSInformation QoSFlowLevelQoSParameters OPTIONAL, + mBS-Flows-Mapped-To-MRB-List MBS-Flows-Mapped-To-MRB-List OPTIONAL, + mBS-DL-PDCP-SN-Length PDCPSNLength OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { MulticastMRBs-ToBeModified-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +} + +MulticastMRBs-ToBeModified-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +MulticastMRBs-ToBeReleased-Item ::= SEQUENCE { + mRB-ID MRB-ID, + iE-Extensions ProtocolExtensionContainer { { MulticastMRBs-ToBeReleased-ItemExtIEs } } OPTIONAL, + ... +} + +MulticastMRBs-ToBeReleased-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +MulticastMRBs-ToBeSetup-Item ::= SEQUENCE { + mRB-ID MRB-ID, + mRB-QoSInformation QoSFlowLevelQoSParameters, + mBS-Flows-Mapped-To-MRB-List MBS-Flows-Mapped-To-MRB-List, + mBS-DL-PDCP-SN-Length PDCPSNLength, + iE-Extensions ProtocolExtensionContainer { { MulticastMRBs-ToBeSetup-Item-ExtIEs } }, + ... +} +``` + +``` +MulticastMRBs-ToBeSetup-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +MulticastMRBs-ToBeSetupMod-Item ::= SEQUENCE { +``` + +``` + mRB-ID MRB-ID, +``` + +``` + mRB-QoSInformation QoSFlowLevelQoSParameters, +``` + +``` + mBS-Flows-Mapped-To-MRB-List MBS-Flows-Mapped-To-MRB-List, +``` + +``` + mBS-DL-PDCP-SN-Length PDCPSNLength, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { MulticastMRBs-ToBeSetupMod-Item-ExtIEs } }, +``` + +``` + ... +``` + +``` +} +``` + +``` +MulticastMRBs-ToBeSetupMod-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +MultiplexingInfo ::= SEQUENCE{ +``` + +``` + iAB-MT-Cell-List IAB-MT-Cell-List, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { MultiplexingInfo-ExtIEs } } OPTIONAL +``` + +``` +} +``` + +``` +MultiplexingInfo-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +MusimCapabilityRestrictionIndication ::= ENUMERATED {true, ...} + +M2Configuration ::= ENUMERATED {true, ...} + +M5Configuration ::= SEQUENCE { + m5period M5period, + m5-links-to-log M5-Links-to-log, + iE-Extensions ProtocolExtensionContainer { { M5Configuration-ExtIEs } } OPTIONAL, + ... +} + +M5Configuration-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + {ID id-M5ReportAmount CRITICALITY ignore EXTENSION M5ReportAmount PRESENCE optional }, + ... +} + +M5period ::= ENUMERATED { ms1024, ms2048, ms5120, ms10240, min1, ... } + +M5ReportAmount ::= ENUMERATED { r1, r2, r4, r8, r16, r32, r64, infinity, ... } +``` + +M5-Links-to-log ::= ENUMERATED {uplink, downlink, both-uplink-and-downlink, ...} + +M6Configuration ::= SEQUENCE { +    m6report-Interval M6report-Interval, +    m6-links-to-log M6-Links-to-log, +    iE-Extensions ProtocolExtensionContainer { { M6Configuration-ExtIEs } } OPTIONAL, +    ... +} + +M6Configuration-ExtIEs FIAP-PROTOCOL-EXTENSION ::= { +    {ID id-M6ReportAmount CRITICALITY ignore EXTENSION M6ReportAmount PRESENCE optional }, +    ... +} + +M6report-Interval ::= ENUMERATED { ms120, ms240, ms640, ms1024, ms2048, ms5120, ms10240, ms20480, ms40960, min1, min6, min12, min30, ..., ms480 } + +M6ReportAmount ::= ENUMERATED { r1, r2, r4, r8, r16, r32, r64, infinity, ... } + +M6-Links-to-log ::= ENUMERATED {uplink, downlink, both-uplink-and-downlink, ...} + +M7Configuration ::= SEQUENCE { + +``` + m7period M7period, + m7-links-to-log M7-Links-to-log, + iE-Extensions ProtocolExtensionContainer { { M7Configuration-ExtIEs } } OPTIONAL, + ... +} + +M7Configuration-ExtIEs FLAP-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, ... } + +M7-Links-to-log ::= ENUMERATED {downlink, ...} + +MDT-Activation ::= ENUMERATED { + immediate-MDT-only, + immediate-MDT-and-Trace, + ... +} + +MDTConfiguration ::= SEQUENCE { +``` + +``` + mdt-Activation MDT-Activation, + measurementsToActivate MeasurementsToActivate, + m2Configuration M2Configuration OPTIONAL, + -- C-ifM2: This IE shall be present if the Measurements to Activate IE has the second bit set to "1". + m5Configuration M5Configuration OPTIONAL, + -- C-ifM5: This IE shall be present if the Measurements to Activate IE has the fifth bit set to "1". + m6Configuration M6Configuration OPTIONAL, + -- C-ifM6: This IE shall be present if the Measurements to Activate IE has the seventh bit set to "1". + m7Configuration M7Configuration OPTIONAL, + -- C-ifM7: This IE shall be present if the Measurements to Activate IE has the eighth bit set to "1". + iE-Extensions ProtocolExtensionContainer { { MDTConfiguration-ExtIEs} } OPTIONAL, + ... +} + +MDTConfiguration-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + + +MDTPLMNList ::= SEQUENCE (SIZE(1..maxnoofMDTPLMNs)) OF PLMN-Identity + +MDTPLMNModificationList ::= SEQUENCE (SIZE(0..maxnoofMDTPLMNs)) OF PLMN-Identity + + +MeasuredResultsValue ::= CHOICE { + uL-AngleOfArrival UL-AoA, +``` + +``` + uL-SRS-RSRP UL-SRS-RSRP, + uL-RTOA UL-RTOA-Measurement, + gNB-RxTxTimeDiff GNB-RxTxTimeDiff, + choice-extension ProtocolIE-SingleContainer { { MeasuredResultsValue-ExtIEs } } +} + +MeasuredResultsValue-ExtIEs FLAP-PROTOCOL-IES ::= { + { ID id-ZoAInformation CRITICALITY reject TYPE ZoAInformation PRESENCE mandatory}| + { ID id-MultipleULAoA CRITICALITY reject TYPE MultipleULAoA PRESENCE mandatory}| + { ID id-UL-SRS-RSRPP CRITICALITY reject TYPE UL-SRS-RSRPP PRESENCE mandatory}, + ... +} + +MeasurementsToActivate ::= BIT STRING (SIZE (8)) + +Mobile-TRP-LocationInformation ::= SEQUENCE { + location-Information OCTET STRING OPTIONAL, + velocity-Information OCTET STRING OPTIONAL, + location-time-stamp Timestamp OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Mobile-TRP-LocationInformation-ExtIEs} } OPTIONAL, + ... +} + +Mobile-TRP-LocationInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +Mobile-IAB-MT-UE-ID ::= OCTET STRING + +MUSIM-GapConfig ::= OCTET STRING + +-- N + +NRA2XServicesAuthorized ::= SEQUENCE { + aerialUE AerialUE OPTIONAL, + controllerUE ControllerUE OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {NRA2XServicesAuthorized-ExtIEs} } OPTIONAL +} + +NRA2XServicesAuthorized-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +AerialUE ::= ENUMERATED { + authorized, + not-authorized, +``` + +``` + ... +} + +ControllerUE ::= ENUMERATED { + authorized, + not-authorized, + ... +} + +N3CIndirectPathAddition ::= SEQUENCE { + targetRelayUEID GNB-DU-UE-FLAP-ID, + iE-Extensions ProtocolExtensionContainer { { N3CIndirectPathAddition-ExtIEs } } OPTIONAL, + ... +} + +N3CIndirectPathAddition-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +NA-Resource-Configuration-List ::= SEQUENCE (SIZE(1.. maxnoofHSNASlots)) OF NA-Resource-Configuration-Item + +NA-Resource-Configuration-Item ::= SEQUENCE { + nADownlink NADownlink OPTIONAL, +``` + +``` + nAUplink NAUplink OPTIONAL, + nAFlexible NAFlexible OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { NA-Resource-Configuration-Item-ExtIEs} } OPTIONAL +} + +NA-Resource-Configuration-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +NADownlink ::= ENUMERATED { true, false, ...} +NAFlexible ::= ENUMERATED { true, false, ...} +NAUplink ::= ENUMERATED { true, false, ...} + +Ncd-SSB-RedCapInitialBWP-SDT ::= OCTET STRING + +NetworkControlledRepeaterAuthorized ::= ENUMERATED { authorized, not-authorized, ...} + +NCGI-to-be-Updated-List-Item ::= SEQUENCE { + oLDNCGI NRCGI, + nEWNCGI NRCGI, + iE-Extensions ProtocolExtensionContainer { { NCGI-to-be-Updated-List-ItemExtIEs} } OPTIONAL, + ... +} +``` + +``` + +NCGI-to-be-Updated-List-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +Neighbour-Node-Cells-List ::= SEQUENCE (SIZE(1..maxnoofNeighbourNodeCellsIAB)) OF Neighbour-Node-Cells-List-Item + +``` + +``` + +Neighbour-Node-Cells-List-Item ::= SEQUENCE{ + nRCGI NRCGI, + gNB-CU-UE-FlAP-ID GNB-CU-UE-FlAP-ID OPTIONAL, + gNB-DU-UE-FlAP-ID GNB-DU-UE-FlAP-ID OPTIONAL, + peer-Parent-Node-Indicator ENUMERATED {true, ...} OPTIONAL, + IAB-DU-Cell-Resource-Configuration-Mode-Info IAB-DU-Cell-Resource-Configuration-Mode-Info OPTIONAL, + IAB-STC-Info IAB-STC-Info OPTIONAL, + rACH-Config-Common RACH-Config-Common OPTIONAL, + rACH-Config-Common-IAB RACH-Config-Common-IAB OPTIONAL, + cSI-RS-Configuration OCTET STRING OPTIONAL, + sR-Configuration OCTET STRING OPTIONAL, + pDCCH-ConfigSIB1 OCTET STRING OPTIONAL, + sCS-Common OCTET STRING OPTIONAL, + iE-Extensions ProtocolExtensionContainer {{Neighbour-Node-Cells-List-Item-ExtIEs}} OPTIONAL +} + +``` + +``` + +Neighbour-Node-Cells-List-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +} + +NeedforGap::= ENUMERATED {true, ...} + +NeedForGapsInfoNR ::= OCTET STRING + +NeedForGapNCSGInfoNR ::= OCTET STRING + +NeedForGapNCSGInfoEUTRA ::= OCTET STRING + +NeedForInterruptionInfoNR ::= OCTET STRING + +Neighbour-Cell-Information-Item ::= SEQUENCE { + +    nRCGI                    NRCGI, + +    intendedTDD-DL-ULConfig    IntendedTDD-DL-ULConfig OPTIONAL, + +    iE-Extensions    ProtocolExtensionContainer { { Neighbour-Cell-Information-ItemExtIEs } }    OPTIONAL + +} + +Neighbour-Cell-Information-ItemExtIEs    FLAP-PROTOCOL-EXTENSION ::= { + +    ... + +} + +NeighbourNR-CellsForSON-List ::= SEQUENCE (SIZE(1.. maxNeighbourCellforSON)) OF NeighbourNR-CellsForSON-Item + +``` +NeighbourNR-CellsForSON-Item ::= SEQUENCE { + nRCGI NRCGI, + nR-ModeInfoRel16 NR-ModeInfoRel16 OPTIONAL, + sSB-PositionsInBurst SSB-PositionsInBurst OPTIONAL, + nRPRACHConfig NRPRACHConfig OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { NeighbourNR-CellsForSON-Item-ExtIEs} } OPTIONAL, + ... +} + +NeighbourNR-CellsForSON-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +NGRANAllocationAndRetentionPriority ::= SEQUENCE { + priorityLevel PriorityLevel, + pre-emptionCapability Pre-emptionCapability, + pre-emptionVulnerability Pre-emptionVulnerability, + iE-Extensions ProtocolExtensionContainer { {NGRANAllocationAndRetentionPriority-ExtIEs} } OPTIONAL +} + +NGRANAllocationAndRetentionPriority-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +NGRANHighAccuracyAccessPointPosition ::= SEQUENCE { + latitude INTEGER (-2147483648.. 2147483647), + longitude INTEGER (-2147483648.. 2147483647), + altitude INTEGER (-64000..1280000), + uncertaintySemi-major INTEGER (0..255), + uncertaintySemi-minor INTEGER (0..255), + orientationOfMajorAxis INTEGER (0..179), + horizontalConfidence INTEGER (0..100), + uncertaintyAltitude INTEGER (0..255), + verticalConfidence INTEGER (0..100), + + iE-Extensions ProtocolExtensionContainer { { NGRANHighAccuracyAccessPointPosition-ExtIEs} } OPTIONAL +} +``` + +``` +NGRANHighAccuracyAccessPointPosition-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +NID ::= BIT STRING (SIZE(44)) +``` + +``` +NonFlterminatingTopologyIndicator ::= ENUMERATED { + true, + ... +} +``` + +} + +NR-CGI-List-For-Restart-Item ::= SEQUENCE { + +nRCGI                    NRCGI, +iE-Extensions        ProtocolExtensionContainer { { NR-CGI-List-For-Restart-ItemExtIEs } } OPTIONAL, +... + +} + +NR-CGI-List-For-Restart-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +NrofSymbolsExtended ::= ENUMERATED {n8, n10, n12, n14, ...} + +NR-PRSBeamInformation ::= SEQUENCE { + +nR-PRSBeamInformationList      NR-PRSBeamInformationList, +LCStoGCSTranslationList        LCStoGCSTranslationList      OPTIONAL, +iE-Extensions    ProtocolExtensionContainer { { NR-PRSBeamInformation-ExtIEs } } OPTIONAL + +} + +NR-PRSBeamInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +NR-PRSBeamInformationList ::= SEQUENCE (SIZE(1.. maxnoofPRS-ResourceSets)) OF NR-PRSBeamInformationItem + +NR-PRSBeamInformationItem ::= SEQUENCE { +    pRSResourceSetID    PRS-Resource-Set-ID, +    pRSAngleList        PRSAngleList, +    iE-Extensions        ProtocolExtensionContainer { { NR-PRSBeamInformationItem-ExtIEs } } OPTIONAL +} + +NR-PRSBeamInformationItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +NR-TADV ::= INTEGER (0.. 7690) + +NRedCapUEIndication ::= ENUMERATED {true, ...} + +ERedcap-Bcast-Information ::= BIT STRING(SIZE(8)) + +NRedCapUEIndication ::= ENUMERATED {true, ...} + +NRPagingeDRXInformation ::= SEQUENCE { +    nripaging-eDRX-Cycle-Idle        NRPaging-eDRX-Cycle-Idle, +    nripaging-Time-Window            NRPaging-Time-Window                                    OPTIONAL, +    iE-Extensions                    ProtocolExtensionContainer { { NRPagingeDRXInformation-ExtIEs } } OPTIONAL, + +``` + ... +} + +NRPagingeDRXInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +NRPaging-eDRX-Cycle-Idle ::= ENUMERATED { + hfquarter, hfhalf, hf1, hf2, hf4, + hf8, hf16, hf32, hf64, hf128, hf256, hf512, hf1024, + ... +} + +NRPaging-Time-Window ::= ENUMERATED { + s1, s2, s3, s4, s5, + s6, s7, s8, s9, s10, + s11, s12, s13, s14, s15, s16, + ..., + s17, s18, s19, s20, s21, + s22, s23, s24, s25, s26, + s27, s28, s29, s30, s31, s32 +} +``` + +``` +NR Paging eDRX Information for RRC INACTIVE ::= SEQUENCE { + nrPaging-eDRX-Cycle-Inactive NR Paging-eDRX-Cycle-Inactive, + iE-Extensions ProtocolExtensionContainer { { NR Paging eDRX Information for RRC INACTIVE-ExtIEs } } OPTIONAL, + ... +} + +NR Paging eDRX Information for RRC INACTIVE-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +NR Paging-eDRX-Cycle-Inactive ::= ENUMERATED { + hfquarter, hfhalf, hf1, + ... +} + +NR Paging long eDRX Information for RRC INACTIVE ::= SEQUENCE { + nrPaging-long-eDRX-Cycle-Inactive NR Paging-long-eDRX-Cycle-Inactive, + nrPaging-Time-Window-Inactive NR Paging-Time-Window-Inactive, + iE-Extensions ProtocolExtensionContainer { { NR Paging long eDRX Information for RRC INACTIVE-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +NR Paging long eDRX Information for RRC INACTIVE-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +NR Paging long eDRX Cycle-Inactive ::= ENUMERATED { +``` + +``` + hf2, hf4, hf8, hf16, hf32, hf64, hf128, hf256, hf512, hf1024 +``` + +``` +} +``` + +``` +NR Paging Time Window-Inactive ::= ENUMERATED { +``` + +``` + s1, s2, s3, s4, s5, +``` + +``` + s6, s7, s8, s9, s10, +``` + +``` + s11, s12, s13, s14, s15, s16, +``` + +``` + s17, s18, s19, s20, s21, s22, +``` + +``` + s23, s24, s25, s26, s27, s28, s29, +``` + +``` + s30, s31, s32, ... +``` + +``` +} +``` + +``` +NonDynamic5QIDescriptor ::= SEQUENCE { +``` + +``` + fiveQI INTEGER (0..255, ...), +``` + +``` + qosPriorityLevel INTEGER (1..127) OPTIONAL, +``` + +``` + averagingWindow AveragingWindow OPTIONAL, +``` + +``` + maxDataBurstVolume MaxDataBurstVolume OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { NonDynamic5QIDescriptor-ExtIEs } } OPTIONAL +``` + +``` +} + +NonDynamic5QIDescriptor-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-CNPacketDelayBudgetDownlink CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional } | + { ID id-CNPacketDelayBudgetUplink CRITICALITY ignore EXTENSION ExtendedPacketDelayBudget PRESENCE optional }, + ... +} + +NonDynamicPQIDescriptor ::= SEQUENCE { + fiveQI INTEGER (0..255, ...), + qosPriorityLevel INTEGER (1..8, ...) OPTIONAL, + averagingWindow AveragingWindow OPTIONAL, + maxDataBurstVolume MaxDataBurstVolume OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { NonDynamicPQIDescriptor-ExtIEs } } OPTIONAL +} + +NonDynamicPQIDescriptor-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +NonUPTrafficType ::= ENUMERATED {ue-associated, non-ue-associated, non-fl, bap-control-pdu,...} + +NoofDownlinkSymbols ::= INTEGER (0..14) +``` + +NoofUplinkSymbols ::= INTEGER (0..14) + +Notification-Cause ::= ENUMERATED {fulfilled, not-fulfilled, ...} + +NotificationControl ::= ENUMERATED {active, not-active, ...} + +NotificationInformation ::= SEQUENCE { +    message-Identifier MessageIdentifier, +    serialNumber SerialNumber, +    iE-Extensions ProtocolExtensionContainer { { NotificationInformationExtIEs} } OPTIONAL, +    ... +} + +NotificationInformationExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +NPNBroadcastInformation ::= CHOICE { +    sNPN-Broadcast-Information NPN-Broadcast-Information-SNPN, +    pNI-NPN-Broadcast-Information NPN-Broadcast-Information-PNI-NPN, +    choice-extension ProtocolIE-SingleContainer { {NPNBroadcastInformation-ExtIEs} } +} + +NPNBroadcastInformation-ExtIEs FLAP-PROTOCOL-IES ::= { + +``` + ... +} + +NPN-Broadcast-Information-SNPN ::= SEQUENCE { + broadcastSNPNID-List BroadcastSNPN-ID-List, + iE-Extension ProtocolExtensionContainer { {NPN-Broadcast-Information-SNPN-ExtIEs} } OPTIONAL, + ... +} + +NPN-Broadcast-Information-SNPN-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +NPN-Broadcast-Information-PNI-NPN ::= SEQUENCE { + broadcastPNI-NPN-ID-Information BroadcastPNI-NPN-ID-List, + iE-Extension ProtocolExtensionContainer { {NPN-Broadcast-Information-PNI-NPN-ExtIEs} } OPTIONAL, + ... +} + +NPN-Broadcast-Information-PNI-NPN-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +NPNSupportInfo ::= CHOICE { +``` + +``` +sNPN-Information NID, +choice-extension ProtocolIE-SingleContainer { { NPNSupportInfo-ExtIEs } } +} + +NPNSupportInfo-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +NRCarrierList ::= SEQUENCE (SIZE(1..maxnoofNRSCSs)) OF NRCarrierItem + +NRCarrierItem ::= SEQUENCE { + carrierSCS NRSCS, + offsetToCarrier INTEGER (0..2199, ...), + carrierBandwidth INTEGER (0..maxnoofPhysicalResourceBlocks, ...), + iE-Extension ProtocolExtensionContainer { {NRCarrierItem-ExtIEs} } OPTIONAL, + ... +} + +NRCarrierItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +NRFreqInfo ::= SEQUENCE { + nRARFCN INTEGER (0..maxNRARFCN), +} +``` + +``` + sul-Information SUL-Information OPTIONAL, + freqBandListNr SEQUENCE (SIZE(1..maxnoofNrCellBands)) OF FreqBandNrItem, + iE-Extensions ProtocolExtensionContainer { { NRFreqInfoExtIEs} } OPTIONAL, + ... +} + +NRFreqInfoExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-FrequencyShift7p5khz CRITICALITY ignore EXTENSION FrequencyShift7p5khz PRESENCE optional }, + ... +} + +NRCGI ::= SEQUENCE { + pLMN-Identity PLMN-Identity, + nRCellIdentity NRCellIdentity, + iE-Extensions ProtocolExtensionContainer { {NRCGI-ExtIEs} } OPTIONAL, + ... +} + +NRCGI-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +NR-Mode-Info ::= CHOICE { + fDD FDD-Info, +``` + +``` +tDD TDD-Info, +choice-extension ProtocolIE-SingleContainer { { NR-Mode-Info-ExtIEs} } +} + +NR-Mode-Info-ExtIEs FLAP-PROTOCOL-IES ::= { + { ID id-NR-U CRITICALITY ignore TYPE NR-U-Channel-Info-List PRESENCE mandatory}, + ... +} + +NR-ModeInfoRel16 ::= CHOICE { + fDD FDD-InfoRel16, + tDD TDD-InfoRel16, + choice-extension ProtocolIE-SingleContainer { { NR-ModeInfoRel16-ExtIEs} } +} + +NR-ModeInfoRel16-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +NRPRACHConfig ::= SEQUENCE { + ulPRACHConfigList NRPRACHConfigList OPTIONAL, + sulPRACHConfigList NRPRACHConfigList OPTIONAL, + iE-Extension ProtocolExtensionContainer { {NRPRACHConfig-ExtIEs} } OPTIONAL, +``` + +``` + +... + +} + +NRPRACHConfig-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +NRCellIdentity ::= BIT STRING (SIZE(36)) + +NRNRB ::= ENUMERATED { nrb11, nrb18, nrb24, nrb25, nrb31, nrb32, nrb38, nrb51, nrb52, nrb65, nrb66, nrb78, nrb79, nrb93, nrb106, nrb107, nrb121, +nrb132, nrb133, nrb135, nrb160, nrb162, nrb189, nrb216, nrb217, nrb245, nrb264, nrb270, nrb273, ..., nrb33, nrb62, nrb124, nrb148, nrb248, nrb44, +nrb58, nrb92, nrb119, nrb188, nrb242, nrb15} + +NRPCI ::= INTEGER(0..1007) + +NRPRACHConfigList ::= SEQUENCE (SIZE(0..maxnoofPRACHconfigs)) OF NRPRACHConfigItem + +NRPRACHConfigItem ::= SEQUENCE { + nRSCS NRSCS, + prachFreqStartfromCarrier INTEGER (0..maxnoofPhysicalResourceBlocks-1, ...), + prachFDM ENUMERATED {one, two, four, eight, ...}, + prachConfigIndex INTEGER (0..255, ..., 256..262), + ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, + two, four, eight, sixteen, ...}, +} + +``` + +``` + freqDomainLength FreqDomainLength, + zeroCorrelZoneConfig INTEGER (0..15), + iE-Extension ProtocolExtensionContainer { { NRPRACHConfigItem-ExtIEs } } OPTIONAL, + ... +} + +NRPRACHConfigItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +NRSCS ::= ENUMERATED { scs15, scs30, scs60, scs120, ..., scs480, scs960} + +NRUERLFReportContainer ::= OCTET STRING + +NR-U-Channel-Info-List ::= SEQUENCE (SIZE (1..maxnoofNR-UChannelIDs)) OF NR-U-Channel-Info-Item + +NR-U-Channel-Info-Item ::= SEQUENCE { + nr-U-channel-ID INTEGER(1.. maxnoofNR-UChannelIDs,...), + nR-ARFCN INTEGER (0..maxNRARFCN), + bandwidth ENUMERATED{mHz-10,mHz-20,mHz-40, mHz-60, mHz-80,...}, + iE-Extensions ProtocolExtensionContainer { { NR-U-Channel-Info-List-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +NR-U-Channel-Info-List-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +NR-U-Channel-List ::= SEQUENCE (SIZE (1..maxnoofNR-UChannelIDs)) OF NR-U-Channel-Item +``` + +``` +NR-U-Channel-Item ::= SEQUENCE { +``` + +``` + nR-U-ChannelID +``` + +``` + INTEGER(1..maxnoofNR-UChannelIDs), +``` + +``` + channelOccupancyTimePercentageDL +``` + +``` + ChannelOccupancyTimePercentage, +``` + +``` + energyDetectionThreshold +``` + +``` + EnergyDetectionThreshold, +``` + +``` + iE-Extensions +``` + +``` + ProtocolExtensionContainer { { NR-U-Channel-Item-ExtIEs } } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +NR-U-Channel-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + { ID id-ChannelOccupancyTimePercentageUL CRITICALITY ignore EXTENSION ChannelOccupancyTimePercentage PRESENCE optional}| +``` + +``` + { ID id-RadioResourceStatusNR-U +``` + +``` + CRITICALITY ignore EXTENSION RadioResourceStatusNR-U PRESENCE optional}, +``` + +``` + ... +``` + +``` +} +``` + +``` +NumberofActiveUEs ::= INTEGER(0..16777215, ...) +``` + +NumberOfBroadcasts ::= INTEGER (0..65535) + +NumberofBroadcastRequest ::= INTEGER (0..65535) + +NumberOfTRPRxTEG ::= ENUMERATED {two, three, four, six, eight, ...} + +NumberOfTRPTxTEG ::= ENUMERATED {two, three, four, six, eight, ...} + +NumDLULSymbols ::= SEQUENCE { +    numDLSymbols    INTEGER (0..13, ...), +    numULSymbols    INTEGER (0..13, ...), +    iE-Extensions    ProtocolExtensionContainer { { NumDLULSymbols-ExtIEs } } OPTIONAL +} + +NumDLULSymbols-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    { ID id-permutation    CRITICALITY ignore    EXTENSION Permutation    PRESENCE optional }, +    ... +} + +NRV2XServicesAuthorized ::= SEQUENCE { +    vehicleUE    VehicleUE    OPTIONAL, +    pedestrianUE    PedestrianUE    OPTIONAL, + +``` + iE-Extensions ProtocolExtensionContainer { {NRV2XServicesAuthorized-ExtIEs} } OPTIONAL + } + + NRV2XServicesAuthorized-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... + } + + NRUESidelinkAggregateMaximumBitrate ::= SEQUENCE { + uENRSidelinkAggregateMaximumBitrate BitRate, + iE-Extensions ProtocolExtensionContainer { {NRUESidelinkAggregateMaximumBitrate-ExtIEs} } OPTIONAL + } + + NRUESidelinkAggregateMaximumBitrate-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... + } + + NZP-CSI-RS-ResourceID ::= INTEGER (0..191) + + N6JitterInformation ::= SEQUENCE { + n6JitterLowerBound INTEGER (-127..127), + n6JitterUpperBound INTEGER (-127..127), + iE-Extensions ProtocolExtensionContainer { { N6JitterInformationExtIEs } } OPTIONAL, + ... + } +``` + +``` +N6JitterInformationExtIEs FIAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +-- O +``` + +``` +OffsetToPointA ::= INTEGER (0..2199,...) +``` + +``` +OnDemandPRS-Info ::= SEQUENCE { +``` + +``` + onDemandPRSRequestAllowed BIT STRING (SIZE (16)), + allowedResourceSetPeriodicityValues BIT STRING (SIZE (24)) OPTIONAL, + allowedPRSBandwidthValues BIT STRING (SIZE (64)) OPTIONAL, + allowedResourceRepetitionFactorValues BIT STRING (SIZE (8)) OPTIONAL, + allowedResourceNumberOfSymbolsValues BIT STRING (SIZE (8)) OPTIONAL, + allowedCombSizeValues BIT STRING (SIZE (8)) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { OnDemandPRS-Info-ExtIEs } } OPTIONAL, + ... +``` + +``` +} +``` + +``` +OnDemandPRS-Info-ExtIEs FIAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +-- P + +PacketDelayBudget ::= INTEGER (0..1023, ...) + +PacketErrorRate ::= SEQUENCE { +    pER-Scalar          PER-Scalar, +    pER-Exponent        PER-Exponent, +    iE-Extensions      ProtocolExtensionContainer { {PacketErrorRate-ExtIEs} } OPTIONAL, +    ... +} + +PacketErrorRate-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +PathAdditionInformation ::= CHOICE { +    indirectPathAddition          IndirectPathAddition, +    directPathAddition            NULL, +    n3C-indirectPathAddition    N3CIndirectPathAddition, +    choice-extension            ProtocolIE-SingleContainer { { PathAdditionInformation-ExtIEs} } +} + +PathAdditionInformation-ExtIEs FLAP-PROTOCOL-IES ::= { +    ... +} + +``` +} + +PER-Scalar ::= INTEGER (0..9, ...) + +PER-Exponent ::= INTEGER (0..9, ...) + +PagingCell-Item ::= SEQUENCE { + nRCGI NRCGI , + iE-Extensions ProtocolExtensionContainer { { PagingCell-ItemExtIEs } } OPTIONAL +} + +PagingCell-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-LastUsedCellIndication CRITICALITY ignore EXTENSION LastUsedCellIndication PRESENCE optional }| + { ID id-PEISubgroupingSupportIndication CRITICALITY ignore EXTENSION PEISubgroupingSupportIndication PRESENCE optional }| + { ID id-Recommended-SSBs-List CRITICALITY ignore EXTENSION Recommended-SSBs-List PRESENCE optional }, + ... +} + +Recommended-SSBs-List ::= SEQUENCE (SIZE(1.. maxnoofSSBAreas)) OF RecommendedSSBItem-List-Item + +RecommendedSSBItem-List-Item ::= SEQUENCE { + sSB-Index SSB-Index, + iE-Extensions ProtocolExtensionContainer { { RecommendedSSBItem-List-Item-ExtIEs } } OPTIONAL +} +``` + +``` +RecommendedSSBItem-List-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +PagingDRX ::= ENUMERATED { +``` + +``` + v32, +``` + +``` + v64, +``` + +``` + v128, +``` + +``` + v256, +``` + +``` + ... +``` + +``` +} +``` + +``` +PagingIdentity ::= CHOICE { +``` + +``` + rANUEPagingIdentity RANUEPagingIdentity, +``` + +``` + cNUEPagingIdentity CNUEPagingIdentity, +``` + +``` + choice-extension ProtocolIE-SingleContainer { { PagingIdentity-ExtIEs } } +``` + +``` +} +``` + +``` +PagingCause ::= ENUMERATED { voice, ... } +``` + +``` +PagingIdentity-ExtIEs FLAP-PROTOCOL-IES ::= { +``` + +``` + ... +``` + +``` +} +``` + +PagingOrigin ::= ENUMERATED { non-3gpp, ... } + +PagingPriority ::= ENUMERATED { prioLevel1, prioLevel2, prioLevel3, prioLevel4, prioLevel5, prioLevel6, prioLevel7, prioLevel8, ... } + +ParentTTimeSource ::= ENUMERATED { synce, ptp, gnss, atomicclock, terrestrialradio, serialtimecode, ntp, handset, other, ... } + +PEIPSAssistanceInfo ::= SEQUENCE { +    cNSubgroupID          CNSubgroupID, +    iE-Extensions      ProtocolExtensionContainer { { PEIPSAssistanceInfo-ExtIEs } } OPTIONAL +} + +PEIPSAssistanceInfo-ExtIEs FIAP-PROTOCOL-EXTENSION ::= { +    ... +} + +RelativePathDelay ::= CHOICE { +    k0                  INTEGER (0..16351), +    k1                  INTEGER (0..8176), +    k2                  INTEGER (0..4088), +    k3                  INTEGER (0..2044), +    k4                  INTEGER (0..1022), +    k5                  INTEGER (0..511), +    choice-extension    ProtocolIE-SingleContainer { { RelativePathDelay-ExtIEs } } + +``` +} + +RelativePathDelay-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +Parent-IAB-Nodes-NA-Resource-Configuration-List ::= SEQUENCE (SIZE(1..maxnoofHSNASlots)) OF Parent-IAB-Nodes-NA-Resource-Configuration-Item + +Parent-IAB-Nodes-NA-Resource-Configuration-Item ::= SEQUENCE { + nADownlink NADownlink OPTIONAL, + nAUplink NAUplink OPTIONAL, + nAFlexible NAFlexible OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Parent-IAB-Nodes-NA-Resource-Configuration-Item-ExtIEs} } OPTIONAL +} + +Parent-IAB-Nodes-NA-Resource-Configuration-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PartialSuccessCell ::= SEQUENCE { + broadcastCellList BroadcastCellList, + iE-Extensions ProtocolExtensionContainer { { PartialSuccessCell-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +PartialSuccessCell-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PathlossReferenceInfo ::= SEQUENCE { + pathlossReferenceSignal PathlossReferenceSignal, + iE-Extensions ProtocolExtensionContainer { {PathlossReferenceInfo-ExtIEs} } OPTIONAL +} + +PathlossReferenceInfo-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PathlossReferenceSignal ::= CHOICE { + sSB SSB, + dL-PRS DL-PRS, + choice-extension ProtocolIE-SingleContainer { {PathlossReferenceSignal-ExtIEs} } +} + +PathlossReferenceSignal-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +PathSwitchConfiguration ::= SEQUENCE { +``` + +``` +targetRelayUEID BIT STRING(SIZE(24)), +remoteUELocalID RemoteUELocalID, +t420 ENUMERATED {ms50, ms100, ms150, ms200, ms500, ms1000, ms2000, ms10000}, +iE-Extensions ProtocolExtensionContainer { { PathSwitchConfiguration-ExtIEs } } OPTIONAL, +... +} +``` + +``` +PathSwitchConfiguration-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PC5QoSFlowIdentifier ::= INTEGER (1..2048) +``` + +``` +PC5-QoS-Characteristics ::= CHOICE { + non-Dynamic-PQI NonDynamicPQIDescriptor, + dynamic-PQI DynamicPQIDescriptor, + choice-extension ProtocolIE-SingleContainer { { PC5-QoS-Characteristics-ExtIEs } } +} +``` + +``` +PC5-QoS-Characteristics-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +PC5QoSParameters ::= SEQUENCE { + pC5-QoS-Characteristics PC5-QoS-Characteristics, + pC5-QoS-Flow-Bit-Rates PC5FlowBitRates OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PC5QoSParameters-ExtIEs } } OPTIONAL, + ... +} + +PC5QoSParameters-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PC5FlowBitRates ::= SEQUENCE { + guaranteedFlowBitRate BitRate, + maximumFlowBitRate BitRate, + iE-Extensions ProtocolExtensionContainer { { PC5FlowBitRates-ExtIEs } } OPTIONAL, + ... +} + +PC5FlowBitRates-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PC5RLCChannelID ::= INTEGER (1..512, ...) +``` + +``` +PC5RLCChannelQoSInformation ::= CHOICE { + pC5RLCChannelQoS QoSFlowLevelQoSParameters, + pC5ControlPlaneTrafficType ENUMERATED {srb1,srb2,...}, + choice-extension ProtocolIE-SingleContainer { { PC5RLCChannelQoSInformation-ExtIEs} } +} + +PC5RLCChannelQoSInformation-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +PC5RLCChannelToBeSetupList ::= SEQUENCE (SIZE(1.. maxnoofPC5RLCChannels)) OF PC5RLCChannelToBeSetupItem + +PC5RLCChannelToBeSetupItem ::= SEQUENCE { + pC5RLCChannelID PC5RLCChannelID, + remoteUELocalID RemoteUELocalID OPTIONAL, + pC5RLCChannelQoSInformation PC5RLCChannelQoSInformation, + rLCMode RLCMode, + iE-Extensions ProtocolExtensionContainer { { PC5RLCChannelToBeSetupItem-ExtIEs } } OPTIONAL, + ... +} + +PC5RLCChannelToBeSetupItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +PC5RLCChannelToBeModifiedList ::= SEQUENCE (SIZE(1.. maxnoofPC5RLCChannels)) OF PC5RLCChannelToBeModifiedItem + +PC5RLCChannelToBeModifiedItem ::= SEQUENCE { +    pC5RLCChannelID              PC5RLCChannelID, +    remoteUELocalID              RemoteUELocalID          OPTIONAL, +    pC5RLCChannelQoSInformation  PC5RLCChannelQoSInformation          OPTIONAL, +    rLCMode                      RLCMode          OPTIONAL, +    iE-Extensions              ProtocolExtensionContainer { { PC5RLCChannelToBeModifiedItem-ExtIEs } } OPTIONAL, +    ... +} + +PC5RLCChannelToBeModifiedItem-ExtIEs  FIAP-PROTOCOL-EXTENSION ::= { +    ... +} + +PC5RLCChannelToBeReleasedList ::= SEQUENCE (SIZE(1.. maxnoofPC5RLCChannels)) OF PC5RLCChannelToBeReleasedItem + +PC5RLCChannelToBeReleasedItem ::= SEQUENCE { +    pC5RLCChannelID              PC5RLCChannelID, +    remoteUELocalID              RemoteUELocalID          OPTIONAL, +    iE-Extensions              ProtocolExtensionContainer { { PC5RLCChannelToBeReleasedItem-ExtIEs } } OPTIONAL, +    ... +} + +``` +PC5RLCChannelToBeReleasedItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PC5RLCChannelSetupList ::= SEQUENCE (SIZE(1.. maxnoofPC5RLCChannels)) OF PC5RLCChannelSetupItem + +PC5RLCChannelSetupItem ::= SEQUENCE { + pC5RLCChannelID PC5RLCChannelID, + remoteUELocalID RemoteUELocalID OPTIONAL, + iE-Extensions ProtocolExtensionContainer { PC5RLCChannelSetupItem-ExtIEs } OPTIONAL, + ... +} + +PC5RLCChannelSetupItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PC5RLCChannelFailedToBeSetupList ::= SEQUENCE (SIZE(1.. maxnoofPC5RLCChannels)) OF PC5RLCChannelFailedToBeSetupItem + +PC5RLCChannelFailedToBeSetupItem ::= SEQUENCE { + pC5RLCChannelID PC5RLCChannelID, + remoteUELocalID RemoteUELocalID OPTIONAL, + cause Cause OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { PC5RLCChannelFailedToBeSetupItem-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +PC5RLCChannelFailedToBeSetupItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PC5RLCChannelModifiedList ::= SEQUENCE (SIZE(1.. maxnoofPC5RLCChannels)) OF PC5RLCChannelModifiedItem +``` + +``` +PC5RLCChannelModifiedItem ::= SEQUENCE { + pC5RLCChannelID PC5RLCChannelID, + remoteUELocalID RemoteUELocalID OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PC5RLCChannelModifiedItem-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +PC5RLCChannelModifiedItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PC5RLCChannelFailedToBeModifiedList ::= SEQUENCE (SIZE(1.. maxnoofPC5RLCChannels)) OF PC5RLCChannelFailedToBeModifiedItem +``` + +``` +PC5RLCChannelFailedToBeModifiedItem ::= SEQUENCE { +``` + +``` + pC5RLCChannelID PC5RLCChannelID, + remoteUELocalID RemoteUELocalID OPTIONAL, + cause Cause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { PC5RLCChannelFailedToBeModifiedItem-ExtIEs } OPTIONAL, + ... +} +``` + +``` +PC5RLCChannelFailedToBeModifiedItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PC5RLCChannelRequiredToBeModifiedList ::= SEQUENCE (SIZE(1.. maxnoofPC5RLCChannels)) OF PC5RLCChannelRequiredToBeModifiedItem +``` + +``` +PC5RLCChannelRequiredToBeModifiedItem ::= SEQUENCE { + pC5RLCChannelID PC5RLCChannelID, + remoteUELocalID RemoteUELocalID OPTIONAL, + iE-Extensions ProtocolExtensionContainer { PC5RLCChannelRequiredToBeModifiedItem-ExtIEs } OPTIONAL, + ... +} +``` + +``` +PC5RLCChannelRequiredToBeModifiedItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PC5RLCChannelRequiredToBeReleasedList ::= SEQUENCE (SIZE(1.. maxnoofPC5RLCChannels)) OF PC5RLCChannelRequiredToBeReleasedItem + +PC5RLCChannelRequiredToBeReleasedItem ::= SEQUENCE { + pC5RLCChannelID PC5RLCChannelID, + remoteUELocalID RemoteUELocalID OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PC5RLCChannelRequiredToBeReleasedItem-ExtIEs } } OPTIONAL, + ... +} + +PC5RLCChannelRequiredToBeReleasedItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDCCH-BlindDetectionSCG ::= OCTET STRING + +PDCMeasurementPeriodicity ::= ENUMERATED +{ms80, ms120, ms160, ms240, ms320, ms480, ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ...} + +PDCMeasurementQuantities ::= SEQUENCE (SIZE (1.. maxnoofMeasPDC)) OF ProtocolIE-SingleContainer { {PDCMeasurementQuantities-ItemIEs} } + +PDCMeasurementQuantities-ItemIEs FLAP-PROTOCOL-IES ::= { + { ID id-PDCMeasurementQuantities-Item CRITICALITY reject TYPE PDCMeasurementQuantities-Item PRESENCE mandatory} +} +``` + +``` +PDCMeasurementQuantities-Item ::= SEQUENCE { + pDCMeasurementQuantitiesValue PDCMeasurementQuantitiesValue, + iE-Extensions ProtocolExtensionContainer { { PDCMeasurementQuantitiesValue-ExtIEs} } OPTIONAL +} + +PDCMeasurementQuantitiesValue-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDCMeasurementQuantitiesValue ::= ENUMERATED { + nr-pdc-tadv, + gNB-rx-tx, + ... +} + +PDCMeasurementResult ::= SEQUENCE { + pDCMeasuredResultsList PDCMeasuredResultsList, + iE-Extensions ProtocolExtensionContainer { { PDCMeasurementResult-ExtIEs} } OPTIONAL +} + +PDCMeasurementResult-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PDCMeasuredResultsList ::= SEQUENCE (SIZE(1..maxnoofMeasPDC)) OF PDCMeasuredResults-Item + +PDCMeasuredResults-Item ::= SEQUENCE { + pDCMeasuredResults-Value PDCMeasuredResults-Value, + iE-Extensions ProtocolExtensionContainer {{ PDCMeasuredResults-Item-ExtIEs }} OPTIONAL +} + +PDCMeasuredResults-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PDCMeasuredResults-Value ::= CHOICE { + pDC-TADV-NR PDC-TADV-NR, + pDC-RxTxTimeDiff PDC-RxTxTimeDiff, + choice-extension ProtocolIE-SingleContainer { { PDCMeasuredResults-Value-ExtIEs} } +} + +PDCMeasuredResults-Value-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +PDCReportType ::= ENUMERATED { + onDemand, + periodic, +} +``` + +``` + ... +} + +PDC-RxTxTimeDiff ::= INTEGER (0..61565, ...) + +PDC-TADV-NR ::= INTEGER (0..62500, ...) + +PDCP-SN ::= INTEGER (0..4095) + +PDCPSNLength ::= ENUMERATED { twelve-bits, eighteen-bits, ... } + +PDUSessionID ::= INTEGER (0..255) + +PEISubgroupingSupportIndication ::= ENUMERATED { true, ... } + +ReportingPeriodicityValue ::= INTEGER (0..512, ...) + +Periodicity ::= INTEGER (0..640000, ...) + +PeriodicitySRS ::= ENUMERATED { ms0p125, ms0p25, ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms4, ms5, ms8, ms10, ms16, ms20, ms32, ms40, ms64, ms80, ms160, ms320, ms640, ms1280, ms2560, ms5120, ms10240, ... } + +PeriodicityList ::= SEQUENCE (SIZE(1.. maxnoSRS-ResourcePerSet)) OF PeriodicityList-Item + +PeriodicityList-Item ::= SEQUENCE { +``` + +``` + periodicitySRS PeriodicitySRS, + iE-Extensions ProtocolExtensionContainer { { PeriodicityList-ItemExtIEs } } OPTIONAL +} +``` + +``` +PeriodicityList-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PeriodicityBound ::= SEQUENCE { + periodicityLowerBound Periodicity, + periodicityUpperBound Periodicity, + iE-Extensions ProtocolExtensionContainer { { PeriodicityBound-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +PeriodicityBound-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +AllowedPeriodicityList ::= SEQUENCE (SIZE(1..maxnoofPeriodicities)) OF Periodicity +``` + +``` +PeriodicityRange ::= CHOICE { + periodicityBound PeriodicityBound, + periodicityList AllowedPeriodicityList, +``` + +``` +choice-extensions ProtocolIE-SingleContainer { {PeriodicityRange-ExtIEs} } +} + +PeriodicityRange-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +Permutation ::= ENUMERATED {dfu, ufd, ...} + +Ph-InfoMCG ::= OCTET STRING + +Ph-InfoSCG ::= OCTET STRING + +PLMN-Identity ::= OCTET STRING (SIZE(3)) + +PlayoutDelayForMediaStartup ::= OCTET STRING + +PortNumber ::= BIT STRING (SIZE (16)) + +PosAssistance-Information ::= OCTET STRING + +PosAssistanceInformationFailureList ::= OCTET STRING +``` + +PosBroadcast ::= ENUMERATED { + +start, + +stop, + +... + +} + +PosConextRevIndication ::= ENUMERATED {true, ...} + +PositioningBroadcastCells ::= SEQUENCE (SIZE (1..maxNoBcastCell)) OF NRCGI + +PosMeasGapPreConfigList ::= SEQUENCE { + +posMeasGapPreConfigToAddModList OCTET STRING OPTIONAL, + +posMeasGapPreConfigToReleaseList OCTET STRING OPTIONAL, + +iE-Extensions ProtocolExtensionContainer { { PosMeasGapPreConfigList-ExtIEs} } OPTIONAL + +} + +PosMeasGapPreConfigList-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +MeasurementPeriodicity ::= ENUMERATED + +{ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, min1, min6, min12, min30, ..., ms20480, ms40960, extended } + +MeasurementPeriodicityExtended ::= ENUMERATED {ms160, ms320, ms1280, ms2560, ms61440, ms81920, ms368640, ms737280, ms1843200, ...} + +PosMeasurementPeriodicityNR-AoA ::= ENUMERATED { + +ms160, + +ms320, + +ms640, + +ms1280, + +ms2560, + +ms5120, + +ms10240, + +ms20480, + +ms40960, + +ms61440, + +ms81920, + +ms368640, + +ms737280, + +ms1843200, + +... + +} + +PosMeasurementQuantities ::= SEQUENCE (SIZE(1.. maxnoofPosMeas)) OF PosMeasurementQuantities-Item + +``` + +PosMeasurementQuantities-Item ::= SEQUENCE { + posMeasurementType PosMeasurementType, + timingReportingGranularityFactor INTEGER (0..5) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PosMeasurementQuantities-ItemExtIEs} } OPTIONAL +} + +``` + +``` + +PosMeasurementQuantities-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +PosMeasurementResult ::= SEQUENCE (SIZE (1.. maxnoofPosMeas)) OF PosMeasurementResultItem + +``` + +``` + +PosMeasurementResultItem ::= SEQUENCE { + measuredResultsValue MeasuredResultsValue, + timeStamp Timestamp, + measurementQuality TRPMeasurementQuality OPTIONAL, + measurementBeamInfo MeasurementBeamInfo OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PosMeasurementResultItemExtIEs } } OPTIONAL +} + +``` + +``` + +PosMeasurementResultItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-ARP-ID CRITICALITY ignore EXTENSION ARP-ID PRESENCE optional}| + { ID id-SRSResourcetype CRITICALITY ignore EXTENSION SRSResourcetype PRESENCE optional}| + { ID id-LoS-NLoSInformation CRITICALITY ignore EXTENSION LoS-NLoSInformation PRESENCE optional }| +} + +``` + +``` +{ ID id-Mobile-TRP-LocationInformation CRITICALITY ignore EXTENSION Mobile-TRP-LocationInformation PRESENCE optional }, +... +} +``` + +``` +PosMeasurementResultList ::= SEQUENCE (SIZE(1.. maxNoOfMeasTRPs)) OF PosMeasurementResultList-Item +``` + +``` +PosMeasurementResultList-Item ::= SEQUENCE { + posMeasurementResult PosMeasurementResult, + tRPID TRPID, + iE-Extensions ProtocolExtensionContainer { { PosMeasurementResultList-ItemExtIEs } } OPTIONAL +} +``` + +``` +PosMeasurementResultList-ItemExtIEs FIAP-PROTOCOL-EXTENSION ::= { + { ID id-NRCGI CRITICALITY ignore EXTENSION NRCGI PRESENCE optional }, + ... +} +``` + +``` +PosMeasurementType ::= ENUMERATED { + gnb-rx-tx, + ul-srs-rsrp, + ul-aoa, + ul-rtoa, + ... , + multiple-ul-aoa, +} +``` + +``` + ul-srs-rsrpp +} + +PosReportCharacteristics ::= ENUMERATED { + ondemand, + periodic, + ... +} + +PosResourceSetType ::= CHOICE { + periodic PosResourceSetTypePR, + semi-persistent PosResourceSetTypeSP, + aperiodic PosResourceSetTypeAP, + choice-extension ProtocolIE-SingleContainer { { PosResourceSetType-ExtIEs } } +} + +PosResourceSetType-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +PosResourceSetTypePR ::= SEQUENCE { + posperiodicSet ENUMERATED{true, ...}, + iE-Extensions ProtocolExtensionContainer { { PosResourceSetTypePR-ExtIEs} } OPTIONAL +} +``` + +``` +PosResourceSetTypePR-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PosResourceSetTypeSP ::= SEQUENCE { + possemi-persistentSet ENUMERATED{true, ...}, + iE-Extensions ProtocolExtensionContainer { { PosResourceSetTypeSP-ExtIEs} } OPTIONAL +} + +PosResourceSetTypeSP-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PosResourceSetTypeAP ::= SEQUENCE { + sRSResourceTrigger-List INTEGER(1..3), + iE-Extensions ProtocolExtensionContainer { { PosResourceSetTypeAP-ExtIEs} } OPTIONAL +} + +PosResourceSetTypeAP-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PosSITypeList ::= SEQUENCE (SIZE(1.. maxnoofPosSITypes)) OF PosSIType-Item +``` + +``` +PosSItype-Item ::= SEQUENCE { + posSItype PosSItype , + iE-Extensions ProtocolExtensionContainer { { PosSItype-ItemExtIEs } } OPTIONAL +} + +PosSItype-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PosSItype ::= INTEGER (1..32, ...) + +PosSRSResourceID-List ::= SEQUENCE (SIZE (1..maxnoSRS-PosResourcePerSet)) OF SRSPosResourceID + +PosSRSResource-Item ::= SEQUENCE { + srs-PosResourceId SRSPosResourceID, + transmissionCombPos TransmissionCombPos, + startPosition INTEGER (0..13), + nrofSymbols ENUMERATED { n1, n2, n4, n8, n12 }, + freqDomainShift INTEGER (0..268), + c-SRS INTEGER (0..63), + groupOrSequenceHopping ENUMERATED { neither, groupHopping, sequenceHopping }, + resourceTypePos ResourceTypePos, + sequenceId INTEGER (0.. 65535), + spatialRelationPos SpatialRelationPos OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { PosSRSResource-Item-ExtIEs } } OPTIONAL +} +``` + +``` +PosSRSResource-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PosSRSResource-List ::= SEQUENCE (SIZE (1..maxnoSRS-PosResources)) OF PosSRSResource-Item +``` + +``` +PosSRSResourceSet-Item ::= SEQUENCE { + possrsResourceSetID INTEGER(0..15), + possRSResourceID-List PosSRSResourceID-List, + posresourceSetType PosResourceSetType, + iE-Extensions ProtocolExtensionContainer { { PosSRSResourceSet-Item-ExtIEs } } OPTIONAL +} +``` + +``` +PosSRSResourceSet-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PosSRSResourceSet-List ::= SEQUENCE (SIZE (1..maxnoSRS-PosResourceSets)) OF PosSRSResourceSet-Item +``` + +``` +PrimaryPathIndication ::= ENUMERATED { + true, +``` + +``` + false, + ... +} + +Pre-emptionCapability ::= ENUMERATED { + shall-not-trigger-pre-emption, + may-trigger-pre-emption +} + +Pre-emptionVulnerability ::= ENUMERATED { + not-pre-emptable, + pre-emptable +} + +Preconfigured-measurement-GAP-Request ::= ENUMERATED {true, ...} + +PriorityLevel ::= INTEGER { spare (0), highest (1), lowest (14), no-priority (15) } (0..15) + +ProtectedEUTRAResourceIndication ::= OCTET STRING + +Protected-EUTRA-Resources-Item ::= SEQUENCE { + spectrumSharingGroupID SpectrumSharingGroupID, + eUTRACells-List EUTRACells-List, + iE-Extensions ProtocolExtensionContainer { { Protected-EUTRA-Resources-ItemExtIEs } } OPTIONAL +} +``` + +} + +Protected-EUTRA-Resources-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +PRSConfiguration ::= SEQUENCE { + +pRSResourceSet-List PRSResourceSet-List, + +iE-Extensions ProtocolExtensionContainer { { PRSConfiguration-ExtIEs } } OPTIONAL + +} + +PRSConfiguration-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +PRSInformationPos ::= SEQUENCE { + +pRS-IDPos INTEGER(0..255), + +pRS-Resource-Set-IDPos INTEGER(0..7), + +pRS-Resource-IDPos INTEGER(0..63) OPTIONAL, + +iE-Extensions ProtocolExtensionContainer { { PRSInformationPos-ExtIEs } } OPTIONAL + +} + +PRSInformationPos-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +``` +} + +PRS-Measurement-Info-List ::= SEQUENCE (SIZE(1..maxFreqLayers)) OF PRS-Measurement-Info-List-Item + +PRS-Measurement-Info-List-Item ::= SEQUENCE { + pointA INTEGER (0..3279165), + measPRSPeriodicity ENUMERATED {ms20, ms40, ms80, ms160, ...}, + measPRSOffset INTEGER (0..159, ...), + measurementPRSLength ENUMERATED {ms1dot5, ms3, ms3dot5, ms4, ms5dot5, ms6, ms10, ms20}, + iE-Extensions ProtocolExtensionContainer { { PRS-Measurement-Info-List-Item-ExtIEs } } OPTIONAL, + ... +} + +PRS-Measurement-Info-List-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +Potential-SpCell-Item ::= SEQUENCE { + potential-SpCell-ID NRCGI , + iE-Extensions ProtocolExtensionContainer { { Potential-SpCell-ItemExtIEs } } OPTIONAL, + ... +} +``` + +``` +Potential-SpCell-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PRSAngleList ::= SEQUENCE (SIZE(1.. maxnoofPRS-ResourcesPerSet)) OF PRSAngleItem + +PRSAngleItem ::= SEQUENCE { + nR-PRS-Azimuth INTEGER (0..359), + nR-PRS-Azimuth-fine INTEGER (0..9), + nR-PRS-Elevation INTEGER (0..180), + nR-PRS-Elevation-fine INTEGER (0..9), + iE-Extensions ProtocolExtensionContainer { { PRSAngleItem-ItemExtIEs } } OPTIONAL +} + +PRSAngleItem-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-PRS-Resource-ID CRITICALITY ignore EXTENSION PRS-Resource-ID PRESENCE optional }, + ... +} + +PRSConfigRequestType ::= ENUMERATED {configure, off, ...} + +PRSMuting ::= SEQUENCE { + pRSMutingOption1 PRSMutingOption1 OPTIONAL, +``` + +``` + pRSMutingOption2 PRSMutingOption2 OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PRSMuting-ExtIEs} } OPTIONAL +} + +PRSMuting-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PRSMutingOption1 ::= SEQUENCE { + mutingPattern DL-PRSMutingPattern, + mutingBitRepetitionFactor ENUMERATED{rf1,rf2,rf4,rf8,...}, + iE-Extensions ProtocolExtensionContainer { { PRSMutingOption1-ExtIEs} } OPTIONAL +} + +PRSMutingOption1-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PRSMutingOption2 ::= SEQUENCE { + mutingPattern DL-PRSMutingPattern, + iE-Extensions ProtocolExtensionContainer { { PRSMutingOption2-ExtIEs} } OPTIONAL +} + +PRSMutingOption2-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` +... +} + +PRS-Resource-ID ::= INTEGER (0..63) + +PRSResource-List ::= SEQUENCE (SIZE (1..maxnoofPRSresources)) OF PRSResource-Item + +PRSResource-Item ::= SEQUENCE { + pRSResourceID PRS-Resource-ID, + sequenceID INTEGER (0..4095), + rEOffset INTEGER (0..11,...), + resourceSlotOffset INTEGER (0..511), + resourceSymbolOffset INTEGER (0..12), + qCLInfo PRSResource-QCLInfo OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PRSResource-Item-ExtIEs} } OPTIONAL +} + +PRSResource-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-ExtendedResourceSymbolOffset CRITICALITY ignore EXTENSION ExtendedResourceSymbolOffset PRESENCE optional}, + ... +} + +ExtendedResourceSymbolOffset ::= INTEGER (0..13,...) +``` + +``` +PRSResource-QCLInfo ::= CHOICE { + qCLSourceSSB PRSResource-QCLSourceSSB, + qCLSourcePRS PRSResource-QCLSourcePRS, + choice-extension ProtocolIE-SingleContainer { { PRSResource-QCLInfo-ExtIEs } } +} + +PRSResource-QCLInfo-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +PRSResource-QCLSourceSSB ::= SEQUENCE { + pCI-NR INTEGER(0..1007), + SSB-Index SSB-Index OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PRSResource-QCLSourceSSB-ExtIEs } } OPTIONAL, + ... +} + +PRSResource-QCLSourceSSB-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PRSResource-QCLSourcePRS ::= SEQUENCE { + qCLSourcePRSResourceSetID PRS-Resource-Set-ID, + qCLSourcePRSResourceID PRS-Resource-ID OPTIONAL, +``` + +``` + +iE-Extensions ProtocolExtensionContainer { { PRSResource-QCLSourcePRS-ExtIEs } } OPTIONAL +} + +PRSResource-QCLSourcePRS-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PRS-Resource-Set-ID ::= INTEGER(0..7) + +PRSResourceSet-List ::= SEQUENCE (SIZE (1.. maxnoofPRSresourceSets)) OF PRSResourceSet-Item + +PRSResourceSet-Item ::= SEQUENCE { + pRSResourceSetID PRS-Resource-Set-ID, + subcarrierSpacing ENUMERATED{kHz15, kHz30, kHz60, kHz120, ...}, + pRSbandwidth INTEGER(1..63), + startPRB INTEGER(0..2176), + pointA INTEGER (0..3279165), + combSize ENUMERATED{n2, n4, n6, n12, ...}, + cPType ENUMERATED{normal, extended, ...}, + resourceSetPeriodicity ENUMERATED{n4,n5,n8,n10,n16,n20,n32,n40,n64,n80,n160,n320,n640,n1280,n2560,n5120,n10240,n20480,n40960, +n81920,..., n128, n256, n512}, + resourceSetSlotOffset INTEGER(0..81919,...), + resourceRepetitionFactor ENUMERATED{rf1,rf2,rf4,rf6,rf8,rf16,rf32,...}, + resourceTimeGap ENUMERATED{tg1,tg2,tg4,tg8,tg16,tg32,...}, + resourceNumberOfSymbols ENUMERATED{n2,n4,n6,n12,...,n1}, + pRSMuting PRSMuting OPTIONAL, +} + +``` + +``` + pRSResourceTransmitPower INTEGER(-60..50), + pRSResource-List PRSResource-List, + iE-Extensions ProtocolExtensionContainer { { PRSResourceSet-Item-ExtIEs } } OPTIONAL +} + +PRSResourceSet-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PRSTransmissionOffIndication ::= CHOICE { + pRSTransmissionOffPerTRP NULL, + pRSTransmissionOffPerResourceSet PRSTransmissionOffPerResourceSet, + pRSTransmissionOffPerResource PRSTransmissionOffPerResource, + choice-extension ProtocolIE-SingleContainer { { PRSTransmissionOffIndication-ExtIEs } } +} + +PRSTransmissionOffIndication-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +PRSTransmissionOffPerResource ::= SEQUENCE (SIZE (1..maxnoofPRSresourceSets)) OF PRSTransmissionOffPerResource-Item + +PRSTransmissionOffPerResource-Item ::= SEQUENCE { + pRSResourceSetID PRS-Resource-Set-ID, +``` + +``` +pRSTransmissionOffIndicationPerResourceList SEQUENCE (SIZE(1.. maxnoofPRSresources)) OF PRSTransmissionOffIndicationPerResource-Item, +iE-Extensions ProtocolExtensionContainer { { PRSTransmissionOffPerResource-Item-ExtIEs } } OPTIONAL, +... +} + +PRSTransmissionOffPerResource-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +... +} + +PRSTransmissionOffIndicationPerResource-Item ::= SEQUENCE { + pRSResourceID PRS-Resource-ID, + iE-Extensions ProtocolExtensionContainer { { PRSTransmissionOffIndicationPerResource-Item-ExtIEs } } OPTIONAL, + ... +} + +PRSTransmissionOffIndicationPerResource-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +... +} + +PRSTransmissionOffInformation ::= SEQUENCE { + pRSTransmissionOffIndication PRSTransmissionOffIndication, + iE-Extensions ProtocolExtensionContainer { { PRSTransmissionOffInformation-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +PRSTransmissionOffInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PRSTransmissionOffPerResourceSet ::= SEQUENCE (SIZE (1..maxnoofPRSresourceSets)) OF PRSTransmissionOffPerResourceSet-Item + +PRSTransmissionOffPerResourceSet-Item ::= SEQUENCE { + pRSResourceSetID PRS-Resource-Set-ID, + iE-Extensions ProtocolExtensionContainer { { PRSTransmissionOffPerResourceSet-Item-ExtIEs } } OPTIONAL, + ... +} + +PRSTransmissionOffPerResourceSet-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PWS-Failed-NR-CGI-Item ::= SEQUENCE { + nRCGI NRCGI, + numberOfBroadcasts NumberOfBroadcasts, + iE-Extensions ProtocolExtensionContainer { { PWS-Failed-NR-CGI-ItemExtIEs } } OPTIONAL, + ... +} +``` + +``` +PWS-Failed-NR-CGI-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +PWSSystemInformation ::= SEQUENCE { + sIBType SIBType-PWS, + sIBmessage OCTET STRING, + iE-Extensions ProtocolExtensionContainer { { PWSSystemInformationExtIEs } } OPTIONAL, + ... +} + +PWSSystemInformationExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-NotificationInformation CRITICALITY ignore EXTENSION NotificationInformation PRESENCE optional } | + { ID id-AdditionalSIBMessageList CRITICALITY reject EXTENSION AdditionalSIBMessageList PRESENCE optional }, + ... +} + +PrivacyIndicator ::= ENUMERATED {immediate-MDT, logged-MDT, ...} + +PRS-ID ::= INTEGER(0..255) + +PRSTRPList ::= SEQUENCE (SIZE(1.. maxnoofTRPs)) OF PRSTRPItem +``` + +``` +PRSTRPItem ::= SEQUENCE { + tRP-ID TRPID, + requestedDLPRSTransmissionCharacteristics RequestedDLPRSTransmissionCharacteristics OPTIONAL, + -- The IE shall be present if the PRS Configuration Request Type IE is set to "configure" -- + pRSTransmissionOffInformation PRSTransmissionOffInformation OPTIONAL, + -- The IE shall be present if the PRS Configuration Request Type IE is set to "off" -- + + iE-Extensions ProtocolExtensionContainer { { PRSTRPItem-ExtIEs} } OPTIONAL, + ... +} + +PRSTRPItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +RequestedDLPRSTransmissionCharacteristics ::= SEQUENCE { + requestedDLPRSResourceSet-List RequestedDLPRSResourceSet-List, + numberOfFrequencyLayers INTEGER(1..4) OPTIONAL, + startTimeAndDuration StartTimeAndDuration OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { RequestedDLPRSTransmissionCharacteristics-ExtIEs} } OPTIONAL, + ... +} + +RequestedDLPRSTransmissionCharacteristics-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` + +} + +RequestedDLPRSResourceSet-List ::= SEQUENCE (SIZE (1..maxnoofPRSresourceSets)) OF RequestedDLPRSResourceSet-Item + +RequestedDLPRSResourceSet-Item ::= SEQUENCE { + pRSbandwidth INTEGER(1..63), + combSize ENUMERATED{n2, n4, n6, n12, ...} OPTIONAL, + resourceSetPeriodicity ENUMERATED{n4,n5,n8,n10,n16,n20,n32,n40,n64,n80,n160,n320,n640,n1280,n2560,n5120,n10240,n20480,n40960, +n81920,..., n128, n256, n512} OPTIONAL, + resourceRepetitionFactor ENUMERATED{rf1,rf2,rf4,rf6,rf8,rf16,rf32,...} OPTIONAL, + resourceNumberOfSymbols ENUMERATED{n2,n4,n6,n12,...,n1} OPTIONAL, + requestedDLPRSResource-List RequestedDLPRSResource-List OPTIONAL, + resourceSetStartTimeAndDuration StartTimeAndDuration OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { RequestedDLPRSResourceSet-Item-ExtIEs} } OPTIONAL, + ... +} + +RequestedDLPRSResourceSet-Item-ExtIEs FIAP-PROTOCOL-EXTENSION ::= { + ... +} + +RequestedDLPRSResource-List ::= SEQUENCE (SIZE (1..maxnoofPRSresources)) OF RequestedDLPRSResource-Item + +RequestedDLPRSResource-Item ::= SEQUENCE { + qCLInfo PRSResource-QCLInfo OPTIONAL, +} + +``` + +``` + iE-Extensions ProtocolExtensionContainer { { RequestedDLPRSResource-Item-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +RequestedDLPRSResource-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PRSTransmissionTRPList ::= SEQUENCE (SIZE(1.. maxnoofTRPs)) OF PRSTransmissionTRPItem +``` + +``` +PRSTransmissionTRPItem ::= SEQUENCE { + tRP-ID TRPID, + pRSConfiguration PRSConfiguration, + iE-Extensions ProtocolExtensionContainer { { PRSTransmissionTRPItem-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +PRSTransmissionTRPItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +PreambleIndex ::= INTEGER(0..63) +``` + +``` +PDUSetQoSParameters ::= SEQUENCE { + pduSetDelayBudget ExtendedPacketDelayBudget OPTIONAL, + pduSetErrorRate PacketErrorRate OPTIONAL, + pduSetIntegratedHandlingInformation ENUMERATED {true, false, ...} OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { PDUSetQoSParameters-ExtIEs } } OPTIONAL +} +``` + +``` +PDUSetQoSParameters-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +-- Q + +``` +QCI ::= INTEGER (0..255) +``` + +``` +QoEInformation ::= SEQUENCE { + qoEInformationList QoEInformationList, + iE-Extensions ProtocolExtensionContainer { { QoEInformation-ExtIEs } } OPTIONAL +} +``` + +``` +QoEInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +QoEInformationList ::= SEQUENCE (SIZE(1.. maxnoofQoEInformation)) OF QoEInformationList-Item +``` + +``` +QoEInformationList-Item ::= SEQUENCE { + qoEMetrics QoEMetrics OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { QoEInformationList-Item-ExtIEs} } OPTIONAL +} +``` + +``` +QoEInformationList-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + {ID id-dRB-List CRITICALITY ignore EXTENSION DRB-List PRESENCE optional}, + ... +} +``` + +``` +QoEMetrics ::= SEQUENCE { + appLayerBufferLevelList AppLayerBufferLevelList OPTIONAL, + playoutDelayForMediaStartup PlayoutDelayForMediaStartup OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { QoEMetrics-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +QoEMetrics-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` + +QoS-Characteristics ::= CHOICE { + non-Dynamic-5QI NonDynamic5QIDescriptor, + dynamic-5QI Dynamic5QIDescriptor, + choice-extension ProtocolIE-SingleContainer { { QoS-Characteristics-ExtIEs } } +} + +QoS-Characteristics-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +QoSFlowIdentifier ::= INTEGER (0..63) + +QoSFlowLevelQoSParameters ::= SEQUENCE { + qoS-Characteristics QoS-Characteristics, + nGRANallocationRetentionPriority NGRANAllocationAndRetentionPriority, + gBR-QoS-Flow-Information GBR-QoSFlowInformation OPTIONAL, + reflective-QoS-Attribute ENUMERATED {subject-to, ...} OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { QoSFlowLevelQoSParameters-ExtIEs } } OPTIONAL +} + +QoSFlowLevelQoSParameters-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-PDUSessionID CRITICALITY ignore EXTENSION PDUSessionID PRESENCE optional}| + { ID id-ULPDUSessionAggregateMaximumBitRate CRITICALITY ignore EXTENSION BitRate PRESENCE optional}| + { ID id-QosMonitoringRequest CRITICALITY ignore EXTENSION QosMonitoringRequest PRESENCE optional}| +} + +``` + +``` +{ ID id-PDCPTerminatingNodeDLTNLAddrInfo CRITICALITY ignore EXTENSION TransportLayerAddress PRESENCE optional }| +{ ID id-PDUSetQoSParameters CRITICALITY ignore EXTENSION PDUSetQoSParameters PRESENCE optional}, +... +} +``` + +``` +QoSFlowMappingIndication ::= ENUMERATED {ul,dl,...} +``` + +``` +QoSInformation ::= CHOICE { + eUTRANQoS EUTRANQoS, + choice-extension ProtocolIE-SingleContainer { { QoSInformation-ExtIEs} } +} +``` + +``` +QoSInformation-ExtIEs FLAP-PROTOCOL-IES ::= { + { ID id-DRB-Information CRITICALITY ignore TYPE DRB-Information PRESENCE mandatory}, + ... +} +``` + +``` +QosMonitoringRequest ::= ENUMERATED {ul, dl, both, ..., stop} +``` + +``` +QoSParaSetIndex ::= INTEGER (1..8, ...) +``` + +``` +QoSParaSetNotifyIndex ::= INTEGER (0..8, ...) +``` + +``` +-- R +``` + +RACH-Config-Common ::= OCTET STRING + +RACH-Config-Common-IAB ::= OCTET STRING + +RAReportContainer ::= OCTET STRING + +RAReportList ::= SEQUENCE (SIZE(1.. maxnoofRAReports)) OF RAReportItem + +RAReportItem ::= SEQUENCE { +    rAReportContainer              RAReportContainer, +    uEAAssistantIdentifier     GNB-DU-UE-FlAP-ID          OPTIONAL, +    iE-Extensions                ProtocolExtensionContainer { RAReportItem-ExtIEs }   OPTIONAL, +    ... +} + +RAReportItem-ExtIEs   FlAP-PROTOCOL-EXTENSION ::= { +    ... +} + +RAReportIndicationList ::= SEQUENCE (SIZE(1..maxnoofUEsforRAReportIndications)) OF RAReportIndicationList-Item + +RAReportIndicationList-Item ::= SEQUENCE { +    gNB-CU-UE-FlAP-ID                  GNB-CU-UE-FlAP-ID, + +``` +iE-Extensions ProtocolExtensionContainer { { RAReportIndicationList-Item-ExtIEs} } OPTIONAL, +... + +} + +RAReportIndicationList-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +RadioResourceStatus ::= SEQUENCE { + sSBAreaRadioResourceStatusList SSBAreaRadioResourceStatusList, + iE-Extensions ProtocolExtensionContainer { { RadioResourceStatus-ExtIEs} } OPTIONAL +} + +RadioResourceStatus-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-SliceRadioResourceStatus CRITICALITY ignore EXTENSION SliceRadioResourceStatus PRESENCE optional }| + { ID id-MIMOPRBusageInformation CRITICALITY ignore EXTENSION MIMOPRBusageInformation PRESENCE optional }, + ... +} + +RadioResourceStatusNR-U ::= SEQUENCE { + dl-Total-PRB-usage INTEGER (0..100), +} +``` + +``` + ul-Total-PRB-usage INTEGER (0..100), + iE-Extensions ProtocolExtensionContainer { { RadioResourceStatusNR-U-ExtIEs} } OPTIONAL, + ... +} + +RadioResourceStatusNR-U-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +MIMO PRB Usage Information ::= SEQUENCE { + dl-GBR-PRB-usage-for-MIMO INTEGER (0..100), + ul-GBR-PRB-usage-for-MIMO INTEGER (0..100), + dl-non-GBR-PRB-usage-for-MIMO INTEGER (0..100), + ul-non-GBR-PRB-usage-for-MIMO INTEGER (0..100), + dl-Total-PRB-usage-for-MIMO INTEGER (0..100), + ul-Total-PRB-usage-for-MIMO INTEGER (0..100), + iE-Extensions ProtocolExtensionContainer { { MIMO PRB Usage Information-ExtIEs} } OPTIONAL, + ... +} + +MIMO PRB Usage Information-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +RAN feedback type ::= CHOICE { +``` + +``` +proactive RANfeedbacktype-proactive, +reactive RANfeedbacktype-reactive, +choice-extensions ProtocolIE-SingleContainer { {RANfeedbacktype-ExtIEs} } +} + +RANfeedbacktype-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +RANfeedbacktype-proactive ::= SEQUENCE { + burstArrivalTimeWindow BurstArrivalTimeWindow, + periodicityRange PeriodicityRange OPTIONAL, + iE-Extension ProtocolExtensionContainer { {RANfeedbacktype-proactive-ExtIEs} } OPTIONAL, + ... +} + +RANfeedbacktype-proactive-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +RANfeedbacktype-reactive ::= SEQUENCE { + capabilityForBATAdaptation ENUMERATED {true, ...}, + iE-Extension ProtocolExtensionContainer { {RANfeedbacktype-reactive-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +} + +RANfeedbacktype-reactive-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +RANTSSRequestType ::= ENUMERATED {start, stop, ...} + +RANTimingSynchronisationStatusInfo ::= SEQUENCE { + synchronisationstate ENUMERATED {locked, holdover, freeRun, ...} OPTIONAL, + traceabletoUTC ENUMERATED { true, false, ...} OPTIONAL, + traceabletoGNSS ENUMERATED { true, false, ...} OPTIONAL, + clockFrequencyStability BIT STRING (SIZE(16)) OPTIONAL, + clockAccuracy ClockAccuracy OPTIONAL, + parentTimeSource ParentTimeSource OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { RANTimingSynchronisationStatusInfo-ExtIEs} } OPTIONAL, + ... +} + +RANTimingSynchronisationStatusInfo-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +ClockAccuracy ::= CHOICE { +``` + +``` + clockAccuracyValue INTEGER (1..40000000, ...), + clockAccuracyIndex INTEGER (32..47, ...), + choice-Extensions ProtocolIE-SingleContainer { { ClockAccuracy-ExtIEs } } +} + +ClockAccuracy-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +RANAC ::= INTEGER (0..255) + +RAN-MeasurementID ::= INTEGER (1.. 65536, ...) + +RAN-UE-MeasurementID ::= INTEGER (1.. 256, ...) + +RAN-UE-PDC-MeasID ::= INTEGER (1..16, ...) + +RANUEID ::= OCTET STRING (SIZE (8)) + +RANUEPagingIdentity ::= SEQUENCE { + iRNTI BIT STRING (SIZE(40)), + iE-Extensions ProtocolExtensionContainer { { RANUEPagingIdentity-ExtIEs } } OPTIONAL +} + +RANUEPagingIdentity-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +RAT-FrequencyPriorityInformation ::= CHOICE { + eNDC SubscriberProfileIDforRFP, + nGRAN RAT-FrequencySelectionPriority, + choice-extension ProtocolIE-SingleContainer { { RAT-FrequencyPriorityInformation-ExtIEs} } +} + +RAT-FrequencyPriorityInformation-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +RAT-FrequencySelectionPriority ::= INTEGER (1.. 256, ...) + +RBSetConfiguration ::= SEQUENCE { + subcarrierSpacing SubcarrierSpacing, + rBSetSize RBSetSize, + nUmberRBsets INTEGER(1..maxnoofRBsetsPerCell), + iE-Extensions ProtocolExtensionContainer { { RBSetConfiguration-ExtIEs} } OPTIONAL +} + +RBSetConfiguration-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +} + +RBSetSize ::= ENUMERATED { rb2, rb4, rb8, rb16, rb32, rb64} + + +Re-routingEnableIndicator ::= ENUMERATED { + true, + false, + ... +} + +Recommended-SSBs-for-Paging-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF Recommended-SSBs-for-Paging-List-Item + +Recommended-SSBs-for-Paging-List-Item ::= SEQUENCE { + nGCGI NRCGI, + sSBs-forPaging-List SSBs-forPaging-List, + iE-Extensions ProtocolExtensionContainer { { Recommended-SSBs-for-Paging-List-Item-ExtIEs} } OPTIONAL +} + +Recommended-SSBs-for-Paging-List-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +Redcap-Bcast-Information ::= BIT STRING(SIZE(8)) + +RedCapIndication ::= ENUMERATED {true, ...} + +Reestablishment-Indication ::= ENUMERATED { +    reestablished, +    ... +} + +ReferencePoint ::= CHOICE { +    coordinateID                CoordinateID, +    referencePointCoordinate    AccessPointPosition, +    referencePointCoordinateHA    NGRANHighAccuracyAccessPointPosition, +    choice-Extension            ProtocolIE-SingleContainer { { ReferencePoint-ExtIEs } } +} + +ReferencePoint-ExtIEs FLAP-PROTOCOL-IES ::= { +    ... +} + +ReferenceSFN ::= INTEGER (0..1023) + +``` +ReferenceSignal ::= CHOICE { + nZP-CSI-RS NZP-CSI-RS-ResourceID, + sSB SSB, + sRS SRSResourceID, + positioningSRS SRSPosResourceID, + dL-PRS DL-PRS, + choice-extension ProtocolIE-SingleContainer {ReferenceSignal-ExtIEs } +} +``` + +``` +ReferenceSignal-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +RA-RNTI ::= INTEGER (0..65535, ...) +``` + +``` +ReferenceConfiguration ::= CHOICE { + rEQUESTforLowerLayerConfiguration RequestforLowerLayerConfiguration, + lTMReferenceConfiguration LTMReferenceConfiguration, + choice-extension ProtocolIE-SingleContainer { ReferenceConfiguration-ExtIEs } +} +``` + +``` +ReferenceConfiguration-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} +``` + +} + +``` +RelativeCartesianLocation ::= SEQUENCE { + xYZunit ENUMERATED {mm, cm, dm, ...}, + xvalue INTEGER (-65536..65535), + yvalue INTEGER (-65536..65535), + zvalue INTEGER (-32768..32767), + locationUncertainty LocationUncertainty, + iE-Extensions ProtocolExtensionContainer { { RelativeCartesianLocation-ExtIEs} } OPTIONAL +} +``` + +``` +RelativeCartesianLocation-ExtIEs FIAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +RelativeGeodeticLocation ::= SEQUENCE { + milli-Arc-SecondUnits ENUMERATED {zerodot03, zerodot3, three, ...}, + heightUnits ENUMERATED {mm, cm, m, ...}, + deltaLatitude INTEGER (-1024.. 1023), + deltaLongitude INTEGER (-1024.. 1023), + deltaHeight INTEGER (-1024.. 1023), + locationUncertainty LocationUncertainty, + iE-extensions ProtocolExtensionContainer {{RelativeGeodeticLocation-ExtIEs }} OPTIONAL +} +``` + +} + +RelativeGeodeticLocation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +RemoteUELocalID ::= INTEGER (0..255, ...) + +ReferenceTime ::= OCTET STRING + +RegistrationRequest ::= ENUMERATED{start, stop, add, ...} + +ReportCharacteristics ::= BIT STRING (SIZE(32)) + +ReportingPeriodicity ::= ENUMERATED{ms500, ms1000, ms2000, ms5000, ms10000, ...} + +RequestedBandCombinationIndex ::= OCTET STRING + +RequestedFeatureSetEntryIndex ::= OCTET STRING + +RequestedP-MaxFR2 ::= OCTET STRING + +Requested-PDCCH-BlindDetectionSCG ::= OCTET STRING + +``` +RequestedSRSTransmissionCharacteristics ::= SEQUENCE { + numberOfTransmissions INTEGER (0..500, ...) OPTIONAL, + -- The IE shall be present if the Resource Type IE is set to "periodic" -- + resourceType ENUMERATED {periodic, semi-persistent, aperiodic,...}, + bandwidthSRS BandwidthSRS, + sRSResourceSetList SRSResourceSetList OPTIONAL, + sSBInformation SSBInformation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { RequestedSRSTransmissionCharacteristics-ExtIEs} } OPTIONAL +} +``` + +``` +RequestedSRSTransmissionCharacteristics-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-SrsFrequency CRITICALITY ignore EXTENSION SrsFrequency PRESENCE optional }, + ... +} +``` + +``` +RequestType ::= ENUMERATED {offer, execution, ...} +``` + +``` +ResourceCoordinationEUTRACellInfo ::= SEQUENCE { + eUTRA-Mode-Info EUTRA-Coex-Mode-Info, + eUTRA-PRACH-Configuration EUTRA-PRACH-Configuration, + iE-Extensions ProtocolExtensionContainer { { ResourceCoordinationEUTRACellInfo-ExtIEs } } OPTIONAL, +``` + +``` + ... +} + +ResourceCoordinationEUTRACellInfo-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + {ID id-IgnorePRACHConfiguration CRITICALITY reject EXTENSION IgnorePRACHConfiguration PRESENCE optional }, + ... +} + +ResourceCoordinationTransferInformation ::= SEQUENCE { + meNB-Cell-ID EUTRA-Cell-ID, + resourceCoordinationEUTRACellInfo ResourceCoordinationEUTRACellInfo OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { ResourceCoordinationTransferInformation-ExtIEs } } OPTIONAL, + ... +} + +ResourceCoordinationTransferInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +ResourceCoordinationTransferContainer ::= OCTET STRING + +ResourceSetType ::= CHOICE { + periodic ResourceSetTypePeriodic, + semi-persistent ResourceSetTypeSemi-persistent, +``` + +``` +aperiodic ResourceSetTypeAperiodic, +choice-extension ProtocolIE-SingleContainer {{ ResourceSetType-ExtIEs }} +} + +ResourceSetType-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +ResourceSetTypePeriodic ::= SEQUENCE { + periodicSet ENUMERATED{true, ...}, + iE-Extensions ProtocolExtensionContainer { { ResourceSetTypePeriodic-ExtIEs} } OPTIONAL +} + +ResourceSetTypePeriodic-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +ResourceSetTypeSemi-persistent ::= SEQUENCE { + semi-persistentSet ENUMERATED{true, ...}, + iE-Extensions ProtocolExtensionContainer { { ResourceSetTypeSemi-persistent-ExtIEs} } OPTIONAL +} + +ResourceSetTypeSemi-persistent-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +} + +ResourceSetTypeAperiodic ::= SEQUENCE { + sRSResourceTrigger-List INTEGER(1..3), + slotoffset INTEGER(0..32), + iE-Extensions ProtocolExtensionContainer { { ResourceSetTypeAperiodic-ExtIEs} } OPTIONAL +} + +ResourceSetTypeAperiodic-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +RepetitionFactorExtended ::= ENUMERATED {n3, n5, n6, n7, n8, n10, n12, n14, ...} + +RepetitionPeriod ::= INTEGER (0..131071, ...) + +ReportingRequestType ::= SEQUENCE { + eventType EventType, + reportingPeriodicityValue ReportingPeriodicityValue OPTIONAL, + -- C-ifEventTypeisPeriodic: This IE shall be present if the Event Type IE is set to "periodic" in the Event Type IE. + iE-Extensions ProtocolExtensionContainer { {ReportingRequestType-ExtIEs} } OPTIONAL +} + +ReportingRequestType-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +} + +ResourceType ::= CHOICE { + periodic ResourceTypePeriodic, + semi-persistent ResourceTypeSemi-persistent, + aperiodic ResourceTypeAperiodic, + choice-extension ProtocolIE-SingleContainer {{ ResourceType-ExtIEs }} +} + +ResourceType-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +ResourceTypePeriodic ::= SEQUENCE { + periodicity ENUMERATED{slot1, slot2, slot4, slot5, slot8, slot10, slot16, slot20, slot32, slot40, slot64, slot80, slot160, slot320, + slot640, slot1280, slot2560, ...}, + offset INTEGER(0..2559, ...), + iE-Extensions ProtocolExtensionContainer {{ ResourceTypePeriodic-ExtIEs} } OPTIONAL +} + +ResourceTypePeriodic-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +ResourceTypeSemi-persistent ::= SEQUENCE { +``` + +``` +periodicity ENUMERATED{slot1, slot2, slot4, slot5, slot8, slot10, slot16, slot20, slot32, slot40, slot64, slot80, slot160, slot320, +slot640, slot1280, slot2560, ...}, +``` + +``` +offset INTEGER(0..2559, ...), +``` + +``` +iE-Extensions ProtocolExtensionContainer { { ResourceTypeSemi-persistent-ExtIEs} } OPTIONAL +``` + +``` +} +``` + +``` +ResourceTypeSemi-persistent-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` +... +``` + +``` +} +``` + +``` +ResourceTypeAperiodic ::= SEQUENCE { +``` + +``` +aperiodicResourceType ENUMERATED{true, ...}, +``` + +``` +iE-Extensions ProtocolExtensionContainer { { ResourceTypeAperiodic-ExtIEs} } OPTIONAL +``` + +``` +} +``` + +``` +ResourceTypeAperiodic-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` +... +``` + +``` +} +``` + +``` +ResourceTypePos ::= CHOICE { +``` + +``` +periodic ResourceTypePeriodicPos, +``` + +``` +semi-persistent ResourceTypeSemi-persistentPos, +``` + +``` +aperiodic ResourceTypeAperiodicPos, +``` + +``` +choice-extension ProtocolIE-SingleContainer {{ ResourceTypePos-ExtIEs }} +``` + +``` +} +``` + +ResourceTypePos-ExtIEs FLAP-PROTOCOL-IES ::= { + +... + +} + +ResourceTypePeriodicPos ::= SEQUENCE { + +periodicity            ENUMERATED{slot1, slot2, slot4, slot5, slot8, slot10, slot16, slot20, slot32, slot40, slot64, slot80, slot160, slot320, slot640, slot1280, slot2560, slot5120, slot10240, slot40960, slot81920, ..., slot128, slot256, slot512, slot20480}, + +offset                INTEGER(0..81919, ...), + +iE-Extensions        ProtocolExtensionContainer { { ResourceTypePeriodicPos-ExtIEs} }    OPTIONAL + +} + +ResourceTypePeriodicPos-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +ResourceTypeSemi-persistentPos ::= SEQUENCE { + +periodicity            ENUMERATED{slot1, slot2, slot4, slot5, slot8, slot10, slot16, slot20, slot32, slot40, slot64, slot80, slot160, slot320, slot640, slot1280, slot2560, slot5120, slot10240, slot40960, slot81920, ..., slot128, slot256, slot512, slot20480}, + +offset                INTEGER(0..81919, ...), + +iE-Extensions        ProtocolExtensionContainer { { ResourceTypeSemi-persistentPos-ExtIEs} } OPTIONAL + +} + +ResourceTypeSemi-persistentPos-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +``` +} + +ResourceTypeAperiodicPos ::= SEQUENCE { + slotOffset INTEGER (0..32), + iE-Extensions ProtocolExtensionContainer { { ResourceTypeAperiodicPos-ExtIEs} } OPTIONAL +} + +ResourceTypeAperiodicPos-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +RLCDuplicationInformation ::= SEQUENCE { + rLCDuplicationStateList RLCDuplicationStateList, + primaryPathIndication PrimaryPathIndication OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {RLCDuplicationInformation-ExtIEs} } OPTIONAL +} + +RLCDuplicationInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +RLCDuplicationStateList ::= SEQUENCE (SIZE(1..maxnoofRLCDuplicationState)) OF RLCDuplicationState-Item + +RLCDuplicationState-Item ::=SEQUENCE { +``` + +``` + duplicationState DuplicationState, + iE-Extensions ProtocolExtensionContainer { {RLCDuplicationState-Item-ExtIEs} } OPTIONAL, + ... +} + +RLCDuplicationState-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +RLCFailureIndication ::= SEQUENCE { + associatedLCID LCID, + iE-Extensions ProtocolExtensionContainer { {RLCFailureIndication-ExtIEs} } OPTIONAL +} + +RLCFailureIndication-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +RLCMode ::= ENUMERATED { + rlc-am, + rlc-um-bidirectional, + rlc-um-unidirectional-ul, + rlc-um-unidirectional-dl, +``` + +``` + ... +} + +RLC-Status ::= SEQUENCE { + reestablishment-Indication Reestablishment-Indication, + iE-Extensions ProtocolExtensionContainer { { RLC-Status-ExtIEs } } OPTIONAL, + ... +} + +RLC-Status-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +RLFReportInformationList ::= SEQUENCE (SIZE(1.. maxnoofRLFReports)) OF RLFReportInformationItem + +RLFReportInformationItem ::= SEQUENCE { + nRUELFReportContainer NRUELFReportContainer, + uEAassistantIdentifier GNB-DU-UE-FLAP-ID OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { RLFReportInformationItem-ExtIEs } } OPTIONAL, + ... +} + +RLFReportInformationItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +} + +RIMRSDetectionStatus ::= ENUMERATED {rs-detected, rs-disappeared, ...} + +RRContainer ::= OCTET STRING + +RRContainer-RRSetupComplete ::= OCTET STRING + +``` +RRCDeliveryStatus ::= SEQUENCE { + delivery-status PDCP-SN, + triggering-message PDCP-SN, + iE-Extensions ProtocolExtensionContainer { { RRCDeliveryStatus-ExtIEs } } OPTIONAL} +``` + +``` +RRCDeliveryStatus-ExtIEs FIAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +RRCDeliveryStatusRequest ::= ENUMERATED {true, ...} + +``` +RRReconfigurationCompleteIndicator ::= ENUMERATED { + true, + ... + failure +``` + +``` + } + + RRC-Terminating-IAB-Donor-Related-Info ::= SEQUENCE { + rRC-TerminatingIAB-Donor-gNB-ID GlobalGNB-ID, + mobileIAB-MT-BAP-Address BAPAddress, + iE-Extensions ProtocolExtensionContainer { { RRC-Terminating-IAB-Donor-Related-Info-ExtIEs} } OPTIONAL, + ... + } + + RRC-Terminating-IAB-Donor-Related-Info-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... + } + + RRC-Version ::= SEQUENCE { + latest-RRC-Version BIT STRING (SIZE(3)), + iE-Extensions ProtocolExtensionContainer { { RRC-Version-ExtIEs } } OPTIONAL} + + RRC-Version-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + {ID id-latest-RRC-Version-Enhanced CRITICALITY ignore EXTENSION OCTET STRING (SIZE(3)) PRESENCE optional }, + ... + } + + RoutingID ::= OCTET STRING +``` + +``` +ResponseTime ::= SEQUENCE { + time INTEGER (1..128,...), + timeUnit ENUMERATED {second, ten-seconds, ten-milliseconds,...}, + iE-Extensions ProtocolExtensionContainer { { ResponseTime-ExtIEs} } OPTIONAL, + ... +} + +ResponseTime-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +RACHConfiguration ::= OCTET STRING + +RequestforRACHConfiguration ::= ENUMERATED {true, ...} + +RequestforLowerLayerConfiguration ::= ENUMERATED {true, ...} + +RxTxTimingErrorMargin ::= ENUMERATED {tc0dot5, tc1, tc2, tc4, tc8, tc12, tc16, tc20, tc24, tc32, tc40, tc48, tc64, tc80, tc96, tc128, ...} + +-- S +``` + +``` +SCell-FailedtoSetup-Item ::= SEQUENCE { + sCell-ID NRCGI , + cause Cause OPTIONAL , + iE-Extensions ProtocolExtensionContainer { { SCell-FailedtoSetup-ItemExtIEs } } OPTIONAL, + ... +} + +SCell-FailedtoSetup-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SCell-FailedtoSetupMod-Item ::= SEQUENCE { + sCell-ID NRCGI , + cause Cause OPTIONAL , + iE-Extensions ProtocolExtensionContainer { { SCell-FailedtoSetupMod-ItemExtIEs } } OPTIONAL, + ... +} + +SCell-FailedtoSetupMod-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SCell-ToBeRemoved-Item ::= SEQUENCE { + sCell-ID NRCGI , +``` + +``` + iE-Extensions ProtocolExtensionContainer { { SCell-ToBeRemoved-ItemExtIEs } } OPTIONAL, + ... +} + +SCell-ToBeRemoved-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SCell-ToBeSetup-Item ::= SEQUENCE { + sCell-ID NRCGI , + sCellIndex SCellIndex, + sCellULConfigured CellULConfigured OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SCell-ToBeSetup-ItemExtIEs } } OPTIONAL, + ... +} + +SCell-ToBeSetup-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-ServingCellMO CRITICALITY ignore EXTENSION ServingCellMO PRESENCE optional }, + ... +} + +SCell-ToBeSetupMod-Item ::= SEQUENCE { + sCell-ID NRCGI , + sCellIndex SCellIndex, +``` + +``` +sCellULConfigured CellULConfigured OPTIONAL, +iE-Extensions ProtocolExtensionContainer { { SCell-ToBeSetupMod-ItemExtIEs } } OPTIONAL, +... +} + +SCell-ToBeSetupMod-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-ServingCellMO CRITICALITY ignore EXTENSION ServingCellMO PRESENCE optional }, + ... +} + +SCellIndex ::=INTEGER (1..31, ...) + +SCGActivationRequest ::= ENUMERATED {activate-scg, deactivate-scg, ...} + +SCGActivationStatus ::= ENUMERATED {scg-activated, scg-deactivated, ...} + +SCGIndicator ::= ENUMERATED{released, ...} + +SCS-480 ::= INTEGER(0..319) + +SCS-960 ::= INTEGER(0..639) + +SCS-SpecificCarrier ::= SEQUENCE { + offsetToCarrier INTEGER (0..2199,...), +``` + +``` + subcarrierSpacing ENUMERATED {kHz15, kHz30, kHz60, kHz120, ..., kHz480, kHz960}, + carrierBandwidth INTEGER (1..275,...), + iE-Extensions ProtocolExtensionContainer { { SCS-SpecificCarrier-ExtIEs } } OPTIONAL +} + +SCS-SpecificCarrier-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SDTBearerConfigurationQueryIndication ::= ENUMERATED {true, ...} + +SDTBearerConfigurationInfo ::= SEQUENCE { + sDTBearerConfig-List SDTBearerConfig-List, + iE-Extensions ProtocolExtensionContainer { { SDTBearerConfigurationInfo-ExtIEs } } OPTIONAL +} + +SDTBearerConfigurationInfo-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SDTBearerConfig-List ::= SEQUENCE (SIZE(1..maxnoofSDTBearers)) OF SDTBearerConfig-List-Item + +SDTBearerConfig-List-Item ::= SEQUENCE{ + sDTBearerType SDTBearerType, +``` + +``` + sDTRLCBearerConfiguration sDTRLCBearerConfiguration, + iE-Extensions ProtocolExtensionContainer {{ SDTBearerConfig-List-Item-ExtIEs}} OPTIONAL +} + +SDTBearerConfig-List-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SDTBearerType ::= CHOICE { + sRB SRBID, + dRB DRBID, + choice-extension ProtocolIE-SingleContainer {{ SDTBearerType-ExtIEs }} +} + +SDTBearerType-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +SDT-MAC-PHY-CG-Config ::= OCTET STRING + +SDTInformation ::= SEQUENCE { + sdtIndicator ENUMERATED {true,...}, + sdtAssistantInformation ENUMERATED {singlepacket, multiplepackets,...} OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SDTInformation-ExtIEs } } OPTIONAL +} +``` + +``` +} + +SDTInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SDTRLCBearerConfiguration ::= OCTET STRING + +SDT-Termination-Request ::= ENUMERATED {radio-link-problem, normal, ..., sdt-volume-threshold-crossed} + +SDT-Volume-Threshold ::= INTEGER(1.. 192000,...) + +Search-window-information ::= SEQUENCE { + expectedPropagationDelay INTEGER (-3841..3841,...), + delayUncertainty INTEGER (1..246,...), + iE-Extensions ProtocolExtensionContainer { { Search-window-information-ExtIEs } } OPTIONAL +} + +Search-window-information-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SerialNumber ::= BIT STRING (SIZE (16)) +``` + +SIBType-PWS ::= INTEGER (6..8, ...) + +SelectedBandCombinationIndex ::= OCTET STRING + +SelectedFeatureSetEntryIndex ::= OCTET STRING + +CG-ConfigInfo ::= OCTET STRING + +ServCellInfoList ::= OCTET STRING + +ServCellIndex ::= INTEGER (0..31, ...) + +ServingCellMO ::= INTEGER (1..64, ...) + +ServingCellMO-List-Item ::= SEQUENCE { + servingCellMO ServingCellMO, + sSB-Frequency INTEGER (0..3279165), + iE-Extensions ProtocolExtensionContainer { { ServingCellMO-List-Item-ExtIEs } } OPTIONAL +} + +ServingCellMO-List-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +ServingCellMO-encoded-in-CGC-List ::= SEQUENCE (SIZE(1.. maxNrofBWPs)) OF ServingCellMO-encoded-in-CGC-Item + +ServingCellMO-encoded-in-CGC-Item ::= SEQUENCE { +    servingCellMO                  ServingCellMO, +    iE-Extensions                ProtocolExtensionContainer { { ServingCellMO-encoded-in-CGC-Item-ExtIEs } } OPTIONAL, +    ... +} + +ServingCellMO-encoded-in-CGC-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    { ID id-BWP-Id CRITICALITY ignore EXTENSION BWP-Id PRESENCE optional }, +    ... +} + +Served-Cell-Information ::= SEQUENCE { +    nRCGI                          NRCGI, +    nRPCI                          NRPCI, +    fiveGS-TAC                   FiveGS-TAC          OPTIONAL, +    configured-EPS-TAC          Configured-EPS-TAC      OPTIONAL, +    servedPLMNs                  ServedPLMNs-List, +    nR-Mode-Info                NR-Mode-Info, +    measurementTimingConfiguration OCTET STRING, +    iE-Extensions                ProtocolExtensionContainer { { Served-Cell-Information-ExtIEs } } OPTIONAL, +    ... +} + +``` + +Served-Cell-Information-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-RANAC CRITICALITY ignore EXTENSION RANAC PRESENCE optional }| + { ID id-ExtendedServedPLMNs-List CRITICALITY ignore EXTENSION ExtendedServedPLMNs-List PRESENCE optional }| + { ID id-Cell-Direction CRITICALITY ignore EXTENSION Cell-Direction PRESENCE optional }| + { ID id-BPLMN-ID-Info-List CRITICALITY ignore EXTENSION BPLMN-ID-Info-List PRESENCE optional }| + { ID id-Cell-Type CRITICALITY ignore EXTENSION CellType PRESENCE optional}| + { ID id-ConfiguredTACIndication CRITICALITY ignore EXTENSION ConfiguredTACIndication PRESENCE optional }| + { ID id-AggressorgNBSetID CRITICALITY ignore EXTENSION AggressorgNBSetID PRESENCE optional}| + { ID id-VictimgNBSetID CRITICALITY ignore EXTENSION VictimgNBSetID PRESENCE optional}| + { ID id-IAB-Info-IAB-DU CRITICALITY ignore EXTENSION IAB-Info-IAB-DU PRESENCE optional}| + { ID id-SSB-PositionsInBurst CRITICALITY ignore EXTENSION SSB-PositionsInBurst PRESENCE optional }| + { ID id-NRPRACHConfig CRITICALITY ignore EXTENSION NRPRACHConfig PRESENCE optional }| + { ID id-SFN-Offset CRITICALITY ignore EXTENSION SFN-Offset PRESENCE optional }| + { ID id-NPNBroadcastInformation CRITICALITY reject EXTENSION NPNBroadcastInformation PRESENCE optional }| + { ID id-Supported-MBS-FSA-ID-List CRITICALITY ignore EXTENSION Supported-MBS-FSA-ID-List PRESENCE optional }| + { ID id-Redcap-Bcast-Information CRITICALITY ignore EXTENSION Redcap-Bcast-Information PRESENCE optional }| + { ID id-ERedcap-Bcast-Information CRITICALITY ignore EXTENSION ERedcap-Bcast-Information PRESENCE optional } + , + ... +} + +``` + +``` + +Serving-Cells-List ::= SEQUENCE (SIZE(1..maxnoofServingCells)) OF Serving-Cells-List-Item + +``` + +``` +Serving-Cells-List-Item ::= SEQUENCE{ + nRCGI NRCGI, + iAB-MT-Cell-NA-Resource-Configuration-Mode-Info IAB-MT-Cell-NA-Resource-Configuration-Mode-Info OPTIONAL, + iE-Extensions ProtocolExtensionContainer {{Serving-Cells-List-Item-ExtIEs}} OPTIONAL +} + +Serving-Cells-List-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +Supported-MBS-FSA-ID-List ::= SEQUENCE (SIZE(1.. maxnoofMBSFSAs)) OF MBS-FrequencySelectionArea-Identity + +MBS-FrequencySelectionArea-Identity ::= OCTET STRING (SIZE(3)) + +SFN-Offset ::= SEQUENCE { + sFN-Time-Offset BIT STRING (SIZE(24)), + iE-Extensions ProtocolExtensionContainer { {SFN-Offset-ExtIEs} } OPTIONAL, + ... +} + +SFN-Offset-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +Served-Cells-To-Add-Item ::= SEQUENCE { + served-Cell-Information Served-Cell-Information, + gNB-DU-System-Information GNB-DU-System-Information OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Served-Cells-To-Add-ItemExtIEs } } OPTIONAL, + ... +} + +Served-Cells-To-Add-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +Served-Cells-To-Delete-Item ::= SEQUENCE { + oldNRCGI NRCGI , + iE-Extensions ProtocolExtensionContainer { { Served-Cells-To-Delete-ItemExtIEs } } OPTIONAL, + ... +} + +Served-Cells-To-Delete-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +Served-Cells-To-Modify-Item ::= SEQUENCE { + oldNRCGI NRCGI , + served-Cell-Information Served-Cell-Information , +``` + +``` +gNB-DU-System-Information GNB-DU-System-Information OPTIONAL , +iE-Extensions ProtocolExtensionContainer { { Served-Cells-To-Modify-ItemExtIEs } } OPTIONAL, +... +} + +Served-Cells-To-Modify-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +Served-EUTRA-Cells-Information ::= SEQUENCE { + eUTRA-Mode-Info EUTRA-Mode-Info, + protectedEUTRAResourceIndication ProtectedEUTRAResourceIndication, + iE-Extensions ProtocolExtensionContainer { {Served-EUTRA-Cell-Information-ExtIEs} } OPTIONAL, + ... +} + +Served-EUTRA-Cell-Information-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +Service-State ::= ENUMERATED { + in-service, + out-of-service, + ... +} +``` + +} + +Service-Status ::= SEQUENCE { + +    service-state              Service-State, +    switchingOffOngoing      ENUMERATED {true, ...} OPTIONAL, +    iE-Extensions          ProtocolExtensionContainer { { Service-Status-ExtIEs } } OPTIONAL, +    ... +} + +Service-Status-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +    ... +} + +RelativeTime1900 ::= BIT STRING (SIZE (64)) + +ShortDRXCycleLength ::= ENUMERATED {ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30, ms32, ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640, ...} + +ShortDRXCycleTimer ::= INTEGER (1..16) + +SIB1-message ::= OCTET STRING + +SIB10-message ::= OCTET STRING + +SIB12-message ::= OCTET STRING + +SIB13-message ::= OCTET STRING + +SIB14-message ::= OCTET STRING + +SIB15-message ::= OCTET STRING + +SIB17-message ::= OCTET STRING + +SIB20-message ::= OCTET STRING + +SIBX-message ::= OCTET STRING + +SItype ::= INTEGER (1..32, ...) + +SItype-List ::= SEQUENCE (SIZE(1.. maxnoofSItypes)) OF SItype-Item + +SItype-Item ::= SEQUENCE { +    sSItype        SItype , +    iE-Extensions    ProtocolExtensionContainer { { SItype-ItemExtIEs } }    OPTIONAL +} + +SItype-ItemExtIEs    FLAP-PROTOCOL-EXTENSION ::= { + +``` + ... +} + +SibtypetobeupdatedListItem ::= SEQUENCE { + sIBtype INTEGER (2..32,...), + sIBmessage OCTET STRING, + valueTag INTEGER (0..31,...), + iE-Extensions ProtocolExtensionContainer { { SibtypetobeupdatedListItem-ExtIEs } } OPTIONAL, + ... +} + +SibtypetobeupdatedListItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + {ID id-areaScope CRITICALITY ignore EXTENSION AreaScope PRESENCE optional}, + ... +} + +SidelinkRelayConfiguration ::= SEQUENCE { + gNB-DU-UE-FlAPIDofRelayUE GNB-DU-UE-FlAP-ID, + remoteUELocalID RemoteUELocalID, + sidelinkConfigurationContainer SidelinkConfigurationContainer OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SidelinkRelayConfiguration-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +SidelinkRelayConfiguration-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +SidelinkConfigurationContainer ::= OCTET STRING +``` + +``` +SLDRBID ::= INTEGER (1..512, ...) +``` + +``` +SLDRBInformation ::= SEQUENCE { +``` + +``` + sLDRB-QoS PC5QoSParameters, +``` + +``` + flowsMappedToSLDRB-List FlowsMappedToSLDRB-List, +``` + +``` + ... +``` + +``` +} +``` + +``` +SLDRBs-FailedToBeModified-Item ::= SEQUENCE { +``` + +``` + sLDRBID SLDRBID , +``` + +``` + cause Cause OPTIONAL, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { SLDRBs-FailedToBeModified-ItemExtIEs } } OPTIONAL +``` + +``` +} +``` + +``` +SLDRBs-FailedToBeModified-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +SLDRBs-FailedToBeSetup-Item ::= SEQUENCE { + sLDRBID SLDRBID, + cause Cause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SLDRBs-FailedToBeSetup-ItemExtIEs } } OPTIONAL +} + +SLDRBs-FailedToBeSetup-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SLDRBs-FailedToBeSetupMod-Item ::= SEQUENCE { + sLDRBID SLDRBID , + cause Cause OPTIONAL , + iE-Extensions ProtocolExtensionContainer { { SLDRBs-FailedToBeSetupMod-ItemExtIEs } } OPTIONAL +} + +SLDRBs-FailedToBeSetupMod-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SLDRBs-Modified-Item ::= SEQUENCE { + sLDRBID SLDRBID, + iE-Extensions ProtocolExtensionContainer { { SLDRBs-Modified-ItemExtIEs } } OPTIONAL +} +``` + +``` +} +``` + +``` +SLDRBs-Modified-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +SLDRBs-ModifiedConf-Item ::= SEQUENCE { +``` + +``` + sLDRBID SLDRBID, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { SLDRBs-ModifiedConf-ItemExtIEs } } OPTIONAL +``` + +``` +} +``` + +``` +SLDRBs-ModifiedConf-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +SLDRBs-Required-ToBeModified-Item ::= SEQUENCE { +``` + +``` + sLDRBID SLDRBID, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { SLDRBs-Required-ToBeModified-ItemExtIEs } } OPTIONAL +``` + +``` +} +``` + +``` +SLDRBs-Required-ToBeModified-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +SLDRBs-Required-ToBeReleased-Item ::= SEQUENCE { + sLDRBID sLDRBID, + iE-Extensions ProtocolExtensionContainer { { SLDRBs-Required-ToBeReleased-ItemExtIEs } } OPTIONAL +} +``` + +``` +SLDRBs-Required-ToBeReleased-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SLDRBs-Setup-Item ::= SEQUENCE { + sLDRBID sLDRBID, + iE-Extensions ProtocolExtensionContainer { { SLDRBs-Setup-ItemExtIEs } } OPTIONAL +} +``` + +``` +SLDRBs-Setup-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SLDRBs-SetupMod-Item ::= SEQUENCE { + sLDRBID sLDRBID, + iE-Extensions ProtocolExtensionContainer { { SLDRBs-SetupMod-ItemExtIEs } } OPTIONAL +} +``` + +``` +SLDRBs-SetupMod-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +SLDRBs-ToBeModified-Item ::= SEQUENCE { + sLDRBID sLDRBID, + sLDRBInformation sLDRBInformation OPTIONAL, + rLCMode rLCMode OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SLDRBs-ToBeModified-ItemExtIEs } } OPTIONAL +} + +SLDRBs-ToBeModified-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + {ID id-duplicationIndication CRITICALITY ignore EXTENSION DuplicationIndication PRESENCE optional}, + ... +} + +SLDRBs-ToBeReleased-Item ::= SEQUENCE { + sLDRBID sLDRBID, + iE-Extensions ProtocolExtensionContainer { { SLDRBs-ToBeReleased-ItemExtIEs } } OPTIONAL +} + +SLDRBs-ToBeReleased-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SLDRBs-ToBeSetup-Item ::= SEQUENCE { + sLDRBID sLDRBID, + sLDRBInformation sLDRBInformation, + rLCMode RLCMode, + + iE-Extensions ProtocolExtensionContainer { { SLDRBs-ToBeSetup-ItemExtIEs } } OPTIONAL +} + +SLDRBs-ToBeSetup-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + {ID id-duplicationIndication CRITICALITY ignore EXTENSION DuplicationIndication PRESENCE optional}, + ... +} + +SLDRBs-ToBeSetupMod-Item ::= SEQUENCE { + sLDRBID sLDRBID, + sLDRBInformation sLDRBInformation, + rLCMode RLCMode OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SLDRBs-ToBeSetupMod-ItemExtIEs } } OPTIONAL +} + +SLDRBs-ToBeSetupMod-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + {ID id-duplicationIndication CRITICALITY ignore EXTENSION DuplicationIndication PRESENCE optional}, + ... +} +``` + +SLDRXCycleList ::= SEQUENCE (SIZE(1.. maxnoofSLdestinations)) OF SLDRXCycleItem + +SLDRXCycleItem ::= SEQUENCE { + +    rXUEID                  BIT STRING (SIZE(24)), + +    sLD RXInformation      SLDRXInformation, + +    iE-Extensions          ProtocolExtensionContainer { { SLDRXCycleItem-ExtIEs } } OPTIONAL, + +    ... + +} + +SLDRXCycleItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +    ... + +} + +SLDRXInformation ::= CHOICE { + +    sLD RXCycle          SLDRXCycleLength, + +    nosLD RX           SLDRXConfigurationIndicator, + +    choice-extension   ProtocolIE-SingleContainer { { SLDRXInformation-ExtIEs } } + +} + +SLDRXCycleLength ::= ENUMERATED{ms10, ms20, ms32, ms40, ms60, ms64, ms70, ms80, ms128, ms160, ms256, ms320, ms512, ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240, ...} + +SLDRXConfigurationIndicator ::= ENUMERATED{ release, ...} + +``` +SLDRXInformation-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +SL-PHY-MAC-RLC-Config ::= OCTET STRING + +SL-RLC-ChannelToAddModList ::= OCTET STRING + +SL-ConfigDedicatedEUTRA-Info ::= OCTET STRING + +SliceAvailableCapacity ::= SEQUENCE { + sliceAvailableCapacityList SliceAvailableCapacityList, + iE-Extensions ProtocolExtensionContainer { { SliceAvailableCapacity-ExtIEs} } OPTIONAL +} + +SliceAvailableCapacity-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SliceAvailableCapacityList ::= SEQUENCE (SIZE(1.. maxnoofBPLMNsNR)) OF SliceAvailableCapacityItem + +SliceAvailableCapacityItem ::= SEQUENCE { + pLMNIdentity PLMN-Identity, + sNSSAIAvailableCapacity-List SNSSAIAvailableCapacity-List, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { SliceAvailableCapacityItem-ExtIEs} } OPTIONAL +} + +SliceAvailableCapacityItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SNSSAIAvailableCapacity-List ::= SEQUENCE (SIZE(1.. maxnoofSliceItems)) OF SNSSAIAvailableCapacity-Item + +SNSSAIAvailableCapacity-Item ::= SEQUENCE { + sNSSAI SNSSAI, + sliceAvailableCapacityValueDownlink INTEGER (0..100) OPTIONAL, + sliceAvailableCapacityValueUplink INTEGER (0..100) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SNSSAIAvailableCapacity-Item-ExtIEs } } OPTIONAL +} + +SNSSAIAvailableCapacity-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SliceRadioResourceStatus ::= SEQUENCE { + sliceRadioResourceStatus SliceRadioResourceStatus-List, + iE-Extensions ProtocolExtensionContainer { { SliceRadioResourceStatus-ExtIEs} } OPTIONAL +} +``` + +``` +SliceRadioResourceStatus-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SliceRadioResourceStatus-List ::= SEQUENCE (SIZE(1..maxnoofBPLMNsNR)) OF SliceRadioResourceStatus-Item + +SliceRadioResourceStatus-Item ::= SEQUENCE { + pLMNIdentity PLMN-Identity, + sNSSAIRadioResourceStatus-List SNSSAIRadioResourceStatus-List, + iE-Extensions ProtocolExtensionContainer { { SliceRadioResourceStatus-Item-ExtIEs} } OPTIONAL +} + +SliceRadioResourceStatus-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SNSSAIRadioResourceStatus-List ::= SEQUENCE (SIZE(1.. maxnoofSliceItems)) OF SNSSAIRadioResourceStatus-Item + +SNSSAIRadioResourceStatus-Item ::= SEQUENCE { + sNSSAI SNSSAI, + sNSSAIIdlGBRPRBusage INTEGER (0..100), + sNSSAIulGBRPRBusage INTEGER (0..100), +} +``` + +``` + sNSSAIIdlNonGBRPRBusage INTEGER (0..100), + sNSSAIulNonGBRPRBusage INTEGER (0..100), + sNSSAIIdlTotalPRBallocation INTEGER (0..100), + sNSSAIulTotalPRBallocation INTEGER (0..100), + iE-Extensions ProtocolExtensionContainer { { SNSSAIRadioResourceStatus-Item-ExtIEs } } OPTIONAL +} + +SNSSAIRadioResourceStatus-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SliceSupportList ::= SEQUENCE (SIZE(1.. maxnoofSliceItems)) OF SliceSupportItem + +SliceSupportItem ::= SEQUENCE { + sNSSAI SNSSAI, + iE-Extensions ProtocolExtensionContainer { { SliceSupportItem-ExtIEs } } OPTIONAL +} + +SliceSupportItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SliceToReportList ::= SEQUENCE (SIZE(1.. maxnoofBPLMNsNR)) OF SliceToReportItem +``` + +``` +SliceToReportItem ::= SEQUENCE { + pLMNIdentity PLMN-Identity, + sNSSAIlist SNSSAI-list, + iE-Extensions ProtocolExtensionContainer { { SliceToReportItem-ExtIEs } } OPTIONAL +} +``` + +``` +SliceToReportItem-ExtIEs FIAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SlotNumber ::= INTEGER (0..79) +``` + +``` +SNSSAI-list ::= SEQUENCE (SIZE(1.. maxnoofSliceItems)) OF SNSSAI-Item +``` + +``` +SNSSAI-Item ::= SEQUENCE { + sNSSAI SNSSAI, + iE-Extensions ProtocolExtensionContainer { { SNSSAI-Item-ExtIEs } } OPTIONAL +} +``` + +``` +SNSSAI-Item-ExtIEs FIAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +Slot-Configuration-List ::= SEQUENCE (SIZE(1.. maxnoofslots)) OF Slot-Configuration-Item +``` + +``` +Slot-Configuration-Item ::= SEQUENCE { + slotIndex INTEGER (0..5119, ...), + symbolAllocInSlot SymbolAllocInSlot, + iE-Extensions ProtocolExtensionContainer { { Slot-Configuration-ItemExtIEs } } OPTIONAL +} +``` + +``` +Slot-Configuration-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SNSSAI ::= SEQUENCE { + sST OCTET STRING (SIZE(1)), + sD OCTET STRING (SIZE(3)) OPTIONAL , + iE-Extensions ProtocolExtensionContainer { { SNSSAI-ExtIEs } } OPTIONAL +} +``` + +``` +SNSSAI-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SpatialDirectionInformation ::= SEQUENCE { + nR-PRSBeamInformation NR-PRSBeamInformation, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { SpatialDirectionInformation-ExtIEs } } OPTIONAL +} +``` + +``` +SpatialDirectionInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SpatialRelationInfo ::= SEQUENCE { + spatialRelationforResourceID SpatialRelationforResourceID, + iE-Extensions ProtocolExtensionContainer { {SpatialRelationInfo-ExtIEs} } OPTIONAL +} +``` + +``` +SpatialRelationInfo-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SpatialRelationforResourceID ::= SEQUENCE (SIZE(1..maxnoofSpatialRelations)) OF SpatialRelationforResourceIDItem +``` + +``` +SpatialRelationforResourceIDItem ::= SEQUENCE { + referenceSignal ReferenceSignal, + iE-Extensions ProtocolExtensionContainer { {SpatialRelationforResourceIDItem-ExtIEs} } OPTIONAL +} +``` + +``` +SpatialRelationforResourceIDItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +SpatialRelationPerSRSResource ::= SEQUENCE { + spatialRelationPerSRSResource-List SpatialRelationPerSRSResource-List, + iE-Extensions ProtocolExtensionContainer { { SpatialRelationPerSRSResource-ExtIEs} } OPTIONAL, + ... +} + +SpatialRelationPerSRSResource-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SpatialRelationPerSRSResource-List ::= SEQUENCE (SIZE (1.. maxnoSRS-ResourcePerSet)) OF SpatialRelationPerSRSResourceItem + +SpatialRelationPerSRSResourceItem ::= SEQUENCE { + referenceSignal ReferenceSignal, + iE-Extensions ProtocolExtensionContainer { { SpatialRelationPerSRSResourceItem-ExtIEs} } OPTIONAL, + ... +} + +SpatialRelationPerSRSResourceItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SpatialRelationPos ::= CHOICE { + sSBPos SSB, + pRSInformationPos PRSInformationPos, + choice-extension ProtocolIE-SingleContainer {{ SpatialInformationPos-ExtIEs }} +} + +SpatialInformationPos-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +SpectrumSharingGroupID ::= INTEGER (1..maxCellineNB) + +SRBID ::= INTEGER (0..3, ...) + +SRBs-FailedToBeSetup-Item ::= SEQUENCE { + sRBID SRBID , + cause Cause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SRBs-FailedToBeSetup-ItemExtIEs } } OPTIONAL, + ... +} + +SRBs-FailedToBeSetup-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +} + +SRBs-FailedToBeSetupMod-Item ::= SEQUENCE { + +sRBID SRBID , + +cause Cause OPTIONAL, + +iE-Extensions ProtocolExtensionContainer { { SRBs-FailedToBeSetupMod-ItemExtIEs } } OPTIONAL, + +... + +} + +SRBs-FailedToBeSetupMod-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +SRBs-Modified-Item ::= SEQUENCE { + +sRBID SRBID, + +LCID LCID, + +iE-Extensions ProtocolExtensionContainer { { SRBs-Modified-ItemExtIEs } } OPTIONAL, + +... + +} + +SRBs-Modified-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +``` +SRBs-Required-ToBeReleased-Item ::= SEQUENCE { + sRBID sRBID, + iE-Extensions ProtocolExtensionContainer { { SRBs-Required-ToBeReleased-ItemExtIEs } } OPTIONAL, + ... +} +``` + +``` +SRBs-Required-ToBeReleased-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SRBs-Setup-Item ::= SEQUENCE { + sRBID sRBID, + lCID lCID, + iE-Extensions ProtocolExtensionContainer { { SRBs-Setup-ItemExtIEs } } OPTIONAL, + ... +} +``` + +``` +SRBs-Setup-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SRBs-SetupMod-Item ::= SEQUENCE { + sRBID sRBID, + lCID lCID, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { SRBs-SetupMod-ItemExtIEs } } OPTIONAL, + ... +} + +SRBs-SetupMod-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SRBs-ToBeReleased-Item ::= SEQUENCE { + sRBID SRBID, + iE-Extensions ProtocolExtensionContainer { { SRBs-ToBeReleased-ItemExtIEs } } OPTIONAL, + ... +} + +SRBs-ToBeReleased-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SRBs-ToBeSetup-Item ::= SEQUENCE { + sRBID SRBID , + duplicationIndication DuplicationIndication OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SRBs-ToBeSetup-ItemExtIEs } } OPTIONAL, + ... +} +``` + +``` +SRBs-ToBeSetup-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-AdditionalDuplicationIndication CRITICALITY ignore EXTENSION AdditionalDuplicationIndication PRESENCE optional }| + { ID id-SDTRLCBearerConfiguration CRITICALITY ignore EXTENSION SDTRLCBearerConfiguration PRESENCE optional }| + { ID id-SRBMappingInfo CRITICALITY ignore EXTENSION UuRLCChannelID PRESENCE optional }, + ... +} + +SRBs-ToBeSetupMod-Item ::= SEQUENCE { + sRBID SRBID, + duplicationIndication DuplicationIndication OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SRBs-ToBeSetupMod-ItemExtIEs } } OPTIONAL, + ... +} + +SRBs-ToBeSetupMod-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-AdditionalDuplicationIndication CRITICALITY ignore EXTENSION AdditionalDuplicationIndication PRESENCE optional }| + { ID id-SRBMappingInfo CRITICALITY ignore EXTENSION UuRLCChannelID PRESENCE optional }| + { ID id-CG-SDTIndicatorSetup CRITICALITY reject EXTENSION CG-SDTIndicatorSetup PRESENCE optional }, + ... +} + +SRSCarrier-List ::= SEQUENCE (SIZE(1.. maxnoSRS-Carriers)) OF SRSCarrier-List-Item +``` + +``` +SRSCarrier-List-Item ::= SEQUENCE { + pointA INTEGER (0..3279165), + uplinkChannelBW-PerSCS-List UplinkChannelBW-PerSCS-List, + activeULBWP ActiveULBWP, + pci NRPCI OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SRSCarrier-List-Item-ExtIEs } } OPTIONAL +} + +SRSCarrier-List-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SRSConfig ::= SEQUENCE { + sRSResource-List SRSResource-List OPTIONAL, + posSRSResource-List PosSRSResource-List OPTIONAL, + sRSResourceSet-List SRSResourceSet-List OPTIONAL, + posSRSResourceSet-List PosSRSResourceSet-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SRSConfig-ExtIEs } } OPTIONAL +} + +SRSConfig-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SRSConfiguration ::= SEQUENCE { + sRSCarrier-List SRSCarrier-List, + iE-Extensions ProtocolExtensionContainer { { SRSConfiguration-ExtIEs } } OPTIONAL +} +``` + +``` +SRSConfiguration-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SrsFrequency ::= INTEGER (0..3279165) +``` + +``` +SRSPortIndex ::= ENUMERATED {id1000, id1001, id1002, id1003,...} +``` + +``` +SRSPosResourceID ::= INTEGER (0..63) +``` + +``` +SRSResource ::= SEQUENCE { + sRSResourceID SRSResourceID, + nrofSRS-Ports ENUMERATED {port1, ports2, ports4}, + transmissionComb TransmissionComb, + startPosition INTEGER (0..13), + nrofSymbols ENUMERATED {n1, n2, n4}, + repetitionFactor ENUMERATED {n1, n2, n4}, + freqDomainPosition INTEGER (0..67), + freqDomainShift INTEGER (0..268), +} +``` + +``` +c-SRS INTEGER (0..63), +b-SRS INTEGER (0..3), +b-hop INTEGER (0..3), +groupOrSequenceHopping ENUMERATED { neither, groupHopping, sequenceHopping }, +resourceType ResourceType, +sequenceId INTEGER (0..1023), +iE-Extensions ProtocolExtensionContainer { { SRSResource-ExtIEs } } OPTIONAL +} + +SRSResource-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-nrofSymbolsExtended CRITICALITY ignore EXTENSION NrofSymbolsExtended PRESENCE optional}| + { ID id-repetitionFactorExtended CRITICALITY ignore EXTENSION RepetitionFactorExtended PRESENCE optional}| + { ID id-startRBHopping CRITICALITY ignore EXTENSION StartRBHopping PRESENCE optional}| + { ID id-startRBIndex CRITICALITY ignore EXTENSION StartRBIndex PRESENCE optional}, + ... +} + +SRSResourceID ::= INTEGER (0..63) + +SRSResourceID-List ::= SEQUENCE (SIZE (1..maxnoSRS-ResourcePerSet)) OF SRSResourceID + +SRSResource-List ::= SEQUENCE (SIZE (1..maxnoSRS-Resources)) OF SRSResource + +SRSResourceSet ::= SEQUENCE { +``` + +``` +sRSResourceSetID SRSResourceSetID, +sRSResourceID-List SRSResourceID-List, +resourceSetType ResourceSetType, +iE-Extensions ProtocolExtensionContainer { { SRSResourceSet-ExtIEs } } OPTIONAL +} + +SRSResourceSet-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SRSResourceSetID ::= INTEGER (0..15, ...) + +SRSResourceSetList ::= SEQUENCE (SIZE(1.. maxnoSRS-ResourceSets)) OF SRSResourceSetItem + +SRSResourceSetItem ::= SEQUENCE { + numSRSresourcesperset INTEGER (1..16, ...) OPTIONAL, + periodicityList PeriodicityList OPTIONAL, + spatialRelationInfo SpatialRelationInfo OPTIONAL, + pathlossReferenceInfo PathlossReferenceInfo OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SRSResourceSetItemExtIEs } } OPTIONAL +} + +SRSResourceSetItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-SRSSpatialRelationPerSRSResource CRITICALITY ignore EXTENSION SpatialRelationPerSRSResource PRESENCE optional}, +``` + +``` + ... +} + +SRSResourceSet-List ::= SEQUENCE (SIZE (1..maxnoSRS-ResourceSets)) OF SRSResourceSet + +SRSResourceTrigger ::= SEQUENCE { + aperiodicSRSResourceTriggerList AperiodicSRSResourceTriggerList, + iE-Extensions ProtocolExtensionContainer { {SRSResourceTrigger-ExtIEs} } OPTIONAL +} + +SRSResourceTrigger-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SRSResourcetype ::= SEQUENCE { + sRSResourceTypeChoice SRSResourceTypeChoice, + iE-Extensions ProtocolExtensionContainer { { SRSResourcetype-ExtIEs} } OPTIONAL, + ... +} + +SRSResourcetype-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-SRSPortIndex CRITICALITY ignore EXTENSION SRSPortIndex PRESENCE optional }, + ... +} +``` + +} + +SRSResourceTypeChoice ::= CHOICE { +    sRSResourceInfo          SRSInfo, +    posSRSResourceInfo     PosSRSInfo, +    choice-extension       ProtocolIE-SingleContainer { { SRSResourceTypeChoice-ExtIEs } } +} + +SRSResourceTypeChoice-ExtIEs FLAP-PROTOCOL-IES ::= { +    ... +} + +SRSInfo ::= SEQUENCE { +    sRSResource          SRSResourceID, +    ... +} + +SRSPosRRInactiveConfig ::= OCTET STRING + +SRSPosRRInactiveQueryIndication ::= ENUMERATED {true, ...} + +PosSRSInfo ::= SEQUENCE { +    posSRSResourceID     SRSPosResourceID, +    ... +} + +} + +SSB ::= SEQUENCE { + +    pCI-NR            NRPCI, +    ssb-index          SSB-Index  OPTIONAL, +    iE-Extensions    ProtocolExtensionContainer { { SSB-ExtIEs } } OPTIONAL + +} + +SSBCoverageModification-List ::= SEQUENCE (SIZE (1..maxnoofSSBAreas)) OF SSBCoverageModification-Item + +SSBCoverageModification-Item ::= SEQUENCE { + +    sSBIndex            INTEGER(0..63), +    sSBCoverageState    SSBCoverageState, +    iE-Extensions    ProtocolExtensionContainer { { SSBCoverageModification-Item-ExtIEs } } OPTIONAL, + +    ... + +} + +SSBCoverageModification-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +{ ID id-Coverage-Modification-Cause CRITICALITY ignore EXTENSION CCO-issue-detection PRESENCE optional }, + +    ... + +} + +SSBCoverageState ::= INTEGER (0..15, ...) + +SSB-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SSB-freqInfo ::= INTEGER (0..maxNRARFCN) + +SSB-Index ::= INTEGER(0..63) + +SSB-subcarrierSpacing ::= ENUMERATED {kHz15, kHz30, kHz120, kHz240, spare3, spare2, spare1, ...} + +SSB-transmissionPeriodicity ::= ENUMERATED {sf10, sf20, sf40, sf80, sf160, sf320, sf640, ...} + +SSB-transmissionTimingOffset ::= INTEGER (0..127, ...) + +SSB-transmissionBitmap ::= CHOICE { + shortBitmap BIT STRING (SIZE (4)), + mediumBitmap BIT STRING (SIZE (8)), + longBitmap BIT STRING (SIZE (64)), + choice-extension ProtocolIE-SingleContainer { { SSB-transmisisonBitmap-ExtIEs } } +} + +``` +SSB-transmisisonBitmap-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +SSBAreaCapacityValueList ::= SEQUENCE (SIZE(1.. maxnoofSSBAreas)) OF SSBAreaCapacityValueItem + +SSBAreaCapacityValueItem ::= SEQUENCE { + sSBIndex INTEGER(0..63), + sSBAreaCapacityValue INTEGER (0..100), + iE-Extensions ProtocolExtensionContainer { { SSBAreaCapacityValueItem-ExtIEs} } OPTIONAL +} + +SSBAreaCapacityValueItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SSBAreaRadioResourceStatusList ::= SEQUENCE (SIZE(1.. maxnoofSSBAreas)) OF SSBAreaRadioResourceStatusItem + +SSBAreaRadioResourceStatusItem ::= SEQUENCE { + sSBIndex INTEGER(0..63), + sSBAreaDLGBRPRBusage INTEGER (0..100), + sSBAreaULGBRPRBusage INTEGER (0..100), + sSBAreaDLnon-GBRPRBusage INTEGER (0..100), + sSBAreaULnon-GBRPRBusage INTEGER (0..100), +} +``` + +``` + sSBAreaDLTotalPRBusage INTEGER (0..100), + sSBAreaULTotalPRBusage INTEGER (0..100), + dLschedulingPDCCHCCEusage INTEGER (0..100) OPTIONAL, + uLschedulingPDCCHCCEusage INTEGER (0..100) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SSBAreaRadioResourceStatusItem-ExtIEs} } OPTIONAL +} +``` + +``` +SSBAreaRadioResourceStatusItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SSBInformation ::= SEQUENCE { + sSBInformationList SSBInformationList, + iE-Extensions ProtocolExtensionContainer { { SSBInformation-ExtIEs } } OPTIONAL +} +``` + +``` +SSBInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SSBInformationList ::= SEQUENCE (SIZE(1.. maxnoofSSBs)) OF SSBInformationItem +``` + +``` +SSBInformationItem ::= SEQUENCE { + sSB-Configuration SSB-TF-Configuration, +``` + +``` +pCI-NR NRPCI, +iE-Extensions ProtocolExtensionContainer { { SSBInformationItem-ExtIEs } } OPTIONAL +} + +SSBInformationItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SSB-PositionsInBurst ::= CHOICE { + shortBitmap BIT STRING (SIZE (4)), + mediumBitmap BIT STRING (SIZE (8)), + longBitmap BIT STRING (SIZE (64)), + choice-extension ProtocolIE-SingleContainer { { SSB-PositionsInBurst-ExtIEs } } +} + +SSB-PositionsInBurst-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +SSBs-activated-List ::= SEQUENCE (SIZE(1.. maxnoofSSBAreas)) OF SSB-Index + +SSBs-forPaging-List ::= SEQUENCE (SIZE(1.. maxnoofSSBAreas)) OF SSB-Index + +SSBs-toBeActivated-List ::= SEQUENCE (SIZE(1.. maxnoofSSBAreas)) OF SSB-Index +``` + +``` +SSB-TF-Configuration ::= SEQUENCE { + sSB-frequency INTEGER (0..3279165), + sSB-subcarrier-spacing ENUMERATED {kHz15, kHz30, kHz60, kHz120, kHz240, ..., kHz480, kHz960}, + -- The value kHz60 is not supported in this version of the specification. + sSB-Transmit-power INTEGER (-60..50), + sSB-periodicity ENUMERATED {ms5, ms10, ms20, ms40, ms80, ms160, ...}, + sSB-half-frame-offset INTEGER(0..1), + sSB-SFN-offset INTEGER(0..15), + sSB-position-in-burst SSB-PositionsInBurst OPTIONAL, + sFNInitialisationTime RelativeTime1900 OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SSB-TF-Configuration-ExtIEs} } OPTIONAL +} +``` + +``` +SSB-TF-Configuration-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +SSBToReportList ::= SEQUENCE (SIZE(1.. maxnoofSSBAreas)) OF SSBToReportItem +``` + +``` +SSBToReportItem ::= SEQUENCE { + sSBIndex INTEGER(0..63), +``` + +``` + iE-Extensions ProtocolExtensionContainer { { SSBSReportItem-ExtIEs } } OPTIONAL +} + +SSBSReportItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +StartRBIndex ::= CHOICE{ + freqScalingFactor2 INTEGER(0..1), + freqScalingFactor4 INTEGER(0..3), + choice-extension ProtocolIE-SingleContainer { { StartRBIndex-ExtIEs } } +} + +StartRBIndex-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +StartRBHopping ::= ENUMERATED {enable} + +StartTimeAndDuration ::= SEQUENCE { + startTime RelativeTime1900 OPTIONAL, + duration INTEGER (0..90060, ...) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { StartTimeAndDuration-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +StartTimeAndDuration-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SUL-Information ::= SEQUENCE { + sUL-NRARFCN INTEGER (0..maxNRARFCN), + sUL-transmission-Bandwidth Transmission-Bandwidth, + iE-Extensions ProtocolExtensionContainer { { SUL-InformationExtIEs} } OPTIONAL, + ... +} + +SUL-InformationExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-CarrierList CRITICALITY ignore EXTENSION NRCarrierList PRESENCE optional }| + { ID id-FrequencyShift7p5khz CRITICALITY ignore EXTENSION FrequencyShift7p5khz PRESENCE optional }, + ... +} + +SubcarrierSpacing ::= ENUMERATED { kHz15, kHz30, kHz60, kHz120, kHz240, spare3, spare2, spare1, ...} + +SubscriberProfileIDforRFP ::= INTEGER (1..256, ...) + +SuccessfulHOReportInformationList ::= SEQUENCE (SIZE(1.. maxnoofSuccessfulHOReports)) OF SuccessfulHOReportInformation-Item +``` + +``` +SuccessfulHOREportInformation-Item ::= SEQUENCE { + successfulHOREportContainer OCTET STRING, + iE-Extensions ProtocolExtensionContainer { { SuccessfulHOREportInformation-Item-ExtIEs } } OPTIONAL +} + +SuccessfulHOREportInformation-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SuccessfulPSCellChangeReportInformationList ::= SEQUENCE (SIZE(1.. maxnoofSuccessfulPSCellChangeReports)) OF +SuccessfulPSCellChangeReportInformation-Item + +SuccessfulPSCellChangeReportInformation-Item ::= SEQUENCE { + successfulPSCellChangeReportContainer OCTET STRING, + iE-Extensions ProtocolExtensionContainer { { SuccessfulPSCellChangeReportInformation-Item-ExtIEs } } OPTIONAL +} + +SuccessfulPSCellChangeReportInformation-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SULAccessIndication ::= ENUMERATED {true,...} + +SupportedSULFreqBandItem ::= SEQUENCE { +``` + +``` +freqBandIndicatorNr INTEGER (1..1024,...), +iE-Extensions ProtocolExtensionContainer { { SupportedSULFreqBandItem-ExtIEs } } OPTIONAL, +... +} + +SupportedSULFreqBandItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SupportedUETypesList ::= SEQUENCE (SIZE(1.. maxnoofUETypes)) OF SupportedUETypesList-Item + +SupportedUETypesList-Item ::= SEQUENCE { + supportedUETypes ENUMERATED {non-redcap-ue, redcap-ue, ...}, + iE-Extensions ProtocolExtensionContainer { { SupportedUETypesList-Item-ExtIEs } } OPTIONAL, + ... +} + +SupportedUETypesList-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +SurvivalTime ::= INTEGER (0.. 1920000,...) + +SymbolAllocInSlot ::= CHOICE { +``` + +``` + all-DL NULL, + all-UL NULL, + both-DL-and-UL NumDLULSymbols, + choice-extension ProtocolIE-SingleContainer { { SymbolAllocInSlot-ExtIEs } } +} +``` + +``` +SymbolAllocInSlot-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +SystemFrameNumber ::= INTEGER (0..1023) +``` + +``` +SystemInformationAreaID ::= BIT STRING (SIZE (24)) +``` + +``` +-- T +``` + +``` +TAI ::= SEQUENCE { + pLMN-Identity PLMN-Identity, + fiveGS-TAC FiveGS-TAC, + iE-Extensions ProtocolExtensionContainer { { TAI-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +TAI-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +FiveGS-TAC ::= OCTET STRING (SIZE(3)) + +Configured-EPS-TAC ::= OCTET STRING (SIZE(2)) + +TargetCellList ::= SEQUENCE (SIZE(1..maxnoofCHOCells)) OF TargetCellList-Item + +TargetCellList-Item ::= SEQUENCE { + target-cell NRCGI, + iE-Extensions ProtocolExtensionContainer { { TargetCellList-Item-ExtIEs} } OPTIONAL +} + +TargetCellList-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +NSAGSupportList ::= SEQUENCE (SIZE(1.. maxnoofNSAGs)) OF NSAGSupportItem + +NSAGSupportItem ::= SEQUENCE { + nSAG-ID NSAG-ID, + nSAGSliceSupport ExtendedSliceSupportList, +``` + +``` +iE-Extensions ProtocolExtensionContainer { {NSAGSupportItem-ExtIEs} } OPTIONAL, +... +} + +NSAGSupportItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +... +} + +NSAG-ID ::= INTEGER (0..255, ...) + +TCIStateID ::= INTEGER (0..127) + +TCIStatesConfigurationsList ::= SEQUENCE { + jointorDLTCIStatesConfigurationsList JointorDLTCIStatesConfigurationsList OPTIONAL, + uLTCIStatesConfigurationsList ULTCIStatesConfigurationsList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { TCIStatesConfigurationsList-ExtIEs} } OPTIONAL, + ... +} + +TCIStatesConfigurationsList-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +... +} +``` + +TAInformation-List ::= SEQUENCE (SIZE(1.. maxnoofTAList)) OF TAInformationItem + +TAInformationItem ::= SEQUENCE { +    nRCGI                  NRCGI, +    tAValue              TAValue, +    preambleIndex        PreambleIndex, +    rA-RNTI              RA-RNTI, +    sourceGNB-DU-ID      GNB-DU-ID, +    iE-Extensions        ProtocolExtensionContainer { { TAInformationItem-ExtIEs} } OPTIONAL, +    ... +} + +TAInformationItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +TAValue ::= INTEGER (0..4095) + +TDD-Info ::= SEQUENCE { +    nRFreqInfo              NRFreqInfo, +    transmission-Bandwidth  Transmission-Bandwidth, +    iE-Extensions          ProtocolExtensionContainer { { TDD-Info-ExtIEs} } OPTIONAL, +    ... +} + +``` +TDD-Info-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + {ID id-IntendedTDD-DL-ULConfig CRITICALITY ignore EXTENSION IntendedTDD-DL-ULConfig PRESENCE optional}| + {ID id-TDD-UL-DLConfigCommonNR CRITICALITY ignore EXTENSION TDD-UL-DLConfigCommonNR PRESENCE optional }| + {ID id-CarrierList CRITICALITY ignore EXTENSION NRCarrierList PRESENCE optional }, + ... +} + +TDD-InfoRel16 ::= SEQUENCE { + tDD-FreqInfo FreqInfoRel16 OPTIONAL, + sUL-FreqInfo FreqInfoRel16 OPTIONAL, + tDD-UL-DLConfigCommonNR TDD-UL-DLConfigCommonNR OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {TDD-InfoRel16-ExtIEs} } OPTIONAL, + ... +} + +TDD-InfoRel16-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +TDD-UL-DLConfigCommonNR ::= OCTET STRING + +TRPTEGInformation ::= CHOICE { +``` + +``` + rxTx-TEG RxTxTEG, + rx-TEG RxTEG, + choice-extension ProtocolIE-SingleContainer { { TRPTEGInformation-ExtIEs } } +} + +TRPTEGInformation-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +RxTxTEG ::= SEQUENCE { + tRP-RxTx-TEGInformation TRP-RxTx-TEGInformation, + tRP-Tx-TEGInformation TRP-Tx-TEGInformation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { RxTxTEG-ExtIEs } } OPTIONAL, + ... +} + +RxTxTEG-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +RxTEG ::= SEQUENCE { + tRP-Rx-TEGInformation TRP-Rx-TEGInformation, + tRP-Tx-TEGInformation TRP-Tx-TEGInformation, + iE-Extensions ProtocolExtensionContainer { { RxTEG-ExtIEs } } OPTIONAL, +``` + +``` + ... +} + +RxTEG-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +TimeReferenceInformation ::= SEQUENCE { + referenceTime ReferenceTime, + referenceSFN ReferenceSFN, + uncertainty Uncertainty, + timeInformationType TimeInformationType, + iE-Extensions ProtocolExtensionContainer { {TimeReferenceInformation-ExtIEs} } OPTIONAL +} + +TimeReferenceInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +TimeInformationType ::= ENUMERATED {localClock} + +TimeStamp ::= SEQUENCE { + systemFrameNumber SystemFrameNumber, + slotIndex TimeStampSlotIndex, +``` + +``` + measurementTime RelativeTime1900 OPTIONAL, + iE-Extension ProtocolExtensionContainer { { TimeStamp-ExtIEs } } OPTIONAL +} +``` + +``` +TimeStamp-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +TimeStampSlotIndex ::= CHOICE { + sCS-15 INTEGER(0..9), + sCS-30 INTEGER(0..19), + sCS-60 INTEGER(0..39), + sCS-120 INTEGER(0..79), + choice-extension ProtocolIE-SingleContainer { { TimeStampSlotIndex-ExtIEs } } +} +``` + +``` +TimeStampSlotIndex-ExtIEs FLAP-PROTOCOL-IES ::= { + { ID id-SCS-480 CRITICALITY reject TYPE SCS-480 PRESENCE mandatory } | + { ID id-SCS-960 CRITICALITY reject TYPE SCS-960 PRESENCE mandatory }, + ... +} +``` + +``` +TimeToWait ::= ENUMERATED {v1s, v2s, v5s, v10s, v20s, v60s, ...} +``` + +TimingErrorMargin ::= ENUMERATED {m0Tc, m2Tc, m4Tc, m6Tc, m8Tc, m12Tc, m16Tc, m20Tc, m24Tc, m32Tc, m40Tc, m48Tc, m56Tc, m64Tc, m72Tc, m80Tc, ...} + +TimingMeasurementQuality ::= SEQUENCE { +    measurementQuality    INTEGER(0..31), +    resolution            ENUMERATED{m0dot1, m1, m10, m30, ...}, +    iE-Extensions        ProtocolExtensionContainer { { TimingMeasurementQuality-ExtIEs} }    OPTIONAL +} + +TimingMeasurementQuality-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +TMGI ::= OCTET STRING (SIZE(6)) + +TNLAssociationUsage ::= ENUMERATED { +    ue, +    non-ue, +    both, +    ... +} + +TNLCapacityIndicator ::= SEQUENCE { +    dLTNLOfferedCapacity        INTEGER (1.. 16777216,...), +    dLTNLAvailableCapacity    INTEGER (0.. 100,...), +} + +``` + uLTNLOfferedCapacity INTEGER (1.. 16777216,...), + uLTNLAvailableCapacity INTEGER (0.. 100,...), + iE-Extensions ProtocolExtensionContainer { { TNLCapacityIndicator-ExtIEs } } OPTIONAL +} + +TNLCapacityIndicator-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +TraceActivation ::= SEQUENCE { + traceID TraceID, + interfacesToTrace InterfacesToTrace, + traceDepth TraceDepth, + traceCollectionEntityIPAddress TransportLayerAddress, + iE-Extensions ProtocolExtensionContainer { { TraceActivation-ExtIEs } } OPTIONAL +} + +TraceActivation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + {ID id-mdtConfiguration CRITICALITY ignore EXTENSION MDTConfiguration PRESENCE optional}| + {ID id-TraceCollectionEntityURI CRITICALITY ignore EXTENSION URI-address PRESENCE optional}, + ... +} + +TraceDepth ::= ENUMERATED { +``` + +``` + minimum, + medium, + maximum, + minimumWithoutVendorSpecificExtension, + mediumWithoutVendorSpecificExtension, + maximumWithoutVendorSpecificExtension, + ... +} + +TraceID ::= OCTET STRING (SIZE(8)) + +TrafficMappingInfo ::= CHOICE { + iPtoLayer2TrafficMappingInfo iPtoLayer2TrafficMappingInfo, + bAPlayerBHRLCchannelMappingInfo bAPlayerBHRLCchannelMappingInfo, + choice-extension ProtocolIE-SingleContainer { { TrafficMappingInfo-ExtIEs } } +} + +TrafficMappingInfo-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +TransportLayerAddress ::= BIT STRING (SIZE(1..160, ...)) + +TransactionID ::= INTEGER (0..255, ...) +``` + +``` +Transmission-Bandwidth ::= SEQUENCE { + nRSCS NRSCS, + nRNRB NRNRB, + iE-Extensions ProtocolExtensionContainer { { Transmission-Bandwidth-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +Transmission-Bandwidth-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +TransmissionComb ::= CHOICE { + n2 SEQUENCE { + combOffset-n2 INTEGER (0..1), + cyclicShift-n2 INTEGER (0..7) + }, + n4 SEQUENCE { + combOffset-n4 INTEGER (0..3), + cyclicShift-n4 INTEGER (0..11) + }, + choice-extension ProtocolIE-SingleContainer { { TransmissionComb-ExtIEs } } +} +``` + +``` +TransmissionComb-ExtIEs FLAP-PROTOCOL-IES ::= { +``` + +``` +{ ID id-transmissionCombn8 CRITICALITY reject TYPE TransmissionCombn8 PRESENCE mandatory}, +... +} + +TransmissionCombn8 ::= SEQUENCE { + combOffset-n8 INTEGER (0..7), + cyclicShift-n8 INTEGER (0..5), + iE-Extensions ProtocolExtensionContainer { { TransmissionCombn8-ExtIEs } } OPTIONAL +} + +TransmissionCombn8-ExtIEs FIAP-PROTOCOL-EXTENSION ::= { + ... +} + +TransmissionCombPos ::= CHOICE { + n2 SEQUENCE { + combOffset-n2 INTEGER (0..1), + cyclicShift-n2 INTEGER (0..7) + }, + n4 SEQUENCE { + combOffset-n4 INTEGER (0..3), + cyclicShift-n4 INTEGER (0..11) + }, + n8 SEQUENCE { +``` + +``` + combOffset-n8 INTEGER (0..7), + cyclicShift-n8 INTEGER (0..5) + }, + + choice-extension ProtocolIE-SingleContainer { { TransmissionCombPos-ExtIEs } } +} + +TransmissionCombPos-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +TransmissionStopIndicator ::= ENUMERATED {true, ... } + +Transport-UP-Layer-Address-Info-To-Add-List ::= SEQUENCE (SIZE(1.. maxnooFTLAs)) OF Transport-UP-Layer-Address-Info-To-Add-Item + +Transport-UP-Layer-Address-Info-To-Add-Item ::= SEQUENCE { + iP-SecTransportLayerAddress TransportLayerAddress, + gTPTransportLayerAddressToAdd GTPTLAs OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Transport-UP-Layer-Address-Info-To-Add-ItemExtIEs } } OPTIONAL +} + +Transport-UP-Layer-Address-Info-To-Add-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +Transport-UP-Layer-Address-Info-To-Remove-List ::= SEQUENCE (SIZE(1.. maxnoofTLAs)) OF Transport-UP-Layer-Address-Info-To-Remove-Item + +Transport-UP-Layer-Address-Info-To-Remove-Item ::= SEQUENCE { +    iP-SecTransportLayerAddress    TransportLayerAddress, +    gTPTransportLayerAddressToRemove    GTPTLAs    OPTIONAL, +    iE-Extensions    ProtocolExtensionContainer { { Transport-UP-Layer-Address-Info-To-Remove-ItemExtIEs } } OPTIONAL +} + +Transport-UP-Layer-Address-Info-To-Remove-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +TransmissionActionIndicator ::= ENUMERATED {stop, ..., restart } + +TRPBeamAntennaInformation ::= SEQUENCE { +    choice-TRP-Beam-Antenna-Info-Item    Choice-TRP-Beam-Antenna-Info-Item    , +    iE-Extensions    ProtocolExtensionContainer { { TRPBeamAntennaInformation-ExtIEs } }    OPTIONAL, +    ... +} + +TRPBeamAntennaInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +``` +Choice-TRP-Beam-Antenna-Info-Item ::= CHOICE { + reference TRPID, + explicit TRP-BeamAntennaExplicitInformation, + noChange NULL, + choice-extension ProtocolIE-SingleContainer { { Choice-TRP-Beam-Info-Item-ExtIEs } } +} + +Choice-TRP-Beam-Info-Item-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +TRP-BeamAntennaExplicitInformation ::= SEQUENCE { + trp-BeamAntennaAngles TRP-BeamAntennaAngles, + lcs-to-gcs-translation LCS-to-GCS-Translation OPTIONAL, + iE-Extensions ProtocolExtensionContainer {{ TRP-BeamAntennaExplicitInformation-ExtIEs}} OPTIONAL, + ... +} + +TRP-BeamAntennaExplicitInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +TRP-BeamAntennaAngles ::= SEQUENCE (SIZE (1.. maxnoAzimuthAngles)) OF TRP-BeamAntennaAnglesList-Item + +TRP-BeamAntennaAnglesList-Item ::= SEQUENCE { +    trp-azimuth-angle                    INTEGER (0..359), +    trp-azimuth-angle-fine              INTEGER (0..9) OPTIONAL, +    trp-elevation-angle-list            SEQUENCE (SIZE (1.. maxnoElevationAngles)) OF TRP-ElevationAngleList-Item, +    iE-Extensions                        ProtocolExtensionContainer {{ TRP-BeamAntennaAnglesList-Item-ExtIEs}} OPTIONAL, +    ... +} + +TRP-BeamAntennaAnglesList-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +TRP-ElevationAngleList-Item ::= SEQUENCE { +    trp-elevation-angle                  INTEGER (0..180), +    trp-elevation-angle-fine            INTEGER (0..9) OPTIONAL, +    trp-beam-power-list                SEQUENCE (SIZE (2..maxNumResourcesPerAngle)) OF TRP-Beam-Power-Item, +    iE-Extensions                        ProtocolExtensionContainer {{ TRP-ElevationAngleList-Item-ExtIEs}} OPTIONAL, +    ... +} + +TRP-ElevationAngleList-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +``` +TRP-Beam-Power-Item ::= SEQUENCE { + pRSResourceSetID PRS-Resource-Set-ID OPTIONAL, + pRSResourceID PRS-Resource-ID, + relativePower INTEGER (0..30), --negative value + relativePowerFine INTEGER (0..9) OPTIONAL, + iE-Extensions ProtocolExtensionContainer {{ TRP-Beam-Power-Item-ExtIEs}} + OPTIONAL, + ... +} +``` + +``` +TRP-Beam-Power-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +TRPID ::= INTEGER (0.. maxnoofTRPs, ...) +``` + +``` +TRPInformation ::= SEQUENCE { + tRPID TRPID, + tRPInformationTypeResponseList TRPInformationTypeResponseList, + iE-Extensions ProtocolExtensionContainer { { TRPInformation-ExtIEs } } + OPTIONAL +} +``` + +``` +TRPInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` +{ ID id-Mobile-IAB-MT-UE-ID CRITICALITY reject EXTENSION Mobile-IAB-MT-UE-ID PRESENCE optional}, + +--This IE shall be present if the TRP type IE is set to the value "mobile-trp" + +... + +} + +TRPInformationItem ::= SEQUENCE { + + tRPInformation TRPInformation, + + iE-Extensions ProtocolExtensionContainer { TRPInformationItem-ExtIEs } } OPTIONAL + +} + +TRPInformationItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + + ... + +} + +TRPInformationTypeItem ::= ENUMERATED { + + nrPCI, + + nG-RAN-CGI, + + arfcn, + + pRSConfig, + + sSBConfig, + + sFNInitTime, + + spatialDirectInfo, + + geoCoord, + + ... } +``` + +``` + trp-type, + ondemandPRS, + trpTxTeg, + beam-antenna-info, + mobile-trp-location-info + +} +``` + +``` +TRPInformationTypeResponseList ::= SEQUENCE (SIZE(1.. maxnoofTRPInfoTypes)) OF TRPInformationTypeResponseItem +``` + +``` +TRPInformationTypeResponseItem ::= CHOICE { + pCI-NR NRPCI, + nG-RAN-CGI NRCGI, + nRARFCN INTEGER (0..maxNRARFCN), + pRSConfiguration PRSConfiguration, + sSBInformation SSBInformation, + sFNInitialisationTime RelativeTime1900, + spatialDirectionInformation SpatialDirectionInformation, + geographicalCoordinates GeographicalCoordinates, + choice-extension ProtocolIE-SingleContainer { { TRPInformationTypeResponseItem-ExtIEs } } +} +``` + +``` +TRPInformationTypeResponseItem-ExtIEs FLAP-PROTOCOL-IES ::= { +``` + +``` +{ ID id-TRPTType CRITICALITY reject TYPE TRPTType PRESENCE mandatory }| +{ ID id-OnDemandPRS CRITICALITY reject TYPE OnDemandPRS-Info PRESENCE mandatory}| +{ ID id-TRPTxTEGAssociation CRITICALITY reject TYPE TRPTxTEGAssociation PRESENCE mandatory}| +{ ID id-TRPBeamAntennaInformation CRITICALITY reject TYPE TRPBeamAntennaInformation PRESENCE mandatory }| +{ ID id-Mobile-TRP-LocationInformation CRITICALITY reject TYPE Mobile-TRP-LocationInformation PRESENCE mandatory }, +... +} +``` + +``` +TRPList ::= SEQUENCE (SIZE(1.. maxnoofTRPs)) OF TRPListItem +``` + +``` +TRPListItem ::= SEQUENCE { + tRPID TRPID, + iE-Extensions ProtocolExtensionContainer { { TRPListItem-ExtIEs } } OPTIONAL +} +``` + +``` +TRPListItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +TRPMeasurementQuality ::= SEQUENCE { + tRPMeasurementQuality-Item TRPMeasurementQuality-Item, + iE-Extensions ProtocolExtensionContainer { { TRPMeasurementQuality-ExtIEs } } OPTIONAL +} +``` + +``` +TRPMeasurementQuality-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +TRPMeasurementQuality-Item ::= CHOICE { + timingMeasurementQuality TimingMeasurementQuality, + angleMeasurementQuality AngleMeasurementQuality, + choice-extension ProtocolIE-SingleContainer { { TRPMeasurementQuality-Item-ExtIEs } } +} + +TRPMeasurementQuality-Item-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +TRP-MeasurementRequestList ::= SEQUENCE (SIZE (1..maxNoOfMeasTRPs)) OF TRP-MeasurementRequestItem + +TRP-MeasurementRequestItem ::= SEQUENCE { + tRPID TRPID, + search-window-information Search-window-information OPTIONAL, + iE-extensions ProtocolExtensionContainer { { TRP-MeasurementRequestItem-ExtIEs } } OPTIONAL +} + +TRP-MeasurementRequestItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` +{ ID id-NRCGI CRITICALITY ignore EXTENSION NRCGI PRESENCE optional }| +{ ID id-AoA-SearchWindow CRITICALITY ignore EXTENSION AoA-AssistanceInfo PRESENCE optional }| +{ ID id-NumberOfTRPRxTEG CRITICALITY ignore EXTENSION NumberOfTRPRxTEG PRESENCE optional }| +{ ID id-NumberOfTRPRxTxTEG CRITICALITY ignore EXTENSION NumberOfTRPRxTxTEG PRESENCE optional }, +... +} +``` + +``` +TRP-PRS-Info-List ::= SEQUENCE (SIZE(1.. maxnoofPRSTRPs)) OF TRP-PRS-Info-List-Item +``` + +``` +TRP-PRS-Info-List-Item ::= SEQUENCE { + tRP-ID TRPID, + nR-PCI NRPCI, + cGI-NR NRCGI OPTIONAL, + pRSConfiguration PRSConfiguration, + iE-Extensions ProtocolExtensionContainer { { TRP-PRS-Info-List-Item-ExtIEs} } OPTIONAL, + ... +} +``` + +``` +TRP-PRS-Info-List-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +TRPPositionDefinitionType ::= CHOICE { +``` + +``` + direct TRPPositionDirect, + referenced TRPPositionReferenced, + choice-extension ProtocolIE-SingleContainer { { TRPPositionDefinitionType-ExtIEs } } +} + +TRPPositionDefinitionType-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +TRPPositionDirect ::= SEQUENCE { + accuracy TRPPositionDirectAccuracy, + iE-extensions ProtocolExtensionContainer { { TRPPositionDirect-ExtIEs } } OPTIONAL +} + +TRPPositionDirect-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +TRPPositionDirectAccuracy ::= CHOICE { + tRPPosition AccessPointPosition, + tRPHAPosition NGRANHighAccuracyAccessPointPosition, + choice-extension ProtocolIE-SingleContainer { { TRPPositionDirectAccuracy-ExtIEs } } +} +``` + +``` +TRPPositionDirectAccuracy-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +TRPPositionReferenced ::= SEQUENCE { + referencePoint ReferencePoint, + referencePointType TRPReferencePointType, + iE-extensions ProtocolExtensionContainer { { TRPPositionReferenced-ExtIEs } } OPTIONAL +} + +TRPPositionReferenced-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +TRPReferencePointType ::= CHOICE { + tRPPositionRelativeGeodetic RelativeGeodeticLocation, + tRPPositionRelativeCartesian RelativeCartesianLocation, + choice-extension ProtocolIE-SingleContainer { { TRPReferencePointType-ExtIEs } } +} + +TRPReferencePointType-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} +``` + +``` +TRP-Rx-TEGInformation ::= SEQUENCE { + tRP-Rx-TEGID INTEGER (0..31), + tRP-Rx-TimingErrorMargin TimingErrorMargin, + iE-Extensions ProtocolExtensionContainer { { TRP-Rx-TEGInformation-ExtIEs } } OPTIONAL, + ... +} + +TRP-Rx-TEGInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +TRP-RxTx-TEGInformation ::= SEQUENCE { + tRP-RxTx-TEGID INTEGER (0..255), + tRP-RxTx-TimingErrorMargin RxTxTimingErrorMargin, + iE-Extensions ProtocolExtensionContainer { { TRP-RxTx-TEGInformation-ExtIEs } } OPTIONAL, + ... +} + +TRP-RxTx-TEGInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +TRP-Tx-TEGInformation ::= SEQUENCE { +``` + +``` + tRP-Tx-TEGID INTEGER (0..7), + tRP-Tx-TimingErrorMargin TimingErrorMargin, + iE-Extensions ProtocolExtensionContainer { { TRP-Tx-TEGInformation-ExtIEs } } OPTIONAL, + ... +} + +TRP-Tx-TEGInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +TRPTxTEGAssociation ::= SEQUENCE (SIZE(1.. maxnoTRPTEGs)) OF TRPTEG-Item + +TRPTEG-Item ::= SEQUENCE { + tRP-Tx-TEGInformation TRP-Tx-TEGInformation, + dl-PRSResourceSetID PRS-Resource-Set-ID, + dl-PRSResourceID-List SEQUENCE (SIZE(1.. maxnoofPRS-ResourcesPerSet)) OF DLPRSResourceID-Item OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { TRPTEGItem-ExtIEs } } OPTIONAL, + ... +} + +TRPTEGItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +DLPRSResourceID-Item ::= SEQUENCE { + dl-PRSResourceID PRS-Resource-ID, + iE-Extensions ProtocolExtensionContainer { { DLPRSResource-Item-ExtIEs} } OPTIONAL, + ... +} + +DLPRSResource-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +TypeOfError ::= ENUMERATED { + not-understood, + missing, + ... +} + +Transport-Layer-Address-Info ::= SEQUENCE { + transport-UP-Layer-Address-Info-To-Add-List Transport-UP-Layer-Address-Info-To-Add-List OPTIONAL, + transport-UP-Layer-Address-Info-To-Remove-List Transport-UP-Layer-Address-Info-To-Remove-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Transport-Layer-Address-Info-ExtIEs } } OPTIONAL +} + +Transport-Layer-Address-Info-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +} + +TRPType ::= ENUMERATED { + prsOnlyTP, + srsOnlyRP, + tp, + rp, + trp, + ..., + mobile-trp +} + +TSCAssistanceInformation ::= SEQUENCE { + periodicity Periodicity, + burstArrivalTime BurstArrivalTime OPTIONAL, + iE-Extensions ProtocolExtensionContainer { TSCAssistanceInformation-ExtIEs } OPTIONAL, + ... +} + +TSCAssistanceInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-SurvivalTime CRITICALITY ignore EXTENSION SurvivalTime PRESENCE optional }| + { ID id-RANfeedbacktype CRITICALITY ignore EXTENSION RANfeedbacktype PRESENCE optional }| + { ID id-N6JitterInformation CRITICALITY ignore EXTENSION N6JitterInformation PRESENCE optional }, +``` + +``` +... +} + +TSCTrafficCharacteristics ::= SEQUENCE { + tSCAssistanceInformationDL TSCAssistanceInformation OPTIONAL, + tSCAssistanceInformationUL TSCAssistanceInformation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { TSCTrafficCharacteristics-ExtIEs} } OPTIONAL, + ... +} + +TSCTrafficCharacteristics-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +TSCTrafficCharacteristicsFeedback ::= SEQUENCE { + tSCFeedbackInformationDL TSCFeedbackInformation OPTIONAL, + tSCFeedbackInformationUL TSCFeedbackInformation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { TSCTrafficCharacteristicsFeedback-ExtIEs} } OPTIONAL, + ... +} + +TSCTrafficCharacteristicsFeedback-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +TSCFeedbackInformation ::= SEQUENCE { + burstArrivalTimeOffset INTEGER (-640000..640000, ...), + adjustedPeriodicity Periodicity OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { TSCFeedbackInformation-ExtIEs} } OPTIONAL, + ... +} + +TSCFeedbackInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +TRP-MeasurementUpdateList ::= SEQUENCE (SIZE (1..maxNoOfMeasTRPs)) OF TRP-MeasurementUpdateItem + +TRP-MeasurementUpdateItem ::= SEQUENCE { + tRP-ID TRPID, + aoA-window-information AoA-AssistanceInfo OPTIONAL, + iE-extensions ProtocolExtensionContainer { { TRP-MeasurementUpdateItem-ExtIEs } } OPTIONAL, + ... +} + +TRP-MeasurementUpdateItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-NumberOfTRPRxTEG CRITICALITY ignore EXTENSION NumberOfTRPRxTEG PRESENCE optional }| + { ID id-NumberOfTRPRxTxTEG CRITICALITY ignore EXTENSION NumberOfTRPRxTxTEG PRESENCE optional }, +``` + +``` + ... +} + +TwoPHRModeMCG ::= ENUMERATED {enabled, ...} + +TwoPHRModeSCG ::= ENUMERATED {enabled, ...} + +-- U + +UAC-Assistance-Info ::= SEQUENCE { + uACPLMN-List UACPLMN-List, + iE-Extensions ProtocolExtensionContainer { { UAC-Assistance-InfoExtIEs} } OPTIONAL +} + +UAC-Assistance-InfoExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +UACPLMN-List ::= SEQUENCE (SIZE(1..maxnoofUACPLMNs)) OF UACPLMN-Item + +UACPLMN-Item ::= SEQUENCE { + pLMNIdentity PLMN-Identity, + uACType-List UACType-List, iE-Extensions ProtocolExtensionContainer { { UACPLMN-Item-ExtIEs} } OPTIONAL +} +``` + +``` +UACPLMN-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-NID CRITICALITY ignore EXTENSION NID PRESENCE optional }, + ... +} + +UACType-List ::= SEQUENCE (SIZE(1..maxnoofUACperPLMN)) OF UACType-Item + +UACType-Item ::= SEQUENCE { + uACReductionIndication UACReductionIndication, + uACCategoryType UACCategoryType, + iE-Extensions ProtocolExtensionContainer { { UACType-Item-ExtIEs } } OPTIONAL +} + +UACType-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +UACCategoryType ::= CHOICE { + uACStandardized UACAction, + uACOperatorDefined UACOperatorDefined, + choice-extension ProtocolIE-SingleContainer { { UACCategoryType-ExtIEs } } +} +``` + +UACCategoryType-ExtIEs FLAP-PROTOCOL-IES ::= { + +... + +} + +UACOperatorDefined ::= SEQUENCE { + +accessCategory INTEGER (32..63,...), + +accessIdentity BIT STRING (SIZE(7)), + +iE-Extensions ProtocolExtensionContainer { { UACOperatorDefined-ExtIEs } } OPTIONAL + +} + +UACOperatorDefined-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +UACAction ::= ENUMERATED { + +reject-non-emergency-mo-dt, + +reject-rrc-cr-signalling, + +permit-emergency-sessions-and-mobile-terminated-services-only, + +permit-high-priority-sessions-and-mobile-terminated-services-only, + +... + +} + +UACReductionIndication ::= INTEGER (0..100) + +``` +UE-associatedLogicalFl-ConnectionItem ::= SEQUENCE { + gNB-CU-UE-FlAP-ID GNB-CU-UE-FlAP-ID OPTIONAL, + gNB-DU-UE-FlAP-ID GNB-DU-UE-FlAP-ID OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UE-associatedLogicalFl-ConnectionItemExtIEs} } OPTIONAL, + ... +} + +UEAssistanceInformation ::= OCTET STRING + +UEAssistanceInformationEUTRA ::= OCTET STRING + +UE-associatedLogicalFl-ConnectionItemExtIEs FlAP-PROTOCOL-EXTENSION ::= { + ... +} + +UE-CapabilityRAT-ContainerList ::= OCTET STRING + +UEContextNotRetrievable ::= ENUMERATED {true, ...} + +UEIdentityIndexValue ::= CHOICE { + indexLength10 BIT STRING (SIZE (10)), + choice-extension ProtocolIE-SingleContainer { {UEIdentityIndexValueChoice-ExtIEs} } +``` + +``` +} + +UEIdentityIndexValueChoice-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +UEIdentity-List-For-Paging-Item ::= SEQUENCE { + uEIdentityIndexValue UEIdentityIndexValue, + pagingDRX PagingDRX OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UEIdentity-List-For-Paging-Item-ExtIEs} } OPTIONAL +} + +UEIdentity-List-For-Paging-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +UE-MulticastMRBs-ConfirmedToBeModified-Item ::= SEQUENCE { + mRB-ID MRB-ID, + mrb-type-reconfiguration MBSPTPTransmissionTunnelRequired OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UE-MulticastMRBs-ConfirmedToBeModified-Item-ExtIEs } } OPTIONAL +} + +UE-MulticastMRBs-ConfirmedToBeModified-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +} + +UE-MulticastMRBs-RequiredToBeModified-Item ::= SEQUENCE { + + mRB-ID MRB-ID, + + mrb-type-reconfiguration ENUMERATED {true, ...} OPTIONAL, + + mrb-reconfigured-RLctype ENUMERATED { + + rlc-um-ptp, + + rlc-am-ptp, + + rlc-um-dl-ptm, + + two-rlc-um-dl-ptp-and-dl-ptm, + + three-rlc-um-dl-ptp-ul-ptp-dl-ptm, + + two-rlc-am-ptp-um-dl-ptm, + + ...} OPTIONAL, + + iE-Extensions ProtocolExtensionContainer { { UE-MulticastMRBs-RequiredToBeModified-Item-ExtIEs } } OPTIONAL + +} + +UE-MulticastMRBs-RequiredToBeModified-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + + { ID id-MulticastFlUContextReferenceCU CRITICALITY reject EXTENSION MulticastFlUContextReferenceCU PRESENCE +optional}, + + ... + +} + +UE-MulticastMRBs-RequiredToBeReleased-Item ::= SEQUENCE { + + mRB-ID MRB-ID, + + iE-Extensions ProtocolExtensionContainer { { UE-MulticastMRBs-RequiredToBeReleased-Item-ExtIEs } } OPTIONAL + +} +``` + +``` +UE-MulticastMRBs-RequiredToBeReleased-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +UE-MulticastMRBs-Setup-Item ::= SEQUENCE { +``` + +``` + mRB-ID MRB-ID, +``` + +``` + multicastFlUContextReferenceCU MulticastFlUContextReferenceCU, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { UE-MulticastMRBs-Setup-Item-ExtIEs } } OPTIONAL +``` + +``` +} +``` + +``` +UE-MulticastMRBs-Setup-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +UE-MulticastMRBs-Setupnew-Item ::= SEQUENCE { +``` + +``` + mRB-ID MRB-ID, +``` + +``` + multicastFlUContextReferenceCU MulticastFlUContextReferenceCU, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { UE-MulticastMRBs-Setupnew-Item-ExtIEs } } OPTIONAL +``` + +``` +} +``` + +``` +UE-MulticastMRBs-Setupnew-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +UE-MulticastMRBs-ToBeReleased-Item ::= SEQUENCE { + mRB-ID MRB-ID, + iE-Extensions ProtocolExtensionContainer { { UE-MulticastMRBs-ToBeReleased-Item-ExtIEs } } OPTIONAL +} + +UE-MulticastMRBs-ToBeReleased-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +UE-MulticastMRBs-ToBeSetup-Item ::= SEQUENCE { + mRB-ID MRB-ID, + mbsPTPRetransmissionTunnelRequired MBSPTPRetransmissionTunnelRequired OPTIONAL, + mbsPTPForwardingRequiredInformation MRB-ProgressInformation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UE-MulticastMRBs-ToBeSetup-Item-ExtIEs } } OPTIONAL +} + +UE-MulticastMRBs-ToBeSetup-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-Source-MRB-ID CRITICALITY ignore EXTENSION MRB-ID PRESENCE optional }, + ... +} + +UE-MulticastMRBs-ToBeSetup-atModify-Item ::= SEQUENCE { + mRB-ID MRB-ID, +``` + +``` + mbsPTPRetransmissionTunnelRequired MBSPTPRetransmissionTunnelRequired OPTIONAL, + mbsPTPForwardingRequiredInformation MRB-ProgressInformation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UE-MulticastMRBs-ToBeSetup-atModify-Item-ExtIEs } } OPTIONAL +} +``` + +``` +UE-MulticastMRBs-ToBeSetup-atModify-Item-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +UEPagingCapability ::= SEQUENCE { + iNACTIVEStatePODeterminaton ENUMERATED {supported, ...} OPTIONAL, + iE-Extension ProtocolExtensionContainer { { UEPagingCapability-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +UEPagingCapability-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-RedCapIndication CRITICALITY ignore EXTENSION RedCapIndication PRESENCE optional }, + ... +} +``` + +``` +UEReportingInformation ::= SEQUENCE { + reportingAmount ENUMERATED {ma0, ma1, ma2, ma4, ma8, ma16, ma32, ma64}, + reportingInterval ENUMERATED {none, one, two, four, eight, ten, sixteen, twenty, thirty-two, sixty-four, ...}, +} +``` + +``` + iE-extensions ProtocolExtensionContainer { { UEReportingInformation-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +UEReportingInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +UlTxDirectCurrentMoreCarrierInformation ::= OCTET STRING +``` + +``` +UL-AoA ::= SEQUENCE { + azimuthAoA INTEGER (0..3599), + zenithAoA INTEGER (0..1799) OPTIONAL, + LCS-to-GCS-Translation LCS-to-GCS-Translation OPTIONAL, + iE-extensions ProtocolExtensionContainer { { UL-AoA-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +UL-AoA-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +UL-BH-Non-UP-Traffic-Mapping ::= SEQUENCE { + uL-BH-Non-UP-Traffic-Mapping-List UL-BH-Non-UP-Traffic-Mapping-List, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { UL-BH-Non-UP-Traffic-Mapping-ExtIEs } } OPTIONAL +} + +UL-BH-Non-UP-Traffic-Mapping-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-BH-Non-UP-Traffic-Mapping-List ::= SEQUENCE (SIZE(1..maxnoofNonUPTrafficMappings)) OF UL-BH-Non-UP-Traffic-Mapping-Item + +UL-BH-Non-UP-Traffic-Mapping-Item ::= SEQUENCE { + nonUPTrafficType NonUPTrafficType, + bHInfo BHInfo, + iE-Extensions ProtocolExtensionContainer { { UL-BH-Non-UP-Traffic-Mapping-ItemExtIEs } } OPTIONAL +} + +UL-BH-Non-UP-Traffic-Mapping-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +ULConfiguration ::= SEQUENCE { + uLUEConfiguration ULUEConfiguration, + iE-Extensions ProtocolExtensionContainer { { ULConfigurationExtIEs } } OPTIONAL, + ... +} +``` + +ULConfigurationExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +... + +} + +UL-GapFR2-Config ::= OCTET STRING + +UL-RTOA-Measurement ::= SEQUENCE { + +uL-RTOA-MeasurementItem UL-RTOA-MeasurementItem, + +additionalPath-List AdditionalPath-List OPTIONAL, + +iE-Extensions ProtocolExtensionContainer { { UL-RTOA-Measurement-ExtIEs } } OPTIONAL + +} + +UL-RTOA-Measurement-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + +{ ID id-ExtendedAdditionalPathList CRITICALITY ignore EXTENSION ExtendedAdditionalPathList PRESENCE optional}| + +{ ID id-TRPRx-TEGInformation CRITICALITY ignore EXTENSION TRP-Rx-TEGInformation PRESENCE optional}, + +... + +} + +UL-RTOA-MeasurementItem ::= CHOICE { + +k0 INTEGER (0..1970049), + +k1 INTEGER (0..985025), + +k2 INTEGER (0..492513), + +k3 INTEGER (0..246257), + +k4 INTEGER (0..123129), + +``` +k5 INTEGER (0..61565), +choice-extension ProtocolIE-SingleContainer { { UL-RTOA-MeasurementItem-ExtIEs } } +} + +UL-RTOA-MeasurementItem-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +UL-SRS-RSRP ::= INTEGER (0..126) + +UL-SRS-RSRPP ::= SEQUENCE { + firstPathRSRPP INTEGER (0..126), + iE-extensions ProtocolExtensionContainer { { UL-SRS-RSRPP-ExtIEs } } OPTIONAL, + ... +} + +UL-SRS-RSRPP-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +ULUEConfiguration ::= ENUMERATED {no-data, shared, only, ...} + +UL-UP-TNL-Information-to-Update-List-Item ::= SEQUENCE { +``` + +``` + uLUPTNLInformation UPTransportLayerInformation, + newULUPTNLInformation UPTransportLayerInformation OPTIONAL, + bHInfo BHInfo, + iE-Extensions ProtocolExtensionContainer { { UL-UP-TNL-Information-to-Update-List-ItemExtIEs } } OPTIONAL, + ... +} + +UL-UP-TNL-Information-to-Update-List-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-UP-TNL-Address-to-Update-List-Item ::= SEQUENCE { + oldIPAdress TransportLayerAddress, + newIPAdress TransportLayerAddress, + iE-Extensions ProtocolExtensionContainer { { UL-UP-TNL-Address-to-Update-List-ItemExtIEs } } OPTIONAL, + ... +} + +UL-UP-TNL-Address-to-Update-List-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +ULUPTNLInformation-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofULUPTNLInformation)) OF ULUPTNLInformation-ToBeSetup-Item +``` + +``` +ULUPtNLInformation-ToBeSetup-Item ::=SEQUENCE { + uUPtNLInformation UPTransportLayerInformation, + iE-Extensions ProtocolExtensionContainer { { ULUPtNLInformation-ToBeSetup-ItemExtIEs } } OPTIONAL, + ... +} +``` + +``` +ULUPtNLInformation-ToBeSetup-ItemExtIEs FLAP-PROTOCOL-EXTENSION ::= { + { ID id-BHInfo CRITICALITY ignore EXTENSION BHInfo PRESENCE optional }| + { ID id-DRBMappingInfo CRITICALITY ignore EXTENSION UuRLCChannelID PRESENCE optional }, + ... +} +``` + +``` +Uncertainty ::= INTEGER (0..32767, ...) +``` + +``` +UplinkChannelBW-PerSCS-List ::= SEQUENCE (SIZE (1..maxnoSCSs)) OF SCS-SpecificCarrier +``` + +``` +UplinkTxDirectCurrentListInformation ::= OCTET STRING +``` + +``` +UplinkTxDirectCurrentTwoCarrierListInfo ::= OCTET STRING +``` + +``` +UPTransportLayerInformation ::= CHOICE { + gTPTunnel GTPTunnel, + choice-extension ProtocolIE-SingleContainer { { UPTransportLayerInformation-ExtIEs } } +} +``` + +``` +UPTransportLayerInformation-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} + +URI-address ::= VisibleString + +Uncertainty-range-AoA ::= INTEGER (0..3599) + +Uncertainty-range-ZoA ::= INTEGER (0..1799) + +UuRLCChannelID ::= INTEGER (1..32) + +UuRLCChannelQoSInformation ::= CHOICE { + uuRLCChannelQoS QoSFlowLevelQoSParameters, + uuControlPlaneTrafficType ENUMERATED {srb0,srb1,srb2,...}, + choice-extension ProtocolIE-SingleContainer { { UuRLCChannelQoSInformation-ExtIEs} } +} + +UuRLCChannelQoSInformation-ExtIEs FLAP-PROTOCOL-IES ::= { + ... +} +``` + +UuRLCChannelToBeSetupList ::= SEQUENCE (SIZE(1.. maxnoofUuRLCChannels)) OF UuRLCChannelToBeSetupItem + +UuRLCChannelToBeSetupItem ::= SEQUENCE { +    uuRLCChannelID                    UuRLCChannelID, +    uuRLCChannelQoSInformation    UuRLCChannelQoSInformation, +    rLCMode                            RLCMode, +    iE-Extensions                    ProtocolExtensionContainer { { UuRLCChannelToBeSetupItem-ExtIEs } } OPTIONAL, +    ... +} + +UuRLCChannelToBeSetupItem-ExtIEs    FLAP-PROTOCOL-EXTENSION ::= { +    ... +} + +UuRLCChannelToBeModifiedList ::= SEQUENCE (SIZE(1.. maxnoofUuRLCChannels)) OF UuRLCChannelToBeModifiedItem + +UuRLCChannelToBeModifiedItem ::= SEQUENCE { +    uuRLCChannelID                    UuRLCChannelID, +    uuRLCChannelQoSInformation    UuRLCChannelQoSInformation            OPTIONAL, +    rLCMode                            RLCMode            OPTIONAL, +    iE-Extensions                    ProtocolExtensionContainer { { UuRLCChannelToBeModifiedItem-ExtIEs } } OPTIONAL, +    ... +} + +``` +UuRLCChannelToBeModifiedItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +UuRLCChannelToBeReleasedList ::= SEQUENCE (SIZE(1.. maxnoofUuRLCChannels)) OF UuRLCChannelToBeReleasedItem +``` + +``` +UuRLCChannelToBeReleasedItem ::= SEQUENCE { +``` + +``` + uuRLCChannelID UuRLCChannelID, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { UuRLCChannelToBeReleasedItem-ExtIEs } } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +UuRLCChannelToBeReleasedItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +UuRLCChannelSetupList ::= SEQUENCE (SIZE(1.. maxnoofUuRLCChannels)) OF UuRLCChannelSetupItem +``` + +``` +UuRLCChannelSetupItem ::= SEQUENCE { +``` + +``` + uuRLCChannelID UuRLCChannelID, +``` + +``` + iE-Extensions ProtocolExtensionContainer { { UuRLCChannelSetupItem-ExtIEs } } OPTIONAL, +``` + +``` + ... +``` + +``` +} +``` + +``` +UuRLCChannelSetupItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +UuRLCChannelFailedToBeSetupList ::= SEQUENCE (SIZE(1.. maxnoofUuRLCChannels)) OF UuRLCChannelFailedToBeSetupItem + +UuRLCChannelFailedToBeSetupItem ::= SEQUENCE { + uuRLCChannelID UuRLCChannelID, + cause Cause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UuRLCChannelFailedToBeSetupItem-ExtIEs } } OPTIONAL, + ... +} + +UuRLCChannelFailedToBeSetupItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +UuRLCChannelModifiedList ::= SEQUENCE (SIZE(1.. maxnoofUuRLCChannels)) OF UuRLCChannelModifiedItem + +UuRLCChannelModifiedItem ::= SEQUENCE { + uuRLCChannelID UuRLCChannelID, + iE-Extensions ProtocolExtensionContainer { { UuRLCChannelModifiedItem-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +UuRLCChannelModifiedItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +UuRLCChannelFailedToBeModifiedList ::= SEQUENCE (SIZE(1.. maxnoofUuRLCChannels)) OF UuRLCChannelFailedToBeModifiedItem + +UuRLCChannelFailedToBeModifiedItem ::= SEQUENCE { + uuRLCChannelID UuRLCChannelID, + cause Cause OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UuRLCChannelFailedToBeModifiedItem-ExtIEs } } OPTIONAL, + ... +} + +UuRLCChannelFailedToBeModifiedItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +UuRLCChannelRequiredToBeModifiedList ::= SEQUENCE (SIZE(1.. maxnoofUuRLCChannels)) OF UuRLCChannelRequiredToBeModifiedItem + +UuRLCChannelRequiredToBeModifiedItem ::= SEQUENCE { + uuRLCChannelID UuRLCChannelID, + iE-Extensions ProtocolExtensionContainer { { UuRLCChannelRequiredToBeModifiedItem-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +} + +UuRLCChannelRequiredToBeModifiedItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +UuRLCChannelRequiredToBeReleasedList ::= SEQUENCE (SIZE(1.. maxnoofUuRLCChannels)) OF UuRLCChannelRequiredToBeReleasedItem + +UuRLCChannelRequiredToBeReleasedItem ::= SEQUENCE { + uuRLCChannelID UuRLCChannelID, + iE-Extensions ProtocolExtensionContainer { { UuRLCChannelRequiredToBeReleasedItem-ExtIEs } } OPTIONAL, + ... +} + +UuRLCChannelRequiredToBeReleasedItem-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- V + +VictimgNBSetID ::= SEQUENCE { + victimgNBSetID GNBSetID, + iE-Extensions ProtocolExtensionContainer { { VictimgNBSetID-ExtIEs } } OPTIONAL +``` + +``` +} +``` + +``` +VictimNBSetID-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { +``` + +``` + ... +``` + +``` +} +``` + +``` +VehicleUE ::= ENUMERATED { +``` + +``` + authorized, +``` + +``` + not-authorized, +``` + +``` + ... +``` + +``` +} +``` + +``` +PedestrianUE ::= ENUMERATED { +``` + +``` + authorized, +``` + +``` + not-authorized, +``` + +``` + ... +``` + +``` +} +``` + +``` +-- V +``` + +``` +-- W +``` + +``` +-- X +``` + +-- Y + +-- Z + +``` + +ZoAInformation ::= SEQUENCE { + zenithAoA INTEGER (0..1799), + LCS-to-GCS-Translation LCS-to-GCS-Translation OPTIONAL, + iE-extensions ProtocolExtensionContainer { { ZoAInformation-ExtIEs } } OPTIONAL, + ... +} + +``` + +``` + +ZoAInformation-ExtIEs FLAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +END + +-- ASN1STOP + +## 9.4.6 Common Definitions + +-- ASN1START + +-- \*\*\*\*\* + +-- + +-- Common definitions + +-- + +-- \*\*\*\*\* + +FlAP-CommonDataTypes { + +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + +ngran-access (22) modules (3) flap (3) version1 (1) flap-CommonDataTypes (3) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +Criticality ::= ENUMERATED { reject, ignore, notify } + +Presence ::= ENUMERATED { optional, conditional, mandatory } + +PrivateIE-ID ::= CHOICE { + +local INTEGER (0..65535), + +global OBJECT IDENTIFIER + +} + +ProcedureCode ::= INTEGER (0..255) + +ProtocolExtensionID ::= INTEGER (0..65535) + +ProtocolIE-ID := INTEGER (0..65535) + +TriggeringMessage := ENUMERATED { initiating-message, successful-outcome, unsuccessful-outcome } + +END + +-- ASN1STOP + +## 9.4.7 Constant Definitions + +-- ASN1START + +-- \*\*\*\*\* + +-- + +-- Constant definitions + +-- + +-- \*\*\*\*\* + +Flap-Constants { + +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + +ngran-access (22) modules (3) flap (3) version1 (1) flap-Constants (4) } + +DEFINITIONS AUTOMATIC TAGS := + +BEGIN + +-- \*\*\*\*\* + +``` + +-- +-- IE parameter types from other modules. +-- +-- ************************************************************** + +``` + +IMPORTS + +``` + + ProcedureCode, + ProtocolIE-ID + +``` + +FROM F1AP-CommonDataTypes; + +``` + +-- ************************************************************** +-- +-- Elementary Procedures +-- +-- ************************************************************** + +``` + +``` + +id-Reset ProcedureCode ::= 0 +id-F1Setup ProcedureCode ::= 1 +id-ErrorIndication ProcedureCode ::= 2 +id-gNBDUConfigurationUpdate ProcedureCode ::= 3 +id-gNBCUConfigurationUpdate ProcedureCode ::= 4 +id-UEContextSetup ProcedureCode ::= 5 + +``` + +| | | +|-------------------------------------|----------------------| +| id-UEContextRelease | ProcedureCode ::= 6 | +| id-UEContextModification | ProcedureCode ::= 7 | +| id-UEContextModificationRequired | ProcedureCode ::= 8 | +| id-UEMobilityCommand | ProcedureCode ::= 9 | +| id-UEContextReleaseRequest | ProcedureCode ::= 10 | +| id-InitialULRRCMessageTransfer | ProcedureCode ::= 11 | +| id-DLRRCMessageTransfer | ProcedureCode ::= 12 | +| id-ULRRCMessageTransfer | ProcedureCode ::= 13 | +| id-privateMessage | ProcedureCode ::= 14 | +| id-UEInactivityNotification | ProcedureCode ::= 15 | +| id-GNBDUResourceCoordination | ProcedureCode ::= 16 | +| id-SystemInformationDeliveryCommand | ProcedureCode ::= 17 | +| id-Paging | ProcedureCode ::= 18 | +| id-Notify | ProcedureCode ::= 19 | +| id-WriteReplaceWarning | ProcedureCode ::= 20 | +| id-PWSCancel | ProcedureCode ::= 21 | +| id-PWSRestartIndication | ProcedureCode ::= 22 | +| id-PWSFailureIndication | ProcedureCode ::= 23 | +| id-GNBDUStatusIndication | ProcedureCode ::= 24 | +| id-RRCDeliveryReport | ProcedureCode ::= 25 | +| id-F1Removal | ProcedureCode ::= 26 | +| id-NetworkAccessRateReduction | ProcedureCode ::= 27 | +| id-TraceStart | ProcedureCode ::= 28 | +| id-DeactivateTrace | ProcedureCode ::= 29 | + +| | | +|---------------------------------------------|----------------------| +| id-DUCURadioInformationTransfer | ProcedureCode ::= 30 | +| id-CUDURadioInformationTransfer | ProcedureCode ::= 31 | +| id-BAPMappingConfiguration | ProcedureCode ::= 32 | +| id-GNBDUResourceConfiguration | ProcedureCode ::= 33 | +| id-IABTNLAddressAllocation | ProcedureCode ::= 34 | +| id-IABUPConfigurationUpdate | ProcedureCode ::= 35 | +| id-resourceStatusReportingInitiation | ProcedureCode ::= 36 | +| id-resourceStatusReporting | ProcedureCode ::= 37 | +| id-accessAndMobilityIndication | ProcedureCode ::= 38 | +| id-accessSuccess | ProcedureCode ::= 39 | +| id-cellTrafficTrace | ProcedureCode ::= 40 | +| id-PositioningMeasurementExchange | ProcedureCode ::= 41 | +| id-PositioningAssistanceInformationControl | ProcedureCode ::= 42 | +| id-PositioningAssistanceInformationFeedback | ProcedureCode ::= 43 | +| id-PositioningMeasurementReport | ProcedureCode ::= 44 | +| id-PositioningMeasurementAbort | ProcedureCode ::= 45 | +| id-PositioningMeasurementFailureIndication | ProcedureCode ::= 46 | +| id-PositioningMeasurementUpdate | ProcedureCode ::= 47 | +| id-TRPInformationExchange | ProcedureCode ::= 48 | +| id-PositioningInformationExchange | ProcedureCode ::= 49 | +| id-PositioningActivation | ProcedureCode ::= 50 | +| id-PositioningDeactivation | ProcedureCode ::= 51 | +| id-E-CIDMeasurementInitiation | ProcedureCode ::= 52 | +| id-E-CIDMeasurementFailureIndication | ProcedureCode ::= 53 | + +| | | +|---------------------------------------------|----------------------| +| id-E-CIDMeasurementReport | ProcedureCode ::= 54 | +| id-E-CIDMeasurementTermination | ProcedureCode ::= 55 | +| id-PositioningInformationUpdate | ProcedureCode ::= 56 | +| id-ReferenceTimeInformationReport | ProcedureCode ::= 57 | +| id-ReferenceTimeInformationReportingControl | ProcedureCode ::= 58 | +| id-BroadcastContextSetup | ProcedureCode ::= 59 | +| id-BroadcastContextRelease | ProcedureCode ::= 60 | +| id-BroadcastContextReleaseRequest | ProcedureCode ::= 61 | +| id-BroadcastContextModification | ProcedureCode ::= 62 | +| id-MulticastGroupPaging | ProcedureCode ::= 63 | +| id-MulticastContextSetup | ProcedureCode ::= 64 | +| id-MulticastContextRelease | ProcedureCode ::= 65 | +| id-MulticastContextReleaseRequest | ProcedureCode ::= 66 | +| id-MulticastContextModification | ProcedureCode ::= 67 | +| id-MulticastDistributionSetup | ProcedureCode ::= 68 | +| id-MulticastDistributionRelease | ProcedureCode ::= 69 | +| id-PDCMeasurementInitiation | ProcedureCode ::= 70 | +| id-PDCMeasurementReport | ProcedureCode ::= 71 | +| id-PDCMeasurementInitiationRequest | ProcedureCode ::= 72 | +| id-PDCMeasurementInitiationResponse | ProcedureCode ::= 73 | +| id-PDCMeasurementInitiationFailure | ProcedureCode ::= 74 | +| id-pRSConfigurationExchange | ProcedureCode ::= 75 | +| id-measurementPreconfiguration | ProcedureCode ::= 76 | +| id-measurementActivation | ProcedureCode ::= 77 | + +``` + +id-QoEInformationTransfer ProcedureCode ::= 78 +id-PDCMeasurementTerminationCommand ProcedureCode ::= 79 +id-PDCMeasurementFailureIndication ProcedureCode ::= 80 +id-PosSystemInformationDeliveryCommand ProcedureCode ::= 81 +id-DUCUCellSwitchNotification ProcedureCode ::= 82 +id-CUDUCellSwitchNotification ProcedureCode ::= 83 +id-DUCUTAInformationTransfer ProcedureCode ::= 84 +id-CUDUTAInformationTransfer ProcedureCode ::= 85 +id-QoEInformationTransferControl ProcedureCode ::= 86 +id-RachIndication ProcedureCode ::= 87 +id-TimingSynchronisationStatus ProcedureCode ::= 88 +id-TimingSynchronisationStatusReport ProcedureCode ::= 89 +id-MIABF1SetupTriggering ProcedureCode ::= 90 +id-MIABF1SetupOutcomeNotification ProcedureCode ::= 91 +id-MulticastContextNotification ProcedureCode ::= 92 +id-MulticastCommonConfiguration ProcedureCode ::= 93 +id-BroadcastTransportResourceRequest ProcedureCode ::= 94 + +``` + +``` + +-- ***** +-- +-- Extension constants +-- +-- ***** + +``` + +``` +maxPrivateIEs INTEGER ::= 65535 +maxProtocolExtensions INTEGER ::= 65535 +maxProtocolIEs INTEGER ::= 65535 + +-- ***** +-- +-- Lists +-- +-- ***** + +maxNRARFCN INTEGER ::= 3279165 +maxnoofErrors INTEGER ::= 256 +maxnoofIndividualFlConnectionsToReset INTEGER ::= 65536 +maxCeilingNBDU INTEGER ::= 512 +maxnoofSCells INTEGER ::= 32 +maxnoofSRBs INTEGER ::= 8 +maxnoofDRBs INTEGER ::= 64 +maxnoofULUPTNLInformation INTEGER ::= 2 +maxnoofDLUPTNLInformation INTEGER ::= 2 +maxnoofBPLMNs INTEGER ::= 6 +maxnoofCandidateSpCells INTEGER ::= 64 +maxnoofPotentialSpCells INTEGER ::= 64 +maxnoofNrCellBands INTEGER ::= 32 +maxnoofSIBTypes INTEGER ::= 32 +``` + +| | | +|------------------------|-------------------| +| maxnoofSITypes | INTEGER ::= 32 | +| maxnoofPagingCells | INTEGER ::= 512 | +| maxnoofTNLAssociations | INTEGER ::= 32 | +| maxnoofQoSFlows | INTEGER ::= 64 | +| maxnoofSliceItems | INTEGER ::= 1024 | +| maxCellineNB | INTEGER ::= 256 | +| maxnoofExtendedBPLMNs | INTEGER ::= 6 | +| maxnoofUEIDs | INTEGER ::= 65536 | +| maxnoofBPLMNsNR | INTEGER ::= 12 | +| maxnoofUACPLMNs | INTEGER ::= 12 | +| maxnoofUACperPLMN | INTEGER ::= 64 | +| maxnoofAdditionalSIBs | INTEGER ::= 63 | +| maxnoofslots | INTEGER ::= 5120 | +| maxnoofTLAs | INTEGER ::= 16 | +| maxnoofGTPTLAs | INTEGER ::= 16 | +| maxnoofBHRLCChannels | INTEGER ::= 65536 | +| maxnoofRoutingEntries | INTEGER ::= 1024 | +| maxnoofIABSTCInfo | INTEGER ::= 45 | +| maxnoofSymbols | INTEGER ::= 14 | +| maxnoofServingCells | INTEGER ::= 32 | +| maxnoofDUFSlots | INTEGER ::= 320 | +| maxnoofHSNASlots | INTEGER ::= 5120 | +| maxnoofServedCellsIAB | INTEGER ::= 512 | +| maxnoofSSBarea | INTEGER ::= 64 | + +| | | +|-------------------------------------|----------------------| +| maxnoofChildIABNodes | INTEGER ::= 1024 | +| maxnoofNonUPTrafficMappings | INTEGER ::= 32 | +| maxnoofTLAsIAB | INTEGER ::= 1024 | +| maxnoofMappingEntries | INTEGER ::= 67108864 | +| maxnoofDSInfo | INTEGER ::= 64 | +| maxnoofEgressLinks | INTEGER ::= 2 | +| maxnoofULUPTNLInformationforIAB | INTEGER ::= 32678 | +| maxnoofUPTNLAddresses | INTEGER ::= 8 | +| maxnoofSLDRBs | INTEGER ::= 512 | +| maxnoofQoSParaSets | INTEGER ::= 8 | +| maxnoofPC5QoSFlows | INTEGER ::= 2048 | +| maxnoofSSBAreas | INTEGER ::= 64 | +| maxnoofPhysicalResourceBlocks | INTEGER ::= 275 | +| maxnoofPhysicalResourceBlocks-1 | INTEGER ::= 274 | +| maxnoofPRACHconfigs | INTEGER ::= 16 | +| maxnoofRReports | INTEGER ::= 64 | +| maxnoofRLFReports | INTEGER ::= 64 | +| maxnoofAdditionalPDCPDuplicationTNL | INTEGER ::= 2 | +| maxnoofRLCDuplicationState | INTEGER ::= 3 | +| maxnoofCHOCells | INTEGER ::= 8 | +| maxnoofMDTPLMNs | INTEGER ::= 16 | +| maxnoofCAGsupported | INTEGER ::= 12 | +| maxnoofNIDsupported | INTEGER ::= 12 | +| maxnoofNRSCSs | INTEGER ::= 5 | + +| | | +|----------------------------|-------------------| +| maxnoofExtSliceItems | INTEGER ::= 65535 | +| maxnoofPosMeas | INTEGER ::= 16384 | +| maxnoofTRPInfoTypes | INTEGER ::= 64 | +| maxnoofTRPs | INTEGER ::= 65535 | +| maxnoofSRSTriggerStates | INTEGER ::= 3 | +| maxnoofSpatialRelations | INTEGER ::= 64 | +| maxnoBcastCell | INTEGER ::= 16384 | +| maxnoofAngleInfo | INTEGER ::= 65535 | +| maxnooflcs-gcs-translation | INTEGER ::= 3 | +| maxnoofPath | INTEGER ::= 2 | +| maxnoofMeasE-CID | INTEGER ::= 64 | +| maxnoofSSBs | INTEGER ::= 255 | +| maxnoSRS-ResourceSets | INTEGER ::= 16 | +| maxnoSRS-ResourcePerSet | INTEGER ::= 16 | +| maxnoSRS-Carriers | INTEGER ::= 32 | +| maxnoSCSs | INTEGER ::= 5 | +| maxnoSRS-Resources | INTEGER ::= 64 | +| maxnoSRS-PosResources | INTEGER ::= 64 | +| maxnoSRS-PosResourceSets | INTEGER ::= 16 | +| maxnoSRS-PosResourcePerSet | INTEGER ::= 16 | +| maxnoofPRS-ResourceSets | INTEGER ::= 2 | +| maxnoofPRS-ResourcesPerSet | INTEGER ::= 64 | +| maxNoOfMeasTRPs | INTEGER ::= 64 | +| maxnoofPRSresourceSets | INTEGER ::= 8 | + +| | | +|----------------------------------|------------------| +| maxnoofPRresources | INTEGER ::= 64 | +| maxnoofSuccessfulHOReports | INTEGER ::= 64 | +| maxnoofNR-UchannelIDs | INTEGER ::= 16 | +| maxServedCellforSON | INTEGER ::= 256 | +| maxNeighbourCellforSON | INTEGER ::= 32 | +| maxAffectedCells | INTEGER ::= 32 | +| maxnoofMRBs | INTEGER ::= 32 | +| maxnoofMBSQoSFlows | INTEGER ::= 64 | +| maxnoofMBSFSA | INTEGER ::= 256 | +| maxnoofUEIDforPaging | INTEGER ::= 4096 | +| maxnoofCellsforMBS | INTEGER ::= 512 | +| maxnoofTAIforMBS | INTEGER ::= 512 | +| maxnoofMBSAreaSessionIDs | INTEGER ::= 256 | +| maxnoofMBSServiceAreaInformation | INTEGER ::= 256 | +| maxnoofIABCongInd | INTEGER ::= 1024 | +| maxnoofNeighbourNodeCellsIAB | INTEGER ::= 1024 | +| maxnoofRBsetsPerCell | INTEGER ::= 8 | +| maxnoofRBsetsPerCell-1 | INTEGER ::= 7 | +| maxnoofMeasPDC | INTEGER ::= 16 | +| maxnoARPs | INTEGER ::= 16 | +| maxnoofULAcAs | INTEGER ::= 8 | +| maxNoPathExtended | INTEGER ::= 8 | +| maxnoTRPTEGs | INTEGER ::= 8 | +| maxFreqLayers | INTEGER ::= 4 | + +| | | +|---------------------------------------|------------------| +| maxNumResourcesPerAngle | INTEGER ::= 24 | +| maxnoAzimuthAngles | INTEGER ::= 3600 | +| maxnoElevationAngles | INTEGER ::= 1801 | +| maxnoofPRSTRPs | INTEGER ::= 256 | +| maxnoofQoEInformation | INTEGER ::= 16 | +| maxnoofUuRLCChannels | INTEGER ::= 32 | +| maxnoofPC5RLCChannels | INTEGER ::= 512 | +| maxnoofSMBRValues | INTEGER ::= 8 | +| maxnoofMRBsforUE | INTEGER ::= 64 | +| maxnoofMBSSessionsofUE | INTEGER ::= 256 | +| maxnoofSLdestinations | INTEGER ::= 32 | +| maxnoofNSAGs | INTEGER ::= 256 | +| maxnoofSDTBearers | INTEGER ::= 72 | +| maxnoofServingCellMOs | INTEGER ::= 16 | +| maxNrofBWPsp | INTEGER ::= 8 | +| maxnoofPosSITypes | INTEGER ::= 32 | +| maxnoofUETypes | INTEGER ::= 8 | +| maxnoofLTMCells | INTEGER ::= 8 | +| maxnoofJointorDLTCIStates | INTEGER ::= 128 | +| maxnoofULTCIStates | INTEGER ::= 64 | +| maxnoofTAList | INTEGER ::= 8 | +| maxnoofUEsInQMCTransferControlMessage | INTEGER ::= 512 | +| maxnoofUEsforRAReportIndications | INTEGER ::= 64 | +| maxnoofSuccessfulPSCellChangeReports | INTEGER ::= 64 | +| maxnoofPeriodicities | INTEGER ::= 8 | + +``` + +maxnoofThresholdMBS INTEGER ::= 64 +maxMBSSessionsinSessionInfoList INTEGER ::= 1024 + +``` + +``` + +-- ***** +-- +-- IEs +-- +-- ***** + +``` + +``` + +id-Cause ProtocolIE-ID ::= 0 +id-Cells-Failed-to-be-Activated-List ProtocolIE-ID ::= 1 +id-Cells-Failed-to-be-Activated-List-Item ProtocolIE-ID ::= 2 +id-Cells-to-be-Activated-List ProtocolIE-ID ::= 3 +id-Cells-to-be-Activated-List-Item ProtocolIE-ID ::= 4 +id-Cells-to-be-Deactivated-List ProtocolIE-ID ::= 5 +id-Cells-to-be-Deactivated-List-Item ProtocolIE-ID ::= 6 +id-CriticalityDiagnostics ProtocolIE-ID ::= 7 +id-CUtoDURRCInformation ProtocolIE-ID ::= 9 +id-DRBs-FailedToBeModified-Item ProtocolIE-ID ::= 12 + +``` + +| | | +|------------------------------------|----------------------| +| id-DRBs-FailedToBeModified-List | ProtocolIE-ID ::= 13 | +| id-DRBs-FailedToBeSetup-Item | ProtocolIE-ID ::= 14 | +| id-DRBs-FailedToBeSetup-List | ProtocolIE-ID ::= 15 | +| id-DRBs-FailedToBeSetupMod-Item | ProtocolIE-ID ::= 16 | +| id-DRBs-FailedToBeSetupMod-List | ProtocolIE-ID ::= 17 | +| id-DRBs-ModifiedConf-Item | ProtocolIE-ID ::= 18 | +| id-DRBs-ModifiedConf-List | ProtocolIE-ID ::= 19 | +| id-DRBs-Modified-Item | ProtocolIE-ID ::= 20 | +| id-DRBs-Modified-List | ProtocolIE-ID ::= 21 | +| id-DRBs-Required-ToBeModified-Item | ProtocolIE-ID ::= 22 | +| id-DRBs-Required-ToBeModified-List | ProtocolIE-ID ::= 23 | +| id-DRBs-Required-ToBeReleased-Item | ProtocolIE-ID ::= 24 | +| id-DRBs-Required-ToBeReleased-List | ProtocolIE-ID ::= 25 | +| id-DRBs-Setup-Item | ProtocolIE-ID ::= 26 | +| id-DRBs-Setup-List | ProtocolIE-ID ::= 27 | +| id-DRBs-SetupMod-Item | ProtocolIE-ID ::= 28 | +| id-DRBs-SetupMod-List | ProtocolIE-ID ::= 29 | +| id-DRBs-ToBeModified-Item | ProtocolIE-ID ::= 30 | +| id-DRBs-ToBeModified-List | ProtocolIE-ID ::= 31 | +| id-DRBs-ToBeReleased-Item | ProtocolIE-ID ::= 32 | +| id-DRBs-ToBeReleased-List | ProtocolIE-ID ::= 33 | +| id-DRBs-ToBeSetup-Item | ProtocolIE-ID ::= 34 | +| id-DRBs-ToBeSetup-List | ProtocolIE-ID ::= 35 | +| id-DRBs-ToBeSetupMod-Item | ProtocolIE-ID ::= 36 | + +| | | +|------------------------------------------|----------------------| +| id-DRBs-ToBeSetupMod-List | ProtocolIE-ID ::= 37 | +| id-DRXCycle | ProtocolIE-ID ::= 38 | +| id-DUtoCURRCInformation | ProtocolIE-ID ::= 39 | +| id-gNB-CU-UE-FlAP-ID | ProtocolIE-ID ::= 40 | +| id-gNB-DU-UE-FlAP-ID | ProtocolIE-ID ::= 41 | +| id-gNB-DU-ID | ProtocolIE-ID ::= 42 | +| id-GNB-DU-Served-Cells-Item | ProtocolIE-ID ::= 43 | +| id-gNB-DU-Served-Cells-List | ProtocolIE-ID ::= 44 | +| id-gNB-DU-Name | ProtocolIE-ID ::= 45 | +| id-NRCellID | ProtocolIE-ID ::= 46 | +| id-oldgNB-DU-UE-FlAP-ID | ProtocolIE-ID ::= 47 | +| id-ResetType | ProtocolIE-ID ::= 48 | +| id-ResourceCoordinationTransferContainer | ProtocolIE-ID ::= 49 | +| id-RRCContainer | ProtocolIE-ID ::= 50 | +| id-SCell-ToBeRemoved-Item | ProtocolIE-ID ::= 51 | +| id-SCell-ToBeRemoved-List | ProtocolIE-ID ::= 52 | +| id-SCell-ToBeSetup-Item | ProtocolIE-ID ::= 53 | +| id-SCell-ToBeSetup-List | ProtocolIE-ID ::= 54 | +| id-SCell-ToBeSetupMod-Item | ProtocolIE-ID ::= 55 | +| id-SCell-ToBeSetupMod-List | ProtocolIE-ID ::= 56 | +| id-Served-Cells-To-Add-Item | ProtocolIE-ID ::= 57 | +| id-Served-Cells-To-Add-List | ProtocolIE-ID ::= 58 | +| id-Served-Cells-To-Delete-Item | ProtocolIE-ID ::= 59 | +| id-Served-Cells-To-Delete-List | ProtocolIE-ID ::= 60 | + +| | | +|------------------------------------------------|----------------------| +| id-Served-Cells-To-Modify-Item | ProtocolIE-ID ::= 61 | +| id-Served-Cells-To-Modify-List | ProtocolIE-ID ::= 62 | +| id-SpCell-ID | ProtocolIE-ID ::= 63 | +| id-SRBID | ProtocolIE-ID ::= 64 | +| id-SRBs-FailedToBeSetup-Item | ProtocolIE-ID ::= 65 | +| id-SRBs-FailedToBeSetup-List | ProtocolIE-ID ::= 66 | +| id-SRBs-FailedToBeSetupMod-Item | ProtocolIE-ID ::= 67 | +| id-SRBs-FailedToBeSetupMod-List | ProtocolIE-ID ::= 68 | +| id-SRBs-Required-ToBeReleased-Item | ProtocolIE-ID ::= 69 | +| id-SRBs-Required-ToBeReleased-List | ProtocolIE-ID ::= 70 | +| id-SRBs-ToBeReleased-Item | ProtocolIE-ID ::= 71 | +| id-SRBs-ToBeReleased-List | ProtocolIE-ID ::= 72 | +| id-SRBs-ToBeSetup-Item | ProtocolIE-ID ::= 73 | +| id-SRBs-ToBeSetup-List | ProtocolIE-ID ::= 74 | +| id-SRBs-ToBeSetupMod-Item | ProtocolIE-ID ::= 75 | +| id-SRBs-ToBeSetupMod-List | ProtocolIE-ID ::= 76 | +| id-TimeToWait | ProtocolIE-ID ::= 77 | +| id-TransactionID | ProtocolIE-ID ::= 78 | +| id-TransmissionActionIndicator | ProtocolIE-ID ::= 79 | +| id-UE-associatedLogicalFl-ConnectionItem | ProtocolIE-ID ::= 80 | +| id-UE-associatedLogicalFl-ConnectionListResAck | ProtocolIE-ID ::= 81 | +| id-gNB-CU-Name | ProtocolIE-ID ::= 82 | +| id-SCell-FailedtoSetup-List | ProtocolIE-ID ::= 83 | +| id-SCell-FailedtoSetup-Item | ProtocolIE-ID ::= 84 | + +| | | +|------------------------------------------------------|-----------------------| +| id-SCell-FailedtoSetupMod-List | ProtocolIE-ID ::= 85 | +| id-SCell-FailedtoSetupMod-Item | ProtocolIE-ID ::= 86 | +| id-RRCReconfigurationCompleteIndicator | ProtocolIE-ID ::= 87 | +| id-Cells-Status-Item | ProtocolIE-ID ::= 88 | +| id-Cells-Status-List | ProtocolIE-ID ::= 89 | +| id-Candidate-SpCell-List | ProtocolIE-ID ::= 90 | +| id-Candidate-SpCell-Item | ProtocolIE-ID ::= 91 | +| id-Potential-SpCell-List | ProtocolIE-ID ::= 92 | +| id-Potential-SpCell-Item | ProtocolIE-ID ::= 93 | +| id-FullConfiguration | ProtocolIE-ID ::= 94 | +| id-C-RNTI | ProtocolIE-ID ::= 95 | +| id-SpCellULConfigured | ProtocolIE-ID ::= 96 | +| id-InactivityMonitoringRequest | ProtocolIE-ID ::= 97 | +| id-InactivityMonitoringResponse | ProtocolIE-ID ::= 98 | +| id-DRB-Activity-Item | ProtocolIE-ID ::= 99 | +| id-DRB-Activity-List | ProtocolIE-ID ::= 100 | +| id-EUTRA-NR-CellResourceCoordinationReq-Container | ProtocolIE-ID ::= 101 | +| id-EUTRA-NR-CellResourceCoordinationReqAck-Container | ProtocolIE-ID ::= 102 | +| id-Protected-EUTRA-Resources-List | ProtocolIE-ID ::= 105 | +| id-RequestType | ProtocolIE-ID ::= 106 | +| id-ServCellIndex | ProtocolIE-ID ::= 107 | +| id-RAT-FrequencyPriorityInformation | ProtocolIE-ID ::= 108 | +| id-ExecuteDuplication | ProtocolIE-ID ::= 109 | +| id-NRCGI | ProtocolIE-ID ::= 111 | + +| | | +|------------------------------------------------|-----------------------| +| id-PagingCell-Item | ProtocolIE-ID ::= 112 | +| id-PagingCell-List | ProtocolIE-ID ::= 113 | +| id-PagingDRX | ProtocolIE-ID ::= 114 | +| id-PagingPriority | ProtocolIE-ID ::= 115 | +| id-SIType-List | ProtocolIE-ID ::= 116 | +| id-UEIdentityIndexValue | ProtocolIE-ID ::= 117 | +| id-gNB-CUSystemInformation | ProtocolIE-ID ::= 118 | +| id-HandoverPreparationInformation | ProtocolIE-ID ::= 119 | +| id-GNB-CU-TNL-Association-To-Add-Item | ProtocolIE-ID ::= 120 | +| id-GNB-CU-TNL-Association-To-Add-List | ProtocolIE-ID ::= 121 | +| id-GNB-CU-TNL-Association-To-Remove-Item | ProtocolIE-ID ::= 122 | +| id-GNB-CU-TNL-Association-To-Remove-List | ProtocolIE-ID ::= 123 | +| id-GNB-CU-TNL-Association-To-Update-Item | ProtocolIE-ID ::= 124 | +| id-GNB-CU-TNL-Association-To-Update-List | ProtocolIE-ID ::= 125 | +| id-MaskedIMEISV | ProtocolIE-ID ::= 126 | +| id-PagingIdentity | ProtocolIE-ID ::= 127 | +| id-DUtoCURRCCContainer | ProtocolIE-ID ::= 128 | +| id-Cells-to-be-Barred-List | ProtocolIE-ID ::= 129 | +| id-Cells-to-be-Barred-Item | ProtocolIE-ID ::= 130 | +| id-TAISliceSupportList | ProtocolIE-ID ::= 131 | +| id-GNB-CU-TNL-Association-Setup-List | ProtocolIE-ID ::= 132 | +| id-GNB-CU-TNL-Association-Setup-Item | ProtocolIE-ID ::= 133 | +| id-GNB-CU-TNL-Association-Failed-To-Setup-List | ProtocolIE-ID ::= 134 | +| id-GNB-CU-TNL-Association-Failed-To-Setup-Item | ProtocolIE-ID ::= 135 | + +| | | +|------------------------------------------|-----------------------| +| id-DRB-Notify-Item | ProtocolIE-ID ::= 136 | +| id-DRB-Notify-List | ProtocolIE-ID ::= 137 | +| id-NotificationControl | ProtocolIE-ID ::= 138 | +| id-RANAC | ProtocolIE-ID ::= 139 | +| id-PWSSystemInformation | ProtocolIE-ID ::= 140 | +| id-RepetitionPeriod | ProtocolIE-ID ::= 141 | +| id-NumberOfBroadcastRequest | ProtocolIE-ID ::= 142 | +| id-Cells-To-Be-Broadcast-List | ProtocolIE-ID ::= 144 | +| id-Cells-To-Be-Broadcast-Item | ProtocolIE-ID ::= 145 | +| id-Cells-Broadcast-Completed-List | ProtocolIE-ID ::= 146 | +| id-Cells-Broadcast-Completed-Item | ProtocolIE-ID ::= 147 | +| id-Broadcast-To-Be-Cancelled-List | ProtocolIE-ID ::= 148 | +| id-Broadcast-To-Be-Cancelled-Item | ProtocolIE-ID ::= 149 | +| id-Cells-Broadcast-Cancelled-List | ProtocolIE-ID ::= 150 | +| id-Cells-Broadcast-Cancelled-Item | ProtocolIE-ID ::= 151 | +| id-NR-CGI-List-For-Restart-List | ProtocolIE-ID ::= 152 | +| id-NR-CGI-List-For-Restart-Item | ProtocolIE-ID ::= 153 | +| id-PWS-Failed-NR-CGI-List | ProtocolIE-ID ::= 154 | +| id-PWS-Failed-NR-CGI-Item | ProtocolIE-ID ::= 155 | +| id-ConfirmedUEID | ProtocolIE-ID ::= 156 | +| id-Cancel-all-Warning-Messages-Indicator | ProtocolIE-ID ::= 157 | +| id-GNB-DU-UE-AMBR-UL | ProtocolIE-ID ::= 158 | +| id-DRXConfigurationIndicator | ProtocolIE-ID ::= 159 | +| id-RLC-Status | ProtocolIE-ID ::= 160 | + +| | | +|-----------------------------------------|-----------------------| +| id-DLPDCPSNLength | ProtocolIE-ID ::= 161 | +| id-GNB-DUConfigurationQuery | ProtocolIE-ID ::= 162 | +| id-MeasurementTimingConfiguration | ProtocolIE-ID ::= 163 | +| id-DRB-Information | ProtocolIE-ID ::= 164 | +| id-ServingPLMN | ProtocolIE-ID ::= 165 | +| id-Protected-EUTRA-Resources-Item | ProtocolIE-ID ::= 168 | +| id-GNB-CU-RRC-Version | ProtocolIE-ID ::= 170 | +| id-GNB-DU-RRC-Version | ProtocolIE-ID ::= 171 | +| id-GNBDOOverloadInformation | ProtocolIE-ID ::= 172 | +| id-CellGroupConfig | ProtocolIE-ID ::= 173 | +| id-RLCFailureIndication | ProtocolIE-ID ::= 174 | +| id-UplinkTxDirectCurrentListInformation | ProtocolIE-ID ::= 175 | +| id-DC-Based-Duplication-Configured | ProtocolIE-ID ::= 176 | +| id-DC-Based-Duplication-Activation | ProtocolIE-ID ::= 177 | +| id-SULAccessIndication | ProtocolIE-ID ::= 178 | +| id-AvailablePLMNList | ProtocolIE-ID ::= 179 | +| id-PDUSessionID | ProtocolIE-ID ::= 180 | +| id-ULPDUSessionAggregateMaximumBitRate | ProtocolIE-ID ::= 181 | +| id-ServingCellMO | ProtocolIE-ID ::= 182 | +| id-QoSFlowMappingIndication | ProtocolIE-ID ::= 183 | +| id-RRCDeliveryStatusRequest | ProtocolIE-ID ::= 184 | +| id-RRCDeliveryStatus | ProtocolIE-ID ::= 185 | +| id-BearerTypeChange | ProtocolIE-ID ::= 186 | +| id-RLCMode | ProtocolIE-ID ::= 187 | + +| | | +|--------------------------------------------|-----------------------| +| id-Duplication-Activation | ProtocolIE-ID ::= 188 | +| id-Dedicated-SIDelivery-NeededUE-List | ProtocolIE-ID ::= 189 | +| id-Dedicated-SIDelivery-NeededUE-Item | ProtocolIE-ID ::= 190 | +| id-DRX-LongCycleStartOffset | ProtocolIE-ID ::= 191 | +| id-ULPDCPSNLength | ProtocolIE-ID ::= 192 | +| id-SelectedBandCombinationIndex | ProtocolIE-ID ::= 193 | +| id-SelectedFeatureSetEntryIndex | ProtocolIE-ID ::= 194 | +| id-ResourceCoordinationTransferInformation | ProtocolIE-ID ::= 195 | +| id-ExtendedServedPLMNs-List | ProtocolIE-ID ::= 196 | +| id-ExtendedAvailablePLMN-List | ProtocolIE-ID ::= 197 | +| id-Associated-SCell-List | ProtocolIE-ID ::= 198 | +| id-latest-RRC-Version-Enhanced | ProtocolIE-ID ::= 199 | +| id-Associated-SCell-Item | ProtocolIE-ID ::= 200 | +| id-Cell-Direction | ProtocolIE-ID ::= 201 | +| id-SRBs-Setup-List | ProtocolIE-ID ::= 202 | +| id-SRBs-Setup-Item | ProtocolIE-ID ::= 203 | +| id-SRBs-SetupMod-List | ProtocolIE-ID ::= 204 | +| id-SRBs-SetupMod-Item | ProtocolIE-ID ::= 205 | +| id-SRBs-Modified-List | ProtocolIE-ID ::= 206 | +| id-SRBs-Modified-Item | ProtocolIE-ID ::= 207 | +| id-Ph-InfoSCG | ProtocolIE-ID ::= 208 | +| id-RequestedBandCombinationIndex | ProtocolIE-ID ::= 209 | +| id-RequestedFeatureSetEntryIndex | ProtocolIE-ID ::= 210 | +| id-RequestedP-MaxFR2 | ProtocolIE-ID ::= 211 | + +| | | +|----------------------------------------------|-----------------------| +| id-DRX-Config | ProtocolIE-ID ::= 212 | +| id-IgnoreResourceCoordinationContainer | ProtocolIE-ID ::= 213 | +| id-UEAssistanceInformation | ProtocolIE-ID ::= 214 | +| id-NeedforGap | ProtocolIE-ID ::= 215 | +| id-PagingOrigin | ProtocolIE-ID ::= 216 | +| id-new-gNB-CU-UE-FLAP-ID | ProtocolIE-ID ::= 217 | +| id-RedirectedRRcmessage | ProtocolIE-ID ::= 218 | +| id-new-gNB-DU-UE-FLAP-ID | ProtocolIE-ID ::= 219 | +| id-NotificationInformation | ProtocolIE-ID ::= 220 | +| id-PLMNAssistanceInfoForNetShar | ProtocolIE-ID ::= 221 | +| id-UEContextNotRetrievable | ProtocolIE-ID ::= 222 | +| id-BPLMN-ID-Info-List | ProtocolIE-ID ::= 223 | +| id-SelectedPLMNID | ProtocolIE-ID ::= 224 | +| id-UAC-Assistance-Info | ProtocolIE-ID ::= 225 | +| id-RANUEID | ProtocolIE-ID ::= 226 | +| id-GNB-DU-TNL-Association-To-Remove-Item | ProtocolIE-ID ::= 227 | +| id-GNB-DU-TNL-Association-To-Remove-List | ProtocolIE-ID ::= 228 | +| id-TNLAssociationTransportLayerAddressgNBUDU | ProtocolIE-ID ::= 229 | +| id-portNumber | ProtocolIE-ID ::= 230 | +| id-AdditionalSIBMessageList | ProtocolIE-ID ::= 231 | +| id-Cell-Type | ProtocolIE-ID ::= 232 | +| id-IgnorePRACHConfiguration | ProtocolIE-ID ::= 233 | +| id-CG-Config | ProtocolIE-ID ::= 234 | +| id-PDCCH-BlindDetectionSCG | ProtocolIE-ID ::= 235 | + +| | | +|--------------------------------------|-----------------------| +| id-Requested-PDCCH-BlindDetectionSCG | ProtocolIE-ID ::= 236 | +| id-Ph-InfoMCG | ProtocolIE-ID ::= 237 | +| id-MeasGapSharingConfig | ProtocolIE-ID ::= 238 | +| id-systemInformationAreaID | ProtocolIE-ID ::= 239 | +| id-areaScope | ProtocolIE-ID ::= 240 | +| id-RRCContainer-RRCSsetupComplete | ProtocolIE-ID ::= 241 | +| id-TraceActivation | ProtocolIE-ID ::= 242 | +| id-TraceID | ProtocolIE-ID ::= 243 | +| id-Neighbour-Cell-Information-List | ProtocolIE-ID ::= 244 | +| id-SymbolAllocInSlot | ProtocolIE-ID ::= 246 | +| id-NumDLULSymbols | ProtocolIE-ID ::= 247 | +| id-AdditionalRRMPriorityIndex | ProtocolIE-ID ::= 248 | +| id-DUCURadioInformationType | ProtocolIE-ID ::= 249 | +| id-CUDURadioInformationType | ProtocolIE-ID ::= 250 | +| id-AggressorNBSetID | ProtocolIE-ID ::= 251 | +| id-VictimNBSetID | ProtocolIE-ID ::= 252 | +| id-LowerLayerPresenceStatusChange | ProtocolIE-ID ::= 253 | +| id-Transport-Layer-Address-Info | ProtocolIE-ID ::= 254 | +| id-Neighbour-Cell-Information-Item | ProtocolIE-ID ::= 255 | +| id-IntendedTDD-DL-ULConfig | ProtocolIE-ID ::= 256 | +| id-QosMonitoringRequest | ProtocolIE-ID ::= 257 | +| id-BHChannels-ToBeSetup-List | ProtocolIE-ID ::= 258 | +| id-BHChannels-ToBeSetup-Item | ProtocolIE-ID ::= 259 | +| id-BHChannels-Setup-List | ProtocolIE-ID ::= 260 | + +| | | +|-------------------------------------------|-----------------------| +| id-BHChannels-Setup-Item | ProtocolIE-ID ::= 261 | +| id-BHChannels-ToBeModified-Item | ProtocolIE-ID ::= 262 | +| id-BHChannels-ToBeModified-List | ProtocolIE-ID ::= 263 | +| id-BHChannels-ToBeReleased-Item | ProtocolIE-ID ::= 264 | +| id-BHChannels-ToBeReleased-List | ProtocolIE-ID ::= 265 | +| id-BHChannels-ToBeSetupMod-Item | ProtocolIE-ID ::= 266 | +| id-BHChannels-ToBeSetupMod-List | ProtocolIE-ID ::= 267 | +| id-BHChannels-FailedToBeModified-Item | ProtocolIE-ID ::= 268 | +| id-BHChannels-FailedToBeModified-List | ProtocolIE-ID ::= 269 | +| id-BHChannels-FailedToBeSetupMod-Item | ProtocolIE-ID ::= 270 | +| id-BHChannels-FailedToBeSetupMod-List | ProtocolIE-ID ::= 271 | +| id-BHChannels-Modified-Item | ProtocolIE-ID ::= 272 | +| id-BHChannels-Modified-List | ProtocolIE-ID ::= 273 | +| id-BHChannels-SetupMod-Item | ProtocolIE-ID ::= 274 | +| id-BHChannels-SetupMod-List | ProtocolIE-ID ::= 275 | +| id-BHChannels-Required-ToBeReleased-Item | ProtocolIE-ID ::= 276 | +| id-BHChannels-Required-ToBeReleased-List | ProtocolIE-ID ::= 277 | +| id-BHChannels-FailedToBeSetup-Item | ProtocolIE-ID ::= 278 | +| id-BHChannels-FailedToBeSetup-List | ProtocolIE-ID ::= 279 | +| id-BHInfo | ProtocolIE-ID ::= 280 | +| id-BAPAddress | ProtocolIE-ID ::= 281 | +| id-ConfiguredBAPAddress | ProtocolIE-ID ::= 282 | +| id-BH-Routing-Information-Added-List | ProtocolIE-ID ::= 283 | +| id-BH-Routing-Information-Added-List-Item | ProtocolIE-ID ::= 284 | + +| | | +|----------------------------------------------|-----------------------| +| id-BH-Routing-Information-Removed-List | ProtocolIE-ID ::= 285 | +| id-BH-Routing-Information-Removed-List-Item | ProtocolIE-ID ::= 286 | +| id-UL-BH-Non-UP-Traffic-Mapping | ProtocolIE-ID ::= 287 | +| id-Activated-Cells-to-be-Updated-List | ProtocolIE-ID ::= 288 | +| id-Child-Nodes-List | ProtocolIE-ID ::= 289 | +| id-IAB-Info-IAB-DU | ProtocolIE-ID ::= 290 | +| id-IAB-Info-IAB-donor-CU | ProtocolIE-ID ::= 291 | +| id-IAB-TNL-Addresses-To-Remove-List | ProtocolIE-ID ::= 292 | +| id-IAB-TNL-Addresses-To-Remove-Item | ProtocolIE-ID ::= 293 | +| id-IAB-Allocated-TNL-Address-List | ProtocolIE-ID ::= 294 | +| id-IAB-Allocated-TNL-Address-Item | ProtocolIE-ID ::= 295 | +| id-IABIPv6RequestType | ProtocolIE-ID ::= 296 | +| id-IABv4AddressesRequested | ProtocolIE-ID ::= 297 | +| id-IAB-Barred | ProtocolIE-ID ::= 298 | +| id-TrafficMappingInformation | ProtocolIE-ID ::= 299 | +| id-UL-UP-TNL-Information-to-Update-List | ProtocolIE-ID ::= 300 | +| id-UL-UP-TNL-Information-to-Update-List-Item | ProtocolIE-ID ::= 301 | +| id-UL-UP-TNL-Address-to-Update-List | ProtocolIE-ID ::= 302 | +| id-UL-UP-TNL-Address-to-Update-List-Item | ProtocolIE-ID ::= 303 | +| id-DL-UP-TNL-Address-to-Update-List | ProtocolIE-ID ::= 304 | +| id-DL-UP-TNL-Address-to-Update-List-Item | ProtocolIE-ID ::= 305 | +| id-NRV2XServicesAuthorized | ProtocolIE-ID ::= 306 | +| id-LTEV2XServicesAuthorized | ProtocolIE-ID ::= 307 | +| id-NRUESidelinkAggregateMaximumBitrate | ProtocolIE-ID ::= 308 | + +| | | +|-----------------------------------------|-----------------------| +| id-LTEUESidelinkAggregateMaximumBitrate | ProtocolIE-ID ::= 309 | +| id-SIB12-message | ProtocolIE-ID ::= 310 | +| id-SIB13-message | ProtocolIE-ID ::= 311 | +| id-SIB14-message | ProtocolIE-ID ::= 312 | +| id-SLDRBs-FailedToBeModified-Item | ProtocolIE-ID ::= 313 | +| id-SLDRBs-FailedToBeModified-List | ProtocolIE-ID ::= 314 | +| id-SLDRBs-FailedToBeSetup-Item | ProtocolIE-ID ::= 315 | +| id-SLDRBs-FailedToBeSetup-List | ProtocolIE-ID ::= 316 | +| id-SLDRBs-Modified-Item | ProtocolIE-ID ::= 317 | +| id-SLDRBs-Modified-List | ProtocolIE-ID ::= 318 | +| id-SLDRBs-Required-ToBeModified-Item | ProtocolIE-ID ::= 319 | +| id-SLDRBs-Required-ToBeModified-List | ProtocolIE-ID ::= 320 | +| id-SLDRBs-Required-ToBeReleased-Item | ProtocolIE-ID ::= 321 | +| id-SLDRBs-Required-ToBeReleased-List | ProtocolIE-ID ::= 322 | +| id-SLDRBs-Setup-Item | ProtocolIE-ID ::= 323 | +| id-SLDRBs-Setup-List | ProtocolIE-ID ::= 324 | +| id-SLDRBs-ToBeModified-Item | ProtocolIE-ID ::= 325 | +| id-SLDRBs-ToBeModified-List | ProtocolIE-ID ::= 326 | +| id-SLDRBs-ToBeReleased-Item | ProtocolIE-ID ::= 327 | +| id-SLDRBs-ToBeReleased-List | ProtocolIE-ID ::= 328 | +| id-SLDRBs-ToBeSetup-Item | ProtocolIE-ID ::= 329 | +| id-SLDRBs-ToBeSetup-List | ProtocolIE-ID ::= 330 | +| id-SLDRBs-ToBeSetupMod-Item | ProtocolIE-ID ::= 331 | +| id-SLDRBs-ToBeSetupMod-List | ProtocolIE-ID ::= 332 | + +| | | +|-----------------------------------|-----------------------| +| id-SLDRBs-SetupMod-List | ProtocolIE-ID ::= 333 | +| id-SLDRBs-FailedToBeSetupMod-List | ProtocolIE-ID ::= 334 | +| id-SLDRBs-SetupMod-Item | ProtocolIE-ID ::= 335 | +| id-SLDRBs-FailedToBeSetupMod-Item | ProtocolIE-ID ::= 336 | +| id-SLDRBs-ModifiedConf-List | ProtocolIE-ID ::= 337 | +| id-SLDRBs-ModifiedConf-Item | ProtocolIE-ID ::= 338 | +| id-UEAssistanceInformationEUTRA | ProtocolIE-ID ::= 339 | +| id-PC5LinkAMBR | ProtocolIE-ID ::= 340 | +| id-SL-PHY-MAC-RLC-Config | ProtocolIE-ID ::= 341 | +| id-SL-ConfigDedicatedEUTRA-Info | ProtocolIE-ID ::= 342 | +| id-AlternativeQoSParaSetList | ProtocolIE-ID ::= 343 | +| id-CurrentQoSParaSetIndex | ProtocolIE-ID ::= 344 | +| id-gNBCUMeasurementID | ProtocolIE-ID ::= 345 | +| id-gNBDUMeasurementID | ProtocolIE-ID ::= 346 | +| id-RegistrationRequest | ProtocolIE-ID ::= 347 | +| id-ReportCharacteristics | ProtocolIE-ID ::= 348 | +| id-CellToReportList | ProtocolIE-ID ::= 349 | +| id-CellMeasurementResultList | ProtocolIE-ID ::= 350 | +| id-HardwareLoadIndicator | ProtocolIE-ID ::= 351 | +| id-ReportingPeriodicity | ProtocolIE-ID ::= 352 | +| id-TNLCapacityIndicator | ProtocolIE-ID ::= 353 | +| id-CarrierList | ProtocolIE-ID ::= 354 | +| id-ULCarrierList | ProtocolIE-ID ::= 355 | +| id-FrequencyShift7p5khz | ProtocolIE-ID ::= 356 | + +| | | +|------------------------------------------|-----------------------| +| id-SSB-PositionsInBurst | ProtocolIE-ID ::= 357 | +| id-NRPRACHConfig | ProtocolIE-ID ::= 358 | +| id-RAReportList | ProtocolIE-ID ::= 359 | +| id-RLFReportInformationList | ProtocolIE-ID ::= 360 | +| id-TDD-UL-DLConfigCommonNR | ProtocolIE-ID ::= 361 | +| id-CNPacketDelayBudgetDownlink | ProtocolIE-ID ::= 362 | +| id-ExtendedPacketDelayBudget | ProtocolIE-ID ::= 363 | +| id-TSCTrafficCharacteristics | ProtocolIE-ID ::= 364 | +| id-ReportingRequestType | ProtocolIE-ID ::= 365 | +| id-TimeReferenceInformation | ProtocolIE-ID ::= 366 | +| id-CNPacketDelayBudgetUplink | ProtocolIE-ID ::= 369 | +| id-AdditionalPDCPDuplicationTNL-List | ProtocolIE-ID ::= 370 | +| id-RLCDuplicationInformation | ProtocolIE-ID ::= 371 | +| id-AdditionalDuplicationIndication | ProtocolIE-ID ::= 372 | +| id-ConditionalInterDUMobilityInformation | ProtocolIE-ID ::= 373 | +| id-ConditionalIntraDUMobilityInformation | ProtocolIE-ID ::= 374 | +| id-targetCellsToCancel | ProtocolIE-ID ::= 375 | +| id-requestedTargetCellGlobalID | ProtocolIE-ID ::= 376 | +| id-ManagementBasedMDTPLMNList | ProtocolIE-ID ::= 377 | +| id-TraceCollectionEntityIPAddress | ProtocolIE-ID ::= 378 | +| id-PrivacyIndicator | ProtocolIE-ID ::= 379 | +| id-TraceCollectionEntityURI | ProtocolIE-ID ::= 380 | +| id-mdtConfiguration | ProtocolIE-ID ::= 381 | +| id-ServingNID | ProtocolIE-ID ::= 382 | + +| | | +|--------------------------------------------|-----------------------| +| id-NPNBroadcastInformation | ProtocolIE-ID ::= 383 | +| id-NPNSupportInfo | ProtocolIE-ID ::= 384 | +| id-NID | ProtocolIE-ID ::= 385 | +| id-AvailableSNPN-ID-List | ProtocolIE-ID ::= 386 | +| id-SIB10-message | ProtocolIE-ID ::= 387 | +| id-DLCarrierList | ProtocolIE-ID ::= 389 | +| id-ExtendedTAISliceSupportList | ProtocolIE-ID ::= 390 | +| id-RequestedSRSTransmissionCharacteristics | ProtocolIE-ID ::= 391 | +| id-PosAssistance-Information | ProtocolIE-ID ::= 392 | +| id-PosBroadcast | ProtocolIE-ID ::= 393 | +| id-RoutingID | ProtocolIE-ID ::= 394 | +| id-PosAssistanceInformationFailureList | ProtocolIE-ID ::= 395 | +| id-PosMeasurementQuantities | ProtocolIE-ID ::= 396 | +| id-PosMeasurementResultList | ProtocolIE-ID ::= 397 | +| id-TRPInformationTypeListTRPReq | ProtocolIE-ID ::= 398 | +| id-TRPInformationTypeItem | ProtocolIE-ID ::= 399 | +| id-TRPInformationListTRPResp | ProtocolIE-ID ::= 400 | +| id-TRPInformationItem | ProtocolIE-ID ::= 401 | +| id-LMF-MeasurementID | ProtocolIE-ID ::= 402 | +| id-SRSType | ProtocolIE-ID ::= 403 | +| id-ActivationTime | ProtocolIE-ID ::= 404 | +| id-AbortTransmission | ProtocolIE-ID ::= 405 | +| id-PositioningBroadcastCells | ProtocolIE-ID ::= 406 | +| id-SRSConfiguration | ProtocolIE-ID ::= 407 | + +| | | +|-------------------------------------|-----------------------| +| id-PosReportCharacteristics | ProtocolIE-ID ::= 408 | +| id-PosMeasurementPeriodicity | ProtocolIE-ID ::= 409 | +| id-TRPLList | ProtocolIE-ID ::= 410 | +| id-RAN-MeasurementID | ProtocolIE-ID ::= 411 | +| id-LMF-UE-MeasurementID | ProtocolIE-ID ::= 412 | +| id-RAN-UE-MeasurementID | ProtocolIE-ID ::= 413 | +| id-E-CID-MeasurementQuantities | ProtocolIE-ID ::= 414 | +| id-E-CID-MeasurementQuantities-Item | ProtocolIE-ID ::= 415 | +| id-E-CID-MeasurementPeriodicity | ProtocolIE-ID ::= 416 | +| id-E-CID-MeasurementResult | ProtocolIE-ID ::= 417 | +| id-Cell-Portion-ID | ProtocolIE-ID ::= 418 | +| id-SFNInitialisationTime | ProtocolIE-ID ::= 419 | +| id-SystemFrameNumber | ProtocolIE-ID ::= 420 | +| id-SlotNumber | ProtocolIE-ID ::= 421 | +| id-TRP-MeasurementRequestList | ProtocolIE-ID ::= 422 | +| id-MeasurementBeamInfoRequest | ProtocolIE-ID ::= 423 | +| id-E-CID-ReportCharacteristics | ProtocolIE-ID ::= 424 | +| id-ConfiguredTACIndication | ProtocolIE-ID ::= 425 | +| id-Extended-GNB-CU-Name | ProtocolIE-ID ::= 426 | +| id-Extended-GNB-DU-Name | ProtocolIE-ID ::= 427 | +| id-F1CTransferPath | ProtocolIE-ID ::= 428 | +| id-SFN-Offset | ProtocolIE-ID ::= 429 | +| id-TransmissionStopIndicator | ProtocolIE-ID ::= 430 | +| id-SrsFrequency | ProtocolIE-ID ::= 431 | + +| | | +|--------------------------------------------------|-----------------------| +| id-SCGIndicator | ProtocolIE-ID ::= 432 | +| id-EstimatedArrivalProbability | ProtocolIE-ID ::= 433 | +| id-TRPType | ProtocolIE-ID ::= 434 | +| id-SRSSpatialRelationPerSRSResource | ProtocolIE-ID ::= 435 | +| id-PDCPTerminatingNodeDLTNLAddrInfo | ProtocolIE-ID ::= 436 | +| id-ENBDLNLAddress | ProtocolIE-ID ::= 437 | +| id-PosMeasurementPeriodicityExtended | ProtocolIE-ID ::= 438 | +| id-PRS-Resource-ID | ProtocolIE-ID ::= 439 | +| id-LocationMeasurementInformation | ProtocolIE-ID ::= 440 | +| id-SliceRadioResourceStatus | ProtocolIE-ID ::= 441 | +| id-CompositeAvailableCapacity-SUL | ProtocolIE-ID ::= 442 | +| id-SuccessfulHOReportInformationList | ProtocolIE-ID ::= 443 | +| id-NR-U-Channel-List | ProtocolIE-ID ::= 444 | +| id-NR-U | ProtocolIE-ID ::= 445 | +| id-Coverage-Modification-Notification | ProtocolIE-ID ::= 446 | +| id-CCO-Assistance-Information | ProtocolIE-ID ::= 447 | +| id-Neighbor-node-CCO-Assistance-Information-List | ProtocolIE-ID ::= 448 | +| id-CellsForSON-List | ProtocolIE-ID ::= 449 | +| id-MIMO PRB Usage Information | ProtocolIE-ID ::= 450 | +| id-gNB-CU-MBS-FLAP-ID | ProtocolIE-ID ::= 451 | +| id-gNB-DU-MBS-FLAP-ID | ProtocolIE-ID ::= 452 | +| id-MBS-Area-Session-ID | ProtocolIE-ID ::= 453 | +| id-MBS-CUtoDURRCInformation | ProtocolIE-ID ::= 454 | +| id-MBS-Session-ID | ProtocolIE-ID ::= 455 | + +| | | +|------------------------------------------|-----------------------| +| id-SNSSAI | ProtocolIE-ID ::= 456 | +| id-MBS-Broadcast-NeighbourCellList | ProtocolIE-ID ::= 457 | +| id-BroadcastMRBs-FailedToBeModified-List | ProtocolIE-ID ::= 458 | +| id-BroadcastMRBs-FailedToBeModified-Item | ProtocolIE-ID ::= 459 | +| id-BroadcastMRBs-FailedToBeSetup-List | ProtocolIE-ID ::= 460 | +| id-BroadcastMRBs-FailedToBeSetup-Item | ProtocolIE-ID ::= 461 | +| id-BroadcastMRBs-FailedToBeSetupMod-List | ProtocolIE-ID ::= 462 | +| id-BroadcastMRBs-FailedToBeSetupMod-Item | ProtocolIE-ID ::= 463 | +| id-BroadcastMRBs-Modified-List | ProtocolIE-ID ::= 464 | +| id-BroadcastMRBs-Modified-Item | ProtocolIE-ID ::= 465 | +| id-BroadcastMRBs-Setup-List | ProtocolIE-ID ::= 466 | +| id-BroadcastMRBs-Setup-Item | ProtocolIE-ID ::= 467 | +| id-BroadcastMRBs-SetupMod-List | ProtocolIE-ID ::= 468 | +| id-BroadcastMRBs-SetupMod-Item | ProtocolIE-ID ::= 469 | +| id-BroadcastMRBs-ToBeModified-List | ProtocolIE-ID ::= 470 | +| id-BroadcastMRBs-ToBeModified-Item | ProtocolIE-ID ::= 471 | +| id-BroadcastMRBs-ToBeReleased-List | ProtocolIE-ID ::= 472 | +| id-BroadcastMRBs-ToBeReleased-Item | ProtocolIE-ID ::= 473 | +| id-BroadcastMRBs-ToBeSetup-List | ProtocolIE-ID ::= 474 | +| id-BroadcastMRBs-ToBeSetup-Item | ProtocolIE-ID ::= 475 | +| id-BroadcastMRBs-ToBeSetupMod-List | ProtocolIE-ID ::= 476 | +| id-BroadcastMRBs-ToBeSetupMod-Item | ProtocolIE-ID ::= 477 | +| id-Supported-MBS-FSA-ID-List | ProtocolIE-ID ::= 478 | +| id-UEIdentity-List-For-Paging-List | ProtocolIE-ID ::= 479 | + +| | | +|------------------------------------------|-----------------------| +| id-UEIdentity-List-For-Paging-Item | ProtocolIE-ID ::= 480 | +| id-MBS-ServiceArea | ProtocolIE-ID ::= 481 | +| id-MulticastMRBs-FailedToBeModified-List | ProtocolIE-ID ::= 482 | +| id-MulticastMRBs-FailedToBeModified-Item | ProtocolIE-ID ::= 483 | +| id-MulticastMRBs-FailedToBeSetup-List | ProtocolIE-ID ::= 484 | +| id-MulticastMRBs-FailedToBeSetup-Item | ProtocolIE-ID ::= 485 | +| id-MulticastMRBs-FailedToBeSetupMod-List | ProtocolIE-ID ::= 486 | +| id-MulticastMRBs-FailedToBeSetupMod-Item | ProtocolIE-ID ::= 487 | +| id-MulticastMRBs-Modified-List | ProtocolIE-ID ::= 488 | +| id-MulticastMRBs-Modified-Item | ProtocolIE-ID ::= 489 | +| id-MulticastMRBs-Setup-List | ProtocolIE-ID ::= 490 | +| id-MulticastMRBs-Setup-Item | ProtocolIE-ID ::= 491 | +| id-MulticastMRBs-SetupMod-List | ProtocolIE-ID ::= 492 | +| id-MulticastMRBs-SetupMod-Item | ProtocolIE-ID ::= 493 | +| id-MulticastMRBs-ToBeModified-List | ProtocolIE-ID ::= 494 | +| id-MulticastMRBs-ToBeModified-Item | ProtocolIE-ID ::= 495 | +| id-MulticastMRBs-ToBeReleased-List | ProtocolIE-ID ::= 496 | +| id-MulticastMRBs-ToBeReleased-Item | ProtocolIE-ID ::= 497 | +| id-MulticastMRBs-ToBeSetup-List | ProtocolIE-ID ::= 498 | +| id-MulticastMRBs-ToBeSetup-Item | ProtocolIE-ID ::= 499 | +| id-MulticastMRBs-ToBeSetupMod-List | ProtocolIE-ID ::= 500 | +| id-MulticastMRBs-ToBeSetupMod-Item | ProtocolIE-ID ::= 501 | +| id-MBSMulticastFlUContextDescriptor | ProtocolIE-ID ::= 502 | +| id-MulticastFlUContext-ToBeSetup-List | ProtocolIE-ID ::= 503 | + +| | | +|----------------------------------------------------|-----------------------| +| id-MulticastFlUContext-ToBeSetup-Item | ProtocolIE-ID ::= 504 | +| id-MulticastFlUContext-Setup-List | ProtocolIE-ID ::= 505 | +| id-MulticastFlUContext-Setup-Item | ProtocolIE-ID ::= 506 | +| id-MulticastFlUContext-FailedToBeSetup-List | ProtocolIE-ID ::= 507 | +| id-MulticastFlUContext-FailedToBeSetup-Item | ProtocolIE-ID ::= 508 | +| id-IABCongestionIndication | ProtocolIE-ID ::= 509 | +| id-IABConditionalRRMessageDeliveryIndication | ProtocolIE-ID ::= 510 | +| id-FlCTransferPathNRDC | ProtocolIE-ID ::= 511 | +| id-BufferSizeThresh | ProtocolIE-ID ::= 512 | +| id-IAB-TNL-Addresses-Exception | ProtocolIE-ID ::= 513 | +| id-BAP-Header-Rewriting-Added-List | ProtocolIE-ID ::= 514 | +| id-BAP-Header-Rewriting-Added-List-Item | ProtocolIE-ID ::= 515 | +| id-Re-routingEnableIndicator | ProtocolIE-ID ::= 516 | +| id-NonFlterminatingTopologyIndicator | ProtocolIE-ID ::= 517 | +| id-EgressNonFlterminatingTopologyIndicator | ProtocolIE-ID ::= 518 | +| id-IngressNonFlterminatingTopologyIndicator | ProtocolIE-ID ::= 519 | +| id-rBSetConfiguration | ProtocolIE-ID ::= 520 | +| id-frequency-Domain-HSNA-Configuration-List | ProtocolIE-ID ::= 521 | +| id-child-IAB-Nodes-NA-Resource-List | ProtocolIE-ID ::= 522 | +| id-Parent-IAB-Nodes-NA-Resource-Configuration-List | ProtocolIE-ID ::= 523 | +| id-uL-FreqInfo | ProtocolIE-ID ::= 524 | +| id-uL-Transmission-Bandwidth | ProtocolIE-ID ::= 525 | +| id-dL-FreqInfo | ProtocolIE-ID ::= 526 | +| id-dL-Transmission-Bandwidth | ProtocolIE-ID ::= 527 | + +| | | +|------------------------------------|-----------------------| +| id-uL-NR-Carrier-List | ProtocolIE-ID ::= 528 | +| id-dL-NR-Carrier-List | ProtocolIE-ID ::= 529 | +| id-nRFreqInfo | ProtocolIE-ID ::= 530 | +| id-transmission-Bandwidth | ProtocolIE-ID ::= 531 | +| id-nR-Carrier-List | ProtocolIE-ID ::= 532 | +| id-Neighbour-Node-Cells-List | ProtocolIE-ID ::= 533 | +| id-Serving-Cells-List | ProtocolIE-ID ::= 534 | +| id-permutation | ProtocolIE-ID ::= 535 | +| id-MDTPollutedMeasurementIndicator | ProtocolIE-ID ::= 536 | +| id-M5ReportAmount | ProtocolIE-ID ::= 537 | +| id-M6ReportAmount | ProtocolIE-ID ::= 538 | +| id-M7ReportAmount | ProtocolIE-ID ::= 539 | +| id-SurvivalTime | ProtocolIE-ID ::= 540 | +| id-PDCMeasurementPeriodicity | ProtocolIE-ID ::= 541 | +| id-PDCMeasurementQuantities | ProtocolIE-ID ::= 542 | +| id-PDCMeasurementQuantities-Item | ProtocolIE-ID ::= 543 | +| id-PDCMeasurementResult | ProtocolIE-ID ::= 544 | +| id-PDCReportType | ProtocolIE-ID ::= 545 | +| id-RAN-UE-PDC-MeasID | ProtocolIE-ID ::= 546 | +| id-SCGActivationRequest | ProtocolIE-ID ::= 547 | +| id-SCGActivationStatus | ProtocolIE-ID ::= 548 | +| id-PRSTRPList | ProtocolIE-ID ::= 549 | +| id-PRSTransmissionTRPList | ProtocolIE-ID ::= 550 | +| id-OnDemandPRS | ProtocolIE-ID ::= 551 | + +| | | +|-----------------------------------------------|-----------------------| +| id-AoA-SearchWindow | ProtocolIE-ID ::= 552 | +| id-TRP-MeasurementUpdateList | ProtocolIE-ID ::= 553 | +| id-ZoAInformation | ProtocolIE-ID ::= 554 | +| id-ResponseTime | ProtocolIE-ID ::= 555 | +| id-ARPLocationInfo | ProtocolIE-ID ::= 556 | +| id-ARP-ID | ProtocolIE-ID ::= 557 | +| id-MultipleULAoA | ProtocolIE-ID ::= 558 | +| id-UL-SRS-RSRP | ProtocolIE-ID ::= 559 | +| id-SRSResourcetype | ProtocolIE-ID ::= 560 | +| id-ExtendedAdditionalPathList | ProtocolIE-ID ::= 561 | +| id-LoS-NLoSInformation | ProtocolIE-ID ::= 562 | +| id-NumberOfTRPRxTEG | ProtocolIE-ID ::= 564 | +| id-NumberOfTRPRxTxTEG | ProtocolIE-ID ::= 565 | +| id-TRPTxTEGAssociation | ProtocolIE-ID ::= 566 | +| id-TRPTEGInformation | ProtocolIE-ID ::= 567 | +| id-TRPRx-TEGInformation | ProtocolIE-ID ::= 568 | +| id-TRP-PRS-Info-List | ProtocolIE-ID ::= 569 | +| id-PRS-Measurement-Info-List | ProtocolIE-ID ::= 570 | +| id-PRSConfigRequestType | ProtocolIE-ID ::= 571 | +| id-MeasurementTimeOccasion | ProtocolIE-ID ::= 573 | +| id-MeasurementCharacteristicsRequestIndicator | ProtocolIE-ID ::= 574 | +| id-UEReportingInformation | ProtocolIE-ID ::= 575 | +| id-PosConextRevIndication | ProtocolIE-ID ::= 576 | +| id-TRPBeamAntennaInformation | ProtocolIE-ID ::= 577 | + +| | | +|--------------------------------------------|-----------------------| +| id-NRRedCapUEIndication | ProtocolIE-ID ::= 578 | +| id-Redcap-Bcast-Information | ProtocolIE-ID ::= 579 | +| id-RANUEPagingDRX | ProtocolIE-ID ::= 580 | +| id-CNUEPagingDRX | ProtocolIE-ID ::= 581 | +| id-NRPagingeDRXInformation | ProtocolIE-ID ::= 582 | +| id-NRPagingeDRXInformationforRRRCINACTIVE | ProtocolIE-ID ::= 583 | +| id-NR-TADV | ProtocolIE-ID ::= 584 | +| id-QoEInformation | ProtocolIE-ID ::= 585 | +| id-CG-SDTQueryIndication | ProtocolIE-ID ::= 586 | +| id-SDT-MAC-PHY-CG-Config | ProtocolIE-ID ::= 587 | +| id-CG-SDTKeptIndicator | ProtocolIE-ID ::= 588 | +| id-CG-SDTIndicatorSetup | ProtocolIE-ID ::= 589 | +| id-CG-SDTIndicatorMod | ProtocolIE-ID ::= 590 | +| id-CG-SDTSessionInfoOld | ProtocolIE-ID ::= 591 | +| id-SDTInformation | ProtocolIE-ID ::= 592 | +| id-SDTRLCBearerConfiguration | ProtocolIE-ID ::= 593 | +| id-FiveG-ProSeAuthorized | ProtocolIE-ID ::= 594 | +| id-FiveG-ProSeUEPC5AggregateMaximumBitrate | ProtocolIE-ID ::= 595 | +| id-FiveG-ProSePC5LinkAMBR | ProtocolIE-ID ::= 596 | +| id-SRBMappingInfo | ProtocolIE-ID ::= 597 | +| id-DRBMappingInfo | ProtocolIE-ID ::= 598 | +| id-UuRLCChannelToBeSetupList | ProtocolIE-ID ::= 599 | +| id-UuRLCChannelToBeModifiedList | ProtocolIE-ID ::= 600 | +| id-UuRLCChannelToBeReleasedList | ProtocolIE-ID ::= 601 | + +| | | +|------------------------------------------|-----------------------| +| id-UuRLCChannelSetupList | ProtocolIE-ID ::= 602 | +| id-UuRLCChannelFailedToBeSetupList | ProtocolIE-ID ::= 603 | +| id-UuRLCChannelModifiedList | ProtocolIE-ID ::= 604 | +| id-UuRLCChannelFailedToBeModifiedList | ProtocolIE-ID ::= 605 | +| id-UuRLCChannelRequiredToBeModifiedList | ProtocolIE-ID ::= 606 | +| id-UuRLCChannelRequiredToBeReleasedList | ProtocolIE-ID ::= 607 | +| id-PC5RLCChannelToBeSetupList | ProtocolIE-ID ::= 608 | +| id-PC5RLCChannelToBeModifiedList | ProtocolIE-ID ::= 609 | +| id-PC5RLCChannelToBeReleasedList | ProtocolIE-ID ::= 610 | +| id-PC5RLCChannelSetupList | ProtocolIE-ID ::= 611 | +| id-PC5RLCChannelFailedToBeSetupList | ProtocolIE-ID ::= 612 | +| id-PC5RLCChannelFailedToBeModifiedList | ProtocolIE-ID ::= 613 | +| id-PC5RLCChannelRequiredToBeModifiedList | ProtocolIE-ID ::= 614 | +| id-PC5RLCChannelRequiredToBeReleasedList | ProtocolIE-ID ::= 615 | +| id-PC5RLCChannelModifiedList | ProtocolIE-ID ::= 616 | +| id-SidelinkRelayConfiguration | ProtocolIE-ID ::= 617 | +| id-UpdatedRemoteUELocalID | ProtocolIE-ID ::= 618 | +| id-PathSwitchConfiguration | ProtocolIE-ID ::= 619 | +| id-PagingCause | ProtocolIE-ID ::= 620 | +| id-MUSIM-GapConfig | ProtocolIE-ID ::= 621 | +| id-PEIPSAssistanceInfo | ProtocolIE-ID ::= 622 | +| id-UEPagingCapability | ProtocolIE-ID ::= 623 | +| id-LastUsedCellIndication | ProtocolIE-ID ::= 624 | +| id-SIB17-message | ProtocolIE-ID ::= 625 | + +| | | +|-------------------------------------------|-----------------------| +| id-GNBDUUESliceMaximumBitRateList | ProtocolIE-ID ::= 626 | +| id-SIB20-message | ProtocolIE-ID ::= 627 | +| id-UE-MulticastMRBs-ToBeReleased-List | ProtocolIE-ID ::= 628 | +| id-UE-MulticastMRBs-ToBeReleased-Item | ProtocolIE-ID ::= 629 | +| id-UE-MulticastMRBs-ToBeSetup-List | ProtocolIE-ID ::= 630 | +| id-UE-MulticastMRBs-ToBeSetup-Item | ProtocolIE-ID ::= 631 | +| id-MulticastMBSSessionSetupList | ProtocolIE-ID ::= 632 | +| id-MulticastMBSSessionRemoveList | ProtocolIE-ID ::= 633 | +| id-PosMeasurementAmount | ProtocolIE-ID ::= 634 | +| id-SDT-Termination-Request | ProtocolIE-ID ::= 635 | +| id-pathPower | ProtocolIE-ID ::= 636 | +| id-DU-RX-MT-RX-Extend | ProtocolIE-ID ::= 637 | +| id-DU-TX-MT-TX-Extend | ProtocolIE-ID ::= 638 | +| id-DU-RX-MT-TX-Extend | ProtocolIE-ID ::= 639 | +| id-DU-TX-MT-RX-Extend | ProtocolIE-ID ::= 640 | +| id-BAP-Header-Rewriting-Removed-List | ProtocolIE-ID ::= 641 | +| id-BAP-Header-Rewriting-Removed-List-Item | ProtocolIE-ID ::= 642 | +| id-SLDRXCycleList | ProtocolIE-ID ::= 643 | +| id-TAINSAGSupportList | ProtocolIE-ID ::= 644 | +| id-SL-RLC-ChannelToAddModList | ProtocolIE-ID ::= 645 | +| id-BroadcastAreaScope | ProtocolIE-ID ::= 646 | +| id-ManagementBasedMDTPLMNModificationList | ProtocolIE-ID ::= 647 | +| id-SIB15-message | ProtocolIE-ID ::= 648 | +| id-ActivationRequestType | ProtocolIE-ID ::= 649 | + +| | | +|------------------------------------------------|-----------------------| +| id-PosMeasGapPreConfigList | ProtocolIE-ID ::= 650 | +| id-InterFrequencyConfig-NoGap | ProtocolIE-ID ::= 651 | +| id-MBSInterestIndication | ProtocolIE-ID ::= 652 | +| id-UE-MulticastMRBs-ConfirmedToBeModified-List | ProtocolIE-ID ::= 653 | +| id-UE-MulticastMRBs-ConfirmedToBeModified-Item | ProtocolIE-ID ::= 654 | +| id-UE-MulticastMRBs-RequiredToBeModified-List | ProtocolIE-ID ::= 655 | +| id-UE-MulticastMRBs-RequiredToBeModified-Item | ProtocolIE-ID ::= 656 | +| id-UE-MulticastMRBs-RequiredToBeReleased-List | ProtocolIE-ID ::= 657 | +| id-UE-MulticastMRBs-RequiredToBeReleased-Item | ProtocolIE-ID ::= 658 | +| id-L571Info | ProtocolIE-ID ::= 659 | +| id-L1151Info | ProtocolIE-ID ::= 660 | +| id-SCS-480 | ProtocolIE-ID ::= 661 | +| id-SCS-960 | ProtocolIE-ID ::= 662 | +| id-SRSPortIndex | ProtocolIE-ID ::= 663 | +| id-PEISubgroupingSupportIndication | ProtocolIE-ID ::= 664 | +| id-NeedForGapsInfoNR | ProtocolIE-ID ::= 665 | +| id-NeedForGapNCSGInfoNR | ProtocolIE-ID ::= 666 | +| id-NeedForGapNCSGInfoEUTRA | ProtocolIE-ID ::= 667 | +| id-procedure-code-668-not-to-be-used | ProtocolIE-ID ::= 668 | +| id-procedure-code-669-not-to-be-used | ProtocolIE-ID ::= 669 | +| id-procedure-code-670-not-to-be-used | ProtocolIE-ID ::= 670 | +| id-Source-MRB-ID | ProtocolIE-ID ::= 671 | +| id-PosMeasurementPeriodicityNR-AoA | ProtocolIE-ID ::= 672 | +| id-RedCapIndication | ProtocolIE-ID ::= 673 | + +| | | +|---------------------------------------------|-----------------------| +| id-SRSPosRRInactiveConfig | ProtocolIE-ID ::= 674 | +| id-SDTBearerConfigurationQueryIndication | ProtocolIE-ID ::= 675 | +| id-SDTBearerConfigurationInfo | ProtocolIE-ID ::= 676 | +| id-UL-GapFR2-Config | ProtocolIE-ID ::= 677 | +| id-ConfigRestrictInfoDAPS | ProtocolIE-ID ::= 678 | +| id-UE-MulticastMRBs-Setup-List | ProtocolIE-ID ::= 679 | +| id-UE-MulticastMRBs-Setup-Item | ProtocolIE-ID ::= 680 | +| id-MulticastFlUContextReferenceCU | ProtocolIE-ID ::= 681 | +| id-PosSItypeList | ProtocolIE-ID ::= 682 | +| id-DAPS-HO-Status | ProtocolIE-ID ::= 683 | +| id-UplinkTxDirectCurrentTwoCarrierListInfo | ProtocolIE-ID ::= 684 | +| id-UE-MulticastMRBs-ToBeSetup-atModify-List | ProtocolIE-ID ::= 685 | +| id-UE-MulticastMRBs-ToBeSetup-atModify-Item | ProtocolIE-ID ::= 686 | +| id-MC-PagingCell-List | ProtocolIE-ID ::= 687 | +| id-MC-PagingCell-Item | ProtocolIE-ID ::= 688 | +| id-SRSPosRRInactiveQueryIndication | ProtocolIE-ID ::= 689 | +| id-ULTxDirectCurrentMoreCarrierInformation | ProtocolIE-ID ::= 690 | +| id-CPACMCGInformation | ProtocolIE-ID ::= 691 | +| id-TwoPHRModeMCG | ProtocolIE-ID ::= 692 | +| id-TwoPHRModeSCG | ProtocolIE-ID ::= 693 | +| id-ExtendedUEIdentityIndexValue | ProtocolIE-ID ::= 694 | +| id-ServingCellMO-List | ProtocolIE-ID ::= 695 | +| id-ServingCellMO-List-Item | ProtocolIE-ID ::= 696 | +| id-ServingCellMO-encoded-in-CGC-List | ProtocolIE-ID ::= 697 | + +| | | +|------------------------------------------|-----------------------| +| id-HashedUEIdentityIndexValue | ProtocolIE-ID ::= 698 | +| id-UE-MulticastMRBs-Setupnew-List | ProtocolIE-ID ::= 699 | +| id-UE-MulticastMRBs-Setupnew-Item | ProtocolIE-ID ::= 700 | +| id-ncd-SSB-RedCapInitialBWP-SDT | ProtocolIE-ID ::= 701 | +| id-nrofSymbolsExtended | ProtocolIE-ID ::= 702 | +| id-repetitionFactorExtended | ProtocolIE-ID ::= 703 | +| id-startRBHopping | ProtocolIE-ID ::= 704 | +| id-startRBIndex | ProtocolIE-ID ::= 705 | +| id-transmissionComb8 | ProtocolIE-ID ::= 706 | +| id-ServCellInfoList | ProtocolIE-ID ::= 707 | +| id-DedicatedSIDeliveryIndication | ProtocolIE-ID ::= 708 | +| id-Configured-BWP-List | ProtocolIE-ID ::= 709 | +| id-Preconfigured-measurement-GAP-Request | ProtocolIE-ID ::= 710 | +| id-BWP-Id | ProtocolIE-ID ::= 711 | +| id-NetworkControlledRepeaterAuthorized | ProtocolIE-ID ::= 712 | +| id-MT-SDT-Information | ProtocolIE-ID ::= 713 | +| id-ExtendedResourceSymbolOffset | ProtocolIE-ID ::= 714 | +| id-NeedForInterruptionInfoNR | ProtocolIE-ID ::= 715 | +| id-SDT-Volume-Threshold | ProtocolIE-ID ::= 716 | +| id-SupportedUETypeList | ProtocolIE-ID ::= 717 | +| id-MusimCapabilityRestrictionIndication | ProtocolIE-ID ::= 718 | +| id-duplicationIndication | ProtocolIE-ID ::= 719 | +| id-LTMInformation-Setup | ProtocolIE-ID ::= 720 | +| id-LTMConfigurationIDMappingList | ProtocolIE-ID ::= 721 | + +| | | +|------------------------------------------------|-----------------------| +| id-LTMInformation-Modify | ProtocolIE-ID ::= 722 | +| id-LTMCells-ToBeReleased-List | ProtocolIE-ID ::= 723 | +| id-LTMCells-ToBeReleased-Item | ProtocolIE-ID ::= 724 | +| id-LTMConfiguration | ProtocolIE-ID ::= 725 | +| id-EarlySyncInformation-Request | ProtocolIE-ID ::= 726 | +| id-EarlySyncInformation | ProtocolIE-ID ::= 727 | +| id-EarlySyncInformation-List | ProtocolIE-ID ::= 728 | +| id-LTMCellSwitchInformation | ProtocolIE-ID ::= 729 | +| id-TAInformation-List | ProtocolIE-ID ::= 730 | +| id-Source-gNB-DU-ID | ProtocolIE-ID ::= 731 | +| id-dRB-List | ProtocolIE-ID ::= 732 | +| id-DeactivationIndication | ProtocolIE-ID ::= 733 | +| id-RAReportIndicationList | ProtocolIE-ID ::= 734 | +| id-ChannelOccupancyTimePercentageUL | ProtocolIE-ID ::= 735 | +| id-SuccessfulPSCellChangeReportInformationList | ProtocolIE-ID ::= 736 | +| id-RadioResourceStatusNR-U | ProtocolIE-ID ::= 737 | +| id-FiveG-ProSeLayer2Multipath | ProtocolIE-ID ::= 738 | +| id-FiveG-ProSeLayer2UEtoUERelay | ProtocolIE-ID ::= 739 | +| id-FiveG-ProSeLayer2UEtoUERemote | ProtocolIE-ID ::= 740 | +| id-PathAdditionInformation | ProtocolIE-ID ::= 741 | +| id-Recommended-SSBs-List | ProtocolIE-ID ::= 742 | +| id-Recommended-SSBs-for-Paging-List | ProtocolIE-ID ::= 743 | +| id-SSBs-withinTheCell-tobe-Activated-List | ProtocolIE-ID ::= 744 | +| id-Cells-With-SSBs-Activated-List | ProtocolIE-ID ::= 745 | + +| | | +|----------------------------------------------|-----------------------| +| id-Cells-Allowed-to-be-Deactivated-List | ProtocolIE-ID ::= 746 | +| id-Cells-Allowed-to-be-Deactivated-List-Item | ProtocolIE-ID ::= 747 | +| id-Coverage-Modification-Cause | ProtocolIE-ID ::= 748 | +| id-RANTSSRequestType | ProtocolIE-ID ::= 749 | +| id-RANTimingSynchronisationStatusInfo | ProtocolIE-ID ::= 750 | +| id-TSCTrafficCharacteristicsFeedback | ProtocolIE-ID ::= 751 | +| id-RANfeedbacktype | ProtocolIE-ID ::= 752 | +| id-Mobile-TRP-LocationInformation | ProtocolIE-ID ::= 753 | +| id-Mobile-IAB-MT-UE-ID | ProtocolIE-ID ::= 754 | +| id-Target-gNB-ID | ProtocolIE-ID ::= 755 | +| id-Target-gNB-IP-address | ProtocolIE-ID ::= 756 | +| id-Target-SeGW-IP-address | ProtocolIE-ID ::= 757 | +| id-Activated-Cells-Mapping-List | ProtocolIE-ID ::= 758 | +| id-Activated-Cells-Mapping-List-Item | ProtocolIE-ID ::= 759 | +| id-F1SetupOutcome | ProtocolIE-ID ::= 760 | +| id-RRC-Terminating-IAB-Donor-Related-Info | ProtocolIE-ID ::= 761 | +| id-RRC-Terminating-IAB-Donor-gNB-ID | ProtocolIE-ID ::= 762 | +| id-NCGI-to-be-Updated-List | ProtocolIE-ID ::= 763 | +| id-NCGI-to-be-Updated-List-Item | ProtocolIE-ID ::= 764 | +| id-Mobile-IAB-MTUserLocationInformation | ProtocolIE-ID ::= 765 | +| id-MobileAccessPointLocation | ProtocolIE-ID ::= 766 | +| id-AssociatedSessionID | ProtocolIE-ID ::= 767 | +| id-IndicationMCInactiveReception | ProtocolIE-ID ::= 768 | +| id-MulticastCU2DURRCCInfo | ProtocolIE-ID ::= 769 | + +``` + +id-MBSMulticastSessionReceptionState ProtocolIE-ID ::= 770 +id-F1UTunnelNotEstablished ProtocolIE-ID ::= 771 +id-MulticastDU2CURRCInfo ProtocolIE-ID ::= 772 +id-SIB1-message ProtocolIE-ID ::= 773 +id-MulticastCU2DUCommonRRCInfo ProtocolIE-ID ::= 774 +id-PDUSetQoSParameters ProtocolIE-ID ::= 775 +id-N6JitterInformation ProtocolIE-ID ::= 776 +id-ECNMarkingorCongestionInformationReportingRequest ProtocolIE-ID ::= 777 +id-ECNMarkingorCongestionInformationReportingStatus ProtocolIE-ID ::= 778 +id-NRA2XServicesAuthorized ProtocolIE-ID ::= 779 +id-LTEA2XServicesAuthorized ProtocolIE-ID ::= 780 +id-NRUESidelinkAggregateMaximumBitrateForA2X ProtocolIE-ID ::= 781 +id-LTEUESidelinkAggregateMaximumBitrateForA2X ProtocolIE-ID ::= 782 +id-NRRedCapUEIndication ProtocolIE-ID ::= 783 +id-ERedcap-Bcast-Information ProtocolIE-ID ::= 784 +id-NRPaginglongEDRXInformationforRRCINACTIVE ProtocolIE-ID ::= 785 + +``` + +END + +-- ASN1STOP + +## 9.4.8 Container Definitions + +-- ASN1START + +-- \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* + +``` + +-- +-- Container definitions +-- +-- ***** + +FlAP-Containers { + + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + + ngran-access (22) modules (3) flap (3) version1 (1) flap-Containers (5) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** + +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + + Criticality, + + Presence, + + PrivateIE-ID, + + ProtocolExtensionID, + +``` + +``` + +ProtocolIE-ID + +FROM FlAP-CommonDataTypes + maxPrivateIEs, + maxProtocolExtensions, + maxProtocolIEs + +FROM FlAP-Constants; + +-- ***** +-- +-- Class Definition for Protocol IEs +-- +-- ***** + +FlAP-PROTOCOL-IES ::= CLASS { + &id ProtocolIE-ID UNIQUE, + &criticality Criticality, + &Value, + &presence Presence +} + +WITH SYNTAX { + ID &id + CRITICALITY &criticality + +``` + +``` + TYPE &Value + PRESENCE &presence +} + +-- ***** +-- +-- Class Definition for Protocol IEs +-- +-- ***** +``` + +``` +FLAP-PROTOCOL-IES-PAIR ::= CLASS { + &id ProtocolIE-ID UNIQUE, + &firstCriticality Criticality, + &FirstValue, + &secondCriticality Criticality, + &SecondValue, + &presence Presence +} +``` + +``` +WITH SYNTAX { + ID &id + FIRST CRITICALITY &firstCriticality + FIRST TYPE &FirstValue + SECOND CRITICALITY &secondCriticality + SECOND TYPE &SecondValue +} +``` + +``` + + PRESENCE &presence +} + +-- ***** +-- +-- Class Definition for Protocol Extensions +-- +-- ***** + +``` + +``` + +FLAP-PROTOCOL-EXTENSION ::= CLASS { + &id ProtocolExtensionID UNIQUE, + &criticality Criticality, + &Extension, + &presence Presence +} + +WITH SYNTAX { + ID &id + CRITICALITY &criticality + EXTENSION &Extension + PRESENCE &presence +} + +-- ***** +-- + +``` + +-- Class Definition for Private IEs + +-- + +-- \*\*\*\*\* + +FlAP-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 {FlAP-PROTOCOL-IES : IEsSetParam} ::= + +``` + +SEQUENCE (SIZE (0..maxProtocolIEs)) OF + ProtocolIE-Field {{IEsSetParam}} + +ProtocolIE-SingleContainer {FLAP-PROTOCOL-IES : IEsSetParam} ::= + ProtocolIE-Field {{IEsSetParam}} + +ProtocolIE-Field {FLAP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE { + id FLAP-PROTOCOL-IES.&id {{IEsSetParam}}, + criticality FLAP-PROTOCOL-IES.&criticality {{IEsSetParam}{@id}}, + value FLAP-PROTOCOL-IES.&Value {{IEsSetParam}{@id}} +} + +-- ***** +-- +-- Container for Protocol IE Pairs +-- +-- ***** + +ProtocolIE-ContainerPair {FLAP-PROTOCOL-IES-PAIR : IEsSetParam} ::= + SEQUENCE (SIZE (0..maxProtocolIEs)) OF + ProtocolIE-FieldPair {{IEsSetParam}} + +ProtocolIE-FieldPair {FLAP-PROTOCOL-IES-PAIR : IEsSetParam} ::= SEQUENCE { + id FLAP-PROTOCOL-IES-PAIR.&id {{IEsSetParam}}, + +``` + +``` + firstCriticality FLAP-PROTOCOL-IES-PAIR.&firstCriticality ({IEsSetParam}{@id}), + firstValue FLAP-PROTOCOL-IES-PAIR.&FirstValue ({IEsSetParam}{@id}), + secondCriticality FLAP-PROTOCOL-IES-PAIR.&secondCriticality ({IEsSetParam}{@id}), + secondValue FLAP-PROTOCOL-IES-PAIR.&SecondValue ({IEsSetParam}{@id}) +} +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- Container for Protocol Extensions +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +ProtocolExtensionContainer {FLAP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= +``` + +``` + SEQUENCE (SIZE (1..maxProtocolExtensions)) OF +``` + +``` + ProtocolExtensionField {ExtensionSetParam} +``` + +``` +ProtocolExtensionField {FLAP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE { +``` + +``` + id FLAP-PROTOCOL-EXTENSION.&id ({ExtensionSetParam}), + criticality FLAP-PROTOCOL-EXTENSION.&criticality ({ExtensionSetParam}{@id}), + extensionValue FLAP-PROTOCOL-EXTENSION.&Extension ({ExtensionSetParam}{@id}) +} +``` + +``` +-- ***** +``` + +``` +-- +``` + +``` +-- Container for Private IEs +``` + +``` +-- +``` + +``` +-- ***** +``` + +``` +PrivateIE-Container {FLAP-PRIVATE-IES : IEsSetParam} ::= +``` + +``` + SEQUENCE (SIZE (1.. maxPrivateIEs)) OF +``` + +``` + PrivateIE-Field {IEsSetParam} +``` + +``` +PrivateIE-Field {FLAP-PRIVATE-IES : IEsSetParam} ::= SEQUENCE { +``` + +``` + id FLAP-PRIVATE-IES.&id ({IEsSetParam}), +``` + +``` + criticality FLAP-PRIVATE-IES.&criticality ({IEsSetParam}{@id}), +``` + +``` + value FLAP-PRIVATE-IES.&Value ({IEsSetParam}{@id}) +``` + +``` +} +``` + +``` +END +``` + +``` +-- ASN1STOP +``` + +## 9.5 Message Transfer Syntax + +FIAP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax, as specified in ITU-T Recommendation X.691 [5]. + +## 9.6 Timers + +--- + +## 10 Handling of unknown, unforeseen and erroneous protocol data + +Clause 10 of TS 38.413 [3] 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 | | +| 2017-06 | R3 NR#2 | R3-172493 | - | - | - | First version | 0.1.0 | | +| 2017-07 | R3 NR#2 | R3-172640 | - | - | - | Incorporated agreed TPs from R3 NR#2 Adhoc | 0.2.0 | | +| 2017-08 | R3#97 | R3-173451 | - | - | - | Incorporated agreed TPs from R3#97 | 0.3.0 | | +| 2017-10 | R3#97b | R3-174247 | - | - | - | Incorporated agreed TPs from R3#97b | 0.4.0 | | +| 2017-12 | R3#98 | R3-175062 | - | - | - | Incorporated agreed TPs from R3#98 | 0.5.0 | | +| 2017-12 | RAN#78 | RP-172287 | | | | Submitted for approval to RAN | 1.0.0 | | +| 2017-12 | RAN#78 | | | | | TR approved by RAN plenary | 15.0.0 | | +| 2018-03 | RP-79 | RP-180468 | 0001 | 2 | B | Baseline CR for March version of TS 38.473 covering agreements of RAN3#99 | 15.1.0 | | +| 2018-04 | | | | | | Editorial correction to ASN.1 (correction to id-TimeToWait ProtocolIE-ID) | 15.1.1 | | +| 2018-06 | RP-80 | RP-181237 | 0011 | 6 | B | Introduction of SA NR (38.473 Baseline CR covering RAN3 agreements) | 15.2.0 | | +| 2018-06 | RP-80 | RP-181239 | 0043 | 3 | F | Essential corrections of EN-DC for NSA NR (38.473 Baseline CR covering RAN3 agreements) | 15.2.0 | | +| 2018-06 | RP-80 | RP-181237 | 0045 | - | B | F1 support for LTE - NR coexistence | 15.2.0 | | +| 2018-06 | RP-80 | | | | | Correction to ASN.1 and to Change History table | 15.2.1 | | +| 2018-09 | RP-81 | RP-181920 | 0055 | 2 | F | Introduction of DU Configuration Query | 15.3.0 | | +| 2018-09 | RP-81 | RP-181921 | 0056 | 4 | F | CR to 38.473 on further clarifications on System information transfer over F1 | 15.3.0 | | +| 2018-09 | RP-81 | RP-181921 | 0058 | 4 | F | CR to 38.473 on corrections to System information delivery | 15.3.0 | | +| 2018-09 | RP-81 | RP-181920 | 0059 | 1 | F | CR to 38.473 on corrections to PWS transfer over F1 | 15.3.0 | | +| 2018-09 | RP-81 | RP-181921 | 0063 | 3 | F | CR to 38.473 on PDCP SN over F1 interface | 15.3.0 | | +| 2018-09 | RP-81 | RP-181922 | 0064 | 3 | F | NR Corrections (38.473 Baseline CR covering RAN3-101 agreements) | 15.3.0 | | +| 2018-09 | RP-81 | RP-181997 | 0068 | - | F | Introduction of UL AMBR on F1 | 15.3.0 | | +| 2018-09 | RP-81 | RP-181921 | 0072 | 3 | F | Correction on cell management | 15.3.0 | | +| 2018-09 | RP-81 | RP-181921 | 0073 | 2 | F | RLC Mode Indication over F1 | 15.3.0 | | +| 2018-09 | RP-81 | RP-181921 | 0076 | 3 | F | CR to 38.473 on UE Identity Index value | 15.3.0 | | +| 2018-09 | RP-81 | RP-181920 | 0077 | 1 | F | Correction for UE Context Modification on presence of ServCellIndex IE | 15.3.0 | | +| 2018-09 | RP-81 | RP-181920 | 0078 | - | F | Executing duplication for RRC-container | 15.3.0 | | +| 2018-09 | RP-81 | RP-181921 | 0079 | 1 | F | Indication of RLC re-establishment at the gNB-DU | 15.3.0 | | +| 2018-09 | RP-81 | RP-181920 | 0080 | - | F | Exchange of SMTC over F1 | 15.3.0 | | +| 2018-09 | RP-81 | RP-181920 | 0081 | - | F | Solving remaining issues with QoS parameters – TS 38.473 | 15.3.0 | | +| 2018-09 | RP-81 | RP-181921 | 0090 | - | F | Correction of 5GS TAC | 15.3.0 | | +| 2018-09 | RP-81 | RP-181921 | 0095 | 1 | F | Extend the RANAC size to 8bits | 15.3.0 | | +| 2018-09 | RP-81 | RP-181921 | 0097 | - | F | Corrections of Choice | 15.3.0 | | +| 2018-09 | RP-81 | RP-181921 | 0098 | 1 | F | Correction of TNL criticality | 15.3.0 | | +| 2018-09 | RP-81 | RP-181921 | 0099 | 1 | F | Corrections of usage of single container | 15.3.0 | | +| 2018-09 | RP-81 | RP-181921 | 0105 | 2 | B | RRc version handling | 15.3.0 | | +| 2018-09 | RP-81 | RP-181921 | 0106 | 1 | B | Introduction of Overload Handling in F1-C | 15.3.0 | | +| 2018-09 | RP-81 | RP-181921 | 0113 | - | F | CR to 38.473 on presence of QoS information | 15.3.0 | | +| 2018-09 | RP-81 | RP-181921 | 0114 | 1 | F | Correction C-RNTI format | 15.3.0 | | +| 2018-09 | RP-81 | RP-181921 | 0115 | - | F | Correction of QoS Parameters | 15.3.0 | | +| 2018-09 | RP-81 | RP-181921 | 0116 | 1 | F | Correction on F1 Setup Request | 15.3.0 | | +| 2018-12 | RP-82 | RP-182446 | 0070 | 3 | F | RRc Delivery Indication | 15.4.0 | | +| 2018-12 | RP-82 | RP-182446 | 0117 | 1 | F | Correction of AMBR Enforcement | 15.4.0 | | +| 2018-12 | RP-82 | RP-182446 | 0138 | - | F | CR for correction on Initial UL RRC message transfer | 15.4.0 | | +| 2018-12 | RP-82 | RP-182446 | 0140 | 1 | F | CR to 38.473 on bearer type change indication | 15.4.0 | | +| 2018-12 | RP-82 | RP-182446 | 0142 | 1 | F | CR to 38.473 on correction to PWS System Information | 15.4.0 | | +| 2018-12 | RP-82 | RP-182446 | 0144 | 2 | F | CR to 38.473 on asymmetric mapping for UL and DL QoS flow | 15.4.0 | | +| 2018-12 | RP-82 | RP-182447 | 0145 | 4 | F | Corrections on UE-associated LTE/NR resource coordination | 15.4.0 | | +| 2018-12 | RP-82 | RP-182446 | 0147 | 2 | F | CR for F1 Cell Management | 15.4.0 | | + +| Change history | | | | | | | | | +|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------|-------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 2018-12 | RP-82 | RP-182447 | 0150 | 1 | F | Missing Transaction ID in non-UE-associated procedures | 15.4.0 | | +| 2018-12 | RP-82 | RP-182446 | 0157 | 1 | F | CR to 38.473 on mapping of servingCellMO and Serving Cell | 15.4.0 | | +| 2018-12 | RP-82 | RP-182446 | 0160 | 1 | F | CR to 38.473 on UE context modification required procedure | 15.4.0 | | +| 2018-12 | RP-82 | RP-182447 | 0165 | 1 | F | Addition of the RLC Mode information for bearer modification | 15.4.0 | | +| 2018-12 | RP-82 | RP-182448 | 0167 | 2 | F | Rapporteur CR to align tabular | 15.4.0 | | +| 2018-12 | RP-82 | RP-182448 | 0168 | 2 | F | Rapporteur CR to align ASN.1 | 15.4.0 | | +| 2018-12 | RP-82 | RP-182447 | 0169 | 2 | F | Correction of MaxnoofBPLMNs | 15.4.0 | | +| 2018-12 | RP-82 | RP-182351 | 0174 | 2 | F | Correction on PDCP SN length on F1 | 15.4.0 | | +| 2018-12 | RP-82 | RP-182447 | 0178 | 2 | F | CR for TS 38.473 for MR-DC coordination | 15.4.0 | | +| 2018-12 | RP-82 | RP-182447 | 0179 | 2 | F | Support of system information update for active UE without CSS | 15.4.0 | | +| 2018-12 | RP-82 | RP-182447 | 0187 | 1 | F | CR to 38.473 on clarification to the presence of UE AMBR | 15.4.0 | | +| 2018-12 | RP-82 | RP-182506 | 0195 | 2 | F | CR on Scell release for RLC failure | 15.4.0 | | +| 2018-12 | RP-82 | RP-182447 | 0205 | 1 | F | About bandcombinationindex and featureSetEntryIndex | 15.4.0 | | +| 2018-12 | RP-82 | RP-182447 | 0211 | 1 | F | CR to 38.473 on DRB PDCP duplication | 15.4.0 | | +| 2018-12 | RP-82 | RP-182447 | 0216 | 1 | F | CR to 38.473 on clarifications on system information update over F1 | 15.4.0 | | +| 2018-12 | RP-82 | RP-182448 | 0219 | - | F | Correction of RRC version handling and UE inactivity notification | 15.4.0 | | +| 2019-01 | RP-82 | | | | | - correction to ASN.1:
addming a missing change to "WriteReplaceWarningResponseEs F1AP-PROTOCOL-IES ::= {" | 15.4.1 | | +| 2019-03 | RP-83 | RP-190555 | 0202 | 2 | F | Indication that cells are only UL or DL on F1 | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0204 | 1 | F | AMF initiated UE Context Release failure cause | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0220 | 1 | F | Correction to reconfiguration with sync for gNB-DU | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0225 | 1 | F | Introduction of PH-InforSCG in DU to CU RRC Information | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0226 | 1 | F | CR to 38.473 on Measurement gap coordination | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0228 | 1 | F | CR for TS 38.473 for MR-DC coordination | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0229 | 2 | F | Condition for inclusion of the Dedicated SI Delivery Needed UE List IE | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0230 | 1 | F | Correction of the Transmission stop/restart indication | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0231 | - | F | Corrections on gNB-CU/gNB-DU Configuration Update | 15.5.0 | | +| 2019-03 | RP-83 | RP-190556 | 0236 | 2 | F | Correction of QoS Flow Mapping Indication | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0244 | - | F | Release due to pre-emption | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0245 | 2 | F | CR on RRC container in UE context modification request message | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0246 | 2 | F | CR on UE context modification refuse | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0247 | - | F | Transaction ID in Error Indication procedure | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0249 | 2 | F | Cells to be deactivated over F1 | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0251 | 1 | F | CR to 38.473 on SRB duplication and LCID | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0258 | - | F | CR to 38.473 on corrections for removal of PDCP duplication for SRB | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0263 | 1 | F | CR to 38.473 on transfering UEAssistanceInformation over F1 | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0265 | - | F | Rapporteur updates | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0266 | 1 | F | Correction on gNB-DU Resource Coordination | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0267 | 1 | F | Endpoint IP address and port | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0268 | 1 | F | Correction to add paging origin IE | 15.5.0 | | +| 2019-03 | RP-83 | RP-190555 | 0269 | 2 | F | Multiple SCTP associations over F1AP | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0272 | 1 | F | About Cells Failed to be Activated IE in gNB-CU Configuration Update Ack | 15.5.0 | | +| 2019-03 | RP-83 | RP-190556 | 0273 | 1 | F | gNB-DU UE Aggregate Maximum Bit Rate Uplink correction | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0276 | 1 | F | RRC Reconfiguration failure | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0278 | 1 | F | Node behaviour at reception of DU to CU RRC Information | 15.5.0 | | +| 2019-03 | RP-83 | RP-190554 | 0281 | - | F | Addition of Transaction ID to Initial UL RRC Message Transfer | 15.5.0 | | +| 2019-07 | RP-84 | RP-191397 | 0200 | 5 | F | RAN sharing with multiple Cell ID broadcast | 15.6.0 | | +| 2019-07 | RP-84 | RP-191397 | 0270 | 5 | F | Addition of Network Access Rate Reduction message | 15.6.0 | | +| 2019-07 | RP-84 | RP-191397 | 0271 | 3 | F | RAN UE ID for F1 | 15.6.0 | | +| 2019-07 | RP-84 | RP-191396 | 0283 | 2 | F | MR-DC resource coordination in F1 | 15.6.0 | | +| 2019-07 | RP-84 | RP-191396 | 0316 | 2 | F | Full configuration indication from gNB-CU to gNB-DU. | 15.6.0 | | +| 2019-07 | RP-84 | RP-191396 | 0322 | 2 | F | CR to 38.473 on clarification to RRC reconfigure complete indicator | 15.6.0 | | +| 2019-07 | RP-84 | RP-191394 | 0326 | 2 | F | CR to 38.473 on deconfiguring CA based PDCP duplication for DRB | 15.6.0 | | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2019-07 | RP-84 | RP-191395 | 0330 | 3 | F | CR to 38.473 on Removal of Multiple TNLAs | 15.6.0 | +| 2019-07 | RP-84 | RP-191396 | 0348 | - | F | Full configuration in UE Context Setup | 15.6.0 | +| 2019-07 | RP-84 | RP-191396 | 0351 | 2 | F | CR on PWS segmentation over F1 | 15.6.0 | +| 2019-07 | RP-84 | RP-191396 | 0352 | 1 | F | CR on cell type over F1 | 15.6.0 | +| 2019-07 | RP-84 | RP-191396 | 0357 | - | F | Rapporteur updates: Alignment and editorials | 15.5.0 | +| 2019-07 | RP-84 | RP-191396 | 0358 | - | F | Rapporteur update: Correction of Presence for DRB information | 15.6.0 | +| 2019-07 | RP-84 | RP-191396 | 0359 | - | F | Rapporteur updates: Correction of Presence for E-UTRA PRACH Configuration | 15.6.0 | +| 2019-07 | RP-84 | RP-191396 | 0370 | - | F | Full configuration IE included in the UE Context Modification Response. | 15.6.0 | +| 2019-07 | RP-84 | RP-191396 | 0376 | - | F | CR to 38.473 on clarification for UP TNL Information IE over F1 | 15.6.0 | +| 2019-07 | RP-84 | RP-191396 | 0377 | 2 | F | Procedure description on optional IEs in CU to DU RRC information IE. | 15.6.0 | +| 2019-09 | RP-85 | RP-192166 | 0343 | 3 | F | CR on MR-DC low layer coordination with an MgNB-DU | 15.7.0 | +| 2019-09 | RP-85 | RP-192166 | 0344 | 2 | F | CR on MCG PHR format in MgNB-DU | 15.7.0 | +| 2019-09 | RP-85 | RP-192166 | 0388 | - | F | CR on DC Coordination for PDCCH Blind Detection | 15.7.0 | +| 2019-09 | RP-85 | RP-192167 | 0393 | 1 | F | Rapporteur update - clarification of semantics | 15.7.0 | +| 2019-09 | RP-85 | RP-192166 | 0399 | 1 | F | Clarification for TNLA removal | 15.7.0 | +| 2019-12 | RP-86 | RP-192915 | 0318 | 5 | F | Correction about gNB-CU System Information IE | 15.8.0 | +| 2019-12 | RP-86 | RP-192915 | 0447 | 1 | F | On CellGroupConfig handling | 15.8.0 | +| 2019-12 | RP-86 | RP-192915 | 0458 | 1 | F | Correction of S-NSSAI coding | 15.8.0 | +| 2019-12 | RP-86 | RP-192915 | 0459 | 1 | F | Removal of Requested P-MaxFR2 | 15.8.0 | +| 2019-12 | RP-86 | RP-192915 | 0479 | 2 | F | Addition of Message Identifier and Serial Number to PWS Cancel Request | 15.8.0 | +| 2019-12 | RP-86 | RP-192916 | 0482 | 2 | F | Clarifications on SCell lists | 15.8.0 | +| 2019-12 | RP-86 | RP-192916 | 0494 | - | F | RRC Container in Modification Procedure | 15.8.0 | +| 2019-12 | RP-86 | RP-192916 | 0508 | 0 | F | CR to 38.473 on applicability of the IE Selected BandCombinationIndex and Selected FeatureSetEntryIndex | 15.8.0 | +| 2019-12 | RP-86 | RP-192916 | 0509 | 1 | F | CR to 38.473 on MeasGapSharingConfig and gNB-CU System Information | 15.8.0 | +| 2019-12 | RP-86 | RP-192916 | 0510 | 1 | F | CR to 38.473 on cause values over F1 | 15.8.0 | +| 2019-12 | RP-86 | RP-192916 | 0515 | 2 | F | Clarification on Initial UL RRC Message Transfer procedure | 15.8.0 | +| 2019-12 | RP-86 | RP-192913 | 0280 | 7 | F | Trace function support for F1AP | 16.0.0 | +| 2019-12 | RP-86 | RP-192908 | 0287 | 7 | B | Support for CLI | 16.0.0 | +| 2019-12 | RP-86 | RP-192913 | 0314 | 5 | B | Introduction of Additional RRM Policy Index (ARPI) | 16.0.0 | +| 2019-12 | RP-86 | RP-192908 | 0339 | 6 | B | CR to F1-AP for RIM new message | 16.0.0 | +| 2019-12 | RP-86 | RP-192915 | 0460 | - | F | Removal of unused IEs | 16.0.0 | +| 2019-12 | RP-86 | RP-192913 | 0463 | 1 | C | Extending the MDBV Range | 16.0.0 | +| 2019-12 | RP-86 | RP-192910 | 0514 | 3 | B | CR for TS38.473 on supporting SN Resume during the RRCResume procedure | 16.0.0 | +| 2019-12 | RP-86 | RP-192914 | 0518 | 2 | F | Support for setting up IPSec a priori in F1 | 16.0.0 | +| 2020-03 | RP-87-e | RP-200428 | 0522 | 1 | A | Correction of PWS Failure Indication | 16.1.0 | +| 2020-03 | RP-87-e | RP-200428 | 0525 | - | A | Correction of the presence of UL UP TNL Information to be setup List IE in tabular | 16.1.0 | +| 2020-03 | RP-87-e | RP-200425 | 0527 | 2 | F | Corrections to CLI | 16.1.0 | +| 2020-03 | RP-87-e | RP-200425 | 0528 | 1 | D | Rapporteur: Editorial updates | 16.1.0 | +| 2020-03 | RP-87-e | RP-200425 | 0530 | 2 | B | E2E delay measurement for Qos monitoring for URLLC | 16.1.0 | +| 2020-03 | RP-87-e | RP-200428 | 0534 | 1 | A | Correction relating to Initial UL RRC Message Transfer procedure CR 38.473 | 16.1.0 | +| 2020-07 | RP-88-e | RP-201077 | 0285 | 17 | B | BL CR to 38.473: Support for IAB | 16.2.0 | +| 2020-07 | RP-88-e | RP-201074 | 0432 | 12 | B | Support of NR V2X over F1 | 16.2.0 | +| 2020-07 | RP-88-e | RP-201082 | 0441 | 12 | B | Addition of SON features | 16.2.0 | +| 2020-07 | RP-88-e | RP-201079 | 0477 | 8 | B | Introduction of NR_IOT support to TS 38.473 | 16.2.0 | +| 2020-07 | RP-88-e | RP-201075 | 0481 | 10 | B | Baseline CR for introducing Rel-16 NR mobility enhancement | 16.2.0 | +| 2020-07 | RP-88-e | RP-201082 | 0492 | 6 | B | Addition of MDT features | 16.2.0 | +| 2020-07 | RP-88-e | RP-201080 | 0502 | 7 | B | Introduction of NPN | 16.2.0 | +| 2020-07 | RP-88-e | RP-201076 | 0537 | 1 | B | CR38.473 on TDD pattern for NR-DC power control cordination for sol1 | 16.2.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|----------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2020-07 | RP-88-e | RP-201085 | 0539 | - | F | Rapporteur: Corrections after implementation | 16.2.0 | +| 2020-07 | RP-88-e | RP-201090 | 0543 | 2 | A | Encoding PLMNs in served cell information NR | 16.2.0 | +| 2020-07 | RP-88-e | RP-201091 | 0545 | 1 | A | Correction for usage of Cell Broadcast Cancelled List | 16.2.0 | +| 2020-07 | RP-88-e | RP-201091 | 0548 | 1 | A | Correction on UE CONTEXT MODIFICATION REQUIRED message | 16.2.0 | +| 2020-07 | RP-88-e | RP-201085 | 0561 | 1 | F | Correction on CLI | 16.2.0 | +| 2020-07 | RP-88-e | RP-201090 | 0567 | - | A | Encoding PLMNs in served cell information IEs - semantics corrections | 16.2.0 | +| 2020-07 | RP-88-e | RP-201092 | 0570 | 1 | A | Correction for UL UP TNL Information | 16.2.0 | +| 2020-07 | RP-88-e | RP-201092 | 0572 | - | A | Correction on RRC Container in Initial UL RRC Message Transfer | 16.2.0 | +| 2020-07 | RP-88-e | RP-201092 | 0576 | 1 | A | Correction on RRC Connection Reconfiguration Complete Indicator | 16.2.0 | +| 2020-07 | RP-88-e | RP-201092 | 0581 | 2 | F | Corrections of Inactive UE Context stored at gNB-DU | 16.2.0 | +| 2020-07 | RP-88-e | RP-201085 | 0600 | 2 | F | Correction on RF parameters in NR cell information | 16.2.0 | +| 2020-07 | RP-88-e | RP-201090 | 0601 | 4 | F | Correction of S-NSSAI range | 16.2.0 | +| 2020-07 | RP-88-e | RP-201092 | 0603 | 2 | A | Correction for Handover Preparation Information | 16.2.0 | +| 2020-07 | RP-88-e | RP-201092 | 0607 | 1 | A | CR on Concurrent Warning Message Indicator over F1 (Rel-16) | 16.2.0 | +| 2020-07 | RP-88-e | RP-201092 | 0615 | - | A | Section renumbering for PWS cancel | 16.2.0 | +| 2020-07 | RP-88-e | RP-201092 | 0616 | - | A | Correction on DL RRC MESSAGE TRANSFER | 16.2.0 | +| 2020-07 | RP-88-e | RP-201092 | 0618 | - | A | Addition of abnormal conditions in PWS Cancel procedure | 16.2.0 | +| 2020-09 | RP-89-e | RP-201850 | 0495 | 10 | B | Introduction of positioning support over F1AP | 16.3.0 | +| 2020-09 | RP-89-e | RP-201956 | 0557 | 2 | A | Support of PSCell/SCell-only operation mode | 16.3.0 | +| 2020-09 | RP-89-e | RP-201956 | 0583 | 5 | F | Cell Creation Rejection when max number of supported cells is exceeded at CU CR 38.473 | 16.3.0 | +| 2020-09 | RP-89-e | RP-201956 | 0587 | 5 | A | Measurement gap deactivation over F1AP CR 38.473 | 16.3.0 | +| 2020-09 | RP-89-e | RP-201949 | 0619 | 2 | F | Slot list length correction in TDD UL-DL Configuration | 16.3.0 | +| 2020-09 | RP-89-e | RP-201956 | 0625 | 1 | F | Addition of abnormal conditions in Write-Replace Warning procedure | 16.3.0 | +| 2020-09 | RP-89-e | RP-201956 | 0628 | 2 | A | Correction of PSCell/SCell-only mode | 16.3.0 | +| 2020-09 | RP-89-e | RP-201956 | 0634 | 1 | A | Correction on UE Context Modification Procedure | 16.3.0 | +| 2020-09 | RP-89-e | RP-201956 | 0639 | 1 | F | Rapporteur Corrections | 16.3.0 | +| 2020-09 | RP-89-e | RP-201949 | 0640 | - | F | Correction of procedure ID | 16.3.0 | +| 2020-09 | RP-89-e | RP-201956 | 0642 | - | A | Correction of PWS cancel | 16.3.0 | +| 2020-09 | RP-89-e | RP-201949 | 0643 | 1 | F | Corrections on PC5 Link Aggregated Bit Rate | 16.3.0 | +| 2020-09 | RP-89-e | RP-201949 | 0660 | - | F | Correction on the Maximum Number of CHO Preparations in F1AP | 16.3.0 | +| 2020-09 | RP-89-e | RP-201956 | 0663 | 1 | F | Corrections to 38.473 on node name type | 16.3.0 | +| 2020-09 | RP-89-e | RP-201947 | 0664 | 1 | F | Correction on IAB-DU configuration | 16.3.0 | +| 2020-09 | RP-89-e | RP-201982 | 0671 | - | F | Correction on IAB-DU configuration | 16.3.0 | +| 2020-09 | RP-89-e | | | | | Correct wrong numbering of protocolIE-ID in clause 9.4.7 | 16.3.1 | +| 2020-12 | RP-90-e | RP-202310 | 0645 | 2 | F | Uniqueness of BH RLC channel ID | 16.4.0 | +| 2020-12 | RP-90-e | RP-202310 | 0658 | 3 | F | Correction on V2X related information | 16.4.0 | +| 2020-12 | RP-90-e | RP-202310 | 0665 | 2 | F | Correction on unsuccessful operations of IAB procedures | 16.4.0 | +| 2020-12 | RP-90-e | RP-202310 | 0666 | 1 | F | Correction on the identification of IAB-donor-DU | 16.4.0 | +| 2020-12 | RP-90-e | RP-202310 | 0667 | 2 | F | Correction on the Context Setup procedure for IAB node | 16.4.0 | +| 2020-12 | RP-90-e | RP-202310 | 0668 | 1 | F | Correction on BAP address | 16.4.0 | +| 2020-12 | RP-90-e | RP-202310 | 0672 | 1 | F | CR on F1-C transfer for Rel-16 IAB | 16.4.0 | +| 2020-12 | RP-90-e | RP-202311 | 0677 | - | F | Correction of F1AP positioning procedures | 16.4.0 | +| 2020-12 | RP-90-e | RP-202311 | 0678 | 1 | F | Corrections to tabular and asn.1 for NR positioning (F1AP) | 16.4.0 | +| 2020-12 | RP-90-e | RP-202310 | 0681 | 1 | F | Correction of alternative QoS profile | 16.4.0 | +| 2020-12 | RP-90-e | RP-202313 | 0683 | - | F | Removal of duplicated imports | 16.4.0 | +| 2020-12 | RP-90-e | RP-202312 | 0684 | 2 | F | Corrections of UL and DL carrier list | 16.4.0 | +| 2020-12 | RP-90-e | RP-202311 | 0689 | 1 | F | RRC alignment and various correction including ASN.1 | 16.4.0 | +| 2020-12 | RP-90-e | RP-202311 | 0691 | 1 | F | Correction of RLC Duplication Information over F1 | 16.4.0 | +| 2020-12 | RP-90-e | RP-202288 | 0695 | 3 | A | Correction on value range of UAC reduction Indication | 16.4.0 | +| 2020-12 | RP-90-e | RP-202311 | 0709 | 1 | F | Coupling TRP ID and Cell ID in Measurement procedures | 16.4.0 | +| 2021-03 | RP-91-e | RP-210123 | 0431 | 7 | B | Introduction of SFN Offset per cell over F1 | 16.5.0 | +| 2021-03 | RP-91-e | RP-210240 | 0632 | 6 | A | Correction on Overlapping Band Handling over F1 | 16.5.0 | +| 2021-03 | RP-91-e | RP-210235 | 0676 | 2 | F | Correction on PRACH coordination | 16.5.0 | +| 2021-03 | RP-91-e | RP-210239 | 0702 | 3 | F | Cause value on F1 for insufficient UE capabilities CR 38.473 | 16.5.0 | +| 2021-03 | RP-91-e | RP-210239 | 0711 | 1 | F | Update on QoS monitoring control | 16.5.0 | + +| Change history | | | | | | | | | +|----------------|---------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------|-------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 2021-03 | RP-91-e | RP-210233 | 0715 | 2 | F | Stage-3 CR on transmission stop for Rel-16 DAPS handover | 16.5.0 | | +| 2021-03 | RP-91-e | RP-210232 | 0720 | 1 | F | Correction of NPN related Cell Information | 16.5.0 | | +| 2021-03 | RP-91-e | RP-210231 | 0721 | - | F | Correction on IAB configuration | 16.5.0 | | +| 2021-03 | RP-91-e | RP-210231 | 0722 | - | F | Correction on BAP address configuration for IAB-donor-DU | 16.5.0 | | +| 2021-03 | RP-91-e | RP-210230 | 0725 | 1 | F | Including SRS frequency information in Positioning Information Request | 16.5.0 | | +| 2021-03 | RP-91-e | RP-210231 | 0728 | 2 | F | CR to 38.473: Correction on IAB related definitions and unsuccessful establishment of a BH RLC channel | 16.5.0 | | +| 2021-03 | RP-91-e | RP-210230 | 0736 | - | F | Correction of the PCI IE presence in the ASN.1 for the SRS Configuration | 16.5.0 | | +| 2021-06 | RP-92-e | RP-211334 | 0704 | 4 | A | How to release SCG configuration between MN-CU and MN-DU CR 38.473 | 16.6.0 | | +| 2021-06 | RP-92-e | RP-211315 | 0712 | 2 | F | Clarification on TAI Slice Support List | 16.6.0 | | +| 2021-06 | RP-92-e | RP-211323 | 0740 | 2 | F | Enabling CHO with SCG configuration | 16.6.0 | | +| 2021-06 | RP-92-e | RP-211327 | 0743 | - | F | Correction of Spatial Relation Information | 16.6.0 | | +| 2021-06 | RP-92-e | RP-211317 | 0744 | - | F | Correction on reference to RACH-Report | 16.6.0 | | +| 2021-06 | RP-92-e | RP-211330 | 0753 | - | F | Stage-3 CR on system information message over F1 (Rel-16) | 16.6.0 | | +| 2021-06 | RP-92-e | RP-211333 | 0760 | - | A | Correction on SRB ID | 16.6.0 | | +| 2021-06 | RP-92-e | RP-211334 | 0762 | 3 | A | gNB-DU UE Aggregate Maximum Bit Rate Uplink correction | 16.6.0 | | +| 2021-06 | RP-92-e | RP-211322 | 0763 | - | F | Miscellaneous corrections on IAB in TS 38.473 | 16.6.0 | | +| 2021-06 | RP-92-e | RP-211327 | 0765 | 1 | F | Correction on SFN Initialisation Time | 16.6.0 | | +| 2021-06 | RP-92-e | RP-211327 | 0766 | - | F | Correction on relative cartesian coordinate | 16.6.0 | | +| 2021-06 | RP-92-e | RP-211322 | 0770 | 1 | F | Correction on BH RLC CH configured for BAP control PDU | 16.6.0 | | +| 2021-06 | RP-92-e | RP-211322 | 0771 | - | F | Correction on gNB-DU Resource Configuration | 16.6.0 | | +| 2021-06 | RP-92-e | RP-211322 | 0772 | 1 | F | Correction on UL BH information configuration for DRBs support CA based duplication | 16.6.0 | | +| 2021-06 | RP-92-e | RP-211317 | 0776 | 1 | F | Correction on MLB for TS 38.473 | 16.6.0 | | +| 2021-09 | RP-93-e | RP-211876 | 0790 | 1 | F | Correction of served cell information for NPN | 16.7.0 | | +| 2021-09 | RP-93-e | RP-211880 | 0792 | 1 | F | Correction of wrong CR implementation for Stage-3 CR on transmission stop for Rel-16 DAPS handover | 16.7.0 | | +| 2021-09 | RP-93-e | RP-211883 | 0796 | 1 | F | Adding procedural text for System Frame Number and Slot Number | 16.7.0 | | +| 2021-09 | RP-93-e | RP-211881 | 0800 | - | A | Correction of the IE related to E-UTRA resource coordination in F1AP | 16.7.0 | | +| 2021-12 | RP-94-e | RP-212864 | 0804 | 1 | A | Correction on F1 Removal for RAN Sharing in Rel-16 | 16.8.0 | | +| 2021-12 | RP-94-e | RP-212864 | 0811 | 4 | F | Incorrect Node Name IE in ASN.1 | 16.8.0 | | +| 2021-12 | RP-94-e | RP-213174 | 0822 | 3 | F | Correction on PRS-only TRP | 16.8.0 | | +| 2021-12 | RP-94-e | RP-212867 | 0827 | 1 | F | Support of providing spatial relation per SRS resource from gNB-CU to gNB-DU | 16.8.0 | | +| 2022-03 | RP-95-e | RP-220279 | 0778 | 4 | F | Support of dynamic ACL during dual connectivity | 16.9.0 | | +| 2022-03 | RP-95-e | RP-220276 | 0837 | 1 | F | Correction on packet delay budget for IAB access link in TS 38.473 | 16.9.0 | | +| 2022-03 | RP-95-e | RP-220276 | 0838 | - | F | CR to 38.473: Correction on IAB TNL Address Allocation procedure | 16.9.0 | | +| 2022-03 | RP-95-e | RP-220242 | 0844 | 2 | F | CR to TS38.473: Correction on PC5 QoS parameters for NR V2X | 16.9.0 | | +| 2022-03 | RP-95-e | RP-220281 | 0847 | 1 | F | Correction on positioning information configuration | 16.9.0 | | +| 2022-03 | RP-95-e | RP-220281 | 0848 | 1 | F | Correction on Measurement Periodicity | 16.9.0 | | +| 2022-03 | RP-95-e | RP-220281 | 0849 | 1 | F | Correction on PRS Beam Information | 16.9.0 | | +| 2022-03 | RP-95-e | RP-220281 | 0850 | - | F | CR for the correction on measurement gap configuration for position | 16.9.0 | | +| 2022-03 | RP-95-e | RP-220278 | 0854 | 1 | F | Correction of frequency information for DL only or UL only cell | 16.9.0 | | +| 2022-03 | RP-95-e | RP-220276 | 0860 | - | F | (Stage-3) Clarification on IAB Address Remove | 16.9.0 | | +| 2022-03 | RP-95-e | RP-220221 | 0710 | 9 | B | Addition of SON features enhancement | 17.0.0 | | +| 2022-03 | RP-95-e | RP-220224 | 0716 | 6 | B | Introduction of NR MBS | 17.0.0 | | +| 2022-03 | RP-95-e | RP-220222 | 0737 | 13 | B | CP-based Congestion Indication for IAB Networks | 17.0.0 | | +| 2022-03 | RP-95-e | RP-220221 | 0738 | 7 | B | BLCR to 38.473: Support of MDT enhancement | 17.0.0 | | +| 2022-03 | RP-95-e | RP-220223 | 0751 | 7 | B | Introduction of Enhanced IIoT support over F1 | 17.0.0 | | +| 2022-03 | RP-95-e | RP-220218 | 0777 | 10 | B | SCG BL CR to TS 38.473 | 17.0.0 | | +| 2022-03 | RP-95-e | RP-220218 | 0795 | 5 | B | BLCR to TS 38.473 for Conditional PScell Change/Addition | 17.0.0 | | +| 2022-03 | RP-95-e | RP-220228 | 0803 | 6 | B | Introduction of NR Positioning enhancements | 17.0.0 | | +| 2022-03 | RP-95-e | RP-220230 | 0806 | 6 | B | BL CR to F1AP on Rel-17 RedCap | 17.0.0 | | +| 2022-03 | RP-95-e | RP-220236 | 0817 | 2 | B | Addition of NR Timing Advance reporting for NR UL E-CID | 17.0.0 | | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| | | | | | | [NRTADV] | | +| 2022-03 | RP-95-e | RP-220229 | 0826 | 7 | B | Support of QoE information transfer | 17.0.0 | +| 2022-03 | RP-95-e | RP-220233 | 0833 | 3 | B | CG-SDT BLCR to TS38.473 | 17.0.0 | +| 2022-03 | RP-95-e | RP-220233 | 0834 | 3 | B | Support of RACH-based SDT | 17.0.0 | +| 2022-03 | RP-95-e | RP-220231 | 0842 | 3 | B | Introduction of SideLink Relay | 17.0.0 | +| 2022-03 | RP-95-e | RP-220219 | 0852 | 4 | B | Introduction of MultiSIM support over F1 | 17.0.0 | +| 2022-03 | RP-95-e | RP-220235 | 0855 | 4 | B | Support for UE Power Saving Enhancements | 17.0.0 | +| 2022-03 | RP-95-e | RP-220232 | 0856 | 1 | B | (BLCR to TS 38.473) Supporting network slicing enhancement | 17.0.0 | +| 2022-03 | RP-95-e | RP-220236 | 0858 | | D | Editorial corrections | 17.0.0 | +| 2022-06 | RP-96 | RP-221143 | 0862 | 2 | F | QoE Rel-17 Corrections | 17.1.0 | +| 2022-06 | RP-96 | RP-221132 | 0863 | - | F | Correction of PDC Measurement Periodicity values | 17.1.0 | +| 2022-06 | RP-96 | RP-221141 | 0864 | 1 | F | Correction of R17 SON features enhancement | 17.1.0 | +| 2022-06 | RP-96 | RP-221134 | 0865 | 1 | F | Corrections on NR MBS in F1AP | 17.1.0 | +| 2022-06 | RP-96 | RP-221134 | 0866 | - | F | NR MBS F1AP asn.1 correction | 17.1.0 | +| 2022-06 | RP-96 | RP-221136 | 0868 | 2 | F | Correction on CG based SDT | 17.1.0 | +| 2022-06 | RP-96 | RP-221150 | 0879 | 1 | A | F1AP CR for ACL remaining issues | 17.1.0 | +| 2022-06 | RP-96 | RP-221145 | 0880 | 4 | F | CR to 38.473 on Measurement Amount | 17.1.0 | +| 2022-06 | RP-96 | RP-221139 | 0884 | - | F | ASN.1 corrections on NR SL relay for 38.473 | 17.1.0 | +| 2022-06 | RP-96 | RP-221137 | 0887 | 2 | F | Correction to MUSIM | 17.1.0 | +| 2022-06 | RP-96 | RP-221139 | 0892 | 1 | F | Corrections for SL_relay (F1AP) | 17.1.0 | +| 2022-06 | RP-96 | RP-221126 | 0894 | 1 | F | Correction on RedCap Broadcast Information for TS38.473 | 17.1.0 | +| 2022-06 | RP-96 | RP-221131 | 0896 | 1 | F | F1AP ASN.1 review for NR Positioning Enhancements | 17.1.0 | +| 2022-06 | RP-96 | RP-221134 | 0897 | | F | Remove the editor's notes | 17.1.0 | +| 2022-06 | RP-96 | RP-221136 | 0900 | 1 | F | Correction on SRB SDT indication | 17.1.0 | +| 2022-06 | RP-96 | RP-221136 | 0901 | 1 | F | Correction on SDT termination request in F1 | 17.1.0 | +| 2022-06 | RP-96 | RP-221141 | 0902 | 1 | F | Correction on SON feature enhancements - F1AP | 17.1.0 | +| 2022-06 | RP-96 | RP-221131 | 0905 | 3 | F | Positioning corrections for F1AP | 17.1.0 | +| 2022-06 | RP-96 | RP-221132 | 0908 | 2 | F | Correction of PDC Measurement Initiation Failure message | 17.1.0 | +| 2022-06 | RP-96 | RP-221805 | 0910 | 2 | F | Correction for IAB inter-donor DU re-routing and resource multiplexing | 17.1.0 | +| 2022-06 | RP-96 | RP-221149 | 0913 | 1 | A | Correction on IAB-DU cell resource configuration | 17.1.0 | +| 2022-06 | RP-96 | RP-221130 | 0916 | 2 | F | CR to TS38.473: Correction on PC5 DRX parameters for NR V2X | 17.1.0 | +| 2022-06 | RP-96 | RP-221139 | 0920 | | F | Corrections on Remote UE Local ID | 17.1.0 | +| 2022-06 | RP-96 | RP-221141 | 0921 | 2 | F | F1AP corrections for NR-U | 17.1.0 | +| 2022-06 | RP-96 | RP-221152 | 0923 | 2 | A | Correction for PRS Muting | 17.1.0 | +| 2022-06 | RP-96 | RP-221132 | 0924 | 2 | F | NR-IoT F1AP correction | 17.1.0 | +| 2022-06 | RP-96 | RP-221129 | 0927 | 2 | F | Supporting network slice AS group | 17.1.0 | +| 2022-06 | RP-96 | RP-221129 | 0928 | 1 | F | Correction of the presence of UE-Slice-MBR | 17.1.0 | +| 2022-06 | RP-96 | RP-221141 | 0929 | - | F | Corrections to Load Balancing Enhancements | 17.1.0 | +| 2022-06 | RP-96 | RP-221139 | 0930 | 2 | F | Corrections for SL relay | 17.1.0 | +| 2022-06 | RP-96 | RP-221145 | 0932 | 2 | D | Editorial corrections | 17.1.0 | +| 2022-06 | RP-96 | RP-221134 | 0938 | 1 | F | Correction on MBS features | 17.1.0 | +| 2022-06 | RP-96 | RP-221136 | 0939 | 1 | F | Correction on SDT in F1AP | 17.1.0 | +| 2022-06 | RP-96 | RP-221136 | 0940 | 1 | F | Correction on Rel-17 SDT (F1AP) | 17.1.0 | +| 2022-06 | RP-96 | RP-221141 | 0945 | 1 | F | Correction on update management based MDT user consent | 17.1.0 | +| 2022-06 | RP-96 | RP-221131 | 0948 | 2 | F | Support of multiple measurement instances | 17.1.0 | +| 2022-06 | RP-96 | RP-221145 | 0949 | 1 | F | Supporting the disaster roaming information [MINT] | 17.1.0 | +| 2022-06 | RP-96 | RP-221150 | 0951 | 2 | A | SIB Issues Rel-17 | 17.1.0 | +| 2022-06 | RP-96 | RP-221150 | 0953 | 1 | A | gNB-CU and gNB-DU Name in Configuration Update Procedures | 17.1.0 | +| 2022-06 | RP-96 | RP-221137 | 0957 | - | F | Clarification on the paging cause | 17.1.0 | +| 2022-06 | RP-96 | RP-221143 | 0958 | 1 | F | CR to 38.473 on ASN.1 corrections of QoE measurement | 17.1.0 | +| 2022-06 | RP-96 | RP-221152 | 0964 | | A | ASN.1 correction for UL-AoA | 17.1.0 | +| 2022-06 | RP-96 | RP-221141 | 0965 | 1 | F | ASN.1 corrections | 17.1.0 | +| 2022-06 | RP-96 | RP-221141 | 0968 | 1 | F | CCO corrections | 17.1.0 | +| 2022-06 | RP-96 | RP-221131 | 0969 | - | F | Corrections to Measurement Pre-configuration Information Transfer | 17.1.0 | +| 2022-06 | RP-96 | RP-221628 | 0971 | - | F | Removal of UE Tx TEG Association from F1AP | 17.1.0 | +| 2022-09 | RP-97-e | RP-222201 | 0889 | 2 | A | Correction on interFrequencyConfig-NoGap | 17.2.0 | +| 2022-09 | RP-97-e | RP-222189 | 0890 | 2 | F | Correction to SDT for supporting delta signaling | 17.2.0 | +| 2022-09 | RP-97-e | RP-222188 | 0978 | - | F | Correction on Broadcast and Unicast co-existence | 17.2.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-09 | RP-97-e | RP-222183 | 0981 | 1 | F | Miscellaneous Correction on IAB | 17.2.0 | +| 2022-09 | RP-97-e | RP-222188 | 0984 | 1 | F | Further Corrections for NR MBS | 17.2.0 | +| 2022-09 | RP-97-e | RP-222188 | 0985 | 2 | F | Corrections for the establishment of F1-U ptp retransmission tunnels | 17.2.0 | +| 2022-09 | RP-97-e | RP-222185 | 0986 | 3 | B | CR for TS38.473 on Extending NR Operation to 71GHz | 17.2.0 | +| 2022-09 | RP-97-e | RP-222186 | 0988 | | F | Addition of SRS port index | 17.2.0 | +| 2022-09 | RP-97-e | RP-222190 | 0989 | 1 | F | SL relay corrections | 17.2.0 | +| 2022-09 | RP-97-e | RP-222187 | 0994 | 1 | F | Correction of UE Paging Capability | 17.2.0 | +| 2022-09 | RP-97-e | RP-222201 | 0997 | 1 | F | Correction on measurement gap configuration over F1 in Rel-17 | 17.2.0 | +| 2022-09 | RP-97-e | RP-222186 | 0998 | 2 | F | Support of timing error margins for TEGs in F1AP | 17.2.0 | +| 2022-09 | RP-97-e | RP-222188 | 1000 | 1 | F | Introduction of MBS specific cause values | 17.2.0 | +| 2022-09 | RP-97-e | RP-222188 | 1001 | 1 | F | Correction on Multicast Group Paging | 17.2.0 | +| 2022-09 | RP-97-e | RP-222188 | 1002 | 1 | F | Correction on MRB ID Change | 17.2.0 | +| 2022-09 | RP-97-e | RP-222603 | 1004 | 4 | A | CR to 38.473 on E-CID measurement periodicity | 17.2.0 | +| 2022-09 | RP-97-e | RP-222088 | 1013 | 3 | F | Correction on RedCap paging capability | 17.2.0 | +| 2022-09 | RP-97-e | RP-222186 | 1016 | 1 | F | Rel-17 ePos correction for the missing support of SRS-PosRRC-InactiveConfig-r17 configuration | 17.2.0 | +| 2022-09 | RP-97-e | RP-222189 | 1017 | 1 | F | Transferring CG-SDT configuration and SRS positioning Inactive configuration from DU to CU | 17.2.0 | +| 2022-09 | RP-97-e | RP-222088 | 1019 | 1 | F | Correction of the maximum PTW length of IDLE eDRX | 17.2.0 | +| 2022-09 | RP-97-e | RP-222189 | 1021 | 1 | F | Correction on Rel-17 SDT | 17.2.0 | +| 2022-09 | RP-97-e | RP-222638 | 1025 | 3 | F | Introduction of uplink GapFR2 [NR_RF_FR2_req_enh2-Core] | 17.2.0 | +| 2022-09 | RP-97-e | RP-222186 | 1027 | 2 | F | Correction to positioning gap configuration | 17.2.0 | +| 2022-09 | RP-97-e | RP-222191 | 1031 | - | F | Correction to Report Characteristics | 17.2.0 | +| 2022-09 | RP-97-e | RP-222186 | 1034 | - | F | Correction on Measurement Time Occasion | 17.2.0 | +| 2022-09 | RP-97-e | RP-222191 | 1035 | 1 | F | Correction on NR-U MLB | 17.2.0 | +| 2022-12 | RP-98-e | RP-222883 | 0975 | 4 | A | R17CR for DAPS over F1 to TS38.473 | 17.3.0 | +| 2022-12 | RP-98-e | RP-222884 | 1012 | 1 | A | Correction of on-demand SI for connected UE | 17.3.0 | +| 2022-12 | RP-98-e | RP-222879 | 1039 | 1 | F | Further correction to Report Characteristics | 17.3.0 | +| 2022-12 | RP-98-e | RP-222882 | 1043 | 3 | F | Provision of MBS Multicast F1-U references to UE Context in gNB-CU enabling retrieval of data forwarding progress information | 17.3.0 | +| 2022-12 | RP-98-e | RP-222886 | 1046 | 2 | F | Correction of TRP TEG | 17.3.0 | +| 2022-12 | RP-98-e | RP-222884 | 1052 | 2 | A | Correction on generation of gap type over F1 in Rel-17 | 17.3.0 | +| 2022-12 | RP-98-e | RP-222886 | 1054 | 1 | F | Correction of Timing Error Margin | 17.3.0 | +| 2022-12 | RP-98-e | RP-222887 | 1057 | 1 | A | CR to 38.473 on SRS periodicity | 17.3.0 | +| 2022-12 | RP-98-e | RP-222886 | 1058 | 1 | F | Correction of ASN.1 for UL RTOA Measurement | 17.3.0 | +| 2022-12 | RP-98-e | RP-222887 | 1060 | 3 | A | Correction on positioning SI delivery over F1AP | 17.3.0 | +| 2022-12 | RP-98-e | RP-222881 | 1061 | 1 | F | Correction on resource configuration for IAB | 17.3.0 | +| 2022-12 | RP-98-e | RP-222886 | 1072 | - | F | Correction on presence of timing error margin for TRP TEGs | 17.3.0 | +| 2022-12 | RP-98-e | RP-222883 | 1075 | 1 | A | CR for DAPS state transfer in case of split gNB deployment to Rel-17 38.473 | 17.3.0 | +| 2022-12 | RP-98-e | RP-222888 | 1076 | 1 | F | SL relay corrections | 17.3.0 | +| 2022-12 | RP-98-e | RP-222888 | 1077 | 4 | F | Correction to 38.473 for SL relay (R17) | 17.3.0 | +| 2022-12 | RP-98-e | RP-222957 | 1081 | 5 | A | Support of DC Location for two UL CCs in Split architecture | 17.3.0 | +| 2022-12 | RP-98-e | RP-222882 | 1083 | 1 | F | Correction on NR MBS over F1AP | 17.3.0 | +| 2022-12 | RP-98-e | RP-222882 | 1084 | 1 | F | Correction on MRB QoS Information | 17.3.0 | +| 2022-12 | RP-98-e | RP-222879 | 1091 | 2 | F | Correction on Resource Status Reporting procedure over F1 | 17.3.0 | +| 2022-12 | RP-98-e | RP-222885 | 1094 | 2 | F | Support of DC Location for more carriers in Split architecture (The CR is not implemented. The CR is postponed to next plenary meeting due to the fact that it is impossible to modify a paragraph via 2 separate CRs without CR clash) | 17.3.0 | +| 2022-12 | RP-98-e | RP-222886 | 1100 | 1 | F | Support of DC Location for more carriers in Split architecture | 17.3.0 | +| 2023-03 | RAN#99 | RP-230591 | 1029 | 4 | B | Introduction of two PHR mode [NR_feMIMO-Core] | 17.4.0 | +| 2023-03 | RAN#99 | RP-230582 | 1090 | 4 | F | Correction to conditional MCG configuration in CPAC | 17.4.0 | +| 2023-03 | RAN#99 | RP-230589 | 1093 | 4 | F | Correction to support NCD-SSB RedCap requirements in F1AP | 17.4.0 | +| 2023-03 | RAN#99 | RP-230593 | 1094 | 3 | F | Correction for supporting DC Location for more carriers in Split architecture | 17.4.0 | +| 2023-03 | RAN#99 | RP-230585 | 1097 | 2 | F | Correction of NR PRACH Configuration List for FR2-2 | 17.4.0 | +| 2023-03 | RAN#99 | RP-230581 | 1113 | 1 | F | Correction on missing cause value for CG-SDT | 17.4.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-03 | RAN#99 | RP-230589 | 1114 | 2 | F | Correction on the UE identity index for paging RedCap UE to TS38.473 | 17.4.0 | +| 2023-03 | RAN#99 | RP-230596 | 1116 | - | A | Correction on IAB UP configuration update | 17.4.0 | +| 2023-03 | RAN#99 | RP-230583 | 1117 | 1 | F | Correction on NR MBS Broadcast aspects | 17.4.0 | +| 2023-03 | RAN#99 | RP-230587 | 1118 | 1 | F | Correction of gNB Rx-Tx Time Difference | 17.4.0 | +| 2023-03 | RAN#99 | RP-230590 | 1120 | 1 | F | Correction of RRC references for SLrelay | 17.4.0 | +| 2023-03 | RAN#99 | RP-230593 | 1121 | - | F | Correction of RRC references for DRX | 17.4.0 | +| 2023-03 | RAN#99 | RP-230593 | 1122 | - | F | Correction of RRC references | 17.4.0 | +| 2023-03 | RAN#99 | RP-230591 | 1124 | 2 | B | Missing transmission bandwidth configurations in F1AP | 17.4.0 | +| 2023-03 | RAN#99 | RP-230583 | 1125 | 1 | F | Correction of F1 Broadcast Setup | 17.4.0 | +| 2023-03 | RAN#99 | RP-230588 | 1126 | - | F | PRS configuration procedure correction | 17.4.0 | +| 2023-03 | RAN#99 | RP-230581 | 1127 | 1 | F | Correction to CellGroupConfig handling for SDT | 17.4.0 | +| 2023-03 | RAN#99 | RP-230584 | 1131 | 2 | F | Correction on NR-U Channel ID | 17.4.0 | +| 2023-03 | RAN#99 | RP-230595 | 1137 | 2 | A | ASN.1 Correction of M6 Configuration | 17.4.0 | +| 2023-03 | RAN#99 | RP-230586 | 1138 | 1 | F | Correction to TS 38.473 on Re-routing Enable Indicator | 17.4.0 | +| 2023-04 | RAN#99 | - | - | - | - | Editorial Changes(font, style, line break) | 17.4.1 | +| 2023-06 | RAN#100 | RP-231073 | 1119 | 2 | F | Correction of Burst Arrival Time semantics description | 17.5.0 | +| 2023-06 | RAN#100 | RP-231075 | 1135 | 3 | A | Correction of SIType List | 17.5.0 | +| 2023-06 | RAN#100 | RP-231075 | 1144 | 2 | A | Corrections on TNL association addition, update and removal (F1AP) | 17.5.0 | +| 2023-06 | RAN#100 | RP-231072 | 1145 | 2 | F | Correction to TS 38.473 on RB Set Configuration | 17.5.0 | +| 2023-06 | RAN#100 | RP-231079 | 1146 | 2 | F | Introduction of the UE hashed ID to 38.473 | 17.5.0 | +| 2023-06 | RAN#100 | RP-231074 | 1147 | 2 | F | Correction on Broadcast Partial Success | 17.5.0 | +| 2023-06 | RAN#100 | RP-231081 | 1150 | 3 | A | ASN.1 Correction of PRACH Configuration | 17.5.0 | +| 2023-06 | RAN#100 | RP-231071 | 1158 | 2 | F | F1AP Rel-17 correction for NR-U metrics | 17.5.0 | +| 2023-06 | RAN#100 | RP-231080 | 1159 | 2 | F | Correction on F1AP for L2 U2N Relay | 17.5.0 | +| 2023-06 | RAN#100 | RP-231084 | 1162 | 2 | F | Correction of Extended Packet Delay Budget | 17.5.0 | +| 2023-06 | RAN#100 | RP-231075 | 1165 | 2 | A | Correction on E-UTRA - NR Cell Resource Coordination | 17.5.0 | +| 2023-06 | RAN#100 | RP-231074 | 1166 | 2 | F | Transfer of MBSInterestIndication from CU to DU | 17.5.0 | +| 2023-06 | RAN#100 | RP-231074 | 1170 | 1 | F | Correction of MRB Setup | 17.5.0 | +| 2023-06 | RAN#100 | RP-231079 | 1172 | 0 | F | Correction of RedCap-specific initial DL BWP without CD-SSB for SDT | 17.5.0 | +| 2023-06 | RAN#100 | RP-231077 | 1177 | 1 | F | SRS Resource correction on Comb 8, Number of Symbols and Repetition Factor | 17.5.0 | +| 2023-06 | RAN#100 | RP-231077 | 1179 | 1 | F | Subcarrier Spacing correction | 17.5.0 | +| 2023-09 | RAN#101 | RP-231896 | 1175 | 3 | A | Correction on IAB bar configuration | 17.6.0 | +| 2023-09 | RAN#101 | RP-231897 | 1191 | 1 | F | Correction of Distribution procedure | 17.6.0 | +| 2023-09 | RAN#101 | RP-231901 | 1193 | 1 | F | Mapping of SRB1 for the remote UE | 17.6.0 | +| 2023-09 | RAN#101 | RP-231899 | 1197 | - | A | Correction to TS 38.473 on inter-node message for CU-DU split scenario | 17.6.0 | +| 2023-09 | RAN#101 | RP-231896 | 1203 | - | A | Configuration of BH information for DRBs support CA based duplication | 17.6.0 | +| 2023-09 | RAN#101 | RP-231897 | 1205 | 1 | F | Correction on condition of successful MBS Broadcast Context Setup | 17.6.0 | +| 2023-09 | RAN#101 | RP-231900 | 1206 | 1 | F | PRS CONFIGURATION REQUEST Correction | 17.6.0 | +| 2023-09 | RAN#101 | RP-231900 | 1211 | - | A | Correction of Positioning SIType List | 17.6.0 | +| 2023-09 | RAN#101 | RP-231898 | 1215 | 1 | F | Rel-17 Correction in the UE Context Modification procedure abnormal description for conditional mobility modification | 17.6.0 | +| 2023-12 | RAN#102 | RP-233851 | 1220 | 3 | F | Correction on SI delivery to RedCap UE | 17.7.0 | +| 2023-12 | RAN#102 | RP-233851 | 1223 | 4 | F | Support of preconfigured Measurement GAP | 17.7.0 | +| 2023-12 | RAN#102 | RP-233848 | 1230 | 1 | F | Clarification on gNB-DU Cell Resource Configuration for IAB | 17.7.0 | +| 2023-12 | RAN#102 | RP-233849 | 1233 | 1 | F | Correction of F1-U context Reference for PTM | 17.7.0 | +| 2023-12 | RAN#102 | RP-233850 | 1237 | - | F | Correction to F1AP for the misalignment on DL PRS | 17.7.0 | +| 2023-12 | RAN#102 | RP-233850 | 1246 | - | F | Correction on TRP Information Type Response Item IE of Positioning | 17.7.0 | +| 2023-12 | RAN#102 | RP-233847 | 1247 | 1 | F | Correction on NR-Mode-Info IE of SON | 17.7.0 | +| 2023-12 | RAN#102 | RP-233818 | 1037 | 13 | B | Additions for L1/L2 triggered mobility | 18.0.0 | +| 2023-12 | RAN#102 | RP-233833 | 1070 | 11 | B | Introduction of R18 QoE measurement enhancements | 18.0.0 | +| 2023-12 | RAN#102 | RP-233832 | 1105 | 11 | B | Addition of SON features enhancement | 18.0.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|--------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-12 | RAN#102 | RP-233814 | 1109 | 7 | B | Support of Network-Controlled Repeater | 18.0.0 | +| 2023-12 | RAN#102 | RP-233822 | 1123 | 10 | B | Support for NR Sidelink Relay Enhancements | 18.0.0 | +| 2023-12 | RAN#102 | RP-233817 | 1129 | 11 | B | Introduction of Network Energy Saving | 18.0.0 | +| 2023-12 | RAN#102 | RP-233819 | 1140 | 8 | B | Introduction on MT-SDT | 18.0.0 | +| 2023-12 | RAN#102 | RP-233845 | 1167 | 3 | B | Support 1-symbol PRS [1symbol_PRS] | 18.0.0 | +| 2023-12 | RAN#102 | RP-233838 | 1168 | 8 | B | Introduction of 5G Timing Resiliency and URLLC enhancements | 18.0.0 | +| 2023-12 | RAN#102 | RP-233816 | 1169 | 8 | B | Introduction on NR Redcap Enhancement | 18.0.0 | +| 2023-12 | RAN#102 | RP-233834 | 1176 | 10 | B | (CR to 38.473): Support for mobile IAB | 18.0.0 | +| 2023-12 | RAN#102 | RP-233829 | 1189 | 7 | B | Introduction of NR MBS enhancements | 18.0.0 | +| 2023-12 | RAN#102 | RP-233842 | 1194 | 2 | B | Introduction of measurements without gap with interruption | 18.0.0 | +| 2023-12 | RAN#102 | RP-233845 | 1213 | 3 | B | Switching from SDT to RRC connected state [Large SDT Uplink Data] | 18.0.0 | +| 2023-12 | RAN#102 | RP-233830 | 1219 | 5 | B | Support for NR XR | 18.0.0 | +| 2023-12 | RAN#102 | RP-233841 | 1221 | 2 | B | Introduction of 3 MHz channel bandwidth | 18.0.0 | +| 2023-12 | RAN#102 | RP-233839 | 1226 | 2 | B | RAN impact on supporting Network Slice Service continuity scenario | 18.0.0 | +| 2023-12 | RAN#102 | RP-233818 | 1227 | 2 | B | On Subsequent CPAC | 18.0.0 | +| 2023-12 | RAN#102 | RP-233845 | 1231 | 2 | B | Introduction of RedCap UE MBS Broadcast reception [RedcapMBS] | 18.0.0 | +| 2023-12 | RAN#102 | RP-233821 | 1232 | 1 | B | Introduction of early capability restriction for Multi-SIM | 18.0.0 | +| 2023-12 | RAN#102 | RP-233813 | 1248 | 1 | B | Introduction of SL CA over F1 interface | 18.0.0 | +| 2023-12 | RAN#102 | RP-233825 | 1250 | 0 | B | A2X communication services support in F1AP | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38474/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg b/marked/Rel-18/38_series/38474/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23fccb4bbc94e7e6f8fa3ce7eb46d7bd7ec30589 --- /dev/null +++ b/marked/Rel-18/38_series/38474/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ad107877180d3c68401eed08dd8dfc426490ebe80620d3c4f78f8afaa974684 +size 13577 diff --git a/marked/Rel-18/38_series/38474/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38474/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9d2513cf039cef9aac0def2bc9f0b4d23fbc565 --- /dev/null +++ b/marked/Rel-18/38_series/38474/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04960319a82a56f29457c520fa5fb586775f78656972f5ca2c99a49ab8e07e46 +size 9536 diff --git a/marked/Rel-18/38_series/38474/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38474/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51eea4073e63c16d0e8fc2ffc49d0a4b2b4a648c --- /dev/null +++ b/marked/Rel-18/38_series/38474/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddbf217f6a98fcd0371b88a55811a0464e33a9504ea298c457b4e2cc21d7ca40 +size 5758 diff --git a/marked/Rel-18/38_series/38474/raw.md b/marked/Rel-18/38_series/38474/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e411374752614aeca95f4c9276bfdd8b3f3e501d --- /dev/null +++ b/marked/Rel-18/38_series/38474/raw.md @@ -0,0 +1,196 @@ + + +# 3GPP TS 38.474 V18.0.0(2024-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 data 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 ..... | 6 | +| 4 Data Link Layer ..... | 6 | +| 5 F1 Interface user plane protocol..... | 6 | +| 5.1 General ..... | 6 | +| 5.2 GTP-U ..... | 6 | +| 5.3 UDP/IP ..... | 6 | +| 5.4 Diffserv code point marking ..... | 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 specifies the standards for user data transport protocols and related signalling protocols to establish user plane transport bearers over the F1 interface. The F1 interface provides means for interconnecting a gNB-CU and a gNB-DU of a gNB within an NG-RAN, or for interconnection a gNB-CU and a gNB-DU of an en-gNB within an E-UTRAN. + +# --- 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.281: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)". +- [3] IETF RFC 768 (1980-08): "User Datagram Protocol". +- [4] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the Ipv4 and Ipv6 Headers". +- [5] IETF RFC 8200 (2017-07): "Internet Protocol, Version 6 (Ipv6) Specification". +- [6] IETF RFC 791 (1981-09): "Internet Protocol". +- [7] 3GPP TS 38.300: "NR; Overall description; Stage-2". +- [8] 3GPP TS 38.401: "NG-RAN; Architecture Description". +- [9] 3GPP TS 37.340: "NR; Multi-connectivity; Overall description; 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]. + +**en-gNB**: as defined in TS 37.340 [9]. + +**F1**: interface between a gNB-DU and a gNB-CU, providing an interconnection point between the gNB-DU and the gNB-CU. + +**gNB-CU**: as defined in TS 38.401 [8]. + +**gNB-DU**: as defined in TS 38.401 [8]. + +**gNB**: as defined in TS 38.300 [7]. + +## 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]. + +| | | +|------|--------------------------------| +| GTP | GPRS Tunnelling Protocol | +| IAB | Integrated Access and Backhaul | +| IP | Internet Protocol | +| TEID | Tunnel Endpoint Identifier | +| UDP | User Datagram Protocol | + +# --- 4 Data Link Layer + +Any data link protocol that fulfils the requirements toward the upper layer may be used. + +# --- 5 F1 Interface user plane protocol + +## 5.1 General + +The transport layer for data streams over F1 is an IP based Transport. The following figure shows the transport protocol stacks over F1. + +![Diagram showing the transport network layer stack for data streams over F1. The stack consists of five layers: GTP-U at the top, followed by UDP, then IPv6 (RFC 2460) and/or IPv4 (RFC 791), then Data link layer, and finally Physical layer at the bottom.](43fec6623ab9cb223a9ff74e2d2a4402_img.jpg) + +| | +|---------------------------------------------| +| GTP-U | +| UDP | +| IPv6 (RFC 2460)
and/or
IPv4 (RFC 791) | +| Data link layer | +| Physical layer | + +Diagram showing the transport network layer stack for data streams over F1. The stack consists of five layers: GTP-U at the top, followed by UDP, then IPv6 (RFC 2460) and/or IPv4 (RFC 791), then Data link layer, and finally Physical layer at the bottom. + +**Figure 5.1: Transport network layer for data streams over F1** + +The GTP-U (TS 29.281 [2]) protocol over UDP over IP shall be supported as the transport for data streams on the F1 interface. The data link layer is as specified in clause 4. + +The transport bearer is identified by the GTP-U TEID (TS 29.281 [2]) and the IP address (source TEID, destination TEID, source IP address, destination IP address). + +## 5.2 GTP-U + +The GTP-U (TS 29.281 [2]) protocol shall be used over the F1 interface between gNB-DU and gNB-CU. + +## 5.3 UDP/IP + +The path protocol used shall be UDP (IETF RFC 768 [3]). + +The UDP port number for GTP-U shall be as defined in TS 29.281 [2]. + +The gNB-DU and the gNB-CU shall support fragmentation and assembly of GTP packets at the IP layer. + +The gNB-DU and the gNB-CU shall support Ipv6 (IETF RFC 8200 [5]) and/or Ipv4 (IETF RFC 791 [6]). + +There may be one or several IP addresses in the gNB-DU and in the gNB-CU. The packet processing function in the gNB-CU shall send downstream packets of a given bearer to the gNB-DU IP address (received in F1AP) associated to that particular bearer. The packet processing function in the gNB-DU shall send upstream packets of a given bearer to the gNB-CU IP address (received in F1AP) associated to that particular bearer. + +The Transport Layer Address signalled in F1AP messages is a bit string of: + +- a) 32 bits in case of Ipv4 address according to IETF RFC 791 [6]; or +- b) 128 bits in case of Ipv6 address according to IETF RFC 8200 [5]; or +- c) 160 bits if both Ipv4 and Ipv6 addresses are signalled, in which case the Ipv4 address is contained in the first 32 bits. + +## 5.4 Diffserv code point marking + +IP Differentiated Services code point marking (IETF RFC 2474 [4]) shall be supported. Except the downlink F1-U to the IAB node, the mapping between traffic categories and Diffserv code points shall be configurable by O&M based on 5G QoS Identifier (5QI) , the Priority Level (if explicitly signalled), and other NG-RAN traffic parameters (e.g. ARP). Traffic categories are implementation-specific and may be determined from the application parameters. In the IAB system, the Diffserv code points used for the downlink F1-U shall be configurable by the CU-CP based on the O&M-configured mapping between traffic categories and Diffserv code points. \ No newline at end of file diff --git a/marked/Rel-18/38_series/38761/0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg b/marked/Rel-18/38_series/38761/0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f697397ed8dd00edfa140d847df999a0601ef5f7 --- /dev/null +++ b/marked/Rel-18/38_series/38761/0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:769521eebde44bad0f36e61a7d857867108942acc475c7132326e97d156d6aad +size 50887 diff --git a/marked/Rel-18/38_series/38761/051638d871c75230edb3d005fa668810_img.jpg b/marked/Rel-18/38_series/38761/051638d871c75230edb3d005fa668810_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2a652aa67254a8a8c4f2f0bbf1692aa8bc0038f --- /dev/null +++ b/marked/Rel-18/38_series/38761/051638d871c75230edb3d005fa668810_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1b76fa1ffab60100221b7eb38dc3db5954e38495519c06a6628feebbee2fe02 +size 26334 diff --git a/marked/Rel-18/38_series/38761/0892c0cb3b8502a44c4fe4e786be912a_img.jpg b/marked/Rel-18/38_series/38761/0892c0cb3b8502a44c4fe4e786be912a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35d506ee155bfd1d5ce8c3f9245b68a85c874278 --- /dev/null +++ b/marked/Rel-18/38_series/38761/0892c0cb3b8502a44c4fe4e786be912a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bac93b173a67b6c1eba453bad5f66d03eb87fb5d53a1cc0c72905e48d36578df +size 48846 diff --git a/marked/Rel-18/38_series/38761/0a8d173734e4e46c344178e8d21bcbc3_img.jpg b/marked/Rel-18/38_series/38761/0a8d173734e4e46c344178e8d21bcbc3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..678e131d8adb0412bc7bcce3d73fb6bd3c01e239 --- /dev/null +++ b/marked/Rel-18/38_series/38761/0a8d173734e4e46c344178e8d21bcbc3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50a947cf269b94545bcae45cbe0fabcd218d096851228ee2cc5f5f2fc59e146e +size 36263 diff --git a/marked/Rel-18/38_series/38761/0cda1f4c603972dc23aefc2cc3cbd135_img.jpg b/marked/Rel-18/38_series/38761/0cda1f4c603972dc23aefc2cc3cbd135_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fa5be669c87a0796301f21f7f15007aa3eea3da --- /dev/null +++ b/marked/Rel-18/38_series/38761/0cda1f4c603972dc23aefc2cc3cbd135_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c29d98fc07c37b9405d06d7de5bca095570788de1a9cf603d8d2ed54c9f0457d +size 30819 diff --git a/marked/Rel-18/38_series/38761/0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg b/marked/Rel-18/38_series/38761/0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d365a7b5d745d54a3c99ea35399a62a5d59b4452 --- /dev/null +++ b/marked/Rel-18/38_series/38761/0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2916a92c10be46685fda79b14d6626da1eccf480972e29a062062e85264b012e +size 35797 diff --git a/marked/Rel-18/38_series/38761/0f26e70157bd4c45f825795cdcd20fbd_img.jpg b/marked/Rel-18/38_series/38761/0f26e70157bd4c45f825795cdcd20fbd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3606bfa45ac4ba1fe9b1f6049aad800fd2f4517 --- /dev/null +++ b/marked/Rel-18/38_series/38761/0f26e70157bd4c45f825795cdcd20fbd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cedc9e131bc0340782598b7227966a8862b999258d4b72603ce05985d5b3bb9 +size 29659 diff --git a/marked/Rel-18/38_series/38761/1033ab90cd19fd4c5901966aeec07a86_img.jpg b/marked/Rel-18/38_series/38761/1033ab90cd19fd4c5901966aeec07a86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6587a07104404f8603cd720f16cb0f31ef0acbd --- /dev/null +++ b/marked/Rel-18/38_series/38761/1033ab90cd19fd4c5901966aeec07a86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d7e8f6575b4e916c52bb85a3028de5027a978546df1d332c085316b2a2b29c3 +size 40294 diff --git a/marked/Rel-18/38_series/38761/1145fc59efdc7dacc8d3c715d7ff3248_img.jpg b/marked/Rel-18/38_series/38761/1145fc59efdc7dacc8d3c715d7ff3248_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8fd1a404fe6a20e459895088cf7c4525f3aa4854 --- /dev/null +++ b/marked/Rel-18/38_series/38761/1145fc59efdc7dacc8d3c715d7ff3248_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cec03d1ccf4977ea5a0d4f36d31fc910cacdae4326e296783803ff23aee6c026 +size 29118 diff --git a/marked/Rel-18/38_series/38761/1a6a826cc13d4e964b7bda69508d78e6_img.jpg b/marked/Rel-18/38_series/38761/1a6a826cc13d4e964b7bda69508d78e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b91fab1aee98a2012f6dfd0d64c3143ca35264ea --- /dev/null +++ b/marked/Rel-18/38_series/38761/1a6a826cc13d4e964b7bda69508d78e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:703132913ffce63140fb23687a1f3cb44ea85c9fb9f72c97644d2fa551a0d273 +size 26695 diff --git a/marked/Rel-18/38_series/38761/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg b/marked/Rel-18/38_series/38761/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89b5ef2ae94d6fbb5c46ef34887fe24119b15e25 --- /dev/null +++ b/marked/Rel-18/38_series/38761/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e6a7c597b61399b37e793efed2bc8dc45619dd9753189ce42b4dc8f7253b9ea +size 34935 diff --git a/marked/Rel-18/38_series/38761/1c427123350e0e73e2a109b79069314b_img.jpg b/marked/Rel-18/38_series/38761/1c427123350e0e73e2a109b79069314b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eeb54b0bc26f51863ac04795fc6072da2ac28668 --- /dev/null +++ b/marked/Rel-18/38_series/38761/1c427123350e0e73e2a109b79069314b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4488f4135b5dcb41bce039e5e35cb564ddbf1b24c52c49362863c960accdc91 +size 28919 diff --git a/marked/Rel-18/38_series/38761/20e597e389dfd8d131e05ad6e1617dcd_img.jpg b/marked/Rel-18/38_series/38761/20e597e389dfd8d131e05ad6e1617dcd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc06ac22f2e20ab96e3e8d5be00226e77974f645 --- /dev/null +++ b/marked/Rel-18/38_series/38761/20e597e389dfd8d131e05ad6e1617dcd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec16471771d9d9827c8bc4c48bd47e6bec3e2cc9307bd2c783ef6f6a66782219 +size 34478 diff --git a/marked/Rel-18/38_series/38761/237dbb78d0cad58f4dfc140988f3cd16_img.jpg b/marked/Rel-18/38_series/38761/237dbb78d0cad58f4dfc140988f3cd16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..969ed02bc1f3b419ae30cca6d1c2c3c23fd0dd7f --- /dev/null +++ b/marked/Rel-18/38_series/38761/237dbb78d0cad58f4dfc140988f3cd16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09c2cc36c7e3a4333eaada9295f88f3160b6f4233e2e44d3dd522064801644cd +size 37292 diff --git a/marked/Rel-18/38_series/38761/27b3968bf5ede712f8defd1a7ed30a7a_img.jpg b/marked/Rel-18/38_series/38761/27b3968bf5ede712f8defd1a7ed30a7a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e41ed3651e574773482cdbd03771cc5869a07709 --- /dev/null +++ b/marked/Rel-18/38_series/38761/27b3968bf5ede712f8defd1a7ed30a7a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be91aa89b115277f6756a0f1c2abaa0cdc4df4b7f83edab613d6e5e33376aa54 +size 31794 diff --git a/marked/Rel-18/38_series/38761/2f73c3f1961c12d27d0d18fe7befbf0c_img.jpg b/marked/Rel-18/38_series/38761/2f73c3f1961c12d27d0d18fe7befbf0c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..924f0316bc23b84a29037993cb5d123d947d0ba5 --- /dev/null +++ b/marked/Rel-18/38_series/38761/2f73c3f1961c12d27d0d18fe7befbf0c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5bb7cb256dc17f63ada1035002a3ca347c6fadcd14483156f36c2e143aa695f +size 25456 diff --git a/marked/Rel-18/38_series/38761/303b94716b6713757d1fdf940a6b345f_img.jpg b/marked/Rel-18/38_series/38761/303b94716b6713757d1fdf940a6b345f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a0d6f12e40d08f7ce98735de806b33488c9b0b8 --- /dev/null +++ b/marked/Rel-18/38_series/38761/303b94716b6713757d1fdf940a6b345f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ccea0e3c6add7dcbbad85ff3e4314820df2ef5471318afa0afdd29ddfbbba0b +size 52861 diff --git a/marked/Rel-18/38_series/38761/3468bcffa38de23cef94bfb460ccb301_img.jpg b/marked/Rel-18/38_series/38761/3468bcffa38de23cef94bfb460ccb301_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e39984281ed51321183bd8a0f39e0bf73ce8811 --- /dev/null +++ b/marked/Rel-18/38_series/38761/3468bcffa38de23cef94bfb460ccb301_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3408283f2ef1bc8dca2b626e6d6bf05770320a4759a2d1407f1aa17ecebade6a +size 29712 diff --git a/marked/Rel-18/38_series/38761/367ee68d9b8e16d27f4271a3c5c8ed18_img.jpg b/marked/Rel-18/38_series/38761/367ee68d9b8e16d27f4271a3c5c8ed18_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c37523c3133b1f46c44161ed98cf760dc0180504 --- /dev/null +++ b/marked/Rel-18/38_series/38761/367ee68d9b8e16d27f4271a3c5c8ed18_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49cd192941671df62ed6bb06e696cdeaf21e9e515824505a5c8afc035e6bbc2e +size 37142 diff --git a/marked/Rel-18/38_series/38761/38f59dafa78bf91b21094afd436ead19_img.jpg b/marked/Rel-18/38_series/38761/38f59dafa78bf91b21094afd436ead19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68f21f277d5873ed6aed576bb4e3bebeaf4cb3a5 --- /dev/null +++ b/marked/Rel-18/38_series/38761/38f59dafa78bf91b21094afd436ead19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60e26f32555ea9022c411003ce2a7f96a83b6f2427db25ae03c15f8bf18de0ee +size 27618 diff --git a/marked/Rel-18/38_series/38761/3a310163273edcf70c19269a06d0cdf2_img.jpg b/marked/Rel-18/38_series/38761/3a310163273edcf70c19269a06d0cdf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..505d1b011017a3c4554a6ac3ddfb02e3ea305ad8 --- /dev/null +++ b/marked/Rel-18/38_series/38761/3a310163273edcf70c19269a06d0cdf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6f0a9343098d6e140cb90363dcb5e0370734889f1f11c79ca107f4dd0287662 +size 35514 diff --git a/marked/Rel-18/38_series/38761/3d7e0eb9c7e514f3026945a039354da4_img.jpg b/marked/Rel-18/38_series/38761/3d7e0eb9c7e514f3026945a039354da4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6959f504f9e30397cbe262dd54b89ead31db16eb --- /dev/null +++ b/marked/Rel-18/38_series/38761/3d7e0eb9c7e514f3026945a039354da4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b63d442eed1b45bb936025e4c587507241a819549be3f8041f0f0e11b3536593 +size 44824 diff --git a/marked/Rel-18/38_series/38761/3e0c2bf6c51c575d096c7fc95c1e8454_img.jpg b/marked/Rel-18/38_series/38761/3e0c2bf6c51c575d096c7fc95c1e8454_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ff72d71f564e271924bb3bf90b988569b047037 --- /dev/null +++ b/marked/Rel-18/38_series/38761/3e0c2bf6c51c575d096c7fc95c1e8454_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86d3943cdc367cf1b1812fdef269dfb6b3e81421d7fc355dc93bba011c629782 +size 30121 diff --git a/marked/Rel-18/38_series/38761/42ff8b598a0818ca8b6ef30850ad5f4e_img.jpg b/marked/Rel-18/38_series/38761/42ff8b598a0818ca8b6ef30850ad5f4e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57883c63bbc5594ae1700736bfa69055c688b4dd --- /dev/null +++ b/marked/Rel-18/38_series/38761/42ff8b598a0818ca8b6ef30850ad5f4e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4705151a74151c151dfcc359d880b5dcffa669416692bcbdffac4bd8c3110299 +size 48069 diff --git a/marked/Rel-18/38_series/38761/45329c7d9aa2bd1290af5b2027f08d7e_img.jpg b/marked/Rel-18/38_series/38761/45329c7d9aa2bd1290af5b2027f08d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17bfc4fab43a4e7b93942250e9ce58041c642377 --- /dev/null +++ b/marked/Rel-18/38_series/38761/45329c7d9aa2bd1290af5b2027f08d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d41e94536f2f84ab6120cf030616852cc4e036e62f904a3a8fd02b6f5a196a75 +size 56761 diff --git a/marked/Rel-18/38_series/38761/47e75dc9e83054b2dac3df8bf3e57019_img.jpg b/marked/Rel-18/38_series/38761/47e75dc9e83054b2dac3df8bf3e57019_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b247cbdb3e2e4a7b215a38306471a5adba5ba543 --- /dev/null +++ b/marked/Rel-18/38_series/38761/47e75dc9e83054b2dac3df8bf3e57019_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef53d0487e59c391c7f389b3d7aecae3e1991bdd7c81f6587217d2396652feb6 +size 39831 diff --git a/marked/Rel-18/38_series/38761/484cfbdc05aee471306eeb11c0ee2543_img.jpg b/marked/Rel-18/38_series/38761/484cfbdc05aee471306eeb11c0ee2543_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a029bf2f751f3d2aec30da663370002d049b4a8a --- /dev/null +++ b/marked/Rel-18/38_series/38761/484cfbdc05aee471306eeb11c0ee2543_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9568b4a280a282dc8b093321679e5336e18a05c11c261bf1172afcbc9a952f46 +size 32772 diff --git a/marked/Rel-18/38_series/38761/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg b/marked/Rel-18/38_series/38761/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10864e2490a00694e5cedf186375b1ebafd8fc12 --- /dev/null +++ b/marked/Rel-18/38_series/38761/4dfe30ac5a87d018364a0ac42ea533fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21c958fc47f8ee4aaed4f68819f0de3f6ccbb6e4dde5c66f5511e67970fdaed7 +size 48935 diff --git a/marked/Rel-18/38_series/38761/50fecd0e7c9bf4ebf321d8367d42cc94_img.jpg b/marked/Rel-18/38_series/38761/50fecd0e7c9bf4ebf321d8367d42cc94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72fde258d67cd7a00550080e52678596eb62ae59 --- /dev/null +++ b/marked/Rel-18/38_series/38761/50fecd0e7c9bf4ebf321d8367d42cc94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aae4b8600409fa3183b897df9dd0a60b3ec53a55f68dcedb2efe82217a34dc0d +size 75599 diff --git a/marked/Rel-18/38_series/38761/516d9f1866cc2e359a35fb1d8c046454_img.jpg b/marked/Rel-18/38_series/38761/516d9f1866cc2e359a35fb1d8c046454_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c65cf7876edeb10bea87b03b17a0f7cb194d4e5 --- /dev/null +++ b/marked/Rel-18/38_series/38761/516d9f1866cc2e359a35fb1d8c046454_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8a134a20348d9dac0c549e1f300db839cbb1b87b261d5d452dbecb44f5f8353 +size 29170 diff --git a/marked/Rel-18/38_series/38761/52f284e10be4323639b32fdd60e463db_img.jpg b/marked/Rel-18/38_series/38761/52f284e10be4323639b32fdd60e463db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02bf957b0022892dced6e5a895328260f1344efa --- /dev/null +++ b/marked/Rel-18/38_series/38761/52f284e10be4323639b32fdd60e463db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50d4df49173c7a26f6310764609bb0807c8cc2cf5109f37b3e2a7e1a398f52cd +size 42270 diff --git a/marked/Rel-18/38_series/38761/5314dd284c2a98c866862ee0f0fee301_img.jpg b/marked/Rel-18/38_series/38761/5314dd284c2a98c866862ee0f0fee301_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb3114097ea057093b3a48de5b58d13b053e9171 --- /dev/null +++ b/marked/Rel-18/38_series/38761/5314dd284c2a98c866862ee0f0fee301_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b58cd3e13789825baa8b30ea7801c316650547f3f0947e44834351df494a234b +size 55663 diff --git a/marked/Rel-18/38_series/38761/58f42a91047786934d8a7e258d581ca2_img.jpg b/marked/Rel-18/38_series/38761/58f42a91047786934d8a7e258d581ca2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cd16d8be4cbafe147de18bf2f8feb4e3ff10343 --- /dev/null +++ b/marked/Rel-18/38_series/38761/58f42a91047786934d8a7e258d581ca2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae86d4d7d2b5a152db8056c35ae915ba381f243f5b35d9109868fd7235ea6698 +size 25496 diff --git a/marked/Rel-18/38_series/38761/5e16d3613b74558acc74ff6d7fd75fa9_img.jpg b/marked/Rel-18/38_series/38761/5e16d3613b74558acc74ff6d7fd75fa9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..abb4a1f61eaa8394cf35fac27ea422e3202066a0 --- /dev/null +++ b/marked/Rel-18/38_series/38761/5e16d3613b74558acc74ff6d7fd75fa9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99255c30f62bfa6d3576f23a67fbd4dd145d87879a1da363bccd08d274b2337f +size 33892 diff --git a/marked/Rel-18/38_series/38761/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38761/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49a42b1920ccb96dc10125e034b980b1044df37f --- /dev/null +++ b/marked/Rel-18/38_series/38761/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4dfded7747299d30b77f6087b7afc3e684f4cc2adb0c3d97df10e640e8df08a +size 9319 diff --git a/marked/Rel-18/38_series/38761/624d9669faa18991d525fea5f0e03269_img.jpg b/marked/Rel-18/38_series/38761/624d9669faa18991d525fea5f0e03269_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf0c35453dd73a608018478f6b871b62dcd5ff4d --- /dev/null +++ b/marked/Rel-18/38_series/38761/624d9669faa18991d525fea5f0e03269_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56d31bdfafde4185b503d6d610b1940c02d75f914dd0615690fa1a7a802fe798 +size 58023 diff --git a/marked/Rel-18/38_series/38761/62ad98a4bc47922b5cf47de04571dae8_img.jpg b/marked/Rel-18/38_series/38761/62ad98a4bc47922b5cf47de04571dae8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2cc596bad86380b0a57ff40798770d0b28146b66 --- /dev/null +++ b/marked/Rel-18/38_series/38761/62ad98a4bc47922b5cf47de04571dae8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3c84be196c9db5db40692bb8e4fc632f02016545710759e95df7b03ae8dca2e +size 27976 diff --git a/marked/Rel-18/38_series/38761/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38761/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a32e5076145d2044e9debbcc7524bf53d998c71 --- /dev/null +++ b/marked/Rel-18/38_series/38761/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a70887f5f42acfb7aee1fcb62ea09dc57e86e98f1b5c964ca044193d137cd51 +size 5645 diff --git a/marked/Rel-18/38_series/38761/67518cfe156890dac13b5e67abd10dc1_img.jpg b/marked/Rel-18/38_series/38761/67518cfe156890dac13b5e67abd10dc1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98157a5fc249a5f343549ed59cd274bcb1ae6d8c --- /dev/null +++ b/marked/Rel-18/38_series/38761/67518cfe156890dac13b5e67abd10dc1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3254d0db021e129ad391028353d2f5c0a07ba935f0608088b535289356b69efe +size 28188 diff --git a/marked/Rel-18/38_series/38761/6e5a85131eedf6b98db62877ee64506e_img.jpg b/marked/Rel-18/38_series/38761/6e5a85131eedf6b98db62877ee64506e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..343288313872df212a8b8a3897284eed51659f2f --- /dev/null +++ b/marked/Rel-18/38_series/38761/6e5a85131eedf6b98db62877ee64506e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf800e6359a5cfdaba75c6d37cba1c511768882a669625cb262e3b3ba73ea549 +size 29751 diff --git a/marked/Rel-18/38_series/38761/72d357d406618f3f884c3876fc3058ee_img.jpg b/marked/Rel-18/38_series/38761/72d357d406618f3f884c3876fc3058ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92608954989d82313d8decbda416340619c106bd --- /dev/null +++ b/marked/Rel-18/38_series/38761/72d357d406618f3f884c3876fc3058ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2a7872a7858ebd6ef9bad25442d40d923602cc73caecb8842b84f2e9ab9b172 +size 30282 diff --git a/marked/Rel-18/38_series/38761/73e5c1369b67ddccf657e54d0434cc2b_img.jpg b/marked/Rel-18/38_series/38761/73e5c1369b67ddccf657e54d0434cc2b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bfe63bc7b2f3c4fb668263103ed72aedcc0b4e4 --- /dev/null +++ b/marked/Rel-18/38_series/38761/73e5c1369b67ddccf657e54d0434cc2b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6290c2b53239c5ac89ac63e81b613be6d5522f0b612942af891746c8157a4ba7 +size 26702 diff --git a/marked/Rel-18/38_series/38761/74448f9178da618d823e5a5dadc56fb5_img.jpg b/marked/Rel-18/38_series/38761/74448f9178da618d823e5a5dadc56fb5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1685141a39dd88756c6349e128c04c70fff62067 --- /dev/null +++ b/marked/Rel-18/38_series/38761/74448f9178da618d823e5a5dadc56fb5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3074a9b2c33852257de31b1c6c4ac375232b7c9fad3185eb3eafb065ed8b39eb +size 34103 diff --git a/marked/Rel-18/38_series/38761/7f687094e6abe34a9cf491942b296d9a_img.jpg b/marked/Rel-18/38_series/38761/7f687094e6abe34a9cf491942b296d9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a04f68cb865bab257a19004a681bcd2c4232287f --- /dev/null +++ b/marked/Rel-18/38_series/38761/7f687094e6abe34a9cf491942b296d9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1da7f5154054484a6408b84f2550ac45b9045252dec9f6c4ecf3c6b5cd8399b8 +size 74572 diff --git a/marked/Rel-18/38_series/38761/809eec371620084c4b949c66d5d7bae0_img.jpg b/marked/Rel-18/38_series/38761/809eec371620084c4b949c66d5d7bae0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4bb7be0d43fddff7a4408aa827cea50a59e1357 --- /dev/null +++ b/marked/Rel-18/38_series/38761/809eec371620084c4b949c66d5d7bae0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c728ac7876f065f27b551aa3791f21c072020a7cc4b9053355292bc339dc2867 +size 29821 diff --git a/marked/Rel-18/38_series/38761/853ef5420f0432e626e83987e3f38a0b_img.jpg b/marked/Rel-18/38_series/38761/853ef5420f0432e626e83987e3f38a0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..050443b0fa6d6917d64e3620776f63e7ed50bd79 --- /dev/null +++ b/marked/Rel-18/38_series/38761/853ef5420f0432e626e83987e3f38a0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5dc8ab6ec566b2b7e8c81baa284863f09ba7a6faffa06a8b970de49c2343982 +size 39057 diff --git a/marked/Rel-18/38_series/38761/85b10db535b22e64c7d37f362705ddbf_img.jpg b/marked/Rel-18/38_series/38761/85b10db535b22e64c7d37f362705ddbf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1e866d55bd78fadb68e76cedfc7504fc9a29b65 --- /dev/null +++ b/marked/Rel-18/38_series/38761/85b10db535b22e64c7d37f362705ddbf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55ebc6a7b882aa2d6f3e0d8d2bb29b61ffb4e12d10c6860e78f786d6ef473aee +size 31712 diff --git a/marked/Rel-18/38_series/38761/86089bb74e9c313a8c62cd0cb41c3e66_img.jpg b/marked/Rel-18/38_series/38761/86089bb74e9c313a8c62cd0cb41c3e66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9b05bd3ab7cf688751c4e0fad6b132f306a5e14 --- /dev/null +++ b/marked/Rel-18/38_series/38761/86089bb74e9c313a8c62cd0cb41c3e66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09167a0116c710d2ff05e3e5bf79a0245bd97afc539b4c6ca52c0c475ce878c1 +size 29448 diff --git a/marked/Rel-18/38_series/38761/8791f79b259a7463279c1aeb14c31580_img.jpg b/marked/Rel-18/38_series/38761/8791f79b259a7463279c1aeb14c31580_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..631d8639dc54f87ca1f2ec70084f6d8cb81a08dd --- /dev/null +++ b/marked/Rel-18/38_series/38761/8791f79b259a7463279c1aeb14c31580_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a889083011d3237387e5e901fb726c93ff193444851bef50f2bf292bb78288c +size 53426 diff --git a/marked/Rel-18/38_series/38761/8a597e344d10e36bbb2f243f6c4e74c6_img.jpg b/marked/Rel-18/38_series/38761/8a597e344d10e36bbb2f243f6c4e74c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95ac52dd7d6c73b9aafc26f1a58016654d1cf00c --- /dev/null +++ b/marked/Rel-18/38_series/38761/8a597e344d10e36bbb2f243f6c4e74c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3662e80e706d408b0fde2e7d2c9dd92b6562b241e09549b912e63d2a9d0a12c +size 29656 diff --git a/marked/Rel-18/38_series/38761/8ba0063bcb9cdac03f1c4497526f1898_img.jpg b/marked/Rel-18/38_series/38761/8ba0063bcb9cdac03f1c4497526f1898_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32a67df89f239a41cfe7aff1112a85eef7fcaf57 --- /dev/null +++ b/marked/Rel-18/38_series/38761/8ba0063bcb9cdac03f1c4497526f1898_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce6e0c2ed966b48436c8888a0208d0fe717b84303273f0cc3d40f99912443904 +size 30032 diff --git a/marked/Rel-18/38_series/38761/8f7b458d3cc18ca96924473839d68ae6_img.jpg b/marked/Rel-18/38_series/38761/8f7b458d3cc18ca96924473839d68ae6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5e50a596ec45384f391b9d86b1a444e5be01673 --- /dev/null +++ b/marked/Rel-18/38_series/38761/8f7b458d3cc18ca96924473839d68ae6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c011b877e49dc16e184413a2742a3a5dff83bdcce0616d6456f9634e6847853 +size 66200 diff --git a/marked/Rel-18/38_series/38761/8fd97886a32c3ac7abb08aba9f7f231b_img.jpg b/marked/Rel-18/38_series/38761/8fd97886a32c3ac7abb08aba9f7f231b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e1ccc26b1cf69819664bf4509ebb3de5e685b60 --- /dev/null +++ b/marked/Rel-18/38_series/38761/8fd97886a32c3ac7abb08aba9f7f231b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7fdedb50ecb97ba44ae7bbd8d4d828e427f031ef4717bb00dd9905a715f461a +size 39972 diff --git a/marked/Rel-18/38_series/38761/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg b/marked/Rel-18/38_series/38761/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..686191630b347ad6641cd61e81c624bc13a6291a --- /dev/null +++ b/marked/Rel-18/38_series/38761/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd529fe3734895d849ee60d0d7bed4fd0bfb6882a70ef4a3edf0f0f9aa68a2f2 +size 28237 diff --git a/marked/Rel-18/38_series/38761/939b79420df0cf962959ccef56f3371f_img.jpg b/marked/Rel-18/38_series/38761/939b79420df0cf962959ccef56f3371f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..968da0493cda177a5886298abf67827d86cdb7f8 --- /dev/null +++ b/marked/Rel-18/38_series/38761/939b79420df0cf962959ccef56f3371f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:153c2c233ed9e2ac8ec852b7d58aa3a9666e88dabd0c97f31b81955279212c39 +size 31220 diff --git a/marked/Rel-18/38_series/38761/95720c661c3650650edc281e74706340_img.jpg b/marked/Rel-18/38_series/38761/95720c661c3650650edc281e74706340_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a626894d0123192bc916df9d228d7618a49c16ba --- /dev/null +++ b/marked/Rel-18/38_series/38761/95720c661c3650650edc281e74706340_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14a0ea9eedc5c4156b3126fbe46461e99ec7702a441e4fcfdfb8e66ca1c75170 +size 27457 diff --git a/marked/Rel-18/38_series/38761/98ee20ceb85cd84e2415b20b1eda1bcf_img.jpg b/marked/Rel-18/38_series/38761/98ee20ceb85cd84e2415b20b1eda1bcf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2ea3abe63b5ccb8bad94983eb735eee32816d08 --- /dev/null +++ b/marked/Rel-18/38_series/38761/98ee20ceb85cd84e2415b20b1eda1bcf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:855166e3e1945912667459c64ea784f298e5619a029a63b6bf566f8ddca42706 +size 52985 diff --git a/marked/Rel-18/38_series/38761/9c8070d46f1d2480a875239e792f1ef6_img.jpg b/marked/Rel-18/38_series/38761/9c8070d46f1d2480a875239e792f1ef6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e48f655b4068c0630ff9847aaefc2283089d7a41 --- /dev/null +++ b/marked/Rel-18/38_series/38761/9c8070d46f1d2480a875239e792f1ef6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1405b09be9b8deb6d1c0d3c35b02716a427b9fe7b5a7337bd05acd158ccc491 +size 32040 diff --git a/marked/Rel-18/38_series/38761/9f92854fe6ecaf47760515c891a4fccc_img.jpg b/marked/Rel-18/38_series/38761/9f92854fe6ecaf47760515c891a4fccc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..841c59746584719775f4cd20f5857e88f6a3bc93 --- /dev/null +++ b/marked/Rel-18/38_series/38761/9f92854fe6ecaf47760515c891a4fccc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:964751e8308bb453cd60278153ae11af2010dccbf90b935efd6387b4046bc357 +size 43428 diff --git a/marked/Rel-18/38_series/38761/a1545557e366b6302109d13360b199c3_img.jpg b/marked/Rel-18/38_series/38761/a1545557e366b6302109d13360b199c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..236622fab3a39ce024da7b3841b07df2a65cf0be --- /dev/null +++ b/marked/Rel-18/38_series/38761/a1545557e366b6302109d13360b199c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1dcf27b31a5cb5ac1aa979e6d52bc7dca9046c6d0ba49212e254755cb9057df1 +size 30719 diff --git a/marked/Rel-18/38_series/38761/a289b64f80c6df506c0c55d553fc4496_img.jpg b/marked/Rel-18/38_series/38761/a289b64f80c6df506c0c55d553fc4496_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4393de54383694cbe1d3e2459fd3512919d53af --- /dev/null +++ b/marked/Rel-18/38_series/38761/a289b64f80c6df506c0c55d553fc4496_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1e7af7d41dd734db1130a3c4568350c1b2bb606275ac26b6b80910e2f9f12cc +size 74375 diff --git a/marked/Rel-18/38_series/38761/a28fca9a7503d40707ef5273befe1be4_img.jpg b/marked/Rel-18/38_series/38761/a28fca9a7503d40707ef5273befe1be4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..876c6969b9953d0df80e99c17270626d4b7d77f4 --- /dev/null +++ b/marked/Rel-18/38_series/38761/a28fca9a7503d40707ef5273befe1be4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:051240b4749c3f35b599a3807f17bb145bfe50a354bb1f6e539e2358549ce5e2 +size 28452 diff --git a/marked/Rel-18/38_series/38761/a430996a9e8993deb0c6b25da234744b_img.jpg b/marked/Rel-18/38_series/38761/a430996a9e8993deb0c6b25da234744b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2f727bac9b075f8d26468fa7cc30cf706cde78f --- /dev/null +++ b/marked/Rel-18/38_series/38761/a430996a9e8993deb0c6b25da234744b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54c9804d505f582d8b8ba13d55dc71444f726340fde2fff83675ab166ac1a531 +size 32041 diff --git a/marked/Rel-18/38_series/38761/a82f2d67d7b1d9645cacd98ecc78608f_img.jpg b/marked/Rel-18/38_series/38761/a82f2d67d7b1d9645cacd98ecc78608f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a70113742966179a17d95e8ab2bff3b2ed1ddb49 --- /dev/null +++ b/marked/Rel-18/38_series/38761/a82f2d67d7b1d9645cacd98ecc78608f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69f4d876a274293f3ed2110c32acb369a57daa3642bd9cc7192d7c4fc3cd25e1 +size 50241 diff --git a/marked/Rel-18/38_series/38761/a85105fd544c64ef624aa45c72378647_img.jpg b/marked/Rel-18/38_series/38761/a85105fd544c64ef624aa45c72378647_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00bcae9490bf825252269214ca7fb86c7543392b --- /dev/null +++ b/marked/Rel-18/38_series/38761/a85105fd544c64ef624aa45c72378647_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b723c0d2d271e95d2b34abbb514fea117162b0098870ea8514e020762f21124 +size 30447 diff --git a/marked/Rel-18/38_series/38761/aa1b948a76d8a599c76b5033f5db9e2b_img.jpg b/marked/Rel-18/38_series/38761/aa1b948a76d8a599c76b5033f5db9e2b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26e8ca4bfb578846b47ce7c390db7fca20f17d7f --- /dev/null +++ b/marked/Rel-18/38_series/38761/aa1b948a76d8a599c76b5033f5db9e2b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf078cfdf6c81a63e0808fbcd1eb773bd4cbe8cc621670a55a987e96d2accd80 +size 31521 diff --git a/marked/Rel-18/38_series/38761/b2e1c48ea85ca7aef5ab959221c8ff6b_img.jpg b/marked/Rel-18/38_series/38761/b2e1c48ea85ca7aef5ab959221c8ff6b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ebb78a86c33e36d2f71cd3deb5c4c9c8ae00c47 --- /dev/null +++ b/marked/Rel-18/38_series/38761/b2e1c48ea85ca7aef5ab959221c8ff6b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41f719c05bd585552938f59e8d724497d002701343d28f2d8230c6a79575ac06 +size 29007 diff --git a/marked/Rel-18/38_series/38761/b30a71a63c0093c8f54a2a57b1f601bb_img.jpg b/marked/Rel-18/38_series/38761/b30a71a63c0093c8f54a2a57b1f601bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7709f84635043de4d7cf3cbee473d8604f216e35 --- /dev/null +++ b/marked/Rel-18/38_series/38761/b30a71a63c0093c8f54a2a57b1f601bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c402ebe5f4157e9208aef0a62d186d48c2253589ea38263f869a03655575810 +size 36051 diff --git a/marked/Rel-18/38_series/38761/b51b03092124a58634f30947c8c76ef8_img.jpg b/marked/Rel-18/38_series/38761/b51b03092124a58634f30947c8c76ef8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ce2a865de43a91b8780674249ea800c5e2ed06f --- /dev/null +++ b/marked/Rel-18/38_series/38761/b51b03092124a58634f30947c8c76ef8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:daf818d8862e70a0721755bf03145797b72257ea0399206d6232df035d996a6e +size 25186 diff --git a/marked/Rel-18/38_series/38761/b5c525e7df912952586920ac3d3e4c57_img.jpg b/marked/Rel-18/38_series/38761/b5c525e7df912952586920ac3d3e4c57_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13d796a2f7d630a46451fa3354dca1570120d820 --- /dev/null +++ b/marked/Rel-18/38_series/38761/b5c525e7df912952586920ac3d3e4c57_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c28cf267332a4126eb041256008c27c3239b981a66127a504e2ebb7ee76dc3e9 +size 28354 diff --git a/marked/Rel-18/38_series/38761/b712e7522f1bb7135730c7d1abb46d43_img.jpg b/marked/Rel-18/38_series/38761/b712e7522f1bb7135730c7d1abb46d43_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50e9db9a38273270f0e6655d7447a0783fe38427 --- /dev/null +++ b/marked/Rel-18/38_series/38761/b712e7522f1bb7135730c7d1abb46d43_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23224a952ed763397250f73fdc778579ada0222503cbf6089a3891faf1f00296 +size 29690 diff --git a/marked/Rel-18/38_series/38761/b78854f39d5fe3c45a918555e158ee58_img.jpg b/marked/Rel-18/38_series/38761/b78854f39d5fe3c45a918555e158ee58_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee887fec21197bafcf2c908e762352ca56bc7479 --- /dev/null +++ b/marked/Rel-18/38_series/38761/b78854f39d5fe3c45a918555e158ee58_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6e78e62b07b2ad709d2ecb66e910aa047554ff06407c0f557c8554baf547e67 +size 38209 diff --git a/marked/Rel-18/38_series/38761/b8261918596971c3801af23435c5ea50_img.jpg b/marked/Rel-18/38_series/38761/b8261918596971c3801af23435c5ea50_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87ee7db9e7dc8bd67bb83714b06a594725fe392d --- /dev/null +++ b/marked/Rel-18/38_series/38761/b8261918596971c3801af23435c5ea50_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbfe4de2277add196c42e071bcca09d4545f14588c8181178723cff6b6121ea0 +size 47286 diff --git a/marked/Rel-18/38_series/38761/b88b618bb8863766bd545c6bfb31f850_img.jpg b/marked/Rel-18/38_series/38761/b88b618bb8863766bd545c6bfb31f850_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d9da8140a635c25307bbc1f3630b1dbed411da2 --- /dev/null +++ b/marked/Rel-18/38_series/38761/b88b618bb8863766bd545c6bfb31f850_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cae216c98d24d998967227baa1a50bdf2cd8de28040165bce5486b6237c7e853 +size 34435 diff --git a/marked/Rel-18/38_series/38761/bac21fd48fcd7f025c723590e07d1823_img.jpg b/marked/Rel-18/38_series/38761/bac21fd48fcd7f025c723590e07d1823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e502aea1943e37ee3987a331cad821a493504ed --- /dev/null +++ b/marked/Rel-18/38_series/38761/bac21fd48fcd7f025c723590e07d1823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1db8563cd62a4b3a865fbd1441b855b049e06ccfa238a9cba0e1bca60326c89 +size 34352 diff --git a/marked/Rel-18/38_series/38761/bd4617f25d15430eb78c2d6d75a99dde_img.jpg b/marked/Rel-18/38_series/38761/bd4617f25d15430eb78c2d6d75a99dde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dfd965275bb2323b2f6858e27d1b14acb5f42f7a --- /dev/null +++ b/marked/Rel-18/38_series/38761/bd4617f25d15430eb78c2d6d75a99dde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92472734c759752cd31394cd5ef6062f63312a4f60da81ed1d72cc7fe76213a1 +size 38994 diff --git a/marked/Rel-18/38_series/38761/c17eaf807acd5faec68da19dd16929be_img.jpg b/marked/Rel-18/38_series/38761/c17eaf807acd5faec68da19dd16929be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e7f63b7616d002ab278a1847b0a4c137382facb --- /dev/null +++ b/marked/Rel-18/38_series/38761/c17eaf807acd5faec68da19dd16929be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e427c8533e4887f7063bdc958982eaff8891a73eeee48ab63957a2120e2b4780 +size 34869 diff --git a/marked/Rel-18/38_series/38761/c19f313a256eec398179c6859dc32a5b_img.jpg b/marked/Rel-18/38_series/38761/c19f313a256eec398179c6859dc32a5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9982c3832d39cf49ae15fa75399809188df75f5 --- /dev/null +++ b/marked/Rel-18/38_series/38761/c19f313a256eec398179c6859dc32a5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16be237ba7602c94532e5b6f7191f91f0aeea7a51c74fcc296f594d04fcd8bb1 +size 28416 diff --git a/marked/Rel-18/38_series/38761/c4c8cd9c58f395c25a2a2b217ca7c2fb_img.jpg b/marked/Rel-18/38_series/38761/c4c8cd9c58f395c25a2a2b217ca7c2fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0010bbdb220fb67979008536001931a3c810071 --- /dev/null +++ b/marked/Rel-18/38_series/38761/c4c8cd9c58f395c25a2a2b217ca7c2fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08ef266243093be3de6843d8e260bde3e108215926560cc66a564082850cd5be +size 74464 diff --git a/marked/Rel-18/38_series/38761/c531b0e7e06671c980f2ed0d753d2fbc_img.jpg b/marked/Rel-18/38_series/38761/c531b0e7e06671c980f2ed0d753d2fbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3a5a0d8ef2f2f027ae1b76c7b6905da912786a8 --- /dev/null +++ b/marked/Rel-18/38_series/38761/c531b0e7e06671c980f2ed0d753d2fbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1dffbabd4386fe00c8c13b7d03bb2df97a4ce677e4e39fdc7caea28bdcc04e3 +size 29565 diff --git a/marked/Rel-18/38_series/38761/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg b/marked/Rel-18/38_series/38761/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4ccea9dd970c1c54defd96ccaac093897a7acf6 --- /dev/null +++ b/marked/Rel-18/38_series/38761/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad22d7985ed66ec491f2d1d0fcdae7a0a33cc8665f0391064e7a720aa41e11dd +size 31293 diff --git a/marked/Rel-18/38_series/38761/cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg b/marked/Rel-18/38_series/38761/cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88ba4f066fb1054b2c11dc025936e82a38470a87 --- /dev/null +++ b/marked/Rel-18/38_series/38761/cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19def868a5593ca2c11664d9ec1a2b7f83a2942bc5630b79953710f10d7b322d +size 28926 diff --git a/marked/Rel-18/38_series/38761/cd31d0e7e4b524e074808154dd279205_img.jpg b/marked/Rel-18/38_series/38761/cd31d0e7e4b524e074808154dd279205_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e935716f80d9a8ee28eb9bcacf154586efdc363 --- /dev/null +++ b/marked/Rel-18/38_series/38761/cd31d0e7e4b524e074808154dd279205_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2db868bb8a252cff47246188faf8e6905bc59e25cdcc7e53c432e182e121aef +size 44986 diff --git a/marked/Rel-18/38_series/38761/cd965c09af15211ca52d38d49be7b515_img.jpg b/marked/Rel-18/38_series/38761/cd965c09af15211ca52d38d49be7b515_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00c5de9bd24c46ba37b101f1abc86ebffd927d36 --- /dev/null +++ b/marked/Rel-18/38_series/38761/cd965c09af15211ca52d38d49be7b515_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d6778475b47a02d62b5dcf291b29cee2b0b8bea50c679da4fe8f28aa0f09e9e +size 33611 diff --git a/marked/Rel-18/38_series/38761/cfc852835f2d91bea8dc074568937e22_img.jpg b/marked/Rel-18/38_series/38761/cfc852835f2d91bea8dc074568937e22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad8a45814450064d3b77f548fe0cdc1c2e3bc3ad --- /dev/null +++ b/marked/Rel-18/38_series/38761/cfc852835f2d91bea8dc074568937e22_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c4c46a3b53c5ffcf0ceedad84335384c1208a01003bb054d12cb8d270a27eff +size 38791 diff --git a/marked/Rel-18/38_series/38761/d04ba66e3c0eccfd8fd2b0d176d3c941_img.jpg b/marked/Rel-18/38_series/38761/d04ba66e3c0eccfd8fd2b0d176d3c941_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d638b78f5a54e232965dad9476ee53304da5d969 --- /dev/null +++ b/marked/Rel-18/38_series/38761/d04ba66e3c0eccfd8fd2b0d176d3c941_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:370d7b7789d4966e74ce214b973c548ce5c94707eb806c150894c24d4f9a0dd9 +size 39184 diff --git a/marked/Rel-18/38_series/38761/d1c99a42332e5ee19f3b840281c26681_img.jpg b/marked/Rel-18/38_series/38761/d1c99a42332e5ee19f3b840281c26681_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11e93acdedf0870f7ae124d40f710149e2693490 --- /dev/null +++ b/marked/Rel-18/38_series/38761/d1c99a42332e5ee19f3b840281c26681_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20f4e2d6f9db13fbfc32085023674b576155f71ffc8f43745bbff65d28f356c0 +size 39849 diff --git a/marked/Rel-18/38_series/38761/d2adade462af578f17e01b2a65b53c12_img.jpg b/marked/Rel-18/38_series/38761/d2adade462af578f17e01b2a65b53c12_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f4a0fdd9465604a422d4df071fee1796e1f6cff --- /dev/null +++ b/marked/Rel-18/38_series/38761/d2adade462af578f17e01b2a65b53c12_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5414c0874e4a49bdb271d83e805111f19a67c8856b40ae6f4d03c5e65c37e15 +size 33494 diff --git a/marked/Rel-18/38_series/38761/d369dc114803a761d452c13ee58ed579_img.jpg b/marked/Rel-18/38_series/38761/d369dc114803a761d452c13ee58ed579_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73d0f3b2b539f5d193f7892542a78f9390859166 --- /dev/null +++ b/marked/Rel-18/38_series/38761/d369dc114803a761d452c13ee58ed579_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65ad40bd1b8a7f4184269d9a767794f8d4c62b3d8baf08e70c47bcb1d289bde5 +size 57254 diff --git a/marked/Rel-18/38_series/38761/d4852169b63bedb68b1f3c5b3b9b0cc0_img.jpg b/marked/Rel-18/38_series/38761/d4852169b63bedb68b1f3c5b3b9b0cc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72a61484b8d7f41757779b52920b1befd6085f85 --- /dev/null +++ b/marked/Rel-18/38_series/38761/d4852169b63bedb68b1f3c5b3b9b0cc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8eb75805f2f3d7eb2d73ef1db218c79d7d8d0d6c4c4097b794171a623d82557d +size 40434 diff --git a/marked/Rel-18/38_series/38761/d49bc18ad8867b97bbb9aa580449a641_img.jpg b/marked/Rel-18/38_series/38761/d49bc18ad8867b97bbb9aa580449a641_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ec455b1ebec3cd0b27be51f4e4d25926b6e2655 --- /dev/null +++ b/marked/Rel-18/38_series/38761/d49bc18ad8867b97bbb9aa580449a641_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1b4b945007a150d7743ac26f6775e0b993dfa1bcf566dc8c745670f2eb6169a +size 37350 diff --git a/marked/Rel-18/38_series/38761/d6a5f8423065d7cef55e11a0007014d9_img.jpg b/marked/Rel-18/38_series/38761/d6a5f8423065d7cef55e11a0007014d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc391450d4d449562f361e3bfa8bb498cd184f14 --- /dev/null +++ b/marked/Rel-18/38_series/38761/d6a5f8423065d7cef55e11a0007014d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0e87f1a668298b16ec649bbc265e9f876842f10e501a6267385f08ce25e818a +size 29637 diff --git a/marked/Rel-18/38_series/38761/d6ef69cf73d5a878b050b2d7599e1816_img.jpg b/marked/Rel-18/38_series/38761/d6ef69cf73d5a878b050b2d7599e1816_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c98d76815484cf4287937f0e11b1a19e14e1581 --- /dev/null +++ b/marked/Rel-18/38_series/38761/d6ef69cf73d5a878b050b2d7599e1816_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1cc637ab101628c0b29b172aba5372c83202420820d839d465ea823d9656ff0 +size 27830 diff --git a/marked/Rel-18/38_series/38761/d74e83c626faf36154df84683d6c6673_img.jpg b/marked/Rel-18/38_series/38761/d74e83c626faf36154df84683d6c6673_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebb3c0a6748e58fae38669bda925b33fb27d6967 --- /dev/null +++ b/marked/Rel-18/38_series/38761/d74e83c626faf36154df84683d6c6673_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a33ac187584f7e3fcc06416f23ea211a0c7f37952938c36a292be019b3c78cb +size 29678 diff --git a/marked/Rel-18/38_series/38761/d8d893dd559845f86c5dd46147ef98b6_img.jpg b/marked/Rel-18/38_series/38761/d8d893dd559845f86c5dd46147ef98b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22bd3461540ee147409e4ffde02fb2957edbc8ac --- /dev/null +++ b/marked/Rel-18/38_series/38761/d8d893dd559845f86c5dd46147ef98b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4cde52c6b6f2ff8ef361df710301c59c42f27623f35e6cd86ccb45ec8e5e0b4 +size 41124 diff --git a/marked/Rel-18/38_series/38761/dd330f8b8f6c16eae20c3a676b4eb804_img.jpg b/marked/Rel-18/38_series/38761/dd330f8b8f6c16eae20c3a676b4eb804_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27eceb084111d97397a27e0d4be48e039669200c --- /dev/null +++ b/marked/Rel-18/38_series/38761/dd330f8b8f6c16eae20c3a676b4eb804_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3124f53c907820191081ad001f7b87655e35c32e3a282e7b9225a5617c10d569 +size 56657 diff --git a/marked/Rel-18/38_series/38761/df7cb4ea9bd6c3f445f3e264773b125f_img.jpg b/marked/Rel-18/38_series/38761/df7cb4ea9bd6c3f445f3e264773b125f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88d7c2e177dc04af6738a1966fb203166f307249 --- /dev/null +++ b/marked/Rel-18/38_series/38761/df7cb4ea9bd6c3f445f3e264773b125f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10fb7d86bcbc27258a1fbbdcdf4260480e098f4643a6cf958ec0fd7aa391642a +size 27025 diff --git a/marked/Rel-18/38_series/38761/e046996962d6740cf050a5640e0c6b40_img.jpg b/marked/Rel-18/38_series/38761/e046996962d6740cf050a5640e0c6b40_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b288ea10852ee0f3e8bd725abb0ddce7f0169e67 --- /dev/null +++ b/marked/Rel-18/38_series/38761/e046996962d6740cf050a5640e0c6b40_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89e9bdf95701c12dd8712ea1bbf6803275851f54779f58942f8f13c82f5075c2 +size 26079 diff --git a/marked/Rel-18/38_series/38761/ebce355620876e10f907f8b71926c112_img.jpg b/marked/Rel-18/38_series/38761/ebce355620876e10f907f8b71926c112_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fb3269a5c7de226f9f5e4c384e258700649dfe0 --- /dev/null +++ b/marked/Rel-18/38_series/38761/ebce355620876e10f907f8b71926c112_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5540bcb690ed9dc8ee65f75c8161a227a441f36ac422e9f5868001a2abddb03 +size 56766 diff --git a/marked/Rel-18/38_series/38761/ebd9fdefdb8b316d7bc166aa3ed924a3_img.jpg b/marked/Rel-18/38_series/38761/ebd9fdefdb8b316d7bc166aa3ed924a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bfb3c3fb61ff2abc52388e332cf2c3069d81251 --- /dev/null +++ b/marked/Rel-18/38_series/38761/ebd9fdefdb8b316d7bc166aa3ed924a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0848c51fc1d6cee56e80ff3d50eae13077f6341c1cef32fa709f067974c86081 +size 42109 diff --git a/marked/Rel-18/38_series/38761/ef177a7090c8da3fcd9beb78e78fd68f_img.jpg b/marked/Rel-18/38_series/38761/ef177a7090c8da3fcd9beb78e78fd68f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d935decbe5f75eb4b826273a6179f3a81a6648b2 --- /dev/null +++ b/marked/Rel-18/38_series/38761/ef177a7090c8da3fcd9beb78e78fd68f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afad5e00b7813e56d4708fb994334d801138f14bd4944327a12cc9ce14de0cf7 +size 27422 diff --git a/marked/Rel-18/38_series/38761/f1c3ae01c82d4410b559fad6174a2f1a_img.jpg b/marked/Rel-18/38_series/38761/f1c3ae01c82d4410b559fad6174a2f1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc5d1e007f8c894cc12487b5137a6dbfe9a4bb63 --- /dev/null +++ b/marked/Rel-18/38_series/38761/f1c3ae01c82d4410b559fad6174a2f1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7f38438be454df6bd65ef95d28dc11bc572bc9831223ca892d09b6729a3fcdc +size 45573 diff --git a/marked/Rel-18/38_series/38761/f85bf99d372e735d228361bf4d3cf7e6_img.jpg b/marked/Rel-18/38_series/38761/f85bf99d372e735d228361bf4d3cf7e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b15a65cf83e8d7f2a9ea0be0c0005fa726fbe0f1 --- /dev/null +++ b/marked/Rel-18/38_series/38761/f85bf99d372e735d228361bf4d3cf7e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f86f3d6ac8040dbdae5067021861f27a179410b803d872d8cb302048d78871f1 +size 28289 diff --git a/marked/Rel-18/38_series/38761/fc857414626a8d94d132e12d9afe52a4_img.jpg b/marked/Rel-18/38_series/38761/fc857414626a8d94d132e12d9afe52a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df44d56058e6911bdce2cb235f9d1cf74fad52f7 --- /dev/null +++ b/marked/Rel-18/38_series/38761/fc857414626a8d94d132e12d9afe52a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9b52e016c78f494f6ce94e56e3c8cecd59301aee41de21cb09adc4dc7d749b1 +size 26114 diff --git a/marked/Rel-18/38_series/38761/fd188843e5acb8e0d76372860b5f5962_img.jpg b/marked/Rel-18/38_series/38761/fd188843e5acb8e0d76372860b5f5962_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30252a1e11862cc406674a2e1d400744ebbbfa6d --- /dev/null +++ b/marked/Rel-18/38_series/38761/fd188843e5acb8e0d76372860b5f5962_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5786721f179d5f5796a4e1aa0de70203ae398dde253430c080d2a1b4258c0b9a +size 47152 diff --git a/marked/Rel-18/38_series/38761/fdcfba1180dc160c7d539c5fb2a6c1e6_img.jpg b/marked/Rel-18/38_series/38761/fdcfba1180dc160c7d539c5fb2a6c1e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a913d459733c9d3ccba17961896b3fe28277248 --- /dev/null +++ b/marked/Rel-18/38_series/38761/fdcfba1180dc160c7d539c5fb2a6c1e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b820ff5d8b74eead1dff296d14aa75d6dc6d106fc092eab7bc8f85568077c257 +size 27943 diff --git a/marked/Rel-18/38_series/38761/ff2492be4fa814905acbad18f261b8a5_img.jpg b/marked/Rel-18/38_series/38761/ff2492be4fa814905acbad18f261b8a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1133210a9ada97c88dc38875b46d1c061effc473 --- /dev/null +++ b/marked/Rel-18/38_series/38761/ff2492be4fa814905acbad18f261b8a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a259dff7cc12949481ae6790c528d14830f1e0d3d0f75f1008a5a20cde8fc3a7 +size 29208 diff --git a/marked/Rel-18/38_series/38761/raw.md b/marked/Rel-18/38_series/38761/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3bff525d3951f09dd2ac2aa61fba96cdec7e9863 --- /dev/null +++ b/marked/Rel-18/38_series/38761/raw.md @@ -0,0 +1,1917 @@ + + +# **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Measurements of Multiple Input Multiple Output (MIMO) Over- the-Air (OTA) performance of User Equipment (UE); (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 + +## **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 of terms, symbols and abbreviations..... | 8 | +| 3.1 Terms..... | 8 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 9 | +| 4 General..... | 10 | +| 4.1 Device types..... | 10 | +| 4.2 Testing configuration ..... | 10 | +| 4.3 Testing Bands..... | 10 | +| 5 Measurement setup ..... | 10 | +| 5.1 General ..... | 10 | +| 5.2 Measurement setup for FR1 MIMO OTA..... | 10 | +| 5.3 Measurement setup for FR2 MIMO OTA..... | 10 | +| 6 Channel Model Validation ..... | 10 | +| 6.1 General ..... | 10 | +| 6.2 Verification of Channel Model implementation of FR1 ..... | 11 | +| 6.2.1 Framework..... | 11 | +| 6.2.2 Channel Model Validation Results..... | 11 | +| 6.2.2.1 Power Delay Profile (PDP)..... | 11 | +| 6.2.2.2 Doppler/Temporal correlation ..... | 17 | +| 6.2.2.3 Spatial correlation..... | 27 | +| 6.2.2.4 Cross-polarization..... | 34 | +| 6.2.2.5 Power validation ..... | 37 | +| 6.3 Verification of Channel Model implementation of FR2 ..... | 39 | +| 6.3.1 Framework..... | 39 | +| 6.3.2 Channel Model Validation Results..... | 40 | +| 6.3.2.1 Power Delay Profile (PDP)..... | 40 | +| 6.3.2.2 Doppler/Temporal correlation ..... | 42 | +| 6.3.2.3 PAS similarity percentage (PSP) ..... | 44 | +| 6.3.2.4 Cross-polarization..... | 47 | +| 6.3.2.5 Power validation ..... | 48 | +| 7 Lab alignment of FR1 MIMO OTA..... | 48 | +| 7.1 General ..... | 48 | +| 7.2 Noise impact in MPAC on MIMO performance..... | 49 | +| 7.3 Lab alignment campaign for frequency bands > 1GHz ..... | 51 | +| 7.3.1 Framework..... | 51 | +| 7.3.2 Measurement results..... | 51 | +| 7.3.3 Pass/fail limits ..... | 53 | +| 7.3.4 Conclusion..... | 53 | +| 7.4 Lab alignment campaign for frequency bands < 1GHz ..... | 53 | +| 7.4.1 Framework..... | 53 | +| 7.4.2 Measurement results..... | 54 | +| 7.4.3 Pass/fail limits ..... | 54 | +| 7.4.4 Conclusion..... | 54 | +| 8 Lab alignment of FR2 MIMO OTA..... | 54 | +| 8.1 Framework ..... | 54 | +| 8.2 Measurement results..... | 55 | +| 8.3 Pass/fail limits ..... | 55 | +| 8.4 Conclusion..... | 55 | + +# **Annex A: Change history 56** + +# 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 Technique Report for Measurements of Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) performance of User Equipment (UE). It includes analysis and measurement results of MIMO OTA in Frequency Range 1 and Frequency Range 2, such as verification of channel models, lab alignment activities, etc.. + +# --- 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 38.151: "NR; Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) performance requirements for NR UEs". +- [3] 3GPP TR 38.827: "Study on radiated metrics and test methodology for the verification of multi-antenna reception performance of NR User Equipment (UE)". +- [4] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone" +- [5] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone" +- [6] 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" +- [7] 3GPP TS 38.101-4: "NR; User Equipment (UE) radio transmission and reception; Part 4: Performance requirements" +- [8] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception" +- [9] 3GPP TS 38.508-1: "5GS; User Equipment (UE) conformance specification; Part 1: Common test environment" +- [10] 3GPP TR 38.901: "Study on channel model for frequencies from 0.5 to 100 GHz" +- [11] F. Zhang, L. Hentilä, P. Kyösti and W. Fan, "Millimeter-wave New Radio Test Zone Validation for MIMO Over-the-air Testing," in IEEE Transactions on Antennas and Propagation, doi: 10.1109/TAP.2021.3111326. + +# --- 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]. + +**FS:** UE used in a free space configuration. + +**Handheld UE:** A UE intended to be used in hand held scenario. + +**MIMO Average Spherical Coverage:** An averaged sensitivity of best 18 FR2 MIMO OTA sensitivity values within the 3D sphere with constant-density points for PC3 device. + +**Primary mechanical mode:** The mode that is most often used for a specific user scenario. Every terminal has at least one primary mechanical mode, if multiple modes are supported, different primary mechanical modes may be applicable for different user scenarios, e.g., different primary mechanical modes for Free Space and Hand phantom usage for the same UE. + +**PSP (PAS Similarity Percentage):** The similarity of the PAS produced by the OTA system and the reference PAS, which is presented by the Total Variation Distance (TVD) of power angular spectrum (PAS). PSP is defined as $(1 - \text{TVD}) * 100\%$ . PSP=100% denotes full similarity and PSP=0% denotes full dissimilarity.. + +## 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]. + +| | | +|---------|-------------------------------------------------------------------------------------------------------| +| AOA | Azimuth angle Of Arrival | +| AOD | Azimuth angle Of Departure | +| BS | Base Station | +| CDL | Clustered Delay Line | +| CW | Continuous Wave | +| DML | Data Mode Landscape | +| DMP | Data Mode Portrait | +| DMSU | Data Mode Screen Up | +| DUT | Device Under Test | +| EUT | Equipment Under Test | +| FR1 | Frequency Range 1 | +| FR2 | Frequency Range 2 | +| FS | Free Space | +| MASC | MIMO Average Spherical Coverage | +| MIMO | Multiple Input Multiple Output | +| MPAC | Multi-Probe Anechoic Chamber | +| NR | New Radio | +| NSA | Non-Standalone, a mode of operation where operation of an other radio is assisted with an other radio | +| OTA | Over The Air | +| PAS | Power Angular Spectrum | +| PDP | Power Delay Profile | +| PSP | PAS Similarity Percentage | +| RS-EPRE | Reference Signal-Energy Per Resource Element | +| SS | System Simulator | +| SSS | Secondary Synchronization Signal | +| TRMS | Total Radiated Multi-antenna Sensitivity | +| UE | User Equipment | +| UMa | Urban Macro | +| UMi | Urban Micro | +| XPR | Cross-Polarization Ratio | +| ZOA | Zenith angle Of Arrival | +| ZOD | Zenith angle Of Departure | +| ZSA | Zenith angle Spread of Arrival | + +ZSD + +Zenith angle Spread of Departure + +# --- 4 General + +## 4.1 Device types + +The present technical report covers the smartphone device type. + +## 4.2 Testing configuration + +The present technical report covers the free space (FS) testing configuration. + +## 4.3 Testing Bands + +The present technical report covers both FR1 and FR2 operating bands. FR1 operating bands are defined in TS 38.101-1 [4] and FR2 operating bands are defined in TS 38.101-2 [5]. NSA band combinations are defined in TS 38.101-3 [6]. E-UTRA is designed to operate in operating bands defined in TS 36.101 [8]. + +# --- 5 Measurement setup + +## 5.1 General + +The measurements in the present technical report are based on the test methodology defined in 3GPP TS 38.151 [2] and 3GPP TR 38.827 [3]. + +## 5.2 Measurement setup for FR1 MIMO OTA + +The multi-probe anechoic chamber (MPAC) test method is the reference methodology for FR NR MIMO OTA testing, the measurement setup and test procedure are defined in TS 38.151 [2]. + +## 5.3 Measurement setup for FR2 MIMO OTA + +The 3D MPAC test method is the reference methodology for FR2 NR MIMO OTA testing, the measurement setup and test procedure are defined in TS 38.151 [2]. + +# --- 6 Channel Model Validation + +## 6.1 General + +This clause describes the FR1 and FR2 MIMO OTA channel model validation measurements. The purpose of channel model validation is to ensure that the channel models are correctly implemented and hence capable of generating the propagation environment, as described by the model, within the test zone. + +## 6.2 Verification of Channel Model implementation of FR1 + +### 6.2.1 Framework + +This clause describes how to proceed Channel Model Validation for FR1 MIMO OTA with MPAC system. + +- The channel model validation measurements shall be performed according to the procedures in Annex C.3 of TS 38.151, including: + - Power Delay Profile (PDP) + - Doppler/Temporal correlation + - Spatial correlation + - Cross-polarization + - Power validation +- Channel model: FR1 UMa CDL-C and UMi CDL-C, as specified in Annex C.1 of TS 38.151 +- Test frequency: as specified in Tables C.3.1-1 and C.3.1-2 of TS 38.151 +- Pass/fail limits: as defined in Annex C.4 of TS 38.151 + +### 6.2.2 Channel Model Validation Results + +This clause presents channel model validation results from different labs with different types of equipment and setup vendors. All the validation results are included for comparison. Table 6.2.2-1 lists equipment and setup vendors of different labs. + +**Table 6.2.2-1: Equipment and setup vendors of different labs** + +| Labs | Channel Emulator | BS Emulator | System | +|-------|----------------------------------------------------------|-------------|----------| +| Lab 1 | Vendor A | Vendor I | Vendor 1 | +| Lab 2 | Vendor B (for bands n41, n78)
Vendor A (for band n28) | Vendor II | Vendor 4 | +| Lab 3 | Vendor B | Vendor II | Vendor 1 | +| Lab 4 | Vendor A | Vendor II | Vendor 3 | +| Lab 5 | Vendor A | Vendor III | Vendor 3 | +| Lab 6 | Vendor B | Vendor I | Vendor 2 | +| Lab 7 | Vendor B | Vendor I | Vendor 1 | + +#### 6.2.2.1 Power Delay Profile (PDP) + +The PDP should be validated in a Beam-Specific manner. It is assumed that the beams are mapped to the inputs of the channel emulator as follows: + +- Beam 1: Input 1 and Input 2 +- Beam 2: Input 3 and Input 4 (CDL-C UMa only) + +The PDP measurement results of UMa CDL-C for bands n41 and n78 are presented in Figures 6.2.2.1-1~5. + +![PDP plot for Band n41 Beam 1 at 2.45 GHz. The graph shows Relative Power (dB) from -40 to 0 on the y-axis and Delay (ns) from 0 to 500 on the x-axis. A blue line represents the Measured PDP, and red 'x' marks represent the Reference PDP. The measured PDP has a main peak at approximately 230 ns delay with a power of 0 dB. Other smaller peaks are visible at approximately 80 ns, 280 ns, 450 ns, and 480 ns delay.](ff2492be4fa814905acbad18f261b8a5_img.jpg) + +PDP plot for Band n41 Beam 1 at 2.45 GHz. The graph shows Relative Power (dB) from -40 to 0 on the y-axis and Delay (ns) from 0 to 500 on the x-axis. A blue line represents the Measured PDP, and red 'x' marks represent the Reference PDP. The measured PDP has a main peak at approximately 230 ns delay with a power of 0 dB. Other smaller peaks are visible at approximately 80 ns, 280 ns, 450 ns, and 480 ns delay. + +![PDP plot for Band n41 Beam 2 at 2.45 GHz. The graph shows Relative Power (dB) from -40 to 0 on the y-axis and Delay (ns) from 0 to 500 on the x-axis. A blue line represents the Measured PDP, and red 'x' marks represent the Reference PDP. The measured PDP has a main peak at approximately 80 ns delay with a power of 0 dB. Other significant peaks are at approximately 240 ns, 280 ns, 450 ns, and 480 ns delay.](86089bb74e9c313a8c62cd0cb41c3e66_img.jpg) + +PDP plot for Band n41 Beam 2 at 2.45 GHz. The graph shows Relative Power (dB) from -40 to 0 on the y-axis and Delay (ns) from 0 to 500 on the x-axis. A blue line represents the Measured PDP, and red 'x' marks represent the Reference PDP. The measured PDP has a main peak at approximately 80 ns delay with a power of 0 dB. Other significant peaks are at approximately 240 ns, 280 ns, 450 ns, and 480 ns delay. + +(a) Band n41 + +![PDP plot for Band n78 Beam 1 at 3.6 GHz. The graph shows Relative Power (dB) from -40 to 0 on the y-axis and Delay (ns) from 0 to 500 on the x-axis. A blue line represents the Measured PDP, and red 'x' marks represent the Reference PDP. The measured PDP has a main peak at approximately 230 ns delay with a power of 0 dB. Other smaller peaks are visible at approximately 80 ns, 280 ns, 450 ns, and 480 ns delay.](b712e7522f1bb7135730c7d1abb46d43_img.jpg) + +PDP plot for Band n78 Beam 1 at 3.6 GHz. The graph shows Relative Power (dB) from -40 to 0 on the y-axis and Delay (ns) from 0 to 500 on the x-axis. A blue line represents the Measured PDP, and red 'x' marks represent the Reference PDP. The measured PDP has a main peak at approximately 230 ns delay with a power of 0 dB. Other smaller peaks are visible at approximately 80 ns, 280 ns, 450 ns, and 480 ns delay. + +![PDP plot for Band n78 Beam 2 at 3.6 GHz. The graph shows Relative Power (dB) from -40 to 0 on the y-axis and Delay (ns) from 0 to 500 on the x-axis. A blue line represents the Measured PDP, and red 'x' marks represent the Reference PDP. The measured PDP has a main peak at approximately 80 ns delay with a power of 0 dB. Other significant peaks are at approximately 240 ns, 280 ns, 450 ns, and 480 ns delay.](72d357d406618f3f884c3876fc3058ee_img.jpg) + +PDP plot for Band n78 Beam 2 at 3.6 GHz. The graph shows Relative Power (dB) from -40 to 0 on the y-axis and Delay (ns) from 0 to 500 on the x-axis. A blue line represents the Measured PDP, and red 'x' marks represent the Reference PDP. The measured PDP has a main peak at approximately 80 ns delay with a power of 0 dB. Other significant peaks are at approximately 240 ns, 280 ns, 450 ns, and 480 ns delay. + +(b) Band n78 + +Figure 6.2.2.1-1: Lab 1: PDP measurement results for CDL-C UMa, (a) Band n41, beam 1 and beam 2; (b) Band n78, beam 1 and beam 2. CE bandwidth: 100MHz + +![PDP plot for Band n41 Beam 1 at 2.45 GHz. The graph shows Mag[dB] from -40 to 0 on the y-axis and Time[ns] from 0 to 500 on the x-axis. A blue line represents the measured PDP, and red 'x' marks represent the reference PDP. The measured PDP has a main peak at approximately 230 ns time with a power of 0 dB. Other smaller peaks are visible at approximately 80 ns, 280 ns, 450 ns, and 480 ns time.](2f73c3f1961c12d27d0d18fe7befbf0c_img.jpg) + +PDP plot for Band n41 Beam 1 at 2.45 GHz. The graph shows Mag[dB] from -40 to 0 on the y-axis and Time[ns] from 0 to 500 on the x-axis. A blue line represents the measured PDP, and red 'x' marks represent the reference PDP. The measured PDP has a main peak at approximately 230 ns time with a power of 0 dB. Other smaller peaks are visible at approximately 80 ns, 280 ns, 450 ns, and 480 ns time. + +![PDP plot for Band n41 Beam 2 at 2.45 GHz. The graph shows Mag[dB] from -40 to 0 on the y-axis and Time[ns] from 0 to 500 on the x-axis. A blue line represents the measured PDP, and red 'x' marks represent the reference PDP. The measured PDP has a main peak at approximately 80 ns time with a power of 0 dB. Other significant peaks are at approximately 240 ns, 280 ns, 450 ns, and 480 ns time.](b51b03092124a58634f30947c8c76ef8_img.jpg) + +PDP plot for Band n41 Beam 2 at 2.45 GHz. The graph shows Mag[dB] from -40 to 0 on the y-axis and Time[ns] from 0 to 500 on the x-axis. A blue line represents the measured PDP, and red 'x' marks represent the reference PDP. The measured PDP has a main peak at approximately 80 ns time with a power of 0 dB. Other significant peaks are at approximately 240 ns, 280 ns, 450 ns, and 480 ns time. + +(a) Band n41 + +![Two line graphs showing Power Delay Profile (PDP) for CDL-C UMa 3.6GHz. The left graph is for Beam 1 and the right is for Beam 2. Both plots show Mag[dB] on the y-axis (from -40 to 0) versus Time[ns] on the x-axis (from 0 to 500). Each plot compares 'reference' (red asterisks) and 'measured' (blue line) data. In Beam 1, the main peak is at approximately 230 ns. In Beam 2, the main peak is at approximately 80 ns, with several smaller peaks at other delays.](42ff8b598a0818ca8b6ef30850ad5f4e_img.jpg) + +Two line graphs showing Power Delay Profile (PDP) for CDL-C UMa 3.6GHz. The left graph is for Beam 1 and the right is for Beam 2. Both plots show Mag[dB] on the y-axis (from -40 to 0) versus Time[ns] on the x-axis (from 0 to 500). Each plot compares 'reference' (red asterisks) and 'measured' (blue line) data. In Beam 1, the main peak is at approximately 230 ns. In Beam 2, the main peak is at approximately 80 ns, with several smaller peaks at other delays. + +(b) Band n78 + +Figure 6.2.2.1-2: Lab 2: PDP measurement results for CDL-C UMa, (a) Band n41, beam 1 and beam 2; (b) Band n78, beam 1 and beam 2 + +![Two line graphs showing Power Delay Profile (PDP) for 2.45GHz. The left graph is for Beam 1 and the right is for Beam 2. Both plots show Mag[dB] on the y-axis (from -40 to 5) versus Delay[ns] on the x-axis (from 0 to 500). Each plot compares 'Reference' (red circles) and 'Measured' (blue line) data. In Beam 1, the main peak is at approximately 230 ns. In Beam 2, the main peak is at approximately 80 ns.](dd330f8b8f6c16eae20c3a676b4eb804_img.jpg) + +Two line graphs showing Power Delay Profile (PDP) for 2.45GHz. The left graph is for Beam 1 and the right is for Beam 2. Both plots show Mag[dB] on the y-axis (from -40 to 5) versus Delay[ns] on the x-axis (from 0 to 500). Each plot compares 'Reference' (red circles) and 'Measured' (blue line) data. In Beam 1, the main peak is at approximately 230 ns. In Beam 2, the main peak is at approximately 80 ns. + +(a) Band n41 + +![Two line graphs showing Power Delay Profile (PDP) for 3.6GHz. The left graph is for Beam 1 and the right is for Beam 2. Both plots show Mag[dB] on the y-axis (from -40 to 5) versus Delay[ns] on the x-axis (from 0 to 500). Each plot compares 'Reference' (red circles) and 'Measured' (blue line) data. In Beam 1, the main peak is at approximately 230 ns. In Beam 2, the main peak is at approximately 80 ns.](624d9669faa18991d525fea5f0e03269_img.jpg) + +Two line graphs showing Power Delay Profile (PDP) for 3.6GHz. The left graph is for Beam 1 and the right is for Beam 2. Both plots show Mag[dB] on the y-axis (from -40 to 5) versus Delay[ns] on the x-axis (from 0 to 500). Each plot compares 'Reference' (red circles) and 'Measured' (blue line) data. In Beam 1, the main peak is at approximately 230 ns. In Beam 2, the main peak is at approximately 80 ns. + +(b) Band n78 + +Figure 6.2.2.1-3: Lab 3: PDP measurement results for CDL-C UMa, (a) Band n41, beam 1 and beam 2; (b) Band n78, beam 1 and beam 2. CE bandwidth: 40MHz + +![Two line graphs showing Power Delay Profile (PDP) for 2.45GHz. The left graph is '2.45GHz Beam1 PDP' and the right graph is '2.45GHz Beam2 PDP'. Both plots show Mag[dB] on the y-axis (0 to -40) versus Time[ns] on the x-axis (0 to 1000). A blue line represents 'measured' data and red asterisks represent 'reference' data. In Beam 1, the main peak is at approximately 250 ns. In Beam 2, the main peak is at approximately 100 ns, with several smaller peaks at other times.](98ee20ceb85cd84e2415b20b1eda1bcf_img.jpg) + +Two line graphs showing Power Delay Profile (PDP) for 2.45GHz. The left graph is '2.45GHz Beam1 PDP' and the right graph is '2.45GHz Beam2 PDP'. Both plots show Mag[dB] on the y-axis (0 to -40) versus Time[ns] on the x-axis (0 to 1000). A blue line represents 'measured' data and red asterisks represent 'reference' data. In Beam 1, the main peak is at approximately 250 ns. In Beam 2, the main peak is at approximately 100 ns, with several smaller peaks at other times. + +(a) Band n41 + +![Two line graphs showing Power Delay Profile (PDP) for 3.6GHz. The left graph is '3.6GHz Beam1 PDP' and the right graph is '3.6GHz Beam2 PDP'. Both plots show Mag[dB] on the y-axis (0 to -40) versus Time[ns] on the x-axis (0 to 1000). A blue line represents 'measured' data and red asterisks represent 'reference' data. In Beam 1, the main peak is at approximately 250 ns. In Beam 2, the main peak is at approximately 100 ns, with several smaller peaks at other times.](8791f79b259a7463279c1aeb14c31580_img.jpg) + +Two line graphs showing Power Delay Profile (PDP) for 3.6GHz. The left graph is '3.6GHz Beam1 PDP' and the right graph is '3.6GHz Beam2 PDP'. Both plots show Mag[dB] on the y-axis (0 to -40) versus Time[ns] on the x-axis (0 to 1000). A blue line represents 'measured' data and red asterisks represent 'reference' data. In Beam 1, the main peak is at approximately 250 ns. In Beam 2, the main peak is at approximately 100 ns, with several smaller peaks at other times. + +(b) Band n78 + +Figure 6.2.2.1-4: Lab 4: PDP measurement results for CDL-C UMa, (a) Band n41, beam 1 and beam 2; (b) Band n78, beam 1 and beam 2. + +![Two line graphs showing PDP for CDL-C UMa at fc=2450MHz. The left graph is 'PDP, CDL-C UMa beam 1, fc=2450MHz' and the right graph is 'PDP, CDL-C UMa beam 2, fc=2450MHz'. Both plots show Mag[dB] on the y-axis (0 to -40) versus Time[ns] on the x-axis (0 to 500). A blue line represents 'Measured' data and orange crosses represent 'Reference' data. In Beam 1, the main peak is at approximately 250 ns. In Beam 2, the main peak is at approximately 100 ns, with several smaller peaks at other times.](303b94716b6713757d1fdf940a6b345f_img.jpg) + +Two line graphs showing PDP for CDL-C UMa at fc=2450MHz. The left graph is 'PDP, CDL-C UMa beam 1, fc=2450MHz' and the right graph is 'PDP, CDL-C UMa beam 2, fc=2450MHz'. Both plots show Mag[dB] on the y-axis (0 to -40) versus Time[ns] on the x-axis (0 to 500). A blue line represents 'Measured' data and orange crosses represent 'Reference' data. In Beam 1, the main peak is at approximately 250 ns. In Beam 2, the main peak is at approximately 100 ns, with several smaller peaks at other times. + +a. Band 41 + +![Two line graphs showing PDP for CDL-C UMa beam 1 and beam 2 at fc=3600MHz. The left graph is for beam 1 and the right is for beam 2. Both show 'Measured' (blue line) and 'Reference' (orange crosses) data points. The x-axis is Time (us) from 0 to 500, and the y-axis is Power Level (dB) from -40 to 0. Beam 1 has a main peak around 250 us, while beam 2 has multiple peaks, with the highest around 100 us.](0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg) + +Two line graphs showing PDP for CDL-C UMa beam 1 and beam 2 at fc=3600MHz. The left graph is for beam 1 and the right is for beam 2. Both show 'Measured' (blue line) and 'Reference' (orange crosses) data points. The x-axis is Time (us) from 0 to 500, and the y-axis is Power Level (dB) from -40 to 0. Beam 1 has a main peak around 250 us, while beam 2 has multiple peaks, with the highest around 100 us. + +b. Band n78 + +Figure 6.2.2.1-5: Lab 5: PDP measurement results for CDL-C UMa, (a) Band n41, beam 1 and beam 2; (c) Band n78, beam 1 and beam 2. + +![Two line graphs for Band n41 at 2450MHz. The left graph is for Beam 1 (Input1+Input2) and the right is for Beam 2 (Input3+Input4). Both show 'Measured' (black line), 'Original Model' (red stars), and 'Agreed Reference' (green circles) data. The x-axis is Time (us) from 0 to 500, and the y-axis is Power Level (dB) from -40 to 5. Both beams show a primary peak around 250 us.](fd188843e5acb8e0d76372860b5f5962_img.jpg) + +Two line graphs for Band n41 at 2450MHz. The left graph is for Beam 1 (Input1+Input2) and the right is for Beam 2 (Input3+Input4). Both show 'Measured' (black line), 'Original Model' (red stars), and 'Agreed Reference' (green circles) data. The x-axis is Time (us) from 0 to 500, and the y-axis is Power Level (dB) from -40 to 5. Both beams show a primary peak around 250 us. + +(a) Band n41 + +![Two line graphs for Band n78 at 3600MHz. The left graph is for Beam 1 (Input1+Input2) and the right is for Beam 2 (Input3+Input4). Both show 'Measured' (black line), 'Original Model' (red stars), and 'Agreed Reference' (green circles) data. The x-axis is Time (us) from 0 to 500, and the y-axis is Power Level (dB) from -40 to 5. Both beams show a primary peak around 250 us.](b8261918596971c3801af23435c5ea50_img.jpg) + +Two line graphs for Band n78 at 3600MHz. The left graph is for Beam 1 (Input1+Input2) and the right is for Beam 2 (Input3+Input4). Both show 'Measured' (black line), 'Original Model' (red stars), and 'Agreed Reference' (green circles) data. The x-axis is Time (us) from 0 to 500, and the y-axis is Power Level (dB) from -40 to 5. Both beams show a primary peak around 250 us. + +(b) Band n78 + +Figure 6.2.2.1-6: Lab 6: PDP measurement results for CDL-C UMa, (a) Band n41, beam 1 and beam 2; (b) Band n78, beam 1 and beam 2. + +The PDP measurement results of UMi CDL-C for band n28 are presented in Figures 6.2.2.1-7~12. + +![PDP, UMi CDL-C, FR1, Beam 1, X2V, fc=722 MHz plot showing Relative power [dB] vs Delay [ns].](0a8d173734e4e46c344178e8d21bcbc3_img.jpg) + +This line graph shows the Power Delay Profile (PDP) for UMi CDL-C, FR1, Beam 1, X2V at a carrier frequency of 722 MHz. The y-axis represents Relative power [dB] from -40 to 0, and the x-axis represents Delay [ns] from 0 to 160. A blue line represents the 'Measured' data, showing a primary peak at approximately 65 ns with a power of 0 dB. A red asterisk marks the 'Reference' data point at this peak. Other smaller peaks are visible at approximately 20 ns (-20 dB) and 130 ns (-32 dB), both marked with red asterisks. + +PDP, UMi CDL-C, FR1, Beam 1, X2V, fc=722 MHz plot showing Relative power [dB] vs Delay [ns]. + +Figure 6.2.2.1-7: Lab 1: PDP measurement results for CDL-C UMi at Band n28, beam 1 + +![CDL-C UMi 722MHz Beam1 PDP plot showing Mag[dB] vs Time[ns].](1145fc59efdc7dacc8d3c715d7ff3248_img.jpg) + +This line graph shows the PDP for CDL-C UMi at 722 MHz for Beam 1. The y-axis represents Mag[dB] from -40 to 0, and the x-axis represents Time[ns] from 0 to 150. A blue line represents the 'measured' data, with a main peak at approximately 65 ns reaching 0 dB. Red asterisks mark the 'theory' data points at approximately 20 ns (-20 dB), 65 ns (0 dB), and 130 ns (-32 dB). + +CDL-C UMi 722MHz Beam1 PDP plot showing Mag[dB] vs Time[ns]. + +Figure 6.2.2.1-8: Lab 2: PDP measurement results for CDL-C UMi at Band n28, beam 1 + +![N28 722MHz PDP plot showing Delay/ns vs PDP/dB.](cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg) + +This line graph shows the PDP for N28 at 722 MHz. The y-axis represents Delay/ns from -80 to 0, and the x-axis represents PDP/dB from 0 to 1040. A blue line shows the profile, with a sharp peak at approximately 80 ns reaching 0 ns delay. Several smaller peaks are visible at lower power levels, with the highest of these reaching approximately -40 ns delay at around 440 dB PDP. + +N28 722MHz PDP plot showing Delay/ns vs PDP/dB. + +Figure 6.2.2.1-9: Lab 4: PDP measurement results for CDL-C UMi at Band n28, beam 1 + +![Figure 6.2.2.1-10: PDP measurement results for CDL-C UMi beam 1, fc=722MHz. The graph shows Power Level (dB) on the y-axis (from -45 to 0) versus Time (us) on the x-axis (from 0 to 140). A blue line represents 'Measured' data, and red 'x' marks represent 'Reference' data. The measured data shows a peak around 65 us at approximately -2 dB, while the reference data points are at approximately -30 dB at 0 us, -20 dB at 20 us, -2 dB at 65 us, and -30 dB at 130 us.](cbc4516eb885829fe8c9dabc0946dcbe_img.jpg) + +Figure 6.2.2.1-10: PDP measurement results for CDL-C UMi beam 1, fc=722MHz. The graph shows Power Level (dB) on the y-axis (from -45 to 0) versus Time (us) on the x-axis (from 0 to 140). A blue line represents 'Measured' data, and red 'x' marks represent 'Reference' data. The measured data shows a peak around 65 us at approximately -2 dB, while the reference data points are at approximately -30 dB at 0 us, -20 dB at 20 us, -2 dB at 65 us, and -30 dB at 130 us. + +Figure 6.2.2.1-10: Lab 5: PDP measurement results for CDL-C UMi at Band n28, beam 1 + +![Figure 6.2.2.1-11: PDP measurement results for CDL-C UMi at Band n28, beam 1. The graph shows Power Level (dB) on the y-axis (from -40 to 5) versus Time (us) on the x-axis (from 0 to 500). A black line represents 'Measured' data, and green circles represent '3GPP Target' data. The measured data shows multiple peaks, with the highest peak around 65 us at approximately -2 dB. The 3GPP target data points are at approximately -30 dB at 0 us, -20 dB at 20 us, -2 dB at 65 us, and -30 dB at 130 us.](fc857414626a8d94d132e12d9afe52a4_img.jpg) + +Figure 6.2.2.1-11: PDP measurement results for CDL-C UMi at Band n28, beam 1. The graph shows Power Level (dB) on the y-axis (from -40 to 5) versus Time (us) on the x-axis (from 0 to 500). A black line represents 'Measured' data, and green circles represent '3GPP Target' data. The measured data shows multiple peaks, with the highest peak around 65 us at approximately -2 dB. The 3GPP target data points are at approximately -30 dB at 0 us, -20 dB at 20 us, -2 dB at 65 us, and -30 dB at 130 us. + +Figure 6.2.2.1-11: Lab 6: PDP measurement results for CDL-C UMi at Band n28, beam 1 + +![Figure 6.2.2.1-12: PDP measurement results for CDL-C UMi at Band n28, beam 1. The graph shows Power Level (dB) on the y-axis (from -40 to 0) versus Time (us) on the x-axis (from 0 to 150). A green line represents 'Magnitude' data, and red 'x' marks represent 'Target' data. The magnitude data shows a peak around 65 us at approximately -2 dB, while the target data points are at approximately -30 dB at 0 us, -20 dB at 20 us, -2 dB at 65 us, and -30 dB at 130 us.](a430996a9e8993deb0c6b25da234744b_img.jpg) + +Figure 6.2.2.1-12: PDP measurement results for CDL-C UMi at Band n28, beam 1. The graph shows Power Level (dB) on the y-axis (from -40 to 0) versus Time (us) on the x-axis (from 0 to 150). A green line represents 'Magnitude' data, and red 'x' marks represent 'Target' data. The magnitude data shows a peak around 65 us at approximately -2 dB, while the target data points are at approximately -30 dB at 0 us, -20 dB at 20 us, -2 dB at 65 us, and -30 dB at 130 us. + +Figure 6.2.2.1-12: Lab 7: PDP measurement results for CDL-C UMi at Band n28, beam 1 + +#### 6.2.2.2 Doppler/Temporal correlation + +The Doppler should be validated in a Beam-Specific manner. It is assumed that the beams are mapped to the inputs of the channel emulator as follows: + +- Beam 1: Input 1 and Input 2 +- Beam 2: Input 3 and Input 4 (CDL-C UMa only) + +The Doppler measurement results of UMa CDL-C for bands n41 and n78 are presented in Figures 6.2.2.2-1~6. + +![Temporal auto-correlation plot for Beam 1, H11, fc=2.45 GHz. The y-axis is 'Correlation' from 0 to 1, and the x-axis is 'Distance [λ]' from 0 to 5. Two lines are plotted: 'Measured TCF' (blue line with star markers) and 'Reference TCF' (red solid line). Both lines start at 1.0 at 0 λ and decay rapidly, reaching a local minimum around 1.5 λ, then oscillate with a peak around 3.5 λ and a trough around 4.5 λ.](fdcfba1180dc160c7d539c5fb2a6c1e6_img.jpg) + +Temporal auto-correlation plot for Beam 1, H11, fc=2.45 GHz. The y-axis is 'Correlation' from 0 to 1, and the x-axis is 'Distance [λ]' from 0 to 5. Two lines are plotted: 'Measured TCF' (blue line with star markers) and 'Reference TCF' (red solid line). Both lines start at 1.0 at 0 λ and decay rapidly, reaching a local minimum around 1.5 λ, then oscillate with a peak around 3.5 λ and a trough around 4.5 λ. + +(a-1) Beam 1, H11 + +![Temporal auto-correlation plot for Beam 2, H11, fc=2.45 GHz. The y-axis is 'Correlation' from 0 to 1, and the x-axis is 'Distance [λ]' from 0 to 5. Two lines are plotted: 'Measured TCF' (blue line with star markers) and 'Reference TCF' (red solid line). Both lines start at 1.0 at 0 λ and decay rapidly, reaching a local minimum around 1.5 λ, then oscillate with a peak around 3.5 λ and a trough around 4.5 λ.](62ad98a4bc47922b5cf47de04571dae8_img.jpg) + +Temporal auto-correlation plot for Beam 2, H11, fc=2.45 GHz. The y-axis is 'Correlation' from 0 to 1, and the x-axis is 'Distance [λ]' from 0 to 5. Two lines are plotted: 'Measured TCF' (blue line with star markers) and 'Reference TCF' (red solid line). Both lines start at 1.0 at 0 λ and decay rapidly, reaching a local minimum around 1.5 λ, then oscillate with a peak around 3.5 λ and a trough around 4.5 λ. + +(a-2) Beam 2, H11 + +![Temporal auto-correlation plot for Beam 1, H12, fc=2.45 GHz. The y-axis is 'Correlation' from 0 to 1, and the x-axis is 'Distance [λ]' from 0 to 5. Two lines are plotted: 'Measured TCF' (blue line with star markers) and 'Reference TCF' (red solid line). Both lines start at 1.0 at 0 λ and decay rapidly, reaching a local minimum around 1.5 λ, then oscillate with a peak around 3.5 λ and a trough around 4.5 λ.](67518cfe156890dac13b5e67abd10dc1_img.jpg) + +Temporal auto-correlation plot for Beam 1, H12, fc=2.45 GHz. The y-axis is 'Correlation' from 0 to 1, and the x-axis is 'Distance [λ]' from 0 to 5. Two lines are plotted: 'Measured TCF' (blue line with star markers) and 'Reference TCF' (red solid line). Both lines start at 1.0 at 0 λ and decay rapidly, reaching a local minimum around 1.5 λ, then oscillate with a peak around 3.5 λ and a trough around 4.5 λ. + +(a-3) Beam 1, H12 + +![Temporal auto-correlation plot for Beam 2, H12, fc=2.45 GHz. The y-axis is 'Correlation' from 0 to 1, and the x-axis is 'Distance [λ]' from 0 to 5. Two lines are plotted: 'Measured TCF' (blue line with star markers) and 'Reference TCF' (red solid line). Both lines start at 1.0 at 0 λ and decay rapidly, reaching a local minimum around 1.5 λ, then oscillate with a peak around 3.5 λ and a trough around 4.5 λ.](c19f313a256eec398179c6859dc32a5b_img.jpg) + +Temporal auto-correlation plot for Beam 2, H12, fc=2.45 GHz. The y-axis is 'Correlation' from 0 to 1, and the x-axis is 'Distance [λ]' from 0 to 5. Two lines are plotted: 'Measured TCF' (blue line with star markers) and 'Reference TCF' (red solid line). Both lines start at 1.0 at 0 λ and decay rapidly, reaching a local minimum around 1.5 λ, then oscillate with a peak around 3.5 λ and a trough around 4.5 λ. + +(a-4) Beam 2, H12 + +![Temporal auto-correlation plot for Beam 1, X2V, fc=2.45 GHz. The y-axis is 'Correlation' from 0 to 1, and the x-axis is 'Distance [λ]' from 0 to 5. Two lines are plotted: 'Measured TCF' (blue line with star markers) and 'Reference TCF' (red solid line). Both lines start at 1.0 at 0 λ and decay rapidly, reaching a local minimum around 1.5 λ, then oscillate with a peak around 3.5 λ and a trough around 4.5 λ.](95720c661c3650650edc281e74706340_img.jpg) + +Temporal auto-correlation plot for Beam 1, X2V, fc=2.45 GHz. The y-axis is 'Correlation' from 0 to 1, and the x-axis is 'Distance [λ]' from 0 to 5. Two lines are plotted: 'Measured TCF' (blue line with star markers) and 'Reference TCF' (red solid line). Both lines start at 1.0 at 0 λ and decay rapidly, reaching a local minimum around 1.5 λ, then oscillate with a peak around 3.5 λ and a trough around 4.5 λ. + +(a-5) Beam 1, X2V + +![Temporal auto-correlation plot for Beam 2, X2V, fc=2.45 GHz. The y-axis is 'Correlation' from 0 to 1, and the x-axis is 'Distance [λ]' from 0 to 5. Two lines are plotted: 'Measured TCF' (blue line with star markers) and 'Reference TCF' (red solid line). Both lines start at 1.0 at 0 λ and decay rapidly, reaching a local minimum around 1.5 λ, then oscillate with a peak around 3.5 λ and a trough around 4.5 λ.](38f59dafa78bf91b21094afd436ead19_img.jpg) + +Temporal auto-correlation plot for Beam 2, X2V, fc=2.45 GHz. The y-axis is 'Correlation' from 0 to 1, and the x-axis is 'Distance [λ]' from 0 to 5. Two lines are plotted: 'Measured TCF' (blue line with star markers) and 'Reference TCF' (red solid line). Both lines start at 1.0 at 0 λ and decay rapidly, reaching a local minimum around 1.5 λ, then oscillate with a peak around 3.5 λ and a trough around 4.5 λ. + +(a-6) Beam 2, X2V + +![Temporal auto-correlation plot for Beam 1, X2V at fc=2.45 GHz. The graph shows Correlation (0 to 1) vs Distance [λ] (0 to 5). Measured TCF (blue stars) and Reference TCF (red line) both start at 1.0 and decay rapidly, reaching a minimum around 0.1 at 3λ, then oscillating slightly.](1a6a826cc13d4e964b7bda69508d78e6_img.jpg) + +Temporal auto-correlation, UMa CDL-C FR1 +Beam 1, X2V, fc=2.45 GHz + +Temporal auto-correlation plot for Beam 1, X2V at fc=2.45 GHz. The graph shows Correlation (0 to 1) vs Distance [λ] (0 to 5). Measured TCF (blue stars) and Reference TCF (red line) both start at 1.0 and decay rapidly, reaching a minimum around 0.1 at 3λ, then oscillating slightly. + +(a-7) Beam 1, X2V + +![Temporal auto-correlation plot for Beam 2, X2V at fc=2.45 GHz. The graph shows Correlation (0 to 1) vs Distance [λ] (0 to 5). Measured TCF (blue stars) and Reference TCF (red line) both start at 1.0 and decay rapidly, reaching a minimum around 0.1 at 3λ, then oscillating slightly.](df7cb4ea9bd6c3f445f3e264773b125f_img.jpg) + +Temporal auto-correlation, UMa CDL-C FR1 +Beam 2, X2V, fc=2.45 GHz + +Temporal auto-correlation plot for Beam 2, X2V at fc=2.45 GHz. The graph shows Correlation (0 to 1) vs Distance [λ] (0 to 5). Measured TCF (blue stars) and Reference TCF (red line) both start at 1.0 and decay rapidly, reaching a minimum around 0.1 at 3λ, then oscillating slightly. + +(a-8) Beam 2, X2V + +(a) Band n41 + +![Temporal auto-correlation plot for Beam 1, H11 at fc=3.6 GHz. The graph shows Correlation (0 to 1) vs Distance [λ] (0 to 5). Measured TCF (blue stars) and Reference TCF (red line) both start at 1.0 and decay rapidly, reaching a minimum around 0.1 at 3λ, then oscillating slightly.](ef177a7090c8da3fcd9beb78e78fd68f_img.jpg) + +Temporal auto-correlation, UMa CDL-C FR1 +Beam 1, H11, fc=3.6 GHz + +Temporal auto-correlation plot for Beam 1, H11 at fc=3.6 GHz. The graph shows Correlation (0 to 1) vs Distance [λ] (0 to 5). Measured TCF (blue stars) and Reference TCF (red line) both start at 1.0 and decay rapidly, reaching a minimum around 0.1 at 3λ, then oscillating slightly. + +(b-1) Beam 1, H11 + +![Temporal auto-correlation plot for Beam 2, H11 at fc=3.6 GHz. The graph shows Correlation (0 to 1) vs Distance [λ] (0 to 5). Measured TCF (blue stars) and Reference TCF (red line) both start at 1.0 and decay rapidly, reaching a minimum around 0.1 at 3λ, then oscillating slightly.](a28fca9a7503d40707ef5273befe1be4_img.jpg) + +Temporal auto-correlation, UMa CDL-C FR1 +Beam 2, H11, fc=3.6 GHz + +Temporal auto-correlation plot for Beam 2, H11 at fc=3.6 GHz. The graph shows Correlation (0 to 1) vs Distance [λ] (0 to 5). Measured TCF (blue stars) and Reference TCF (red line) both start at 1.0 and decay rapidly, reaching a minimum around 0.1 at 3λ, then oscillating slightly. + +(b-2) Beam 2, H11 + +![Temporal auto-correlation plot for Beam 1, X2V at fc=3.6 GHz. The graph shows Correlation (0 to 1) vs Distance [λ] (0 to 5). Measured TCF (blue stars) and Reference TCF (red line) both start at 1.0 and decay rapidly, reaching a minimum around 0.1 at 3λ, then oscillating slightly.](b2e1c48ea85ca7aef5ab959221c8ff6b_img.jpg) + +Temporal auto-correlation, UMa CDL-C FR1 +Beam 1, X2V, fc=3.6 GHz + +Temporal auto-correlation plot for Beam 1, X2V at fc=3.6 GHz. The graph shows Correlation (0 to 1) vs Distance [λ] (0 to 5). Measured TCF (blue stars) and Reference TCF (red line) both start at 1.0 and decay rapidly, reaching a minimum around 0.1 at 3λ, then oscillating slightly. + +(b-3) Beam 1, X2V + +![Temporal auto-correlation plot for Beam 2, X2V at fc=3.6 GHz. The graph shows Correlation (0 to 1) vs Distance [λ] (0 to 5). Measured TCF (blue stars) and Reference TCF (red line) both start at 1.0 and decay rapidly, reaching a minimum around 0.1 at 3λ, then oscillating slightly.](d74e83c626faf36154df84683d6c6673_img.jpg) + +Temporal auto-correlation, UMa CDL-C FR1 +Beam 2, X2V, fc=3.6 GHz + +Temporal auto-correlation plot for Beam 2, X2V at fc=3.6 GHz. The graph shows Correlation (0 to 1) vs Distance [λ] (0 to 5). Measured TCF (blue stars) and Reference TCF (red line) both start at 1.0 and decay rapidly, reaching a minimum around 0.1 at 3λ, then oscillating slightly. + +(b-4) Beam 2, X2V + +(b) Band n78 + +Figure 6.2.2.2-1: Lab 1: Doppler measurement results for CDL-C UMa, (a) Band n41 with different beams and different polarizations; (b) Band n78 with different beams and different polarizations + +![CDL-C UMa 2.45GHz Beam1 Temporal Correlation plot showing measured and reference data for Beam 1 at 2.45GHz.](1c427123350e0e73e2a109b79069314b_img.jpg) + +CDL-C UMa 2.45GHz Beam1 Temporal Correlation + +This plot shows the temporal correlation $|\rho|$ versus distance in $\lambda$ for Beam 1 at 2.45GHz. The y-axis ranges from 0 to 1, and the x-axis ranges from 0 to 5. The 'measured' data (blue line with stars) and 'reference' data (red line) both start at $|\rho| = 1$ at 0 $\lambda$ and decay rapidly, reaching a local minimum near 0.1 around 2.5 $\lambda$ , followed by small oscillations. + +CDL-C UMa 2.45GHz Beam1 Temporal Correlation plot showing measured and reference data for Beam 1 at 2.45GHz. + +![CDL-C UMa 2.45GHz Beam2 Temporal Correlation plot showing measured and reference data for Beam 2 at 2.45GHz.](3468bcffa38de23cef94bfb460ccb301_img.jpg) + +CDL-C UMa 2.45GHz Beam2 Temporal Correlation + +This plot shows the temporal correlation $|\rho|$ versus distance in $\lambda$ for Beam 2 at 2.45GHz. The axes and data series are identical to the Beam 1 plot, showing a similar decay pattern from $|\rho| = 1$ at 0 $\lambda$ to a minimum around 2.5 $\lambda$ . + +CDL-C UMa 2.45GHz Beam2 Temporal Correlation plot showing measured and reference data for Beam 2 at 2.45GHz. + +(a) Band n41 + +![CDL-C UMa 3.6GHz Beam1 Temporal Correlation plot showing measured and reference data for Beam 1 at 3.6GHz.](3e0c2bf6c51c575d096c7fc95c1e8454_img.jpg) + +CDL-C UMa 3.6GHz Beam1 Temporal Correlation + +This plot shows the temporal correlation $|\rho|$ versus distance in $\lambda$ for Beam 1 at 3.6GHz. The axes and data series are identical to the 2.45GHz plots. A tooltip at the bottom right indicates a data point at X 5 and Y 0.048172. + +CDL-C UMa 3.6GHz Beam1 Temporal Correlation plot showing measured and reference data for Beam 1 at 3.6GHz. + +![CDL-C UMa 3.6GHz Beam2 Temporal Correlation plot showing measured and reference data for Beam 2 at 3.6GHz.](8a597e344d10e36bbb2f243f6c4e74c6_img.jpg) + +CDL-C UMa 3.6GHz Beam2 Temporal Correlation + +This plot shows the temporal correlation $|\rho|$ versus distance in $\lambda$ for Beam 2 at 3.6GHz. The axes and data series are identical to the other plots, showing a similar decay pattern. + +CDL-C UMa 3.6GHz Beam2 Temporal Correlation plot showing measured and reference data for Beam 2 at 3.6GHz. + +(b) Band n78 + +Figure 6.2.2.2-2: Lab 2: Doppler measurement results for CDL-C UMa, (a) Band n41, beam 1 and beam 2; (b) Band n78, beam 1 and beam 2 + +![2.45GHz Beam1, Temporal correlation plot showing measured and theory data.](9260ae281f6b6470331f4a0f82dbc2b1_img.jpg) + +2.45GHz Beam1, Temporal correlation + +This plot shows the temporal correlation $|\rho|$ versus distance in $\lambda$ for 2.45GHz Beam1. The y-axis ranges from 0 to 1, and the x-axis ranges from 0 to 5. The 'measured' data (blue line with stars) starts at 1.0 at 0 $\lambda$ , drops sharply to about 0.2 at 1 $\lambda$ , and then oscillates around 0.1. The 'theory' data (red line) follows the measured data closely. + +2.45GHz Beam1, Temporal correlation plot showing measured and theory data. + +![2.45GHz Beam2, Temporal correlation plot showing measured and theory data.](f85bf99d372e735d228361bf4d3cf7e6_img.jpg) + +2.45GHz Beam2, Temporal correlation + +This plot shows the temporal correlation $|\rho|$ versus distance in $\lambda$ for 2.45GHz Beam2. The y-axis ranges from 0 to 1, and the x-axis ranges from 0 to 5. The 'measured' data (blue line with stars) starts at 1.0 at 0 $\lambda$ , drops sharply to about 0.2 at 1 $\lambda$ , and then oscillates around 0.1. The 'theory' data (red line) follows the measured data closely. + +2.45GHz Beam2, Temporal correlation plot showing measured and theory data. + +![2.45GHz BeamCombined, Temporal correlation plot showing measured and theory data.](c531b0e7e06671c980f2ed0d753d2fbc_img.jpg) + +2.45GHz BeamCombined, Temporal correlation + +This plot shows the temporal correlation $|\rho|$ versus distance in $\lambda$ for 2.45GHz BeamCombined. The y-axis ranges from 0 to 1, and the x-axis ranges from 0 to 5. The 'measured' data (blue line with stars) starts at 1.0 at 0 $\lambda$ , drops sharply to about 0.2 at 0.5 $\lambda$ , has a small peak of about 0.35 at 1 $\lambda$ , and then oscillates around 0.1. The 'theory' data (red line) follows the measured data closely. + +2.45GHz BeamCombined, Temporal correlation plot showing measured and theory data. + +(a) Band n41 + +![3.6GHz Beam1, Temporal correlation plot showing measured and theory data.](d6ef69cf73d5a878b050b2d7599e1816_img.jpg) + +3.6GHz Beam1, Temporal correlation + +This plot shows the temporal correlation $|\rho|$ versus distance in $\lambda$ for 3.6GHz Beam1. The y-axis ranges from 0 to 1, and the x-axis ranges from 0 to 5. The 'measured' data (blue line with stars) starts at 1.0 at 0 $\lambda$ , drops sharply to about 0.2 at 1 $\lambda$ , and then oscillates around 0.1. The 'theory' data (red line) follows the measured data closely. + +3.6GHz Beam1, Temporal correlation plot showing measured and theory data. + +![3.6GHz Beam2, Temporal correlation plot showing measured and theory data.](58f42a91047786934d8a7e258d581ca2_img.jpg) + +3.6GHz Beam2, Temporal correlation + +This plot shows the temporal correlation $|\rho|$ versus distance in $\lambda$ for 3.6GHz Beam2. The y-axis ranges from 0 to 1, and the x-axis ranges from 0 to 5. The 'measured' data (blue line with stars) starts at 1.0 at 0 $\lambda$ , drops sharply to about 0.2 at 1 $\lambda$ , and then oscillates around 0.1. The 'theory' data (red line) follows the measured data closely. + +3.6GHz Beam2, Temporal correlation plot showing measured and theory data. + +(b) Band n78 + +![Two line graphs showing temporal correlation |ρ| vs distance in λ for 4.7GHz Beam1 and Beam2. Both graphs compare measured (blue stars) and theory (red line) data. The correlation starts at 1.0 at 0λ and decays towards 0.1 by 1.5λ, with minor oscillations thereafter.](ebce355620876e10f907f8b71926c112_img.jpg) + +Figure 6.2.2.2-3 (c) Band n79: Two line graphs showing temporal correlation $|\rho|$ versus Distance in $\lambda$ for 4.7GHz. The left graph is for Beam 1 and the right graph is for Beam 2. Both graphs show measured data (blue stars) and theoretical data (red line). The correlation starts at 1.0 at 0 $\lambda$ and decays towards 0.1 by 1.5 $\lambda$ , with minor oscillations thereafter. + +Two line graphs showing temporal correlation |ρ| vs distance in λ for 4.7GHz Beam1 and Beam2. Both graphs compare measured (blue stars) and theory (red line) data. The correlation starts at 1.0 at 0λ and decays towards 0.1 by 1.5λ, with minor oscillations thereafter. + +**(c) Band n79** + +**Figure 6.2.2.2-3: Lab 3: Doppler measurement results for CDL-C UMa, (a) Band n41, beam 1, beam 2, and combined beams; (b) Band n78, beam 1 and beam 2; (c) Band n79, beam 1 and beam 2** + +![Two line graphs for Band n41 at 2450MHz showing correlation vs wavelength for beam 1 and beam 2. Each graph includes reference, measured, upper limit, and down limit curves. The measured correlation drops from 1.0 and stabilizes around 0.1 after 1λ.](bd4617f25d15430eb78c2d6d75a99dde_img.jpg) + +Figure 6.2.2.2-4 (a) Band n41: Two line graphs showing correlation versus Wavelength for CDL-C UMa at 2450MHz. The left graph is for beam 1 and the right graph is for beam 2. Both graphs show reference curve (blue line), measured curve (red line), upper limit (green line), and down limit (purple line). The correlation starts at 1.0 at 0 $\lambda$ and decays towards 0.1 by 1.5 $\lambda$ , with minor oscillations thereafter. + +Two line graphs for Band n41 at 2450MHz showing correlation vs wavelength for beam 1 and beam 2. Each graph includes reference, measured, upper limit, and down limit curves. The measured correlation drops from 1.0 and stabilizes around 0.1 after 1λ. + +**(a) Band n41** + +![Two line graphs for Band n78 at 3600MHz showing correlation vs wavelength for beam 1 and beam 2. Each graph includes reference, measured, upper limit, and down limit curves. The measured correlation drops from 1.0 and stabilizes around 0.1 after 1λ.](47e75dc9e83054b2dac3df8bf3e57019_img.jpg) + +Figure 6.2.2.2-4 (b) Band n78: Two line graphs showing correlation versus Wavelength for CDL-C UMa at 3600MHz. The left graph is for beam 1 and the right graph is for beam 2. Both graphs show reference curve (blue line), measured curve (red line), upper limit (green line), and down limit (purple line). The correlation starts at 1.0 at 0 $\lambda$ and decays towards 0.1 by 1.5 $\lambda$ , with minor oscillations thereafter. + +Two line graphs for Band n78 at 3600MHz showing correlation vs wavelength for beam 1 and beam 2. Each graph includes reference, measured, upper limit, and down limit curves. The measured correlation drops from 1.0 and stabilizes around 0.1 after 1λ. + +**(b) Band n78** + +**Figure 6.2.2.2-4: Lab 4: Doppler measurement results for CDL-C UMa, (a) Band n41, beam 1 and beam 2; (b) Band n78, beam 1 and beam 2** + +![Line graph for Beam1 showing Measured (blue) and Reference (orange) values across 40 samples. The values start at 1.0 and generally decrease, stabilizing around 0.1 after sample 10.](7f687094e6abe34a9cf491942b296d9a_img.jpg) + +### Beam1 + +This line graph compares 'Measured' (blue line) and 'Reference' (orange line) data for Beam1. The y-axis represents a normalized value from 0 to 1.0 in increments of 0.1. The x-axis lists 40 samples, grouped into four sets of ten (00-09, 10-19, 20-29, 30-39). Both lines start at 1.0. They drop sharply until sample 10, reaching a value of approximately 0.2. From sample 10 onwards, the values fluctuate at a lower level, generally staying between 0.05 and 0.15. The two lines are very close to each other throughout the entire range. + +Line graph for Beam1 showing Measured (blue) and Reference (orange) values across 40 samples. The values start at 1.0 and generally decrease, stabilizing around 0.1 after sample 10. + +![Line graph for Beam2 showing Measured (blue) and Reference (orange) values across 40 samples. The values start at 1.0 and decrease, stabilizing around 0.1 after sample 10.](c4c8cd9c58f395c25a2a2b217ca7c2fb_img.jpg) + +### Beam2 + +This line graph compares 'Measured' (blue line) and 'Reference' (orange line) data for Beam2. The axes and data series are identical in format to the Beam1 graph. The data starts at 1.0 and shows a similar downward trend, stabilizing around 0.1 after sample 10. The 'Measured' and 'Reference' lines are nearly perfectly overlaid, showing excellent agreement between the two datasets. + +Line graph for Beam2 showing Measured (blue) and Reference (orange) values across 40 samples. The values start at 1.0 and decrease, stabilizing around 0.1 after sample 10. + +(a) Band n41 + +![Line graph titled 'Beam1' showing Measured (blue) and Reference (orange) correlation values over distance for Band n78. The y-axis ranges from 0 to 1. The x-axis shows distance in wavelengths (λ) from 0 to 5, with labels every 0.1λ up to 0.9λ, then every 0.2λ up to 1.9λ, then every 0.3λ up to 2.9λ, then every 0.4λ up to 3.9λ, and finally every 0.5λ up to 5.0λ. The correlation starts at 1.0 and drops to around 0.1 by 1.0λ, then fluctuates slightly between 0.1 and 0.2.](a289b64f80c6df506c0c55d553fc4496_img.jpg) + +Beam1 + +Measured + +Reference + +Line graph titled 'Beam1' showing Measured (blue) and Reference (orange) correlation values over distance for Band n78. The y-axis ranges from 0 to 1. The x-axis shows distance in wavelengths (λ) from 0 to 5, with labels every 0.1λ up to 0.9λ, then every 0.2λ up to 1.9λ, then every 0.3λ up to 2.9λ, then every 0.4λ up to 3.9λ, and finally every 0.5λ up to 5.0λ. The correlation starts at 1.0 and drops to around 0.1 by 1.0λ, then fluctuates slightly between 0.1 and 0.2. + +![Line graph titled 'Beam2' showing Measured (blue) and Reference (orange) correlation values over distance for Band n78. The y-axis ranges from 0.000 to 1.000. The x-axis shows distance in wavelengths (λ) from 0 to 5, with labels every 0.1λ up to 0.9λ, then every 0.2λ up to 1.9λ, then every 0.3λ up to 2.9λ, then every 0.4λ up to 3.9λ, and finally every 0.5λ up to 5.0λ. The correlation starts at 1.0 and drops to around 0.1 by 1.0λ, then fluctuates slightly between 0.1 and 0.2.](50fecd0e7c9bf4ebf321d8367d42cc94_img.jpg) + +Beam2 + +Measured + +Reference + +Line graph titled 'Beam2' showing Measured (blue) and Reference (orange) correlation values over distance for Band n78. The y-axis ranges from 0.000 to 1.000. The x-axis shows distance in wavelengths (λ) from 0 to 5, with labels every 0.1λ up to 0.9λ, then every 0.2λ up to 1.9λ, then every 0.3λ up to 2.9λ, then every 0.4λ up to 3.9λ, and finally every 0.5λ up to 5.0λ. The correlation starts at 1.0 and drops to around 0.1 by 1.0λ, then fluctuates slightly between 0.1 and 0.2. + +(b) Band n78 + +Figure 6.2.2.2-5: Lab 5: Doppler measurement results for CDL-C UMa, (a) Band n41, beam 1 and beam 2; (b) Band n78, beam 1 and beam 2 + +![Two side-by-side line graphs for Band n41. The left graph is titled 'F64 TCF 2450MHz Beam1 (Input1+Input2) 100km/h 4kHz Av' and the right graph is titled 'F64 TCF 2450MHz Beam2 (Input3+Input4) 100km/h 4kHz'. Both graphs show |Correlation| on the y-axis (0 to 1) versus Distance (λ) on the x-axis (0 to 5). The 'Measured' series is red and the 'Reference' series is blue. In both graphs, the correlation drops from 1.0 at 0λ to around 0.1 at 1.0λ, then fluctuates between 0.1 and 0.2 for the rest of the distance.](d369dc114803a761d452c13ee58ed579_img.jpg) + +F64 TCF 2450MHz Beam1 (Input1+Input2) 100km/h 4kHz Av + +Measured + +Reference + +|Correlation| + +Distance ( $\lambda$ ) + +F64 TCF 2450MHz Beam2 (Input3+Input4) 100km/h 4kHz + +Measured + +Reference + +|Correlation| + +Distance ( $\lambda$ ) + +Two side-by-side line graphs for Band n41. The left graph is titled 'F64 TCF 2450MHz Beam1 (Input1+Input2) 100km/h 4kHz Av' and the right graph is titled 'F64 TCF 2450MHz Beam2 (Input3+Input4) 100km/h 4kHz'. Both graphs show |Correlation| on the y-axis (0 to 1) versus Distance (λ) on the x-axis (0 to 5). The 'Measured' series is red and the 'Reference' series is blue. In both graphs, the correlation drops from 1.0 at 0λ to around 0.1 at 1.0λ, then fluctuates between 0.1 and 0.2 for the rest of the distance. + +(a) Band n41 + +![Two line graphs showing |Correlation| vs Distance (λ) for F64 TCF 3600MHz. The left graph is for Beam1 (Input1+Input2) and the right graph is for Beam2 (Input3+Input4). Both show Measured (red) and Reference (blue) data. In both cases, the correlation starts at 1.0 at 0λ and drops to near zero by 2λ, with minor oscillations between 2λ and 5λ.](45329c7d9aa2bd1290af5b2027f08d7e_img.jpg) + +F64 TCF 3600MHz Beam1 (Input1+Input2) 100km/h 4kHz Av + +F64 TCF 3600MHz Beam2 (Input3+Input4) 100km/h 4kHz Av + +Two line graphs showing |Correlation| vs Distance (λ) for F64 TCF 3600MHz. The left graph is for Beam1 (Input1+Input2) and the right graph is for Beam2 (Input3+Input4). Both show Measured (red) and Reference (blue) data. In both cases, the correlation starts at 1.0 at 0λ and drops to near zero by 2λ, with minor oscillations between 2λ and 5λ. + +(b) Band n78 + +Figure 6.2.2.2-6: Lab 6: Doppler measurement results for CDL-C UMa, (a) Band n41, beam 1 and beam 2; (b) Band n78, beam 1 and beam 2 + +The Doppler measurement results of UMi CDL-C for band n28 are presented in Figures 6.2.2.2-7~12. + +![Line graph titled 'Temporal correlation, UMi CDL-C, FR1 Beam 1, X2V, fc=722 MHz'. It plots Correlation vs Distance [λ] from 0.0 to 5.0. It includes Measured (red solid), Reference (blue dotted), and Limits (grey dashed) lines. The correlation starts at 1.0 and decays towards 0.1 by 5.0λ.](f1c3ae01c82d4410b559fad6174a2f1a_img.jpg) + +Temporal correlation, UMi CDL-C, FR1 +Beam 1, X2V, fc=722 MHz + +Line graph titled 'Temporal correlation, UMi CDL-C, FR1 Beam 1, X2V, fc=722 MHz'. It plots Correlation vs Distance [λ] from 0.0 to 5.0. It includes Measured (red solid), Reference (blue dotted), and Limits (grey dashed) lines. The correlation starts at 1.0 and decays towards 0.1 by 5.0λ. + +Figure 6.2.2.2-7: Lab 1: Doppler measurement results for CDL-C UMi at Band n28, beam 1 + +![Line graph titled 'CDL-C UMi 722MHz Beam1 Temporal Correlation'. It plots |ρ| vs Distance in λ from 0 to 5. It includes measured (blue line with dots) and reference (red solid line) data. The correlation starts at 1.0 and decays towards 0.1 by 5λ.](367ee68d9b8e16d27f4271a3c5c8ed18_img.jpg) + +CDL-C UMi 722MHz Beam1 Temporal Correlation + +Line graph titled 'CDL-C UMi 722MHz Beam1 Temporal Correlation'. It plots |ρ| vs Distance in λ from 0 to 5. It includes measured (blue line with dots) and reference (red solid line) data. The correlation starts at 1.0 and decays towards 0.1 by 5λ. + +Figure 6.2.2.2-8: Lab 2: Doppler measurement results for CDL-C UMi at Band n28, beam 1 + +![N28 722MHz Temporal Correlation plot showing Correlation vs Wavelength for Lower, Upper, and Measured data series.](a1545557e366b6302109d13360b199c3_img.jpg) + +This line graph, titled "N28 722MHz Temporal Correlation", plots Correlation (y-axis, 0 to 1.2) against Wavelength (x-axis, 0 to 5). Three data series are shown: "Lower" (blue line with circles), "Upper" (orange line with circles), and "Measured" (yellow line with circles). All series start at a correlation of 1.0 at wavelength 0. The "Lower" series decreases steadily to about 0.1 at wavelength 2.6, then drops sharply to 0.0 at wavelength 2.8 and remains there. The "Upper" series decreases to about 0.3 at wavelength 2.8 and then levels off. The "Measured" series decreases to about 0.2 at wavelength 2.8 and then levels off. + +N28 722MHz Temporal Correlation plot showing Correlation vs Wavelength for Lower, Upper, and Measured data series. + +Figure 6.2.2.2-9: Lab 4: Doppler measurement results for CDL-C UMi at Band n28, beam 1 + +![Temporal correlation, CDL-C UMi beam 1, fc=722MHz plot showing Measured, Reference1, Lower, and Upper data series.](d8d893dd559845f86c5dd46147ef98b6_img.jpg) + +This line graph, titled "Temporal correlation, CDL-C UMi beam 1, fc=722MHz", plots Correlation (y-axis, 0 to 1) against Wavelength (x-axis, 0 to 5). Four data series are shown: "Measured" (solid purple line), "Reference1" (solid red line), "Lower" (dashed blue line), and "Upper" (dashed light blue line). All series start at a correlation of 1.0 at wavelength 0. The "Measured" and "Reference1" series decrease to about 0.1 at wavelength 2.6, then drop sharply to 0.0 at wavelength 2.8 and remain there. The "Lower" series decreases to about 0.3 at wavelength 2.6 and then drops to 0.0 at wavelength 2.8. The "Upper" series decreases to about 0.3 at wavelength 2.6 and then drops to 0.0 at wavelength 2.8. + +Temporal correlation, CDL-C UMi beam 1, fc=722MHz plot showing Measured, Reference1, Lower, and Upper data series. + +Figure 6.2.2.2-10: Lab 5: Doppler measurement results for CDL-C UMi at Band n28, beam 1 + +![TCF Beam 1 (Input 1 + Input 2) 722 MHz plot showing |Correlation| vs Distance (λ) for Measured, Reference, upper, and lower data series.](cd31d0e7e4b524e074808154dd279205_img.jpg) + +This line graph, titled "TCF Beam 1 (Input 1 + Input 2) 722 MHz", plots |Correlation| (y-axis, 0 to 1) against Distance (λ) (x-axis, 0 to 5). Four data series are shown: "Measured" (solid red line), "Reference" (solid blue line), "upper" (solid black line), and "lower" (solid black line). All series start at a correlation of 1.0 at distance 0. The "upper" series decreases to about 0.3 at distance 2.5, then drops to 0.0 at distance 2.8 and remains there. The "lower" series decreases to about 0.3 at distance 2.5, then drops to 0.0 at distance 2.8 and remains there. The "Measured" and "Reference" series decrease to about 0.1 at distance 2.6, then drop to 0.0 at distance 2.8 and remain there. + +TCF Beam 1 (Input 1 + Input 2) 722 MHz plot showing |Correlation| vs Distance (λ) for Measured, Reference, upper, and lower data series. + +Figure 6.2.2.2-11: Lab 6: Doppler measurement results for CDL-C UMi at Band n28, beam 1 + +![Line graph titled 'Temporal correlation CDL-C UMi beam 1, Fc=722MHz'. The Y-axis represents correlation from 0 to 1. The X-axis represents normalized Doppler shift from 0.0 to 5.0. Four data series are shown: 'Measured' (solid green line), 'Lower limit' (dashed light blue line), 'Upper limit' (dashed dark blue line), and 'Target' (dashed red line). All curves start at 1.0 at X=0.0 and decay. The Measured and Target curves overlap closely, reaching a minimum near 0.05 at X=4.2 before slightly rising. The Upper limit stays above the Measured curve, leveling off at 0.3 for X > 2.6. The Lower limit drops to 0.0 at X=2.6.](c17eaf807acd5faec68da19dd16929be_img.jpg) + +Line graph titled 'Temporal correlation CDL-C UMi beam 1, Fc=722MHz'. The Y-axis represents correlation from 0 to 1. The X-axis represents normalized Doppler shift from 0.0 to 5.0. Four data series are shown: 'Measured' (solid green line), 'Lower limit' (dashed light blue line), 'Upper limit' (dashed dark blue line), and 'Target' (dashed red line). All curves start at 1.0 at X=0.0 and decay. The Measured and Target curves overlap closely, reaching a minimum near 0.05 at X=4.2 before slightly rising. The Upper limit stays above the Measured curve, leveling off at 0.3 for X > 2.6. The Lower limit drops to 0.0 at X=2.6. + +**Figure 6.2.2.2-12: Lab 7: Doppler measurement results for CDL-C UMi at Band n28, beam 1** + +#### 6.2.2.3 Spatial correlation + +The Spatial correlation should be validated in a Beam-Combined manner. It is assumed that the beams are mapped to the inputs of the channel emulator as follows: + +- Beam 1: Input 1 and Input 2 +- Beam 2: Input 3 and Input 4 (CDL-C UMa only) +- Combined beam for CDL-C UMa: Input 1 + Input 2 + Input 3 + Input 4 +- Combined beam for CDL-C UMi: Input 1 + Input 2 + +The Spatial correlation measurement results of UMa CDL-C for bands n41 and n78 are presented in Figures 6.2.2.3-1~6. + +![Spatial Correlation, UMa CDL-C FR1 BS Array 4x8, Beam 1, fc=2.45 GHz. Plot showing Measured SCF (blue line with stars) and Reference SCF (red line with circles) vs Azimuth angle [°].](6e5a85131eedf6b98db62877ee64506e_img.jpg) + +This plot shows the spatial correlation $|\rho|$ for Beam 1 at 2.45 GHz. The x-axis represents the azimuth angle from 270° to 280° in 5° increments. The y-axis represents the spatial correlation $|\rho|$ from 0 to 1. The 'Measured SCF' (blue line with star markers) and 'Reference SCF' (red line with circle markers) both start at $|\rho| \approx 1.0$ at 270°. They decrease to a minimum of $|\rho| \approx 0.1$ at 145°. They then rise to a local peak of $|\rho| \approx 0.25$ at 70°, drop to another local minimum of $|\rho| \approx 0.15$ at 45°, and finally rise to $|\rho| \approx 0.95$ at 280°. + +Spatial Correlation, UMa CDL-C FR1 BS Array 4x8, Beam 1, fc=2.45 GHz. Plot showing Measured SCF (blue line with stars) and Reference SCF (red line with circles) vs Azimuth angle [°]. + +![Spatial Correlation, UMa CDL-C FR1 BS Array 4x8, Beam 2, fc=2.45 GHz. Plot showing Measured SCF (blue line with stars) and Reference SCF (red line with circles) vs Azimuth angle [°].](939b79420df0cf962959ccef56f3371f_img.jpg) + +This plot shows the spatial correlation $|\rho|$ for Beam 2 at 2.45 GHz. The axes are the same as the first plot. Both 'Measured SCF' and 'Reference SCF' start at $|\rho| \approx 1.0$ at 270°. They decrease to a local minimum of $|\rho| \approx 0.75$ at 210°. They then rise to a local peak of $|\rho| \approx 0.85$ at 145°. They decrease to a minimum of $|\rho| \approx 0.1$ at 45° and 355°. Finally, they rise to $|\rho| \approx 0.85$ at 280°. + +Spatial Correlation, UMa CDL-C FR1 BS Array 4x8, Beam 2, fc=2.45 GHz. Plot showing Measured SCF (blue line with stars) and Reference SCF (red line with circles) vs Azimuth angle [°]. + +![Spatial Correlation, UMa CDL-C FR1 Combined beams fc=2.45 GHz. Plot showing Measured SCF (blue line with stars) and Reference SCF (red line with circles) vs Azimuth angle [°].](d6a5f8423065d7cef55e11a0007014d9_img.jpg) + +This plot shows the spatial correlation $|\rho|$ for combined beams at 2.45 GHz. The axes are the same as the first plot. Both 'Measured SCF' and 'Reference SCF' start at $|\rho| \approx 1.0$ at 270°. They decrease to a minimum of $|\rho| \approx 0.1$ at 45°. They then rise to $|\rho| \approx 0.75$ at 280°. + +Spatial Correlation, UMa CDL-C FR1 Combined beams fc=2.45 GHz. Plot showing Measured SCF (blue line with stars) and Reference SCF (red line with circles) vs Azimuth angle [°]. + +(a) Band n41 + +![Spatial Correlation, UMa CDL-C FR1 Combined beams fc=3.6 GHz. Plot showing Measured SCF (blue line with stars) and Reference SCF (red line with circles) vs Azimuth angle [°].](27b3968bf5ede712f8defd1a7ed30a7a_img.jpg) + +This plot shows the spatial correlation $|\rho|$ for combined beams at 3.6 GHz. The axes are the same as the first plot. Both 'Measured SCF' and 'Reference SCF' start at $|\rho| \approx 1.0$ at 270°. They decrease to a local minimum of $|\rho| \approx 0.2$ at 145°. They rise to a local peak of $|\rho| \approx 0.65$ at 120°. They decrease to a minimum of $|\rho| \approx 0.15$ at 45° and 355°. Finally, they rise to $|\rho| \approx 0.95$ at 280°. + +Spatial Correlation, UMa CDL-C FR1 Combined beams fc=3.6 GHz. Plot showing Measured SCF (blue line with stars) and Reference SCF (red line with circles) vs Azimuth angle [°]. + +(b) Band n78 + +Figure 6.2.2.3-1: Lab 1: Spatial correlation measurement results for CDL-C UMa, (a) Band n41, beam 1, beam 2, and combined beams; (b) Band n78, combined beams + +![Line graph titled 'CDL-C UMa 2.45GHz beamCombine Spatial Correlaiton'. The y-axis is 'Spatial Correlation |ρ|' from 0 to 1. The x-axis is 'Sensor Array Positoin' from 0 to 20. Two lines are plotted: 'measured' (blue circles) and 'reference' (red stars). The correlation starts at 1.0 at position 0 and decreases to about 0.1 at position 16, then rises to about 0.8 at position 20.](85b10db535b22e64c7d37f362705ddbf_img.jpg) + +Line graph titled 'CDL-C UMa 2.45GHz beamCombine Spatial Correlaiton'. The y-axis is 'Spatial Correlation |ρ|' from 0 to 1. The x-axis is 'Sensor Array Positoin' from 0 to 20. Two lines are plotted: 'measured' (blue circles) and 'reference' (red stars). The correlation starts at 1.0 at position 0 and decreases to about 0.1 at position 16, then rises to about 0.8 at position 20. + +(a) Band n41 + +![Line graph titled 'CDL-C UMa 3.6GHz beamCombine Spatial Correlaiton'. The y-axis is 'Spatial Correlation |ρ|' from 0 to 1. The x-axis is 'Sensor Array Positoin' from 0 to 30. Two lines are plotted: 'measured' (blue circles) and 'reference' (red stars). The correlation starts at 1.0 at position 0 and decreases to about 0.1 at position 27, then rises to about 0.9 at position 30.](484cfbdc05aee471306eeb11c0ee2543_img.jpg) + +Line graph titled 'CDL-C UMa 3.6GHz beamCombine Spatial Correlaiton'. The y-axis is 'Spatial Correlation |ρ|' from 0 to 1. The x-axis is 'Sensor Array Positoin' from 0 to 30. Two lines are plotted: 'measured' (blue circles) and 'reference' (red stars). The correlation starts at 1.0 at position 0 and decreases to about 0.1 at position 27, then rises to about 0.9 at position 30. + +(b) Band n78 + +Figure 6.2.2.3-2: Lab 2: Spatial correlation measurement results for CDL-C UMa, (a) Band n41 with combined beams; (b) Band n78 with combined beams + +![Line graph titled '2.45GHz Beam1'. The y-axis is 'Spatial Correlation' from 0 to 1. The x-axis is 'Azimuth angle[°]' from 270 to 280. Two lines are plotted: 'measured' (blue circles) and 'reference' (orange stars). The correlation starts at 1.0 at 270° and decreases to about 0.1 at 45°.](9c8070d46f1d2480a875239e792f1ef6_img.jpg) + +Line graph titled '2.45GHz Beam1'. The y-axis is 'Spatial Correlation' from 0 to 1. The x-axis is 'Azimuth angle[°]' from 270 to 280. Two lines are plotted: 'measured' (blue circles) and 'reference' (orange stars). The correlation starts at 1.0 at 270° and decreases to about 0.1 at 45°. + +![Line graph titled '2.45GHz Beam2'. The y-axis is 'Spatial Correlation' from 0 to 1. The x-axis is 'Azimuth angle[°]' from 270 to 280. Two lines are plotted: 'measured' (blue circles) and 'reference' (orange stars). The correlation starts at 1.0 at 270° and decreases to about 0.1 at 45°.](aa1b948a76d8a599c76b5033f5db9e2b_img.jpg) + +Line graph titled '2.45GHz Beam2'. The y-axis is 'Spatial Correlation' from 0 to 1. The x-axis is 'Azimuth angle[°]' from 270 to 280. Two lines are plotted: 'measured' (blue circles) and 'reference' (orange stars). The correlation starts at 1.0 at 270° and decreases to about 0.1 at 45°. + +![Line graph titled '2.45GHz, BeamCombined'. The y-axis is 'Spatial Correlation' from 0 to 1. The x-axis is 'Azimuth angle[°]' from 270 to 280. Two lines are plotted: 'measured' (blue circles) and 'reference' (orange stars). The correlation starts at 1.0 at 270° and decreases to about 0.1 at 45°.](d2adade462af578f17e01b2a65b53c12_img.jpg) + +Line graph titled '2.45GHz, BeamCombined'. The y-axis is 'Spatial Correlation' from 0 to 1. The x-axis is 'Azimuth angle[°]' from 270 to 280. Two lines are plotted: 'measured' (blue circles) and 'reference' (orange stars). The correlation starts at 1.0 at 270° and decreases to about 0.1 at 45°. + +(a) Band n41 + +![Line graph titled '3.6GHz, BeamCombined' showing Spatial Correlation vs Azimuth angle [°]. The y-axis ranges from 0 to 1. The x-axis ranges from 270 to 280 degrees. Two data series are plotted: 'measured' (blue line with circular markers) and 'reference' (orange line with circular markers). Both series start at a correlation of 1.0 at 270 degrees and generally decrease, with some fluctuations, ending near 0.4 at 280 degrees.](1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg) + +Line graph titled '3.6GHz, BeamCombined' showing Spatial Correlation vs Azimuth angle [°]. The y-axis ranges from 0 to 1. The x-axis ranges from 270 to 280 degrees. Two data series are plotted: 'measured' (blue line with circular markers) and 'reference' (orange line with circular markers). Both series start at a correlation of 1.0 at 270 degrees and generally decrease, with some fluctuations, ending near 0.4 at 280 degrees. + +(b) Band n78 + +Figure 6.2.2.3-3: Lab 3: Spatial correlation measurement results for CDL-C UMa, (a) Band n41, beam 1, beam 2, and combined beams; (b) Band n78, combined beams + +![Line graph titled 'CDLC UMA beam combine 2450Mhz' showing Correlation vs Position/degree. The y-axis ranges from 0 to 1.2. The x-axis shows positions from 270 to 294.6 degrees. Four data series are plotted: 'beam combine reference' (blue line with circular markers), 'measured curve' (red line with circular markers), 'upper limit' (green line with circular markers), and 'down limit' (purple line with circular markers). The correlation starts around 0.9, remains relatively stable until 185.9 degrees, then drops sharply to around 0.2 at 144.9 degrees, before rising back to around 0.8 at 294.6 degrees.](1033ab90cd19fd4c5901966aeec07a86_img.jpg) + +Line graph titled 'CDLC UMA beam combine 2450Mhz' showing Correlation vs Position/degree. The y-axis ranges from 0 to 1.2. The x-axis shows positions from 270 to 294.6 degrees. Four data series are plotted: 'beam combine reference' (blue line with circular markers), 'measured curve' (red line with circular markers), 'upper limit' (green line with circular markers), and 'down limit' (purple line with circular markers). The correlation starts around 0.9, remains relatively stable until 185.9 degrees, then drops sharply to around 0.2 at 144.9 degrees, before rising back to around 0.8 at 294.6 degrees. + +(a) Band n41 + +![Line graph titled 'CDLC UMA beam combine 3600Mhz' showing Correlation vs Position/degree. The y-axis ranges from 0 to 1.2. The x-axis shows positions from 270 to 277.6 degrees. Four data series are plotted: 'beam combine reference' (blue line with circular markers), 'measured curve' (red line with circular markers), 'upper limit' (green line with circular markers), and 'down limit' (purple line with circular markers). The correlation starts around 0.9, remains relatively stable until 184.1 degrees, then drops sharply to around 0.2 at 156.1 degrees, before rising back to around 0.8 at 277.6 degrees.](b78854f39d5fe3c45a918555e158ee58_img.jpg) + +Line graph titled 'CDLC UMA beam combine 3600Mhz' showing Correlation vs Position/degree. The y-axis ranges from 0 to 1.2. The x-axis shows positions from 270 to 277.6 degrees. Four data series are plotted: 'beam combine reference' (blue line with circular markers), 'measured curve' (red line with circular markers), 'upper limit' (green line with circular markers), and 'down limit' (purple line with circular markers). The correlation starts around 0.9, remains relatively stable until 184.1 degrees, then drops sharply to around 0.2 at 156.1 degrees, before rising back to around 0.8 at 277.6 degrees. + +(b) Band n78 + +Figure 6.2.2.3-4: Lab 4: Spatial correlation measurement results for CDL-C UMa, (a) Band n41, combined beams; (b) Band n78, combined beams + +![Line graph titled 'Combined Beams' for Band n41. The y-axis represents correlation from 0 to 1, and the x-axis represents beam indices from 1 to 20. Two lines are plotted: a blue 'Reference' line and an orange 'Measured' line. Both lines start at 1.0 for beam 1 and gradually decrease to approximately 0.65 at beam 13. At beam 14, there is a sharp drop to about 0.25. The correlation remains low until beam 17, then rises to about 0.75 at beam 20. The two lines are nearly perfectly overlaid.](20e597e389dfd8d131e05ad6e1617dcd_img.jpg) + +| Beam Index | Reference | Measured | +|------------|-----------|----------| +| 1 | 1.0 | 1.0 | +| 2 | 0.98 | 0.98 | +| 3 | 0.95 | 0.95 | +| 4 | 0.92 | 0.92 | +| 5 | 0.88 | 0.88 | +| 6 | 0.85 | 0.85 | +| 7 | 0.83 | 0.83 | +| 8 | 0.81 | 0.81 | +| 9 | 0.8 | 0.8 | +| 10 | 0.78 | 0.78 | +| 11 | 0.75 | 0.75 | +| 12 | 0.7 | 0.7 | +| 13 | 0.65 | 0.65 | +| 14 | 0.25 | 0.25 | +| 15 | 0.22 | 0.22 | +| 16 | 0.2 | 0.2 | +| 17 | 0.1 | 0.1 | +| 18 | 0.15 | 0.15 | +| 19 | 0.4 | 0.4 | +| 20 | 0.75 | 0.75 | + +Line graph titled 'Combined Beams' for Band n41. The y-axis represents correlation from 0 to 1, and the x-axis represents beam indices from 1 to 20. Two lines are plotted: a blue 'Reference' line and an orange 'Measured' line. Both lines start at 1.0 for beam 1 and gradually decrease to approximately 0.65 at beam 13. At beam 14, there is a sharp drop to about 0.25. The correlation remains low until beam 17, then rises to about 0.75 at beam 20. The two lines are nearly perfectly overlaid. + +(a) Band n41 + +![Line graph titled 'Combined Beams' for Band n78. The y-axis represents correlation from 0 to 1, and the x-axis represents beam indices from 1 to 29. Two lines are plotted: a blue 'Reference' line and a yellow 'Measured' line. Both lines start at 1.0 for beam 1 and gradually decrease to about 0.4 at beam 19. At beam 21, there is a sharp drop to about 0.15. The correlation then fluctuates, with peaks at beams 22 (~0.7), 24 (~0.45), and 27 (~0.45), and a sharp rise to about 0.95 at beam 29. The two lines are nearly perfectly overlaid.](d1c99a42332e5ee19f3b840281c26681_img.jpg) + +| Beam Index | Reference | Measured | +|------------|-----------|----------| +| 1 | 1.0 | 1.0 | +| 3 | 0.95 | 0.95 | +| 5 | 0.85 | 0.85 | +| 7 | 0.75 | 0.75 | +| 9 | 0.72 | 0.72 | +| 11 | 0.7 | 0.7 | +| 13 | 0.68 | 0.68 | +| 15 | 0.65 | 0.65 | +| 17 | 0.6 | 0.6 | +| 19 | 0.4 | 0.4 | +| 21 | 0.15 | 0.15 | +| 22 | 0.7 | 0.7 | +| 23 | 0.45 | 0.45 | +| 24 | 0.45 | 0.45 | +| 25 | 0.2 | 0.2 | +| 26 | 0.25 | 0.25 | +| 27 | 0.45 | 0.45 | +| 28 | 0.35 | 0.35 | +| 29 | 0.95 | 0.95 | + +Line graph titled 'Combined Beams' for Band n78. The y-axis represents correlation from 0 to 1, and the x-axis represents beam indices from 1 to 29. Two lines are plotted: a blue 'Reference' line and a yellow 'Measured' line. Both lines start at 1.0 for beam 1 and gradually decrease to about 0.4 at beam 19. At beam 21, there is a sharp drop to about 0.15. The correlation then fluctuates, with peaks at beams 22 (~0.7), 24 (~0.45), and 27 (~0.45), and a sharp rise to about 0.95 at beam 29. The two lines are nearly perfectly overlaid. + +(b) Band n78 + +Figure 6.2.2.3-5: Lab 5: Spatial correlation measurement results for CDL-C UMa, (a) Band n41, combined beams; (b) Band n78, combined beams + +![Line graph titled 'F64 Spatial Corr 2450MHz Combined Beams'. The y-axis is labeled 'Correlation' and ranges from 0 to 1. The x-axis is labeled 'Azimuth point' and ranges from 1 to 20. Two lines are plotted: a red 'Reference' line and a blue 'Measured' line. Both lines start at 1.0 for point 1 and gradually decrease to about 0.8 at point 10. At point 14, there is a sharp drop to about 0.25. The correlation remains low until point 17, then rises to about 0.8 at point 20. The two lines are nearly perfectly overlaid.](d04ba66e3c0eccfd8fd2b0d176d3c941_img.jpg) + +| Azimuth Point | Reference | Measured | +|---------------|-----------|----------| +| 1 | 1.0 | 1.0 | +| 2 | 0.98 | 0.98 | +| 3 | 0.95 | 0.95 | +| 4 | 0.92 | 0.92 | +| 5 | 0.88 | 0.88 | +| 6 | 0.85 | 0.85 | +| 7 | 0.83 | 0.83 | +| 8 | 0.81 | 0.81 | +| 9 | 0.8 | 0.8 | +| 10 | 0.78 | 0.78 | +| 11 | 0.75 | 0.75 | +| 12 | 0.7 | 0.7 | +| 13 | 0.65 | 0.65 | +| 14 | 0.25 | 0.25 | +| 15 | 0.22 | 0.22 | +| 16 | 0.2 | 0.2 | +| 17 | 0.1 | 0.1 | +| 18 | 0.15 | 0.15 | +| 19 | 0.4 | 0.4 | +| 20 | 0.8 | 0.8 | + +Line graph titled 'F64 Spatial Corr 2450MHz Combined Beams'. The y-axis is labeled 'Correlation' and ranges from 0 to 1. The x-axis is labeled 'Azimuth point' and ranges from 1 to 20. Two lines are plotted: a red 'Reference' line and a blue 'Measured' line. Both lines start at 1.0 for point 1 and gradually decrease to about 0.8 at point 10. At point 14, there is a sharp drop to about 0.25. The correlation remains low until point 17, then rises to about 0.8 at point 20. The two lines are nearly perfectly overlaid. + +(a) Band n41 + +![Line graph titled 'F64 Spatial Corr 3600MHz Combined Beams' showing correlation vs azimuth point for Reference and Measured beams.](4dfe30ac5a87d018364a0ac42ea533fe_img.jpg) + +This line graph, titled "F64 Spatial Corr 3600MHz Combined Beams", plots the correlation between two beams across 30 azimuth points. The y-axis is labeled "Correlation" and ranges from 0 to 1. The x-axis is labeled "Azimuth point" and ranges from 1 to 30. Two data series are shown: a red line for "Reference" and a blue line for "Measured". Both lines start at a correlation of 1.0 at point 1 and generally decrease as the azimuth point increases, with some fluctuations. The measured correlation is slightly lower than the reference correlation for most points. + +| Azimuth point | Reference | Measured | +|---------------|-----------|----------| +| 1 | 1.0 | 1.0 | +| 2 | 0.95 | 0.95 | +| 3 | 0.9 | 0.9 | +| 4 | 0.85 | 0.85 | +| 5 | 0.8 | 0.8 | +| 6 | 0.78 | 0.78 | +| 7 | 0.75 | 0.75 | +| 8 | 0.72 | 0.72 | +| 9 | 0.7 | 0.7 | +| 10 | 0.68 | 0.68 | +| 11 | 0.66 | 0.66 | +| 12 | 0.64 | 0.64 | +| 13 | 0.62 | 0.62 | +| 14 | 0.6 | 0.6 | +| 15 | 0.58 | 0.58 | +| 16 | 0.55 | 0.55 | +| 17 | 0.5 | 0.5 | +| 18 | 0.45 | 0.45 | +| 19 | 0.4 | 0.4 | +| 20 | 0.42 | 0.55 | +| 21 | 0.2 | 0.2 | +| 22 | 0.65 | 0.65 | +| 23 | 0.5 | 0.5 | +| 24 | 0.45 | 0.6 | +| 25 | 0.2 | 0.2 | +| 26 | 0.15 | 0.15 | +| 27 | 0.15 | 0.15 | +| 28 | 0.4 | 0.3 | +| 29 | 0.4 | 0.35 | +| 30 | 0.95 | 0.95 | + +Line graph titled 'F64 Spatial Corr 3600MHz Combined Beams' showing correlation vs azimuth point for Reference and Measured beams. + +(b) Band n78 + +Figure 6.2.2.3-6: Lab 6: Spatial correlation measurement results for CDL-C UMa, (a) Band n41, combined beams; (b) Band n78, combined beams + +The Spatial correlation measurement results of UMi CDL-C for band n28 are presented in Figures 6.2.2.3-7~12. + +![Line graph titled 'Spatial correlation, UMi CDL-C, FR1 Beam 1, fc=722 MHz' showing correlation vs azimuth angle for Measured, Reference, and Limits.](3d7e0eb9c7e514f3026945a039354da4_img.jpg) + +This line graph, titled "Spatial correlation, UMi CDL-C, FR1 Beam 1, fc=722 MHz", plots the correlation against the azimuth angle in degrees. The y-axis is labeled "Correlation" and ranges from 0.4 to 1.0. The x-axis is labeled "Azimuth angle [°]" and ranges from 270 to -90. Three data series are shown: a red line with circles for "Measured", a blue dashed line with stars for "Reference", and two dashed grey lines for "Limits". The correlation starts at 1.0 for angles 270, 225, and 180 degrees. It decreases to a minimum around 45 degrees (Measured: ~0.72, Reference: ~0.8) and then increases back towards 1.0 at -90 degrees. + +| Azimuth angle [°] | Measured | Reference | Upper Limit | Lower Limit | +|-------------------|----------|-----------|-------------|-------------| +| 270 | 1.0 | 1.0 | 1.0 | 0.9 | +| 225 | 1.0 | 1.0 | 1.0 | 0.9 | +| 180 | 1.0 | 1.0 | 1.0 | 0.85 | +| 135 | 0.78 | 0.85 | 0.95 | 0.75 | +| 90 | 0.72 | 0.8 | 0.9 | 0.7 | +| 45 | 0.72 | 0.8 | 0.9 | 0.7 | +| 0 | 0.88 | 0.9 | 1.0 | 0.8 | +| -45 | 0.98 | 0.98 | 1.0 | 0.9 | +| -90 | 1.0 | 1.0 | 1.0 | 0.9 | + +Line graph titled 'Spatial correlation, UMi CDL-C, FR1 Beam 1, fc=722 MHz' showing correlation vs azimuth angle for Measured, Reference, and Limits. + +Figure 6.2.2.3-7: Lab 1: Spatial correlation measurement results for CDL-C UMi at Band n28, beam 1 + +![Figure 6.2.2.3-8: CDL-C UMi 722MHz Beam1 Spatial Correlation plot. The y-axis is 'Spatial Correlation |ρ|' ranging from 0.75 to 1.0. The x-axis is 'Sensor Array Position' from 1 to 10. Two data series are shown: 'theory' (blue line with star markers) and 'measured' (red line with circle markers). Both series start at 1.0 for positions 1-4, then decrease to a minimum at position 8 (theory ≈ 0.80, measured ≈ 0.82) before rising back towards 1.0 at position 10.](853ef5420f0432e626e83987e3f38a0b_img.jpg) + +| Sensor Array Position | Theory ρ | Measured ρ | +|-----------------------|-----------|-------------| +| 1 | 1.00 | 1.00 | +| 2 | 1.00 | 1.00 | +| 3 | 1.00 | 1.00 | +| 4 | 1.00 | 1.00 | +| 5 | 0.99 | 0.99 | +| 6 | 0.98 | 0.98 | +| 7 | 0.84 | 0.85 | +| 8 | 0.80 | 0.82 | +| 9 | 0.91 | 0.94 | +| 10 | 0.99 | 0.99 | + +Figure 6.2.2.3-8: CDL-C UMi 722MHz Beam1 Spatial Correlation plot. The y-axis is 'Spatial Correlation |ρ|' ranging from 0.75 to 1.0. The x-axis is 'Sensor Array Position' from 1 to 10. Two data series are shown: 'theory' (blue line with star markers) and 'measured' (red line with circle markers). Both series start at 1.0 for positions 1-4, then decrease to a minimum at position 8 (theory ≈ 0.80, measured ≈ 0.82) before rising back towards 1.0 at position 10. + +Figure 6.2.2.3-8: Lab 2: Spatial correlation measurement results for CDL-C UMi at Band n28, beam 1 + +![Figure 6.2.2.3-9: N28 722MHz Spatial Correlation plot. The y-axis is 'Correlation' ranging from 0.5 to 1.1. The x-axis is 'Position/degree' with values: 270, 254.1, 238.3, 222.4, 206.6, 190.7, 120.52, 61.05, 1.57, 302.09. Three data series are shown: 'Lower' (blue line with circle markers), 'Upper' (orange line with circle markers), and 'Measured' (yellow line with circle markers). All series start near 1.0, dip at position 61.05 (Measured ≈ 0.70, Lower ≈ 0.70, Upper ≈ 0.90), and then rise back towards 1.0.](8fd97886a32c3ac7abb08aba9f7f231b_img.jpg) + +| Position/degree | Lower | Upper | Measured | +|-----------------|-------|-------|----------| +| 270 | 0.90 | 1.00 | 1.00 | +| 254.1 | 0.90 | 1.00 | 1.00 | +| 238.3 | 0.90 | 1.00 | 1.00 | +| 222.4 | 0.90 | 1.00 | 1.00 | +| 206.6 | 0.89 | 1.00 | 1.00 | +| 190.7 | 0.88 | 1.00 | 0.98 | +| 120.52 | 0.73 | 0.95 | 0.78 | +| 61.05 | 0.70 | 0.90 | 0.70 | +| 1.57 | 0.81 | 1.00 | 0.85 | +| 302.09 | 0.89 | 1.00 | 1.00 | + +Figure 6.2.2.3-9: N28 722MHz Spatial Correlation plot. The y-axis is 'Correlation' ranging from 0.5 to 1.1. The x-axis is 'Position/degree' with values: 270, 254.1, 238.3, 222.4, 206.6, 190.7, 120.52, 61.05, 1.57, 302.09. Three data series are shown: 'Lower' (blue line with circle markers), 'Upper' (orange line with circle markers), and 'Measured' (yellow line with circle markers). All series start near 1.0, dip at position 61.05 (Measured ≈ 0.70, Lower ≈ 0.70, Upper ≈ 0.90), and then rise back towards 1.0. + +Figure 6.2.2.3-9: Lab 4: Spatial correlation measurement results for CDL-C UMi at Band n28, beam 1 + +![Figure 6.2.2.3-10: Spatial correlation, CDL-C UMi beam 1, fc=722MHz plot. The y-axis is 'Spatial correlation' ranging from 0.4 to 1.1. The x-axis is 'Position/degree' with values: 270, 254.1, 238.3, 222.4, 206.6, 190.7, 120.5, 61.1, 1.6, 302.1. Four data series are shown: 'Measured' (solid dark purple line with circle markers), 'Reference' (solid red line), 'Lower' (dashed blue line), and 'Upper' (dashed light blue line). All series start near 1.0, dip at position 61.1 (Measured ≈ 0.90, Reference ≈ 0.80, Lower ≈ 0.70, Upper ≈ 0.70), and then rise back towards 1.0.](5e16d3613b74558acc74ff6d7fd75fa9_img.jpg) + +| Position/degree | Measured | Reference | Lower | Upper | +|-----------------|----------|-----------|-------|-------| +| 270 | 1.00 | 1.00 | 0.90 | 1.00 | +| 254.1 | 1.00 | 1.00 | 0.90 | 1.00 | +| 238.3 | 1.00 | 1.00 | 0.90 | 1.00 | +| 222.4 | 1.00 | 1.00 | 0.90 | 1.00 | +| 206.6 | 1.00 | 1.00 | 0.90 | 1.00 | +| 190.7 | 1.00 | 1.00 | 0.90 | 1.00 | +| 120.5 | 0.93 | 0.83 | 0.73 | 0.93 | +| 61.1 | 0.90 | 0.80 | 0.70 | 0.90 | +| 1.6 | 0.97 | 0.90 | 0.80 | 1.00 | +| 302.1 | 1.00 | 1.00 | 0.90 | 1.00 | + +Figure 6.2.2.3-10: Spatial correlation, CDL-C UMi beam 1, fc=722MHz plot. The y-axis is 'Spatial correlation' ranging from 0.4 to 1.1. The x-axis is 'Position/degree' with values: 270, 254.1, 238.3, 222.4, 206.6, 190.7, 120.5, 61.1, 1.6, 302.1. Four data series are shown: 'Measured' (solid dark purple line with circle markers), 'Reference' (solid red line), 'Lower' (dashed blue line), and 'Upper' (dashed light blue line). All series start near 1.0, dip at position 61.1 (Measured ≈ 0.90, Reference ≈ 0.80, Lower ≈ 0.70, Upper ≈ 0.70), and then rise back towards 1.0. + +Figure 6.2.2.3-10: Lab 5: Spatial correlation measurement results for CDL-C UMi at Band n28, beam 1 + +![Line graph titled 'Spatial Correlation x Azimuth at 722MHz'. The y-axis represents correlation from 0 to 1. The x-axis represents azimuth from 1 to 10. Two lines are plotted: 'Measured correlation' (blue solid) and 'Target correlation' (red solid). Both lines start at 1.0, remain nearly constant until azimuth 6, then dip to a minimum of approximately 0.8 at azimuth 8, before rising back to 1.0 at azimuth 10.](051638d871c75230edb3d005fa668810_img.jpg) + +Line graph titled 'Spatial Correlation x Azimuth at 722MHz'. The y-axis represents correlation from 0 to 1. The x-axis represents azimuth from 1 to 10. Two lines are plotted: 'Measured correlation' (blue solid) and 'Target correlation' (red solid). Both lines start at 1.0, remain nearly constant until azimuth 6, then dip to a minimum of approximately 0.8 at azimuth 8, before rising back to 1.0 at azimuth 10. + +Figure 6.2.2.3-11: Lab 6: Spatial correlation measurement results for CDL-C UMi at Band n28, beam 1 + +![Line graph titled 'Spatial correlation, CDL-C UMi Beam1 Fc=722MHz'. The y-axis represents correlation from 0.4 to 1.0. The x-axis shows frequency values: 270, 254.1, 238.3, 222.4, 206.6, 190.7, 120.5, 61.1, 1.6, 302.1. Four lines are plotted: 'Measured' (green solid), 'Target' (red dashed), 'Lower limit' (blue dashed), and 'Upper limit' (blue dashed). The measured and target lines are nearly identical, starting at 1.0, dipping to about 0.8 at 61.1 MHz, and returning to 1.0 at 302.1 MHz. The lower limit line follows a similar pattern but dips lower, reaching about 0.7 at 61.1 MHz.](bac21fd48fcd7f025c723590e07d1823_img.jpg) + +Line graph titled 'Spatial correlation, CDL-C UMi Beam1 Fc=722MHz'. The y-axis represents correlation from 0.4 to 1.0. The x-axis shows frequency values: 270, 254.1, 238.3, 222.4, 206.6, 190.7, 120.5, 61.1, 1.6, 302.1. Four lines are plotted: 'Measured' (green solid), 'Target' (red dashed), 'Lower limit' (blue dashed), and 'Upper limit' (blue dashed). The measured and target lines are nearly identical, starting at 1.0, dipping to about 0.8 at 61.1 MHz, and returning to 1.0 at 302.1 MHz. The lower limit line follows a similar pattern but dips lower, reaching about 0.7 at 61.1 MHz. + +Figure 6.2.2.3-12: Lab 7: Spatial correlation measurement results for CDL-C UMi at Band n28, beam 1 + +#### 6.2.2.4 Cross-polarization + +The Cross-polarization should be validated in a Beam-Specific manner. It is assumed that the beams are mapped to the inputs of the channel emulator as follows: + +- Beam 1: Input 1 and Input 2 +- Beam 2: Input 3 and Input 4 (CDL-C UMa only) + +The Cross-polarization measurement results of UMa CDL-C for bands n41 and n78 are presented in Table 6.2.2.4-1~6. + +Table 6.2.2.4-1: Lab 1: Cross-polarization verification results for CDL-C UMa, bands n41 and n78 + +| Frequency | Beam | Reference | Measurement result | +|--------------------|--------|-----------------------|--------------------| +| fc ≤ 2.5 GHz (n41) | Beam 1 | Input 1+2: V/H = 0 dB | 0.44 dB | +| | Beam 2 | Input 3+4: V/H = 0 dB | 0.55 dB | +| fc > 2.5 GHz (n78) | Beam 1 | Input 1+2: V/H = 0 dB | 0.49 dB | +| | Beam 2 | Input 3+4: V/H = 0 dB | 0.58 dB | + +Table 6.2.2.4-2: Lab 2: Cross-polarization verification results for CDL-C UMa, bands n41 and n78 + +| Frequency | Beam | Reference | Measurement result | +|--------------------|--------|-------------------------------------------------|---------------------------------------------------| +| fc ≤ 2.5 GHz (n41) | Beam 1 | Input 1: V/H = -0.5 dB
Input 2: V/H = 0.6 dB | Input 1: V/H = -0.96 dB
Input 2: V/H = 0.94 dB | +| | Beam 2 | Input 3: V/H = -0.6 dB
Input 4: V/H = 0.7 dB | Input 3: V/H = -0.11 dB
Input 4: V/H = 0.71 dB | +| fc > 2.5 GHz (n78) | Beam 1 | Input 1: V/H = -0.6 dB
Input 2: V/H = 0.7 dB | Input 1: V/H = -0.51 dB
Input 2: V/H = 1.19 dB | +| | Beam 2 | Input 3: V/H = -0.7 dB
Input 4: V/H = 0.8 dB | Input 3: V/H = -0.41 dB
Input 4: V/H = 0.47 dB | + +Table 6.2.2.4-3: Lab 3: Cross-polarization verification results for CDL-C UMa, bands n41 and n78 + +| Frequency | Beam | Reference | Measurement result | +|--------------------|--------|---------------------------------------------------------------------------|---------------------------------------------------------------------------------| +| fc ≤ 2.5 GHz (n41) | Beam 1 | Input 1: V/H = -0.5 dB
Input 2: V/H = 0.6 dB
Input 1+ 2: V/H = 0 dB | Input 1: V/H = -0.98 dB
Input 2: V/H = 0.63 dB
Input 1+ 2: V/H = -0.21 dB | +| | Beam 2 | Input 3: V/H = -0.6 dB
Input 4: V/H = 0.7 dB
Input 3+4: V/H = 0 dB | Input 3: V/H = -1.1dB
Input 4: V/H = -0.07 dB
Input 3+4: V/H = -0.60 dB | +| fc > 2.5 GHz (n78) | Beam 1 | Input 1: V/H = -0.6 dB
Input 2: V/H = 0.7 dB
Input 1+ 2: V/H = 0 dB | Input 1: V/H = -0.45
Input 2: V/H = 1.32 dB
Input 1+ 2: V/H = 0.39 dB | +| | Beam 2 | Input 3: V/H = -0.7 dB
Input 4: V/H = 0.8 dB
Input 3+4: V/H = 0 dB | Input 3: V/H = 0.25
Input 4: V/H = 1.61
Input 3+4: V/H = 0.91 dB | + +Table 6.2.2.4-4: Lab 4: Cross-polarization verification results for CDL-C UMa, bands n41 and n78 + +| Frequency | Beam | Reference | Measurement result | +|--------------------|--------|------------------------|--------------------| +| fc ≤ 2.5 GHz (n41) | Beam 1 | Input 1: V/H = -0.5 dB | -0.48 dB | +| | | Input 2: V/H = 0.6 dB | 0.57 dB | +| | Beam 2 | Input 3: V/H = -0.6 dB | -0.69 dB | +| | | Input 4: V/H = 0.7 dB | 0.71 dB | +| fc > 2.5 GHz (n78) | Beam 1 | Input 1: V/H = -0.6 dB | -0.48 | +| | | Input 2: V/H = 0.7 dB | 0.99 | +| | Beam 2 | Input 3: V/H = -0.7 dB | -0.34 | +| | | Input 4: V/H = 0.8 dB | 1.13 | + +Table 6.2.2.4-5: Lab 5: Cross-polarization verification results for CDL-C UMa, band n41 + +| Frequency | Beam | Reference | Measurement result | +|--------------------|--------|------------------------|--------------------| +| fc ≤ 2.5 GHz (n41) | Beam 1 | Input 1: V/H = -0.5 dB | -0.48 dB | +| | | Input 2: V/H = 0.6 dB | 0.61 dB | +| | Beam 2 | Input 3: V/H = -0.6 dB | -0.64 dB | +| | | Input 4: V/H = 0.7 dB | 0.68 dB | + +**Table 6.2.2.4-6: Lab 6: Cross-polarization verification results for CDL-C UMa, bands n41 and n78** + +| Frequency | Beam | Reference | Measurement result | +|--------------------------|--------|-----------------------|--------------------| +| $f_c \leq 2.5$ GHz (n41) | Beam 1 | Input 1+2: V/H = 0 dB | -0.6555 dB | +| | Beam 2 | Input 3+4: V/H = 0 dB | -0.0676 dB | +| $f_c > 2.5$ GHz (n78) | Beam 1 | Input 1+2: V/H = 0 dB | 0.5064 dB | +| | Beam 2 | Input 3+4: V/H = 0 dB | 0.6414 dB | + +The Cross-polarization measurement results of UMi CDL-C for band n428 are presented in Table 6.2.2.4-7~12. + +**Table 6.2.2.4-7: Lab 1: Cross-polarization verification results for CDL-C UMi, Band n28** + +| Frequency | Beam | Reference | Measurement result | Pass/fail limit | +|-----------------|--------|-----------------------|--------------------|-----------------| +| $f_c = 722$ MHz | Beam 1 | Input 1+2: V/H = 0 dB | V/H = -0.08 dB | $\pm 1$ dB | + +**Table 6.2.2.4-8: Lab 2: Cross-polarization verification results for CDL-C UMi, Band n28** + +| Frequency | Beam | Reference | Measurement result | Pass/fail limit | +|-----------------|--------|-----------------------|--------------------|-----------------| +| $f_c = 722$ MHz | Beam 1 | Input 1+2: V/H = 0 dB | V/H = 0.15 dB | $\pm 1$ dB | + +**Table 6.2.2.4-9: Lab 4: Cross-polarization verification results for CDL-C UMi, Band n28** + +| Frequency | Beam | Reference | Measurement result | Pass/fail limit | +|-----------------|--------|-----------------------|--------------------|-----------------| +| $f_c = 722$ MHz | Beam 1 | Input 1+2: V/H = 0 dB | V/H = -0.14 dB | $\pm 1$ dB | + +**Table 6.2.2.4-10: Lab 5: Cross-polarization verification results for CDL-C UMi, Band n28** + +| Frequency | Beam | Reference | Measurement result | Pass/fail limit | +|-----------------|--------|-----------------------|--------------------|-----------------| +| $f_c = 722$ MHz | Beam 1 | Input 1+2: V/H = 0 dB | V/H = -0.09 dB | $\pm 1$ dB | + +**Table 6.2.2.4-11: Lab 6: Cross-polarization verification results for CDL-C UMi, Band n28** + +| Frequency | Beam | Reference | Measurement result | Pass/fail limit | +|-----------------|--------|-----------------------|--------------------|-----------------| +| $f_c = 722$ MHz | Beam 1 | Input 1+2: V/H = 0 dB | V/H = 0.59 dB | $\pm 1$ dB | + +**Table 6.2.2.4-12: Lab 7: Cross-polarization verification results for CDL-C UMi, Band n28** + +| Frequency | Beam | Reference | Measurement result | Pass/fail limit | +|-----------------|--------|-----------------------|--------------------|-----------------| +| $f_c = 722$ MHz | Beam 1 | Input 1+2: V/H = 0 dB | V/H = -0.71 dB | $\pm 1$ dB | + +#### 6.2.2.5 Power validation + +The Power validation results of UMa CDL-C for bands n41 and n78 are presented in Table 6.2.2.5-1~3. + +**Table 6.2.2.5-1: Lab 1: Power validation results for CDL-C UMa, bands n41 and n78 (Unit: dBm/30kHz)** + +| CDL-C UMa, n41, 2592.99 MHz | | | | | +|-----------------------------|------------------|----------------------|----------|--------| +| Measured V power | Measured H power | Measured total power | Expected | Delta | +| -79.6244 | -79.5959 | -76.5999 | -77 | 0.4001 | +| CDL-C UMa, n78, 3549.99 MHz | | | | | +| Measured V power | Measured H power | Measured total power | Expected | Delta | +| -79.9988 | -79.6618 | -76.8168 | -77 | 0.1832 | + +**Table 6.2.2.5-2: Lab 4: Power validation results for CDL-C UMa, bands n41 and n78 (Unit: dBm/30kHz)** + +| | | | +|-----------------------|--------|-------------| +| UMa CDL-C
2450 MHz | Dipole | S=-50.6dBm | +| | Loop | S=-50.4dBm | +| UMa CDL-C
3600 MHz | Dipole | S=-45.6dBm | +| | Loop | S=-46.68dBm | + +Table 6.2.2.5-3 (a): Lab 6: Power validation results for CDL-C UMa, band n41 (Unit: dBm/30kHz) + +| | | +|-----------------------------------|--------| +| V component [dBm] | -56.48 | +| Interferer V component [dBm] | -84.73 | +| H component [dBm] | -57.14 | +| Interferer H component [dBm] | -85.16 | +| V component compensated [dBm] | -52.55 | +| Interferer V component comp [dBm] | -80.80 | +| H component comp [dBm] | -52.71 | +| Interferer H component comp [dBm] | -80.73 | +| Target Power [dBm/20MHz] | -50.00 | +| Measured Total Power [dBm/20MHz] | -49.62 | +| Delta Power [dB] | 0.38 | +| Target SIR [dBm/20 MHz] | | +| Measured SIR [dB] | 28.13 | +| Delta SIR [dB] | 28.13 | +| Target V/H radio [dB] | 0.00 | +| Measured V/H [dB] | 0.16 | +| Delta V/H [dB] | 0.16 | + +Table 6.2.2.5-3 (b): Lab 6: Power validation results for CDL-C UMa, band n78 (Unit: dBm/30kHz) + +| | | +|-----------------------------------|--------| +| V component [dBm] | -57.05 | +| Interferer V component [dBm] | -85.51 | +| H component [dBm] | -58.59 | +| Interferer H component [dBm] | -86.36 | +| V component compensated [dBm] | -53.31 | +| Interferer V component comp [dBm] | -81.78 | +| H component comp [dBm] | -53.85 | +| Interferer H component comp [dBm] | -81.63 | +| Target Power [dBm/20MHz] | -50.00 | +| Measured Total Power [dBm/20MHz] | -50.56 | +| Delta Power [dB] | -0.56 | +| Target SIR [dBm/20 MHz] | | +| Measured SIR [dB] | 28.13 | +| Delta SIR [dB] | 28.13 | +| Target V/H radio [dB] | 0.00 | +| Measured V/H [dB] | 0.54 | +| Delta V/H [dB] | 0.54 | + +The Power validation results of UMi CDL-C for band n28 are presented in Table 6.2.2.5-4~8. + +**Table 6.2.2.5-4: Lab 1: Power validation results for CDL-C UMi, Band n28 (Unit: dBm/15kHz)** + +| Frequency | Measured V power | Measured H power | Measured total power | Target power | Delta | Pass/fail limit | +|-----------|------------------|------------------|----------------------|--------------|-------------|-----------------| +| 780.5 MHz | -83.1288 | -82.9819 | -80.0444 | -80 | -
0.0444 | ±1.5 dB | + +**Table 6.2.2.5-5: Lab 4: Power validation results for CDL-C UMi, Band n28 (Unit: dBm/15kHz)** + +| Frequency | Measured power | Target power | Delta | Pass/fail limit | +|-----------|----------------|--------------|-------------|-----------------| +| 780.5 MHz | -70.6609811 | -70.6 | -0.06098109 | ±1.5 dB | +| | -80.5325084 | -80.6 | 0.067491565 | | +| | -90.116428 | -90.6 | 0.483572032 | | + +**Table 6.2.2.5-6: Lab 5: Power validation results for CDL-C UMi, Band n28 (Unit: dBm/15kHz)** + +| Frequency | Measured power | Target power | Delta | Pass/fail limit | +|-----------|----------------|--------------|-------|-----------------| +| 780.5 MHz | NA | NA | 1.3 | ±1.5 dB | + +**Table 6.2.2.5-7: Lab 6: Power validation results for CDL-C UMi, Band n28 (Unit: dBm/15kHz)** + +| Frequency | Measured power | Target power | Delta | Pass/fail limit | +|-----------|----------------|--------------|-------|-----------------| +| 780.5 MHz | -49.64 | -50.00 | 0.36 | ±1.5 dB | + +**Table 6.2.2.5-8: Lab 7: Power validation results for CDL-C UMi, Band n28 (Unit: dBm/15kHz)** + +| Frequency | Measured power | Target power | Delta | Pass/fail limit | +|-----------|----------------|--------------|--------|-----------------| +| 780.5 MHz | NA | NA | 0.0002 | ±1.5 dB | + +## 6.3 Verification of Channel Model implementation of FR2 + +### 6.3.1 Framework + +This clause describes how to proceed Channel Model Validation for FR2 MIMO OTA with 3D-MPAC system. + +- The channel model validation measurements shall be performed as described in Annex D.3 of TS 38.151, including: + - Power delay profile (PDP) + - Doppler/Temporal correlation + - PAS similarity percentage (PSP) + - Cross-polarization + +- Power validation +2. Channel model: FR2 UMi CDL-C, as specified in Annex D.1 of TS 38.151 + 3. Test frequency: as specified in Tables D.3.1-1 of TS 38.151 + 4. Pass/fail limits: as defined in Annex D.2 of TS 38.151 + +### 6.3.2 Channel Model Validation Results + +This clause presents channel model validation results from different labs with different types of equipment and setup vendors. All the validation results are included for comparison. Table 6.3.2-1 lists equipment and setup vendors of different labs. + +**Table 6.3.2-1: Equipment and setup vendors of different labs (FR2)** + +| Labs | Channel Emulator | BS Simulator | System | +|-------|------------------|--------------|------------| +| Lab A | Vendor 1 | Vendor A | Vendor I | +| Lab B | Vendor 2 | TBA | Vendor II | +| Lab C | Vendor 1 | TBA | Vendor III | +| Lab D | Vendor 2 | TBA | Vendor II | +| Lab E | Vendor 1 | TBA | Vendor III | +| Lab F | Vendor 1 | TBA | Vendor IV | + +#### 6.3.2.1 Power Delay Profile (PDP) + +The PDP measurement results of UMi CDL-C for bands n261/28GHz are presented in Figures 6.3.2.1-1~6. + +![Figure 6.3.2.1-1: PDP measurement results for CDL-C UMi at 28GHz. The graph shows Magnitude [dB] on the y-axis (from -40 to 5) versus Delay [ns] on the x-axis (from -20 to 120). Three data series are plotted: 'Measured' (blue line), 'Model' (orange line with circles), and 'Target (3GPP TS 38.151)' (black squares). The 'Measured' data shows a broad peak around 40 ns delay. The 'Model' data shows several sharp peaks, with the highest peak at approximately 40 ns delay reaching about -5 dB. The 'Target' data points are located at approximately 15 ns, 40 ns, and 75 ns delay, with magnitudes around -18 dB, -5 dB, and -30 dB respectively.](a82f2d67d7b1d9645cacd98ecc78608f_img.jpg) + +Figure 6.3.2.1-1: PDP measurement results for CDL-C UMi at 28GHz. The graph shows Magnitude [dB] on the y-axis (from -40 to 5) versus Delay [ns] on the x-axis (from -20 to 120). Three data series are plotted: 'Measured' (blue line), 'Model' (orange line with circles), and 'Target (3GPP TS 38.151)' (black squares). The 'Measured' data shows a broad peak around 40 ns delay. The 'Model' data shows several sharp peaks, with the highest peak at approximately 40 ns delay reaching about -5 dB. The 'Target' data points are located at approximately 15 ns, 40 ns, and 75 ns delay, with magnitudes around -18 dB, -5 dB, and -30 dB respectively. + +**Figure 6.3.2.1-1: Lab A: PDP measurement results for CDL-C UMi at 28GHz** + +![PDP, FR2 UMi CDL-C, fc = 27925MHz plot showing Relative power [dB] vs Delay [ns].](cfc852835f2d91bea8dc074568937e22_img.jpg) + +This line graph shows the Power Delay Profile (PDP) for FR2 UMi CDL-C at a carrier frequency (fc) of 27925MHz. The y-axis represents 'Relative power [dB]' ranging from -40 to 0, and the x-axis represents 'Delay [ns]' ranging from 0 to 160. A blue line represents the 'Measured' data, showing a primary peak at approximately 40 ns with a power of 0 dB, and secondary peaks at approximately 15 ns (-18 dB) and 75 ns (-32 dB). Red 'x' marks represent the 'Reference' data points, which align with the peaks of the measured data. + +| Delay [ns] | Relative power [dB] (Measured) | Relative power [dB] (Reference) | +|------------|--------------------------------|---------------------------------| +| 0 | -30 | -30 | +| 15 | -18 | -18 | +| 40 | 0 | 0 | +| 75 | -32 | -32 | +| 100 | -40 | -40 | + +PDP, FR2 UMi CDL-C, fc = 27925MHz plot showing Relative power [dB] vs Delay [ns]. + +Figure 6.3.2.1-2: Lab B: PDP measurement results for CDL-C UMi at band n261 + +![CDL-C UMi 28GHz Beam1 PDP plot showing Mag[dB] vs Time[ns].](809eec371620084c4b949c66d5d7bae0_img.jpg) + +This line graph shows the PDP for CDL-C UMi at 28GHz for Beam 1. The y-axis represents 'Mag[dB]' ranging from -50 to 0, and the x-axis represents 'Time[ns]' ranging from 0 to 300. A blue line represents the 'Measured' data, with a main peak at approximately 40 ns (0 dB) and smaller peaks at approximately 15 ns (-18 dB) and 75 ns (-32 dB). Red circles represent the 'Theoretical' data points, which align with the peaks of the measured data. + +| Time [ns] | Mag[dB] (Measured) | Mag[dB] (Theoretical) | +|-----------|--------------------|-----------------------| +| 0 | -30 | -30 | +| 15 | -18 | -18 | +| 40 | 0 | 0 | +| 75 | -32 | -32 | +| 100 | -50 | -50 | + +CDL-C UMi 28GHz Beam1 PDP plot showing Mag[dB] vs Time[ns]. + +Figure 6.3.2.1-3: Lab C: PDP measurement results for CDL-C UMi at band n261 + +![PDP measurement results plot showing (dB) vs Time[ns].](b88b618bb8863766bd545c6bfb31f850_img.jpg) + +This line graph shows the PDP measurement results. The y-axis represents '(dB)' ranging from -45 to 0, and the x-axis represents 'Time[ns]' ranging from 0 to 120. A black line represents the 'Measured' data, showing a main peak at approximately 40 ns (0 dB) and smaller peaks at approximately 15 ns (-18 dB) and 75 ns (-32 dB). Blue circles represent the 'Reference' data points, which align with the peaks of the measured data. Yellow rectangular boxes highlight the peaks at 15 ns, 40 ns, and 75 ns. + +| Time [ns] | (dB) (Measured) | (dB) (Reference) | +|-----------|-----------------|------------------| +| 0 | -30 | -30 | +| 15 | -18 | -18 | +| 40 | 0 | 0 | +| 75 | -32 | -32 | +| 100 | -40 | -40 | + +PDP measurement results plot showing (dB) vs Time[ns]. + +Figure 6.3.2.1-4: Lab D: PDP measurement results for CDL-C UMi at band n261 + +![Figure 6.3.2.1-5: PDP measurement results for CDL-C UMi at band n261. The graph plots Power Level [dB] on the y-axis (from -50 to 10) against Time [ns] on the x-axis (from 0 to 120). It features three data series: 'Measured' (green line), 'Original Model' (blue dots), and 'Reference' (red dots). The measured data shows a primary peak at approximately 40 ns with a power level near 0 dB, and secondary peaks at roughly 15 ns and 80 ns. The model and reference points closely follow the measured peaks.](516d9f1866cc2e359a35fb1d8c046454_img.jpg) + +Figure 6.3.2.1-5: PDP measurement results for CDL-C UMi at band n261. The graph plots Power Level [dB] on the y-axis (from -50 to 10) against Time [ns] on the x-axis (from 0 to 120). It features three data series: 'Measured' (green line), 'Original Model' (blue dots), and 'Reference' (red dots). The measured data shows a primary peak at approximately 40 ns with a power level near 0 dB, and secondary peaks at roughly 15 ns and 80 ns. The model and reference points closely follow the measured peaks. + +Figure 6.3.2.1-5 Lab E: PDP measurement results for CDL-C UMi at band n261 + +![Figure 6.3.2.1-6: PDP measurement results for CDL-C UMi at 28GHz. The graph plots Magnitude [dB] on the y-axis (from -60 to 0) against Delay [ns] on the x-axis (from -50 to 450). It includes three series: 'Measured' (blue line), 'theor.' (orange line with circles), and 'BWFiltered theor.' (yellow line). Three major peaks are identified with callouts: X: 38.2, Y: -2.7; X: 162.6, Y: -41.27; and X: 255.5, Y: -43.12. The theoretical and filtered theoretical models align well with the measured data peaks.](74448f9178da618d823e5a5dadc56fb5_img.jpg) + +Figure 6.3.2.1-6: PDP measurement results for CDL-C UMi at 28GHz. The graph plots Magnitude [dB] on the y-axis (from -60 to 0) against Delay [ns] on the x-axis (from -50 to 450). It includes three series: 'Measured' (blue line), 'theor.' (orange line with circles), and 'BWFiltered theor.' (yellow line). Three major peaks are identified with callouts: X: 38.2, Y: -2.7; X: 162.6, Y: -41.27; and X: 255.5, Y: -43.12. The theoretical and filtered theoretical models align well with the measured data peaks. + +Figure 6.3.2.1-6 Lab F: PDP measurement results for CDL-C UMi at 28GHz + +#### 6.3.2.2 Doppler/Temporal correlation + +The Doppler measurement results of UMi CDL-C for bands n261/28GHz are presented in Figures 6.3.2.2-1~6. + +![Figure 6.3.2.2-1: Doppler measurement results for CDL-C UMi at band n261. The graph plots |correlation| on the y-axis (from 0 to 1) against Distance [λ] on the x-axis (from 0 to 5). It compares 'Measured' (blue line) and 'Reference' (orange line) data for the model 'CDL-C_UMi_OTA_FR2_3GPP_n261'. Both lines show a smooth decay from a correlation of 1.0 at 0 λ, reaching a minimum near 0.0 at approximately 4 λ, before a slight rise towards 5 λ.](cd965c09af15211ca52d38d49be7b515_img.jpg) + +Figure 6.3.2.2-1: Doppler measurement results for CDL-C UMi at band n261. The graph plots |correlation| on the y-axis (from 0 to 1) against Distance [λ] on the x-axis (from 0 to 5). It compares 'Measured' (blue line) and 'Reference' (orange line) data for the model 'CDL-C\_UMi\_OTA\_FR2\_3GPP\_n261'. Both lines show a smooth decay from a correlation of 1.0 at 0 λ, reaching a minimum near 0.0 at approximately 4 λ, before a slight rise towards 5 λ. + +Figure 6.3.2.2-1: Lab A: Doppler measurement results for CDL-C UMi at band n261 + +![Figure 6.3.2.2-2: Temporal correlation, UMi CDL-C, FR2, fc = 27925MHz. A line graph showing Correlation (Y-axis, 0.0 to 1.0) versus Distance [λ] (X-axis, 0.0 to 5.0). The graph includes three data series: 'Correlation' (solid red line), 'Reference' (dotted blue line), and 'Limits' (dashed grey lines). The correlation starts at 1.0 at 0λ and decreases, reaching a minimum near 0.0 at 4.0λ, then slightly increases to about 0.15 at 5.0λ. The reference line follows the correlation line closely. The limits are shown as two dashed grey lines, one above and one below the correlation line, indicating the expected range.](0892c0cb3b8502a44c4fe4e786be912a_img.jpg) + +Temporal correlation, UMi CDL-C, FR2 + $f_c = 27925\text{MHz}$ + +Figure 6.3.2.2-2: Temporal correlation, UMi CDL-C, FR2, fc = 27925MHz. A line graph showing Correlation (Y-axis, 0.0 to 1.0) versus Distance [λ] (X-axis, 0.0 to 5.0). The graph includes three data series: 'Correlation' (solid red line), 'Reference' (dotted blue line), and 'Limits' (dashed grey lines). The correlation starts at 1.0 at 0λ and decreases, reaching a minimum near 0.0 at 4.0λ, then slightly increases to about 0.15 at 5.0λ. The reference line follows the correlation line closely. The limits are shown as two dashed grey lines, one above and one below the correlation line, indicating the expected range. + +Figure 6.3.2.2-2: Lab B: Doppler measurement results for CDL-C UMi at band n261 + +![Figure 6.3.2.2-3: CDL-C UMi 28GHz Beam 1 Temporal Correlation. A line graph showing |ρ| (Y-axis, 0 to 1) versus Distance in λ (X-axis, 0 to 5). The graph includes two data series: 'measured' (blue line with star markers) and 'reference' (solid red line). Both lines start at 1.0 at 0λ and decrease, reaching a minimum near 0.0 at 4.0λ, then slightly increases to about 0.15 at 5.0λ. The measured and reference lines are nearly perfectly overlaid.](d49bc18ad8867b97bbb9aa580449a641_img.jpg) + +CDL-C UMi 28GHz Beam 1 Temporal Correlation + +Figure 6.3.2.2-3: CDL-C UMi 28GHz Beam 1 Temporal Correlation. A line graph showing |ρ| (Y-axis, 0 to 1) versus Distance in λ (X-axis, 0 to 5). The graph includes two data series: 'measured' (blue line with star markers) and 'reference' (solid red line). Both lines start at 1.0 at 0λ and decrease, reaching a minimum near 0.0 at 4.0λ, then slightly increases to about 0.15 at 5.0λ. The measured and reference lines are nearly perfectly overlaid. + +Figure 6.3.2.2-3: Lab C: Doppler measurement results for CDL-C UMi at 28GHz + +![Figure 6.3.2.2-4: Doppler measurement results for CDL-C UMi at band n261. A line graph showing ρ (Y-axis, 0 to 1) versus Distance(λ) (X-axis, 0 to 5). The graph includes three data series: 'Measured' (solid blue line), 'Lower' (dashed red line), and 'Upper' (dashed red line). The measured line starts at 1.0 at 0λ and decreases, reaching a minimum near 0.0 at 3.2λ, then slightly increases to about 0.15 at 5.0λ. The lower limit is at 0.0 for distances greater than 2λ. The upper limit is at 0.3 for distances greater than 2λ.](237dbb78d0cad58f4dfc140988f3cd16_img.jpg) + +Distance( $\lambda$ ) + +— Measured    - - - Lower    - - - Upper + +Figure 6.3.2.2-4: Doppler measurement results for CDL-C UMi at band n261. A line graph showing ρ (Y-axis, 0 to 1) versus Distance(λ) (X-axis, 0 to 5). The graph includes three data series: 'Measured' (solid blue line), 'Lower' (dashed red line), and 'Upper' (dashed red line). The measured line starts at 1.0 at 0λ and decreases, reaching a minimum near 0.0 at 3.2λ, then slightly increases to about 0.15 at 5.0λ. The lower limit is at 0.0 for distances greater than 2λ. The upper limit is at 0.3 for distances greater than 2λ. + +Figure 6.3.2.2-4: Lab D: Doppler measurement results for CDL-C UMi at band n261 + +![Figure 6.3.2.2-5: Doppler measurement results for CDL-C UMi at band n261. The graph plots correlation (0.0 to 1.0) against distance (0 to 5). Three curves are shown: 'Measure' (red), 'Target' (blue), and 'current spec' (green). The 'current spec' curve drops to zero at distance 2. The 'Measure' and 'Target' curves drop to near zero at distance 4 and then rise slightly at distance 5.](a85105fd544c64ef624aa45c72378647_img.jpg) + +Figure 6.3.2.2-5 is a line graph showing Doppler measurement results for CDL-C UMi at band n261. The y-axis represents correlation, ranging from 0.0 to 1.0. The x-axis represents distance, ranging from 0 to 5. Three curves are plotted: 'Measure' (red line), 'Target' (blue line), and 'current spec' (green line). The 'current spec' curve starts at 1.0 at distance 0, drops sharply to 0.0 at distance 2, and remains at 0.0 for distances greater than 2. The 'Measure' and 'Target' curves start at 1.0 at distance 0, drop to a minimum of approximately 0.0 at distance 4, and then rise to approximately 0.1 at distance 5. + +| Distance | Measure | Target | current spec | +|----------|---------|--------|--------------| +| 0 | 1.0 | 1.0 | 1.0 | +| 1 | 0.4 | 0.4 | 0.4 | +| 2 | 0.2 | 0.2 | 0.0 | +| 3 | 0.15 | 0.15 | 0.0 | +| 4 | 0.0 | 0.0 | 0.0 | +| 5 | 0.1 | 0.1 | 0.0 | + +Figure 6.3.2.2-5: Doppler measurement results for CDL-C UMi at band n261. The graph plots correlation (0.0 to 1.0) against distance (0 to 5). Three curves are shown: 'Measure' (red), 'Target' (blue), and 'current spec' (green). The 'current spec' curve drops to zero at distance 2. The 'Measure' and 'Target' curves drop to near zero at distance 4 and then rise slightly at distance 5. + +Figure 6.3.2.2-5: Lab E: Doppler measurement results for CDL-C UMi at band n261 + +![Figure 6.3.2.2-6: Doppler measurement results for CDL-C UMi at 28GHz. The graph plots |correlation| (0 to 1) against Distance [λ] (0 to 5). Two curves are shown: 'Measured 12V' (blue) and 'Theoretical 12V' (orange). Both curves start at 1.0 at distance 0, drop to a minimum of approximately 0.1 at distance 4, and then rise slightly at distance 5.](b30a71a63c0093c8f54a2a57b1f601bb_img.jpg) + +Figure 6.3.2.2-6 is a line graph titled 'Temporal correlation at 28000 MHz Model: CDL-C\_UMi'. The y-axis represents |correlation|, ranging from 0 to 1. The x-axis represents Distance [ $\lambda$ ], ranging from 0 to 5. Two curves are plotted: 'Measured 12V' (blue line) and 'Theoretical 12V' (orange line). Both curves start at 1.0 at distance 0, drop to a minimum of approximately 0.1 at distance 4, and then rise slightly to approximately 0.15 at distance 5. + +| Distance [ $\lambda$ ] | Measured 12V | Theoretical 12V | +|------------------------|--------------|-----------------| +| 0 | 1.0 | 1.0 | +| 1 | 0.4 | 0.4 | +| 2 | 0.2 | 0.2 | +| 3 | 0.15 | 0.15 | +| 4 | 0.1 | 0.1 | +| 5 | 0.15 | 0.15 | + +Figure 6.3.2.2-6: Doppler measurement results for CDL-C UMi at 28GHz. The graph plots |correlation| (0 to 1) against Distance [λ] (0 to 5). Two curves are shown: 'Measured 12V' (blue) and 'Theoretical 12V' (orange). Both curves start at 1.0 at distance 0, drop to a minimum of approximately 0.1 at distance 4, and then rise slightly at distance 5. + +Figure 6.3.2.2-6: Lab F: Doppler measurement results for CDL-C UMi at 28GHz + +#### 6.3.2.3 PAS similarity percentage (PSP) + +The PAS measurement results of UMi CDL-C for band n261/28GHz are presented in Figures 6.3.2.3-1~6. The corresponding PSP values are summarized in Table 6.3.2.3-1. + +UMi\_CDL-C, fc = 28 GHz +PSP (Ref <-> Meas.): 91.4% + +![Two heatmaps comparing reference and measured PAS for CDL-C UMi at band n261. The left plot is 'Ref PAS seen by DUT' and the right is 'Meas. PAS seen by DUT'. Both show Elevation [deg] on the y-axis (-80 to 80) and Azimuth [deg] on the x-axis (-50 to 50).](ebd9fdefdb8b316d7bc166aa3ed924a3_img.jpg) + +Figure 6.3.2.3-1 displays two heatmaps comparing the Reference PAS (Power Azimuth Spectrum) seen by the DUT (Device Under Test) and the Measured PAS seen by the DUT for the CDL-C UMi scenario at band n261. The plots show Elevation [deg] on the Y-axis (ranging from -80 to 80) and Azimuth [deg] on the X-axis (ranging from -50 to 50). The color scale indicates power levels, with red/yellow representing higher power and blue/cyan representing lower power. The Reference PAS shows a broad, dominant peak centered around 0 degrees Azimuth and 0 degrees Elevation. The Measured PAS shows a similar overall structure but with more defined, sharper peaks and valleys, indicating better angular resolution or different scattering characteristics in the measurement environment. + +Two heatmaps comparing reference and measured PAS for CDL-C UMi at band n261. The left plot is 'Ref PAS seen by DUT' and the right is 'Meas. PAS seen by DUT'. Both show Elevation [deg] on the y-axis (-80 to 80) and Azimuth [deg] on the x-axis (-50 to 50). + +Figure 6.3.2.3-1: Lab A: PAS measurement results for CDL-C UMi at band n261 + +![Two heatmaps for Lab B PAS measurement results. (a) Ref. PAS Seen by DUT and (b) Measured PAS Seen by DUT. Both show Response vs. Angle [df].](8f7b458d3cc18ca96924473839d68ae6_img.jpg) + +Figure 6.3.2.3-2 displays two heatmaps showing the PAS measurement results for the CDL-C UMi scenario at band n261. Plot (a) shows the Reference PAS Seen by the DUT, and Plot (b) shows the Measured PAS Seen by the DUT. Both plots show the Response (Y-axis, ranging from -50 to 50) versus Angle [df] (X-axis, ranging from -80 to 80). The color scale indicates power levels, with red/yellow representing higher power and blue/cyan representing lower power. Both plots show a dominant peak centered around 0 degrees Azimuth and 0 degrees Elevation, with the measured result (b) showing more pronounced side lobes and nulls compared to the reference result (a). + +Two heatmaps for Lab B PAS measurement results. (a) Ref. PAS Seen by DUT and (b) Measured PAS Seen by DUT. Both show Response vs. Angle [df]. + +Figure 6.3.2.3-2: Lab B: PAS measurement results for CDL-C UMi at band n261 + +![Heatmap of Measured PAS of CDL-C UMi. Shows Response vs. phi. Color scale ranges from -50 to 0.](0cda1f4c603972dc23aefc2cc3cbd135_img.jpg) + +Figure 6.3.2.3-3 displays the Measured PAS of the CDL-C UMi scenario at band n261. The plot shows the Response (Y-axis, ranging from -80 to 80) versus $\phi$ (X-axis, ranging from -80 to 80). The color scale indicates power levels, with red/yellow representing higher power and blue/cyan representing lower power. The measured PAS shows a broad, dominant peak centered around 0 degrees Azimuth and 0 degrees Elevation, with some secondary peaks visible at higher elevation angles. + +Heatmap of Measured PAS of CDL-C UMi. Shows Response vs. phi. Color scale ranges from -50 to 0. + +Figure 6.3.2.3-3: Lab C: PAS measurement results for CDL-C UMi at band n261 + +![Heatmap (a) showing Ref. PAS Seen by DUT. The plot shows power density across a grid of theta (0 to 90) and phi (-90 to 90). A color bar on the right indicates values from 0 to -35 dB.](0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg) + +Heatmap (a) showing Ref. PAS Seen by DUT. The plot shows power density across a grid of theta (0 to 90) and phi (-90 to 90). A color bar on the right indicates values from 0 to -35 dB. + +(a) Ref. PAS Seen by DUT + +![Heatmap (b) showing Measured PAS Seen by DUT. The plot shows power density across a grid of theta (0 to 90) and phi (-90 to 90). A color bar on the right indicates values from 0 to -45 dB.](3a310163273edcf70c19269a06d0cdf2_img.jpg) + +Heatmap (b) showing Measured PAS Seen by DUT. The plot shows power density across a grid of theta (0 to 90) and phi (-90 to 90). A color bar on the right indicates values from 0 to -45 dB. + +(b) Measured PAS Seen by DUT + +Figure 6.3.2.3-4: Lab D: PAS measurement results for CDL-C UMi at band n261 + +![Heatmap showing PAS measurement results for Lab E. The plot shows power density across a grid of Zenith [deg] (0.0 to 180.0) and Azimuth [deg] (-90.0 to 90.0).](e046996962d6740cf050a5640e0c6b40_img.jpg) + +Heatmap showing PAS measurement results for Lab E. The plot shows power density across a grid of Zenith [deg] (0.0 to 180.0) and Azimuth [deg] (-90.0 to 90.0). + +Figure 6.3.2.3-5: Lab E: PAS measurement results for CDL-C UMi at band n261 + +![Comparison of Ref PAS seen by DUT and Meas. PAS seen by DUT. Both plots show power density across a grid of Elevation [deg] (-80 to 80) and Azimuth [deg] (-50 to 50).](52f284e10be4323639b32fdd60e463db_img.jpg) + +Reference vs. Measured, CDL-C UMi, PSP = 90.9% + +Comparison of Ref PAS seen by DUT and Meas. PAS seen by DUT. Both plots show power density across a grid of Elevation [deg] (-80 to 80) and Azimuth [deg] (-50 to 50). + +Figure 6.3.2.3-6: Lab F: PAS measurement results for CDL-C UMi at band n261 + +**Table 6.3.2.3-1: PSP verification results for CDL-C UMi, band n261** + +| Lab | PSP value | Pass/fail limit | +|-------|-----------|-----------------| +| Lab A | 91.4% | 84% | +| Lab B | 89.7% | | +| Lab C | 94% | | +| Lab D | 86.2% | | +| Lab E | 91.3% | | +| Lab F | 90.9% | | + +#### 6.3.2.4 Cross-polarization + +The Cross-polarization measurement results of UMi CDL-C for bands n261/28GHz are presented in Table 6.3.2.4-1~5. + +**Table 6.3.2.4-1: Lab A: Cross-polarization verification results for CDL-C UMi, band n261** + +| Beam | Reference | Measurement result | Delta | Pass/fail limit | +|--------|-------------------------|--------------------|---------|-----------------| +| Beam 1 | Input 1: V/H = -0.45 dB | V/H = -0.38 dB | 0.07 dB | $\pm 1.5$ dB | +| | Input 2: V/H = 0.49 dB | V/H = 0.76 dB | 0.27 dB | | +| | Input 1+2: V/H = 0 dB | V/H = 0.44dB | 0.44 dB | | + +**Table 6.3.2.4-2: Lab B: Cross-polarization verification results for CDL-C UMi, band n261** + +| Beam | Reference | Measurement result | Delta | Pass/fail limit | +|--------|-------------------------|--------------------|----------|-----------------| +| Beam 1 | Input 1: V/H = -0.45 dB | V/H = -0.70 dB | -0.25 dB | $\pm 1.5$ dB | +| | Input 2: V/H = 0.49 dB | V/H = 1.27 dB | 0.78 dB | | +| | Input 1+2: V/H = 0 dB | V/H = -0.23dB | -0.23 dB | | + +**Table 6.3.2.4-3: Lab C: Cross-polarization verification results for CDL-C UMi, band n261** + +| Beam | Reference | Measurement result | Delta | Pass/fail limit | +|--------|-------------------------|--------------------|----------|-----------------| +| Beam 1 | Input 1: V/H = -0.45 dB | V/H = 1.01 dB | 1.46 dB | $\pm 1.5$ dB | +| | Input 2: V/H = 0.49 dB | V/H = -0.51 dB | -1.00 dB | | + +**Table 6.3.2.4-4: Lab D: Cross-polarization verification results for CDL-C UMi, band n261** + +| Beam | Reference | Measurement result | Delta | Pass/fail limit | +|--------|-----------------------|--------------------|----------|-----------------| +| Beam 1 | Input 1+2: V/H = 0 dB | V/H = -0.28dB | -0.28 dB | $\pm 1.5$ dB | + +**Table 6.3.2.4-5: Lab E: Cross-polarization verification results for CDL-C UMi, band n261** + +| Beam | Reference | Measurement result | Delta | Pass/fail limit | +|--------|-------------------------|--------------------|----------|-----------------| +| Beam 1 | Input 1: V/H = -0.45 dB | V/H = -0.80 dB | -0.35 dB | $\pm 1.5$ dB | +| | Input 2: V/H = 0.49 dB | V/H = 1.01 dB | 0.52 dB | | +| | Input 1+2: V/H = 0 dB | V/H = 0.76 dB | 0.76 dB | | + +#### 6.3.2.5 Power validation + +The Power validation results of UMi CDL-C for bands n261 are presented in Table 6.3.2.5-1~4. + +**Table 6.3.2.5-1: Lab A: Power validation results for CDL-C UMi, band n261 (Unit: dBm/120kHz)** + +| Band | Measured EPRE | Target EPRE | Delta | Pass/fail limit | +|------|---------------|-------------|-------|-----------------| +| n261 | -74.3 | -74 | -0.3 | $\pm 1.5$ dB | + +**Table 6.3.2.5-2: Lab B: Power validation results for CDL-C UMi, band n261 (Unit: dBm/120kHz)** + +| Band | Measured V power | Measured H power | Measured total power | Target power | Delta | Pass/fail limit | +|------|------------------|------------------|----------------------|--------------|--------|-----------------| +| n261 | -110.314 | -110.807 | -107.543 | -107 | -0.543 | $\pm 1.5$ dB | + +**Table 6.3.2.5-3: Lab C: Power validation results for CDL-C UMi, band n261 (Unit: dBm/120kHz)** + +| Band | Measured power | Target power | Delta | Pass/fail limit | +|------|----------------|--------------|-------|-----------------| +| n261 | -43.96 | -43.18 | -0.78 | $\pm 1.5$ dB | + +**Table 6.3.2.5-4: Lab E: Power validation results for CDL-C UMi, band n261 (Unit: dBm/120kHz)** + +| Band | Measured power | Target power | Delta | Pass/fail limit | +|------|----------------|--------------|-------|-----------------| +| n261 | -42.16 | -42.84 | 0.68 | $\pm 1.5$ dB | + +# 7 Lab alignment of FR1 MIMO OTA + +## 7.1 General + +To establish valid and trustable measurement data pools for defining FR1 MIMO OTA requirements, lab alignment campaigns are required before measurement campaign for ensuring there is no unexpected deviations among labs. 3GPP RAN4 performed a lab alignment campaign for bands > 1GHz during Rel-17, and a lab alignment campaign for bands < 1GHz during Rel-18. + +## 7.2 Noise impact in MPAC on MIMO performance + +This clause includes analysis and experimental measurement results of the impact of noise in MPAC on FR1 MIMO OTA performance. + +During Rel-18, several companies studied the impact of noise in MPAC on FR1 MIMO OTA performance, conducted experiments, and obtained similar observations. It was found that by adding suitable attenuators after the amplifiers in MPAC system, the impact of noise can be eliminated and the MIMO OTA measurement results can be corrected, as shown in Figure 7.2-1. + +![Figure 7.2-1: Measurement setup for correcting FR1 MIMO OTA test results with MPAC. The diagram shows a signal flow from a Base Station Simulator to a Channel Fading Emulator, then to Amplifiers, and finally to an Attenuator. Downlink signals are sent from the Attenuator into an Anechoic Chamber containing a Device Under Test (DUT) within a 20cm diameter test zone. Uplink signals are received from the DUT and sent back to the Base Station Simulator.](0f26e70157bd4c45f825795cdcd20fbd_img.jpg) + +Figure 7.2-1: Measurement setup for correcting FR1 MIMO OTA test results with MPAC. The diagram shows a signal flow from a Base Station Simulator to a Channel Fading Emulator, then to Amplifiers, and finally to an Attenuator. Downlink signals are sent from the Attenuator into an Anechoic Chamber containing a Device Under Test (DUT) within a 20cm diameter test zone. Uplink signals are received from the DUT and sent back to the Base Station Simulator. + +**Figure 7.2-1: Measurement setup for correcting FR1 MIMO OTA test results with MPAC** + +The measurement results (12 orientations average in FS DMP mode) at bands n28 (780.5MHz) and n41 (2593MHz) obtained by Lab 1 are shown in Figure 7.2-2. The same DUT were measured with different attenuation values. It can be observed that, as the attenuation value increases, the measurement results first get better and then become stable. At the lower frequency, the effect of the attenuation value is more obvious, and it requires a larger attenuation to make the measurement results stable. The reason is that at lower frequency, the path loss from the amplifier output to the chamber centre is smaller, and when the amplifier noise arrives at the chamber centre, it has higher power than that at higher frequency. + +Adding attenuators after the amplifiers can reduce the noise and make it neglectable for FR1 MIMO OTA testing. A suitable attenuation value can be selected, e.g., for band n28, the measurement results with 20dB-attenuation and 30dB-attenuation are almost the same, but the measurement result with 10dB-attenuation is worse, which means 20dB-attenuation is enough for band n28 in Lab 1's MPAC system. + +![Figure 7.2-2(a): Measured MIMO OTA performance for Band n28 (780.5MHz). The graph plots Throughput (Mbps) on the y-axis (15 to 45) against Normalized RS EPRE (dBm/15 kHz) on the x-axis (-10 to 0). Four curves are shown: 0dB attenuation (blue dashed), 10dB attenuation (green dashed), 20dB attenuation (red solid), and 30dB attenuation (black dotted). A horizontal dashed line at approximately 28 Mbps indicates the 70% TP level. The 20dB and 30dB curves reach the 70% TP level around -6 dBm, while the 10dB curve reaches it around -4 dBm.](8ba0063bcb9cdac03f1c4497526f1898_img.jpg) + +Figure 7.2-2(a): Measured MIMO OTA performance for Band n28 (780.5MHz). The graph plots Throughput (Mbps) on the y-axis (15 to 45) against Normalized RS EPRE (dBm/15 kHz) on the x-axis (-10 to 0). Four curves are shown: 0dB attenuation (blue dashed), 10dB attenuation (green dashed), 20dB attenuation (red solid), and 30dB attenuation (black dotted). A horizontal dashed line at approximately 28 Mbps indicates the 70% TP level. The 20dB and 30dB curves reach the 70% TP level around -6 dBm, while the 10dB curve reaches it around -4 dBm. + +**(a) Band n28 (780.5MHz)** + +![Figure 7.2-2(b): Measured MIMO OTA performance for Band n41 (2593MHz). The graph plots Throughput (Mbps) on the y-axis (40 to 160) against Normalized RS EPRE (dBm/30 kHz) on the x-axis (-10 to 0). Three curves are shown: 0dB attenuation (blue dashed), 10dB attenuation (green dashed), and 20dB attenuation (red solid). A horizontal dashed line at approximately 95 Mbps indicates the 70% TP level. All three curves reach the 70% TP level around -6 dBm, showing less difference between attenuation values compared to band n28.](b5c525e7df912952586920ac3d3e4c57_img.jpg) + +Figure 7.2-2(b): Measured MIMO OTA performance for Band n41 (2593MHz). The graph plots Throughput (Mbps) on the y-axis (40 to 160) against Normalized RS EPRE (dBm/30 kHz) on the x-axis (-10 to 0). Three curves are shown: 0dB attenuation (blue dashed), 10dB attenuation (green dashed), and 20dB attenuation (red solid). A horizontal dashed line at approximately 95 Mbps indicates the 70% TP level. All three curves reach the 70% TP level around -6 dBm, showing less difference between attenuation values compared to band n28. + +**(b) Band n41 (2593MHz)** + +**Figure 7.2-2: Measured MIMO OTA performance with different attenuation values (in Lab 1)** + +Figures 7.2-3 and 7.2-4 present the measurement results at band n28 (780.5MHz) from Lab 2 and Lab 4. Similar phenomenon can be observed. + +![Figure 7.2-3: Measured MIMO OTA performance at band n28 (780.5MHz) with different attenuation values (in Lab 2). The graph plots Throughput (Mbps) on the y-axis (20 to 40) against Normalized RS EPRE (dBm/15kHz) on the x-axis (-20 to 0). Four curves are shown for 0dB, 10dB, 20dB, and 30dB attenuation. A dashed horizontal line at 28 Mbps indicates the 70% Throughput level.](9f92854fe6ecaf47760515c891a4fccc_img.jpg) + +Figure 7.2-3: Measured MIMO OTA performance at band n28 (780.5MHz) with different attenuation values (in Lab 2). The graph plots Throughput (Mbps) on the y-axis (20 to 40) against Normalized RS EPRE (dBm/15kHz) on the x-axis (-20 to 0). Four curves are shown for 0dB, 10dB, 20dB, and 30dB attenuation. A dashed horizontal line at 28 Mbps indicates the 70% Throughput level. + +**Figure 7.2-3: Measured MIMO OTA performance at band n28 (780.5MHz) with different attenuation values (in Lab 2)** + +![Figure 7.2-4: Measured MIMO OTA performance at band n28 (780.5MHz) with different attenuation values (in Lab 4). The graph plots Normalized Tput (Mbps) on the y-axis (0.2 to 1.2) against Normalized RS epre (dBm/15kHz) on the x-axis (-13 to -1). Four curves are shown for 0dB, 10dB, 20dB, and 30dB attenuation. A dashed horizontal line at 0.7 indicates the 0.7 max Tput level.](73e5c1369b67ddccf657e54d0434cc2b_img.jpg) + +Figure 7.2-4: Measured MIMO OTA performance at band n28 (780.5MHz) with different attenuation values (in Lab 4). The graph plots Normalized Tput (Mbps) on the y-axis (0.2 to 1.2) against Normalized RS epre (dBm/15kHz) on the x-axis (-13 to -1). Four curves are shown for 0dB, 10dB, 20dB, and 30dB attenuation. A dashed horizontal line at 0.7 indicates the 0.7 max Tput level. + +**Figure 7.2-4: Measured MIMO OTA performance at band n28 (780.5MHz) with different attenuation values (in Lab 4)** + +Table 7.2-1 presents the measurement results at band n28 (780.5MHz) from Lab 6, RS EPRE difference between FR1 MIMO OTA system with and without 10dB attenuators are listed. + +**Table 7.2-1: Measured RS EPRE difference between FR1 MIMO OTA system with and without 10dB attenuators at band n28 (780.5MHz) in Lab 6** + +| Percentile of max TP | RS EPRE $\Delta$ between FR1 MIMO OTA system with and without 10dB attenuators | +|----------------------|--------------------------------------------------------------------------------| +| @ 50% throughput | 0.59 dB | +| @ 70% throughput | 0.66 dB | +| @ 90% throughput | 0.67 dB | + +Based on the observations, RAN4 reached the following agreements: + +- Labs should first exclude the impact of noise before performing MIMO OTA measurements, especially for frequency bands <1GHz. +- Perform a low-band lab alignment activity at Band n28, to cross-validate the measurement results from different labs and ensure the validity of the data pool for requirements definition. + +## 7.3 Lab alignment campaign for frequency bands > 1GHz + +### 7.3.1 Framework + +This clause defines the working procedure on how to proceed the lab alignment campaign for frequency bands > 1GHz. + +Labs/companies volunteer to participate in the performance requirement part shall complete the lab alignment measurements and system validation measurements, results should be submitted to RAN4 for review. + +Using the testing conditions as defined in TS38.151. + +The test bands for lab alignment are n41 and n78. Three performance alignment devices (PADs) for each band should be tested to ensure the alignment of measurement results. + +TRMS value in SA mode will be used for alignment comparison. + +The reference value of each PAD should be the average of the PAD measurement results submitted on or before 12:00 UTC 30th April 2022, based on the condition at least 3 labs' results collected. Submission with measurement data after 12:00 UTC 30th April can be considered for lab alignment, but will not change the reference TRMS value. + +The acceptance criteria for declaring alignment should be defined based on the preliminary MU value of MPAC system. The detailed criteria for accepting the outcome of the lab alignment activity are listed in Table 7.3.3-1. + +**Table 7.3.3-1: Requirements for lab alignment results (FR1 MIMO OTA)** + +| Band | Case | Acceptance criteria | +|------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| n41 | PAD_1 | The deviation between the measurement result and the reference value of each PAD shall be less than the pass/fail limit, i.e., $ \text{TRMS}_{\text{average},70\_\text{mea}} - \text{TRMS}_{\text{average},70\_\text{ref}} \leq \text{pass/fail limit}$ | +| | PAD_2 | | +| | PAD_3 | | +| n78 | PAD_1 | The deviation between the measurement result and the reference value of each PAD shall be less than the pass/fail limit, i.e., $ \text{TRMS}_{\text{average},70\_\text{mea}} - \text{TRMS}_{\text{average},70\_\text{ref}} \leq \text{pass/fail limit}$ | +| | PAD_2 | | +| | PAD_3 | | + +Note: + +- The PAD measurement results shall NOT be shared to anyone before submitting to RAN4 meetings or sharing in the NR MIMO OTA reflector. Comparison and alignment analyses should only be done in RAN4 meetings. +- Three PADs for each band are selected. Labs should submit PAD measurements results in an anonymous approach, i.e., the PADs for each band should be marked as PAD\_1, PAD\_2, and PAD\_3, respectively. The mapping between the codename PAD\_n and the actual PAD shall only be known among the labs participated in the alignment activity, and shall NOT be disclosed to any other companies. + +### 7.3.2 Measurement results + +RAN4 carried out the lab alignment campaign for frequency bands > 1GHz during Rel-17. Considering the test burden and urgent timeline, RAN4 decided to select three smartphones (named as PADs, Performance Alignment Devices) as reference DUTs, and select two bands, n41 and n78, to perform FR1 MIMO OTA lab alignment activity for frequencies bands > 1GHz. + +There are 6 test labs participated in the lab alignment campaign, the reference value of each PAD at each band is derived based on linear average (with dBm) of PAD measurement results submitted by all labs. The summary of the lab alignment results is shown in Table 7.3.2-1 and Figure 7.3.2-1. The TRMS offset between each measurement result and reference value of FR1 MIMO OTA lab alignment is shown in Table 7.3.2-2 and Figure 7.3.2-1. + +**Table 7.3.2-1: Summary of FR1 MIMO OTA lab alignment results for bands > 1GHz** + +| Device | Band | TRMS measurement result [dBm/30kHz] | | | | | | Average approach | Reference value | Max-Min deviation | +|-----------|------|-------------------------------------|--------|---------|--------|--------|---------|------------------|-----------------|-------------------| +| | | Lab 1 | Lab 2 | Lab 3 | Lab 4 | Lab 5 | Lab 6 | | | | +| PAD_n41_1 | n41 | -96.43 | -97.61 | -98.20 | -97.45 | -96.88 | -99.10 | Linear average | -97.61 | 2.67 | +| PAD_n41_2 | n41 | -99.30 | -97.80 | -100.02 | -99.96 | -99.62 | -101.43 | | -99.69 | 3.63 | +| PAD_n41_3 | n41 | -96.31 | -97.39 | -97.81 | -96.53 | -96.74 | -98.59 | | -97.23 | 2.28 | +| PAD_n78_1 | n78 | -96.02 | -96.54 | -96.44 | -96.10 | -96.53 | -98.38 | | -96.67 | 2.36 | +| PAD_n78_2 | n78 | -95.42 | -95.95 | -96.11 | -96.48 | -96.66 | -98.97 | | -96.60 | 3.55 | +| PAD_n78_3 | n78 | -99.06 | -97.42 | -99.53 | -99.08 | -99.54 | NA | | -98.93 | 2.12 | + +Table 7.3.2-2: FR1 MIMO OTA lab alignment outcome - TRMS offset (for bands > 1GHz) + +| Device | Band | TRMS offset from reference [dBm/30kHz] | | | | | | Pass/fail limit | +|--------------------------|------|----------------------------------------|-------|-------|-------|-------|-------|--------------------------------| +| | | Lab 1 | Lab 2 | Lab 3 | Lab 4 | Lab 5 | Lab 6 | | +| PAD_n41_1 | n41 | 1.18 | 0.00 | -0.59 | 0.16 | 0.73 | -1.49 | +/- 0.75 MU, i.e., +/- 2.25 dB | +| PAD_n41_2 | n41 | 0.39 | 1.89 | -0.33 | -0.27 | 0.07 | -1.74 | | +| PAD_n41_3 | n41 | 0.92 | -0.16 | -0.58 | 0.70 | 0.49 | -1.36 | | +| PAD_n78_1 | n78 | 0.65 | 0.13 | 0.22 | 0.57 | 0.14 | -1.71 | +/- 0.75 MU, i.e., +/- 2.55 dB | +| PAD_n78_2 | n78 | 1.18 | 0.65 | 0.48 | 0.12 | -0.06 | -2.37 | | +| PAD_n78_3 | n78 | -0.13 | 1.51 | -0.60 | -0.15 | -0.61 | NA | | +| Lab alignment conclusion | | Pass | Pass | Pass | Pass | Pass | Pass | | + +![Bar chart showing TRMS measurement results for six devices across six labs. The y-axis ranges from -101.43 to -95.42 dBm/30kHz. The x-axis lists devices PAD_n41_1, PAD_n41_2, PAD_n41_3, PAD_n78_1, PAD_n78_2, and PAD_n78_3. Each device has six bars representing Lab 1 to Lab 6. Data labels are provided above each bar.](5314dd284c2a98c866862ee0f0fee301_img.jpg) + +MIMO OTA lab alignment — TRMS measurement results [dBm/30kHz] + +| Device | Lab 1 | Lab 2 | Lab 3 | Lab 4 | Lab 5 | Lab 6 | +|-----------|--------|--------|---------|--------|--------|---------| +| PAD_n41_1 | -96.43 | -97.61 | -98.20 | -97.45 | -96.88 | -99.10 | +| PAD_n41_2 | -99.30 | -97.80 | -100.02 | -99.96 | -99.62 | -101.43 | +| PAD_n41_3 | -96.31 | -97.39 | -97.81 | -96.53 | -96.74 | -98.59 | +| PAD_n78_1 | -96.02 | -96.54 | -96.44 | -96.10 | -96.53 | -98.38 | +| PAD_n78_2 | -95.42 | -95.95 | -96.11 | -96.48 | -96.66 | -98.97 | +| PAD_n78_3 | -99.06 | -97.42 | -99.53 | -99.08 | -99.54 | NA | + +Bar chart showing TRMS measurement results for six devices across six labs. The y-axis ranges from -101.43 to -95.42 dBm/30kHz. The x-axis lists devices PAD\_n41\_1, PAD\_n41\_2, PAD\_n41\_3, PAD\_n78\_1, PAD\_n78\_2, and PAD\_n78\_3. Each device has six bars representing Lab 1 to Lab 6. Data labels are provided above each bar. + +Figure 7.3.2-1: Measurement results of FR1 MIMO OTA lab alignment for bands > 1GHz + +![Bar chart showing TRMS offset from reference for six devices across six labs. The y-axis ranges from -3.0 to 3.0 dBm/30kHz. The x-axis lists devices PAD_n41_1, PAD_n41_2, PAD_n41_3, PAD_n78_1, PAD_n78_2, and PAD_n78_3. Each device has six bars representing Lab 1 to Lab 6. Data labels are provided above each bar.](d4852169b63bedb68b1f3c5b3b9b0cc0_img.jpg) + +MIMO OTA lab alignment — TRMS offset [dBm/30kHz] + +| Device | Lab 1 | Lab 2 | Lab 3 | Lab 4 | Lab 5 | Lab 6 | +|-----------|-------|-------|-------|-------|-------|-------| +| PAD_n41_1 | 1.18 | 0.00 | -0.59 | 0.16 | 0.73 | -1.49 | +| PAD_n41_2 | 0.39 | 1.89 | -0.33 | -0.27 | 0.07 | -1.74 | +| PAD_n41_3 | 0.92 | -0.16 | -0.58 | 0.70 | 0.49 | -1.36 | +| PAD_n78_1 | 0.65 | 0.13 | 0.22 | 0.57 | 0.14 | -1.71 | +| PAD_n78_2 | 1.18 | 0.65 | 0.48 | 0.12 | -0.06 | -2.37 | +| PAD_n78_3 | -0.13 | 1.51 | -0.60 | -0.15 | -0.61 | NA | + +Bar chart showing TRMS offset from reference for six devices across six labs. The y-axis ranges from -3.0 to 3.0 dBm/30kHz. The x-axis lists devices PAD\_n41\_1, PAD\_n41\_2, PAD\_n41\_3, PAD\_n78\_1, PAD\_n78\_2, and PAD\_n78\_3. Each device has six bars representing Lab 1 to Lab 6. Data labels are provided above each bar. + +Figure 7.3.2-2: Deviation between each measurement result and reference value of FR1 MIMO OTA lab alignment for bands > 1GHz + +### 7.3.3 Pass/fail limits + +Based on the preliminary MU assessment of FR1 MPAC system in Annex A.2.5 of TS 38.151, and lab alignment measurement results in Clause 7.3.2, RAN4 decided the final pass/fail limits for FR1 MIMO OTA lab alignment activity for bands > 1GHz as 0.75\* preliminary MU, i.e., + +- < 3GHz: 2.25 dB +- > 3GHz: 2.55 dB + +### 7.3.4 Conclusion + +RAN4 concluded the successful FR1 MIMO OTA lab alignment activity for bands > 1GHz, all the 6 test labs are aligned. FR1 MIMO OTA performance requirements for bands > 1GHz are specified based on the measurement results submitted by the above aligned test labs. + +## 7.4 Lab alignment campaign for frequency bands < 1GHz + +### 7.4.1 Framework + +This clause defines the working procedure on how to proceed the lab alignment campaign for frequency bands < 1GHz. + +1. Test labs are invited to participate in the lab alignment activity, the following conditions should be fulfilled : + - At least 3 participating labs are required. + - Participating labs shall complete channel model validation. + - Participating labs should have sufficient test resource to provide on-time measurement results without delay. + - Participating labs should first examine and exclude the impact of noise before submitting PAD measurement results. +2. Test methodology: + - Test plan: 3GPP TS 38.151 + - Test system: MPAC +3. Test cases for Lab Alignment Activity: + - Test band: n28 + - Number of test cases: 3 PADs + - Operation mode: NR Standalone (SA) + - Use scenario: Free space +4. Test results submission: + - Use the same worksheet template in R4-2316308 to submit the measurement results + - The measurement results should be submitted to RAN4 by anonymous approach (the UE model shall not be disclosed publicly) + - Results shall not be shared between labs before submitting to RAN4 meetings or sharing in the RAN4 reflector. Comparison and lab alignment analysis should only be done in RAN4 meetings/discussions +5. Lab alignment criteria: + - The pass/fail criteria are defined as the maximum deviation between the measurement result and the reference value + +- The reference value will be derived based on the averaging approach (linear average in dBm) of lab alignment data pool from $\geq 3$ labs +- Apparent outliers (if identified) will not be considered in the average process for reference value. The PAD measurement result deviates over $1.5 \times \text{preliminary MU}$ (i.e., 4.55dB) from all the other labs' results should be identified as apparent outlier. +- Pass/fail limit for lab alignment should be defined as $X \times \text{preliminary MU}$ (X is TBD) as baseline. + +#### 6. Volunteer lab procedures: + +- PAD delivery scheme: Decide PAD delivery scheme after all the volunteer labs and PADs information being confirmed. +- PAD measurement time in each volunteer lab: finalize PAD measurement within [7] workdays, and deliver to the next lab ASAP with PAD delivery In/Out information shared in email-reflector. + +### 7.4.2 Measurement results + + + +### 7.4.3 Pass/fail limits + + + +### 7.4.4 Conclusion + + + +# --- 8 Lab alignment of FR2 MIMO OTA + +## 8.1 Framework + +This clause defines the working procedure on how to proceed the FR2 MIMO OTA lab alignment campaign. The purpose of lab alignment activity is to ensure there is no unexpected lab deviation and establish full trust and confidence on the measurement data pool for specifying FR2 MIMO OTA performance requirements. + +1. Test labs are invited to participate in the lab alignment activity, the following conditions should be fulfilled: + - At least 3 participating labs are required. + - Participating labs shall complete channel model validation. + - Participating labs should have sufficient test resource to provide on-time measurement results without delay. + - Each lab should finalize PAD measurement within 10 workdays, and deliver to the next lab in the same country ASAP with PAD In/Out information shared via email-reflector; otherwise, labs in the same country should equally share the period for testing the PADs. +2. Test methodology: + - Test plan: 3GPP TS 38.151 +3. Test cases for Lab Alignment Activity: + - Test band: n261 (for PADs that support n261), n257 (for the PAD that does not support n261) + +- Number of test cases: 2~4 PADs per-band + - Operation mode: NR Non-Standalone (NSA) is preferred and SA is not precluded, and should be mapped with the measurement results submission. + - Power class: PC3 +4. Test results submission: +- Use the same worksheet template in R4-2308740 to submit the measurement results + - The measurement results should be submitted to RAN4 by anonymous approach (the UE model shall not be disclosed publicly) + - Results shall not be shared between labs before submitting to RAN4 meetings or sharing in the RAN4 reflector. Comparison and lab alignment analysis should only be done in RAN4 meetings/discussions +5. Lab alignment criteria: +- The pass/fail criteria are defined as the maximum deviation between the MASC measurement result and the reference value + - The reference value is derived based on the per-band averaging approach of lab alignment data pool from $\geq 3$ labs, whether apparent outliers will be considered in averaging process, or not, is FFS + - Pass/fail limit for lab alignment should be derived from the preliminary MU value. Adopt $[0.5-1] * \text{preliminary MU}$ as starting point and further check after the FR2 MU is decided and some PAD measurement results are available. + +## 8.2 Measurement results + + + +## 8.3 Pass/fail limits + + + +## 8.4 Conclusion + + + +# Annex A: Change history + +| Change history | | | | | | | | +|----------------|-----------|------------|----|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-10 | R4#108bis | R4-2316704 | | | | Skeleton of TR38.761 on Measurement of NR MIMO OTA performance | 0.0.1 | +| 2023-11 | R4#109 | R4-2319164 | | | | R4-2316946 TP to TR 38.761 on channel model validation for n41 n78
R4-2316968 TP to TR 38.761 on lab alignment for bands > 1GHz | 0.1.0 | +| 2023-11 | R4#109 | R4-2320179 | | | | R4-2321107 TP to TR 38.761 on Lab 6 Power Validation
R4-2320060 TP to TR 38.761 on General Aspects and Measurement Setup
R4-2320062 TP to TR 38.761 on FR2 channel model validation
R4-2318895 TP for TR 38.761 on channel model validation for n78 and n41
R4-2320061 TP to TR 38.761 on channel model validation for n28
R4-2321108 TP to TR 38.761 on FR1 noise impact
R4-2320064 TP to TR 38.761 on Rel-18 lab alignment framework | 0.2.0 | +| 2023-12 | RAN#102 | RP-23xxxxx | | | | Presented to RAN for approval | 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/38_series/38835/07f537f57749b75157f742525e6a8dbc_img.jpg b/marked/Rel-18/38_series/38835/07f537f57749b75157f742525e6a8dbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62ab3c69409cf5069465f3671f63a9d102195f34 --- /dev/null +++ b/marked/Rel-18/38_series/38835/07f537f57749b75157f742525e6a8dbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a76b37f1dfad02d0acc18bd147c890043bc542882c6de8c11e3cd02e7a205573 +size 10468 diff --git a/marked/Rel-18/38_series/38835/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38835/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5ee10d2b206ea0f3276b5a18ade81035d74e757 --- /dev/null +++ b/marked/Rel-18/38_series/38835/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aac18b87d7827291573c41bcb4be4e6dabf29f71c717104e89cc223263134615 +size 10527 diff --git a/marked/Rel-18/38_series/38835/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38835/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e6c3a73def83062420fb682a3c01e5171b731be --- /dev/null +++ b/marked/Rel-18/38_series/38835/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0979e0723a1da51bed5aac63c9e90ca3ba07874980a5104cd592e94e4ba0a83d +size 6500 diff --git a/marked/Rel-18/38_series/38835/d17f75945bbb3feb84a153ecfedb9b81_img.jpg b/marked/Rel-18/38_series/38835/d17f75945bbb3feb84a153ecfedb9b81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f59c5a8db3c96428c50243545bdc67993f697c5 --- /dev/null +++ b/marked/Rel-18/38_series/38835/d17f75945bbb3feb84a153ecfedb9b81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c42f49981d9ff6b00f0d849ffbff6d67f809c42e0341655943ec8eb4704fb64b +size 44213 diff --git a/marked/Rel-18/38_series/38835/d3f6de4fe9f9138fc6afc584b5104433_img.jpg b/marked/Rel-18/38_series/38835/d3f6de4fe9f9138fc6afc584b5104433_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d514cdf09b0af132fc17e5445f19c999a14456b --- /dev/null +++ b/marked/Rel-18/38_series/38835/d3f6de4fe9f9138fc6afc584b5104433_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a46d9a8b388fececeb7859082ff34e514664c11dcd51dd99c07aadcfaaa9c8e5 +size 12776 diff --git a/marked/Rel-18/38_series/38835/raw.md b/marked/Rel-18/38_series/38835/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9c958b6aeeaeb34e7294d78738005bb2489515fe --- /dev/null +++ b/marked/Rel-18/38_series/38835/raw.md @@ -0,0 +1,3525 @@ + + +# **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Study on XR enhancements for 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 capital 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' in smaller 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..... | 5 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms, symbols and abbreviations..... | 8 | +| 3.1 Terms..... | 8 | +| 3.2 Abbreviations..... | 8 | +| 4 Introduction to Extended Reality..... | 9 | +| 4.1 Extended Reality Types..... | 9 | +| 4.2 Human Perception and Tracking..... | 9 | +| 4.3 Capture, Encoding and Delivery..... | 10 | +| 4.3.1 Video..... | 10 | +| 4.3.2 Audio..... | 11 | +| 4.4 XR Engines and Rendering..... | 11 | +| 4.5 Characteristics and Requirements..... | 11 | +| 4.5.1 General..... | 11 | +| 4.5.2 Video..... | 12 | +| 4.5.3 Audio..... | 12 | +| 4.5.4 Pose Information..... | 12 | +| 5 XR Enhancements for NR..... | 13 | +| 5.1 XR Awareness..... | 13 | +| 5.1.1 General..... | 13 | +| 5.1.2 Layer 2 Structure..... | 14 | +| 5.2 Power Saving Techniques..... | 15 | +| 5.2.1 Physical Layer Enhancements..... | 15 | +| 5.2.2 Layer 2 Enhancements..... | 15 | +| 5.3 Capacity Improvements Techniques..... | 15 | +| 5.3.1 Physical Layer Enhancements..... | 15 | +| 5.3.2 Layer 2 Enhancements..... | 15 | +| 6 Conclusions..... | 16 | +| Annex A (informative): Evaluation Methodology..... | 17 | +| Annex B (informative): Evaluation Studies..... | 18 | +| B.1 Capacity performance evaluation results..... | 18 | +| B.1.1 Multi-PDSCH scheduling by a single DCI..... | 18 | +| B.1.2 Cooperative MIMO via DL interference probing based on SRS enhancement..... | 21 | +| B.1.3 Enhanced CQI for CBG-based transmissions..... | 23 | +| B.1.4 Enhanced CQI based on DMRS..... | 25 | +| B.1.5 Soft HARQ-ACK enhancements..... | 27 | +| B.1.6 Configured grant scheduling..... | 29 | +| B.1.7 Scheduling restrictions due to RRM measurements..... | 39 | +| B.1.8 Buffer status report..... | 42 | +| B.1.9 UL delay-aware scheduling..... | 43 | +| B.1.10 XR-specific playoutDelayForMediaStartup for gNB scheduling awareness..... | 44 | +| B.2 Power saving performance evaluation results..... | 46 | +| B.2.1 Enhanced CDRX for semi-static periodicity alignment..... | 46 | +| B.2.2 Dynamic CDRX alignment..... | 60 | +| B.2.3 Non-uniform PMOs within CDRX On Duration..... | 65 | +| B.2.4 Two-stage CDRX On Duration..... | 66 | +| B.2.5 Jitter handling by LP-WUS..... | 72 | +| B.2.6 Early stopping of On Duration Timer..... | 75 | +| B.2.7 Additional DRX active time..... | 77 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------------|------------| +| B.2.8 | Multiple active CDRX configurations..... | 85 | +| B.2.9 | Dynamic grant enhancement with XR-specific pre-scheduling..... | 92 | +| B.2.10 | SPS+DG with UE power saving scheme..... | 95 | +| B.2.11 | PDCCH skipping and interaction with HARQ retransmission..... | 96 | +| B.2.12 | Enhancements to PDCCH skipping indication..... | 106 | +| B.2.13 | Non-scheduling DCI based PDCCH skipping and continuous PDCCH skipping..... | 110 | +| B.2.14 | SSSG switching enhancements..... | 111 | +| B.2.15 | DCP indicated SSSG switching..... | 116 | +| B.2.16 | Retransmission-less CG for UL pose transmission..... | 116 | +| B.2.17 | XR-specific playoutDelayForMediaStartup for XR UE power saving enhancement..... | 117 | +| B.2.18 | Partial UL transmission..... | 118 | +| Annex C (informative): | RAN2 Study Item Agreements..... | 119 | +| C.1 | RAN2#119-e..... | 119 | +| C.2 | RAN2#119bis-e..... | 119 | +| C.3 | RAN2#120..... | 120 | +| C.4 | RAN2#121..... | 121 | +| Annex D (informative): | Change history..... | 122 | + +# 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 intended to capture the output of the study item on XR Enhancements for NR [10], which aims at investigating power saving and capacity enhancements techniques tailored for XR services, as well as means to provide XR-awareness in RAN. + +This study follows a series of earlier studies conducted in 3GPP by SA1 [2], SA4 [5] [6] [7] and RAN1 [8]. It is complemented by work in SA2 [12], SA4 [11] and SA6 [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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TR 22.842: "Study on Network Controlled Interactive Service (NCIS) in the 5G System (5GS)". +- [3] 3GPP TR 23.748: "Study on enhancement of support for Edge Computing in 5G Core network(5GC)". +- [4] 3GPP TR 23.758: "Study on application architecture for enabling Edge Applications". +- [5] 3GPP TR 26.918: "Virtual Reality (VR) media services over 3GPP". +- [6] 3GPP TR 26.926: "Traffic Models and Quality Evaluation Methods for Media and XR Services in 5G Systems". +- [7] 3GPP TR 26.928: "Extended Reality (XR) in 5G". +- [8] 3GPP TR 38.838: "Study on XR (Extended Reality) evaluations for NR". +- [9] 3GPP TR 23.700-60: "Study on architecture enhancement for XR and media services". +- [10] RP-220285: "Study on XR Enhancements for NR". +- [11] SP-210043: "Feasibility Study on Typical Traffic Characteristics for XR Services and other Media". +- [12] SP-220705: "Study on XR (Extended Reality) and media services". +- [13] S4-220505: "LS Reply on QoS support with PDU Set granularity". +- [14] S4aV220921: "Reply LS on further details on XR traffic". +- [15] 3GPP TS 38.300: "NR and NG-RAN Overall description; Stage-2". +- [16] S4-221626: "Reply LS on Pose Information". +- [17] S4aR230035: "Reply LS on PDU Set Handling" + +# 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]. + +**Field of view:** the angle of visible field expressed in degrees measured from the focal point. + +**PDU Set:** A PDU Set is composed of one or more PDUs carrying the payload of one unit of information generated at the application level (e.g. a frame or video slice for XRM Services, as used in TR 26.926 [6]). In some implementations all PDUs in a PDU Set are needed by the application layer to use the corresponding unit of information. In other implementations, the application layer can still recover parts or all of the information unit, when some PDUs are missing. + +**Multi-modal Data:** Multi-modal Data is defined to describe the input data from different kinds of devices/sensors or the output data to different kinds of destinations (e.g. one or more UEs) required for the same task or application. Multi-modal Data consists of more than one Single-modal Data, and there is strong dependency among each Single-modal Data. Single-modal Data can be seen as one type of data. + +**Data Burst:** Data produced by the application in a short period of time, comprising PDUs from one or more PDU Sets. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1], TS 38.300 [15] 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] and in TS 38.300 [15]. + +| | | +|-------|----------------------------------------| +| 3DoF | Three Degrees of Freedom | +| 6DoF | Six Degrees of freedom | +| AR | Augmented Reality | +| DASH | Dynamic Adaptive Streaming over HTTP | +| FEC | Forward Error Correction | +| FoV | Field of view | +| FPS | Frames Per Second | +| GBR | Guaranteed Bit Rate | +| GFBR | Guaranteed Flow Bit Rate | +| HEVC | High-Efficiency Video Coding | +| HMD | Head-Mounted Display | +| HUD | Heads-Up Display | +| PDB | Packet Delay Budget | +| PDU | Protocol Data Unit | +| PER | Packet Error Rate | +| PSDB | PDU-Set Delay Budget | +| PSER | PDU-Set Error Rate | +| PSI | PDU-Set Importance | +| PSIHI | PDU-Set Integrated Handling Indication | +| QCI | QoS Class Identifier | +| QFI | QoS Flow ID | +| QoE | Quality of Experience | +| QoS | Quality of Service | +| VR | Virtual Reality | +| XR | Extended reality | + +# 4 Introduction to Extended Reality + +## 4.1 Extended Reality Types + +Extended Reality (**XR**) refers to all real-and-virtual combined environments and human-machine interactions generated by computer technology and wearables. XR is an umbrella term for different types of realities (see TR 26.918 [5] and TR 26.928 [7]): + +- Virtual reality (**VR**) is a rendered version of a delivered visual and audio scene. The rendering is designed to mimic the visual and audio sensory stimuli of the real world as naturally as possible to an observer or user as they move within the limits defined by the application. Virtual reality usually, but not necessarily, requires a user to wear a head mounted display (HMD), to completely replace the user's field of view with a simulated visual component, and to wear headphones, to provide the user with the accompanying audio. Some form of head and motion tracking of the user in VR is usually also necessary to allow the simulated visual and audio components to be updated in order to ensure that, from the user's perspective, items and sound sources remain consistent with the user's movements. +- Augmented reality (**AR**) is when a user is provided with additional information or artificially generated items or content overlaid upon their current environment. Such additional information or content will usually be visual and/or audible and their observation of their current environment may be direct, with no intermediate sensing, processing and rendering, or indirect, where their perception of their environment is relayed via sensors and may be enhanced or processed. +- Mixed reality (**MR**) is an advanced form of AR where some virtual elements are inserted into the physical scene with the intent to provide the illusion that these elements are part of the real scene. + +Other terms used in the context of XR are Immersion as the sense of being surrounded by the virtual environment as well as Presence providing the feeling of being physically and spatially located in the virtual environment. The sense of presence provides significant minimum performance requirements for different technologies such as tracking, latency, persistency, resolution and optics. + +This document uses the acronym XR throughout to refer to equipment, applications and functions used for VR, AR and MR. Examples include, but are not limited to HMDs for VR, optical see-through glasses and camera see-through HMDs for AR and MR and mobile devices with positional tracking and camera. They all offer some degree of spatial tracking and the spatial tracking results in an interaction to view some form of virtual content. + +## 4.2 Human Perception and Tracking + +For providing XR experiences that make the user feel *immersed* and *present*, several relevant quality of experience factors have been collected (see TR 26.926 [7]). Presence is the feeling of being physically and spatially located in an environment. Presence is divided into 2 types: Cognitive Presence and Perceptive Presence. Cognitive Presence is the presence of one's mind. It can be achieved by watching a compelling film or reading an engaging book. Cognitive Presence is important for an immersive experience of any kind. Perceptive Presence is the presence of one's senses. To accomplish perceptive presence, one's senses, sights, sound, touch and smell, have to be tricked. To create perceptive presence, the XR Device has to fool the user's senses, most notably the audio-visual system. XR Devices achieve this through positional tracking based on the movement. The goal of the system is to maintain your sense of presence and avoid breaking it. Perceptive Presence is the objective to be achieved by XR applications. + +The Human field of view (**FoV**) is defined as the area of vision at a given moment (with a fixed head). It is the angle of visible field expressed in degrees measured from the focal point. The monocular FoV is the angle of the visible field of one eye whereas the binocular FoV is the combination of the two eyes fields (see TR 26.918 [5]). The binocular horizontal FoV is around 200-220°, while the vertical one around 135°. The central vision, which is about 60°, is also called the comfort zone where sensibility to details is the most important. Although less sensitive to definition, the peripheral vision is more receptive to movements. + +In XR, actions and interactions involve movements and gestures. Thereby, the Degrees of Freedom (**DoF**) describe the number of independent parameters used to define movement in the 3D space (see TR 26.928 [7]): + +- 3DoF: three rotational and un-limited movements around the X, Y and Z axes (respectively pitch, yaw and roll). A typical use case is a user sitting in a chair looking at 3D 360 VR content on an HMD. + +![Figure 4.2-1: 3DoF diagram showing a person sitting in a chair with arrows indicating Yaw, Pitch, and Roll* rotation axes.](07f537f57749b75157f742525e6a8dbc_img.jpg) + +A diagram of a person sitting in a chair, illustrating the three degrees of freedom (3DoF) for head rotation. The person is shown from a side profile. Three curved arrows indicate the rotational axes: 'Yaw' (vertical axis, rotating left and right), 'Pitch' (horizontal axis, rotating up and down), and 'Roll\*' (diagonal axis, rotating side to side). A small 3D icon of a head is shown at the bottom right. + +Figure 4.2-1: 3DoF diagram showing a person sitting in a chair with arrows indicating Yaw, Pitch, and Roll\* rotation axes. + +Figure 4.2-1: 3DoF + +- 6DoF: 3DoF with full translational movements along X, Y and Z axes. Beyond the 3DoF experience, it adds (i) moving up and down (elevating/heaving); (ii) moving left and right (strafing/swaying); and (iii) moving forward and backward (walking/surging). A typical use case is a user freely walking through 3D 360 VR content (physically or via dedicated user input means) displayed on an HMD. + +![Figure 4.2-2: 6DoF diagram showing a person standing with arrows indicating Up, Down, Left, Right, Forward, Backward, Yaw, Pitch, and Roll rotation axes.](d3f6de4fe9f9138fc6afc584b5104433_img.jpg) + +A diagram of a person standing, illustrating the six degrees of freedom (6DoF) for head movement. The person is shown from a front view. Three curved arrows indicate the rotational axes: 'Yaw' (vertical axis), 'Pitch' (horizontal axis), and 'Roll' (diagonal axis). Six straight arrows indicate the translational axes: 'Up' (vertical), 'Down' (vertical), 'Left' (horizontal), 'Right' (horizontal), 'Forward' (depth), and 'Backward' (depth). A small 3D icon of a head is shown at the bottom right. + +Figure 4.2-2: 6DoF diagram showing a person standing with arrows indicating Up, Down, Left, Right, Forward, Backward, Yaw, Pitch, and Roll rotation axes. + +Figure 4.2-2: 6DoF + +An **XR View** describes a single view into an XR scene for a given time. Each view corresponds to a display or portion of a display used by an XR device to present the portion of the scene to the user. + +An **XR Viewport** describes a viewport, or a rectangular region, of a graphics surface. The XR viewport corresponds to the projection of the XR View onto a target display. An XR viewport is predominantly defined by the width and height of the rectangular dimensions of the viewport. + +An **XR Pose** describes a *position* and *orientation* in space relative to an XR Space. An essential element of XR is the spatial tracking of the viewer pose. + +## 4.3 Capture, Encoding and Delivery + +### 4.3.1 Video + +XR content may be represented in different formats, e.g. panoramas or spheres depending on the capabilities of the capture systems. Since modern video coding standards are not designed to handle spherical content. Projection is used for conversion of a spherical (or 360°) video into a two-dimensional rectangular video before the encoding stage. After projection, the obtained two-dimensional rectangular image can be partitioned into regions (e.g. front, right, left, back, top, bottom) that can be rearranged to generate "packed" frames to increase coding efficiency or viewport dependent stream arrangement. + +There are mainly three approaches that can be considered for 360 video delivery (see TR 26.918 [5]): + +- Single stream approach: the single stream approach consists in providing the full 360 video and showing the interesting part only. Solutions that lie within this group have the drawback that either they may not be scalable + +or they may impose a big challenge in terms of required network resources (high bitrate of high resolution video) and required processing at the client side (decode a very high resolution video). + +- Multi-stream approach: the multi-stream approach consists of encoding several streams, each of them emphasizing a given viewport and making them available for the receiver, so that the receiver decides which stream is delivered at each time instance. +- Tiled stream approach: the tiled stream approach consists in emphasizing the current user viewport through transmitting non-viewport samples with decreased resolution. The tiles can be provided as one common bitstream (using motion-constrained HEVC tiles) or as separate video streams. + +In modern video codecs (see S4-220505 [13]): + +- Complex prediction structures are used that take into account application constraints, encoding complexity, latency and dynamic decisions in the encoding. This may result in irregularities, for example based on sequence properties. In particular for low-latency delivery with error resiliency, different flavours of encoding operations are in use, and the concept of I, P and B pictures is not generally applicable. +- All PDUs in a PDU Set are needed by the application layer to use the corresponding unit of information in some implementations; while in some others, receivers may use the data up to the first lost fragmentation unit to recover at least parts of the video data and apply error concealment afterward. +- Furthermore, in motion-compensated predicted video decoding, some frames refer to other frames based on the video encoding configuration but also based on dynamic operational decisions. As a consequence, a PDU Set may "depend" on previously received PDU Sets. However, such dependencies do not necessarily result in discarding dependent information units. + +### 4.3.2 Audio + +For Audio, we can distinguish channel-based and object-based representations (see TR 26.918 [5]): + +- Channel-based representation using multiple microphones to capture sounds from different directions and post-processing techniques are well known in the industry, as they have been the standard for decades. +- Object-based representations represent a complex auditory scene as a collection of single audio elements, each comprising an audio waveform and a set of associated parameters or metadata. The metadata embody the artistic intent by specifying the transformation of each of the audio elements to playback by the final reproduction system. Sound objects generally use monophonic audio tracks that have been recorded or synthesized through a process of sound design. These sound elements can be further manipulated, so as to be positioned in a horizontal plane around the listener, or in full three-dimensional space using positional metadata. + +## 4.4 XR Engines and Rendering + +XR engines provide a middleware that abstracts hardware and software functionalities for developers of XR applications (see TR 26.928 [7]). Typical components include a rendering engine for graphics, an audio engine for sound, and a physics engine for emulating the laws of physics. In the remainder of this Technical Report, the term *XR engine* is used to provide any type of typical XR functionalities as mentioned above. + +The processing of an XR engine is not exclusively carried out in the device GPU. In power and resource constrained devices, it can be assisted or split across the network through edge computing (see TR 22.842 [2]): the UE sends the sensor data in uplink direction to the cloud side in a real time manner and when the cloud side receives the sensor data, it performs rendering computing and produces the multimedia data and then sends back to the user devices for display. This is where NR can play an essential role. + +## 4.5 Characteristics and Requirements + +### 4.5.1 General + +In general, the RTP layer can handle out-of-sequence reception of RTP packets, and some codecs even require it for good operations (instead of having to cope with increased delays to satisfy in-sequence delivery). Thus, a mode of + +operation where the lower-layers on the receiver side do not always enforce in-sequence delivery to upper layers is preferred (see S4aR230035 [17]). + +Other than that, it is difficult to identify characteristics common for different XR applications since they heavily depend on the application choices, such as the application itself, the codec in use, the data formats and the encoding operation (see S4-220505 [13]). In particular, low-latency XR and cloud gaming video services such as Split-Rendering or Cloud Gaming typically would not use the traditional coding structure with a fixed Group of Picture (GOP). In addition, the field of low-latency video delivery is undergoing heavy innovation and new coding methods may be established frequently. Thus, the traffic characteristics and requirements derived from the work done in SA4 (TR 26.926 [6] and TR 26.928 [7]) and listed below, can only be used as a baseline when specific examples for XR traffic characteristics are needed – bearing in mind that they are not universally applicable for all XR applications. + +### 4.5.2 Video + +The **frame rate** for XR video varies from 15 frames per second up to 90 or even 120 frames per second, with a typical minimum of 60 for VR (see TR 26.918 [5] and TR 26.926 [6]). + +According to TR 26.918 [5], the **latency** of action of the angular or rotational vestibulo-ocular reflex is known to be of the order of 10 ms or in a range from 7-15 milliseconds and it seems reasonable that this should represent a performance goal for XR systems. This results in a motion-to-photon latency of less than 20 milliseconds, with 10ms being given as a goal. + +Regarding the **bit rates**, between 10 and 200Mbps can be expected for XR depending on frame rate, resolution and codec efficiency (see TR 26.926 [6] and TR 26.928 [7]). + +### 4.5.3 Audio + +According to TR 26.918 [5], due to the relatively slower speed of sound compared to that of light, it is natural that users are more accustomed to, and therefore tolerant of, sound being relatively delayed with respect to the video component than sound being relatively in advance of the video component. Recent studies have led to recommendations of an accuracy of between 15 ms (audio delayed) and 5 ms (audio advanced) for the **synchronization**, with recommended absolute limits of 60 ms (audio delayed) and 40 ms (audio advanced) for broadcast video. + +### 4.5.4 Pose Information + +To maintain a reliable registration of the virtual world with the real world, as well as to ensure accurate tracking of the XR Viewer pose, XR applications require highly accurate, low-latency tracking of the device at about 1kHz sampling frequency. The size of a XR Viewer Pose associated to time, typically results in packets of size in the range of 30-100 bytes, such that the generated data is around several hundred kbit/s if delivered over the network with latency requirements in the range of 10-20ms (see TR 26.928 [7]). + +Repeatedly providing the XR Viewer Pose for the same display time may not necessarily return the same result (the prediction gets increasingly accurate as the information is closer to the time when a prediction is made) and there is a trade-off between providing several XR Viewer Pose for a display time and using the same XR Viewer Pose for several consecutive display times. However, it can be assumed that sending one XR Viewer Pose aligned with the frame rate of the rendered video may be sufficient, for example at 60fps (see S4-221626 [16]). + +NOTE: In case the pose is used for pre-rendering in the network (edge/cloud), an accurate and most recent pose information is preferable. + +Pose information has to be delivered with ultra-high reliability, therefore, similar performance as URLLC is expected i.e. packet loss rate should be lower than 10E-3 for uplink sensor data – see S4-221626 [16]. + +# 5 XR Enhancements for NR + +## 5.1 XR Awareness + +### 5.1.1 General + +In both uplink and downlink, XR-Awareness contributes to optimizations of gNB radio resource scheduling and relies at least on the notions of PDU Set and Data Burst (see TR 23.700-60 [9]): a PDU Set is composed of one or more PDUs carrying the payload of one unit of information generated at the application level (e.g. a frame or video slice), while a Data Burst is a set of data PDUs generated and sent by the application in a short period of time. + +NOTE 1: A Data Burst can be composed of multiple PDUs belonging to one or multiple PDU Sets. During a Data Burst, periods of data transmission inactivity should not be assumed. Although the duration of Data Bursts may vary, it can be assumed that it stays within the same order of magnitude. Also, the arrival time of the first packet of a data burst cannot be provided by 5GC. + +The following information may be provided by the CN to RAN (see TR 23.700-60 [9]): + +- Semi-static information per QoS flow: + - Periodicity for UL and DL traffic of the QoS Flow provided via TSCAI/TSCAC; + - DL Traffic jitter information (e.g. jitter range) associated with each periodicity of the QoS flow provided via TSCAI/TSCAC. + - PDU Set QoS parameters of the QoS flow (i.e. applicable to all PDU sets of the QoS flow) provided by the SMF via NGAP: + - PDU Set Error Rate (PSER): defines an upper bound for a rate of non-congestion related PDU Set losses between RAN and the UE (see TR 23.700-60 [9]). + +NOTE 2: In this release, a PDU set is considered as successfully delivered only when all PDUs of a PDU Set are delivered successfully, and if the PSER is available, the usage of PSER supersedes the usage of PER. + +- PDU Set Delay Budget (PSDB): time between reception of the first PDU (at the UPF in DL, at the UE in UL) and the successful delivery of the last arrived PDU of a PDU Set (at the UE in DL, at the UPF in UL). PSDB is an optional parameter and when provided, the PSDB supersedes the PDB (see TR 23.700-60 [9]). +- PDU Set Integrated Handling Indication (PSIHI): indicates whether all PDUs of the PDU Set are needed for the usage of PDU Set by application layer. +- PDU Set Information and Identification (dynamic information for DL provided by user plane in GTP-U header): + - PDU Set Sequence Number; + - PDU Set Size in bytes (FFS); + - PDU SN within a PDU Set; + - Indication of End PDU of the PDU Set; + - PDU Set Importance (PSI): identifies the relative importance of a PDU Set compared to other PDU Sets within a QoS Flow. RAN may use it for PDU Set level packet discarding in presence of congestion; + - End of Data Burst indication in the header of the last PDU of the Data Burst (optional). + +For the uplink XR traffic, the UE needs to be able to identify PDU Set and Data Bursts dynamically, including PSI, but in-band marking over Uu of PDUs is not needed. Additional potential improvements to enhance the scheduling of uplink resources are given in clause 5.3.2. + +When the PSIHI is set for a QoS flow, as soon as one PDU of a PDU set is known to be lost, the remaining PDUs of that PDU Set can be considered as no longer needed by the application and may be subject to discard operation (see clause 5.3.2). + +NOTE 3: It cannot always be assumed that the remaining PDUs are not useful and can safely be discarded. + +NOTE 4: In case of Forward Error Correction (FEC), active discarding of PDUs when assuming that a large enough number of packets have already been transmitted for FEC to recover without the remaining PDUs is not recommended as it might trigger an increase of FEC packets (see S4aV220921 [14]). + +### 5.1.2 Layer 2 Structure + +Depending on how the mapping of PDU Sets onto QoS flows is done in the NAS and how QoS flows are mapped onto DRBs in the AS, we can distinguish the following alternatives (as depicted on Figure 5.1.2-1 below): + +- 111: one-to-one mapping between types of PDU Sets and QoS flows in the NAS and one-to-one mapping between QoS flows and DRBs in the AS. From a Layer 2 structure viewpoint, this alternative is already possible and requires as many DRBs as types of PDU Sets. Providing different QoS for the types of PDU Sets sent in different DRBs is already possible. +- NN1: one-to-one mapping between types of PDU Sets and QoS flows in the NAS and possible multiplexing of QoS flows in one DRB in the AS. From a Layer 2 structure viewpoint, this alternative is already possible but gives each QoS flows multiplexed in a DRB the same QoS. Providing different QoS for the types of PDU Sets (i.e. QoS flows) multiplexed in a single DRB is currently not possible. +- NI1: possible multiplexing of types of PDU Sets in one QoS flow in the NAS and one-to-one mapping between QoS flows and DRBs in the AS. From a Layer 2 structure viewpoint, this alternative is already possible but gives each QoS flow/DRB one QoS. Providing different QoS for the types of PDU Sets multiplexed in a single QoS flow/DRB is currently not possible. +- N1N: possible multiplexing of types of PDU Sets in one QoS flow in the NAS and demultiplexing of types of PDU Sets from one QoS flow on multiple DRBs in the AS. From a Layer 2 structure viewpoint, demultiplexing of types of PDU Sets from one QoS flow onto multiple DRBs is currently not possible. + +NOTE: The multiplexing of several types of PDU sets on the same QoS flow is allowed by the CN. + +![Figure 5.1.2-1: Mapping Alternatives. The diagram shows four vertical columns representing different mapping alternatives. Each column shows the flow from PDU Sets at the top, through QoS flows in the middle, to DRBs at the bottom. Alternative 111 shows a one-to-one mapping: PDU Set 1 to QoS flow 1 to DRB1, and PDU Set 2 to QoS flow 2 to DRB2. Alternative NN1 shows PDU Set 1 to QoS flow 1 and PDU Set 2 to QoS flow 2, both of which are then multiplexed into a single DRB A. Alternative NI1 shows both PDU Set 1 and PDU Set 2 being multiplexed into a single QoS flow A, which is then mapped to a single DRB A. Alternative N1N shows both PDU Set 1 and PDU Set 2 being multiplexed into a single QoS flow A, which is then demultiplexed into two separate DRBs, DRB1 and DRB2.](d17f75945bbb3feb84a153ecfedb9b81_img.jpg) + +Figure 5.1.2-1: Mapping Alternatives. The diagram shows four vertical columns representing different mapping alternatives. Each column shows the flow from PDU Sets at the top, through QoS flows in the middle, to DRBs at the bottom. Alternative 111 shows a one-to-one mapping: PDU Set 1 to QoS flow 1 to DRB1, and PDU Set 2 to QoS flow 2 to DRB2. Alternative NN1 shows PDU Set 1 to QoS flow 1 and PDU Set 2 to QoS flow 2, both of which are then multiplexed into a single DRB A. Alternative NI1 shows both PDU Set 1 and PDU Set 2 being multiplexed into a single QoS flow A, which is then mapped to a single DRB A. Alternative N1N shows both PDU Set 1 and PDU Set 2 being multiplexed into a single QoS flow A, which is then demultiplexed into two separate DRBs, DRB1 and DRB2. + +**Figure 5.1.2-1: Mapping Alternatives** + +When comparing these alternatives, it was agreed that a QoS flow cannot be mapped onto multiple DRBs in the uplink, thereby excluding alternative N1N. For the other alternatives, providing different QoS by splitting PDU sets of one DRB to different RLC bearers will not be possible i.e. that splitting a DRB onto multiple RLC entities will remain limited to existing cases (e.g. duplication). + +In addition, the notion of PDU Set does not impact the granularity of: + +- SDAP SDU handling: SDAP still maps every incoming SDU to a single PDU for a single PDCP entity; +- Retransmissions: HARQ still relies on MAC PDUs and ARQ on RLC PDUs. + +In terms of logical channel prioritisation in uplink, changes due to PDU prioritisation will not be introduced, e.g. delay criteria was considered but agreed not to be pursued further unless fundamental issues are identified. + +## 5.2 Power Saving Techniques + +### 5.2.1 Physical Layer Enhancements + +The evaluation results for proposed and studied power saving enhancement schemes are available in Annex B.2. + +### 5.2.2 Layer 2 Enhancements + +Most XR frame rates (15, 30, 45, 60, 72, 90 and 120fps) correspond to periodicities which are not an integer (66.66, 33.33, 22.22, 16.66, 13.88, 11.11 and 8.33ms respectively). The corresponding support by DRX will be dealt with in a semi-static manner at least (e.g. via RRC signalling). + +In addition, RRC pre-configuration and switching of configurations of DRX can be considered for enhancements of XR power saving. + +## 5.3 Capacity Improvements Techniques + +### 5.3.1 Physical Layer Enhancements + +The following enhancements for configured grant-based transmission are recommended: + +- Multiple CG PUSCH transmission occasions in a period of a single CG PUSCH configuration; +- Dynamic indication of unused CG PUSCH occasion(s) based on UCI (e.g., CG-UCI or a new UCI) by the UE. + +The corresponding capacity performance evaluation results are available in Annex B.1.6. + +The evaluation results for other proposed and studied capacity enhancement schemes are available in Annex B.1. + +### 5.3.2 Layer 2 Enhancements + +In order to enhance the scheduling of uplink resources for XR, the following improvements are envisioned: + +- One or more additional BS table(s) to reduce the quantisation errors in BSR reporting (e.g. for high bit rates); +- Delay knowledge of buffered data, consisting of e.g. remaining time, and distinguishing how much data is buffered for which delay. It is to be determined whether the delay information is reported as part of BSR or as a new MAC CE. Also, how the delay information can be up to date considering e.g. scheduling and transmission delays needs to be investigated further. +- Additional BSR triggering conditions to allow timely availability of buffer status information can be investigated further. +- Delivery of some assistance information (e.g. periodicity) reusing TSCAI as a baseline. Whether additional mechanism is required can be further considered with an assumption that all information may not be always available at UE application. +- Signalling of UL traffic arrival information from the UE to the gNB e.g. to cope with jitter in case of tethering (FFS). + +For PDCP discard operation in uplink, the timer-based discard operation (when configured) should apply to all SDUs/PDUs belonging to the same PDU Set. Furthermore, for a PDU Set in a QoS flow for which the PSIHI is set, when one PDU of that PDU set is known to either be lost or associated to a discarded SDU (see clause 5.1.1), all remaining PDUs of that PDU Set could be discarded at the transmitter to free up radio resources. + +In case of congestion, the PSI may be used for PDU set discarding (see clause 5.1.1) and in uplink, a PDU set discard mechanism taking the PSI into account will be introduced. + +In uplink, the usage of Configured Grant brings potential benefits for XR services with the enhancements recommended in clause 5.3.1, while in downlink, enhancements to Semi-Persistent scheduling are not foreseen to bring any benefits. + +NOTE: The layer 2 components of the mechanisms recommended in clause 5.3.1 will be specified. + +# --- 6 Conclusions + +In conclusion of the study, the following enhancements for XR services are recommended: + +- For XR Awareness: + - Provisioning by CN of semi-static information per QoS flow (e.g. PDU set QoS parameters), dynamic information per PDU set (PDU Set information and Identification) and End of Data Burst indication (as per TR 23.700-60 [9]); + - Identifying by UE of PDU Sets, Data bursts and PSI; + - Provisioning by UE of XR traffic assistance information e.g. periodicity, UL traffic arrival information (FFS). +- For Power Saving: + - DRX support of XR frame rates corresponding to non-integer periodicities (through at least semi-static mechanisms e.g. RRC signalling). +- For Capacity Enhancements: + - Multiple CG PUSCH transmission occasions in a period of a single CG PUSCH configuration; + - Dynamic indication of unused CG PUSCH occasion(s) based on UCI by the UE; + - BSR enhancements including at least new BS Table(s); + - Delay reporting of buffered data in uplink; + - Discard operation of PDU Sets. + +# Annex A (informative): Evaluation Methodology + +Rel-17 evaluation methodology for XR power saving and capacity enhancements (see TR 38.838 [8]) is used as the baseline evaluation methodology for UE power saving and capacity evaluation of Rel-18 XR. + +System capacity is identified as KPI for capacity study, which is defined as the maximum number of users per cell with at least Y % of UEs being satisfied. A UE is declared as a satisfied UE if all considered streams meet their own packet error rate (PER) and PDB requirements, i.e., more than X% of packets are successfully transmitted within a given air interface PDB. From Rel-17 XR evaluation methodology, baseline parameters are Y= 90% and X = 99%. + +For power saving evaluation, power saving gain and capacity gain are calculated with respect to the AlwaysOn baseline unless otherwise noted. Jitter in DL is assumed on unless otherwise noted. + +In addition to the values for jitter in DL in Table 5.1-2 in TR 38.838 [8], the following statistical parameters can also be optionally evaluated in Rel-18 XR SI. + +NOTE: This optional assumption is not applicable to the evaluation of 90 FPS and above. + +**Table A-1: Statistical parameters to be optionally evaluated in Rel-18 XR SI** + +| Parameter | unit | Optional value for evaluation | +|------------------|------|-------------------------------| +| Mean | ms | 0 | +| STD | ms | 5 | +| Truncation range | ms | [-8, 8] | + +# Annex B (informative): Evaluation Studies + +## B.1 Capacity performance evaluation results + +### B.1.1 Multi-PDSCH scheduling by a single DCI + +This clause captures the capacity performance evaluation results for dynamic scheduling when multi-PDSCH is scheduled by a single DCI. Due to large XR video frame as per 38.838, resources in a single slot may be not enough to convey all the data of a frame, resulting in resource allocation spanning more than one slot. Thereby, in this clause, multi-PDSCH scheduling by a single DCI is evaluated to transmit XR video frame over multiple slots. + +The performance of single-PDSCH scheduling, where X symbol(s) are always reserved for PDCCH transmission in each slot (scheme 1.1 in Tables B.1.1-1,2,3) has been compared against various schemes for multi-PDSCH scheduling. Particularly, the following schemes, where multi-PDSCH is scheduled by a single DCI, have been evaluated: + +- Scheme 1.2: Multi-PDSCH scheduling, where unoccupied CORESET in a slot can be re-used for PDSCH transmission. +- Scheme 1.3: Multi-PDSCH scheduling, where X symbol(s) are always reserved for PDCCH transmission in each slot. +- Scheme 1.4: Multi-PDSCH scheduling with FDRA enhancement - more than one FDRA indication is contained in the scheduling DCI, each of which is applied to one or more scheduled PDSCH. +- Scheme 1.5: Multi-PDSCH scheduling enhancement with early HARQ-ACK feedback - multiple PUCCHs may be considered where HARQ-ACK for the earlier PDSCH(s) can be reported earlier than the later PDSCH(s) scheduled by the same DCI, to reduce latency of HARQ-ACK feedback. +- Scheme 1.6: Multi-PDSCH scheduling where single PDCCH schedules up to 4 PDSCHs and full flexibility in terms of resource (RB allocation) as well as MCS for each of the 4 PDSCHs. +- Scheme 1.7: Multi-PDSCH scheduling, where X symbols per slot are used for PDCCH if there is at least one UE that needs to be scheduled with first TB out of multiple TBs and 0 symbols per slot are used for PDCCH if no UE with the first TB out of multiple TBs needs to be scheduled. + +The performance results of the above schemes are reported in Table B.1.1-1, Table B.1.1-2, Table B.1.1-3 in terms of the ratio of satisfied users. + +Table B.1.1-1: FR1, DL, InH, VR/AR and Cloud Gaming at 60 FPS + +| Source | Tdoc Source | Scheme | TDD form at | SU/MU-MIMO | Data rate (Mbps) | PDB (ms) | Capacity (UEs/cell) | C1=floor (Capacity) | % of satisfied UEs when #UEs/cell =C1 | Notes | +|-----------------------|-------------|---------|-------------|------------|------------------|----------|---------------------|---------------------|---------------------------------------|------------| +| Source [vivo] | R1-2208661 | 1.1* | DDD SU | SU-MIMO | 30 | 10 | 9.8 | 9 | 96.61% | Note 1,3 | +| | | | | | 45 | | 6.08 | 6 | 91.67% | | +| Source [vivo] | R1-2208661 | 1.1** | DDD SU | SU-MIMO | 30 | 10 | 8.16 | 8 | 91.07% | Note 1,3 | +| | | | | | 45 | | 4.66 | 4 | 97.22% | | +| Source [vivo] | R1-2208661 | 1.1*** | DDD SU | SU-MIMO | 30 | 10 | 10.25 | 10 | 93.06% | Note 1,3 | +| Source [vivo] | R1-2208661 | 1.2* | DDD SU | SU-MIMO | 30 | 10 | 10.37 | 10 | 95% | Note 1,2,3 | +| | | | | | 45 | | 6.27 | 6 | 94.91% | | +| Source [vivo] | R1-2208661 | 1.2** | DDD SU | SU-MIMO | 30 | 10 | 9.58 | 9 | 95.14% | Note 1,2,3 | +| | | | | | 45 | | 5.57 | 5 | 96.67% | | +| Source [vivo] | R1-2208661 | 1.2*** | DDD SU | SU-MIMO | 30 | 10 | 10.1 | 10 | 91.28% | Note 1,2,3 | +| Source [vivo] | R1-2208661 | 1.3* | DDD SU | SU-MIMO | 30 | 10 | 8.81 | 8 | 93.89% | Note 1,3 | +| Source [vivo] | R1-2208661 | 1.3** | DDD SU | SU-MIMO | 30 | 10 | 7.25 | 7 | 92.02% | Note 1,3 | +| Source [vivo] | R1-2208661 | 1.3*** | DDD SU | SU-MIMO | 30 | 10 | 9.68 | 9 | 98.37% | Note 1,3 | +| Source [vivo] | R1-2208661 | 1.4* | DDD SU | SU-MIMO | 30 | 10 | 11.09 | 11 | 90.8% | Note 1,2 | +| Source [vivo] | R1-2208661 | 1.5* | DDD SU | SU-MIMO | 30 | 10 | 10.59 | 10 | 95.72% | Note 1,2 | +| Source [InterDigital] | R1-2209658 | 1.1** | DDD SU | SU-MIMO | 30 | 10 | 5.3 | 5 | 94% | Note 1 | +| | | | | | 45 | | 3.1 | 3 | 91.5% | | +| Source [InterDigital] | R1-2209658 | 1.1** | DDD SU | SU-MIMO | 30 | 15 | 7.2 | 7 | 94.5% | Note 1 | +| Source [InterDigital] | R1-2209658 | 1.6**** | DDD SU | SU-MIMO | 30 | 10 | 7.8 | 7 | 97% | Note 1,2 | +| | | | | | 45 | | 4.1 | 4 | 91% | | +| Source [InterDigital] | R1-2209658 | 1.6**** | DDD SU | SU-MIMO | 30 | 15 | 10 | 10 | 100% | Note 1,2 | +| Source [ZTE] | R1-2209198 | 1.1** | DDD SU | SU-MIMO | 30 | 10 | 9.1 | 9 | 91% | Note 1 | +| | | | | | 60 | | 3.4 | 3 | 97% | | +| Source [ZTE] | R1-2209198 | 1.7** | DDD SU | SU-MIMO | 30 | 10 | 7.9 | 7 | 96% | Note 1,2,4 | +| | | | | | 60 | | 3.7 | 3 | 99% | | + +NOTE 1: BS antenna parameters: 32TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (4,4,2,1,1,4,4) + +NOTE 2: No symbol for PDCCH is reserved in the slot where no scheduling DCI is transmitted + +NOTE 3: Results does not consider any other PDCCH that may occupy the CORESET(s) than scheduling DCI, e.g. broadcast PDCCH + +NOTE 4: Results consider 2 symbols are used for PDCCH, if at least one UE needs to be scheduled with the first TB out of multiple TBs + +\* Number of PDCCH symbols per slot = 1 + +\*\* Number of PDCCH symbols per slot = 2 + +\*\*\* Number of PDCCH symbols per slot = 0.5 + +\*\*\*\* Number of PDCCH symbols per slot = 4 + +**Table B.1.1-2: FR1, DL, DU, VR/AR and Cloud Gaming at 60 FPS** + +| Source | Tdoc Source | Scheme | TDD form at | SU/MU-MIMO | Data rate (Mbps) | PDB (ms) | Capacity (UEs/cell) | C1=floor (Capacity) | % of satisfied UEs when #UEs/cell =C1 | Notes | +|-----------------------|-------------|---------|-------------|------------|------------------|----------|---------------------|---------------------|---------------------------------------|--------| +| Source [InterDigital] | R1-2209658 | 1.1** | DDD SU | SU-MIMO | 30 | 10 | 5.5 | 5 | 95% | Note 1 | +| | | | | | 45 | | 3.7 | 3 | 100% | | +| Source [InterDigital] | R1-2209658 | 1.1** | DDD SU | SU-MIMO | 30 | 15 | 7.5 | 7 | 95% | Note 1 | +| Source [InterDigital] | R1-2209658 | 1.6**** | DDD SU | SU-MIMO | 30 | 10 | 8.4 | 8 | 94.5% | Note 1 | +| | | | | | 45 | | 5.1 | 5 | 91.5% | | +| Source [InterDigital] | R1-2209658 | 1.6**** | DDD SU | SU-MIMO | 30 | 15 | 9.1 | 9 | 91% | Note 1 | + +NOTE 1: BS antenna parameters: 32TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (8,2,2,1,1;8,2) + +\* Number of PDCCH symbols per slot = 1 + +\*\* Number of PDCCH symbols per slot = 2 + +\*\*\* Number of PDCCH symbols per slot = 0.5 + +\*\*\*\* Number of PDCCH symbols per slot = 4 + +**Table B.1.1-3: FR1, DL, UMa, VR/AR at 60 FPS** + +| Source | Tdoc Source | Scheme | TDD form at | SU/MU-MIMO | Data rate (Mbps) | PDB (ms) | Capacity (UEs/cell) | C1=floor (Capacity) | % of satisfied UEs when #UEs/cell =C1 | Notes | +|--------------|-------------|--------|-------------|------------|------------------|----------|---------------------|---------------------|---------------------------------------|------------| +| Source [ZTE] | R1-2209198 | 1.1** | DDD SU | SU-MIMO | 30 | 10 | 8.8 | 8 | 97% | Note 1 | +| Source [ZTE] | R1-2209198 | 1.7** | DDD SU | SU-MIMO | 30 | 10 | 7.6 | 7 | 96% | Note 1,2,4 | + +NOTE 1: BS antenna parameters: 64TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (8,8,2,1,1;4,8) + +NOTE 2: No symbol for PDCCH is reserved in the slot where no scheduling DCI is transmitted + +NOTE 3: Results did not consider any other PDCCH that may occupy the CORESET(s) than scheduling DCI, e.g. broadcast PDCCH + +NOTE 4: Results consider 2 symbols are used for PDCCH, if the slot is not the first slot of multiple TB scheduling for one UE but is the first slot of multiple TBs scheduling or the slot of single TB scheduling for another UE + +\* Number of PDCCH symbols per slot = 1 + +\*\* Number of PDCCH symbols per slot = 2 + +\*\*\* Number of PDCCH symbols per slot = 0.5 + +\*\*\*\* Number of PDCCH symbols per slot = 4 + +Based on the evaluation results in Table B.1.1-1 and Table B.1.1-3, the following observations regarding multi-PDSCH scheduling by a single DCI as compared to single PDSCH scheduling can be made: + +- For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is decreased from 9.8 UEs per cell with single-PDSCH scheduling to 8.81 UEs per cell with multi-PDSCH scheduling, where 1 symbol is always reserved for PDCCH transmission in each slot (capacity drop is -10%). Similar trend is observed when number of PDCCH symbols per slot is equal to 0.5 or 2 symbols. +- For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is increased from 9.8 UEs per cell with single-PDSCH scheduling to 10.37 UEs per cell with multi-PDSCH scheduling, where unoccupied CORESET in a slot can be re-used for PDSCH transmission (1 symbol for PDCCH transmission in each slot) (capacity gain is 6%). For VR/AR single-stream traffic model, 45Mbps, 10ms PDB, the results show similar trend. + +- For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is decreased from 10.25 UEs per cell with single-PDSCH scheduling to 10.1 UEs per cell with multi-PDSCH scheduling, where unoccupied CORESET in a slot can be re-used for PDSCH transmission (0.5 for PDCCH transmission in each slot) (capacity drop is -1.46%). +- For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [ZTE] that the capacity is decreased from 9.1 UEs per cell with single-PDSCH scheduling to 7.9 UEs per cell with multi-PDSCH scheduling, where 2 symbols per slot are used for PDCCH if there is at least one UE that needs to be scheduled with first TB out of multiple TBs (capacity drop is -13%). For FR1, UMa scenario, the results show similar trend. +- For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 60Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [ZTE] that the capacity is increased from 3.4 UEs per cell with single-PDSCH scheduling to 3.7 UEs per cell with multi-PDSCH scheduling, where 2 symbols per slot are used for PDCCH if there is at least one UE that needs to be scheduled with first TB out of multiple TBs (capacity gain is 8%). + +Based on the evaluation results in Table B.1.1-1 and Table B.1.1-2, the following observations regarding enhanced multi-PDSCH scheduling by a single DCI can be made: + +- For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is increased from 10.37 UEs per cell with multi-PDSCH scheduling to 10.59 UEs per cell with multi-PDSCH scheduling enhancement of early HARQ-ACK feedback (unoccupied CORESET in a slot can be re-used for PDSCH transmission, 1 symbol for PDCCH transmission in each slot) (capacity gain is 2.12%). +- For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is increased from 10.37 UEs per cell with multi-PDSCH scheduling to 11.09 UEs per cell with multi-PDSCH scheduling FDRA enhancement (unoccupied CORESET in a slot can be re-used for PDSCH transmission, 1 symbol for PDCCH transmission in each slot) (capacity gain is 7%). +- For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [InterDigital] that the capacity is increased from 5.3 UEs per cell with single-PDSCH scheduling to 7.2 UEs per cell with multi-PDSCH scheduling, where single PDCCH schedules up to 4 PDSCHs/PUSCHs and full flexibility in terms of resource (RB allocation) as well as MCS for each of the 4 PDSCHs/PUSCHs (capacity gain is 36%). For VR/AR single-stream traffic model, 45Mbps, 10ms PDB and for CG single-stream traffic model, 15ms PDB, the results show similar trend. +- For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [InterDigital] that the capacity is increased from 5.5 UEs per cell with single-PDSCH scheduling to 8.4 UEs per cell with multi-PDSCH scheduling, where single PDCCH schedules up to 4 PDSCHs/PUSCHs and full flexibility in terms of resource (RB allocation) as well as MCS for each of the 4 PDSCHs/PUSCHs (capacity gain is 53%). For VR/AR single-stream traffic model, 45Mbps, 10ms PDB and for CG single-stream traffic model, 15ms PDB, the results show similar trend. + +### B.1.2 Cooperative MIMO via DL interference probing based on SRS enhancement + +This clause captures the capacity performance evaluation results for cooperative MIMO in TDD with downlink interference probing via SRS and precoding via bi-directional training (BiT). In TDD system, channel UL-DL reciprocity is utilized to obtain DL channel state information for improved performance of single-cell (non-cooperative) MU-MIMO. However, inter-cell interference is still the bottleneck that limits further capacity improvement. + +The performance of MU-MIMO with zero forcing precoding (scheme 2.1 in Tables B.1.2-1,2) has been compared against Cooperative MIMO with DL interference probing (scheme 2.2 in Tables B.1.2-1,2). + +Scheme 2.2: Cooperative MIMO with DL interference probing via SRS and precoding via bi-directional training (BiT), is the scheme where SRS triggering and transmission are enhanced to directly reflect DL interference spatial information (utilizing UL-DL reciprocity). Each gNB performs its own (MU) scheduling and instructs the scheduled UEs to sound on the scheduled PRBs. Then by TDD reciprocity, a gNB seeing strong UL interference from a certain + +spatial direction on the SRS resources (for example, via estimating the UL spatial covariance matrix of interference signals) implies that in DL transmission the gNB will cause strong interference to UE(s) in that direction. The gNB can then adjust the precoding for DL interference avoidance during the PDSCH transmissions. Each gNB measures the corresponding UL SRS resources and adjusts its DL precoding accordingly to achieve multi-cell DL interference coordination/avoidance in a distributed way, and hence the so-called 'Bi-directional Training' (BiT). + +The performance results are reported in B.1.2-1 and B.1.2-2 in terms of the ratio of satisfied users. + +**Table B.1.2-1: FR1, DL, DU, VR/AR and Cloud Gaming at 60 FPS** + +| Source | Tdoc Source | Scheme | TDD form at | SU/MU-MIMO | Data rate (Mbps) | PDB (ms) | Capacity (UEs/cell) | C1=floor (Capacity) | % of satisfied UEs when #UEs/cell =C1 | Notes | +|---------------------|-------------|--------|-------------|------------|------------------|----------|---------------------|---------------------|---------------------------------------|--------| +| Source [Future wei] | R1-2208377 | 2.1 | DDD SU | MU-MIMO | 45 | 10 | 12.2 | 12 | 90% | Note 1 | +| | | | | | | 15 | 17.4 | 17 | 94% | | +| Source [Future wei] | R1-2208377 | 2.2 | DDD SU | MU-MIMO | 45 | 10 | 16.9 | 16 | 91% | Note 1 | +| | | | | | | 15 | 21.7 | 21 | 92% | | +| Source [Future wei] | R1-2208377 | 2.1 | DDD SU | MU-MIMO | 30 | 10 | 21.7 | 21 | 91% | Note 1 | +| | | | | | | 15 | 27.1 | 27 | 91% | | +| Source [Future wei] | R1-2208377 | 2.2 | DDD SU | MU-MIMO | 30 | 10 | 25.8 | 25 | 91% | Note 1 | +| | | | | | | 15 | 30.1 | 30 | 91% | | +| Source [Future wei] | R1-2208377 | 2.1 | DDD UU | MU-MIMO | 45 | 10 | 8 | 8 | 90% | Note 1 | +| | | | | | | 15 | 12.7 | 12 | 96% | | +| Source [Future wei] | R1-2208377 | 2.2 | DDD UU | MU-MIMO | 45 | 10 | 13.1 | 13 | 90% | Note 1 | +| | | | | | | 15 | 16.9 | 16 | 95% | | +| Source [Future wei] | R1-2208377 | 2.1 | DDD UU | MU-MIMO | 30 | 10 | 13.7 | 13 | 92% | Note 1 | +| | | | | | | 15 | 21.5 | 21 | 93% | | +| Source [Future wei] | R1-2208377 | 2.2 | DDD UU | MU-MIMO | 30 | 10 | 19.9 | 19 | 93% | Note 1 | +| | | | | | | 15 | 25.6 | 25 | 93% | | + +NOTE 1: BS antenna parameters: 64TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (8,8,2,1,1:4,8). + +**Table B.1.2-2: FR1, DL, UMa, VR/AR and Cloud Gaming at 60 FPS** + +| Source | Tdoc Source | Scheme | TDD form at | SU/MU-MIMO | Data rate (Mbps) | PDB (ms) | Capacity (UEs/cell) | C1=floor (Capacity) | % of satisfied UEs when #UEs/cell =C1 | Notes | +|---------------------|-------------|--------|-------------|------------|------------------|----------|---------------------|---------------------|---------------------------------------|--------| +| Source [Future wei] | R1-2208377 | 2.1 | DDD SU | MU-MIMO | 45 | 10 | 7 | 7 | 90% | Note 1 | +| | | | | | | 15 | 9.7 | 9 | 93% | | +| Source [Future wei] | R1-2208377 | 2.2 | DDD SU | MU-MIMO | 45 | 10 | 9 | 9 | 90% | Note 1 | +| | | | | | | 15 | 11.6 | 11 | 92% | | +| Source [Future wei] | R1-2208377 | 2.1 | DDD SU | MU-MIMO | 30 | 10 | 11.4 | 11 | 94% | Note 1 | +| | | | | | | 15 | 14.2 | 14 | 91% | | +| Source [Future wei] | R1-2208377 | 2.2 | DDD SU | MU-MIMO | 30 | 10 | 13.2 | 13 | 92% | Note 1 | +| | | | | | | 15 | 16 | 16 | 90% | | +| Source [Future wei] | R1-2208377 | 2.1 | DDD UU | MU-MIMO | 45 | 10 | 5.2 | 5 | 90% | Note 1 | +| | | | | | | 15 | 6.8 | 6 | 94% | | +| Source [Future | R1-2208377 | 2.2 | DDD UU | MU-MIMO | 45 | 10 | 6.6 | 6 | 93% | Note 1 | +| | | | | | | 15 | 9.4 | 9 | 91% | | + +| | | | | | | | | | | | +|--------------------------------------------------------------------------------------|------------|-----|--------|---------|----|----|------|----|-----|--------| +| Source [Futurewei] | R1-2208377 | 2.1 | DDD UU | MU-MIMO | 30 | 10 | 8.8 | 8 | 90% | Note 1 | +| | | | | | | 15 | 11.4 | 11 | 94% | | +| Source [Futurewei] | R1-2208377 | 2.2 | DDD UU | MU-MIMO | 30 | 10 | 10.4 | 10 | 92% | Note 1 | +| | | | | | | 15 | 13.3 | 13 | 93% | | +| NOTE 1: BS antenna parameters: 64TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (8,8,2,1,1:4,8). | | | | | | | | | | | + +Based on the evaluation results in Table B.1.2-1 and Table B.1.2-2, the following observations can be made: + +- For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with MU-MIMO, 64TxRU and DDDSU, it is observed from Source [Futurewei] that the capacity is increased from 21.7 UEs per cell with MU-MIMO and zero forcing precoding to 25.8 UEs per cell with Cooperative MIMO via SRS enhancements (capacity gain is 19%). For 15ms PDB, the capacity gain is 11%. For UMa scenario, the results show similar trend. +- For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 45Mbps, 10ms PDB, 60 FPS, with MU-MIMO, 64TxRU and DDDSU, it is observed from Source [Futurewei] that the capacity is increased from 12.2 UEs per cell with MU-MIMO and zero forcing precoding to 16.9 UEs per cell with Cooperative MIMO via SRS enhancements (capacity gain is 39%). For 15ms PDB, the capacity gain is 24%. For UMa scenario, the results show similar trend. +- For FR1, UMa, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 45Mbps, 10ms PDB, 60 FPS, with MU-MIMO, 64TxRU and DDDSU, it is observed from Source [Futurewei] that the capacity is increased from 7 UEs per cell with MU-MIMO and zero forcing precoding to 9 UEs per cell with Cooperative MIMO via SRS enhancements (capacity gain is 28%). For 15ms PDB, the capacity gain is 19%. +- For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with MU-MIMO, 64TxRU and DDDUU, it is observed from Source [Futurewei] that the capacity is increased from 13.7 UEs per cell with MU-MIMO and zero forcing precoding to 19.9 UEs per cell with Cooperative MIMO via SRS enhancements (capacity gain is 45%). For 15ms PDB, the capacity gain is 19%. +- For FR1, UMa, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with MU-MIMO, 64TxRU and DDDUU, it is observed from Source [Futurewei] that the capacity is increased from 8.8 UEs per cell with MU-MIMO and zero forcing precoding to 10.4 UEs per cell with Cooperative MIMO via SRS enhancements (capacity gain is 18%). For 15ms PDB, the capacity gain is 16%. +- For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 45Mbps, 10ms PDB, 60 FPS, with MU-MIMO, 64TxRU and DDDUU, it is observed from Source [Futurewei] that the capacity is increased from 8 UEs per cell with MU-MIMO and zero forcing precoding to 13.1 UEs per cell with Cooperative MIMO via SRS enhancements (capacity gain is 64%). For 15ms PDB, the capacity gain is 33%. +- For FR1, UMa, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 45Mbps, 10ms PDB, 60 FPS, with MU-MIMO, 64TxRU and DDDUU, it is observed from Source [Futurewei] that the capacity is increased from 5.2 UEs per cell with MU-MIMO and zero forcing precoding to 6.6 UEs per cell with Cooperative MIMO via SRS enhancements (capacity gain is 27%). For 15ms PDB, the capacity gain is 38%. + +### B.1.3 Enhanced CQI for CBG-based transmissions + +This clause captures the capacity performance evaluation results of enhanced CQI (eCQI) for code block group (CBG)-based transmissions. The use of CBG-based transmissions allows avoiding a re-transmission of the full transport block in case the receiver fails to correctly decode the full TB. A large size of one video frame as per TR 38.838, results in a large TB(s) size to convey a video frame. + +The performance of the current legacy link adaptation with TB-based transmission legacy CQI reporting (scheme 3.1 in Table B.1.3-1) has been compared against CBG-based transmission with eCQI (scheme 3.2 in Table B.1.3-1). The legacy CQI corresponds to the highest supported MCS while not exceeding a 10% BLER target for the TBs. + +Scheme 3.2: eCQI is the scheme where UE estimates the highest supported MCS (expressed via a CQI index), assuming that downlink transmissions occupy a set of downlink physical resource blocks termed the CSI reference resource with M code block groups, while the error probability of at most N failed code block groups does not exceed P. Parameters + +M, N, and P may be configured by the network, or fixed to values that are attractive for XR services. The configuration of the UE to use eCQI may be conducted with RRC signaling (note that configuration of current CQI schemes for a UE to use is also via RRC). The reporting of the eCQI can be in the form of an eCQI index (from current CQI tables [TS38.214 - Tables in 5.2.2.1] or enhanced CQI tables) that will guide the gNB to choose the supported modulation scheme, effective code rate, and overall efficiency that for its PDSCH transmissions. For the CBG-based transmission with eCQI, results are shown for parameter settings M=8 assuming either N=2 or N=4 and P= 50%. + +The performance results are reported in Table B.1.3-1 in terms of the ratio of satisfied users. + +**Table B.1.3-1: FR1, DL, InH, VR/AR and Cloud Gaming at 60 FPS** + +| Source | Tdoc Source | Scheme | TDD form at | SU/MU-MIMO | Data rate (Mbps) | PDB (ms) | Capacity (UEs/cell) | C1=floor (Capacity) | % of satisfied UEs when #UEs/cell =C1 | Notes | +|----------------|-------------|--------|-------------|------------|------------------|----------|---------------------|---------------------|---------------------------------------|----------| +| Source [Nokia] | R1-2209536 | 3.2* | DDD SU | SU-MIMO | 30 | 10 | 6.35 | 6 | 99% | Note 1,2 | +| | | | | | | 15 | 7.31 | 7 | 99% | | +| Source [Nokia] | R1-2209536 | 3.2* | DDD SU | SU-MIMO | 45 | 10 | 4.15 | 4 | 95% | Note 1,2 | +| | | | | | | 15 | 5.12 | 5 | 95% | | +| Source [Nokia] | R1-2209536 | 3.2** | DDD SU | SU-MIMO | 30 | 10 | 6.22 | 6 | 97% | Note 1,2 | +| | | | | | | 15 | 7.31 | 7 | 99% | | +| Source [Nokia] | R1-2209536 | 3.2** | DDD SU | SU-MIMO | 45 | 10 | 4.10 | 4 | 93% | Note 1,2 | +| | | | | | | 15 | 4.83 | 4 | 100% | | +| Source [Nokia] | R1-2209536 | 3.1 | DDD SU | SU-MIMO | 30 | 10 | 5.45 | 5 | 95% | Note 1 | +| | | | | | | 15 | 6.31 | 6 | 98% | | +| Source [Nokia] | R1-2209536 | 3.1 | DDD SU | SU-MIMO | 45 | 10 | 3.35 | 3 | 99% | Note 1 | +| | | | | | | 15 | 4.18 | 4 | 94% | | + +NOTE 1: BS antenna parameters: 32TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (4,4,2,1,1,4,4) +NOTE 2: non-iid CBG errors in a TB are assumed +\* At most N failed code block groups, N= 4 +\*\* At most N failed code block groups, N= 2 + +Based on the evaluation results in Table B.1.3-1, the following observations can be made: + +- For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [Nokia] that the capacity is increased from 5.45 UEs per cell with legacy CQI to 6.35 UEs per cell with eCQI, where the error probability of at most N=4 failed code block groups out of 8 CBGs does not exceed P = 50% (capacity gain is 17%). For N=2, the results show similar trend. +- For FR1, InH, DL, with 100MHz bandwidth for Cloud Gaming single-stream traffic model, 30Mbps, 15ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [Nokia] that the capacity is increased from 6.31 UEs per cell with legacy CQI to 7.31 users per cell with eCQI, where the error probability of at most N=4 failed code block groups out of 8 CBGs does not exceed P = 50% (capacity gain is 16%). For N=2, the results show similar trend. +- For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 45Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [Nokia] that the capacity is increased from 3.35 UEs per cell with legacy CQI to 4.15 UEs per cell with eCQI, where the error probability of at most N=4 failed code block groups out of 8 CBGs does not exceed P = 50% (capacity gain is 24%). For N=2, the results show similar trend. +- For FR1, InH, DL, with 100MHz bandwidth for Cloud Gaming single-stream traffic model, 45Mbps, 15ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [Nokia] that the capacity is increased from 4.18 UEs per cell with legacy CQI to 5.12 UEs per cell with eCQI, where the error probability of at most N=4 failed code block groups out of 8 CBGs does not exceed P = 50% (capacity gain is 22%). For N=2, the results show similar trend. + +### B.1.4 Enhanced CQI based on DMRS + +This clause captures the capacity performance evaluation results of DMRS-based enhanced CQI reporting where the initial transmission is based on legacy CQI reporting, while the retransmission is DMRS based CQI reporting. + +The performance of the current TB-based transmission with legacy CQI reporting (scheme 4.1 in Tables B.1.4) has been compared against CBG-based transmission (scheme 4.2 in Tables B.1.4) as well as TB-based re-transmission and DMRS-based CQI (scheme 4.3 in Tables B.1.4): + +- Scheme 4.1: TB-based re-transmission (baseline scheme). In this scheme, TB-based retransmission is applied with legacy CSI reporting. Different outer-loop link adaptation configurations are used. +- Scheme 4.2: CBG-based re-transmission. In this scheme, CBG-based retransmission is applied with legacy CSI reporting. Different outer-loop link adaptation configurations are used. The number of CBGs per TB is equal to 8. +- Scheme 4.3: TB-based re-transmission with DMRS-based CQI. In this scheme, TB-based transmission/retransmission is applied where for the initial TB transmission legacy CQI reporting is used, while for the retransmission DMRS-based CQI reporting is used. + +The performance results are reported in Table B.1.4-1 and Table B.1.4-2 in terms of the ratio of satisfied users. + +**Table B.1.4-1: FR1, DL, InH, VR/AR and Cloud Gaming at 60 FPS** + +| Source | Tdoc Source | Scheme | TDD format | SU/MU-MIMO | Data rate (Mbps) | PDB (ms) | Capacity (UEs/cell) | C1=floor (Capacity) | % of satisfied UEs when #UEs/cell = C1 | Notes | +|-------------------|-------------|--------|------------|------------|------------------|----------|---------------------|---------------------|----------------------------------------|------------| +| Source [Ericsson] | R1-2208402 | 4.1* | DDDSU | SU-MIMO | 30 | 10 | 8.03 | 8 | 90% | Note 1,2 | +| | | | | | | 15 | 10.22 | 10 | 92% | | +| Source [Ericsson] | R1-2208402 | 4.2* | DDDSU | SU-MIMO | 30 | 10 | 8.08 | 8 | 91% | Note 1,2,3 | +| | | | | | | 15 | 10.34 | 10 | 93% | | +| Source [Ericsson] | R1-2208402 | 4.3* | DDDSU | SU-MIMO | 30 | 10 | 8.52 | 8 | 93% | Note 1,2 | +| | | | | | | 15 | 11.37 | 11 | 94% | | +| Source [Ericsson] | R1-2208402 | 4.1** | DDDSU | SU-MIMO | 30 | 10 | 7.21 | 7 | 92% | Note 1,2 | +| | | | | | | 15 | 8.29 | 8 | 93% | | +| Source [Ericsson] | R1-2208402 | 4.2** | DDDSU | SU-MIMO | 30 | 10 | 7.25 | 7 | 93% | Note 1,2,3 | +| | | | | | | 15 | 8.33 | 8 | 93% | | +| Source [Ericsson] | R1-2208402 | 4.3** | DDDSU | SU-MIMO | 30 | 10 | 7.49 | 7 | 94% | Note 1,2 | +| | | | | | | 15 | 8.66 | 8 | 94% | | +| Source [Ericsson] | R1-2208402 | 4.1*** | DDDSU | SU-MIMO | 30 | 10 | 7.89 | 7 | 96% | Note 1,2 | +| | | | | | | 15 | 9.48 | 9 | 94% | | +| Source [Ericsson] | R1-2208402 | 4.2*** | DDDSU | SU-MIMO | 30 | 10 | 8.01 | 8 | 90% | Note 1,2,3 | +| | | | | | | 15 | 9.59 | 9 | 95% | | +| Source [Ericsson] | R1-2208402 | 4.3*** | DDDSU | SU-MIMO | 30 | 10 | 8.53 | 8 | 94% | Note 1,2 | +| | | | | | | 15 | 10.31 | 10 | 93% | | + +NOTE 1: BS antenna parameters: 32TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (4,4,2,1,1,4,4) +NOTE 2: Interleaved VRB-to-PRB mapping is applied +NOTE 3: iid CBG errors in a TB are assumed +\* without outer loop, BLER = 10% +\*\* with outer loop, BLER = 10% +\*\*\* with outer loop, BLER = 22% + +**Table B.1.4-2: FR1, DL, UMa, VR/AR and Cloud Gaming at 60 FPS** + +| Source | Tdoc Source | Scheme | TDD format | SU/MU-MIMO | Data rate (Mbps) | PDB (ms) | Capacity (UEs/cell) | C1=floor (Capacity) | % of satisfied UEs when #UEs/cell = C1 | Notes | +|-------------------|-------------|--------|------------|------------|------------------|----------|---------------------|---------------------|----------------------------------------|------------| +| Source [Ericsson] | R1-2208402 | 4.1* | DDDSU | SU-MIMO | 30 | 10 | 5.59 | 5 | 94% | Note 1,2 | +| | | | | | | 15 | 9.0 | 9 | 90% | | +| Source [Ericsson] | R1-2208402 | 4.2* | DDDSU | SU-MIMO | 30 | 10 | 5.80 | 5 | 95% | Note 1,2,3 | +| | | | | | | 15 | 9.15 | 9 | 91% | | +| Source [Ericsson] | R1-2208402 | 4.3* | DDDSU | SU-MIMO | 30 | 10 | 6.79 | 6 | 94% | Note 1,2 | +| | | | | | | 15 | 10.28 | 10 | 93% | | +| Source [Ericsson] | R1-2208402 | 4.1** | DDDSU | SU-MIMO | 30 | 10 | 5.88 | 5 | 96% | Note 1,2 | +| | | | | | | 15 | 7.26 | 7 | 92% | | +| Source [Ericsson] | R1-2208402 | 4.2** | DDDSU | SU-MIMO | 30 | 10 | 5.9 | 5 | 97% | Note 1,2,3 | +| | | | | | | 15 | 7.29 | 7 | 93% | | +| Source [Ericsson] | R1-2208402 | 4.3** | DDDSU | SU-MIMO | 30 | 10 | 6.13 | 6 | 91% | Note 1,2 | +| | | | | | | 15 | 7.40 | 7 | 93% | | +| Source [Ericsson] | R1-2208402 | 4.1*** | DDDSU | SU-MIMO | 30 | 10 | 6.40 | 6 | 93% | Note 1,2 | +| | | | | | | 15 | 8.24 | 8 | 92% | | +| Source [Ericsson] | R1-2208402 | 4.2*** | DDDSU | SU-MIMO | 30 | 10 | 6.46 | 6 | 93% | Note 1,2,3 | +| | | | | | | 15 | 8.32 | 8 | 93% | | +| Source [Ericsson] | R1-2208402 | 4.3*** | DDDSU | SU-MIMO | 30 | 10 | 7 | 7 | 90.0% | Note 1,2 | +| | | | | | | 15 | 8.84 | 8 | 96% | | + +NOTE 1: BS antenna parameters: 64TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (8,8,2,1,1;4,8) +NOTE 2: Interleaved VRB-to-PRB mapping is applied +NOTE 3: iid CBG errors in a TB are assumed +\* without outer loop, BLER = 10% +\*\* with outer loop, BLER = 10% +\*\*\* with outer loop, BLER = 22% + +Based on the evaluation results in Table B.1.4-1 and Table B.1.4-2, the following observations can be made: + +- For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [Ericsson] that the capacity is increased by 6%, 4% and 8% when DMRS-based CQI is used as compared to legacy CQI for outer-loop link adaptation configurations of 'disabled', BLER=10% and BLER=22%, respectively. +- For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 15ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [Ericsson] that the capacity is increased by 11%, 4% and 9% when DMRS-based CQI is used as compared to legacy CQI for outer-loop link adaptation configurations of 'disabled', BLER=10% and BLER=22%, respectively. +- For FR1, UMa, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is increased by 21%, 4% and 9% when DMRS-based CQI is used as compared to legacy CQI for outer-loop link adaptation configurations of 'disabled', BLER=10% and BLER=22%, respectively. +- For FR1, UMa, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 15ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is increased by 14%, 2% and 7% when DMRS-based CQI is used as compared to legacy CQI for outer-loop link adaptation configurations of 'disabled', BLER=10% and BLER=22%, respectively. + +### B.1.5 Soft HARQ-ACK enhancements + +This clause captures the capacity performance evaluation results of soft HARQ-ACK enhancements. HARQ allows to recover transport blocks that are not successfully decoded by means of retransmissions. It can be leveraged to use MCS close to what the radio channel can support while maintaining high reliability. The gNB chooses the MCS for a transmission based on its knowledge of the channel conditions, but it cannot always precisely predict how they evolve. + +The performance of Baseline HARQ-ACK (scheme 5.1 in Tables B.1.5-1,2,3) has been compared against different schemes with soft HARQ-ACK. Particularly, the following schemes, with soft HARQ-ACK, have been evaluated: + +- Scheme 5.2: Soft HARQ-ACK indicating delta MCS: UE provides enhanced HARQ-ACK feedback beyond the single bit ACK/NACK status in the form of a Delta MCS based on PDSCH decoding. The soft HARQ-ACK feedback uses SINR measurements done on each TB and link curves obtained from link level simulations. Then the information the UE feeds back to the gNB is an estimation of how far the experienced SINR is from the SINR that would allow a reliable decoding of the TB. +- Scheme 5.3: Soft HARQ-ACK indicating number of redundant transmissions: 2-bit soft-HARQ feedback is reported by the UE and used by the gNB scheduler. The 2-bit soft-HARQ feedback represents 4 states: ACK, and NACK with n=1, 2, or 3, where "n" indicates how many redundant transmissions are requested by the UE. + +The performance results are reported in Table B.1.5-1, Table B.1.5-2, Table B.1.5-3 in terms of the ratio of satisfied users. + +**Table B.1.5-1: FR1, DL, InH, VR/AR at 60 FPS** + +| Source | Tdoc Source | Scheme | TDD form at | SU/MU-MIMO | Data rate (Mbps) | PDB (ms) | Capacity (UEs/cell) | C1=floor (Capacity) | % of satisfied UEs when #UEs/cell =C1 | Notes | +|--------------------|-------------|--------|-------------|------------|------------------|----------|---------------------|---------------------|---------------------------------------|--------| +| Source [Qualco mm] | R1-2210003 | 5.2* | DDD SU | MU-MIMO | 60 | 10 | 2.93 | 2 | 97.7% | Note 1 | +| | | | | | 45 | | 5.4 | 5 | 92.3% | | +| | | | | | 30 | | 8.96 | 8 | 95% | | +| Source [Qualco mm] | R1-2210003 | 5.1* | DDD SU | MU-MIMO | 60 | 10 | 0 | 0 | N.A. | Note 1 | +| | | | | | 45 | | 4.5 | 4 | 93.1% | | +| | | | | | 30 | | 8.5 | 8 | 92.9% | | +| Source [Qualco mm] | R1-2210003 | 5.2** | DDD SU | MU-MIMO | 60 | 10 | 2.1 | 2 | 91.25% | Note 1 | +| | | | | | 45 | | 4.1 | 4 | 91%% | | +| | | | | | 30 | | 7.8 | 7 | 93.5% | | +| Source [Qualco mm] | R1-2210003 | 5.1** | DDD SU | MU-MIMO | 60 | 10 | 0 | 0 | N.A. | Note 1 | +| | | | | | 45 | | 0 | 0 | N.A. | | +| | | | | | 30 | | 0 | 0 | N.A. | | +| Source [Qualco mm] | R1-2210003 | 5.2*** | DDD SU | MU-MIMO | 60 | 10 | 1.17 | 1 | 91.25% | Note 1 | +| Source [Qualco mm] | R1-2210003 | 5.1*** | DDD SU | MU-MIMO | 60 | 10 | 0 | 0 | N.A. | Note 1 | +| Source [ZTE] | R1-2203607 | 5.2*** | DDD SU | MU-MIMO | 60 | 10 | 3.3 | 3 | 93% | Note 1 | +| Source [ZTE] | R1-2203607 | 5.1*** | DDD SU | MU-MIMO | 60 | 10 | 0 | 0 | N.A. | Note 1 | + +NOTE 1: BS antenna parameters: 32TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (4,4,2,1,1;4,4) +\* gNB processing delay k3 (from HARQ feedback to retransmission) = 4 slots +\*\* gNB processing delay k3 (from HARQ feedback to retransmission) = 6 slots +\*\*\* gNB processing delay k3 (from HARQ feedback to retransmission) = 8 slots + +**Table B.1.5-2: FR1, DL, DU, VR/AR at 60 FPS** + +| Source | Tdoc Source | Scheme | TDD form at | SU/MU-MIMO | Data rate (Mbps) | PDB (ms) | Capacity (UEs/cell) | C1=floor (Capacity) | % of satisfied UEs when #UEs/cell =C1 | Notes | +|--------|-------------|--------|-------------|------------|------------------|----------|---------------------|---------------------|---------------------------------------|-------| +|--------|-------------|--------|-------------|------------|------------------|----------|---------------------|---------------------|---------------------------------------|-------| + +| | | | | | | | | | | | +|---------------------|------------|---------|--------|---------|----|----|------|----|-------|--------| +| Source [Qualco mm] | R1-2210003 | 5.2* | DDD SU | MU-MIMO | 60 | 10 | 4.6 | 4 | 94.5% | Note 1 | +| | | | | | 45 | | 7.5 | 7 | 93% | | +| | | | | | 30 | | 11.9 | 11 | 94.1% | | +| Source [Qualco mm] | R1-2210003 | 5.1* | DDD SU | MU-MIMO | 60 | 10 | 0 | 0 | N.A. | Note 1 | +| | | | | | 45 | | 6.6 | 6 | 92.2% | | +| | | | | | 30 | | 11.3 | 11 | 91.3% | | +| Source [Qualco mm] | R1-2210003 | 5.2** | DDD SU | MU-MIMO | 60 | 10 | 2.8 | 2 | 92.9% | Note 1 | +| | | | | | 45 | | 5.5 | 5 | 92.4% | | +| | | | | | 30 | | 10.4 | 10 | 92% | | +| Source [Qualco mm] | R1-2210003 | 5.1** | DDD SU | MU-MIMO | 60 | 10 | 0 | 0 | N.A. | Note 1 | +| | | | | | 45 | | 0 | 0 | N.A. | | +| | | | | | 30 | | 0 | 0 | N.A. | | +| Source [Qualco mm] | R1-2210003 | 5.2*** | DDD SU | MU-MIMO | 60 | 10 | 2 | 2 | 90.1% | Note 1 | +| Source [Qualco mm] | R1-2210003 | 5.1*** | DDD SU | MU-MIMO | 60 | 10 | 0 | 0 | N.A. | Note 1 | +| Source [Future wei] | R1-2208377 | 5.1**** | DDD UU | MU-MIMO | 45 | 10 | 8.4 | 8 | 91% | Note 1 | +| Source [Future wei] | R1-2208377 | 5.3**** | DDD UU | MU-MIMO | 45 | 10 | 7.9 | 7 | 90% | Note 1 | + +NOTE 1: BS antenna parameters: 64TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (8,8,2,1,1:4,8) + +\* gNB processing delay k3 (from HARQ feedback to retransmission) = 4 slots + +\*\* gNB processing delay k3 (from HARQ feedback to retransmission) = 6 slots + +\*\*\* gNB processing delay k3 (from HARQ feedback to retransmission) = 8 slots + +\*\*\*\* UE processing delay and gNB processing delay = 10 slots + +**Table B.1.5-3: FR1, DL, UMa, VR/AR at 60 FPS** + +| Source | Tdoc Source | Scheme | TDD form at | SU/MU-MIMO | Data rate (Mbps) | PDB (ms) | Capacity (UEs/cell) | C1=floor (Capacity) | % of satisfied UEs when #UEs/cell =C1 | Notes | +|-----------------------------------------------------------------------------------------------------------------------------------------------------|-------------|---------|-------------|------------|------------------|----------|---------------------|---------------------|---------------------------------------|--------| +| Source [Future wei] | R1-2208377 | 5.1**** | DDD UU | MU-MIMO | 45 | 10 | 6.2 | 6 | 90.3% | Note 1 | +| Source [Future wei] | R1-2208377 | 5.3**** | DDD UU | MU-MIMO | 45 | 10 | 6.1 | 6 | 91.3% | Note 1 | +| NOTE 1: BS antenna parameters: 64TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (8,8,2,1,1:4,8)
**** UE processing delay and gNB processing delay = 10 slots | | | | | | | | | | | + +Based on the evaluation results in Table B.1.5-1, Table B.1.5-2, Table B.1.5-3 the following observations can be made: + +- For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Qualcomm] that the capacity is increased from 11.3 UEs per cell with baseline HARQ-ACK to 11.9 UEs per cell with soft HARQ-ACK indicating delta MCS based on PDSCH decoding and k3=4 slots (capacity gain is 5%). For InH scenario, the results show similar trend. +- For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 45Mbps, 10ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Qualcomm] that the capacity is increased from 6.6 UEs per cell with baseline HARQ-ACK to 7.5 UEs per cell with soft HARQ-ACK indicating delta MCS based on PDSCH decoding and k3=4 slots (capacity gain is 14%). For InH scenario, the results show similar trend. +- For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 60Mbps, 10ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Qualcomm] that the capacity is increased from 0 UEs per cell with baseline HARQ-ACK to 4.6 UEs per cell with soft HARQ-ACK indicating delta MCS based on PDSCH decoding and k3=4 slots. For InH scenario, the results show similar trend. + +- For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Qualcomm] that the capacity is increased from 0 UEs per cell with baseline HARQ-ACK to 10.4 UEs per cell with soft HARQ-ACK indicating delta MCS based on PDSCH decoding and k3=6 slots. For InH scenario, the results show similar trend. +- For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 45Mbps, 10ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Qualcomm] that the capacity is increased from 0 UEs per cell with baseline HARQ-ACK to 5.5 UEs per cell with soft HARQ-ACK indicating delta MCS based on PDSCH decoding and k3=6 slots. For InH scenario, the results show similar trend. +- For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 60Mbps, 10ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Qualcomm] that the capacity is increased from 0 UEs per cell with baseline HARQ-ACK to 2.8 UEs per cell with soft HARQ-ACK indicating delta MCS based on PDSCH decoding and k3=6 slots. For InH scenario, the results show similar trend. +- For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 60Mbps, 10ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Qualcomm] that the capacity is increased from 0 UEs per cell with baseline HARQ-ACK to 2 UEs per cell with soft HARQ-ACK indicating delta MCS based on PDSCH decoding and k3=8 slots. For InH scenario, the results show similar trend. +- For FR1, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 60Mbps, 10ms PDB, 60 FPS, with MU-MIMO, it is observed from Source [ZTE] that the capacity is increased from 0 UEs per cell with baseline HARQ-ACK to 3.3 UEs per cell with soft HARQ-ACK indicating delta MCS based on PDSCH decoding and k3=8 slots. +- For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 45Mbps, 10ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Futurewei] that the capacity is decreased from 8.4 UEs per cell with baseline HARQ-ACK to 7.9 UEs per cell with soft HARQ-ACK indicating how many redundant transmissions are requested by the UE (capacity drop is -6%). +- For FR1, UMa, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 45Mbps, 10ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Futurewei] that the capacity is decreased from 6.2 UEs per cell with baseline HARQ-ACK to 6.1 UEs per cell with soft HARQ-ACK indicating how many redundant transmissions are requested by the UE (capacity drop is -2%). + +### B.1.6 Configured grant scheduling + +This clause captures the capacity performance evaluation results for configured grant scheduling. A UE can transmit UL data using CG resources after configuration (of a CG Config Type 1) or activation (of a CG Config Type 2), without the need of receiving UL grant from the gNB. + +The performance of dynamic grant (DG) scheduling has been compared against configured grant (CG) scheduling. Particularly, the following schemes have been evaluated: + +- Scheme 6.1.1: DG scheduling with SR followed by UL grant with BSR and data. It is assumed that an SR is triggered upon arrival of a new XR packet in the UE buffer. An UL resource is then granted to the UE to transmit BSR and a number of UL data. A periodicity of SR and a size of initial UL grant may vary and are indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3. +- Scheme 6.1.2: DG scheduling with SR followed by UL grant with BSR only. A periodicity of SR may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3. +- Scheme 6.2: Pre-scheduling dynamic grant: The scheduling is based on dynamic grants where it is assumed that the network is provided with XR traffic periodicity. An initial grant to the UE when its traffic is expected is transmitted (implementation-based learning) without using SR. A size of initial UL grant may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3. +- Scheme 6.3: Dynamic scheduling with genie BSR (DG with genie BSR): The scheduling is based on dynamic grants where it is assumed BSR is available with zero delay at the scheduler when a new XR packet arrives in the UE buffer, to be used for indicating UL grants to the UE. Hence, in this case, no SR or BSR delay is assumed. + +- Scheme 6.4: Single CG configuration, where single PUSCH occasion per CG period is pre-configured with certain periodicity without relying on SR. In this scheme no scheduling delay is assumed. CG periodicity may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3. +- Scheme 6.5.1: Multiple CG configurations, where multiple PUSCH occasions per CG period are pre-configured with certain periodicity without relying on SR. In this scheme no scheduling delay is assumed. CG periodicity may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3. +- Scheme 6.5.2: Multiple CG configurations, where multiple PUSCH occasions per CG period are pre-configured with certain periodicity without relying on SR. In this scheme scheduling delay for scheduling more packets with DG is assumed as 2.5 ms. CG periodicity may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3. +- Scheme 6.6.1: Hybrid CG+DG scheduling – the scheduling is based on a combined use of configured and dynamic grants. SR resources are not used. Instead, CG resources are configured with a certain size in UL slot in order to transmit BSR and data when a new XR packet arrives. Whenever a new XR packet arrives in the UE buffer, the UE uses the nearest possible CG PUSCH occasion for BSR transmission and possibly some amount of data. The network can thus use the BSR to provide dynamic grants for the following data transmission. CG periodicity and size of CG grant may vary and are indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3. +- Scheme 6.6.2: Hybrid CG+DG scheduling – the scheduling is based on a combined use of configured and dynamic grants. SR resources are not used. Instead, CG resources are configured with a certain size in order to transmit BSR only when a new XR packet arrives. It is assumed that one PUSCH occasion per CG period is pre-configured with certain periodicity to align PUSCH occasions with XR packets. Whenever a new XR packet arrives in the UE buffer, the UE uses the nearest possible CG PUSCH occasion for BSR transmission. The network can thus use the BSR to provide dynamic grants for the corresponding data scheduling. CG periodicity and size of CG grant may vary and are indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3. +- Scheme 6.6.3: Hybrid CG+DG scheduling – the scheduling is based on a combined use of configured and dynamic grants. SR resources are not used. Instead, CG resources are configured with a certain size in UL slot in order to transmit BSR and data when a new XR packet arrives. Whenever a new XR packet arrives in the UE's buffer, the UE uses the nearest possible CG PUSCH occasion for BSR transmission and possibly some amount of data. The network can thus use the BSR to provide dynamic grants for the following data transmission. The PDCCH monitoring window for the dynamic grant is pre-configured and associated with the CG PUSCH occasion in each CG period. The enhanced BSR that the BSR report will be triggered at the first used CG PUSCH occasion in each CG period to indicate to the gNB the remaining packet size is assumed. If the BSR is reported by the UE with the status "not empty", the UE would monitor PDCCH in the subsequent slots for dynamic grant after XR packet transmission with the CG resource, in which the dynamic grant is used to schedule the remaining data of XR packet. If the BSR is reported by the UE with the status "empty", the UE would not monitor PDCCH in the subsequent slots of the PDCCH monitoring window for XR packet transmission. Furthermore, if the XR packets are completely transmitted during the monitoring window, the UE can be indicated to go to sleep. If the XR packets arrive during the monitoring window, the UE can be indicated to skip the PDCCH monitoring until the packets arrive. CG periodicity and size of CG grant may vary and are indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3. +- Scheme 6.7: Enhanced CG with flexible resource allocation, where at least one PUSCH occasion per CG period is pre-configured with certain periodicity without relying on SR. In this scheme, it is assumed the UE can indicate to gNB unused CG PUSCH resources via CG-UCI. CG periodicity may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3. +- Scheme 6.8: Enhanced CG with dynamic adaptation of CG parameters and indication of unused/used CG PUSCH occasion(s). In this scheme, the UE adjusts CG parameters dynamically: MCS, number of PRBs, number of layers within the CG resource. The UE indicates these scheduling parameters to the gNB via UCI transmitted separately in the same CG resource, and whether the subsequent CG PUSCH occasions will be used/unused until next XR packet arrival. It is assumed that at least one PUSCH occasion per CG period is pre-configured with certain periodicity without relying on SR. CG periodicity may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3. +- Scheme 6.9: Enhanced CG with indication of unused/used CG PUSCH occasion(s), where the UE only indicates if the subsequent CG PUSCH occasions will be used/unused until next XR packet arrival. It is assumed that at least one PUSCH occasion per CG period is pre-configured with certain periodicity without relying on SR. CG periodicity may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3. + +- Scheme 6.10: Enhanced CG with MAC CE based dynamic resource adjustment indication. In this scheme, CG resource is used to carry MAC CE based dynamic resource adjustment indication and video data, and resource adjustment indication delay based on MAC CE is 2.5ms. It is assumed that at least one PUSCH occasion per CG period is pre-configured with certain periodicity to align PUSCH occasions with XR packets without relying on SR. CG periodicity may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3. +- Scheme 6.11: Enhanced CG with UCI based dynamic resource adjustment indication. In this scheme, CG resource is used to carry UCI based dynamic resource adjustment indication and video data, and resource adjustment indication delay based on UCI is 0.5ms. It is assumed that at least one PUSCH occasion per CG period is pre-configured with certain periodicity to align PUSCH occasions with XR packets without relying on SR. CG periodicity may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3. +- Scheme 6.12: Enhanced CG with UCI based dynamic resource adjustment indication. In this scheme, CG resource is used to carry UCI based dynamic resource adjustment indication only, and the dynamic resource adjustment indication is used to inform the gNB data volume of an XR packet or required resources to transmit the XR packet. Resource adjustment indication delay based on UCI is 0.5ms. It is assumed that one PUSCH occasion per CG period is pre-configured with certain periodicity to align PUSCH occasions with XR packets without relying on SR. CG periodicity may vary and is indicated separately in Table B.1.6-1, Table B.1.6-2, Table B.1.6-3. + +Table B.1.6-1: FR1, UL, InH, AR at 60 FPS + +| Source | Tdoc Source | Scheme | TDD form at | SU/MU-MIMO | Data rate (Mbps) | PDB (ms) | Capacity (UEs/cell) | C1=floor (Capacity) | % of satisfied UEs when #UEs/cell =C1 | Notes | +|-----------------------|-------------|----------|-------------|------------|------------------|----------|---------------------|---------------------|---------------------------------------|------------------| +| Source [CATT] | R1-2211175 | 6.1.1 | DDD UU | SU-MIMO | 10 | 30 | 5.4 | 5 | 90% | Note 1,2,15 | +| Source [CATT] | R1-2211175 | 6.4* | DDD UU | SU-MIMO | 10 | 30 | <1 | 0 | N.A. | Note 1 | +| Source [CATT] | R1-2211175 | 6.6.3* | DDD UU | SU-MIMO | 10 | 30 | 7.3 | 7 | 91% | Note 1,10,17 | +| Source [CATT] | R1-2211175 | 6.2* | DDD UU | SU-MIMO | 10 | 30 | 7.2 | 7 | 90% | Note 1,13,16 | +| Source [InterDigital] | R1-2211843 | 6.1.1 | DDD SU | SU-MIMO | 10 | 30 | 7.1 | 7 | 91% | Note 1,2,12,18 | +| | | | | | | 10 | 2 | 2 | 100% | | +| Source [InterDigital] | R1-2211843 | 6.4** | DDD SU | SU-MIMO | 10 | 30 | 6 | 6 | 100% | Note 1 | +| | | | | | | 10 | 4.7 | 4 | 98% | | +| Source [InterDigital] | R1-2211843 | 6.7** | DDD SU | SU-MIMO | 10 | 30 | 7.5 | 7 | 100% | Note 1 | +| | | | | | | 10 | 5.2 | 5 | 99% | | +| Source [vivo] | R1-2212595 | 6.5.2*** | DDD SU | SU-MIMO | 10 | 30 | 11.3 | 11 | 92.42% | Note 1,7,14 | +| | | | | | | 10 | 6.22 | 6 | 93.26% | | +| Source [vivo] | R1-2212595 | 6.10*** | DDD SU | SU-MIMO | 10 | 30 | 11.85 | 11 | 93.46% | Note 1,7 | +| | | | | | | 10 | 6.42 | 6 | 94.44% | | +| Source [vivo] | R1-2212595 | 6.11*** | DDD SU | SU-MIMO | 10 | 30 | 12.87 | 12 | 95.18% | Note 1,7 | +| | | | | | | 10 | 7.81 | 7 | 96.23% | | +| Source [vivo] | R1-2212595 | 6.6.2*** | DDD SU | SU-MIMO | 10 | 30 | 13.96 | 13 | 94.08% | Note 1,8,14 | +| | | | | | | 10 | 6.12 | 6 | 92.13% | | +| Source [vivo] | R1-2212595 | 6.12*** | DDD SU | SU-MIMO | 10 | 10 | 8.79 | 8 | 93.52% | Note 1,8 | +| Source [vivo] | R1-2212595 | 6.5.2*** | DDD SU | SU-MIMO | 10 | 10 | 7.53 | 7 | 94.41% | Note 1,9,14 | +| Source [vivo] | R1-2212595 | 6.11*** | DDD SU | SU-MIMO | 10 | 10 | 8.83 | 8 | 93.92% | Note 1,9 | +| Source [vivo] | R1-2212595 | 6.1.1*** | DDD SU | SU-MIMO | 10 | 30 | 13.94 | 13 | 93.96% | Note 1,3,4,11,13 | +| | | | | | | 10 | 2.33 | 2 | 95.69% | | +| Source | R1- | 6.1.1*** | DDD | SU- | 10 | 30 | 13.82 | 13 | 93.5% | Note | + +| | | | | | | | | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------|-----------|---------|----|----|-------|----|--------|-----------------| +| [vivo] | 2212595 | | SU | MIMO | | 10 | 0 | 0 | N.A. | 1,5,6,1
1,14 | +| Source [vivo] | R1-2212595 | 6.5.2*** | DDD
UU | SU-MIMO | 10 | 30 | 13.41 | 13 | 91.67% | Note | +| | | | | | | 10 | 10.13 | 10 | 94.18% | 1,7,14 | +| Source [vivo] | R1-2212595 | 6.10*** | DDD
UU | SU-MIMO | 10 | 30 | 13.85 | 13 | 92.72% | Note | +| | | | | | | 10 | 10.76 | 10 | 94.61% | 1,7 | +| Source [vivo] | R1-2212595 | 6.11*** | DDD
UU | SU-MIMO | 10 | 30 | 14.94 | 14 | 92.45% | Note | +| | | | | | | 10 | 14.54 | 14 | 93.07% | 1,7 | +| Source [vivo] | R1-2212595 | 6.6.2*** | DDD
UU | SU-MIMO | 10 | 30 | 16.73 | 16 | 92.26% | Note | +| | | | | | | 10 | 6.57 | 6 | 95.15% | 1,8,14 | +| Source [vivo] | R1-2212595 | 6.1.1*** | DDD
UU | SU-MIMO | 10 | 30 | 15.56 | 15 | 93.42% | Note | +| | | | | | | 10 | 3.51 | 3 | 93.24% | 1,3,4,1
1,14 | +| Source [vivo] | R1-2212595 | 6.1.1*** | DDD
UU | SU-MIMO | 10 | 30 | 15.2 | 15 | 92.8% | Note | +| | | | | | | 10 | 0 | 0 | N.A. | 1,5,6,1
1,14 | +| Source [vivo] | R1-2212595 | 6.12*** | DDD
UU | SU-MIMO | 10 | 10 | 10.32 | 10 | 94.17% | Note
1,8 | +| Source [vivo] | R1-2212595 | 6.5.2*** | DDD
UU | SU-MIMO | 10 | 10 | 13.63 | 13 | 92.46% | Note
1,9,14 | +| Source [vivo] | R1-2212595 | 6.11*** | DDD
UU | SU-MIMO | 10 | 10 | 15.15 | 15 | 92.21% | Note
1,9 | +| Note 1: BS antenna parameters: 32TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (4,4,2,1,1;4,4)
Note 2: SR periodicity = 5 ms
Note 3: SR delay = 3 ms
Note 4: SR delay contains at least: delay for aligning to the nearest SR transmission occasion when an XR packet arrives, gNB processing delay for the reported SR.
Note 5: SR delay = 5 ms
Note 6: SR delay contains at least: delay for aligning to the nearest SR transmission occasion when an XR packet arrives, gNB processing delay for the reported SR.
Note 7: Size of configured grant = 166.7 kbit, and the number of PUSCH occasions depends on some factors such as channel quality of the UE, and available resource, etc.
Note 8: Size of configured grant = 80 bit
Note 9: Size of configured grant = 83.4 kbit, and the number of PUSCH occasions depends on some factors such as channel quality of the UE, and available resource, etc.
Note 10: Size of configured grant = 12096 bytes (128 PRBs with MCS 24)
Note 11: Size of initial UL grant = 83.4 kbit
Note 12: Size of initial UL grant = 400 kbits
Note 13: Size of initial UL grant = 128 PRBs with dynamic MCS selection
Note 14: BSR delay = 2.5 ms
Note 15: Scheduling delay is 5 ms-15 ms
Note 16: Scheduling delay is 0 ms-15 ms
Note 17: Scheduling delay is 2 ms-15 ms
Note 18: Scheduling delay = 5ms
* CG periodicity = 16 ms
** CG periodicity = 10 ms
*** CG periodicity pattern = (17,17,16) ms to align each CG occasion with a corresponding XR packet | | | | | | | | | | | + +Table B.1.6-2: FR1, UL, DU, AR at 60 FPS + +| Source | Tdoc Source | Scheme | TDD form at | SU/MU-MIMO | Data rate (Mbps) | PDB (ms) | Capacity (UEs/cell) | C1=floor (Capacity) | % of satisfied UEs when #UEs/cell =C1 | Notes | +|-------------------|-------------|--------|-------------|------------|------------------|----------|---------------------|---------------------|---------------------------------------|--------------| +| Source [Ericsson] | R1-2210923 | 6.1.1 | DDD
SU | SU-MIMO | 10 | 30 | 6.42 | 6 | 92% | Note | +| | | | | | | 15 | 0.68 | 0 | N.A. | 1,2,13,22 | +| Source [Ericsson] | R1-2210923 | 6.1.1 | DDD
SU | SU-MIMO | 10 | 30 | 6.8 | 6 | 95% | Note | +| | | | | | | 15 | 2.06 | 2 | 90% | 1,2,14,18,22 | +| Source [Ericsson] | R1-2210923 | 6.2 | DDD
SU | SU-MIMO | 10 | 30 | 6.86 | 6 | 95% | Note | +| | | | | | | 15 | 4.54 | 4 | 93% | 1,2,14,22 | +| Source | R1- | 6.4* | DDD | SU- | 10 | 30 | 6.35 | 6 | 93% | Note | + +| | | | | | | | | | | | +|-------------------|------------|-----------|--------|---------|----|----|------|---|--------|--------------------| +| [Ericsson] | 2210923 | 6.4** | SU | MIMO | | 15 | 2.75 | 2 | 92% | 1,2,10,19 | +| Source [Ericsson] | R1-2210923 | 6.6.1* | DDD SU | SU-MIMO | 10 | 30 | 6.97 | 6 | 95% | Note 1,2,10,18,22 | +| | | 6.6.1** | | | | 15 | 4.97 | 4 | 94% | | +| Source [Ericsson] | R1-2210923 | 6.3 | DDD SU | SU-MIMO | 10 | 30 | 7.1 | 7 | 91% | Note 1,2 | +| | | | | | | 15 | 5.02 | 5 | 90% | | +| Source [Huawei] | R1-2212650 | 6.1.1 | DDD SU | MU-MIMO | 10 | 10 | 0 | 0 | N.A. | Note 1,3,15,18,24 | +| Source [Huawei] | R1-2212650 | 6.1.1 | DDD SU | MU-MIMO | 10 | 10 | 0 | 0 | N.A. | Note 1,3,16,18,24 | +| Source [Huawei] | R1-2212650 | 6.2 | DDD SU | MU-MIMO | 10 | 10 | 1.7 | 1 | 94.29% | Note 1,15,16,19,24 | +| Source [Huawei] | R1-2212650 | 6.4*** | DDD SU | MU-MIMO | 10 | 10 | 1 | 1 | 90.95% | Note 1,12 | +| Source [Huawei] | R1-2212650 | 6.1.1 | DDD SU | MU-MIMO | 10 | 15 | 0 | 0 | N.A. | Note 1,3,15,18,24 | +| Source [Huawei] | R1-2212650 | 6.1.1 | DDD SU | MU-MIMO | 10 | 15 | 0 | 0 | N.A. | Note 1,3,16,18,20 | +| Source [Huawei] | R1-2212650 | 6.2 | DDD SU | MU-MIMO | 10 | 15 | >3 | 3 | 96% | Note 1,16,19,24 | +| Source [Huawei] | R1-2212650 | 6.6.1*** | DDD SU | MU-MIMO | 10 | 15 | 0 | 0 | N.A. | Note 1,12,22 | +| Source [Huawei] | R1-2212650 | 6.5.2*** | DDD SU | MU-MIMO | 10 | 15 | 1.4 | 1 | 97.14% | Note 1,9,12,22 | +| Source [Huawei] | R1-2212650 | 6.9*** | DDD SU | MU-MIMO | 10 | 15 | 1.7 | 1 | 98.57% | Note 1,12,21,22 | +| Source [Sony] | R1-2211625 | 6.1.1 | DDD SU | SU-MIMO | 10 | 10 | 0 | 0 | N.A. | Note 1,3,14,23 | +| | | | | | | 15 | 3 | 3 | 90% | | +| | | | | | | 30 | 6.35 | 6 | 91% | | +| Source [Sony] | R1-2211625 | 6.4** | DDD SU | SU-MIMO | 10 | 10 | 0 | 0 | N.A. | Note 1 | +| Source [Sony] | R1-2211625 | 6.8** | DDD SU | SU-MIMO | 10 | 10 | 4 | 4 | 90% | Note 1,10,21 | +| | | 6.8** | | | | 15 | 4.4 | 4 | 92.5% | Note 1,10,21 | +| | | 6.8* | | | | 30 | 6.4 | 6 | 96.5% | Note 1,11,21 | +| Source [Sony] | R1-2211625 | 6.9** | DDD SU | SU-MIMO | 10 | 10 | 1.6 | 1 | 96% | Note 1,10,21 | +| | | 6.9** | | | | 15 | 3.25 | 3 | 92.5% | Note 1,10,21 | +| | | 6.9* | | | | 30 | 6 | 6 | 90% | Note 1,11,21 | +| Source [ZTE] | R1-2211906 | 6.5.1**** | DDD SU | SU-MIMO | 20 | 30 | <1 | 0 | N.A. | Note 1,4 | +| | | | | | | 15 | <1 | 0 | N.A. | | +| | | | | | | 10 | <1 | 0 | N.A. | | +| Source | R1- | 6.1.2 | DDD | SU- | 20 | 30 | 3.5 | 3 | 94% | Note | + +| | | | | | | | | | | | +|--------------|------------|-----------|--------|---------|----|----|-----|---|------|----------------------| +| [ZTE] | 2211906 | | SU | MIMO | | 15 | <1 | 0 | N.A. | 1,3,23 | +| | | | | | | 10 | <1 | 0 | N.A. | | +| Source [ZTE] | R1-2211906 | 6.1.1 | DDD SU | SU-MIMO | 20 | 30 | 3.6 | 3 | 95% | Note 1,3,17, 22 | +| | | | | | | 15 | 2.1 | 2 | 91% | | +| | | | | | | 10 | <1 | 0 | N.A. | | +| Source [ZTE] | R1-2211906 | 6.9**** | DDD SU | SU-MIMO | 20 | 30 | 3.9 | 3 | 96% | Note 1,5 | +| | | | | | | 15 | 3.5 | 3 | 93% | | +| | | | | | | 10 | 2.6 | 2 | 95% | | +| Source [ZTE] | R1-2211906 | 6.6.1**** | DDD SU | SU-MIMO | 20 | 30 | 3.7 | 3 | 95% | Note 1, 8, 11,22, 25 | +| | | | | | | 15 | 2.1 | 2 | 91% | | +| | | | | | | 10 | <1 | 0 | N.A. | | +| Source [ZTE] | R1-2211906 | 6.1.1 | DDD SU | SU-MIMO | 20 | 30 | 3.4 | 3 | 93% | Note 1,3,20, 22 | +| | | | | | | 15 | <1 | 0 | N.A. | | +| Source [ZTE] | R1-2211906 | 6.6.1**** | DDD SU | SU-MIMO | 20 | 30 | 3.5 | 3 | 93% | Note 1,8,20, 22,25 | +| | | | | | | 15 | <1 | 0 | N.A. | | +| Source [ZTE] | R1-2211906 | 6.5.1**** | DDD SU | SU-MIMO | 10 | 15 | <1 | 0 | N.A. | Note 1,6 | +| | | | | | | 10 | <1 | 0 | N.A. | | +| Source [ZTE] | R1-2211906 | 6.1.2 | DDD SU | SU-MIMO | 10 | 15 | 4 | 4 | 90% | Note 1,3,23 | +| | | | | | | 10 | <1 | 0 | N.A. | | +| Source [ZTE] | R1-2211906 | 6.1.1 | DDD SU | SU-MIMO | 10 | 15 | 7 | 7 | 90% | Note 1,3,17, 22 | +| | | | | | | 10 | <1 | 0 | N.A. | | +| Source [ZTE] | R1-2211906 | 6.9**** | DDD SU | SU-MIMO | 10 | 15 | 8.2 | 8 | 91% | Note 1,7 | +| | | | | | | 10 | 5.4 | 5 | 91% | | +| Source [ZTE] | R1-2211906 | 6.6.1**** | DDD SU | SU-MIMO | 10 | 15 | 7.1 | 7 | 91% | Note 1,8, 11,22, 25 | + +NOTE 1: 64TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (8,8,2,1,1:4,8) + +NOTE 2: SR periodicity = 5ms + +NOTE 3: SR periodicity = 2.5 ms + +NOTE 4: 10 CG configurations with single CG PUSCH in a period in each CG configuration + +NOTE 5: 10 CG PUSCH in a period + +NOTE 6: 8 CG configurations with single CG PUSCH in a period in each CG configuration + +NOTE 7: 8 CG PUSCH in a period + +NOTE 8: Single CG PUSCH in a period + +NOTE 9: At least one PUSCH per CG occasion is pre-configured. + +NOTE 10: Size of configured grant = 60 kbit + +NOTE 11: Size of configured grant = 100 kbit + +NOTE 12: Size of configured grant is different for different UEs and it is up to configured resources and MCS + +NOTE 13: Size of initial UL grant = 288 bits + +NOTE 14: Size of initial UL grant = 117 kbit + +NOTE 15: Size of initial UL grant = 400 bits + +NOTE 16: Size of initial UL grant = 83.3 kbit + +NOTE 17: Size of initial UL grant is ideal at scheduler + +NOTE 18: No knowledge of XR traffic periodicity is assumed + +NOTE 19: It is assumed that the XR periodicity, frame size range and arrivals related information is known by gNB + +NOTE 20: BSR error probability is 10% + +NOTE 21: The indication of unused occasions was conveyed via new separate UCI + +NOTE 22: Scheduling delay is 2.5 ms + +NOTE 23: Scheduling delay is 5 ms + +NOTE 24: Scheduling delay is 2 slots + +NOTE 25: If CG occasion collides with DL slot due to CG periodicity equal to 16.5 ms, that particular CG occasion is not used. + +\* CG periodicity = 5 ms + +\*\* CG periodicity = 2.5 ms + +\*\*\* CG periodicity pattern = (17,17,16) ms, the periodicities of packet arrival and CG PUSCH have been aligned + +\*\*\*\* CG periodicity = 16.5 ms, the periodicities of packet arrival and the first CG PUSCH in each period have been aligned + +**Table B.1.6-3: FR1, UL, InH, AR pose/control at 250 FPS** + +| Source | Tdoc Source | Scheme | TDD form at | SU/MU-MIMO | Data rate (Mbps) | PDB (ms) | Capacity (UEs/cell) | C1=floor (Capacity) | % of satisfied UEs when #UEs/cell = C1 | Notes | +|---------------|-------------|--------|-------------|------------|------------------|----------|---------------------|---------------------|----------------------------------------|------------| +| Source [vivo] | R1-2212595 | 6.1.1 | DDD SU | SU-MIMO | 0.2 | 10 | >30 | | | Note 1,2,4 | +| Source [vivo] | R1-2212595 | 6.1.1 | DDD SU | SU-MIMO | 0.2 | 10 | >30 | | | Note 1,3,4 | +| Source [vivo] | R1-2212595 | 6.4* | DDD SU | SU-MIMO | 0.2 | 10 | >30 | | | Note 1 | + +NOTE 1: BS antenna parameters: 32TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (4,4,2,1,1:4,4) +NOTE 2: SR delay = 3 ms +NOTE 3: SR delay = 5 ms +NOTE 4: Size of initial UL grant = 100 bytes +\* CG periodicity = 5 ms + +Based on the evaluation results in Table B.1.6-1, Table B.1.6-2 the following observations can be made: + +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is increased from 6.42 UEs per cell with DG scheduling with SR followed by small initial UL grant (288 bits) with BSR and data (scheme 6.1.1) to 6.86 UEs per cell with pre-scheduling dynamic grant (scheme 6.2) (capacity gain is 7%). The capacity gain for 15ms PDB is 567%. +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is increased from 6.8 UEs per cell with DG scheduling with SR followed by large initial UL grant (117 kbit) with BSR and data (scheme 6.1.1) to 6.86 UEs per cell with pre-scheduling dynamic grant (scheme 6.2) (capacity gain is 1%). The capacity gain for 15ms PDB is 120%. +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is decreased from 6.42 UEs per cell with DG scheduling with SR followed by small initial UL grant (288 bits) with BSR and data (scheme 6.1.1) to 6.35 UEs per cell with single CG configuration (scheme 6.4) (capacity drop is -1%). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is decreased from 6.8 UEs per cell with DG scheduling with SR followed by large initial UL grant (117 kbit) with BSR and data (scheme 6.1.1) to 6.35 UEs per cell with single CG configuration (scheme 6.4) (capacity drop is -7%). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is increased from 0.68 UEs per cell with DG scheduling with SR followed by small initial UL grant (288 bits) with BSR and data (scheme 6.1.1) to 2.75 UEs per cell with single CG configuration (scheme 6.4) (capacity gain is 304%). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is increased from 2.06 UEs per cell with DG scheduling with SR followed by large initial UL grant (117 kbit) with BSR and data (scheme 6.1.1) to 2.75 UEs per cell with single CG configuration (scheme 6.4) (capacity gain is 33%). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is increased from 6.35 UEs per cell with single CG configuration (scheme 6.4) to 6.86 UEs per cell with pre-scheduling dynamic grant (scheme 6.2) (capacity gain is 8%). The capacity gain for 15ms PDB is 65%. +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is increased from 6.35 UEs per cell with single CG configuration (scheme 6.4) to 6.97 UEs per cell with hybrid scheduling CG+DG, where CG resources are configured with a certain size in every UL slot in order to transmit BSR and data when new data arrives (scheme 6.6.1) (capacity gain is 10%). The capacity gain for 15ms PDB is 81%. + +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is increased from 6.86 UEs per cell with pre-scheduling dynamic grant (scheme 6.2) to 6.97 UEs per cell with hybrid scheduling CG+DG, where CG resources are configured with a certain size in every UL slot in order to transmit BSR and data when new data arrives (scheme 6.6.1) (capacity gain is 2%). The capacity gain for 15ms PDB is 9%. +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Ericsson] that the capacity is increased from 6.97 UEs per cell with hybrid scheduling CG+DG, where CG resources are configured with a certain size in every UL slot in order to transmit BSR and data when new data arrives (scheme 6.6.1) to 7.1 UEs per cell with dynamic scheduling with genie BSR (scheme 6.3) (capacity gain is 2%). The capacity gain for 15ms PDB is 1%. +- For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [InterDigital] that the capacity is decreased from 7.1 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 6 UEs per cell with single CG configuration (scheme 6.4) (capacity drop is -15%). +- For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [InterDigital] that the capacity is increased from 2 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 4.7 UEs per cell with single CG configuration (scheme 6.4) (capacity gain is 135%). +- For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [InterDigital] that the capacity is increased from 7.1 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 7.5 UEs per cell with enhanced CG with flexible resource allocation (scheme 6.7) (capacity gain is 6%). +- For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [InterDigital] that the capacity is increased from 2 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 5.2 UEs per cell with enhanced CG with flexible resource allocation (scheme 6.7) (capacity gain is 160%). +- For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [CATT] that the capacity is decreased from 5.4 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 0 UEs per cell with single CG configuration (scheme 6.4). +- For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [CATT] that the capacity is increased from 5.4 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 7.3 UEs per cell with hybrid CG+DG scheduling (scheme 6.6.3) (capacity gain is 35%). +- For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [CATT] that the capacity is increased from 5.4 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 7.2 UEs per cell with pre-scheduling dynamic grant (scheme 6.2) (capacity gain is 33%). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Sony] that the capacity is decreased from 6.35 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 5.6 UEs per cell with single CG configuration (scheme 6.4) (capacity drop is -11%). The capacity drop for 15ms PDB is 17%. +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Sony] that the capacity is increased from 6.35 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 6.4 UEs per cell with enhanced CG with dynamic adaptation of CG parameters and indication of unused/used CG PUSCH occasion(s) (scheme 6.8) (capacity gain is 1%). The capacity gain for 15ms PDB is 44%. +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Sony] that the capacity is decreased from 6.35 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 6 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity drop is -6%). + +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [Sony] that the capacity is increased from 3 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 3.25 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity gain is 8%). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 20Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is increased from 3.5 UEs per cell with DG scheduling with SR followed by UL grant with BSR only (scheme 6.1.2) to 3.6 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) (capacity gain is 3%). The trend is similar for PDB=10 ms and 15 ms as well as for 10Mbps scenario. +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 20Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is decreased from 3.6 UEs per cell with DG scheduling with SR followed by UL grant with BSR and data (scheme 6.1.1) to 0 UEs per cell with multiple CG configurations (scheme 6.5.1). The trend is similar for PDB=10 ms and 15 ms as well as for 10Mbps scenario. +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 20Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is increased from 3.6 UEs per cell with DG scheduling with SR followed by UL grant with BSR and data (scheme 6.1.1) to 3.9 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity gain is 8%). The trend is similar if compare (scheme 6.1.2) with (scheme 6.9). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 20Mbps, 15ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is increased from 2.1 UEs per cell (scheme 6.1.1) to 3.5 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity gain is 66.7%). The trend is similar if compare (scheme 6.9) with (scheme 6.1.2) or (scheme 6.6.1) for PDB=15 ms and for 20Mbps scenario. +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is increased from 7 UEs per cell (scheme 6.1.1) to 8.2 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity gain is 17%). The trend is similar if compare (scheme 6.9) with (scheme 6.6.1) for PDB=15 ms and for 10Mbps scenario. +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 20Mbps, 10ms PDB, 60FPS, with SU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is increased from 0 UE per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 1.1) to 2.6 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 9). The trend is similar if compare (scheme 1.2) with (scheme 9). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 20Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is increased from 3.7 UEs per cell with hybrid CG+DG scheduling (scheme 6.6.1) to 3.9 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity gain is 5%). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is increased from 4 UEs per cell (scheme 6.1.2) to 8.2 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity gain is 95.2%). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 20Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is increased from 3.5 UEs per cell (scheme 6.6.1) assuming 10% BSR error probability to 3.9 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity gain is 11.4%). +- For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is increased from 2.33 UEs per cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 6.22 UEs per cell with multiple CG configurations (scheme 6.5.2) (capacity gain is 167%). +- For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is increased from 2.33 UEs per + +cell with DG scheduling with SR followed by initial UL grant with BSR and data (scheme 6.1.1) to 6.12 UEs per cell with hybrid CG+DG scheduling (scheme 6.6.2) (capacity gain is 163%). + +- For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is increased from 6.12 UEs per cell with hybrid CG+DG scheduling (scheme 6.6.2) to 6.42 UEs per cell with enhanced CG with MAC CE based dynamic resource adjustment indication (scheme 6.10) (capacity gain is 5%). +- For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is increased from 6.12 UEs per cell with hybrid CG+DG scheduling (scheme 6.6.2) to 7.81 UEs per cell with enhanced CG with UCI based dynamic resource adjustment indication (scheme 6.11) (capacity gain is 28%). +- For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [vivo] that the capacity is increased from 6.12 UEs per cell with hybrid CG+DG scheduling (scheme 6.6.2) to 8.79 UEs per cell with enhanced CG with UCI based dynamic resource adjustment indication (scheme 6.12) (capacity gain is 44%). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Huawei] that the capacity is increased from 0 UEs per cell with DG scheduling with SR followed by small initial UL grant (400 bits) with BSR and data (scheme 6.1.1) to 1 UE per cell with single CG configuration (scheme 6.4). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Huawei] that the capacity is increased from 0 UEs per cell with DG scheduling with SR followed by large initial UL grant (83.3 kbit) with BSR and data (scheme 6.1.1) to 1 UE per cell with single CG configuration (scheme 6.4). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 10ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Huawei] that the capacity is increased from 1 UE per cell with cell with single CG configuration (scheme 6.4) to 1.7 UEs per cell with pre-scheduling dynamic grant (scheme 6.2) (capacity gain is 70%). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Huawei] that the capacity is increased from 0 UEs per cell with DG scheduling with SR followed by small initial UL grant (400 bits) with BSR and data (scheme 6.1.1) to 1.7 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Huawei] that the capacity is increased from 0 UEs per cell with DG scheduling with SR followed by large initial UL grant (83.3 kbit) with BSR and data (scheme 6.1.1) to 1.7 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Huawei] that the capacity is increased from 1.4 UEs per cell with multiple CG configuration (scheme 6.5.2) to 1.7 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity gain is 21%). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Huawei] that the capacity is increased from 0 UEs per cell with hybrid CG+DG scheduling (scheme 6.6.1) to 1.7 UEs per cell with enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Huawei] that the capacity is decreased from 3 UEs per cell with cell with pre-scheduling dynamic grant (scheme 6.2) to 1.7 UEs per cell with Enhanced CG with indication of unused/used CG PUSCH occasion(s) (scheme 6.9) (capacity drop is -43%). + +### B.1.7 Scheduling restrictions due to RRM measurements + +This clause captures the capacity performance evaluation results with and without intra- and inter frequency RRM measurement restrictions. Scheduling restrictions apply for the UEs during time-intervals where it is performing intra-frequency RRM measurements at FR2, or gap assisted inter-frequency RRM measurements. Such scheduling restrictions does not allow to transmit PUCCH/PUSCH/SRS or receive PDCCH/PDSCH/CSI-RS. When XR frame arrival collides with RRM measurements, the XR frame will be delayed for the duration of SMTC window or measurement gap (MG). + +The performance with SMTC/MG scheduling restrictions (scheme 7.2 and 7.4 in Table B.1.7-1 and Table B.1.7-2) has been compared against no SMTC/MG scheduling restrictions as well as with adaptation of MG period. Particularly, the following schemes have been evaluated: + +- Scheme 7.1: Without SMTC scheduling restrictions. In this scheme, no scheduling restrictions for FR2 intra-frequency measurements were assumed. This can be realized via gNB-2-UE signalling to configure the UE with time-mask where it shall always prioritize PDCCH/PDSCH decoding and/or PUSCH transmission in line with XR traffic, even if colliding with SMTC windows. Alternatively, the UE-to-gNB signalling to make the gNB scheduler aware of when *s-MeasureConfig* induced scheduling restrictions apply could be applied. +- Scheme 7.2: With SMTC scheduling restrictions. In this scheme, scheduling restrictions every 20 ms time period for an SMTC window of 5 ms for FR2 intra-frequency measurements were assumed. In case the SMTC windows with scheduling restrictions collide with time periods where the gNB would need to schedule the XR transmission, XR frame transmission will be delayed. +- Scheme 7.3: No scheduling restrictions during measurement gap. In this scheme, no scheduling restrictions during measurement gap for inter-frequency measurements were assumed. +- Scheme 7.4: With scheduling restrictions during measurement gap. In this scheme, scheduling restrictions for the duration of measurement gap length of 6 ms are applied. Measurement gaps (MG) are configured to allow UE to do inter-frequency neighbour cell measurement and the corresponding RF tuning for RRM purposes (e.g. mobility, load balancing, CA set-up). In case the MG with scheduling restrictions collide with time periods where the gNB would need to schedule the XR transmission, XR frame transmission will be delayed. +- Scheme 7.5.1: Adaptation of MG period. The MG period is adapted to be 2 times when PCell RSRP is 2dB better than the best neighbour cell and 4 times when PCell RSRP is 4dB better than the best neighbour cell. The UE speed is 30km/h. +- Scheme 7.5.2 Adaptation of MG period. The MG period is adapted to be 4 times when PCell RSRP is 2dB better than the best neighbour cell and 8 times when PCell RSRP is 4dB better than the best neighbour cell. The UE speed is 30km/h. + +**Table B.1.7-1: FR2, DL, InH, VR/AR at 60 FPS** + +| Source | Tdoc Source | Scheme | TDD form at | SU/MU-MIMO | Data rate (Mbps) | PDB (ms) | Capacity (UEs/cell) | C1=floor (Capacity) | % of satisfied UEs when #UEs/cell =C1 | Notes | +|----------------|-------------|--------|-------------|------------|------------------|----------|---------------------|---------------------|---------------------------------------|--------| +| Source [Nokia] | R1-2211552 | 7.1 | DDD SU | SU-MIMO | 30 | 10 | 7 | 7 | 90% | Note 1 | +| Source [Nokia] | R1-2211552 | 7.2 | DDD SU | SU-MIMO | 30 | 10 | 3.1 | 3 | 92% | Note 1 | +| Source [Nokia] | R1-2211552 | 7.1 | DDD SU | SU-MIMO | 30 | 15 | 9 | 9 | 91% | Note 1 | +| Source [Nokia] | R1-2211552 | 7.2 | DDD SU | SU-MIMO | 30 | 15 | 6.25 | 6 | 93% | Note 1 | + +NOTE 1: BS antenna parameters: 2TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (4,8,2,2,2;1,1) + +**Table B.1.7-2: FR1, DL, DU, VR/AR at 60 FPS** + +| Source | Tdoc | Scheme | TDD | SU/MU- | Data | PDB | Capa | C1=floor | % of | Notes | +|--------|------|--------|-----|--------|------|-----|------|----------|------|-------| +|--------|------|--------|-----|--------|------|-----|------|----------|------|-------| + +| | Source | | form at | MIMO | rate (Mbps) | (ms) | city (UEs/cell) | (Capacity ) | satisfied UEs when #UEs/cell =C1 | | +|--------------------|------------|-----------|---------|---------|-------------|------|-----------------|-------------|----------------------------------|--------| +| Source [Media Tek] | R1-2212254 | 7.3 | DDD SU | SU-MIMO | 30 | 10 | 10.6 | 10 | 90.67% | Note 1 | +| Source [Media Tek] | R1-2212254 | 7.4* | DDD SU | SU-MIMO | 30 | 10 | 0 | 0 | N.A. | Note 1 | +| Source [Media Tek] | R1-2212254 | 7.4** | DDD SU | SU-MIMO | 30 | 10 | 2 | 2 | 88.1% | Note 1 | +| Source [Media Tek] | R1-2212254 | 7.5.1* | DDD SU | SU-MIMO | 30 | 10 | 0.5 | 0 | N.A. | Note 1 | +| Source [Media Tek] | R1-2212254 | 7.5.1** | DDD SU | SU-MIMO | 30 | 10 | 7.2 | 7 | 90.48% | Note 1 | +| Source [Media Tek] | R1-2212254 | 7.5.2* | DDD SU | SU-MIMO | 30 | 10 | 0.8 | 0 | N.A. | Note 1 | +| Source [Media Tek] | R1-2212254 | 7.5.2** | DDD SU | SU-MIMO | 30 | 10 | 8.7 | 8 | 92.62% | Note 1 | +| Source [Media Tek] | R1-2212254 | 7.4*** | DDD SU | SU-MIMO | 30 | 10 | 0 | 0 | N.A. | Note 1 | +| Source [Media Tek] | R1-2212254 | 7.4**** | DDD SU | SU-MIMO | 30 | 10 | 7.2 | 7 | 90.48% | Note 1 | +| Source [Media Tek] | R1-2212254 | 7.5.1*** | DDD SU | SU-MIMO | 30 | 10 | 0.9 | 0 | N.A. | Note 1 | +| Source [Media Tek] | R1-2212254 | 7.5.1**** | DDD SU | SU-MIMO | 30 | 10 | 8.7 | 8 | 92.62% | Note 1 | +| Source [Media Tek] | R1-2212254 | 7.5.2*** | DDD SU | SU-MIMO | 30 | 10 | 5.5 | 5 | 90.32% | Note 1 | +| Source [Media Tek] | R1-2212254 | 7.5.2**** | DDD SU | SU-MIMO | 30 | 10 | 9.2 | 9 | 90.66% | Note 1 | + +NOTE 1: BS antenna parameters: 64TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (8,8,2,1,1:4,8) + +\* MG configuration 40 ms, all UE + +\*\* MG configuration 40 ms, cell-edge 20% UE + +\*\*\* MG configuration 80 ms, all UE + +\*\*\*\* MG configuration 80 ms, cell-edge 20% UE + +Based on the evaluation results in Table B.1.7-1 and Table B.1.7-2 the following observations can be made: + +- For FR2, InH, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 2TxRU, it is observed from Source [Nokia] that the capacity is increased from 3.1 UEs per cell with SMTC scheduling restrictions for FR2 intra-frequency measurements (5 ms SMTC window every 20 ms) to 7 UEs per cell without SMTC scheduling restrictions for FR2 intra-frequency measurements (capacity gain is 126%). For 15ms PDB the capacity gain is 44%. +- For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [MediaTek] that the capacity is increased from 0 UEs per cell with MG scheduling restrictions for inter-frequency measurements for all UEs (6 ms MG length every 40 ms) to 10.6 UEs per cell without MG scheduling restrictions for inter-frequency measurements. Similar trend is observed for MG configuration 80 ms. +- For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [MediaTek] that the capacity is increased from 2 UEs per cell with MG scheduling restrictions for inter-frequency measurements for all 20% UEs (6 ms MG + +length every 40 ms) to 10.6 UEs per cell without MG scheduling restrictions for inter-frequency measurements (capacity gain is 400%). Similar trend is observed for MG configuration 80 ms. + +- For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [MediaTek] that the capacity is increased from 0 UEs per cell with MG scheduling restrictions for inter-frequency measurements for all UEs (6 ms MG length every 40 ms) to 0.5 UEs per cell with adaptation of MG period for inter-frequency measurements, where MG period is adapted to be 2 times when PCell RSRP is 2dB better than the best neighbour cell and 4 times when PCell RSRP is 4dB better than the best neighbour cell. Similar trend is observed for MG configuration 80 ms. +- For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [MediaTek] that the capacity is increased from 2 UEs per cell with MG scheduling restrictions for inter-frequency measurements for all 20% UEs (6 ms MG length every 40 ms) to 7.2 UEs per cell with adaptation of MG period restrictions for inter-frequency measurements, where MG period is adapted to be 2 times when PCell RSRP is 2dB better than the best neighbour cell and 4 times when PCell RSRP is 4dB better than the best neighbour cell (capacity gain is 250%). Similar trend is observed for MG configuration 80 ms. +- For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [MediaTek] that the capacity is increased from 0 UEs per cell with MG scheduling restrictions for inter-frequency measurements for all UEs (6 ms MG length every 40 ms) to 0.8 UEs per cell with adaptation of MG period for inter-frequency measurements, where MG period is adapted to be 2 times when PCell RSRP is 2dB better than the best neighbour cell and 4 times when PCell RSRP is 4dB better than the best neighbour cell. Similar trend is observed for MG configuration 80 ms. +- For FR1, DU, DL, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 64TxRU, it is observed from Source [MediaTek] that the capacity is increased from 2 UEs per cell with MG scheduling restrictions for inter-frequency measurements for all 20% UEs (6 ms MG length every 40 ms) to 8.7 UEs per cell with adaptation of MG period restrictions for inter-frequency measurements, where MG period is adapted to be 2 times when PCell RSRP is 2dB better than the best neighbour cell and 4 times when PCell RSRP is 4dB better than the best neighbour cell (capacity gain is 335%). Similar trend is observed for MG configuration 80 ms. + +### B.1.8 Buffer status report + +This clause captures the capacity performance evaluation results of enhancements related to buffer status report (BSR). + +The performance of legacy BSR (scheme 8.1 in Table B.1.8-1 and Table B.1.8-2) has been compared against enhanced BSR schemes. Particularly, the following schemes have been evaluated: + +- Scheme 8.1: Legacy dynamic scheduling with legacy BSR. +- Scheme 8.2: BSR with precise buffer size, where new buffer status (BS) table(s) with finer granularity is designed. +- Scheme 8.3: XR-specific triggering mechanism of BSR report. In this scheme, the pre-scheduling dynamic grant based on the XR awareness is considered and XR specific PDCCH monitoring is aligned with the periodicity of XR packet generation. The BSR is also enhanced to have XR-specific triggering mechanism of BSR report to minimize the scheduling delay. The XR-specific BSR report triggering mechanism is that the BSR report will be triggered at the 1st PUSCH of each XR packet at each cycle to inform gNB the remaining packet size to be transmitted after the 1st PUSCH transmission of the XR traffic. When gNB receive the BSR, gNB would schedule UE the UL PUSCH transmission until the completion of XR packet delivery in this cycle. + +**Table B.1.8-1: FR1, UL, InH, AR at 60 FPS** + +| Source | Tdoc Source | Scheme | TDD format | SU/MU-MIMO | Data rate (Mbps) | PDB (ms) | Capacity (UEs/cell) | C1=floor (Capacity) | % of satisfied UEs when #UEs/cell =C1 | Notes | +|---------------|-------------|--------|------------|------------|------------------|----------|---------------------|---------------------|---------------------------------------|----------| +| Source [CATT] | R1-2211175 | 8.1 | DDD UU | SU-MIMO | 10 | 30 | 5.4 | 5 | 90 | Note 1,2 | +| Source [CATT] | R1-2211175 | 8.3 | DDD UU | SU-MIMO | 10 | 30 | 7.2 | 7 | 90 | Note 1,2 | + +NOTE 1: BS antenna parameters: 32TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (4,4,2,1,1;4,4) +NOTE 2: SR/BSR periodicity = 5 ms + +**Table B.1.8-2: FR1, UL, DU, AR at 60 FPS** + +| Source | Tdoc Source | Scheme | TDD format | SU/MU-MIMO | Data rate (Mbps) | PDB (ms) | Capacity (UEs/cell) | C1=floor (Capacity) | % of satisfied UEs when #UEs/cell =C1 | Notes | +|--------------|-------------|--------|------------|------------|------------------|----------|---------------------|---------------------|---------------------------------------|----------| +| Source [ZTE] | R1-2211906 | 8.1* | DDD SU | MU-MIMO | 10 | 30 | 9.5 | 9 | 95 | Note 1,2 | +| | | | | | 20 | | 3.4 | 3 | 91 | | +| Source [ZTE] | R1-2211906 | 8.2 | DDD SU | MU-MIMO | 10 | 30 | 10.9 | 10 | 94 | Note 1,2 | +| | | | | | 20 | | 5.1 | 5 | 90 | | + +NOTE 1: BS antenna parameters: 64TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (8,8,2,1,1;4,8) +NOTE 2: SR periodicity = 2.5 ms +\* The length of the field for the Short BSR format and the Short Truncated BSR format is 5 bits + +Based on the evaluation results in Table B.1.8-1 and Table B.1.8-2 the following observations can be made: + +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is increased from 9.5 UEs per cell with Legacy BSR to 10.9 UEs per cell with BSR with precise buffer size (capacity gain is 15%). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 20Mbps, 30ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [ZTE] that the capacity is increased from 3.4 UEs per cell with Legacy BSR to 5.1 UEs per cell with BSR with precise buffer size (capacity gain is 50%). +- For FR1, InH, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 30ms PDB, 60 FPS, with SU-MIMO and 32TxRU, it is observed from Source [CATT] that the capacity is increased from 5.4 UEs per cell with dynamic grant scheduling to 7.2 UEs per cell with XR-specific triggering mechanism of BSR report (capacity gain is 33%). + +### B.1.9 UL delay-aware scheduling + +This clause captures the capacity performance evaluation results of enhancements related to UL delay aware scheduling. + +The performance proportional fair scheduling (scheme 9.1 in Table B.1.9-1) has been compared against delay-aware scheduling. Particularly, the following schemes have been evaluated: + +- Scheme 9.1: Proportional fair (PF) scheduling, where gNB uses PF scheduling, i.e., the scheduling priority of each user is calculated as the ratio of the instantaneous data rate over the historical data rate. The gNB does not consider delay during scheduling. +- Scheme 9.2: Delay-aware scheduling, where gNB is not aware of the exact UL data arrival time and can only apply SR or BSR reception time for delay-aware scheduling. +- Scheme 9.3: Delay-aware scheduling, where gNB is aware of the exact data arrival time and uses the exact data arrival time for delay-aware scheduling. + +**Table B.1.9-1: FR1, UL, DU, AR at 60 FPS** + +| Source | Tdoc Source | Scheme | TDD form at | SU/MU-MIMO | Data rate (Mbps) | PDB (ms) | Capacity (UEs/cell) | C1=floor (Capacity) | % of satisfied UEs when #UEs/cell =C1 | Notes | +|-------------------|-------------|--------|-------------|------------|------------------|----------|---------------------|---------------------|---------------------------------------|-----------| +| Source [Huawei i] | R1-2210907 | 9.1 | DDD SU | MU-MIMO | 10 | 15 | 3 | 3 | 90 | Note 1, 2 | +| Source [Huawei i] | R1-2210907 | 9.2 | DDD SU | MU-MIMO | 10 | 15 | 3.2 | 3 | 90.5 | Note 1, 2 | +| Source [Huawei i] | R1-2210907 | 9.3 | DDD SU | MU-MIMO | 10 | 15 | 3.8 | 3 | 91.5 | Note 1, 2 | + +NOTE 1: BS antenna parameters: 64TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (8,8,2,1,1;4,8) +NOTE 2: SR/BSR periodicity = 5 ms + +Based on the evaluation results in Table B.1.9-1 the following observations can be made: + +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Huawei] that the capacity is increased from 3 UEs per cell with proportional fair scheduling to 3.2 UEs per cell with delay-aware scheduling, where gNB is not aware of the exact data arrival time (capacity gain is 7%). +- For FR1, DU, UL, with 100MHz bandwidth for AR single-stream traffic model, 10Mbps, 15ms PDB, 60 FPS, with MU-MIMO and 64TxRU, it is observed from Source [Huawei] that the capacity is increased from 3.2 UEs per cell with delay-aware scheduling, where gNB is not aware of the exact data arrival time to 3.8 UEs per cell with delay-aware scheduling, where gNB is aware of the exact data arrival time (capacity gain is 19%). + +### B.1.10 XR-specific *playoutDelayForMediaStartup* for gNB scheduling awareness + +This clause captures the capacity performance evaluation results of enhancements related to gNB awareness about *playoutDelayForMediaStartup* and *appLayerBufferLevel*, where the former is the waiting time that the user experiences for media start-up and the latter is buffer level, which indicates the playout duration for which media data of all active media components is available starting from the current playout time, where. + +The performance dynamic grant scheduling (scheme 10.1 in Table B.1.10-1) has been compared against the scheme with *playoutDelayForMediaStartup* and *appLayerBufferLevel* awareness. Particularly, the following schemes have been evaluated: + +- Scheme 10.1: Dynamic grant scheduling. +- Scheme 10.2: XR-specific *playoutDelayForMediaStartup* scheme. In this scheme, the *playoutDelayForMediaStartup* and *appLayerBufferLevel* is shared by the UE with the gNB. The scheme assumes, the feedback of XR-specific *playoutDelayForMediaStartup* and *appLayerBufferLevel* from UE would give the gNB scheduler additional delay budget in scheduling the XR data transmission to achieve additional link adaptation gain. For example, when the reported *appLayerBufferLevel* is 3 frames, gNB scheduler extends PDB for scheduling the XR packet on PDSCH for additional 50 ms. gNB prioritizes the UE scheduling based on the extended delay budget from the reported playout delay size and buffer level, in which a group UEs in the same priority queue are with the same length of playout delay. + +**Table B.1.10-1: FR1, DL, InH, VR/AR at 60 FPS** + +| Source | Tdoc Source | Scheme | TDD form at | SU/MU-MIMO | Data rate (Mbps) | PDB (ms) | Capacity (UEs/cell) | C1=floor (Capacity) | % of satisfied UEs when #UEs/cell =C1 | Notes | +|---------------|-------------|----------|-------------|------------|------------------|----------|---------------------|---------------------|---------------------------------------|----------| +| Source [CATT] | R1-2211175 | 10.1 | DDD SU | MU-MIMO | 30 | 10 | 10.9 | 10 | 90.97% | Note 1,2 | +| Source [CATT] | R1-2211175 | 10.1 | DDD SU | SU-MIMO | 30 | 10 | 3.7 | 3 | 92.5% | Note 1,2 | +| Source [CATT] | R1-2211175 | 10.1 | DDD SU | MU-MIMO | 30 | 10 | 11.5 | 11 | 95.83% | Note 1,3 | +| Source [CATT] | R1-2211175 | 10.1 | DDD SU | SU-MIMO | 30 | 10 | 5.8 | 5 | 96.7% | Note 1,3 | +| Source [CATT] | R1-2211175 | 10.2* | DDD SU | MU-MIMO | 30 | 10 | 16 | 16 | 95% | Note 1 | +| Source [CATT] | R1-2211175 | 10.2** | DDD SU | MU-MIMO | 30 | 10 | 20 | 20 | 92% | Note 1 | +| Source [CATT] | R1-2211175 | 10.2*** | DDD SU | MU-MIMO | 30 | 10 | 20 | 20 | 91% | Note 1 | +| Source [CATT] | R1-2211175 | 10.2** | DDD SU | SU-MIMO | 30 | 10 | 7.3 | 7 | 91.3% | Note 1 | +| Source [CATT] | R1-2211175 | 10.2*** | DDD SU | SU-MIMO | 30 | 10 | 11.8 | 11 | 98.3% | Note 1 | +| Source [CATT] | R1-2211175 | 10.2**** | DDD SU | SU-MIMO | 30 | 10 | 11.3 | 11 | 94.4% | Note 1 | + +NOTE 1: BS antenna parameters: 32TxRUs, (M, N, P, Mg, Ng; Mp, Np) = (4,4,2,1,1:4,4) +NOTE 2: C-DRX configuration (16,12,4) +NOTE 3: UE always on +\* 2 frames playout delay +\*\* 3 frames playout delay +\*\*\* 4 frames playout delay +\*\*\*\* mixed playout delay {3, 4} + +Based on the evaluation results in Table B.1.10-1 the following observations can be made: + +- For FR1, DL, InH, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with MU-MIMO and 32TxRU, C-DRX configuration (16,12,4), it is observed from Source [CATT] that the capacity is increased from 10.9 UEs per cell with grant scheduling to 16/20/20 UEs per cell with XR-specific playoutDelayForMediaStartup scheme with 2/3/4 frames playout delay, respectively (capacity gains are 47%/83%/83%). +- For FR1, DL, InH, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with MU-MIMO and 32TxRU, UE always on, it is observed from Source [CATT] that the capacity is increased from 11.5 UEs per cell with grant scheduling to 16/20/20 UEs per cell with XR-specific playoutDelayForMediaStartup scheme with 2/3/4 frames playout delay, respectively (capacity gains are 39%/74%/74%). +- For FR1, DL, InH, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, C-DRX configuration (16,12,4), it is observed from Source [CATT] that the capacity is increased from 3.7 UEs per cell with grant scheduling to 7.3/11.8/11.3 UEs per cell with XR-specific playoutDelayForMediaStartup scheme with 3/4 and mixed {3,4} frames playout delay, respectively (capacity gains are 97%/219%/205%). +- For FR1, DL, InH, with 100MHz bandwidth for VR/AR single-stream traffic model, 30Mbps, 10ms PDB, 60 FPS, with SU-MIMO and 32TxRU, UE always on, it is observed from Source [CATT] that the capacity is increased from 5.8 UEs per cell with grant scheduling to 7.3/11.8/11.3 UEs per cell with XR-specific playoutDelayForMediaStartup scheme with 3/4 and mixed {3,4} frames playout delay, respectively (capacity gains are 26%/103%/95%). + +## B.2 Power saving performance evaluation results + +### B.2.1 Enhanced CDRX for semi-static periodicity alignment + +This clause captures evaluation results for enhanced CDRX based on semi-static periodicity alignment between CDRX and XR traffic. The following evaluations were provided by companies: + +- Ericsson and Intel evaluated configuring shifts for the start offset of CDRX On Duration and a number of DRX cycles after which the shifts should be added. +- Huawei evaluated configuring multiple start offsets for multiple On Durations within each CDRX cycle to align with multiple XR data arrivals. +- vivo evaluated multiple DRX configurations with different drx-StartOffset values. +- vivo evaluated one DRX cycle can contain multiple DRX On Durations based on single DRX configuration. +- Ericsson, vivo, OPPO, CATT, Intel, ZTE and Nokia evaluated the CDRX cycle pattern with multiple cycle values (e.g., {16ms, 17ms, 17ms} for 60fps XR video). +- ZTE, MediaTek and Qualcomm evaluated uniform non-integer number CDRX cycles with quantization operations in DRX formulas. +- ZTE evaluated multiple CDRX configurations with staggered offsets to align with multiple XR data arrivals. + +NOTE: For enhanced CDRX with semi-static periodicity alignment, different companies used different notations (e.g., "Matched CDRX", "eCDRX", "Enhanced C-DRX") to refer to their specific method to achieve periodicity alignment. There was no attempt to align notation. + +**Table B.2.1-1: FR1, DL+UL, DU, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | OD T (ms) | IA T (ms) | Load H/L | #UE/cell | floor (Capacity) | % of DL satisfied UE | % of UL satisfied UE | % of DL + UL satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|----------|----------------|-------------|------------------------|-----------------|-----------|-----------|----------|----------|------------------|----------------------|----------------------|---------------------------|-------------------|-------------------------|-------------------------------|------------------------| +| Ericsson | 35 | R1-2210922 | Always On | - | - | - | H | 8 | 8 | - | - | 90.1 % | 0% | 0.0 % | 0.0 % | Note1 | +| Ericsson | 36 | R1-2210922 | R15/16 DRX (Long DRX) | 10 | 8 | 4 | H | 8 | 8 | - | - | 86.9 % | -3.6 % | 2.6 % | 2.7 % | Note1 | +| Ericsson | 37 | R1-2210922 | R15/16 DRX (Short DRX) | 4 | 2 | 4 | H | 8 | 8 | - | - | 80.2 % | -11.0 % | 6.1 % | 6.1 % | Note1 | +| Ericsson | 38 | R1-2210922 | Matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | - | - | 85.5 % | -5.1 % | 7.2 % | 7.1 % | Note 1,2 | +| Ericsson | 39 | R1-2210922 | Matched CDRX | 17/17/16 | 10 | 4 | H | 8 | 8 | - | - | 86.4 % | -4.1 % | 7.6 % | 7.5 % | Note1 | + +NOTE 1: the DL traffic has a second flow for audio with 30ms PDB + +NOTE 2: Matched CDRX has (drx\_offset=3, traffic\_time\_offset=2 ms, drx-LongCycle=16 ms) + +Based on the evaluation results in Table B.2.1-1, the following observations can be made. + +- For FR1, DL + UL joint evaluation, DU, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from Ericsson that: + - Semi-static alignment provides: + - mean power saving gain of 7.4% in the range of 7.2% to 7.6% for all UEs + - mean capacity gain of -4.6% in the range of -5.1% to -4.1%% + - R15/16 CDRX as the performance reference provides: + - mean power saving gain of 4.35% in the range of 2.6% to 6.1% for all UEs + - mean capacity gain of -7.30% in the range of -11% to -3.6% + +**Table B.2.1-2: FR1, DL+UL, InH, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of DL satisfied UE | % of UL satisfied UE | % of DL + UL satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|------------------------------------------------|-----------------|----------|----------|----------|----------|------------------|----------------------|----------------------|---------------------------|-------------------|-------------------------|-------------------------------|------------------------| +| ZTE | 8 | R1-2211905 | Always On | - | - | - | H | 11 | 11 | 93.18% | 100% | 93.18% | 0% | - | - | | +| ZTE | 9 | R1-2211905 | R15 CDRX | 10 | 8 | 4 | H | 11 | 11 | 90.15% | 100% | 90.15% | -3.3% | 6.65% | - | | +| ZTE | 10 | R1-2211905 | R15 CDRX | 16 | 10 | 5 | H | 11 | 11 | 81.82% | 100% | 81.82% | -12.2% | 13.9% | - | | +| ZTE | 12 | R1-2211905 | Non-uniform CDRX cycle | (17, 17, 16) | 6 | 4 | H | 11 | 11 | 90.15% | 100% | 90.15% | -3.3% | 23.86% | - | | +| ZTE | 13 | R1-2211905 | Uniform non-inter CDRX cycle | (1000/60) | 6 | 4 | H | 11 | 11 | 90.15% | 100% | 90.15% | -3.3% | 23.85% | - | | +| ZTE | 14 | R1-2211905 | Enhanced multiple CDRX (3 CDRX configurations) | 50 ms DRX cycle | 6 | 4 | H | 11 | 11 | 90.11% | 100% | 90.11% | -3.3% | 24% | - | | + +Based on the evaluation results in Table B.2.1-2, the following observations can be made. + +- For FR1, DL + UL joint evaluation, InH, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from ZTE that: + - Semi-static alignment provides: + - mean power saving gain of 23.8% in the range of 24% to 23.90% for all UEs + - mean capacity gain of -3.33% in the range of -3.33% to -3.33% + - R15 CDRX as the performance reference provides: + - mean power saving gain of 10.28% in the range of 6.65% to 13.9% for all UEs + - mean capacity gain of -7.75% in the range of -12.2% to -3.33% + +**Table B.2.1-3: FR1, DL-only, DU, VR30** + +| source | data row index | Tdo source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|------------|-------------------------------------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| OP PO | 1 | R1-2211490 | Always On | - | - | - | H | 5 | 5 | 90.18 % | 0.0% | 0.0% | 0.0% | | +| OP PO | 2 | R1-2211490 | R15/16 CDRX | 16 | 14 | 2 | H | 5 | 5 | 88.77 % | -1.6% | 5.11% | 5.55% | | +| OP PO | 3 | R1-2211490 | Non-uniform CDRX cycle pattern | {17,17,16} | 10 | 2 | H | 5 | 5 | 88.77 % | -1.6% | 18.72 % | 19.43% | | +| Huawei | 1 | R1-2210906 | Always On | - | - | - | H | 11 | 11 | 93.42 % | 0.0% | 0.0% | - | | +| Huawei | 2 | R1-2210906 | Legacy C-DRX | 16 | 12 | 4 | H | 11 | 11 | 83.20 % | -10.9 % | 5.57% | - | | +| Huawei | 3 | R1-2210906 | Enhanced C-DRX | 50 {0, 16, 33} | 12 | 4 | H | 11 | 11 | 91.43 % | -2.1% | 7.64% | - | | +| QC | 4 | R1-2212134 | Always On | - | - | - | H | 13 | 12 | 89.3 % | 0.0% | 0% | - | | +| QC | 5 | R1-2212134 | Rel15/16 CDRX | 16 | 12 | 8 | H | 13 | 12 | 78.8 % | -11.8 % | 6.04% | - | | +| QC | 6 | R1-2212134 | eCDRX | 16/17/17 | 12 | 8 | H | 13 | 12 | 90.0 % | 0.8% | 3.92% | - | | +| QC | 7 | R1-2212134 | Rel15/16 CDRX + PDCCH skipping | 16 | 12 | 8 | H | 13 | 12 | 38.3 % | -57.1 % | 25.7% | - | | +| QC | 8 | R1-2212134 | eCDRX + PDCCH skipping | 16/17/17 | 12 | 8 | H | 13 | 12 | 87.5 % | -2.0% | 24.5% | - | | +| QC | 9 | R1-2212134 | Rel15/16 CDRX + PDCCH skipping + SSSG switching | 16 | 12 | 8 | H | 13 | 12 | 13.6 % | -84.8 % | 29.7% | - | | +| QC | 10 | R1-2212134 | eCDRX + PDCCH skipping + SSSG switching | 16/17/17 | 12 | 8 | H | 13 | 12 | 82.5 % | -7.6% | 28.8% | - | | +| QC | 52 | R1-2212134 | Always On | - | - | - | H | 12 | 12 | 94.6 % | 0.0% | 0% | - | | +| QC | 53 | R1-2212134 | Rel15/16 CDRX | 16 | 12 | 8 | H | 12 | 12 | 86.5 % | -8.6% | 6.17% | - | | +| QC | 54 | R1-2212134 | eCDRX | 16/17/17 | 12 | 8 | H | 12 | 12 | 94.6 % | 0.0% | 4.26% | - | | +| QC | 55 | R1- | Rel15/16 | 16 | 12 | 8 | H | 12 | 12 | 47.6 | -49.7 | 26.4% | - | | + +| | | | | | | | | | | | | | | | +|----------------------|----|--------------------|--------------------------------------------------------------------|--------------|----|---|---|----|----|------------|------------|-------|-------|-----------| +| C | | 2212
134 | CDRX +
PDCCH
skipping | | | | | | | % | % | | | | +| Q
C | 56 | R1-
2212
134 | eCDRX
+
PDCCH
skipping | 16/17
/17 | 12 | 8 | H | 12 | 12 | 92.7
% | -2.0% | 25.7% | - | | +| Q
C | 57 | R1-
2212
134 | Rel15/16
CDRX +
PDCCH
skipping
+ SSSG
switchin
g | 16 | 12 | 8 | H | 12 | 12 | 19.8
% | -79.1
% | 30.6% | - | | +| Q
C | 58 | R1-
2212
134 | eCDRX
+
PDCCH
skipping
+ SSSG
switchin
g | 16/17
/17 | 12 | 8 | H | 12 | 12 | 90.4
% | -4.4% | 30.1% | - | | +| Eri
cs
so
n | 1 | R1-
2210
922 | Always
On | - | - | - | H | 8 | 8 | 91.7
% | 0.0% | 0% | 0% | | +| Eri
cs
so
n | 2 | R1-
2210
922 | R15/16
DRX
(Long
DRX) | 10 | 8 | 4 | H | 8 | 8 | 86.9
% | -5.2% | 4.3% | 4.9% | | +| Eri
cs
so
n | 3 | R1-
2210
922 | R15/16
DRX
(Short
DRX) | 4 | 2 | 4 | H | 8 | 8 | 78.2
% | -14.7
% | 10.4% | 11.0% | | +| Eri
cs
so
n | 4 | R1-
2210
922 | Matched
CDRX | 16.6 | 10 | 4 | H | 8 | 8 | 87.2
% | -4.9% | 10.5% | 11.4% | Note
1 | +| Eri
cs
so
n | 5 | R1-
2210
922 | Matched
CDRX | 17/17
/16 | 10 | 4 | H | 8 | 8 | 87.0
% | -5.1% | 10.1% | 10.5% | | +| Eri
cs
so
n | 1 | R1-
2210
922 | Always
On | - | - | - | L | 2 | 8 | 100% | 0.0% | 0% | 0% | | +| Eri
cs
so
n | 2 | R1-
2210
922 | R15/16
DRX
(Long
DRX) | 10 | 8 | 4 | L | 2 | 8 | 100% | 0.0% | 4.8% | 4.8% | | +| Eri
cs
so
n | 3 | R1-
2210
922 | R15/16
DRX
(Short
DRX) | 4 | 2 | 4 | L | 2 | 8 | 100% | 0.0% | 12.4% | 12.4% | | +| Eri
cs
so
n | 4 | R1-
2210
922 | Matched
CDRX | 16.6 | 10 | 4 | L | 2 | 8 | 100% | 0.0% | 12.8% | 12.8% | Note
1 | +| Eri
cs
so
n | 5 | R1-
2210
922 | Matched
CDRX | 17/17
/16 | 10 | 4 | L | 2 | 8 | 100% | 0.0% | 12.5% | 12.5% | | +| Int
el | 1 | R1-
2211
389 | AlwaysOn
-
baseline | - | - | - | H | 4 | 4 | 99.25
% | 0.0% | 0.00% | - | Note
2 | +| Int
el | 2 | R1-
2211
389 | R15/16C
DRX | 8 | 6 | 6 | H | 4 | 4 | 95.00
% | -4.3% | 4.79% | - | Note
2 | +| Int | 3 | R1- | Enhance | 8 | 6 | 6 | H | 4 | 4 | 99.25 | 0.0% | 10.54 | - | Note | + +| | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------|----|--------------------|------------------------|----|----|---|---|---|---|------------|-------|-------|---|-------------| +| el | | 2211
389 | d CDRX | | | | | | | % | | % | | 2,3 | +| Int
el | 4 | R1-
2211
389 | R15/16C
DRX | 16 | 14 | 4 | H | 4 | 4 | 96.00
% | -3.3% | 3.13% | - | Note
2 | +| Int
el | 5 | R1-
2211
389 | Enhanced
CDRX | 16 | 14 | 4 | H | 4 | 4 | 99.25
% | 0.0% | 8.37% | - | Note
2,4 | +| Int
el | 11 | R1-
2211
389 | AlwaysOn -
baseline | - | - | - | H | 4 | 4 | 98.25
% | 0.0% | 0.00% | - | | +| Int
el | 12 | R1-
2211
389 | R15/16C
DRX | 8 | 6 | 6 | H | 4 | 4 | 93.00
% | -5.3% | 4.62% | - | | +| Int
el | 13 | R1-
2211
389 | Enhanced
CDRX | 8 | 6 | 6 | H | 4 | 4 | 95.75
% | -2.5% | 7.19% | - | Note
3 | +| Int
el | 14 | R1-
2211
389 | R15/16C
DRX | 16 | 14 | 4 | H | 4 | 4 | 95.50
% | -2.8% | 3.23% | - | | +| Int
el | 15 | R1-
2211
389 | Enhanced
CDRX | 16 | 14 | 4 | H | 4 | 4 | 97.25
% | -1.0% | 4.56% | - | Note
4 | +| NOTE 1: Matched CDRX has (drx_offset=3, traffic_time_offset=2 ms, drx-LongCycle=16 ms) | | | | | | | | | | | | | | | +| NOTE 2: jitter is off | | | | | | | | | | | | | | | +| NOTE 3: start offset adjusted every 6 cycles | | | | | | | | | | | | | | | +| NOTE 4: start offset adjusted every 3 cycles | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.1-3, the following observations can be made. + +- For FR1, DL only evaluation, DU, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from OPPO, Huawei, Qualcomm, Ericsson and Intel that: + - semi-static alignment provides: + - mean power saving gain of 8.36% in the range of 3.92% to 18.72% for all UEs + - mean capacity gain of -2.05% in the range of -5.10% to 0.80% + - R15/16 CDRX as the performance reference provides: + - mean power saving gain of 5.68% in the range of 3.23% to 10.4% for all UEs + - mean capacity gain of -7.61% in the range of -14.70% to -1.60% +- For FR1, DL only evaluation, DU, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from Qualcomm that: + - semi-static alignment + R17 PDCCH monitoring adaptation provides: + - mean power saving gain of 27.28% in the range of 24.5% to 30.1% for all UEs + - mean capacity gain of -4.00% in the range of -7.60% to -2.00% + - R15/16 CDRX + R17 PDCCH monitoring adaptation as the performance reference provides: + - mean power saving gain of 28.1% in the range of 25.7% to 30.6% for all UEs + - mean capacity gain of -67.68% in the range of -84.80% to -49.70% +- For FR1, DL only evaluation, DU, low load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from Ericsson that: + - semi-static alignment provides: + - mean power saving gain of 12.65% in the range of 12.50% to 12.80% for all UEs + +- capacity gain of 0% +- R15/16 CDRX as the performance reference provides: + - mean power saving gain of 8.60% in the range of 4.80% to 12.40% for all UEs + - capacity gain of 0% +- For FR1, DL only evaluation, DU, high load, jitter off, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from Intel that: + - semi-static alignment provides: + - mean power saving gain of 9.46% in the range of 8.37% to 10.54% for all UEs + - capacity gain of 0.0% + - R15/16 CDRX as the performance reference provides: + - mean power saving gain of 3.96% in the range of 3.13% to 4.79% for all UEs + - mean capacity gain of -3.8% in the range of -3.3% to -4.3% + +**Table B.2.1-4: FR1, DL-only, DU, CG30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +|--------|----------------|-------------|---------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| + +| | | | | | | | | | | | | | | | +|----------------------------------------------|----|------------|----------------------------|------|----|---|---|----|----|---------|-------|---------|---|----------| +| MT K | 22 | R1-2207008 | Always On - baseline | - | - | - | H | 12 | 12 | 94.6 % | 0.0% | 0% | - | | +| MT K | 23 | R1-2207008 | R17 CDRX | 16 | 12 | 8 | H | 12 | 12 | 92.7 % | -2.0% | 5.4% | - | | +| MT K | 24 | R1-2207008 | eCDRX (rational DRX cycle) | 50/3 | 12 | 8 | H | 12 | 12 | 94.3 % | -0.3% | 9.9% | - | | +| Intel | 6 | R1-2211389 | Always On - baseline | - | - | - | H | 4 | 4 | 99.75 % | 0.0% | 0.00% | - | Note 1 | +| Intel | 7 | R1-2211389 | R15/16 CDRX | 8 | 6 | 6 | H | 4 | 4 | 97.25 % | -2.5% | 4.79% | - | Note 1 | +| Intel | 8 | R1-2211389 | Enhanced CDRX | 8 | 6 | 6 | H | 4 | 4 | 99.75 % | 0.0% | 10.54 % | - | Note 1,2 | +| Intel | 9 | R1-2211389 | R15/16 CDRX | 16 | 14 | 4 | H | 4 | 4 | 98.25 % | -1.5% | 3.13% | - | Note 1 | +| Intel | 10 | R1-2211389 | Enhanced CDRX | 16 | 14 | 4 | H | 4 | 4 | 99.75 % | 0.0% | 8.37% | - | Note 1,3 | +| Intel | 16 | R1-2211389 | Always On - baseline | - | - | - | H | 4 | 4 | 98.75 % | 0.0% | 0.00% | - | | +| Intel | 17 | R1-2211389 | R15/16 CDRX | 8 | 6 | 6 | H | 4 | 4 | 95.25 % | -3.5% | 4.62% | - | | +| Intel | 18 | R1-2211389 | Enhanced CDRX | 8 | 6 | 6 | H | 4 | 4 | 97.50 % | -1.3% | 7.19% | - | Note 2 | +| Intel | 19 | R1-2211389 | R15/16 CDRX | 16 | 14 | 4 | H | 4 | 4 | 97.25 % | -1.5% | 3.23% | - | | +| Intel | 20 | R1-2211389 | Enhanced CDRX | 16 | 14 | 4 | H | 4 | 4 | 98.25 % | -0.5% | 4.56% | - | Note 3 | +| NOTE 1: jitter is off | | | | | | | | | | | | | | | +| NOTE 2: start offset adjusted every 6 cycles | | | | | | | | | | | | | | | +| NOTE 3: start offset adjusted every 3 cycles | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.1-4, the following observations can be made: + +- For FR1, DL only evaluation, DU, high load, CG 30Mbps traffic at 60fps and 15ms PDB, it is observed from MediaTek and Intel that: + - semi-static alignment provides: + - mean power saving gain of 7.22% in the range of 4.56% to 9.90% for all UEs + - mean capacity gain of -0.70% in the range of -1.30% to -0.3% + - R15/16 CDRX as the performance reference provides: + - mean power saving gain of 4.42% in the range of 3.23% to 5.40% for all UEs + - mean capacity gain of -2.33% in the range of -3.5% to -1.5% +- For FR1, DL only evaluation, DU, high load, jitter off, CG 30Mbps traffic at 60fps and 15ms PDB, it is observed from Intel that: + +- semi-static alignment provides: + - mean power saving gain of 9.46% in the range of 8.37% to 10.54% for all UEs + - capacity gain of 0% +- R15/16 CDRX as the performance reference provides: + - mean power saving gain of 3.96% in the range of 3.13% to 4.79% for all UEs + - mean capacity gain of -2.0% in the range of -1.5% to -2.5% + +**Table B.2.1-5: FR1, DL-only, InH, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +|--------|----------------|-------------|---------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| + +| | | | | | | | | | | | | | | | +|------|---|------------|------------------------------------------------|----------------|----|---|---|----|----|---------|---------|---------|---|--| +| ZTE | 1 | R1-2211905 | Always On | - | - | - | H | 11 | 11 | 93.18 % | 0.0% | 0.0% | - | | +| ZTE | 2 | R1-2211905 | R15 CDRX | 10 | 8 | 4 | H | 11 | 11 | 90.15 % | -3.3% | 7% | - | | +| ZTE | 3 | R1-2211905 | R15 CDRX | 16 | 10 | 5 | H | 11 | 11 | 81.82 % | -12.2 % | 18.47 % | - | | +| ZTE | 5 | R1-2211905 | Non-uniform CDRX cycle | (17,17,16) | 6 | 4 | H | 11 | 11 | 90.15 % | -3.3% | 33.9% | - | | +| ZTE | 6 | R1-2211905 | Uniform non-integer CDRX cycle | (1000/60) | 6 | 4 | H | 11 | 11 | 90.18 % | -3.2% | 33.8% | - | | +| ZTE | 7 | R1-2211905 | Enhanced multiple CDRX (3 CDRX configurations) | 50ms DRX cycle | 6 | 4 | H | 11 | 11 | 90.1 % | -3.3% | 34% | - | | +| vivo | | R1-2211024 | Always On | - | - | - | L | 5 | 10 | 100% | 0.0% | 0.0% | - | | +| vivo | | R1-2211024 | R15/16 DRX | 16 | 14 | 4 | L | 5 | 10 | 100% | 0.0% | 3.67% | - | | +| vivo | | R1-2211024 | R15/16 DRX | 10 | 8 | 4 | L | 5 | 10 | 100% | 0.0% | 5.72% | - | | +| vivo | | R1-2211024 | R15/16 DRX | 4 | 3 | 1 | L | 5 | 10 | 100% | 0.0% | 4.63% | - | | +| vivo | | R1-2211024 | R15/16 DRX | 16 | 8 | 4 | L | 5 | 10 | 11.67 % | -88.3 % | 19.71 % | - | | +| vivo | | R1-2211024 | R15/16 DRX | 10 | 5 | 2 | L | 5 | 10 | 78.33 % | -21.7 % | 15.41 % | - | | +| vivo | | R1-2211024 | R15/16 DRX | 10 | 4 | 2 | L | 5 | 10 | 52.22 % | -47.8 % | 22.17 % | - | | +| vivo | | R1-2211024 | Enhanced DRX | 16.67 | 8 | 4 | L | 5 | 10 | 100% | 0.0% | 13.05 % | - | | +| vivo | | R1-2211024 | Always On | - | - | - | H | 10 | 10 | 92.50 % | 0.0% | 0.0% | - | | +| vivo | | R1-2211024 | R15/16 DRX | 16 | 14 | 4 | H | 10 | 10 | 91.81 % | -0.7% | 3.46% | - | | +| vivo | | R1-2211024 | R15/16 DRX | 10 | 8 | 4 | H | 10 | 10 | 91.25 % | -1.4% | 5.10% | - | | +| vivo | | R1-2211024 | R15/16 DRX | 4 | 3 | 1 | H | 10 | 10 | 91.68 % | -0.9% | 4.03% | - | | +| vivo | | R1-2211024 | R15/16 DRX | 16 | 8 | 4 | H | 10 | 10 | 2.78 % | -97.0 % | 18.21 % | - | | +| vivo | | R1-2211024 | R15/16 DRX | 10 | 5 | 2 | H | 10 | 10 | 45.00 % | -51.4 % | 13.10 % | - | | + +| | | | | | | | | | | | | | | | +|-----------------------------------------------------------|---|------------|-------------------------------------------|-----------|----|---|---|----|----|---------|----------|---------|---|--------| +| vivo | | R1-2211024 | R15/16 DRX | 10 | 4 | 2 | H | 10 | 10 | 22.50 % | -75.7 % | 18.70 % | - | | +| vivo | | R1-2211024 | Enhanced DRX | 16.67 | 8 | 4 | H | 10 | 10 | 91.94 % | -0.6% | 10.08 % | - | | +| CATT | 1 | R1-2211174 | Baseline : DG scheduling and UE always-on | - | - | - | H | 12 | 12 | 95.8 % | 0.0% | 0.0% | - | | +| CATT | 2 | R1-2211174 | DG scheduling with C-DRX | 16 | 12 | 4 | H | 12 | 12 | 90.0 % | -6.1% | 8.0% | - | | +| CATT | 3 | R1-2211174 | Enhanced C-DRX | 17/17 /16 | 8 | 4 | H | 12 | 12 | 0.0% | -100.0 % | 25.5% | - | | +| CATT | 3 | R1-2211174 | Enhanced C-DRX | 17/17 /16 | 8 | 4 | H | 12 | 12 | 0.0% | -100.0 % | 19.0% | - | Note 1 | +| CATT | 4 | R1-2211174 | Enhanced C-DRX | 17/17 /16 | 10 | 4 | H | 12 | 12 | 21.7 % | -77.3 % | 14.8% | - | | +| CATT | 4 | R1-2211174 | Enhanced C-DRX | 17/17 /16 | 10 | 4 | H | 12 | 12 | 21.7 % | -77.3 % | 7.4% | - | Note 1 | +| CATT | 5 | R1-2211174 | Enhanced C-DRX | 17/17 /16 | 12 | 4 | H | 12 | 12 | 84.2 % | -12.1 % | 9.3% | - | | +| CATT | 5 | R1-2211174 | Enhanced C-DRX | 17/17 /16 | 12 | 4 | H | 12 | 12 | 84.2 % | -12.1 % | 1.4% | - | Note 1 | +| Nokia | | R1-2211551 | Always On Baseline | - | - | - | H | 5 | 5 | 95% | 0.0% | 0.0% | - | | +| Nokia | 7 | R1-2211551 | CDRX | 16 | 8 | 8 | H | 5 | 5 | 0% | -100.0 % | - | - | | +| Nokia | 8 | R1-2211551 | Cyclic DRX pattern {16,17} | {16,17} | 8 | 8 | H | 5 | 5 | 0% | -100.0 % | - | - | | +| NOTE 1: PSG is calculated w.r.t. DG scheduling with C-DRX | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.1-5, the following observations can be made: + +- For FR1, DL only evaluation, InH, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from ZTE, vivo, CATT and Nokia that: + - semi-static alignment provides: + - mean power saving gain of 23.05% in the range of 9.30% to 34% for all UEs with + - mean capacity gain of -28.54% in the range of -100% to -0.60% + - R15/16 CDRX as the performance reference provides: + - mean power saving gain of 10.67% in the range of 3.46% to 18.70% for all UEs with + - mean capacity gain of -27.63% in the range of -100% to -0.70% +- For FR1, DL only evaluation, InH, low load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from vivo that: + - semi-static alignment provides: + +- power saving gain of 13.05% for all UEs with +- capacity gain of 0% +- R15/16 CDRX as the performance reference provides: + - mean power saving gain of 11.89% in the range of 3.67% to 22.17% for all UEs with + - mean capacity gain of -26.30% in the range of -88.3% to 0% + +**Table B.2.1-6: FR2, DL-only, InH, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| QC | 13 | R1-2212134 | Always On | - | - | - | H | 7 | 7 | 90% | 0.0% | 0% | - | Note 1 | +| QC | 14 | R1-2212134 | Rel15/16 CDRX | 16 | 4 | 4 | H | 7 | 7 | 0% | -100.0% | 28.60% | - | Note 1 | +| QC | 15 | R1-2212134 | Rel15/16 CDRX | 16 | 8 | 8 | H | 7 | 7 | 42% | -53.3% | 8.70% | - | Note 1 | +| QC | 16 | R1-2212134 | Rel15/16 CDRX | 16 | 8 | 16 | H | 7 | 7 | 90% | 0.0% | 0.29% | - | Note 1 | +| QC | 17 | R1-2212134 | eCDRX | 16/17/17 | 4 | 4 | H | 7 | 7 | 90% | 0.0% | 18.93% | - | Note 1 | +| QC | 18 | R1-2212134 | eCDRX | 16/17/17 | 8 | 8 | H | 7 | 7 | 90% | 0.0% | 7.71% | - | Note 1 | +| QC | 19 | R1-2212134 | eCDRX | 16/17/17 | 8 | 16 | H | 7 | 7 | 90% | 0.0% | 0.30% | - | Note 1 | +| QC | 20 | R1-2212134 | Always On | - | - | - | H | 7 | 7 | 90% | 0.0% | 0% | - | | +| QC | 21 | R1-2212134 | Rel15/16 CDRX | 16 | 4 | 4 | H | 7 | 7 | 0% | -100.0% | 28.44% | - | | +| QC | 22 | R1-2212134 | Rel15/16 CDRX | 16 | 8 | 8 | H | 7 | 7 | 50% | -44.4% | 9.64% | - | | +| QC | 23 | R1-2212134 | Rel15/16 CDRX | 16 | 8 | 16 | H | 7 | 7 | 65% | -27.8% | 4.10% | - | | +| QC | 24 | R1-2212134 | eCDRX | 16/17/17 | 4 | 4 | H | 7 | 7 | 27% | -70.0% | 25.10% | - | | +| QC | 25 | R1-2212134 | eCDRX | 16/17/17 | 8 | 8 | H | 7 | 7 | 84% | -6.7% | 8.28% | - | | +| QC | 26 | R1-2212134 | eCDRX | 16/17/17 | 8 | 16 | H | 7 | 7 | 88% | -2.2% | 2.43% | - | | + +NOTE 1: jitter is off. + +Based on the evaluation results in Table B.2.1-6, the following observations can be made: + +- For FR2, DL only evaluation, InH, high load, jitter off, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from Qualcomm that: + +- semi-static alignment provides: + - mean power saving gain of 8.98% in the range of 0.30% to 18.93% for all UEs + - capacity gain of 0% +- R15/16 CDRX as the performance reference provides: + - mean power saving gain of 12.53% in the range of 0.29% to 28.60% for all UEs + - mean capacity gain of -51.10% in the range of -100% to 0% +- For FR2, DL only evaluation, InH, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from Qualcomm that: + - semi-static alignment provides: + - mean power saving gain of 11.94% in the range of 2.43% to 25.10% for all UEs + - mean capacity gain of -26.30% in the range of -70.00% to -2.2% + - R15/16 CDRX as the performance reference provides: + - mean power saving gain of 14.06% in the range of 4.10% to 28.44% for all UEs + - mean capacity gain of -57.4% in the range of -100% to -27.8% + +**Table B.2.1-7: FR1, DL-only, InH, CG30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| Nokia | | R1-2211551 | Always On Baseline | - | - | - | H | 6 | 6 | 90% | 0.0% | 0.0% | - | | +| Nokia | 1 | R1-2211551 | CDRX | 16 | 8 | 8 | H | 6 | 6 | 60% | -33.3% | 13.30% | - | | +| Nokia | 2 | R1-2211551 | Cyclic DRX pattern | {16,17,17} | 8 | 8 | H | 6 | 6 | 40% | -55.6% | 16.00% | - | | + +Based on the evaluation results in Table B.2.1-7, the following observations can be made: + +- For FR1, DL only evaluation, InH, high load, CG 30Mbps traffic at 60fps and 15ms PDB, it is observed from Nokia that: + - semi-static CDRX periodicity alignment provides: + - power saving of 16.00% + - capacity gain of -55.6% + - R15/16 CDRX provides: + - mean power saving gain of 13.30% for all UEs + - capacity gain of -33.3% + +### B.2.2 Dynamic CDRX alignment + +This clause captures evaluation results for enhanced CDRX based on dynamic alignment between CDRX and XR traffic. The following evaluations were provided by companies: + +- Nokia evaluated dynamic adaptation of DRX parameters based on auxiliary L1/L2 signalling in addition to semi-static solution to align XR traffic and CDRX operation. +- ZTE and Qualcomm evaluated dynamic CDRX enhancement to adjust the CDRX start offset. + +**Table B.2.2-1: FR1, DL+UL pose/control, InH, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of DL satisfied UE | % of UL satisfied UE | % of DL + UL satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------------------------|-----------------|----------|----------|----------|----------|------------------|----------------------|----------------------|---------------------------|-------------------|-------------------------|-------------------------------|------------------------| +| ZTE | 8 | R1-2211905 | Always on | - | - | - | H | 11 | 11 | 93.18% | 100% | 93.18% | 0.00% | 0% | - | | +| ZTE | 11 | R1-2211905 | Dynamic indication | 50 | 6 | 4 | H | 11 | 11 | 90.1% | 100% | 90.1% | -3.31% | 23% | - | | +| ZTE | 12 | R1-2211905 | Non-uniform CDRX cycle | 17-17-16 | 6 | 4 | H | 11 | 11 | 90.15% | 100% | 90.15% | -3.25% | 23.86% | - | | +| ZTE | 13 | R1-2211905 | Uniform non-integer CDRX cycle | (1000/60) | 6 | 4 | H | 11 | 11 | 90.15% | 100% | 90.15% | -3.25% | 23.85% | - | | +| ZTE | 14 | R1-2211905 | Multiple CDRX (3 CDRX configurations) | 50 ms DRX cycle | 6 | 4 | H | 11 | 11 | 90.11% | 100% | 90.11% | -3.29% | 24% | - | | + +Based on the evaluation results in Table B.2.2-1, the following observations can be made: + +- For FR1, DL + UL joint evaluation, InH, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from ZTE that: + - dynamic alignment provides: + - power saving gain of 23% for all UEs + - capacity gain of -3.31% + - semi-static alignment as the performance reference provides: + - mean power saving gain of 23.90% in the range of 23.85% to 24% for all UEs + - mean capacity gain of -3.26% in the range of -3.29% to -3.25%. + +**Table B.2.2-2: FR1, DL-only, InH, CG30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | O D T (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------|-----------------|------------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| Nokia | | R1-2211551 | Always On Baseline | - | - | - | H | 6 | 6 | 90% | 0.0% | 0.0% | - | | +| Nokia | 1 | R1-2211551 | CDRX | 16 | 8 | 8 | H | 6 | 6 | 60% | -33.3% | 13.30% | - | | +| Nokia | 2 | R1-2211551 | Cyclic DRX pattern | {16,17,17} | 8 | 8 | H | 6 | 6 | 40% | -55.6% | 16.00% | - | | +| Nokia | 3 | R1-2211551 | Adaptive DRX | 16 | 8 | 8 | H | 6 | 6 | 62% | -31.1% | 15.00% | - | Note 1 | +| Nokia | 4 | R1-2211551 | Adaptive DRX | {16,17,17} | 8 | 8 | H | 6 | 6 | 62% | -31.1% | 15.00% | - | Note 1 | +| Nokia | 5 | R1-2211551 | Adaptive DRX | 16 | 8 | 8 | H | 6 | 6 | 75% | -16.7% | 19.00% | - | Note 2 | + +NOTE 1: startOffset = ExpectedArrival - FixedTimeShift +NOTE 2: scalingFactor X={1/2,1/4} + +Based on the evaluation results in Table B.2.2-2, the following observations can be made: + +- For FR1, DL only evaluation, InH, high load, CG 30Mbps traffic at 60fps and 15ms PDB, it is observed from Nokia that: + - adaptive DRX provides: + - mean power saving gain of 16.33% in the range of 15.00% to 19.00% for all UEs + - mean capacity gain of -26.3% in the range of -31.1% to -16.7% + - semi-static CDRX periodicity alignment provides: + - power saving of 16.00% + - capacity gain of -55.6% + - R15/16 CDRX provides: + - mean power saving gain of 13.30% for all UEs + - capacity gain of -33.3% + +**Table B.2.2-3: FR1, DL-only, InH, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | O D T (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------|-----------------|------------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +|--------|----------------|-------------|---------------------|-----------------|------------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| + +| | | | | | | | | | | | | | | | +|--------|----|------------|---------------------------------------|----------------|---|---|---|----|----|---------|----------|---------|---|--------| +| No kia | | R1-2211551 | Always On Baseline | - | - | - | H | 5 | 5 | 95% | 0.0% | 0.0% | - | | +| No kia | 7 | R1-2211551 | CDRX | 16 | 8 | 8 | H | 5 | 5 | 0% | -100.0 % | - | - | | +| No kia | 8 | R1-2211551 | Cyclic DRX pattern | {16,17,17} | 8 | 8 | H | 5 | 5 | 0% | -100.0 % | - | - | | +| No kia | 9 | R1-2211551 | Adaptive DRX | 16 | 8 | 8 | H | 5 | 5 | 25% | -73.7 % | 15.00 % | - | Note 1 | +| No kia | 10 | R1-2211551 | Adaptive DRX | {16,17,17} | 8 | 8 | H | 5 | 5 | 25% | -73.7 % | 15.00 % | - | Note 1 | +| No kia | 11 | R1-2211551 | Adaptive DRX | 16 | 8 | 8 | H | 5 | 5 | 70% | -26.3 % | 19.00 % | - | Note 2 | +| ZTE | 1 | R1-2211905 | Always on | - | - | - | H | 11 | 11 | 93.18 % | 0.00% | 0% | - | | +| ZTE | 4 | R1-2211905 | Dynamic indication | 50 | 6 | 4 | H | 11 | 11 | 90.1 % | -3.31 % | 33% | - | | +| ZTE | 5 | R1-2211905 | Non-uniform CDRX cycle | 17-17-16 | 6 | 4 | H | 11 | 11 | 90.15 % | -3.25 % | 33.9% | - | | +| ZTE | 6 | R1-2211905 | Uniform non-integer CDRX cycle | (1000/60) | 6 | 4 | H | 11 | 11 | 90.18 % | -3.22 % | 33.8% | - | | +| ZTE | 7 | R1-2211905 | Multiple CDRX (3 CDRX configurations) | 50ms DRX cycle | 6 | 4 | H | 11 | 11 | 90.1 % | -3.31 % | 34% | - | | + +NOTE 1: startOffset = ExpectedArrival - FixedTimeShift + +NOTE 2: scalingFactor X={1/2, 1/4} + +Based on the evaluation results in Table B.2.2-3, the following observations can be made: + +- For FR1, DL only evaluation, InH, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from Nokia that: + - adaptive DRX provides: + - mean power saving gain of 16.33% in the range of 15.00% to 19.00% for all UEs + - mean capacity gain of -57.90% in the range of -73.7% to -26.3% + - semi-static CDRX periodicity alignment and R15/16 CDRX provides: + - capacity gain of -100% +- For FR1, DL only evaluation, InH, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from ZTE that: + - dynamic alignment provides power: + - saving gain of 33% for all UEs + - capacity gain of -3.31%. + +- semi-static alignment as the performance reference provides: + - mean power saving gain of 33.90% in the range of 33.80% to 34% for all UEs + - mean capacity gain of -3.26% in the range of -3.22% to -3.31%. + +**Table B.2.2-4: FR2, DL-only, InH, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------------------------------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|------------------------| +| QC | 39 | R1-2212134 | Always On | - | - | - | H | 7 | 7 | 90% | 0.0% | 0% | | +| QC | 40 | R1-2212134 | eCDRX + PDCCH skipping | 16 | 4 | 4 | H | 7 | 7 | 27% | -70.0% | 31.5% | Note 1 | +| QC | 41 | R1-2212134 | eCDRX + PDCCH skipping | 16 | 8 | 8 | H | 7 | 7 | 84% | -6.7% | 17.4% | Note 1 | +| QC | 42 | R1-2212134 | eCDRX + PDCCH skipping | 16 | 8 | 16 | H | 7 | 7 | 88% | -2.2% | 12.7% | Note 1 | +| QC | 43 | R1-2212134 | Enhancement: eCDRX + PDCCH skipping + Adaptive ON Start | 16 | 4 | 4 | H | 7 | 7 | 27% | -70.0% | 60.5% | Note 1 | +| QC | 44 | R1-2212134 | Enhancement: eCDRX + PDCCH skipping + Adaptive ON Start | 16 | 8 | 8 | H | 7 | 7 | 84% | -6.7% | 48.9% | Note 1 | +| QC | 45 | R1-2212134 | Enhancement: eCDRX + PDCCH skipping + Adaptive ON Start | 16 | 8 | 16 | H | 7 | 7 | 88% | -2.2% | 42.7% | Note 1 | +| QC | 46 | R1-2212134 | eCDRX + PDCCH skipping | 16 | 4 | 4 | H | 7 | 7 | 27% | -70.0% | 45.5% | Note 2 | +| QC | 47 | R1-2212134 | eCDRX + PDCCH skipping | 16 | 8 | 8 | H | 7 | 7 | 84% | -6.7% | 43.1% | Note 2 | +| QC | 48 | R1-2212134 | eCDRX + PDCCH skipping | 16 | 8 | 16 | H | 7 | 7 | 88% | -2.2% | 43.7% | Note 2 | +| QC | 49 | R1-2212134 | Enhancement: eCDRX + PDCCH skipping + Adaptive ON Start | 16 | 4 | 4 | H | 7 | 7 | 27% | -70.0% | 74.5% | Note 2 | +| QC | 50 | R1-2212134 | Enhancement: eCDRX + PDCCH skipping + Adaptive ON Start | 16 | 8 | 8 | H | 7 | 7 | 84% | -6.7% | 74.6% | Note 2 | +| QC | 51 | R1-2212134 | Enhancement: eCDRX + PDCCH skipping + Adaptive ON Start | 16 | 8 | 16 | H | 7 | 7 | 88% | -2.2% | 73.7% | Note 2 | + +NOTE 1: PDCCH skipping inside ON duration only + +NOTE 2: PDCCH skipping inside ON duration and for IAT (early IAT termination) + +Based on the evaluation results in Table B.2.2-4, the following observations can be made: + +- For FR2, DL only evaluation, InH, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from Qualcomm that: + - adaptive On Start (on top of semi-static alignment and PDCCH skipping) provides: + - mean power saving gain of 62.48% in the range of 42.70% and 74.60% for all UEs + - mean capacity gain of -26.30% in the range of -70.0% to -2.2% + - semi-static alignment and PDCCH skipping as the performance reference provides: + - mean power saving gain of 32.32% in the range of 12.70% to 45.50% for all UEs + - mean capacity gain of -26.30% in the range of -70.0% to -2.2% + +**Table B.2.2-5: FR1, DL-only, DU, CG30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| Nokia | | R1-2206225 | Always On Baseline | - | - | - | H | 8 | 8 | 96% | | 0.0% | - | | +| Nokia | 1 | R1-2206225 | CDRX | 16 | 8 | 8 | H | 8 | 6 | 50% | -48% | 13.30% | - | | +| Nokia | 2 | R1-2206225 | Adaptive DRX | 16 | [1,16] | 0 | H | 8 | 6 | 69% | -28% | 12.00% | - | Note 1 | +| Nokia | 3 | R1-2206225 | Adaptive DRX | 16 | [8,16] | 0 | H | 8 | 7 | 76% | -20% | 9.00% | - | Note 2 | +| Nokia | 4 | R1-2206225 | Adaptive DRX | 16 | [4,12] | 0 | H | 8 | 3 | 5% | -94% | 22.00% | - | Note 3 | + +NOTE 1: Onduration can be adapted in the range indicated in ODT column. +NOTE 2: Onduration can be adapted in the range indicated in ODT column. Range for startOffset adaptation was [0,2]ms +NOTE 3: Onduration can be adapted in the range indicated in ODT column. Range for startOffset adaptation was [0,4]ms + +Based on the evaluation results in Table B.2.2-5, the following observations can be made: + +- For FR1, DL only evaluation, DU, high load, CG 30Mbps traffic at 60fps and 15ms PDB, it is observed from Nokia that: + - adaptive DRX provides: + - mean power saving gain of 13.33% in the range of 9.00% to 22.00% for all UEs + - mean capacity gain of -47.33xx% in the range of -20% to X-94%% + - R15/16 CDRX provides: + - mean power saving gain of 13.30% for all UEs + - capacity gain of -48% + +**Table B.2.2-6: FR1, DL-only, DU, AR/VR30** + +| source | data row | Tdoc source | Power saving scheme | CDRX cycle | ODT (ms) | IAT | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs | Mean PSG of satisfied | Additional Assu | +|--------|----------|-------------|---------------------|------------|----------|-----|----------|----------|------------------|-------------------|-------------------|---------------------|-----------------------|-----------------| +|--------|----------|-------------|---------------------|------------|----------|-----|----------|----------|------------------|-------------------|-------------------|---------------------|-----------------------|-----------------| + +| | w ind ex | | | (ms) | | ( m s ) | | l | | | | (%) | d UEs (%) | mptio ns | +|--------|----------|-------------|--------------------|------|--------|---------|---|---|---|-----|-------|-------|-----------|----------| +| No kia | | R1-2206 225 | Always On Baseline | - | - | - | H | 6 | 6 | 96% | | 0.0% | - | | +| No kia | 1 | R1-2206 225 | CDRX | 16 | 8 | 8 | H | 6 | 0 | 0% | -100% | 0.0% | - | | +| No kia | 2 | R1-2206 225 | Adaptive DRX | 16 | [1,16] | 0 | H | 6 | 4 | 25% | -73% | 9.3% | - | Note 1 | +| No kia | 3 | R1-2206 225 | Adaptive DRX | 16 | [8,16] | 0 | H | 6 | 5 | 71% | -26% | 13% | - | Note 2 | +| No kia | 4 | R1-2206 225 | Adaptive DRX | 16 | [4,12] | 0 | H | 6 | 2 | 5% | -69% | 18.2% | - | Note 3 | + +NOTE 1: Onduration can be adapted in the range indicated in ODT column. +NOTE 2: Onduration can be adapted in the range indicated in ODT column. Range for startOffset adaptation was [0,2]ms +NOTE 3: Onduration can be adapted in the range indicated in ODT column. Range for startOffset adaptation was [0,3]ms + +Based on the evaluation results in Table B.2.2-6, the following observations can be made: + +- For FR1, DL only evaluation, DU, high load, AR/VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from Nokia that: + - adaptive DRX provides: + - mean power saving gain of 13.5% in the range of 9.3% to 18.2% for all UEs + - mean capacity gain of -56% in the range of -26% to -73% + - R15/16 CDRX provides: + - mean power saving gain of 0% for all UEs + - capacity gain of -100% + +### B.2.3 Non-uniform PMOs within CDRX On Duration + +This clause captures evaluation results for non-uniform PDCCH monitoring occasions (PMOs) within CDRX On Duration: + +- Huawei evaluated configuring non-uniform PDCCH monitoring occasions within C-DRX On Duration based on bitmap to match with jitter distribution. + +**Table B.2.3-1: FR1, DL-only, DU, VR30** + +| so urc e | dat a ro w ind ex | Tdoc sour ce | Power saving scheme | CDRX cycle (ms) | O D T (m s) | IAT (ms ) | Loa d H/L | #U E /cel l | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|----------|-------------------|--------------|---------------------|-----------------|-------------|-----------|-----------|-------------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| Huawei | 4 | R1-2210 906 | Always On | - | 12 | 4 | H | 11 | 11 | 93.42 % | 0.0% | 0.0% | - | | +| Huawei | 5 | R1-2210 906 | Legacy C-DRX | 16 | 12 | 4 | H | 11 | 11 | 83.20 % | -10.9% | 5.57% | - | | +| Huawei | 6 | R1-2210 906 | Aligned CDRX | 50 {0, 16, 33} | 12 | 4 | H | 11 | 11 | 91.43 % | -2.1% | 7.64% | - | Note 1 | +| Huawei | 7 | R1-2210 906 | Aligned CDRX | 50 {0, 16, 33} | 12 | 4 | H | 11 | 11 | 85.89 % | -8.1% | 15.81% | - | Note 2 | + +| | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|------------|---------------------------------|----------------|----|---|---|----|----|---------|-------|--------|---|--------| +| ei | | 906 | 33} | | | | | | | | | | | | +| Huawei | 8 | R1-2210906 | Aligned CDRX + Non-uniform PMOs | 50 {0, 16, 33} | 12 | 4 | H | 11 | 11 | 89.70 % | -4.0% | 16.23% | - | Note 3 | +| Huawei | 9 | R1-2210906 | Aligned CDRX + Non-uniform PMOs | 50 {0, 16, 33} | 12 | 4 | H | 11 | 11 | 85.71 % | -8.3% | 20.75% | - | Note 4 | +| NOTE 1: PDCCH monitoring pattern within DRX On Duration is [1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1]
NOTE 2: PDCCH monitoring pattern within DRX On Duration is [0, 0, 0, 0, 1, 1, 1, 1, 0, 0, 0, 0, 1, 1, 1, 1, 0, 0, 0, 0, 1, 1, 1, 1]
NOTE 3: PDCCH monitoring pattern within DRX On Duration is [0, 0, 0, 0, 1, 0, 1, 0, 0, 1, 1, 1, 1, 1, 0, 1, 1, 0, 1, 0, 1, 0, 0, 1]
NOTE 4: PDCCH monitoring pattern within DRX On Duration is [0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 1, 1, 1, 0, 1, 0, 1, 0, 0, 1, 0, 0, 0, 0]
In the PDCCH monitoring pattern, 1 indicates a slot with PDCCH monitoring and 0 indicates a slot without PDCCH monitoring. | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.3-1, the following observations can be made: + +- For FR1, DL only evaluation, DU, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from Huawei that: + - non-uniform PMOs within On Duration provides: + - mean power saving gain of 18.49% in the range of 16.23% and 20.75% for all UEs + - mean capacity gain of -6.15% in the range of -8.3% to -4.0% + - sparse PDCCH monitoring as the performance reference provides: + - mean power saving gain of 11.73% in the range of 7.64% to 15.81% for all UEs + - mean capacity gain of -5.10% in the range of -8.1% to -2.1% + +### B.2.4 Two-stage CDRX On Duration + +This clause captures evaluation results for two-stage CDRX On Duration + +- Ericsson evaluated the two-stage DRX solution with multiple inner On Durations within the outer On Duration and compared its performance with that of R17 PDCCH monitoring adaptation. +- vivo compared R17 PDCCH monitoring adaptation and the two-stage On-Duration by performance evaluations. + +**Table B.2.4-1: FR1, DL+UL, DU, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE / cell | floor (Capacity) | % of DL satisfied UE | % of UL satisfied UE | % of DL + UL satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|----------|----------------|-------------|------------------------|-----------------|----------|----------|----------|------------|------------------|----------------------|----------------------|---------------------------|-------------------|-------------------------|-------------------------------|------------------------| +| Ericsson | 35 | R1-2210922 | Always On | - | - | - | H | 8 | 8 | - | - | 90.1 % | 0.0% | - | - | Note1 | +| | 38 | R1-2210922 | Matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | - | - | 85.5 % | -5.1 % | 7.2% | 7.1% | Note1,2 | +| | 40 | R1-2210922 | PDCCH skipping & match | 16.6 | 10 | 4 | H | 8 | 8 | - | - | 84.7 % | -6.0 % | 7.6% | 7.6% | Note1,2 | + +| | | | | | | | | | | | | | | | | | +|------------------|----|------------|---------------------------------------------------------------------------------------|---------------------------------|-------------------------------|---|---|---|---|---|---|--------|---------|--------|--------|-------------| +| | | | ed
CDRX | | | | | | | | | | | | | | +| Eri
css
on | 41 | R1-2210922 | R17 SSSG switching (sparse SSSG: 2 ms on / 2 ms off) & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | - | - | 66.0 % | -26.7 % | 10.3 % | 10.3 % | Note1
,2 | +| Eri
css
on | 42 | R1-2210922 | R17 SSSG switching (sparse SSSG: 1 ms on / 1 ms off) & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | - | - | 79.8 % | -11.4 % | 10.7 % | 10.7 % | Note1
,2 | +| Eri
css
on | 43 | R1-2210922 | R17 SSSG switching (sparse SSSG: 1 ms on / 1 ms off) & PDCC H skipping & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | - | - | 79.9 % | -11.3 % | 11.3 % | 11.2 % | Note1
,2 | +| Eri
css
on | 44 | R1-2210922 | Two-stage DRX & matched CDRX | outer DR X: 16.6; inner DR X: 4 | outer OD T: 10; inner OD T: 2 | 4 | H | 8 | 8 | - | - | 80.2 % | -11.0 % | 9.1% | 9.1% | Note1
,3 | +| Eri
css
on | 45 | R1-2210922 | Two-stage DRX & matched CDRX | outer DR X: 16.6; inner DR X: 2 | outer OD T: 10; inner OD T: 1 | 4 | H | 8 | 8 | - | - | 81.5 % | -9.5 % | 10.7 % | 10.7 % | Note1
,3 | +| Eri
css
on | 46 | R1-2210922 | Two-stage DRX & PDCC H skipping & matched CDRX | outer DR X: 16.6; inner DR X: 2 | outer OD T: 10; inner OD T: 1 | 4 | H | 8 | 8 | - | - | 79.8 % | -11.4 % | 9.5% | 9.5% | Note1
,3 | + +| | | | ed CDRX | DR X: 4 | T: 2 | | | | | | | | | | | | +|-----------|----|------------|------------------------------------------------|---------------------------------|-------------------------------|---|---|---|---|---|---|--------|---------|--------|--------|----------| +| Eri csson | 47 | R1-2210922 | Two-stage DRX & PDCC H skipping & matched CDRX | outer DR X: 16.6; inner DR X: 2 | outer OD T: 10; inner OD T: 1 | 4 | H | 8 | 8 | - | - | 80.7 % | -10.4 % | 11.5 % | 11.5 % | Note1 ,3 | + +NOTE 1: the DL traffic has a second flow for audio with 30ms PDB +NOTE 2: Matched CDRX cycle has (drx\_offset=3, traffic\_time\_offset=2 ms, drx-LongCycle=16 ms) +NOTE 3: Outer CDRX cycle has (drx\_offset=3, traffic\_time\_offset=2 ms, drx-LongCycle=16 ms) + +Based on the evaluation results in Table B.2.4-1, the following observations can be made: + +- For FR1, DL + UL joint evaluation, DU, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from Ericsson that: + - two-stage CDRX On Duration provides: + - mean power saving gain of 10.20% in the range of 9.10% to 11.50% for all UEs + - mean capacity gain of -10.58% in the range of -11.4% to -9.5% + - sparse PDDCH monitoring followed by SSSG switching as the performance reference provides: + - mean power saving gain of 10.77% in the range of 10.30% to 11.30% for all UEs + - mean capacity gain of -16.47% in the range of -26.7% to -11.3% + +**Table B.2.4-2: FR1, DL-only, DU, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE / cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|-----------|----------------|-------------|---------------------------------------------------------------------|-----------------|----------|----------|----------|------------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| Eri csson | 1 | R1-2210922 | Always On | - | - | - | H | 8 | 8 | 91.7% | 0.0% | 0.0% | 0.0% | | +| Eri csson | 4 | R1-2210922 | Matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | 87.2% | -4.9% | 10.5% | 11.4% | Note 1 | +| Eri csson | 6 | R1-2210922 | PDCC skipping & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | 87.3% | -4.8% | 15.8% | 16.0% | Note 1 | +| Eri csson | 7 | R1-2210922 | R17 SSSG switching (sparse SSSG: 2 ms on / 2 ms off) & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | 53.9% | -41.2% | 15.5% | 16.0% | Note 1 | +| Eri csson | 8 | R1-2210922 | R17 SSSG switching (sparse SSSG: 1 ms on / 1 ms off) & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | 78.4% | -14.5% | 16.4% | 16.5% | Note 1 | +| Eri csson | 9 | R1-2210 | R17 SSSG | 16.6 | 10 | 4 | H | 8 | 8 | 78.9% | -14.0% | 20.2% | 20.4% | Note 1 | + +| | | | | | | | | | | | | | | | +|------------------|----|----------------|----------------------------------------------------------------------------|-------------------------------|-----------------------------|---|---|---|---|-------|--------|-------|-------|--------| +| on | | 922 | switching (sparse SSG: 1 ms on / 1 ms off) & PDCCH skipping & matched CDRX | | | | | | | | | | | | +| Eri
css
on | 10 | R1-2210
922 | Two-stage DRX & matched CDRX | outer DRX: 16.6; inner DRX: 4 | outer ODT: 10; inner ODT: 2 | 4 | H | 8 | 8 | 79.2% | -13.6% | 14.8% | 15.1% | Note 2 | +| Eri
css
on | 11 | R1-2210
922 | Two-stage DRX & matched CDRX | outer DRX: 16.6; inner DRX: 2 | outer ODT: 10; inner ODT: 1 | 4 | H | 8 | 8 | 80.2% | -12.5% | 16.2% | 16.6% | Note 2 | +| Eri
css
on | 12 | R1-2210
922 | Two-stage DRX & PDCCH skipping & matched CDRX | outer DRX: 16.6; inner DRX: 4 | outer ODT: 10; inner ODT: 2 | 4 | H | 8 | 8 | 78.6% | -14.3% | 19.2% | 19.4% | Note 2 | +| Eri
css
on | 13 | R1-2210
922 | Two-stage DRX & PDCCH skipping & matched CDRX | outer DRX: 16.6; inner DRX: 2 | outer ODT: 10; inner ODT: 1 | 4 | H | 8 | 8 | 80.4% | -12.3% | 20.4% | 20.6% | Note 2 | +| Eri
css
on | 18 | R1-2210
922 | Always On | - | - | - | L | 2 | 8 | 100% | 0.0% | 0.0% | 0.0% | | +| Eri
css
on | 20 | R1-2210
922 | Matched CDRX | 16.6 | 10 | 4 | L | 2 | 8 | 100% | 0.0% | 12.8% | 12.8% | Note 1 | +| Eri
css
on | 23 | R1-2210
922 | PDCCH skipping & matched CDRX | 16.6 | 10 | 4 | L | 2 | 8 | 100% | 0.0% | 22.5% | 22.5% | Note 1 | +| Eri
css
on | 24 | R1-2210
922 | R17 SSSG switching (sparse SSG: 2 ms on / 2 ms off) & matched CDRX | 16.6 | 10 | 4 | L | 2 | 8 | 82.9% | -17.1% | 18.2% | 18.2% | Note 1 | +| Eri
css
on | 25 | R1-2210
922 | R17 SSSG switching (sparse SSG: 1 ms on / 1 ms off) & matched CDRX | 16.6 | 10 | 4 | L | 2 | 8 | 100% | 0.0% | 19.2% | 19.2% | Note 1 | +| Eri
css
on | 26 | R1-2210
922 | R17 SSSG switching (sparse SSG: 1 ms on / 1 ms off) & PDCCH skipping | 16.6 | 10 | 4 | L | 2 | 8 | 100% | 0.0% | 26.6% | 26.6% | Note 1 | + +| | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------|----|------------|-----------------------------------------------|-------------------------------|-----------------------------|---|---|---|---|------|------|-------|-------|--------| +| | | | & matched CDRX | | | | | | | | | | | | +| Eri
css
on | 27 | R1-2210922 | Two-stage DRX & matched CDRX | outer DRX: 16.6; inner DRX: 4 | outer ODT: 10; inner ODT: 2 | 4 | L | 2 | 8 | 100% | 0.0% | 16.7% | 16.7% | Note 2 | +| Eri
css
on | 28 | R1-2210922 | Two-stage DRX & matched CDRX | outer DRX: 16.6; inner DRX: 2 | outer ODT: 10; inner ODT: 1 | 4 | L | 2 | 8 | 100% | 0.0% | 19.0% | 19.0% | Note 2 | +| Eri
css
on | 29 | R1-2210922 | Two-stage DRX & PDCCH skipping & matched CDRX | outer DRX: 16.6; inner DRX: 4 | outer ODT: 10; inner ODT: 2 | 4 | L | 2 | 8 | 100% | 0.0% | 25.9% | 25.9% | Note 2 | +| Eri
css
on | 30 | R1-2210922 | Two-stage DRX & PDCCH skipping & matched CDRX | outer DRX: 16.6; inner DRX: 2 | outer ODT: 10; inner ODT: 1 | 4 | L | 2 | 8 | 100% | 0.0% | 27.0% | 27.0% | Note 2 | +| NOTE 1: Matched CDRX cycle has (drx_offset=3, traffic_time_offset=2 ms, drx-LongCycle=16 ms) | | | | | | | | | | | | | | | +| NOTE 2: Outer CDRX cycle has (drx_offset=3, traffic_time_offset=2 ms, drx-LongCycle=16 ms) | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.4-2, the following observations can be made: + +- For FR1, DL only, DU, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from Ericsson that: + - two-stage CDRX On Duration provides: + - mean power saving gain of 17.65% in the range of 4.80% to 20.40% for all UEs + - mean capacity gain of -13.18% in the range of -14.30% to -12.30% + - sparse PDDCH monitoring followed by SSSG switching as the performance reference provides: + - mean power saving gain of 17.37% in the range of 15.50% to 20.20% for all UEs + - mean capacity gain of -23.23% in the range of -41.20% to -14.00% +- For FR1, DL only, DU, low load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from Ericsson that: + - two-stage CDRX On Duration provides: + - mean power saving gain of 22.15% in the range of 6.70% to 27.00% for all UEs + - mean capacity gain of 0% + - sparse PDDCH monitoring followed by SSSG switching as the performance reference provides: + - mean power saving gain of 21.33% in the range of 18.20% to 26.60% for all UEs + - mean capacity gain of -5.70% in the range of 0.00% to -17.10% + +**Table B.2.4-3: FR1, DL-only, InH, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE / cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------|-----------------|----------|----------|----------|------------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +|--------|----------------|-------------|---------------------|-----------------|----------|----------|----------|------------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| + +| | ex | | | | | | | | | | | | | | +|------|----|------------|---------------------------------|------------------------------------|---------------------------------|--------------------------------|---|----|----|---------|-------|---------|---|----------| +| vivo | | R1-2211024 | Always On | - | - | - | L | 5 | 10 | 100% | 0.0% | 0.0% | - | | +| vivo | | R1-2211024 | R17 PDCCH monitoring adaptation | 16.67 | 8 | 4 | L | 5 | 10 | 100% | 0.0% | 23.36 % | - | Note1 ,2 | +| vivo | | R1-2211024 | R17 PDCCH monitoring adaptation | 16.67 | 8 | 4 | L | 5 | 10 | 100% | 0.0% | 25.39 % | - | Note1 ,3 | +| vivo | | R1-2211024 | Two-stage CDRX | Outer CDRX: 16.67
Inner CDRX: 4 | Outer CDRX: 10
Inner CDRX: 2 | Outer CDRX: 4
Inner CDRX: 4 | L | 5 | 10 | 100% | 0.0% | 21.52 % | - | Note4 | +| vivo | | R1-2211024 | Always On | - | - | - | H | 10 | 10 | 92.50 % | 0.0% | 0.0% | - | | +| vivo | | R1-2211024 | R17 PDCCH monitoring adaptation | 16.67 | 8 | 4 | H | 10 | 10 | 92.22 % | -0.3% | 19.28 % | - | Note1 ,2 | +| vivo | | R1-2211024 | R17 PDCCH monitoring adaptation | 16.67 | 8 | 4 | H | 10 | 10 | 88.52 % | -4.3% | 21.84 % | - | Note1 ,3 | +| vivo | | R1-2211024 | Two-stage CDRX | Outer CDRX: 16.67
Inner CDRX: 4 | Outer CDRX: 10
Inner CDRX: 2 | Outer CDRX: 4
Inner CDRX: 4 | H | 10 | 10 | 86.89 % | -6.1% | 16.36 % | - | Note4 | + +NOTE 1: PDCCH skipping is indicated in the DCI that schedules a dummy PDSCH after all the HARQ-ACK processes of transmissions have been completed + +NOTE 2: applying R17 sparse SSSG with PDCCH monitoring every 2 slots when DRX Onduration starts and switch to dense SSSG with PDCCH monitoring every 1 slot after detecting DCI scheduling XR traffic burst + +NOTE 3: applying R17 sparse SSSG with PDCCH monitoring every 4 slots when DRX Onduration starts and switch to dense SSSG with PDCCH monitoring every 1 slot after detecting DCI scheduling XR traffic burst + +NOTE 4: 4ms CDRX cycle and 2ms ODT for inner CDRX + +Based on the evaluation results in Table B.2.4-3, the following observations can be made: + +- For FR1, DL only, InH, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from vivo that: + - two-stage CDRX On Duration provides: + - power saving gain of 16.36% for all UEs + - capacity gain of -6.1% + - sparse PDCCH monitoring followed by SSSG switching as the performance reference provides: + - mean power saving gain of 20.56% in the range of 19.28% to 21.84% for all UEs + - mean capacity gain of -2.3% in the range of -4.3% to -0.3% +- For FR1, DL only, InH, low load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from vivo that: + +- two-stage CDRX On Duration provides: + - power saving gain of 21.52% for all UEs + - mean capacity gain of 0.0% +- sparse PDDCH monitoring followed by SSSG switching as the performance reference provides: + - mean power saving gain of 24.38% in the range of 23.36% to 25.39% for all UEs + - mean capacity gain of 0.0% + +### B.2.5 Jitter handling by LP-WUS + +This clause captures evaluation results for LP-WUS based jitter handling + +- vivo and Xiaomi evaluated LP-WUS based wakeup mechanism for XR traffic in presence of jitter, i.e., UE wakes up after a LP-WUS is detected. LP-WUS evaluation methodologies such as power modelling of WUS detection and gap between detected LP-WUS and UE wakeup are based on their own assumptions. + +**Table FR1 B.2.5-1, DL-only, DU, VR45** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE / cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|-----------------------|-----------------|----------|----------|----------|------------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| Xiaomi | 1 | R1-2211341 | Always On | - | - | - | H | 3 | 3 | 96.61% | 0.0% | - | 0.0% | | +| Xiaomi | 2 | R1-2211341 | Rel-17 PDCCH skipping | - | - | - | H | 3 | 3 | 95% | -1.7% | - | 41.74% | Note 1 | +| Xiaomi | 4 | R1-2211341 | LP-WUS | - | - | - | H | 3 | 3 | 95% | -1.7% | - | 54.92% | Note 1, 2, 3 | + +NOTE 1: PDCCH skipping with 2 candidate durations(8/10ms) +NOTE 2: the relative power of LP WUS monitoring is assumed to be 1 +NOTE 3: the resource overhead for LP WUS is not considered + +Based on the evaluation results in Table B.2.5-1, the following observations can be made: + +- For FR1, DL only, DU, high load, VR 45Mbps traffic at 60fps and 10ms PDB, it is observed from Xiaomi that: + - LP-WUS based jitter handling provides: + - power saving gain of 54.92% for satisfied UEs + - mean capacity gain of -1.7% + +**Table B.2.5-2: FR1, DL-only, InH, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE / cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------|-----------------|----------|----------|----------|------------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| vivo | | R1-2211024 | Always On | - | - | - | L | 5 | 10 | 100% | 0.0% | - | - | Note1 | +| vivo | | R1-2211024 | Always On | - | - | - | L | 5 | 10 | 100% | 0.0% | - | - | Note2 | +| vivo | | R1-2211024 | Always On | - | - | - | L | 5 | 10 | 100% | 0.0% | - | - | Note3 | +| vivo | | R1- | Always | - | - | - | L | 5 | 10 | 100% | 0.0% | - | - | Note4 | + +| | | | | | | | | | | | | | | | +|-------|--|-------------|---------------------------------|-------|----|---|---|----|----|---------|---------|---------|---|------------------| +| o | | 2211 024 | On | | | | | | | | | | | | +| viv o | | R1-2211 024 | R17 PDCCH monitoring adaptation | 16.67 | 8 | 4 | L | 5 | 10 | 100% | 0.0% | 23.36 % | - | Note1 ,5,6 | +| viv o | | R1-2211 024 | R17 PDCCH monitoring adaptation | 16.67 | 12 | 4 | L | 5 | 10 | 100% | 0.0% | 18.73 % | - | Note2 ,5,6 | +| viv o | | R1-2211 024 | R17 PDCCH monitoring adaptation | 16.67 | 16 | 4 | L | 5 | 10 | 100% | 0.0% | 15.79 % | - | Note3 ,5,6 | +| viv o | | R1-2211 024 | R17 PDCCH monitoring adaptation | 16.67 | 16 | 4 | L | 5 | 10 | 100% | 0.0% | 13.91 % | - | Note4 ,5,6 | +| viv o | | R1-2211 024 | LP-WUS scheme | 16.67 | 8 | 4 | L | 5 | 10 | 100% | 0.0% | 29.71 % | - | Note1 ,5,7,1 0 | +| viv o | | R1-2211 024 | LP-WUS scheme | 16.67 | 12 | 4 | L | 5 | 10 | 100% | 0.0% | 28.26 % | - | Note2 ,5,7,1 0 | +| viv o | | R1-2211 024 | LP-WUS scheme | 16.67 | 16 | 4 | L | 5 | 10 | 100% | 0.0% | 29.36 % | - | Note3 ,5,7,1 0 | +| viv o | | R1-2211 024 | LP-WUS scheme | 16.67 | 16 | 4 | L | 5 | 10 | 100% | 0.0% | 29.28 % | - | Note4 ,5,7,1 0 | +| viv o | | R1-2211 024 | LP-WUS scheme | 16.67 | 8 | 4 | L | 5 | 10 | 89.44 % | -10.6 % | 34.10 % | - | Note1 ,5,8,1 0 | +| viv o | | R1-2211 024 | LP-WUS scheme | 16.67 | 12 | 4 | L | 5 | 10 | 87.22 % | -12.8 % | 34.83 % | - | Note2 ,5,8,1 0 | +| viv o | | R1-2211 024 | LP-WUS scheme | 16.67 | 16 | 4 | L | 5 | 10 | 87.60 % | -12.4 % | 37.87 % | - | Note3 ,5,8,1 0 | +| viv o | | R1-2211 024 | LP-WUS scheme | 16.67 | 8 | 4 | L | 5 | 10 | 99.44 % | -0.6% | 34.10 % | - | Note1 ,5,8,9 ,10 | +| viv o | | R1-2211 024 | LP-WUS scheme | 16.67 | 12 | 4 | L | 5 | 10 | 99.44 % | -0.6% | 34.83 % | - | Note2 ,5,8,9 ,10 | +| viv o | | R1-2211 024 | LP-WUS scheme | 16.67 | 16 | 4 | L | 5 | 10 | 99.33 % | -0.7% | 37.87 % | - | Note3 ,5,8,9 ,10 | +| viv o | | R1-2211 024 | Always On | - | - | - | H | 10 | 10 | 92.50 % | 0.0% | - | - | Note1 | +| viv o | | R1-2211 024 | Always On | - | - | - | H | 10 | 10 | 92.33 % | 0.0% | - | - | Note2 | +| viv o | | R1-2211 024 | Always On | - | - | - | H | 10 | 10 | 91.83 % | 0.0% | - | - | Note3 | +| viv o | | R1-2211 024 | Always On | - | - | - | H | 10 | 10 | 90.94 % | 0.0% | - | - | Note4 | +| viv o | | R1-2211 024 | R17 PDCCH monitoring adaptation | 16.67 | 8 | 4 | H | 10 | 10 | 92.22 % | -0.3% | 19.28 % | - | Note1 ,5,6 | +| viv o | | R1-2211 024 | R17 PDCCH | 16.67 | 12 | 4 | H | 10 | 10 | 92.16 % | -0.2% | 14.96 % | - | Note2 ,5,6 | + +| | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|------------|---------------------------------|-------|----|---|---|----|----|---------|---------|---------|---|----------------| +| | | 024 | monitoring adaptation | | | | | | | | | | | | +| vivo | | R1-2211024 | R17 PDCCH monitoring adaptation | 16.67 | 16 | 4 | H | 10 | 10 | 91.05 % | -0.8% | 12.26 % | - | Note3,5,6 | +| vivo | | R1-2211024 | R17 PDCCH monitoring adaptation | 16.67 | 16 | 4 | H | 10 | 10 | 91.01 % | 0.1% | 11.17 % | - | Note4,5,6 | +| vivo | | R1-2211024 | LP-WUS scheme | 16.67 | 8 | 4 | H | 10 | 10 | 92.22 % | -0.3% | 25.10 % | - | Note1,5,7,10 | +| vivo | | R1-2211024 | LP-WUS scheme | 16.67 | 12 | 4 | H | 10 | 10 | 92.20 % | -0.1% | 24.08 % | - | Note2,5,7,10 | +| vivo | | R1-2211024 | LP-WUS scheme | 16.67 | 16 | 4 | H | 10 | 10 | 91.08 % | -0.8% | 24.68 % | - | Note3,5,7,10 | +| vivo | | R1-2211024 | LP-WUS scheme | 16.67 | 16 | 4 | H | 10 | 10 | 91.11 % | 0.2% | 25.90 % | - | Note4,5,7,10 | +| vivo | | R1-2211024 | LP-WUS scheme | 16.67 | 8 | 4 | H | 10 | 10 | 54.17 % | -41.4 % | 29.22 % | - | Note1,5,8,10 | +| vivo | | R1-2211024 | LP-WUS scheme | 16.67 | 12 | 4 | H | 10 | 10 | 53.61 % | -41.9 % | 30.26 % | - | Note2,5,8,10 | +| vivo | | R1-2211024 | LP-WUS scheme | 16.67 | 16 | 4 | H | 10 | 10 | 54.86 % | -40.3 % | 33.18 % | - | Note3,5,8,10 | +| vivo | | R1-2211024 | LP-WUS scheme | 16.67 | 8 | 4 | H | 10 | 10 | 82.78 % | -10.5 % | 29.22 % | - | Note1,5,8,9,10 | +| vivo | | R1-2211024 | LP-WUS scheme | 16.67 | 12 | 4 | H | 10 | 10 | 82.25 % | -10.9 % | 30.26 % | - | Note2,5,8,9,10 | +| vivo | | R1-2211024 | LP-WUS scheme | 16.67 | 16 | 4 | H | 10 | 10 | 82.51 % | -10.1 % | 33.18 % | - | Note3,5,8,9,10 | +| NOTE 1: jitter range = [-4, +4]ms, STD=2ms | | | | | | | | | | | | | | | +| NOTE 2: jitter range = [-6, +6]ms, STD=2ms | | | | | | | | | | | | | | | +| NOTE 3: jitter range = [-8, +8]ms, STD=5ms | | | | | | | | | | | | | | | +| NOTE 4: jitter range = [-10, +10]ms, STD=5ms | | | | | | | | | | | | | | | +| NOTE 5: PDCCH skipping is indicated in the DCI that schedules a dummy PDSCH after all the HARQ-ACK processes of transmissions have been completed | | | | | | | | | | | | | | | +| NOTE 6: applying R17 sparse SSSG with PDCCH monitoring every 2 slots when DRX Onduration starts and switch to dense SSSG with PDCCH monitoring every 1 slot after detecting DCI scheduling XR traffic burst | | | | | | | | | | | | | | | +| NOTE 7: the total relative power (including the power of both LP-WUR and main radio) for LP-WUS monitoring is 45 units with no wake-up latency | | | | | | | | | | | | | | | +| NOTE 8: the total relative power (including the power of both LP-WUR and main radio) for LP-WUS monitoring is 20 units with 3ms wake-up latency | | | | | | | | | | | | | | | +| NOTE 9: UE satisfaction metric as 95% packet successful rate | | | | | | | | | | | | | | | +| NOTE 10: the resource overhead for LP WUS is not considered | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.5-2, the following observations can be made: + +- For FR1, DL only, InH, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from vivo that: + - LP-WUS jitter handling provides: + - mean power saving gain of 28.51% in the range of 24.08% to 33.18% for all UEs + - mean capacity gain of -15.61% in the range of -41.90% to -0.10% + +- sparse PDDCH monitoring followed by SSSG switching to dense PDCCH monitoring as the performance reference provides: + - mean power saving gain of 14.42% in the range of 11.17% to 19.28% for all UEs + - mean capacity gain of -0.30% in the range of -0.80% to -0.10% for all UEs +- For FR1, DL only, InH, low load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from vivo that: + - LP-WUS jitter handling provides: + - mean power saving gain of 33.02% in the range of 29.71% to 37.87% for all UEs + - mean capacity gain of -3.77% in the range of -12.80% to 0.0% + - sparse PDDCH monitoring followed by SSSG switching to dense PDCCH monitoring as the performance reference provides: + - mean power saving gain of 17.95% in the range of 13.91% to 23.36% for all UEs + - mean capacity gain of 0% + +### B.2.6 Early stopping of On Duration Timer + +This clause captures evaluation results for early stopping of DRX On Duration Timer based on the expiration of InactivityTimer or a configured time window: + +- Huawei, Xiaomi and MediaTek evaluated early stopping of the On Duration Timer after the InactivityTimer or a configured time window expires to stop PDCCH monitoring. + +**Table B.2.6-1: FR1, DL-only, DU, VR30** + +| source | arrow index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|-------------|-------------|--------------------------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| Huawei | 11 | R1-2210906 | Always On | - | 12 | 4 | H | 11 | 11 | 93.42% | 0.0% | 0.0% | - | | +| Huawei | 12 | R1-2210906 | Aligned CDRX | 50 {0, 16, 33} | 12 | 4 | H | 11 | 11 | 91.43% | -2.1% | 7.64% | - | | +| Huawei | 13 | R1-2210906 | Aligned CDRX + early stopping of ODT | 50 {0, 16, 33} | 12 | 4 | H | 11 | 11 | 88.23% | -5.6% | 10.22% | - | | + +Based on the evaluation results in Table B.2.6-1, the following observations can be made. + +- For FR1, DL only, DU, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from Huawei that: + - on top of eCDRX, the early stopping of ODT provides: + - power saving gain of 10.22% for all UEs + - capacity gain of -5.6% + - eCDRX as the performance reference provides: + - power saving gain of 7.64% for all UEs + - capacity gain of -2.1% + +**Table B.2.6-2: FR1, DL-only, DU, CG30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|----------------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| MTK | 22 | R1-2212253 | AlwaysOn - baseline | 0 | 0 | 0 | H | 12 | 12 | 94.6% | 0.0% | 0% | - | | +| MTK | 23 | R1-2212253 | R15/16C DRX | 16 | 12 | 8 | H | 12 | 12 | 92.7% | -2.0% | 5.4% | - | | +| MTK | 24 | R1-2212253 | eCDRX (rational DRX cycle) | (50/3) | 12 | 8 | H | 12 | 12 | 94.3% | -0.3% | 9.9% | - | | +| MTK | 25 | R1-2212253 | eCDRX + stop ODT early | (50/3) | 12 | 8 | H | 12 | 12 | 92.4% | -2.3% | 16.6% | - | | + +Based on the evaluation results in Table B.2.6-2, the following observations can be made: + +- For FR1, DL only, DU, high load, CG 30Mbps traffic at 60fps and 15ms PDB, it is observed from MediaTek that: + - with eCDRX, the early stopping of ODT provides: + - power saving gain of 16.6% for all UEs + - capacity gain of -2.3% + - eCDRX as the performance reference provides: + - power saving gain of 9.9% for all UEs + - capacity gain of -0.3% + +**Table B.2.6-3: FR1, DL-only, DU, VR45** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|-------------------------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| Xiaomi | 1 | R1-2211341 | AlwaysOn | - | - | - | H | 3 | 3 | 100% | 0.0% | - | 0.0% | | +| Xiaomi | 6 | R1-2211341 | CDRX | 16/17/17 | 12 | 4 | H | 3 | 3 | 98.41% | -1.59% | - | 11.39% | | +| Xiaomi | 5 | R1-2211341 | CDRX+ On duration early termination | 16/17/17 | 12 | 4 | H | 3 | 3 | 94.92% | -5.08% | - | 43.18% | | + +Based on the evaluation results in Table B.2.6-3, the following observations can be made: + +- For FR1, DL only, DU, high load, VR 45Mbps traffic at 60fps and 10ms PDB, it is observed from Xiaomi that: + - with eCDRX, the early stopping of ODT provides: + - power saving gain of 43.18% for satisfied UEs + - capacity gain of -5.08% + - eCDRX as the performance reference provides: + +- power saving gain of 11.39% for all UEs +- capacity gain of -1.59% + +### B.2.7 Additional DRX active time + +This clause captures evaluation results for additional DRX active time. + +- ZTE evaluated the extension for additional active time if UE does not receive UE specific data scheduled by a PDCCH CRC scrambled by the XR-specific RNTI within current active time. +- OPPO evaluated additional On Duration triggered by dynamic signaling such as a DCI to receive data that arrives after the On Duration expires. +- Nokia evaluated the Extension of Active Time (EAT) to extend DRX active time if XR frame does not arrive before the On Duration timer expires. +- vivo compared the additional DRX active time and R17 PDCCH monitoring adaptation scheme. + +**Table B.2.7-1: FR1, DL+UL, InH, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | OD T (ms) | IAT (ms) | Load H/L | #UE / cell | floor (Capacity) | % of DL satisfied UE | % of UL satisfied UE | % of DL + UL satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------------------------|---------------------|-----------|----------|----------|------------|------------------|----------------------|----------------------|---------------------------|-------------------|-------------------------|-------------------------------|------------------------| +| ZTE | 52 | R1-2212596 | Always on | - | - | - | H | 11 | 11 | - | - | 90.15% | 0.00% | 0% | - | Note 1 | +| ZTE | 15 | R1-2212596 | Aligned CDRX | Aligned every 50 ms | 12 | 4 | H | 11 | 11 | 88.36% | 100% | 88.36% | -1.99% | 7.5% | - | Note 1 | +| ZTE | 16 | R1-2212596 | Additional active time + aligned CDRX | Aligned every 50 ms | 5 | 4 | H | 11 | 11 | 90% | 100% | 90% | -0.17% | 14.18% | - | Note 1,2 | + +NOTE 1: Jitter range = [-8,8]ms +NOTE 2: additional active time = original DRX On duration + +Based on the evaluation results in Table B.2.7-1, the following observations can be made: + +- For FR1, DL and UL joint evaluation, InH, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from ZTE that: + - on top of eCDRX, additional active time provides: + - power saving gain of 14.18% for all UEs + - capacity gain of -0.17%. + - eCDRX as the performance reference provides: + - power saving gain of 7.5% for all UEs + - capacity gain of -1.99%. + +**Table B.2.7-2: FR1, DL+UL, InH, VR45** + +| so | dat | Tdoc | Power | CD | OD | IAT | Lo | #U | floor | % of | % of | % of | Cap | Mea | Mea | Addit | +|----|-----|------|-------|----|----|-----|----|----|-------|------|------|------|-----|-----|-----|-------| +|----|-----|------|-------|----|----|-----|----|----|-------|------|------|------|-----|-----|-----|-------| + +| Source | Row index | Source | Saving scheme | RX cycle (ms) | T (ms) | (ms) | ad H/L | E / cell | (Capacity) | DL satisfied UE | UL satisfied UE | DL + UL satisfied UE | Capacity gain (%) | n PSG of all UEs (%) | n PSG of satisfied UEs (%) | Additional Assumptions | +|--------|-----------|------------|---------------------------------------|---------------------|--------|------|--------|----------|------------|-----------------|-----------------|----------------------|-------------------|----------------------|----------------------------|------------------------| +| ZTE | 54 | R1-2212596 | Always on | - | - | - | H | 7 | 7 | - | - | 90.48% | 0.00% | - | - | Note 1 | +| ZTE | 19 | R1-2212596 | Aligned CDRX | Aligned every 50 ms | 12 | 5 | H | 7 | 7 | 90% | 100% | 90% | -0.53% | 7.5% | - | Note 1 | +| ZTE | 20 | R1-2212596 | Additional active time + aligned CDRX | Aligned every 50 ms | 6 | 5 | H | 7 | 7 | 88.1% | 100% | 88.1% | -2.63% | 15.16% | - | Note 1,2 | + +NOTE 1: Jitter range = [-8,8]ms + +NOTE 2: additional active time = original DRX On duration + +Based on the evaluation results in Table B.2.7-2, the following observations can be made: + +- For FR1, DL and UL joint evaluation, InH, high load, VR 45Mbps traffic at 60fps and 10ms PDB, it is observed from ZTE that: + - on top of eCDRX, additional active time provides: + - power saving gain of 15.16% for all UEs + - capacity gain of -2.63%. + - eCDRX as the performance reference provides: + - power saving gain of 7.5% for all UEs + - capacity gain of -0.53%. + +Table B.2.7-3: FR1, DL+UL, InH, CG30 + +| Source | data row index | Tdoc source | Power saving scheme | CD RX cycle (ms) | OD T (ms) | IAT (ms) | Load H/L | #U / cell | floor (Capacity) | % of DL satisfied UE | % of UL satisfied UE | % of DL + UL satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------------------------|---------------------|-----------|----------|----------|-----------|------------------|----------------------|----------------------|---------------------------|-------------------|-------------------------|-------------------------------|------------------------| +| ZTE | 56 | R1-2212596 | Always on | - | - | - | H | 12 | 12 | 96.53% | 100% | 96.53% | 0.00% | 0% | - | | +| ZTE | 23 | R1-2212596 | Aligned CDRX | Aligned every 50 ms | 6 | 4 | H | 12 | 12 | 84% | 100% | 84% | -12.98% | 21.2% | - | | +| ZTE | 24 | R1-2212596 | Additional active time + aligned CDRX | Aligned every 50 ms | 6 | 4 | H | 12 | 12 | 88.19% | 100% | 88.19% | -8.64% | 21.3% | - | Note 1 | + +NOTE 1: additional active time = original DRX On duration + +Based on the evaluation results in Table B.2.7-3, the following observations can be made: + +- For FR1, DL and UL joint evaluation, InH, high load, CG 30Mbps traffic at 60fps and 15ms PDB, it is observed from ZTE that: + - on top of eCDRX, additional active time provides: + - power saving gain of 21.3% for all UEs + - capacity gain of -8.64%. + - eCDRX as the performance reference provides: + - power saving gain of 21.2% for all UEs + - capacity gain of -12.98%. + +**Table B.2.7-4: FR1, DL-only, InH, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------------------------|--------------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| ZTE | 53 | R1-2212596 | Always on | - | - | - | H | 11 | 11 | 90.15% | 0.00% | 0% | - | Note 1 | +| ZTE | 17 | R1-2212596 | Aligned CDRX | Aligned every 50ms | 12 | 4 | H | 11 | 11 | 88.36% | -1.99% | 10.4% | - | Note 1 | +| ZTE | 18 | R1-2212596 | Additional active time + aligned CDRX | Aligned every 50ms | 5 | 4 | H | 11 | 11 | 90% | -0.17% | 30% | - | Note 1,2 | +| vivo | | R1-2208660 | Always On | - | - | - | L | 5 | 10 | 100% | 0% | 0% | - | | +| vivo | | R1-2208660 | R17 PDCCH monitoring adaptation | 16.67 | 8 | 4 | L | 5 | 10 | 100% | 0% | 23.36% | - | Note 3,4 | +| vivo | | R1-2208660 | Additional On-Duration | 16.67 | 4 | 4 | L | 5 | 10 | 100% | 0% | 18.73% | - | Note 5 | +| vivo | | R1-2208660 | Always On | - | - | - | H | 10 | 10 | 92.50% | 0.0% | 0% | - | | +| vivo | | R1-2208660 | R17 PDCCH monitoring adaptation | 16.67 | 8 | 4 | H | 10 | 10 | 92.22% | -0.3% | 19.28% | - | Note 3,4 | +| vivo | | R1-2208660 | Additional On-Duration | 16.67 | 4 | 4 | H | 10 | 10 | 91.49% | -1.1% | 14.68% | - | Note 5 | + +| | | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | Jitter range = [-8,8]ms | +| NOTE 2: | additional active time = original DRX On duration | +| NOTE 3: | PDCCH skipping is indicated in the DCI that schedules a dummy PDSCH after all the HARQ-ACK processes of transmissions have been completed | +| NOTE 4: | applying R17 sparse SSSG with PDCCH monitoring every 2 slots when DRX Onduration starts and switch to dense SSSG with PDCCH monitoring every 1 slot after detecting DCI scheduling XR traffic burst | +| NOTE 5: | additional DRX onduration length is 4ms | + +Based on the evaluation results in Table B.2.7-4, the following observations can be made: + +- For FR1, DL only, InH, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from ZTE that: + - with eCDRX, additional active time provides: + - power saving gain of 30% for all UEs + - capacity gain of -0.17%. + - eCDRX as the performance reference provides power: + - saving gain of 10.4% for all UEs + - capacity gain of -1.99%. +- For FR1, DL only, InH, low load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from vivo that: + - on top of eCDRX, additional active time provides: + - power saving gain of 18.73% for all UEs + - capacity gain of 0% + - eCDRX with R17 PDCCH monitoring adaptation as the performance reference provides: + - power saving gain of 23.36% for all UEs + - capacity gain of 0% +- For FR1, DL only, InH, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from vivo that: + - with eCDRX, additional active time provides: + - power saving gain of 14.68% for all UEs + - capacity gain of -1.1% + - eCDRX with R17 PDCCH monitoring adaptation as the performance reference provides: + - power saving gain of 19.28% for all UEs + - capacity gain of -0.3% + +**Table B.2.7-5: FR1, DL-only, InH, CG30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | O D T (ms) | IAT (ms) | Load H/L | #U E /cel l | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------|-----------------|------------|----------|----------|-------------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| ZTE | 57 | R1-2212596 | Always On | - | - | - | H | 12 | 12 | 96.53 % | 0.00% | 0% | - | | +| ZTE | 25 | R1-2212596 | Aligned CDRX | Aligned every | 6 | 4 | H | 12 | 12 | 84% | -12.98 % | 30.9% | - | | + +| | | | | | | | | | | | | | | | +|----------------------------------------------------------|----|------------|---------------------------------------|--------------------|---|---|---|----|----|---------|----------|---------|---|--------| +| | | | | 50ms | | | | | | | | | | | +| ZTE | 26 | R1-2212596 | Aligned CDRX | Aligned every 50ms | 8 | 6 | H | 12 | 12 | 88.89 % | -7.91% | 20.6% | - | | +| ZTE | 27 | R1-2212596 | Additional active time + aligned CDRX | Aligned every 50ms | 6 | 4 | H | 12 | 12 | 88.19 % | -8.64% | 32.4% | - | Note 1 | +| Nokia | | R1-2209535 | Always On Baseline | - | - | - | H | 6 | 6 | 90.00 % | 0.00% | 0.0% | - | - | +| Nokia | 1 | R1-2209535 | C-DRX with EAT | 16 | 8 | 0 | H | 6 | 6 | 51.38 % | -42.91 % | 30.33 % | - | Note 2 | +| Nokia | 2 | R1-2209535 | C-DRX with EAT | 16 | 6 | 0 | H | 6 | 6 | 49.86 % | -44.60 % | 30.40 % | - | Note 2 | +| Nokia | 3 | R1-2209535 | C-DRX with EAT | 16 | 4 | 0 | H | 6 | 6 | 51.80 % | -42.44 % | 30.43 % | - | Note 2 | +| Nokia | 4 | R1-2209535 | C-DRX with EAT | 16 | 2 | 0 | H | 6 | 6 | 51.80 % | -42.44 % | 30.43 % | - | Note 2 | +| NOTE1: additional active time = original DRX On duration | | | | | | | | | | | | | | | +| NOTE2: Extension timer = 1ms | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.7-5, the following observations can be made: + +- For FR1, DL only, InH, high load, CG 30Mbps traffic at 60fps and 15ms PDB, it is observed from ZTE that: + - on top of eCDRX, additional active time provides: + - power saving gain of 32.4% for all UEs + - capacity gain of -8.64%. + - eCDRX as the performance reference provides: + - mean power saving gain of 25.75% in the range of 20.6% to 30.9% for all UEs + - mean capacity gain of -10.45% in the range of -12.985 to -7.91%. +- For FR1, DL only, InH, high load, CG 30Mbps traffic at 60fps and 15ms PDB, it is observed from Nokia that: + - Extension of active time provides: + - mean power saving gain of 30.40% for all UEs in the range of 30.33% to 30.43% + - mean capacity gain of -43.10% for all UEs in the range of -44.60% to -42.44% + +**Table B.2.7-6: FR1, DL-only, InH, VR45** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | O D T (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------|-----------------|------------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +|--------|----------------|-------------|---------------------|-----------------|------------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| + +| | | | | | | | | | | | | | | | +|-----|----|------------|------------------------------------------------------|--------------------|----|---|---|---|---|---------|----------|--------|---|----------| +| ZTE | 55 | R1-2212596 | Always on | - | - | - | H | 7 | 7 | 90.48 % | 0.00% | 0.00% | - | Note 1 | +| ZTE | 21 | R1-2212596 | Aligned CDRX | Aligned every 50ms | 12 | 5 | H | 7 | 7 | 90% | -0.53% | 8.47% | - | Note 1 | +| ZTE | 22 | R1-2212596 | Additional active time + aligned CDRX | Aligned every 50ms | 6 | 5 | H | 7 | 7 | 88.1% | -2.63% | 20% | - | Note 1,3 | +| ZTE | 39 | R1-2212596 | Always on | - | - | - | H | 7 | 7 | 90% | 0.00% | 0.00% | - | Note 2 | +| ZTE | 41 | R1-2212596 | Aligned CDRX | Aligned every 50ms | 14 | 5 | H | 7 | 7 | 88.10 % | -2.11% | 4.60% | - | Note2 | +| ZTE | 40 | R1-2212596 | Aligned CDRX | Aligned every 50ms | 12 | 5 | H | 7 | 7 | 80% | -11.11 % | 9.46% | - | Note2 | +| ZTE | 42 | R1-2212596 | Additional active time + aligned CDRX | Aligned every 50ms | 2 | 4 | H | 7 | 7 | 89.48 % | -0.58% | 19% | - | Note2 ,3 | +| ZTE | 44 | R1-2212596 | PDCCH Skipping (duration = 2ms,4ms) | Aligned every 50ms | 14 | 5 | H | 7 | 7 | 72.62 % | -19.31 % | 10.84% | - | Note2 | +| ZTE | 43 | R1-2212596 | PDCCH skipping with dummy grant (duration = 4ms,8ms) | Aligned every 50ms | 14 | 5 | H | 7 | 7 | 80.95 % | -10.1% | 13.03% | - | Note2 | + +NOTE 1: Jitter range = [-8,8]ms, STD = 2.9ms + +NOTE 2: Jitter range = [-8,8]ms, STD = 5ms + +NOTE 3: additional active time = original DRX On duration + +Based on the evaluation results in Table B.2.7-6, the following observations can be made: + +- For FR1, DL only, InH, high load, VR 45Mbps traffic at 60fps and 10ms PDB, it is observed from ZTE that: + - on top of eCDRX, additional active time provides mean: + - power saving gain of 19.5% in the range of 19% to 20% for all UEs + - mean capacity gain of -1.61% in the range of -2.63% to -0.58%. + - eCDRX performance reference provides: + - mean power saving gain of 7.51% in the range of 4.60% to 9.46% for all UEs + +- mean capacity gain of -4.58% in the range of -11.11% to -0.53%. +- eCDRX + PDCCH skipping performance reference provides: + - mean power saving gain of 11.94% in the range of 10.84% to 13.03% for all UEs + - mean capacity gain of -14.71% in the range of -19.31% to -10.1%. + +**Table B.2.7-7: FR1, DL-only, DU, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|------------------------------------------------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| OPPO | 1 | R1-2211490 | Always On | - | - | - | H | 5 | 5 | 90.18 % | 0.0% | 0.0% | 0.0% | | +| OPPO | 3 | R1-2211490 | Non-uniform CDRX cycle pattern | {17,17,16} | 10 | 2 | H | 5 | 5 | 88.77 % | -1.6% | 18.72% | 19.43% | | +| OPPO | 4 | R1-2211490 | Non-uniform CDRX cycle pattern with dynamic additional ODT | {17,17,16} | 4 | 2 | H | 5 | 5 | 90.18 % | 0.0% | 30.86% | 32.33% | Note1 | + +NOTE 1: another DRX On Duration time indicated by DCI is 4ms + +Based on the evaluation results in Table B.2.7-7, the following observations can be made: + +- For FR1, DL only, DU, high load, VR 30Mbps traffic at 60fps and 10ms PDB, it is observed from OPPO that: + - on top of eCDRX, additional active time provides: + - power saving gain of 30.86% for all UEs + - capacity gain of 0.0% + - eCDRX as the performance reference provides: + - power saving gain of 18.72% for all UEs + - capacity gain of -1.6% + +**Table B.2.7-8: FR1, DL-only, DU, VR45** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| ZTE | 58 | R1-2212596 | Always on | - | - | - | H | 7 | 7 | 91.16 % | 0.00% | 0% | - | Note 1 | +| ZTE | 34 | R1-2212 | Aligned CDRX | Aligned | 14 | 5 | H | 7 | 7 | 87% | -4.56% | 4.86% | - | Note 1 | + +| | | | | | | | | | | | | | | | +|-----|----|------------|-------------------------------------------------------------------------|--------------------|----|---|---|---|---|---------|----------|--------|---|----------| +| | | 596 | | every 50ms | | | | | | | | | | | +| ZTE | 35 | R1-2212596 | Additional active time + aligned CDRX | Aligned every 50ms | 2 | 5 | H | 7 | 7 | 90.48 % | -0.75% | 20.53% | - | Note 1,2 | +| ZTE | 36 | R1-2212596 | PDCCH skipping (duration = 2ms, 4ms) | Aligned every 50ms | 14 | 5 | H | 7 | 7 | 82% | -10.05 % | 9.2% | - | Note 1 | +| ZTE | 28 | R1-2212596 | Always On | - | - | - | H | 7 | 7 | 91.16 % | 0.00% | 0.0% | - | | +| ZTE | 29 | R1-2212596 | Aligned CDRX | Aligned every 50ms | 8 | 5 | H | 7 | 7 | 89.8% | -1.49% | 23% | - | | +| ZTE | 30 | R1-2212596 | Aligned CDRX | Aligned every 50ms | 10 | 5 | H | 7 | 7 | 90.48 % | -0.75% | 16% | - | | +| ZTE | 31 | R1-2212596 | Additional active time + aligned CDRX | Aligned every 50ms | 2 | 5 | H | 7 | 7 | 91.84 % | 0.75% | 26.24% | - | Note 2 | +| ZTE | 32 | R1-2212596 | Additional active time + aligned CDRX + PDCCH skipping (duration = 2ms) | Aligned every 50ms | 2 | 5 | H | 7 | 7 | 91.16 % | 0.00% | 33.5% | - | | +| ZTE | 33 | R1-2212596 | PDCCH skipping (duration = 2ms, 4ms) | Aligned every 50ms | 10 | 5 | H | 7 | 7 | 84% | -7.9% | 24% | - | Note2 | +| ZTE | 46 | R1-2212596 | Always on | - | - | - | H | 7 | 7 | 90% | 0.00% | 0% | - | Note3 | +| ZTE | 47 | R1-2212596 | Aligned CDRX | Aligned every 50ms | 14 | 5 | H | 7 | 7 | 85% | -5.56% | 4.50% | - | Note3 | +| ZTE | 48 | R1-2212596 | Additional active time + aligned CDRX | Aligned every 50ms | 2 | 4 | H | 7 | 7 | 84% | -6.67% | 18% | - | Note3 | +| ZTE | 49 | R1-2212596 | PDCCH Skipping (duration = 2ms, 4ms) | Aligned every 50ms | 14 | 5 | H | 7 | 7 | 74% | -17.78 % | 9.6% | - | Note3 | +| ZT | 50 | R1- | PDCCH | Aligned | 14 | 5 | H | 7 | 7 | 80% | -11.11 | 12% | - | Note3 | + +| | | | | | | | | | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------------------------------------------|--------------|--|--|--|--|--|--|--|---|--|--|--| +| E | 2212
596 | skipping with dummy grant (duration = 4ms, 8ms) | d every 50ms | | | | | | | | % | | | | +| NOTE 1: Jitter range = [-8,8]ms, STD = 2.9ms
NOTE 2: additional active time = original DRX On duration
NOTE 3: Jitter range = [-8,8]ms, STD = 5ms | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.7-8, the following observations can be made: + +- For FR1, DL only, DU, high load, VR 45Mbps traffic at 60fps and 10ms PDB, it is observed from ZTE that: + - with eCDRX, additional active time provides: + - mean power saving gain of 24.57% in the range of 18% to 33.50% for all UEs + - mean capacity gain of -1.67% in the range of -6.67% to 0.75% + - eCDRX performance reference provides: + - mean power saving gain of 12.09% in the range of 4.50% to 23% for all UEs + - mean capacity gain of -3.09% in the range of -5.56% to -0.75% + - eCDRX + PDCCH skipping performance reference provides: + - mean power saving gain of 13.70% in the range of 9.20% to 24% for all UEs + - mean capacity gain of -11.71% in the range of -17.78% to -7.90% + +### B.2.8 Multiple active CDRX configurations + +This clause captures evaluation results for multiple active CDRX configurations for multiple XR traffic flows. + +- Ericsson and InterDigital evaluated the multiple active CDRX configurations separately for XR video and the other traffics. +- vivo compared multiple active CDRX configurations and a single active CDRX configuration with SPS or a single active CDRX configuration only. + +**Table B.2.8-1: FR1, DL+UL, DU, VR30 at 30fps + DL Audio** + +| source | arrow index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of DL satisfied UE | % of UL satisfied UE | % of DL + UL satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|-------------|-------------|-------------|------------------------|-----------------|----------|----------|----------|----------|------------------|----------------------|----------------------|---------------------------|-------------------|-------------------------|-------------------------------|------------------------| +| Ericsson on | | R1-2210922 | Always On | - | - | - | H | 5 | 5 | - | - | 94.0 % | 0.0% | 0% | 0% | | +| Ericsson on | | R1-2210922 | R15/16 DRX (Long DRX) | 10 | 8 | 4 | H | 5 | 5 | - | - | 90.7 % | -3.5 % | 3.0% | 3.3% | | +| Ericsson on | | R1-2210922 | R15/16 DRX (Short DRX) | 4 | 2 | 4 | H | 5 | 5 | - | - | 85.9 % | -8.6 % | 6.9% | 7.2% | | +| Ericsson on | | R1-2210922 | Matched CDRX | 33.3 | 10 | 4 | H | 5 | 5 | - | - | 0% | -100.0% | 18.4 % | - | Note 2 | + +| | | | | | | | | | | | | | | | | | +|------------------|--|------------|-----------------------------------------------|---------------------------------|-------------------------------|---|---|---|---|---|---|--------|---------|--------|--------|----------| +| Eri
css
on | | R1-2210922 | Multi-flow DRX & Matched CDRX | 33.3 | 10 | 4 | H | 5 | 5 | - | - | 88.4 % | -6.0 % | 13.4 % | 13.6 % | Note1 ,2 | +| Eri
css
on | | R1-2210922 | Multi-flow DRX & two-stage DRX & Matched CDRX | out er DRX: 33.3; inn er DRX: 4 | out er ODT: 10; inn er ODT: 2 | 4 | H | 5 | 5 | - | - | 81.8 % | -13.0 % | 16.9 % | 17.2 % | Note2 ,3 | + +NOTE 1: for the second CDRX, CDRX cycle = 10ms, ODT = 2ms, IAT = 0ms. +NOTE 2: Matched CDRX has (drx\_offset=3, traffic\_time\_offset=1 ms, drx-LongCycle=33 ms) +NOTE 3: for the second CDRX, CDRX cycle = 10ms, ODT = 2ms, IAT = 4ms. + +Based on the evaluation results in Table B.2.8-1, the following observations can be made: + +- For FR1, DL + UL joint evaluation, DU, high load, VR 30Mbps traffic at 30fps with 10ms PDB and DL audio with 10ms PDB, it is observed from Ericsson that: + - eCDRX with a single CDRX configuration provides: + - power saving gain of 18.4% for all UEs + - capacity gain of -100% + - Multiple CDRX configurations + eCDRX provides: + - power saving gain of 13.4% + - capacity gain of -6.0% + - Multiple CDRX configurations + eCDRX + two-stage DRX provides: + - power saving gain of 17.2% + - capacity gain of -13.0% + +**Table B.2.8-2: FR1, DL+UL, DU, VR30 at 45fps + DL Audio** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE / cell | floor (Capacity) | % of DL satisfied UE | % of UL satisfied UE | % of DL + UL satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|------------------|----------------|-------------|--------------------------|-----------------|----------|----------|----------|------------|------------------|----------------------|----------------------|---------------------------|-------------------|-------------------------|-------------------------------|------------------------| +| Eri
css
on | | R1-2210922 | Always On | - | - | - | H | 7 | 7 | - | - | 90.1 % | 0.0% | - | - | | +| Eri
css
on | | R1-2210922 | R15/16 DRX (Long DRX) | 10 | 8 | 4 | H | 7 | 7 | - | - | 86.3 % | -4.2 % | 2.7% | 2.6% | | +| Eri
css
on | | R1-2210922 | R15/16 DRX (Short DRX) | 4 | 2 | 4 | H | 7 | 7 | - | - | 78.7 % | -12.7 % | 6.4% | 6.4% | | +| Eri
css
on | | R1-2210922 | Matched CDRX | 22.2 | 10 | 4 | H | 7 | 7 | - | - | 0% | -100.0% | 12.3 % | - | Note 2 | +| Eri
css
on | | R1-2210922 | Multi-flow DRX & Matched | 22.2 | 10 | 4 | H | 7 | 7 | - | - | 85.9 % | -4.7 % | 10.1 % | 10.0 % | Note1 ,2 | + +| | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------|--|------------|-----------------------------------------------|-------------------------------------|-------------------------------|---|---|---|---|---|---|--------|---------|--------|--------|---------| +| | | | CDRX | | | | | | | | | | | | | | +| Ericsson | | R1-2210922 | Multi-flow DRX & two-stage DRX & Matched CDRX | outer DRX: X: 22.2; inner DRX: X: 4 | outer OD T: 10; inner OD T: 2 | 4 | H | 7 | 7 | - | - | 71.3 % | -20.9 % | 13.1 % | 12.8 % | Note1,2 | +| NOTE 1: for the second CDRX cycle = 10ms, ODT = 2ms, IAT = 0ms. | | | | | | | | | | | | | | | | | +| NOTE 2: Matched CDRX has (drx_offset=9, traffic_time_offset=2 ms, drx-LongCycle=22 ms) | | | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.8-2, the following observations can be made: + +- For FR1, DL + UL joint evaluation, DU, high load, VR 45Mbps traffic at 30fps with 10ms PDB and DL audio with 10ms PDB, it is observed from Ericsson that: + - eCDRX with a single CDRX configuration provides: + - power saving gain of 12.3% for all UEs + - capacity gain of -100% + - Multiple CDRX configurations + eCDRX provides: + - power saving gain of 10.1% + - capacity gain of -4.7% + - Multiple CDRX configurations + eCDRX + two-stage DRX provides: + - power saving gain of 13.1% + - capacity gain of -20.9% + +**Table B.2.8-3: FR1, DL-only, InH, VR30 at 60fps + DL Audio** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------------------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| video | | R1-2211024 | Always On | - | - | - | L | 5 | 10 | 100% | 0% | - | - | | +| video | | R1-2211024 | One active CDRX for video | 16.67 | 8 | 4 | L | 5 | 10 | 100% | 0% | 11.70% | - | | +| video | | R1-2211024 | One active CDRX for video and SPS for audio | 16.67 | 8 | 4 | L | 5 | 10 | 100% | 0% | 9.81% | - | | +| video | | R1-2211024 | Multiple CDRXs | 16.67 | 8 | 4 | L | 5 | 10 | 100% | 0% | 9.72% | - | Note1 | +| video | | R1-2211024 | Multiple CDRXs | 16.67 | 8 | 4 | L | 5 | 10 | 100% | 0% | 9.52% | - | Note2 | + +| | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------|--|------------|---------------------------------------------|-------|---|---|---|----|----|---------|-------|-------|---|-------| +| vivo | | R1-2211024 | Always On | - | - | - | H | 10 | 10 | 92.09 % | 0.0% | - | - | | +| vivo | | R1-2211024 | One active CDRX for video | 16.67 | 8 | 4 | H | 10 | 10 | 91.07 % | -1.1% | 9.23% | - | | +| vivo | | R1-2211024 | One active CDRX for video and SPS for audio | 16.67 | 8 | 4 | H | 10 | 10 | 91.66 % | -0.5% | 8.14% | - | | +| vivo | | R1-2211024 | Multiple CDRXs | 16.67 | 8 | 4 | H | 10 | 10 | 91.02 % | -1.2% | 8.04% | - | Note1 | +| vivo | | R1-2211024 | Multiple CDRXs | 16.67 | 8 | 4 | H | 10 | 10 | 91.46 % | -0.7% | 6.95% | - | Note2 | +| NOTE 1: for the second CDRX, CDRX cycle = 10ms, ODT = 2ms, IAT = 0ms. | | | | | | | | | | | | | | | +| NOTE 2: for the second CDRX, CDRX cycle = 10ms, ODT = 2ms, IAT = 2ms. | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.8-3, the following observations can be made: + +- For FR1, DL-only evaluation, InH, high load, VR 30Mbps traffic at 60fps with 10ms PDB and DL audio, it is observed from vivo that: + - multiple CDRX configurations with eCDRX provides: + - mean power saving gain of 7.50% in the range of 6.95% to 8.04% + - mean capacity gain of -0.95% in the range of -1.2% to -0.7% + - single eCDRX + SPS performance reference provides: + - power saving gain of 8.14% + - capacity gain of -0.5% + - single eCDRX performance reference provides: + - power saving gain of 9.23% + - capacity gain of -1.1% +- For FR1, DL-only evaluation, InH, low load, VR 30Mbps traffic at 60fps with 10ms PDB and DL audio, it is observed from vivo that: + - multiple CDRX configurations with eCDRX provides: + - mean power saving gain of 9.62% in the range of 9.52% to 9.72% + - mean capacity gain of 0% + - single eCDRX + SPS performance reference provides: + - power saving gain of 9.81% + - mean capacity gain of 0% + - single eCDRX performance reference provides: + - power saving gain of 11.70% + +- capacity gain of 0% + +**Table B.2.8-4: FR1, DL-only, InH, VR30 at 30fps + DL Audio** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------------|----------------|-------------|---------------------------------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| InterDigital | 5 | R1-2211842 | Always On | - | - | - | H | 3 | 3 | 91.70 % | 0.0% | 0.0% | - | | +| InterDigital | 6 | R1-2211842 | Single CDRX Config | 10 | 8 | 2 | H | 3 | 3 | 83.30 % | -9.2% | 6.22% | - | | +| InterDigital | 7 | R1-2211842 | Multi-CDRX Config Set 1 | 33 | 10 | 6 | H | 3 | 3 | 72.20 % | -21.3% | 12.82% | - | Note1 | +| InterDigital | 7 | R1-2211842 | Multi-CDRX Config Set 1 | 33 | 10 | 6 | H | 3 | 3 | 72.20 % | -21.3% | 6.97% | - | Note1,6 | +| InterDigital | 8 | R1-2211842 | Multi-CDRX Config Set 2 | 33 | 12 | 4 | H | 3 | 3 | 72.20 % | -21.3% | 18.09% | - | Note2 | +| InterDigital | 8 | R1-2211842 | Multi-CDRX Config Set 2 | 33 | 12 | 4 | H | 3 | 3 | 72.20 % | -21.3% | 12.54% | - | Note2,6 | +| vivo | | R1-2211024 | Always On | - | - | - | L | 3 | 6 | 100% | 0.0% | 0.0% | - | Note5 | +| vivo | | R1-2211024 | One active CDRX for video | 33.33 | 8 | 4 | L | 3 | 6 | 0.00% | -100.0 % | 41.06% | - | Note5 | +| vivo | | R1-2211024 | One active CDRX for video and SPS for audio | 33.33 | 8 | 4 | L | 3 | 6 | 100% | 0.0% | 20.70% | - | Note5 | +| vivo | | R1-2211024 | Multiple CDRXs | 33.33 | 8 | 4 | L | 3 | 6 | 100% | 0.0% | 19.84% | - | Note3,5 | +| vivo | | R1-2211024 | Multiple CDRXs | 33.33 | 8 | 4 | L | 3 | 6 | 100% | 0.0% | 18.81% | - | Note4,5 | +| vivo | | R1-2211024 | Always On | - | - | - | H | 6 | 6 | 94.91 % | 0.0% | 0.0% | - | Note5 | +| vivo | | R1-2211 | One active | 33.33 | 8 | 4 | H | 6 | 6 | 0.00% | -100.0 | 37.32% | - | Note5 | + +| | | | | | | | | | | | | | | | +|------|--|------------|---------------------------------------------|-------|---|---|---|---|---|---------|-------|--------|---|----------| +| | | 024 | CDRX for video | | | | | | | | % | | | | +| vivo | | R1-2211024 | One active CDRX for video and SPS for audio | 33.33 | 8 | 4 | H | 6 | 6 | 94.44 % | -0.5% | 19.02% | - | Note5 | +| vivo | | R1-2211024 | Multiple CDRXs | 33.33 | 8 | 4 | H | 6 | 6 | 93.98 % | -1.0% | 18.34% | - | Note3 ,5 | +| vivo | | R1-2211024 | Multiple CDRXs | 33.33 | 8 | 4 | H | 6 | 6 | 94.44 % | -0.5% | 16.85% | - | Note4 ,5 | + +NOTE 1: for the second CDRX, CDRX cycle = 10ms, ODT = 2ms, IAT = 6ms. +NOTE 2: for the second CDRX, CDRX cycle = 10ms, ODT = 2ms, IAT = 4ms. +NOTE 3: for the second CDRX, CDRX cycle = 10ms, ODT = 2ms, IAT = 0ms. +NOTE 4: for the second CDRX, CDRX cycle = 10ms, ODT = 2ms, IAT = 2ms. +NOTE 5: DL audio has 10ms PDB +NOTE 6: PSG is calculated w.r.t. single CDRX scheme + +Based on the evaluation results in Table B.2.8-4, the following observations can be made: + +- For FR1, DL only evaluation, InH, high load, AR 30Mbps traffic at 30fps with 10ms PDB and DL audio, it is observed from InterDigital that: + - Multiple CDRX configurations provides: + - mean power saving gain of 15.54% in the range of 12.82% to 18.09% + - mean capacity gain of -21.3% + - performance reference a single CDRX configuration provides: + - power saving gain of 6.22% for all UEs + - capacity gain of -9.2% +- For FR1, DL-only evaluation, InH, high load, VR 30Mbps traffic at 30fps with 10ms PDB and DL audio with 10ms PDB, it is observed from vivo that: + - multiple CDRX configurations with eCDRX provides: + - mean power saving gain of 17.60% in the range of 16.85% to 18.34% + - mean capacity gain of -0.75% in the range of -1.0% to -0.5% + - performance reference single eCDRX + SPS provides: + - power saving gain of 19.02% + - capacity gain of -0.5% + - performance reference single eCDRX provides: + - power saving gain of 37.32% + - capacity gain of -100% +- For FR1, DL-only evaluation, InH, low load, VR 30Mbps traffic at 30fps with 10ms PDB and DL audio with 10ms PDB, it is observed from vivo that: + - multiple CDRX configurations with eCDRX provides: + +- mean power saving gain of 19.33% in the range of 18.81% to 19.84% +- capacity gain of 0% +- performance reference single eCDRX + SPS provides: + - power saving gain of 20.70% + - capacity gain of 0% +- performance reference single eCDRX provides: + - power saving gain of 41.06% + - capacity gain of -100% + +**Table B.2.8-5: FR1, DL-only, CG, VR30 at 30fps + DL Audio** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------------|----------------|-------------|-------------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| InterDigital | 1 | R1-2211842 | Always On | - | - | - | H | 3 | 3 | 100% | 0.0% | 0.0% | - | | +| InterDigital | 2 | R1-2211842 | Single CDRX Config | 10 | 8 | 2 | H | 3 | 3 | 100% | 0.0% | 7.647% | - | | +| InterDigital | 3 | R1-2211842 | Multi-CDRX Config Set 1 | 33 | 10 | 6 | H | 3 | 3 | 94.40% | -5.6% | 12.082% | - | Note1 | +| InterDigital | 3 | R1-2211842 | Multi-CDRX Config Set 1 | 33 | 10 | 6 | H | 3 | 3 | 94.40% | -5.6% | 4.73% | - | Note1,3 | +| InterDigital | 4 | R1-2211842 | Multi-CDRX Config Set 2 | 33 | 12 | 4 | H | 3 | 3 | 91.70% | -8.3% | 17.16% | - | Note2 | +| InterDigital | 4 | R1-2211842 | Multi-CDRX Config Set 2 | 33 | 12 | 4 | H | 3 | 3 | 91.70% | -8.3% | 10.23% | - | Note2,3 | + +NOTE 1: for the second CDRX, CDRX cycle = 10ms, ODT = 2ms, IAT = 6ms. +NOTE 2: for the second CDRX, CDRX cycle = 10ms, ODT = 2ms, IAT = 4ms. +NOTE 3: PSG is calculated w.r.t. single CDRX scheme + +Based on the evaluation results in Table B.2.8-5, the following observations can be made: + +- For FR1, DL only evaluation, InH, high load, CG 30Mbps traffic at 30fps with 15ms PDB and DL audio, it is observed from InterDigital that: + - single CDRX configuration provides: + - power saving gain of 7.647% for all UEs + - capacity gain of 0% + +- Multiple CDRX configurations provides: + - mean power saving gain of 14.62% in the range of 12.08% to 17.16% + - mean capacity gain of -6.95% in the range of -8.3% to -5.6% + +### B.2.9 Dynamic grant enhancement with XR-specific pre-scheduling + +This clause captures evaluation results for dynamic grant enhancement with XR-specific pre-scheduling: + +- CATT evaluated the pre-configured XR-specific PDCCH monitoring cycle and monitoring window disassociated with C-DRX which is aligned with the periodic XR packet generation cycle. UE is allowed to monitor PDCCH for XR-specific PDCCH monitoring cycle at both DRX ON and OFF. CATT also evaluated multicarrier solutions with one carrier for XR service and the second carrier for eMBB service. + +**Table B.2.9-1: FR1, DL-only, InH, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------------------------------------------------------------------------------------------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| CATT | 1 | R1-2211174 | Baseline: DG scheduling and UE always-on | - | - | - | H | 12 | 12 | 95.8% | 0.0% | 0.0% | - | | +| CATT | 2 | R1-2211174 | DG scheduling with C-DRX | 16 | 12 | 4 | H | 12 | 12 | 90.0% | -6.1% | 8.0% | - | | +| CATT | 3 | R1-2211174 | Semi-static C-DRX enhancement | 17/17/16 | 8 | 4 | H | 12 | 12 | 0.0% | -100.0% | 25.5% | - | | +| CATT | 3 | R1-2211174 | Semi-static C-DRX enhancement | 17/17/16 | 8 | 4 | H | 12 | 12 | 0.0% | -100.0% | 19.0% | - | Note1 | +| CATT | 9 | R1-2211174 | Dynamic grant enhancement with XR-specific pre-scheduling scheme 1: Pre-scheduling DG window (16, 12) | 16 | 12 | 0 | H | 12 | 12 | 90.0% | -6.1% | 11.7% | - | | +| CATT | 9 | R1-2211174 | Dynamic grant enhancement with XR-specific pre-scheduling scheme 1: Pre-scheduling DG window (16, 12) | 16 | 12 | 0 | H | 12 | 12 | 90.0% | -0.0% | 3.8% | - | Note1 | +| CATT | 10 | R1-2211174 | Dynamic grant enhancement with XR-specific pre-scheduling scheme 2: Dynamic grant enhancement with XR-specific pre- | 16 | 12 | 0 | H | 12 | 12 | 89.7% | -7.0% | 22.4% | - | | + +| | | | | | | | | | | | | | | | +|-----------------------------------------------------------|----|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----|---|---|----|----|-------|-------|-------|---|-------| +| | | | scheduling with non-scheduling PDCCH skipping indication | | | | | | | | | | | | +| CA TT | 10 | R1-2211 174 | Dynamic grant enhancement with XR-specific pre-scheduling scheme 2: Dynamic grant enhancement with XR-specific pre-scheduling with non-scheduling PDCCH skipping indication | 16 | 12 | 0 | H | 12 | 12 | 89.7% | -0.9% | 15.7% | - | Note1 | +| CA TT | 11 | R1-2211 174 | Dynamic grant enhancement with XR-specific pre-scheduling scheme 3: Pre-scheduling DG window (16, 12) with go-to-sleep | 16 | 12 | 0 | H | 12 | 12 | 90.0% | -6.1% | 24.0% | - | | +| CA TT | 11 | R1-2211 174 | Dynamic grant enhancement with XR-specific pre-scheduling scheme 3: Pre-scheduling DG window (16, 12) with go-to-sleep | 16 | 12 | 0 | H | 12 | 12 | 90.0% | -0.0% | 17.4% | - | Note1 | +| CA TT | 12 | R1-2211 174 | Dynamic grant enhancement with XR-specific pre-scheduling scheme 4: Pre-scheduling DG window (16, 12) with PDCCH skipping and go-to-sleep | 16 | 12 | 0 | H | 12 | 12 | 89.7% | -7.0% | 29.4% | - | | +| CA TT | 12 | R1-2211 174 | Dynamic grant enhancement with XR-specific pre-scheduling scheme 4: Pre-scheduling DG window (16, 12) with PDCCH skipping and go-to-sleep | 16 | 12 | 0 | H | 12 | 12 | 89.7% | -0.9% | 23.3% | - | Note1 | +| NOTE 1: PSG is calculated w.r.t. DG scheduling with C-DRX | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.9-1, the following observations can be made: + +- For FR1, DL only evaluation, InH, high load, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from CATT that: + - dynamic grant enhancement with XR-specific pre-scheduling scheme could obtain: + - mean power saving gain of 21.88% in the range of 11.7% to 29.40% + - mean capacity gain of -6.55% in the range of -7.00% to -6.10% + - semi-static C-DRX enhancement scheme with (17/17/16, 8, 4) as the performance reference obtains: + - mean power saving gain of 22.50% in the range of 19.00% to 25.50% + - mean capacity gain of -100% + - DG scheduling with C-DRX as the performance reference obtains: + - mean power saving gain of 15.05% in the range of 3.8% to 23.3% + - mean capacity gain of -0.45% + +**Table B.2.9-2: FR1, DL-only, multi-carrier, InH, VR30 + IM** + +| source | data row index | Tdo c source | Power saving scheme | CDRX cycle (ms) | O D T (ms) | IAT (ms) | Load H/L | #U E /cel l | floor (Capacity ) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Additional Assumptions | +|--------|----------------|--------------------|---------------------------------------------------------------------------------------------------------------|-----------------|------------|----------|----------|-------------|-------------------|-------------------|-------------------|-------------------------|------------------------| +| CATT | 1 | R1-221
117
4 | Baseline: DG scheduling and UE always-on | - | - | - | H | 12 | 12 | 95.8% | 0.00% | 0.0% | | +| CATT | 3 | R1-221
117
4 | Enhanced C-DRX | 16/17/17 | 8 | 4 | H | 12 | 12 | 0.0% | -100.00 % | 19.0% | Note1,3 | +| | 27 | R1-221
117
4 | Enhanced C-DRX | 16/17/17 | 8 | 4 | H | 12 | 12 | - | - | 27.4% | Note2,3 | +| CATT | 12 | R1-221
117
4 | Dynamic grant enhancement with XR-specific pre-scheduling window (16, 12) with PDCCH skipping and go-to-sleep | - | - | - | H | 12 | 12 | 89.2% | -0.45% | 23.3% | Note1,3 | +| | 26 | R1-221
117
4 | C-DRX for IM | 320 | 10 | 80 | H | 12 | 12 | - | - | 87.2% | Note2,3 | + +NOTE 1: first carrier for XR service +NOTE 2: second carrier for eMBB service +NOTE 3: baseline is DG scheduling with C-DRX(16, 12, 4) and Rel-17 PDCCH skipping scheme + +Based on the evaluation results in Table B.2.9-2, the following observations can be made: + +- For FR1, DL only evaluation, InH, high load, multi-carrier, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from CATT that: + - Dynamic grant enhancement with XR-specific pre-scheduling scheme for XR traffic carrier and IM traffic carrier provides: + - mean power saving gain of 23.3% for the XR traffic carrier + +- mean power saving gain of 87.2% for the IM traffic carrier +- mean capacity gain of -0.45% for the XR traffic carrier +- enhanced C-DRX (16/17/17, 8, 4) as performance reference provides: + - mean power saving gain of 19.0% for the XR traffic carrier + - mean power saving gain of 27.4% for the IM traffic carrier + - mean capacity gain of -100% for the XR traffic carrier + +When XR and IM traffic transmitted in different carriers, the semi-static C-DRX enhancement scheme with (16/17/17, 8, 4) degrade 59.8% PSG of carrier with IM traffic compared with that of dynamic grant enhancement with XR-specific pre-scheduling scheme. + +### B.2.10 SPS+DG with UE power saving scheme + +This clause captures evaluation results for the UE power saving scheme of SPS enhancement with dynamic grant (DG): + +- CATT evaluated the periodic SPS occasion which provides wake-up timing for XR UE during DRX OFF and subsequent dynamic grant window for the transmission of XR packets. When XR packet arrives after the SPS occasion, gNB could indicate UE to perform PDCCH skipping until XR packet arrival and to transform to sleep state after XR packet transmission finishes. + +**Table B.2.10-1: FR1, DL-only, InH, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|------------------------------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| CATT | 1 | R1-2211174 | Baseline: DG scheduling and UE always-on | - | - | - | H | 12 | 12 | 95.8% | 0.0% | 0.0% | 0.0% | | +| CATT | 2 | R1-2211174 | DG scheduling with C-DRX | 16 | 12 | 4 | H | 12 | 12 | 90.0% | -6.1% | 8.0% | 8.0% | | +| CATT | 21 | R1-2211174 | SPS enhancement | - | - | - | H | 12 | 12 | 90.0% | -6.1% | 12.5% | 12.6% | | +| CATT | 21 | R1-2211174 | SPS enhancement | - | - | - | H | 12 | 12 | 90.0% | -0.0% | 9.8% | 9.9% | Note1 | +| CATT | 22 | R1-2211174 | Multiple SPS configurations | - | - | - | H | 12 | 12 | 0.0% | -100.0% | 47.4% | - | | +| CATT | 22 | R1-2211174 | Multiple SPS configurations | - | - | - | H | 12 | 12 | 0.0% | -100.0% | 46.1% | - | Note1 | +| CATT | 23 | R1-2211174 | SPS enhancement with go-to-sleep | - | - | - | H | 12 | 12 | 88.33% | -7.8% | 39.8% | 39.9% | | +| CATT | 23 | R1-2211174 | SPS enhancement with go-to-sleep | - | - | - | H | 12 | 12 | 88.33% | -1.9% | 38.0% | 38.1% | Note1 | + +NOTE 1: PSG is calculated w.r.t. DG scheduling with C-DRX + +Based on the evaluation results in Table B.2.10-1, the following observations can be made: + +- For FR1, DL only evaluation, InH, high load, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from CATT that: + - SPS +DG with power saving schemes provides: + - mean power saving gain of 25.03% in the range of 9.80% to 39.8% + - mean capacity gain of -3.9% in the range of -0.0% to -7.8% + - DG scheduling with C-DRX(16, 12, 4) as the performance reference provides: + - mean power saving gain of 8.0% + - mean capacity gain of -6.1% + - multiple SPS configurations as the performance reference provides: + - mean power saving gain of 46.75% in the range of 46.10% to 47.40% + - mean capacity gain of -100% + +### B.2.11 PDCCH skipping and interaction with HARQ retransmission + +This clause captures evaluation results for PDCCH skipping and interaction with HARQ retransmission: + +- Ericsson, vivo, MediaTek and ZTE evaluated the scheme that UE can resume PDCCH monitoring during the time when DRX retransmission timer is running if NACK is transmitted after PDCCH skipping has started. + +**Table B.2.11-1: FR1, DL+UL, DU, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CD RX cycle (ms) | OD T (ms) | IAT (ms) | Load H/L | #UE / cell | floor (Capacity) | % of DL satisfied UE | % of UL satisfied UE | % of DL + UL satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|----------|----------------|-------------|-------------------------------|------------------|-----------|----------|----------|------------|------------------|----------------------|----------------------|---------------------------|-------------------|-------------------------|-------------------------------|------------------------| +| Ericsson | 35 | R1-2210922 | Always On | - | - | - | H | 8 | 8 | | | 90.1% | 0.0% | 0.0% | 0.0% | Note 1 | +| Ericsson | 36 | R1-2210922 | R15/16 DRX (Long DRX) | 10 | 8 | 4 | H | 8 | 8 | | | 86.9% | -3.6% | 2.6% | 2.7% | Note 1 | +| Ericsson | 37 | R1-2210922 | R15/16 DRX (Short DRX) | 4 | 2 | 4 | H | 8 | 8 | | | 80.2% | -11.0% | 6.1% | 6.1% | Note 1 | +| Ericsson | 38 | R1-2210922 | Matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | | | 85.5% | -5.1% | 7.2% | 7.1% | Note 1,2 | +| Ericsson | 39 | R1-2210922 | Matched CDRX | 17/17/16 | 10 | 4 | H | 8 | 8 | | | 86.4% | -4.1% | 7.6% | 7.5% | Note 1 | +| Ericsson | 40 | R1-2210922 | PDCCH skipping & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | | | 84.7% | -6.0% | 7.6% | 7.6% | Note 1,2 | +| MTK | 18 | R1-2212253 | AlwaysOn - baseline | - | - | - | H | 8 | 8 | | | 92.14% | 0.0% | 0.0% | | | +| MTK | 19 | R1-2212253 | R17 PDCC H skipping | - | - | - | H | 8 | 8 | | | 62% | -32.7% | 3.96% | | Note3 | + +| | | | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------|----|------------|---------------------|---|---|---|---|---|---|--|--|--------|-------|--------|--|-------| +| MT K | 20 | R1-2212253 | R17 PDCCH skipping | - | - | - | H | 8 | 8 | | | 85.62% | -7.1% | 6.39% | | Note4 | +| MT K | 21 | R1-2212253 | Enh: PDCCH skipping | - | - | - | H | 8 | 8 | | | 89.05% | -3.4% | 17.66% | | Note5 | +| NOTE 1: the DL traffic has a second flow for audio with 30ms PDB | | | | | | | | | | | | | | | | | +| NOTE 2: Matched CDRX has (drx_offset=3, traffic_time_offset=2 ms, drx-LongCycle=16 ms) | | | | | | | | | | | | | | | | | +| NOTE 3: PDCCH skipping duration is 3ms | | | | | | | | | | | | | | | | | +| NOTE 4: PDCCH skipping duration is 2ms | | | | | | | | | | | | | | | | | +| NOTE 5: PDCCH skipping duration is 12ms, UE resumes PDCCH monitoring if UE transmits NACK | | | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.11-1, the following observations can be made: + +- For FR1, DL + UL joint evaluation, DU, high load, VR 30Mbps traffic at 60fps with 10ms PDB and DL audio, it is observed from Ericsson that: + - eCDRX as performance reference provides: + - mean power saving gain of 7.4% in the range of 7.2% to 7.6% for all UEs + - mean capacity gain of -4.60% in the range of -5.1% to -4.1% + - PDCCH skipping enhancement with eCDRX provides: + - power saving gain of 7.6% for all UEs + - capacity gain of -6.0% +- For FR1, DL + UL joint evaluation, DU, high load, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from MediaTek that: + - R17 PDCCH skipping performance reference provides: + - mean power saving gain of 5.18% in the range of 3.96% to 6.39% for all UEs + - mean capacity gain of -19.90% in the range of -32.7% to -7.1% + - enhanced PDCCH skipping provides: + - power saving gain of 17.66% + - capacity gain of -3.4% + +**Table B.2.11-2: FR1, DL-only, DU, CG30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| MT K | 1 | R1-2209517 | Always On | - | - | - | H | 12 | 12 | 92.54% | 0.0% | 0% | | | +| MT K | 2 | R1-2209517 | Rel-17 PDCCH skipping 5ms | - | - | - | H | 12 | 12 | 62.94% | -32.0% | 14.11% | | Note 1 | +| MT K | 3 | R1-2209517 | Rel-17 PDCCH skipping | - | - | - | H | 12 | 12 | 83.10% | -10.2% | 11.13% | | Note 2 | +| MT K | 4 | R1-2209517 | Rel-17 PDCCH skipping | - | - | - | H | 12 | 12 | 87.78% | -5.1% | 8.64% | | Note 3 | +| MT | 5 | R1- | PDCCH | - | - | - | H | 12 | 12 | 84.37 | -8.8% | 29.60% | | Note | + +| | | | | | | | | | | | | | | | +|------|---|----------------|----------------------------|---|---|---|---|----|----|---------|-------|--------|--|-----------| +| K | | 2209
517 | skipping enhancement | | | | | | | % | | | | 4 | +| MT K | 5 | R1-2209
517 | PDCCH skipping enhancement | - | - | - | H | 12 | 12 | 84.37 % | -8.8% | 20.78% | | Note 4, 5 | + +NOTE 1: PDCCH skipping duration is 5ms +NOTE 2: PDCCH skipping duration is 4ms +NOTE 3: PDCCH skipping duration is 3ms +NOTE 4: PDCCH skipping duration is 12ms, UE resumes PDCCH monitoring if UE transmits NACK +NOTE 5: PSG is calculated w.r.t. Rel-17 PDCCH skipping with duration equal to 3ms + +Based on the evaluation results in Table B.2.11-2, the following observations can be made: + +- For FR1, DL + UL joint evaluation, DU, high load, CG 30Mbps traffic at 60fps with 15ms PDB, it is observed from MediaTek that: + - Rel-17 PDCCH skipping performance reference provides: + - mean power saving gain of 11.29% in the range of 8.64% to 14.11% for all UEs + - mean capacity gain of -15.77% in the range of -32.0% to -5.1% + - enhanced PDCCH skipping provides: + - mean power saving gain of 25.19% in the range of 20.78% to 29.60% for all UEs + - capacity gain of -8.8% + +**Table B.2.11-3: FR1, DL-only, DU, VR30** + +| source | arrow index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|-----------|-------------|----------------|----------------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| MT K | 6 | R1-2209
517 | Always On | - | - | - | H | 8 | 8 | 97.02 % | 0.0% | 0% | - | | +| MT K | 7 | R1-2209
517 | Rel-17 PDCCH skipping 5ms | - | - | - | H | 8 | 8 | 72.38 % | -25.4% | 8.62% | - | Note 1 | +| MT K | 8 | R1-2209
517 | Rel-17 PDCCH skipping | - | - | - | H | 8 | 8 | 93.10 % | -4.0% | 5.27% | - | Note 2 | +| MT K | 9 | R1-2209
517 | PDCCH skipping enhancement | - | - | - | H | 8 | 8 | 96.08 % | -1.0% | 31.77% | - | Note 3 | +| MT K | 9 | R1-2209
517 | PDCCH skipping enhancement | - | - | - | H | 8 | 8 | 96.08 % | -1.0% | 27.97% | - | Note 3, 4 | +| MT K | 14 | R1-2209
517 | CDRX baseline | 16 | 10 | 5 | H | 8 | 8 | 33.10 % | -65.9% | 0.0% | - | | +| MT K | 15 | R1-2209
517 | Rel-17 PDCCH skipping | 16 | 10 | 5 | H | 8 | 8 | 16.50 % | -83.0% | 6.04% | - | Note 1 | +| MT K | 16 | R1-2209
517 | Rel-17 PDCCH skipping | 16 | 10 | 5 | H | 8 | 8 | 3.30% | -96.6% | 9.41% | - | Note 2 | +| MT K | 17 | R1-2209
517 | PDCCH skipping enhancement | 16 | 10 | 5 | H | 8 | 8 | 21.70 % | -77.6% | 23.27% | - | Note 3 | +| Eri csson | 1 | R1-2210
922 | Always On | - | - | - | H | 8 | 8 | 91.7% | 0.0% | 0% | 0% | | +| Eri | 2 | R1- | R15/16 | 10 | 8 | 4 | H | 8 | 8 | 86.9% | -5.2% | 4.3% | 4.9% | | + +| | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------|---|-------------|-------------------------------|----------|----|---|---|---|---|-------|--------|-------|-------|--------| +| css on | | 2210 922 | DRX (Long DRX) | | | | | | | | | | | | +| Eri css on | 3 | R1-2210 922 | R15/16 DRX (Short DRX) | 4 | 2 | 4 | H | 8 | 8 | 78.2% | -14.7% | 10.4% | 11.0% | | +| Eri css on | 4 | R1-2210 922 | Matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | 87.2% | -4.9% | 10.5% | 11.4% | Note 5 | +| Eri css on | 5 | R1-2210 922 | Matched CDRX | 17/17/16 | 10 | 4 | H | 8 | 8 | 87.0% | -5.1% | 10.1% | 10.5% | | +| Eri css on | 6 | R1-2210 922 | PDCCH skipping & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | 87.3% | -4.8% | 15.8% | 16.0% | Note 5 | +| Eri css on | 1 | R1-2210 922 | Always On | - | - | - | L | 2 | 8 | 100% | 0.0% | 0% | 0% | | +| Eri css on | 2 | R1-2210 922 | R15/16 DRX (Long DRX) | 10 | 8 | 4 | L | 2 | 8 | 100% | 0.0% | 4.8% | 4.8% | | +| Eri css on | 3 | R1-2210 922 | R15/16 DRX (Short DRX) | 4 | 2 | 4 | L | 2 | 8 | 100% | 0.0% | 12.4% | 12.4% | | +| Eri css on | 4 | R1-2210 922 | Matched CDRX | 16.6 | 10 | 4 | L | 2 | 8 | 100% | 0.0% | 12.8% | 12.8% | Note 5 | +| Eri css on | 5 | R1-2210 922 | Matched CDRX | 17/17/16 | 10 | 4 | L | 2 | 8 | 100% | 0.0% | 12.5% | 12.5% | | +| Eri css on | 6 | R1-2210 922 | PDCCH skipping & matched CDRX | 16.6 | 10 | 4 | L | 2 | 8 | 100% | 0.0% | 22.5% | 22.5% | Note 5 | +| NOTE 1: PDCCH skipping duration is 3ms | | | | | | | | | | | | | | | +| NOTE 2: PDCCH skipping duration is 2ms | | | | | | | | | | | | | | | +| NOTE 3: PDCCH skipping duration is 12ms, UE resumes PDCCH monitoring if UE transmits NACK | | | | | | | | | | | | | | | +| NOTE 4: PSG is calculated w.r.t. Rel-17 PDCCH skipping with duration equal to 2ms | | | | | | | | | | | | | | | +| NOTE 5: Matched CDRX has (drx_offset=3, traffic_time_offset=2 ms, drx-LongCycle=16 ms) | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.11-3, the following observations can be made: + +- For FR1, DL only evaluation, DU, high load, DRX not configured, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from MediaTek that: + - R17 PDCCH skipping as performance reference provides: + - mean power saving gain of 6.95% in the range of 5.27% to 8.62% for all UEs + - mean capacity gain of -14.70% in the range of -25.4% to -4.0% + - enhanced PDCCH skipping provides: + - mean power saving gain of 29.87% in the range of 27.97% to 31.77% for all UEs + - capacity gain of -1.0% +- For FR1, DL only evaluation, DU, high load, DRX configured, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from MediaTek that: + - R17 PDCCH skipping as performance reference provides: + - mean power saving gain of 7.73% in the range of 6.04% to 9.41% for all UEs + - mean capacity gain of -89.80% in the range of -96.6% to -83.0% + +- enhanced PDCCH skipping provides: + - power saving gain of 23.27% + - capacity gain of -77.6% +- For FR1, DL only evaluation, DU, high load, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from Ericsson that: + - eCDRX as performance reference provides: + - mean power saving gain of 10.3% in the range of 10.1% to 10.5% for all UEs + - mean capacity gain of -5.0% in the range of -5.1% to -4.9% + - PDCCH skipping enhancement with eCDRX provides: + - power saving gain of 15.8% for all UEs + - capacity gain of -4.8% +- For FR1, DL only evaluation, DU, low load, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from Ericsson that: + - eCDRX as performance reference provides: + - mean power saving gain of 12.65% in the range of 12.5% to 12.8% for all UEs + - capacity gain of 0% + - PDCCH skipping enhancement with eCDRX provides: + - power saving gain of 22.5% for all UEs + - capacity gain of 0% + +**Table B.2.11-4: FR1, DL-only, DU, VR45** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|------------------------------------------------------|--------------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| ZTE | 46 | R1-2211905 | Always on | - | - | - | H | 7 | 7 | 90% | 0.00% | 0% | - | Note1 | +| ZTE | 47 | R1-2211905 | Aligned CDRX | Aligned every 50ms | 14 | 5 | H | 7 | 7 | 85% | -5.56% | 4.50% | - | Note1 | +| ZTE | 49 | R1-2211905 | PDCCH Skipping (duration = 2ms,4ms) | Aligned every 50ms | 14 | 5 | H | 7 | 7 | 74% | -17.78% | 9.6% | - | Note1 | +| ZTE | 50 | R1-2211905 | PDCCH skipping with dummy grant (duration = 4ms,8ms) | Aligned every 50ms | 14 | 5 | H | 7 | 7 | 80% | -11.11% | 12% | - | Note1 | +| ZTE | 51 | R1-2211 | PDCCH Skipping | Aligned | 14 | 5 | H | 7 | 7 | 84% | -6.67% | 16% | - | Note1 | + +| | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------|----|-------------|-------------------------------------------|------------|---|---|---|---|---|---------|--------|--------|---|---------| +| | | 905 | with retransmission (duration = 3ms, 7ms) | every 50ms | | | | | | | | | | | +| MT K | 10 | R1-2209 517 | Always On | - | - | - | H | 4 | 4 | 95.71 % | 0.0% | 0% | - | | +| MT K | 11 | R1-2209 517 | Rel-17 PDCCH skipping | - | - | - | H | 4 | 4 | 67.38 % | -29.6% | 7.97% | - | Note2 | +| MT K | 12 | R1-2209 517 | Rel-17 PDCCH skipping | - | - | - | H | 4 | 4 | 89.52 % | -6.5% | 4.90% | - | Note3 | +| MT K | 13 | R1-2209 517 | PDCCH skipping enhancement | - | - | - | H | 4 | 4 | 93.10 % | -2.7% | 29.31% | - | Note4 | +| MT K | 13 | R1-2209 517 | PDCCH skipping enhancement | - | - | - | H | 4 | 4 | 93.10 % | -2.7% | 25.68% | - | Note4,5 | +| NOTE 1: Jitter range = [-8,8]ms, STD = 5ms | | | | | | | | | | | | | | | +| NOTE 2: PDCCH skipping duration is 3ms | | | | | | | | | | | | | | | +| NOTE 3: PDCCH skipping duration is 2ms | | | | | | | | | | | | | | | +| NOTE 4: PDCCH skipping duration is 12ms, UE resumes PDCCH monitoring 5ms if UE transmits NACK | | | | | | | | | | | | | | | +| NOTE 5: PSG is calculated w.r.t. Rel-17 PDCCH skipping with duration equal to 2ms | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.11-4, the following observations can be made: + +- For FR1, DL only evaluation, DU, high load, VR 45Mbps traffic at 60fps with 10ms PDB, it is observed from ZTE that: + - R17 PDCCH skipping + eCDRX as performance reference provides: + - mean power saving gain of 10.80% in the range of 9.6% to 12% for all UEs + - mean capacity gain of -14.45% in the range of -17.78% to -11.11% + - PDCCH skipping with retransmission enhancement + eCDRX provides: + - power saving gain of 16% for all UEs with + - capacity gain of -6.67% +- For FR1, DL only evaluation, DU, high load, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from MediaTek: + - R17 PDCCH skipping as performance reference provides: + - mean power saving gain of 6.44% in the range of 4.90% to 7.97% for all UEs + - mean capacity gain of -18.05% in the range of -29.6% to -6.5% + - enhanced PDCCH skipping without DRX provides: + - mean power saving gain of 27.50% in the range of 25.68% to 29.31% for all UEs + - capacity gain of -2.70% + +**Table B.2.11-5: FR1, DL-only, InH, VR45** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +|--------|----------------|-------------|---------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| + +| | | | | | | | | | | | | | | | +|--------------------------------------------|----|------------|---------------------------------------------------------|--------------------|----|---|---|---|---|--------|---------|--------|---|-------| +| ZTE | 39 | R1-2211905 | Always on | - | - | - | H | 7 | 7 | 90% | 0.00% | 0.00% | - | Note1 | +| ZTE | 41 | R1-2211905 | Aligned CDRX | Aligned every 50ms | 14 | 5 | H | 7 | 7 | 88.10% | -2.11% | 4.60% | - | Note1 | +| ZTE | 40 | R1-2211905 | Aligned CDRX | Aligned every 50ms | 12 | 5 | H | 7 | 7 | 80% | -11.11% | 9.46% | - | Note1 | +| ZTE | 44 | R1-2211905 | PDCCH Skipping (duration = 2ms,4ms) | Aligned every 50ms | 14 | 5 | H | 7 | 7 | 72.62% | -19.31% | 10.84% | - | Note1 | +| ZTE | 43 | R1-2211905 | PDCCH skipping with dummy grant (duration = 4ms,8ms) | Aligned every 50ms | 14 | 5 | H | 7 | 7 | 80.95% | -10.06% | 13.03% | - | Note1 | +| ZTE | 45 | R1-2211905 | PDCCH Skipping with retransmission (duration = 3ms,7ms) | Aligned every 50ms | 14 | 5 | H | 7 | 7 | 84.52% | -6.1% | 16.31% | - | Note1 | +| NOTE 1: Jitter range = [-8,8]ms, STD = 5ms | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.11-5, the following observations can be made: + +- For FR1, DL only evaluation, InH, high load, VR 45Mbps traffic at 60fps with 10ms PDB, it is observed from ZTE that: + - R17 PDCCH skipping + eCDRX performance reference provides: + - mean power saving gain of 11.94% in the range of 10.84% to 13.03% for all UEs + - mean capacity gain of -14.69% in the range of -19.31% to -10.06%. + - PDCCH skipping with retransmission enhancement + eCDRX provides: + - power saving gain of 16.31% for all UEs + - capacity gain of -6.1%. + +**Table B.2.11-6: FR1, DL-only, InH, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycles (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------|------------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| vivo | | R1-2211024 | Always On | - | - | - | L | 5 | 10 | 100% | 0.0% | 0.0% | - | Note1 | + +| | | | | | | | | | | | | | | | +|------|--|------------|-----------------------------------------------------------------|-------|----|---|---|----|----|--------|---------|--------|---|-----------------| +| vivo | | R1-2211024 | Always On | - | - | - | L | 5 | 10 | 100% | 0.0% | 0.0% | - | Note2 | +| vivo | | R1-2211024 | R17 PDCCH monitoring adaptation | 16.67 | 8 | 4 | L | 5 | 10 | 100% | 0.0% | 23.36% | - | Note1, 4,5, 9 | +| vivo | | R1-2211024 | R17 PDCCH monitoring adaptation | 16.67 | 16 | 4 | L | 5 | 10 | 100% | 0.0% | 15.79% | - | Note2, 4,5, 9 | +| vivo | | R1-2211024 | Enhanced PDCCH skipping with HARQ interaction | 16.67 | 8 | 4 | L | 5 | 10 | 100% | 0.0% | 37.13% | - | Note1, 3,5, 9 | +| vivo | | R1-2211024 | Enhanced PDCCH skipping with HARQ interaction | 16.67 | 16 | 4 | L | 5 | 10 | 100% | 0.0% | 27.77% | - | Note2, 3,5, 9 | +| vivo | | R1-2211024 | LP-WUS scheme and enhanced PDCCH skipping with HARQ interaction | 16.67 | 8 | 4 | L | 5 | 10 | 100% | 0.0% | 43.84% | - | Note1, 3,8, 9 | +| vivo | | R1-2211024 | LP-WUS scheme and enhanced PDCCH skipping with HARQ interaction | 16.67 | 16 | 4 | L | 5 | 10 | 100% | 0.0% | 41.90% | - | Note2, 3,8, 9 | +| vivo | | R1-2211024 | Always On | - | - | - | H | 10 | 10 | 92.50% | 0.0% | - | - | Note1 | +| vivo | | R1-2211024 | R17 PDCCH monitoring adaptation | 16.67 | 8 | 4 | H | 10 | 10 | 1.11% | -98.80% | 35.21% | - | Note1, 3,5, 9 | +| vivo | | R1-2211024 | R17 PDCCH monitoring adaptation | 16.67 | 8 | 4 | H | 10 | 10 | 92.22% | -0.30% | 19.28% | - | Note1, 4,5, 9 | +| vivo | | R1-2211024 | Enhanced PDCCH skipping with HARQ interaction | 16.67 | 8 | 4 | H | 10 | 10 | 92.22% | -0.30% | 32.18% | - | Note1, 3,5, 9 | +| vivo | | R1-2211024 | LP-WUS scheme and enhanced PDCCH skipping with HARQ interaction | 16.67 | 8 | 4 | H | 10 | 10 | 92.22% | -0.30% | 38.47% | - | Note1, 3,8, 9 | +| vivo | | R1-2211024 | Always On | - | - | - | H | 10 | 10 | 97.45% | 0.0% | - | - | Note1, 7 | +| vivo | | R1-2211024 | R17 PDCCH monitoring adaptation | 16.67 | 8 | 4 | H | 10 | 10 | 2.22% | -97.72% | 35.21% | - | Note1, 3,5,7, 9 | +| vivo | | R1-2211024 | R17 PDCCH monitoring adaptation | 16.67 | 8 | 4 | H | 10 | 10 | 97.45% | 0% | 19.28% | - | Note1, 4,5,7, 9 | +| vivo | | R1-2211024 | Enhanced PDCCH skipping with HARQ | 16.67 | 8 | 4 | H | 10 | 10 | 97.45% | 0% | 32.18% | - | Note1, 3,5,7, 9 | + +| | | | | | | | | | | | | | | | +|------|--|------------|--------------------------------------------------------------------------------------|-----------|----|---|---|----|----|---------|----------|--------|---|---------------------| +| vivo | | R1-2211024 | interaction
Always On | - | - | - | H | 10 | 10 | 93.12 % | 0.0% | - | - | Note1 ,6 | +| vivo | | R1-2211024 | R17
PDCCH
monitoring
adaptation | 16.6
7 | 8 | 4 | H | 10 | 10 | 2.08% | -97.77 % | 32.77% | - | Note1 ,3,5,6, 9 | +| vivo | | R1-2211024 | R17
PDCCH
monitoring
adaptation | 16.6
7 | 8 | 4 | H | 10 | 10 | 92.78 % | -0.37% | 19.48% | - | Note1 ,4,5,6, 9 | +| vivo | | R1-2211024 | Enhanced
PDCCH
skipping
with HARQ
interaction | 16.6
7 | 8 | 4 | H | 10 | 10 | 92.78 % | -0.37% | 32.49% | - | Note1 ; 3,5,6, 9 | +| vivo | | R1-2211024 | Always On | - | - | - | H | 10 | 10 | 97.45 % | 0.0% | - | - | Note1 ,6,7 | +| vivo | | R1-2211024 | R17
PDCCH
monitoring
adaptation | 16.6
7 | 8 | 4 | H | 10 | 10 | 94.91 % | -2.61% | 32.77% | - | Note1 ,3,5,6, 7, 9 | +| vivo | | R1-2211024 | R17
PDCCH
monitoring
adaptation | 16.6
7 | 8 | 4 | H | 10 | 10 | 97.45 % | 0% | 19.48% | - | Note1 ,4,5,6, 7, 9 | +| vivo | | R1-2211024 | Enhanced
PDCCH
skipping
with HARQ
interaction | 16.6
7 | 8 | 4 | H | 10 | 10 | 97.45 % | 0% | 32.49% | - | Note1 ; 3,5,6, 7, 9 | +| vivo | | R1-2211024 | Always On | - | - | - | H | 10 | 10 | 91.83 % | 0.0% | - | - | Note2 | +| vivo | | R1-2211024 | R17
PDCCH
monitoring
adaptation | 16.6
7 | 16 | 4 | H | 10 | 10 | 91.05 % | -0.90% | 12.26% | - | Note2 ,4,5, 9 | +| vivo | | R1-2211024 | Enhanced
PDCCH
skipping
with HARQ
interaction | 16.6
7 | 16 | 4 | H | 10 | 10 | 91.20 % | -0.69% | 23.67% | - | Note2 , 3,5, 9 | +| vivo | | R1-2211024 | LP-WUS
scheme
and
enhanced
PDCCH
skipping
with HARQ
interaction | 16.6
7 | 16 | 4 | H | 10 | 10 | 91.20 % | -0.69% | 37.20% | - | Note2 , 3,8, 9 | + +NOTE 1: jitter range = [-4, +4]ms, STD = 2ms +NOTE 2: jitter range = [-8, +8]ms, STD = 5ms +NOTE 3: the network indicates PDCCH skipping in the DCI that schedules the initial PDSCH transmission of the last DL packet of an XR traffic burst +NOTE 4: PDCCH skipping is indicated in the DCI that schedules a dummy PDSCH after all the HARQ-ACK processes of transmissions have been completed +NOTE 5: applying R17 sparse SSSG with PDCCH monitoring every 2 slots when DRX Onduration starts and switch to dense SSSG with PDCCH monitoring every 1 slot after detecting DCI scheduling XR traffic burst +NOTE 6: initial BLER is reduced from 10% to 1% +NOTE 7: satisfaction metric as 95% packet successful rate +NOTE 8: the total relative power (including the power of both LP-WUR and main radio) for LP-WUS monitoring is 45 with no wake-up latency. The resource overhead for LP WUS is not considered. +NOTE 9: PDCCH skipping durations include 10 ms, 16 ms + +Based on the evaluation results in Table B.2.11-6, the following observations can be made: + +- For FR1, DL only evaluation, InH, low load, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from vivo that: + - R17 PDCCH skipping + eCDRX performance reference provides: + +- mean power saving gain of 19.58% in the range of 15.79% to 23.36% for all UEs +- capacity gain of 0% +- Enhanced PDCCH skipping + eCDRX provides: + - mean power saving gain of 32.45% in the range of 27.77% to 37.13% for all UEs + - capacity gain of 0% +- When LP-WUS is adopted, enhanced PDCCH skipping + eCDRX + LP-WUS provides: + - mean power saving gain of 42.87% in the range of 41.90% to 43.84% for all UEs + - capacity gain of 0% +- For FR1, DL only evaluation, InH, high load, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from vivo that: + - R17 PDCCH skipping + eCDRX performance reference provides: + - mean power saving gain of 25.08% in the range of 12.26% to 35.21% for all UEs + - mean capacity gain of -33.16% in the range of -98.80% to 0.0%. + - Enhanced PDCCH skipping + eCDRX provides: + - mean power saving gain of 30.60% in the range of 23.67% to 32.49% for all UEs + - mean capacity gain of -0.05% in the range of -0.37% to 0.0%. + - When LP-WUS is adopted, enhanced PDCCH skipping + eCDRX provides: + - mean power saving gain of 37.84% in the range of 37.20% to 38.47% for all UEs + - mean capacity gain of -0.50% in the range of -0.69% to -0.30%. + +### B.2.12 Enhancements to PDCCH skipping indication + +This clause captures evaluation results for various enhancements for the PDCCH skipping indications: + +- Huawei and vivo evaluated the adaptive PDCCH skipping duration until the earliest possible arrival time of the next frame, i.e., the next jitter boundary position. +- Xiaomi evaluated PDCCH skipping with four skipping durations. +- CATT evaluated PDCCH skipping by introducing the go-to-sleep indication for UE transition to the sleep state immediately. +- Ericsson compared two cases by evaluations when CDRX is configured with: i) Rel-17 PDCCH skipping with two durations only; ii) or enhanced PDCCH skipping with arbitrary skipping duration covering the remaining DRX active time. + +**Table B.2.12-1: FR1, DL+UL, DU, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of DL satisfied UE | % of UL satisfied UE | % of DL + UL satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|----------|----------------|-------------|---------------------|-----------------|----------|----------|----------|----------|------------------|----------------------|----------------------|---------------------------|-------------------|-------------------------|-------------------------------|------------------------| +| Ericsson | 1 | R1-2208401 | Always On | - | - | - | H | 8 | 8 | - | - | 90.1% | 0.0% | 0.0% | 0.0% | Note1 | +| Ericsson | 7 | R1-2208 | R17 PDCC | 16.6 | 10 | 4 | H | 8 | 8 | | | 72.2% | -19.9% | 10.5% | 10.4% | Note1,2,4 | + +| | | | | | | | | | | | | | | | | | +|----------|----|------------|-----------------------------------------|------|----|---|---|---|---|---|---|--------|---------|--------|--------|-----------| +| | | 401 | H skipping & matched CDRX | | | | | | | | | | | | | | +| Ericsson | 8 | R1-2208401 | Enhanced PDCC H skipping & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | | | 72.4 % | -19.6 % | 10.5 % | 10.5 % | Note1,3,4 | +| Ericsson | | R1-2208401 | Always On | - | - | - | L | 2 | 8 | - | - | 99.5 % | 0.0% | 0.0% | 0.0% | Note1 | +| Ericsson | 15 | R1-2208401 | R17 PDCC H skipping & matched CDRX | 16.6 | 10 | 4 | L | 2 | 8 | | | 96.6 % | -2.9 % | 11.2 % | 11.9 % | Note1,2,4 | +| Ericsson | 16 | R1-2208401 | Enhanced PDCC H skipping & matched CDRX | 16.6 | 10 | 4 | L | 2 | 8 | | | 97.3 % | -2.2 % | 11.2 % | 12.0 % | Note1,3,4 | + +NOTE 1: the DL traffic has a second flow for audio with 30ms PDB +NOTE 2: two possible PDCCH skipping periods 5 & 10ms +NOTE 3: UE skips the remaining DRX active time +NOTE 4: Matched CDRX has (drx\_offset=3, traffic\_time\_offset=2 ms, drx-LongCycle=16 ms) + +Based on the evaluation results in Table B.2.12-1, the following observations can be made: + +- For FR1, DL + UL joint evaluation, DU, DRX configured, VR 30Mbps traffic at 60fps with 10ms PDB and DL audio, it is observed from Ericsson that: + - Rel-17 PDCCH skipping with two durations as performance reference provides: + - For high load, power saving gain of 10.4% and capacity gain of -19.9% + - For low load, power saving gain of 11.2% and capacity gain of -2.9% + - enhanced PDCCH skipping with arbitrary skipping duration covering the remaining DRX active time provides: + - For high load, power saving gain of 10.5% and capacity gain of -19.6% + - For low load, power saving gain of 11.2% and capacity gain of -2.2% + +**Table B.2.12-2: FR1, DL-only, DU, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|-----------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| Huawei | 1 | R1-2210906 | Always On | - | - | - | H | 11 | 11 | 93.42 % | 0.0% | 0.0% | - | | +| Huawei | 10 | R1-2210906 | Rel-17 PDCCH Skipping | - | - | - | H | 11 | 11 | 93.42 % | 0.0% | 12.12% | - | Note 1 | + +| | | | | | | | | | | | | | | | +|------------------------------------------------------------------------------------------|----|------------|---------------------------------------|---|---|---|---|----|----|---------|------|--------|---|--------| +| Huawei | 11 | R1-2210906 | Rel-17 PDCCH Skipping | - | - | - | H | 11 | 11 | 93.42 % | 0.0% | 11.15% | - | Note 2 | +| Huawei | 12 | R1-2210906 | PDCCH skipping with adaptive duration | - | - | - | H | 11 | 11 | 93.42 % | 0.0% | 18.35% | - | Note 3 | +| NOTE 1: Set of PDCCH skipping duration is {5, 10, 15}ms | | | | | | | | | | | | | | | +| NOTE 2: Set of PDCCH skipping duration is {4, 16, 29}ms | | | | | | | | | | | | | | | +| NOTE 3: UE skips PDCCH monitoring until the earliest possible arrival time of next frame | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.12-2, the following observations can be made: + +- For FR1, DL-only evaluation, DU, DRX not configured, high load, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from Huawei that: + - PDCCH skipping with adaptive duration provides: + - power saving gain of 18.35% + - capacity gain of 0.00% + - R17 PDCCH skipping performance reference provides: + - mean power saving gain of 11.64% in the range of 11.15% to 12.12% and + - capacity gain of 0.00% + +**Table B.2.12-3: FR1, DL-only, DU, VR45** + +| source | arrow index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|----------------------------------------------------------------|-------------|-------------|----------------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| Xiaomi | 1 | R1-2211341 | AlwaysOn | - | - | - | H | 3 | 3 | 97% | 0.0% | - | 0.0% | | +| Xiaomi | 2 | R1-2211341 | Rel-17 PDCCH skipping | - | - | - | H | 3 | 3 | 95% | -2.1% | - | 41.74% | Note 1 | +| Xiaomi | 3 | R1-2211341 | PDCCH skipping enhancement | - | - | - | H | 3 | 3 | 96% | -1.0% | - | 47.40% | Note 2 | +| NOTE 1: PDCCH skipping with 2 candidate durations(8/10ms) | | | | | | | | | | | | | | | +| NOTE 2: PDCCH skipping with 4 candidate durations(6/8/10/12ms) | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.12-3, the following observations can be made: + +- For FR1, DL-only evaluation, DU, DRX not configured, high load, VR 45Mbps traffic at 60fps with 10ms PDB, it is observed from Xiaomi that: + - Rel-17 PDCCH skipping with 2 candidate durations as performance reference provides: + - power saving gain of 41.74% + - capacity gain of -2.1% + - PDCCH skipping enhancement with 4 candidate durations provides: + - power saving gain of 47.40% for all UEs + - capacity gain of -1.0% + +**Table B.2.12-4: FR1, DL-only, InH, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | O D T (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|------------------------------------------|-----------------|------------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| CATT | 1 | R1-2211174 | Baseline: DG scheduling and UE always-on | - | - | - | H | 12 | 12 | 95.8% | 0.0% | 0.0% | 0.0% | | +| CATT | 2 | R1-2211174 | DG scheduling with C-DRX | 16 | 12 | 4 | H | 12 | 12 | 90.0% | -6.1% | 8.0% | 8.0% | | +| CATT | 7 | R1-2211174 | PDCCH skipping enhancement (Go-to-sleep) | 16 | 12 | 4 | H | 12 | 12 | 90.00% | -6.1% | 24.0% | 24.4% | | +| CATT | 7 | R1-2211174 | PDCCH skipping enhancement (Go-to-sleep) | 16 | 12 | 4 | H | 12 | 12 | 90.00% | -6.1% | 17.4% | 17.8% | Note1 | +| vivo | | R1-2211024 | Always On | - | - | - | L | 5 | 10 | 100% | 0.0% | 0.0% | - | | +| vivo | | R1-2211024 | R17 PDCCH monitoring adaptation | - | - | - | L | 5 | 10 | 100% | 0.0% | 6.93% | - | Note2,4 | +| vivo | | R1-2211024 | R17 PDCCH monitoring adaptation | - | - | - | L | 5 | 10 | 100% | 0.0% | 18.18% | - | Note2,3,4 | +| vivo | | R1-2211024 | Enhanced PDCCH skipping | - | - | - | L | 5 | 10 | 100% | 0.0% | 12.06% | - | Note2,5 | +| vivo | | R1-2211024 | Enhanced PDCCH skipping | - | - | - | L | 5 | 10 | 100% | 0.0% | 23.36% | - | Note2,3,5 | +| vivo | | R1-2211024 | Always On | - | - | - | H | 10 | 10 | 92.50% | 0.0% | 0.0% | - | | +| vivo | | R1-2211024 | R17 PDCCH monitoring adaptation | - | - | - | H | 10 | 10 | 92.28% | -0.2% | 5.66% | - | Note2,4 | +| vivo | | R1-2211024 | R17 PDCCH monitoring adaptation | - | - | - | H | 10 | 10 | 92.22% | -0.3% | 14.25% | - | Note2,3,4 | +| vivo | | R1-2211024 | Enhanced PDCCH skipping | - | - | - | H | 10 | 10 | 92.30% | -0.2% | 10.46% | - | Note2,5 | +| vivo | | R1-2211024 | Enhanced PDCCH skipping | - | - | - | H | 10 | 10 | 92.22% | -0.3% | 19.28% | - | Note2,3,5 | + +NOTE 1: PSG is calculated w.r.t. DG scheduling with C-DRX + +NOTE 2: PDCCH skipping is indicated in the DCI that schedules a dummy PDSCH after all the HARQ-ACK processes of transmissions have been completed + +NOTE 3: applying R17 sparse SSSG with PDCCH monitoring every 2 slots before XR traffic burst arrives and switch to dense SSSG with PDCCH monitoring every 1 slot after detecting DCI scheduling XR traffic burst + +NOTE 4: with [6ms, 4ms, 2ms] candidate skipping durations + +NOTE 5: one-shot skipping to the next jitter boundary position + +Based on the evaluation results in Table B.2.12-4, the following observations can be made: + +- For FR1, DL-only evaluation, InH, high load, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from CATT that: + - go-to-sleep based on PDCCH skipping enhancement provides: + - power saving gain of 24.0% for all UEs + - capacity gain of -6.1% + - DG scheduling with C-DRX which provides: + - power saving gain of 8.0% + - capacity gain of -6.1% +- For FR1, DL-only evaluation, InH, low load, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from vivo that: + - enhanced PDCCH skipping provides: + - mean power saving gain of 17.71% in the range of 12.06% to 23.36% + - mean capacity gain of 0.00% + - R17 PDCCH monitoring provides: + - mean power saving gain of 12.56% in the range of 6.93% to 18.18% + - mean capacity gain of 0.00% +- For FR1, DL-only evaluation, InH, high load, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from vivo that: + - enhanced PDCCH skipping provides: + - mean power saving gain of 14.87% in the range of 10.46% to 19.28% + - mean capacity gain of -0.25% in the range of -0.3% to -0.2% + - R17 PDCCH monitoring provides: + - mean power saving gain of 9.96% in the range of 5.66% to 14.25% + - mean capacity gain of -0.25% in the range of -0.3% to -0.2% + +### B.2.13 Non-scheduling DCI based PDCCH skipping and continuous PDCCH skipping + +This clause captures evaluation results for non-scheduling DCI based PDCCH skipping and UE continuous PDCCH skipping: + +- CATT evaluated non-scheduling DCI based PDCCH skipping indication to reduce unnecessary PDCCH monitoring when no XR data is scheduled for transmission. On top of this, gNB configures a short PDCCH skipping duration and UE continuously skips the PMOs until the DCI is successfully decoded at the time of packet arrival. + +**Table B.2.13-1: FR1, DL-only, InH, VR30** + +| Source | data row index | Tdoc source | Power saving scheme | CD RX cycle (ms) | OD T (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------|------------------|-----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +|--------|----------------|-------------|---------------------|------------------|-----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| + +| | | | | | | | | | | | | | | | +|--------------------------------------------------------------------------------------------|---|------------|----------------------------------------------------------------------------------------------------------------------------------|----|----|---|---|----|----|--------|--------|-------|-------|-------| +| CA TT | 1 | R1-2211174 | Baseline: DG scheduling and UE always-on | - | - | - | H | 12 | 12 | 95.8% | 0.0% | 0.0% | 0.0% | | +| CA TT | 2 | R1-2211174 | DG scheduling with C-DRX | 16 | 12 | 4 | H | 12 | 12 | 90.0% | -6.1% | 8.0% | 8.0% | Note1 | +| CA TT | 6 | R1-2211174 | PDCCH skipping enhancement (non-scheduling and scheduling DCI with persistent skipping indication) | 16 | 12 | 4 | H | 12 | 12 | 89.70% | -6.4% | 22.4% | 22.4% | Note1 | +| CA TT | 6 | R1-2211174 | PDCCH skipping enhancement (non-scheduling and scheduling DCI with persistent skipping indication) | 16 | 12 | 4 | H | 12 | 12 | 89.70% | -0.33% | 15.7% | 15.7% | Note2 | +| CA TT | 7 | R1-2211174 | PDCCH skipping enhancement (Go-to-sleep) | 16 | 12 | 4 | H | 12 | 12 | 90.00% | -6.1% | 24.0% | 24.4% | Note1 | +| CA TT | 7 | R1-2211174 | PDCCH skipping enhancement (Go-to-sleep) | 16 | 12 | 4 | H | 12 | 12 | 90.00% | 0% | 17.4% | 17.8% | Note2 | +| CA TT | 8 | R1-2211174 | PDCCH skipping enhancement (non-scheduling and scheduling DCI with continuous PDCCH skipping and dynamic go-to-sleep indication) | 16 | 12 | 4 | H | 12 | 12 | 89.70% | -6.4% | 29.4% | 29.9% | Note1 | +| CA TT | 8 | R1-2211174 | PDCCH skipping enhancement (non-scheduling and scheduling DCI with continuous PDCCH skipping and dynamic go-to-sleep indication) | 16 | 12 | 4 | H | 12 | 12 | 89.70% | -0.33% | 23.3% | 23.8% | Note2 | +| NOTE 1: power saving gain and capacity gain are calculated w.r.t. Always-On | | | | | | | | | | | | | | | +| NOTE 2: power saving gain and capacity gain are calculated w.r.t. DG scheduling with C-DRX | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.13-1, the following observations can be made: + +- For FR1, DL-only evaluation, InH, high load, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from CATT that the: + - non-scheduling DCI based PDCCH skipping with persistent skipping indication provides: + - mean power saving gain of 22.4% w.r.t. Always-On + - mean capacity gain of -6.4% w.r.t. Always-On + - mean power saving gain of 15.7% w.r.t. DG scheduling with C-DRX(16, 12, 4) + - mean capacity gain of -0.33% w.r.t. DG scheduling with C-DRX(16, 12, 4) + - go-to-sleep indication scheme with C-DRX(16, 12, 4) provides: + - mean power saving gain of 24.0% to 24.4% w.r.t. Always-On + - mean capacity gain of -6.1% w.r.t. Always-On + - mean power saving gain of 17.4% to 17.8% w.r.t. DG scheduling with C-DRX(16, 12, 4) + - mean capacity gain of 0% w.r.t. DG scheduling with C-DRX(16, 12, 4) + - non-scheduling and scheduling DCI with continuous PDCCH skipping and dynamic go-to-sleep indication provides: + +- mean power saving gain of 29.4% to 29.9% w.r.t. Always-On +- mean capacity gain of -6.4% w.r.t. Always-On +- mean power saving gain of 23.3% to 23.8% w.r.t. DG scheduling with C-DRX(16, 12, 4) +- mean capacity gain of -0.33% w.r.t. DG scheduling with C-DRX(16, 12, 4) +- DG scheduling with C-DRX(16, 12, 4) as the performance reference provides: + - mean power saving gain of 8% w.r.t. Always-On + - mean capacity gain of -6.1% w.r.t. Always-On + +### B.2.14 SSSG switching enhancements + +This clause captures evaluation results for enhancements to SSSG switching: + +- Ericsson evaluated enhanced SSSG switching based on (a) an implicit SSSG with sparse PDCCH monitoring applies at the start of drx-OnDuration and another SSSG with dense PDCCH monitoring in every time slot applies when a PDCCH for data traffic is received, (b) align the search space set monitoring pattern w.r.t. the DRX cycle. + +**Table B.2.14-1: FR1, DL+UL, DU, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of DL satisfied UE | % of UL satisfied UE | % of DL + UL satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|----------|----------------|-------------|--------------------------------------------------------------------------------------|-----------------|----------|----------|----------|----------|------------------|----------------------|----------------------|---------------------------|-------------------|-------------------------|-------------------------------|------------------------| +| Ericsson | 35 | R1-2210922 | Always On | - | - | - | H | 8 | 8 | - | - | 90.1% | 0.0% | 0.0% | 0.0% | Note 1 | +| Ericsson | 41 | R1-2210922 | R17 SSSG switching (sparse SSSG: 2 ms on / 2 ms off) & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | - | - | 66.0% | -26.7% | 10.3% | 10.3% | Note 1,2 | +| Ericsson | 42 | R1-2210922 | R17 SSSG switching (sparse SSSG: 1 ms on / 1 ms off) & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | - | - | 79.8% | -11.4% | 10.7% | 10.7% | Note 1,2 | +| Ericsson | 43 | R1-2210922 | R17 SSSG switching (sparse SSSG: 1 ms on / 1 ms off) & PDCCH skipping & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | - | - | 79.9% | -11.3% | 11.3% | 11.2% | Note 1,2 | +| Ericsson | 48 | R1-2210922 | Enhanced SSSG switching (sparse SSSG: 2 ms on / 2 ms off) & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | - | - | 80.0% | -11.2% | 9.7% | 9.7% | Note 1,2 | + +| | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------|----|------------|-------------------------------------------------------------------------------------------|------|----|---|---|---|---|---|---|--------|---------|--------|--------|----------| +| Eri
css
on | 49 | R1-2210922 | Enhanced SSSG switching (sparse SSSG: 1 ms on / 1 ms off) & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | - | - | 79.5 % | -11.8 % | 11.5 % | 11.5 % | Note 1,2 | +| Eri
css
on | 50 | R1-2210922 | Enhanced SSSG switching (sparse SSSG: 1 ms on / 1 ms off) & PDCCH skipping & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | - | - | 78.7 % | -12.7 % | 12.2 % | 12.1 % | Note 1,2 | +| NOTE 1: the DL traffic has a second flow for audio with 30ms PDB | | | | | | | | | | | | | | | | | +| NOTE 2: Matched CDRX has (drx_offset=3, traffic_time_offset=2 ms, drx-LongCycle=16 ms) | | | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.14-1, the following observations can be made: + +- For FR1, DL + UL joint evaluation, DU, VR 30Mbps traffic at 60fps with 10ms PDB and DL audio, it is observed from Ericsson that: + - R17 SSSG switching performance reference provides: + - mean power saving gain of 10.50% in the range of 10.3% to 10.7% + - mean capacity gain of -19.05% in the range of -26.7% to -11.4% + - enhanced SSSG switching provides: + - mean power saving gain of 10.60% in the range of 9.7% to 11.5% for all UEs + - mean capacity gain of -11.5% in the range of -11.8% to -11.2% +- R17 SSSG switching + PDCCH skipping performance reference provides: + - power saving gain of 11.3% + - capacity gain of -11.3% +- enhanced SSSG switching + PDCCH skipping provides: + - mean power saving gain of 12.2% + - capacity gain of -12.7% + +**Table B.2.14-2: FR1, DL-only, DU, VR30** + +| Source | data row index | Tdoc source | Power saving scheme | CD RX cycle (ms) | OD T (ms) | IA T (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|----------|----------------|-------------|---------------------------------------------------------------------|------------------|-----------|-----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| Ericsson | 1 | R1-2210922 | Always On | - | - | - | H | 8 | 8 | 91.7% | 0.0% | 0.0% | 0.0% | | +| Ericsson | 7 | R1-2210922 | R17 SSSG switching (sparse SSSG: 2 ms on / 2 ms off) & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | 53.9% | -41.2 % | 15.5% | 16.0% | Note 1 | +| Ericsson | 8 | R1-2210 | R17 SSSG switching | 16. | 10 | 4 | H | 8 | 8 | 78.4% | -14.5 % | 16.4% | 16.5% | Note 1 | + +| | | | | | | | | | | | | | | | +|----------|----|------------|-------------------------------------------------------------------------------------------|------|----|---|---|---|---|-------|--------|-------|-------|--------| +| n | | 922 | (sparse SSSG: 1 ms on / 1 ms off) & matched CDRX | 6 | | | | | | | | | | | +| Ericsson | 9 | R1-2210922 | R17 SSSG switching (sparse SSSG: 1 ms on / 1 ms off) & PDCCH skipping & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | 78.9% | -14.0% | 20.2% | 20.4% | Note 1 | +| Ericsson | 14 | R1-2210922 | Enhanced SSSG switching (sparse SSSG: 2 ms on / 2 ms off) & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | 77.8% | -15.2% | 15.2% | 15.5% | Note 1 | +| Ericsson | 15 | R1-2210922 | Enhanced SSSG switching (sparse SSSG: 1 ms on / 1 ms off) & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | 77.8% | -15.2% | 17.1% | 17.2% | Note 1 | +| Ericsson | 16 | R1-2210922 | Enhanced SSSG switching (sparse SSSG: 2 ms on / 2 ms off) & PDCCH skipping & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | 78.7% | -14.2% | 18.0% | 18.2% | Note 1 | +| Ericsson | 17 | R1-2210922 | Enhanced SSSG switching (sparse SSSG: 1 ms on / 1 ms off) & PDCCH skipping & matched CDRX | 16.6 | 10 | 4 | H | 8 | 8 | 78.1% | -14.8% | 20.7% | 20.9% | Note 1 | +| Ericsson | 18 | R1-2210922 | Always On | - | - | - | L | 2 | 8 | 100% | 0.0% | 0% | 0% | | +| Ericsson | 24 | R1-2210922 | R17 SSSG switching (sparse SSSG: 2 ms on / 2 ms off) & matched CDRX | 16.6 | 10 | 4 | L | 2 | 8 | 82.9% | -17.1% | 18.2% | 18.2% | Note 1 | +| Ericsson | 25 | R1-2210922 | R17 SSSG switching (sparse SSSG: 1 ms on / 1 ms off) & matched CDRX | 16.6 | 10 | 4 | L | 2 | 8 | 100% | 0.0% | 19.2% | 19.2% | Note 1 | +| Ericsson | 23 | R1-2210922 | R17 SSSG switching (sparse SSSG: 1 ms on / 1 ms off) & PDCCH skipping & matched CDRX | 16.6 | 10 | 4 | L | 2 | 8 | 100% | 0.0% | 26.6% | 26.6% | Note 1 | +| Ericsson | 31 | R1-2210922 | Enhanced SSSG switching (sparse SSSG: 2 ms on / 2 ms off) & matched CDRX | 16.6 | 10 | 4 | L | 2 | 8 | 100% | 0.0% | 17.3% | 17.3% | Note 1 | +| Ericsson | 32 | R1-2210 | Enhanced SSSG | 16.6 | 10 | 4 | L | 2 | 8 | 100% | 0.0% | 19.3% | 19.3% | Note 1 | + +| | | | | | | | | | | | | | | | +|----------|----|------------|-----------------------------------------------------------------------------------------|------|----|---|---|---|---|------|------|-------|-------|--------| +| n | | 922 | switching (sparse SSG: 1 ms on / 1 ms off) & matched CDRX | | | | | | | | | | | | +| Ericsson | 33 | R1-2210922 | Enhanced SSG switching (sparse SSG: 2 ms on / 2 ms off) & PDCCH skipping & matched CDRX | 16.6 | 10 | 4 | L | 2 | 8 | 100% | 0.0% | 23.5% | 23.5% | Note 1 | +| Ericsson | 34 | R1-2210922 | Enhanced SSG switching (sparse SSG: 1 ms on / 1 ms off) & PDCCH skipping & matched CDRX | 16.6 | 10 | 4 | L | 2 | 8 | 100% | 0.0% | 27.1% | 27.1% | Note 1 | + +NOTE 1: Matched CDRX has (drx\_offset=3, traffic\_time\_offset=2 ms, drx-LongCycle=16 ms) + +Based on the evaluation results in Table B.2.14-2, the following observations can be made: + +- For FR1, DL only evaluation, DU, high load, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from Ericsson that: + - enhanced SSG switching provides: + - mean power saving gain of 16.15% in the range of 15.2% to 17.1% for all UEs + - capacity gain of -15.2% + - R17 SSG switching performance reference provides: + - mean power saving gain of 15.95% in the range of 15.5% to 16.4% + - mean capacity gain of -27.85% in the range of -41.2% to -14.5% + - enhanced SSG switching + PDCCH skipping provides: + - mean power saving gain of 19.35% in the range of 18.0% to 20.7% + - mean capacity gain of -14.5% in the range of -14.8% to -14.2% + - R17 SSG switching + PDCCH skipping performance reference provides: + - power saving gain of 20.2% + - capacity gain of -14.0% +- For FR1, DL only evaluation, DU, low load, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from Ericsson that: + - enhanced SSG switching provides: + - mean power saving gain of 18.30% in the range of 17.3% to 19.3% for all UEs + - capacity gain of 0% + - R17 SSG switching performance reference provides: + - mean power saving gain of 18.7% in the range of 18.2% to 19.2% + - mean capacity gain of -8.6% in the range of -17.1% to 0% + - enhanced SSG switching + PDCCH skipping provides: + +- mean power saving gain of 25.30% in the range of 23.50% to 27.10% +- capacity gain of 0% +- R17 SSSG switching + PDCCH skipping performance reference provides: + - power saving gain of 26.6% + - capacity gain of 0% + +### B.2.15 DCP indicated SSSG switching + +- Nokia evaluated using DCI 2\_6 outside the CDRX active time to trigger SSSG switching for PDCCH monitoring adaptation. + +Table B.2.15-1: 2 FR1, DL-only, InH, CG30 + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE / cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|----------------------------------------|-----------------|----------|----------|----------|------------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| Nokia | | R1-2209535 | Always On Baseline | - | - | - | H | 6 | 6 | 90.00 % | 0.00% | - | - | - | +| Nokia | 1 | R1-2209535 | C-DRX + SSSG switching without DCI 2_6 | 16 | 8 | 8 | H | 6 | 6 | 6.25 % | -93.06 % | 38.27 % | - | Note 1 | +| Nokia | 2 | R1-2209535 | C-DRX + SSSG switching with DCI 2_6 | 16 | 8 | 8 | H | 6 | 6 | 13.47 % | -85.03 % | 34.11 % | - | Note 1 | +| Nokia | 3 | R1-2209535 | C-DRX + SSSG switching without DCI 2_6 | 16 | 8 | 8 | H | 6 | 6 | 0.00 % | -100.00 % | 47.60 % | - | Note 2 | +| Nokia | 4 | R1-2209535 | C-DRX + SSSG switching with DCI 2_6 | 16 | 8 | 8 | H | 6 | 6 | 0.90 % | -99.00 % | 35.97 % | - | Note 2 | + +NOTE 1: SSSG0 ks = 2, SSSG1 ks = 1, searchSpaceSwitchTimer = 8 ms +NOTE 2: SSSG0 ks = 4, SSSG1 ks = 1, searchSpaceSwitchTimer = 8 ms + +Based on the evaluation results in Table B.2.15-1, the following observations can be made: + +- For FR1, DL only evaluation, InH, high load, CG 30Mbps traffic at 60fps with 15ms PDB, it is observed from Nokia that: + - DCP indicated SSSG switching provides: + - mean power saving gain of 35.04% in the range of 34.11% to 35.97% + - mean capacity gain of -92.02% in the range of -99.00% to -85.03% + - R17 SSSG switching performance reference provides: + - mean power saving gain of 42.94% in the range of 38.27% to 47.60% + - mean capacity gain of -96.53% in the range of -93.06% to -100.00% + +### B.2.16 Retransmission-less CG for UL pose transmission + +This clause captures evaluation results for retransmission-less CG for UL pose transmission: + +- Qualcomm evaluated disabling the retransmission for CG for UL pose information so that UE does not monitor related UL retransmission scheduling DCI. Conservative MCS is configured for successful transmission of the UL pose by the first transmission. + +**Table B.2.16-1: FR1, DL+UL, DU, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|---------------------------------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|-------------------------------|------------------------| +| QC | 1 | R1-2212134 | Always On | - | - | - | H | 10 | 10 | 94.603% | 0.0% | 0% | | | +| QC | 2 | R1-2212134 | Aligned CDRX + CG with UL retransmission | 16/17/17 | 4 | 4 | H | 10 | 10 | 92.698% | -2.0% | 1.8% | | Note 1 | +| QC | 3 | R1-2212134 | Aligned CDRX + CG without UL retransmission | 16/17/17 | 4 | 4 | H | 10 | 10 | 92.619% | -2.1% | 20.0% | | | + +NOTE 1: retransmission timer is set to 4ms + +Based on the evaluation results in Table B.2.16-1, the following observations can be made: + +- For FR1, DL + UL joint evaluation, DU, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from Qualcomm that: + - retransmission-less CG for UL pose provides: + - power saving gain of 20.0% for all UEs + - capacity gain of -2.1% + - performance reference CG with UL retransmission provides: + - power saving gain of 1.8% + - capacity gain of -2.0% + +### B.2.17 XR-specific playoutDelayForMediaStartup for XR UE power saving enhancement + +This clause captures evaluation results for XR-specific playoutDelayForMediaStartup for XR UE power saving enhancement: + +- CATT evaluated XR-specific playoutDelayForMediaStartup for XR UE power saving enhancement. When the size of the playout buffer is fed back to the gNB scheduler, gNB could have additional PDB for resource allocation of XR packet. + +**Table B.2.17-1: FR1, DL-only, InH, VR30** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity performance gain | Mean PSG of all UEs (%) | Mean PSG of satisfied UEs (%) | Additional Assumptions | +|--------|----------------|-------------|-------------------------------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|---------------------------|-------------------------|-------------------------------|------------------------| +| CATT | 1 | R1-2211174 | Baseline: DG scheduling with UE always on | - | - | - | H | 12 | 12 | 95.83% | 0.0% | 0.0% | - | | + +| | | | | | | | | | | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------|----|------------|------------------------------------------------------------------------------------|----|---|---|---|----|----|---------|-----|--------|---|----------| +| CA TT | 24 | R1-2211174 | XR-specific playoutDelayForMediaStartup scheme with go-to-sleep | 16 | 8 | 4 | H | 20 | 20 | 94.17 % | 67% | 26.43% | - | Note1 ,2 | +| CA TT | 25 | R1-2211174 | XR-specific playoutDelayForMediaStartup scheme with PDCCH skipping and go-to-sleep | 16 | 8 | 4 | H | 20 | 20 | 93.3% | 67% | 28.51% | - | Note1 ,2 | +| NOTE 1: The power saving gain is based on the same capacity as that of the baseline scheme (DG scheduling with UE always on). | | | | | | | | | | | | | | | +| NOTE 2: 3 frames playout buffer for all UEs | | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.17-1, the following observations can be made: + +- For FR1, DL only, InH, VR 30Mbps traffic at 60fps with 10ms PDB, it is observed from CATT that with the awareness of UE XR-specific playoutDelayForMediaStartup, UE can achieve: + - mean power saving gain of 26.43% to 28.51% + - mean capacity gain of 67% + +### B.2.18 Partial UL transmission + +This clause captures evaluation results for partial UL transmission: + +- Qualcomm evaluated the scheme for UE to transmit over a resource among the allocated resource that is just enough to transmit the UL data with a new UCI indicating to gNB the resources utilized/skipped in the PUSCH or the MCS selected by the UE. + +**Table B.2.18-1: FR1, UL-only, UMa, UL Pose/Control** + +| source | data row index | Tdoc source | Power saving scheme | CDRX cycle (ms) | ODT (ms) | IAT (ms) | Load H/L | #UE/cell | floor (Capacity) | % of satisfied UE | Capacity gain (%) | Mean PSG of all UEs (%) | Additional Assumptions | +|--------------------------------------------------------------------|----------------|-------------|------------------------------------------|-----------------|----------|----------|----------|----------|------------------|-------------------|-------------------|-------------------------|------------------------| +| QC | 11 | R1-2212134 | Baseline: Wideband UL Scheduler Baseline | - | - | - | H | 4 | 4 | 95% | 0% | 0.00% | | +| QC | 12 | R1-2212134 | Partial Uplink Transmission | - | - | - | H | 4 | 4 | 95% | 0% | 12.73% | Note1 | +| NOTE 1: power saving is calculated w.r.t. wideband UL transmission | | | | | | | | | | | | | | + +Based on the evaluation results in Table B.2.18-1, the following observations can be made: + +- For FR1, UL only evaluation, UMa, UL pose/control, it is observed from Qualcomm that with respect to the wideband UL transmission, the partial UL transmission provides: + - power saving gain of 12.73% + - capacity gain of 0% + +# --- Annex C (informative): RAN2 Study Item Agreements + +## C.1 RAN2#119-e + +Agreements from RAN2#119-e meeting: + +- RAN2 does not intend to ask RAN1 to change their simulation assumptions. +- RAN2 should take SA2/SA4 work into account. +- RAN2 assumes that PDU Set based parameters and PDU Set related information may be used for better support of XR services. RAN2 can consider both UL and DL directions. +- RAN2 will study PDU Set based parameters and PDU Set related information handling in Network and UE. +- RAN2 to adopt the current SA2 definition of PDU Set as an application media unit as working assumption, subjected to further guidance from SA2 and SA4. +- XR awareness discussion in RAN2 should consider PDU set characteristics and how to use the information available on those (for UL and/or DL). Can also consider how to handle data bursts. +- RAN2 can study e.g. periodicity, arrival time, jitter and frame-size variations for XR awareness to enable power savings and capacity enhancements. Can study also how often such parameters change (i.e. how dynamic they are). +- RAN2 can consider how PDU sets can be mapped to DRBs (FFS if SA2 discussion on PDU set mapping to QoS (sub-)flows impacts this). +- RAN2 to focus on the following issues for power saving, as well necessary parameters XR-awareness to support such enhancements, i.e.: + - DRX enhancements to address the issues of DRX cycle mismatch and jitter; + - Identify necessary parameters from CN for XR-awareness for power saving. +- Enhancements to Rel-17 PDCCH adaptation can be discussed based on RAN1 feedback, if they have any RAN2 impact. +- RAN2-specific aspects can be studied based on contributions (e.g. multiple XR traffic flows with different periodicities, SFN wrap-around, RAN2-specific CDRX aspects, ...). +- As starting point, RAN2 can further discuss the solutions in TR 38.838 that can impact on L2 operation (e.g., BSR, LCP, assistance information for scheduling, packet discarding, prioritization) for XR-specific capacity improvement. RAN2-specific solutions are not precluded (even if RAN1 hasn't discussed them before). +- Enhancement to SPS/CG should be justified for XR scheduling and should be evaluated against dynamic grant (DG) scheduling which should be considered as baseline. Should justify why enhancements are needed. +- RAN2 considers SPS enhancements may not be needed in Rel-18 XR since PDCCH capacity is not assumed to be a problem for XR. FFS if SPS has some power consumption benefits. + +## --- C.2 RAN2#119bis-e + +Agreements from RAN2#119bis-e meeting: + +- From RAN2 viewpoint, the following information would be useful for PDU set handling in UL and DL: + - Semi-static information (from CN to RAN): At least PSER and PSDB; + +- Dynamic information: At least identifying which PDU belongs to which data burst/PDU set is also needed, including means to determine at least PDU set boundaries. +- Capture the models 1a/b, 2a/b (from R2-2209777) in TR and indicate what is possible in current specifications and how. FFS how LCH options work in each case. +- SDAP maps each data packet in a PDU set to a single PDCP SDU, as in legacy (i.e. each PDU is only mapped to a single SDU). +- HARQ and RLC re-/transmissions for XR traffic are done as in legacy (i.e. they are not based on XR PDU sets). +- For UE transmitter, the PDCP discard should be performed per PDU set basis. +- For UE transmitter, the PDCP discard is managed per SDU for PDU set, the PDCP entity discards all PDCP SDUs associated with the PDU set. +- At least RRC pre-configuration and switching of configurations of DRX could be considered for enhancements of XR power saving. Other solutions are not precluded and can be further discussed. +- Introduce new BS table(s) to reduce the quantisation errors (e.g. for high bit rates). FFS how new BSR tables are created and how they impact BSR formats (can be discussed in WI phase). +- Delay information consists of at least "remaining time". +- RAN2 considers a delay information is useful for XR. FFS if dynamic reporting from UE to network (e.g. via BSR) is needed, or whether PSDB is sufficient. If we have delay information, it needs to distinguish how much data is buffered for which delay value. Stage-3 details (e.g. what's contained, how the triggering is done) can be discussed in the WI phase. +- If we have delay information reporting, RAN2 aims to define how the UE determines the "remaining time" in the delay information. +- Current CG configurations can be reused for UL XR traffic. FFS if enhancements are needed (RAN1 is already discussing something). RAN2 can discuss this in the next meeting. +- RAN2 can discuss potential enhancement to provide some assistant information on UL XR traffic for CG configurations at the gNB. FFS whether TSCAI can already provide all necessary information. +- RAN2 discuss whether additional traffic or QoS related information on downlink traffic beyond what has been agreed by SA2 needs to be provided to RAN for UE power savings. +- RAN2 study what traffic and QoS related information on uplink traffic (e.g. counterpart of what has been agreed by SA2) should be provided to RAN for UE power savings and how the information may be provided to RAN. +- Capture in TR that traffic parameters and Jitter are semi-static info. +- Can capture also SA2 agreements related to how they impact RAN2. + +## --- C.3 RAN2#120 + +Agreements from RAN2#120 meeting: + +- N1N excluded. +- Splitting DRB into multiple LCH (DC like) FFS. +- Should try to understand why we would need to treat PDU sets differently over the radio and why different PDU sets are muxed over same flows. Also need to understand need for reordering. LS to SA2/SA4 sent in R2-2213351. +- Agree that UE identifies PDU Sets / Bursts. +- In-band marking not needed. Further information considered if BSR is not enough. + +- Handling of discard FFS. +- Regarding making LCP delay aware: + - If delay-aware LCP is introduced, need the ability to turn it off; + - SRBs not impacted. + - Not considered further unless fundamental issues are identified. +- RAN2 to support timer-based discarding of UL transmit side of PDCP PDU/SDUs of a PDU set. FFS how this is modelled in PDCP specification, can be discussed in WI phase. +- RAN2 aims to allow XR frame rates that correspond to non-integer periodicities in at least semi-static manner (e.g. RRC). Details can be left to WI phase. +- RAN2 thinks we need one or more additional BSR table(s) for XR. FFS whether these are static (=specified) or dynamic (e.g. generated, differs according to some RRC parameter), can be discussed in WI phase. +- RAN2 will introduce data volume information associated with delay information (e.g. remaining time) in a MAC CE. FFS if this is extension of BSR or new format. FFS how to do that (e.g. what exactly is reported) and how to ensure this information is up-to-date e.g. considering UL scheduling delay. +- RAN2 needs to discuss additional BSR triggering conditions to allow timely availability of buffer status information at gNB. This can be discussed in WI phase. +- RAN2 sees some benefit from CG to XR services. RAN2 will address enhancements triggered by RAN1 work. +- RAN2 agrees some assistance information can be beneficial (e.g. periodicity, packet size). RAN2 assumes baseline could be TSCAI (pending SA2 conclusions), can discuss during WI phase whether something additional is needed on top of that. If any assistance information is needed, its definition should be standardized. +- RAN2 thinks all information may not be always available at UE application. + +## --- C.4 RAN2#121 + +Agreements from RAN2#121 meeting: + +- RAN2 thinks that how PSER is enforced is up to network implementation. +- Introduce UL PDU Set Importance. How UE derives this will be handled in UE implementation. +- Can indicate that in RAN2 considers PDU set concept applicable to both UL and DL in LS to SA2. +- RAN2 thinks UL jitter may be present for XR (e.g. for tethering use cases). It is unclear how network would use UL jitter information (depends on what would be signalled and would anyway be up to network implementation). +- RAN2 intends to support tethering use case for XR. This may require signalling of some UL traffic arrival information from UE to network. +- Since we already agreed to not support delay-aware LCP, RAN2 aims not to introduce changes to LCP due to PDU prioritization. +- RAN2 thinks PSI can be useful for PDU set-based discard. RAN2 aims to introduce a mechanism to allow UE to handle discarding of packets with different PSI in case of congestion. FFS for other cases. +- Support of RLC bearer splitting should be limited to existing cases (e.g. PDCP duplication), no new XR-specific functionality. + +# Annex D (informative): Change history + +| Change history | | | | | | | | +|----------------|-------------|------------|----|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-04 | RAN1#109 | R1-2204673 | | | | Initial Skeleton. | 0.0.1 | +| 2022-08 | RAN2#119 | R2-2207373 | | | | Initial Skeleton. | 0.0.1 | +| 2022-08 | RAN2#119 | R2-2207374 | | | | Updated Structure. | 0.0.2 | +| 2022-08 | RAN2#119 | R2-2208748 | | | | First Endorsed Baseline. | 0.1.0 | +| 2022-08 | RAN2#119 | R2-2208749 | | | | Table of Content updated. | 0.1.1 | +| 2022-09 | RAN2#119 | R2-2209220 | | | | Overview and first RAN2 agreements included. | 0.2.0 | +| 2022-10 | RAN2#119bis | R2-2210814 | | | | Relevant definitions from 23.700-60 included
Useful pieces of information from SA4 LS added (S4-220505 and S4aV220921)
RAN2 agreements on PDU Set handling, discard, L2 structure captured, BS tables and delay reporting added. | 0.3.0 | +| 2022-11 | RAN2#120 | R2-2212908 | | | | Minor editorial corrections | 0.3.1 | +| 2022-12 | RAN2#120 | R2-2213229 | | | | RAN2 agreements on PDU Set handling, L2 architecture, BSR, discard and assistance information captured.
SA2 agreements on KI#4,5 (S2-2211440) and KI#8 (S2-2211404) captured.
RAN1 agreements (R1-2213015). | 0.4.0 | +| 2022-12 | RAN#98 | RP-223187 | | | | Clean version for information. | 1.0.0 | +| 2023-02 | RAN2#121 | R2-2300152 | | | | Update reflecting latest agreements from SA2 and SA4. | 1.0.1 | +| 2023-03 | RAN2#121 | R2-2302309 | | | | RAN2 agreements on radio protocols impacts. | 1.0.2 | +| 2023-03 | RAN#99 | RP-230307 | | | | Clean version for approval. | 2.0.0 | +| 2023-03 | RAN#99 | | | | | Promoted to version 18.0.0 | 18.0.0 | +| 2023-04 | RAN#99 | | | | | Swapped Figure 5.1.2-1 into a higher-resolution one | 18.0.1 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38846/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-18/38_series/38846/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46816db812cbd3ead4eb47ad668c5a86d6002622 --- /dev/null +++ b/marked/Rel-18/38_series/38846/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9ddfb4326279c9c1efc4be364810fc005a2dd103e2342004a091f80cb5baf04 +size 107280 diff --git a/marked/Rel-18/38_series/38846/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38846/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66e93ed1c950ee9bf3c824d9edebf36bdb10bb6b --- /dev/null +++ b/marked/Rel-18/38_series/38846/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4c897efa4b937e3445fc82e9681b40be2dff805f5ac5a958b8d0da8c594d7bb +size 7625 diff --git a/marked/Rel-18/38_series/38846/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38846/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c13ebf588a54b69894ac9f2b4fd70a7c80d7731 --- /dev/null +++ b/marked/Rel-18/38_series/38846/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8f13b0d1fe6af2abe6eb271741d114d18c1bf928bf2dec59b6b4bf488f557d7 +size 5581 diff --git a/marked/Rel-18/38_series/38846/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-18/38_series/38846/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63e438bc2927360ce807227f2f857c2a5c15dd54 --- /dev/null +++ b/marked/Rel-18/38_series/38846/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:249b97bf952b372f89e0d52a60fd66ce3985878c1da550b7c9257aa24730b302 +size 70971 diff --git a/marked/Rel-18/38_series/38846/b90dcb4c35f1875e19ca312a6cf4adae_img.jpg b/marked/Rel-18/38_series/38846/b90dcb4c35f1875e19ca312a6cf4adae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..943b5b7fe5e06f9cfb332027fba2c548eb19a434 --- /dev/null +++ b/marked/Rel-18/38_series/38846/b90dcb4c35f1875e19ca312a6cf4adae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16629ed63e532f5060b11c016bd381472114dd673c60dca8d660daff84ce7829 +size 29363 diff --git a/marked/Rel-18/38_series/38846/c85b57b2414f341860dfc338e1cf2509_img.jpg b/marked/Rel-18/38_series/38846/c85b57b2414f341860dfc338e1cf2509_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..543ac26f4877dc763f74058bbb3a627685ef817b --- /dev/null +++ b/marked/Rel-18/38_series/38846/c85b57b2414f341860dfc338e1cf2509_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ed337e5259fdfdf915b7277c12406c99b0d8dded1d63ef7a234beaaaa9cb4ed +size 37574 diff --git a/marked/Rel-18/38_series/38846/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-18/38_series/38846/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49192ac6be1dab2f20744579931ef6c13515ffda --- /dev/null +++ b/marked/Rel-18/38_series/38846/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d338c70ce5fa555155ef8178eb4d42d492dd07e8c2d7d7d6ddc4e9ebaa279a67 +size 41494 diff --git a/marked/Rel-18/38_series/38846/f1cbfa3fc27f58581615654fec4335d8_img.jpg b/marked/Rel-18/38_series/38846/f1cbfa3fc27f58581615654fec4335d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..561eba01a3b71b1acf16f0ea2c1dc0e9a7daabde --- /dev/null +++ b/marked/Rel-18/38_series/38846/f1cbfa3fc27f58581615654fec4335d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a2bd1991aee442e8f5aa71f9e95b7906d47877904e12c2575e0e7458855f78f +size 22615 diff --git a/marked/Rel-18/38_series/38846/f7d969388c4f7e30cd04a061314bfa0e_img.jpg b/marked/Rel-18/38_series/38846/f7d969388c4f7e30cd04a061314bfa0e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fee40ad0e2fe5886f5d8d9878dc8801deba68618 --- /dev/null +++ b/marked/Rel-18/38_series/38846/f7d969388c4f7e30cd04a061314bfa0e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f272924169351500a0b573c2105c4da0b84f3eb575684e81c94dacb71f0c83f +size 27986 diff --git a/marked/Rel-18/38_series/38846/raw.md b/marked/Rel-18/38_series/38846/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..05df22dfc7293dc24886856214f3676dffd5d51f --- /dev/null +++ b/marked/Rel-18/38_series/38846/raw.md @@ -0,0 +1,2402 @@ + + +# 3GPP TR 38.846 V18.0.0 (2023-12) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on simplification of band combination specification for NR and LTE (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 of terms, symbols and abbreviations..... | 7 | +| 3.1 Terms..... | 7 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations ..... | 8 | +| 4 Background..... | 9 | +| 5 Working procedure of specifying band combinations ..... | 10 | +| 5.1 General ..... | 10 | +| 5.1A Band combination request..... | 11 | +| 5.1A.1 Band combination workflow ..... | 11 | +| 5.1A.1.1 The workflow on introduction of band combinations for block approval..... | 11 | +| 5.1B Usage of band combination..... | 12 | +| 5.1B.1 Notation of CA or DC configurations in the request sheets and work item descriptions ..... | 12 | +| 5.2 New templates for specifying band combinations ..... | 12 | +| 5.2.1 Templates for PC3 band combinations..... | 12 | +| 5.2.2 Templates for high power UE band combinations..... | 14 | +| 5.2.3 New templates of delta T IB / R IB due to NE-DC and SUL band combinations in Rel-18 ..... | 15 | +| 5.2.4 New template for $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ tables for CA/DC ..... | 16 | +| 5.3 Fallback aspects for specifying band combinations..... | 17 | +| 5.4 Submitting technical contributions (Tdoc) for specifying band combinations..... | 18 | +| 5.4.1 Text Proposal (TP) or Draft Change Request (draft CR) ..... | 18 | +| 5.4.2 Specific for Text Proposal (TP)..... | 18 | +| 5.4.3 Specific for Draft Change Request (draft CR) ..... | 18 | +| 5.4.4 Which agenda to submit the Tdoc for ..... | 18 | +| 6 Guidelines of specifying band combinations..... | 18 | +| 6.1 General ..... | 18 | +| 6.1A Notation of lists of bands and bandwidths within a configuration..... | 20 | +| 6.1A.1 Band numbers ..... | 20 | +| 6.1A.2 Bandwidth classes ..... | 20 | +| 6.1A.2.1 Bandwidth classes for LTE..... | 20 | +| 6.1A.2.2 Bandwidth classes for NR..... | 21 | +| 6.1B Rules to be used for the notation of CA or DC configurations ..... | 22 | +| 6.1C Adding or removing channel BW's in NR CA configurations ..... | 23 | +| 6.1C.1 Adding channel BW's in NR CA configurations ..... | 23 | +| 6.1C.2 Removing channel BW's in NR CA configurations ..... | 23 | +| 6.1C.2.1 Removing of not possible channel BW's ..... | 23 | +| 6.1C.2.2 Removing of possible channel BW's..... | 23 | +| 6.2 Guidelines on band combination fallbacks ..... | 24 | +| 6.2.1 General definition of fallbacks ..... | 24 | +| 6.2.2 Mandatory Fallbacks ..... | 25 | +| 6.2.3 Fallbacks of EN-DC Configurations ..... | 26 | +| 6.2.4 Fallbacks of UL Configurations ..... | 26 | +| 6.2.5 Fallback rules for some exceptional cases..... | 26 | +| 6.2.6 Guidelines on valid CBW for higher order BC depending on fallbacks..... | 27 | +| 6.3 Guidelines on delta T IB and R IB due to band combinations ..... | 27 | +| 6.4 Guidelines on simplification for CA configurations ..... | 28 | +| 6.5 Guidelines on Co-Existence analysis..... | 29 | +| 6.5.1 Uplink Intra-Band CA with one UL CC transmissions..... | 29 | +| 6.5.2 Uplink Intra-Band CA with two UL CC transmissions..... | 30 | +| 6.5.3 Uplink triple beat..... | 32 | +| 6.6 Rules for band combination with BCS4/BCS5 ..... | 33 | +| 6.6.1 Introduction of BCS4/BCS5 ..... | 33 | + +| | | | +|---------------------------------------------------|--------------------------------------------------------------------------------------------------------------|-----------| +| 6.6.2 | Guidelines for band combination with BCS4/BCS5 ..... | 34 | +| 6.6.3 | The maximum aggregated bandwidth for intra-band CA with BCS4/BCS5 ..... | 35 | +| 6.7 | Guidelines on simplification for 3DL/2UL MSD due to 2UL IMD interference ..... | 35 | +| 6.8 | Guidelines on configuration tables..... | 36 | +| 6.8.1 | CA configuration table ..... | 36 | +| 6.8.2 | DC configuration table ..... | 39 | +| 6.8.3 | SUL configuration table ..... | 44 | +| 7 | Test burden reduction for band combinations..... | 46 | +| 7.1 | General ..... | 46 | +| 7.2 | Similarity and Dependency of Tx RF requirements for different features on the same band combination..... | 46 | +| 7.2.1 | Maximum output power ..... | 46 | +| 7.2.2 | Spurious emission for UE-to-UE coexistence..... | 54 | +| 7.3 | Similarity and Dependency of Rx RF requirements for different features on the same band combination .... | 54 | +| 7.3.1 | REFSENS exception due to harmonic/harmonic mixing interference for inter-band combinations (two bands) ..... | 54 | +| 7.3.2 | REFSENS exception due to cross band isolation interference for inter-band combinations (two bands) ..... | 54 | +| 7.3.3 | REFSENS exception due to inter-modulation distortion for inter-band combinations (two bands)..... | 55 | +| 7.3.4 | REFSENS requirements without any degradation for inter-band combinations (two bands)..... | 68 | +| 7.4 | Test burden reduction for multiple MSD ..... | 68 | +| 8 | Conclusion ..... | 71 | +| Annex A (informative): Change history..... | | 72 | + +# 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 simplification of band combination specification for NR and LTE. The purpose of this TR is to further optimize and improve the working procedure for specifying band combination. A technical report will be created to collect the rules of band combination during the timescale of Rel-18 so as to improve the efficiency of band combination specifying and the quality of specifications. The dependency and applicability for RF requirements among different features for the same spectrum combination to reduce the redundant tests will also be investigated in the TR. The valid rules and valuable guidelines for requesting and specifying band combinations in Rel-17 TR 38.862 [7] are captured in the TR. + +# 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-221790, "Revised SID: Study on simplification of band combination specification for NR and LTE", RAN#96. +- [3] 3GPP TR 38.817-01: "General aspects for User Equipment (UE) Radio Frequency (RF) for NR". +- [4] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [5] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone". +- [6] 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". +- [7] TR38.862: "Study on band combination handling in RAN4". +- [8] RP-202832, "New WID: Introduction of bandwidth combination set 4 (BCS4) for NR", RAN#90-e. +- [9] R4-2220556, WF on triple beat rules and MSD for inter-band with 2UL with intra-band ULCA, RAN4#105. + +# 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]. + +**Aggregated Channel Bandwidth:** The RF bandwidth in which a UE transmits and receives multiple contiguously aggregated carriers. + +**Carrier aggregation:** Aggregation of two or more component carriers in order to support wider transmission bandwidths. + +**Carrier aggregation band:** A set of one or more operating bands across which multiple carriers are aggregated with a specific set of technical requirements. + +**Carrier aggregation bandwidth class:** A class defined by the aggregated transmission bandwidth configuration and maximum number of component carriers supported by a UE. + +**Carrier aggregation configuration:** A combination of CA operating band(s) and CA bandwidth class(es) supported by a UE. + +**Contiguous carriers:** A 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. + +**Fallback group:** Group of carrier aggregation bandwidth classes for which it is mandatory for a UE to be able to fallback to lower order CA bandwidth class configuration. It is not mandatory for a UE to be able to fallback to lower order CA bandwidth class configuration that belong to a different fallback group. + +**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. + +**Sub-block:** This is one contiguous allocated block of spectrum for transmission and reception by the same UE. There may be multiple instances of sub-blocks within an RF bandwidth. + +## 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 inter-band CA operation, for serving cell $c$ | +| $\Delta T_{IB,c}$ | Allowed maximum configured output power relaxation due to support for inter-band CA operation, inter-band NR-DC operation and due to support for SUL operations, for serving cell $c$ | +| $BW_{Channel}$ | Channel bandwidth | +| $BW_{Channel\_CA}$ | Aggregated channel bandwidth, expressed in MHz | +| $N_{RB}$ | Transmission bandwidth configuration, expressed in units of resource blocks | + +## 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]. + +| | | +|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BCS | Bandwidth Combination Set | +| BS | Base Station | +| BW | Bandwidth | +| CA | Carrier Aggregation | +| CA_nX-nY | Inter-band CA of component carrier(s) in one sub-block within Band nX and component carrier(s) in one sub-block within Band nY where nX and nY are the applicable NR operating bands . | +| CC | Component carrier | +| DC | Dual Connectivity | +| DL | DownLink | +| E-UTRA | Evolved Universal Terrestrial Radio Access | +| EN-DC | E-UTRA/NR DC | +| FDD | Frequency Division Duplex | +| IMD | Inter-modulation | +| LTE | Long Term Evolution | +| MR-DC | Multi-radio DC | +| MSD | Maximum Sensitivity Deduction | +| NE-DC | NR/E-UTRA DC | +| NR | New Radio | + +| | | +|-------|-----------------------| +| NR-DC | NR/NR DC | +| RF | Radio Frequency | +| Rx | Receiver | +| SCS | Subcarrier spacing | +| TDD | Time Division Duplex | +| Tx | Transmitter | +| UE | User Equipment | +| UL | UpLink | +| V2X | Vehicle to Everything | + +# 4 Background + +At 3GPP RAN#96 meeting, a revised Rel-18 Study Item “Study on simplification of band combination specification for NR and LTE” was approved. The objectives are as follows, + +- Investigate and simplify the working procedure for approving documents for TS and TR to improve the efficiency to specify band combinations and the quality of specifications +- Improve the efficiency considering + - RAN4 reduces the redundant and unnecessary work for big CRs, draft CRs and/or TPs, if any + - The following rules will be investigated and defined if necessary + - Investigate whether the workflow can be improved under the condition that quality can be guaranteed. + - Develop rules or guidelines covering the process of not for block approval. + - Develop the necessary tools to reduce RAN4’s workloads if feasible +- Improve the quality considering + - RAN4 improves the procedures for cross-checking to avoid conflict between big CR/CRs across basket WIs and other WIs + - RAN4 captures the agreements about the rules and guidelines including but not being limited to the outcome of the above sub-bullets in the corresponding TR + +Investigate the feasibility and optimize the specification structure and reduce the test burden + +- Study the methodology to simplify the test efforts for a UE supporting multiple features, e.g., NR-CA, EN-DC on the same band combination +- Study of similarity and dependency of RF requirements for different features on the same band combination +- Study the methodology to simplify RF requirement specifications for + - MSD requirements in 38.101-1 and 38.101-3, e.g., reducing the test configurations with different bandwidth combinations + - For Delta\_TIB and Delta\_RIB requirements, investigate and define the framework of the general principle or requirements with band-combination specific exceptions + - For Delta\_TC,c, investigate whether it can be removed in low boundary formula for Pcmax + +NOTE 1: The requirements applicable to UE won’t be changed or increased. + +NOTE 2: The work should be applied to all the power classes + +The target is that after the completion of the study item, the working procedure to specify the band combinations will be refined and the quality of specifications will be improved in the stage of Rel-18. A set of new guidance on band combination handling, rule collections and band combination optimization for RAN4 specifications will be approved. + +The feasibility to reduce the test burden of band combinations will be discussed. It is suggested that the rules related to the band combinations should be applied to the latest RAN4 specifications after the completion of the SI. + +# 5 Working procedure of specifying band combinations + +## 5.1 General + +In order to make the band combinations work more efficient, RAN4 has decided to re-organize the corresponding basket WIs in Rel-18 with the following agreements. + +- *General:* + - *To merge 1BUL and 2BUL basket WI for NR CA, i.e. merged into xBUL (x=1,2).* + - *To establish one basket WI for SUL and one basket WI for V2X.* + - *NR SUL combos\_R18.* + - *NR LTE V2X\_PC5 combos\_R18.* + - *2UL CA in FR1 + 1UL in FR2 can be treated in 2UL since we don't need to count the number of FR2 UL.* + - *There is no need to set a dedicated WI for non-block approval combos.* +- *Consider the following NR CA/DC band combination basket WIDs in Rel-18.* + - *NR CA/DC* + - *NR\_CA\_R18\_intra including TR and TP's.* + - *NR\_CADC\_R18\_2BDL\_xBUL (x=1,2) including TR and TP's.* + - *NR\_CADC\_R18\_3BDL\_xBUL (x=1,2) including TR and TP's.* + - *NR\_CADC\_R18\_yBDL\_xBUL (y=4,5,6, x=1,2) without TR and TP's.* + - *MR DC* + - *DC\_R18\_1BLTE\_1BNR\_2DL2UL.* + - *DC\_R18\_2BLTE\_1BNR\_3DL2UL.* + - *DC\_R18\_xBLTE\_1BNR\_yDL2UL (x= 3, 4, 5).* + - *DC\_R18\_xBLTE\_2BNR\_yDL2UL.* + - *DC\_R18\_xBLTE\_yBNR\_zDL2UL (x=1, 2, 3, y>2, z≤6).* + - *DC\_R18\_xBLTE\_yBNR\_zDL3UL (x=1, 2, 3, 4, y=1, 2; 3≤z≤6).* + +Regarding to the simplification of working procedure, the following agreements have been achieved. + +- The proponent of new BC request should be the first responsible person for checking the fallback BCs for a new BC request, and all companies are encouraged to check the fallbacks. +- With regard to the order of the request BC and its fallbacks, it is agreed that the higher order combination and its fallbacks request could be in parallel. +- For the deadline of BC request, same deadline as RAN4 Tdoc submission is supposed. + - No request of adding new band combinations into basket WIs will be handled for bis-meeting and ad-hoc meeting. + - No new band combination is allowed to be requested after the deadline. +- It is allowed to only correct the missing fallback and add more supporting companies for the proposed band combinations. + +For V2X basket WI, the working procedure agreed in normal CA/DC basket WIs also be applied. + +- To ensure the higher order combination not earlier than the lower order combinations in the spec, the following guidelines applied. + - Document the definition of fallback modes and the rules related to fallback mode in RAN4 TR. + +- The big CRs for higher and lower order band combinations should be agreed in the same meeting. +- The rapporteurs do not have bland rows in the WID spreadsheets to facilitate the readers to sort out the interested band combinations. + +## 5.1A Band combination request + +### 5.1A.1 Band combination workflow + +#### 5.1A.1.1 The workflow on introduction of band combinations for block approval + +In order to improve the efficiency of RAN4's work, it's necessary to introduce a clear workflow on the introduction of band combinations for block approval. The workflow on the introduction of band combinations for block approval is shown as figure 5.1A.1.1-1 as a typical example for one RAN4 meeting in one quarter. The specific steps are listed as below. + +#1 Band combinations should be requested by contact person using request template. And the request spread sheet should be shared in the reflector 3GPP\_TSG\_RAN\_WG4\_NR\_BANDS for NR CA, MR DC and SUL band combinations or 3GPP\_TSG\_RAN\_WG4\_CA for LTE CA band combinations before RAN4#(X-1) meeting. + +#2 Band combinations should be captured into the draft revised WIDs during RAN4#(X-1) meeting by rapporteurs. + +#3 The official revised basket WIDs can be approved together with requested band combinations during RAN#(Y-1) meeting. + +#4 Proponents should prepare and submit the corresponding contributions, e.g. draft CR, TP before RAN4#X meeting. If a draft CR or TP is depending on approval of lower order fallbacks submitted at the same meeting, this need to be clearly mentioned in the cover sheet of the draft CR or in the heading of the TP. + +#5 The Block/Approval procedure is applicable to the band combinations in one week before formal RAN4#X meeting, if there is no general issues observed. + +#6 The contributions will be discussed during RAN4#X meeting. If there are no technical concerns and if all the needed fallbacks are completed, the band combinations can be approved. And the final decision will be made by chairman. + +#7 If the contributions are approved or endorsed, the corresponding band combinations should be captured into the big CRs and/or TRs by rapporteurs. Note: The big CR is an official CR which is used to capture all the corrections for one specification by rapporteur under basket WI. + +#8 Email approval can be used for the big CRs and/or TRs in one week after formal RAN4#X meeting. + +#9 The status of band combinations should be shared by contact person after formal RAN4#X meeting. + +#10 The status of band combinations should be captured into the WID and/or SR by rapporteurs. + +#11 RAN #Y will approve the big CRs and revised WIDs. + +#12 The agreed band combinations will be introduced into the specification in next version. + +![Flowchart illustrating the workflow on the introduction of band combinations for block approval. The process starts with 'Start Band combination' and proceeds through 12 steps, including requests, captures, approvals, and final introduction into the spec. Key templates mentioned are 'Request template', 'Basket WID template', and 'SR template'. Timing markers include 'Before RAN4#(X-1)', 'During RAN4#(X-1)', 'During RAN#(Y-1)', 'During RAN4#X', 'One week Before formal RAN4#X', 'One week After formal RAN4#X', and 'During RAN#Y'.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +graph TD + Start([Start Band combination]) --> S1[#1 Requested by contact person] + S1 --> S2[#2 Captured into draft revised WID] + S2 --> S3[#3 Revised WID is approved by RANp] + S3 --> S4[#4 Prepare and submit the draft CR/ TP] + S4 --> S5[#5 Block/Approval] + S5 --> S6[#6 Approve/Endorse the contributions after discussion] + S6 --> S7[#7 Captured into the big CR/ TR by rapporteur] + S7 --> S8[#8 Email approval for big CR and TR] + S8 --> S9[#9 The status is shared by contact person] + S9 --> S10[#10 The combo's status is captured into WID and SR] + S10 --> S11[#11 RAN plenary approves the big CR and revised WID] + S11 --> S12[#12 Band combinations will be introduced into the spec] + S12 --> End([End]) + + S1 --- RT[Request template] + S1 --- BR1[Before RAN4#(X-1)] + S2 --- BWT[Basket WID template] + S2 --- DR1[During RAN4#(X-1)] + S3 --- DR2[During RAN#(Y-1)] + S4 --- BR2[Before RAN4#X] + S5 --- OW1[One week Before formal RAN4#X] + S6 --- DR3[During RAN4#X] + S7 --- DR4[During RAN4#X] + S8 --- OW2[One week After formal RAN4#X] + S9 --- ST[SR template] + S9 --- OW3[One week After formal RAN4#X] + S10 --- ST2[SR template] + S10 --- OW4[One week After formal RAN4#X] + S11 --- BWT2[Basket WID template] + S11 --- DR5[During RAN#Y] + +``` + +Flowchart illustrating the workflow on the introduction of band combinations for block approval. The process starts with 'Start Band combination' and proceeds through 12 steps, including requests, captures, approvals, and final introduction into the spec. Key templates mentioned are 'Request template', 'Basket WID template', and 'SR template'. Timing markers include 'Before RAN4#(X-1)', 'During RAN4#(X-1)', 'During RAN#(Y-1)', 'During RAN4#X', 'One week Before formal RAN4#X', 'One week After formal RAN4#X', and 'During RAN#Y'. + +Figure 5.1A.1.1-1 The workflow on the introduction of band combinations for block approval + +## 5.1B Usage of band combination + +### 5.1B.1 Notation of CA or DC configurations in the request sheets and work item descriptions + +The configurations notation discussed in Clause 5 are also used for the CA/DC configurations in the columns for the CA/DC configurations for DL and UL in the request sheets and the combination tables within the WIDs. However, multiple errors within the specifications have been observed, which motivate the need to define the following rules how to implement these band combinations within the CA/DC configurations lists within the excel tables in the request sheets and WIDs: + +- Each cell of the CA or DC configuration column in the Excel tables shall contain only one single CA/DC configuration using the notation of the configurations as discussed above +- Similar CA or DC configurations with different bandwidth classes shall use another row in the same column of the table. +- The UL configurations column shall only contain the UL configurations valid for the CA/DC configuration in the same row, if there are multiple valid UL configurations they can be listed one after the other separated with “,” (a comma followed by a space), but they can also be using a single completely filled row for each of the valid UL configurations +- There shall be no merged cells in the table +- The WI rapporteur checks if the notation of the CA/DC configurations is correct and if not returns the request to the requestor. Incorrect requests should not be added to the table in the WID. + +## 5.2 New templates for specifying band combinations + +### 5.2.1 Templates for PC3 band combinations + +Some general rules are listed about the Excel spread sheet template. + +#1 The Excel spread sheet can be used as the templates of request sheet, status report, and band combinations table in basket WI. The templates can be found in the following 3GPP ftp server. + +#2 All request table, status report table and band combination index table of basket WID are unified to use one template for band combination information sheet. + +#3 Cover sheet which is the first sheet in the template can be only used by Contact Company which needs to request new band combinations or some modifications or report the band combinations' status instead of the official basket WID or Status Report. Cover sheet can be further updated after additional basket WIs are approved in RAN plenary. + +#4 Rapporteurs can choose some of these BCS table sheets to suit their WID. For BCS4/BCS5 there is no need to add information in the BCS sheet since there is no channel BW details to be filled in for them. + +#5 Only one sheet/Excel attachment is used for both the WID and the status report by rapporteurs. + +#6 The following rules and marks can be used to indicate the change marks for the band combinations in the Excel spread sheet. + +1) The Excel sheet included in the status report and the WID would have 2 worksheets. + +- Details of band combinations status of RAN #Y-1. It's the simple copy from last RAN meeting. +- Details of band combinations status of RAN #Y + +2) The worksheet of RAN #Y would have an extra column A "Are there any change marks?" which includes 4 words: + +- **New** for new if the whole line is new. Those lines could be marked in blue. +- **Modified** for modified if any field in this line is modified. The modified field could be marked in yellow. +- **Deleted** for deleted if the whole line needs to be removed. The whole line could be marked in red. +- **Unchanged** for all the information about combination aren't changed. + +| Change marks | Explanation | +|--------------|------------------------------------------------------------------------------------------------------------------------------------| +| New | Each new row from a contact company request is marked in blue with New in first column. | +| Modified | Some columns of the row are modified. The rapporteur will mark those changed cells in yellow and use Modified in the first column. | +| Deleted | For a removed band combination, the rapporteur marks the row in red and uses Deleted in first column. | +| Unchanged | No changes in any field of the row | + +3) How would this Excel sheet be used: + +3.1) WID update: + +- Excel lists from RAN #Y-1 are taken, all lines with "Deleted" are removed, all yellow and blue highlights are removed, all words "New" and "Modified" in "changes" column A are changed to "Unchanged" + +- This provides the updated intermediate Excel lists of RAN #Y-1 and copies of both lists are made to make the intermediate lists for RAN #Y + +If we start this with new release, then the RAN #Y-1 lists would not be needed because there are no new release combinations yet. + +- Now lists of RAN #Y are updated: + +- all new lines coming from contact company requests are inserted and marked in blue with "New" in first line + +- There may be some to be modified, so rapporteur will mark changed fields in yellow and use “Modified” in first column +- There may be a few to be deleted, so rapporteur marks the line in red and uses “Deleted” in first column +- If all the information about combination aren’t changed, rapporteur marks the line in unfilled colour and uses “Unchanged” in first column. +- For the changes in the BCS sheet, rapporteurs and proponent can mark change fields in yellow. + +#### 3.2) Status Report update: + +- Assuming the WID update Excel list is ready after the RAN4 meeting, + +The rapporteur can use the same Excel list for the status report: i.e. + +- Contact companies can easily filter for ongoing combinations of their company and then + - Leave the line unchanged if all the information about combination aren’t changed. + - Change the status to completed, fill in column A~T, then these mark all these modified field in yellow and indicate Modified in first column + - Change the status to stopped, mark this field in yellow and indicate “Modified” in first column. +- Rapporteurs can check and take over the different inputs into their master copy. + +The R18 PC3 basket WID items were improved in RAN#96 meeting, including PC3 ENDC/NEDC, NR CA/DC, SUL and V2X basket WIDs, due to some of the R17 PC3 basket WID items are merged into one R18 PC3 basket WID, and also the table templates in the specification were changed during R17 discussion. Therefore, the original templates of band combination request sheet, status report and band combination table should be updated accordingly. + +The updated EXCEL templates of band combination request sheet, status report and band combination table for Rel-18 PC3 band combinations can be found in the following 3GPP ftp server. + +[https://www.3gpp.org/ftp/tsg\\_ran/WG4\\_Radio/Templates/](https://www.3gpp.org/ftp/tsg_ran/WG4_Radio/Templates/) + +*(Editor's note: The approved latest templates for PC3 band combinations are in R4-2307985)* + +Besides the updated EXCEL templates, the other general rules captured in the section 6.2.2 in TR 38.862 [7] are still valid. + +The update templates for PC3 NR CA, EN-DC, SUL and V2X band combinations in Rel-18 include the sheets for ‘Cover sheet’, ‘Band combination table’, ‘FR1 intra-band CA BCS table’, ‘FR2 intra-band CA BCS table’, ‘FR2 intra-band NCCA BCS table’, ‘Intra-band ENDC BCS table’, ‘FR1 inter-band BCS table’, ‘FR2 inter-band BCS table’, ‘FR1+FR2 inter-band BCS table’, ‘SUL band combination BCS table’, ‘V2X band combination BCS table’ and ‘FR1 Mixed intra-band CA BCS’: + +- Merging all the channel bandwidth columns into one column. +- Using ‘,’ between two adjacent channel bandwidths. +- Removing the channel bandwidth number in the table head. +- Only for inter-band NR CA) Using simple texts like ‘CA\_nXC\_BCS0’ or ‘CA\_nX(2A)\_BCS0’ for the constitute band supporting intra-band contiguous or non-contiguous CA , respectively, associated with a new note of “The CA configurations are given in Table 5.5A.1-1 or Table 5.5A.2-1 in this specification”. + +### 5.2.2 Templates for high power UE band combinations + +Specifying HPUE band combination follows the same procedure as PC3 band combination. Request for additions of HPUE band combinations shall be provided by the proponents and sent to the 3GPP\_TSG\_RAN\_WG4\_NR\_BANDS email reflector before a RAN4 Tdoc submission deadline and no new band combinations are allowed to be requested after the deadline except to correct the missing fallback and add more supporting companies for the proposed band + +combinations. The templates can be found in the following 3GPP ftp server and be applied to HPUE band combination request, revised WID and status report. + +[https://www.3gpp.org/ftp/tsg\\_ran/WG4\\_Radio/Templates/](https://www.3gpp.org/ftp/tsg_ran/WG4_Radio/Templates/) + +(Editor's note: The approved latest templates for HPUE band combinations are in R4-2306587) + +Because there is no MSD analysis for FR1+FR2 NR-CA, NR-DC and EN-DC combinations ( $3 \times 7.125 \text{ GHz} = 21.375 \text{ GHz}$ which is below the lower edge of the TN FR2 range of 24.25 GHz), there is no need to request HPUE for FR1+FR2 combinations, or to document support for HPUE for FR1+FR2 combinations in 38.101-3. The FR1 HPUE requirements for the FR1 fallbacks of FR1+FR2 combinations apply to the FR1 part of FR1+FR2 combinations. + +The templates for HPUE band combination in Rel-18 include the sheets for ‘Cover sheet’, ‘1.1&1.2 BC table’, ‘1.3 BC table with 2 SUL cells’ and ‘2 BC table’, in which the band combination list categorizes into: + +- 1.1 Band combination list for Power class 2 NR Inter-band CA/DC for y bands DL with x bands UL (x=1, 2). + - o HPUE\_FR1\_TDD\_NR\_CADC\_SUL\_R18 + - o Power class cases for uplink + - 1UL(TDD): PC2 on TDD band + - 2UL(FDD+TDD, TDD+FDD, TDD+TDD): PC3 on FDD band, PC2 or PC3 on TDD band +- 1.2 Band combination list for Power class 1.5. + - o HPUE\_FR1\_TDD\_NR\_CADC\_SUL\_R18 + - o Power class cases for uplink + - 1UL(TDD): PC1.5 on TDD band +- 1.3 Band combination list for Power class 2 SUL band combinations with or without CA for y bands DL with 2 bands UL. + - o HPUE\_FR1\_TDD\_NR\_CADC\_SUL\_R18 + - o Power class cases for uplink + - SUL: PC3 or PC2 on SUL band + - NUL(TDD): PC2 on TDD band, where NUL = Normal Uplink in contrast to SUL. +- 2 Band combination list for High power UE (power class m with $1 < m < 3$ ) for a single FR1 band in UL of Dual Connectivity (DC) combinations of x bands (x=1,2,3, 4 for y=1 or x=1, 2 for y=2) LTE inter-band CA (xDL/1UL) and y bands NR inter-band CA (yDL/1UL). + - o HPUE\_FR1\_DC\_LTE\_NR\_R18 + +### 5.2.3 New templates of delta TIB / RIB due to NE-DC and SUL band combinations in Rel-18 + +For inter-band NE-DC within FR1, unless otherwise stated, the value of $\Delta T_{IB,c}$ for the correspondingly specified EN-DC combination is applicable. However, for some specific NE-DC combinations, there are no corresponding EN-DC combinations defined in the spec. To unify the template as the cases in EN-DC combinations, the new delta $T_{IB}$ template in Table 5.2.3-1 and delta RIB template in Table 5.2.3-2 for NE-DC combinations applies respectively, two bands as an example. + +**Table 5.2.3-1: New template for $\Delta T_{IB,c}$ due to NE-DC (two bands)** + +| Inter-band NE-DC configuration | $\Delta T_{IB,c}$ for NR band / E-UTRA band (dB)* | | | | +|-------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------|--|--|--| +| | Component band in order of bands in configuration** | | | | +| DC_nx_y | | | | | +| NOTE *: “-” denotes $\Delta T_{IB,c} = 0$ . | | | | | +| NOTE **: The component band order in the configuration should be listed by the order of NR band and E-UTRA band respectively. | | | | | + +**Table 5.2.3-2: New template for $\Delta R_{IB,c}$ due to NE-DC (two bands)** + +| Inter-band NE-DC configuration | $\Delta R_{IB,c}$ for NR band / E-UTRA band (dB)* | | | | +|-------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------|--|--|--| +| | Component band in order of bands in configuration** | | | | +| DC nx y | | | | | +| NOTE *: “-” denotes $\Delta R_{IB,c} = 0$ . | | | | | +| NOTE **: The component band order in the configuration should be listed by the order of NR band and E-UTRA band respectively. | | | | | + +For the UE which supports SUL band combination, the template for $\Delta T_{IB,c}$ in Table 5.2.3-3 and $\Delta R_{IB,c}$ in Table 5.2.3-4 applies respectively, three bands as an example. + +**Table 5.2.3-3: New template for $\Delta T_{IB,c}$ due to SUL band combination (three bands)** + +| Band combination for SUL | $\Delta T_{IB,c}$ for NR bands / SUL band (dB)* | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------|--|--|--|--|--| +| | Component band in order of bands in configuration** | | | | | | +| CA nx SUL ny-nz | | | | | | | +| NOTE *: “-” denotes $\Delta T_{IB,c} = 0$ . | | | | | | | +| NOTE **: The component band order in the configuration should be listed by the order of NR bands and SUL band, such as for CA_n79_SUL_n41-n83 the band order from left to right is n41, n79 and n83. | | | | | | | + +**Table 5.2.3-4: New template for $\Delta R_{IB,c}$ due to SUL band combination (three bands)** + +| Band combination for SUL | $\Delta R_{IB,c}$ for NR bands / SUL band (dB)* | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------|--|--|--|--|--| +| | Component band in order of bands in configuration** | | | | | | +| CA nx SUL ny-nz | | | | | | | +| NOTE *: “-” denotes $\Delta R_{IB,c} = 0$ . | | | | | | | +| NOTE **: The component band order in the configuration should be listed by the order of NR bands and SUL band, such as for CA_n1_SUL_n78-n80 the band order from left to right is n1, n78 and n80. | | | | | | | + +### 5.2.4 New template for $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ tables for CA/DC + +For the UE which supports CA/DC configurations, the allowed maximum configured output power relaxation has been set for the inter-band or SUL operation as $\Delta T_{IB,c}$ . The allowed reference sensitivity relaxation has been set for the inter-band operation as $\Delta R_{IB,c}$ . However, with the explosive growth of the number of combinations, the $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ tables in the specifications are seriously oversized and the readability is deteriorated. To optimize the tables of $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ , a new template in Table 5.2.4-1 and Table 5.2.4-2 is proposed in Rel-18 respectively. + +**Table 5.2.4-1: New template for $\Delta T_{IB,c}$ tables in Rel-18** + +| Inter-band EN-DC configuration | $\Delta T_{IB,c}$ for E-UTRA band / NR band (dB) | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|-----|-----|-----|-----| +| | Component band in order of bands in configuration | | | | | +| DC 1-3-7-40 n78 | 0.6 | 0.6 | 0.5 | 0.3 | 0.8 | +| DC 1-3-8-11 n28 | 0.3 | 0.8 | 0.6 | 0.9 | 0.6 | +| ... | ... | ... | ... | ... | ... | +| Note 1: “-” denotes $\Delta T_{IB,c} = 0$ . | | | | | | +| Note 2: The component band order in the configuration should be listed by the order of E-UTRA band and NR band respectively, such as for DC_2-48_(n)5 the band order from left to right is 2, 5, 48 and n5. | | | | | | + +**Table 5.2.4-2: New template for $\Delta R_{IB,c}$ tables in Rel-18** + +| Inter-band EN-DC configuration | $\Delta R_{IB,c}$ for E-UTRA band / NR band (dB) | | | | | +|--------------------------------|---------------------------------------------------|--|--|--|--| +| | Component band in order of bands in configuration | | | | | + +| | | | | | | +|-----------------|-----|-----|-----|-----|-----| +| DC 1-3-7-40 n78 | 0.2 | 0.2 | - | 0.4 | 0.5 | +| DC 1-3-8-11 n28 | - | 0.3 | 0.2 | 0.5 | 0.2 | +| ... | ... | ... | ... | ... | ... | + +Note 1: "-" denotes $\Delta R_{IB,C} = 0$ . +Note 2: The component band order in the configuration should be listed by the order of E-UTRA band and NR band respectively, such as for DC\_2-48\_(n)5 the band order from left to right is 2, 5, 48 and n5. + +## 5.3 Fallback aspects for specifying band combinations + +For companies to propose the new band combinations in the band combination basket WIDs, some restrictions on the fallback aspects should be taken into account. The proponents should propose all the necessary fallback modes together with the proposed band combinations. To make the rules on fallback aspects common understanding in RAN4 and to facilitate delegates who are not very familiar with such rules when preparing the band combination proposals, the following text is suggested to be captured in the justification of each band combination basket WID. + +- *Request for additions of band combinations to this WI shall be provided using an agreed template and sent to the 3GPP\_TSG\_RAN\_WG4\_NR\_BANDS email reflector before a RAN4 Tdoc submission deadline and no new band combinations are allowed to be requested after the deadline except to correct the missing fallback and add more supporting companies for the proposed band combinations.* +- *When a proponent requests a new band combination, all the next level fallback configurations shall be listed and recorded in the request template and the status ("New", "Ongoing", "Completed") of all the fallback configurations shall be declared accurately and clearly. For "New" fallback configurations, the proponent shall ensure these fallback configurations are also requested together with the higher order band combination in the same meeting.* +- *A band combination configuration can only be considered as completed when all of the fallback configurations are completed and specified in advance or at the same meeting. It is the responsibility of the proponent to ensure the status of all of the fallback mode configurations. Rapporteurs and other companies are encouraged to check the status of all of the fallback configurations once the higher order band combinations are declared as completed.* + +(Note: 3GPP\_TSG\_RAN\_WG4\_CA is used for the LTE CA baskets WI) When the below approved rule is not followed by the proponents, TP/draft CR could be flagged by rapporteurs/ interested companies, and the TP/draft CR shall be noted if the lower order fallbacks are missing. + +- # Proponents should prepare and submit the corresponding contributions, e.g. draft CR, TP before RAN4#X meeting. +- # Proponents should clearly mention the following two conditions in the cover sheet of the draft CR or in the heading of the TP. + - 1) Whether there are pending lower order fallbacks submitted at the same meeting related to the combos in this draft CR/TP. (Yes with Tdoc numbers or No) + - 2) Whether there were lower order fallbacks approved in the last meeting related to the combos in this draft CR/TP, if the last meeting is a bis meeting. (Yes with Tdoc numbers or No) + +Examples for the cases when the last meeting is a bis meeting: + +- #1: The draft CRs/or TPs for the fallback combinations in the same meeting: R4-xxxxxxx. +There is no related lower order fallbacks in the last bis meeting. +- #2: There is no pending lower order fallbacks in the same meeting. +The draft CRs/or TPs for the fallback combinations in the last bis meeting: R4-xxxxxxx +- #3: There is no pending lower order fallbacks in the same meeting. +There is no related lower order fallbacks in the last bis meeting. +- #4: The draft CRs/or TPs for the fallback combinations in the same meeting: R4-xxxxxxx. +The draft CRs/or TPs for the fallback combinations in the last bis meeting: R4-xxxxxxx + +## 5.4 Submitting technical contributions (Tdoc) for specifying band combinations + +### 5.4.1 Text Proposal (TP) or Draft Change Request (draft CR) + +The R18 PC3 basket WID items were improved in RAN#96 meeting, including PC3 ENDC/NEDC, NR CA/DC, SUL and V2X basket WIDs, due to some of the R17 PC3 basket WID items are merged into one R18 PC3 basket WID, and also the table templates When providing technical contributions for the inclusion of a band combination there are two possible approaches. + +- 1) Text Proposal (TP) to a Technical Report (TR) for the specific basket Work Item (WI). +- 2) Draft Change Request (draft CR) to the Technical Specification (TS) + +RAN4 have agreed that if there is a need for any technical study/analysis as UE coexistence studies potentially resulting in relaxations needed defined this needs to be provided via a TP to a TR such that this study/analysis is captured in the TR. For new band combinations which does not require any technical study/analysis RAN4 has agreed to introduce these via draft CR directly to the TS. It shall be noted that not all the basket WIs have a TR indicating for which technical study/analysis may be needed and for which there is no need. + +### 5.4.2 Specific for Text Proposal (TP) + +TPs shall be drafted using the latest version of the corresponding TR as baseline and if included to the TR the provided template in the TR. All additions intended to be captured to the TR shall be marked with change-marks. + +Sourcing company/companies are encouraged to combine all related band combinations to a single Tdoc for the TR containing one or more TPs with the needed technical analysis. + +### 5.4.3 Specific for Draft Change Request (draft CR) + +Draft CRs shall be drafted using the latest version of the corresponding TS as baseline. All additions intended to be captured to the TR shall be marked with change-marks. + +Sourcing company/companies shall provide a single draft CR per basket WI corresponding to an individual agenda item at the RAN4 meetings. Noting that if a company is working with multiple other companies for providing technical input (draft CRs) for the same type of combinations (i.e. basket WI) each different group of sourcing companies shall be allowed to submit individual Tdocs. It shall also be noted that if different types of draftCRs are needed (e.g. Cat.B and Cat.F) a single draftCR per type is allowed. + +### 5.4.4 Which agenda to submit the Tdoc for + +The TP or draft CR shall be submitted to the agenda corresponding to the basket WI for which the specific band combination belongs (i.e. is included in the WID). Attention shall be made to which type of combinations it is under the basket if there are different sub-agendas for e.g. with or without FR2 parts of the combination. + +Exceptions for submitting to the agenda corresponding to the basket WI is agreed by RAN in WF [9] and listed below. + +- 1) Intra-band CA or DC (intra-band UL related MSD or band protection) +- 2) 2 band inter-band CA or DC (intra-band UL CA IMD related MSD, LB-LB cases) +- 3) 3 band inter-band CA or DC (intra-band UL CA triple beat related MSD, LB-LB-LB cases) + +In case of any of the exceptions above the TP or draft CR shall be submitted to the “not for block approval” agenda. + +# --- 6 Guidelines of specifying band combinations + +## 6.1 General + +The notation of the band combinations in the 38.101 specifications as well as the combination request lists by the operators and the basket WIDs can have significant impact, as it can become unclear what combination is really meant + +in the request or specification in cases of errors. Then the combination may be misinterpreted, not taken into account when implementing combinations in BS or UEs or even removed from specs or requests. Also automated processing of the tables will become difficult with too many bugs. + +Generally the notation of band combinations starts with the type of the configuration (mainly CA or DC), followed by one list (either LTE or NR) or two lists (first LTE, then NR) of bands with bandwidths. The following types of band combinations are defined in 3GPP specifications: + +Carrier Aggregation: Starts with “CA\_” as the first three characters. Then either a list of LTE or NR carriers is following, where the carriers or bands are always separated by “-”. LTE and NR carriers cannot be combined, that would be a DC combination. Examples: + +- CA\_1A-2A (LTE) +- CA\_n1A-n2A (NR) +- Examples for wrong notations: CA\_1A\_2A (“\_” instead of “-” between the carriers/bands), CA-1A-2A (no “\_” but “-” after “CA”), CA\_1A\_n2A (this would need to be a DC combination) +- NOTE: LTE examples are provided for information only + +Dual Connectivity: Starts with “DC\_” as the first three characters, then for EN-DC configurations followed by the list of LTE carriers, a “\_” as separation between the LTE and NR carriers and then the list of NR carriers. For NE-DC configurations the list begins with NR carriers, a “\_” as separation between the NR and LTE carriers, and then the list of LTE carriers. There are exceptions for SUL EN-DC combinations, which separate the LTE and NR carriers by “\_SUL\_” instead of “\_”, and contiguous intra-band EN-DC combinations using “(n)” instead of “\_” and the “n” of the first NR band in the list. DC configurations within LTE or NR just list the carriers after “DC\_”. For EN-DC combinations for V2X the “DC\_” at the beginning is replaced by “V2X\_”, even if it is still an EN-DC combination. Examples: + +- DC\_1A\_n2A (EN-DC) +- DC\_1A-2A (LTE-DC) +- DC\_n1A-n2A (NR-DC) +- DC\_(n)1AA (EN-DC with contiguous intra-band LTE and NR carriers) +- DC\_1(n)AA (NE-DC with contiguous intra-band NR and LTE carriers) +- DC\_1A-(n)2AA (EN-DC with one LTE carrier followed by contiguous intra-band LTE and NR carriers) +- DC\_2(n)AA-1A (NE-DC with one LTE carrier followed by contiguous intra-band NR and LTE carriers) +- DC\_n78A\_1A-3A (NE-DC) +- Examples for wrong notations: DC\_1A-n2A (“-” instead of “\_” between the LTE and NR carriers/bands for EN-DC combinations), DC-1A-2A (no “\_” but “-” after “DC”), DC\_n1A\_n2A (“\_” instead of “-” between the NR carriers/bands for NR-DC combinations) + +Supplementary UL: NR SA configurations start with “SUL\_” as the first four characters for SUL band combination with single carrier, as it is only NR without LTE, if it is within an EN-DC combination there is a “\_SUL\_” between the LTE and the NR part instead of the “\_SUL\_” at the beginning, using the usual “DC\_” as the first characters. For uplink EN-DC configuration, if TDM operation of uplink sharing from UE perspective (ULSUP) is chosen, the notation of “\_ULSUP-TDM\_” is used. The FDM operation of uplink sharing from UE perspective is not supported in current specifications. If SUL band combination with intra-band contiguous CA, intra-band non-contiguous CA or inter-band CA, the notation starts with “CA\_” as the first three characters. Examples: + +- SUL\_n2A-n80A (n80 being the SUL band) +- CA\_n41C-n80A (n80 being the SUL band) +- CA\_n78(2A)-n86A (n86 being the SUL band) +- CA\_n1A\_n78A-n81A (n81 being the SUL band) + +- DC\_1A\_SUL\_n2A-n80A (n80 being the SUL band) +- DC\_3A\_n80A\_ULSUP-TDM\_n78A (TDM operation on SUL\_n78-n80) + +In summary the following types and notations are defined: + +- CA\_ ...: A Carrier Aggregation configuration followed by the list of either LTE or NR carriers, or SUL band combination with NR intra-band contiguous, non-contiguous or inter-band CA carriers. +- DC\_ ...: A Dual Connectivity configuration followed by the list of either LTE carriers for LTE-DC or NR carriers for NR-DC or for EN-DC first LTE carriers, then “\_” and the NR carriers or for NE-DC first NR carriers, then “\_” and the LTE carriers. In case of a DC combination for V2X, the “DC\_” is replaced with “V2X\_”. +- SUL\_ ...: A Carrier Aggregation configuration including one SUL band followed by a single NR carrier. In case of a DC configuration with SUL, the “SUL\_” is shifted behind the “\_” separating the LTE and NR carriers and the configuration starts with “DC\_” as usual for DC configurations. In case of an uplink EN-DC configuration with SUL, “\_ULSUP-TDM\_” is applied for TDM operation for uplink sharing from UE perspective. + +## 6.1A Notation of lists of bands and bandwidths within a configuration + +### 6.1A.1 Band numbers + +A list of LTE or NR carriers within a CA or DC configuration is either a single or multiple LTE or NR carriers. The simplest one is just a single carrier. It consists of the band number followed by the bandwidth class, which is “A” for a single carrier. For LTE the band number is just the number of the band, for NR carriers the numerical part of the band notation is preceded by an “n”, indicating this is a NR band, not a LTE band. NR bands above n256 are FR2 bands, below n256 are FR1 bands. The band number is always followed by the bandwidth class, which can be quite complicated for NR combinations with intra-band CA. Bandwidth classes other than “A” indicate multiple carriers in that band. In the list there can be multiple entries for inter-band CA configurations (in LTE also intra-band non-contiguous CA), which are always separated by “-”. The band numbers are sorted in increasing numbers. LTE and NR bands in the same frequency range usually have the same band number. Examples: + +- Notation of a single LTE carrier: 1A, 2A, 3A etc. +- Notation of a single NR carrier: n1A, n2A, n3A etc. +- List of multiple LTE carriers on different bands: 1A-2A-3A. +- List of multiple NR carriers on different bands: n1A-n2A-n3A. + +### 6.1A.2 Bandwidth classes + +##### 6.1A.2.1 Bandwidth classes for LTE + +An entry within the list of carriers always starts with the band number followed by the bandwidth class. In LTE the bandwidth classes (if not “A”) mean this is a contiguous CA configuration with multiple carriers. They are specified in table 5.6A-1 in 36.101 and can range from “A” for a single carrier up to F for 5 carriers. BW class I is specified for 8 carriers, but is not used. Non-contiguous CA combinations are just listing multiple sub-blocks separated by “-”. Examples: + +- CA\_1B: Two contiguously aggregated LTE carriers with 20MHz or less in band 1. +- CA\_2F: Five contiguously aggregated LTE carriers with up to 100MHz in band 2. +- CA\_3A-3A: Two non-contiguously aggregated LTE carriers in band 3 +- CA\_4A-4E: A single carrier followed by a gap and then followed by four contiguously aggregated carriers with up to 80MHz +- A single carrier is no CA configuration as there is nothing aggregated, so there is no CA\_5A, this is just 5A. + +##### 6.1A.2.2 Bandwidth classes for NR + +NR bandwidth classes are much more complicated. Also here an entry within the list of carriers always starts with the band number followed by the bandwidth class. But in NR the bandwidth class includes contiguous and non-contiguous CA and a mixture of contiguous and non-contiguous CA. For contiguous CA the bandwidth classes are specified similar to LTE, but separate for FR1 and FR2. For FR1 contiguous CA BW classes are specified in table 5.3A.5-1 in 38.101-1 ranging from A to O (F is not used), in which the classes M, N and O are applicable for the use with shared spectrum channel access. For FR2 in 5.3A.4-1 in 38.101-2 ranging from A to W(N is not used), and R2 to R12, in which the classes V and W are applicable only for FR2-2 operating bands. The CA bandwidth classes for NR are categorized into different fallback groups (FBG). It is mandatory for a UE to be able to fallback to lower order NR CA bandwidth class configuration within a FBG, and not mandatory for a UE to be able to fallback to lower order NR CA bandwidth class configuration that belong to a different FBG. + +A special kind or BW class specification is when there are intra-band contiguous LTE and NR carriers within an EN-DC combination like DC\_(n)1AA. In this case the LTE and NR carriers within that band are combined to a single entry of the list of carriers starting with (n) indicating that it can be “n” for the NR carrier, or no “n” for the LTE carrier. This is followed by the numerical value of the band (here “1”) and then the contiguous BW class for the LTE part and the contiguous BW class for the NR part. So DC\_(n)1AA means that there is a single carrier for LTE and a single carrier for NR side-by-side contiguously aggregated in band 1. This can be extended by more contiguous carriers on the LTE or NR side or both, for example DC\_(n)41DA means three contiguous carriers for LTE besides a single carrier for NR. This can be extended by other LTE carriers in front of the combination of carriers with (n) or with other NR carriers behind the (n) part, for example DC\_1A-(n)2AA or DC\_(n)2AA-n3A. The (n) part is considered as the last LTE combination in the list or the first NR combination in the list, therefore adding it with a “-” instead of a “.”. For intra-band contiguous NE-DC configuration, instead of (n)X in EN-DC, the notation X(n) is used. In this case, DC\_X(n)yz indicates the contiguous NR Band carriers with channel bandwidth class y in Band nX is followed by the contiguous LTE carries with channel bandwidth z in Band X. For example, DC\_3(n)AA denotes the NE-DC combination of single carrier for NR in Band n3 and single carrier for LTE in Band 3. + +However, the BW class part of a NR configuration also includes non-contiguous intra-band CA. For a combination containing any non-contiguous CA, i.e. a gap between any aggregated carriers, each block of single or contiguously aggregated carriers is called a sub-block, where a sub-block can also consist of the contiguously aggregated carriers as stated above. While in LTE single non-contiguously aggregated carriers are just duplicated like CA\_1A-1A, in NR the number of non-contiguous carriers of a BW class is counted and put in parenthesis with the number of sub-blocks of this type preceding the bandwidth class. Therefore a configuration with two non-contiguous carriers will have a BW class (2A) in NR, so the combination will be named CA\_n1(2A), meaning there are two non-contiguous carriers with BW class A in band n1. + +However, there can also be the combination of contiguous and non-contiguous intra-band CA in NR. In this case the sub-blocks of each BW class are separately counted and added within the brackets. For example if there are in a n260 FR2 CA combination two sub-blocks of BW class “A” (single carriers), three of BW class “G” (two contiguous carriers up to 100MHz) and one of BW class O (two carriers with 50 or 100MHz), the full combination will be named CA\_n260(2A-3G-Q), having 6 sub-blocks with in total 10 carriers. Examples: + +- CA\_n1B: Two contiguously aggregated NR carriers with 100MHz or less in band n1 (FR1). +- CA\_n2D: Three contiguously aggregated NR carriers with up to 300MHz in band n2. +- CA\_n3(2A): Two non-contiguously aggregated NR carriers in band n3 +- CA\_n260G: Two contiguously aggregated NR carriers with 150 or 200MHz in band n260 (FR2). +- CA\_n260M: Eight contiguously aggregated NR carriers with 750 or 800MHz in band n260 (FR2). +- CA\_n260(2A): Two non-contiguously aggregated NR carriers in band n260 with up to 800MHz (2x400MHz) +- CA\_n260(A-M): A single carrier followed by a gap and then followed by eight contiguously aggregated carriers with up to 100MHz each +- CA\_n260(2A-3G-Q): Two single carriers up to 400MHz each, three sub-blocks with two carriers each of 150 or 200MHz per sub-block followed by another sub-block with two carriers of 50 or 100MHz each. + +## 6.1B Rules to be used for the notation of CA or DC configurations + +The following are the rules for generating the configuration notations: + +- Each configuration needs to start with “CA\_”, “DC\_”, “SUL\_” or “V2X\_”. +- DC combinations include a list of LTE carriers first, followed by the list of NR carriers. +- Entries within a list of either LTE carriers or NR carriers need to be separated by “-”, not “\_”. +- The list of LTE carriers and the list of NR carriers within an EN\_DC combination need to be separated by “\_”, for contiguous intra-band EN-DC the two lists are connected with the (n)xxAA like notation, not “\_” (xx is the band number), for contiguous intra-band NE-DC the two lists are connected with the xx(n)AA like notation, not “\_” (xx is the band number). In specific cases “\_SUL\_” connects the two lists. +- Contiguous LTE+NR intra-band carriers within a DC combination are using the notation (n)xxAA (xx is the band number), Contiguous NR+LTE intra-band carriers within a DC combination are using the notation xx(n)AA (xx is the band number). +- No other characters than “A” to “Z”, “0” to “9”, “(”, “)”, “-”, “\_” and “n” are allowed within the notation, especially no spaces “ ”, “/”, “.”, LineFeed, CR, other special characters. +- Entries within the list of carriers need to be sorted in numerical order, i.e. first band n1, then n2, then n3, then n260, i.e. CA\_1A-2A, not CA\_2A-1A, but LTE and NR combinations are separately sorted, i.e. DC\_2A\_n1A, entries with (n) are always between the LTE and NR lists. +- Bandwidth notations are either a single character according to the BW class lists of contiguously aggregated carriers, two of these characters in case of combinations with (n) or for NR non-contiguous intra-band combinations specific expressions listing multiple carriers within “()”. +- Within the “()” of non-contiguous NR combinations there will only be BW class letters for the BW class of contiguous sub-blocks preceded by a number indicating the number of sub-blocks of this BW class, if there are multiple different BW classes they are listed in ascending BW class order separated by “-”. + +Examples of correct notations are as follows: + +- DC\_1A-2A\_n260(A-M) +- DC\_1A-2A-2A-2A\_n3(3A) +- DC\_1A-(n)2AA-n3A +- DC\_1A-2A-3A-4A-5A\_n6A-n260(2A-3G-Q) +- Some incorrect examples we have seen: DC\_1A-2A\_n3A(3A) (no “A” before the bracket); DC\_2A-1A\_n3(3A) (wrong sort order of LTE bands); DC\_1A- 2A\_n260(A-M) (a “ ” (space) between the “-“ and the “2”); DC\_1A-2A\_n260A/G/H/I/J/K/L/M (no “/” allowed within a configuration, multiple configurations not allowed within the notation, use separate configuration notations for each configuration). + +Currently this notation for the CA/DC configurations is used as specified in 36.101 for LTE and 38.101 for NR. However, multiple errors within the specifications have been observed, which motivate the need to define the following rules how to handle the CA/DC configurations in the -101 specs. Below are the general rules how to implement these band combinations within the CA/DC configurations within the tables in clause 5.5: + +- Each cell of the configuration table should contain only one combination of bands in the first column with the exception that combinations having the same bands but different intra-band contiguous BW classes can be listed in the same cell. Also all non-contiguous combinations can be listed in one cell, but separated from the contiguous combinations in another cell. +- In the UL column there shall only be UL configurations that belong to the configurations in the first column. Unfortunately this means that in the UL column there can be higher order configurations than some of the configurations in the first column, however, they cannot be used with such a lower order combination. This was agreed some time ago as a “table simplification”, but creates some hassle as there are UL combinations listed that cannot be supported with the DLs. + +- Multiple configurations with different bandwidth classes shall be separated by pressing the return key, you will see the ¶ sign at the end of the line if you activated the button to view these special characters, no other special characters to separate configuration shall be used. +- There shall be no special characters not belonging to the combinations in any configuration cell, no spaces “ ”, “/”, “.”, or any other special characters. +- If there are notes for a specific configuration, the note shall be using superscript font and added at the end of the configuration list within a cell, not anywhere within the configuration or separated with any other characters, multiple notes shall be separated just by a comma, all in superscript. + +## 6.1C Adding or removing channel BW's in NR CA configurations + +### 6.1C.1 Adding channel BW's in NR CA configurations + +If it is discovered that it was forgotten to define a channel bandwidth when defining a band combination, the correct way is to define a new BCS row for that band combination. Such a definition of a new BCS follows the normally procedures of definitions of new BCS's. + +Preferably no exceptions should be made to the rule above. Exception can only be if all UE vendors can confirm that ... + +- a) no existing UE advertises the affected channel bandwidth (in the channel-BW bitmap) or the affected band combination (in the supportedBandCombinationList), or +- b) all existing UEs that advertise the affected channel bandwidth and the band combination support and accept the configuration of that channel bandwidth in that BC. + +The rule to follow by CR-authors and basket WI rapporteurs: + +- If a channel bandwidth is added to an existing bandwidth combination set and if this channel bandwidth was already defined in Table 5.3.5-1 (“Channel bandwidths for each NR band”) in a previous version of the specification: + - *The change is non-backwards-compatible and needs to be documented on the CR cover page with the wording “The addition of the channel bandwidth XXX to BCS#Y of band combination ABC is intentional and potential non-backwards compatible (NBC) impact have been considered.* + +#### 6.1C.2 Removing channel BW's in NR CA configurations + +##### 6.1C.2.1 Removing of not possible channel BW's + +If it is discovered that a channel bandwidth in a band combination set is defined for a band that is not defined in Table 5.3.5-1 (“Channel bandwidths for each NR band”) it needs to be removed. Such a removal is not a non-backward compatible change. This is a correction of an inconsistency in the specification. + +##### 6.1C.2.2 Removing of possible channel BW's + +If it is discovered that a channel bandwidth was mistakenly included when defining the band combination, the correct way is to define a new BCS row in that band combination. Such a definition of a new BCS follows the normally procedures of definitions of new BCS's. + +Preferably no exceptions should be made to that rule. Exception can only be if all UE vendors can confirm that ... + +- a) no existing UE advertises the affected channel bandwidth (in the channel-BW bitmap) or the affected band combination (in the supportedBandCombinationList). + +The rule to follow by CR-authors and basket WI rapporteurs: + +- If a channel bandwidth is removed from an existing bandwidth combination set and if this channel bandwidth was already defined in Table 5.3.5-1 (“Channel bandwidths for each NR band”) in a previous version of the specification: + +- *The change is non-backwards-compatible and needs to be documented on the CR cover page with the wording* "The removal of the channel bandwidth XXX to BCS#Y of band combination ABC is intentional and potential non-backwards compatible (NBC) impact have been considered." + +## 6.2 Guidelines on band combination fallbacks + +### 6.2.1 General definition of fallbacks + +In the 36.101 and 38.101 specs thousands of band combinations for LTE, EN-DC, NR-DC... are specified having at least two carriers, but in most cases many more than two carriers. There are already many rules and definitions for these configurations. + +Definitions: + +- A fallback DC, CA or SUL configuration is a configuration, where one of the carriers of the higher order configuration is removed. +- A mandatory fallback is a fallback that is mandatory to be specified in the UE specification and supported by the UE. +- A Fallback Group is specified for contiguous CA, only fallback configurations within the same fallback group need to be supported. + +Explanations and rules: + +- A higher order configuration has generally the same number of fallbacks as it has carriers, i.e. a configuration with 4 carriers has 4 next level fallbacks. +- Example: CA\_n1A-n2A-n3A-n4A has the 4 next level fallbacks CA\_n2A-n3A-n4A, CA\_n1A-n3A-n4A, CA\_n1A-n2A-n4A, CA\_n1A-n2A-n3A, where the first, the second, the third and the fourth carrier have been removed. +- For intra-band CA some of the fallbacks are identical, so that the number of unique fallbacks can be lower than the number of carriers. For contiguous intra-band CA there is only one unique fallback, for non-contiguous intra-band CA as well. For contiguous intra-band configurations removing one of the middle carriers would not result in a valid fallback, since this would transform the contiguous configuration to a non-contiguous configuration. But for the combination of contiguous and non-contiguous intra-band CA there will usually be more than one unique fallback left. +- Example: CA\_n1(3A) would have three fallbacks, where the first, the second or the third carrier would be removed, but in all three cases the resulting fallback is the same: CA\_n1(2A), so we only have one unique fallback configuration left out of the three. +- Example: CA\_n1D would have three fallbacks, where the first, the second or the third carrier would be removed, but in all three cases the resulting fallback is the same: CA\_n1C, so we only have one unique fallback configuration left out of the three. Additionally removing the middle carrier doesn't result in a valid fallback, since it would change the contiguous configuration to a non-contiguous one. +- Example: CA\_n265R12 would have twelve fallbacks, where the first, the second ... twelfth carrier would be removed, but in all twelve cases the resulting fallback is the same: CA\_n265R11, so we only have one unique fallback configuration left out of the twelve. Also here removing one of the middle carrier doesn't result in a valid fallback, since it would change the contiguous configuration to a non-contiguous one. +- Example: CA\_n1(A-C) would have three fallbacks, where the first, the second or the third carrier would be removed, this would result in CA\_n1C, CA\_n1(2A), CA\_n1(2A) as fallbacks, where the last two are duplicates, so in this case we have two unique fallback configurations left out of the three: CA\_n1C and CA\_n1(2A). +- For intra-band contiguous CA we have to follow the fallback groups. Only fallbacks within this group can be used, BW classes outside the fallback group are no legal fallbacks. +- Example: CA\_n1D falls back to CA\_n1C. +- Example: CA\_n1C falls back to CA\_n1A, BUT NOT to CA\_n1B, since this is in a different fallback group. + +- Example: CA\_n265I (FR2) falls back to CA\_n265H, this falls back to CA\_n265G, this falls back to CA\_n265A, NOT to CA\_n265F. +- For combined contiguous and non-contiguous intra-band CA, which is mainly used for FR2, there will be many fallbacks, especially when there is a large number of carriers, but also there some fallbacks after removing a carrier may be duplicates. +- Example: CA\_n265(A-G-H), removing the “A” carrier results in CA\_n265(G-H), removing one of the “G” carriers results in CA\_n265(A-A-H), which will be correctly written as CA\_n265(2A-H), removing one of the “H” carrier will result in CA\_n265(A-G-G), which will be correctly written as CA\_n265(A-2G), so we get three unique configurations out of these six carriers. + +### 6.2.2 Mandatory Fallbacks + +In general all fallbacks need to be specified and supported until we end up at a single carrier. So it is necessary to generate a fallback tree starting at the configuration with the highest number of carriers down to a single carrier. + +- A configuration has as many fallback levels as the highest order combination has carriers. For example a four carrier combination will have four three carrier fallbacks, each of these has three two carrier fallbacks, each of these would end up in single carriers. However, in this chain there will again be some duplicates. + +Example: CA\_n1A-n2A-n3A-n4An has these fallbacks: + +- CA\_n2A-n3A-n4A, CA\_n1A-n3A-n4A, CA\_n1A-n2A-n4A, CA\_n1A-n2A-n3A. + +These four combinations have these two carrier fallbacks (colors as above): + +- CA\_n3A-n4A, CA\_n2A-n4A, CA\_n2A-n3A, CA\_n3A-n4A, CA\_n1A-n4A, CA\_n1A-n3A, CA\_n2A-n4A, CA\_n1A-n4A, CA\_n1A-n2A, CA\_n2A-n3A, CA\_n1A-n3A, CA\_n1A-n2A. + +As we see there are several duplicates, removing these we end up with these second level fallbacks: + +- CA\_n3A-n4A, CA\_n2A-n4A, CA\_n2A-n3A, CA\_n1A-n4A, CA\_n1A-n3A, CA\_n1A-n2A. +- All of these end up in 4 single carriers of n1A, n2A, n3A and n4A. +- This is a recursive action, we first have to check the next lower level fallbacks, then take these as the basis for the next lower level and so on, until we end up with single carriers. +- All fallbacks for these DC, CA or SUL combinations are mandatory to be supported, as long as the corresponding UL is supported as well. + +One relatively simple example of such a combination is DC\_2A\_n261(H-I). But already this simple example generates a fallback tree with 12 fallbacks when going from 8 carriers to a single dual carrier DC combination. This is shown in figure 6.2.2-1: + +![Figure 6.2.2-1: Fallback tree for DC_2A_n261(H-I). The diagram shows a hierarchical tree of fallback paths. The root node is DC_2A_n261(H-I). It branches into two main paths: DC_2A_n261(G-I) and DC_2A_n261(H-H) = DC_2A_n261(2H). The DC_2A_n261(G-I) path branches into DC_2A_n261(A-I) and DC_2A_n261(G-H). The DC_2A_n261(A-I) path branches into DC_2A_n261I and DC_2A_n261(A-H). The DC_2A_n261(G-H) path branches into DC_2A_n261(G-G) = DC_2A_n261(2G). The DC_2A_n261I path branches into DC_2A_n261H and DC_2A_n261G. The DC_2A_n261(A-H) path branches into DC_2A_n261(A-G) and DC_2A_n261(A-A) = DC_2A_n261(2A). The DC_2A_n261H path branches into DC_2A_n261G and DC_2A_n261A. The DC_2A_n261G path branches into DC_2A_n261A. The DC_2A_n261(A-G) path branches into DC_2A_n261A. The DC_2A_n261(2G) path branches into DC_2A_n261A. The DC_2A_n261(2A) path branches into DC_2A_n261A. A long red curved arrow at the top indicates the overall transition from the root to the final single carrier state.](f7d969388c4f7e30cd04a061314bfa0e_img.jpg) + +Figure 6.2.2-1: Fallback tree for DC\_2A\_n261(H-I). The diagram shows a hierarchical tree of fallback paths. The root node is DC\_2A\_n261(H-I). It branches into two main paths: DC\_2A\_n261(G-I) and DC\_2A\_n261(H-H) = DC\_2A\_n261(2H). The DC\_2A\_n261(G-I) path branches into DC\_2A\_n261(A-I) and DC\_2A\_n261(G-H). The DC\_2A\_n261(A-I) path branches into DC\_2A\_n261I and DC\_2A\_n261(A-H). The DC\_2A\_n261(G-H) path branches into DC\_2A\_n261(G-G) = DC\_2A\_n261(2G). The DC\_2A\_n261I path branches into DC\_2A\_n261H and DC\_2A\_n261G. The DC\_2A\_n261(A-H) path branches into DC\_2A\_n261(A-G) and DC\_2A\_n261(A-A) = DC\_2A\_n261(2A). The DC\_2A\_n261H path branches into DC\_2A\_n261G and DC\_2A\_n261A. The DC\_2A\_n261G path branches into DC\_2A\_n261A. The DC\_2A\_n261(A-G) path branches into DC\_2A\_n261A. The DC\_2A\_n261(2G) path branches into DC\_2A\_n261A. The DC\_2A\_n261(2A) path branches into DC\_2A\_n261A. A long red curved arrow at the top indicates the overall transition from the root to the final single carrier state. + +Figure 6.2.2-1: Fallback tree for DC\_2A\_n261(H-I) + +There are much more complicated CA combinations that will create many more combinations like CA\_n260(2A-2O-Q) and there are many of these combinations. For CA\_n260(2A-2O-Q) for example there is a fallback tree with 46 unique fallback combinations (all duplicates already removed). This combination is already in 38.101, however, most of these fallbacks were initially missing and added later. + +All of these fallbacks have to be specified in 38.101 specs and need to be supported by the UE. + +### 6.2.3 Fallbacks of EN-DC Configurations + +In 38.101-3 we find this general rule on fallbacks for EN-DC combinations: + +*“A terminal which supports an inter-band EN-DC configuration with a certain UL configuration shall support the all lower order DL configurations of the lower order EN-DC combinations, which have this certain UL configuration and the fallbacks of this UL configuration.”* + +Of course this means that we have to support all fallbacks for which this rule is fulfilled. + +This rule is a restriction of the general rule that all fallbacks need to be supported. The reason is that there can be combinations, for which the UL is not supported, of course when there is no UL, also the DL combination doesn't make sense anymore. + +- Assumption: DC\_1A-2A\_n3A is the DL configuration and DC\_1A\_n3A is supported as the UL. + - DC\_1A-2A\_n3A as DL configuration has DC\_1A\_n3A, DC\_2A\_n3A as next level fallbacks. + - The fallback DC\_1A\_n3A has the same UL DC\_1A\_n3A as the higher order combination, therefore this fallback is mandatory to be supported. + - The fallback DC\_2A\_n3A would need DC\_2A\_n3A as the UL, but only DC\_1A\_n3A is supported for the UL of the higher order combination, therefore this fallback is not mandatory to be supported. + +Fallbacks from EN-DC to E-UTRA only or NR only configurations need to be supported as well. For example if we have a configuration DC\_1A-2A-3A\_n4A-n5A of course the constituent LTE combination CA\_1A-2A-3A as well as NR CA\_n4A-n5A need to be specified in 36.101 and 38.101 respectively and it is mandatory to support them, since the EN-DC combination is based on them. + +### 6.2.4 Fallbacks of UL Configurations + +Of course fallbacks of UL configurations need to be specified and supported as well. + +- All fallbacks of UL configurations with higher order need to be supported down to a single carrier. +- Example: UL CA\_n265M needs these UL fallbacks: CA\_n265L, CA\_n265K, CA\_n265J, CA\_n265I, CA\_n265H, CA\_n265G, n265A. +- Example: UL EN-DC DC\_1A\_n265M needs these UL fallbacks: DC\_1A\_n265L, DC\_1A\_n265K, DC\_1A\_n265J, DC\_1A\_n265I, DC\_1A\_n265H, DC\_1A\_n265G, DC\_1A\_n265A. + +Generally there is the rule that UL configurations can only have the same, or less carriers that are part of the DL configuration, as an example it is not allowed to have an UL configuration DC\_1A\_n265M for a DL configuration DC\_1A\_n265H. + +### 6.2.5 Fallback rules for some exceptional cases + +For some band combinations which include SDL bands (e.g. band n75) and/or only DL Scell bands (band combinations including band n7/7 and band n38/38 together), some fallback band combinations which can't be deployed in reality can't be considered as fallbacks. + +For example: + +- DC\_1A\_n75A-n78A: fallback is DC\_1A\_n78A. And DC\_1A\_n75A which can't be deployed in reality can't be considered as fallbacks. All fallbacks of UL configurations with higher order need to be supported down to a single carrier. +- DC\_1A-7A\_n38A-n78A: fallbacks are DC\_1A-7A\_n78A and DC\_1A\_n38A-n78A. DC\_1A-7A\_n38A and DC\_7A\_n38A-78A which can't be deployed in reality can't be considered as fallbacks. +- DL CA\_n1A-n7A-n38A: fallbacks are DL CA\_n1A-n7A and DL CA\_n1A-n38A. DL CA\_n7A-n38A which can't be deployed in reality can't be considered as fallbacks. + +Generally, this special principle can be summarized as below. For a band combinations, if one RAT (LTE part or NR part) of this BC only include SDL band(s) and/or only DL Scell band(s), this BC which can't be deployed in reality can't be considered as fallbacks. + +### 6.2.6 Guidelines on valid CBW for higher order BC depending on fallbacks + +In current RAN4 specifications, for traditional BCS, some new CBWs such as 35MHz/45MHz were added in the higher order combinations but not yet introduced in the corresponding fallback lower order combinations. It results in the inconsistencies and leads some extra maintenance work to remove the CBWs in the higher order combinations that are missing in the lower fallbacks for traditional BCS. The following guidelines on valid CBW for new higher order BC request in traditional BCS from Rel-18 are to be supported. Note that for BCS4 and 5, the guideline does not apply. + +- The per band supported channel bandwidths in a new higher order band combination from Rel-18 with traditional BCS should be a subset of or equal to channel bandwidths supported for the same band in at least one of the corresponding lower order band combination of the BCS. +- Band combination with the supported per channel bandwidths not meeting the above guidance should not be requested. + +## 6.3 Guidelines on delta $T_{IB}$ and $R_{IB}$ due to band combinations + +To optimize the tables of $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ due to band combinations, a new template for Rel-18 is proposed in clause 8.3.2 in TR 38.862. + +Regarding to the optimized template for $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ tables, only the configurations having the same component E-UTRA / NR bands can be grouped into one cell (row). For example, in Table 6.3-1 for the $\Delta T_{IB,c}$ of the following inter-band EN-DC configurations, since the component bands are not the same, two rows should be filled separately in the new template. However, for the configurations “DC\_3-7-8\_n1-n78”, “DC\_3-3-7-8\_n1-n78”, “DC\_3-7-7-8\_n1-n78” and “DC\_3-3-7-7-8\_n1-n78” having the same component bands, they should be merged into one cell. + +**Table 6.3-1: Example for $\Delta T_{IB,c}$ for Inter-band EN-DC configurations** + +| Inter-band EN-DC configuration | E-UTRA or NR Band | $\Delta T_{IB,c}$ (dB) | +|--------------------------------|-------------------|------------------------| +| DC_3-7-8_n1-n78 | 3 | 0.6 | +| DC_3-3-7-8_n1-n78 | | | +| DC_3-7-7-8_n1-n78 | | | +| DC_3-3-7-7-8_n1-n78 | | | +| DC_3-7_n1-n8-n78 | | | +| DC_3-3-7_n1-n8-n78 | | | +| DC_3-7-7_n1-n8-n78 | | | +| DC_3-3-7-7_n1-n8-n78 | | | +| | 7 | 0.6 | +| | 8 or n8 | 0.6 | +| | n1 | 0.6 | +| | n78 | 0.8 | + +| Inter-band EN-DC configuration | $\Delta T_{IB,c}$ for E-UTRA band / NR band (dB) 6 | | | | | +|--------------------------------|----------------------------------------------------------------|-----|-----|-----|-----| +| | Component band in order of bands in configuration 7 | | | | | +| DC_3-7-8_n1-n78 | 0.6 | 0.6 | 0.6 | 0.6 | 0.8 | +| DC_3-3-7-8_n1-n78 | | | | | | +| DC_3-7-7-8_n1-n78 | | | | | | +| DC_3-3-7-7-8_n1-n78 | | | | | | +| DC_3-7_n1-n8-n78 | 0.6 | 0.6 | 0.6 | 0.6 | 0.8 | +| DC_3-3-7_n1-n8-n78 | | | | | | +| DC_3-7-7_n1-n8-n78 | | | | | | +| DC_3-3-7-7_n1-n8-n78 | | | | | | + +**Guideline 1: It is supposed that only the configurations having the same component E-UTRA / NR bands can be grouped into one cell (row) for the new $\Delta T_{IB,c}$ and $\Delta R_{IB,c}$ templates.** + +With regard to the values for a band combination in the $\Delta T_{IB,c}$ / $\Delta R_{IB,c}$ table, considering that a statement of ‘Unless otherwise stated, $\Delta T_{IB,c}$ / $\Delta R_{IB,c}$ is set to zero’ having been specified in the general part of specification, it is reasonable to remove the combination in the $\Delta T_{IB,c}$ / $\Delta R_{IB,c}$ table with all component band having the value of ‘-’ (zero). For example in the following $\Delta R_{IB,c}$ Table 6.3-2, the CA combinations CA\_n1-n3-n5, CA\_n1-n3-n18 and CA\_n1-n3-n20 do not need to be listed in the table. + +**Table 6.3-2: Example for $\Delta R_{IB,c}$ for Inter-band CA configurations** + +| Inter-band CA combination | $\Delta R_{IB,c}$ for NR bands (dB) 9 | | | +|---------------------------|-----------------------------------------------------------------|-----|-----| +| | Component band in order of bands in configuration 10 | | | +| CA_n1-n3-n5 | - | - | - | +| CA_n1-n3-n8 | 0.2 | 0.2 | 0.5 | +| CA_n1-n3-n18 | - | - | - | +| CA_n1-n3-n20 | - | - | - | + +**Guideline 2: For the band combination with all the component bands having the $\Delta T_{IB,c} / \Delta R_{IB,c}$ values as ‘-’ (zero), there is no need to be listed in the $\Delta T_{IB,c} / \Delta R_{IB,c}$ table.** + +There are some special delta TIB and RIB values for the band combinations having SUL, SDL, immediately close component band, band combination with overlapping component band, and EN-DC combination with LTE LAA component band in the current specifications. However, the denotations for the delta TIB and RIB values for these special constituent band are inconsistent among different band combinations, some of which having the value of “-”, some of which having the value of “N/A”, while some of others having the value of non-zero number. To avoid inconsistencies, the following guideline is applied to the band combinations having special component band. + +**Guideline 3: For the component bands which are special bands such as SDL band, SUL band, immediately close band, band combination with overlapping band, and EN-DC combination with LTE LAA band, etc.** + +- Non-zero value is not allowed for the special bands in the delta TIB/RIB tables. +- If uplink is not supported on a constituted band of the DC/CA band combination, "N/A" is used when deriving the delta T requirements for that constituted band of the band combination. +- If downlink is not supported on a constituted band of the DC/CA band combination, "N/A" is used when deriving the delta R requirements for that constituted band of the band combination. + +## 6.4 Guidelines on simplification for CA configurations + +For CA configurations in the columns for DL and UL CA configurations, all the possible configurations are explicitly listed in the current CA configuration tables. However, the redundancy issue is becoming more and more serious in the CA configuration tables especially when multiple component frequency bands are involved. The permutation of component bands and CA BW classes results in explosive size of CA configuration table. In order to alleviate the workload for Rel-18 basket WID rapporteurs, the following guideline is proposed to CA configuration tables. + +**Guideline 1: There shall be no special characters such as “ ”, “;”, “:”, “/” or any other special character not belonging to the combinations with the exception that the delimiter “/” is allowed in the FR2 part of the uplink configurations. A note as below is suggested to be added at the end of the configuration tables.** + +Note: The delimiter “/” will only be used in the uplink configurations for the sake of simplicity. For example, CA\_nxA-nyA/B/C denotes CA\_nxA-nyA, CA\_nxA-nyB and CA\_nxA-nyC, where nx and ny are two NR bands, ny is a FR2 band and A, B and C are the corresponding bandwidth classes respectively. + +Table 6.4-1: Example for simplified inter-band CA configuration table + +| NR CA configuration | Uplink configuration(*) | NR Band | Channel bandwidth (MHz) (NOTE 1) | Bandwidth combination set | +|---------------------|--------------------------------------------------------------------------|---------|-------------------------------------------------|---------------------------| +| CA_n2A-n77A-n260A | CA_n2A-n77A
CA_n77A-n260A
CA_n2A-n260A | n2 | 5, 10, 15, 20 | 0 | +| | | n77 | 10, 15, 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | | +| | | n260 | 50, 100, 200, 400 | | +| CA_n2A-n77A-n260G | CA_n2A-n77A
CA_n2A-n260A/G
CA_n77A-n260A/G | n2 | 5, 10, 15, 20 | 0 | +| | | n77 | 10, 15, 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | | +| | | n260 | CA_n260G | | +| CA_n2A-n77A-n260H | CA_n2A-n77A
CA_n2A-n260A/G/H
CA_n77A-n260A/G/H | n2 | 5, 10, 15, 20 | 0 | +| | | n77 | 10, 15, 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | | +| | | n260 | CA_n260H | | +| CA_n2A-n77A-n260I | CA_n2A-n77A
CA_n2A-n260A/G/H/I
CA_n77A-n260A/G/H/I | n2 | 5, 10, 15, 20 | 0 | +| | | n77 | 10, 15, 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | | +| | | n260 | CA_n260I | | +| CA_n2A-n77A-n260J | CA_n2A-n77A
CA_n2A-n260A/G/H/I/J
CA_n77A-n260A/G/H/I/J | n2 | 5, 10, 15, 20 | 0 | +| | | n77 | 10, 15, 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | | +| | | n260 | CA_n260J | | +| CA_n2A-n77A-n260K | CA_n2A-n77A
CA_n2A-n260A/G/H/I/J/K
CA_n77A-n260A/G/H/I/J/K | n2 | 5, 10, 15, 20 | 0 | +| | | n77 | 10, 15, 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | | +| | | n260 | CA_n260K | | +| CA_n2A-n77A-n260L | CA_n2A-n77A
CA_n2A-n260A/G/H/I/J/K/L
CA_n77A-n260A/G/H/I/J/K/L | n2 | 5, 10, 15, 20 | 0 | +| | | n77 | 10, 15, 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | | +| | | n260 | CA_n260L | | +| CA_n2A-n77A-n260M | CA_n2A-n77A
CA_n2A-n260A/G/H/I/J/K/L/M
CA_n77A-n260A/G/H/I/J/K/L/M | n2 | 5, 10, 15, 20 | 0 | +| | | n77 | 10, 15, 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | | +| | | n260 | CA_n260M | | + +Note (\*): The delimiter "/" will only be used in the uplink configurations for the sake of simplicity. For example, CA\_nxA-nyA/B/C denotes CA\_nxA-nyA, CA\_nxA-nyB and CA\_nxA-nyC, where nx and ny are two NR bands, ny is a FR2 band and A, B and C are the corresponding bandwidth class respectively. + +## 6.5 Guidelines on Co-Existence analysis + +### 6.5.1 Uplink Intra-Band CA with one UL CC transmissions + +For harmonic mixing analysis where the UL of either band can directly or in the form of uplink harmonic interfere the DL receive band of the other band in the combination the following rules applies for the study of the combinations + +besides the frequency range checks. The rules are split into those of PC3 in Table 6.5.1-1 and those for PC2 or PC1.5 in Table 6.5.1-2. The cells in grey do not require harmonic mixing analysis. For certain UL/DL combinations an additional check on the DL frequency of the impacted receive band must be made. + +**Table 6.5.1-1: PC3 and PC5 harmonic mixing rules of analysis applicability** + +| PC3 and PC5 of UL band | | | | | +|------------------------|-----|-----|------------------|-----| +| | UL1 | UL2 | UL3 | UL4 | +| DL2 | TBD | N/A | DL > 3GHz | N/A | +| DL3 | All | All | N/A | TBD | +| DL4 | TBD | N/A | DL > [3 or 5]GHz | N/A | +| DL5 | All | TBD | N/A | N/A | + +**Table 6.5.1-2: PC2 and PC1.5 harmonic mixing rules of analysis applicability** + +| PC2 and PC1.5 of UL band | | | | | +|--------------------------|-----|-----|-------------|-----| +| | UL1 | UL2 | UL3 | UL4 | +| DL2 | TBD | N/A | All | N/A | +| DL3 | All | All | N/A | TBD | +| DL4 | All | N/A | DL > [3]GHz | N/A | +| DL5 | All | TBD | N/A | N/A | + +The TBD's in tables 6.5.1-1 and 6.5.1-2 shall be further evaluated based on companies technical analysis during Rel-18. + +### 6.5.2 Uplink Intra-Band CA with two UL CC transmissions + +When adding a band combination including two uplink transmission in one UL Intra-Band Carrier Aggregation this study is needed for both non-contiguous and contiguous intra-band uplink CA. + +There are 5 cases to consider where IMDs of the two CCs of an intra-band UL CA may cause MSD issues: + +- FDD band with DL and UL contiguous intra-band CA (CA\_nXXB/ C UL and DL) => IMDs of intra band CA can cause MSD up to 7th order, only odd orders should be an issue. +- FDD band with DL and UL non-contiguous intra-band CA (CA\_nXX(2A) UL and DL) => IMDs of intra band CA can cause MSD up to 7th order, only odd orders should be an issue. +- Two band simultaneous Rx/Tx combinations with 1 band UL with contiguous intra-band CA => IMDs of intra band CA can cause MSD up to 9th order, only odd order should be an issue as 2nd and 4th order are limited to 400MHz and higher even orders are typically low. +- Two band simultaneous Rx/Tx combinations with 1 band UL with non-contiguous intra-band CA => IMDs of intra band CA can cause MSD up to 7th order, 2nd order can be up to 600MHz and should not be an issue while 4th order can be an issue for low bands as it can reach up to 1200Mhz and higher even orders are typically low. +- Two band simultaneous Rx/Tx combinations with 2 band UL with contiguous intra-band CA in one of the bands => IMDs of intra band CA can cause MSD up to 7th order, 2nd order can be up to 600MHz and should not be an issue while 4th order can be an issue for low bands as it can reach up to 1200Mhz and higher even orders are typically low. +- The assumption that out of even order IMDs, only 4th order IMD is an issue, is based on the fact that in R18: + - Maximum UL aggregated BW for contiguous intra-band is 200MHz. + - Maximum bandwidth separation class is 600MHz. +- Two band simultaneous Rx/Tx combinations with 2 band UL with non-contiguous intra-band CA in one of the bands is not considered because it would require 3 non-contiguous UL clusters which is not allowed in R18. + +Based on the above, an IMD calculation table can be made generic for all above cases as shown in Table 6.5.2-1. + +**Table 6.5.2-1: Co-existence studies for uplink configurations including intra-band UL CA** + +| Configuration | Channel BW | Minimum Channel separation | Maximum Instantaneous UL BW | Minimum frequency | Maximum frequency | | +|---------------------|-----------------|----------------------------|-----------------------------|-------------------|-------------------|-----------------| +| Data | | | | | | - | +| CC location | fU1L | fU2L | fU3L | fU1H | fU2H | fU3H | +| Frequency | | | | | | | +| 2nd | fU1L-fU2L | fU1L-fU3L | fU1L + fU2L | fU1H+fU2H | - | - | +| Interference ranges | | | | | - | - | +| 3rd | 2*fU1L-fU3L | 2*fU1H-fU3H | 2*fU1L + fU2L | 2*fU1H + fU2H | - | - | +| Interference ranges | | | | | - | - | +| 4th | 2*fU1L - 2*fU2L | 2*fU1H - 2*fU3H | 3*fU1L - fU3L | 3*fU1H - fU3H | 3*fU1L + fU2L | 3*fU1H + fU2H | +| Interference ranges | | | | | | | +| 5th | 3*fU1L - 2*fU3L | 3*fU1H - 2*fU3H | 4*fU1L - fU3L | 4*fU1H - fU3H | 4*fU1L + fU2L | 4*fU1H + fU2H | +| Interference ranges | | | | | | | +| 6th | 3*fU1L - 3*fU2L | 3*fU1H - 3*fU3H | 4*fU1L - 2*fU3L | 4*fU1H - 2*fU3H | 5*fU1L - fU3L | 5*fU1H - fU3H | +| Interference ranges | | | | | | | +| 7th | 4*fU1L - 3*fU3L | 4*fU1H - 3*fU3H | 5*fU1L - 2*fU3L | 5*fU1H - 2*fU3H | 6*fU1L - fU3L | 6*fU1H - fU3H | +| Interference ranges | | | | | | | +| 9th | 5*fU1L - 4*fU3L | 5*fU1H - 4*fU3H | 6*fU1L - 3*fU3L | 6*fU1H - 3*fU3H | 7*fU1L - 2*fU3L | 7*fU1H - 2*fU3H | +| Interference ranges | | | | | | | + +If any issues are identified via the calculations presented in Table 6.5.2-1 additional REFSENS requirements may be needed. + +In the Table 6.5.2-1 the following abbreviations is used: + +fU1L = minimum frequency of TX aggressor band of ULCC1 lower band range (i.e. Minimum frequency edge of the band) + +fU2L = minimum frequency of TX aggressor band of ULCC2 lower band range (i.e. Minimum frequency edge of the band) + +fU3L = maximum frequency of TX aggressor band of ULCC2 lower band range (i.e. Minimum frequency edge of the band + Maximum Instantaneous UL BW) + +fU1H = maximum frequency of TX aggressor band of ULCC1 higher band range (i.e. Maximum frequency edge of the band) + +fU2H = minimum frequency of TX aggressor band of ULCC2 higher band range + +fU3H = maximum frequency of TX aggressor band of ULCC2 higher band range (i.e. Minimum frequency edge of the band - Maximum Instantaneous UL BW) + +fD1L = minimum frequency of RX victim band of DLCC placed on the lower frequency side of the TX aggressor band + +fD1H = maximum frequency of RX victim band of DLCC placed on the lower frequency side of the TX aggressor band + +fD2L = minimum frequency of RX victim band of DLCC placed on the higher frequency side of the TX aggressor band + +fD2H = maximum frequency of RX victim band of DLCC placed on the higher frequency side of the TX aggressor band + +Channel BW = Channel bandwidth of the component carrier. + +- Equal to minimum UL CBW for non-contiguous UL CA + +- Equal to the maximum UL CBW combination that fits the minimum between the maximum aggregated CBW for the BCS and the band bandwidth for contiguous UL CA + +Minimum channel separation = Minimum frequency separation between the two component carriers or the inter CC GB + +- Equal to 0 for contiguous intra-band UL CA + +- Equal to minimum CBW for non-contiguous ULCA + +Maximum channel separation = Maximum frequency separation between the two component carriers or aggregated uplink BW + +- For contiguous intra-band UL CA it is equal to either the aggregated bandwidth or total bandwidth of the band, whatever is the smallest. + +- For non-contiguous intra-band UL CA it is equal to either the bandwidth separation class bandwidth or total bandwidth of the band, whatever is the smallest. + +![Figure 6.5.2-1: Co-existence studies for Uplink Intra-Band Non-Contiguous CA. The diagram shows two rows of frequency bands. The top row shows three victim bands (DLCC) with widths n, a, and m, and an aggressor band (ULCC) with widths a, b, b, b, b, a. The bottom row shows the same bands with additional labels: f_D1L, f_D1H, f_U1L, f_U2L, f_U3L, f_U3H, f_U2H, f_U1H, f_D2L, f_D2H. It also shows gaps d and c between the bands.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +Figure 6.5.2-1: Co-existence studies for Uplink Intra-Band Non-Contiguous CA. The diagram shows two rows of frequency bands. The top row shows three victim bands (DLCC) with widths n, a, and m, and an aggressor band (ULCC) with widths a, b, b, b, b, a. The bottom row shows the same bands with additional labels: f\_D1L, f\_D1H, f\_U1L, f\_U2L, f\_U3L, f\_U3H, f\_U2H, f\_U1H, f\_D2L, f\_D2H. It also shows gaps d and c between the bands. + +**Figure 6.5.2-1: Co-existence studies for Uplink Intra-Band Non-Contiguous CA** + +### 6.5.3 Uplink triple beat + +When adding a band combination including three uplink transmission - one with UL intra-band carrier aggregation, which makes two tones and a third in the form of a single uplink component carrier this study is needed regardless if the intra-band CA is non-contiguous or contiguous intra-band uplink CA. + +**Table 6.5.3-1: Band nX and Band nY triple beat IMD products** + +| | | | | | | +|--------------|-------------------|--------------------|-------------------|--------------------|--------------------| +| CC location | fU1L | fU2L | fU3L | fU1H | CBW | +| Frequency | - | - | - | - | | +| CC location | fSCCL | fSCCH | fU2H | fU3H | Min ch. separation | +| Frequency | - | - | - | - | | +| 1st order TB | fU3L -fU1L- fSCCL | fU2L -fU1L + fSCCL | fU2L -fU1L- fSCCH | fU3L -fU1L + fSCCH | Max ch. separation | +| Ranges | - | - | - | - | | +| 1st order TB | fU2L+fU1L-fSCCH | fU1H+fU2H-fSCCL | fU2L +fU1L+fSCCL | fU1H +fU2H+fSCCH | | +| Ranges | - | - | - | - | | + +If any issues are identified via the calculations presented in Table 6.5.3-1 additional REFSENS requirements may be needed. + +In the Table 6.5.3-1 the following abbreviations is used: + +fU1L = minimum frequency of TX aggressor band of ULCC1 lower band range (i.e. Minimum frequency edge of the band) + +fU2L = minimum frequency of TX aggressor band of ULCC2 lower band range (i.e. Minimum frequency edge of the band) + +fU3L = maximum frequency of TX aggressor band of ULCC2 lower band range (i.e. Minimum frequency edge of the band + Maximum Instantaneous UL BW) + +fU1H = maximum frequency of TX aggressor band of ULCC1 higher band range (i.e. Maximum frequency edge of the band) + +fU2H = minimum frequency of TX aggressor band of ULCC2 higher band range + +fU3H = maximum frequency of TX aggressor band of ULCC2 higher band range (i.e. Minimum frequency edge of the band - Maximum Instantaneous UL BW) + +fSCCL = minimum frequency in single CC band + +fSCCH = maximum frequency in single CC band + +![Figure 6.5.3-1: Co-existence studies triple beat. The diagram shows two rows of frequency bands. The top row shows three main frequency regions: F_BW_SingleCC_Lower, F_BW_NC_CC, and F_BW_SingleCC_Higher. F_BW_SingleCC_Lower contains ULCC_S1 with bandwidth 'n'. F_BW_NC_CC contains a sequence of ULCC1 (bandwidth 'a'), ULCC2 (bandwidth 'b'), ULCC2 (bandwidth 'b'), ULCC2 (bandwidth 'b'), ULCC2 (bandwidth 'b'), and ULCC1 (bandwidth 'a'). F_BW_SingleCC_Higher contains ULCC_S2 with bandwidth 'm'. The bottom row shows the same three frequency regions with different component carrier configurations: F_BW_SingleCC_Lower, F_BW_NC_CC, and F_BW_SingleCC_Higher. F_BW_NC_CC contains ULCC1 (bandwidth 'a'), ULCC2 (bandwidth 'b'), ULCC2 (bandwidth 'b'), ULCC2 (bandwidth 'b'), ULCC2 (bandwidth 'b'), and ULCC1 (bandwidth 'a'). There are additional labels 'd', 'c', and 'c' between the carriers. Frequency markers f_SCC_L, f_SCC_H, f_U1L, f_U2L, f_U3L, f_U3H, f_U2H, f_U1H, f_SCC_L, and f_SCC_H are shown along the bottom axis.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +**Channel BW = Channel bandwidth of the component carrier** + +**Minimum channel separation = Minimum frequency separation between the two component carriers or the inter CC GB** + +**Maximum channel separation = Maximum frequency separation between the two CCs or aggregated uplink BW** + +Figure 6.5.3-1: Co-existence studies triple beat. The diagram shows two rows of frequency bands. The top row shows three main frequency regions: F\_BW\_SingleCC\_Lower, F\_BW\_NC\_CC, and F\_BW\_SingleCC\_Higher. F\_BW\_SingleCC\_Lower contains ULCC\_S1 with bandwidth 'n'. F\_BW\_NC\_CC contains a sequence of ULCC1 (bandwidth 'a'), ULCC2 (bandwidth 'b'), ULCC2 (bandwidth 'b'), ULCC2 (bandwidth 'b'), ULCC2 (bandwidth 'b'), and ULCC1 (bandwidth 'a'). F\_BW\_SingleCC\_Higher contains ULCC\_S2 with bandwidth 'm'. The bottom row shows the same three frequency regions with different component carrier configurations: F\_BW\_SingleCC\_Lower, F\_BW\_NC\_CC, and F\_BW\_SingleCC\_Higher. F\_BW\_NC\_CC contains ULCC1 (bandwidth 'a'), ULCC2 (bandwidth 'b'), ULCC2 (bandwidth 'b'), ULCC2 (bandwidth 'b'), ULCC2 (bandwidth 'b'), and ULCC1 (bandwidth 'a'). There are additional labels 'd', 'c', and 'c' between the carriers. Frequency markers f\_SCC\_L, f\_SCC\_H, f\_U1L, f\_U2L, f\_U3L, f\_U3H, f\_U2H, f\_U1H, f\_SCC\_L, and f\_SCC\_H are shown along the bottom axis. + +**Figure 6.5.3-1: Co-existence studies triple beat** + +For two-band inter-band CA or DC combinations, the precondition is that: + +- The 2 UL bands are part of the same band group or belong to adjacent band groups as defined in Table 6.5.3-2. + +For three-band inter-band CA or DC combinations and triple beat in third band, the precondition is that: + +- The 3rd DL band belongs to the same band group or belongs to a band group which is adjacent to either one of the UL bands, where band groups are defined in Table 6.5.3-2. + +For the case when the victim band may be affected by a 1st order triple-beat product, proponents should systematically check if the downlink band may be affected by dual uplink IMD3 interference. If the test point is missing, a dual UL IMD3 MSD test point should be specified. + +If the triple beat frequency is composed of the frequency sum of the 2 discrete RBs in the contiguous UL CA, there is no need to specify the TB test configuration as the requirement can already be verified by the fallback 2UL IMD3. The generic guidelines can be found in clause 7.4 for type 3 UL configurations. + +**Table 6.5.3-2: Band group definition for adjacent band-group criterion** + +| FR1 band group range | | | | | | +|----------------------|------------|------------|-------------|-------------|-------------| +| Name | FR1-1 (LB) | FR1-2 (MB) | FR1-3 (HB) | FR1-4 (VHB) | FR1-5 (UHB) | +| Range (MHz) | 600-1000 | 1400-2200 | 2300-2700 | 3300-5000 | 5150-7125 | +| Duplex mode | Mostly FDD | Mostly FDD | FDD and TDD | TDD only | TDD only | + +## 6.6 Rules for band combination with BCS4/BCS5 + +### 6.6.1 Introduction of BCS4/BCS5 + +In NR band combination, it is a challenge for operators to request new NR CA and SUL band combinations when new channel bandwidths are added to existing bands in the band combinations. Operators have to go back and create new Bandwidth Combinations Sets for existing band combinations in order to be able to use those new channel bandwidths in NR CA and SUL. To reduce the workload in RAN4, a new WID for creating a new type of BCS was approved in [8]. + +BCS4/BCS5 are allowed to be applied to new band combinations in RAN4 which indicate UE to support up to all of the channel bandwidths for the band in the band combination. BCS4 is release independent to Rel-15 with no new signalling while BCS5 is functionally equivalent to BCS4 except that the new signalling [*supportedMinBandwidthDL/supportedMinBandwidthUL*] introduced in Rel-17 such as the limitation to the supporting channel bandwidth in each band within the band combination would apply, and BCS5 with the signalling [*supportedMinBandwidthDL/supportedMinBandwidthUL*] is allowed for early implementation from Rel-15. For a legacy gNB that was not upgraded to understand BCS4 or BCS5 with the new signalling, it would enable to ignore BCS4 or BCS5 with the new signalling. + +Considering that BCSs are not defined or reported separately for UL and DL for traditional BCSs, there is also no need to differentiate BCS4/BCS5 for UL and DL. BCS4/BCS5 can be used for FR1 intra-band UL CA. Table 6.6.1-1 shows + +the template for NR CA configurations for intra-band contiguous CA with BCS4/BCS5. Table 6.6.1-2 shows the template for NR CA configurations for intra-band non-contiguous CA with BCS4/BCS5. For inter-band CA combinations including FR1 intra-band CA and with BCS4/BCS5, the bandwidth combination sets for the FR1 intra-band CA are BCS4/BCS5. The BCS4/BCS5 are represented in the inter-band CA configuration table by using the option which covers inter-band and intra-band as shown in Table 6.6.1-3. For SUL band combinations, BCS4/BCS5 reuse the same template with inter-band CA as in Table 6.6.1-3. + +**Table 6.6.1-1: Template for NR intra-band contiguous CA configurations with BCS4/BCS5** + +| NR CA configuration / Bandwidth combination set | | | | | | | | | +|-------------------------------------------------|--------------------------|--------------------------------------------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|------------------------------------|---------------------------| +| NR CA configuration n | Uplink CA configurations | Channel bandwidths for carrier (MHz) | Channel bandwidths for carrier (MHz) | Channel bandwidths for carrier (MHz) | Channel bandwidths for carrier (MHz) | Channel bandwidths for carrier (MHz) | Maximum aggregated bandwidth (MHz) | Bandwidth combination set | +| CA_nXC | CA_nXC | 40 | 80, 100 | | | | 180 | 0 | +| | | 50, 60, 80 | 60, 80, 100 | | | | | | +| | | ... | ... | | | | ... | ... | +| | | See nX channel bandwidths in Table 5.3.5-1 for each carrier 2 | | | | | TBD | 4 and 5 | + +NOTE 1: 5 MHz is not applicable for 30/60 kHz SCS. +NOTE 2: The aggregated bandwidth must be greater than or equal to the minimum for the bandwidth class defined in Table 5.3A.5-1, and smaller than or equal to the maximum aggregated bandwidth. + +**Table 6.6.1-2: Template for NR intra-band non-contiguous CA configurations with BCS4/BCS5** + +| NR CA configuration / Bandwidth combination set | | | | | | | | +|-------------------------------------------------|--------------------------|-------------------------------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|------------------------------------|---------------------------| +| NR CA configuration n | Uplink CA configurations | Channel bandwidths for carrier (MHz) | Channel bandwidths for carrier (MHz) | Channel bandwidths for carrier (MHz) | Channel bandwidths for carrier (MHz) | Maximum aggregated bandwidth (MHz) | Bandwidth combination set | +| CA_nX(2A) | CA_nX(2A) | 40, 50, 60, 80, 100 | 40, 50, 60, 80, 100 | | | 180 | 0 | +| | | ... | ... | | | ... | ... | +| | | See nX channel bandwidths in Table 5.3.5-1 for each carrier | | | | TBD | 4 and 5 | + +**Table 6.6.1-3: Template for NR inter-band CA configurations including FR1 intra-band CA with BCS4/BCS5** + +| NR CA configuration | Uplink CA configuration | NR Band | Channel bandwidth (MHz) | | | | | | Bandwidth combination set | +|---------------------|-------------------------|---------|---------------------------------------------|----|----|----|----|----|---------------------------| +| | | | 5 | 10 | 15 | 20 | 25 | 30 | | +| CA_nXA-nYA | CA_nXA-nYA | nX | 5 | 10 | 15 | 20 | | | 0 | +| | | nY | 5 | 10 | 15 | 20 | 25 | 30 | | +| | | nX | See nX channel bandwidths in Table 5.3.5-1 | | | | | | 4 and 5 | +| | | nY | See nY channel bandwidths in Table 5.3.5-1 | | | | | | | +| CA_nXA-nYC | CA_nXA-nYA | nX | 5 | 10 | 15 | 20 | | | 0 | +| | | nY | 5 | 10 | 15 | 20 | 25 | 30 | | +| | | nX | See nX channel bandwidths in Table 5.3.5-1 | | | | | | 4 and 5 | +| | | nY | See nY channel bandwidths in Table 5.5A.1-1 | | | | | | | + +With regards to the applicability of BCS4/BCS5 to FR2 intra-band combinations, since all FR2 combinations only have BCS0 and new channel bandwidth have not been added, BCS4/BCS5 are probably not needed for FR2. For FR1+FR2 BCS4/BCS5 combinations the configuration table shall state that BCS0 applies for the intra-band FR2 part (when applicable). + +### 6.6.2 Guidelines for band combination with BCS4/BCS5 + +The following are the rules for applying BCS4/BCS5 for band combination request: + +- BCS4/BCS5 apply to SUL, NR CA, NR DC and SUL and/or NR CA part of inter-band MR-DC while it does not apply to intra-band MR DC. +- BCS4/ BCS5 shall be requested together, but BCS5 can't be reported together with BCS4. +- For BCS4/BCS5 there is no need to add information in a BCS sheet about which channel bandwidths that are supported since there is no such details to be filled in for BCS4 and BCS5. For BCS4 and BCS5 it is enough just to fill in the band combination table sheet. +- If needed, traditional BCSs are allowed for all releases. For a new band combination in Rel-17 and onwards, if BCS4/BCS5 are requested, traditional BCSs are allowed pending on the proponents, the network of the proponents of BCS4/BCS5 is demanded to recognize BCS4/BCS5. + +### 6.6.3 The maximum aggregated bandwidth for intra-band CA with BCS4/BCS5 + +To guarantee the BCS4/BCS5 can cover all the possible bandwidth configurations for intra-band CA, the maximum aggregated bandwidth chosen for BCS4/BCS5 should equal to- $\min\{n * \max \text{ channel bandwidth of each carrier, BW}_{\text{Channel\_CA}} \text{ of each CA bandwidth class, Maximum frequency range of each band}\}$ for intra-band contiguous CA. + +- $\min\{n * \max \text{ channel bandwidth of each carrier, Maximum frequency range of each band} - \text{Minimum sub-block gaps}\}$ for intra-band non-contiguous CA. + +where n is the number of aggregated CCs, minimum sub-block gaps indicates the sum of the min sub-block gap between the upper edge of lower component carrier and lower edge of higher component carrier that UE can support per band combination in two adjacent non-contiguous component carriers. + +The value of min sub-block gaps could be clarified by the request operator but it should try to cover the needs of all possible operators. + +## 6.7 Guidelines on simplification for 3DL/2UL MSD due to 2UL IMD interference + +For inter-band NR-CA or inter-band EN-DC 3DL/2UL MSD requirements due to dual UL IMD interference, a maximum of two uplink configurations shall be specified: one uplink configuration in each band of the 2UL inter-band CA or DC configuration. + +The UL carrier frequency "UL Fc" and the UL RB allocation "UL LCRB" of the 3rd DL band which is affected by 2UL IMD interference shall be specified as "N/A". + +These guidelines are illustrated in the examples of Table 6.7-1 and Table 6.7-2, including the special case of 3DL/2UL EN-DC combination with only 2 frequency bands where one of the constituent bands is configured for intra-band CA operation, for example DC\_66A\_(n)5AA captured in Table 6.7-2. + +**Table 6.7-1: Example of removing 3UL configurations for NR-CA 3DL/2UL MSD test points due to 2UL IMD interference** + +| Band / Channel bandwidth / N RB / Duplex mode | | | | | | | | Source of IMD | +|----------------------------------------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|---------------| +| NR CA band combination | NR band | UL F c (MHz) | UL/DL BW (MHz) | UL L CRB | DL F c (MHz) | MSD (dB) | Duplex mode | | +| CA_n1-n3-n28 | n1 | 1975 | 5 | 25 | 2165 | N/A | FDD | N/A | +| | n28 | 710.5 | 5 | 25 | 765.5 | N/A | FDD | N/A | +| | n3 | N/A | 5 | N/A | 1818.5 | 4.0 | FDD | IMD5 | +| | n3 | 1780 | 5 | 25 | 1875 | N/A | FDD | N/A | +| | n28 | 710.5 | 5 | 25 | 765.5 | N/A | FDD | N/A | +| | n1 | N/A | 5 | N/A | 2139 | 11.0 | FDD | IMD4 | +| CA_n1-n3-n41 | n1 | 1977.5 | 5 | 25 | 2167.5 | N/A | FDD | N/A | +| | n3 | 1712.5 | 5 | 25 | 1807.5 | N/A | FDD | N/A | +| | n41 | N/A | 10 | N/A | 2507.5 | 5.0 | TDD | IMD5 | + +**Table 6.7-2: Example of removing 3UL configurations for EN-DC 3DL/2UL MSD test points due to 2UL IMD interference** + +| NR or E-UTRA Band / Channel bandwidth / NRB / MSD | | | | | | | | +|---------------------------------------------------|-----------------|-------------------------|----------------|---------------------|-------------------------|----------|-----------| +| EN-DC Configuration | EUTRA / NR band | UL F c (MHz) | UL/DL BW (MHz) | UL L CRB | DL F c (MHz) | MSD (dB) | IMD order | +| DC_1A-3A_n28A
DC_1A-3C_n28A | 1 | 1975 | 5 | 25 | 2165 | N/A | N/A | +| | 3 | N/A | 5 | N/A | 1818.5 | 4.0 | IMD5 | +| | n28 | 710.5 | 5 | 25 | 765.5 | N/A | N/A | +| | 1 | N/A | 5 | N/A | 2139 | 11.0 | IMD4 | +| | 3 | 1780 | 5 | 25 | 1875 | N/A | N/A | +| | n28 | 710.5 | 5 | 25 | 765.5 | N/A | N/A | +| DC_66A-(n)5AA | 66 | 1721 | 5 | 25 | 2121 | N/A | N/A | +| | 5 | N/A | 5 | N/A | 878 | 25 | IMD2 | +| | n5 | 838 | 5 | 25 | 883 | 30 | IMD2 | + +## 6.8 Guidelines on configuration tables + +### 6.8.1 CA configuration table + +The CA configuration table in TS 38.101-1/-2/-3 provides the information of channel bandwidth, SCS and bandwidth combination set of the bands for each CA configuration. The uplink CA configuration information is also included in the configuration tables for the allowed UL CA configurations supported by the specification. + +For inter-band CA configuration table, considering the huge number of configurations introduced into the spec, the guideline for the spec structure is as below: + +- All combinations having the same number of constituent bands are categorized into one sub-clause, see Fig 6.8.1-1. +- For two bands inter-band CA configuration table in TS 38.101-1 5.5A.3.1, a “sub-table-group” tag is suggested to be applied for the purpose of easier retrieval, see Fig 6.8.1-2. +- For the other inter-band CA configuration tables which have huge configurations of more than 50 pages, the big table could be split to a limited number of up to three smaller sub-tables. The sub-tables should not have less than 40 pages and the maximum number should be 3 sub-tables after the split. + +![Figure 6.8.1-1: Example for sub-clauses for inter-band CA configurations. The diagram shows a hierarchical list of sub-clauses under '5.5A Configuration for CA'. The sub-clause '5.5A.1 Inter-band CA configurations between FR1 and FR2' is expanded, showing four sub-clauses: '5.5A.1.1 Inter-band CA configurations between FR1 and FR2 (two bands)', '5.5A.1.2 Inter-band CA configurations between FR1 and FR2 (three bands)', '5.5A.1.3 Inter-band CA configurations between FR1 and FR2 (four bands)', and '5.5A.1.4 Inter-band CA configurations between FR1 and FR2 (five bands)'. The first sub-clause is circled in red. The text '38.101-3' is written in red above the list. The text 'new' is written in red next to the last sub-clause.](c85b57b2414f341860dfc338e1cf2509_img.jpg) + +Figure 6.8.1-1: Example for sub-clauses for inter-band CA configurations. The diagram shows a hierarchical list of sub-clauses under '5.5A Configuration for CA'. The sub-clause '5.5A.1 Inter-band CA configurations between FR1 and FR2' is expanded, showing four sub-clauses: '5.5A.1.1 Inter-band CA configurations between FR1 and FR2 (two bands)', '5.5A.1.2 Inter-band CA configurations between FR1 and FR2 (three bands)', '5.5A.1.3 Inter-band CA configurations between FR1 and FR2 (four bands)', and '5.5A.1.4 Inter-band CA configurations between FR1 and FR2 (five bands)'. The first sub-clause is circled in red. The text '38.101-3' is written in red above the list. The text 'new' is written in red next to the last sub-clause. + +Figure 6.8.1-1 Example for sub-clauses for inter-band CA configurations + +![Figure 6.8.1-2: Example for “sub-table-group” tag for two bands inter-band CA configurations. The diagram shows a hierarchical list of sub-clauses under '5.5A.3 Configurations for inter-band CA'. The sub-clause '5.5A.3.1 Configurations for inter-band CA (two bands)' is expanded, showing three sub-clauses: 'Table 5.5A.3.1-1a ~ Table 5.5A.3.1-1e', 'Table 5.5A.3.1-1f ~ Table 5.5A.3.1-1j', and 'Table 5.5A.3.1-1k~ Table 5.5A.3.1-1n'. These three sub-clauses are grouped by a red curly brace and labeled 'new tag' in red.](f1cbfa3fc27f58581615654fec4335d8_img.jpg) + +Figure 6.8.1-2: Example for “sub-table-group” tag for two bands inter-band CA configurations. The diagram shows a hierarchical list of sub-clauses under '5.5A.3 Configurations for inter-band CA'. The sub-clause '5.5A.3.1 Configurations for inter-band CA (two bands)' is expanded, showing three sub-clauses: 'Table 5.5A.3.1-1a ~ Table 5.5A.3.1-1e', 'Table 5.5A.3.1-1f ~ Table 5.5A.3.1-1j', and 'Table 5.5A.3.1-1k~ Table 5.5A.3.1-1n'. These three sub-clauses are grouped by a red curly brace and labeled 'new tag' in red. + +Figure 6.8.1-2 Example for “sub-table-group” tag for two bands inter-band CA configurations + +For CA within FR1 bands, TS 38.101-1 [4] provides the CA configuration tables for intra-band contiguous CA, intra-band non-contiguous CA and inter-band CA for NR FR1 bands. The additional information for maximum aggregated bandwidth is set for intra-band contiguous and intra-band non-contiguous CA configuration tables for FR1. + +For CA within FR2 bands, TS 38.101-2 [5] provides the CA configuration tables for intra-band contiguous CA, intra-band non-contiguous CA and inter-band CA for NR FR2 bands. The additional information for maximum aggregated bandwidth is set for intra-band contiguous and intra-band non-contiguous CA configuration tables in TS 38.101-2 [5]. For intra-band non-contiguous CA, the concept of sub-block is applied to FR2. Sub-blocks belonging to a CA + +configuration can be in any order. This means a certain CA configuration acronym includes all sub-block arrangements which have exactly the same sub-block set. As an example, CA\_n260(2G-3O) denotes CA\_n260(2O-2G-O), CA\_n260(G-3O-G) etc, but these are not listed in tables separately. + +For CA between FR1 and FR2 bands, TS 38.101-3 [6] provides the inter-band CA configuration tables for NR bands between FR1 and FR2. + +For the uplink CA configuration, “-” in the configuration table denotes that non-CA operation is supported in this configuration, i.e. only single carrier operation for the constituent band is used for uplink. + +For the sake of brevity and to reduce the size of CA configuration tables, instead of showing explicitly in the CA configuration tables, the SCS info for each NR band in the configuration is referred to the channel bandwidths for each NR band in clause 5.3.5 of TS 38.101-1 [4] and TS 38.101-2 [5]. For configurations including intra-band contiguous part, the detail configuration for this part is referred to the corresponding intra-band contiguous CA configuration table. Examples: + +For NR inter-band CA configuration with two bands in FR1, Table 6.8.1-1 illustrates that, + +- CA\_n1A-n3A consists of two NR bands n1 and n3 whose SCS values are defined in Table 6.8.1-2. For example, for NR band n1, the supported channel bandwidth in BCS0 is 5MHz, 10MHz, 15MHz and 20MHz where channel bandwidth 5MHz supports SCS with only 15kHz, channel bandwidths 10MHz, 15MHz and 20MHz support all SCS of {15kHz, 30kHz, 60kHz}. +- CA\_n1B-n3A having intra-band contiguous part CA\_n1B, the configuration of band n1 for the corresponding CA part is referred to CA\_n1B\_BCS0 defined in intra-band contiguous CA configuration table. +- CA\_n2A-n66A consists of two BCSs. The UL CA configurations denote the allowed UL CA configurations supported by the specification. For BCS0, the uplink configuration “-” indicates that non-CA operation is supported and only single carrier operation is used in uplink. For BCS1, the uplink configuration supports CA configuration CA\_n2A-n66A. +- For some configurations, there are regional spectrum limitations to the corresponding bands and the notes can be found in the configuration table, such as for CA\_n2A-n48A\_BCS0, the channel bandwidths 50MHz, 60MHz, 80MHz, 90MHz and 100MHz are applicable only to downlink. + +For channel bandwidth per operating band defined in clause 5.3.5 of TS 38.101-1/-2 and TS 38.104, Table 6.8.1-2 illustrates that, + +- The requirements for each configuration should be complied with the combination of channel bandwidths, SCS for each operating band defined in the table. +- For some bands the limitations to the bandwidth may be captured with notes in the table, such as for NR band n48, the channel bandwidth 5MHz is restricted to operation when carrier is configured as an SCell part of DC or CA configuration. + +Table 6.8.1-1: NR CA configurations and bandwidth combinations sets defined for inter-band CA (two bands) + +| NR CA configuration | Uplink CA configuration or single uplink carrier 10 | NR Band | Channel bandwidth (MHz) (NOTE 3) | Bandwidth combination set | +|---------------------|----------------------------------------------------------------|---------|-----------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| CA_n1A-n3A | CA_n1A-n3A | n1 | 5, 10, 15, 20 | 0 | +| | | n3 | 5, 10, 15, 20, 25, 30 | | +| | | n1 | 5, 10, 15, 20, 25, 30, 40, 50 | 1 | +| | | n3 | 5, 10, 15, 20, 25, 30, 40 | | +| | | n1 | 5, 10, 15, 20 | 2 | +| | | n3 | 5, 10, 15, 20, 25, 30, 35, 40 | | +| | | n1 | n1 channel bandwidths in Table 5.3.5-1 | 4 and 5 | +| | | n3 | n3 channel bandwidths in Table 5.3.5-1 | | +| CA_n1A-n3B | - | n1 | 5, 10, 15, 20 | 0 | +| | | n3 | CA n3B BCS0 | | +| CA_n1B-n3A | CA_n1A-n3A | n1 | CA n1B BCS0 | 0 | +| | | n3 | 5, 10, 15, 20, 25, 30 | | +| | | n1 | CA n1B BCS0 | 1 | +| | | n3 | 5, 10, 15, 20, 25, 30, 40 | | +| ... | ... | ... | ... | ... | +| CA_n2A-n48A | CA_n2A-n48A | n2 | 5, 10, 15, 20 | 0 | +| | | n48 | 5, 10, 15, 20, 40, 50 1 , 60 1 , 80 1 , 90 1 , 100 1 | | +| | | n2 | 5, 10, 15, 20 | 1 | +| | | n48 | 5, 10, 15, 20, 30, 40, 50 1 , 60 1 , 70 1 , 80 1 , 90 1 , 100 1 | | +| ... | ... | ... | ... | ... | +| CA_n2A-n66A | - | n2 | 5, 10, 15, 20 | 0 | +| | | n66 | 5, 10, 15, 20, 40 | | +| | CA_n2A-n66A | n2 | 5, 10, 15, 20 | 1 | +| | | n66 | 5, 10, 15, 20, 25, 30, 40 | | +| ... | ... | ... | ... | ... | + +NOTE 1: This UE channel bandwidth is applicable only to downlink. + +Table 6.8.1-2: Channel bandwidths for each NR band + +| NR Band | SCS (kHz) | UE Channel bandwidth (MHz) | | | | | | | | | | | | | | | +|---------|-----------|----------------------------|-----|-----|-----|-----|-----|-----|-----|-----|-----------------|-----------------|-----------------|-----------------|-----------------|------------------| +| | | 5 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | 50 | 60 | 70 | 80 | 90 | 100 | +| n1 | 15 | 5 | 10 | 15 | 20 | 25 | 30 | | 40 | 45 | 50 | | | | | | +| | 30 | | 10 | 15 | 20 | 25 | 30 | | 40 | 45 | 50 | | | | | | +| | 60 | | 10 | 15 | 20 | 25 | 30 | | 40 | 45 | 50 | | | | | | +| n2 | 15 | 5 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | | | | | | | | +| | 30 | | 10 | 15 | 20 | 25 | 30 | 35 | 40 | | | | | | | | +| | 60 | | 10 | 15 | 20 | 25 | 30 | 35 | 40 | | | | | | | | +| n3 | 15 | 5 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | 50 | | | | | | +| | 30 | | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | 50 | | | | | | +| | 60 | | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | 50 | | | | | | +| ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | +| n41 | 15 | 5 4,11 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | 50 | | | | | | +| | 30 | | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | 50 | 60 | 70 | 80 | 90 | 100 | +| | 60 | | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | 50 | 60 | 70 | 80 | 90 | 100 | +| ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | +| n48 | 15 | 5 5 | 10 | 15 | 20 | | 30 | | 40 | | 50 6 | | | | | | +| | 30 | | 10 | 15 | 20 | | 30 | | 40 | | 50 6 | 60 6 | 70 6 | 80 6 | 90 6 | 100 6 | +| | 60 | | 10 | 15 | 20 | | 30 | | 40 | | 50 6 | 60 6 | 70 6 | 80 6 | 90 6 | 100 6 | +| ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | +| n66 | 15 | 5 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | | | | | | | +| | 30 | | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | | | | | | | +| | 60 | | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | | | | | | | +| ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | +| n78 | 15 | | 10 | 15 | 20 | 25 | 30 | | 40 | | 50 | | | | | | +| | 30 | | 10 | 15 | 20 | 25 | 30 | | 40 | | 50 | 60 | 70 | 80 | 90 | 100 | +| | 60 | | 10 | 15 | 20 | 25 | 30 | | 40 | | 50 | 60 | 70 | 80 | 90 | 100 | +| ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | +| n80 | 15 | 5 | 10 | 15 | 20 | 25 | 30 | | 40 | | | | | | | | +| | 30 | | 10 | 15 | 20 | 25 | 30 | | 40 | | | | | | | | +| | 60 | | 10 | 15 | 20 | 25 | 30 | | 40 | | | | | | | | +| ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | +| n86 | 15 | 5 | 10 | 15 | 20 | | | | 40 | | | | | | | | +| | 30 | | 10 | 15 | 20 | | | | 40 | | | | | | | | +| | 60 | | 10 | 15 | 20 | | | | 40 | | | | | | | | +| ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | + +NOTE 1: Void. + +NOTE 2: Void. + +NOTE 3: This UE channel bandwidth is applicable only to downlink. + +NOTE 4: This UE channel bandwidth is optional in this release of the specification. + +NOTE 5: For this bandwidth, the minimum requirements are restricted to operation when carrier is configured as an SCell part of DC or CA configuration. + +NOTE 6: For this bandwidth, the minimum requirements are restricted to operation when carrier is configured as a downlink SCell part of CA configuration. + +NOTE 7: For the 20 MHz bandwidth, the minimum requirements are specified for NR UL carrier frequencies confined to either 713-723 MHz or 728-738 MHz. For the 25 MHz bandwidth, the minimum requirements are specified for NR UL carrier frequencies confined to either 715.5-720.5 MHz or 730.5-735.5 MHz. For the 30 MHz bandwidth, the minimum requirements are specified for NR UL transmission bandwidth configuration confined to either 703-733 or 718-748 MHz. + +NOTE 8: This UE channel bandwidth is applicable only to uplink. + +NOTE 9: Void. + +NOTE 10: For this band, UE channel bandwidths which are applicable to sidelink operation are specified in Table 5.3E.1-1. + +NOTE 11: Not all frequency positions of 5 MHz carriers are possible due limitations of the SSB position relative to the 5 MHz channels. 5 MHz channels with $F_c$ such that $2499+N*1.2 \leq F_c < 2499.3+N*1.2$ MHz for $0 \leq N < 157$ are not compatible with SSB positions and cannot be used for 5 MHz n41. + +NOTE 12: This UE channel Bandwidth is optional for uplink in this release of the specification. + +### 6.8.2 DC configuration table + +NR-DC configurations within FR1 are specified in clause 5.5B of TS 38.101-1. In the configuration table, only NR-DC configurations and uplink NR-DC configurations are listed. The bandwidth combination sets for the corresponding inter-band CA, i.e., dual uplink inter-band carrier aggregation with uplink assigned to two NR bands, are applicable to Dual Connectivity. + +EN-DC and NE-DC configurations are specified in clause 5.5B of TS 38.101-3. In the configuration table, in addition to the downlink configurations and uplink configurations, the combinations of intra-band contiguous, non-contiguous and inter-band within FR1 also include the column of “Single UL allowed”. The combination of some frequency bands in the configuration might be a bit problematic due to self-interference, as defined in TS38.306. UE may indicate capability of not supporting simultaneous dual and triple uplink operation due to possible intermodulation interference to its own primary downlink channel bandwidth if the intermodulation order is 2 or if the intermodulation order is 3 for the combinations when both operating bands are between 450 MHz – 960 MHz or between 1427 MHz – 2690 MHz. In case for the EN-DC configurations for which the intermodulation products caused by the dual and triple uplink operation fall into the receive band but do not interfere with the own primary downlink channel bandwidth as defined in Annex-I of TS 38.101-3 the UE is mandated to operate in dual and triple uplink mode. Single Uplink is also allowed for certain band combinations where intermodulation or reverse intermodulation products could create difficulty for meeting emission requirements. For EN-DC and NE-DC combinations of order 3 or higher, “Single Uplink allowed” UL configurations captured in the corresponding order 2 tables apply. As for an example, to mitigate the self-interference issue, the EN-DC configuration DC\_3A\_n78A has specified which band combinations are allowed to stray from the stringent requirement for simultaneous transmission and reception. The uplink needs to alternate between 1.8GHz and 3.5GHz. While 3.5GHz uplink transmission is ongoing, no data should be scheduled by the network on the 1.8GHz LTE carrier. + +Apart from the above EN-DC and NE-DC configurations, TS 38.101-3 also specified inter-band NR-DC configuration between FR1 and FR2. The configurations and bandwidth combination sets for the FR1-FR2 NR-DC combinations are defined in the tables for FR1-FR2 inter-band carrier aggregation. + +In order to reduce the EN-DC, NE-DC and NR-DC configuration table size, the following rules should be applied to the grouping of the configurations. + +- Grouping of DC configurations is based on common band combination. +- In case E-UTRA or/and NR has non-contiguous CA, it will be on a separate row compared to cases when DC configuration has only single carrier or contiguous CA operation. +- Common band combination should be considered as the configurations having the same band sequence, such as DC\_x-y-y\_nz and DC\_x-x-y\_nz are different band combinations, while all configurations with DC\_x-y\_nz(\*) having non-contiguous parts in band nz are considered as common band combination. + +*Examples (EN-DC with NR band having non-contiguous part):* + +| EN-DC configuration | Uplink EN-DC configuration | +|---------------------|----------------------------| +| DC_2A_n258A | DC_2A_n258A | +| DC_2A_n258D | DC_2A_n258D | +| DC_2A_n258G | DC_2A_n258G | +| DC_2A_n258H | DC_2A_n258H | +| DC_2A_n258O | DC_2A_n258O | +| DC_2A_n258P | DC_2A_n258P | +| DC_2A_n258Q | DC_2A_n258Q | +| DC_2A_n258(2A) | DC_2A_n258A | +| DC_2A_n258(3A) | | +| DC_2A_n258(4A) | | +| DC_2A_n258(5A) | | + +*Examples (EN-DC with E-UTRA band having non-contiguous part):* + +| EN-DC configuration | Uplink EN-DC configuration | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------| +| DC_7A_n257A
DC_7A_n257D
DC_7A_n257E
DC_7A_n257F
DC_7A_n257G
DC_7A_n257H
DC_7A_n257I
DC_7A_n257J
DC_7A_n257K
DC_7A_n257L
DC_7A_n257M | DC_7A_n257A
DC_7A_n257D
DC_7A_n257G
DC_7A_n257H
DC_7A_n257I | +| DC_7A-7A_n257A
DC_7A-7A_n257D
DC_7A-7A_n257E
DC_7A-7A_n257F
DC_7A-7A_n257G
DC_7A-7A_n257H
DC_7A-7A_n257I
DC_7A-7A_n257J
DC_7A-7A_n257K
DC_7A-7A_n257L
DC_7A-7A_n257M | DC_7A_n257A
DC_7A_n257D
DC_7A_n257G
DC_7A_n257H
DC_7A_n257I | + +*Examples (NE-DC with E-UTRA band having non-contiguous part):* + +| NE-DC configuration | Uplink NE-DC configuration | +|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| DC_n257A_7A
DC_n257G_7A
DC_n257H_7A
DC_n257I_7A
DC_n257J_7A
DC_n257K_7A
DC_n257L_7A
DC_n257M_7A | DC_n257A_7A | +| DC_n257A_7A-7A
DC_n257G_7A-7A
DC_n257H_7A-7A
DC_n257I_7A-7A
DC_n257J_7A-7A
DC_n257K_7A-7A
DC_n257L_7A-7A
DC_n257M_7A-7A | DC_n257A_7A | + +*Examples (NR-DC with NR band having non-contiguous part):* + +| NR-DC configuration | Uplink NR-DC configuration | +|------------------------------------------------------------------------------|------------------------------------------------------------------------------| +| DC_n3A-n257A
DC_n3A-n257D
DC_n3A-n257G
DC_n3A-n257H
DC_n3A-n257I | DC_n3A-n257A
DC_n3A-n257D
DC_n3A-n257G
DC_n3A-n257H
DC_n3A-n257I | +| DC_n3(2A)-n257A
DC_n3(2A)-n257G
DC_n3(2A)-n257H
DC_n3(2A)-n257I | DC_n3A-n257A
DC_n3A-n257G
DC_n3A-n257I
DC_n3A-n257H | + +*Examples (Incorrect grouping case):* + +| EN-DC configuration | Uplink EN-DC configurationp | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DC_2A_n261A
DC_2A_n261(2A)
DC_2A_n261(3A)
DC_2A_n261(4A) | DC_2A_n261A | +| DC_2A_n261B
DC_2A_n261C
DC_2A_n261D
DC_2A_n261E
DC_2A_n261F
DC_2A_n261G
DC_2A_n261H
DC_2A_n261I
DC_2A_n261J
DC_2A_n261K
DC_2A_n261L
DC_2A_n261M
DC_2A_n261O
DC_2A_n261P
DC_2A_n261Q | DC_2A_n261A
DC_2A_n261B
DC_2A_n261C
DC_2A_n261D
DC_2A_n261E
DC_2A_n261F
DC_2A_n261G
DC_2A_n261H
DC_2A_n261I
DC_2A_n261O
DC_2A_n261P
DC_2A_n261Q | + +In this case, for DC\_2\_n261, the configurations with non-contiguous CA part CA\_n261(\*) such as DC\_2A\_n261(2A), DC\_2A\_n261(3A) and DC\_2A\_n261(4A) are mis-grouped with DC\_2A\_n261A which has only single carrier. They should be revised as follows. + +| EN-DC configuration | Uplink EN-DC configuration | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DC_2A_n261A
DC_2A_n261B
DC_2A_n261C
DC_2A_n261D
DC_2A_n261E
DC_2A_n261F
DC_2A_n261G
DC_2A_n261H
DC_2A_n261I
DC_2A_n261J
DC_2A_n261K
DC_2A_n261L
DC_2A_n261M
DC_2A_n261O
DC_2A_n261P
DC_2A_n261Q | DC_2A_n261A
DC_2A_n261B
DC_2A_n261C
DC_2A_n261D
DC_2A_n261E
DC_2A_n261F
DC_2A_n261G
DC_2A_n261H
DC_2A_n261I
DC_2A_n261O
DC_2A_n261P
DC_2A_n261Q | +| DC_2A_n261(2A)
DC_2A_n261(3A)
DC_2A_n261(4A) | DC_2A_n261A | + +Regarding to the common band combination, it means the configurations having the same band sequence. For example, DC\_x-x-y\_nz and DC\_x-y-y\_nz are not considered as the common band combination. + +Examples (Incorrect understanding of common band combination): + +| EN-DC configuration | Uplink EN-DC configuration | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| DC_2A-66A_n261A
DC_2A-66A_n261G
DC_2A-66A_n261H
DC_2A-66A_n261I
DC_2A-66A_n261J
DC_2A-66A_n261K
DC_2A-66A_n261L
DC_2A-66A_n261M | DC_2A_n261A
DC_66A_n261A
DC_2A_n261G
DC_66A_n261G
DC_2A_n261H
DC_66A_n261H
DC_2A_n261I
DC_66A_n261I | +| DC_2A-2A-66A_n261A
DC_2A-2A-66A_n261G
DC_2A-2A-66A_n261H
DC_2A-2A-66A_n261I
DC_2A-2A-66A_n261J
DC_2A-2A-66A_n261K
DC_2A-2A-66A_n261L
DC_2A-2A-66A_n261M
DC_2A-66A-66A_n261A
DC_2A-66A-66A_n261G
DC_2A-66A-66A_n261H
DC_2A-66A-66A_n261I
DC_2A-66A-66A_n261J
DC_2A-66A-66A_n261K
DC_2A-66A-66A_n261L
DC_2A-66A-66A_n261M | DC_2A_n261A
DC_66A_n261A
DC_2A_n261G
DC_66A_n261G
DC_2A_n261H
DC_66A_n261H
DC_2A_n261I
DC_66A_n261I | + +In this case, the configurations DC\_2-66\_n261, DC\_2-2-66\_n261 and DC\_2-66-66\_n261 are not common band combinations. They should be re-grouped as follows. + +| EN-DC configuration | Uplink EN-DC configuration | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| DC_2A-66A_n261A
DC_2A-66A_n261G
DC_2A-66A_n261H
DC_2A-66A_n261I
DC_2A-66A_n261J
DC_2A-66A_n261K
DC_2A-66A_n261L
DC_2A-66A_n261M | DC_2A_n261A
DC_66A_n261A
DC_2A_n261G
DC_66A_n261G
DC_2A_n261H
DC_66A_n261H
DC_2A_n261I
DC_66A_n261I | +| DC_2A-2A-66A_n261A
DC_2A-2A-66A_n261G
DC_2A-2A-66A_n261H
DC_2A-2A-66A_n261I
DC_2A-2A-66A_n261J
DC_2A-2A-66A_n261K
DC_2A-2A-66A_n261L
DC_2A-2A-66A_n261M | DC_2A_n261A
DC_66A_n261A
DC_2A_n261G
DC_66A_n261G
DC_2A_n261H
DC_66A_n261H
DC_2A_n261I
DC_66A_n261I | +| DC_2A-66A-66A_n261A
DC_2A-66A-66A_n261G
DC_2A-66A-66A_n261H
DC_2A-66A-66A_n261I
DC_2A-66A-66A_n261J
DC_2A-66A-66A_n261K
DC_2A-66A-66A_n261L
DC_2A-66A-66A_n261M | DC_2A_n261A
DC_66A_n261A
DC_2A_n261G
DC_66A_n261G
DC_2A_n261H
DC_66A_n261H
DC_2A_n261I
DC_66A_n261I | + +For the uplink support in the configuration table, the valid uplink configurations are specified that uplink does not have more carriers than downlink. For the UL configuration type, it should be consistent within one row, i.e., there should not be a mixture of contiguous and non-contiguous UL CA within a row. If multiple UL DC configurations are indicated with multiple DL DC configurations, only UL DC configurations with the same or a lower number of carriers in the same fallback group are valid UL configurations. + +#### *Examples:* + +- DC\_5A\_n261G is not a valid uplink configuration for DC\_5A\_n261A. + +- DC\_5A\_n261(2A) and DC\_5A\_n261A are not allowed to be in the same row in the configuration table. + +For the sequence of EN-DC combinations, the following rules apply. + +- EN-DC configurations should be sorted by LTE band combination, then NR band combination. +- LTE combinations should be sorted by the first band number, then the first bandwidth character, then the second band number, then the second bandwidth character and so on. +- The same sort order should be applied for the NR part, there combinations with () should be sorted alphanumerically within the brackets after the contiguous combinations. + +For the sequence of NE-DC combinations, the following rules apply. + +- NE-DC configurations should be sorted by NR band combination, then LTE band combination. +- NR combinations should be sorted by the first band number, then the first bandwidth character, then the second band number, then the second bandwidth character and so on. For the combinations with () should be sorted alphanumerically within the brackets after the contiguous combinations. +- LTE combinations should be sorted by the first band number, then the first bandwidth character, then the second band number, then the second bandwidth character and so on. + +For the sequence of NR-DC combinations, the following rules apply. + +- DC combinations should be sorted by the first band number, then the first bandwidth character, then the second band number, then the second bandwidth character and so on. +- For the combinations with () should be sorted alphanumerically within the brackets after the contiguous combinations. + +#### Examples: + +- DC\_1A\_n77A +- DC\_1A\_n77C +- DC\_1C\_n77A +- DC\_1C-2A\_n77A +- DC\_41A-42A\_n79A +- DC\_41A-42C\_n79A +- DC\_41C-42A\_n79A +- DC\_41C-42C\_n79A +- DC\_41C-42C\_n257A +- DC\_41C-42C\_n257M +- DC\_41C-42C\_n257(2A) +- DC\_41C-42C\_n257(2A-2O) +- DC\_41C-42C\_n257(8A) +- DC\_41C-42C\_n257(D-G) + +### 6.8.3 SUL configuration table + +The SUL band combination with CA in TS 38.101-1 [4] provides the configurations of channel bandwidth, SCS and bandwidth combination set of the bands for each SUL combination. The SUL configuration information is also included in the configuration tables for the allowed SUL configurations supported by the specification. + +For the sake of brevity and to reduce the size of SUL band combination with intra-band contiguous CA, intra-band non-contiguous CA and inter-band CA, instead of showing explicitly in the SUL configuration tables, the SCS info for each NR band and SUL band in the configuration is referred to the channel bandwidths for each NR band in clause 5.3.5 of TS 38.101-1 [4]. Examples: + +For SUL band combination with intra-band non-contiguous CA, Table 6.8.3-1 illustrates that, + +- CA\_n78(2A)-n86A consists of NR band n78 and SUL band n86 whose SCS values are defined in Table 6.8.1-2. For example, for SUL band n86, the supported channel bandwidth in BCS0 is 5MHz, 10MHz, 15MHz and 20MHz where channel bandwidth 5MHz supports SCS with only 15kHz, channel bandwidths 10MHz, 15MHz and 20MHz support all SCS of {15kHz, 30kHz, 60kHz}. +- CA\_n78(2A) with intra-band non-contiguous CA, the configuration is referred to BCS0 defined in clause 5.5.A.2 of TS 38.101-1 for intra-band non-contiguous CA configuration table. +- The SUL configuration for SUL\_n78A-n86A can be referred to Table 6.8.3-4. + +For SUL band combination with intra-band contiguous CA, Table 6.8.3-2 illustrates that, + +- SUL\_n41C-n80A consists of NR band n41 and SUL band n80 whose SCS values are defined in Table 6.8.1-2. For example, for SUL band n80, the supported channel bandwidth in BCS0 is 5MHz, 10MHz, 15MHz, 20MHz, 25MHz, 30MHz and 40MHz where channel bandwidth 5MHz supports SCS with only 15kHz, channel bandwidths 10MHz, 15MHz, 20MHz, 25MHz, 30MHz and 40MHz support all SCS of {15kHz, 30kHz, 60kHz}. +- CA\_n41C with intra-band contiguous CA, the configuration is referred to BCS0 defined in clause 5.5.A.1 of TS 38.101-1 for intra-band contiguous CA configuration table. +- The SUL configuration for SUL\_n41A-n80A can be referred to Table 6.8.3-4. + +For SUL band combination with inter-band CA, Table 6.8.3-3 illustrates that, + +- CA\_n1A\_n78A-n80A consists of NR band n1 and SUL band combination of SUL\_n78A-n80A, whose SCS values are defined in Table 6.8.1-2. For example, for NR band n1, the supported channel bandwidth in BCS0 is 5MHz, 10MHz, 15MHz, 20MHz, 25MHz, 30MHz, 40MHz and 50MHz where channel bandwidth 5MHz supports SCS with only 15kHz, channel bandwidths 10MHz, 15MHz, 20MHz, 25MHz, 30MHz, 40MHz and 50MHz support all SCS of {15kHz, 30kHz, 60kHz}. +- The SUL configuration for SUL\_n78A-n80A can be referred to Table 6.8.3-4. + +**Table 6.8.3-1: Supported channel bandwidths per SUL band combination with intra-band non-contiguous CA** + +| SUL band combination with intra-band non-contiguous CA | SUL configuration | NR Band | Channel bandwidth (MHz) (NOTE 1) | Bandwidth combination set | +|--------------------------------------------------------|-------------------|---------|----------------------------------|---------------------------| +| ... | ... | ... | ... | ... | +| CA_n78(2A)-n86A | SUL_n78A-n86A | n78 | CA_n78(2A)_BCS0 | 0 | +| | | n86 | 5, 10, 15, 20 | | +| ... | ... | ... | ... | ... | + +NOTE 1: The SCS of each channel bandwidth for NR band refers to Table 5.3.5-1. + +**Table 6.8.3-2: Supported channel bandwidths per SUL band combination with intra-band contiguous CA** + +| SUL band combination with CA | SUL configuration | NR Band | Channel bandwidth (MHz) (NOTE 1) | Bandwidth combination set | +|------------------------------|-------------------------------|---------|----------------------------------|---------------------------| +| ... | ... | ... | ... | ... | +| CA_n41C-n80A | SUL_n41A-n80A
CA_n41C-n80A | n41 | CA_n41C_BCS1 | 0 | +| | | n80 | 5, 10, 15, 20, 25, 30, 40 | | +| ... | ... | ... | ... | ... | + +NOTE 1: The SCS of each channel bandwidth for NR band refers to Table 5.3.5-1. + +**Table 6.8.3-3: Supported channel bandwidths per SUL band combination with inter-band CA** + +| SUL band combination with CA | UL configuration | NR Band | Channel bandwidth (MHz) (NOTE 1) | Bandwidth combination set | +|------------------------------|------------------|---------|-------------------------------------------------|---------------------------| +| ... | ... | ... | ... | ... | +| CA_n1A_n78A-n80A | SUL_n78A-n80A | n1 | 5, 10, 15, 20, 25, 30, 40, 50 | 0 | +| | | n78 | 10, 15, 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | | +| | | n80 | 5, 10, 15, 20, 25, 30, 40 | | +| ... | ... | ... | ... | ... | + +**Table 6.8.3-4: Supported channel bandwidths per SUL band combination** + +| SUL configuration | NR Band | Channel bandwidth (MHz) (NOTE 1) | Bandwidth combination set | +|-------------------|---------|-------------------------------------------------|---------------------------| +| ... | ... | ... | ... | +| SUL_n41A-n80A | n41 | 10, 15, 20, 40, 50, 60, 80, 90, 100 | 0 | +| | n80 | 5, 10, 15, 20, 25, 30 | | +| | n41 | 10, 15, 20, 30, 40, 50, 60, 80, 90, 100 | 1 | +| | n80 | 5, 10, 15, 20, 25, 30, 40 | | +| ... | ... | ... | ... | +| SUL_n78A-n80A | n78 | 10, 15, 20, 40, 50, 60, 80, 90, 100 | 0 | +| | n80 | 5, 10, 15, 20, 25, 30 | | +| | n78 | 10, 15, 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | 1 | +| | n80 | 5, 10, 15, 20, 25, 30, 40 | | +| ... | ... | ... | ... | +| SUL_n78A-n86A | n78 | 10, 15, 20, 40, 50, 60, 70, 80, 90, 100 | 0 | +| | n86 | 5, 10, 15, 20 | | +| ... | ... | ... | ... | + +NOTE 1: The SCS of each channel bandwidth for NR band refers to Table 5.3.5-1. + +# 7 Test burden reduction for band combinations + +## 7.1 General + +One of the objectives in this SI is to investigate the feasibility and optimize the specification structure and reduce the test burden. Currently, the main RF requirements related to specific band combinations include maximum output power (MOP), spurious emission for UE-to-UE coexistence, REFSENS and REFSENS exceptions due to harmonic/harmonic mixing/cross band isolation/IMD interference. Obviously, RF requirements for different features on the same band combination have some similarities and dependency. Especially, the RF implementations are similar and RF architectures can be reused for different features on the same band combination. It's very meaningful to study the similarity and dependency of RF requirements for different features on the same band combination and find out the feasibility to further optimize the specification structure and reduce the test burden. For example, CA\_nA-nB (NR CA), DC\_nA-nB (NR-DC), DC\_A\_nB (EN-DC), DC\_B\_nA (EN-DC), DC\_nB\_A (NE-DC), DC\_nA\_B (NE-DC) (different features on same band combination) can use same RF implementation. + +## 7.2 Similarity and Dependency of Tx RF requirements for different features on the same band combination + +### 7.2.1 Maximum output power + +As an example, PC3 MOP requirements for all the UL NR CA, UL NR DC, EN-DC and NE-DC band combinations in table 7.2.1-1 based on the TS 38.101-1-h60 and TS 38.101-3-h60. One band combination may be chosen to verify PC3 MOP testing for some band combinations in same row in table 7.2.1-1, as a result of reducing test burden. It's suggested to randomly choose one band combination that UE support for MOP testing. The proposed test reduction could be considered for an informative annex in the TS since the final decision should be taken by RAN5 based on the industry certification testing needs. + +**Table 7.2.1-1: Band combination PC3 MOP requirements for the same frequency range with different features** + +| Uplink NR CA Configuration | Uplink NR DC Configuration | Uplink EN-DC Configuration | Uplink NE-DC Configuration | Class 3 (dBm) | Tolerance (dB) | +|----------------------------|----------------------------|----------------------------------------------------|----------------------------|---------------|----------------| +| CA_n1A-n3A | DC_n1A-n3A | DC_1A_n3A
DC_3A_n1A
DC_1A_n80A
DC_3A_n84A | DC_n3A_1A | 23 | +2/-3 | +| CA_n1A-n5A | | DC_1A_n5A | | 23 | +2/-3 | +| CA_n1A-n7A | DC_n1A-n7A | DC_1A_n7A
DC_7A_n1A | | 23 | +2/-3 | +| CA_n1A-n8A | | DC_1A_n8A
DC_8A_n1A | DC_n8A_1A | 23 | +2/-3 | +| CA_n1A-n18A | | | | 23 | +2/-3 | +| CA_n1A-n20A | | DC_1A_n20A
DC_20A_n1A | | 23 | +2/-3 | +| CA_n1A-n28A | DC_n1A-n28A | DC_1A_n28A
DC_28A_n1A | DC_n1A_28A | 23 | +2/-3 | +| | | DC_1A_n38A
DC_38A_n1A | | 23 | +2/-3 | +| CA_n1A-n40A | | DC_1A_n40A
DC_40A_n1A | | 23 | +2/-3 | +| CA_n1A-n41A | DC_n1A-n41A | DC_1A_n41A
DC_41A_n1A | | 23 | +2/-3 | +| | | DC_1A_n50A | | 23 | +2/-3 | +| | | DC_1A_n51A | | 23 | +2/-3 | +| | | DC_1A_n71A | | 23 | +2/-3 | +| CA_n1A-n74A | | | | 23 | +2/-3 | +| CA_n1A-n77A | DC_n1A-n77A | DC_1A_n77A
DC_1A_n84A_ULSUP-TDM_n77A | DC_n77A_1A | 23 | +2/-3 | +| CA_n1A-n78A | DC_n1A-n78A | DC_1A_n78A
DC_1A_n84A_ULSUP-TDM_n78A | DC_n78A_1A | 23 | +2/-3 | +| CA_n1A-n79A | DC_n1A-n79A | DC_1A_n79A
DC_1A_n84A_ULSUP-TDM_n79A | | 23 | +2/-3 | +| CA_n2A-n5A | DC_n2A-n5A | DC_2A_n5A
DC_5A_n2A | | 23 | +2/-3 | +| CA_n2A-n7A | | DC_2A_n7A
DC_7A_n2A | | 23 | +2/-3 | +| CA_n2A-n12A | | DC_2A_n12A
DC_12A_n2A | | 23 | +2/-3 | +| CA_n2A-n14A | | DC_14A_n2A | | 23 | +2/-3 | +| | | DC_2A_n25A | | 23 | +2/-3 | +| | | DC_2A_n28A
DC_28A_n2A | | 23 | +2/-3 | +| CA_n2A-n30A | | DC_2A_n30A
DC_30A_n2A | | 23 | +2/-3 | +| | | DC_2A_n38A | | 23 | +2/-3 | +| | | DC_2A_n41A | | 23 | +2/-3 | +| | | DC_2A_n46A | | 23 | +2/-3 | +| CA_n2A-n48A | DC_n2A-n48A | DC_2A_n48A
DC_48A_n2A | | 23 | +2/-3 | +| CA_n2A-n66A | DC_n2A-n66A | DC_2A_n66A
DC_66A_n2A | | 23 | +2/-3 | +| | | DC_2A_n71A
DC_71A_n2A | | 23 | +2/-3 | +| CA_n2A-n77A | DC_n2A-n77A | DC_2A_n77A | | 23 | +2/-3 | +| CA_n2A-n78A | | DC_2A_n78A | | 23 | +2/-3 | +| CA_n3A-n5A | | DC_3A_n5A | | 23 | +2/-3 | +| CA_n3A-n7A | | DC_3A_n7A
DC_7A_n3A
DC_7A_n80A | | 23 | +2/-3 | +| CA_n3A-n8A | | DC_3A_n8A
DC_8A_n3A
DC_8A_n80A | DC_n3A_8A
DC_n8A_3A | 23 | +2/-3 | +| CA_n3A-n18A | | DC_18A_n3A | | 23 | +2/-3 | + +| Uplink NR CA Configuration | Uplink NR DC Configuration | Uplink EN-DC Configuration | Uplink NE-DC Configuration | Class 3 (dBm) | Tolerance (dB) | +|----------------------------|----------------------------|-------------------------------------------------------|----------------------------|---------------|----------------| +| CA_n3A-n20A | | DC_3A_n20A
DC_3A_n82A
DC_20A_n3A
DC_20A_n80A | | 23 | +2/-3 | +| CA_n3A-n28A | DC_n3A-n28A | DC_3A_n28A
DC_28A_n3A | DC_n28A_3A | 23 | +2/-3 | +| CA_n3A-n34A | | | | 23 | +2/-3 | +| CA_n3-n38A | | DC_3A_n38A
DC_38A_n3A | | 23 | +2/-3 | +| CA_n3A-n40A | | DC_3A_n40A | | 23 | +2/-3 | +| CA_n3A-n41A | DC_n3A-n41A | DC_3A_n41A
DC_3A_n80A_ULSUP-TDM_n41
DC_41A_n3A | DC_n41A_3A | 23 | +2/-3 | +| | | DC_3A_n50A | | 23 | +2/-3 | +| | | DC_3A_n51A | | 23 | +2/-3 | +| | | DC_3A_n71A | | 23 | +2/-3 | +| CA_n3A-n74A | | | | 23 | +2/-3 | +| CA_n3A-n77A | DC_n3A-n77A | DC_3A_n77A
DC_3A_n80A_ULSUP-TDM_n77A | DC_n77A_3A | 23 | +2/-3 | +| CA_n3A-n78A | DC_n3A-n78A | DC_3A_n78A
DC_3A_n80A_ULSUP-TDM_n78A | DC_n78A_3A | 23 | +2/-3 | +| CA_n3A-n79A | DC_n3A-n79A | DC_3A_n79A
DC_3A_n80A_ULSUP-TDM_n79A | | 23 | +2/-3 | +| | | DC_4A_n2A | | 23 | +2/-3 | +| | | DC_4A_n5A | | 23 | +2/-3 | +| | | DC_4A_n7A | | 23 | +2/-3 | +| | | DC_4A_n28A | | 23 | +2/-3 | +| | | DC_4A_n38A | | 23 | +2/-3 | +| | | DC_4A_n41A | | 23 | +2/-3 | +| | | DC_4A_n78A | | 23 | +2/-3 | +| CA_n5A-n7A | | DC_5A_n7A
DC_7A_n5A | | 23 | +2/-3 | +| CA_n5A-n12A | | DC_5A_n12A
DC_12A_n5A | | 23 | +2/-3 | +| CA_n5A-n14A | | DC_14A_n5A | | 23 | +2/-3 | +| CA_n5A-n25A | | | | 23 | +2/-3 | +| CA_n5A-n30A | | DC_5A_n30A
DC_30A_n5A | | 23 | +2/-3 | +| | | DC_5A_n38A | | 23 | +2/-3 | +| CA_n5A-n40A | | DC_5A_n40A | | 23 | +2/-3 | +| CA_n5A-n48A | DC_n5A-n48A | DC_5A_n48A
DC_48A_n5A | | 23 | +2/-3 | +| CA_n5A-n66A | DC_n5A-n66A | DC_5A_n66A
DC_66A_n5A | | 23 | +2/-3 | +| | | DC_5A_n71A
DC_71A_n5A | | 23 | +2/-3 | +| CA_n5A-n77A | DC_n5A-n77A | DC_5A_n77A | | 23 | +2/-3 | +| CA_n5A-n78A | | DC_5A_n78A | DC_n78A_5A | 23 | +2/-3 | +| CA_n5A-n79A | | DC_5A_n79A | | 23 | +2/-3 | +| | | DC_7A_n8A
DC_8A_n7A | | 23 | +2/-3 | +| | | DC_7A_n20A
DC_20A_n7A | | 23 | +2/-3 | +| CA_n7A-n25A | | DC_7A_n25A | | 23 | +2/-3 | +| CA_n7A-n28A | | DC_7A_n28A
DC_28A_n7A | | 23 | +2/-3 | +| CA_n7A-n40A | | DC_7A_n40A | | 23 | +2/-3 | +| CA_n7A-n46A | DC_n7A-n46A | | | 23 | +2/-3 | +| | | DC_7A_n51A | | 23 | +2/-3 | + +| Uplink NR CA Configuration | Uplink NR DC Configuration | Uplink EN-DC Configuration | Uplink NE-DC Configuration | Class 3 (dBm) | Tolerance (dB) | +|----------------------------|----------------------------|-----------------------------------------|----------------------------|---------------|----------------| +| CA_n7A-n66A | | DC_7A_n66A
DC_66A_n7A | | 23 | +2/-3 | +| | | DC_7A_n71A | | 23 | +2/-3 | +| CA_n7A-n77A | | DC_7A_n77A | | 23 | +2/-3 | +| CA_n7A-n78A | DC_n7A-n78A | DC_7A_n78A | DC_n78A_7A | 23 | +2/-3 | +| | | DC_7A_n79A | | 23 | +2/-3 | +| | | DC_8A_n2A | | 23 | +2/-3 | +| | | DC_8A_n20A
DC_20A_n8A | | 23 | +2/-3 | +| | | DC_8A_n28A
DC_28A_n8A | DC_n28A_8A | | | +| CA_n8A-n34A | | DC_8A_n34A | | 23 | +2/-3 | +| CA_n8A-n39A | | DC_8A_n39A | | 23 | +2/-3 | +| CA_n8A-n40A | | DC_8A_n40A | | 23 | +2/-3 | +| CA_n8A-n41A | | DC_8A_n41A
DC_8A_n81A_ULSUP-TDM_n41 | DC_n41A_8A | 23 | +2/-3 | +| CA_n8A-n77A | | DC_8A_n77A | DC_n77A_8A | 23 | +2/-3 | +| CA_n8A-n78A | | DC_8A_n78A
DC_8A_n81A_ULSUP-TDM_n78A | DC_n78A_8A | 23 | +2/-3 | +| CA_n8A-n79A | | DC_8A_n79A
DC_8A_n81A_ULSUP-TDM_n79A | | 23 | +2/-3 | +| | | DC_11A_n1A | | 23 | +2/-3 | +| | | DC_11A_n3A | | 23 | +2/-3 | +| | | DC_11A_n28A | | 23 | +2/-3 | +| | | DC_11A_n41A | | 23 | +2/-3 | +| | | DC_11A_n77A | | 23 | +2/-3 | +| | | DC_11A_n78A | | 23 | +2/-3 | +| | | DC_11A_n79A | | 23 | +2/-3 | +| | | DC_12A_n7A | | 23 | +2/-3 | +| | | DC_12A_n25A | | 23 | +2/-3 | +| CA_n12A-n30A | | DC_12A_n30A | | 23 | +2/-3 | +| | | DC_12A_n38A | | 23 | +2/-3 | +| | | DC_12A_n41A | | 23 | +2/-3 | +| CA_n12A-n66A | | DC_12A_n66A
DC_66A_n12A | | 23 | +2/-3 | +| | | DC_12A_n71A | | 23 | +2/-3 | +| CA_n12A-n77A | | DC_12A_n77A | | 23 | +2/-3 | +| | | DC_12A_n78A | | 23 | +2/-3 | +| | | DC_13A_n2A | | 23 | +2/-3 | +| | | DC_13A_n5A | | 23 | +2/-3 | +| | | DC_13A_n7A | | 23 | +2/-3 | +| CA_n13A-n25A | | DC_13A_n25A | | 23 | +2/-3 | +| | | DC_13A_n48A | | 23 | +2/-3 | +| CA_n13A-n66A | | DC_13A_n66A | | 23 | +2/-3 | +| | | DC_13A_n71A | | 23 | +2/-3 | +| CA_n13A-n77A | | DC_13A_n77A | | 23 | +2/-3 | +| | | DC_13A_n78A | | 23 | +2/-3 | +| CA_n14A-n30A | | DC_14A_n30A | | 23 | +2/-3 | +| CA_n14A-n66A | | DC_14A_n66A | | 23 | +2/-3 | +| CA_n14A-n77A | | DC_14A_n77A | | 23 | +2/-3 | +| CA_n18A-n28A | | DC_18A_n28A | | 23 | +2/-3 | + +| Uplink NR CA Configuration | Uplink NR DC Configuration | Uplink EN-DC Configuration | Uplink NE-DC Configuration | Class 3 (dBm) | Tolerance (dB) | +|----------------------------|----------------------------|-------------------------------------------|----------------------------|---------------|----------------| +| CA_n18A-n41A | | DC_18A_n41A | | 23 | +2/-3 | +| CA_n18A-n74A | | | | 23 | +2/-3 | +| CA_n18A-n77A | | DC_18A_n77A | | 23 | +2/-3 | +| CA_n18A-n78A | | DC_18A_n78A | | 23 | +2/-3 | +| | | DC_18A_n79A | | 23 | +2/-3 | +| | | DC_19A_n1A | | 23 | +2/-3 | +| | | DC_19A_n77A | | 23 | +2/-3 | +| | | DC_19A_n78A | | 23 | +2/-3 | +| | | DC_19A_n79A | | 23 | +2/-3 | +| CA_n20A-n28A | | DC_20A_n28A
DC_20A_n83A | DC_n28A_20A | 23 | +2/-3 | +| | | DC_20A_n38A | | 23 | +2/-3 | +| | | DC_20A_n41A | | 23 | +2/-3 | +| | | DC_20A_n50A | | 23 | +2/-3 | +| | | DC_20A_n51A | | 23 | +2/-3 | +| | | DC_20A_n77A | | 23 | +2/-3 | +| CA_n20A-n78A | | DC_20A_n78A
DC_20A_n82A_ULSUP-TDM_n78A | | 23 | +2/-3 | +| | | DC_21A_n1A | | 23 | +2/-3 | +| | | DC_21A_n28A | | 23 | +2/-3 | +| | | DC_21A_n77A | | 23 | +2/-3 | +| | | DC_21A_n78A | | 23 | +2/-3 | +| | | DC_21A_n79A | | 23 | +2/-3 | +| CA_n24A-n41A | | | | 23 | +2/-3 | +| CA_n24A-n48A | | | | 23 | +2/-3 | +| CA_n24A-n77A | | | | 23 | +2/-3 | +| CA_n25A-n38A | | DC_25A_n41A | | 23 | +2/-3 | +| CA_n25A-n41A | | | | 23 | +2/-3 | +| CA_25A-n48A | | DC_48A_n25A | | 23 | +2/-3 | +| CA_n25A-n66A | | DC_66A_n25A | | 23 | +2/-3 | +| CA_n25A-n77A | | DC_25A_n77A | | 23 | +2/-3 | +| CA_n25A-n78A | | DC_25A_n78A | | 23 | +2/-3 | +| | | DC_26A_n25A | | 23 | +2/-3 | +| | | DC_26A_n41A | | 23 | +2/-3 | +| CA_n26A-n66A | | | | 23 | +2/-3 | +| CA_n26A-n70A | | | | 23 | +2/-3 | +| | | DC_26A_n77A | | 23 | +2/-3 | +| | | DC_26A_n78A | DC_n78A_26A | 23 | +2/-3 | +| | | DC_26A_n79A | | 23 | +2/-3 | +| | | DC_28A_n5A | | 23 | +2/-3 | +| CA_n28A-n34A | | | DC_n28A_34A | 23 | +2/-3 | +| CA_n28A-n39A | | | DC_n28A_39A | 23 | +2/-3 | +| CA_n28A-n40A | | DC_28A_n40A | DC_n28A_40A | 23 | +2/-3 | + +| Uplink NR CA Configuration | Uplink NR DC Configuration | Uplink EN-DC Configuration | Uplink NE-DC Configuration | Class 3 (dBm) | Tolerance (dB) | +|----------------------------|----------------------------|--------------------------------------------------------------|----------------------------|---------------|----------------| +| CA_n28A-n41A | DC_n28A-n41A | DC_28A_n41A
DC_28A_n83A_ULSUP-
TDM_n41A
DC_41A_n28A | | 23 | +2/-3 | +| CA_n28A-n46A | DC_n28A-n46A | | | 23 | +2/-3 | +| CA_n28A-n50A | | DC_28A_n50A | | 23 | +2/-3 | +| | | DC_28A_n51A | | 23 | +2/-3 | +| | | DC_28A_n66A
DC_66A_n28A | | 23 | +2/-3 | +| CA_n28A-n74A | | | | 23 | +2/-3 | +| CA_n28A-n77A | DC_n28A-n77A | DC_28A_n77A | | 23 | +2/-3 | +| CA_n28A-n78A | DC_n28A-n78A | DC_28A_n78A
DC_28A_n83A_ULSUP-
TDM_n78A | | 23 | +2/-3 | +| CA_n28A-n79A | DC_n28A-n79A | DC_28A_n79A | | 23 | +2/-3 | +| CA_n34A-n79A | | | | 23 | +2/-3 | +| CA_n30A-n66A | | DC_30A_n66A
DC_66A_n30A | | 23 | +2/-3 | +| CA_n30A-n77A | | DC_30A_n77A | | 23 | +2/-3 | +| CA_n34A-n40A | | | | 23 | +2/-3 | +| CA_n34A-n41A | | | DC_n41A_34A | 23 | +2/-3 | +| | | DC_38A_n8A | | 23 | +2/-3 | +| | | DC_38A_n28A | | 23 | +2/-3 | +| CA_n38A-n66A | | DC_66A_n38A | | 23 | +2/-3 | +| CA_n38A-n78A | | DC_38A_n78A | | 23 | +2/-3 | +| | | DC_38A_n79A | | 23 | +2/-3 | +| CA_n39A-n40A | | DC_39A_n40A | | 23 | +2/-3 | +| CA_n39A-n41A | | DC_39A_n41A | DC_n41A_39A | 23 | +2/-3 | +| | | DC_39A_n78A | | 23 | +2/-3 | +| CA_n39A-n79A | | DC_39A_n79A | | 23 | +2/-3 | +| CA_n40A-n41A | | DC_40A_n41A | DC_n41A_40A | 23 | +2/-3 | +| CA_n40A-n77A | | DC_40A_n77A | | 23 | +2/-3 | +| CA_n40A-n78A | | DC_40A_n78A | | 23 | +2/-3 | +| CA_n40A-n79A | | DC_40A_n79A | | 23 | +2/-3 | +| CA_n41A-n48A | | | | 23 | +2/-3 | +| CA_n41A-n50A | | | | 23 | +2/-3 | +| CA_n41A-n66A | | DC_66A_n41A | | 23 | +2/-3 | +| CA_n41A-n70A | | | | 23 | +2/-3 | +| CA_n41A-n71A | | DC_71A_n41A | | 23 | +2/-3 | +| CA_n41A-n74A | | | | 23 | +2/-3 | + +| Uplink NR CA Configuration | Uplink NR DC Configuration | Uplink EN-DC Configuration | Uplink NE-DC Configuration | Class 3 (dBm) | Tolerance (dB) | +|----------------------------|----------------------------|-----------------------------------------------|----------------------------|---------------|----------------| +| CA_n41A-n77A | DC_n41A-n77A | DC_41A_n77A | | 23 | +2/-3 | +| CA_n41A-n78A | DC_n41A-n78A | DC_41A_n78A | | 23 | +2/-3 | +| CA_n41A-n79A | | DC_41A_n79A | | 23 | +2/-3 | +| | | DC_42A_n1A | | 23 | +2/-3 | +| | | DC_42A_n3A | | 23 | +2/-3 | +| | | DC_42A_n28A | | 23 | +2/-3 | +| | | DC_42A_n51A | | 23 | +2/-3 | +| | | DC_42A_n77A | | 23 | +2/-3 | +| | | DC_42A_n78A | | 23 | +2/-3 | +| | | DC_42A_n79A | | 23 | +2/-3 | +| CA_n46A-n48A | DC_n46A-n48A | | | 23 | +2/-3 | +| CA_n46A-n48B | DC_n46A-n48B | | | 23 | +2/-3 | +| CA_n46A-n78A | DC_n46A-n78A | | | 23 | +2/-3 | +| | | DC_48A_n12A | | 23 | +2/-3 | +| CA_n48A-n66A | DC_n48A-n66A | DC_48A_n66A
DC_66A_n48A | | 23 | +2/-3 | +| CA_n48A-n70A | DC_n48A-n70A | | | 23 | +2/-3 | +| CA_n48A-n71A | DC_n48A-n71A | DC_48A_n71A
DC_71A_n48A | | 23 | +2/-3 | +| CA_n48A-n96A | DC_n48A-n96A | | | 23 | +2/-3 | +| CA_n48B-n96A | DC_n48B-n96A | | | 23 | +2/-3 | +| CA_n48A-n96B | | | | 23 | +2/-3 | +| CA_n50A-n78A | | | | 23 | +2/-3 | +| | | DC_66A_n46A | | 23 | +2/-3 | +| CA_n66A-n71A | | DC_66A_n71A
DC_71A_n66A | | 23 | +2/-3 | +| CA_n66A-n77A | DC_n66A-n77A | DC_66A_n77A | | 23 | +2/-3 | +| CA_n66A-n78A | | DC_66A_n78A
DC_66A_n86A_ULSUP-
TDM_n78A | | 23 | +2/-3 | +| CA_n70A-n71A | | | | 23 | +2/-3 | +| CA_n70A-n78A | | | | 23 | +2/-3 | +| | | DC_71A_n38A | | 23 | +2/-3 | +| CA_n71A-n77A | | | | 23 | +2/-3 | +| CA_n71A-n78A | | DC_71A_n78A | | 23 | +2/-3 | +| CA_n74A-n77A | | | | 23 | +2/-3 | +| CA_n74A-n78A | | | | 23 | +2/-3 | +| CA_n77A-n79A | DC_n77A-n79A | | | 23 | +2/-3 | +| CA_n78A-n79A | | | | 23 | +2/-3 | +| CA_n78A-n92A | | | | 23 | +2/-3 | + +### 7.2.2 Spurious emission for UE-to-UE coexistence + +Generally, if CA\_nA-nB, DC\_A\_nB (DC\_A\_nD), DC\_B\_nA (DC\_B\_nC), DC\_nB\_A, DC\_nA\_B have same spurious emission requirements for UE to UE coexistence, it may not be needed to test the spurious emission requirements for UE to UE coexistence for each UL configuration again and again. Once one of these UL configurations is verified, the other UL configurations for different feature in same band combination can be considered as being capable of meeting these requirements. + +NOTE: Band nC and nD are the corresponding SUL bands with same UL frequency range of band nA and nB, e.g. SUL band n80 has same UL frequency range of band n3. + +## 7.3 Similarity and Dependency of Rx RF requirements for different features on the same band combination + +### 7.3.1 REFSENS exception due to harmonic/harmonic mixing interference for inter-band combinations (two bands) + +For reference sensitivity exception due to harmonic/harmonic mixing specified for ENDC/NEDC band combinations, it's suggested to follow the same principles as for NR CA BCS4 WI in WF R4-2210565 as a starting point. + +### 7.3.2 REFSENS exception due to cross band isolation interference for inter-band combinations (two bands) + +For reference sensitivity exception due to cross band isolation specified for ENDC band combinations, it's suggested to follow the same principles as for NR CA BCS4 WI in WF R4-2210565 as a starting point. + +The following guidelines clarify WF R4-2210565 with regards to specifying MSD test points due to cross-band isolation when the UL band is an FDD band configured for intra-band uplink CA operation. + +Guidelines for cross-band isolation MSD due to FDD band dual uplink intra-band contiguous CA interference: + +#### 1 FDD band intra-band contiguous uplink CA configuration: + +- a) PCC/SCC: the UL CBW, SCS, and UL RB allocation "Lcrb" should be configured to the specified PCC/SCC CBW/SCS/Lcrb of the band's MSD test point. + +For example, for uplink CA\_n5B, the PCC/SCC CBW, SCS and Lcrb should be configured according to the TS38.101-1 Table 7.3A.2.1-1, i.e. CBW: 10MHz+10MHz, SCS:15/15 (kHz), Lcrb:10RB/10RB. + +In case the FDD band UL-CA MSD test point is not specified: + +- i) The PCC/SCC UL CBW shall be set equal. + +If configuring equal CBW is not possible, then set the PCC CBW 5MHz smaller [R4-2320995]. + +- ii) The aggregated UL RB allocation (aka "RBtot") is set equal to the Lcrb specified for the single carrier REFSENS test point that corresponds to the UL-CA aggregated BW. + +Example, for UL-CA 10MHz+10MHz, adopt the Lcrb specified for 20MHz CBW REFSENS [R4-2320995]. + +- iii) The PCC/SCC UL RB allocation "Lcrb" should be configured to ensure equal PSD between across the PCC and the SCC. + +- b) The PCC/SCC UL RBstart shall be configured to create a direct hit collision of the affected DL SCC with the lowest 2UL IMD product. If conditions to create a direct hit collision cannot be met, then configure the PCC/SCC RBstart that results in a partial collision of the lowest 2UL IMD product. +- c) The highest IMD order to be considered is [13]. +- d) Configure the UL carrier frequency closest to the affected DL SCC carrier frequency. +- e) Whenever possible, the UL band configuration should be configured to avoid self-desense. + +In case self-desense cannot be avoided: + +- i) The MSD test point shall not lead to a higher desense than the band's MSD test point (when specified), + - ii) To prevent radio link failure during conformance test, RAN5 should be informed that self-desense may occur on the UL FDD band. +- 2) Affected DL band SCC configuration: +- a) DL SCC carrier frequency: configured closest to the FDD UL-CA carrier. + - b) DL SCC CBW: configured to its smallest supported CBW. + +The following guidelines clarify WF R4-2210565 with regards to specifying MSD test points due to cross-band isolation for SUL and their NR-CA counterparts. + +Guidelines for MSD test points due to cross-band isolation for SUL: + +- For SUL band combinations, and for the first test point which evaluates the MSD for the lowest DL CBW, the SUL band should be configured with the highest supported CBW, as specified in Table 5.5C-1. This ensures that the SUL band lowest IMD order has a maximum reach towards the DL affected band. +- For the second test point, the choice of the SUL CBW remains open to account for exceptions or regional concerns, or to address a proponent's request. +- The SUL SCS should be the lowest SCS that can be supported for the selected SUL CBW. For example, if the SUL CBW is 50 MHz, then SCS15 kHz should be specified. +- For the UL configuration " $L_{\text{crb}}$ " for the SUL band: The UL $L_{\text{crb}}$ of the NR band counterpart as defined in Table 7.3.2-3 (UL configuration for UL Band REFSSENS) for the corresponding SUL band CBW is specified. A SUL-NR counterpart look-up is provided in Table 7.3.2-1. + +**Table 7.3.2-1: SUL-NR counterpart lookup table** + +| SUL band | NR UL Band counterpart | $F_{\text{UL low}} - F_{\text{UL high}}$ (MHz) | +|----------|------------------------|------------------------------------------------| +| n80 | n3 | 1710 – 1785 | +| n81 | n8 | 880 – 915 | +| n82 | n20 | 832 – 862 | +| n83 | n28 | 703 – 748 | +| n84 | n1 | 1920 – 1980 | +| n86 | n66 | 1710 – 1780 | +| n89 | n5 | 824 – 849 | +| n95 | n34 | 2010 – 2025 | +| n97 | n40 | 2300 – 2400 | +| n98 | n39 | 1880 – 1920 | +| n99 | n24 | 1626.5 – 1660.5 | + +- The SUL $RB_{\text{start}}$ should ensure that the UL RBs are positioned closest to the DL affected band. +- The SUL carrier center frequency should be configured closest to the affected DL band. + +### 7.3.3 REFSSENS exception due to inter-modulation distortion for inter-band combinations (two bands) + +MSD due to IMD for NR CA, NR DC, EN-DC and NE-DC band combinations with two bands are shown in table 7.3.3-1 based on the TS 38.101-1 v18.0.0 and TS 38.101-3 v18.0.0. One band combination can be chosen to verify the requirements for some band combinations in same row in table 7.3.3-1, as a result of reducing test burden. It's suggested to randomly choose one band combination that UE support for MSD testing. The final decision should be taken by RAN5 based on the industry certification testing needs. + +**Table 7.3.3-1 Band combination with different features in the same frequency range for PC3 MSD due to IMD interference** + +| NR or E-UTRA Band / Channel bandwidth / N RB / MSD | | | | | | | | Band / Channel bandwidth / N RB / Duplex mode | | | | | | | | Source of IMD | +|----------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-------------------------|----------------|---------------------|-------------------------|----------|-------------------|----------------------------------------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|------------------------------| +| EN-DC Configuration | EUTRA or NR band | UL F c (MHz) | UL/DL BW (MHz) | UL L CRB | DL F c (MHz) | MSD (dB) | IMD order | NR CA band combination | NR band | UL F c (MHz) | UL/DL BW (MHz) | UL L CRB | DL F c (MHz) | MSD (dB) | Duplex mode | | +| DC_1_n3 | 1 | 1950 | 5 | 25 | 2140 | 23 | IMD3 | CA_n1-n3 | n1 | 1950 | 5 | 25 | 2140 | 23 | FDD | IMD 3 | +| | n3 | 1760 | 5 | 25 | 1855 | N/A | N/A | | n3 | 1760 | 5 | 25 | 1855 | N/A | TDD | N/A | +| DC_1A_n8A | 1 | 1965 | 5 | 25 | 2155 | 6.0 | IMD4 | CA_n1-n8 | n1 | 1965 | 5 | 25 | 2155 | 6.0 | FDD | IMD 4 | +| | n8 | 887.5 | 5 | 25 | 932.5 | N/A | N/A | | n8 | 887.5 | 5 | 25 | 932.5 | N/A | FDD | N/A | +| DC_1A_n77A,
DC_1A_SUL_n77A-n84A,
DC_1A_n77(2A), | 1 | 1950 | 5 | 25 | 2140 | 29.8 | IMD2 3 | CA_n1-n77 | 1 | 1950 | 5 | 25 | 2140 | 29.8 | FDD | IMD 24 | +| | n77 | 4090 | 10 | 50 | 4090 | N/A | N/A | | n77 | 4090 | 10 | 50 | 4090 | N/A | TDD | N/A | +| DC_1A_n77A,
DC_1A_SUL_n77A-n84A,
DC_1A_n77(2A),
DC_1A_n77(3A),
DC_1A_n78A,
DC_1A_SUL_n78A-n84A,
DC_1A_n78(2A),
DC_1A_n78(A-C) | 1 | 1950 | 5 | 25 | 2140 | 8.0 | IMD4 3 | CA_n1-n77 | 1 | 1950 | 5 | 25 | 2140 | 8.0 | FDD | IMD 44 | +| | n77,
n78 | 3710 | 10 | 50 | 3710 | N/A | N/A | | n77 | 3710 | 10 | 50 | 3710 | N/A | TDD | N/A | +| DC_2A_n48A | 2 | 1852.5 | 5 | 25 | 1932.5 | 12 | IMD4 | CA_n2-n48 | n2 | 1852.5 | 5 | 25 | 1932.5 | 12 | FDD | IMD 4 | +| | n48 | 3625 | 20 | 100 | 3625 | N/A | N/A | | n48 | 3625 | 20 | 100 | 3625 | N/A | TDD | N/A | +| DC_2A_n66A,
DC_2A-2A_n66A
DC_2A_n66(2A) | 2 | 1855 | 5 | 25 | 1935 | 20 | IMD3 | CA_n2-n66 | n2 | 1855 | 5 | 25 | 1935 | 20 | FDD | IMD 3 | +| | n66 | 1775 | 5 | 25 | 2175 | N/A | N/A | | n66 | 1775 | 5 | 25 | 2175 | N/A | FDD | N/A | +| DC_2A_n66A,
DC_2A-2A_n66A
DC_2A_n66(2A) | 2 | 1883.3 | 5 | 25 | 1963.3 | N/A | N/A | CA_n2-n66 | n2 | 1883.3 | 5 | 25 | 1963.3 | N/A | FDD | N/A | +| | n66 | 1750 | 5 | 25 | 2150 | 4 | IMD5 | | n66 | 1750 | 5 | 25 | 2150 | 4 | FDD | IMD 5 | + +| NR or E-UTRA Band / Channel bandwidth / N RB / MSD | | | | | | | | Band / Channel bandwidth / N RB / Duplex mode | | | | | | | | Source of IMD | +|-----------------------------------------------------------------------------------|--------------------|-------------------------|----------------|---------------------|-------------------------|----------|-------------------|----------------------------------------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|--------------------| +| EN-DC Configuration | EUTRA A or NR band | UL F c (MHz) | UL/DL BW (MHz) | UL L CRB | DL F c (MHz) | MSD (dB) | IMD order | NR CA band combination | NR band | UL F c (MHz) | UL/DL BW (MHz) | UL C LRB | DL F c (MHz) | MSD (dB) | Duplex mode | | +| DC_2A_n77A
DC_2A_n77(2A)
DC_2A-2A_n77A
DC_2A_n77(2A)
DC_2A-2A_n77(2A) | 2 | 1855 | 5 | 25 | 1935 | 26 | IMD2 | CA_n2-n77 | n2 | 1855 | 5 | 25 | 1935 | 26 | FDD | IMD 2 | +| | n77 | 3790 | 10 | 50 | 3790 | N/A | N/A | | n77 | 3790 | 10 | 50 | 3790 | N/A | TDD | N/A | +| | 2 | 1900 | 5 | 25 | 1980 | 8.0 | IMD4 | CA_n2-n77 | n2 | 1900 | 5 | 25 | 1980 | 8.0 | FDD | IMD 4 | +| | n77 | 3720 | 10 | 50 | 3720 | N/A | N/A | | n77 | 3720 | 10 | 50 | 3720 | N/A | TDD | N/A | +| | 2 | 1885 | 5 | 25 | 1965 | 5 | IMD5 | CA_n2-n77 | n2 | 1885 | 5 | 25 | 1965 | 5 | FDD | IMD 5 | +| | n77 | 3810 | 10 | 50 | 3810 | N/A | N/A | | n77 | 3810 | 10 | 50 | 3810 | N/A | TDD | N/A | +| DC_2A_n78A
DC_2A_n78(2A)
DC_2A-2A_n78(2A) | 2 | 1855 | 5 | 25 | 1935 | 26 | IMD2 3 | CA_n2-n78 | n2 | 1855 | 5 | 25 | 1935 | 26 | FDD | IMD 2 4 | +| | n78 | 3790 | 10 | 50 | 3790 | N/A | N/A | | n78 | 3790 | 10 | 50 | 3790 | N/A | TDD | N/A | +| DC_3_n1 | 3 | 1760 | 5 | 25 | 1855 | N/A | N/A | CA_n1-n3 | n1 | 1950 | 5 | 25 | 2140 | 23 | FDD | IMD 3 | +| | n1 | 1950 | 5 | 25 | 2140 | 23 | IMD3 | | n3 | 1760 | 5 | 25 | 1855 | N/A | TDD | N/A | +| DC_3_n5 | 3 | 1771 | 10 | 50 | 1866 | 4 | IMD4 | CA_n3-n5 | n3 | 1771 | 10 | 50 | 1866 | 4 | FDD | IMD 4 | +| | n5 | 838 | 5 | 25 | 883 | N/A | N/A | | n5 | 838 | 5 | 25 | 883 | N/A | FDD | N/A | +| | 3 | 1721 | 10 | 50 | 1816 | N/A | N/A | CA_n3-n5 | n3 | 1721 | 10 | 50 | 1816 | N/A | FDD | N/A | +| | n5 | 838 | 5 | 25 | 883 | 24 | IMD2 3 | | n5 | 838 | 5 | 25 | 883 | 24 | FDD | IMD 2 3 | +| DC_3A_n7A
DC_3C_n7A | 3 | 1730 | 5 | 25 | 1825 | N/A | N/A | CA_n3-n7 | n3 | 1730 | 5 | 25 | 1825 | N/A | FDD | N/A | +| | n7 | 2535 | 10 | 50 | 2655 | 10.2 | IMD4 | | n7 | 2535 | 10 | 50 | 2655 | 10.2 | FDD | IMD 4 | +| DC_3_n8 | n8 | 900 | 5 | 25 | 945 | 8 | IMD4 3 | CA_n3-n8 | n3 | 1755 | 10 | 50 | 1850 | N/A | FDD | N/A | +| | 3 | 1755 | 10 | 50 | 1850 | N/A | N/A | | n8 | 900 | 5 | 25 | 945 | 8 | FDD | IMD 4 4 | +| | n8 | 897.5 | 5 | 25 | 942.5 | N/A | N/A | CA_n3-n8 | n3 | 1747.5 | 10 | 50 | 1842.5 | 6.4 | FDD | IMD 5 | + +| NR or E-UTRA Band / Channel bandwidth / N RB / MSD | | | | | | | | Band / Channel bandwidth / N RB / Duplex mode | | | | | | | | Source of IMD | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-------------------------|----------------|---------------------|-------------------------|----------|-------------------|----------------------------------------------------------|-------------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|---------------------| +| EN-DC Configuration | EUTRA A or NR band | UL F c (MHz) | UL/DL BW (MHz) | UL L CRB | DL F c (MHz) | MSD (dB) | IMD order | NR CA band combination | NR band | UL F c (MHz) | UL/DL BW (MHz) | UL L CRB | DL F c (MHz) | MSD (dB) | Duplex mode | | +| | 3 | 1747.5 | 10 | 50 | 1842.5 | 6.4 | IMD5 | | n8 | 897.5 | 5 | 25 | 942.5 | N/A | FDD | N/A | +| DC_3A_n26A | 3 | 1771 | 10 | 50 | 1866 | 4 | IMD4 | CA_n3-n26 | n3 | 1771 | 5 | 25 | 1866 | 4 | FDD | IMD 4 | +| | n26 | 838 | 5 | 25 | 883 | N/A | N/A | | n26 | 838 | 5 | 25 | 883 | N/A | FDD | N/A | +| | 3 | 1721 | 10 | 50 | 1816 | N/A | N/A | CA_n3-n26 | n3 | 1721 | 5 | 25 | 1816 | N/A | FDD | N/A | +| | n26 | 838 | 5 | 25 | 883 | 24 | IMD2 3 | | n26 | 838 | 5 | 25 | 883 | 26 | FDD | IMD 2 11 | +| DC_3A_n38A | 3 | 1712.8 | 5 | 25 | 1807.8 | 8.2 | IMD4 | CA_n3-n38 | n3 | 1713 | 5 | 25 | 1808 | 8.2 | FDD | IMD 4 | +| | n38 | 2616.7 | 10 | 50 | 2616.7 | N/A | N/A | | n38 | 2617 | 5 | 25 | 2617 | N/A | TDD | N/A | +| DC_3A_n41A
DC_3C_n41A
DC_3A_SUL_n41A-n80A,
DC_3C_SUL_n41A-n80A | 3 | 1740 | 5 | 25 | 1835 | 8.2 | IMD4 | CA_n3-n41 | n3 | 1740 | 5 | 25 | 1835 | 8.2 | FDD | IMD 4 | +| | n41 | 2657.5 | 10 | 50 | 2657.5 | N/A | N/A | | n41 | 2657.5 | 10 | 50 | 2657.5 | N/A | TDD | N/A | +| DC_3A_n77A,
DC_3A_n77(2A),
DC_3A_n77(3A),
DC_3A_SUL_n77A-n80A,
DC_3A_n78A,
DC_3A_SUL_n78A-n80A,
DC_3A_n78(2A),
DC_3A_n78(A-C),
DC_3C_n78A
DC_3C_n78(2A) | 3 | 1740 | 5 | 25 | 1835 | 26 | IMD2 3 | CA_n3-n77
CA_n3-n78 | n3 | 1740 | 5 | 25 | 1835 | 26 | FDD | IMD 2 4 | +| | n77,
n78 | 3575 | 10 | 50 | 3575 | N/A | N/A | | n77,
n78 | 3575 | 10 | 50 | 3575 | N/A | TDD | N/A | + +| NR or E-UTRA Band / Channel bandwidth / N RB / MSD | | | | | | | | Band / Channel bandwidth / N RB / Duplex mode | | | | | | | | Source of IMD | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-------------------------|----------------|---------------------|-------------------------|----------|-------------------|----------------------------------------------------------|----------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|-------------------| +| EN-DC Configuration | EUTRA A or NR band | UL F c (MHz) | UL/DL BW (MHz) | UL C LRB | DL F c (MHz) | MSD (dB) | IMD order | NR CA band combination | NR band | UL F c (MHz) | UL/DL BW (MHz) | UL C LRB | DL F c (MHz) | MSD (dB) | Duplex mode | | +| DC_3A_n77A,
DC_3A_n77(2A),
DC_3C_n77A,
DC_3C_n77(2A),
DC_3A_SUL_n77A-n80A,
DC_3A_n78A,
DC_3A_SUL_n78A-n80A,
DC_3A_n78(2A),
DC_3C_n78A,
DC_3C_n78(2A) | 3 | 1765 | 5 | 25 | 1860 | 8.0 | IMD4 3 | CA_n3-n77
CA_n3-n78 | n3 | 1740 | 5 | 25 | 1835 | 26 | FDD | IMD 24 | +| | n77, n78 | 3435 | 10 | 50 | 3435 | N/A | N/A | | n77, n78 | 3575 | 10 | 50 | 3575 | N/A | TDD | N/A | +| DC_5A_n3A | 5 | 838 | 5 | 25 | 883 | N/A | N/A | CA_n3-n5 | n3 | 1771 | 10 | 50 | 1866 | 4 | FDD | IMD 4 | +| | n3 | 1771 | 10 | 50 | 1866 | 4 | IMD4 | | n5 | 838 | 5 | 25 | 883 | N/A | FDD | N/A | +| | 5 | 838 | 5 | 25 | 883 | 24 | IMD2 3 | CA_n3-n5 | n3 | 1721 | 10 | 50 | 1816 | N/A | FDD | N/A | +| | n3 | 1721 | 10 | 50 | 1816 | N/A | N/A | | n5 | 838 | 5 | 25 | 883 | 24 | FDD | IMD 23 | +| DC_5_n7 | n7 | 2547 | 10 | 50 | 2667 | N/A | N/A | CA_n5-n7 | n5 | 834 | 5 | 25 | 879 | 12 | FDD | IMD 34 | +| | 5 | 834 | 5 | 25 | 879 | 12 | IMD3 3 | | n7 | 2547 | 10 | 50 | 2667 | N/A | FDD | N/A | +| DC_5A_n66A | 5 | 838 | 5 | 25 | 883 | 30 | IMD2 3 | CA_n5-n66 | n5 | 838 | 5 | 25 | 883 | 30 | FDD | IMD 24 | +| | n66 | 1721 | 5 | 25 | 2121 | N/A | N/A | | n66 | 1721 | 5 | 25 | 2121 | N/A | FDD | N/A | +| DC_5A_n77A 8
DC_5A_n77(2A) 8
DC_5A_n77(3A) 8 | 5 | 844 | 5 | 25 | 889 | 8.3 | IMD4 | CA_n5-n77 13 | n5 | 844 | 5 | 25 | 889 | 8.3 | FDD | IMD 4 | +| | n77 | 3421 | 10 | 50 | 3421 | N/A | N/A | | n77 | 3421 | 10 | 50 | 3421 | N/A | TDD | N/A | +| | 5 | 826.5 | 5 | 25 | 871.5 | 5.5 | IMD5 | CA_n5-n77 13 | n5 | 829 | 5 | 25 | 874 | 5.5 | FDD | IMD 5 | +| | n77 | 4177.5 | 10 | 50 | 4177.5 | N/A | N/A | | n77 | 4190 | 10 | 50 | 4190 | N/A | TDD | N/A | +| DC_5A_n78A
DC_5A_n78(2A)
DC_5A_n78(A-C)
DC_5A_n78C | 5 | 844 | 5 | 25 | 889 | 8.3 | IMD4 | CA_n5-n78 | n5 | 844 | 5 | 25 | 889 | 8.3 | FDD | IMD 4 | + +| NR or E-UTRA Band / Channel bandwidth / N RB / MSD | | | | | | | | Band / Channel bandwidth / N RB / Duplex mode | | | | | | | | Source of IMD | +|---------------------------------------------------------------------------------------------------------------------|--------------------|-------------------------|----------------|---------------------|-------------------------|----------|-------------------|----------------------------------------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|---------------------| +| EN-DC Configuration | EUTRA A or NR band | UL F c (MHz) | UL/DL BW (MHz) | UL C LRB | DL F c (MHz) | MSD (dB) | IMD order | NR CA band combination | NR band | UL F c (MHz) | UL/DL BW (MHz) | UL C LRB | DL F c (MHz) | MSD (dB) | Duplex mode | | +| DC_7_n3 | n78 | 3421 | 10 | 50 | 3421 | N/A | N/A | CA_n3-n7 | n78 | 3421 | 10 | 50 | 3421 | N/A | TDD | N/A | +| | 7 | 2535 | 10 | 50 | 2655 | 13 | IMD4 | | n3 | 1730 | 5 | 25 | 1825 | N/A | FDD | N/A | +| | n3 | 1730 | 5 | 25 | 1825 | N/A | N/A | | n7 | 2535 | 10 | 50 | 2655 | 10.2 | FDD | IMD 4 | +| DC_7_n5 | 7 | 2547 | 10 | 50 | 2667 | N/A | N/A | CA_n5-n7 | n5 | 834 | 5 | 25 | 879 | 12 | FDD | IMD 3 4 | +| | n5 | 834 | 5 | 25 | 879 | 12 | IMD3 3 | | n7 | 2547 | 10 | 50 | 2667 | N/A | FDD | N/A | +| DC_7A_n26A
DC_7C_n26A | 7 | 2547 | 10 | 50 | 2667 | N/A | N/A | CA_n7-n26 | n7 | 2556 | 5 | 25 | 2676 | N/A | FDD | N/A | +| | n26 | 834 | 5 | 25 | 879 | 12 | IMD3 3 | | n26 | 837 | 5 | 25 | 882 | 16.0 | FDD | IMD 3 11 | +| | 7 | 2567.5 | 5 | 25 | 2687.5 | 2.5 | IMD5 | CA_n7-n26 | n7 | 2567.5 | 5 | 25 | 2687.5 | 2.5 | FDD | IMD 5 | +| | n26 | 816.5 | 5 | 25 | 861.5 | N/A | N/A | | n26 | 816.5 | 5 | 25 | 861.5 | N/A | FDD | N/A | +| DC_7_n40 | 7 | 2510 | 5 | 25 | 2630 | 23 | IMD3 | CA_n7-n40 | n7 | 2510 | 5 | 25 | 2630 | 23 | FDD | IMD 3 | +| | n40 | 2390 | 5 | 25 | 2390 | N/A | N/A | | n40 | 2390 | 5 | 25 | 2390 | N/A | TDD | N/A | +| DC_7A_n66A
DC_7A-7A_n66A
DC_7C_n66A | 7 | 2535 | 10 | 50 | 2655 | 15 | IMD4 | CA_n7-n66 | n7 | 2535 | 10 | 50 | 2655 | 15 | FDD | IMD 4 | +| | n66 | 1730 | 5 | 25 | 2130 | N/A | N/A | | n66 | 1730 | 5 | 25 | 2130 | N/A | FDD | N/A | +| DC_7A_n77A
DC_7A-7A_n77(2A)
DC_7A-7A_n77(3A)
DC_7A_n77(2A)
DC_7A_n77(3A)
DC_7C_n77A
DC_7C_n77(2A) | 7 | 2540 | 5 | 25 | 2660 | 7.1 | IMD4 | CA_n7-n77 | n7 | 2540 | 5 | 25 | 2660 | 7.1 | FDD | IMD 4 | +| | n77 | 3870 | 10 | 50 | 3870 | N/A | N/A | | n77 | 3870 | 10 | 50 | 3870 | N/A | TDD | N/A | +| DC_8A_n1A | 8 | 887.5 | 5 | 25 | 932.5 | N/A | N/A | CA_n1-n8 | n1 | 1965 | 5 | 25 | 2155 | 6.0 | FDD | IMD 4 | +| | n1 | 1965 | 5 | 25 | 2155 | 6 | IMD4 | | n8 | 887.5 | 5 | 25 | 932.5 | N/A | FDD | N/A | +| DC_8A_n3A | 8 | 900 | 5 | 25 | 945 | 8 | IMD4 3 | CA_n3-n8 | n3 | 1755 | 10 | 50 | 1850 | N/A | FDD | N/A | +| | n3 | 1755 | 10 | 50 | 1850 | N/A | N/A | | n8 | 900 | 5 | 25 | 945 | 8 | FDD | IMD 4 4 | + +| NR or E-UTRA Band / Channel bandwidth / N RB / MSD | | | | | | | | Band / Channel bandwidth / N RB / Duplex mode | | | | | | | | Source of IMD | +|-----------------------------------------------------------------------------------------------------|--------------------|-------------------------|----------------|---------------------|-------------------------|----------|-------------------|----------------------------------------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|--------------------| +| EN-DC Configuration | EUTRA A or NR band | UL F c (MHz) | UL/DL BW (MHz) | UL L CRB | DL F c (MHz) | MSD (dB) | IMD order | NR CA band combination | NR band | UL F c (MHz) | UL/DL BW (MHz) | UL C LRB | DL F c (MHz) | MSD (dB) | Duplex mode | | +| DC_8A_n41A
DC_8A_SUL_n41A-n81A | 8 | 897.5 | 5 | 25 | 942.5 | N/A | N/A | CA_n3-n8 | n3 | 1747.5 | 10 | 50 | 1842.5 | 6.4 | FDD | IMD 5 | +| | n3 | 1747.5 | 10 | 50 | 1842.5 | 6.4 | IMD5 | | n8 | 897.5 | 5 | 25 | 942.5 | N/A | FDD | N/A | +| DC_8A_n41A
DC_8A_SUL_n41A-n81A | 8 | 882.5 | 5 | 25 | 927.5 | 12.1 | IMD3 3 | CA_n8-n41 | n8 | 882.5 | 5 | 25 | 927.5 | 12.1 | FDD | IMD 3 4 | +| | n41 | 2685 | 10 | 50 | 2685 | N/A | N/A | | n41 | 2685 | 10 | 50 | 2685 | N/A | TDD | N/A | +| DC_8A_n77A,
DC_8A_n78A,
DC_8B_n78A
DC_8A_n78(2A),
DC_8A_n77(3A),
DC_8A_SUL_n78A-n81A | 8 | 897.5 | 5 | 25 | 942.5 | 8.3 | IMD4 | CA_n8-n78 | n8 | 897.5 | 5 | 25 | 942.5 | 8.3 | FDD | IMD 4 | +| | n77,
n78 | 3635 | 10 | 50 | 3635 | N/A | N/A | | n78 | 3635 | 10 | 50 | 3635 | N/A | TDD | N/A | +| DC_8A_n79A,
DC_8A_n79C,
DC_8A_SUL_n79A-n81A | 8 | 897.5 | 5 | 25 | 942.5 | 4.8 | IMD5 | CA_n8-n79 | n8 | 897.5 | 5 | 25 | 942.5 | 4.8 | FDD | IMD 5 | +| | n79 | 4532.5 | 40 | 216 | 4532.5 | N/A | N/A | | n79 | 4532.5 | 40 | 216 | 4532.5 | N/A | TDD | N/A | +| DC_12A_n77A
DC_12A_n77(2A) | 12 | 702 | 5 | 20 | 732 | 5.5 | IMD5 | CA_n12-n77 | n12 | 702 | 5 | 20 | 732 | 5.5 | FDD | IMD 5 | +| | n77 | 3540 | 10 | 50 | 3540 | N/A | N/A | | n77 | 3540 | 10 | 50 | 3540 | N/A | TDD | N/A | +| DC_13A_n77A | 13 | 784.5 | 5 | 20 | 753.5 | 5.5 | IMD5 | CA_n13-n77 | n13 | 782 | 5 | 20 | 751 | 5.5 | FDD | IMD 5 | +| | n77 | 3891.5 | 10 | 50 | 3891.5 | N/A | N/A | | n77 | 3880 | 10 | 50 | 3880 | N/A | TDD | N/A | +| DC_14A_n5A | 14 | 791 | 5 | 25 | 761 | N/A | N/A | CA_n5-n14 | n5 | 836 | 5 | 25 | 881 | 25 | FDD | IMD 3 4 | +| | n5 | 836 | 5 | 25 | 881 | 25 | IMD3 | | n14 | 791 | 5 | 25 | 761 | N/A | FDD | N/A | +| | 14 | 795.5 | 5 | 25 | 765.5 | 25 | IMD3 | CA_n5-n14 | n5 | 826.5 | 5 | 25 | 871.5 | N/A | FDD | N/A | +| | n5 | 826.5 | 5 | 25 | 871.5 | N/A | N/A | | n14 | 795.5 | 5 | 25 | 765.5 | 25 | FDD | IMD 3 | +| DC_14A_n77A
DC_14A_n77(2A) | 14 | 795.5 | 5 | 15 | 765.5 | 5.5 | IMD5 | CA_n14-n77 | n14 | 793 | 5 | 20 | 763 | 5.5 | FDD | IMD 5 | +| | n77 | 3947.5 | 10 | 50 | 3947.5 | N/A | N/A | | n77 | 3935 | 10 | 50 | 3935 | N/A | TDD | N/A | +| DC_18A_n3A | 18 | 823 | 5 | 25 | 868 | N/A | N/A | CA_n3-n18 | n18 | 818 | 5 | 25 | 863 | N/A | FDD | N/A | + +| NR or E-UTRA Band / Channel bandwidth / N RB / MSD | | | | | | | | Band / Channel bandwidth / N RB / Duplex mode | | | | | | | | Source of IMD | +|------------------------------------------------------------------------------------------------------|--------------------|-------------------------|----------------|---------------------|-------------------------|----------|-----------|----------------------------------------------------------|----------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|--------------------| +| EN-DC Configuration | EUTRA A or NR band | UL F c (MHz) | UL/DL BW (MHz) | UL L CRB | DL F c (MHz) | MSD (dB) | IMD order | NR CA band combination | NR band | UL F c (MHz) | UL/DL BW (MHz) | UL C LRB | DL F c (MHz) | MSD (dB) | Duplex mode | | +| | n3 | 1721 | 5 | 25 | 1816 | 4 | IMD4 | | n3 | 1731 | 5 | 25 | 1826 | 4 | FDD | IMD 4 | +| DC_18A_n77A
DC_18A_n78A | 18 | N/A | N/A | N/A | N/A | N/A | IMD4 | CA_n18-n77 9
CA_n18-n78 9 | n18 | N/A | N/A | N/A | N/A | N/A | FDD | IMD 4 | +| | n77, n78 | N/A | N/A | N/A | N/A | N/A | N/A | | n77, n78 | N/A | N/A | N/A | N/A | N/A | TDD | N/A | +| DC_20A_n3A | 20 | 840 | 5 | 25 | 799 | N/A | N/A | CA_n3-n20 | 3 | 1775 | 5 | 25 | 1870 | 4 | FDD | IMD 4 | +| | n3 | 1775 | 5 | 25 | 1870 | 4 | IMD4 | | 20 | 840 | 5 | 25 | 799 | N/A | FDD | N/A | +| | 20 | 847 | 5 | 25 | 806 | 9 | IMD4 | | 3 | 1735 | 5 | 25 | 1830 | N/A | FDD | N/A | +| | n3 | 1735 | 5 | 25 | 1830 | N/A | N/A | | 20 | 847 | 5 | 25 | 806 | 9 | FDD | IMD 4 | +| DC_20A_n77A,
DC_20A_n78A
DC_20A_n78C 7 ,
DC_20A_n78(2A),
DC_20A_SUL_n78A-n82A | 20 | 850 | 5 | 25 | 809 | 11 | IMD4 | CA_n20-n78 | n20 | 850 | 5 | 25 | 809 | 11 | FDD | IMD 4 | +| | n77, n78 | 3359 | 10 | 50 | 3359 | N/A | N/A | | n78 | 3359 | 10 | 50 | 3359 | N/A | TDD | N/A | +| DC_25A_n77A
DC_25A-25A_n77A | 25 | 1855 | 5 | 25 | 1935 | 26 | IMD2 | CA_n25-n77 | n25 | 1855 | 5 | 25 | 1935 | 26 | FDD | IMD 2 | +| | n77 | 3790 | 10 | 50 | 3790 | N/A | N/A | | n77 | 3790 | 10 | 50 | 3790 | N/A | TDD | N/A | +| | 25 | 1900 | 5 | 25 | 1980 | 8 | IMD4 | | n25 | 1900 | 5 | 25 | 1980 | 8.0 | FDD | IMD 4 | +| | n77 | 3720 | 10 | 50 | 3720 | N/A | N/A | | n77 | 3690 | 10 | 50 | 3690 | N/A | TDD | N/A | +| | 25 | 1885 | 5 | 25 | 1965 | 5 | IMD5 | | n25 | 1885 | 5 | 25 | 1965 | 5 | FDD | IMD 5 | +| | n77 | 3810 | 10 | 50 | 3810 | N/A | N/A | | n77 | 3790 | 10 | 50 | 3790 | N/A | TDD | N/A | +| DC_25A_n78A
DC_25A-25A_n78A | 25 | 1855 | 5 | 25 | 1935 | 26 | IMD2 | CA_n25-n78 | n25 | 1855 | 5 | 25 | 1935 | 26 | FDD | IMD 2 4 | +| | n78 | 3790 | 10 | 50 | 3790 | N/A | N/A | | n78 | 3790 | 10 | 50 | 3790 | N/A | TDD | N/A | +| DC_28_n50 | 28 | 730 | 10 | 50 | 775 | 15.3 | IMD 2 | CA_n28-n50 | n28 | 730 | 10 | 50 | 775 | 15.3 | FDD | IMD 2 | +| | n50 | 1500 | 10 | 50 | 1500 | N/A | N/A | | n50 | 1500 | 10 | 50 | 1500 | N/A | TDD | N/A | +| | 28 | 740 | 10 | 50 | 785 | 6 | IMD 4 | CA_n28-n50 | n28 | 740 | 10 | 50 | 785 | 6.0 | FDD | IMD 4 4 | + +| NR or E-UTRA Band / Channel bandwidth / N RB / MSD | | | | | | | | Band / Channel bandwidth / N RB / Duplex mode | | | | | | | | Source of IMD | +|-------------------------------------------------------------------------|--------------------|-------------------------|----------------|---------------------|-------------------------|----------|-----------|----------------------------------------------------------|-------------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|---------------| +| EN-DC Configuration | EUTRA A or NR band | UL F c (MHz) | UL/DL BW (MHz) | UL L CRB | DL F c (MHz) | MSD (dB) | IMD order | NR CA band combination | NR band | UL F c (MHz) | UL/DL BW (MHz) | UL L CRB | DL F c (MHz) | MSD (dB) | Duplex mode | | +| | n50 | 1500 | 10 | 50 | 1500 | N/A | N/A | | n50 | 1500 | 10 | 50 | 1500 | N/A | TDD | N/A | +| DC_26A_n77A,
DC_26A_n78A | 26 | 836.5 | 5 | 25 | 881.5 | 11.1 | IMD4 | CA_n26-n78 | n26 | 836.5 | 5 | 25 | 881.5 | 11.1 | FDD | IMD 4 | +| | n77,
n78 | 3391 | 10 | 50 | 3391 | N/A | N/A | | n78 | 3391 | 10 | 50 | 3391 | N/A | TDD | N/A | +| DC_28A_n77A,
DC_28A_n78A,
DC_28A_n78(2A),
DC_28A_SUL_n78A-n83A | 28 | 705.5 | 5 | 25 | 760.5 | 5.5 | IMD5 | CA_n28-n77 | n28 | 705.5 | 5 | 25 | 760.5 | 5.5 | FDD | IMD 5 | +| | n77,
n78 | 3582.5 | 10 | 50 | 3582.5 | N/A | N/A | | n77/
n78 | 3582.5 | 10 | 50 | 3582.5 | N/A | TDD | N/A | +| DC_30A_n77A
DC_30A_n77(2A) | 30 | 2310 | 5 | 25 | 2355 | 8.0 | IMD4 | CA_n30-n77 | n30 | 2310 | 5 | 25 | 2355 | 8.0 | FDD | IMD 4 | +| | n77 | 3487.5 | 10 | 50 | 3487.5 | N/A | N/A | | n77 | 3487.5 | 10 | 50 | 3487.5 | N/A | TDD | N/A | +| DC_38A_n3A | n3 | 1713 | 5 | 25 | 1808 | 8.2 | IMD4 | CA_n3-n38 | n3 | 1713 | 5 | 25 | 1808 | 8.2 | FDD | IMD 4 | +| | 38 | 2617 | 5 | 25 | 2617 | N/A | N/A | | n38 | 2617 | 5 | 25 | 2617 | N/A | TDD | N/A | +| DC_41A_n3A
DC_41C_n3A | n3 | 1740 | 5 | 25 | 1835 | 8.2 | IMD4 | CA_n3-n41 | n3 | 1740 | 5 | 25 | 1835 | 8.2 | FDD | IMD 4 | +| | 41 | 2657.5 | 5 | 25 | 2657.5 | N/A | N/A | | n41 | 2657.5 | 10 | 50 | 2657.5 | N/A | TDD | N/A | +| DC_48A_n2A
DC_48C_n2A
DC_48D_n2A
DC_48E_n2A | 48 | 3625 | 20 | 100 | 3625 | N/A | N/A | CA_n2-n48 | n2 | 1852.5 | 5 | 25 | 1932.5 | 12 | FDD | IMD 4 | +| | n2 | 1852.5 | 5 | 25 | 1932.5 | 12 | IMD4 | | n48 | 3625 | 20 | 100 | 3625 | N/A | TDD | N/A | +| DC_48A_n25A
DC_48C_n25A
DC_48D_n25A | 48 | 3625 | 20 | 100 | 3625 | N/A | N/A | CA_n25-n48 | n25 | 1852.5 | 5 | 25 | 1932.5 | 12 | FDD | IMD 4 | +| | n25 | 1852.5 | 5 | 25 | 1932.5 | 12 | IMD4 | | n48 | 3625 | 20 | 100 | 3625 | N/A | TDD | N/A | +| DC_48A_n66A
DC_48C_n66A
DC_48D_n66A | 48 | 3630 | 20 | 100 | 3630 | N/A | N/A | CA_n48-n66 | n48 | 3660 | 5 | 25 | 3660 | N/A | TDD | N/A | +| | n66 | 1715 | 5 | 25 | 2115 | 4 | IMD5 | | n66 | 1730 | 5 | 25 | 2130 | 5.0 | FDD | IMD 5 | + +| NR or E-UTRA Band / Channel bandwidth / N RB / MSD | | | | | | | | Band / Channel bandwidth / N RB / Duplex mode | | | | | | | | Source of IMD | +|--------------------------------------------------------------------|--------------------|-------------------------|----------------|---------------------|-------------------------|----------|-------------------|----------------------------------------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|--------------------| +| EN-DC Configuration | EUTRA A or NR band | UL F c (MHz) | UL/DL BW (MHz) | UL L CRB | DL F c (MHz) | MSD (dB) | IMD order | NR CA band combination | NR band | UL F c (MHz) | UL/DL BW (MHz) | UL L CRB | DL F c (MHz) | MSD (dB) | Duplex mode | | +| DC_66A_n2A,
DC_66A-66A_n2A | 66 | 1775 | 5 | 25 | 2175 | N/A | N/A | CA_n2-n66 | n2 | 1855 | 5 | 25 | 1935 | 20 | FDD | IMD 3 | +| | n2 | 1855 | 5 | 25 | 1935 | 20 | IMD3 | | n66 | 1775 | 5 | 25 | 2175 | N/A | FDD | N/A | +| | 66 | 1750 | 5 | 25 | 2150 | 4 | IMD5 | CA_n2-n66 | n2 | 1883.3 | 5 | 25 | 1963.3 | N/A | FDD | N/A | +| | n2 | 1883.3 | 5 | 25 | 1963.3 | N/A | N/A | | n66 | 1750 | 5 | 25 | 2150 | 4 | FDD | IMD 5 | +| DC_66A_n5A | n5 | 838 | 5 | 25 | 883 | 30 | IMD2 3 | CA_n5-n66 | n5 | 838 | 5 | 25 | 883 | 30 | FDD | IMD 2 4 | +| | 66 | 1721 | 5 | 25 | 2121 | N/A | N/A | | n66 | 1721 | 5 | 25 | 2121 | N/A | FDD | N/A | +| DC_66A_n7A
DC_66A-66A_n7A
DC_66A_n7(2A)
DC_66A-66A_n7(2A) | 66 | 1730 | 5 | 25 | 2130 | N/A | N/A | CA_n7-n66 | n7 | 2535 | 10 | 50 | 2655 | 15 | FDD | IMD 4 | +| | n7 | 2535 | 10 | 50 | 2655 | 15 | IMD4 | | n66 | 1730 | 5 | 25 | 2130 | N/A | FDD | N/A | +| DC_66A_n25A | 66 | 1775 | 5 | 25 | 2175 | N/A | N/A | CA_n25-n66 | n66 | 1775 | 5 | 25 | 2175 | N/A | FDD | N/A | +| | n25 | 1855 | 5 | 25 | 1935 | 20 | IMD3 | | n25 | 1855 | 5 | 25 | 1935 | 20 | FDD | IMD 3 | +| | 66 | 1712.5 | 5 | 25 | 2112.5 | 23 | IMD3 | CA_n25-n66 | n66 | 1712.5 | 5 | 25 | 2112.5 | 23 | FDD | IMD 3 | +| | n25 | 1912.5 | 5 | 25 | 1992.5 | N/A | N/A | | n25 | 1912.5 | 5 | 25 | 1992.5 | N/A | FDD | N/A | +| | 66 | 1750 | 5 | 25 | 2150 | 4 | IMD5 | CA_n25-n66 | n66 | 1750 | 5 | 25 | 2150 | 4 | FDD | IMD 5 | +| | n25 | 1883.3 | 5 | 25 | 1963.3 | N/A | N/A | | n25 | 1883.3 | 5 | 25 | 1963.3 | N/A | FDD | N/A | +| DC_66A_n48A | 66 | 1715 | 5 | 25 | 2115 | 4 | IMD5 | CA_n48-n66 | n48 | 3660 | 5 | 25 | 3660 | N/A | TDD | N/A | +| | n48 | 3630 | 20 | 100 | 3630 | N/A | N/A | | n66 | 1730 | 5 | 25 | 2130 | 5.0 | FDD | IMD 5 | +| DC_66A_n71A | 66 | 1750 | 5 | 25 | 2150 | 5 | IMD4 | CA_n66-n71 | n66 | 1750 | 5 | 25 | 2150 | 5 | FDD | IMD 4 | +| | n71 | 675 | 5 | 25 | 629 | N/A | N/A | | n71 | 675 | 5 | 25 | 629 | N/A | FDD | N/A | + +| NR or E-UTRA Band / Channel bandwidth / N RB / MSD | | | | | | | | Band / Channel bandwidth / N RB / Duplex mode | | | | | | | | Source of IMD | +|-------------------------------------------------------------------------------------------------------------------------|--------------------|-------------------------|----------------|---------------------|-------------------------|----------|-----------|----------------------------------------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|---------------| +| EN-DC Configuration | EUTRA A or NR band | UL F c (MHz) | UL/DL BW (MHz) | UL L CRB | DL F c (MHz) | MSD (dB) | IMD order | NR CA band combination | NR band | UL F c (MHz) | UL/DL BW (MHz) | UL C LRB | DL F c (MHz) | MSD (dB) | Duplex mode | | +| DC_66A_n77A
DC_66A_n77(2A)
DC_66A-66A_n77A
DC_66A-66A_n77(2A)
DC_66A-66A-66A_n77A
DC_66A-66A-66A_n77(2A) | 66 | 1775 | 5 | 25 | 2175 | 31.0 | IMD2 | CA_n66-n77 | n66 | 1775 | 5 | 25 | 2175 | 31 | FDD | IMD 2 | +| | n77 | 3950 | 10 | 50 | 3950 | N/A | N/A | | n77 | 3950 | 10 | 50 | 3950 | N/A | TDD | N/A | +| | 66 | 1760 | 5 | 25 | 2160 | 5.0 | IMD5 | CA_n66-n77 | n66 | 1760 | 5 | 25 | 2160 | 5.0 | FDD | IMD 5 | +| | n77 | 3720 | 10 | 50 | 3720 | N/A | N/A | | n77 | 3720 | 10 | 50 | 3720 | N/A | TDD | N/A | +| DC_66A_n78A | 66 | 1730 | 5 | 25 | 2150 | 5.0 | IMD5 | CA_n66-n78 | n66 | 1730 | 5 | 25 | 2130 | 5.0 | FDD | IMD 5 | +| | n78 | 3660 | 10 | 50 | 3660 | N/A | N/A | | n78 | 3660 | 10 | 50 | 3660 | N/A | TDD | N/A | +| DC_71A_n41A | 71 | 666 | 5 | 25 | 620 | 11 | IMD4 | CA_n41-n71 | n41 | 2614 | 5 | 25 | 2614 | N/A | TDD | N/A | +| | n41 | 2618 | 5 | 25 | 2618 | N/A | N/A | | n71 | 665 | 5 | 25 | 619 | 11 | FDD | IMD 4 | +| DC_71A_n66A | 71 | 675 | 5 | 25 | 629 | N/A | N/A | CA_n66-n71 | n66 | 1750 | 5 | 25 | 2150 | 5 | FDD | IMD 4 | +| | n66 | 1750 | 5 | 25 | 2150 | 5 | IMD4 | | n71 | 675 | 5 | 25 | 629 | N/A | FDD | N/A | +| DC_71A_n77A 8 | 71 | 671 | 5 | 25 | 625 | 5.5 | IMD5 | CA_n71-n77 13 | n71 | 671 | 5 | 25 | 625 | 5.5 | FDD | IMD 5 | +| | n77 | 3309 | 10 | 50 | 3309 | N/A | N/A | | n77 | 3309 | 10 | 50 | 3309 | N/A | TDD | N/A | +| DC_71A_n78A | 71 | 681.5 | 5 | 25 | 635.5 | 5.5 | IMD5 | CA_n71-n78 | n71 | 681.5 | 5 | 25 | 635.5 | 5.5 | FDD | IMD 5 | +| DC_71A_n78(2A) | n78 | 3361.5 | 10 | 50 | 3361.5 | N/A | N/A | | n78 | 3361.5 | 10 | 50 | 3361.5 | N/A | TDD | N/A | + +| NR or E-UTRA Band / Channel bandwidth / N RB / MSD | | | | | | | | Band / Channel bandwidth / N RB / Duplex mode | | | | | | | Source of IMD | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-------------------------|----------------|---------------------|-------------------------|----------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|---------------| +| EN-DC Configuration | EUTRA or NR band | UL F c (MHz) | UL/DL BW (MHz) | UL L CRB | DL F c (MHz) | MSD (dB) | IMD order | NR CA band combination | NR band | UL F c (MHz) | UL/DL BW (MHz) | UL C LRB | DL F c (MHz) | MSD (dB) | Duplex mode | +| NOTE 1: E-UTRA carrier shall be set to min(+20 dBm, P CMAX_L_E-UTRA,c ) and NR carrier shall be set to min(+20 dBm, P CMAX_L,f,c,NR ) as defined in clause 6.2B.4.1.3.
NOTE 2: RB start = 0
NOTE 3: This band is subject to IMD5 also which MSD is not specified.
NOTE 4: Void
NOTE 5: Void
NOTE 6: For NR band, UL/DL BW and UL L CRB can be adjusted according to the supported BW and lowest SCS supported by the UE.
NOTE 7: The frequency range in band n28 is restricted for this band combination to 728 - 738 MHz for the UL and 783 - 793 MHz for the DL. This band is subject to IMD2, IMD4 and IMD5 fall in n28 also which MSD is not specified. In addition, this band is subject to IMD4 fall in B21 also which MSD is not specified.
NOTE 8: For a UE which supports this band combination only when the Band n77 frequency range restriction defined in NOTE 12 of Table 5.2-1 from TS 38.101-1 applies, the MSD test point(s) cannot be verified for the band combination and the test point(s) can be skipped. | | | | | | | | NOTE 1: Both of the transmitters shall be set min(+20 dBm, P CMAX_L,f,c ) as defined in clause 6.2A.4
NOTE 2: RB START = 0, 15 kHz SCS is assumed.
NOTE 3: No requirements apply when there is at least one individual RE within the intermodulation generated by the dual uplink is within the downlink transmission bandwidth of the FDD band. The reference sensitivity should only be verified when this is not the case (the requirements specified in clause 7.3 apply).
NOTE 4: This band is subject to IMD5 also which MSD is not specified.
NOTE 5: Void.
NOTE 6: Considering the spectrum holdings of the operator for CA_n77(2A) (when one uplink sub block is assigned within 3300-3400MHz, the other uplink sub block is not assigned within 4000-4200MHz or vice versa), no IMD5 result will fall in Rx frequency range of band n3. Therefore, no MSD requirement apply for this CA configuration when two uplink sub blocks are assigned within CA_77(2A).
NOTE 7: In current release the maximum separation bandwidth class is 600MHz, therefore, no IMD2 MSD requirement apply for this CA configuration when two uplink sub blocks are assigned within CA_77(2A).
NOTE 8: There is no IMD4/5 products in band n18 downlink for n77 operating in 3520 – 3560 MHz, 3700 – 3800MHz and 4000 - 4100MHz frequency range.
NOTE 9: There is no IMD4 product in band n18 downlink for n78 operating in 3520 – 3560MHz and 3700-3800MHz frequency range.
NOTE 10: There is no IMD4 product in band n24 downlink for n77 operating in 3450 – 3980 MHz and n24 uplink restricted to between 1627.5 – 1637.5 MHz and between 1646.5 – 1656.5 MHz.
NOTE 11: This band is subject to IMD5 also which MSD is not specified..
NOTE 12: This band supports intra-band non-contiguous uplink configuration.
NOTE 13: For a UE which supports this band combination only when the Band n77 frequency range restriction defined in NOTE 12 of Table 5.2-1 applies, the MSD test point(s) cannot be verified for the band combination and the test point(s) can be skipped.
NOTE 14: Applicable when n41 spectrum is restricted to 2515-2675MHz | | | | | | | | + +### 7.3.4 REFSENS requirements without any degradation for inter-band combinations (two bands) + +For band combinations DL\_nA-nB\_UL\_nA-nB / DL\_B\_nA\_UL\_B\_nA / DL\_A\_nB\_UL\_A\_nB / DL\_nB\_A\_UL\_nB\_A / DL\_nA\_B\_UL\_nA\_B which doesn't have any MSD requirements, it's suggested to test one of them in order to reduce the test burden for REFSENS requirements and final decision is up to RAN5. The reason is that the same Rx RF implementation is used to achieve these band combinations. + +For some special cases which have different delta Rib requirements, the requirements specified in clause 7.3A.3.2 from TS 38.101-1 can be reused. + +## 7.4 Test burden reduction for multiple MSD + +In current RAN4 spec, there are tables for the reference sensitivity exceptions due to intermodulation interference with 2UL CA. The test points in the reference sensitivity requirements specified for the single band are relaxed by the amount of the corresponding MSD values, shown as an example in Table 7.4-1. For some CA configurations such as CA\_n2-n77, CA\_n3-n77 and CA\_n3-n78, multiple test points with different order IMD are defined, while for some other CA configurations such as CA\_n2-n78, only 2nd order IMD2 having the worst case MSD are defined, although the corresponding band is subject to the 5th order IMD5. At the end of the table, a "Note 4" is set to indicate that MSD is not specified for the interfered band although IMD5 may fall into the Rx frequencies of the interfered band. To reduce the test burden, the following guidelines for handling multiple MSD should be taken into consideration. + +Table 7.4-1: Example for inter-band reference sensitivity with multiple MSD + +| Band / Channel bandwidth / N RB / Duplex mode | | | | | | | | Source of IMD | +|----------------------------------------------------------|---------|-------------------------|----------------|---------------------|-------------------------|----------|-------------|-------------------| +| NR CA band combination | NR band | UL F c (MHz) | UL/DL BW (MHz) | UL C LRB | DL F c (MHz) | MSD (dB) | Duplex mode | | +| CA_n1-n3 | n1 | 1950 | 5 | 25 | 2140 | 23 | FDD | IMD3 | +| | n3 | 1760 | 5 | 25 | 1855 | N/A | TDD | N/A | +| CA_n1-n8 | n1 | 1965 | 5 | 25 | 2155 | 6.0 | FDD | IMD4 | +| | n8 | 887.5 | 5 | 25 | 932.5 | N/A | FDD | N/A | +| CA_n1-n78 | n1 | 1950 | 5 | 25 | 2140 | 8.0 | FDD | IMD4 | +| | n78 | 3710 | 10 | 50 | 3710 | N/A | TDD | N/A | +| CA_n2-n48 | n2 | 1852.5 | 5 | 25 | 1932.5 | 12 | FDD | IMD4 | +| | n48 | 3625 | 20 | 100 | 3625 | N/A | TDD | N/A | +| CA_n2-n77 | n2 | 1855 | 5 | 25 | 1935 | 26 | FDD | IMD2 | +| | n77 | 3790 | 10 | 50 | 3790 | N/A | TDD | N/A | +| | n2 | 1900 | 5 | 25 | 1980 | 8.0 | FDD | IMD4 | +| | n77 | 3720 | 10 | 50 | 3720 | N/A | TDD | N/A | +| | n2 | 1885 | 5 | 25 | 1965 | 5 | FDD | IMD5 | +| | n77 | 3810 | 10 | 50 | 3810 | N/A | TDD | N/A | +| CA_n2-n78 | n2 | 1855 | 5 | 25 | 1935 | 26 | FDD | IMD2 4 | +| | n78 | 3790 | 10 | 50 | 3790 | N/A | TDD | N/A | +| CA_n3-n7 | n3 | 1730 | 5 | 25 | 1825 | N/A | FDD | N/A | +| | n7 | 2535 | 10 | 50 | 2655 | 10.2 | FDD | IMD4 | +| CA_n3-n8 | n3 | 1755 | 10 | 50 | 1850 | N/A | FDD | N/A | +| | n8 | 900 | 5 | 25 | 945 | 8 | FDD | IMD4 4 | +| | n3 | 1747.5 | 10 | 50 | 1842.5 | 6.4 | FDD | IMD5 | +| | n8 | 897.5 | 5 | 25 | 942.5 | N/A | FDD | N/A | +| CA_n3-n38 | n3 | 1713 | 5 | 25 | 1808 | 8.2 | FDD | IMD4 | +| | n38 | 2617 | 5 | 25 | 2617 | N/A | TDD | N/A | +| CA_n3-n41 | n3 | 1740 | 5 | 25 | 1835 | 8.2 | FDD | IMD4 | +| | n41 | 2657.5 | 10 | 50 | 2657.5 | N/A | TDD | N/A | +| CA_n3-n77 | n3 | 1740 | 5 | 25 | 1835 | 26 | FDD | IMD2 4 | +| | n77 | 3575 | 10 | 50 | 3575 | N/A | TDD | N/A | +| | n3 | 1765 | 5 | 25 | 1860 | 8.0 | FDD | IMD4 4 | +| | n77 | 3435 | 10 | 50 | 3435 | N/A | TDD | N/A | +| CA_n3-n78 | n3 | 1740 | 5 | 25 | 1835 | 26 | FDD | IMD2 4 | +| | n78 | 3575 | 10 | 25 | 3575 | N/A | TDD | N/A | +| | n3 | 1765 | 5 | 25 | 1860 | 8.0 | FDD | IMD4 4 | +| | n78 | 3435 | 10 | 25 | 3435 | N/A | TDD | N/A | +| ... | ... | ... | ... | ... | ... | ... | ... | ... | + +NOTE 4: This band is subject to IMD5 also which MSD is not specified. + +For a given 2 band DL CA combination, MSD test points corresponding to type 1,2,3 UL configuration are captured in the same table entry. + +- **Type 1:** UL configuration = 2 UL CCs configured with intra-band UL CA configured in one of the two band. Intra-band UL CA may be contiguous (like UL CA\_n41C) or non-contiguous (like UL CA\_n78(2A)). +- **Type 2:** UL configuration = 2 UL CCs configured inter-band UL CA with 1UL CC in each of UL band. Example: UL CA\_n3A\_n78A. +- **Type 3:** UL configuration = 3 UL CCs with 1 CC in one UL band, and 2 UL CCs configured intra-band CA in the other band. Example: UL CA\_n3A-n41C. + +Guideline 1: It is proposed that for the test points with reference sensitivity exceptions due to intermodulation interference with 2UL CA, the limitation to higher order IMD source could be a solution to reduce test burden. + +- The existing IMD MSD requirements in Rel-17 specifications are kept unchanged. +- For Rel-18 new introduced band combinations, +- For type 1 UL configurations (e.g. UL\_CA\_n41C or CA\_n78(2A)) + +- The lowest order IMD is recommended as worst case to represent single band UL transmission with UL configured intra-band CA. +- If the DL band may be affected by a mix of even and odd order IMD products, the MSD value of the lowest even and the lowest odd order IMD, if any, shall be defined in the specifications. +- A footnote shall be attached to the DL band to indicate that MSD may occur for higher order IMD products, and these orders shall be specified in the footnote. +- As an exception to this rule, a second MSD test point may be specified to capture the MSD that may occur due to the next highest odd order or due to the next highest even order IMD product. This exception ensures regional frequency restrictions are accounted for. For example, in CA\_n66\_n77 the type 1 IMD7 MSD test point (next highest odd order) may be retained in addition to the type 1 IMD5 MSD test point (lowest odd order). +- A footnote shall be attached to the UL band that is configured intra-band UL CA to distinguish the case of intra-band contiguous vs intra-band non-contiguous CA. +- For type 2 UL configurations (e.g. UL\_CA\_n1A-n3A) + +If only one IMD order occurs per victim band, the MSD value if any shall be defined in the specifications. + +If the DL band may be affected by a mix of even and odd order IMD products, then the MSD value of the lowest even and the lowest odd order IMD, if any, shall be defined in the specifications. + +A footnote shall be attached to the DL band to indicate that MSD may occur for higher order IMD products, and these orders shall be specified in the footnote. + +If the DL band may be affected only by multiple even order IMD products, or only by multiple odd order IMD products, then the MSD value of the lowest even order IMD or the MSD value of the lowest odd order IMD, if any, shall be defined in the specifications. + +The lowest order IMD is recommended as worst case to represent the whole spectrum of the inter-band CA combinations. + +Optionally, a second MSD test point may be specified on a case-by-case basis to account for additional IMD orders. It is recommended this 2nd MSD test point corresponds to the lowest even and the lowest odd order IMD. For example, if DL band is affected by IMD2/3/5, we may consider a maximum of test points: one for IMD2 and one for IMD3. + +Any additional IMD order that is not specified shall be indicated by a note in the table. + +- For type 3 UL configurations (e.g. CA\_n3A-n41C or DC\_3C\_n1A-n75A) + +For the case when the victim band may be affected by a 1st order triple-beat product Proponents should systematically check if the downlink band may be affected by dual uplink IMD3 interference. If the test point is missing, a dual UL IMD3 MSD test point should be specified. + +If TB frequency is composed of the frequency sum of the 2 discrete RBs in the contiguous UL CA, there is no need to specify the TB test configuration as the requirement can already be verified by the fallback 2UL IMD3. With reference to WF R4-2220556 [9], only the TB1 product $|f_1+f_2-f_3|$ and TB2 product $|f_1-f_2+f_3|$ should be considered – refer to TB landscape example of Figure 7.4-1. + +![Figure 7.4-1: Landscape of 1st order triple beat products for the example of DC_3C_n1A-n75A. The diagram shows frequency bands and triple beat (TB) products. On the left, band B32 (n75) is shown with TB3 at |f2+f3-f1|. In the center, band n3 ULCA is shown with f2 and f3. To the right, band n1 1UL is shown with TB1 at |f1+f2-f3|, f1, and TB2 at |f1-f2+f3|. Further right, band n1 DL band is shown with TB4 at f1+f2+f3. A break in the axis is indicated between 2300 and 2400 MHz.](b90dcb4c35f1875e19ca312a6cf4adae_img.jpg) + +Figure 7.4-1: Landscape of 1st order triple beat products for the example of DC\_3C\_n1A-n75A. The diagram shows frequency bands and triple beat (TB) products. On the left, band B32 (n75) is shown with TB3 at |f2+f3-f1|. In the center, band n3 ULCA is shown with f2 and f3. To the right, band n1 1UL is shown with TB1 at |f1+f2-f3|, f1, and TB2 at |f1-f2+f3|. Further right, band n1 DL band is shown with TB4 at f1+f2+f3. A break in the axis is indicated between 2300 and 2400 MHz. + +**Figure 7.4-1: Landscape of 1st order triple beat products for the example of DC\_3C\_n1A-n75A** + +- If TB consists of intra-band contiguous UL CA in a FDD band, the selection of test configuration should strive to avoid FDD band self-interference to its own DL carriers with at least up to IMD7. +- The following WF [9] guidelines remain applicable: + - 2.1 WF on Pre-Condition for TB MSD Analysis with 3UL CCs + - 2.2 WF on Pre-Condition for TB MSD Analysis with 4UL CCs + - 2.3 WF on Triple-Beat Detection for two-band combinations + - 2.5 WF on MSD analysis + - 2.6 WF on Capturing MSD Test Points + +# 8 Conclusion + +Compared with previous generations, 5G NR has much more complex band combination configurations being specified. The study item handles the simplification of band combination and rule collection for RAN4 specifications in the stage of Rel-18. The key functionalities of this SI mainly include the following aspects. + +- To keep a TR running with all the valid rules and valuable guidelines for band combinations being captured, the related contents in Rel-17 TR 38.862 are transited in this TR. +- The working procedure for specifying band combinations including templates for specifying band combinations, fallback aspects for specifying band combinations and submitting technical contributions for specifying band combinations have been proposed. +- Guidelines of specifying band combinations on fallbacks, delta TIB/RIB, configuration table structure, co-existence analysis and simplification for MSD due to IMD interference, etc. have been studied. +- To include 2UL inter-band CA/DC coexistence reduction, FR1 CA/DC, FR1 EN-DC/NE-DC and LTE CA cases are agreed to be applied to NR/LTE specifications. +- The dependency and applicability for RF requirements among different features for the same spectrum combination to reduce the redundant tests have been analysed. +- The guidelines for test burden reduction for harmonic mixing, cross-band isolation MSD and inter-modulation distortion for inter-band combinations have been investigated. + +# --- Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-----------------|------------|----|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-08 | RAN4 #104-e | R4-2215080 | | | | 1. R4-2215080, TR skeleton, ZTE | 0.0.1 | +| 2022-10 | RAN4 #104-bis-e | R4-2216616 | | | | 1. R4-2216620, TP for TR 38.846 on rules of delta TIB and RIB due to band combinations, ZTE
2. R4-2217719, TP for TR38.846_Update template for R18 PC3 basket WIDs, ZTE
3. R4-2217720, TP on test burden reduction, Huawei, HiSilicon
4. R4-2217721, Fallbacks in 38.101 specs, Apple
5. R4-2217722, TP for TR 38.846 on working procedure of specifying band combinations, ZTE | 0.1.0 | +| 2022-11 | RAN4 #105 | R4-2219762 | | | | 1. R4-2220510, TP for TR 38.846 to capture some agreements for REFSENS test burden reduction, Huawei, HiSilicon
2. R4-2220511, TP for TR 38.846 on test burden reduction for multiple MSD in band combinations, ZTE Corporation
3. R4-2219626, TP for TR 38.846 to capture the fallback rules with exceptional cases, Huawei, HiSilicon
4. R4-2219759, TP for TR 38.846 on templates of delta TIB and RIB for NE-DC and SUL band combinations, ZTE Corporation | 0.2.0 | +| 2023-03 | RAN4 #106 | R4-2302551 | | | | 1. R4-2303512, TP for TR 38.846 on template for mixed intra-band contiguous and non-contiguous NR CA, ZTE
2. R4-2303543, Updates of template for R18 PC3 ENDC NRCA SUL V2X band combinations, ZTE
3. R4-2303513, TP for TR 38.846 on simplification for CA uplink configurations, ZTE
4. R4-2303514, TP for TR 38.846 to capture some agreements for MSD test burden reduction, Huawei, HiSilicon
5. R4-2203515, TP for TR 38.846 to add guidance on document type for addition of band combinations, Nokia | 0.3.0 | +| 2023-04 | RAN4 #106bis-e | R4-2304726 | | | | 1. R4-2306585, TP for TR 38.846 on valid CBW for higher order BC configurations, ZTE
2. R4-2306586, TP for TR 38.846 on template for R18 HPUE band combination, ZTE
3. R4-2306587, Template for R18 HPUE band combinations, ZTE
4. R4-2306588, TP for TR 38.846 on test burden reduction for multiple MSD in band combinations, Skyworks Solutions, Inc. | 0.4.0 | +| 2023-05 | RAN4 #107 | R4-2307981 | | | | 1. R4-2307985, Template v1.2 for R18 PC3 ENDC NRCA SUL V2X band combinations, ZTE
2. R4-2307986, TP for TR 38.846 on update template info for R18 PC3 and HPUE band combination, ZTE
3. R4-2310274, TP to TR 38.846 to add guidance on Co-existence studies for Uplink Intra-Band Non-Contiguous CA, Nokia, Nokia Shanghai Bell, Skyworks Solutions, Inc.
4. R4-2307867, 2UL UE to UE co-ex simplification for EN-DC, Nokia
5. R4-2309715, TP for 38.846: HPUE for FR1+FR2 band combinations, T-Mobile USA, Ericsson, Nokia, AT&T, Verizon, Skyworks Solutions, Inc. | 0.5.0 | +| 2023-06 | RP#100 | RP-231290 | | | | 1. RP-231290, TR 38.846 v1.0.0_Study on simplification of band combination specification for NR and LTE, ZTE | 1.0.0 | +| 2023-09 | RAN4#108 | R4-2312595 | | | | 1. R4-2311928, TP for TR 38.846 Update the rule on the fallback information aspect for specifying band combinations, Samsung, CHTT, ZTE
2. R4-2314684, TP for TR 38.846_Capture the valid rules and guidelines of TR 38.862 into TR 38.846, ZTE, CHTT
3. R4-2314685, TP for TR 38.846 on test burden reduction for type 3 TB MSD, Skyworks Solutions Inc.
4. R4-2314686, TP for TR 38.846 guidelines on simplification for 3DL2UL MSD, Skyworks Solutions Inc. | 1.1.0 | + +| | | | | | | | | +|---------|--------------|------------|--|--|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| 2023-10 | RAN4#108 bis | R4-2316679 | | | | 1. R4-2316686, TP for FS_SimBC on TR 38.846 cleanup, ZTE
2. R4-2316687, TP for TR 38.846_Restructure the clause for optimization on band combinations, ZTE, CHTTL
3. R4-2316436, TP for TR 38.846 about that BCS4 and BCS5 channel BW does not need to be specified in BCS sheet, Ericsson
4. R4-2316689, TP for TR 38.846_Guidelines on delta TIB and RIB special values for band combinations, ZTE, CHTTL | 1.3.0 | +| 2023-11 | RAN4#109 | R4-2319604 | | | | 1. R4-2320998, TP for TR 38.846 Guidelines on Cross-band MSD test points for SUL, Skyworks
2. R4-2320999, TP for TR38.846 Guidelines on Cross-band MSD with FDD UL-CA, Skyworks
3. R4-2321794, TP for TR 38.846: On bandwidth classes for NR band combinations, ZTE
4. R4-2321795, TP to TR38.846 of Guidelines on Co-existence analysis for triple beat, Nokia, Nokia Shanghai Bell
5. R4-2321796, TP to TR 38.846 Addition of Guidelines on Harmonic mixing MSD requirements, Nokia, Nokia Shanghai Bell
6. R4-2321921, TP for TR 38.846: On spec structure for inter-band CA configuration tables, ZTE | 1.4.0 | +| 2023-12 | RAN#102 | RP-233235 | | | | 1. RP-233235, Presentation of TR 38.846 to TSG#102, ZTE | 2.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/38_series/38848/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/Rel-18/38_series/38848/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19452f7c2442e02d268f79c1377ff6c3d4a9c34d --- /dev/null +++ b/marked/Rel-18/38_series/38848/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a00c27f3aa19958ccd0efb9c63851f2aacd2260053db870e262c887869da9c4 +size 14894 diff --git a/marked/Rel-18/38_series/38848/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/Rel-18/38_series/38848/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8039ff9fd313390e6fb1f474101d704b86961b33 --- /dev/null +++ b/marked/Rel-18/38_series/38848/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3edb3f01f2e7c2115dda712fbb478f70caf7c30da55946ce22b9d795d8f5f37 +size 10872 diff --git a/marked/Rel-18/38_series/38848/5a95b187de0044da69b7322e04761b86_img.jpg b/marked/Rel-18/38_series/38848/5a95b187de0044da69b7322e04761b86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a99ca6d629a3ae683b693909e14b79cd5c99ea79 --- /dev/null +++ b/marked/Rel-18/38_series/38848/5a95b187de0044da69b7322e04761b86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5265353b07d275b3a9ba953158c9b787c8fd606a015101265452c163ad4eb3f +size 19811 diff --git a/marked/Rel-18/38_series/38848/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38848/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3d265b5c1510060c42e00faaed724afeb499726 --- /dev/null +++ b/marked/Rel-18/38_series/38848/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee9e28b1e2f9449d6ce5c10076c30080feefc2997c2a6498a4f38d11627cede6 +size 9665 diff --git a/marked/Rel-18/38_series/38848/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38848/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e87b496fa8de3d781bdcd544bbdca4463d5ce14 --- /dev/null +++ b/marked/Rel-18/38_series/38848/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7276670225c34ed9cba49422b9257140606b9b76f607cd3733bd5e19f5ced023 +size 5657 diff --git a/marked/Rel-18/38_series/38848/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/marked/Rel-18/38_series/38848/78ffccd66df9bafd96e3e081110d09dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8651b1b17752db6391e1a2dfcf5a4f968963738d --- /dev/null +++ b/marked/Rel-18/38_series/38848/78ffccd66df9bafd96e3e081110d09dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93e9e3d90ccf3dbf2663a7f5a5a95ff343bed014be33cca4f6922e862556226b +size 18838 diff --git a/marked/Rel-18/38_series/38848/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-18/38_series/38848/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c59aa97aa5b79449ffa720d5ffbb4c201f8a309 --- /dev/null +++ b/marked/Rel-18/38_series/38848/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37b9a93599735e721d1645cbda8e8449c465a1a052ddaec493fa4b3d00d73066 +size 18258 diff --git a/marked/Rel-18/38_series/38848/raw.md b/marked/Rel-18/38_series/38848/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3dc3bbefb21bb9ac977db154dd53b654eef09670 --- /dev/null +++ b/marked/Rel-18/38_series/38848/raw.md @@ -0,0 +1,731 @@ + + +# 3GPP TR 38.848 V18.0.0 (2023-09) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on Ambient IoT (Internet of Things) in RAN (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 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. + +© 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 | +| Introduction ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions of terms, symbols and abbreviations ..... | 8 | +| 3.1 Terms..... | 8 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations ..... | 8 | +| 4 Deployment scenarios, use cases, services ..... | 8 | +| 4.1 Use cases/services ..... | 8 | +| 4.1.1 Representative use cases..... | 8 | +| 4.2 Deployment scenarios and connectivity topologies..... | 10 | +| 4.2.0 Introduction ..... | 10 | +| 4.2.1 Connectivity topologies..... | 11 | +| 4.2.1.0 Introduction..... | 11 | +| 4.2.1.1 Topology 1: BS $\leftrightarrow$ Ambient IoT device..... | 12 | +| 4.2.1.2 Topology 2: BS $\leftrightarrow$ intermediate node $\leftrightarrow$ Ambient IoT device..... | 12 | +| 4.2.1.3 Topology 3: BS $\leftrightarrow$ assisting node $\leftrightarrow$ Ambient IoT device $\leftrightarrow$ BS ..... | 12 | +| 4.2.1.4 Topology 4: UE $\leftrightarrow$ Ambient IoT device ..... | 13 | +| 4.2.2 Deployment scenarios ..... | 13 | +| 4.2.2.1 Deployment scenario 1: Device indoors, basestation indoors ..... | 13 | +| 4.2.2.2 Deployment scenario 2: Device indoors, basestation outdoors ..... | 14 | +| 4.2.2.3 Deployment scenario 3: Device indoors, UE-based reader ..... | 15 | +| 4.2.2.4 Deployment scenario 4: Device outdoors, basestation outdoors ..... | 15 | +| 4.2.2.5 Deployment scenario 5: Device outdoors, UE-based reader ..... | 16 | +| 4.3 Device categorization..... | 16 | +| 5 RAN design targets ..... | 17 | +| 5.1 Device power consumption..... | 17 | +| 5.2 Device complexity..... | 17 | +| 5.3 Coverage..... | 17 | +| 5.4 User experienced data rate ..... | 17 | +| 5.5 Maximum message size ..... | 18 | +| 5.6 Latency ..... | 18 | +| 5.7 Positioning accuracy ..... | 18 | +| 5.8 Connection/device density ..... | 18 | +| 5.9 Moving speed of device ..... | 18 | +| 6 Comparison and assessment..... | 19 | +| 6.1.1 Device power consumption ..... | 19 | +| 6.1.2 Device complexity..... | 19 | +| 6.1.3 Coverage..... | 19 | +| 6.1.4 User experienced data rate..... | 19 | +| 6.1.5 Maximum message size..... | 20 | +| 6.1.6 Latency ..... | 20 | +| 6.1.7 Positioning accuracy..... | 20 | +| 6.1.8 Connection/device density..... | 20 | +| 6.1.9 Moving speed of device..... | 20 | +| 6.2 Required RAN functionalities..... | 20 | +| 7 Conclusions and recommendations..... | 22 | +| 7.1 Summary ..... | 22 | +| 7.2 Recommendations ..... | 22 | + +| | | +|-----------------------------------------------------------|-----------| +| Annex A: Energy sources for energy harvesting..... | 23 | +| Annex B: Change history..... | 23 | + +# --- 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. + +# --- Introduction + +In recent years, IoT has attracted much attention in the wireless communication world. More 'things' are expected to be interconnected for improving productivity efficiency and increasing comforts of life. Further reduction of size, complexity, and power consumption of IoT devices can enable the deployment of tens or even hundreds of billions of IoT devices for various applications and provide added value across the entire value chain. It is impossible to power all the IoT devices by battery that needs to be replaced or recharged manually, which leads to high maintenance cost, serious environmental issues, and even safety hazards for some use cases, for example, wireless sensors in electrical power, and petroleum industries. + +Most of the existing wireless communication devices are powered by batteries that need to be replaced or recharged manually. The automation and digitization of various industries opens numerous new markets requiring new IoT technologies of supporting batteryless devices with no energy storage capability or devices with energy storage that do not need to be replaced or recharged manually. + +An example type of application is asset identification, which presently has to resort mainly to barcodes and RFID in most industries. The main advantage of these two technologies is the ultra-low complexity and small form factor of the tags. However, the limited reading range of a few meters usually requires handheld scanning which leads to labor intensive and time-consuming operations, or RFID portals/gates which leads to costly deployments. Moreover, the lack of interference management scheme results in severe interference between RFID readers and capacity problems, especially in case of dense deployment. It is hard to support a large-scale network with seamless coverage for RFID. + +In contrast, this study investigates the feasibility of a new IoT technology to open new markets within 3GPP systems, whose number of connections and/or device density can be orders of magnitude higher than existing 3GPP IoT technologies, and which can provide complexity and power consumption orders-of-magnitude lower than existing 3GPP LPWA technologies such as NB-IoT and LTE-MTC. + +# --- 1 Scope + +The present document reports on the feasibility of meeting the design targets for relevant use cases of a new 3GPP IoT technology, on the basis of suitable deployment scenarios in a 3GPP system, which relies on ultra-low complexity devices with ultra-low power consumption for very-low end IoT applications. It intends to provide a clear differentiation, i.e. addressing use cases and scenarios that *cannot* otherwise be fulfilled based on existing 3GPP LPWA IoT technology. + +In terms of energy storage, the study considers the following device characteristics: + +- Pure batteryless devices with no energy storage capability at all, and completely dependent on the availability of an external source of energy. +- Devices with limited energy storage capability that do not need to be replaced or recharged manually. + +# --- 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 22.840: "Study on Ambient power-enabled Internet of Things". +- [3] "A Battery-Free Tag for Wireless Monitoring of Heart Sounds", 2009 Sixth International Workshop on Wearable and Implantable Body Sensor Networks, June 2009 +- [4] "A Survey of Low-Power Transceivers and Their Applications", IEEE Circuits and Systems Magazine (Vol. 15), third quarter 2015. +- [5] [http://www.winlab.rutgers.edu/~crose/322\\_html/envelope\\_detector.html](http://www.winlab.rutgers.edu/~crose/322_html/envelope_detector.html). +- [6] Liu, V., Talla, V., & Gollakota, S. (2014). Enabling instantaneous feedback with full-duplex backscatter. Proceedings of the 20th Annual International Conference on Mobile Computing and Networking MobiCom '14. +- [7] RP-231627, "Input to Study on Ambient IoT in RAN", Ericsson, RAN#101, September 2023. +- [8] D. A. Loku Galappaththige, et. al., "Link Budget Analysis for Backscatter-Based Passive IoT", IEEE Access, vol. 10, pp. 128890-128922, 2022. +- [9] "A 2.4 GHz Interferer-Resilient Wake-Up Receiver Using A Dual-IF Multi-Stage N-Path Architecture", IEEE Journal of Solid-State Circuits (Vol. 51), Sept. 2016 +- [10] "An 802.11ba-based wake-up radio receiver with Wi-Fi transceiver integration", IEEE J. Solid-State Circuits (Vol. 55), May 2020. +- [11] J. Bae and H. Yoo, "A low energy injection-locked FSK transceiver with frequency-to-amplitude conversion for body sensor applications," 2010 Symposium on VLSI Circuits, 2010, pp. 133-134, doi: 10.1109/VLSIC.2010.5560325. + +- [12] K. Tang et al., "A 75.3 pJ/b Ultra-Low Power MEMS-Based FSK Transmitter in ISM-915 MHz Band for Pico-IoT Applications," 2021 IEEE International Symposium on Circuits and Systems (ISCAS), 2021, pp. 1-4, doi: 10.1109/ISCAS51556.2021.9401715 +- [13] M. S. Jahan, J. Langford and J. Holleman, "A low-power FSK/OOK transmitter for 915 MHz ISM band," 2015 IEEE Radio Frequency Integrated Circuits Symposium (RFIC), 2015, pp. 163-166, doi: 10.1109/RFIC.2015.7337730. +- [14] RP-222644, "Revised SID: Study on low-power Wake-up Signal and Receiver for NR", vivo, September 2022. +- [15] 3GPP TR 38.869, "Study on low-power Wake-up Signal and Receiver for NR". +- [16] F. Amato et. al., "Tunneling RFID Tags for Long-Range and Low-Power Microwave Applications", IEEE Journal of Radio Frequency Identification, vol. 2, no. 2, pp. 93-103, June 2018. +- [17] RP-231559 "Views on Ambient IoT (Rel-18 SI)", Qualcomm, RAN#101, September 2023. +- [18] RP-231598 "Discussion on Ambient IoT", Semtech (Sierra Wireless) , RAN#101, September 2023. +- [19] RP-231617 "Ambient IoT deployment feasibilities", Nokia, Nokia Shanghai Bell, RAN#101, September 2023. +- [20] RP-231627 "Input to Study on Ambient IoT in RAN", Ericsson, RAN#101, September 2023. +- [21] RP-231810 "Remaining issues on Ambient IoT SI", vivo, RAN#101, September 2023. +- [22] RP-231848 "Further consideration on ambient IoT for RAN", OPPO, RAN#101, September 2023. +- [23] RP-231915 "Further discussion on Ambient IoT in RAN", Spreadtrum Communications, RAN#101, September 2023. +- [24] RP-232284 "Feasibility analysis on coverage of A-IoT ZTE", Sanechips, RAN#101, September 2023. +- [25] RP-232408 "Discussion on Feasibility assessment and required functionalities for Ambient IoT", Huawei, HiSilicon, RAN#101, September 2023. +- [26] C. Xu et. al, "Practical Backscatter Communication Systems for Battery-Free Internet of Things: A Tutorial and Survey of Recent Research," IEEE Signal Processing Magazine, vol. 35, no. 5, pp. 16-27, Sept. 2018. +- [27] Chenyang Li , Lingfei Mo, and Dongkai Zhang, "Review on UHF RFID Localization Methods", IEEE Journal of Radio Frequency Identification, VOL. 3, NO. 4, DECEMBER 2019. +- [28] Deep Convolutional Neural Network for Passive RFID Tag Localization Via Joint RSSI and PDOA Fingerprint Features, IEEE Access (Vol. 9), Jan. 2021. +- [29] A Multi-tag Cooperative Localization Algorithm Based on Weighted Multidimensional Scaling for Passive UHF RFID, IEEE Internet of Things Journal (Vol. 6), Mar. 2019. +- [30] Lam K H, Cheung C C, Lee W C, "RSSI-based LoRa localization systems for large-scale indoor and outdoor environments", IEEE Transactions on Vehicular Technology, VOL. 68, No. 12, December 2019. +- [31] Sallouha H, Chiumento A, Pollin S, "Localization in long-range ultra-narrow band IoT networks using RSSI", 2017 IEEE International Conference on Communications (ICC), IEEE, May 2017 +- [32] Xingqin Lin, Johan Bergman, Fredrik Gunnarsson, etc., "Positioning for the Internet of Things: A 3GPP Perspective", IEEE Communications Magazine, VOL. 55, NO. 12, DECEMBER 2017. + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +## 3.2 Symbols + +## 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]. + +| | | +|---------|--------------------------------------------------| +| ASK | Amplitude-shift keying | +| DO | Device-originated | +| DT | Device-terminated | +| DO-A | Device-originated – autonomous | +| DO-DTT | Device-originated – device-terminated triggered | +| EPC | Electronic product code | +| FSK | Frequency-shift keying | +| IoT | Internet of Things | +| LPWA | Low-power, wide-area | +| LTE-MTC | Long Term Evolution – Machine Type Communication | +| NB-IoT | Narrowband IoT | +| OOK | On-off keying | +| RFID | Radio-frequency identification | +| rUC | representative Use Case | +| UHF | Ultra-high frequency | + +# --- 4 Deployment scenarios, use cases, services + +## 4.1 Use cases/services + +### 4.1.1 Representative use cases + +Two sets or levels of grouping were defined. The first, Grouping A, is on the basis of the deployment environment(s) described for a use case in TR 22.840 [2], and the second, Grouping B, is on the basis of functionality/application described in TR 22.840 [2]. + +Grouping A: + +- Indoor +- Outdoor +- Indoor/outdoor + +Grouping B: + +- Inventory +- Sensors +- Positioning +- Command + +These two groupings are then used to form representative use cases (rUCs) as follows, which are used in Clause 4.2 – Deployment scenarios and connectivity topologies. + +- rUC1: Indoor inventory +- rUC2: Indoor sensors +- rUC3: Indoor positioning +- rUC4: Indoor command +- rUC5: Outdoor inventory +- rUC6: Outdoor sensors +- rUC7: Outdoor positioning +- rUC8: Outdoor command + +This resulted in the following mapping from SA1 use cases and traffic scenarios onto RAN rUCs: + +**Table 4.1.1-1: Mapping between RAN representative use cases and SA1 use cases** + +| rUC | Applicable SA1 UCs / traffic scenarios | +|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| rUC1: Indoor inventory | 5.1 Automated warehousing
5.2 Medical instruments inventory management and positioning
5.4 Non-Public Network for logistics
5.5 Automobile manufacturing
5.7 Airport terminal / shipping port
5.15 Smart laundry
5.16 Automated supply chain distribution
5.18 Fresh food supply chain
5.27 End-to-end logistics
6.1 Flower auction
6.3 Electronic shelf label | +| rUC2: Indoor sensor | 5.6 Smart homes
5.13 Base station machine room environmental supervision
5.15 Smart laundry
5.20 Smart agriculture
5.23 Smart pig farm
6.2 Cow stable | +| rUC3: Indoor positioning | 5.8 Finding Remote Lost Item
5.9 Location service
5.10 Ranging in a home
5.12 Personal belongings finding
5.14 Positioning in shopping centre
5.21 Museum Guide | +| rUC4: Indoor command | 5.11 Online modification of medical instruments status
5.17 Device activation and deactivation
5.26 Elderly Health Care
5.29 Device Permanent Deactivation
6.3 Electronic shelf label | +| rUC5: Outdoor inventory | 5.2 Medical instruments inventory management and positioning
5.4 Non-public network for logistics
5.7 Airport terminal / shipping port
5.16 Automated supply chain distribution | +| rUC6: Outdoor sensor | 5.3 Smart grids
5.19 Forest Fire Monitoring
5.22 Dairy farming
5.24 Smart manhole cover safety monitoring
5.25 Smart bridge health monitoring | +| rUC7: Outdoor positioning | 5.8 Finding remote lost item
5.9 Location service
5.12 Personal belongings finding | +| rUC8: Outdoor command | 5.11 Online modification of medical instruments status
5.17 Device activation and deactivation
5.26 Elderly Health Care
5.30 Controller in smart agriculture | + +## 4.2 Deployment scenarios and connectivity topologies + +### 4.2.0 Introduction + +Deployment scenarios for Ambient IoT have been studied on the basis of a list of characteristics, and the representative use case(s) applicable to a scenario. The possible descriptions of the characteristics are as follows: + +**Table 4.2.0-1: Characteristics of deployment scenarios** + +| Characteristic | Possible description entries | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Environment (of the device) | Indoor
Outdoor
Indoor or outdoor | +| Basestation characteristic (if any) | Macro-cell-based deployment
Micro-cell-based deployment
Pico-cell-based deployment
None | +| Connectivity topology | See section 4.2.1 | +| Spectrum | Licensed FDD
Licensed TDD
Unlicensed

Note: In each connectivity topology of the study, if a BS is present, it is assumed that the BS uses licensed spectrum | +| Coexistence with existing 3GPP technologies | Deployed on the same sites as an existing 3GPP deployment corresponding to the basestation type.
Deployed on new sites without an assumption of an existing 3GPP deployment. | +| Traffic assumption | Device-terminated (DT)
Device-originated (DO)

DO traffic includes DO autonomous (DO-A), and DO device-terminated triggered (DO-DTT) | +| Device characteristic | See Section 4.3:
Device A
Device B
Device C | + +The study has considered Ambient IoT deployments in-band to NR, in guard-band of NR, and in standalone band from NR. + +### 4.2.1 Connectivity topologies + +#### 4.2.1.0 Introduction + +The following connectivity topologies for Ambient IoT networks and devices are defined for the purposes of the study. In all these topologies, the Ambient IoT device may be provided with a carrier wave from other node(s) either inside or outside the topology. The links in each topology may be bidirectional or unidirectional. + +BS, UE, assisting node, or intermediate node could be multiple BSs or UEs, respectively. The mixture of indoor and outdoor placement of such nodes is regarded as a network implementation choice. Account would need to be taken of potential impact on device or node complexity. In the connectivity topologies, this does not imply the existence of multi-hop assisting or intermediate nodes. + +#### 4.2.1.1 Topology 1: BS $\leftrightarrow$ Ambient IoT device + +![Diagram of Topology 1: BS <-> Ambient IoT device. A Base Station (BS) on the left and an Ambient IoT device on the right are connected by a double-headed arrow. Above the BS, a horizontal arrow points right, labeled 'Ambient IoT data/signaling'.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +Diagram of Topology 1: BS <-> Ambient IoT device. A Base Station (BS) on the left and an Ambient IoT device on the right are connected by a double-headed arrow. Above the BS, a horizontal arrow points right, labeled 'Ambient IoT data/signaling'. + +Figure 4.2.1.1-1: Topology 1 + +In Topology 1, the Ambient IoT device directly and bidirectionally communicates with a basestation. The communication between the basestation and the ambient IoT device includes Ambient IoT data and/or signalling. This topology includes the possibility that the BS transmitting to the Ambient IoT device is a different from the BS receiving from the Ambient IoT device. + +#### 4.2.1.2 Topology 2: BS $\leftrightarrow$ intermediate node $\leftrightarrow$ Ambient IoT device + +![Diagram of Topology 2: BS <-> intermediate node <-> Ambient IoT device. A Base Station (BS) on the left is connected to an intermediate node (a black circle) by a dashed double-headed arrow labeled 'Uu'. The intermediate node is connected to an Ambient IoT device on the right by a solid double-headed arrow. Above the BS, a horizontal arrow points right, labeled 'Ambient IoT data/signaling'.](78ffccd66df9bafd96e3e081110d09dd_img.jpg) + +Diagram of Topology 2: BS <-> intermediate node <-> Ambient IoT device. A Base Station (BS) on the left is connected to an intermediate node (a black circle) by a dashed double-headed arrow labeled 'Uu'. The intermediate node is connected to an Ambient IoT device on the right by a solid double-headed arrow. Above the BS, a horizontal arrow points right, labeled 'Ambient IoT data/signaling'. + +Figure 4.2.1.2-1: Topology 2 + +In Topology 2, the Ambient IoT device communicates bidirectionally with an intermediate node between the device and basestation. In this topology, the intermediate node can be a relay, IAB node, UE, repeater, etc. which is capable of Ambient IoT. The intermediate node transfers Ambient IoT data and/or signalling between BS and the Ambient IoT device. + +#### 4.2.1.3 Topology 3: BS $\leftrightarrow$ assisting node $\leftrightarrow$ Ambient IoT device $\leftrightarrow$ BS + +![Diagram of Topology 3 with downlink assistance. A Base Station (BS) on the left is connected to an assisting node (a light blue circle) by a dashed double-headed arrow labeled 'Uu'. The assisting node is connected to an Ambient IoT device (represented by a small square icon) by a solid double-headed arrow. The Ambient IoT device is also connected back to the BS by a solid double-headed arrow. Above the BS, a horizontal arrow points right, labeled 'Ambient IoT data/signaling'.](5a95b187de0044da69b7322e04761b86_img.jpg) + +Diagram of Topology 3 with downlink assistance. A Base Station (BS) on the left is connected to an assisting node (a light blue circle) by a dashed double-headed arrow labeled 'Uu'. The assisting node is connected to an Ambient IoT device (represented by a small square icon) by a solid double-headed arrow. The Ambient IoT device is also connected back to the BS by a solid double-headed arrow. Above the BS, a horizontal arrow points right, labeled 'Ambient IoT data/signaling'. + +Figure 4.2.1.3-1: Topology 3 with downlink assistance + +![Figure 4.2.1.3-2: Topology 3 with uplink assistance. The diagram shows a Base Station (BS) on the left, an Ambient IoT device in the center, and an assisting node on the right. A solid arrow points from the BS to the Ambient IoT device. A dashed arrow points from the Ambient IoT device to the assisting node. A solid arrow points from the assisting node to the BS. A dashed arrow points from the BS to the Ambient IoT device. A label 'Uu' is placed above the dashed arrow from the BS to the Ambient IoT device. A label 'Ambient IoT data/signaling' is placed above the solid arrow from the BS to the Ambient IoT device.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Figure 4.2.1.3-2: Topology 3 with uplink assistance. The diagram shows a Base Station (BS) on the left, an Ambient IoT device in the center, and an assisting node on the right. A solid arrow points from the BS to the Ambient IoT device. A dashed arrow points from the Ambient IoT device to the assisting node. A solid arrow points from the assisting node to the BS. A dashed arrow points from the BS to the Ambient IoT device. A label 'Uu' is placed above the dashed arrow from the BS to the Ambient IoT device. A label 'Ambient IoT data/signaling' is placed above the solid arrow from the BS to the Ambient IoT device. + +Figure 4.2.1.3-2: Topology 3 with uplink assistance + +In Topology 3, the Ambient IoT device transmits data/signalling to a basestation, and receives data/signalling from the assisting node; or the Ambient IoT device receives data/signalling from a basestation and transmits data/signalling to the assisting node. In this topology, the assisting node can be a relay, IAB, UE, repeater, etc. which is capable of ambient IoT. + +#### 4.2.1.4 Topology 4: UE $\leftrightarrow$ Ambient IoT device + +![Figure 4.2.1.4-1: Topology 4. The diagram shows a User Equipment (UE) on the left and an Ambient IoT device on the right. A solid arrow points from the UE to the Ambient IoT device. A dashed arrow points from the Ambient IoT device to the UE. A label 'Ambient IoT data/signaling' is placed above the solid arrow from the UE to the Ambient IoT device.](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg) + +Figure 4.2.1.4-1: Topology 4. The diagram shows a User Equipment (UE) on the left and an Ambient IoT device on the right. A solid arrow points from the UE to the Ambient IoT device. A dashed arrow points from the Ambient IoT device to the UE. A label 'Ambient IoT data/signaling' is placed above the solid arrow from the UE to the Ambient IoT device. + +Figure 4.2.1.4-1: Topology 4 + +In Topology 4, the Ambient IoT device communicates bidirectionally with a UE. The communication between UE and the ambient IoT device includes Ambient IoT data and/or signalling. + +### 4.2.2 Deployment scenarios + +#### 4.2.2.1 Deployment scenario 1: Device indoors, basestation indoors + +With Ambient IoT device indoors and basestation indoors, this deployment scenario is characterized according to Table 4.2.2.1-1. + +Table 4.2.2.1-1: Characteristics of deployment scenario 1 + +| Applicable representative use cases | Characteristics | Description (NOTE 1) | +|---------------------------------------------------------------------------|----------------------------------------------------|----------------------------------------| +| Indoor inventory
Indoor sensor
Indoor positioning
Indoor command | Environment (of device) | Indoor | +| | Basestation characteristic (if any) | Micro- or pico-cell | +| | Connectivity topology | Topology (1), (2), (3) | +| | Spectrum | Licensed FDD, licensed TDD, unlicensed | +| | Coexistence with existing 3GPP technologies | Co-site or new site | +| | Traffic assumption | DT and DO | +| | Device characteristic | Device A or Device B or Device C | + +NOTE 1: Descriptions may not be applicable for some Devices (A, B). + +#### 4.2.2.2 Deployment scenario 2: Device indoors, basestation outdoors + +With Ambient IoT device indoors and basestation outdoors, this deployment scenario is characterized according to Table 4.2.2.2-1. + +**Table 4.2.2.2-1: Characteristics of deployment scenario 2** + +| Applicable representative use cases | Characteristics | Description (NOTE 1) | +|---------------------------------------------------------------------------|----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| +| Indoor inventory
Indoor sensor
Indoor positioning
Indoor command | Environment (of device) | Indoor | +| | Basestation characteristic (if any) | Macro- or Micro- cell BS | +| | Connectivity topology | Topology (1), (2), (3)
Note: The location of intermediate or assisting node (if any) is indoor or outdoor | +| | Spectrum | Licensed FDD, licensed TDD, unlicensed | +| | Coexistence with existing 3GPP technologies | Co-site or new site | +| | Traffic assumption | DT and DO | +| | Device characteristic | Device C may support Topology (1), (2), (3),
Device A may support Topology (2),
Device B may support Topology (2), (3) | + +NOTE 1: Descriptions may not be applicable for some Devices (A, B). + +#### 4.2.2.3 Deployment scenario 3: Device indoors, UE-based reader + +With Ambient IoT device indoors and UE-based reader, this deployment scenario is characterized according to Table 4.2.2.3-1. + +**Table 4.2.2.3-1: Characteristics of deployment scenario 3** + +| Applicable representative use cases | Characteristics | Description (NOTE 1) | +|---------------------------------------------------------------------------|----------------------------------------------------|----------------------------------------| +| Indoor inventory
Indoor sensor
Indoor positioning
Indoor command | Environment (of device) | Indoor | +| | Basestation characteristic (if any) | None | +| | Connectivity topology | Topology (4) | +| | Spectrum | Licensed FDD, licensed TDD, unlicensed | +| | Coexistence with existing 3GPP technologies | NA | +| | Traffic assumption | DT and DO | +| | Device characteristic | Device A or Device B or Device C | + +NOTE 1: Descriptions may not be applicable for some Devices (A, B). + +#### 4.2.2.4 Deployment scenario 4: Device outdoors, basestation outdoors + +With Ambient IoT device outdoors and basestation outdoors, this deployment scenario is characterized according to Table 4.2.2.4-1. + +**Table 4.2.2.4-1: Characteristics of deployment scenario 4** + +| Applicable representative use cases | Characteristics | Description (NOTE 1) | +|-------------------------------------------------------------------------------|----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| Outdoor inventory
Outdoor sensor
Outdoor positioning
Outdoor command | Environment (of device) | Outdoor | +| | Basestation characteristic (if any) | Macro- or Micro- cell BS | +| | Connectivity topology | Topology (1), (2), (3) | +| | Spectrum | Licensed FDD, licensed TDD, or unlicensed. | +| | Coexistence with existing 3GPP technologies | Co-site or new site | +| | Traffic assumption | DT and DO | +| | Device characteristic | Device C may support Topology (1), (2), (3),
Device A may support Topology (2), Device B may support Topology (2), (3) | + +NOTE 1: Descriptions may not be applicable for some Devices (A, B). + +#### 4.2.2.5 Deployment scenario 5: Device outdoors, UE-based reader + +With Ambient IoT device outdoors and UE-based reader, this deployment scenario is characterized according to Table 4.2.2.5-1. + +**Table 4.2.2.5-1: Characteristics of deployment scenario 5** + +| Applicable representative use cases | Characteristics | Description (NOTE 1) | +|-------------------------------------------------------------------------------|----------------------------------------------------|----------------------------------------| +| Outdoor inventory
Outdoor sensor
Outdoor positioning
Outdoor command | Environment (of device) | Outdoor | +| | Basestation characteristic (if any) | None | +| | Connectivity topology | Topology (4) | +| | Spectrum | Licensed FDD, licensed TDD, unlicensed | +| | Coexistence with existing 3GPP technologies | NA | +| | Traffic assumption | DT and DO | +| | Device characteristic | Device A or Device B or Device C | + +NOTE 1: Descriptions may not be applicable for some Devices (A, B). + +## 4.3 Device categorization + +Ambient IoT devices are characterized in the study according to their energy storage capacity, and capability of generating RF signals for their transmissions. + +The study considers that a device has either: + +- No energy storage at all; or +- Limited energy storage + +Relying on these storage capacities, the study considers the following set of Ambient IoT devices: + +- Device A: No energy storage, no independent signal generation/amplification, i.e. backscattering transmission. +- Device B: Has energy storage, no independent signal generation, i.e. backscattering transmission. Use of stored energy can include amplification for reflected signals. +- Device C: Has energy storage, has independent signal generation, i.e., active RF components for transmission. + +A limited energy storage can be different among implementations within Device B or implementations within Device C, and different between Device B and Device C. Such storage is expected to be order(s) of magnitude smaller than an NB-IoT device would typically include. + +Device A, B, and C are able to demodulate control, data, etc from the relevant entity in RAN according to connectivity topology. + +# 5 RAN design targets + +## 5.1 Device power consumption + +For Device A, the power consumption target during transmitting/receiving is $\leq 1 \mu\text{W}$ or $\leq 10 \mu\text{W}$ , + +For Device B, the target during transmitting/receiving is such that: + +- Device A power consumption $\ll$ Device B power consumption $<$ Device C power consumption; or +- Device A power consumption $\leq$ Device B power consumption $<$ Device C power consumption. + +The device power consumption during transmitting/receiving for Device C is $\leq 1 \text{ mW}$ to $\leq 10 \text{ mW}$ . + +## 5.2 Device complexity + +For Device A, the complexity target is to be comparable to UHF RFID ISO18000-6C (EPC C1G2). + +For Device B, the target is such that: + +- Device A complexity $<$ Device B complexity $<$ Device C complexity. + +For Device C, the complexity target is to be orders-of-magnitude lower than NB-IoT. + +## 5.3 Coverage + +The coverage target for both DL and UL is represented by the maximum distance: + +- Between Ambient IoT device and basestation in Topology (1) and (3) +- Between Ambient IoT device and intermediate or assisting node in Topology (2) and (3), respectively +- Between Ambient IoT device and UE in Topology (4). + +Details relevant to the maximum distance such as sensitivity, BLER, transmit power, etc. are for WG expertise to study further. + +The design target of coverage is: + +By indoor / outdoor, grouping different Devices into a range that WGs can sub-select within + +- the maximum distance of 10 – 50 m for indoor +- the maximum distance of 50 – 500 m for outdoor + +NOTE: Different target values within these ranges may apply to different devices A/B/C and deployment scenarios 1-5. + +NOTE: If BS is present, then continuous coverage (from the device perspective) based on a typical ISD between base stations is assumed. This does not imply an assumption of any particular topology. + +NOTE: For Device A & B, the emitter-to-tag distance should be reported as part of the assessment. + +## 5.4 User experienced data rate + +The user experienced data rate target is, for the uplink and downlink, maximum not less than 5 kbps, and minimum not less than 0.1 kbps. + +## 5.5 Maximum message size + +The design target of maximum message size is approximately 1000 bits to be received by the Ambient IoT device, and approximately 1000 bits to be transmitted from the Ambient IoT device, based on the maximum application layer packet size. + +RAN1/RAN2 can refine as needed for TB size design. + +## 5.6 Latency + +The one-way end-to-end maximum latency targets, as defined in TR 22.840, are: + +- Longer latency target: 10 seconds +- Shorter latency target: 1 second + +A use case is assigned to a latency target according to TR 22.840. RAN WGs can refine a definition of latency suitable for their work within the above. + +NOTE: The time for charging the Ambient IoT device storage (if present) is not included in the latency defined above. Time for energy harvesting, charging, etc. is regarded as an implementation issue only. + +NOTE: The one-way end-to-end maximum latency is assumed to also include query/triggering time. + +## 5.7 Positioning accuracy + +The design target of absolute positioning accuracy when performed by the cellular network (including assisting nodes when present) is: + +- 1~3 meters @ 90% indoor location. +- Several tens of meters @ 90% outdoor location. + +The design target of relative ranging accuracy for topology 4 is: + +- 1~3 meters @ 90% indoor and outdoor location + +## 5.8 Connection/device density + +According to the consolidated potential KPIs in TR 22.840, the maximum connection density target is: + +- 150 devices per 100 m2 for indoor scenarios. +- 20 devices per 100 m2 for outdoor scenarios. + +RAN WGs will define the 2D or 3D distribution(s) of devices. + +## 5.9 Moving speed of device + +The design target of moving speed of Ambient IoT device is 10 km/h, at least for indoor scenarios. + +NOTE: Absolute speed is used in Topology (1), (2) and (3). Relative speed is used in Topology (4). + +# 6 Comparison and assessment + +## 6.1 Preliminary feasibility assessment + +### 6.1.1 Device power consumption + +Feasibility of power consumption for Device A at $\leq 1 \mu\text{W}$ level has been reported by reference to [3], [4], [5], [6], and at $\leq 10 \mu\text{W}$ level by [7] depending on component choices such as in [8]. Feasibility of power consumption for Device C at $\leq 1 \text{mW}$ level has been reported by reference to [9], [10], [11], [12], [13], and by reference in part to the receiver architectures discussed in the Rel-18 SI on low-power wake up signal/receiver [14] [15] at $\leq 10 \text{mW}$ level. For Device B, which adds energy storage to Device A and has been described as also potentially including (without limitation), e.g. reflection amplification, feasibility of power consumption in the order of hundreds of $\mu\text{W}$ has been reported by [7] depending on component choices such as in [16]. + +### 6.1.2 Device complexity + +Feasibility assessment for this aspect was presented on a qualitative basis by companies describing exemplary waveform, and/or transmitter, and/or receiver architectures which, according to their analysis, would satisfy the device power consumption design target. It was also observed that the amount of energy storage could affect device complexity. Examples of considered waveforms include OOK/FSK, and ASK. Examples of considered transmitter architectures for Device A/B include those based on backscattering technology, and receiver architectures based on envelope detection, while for Device C, very low power consumption heterodyne/homodyne architectures were reported as satisfying the complexity design target. + +On the other hand, aspects such as the memory required for security, authentication, etc., and hardware used for encryption processing would add to the complexity of the device. There were also discussions of the quality required in circuitry such as energy harvesting, backscattering, and PAs which, as their efficiency increases, tend to have higher complexity. + +Detailed analysis of designs which meet the device complexity requirement is considered to require WG-level technical expertise. + +### 6.1.3 Coverage + +Feasibility of a coverage target was assessed by sources differently for Devices A, B, C. In addition to typical elements comprising a 3GPP coverage evaluation, such as BS/intermediate/assistant node transmit power and receive sensitivity, device receiver sensitivity, propagation losses, etc. (which vary according to the specific calculation method), aspects particular to Ambient IoT devices were added. These include: + +- Device A/B backscattering activation power threshold +- Device B amplification (if any) +- Device A/B reflection loss +- Distance from carrier wave source to Ambient IoT device, for Device A/B +- Power of carrier wave source and/or incident power at Device A/B from carrier wave source + +Although different evaluation methodologies were adopted by sources [17] – [25], the coverage of Device A is reported as less than Device B (with or without amplification), which is less than Device C. The coverage of Ambient IoT devices relying on backscattering technology was reported to increase as the carrier wave source gets closer to the Ambient IoT device, due to the higher incident power on the device. + +### 6.1.4 User experienced data rate + +Full user-experienced data rate assessment was noted as requiring WG-level technical expertise, and detailed assumptions on air interface design. For TSG-level purposes, companies used simplified approximates. Peak data rate was one such approximant, where companies reported values above 5 kbps for uplink and downlink to be achievable + +according to various sets of assumptions including sufficient bandwidth, and in one case noted that the components assumed by reference to [26] would need further investigation whether the device power consumption target could be simultaneously met. One source [17] estimated data rate by accounting for device charging time and operation time, resulting in data rates 0.14 – 2.24 kbps for uplink and downlink. + +### 6.1.5 Maximum message size + +Companies' study of the feasibility of this design requirement was by reference to e.g. RFID which supports message sizes larger than about 1000 bits. It was also observed that the different Devices could be regarded as feasible for different maximum message sizes. + +### 6.1.6 Latency + +Feasibility of latency was reported typically by comparing a message size to a data rate, for example 5 kbps / 1000 bit = 200 ms latency for the largest message size at the target peak rate. Feasibility would also depend on a consideration of signalling procedures and possible random access-like procedure. + +### 6.1.7 Positioning accuracy + +Feasibility assessment for this aspect has been reported by reference to technologies of a similar complexity level, such as UHF RFID achieving 2-3 m accuracy in [27], [28], [29] indoors, and ultra-narrow IoT achieving from several tens to 100 or 150 m in [30], [31], [32] outdoors. It is also observed that Device A and B need to have a carrier wave source in an appropriate distance to be able to transmit signals for positioning. + +### 6.1.8 Connection/device density + +Feasibility of the target was discussed from the basis of assuming cell access procedures, and device addressing. It was discussed as applying a requirement on the design of such procedures, identities, etc. rather than being a matter for feasibility assessment before starting such designs. + +### 6.1.9 Moving speed of device + +The feasibility aspects that were reported related to the impact of Doppler shift or channel coherence on the possible types of modulation contemplated by companies for especially Device A and B. It was observed, without limiting RAN WG design scope, that at least for low-order non-OFDM modulation, Doppler impacts at the low moving-speed level implied in Clause 5.9 would likely be acceptable, although the impact on transmission times potentially a multiple of the coherence time should also be studied in RAN WGs. + +## 6.2 Required RAN functionalities + +The assumptions on required functionality have been studied on the basis of supporting certain RAN design targets as well as other requirements. At least the following potential functionalities are identified in different sets, respectively, according to the purpose of each functionality assumed to be mainly used for. An entry in the tables below neither implies nor precludes RAN specification impact. + +**Table 6.2-1: Required RAN functionality set #1: for supporting RAN design target** + +| Design target | Functionality | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Device power and complexity |
  • - Ultra-low power transceiver / Device architecture
  • - Transmitting based on backscattering (including carrier wave provision for backscattering) for Device A and Device B
  • - Low-complexity waveform / modulation / coding / signal / channel / synchronization scheme, if applicable to Device, robust to frequency error and timing error
  • - Compact protocol stack and lightweight signaling procedure
| +| Coverage |
  • - Techniques for the required coverage with low device complexity (e.g., forward error correction, enough receiver sensitivity and transmitted power, reflection gain enhancement), if applicable and needed to the Device type
| +| User experienced data rate |
  • - Compact protocol stack and lightweight signaling procedure
  • - Potential schemes as applicable, such as, e.g. flexible modulation/code rate, resource allocation, multiple access methods
| +| Maximum message size |
  • - Compact protocol stack and lightweight signaling procedure
  • - Signal/channel design which can deliver the maximum message size
| +| Latency |
  • - Access mechanisms and signaling procedures which allow meeting the latency target
| +| Positioning support |
  • - Positioning method(s) applicable to the connectivity topologies for the required positioning accuracy for Ambient IoT device
| +| Connection density |
  • - Efficient multiple access methods and contention handling
  • - Ability to control the operation for one or more of the Ambient IoT devices, within the applicable area, including e.g. the selection of devices
| +| Moving speed of device |
  • - Physical layer design (low-order modulation, reference signal etc. and others) robust to the appropriate ranges of moving speeds
| + +**Table 6.2-2: Required RAN functionality set #2: for supporting other requirements** + +| Requirement | Functionality | +|---------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Device management |
  • - RAN aspects of identification, activation/deactivation, and other management functionalities of Ambient IoT devices and other involved devices (e.g. readers) if applicable, and related signalling to/from the CN if any/needed
| +| Security* |
  • - Authentication (when needed), encryption, data integrity, authorization (when needed)
| +| Mobility |
  • - Mobility management (at least cell selection/re-selection -like function) for device C
  • - Handling for Devices A and B
| +| Interference management and coexistence |
  • - Interference management/coordination scheme
  • - Potential full duplex capability of BS/UE, including self-interference suppression, may be required for BS/UE to communicate with Device A and Device B, if carrier wave transmission and backscatter reception is performed simultaneously at least on the same band by the same BS/UE.
  • - Coexistence with existing and adjacent network infrastructure, and possibility to reuse existing network deployments or use new network deployments.
| +| CN connectivity |
  • - RAN functionality for Ambient IoT to support CN (when present), with possibility of potential lightweight protocol stack architecture and simplified signaling procedures.
| +| Compatibility among connectivity topologies |
  • - From the perspective of the Ambient IoT device, strive for operation to be agnostic to RAN connectivity topologies.
| + +\*NOTE: This does not necessarily mean security has RAN impact, further study is needed. + +The required functionalities may not all be addressed in the same Release. + +In the above, both existing and new techniques may be considered. + +# 7 Conclusions and recommendations + +## 7.1 Summary + +The study has described eight rUCs in RAN, being indoor/outdoor for each of inventory, sensors, positioning, and command. These rUCs encompass the UCs or traffic scenarios from TR 22.840 as shown in Table 4.1-1. + +Four general connectivity topologies were studied in Clause 4.2.1: BS $\leftrightarrow$ Ambient IoT device, BS $\leftrightarrow$ intermediate node $\leftrightarrow$ Ambient IoT device, BS $\leftrightarrow$ assisting node $\leftrightarrow$ Ambient IoT device $\leftrightarrow$ BS, and UE $\leftrightarrow$ Ambient IoT device. + +Three devices were studied: Device A, B, and C, differentiated according to inclusion of backscattering transmission or independent signal generation, and inclusion or not of energy storage. + +Together with other characteristics, the topologies and devices were used to study deployment scenarios for Ambient IoT, shown in Clause 4.2.2, differentiated according to whether the device and basestation/UE-based reader are respectively indoors or outdoors. + +A set of RAN design targets were developed, complementary to, and/or derived from, the requirements reported in TR 22.840, in Clause 5. Further details of these targets are assumed to be provided by WG-level expertise. + +A non-exclusive list of functionalities needed in Ambient IoT from the RAN perspective was formulated on the basis of supporting the RAN design targets, and for supporting other requirements. The study has not investigated in detail the implication of CN-related functionalities. + +Finally, a preliminary feasibility assessment was conducted on the basis of the set of design targets in Clause 5. This was by a mixture of reference to external sources, characteristics of, or hardware used by, other technologies, and companies' own analyses. + +## 7.2 Recommendations + +It is concluded in preliminary feasibility analysis at TSG-RAN level that Ambient IoT is feasible and beneficial, and further WG-level study is recommended prior to normative work. + +For the initial WG-level study of Ambient IoT + +- RAN is recommended to down-select further starting from: + - Deployment scenario 1 with Topology 1 + - Deployment scenario 2 with Topology 1 + - Deployment scenario 2 with Topology 2 + - Deployment scenario 4 with Topology 1 + - Deployment scenario 4 with Topology 3 +- FR1 licensed spectrum is recommended + - Note: selection or prioritization between FDD and FDD/TDD is to be decided +- RAN is recommended to down-select to one or more of: + - Spectrum in-band to NR, in guard-band to LTE/NR, and in standalone band(s) + +It is recommended to direct the RAN WGs to use the design targets reported in Clause 5. The RAN WGs are expected to refine the design targets according to their technical expertise, as needed. + +# Annex A: Energy sources for energy harvesting + +Companies have reported the following energy sources for energy harvesting in literature: RF, solar/light, piezoelectric (kinetic/vibration), electromagnetic, electrostatic, heat/thermal, thermoelectric, magnetic, wind/water, acoustic, etc. + +# Annex B: Change history + +| Change history | | | | | | | | +|----------------|----------|-----------|----|-----|-----|---------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-12 | RAN#98e | RP-223073 | | | | Skeleton for Study on Ambient IoT (Internet of Things) in RAN | 0.0.1 | +| 2022-12 | RAN#98e | RP-223526 | | | | Skeleton for Study on Ambient IoT (Internet of Things) in RAN | 0.0.2 | +| 2023-03 | RAN#99 | RP-230419 | | | | TR 38.848 v0.1.0 Study on Ambient IoT (Internet of Things) | 0.1.0 | +| 2023-06 | RAN#100 | RP-231208 | | | | TR 38.848 v0.2.0 Study on Ambient IoT (Internet of Things) | 0.2.0 | +| 2023-09 | RAN#101 | RP-232230 | | | | TR 38.848 v0.3.0 Study on Ambient IoT (Internet of Things) | 0.3.0 | +| 2023-09 | RAN#101 | RP-232695 | | | | TR 38.848 v1.0.0 Study on Ambient IoT (Internet of Things) | 1.0.0 | +| 2023-09 | RAN #101 | - | | | | Approved by RAN #101 and put under CR control | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38849/0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg b/marked/Rel-18/38_series/38849/0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0789357410b844695692ada0ef48d2c0601d814a --- /dev/null +++ b/marked/Rel-18/38_series/38849/0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cdac7c7fc9ade1df46d9ee4d15325bafcdbe4d50d8244929e0e4c89a8c3483b5 +size 56235 diff --git a/marked/Rel-18/38_series/38849/1c427123350e0e73e2a109b79069314b_img.jpg b/marked/Rel-18/38_series/38849/1c427123350e0e73e2a109b79069314b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77019bfbf627b4884c0f5d94388285a56a51bbe9 --- /dev/null +++ b/marked/Rel-18/38_series/38849/1c427123350e0e73e2a109b79069314b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d667bc7b8534c12e195a1472e26480253648084e838962da93223514ed2cf9d3 +size 45451 diff --git a/marked/Rel-18/38_series/38849/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38849/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0384b52849c0b8bdf9ab09c34bbac6c933420758 --- /dev/null +++ b/marked/Rel-18/38_series/38849/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b188f95f6516c6d1b8fd12682bd9831c73daeed1330fad3564886d68ebcd2bca +size 9593 diff --git a/marked/Rel-18/38_series/38849/602ada2a012ff3cc38d91de2eec5b450_img.jpg b/marked/Rel-18/38_series/38849/602ada2a012ff3cc38d91de2eec5b450_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9c698c5e76a6fa72a09806c49a93df3f68d0d46 --- /dev/null +++ b/marked/Rel-18/38_series/38849/602ada2a012ff3cc38d91de2eec5b450_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e352a08150c4b51512af579496cc0a7d38cc967daea2ab5c7ebb79ef3edc4bfb +size 47085 diff --git a/marked/Rel-18/38_series/38849/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38849/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7927f61b1239d261225220b410e3ffed88c5ef0b --- /dev/null +++ b/marked/Rel-18/38_series/38849/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf1b852352c70ae4b6507e4a2cd8bd48142366a142f3f00a430c18206dfedd57 +size 5817 diff --git a/marked/Rel-18/38_series/38849/723827e0738d2743c3b3423760a5c48e_img.jpg b/marked/Rel-18/38_series/38849/723827e0738d2743c3b3423760a5c48e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a655ed0624d5d0a3e88a8450feb4abc92a5a23bd --- /dev/null +++ b/marked/Rel-18/38_series/38849/723827e0738d2743c3b3423760a5c48e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b79df2f7e8577e7cb2dcf27888d8aadfe524c79c38dca5b4fcab8e705d2f8271 +size 37507 diff --git a/marked/Rel-18/38_series/38849/939b79420df0cf962959ccef56f3371f_img.jpg b/marked/Rel-18/38_series/38849/939b79420df0cf962959ccef56f3371f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b05339e78b1872b228cb2ef8908e00d334835e0 --- /dev/null +++ b/marked/Rel-18/38_series/38849/939b79420df0cf962959ccef56f3371f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:589f59a2811dc58c6ceaf88222e2ca02391dc5aab9f515444a761e7d97f24157 +size 39126 diff --git a/marked/Rel-18/38_series/38849/a706c91f074ac2840c161a3d4a7c0f91_img.jpg b/marked/Rel-18/38_series/38849/a706c91f074ac2840c161a3d4a7c0f91_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a85ae3e49dddbf1ebf36e27e827e4d81934604f2 --- /dev/null +++ b/marked/Rel-18/38_series/38849/a706c91f074ac2840c161a3d4a7c0f91_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:323dc290549ce4b1d1d86d0cbbbfa1ea8813d61ae7788ae5241b47bdf94d8970 +size 48169 diff --git a/marked/Rel-18/38_series/38849/bafe3c344aef7f6f79dab49c9eca89a9_img.jpg b/marked/Rel-18/38_series/38849/bafe3c344aef7f6f79dab49c9eca89a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bde156b1a7173e561b9fbb82717094247493d376 --- /dev/null +++ b/marked/Rel-18/38_series/38849/bafe3c344aef7f6f79dab49c9eca89a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ce321963b61cec04aeee21560cfe2cce74bc67d779c6cff2be1a0e81e16ecd8 +size 53111 diff --git a/marked/Rel-18/38_series/38849/c17eaf807acd5faec68da19dd16929be_img.jpg b/marked/Rel-18/38_series/38849/c17eaf807acd5faec68da19dd16929be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cedae22de9e98ed3e4f9f56ddc28df5dc2a3327 --- /dev/null +++ b/marked/Rel-18/38_series/38849/c17eaf807acd5faec68da19dd16929be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bcb6c0dc85d3fec8e83e091ccfc8120a78511adb79512f9f3695bd60aae39364 +size 28067 diff --git a/marked/Rel-18/38_series/38849/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg b/marked/Rel-18/38_series/38849/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a63b25b388a49f030e76b8e7b8a68b13472db166 --- /dev/null +++ b/marked/Rel-18/38_series/38849/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96f0fc5f5fc38216c8e7680ce001f19ca9fd8d9dd3b55bc04e3997399958126f +size 38691 diff --git a/marked/Rel-18/38_series/38849/f85bf99d372e735d228361bf4d3cf7e6_img.jpg b/marked/Rel-18/38_series/38849/f85bf99d372e735d228361bf4d3cf7e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65e664287f4c29a5b63f89f74f77cd6e3fb6d3a7 --- /dev/null +++ b/marked/Rel-18/38_series/38849/f85bf99d372e735d228361bf4d3cf7e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88487a9a40d85e3fa1de937e792ea0e99744ebcfc997ea667063c533747df532 +size 28790 diff --git a/marked/Rel-18/38_series/38849/fbfbbc91a80a21fc8d0ff7ba9e5865e3_img.jpg b/marked/Rel-18/38_series/38849/fbfbbc91a80a21fc8d0ff7ba9e5865e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45cd6bf3373f552153996ba38addaacc2b2599b4 --- /dev/null +++ b/marked/Rel-18/38_series/38849/fbfbbc91a80a21fc8d0ff7ba9e5865e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6d19ab19400a53e41ea0e973f6b2abf91945d7982423852dfaa2eecb4b5cb11 +size 28088 diff --git a/marked/Rel-18/38_series/38849/raw.md b/marked/Rel-18/38_series/38849/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8637452c3fc358337411f35573969f460e31e154 --- /dev/null +++ b/marked/Rel-18/38_series/38849/raw.md @@ -0,0 +1,1271 @@ + + +# 3GPP TR 38.849 V18.2.0 (2023-12) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Networks; Introduction of 6GHz NR unlicensed operation (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, consisting of 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 red signal icon consisting of three curved lines. Below the icon, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif 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 of terms, symbols and abbreviations..... | 7 | +| 3.1 Terms..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 Background ..... | 8 | +| 5 NR Frequency band definition..... | 8 | +| 5.1 Band definition..... | 8 | +| 5.1.1 Band definition for lower 6GHz NR unlicensed operation..... | 8 | +| 5.1.2 Band definition for the full 6GHz NR unlicensed operation ..... | 8 | +| 5.2 NR-ARFCN and GSCN ..... | 9 | +| 5.2.1 NR-ARFCN and GSCN for full 6GHz NR unlicensed operation ..... | 9 | +| 5.2.2 NR-ARFCN and GSCN for lower 6GHz NR unlicensed operation ..... | 9 | +| 6 RF requirements..... | 10 | +| 6.1 UE specific ..... | 10 | +| 6.1.1 Transmitter characteristics..... | 10 | +| 6.1.1.1 A-MPR for a NS(s) for lower 6GHz NR unlicensed operation in Europe. .... | 11 | +| 6.1.1.1.1 EU/CEPT..... | 11 | +| 6.1.1.2.2 Australia and New Zealand ..... | 16 | +| 6.1.1.2.3 Japan..... | 17 | +| 6.1.1.2 A-MPR for a NS(s) for the full 6GHz NR unlicensed operation..... | 20 | +| 6.1.1.2.1 Canada..... | 20 | +| 6.1.1.2.2 South Korea..... | 23 | +| 6.1.1.2.3 Peru and Chile ..... | 26 | +| 6.1.1.2.4 Brazil ..... | 27 | +| 6.2 BS specific..... | 29 | +| 7 RRM..... | 29 | +| 7.1 Frequency bands grouping ..... | 29 | +| Annex A (informative): Change history..... | 30 | + +# 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 Work Item on New Radio (NR) Access Technology, covering introduction of lower 6GHz NR unlicensed operation for Europe (NR\_6GHz\_unlic\_EU) and in the 5925-7125 MHz range for other regions (NR\_6GHz\_unlic\_full). + +# --- 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 37.890: Feasibility Study on 6 GHz for LTE and NR in Licensed and Unlicensed Operations + +# --- 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]. + +| | | +|----------|------------------------------------------------------------------------| +| ACLR | Adjacent Channel Leakage Ratio | +| ACS | Adjacent Channel Selectivity | +| BS | Base Station | +| BW | Bandwidth | +| EIRP | Effective Isotropic Radiated Power | +| FR | Frequency Range | +| GSCN | Global Synchronization Channel Number | +| ICS | In-Channel Selectivity | +| ITU-R | Radiocommunication Sector of the International Telecommunication Union | +| NR | New Radio | +| NR-ARFCN | NR Absolute Radio Frequency Channel Number | + +| | | +|-----|----------------------| +| OTA | Over The Air | +| RF | Radio Frequency | +| RX | Receiver | +| SCS | Sub-Carrier Spacing | +| TDD | Time division Duplex | + +# 4 Background + +Administrations in Europe have had unlicensed operation in the range 5925 to 6425 MHz for consultation. The result of this consultation is that at the November 2020 meeting the ECC with ECC Decision (20)01 “on the harmonised use of the frequency bands 5945 to 6425 MHz for the implementation of Wireless Access Systems including Radio Local Area Networks (WAS/RLANs)” approved unlicensed operation in the range 5945 to 6425 MHz. This initiated this TR which has later been expanded to also include NR unlicensed operation in the 6 GHz band for other regions. + +NR-Unlicensed is standardized in Rel-16 with the definition of band n96 covering the spectrum range 5925-7125 MHz which is currently applicable in the USA only subject to FCC Report and Order FCC 20-51. For Rel-17 3GPP WG4 is tasked to also enable unlicensed operation in the range 5945 to 6425 MHz for European deployments and in the 5925-7125 MHz range for other regions. + +Regulatory information is maintained in [2]. + +# 5 NR Frequency band definition + +## 5.1 Band definition + +### 5.1.1 Band definition for lower 6GHz NR unlicensed operation + +A NR band for unlicensed operation in the range 5925-6425 MHz is defined as: + +**Table 5.1.1-1: NR operating bands in FR1** + +| NR operating band | Uplink (UL) operating band
BS receive / UE transmit
FUL,low – FUL,high | Downlink (DL) operating band
BS transmit / UE receive
FDL,low – FDL,high | Duplex mode | +|-----------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------|--------------------------------------------------------------------------------|------------------| +| n102 | 5925 MHz – 6425 MHz | 5925 MHz – 6425 MHz | TDD 3 | +| NOTE 3: This band is restricted to operation with shared spectrum channel access as defined in TS 37.213. | | | | + +**Table 5.1.1-2: Channel bandwidths and SCS per operating band in FR1** + +| NR Band | SCS (kHz) | Channel bandwidth (MHz) | | | | | | | | | | | | | | | +|---------|-----------|-------------------------|----|----|----|----|----|----|----|----|----|----|----|----|----|-----| +| | | 5 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | 50 | 60 | 70 | 80 | 90 | 100 | +| n102 | 15 | | | | 20 | | | | 40 | | | | | | | | +| | 30 | | | | 20 | | | | 40 | | | 60 | | 80 | | 100 | +| | 60 | | | | 20 | | | | 40 | | | 60 | | 80 | | 100 | + +### 5.1.2 Band definition for the full 6GHz NR unlicensed operation + +A NR band covering the full 6 GHz unlicensed range is defined as: + +**Table 5.1.2-1: NR operating bands in FR1** + +| NR operating band | Uplink (UL) operating band
BS receive / UE transmit
FUL,low – FUL,high | Downlink (DL) operating band
BS transmit / UE receive
FDL,low – FDL,high | Duplex mode | +|-----------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------|--------------------------------------------------------------------------------|------------------| +| n96 | 5925 MHz – 7125 MHz | 5925 MHz – 7125 MHz | TDD 3 | +| NOTE 3: This band is restricted to operation with shared spectrum channel access as defined in TS 37.213. | | | | + +**Table 5.1.2-2: Channel bandwidths and SCS per operating band in FR1** + +| NR Band | SCS (kHz) | Channel bandwidth (MHz) | | | | | | | | | | | | | | | +|---------|-----------|-------------------------|----|----|----|----|----|----|----|----|----|----|----|----|----|-----| +| | | 5 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | 50 | 60 | 70 | 80 | 90 | 100 | +| n96 | 15 | | | | 20 | | | | 40 | | | | | | | | +| | 30 | | | | 20 | | | | 40 | | | 60 | | 80 | | 100 | +| | 60 | | | | 20 | | | | 40 | | | 60 | | 80 | | 100 | + +## 5.2 NR-ARFCN and GSCN + +### 5.2.1 NR-ARFCN and GSCN for full 6GHz NR unlicensed operation + +Operation in the full 6GHz band is to be aligned with other technologies operation in the same shared spectrum restricted to the following NR-ARFCN and GSCN points. + +Applicable GSCN: + +- GSCN = {9548, 9562, 9576, 9590, 9603, 9617, 9631, 9645, 9659, 9673, 9687, 9701, 9714, 9728, 9742, 9756, 9770, 9784, 9798, 9812, 9826, 9840, 9853, 9867, 9881, 9895, 9909, 9923, 9937, 9951, 9964, 9978, 9992, 10006, 10020, 10034, 10048, 10062, 10076, 10090, 10103, 10117, 10131, 10145, 10159, 10173, 10187, 10201, 10214, 10228, 10242, 10256, 10270, 10284, 10298, 10312, 10325, 10339, 10353} + +Applicable NR-ARFCN: + +- For 20 MHz channel bandwidth, NREF = {795668, 797000, 798332, 799668, 801000, 802332, 803668, 805000, 806332, 807668, 809000, 810332, 811668, 813000, 814332, 815668, 817000, 818332, 819668, 821000, 822332, 823668, 825000, 826332, 827668, 829000, 830332, 831668, 833000, 834332, 835668, 837000, 838332, 839668, 841000, 842332, 843668, 845000, 846332, 847668, 849000, 850332, 851668, 853000, 854332, 855668, 857000, 858332, 859668, 861000, 862332, 863668, 865000, 866332, 867668, 869000, 870332, 871668, 873000, 874332} +- For 40 MHz channel bandwidth, NREF = {797668, 800332, 803000, 805668, 808332, 811000, 813668, 816332, 819000, 821668, 824332, 827000, 829668, 832332, 835000, 837668, 840332, 843000, 845668, 848332, 851000, 853668, 856332, 859000, 861668, 864332, 867000, 869668, 872332} +- For 60 MHz channel bandwidth, NREF = {798332, 799668, 803668, 805000, 809000, 810332, 814332, 815668, 819668, 821000, 825000, 826332, 830332, 831668, 835668, 837000, 841000, 842332, 846332, 847668, 851668, 853000, 857000, 858332, 862332, 863668, 867668, 869000, 873000} +- For 80 MHz channel bandwidth, NREF = {799000, 804332, 809668, 815000, 820332, 825668, 831000, 836332, 841668, 847000, 852332, 857668, 863000, 868332} +- For 100 MHz channel bandwidth, NREF = {799668, 803668, 810332, 814332, 821000, 825000, 831668, 835668, 842332, 846332, 853000, 857000, 863668, 867668, 869000, 870332, 871668} + +### 5.2.2 NR-ARFCN and GSCN for lower 6GHz NR unlicensed operation + +Operation in the lower 6GHz band is to be aligned with other technologies operation in the same shared spectrum restricted to the following NR-ARFCN and GSCN points. + +Applicable GSCN: + +- GSCN = {9548, 9562, 9576, 9590, 9603, 9617, 9631, 9645, 9659, 9673, 9687, 9701, 9714, 9728, 9742, 9756, 9770, 9784, 9798, 9812, 9826, 9840, 9853, 9867} + +Applicable NR-ARFCN: + +- For 20 MHz channel bandwidth, NREF = {795668, 797000, 798332, 799668, 801000, 802332, 803668, 805000, 806332, 807668, 809000, 810332, 811668, 813000, 814332, 815668, 817000, 818332, 819668, 821000, 822332, 823668, 825000, 826332, 827668} +- For 40 MHz channel bandwidth, NREF = {797668, 800332, 803000, 805668, 808332, 811000, 813668, 816332, 819000, 821668, 824332, 827000} +- For 60 MHz channel bandwidth, NREF = {798332, 799668, 803668, 805000, 809000, 810332, 814332, 815668, 819668, 821000, 825000, 826332} +- For 80 MHz channel bandwidth, NREF = {799000, 804332, 809668, 815000, 820332, 825668} +- For 100 MHz channel bandwidth, NREF = {799668, 803668, 810332, 814332, 821000, 825000} + +# --- 6 RF requirements + +## 6.1 UE specific + +### 6.1.1 Transmitter characteristics + +This section details specific transmitter characteristics for a UE operating in the 6 GHz NR band. + +Table 6.1.1-1: Summary of NS values. + +| Country | Mode | | | +|--------------------|-------|-------|---------| +| | SP | LPI | VLP | +| Region 1 | | | | +| EU/CEPT | N/A | NS_58 | NS_64 | +| UK | N/A | NS_01 | NS_65 | +| Morocco | N/A | NS_01 | NS_65 | +| UAE | N/A | NS_01 | N/A | +| Saudi Arabia | N/A | NS_01 | N/A | +| Kenya | N/A | NS_01 | NS_68 | +| Qatar | N/A | NS_01 | NS_65 | +| Jordan | N/A | NS_01 | NS_65 | +| Russian Federation | N/A | NS_01 | NS_68 | +| South Africa | N/A | NS_58 | NS_64 | +| Region 2 | | | | +| US | NS_54 | NS_53 | [NS_66] | +| Canada | NS_54 | NS_59 | NS_66 | +| Brazil | N/A | NS_53 | NS_67 | +| Peru | N/A | NS_53 | N/A | +| Chile | N/A | NS_53 | N/A | +| Costa Rica | N/A | NS_01 | NS_65 | +| Colombia | N/A | NS_53 | N/A | +| Dominican Republic | N/A | NS_60 | NS_66 | +| Argentina | N/A | NS_53 | N/A | +| Region 3 | | | | +| South Korea | N/A | NS_60 | [NS_61] | +| Hong Kong | N/A | NS_58 | NS_64 | +| Australia | N/A | NS_01 | NS_68 | +| New Zealand | N/A | NS_01 | NS_68 | +| Malaysia | N/A | NS_01 | NS_65 | +| Japan | N/A | NS_63 | NS_69 | +| Singapore | N/A | NS_01 | NS_68 | + +#### 6.1.1.1 A-MPR for a NS(s) for lower 6GHz NR unlicensed operation in Europe. + +##### 6.1.1.1.1 EU/CEPT + +Additional emission requirements can be signalled by the network. Each additional emission requirement is associated with a unique network signalling (NS) value indicated in RRC signalling by an NR frequency band number of the applicable operating band as detailed in TS 38.101-1. + +To meet the additional requirements applicable in EU as given in EN 303 687, additional maximum power reduction (A-MPR) is allowed for the maximum output power as specified in Table 6.1.1.1.1-1 for low power indoor (LPI) with PC5 and in Table 6.1.1.1-1b for PC3. + +Table 6.1.1.1-1: A-MPR for PC5 LPI + +| Pre-coding | Modulation | RB Allocation | | +|------------|------------------------|------------------------|---------------------------| +| | | Full 2 (dB) | Partial 3 (dB) | +| DFT-s-ODFM | Pi/2 BPSK 4 | ≤ 1.5 | ≤ 2.5 | +| | QPSK | ≤ 2.0 | ≤ 3.5 | +| | 16 QAM | ≤ 2.5 | ≤ 4.0 | +| | 64 QAM | ≤ 3.5 | ≤ 4.5 | +| | 256 QAM | ≤ 5.0 | ≤ 5.5 | +| CP-OFDM | QPSK | ≤ 3.5 | ≤ 4.5 | +| | 16 QAM | ≤ 4.0 | ≤ 4.5 | +| | 64 QAM | ≤ 5.5 | ≤ 5.5 | +| | 256 QAM | ≤ 7.0 | ≤ 7.0 | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously allocated in the channel. The MPR applies to interlaced allocations with uplink resource allocation type 2 as specified in TS 38.214 [10]. + +NOTE 2: Full RB allocation A-MPR applies when all RB's in a 20 MHz channel or all RB's in all sub-bands for wideband operation are fully allocated and sub-bands are transmitted according to configuration A in Table 6.2F.2-2. + +NOTE 3: Partial RB allocation A-MPR applies when one or more RB's in one or more sub-bands are not allocated or when the transmitted sub-bands for wideband operation are transmitted according to configuration B in Table 6.2F.2-2. + +NOTE 4: Applicable to Pi/2-BPSK modulation when IE powerBoostPi2BPSK is set to 0. + +NOTE 5: The A-MPR applies instead of MPR for 20 MHz channel centered at the nearest NR-ARFCN corresponding to 5955 MHz, 40 MHz channel at the nearest NR-ARFCN corresponding to 5965 MHz, 60 MHz channel at the nearest NR-ARFCN corresponding to 5975 MHz, and 80 MHz channel at the nearest NR-ARFCN corresponding to 5985 MHz. For all other channels, A-MPR is zero and MPR as specified in Table 6.2F.2-1 applies. + +Table 6.1.1.1.1-1a: Signal setup + +| ID | Modulation | Waveform | Allocation | +|----|------------|------------|---------------------| +| 1 | Pi/2 BPSK | DFT-s-OFDM | Full | +| 2 | Pi/2 BPSK | DFT-s-OFDM | Interlaced | +| 3 | Pi/2 BPSK | DFT-s-OFDM | Wideband | +| 4 | Pi/2 BPSK | DFT-s-OFDM | Wideband Interlaced | +| 5 | QPSK | DFT-s-OFDM | Full | +| 6 | QPSK | CP-OFDM | Full | +| 7 | QPSK | DFT-s-OFDM | Interlaced | +| 8 | QPSK | CP-OFDM | Interlaced | +| 9 | QPSK | DFT-s-OFDM | Wideband | +| 10 | QPSK | CP-OFDM | Wideband | +| 11 | QPSK | DFT-s-OFDM | Wideband Interlaced | +| 12 | QPSK | CP-OFDM | Wideband Interlaced | +| 13 | 16QAM | DFT-s-OFDM | Full | +| 14 | 16QAM | CP-OFDM | Full | +| 15 | 16QAM | DFT-s-OFDM | Interlaced | +| 16 | 16QAM | CP-OFDM | Interlaced | +| 17 | 16QAM | DFT-s-OFDM | Wideband | +| 18 | 16QAM | CP-OFDM | Wideband | +| 19 | 16QAM | DFT-s-OFDM | Wideband Interlaced | +| 20 | 16QAM | CP-OFDM | Wideband Interlaced | +| 21 | 64QAM | DFT-s-OFDM | Full | +| 22 | 64QAM | CP-OFDM | Full | +| 23 | 64QAM | DFT-s-OFDM | Interlaced | +| 24 | 64QAM | CP-OFDM | Interlaced | +| 25 | 64QAM | DFT-s-OFDM | Wideband | +| 26 | 64QAM | CP-OFDM | Wideband | +| 27 | 64QAM | DFT-s-OFDM | Wideband Interlaced | +| 28 | 64QAM | CP-OFDM | Wideband Interlaced | +| 29 | 256QAM | DFT-s-OFDM | Full | +| 30 | 256QAM | CP-OFDM | Full | +| 31 | 256QAM | DFT-s-OFDM | Interlaced | +| 32 | 256QAM | CP-OFDM | Interlaced | +| 33 | 256QAM | DFT-s-OFDM | Wideband | +| 34 | 256QAM | CP-OFDM | Wideband | +| 35 | 256QAM | DFT-s-OFDM | Wideband Interlaced | +| 36 | 256QAM | CP-OFDM | Wideband Interlaced | + +![Scatter plot showing Power backoff in dB versus ID for various modulation schemes. The plot shows that as the modulation order increases (from Pi/2 BPSK to 256QAM), the required power backoff also increases. The data points are color-coded by modulation type: Pi/2 BPSK (blue), QPSK (orange), 16QAM (yellow), 64QAM (purple), and 256QAM (green).](602ada2a012ff3cc38d91de2eec5b450_img.jpg) + +| Modulation | ID Range | Power Backoff (dB) Range | +|------------|----------|--------------------------| +| Pi/2 BPSK | 1 - 4 | 1.0 - 4.2 | +| QPSK | 5 - 12 | 1.0 - 4.5 | +| 16QAM | 13 - 20 | 1.5 - 4.5 | +| 64QAM | 21 - 28 | 2.5 - 5.0 | +| 256QAM | 29 - 36 | 4.5 - 7.0 | + +Scatter plot showing Power backoff in dB versus ID for various modulation schemes. The plot shows that as the modulation order increases (from Pi/2 BPSK to 256QAM), the required power backoff also increases. The data points are color-coded by modulation type: Pi/2 BPSK (blue), QPSK (orange), 16QAM (yellow), 64QAM (purple), and 256QAM (green). + +Figure 6.1.1.1.1-1a: A-MPR simulation results for PC3 LPI in EU/CEPT. + +**Table 6.1.1.1.1-1b: A-MPR for PC3 LPI (1TX)** + +| Pre-coding | Modulation | RB Allocation | | +|------------|------------|------------------------|---------------------------| +| | | Full 2 (dB) | Partial 3 (dB) | +| DFT-s-ODFM | Pi/2 BPSK4 | ≤ 1.5 | ≤ 4.5 | +| | QPSK | ≤ 2.0 | ≤ 4.5 | +| | 16 QAM | ≤ 2.5 | ≤ 4.5 | +| | 64 QAM | ≤ 3.0 | ≤ 4.5 | +| | 256 QAM | ≤ 4.5 | ≤ 5.5 | +| CP-OFDM | QPSK | ≤ 3.5 | ≤ 5.0 | +| | 16 QAM | ≤ 4.0 | ≤ 5.0 | +| | 64 QAM | ≤ 4.5 | ≤ 5.5 | +| | 256 QAM | ≤ 6.5 | ≤ 7.0 | + +NOTE 1: The A-MPR shall apply to all SCS in all active 20 MHz sub-bands contiguously allocated in the channel. The MPR applies to interlaced allocations with uplink resource allocation type 2 as specified in TS 38.214 [10]. + +NOTE 2: Full RB allocation A-MPR applies when all RB's in a 20 MHz channel or all RB's in all sub-bands for wideband operation are fully allocated and sub-bands are transmitted according to configuration A in Table 6.2F.2-2. + +NOTE 3: Partial RB allocation A-MPR applies when one or more RB's in one or more sub-bands are not allocated or when the transmitted sub-bands for wideband operation are transmitted according to configuration B in Table 6.2F.2-2. + +NOTE 4: Applicable to Pi/2-BPSK modulation when IE powerBoostPi2BPSK is set to 0. + +NOTE 5: The A-MPR applies instead of MPR for 20 MHz channel centered at the nearest NR-ARFCN corresponding to 5955 MHz, 40 MHz channel at the nearest NR-ARFCN corresponding to 5965 MHz, 60 MHz channel at the nearest NR-ARFCN corresponding to 5975 MHz, 80 MHz channel at the nearest NR-ARFCN corresponding to 5985 MHz. For all other channels, A-MPR is zero and MPR as specified in Table 6.2F.2-1 applies. + +For very low power (VLP) operation the out-of-band emissions and in-band power spectral density requirements are much more restrictive than for LPI. For PC5 VLP, a comprehensive set of A-MPR simulation results is provided below for 20, 40, 60, and 80 MHz channels. In Figure 6.1.1.1-1 all channels in the band are represented while in Figure 6.1.1.1-2 lower edge channels are not illustrated since those are most impacted by the additional spurious emission requirement of -45 dBm/MHz. The lower edge channels found to be impacted were the ones centered at 5955 MHz for 20 MHz channels, 5965 MHz for 40 MHz channels, 5975 MHz and 5995 MHz for 60 MHz channels, and 5985 MHz for 80 MHz channels. + +**Table 6.1.1.1-2. Simulation scenarios for all CBW/SCS** + +| Scenario | Modulation | DFT/CP | Allocation | +|----------|------------|--------|-------------| +| 1 | QPSK | CP | Interlace_0 | +| 2 | QPSK | DFT-S | Interlace_0 | +| 3 | QPSK | CP | Full | +| 4 | QPSK | DFT-S | Full | +| 5 | 16QAM | CP | Interlace_0 | +| 6 | 16QAM | DFT-S | Interlace_0 | +| 7 | 16QAM | CP | Full | +| 8 | 16QAM | DFT-S | Full | +| 9 | 64QAM | CP | Interlace_0 | +| 10 | 64QAM | DFT-S | Interlace_0 | +| 11 | 64QAM | CP | Full | +| 12 | 64QAM | DFT-S | Full | +| 13 | 256QAM | CP | Interlace_0 | +| 14 | 256QAM | DFT-S | Interlace_0 | +| 15 | 256QAM | CP | Full | +| 16 | 256QAM | DFT-S | Full | + +![Scatter plot titled 'A-MPR for PC5 NR-U, VLP 6 GHz EU' showing Power backoff (dB) for 20, 40, 60, and 80 MHz channels across 16 scenarios. The y-axis ranges from 6 to 16 dB, and the x-axis shows scenario numbers 1 to 16. Data points are clustered by scenario, showing a wide range of power backoff values.](0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg) + +This scatter plot displays the power backoff (dB) for 20, 40, 60, and 80 MHz channels across 16 different scenarios. The y-axis represents the power backoff in dB, ranging from 6 to 16. The x-axis represents the scenario number from 1 to 16. For each scenario, there are multiple data points, indicating a variety of power backoff values. The distribution is relatively uniform across the scenarios, with values ranging from approximately 7 dB to 15 dB. + +| Scenario number | Power backoff (dB) range | +|-----------------|--------------------------| +| 1 | 9.1 - 14.8 | +| 2 | 7.6 - 13.8 | +| 3 | 9.4 - 12.9 | +| 4 | 6.8 - 11.2 | +| 5 | 9.7 - 14.9 | +| 6 | 8.4 - 14.2 | +| 7 | 10.1 - 12.9 | +| 8 | 8.0 - 11.7 | +| 9 | 11.7 - 14.9 | +| 10 | 10.4 - 14.2 | +| 11 | 12.1 - 12.9 | +| 12 | 10.0 - 11.8 | +| 13 | 14.1 - 14.9 | +| 14 | 12.8 - 14.2 | +| 15 | 14.5 - 14.7 | +| 16 | 12.3 - 13.0 | + +Scatter plot titled 'A-MPR for PC5 NR-U, VLP 6 GHz EU' showing Power backoff (dB) for 20, 40, 60, and 80 MHz channels across 16 scenarios. The y-axis ranges from 6 to 16 dB, and the x-axis shows scenario numbers 1 to 16. Data points are clustered by scenario, showing a wide range of power backoff values. + +Figure 6.1.1.1.1-1. Power backoff for 20, 40, 60, and 80 MHz channels + +![Scatter plot titled 'A-MPR for PC5 NR-U, VLP 6 GHz EU' showing Power backoff (dB) with lower edge channels excluded across 16 scenarios. The y-axis ranges from 6 to 16 dB, and the x-axis shows scenario numbers 1 to 16. Data points are more tightly clustered than in the previous figure.](bafe3c344aef7f6f79dab49c9eca89a9_img.jpg) + +This scatter plot displays the power backoff (dB) with lower edge channels excluded across 16 different scenarios. The y-axis represents the power backoff in dB, ranging from 6 to 16. The x-axis represents the scenario number from 1 to 16. The data points are more tightly clustered than in the previous figure, indicating a more consistent power backoff across scenarios. The values range from approximately 7 dB to 14.5 dB. + +| Scenario number | Power backoff (dB) range | +|-----------------|--------------------------| +| 1 | 9.1 - 9.2 | +| 2 | 7.6 - 9.9 | +| 3 | 9.4 - 9.5 | +| 4 | 6.8 - 7.5 | +| 5 | 9.7 - 9.8 | +| 6 | 8.4 - 9.8 | +| 7 | 10.1 - 10.2 | +| 8 | 8.0 - 8.5 | +| 9 | 11.7 - 11.8 | +| 10 | 10.4 - 10.9 | +| 11 | 12.1 - 12.2 | +| 12 | 10.0 - 10.5 | +| 13 | 14.1 - 14.2 | +| 14 | 12.8 - 13.3 | +| 15 | 14.5 - 14.6 | +| 16 | 12.3 - 13.0 | + +Scatter plot titled 'A-MPR for PC5 NR-U, VLP 6 GHz EU' showing Power backoff (dB) with lower edge channels excluded across 16 scenarios. The y-axis ranges from 6 to 16 dB, and the x-axis shows scenario numbers 1 to 16. Data points are more tightly clustered than in the previous figure. + +Figure 6.1.1.1.1-2. Power backoff with lower edge channels excluded + +Based on these simulation results, the A-MPR table for VLP is provided below in Table 6.1.1.1.1-3. + +Table 6.1.1.1.1-3. PC5 A-MPR table for VLP + +| Pre-coding | Modulation | RB Allocation (Note 2) | | RB Allocation (Note 3) | | +|------------|------------|------------------------|--------------|------------------------|--------------| +| | | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | +| DFT-s-ODFM | QPSK | ≤ 12 | ≤ 14 | ≤ 8 | ≤ 10 | +| | 16 QAM | ≤ 12 | ≤ 15 | ≤ 9 | ≤ 10 | +| | 64 QAM | ≤ 12 | ≤ 15 | ≤ 11 | ≤ 11 | +| | 256 QAM | ≤ 13 | ≤ 15 | ≤ 13 | ≤ 14 | +| CP-OFDM | QPSK | ≤ 13 | ≤ 15 | ≤ 10 | ≤ 10 | +| | 16 QAM | ≤ 13 | ≤ 15 | ≤ 11 | ≤ 10 | +| | 64 QAM | ≤ 13 | ≤ 15 | ≤ 13 | ≤ 12 | +| | 256 QAM | ≤ 15 | ≤ 15 | ≤ 15 | ≤ 15 | + +NOTE 1: Full allocation A-MPR applies when all RB's in a 20 MHz channel or all RB's in all sub-bands for wideband operation are fully allocated and all sub-bands are transmitted. Partial allocation A-MPR applies when one or more RB's in one or more sub-bands are not allocated or when not all transmitted sub-bands for wideband operation are transmitted. + +NOTE 2: Applicable for 20 MHz channels centered at the nearest NR-ARFCN corresponding to 5955 MHz, 40 MHz channels centered at the nearest NR-ARFCN corresponding to 5965 MHz, 60 MHz channels centered at the nearest NR-ARFCN corresponding to 5975 and 5995 MHz and 80 MHz channels centered at the nearest NR-ARFCN corresponding to 5985 MHz. + +NOTE 3: Applicable for all valid channels other than those enumerated under NOTE 2. + +##### 6.1.1.2.2 Australia and New Zealand + +Table 6.1.1.2.2-1: Signal setup (LPI). + +| ID | Modulation | Waveform | Allocation | +|----|------------|------------|---------------------| +| 1 | QPSK | DFT-s-OFDM | Full | +| 2 | QPSK | CP-OFDM | Full | +| 3 | QPSK | DFT-s-OFDM | Interlaced | +| 4 | QPSK | CP-OFDM | Interlaced | +| 5 | QPSK | DFT-s-OFDM | Wideband | +| 6 | QPSK | CP-OFDM | Wideband | +| 7 | QPSK | DFT-s-OFDM | Wideband Interlaced | +| 8 | QPSK | CP-OFDM | Wideband Interlaced | +| 9 | 16QAM | DFT-s-OFDM | Full | +| 10 | 16QAM | CP-OFDM | Full | +| 11 | 16QAM | DFT-s-OFDM | Interlaced | +| 12 | 16QAM | CP-OFDM | Interlaced | +| 13 | 16QAM | DFT-s-OFDM | Wideband | +| 14 | 16QAM | CP-OFDM | Wideband | +| 15 | 16QAM | DFT-s-OFDM | Wideband Interlaced | +| 16 | 16QAM | CP-OFDM | Wideband Interlaced | +| 17 | 64QAM | DFT-s-OFDM | Full | +| 18 | 64QAM | CP-OFDM | Full | +| 19 | 64QAM | DFT-s-OFDM | Interlaced | +| 20 | 64QAM | CP-OFDM | Interlaced | +| 21 | 64QAM | DFT-s-OFDM | Wideband | +| 22 | 64QAM | CP-OFDM | Wideband | +| 23 | 64QAM | DFT-s-OFDM | Wideband Interlaced | +| 24 | 64QAM | CP-OFDM | Wideband Interlaced | +| 25 | 256QAM | DFT-s-OFDM | Full | +| 26 | 256QAM | CP-OFDM | Full | +| 27 | 256QAM | DFT-s-OFDM | Interlaced | +| 28 | 256QAM | CP-OFDM | Interlaced | +| 29 | 256QAM | DFT-s-OFDM | Wideband | +| 30 | 256QAM | CP-OFDM | Wideband | +| 31 | 256QAM | DFT-s-OFDM | Wideband Interlaced | +| 32 | 256QAM | CP-OFDM | Wideband Interlaced | + +![Scatter plot showing Power backoff (Y-axis, 0 to 10) versus ID (X-axis, 1 to 32) for A-MPR simulation results for PC5 LPI in Australia. The plot shows data points for four modulation schemes: QPSK (blue circles), 16QAM (orange circles), 64QAM (yellow circles), and 256QAM (purple circles). The power backoff values generally range between 6 and 9 dB across the different IDs and modulations.](cbc4516eb885829fe8c9dabc0946dcbe_img.jpg) + +Scatter plot showing Power backoff (Y-axis, 0 to 10) versus ID (X-axis, 1 to 32) for A-MPR simulation results for PC5 LPI in Australia. The plot shows data points for four modulation schemes: QPSK (blue circles), 16QAM (orange circles), 64QAM (yellow circles), and 256QAM (purple circles). The power backoff values generally range between 6 and 9 dB across the different IDs and modulations. + +Figure 6.1.1.2.2-1: A-MPR simulation results for PC5 LPI in Australia. + +Table 6.1.1.2.2-2: A-MPR for PC5 LPI in Australia + +| Pre-coding | Modulation | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | +|------------|------------|---------------------------------------------------------|--------------|-----------|--------------|-----------|--------------|-----------|--------------| +| | | 20 MHz | | 40 MHz | | 60 MHz | | 80 MHz | | +| | | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | +| DFT-s-ODFM | QPSK | ≤ 7.0 | ≤ 9.5 | ≤ 6.0 | ≤ 6.5 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | +| | 16 QAM | ≤ 7.0 | ≤ 9.5 | ≤ 6.0 | ≤ 6.5 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | +| | 64 QAM | ≤ 7.0 | ≤ 9.5 | ≤ 6.0 | ≤ 6.5 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | +| | 256 QAM | ≤ 7.0 | ≤ 9.5 | ≤ 6.0 | ≤ 6.5 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | +| CP-OFDM | QPSK | ≤ 7.0 | ≤ 9.5 | ≤ 6.0 | ≤ 6.5 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | +| | 16 QAM | ≤ 7.0 | ≤ 9.5 | ≤ 6.0 | ≤ 6.5 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | +| | 64 QAM | ≤ 7.0 | ≤ 9.5 | ≤ 6.0 | ≤ 6.5 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | +| | 256 QAM | ≤ 7.0 | ≤ 9.5 | ≤ 6.0 | ≤ 6.5 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | + +NOTE 1: Full allocation A-MPR applies when all RB's in a 20 MHz channel or all RB's in all sub-bands for wideband operation are fully allocated and all sub-bands are transmitted. Partial allocation A-MPR applies when one or more RB's in one or more sub-bands are not allocated but when all sub-bands within the channel are transmitted. When not all sub-bands within the channel are transmitted, the A-MPR associated with the channel bandwidth according to the bandwidth of the contiguously transmitted sub-bands and according to the allocation type applies. + +##### 6.1.1.2.3 Japan + +Table 6.1.1.2.3-1: Signal setup (LPI and VLP). + +| ID | Modulation | Waveform | Allocation | +|----|------------|------------|---------------------| +| 1 | Pi/2 BPSK | DFT-s-OFDM | Full | +| 2 | Pi/2 BPSK | DFT-s-OFDM | Interlaced | +| 3 | Pi/2 BPSK | DFT-s-OFDM | Wideband | +| 4 | Pi/2 BPSK | DFT-s-OFDM | Wideband Interlaced | +| 5 | QPSK | DFT-s-OFDM | Full | +| 6 | QPSK | CP-OFDM | Full | +| 7 | QPSK | DFT-s-OFDM | Interlaced | +| 8 | QPSK | CP-OFDM | Interlaced | +| 9 | QPSK | DFT-s-OFDM | Wideband | +| 10 | QPSK | CP-OFDM | Wideband | +| 11 | QPSK | DFT-s-OFDM | Wideband Interlaced | +| 12 | QPSK | CP-OFDM | Wideband Interlaced | +| 13 | 16QAM | DFT-s-OFDM | Full | +| 14 | 16QAM | CP-OFDM | Full | +| 15 | 16QAM | DFT-s-OFDM | Interlaced | +| 16 | 16QAM | CP-OFDM | Interlaced | +| 17 | 16QAM | DFT-s-OFDM | Wideband | +| 18 | 16QAM | CP-OFDM | Wideband | +| 19 | 16QAM | DFT-s-OFDM | Wideband Interlaced | +| 20 | 16QAM | CP-OFDM | Wideband Interlaced | +| 21 | 64QAM | DFT-s-OFDM | Full | +| 22 | 64QAM | CP-OFDM | Full | +| 23 | 64QAM | DFT-s-OFDM | Interlaced | +| 24 | 64QAM | CP-OFDM | Interlaced | +| 25 | 64QAM | DFT-s-OFDM | Wideband | +| 26 | 64QAM | CP-OFDM | Wideband | +| 27 | 64QAM | DFT-s-OFDM | Wideband Interlaced | +| 28 | 64QAM | CP-OFDM | Wideband Interlaced | +| 29 | 256QAM | DFT-s-OFDM | Full | +| 30 | 256QAM | CP-OFDM | Full | +| 31 | 256QAM | DFT-s-OFDM | Interlaced | +| 32 | 256QAM | CP-OFDM | Interlaced | +| 33 | 256QAM | DFT-s-OFDM | Wideband | +| 34 | 256QAM | CP-OFDM | Wideband | +| 35 | 256QAM | DFT-s-OFDM | Wideband Interlaced | +| 36 | 256QAM | CP-OFDM | Wideband Interlaced | + +![Scatter plot showing Power backoff in dB versus ID for various modulation schemes. The plot shows that as the modulation order increases (from Pi/2 BPSK to 256QAM), the required power backoff also increases. The data points are grouped by modulation type: Pi/2 BPSK (blue diamonds), QPSK (orange circles), 16QAM (yellow triangles), 64QAM (purple diamonds), and 256QAM (green diamonds).](a706c91f074ac2840c161a3d4a7c0f91_img.jpg) + +| Modulation | ID Range | Power Backoff (dB) Range | +|------------|----------|--------------------------| +| Pi/2 BPSK | 1 - 4 | 0.5 - 2.5 | +| QPSK | 5 - 12 | 1.5 - 4.8 | +| 16QAM | 13 - 20 | 2.0 - 5.0 | +| 64QAM | 21 - 28 | 3.5 - 5.5 | +| 256QAM | 29 - 36 | 5.0 - 7.0 | + +Scatter plot showing Power backoff in dB versus ID for various modulation schemes. The plot shows that as the modulation order increases (from Pi/2 BPSK to 256QAM), the required power backoff also increases. The data points are grouped by modulation type: Pi/2 BPSK (blue diamonds), QPSK (orange circles), 16QAM (yellow triangles), 64QAM (purple diamonds), and 256QAM (green diamonds). + +Figure 6.1.1.2.3-1: A-MPR simulation results for PC5 LPI in Japan. + +Table 6.1.1.2.3-3a: A-MPR for PC5 LPI in Japan (lower edge) + +| Pre-coding | Modulation | RB Allocation (Note 2) | RB Allocation (Note 3) | | +|------------|------------------------|------------------------|------------------------|--------------| +| | | Full/Partial | Full (dB) | Partial (dB) | +| DFT-s-OFDM | PI/2 BPSK 4 | See Table PC5 MPR | ≤ 2.0 | ≤ 3.0 | +| | QPSK | | ≤ 2.5 | ≤ 3.5 | +| | 16 QAM | | ≤ 3.0 | ≤ 3.5 | +| | 64 QAM | | ≤ 3.5 | ≤ 4.5 | +| | 256 QAM | | ≤ 5.0 | ≤ 5.5 | +| CP-OFDM | QPSK | | ≤ 4.5 | ≤ 5.0 | +| | 16 QAM | | ≤ 4.5 | ≤ 5.5 | +| | 64 QAM | | ≤ 5.5 | ≤ 5.5 | +| | 256 QAM | | ≤ 7.0 | ≤ 7.0 | + +NOTE 1: Full allocation A-MPR applies when all RB's in a 20 MHz channel or all RB's in all sub-bands for wideband operation are fully allocated and all sub-bands are transmitted. Partial allocation A-MPR applies when one or more RB's in one or more sub-bands are not allocated or when not all transmitted sub-bands for wideband operation are transmitted. + +NOTE 2: Applicable for all valid channels and bandwidths other than those enumerated in NOTE 3. + +NOTE 3: Applicable for 40 MHz channels centered at the nearest NR-ARFCN corresponding to [5965 MHz], 60 MHz channels centered at the nearest NR-ARFCN corresponding to [5975 and 5995 MHz], and 80 MHz channels centered at the nearest NR-ARFCN corresponding to [5985 MHz]. + +NOTE 4: Applicable to Pi/2-BPSK modulation when IE powerBoostPi2BPSK is set to 0. + +NOTE 5: Channel bandwidth sizes of 60MHz and 100MHz are not applicable for this network signalling. + +Table 6.1.1.2.3-3b: A-MPR for PC5 LPI in Japan (upper edge) + +| Pre-coding | Modulation | RB Allocation (Note 3) | | +|------------|------------------------|------------------------|--------------| +| | | Full (dB) | Partial (dB) | +| DFT-s-OFDM | PI/2 BPSK 4 | ≤ 2.0 | ≤ 3.0 | +| | QPSK | ≤ 2.0 | ≤ 3.0 | +| | 16 QAM | ≤ 2.5 | ≤ 3.5 | +| | 64 QAM | ≤ 3.5 | ≤ 4.5 | +| | 256 QAM | ≤ 5.0 | ≤ 5.5 | +| CP-OFDM | QPSK | ≤ 3.5 | ≤ 4.5 | +| | 16 QAM | ≤ 4.0 | ≤ 4.5 | +| | 64 QAM | ≤ 5.5 | ≤ 5.5 | +| | 256 QAM | ≤ 7.0 | ≤ 7.0 | + +NOTE 1: Full allocation A-MPR applies when all RB's in a 20 MHz channel or all RB's in all sub-bands for wideband operation are fully allocated and all sub-bands are transmitted. Partial allocation A-MPR applies when one or more RB's in one or more sub-bands are not allocated or when not all transmitted sub-bands for wideband operation are transmitted. + +NOTE 2: Applicable for 20 MHz channels centered at the nearest NR-ARFCN corresponding to [6415 MHz], 40 MHz channels centered at the nearest NR-ARFCN corresponding to [6405 MHz] and 80 MHz channels centered at the nearest NR-ARFCN corresponding to [6385 MHz]. + +NOTE 3: Applicable to Pi/2-BPSK modulation when IE powerBoostPi2BPSK is set to 0. + +NOTE 4: Channel bandwidth sizes of 60MHz and 100MHz are not applicable for this network signalling. + +![Figure 6.1.1.2.3-2: A-MPR simulation results for PC5 VLP in Japan. A scatter plot showing Power backoff in dB (Y-axis, 1 to 9) versus ID (X-axis, 1 to 36). Data points are categorized by modulation: Pi/2 BPSK (blue), QPSK (orange), 16QAM (yellow), 64QAM (purple), and 256QAM (green). The plot shows that as the ID increases, the power backoff generally increases, with higher-order modulations (like 256QAM) showing higher power backoff values (up to 8 dB) compared to lower-order modulations (like Pi/2 BPSK, which stays around 6 dB).](1c427123350e0e73e2a109b79069314b_img.jpg) + +Figure 6.1.1.2.3-2: A-MPR simulation results for PC5 VLP in Japan. A scatter plot showing Power backoff in dB (Y-axis, 1 to 9) versus ID (X-axis, 1 to 36). Data points are categorized by modulation: Pi/2 BPSK (blue), QPSK (orange), 16QAM (yellow), 64QAM (purple), and 256QAM (green). The plot shows that as the ID increases, the power backoff generally increases, with higher-order modulations (like 256QAM) showing higher power backoff values (up to 8 dB) compared to lower-order modulations (like Pi/2 BPSK, which stays around 6 dB). + +Figure 6.1.1.2.3-2: A-MPR simulation results for PC5 VLP in Japan. + +Table 6.1.1.2.3-3: A-MPR for PC5 VLP in Japan + +| Pre-coding | Modulation | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | +|------------|------------------------|---------------------------------------------------------|--------------|-----------|--------------|-----------|--------------| +| | | 20 MHz | | 40 MHz | | 80 MHz | | +| | | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | +| DFT-s-ODFM | Pi/2 BPSK 2 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.5 | ≤ 6.5 | ≤ 7.0 | +| | QPSK | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.5 | ≤ 6.5 | ≤ 7.0 | +| | 16 QAM | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.5 | ≤ 6.5 | ≤ 7.0 | +| | 64 QAM | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.5 | ≤ 6.5 | ≤ 7.0 | +| | 256 QAM | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.5 | ≤ 6.5 | ≤ 7.0 | +| CP-OFDM | QPSK | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 8.0 | ≤ 6.5 | ≤ 8.5 | +| | 16 QAM | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 8.0 | ≤ 6.5 | ≤ 8.5 | +| | 64 QAM | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 8.0 | ≤ 6.5 | ≤ 8.5 | +| | 256 QAM | ≤ 7.0 | ≤ 6.0 | ≤ 6.0 | ≤ 8.0 | ≤ 7.0 | ≤ 8.5 | + +NOTE 1: Full allocation A-MPR applies when all RB's in a 20 MHz channel or all RB's in all sub-bands for wideband operation are fully allocated and all sub-bands are transmitted. Partial allocation A-MPR applies when one or more RB's in one or more sub-bands are not allocated but when all sub-bands within the channel are transmitted. When not all sub-bands within the channel are transmitted, the A-MPR associated with the channel bandwidth according to the bandwidth of the contiguously transmitted sub-bands and according to the allocation type applies. + +NOTE 2: Applicable to Pi/2-BPSK modulation when IE powerBoostPi2BPSK is set to 0. + +NOTE 3: Channel bandwidth sizes of 60MHz and 100MHz are not applicable for this network signalling. + +#### 6.1.1.2 A-MPR for a NS(s) for the full 6GHz NR unlicensed operation + +##### 6.1.1.2.1 Canada + +Table 6.1.1.2.1-1: Signal setup (LPI). + +| | ID | Waveform | BW | RB Setup | SCS | +|---------------------------|----|------------|----|----------|-----| +| Full Allocation Single CC | 1 | DFT-s-OFDM | 20 | 100RB3 | 15 | +| | 2 | DFT-s-OFDM | 20 | 100RB0 | 15 | +| | 3 | DFT-s-OFDM | 20 | 50RB0 | 30 | +| | 4 | DFT-s-OFDM | 40 | 216RB0 | 15 | +| | 5 | DFT-s-OFDM | 60 | 162RB0 | 30 | +| | 6 | DFT-s-OFDM | 80 | 216RB0 | 30 | +| | 7 | CP-OFDM | 20 | 106RB0 | 15 | +| | 8 | CP-OFDM | 20 | 51RB0 | 30 | +| | 9 | CP-OFDM | 40 | 216RB0 | 15 | + +| | | | | | | +|---------------------------------|----|------------|----|-------------------------|----| +| Interlaced Allocation Single CC | 10 | CP-OFDM | 60 | 162RB0 | 30 | +| | 11 | CP-OFDM | 80 | 217RB0 | 30 | +| | 12 | DFT-s-OFDM | 20 | 1RB0 every 10RBs (10x) | 15 | +| | 13 | DFT-s-OFDM | 40 | 1RB0 every 10RBs (20x) | 15 | +| | 14 | DFT-s-OFDM | 60 | 1RB0 every 10RBs (30x) | 30 | +| | 15 | DFT-s-OFDM | 80 | 1RB0 every 5RBs (40x) | 30 | +| | 16 | CP-OFDM | 20 | 1 RB0 every 10RBs (10x) | 15 | +| | 17 | CP-OFDM | 40 | 1RB0 every 10RBs (22x) | 15 | +| | 18 | CP-OFDM | 60 | 1RB0 every 10RBs (33x) | 30 | +| | 19 | CP-OFDM | 80 | 1RB0 every 5RBs (44x) | 30 | + +![Scatter plot showing Power backoff (dB) vs. Number of RBs (n) for various modulation schemes. The y-axis ranges from 0 to 7 dB, and the x-axis ranges from 1 to 19 RBs. Data points are shown for QPSK (blue circles), 16QAM (orange squares), 64QAM (yellow triangles), 256QAM (purple diamonds), and PI/2 BPSK (green crosses). The power backoff generally decreases as the number of RBs increases, with higher-order modulations showing lower power backoff values.](f85bf99d372e735d228361bf4d3cf7e6_img.jpg) + +Scatter plot showing Power backoff (dB) vs. Number of RBs (n) for various modulation schemes. The y-axis ranges from 0 to 7 dB, and the x-axis ranges from 1 to 19 RBs. Data points are shown for QPSK (blue circles), 16QAM (orange squares), 64QAM (yellow triangles), 256QAM (purple diamonds), and PI/2 BPSK (green crosses). The power backoff generally decreases as the number of RBs increases, with higher-order modulations showing lower power backoff values. + +Figure 6.1.1.2.1-1: A-MPR simulation results for PC5 LPI in Canada. + +Table 6.1.1.2.1-2: A-MPR for PC5 LPI in Canada + +| Pre-coding | Modulation | Channel bandwidth (Sub-band allocation) / RB Allocation | | +|------------|------------|---------------------------------------------------------|--------------| +| | | 20 MHz | | +| | | Full (dB) | Partial (dB) | +| DFT-s-ODFM | PI/2 BPSK | ≤ 3.0 | ≤ 5.5 | +| | QPSK | ≤ 3.0 | ≤ 5.5 | +| | 16 QAM | ≤ 3.0 | ≤ 5.5 | +| | 64 QAM | ≤ 3.5 | ≤ 5.5 | +| | 256 QAM | ≤ 5.0 | ≤ 5.5 | +| CP-OFDM | QPSK | ≤ 3.5 | ≤ 5.5 | +| | 16 QAM | ≤ 4.0 | ≤ 5.5 | +| | 64 QAM | ≤ 5.5 | ≤ 5.5 | +| | 256 QAM | ≤ 7.0 | ≤ 7.0 | + +Table 6.1.1.2.1-3: Signal setup (VLP). + +| ID | Modulation | Waveform | Allocation | +|----|------------|------------|---------------------| +| 1 | QPSK | DFT-s-OFDM | Full | +| 2 | QPSK | CP-OFDM | Full | +| 3 | QPSK | DFT-s-OFDM | Interlaced | +| 4 | QPSK | CP-OFDM | Interlaced | +| 5 | QPSK | DFT-s-OFDM | Wideband | +| 6 | QPSK | CP-OFDM | Wideband | +| 7 | QPSK | DFT-s-OFDM | Wideband Interlaced | +| 8 | QPSK | CP-OFDM | Wideband Interlaced | +| 9 | 16QAM | DFT-s-OFDM | Full | +| 10 | 16QAM | CP-OFDM | Full | +| 11 | 16QAM | DFT-s-OFDM | Interlaced | +| 12 | 16QAM | CP-OFDM | Interlaced | +| 13 | 16QAM | DFT-s-OFDM | Wideband | +| 14 | 16QAM | CP-OFDM | Wideband | +| 15 | 16QAM | DFT-s-OFDM | Wideband Interlaced | +| 16 | 16QAM | CP-OFDM | Wideband Interlaced | +| 17 | 64QAM | DFT-s-OFDM | Full | +| 18 | 64QAM | CP-OFDM | Full | +| 19 | 64QAM | DFT-s-OFDM | Interlaced | +| 20 | 64QAM | CP-OFDM | Interlaced | +| 21 | 64QAM | DFT-s-OFDM | Wideband | +| 22 | 64QAM | CP-OFDM | Wideband | +| 23 | 64QAM | DFT-s-OFDM | Wideband Interlaced | +| 24 | 64QAM | CP-OFDM | Wideband Interlaced | +| 25 | 256QAM | DFT-s-OFDM | Full | +| 26 | 256QAM | CP-OFDM | Full | +| 27 | 256QAM | DFT-s-OFDM | Interlaced | +| 28 | 256QAM | CP-OFDM | Interlaced | +| 29 | 256QAM | DFT-s-OFDM | Wideband | +| 30 | 256QAM | CP-OFDM | Wideband | +| 31 | 256QAM | DFT-s-OFDM | Wideband Interlaced | +| 32 | 256QAM | CP-OFDM | Wideband Interlaced | + +![Scatter plot showing Power backoff (Y-axis, 0 to 20) versus ID (X-axis, 1 to 32). The plot displays simulation results for PC5 VLP in Canada, categorized by modulation type: QPSK (blue diamonds), 16QAM (orange diamonds), 64QAM (yellow diamonds), and 256QAM (purple diamonds). The data points show a general trend of decreasing power backoff as the ID increases, with higher-order modulations generally requiring lower power backoff.](723827e0738d2743c3b3423760a5c48e_img.jpg) + +| ID | Modulation | Power Backoff (dB) | +|----|------------|--------------------| +| 1 | QPSK | 15.5 | +| 2 | QPSK | 14.5 | +| 3 | QPSK | 13.5 | +| 4 | QPSK | 12.5 | +| 5 | QPSK | 11.5 | +| 6 | QPSK | 10.5 | +| 7 | QPSK | 9.5 | +| 8 | QPSK | 8.5 | +| 9 | 16QAM | 15.5 | +| 10 | 16QAM | 14.5 | +| 11 | 16QAM | 13.5 | +| 12 | 16QAM | 12.5 | +| 13 | 16QAM | 11.5 | +| 14 | 16QAM | 10.5 | +| 15 | 16QAM | 9.5 | +| 16 | 16QAM | 8.5 | +| 17 | 64QAM | 15.5 | +| 18 | 64QAM | 14.5 | +| 19 | 64QAM | 13.5 | +| 20 | 64QAM | 12.5 | +| 21 | 64QAM | 11.5 | +| 22 | 64QAM | 10.5 | +| 23 | 64QAM | 9.5 | +| 24 | 64QAM | 8.5 | +| 25 | 256QAM | 15.5 | +| 26 | 256QAM | 14.5 | +| 27 | 256QAM | 13.5 | +| 28 | 256QAM | 12.5 | +| 29 | 256QAM | 11.5 | +| 30 | 256QAM | 10.5 | +| 31 | 256QAM | 9.5 | +| 32 | 256QAM | 8.5 | + +Scatter plot showing Power backoff (Y-axis, 0 to 20) versus ID (X-axis, 1 to 32). The plot displays simulation results for PC5 VLP in Canada, categorized by modulation type: QPSK (blue diamonds), 16QAM (orange diamonds), 64QAM (yellow diamonds), and 256QAM (purple diamonds). The data points show a general trend of decreasing power backoff as the ID increases, with higher-order modulations generally requiring lower power backoff. + +Figure 6.1.1.2.1-2: A-MPR simulation results for PC5 VLP in Canada. + +Table 6.1.1.2.1-4: A-MPR for PC5 VLP in Canada + +| Pre-coding | Modulation | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | +|------------|------------|---------------------------------------------------------|--------------|-----------|--------------|-----------|--------------|-----------|--------------| +| | | 20 MHz | | 40 MHz | | 60 MHz | | 80 MHz | | +| | | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | +| DFT-s-ODFM | QPSK | ≤ 16.0 | ≤ 18.5 | ≤ 12.5 | ≤ 15.5 | ≤ 11.0 | ≤ 14.0 | ≤ 9.5 | ≤ 12.5 | +| | 16 QAM | ≤ 16.0 | ≤ 18.5 | ≤ 12.5 | ≤ 15.5 | ≤ 11.0 | ≤ 14.0 | ≤ 9.5 | ≤ 12.5 | +| | 64 QAM | ≤ 16.0 | ≤ 18.5 | ≤ 12.5 | ≤ 15.5 | ≤ 11.0 | ≤ 14.0 | ≤ 9.5 | ≤ 12.5 | +| | 256 QAM | ≤ 16.0 | ≤ 18.5 | ≤ 12.5 | ≤ 15.5 | ≤ 11.0 | ≤ 14.0 | ≤ 9.5 | ≤ 12.5 | +| CP-OFDM | QPSK | ≤ 16.0 | ≤ 18.5 | ≤ 12.5 | ≤ 15.5 | ≤ 11.0 | ≤ 14.0 | ≤ 9.5 | ≤ 12.5 | +| | 16 QAM | ≤ 16.0 | ≤ 18.5 | ≤ 12.5 | ≤ 15.5 | ≤ 11.0 | ≤ 14.0 | ≤ 9.5 | ≤ 12.5 | +| | 64 QAM | ≤ 16.0 | ≤ 18.5 | ≤ 12.5 | ≤ 15.5 | ≤ 11.0 | ≤ 14.0 | ≤ 9.5 | ≤ 12.5 | +| | 256 QAM | ≤ 16.0 | ≤ 18.5 | ≤ 12.5 | ≤ 15.5 | ≤ 11.0 | ≤ 14.0 | ≤ 9.5 | ≤ 12.5 | + +NOTE 1: Full allocation A-MPR applies when all RB's in a 20 MHz channel or all RB's in all sub-bands for wideband operation are fully allocated and all sub-bands are transmitted. Partial allocation A-MPR applies when one or more RB's in one or more sub-bands are not allocated but when all sub-bands within the channel are transmitted. When not all sub-bands within the channel are transmitted, the A-MPR associated with the channel bandwidth according to the bandwidth of the contiguously transmitted sub-bands and according to the allocation type applies. + +##### 6.1.1.2.2 South Korea + +Table 6.1.1.2.2-1: Signal setup (LPI and VLP). + +| | ID | Waveform | BW | RB Setup | SCS | +|---------------------------------|----|------------|----|-------------------------|-----| +| Full Allocation Single CC | 1 | DFT-s-OFDM | 20 | 100RB3 | 15 | +| | 2 | DFT-s-OFDM | 20 | 100RB0 | 15 | +| | 3 | DFT-s-OFDM | 20 | 50RB0 | 30 | +| | 4 | DFT-s-OFDM | 40 | 216RB0 | 15 | +| | 5 | DFT-s-OFDM | 60 | 162RB0 | 30 | +| | 6 | DFT-s-OFDM | 80 | 216RB0 | 30 | +| | 7 | CP-OFDM | 20 | 106RB0 | 15 | +| | 8 | CP-OFDM | 20 | 51RB0 | 30 | +| | 9 | CP-OFDM | 40 | 216RB0 | 15 | +| | 10 | CP-OFDM | 60 | 162RB0 | 30 | +| | 11 | CP-OFDM | 80 | 217RB0 | 30 | +| Interlaced Allocation Single CC | 12 | DFT-s-OFDM | 20 | 1RB0 every 10RBs (10x) | 15 | +| | 13 | DFT-s-OFDM | 40 | 1RB0 every 10RBs (20x) | 15 | +| | 14 | DFT-s-OFDM | 60 | 1RB0 every 10RBs (30x) | 30 | +| | 15 | DFT-s-OFDM | 80 | 1RB0 every 5RBs (40x) | 30 | +| | 16 | CP-OFDM | 20 | 1 RB0 every 10RBs (10x) | 15 | +| | 17 | CP-OFDM | 40 | 1RB0 every 10RBs (22x) | 15 | +| | 18 | CP-OFDM | 60 | 1RB0 every 10RBs (33x) | 30 | +| | 19 | CP-OFDM | 80 | 1RB0 every 5RBs (44x) | 30 | + +![Scatter plot showing Power backoff (Y-axis, 0 to 9) versus ID (X-axis, 1 to 19) for various modulation schemes. The plot shows that power backoff generally decreases as ID increases, with some outliers. The legend indicates: QPSK (blue circle), 16QAM (orange circle), 64QAM (green circle), 256QAM (purple circle), and Pi/2 BPSK (yellow circle).](fbfbbc91a80a21fc8d0ff7ba9e5865e3_img.jpg) + +| ID | Modulation | Power backoff (dB) | +|----|------------|--------------------| +| 1 | Pi/2 BPSK | 5.8 | +| 2 | Pi/2 BPSK | 5.8 | +| 3 | Pi/2 BPSK | 5.8 | +| 4 | QPSK | 3.5 | +| 4 | 16QAM | 3.8 | +| 4 | 64QAM | 2.5 | +| 4 | 256QAM | 3.8 | +| 5 | QPSK | 3.2 | +| 5 | 16QAM | 3.5 | +| 5 | 64QAM | 2.2 | +| 5 | 256QAM | 3.5 | +| 6 | QPSK | 2.8 | +| 6 | 16QAM | 3.2 | +| 6 | 64QAM | 1.8 | +| 6 | 256QAM | 3.2 | +| 7 | QPSK | 5.5 | +| 7 | 16QAM | 5.5 | +| 7 | 64QAM | 5.5 | +| 7 | 256QAM | 5.5 | +| 8 | QPSK | 5.5 | +| 8 | 16QAM | 5.5 | +| 8 | 64QAM | 5.5 | +| 8 | 256QAM | 5.5 | +| 9 | QPSK | 4.8 | +| 9 | 16QAM | 4.8 | +| 9 | 64QAM | 4.8 | +| 9 | 256QAM | 4.8 | +| 10 | QPSK | 4.5 | +| 10 | 16QAM | 4.5 | +| 10 | 64QAM | 4.5 | +| 10 | 256QAM | 4.5 | +| 11 | QPSK | 4.2 | +| 11 | 16QAM | 4.2 | +| 11 | 64QAM | 4.2 | +| 11 | 256QAM | 4.2 | +| 12 | QPSK | 8.2 | +| 12 | 16QAM | 8.2 | +| 12 | 64QAM | 8.2 | +| 12 | 256QAM | 8.2 | +| 13 | QPSK | 5.2 | +| 13 | 16QAM | 5.2 | +| 13 | 64QAM | 5.2 | +| 13 | 256QAM | 5.2 | +| 14 | QPSK | 4.8 | +| 14 | 16QAM | 4.8 | +| 14 | 64QAM | 4.8 | +| 14 | 256QAM | 4.8 | +| 15 | QPSK | 4.2 | +| 15 | 16QAM | 4.2 | +| 15 | 64QAM | 4.2 | +| 15 | 256QAM | 4.2 | +| 16 | QPSK | 5.2 | +| 16 | 16QAM | 5.2 | +| 16 | 64QAM | 5.2 | +| 16 | 256QAM | 5.2 | +| 17 | QPSK | 5.2 | +| 17 | 16QAM | 5.2 | +| 17 | 64QAM | 5.2 | +| 17 | 256QAM | 5.2 | +| 18 | QPSK | 5.2 | +| 18 | 16QAM | 5.2 | +| 18 | 64QAM | 5.2 | +| 18 | 256QAM | 5.2 | +| 19 | QPSK | 5.2 | +| 19 | 16QAM | 5.2 | +| 19 | 64QAM | 5.2 | +| 19 | 256QAM | 5.2 | + +Scatter plot showing Power backoff (Y-axis, 0 to 9) versus ID (X-axis, 1 to 19) for various modulation schemes. The plot shows that power backoff generally decreases as ID increases, with some outliers. The legend indicates: QPSK (blue circle), 16QAM (orange circle), 64QAM (green circle), 256QAM (purple circle), and Pi/2 BPSK (yellow circle). + +Figure 6.1.1.2.2-1: A-MPR simulation results for PC5 LPI in South Korea. + +Table 6.1.1.2.2-2: A-MPR for PC5 LPI in South Korea + +| Pre-coding | Modulation | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | +|------------|------------|---------------------------------------------------------|--------------|-----------|--------------|-----------|--------------|-----------|--------------| +| | | 20 MHz | | 40 MHz | | 60 MHz | | 80 MHz | | +| | | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | +| DFT-s-ODFM | QPSK | ≤ 6.0 | ≤ 8.5 | ≤ 4.0 | ≤ 5.5 | ≤ 3.5 | ≤ 4.5 | ≤ 3.0 | ≤ 4.5 | +| | 16 QAM | ≤ 6.0 | ≤ 8.5 | ≤ 4.0 | ≤ 5.5 | ≤ 4.0 | ≤ 5.0 | ≤ 3.5 | ≤ 5.0 | +| | 64 QAM | ≤ 6.0 | ≤ 8.5 | ≤ 4.0 | ≤ 5.5 | ≤ 4.0 | ≤ 5.0 | ≤ 3.5 | ≤ 5.0 | +| | 256 QAM | ≤ 6.0 | ≤ 8.5 | ≤ 5.0 | ≤ 5.5 | ≤ 5.0 | ≤ 5.5 | ≤ 5.0 | ≤ 5.5 | +| CP-OFDM | QPSK | ≤ 6.0 | ≤ 8.5 | ≤ 5.5 | ≤ 5.5 | ≤ 5.0 | ≤ 5.5 | ≤ 4.5 | ≤ 5.5 | +| | 16 QAM | ≤ 6.0 | ≤ 8.5 | ≤ 5.5 | ≤ 5.5 | ≤ 5.0 | ≤ 5.5 | ≤ 4.5 | ≤ 5.5 | +| | 64 QAM | ≤ 6.0 | ≤ 8.5 | ≤ 5.5 | ≤ 5.5 | ≤ 5.5 | ≤ 5.5 | ≤ 5.5 | ≤ 5.5 | +| | 256 QAM | ≤ 6.0 | ≤ 8.5 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | + +Table 6.1.1.2.2-3 contains A-MPR values for the 5945-6425MHz frequency range based on South Korea regulatory requirements. + +Table 6.1.1.2.2-3: A-MPR for PC5 VLP in South Korea (5945-6425MHz). + +| Pre-coding | Modulation | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | +|------------|------------|---------------------------------------------------------|--------------|-----------|--------------|-----------|--------------|-----------|--------------| +| | | 20 MHz | | 40 MHz | | 60 MHz | | 80 MHz | | +| | | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | +| DFT-s-ODFM | QPSK | ≤ 7.5 | ≤ 10.0 | ≤ 6.5 | ≤ 6.5 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | +| | 16 QAM | ≤ 7.5 | ≤ 10.5 | ≤ 6.5 | ≤ 6.5 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | +| | 64 QAM | ≤ 7.5 | ≤ 10.5 | ≤ 6.5 | ≤ 6.5 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | +| | 256 QAM | ≤ 7.5 | ≤ 10.5 | ≤ 6.5 | ≤ 6.5 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | +| CP-OFDM | QPSK | ≤ 7.5 | ≤ 10.0 | ≤ 6.5 | ≤ 6.5 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | +| | 16 QAM | ≤ 7.5 | ≤ 10.5 | ≤ 6.5 | ≤ 6.5 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | +| | 64 QAM | ≤ 7.5 | ≤ 10.5 | ≤ 6.5 | ≤ 6.5 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | ≤ 6.0 | +| | 256 QAM | ≤ 7.5 | ≤ 10.5 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | + +NOTE 1: Full allocation A-MPR applies when all RB's in a 20 MHz channel or all RB's in all sub-bands for wideband operation are fully allocated and all sub-bands are transmitted. Partial allocation A-MPR applies when one or more RB's in one or more sub-bands are not allocated but when all sub-bands within the channel are transmitted. When not all sub-bands within the channel are transmitted, the A-MPR associated with the channel bandwidth according to the bandwidth of the contiguously transmitted sub-bands and according to the allocation type applies. + +Table 6.1.1.2.2-4 contains A-MPR values for the 5925-5945MHz frequency range based on South Korea regulatory requirements. + +Table 6.1.1.2.2-4: A-MPR for PC5 VLP in South Korea (5925-5945MHz). + +| Pre-coding | Modulation | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | +|------------|------------|---------------------------------------------------------|--------------|-----------|--------------|-----------|--------------|-----------|--------------| +| | | 20 MHz | | 40 MHz | | 60 MHz | | 80 MHz | | +| | | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | + +| | | | | | | | | | | +|------------|---------|-------|--------|-------|--------|-------|-------|-------|-------| +| DFT-s-ODFM | QPSK | ≤ 8.5 | ≤ 11.5 | ≤ 7.0 | ≤ 9.0 | ≤ 6.5 | ≤ 7.5 | ≤ 6.5 | ≤ 7.0 | +| | 16 QAM | ≤ 8.5 | ≤ 11.5 | ≤ 7.0 | ≤ 9.0 | ≤ 6.5 | ≤ 7.5 | ≤ 6.5 | ≤ 7.0 | +| | 64 QAM | ≤ 8.5 | ≤ 11.5 | ≤ 7.0 | ≤ 9.0 | ≤ 6.5 | ≤ 7.5 | ≤ 6.5 | ≤ 7.0 | +| | 256 QAM | ≤ 8.5 | ≤ 11.5 | ≤ 7.0 | ≤ 9.0 | ≤ 6.5 | ≤ 7.5 | ≤ 6.5 | ≤ 7.0 | +| CP-OFDM | QPSK | ≤ 11 | ≤ 12.5 | ≤ 9.0 | ≤ 11.0 | ≤ 7.5 | ≤ 9.5 | ≤ 7.0 | ≤ 8.5 | +| | 16 QAM | ≤ 11 | ≤ 12.5 | ≤ 9.0 | ≤ 11.0 | ≤ 7.5 | ≤ 9.5 | ≤ 7.0 | ≤ 8.5 | +| | 64 QAM | ≤ 11 | ≤ 12.5 | ≤ 9.0 | ≤ 11.0 | ≤ 7.5 | ≤ 9.5 | ≤ 7.0 | ≤ 8.5 | +| | 256 QAM | ≤ 11 | ≤ 12.5 | ≤ 9.0 | ≤ 11.0 | ≤ 7.5 | ≤ 9.5 | ≤ 7.0 | ≤ 8.5 | + +NOTE 1: Full allocation A-MPR applies when all RB's in a 20 MHz channel or all RB's in all sub-bands for wideband operation are fully allocated and all sub-bands are transmitted. Partial allocation A-MPR applies when one or more RB's in one or more sub-bands are not allocated but when all sub-bands within the channel are transmitted. When not all sub-bands within the channel are transmitted, the A-MPR associated with the channel bandwidth according to the bandwidth of the contiguously transmitted sub-bands and according to the allocation type applies. + +NOTE 2: This table is applicable when the channel raster point is extended so that first 20MHz, i.e. 5925-5945MHz, can be used by NR-U. + +Table 6.1.1.2.2-5 provides the A-MPR values for PC3 LPI with 1Tx based on South Korea regulatory requirements. + +**Table 6.1.1.2.2-5: A-MPR for PC3 LPI with 1Tx in South Korea** + +| Pre-coding | Modulation | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | | | +|------------|------------------------|---------------------------------------------------------|--------------|-----------|--------------|-----------|--------------|-----------|--------------|-----------|--------------| +| | | 20 MHz | | 40 MHz | | 60 MHz | | 80 MHz | | 100 MHz | | +| | | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | +| DFT-s-ODFM | Pi/2 BPSK 2 | ≤ 9.5 | ≤ 11.5 | ≤ 6.0 | ≤ 9.0 | ≤ 4.5 | ≤ 7.0 | ≤ 3.0 | ≤ 6.0 | ≤ 2.5 | ≤ 5.0 | +| | QPSK | ≤ 9.5 | ≤ 11.5 | ≤ 6.0 | ≤ 9.0 | ≤ 4.5 | ≤ 7.0 | ≤ 3.0 | ≤ 6.0 | ≤ 2.5 | ≤ 5.0 | +| | 16 QAM | ≤ 9.5 | ≤ 11.5 | ≤ 6.0 | ≤ 9.0 | ≤ 4.5 | ≤ 7.0 | ≤ 3.0 | ≤ 6.0 | ≤ 2.5 | ≤ 5.0 | +| | 64 QAM | ≤ 9.5 | ≤ 11.5 | ≤ 6.0 | ≤ 9.0 | ≤ 4.5 | ≤ 7.0 | ≤ 3.0 | ≤ 6.0 | ≤ 2.5 | ≤ 5.0 | +| | 256 QAM | ≤ 9.5 | ≤ 11.5 | ≤ 6.0 | ≤ 9.0 | ≤ 4.5 | ≤ 7.0 | ≤ 4.5 | ≤ 6.0 | ≤ 4.5 | ≤ 5.0 | +| CP-OFDM | QPSK | ≤ 9.5 | ≤ 11.5 | ≤ 6.0 | ≤ 9.0 | ≤ 4.5 | ≤ 7.0 | ≤ 4.0 | ≤ 6.0 | ≤ 3.5 | ≤ 5.0 | +| | 16 QAM | ≤ 9.5 | ≤ 11.5 | ≤ 6.0 | ≤ 9.0 | ≤ 4.5 | ≤ 7.0 | ≤ 4.0 | ≤ 6.0 | ≤ 3.5 | ≤ 5.0 | +| | 64 QAM | ≤ 9.5 | ≤ 11.5 | ≤ 6.0 | ≤ 9.0 | ≤ 4.5 | ≤ 7.0 | ≤ 4.0 | ≤ 6.0 | ≤ 4.0 | ≤ 5.0 | +| | 256 QAM | ≤ 9.5 | ≤ 11.5 | ≤ 6.0 | ≤ 9.0 | ≤ 4.5 | ≤ 7.0 | ≤ 5.5 | ≤ 6.5 | ≤ 5.5 | ≤ 6.0 | + +NOTE 1: Full allocation A-MPR applies when all RB's in a 20 MHz channel or all RB's in all sub-bands for wideband operation are fully allocated and all sub-bands are transmitted. Partial allocation A-MPR applies when one or more RB's in one or more sub-bands are not allocated but when all sub-bands within the channel are transmitted. When not all sub-bands within the channel are transmitted, the A-MPR associated with the channel bandwidth according to the bandwidth of the contiguously transmitted sub-bands and according to the allocation type applies. + +NOTE 2: Applicable to Pi/2-BPSK modulation when IE powerBoostPi2BPSK is set to 0. + +Table 6.1.1.2.2-6 provides the A-MPR values for PC3 LPI with 2Tx based on South Korea regulatory requirements. + +Table 6.1.1.2.2-6: A-MPR for PC3 LPI with 2Tx in South Korea + +| Pre-coding | Modulation | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | | | +|------------|------------------------|---------------------------------------------------------|--------------|-----------|--------------|-----------|--------------|-----------|--------------|-----------|--------------| +| | | 20 MHz | | 40 MHz | | 60 MHz | | 80 MHz | | 100 MHz | | +| | | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | +| DFT-s-OFDM | Pi/2 BPSK 2 | ≤ 9.5 | ≤ 11.5 | ≤ 6.0 | ≤ 9.0 | ≤ 4.5 | ≤ 7.0 | ≤ 3.0 | ≤ 6.0 | ≤ 3.0 | ≤ 5.5 | +| | QPSK | ≤ 9.5 | ≤ 11.5 | ≤ 6.0 | ≤ 9.0 | ≤ 4.5 | ≤ 7.0 | ≤ 3.0 | ≤ 6.0 | ≤ 3.0 | ≤ 5.5 | +| | 16 QAM | ≤ 9.5 | ≤ 11.5 | ≤ 6.0 | ≤ 9.0 | ≤ 4.5 | ≤ 7.0 | ≤ 3.0 | ≤ 6.0 | ≤ 3.0 | ≤ 5.5 | +| | 64 QAM | ≤ 9.5 | ≤ 11.5 | ≤ 6.0 | ≤ 9.0 | ≤ 4.5 | ≤ 7.0 | ≤ 3.0 | ≤ 6.0 | ≤ 3.0 | ≤ 5.5 | +| | 256 QAM | ≤ 9.5 | ≤ 11.5 | ≤ 6.0 | ≤ 9.0 | ≤ 4.5 | ≤ 7.0 | ≤ 4.5 | ≤ 6.0 | ≤ 4.5 | ≤ 5.5 | +| CP-OFDM | QPSK | ≤ 9.5 | ≤ 11.5 | ≤ 6.0 | ≤ 9.0 | ≤ 5.0 | ≤ 7.0 | ≤ 4.5 | ≤ 6.0 | ≤ 4.5 | ≤ 5.5 | +| | 16 QAM | ≤ 9.5 | ≤ 11.5 | ≤ 6.0 | ≤ 9.0 | ≤ 5.0 | ≤ 7.0 | ≤ 4.5 | ≤ 6.0 | ≤ 4.5 | ≤ 5.5 | +| | 64 QAM | ≤ 9.5 | ≤ 11.5 | ≤ 6.0 | ≤ 9.0 | ≤ 5.0 | ≤ 7.0 | ≤ 4.5 | ≤ 6.0 | ≤ 4.5 | ≤ 5.5 | +| | 256 QAM | ≤ 9.5 | ≤ 11.5 | ≤ 6.0 | ≤ 9.0 | ≤ 5.0 | ≤ 7.0 | ≤ 5.5 | ≤ 6.5 | ≤ 5.5 | ≤ 6.0 | + +NOTE 1: Full allocation A-MPR applies when all RB's in a 20 MHz channel or all RB's in all sub-bands for wideband operation are fully allocated and all sub-bands are transmitted. Partial allocation A-MPR applies when one or more RB's in one or more sub-bands are not allocated but when all sub-bands within the channel are transmitted. When not all sub-bands within the channel are transmitted, the A-MPR associated with the channel bandwidth according to the bandwidth of the contiguously transmitted sub-bands and according to the allocation type applies + +NOTE 2: Applicable to Pi/2-BPSK modulation when IE powerBoostPi2BPSK is set to 0. + +##### 6.1.1.2.3 Peru and Chile + +Table 6.1.1.2.3-1: Signal setup (LPI). + +| | ID | Waveform | BW | RB Setup | SCS | +|---------------------------------|----|------------|----|-------------------------|-----| +| Full Allocation Single CC | 1 | DFT-s-OFDM | 20 | 100RB3 | 15 | +| | 2 | DFT-s-OFDM | 20 | 100RB0 | 15 | +| | 3 | DFT-s-OFDM | 20 | 50RB0 | 30 | +| | 4 | DFT-s-OFDM | 40 | 216RB0 | 15 | +| | 5 | DFT-s-OFDM | 60 | 162RB0 | 30 | +| | 6 | DFT-s-OFDM | 80 | 216RB0 | 30 | +| | 7 | CP-OFDM | 20 | 106RB0 | 15 | +| | 8 | CP-OFDM | 20 | 51RB0 | 30 | +| | 9 | CP-OFDM | 40 | 216RB0 | 15 | +| | 10 | CP-OFDM | 60 | 162RB0 | 30 | +| | 11 | CP-OFDM | 80 | 217RB0 | 30 | +| Interlaced Allocation Single CC | 12 | DFT-s-OFDM | 20 | 1RB0 every 10RBs (10x) | 15 | +| | 13 | DFT-s-OFDM | 40 | 1RB0 every 10RBs (20x) | 15 | +| | 14 | DFT-s-OFDM | 60 | 1RB0 every 10RBs (30x) | 30 | +| | 15 | DFT-s-OFDM | 80 | 1RB0 every 5RBs (40x) | 30 | +| | 16 | CP-OFDM | 20 | 1 RB0 every 10RBs (10x) | 15 | +| | 17 | CP-OFDM | 40 | 1RB0 every 10RBs (22x) | 15 | +| | 18 | CP-OFDM | 60 | 1RB0 every 10RBs (33x) | 30 | +| | 19 | CP-OFDM | 80 | 1RB0 every 5RBs (44x) | 30 | + +![Figure 6.1.1.2.3-1: A-MPR simulation results for PC5 LPI in Peru and Chile. This is a scatter plot showing Power backoff (Y-axis, 0 to 12) versus ID (X-axis, 1 to 19). Data points are plotted for four modulation schemes: QPSK (blue circles), 16QAM (orange circles), 64QAM (yellow circles), and 256QAM (purple circles). The power backoff values range from approximately 2.5 dB to 11.5 dB across the different IDs and modulations.](c17eaf807acd5faec68da19dd16929be_img.jpg) + +Figure 6.1.1.2.3-1: A-MPR simulation results for PC5 LPI in Peru and Chile. This is a scatter plot showing Power backoff (Y-axis, 0 to 12) versus ID (X-axis, 1 to 19). Data points are plotted for four modulation schemes: QPSK (blue circles), 16QAM (orange circles), 64QAM (yellow circles), and 256QAM (purple circles). The power backoff values range from approximately 2.5 dB to 11.5 dB across the different IDs and modulations. + +Figure 6.1.1.2.3-1: A-MPR simulation results for PC5 LPI in Peru and Chile. + +Table 6.1.1.2.3-2: A-MPR for PC5 LPI in Peru and Chile + +| Pre-coding | Modulation | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | +|------------|------------|---------------------------------------------------------|--------------|-----------|--------------|-----------|--------------|-----------|--------------| +| | | 20 MHz | | 40 MHz | | 60 MHz | | 80 MHz | | +| | | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | +| DFT-s-ODFM | QPSK | ≤ 9.0 | ≤ 12.0 | ≤ 6.0 | ≤ 8.5 | ≤ 4.5 | ≤ 6.5 | ≤ 3.0 | ≤ 5.5 | +| | 16 QAM | ≤ 9.0 | ≤ 12.0 | ≤ 6.0 | ≤ 8.5 | ≤ 4.5 | ≤ 6.5 | ≤ 3.0 | ≤ 5.5 | +| | 64 QAM | ≤ 9.0 | ≤ 12.0 | ≤ 6.0 | ≤ 8.5 | ≤ 4.5 | ≤ 6.5 | ≤ 3.0 | ≤ 5.5 | +| | 256 QAM | ≤ 9.0 | ≤ 12.0 | ≤ 6.0 | ≤ 8.5 | ≤ 5.0 | ≤ 6.5 | ≤ 5.0 | ≤ 5.5 | +| CP-OFDM | QPSK | ≤ 9.0 | ≤ 12.0 | ≤ 6.0 | ≤ 8.5 | ≤ 4.5 | ≤ 6.5 | ≤ 4.0 | ≤ 5.5 | +| | 16 QAM | ≤ 9.0 | ≤ 12.0 | ≤ 6.0 | ≤ 8.5 | ≤ 4.5 | ≤ 6.5 | ≤ 4.0 | ≤ 5.5 | +| | 64 QAM | ≤ 9.0 | ≤ 12.0 | ≤ 6.0 | ≤ 8.5 | ≤ 5.5 | ≤ 6.5 | ≤ 5.5 | ≤ 5.5 | +| | 256 QAM | ≤ 9.0 | ≤ 12.0 | ≤ 7.0 | ≤ 8.5 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | ≤ 7.0 | + +The A-MPR results for PC5 LPI in Peru and Chile are mostly identical to the A-MPR results defined by NS\_53 (LPI in US). In some cases, A-MPR results are 0.5-1dB relaxed comparing to NS\_53. Thus, accounting for the marginal difference between these A-MPR values and NS\_53, the latter can be re-used to support Peru and Chile. + +##### 6.1.1.2.4 Brazil + +Table 6.1.1.2.4-1: Signal setup (VLP). + +| ID | Modulation | Waveform | Allocation | +|----|------------|------------|---------------------| +| 1 | QPSK | DFT-s-OFDM | Full | +| 2 | QPSK | CP-OFDM | Full | +| 3 | QPSK | DFT-s-OFDM | Interlaced | +| 4 | QPSK | CP-OFDM | Interlaced | +| 5 | QPSK | DFT-s-OFDM | Wideband | +| 6 | QPSK | CP-OFDM | Wideband | +| 7 | QPSK | DFT-s-OFDM | Wideband Interlaced | +| 8 | QPSK | CP-OFDM | Wideband Interlaced | +| 9 | 16QAM | DFT-s-OFDM | Full | +| 10 | 16QAM | CP-OFDM | Full | +| 11 | 16QAM | DFT-s-OFDM | Interlaced | +| 12 | 16QAM | CP-OFDM | Interlaced | +| 13 | 16QAM | DFT-s-OFDM | Wideband | +| 14 | 16QAM | CP-OFDM | Wideband | +| 15 | 16QAM | DFT-s-OFDM | Wideband Interlaced | +| 16 | 16QAM | CP-OFDM | Wideband Interlaced | +| 17 | 64QAM | DFT-s-OFDM | Full | +| 18 | 64QAM | CP-OFDM | Full | +| 19 | 64QAM | DFT-s-OFDM | Interlaced | +| 20 | 64QAM | CP-OFDM | Interlaced | +| 21 | 64QAM | DFT-s-OFDM | Wideband | +| 22 | 64QAM | CP-OFDM | Wideband | +| 23 | 64QAM | DFT-s-OFDM | Wideband Interlaced | +| 24 | 64QAM | CP-OFDM | Wideband Interlaced | +| 25 | 256QAM | DFT-s-OFDM | Full | +| 26 | 256QAM | CP-OFDM | Full | +| 27 | 256QAM | DFT-s-OFDM | Interlaced | +| 28 | 256QAM | CP-OFDM | Interlaced | +| 29 | 256QAM | DFT-s-OFDM | Wideband | +| 30 | 256QAM | CP-OFDM | Wideband | +| 31 | 256QAM | DFT-s-OFDM | Wideband Interlaced | +| 32 | 256QAM | CP-OFDM | Wideband Interlaced | + +![Scatter plot showing Power backoff (Y-axis, 0 to 16) versus ID (X-axis, 0 to 32). The plot displays simulation results for PC5 LPI in Brazil. Data points are categorized by Modulation: QPSK (blue circles), 16QAM (orange circles), 64QAM (yellow circles), and 256QAM (purple circles). The power backoff generally increases with ID and is higher for higher-order modulations.](939b79420df0cf962959ccef56f3371f_img.jpg) + +| ID | Modulation | Power Backoff (dB) | +|----|------------|--------------------| +| 1 | QPSK | 12.5 | +| 2 | QPSK | 12.5 | +| 3 | QPSK | 15.0 | +| 4 | QPSK | 15.0 | +| 5 | QPSK | 12.5 | +| 6 | QPSK | 12.5 | +| 7 | QPSK | 15.0 | +| 8 | QPSK | 14.5 | +| 9 | 16QAM | 12.5 | +| 10 | 16QAM | 12.5 | +| 11 | 16QAM | 15.0 | +| 12 | 16QAM | 15.0 | +| 13 | 16QAM | 12.5 | +| 14 | 16QAM | 12.5 | +| 15 | 16QAM | 15.0 | +| 16 | 16QAM | 14.5 | +| 17 | 64QAM | 15.0 | +| 18 | 64QAM | 15.0 | +| 19 | 64QAM | 15.0 | +| 20 | 64QAM | 15.0 | +| 21 | 64QAM | 12.5 | +| 22 | 64QAM | 12.5 | +| 23 | 64QAM | 15.0 | +| 24 | 64QAM | 14.5 | +| 25 | 256QAM | 15.0 | +| 26 | 256QAM | 15.0 | +| 27 | 256QAM | 15.0 | +| 28 | 256QAM | 15.0 | +| 29 | 256QAM | 15.0 | +| 30 | 256QAM | 15.0 | +| 31 | 256QAM | 15.0 | +| 32 | 256QAM | 15.0 | + +Scatter plot showing Power backoff (Y-axis, 0 to 16) versus ID (X-axis, 0 to 32). The plot displays simulation results for PC5 LPI in Brazil. Data points are categorized by Modulation: QPSK (blue circles), 16QAM (orange circles), 64QAM (yellow circles), and 256QAM (purple circles). The power backoff generally increases with ID and is higher for higher-order modulations. + +Figure 6.1.1.2.4-1: A-MPR simulation results for PC5 LPI in Brazil. + +Table 6.1.1.2.4-2: A-MPR for PC5 LPI in Brazil + +| Pre-coding | Modulation | Channel bandwidth (Sub-band allocation) / RB Allocation | | | | | | | | +|------------|------------|---------------------------------------------------------|--------------|-----------|--------------|-----------|--------------|-----------|--------------| +| | | 20 MHz | | 40 MHz | | 60 MHz | | 80 MHz | | +| | | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | Full (dB) | Partial (dB) | +| DFT-s-ODFM | QPSK | ≤ 13.0 | ≤ 15.5 | ≤ 9.5 | ≤ 12.5 | ≤ 8.0 | ≤ 11 | ≤ 6.5 | ≤ 9.5 | +| | 16 QAM | ≤ 13.0 | ≤ 15.5 | ≤ 9.5 | ≤ 12.5 | ≤ 8.0 | ≤ 11 | ≤ 6.5 | ≤ 9.5 | +| | 64 QAM | ≤ 13.0 | ≤ 15.5 | ≤ 9.5 | ≤ 12.5 | ≤ 8.0 | ≤ 11 | ≤ 6.5 | ≤ 9.5 | +| | 256 QAM | ≤ 13.0 | ≤ 15.5 | ≤ 9.5 | ≤ 12.5 | ≤ 8.0 | ≤ 11 | ≤ 6.5 | ≤ 9.5 | +| CP-OFDM | QPSK | ≤ 13.0 | ≤ 15.5 | ≤ 9.5 | ≤ 12.5 | ≤ 8.0 | ≤ 11 | ≤ 6.5 | ≤ 9.5 | +| | 16 QAM | ≤ 13.0 | ≤ 15.5 | ≤ 9.5 | ≤ 12.5 | ≤ 8.0 | ≤ 11 | ≤ 6.5 | ≤ 9.5 | +| | 64 QAM | ≤ 13.0 | ≤ 15.5 | ≤ 9.5 | ≤ 12.5 | ≤ 8.0 | ≤ 11 | ≤ 6.5 | ≤ 9.5 | +| | 256 QAM | ≤ 13.0 | ≤ 15.5 | ≤ 9.5 | ≤ 12.5 | ≤ 8.0 | ≤ 11 | ≤ 6.5 | ≤ 9.5 | + +NOTE 1: Full allocation A-MPR applies when all RB's in a 20 MHz channel or all RB's in all sub-bands for wideband operation are fully allocated and all sub-bands are transmitted. Partial allocation A-MPR applies when one or more RB's in one or more sub-bands are not allocated but when all sub-bands within the channel are transmitted. When not all sub-bands within the channel are transmitted, the A-MPR associated with the channel bandwidth according to the bandwidth of the contiguously transmitted sub-bands and according to the allocation type applies. + +### 6.1.2 Receiver characteristics + +## 6.2 BS specific + +### 6.2.1 Transmitter characteristics + +For operation in full unlicensed band 5925-7125MHz, existing BS transmitter requirements for n96 can be reused. + +### 6.2.2 Receiver characteristics + +For operation in full unlicensed band 5925-7125MHz, existing BS receiver requirements for n96 can be reused. + +# --- 7 RRM + +## 7.1 Frequency bands grouping + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|---------------|------------|----|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2021-01 | RAN4-98e | R4-2101927 | | | | TR Skeleton | 0.0.0 | +| 2021-02 | RAN4-98e | R4-2101928 | | | | draft TR after RAN4-98e | 0.1.0 | +| 2021-04 | RAN4-98bis-e | R4-2107196 | | | | draft TR after RAN4-98bis-e
Inclusion of:
R4-2105384 - TP to TR 38.849 on NR-ARFCN and GSCN points | 0.2.0 | +| 2021-05 | RAN4-99e | R4-2110691 | | | | draft TR after RAN4-99-e
Inclusion of:
R4-2107789 - TP to TR 38.849 on MPR values for LPI deployments
Removal of automatic bullets | 0.3.0 | +| 2021-08 | RAN4-100e | R4-2113692 | | | | draft TR after RAN4-100-e
Inclusion of:
R4-2114883 - TP to TR 38.849 on A-MPR for VLP | 0.4.0 | +| 2021-11 | RAN4-101e | R4-218617 | | | | Update of TR to also include WI NR_6GHz_unlic_full as per RAN agreement. | 0.4.1 | +| 2021-11 | RAN4-101e | R4-218616 | | | | draft TR after RAN4-101-e
Inclusion of:
R4-2117953 - Text proposal for TR 38.849 with A-MPR values | 0.5.0 | +| 2022-01 | RAN4-101bis-e | R4-2201080 | | | | draft TR after RAN4-101bis-e
Inclusion of:
R4-2201083 - TP to TR 38.849 updating clause 5.1 for the lower 6GHz band
R4-2201515 - TP for BS RF requirements
R4-2202264- TP to TR 38.849 updating clause 5.1 for the full 6GHz band
R4-2202258 - TP for TR 38.849
R4-2202263 - TP for TR 38.849 | 0.6.0 | +| 2022-03 | RAN4-102e | R4-2205559 | | | | Draft TR after RAN4-102e
Inclusion of:
R4-2206369 - A-MPR analysis results for NR-U(VLP) considering regulatory parameters in Korea
R4-2205179 - Text proposal for TR 38.849 (background results for the existing A-MPR values)
R4-2203664 - TP for TR 38.849
R4-2206367 - Text proposal for TR 38.849 | 0.7.0 | +| 2022 | RAN95 | RP-220327 | | | | TR for RAN approval | 2.0.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-03 | RAN#95 | | | | | Approved by plenary – Rel-17 spec under change control | 17.0.0 | +| 2022-06 | RAN#96 | RP-221673 | 0001 | | F | CR to TR 38.849 on adding NS value for South Korea VLP mode | 17.1.0 | +| 2023-06 | RAN#100 | RP-231343 | 0003 | 2 | F | Introduction of new countries with associated NS values and A-MPR back-off | 18.0.0 | +| 2023-09 | RAN#101 | RP-232499 | 0004 | | F | Update of the NS values for new countries supporting license-exempt operation on the 6GHz band | 18.1.0 | +| 2023-09 | RAN#101 | RP-232486 | 0005 | | F | Corrections in raster points for NR-ARFCN and GSCN | 18.1.0 | +| 2023-12 | RAN#102 | RP-233345 | 0007 | | F | Adding 20MHz channel raster points for 5925-5945MHz in the full and lower 6GHz bands | 18.2.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38859/574b2eb44f0a91aa9acfd1295dbd23b3_img.jpg b/marked/Rel-18/38_series/38859/574b2eb44f0a91aa9acfd1295dbd23b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2a1611fb2807733aea996b18f333a5cfc49d906 --- /dev/null +++ b/marked/Rel-18/38_series/38859/574b2eb44f0a91aa9acfd1295dbd23b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef61cf372cc040f56a5186707c9f6ea311948c2ae5a4ff2d499f24182f451997 +size 6022 diff --git a/marked/Rel-18/38_series/38859/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38859/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1336537ea24b263d6e72d4c0b08c151e2fd17d38 --- /dev/null +++ b/marked/Rel-18/38_series/38859/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d8d2ca43f7a92e6b2e4e5ad7020fd87ab1bd2a0801cc5a15e7402b2fa644ec5 +size 9571 diff --git a/marked/Rel-18/38_series/38859/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38859/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4712d2e290498dba28121eba436c1b95739f9ac3 --- /dev/null +++ b/marked/Rel-18/38_series/38859/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4289c49f93ddcc36112d878114a8a25c9451464337768feb70efdcd5a382a4ec +size 5675 diff --git a/marked/Rel-18/38_series/38859/a550d30ddc73ace45ba4a90d0ed8ba4d_img.jpg b/marked/Rel-18/38_series/38859/a550d30ddc73ace45ba4a90d0ed8ba4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..858e02f3fef14ecac3ef591ca64bf3ae7a8f797e --- /dev/null +++ b/marked/Rel-18/38_series/38859/a550d30ddc73ace45ba4a90d0ed8ba4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f78bd63babe035fb603bfba370130c251633fd1c883c972fb24b64f18e6319ef +size 5504 diff --git a/marked/Rel-18/38_series/38859/raw.md b/marked/Rel-18/38_series/38859/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6403caa8895c8485bceedf989cdafa766b319158 --- /dev/null +++ b/marked/Rel-18/38_series/38859/raw.md @@ -0,0 +1,2907 @@ + + +# 3GPP TR 38.859 V18.0.0 (2022-12) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on expanded and improved NR positioning; (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. + +© 2022, 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 of terms, symbols and abbreviations..... | 12 | +| 3.1 Terms..... | 12 | +| 3.2 Symbols..... | 12 | +| 3.3 Abbreviations ..... | 12 | +| 4 General descriptions of expanded NR positioning enhancements..... | 13 | +| 5 Sidelink positioning ..... | 14 | +| 5.0 Study objectives ..... | 14 | +| 5.1 Sidelink positioning scenarios and requirements..... | 14 | +| 5.2 Potential solutions for sidelink positioning..... | 16 | +| 5.2.1 Physical layer aspects for SL positioning solutions ..... | 16 | +| 5.2.1.1 Positioning Methods for SL Positioning..... | 16 | +| 5.2.1.2 Physical layer structure and reference signal design for SL positioning..... | 17 | +| 5.2.1.3 Physical layer procedures for SL positioning ..... | 18 | +| 5.2.2 Potential architecture and signaling procedures for sidelink positioning..... | 21 | +| 5.3 Summary of sidelink positioning evaluations ..... | 22 | +| 5.3.1 Evaluation of bandwidth requirements to meet identified accuracy requirements ..... | 22 | +| 5.3.2 Evaluation of absolute positioning, relative positioning, and ranging methods..... | 34 | +| 5.4 Potential specification impact for sidelink positioning..... | 35 | +| 6 Positioning enhancements for improved integrity, accuracy, and power efficiency ..... | 36 | +| 6.1 Integrity for RAT-dependent positioning techniques..... | 36 | +| 6.1.0 Study objectives..... | 36 | +| 6.1.1 Identification of error sources..... | 37 | +| 6.1.2 Methodologies, procedures and signaling for determination of positioning integrity ..... | 39 | +| 6.1.3 Summary of evaluation results for integrity for RAT-dependent positioning techniques ..... | 40 | +| 6.1.4 Potential specification impact for integrity for RAT-dependent positioning techniques..... | 40 | +| 6.2 PRS / SRS bandwidth aggregation..... | 40 | +| 6.2.0 Study objectives..... | 40 | +| 6.2.1 Potential solutions based on PRS / SRS bandwidth aggregation ..... | 40 | +| 6.2.2 Summary of evaluations for PRS/SRS bandwidth aggregation ..... | 41 | +| 6.2.3 Potential specification impact for PRS/SRS bandwidth aggregation..... | 41 | +| 6.3 NR carrier phase positioning..... | 41 | +| 6.3.0 Study objectives..... | 41 | +| 6.3.1 Potential solutions for NR carrier phase positioning..... | 42 | +| 6.3.1.1 Reference signals for NR carrier phase positioning ..... | 42 | +| 6.3.1.2 Physical layer measurements for NR carrier phase positioning ..... | 42 | +| 6.3.1.3 Physical layer procedures for NR carrier phase positioning..... | 42 | +| 6.3.2 Summary of evaluations for NR carrier phase positioning ..... | 43 | +| 6.3.3 Potential specification impact for NR carrier phase positioning..... | 51 | +| 6.4 Low power high accuracy positioning ..... | 52 | +| 6.4.0 Study objectives..... | 52 | +| 6.4.1 Target use cases and requirements for low power high accuracy positioning ..... | 52 | +| 6.4.2 Potential enhancements for low power high accuracy positioning ..... | 53 | +| 6.4.2.1 Physical layer aspects ..... | 53 | +| 6.4.2.2 Higher layer aspects..... | 53 | +| 6.4.3 Summary of evaluations for low power high accuracy positioning..... | 54 | +| 6.4.4 Potential specification impact for low power high accuracy positioning..... | 83 | +| 6.5 Positioning of UEs with reduced capabilities ..... | 84 | +| 6.5.0 Study objectives..... | 84 | +| 6.5.1 Potential solutions for positioning for RedCap UEs ..... | 84 | +| 6.5.2 Summary of evaluations for positioning for RedCap UEs..... | 85 | + +| | | | +|------------------------------------------------|---------------------------------------------------------------------------------|------------| +| 6.5.3 | Potential specification impact for positioning for RedCap UEs..... | 87 | +| 7 | Conclusions..... | 88 | +| 7.0 | Study objectives ..... | 88 | +| 7.1 | Scenarios and requirements for sidelink positioning ..... | 88 | +| 7.2 | Bandwidth requirements for sidelink positioning ..... | 89 | +| 7.3 | Sidelink positioning solutions ..... | 89 | +| 7.4 | Integrity for RAT-dependent positioning techniques..... | 90 | +| 7.5 | PRS/SRS bandwidth aggregation..... | 90 | +| 7.6 | NR carrier phase positioning..... | 91 | +| 7.7 | Low power high accuracy positioning ..... | 91 | +| 7.8 | Positioning of UEs with reduced capabilities ..... | 92 | +| Annex A: Evaluation methodologies ..... | | 93 | +| A.1 | Evaluation methodology for sidelink positioning..... | 93 | +| A.2 | Void..... | 96 | +| A.3 | Evaluation methodology for NR carrier phase positioning ..... | 96 | +| A.4 | Evaluation methodology for low power high accuracy positioning ..... | 98 | +| A.5 | Evaluation methodology for positioning for RedCap UEs ..... | 102 | +| Annex B: Evaluation results..... | | 105 | +| B.1 | Evaluation results for sidelink positioning..... | 105 | +| B.2 | Evaluation results for integrity for RAT-dependent positioning techniques ..... | 105 | +| B.3 | Void..... | 105 | +| B.4 | Evaluation results for NR carrier phase positioning ..... | 105 | +| B.5 | Evaluation results for low power high accuracy positioning ..... | 105 | +| B.6 | Evaluation results for positioning for RedCap UEs..... | 105 | +| Annex X: Change history ..... | | 106 | + +# 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 captures the findings of the study item "Study on Expanded and Improved NR Positioning" [7]. The purpose of this technical report is to document the requirements, additional scenarios, evaluations, and technical proposals treated during the study and provide a way forward toward normative work on expanded enhancements to NR positioning in TSG RAN WGs. + +# 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 38.857: "Study on NR positioning enhancements". +- [3] 3GPP TR 38.845: "Study on scenarios and requirements of in-coverage, partial coverage, and out-of-coverage NR positioning use cases". +- [4] 3GPP TS 22.261: "Service requirements for the 5G system". +- [5] 3GPP TR 22.855: "Study on ranging-based services". +- [6] 3GPP TS 22.104: "Service requirements for cyber-physical control applications in vertical domains". +- [7] RP-222616: "Revised SID on Study on expanded and improved NR positioning". +- [8] 3GPP TR 37.885: "Study on evaluation methodology of new Vehicle-to-Everything (V2X) use cases for LTE and NR". +- [9] 3GPP TR 36.885: "Study on LTE-based V2X Services". +- [10] 3GPP TR 36.843: "Study on LTE Device to Device Proximity Services". +- [11] 3GPP TR 38.901: "Study on channel model for frequencies from 0.5 to 100 GHz". +- [12] 3GPP TR 38.855: "Study on NR positioning support". +- [13] 3GPP TR 38.840: "Study on User Equipment (UE) power saving in NR". +- [14] 3GPP TR 38.802: "Study on New Radio Access Technology - Physical Layer Aspects". +- [15] 3GPP TR 38.830: "Study on NR coverage enhancements". +- [16] 3GPP TS 37.355: "LTE Positioning Protocol (LPP)". +- [17] 3GPP TS 38.455: "NR Positioning Protocol A (NRPPa)". +- [18] R1-2210831 Evaluation of SL positioning Nokia, Nokia Shanghai Bell +- [19] R1-2210900 Finalizing SL positioning evaluation Huawei, HiSilicon +- [20] R1-2211011 Evaluation of sidelink positioning performance vivo + +- [21] R1-2211446 Evaluation results for SL positioning OPPO +- [22] R1-2211202 Further performance evaluation for SL positioning CATT, GOHIGH +- [23] R1-2211615 Evaluation of SL positioning Sony +- [24] R1-2211500 Discussion on evaluation of SL positioning ZTE, CMCC +- [25] R1-2211368 Discussion on evaluation of sidelink positioning xiaomi +- [26] R1-2211739 SL Positioning Evaluation and Performance Lenovo +- [27] R1-2211267 Discussion on evaluation of SL positioning LG Electronics +- [28] R1-2211720 Evaluation results for SL positioning InterDigital, Inc. +- [29] R1-2212049 Discussion on Evaluation for SL Positioning Samsung +- [30] R1-2212121 Sidelink Positioning Evaluation Assumptions and Results Qualcomm Incorporated +- [31] R1-2212739 Evaluation of SL positioning Intel Corporation +- [32] R1-2212427 Evaluation results and observations on V2X and IIoT use case for sidelink positioning CEWiT +- [33] R1-2212512 Evaluation of NR SL positioning and ranging Ericsson +- [34] Void +- [35] R1-2208517 Discussion on Low Power High Accuracy Positioning Quectel +- [36] R1-2208559 Discussion on evaluation on LPHAP Spreadtrum Communications +- [37] R1-2208651 Discussion on Low Power High Accuracy Positioning vivo +- [38] R1-2208737 Views on LPHAP Nokia, Nokia Shanghai Bell +- [39] R1-2208802 Discussion on Low Power High Accuracy Positioning OPPO +- [40] R1-2210242 Discussion on Low Power High Accuracy Positioning CATT +- [41] R1-2209060 On Low Power High Accuracy Positioning Intel Corporation +- [42] R1-2209107 Discussion on Low Power High Accuracy Positioning Sony +- [43] R1-2210398 Discussion on low power high accuracy positioning ZTE +- [44] R1-2209294 Discussion on Low Power High Accuracy Positioning xiaomi +- [45] R1-2209344 Discussion on low power high accuracy positioning CMCC +- [46] R1-2209396 LPHAP considerations Lenovo +- [47] R1-2209490 Discussions on Low Power High Accuracy Positioning (LPHAP) techniques InterDigital, Inc. +- [48] R1-2209739 Discussion on LPHAP Samsung +- [49] R1-2209786 Views on low power high accuracy positioning Sharp +- [50] R1-2209806 Discussion on LPHAP in idle/inactive state LG Electronics +- [51] R1-2209910 Discussion on Low Power High Accuracy Positioning NTT DOCOMO, INC. +- [52] R1-2209993 Requirements, Evaluations, Potential Enhancements for Low Power High Accuracy Positioning Qualcomm Incorporated +- [53] R1-2210178 Evaluations for Low Power High Accuracy Positioning Ericsson + +| | | +|------|--------------------------------------------------------------------------------------------------------| +| [54] | Void | +| [55] | R1-2208652 Discussion on positioning for RedCap UEs vivo | +| [56] | R1-2208738 Views on Positioning for RedCap UEs Nokia, Nokia Shanghai Bell | +| [57] | R1-2208803 Discussion on Positioning for RedCap UEs OPPO | +| [58] | R1-2208985 Discussion on positioning for RedCap UEs CATT | +| [59] | R1-2209061 Enhancements for positioning for RedCap UEs Intel Corporation | +| [60] | R1-2209108 Considerations on positioning for RedCap UEs Sony | +| [61] | R1-2209153 Discussion on positioning support for RedCap UEs NEC | +| [62] | R1-2209217 Discussion on Positioning for RedCap UE ZTE | +| [63] | R1-2209346 Discussion on RedCap positioning CMCC | +| [64] | R1-2209397 Positioning for RedCap devices Lenovo | +| [65] | R1-2209491 Discussions on positioning for RedCap UEs InterDigital, Inc. | +| [66] | R1-2209590 Discussions on Positioning for RedCap UEs Apple | +| [67] | R1-2209740 Discussion on Positioning for RedCap UEs Samsung | +| [68] | R1-2209787 Views on positioning for RedCap UEs Sharp | +| [69] | R1-2209807 Discussion on positioning support for RedCap UEs LG Electronics | +| [70] | R1-2209911 Discussion on positioning for RedCap UEs NTT DOCOMO, INC. | +| [71] | R1-2209994 Positioning for Reduced Capability UEs Qualcomm Incorporated | +| [72] | R1-2210179 Positioning for RedCap UEs Ericsson | +| [73] | R1-2208455 Discussion on NR carrier phase positioning Huawei, HiSilicon | +| [74] | R1-2208650 Discussion on carrier phase measurement enhancements vivo | +| [75] | R1-2208983 Discussion on improved accuracy based on NR carrier phase measurement CATT | +| [76] | R1-2209215 Discussion on carrier phase measurement based positioning ZTE | +| [77] | R1-2210177 Improved accuracy based on NR carrier phase measurement Ericsson | +| [78] | R1-2212379 Evaluation of SL positioning Fraunhofer IIS, Fraunhofer HHI | +| [79] | R1-2210903 Remaining issues for carrier phase positioning Huawei, HiSilicon | +| [80] | R1-2211014 Discussion on carrier phase measurement enhancements vivo | +| [81] | R1-2211205 Further discussion on improved accuracy based on NR carrier phase measurement CATT | +| [82] | R1-2211312 Views on improved accuracy based on NR carrier phase measurement Nokia, Nokia Shanghai Bell | +| [83] | R1-2211406 Improved positioning accuracy with NR carrier phase measurements Intel Corporation | +| [84] | R1-2211435 Discussions on Carrier Phase Measurement for NR Positioning OPPO | +| [85] | R1-2212520 Discussion on carrier phase measurement based positioning ZTE | +| [86] | R1-2211924 Discussion on OFDM based carrier phase measurement in NR LG Electronics | + +- [87] R1-2212859 Discussion on NR Carrier Phase Measurement Samsung +- [88] R1-2212124 Phase Measurements in NR Positioning Qualcomm Incorporated +- [89] R1-2212519 Views on NR carrier phase measurement for positioning accuracy enhancement IIT Kanpur, CEWiT +- [90] R1-2212515 Improved accuracy based on NR carrier phase measurement Ericsson +- [91] R1-2208206 FL Summary #3 Carrier Phase Measurements, Moderator (CATT) +- [92] R1-2210904 Remaining issues for LPHAP Huawei, HiSilicon +- [93] R1-2211015 Discussion on Low Power High Accuracy Positioning vivo +- [94] R1-2211055 Discussions and evaluation of LPHAP enhancements FUTUREWEI +- [95] R1-2211206 Further discussion on Low Power High Accuracy Positioning CATT +- [96] R1-2211239 Discussion on evaluation and solutions for LPHAP Spreadtrum Communications +- [97] R1-2211313 Views on LPHAP Nokia, Nokia Shanghai Bell +- [98] R1-2211371 Discussion on Low Power High Accuracy Positioning xiaomi +- [99] R1-2211407 On Low Power High Accuracy Positioning Intel Corporation +- [100] R1-2211436 Discussion on Low Power High Accuracy Positioning OPPO +- [101] R1-2211504 Discussion on low power high accuracy positioning ZTE +- [102] R1-2211618 Views on Low Power High Accuracy Positioning Sony +- [103] R1-2211688 Discussion on low power high accuracy positioning CMCC +- [104] R1-2211730 Discussions on Low Power High Accuracy Positioning (LPHAP) techniques InterDigital, Inc. +- [105] R1-2211744 LPHAP considerations Lenovo +- [106] R1-2211925 Discussion on LPHAP in idle/inactive state LG Electronics +- [107] R1-2211991 Discussion on Low Power High Accuracy Positioning NTT DOCOMO, INC. +- [108] R1-2212053 Discussion on LPHAP Samsung +- [109] R1-2212125 Requirements, Evaluations, Potential Enhancements for Low Power High Accuracy Positioning Qualcomm Incorporated +- [110] R1-2212516 Evaluations for Low Power High Accuracy Positioning Ericsson +- [111] R1-2210905 Remaining issues of RedCap positioning Huawei, HiSilicon +- [112] R1-2210921 Discussion on Positioning for RedCap UEs Quectel +- [113] R1-2211016 Discussion on positioning for RedCap UEs vivo +- [114] R1-2211207 Further discussion on positioning for RedCap UEs CATT +- [115] R1-2211314 Views on Positioning for RedCap UEs Nokia, Nokia Shanghai Bell +- [116] R1-2211408 Enhancements for positioning for RedCap UEs Intel Corporation +- [117] R1-2211437 Discussion on Positioning for RedCap UEs OPPO +- [118] R1-2212743 Discussion on Positioning for RedCap UE ZTE +- [119] R1-2211619 Views on positioning for RedCap UEs Sony + +- [120] R1-2211689 Discussion on RedCap positioning CMCC +- [121] R1-2211732 Discussions on positioning for RedCap UEs InterDigital, Inc. +- [122] R1-2211741 Public Safety Personal Protection Equipment (PPE) FirstNet, AT&T, UK Home Office, Erillisverket, MINISTERE DE L'INTERIEUR, SyncTechno Inc., Softil, Nkom +- [123] R1-2211745 Positioning for RedCap devices Lenovo +- [124] R1-2211819 On Positioning for RedCap UEs Apple +- [125] R1-2211926 Discussion on positioning support for RedCap UEs LG Electronics +- [126] R1-2211992 Discussion on positioning for RedCap UEs NTT DOCOMO, INC. +- [127] R1-2212054 Discussion on Positioning for RedCap UEs Samsung +- [128] R1-2212126 Positioning for Reduced Capabilities UEs Qualcomm Incorporated +- [129] R1-2212180 Views on positioning for RedCap UEs Sharp +- [130] R1-2212197 The potential solutions for RedCap UEs for positioning MediaTek Inc. +- [131] R1-2212368 Discussion on positioning support for RedCap UEs NEC +- [132] R1-2212517 Positioning for RedCap UEs Ericsson +- [133] R1-2208454 Error source for NR RAT-dependent positioning Huawei, HiSilicon +- [134] R1-2210902 Remaining issues for RAT-dependent integrity Huawei, HiSilicon +- [135] R1-2208649 Discussion on solutions for integrity of RAT-dependent positioning vivo +- [136] R1-2208735 Views on solutions for integrity of RAT-dependent positioning techniques Nokia, Nokia Shanghai Bell +- [137] R1-2209214 Discussion on integrity of RAT dependent positioning ZTE +- [138] R1-2211502 Discussion on integrity of RAT dependent positioning ZTE +- [139] R1-2209488 Discussion on integrity for RAT dependent positioning techniques InterDigital +- [140] Void +- [141] R1-2212051 Discussion on Integrity of RAT Dependent Positioning Samsung +- [142] R1-2210176 Error Sources characterization for integrity of RAT dependent positioning techniques Ericsson +- [143] R1-2210174 Evaluation of NR SL positioning and ranging Ericsson +- [144] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2". +- [145] 3GPP TR 23.700-86: "Study on Architecture Enhancement to support Ranging based services and sidelink positioning". +- [146] 3GPP TS 38.305: "Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN". + +# 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]. + +**Target UE:** UE to be positioned (in this context, using SL, i.e., PC5 interface). + +**Anchor UE:** UE supporting positioning of target UE, e.g., by transmitting and/or receiving reference signals for positioning, providing positioning-related information, etc., over the SL interface. + +**Sidelink positioning:** Positioning UE using reference signals transmitted over SL, i.e., PC5 interface, to obtain absolute position, relative position, or ranging information. + +**Ranging:** Determination of the distance and/or the direction between a UE and another entity, e.g., anchor UE. + +**Sidelink positioning reference signal (SL PRS):** Reference signal transmitted over SL for positioning purposes. + +**SL PRS (pre-)configuration:** (Pre-)configured parameters of SL PRS such as time-frequency resources (other parameters are not precluded) including its bandwidth and periodicity. + +**SLPP:** Protocol for Sidelink positioning procedures. + +## 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], TS 38.305 [146], 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]. + +| | | +|--------|-------------------------------------| +| AGV | Automated Guided Vehicle | +| BW | Bandwidth | +| CFO | Carrier Frequency Offset | +| CP | Carrier Phase | +| CPP | Carrier Phase Positioning | +| DD | Double Differential | +| DL | Downlink | +| GNSS | Global Navigation Satellite System | +| IIoT | Industrial Internet of Things | +| IoT | Internet of Things | +| ITS | Intelligent Transportation Systems | +| KPI | Key Performance Indicator | +| LOS | Line-of-Sight | +| LPHAP | Low Power High Accuracy Positioning | +| NLOS | Non-Line-of-Sight | +| OLPC | Open Loop Power Control | +| OOC | Out Of Coverage | +| PCO | Phase Center Offset | +| PFL | Positioning Frequency Layer | +| PRS | Positioning Reference Signal | +| RAN | Radio Access Network | +| RAT | Radio Access Technology | +| RedCap | Reduced Capability | +| RTK | Real Time Kinematic | + +| | | +|-----|----------------------------| +| SD | Single Differential | +| SI | Study Item | +| SID | Study Item Description | +| SL | Sidelink | +| SRS | Sounding Reference Signals | +| TR | Technical Report | +| TS | Technical Specification | +| UE | User Equipment | +| UL | Uplink | +| V2X | Vehicle to Everything | +| WI | Work Item | + +# --- 4 General descriptions of expanded NR positioning enhancements + +In Release 17, 3GPP RAN conducted studies on "NR positioning enhancements" TR 38.857 [2] and "Scenarios and requirements of in-coverage, partial coverage, and out-of-coverage NR positioning use cases" TR 38.845 [3]. + +The study on "Scenarios and requirements of in-coverage, partial coverage, and out-of-coverage NR positioning use cases" focussed on V2X and public safety use cases with the outcome being captured in TR 38.845 [3]. Additionally, SA1 has developed requirements in TS 22.261 [4] for "Ranging based services" TR 22.855 [5] and has developed positioning accuracy requirements in TS 22.104 [6] for IIoT use cases in out-of-coverage scenarios. There is a need for 3GPP to study and develop sidelink positioning solutions that can support the use cases, scenarios and requirements identified during these activities. + +The study on "NR positioning enhancements" TR 38.857 [2] investigated higher accuracy, and lower latency location, high integrity and reliability requirements resulting from new applications and industry verticals for 5G. Some of the enhancements identified during that work have been specified during the Release 17 Work Item on "NR positioning enhancements", but there remain a number of opportunities for enhancement that have not yet been incorporated into the specifications. + +Regarding higher accuracy, two promising techniques identified in earlier studies will be considered in Release 18: one is to take the advantage of the rich 5G spectrum to increase the bandwidth for the transmission and reception of the positioning reference signals based on PRS/SRS bandwidth aggregation for intra-band carriers, and the other is to use the NR carrier phase measurements. GNSS carrier phase positioning has been used very successfully for centimetre-level positioning but is limited to outdoor applications. NR carrier phase positioning has the potential for significant performance improvements for indoor and outdoor deployments in comparison with the existing NR positioning methods, as well as shorter latency and lower UE power consumption in comparison with RTK-GNSS outdoors. + +Positioning integrity is a measure of the trust in the accuracy of the position-related data and the ability to provide timely warnings based on assistance data provided by the network. The focus in Release 17 work was on GNSS integrity, and for Release 18 it is natural to extend this to address other positioning techniques as well as there are relevant integrity aspects of mission critical use cases that rely on positioning estimates and the corresponding uncertainty estimate. Integrity enables applications to make the correct decisions based on the reported position, e.g., when monitoring a robotic arm to decide whether its arm movement are within allowed limits to ensure safety distances to humans and other objects. + +SA1 has introduced requirements for LPHAP (Low Power High Accuracy Positioning) for industrial IoT scenarios including use cases such as massive asset tracking, AGV tracking in industrial factory and person localization in danger zones. The SA1 requirements are for high accuracy and extreme low power consumption with battery life sustainable up to one or more years. A typical scenario of interest is use case 6 as defined TS 22.104 [6], which corresponds to tracking of workpiece (in- and outdoor) in assembly area and warehouse with a target accuracy of <1m, a positioning interval of 15-30 seconds, and a battery life of 6-12 months. While Release 17 NR positioning has introduced support for positioning in RRC\_INACTIVE state, there is a need to evaluate whether the current system allows LPHAP requirements to be met. + +Release 17 has specified support for RedCap UEs with reduced bandwidth support and reduced complexity including reduced number of receive chains. Such UEs could support NR positioning functionality but there is a gap in that the core and performance requirements have not been specified for the positioning related measurements performed by + +RedCap UEs, and no evaluation was performed to see how the reduced capabilities of RedCap UEs might impact eventual position accuracy. This gap is to be investigated by the present SI. + +# 5 Sidelink positioning + +## 5.0 Study objectives + +The scope of the study on solutions for SL positioning is defined in the SID [7] as: + +- Scenario/requirements for SL positioning +- Identify specific target performance requirements to be considered for the evaluation based on existing 3GPP work and inputs from industry forums +- Define evaluation methodology with which to evaluate SL positioning for the use cases and coverage scenarios, reusing existing methodologies from sidelink communication and from positioning as much as possible +- Study and evaluate performance and feasibility of potential solutions for SL positioning, considering relative positioning, ranging and absolute positioning: + - Evaluate bandwidth requirement needed to meet the identified accuracy requirements + - Study of positioning methods (e.g., TDOA, RTT, AOA/D, etc) including combination of SL positioning measurements with other RAT dependent positioning measurements (e.g., Uu-based measurements) + - Study of sidelink reference signals for positioning purposes from physical layer perspective, including signal design, resource allocation, measurements, associated procedures, etc, reusing existing reference signals, procedures, etc from sidelink communication and from positioning as much as possible + - Study of positioning architecture and signaling procedures (e.g., configuration, measurement reporting, etc) to enable sidelink positioning covering both UE based and network-based positioning. + +## 5.1 Sidelink positioning scenarios and requirements + +The following objectives are captured in SID [7] on scenarios and requirements for study of sidelink positioning solutions: + +- Coverage scenarios to cover: In-coverage, partial-coverage and out-of-coverage. +- Requirements: Based on requirements identified in TR 38.845 [3] and TS 22.261 [4] and TS 22.104 [6]. +- Use cases: V2X (TR 38.845) [3], public safety (TR 38.845) [3], commercial (TS 22.261) [4], IIOT (TS 22.104) [6]. +- Spectrum: ITS, licensed + +Both PC5-only-based positioning solutions and combination of Uu- and PC5-based positioning solutions are considered for study of sidelink positioning. + +Based on the study, from the perspectives of RAN1 and RAN2, both of the following operation scenarios are recommended for normative work: + +- Operation Scenario 1: PC5-only-based positioning. +- Operation Scenario 2: Combination of Uu- and PC5-based positioning. + +For evaluations, in-coverage and out-of-coverage scenarios are prioritized. Further, for evaluation of V2X and public safety use-cases, at least in-coverage and out-of-coverage scenarios are considered, while for evaluation of IIoT and commercial use-cases, at least in-coverage scenarios are considered. + +For evaluations, operation in FR1 bands with channel bandwidths of up to 100 MHz is considered. Additionally, operation in FR2 bands with channel bandwidths of up to 400 MHz is optionally considered. + +For evaluations of relative positioning, the horizontal plane is assumed to be parallel to the ground. + +For this study, requirements on positioning accuracy are expressed as accuracy requirements in terms of percentiles of UEs for one or more of the following metrics: + +- Ranging accuracy, expressed as the difference (error) between the calculated distance/direction and the actual distance/direction in relation to another node +- Relative positioning accuracy, expressed as the difference (error) between the calculated horizontal/vertical position and the actual horizontal/vertical position relative to another node +- Absolute positioning accuracy, expressed as the difference (error) between the calculated horizontal/vertical position and the actual horizontal/vertical position. + +It should be noted that exact applicability of specific requirements can be expected to vary across use-cases. + +For sidelink based ranging, for a given use-case, the value of the distance requirement for ranging distance accuracy is same as the value identified for horizontal positioning accuracy for relative positioning. + +For ranging between two devices, ranging direction accuracy is defined as accuracy of Angle of Arrival (AoA) at a receiving node. + +For evaluation of different use-cases for SL positioning, the considered target accuracy requirements are summarized in Table 5.1-1. + +**Table 5.1-1: Target accuracy requirements for SL positioning** + +| SL Positioning KPIs | V2X | Public Safety | IIoT | Commercial | +|---------------------------------|----------------------------------------------------------------------------------------|-------------------------------------------------------------|----------------------------------------------------|-------------------------------------------| +| Horizontal Positioning Accuracy | Set A (similar to "Set 2" defined in [3]): 1.5 m for 90% of UEs (absolute or relative) | 1 m for 90% of UEs (absolute or relative) | Set A: 1 m for 90% of UEs (absolute or relative) | 1 m for 90% of UEs (absolute or relative) | +| | Set B (similar to "Set 3" defined in [3]): 0.5 m for 90% of UEs (absolute or relative) | | Set B: 0.2 m for 90% of UEs (absolute or relative) | | +| Vertical Positioning Accuracy | Set A: 3 m for 90% of UEs (absolute or relative) | 2 m (absolute or relative between 2 UEs) for 90% of UEs | Set A: 1 m for 90% of UEs (absolute or relative) | 2 m for 90% of UEs (absolute or relative) | +| | Set B: 2 m for 90% of UEs (absolute or relative) | 0.3 m (relative positioning change for 1 UE) for 90% of UEs | Set B: 0.2 m for 90% of UEs (absolute or relative) | | +| Relative Speed | - | Up to 30 km/h | Up to 30 km/h | Up to 30 km/h | +| Angle Accuracy | Set A: $Y = \pm 15^\circ$ for 90% of the UEs | | | | +| | Set B: $Y = \pm 8^\circ$ for 90% of the UEs | | | | + +NOTE 1: For evaluated SL positioning methods, the performance results in Annex B.1 are described in terms of: + +- whether each of the two requirements are satisfied, and +- %-ile of UEs satisfying the target positioning accuracy for a requirement that may not be satisfied with 90%. + +NOTE 2: Target positioning requirements may not necessarily be reached for all scenarios and deployments + +NOTE 3: All positioning techniques may not achieve all positioning requirements in all scenarios. + +## 5.2 Potential solutions for sidelink positioning + +### 5.2.1 Physical layer aspects for SL positioning solutions + +#### 5.2.1.1 Positioning Methods for SL Positioning + +As part of the study on potential solutions for sidelink positioning, at least the following positioning methods using SL measurements are identified for possible introduction: + +- RTT-type solutions using SL + - This includes single-sided (also known as one-way) RTT and double-sided (also known as two-way) RTT + - May include RTT with one or multiple devices. + - Strive to minimize the changes needed on top of the specification support for single-sided RTT, if any, for the introduction of double-sided RTT. + - NOTE: a UE should be able to support single-sided RTT without having to support double-sided RTT. +- SL-AoA + - This includes both Azimuth of Arrival (AoA) and Zenith of Arrival (ZoA) in the study +- SL-TDOA + - For SL-only positioning, at least for the purpose of absolute positioning estimation of a target UE, SL-TDOA corresponds to a method wherein SL PRS are transmitted from multiple anchor UEs to a target UE (i.e., DL-TDOA-like operation), and/or from a target UE to multiple anchor UEs (i.e., UL-TDOA-like operation). + - Based on the study, it was agreed that both DL-TDOA-like operation and UL-TDOA-like operation should be introduced. + - A UE is not required to support both DL-TDOA-like operation and UL-TDOA-like operation. +- SL-AoD + - SL-AoD is deprioritized against the other methods listed above for possible introduction. + +Note that the above identification of methods does not necessarily imply their specification as separate methods nor specification of a unified positioning method for sidelink. + +For the study of different positioning methods, the following aspects are considered: + +- Definition(s) of the corresponding SL measurements for each method +- Applicability of different positioning methods to absolute or relative positioning or ranging, including whether such categorization is needed to be discussed +- For angle-based methods, antenna configuration consideration(s) using practical UE capabilities +- Per-panel location, if UE uses multiple panels +- UE's mobility, especially for V2X scenarios +- Impact of synchronization error(s) between UEs + +- Existing SL measurements (e.g., RSSI, RSRP), and UE ID information etc, may be used. + +With regards to the sidelink positioning measurement report, the following aspects are included as part of the study: + +- Contents of the measurement report, that may include: + - One or more sidelink positioning measurement(s) + - Timestamp(s) associated with a sidelink positioning measurement + - Quality metric(s) associated with a sidelink positioning measurement + - Identification Information for a sidelink positioning measurement +- Time domain behavior of the measurement report (e.g., one-shot, triggered, aperiodic, semi-persistent, periodic). + +Whether sidelink positioning measurements can be higher-layer report and/or a lower-layer report is considered in the study. + +With regards to the Positioning methods supported using SL PRS measurements at least the following measurements are agreed to be introduced: + +- SL Rx-Tx time difference measurement +- SL RSTD measurement +- SL RSRP measurement +- SL RSRPP measurement +- SL RTOA measurement +- SL Azimuth angle of Arrival (AoA) and SL Zenith angle of Arrival (ZoA) measurement. + +#### 5.2.1.2 Physical layer structure and reference signal design for SL positioning + +New reference signal designs for SL positioning/ranging, referred to as SL PRS, are studied using the existing PRS/SRS design and SL design framework as starting points. + +For sequence design for the new reference signal for SL PRS, pseudo-random sequence, using existing DL-PRS sequence as a starting point, is identified as the preferred choice. + +With regards to the numerologies of the SL PRS, the study is limited to those supported for NR Sidelink. + +As part of the study, at least the following aspects are considered: Sequence design, frequency domain pattern, time domain pattern (e.g., number of symbols, repetitions, etc), time domain behavior, configuration/triggering/activation/deactivation of the SL PRS, AGC time, Rx-Tx turnaround times, supportable bandwidth(s), multiplexing options with other SL channels, and randomization/orthogonalization options. + +On the physical structure of SL PRS, a frequency domain pattern following a comb-N design is studied, at least including the following: + +- $N \geq 1$ (where $N=1$ corresponds to full RE mapping pattern) +- Fully staggered SL PRS pattern (e.g., M symbols of SL PRS with comb-N with $M=N$ and, at each symbol a different RE offset is used), Partially staggered SL PRS pattern (e.g., M symbol(s) of SL PRS with comb-N, with $M < N$ , at each symbol a different RE offset is used), Unstaggered SL PRS patterns (e.g., M symbol(s) of SL PRS with comb-N, at each symbol a same RE offset is used, $N > 1$ ) + - Of the above, fully and partially staggered patterns are further prioritized. +- The number of symbols of SL PRS within a slot + - Any relation to the comb-N option + - RE offset pattern repetitions within a slot + +With regards to the frequency and time domain pattern of a SL PRS resource within a slot, a SL PRS resource has the following characteristics: + +- On the value N (comb size) and the number M of SL PRS symbols within a slot excluding the symbol(s) used for AGC training / Rx-Tx turnaround: + - At least the following values are considered as potential candidate values: $N = \{1,2,4,6,8,12\}$ + - The values considered as potential candidate values for M need further consideration during normative work. + - Whether to consider $N > 12$ as a potential candidate value(s) will be considered further during normative work. +- The symbols of a SL PRS resource within a slot are consecutive symbols + - Whether to support consecutive and/or non-consecutive symbols for shared resource pool can be considered further during normative work. +- Details of RE-Offset sequence within a SL PRS resource, including whether to have in the end of the SL PRS pattern a symbol with the same RE-offset as the first symbol, for phase-tracking purpose, can be considered further during normative work. + +For the new SL PRS design, the following are further studied: + +- Number of symbol(s) for AGC and/or Rx-Tx turnaround time. +- Conditions under which AGC training and/or Rx-Tx turnaround time are needed. + +#### 5.2.1.3 Physical layer procedures for SL positioning + +On the configuration/ activation/ deactivation/ triggering/ reservation of SL PRS, the study focused on the following options, with considerations on flexibility, overhead, latency, and reliability: + +- Option 1: High-layer-only signaling involvement in the SL PRS configuration. + - No Lower layer involvement, e.g., SL-MAC-CE or SCI or DCI, for the activation or the triggering of a SL PRS. + - Based on the study, this option may correspond to: + - A SL PRS configuration that is a single-shot or multiple shots. + - A high-layer configuration that may be received from an LMF, a gNB, or a UE. +- Option 2: High-layer and lower-layer signaling involvement in the SL PRS configuration. + - Lower-layer may correspond to SL-MAC-CE, or SCI, or DCI. + - For example, high layer signaling can be used for SL PRS configuration and lower layer signaling can may be used for initiating SL positioning and/or configuration/triggering/activating/deactivating/indicating and potential resource indication/reservation transmission of SL PRS. + +Regarding resource allocation for SL PRS, at least the following schemes are studied: + +- **Scheme 1:** Network-centric operation SL PRS resource allocation (e.g., similar to a legacy Mode 1 solution) + - The network (e.g., gNB, LMF, gNB & LMF) allocates resources for SL PRS +- **Scheme 2:** UE autonomous SL PRS resource allocation (e.g., similar to legacy Mode 2 solution) + - At least one of the UE(s) participating in the sidelink positioning operation allocates resources for SL PRS + - Applicable regardless of the network coverage +- Potential mechanisms, if needed, for SL PRS resource coordination across a number of transmitting UEs (e.g., Inter-UE Coordination (IUC)-like solutions) can be considered further during normative work. + +Regarding Scheme 1 SL PRS resource allocation, a transmitting UE receives a SL PRS resource allocation signaling from the network. One or both of the following options are considered further for the corresponding signaling: + +- Opt. 1: Through higher layers from the LMF +- Opt. 2: Through dynamic grants, or via configurations of configured grant type 1 or type 2 from gNB. + +Regarding Scheme 2 SL PRS resource allocation, at least the following aspects are studied: + +- Resource selection mechanism for SL PRS +- Inter-UE coordination +- Aspects for congestion control mechanisms for SL PRS. + +For Scheme 2 SL PRS resource allocation, one or both of the following options may be supported during normative work: + +- Option 1: A sensing-based resource allocation +- Option 2: A random resource selection +- For either Option 1 or 2, the legacy designs for UE autonomous resource allocation should be used as a starting point and potential enhancements that may be needed may be considered during the normative work. + +Additionally, on SL positioning resource allocation, the following alternatives are studied: + +- Alt. 1: Only dedicated resource pool(s) can be (pre-)configured for SL PRS + - For dedicated resource pool(s) for SL positioning, at least the following details are agreed to be considered: + - which slots can be used, SL frame structure, SL positioning slot structure, multiplexing of SL PRS with control information (if included in the same slot), + - positioning measurement report, + - whether a dedicated frequency allocation (e.g., layer/BWP) is needed for SL PRS, + - resource allocation procedure(s) of SL PRS, + - NOTE: This option may or may not include control information (i.e., configuration/ activation/ deactivation/ triggering of SL PRS) for the purpose of SL positioning operation. +- Alt. 2: Either dedicated resource pool(s) and/or a shared resource pool(s) with sidelink communication can be (pre-)configured for SL PRS + - For shared resource pool(s) for SL positioning, at least the following details are considered: + - Co-existence between SL communication and SL positioning, backward compatibility + - Multiplexing considerations of SL PRS with other PHY channels (PSCCH, PSSCH, PSFCH) and any modifications in the SL-slot structure. + - NOTE: whether other signals/channels can be present in the dedicated resource pool can be considered further during the normative work. + +With regards to the SL Positioning resource allocation, it was agreed that either dedicated resource pool(s) and/or a shared resource pool(s) with sidelink communication can be (pre-)configured for SL PRS. + +- NOTE: this does not imply that the design is the same for both types of resources pools. +- NOTE: shared resources pool(s) should be supported with backward compatibility. + +A dedicated SL PRS resource pool is (pre-)configured in the only SL BWP of a carrier. + +The following options are considered for multiplexing of other channels in a dedicated resource pool for SL positioning in addition to SL PRS: + +- Opt. 1: No other channel can be included beyond SL PRS +- Opt. 2: PSCCH which carries SCI associated with SL PRS transmission(s) is included +- Opt. 3: PSCCH which carries SCI associated with SL PRS transmission(s) and PSSCH associated with SL PRS transmission(s) are included + - Definition of "PSSCH associated with SL PRS transmission(s)" can be considered further during normative work. + +At least for a dedicated resource pool for SL positioning, the following alternatives are studied for subsequent down-selection: + +- Alt. 1: The bandwidth of SL PRS can be same or smaller than that of the resource pool. +- Alt. 2: The bandwidth of SL PRS is the same as that of the resource pool. +- Bandwidth of SL PRS transmission for a shared resource pool can be considered further during normative work. + +For SL Positioning resource (pre-)configuration in a shared resource pool with Rel-16/17/18 sidelink communication, backward compatibility with legacy Rel-16/17 UEs should be ensured. + +With regards to SL signaling of the reservation/indication of SL PRS resource(s) for dedicated resource pool and shared resource pool for positioning: + +- SCI can be used for reserving/indicating one or more SL PRS resource(s) + - NOTE: This does not imply that only SCI is being used. Higher layer signaling may be used for the purpose of indicating a part of the SL PRS configuration. + - Whether SCI is single stage SCI or two stage SCI can be considered further during normative work. +- Use of SL-MAC-CE or other higher-layer signaling for SL PRS resource reservation/indication can be considered further during normative work. + +The granularity of time-domain resource allocation for SL PRS transmission is studied. + +The following options for time-domain resource assignments and associated Tx UE behavior for SL PRS transmissions are studied: + +- Periodic SL PRS + - SL PRS is transmitted periodically with a transmission periodicity. + - Any additional details, including whether or not higher layers can start/stop transmission, can be considered further during normative work. +- Semi-persistent SL PRS + - SL PRS is transmitted periodically with a transmission periodicity after activation and until deactivation. +- Aperiodic SL PRS + - SL PRS is transmitted at least once after either triggering or request. +- Applicability of the above options to SL PRS resource allocation schemes 1 and 2 respectively can be considered further during normative work. + +- Details of Rx UE behavior can be separately discussed during normative work. +- Mechanism(s) to be used for activation/deactivation/triggering can be considered further during normative work. + +Resource allocation for SL-Positioning measurement reports is also included in the study. + +Power control mechanisms for SL PRS transmission, including their necessity, are considered in the study. Based on the study, it was agreed that at least Open Loop Power Control (OLPC) should be introduced during the normative work. + +### 5.2.2 Potential architecture and signaling procedures for sidelink positioning + +#### 5.2.2.1 Potential architecture for SL positioning + +Sidelink positioning in-coverage, partial coverage and out-of-coverage scenarios may be supported. In partial coverage scenarios, either of UEs including target UE and one or multiple anchor UEs may be OOC, but with at least one UE being in coverage. + +The architecture and signaling procedures are studied to support Operation Scenarios 1 and 2 involving PC5-only-based positioning and combination of Uu- and PC5-based positioning respectively. + +NOTE: How to enable the procedures/signaling for supporting SL positioning in partial coverage will be further discussed in normative work. + +RAN2 follow SA2 on the architecture, including the possibility of a UE as a location server. RAT-independent SL positioning is not considered in this release. RAN2 waits for SA2 on the triggering of the positioning procedures from upper layers. + +The current NG-RAN positioning architecture can in principle be re-used to support Sidelink Positioning in in-coverage and partial coverage scenarios. + +#### 5.2.2.2 Sidelink Positioning Protocol (SLPP) + +With regards to the sidelink positioning procedures between UEs, SLPP is introduced to support at least the following functionalities: + +- SL Positioning Capability Transfer +- SL Positioning Assistance Data exchange +- SL Location Information Transfer +- Error handling +- Abort + +The cast type for SLPP signaling is studied, including unicast, groupcast and broadcast. + +Unicast/one-to-one operation is assumed as baseline for exchange of SLPP signaling between UEs. Unicast SLPP session-based operation is supported. At least "centralized" operation is supported, i.e., operation where one UE performs range and/or position calculations based on measurement/location information relating to itself and/or other UEs. It is feasible to send at least the following positioning signaling for groupcast/broadcast (in addition to unicast) from RAN2's perspective: + +- SL positioning capability +- SL positioning assistance data + +Location information is not excluded and can be further considered in normative work. + +RAN2 will further discuss in normative work: + +- The security issues (e.g., requirements for ciphering and/or integrity) on specific information of SL positioning capability and assistance data in groupcast/broadcast. + +- The use cases for applying groupcast/broadcast. + +Both session-based and session-less operation for sidelink positioning signaling are studied. + +Sidelink positioning supports a session-based concept in SLPP, in which signaling messages within a session can be associated with one another by the involved UEs. The relationship to upper-layer designs from SA2 can be discussed during normative work. + +Whether to also support session-less operation and what aspects of session-based operation would not be included can be studied further during normative work. + +At least in the case that positioning methods are supported that do not require a mutual exchange of SLPP messages associated with one another among UEs, SLPP session-less operation can be supported. If session-less operation can be operated with security can be studied further during normative work. + +If it is determined to support group positioning, it is feasible to perform at least ranging with the estimate calculation at multiple UEs. + +SLPP is a separate ASN.1 module from LPP (this does not necessarily imply whether it is included in TS 37.355 [16]). + +For the transport layer of SLPP, RAN2 agrees to down select between PDCP and PC5-U. + +#### 5.2.2.3 Signaling between UE and LMF + +The potential impact to LPP for the support of sidelink positioning procedures between UE and LMF is studied. + +Protocol between UE and LMF for hybrid PC5+Uu positioning and PC5-only positioning in-coverage will be down-selected from the following options during normative work. + +- Extension of LPP, whereby new signaling is to be defined to support hybrid Uu and PC5 based positioning, i.e., extend the existing LPP to support sidelink based positioning between UE and LMF +- Enhancement of LPP whereby SLPP signaling can be transported within LPP transparently, i.e., use the newly defined SLPP to support sidelink based positioning and use the existing LPP to support Uu based positioning; and the SLPP is carried as a container in LPP +- Use of SLPP between the UE and the LMF + +The details of functionalities of LMF for supporting SL positioning will be discussed in normative work. + +## 5.3 Summary of sidelink positioning evaluations + +### 5.3.1 Evaluation of bandwidth requirements to meet identified accuracy requirements + +The methodology for the evaluation of SL positioning can be found in Annex A.1. + +The performance analysis for Rel-18 SL positioning shows that, with increasing of bandwidth of SL PRS, the positioning accuracy improves for both absolute positioning and relative positioning/ranging for all evaluated scenarios. + +For V2X use case in highway scenario, 14 sources ([19], [20], [21], [22], [23], [24], [26], [27], [29], [30], [31], [32], [33], [78]) provided simulation results for FR1, and 2 sources ([27], [32]) provided simulation results for FR2. + +- For absolute horizontal accuracy, the results were provided by 14 sources. 12 out of 14 sources show that, the target requirement Set A can be achieved, and 9 out of 14 sources show that the target requirement Set B cannot be achievable even with 100MHz. +- The requirement 1.5m@90% (Set A) + - is achieved with 20MHz bandwidth in contributions from 2 sources ([19], [24]), + - where Joint Uu/SL positioning is used in contributions from ([19], [24]) + - and is achieved with at least 40MHz bandwidth in contributions from 4 sources ([19], [22], [27], [29]), + - where SL-only positioning is used in contribution from ([19]) + +- and is achieved with at least 100MHz bandwidth in contributions from 8 sources ([20], [21], [23], [24], [26], [78], [32], [33]), + - where SL-only positioning is used in contribution from ([24]) + - where SL-TDOA technique is used in contribution from ([26]) +- and is NOT achieved with 100MHz bandwidth in contributions from 3 sources ([26], [30], [31]) + - where two anchors SL AoA technique is used in contribution from ([26]) +- and is achieved with 200MHz bandwidth in FR2 in contribution from 1 source ([32]). +- The requirement 0.5m@90% (Set B) + - is achieved with at least 100MHz in contributions from 5 sources ([19], [22], [24], [29], [78]), + - where Joint Uu/SL positioning is used in contribution from ([24]) + - and is NOT achieved with 100MHz bandwidth in FR1 or 400MHz in FR2 in contributions from 9 sources ([20], [21], [23], [24], [26], [30], [31], [32], [33]), + - where SL-only positioning is used in contribution from ([24]) + - and is NOT achieved with 200MHz bandwidth in FR2 in contribution from 1 source ([32]) + - and is achieved with 400MHz bandwidth in FR2 in contribution from 1 source ([27]). +- For absolute vertical accuracy, the results were provided by 1 source out of 14 sources. + - The requirement 3m@90% (Set A) + - is achieved with at least 100MHz bandwidth by using Joint Uu/SL positioning in contribution from 1 source ([24]) + - and is NOT achieved with 100MHz bandwidth by using SL-only positioning in contribution from 1 source ([24]). + - The requirement 2m@90% (Set B) + - is achieved with 100MHz bandwidth by using Joint Uu/SL positioning in contribution from 1 source ([24]) + - and is NOT achieved with 100MHz bandwidth by using SL-only positioning in contribution from 1 source ([24]). +- For relative horizontal accuracy, the results were provided by 7 sources out of 14 sources. The performance of relative horizontal accuracy is worse than that of distance accuracy of ranging mainly due to additional angle estimation error. 5 out of 7 sources show Set A can be achieved with at least 100MHz especially for the cases with smaller X values or RSU assist, and 5 out of 7 sources show that Set A cannot be met with 100MHz PRS bandwidth especially for the cases with larger X values or without RSU assist. All 7 sources show Set B cannot be met even by 100MHz in the case without RSU-UE positioning. + - The requirement 1.5m@90% (Set A) + - is achieved with 20MHz bandwidth in contribution from 1 source ([26]) + - X = 25m in contribution from ([26]) where RSU deployment is used for performing relative positioning + - is achieved with at least 40MHz bandwidth in contributions from 2 sources ([19], [22]) + - X = 20m in contribution from ([22]) + - X = 50m in contribution from ([19]) where RSU deployment is additionally used for performing relative positioning + +- and is achieved with at least 100MHz bandwidth in contributions from 5 sources ([19], [22], [24], [26], [32]) + - X = 25m in contribution from ([22]) + - X = 50m in contribution from ([24]) + - X = 25m, 50m and 100m in contribution from ([26]) where RSU deployment is used for performing relative positioning + - X = 150m in contributions from ([19]), where BS or RSU deployment is additionally used for performing relative positioning + - X = 200m in contribution from ([32]) +- and is NOT achieved with 100MHz bandwidth in contributions from 5 sources ([19], [20], [22], [23], [24]) + - X = 50m and 150m in contribution from ([19]) + - X = 25m, 50m, and 100m in contribution from ([20]) + - X = 100m and 150m in contribution from ([22]) + - X = 50m, 100m and 150m in contribution from ([23]) + - X = 150m and 300m in contribution from ([24]) +- The requirement 0.5m@90% (Set B) + - is achieved with at least 100MHz bandwidth in contributions from 2 sources ([19], [26]) + - X = 50m in contribution from ([19]) where RSU deployment is additionally used for performing relative positioning + - X = 25m in contribution from ([26]) where RSU deployment is used for performing relative positioning + - is NOT achieved with 100MHz bandwidth in FR1 or 400MHz in FR2 in contributions from 7 sources ([19], [20], [22], [23], [24], [26], [32]). +- For distance accuracy of ranging, the results were provided by 12 out of 14 sources. 7 out of 12 sources show that the target requirement Set A can be achievable by 20MHz, and 7 out of 12 sources show that the target requirement Set B cannot be achieved with 100MHz bandwidth. +- The requirement 1.5m@90% (Set A) + - is achieved with 20MHz bandwidth in contributions from 5 sources ([19], [20], [22], [24], [27]) + - X = 50m and 150 in contribution from ([19]) + - X = 25m, 50m, and 100m in contribution from ([20]) + - X = 100m and 150m in contribution from ([22]) + - X = 50m, 100m, 150m, 200m and 300m in contribution from ([24]) + - X = 80m and 160m in contribution from ([27]) + - and is achieved with at least 40MHz bandwidth in contribution from 2 sources ([22], [23]) + - X = 20m and 25m in contribution from ([22]) + - X = 50m in contribution from ([23]) + - and is achieved with at least 100MHz bandwidth in contributions from 7 sources ([21], [23], [26], [30], [31], [32]) + +- X = 50m, 100m and 150m in contribution from ([21]) +- X = 50m in contribution from ([23]) +- X = 100m in contribution from ([26]) +- X = 200 m in contribution from ([30], [32]) +- X = 50m and 100m in contribution from ([31]). +- The requirement 0.5m@90% (Set B) + - is achieved with at least 40MHz in contributions from 2 sources ([19], [20]) + - X = 50m in contribution from ([19]) + - X = 25m, 50m, and 100m in contribution from ([20]) + - and is achieved with at least 100MHz in contributions from 4 sources ([19], [22], [23], [24]) + - X = 150m in contribution from ([19]) + - X = 25m, 100m and 150m in contribution from ([22]) + - X = 50m in contribution from ([23]) + - X = 50m, 100m, 150m, 200m and 300m in contribution from ([24]) + - and is NOT achieved with 100MHz bandwidth in contributions from 7 sources ([21], [23], [26], [27], [30], [31], [32]) + - X = 50m, 100m and 150m in contribution from ([21]) + - X = 100m and 150m in contribution from ([23]) + - X = 100 m in contribution from ([26]) + - X = 80m and 160m in contribution from ([27]) + - X = 200 m in contributions from ([30], [32]) + - X = 50m and 100m in contribution from ([31]) + - and is achieved with at least 200MHz in FR2 in contribution from 1 source ([32]) + - X = 200 m in contribution from ([32]). +- For angle accuracy of ranging, the results were provided by 6 sources out of 14 sources. All 6 sources show that both the target requirement Set A and Set B can be achieved by 20MHz. + - The requirement 15°@90% (Set A) + - is achieved with 20MHz bandwidth in contributions from 6 sources ([19], [20], [22], [23], [24], [26]), + - X = 50m and 150m in contribution from ([19]), where RSU deployment is additionally used for X=150m for performing ranging + - X = 25m, 50m, and 100m in contribution from ([20]) + - X = 20m, 100m and 150m in contribution from ([22]) + - X = 50m, 100m and 150m in contribution from ([23]). + - The requirement 8°@90% (Set B) + - is achieved with 20MHz in contributions from 4 sources ([19], [23], [24], [26]) + - X = 50m and 150m in contribution from ([19]), where RSU deployment is additionally used for X=150m for performing ranging + +- X = 50m, 100m and 150m in contribution from ([23]) +- and is achieved with at least 40MHz in contributions from 2 sources ([20], [22]) +- X = 50m, and 100m in contribution from ([20]) +- X = 20m, 100m and 150m in contribution from ([22]). +- NOTE: For each SL PRS bandwidth, the above observations are based on the best performance from each source. +- NOTE: For the relative positioning accuracy or distance accuracy of ranging, X is the maximum distance between UEs for performing relative positioning or ranging. +- NOTE: Super resolution is used by sources ([19], [20], [22], [23], [24], [26], [27], [31], [32]), and is not used by sources ([21], [27], [29], [78], [30]). + +For V2X use case in Urban grid scenario, 11 sources ([19], [20], [21], [22], [23], [24], [25], [26], [30], [31], [32]) provided simulation results for FR1, and 1 source ([32]) provided simulation results for FR2. + +- For absolute horizontal accuracy, the results were provided by 9 out of 11 sources. 7 out of 9 sources show that target requirements Set A cannot be achieved with 100 MHz, and 9 sources show that target requirements Set B cannot be achieved with 100 MHz. +- The requirement 1.5m@90% (Set A) + - is achieved with 100MHz by using Joint Uu/SL positioning in contribution from 3 sources ([24], [30], [32]), + - where LOS-only links are used in contribution from ([32]) + - and is NOT achieved with 100MHz bandwidth in contributions from 7 sources ([19], [20], [21], [22], [24], [26], [31]) + - where SL-only positioning is used in contribution from ([24]) + - where two anchors SL AOA positioning is used in contribution from ([26]). +- The requirement 0.5m@90% (Set B) + - is achieved with at least 100MHz by using Joint Uu/SL positioning in contribution from 1 source ([24]), + - and is NOT achieved with 100MHz bandwidth in FR1 or 400MHz in FR2 in contributions from 9 sources ([19], [20], [21], [22], [24], [26], [30], [31], [32]) + - where SL-only positioning is used in contribution from ([24]) + - where LOS-only links are used in contribution from ([32]). +- For Relative horizontal accuracy, the results were provided by 6 out of 11 sources. The performance of relative horizontal accuracy is worse than that of distance accuracy of ranging mainly due to additional angle estimation error. 5 out of 6 sources show that the target requirement Set A can be achieved by 100MHz especially for the cases with smaller X values. All 6 sources show that the target requirement set B is not achieved even by 100MHz. +- The requirement 1.5m@90% (Set A) + - is achieved with 20MHz bandwidth in contribution from 2 sources ([26], [32]) + - X = 25m and 50m in contribution from ([26]) where RSU deployment is used for performing relative positioning + - X = 250m and LOS-only links are used in contribution from ([32]) + - and is achieved with at least 100MHz bandwidth in contributions from 4 sources ([19], [22], [23], [26]) + +- X = 10m and 50m in contribution from ([19]) +- X = 10m in contributions from ([22], [23]) +- X = 25m, 50m and 100m in contribution from ([26]) +- and is NOT achieved with 100MHz bandwidth in contributions from 3 sources ([20], [22], [23]) + - X = 10m, 25m, and 50m in contribution from ([20]) + - X = 25m in contribution from ([22]) + - X = 50m in contribution from ([23]). +- The requirement 0.5m@90% (Set B) + - is achieved with at least 100MHz bandwidth in contribution from 1 source ([26]) + - X = 25m in contribution from ([26]) where RSU deployment is used for performing relative positioning + - is NOT achieved with 100MHz bandwidth in FR1 or 400MHz in FR2 in contributions from 6 sources ([19], [20], [22], [23], [26], [32]) + - X = 10m, 30m and 50m in contribution from ([23]) + - X = 50m and 100m in contribution from ([26]) where RSU deployment is used for performing relative positioning + - X = 250m and LOS-only links are used in contribution from ([32]). +- For distance accuracy of ranging, the results were provided by 11 sources. 6 out of 11 sources show that the target requirement Set A can be achieved by 20MHz or 40MHz. 7 out of 11 sources show that the target requirement Set B cannot be achieved by 100MHz. +- The requirement 1.5m@90% (Set A) + - is achieved with at least 20MHz in contributions from 4 sources ([20], [22], [26], [32]) + - X = 25m in contribution from ([20]) + - X = 25m in contribution from ([22]) + - X = 100m in contribution from ([26]) + - X = 250m in contribution from ([32]) where RSU deployment is additionally used for performing distance ranging and LOS-only links are used + - and is achieved with at least 40MHz in contributions from 2 sources ([24], [25]) + - X = 20m and 30m in contribution from ([24]) + - X = 20m, 50m and 100m in contribution from ([25]) + - and is achieved with at least 100MHz in contributions from 4 sources ([19], [21], [23], [30]) + - X = 10 and 50m in contribution from ([19]) + - X = 50m, 100m and 150m in contribution from ([21]) + - X = 10m and 30m in contribution from ([23]) + - X = 30m in contribution from ([30]) + - and is NOT achieved with 100MHz bandwidth in contributions from 3 sources ([20], [24], [31]) + - X = 50m and 100m in contribution from ([20]) + +- X = 50m, 80m and 100m in contribution from ([24]) +- X = 50m, 100m in contribution from ([31]) +- and is achieved with at least 200MHz in FR2 in contribution from 1 source ([32]) + - where LOS-only links are used in contribution from ([32]). +- The requirement 0.5m@90% (Set B) + - is achieved with at least 20MHz in contribution from 1 source ([32]) + - X = 250m and LOS-only links are used in contribution from ([32]) + - and is achieved with at least 100MHz in contributions from 4 sources ([19], [22], [23], [25]) + - X = 10m and 50m in contribution from ([19]) + - X = 10m and 25m in contribution from ([22]) + - X = 10m in contribution from ([23]) + - X = 20m, 50m, 100m in contribution from ([25]) + - and is NOT achieved with 100MHz bandwidth in FR1 or 400MHz in FR2 in contributions from 7 sources ([20], [21], [23], [24], [26], [30], [31]) + - X = 30m and 50m in contribution from ([23]) + - X = 30m in contribution from ([30]) + - and is NOT achieved with at least 200MHz in FR2 in contribution from 1 source ([32]) + - where LOS-only links are used in contribution from ([32]). +- For angle accuracy of ranging, the results were provided by 6 out of 11 sources. 5 out of 6 sources show that the target requirement Set A can be achieved with 20MHz or 40MHz, and 4 out of 6 sources show that the target requirement Set B cannot be achieved with 100MHz. +- The requirement 15°@90% (Set A) + - is achieved with 20MHz in contributions from 4 sources ([19], [23], [25], [26]) + - X = 10 and 50m in contribution from ([19]) + - X = 10m, 30m and 50m in contribution from ([23]) + - Optional antenna configuration is used and X = 20m in contribution from ([25]) + - X = 50m and 100m in contribution from ([26]) + - and is achieved with 40MHz in contributions from 2 sources ([22], [25]) + - X = 10m and 25m in contribution from ([22]) + - Optional antenna configuration is used and X = 50m or 100m in contribution from ([25]) + - and is NOT achieved with 100MHz bandwidth in contributions from 2 sources ([20], [25]). +- The requirement 8°@90% (Set B) + - is achieved with 20MHz in contribution from 1 source ([26]) + - X = 50m and 100m in contribution from ([26]) + - and is achieved with 40MHz in contribution from 1 source ([19]) + - X = 10m and BS is additionally used for performing ranging in contribution from ([19]) + +- and is achieved with at least 100MHz in contribution from 3 sources ([19], [23], [25]) + - X = 10m and 50m in contribution from ([19]) + - X = 10m and 30m in contribution from ([23]) + - Optional antenna configuration is used and X = 20m in contribution from ([25]) +- and is NOT achieved with 100MHz bandwidth in contributions from 4 sources ([20], [22], [23], [25]) + - X = 50m in contribution from ([23]). +- NOTE: For each SL PRS bandwidth, the above observations are based on the best performance from each source. +- NOTE: For the relative positioning accuracy or distance accuracy of ranging, X is the maximum distance between UEs for performing relative positioning or ranging. +- NOTE: Super resolution is used by sources ([19], [20], [22], [23], [24], [25], [26], [31], [32]), and is not used by sources ([21], [30]). + +For Public safety use case, 3 sources ([19], [24], [30]) provided simulation results for FR1. + +- For absolute horizontal positioning accuracy, the results were provided by 3 sources. + - The requirement 1m@90% + - is achieved with at least 100MHz in contribution from 1 source ([24]) + - is NOT achieved with at least 40MHz in contribution from 1 source ([30]) + - and is NOT achieved with 100MHz in contribution from 1 source ([19]). +- For Relative horizontal accuracy, the results were provided by 1 out of 3 sources. + - The requirement 1m@90% + - is achieved with at least 100MHz in contribution from 1 source ([19]) + - X = 20m in contribution from ([19]). +- For distance accuracy of ranging, the results were provided by 3 sources. + - The requirement 1m@90% + - is achieved with at least 40MHz in contribution from 1 source ([19]) + - X = 20m in contribution from ([19]) + - is achieved with at least 100MHz in contribution from 1 source ([24]) + - X = 50m and 100m in contribution from ([24]) + - is NOT achieved with at least 40MHz in contribution from 1 source ([30]). +- For angle accuracy of ranging, the results were provided by 2 out of 3 sources. + - The requirement 15°@90% (Set A) + - is achieved with at least 10MHz in contribution from 1 source ([19]) + - X = 20m in contribution from ([19]) + - is achieved with 20MHz in contribution from 1 source ([30]). + - The requirement 8°@90% (Set B) + +- is achieved with at least 20MHz in contribution from 1 source ([19]) + - $X = 20\text{m}$ in contribution from ([19]) +- is NOT achieved with 40MHz in contribution from 1 source ([30]). +- NOTE: for each SL PRS bandwidth, the above observations are based on the best performance from each source. +- NOTE: for the relative positioning accuracy or distance accuracy of ranging, $X$ is the maximum distance between UEs for performing relative positioning or ranging. +- NOTE: Super resolution is used by sources ([19], [24]), and is not used by source ([30]). + +For Commercial use case, 5 sources ([19], [24], [25], [31], [32]) provided simulation results for FR1. + +- For absolute horizontal positioning accuracy, the results were provided by 3 out of 5 sources. + - The requirement 1m@90% + - is achieved with 40MHz in contribution from 1 source ([19]) + - and is achieved with at least 100MHz in contribution from 2 sources ([24], [30]). +- For Relative horizontal accuracy, the results were provided by 1 out of 5 sources. + - The requirement 1m@90% + - is achieved with 40MHz bandwidth in contribution from 1 source ([19]), where anchor UE deployment is additionally used for performing distance ranging + - and is achieved with 100MHz bandwidth in contribution from 1 source ([19]) + - $X = 10\text{m}$ in contribution from ([19]). +- For distance accuracy of ranging, the results were provided by 4 out of 5 sources. All 4 sources show that the target requirement set can be achievable by 100MHz especially for the cases with smaller $X$ values. + - The requirement 1m@90% + - is achieved with at least 20MHz in contribution from 1 source ([25]) + - $X = 10\text{m}$ in contribution from ([25]) + - is achieved with at least 40MHz in contribution from 2 sources ([19], [25]) + - $X = 10\text{m}$ in contribution from ([19]) where anchor UE deployment is additionally used for performing ranging + - $X = 20\text{m}$ and $50\text{m}$ in contribution from ([25]) + - is achieved with at least 100MHz in contribution from 3 sources ([19], [24], [31]) + - $X = 10\text{m}$ in contributions from ([19], [24], [31]) + - and is NOT achieved with at least 100MHz in contribution from 2 sources ([24], [31]) + - $X = 20\text{m}$ , $50\text{m}$ , and $100\text{m}$ in contribution from ([24]) + - $X = 25\text{m}$ and $50\text{m}$ in contribution from ([31]). +- For angle accuracy of ranging, the results were provided by 1 out of 5 sources. + - The requirement 15°@90% (Set A) + - is achieved with at least 20MHz in contribution from 1 source ([19]) + - $X = 10\text{m}$ in contribution from ([19]). + +- The requirement 8°@90% (Set B) + - is achieved with at least 40MHz in contribution from 1 source ([19]) + - X = 10m in contribution from ([19]). +- NOTE: for each SL PRS bandwidth, the above observations are based on the best performance from each source. +- NOTE: for the relative positioning accuracy or distance accuracy of ranging, X is the maximum distance between UEs for performing relative positioning or ranging. +- NOTE: Super resolution is used by sources ([19], [24], [25], [31]), and is not used by source ([30]). + +For IIOT use case in InF-SH scenario, 9 sources ([18], [19], [20], [21], [22], [24], [28], [31], [32]) provided simulation results for FR1, and 1 source ([32]) provided simulation results for FR2. + +- For absolute horizontal positioning accuracy, the results were provided by 8 out of 9 sources. 5 out of 8 sources show that the target requirements Set A can be achieved with at least 100MHz, and 5 out of 8 sources show that the target requirements Set B cannot be achieved with 100MHz. + - The requirement 1m@90% (Set A) + - is achieved with 20MHz in contributions from 1 source ([19]) + - where Joint Uu/SL positioning is used in contribution from ([19]) + - is achieved with 40MHz in contributions from 2 sources ([19], [20]) + - where SL-only positioning is used in contribution from ([19]) + - is achieved with at least 100MHz in contributions from 5 sources ([18], [21], [24], [28], [32]) + - where LOS-only links are used in contribution from ([32]) + - and is not achieved with 100MHz bandwidth in contribution from 1 source ([31]). + - The requirement 0.2m@90% (Set B) + - is achieved with at least 40MHz in contribution from 1 source ([19]) + - where Joint Uu/SL positioning is used in contribution from ([19]) + - and is achieved with at least 100MHz in contribution from 2 sources ([19], [20]) + - where SL-only positioning is used in contribution from ([19]) + - and is NOT achieved with 100MHz bandwidth in contributions from 6 sources ([18], [21], [24], [28], ([31], [32]) + - and is achieved with at least 200MHz bandwidth in FR2 in contribution from 1 source ([32]) + - where LOS-only links are used in contribution from ([32]). +- For absolute vertical accuracy, the results were provided by 1 out of 9 sources. + - The requirement 1m@90% (Set A) + - is NOT achieved with 100MHz bandwidth in contribution from 1 source ([28]). + - The requirement 0.2m@90% (Set B) + - is NOT achieved with 100MHz bandwidth in contribution from 1 source ([28]). +- For Relative horizontal accuracy, the results were provided by 3 out of 9 sources. The performance of relative horizontal accuracy is worse than that of distance accuracy of ranging mainly due to additional angle estimation + +error. All 3 sources show Set A can be met with 40MHz or 100MHz PRS bandwidth. All 3 sources show Set B cannot be met even with 100MHz. + +- The requirement 1m@90% (Set A) + - is achieved with at least 40MHz in contributions from 2 sources ([20], [22]) + - X = 10m in contributions from ([20], [22]) + - is achieved with at least 100MHz in contribution from 1 source ([19]) + - X = 10m in contribution from ([19]). +- The requirement 0.2m@90% (Set B) + - is NOT achieved with 100MHz bandwidth in contributions from 3 sources ([19], [20], [22]). +- For distance accuracy of ranging, the results were provided by 5 out of 9 sources. 4 out of 5 sources show that the target requirement Set A can be achievable by 100MHz, and 3 out of 5 sources show that the target requirement Set B cannot be achieved with 100MHz bandwidth. + - The requirement 1m@90% (Set A) + - is achieved with at least 20MHz in contribution from 1 source ([20]) + - X = 10m in contribution from ([20]) + - is achieved with at least 40MHz in contribution from 1 source ([22]) + - X = 10m in contribution from ([22]) + - is achieved with at least 100MHz in contribution from 2 sources ([21], [24]) + - X = 50m, 100m and 150m in contribution from ([21]) + - X = 10m, 20m, 30m and 50m in contribution from ([24]) + - is NOT achieved with at least 100MHz in contribution from 1 source ([31]) + - X = 10m, and 50m in contribution from ([31]). + - The requirement 0.2m@90% (Set B) + - is achieved with at least 100MHz in contribution from 2 sources ([20], [22]) + - X = 10m in contributions from ([20], [22]) + - and is NOT achieved with 100MHz bandwidth in contributions from 3 sources ([21], [24], [31]). +- For angle accuracy of ranging, the results were provided by 2 out of 9 sources. + - The requirement 15°@90% (Set A) + - is achieved with at least 20MHz in contribution from 1 source ([20]) + - X = 10m in contribution from ([20]) + - is achieved with at least 40MHz in contribution from 1 source ([22]) + - X = 10m in contribution from ([22]). + - The requirement 8°@90% (Set B) + - is achieved with at least 20MHz in contribution from 1 source ([20]) + - X = 10m in contribution from ([20]) + - is achieved with at least 40MHz in contribution from 1 source ([22]) + +- X = 10m in contribution from ([22]). +- NOTE: for each SL PRS bandwidth, the above observations are based on the best performance from each source. +- NOTE: for the relative positioning accuracy or distance accuracy of ranging, X is the maximum distance between UEs for performing relative positioning or ranging. +- NOTE: Super resolution is used by sources ([19], [20], [22], [24], [31], [32]), and is not used by sources ([18], [21]). + +For IIOT use case in InF-DH scenario, 7 sources ([18], [19], [20], [24], [28], [30], [32]) provide simulation results for FR1, and 1 source ([32]) provided simulation results for FR2. + +- For absolute horizontal poisoning accuracy, the results were provided by 7 sources. 5 out of 7 sources show that the target requirements Set A can be achieved with 100MHz, and 5 out of 7 sources show that the target requirements Set B cannot be achieved with 100MHz. + - The requirement 1m@90% (Set A) + - is achieved with 20MHz in contribution from 1 source ([19]) + - where Joint Uu/SL positioning is used in contribution from ([19]) + - is achieved with 40MHz in contribution from 2 sources ([19], [20]) + - where SL-only positioning is used in contribution from ([19]) + - and is achieved with at least 100MHz in contributions from 3 sources ([24], [30], [32]) + - where LOS-only links are used in contribution from ([32]) + - and is NOT achieved with 100MHz bandwidth in FR1 in contributions from 2 sources ([18], [28]). + - The requirement 0.2m@90% (Set B) + - is achieved with at least 100MHz in contribution from 2 sources ([19], [20]) + - is NOT achieved with 100MHz bandwidth in FR1 in contributions from 6 sources ([18], [24], [28], [30], [32]) + - and is achieved with at least 200MHz bandwidth in FR2 in contribution from 1 source ([32]) + - where LOS-only links are used in contribution from ([32]). +- For absolute vertical accuracy, the results were provided by 1 out of 7 sources. + - The requirement 1m@90% (Set A) + - is NOT achieved with 100MHz bandwidth in contribution from 1 source ([28]). + - The requirement 0.2m@90% (Set B) + - is NOT achieved with 100MHz bandwidth in contribution from 1 source ([28]). +- For Relative horizontal accuracy, the results were provided by 2 out of 7 sources. + - The requirement 1m@90% (Set A) + - is achieved with at least 40MHz in contribution from 1 source ([20]) + - X = 10m in contribution from ([20]) + - is achieved with at least 100MHz in contribution from 1 source ([19]) + - X = 10m in contribution from ([19]). + +- The requirement 0.2m@90% (Set B) in InF-DH + - is NOT achieved with 100MHz bandwidth in contribution from 2 sources ([19], [20]). +- For distance accuracy of ranging, the results were provided by 2 out of 7 sources. + - The requirement 1m@90% (Set A) + - is achieved with at least 20MHz in contribution from 1 source ([20]) + - $X = 10\text{m}$ in contribution from ([20]) + - is achieved with at least 100MHz in contribution from 1 source ([24]) + - $X = 10\text{m}$ in contribution from ([24]) + - and is NOT achieved with at least 100MHz in contribution from 1 source ([24]) + - $X = 20\text{m}$ , $30\text{m}$ , and $50\text{m}$ in contribution from ([24]). + - The requirement 0.2m@90% (Set B) + - is achieved with at least 100MHz in contribution from 1 source ([20]) + - $X = 10\text{m}$ in contribution from ([20]) + - and is NOT achieved with 100MHz bandwidth in contribution from 1 source ([24]). +- For angle accuracy of ranging, the results were provided by 1 out of 7 sources. + - The requirement 15°@90% (Set A) + - is achieved with at least 20MHz in contribution from 1 source ([20]) + - $X = 10\text{m}$ in contribution from ([20]). + - The requirement 8°@90% (Set B) + - is achieved with at least 40MHz in contribution from 1 source ([20]) + - $X = 10\text{m}$ in contribution from ([20]). +- NOTE: for each SL PRS bandwidth, the above observations are based on the best performance from each source. +- NOTE: for the relative positioning accuracy or distance accuracy of ranging, $X$ is the maximum distance between UEs for performing relative positioning or ranging. +- NOTE: Super resolution is used by sources ([19], [20], [24], [32]), and is not used by sources ([18], [30]). + +### 5.3.2 Evaluation of absolute positioning, relative positioning, and ranging methods + +The performance analysis for Rel-18 SL positioning shows that different SL positioning methods can be used to determine absolute position of a target UE: + +- Simulation results for SL positioning based on SL-TDOA were reported in contributions from 13 sources ([18], [21], [22], [23], [24], [26], [27], [28], [29], [30], [31], [32], [78]). +- Simulation results for SL positioning based on SL-RTT (multi-RTT) were reported in contributions from 6 sources ([19], [20], [27], [28], [29], [30]). +- Simulation results based on two anchors SL-AOA were provided in contribution from 1 source ([26]). + +For absolute positioning, 5 sources ([19], [24], [30], [32], [33]) provide simulation results for Joint Uu-SL absolute positioning. + +- For V2X use case, 4 sources ([19], [24], [32], [33]) show performance improvement of Joint Uu-SL absolute positioning compared to SL-only positioning. + +- For V2X use case, 2 sources ([32], [33]) show performance improvement of Joint Uu-SL absolute positioning compared to Uu-only positioning. +- For IIOT use case, 3 sources ([19], [24], [32]) show performance improvement of Joint Uu-SL absolute positioning compared to SL-only positioning. +- For IIOT use case, 3 sources ([24], [30], [32]) show performance improvement of Joint Uu-SL absolute positioning compared to Uu-only positioning. +- For Public safety, 1 source ([24]) shows performance improvement of Joint Uu-SL absolute positioning compared to SL-only or Uu-only positioning. +- For commercial use case, 1 source ([24]) shows performance improvement of Joint Uu-SL absolute positioning compared to SL-only positioning. +- For commercial use case, 2 sources ([24], [30]) show performance improvement of Joint Uu-SL absolute positioning compared to Uu-only positioning. + +The performance analysis for Rel-18 SL positioning shows that, SL positioning methods can be used for relative positioning/ ranging between UEs. For relative positioning/ ranging positioning accuracy, + +- Simulation results based on SL-RTT and/or AOA were provided in contributions from 12 sources ([19], [20], [21], [22], [23], [24], [25], [26], [27], [30], [31], [33]). +- Results based SL-TDOA were provided in contribution from 1 source ([32]). + +Simulation results in contributions from 9 sources ([19], [20], [22], [23], [24], [25], [26], [27], [31]) show that relative horizontal accuracy and/or distance accuracy of ranging performance improves with decreasing values of X, where X is the maximum distance between two UEs for performing relative positioning or ranging. + +- In some simulation cases, for a certain SL PRS bandwidth, a target requirement may be achieved for a smaller value of X but may not be achieved for a larger value of X. +- In some simulation cases, a target requirement may be achieved using a smaller SL PRS bandwidth for a smaller value of X but may only be achieved using a larger SL PRS bandwidth for a larger value of X. + +From the reported simulation results, it is observed that SL absolute positioning performance may be degraded due to uncertainty in the anchor UEs' location coordinates and synchronization error (for SL-TDOA) between anchor UEs. + +## 5.4 Potential specification impact for sidelink positioning + +The following summarizes the key areas of potential specification impact from RAN1's perspective that have been identified for the support of solutions for sidelink positioning: + +- Specification changes to support the following two operation scenarios: + - Operation Scenario 1: PC5-only-based positioning. + - Operation Scenario 2: Combination of Uu- and PC5-based positioning. +- Specification changes to introduce: + - RTT-type solution(s) using SL, SL-AoA, SL-TDOA (where DL-TDOA-like operation and UL-TDOA-like operation are included). + - At least the following measurements: SL PRS based Rx-Tx measurement, SL PRS based RSTD measurement, SL PRS based RSRP measurement, SL PRS based RSRPP measurement, SL PRS based RTOA measurement, SL PRS based Azimuth of Arrival (AoA) and SL Zenith of Arrival (ZoA) measurement. + - A new sidelink reference signal (SL PRS), including details of sequence design, physical structure, resource mapping. + +- Support of unicast, Groupcast (not including many to one) and Broadcast of SL PRS transmissions, +- Support of SCI to be used for reserving/indicating one or more SL PRS resources. +- SL PRS resource allocation Scheme 1 and Scheme 2, where Scheme 1 corresponds to a network-centric resource allocation, and Scheme 2 corresponds to UE autonomous SL PRS resource allocation, and potential mechanisms for SL PRS resource coordination. +- SL PRS transmission in dedicated resource pool or shared resource pool that may be shared with Rel-16/Rel-17/Rel-18 SL communication. +- Support of Open Loop Power Control (OLPC) for SL PRS transmissions. +- Details of sidelink positioning measurement reporting. + +RAN2 identified that there is potential specification impact for sidelink positioning including: + +- Introduction of a new protocol for sidelink positioning procedures between UEs, with where it is specified to be determined during normative work. +- The new protocol is a separate ASN.1 module from LPP (this does not necessarily imply whether it is included in TS 37.355 [16]). +- Options for signaling between LMF and UE will be downselected during normative work. + +From the perspective of NG-RAN interface, the following have been identified to have potential specification impact for support of sidelink positioning: + +- Support of sidelink positioning and ranging service authorizations signaling to NG-RAN as needed. + +# --- 6 Positioning enhancements for improved integrity, accuracy, and power efficiency + +## 6.1 Integrity for RAT-dependent positioning techniques + +### 6.1.0 Study objectives + +The following objectives of the study on solutions for integrity for RAT-dependent positioning techniques are listed in the SID [7]: + +- Identification of the error sources. +- Study of methodologies, procedures, signaling, etc for determination of positioning integrity for both UE-based and UE-assisted positioning. +- Reuse of concepts and principles developed for RAT-Independent GNSS positioning integrity are to be prioritized, when possible. + +### 6.1.1 Identification of error sources + +Sources of error for RAT-dependent positioning techniques are studied for timing-based and angle-based positioning methods focussing on the origin of the error source, the model of the error source, criteria for consideration as an error source, and mapping between an error source and a positioning method (e.g., DL, UL, DL&UL positioning method). + +UE-based/assisted DL positioning methods, UL and DL&UL positioning methods are considered in the study. + +For timing-based positioning methods, the following error sources are studied: + +- TRP/UE measurements errors (e.g., ToA, Rx-Tx timing difference) + +- Error in assistance data (e.g., TRP location, Inter-TRP synchronization errors (e.g., RTD)) +- TRP/UE Timing error +- Identification of error sources resulting from the multipath/NLoS channel/radio propagation environment, including multipath/NLoS channel itself as an error source, can be considered further during normative work. + +For angle-based positioning methods, the following error sources are studied: + +- TRP/UE measurements errors (e.g., AoA, RSRP, RSRPP) +- Error in assistance data (e.g., TRP location, TRP beam antenna information) +- Identification of error sources resulting from the multipath/NLoS channel/radio propagation environment, including multipath/NLoS channel itself as an error source, can be considered further during normative work. + +For UE-based positioning integrity mode, whether boresight direction of DL PRS (*NR-DL-PRS-BeamInfo* in TS 37.355 [16]) and/or beam information (*NR-TRP-BeamAntennaInfo* in TS 37.355 [16]) of DL PRS can be error sources can be considered further during normative work, focusing at least on the following aspects: + +- Granularity of boresight direction of DL-PRS and its influence on positioning integrity +- Feasibility and complexity of modelling +- Feasibility of obtaining quality/statistical parameters of beam information from the gNB +- Influence on measurement errors at the UE. + +For DL AoD, whether DL PRS RSRP/RSRPP measurement can be an error source is studied, focusing at least on the following aspect: + +- Impact of RSRP/RSRPP measurement on positioning accuracy. + +For LMF-based positioning integrity mode, whether System Frame Number (SFN) initialization time is an independent error source for UL-TDOA or UE-assisted DL-TDOA is studied. + +Table 6.1.1-1 presents the identified error sources for LMF-based and UE-based positioning integrity modes for different positioning methods. + +Table 6.1.1-1: Error sources for LMF-based and UE-based positioning integrity modes + +| Positioning Integrity Mode | DL TDOA | UL TDOA | Multi-RTT | UL AoA | DL AoD | +|------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------| +| LMF-based (as defined in Table 9.4.1.1.1 in TR 38.857 [2]) |
  • - RSTD measurement
  • - TRP location
  • - Inter-TRP synchronization (can be caused in part by errors in SFN initialization time.)
|
  • - RTOA measurement
  • - TRP location
  • - Inter-TRP synchronization (can be caused in part by errors in SFN initialization time.)
|
  • - UE Rx-Tx time difference measurement
  • - gNB Rx-Tx time difference measurement
  • - TRP location
|
  • - Angle of arrival measurement
  • - TRP location
  • - ARP location (e.g., ARPLocationInformation in TS 38.455 [17])
|
  • - TRP location
  • - DL-PRS RSRPP of the first path or RSRP
| +| UE-based (as defined in Table 9.4.1.1.1 in TR 38.857 [2]) |
  • - TRP location (e.g., NR-TRP-LocationInfo in TS 37.355 [16])
  • - Inter-TRP synchronization (e.g., NR-RTD-Info in TS 37.355 [16])
| | | |
  • - TRP location (e.g., NR-TRP-LocationInfo in TS 37.355 [16])
| + +The distributions of RSTD, RTOA, and UE/gNB Rx-Tx time difference measurement errors are studied considering the following aspects: + +- Whether TEG-related timing error is an independent error source from timing related measurement error (e.g., RTOA, RSTD, UE/gNB Rx-Tx time difference) +- Whether the measurement error is considered for each ToA or for the reported RSTD value +- Other Details (e.g., mean and standard deviation). + +The distribution of angle of arrival measurement error is studied considering the following aspects: + +- Whether the angle of arrival measurement error can be expressed as the error of the AoA/ZoA in LCS or GCS or the error of a defined function of AoA/ZoA in LCS +- Distribution of AoA measurement error for an NLOS/LOS link +- Other Details (e.g., mean, standard deviation). + +The following alternatives for expression of angle of arrival measurement error for determination of positioning integrity for UL AoA are studied with the aim of eventual down-selection: + +- Alt. 1: No conversion (e.g., the measurement error is expressed as error in AoA or ZoA in LCS/GCS) +- Alt. 2: Conversion function (defined as function of AoA/ZoA in LCS). + +Table 6.1.1-2 presents the choices of statistical distributions of the errors for the identified error sources. + +**Table 6.1.1-2: Identified candidates for distributions to model the errors due to different error sources** + +| Error source | Candidate(s) for distribution for error source | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------| +| Timing measurement errors (NOTE 1, 2, 3) | Gaussian distribution | +| Inter-TRP synchronization errors |
  • - Uniform distribution (NOTE 4)
  • - Gaussian distribution
| +| TRP location error (e.g., NR-TRP-LocationInfo in [16]) |
  • - Uniform distribution (NOTE 5)
  • - Gaussian distribution
| +| TRP location error (e.g., Geographical coordinates in [17]) |
  • - Uniform distribution
  • - Gaussian distribution
| +| ARP location error (e.g., ARPLocationInformation in [17]) |
  • - Uniform distribution
  • - Gaussian distribution
| +| NOTE 1: Timing measurement errors are applicable to RSTD, RTOA and UE/gNB Rx-Tx time difference measurements.
NOTE 2: It is assumed that the timing measurement error is associated with the first path.
NOTE 3: It is assumed that the timing measurement error contains TEG related TX/RX timing error if the TEG related information is provided
NOTE 4: This may already be consistent with the uncertainty related to NR-RTD-Info in [16].
NOTE 5: This may already be consistent with the uncertainty related to NR-TRP-LocationInfo in [16]. | | + +### 6.1.2 Methodologies, procedures and signaling for determination of positioning integrity + +#### 6.1.2.1 Integrity principle of operation + +Reuse the concepts and principles developed for RAT-Independent GNSS positioning integrity for RAT-Dependent positioning integrity. + +Both UE-based and LMF-based integrity for RAT-dependent cases are studied and supported in integrity for RAT-dependent positioning. + +Use DNU flag for RAT-dependent integrity, with the meaning that the concerned assistance data cannot be used for integrity calculation but may be usable for positioning. Signaling details and relation to error sources can be determined in normative work. + +#### 6.1.2.2 Signaling for UE-based positioning integrity + +Rel-17 UE-based integrity mode signaling can be used as baseline at least with the following aspects: + +UE sends capability info to LMF on integrity for UE-based mode using LPP capability transfer procedure. + +- LMF sends the assistance data for integrity calculation to UE. LMF provides, in assistance data, the information of error sources (e.g., originated from RAN node) to UE for integrity in UE-based mode. +- LMF sends integrity requirement e.g., TIR to UE in LPP request location information message for integrity of UE-based mode. +- UE sends integrity result to LMF using LPP location information Transfer message. + +#### 6.1.2.3 Signaling for LMF-based positioning integrity + +RAN2 studied LMF-based positioning integrity mode [2], and have identified the following impacts to signaling: + +- UE sends capability info to LMF for LMF-based positioning integrity mode using LPP capability transfer procedure +- LMF sends the request of results related to integrity for integrity error sources to UE for integrity of LMF-based mode +- LMF sends the request of results related to integrity for integrity error sources to RAN for integrity of LMF-based mode + +- RAN sends results related to integrity to LMF using NRPPa message. + +NOTE 1: The signaling to transmit integrity KPI and integrity results can be discussed during normative work. + +NOTE 2: Whether UE sends results related to integrity to LMF using LPP message or not can be discussed during normative work. + +### 6.1.3 Summary of evaluation results for integrity for RAT-dependent positioning techniques + +The distribution of timing measurement error has been studied with evaluations reported by the following sources: [133], [135], [136], [137], [138], [139], [141], and [142]. + +The distribution of angle measurement error has been studied with evaluations reported by the following sources: [133], [134], [135], [137], [138], and [142]. + +Further details on the above can be found in Annex B.2. + +### 6.1.4 Potential specification impact for integrity for RAT-dependent positioning techniques + +For UE-based positioning integrity mode, potential specification impacts related to errors in assistance data (e.g., related to inter-TRP synchronization error and TRP locations) include at least the enhancements to assistance data from the LMF to the UE (e.g., inclusion of parameters related to the error sources). + +Signaling design of both UE-based and LMF-based integrity can be supported. + +## 6.2 PRS / SRS bandwidth aggregation + +### 6.2.0 Study objectives + +In the SID [7], the following is identified as an objective for the study of PRS/SRS bandwidth aggregation towards enabling higher accuracy positioning: + +- Study solutions for accuracy improvement based on PRS/SRS bandwidth aggregation for intra-band carriers considering e.g., timing errors, phase coherency, frequency errors, power imbalance, etc. + +### 6.2.1 Potential solutions based on PRS / SRS bandwidth aggregation + +#### 6.2.1.1 RF aspects + +RF aspects of PRS/SRS bandwidth aggregation for intra-band contiguous carriers is studied by RAN4. Based on the study, PRS/SRS bandwidth aggregation for intra-band contiguous carriers is concluded as feasible for single chain Tx/Rx architectures at both the UE and gNB. + +The assumption for a single-chain Tx architecture is that PRS/SRS resources to be aggregated are transmitted from a single Tx antenna. + +#### 6.2.1.2 RRM aspects + +From the perspective of Radio Resource Management (RRM), the following are assumed for PRS bandwidth aggregation: + +- A common numerology is required across all intra-band contiguous PFLs to be aggregated. +- PRS resources to be aggregated from different PFLs can have different bandwidths (i.e., different number of PRS RBs). +- PRS resources to be aggregated from different PFLs are transmitted in the same slot and in the same symbols. + +- PRS resources to be aggregated from different PFLs are transmitted by the same TRP and associated with a common Antenna Reference Point (ARP). + +From RRM perspective, the following are assumed for SRS bandwidth aggregation: + +- A common numerology is required across all intra-band contiguous carriers to be aggregated. +- SRS resources to be aggregated from different carriers can have different bandwidths (i.e., different number of SRS RBs). +- SRS resources to be aggregated from different carriers are transmitted in the same slot and in the same symbols. + +From RRM perspective, FFT/IFFT size is up to UE implementation. PRS/SRS bandwidth aggregation should allow UE implementation flexibility i.e., single FFT/IFFT or multiple FFTs/IFFTs (i.e., FFT/IFFT per carrier) implementations. + +PRS/SRS bandwidth aggregation may be supported in RRC\_CONNECTED and RRC\_INACTIVE subject to UE capability. + +PRS/SRS bandwidth aggregation across Positioning Frequency Layers (PFLs) for positioning measurements is concluded as feasible from RRM perspective. + +### 6.2.2 Summary of evaluations for PRS/SRS bandwidth aggregation + +RRM impact of possible group delay error between PRS/SRS from different carriers in single RF chain (Tx/Rx) architecture will be considered in RRM requirements during the WI. + +### 6.2.3 Potential specification impact for PRS/SRS bandwidth aggregation + +Specification of RRM requirements including at least PRS measurement period/reporting/accuracy (including margins), and the impacts of PRS measurement on data communication including CA/DC. + +## 6.3 NR carrier phase positioning + +### 6.3.0 Study objectives + +In the SID [7], the following objectives for the study on solutions for accuracy improvement based on NR carrier phase measurements have been identified: + +- Study on reference signals, physical layer measurements, and physical layer procedures to enable positioning based on NR carrier phase measurements for both UE-based and UE-assisted positioning. + +In this study, the reuse of existing PRS and SRS is prioritized, with consideration of new reference signals only if found necessary. + +In the following three clauses, potential solutions, achievable performance, and expected specification impact for support of positioning methods utilizing NR carrier phase measurements are presented. + +For the purposes of discussion, for NR downlink and/or uplink carrier phase positioning, the carrier phase (CP) at a RF frequency at a receiver is a phase that is a function of the signal propagation time from a transmitter antenna reference point of a transmitter (e.g., a TRP or a UE) to a receiver antenna reference point of the receiver (e.g., a UE or a TRP). The propagation time can be expressed in a fractional part of a cycle of the RF frequency and a number of integer cycles, but the CP may be independent of the number of integer cycles. + +### 6.3.1 Potential solutions for NR carrier phase positioning + +#### 6.3.1.1 Reference signals for NR carrier phase positioning + +Existing DL PRS and UL SRS for positioning can be re-used as the reference signals to enable positioning based on NR carrier phase measurements for both UE-based and UE-assisted positioning. Whether to consider enhancements of the + +existing DL PRS and UL SRS for better positioning performance can be considered further. Note that the use of MIMO SRS for positioning purpose is transparent to UE. + +#### 6.3.1.2 Physical layer measurements for NR carrier phase positioning + +The study of the accuracy improvement based on NR carrier phase measurements includes: + +- UE-based and UE-assisted carrier phase positioning +- UL carrier phase positioning and DL carrier phase positioning +- NR carrier phase positioning with the carrier phase measurements of one carrier frequency or multiple frequencies +- Combination of NR carrier phase positioning with another standardized Rel. 17 positioning method, e.g., DL-TDOA, UL-TDOA, Multi-RTT, etc. + +For DL UE-assisted NR carrier phase positioning, at least the following options are considered: + +- The difference between the carrier phase measured from the DL PRS signal(s) of the target TRP and the carrier phase measured from the DL PRS signal(s) of the reference TRP +- The carrier phase measured from the DL PRS signal(s) of a TRP. + +For UL UE-assisted NR carrier phase positioning, at least the carrier phase measured from the UL SRS for positioning purpose is considered. + +#### 6.3.1.3 Physical layer procedures for NR carrier phase positioning + +The impact of integer ambiguity on NR carrier phase positioning and potential solutions to resolve the integer ambiguity when using carrier phase measurements to estimate the propagation delay/distance between transmitting and receiving nodes are studied. + +Benefits of using the carrier phase measurements of multiple DL PFLs for NR carrier phase positioning, which may include the impact of the time gap between the carrier phase measurements of multiple DL PFLs are studied. + +NOTE 1: The initial phase error and the frequency error for each PFL can be modelled independently. + +NOTE 2: For evaluations, the PRSs of all the PFLs of a TRP can be assumed to be transmitted from the same ARP or from different ARPs of the TRP. + +NOTE 3: The location error for ARPs can be modelled independently. + +NOTE 4: The timing errors of the PFLs may not be the same for PFLs in different bands or frequency ranges. + +NOTE 5: In Rel-17, simultaneous reception of DL PRS from multiple frequency layers is not supported. + +The impact of multipath/NLOS on NR carrier phase positioning is evaluated during the study item. Based on the study, it is concluded that multipath/NLOS deteriorates the performance of carrier phase positioning, and it is necessary to consider multipath mitigation for NR carrier phase positioning. + +The effectiveness of the following multipath mitigation methods for NR carrier phase positioning is studied: + +- Identification and separation of the first path and other paths. +- Reporting of the carrier phase of the first path, and optionally, the additional paths. +- The use of LOS/NLOS indication for the carrier phase measurements. + - NOTE: Rel-17 LOS/NLOS indicator can be considered as a starting point. +- The report of other channel information, such as existing RSRP/RSRPP. + +The use of Positioning Reference Unit (PRU) to facilitate NR carrier phase positioning is studied. + +- For DL NR carrier phase positioning, a PRU works as a UE to receive the DL PRS reference signals and provide the DL carrier phase measurements to the LMF, where the double differential measurements can be obtained by the difference of the DL carrier phase measurements from the target UE and those from the PRU for eliminating the measurement errors. +- For UL NR carrier phase positioning, a PRU works as a UE to transmit the UL SRS signals for positioning purpose. The TRPs provide the UL carrier phase measurements obtained from the UL SRS signals of the target UE and of the PRU to the LMF, where the double differential measurements can be obtained by the difference of these UL carrier phase measurements for eliminating the measurement errors. + +The following approaches for NR carrier phase positioning are studied: + +- The reporting of the carrier phase measurements together with the existing positioning measurements. +- The reporting of the carrier phase-based measurements alone without reporting the existing positioning measurements. + +Potential solutions for NR carrier phase positioning are evaluated with the consideration of various error sources, which include phase noise (FR2), carrier frequency offset (CFO)/Doppler, oscillator-drift, transmitter/receiver antenna reference point (ARP) location errors, transmitter/receiver initial phase error, antenna Phase Center Offset (PCO) etc. Detailed evaluation methodology and assumptions are presented in Annex A.3 + +A summary of the evaluation results for the impact of the multipath/NLOS on NR carrier phase positioning are presented in Clause 6.3.2. + +NR carrier phase positioning performance is evaluated at least with the carrier phase measurements of a single measurement instance. + +It should be noted that the use of "carrier phase positioning" does not necessarily imply that it may be defined as a standalone positioning method. + +The potential solutions of integer ambiguity resolution for NR carrier phase positioning were investigated in the study item, which include the following: + +- Reporting of the carrier phases of more than one frequency from UE/TRP to LMF + - NOTE: frequency refers to frequency of carrier or frequency of subcarrier(s) +- Reporting of the determined integer ambiguity and/or the search range of the integer ambiguity from UE/TRP to LMF +- Reporting of the carrier phase measurements together with the legacy positioning measurements from UE/TRP to LMF +- Reporting of the new measurements from UE/TRP to LMF, e.g., based on carrier phase differentials across multiple subcarriers within a carrier + - NOTE: carrier phase differentials across multiple subcarriers within a carrier can be equivalent to time of arrival +- LMF configure the integer ambiguity range between the TRP and target UE (for UE-based NR CPP). + +### 6.3.2 Summary of evaluations for NR carrier phase positioning + +The methodology for the evaluation of NR carrier phase positioning can be found in Annex A.3. + +Evaluations of NR carrier phase positioning were conducted using evaluation assumptions with some differences across sources. Different algorithms and methods are also used for estimating the carrier phases and determining UE's location based on the carrier phases. Thus, for the observations of evaluation results presented in this clause, it is important to consider the details of the evaluation assumptions as well as the algorithms and methods provided by each source in the references (e.g., in Annex B.4). + +The accuracy of NR carrier phase positioning is evaluated under different scenarios (e.g., InF-SH, InF-DH) defined in [11] without considering the error sources listed in Annex A.3 (e.g., timing/ frequency errors, antenna PCO and ARP position errors). The evaluation results can be seen as the reference for studying the impacts of the error sources listed + +in Annex A.3. 9 out of 11 sources ([79], [80], [81], [82], [85], [86], [87], [88], [90]) show that the centimeter-level positioning accuracy can be achieved by the use of carrier phase measurements at least when other error sources are not considered. 2 out of 11 sources ([83], [84]) show that the centimeter-level positioning accuracy can be achieved by the use of ideal resolution of integer ambiguity: + +- Source [79] shows: + - For InF-SH scenario: + - (No differential) UL-CPP (Case 1): <1.0cm @50% and <1.0cm @80%. + - SD UL-CPP (Case 5): <1.0cm @50% and <1.0cm @80%. + - DD DL-CPP (Case 9): <1.0cm @50% and <1.0cm @80%. + - For InF-DH scenario: + - (No differential) UL-CPP (Case 2): <1.0cm @50% and <1.0cm @80%. + - SD UL-CPP (Case 6): <1.0cm @50% and 0.974m @80%. + - DD DL-CPP (Case 10): <1.0cm @50% and 1.014m @80%. +- Source [80] shows: + - For InF-SH scenario: + - SD DL-CPP (Case 102): <1.0cm@50% and <1.0cm @80% + - For InF-DH scenario: + - SD DL-CPP (Case 202): <1.0cm@50% and 0.33m @80% +- Source [81] shows: + - For InF-SH scenario: + - SD DL-CPP (Case 2): <1.0cm @50% and <1.0cm @80%. + - DD DL-CPP (Case 3): <1.0cm @50% and <1.0cm @80%. + - DD DL-CPP (two subcarrier frequencies in one PFL) (Case 4): <1.0cm @50% and <1.0cm @80%. + - DD DL-CPP (two carrier frequencies, two PFLs) (Case 5): <1.0cm @50% and <1.0cm @80%. + - For InF-DH scenario: + - SD DL-CPP (Case 7): 0.6cm @50% and 3.0cm @80%. + - DD DL-CPP (Case 8): 4.6cm @50% and 14.8cm @80%. + - DD DL-CPP (two carrier frequencies, two PFLs) (Case 9): 1.0cm @50% and 2.7cm @80%. +- Source [82] shows: + - For InF-SH scenario: + - DD DL-CPP (Case 1): <1cm @50% and <1cm @80%. +- Source [83] shows: + - For InF-SH scenario: + - SD DL-CPP (Case 1): <1cm @50% and <1cm @80% (with ideal resolution of integer ambiguity) +- Source [84] shows: + - For InF-SH scenario: + +- SD DL-CPP (Case 1): <1cm @50% and <1cm @80% (with ideal resolution of integer ambiguity) +- Source [85] shows: + - For InF-SH scenario: + - DL-CPP (multiple subcarriers within one PFL) (Case 4-1-1): 0.11m @ 50% and 0.51m @80% + - DL-CPP (Case 4-1-2): 0.3cm @ 50% and 0.21m @ 80% + - For InF-DH scenario: + - DL-CPP (Case 4-2-1):0.33m @50% and 0.66m @ 80%. +- Source [86] shows: + - For InF-SH scenario (100MHz and 50MHz Bandwidth): + - SD DL-CPP (horizontal): <1cm @50% and <1cm @80% + - SD DL-CPP (vertical): <1cm @50% and <1cm @80% +- Source [88] shows: + - For InF-SH scenario (400MHz, FR2) + - SD DL-CPP (Case 1): 0.002cm @50% and <0.005cm @80% +- Source [87] shows: + - For InF-SH scenario (10MHz, @3GHz) + - Round-trip carrier phase with slope: < 1cm @ 50% and <1 cm @ 80% + - For InF-SH scenario (100MHz, @3.5GHz) + - Time domain and perfect phase: < 1cm @ 50% and <1 cm @ 80% + - Time domain and estimated phase: < 1cm @ 50% and ~1 cm @ 80% +- Source [90] shows: + - For InF-SH scenario + - DD UL-CPP: <1cm @50% and 2cm @80% +- NOTE 1: Unless indicated otherwise, the results shown above are for horizontal positioning accuracy with a single carrier of bandwidth of 100MHz in FR1. +- NOTE 2: Evaluation results above are mainly used as examples. Additional results and more details of the evaluation assumptions are provided in Annex B.4. +- NOTE 3: The evaluation results for legacy positioning approach may also be available in each of the sources, or in [2]. + +The impact of the initial phases of the transmitter and the receiver on NR carrier phase positioning (CPP) is evaluated in the study item. The evaluation results from the sources (e.g., [73], [74], [75], [76], [82]) show that if the impact of the initial phases of the transmitter and the receiver are not mitigated, it is impossible to support centimeter-level positioning accuracy. + +The effectiveness of using Double Differential (DD) technique with PRU to eliminate the impact of the initial phases of the transmitter and the receiver on NR carrier phase positioning are evaluated in the study item. The evaluation results from the sources ([73], [77], [81], [82], [85]) show that the initial phases of the transmitter and the receiver can be removed effectively by the double differential technique with the use of PRU: + +- Source [73] shows the positioning accuracy of <1cm (80%) for InF-SH and < 1cm (50%) for InF-DH can be reached when the PRU is located within a distance of 5m from the target UE. + +- Source [81] shows the positioning accuracy of <1cm (80%) for InF-SH and 4.6cm (50%) for InF-DH can be reached under the condition that the PRU is located at a fixed location in LOS of the TRP. +- Source [77] shows that the accuracy of <1cm (50%) when the PRU is located within 1m of the target UE. However, the effectiveness reduces when the PRU is located away from the target UE because the channel conditions of the PRU is different from the target UE. +- Source [82] shows the positioning accuracy of < 1cm (80%) for InF-SH can be reached under the condition that the PRU is located a fixed location as shown in [82]. +- Source [85] shows the positioning accuracy of < 1cm (50%) for InF-SH can be reached under the condition that the integer ambiguity range N is limited to $\pm 1$ . +- Source [89] shows the distance accuracy degrades from 0.5cm @ 50% and 5.2cm @80% to 3.3cm @50% and 4.8cm @ 80% by the initial phase offset for InF-DH scenario. + +NOTE 1: In the above results, all other error sources (except initial phase error) were not modelled. + +NOTE 2: Unless indicated otherwise, the results shown above are for horizontal positioning accuracy with a single carrier of bandwidth of 100MHz in FR1. + +NOTE 3. Evaluation results above are mainly used as examples. Additional results and more details of the evaluation assumptions are provided in Annex B.4. + +The impact of the residual CFO at the transmitter and the receiver for NR carrier phase positioning are evaluated during the study item. + +- The evaluation results from the sources ([73], [76]) show that the impact of residual CFO on carrier phase positioning is negligible. +- The evaluation results from the source ([75]) show that the impact of the residual CFO on the performance of carrier phase positioning can be mitigated with the use of the double differential technique with a PRU that is located at a fixed location in LOS of the TRP. +- The evaluation results from the source [80] show that the impact of residual CFO on carrier phase measurement is negligible. However, carrier phase positioning accuracy degrades significantly with residual CFO with single differential (SD) DL-CPP: + - With UE residual CFO 30Hz and TRP residual CFO 10Hz, the accuracy drops from 0.0044m to 0.2m @80% and from 0.0014m to 0.0017m @50% in InF-SH. + - With UE residual CFO 100Hz and TRP residual CFO 10Hz, the accuracy drops from 0.0044m to 0.27m @80% and from 0.0014m to 0.0024m @50% in InF-SH. +- The evaluation results from the source [86] show that carrier phase positioning accuracy degrades slightly with residual CFO with DD DL-CPP: + - With maximum residual CFO 30Hz between UE and TRP, the accuracy drops from 0.0010m to 0.0018m @50% and from 0.0046m to 0.0208m @80% in InF-SH. + - With maximum residual CFO 100Hz between UE and TRP, the accuracy drops from 0.0010m to 0.0027m @50% and from 0.0046m to 0.0440m @80% in InF-SH. +- The evaluation results from the source [88] show the impact of Doppler in FR1 at 3kmph is small enough that it has negligible impact on the carrier phase positioning accuracy with DD DL-CPP, in the simulated scenario under the agreed modelling for residual CFO. + +NOTE 1: Unless indicated otherwise, the results shown above are for horizontal positioning accuracy with a single carrier of bandwidth of 100MHz in FR1. + +NOTE 2: Evaluation results above are mainly used as examples. Additional results and more details of the evaluation assumptions are provided in Annex B.4. + +The impact of the ARP errors on NR carrier phase positioning is evaluated. 8 out of 8 sources ([79], [80], [81], [85], [86], [87], [88], [90]) show that the ARP errors may have significant impact on NR carrier phase positioning accuracy. 3 out of 8 sources ([79], [81], [85]) show the impact of gNB ARP position errors on multi-frequency carrier phase positioning is much smaller than the impact on single-frequency carrier phase positioning. + +- Source [79] shows: + - When double differential is not used: + - For InF-SH scenario with 1cm ARP error: + - UL-CPP (Case 23): 1.3368m @50% and 2.121m @80% + - For InF-DH scenario with 1cm ARP error: + - UL-CPP (Case 24): 1.2329m @ 50% and 1.9317m @80% + - When double differential is used: + - For InF-SH scenario with 1cm ARP error: + - (PRU 5m) DD UL-CPP (Case 27): <1cm @ 50% and 0.57269m @80% + - (PRU 2m) DD UL-CPP (Case31): <1cm @ 50% and <1cm @80% + - For InF-DH scenario with 1cm ARP error: + - (PRU 5m) DD UL-CPP (Case 28): 0.75118m @ 50% and 1.3217m @80% + - (PRU 2m) DD UL-CPP (Case 32): 0.56419m@ 50% and 1.1915m @80% + - When multi-frequency carrier phase positioning is used: + - For InF-SH scenario with 1cm ARP error and random initial phase: + - (PRU 5m) DD UL-CPP (Case 47): 1.252cm @ 50% and 2.765cm @80% + - For InF-SH scenario with 5cm ARP error and random initial phase: + - (PRU 5m) DD UL-CPP (Case 48): 5.986cm @ 50% and 0.11879m @80% +- Source [80] shows: + - For InF-SH scenario with 1cm ARP error: + - SD DL-CPP: 0.09m @50% and 0.20m @80%. + - For InF-SH scenario with 5cm ARP error: + - SD DL-CPP: 0.18m @50% and 0.28m @80% +- Source [81] shows: + - For InF-SH scenario with 1cm ARP error: + - DD DL-CPP (Cases 11): <1.0cm @50% and 11.2cm @80%. + - DD DL-CPP (two subcarrier frequencies within one PFL) (Case 12): <1.0cm @50% and 1.79 cm @80%. + - DD DL-CPP (two carrier frequencies) (Case 13): <1.0cm @50% and 1.3cm @80%. + - For InF-SH scenario with 5cm ARP error: + - DD DL-CPP (two carrier frequencies, two PFLs) (Case 15): 3.3cm @50% and 5.6cm @80%. + - For InF-DH scenario with 1cm ARP error: + - DD DL-CPP (two carrier frequencies, two PFLs) (Case 17): 1.5cm @50% and 3.3cm @80%. + +- Source [85] shows: + - For InF-SH scenario with 1cm ARP error: + - DL-CPP (single carrier, case 3-2-1): 0.24m@50% and 0.44m@80%. + - DL-CPP (multiple subcarriers within one PFL, case 3-2-4): 0.12m @50% and 0.25m@80% + - For InF-SH scenario with 5cm ARP error: + - DL-CPP (single carrier, case 3-2-3): 0.28m@50% and 0.44m@80% + - DL-CPP (multiple subcarriers within one PFL, case 3-2-6): 0.15m@50% and 0.30m@80% +- Source [86] shows: + - For InF-SH scenario with 1cm ARP error: + - DD DL-CPP (single carrier): 0.188m (50%), 0.386m (80%) +- Source [87] shows: + - For InF-SH scenario with 2cm ARP error and random initial phase + - DL-CPP (single carrier, case 08): 1.06m @50% and 1.54m @80% +- Source [88] shows: + - For InF-SH scenario with 1cm ARP error + - DD DL-CPP(Case 6, FR2): 3.487cm (50%) and 7.907cm (80%) (PRU-UE range R = 1m) + - DD DL-CPP(Case 14, FR1): 0.05m (50%) and 0.18m (80%) +- Source [90] shows: + - For InF-SH scenario with 1cm ARP error (average PRU-UE distance = 1m) + - DD DL-CPP: 1.5cm (50%) and 3.0cm (80%) + - For InF-SH scenario with 5cm ARP error (average PRU-UE distance = 1m) + - DD DL-CPP: 10cm (50%) and 0.44m (80%) + +NOTE 1: Unless indicated otherwise, the results shown above are for horizontal positioning accuracy with a single carrier of bandwidth of 100MHz in FR1. + +NOTE 2. Evaluation results above are mainly used as examples. Additional results and more details of the evaluation assumptions are provided in Annex B.4. + +NOTE 3: The evaluation of multi-frequency carriers is based on the agreed assumption in Annex A.4 without requiring a UE to simultaneously measure more than one DL PFL. + +The impact of the UE/TRP PCO errors on NR carrier phase positioning is evaluated in the study item. 2 out of 4 sources ([79], [80]) show that when UE/TRP antenna PCO model of Example 2 is used, the impact of the PCO errors can be significant. 2 out of 4 sources ([81], [88]) show that when UE/TRP antenna PCO model of Example 1 is used, the impact of the PCO errors can be negligible. + +- Source [79] shows: + - For InF-SH scenario with a=3: + - SD DL-CPP (Case 37): 0.8469m @50% and 1.3922m @80%. + - DD DL-CPP (Case 41): < 1cm @50% and <1cm @80%. + +- For InF-DH scenario with $a=3$ : + - SD DL-CPP (Case 38): 0.9192m @50% and 1.4393m @80%. + - DD DL-CPP (Cases 42): 0.4896m @50% and 1.2148m @80% +- Source [80] shows: + - For InF-SH scenario with SD DL-CPP: + - PCO model ( $a=1$ , $w=[-2, +2]$ , $d\Phi=[0, 5]$ ): <1cm @50% and 0.06m @80% + - PCO model ( $a=3$ , $w=[-5, +5]$ , $d\Phi=[0, 5]$ ): <1cm @50% and 0.06m @80% + - PCO model ( $a=3$ , $w=[-5, +5]$ , $d\Phi=[0, 20]$ ): 0.046m @50% and 0.19m @80% +- Source [81] shows: + - For InF-SH scenario: + - DD DL-CPP (Cases 20/21): < 1cm @50% and <1cm @80%. + - For InF-DH scenario: + - DD DL-CPP (Cases 22/23): $\leq 1.3\text{cm}$ @50% and $\leq 2.8\text{cm}$ @80% +- Source [88] shows: + - For InF-SH scenario: + - DD DL-CPP (Cases 4, FR2): + - PCO model ( $a=0$ , $w=5$ ): 0.014cm @50% and 0.063cm @80% + - PCO model ( $a=1$ , $w=5$ ): 0.015cm @50% and 0.076cm @80% + - PCO model ( $a=3$ , $w=5$ ): 0.014cm @50% and 0.270cm @80% + - DD DL-CPP (Cases 12, FR1): + - PCO model ( $a=1$ , $X=5$ ): 0.04m @50% and 0.08m @80% + - PCO model ( $a=3$ , $X=5$ ): 0.04m @50% and 0.08m @80% + +NOTE 1: Unless indicated otherwise, the results shown above are for horizontal positioning accuracy with a single carrier of bandwidth of 100MHz in FR1. + +NOTE 2: Evaluation results above are mainly used as examples. Additional results and more details of the evaluation assumptions are provided in Annex B.4. + +The potential benefits of using the carrier phases of multiple carriers or multiple subcarriers are evaluated in the study item. + +- The evaluation results from the sources (e.g., [79], [81], [85]) show that the use of the carrier phases of multiple carriers or multiple subcarriers together with double differential technique are beneficial for improving the accuracy of double differential carrier phase positioning. +- One source ([80]) show there is no benefit with the use of the carrier phases of multiple carriers for carrier phase positioning when single differential carrier phase positioning is used. +- The evaluation results from the source [87] show that the use of the carrier phases of multiple subcarriers together with round trip carrier phase technique is beneficial for improving the accuracy of carrier phase positioning. + +- The evaluation from the sources [88]) show that combining carrier phase measurements from multiple groups of subcarriers is inferior to coherent processing of all subcarriers to obtain a single more accurate carrier phase measurement. +- The evaluation results from the source [89] shows the use of multiple subcarrier technique is beneficial over single carrier. +- Source [79] shows: + - When single-frequency carrier phases are used: + - For InF-SH scenario with 5cm ARP error and random initial phase: + - (PRU within 5m) DD UL-CPP (Case 45): 0.73594m @ 50% and 1.3812m @80% + - When multi-frequency carrier phases are used: + - For InF-SH scenario with 5cm ARP error and random initial phase: + - (PRU within 5m) DD UL-CPP (Case 48): 5.986cm @ 50% and 0.11879m @80%. +- Source [80] shows: + - When multi-frequency carrier phases are used: + - For InF-SH scenario without other errors, + - SD DL-CPP horizontal accuracy (Cases 703): < 1cm @50% and <1cm @80%. + - For InF-SH scenario with ARP error + - SD DL-CPP horizontal accuracy (Cases 703): < 1cm @50% and 0.18m @80% + - For InF-SH scenario with initial phase error + - SD DL-CPP horizontal accuracy (Cases 704): < 0.18m @50% and 0.34m @80% + - For InF-SH scenario with PCO + - SD DL-CPP horizontal accuracy (Cases 705): < 0.18m @50% and 0.13m @80%. +- Source [81]) shows: + - For InF-SH scenario with other errors (ARP error, random initial phase, CFO/ Oscillator-drift) + - DD DL-CPP horizontal accuracy (Cases 27/28): < 1cm @50% and <=2cm @80%. + - For InF-DH scenario: + - DD DL-CPP horizontal accuracy (Cases 29): 1.6cm @50% and 3.5cm @80%. +- Source [85] shows + - When multiple subcarriers with in one PFL are used: + - For InF-SH scenario with other errors (initial phase on both TRP and UE sides) + - DL-CPP accuracy (Case 1-2-9, N is limited to $\pm 1$ ): 0.12 m@50% and 0.25m @80%. +- Source [87] shows: + - For InF-SH scenario (10MHz, @3GHz) + - With multiple sub-carriers and round-trip carrier phase: < 1cm @ 50% and <1 cm @ 80%. +- Source [88] shows: + +- For InF-SH scenario: + - DD DL-CPP horizontal accuracy (Case 8, FR2): 0.05526m @50% and 1.42119m @80%. +- Source [89]) shows: + - For InF-DH scenario: + - Distance accuracy (Case 3): 0.44cm @50% and 0.55cm @80%. + +NOTE 1: Unless indicated otherwise, the results shown above are for horizontal positioning accuracy with a single carrier of bandwidth of 100MHz in FR1. + +NOTE 2: Evaluation results above are mainly used as examples. Additional results and more details of the evaluation assumptions are provided in Annex B.4. + +The effectiveness of using round-trip carrier phase technique to mitigate the impact of the initial phases of the transmitter and the receiver on NR carrier phase positioning is evaluated by source [87] for InF-SH, which shows achievability of horizontal positioning accuracy of: + +- 0.5cm @80% with continuous sub-carrier allocation in 10 MHz BW (i.e., with enhanced PRS), +- 1cm @80% with Comb-4 sub-carrier allocation in 10 MHz BW and no sub-carrier offset change between symbols (i.e., with enhanced PRS), and +- 1.5cm @80% with Comb-4 sub-carrier allocation in 10 MHz BW and with sub-carrier offset change between symbols (i.e., with existing PRS). + +NOTE: The evaluation results assumed phase coherency between the transmit path and the receive path of each device. + +The positioning accuracy of Phase-Difference-based AoD positioning has been evaluated. Source in [88] shows that, for InF-SH with 20 MHz, a positioning accuracy of 1m (at 80%) is achievable. + +### 6.3.3 Potential specification impact for NR carrier phase positioning + +Regarding the reference signals for NR carrier phase positioning: + +- Existing DL PRS and UL SRS for positioning purpose are recommended as the reference signals to enable positioning based on NR carrier phase measurements for both UE-based and UE-assisted positioning if NR CPP is introduced. + +NOTE: The use of SRS MIMO for NR carrier phase positioning is transparent for UE. + +Regarding the physical layer measurements for NR carrier phase positioning: + +- New measurements are recommended to be introduced for supporting UE-based and UE-assisted NR carrier phase positioning, if NR CPP is introduced. The new measurements include, at least, the following: + - For DL carrier phase positioning, the following candidate measurements are identified (potential down-selection may be considered during normative work). + - The difference between the carrier phase measured from the DL PRS signal(s) of the target TRP and the carrier phase measured from the DL PRS signal(s) of the reference TRP; + - The carrier phase measured from the DL PRS signal(s) of a TRP. + - For UL carrier phase positioning, the carrier phases measured from the UL SRS for positioning purpose is identified as the UL carrier phase measurements. + +NOTE: This proposal does not imply which carrier phase measurements are mapped to which positioning technique. + +Multipath mitigation methods for the carrier phase positioning are recommended to be introduced during normative work, if NR CPP is introduced. The candidate solutions may include, but are not limited to, the following: + +- Reporting of the carrier phase of the first path. +- At least reporting of the carrier phase of the first path, and optionally, the additional paths. +- The use of LOS/NLOS indication for the carrier phase measurements. + - NOTE: Rel-17 LOS/NLOS indicator can be considered as a starting point. +- Reporting of other channel information together with carrier phase measurements, such as existing RSRP/RSRPP. + +At least the double differential technique with PRU is feasible for UE-based, and UE-assisted NR carrier phase positioning, if NR CPP is introduced, at least, for eliminating the impact of the initial phases of the transmitter and the receiver. + +NOTE 1: How to efficiently enable the use of the PRU for supporting NR double differential carrier phase positioning needs further discussion during normative work. + +NOTE 2: The required PRU density also needs further discussion during normative work. + +NOTE 3: Other methods for eliminating the impact of the initial phases of the transmitter and the receiver are not precluded. + +## 6.4 Low power high accuracy positioning + +### 6.4.0 Study objectives + +For the study on enhancing the power efficiency of RAT-dependent positioning methods for LPHAP use cases, the following objectives have been identified in the SID: + +- Study of the requirements on LPHAP as developed by SA1 and evaluation of whether existing RAN functionality can support the power consumption and positioning requirements. + - Based on the evaluation, and, if found beneficial, study of potential enhancements to help address any limitations. + +The study is limited to enhancements to RRC\_INACTIVE and/or RRC\_IDLE states. + +### 6.4.1 Target use cases and requirements for low power high accuracy positioning + +Use case 6 defined in TS 22.104 [6] is the single representative use case for the study of LPHAP. + +For LPHAP, the main objective of the evaluations from the perspective of lower layers is on UE power consumption. + +At least relative power unit is adopted as the performance metric to evaluate the power consumption of the Rel-17 RRC\_INACTIVE state positioning and potential enhancements. + +A reference device (e.g., a mobile phone) with reference traffic type, reference battery capability, and reference battery life is defined for the purpose of identification of the performance gap that achieved by the Rel-17 RRC\_INACTIVE state positioning baseline and the target battery life of LPHAP use case 6. + +For the service type, at least the 'Low Power Periodic and Triggered 5GC-MT-LR Procedures' in TS 23.273 [144] is supported. + +For the evaluations of LPHAP use case 6, the following performance requirements are considered: + +- Horizontal positioning accuracy < 1 m for 90% of UEs +- Positioning interval / duty cycle of 15-30 s + +- UE battery life of 6 months – 1 year. + +### 6.4.2 Potential enhancements for low power high accuracy positioning + +#### 6.4.2.1 Physical layer aspects + +For UL and DL+UL positioning for UEs in RRC\_INACTIVE, the potential benefits and performance gains of enhancements on SRS for positioning to avoid frequent SRS (re)configurations are studied, including at least the following: + +- The (pre-)configuration of SRS for positioning. Details, e.g., signaling and procedure, whether/how it is applicable to an area across multiple cells, consideration of UL overhead/capacity implied by (pre-)configuration and multiple cells, etc. can be considered further during normative work. +- SRS for positioning activation/request procedure(s), e.g., network activation of SRS via paging, UE request to obtain/update SRS via RACH-based procedure. +- Events of invalidity of SRS configuration to trigger the UE request procedure can be considered further during normative work. +- Whether the enhancements may be applicable to UEs in RRC\_IDLE state can be considered further during normative work. + +From RAN1's perspective, DL PRS measurement for UEs in RRC\_IDLE state is recommended for the normative work. + +Enhancements on simplified DL PRS configuration with 1-symbol PRS can be studied further and if needed, specified during normative phase. + +#### 6.4.2.2 Higher layer aspects + +The potential enhancements for Low Power High Accuracy Positioning in higher layer aspect are studied as below: + +##### a. Enhancements on SRS configuration + +Higher layer studied the following candidate enhancements on SRS configuration. + +- Validity area mechanism + - SRS positioning validity area for UL positioning in RRC\_INACTIVE can avoid reconfiguration of SRS configuration upon cell reselection and is recommended for normative work from RAN2's perspective if feasible from RAN1's perspective. + - The solution should not require the gNB to monitor multiple SRS configuration simultaneously for a UE. +- SRS configuration request + +SRS configuration request can be discussed during normative work from RAN2 perspective. Scenarios requiring SRS configuration request include: + +- Scenario 1: During the UL positioning procedure, when the SRS configuration turns invalid, e.g., when the UE moves out of the SRS positioning validity area. +- Scenario 2: At the initiation of UL positioning procedure when an event is detected. + +Detailed solution for the SRS update, e.g., with RRC message, UL MAC, or NG-AP message can be discussed in the WI phase. + +###### - Pre-configure multiple SRS + +Pre-configuration of multiple SRS configurations (e.g., for multiple SRS positioning validity areas) is feasible from RAN2 perspective and can be discussed in normative work. + +The pre-configuration of multiple SRS configurations can be delivered to the UE either by dedicated signalling or SI broadcast. + +##### b. Enhanced DL-PRS configuration + +Alignment between DRX and PRS is beneficial from power saving point of view for LPHAP and is recommended to normative work. Two directions of solutions for DRX/PRS alignments are considered: + +- PRS alignment with fixed DRX +- DRX alignment with fixed PRS + +Solutions for the PRS/DRX alignment, e.g., LMF-based/UE-based solution, is to be discussed. + +Impacts to different RRC states (RRC\_INACTIVE and RRC\_IDLE) is to be discussed. + +##### c. Exposure of LPHAP information to the gNB and/or LMF + +Exposure of LPHAP information to the gNB and/or LMF (e.g., as a UE capability) can be discussed in normative work if any enhancement for LPHAP is agreed, taking into account any guidance from SA2. + +##### d. Positioning in RRC\_IDLE state + +- DL positioning in RRC\_IDLE is recommended to normative work from RAN2's perspective if power saving benefits are confirmed by RAN1. + +Measurement is performed in RRC\_IDLE while measurement report is sent in RRC\_CONNECTED. + +Feasibility of measurement report in msg5 should be evaluated with SA2/3 involved. + +Whether the CN can handle the measurement reports from the UE in RRC\_CONNECTED, while the positioning measurement was performed in RRC\_IDLE, can be evaluated in the WI phase with SA2 involved. + +##### e. Paging relaxation + +Paging relaxation by skipping paging reception in RRC\_INACTIVE for LPHAP is beneficial from power saving point of view and feasible from RAN2's perspective. Skipping paging reception in RRC\_INACTIVE is recommended for normative work from RAN2's perspective for achieving LPHAP requirements, if feasible and beneficial from RAN1's perspective. + +The power saving gain can be further evaluated in RAN1. Impacts of skipping paging for UE in RRC\_INACTIVE to the core network could be evaluated with SA2 involved in the WI phase. + +### 6.4.3 Summary of evaluations for low power high accuracy positioning + +The methodology for the evaluation of Low Power High Accuracy Positioning (LPHAP) can be found in Annex A.4. + +Evaluations of baseline Rel-17 RRC\_INACTIVE state positioning with the evaluation assumptions agreed for the study show that the power consumption on deep sleep state accounts for the highest proportion in the total power. + +For the evaluation on the battery life of the baseline LPHAP Type A device with battery capacity C2 of 800mAh: + +- Based on the results provided by all sources, the target requirement of 6~12 months is not achieved by the existing Rel-17 positioning for UEs in RRC\_INACTIVE state with baseline implementation factor $K = 1$ and baseline evaluation assumptions. +- Based on the results provided by all sources, the target requirement of 6~12 months is not achieved by the existing Rel-17 positioning for UEs in RRC\_INACTIVE state with optional implementation factor $K$ or optional evaluation assumptions. +- For UE-assisted DL positioning, results are provided by 14 sources ([92], [36], [93], [97], [40], [102], [43], [98], [45], [48], [50], [52], [53], [99]) out of 20 sources, and the following are observed: + - The target requirement of 6 months is achieved by 0 source, and is not achieved by 14 sources ([92],[36],[93],[97],[40],[102],[43],[98],[45],[48],[50],[52],[53], [99]) even with the most power efficient case that I-DRX cycle of 10.24s, 1 RS per 1 I-DRX cycle, high SINR, CG-SDT for measurement reporting, and implementation factor $K = 4$ . + +- The target requirement of 12 months is achieved by 0 source, and is not achieved by 14 sources ([92],[36],[93],[97],[40],[102],[43],[98],[45],[48],[50],[52],[53],[99]) even with the most power efficient case that I-DRX cycle of 10.24s, 1 RS per 1 I-DRX cycle, high SINR, CG-SDT for measurement reporting, and implementation factor $K = 4$ . +- For UE-based DL positioning, results are provided by 11 sources ([92], [36], [93], [97], [40], [43], [98], [45], [50], [52], [99]) out of 20 sources, and the following are observed: + - The target requirement of 6 months is achieved by 0 source, and is not achieved by 11 sources ([92],[36],[93],[97],[40],[43],[98],[45],[50],[52],[99]) even with the most power efficient case that I-DRX cycle of 10.24s, 1 RS per 1 I-DRX cycle, high SINR, and implementation factor $K = 4$ . + - The target requirement of 12 months is achieved by 0 source, and is not achieved by 11 sources ([92],[36],[93],[97],[40],[43],[98],[45],[50],[52],[99]) even with the most power efficient case that I-DRX cycle of 10.24s, 1 RS per 1 I-DRX cycle, high SINR, and implementation factor $K = 4$ . +- For UL positioning, results are provided by 13 sources ([92], [36], [93], [97], [40], [43], [98], [45], [48], [50], [52], [53], [99]) out of 20 sources, and the following are observed: + - The target requirement of 6 months is achieved by 0 source, and is not achieved by 13 sources ([92], [36], [93], [97], [40], [43], [98], [45], [48], [50], [52], [53], [99]) even with the most power efficient case that I-DRX cycle of 10.24s, 1 RS per 1 I-DRX cycle, high SINR, no SRS (re)configuration, and implementation factor $K = 4$ . + - The target requirement of 12 months is achieved by 0 source, and is not achieved by 13 sources ([92], [36], [93], [97], [40], [43], [98], [45], [48], [50], [52], [53], [99]) even with the most power efficient case that I-DRX cycle of 10.24s, 1 RS per 1 I-DRX cycle, high SINR, no SRS (re)configuration, and implementation factor $K = 4$ . +- For DL+UL positioning, results are provided by 1 source ([52]) out of 20 sources, and the following are observed: + - The target requirement of 6 months is achieved by 0 source and is not achieved by 1 source ([52]) even with the most power efficient case that I-DRX cycle of 10.24s, 1 RS per 1 I-DRX cycle, high SINR, no SRS (re)configuration, CG-SDT for measurement reporting, and implementation factor $K = 4$ . + - The target requirement of 12 months is achieved by 0 source and is not achieved by 1 source ([52]) even with the most power efficient case that I-DRX cycle of 10.24s, 1 RS per 1 I-DRX cycle, high SINR, no SRS (re)configuration, CG-SDT for measurement reporting, and implementation factor $K = 4$ . + +For the evaluation on the battery life of the optional LPHAP Type B device with battery capacity C2 of 4500mAh: + +- Based on the results provided by all sources, the target requirement of 6~12 months is not achieved by the existing Rel-17 positioning for UEs in RRC\_INACTIVE state with the baseline implementation factor $K=1$ and baseline evaluation assumptions. +- For UE-assisted DL positioning, results are provided by 9 sources ([36], [93], [97], [102], [43], [45], [50], [52], [98]) out of 20 sources, and the following are observed: + - The target requirement of 6 months is achieved by 5 sources ([36], [45], [52], [98], [102]) with the implementation factor $K = 4$ and by 4 sources ([43],[50], [93], [97]) with the implementation factor $K \geq 2$ , and is not achieved by 5 sources with the implementation factor $K < 4$ ([36], [42], [45], [52], [98]) and by 4 sources ([43],[50], [93], [97]) with the implementation factor $K < 2$ . + - The target requirement of 12 months is achieved by 5 sources ([43], [50], [52], [93], [97]) with the case that I-DRX cycle of 10.24s, 1 RS per 1 I-DRX cycle, high SINR, CG-SDT for reporting and implementation factor $K = 4$ , and is not achieved by 9 sources ([36], [93], [97], [102], [43], [45], [50], [52], [98]) with the implementation factor $K < 4$ . +- For UE-based DL positioning, results are provided by 8 sources ([36], [93], [97], [43], [45], [50], [52], [98]) out of 20 sources, and the following are observed: + - The target requirement of 6 months is achieved by 4 sources ([36], [45], [52], [98]) with the implementation factor $K = 4$ and by 4 sources ([43], [50], [93], [97]) with the implementation factor $K \geq 2$ , and is not + +achieved by 4 sources with the implementation factor $K < 4$ ([36], [45], [52], [98]) and by 4 sources ([43],[50], [93], [97]) with the implementation factor $K < 2$ ; + +- The target requirement of 12 months is achieved by 5 sources ([43], [50], [52], [93], [97]) with the case that I-DRX cycle of 10.24s, 1 RS per 1 I-DRX cycle, high SINR, and implementation factor $K = 4$ , and is not achieved by 8 sources ([36], [93], [97], [43], [45], [50], [52], [98]) with the implementation factor $K < 4$ . +- For UL positioning, results are provided by 8 sources ([36], [93], [97], [43], [45], [50], [52], [98]) out of 20 sources, and the following are observed: + - The target requirement of 6 months is achieved by 4 sources ([36], [45], [52], [98]) with the implementation factor $K = 4$ and by 4 sources ([43],[50], [93], [97]) with the implementation factor $K \geq 2$ , and is not achieved by 4 sources ([36], [45], [52], [98]) with the implementation factor $K < 4$ and by 4 sources ([43], [50], [93], [97]) with the implementation factor $K < 2$ ; + - The target requirement of 12 months is achieved by 5 sources ([43], [50], [52], [93], [97]) with the case that I-DRX cycle of 10.24s, 1 RS per 1 I-DRX cycle, high SINR, no SRS (re)configuration, and implementation factor $K = 4$ , and is not achieved by 8 sources ([36], [93], [97], [43], [45], [50], [52], [98]) with the implementation factor $K < 4$ . +- For DL+UL positioning, results are provided by 1 source ([52]) out of 20 sources, and the following are observed: + - The target requirement of 6 months is achieved by 1 source ([52]) with implementation factor $K = 4$ , and is not achieved by 1 source ([52]) with implementation factor $K < 4$ ; + - The target requirement of 12 months is achieved by 1 source ([52]) with the case that I-DRX cycle of 10.24s, 1 RS per 1 I-DRX cycle, high SINR, no SRS (re)configuration, CG-SDT for measurement reporting, and implementation factor $K = 4$ , and is not achieved by 1 source ([52]) with implementation factor $K < 4$ . + +NOTE: The implementation factor $K$ is a factor related to the reference device in the model to convert the relative power unit to the battery life. Four values are introduced for $K$ with $K = 1$ as the baseline and $K = 0.5, 2, 4$ as optional values. The model is captured in the Annex A.4. + +NOTE: Without otherwise noted, "high SINR" in the observation refers to the evaluation case that no intra-/inter-frequency RRM and single SSB for synchronization purpose is considered. + +From evaluations for a LPHAP device, it is observed that the existing Rel-17 positioning procedures for UEs in RRC\_INACTIVE state cannot satisfy the target battery life required by LPHAP use case 6 for majority of the evaluation scenarios that are examined. + +Based on the evaluations, it is concluded that enhancements to meet the target battery life in Rel-18 are necessary. + +Evaluation results of extending DRX cycle are provided by 13 sources ([92], [93], [94], [96], [97], [98], [99], [101], [102], [103], [108], [109], [110]) out of 19 sources, the following is observed: + +- Results with extended DRX cycle beyond 10.24s provide power saving gains with respect to that with the baseline DRX cycle of 1.28s and is beneficial towards meeting the battery life requirement as extended DRX cycle beyond 10.24s allows a UE to remain in a deeper sleep state for a longer duration. +- From the evaluations, + - Power saving gains achieved with extended DRX cycle with respect to baseline DRX cycle 1.28s are provided by 2 sources ([93], [103]): + - In [93], 87%~90% power saving gains are achieved with DRX cycle of 30.72s with respect to that with the baseline DRX cycle of 1.28s. + - In [103], 35.05%~53.70% power saving gains are achieved with DRX cycle of 10.24s with respect to that with the baseline DRX cycle of 1.28s, and 37.56%~57.53% power saving gains are achieved with DRX cycle of 20.48s with respect to that with the baseline DRX cycle of 1.28s. + +- Results on battery life of extended DRX cycle together with ultra-deep sleep state are provided by 13 sources ([92], [93], [94], [96], [97], [98], [99], [101], [102], [103], [108], [109], [110]), and the target requirement of 6~12 months is achieved by 12 sources in some cases. + +Evaluation results of UE (re)entering RRC\_CONNECTED state to obtain SRS (re)configuration for UL/DL+UL positioning are provided by 7 sources ([92], [93], [94], [99], [101], [103], [109], [110]) out of 19 sources, the following is observed: + +- UE (re)entering RRC\_CONNECTED state to obtain SRS (re)configuration increases power consumption, and results without SRS (re)configuration procedure provide power saving gains with respect to that with (re)entering RRC\_CONNECTED state to obtain SRS (re)configuration. +- From the evaluations, + - In [92], 65.2790% of total power is consumed by SRS (re)configuration for UL positioning; UE (re)entering RRC\_CONNECTED state to obtain SRS (re)configuration increases the power consumption by 3 times. + - In [93], UE (re)entering RRC\_CONNECTED state to obtain SRS (re)configuration every 10.24s/20.48s/40.96s increases the power consumption by 8.71%/4.47%/2.23% with DRX cycle of 1.28s and by 13.38%/6.69%/3.34% with DRX cycle of 10.24s. + - In [94], 23.81%~52.62% of total power is consumed by SRS (re)configuration for UL positioning, and 21.65%~26.54% of total power is consumed by SRS (re)configuration for DL+UL positioning. + - In [101], 11.6%~34.4% of total power is consumed by SRS (re)configuration for UL positioning with ultra-deep sleep state option 1 with additional transition energy 10000, and 46.2%~77.5% of total power is consumed by SRS (re)configuration for UL positioning with ultra-deep sleep state option 2. + - In [103], 11.28%~52.41% of total power is consumed by SRS (re)configuration for UL positioning; Without SRS (re)configuration procedure, 55.07%/20.38%/11.85% power saving gains are achieved for DRX cycle of 1.28s/10.24s/20.48s. + +Evaluation results on battery life assuming no SRS (re)configuration together with ultra-deep sleep state are provided by 11 sources ([92], [93], [96], [97], [98], [99], [101], [103], [108], [109], [110]) out of 19 sources, and the target requirement of 6~12 months is achieved by 10 out of 11 sources. + +Evaluation results of minimized gaps between PRS/SRS/paging/reporting/synchronization are provided by 10 sources ([92], [93], [96], [98], [101], [102], [103], [108], [109], [110]) sources out of 19 sources, the following is observed: + +- Minimizing gaps between PRS/SRS/paging/reporting/synchronization reduces power consumption, and results with minimized gaps between PRS/SRS/paging/reporting/synchronization provide power saving gains with respect to that without minimized gaps. +- From the evaluations, + - Comparative results with and without optimization of minimized gaps between PRS/SRS/paging/reporting/synchronization are provided by 3 sources ([102], [103], [110]): + - In [102], 8%~35% and 12.7%~44.5% power saving gains are achieved for DRX cycle 1.28s and 13.2% and 34% power saving gains for DRX cycle 10.24 sec, with minimized gaps between PRS/SRS/paging/reporting/synchronization with sleep states in TR 38.840 and ultra-deep sleep state option 1 with additional transition energy 10000. + - In [103], 5.48%~15.59%, 1.05%~3.60%, and 0.54%~1.96% power saving gains are achieved with minimized gaps between PRS/SRS/paging/reporting/synchronization for DRX cycle 1.28s, 10.24s, and 20.48s with sleep states in TR 38.840; 17.14%~33.33% power saving gains are achieved with minimized gaps between PRS/SRS/paging/reporting/synchronization for DRX cycle of 20.48s with ultra-deep sleep state option 1. + - Results on battery life of assuming minimized gaps between PRS/SRS/paging/reporting/synchronization together with DRX cycle equal to or larger than 10.24s and ultra-deep sleep state are provided by 10 sources + +([92], [93], [96], [98], [101], [102], [103], [108], [109], [110]), and the target requirement of 6~12 months is achieved by 9 sources. + +Results of paging and/or PEI triggered positioning are further provided by 2 sources ([101], [108]) based on minimized gaps, which is beneficial to improve battery life as it allows a UE to perform positioning measurement and/or reporting behaviors: + +- In [101], PEI triggered positioning improves battery life by 0.24~1.64 months, for DRX cycle 10.24s, with multiple ultra-deep sleep state options. +- In [108], paging triggered positioning improves battery life by 0.08 (6.02%) ~0.17 (7.98%) months for DL positioning, and by 0.02 (1.71%)~0.05 (1.96%) months for UL positioning; PEI triggered positioning improves battery life by 0.09 (6.77%) ~0.62 (29.11%) months for DL positioning, and by 0.04 (2.90%) ~0.47 (20.61%) months for UL positioning, for DRX cycle 10.24s and 20.48s, and ultra-deep sleep state option 1 with additional transition energy 10000. + +Results on battery life of skipping paging reception are further provided by 1 source ([92]) out of 19 sources, configuring a DRX cycle longer than positioning periodicity (up to 81.92s) or without paging reception can achieve 44.32%~89% power saving gain and is beneficial to improve battery life as it allows a UE to wake up using ultra-deep sleep state option 2 when only performing positioning related operations to achieve the target requirement of LPHAP. When UE wakes up to perform other operations than just positioning related operations, the UE uses ultra-deep sleep state option 1. + +Results of only using TRS-based synchronization in adjacent slot to SRS is further provided by 1 source ([92]) under ultra-deep sleep state option 2 without paging reception, which achieves 23.33% power saving gain and further improves battery life with respect to that using SSB-based synchronization for UL positioning. + +Evaluation results of simplified PRS configuration on both battery life and accuracy are provided by 1 source ([101]) out of 19 sources, the following is observed: + +- In the case of K=1, C2=800, DRX cycle = 10.24s with ultra-deep sleep option 2, 1-symbol PRS can satisfy 6-month battery life but more than 1 symbol PRS cannot. +- The positioning accuracy of 1-symbol PRS and comb size > 12 barely reduces and can meet the accuracy requirement in some cases. + +Table 6.4.3-1 presents a summary of the potential enhancements and their combinations considered by different sources as part of the study. + +**Table 6.4.3-1: Summary for results of overall enhancements for LPHAP** + +| Source | Evaluation case description | Target requirements are met – Yes/No | | +|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|-------------------| +| | | 6 months | 12 months | +| [92] | UE-assisted DL positioning;
RS = 10.24s, paging = 10.24s, High SINR, CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000; | K = 1, Type A: NO | K = 1, Type A: NO | +| | UE-based DL positioning;
RS = 10.24s, paging = 10.24s, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000; | K = 1, Type A: NO | K = 1, Type A: NO | +| | UE-based DL positioning;
RS = 10.24s, paging = 20.48s, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000; | K = 1, Type A: NO | K = 1, Type A: NO | +| | UE-based DL positioning;
RS = 10.24s, paging = 40.96s, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000; | K = 1, Type A: NO | K = 1, Type A: NO | +| | UE-based DL positioning;
RS = 10.24s, paging = 81.92s, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000; | K = 1, Type A: NO | K = 1, Type A: NO | +| | UE-based DL positioning;
RS = 10.24s, no paging, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000; | K = 1, Type A: NO | K = 1, Type A: NO | +| | UL positioning;
RS = 10.24s, paging = 10.24s, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000; | K = 1, Type A: NO | K = 1, Type A: NO | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------------| +| UL positioning;
RS = 10.24s, paging = 20.48s, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000; | K = 1, Type A: NO | K = 1, Type A: NO | +| UL positioning;
RS = 10.24s, paging = 40.96s, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000; | K = 1, Type A: NO | K = 1, Type A: NO | +| UL positioning;
RS = 10.24s, paging = 81.92s, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized; No
SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000; | K = 1, Type A: NO | K = 1, Type A: NO | +| UL positioning;
RS = 10.24s, no paging, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000; | K = 1, Type A: NO | K = 1, Type A: NO | +| UE-based DL positioning;
RS = 10.24s, paging = 20.48s, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 +
Ultra-deep sleep option 2; | K = 1, Type A: NO | K = 1, Type A: NO | +| UE-based DL positioning;
RS = 10.24s, paging = 40.96s, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 +
Ultra-deep sleep option 2; | K = 1, Type A: NO | K = 1, Type A: NO | +| UE-based DL positioning;
RS = 10.24s, paging = 81.92s, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 +
Ultra-deep sleep option 2; | K = 1, Type A: NO | K = 1, Type A: NO | + +| | | | | +|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| | UE-based DL positioning;
RS = 10.24s, no paging, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 2; | K = 1, Type A: YES | K = 1, Type A: NO | +| | UL positioning;
RS = 10.24s, paging = 20.48s, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 +
Ultra-deep sleep option 2; | K = 1, Type A: NO | K = 1, Type A: NO | +| | UL positioning;
RS = 10.24s, paging = 40.96s, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 +
Ultra-deep sleep option 2; | K = 1, Type A: NO | K = 1, Type A: NO | +| | UL positioning;
RS = 10.24s, paging = 81.92s, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 +
Ultra-deep sleep option 2; | K = 1, Type A: YES | K = 1, Type A: NO | +| | UL positioning;
RS = 10.24s, no paging, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 2; | K = 1, Type A: YES | K = 1, Type A: YES | +| [93] | UE-assisted DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR, CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| UE-assisted DL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR, CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| UE-assisted DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR, CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| UE-assisted DL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR, CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| UE-based DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| UE-based DL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| UE-based DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| UE-based DL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: YES
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| UL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| UL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| UL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | + +| | | | | +|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| | UL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: YES
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| [94] | UE-based DL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 1, Type B: YES | K = 1, Type A: NO
K = 1, Type B: YES | +| [96] | UE-assisted DL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR, CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 2, Type B: NO
K = 4, Type B: YES | +| | UE-based DL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 2, Type B: NO
K = 4, Type B: YES | +| | UL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000
No SRS (re)configuration; | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 2, Type B: NO
K = 4, Type B: YES | +| [97] | UE-assisted DL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 2, Type B: YES
K = 4, Type B: YES | + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| UE-assisted DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| UE-assisted DL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| UE-assisted DL;
DRX = 10.24s, 1 RS per 1 DRX, Low SINR; CG-SDT for reporting
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 2, Type B: NO
K = 4, Type B: YES | +| UE-assisted DL;
DRX = 20.48s, 1 RS per 1 DRX, Low SINR; CG-SDT for reporting
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 2, Type B: YES
K = 4, Type B: YES | +| UE-assisted DL;
DRX = 30.72s, 1 RS per 1 DRX, Low SINR; CG-SDT for reporting
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | + +| | | | +|-----------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| UE-based DL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 2, Type B: YES
K = 4, Type B: YES | +| UE-based DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| UE-based DL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| UE-based DL;
DRX = 10.24s, 1 RS per 1 DRX, Low SINR;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 2, Type B: YES
K = 4, Type B: YES | +| UE-based DL;
DRX = 20.48s, 1 RS per 1 DRX, Low SINR;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 2, Type B: YES
K = 4, Type B: YES | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| UE-based DL;
DRX = 30.72s, 1 RS per 1 DRX, Low SINR;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| UL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000; | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 2, Type B: YES
K = 4, Type B: YES | +| UL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| UL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| UL;
DRX = 10.24s, 1 RS per 1 DRX, Low SINR;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 2, Type B: NO
K = 4, Type B: YES | + +| | | | | +|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| | UL;
DRX = 20.48s, 1 RS per 1 DRX, Low SINR;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 2, Type B: YES
K = 4, Type B: YES | +| | UL;
DRX = 30.72s, 1 RS per 1 DRX, Low SINR;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| [98] | UE-assisted DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES | +| | UE-assisted DL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES | +| | UE-assisted DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Ultra-deep sleep option 2 | K = 1, Type A: YES | K = 1, Type A: YES | +| | UE-based DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES | +| | UE-based DL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES | + +| | | | | +|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------| +| | UE-based DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 2 | K = 1, Type A: YES | K = 1, Type A: YES | +| | UL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES | +| | UL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES | +| | UL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 2 | K = 1, Type A: YES | K = 1, Type A: YES | +| [99] | UE-assisted DL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: NO | K = 1, Type A: NO
K = 4, Type A: NO | +| | UE-assisted DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: YES | K = 1, Type A: NO
K = 4, Type A: NO | +| | UE-assisted DL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: YES | K = 1, Type A: NO
K = 4, Type A: YES | + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|-----------------------------------------| +| UE-assisted DL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 4, Type A: YES | K = 1, Type A: NO
K = 4, Type A: NO | +| UE-assisted DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 4, Type A: YES | K = 1, Type A: NO
K = 4, Type A: YES | +| UE-assisted DL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 4, Type A: YES | K = 1, Type A: NO
K = 4, Type A: YES | +| UE-based DL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: NO | K = 1, Type A: NO
K = 4, Type A: NO | +| UE-based DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: YES | K = 1, Type A: NO
K = 4, Type A: NO | +| UE-based DL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: YES | K = 1, Type A: NO
K = 4, Type A: YES | +| UE-based DL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 4, Type A: YES | K = 1, Type A: NO
K = 4, Type A: NO | +| UE-based DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 4, Type A: YES | K = 1, Type A: NO
K = 4, Type A: YES | +| UE-based DL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 4, Type A: YES | K = 1, Type A: NO
K = 4, Type A: YES | +| UL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: NO | K = 1, Type A: NO
K = 4, Type A: NO | + +| | | | | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------| +| | UL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: YES | K = 1, Type A: NO
K = 4, Type A: NO | +| | UL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: YES | K = 1, Type A: NO
K = 4, Type A: YES | +| | UL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 4, Type A: YES | K = 1, Type A: NO
K = 4, Type A: NO | +| | UL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 4, Type A: YES | K = 1, Type A: NO
K = 4, Type A: YES | +| | UL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: YES
K = 4, Type A: YES | K = 1, Type A: NO
K = 4, Type A: YES | +| [101] | UE-assisted DL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: NO
K = 0.5, Type B: NO
K = 1, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 0.5, Type B: NO
K = 1, Type B: NO | +| | UE-assisted DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 0.5, Type B: YES
K = 1, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 0.5, Type B: NO
K = 1, Type B: YES | +| | UE-assisted DL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 0.5, Type B: NO
K = 1, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 0.5, Type B: NO
K = 1, Type B: NO | + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------| +| UE-assisted DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 0.5, Type B: YES
K = 1, Type B: YES | K = 1, Type A: NO
K = 4, Type A: YES
K = 0.5, Type B: NO
K = 1, Type B: YES | +| UE-assisted DL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 2 | K = 0.5, Type A: NO
K = 1, Type A: NO | K = 0.5, Type A: NO
K = 1, Type A: NO | +| UE-assisted DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 2 | K = 0.5, Type A: NO
K = 1, Type A: YES | K = 0.5, Type A: NO
K = 1, Type A: NO | +| UE-based DL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: NO
K = 0.5, Type B: NO
K = 1, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 0.5, Type B: NO
K = 1, Type B: YES | +| UE-based DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 0.5, Type B: YES
K = 1, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 0.5, Type B: NO
K = 1, Type B: YES | +| UE-based DL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 0.5, Type B: YES
K = 1, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 0.5, Type B: NO
K = 1, Type B: YES | +| UE-based DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 0.5, Type B: YES
K = 1, Type B: YES | K = 1, Type A: NO
K = 4, Type A: YES
K = 0.5, Type B: YES
K = 1, Type B: YES | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------| +| UE-based DL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 2 | K = 0.5, Type A: NO
K = 1, Type A: YES | K = 0.5, Type A: NO
K = 1, Type A: NO | +| UE-based DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 2 | K = 0.5, Type A: YES
K = 1, Type A: YES | K = 0.5, Type A: NO
K = 1, Type A: YES | +| UL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: NO
K = 0.5, Type B: NO
K = 1, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 0.5, Type B: NO
K = 1, Type B: NO | +| UL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 0.5, Type B: YES
K = 1, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 0.5, Type B: NO
K = 1, Type B: YES | +| UL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 0.5, Type B: YES
K = 1, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 0.5, Type B: NO
K = 1, Type B: YES | +| UL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 0.5, Type B: YES
K = 1, Type B: YES | K = 1, Type A: NO
K = 4, Type A: YES
K = 0.5, Type B: YES
K = 1, Type B: YES | +| UL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 2 | K = 0.5, Type A: NO
K = 1, Type A: YES | K = 0.5, Type A: NO
K = 1, Type A: NO | + +| | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------| +| UL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 2 | K = 0.5, Type A: YES
K = 1, Type A: YES | K = 0.5, Type A: NO
K = 1, Type A: YES | +| DL+UL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: NO
K = 0.5, Type B: NO
K = 1, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 0.5, Type B: NO
K = 1, Type B: NO | +| DL+UL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 0.5, Type B: YES
K = 1, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 0.5, Type B: NO
K = 1, Type B: YES | +| DL+UL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 0.5, Type B: YES
K = 1, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 0.5, Type B: NO
K = 1, Type B: YES | +| DL+UL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 0.5, Type B: YES
K = 1, Type B: YES | K = 1, Type A: NO
K = 4, Type A: YES
K = 0.5, Type B: NO
K = 1, Type B: YES | +| DL+UL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 2 | K = 0.5, Type A: NO
K = 1, Type A: YES | K = 0.5, Type A: NO
K = 1, Type A: NO | + +| | | | | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| | DL+UL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 2 | K = 0.5, Type A: NO
K = 1, Type A: YES | K = 0.5, Type A: NO
K = 1, Type A: NO | +| [102] | UE-assisted DL;
DRX = 1.28s, 1 RS per 1 DRX, High SINR, CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 4, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 4, Type B: NO | +| | UE-assisted DL;
DRX = 1.28s, 1 RS per 8 DRX, High SINR, CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 4, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 4, Type B: NO | +| | UE-assisted DL;
DRX = 10.24, 1 RS per 1 DRX, High SINR, CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 4, Type B: YES | +| [103] | UE-assisted DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| | UE-assisted DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| UE-assisted DL;
DRX = 20.48s, 1 RS per 1 DRX, no paging, High SINR;
CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 2 | K = 1, Type A: YES
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| UE-based DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| UE-based DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| UE-based DL;
DRX = 20.48s, 1 RS per 1 DRX, no paging, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 2 | K = 1, Type A: YES
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: YES
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| UL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | + +| | | | | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| | UL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 5000 | K = 1, Type A: NO
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 2, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| | UL;
DRX = 20.48s, 1 RS per 1 DRX, no paging, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 2 | K = 1, Type A: YES
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | K = 1, Type A: YES
K = 2, Type A: YES
K = 4, Type A: YES
K = 1, Type B: YES
K = 2, Type B: YES
K = 4, Type B: YES | +| [108] | UE-assisted DL;
DRX = 1.28s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO | K = 1, Type A: NO | +| | UE-assisted DL;
DRX = 1.28s, 1 RS per 8 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO | K = 1, Type A: NO | +| | UE-assisted DL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO | K = 1, Type A: NO | +| | UE-assisted DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO | K = 1, Type A: NO | + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------------| +| UE-assisted DL;
DRX = 1.28s, 1 RS per 1 DRX, Low SINR; RA-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO | K = 1, Type A: NO | +| UE-assisted DL;
DRX = 1.28s, 1 RS per 8 DRX, Low SINR; RA-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO | K = 1, Type A: NO | +| UE-assisted DL;
DRX = 10.24s, 1 RS per 1 DRX, Low SINR; RA-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO | K = 1, Type A: NO | +| UE-assisted DL;
DRX = 20.48s, 1 RS per 1 DRX, Low SINR; RA-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO | K = 1, Type A: NO | +| UL;
DRX = 1.28s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO | K = 1, Type A: NO | +| UL;
DRX = 1.28s, 1 RS per 8 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO | K = 1, Type A: NO | +| UL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO | K = 1, Type A: NO | + +| | | | | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| | UL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO | K = 1, Type A: NO | +| | UL;
DRX = 1.28s, 1 RS per 1 DRX, Low SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO | K = 1, Type A: NO | +| | UL;
DRX = 1.28s, 1 RS per 8 DRX, Low SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO | K = 1, Type A: NO | +| | UL;
DRX = 10.24s, 1 RS per 1 DRX, Low SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO | K = 1, Type A: NO | +| | UL;
DRX = 20.48s, 1 RS per 1 DRX, Low SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO | K = 1, Type A: NO | +| [109] | UE-assisted DL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 4, Type B: YES | +| | UE-assisted DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 4, Type B: YES | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------| +| UE-assisted DL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 4, Type B: YES | +| UE-based DL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 4, Type B: YES | +| UE-based DL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 4, Type B: YES | +| UE-based DL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 4, Type B: YES | +| UL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 4, Type B: YES | +| UL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 4, Type B: YES | +| UL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 4, Type B: YES | + +| | | | | +|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------| +| | DL+UL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 1, Type B: NO
K = 4, Type B: YES | +| | DL+UL;
DRX = 20.48s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 4, Type A: NO
K = 1, Type B: YES
K = 4, Type B: YES | +| | DL+UL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 4, Type B: YES | K = 1, Type A: NO
K = 4, Type A: YES
K = 1, Type B: YES
K = 4, Type B: YES | +| [110] | UE-assisted DL;
DRX = 1.28s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO | K = 1, Type A: NO | +| | UE-assisted DL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: NO | K = 1, Type A: NO | +| | UL;
DRX = 10.24s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: YES | K = 1, Type A: NO | + +| | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|--------------------| +| UL;
DRX = 30.72s, 1 RS per 1 DRX, High SINR; CG-SDT for reporting;
Gaps between PRS/SRS/paging/reporting is minimized;
No SRS (re)configuration
Ultra-deep sleep option 1 w transition energy 10000 | K = 1, Type A: YES | K = 1, Type A: YES | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|--------------------| + +Evaluation results on the battery life of overall enhancements including at least one or combinations of DRX cycle beyond 10.24s, ultra-deep sleep state, minimized gaps between PRS/SRS/paging/reporting/synchronization, and no SRS (re)configuration procedure, are provided by 13 sources ([92], [93], [94], [96], [97], [98], [99], [101], [102], [103], [108], [109], [110]) out of 19 sources. + +For the evaluation with ultra-deep sleep state option 1 with additional transition energy 10000, results are provided by 13 sources ([92], [93], [94], [96], [97], [98], [99], [101], [102], [103], [108], [109], [110]) out of 19 sources, and the following are observed: + +- For the baseline LPHAP Type A device with battery capacity C2 of 800mAh, the target requirement of 6~12 months is achieved by 1 source ([110]) with baseline implementation factor K = 1, and is achieved by 8 sources ([93], [94], [97], [98], [99], [101], [103], [109]) with optional implementation factor K. +- For the optional LPHAP Type B device with battery capacity C2 of 4500mAh, the target requirement of 6~12 months is achieved by 8 sources ([93], [94], [97], [98], [99], [101], [103], [109]) with baseline implementation factor K = 1, and is achieved by 6 sources ([93], [96], [97], [101], [103], [109]) with optional implementation factor K. + +For the evaluation with ultra-deep sleep state option 1 with additional transition energy 5000, results are provided by 4 sources ([93], [99], [101], [103]) out of 19 sources, and the following are observed: + +- For the baseline LPHAP Type A device with battery capacity C2 of 800mAh, the target requirement of 6~12 months is achieved by 2 sources ([93], [99]) with baseline implementation factor K = 1, and is achieved by 4 sources ([93], [99], [101], [103]) with optional implementation factor K. +- For the optional LPHAP Type B device with battery capacity C2 of 4500mAh, the target requirement of 6~12 months is achieved by 3 sources ([93], [101], [103]) with baseline implementation factor K = 1, and is achieved by 3 sources ([93], [101], [103]) with optional implementation factor K. + +For ultra-deep sleep state option 2 (including TDM-ed with ultra-deep sleep option 1 for power cycles in which paging reception is required), results are provided by 4 sources ([92], [98], [101], [103]) out of 19 sources, and the following are observed: + +- For the baseline LPHAP Type A device with battery capacity C2 of 800mAh, the target requirement of 6~12 months is achieved by 4 sources ([92], [98], [101], [103]) with baseline implementation factor K = 1, and is achieved by 2 sources ([101], [103]) with optional implementation factor K. +- For the optional LPHAP Type B device with battery capacity C2 of 4500mAh, the target requirement of 6~12 months is achieved by 1 source ([103]) with baseline implementation factor K = 1, and is achieved by 1 source ([103]) with optional implementation factor K. + +### 6.4.4 Potential specification impact for low power high accuracy positioning + +Extending DRX cycle beyond 10.24s was studied and found beneficial towards meeting the battery life requirement for LPHAP and is recommended for normative work on Rel-18 positioning enhancements from RAN1's perspective. + +NOTE: No RAN1 specification impact has been identified. + +For UL and DL+UL positioning for UEs in RRC\_INACTIVE state, the details of solutions for enhancements on SRS for positioning to avoid frequent RRC connection for SRS (re)configuration can be further discussed during normative work, which may include but are not limited to one or combinations of the following: + +- SRS for positioning configurations in multiple cells. + - NOTE: Details including issues such as interference, timing advance, spatial relation information, pathloss reference and common SRS parameters across multiple cells can be further discussed during normative work. +- Pre-configuration of one or multiple SRS for positioning configurations. +- SRS for positioning activation/request procedure(s). + +In addition to the above, specification impact can be expected from the perspective of higher layers to support the potential enhancements for LPHAP as detailed in Clause 6.4.2.2. + +## 6.5 Positioning of UEs with reduced capabilities + +### 6.5.0 Study objectives + +The scope of the study on positioning for RedCap UEs is defined in the SID [7] as: + +- Evaluation of positioning performance of existing positioning procedures and measurements with RedCap UEs. +- Based on the evaluations, assessment of the necessity of enhancements and, if needed, identification of enhancements to help address limitations associated with RedCap UEs. + +For the purpose of the study of positioning performance for UEs with Reduced Capabilities (RedCap UEs), the following target performance requirements are considered: + +For commercial use cases for both indoor and outdoor scenarios + +- Horizontal positioning accuracy: ( $< 3$ m) for 90% of UEs +- Vertical positioning accuracy: ( $< 3$ m) for 90% of UEs. + +For IIoT use cases: + +- Horizontal positioning accuracy: ( $< 1$ m) for 90% of UEs +- Vertical positioning accuracy: ( $< 3$ m) for 90% of UEs. + +For the above target requirements for evaluations, it should be noted that the target positioning requirements may not necessarily be achieved for all scenarios and use cases. Further, all positioning techniques may not achieve all positioning requirements in all scenarios. + +### 6.5.1 Potential solutions for positioning for RedCap UEs + +Potential enhancements to UL SRS for positioning to enable transmitter frequency hopping are studied, including but not limited to partial overlapping between hops, hopping bandwidth, and time gap between frequency hopping. + +Potential enhancements to DL PRS to enable transmitter or receiver frequency hopping are studied, including but not limited to impact on processing capability, hopping bandwidth in the positioning frequency layer, time gap between frequency hopping, measurement period, and partial overlapping between hops. + +The potential benefits and performance gains of frequency hopping of the DL PRS and UL SRS are investigated, taking into account at least the following: + +- The impact of Doppler, phase offset, timing offset, power imbalance among hops +- RedCap UE capability and complexity considerations +- Impact of RF retuning during frequency hopping + +- Details of frequency hopping (including Tx hopping and/or Rx hopping, BWP switching). + +In addition, use of NR carrier phase positioning is also studied and evaluated for enabling high accuracy positioning performance for RedCap UEs. + +### 6.5.2 Summary of evaluations for positioning for RedCap UEs + +The methodology for the evaluation of positioning performance for RedCap UEs can be found in Annex A.5. + +For the baseline performance of positioning for Redcap UEs in IIOT scenarios, based on the results provided by a majority of 19 sources, for InF-SH in FR1, the horizontal positioning requirement for IIOT use cases is not achieved by Rel.17 solutions using 5 MHz or 20 MHz of bandwidth. + +- Sources in [111], [72] show that UL TDOA cannot meet the requirement. +- Sources in [71], [72] show that multi-RTT cannot meet the requirement. +- Sources in [57], [58], [59], [60], [62], [65], [67], [72], [115], [127] show that DL-TDOA cannot meet the requirement. +- Source in [55] shows that the requirement can be met using 20 MHz of bandwidth. +- Source in [55] shows that the requirement cannot be met using 5 MHz of bandwidth. +- Source in [125] shows that UL-AoA cannot meet the requirement. +- Source in [128] shows that DL-AoD cannot meet the requirement. + +Based on the results provided by 2 sources ([62], [71]) out of 19 sources, for InF-SH in FR2, the horizontal positioning requirement for IIOT use cases is achieved by Rel.17 solutions using 100 MHz of bandwidth. + +- Source in [62] shows that DL-TDOA can meet the requirement. +- Source in [71] shows that multi-RTT can meet the requirement. + +Based on the result provided by the following source, for InF-DH in FR1, the horizontal positioning requirement for IIOT use cases is not achieved by Rel.17 solutions using 20 MHz of bandwidth. + +- Source in [60], [117], [118] show that the requirements for IIOT use cases cannot be met for InF-DH. + +For the baseline performance of positioning for Redcap UEs in commercial scenarios, + +- based on the results provided by [111] and [113], for UMi in FR1, the horizontal positioning requirement for commercial use cases is not achieved by Rel.17 solutions using 20 MHz of bandwidth and UL TDOA. +- based on the results provided by [67], [113], [118], and [127], for UMi in FR1, the horizontal positioning requirement for commercial use cases is not achieved by Rel.17 solutions using 5MHz or 20 MHz of bandwidth and DL TDOA. +- based on the results provided by [71] and [113], for UMi in FR1, the horizontal positioning requirement for commercial use cases is not achieved by Rel.17 solutions using 20 MHz or 5 MHz of bandwidth and multi-RTT. + +Regarding the performance for positioning of Redcap UEs using frequency hopping in IIoT scenarios, considering phase offset between hops: + +- In FR1, based on the results provided by the following sources: + +- If the phase offset between hops in frequency hopping is compensated, for InF-SH, the positioning requirement for IIOT use cases can be achieved using frequency hopping with partial overlap for the purpose of phase offset compensation, + - Results in [111] show that UL TDOA can meet the requirements. + - Results in [111], [62], and [113] show that DL TDOA can meet the requirements. + - Results in [55], show that the requirement cannot be met, even if the phase is compensated. +- If the phase offset between hops in Frequency hopping is not compensated, + - Results in [62] and [119] show that DL TDOA can meet the requirements if the random phase offset is set to be equal or smaller than $0.4\pi$ . + - Results in [121] show that DL TDOA cannot meet the requirement with the random phase offset distributed from $[-\pi, \pi]$ . +- In FR2, based on the results provided by the following sources: + - Results in [71] show that the requirements can be met even if the phase is not compensated. + - Results in [62] show that PRS frequency hopping can improve positioning performance if the random phase between hops can be adjusted in FR2, InF-SH scenario. + +NOTE: Sources used different combinations of number of hops, gap size between hops and partial overlap sizes in their evaluations. + +Regarding the performance for positioning of Redcap UEs using Rx hopping for reception of the DL PRS or Tx hopping for transmission of the UL SRS in IIoT scenarios, considering time gap between hops: + +- In FR1 for InF SH, based on the results provided by the following sources: + - For UL-TDOA, results in [111] shows that the requirement can be met for a gap of 1ms and cannot be met for a gap of 5ms. + - For DL-TDOA, results in [111] shows that the requirement can be met for a gap of 1ms and cannot be met for a gap of 5ms. + - For DL-TDOA, results in [113] shows that the requirement can be met for a gap of 4ms. + - For DL-TDOA, results in [118] shows that the requirement can be met for a gap of 1ms and cannot be met for a gap of more than 2ms. + - For DL-TDOA, results in [132] shows that the requirement can be met for a gap of 5ms. + +Regarding the performance for positioning of Redcap UEs using Rx hopping for reception of the DL PRS in IIoT scenarios, considering timing error during the frequency hopping: + +- In FR1, for InF-SH, based on the results provided by the following sources: + - For DL-TDOA, results in [113] shows the IIOT horizontal accuracy requirement cannot be met if the timing error is 3ns. + - For DL-TDOA, results in [118] shows the IIOT horizontal accuracy requirement can be met if the timing error is 2ns, but cannot be met if the timing error is 3ns. + +Regarding the performance for positioning of Redcap UEs using frequency hopping in commercial scenarios, considering phase offset between hops: + +- In FR1, based on the results provided ([111], [71]), for the UMi positioning requirement for commercial use cases, positioning accuracy improvement is observed by two sources when the phase offset between hops in Frequency hopping is considered, if frequency hopping with partial overlap for the purpose of phase offset compensation is used, and if the phase offset is compensated. + +- Results in [111] show that positioning accuracy improvement is observed with UL TDOA with phase offset compensation, but requirements are not met. +- Results in [111] show that positioning accuracy improvement is observed with DL TDOA with phase offset compensation, but requirements are not met. +- Results in [71] show that positioning accuracy improvement is observed with Multi RTT with phase offset compensation, but requirements are not met. + +NOTE: Sources used different combinations of number of hops, gap size between hops and partial overlap sizes in their evaluations. + +Regarding the performance for positioning of Redcap UEs using Rx hopping for reception of the DL PRS or Tx hopping for transmission of the UL SRS in IIoT or commercial scenarios, considering time gap between hops together with UE speed: + +- In FR1, for InF-SH based on the results provided by the following sources: + - For UL-TDOA, results in [111] shows that the horizontal accuracy requirement can be met for a gap of 140us for UE speed of up to 120km/h. + - For DL-TDOA, results in [113] shows that the horizontal accuracy requirement can be met for a gap of 2 or 4 ms for UE speed of up to 30km/h, and cannot be met for 60km/h. + - For DL-TDOA, results in [118] shows that the requirement can be met for a gap of 0.1ms for UE speed of up to 150km/h; the horizontal accuracy requirement can be met for a gap of 0.2ms for UE speed of up to 60km/h; the horizontal accuracy requirement can be met for a gap of 0.5ms for UE speed of up to 30km/h; the horizontal accuracy requirement can be met for a gap of 1ms, 2ms, 5ms for UE speed of up to 3km/h. +- In FR1, for UMi, based on the results provided by the following sources: + - For multi-RTT, results in [128] shows that the requirement for commercial scenarios cannot be met, but performance of frequency hopping with 5 hops and 640 $\mu$ sec switching gap degrades only marginally for speeds of 30 or 60 kmh over 3 km/h. + +In FR1, for InF-SH, the performance of carrier phase positioning with RedCap UEs using 20MHz of bandwidth was evaluated without modeling the agreed error sources. Based on the reported results the following observations are made: + +- Results in [113] shows that with an estimated integer ambiguity, a redcap UE using CPP cannot meet the IIOT requirements. +- Results in [113], [114] show that a redcap UE using CPP can meet the IIOT requirement under ideal conditions and known integer ambiguity. +- Results in [118] shows that a redcap UE using CPP cannot meet the IIOT requirements with a fixed search range of integer ambiguity. +- Results in [127] shows that a redcap UE using CPP can meet the IIOT requirements, under some conditions for integer ambiguity resolution. +- Results in [128] shows that a redcap UE using phase-difference AoD improves performance over RSRPP-based AoD but cannot meet the IIoT requirements. +- Results in [132] shows that a redcap UE using CPP can meet the IIOT requirements if frequency hopping enhancements are also used and cannot meet the IIOT requirements without enhancements. + +### 6.5.3 Potential specification impact for positioning for RedCap UEs + +From RAN1's perspective, the following have been identified for potential specification impact to support NR positioning for RedCap UEs: + +- Maximum tolerable phase error, timing gap, and timing error between hops. + +- Considerations for IIoT, commercial, Public Safety and V2X scenarios, and UE capabilities. +- Details on the Tx or Rx hopping pattern(s), including frequency overlapping between hops, if supported. + +# 7 Conclusions + +## 7.0 Study objectives + +The scope of the Rel-18 study item on expanded NR positioning enhancements included various aspects of positioning features in NR systems involving the Uu and PC5 interfaces. These included sidelink (SL) positioning, including evaluation of bandwidth requirements, and performance for absolute and relative positioning, and ranging distance and angle determination; positioning enhancements for improved integrity, accuracy, and power efficiency via defining integrity characteristics for RAT-dependent positioning, PRS/SRS bandwidth aggregation, NR carrier phase positioning, LPHAP; and support of positioning for UEs with Reduced Capabilities (RedCap UEs). + +Based on the studies conducted in RAN working groups, the following conclusions are made. + +## 7.1 Scenarios and requirements for sidelink positioning + +Based on the study, the identified scenarios for the prioritized use-cases and related target requirements are summarized as in Table 7.1-1. + +**Table 7.1-1: Target accuracy requirements for SL positioning** + +| SL Positioning KPIs | V2X | Public Safety | IIoT | Commercial | +|---------------------------------|----------------------------------------------------------------------------------------|-------------------------------------------------------------|----------------------------------------------------|-------------------------------------------| +| Horizontal Positioning Accuracy | Set A (similar to "Set 2" defined in [3]): 1.5 m for 90% of UEs (absolute or relative) | 1 m for 90% of UEs (absolute or relative) | Set A: 1 m for 90% of UEs (absolute or relative) | 1 m for 90% of UEs (absolute or relative) | +| | Set B (similar to "Set 3" defined in [3]): 0.5 m for 90% of UEs (absolute or relative) | | Set B: 0.2 m for 90% of UEs (absolute or relative) | | +| Vertical Positioning Accuracy | Set A: 3 m for 90% of UEs (absolute or relative) | 2 m (absolute or relative between 2 UEs) for 90% of UEs | Set A: 1 m for 90% of UEs (absolute or relative) | 2 m for 90% of UEs (absolute or relative) | +| | Set B: 2 m for 90% of UEs (absolute or relative) | 0.3 m (relative positioning change for 1 UE) for 90% of UEs | Set B: 0.2 m for 90% of UEs (absolute or relative) | | +| Relative Speed | - | Up to 30 km/h | Up to 30 km/h | Up to 30 km/h | +| Angle Accuracy | Set A: $Y = \pm 15^\circ$ for 90% of the UEs | | | | +| | Set B: $Y = \pm 8^\circ$ for 90% of the UEs | | | | + +NOTE 1: For evaluated SL positioning methods, the performance results in Annex B.1 are described in terms of: + +- whether each of the two requirements are satisfied, and +- %-ile of UEs satisfying the target positioning accuracy for a requirement that may not be satisfied with 90%. + +NOTE 2: Target positioning requirements may not necessarily be reached for all scenarios and deployments + +NOTE 3: All positioning techniques may not achieve all positioning requirements in all scenarios. + +## 7.2 Bandwidth requirements for sidelink positioning + +Performance evaluation results reported as part of the study indicate that, depending on sources, use-cases, scenarios, assumptions, and positioning methods used, the identified target requirements can be satisfied with different values of SL PRS bandwidth choices. + +- For FR1 spectrum: + - For certain sources and combinations of use-cases, scenarios, assumptions, and positioning methods, some target requirements can be satisfied with SL PRS bandwidths of 20 MHz or 40 MHz. + - For certain sources and other combinations of use-cases, scenarios, assumptions, and positioning methods, some target requirements require SL PRS bandwidth of 100 MHz or may not be satisfied even with SL PRS bandwidth of 100 MHz. +- For FR2 spectrum, based on submitted results from up to two sources: + - For certain sources and combinations of use-cases, scenarios, assumptions, and positioning methods, some target requirements can be satisfied with SL PRS bandwidth of 200 MHz. + - For certain sources and combinations of use-cases, scenarios, assumptions, and positioning methods, some of the target requirements may not be satisfied even with SL PRS bandwidth of 400 MHz. + +From RAN1's perspective, it is recommended that SL PRS bandwidths of up to 100 MHz are supported by the specifications in FR1 spectrum. + +NOTE: The above recommendations are based on the evaluations in licensed and ITS spectra. + +## 7.3 Sidelink positioning solutions + +Sidelink positioning is recommended for normative work, including: + +- Sidelink positioning in-coverage, partial coverage and out-of-coverage scenarios may be supported. +- How to enable the procedures/signaling for supporting SL positioning in in-coverage, partial coverage and out-of-coverage scenarios will be further discussed in normative work. +- Protocols between UE and UE + - RAN2 will enable the support of SL PRS configuration in normative work based on the progress in RAN1. + - RAN2 will design protocol and procedures for SL positioning between UEs (SLPP) in normative work. +- Protocols between LMF and UE + - RAN2 will discuss the details of functionalities of LMF for supporting SL positioning in normative work. + - RAN2 will discuss the protocol details to support sidelink positioning procedures between UE and LMF in normative work. + +For the solutions for sidelink positioning, + +- The following two operation scenarios are recommended for normative work: + - Operation Scenario 1: PC5-only-based positioning. + - Operation Scenario 2: Combination of Uu- and PC5-based positioning. +- RTT-type solution(s) using SL, SL-AoA, and SL-TDOA are recommended for normative work. + - Both single-sided and double-sided RTT methods, striving to minimize the changes needed on top of the specification support for single-sided RTT, if any, for the introduction of double-sided RTT. + - For SL-TDOA, DL-TDOA-like operation and UL-TDOA-like operation is recommended for normative work. +- For the support of the above methods the following measurements are recommended for normative work: + - SL PRS based Rx-Tx measurement + - SL PRS based RSTD measurement + - SL PRS based RSRP measurement + - SL PRS based RSRPP measurement + - SL PRS based RTOA measurement + - SL PRS based Azimuth of Arrival (AoA) and SL Zenith of Arrival (ZoA) measurement. +- A new sidelink reference signal (SL PRS) is recommended for normative work. + - Such a reference signal should use a comb-based frequency domain structure and a pseudorandom-based sequence where the existing sequence of DL-PRS should be used as a starting point. + - SCI can be used for reserving/indicating one or more SL PRS resources. +- Both a resource allocation Scheme 1 and Scheme 2 is recommended for normative work, where Scheme 1 corresponds to a network-centric operation SL PRS resource allocation and Scheme 2 corresponds to UE autonomous SL PRS resource allocation. + - For resource allocation mechanism for SL PRS in Scheme 2, a sensing-based resource allocation, or a random resource selection, or both, should be introduced, where the legacy designs for UE autonomous resource allocation are used as a starting point. +- With regards to the SL PRS transmission, both dedicated resource pool and shared resource pool with Rel-16/Rel-17/Rel-18 SL communication are recommended for normative work. + - For SL Positioning resource (pre-)configuration in a shared resource pool with Rel-16/17/18 sidelink communication, backward compatibility with legacy Rel-16/17 UEs should be ensured. +- With regards to the power control for SL PRS at least Open Loop Power Control (OLPC) is recommended for normative work. +- Unicast, Groupcast (not including many to one) and Broadcast of SL PRS transmission are recommended for normative work. + +## 7.4 Integrity for RAT-dependent positioning techniques + +Both UE-based and LMF-based integrity for RAT-Dependent Positioning Techniques are recommended for normative work. + +## 7.5 PRS/SRS bandwidth aggregation + +Conclusions on support of PRS/SRS bandwidth aggregation from the studies performed in RAN1 can be found in [2]. + +As part of the current study, PRS/SRS bandwidth aggregation for intra-band contiguous carriers is studied by RAN4. Based on the study, PRS/SRS bandwidth aggregation for intra-band contiguous carriers is concluded as feasible for single chain Tx/Rx architectures at both the UE and gNB. + +The assumption for a single-chain Tx architecture is that PRS/SRS resources to be aggregated are transmitted from a single Tx antenna. + +PRS/SRS bandwidth aggregation across PFLs for positioning measurements is concluded as feasible from RRM perspective. + +## 7.6 NR carrier phase positioning + +Based on the study, it is concluded that it is feasible to use existing DL PRS and SRS signals to obtain the carrier phase measurements for achieving a horizontal accuracy of up to a few centimeters at least at 50% under certain conditions, including the PRU(s) being located in LOS with TRP(s), and the locations of the PRU(s) and TRPs known with centimeter-level accuracy, in the agreed evaluation assumptions. + +If NR CPP is introduced, + +- Existing DL PRS and UL SRS for positioning purpose are recommended as the reference signals to enable positioning based on NR carrier phase measurements for both UE-based and UE-assisted positioning. +- New measurements are recommended to be introduced for supporting UE-based and UE-assisted NR carrier phase positioning. +- Multipath mitigation methods for the carrier phase positioning are recommended to be introduced during normative work. + +## 7.7 Low power high accuracy positioning + +The study of Rel-18 LPHAP focused on the evaluation of whether the existing Rel-17 positioning techniques for UEs in RRC\_INACTIVE state can support the battery life and positioning requirements, and on the analysis of potential enhancements to address any limitations for UEs in RRC\_INACTIVE and/or RRC\_IDLE states, as outlined in Clause 6.4. + +The target use case for LPHAP is studied and confirmed that the use case 6 defined by SA1 as the single representative use case. The performance requirement of LPHAP use case 6 is defined, including horizontal accuracy, positioning interval, and battery life. It is assumed that the target horizontal positioning accuracy requirement on LPHAP of <1m can be achieved by Rel-16/17 positioning techniques with a positioning bandwidth of at least 100MHz. The main objective of the LPHAP evaluations from the perspective of lower layers is on UE power consumption, as outlined in Clause 6.4.1. + +The evaluations on the existing Rel-17 positioning techniques for UEs in RRC\_INACTIVE state show that the target battery life required by LPHAP use case 6 cannot be satisfied for majority of the evaluation scenarios that are examined. Based on the evaluation, it is concluded that enhancements to meet the target battery life in Rel-18 are necessary. + +The following enhancements for LPHAP are recommended for normative work: + +- For UL and DL+UL positioning for UEs in RRC\_INACTIVE state, the enhancements on SRS for positioning in order to avoid frequent RRC connection for SRS (re)configuration is recommended for normative work. +- Extending DRX cycle beyond 10.24s was studied and found beneficial towards meeting the battery life requirement for LPHAP and is recommended for normative work on Rel-18 positioning enhancements from physical layer's perspective. +- From physical layer's perspective, DL PRS measurement for UEs in RRC\_IDLE state is recommended for the normative work. + +Enhancements on simplified DL PRS configuration with 1-symbol PRS can be studied further and if needed, specified during normative phase. + +From RAN2's perspective, LPHAP is recommended for normative work, including: + +- Enhancements on SRS configuration + - SRS positioning validity area for UL positioning in RRC\_INACTIVE is recommended for normative work from RAN2's perspective if feasible from RAN1's perspective. + - SRS configuration request is recommended for normative work from RAN2's perspective. + - Pre-configuration of multiple SRS configurations (e.g., for multiple SRS positioning validity areas) is feasible from RAN2's perspective and recommended for normative work. +- Alignment between DRX and PRS is recommended for normative work. +- DL positioning in RRC\_IDLE is recommended for normative work. +- Skipping paging reception in RRC\_INACTIVE is recommended for normative work for achieving LPHAP requirements, if feasible and beneficial from RAN1's perspective. + +## 7.8 Positioning of UEs with reduced capabilities + +From RAN1's perspective, for positioning of RedCap UEs, support of PRS frequency hopping and SRS frequency hopping are recommended for normative work. + +- During the normative work, the complexity of the corresponding capabilities for RedCap UEs should be addressed for the introduction of appropriate capabilities for RedCap UEs. + +# Annex A: Evaluation methodologies + +## A.1 Evaluation methodology for sidelink positioning + +In this clause, the evaluation methodology and assumptions for evaluation of sidelink positioning methods are described. + +Table A.1-1 lists the performance metrics for evaluation of sidelink positioning. + +**Table A.1-1: Performance metrics for evaluations of sidelink positioning** + +| Evaluation case | Metrics | +|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Relative or absolute positioning |
  • - Horizontal accuracy
  • - Vertical accuracy
| +| Ranging |
  • - Ranging distance
  • - Ranging angle/direction
| +| Metrics to be reported |
  • - The percentiles of positioning/ranging accuracy error including 50%, 67%, 80%, 90% of UEs.
  • - CDF of positioning/ranging accuracy error
  • - For evaluated methods, sources are expected to report:
    • - whether the requirements are satisfied, and
    • - %-ile of UEs satisfying the target positioning accuracy for a requirement that may not be satisfied for 90% of the UEs.
| +| Other metrics | Performance metrics other than positioning accuracy, such as PHY/end-to-end latency, are up to companies | + +Tables A.1-2 through A.1-6 list the assumptions relevant to evaluation of all use-cases and those specific to each of the identified use-cases of V2X, public safety, commercial, and IIoT, respectively. + +**Table A.1-2: Evaluation assumptions common to all evaluations of sidelink positioning** + +| Assumptions | Value | +|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Simulation bandwidth |
  • - FR1: 10, 20, 40 and 100 MHz
  • - FR2: 100, 200 and 400MHz
| +| Reference signals for sidelink positioning |
  • - Baseline: Existing pattern and sequence of DL-PRS or positioning SRS
  • - Other choices of pattern and sequence not precluded – companies to provide details.
  • - AGC settling time is considered.
| +| PHY/link level abstraction | Explicit simulation of all links, individual parameters estimation is applied. Companies to provide description of applied algorithms for estimation of signal location parameters. | +| Network and anchor UE synchronization |
  • - Baseline: Perfect synchronization between network and anchor UEs in the evaluation is assumed.
    • - Network synchronization error and timing errors defined in Table 6-1 in TR 38.857 [2] can also be optionally used for synchronization between BS and BS, between BS and anchor UEs, and between anchor UEs.
| +| Sidelink anchor nodes |
  • - For evaluation of SL only positioning, anchor UEs are used to locate target UEs.
  • - For evaluation of Joint Uu/SL positioning, both BS and anchor UEs are used to locate target UEs.
  • - Baseline for absolute positioning: sidelink anchors location coordinates are perfectly known.
    • - Uncertainty in the sidelink anchors' location coordinates can be considered by companies
| +| UE-pair selection for ranging | Relative positioning or ranging is performed between two UEs within X m. Value(s) of X to be reported by companies. | +| Positioning method | To be reported by companies. | +| Additional considerations |
  • - Companies should report whether SL PRS and other SL signals are FDM-ed or not FDM-ed, and whether other SL signals are present.
  • - System level simulations (rather than link level simulations) are used as the baseline tool.
  • - For SL positioning evaluation in highway scenario or urban grid scenarios, performance metrics can include absolute horizontal accuracy, relative horizontal accuracy, ranging with distance accuracy, and ranging with direction accuracy (optionally).
  • - In highway and urban grid scenarios, other UE types, e.g., pedestrian UE or VRU devices may be further considered.
| + +**Table A.1-3: Evaluation assumptions for evaluations of sidelink positioning for V2X use-cases** + +| Assumptions | Value | | +|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenarios | V2X use-cases with highway and urban grid scenarios defined in TR 37.885 [8].
  • - Road configuration for urban grid and highway provided in Annex A in TR 37.885 [8] is reused.
| | +| | Urban grid for V2X | Highway for V2X | +| Carrier frequency | Uu: 4 GHz
SL: 6 GHz | Uu: 2 GHz or 4GHz
SL: 6 GHz | +| Deployment layout for absolute positioning |
  • - Alt 1 as optional: BS and UE-type RSU deployment follows TR 36.885, where wrap around method of 19*3 hexagonal cells with 500m ISD in Figure A.1.3-3 of clause A.1.3 in TR 36.885 [9] is used.
  • - Alt 2 as baseline: BSs are disabled, UE-type RSUs are uniformly located with 200m spacing on both sides of highway symmetrically.
  • - Optional: staggered/unsymmetrical UE-type RSU distribution like
| BS and UE-type RSU deployment follows the description in clause A.1.3 in TR 36.885 [9].
  • - Companies can provide results for additional BS/ UE-type RSU deployments, e.g., additional UE-type RSUs are added to UE-type RSU deployment in TR 36.885 [9].
| + +| Assumptions | Value | +|----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Diagram showing RSU deployment. Alt 1: Two RSUs on the same side of a road, 200m apart. Alt 2: RSUs on both sides of the road, staggered. NOTE: Alt 1 is assumed for evaluation of joint Uu/PC5 positioning, Alt 2 is assumed for evaluation of PC5-only positioning.

NOTE: Alt 1 is assumed for evaluation of joint Uu/PC5 positioning, Alt 2 is assumed for evaluation of PC5-only positioning.

| +| Deployment layout for relative positioning/ranging |
  • - BSs are disabled
  • - UE type RSU may be disabled (as baseline) or enabled (as optional)
    • - If enabled, UE-type RSUs are uniformly located with 200m spacing on both sides of highway symmetrically.
    • - Optional: staggered/unsymmetrical UE-type RSU distribution like Diagram showing staggered RSU deployment on both sides of a road with 200m spacing between RSUs on the same side.
  • - BSs are disabled (baseline), or enabled (optional)
    • - Companies to report their assumptions
  • - UE type RSU may be disabled or enabled (companies should report their assumption)
    • - If enabled, UE type RSU deployment follows the description clause A.1.3 in TR 36.885 [9].
    • - If enabled, companies can provide additional RSU deployment, e.g., additional RSUs are added to RSU deployment in TR 36.885 [9].
| +| BS Tx power | Macro BS: 49dBm | +| UE Tx power | Vehicle UE or UE type RSU: 23dBm | +| BS receiver noise figure | 5dB | +| UE receiver noise figure | 9 dB | +| UE dropping |

UE dropping option A defined in clause 6.1.2 of TR 37.885 [8]:

  • - UE dropping option A is used for the highway scenario:
    • - Vehicle type distribution: 100% vehicle type 2.
    • - Clustered dropping is not used.
    • - Vehicle speed is 140 km/h in all the lanes as baseline and 70 km/h in all the lanes optionally.
  • - UE dropping option A is used for the urban grid scenario:
    • - Vehicle type distribution: 100% vehicle type 2.
    • - Clustered dropping is not used.
    • - Vehicle speed is 60 km/h in all the lanes.

In the intersection, a UE goes straight, turns left, turns right with the probability of 0.5, 0.25, 0.25, respectively.

| +| UE antenna model |

Description in clause 6.1.4 in TR 37.885 [8] is reused:

  • - Vehicle UE option 1 is the baseline (Vehicle UE antenna is modelled in Table 6.1.4-8 and 6.1.4-9 in TR 37.885 [8])
  • - Vehicle UE option 2 (two panels) can be optionally selected by companies.
| +| Channel model | Description in clause 6.2 in TR 37.885 is reused. | + +**Table A.1-4: Evaluation assumptions for evaluations of sidelink positioning for public safety use-cases** + +| Assumptions | Value | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Overall assumptions | Companies to provide detailed simulation assumptions including selected scenarios, channel models, center frequency, UE drop models, etc. | +| Channel model |

Channel model in TR 36.843 is reused:

  • - Reuse the parameters of "Channel models" specified in Clause A.2.1.2 of TR 36.843 with following modification: Each component of channel model reuses what is specified in TR 38.901.
| +| Anchor UE height | To be reported by companies, e.g., same as TRP height. | + +| Assumptions | Value | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Performance metrics | At least include absolute positioning accuracy and ranging with distance accuracy.
- Optional: Relative positioning accuracy or ranging with angle/direction accuracy. | + +**Table A.1-5: Evaluation assumptions for evaluations of sidelink positioning for commercial use-cases** + +| Assumptions | Value | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Overall assumptions | Companies to provide detailed simulation assumptions including selected scenarios, channel models, center frequency, UE drop models, etc. | +| Channel model | Channel model in TR 36.843 is reused:
Reuse the parameters of "Channel models" specified in Clause A.2.1.2 of TR 36.843 with following modification: Each component of channel model reuses what is specified in TR 38.901. | +| Anchor UE height | To be reported by companies, e.g., same as TRP height. | +| Performance metrics | At least include absolute positioning accuracy and ranging with distance accuracy.
Optional: Relative positioning accuracy or ranging with angle/direction accuracy. | + +**Table A.1-6: Evaluation assumptions for evaluations of sidelink positioning for IIoT use-cases** + +| Assumptions | Value | +|-------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Deployment scenario and BS-to-UE channel models | InF-SH and/or InF-DH defined in TR 38.857 [2]. | +| UE-to-UE channel model |
  • - Option 1: BS-to-UE channel model defined in TR 38.901 [11] is revised:
    • - The UE parameters in the channel model defined in 38.901 [11], e.g., UE height, antenna model, transmit power are used to replace corresponding parameters for BS.
    • - Anchor UE height to be reported by companies, e.g., anchor UE height is the same as TRP.
  • - Option 2: D2D channel mode from 36.843 A.2.1.2 is used.
| +| Anchor UE dropping | Companies to report how to drop anchor UEs and how to select anchor UEs. | +| Performance metrics | At least include absolute and relative positioning accuracy. | + +## --- A.2 Void + +## --- A.3 Evaluation methodology for NR carrier phase positioning + +For evaluations of NR carrier phase positioning, the relevant evaluation assumptions as in TR 38.855 [12] and TR 38.857 [2] are reused, with optional modifications to the assumptions based on appropriate justification. + +Evaluations for FR1 bands are considered as baseline while those for FR2 bands are optional. + +For modelling of error sources, the following may be considered: + +- Phase noise (FR2) +- CFO/Doppler +- Oscillator-drift +- Transmitter/receiver antenna reference point location errors +- Transmitter/receiver initial phase error +- Phase center offset + +NOTE: Other error sources are not precluded + +NOTE: UE mobility can be considered in the evaluations + +NOTE: one or more error sources can be evaluated jointly + +NOTE: companies should provide the error sources model with their evaluations + +The impact of multipath will be considered as part of evaluations of NR carrier phase positioning, and the methods of mitigating the impact of multipath for the carrier phase positioning will be studied, if it is considered necessary after the evaluation. + +The following multipath mitigation methods for the carrier phase positioning, which include, but are not limited to, the following are to be evaluated: + +- The methods of estimating the carrier phase of the first path + - NOTE: Both time-domain and frequency-domain methods can be considered +- LOS/NLOS/ Multi-path indication for the carrier phase measurements for improving the accuracy of the position calculation + - Rel-17 LOS/NLOS indicator can be used as the starting point +- Measurements of the first path and additional paths + - E.g., carrier phase measurements, timing measurements +- Other channel information, such as RSRP/RSRPP, CIR/CFR, etc. + +Further, the use of PRUs to facilitate NR carrier phase positioning can be evaluated. + +Table A.3-1 provides the assumptions for the evaluation of NR carrier phase positioning. + +**Table A.3-1: Assumptions for evaluation of NR carrier phase positioning** + +| Assumptions | Value | | +|------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scenarios |
  • - Baseline: InF-SH, InF-DH
  • - Optional: Indoor Open Office, UMi, Highway scenarios
    • - Other evaluation scenarios are not precluded
    • - Existing Rel-17 DL/UL reference signals for the Uu interface are to be used for the Highway scenario.
| | +| Frequency errors – NOTE 1 | Ideal | Practical | +| Initial residual CFO (is the same for one measurement instances [or multiple phase measurement instances]) | 0 (UE/TRP) | Uniform distribution within:
  • - [-30, +30] Hz (FR1, UE), [-100, +100] Hz (FR1, UE),
  • - [-120, +120] Hz (FR2, UE), [-400, +400] Hz (FR2, UE),
  • - [-10, +10] Hz (for each TRP, FR1),
  • - [-40, +40] Hz (for each TRP, FR2).
| +| Oscillator-drift (is the same for one or multiple phase measurement instances for positioning fix) | 0 (UE/TRP) | Uniform distribution within:
  • - [-0.1, 0.1] ppm (UE)
  • - [-0.02, +0.02] ppm (each TRP) within measurement duration
| +| Antenna reference point (ARP) location error of a TRP | No ARP error | A zero-mean, truncated Gaussian distribution with zero mean and standard deviation of $T=[1, 5]$ cm truncated to $2T$ in each of (x, y, z) direction | +| Initial phase of a transmitter | Modelled as a random variable uniformly distributed within $[0, 2\pi]$
  • - The initial phase of a transmitter applies to all subcarriers of the same carrier frequency associated with the transmitter. The initial phases of a transmitter for different carriers can be assumed to be independent of each other.
| | + +| Assumptions | Value | +|-----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial phase of a receiver | Modelled as a random variable uniformly distributed within $[0, 2\pi]$
  • - The initial phase of a receiver applies to all subcarriers of the same carrier frequency associated with the receiver
  • - The initial phases of a receiver for different carriers can be assumed to be independent of each other.
| +| UE/TRP antenna Phase Center Offset (PCO) | $dPCO = a * dPhi + w$ ,
where
  • - a is the scale factor, a \in [0, 1, 3]
  • - dPhi is the direction difference (in degrees):
    • - Example 1: dPhi is the difference between the true and the calculated (or measured) directions between a transmitter (UE/TRP) and a receiver (TRP/UE).
    • - Example 2: dPhi is the direction difference between one UE to two TRPs, or between one TRP to two UEs.
    • - NOTE: Example 1 may be more suitable for modelling the residual PCO of a calibrated antenna; while Example 2 may be more suitable for modelling the PCO of an uncalibrated antenna (see [91]).
  • - w is 0 or a random variable uniformly distributed within [-2, +2], or [-5, +5], or [-X, +X] degrees
    • - Value of X is left up to companies
  • - NOTE: the above model is valid only when absolute value of dPhi < Y degrees
    • - Value of Y is left up to companies
| +| Time instances for carrier phase measurements | UE position can be calculated by the use of carrier phase measurements obtained at the $M$ sequential time instances, where
  • - Baseline:
    • - M=1
  • - Optional:
    • - M=4
  • - Other values of M
    • - Companies should report their assumptions on UE mobility (e.g., speed)
| + +NOTE 1: The Doppler frequency can be determined based on the UE speed in the evaluation assumption. + +## A.4 Evaluation methodology for low power high accuracy positioning + +Table A.4-1 lists the common assumptions for evaluation of LPHAP. + +**Table A.4-1: Evaluation assumptions common to all evaluations of LPHAP** + +| Assumptions | Value | +|----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Frequency range | FR1 baseline; FR2 optional | +| SCS | 30kHz for FR1 (baseline); 120kHz for FR2 (optional) | +| Bandwidth of the DL PRS and UL SRS for positioning | 100 MHz | +| Measurements per position fix | Single-sample measurement per position fix (baseline); 4-sample measurement per position fix (optional) | +| UE mobility | Up to 3 km/h | +| Power consumption modelling – basic considerations |
  • - Power consumption of 5GC data traffic is not modelled and only the power consumption of the traffic type related to LPHAP positioning (e.g., obtaining/updating SRS configurations, DL PRS measurement reporting, etc.) is considered.
    • - Consideration of power consumption due to paging monitoring is not precluded for baseline evaluation.
  • - Up to each company to provide detailed power model and evaluation results on power consumption in FR2.
  • - Adopt the power consumption model, additional transition energy and total transition time of the three sleep types (deep sleep, light sleep, and micro sleep) in TR38.840 [13] as the evaluation baseline.
| +| Periodicity of DL PRS / UL SRS for positioning | Baseline: 1 DL PRS / UL SRS for positioning occasion per N I-DRX cycle(s)
  • - Candidate values of N to evaluate is 1 and 8 for I-DRX cycle of 1.28s.
    • - Up to companies to select one or both of the above values.
  • - Candidate value of N to evaluate is 1 for I-DRX cycle of 10.24s.
| +| I-DRX configuration | Included in the baseline evaluations
  • - I-DRX cycles: 1.28s (baseline); 10.24s (optional)
  • - NOTE: This does not preclude the case where no I-DRX cycle nor paging is considered in the evaluation of potential solutions to maximize the battery life.
| +| e-DRX and/or paging reception | The following may be optionally considered:
  • - e-DRX cycles to evaluate: 20.48s; 30.72s.
  • - For paging reception:
    • - 1 paging occasion is included in one eDRX cycle
    • - 10% paging rate
  • - No paging reception can be optionally evaluated.
  • - 1 DL PRS and/or UL SRS for positioning occasion per 1 eDRX cycle
    • - Minimizing the gap between PRS measurement, SRS transmission and/or measurement reporting with paging monitoring in time domain can be evaluated.
| +| Positioning Reference Signal Bandwidth assumption | At least when the positioning accuracy is evaluated without jointly evaluating the associated power consumption, the target horizontal positioning accuracy requirement on LPHAP of <1m is assumed to be achieved by Rel-16/17 positioning techniques with a positioning bandwidth of at least 100 MHz. | + +For conversion between relative power unit and device battery lifetime to identify any performance gaps, the following characterization is considered: + +- Battery life is used as the metric to identify the gap + +$$T2 = \frac{P1 * T1 * K}{X} * \frac{C2}{C1} * \frac{1}{P2}$$ + +$$\text{Gap}_{\text{BatLife}} = T2_{\text{req}} - T2$$ + +in which, + +- C1 is the battery capacity of the reference device +- T1 is the battery life of the reference device +- P1 = 50 is the relative power unit obtained based on the reference traffic type +- X is the percentage of the power consumed by the reference traffic type +- C2 is the battery capacity of the LPHAP device + +- P2 is the evaluated relative power unit of the LPHAP device +- T2\_req is the target battery life of the LPHAP device +- K is an implementation factor, K = 1 (baseline); K = 0.5, 2, 4 (optional) + +NOTE: In the above model, the voltage is assumed to be the same for the reference device and the LPHAP device. + +NOTE: As the reference device and LPHAP device characteristics, and therefore the parameter values of the model for determining battery life, is dependent on implementation factors, manufacturer, design options and cost options, it is up to individual company to evaluate the optional K values, and report the corresponding parameter values. + +Examples of these parameters are provided as in Table A.4-2. + +**Table A.4-2: Example values of parameters for conversion between power consumption unit and device battery lifetime** + +| C1 (mAh) | T1 (hours) | X | Reference traffic type | C2 (mAh) | T2_req (months) | +|----------|------------|------|------------------------|-----------------------------------------------------------------------------------|-----------------| +| 4500 | 12 | 20 % | FTP (model 3) | 800 for Type A LPHAP device (baseline)
4500 for Type B LPHAP device (optional) | 6 to 12 | + +The power consumption model used for baseline evaluation of Rel-17 positioning in RRC\_INACTIVE state is as in Table A.4-3. + +**Table A.4-3: Power consumption model for baseline evaluation of Rel-17 positioning in RRC\_INACTIVE state** + +| Power State | Relative power | +|----------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PDCCH-only ( $P_{PDCCH}$ ) | 50 NOTE | +| PDCCH + PDSCH ( $P_{PDCCH+PDSCH}$ ) | 120 | +| SSB proc. ( $P_{SSB}$ ) | 50 | +| UL | 250 (0 dBm)
700 (23 dBm) | +| (Optional) PRACH | 210 | +| (Optional) BWP switching | 50 | +| (Optional) Intra-frequency RRM measurement ( $P_{intra}$ ) | 60 (synchronous case, N=8, measurement only; $P_{intra, meas-only}$ )
80 (combined search and measurement; $P_{intra, search+meas}$ ) | +| (Optional) Inter-frequency RRM measurement ( $P_{inter}$ ) | 60 (measurement only per freq. layer; $P_{inter, meas-only}$ )
150 (neighbor cell search power per freq. layer; $P_{inter, search-only}$ )
Micro sleep power assumed for switch in/out a freq. layer | +| NOTE: Power scaling to 20MHz reception bandwidth follows the rule in Clause 8.1.3 of TR 38.840, i.e., max {reference power * 0.4, 50}. | | + +For the purpose of LPHAP evaluation, an ultra-deep sleep state is considered with the two modelling options as in Table A.4-4. + +**Table A.4-4: Power consumption model for ultra-deep sleep state** + +| Parameters | Values | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| Model A (NOTE 1): | | +| Relative power unit | 0.015 | +| Additional transition energy | 10000 (NOTE 2) | +| Total transition time | 400 ms | +| Model B (NOTE 1, NOTE 3): | | +| Relative power unit | 0.01 | +| Additional transition energy | 480 | +| Total transition time | 25 ms | +| Restrictions in processing associated with Model B after the UE comes out of ultra-deep sleep state can be considered further. | | +| NOTE 1: No new device type is expected based on ultra-deep sleep power modelling.
NOTE 2: Power consumption analysis from individual companies with additional transition energy of 5000 can be optionally evaluated.
NOTE 3: Power consumption analysis from individual companies with Model B can be optionally evaluated. | | + +For DL PRS-based positioning, the following reference configuration is assumed: + +- Number of Positioning Frequency Layers = 1; +- Number of DL PRS resources measured per slot = 8; +- DL PRS instance of smaller than or equal to 1 slot duration. + +The power consumption model for DL PRS-based positioning and UL SRS-based positioning are as in Tables A.4-4 and A.4-5 respectively. + +**Table A.4-5: Power consumption model for DL PRS-based positioning** + +| N: Number of TRPs for DL PRS measurement | Synchronous case (baseline) | | Asynchronous case (optional) | | +|------------------------------------------|-----------------------------|----------------|------------------------------|-----| +| | FR1 (baseline) | FR2 (optional) | FR1 | FR2 | +| N=4 (baseline) | 120 | 195 | 140 | 255 | +| N=8 (optional) | 150 | 225 | 170 | 285 | + +**Table A.4-6: Power consumption model for UL SRS-based positioning** + +| Power State | Relative power | +|-------------|-----------------------------------| +| SRS | 210 (baseline);
700 (optional) | + +For DL positioning, at least the following power components and parameter values are considered for the baseline evaluation of Rel-17 RRC\_INACTIVE positioning: + +- For UE-assisted DL positioning, + - SSB proc. with 2 ms duration and the periodicity of I-DRX cycle; + - Paging with 2 ms duration, the periodicity of I-DRX cycle, and group paging rate of 10%; + - DL PRS measurement with 0.5 ms duration; + - CG-SDT with 1ms duration and the periodicity of positioning interval; + - RRCRelease after the CG-SDT can be optionally included with [1] ms duration; + - (Optional) BWP switching with [1] ms duration; + - (Optional) Intra-/inter-frequency RRM measurement in low SINR condition with [1] ms duration; + +- (Optional) RA-SDT (e.g., including CORSET0 + SIB1, PRACH, RAR, Msg 3/4/5) in case of CG-SDT is unavailable. +- For UE-based DL positioning, + - SSB proc. with 2 ms duration and the periodicity of I-DRX cycle; + - Paging with 2 ms duration, the periodicity of I-DRX cycle, and group paging rate of 10%; + - DL PRS measurement with 0.5 ms duration; + - (Optional) BWP switching with [1] ms duration; + - (Optional) Intra-/inter-frequency RRM measurement in low SINR condition with [1] ms duration. + +For UL positioning, at least the following power components and parameter values are considered for the baseline evaluation of Rel-17 RRC\_INACTIVE positioning: + +- SSB proc. with 2 ms duration and the periodicity of I-DRX cycle; +- Paging with 2 ms duration, the periodicity of I-DRX cycle, and group paging rate of 10%; +- UL SRS for positioning transmission with 0.5 ms duration; +- (Optional) BWP switching with [1] ms duration; +- (Optional) Intra-/inter-frequency RRM measurement in low SINR condition with [1] ms duration. + +In addition to the above, the following should be noted for DL and UL positioning in modelling the power components and timelines: + +- The power component and parameter values for DL and UL positioning are respectively applicable to the DL and UL parts of UE-assisted DL+UL positioning method. +- Additional power components and different parameter values for those in brackets above can be considered in the evaluation. +- Companies are encouraged to provide the assumption on the timeline between different power consumption events in the evaluation of potential enhancements to reduce the transition times between different power states and to extend the sleeping time as much as possible. + +## A.5 Evaluation methodology for positioning for RedCap UEs + +In this clause, the evaluation methodology and assumptions for evaluation of positioning performance for Reduced Capability (RedCap) NR UEs are described. + +For evaluation of RedCap UE positioning performances, all RAT based positioning methods can be considered. Sources should detail the chosen method(s) when presenting performance evaluations. + +Table A.5-1 lists the set of common parameters applicable for evaluation of positioning performance of RedCap UEs. + +**Table A.5-1: Common parameters applicable for all scenarios for Redcap UEs evaluations** + +| Assumptions | FR1 Specific Values | FR2 Specific Values | +|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------| +| Carrier frequency, GHz | 3.5GHz, 700MHz (optional) – NOTE 1 | 28GHz – NOTE 1 | +| Bandwidth, MHz | 20MHz baseline, 5MHz optional | 100MHz | +| Subcarrier spacing, kHz | 30KHz, 15KHz (for 700MHz carriers) | 120kHz | +| Positioning Reference Signals | DL PRS and/or UL SRS.
Sources to detail the chosen configuration of reference signal(s) | | +| Deployment scenarios |
  • - Baseline: (Case 1): UMi street canyon, as described in Table 6.1-1-4 of TR 38.855
  • - Optional outdoor:
    • - (Case 2): UMa, as described in Table 6.1-1-6 of TR 38.855
    • - (Case 3): RMa, companies to report parameters assumed for evaluations.
| | + +| Assumptions | FR1 Specific Values | FR2 Specific Values | +|-----------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
  • - Baseline (Case 4): InF-SH as described in Table 6.1-1 of TR 38.857
  • - Optional indoor (Case 5): Indoor Open Office, as described in Table 6.1-1-3 of TR 38.855
  • - Optional indoor (Case 6): InF-DH as described in Table 6.1-1 of TR 38.857
| | +| gNB model parameters | | | +| gNB noise figure, dB | 5dB | 7dB | +| gNB antenna configuration | At 700MHz:
(M,N,P,Mg,Ng) = (4,2,2,1,1), (dH, dV) = (0.5, 0.8) $\lambda$ – NOTE 3 | | +| UE model parameters | | | +| UE noise figure, dB | 9dB – NOTE 1 | 13dB – NOTE 1 | +| UE max. TX power, dBm | 23dBm – NOTE 1 | 23dBm – NOTE 1
EIRP should not exceed 43 dBm. | +| UE antenna radiation pattern | Omni, 0dBi | Antenna model according to Table 6.1.1-2 in TR 38.855 | +| UE antenna configuration | Panel model 1 – NOTE 1
dH = 0.5 $\lambda$ ,
for 1Rx UEs: (M, N, P, Mg, Ng) = (1, 1, 1, 1, 1)

for 2Rx UEs: (M, N, P, Mg, Ng) = (1, 1, 2, 1, 1) |
  • - (M, N, P, Mg, Ng) = (1, 2, 2, 1, 1) as minimum antenna configuration (baseline)
  • - (M, N, P, Mg, Ng) = (2, 2, 2, 1, 1) as optional configuration.
| +| UE antenna radiation pattern | Omni, 0dBi | Antenna model according to Table 6.1.1-2 in TR 38.855 | +| Number of UE branches | Baseline: 1Rx 1Tx
Optional: 2Rx 1 Tx | Baseline: 2Rx and 1Tx | +| PHY/link level abstraction | Explicit simulation of all links, individual parameters estimation is applied. Companies to provide description of applied algorithms for estimation of signal location parameters. | | +| Network synchronization | The network synchronization error, per UE dropping, is defined as a truncated Gaussian distribution of (T1 ns) rms values between a gNB and a timing reference source which is assumed to have perfect timing, subject to the largest timing difference of T2 ns, where $T2 = 2*T1$
  • - That is, the range of timing errors is [-T2, T2]
  • - T1: 0ns (perfectly synchronized), 50ns (Optional)
| | +| UE/gNB RX and TX timing error | (Optional) The UE/gNB RX and TX timing error, in FR1/FR2, can be modeled as a truncated Gaussian distribution with zero mean and standard deviation of T1 ns, with truncation of the distribution to the [-T2, T2] range, and with $T2=2*T1$ :
  • - T1: X ns for gNB and Y ns for UE
  • - X and Y are up to sources
  • - NOTE: RX and TX timing errors are generated per panel independently
Apply the timing errors as follows:
  • - For each UE drop,
  • - For each panel (in case of multiple panels)
  • - Draw a random sample for the Tx error according to [-2*Y,2*Y] and another random sample for the Rx error according to the same [-2*Y,2*Y] distribution.
  • - For each gNB
  • - For each panel (in case of multiple panels)
  • - Draw a random sample for the Tx error according to [-2*X,2*X] and another random sample for the Rx error according to the same [-2*X,2*X] distribution.
  • - Any additional Time varying aspects of the timing errors, if simulated, can be left up to each company to report.
  • - For UE evaluation assumptions in FR2, it is assumed that the UE can receive or transmit at most from one panel at a time with a panel activation delay of 0ms.
| | +| Selection of RedCap UEs for indoor scenarios for reporting of results |
  • - (Required): The UEs inside the convex hull of the horizontal BS deployment area.
  • - (Optional): All the UEs.
| | +| For the evaluation of TX/RX frequency hopping for positioning of RedCap UEs, value of time gap between two consecutive hops | Includes at least from 100us to 5ms
  • - Sources should indicate if other smaller values are used in their evaluations and justify the feasibility of smaller values.
| | +| For the evaluation of TX/RX frequency hopping for positioning of | 3 km/h, 30 km/h, 60km/h.
  • - Other values are not precluded.
| | + +| Assumptions | FR1 Specific Values | FR2 Specific Values | +|-------------------------------------|---------------------|---------------------| +| RedCap UEs, value of UE speed | | | +| NOTE 1: According to TR 38.802 [14] | | | +| NOTE 2: According to TR 38.901 [11] | | | +| NOTE 3: According to TR38.830 [15] | | | + +# --- Annex B: Evaluation results + +## --- B.1 Evaluation results for sidelink positioning + +Please see separate MS Word file for Annexes B.1, B.2, B.3. + +## --- B.2 Evaluation results for integrity for RAT-dependent positioning techniques + +Please see separate MS Word file for Annexes B.1, B.2, B.3. + +## --- B.3 Void + +## --- B.4 Evaluation results for NR carrier phase positioning + +Please see separate MS Word file for Annex B.4. + +## --- B.5 Evaluation results for low power high accuracy positioning + +Please see separate MS Word file for Annex B.5. + +## --- B.6 Evaluation results for positioning for RedCap UEs + +Please see separate MS Word file for Annexes B.6 and X. + +# Annex X: Change history + +| Change history | | | | | | | | +|----------------|-------------------------------------------------|------------|----|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-05 | RAN1#109-e | R1-2205398 | | | | Baseline TR skeleton. | 0.0.0 | +| 2022-08 | RAN1#110 | R1-2208275 | | | | Incorporating decisions from RAN1 #109-e and RAN1 #110 | 0.1.0 | +| 2022-10 | RAN1#110bis-e | R1-2210715 | | | | Incorporating decisions from RAN1 #109-e, RAN1 #110, and RAN1 #110bis-e | 0.2.0 | +| 2022-11 | RAN1#111,
RAN2#120,
RAN3#118,
RAN4#105 | R1-2213017 | | | | Revised from RAN1#110bis-e version (not endorsed by RAN1) and includes and incorporating decisions from RAN1 #111, RAN2 #120, RAN3 #118, and RAN4 #105. | 0.2.0 | +| 2022-12 | RAN #98e | RP-223289 | | | | v1.0.0, based on RAN1-endorsed v0.2.0, submitted to RAN #98e for approval | 1.0.0 | +| 2022-12 | RAN #98e | | | | | TR under change control further to the approval for inclusion in Rel-18 by RAN | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38870/01809458963aa10a19f3dc0f6a292535_img.jpg b/marked/Rel-18/38_series/38870/01809458963aa10a19f3dc0f6a292535_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0dce6df6c44bcf46b9b60e1fa42d637fead2b0a --- /dev/null +++ b/marked/Rel-18/38_series/38870/01809458963aa10a19f3dc0f6a292535_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e89bc5953aee08f6c37ede9ccbbb7cec4c4d0286cfd776ecd6070f70298e06e6 +size 12851 diff --git a/marked/Rel-18/38_series/38870/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/Rel-18/38_series/38870/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85273c6377750ce4017a1fe5ffece751a287655d --- /dev/null +++ b/marked/Rel-18/38_series/38870/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fa94e202d802e333a013d9351b0e1748d7b211b56b5f2daa1acb3a73f41c440 +size 13197 diff --git a/marked/Rel-18/38_series/38870/07b17a620c75522d53916a11e12d1bff_img.jpg b/marked/Rel-18/38_series/38870/07b17a620c75522d53916a11e12d1bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e2adeb0575f17a63bae79a56909e3e300876c67 --- /dev/null +++ b/marked/Rel-18/38_series/38870/07b17a620c75522d53916a11e12d1bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35d19c86ebf4c99d5529c1fe1f4ad06b914f07252300cbed71b17465f5133612 +size 26653 diff --git a/marked/Rel-18/38_series/38870/07f537f57749b75157f742525e6a8dbc_img.jpg b/marked/Rel-18/38_series/38870/07f537f57749b75157f742525e6a8dbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a6c1053cfc06c7e7499909695d435563176afdb --- /dev/null +++ b/marked/Rel-18/38_series/38870/07f537f57749b75157f742525e6a8dbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf85c7071d5d9c149fba2540e67da803a0ce69daa0ece2b85cea4fdea162e52f +size 79654 diff --git a/marked/Rel-18/38_series/38870/0a12cc47f3c5ca76c39d5943ba8661bd_img.jpg b/marked/Rel-18/38_series/38870/0a12cc47f3c5ca76c39d5943ba8661bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0de20d4555d1031596b15da34fb010391311b431 --- /dev/null +++ b/marked/Rel-18/38_series/38870/0a12cc47f3c5ca76c39d5943ba8661bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a82f78f1e1240924e924fbad8da6f8959b2f0c74cdfee077c05f0ed978e1e54 +size 41201 diff --git a/marked/Rel-18/38_series/38870/0a90113d6c8989e8b3c89c5cf9f926d7_img.jpg b/marked/Rel-18/38_series/38870/0a90113d6c8989e8b3c89c5cf9f926d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..337b4000a7f89f2d292df70e95fe6d30d3d7c0b2 --- /dev/null +++ b/marked/Rel-18/38_series/38870/0a90113d6c8989e8b3c89c5cf9f926d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7b391aa1f581bb154ff90011df5a8d2ff531faf829fb16d1225019e0c866fce +size 71463 diff --git a/marked/Rel-18/38_series/38870/0e62b4ac2303ba5f3ff10123a7c0f273_img.jpg b/marked/Rel-18/38_series/38870/0e62b4ac2303ba5f3ff10123a7c0f273_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e266f6ad856fdf4e9d3026953b9c240f86292f16 --- /dev/null +++ b/marked/Rel-18/38_series/38870/0e62b4ac2303ba5f3ff10123a7c0f273_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c28842c22891790de66b7d5c1733ac3609915616f2aa68c8a0e32c72688db5d5 +size 36355 diff --git a/marked/Rel-18/38_series/38870/10953d657a5f47fdc829a800419dd370_img.jpg b/marked/Rel-18/38_series/38870/10953d657a5f47fdc829a800419dd370_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad289d188dc27b3c3873476b2543df53949957d4 --- /dev/null +++ b/marked/Rel-18/38_series/38870/10953d657a5f47fdc829a800419dd370_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0dbd22d172b83432c804d27890f7b618fa1cfa51c277ee3c9dd42d2f9b65f6a8 +size 17215 diff --git a/marked/Rel-18/38_series/38870/1408b3d336e1d80c7a1abd0682f4f687_img.jpg b/marked/Rel-18/38_series/38870/1408b3d336e1d80c7a1abd0682f4f687_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c7ca36e0d034a143f1f03ab483669f55230286a --- /dev/null +++ b/marked/Rel-18/38_series/38870/1408b3d336e1d80c7a1abd0682f4f687_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55961df9cb2d85b7e34b3a06acd924c48bdb5a1c391ff5ab7d6628b2b9d1b557 +size 53853 diff --git a/marked/Rel-18/38_series/38870/1559db1c389771b44f7dc11d48b06079_img.jpg b/marked/Rel-18/38_series/38870/1559db1c389771b44f7dc11d48b06079_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee14ecbb8c2187132de20f5c4abc2dca087843ed --- /dev/null +++ b/marked/Rel-18/38_series/38870/1559db1c389771b44f7dc11d48b06079_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2832dc109ab756bb49e41f6b02ac7cde70b5b360222e65dd20bf7a21813e1c2f +size 31879 diff --git a/marked/Rel-18/38_series/38870/16d55682e067062054970d108f3d4723_img.jpg b/marked/Rel-18/38_series/38870/16d55682e067062054970d108f3d4723_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..323f49ce58f38914311727da7393ae283f5438c9 --- /dev/null +++ b/marked/Rel-18/38_series/38870/16d55682e067062054970d108f3d4723_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1be278baef5289dc3ffba8c9f0567d99f785cd938a9aa14a49d15a21d67b6e0 +size 23845 diff --git a/marked/Rel-18/38_series/38870/17a042ee648d9fdaddb609aead503980_img.jpg b/marked/Rel-18/38_series/38870/17a042ee648d9fdaddb609aead503980_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43cdab53fd3e449db269caa2375fcd24362297cb --- /dev/null +++ b/marked/Rel-18/38_series/38870/17a042ee648d9fdaddb609aead503980_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f8fa85310991590b431ed7c84ced12054663c7839f48fe6690f4764bd314ba8 +size 12972 diff --git a/marked/Rel-18/38_series/38870/258c1507ae7e731f704a016f660cd469_img.jpg b/marked/Rel-18/38_series/38870/258c1507ae7e731f704a016f660cd469_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d051613b8ec895e70547deb522e8a6f4c1802738 --- /dev/null +++ b/marked/Rel-18/38_series/38870/258c1507ae7e731f704a016f660cd469_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa40621cc1a7df31c581111b3af8b91ecd11bf8e480cd43c5cf8e90827abd505 +size 29188 diff --git a/marked/Rel-18/38_series/38870/2bb31852174adbb3a45abf75f593ac36_img.jpg b/marked/Rel-18/38_series/38870/2bb31852174adbb3a45abf75f593ac36_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95deefc80a7bdf025519e33e5e90e6596054113e --- /dev/null +++ b/marked/Rel-18/38_series/38870/2bb31852174adbb3a45abf75f593ac36_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3f0116a3a365f2772911744da11fced765c57ae3c2cb8e4a61d33b8c3c89820 +size 9756 diff --git a/marked/Rel-18/38_series/38870/2bc39576969969ffe6d3f3d5264bba75_img.jpg b/marked/Rel-18/38_series/38870/2bc39576969969ffe6d3f3d5264bba75_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6e6349c1595d23d7349886fc0dc1770ef60b968 --- /dev/null +++ b/marked/Rel-18/38_series/38870/2bc39576969969ffe6d3f3d5264bba75_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f33c6ffa3186b00d7a9f9d262506ec843538ab85bba6086678d214e11baddf06 +size 11221 diff --git a/marked/Rel-18/38_series/38870/35afbfc3c4a5c0fe01e91ba536605e09_img.jpg b/marked/Rel-18/38_series/38870/35afbfc3c4a5c0fe01e91ba536605e09_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..baa8a93a3765fa31a28f13859edd7484993ebedc --- /dev/null +++ b/marked/Rel-18/38_series/38870/35afbfc3c4a5c0fe01e91ba536605e09_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e1b14f8e0ead962ca27f85b009e87e8c49475b5063419d88434d7545eaae913 +size 45395 diff --git a/marked/Rel-18/38_series/38870/3ad4d1734817fe2ac05fe8d4da4f68e8_img.jpg b/marked/Rel-18/38_series/38870/3ad4d1734817fe2ac05fe8d4da4f68e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a1ca506f5fa9b7be26898346bea8a82212a1fc7 --- /dev/null +++ b/marked/Rel-18/38_series/38870/3ad4d1734817fe2ac05fe8d4da4f68e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7b1069b461278133b085b84d5991a207ef9a474042791d280e878e34e2e161d +size 29467 diff --git a/marked/Rel-18/38_series/38870/475caf31ae90b878f12d651b689cc9d1_img.jpg b/marked/Rel-18/38_series/38870/475caf31ae90b878f12d651b689cc9d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..460b057040f1d5a605d074d47eaa8219d76e0531 --- /dev/null +++ b/marked/Rel-18/38_series/38870/475caf31ae90b878f12d651b689cc9d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc115b65f3d836b6e3c9095b9d18d5faa451f5b0bcc839e8ffd7a6ee390e4f83 +size 31388 diff --git a/marked/Rel-18/38_series/38870/48f188337e3ba41df38fab9ac0afb1bd_img.jpg b/marked/Rel-18/38_series/38870/48f188337e3ba41df38fab9ac0afb1bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de9cdc670e3c8076b937d3c012f6ad181e08e494 --- /dev/null +++ b/marked/Rel-18/38_series/38870/48f188337e3ba41df38fab9ac0afb1bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:304bcbaaa723d365cb2dc35e3d4660920ef1f4f1fbc7240ce9fd1f3240a5b7f4 +size 50902 diff --git a/marked/Rel-18/38_series/38870/505116873ad67b610dfceb37016d04a3_img.jpg b/marked/Rel-18/38_series/38870/505116873ad67b610dfceb37016d04a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c09043709f15d707a4b43cc543b05ff298f0f14a --- /dev/null +++ b/marked/Rel-18/38_series/38870/505116873ad67b610dfceb37016d04a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a414b668c8ee27a6fb8a2de8f027fe765c5fa603ce27b60ea4d118615fbe1cc5 +size 73819 diff --git a/marked/Rel-18/38_series/38870/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-18/38_series/38870/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a8f15c777b880afc560ed4f30fca33a1b8a1077 --- /dev/null +++ b/marked/Rel-18/38_series/38870/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ce049802f805cadaa9a80e78f5f3f0fbeeccf1784db1f17f0064d2839febc33 +size 125597 diff --git a/marked/Rel-18/38_series/38870/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38870/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52c6f136a54cb9c6bddbbe9ddafb95d3873256d0 --- /dev/null +++ b/marked/Rel-18/38_series/38870/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4f5faae188faead3656507fd833fcce34044c122e5e42f5433f4f40a51066c3 +size 9330 diff --git a/marked/Rel-18/38_series/38870/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38870/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d103894fedf7f7cf002336ea035489bb3e1f45b --- /dev/null +++ b/marked/Rel-18/38_series/38870/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2973f6b14213a527e57fa5d26d142ed841846a9035adc4e7ba8b28f201eb5932 +size 5203 diff --git a/marked/Rel-18/38_series/38870/69edc2887e907309499ac95b47ab6905_img.jpg b/marked/Rel-18/38_series/38870/69edc2887e907309499ac95b47ab6905_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc576e88377288894d3eca978cabe4a54df004ea --- /dev/null +++ b/marked/Rel-18/38_series/38870/69edc2887e907309499ac95b47ab6905_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09cbc7f24259a12b7f0902910e8de3598768870e6c881b89a6fea0d35fe9bc49 +size 22297 diff --git a/marked/Rel-18/38_series/38870/6bbc398f520a7bcc5491cab18d3e4cac_img.jpg b/marked/Rel-18/38_series/38870/6bbc398f520a7bcc5491cab18d3e4cac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..483201fc79182b6fd98749a6e67b0f61db7d5585 --- /dev/null +++ b/marked/Rel-18/38_series/38870/6bbc398f520a7bcc5491cab18d3e4cac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fcc3a9699e6096fe1e0422754e114d9608c9b1d14d0fe82458070cb9fab8b61e +size 82149 diff --git a/marked/Rel-18/38_series/38870/6d06e66b7a838f8c809884aeee597a5e_img.jpg b/marked/Rel-18/38_series/38870/6d06e66b7a838f8c809884aeee597a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f86f2001110f41af5a53de1d9a7d31519accff68 --- /dev/null +++ b/marked/Rel-18/38_series/38870/6d06e66b7a838f8c809884aeee597a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02d47aba41895e3b48eff0562a698d93df97fefdd626259452bc197fdc607b94 +size 29829 diff --git a/marked/Rel-18/38_series/38870/6de7dcb072cef2388026fb0f504084b2_img.jpg b/marked/Rel-18/38_series/38870/6de7dcb072cef2388026fb0f504084b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e461c41ed7b8b50b72e632eb0ce3216a485f968c --- /dev/null +++ b/marked/Rel-18/38_series/38870/6de7dcb072cef2388026fb0f504084b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca02faf593a37239bd6f5b5b214f95161b923a2e36a3f0b9b25311546dd349eb +size 56817 diff --git a/marked/Rel-18/38_series/38870/6f1efa91fb9b476380af7a35db4f14bf_img.jpg b/marked/Rel-18/38_series/38870/6f1efa91fb9b476380af7a35db4f14bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3eb31d188237b14385303cb061e6d6bd33d7c70 --- /dev/null +++ b/marked/Rel-18/38_series/38870/6f1efa91fb9b476380af7a35db4f14bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07ef48f305fad352b272528a18e90edb90ac0dd9dcc701e4b6a2b82121fcd9ed +size 76273 diff --git a/marked/Rel-18/38_series/38870/9455ca65b9fc488df790769b0122628e_img.jpg b/marked/Rel-18/38_series/38870/9455ca65b9fc488df790769b0122628e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7136485c569722444fd2598b4fb47e182807d5df --- /dev/null +++ b/marked/Rel-18/38_series/38870/9455ca65b9fc488df790769b0122628e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46445bb5fc34f45c403c87708832962292481771cb95f05605762dde1dcf174d +size 33473 diff --git a/marked/Rel-18/38_series/38870/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-18/38_series/38870/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fd267f7b0172b0ce2da34f212345a317a085f10 --- /dev/null +++ b/marked/Rel-18/38_series/38870/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dfb6d87b7790195d9c9476d772e1184d381cf5d50a4ae043a38fc8ed2562adb8 +size 18845 diff --git a/marked/Rel-18/38_series/38870/9d1abc573e35610946ece87a18cbe862_img.jpg b/marked/Rel-18/38_series/38870/9d1abc573e35610946ece87a18cbe862_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5d6cbe155004ce4df8713dc4a8bb7416a1edd28 --- /dev/null +++ b/marked/Rel-18/38_series/38870/9d1abc573e35610946ece87a18cbe862_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d755cc00ba30fedf2b13c2af5e2d301906b4ee4dc331b610a03efafb586aeb8d +size 48329 diff --git a/marked/Rel-18/38_series/38870/9d71890acd754a1325e9415e44a7dacb_img.jpg b/marked/Rel-18/38_series/38870/9d71890acd754a1325e9415e44a7dacb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aea4c5659812b3b9fd36e527cf7097f7351065b3 --- /dev/null +++ b/marked/Rel-18/38_series/38870/9d71890acd754a1325e9415e44a7dacb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:baa47dfc1c67ec515015694c831d84190f2e3211408a513c7e362c96ac805767 +size 27405 diff --git a/marked/Rel-18/38_series/38870/a0fa8bc25d670cde3905dff620b401ae_img.jpg b/marked/Rel-18/38_series/38870/a0fa8bc25d670cde3905dff620b401ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c35e58de738513a6bf4a865c1789badbdac2e990 --- /dev/null +++ b/marked/Rel-18/38_series/38870/a0fa8bc25d670cde3905dff620b401ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9645390d787d6dd8c054c1d72d8a1c10e1d300f892bd4403592d832e1839810a +size 12351 diff --git a/marked/Rel-18/38_series/38870/acdccfc1d546eaad16a58be576456caf_img.jpg b/marked/Rel-18/38_series/38870/acdccfc1d546eaad16a58be576456caf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d984d711d5ce76cf7d8c506d071a333297538a6 --- /dev/null +++ b/marked/Rel-18/38_series/38870/acdccfc1d546eaad16a58be576456caf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f63e4752efb2485c674a25a05b736341316730920fdcf219db47ac6d0adc4585 +size 15009 diff --git a/marked/Rel-18/38_series/38870/b15e3860e0c96ed16ce77f032da6f107_img.jpg b/marked/Rel-18/38_series/38870/b15e3860e0c96ed16ce77f032da6f107_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed5fca78ef75b20e3856c8e242174f5a27bad1c3 --- /dev/null +++ b/marked/Rel-18/38_series/38870/b15e3860e0c96ed16ce77f032da6f107_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afa5c6528cd31e2b13dd82ad897b31fa72263f13a4677c1183621581108743b1 +size 60977 diff --git a/marked/Rel-18/38_series/38870/b48d146cf1d6e0a01791f52572be6767_img.jpg b/marked/Rel-18/38_series/38870/b48d146cf1d6e0a01791f52572be6767_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3efe8a4db525c2f6235831ebe5961fcbdb9f0708 --- /dev/null +++ b/marked/Rel-18/38_series/38870/b48d146cf1d6e0a01791f52572be6767_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb450db7efabf27a01e7130f58a476dc3bde7f3507a62d6ee8ed5c9e00d86195 +size 10136 diff --git a/marked/Rel-18/38_series/38870/b7251436a2a3c0d1c00c3e935df2a8f5_img.jpg b/marked/Rel-18/38_series/38870/b7251436a2a3c0d1c00c3e935df2a8f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7afaf9549c2be84b57c1d511560e512b189c2c78 --- /dev/null +++ b/marked/Rel-18/38_series/38870/b7251436a2a3c0d1c00c3e935df2a8f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4154e97650cec0c6d3f74998ba4b0f0da69dbd1a56f81d7c7aea8aeb4e285265 +size 103587 diff --git a/marked/Rel-18/38_series/38870/bac51fe73fcd6bf16764b3096edc5cdf_img.jpg b/marked/Rel-18/38_series/38870/bac51fe73fcd6bf16764b3096edc5cdf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4631b0c580aa4361c24a63871e53e57102a8fe24 --- /dev/null +++ b/marked/Rel-18/38_series/38870/bac51fe73fcd6bf16764b3096edc5cdf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99f7211e086a9aa63889513b17c89254a1cd1163f2dddde675532fc4bae7b071 +size 15047 diff --git a/marked/Rel-18/38_series/38870/bfbc4537f78dc2abb796e35936eba3ec_img.jpg b/marked/Rel-18/38_series/38870/bfbc4537f78dc2abb796e35936eba3ec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7040f4b4c5e1a54a9db58210f8c78c6cac39d1e4 --- /dev/null +++ b/marked/Rel-18/38_series/38870/bfbc4537f78dc2abb796e35936eba3ec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ee3a7337c066d695d8dd8df13f76c504fbd31aa8e6b671fc818517adc8c8965 +size 16222 diff --git a/marked/Rel-18/38_series/38870/c1c7af7ea36be0323047962df57d75b0_img.jpg b/marked/Rel-18/38_series/38870/c1c7af7ea36be0323047962df57d75b0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78995434b9b624855026aabfdb4dd12335d88bed --- /dev/null +++ b/marked/Rel-18/38_series/38870/c1c7af7ea36be0323047962df57d75b0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6aedcd473a099d22ba4c6befff54064906b2207b70ee3b34e21bf99961745c8 +size 48203 diff --git a/marked/Rel-18/38_series/38870/c222a9006d6d60a8d81e6ffbfc0e74ad_img.jpg b/marked/Rel-18/38_series/38870/c222a9006d6d60a8d81e6ffbfc0e74ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f22573e123e9c2f984a64d89da0d64e129e56a70 --- /dev/null +++ b/marked/Rel-18/38_series/38870/c222a9006d6d60a8d81e6ffbfc0e74ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57cfe5e1ee7fecc9a4d6ec1937ea5926192435b1bb2244f70df07712905fb28a +size 45494 diff --git a/marked/Rel-18/38_series/38870/c37fe03d7cad74ad675a0eb16aa43821_img.jpg b/marked/Rel-18/38_series/38870/c37fe03d7cad74ad675a0eb16aa43821_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b3d3892319badedc2cd94a05c25ade28aabbfa8 --- /dev/null +++ b/marked/Rel-18/38_series/38870/c37fe03d7cad74ad675a0eb16aa43821_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c7e5689a823f2bdd1a54021e83862730b240fdb094bc62d2ec1b4f194a4f49e +size 24391 diff --git a/marked/Rel-18/38_series/38870/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg b/marked/Rel-18/38_series/38870/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5151d5ad37478fafde6255c930da9a15ce2c53d2 --- /dev/null +++ b/marked/Rel-18/38_series/38870/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba764ebb922e1f9b32ddf26f241bb27e826bb71d4764571916aeb613f3bc4668 +size 16322 diff --git a/marked/Rel-18/38_series/38870/c97b176986d994192dd844e17cd08e3a_img.jpg b/marked/Rel-18/38_series/38870/c97b176986d994192dd844e17cd08e3a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f73f6375ac09fd6171f363626337fa5c9513d2b9 --- /dev/null +++ b/marked/Rel-18/38_series/38870/c97b176986d994192dd844e17cd08e3a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de8861afd965d95f5fb8b7a119745c9cbdec6bebc0a1ba23da729f0df5bddd1a +size 14810 diff --git a/marked/Rel-18/38_series/38870/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-18/38_series/38870/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7754b57f4ea331e376d6f135129758dd873cb06 --- /dev/null +++ b/marked/Rel-18/38_series/38870/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e9cc569a1585ab96bbf95fdf8c93e610b775ba79aff082b1c02cd0209951805 +size 33590 diff --git a/marked/Rel-18/38_series/38870/d244183a8ff3d94b0dcf30140f51020d_img.jpg b/marked/Rel-18/38_series/38870/d244183a8ff3d94b0dcf30140f51020d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eeb832cb643202499d8f5b65ba526951d9db9d8e --- /dev/null +++ b/marked/Rel-18/38_series/38870/d244183a8ff3d94b0dcf30140f51020d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb45fe06e3f337eb2403c9c0bb9646fd785dbd45101612897cff4073f9f2c99b +size 30868 diff --git a/marked/Rel-18/38_series/38870/de5063b406eb787334c453b07b7dcc52_img.jpg b/marked/Rel-18/38_series/38870/de5063b406eb787334c453b07b7dcc52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f02f200f8d8fd53141af7bafd0b29c0ff74c48cd --- /dev/null +++ b/marked/Rel-18/38_series/38870/de5063b406eb787334c453b07b7dcc52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ea38339785f8e65ef399643c689b7eabc11957923fd5699dc83c2be86ee9115 +size 22568 diff --git a/marked/Rel-18/38_series/38870/e2c1c672349c10dccb2563eff6d8260e_img.jpg b/marked/Rel-18/38_series/38870/e2c1c672349c10dccb2563eff6d8260e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53af365ef4ef5b3d16f8bccb2ab790eb4034b17a --- /dev/null +++ b/marked/Rel-18/38_series/38870/e2c1c672349c10dccb2563eff6d8260e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d380a5017878d6366177d2ead3cbe9fd3a9a8c2b1502827a2ef20850abe52198 +size 28763 diff --git a/marked/Rel-18/38_series/38870/e384b831b3fb26071365a8ad1add04f1_img.jpg b/marked/Rel-18/38_series/38870/e384b831b3fb26071365a8ad1add04f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..471ab39d275ff448a8d43224ab9852ed096f05ab --- /dev/null +++ b/marked/Rel-18/38_series/38870/e384b831b3fb26071365a8ad1add04f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed76644c0e7d7060bd423475368e3cb16e7f4ceda61a8e2e4251131bd8b14af7 +size 25196 diff --git a/marked/Rel-18/38_series/38870/e8ff6e66c77a8e96203c9f8db8f0986f_img.jpg b/marked/Rel-18/38_series/38870/e8ff6e66c77a8e96203c9f8db8f0986f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83feda9bf104d380e987b5ba2ee925fe4da20936 --- /dev/null +++ b/marked/Rel-18/38_series/38870/e8ff6e66c77a8e96203c9f8db8f0986f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:912642ead86a55dc68db2cb7d58a464089f76c0c3f8077a40070e2d1ea2687e6 +size 22135 diff --git a/marked/Rel-18/38_series/38870/eb903413d070b64f45cd763804ba443f_img.jpg b/marked/Rel-18/38_series/38870/eb903413d070b64f45cd763804ba443f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..246bec572c1469bf6c986fa3c03a0f95551715ef --- /dev/null +++ b/marked/Rel-18/38_series/38870/eb903413d070b64f45cd763804ba443f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a517b2878d027cdb1ecc0209dfd8407f4182e486797bdc50a51a185f14e5a47b +size 30013 diff --git a/marked/Rel-18/38_series/38870/ec761cfe33c3b66a15601aa23f217a51_img.jpg b/marked/Rel-18/38_series/38870/ec761cfe33c3b66a15601aa23f217a51_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..724b2cb23c89bd9b3a1c484157c76a300c318022 --- /dev/null +++ b/marked/Rel-18/38_series/38870/ec761cfe33c3b66a15601aa23f217a51_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ae855beea6c3662a33ce133e1cf19660c8849d1cd14ad8518953e84e9aee359 +size 18154 diff --git a/marked/Rel-18/38_series/38870/f01b22e5bb303653828200595aece414_img.jpg b/marked/Rel-18/38_series/38870/f01b22e5bb303653828200595aece414_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e6e539c720806824edb5a8b6f456df248619c20 --- /dev/null +++ b/marked/Rel-18/38_series/38870/f01b22e5bb303653828200595aece414_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:731456dc1c9f5f7c409eacbd814e642e0d420eb6fff20f02913aabe2282d4679 +size 24287 diff --git a/marked/Rel-18/38_series/38870/ff3eabf79233f3aa25a5df258f50427a_img.jpg b/marked/Rel-18/38_series/38870/ff3eabf79233f3aa25a5df258f50427a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df083a3729568d952b5b1de076cb228e06fd1e47 --- /dev/null +++ b/marked/Rel-18/38_series/38870/ff3eabf79233f3aa25a5df258f50427a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54fbef05078ad545fccbf0aaede77404f4703f04e4ddc349d273a94e9747f0f9 +size 12332 diff --git a/marked/Rel-18/38_series/38870/raw.md b/marked/Rel-18/38_series/38870/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3e1fab5934c1bf1684875fd79ed907366c6b5c18 --- /dev/null +++ b/marked/Rel-18/38_series/38870/raw.md @@ -0,0 +1,3254 @@ +# **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Enhanced Over-the-Air (OTA) test methods for NR FR1 Total Radiated Power (TRP) and Total Radiated Sensitivity (TRS) (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. 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 + +## **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 + +| | | +|-----------------------------------------------------------------------------|----| +| TOC \o "1-9" Foreword..... | 7 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions of terms, symbols and abbreviations..... | 10 | +| 3.1 Terms..... | 10 | +| 3.2 Symbols..... | 11 | +| 3.3 Abbreviations ..... | 11 | +| 4 General..... | 11 | +| 4.1 Device types..... | 11 | +| 4.2 Testing configuration ..... | 12 | +| 4.2.1 UE use scenarios for TRP TRS test..... | 12 | +| 4.2.2 UE mechanical mode description..... | 12 | +| 4.3 Testing bands..... | 12 | +| 4.3.1 General ..... | 12 | +| 4.3.2 Operating bands..... | 12 | +| 4.3.3 Test parameters for each band..... | 13 | +| 4.3.4 EN-DC band combinations..... | 19 | +| 4.3.5 CA band combinations ..... | 21 | +| 5 Performance metrics ..... | 22 | +| 5.1 Definition of the Total Radiated Power (TRP) ..... | 22 | +| 5.1.1 Definition of the Total Radiated Power (TRP) for AC ..... | 22 | +| 5.1.2 Definition of the Total Radiated Power (TRP) for RC method..... | 23 | +| 5.2 Definition of Total Radiated Sensitivity (TRS) ..... | 23 | +| 5.2.1 Definition of the Total Radiated Sensitivity (TRS) for AC ..... | 23 | +| 5.2.2 Definition of the Total Radiated Sensitivity (TRS) for RC method..... | 24 | +| 6 UE positioning guidelines..... | 24 | +| 6.1 Free space..... | 24 | +| 6.2 Hand phantom only (Browsing mode)..... | 25 | +| 6.2.1 Wide Grip Hand ..... | 25 | +| 6.2.2 PDA Grip Hand ..... | 26 | +| 6.3 Head and Hand phantom (Talk Mode)..... | 27 | +| 6.3.1 General ..... | 27 | +| 6.3.2 Wide Grip Hand and Head ..... | 28 | +| 6.3.3 PDA Grip Hand and Head..... | 28 | +| 6.4 Head phantom only ..... | 28 | +| 6.5 Forearm phantom ..... | 28 | +| 6.5.1 Forearm Phantom placement in the chamber ..... | 28 | +| 6.5.2 Wrist-Worn RedCap Device mounted on the Forearm Phantom ..... | 29 | +| 7 Anechoic Chamber method (Reference method)..... | 30 | +| 7.1 General ..... | 30 | +| 7.2 Test setup..... | 30 | +| 7.3 Calibration procedure..... | 31 | +| 7.4 TRP Test procedure..... | 32 | +| 7.4.1 General ..... | 32 | +| 7.4.2 TRP test procedure for NR 1Tx configuration ..... | 32 | +| 7.4.2.1 UE configuration..... | 32 | +| 7.4.2.2 Test procedure..... | 32 | +| 7.4.3 TRP test procedure for NR 2Tx configuration ..... | 33 | +| 7.4.3.1 UE configuration..... | 33 | +| 7.4.3.2 TxD TRP Test procedure..... | 33 | +| 7.4.3.3 Single-layer UL-MIMO TRP Test procedure..... | 33 | +| 7.4.4 TRP test procedure for NR DL CA configuration..... | 34 | +| 7.4.4.1 UE configuration..... | 34 | + +| | | | +|-------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|-----------| +| 7.4.4.2 | Test procedure..... | 34 | +| 7.5 | TRS Test procedure..... | 34 | +| 7.5.1 | General ..... | 35 | +| 7.5.2 | TRS test procedure for NR 1Tx configuration ..... | 35 | +| 7.5.2.1 | UE configuration..... | 35 | +| 7.5.2.2 | Test Procedure ..... | 35 | +| 7.5.3 | TRS test procedure for NR 2Tx configuration ..... | 35 | +| 7.5.3.1 | UE configuration..... | 35 | +| 7.5.3.2 | Test procedure..... | 36 | +| 7.5.4 | TRS test procedure for NR DL CA configuration..... | 36 | +| 7.5.4.1 | UE configuration..... | 36 | +| 7.5.4.2 | Test procedure..... | 36 | +| 7.6 | Ripple Test for Quiet Zone..... | 36 | +| 7.6.1 | General ..... | 36 | +| 7.6.2 | Ripple test procedure..... | 37 | +| 7.7 | Minimum Range Length ..... | 40 | +| 8 | Reverberation Chamber test methodology..... | 42 | +| 8.1 | General ..... | 42 | +| 8.2 | Test setup..... | 42 | +| 8.3 | Chamber Characterization..... | 43 | +| 8.3.1 | S-parameters and power transfer functions ..... | 43 | +| 8.3.2 | Chamber loading for coherence bandwidth..... | 43 | +| 8.3.2.1 | Coherence bandwidth calculation..... | 44 | +| 8.3.3 | Chamber spatial uniformity ..... | 45 | +| 8.4 | Calibration procedure..... | 46 | +| 8.4.1 | S-parameters measurement..... | 46 | +| 8.4.2 | Calculation of the chamber reference transfer function ..... | 47 | +| 8.5 | TRP Test procedure..... | 48 | +| 8.5.1 | TRP for SA and EN-DC ..... | 48 | +| 8.5.1.1 | Test conditions..... | 48 | +| 8.5.1.2 | UE configurations ..... | 48 | +| 8.5.1.3 | Test procedure..... | 48 | +| 8.6 | TRS Test procedure..... | 49 | +| 8.6.1 | TRS for SA and EN-DC ..... | 49 | +| 8.6.1.1 | Test conditions..... | 49 | +| 8.6.1.2 | UE configurations ..... | 49 | +| 8.6.1.3 | Test procedure..... | 49 | +| 8.7 | Test Volume..... | 49 | +| 9 | Testing time reduction methodologies..... | 50 | +| 9.1 | General ..... | 50 | +| 9.2 | Measurement grids for Anechoic Chamber method ..... | 50 | +| 9.3 | Other solutions ..... | 62 | +| Annex A: UE coordinate system ..... | | 62 | +| A.1 | Reference coordinate system ..... | 62 | +| Annex B: Estimation of Measurement uncertainty ..... | | 64 | +| B.1 | General..... | 64 | +| B.2 | MU contribution descriptions for Anechoic Chamber method..... | 65 | +| B.2.1 | Mismatch uncertainty..... | 65 | +| B.2.1.1 | Mismatch uncertainty between measurement receiver / communication tester and the measurement antenna..... | 65 | +| B.2.1.1.1 | Mismatch uncertainty through the connector between two elements..... | 65 | +| B.2.1.1.2 | Mismatch uncertainty due to the interaction of several elements..... | 66 | +| B.2.1.1.3 | Total combined mismatch uncertainty..... | 67 | +| B.2.1.2 | Mismatch uncertainty of the RF relay ..... | 67 | +| B.2.1.2.1 | First part: RF Relay switched on the co-polarized signal..... | 68 | +| B.2.1.2.1.1 | The mismatch through the connector between two elements ..... | 68 | +| B.2.1.2.1.2 | Mismatch due to the interaction between two elements or more ..... | 68 | + +| | | | +|-------------|----------------------------------------------------------------------|----| +| B.2.1.2.2 | Second part: RF relay switched on the cross-polarized signal ..... | 69 | +| B.2.1.2.2.1 | The mismatch through the connector between two elements ..... | 69 | +| B.2.1.2.2.2 | Mismatch due to the interaction between two elements or more ..... | 69 | +| B.2.1.2.3 | Total combined mismatch uncertainty ..... | 70 | +| B.2.2 | Insertion loss ..... | 70 | +| B.2.2.1 | Insertion loss of the measurement antenna cable ..... | 70 | +| B.2.2.2 | Insertion loss of the measurement antenna attenuator (if used) ..... | 70 | +| B.2.2.3 | Insertion loss of the RF relays (if used) ..... | 70 | +| B.2.2.4 | Insertion loss: calibration antenna feed cable ..... | 70 | +| B.2.2.5 | Insertion loss: calibration antenna attenuator (if used) ..... | 70 | +| B.2.3 | Influence of the antenna cable ..... | 71 | +| B.2.3.1 | Measurement antenna cable ..... | 71 | +| B.2.3.2 | Calibration antenna cable ..... | 71 | +| B.2.4 | Measurement receiver: uncertainty of the absolute level ..... | 71 | +| B.2.5 | Communication tester: uncertainty of the absolute level ..... | 71 | +| B.2.6 | Sensitivity measurement: output level step resolution ..... | 71 | + +| | | | +|----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|-----------| +| B.2.7 | Measurement distance ..... | 71 | +| B.2.7.1 | Offset of phase centre from axis(es) of rotation ..... | 72 | +| B.2.7.1.1 | Offset of DUT phase centre from axis(es) of rotation ..... | 72 | +| B.2.7.1.2 | Offset of calibration antenna phase centre from axis(es) of rotation ..... | 72 | +| B.2.7.2 | Mutual coupling ..... | 72 | +| B.2.7.3 | Phase curvature ..... | 72 | +| B.2.8 | Quality of quiet zone ..... | 73 | +| B.2.9 | DUT Tx-power drift ..... | 73 | +| B.2.10 | DUT sensitivity drift ..... | 74 | +| B.2.11 | Uncertainty related to the use of phantoms ..... | 74 | +| B.2.11.1 | Uncertainty from using different types of SAM phantom ..... | 74 | +| B.2.11.2 | Simulated tissue liquid uncertainty ..... | 74 | +| B.2.11.3 | Uncertainty of dielectric properties and shape of the hand phantom ..... | 74 | +| B.2.11.4 | Uncertainty from using different types of Laptop Ground Plane phantom ..... | 76 | +| B.2.11.5 | Positioning Uncertainty from using Phantoms ..... | 76 | +| B.2.11.6 | Uncertainty of dielectric properties and shape of the forearm phantom ..... | 76 | +| B.2.12 | Coarse sampling grid ..... | 77 | +| B.2.13 | Random uncertainty ..... | 77 | +| B.2.14 | Frequency response ..... | 78 | +| B.2.15 | Uncertainty of network analyser ..... | 78 | +| B.2.16 | Uncertainty of the gain/efficiency of the calibration antenna ..... | 78 | +| B.3 | MU contribution descriptions for Alternative method ..... | 78 | +| B.3.1 | Additional Power Loss in EUT Chassis ..... | 78 | +| B.3.3 | Quality of Spatial Uniformity ..... | 79 | +| B.3.4 | Sensitivity measurement: output level step resolution ..... | 79 | +| B.4 | MU Assessment for TRP ..... | 79 | +| B.4.1 | MU Assessment for TRP in Anechoic Chamber ..... | 79 | +| B.4.2 | MU Assessment for TRP in Reverberation Chamber ..... | 83 | +| B.5 | MU Assessment for TRS ..... | 85 | +| B.5.1 | MU Assessment for TRS in Anechoic Chamber ..... | 85 | +| B.5.2 | MU Assessment for TRS in Reverberation Chamber ..... | 90 | +| Annex C: Environmental requirements ..... | | 94 | +| C.1 | Scope ..... | 94 | +| C.2 | Ambient temperature ..... | 94 | +| C.3 | Operating voltage ..... | 94 | +| Annex D: Phantom Definition ..... | | 95 | +| D.1 | Head Phantom ..... | 95 | +| D.2 | Hand Phantom ..... | 95 | +| D.2.1 | PDA Grip Hand ..... | 95 | +| D.2.2 | Wide Grip Hand ..... | 95 | +| D.3 | Forearm Phantom ..... | 96 | +| Annex E: Harmonization outcome of Alternative method and Reference method ..... | | 97 | +| Annex F: Lab alignment outcome of Reference method ..... | | 98 | +| F.1 | General ..... | 98 | +| F.2 | Rel-17 lab alignment campaign (Browsing mode) ..... | 98 | +| F.2.1 | Framework and workplan ..... | 98 | +| F.2.2 | Measurement results ..... | 100 | +| F.2.3 | Pass/fail limit ..... | 101 | +| F.2.4 | Conclusions ..... | 101 | +| F.3 | Rel-18 lab alignment (Talk mode) ..... | 101 | +| F.3.1 | Framework and workplan ..... | 101 | + +F.3.2 Measurement results..... 101 +F.3.3 Pass/fail limit..... 101 +F.3.4 Conclusions ..... 101 +**Annex G (informative): Change history..... 102** + +# --- 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 enhanced Over-the-Air (OTA) test methods for NR FR1 Total Radiated Power (TRP) and Total Radiated Sensitivity (TRS), for NR standalone (SA) and NR non-standalone (NSA) operation mode. + +In Rel-17, the TRP TRS OTA test method was just developed for a limited scope. This TR targets to define a full set of OTA test methods to cover different UE features for TRP and TRS measurement. + +# --- 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 38.827: "Study on radiated metrics and test methodology for the verification of multi-antenna reception performance of NR User Equipment (UE)". +- [3] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone". +- [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". +- [5] 3GPP TS 38.521-1: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Range 1 Standalone". +- [6] 3GPP TS 38.521-3: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 3: Range 1 and Range 2 Interworking operation with other radios". +- [7] 3GPP TS 38.508-1: "5GS; User Equipment (UE) conformance specification; Part 1: Common test environment". +- [8] 3GPP TR 25.914: "Measurements of radio performances for UMTS terminals in speech mode". +- [9] IEEE Std 149: "IEEE Standard Test Procedures for Antennas", IEEE. +- [10] JCGM 100:2008: "Evaluation of measurement data — Guide to the expression of uncertainty in measurement". +- [11] ETSI TR 102 273-1-1: "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 1: Introduction". +- [12] ETSI TR 100 028-2: "ElectroMagnetic Compatibility and Radio Spectrum Matters (ERM); Uncertainties in the measurement of mobile radio equipment characteristics; Part 2". + +- [13] 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”. +- [14] CTIA Certification™: “CTIA Certification Test Plan for Wireless Device Over-the-Air Performance, CTIA 01.71 Device Setup and Positioning Guidelines”, latest active version available at: +- [15] Foegelle, M.D., “The Surface Standard Deviation Method for TRP Measurement Uncertainty”, 25th Proceedings of the Antenna Measurement Techniques Association (AMTA 2003), A03-027 +- [16] 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 “. +- [17] 3GPP TS 37.544: “Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) Over The Air (OTA) performance; Conformance testing “. +- [18] 3GPP TR 37.941: “Radio Frequency (RF) conformance testing background for radiated Base Station (BS) requirements” +- [19] 3GPP TR 38.810: “NR; Study on test methods” +- [20] 3GPP TR 38.903, “NR; Derivation of test tolerances and measurement uncertainty for User Equipment (UE) conformance test cases” +- [21] “Reverberation Chamber Metrology for Wireless Internet of Things Devices”, Anouk Hubrechtsen, Kate A. Remley and Sara Catteau, IEEE Microwave Magazine, February 2022, pp.75-85 +- [22] “Proximity and antenna orientation effects for large-form-factor devices in a reverberation chamber” Willem T. C. Burger, Kate A. Remley, Christopher L. Holloway, John M. Ladbury, 2013 IEEE International Symposium on Electromagnetic Compatibility, pp.671-676 +- [23] “A Significance Test for Reverberation-Chamber Measurement Uncertainty in Total Radiated Power of Wireless Devices”, Kate A. Remley, Chih-Ming Jack Wang, Dylan F. Williams, Johannes J. aan den Toorn and Christopher L. Holloway, IEEE TRANSACTIONS ON ELECTROMAGNETIC COMPATIBILITY, VOL. 58, NO. 1, FEBRUARY 2016, pp.207-219 +- [24] 3GPP TR 38.834: “Measurements of User Equipment (UE) Over-the-Air (OTA) performance for NR FR1; Total Radiated Power (TRP) and Total Radiated Sensitivity (TRS) test methodology (Release 17)” +- [25] CTIA Certification™: “CTIA Certification Test Plan for Wireless Device Over-the-Air Performance, CTIA 01.72: Near-Field Phantoms”, latest active version available at: +- [26] CTIA Certification™: “CTIA Certification Test Plan for Wireless Device Over-the-Air Performance, CTIA 01.70: Measurement Uncertainty”, latest active version available at: + +# --- 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]. + +**Browsing mode usage:** This mode corresponds to “data” mode, the device is tested via hand-only phantoms. + +**Primary mechanical mode:** The mode that is most often used for a specific user scenario. Every terminal has at least one primary mechanical mode, if multiple modes are supported, different primary mechanical modes may be applicable + +for different user scenarios, e.g., different primary mechanical modes for Browsing mode usage and Talk mode usage for the same UE. + +**Talk mode usage:** This mode corresponds to “talk” mode, the device is tested via head&hand phantoms. + +**Wrist-worn mode usage:** This mode corresponds to wearable device for wrist-worn mode, the device is tested via forearm phantoms. + +## 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]. + +| | | +|---------|-------------------------------------------------------------------------------------------------------| +| AC | Anechoic Chamber | +| BHHL | Beside Head and Hand Left Side (Head and Hand Phantom) | +| BHHR | Beside Head and Hand Right Side (Head and Hand Phantom) | +| CA | Carrier Aggregation | +| DUT | Device Under Test | +| E-UTRA | Evolved UTRA | +| EIRP | Effective Isotropic Radiated Power | +| EUT | Equipment Under Test | +| FR1 | Frequency Range 1 | +| FS | Free Space | +| HL | Hand Left (Hand Phantom Only) | +| HR | Hand Right (Hand Phantom Only) | +| MPR | Allowed maximum power reduction | +| NR | New Radio | +| NSA | Non-Standalone, a mode of operation where operation of an other radio is assisted with an other radio | +| OTA | Over The Air | +| QZ | Quiet Zone | +| RedCap | Reduced Capability | +| SA | Standalone | +| SS | System Simulator | +| TAA | Time-Averaging Algorithm | +| TAS | Tx Antenna Switching | +| TRP | Total Radiated Power | +| TRS | Total Radiated Sensitivity | +| TxD | Tx Diversity | +| UE | User Equipment | +| UL MIMO | Uplink Multiple Antenna transmission | + +# --- 4 General + +## 4.1 Device types + +The following device types are within the scope of enhanced FR1 TRP TRS WI: + +- Smartphone + - Considering UEs with antenna configurations of 1Tx, 2Tx, 2 Rx and 4 Rx +- wearable Redcap UE +- Tablet + +- Laptop embedded equipment (LEE) +- Laptop mounted equipment (LME) + +## 4.2 Testing configuration + +### 4.2.1 UE use scenarios for TRP TRS test + +The following use scenarios are considered for TRP TRS test: + +- Talk mode using head & hand phantom for narrow phones between 56 mm and 72 mm and for wide phones with a width >72 mm and <92 mm. +- Browsing mode using hand phantom for narrow and wide phones +- Using forearm phantom for wrist-worn devices +- Free Space is used for devices not used in above-mentioned scenarios, other phantoms are not precluded for wearable devices + +For smartphones, both browsing mode and talk mode shall be covered. + +For wrist-worn Redcap devices, forearm phantom is the first priority. FFS other Redcap form factor devices. + +For other device types, free space (FS) testing configuration is the first priority. + +### 4.2.2 UE mechanical mode description + +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. If multiple modes are supported, the manufacturer can declare different primary mechanical modes applicable for different user scenarios, e.g., different primary mechanical mode for Browsing mode usage and Talk mode usage for the same UE. + +## 4.3 Testing bands + + + +### 4.3.1 General + +The frequency ranges in which NR can operate are identified as described in Table 4.3.1-1. + +**Table 4.3.1-1: Definition of frequency ranges** + +| Frequency range designation | Corresponding frequency range | +|-----------------------------|-------------------------------| +| FR1 | 410 MHz – 7125 MHz | +| FR2 | 24250 MHz – 52600 MHz | + +The present technical report covers FR1 operating bands and FR1 non-standalone (NSA) operation mode with E-UTRA. + +### 4.3.2 Operating bands + +Operating bands for NR FR1 are defined in Table 5.2-1 and Carrier Aggregation (CA) are defined in Clause 5.5A in TS 38.101-1 [3]. The operating bands for EN-DC are defined in Clause 5.5B in TS 38.101-3 [4]. + +### 4.3.3 Test parameters for each band + +The detailed test parameters for each band are defined in Table 4.3.3-1 and Table 4.3.3-2. + +**Table 4.3.3-1: NR FR1 TRP measurement parameters** + +| NR Band | CBW [MHz] | SCS (kHz) | UL modulation | Range | UL Carrier centre [ARFCN] | UL Carrier Center (MHz) | DL Carrier centre [ARFCN] | DL Carrier Center (MHz) | UL RB Allocation (L CRB @ RB start ) | DL configuration | +|---------|-----------|-----------|--------------------|-------|---------------------------|-------------------------|---------------------------|-------------------------|------------------------------------------------------------|------------------| +| n1 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 385500 | 1927.5 | 423500 | 2117.5 | 36@18 | N/A | +| | | | | Mid | 390000 | 1950 | 428000 | 2140 | | | +| | | | | High | 394500 | 1972.5 | 432500 | 2162.5 | | | +| n2 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 371500 | 1857.5 | 387500 | 1937.5 | 36@18 | N/A | +| | | | | Mid | 376000 | 1880 | 392000 | 1960 | | | +| | | | | High | 380500 | 1902.5 | 396500 | 1982.5 | | | +| n3 | 20 | 15 | DFT-s-OFDM
QPSK | Low | 344000 | 1720 | 363000 | 1815 | 50@25 | N/A | +| | | | | Mid | 349500 | 1747.5 | 368500 | 1842.5 | | | +| | | | | High | 355000 | 1775 | 374000 | 1870 | | | +| n5 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 166300 | 831.5 | 175300 | 876.5 | 36@18 | N/A | +| | | | | Mid | 167300 | 836.5 | 176300 | 881.5 | | | +| | | | | High | 168300 | 841.5 | 177300 | 886.5 | | | +| n7 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 501500 | 2507.5 | 525500 | 2627.5 | 36@18 | N/A | +| | | | | Mid | 507000 | 2535 | 531000 | 2655 | | | +| | | | | High | 512500 | 2562.5 | 536500 | 2682.5 | | | +| n8 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 177500 | 887.5 | 186500 | 932.5 | 36@18 | N/A | +| | | | | Mid | 179500 | 897.5 | 188500 | 942.5 | | | +| | | | | High | 181500 | 907.5 | 190500 | 952.5 | | | +| n12 | 10 | 15 | DFT-s-OFDM
QPSK | Low | 140800 | 704 | 146800 | 734 | 25@12 | N/A | +| | | | | Mid | 141500 | 707.5 | 147500 | 737.5 | | | +| | | | | High | 142200 | 711 | 148200 | 741 | | | +| n14 | 10 | 15 | DFT-s-OFDM
QPSK | Low | 158600 | 793 | 152600 | 763 | 25@12 | N/A | +| | | | | Mid | | | | | | | +| | | | | High | | | | | | | +| n20 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 167900 | 839.5 | 159700 | 798.5 | 36@18 | N/A | +| | | | | Mid | 169400 | 847 | 161200 | 806 | | | +| | | | | High | 170900 | 854.5 | 162700 | 813.5 | | | +| n25 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 371500 | 1857.5 | 387500 | 1937.5 | 36@18 | N/A | +| | | | | Mid | 376500 | 1882.5 | 392500 | 1962.5 | | | +| | | | | High | 381500 | 1907.5 | 397500 | 1987.5 | | | +| n26 | 10 | 15 | DFT-s-OFDM
QPSK | Low | 163800 | 819 | 172800 | 864 | 25@12 | N/A | +| | | | | Mid | 166300 | 831.5 | 175300 | 876.5 | | | +| | | | | High | 168800 | 844 | 177800 | 889 | | | +| n28 | 20 | 15 | DFT-s-OFDM
QPSK | Low | 142600 | 713 | 153600 | 768 | 50@25 | N/A | +| | | | | Mid | 145600 | 728 | 156600 | 783 | | | +| | | | | High | 147600 | 738 | 158600 | 793 | | | +| n30 | 10 | 15 | DFT-s-OFDM
QPSK | Low | 462000 | 2310 | 471000 | 2355 | 25@12 | N/A | +| | | | | Mid | | | | | | | +| | | | | High | | | | | | | +| n34 | 10 | 15 | DFT-s-OFDM
QPSK | Low | 403000 | 2015 | 403000 | 2015 | 25@12 | N/A | +| | | | | Mid | 403500 | 2017.5 | 403500 | 2017.5 | | | +| | | | | High | 404000 | 2020 | 404000 | 2020 | | | +| n38 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 515500 | 2577.5 | 515500 | 2577.5 | 36@18 | N/A | +| | | | | Mid | 519000 | 2595 | 519000 | 2595 | | | +| | | | | High | 522500 | 2612.5 | 522500 | 2612.5 | | | +| n39 | 20 | 15 | DFT-s-OFDM
QPSK | Low | 378000 | 1890 | 378000 | 1890 | 50@25 | N/A | +| | | | | Mid | 380000 | 1900 | 380000 | 1900 | | | +| | | | | High | 382000 | 1910 | 382000 | 1910 | | | +| n40 | 30 | 15 | DFT-s-OFDM
QPSK | Low | 463000 | 2315 | 463000 | 2315 | TBD | N/A | +| | | | | Mid | 470000 | 2350 | 470000 | 2350 | | | +| | | | | High | 477000 | 2385 | 477000 | 2385 | | | +| n41 | 100 | 30 | DFT-s-OFDM
QPSK | Low | 509202 | 2546.01 | 509202 | 2546.01 | 135@67 | N/A | +| | | | | Mid | 518598 | 2592.99 | 518598 | 2592.99 | | | +| | | | | High | 528000 | 2640 | 528000 | 2640 | | | +| n48 | 20 | 15 | | Low | 637334 | 3560.01 | 637334 | 3560.01 | 50@25 | | + +| | | | | | | | | | | | +|-----|---------------|----|-----------------|------|--------|---------|--------|---------|--------|-----| +| | | | DFT-s-OFDM QPSK | Mid | 641666 | 3624.99 | 641666 | 3624.99 | | N/A | +| | | | | High | 646000 | 3690 | 646000 | 3690 | | | +| n50 | 20 | 15 | DFT-s-OFDM QPSK | Low | 288400 | 1442 | 288400 | 1442 | 50@25 | N/A | +| | | | | Mid | 294900 | 1474.5 | 294900 | 1474.5 | | | +| | | | | High | 301400 | 1507 | 301400 | 1507 | | | +| n51 | 5 | 15 | DFT-s-OFDM QPSK | Low | 285900 | 1429.5 | 285900 | 1429.5 | 12@6 | N/A | +| | | | | Mid | | | | | | | +| | | | | High | | | | | | | +| n53 | 10 | 15 | DFT-s-OFDM QPSK | Low | 497700 | 2488.5 | 497700 | 2488.5 | 25@12 | N/A | +| | | | | Mid | 497860 | 2489.3 | 497860 | 2489.3 | | | +| | | | | High | 498000 | 2490 | 498000 | 2490 | | | +| n65 | 15 | 15 | DFT-s-OFDM QPSK | Low | 423500 | 2117.5 | 423500 | 2117.5 | 36@18 | N/A | +| | | | | Mid | 431000 | 2155 | 431000 | 2155 | | | +| | | | | High | 438500 | 2192.5 | 438500 | 2192.5 | | | +| n66 | 20
(20+20) | 15 | DFT-s-OFDM QPSK | Low | 344000 | 1720 | 424000 | 2120 | 50@25 | N/A | +| | | | | Mid | 349000 | 1745 | 429000 | 2145 | | | +| | | | | High | 354000 | 1770 | 434000 | 2170 | | | +| n70 | 15
(15+15) | 15 | DFT-s-OFDM QPSK | Low | 340500 | 1702.5 | 400500 | 2002.5 | 36@18 | N/A | +| | | | | Mid | | | | | | | +| | | | | High | | | | | | | +| n71 | 10 | 15 | DFT-s-OFDM QPSK | Low | 133600 | 668 | 124400 | 622 | 25@12 | N/A | +| | | | | Mid | 136100 | 680.5 | 126900 | 634.5 | | | +| | | | | High | 138600 | 693 | 129400 | 647 | | | +| n74 | 15 | 15 | DFT-s-OFDM QPSK | Low | 286900 | 1434.5 | 296500 | 1482.5 | 36@18 | N/A | +| | | | | Mid | 289700 | 1448.5 | 299300 | 1496.5 | | | +| | | | | High | 292500 | 1462.5 | 302100 | 1510.5 | | | +| n77 | 100 | 30 | DFT-s-OFDM QPSK | Low | 623334 | 3350.01 | 623334 | 3350.01 | 135@67 | N/A | +| | | | | Mid | 650000 | 3750 | 650000 | 3750 | | | +| | | | | High | 676666 | 4149.99 | 676666 | 4149.99 | | | +| n78 | 100 | 30 | DFT-s-OFDM QPSK | Low | 623334 | 3350.01 | 623334 | 3350.01 | 135@67 | N/A | +| | | | | Mid | 636666 | 3549.99 | 636666 | 3549.99 | | | +| | | | | High | 650000 | 3750 | 650000 | 3750 | | | +| n79 | 100 | 30 | DFT-s-OFDM QPSK | Low | 696668 | 4450.02 | 696668 | 4450.02 | 135@67 | N/A | +| | | | | Mid | 713334 | 4700.01 | 713334 | 4700.01 | | | +| | | | | High | 730000 | 4950 | 730000 | 4950 | | | +| n80 | 20 | 15 | DFT-s-OFDM QPSK | Low | 344000 | 1720 | N/A | N/A | 50@25 | N/A | +| | | | | Mid | 349500 | 1747.5 | N/A | N/A | | | +| | | | | High | 355000 | 1775 | N/A | N/A | | | +| n81 | 15 | 15 | DFT-s-OFDM QPSK | Low | 177500 | 887.5 | N/A | N/A | 36@18 | N/A | +| | | | | Mid | 179500 | 897.5 | N/A | N/A | | | +| | | | | High | 181500 | 907.5 | N/A | N/A | | | +| n82 | 15 | 15 | DFT-s-OFDM QPSK | Low | 167900 | 839.5 | N/A | N/A | 36@18 | N/A | +| | | | | Mid | 169400 | 847 | N/A | N/A | | | +| | | | | High | 170900 | 854.5 | N/A | N/A | | | +| n83 | 15 | 15 | DFT-s-OFDM QPSK | Low | 142100 | 710.5 | N/A | N/A | 36@18 | N/A | +| | | | | Mid | 145100 | 725.5 | N/A | N/A | | | +| | | | | High | 148100 | 740.5 | N/A | N/A | | | +| n84 | 15 | 15 | DFT-s-OFDM QPSK | Low | 385500 | 1927.5 | N/A | N/A | 36@18 | N/A | +| | | | | Mid | 390000 | 1950 | N/A | N/A | | | +| | | | | High | 394500 | 1972.5 | N/A | N/A | | | +| n86 | 20 | 15 | DFT-s-OFDM QPSK | Low | 344000 | 1720 | N/A | N/A | 50@25 | N/A | +| | | | | Mid | 349000 | 1745 | N/A | N/A | | | +| | | | | High | 354000 | 1770 | N/A | N/A | | | +| N95 | 10 | 15 | DFT-s-OFDM QPSK | Low | 403000 | 2015 | N/A | N/A | 50@25 | N/A | +| | | | | Mid | 403500 | 2017.5 | N/A | N/A | | | +| | | | | High | 404000 | 2020 | N/A | N/A | | | + +**Table 4.3.3-2: NR FR1 TRS measurement parameters** + +| NR Band | CBW (MHz) | SCS (kHz) | DL modulation | UL modulation | Range | UL Carrier centre [ARFCN] | UL Carrier Center (MHz) | DL Carrier centre [ARFCN] | DL Carrier Center (MHz) | UL RB Allocation (L CRB @ RB start ) | DL Configuration (FULL) | +|---------|-----------|-----------|---------------|---------------|-------|---------------------------|-------------------------|---------------------------|-------------------------|------------------------------------------------------------|-------------------------| +|---------|-----------|-----------|---------------|---------------|-------|---------------------------|-------------------------|---------------------------|-------------------------|------------------------------------------------------------|-------------------------| + +| | | | | | | | | | | | RB, L CRB @
RB start ) | +|-----|-----|----|---------------------|------------------------|------|--------|---------|--------|---------|-------|-------------------------------------------------| +| n1 | 15 | 15 | CP-
OFDM
QPSK | DFT-s-
OFDM
QPSK | Low | 385500 | 1927.5 | 423500 | 2117.5 | 75@4 | 79@0 | +| | | | | | Mid | 390000 | 1950 | 428000 | 2140 | | | +| | | | | | High | 394500 | 1972.5 | 432500 | 2162.5 | | | +| n2 | 15 | 15 | CP-
OFDM
QPSK | DFT-s-
OFDM
QPSK | Low | 371500 | 1857.5 | 387500 | 1937.5 | 50@29 | 79@0 | +| | | | | | Mid | 376000 | 1880 | 392000 | 1960 | | | +| | | | | | High | 380500 | 1902.5 | 396500 | 1982.5 | | | +| n3 | 20 | 15 | CP-
OFDM
QPSK | DFT-s-
OFDM
QPSK | Low | 344000 | 1720 | 363000 | 1815 | 50@56 | 106@0 | +| | | | | | Mid | 349500 | 1747.5 | 368500 | 1842.5 | | | +| | | | | | High | 355000 | 1775 | 374000 | 1870 | | | +| n5 | 15 | 15 | CP-
OFDM
QPSK | DFT-s-
OFDM
QPSK | Low | 166300 | 831.5 | 175300 | 876.5 | 25@54 | 79@0 | +| | | | | | Mid | 167300 | 836.5 | 176300 | 881.5 | | | +| | | | | | High | 168300 | 841.5 | 177300 | 886.5 | | | +| n7 | 15 | 15 | CP-
OFDM
QPSK | DFT-s-
OFDM
QPSK | Low | 501500 | 2507.5 | 525500 | 2627.5 | 75@4 | 79@0 | +| | | | | | Mid | 507000 | 2535 | 531000 | 2655 | | | +| | | | | | High | 512500 | 2562.5 | 536500 | 2682.5 | | | +| n8 | 15 | 15 | CP-
OFDM
QPSK | DFT-s-
OFDM
QPSK | Low | 177500 | 887.5 | 186500 | 932.5 | 25@54 | 79@0 | +| | | | | | Mid | 179500 | 897.5 | 188500 | 942.5 | | | +| | | | | | High | 181500 | 907.5 | 190500 | 952.5 | | | +| n12 | 10 | 15 | CP-
OFDM
QPSK | DFT-s-
OFDM
QPSK | Low | 140800 | 704 | 146800 | 734 | 20@32 | 52@0 | +| | | | | | Mid | 141500 | 707.5 | 147500 | 737.5 | | | +| | | | | | High | 142200 | 711 | 148200 | 741 | | | +| n14 | 10 | 15 | CP-
OFDM
QPSK | DFT-s-
OFDM
QPSK | Low | 158600 | 793 | 152600 | 763 | 20@32 | 52@0 | +| | | | | | Mid | | | | | | | +| | | | | | High | | | | | | | +| n20 | 15 | 15 | CP-
OFDM
QPSK | DFT-s-
OFDM
QPSK | Low | 167900 | 839.5 | 159700 | 798.5 | 20@11 | 79@0 | +| | | | | | Mid | 169400 | 847 | 161200 | 806 | | | +| | | | | | High | 170900 | 854.5 | 162700 | 813.5 | | | +| n25 | 15 | 15 | CP-
OFDM
QPSK | DFT-s-
OFDM
QPSK | Low | 371500 | 1857.5 | 387500 | 1937.5 | 50@29 | 79@0 | +| | | | | | Mid | 376500 | 1882.5 | 392500 | 1962.5 | | | +| | | | | | High | 381500 | 1907.5 | 397500 | 1987.5 | | | +| n26 | 10 | 15 | CP-
OFDM
QPSK | DFT-s-
OFDM
QPSK | Low | 163800 | 819 | 172800 | 864 | 25@27 | 52@0 | +| | | | | | Mid | 166300 | 831.5 | 175300 | 876.5 | | | +| | | | | | High | 168800 | 844 | 177800 | 889 | | | +| n28 | 20 | 15 | CP-
OFDM
QPSK | DFT-s-
OFDM
QPSK | Low | 142600 | 713 | 153600 | 768 | 25@81 | 106@0 | +| | | | | | Mid | 145600 | 728 | 156600 | 783 | | | +| | | | | | High | 147600 | 738 | 158600 | 793 | | | +| n30 | 10 | 15 | CP-
OFDM
QPSK | DFT-s-
OFDM
QPSK | Low | 462000 | 2310 | 471000 | 2355 | 20@32 | 52@0 | +| | | | | | Mid | | | | | | | +| | | | | | High | | | | | | | +| n34 | 10 | 15 | CP-
OFDM
QPSK | DFT-s-
OFDM
QPSK | Low | 403000 | 2015 | 403000 | 2015 | 50@0 | 52@0 | +| | | | | | Mid | 403500 | 2017.5 | 403500 | 2017.5 | | | +| | | | | | High | 404000 | 2020 | 404000 | 2020 | | | +| n38 | 15 | 15 | CP-
OFDM
QPSK | DFT-s-
OFDM
QPSK | Low | 515500 | 2577.5 | 515500 | 2577.5 | 75@0 | 79@0 | +| | | | | | Mid | 519000 | 2595 | 519000 | 2595 | | | +| | | | | | High | 522500 | 2612.5 | 522500 | 2612.5 | | | +| n39 | 20 | 15 | CP-
OFDM
QPSK | DFT-s-
OFDM
QPSK | Low | 378000 | 1890 | 378000 | 1890 | 100@0 | 106@0 | +| | | | | | Mid | 380000 | 1900 | 380000 | 1900 | | | +| | | | | | High | 382000 | 1910 | 382000 | 1910 | | | +| n40 | 30 | 15 | CP-
OFDM
QPSK | DFT-s-
OFDM
QPSK | Low | 463000 | 2315 | 463000 | 2315 | 160@0 | 160@0 | +| | | | | | Mid | 470000 | 2350 | 470000 | 2350 | | | +| | | | | | High | 477000 | 2385 | 477000 | 2385 | | | +| n41 | 100 | 30 | | | Low | 509202 | 2546.01 | 509202 | 2546.01 | 270@0 | | + +| | | | | | | | | | | | | +|------------|----------------|----|--------------|-----------------|------|--------|---------|--------|---------|-------|-------| +| | | | CP-OFDM QPSK | DFT-s-OFDM QPSK | Mid | 518598 | 2592.99 | 518598 | 2592.99 | | 273@0 | +| | | | | | High | 528000 | 2640 | 528000 | 2640 | | | +| n48 | 20 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 637334 | 3560.01 | 637334 | 3560.01 | 100@0 | 106@0 | +| | | | | | Mid | 641666 | 3624.99 | 641666 | 3624.99 | | | +| | | | | | High | 646000 | 3690 | 646000 | 3690 | | | +| n50 | 20 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 288400 | 1442 | 288400 | 1442 | 100@0 | 106@0 | +| | | | | | Mid | 294900 | 1474.5 | 294900 | 1474.5 | | | +| | | | | | High | 301400 | 1507 | 301400 | 1507 | | | +| n51 | 5 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 285900 | 1429.5 | 285900 | 1429.5 | 25@0 | 25@0 | +| | | | | | Mid | | | | | | | +| | | | | | High | | | | | | | +| n53 | 10 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 497700 | 2488.5 | 497700 | 2488.5 | 50@0 | 52@0 | +| | | | | | Mid | 497860 | 2489.3 | 497860 | 2489.3 | | | +| | | | | | High | 498000 | 2490 | 498000 | 2490 | | | +| n65 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 423500 | 2117.5 | 423500 | 2117.5 | 75@4 | 79@0 | +| | | | | | Mid | 431000 | 2155 | 431000 | 2155 | | | +| | | | | | High | 438500 | 2192.5 | 438500 | 2192.5 | | | +| n66 | 20
(20+20 ) | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 344000 | 1720 | 424000 | 2120 | 100@6 | 106@0 | +| | | | | | Mid | 349000 | 1745 | 429000 | 2145 | | | +| | | | | | High | 354000 | 1770 | 434000 | 2170 | | | +| n70 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 340500 | 1702.5 | 400500 | 2002.5 | 75@4 | 79@0 | +| | | | | | Mid | | | | | | | +| | | | | | High | | | | | | | +| n71 | 10 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 133600 | 668 | 124400 | 622 | 25@0 | 52@0 | +| | | | | | Mid | 136100 | 680.5 | 126900 | 634.5 | | | +| | | | | | High | 138600 | 693 | 129400 | 647 | | | +| n74 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 286900 | 1434.5 | 296500 | 1482.5 | 25@54 | 79@0 | +| | | | | | Mid | 289700 | 1448.5 | 299300 | 1496.5 | | | +| | | | | | High | 292500 | 1462.5 | 302100 | 1510.5 | | | +| n75
SDL | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | N/A | N/A | 287900 | 1439.5 | NA | 79@0 | +| | | | | | Mid | N/A | N/A | 294900 | 1474.5 | | | +| | | | | | High | N/A | N/A | 301900 | 1509.5 | | | +| n76
SDL | 5 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | N/A | N/A | 285900 | 1429.5 | NA | 25@0 | +| | | | | | Mid | | | | | | | +| | | | | | High | | | | | | | +| n77 | 100 | 30 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 623334 | 3350.01 | 623334 | 3350.01 | 270@0 | 273@0 | +| | | | | | Mid | 650000 | 3750 | 650000 | 3750 | | | +| | | | | | High | 676666 | 4149.99 | 676666 | 4149.99 | | | +| n78 | 100 | 30 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 623334 | 3350.01 | 623334 | 3350.01 | 270@0 | 273@0 | +| | | | | | Mid | 636666 | 3549.99 | 636666 | 3549.99 | | | +| | | | | | High | 650000 | 3750 | 650000 | 3750 | | | +| n79 | 100 | 30 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 696668 | 4450.02 | 696668 | 4450.02 | 270@0 | 273@0 | +| | | | | | Mid | 713334 | 4700.01 | 713334 | 4700.01 | | | +| | | | | | High | 730000 | 4950 | 730000 | 4950 | | | + +The detailed testing parameters for each band for RedCap UE is defined in Table 4.3.3-3 and Table 4.3.3-4. + +**Table 4.3.3-3: NR FR1 TRP measurement parameters for RedCap UE** + +| NR Band | CBW [MHz] | SCS (kHz) | UL modulation | Range | UL Carrier centre [ARFCN] | UL Carrier Center (MHz) | DL Carrier centre [ARFCN] | DL Carrier Center (MHz) | UL RB Allocation (L CRB @ RB start ) | DL configuration | +|---------|-----------|-----------|---------------|-------|---------------------------|-------------------------|---------------------------|-------------------------|------------------------------------------------------------|------------------| +|---------|-----------|-----------|---------------|-------|---------------------------|-------------------------|---------------------------|-------------------------|------------------------------------------------------------|------------------| + +| | | | | | | | | | | | +|-----|----|----|--------------------|------|--------|----------|--------|----------|-------|-----| +| n1 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 385500 | 1927.5 | 423500 | 2117.5 | 36@18 | N/A | +| | | | | Mid | 390000 | 1950 | 428000 | 2140 | | | +| | | | | High | 394500 | 1972.5 | 432500 | 2162.5 | | | +| n2 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 371500 | 1857.5 | 387500 | 1937.5 | 36@18 | N/A | +| | | | | Mid | 376000 | 1880 | 392000 | 1960 | | | +| | | | | High | 380500 | 1902.5 | 396500 | 1982.5 | | | +| n3 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 343500 | 1717.5 | 362500 | 1812.5 | 36@18 | N/A | +| | | | | Mid | 349500 | 1747.5 | 368500 | 1842.5 | | | +| | | | | High | 355500 | 1777.5 | 374500 | 1872.5 | | | +| n5 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 166300 | 831.5 | 175300 | 876.5 | 36@18 | N/A | +| | | | | Mid | 167300 | 836.5 | 176300 | 881.5 | | | +| | | | | High | 168300 | 841.5 | 177300 | 886.5 | | | +| n7 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 501500 | 2507.5 | 525500 | 2627.5 | 36@18 | N/A | +| | | | | Mid | 507000 | 2535 | 531000 | 2655 | | | +| | | | | High | 512500 | 2562.5 | 536500 | 2682.5 | | | +| n8 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 177500 | 887.5 | 186500 | 932.5 | 36@18 | N/A | +| | | | | Mid | 179500 | 897.5 | 188500 | 942.5 | | | +| | | | | High | 181500 | 907.5 | 190500 | 952.5 | | | +| n12 | 10 | 15 | DFT-s-OFDM
QPSK | Low | 140800 | 704 | 146800 | 734 | 25@12 | N/A | +| | | | | Mid | 141500 | 707.5 | 147500 | 737.5 | | | +| | | | | High | 142200 | 711 | 148200 | 741 | | | +| n14 | 10 | 15 | DFT-s-OFDM
QPSK | Low | 158600 | 793 | 152600 | 763 | 25@12 | N/A | +| | | | | Mid | | | | | | | +| | | | | High | | | | | | | +| n20 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 167900 | 839.5 | 159700 | 798.5 | 36@18 | N/A | +| | | | | Mid | 169400 | 847 | 161200 | 806 | | | +| | | | | High | 170900 | 854.5 | 162700 | 813.5 | | | +| n25 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 371500 | 1857.5 | 387500 | 1937.5 | 36@18 | N/A | +| | | | | Mid | 376500 | 1882.5 | 392500 | 1962.5 | | | +| | | | | High | 381500 | 1907.5 | 397500 | 1987.5 | | | +| n26 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 164300 | 821.5 | 173300 | 866.5 | 36@18 | N/A | +| | | | | Mid | 166300 | 831.5 | 175300 | 876.5 | | | +| | | | | High | 168300 | 841.5 | 177300 | 886.5 | | | +| n28 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 142100 | 710.5 | 153100 | 765.5 | 36@18 | N/A | +| | | | | Mid | 145100 | 725.5 | 156100 | 780.5 | | | +| | | | | High | 148100 | 740.5 | 159100 | 795.5 | | | +| n30 | 10 | 15 | DFT-s-OFDM
QPSK | Low | 462000 | 2310 | 471000 | 2355 | 25@12 | N/A | +| | | | | Mid | | | | | | | +| | | | | High | | | | | | | +| n34 | 10 | 15 | DFT-s-OFDM
QPSK | Low | 403000 | 2015 | 403000 | 2015 | 25@12 | N/A | +| | | | | Mid | 403500 | 2017.5 | 403500 | 2017.5 | | | +| | | | | High | 404000 | 2020 | 404000 | 2020 | | | +| n38 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 515500 | 2577.5 | 515500 | 2577.5 | 36@18 | N/A | +| | | | | Mid | 519000 | 2595 | 519000 | 2595 | | | +| | | | | High | 522500 | 2612.5 | 522500 | 2612.5 | | | +| n39 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 377500 | 1887.5 | 377500 | 1887.5 | 36@18 | N/A | +| | | | | Mid | 380000 | 1900 | 380000 | 1900 | | | +| | | | | High | 382500 | 1912.5 | 382500 | 1912.5 | | | +| n40 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 461500 | 2307.5 | 461500 | 2307.5 | 36@18 | N/A | +| | | | | Mid | 470000 | 2350 | 470000 | 2350 | | | +| | | | | High | 478500 | 2392.5 | 478500 | 2392.5 | | | +| n41 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 500700 | 2503.5 | 500700 | 2503.5 | 36@18 | N/A | +| | | | | Mid | 518601 | 2593.005 | 518601 | 2593.005 | | | +| | | | | High | 536499 | 2682.495 | 536499 | 2682.495 | | | +| n48 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 637168 | 3557.52 | 637168 | 3557.52 | 36@18 | N/A | +| | | | | Mid | 641666 | 3624.99 | 641666 | 3624.99 | | | +| | | | | High | 646166 | 3692.49 | 646166 | 3692.49 | | | +| n50 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 287900 | 1439.5 | 287900 | 1439.5 | 36@18 | N/A | +| | | | | Mid | 294900 | 1474.5 | 294900 | 1474.5 | | | +| | | | | High | 301900 | 1509.5 | 301900 | 1509.5 | | | +| n51 | 5 | 15 | DFT-s-OFDM
QPSK | Low | 285900 | 1429.5 | 285900 | 1429.5 | 12@6 | N/A | +| | | | | Mid | | | | | | | +| | | | | High | | | | | | | +| n53 | 10 | 15 | DFT-s-OFDM
QPSK | Low | 497700 | 2488.5 | 497700 | 2488.5 | 25@12 | N/A | +| | | | | Mid | 497860 | 2489.3 | 497860 | 2489.3 | | | +| | | | | High | 498000 | 2490 | 498000 | 2490 | | | +| n65 | 15 | 15 | DFT-s-OFDM
QPSK | Low | 423500 | 2117.5 | 423500 | 2117.5 | 36@18 | N/A | +| | | | | Mid | 431000 | 2155 | 431000 | 2155 | | | +| | | | | High | 438500 | 2192.5 | 438500 | 2192.5 | | | +| n71 | 10 | 15 | DFT-s-OFDM
QPSK | Low | 133600 | 668 | 124400 | 622 | 25@12 | N/A | +| | | | | Mid | 136100 | 680.5 | 126900 | 634.5 | | | +| | | | | High | 138600 | 693 | 129400 | 647 | | | +| n74 | 15 | | DFT-s-OFDM | Low | 286900 | 1434.5 | 296500 | 1482.5 | 36@18 | | + +| | | | | | | | | | | | +|-----|----|----|-----------------|------|--------|----------|--------|----------|-------|-----| +| n77 | 15 | 15 | DFT-s-OFDM QPSK | Mid | 289700 | 1448.5 | 299300 | 1496.5 | 36@18 | N/A | +| | | | | High | 292500 | 1462.5 | 302100 | 1510.5 | | | +| | | | | Low | 620500 | 3307.5 | 620500 | 3307.5 | | | +| | | | | Mid | 650000 | 3750 | 650000 | 3750 | | | +| n78 | 15 | 15 | DFT-s-OFDM QPSK | High | 679500 | 4192.5 | 679500 | 4192.5 | 36@18 | N/A | +| | | | | Low | 620500 | 3307.5 | 620500 | 3307.5 | | | +| | | | | Mid | 636666 | 3549.99 | 636666 | 3549.99 | | | +| | | | | High | 652832 | 3792.48 | 652832 | 3792.48 | | | +| n79 | 20 | 15 | DFT-s-OFDM QPSK | Low | 694000 | 4410 | 694000 | 4410 | 50@25 | N/A | +| | | | | Mid | 713333 | 4699.995 | 713333 | 4699.995 | | | +| | | | | High | 732667 | 4990.005 | 732667 | 4990.005 | | | + +Table 4.3.3-4: NR FR1 TRS measurement parameters for RedCap UE + +| NR Band | CBW (MHz) | SCS (kHz) | DL modulation | UL modulation | Range | UL Carrier centre [ARFCN] | UL Carrier Center (MHz) | DL Carrier centre [ARFCN] | DL Carrier Center (MHz) | UL RB Allocation (L CRB @ RB start ) | DL Configuration (FULL RB, L CRB @ RB start ) | +|---------|-----------|-----------|---------------|-----------------|-------|---------------------------|-------------------------|---------------------------|-------------------------|------------------------------------------------------------|---------------------------------------------------------------------| +| n1 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 385500 | 1927.5 | 423500 | 2117.5 | 75@4 | 79@0 | +| | | | | | Mid | 390000 | 1950 | 428000 | 2140 | | | +| | | | | | High | 394500 | 1972.5 | 432500 | 2162.5 | | | +| n2 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 371500 | 1857.5 | 387500 | 1937.5 | 50@29 | 79@0 | +| | | | | | Mid | 376000 | 1880 | 392000 | 1960 | | | +| | | | | | High | 380500 | 1902.5 | 396500 | 1982.5 | | | +| n3 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 343500 | 1717.5 | 362500 | 1812.5 | 50@29 | 79@0 | +| | | | | | Mid | 349500 | 1747.5 | 368500 | 1842.5 | | | +| | | | | | High | 355500 | 1777.5 | 374500 | 1872.5 | | | +| n5 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 166300 | 831.5 | 175300 | 876.5 | 25@54 | 79@0 | +| | | | | | Mid | 167300 | 836.5 | 176300 | 881.5 | | | +| | | | | | High | 168300 | 841.5 | 177300 | 886.5 | | | +| n7 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 501500 | 2507.5 | 525500 | 2627.5 | 75@4 | 79@0 | +| | | | | | Mid | 507000 | 2535 | 531000 | 2655 | | | +| | | | | | High | 512500 | 2562.5 | 536500 | 2682.5 | | | +| n8 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 177500 | 887.5 | 186500 | 932.5 | 25@54 | 79@0 | +| | | | | | Mid | 179500 | 897.5 | 188500 | 942.5 | | | +| | | | | | High | 181500 | 907.5 | 190500 | 952.5 | | | +| n12 | 10 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 140800 | 704 | 146800 | 734 | 20@32 | 52@0 | +| | | | | | Mid | 141500 | 707.5 | 147500 | 737.5 | | | +| | | | | | High | 142200 | 711 | 148200 | 741 | | | +| n14 | 10 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 158600 | 793 | 152600 | 763 | 20@32 | 52@0 | +| | | | | | Mid | | | | | | | +| | | | | | High | | | | | | | +| n20 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 167900 | 839.5 | 159700 | 798.5 | 20@11 | 79@0 | +| | | | | | Mid | 169400 | 847 | 161200 | 806 | | | +| | | | | | High | 170900 | 854.5 | 162700 | 813.5 | | | +| n25 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 371500 | 1857.5 | 387500 | 1937.5 | 50@29 | 79@0 | +| | | | | | Mid | 376500 | 1882.5 | 392500 | 1962.5 | | | +| | | | | | High | 381500 | 1907.5 | 397500 | 1987.5 | | | +| n26 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 164300 | 821.5 | 173300 | 866.5 | 25@54 | 79@0 | +| | | | | | Mid | 166300 | 831.5 | 175300 | 876.5 | | | +| | | | | | High | 168300 | 841.5 | 177300 | 886.5 | | | +| n28 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 142100 | 710.5 | 153100 | 765.5 | 25@54 | 79@0 | +| | | | | | Mid | 145100 | 725.5 | 156100 | 780.5 | | | +| | | | | | High | 148100 | 740.5 | 159100 | 795.5 | | | +| n30 | 10 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 462000 | 2310 | 471000 | 2355 | 20@32 | 52@0 | +| | | | | | Mid | | | | | | | +| | | | | | High | | | | | | | +| n34 | 10 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 403000 | 2015 | 403000 | 2015 | 50@0 | 52@0 | +| | | | | | Mid | 403500 | 2017.5 | 403500 | 2017.5 | | | +| | | | | | High | 404000 | 2020 | 404000 | 2020 | | | +| n38 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 515500 | 2577.5 | 515500 | 2577.5 | 75@0 | 79@0 | +| | | | | | Mid | 519000 | 2595 | 519000 | 2595 | | | +| | | | | | High | 522500 | 2612.5 | 522500 | 2612.5 | | | +| n39 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 377500 | 1887.5 | 377500 | 1887.5 | 75@0 | 79@0 | +| | | | | | Mid | 380000 | 1900 | 380000 | 1900 | | | +| | | | | | High | 382500 | 1912.5 | 382500 | 1912.5 | | | +| n40 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 461500 | 2307.5 | 461500 | 2307.5 | 75@0 | 79@0 | +| | | | | | Mid | 470000 | 2350 | 470000 | 2350 | | | +| | | | | | High | 478500 | 2392.5 | 478500 | 2392.5 | | | + +| | | | | | | | | | | | | +|-----|----|----|--------------|-----------------|------|--------|----------|--------|----------|-------|-------| +| n41 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 500700 | 2503.5 | 500700 | 2503.5 | 75@0 | 79@0 | +| | | | | | Mid | 518601 | 2593.005 | 518601 | 2593.005 | | | +| | | | | | High | 536499 | 2682.495 | 536499 | 2682.495 | | | +| n48 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 637168 | 3557.52 | 637168 | 3557.52 | 75@0 | 79@0 | +| | | | | | Mid | 641666 | 3624.99 | 641666 | 3624.99 | | | +| | | | | | High | 646166 | 3692.49 | 646166 | 3692.49 | | | +| n50 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 287900 | 1439.5 | 287900 | 1439.5 | 75@0 | 79@0 | +| | | | | | Mid | 294900 | 1474.5 | 294900 | 1474.5 | | | +| | | | | | High | 301900 | 1509.5 | 301900 | 1509.5 | | | +| n51 | 5 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 285900 | 1429.5 | 285900 | 1429.5 | 25@0 | 25@0 | +| | | | | | Mid | | | | | | | +| | | | | | High | | | | | | | +| n53 | 10 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 497700 | 2488.5 | 497700 | 2488.5 | 50@0 | 52@0 | +| | | | | | Mid | 497860 | 2489.3 | 497860 | 2489.3 | | | +| | | | | | High | 498000 | 2490 | 498000 | 2490 | | | +| n65 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 423500 | 2117.5 | 423500 | 2117.5 | 75@4 | 79@0 | +| | | | | | Mid | 431000 | 2155 | 431000 | 2155 | | | +| | | | | | High | 438500 | 2192.5 | 438500 | 2192.5 | | | +| n70 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 340500 | 1702.5 | 400500 | 2002.5 | 75@4 | 79@0 | +| | | | | | Mid | | | | | | | +| | | | | | High | | | | | | | +| n71 | 10 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 133600 | 668 | 124400 | 622 | 25@0 | 52@0 | +| | | | | | Mid | 136100 | 680.5 | 126900 | 634.5 | | | +| | | | | | High | 138600 | 693 | 129400 | 647 | | | +| n74 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 286900 | 1434.5 | 296500 | 1482.5 | 25@54 | 79@0 | +| | | | | | Mid | 289700 | 1448.5 | 299300 | 1496.5 | | | +| | | | | | High | 292500 | 1462.5 | 302100 | 1510.5 | | | +| n77 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 620500 | 3307.5 | 620500 | 3307.5 | 75@0 | 79@0 | +| | | | | | Mid | 650000 | 3750 | 650000 | 3750 | | | +| | | | | | High | 679500 | 4192.5 | 679500 | 4192.5 | | | +| n78 | 15 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 620500 | 3307.5 | 620500 | 3307.5 | 75@0 | 79@0 | +| | | | | | Mid | 636666 | 3549.99 | 636666 | 3549.99 | | | +| | | | | | High | 652832 | 3792.48 | 652832 | 3792.48 | | | +| n79 | 20 | 15 | CP-OFDM QPSK | DFT-s-OFDM QPSK | Low | 694000 | 4410 | 694000 | 4410 | 100@0 | 106@0 | +| | | | | | Mid | 713333 | 4699.995 | 713333 | 4699.995 | | | +| | | | | | High | 732667 | 4990.005 | 732667 | 4990.005 | | | + +### 4.3.4 EN-DC band combinations + + + +Principle of EN-DC band combinations selection for FR1 TRP TRS OTA testing: + +- 1) Focus on the performance of the NR carrier and do not consider multiple permutations between different LTE bands and NR band under test, i.e., for each NR band, only select one EN-DC band combination. +- 2) For UE supporting multiple EN-DC band combinations for the same NR band, consider only those EN-DC configurations which have no MSD impact on either LTE or NR, i.e., the selected EN-DC combination should be no MSD issue identified in TS 38.101-3 Section 7.3B.2.3 (Inter-band EN-DC within FR1). + +**Table 4.3.4-1: Measurement parameters for example inter-band EN-DC band combinations (two bands)** + +| EN-DC configuration | E-UTRA configurations | NR configurations | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--------------------------| +| DC_3A_n28A | Note1 | Note2 | +| DC_2A_n41A | Note1 | Note2 | +| DC_1A_n78A | Note1 | Note2 | +| DC_1A_n79A | Note1 | Note2 | +| Note 1: As per TS 37.544 [14], Clause 5.3 and 5.4
(Measurement frequencies for E-UTRA FDD and TDD).
Note 2: As per Table 4.3-1 and Table 4.3-2 in this specification.
The measurement parameters for NR Low Mid High ranges correspond to E-UTRA Low Mid High ranges respectively. | | | + +With the above basic principle and EN-DC example band combination, the selection logic for testing is defined by the decision tree below. + +![Flowchart for selecting EN-DC band combination for TRP/TRS testing. It starts with step 1: 'For each NR band that has TRP/TRS requirements specified in TS38.161:'. It then checks if the UE supports the band. If no, it continues to the next band. If yes, it checks if the requirement has been fulfilled by testing the UE in SA mode. If yes, the requirement need not be retested in EN-DC mode; continue to the next band. If no, it checks if the UE supports the example EN-DC band combination in TS38.161, Table 5.2.2-1, which corresponds to the band selected in step #1. If yes, it configures the UE according to the example band combination and perform the test in EN-DC mode. If no, it proceeds to step 3: 'Select an EN-DC band combination candidate as follows:'. Step 3 involves selecting the NR band under test from step #1, and then selecting the next-closest LTE band. It then checks if the UE supports more LTE bands in combination with the selected NR band. If no, it configures the UE according to any band combination which includes the selected NR band and which is self-declared by the OEM. If yes, it checks if the resulting EN-DC configuration fulfill the criteria defined in TS38.161, Clause 5.2.2. If yes, it configures the UE according to the chosen band combination and perform the test in EN-DC mode. If no, it loops back to step 3.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` +graph TD; A[1. For each NR band that has TRP/TRS requirements specified in TS38.161:] --> B{Does the UE support the band?}; B -- No --> C[Continue to the next band]; B -- Yes --> D{Has the requirement been fulfilled by testing the UE in SA mode?}; D -- Yes --> E[Requirement need not be retested in EN-DC mode; continue to the next band]; D -- No --> F{Does the UE support the example EN-DC band combination in TS38.161, Table 5.2.2-1, which corresponds to the band selected in step #1?}; F -- Yes --> G[2. Configure the UE according to the example band combination and perform the test in EN-DC mode]; F -- No --> H[3. Select an EN-DC band combination candidate as follows:]; H --> I[For the NR carrier: select the NR band under test from step #1]; I --> J[For the LTE carrier: select a band with the uplink frequency closest to the LTE band used in the example band combination corresponding to the selected NR carrier in TS38.161, Table 5.2.2-1, and which is supported by the UE in EN-DC configuration with the chosen NR band]; J --> K{Does the resulting EN-DC configuration fulfill the criteria defined in TS38.161, Clause 5.2.2?}; K -- Yes --> L[5. Configure the UE according to the chosen band combination and perform the test in EN-DC mode]; K -- No --> M{Does the UE support more LTE bands in combination with the selected NR band?}; M -- Yes --> N[Select the next-closest LTE band]; N --> J; M -- No --> O[4. Configure the UE according to any band combination which includes the selected NR band and which is self-declared by the OEM]; O --> H; +``` + +Flowchart for selecting EN-DC band combination for TRP/TRS testing. It starts with step 1: 'For each NR band that has TRP/TRS requirements specified in TS38.161:'. It then checks if the UE supports the band. If no, it continues to the next band. If yes, it checks if the requirement has been fulfilled by testing the UE in SA mode. If yes, the requirement need not be retested in EN-DC mode; continue to the next band. If no, it checks if the UE supports the example EN-DC band combination in TS38.161, Table 5.2.2-1, which corresponds to the band selected in step #1. If yes, it configures the UE according to the example band combination and perform the test in EN-DC mode. If no, it proceeds to step 3: 'Select an EN-DC band combination candidate as follows:'. Step 3 involves selecting the NR band under test from step #1, and then selecting the next-closest LTE band. It then checks if the UE supports more LTE bands in combination with the selected NR band. If no, it configures the UE according to any band combination which includes the selected NR band and which is self-declared by the OEM. If yes, it checks if the resulting EN-DC configuration fulfill the criteria defined in TS38.161, Clause 5.2.2. If yes, it configures the UE according to the chosen band combination and perform the test in EN-DC mode. If no, it loops back to step 3. + +Figure 4.3.4-1: Decision tree to select the EN-DC band combination for TRP/TRS testing + +### 4.3.5 CA band combinations + + + +# 5 Performance metrics + +## 5.1 Definition of the Total Radiated Power (TRP) + +### 5.1.1 Definition of the Total Radiated Power (TRP) for AC + +Transmitter power measurements shall be performed using the Total Radiated Power (TRP) as the measurement metric. This clause defines the definition of TRP value of NR FR1 DUT for Anechoic Chamber (AC) method. + +The TRP with Anechoic Chamber method is defined as: + +$$TRP = \frac{1}{4\pi} \int_{\theta=0}^{\pi} \int_{\phi=0}^{2\pi} [EIRP_{\theta}(\theta, \phi) + EIRP_{\phi}(\theta, \phi)] \sin(\theta) d\phi d\theta \quad (5.1)$$ + +Where the effective isotropic radiated power (EIRP) is defined as + +$$EIRP(\theta, \phi) = P_T G_T(\theta, \phi) \quad (5.2)$$ + +Where $P_T G_T$ is the product of the power delivered to the antenna and the antenna's power gain. + +Where $EIRP_{\theta}$ and $EIRP_{\phi}$ are the EIRP in the corresponding $\theta$ and $\phi$ polarizations. + +The summation form based on the $\sin\theta \cdot \Delta\theta$ weights of TRP with Anechoic Chamber method is defined as: + +$$TRP \approx \frac{\pi}{2NM} \sum_{n=0}^{N-1} \sum_{m=0}^{M-1} [EIRP_{\theta}(\theta_n, \phi_m) + EIRP_{\phi}(\theta_n, \phi_m)] \sin \theta_n \quad (5.3)$$ + +Where N and M are the number of sampling intervals for $\theta$ and $\phi$ . $\theta_n$ and $\phi_m$ are the measurement angles. + +The summation form based on the Clenshaw-Curtis quadrature integral approximation of TRP with Anechoic Chamber method is defined as: + +$$TRP \approx \frac{1}{2M} \sum_{n=0}^N \sum_{m=0}^{M-1} [EIRP_{\theta}(\theta_n, \phi_m) + EIRP_{\phi}(\theta_n, \phi_m)] W(\theta_n) \quad (5.4)$$ + +Where the value of $W(\theta_n)$ can be calculated as follows: + +$$W(\theta_n) = \frac{c_i}{N} \left[ 1 - \sum_{j=1}^{\text{int}(\frac{N}{2})} \frac{b_j}{4j^2-1} \cos(2j\theta_n) \right] \quad (5.5)$$ + +with + +$$b_j = \begin{cases} 1, & 2j = N \\ 2, & \text{otherwise} \end{cases}$$ + +and + +$$c_i = \begin{cases} 1, & i = 0 \text{ or } N \\ 2, & \text{otherwise} \end{cases}$$ + +The applicability of TRP quadratures, frequency ranges, and measurement grids is tabulated in Table 5.1.1-1. + +**Table 5.1.1-1: Applicability for TRP measurement grids** + +| Frequency Range | Quadrature | $\Delta\theta=\Delta\phi [^\circ]$ | N | M | Min. Number of Grid Points | +|-----------------|-----------------|------------------------------------|----------|----------|----------------------------| +| < 3GHz | sin( $\theta$ ) | 15 | 12 | 24 | 266 | +| | | 30 | 6 | 12 | 62 | +| | Clenshaw-Curtis | 15 | 12 | 24 | 266 | +| | | 30 | 6 | 12 | 62 | +| > 3GHz | sin( $\theta$ ) | 15 | 12 | 24 | 266 | +| | | 30 | 6 | 12 | 62 | +| | Clenshaw-Curtis | 15 | 12 | 24 | 266 | +| | | 30 | 6 | 12 | 62 | + +### 5.1.2 Definition of the Total Radiated Power (TRP) for RC method + +TRP in the reverberation chamber is a measurement of transmitter performance in an isotropic Rayleigh fading environment that is based on sampling the radiated power of the UE/MS for a discrete number of field combinations. The average value of these statistically distributed samples is proportional to the TRP and by calibrating the average power transfer function, an absolute value of the TRP can be obtained. The TRP with Reverberation Chamber method is defined as: + +$$TRP = \frac{P_{avg}}{C(1-R)P_{ref}}$$ + +Where $P_{ref}$ is the reference power transfer function for the fixed measurement antenna, $R$ is the reflection coefficient for the fixed measurement antenna and $C$ is the path loss in the cables connecting the measurement receiver to fixed measurement antenna. These parameters are calculated from the calibration measurement and are further discussed in calibration section. $P_{avg}$ is the average power measured by the fixed measurement antenna and can be calculated using the following expression: + +$$P_{avg} = \frac{\sum_{m=1}^M |S_{21,m}|^2}{M}$$ + +Where $S_{21,m}$ is sample number $m$ of the complex transfer function measured with the fixed measurement antenna and $M$ is the total number of samples measured. + +## 5.2 Definition of Total Radiated Sensitivity (TRS) + +### 5.2.1 Definition of the Total Radiated Sensitivity (TRS) for AC + +Receiver sensitivity measurements shall be performed using data throughput as the measurement metric. The DUT's receiver sensitivity corresponds to the minimum downlink signal power required to provide a data throughput rate greater than or equal to 95% of the maximum throughput of the reference measurement channel (RMC). + +This definition will be used to calculate the Total Radiated Sensitivity (TRS) value of NR FR1 DUT. + +The TRS with Anechoic Chamber method is defined as: + +$$TRS = \frac{4\pi}{\int_{\theta=0}^{\pi} \int_{\phi=0}^{2\pi} \left[ \frac{1}{EIS_{\theta}(\theta, \phi)} + \frac{1}{EIS_{\phi}(\theta, \phi)} \right] \sin \theta d\phi d\theta} \quad (5.6)$$ + +Where the effective isotropic sensitivity (EIS) is defined as the minimum power level at which the throughput exceeds or equal to 95% of the maximum throughput of the specified RMC, at each sampling point. + +Where $EIS_{\theta}$ and $EIS_{\phi}$ are the EIS in the corresponding $\theta$ and $\phi$ polarizations. + +The summation form based on the $\sin\theta \cdot \Delta\theta$ weights of TRS with Anechoic Chamber method defined as: + +$$TRS \approx \frac{2NM}{\pi \sum_{n=0}^{N-1} \sum_{m=0}^{M-1} \left[ \frac{1}{EIS_{\theta}(\theta_n, \phi_m)} + \frac{1}{EIS_{\phi}(\theta_n, \phi_m)} \right] \sin \theta_n} \quad (5.7)$$ + +Where N and M are the number of sampling intervals for $\theta$ and $\phi$ . $\theta_n$ and $\phi_m$ are the measurement angles. + +The summation form based on the Clenshaw-Curtis quadrature integral approximation of TRS with Anechoic Chamber method is defined as: + +$$TRS \approx \frac{2M}{\sum_{n=0}^N \sum_{m=0}^{M-1} \left[ \frac{1}{EIS_{\theta}(\theta_n, \phi_m)} + \frac{1}{EIS_{\phi}(\theta_n, \phi_m)} \right] W(\theta_n)} \quad (5.8)$$ + +Where the value of $W(\theta_n)$ follows Equation 5.5. + +The applicability of TRP quadratures, frequency ranges, and measurement grids is tabulated in Table 5.2.1-1. + +**Table 5.2.1-1: Applicability for TRS measurement grids** + +| Frequency Range | Quadrature | $\Delta\theta=\Delta\phi$ [ $^{\circ}$ ] | N | M | Min. Number of Grid Points | +|-----------------|-----------------|------------------------------------------|---|----|----------------------------| +| < 3GHz | $\sin(\theta)$ | 30 | 6 | 12 | 62 | +| | Clenshaw-Curtis | 30 | 6 | 12 | 62 | +| > 3GHz | $\sin(\theta)$ | 30 | 6 | 12 | 62 | +| | Clenshaw-Curtis | 30 | 6 | 12 | 62 | +| | | 45 | 4 | 8 | 26 (Note 1) | + +Note 1: When the back pole at $\theta = 180^{\circ}$ cannot be measured due to obstruction and/or blocking, extrapolation is used to estimate EIS at $\theta = 180^{\circ}$ for measurement grids with $\Delta\theta=\Delta\phi=45^{\circ}$ by either a) using at least two points within $15^{\circ}$ of the pole or b) averaging the last cut (i.e. $\theta = 135^{\circ}$ ) + +### 5.2.2 Definition of the Total Radiated Sensitivity (TRS) for RC method + +The calculation of TRS is based on searching for the lowest power received by the UE for a discrete number of field combinations in the chamber. The downlink power received by the UE at each discrete field combination that provides a BER (or BLER) which is better than the specified target BER/BLER level shall be averaged with other such measurements using different field combinations. By calibrating the average power transfer function, an absolute value of the TRS can be obtained when the linear values of all downlink power levels have been averaged. + +The TRS with Reverberation Chamber method is defined as: + +$$TRS = (P_{ref} (1 - R) C) \left( \frac{1}{M} \sum_{m=1}^M \frac{1}{P_{BSS}(m)} \right)^{-1}$$ + +Where $P_{ref}$ is the reference power transfer function for the fixed measurement antenna, $R$ is the reflection coefficient for the fixed measurement antenna and $C$ is the path loss in the cables connecting the measurement receiver to fixed measurement antenna. The parameters are calculated from the calibration measurement and are further discussed in calibration section. $P_{BSS}(m)$ is the output power from the base station emulator when it is adjusted to give the specified digital error rate or throughput from the DUT for mode-stirring sample $m$ . + +# 6 UE positioning guidelines + +## 6.1 Free space + +For Free space configuration, the centre of the reference coordinate system shall be aligned with the geometric centre of the DUT in order to minimize the offset between antenna arrays integrated at any position of the UE and the centre of the quiet zone. + +**Table 6.1-1: UE positioning for Free space** + +| Test condition | DUT orientation | Diagram | +|----------------|-----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Free space DUT | $\alpha = 0^\circ;$
$\beta = 0^\circ;$
$\gamma = 0^\circ$ |

Image: Diagram of a mobile device (DUT) showing its orientation in a 3D coordinate system. The device is upright. The Z-axis is vertical, pointing up, with a rotation matrix R_z(gamma) indicated by a circular arrow. The X-axis points diagonally down-left, with a rotation matrix R_x(alpha) indicated. The Y-axis points horizontally to the right, with a rotation matrix R_y(beta) indicated.

| + +## 6.2 Hand phantom only (Browsing mode) + +The positioning specified in this clause is used for the test cases for Browsing Mode with Hand Phantom. The characteristics of the Hand Phantom are specified in Annex D. Browsing mode is used to simulate user cases where the DUT is held in hand, but not pressed against ear e.g. web browsing and navigation. For hand phantom only, the DUT shall be mounted in a suitable hand phantom and oriented such that the DUT's main display is tilted 45 degrees from vertical: + +- Wide Grip Hand for UE with Width $>72\text{mm}$ and $\leq 92\text{mm}$ +- PDA Grip Hand for UE with Width $\geq 56\text{mm}$ and $\leq 72\text{mm}$ + +### 6.2.1 Wide Grip Hand + +This positioning guideline is suitable for DUTs with width $>72\text{mm}$ and $\leq 92\text{mm}$ . + +The positioning guideline for mounting a DUT in the Wide Grip Hand Phantom defined in CTIA Certification OTA Test Plan 01.71 section 2.2.7 [14], is used for FR1 TRP TRS testing for UE with Width $>72\text{mm}$ and $\leq 92\text{mm}$ in this technical report. + +![Figure 6.2.1-1: Positioning guidance for Wide Grip Hand. The image shows two 3D renderings of a hand phantom holding a device. The left rendering shows the device in a teal color, and the right rendering shows it in a dark blue color. Blue arrows labeled 'contact surfaces' point to the areas where the device is in contact with the hand phantom's fingers and thumb.](48f188337e3ba41df38fab9ac0afb1bd_img.jpg) + +Figure 6.2.1-1: Positioning guidance for Wide Grip Hand. The image shows two 3D renderings of a hand phantom holding a device. The left rendering shows the device in a teal color, and the right rendering shows it in a dark blue color. Blue arrows labeled 'contact surfaces' point to the areas where the device is in contact with the hand phantom's fingers and thumb. + +**Figure 6.2.1-1: Positioning guidance for Wide Grip Hand (© 2001 – 2022 CTIA Certification. Reproduced with permission.), defined in the CTIA Certification OTA Test Plan** + +### 6.2.2 PDA Grip Hand + +This clause defines the positioning guideline for mounting a DUT in the PDA Grip Hand Phantom. This positioning guideline is suitable for DUTs with width $\geq 56\text{mm}$ and $\leq 72\text{mm}$ . + +To help achieve a consistent positioning, the DUT is aligned to a PDA palm spacer. No alignment tool is required. The PDA spacer features side and bottom walls to ensure consistent alignment of DUTs of various sizes. + +1. Place the DUT on the PDA spacer between the fingers and align the DUT to the side wall of the PDA. +2. If the DUT is shorter than 135 mm, then align the top of the DUT with the top of the PDA spacer. Otherwise, align the bottom of the DUT with the bottom wall of the PDA spacer. + +![Figure 6.2.2-1: Right-handed PDA Grip hand phantom with a spacer. The image shows a 3D rendering of a hand phantom holding a device. The device is aligned to a PDA spacer. Labels 'side wall' and 'bottom wall' with arrows point to the respective parts of the spacer.](b48d146cf1d6e0a01791f52572be6767_img.jpg) + +Figure 6.2.2-1: Right-handed PDA Grip hand phantom with a spacer. The image shows a 3D rendering of a hand phantom holding a device. The device is aligned to a PDA spacer. Labels 'side wall' and 'bottom wall' with arrows point to the respective parts of the spacer. + +**Figure 6.2.2-1: Right-handed PDA Grip hand phantom with a spacer** + +NOTE: Use left-handed (mirror-imaged) spacers with left-handed phantoms. + +## 6.3 Head and Hand phantom (Talk Mode) + +### 6.3.1 General + +The positioning specified in this clause is used for the test cases for Talk Mode using Head & Hand Phantom. The characteristics of the Hand Phantom and Head Phantom are specified in Annex D. + +Talk mode is used to simulate user cases where the DUT is placed into a hand phantom, which is holding the DUT against the SAM head phantom, presenting a realistic voice call operation of the DUT. Same as Browsing mode, the DUT for talk mode shall also be mounted in a suitable hand phantom: + +- Wide Grip Hand for UE with Width $>72\text{mm}$ and $\leq 92\text{mm}$ +- PDA Grip Hand for UE with Width $\geq 56\text{mm}$ and $\leq 72\text{mm}$ + +In this section, the procedure provides the guideline on how to place the DUT+hand against the head phantom. The detailed DUT positioning into hand phantom for talk mode is defined in section 6.3.2 and 6.3.3. + +For talk mode, the DUT is attached to the head phantom in “cheek” position. The DUT performance is measured on both left and right side of the head. Three points as shown in Figure 6.3.1-1 define the reference plane: centre of the right ear piece (RE), centre of the left ear piece (LE) and centre of mouth (M). + +Definition of the ‘Cheek’ position: + +1. Align the ear piece of the phone (see Figure 6.3.1-1) at the line RE-LE. Then, position the DUT beside the phantom so that the vertical line (see Figure 6.3.1-3) is parallel to the reference plane in Figure 6.3.1-2 and is aligned with the line M-RE on the reference plane (see Figure 6.3.1-3). +2. Position the DUT so that the ear piece of the DUT touches the ear piece of the phantom head on the line RE-LE. Tilt the DUT chassis towards the cheek of the phantom having the vertical line aligned with the reference plane until any point on the front side of the DUT is in contact with the cheek or until the contact with the ear is lost. + +NOTE: A holder fixture made of e.g. plastic may be used to position the handset against the phantom. + +![Figure 6.3.1-1: Reference plane on head phantom, front view. The diagram shows a front view of a head phantom. A dashed line labeled 'Reference plane' passes through three points: RE (Right Ear), LE (Left Ear), and M (Mouth). The RE and LE points are on the ears, and the M point is on the mouth.](c97b176986d994192dd844e17cd08e3a_img.jpg) + +Figure 6.3.1-1: Reference plane on head phantom, front view. The diagram shows a front view of a head phantom. A dashed line labeled 'Reference plane' passes through three points: RE (Right Ear), LE (Left Ear), and M (Mouth). The RE and LE points are on the ears, and the M point is on the mouth. + +Figure 6.3.1-1: Reference plane on head phantom, front view + +![Figure 6.3.1-2: Reference plane on head phantom, side view. The diagram shows a side view of a head phantom. A dashed line labeled 'Reference plane' passes through two points: RE (Right Ear) and M (Mouth). The RE point is on the ear, and the M point is on the mouth.](2bb31852174adbb3a45abf75f593ac36_img.jpg) + +Figure 6.3.1-2: Reference plane on head phantom, side view. The diagram shows a side view of a head phantom. A dashed line labeled 'Reference plane' passes through two points: RE (Right Ear) and M (Mouth). The RE point is on the ear, and the M point is on the mouth. + +Figure 6.3.1-2: Reference plane on head phantom, side view + +![Figure 6.3.1-3: Reference lines at a mobile handset. The diagram shows a blue mobile handset with a vertical dashed line labeled 'Vertical line' passing through the center. A horizontal dashed line labeled 'Horizontal line' passes through the top of the handset, near the 'ear piece'. The bottom of the handset is divided into two equal halves, each labeled 'Half'.](17a042ee648d9fdaddb609aead503980_img.jpg) + +Figure 6.3.1-3: Reference lines at a mobile handset. The diagram shows a blue mobile handset with a vertical dashed line labeled 'Vertical line' passing through the center. A horizontal dashed line labeled 'Horizontal line' passes through the top of the handset, near the 'ear piece'. The bottom of the handset is divided into two equal halves, each labeled 'Half'. + +**Figure 6.3.1-3: Reference lines at a mobile handset.** + +In addition, 6° tilt angle from the cheek is being used instead of having direct contact between the cheek and DUT. A mask may be used to help configuration of cheek + 6° tilt angle. The mask is a 32 mm wide conformal strip, created by sweeping the surface of the head phantom through a 6° rotation about the ear. Direct DUT contact against the mask thus establishes the required 6° spacing away from the cheek, regardless of DUT form factor. The material for the head phantom mask spacer shall have dielectric constant of less than 1.3 and a loss tangent of less than 0.003. Material additions can be used to help fixing of the mask spacer onto the head phantom. + +In summary, for head + hand phantom, keeping the DUT in the hand phantom in the position defined in clause 6.2, while place the DUT and the hand phantom against the head phantom in such way that the DUT is in 6° tilt angle as described above. + +### 6.3.2 Wide Grip Hand and Head + +This procedure is suitable for talk mode use with DUTs of width $>72\text{mm}$ and $\leq 92\text{mm}$ . The positioning of the DUT in the Wide Grip hand for talk mode is identical to that for browsing mode described in section 6.2.1. + +### 6.3.3 PDA Grip Hand and Head + +This procedure is suitable for talk mode use with DUTs of width $\geq 56\text{mm}$ and $\leq 72\text{mm}$ . The positioning of the DUT in the PDA Grip hand for talk mode is identical to that for browsing mode described in section 6.2.2. + +## 6.4 Head phantom only + +The positioning specified in this clause is used for the test cases for test cases using Head Phantom only. The characteristics of the Head Phantom is specified in Annex D.1. + +Positioning of the DUT against the head only is analogous to the positioning of the DUT for the head+hand (talk mode) configuration of section 6.3.1 with the exception that direct contact with the cheek of the head phantom is used instead of the 6° tilt angle from the cheek. The same coordinate system and reference points previously defined on the head phantom and DUT in section 6.3.1 are used. + +## 6.5 Forearm phantom + +### 6.5.1 Forearm Phantom placement in the chamber + +The Forearm Phantom shall be mounted in the chamber coordinate system as shown in Figure 6.5.1-1. + +![Figure 6.5.1-1: Positioning guidance for Forearm Phantom in the chamber. The image shows a black forearm phantom with a wrist-worn device mounted on it. A coordinate system is overlaid with a blue Z-axis pointing upwards, a green Y-axis pointing to the right, and a red X-axis pointing to the left. The device is positioned on the phantom's wrist area.](0e62b4ac2303ba5f3ff10123a7c0f273_img.jpg) + +Figure 6.5.1-1: Positioning guidance for Forearm Phantom in the chamber. The image shows a black forearm phantom with a wrist-worn device mounted on it. A coordinate system is overlaid with a blue Z-axis pointing upwards, a green Y-axis pointing to the right, and a red X-axis pointing to the left. The device is positioned on the phantom's wrist area. + +**Figure 6.5.1-1: Positioning guidance for Forearm Phantom in the chamber (© 2001 – 2022 CTIA Certification. Reproduced with permission.), defined in the CTIA Certification OTA Test Plan** + +### 6.5.2 Wrist-Worn RedCap Device mounted on the Forearm Phantom + +This positioning guideline is suitable for wrist-worn RedCap devices. + +The positioning guideline defined in CTIA Certification OTA Test Plan 01.71 section 2.3 [14], is used for FR1 TRP TRS testing for wrist-worn RedCap devices in this technical report. + +The Wrist-worn Device should be fully aligned under some specific virtual Plane to make sure the Wrist-worn Device is properly mounted on the Forearm Phantom. Plane *J* cuts through the surface of the forearm phantom and passes through the target test position and is perpendicular to the Y-axis. Plane *J* is the X-Z plane. Plane *K* cuts through the forearm phantom at the target test position and is perpendicular to the Z-axis. Plane *K* is the X-Y plane. Plane *A* and Plane *B* are virtual planes on wrist-worn device. Plane *A* cuts through the center of wrist band and Plane *B* cuts through the center of the display. + +Plane *B* shall be fully aligned with Plane *J* when the device is mounted on the forearm phantom. + +![Figure 6.5.2-1: Positioning guidance for Wrist-Worn Device mounted on the Forearm Phantom. The image shows two views of the device on the phantom. The left view shows the device from the front, with a red vertical line labeled 'Plane J' and a green horizontal line labeled 'Plane B'. The right view shows the device from the side, with a blue horizontal line labeled 'Plane K' and 'Plane A'. A yellow arrow points to the intersection of the device and the phantom, labeled 'Intersection at Face of Phantom'.](e384b831b3fb26071365a8ad1add04f1_img.jpg) + +Figure 6.5.2-1: Positioning guidance for Wrist-Worn Device mounted on the Forearm Phantom. The image shows two views of the device on the phantom. The left view shows the device from the front, with a red vertical line labeled 'Plane J' and a green horizontal line labeled 'Plane B'. The right view shows the device from the side, with a blue horizontal line labeled 'Plane K' and 'Plane A'. A yellow arrow points to the intersection of the device and the phantom, labeled 'Intersection at Face of Phantom'. + +**Figure 6.5.2-1: Positioning guidance for Wrist-Worn Device mounted on the Forearm Phantom (© 2001 – 2022 CTIA Certification. Reproduced with permission.), defined in the CTIA Certification OTA Test Plan** + +DUTs shall be mounted with sufficiently snug band tightness so as to prevent the DUT from slipping off under the force of gravity when the phantom is inverted. + +Similar to handheld UEs, there are also two Orientations for Wrist-worn RedCap Devices representing the Left and Right Wrist, as shown in Figure 6.5.2-2. + +![Two forearm phantoms with wrist-worn devices.](c1c7af7ea36be0323047962df57d75b0_img.jpg) + +Two dark grey forearm phantoms standing vertically. Each has a black wrist-worn device with a digital display. The left phantom's device shows '0:15' and the right one shows '0:01'. Both phantoms have white vertical scale markings. + +Two forearm phantoms with wrist-worn devices. + +Figure 6.5.2-2: Left and Right positioning for Wrist-Worn Device on Forearm Phantom (© 2001 – 2022 CTIA Certification. Reproduced with permission.), defined in the CTIA Certification OTA Test Plan + +# 7 Anechoic Chamber method (Reference method) + +## 7.1 General + +This Clause define the test method with Anechoic Chamber system, which is agreed as a reference method for FR1 TRP and TRS testing. + +## 7.2 Test setup + +For FR1 TRP TRS testing, both Single-antenna and multiple-antennas anechoic chambers can be applied. In Figure 7.2-1, an example TRP TRS test system with combined axes system is presented. + +![Schematic of an FR1 TRP TRS OTA test system.](e2c1c672349c10dccb2563eff6d8260e_img.jpg) + +A schematic diagram of an FR1 TRP TRS OTA test system inside an anechoic chamber. On the left, a horn antenna (B) is mounted on the chamber wall. On the right, a test equipment (e.g., Communication Tester) is connected via a cable (C) to a switch unit. The switch unit is connected to a 'Link' point on a rotating turntable. The turntable is mounted on a vertical axis (A) which is the coordinate reference point. The test equipment is also connected to the antenna (B) via a cable. The diagram shows the test equipment connected to the antenna (B) and the test equipment connector (C) on the test equipment. The coordinate reference point (A) is indicated by a blue dot on the vertical axis. The Link point is indicated by a red dot on the turntable. + +Schematic of an FR1 TRP TRS OTA test system. + +Figure 7.2-1: Example of a FR1 TRP TRS OTA test system with combined axis + +In Figure 7.2-2, an example TRP TRS test system with distributed axes system is presented. + +![Figure 7.2-2: Example of a FR1 TRP TRS OTA test system with distributed axis. The diagram shows a Device Under Test (DUT) on a rotating turntable inside an anechoic chamber. A 'Test Antenna' is positioned to receive signals from the DUT, with a blue arrow indicating the angle theta. A 'Link' antenna is also shown. The 'Test Antenna' is connected to a 'Switch Unit', which is then connected to 'Test Equipment (e.g. Communication Tester)'. The 'Link' antenna is also connected to the 'Test Equipment'.](d0abac95583b52a3b35f74a215567334_img.jpg) + +Figure 7.2-2: Example of a FR1 TRP TRS OTA test system with distributed axis. The diagram shows a Device Under Test (DUT) on a rotating turntable inside an anechoic chamber. A 'Test Antenna' is positioned to receive signals from the DUT, with a blue arrow indicating the angle theta. A 'Link' antenna is also shown. The 'Test Antenna' is connected to a 'Switch Unit', which is then connected to 'Test Equipment (e.g. Communication Tester)'. The 'Link' antenna is also connected to the 'Test Equipment'. + +Figure 7.2-2: Example of a FR1 TRP TRS OTA test system with distributed axis + +## 7.3 Calibration procedure + +The relative power values of the measurement points will be transformed to absolute radiated power values (in dBm) by performing a range path loss calibration measurement. The system needs to be calibrated by using a reference calibration antenna with known gain values. In the range path loss calibration measurement, the reference antenna is measured in the same place as the DUT, i.e. the center of the QZ, and the attenuation of the complete transmission path ( $L_{total}$ ) from the DUT to the measurement receiver/BS simulator is calibrated out. + +![Figure 7.3-1: Example FR1 TRP TRS calibration setup. The diagram shows a calibration setup inside an anechoic chamber. A reference calibration antenna (B) is placed on the left. On the right, a measurement antenna (A) is mounted on a stand. The measurement antenna is connected to a Network Analyzer (E) via a cable. The Network Analyzer (C) is also connected to a Switch Unit. The Switch Unit is connected to the measurement antenna (A). The reference antenna (B) is connected to the Network Analyzer (E). The coordinate reference point (A) is indicated at the center of the test zone.](07b17a620c75522d53916a11e12d1bff_img.jpg) + +Figure 7.3-1: Example FR1 TRP TRS calibration setup. The diagram shows a calibration setup inside an anechoic chamber. A reference calibration antenna (B) is placed on the left. On the right, a measurement antenna (A) is mounted on a stand. The measurement antenna is connected to a Network Analyzer (E) via a cable. The Network Analyzer (C) is also connected to a Switch Unit. The Switch Unit is connected to the measurement antenna (A). The reference antenna (B) is connected to the Network Analyzer (E). The coordinate reference point (A) is indicated at the center of the test zone. + +Figure 7.3-1: Example FR1 TRP TRS calibration setup + +The calibration measurement is repeated for each measurement path (two orthogonal polarizations and each signal path). The range path loss calibration measurement is performed in a two-step process including total path loss measurement and cable calibration. + +Step 1: Cable calibration: the measurement of path loss $L_{DE}$ , by connecting the cable from D to E to the two ports of VNA, and measure the cable path loss. + +Step 2: Total path loss measurement: the measurement of total path loss $L_{BC}$ : + +1. Place the reference calibration antenna (e.g. reference dipole) in the center of the test zone aligned with $\theta$ polarization of the measurement antenna, connected to a VNA port E, with the other VNA port C connected to the input of the Switch box – in Figure 7.3-1. +2. Configure the proper output power of VNA. +3. Measure the response $L_{CE}$ of each path from each $\theta$ polarization of the measurement antenna to the reference antenna in the center of QZ. +4. Repeat the steps 1 to 3 with the reference antenna aligned with the $\phi$ polarization of the measurement antenna. + +Then, the $L_{total} = (L_{CE} - L_{DE} + G_{cal})$ , Where $L_{DE}$ is cable loss from D to E. $G_{cal}$ is the gain or efficiency of the calibration antenna at the frequency of interest. In TRP and TRS measurements point C is connected to the calibrated input/output port of measurement receiver. + +This range path loss calibration procedure is common to both SA and EN-DC measurements. + +## 7.4 TRP Test procedure + + + +### 7.4.1 General + +For TRP and TRS testing in SA or EN-DC mode, measurements should be only performed at NR carrier. The LTE link antenna in EN-DC mode is used to provide a stable LTE link to the DUT without precise path loss or polarization control. + +The TRP of the DUT is measured by sampling the radiated transmit power of the DUT with three-dimensional scan at various locations surrounding the device. The measurement is performed with a constant sampling step of 15 degrees in both theta ( $\theta$ ) and phi ( $\phi$ ) axes for TRP measurement. This accounts for a total of 266 measurements for each of two orthogonal polarizations since measurements at theta = 0 and 180 degrees only require one measurement each. For some test system can not measure 180° EIRP, then the extrapolation approach can be adopted when generating the 3D antenna pattern. All of the measured power values will be integrated to TRP, as defined in Clause 5.1.1. + +For TRP measurement, the evaluations shall be performed at maximum transmit power. + +### 7.4.2 TRP test procedure for NR 1Tx configuration + +#### 7.4.2.1 UE configuration + +For devices containing multiple Tx antennas, the Tx Antenna Switching (TAS) function should be OFF, and the TRP should be measured for each Tx antenna individually. The antenna with better TRP is identified as the primary antenna, and the corresponding TRP result will be used to determine the pass/fail compliance. Otherwise, the primary antenna should be selected based on manufacturer declaration. To ensure the TAS OFF testing, the manufacture should provide either software/guidance to lab to control which Tx antenna is used, or the pre-configured DUT locked at primary antenna. + +For Standalone, the NR System Simulator (SS) and DUT shall be configured per TS 38.521-1 [5], section 6.2.1 (UE maximum output power) using the default settings specified in TS 38.521-1 [5] and TS 38.508-1 [7] as applicable. The measurement should be carried out based on the detailed test parameters for each band, as defined in Clause 4.3. + +For EN-DC, the SS and DUT shall be configured per TS 38.521-3 [6], Section 6.2B.1 (UE Maximum Output Power for EN-DC) using the default settings specified in TS 38.521-3 [6] and TS 38.508-1 [7] as applicable. The measurement should be carried out based on the detailed test parameters for each band, as defined in Clause 4.3. The UL output power of LTE carrier should be set as a constant power of 10dBm, while measuring NR at maximum output power, i.e., with fixed p-MaxEUTRA-r15=10 dBm, and p-NR-FR1 not configured. + +#### 7.4.2.2 Test procedure + + + +For UE configured with 1Tx for NR carrier, SA or EN-DC mode, the measurement procedure includes the following steps: + +- 1) Place the DUT inside the QZ following the positioning guideline defined in Clause 6. +- 2) Connect the SS with the DUT through the link antenna following steps 1 and 2 in section 6.2.1.4.2 of TS 38.521-1 [5] and ensure the DUT transmits with its maximum power. +- 3) Measure the power at each measurement point, and calculate $EIRP(\theta, \phi)$ by adding the composite loss of the entire transmission path. + +The TRP value is calculated using the TRP integration approaches outlined in Clause 5.1.1. + +### 7.4.3 TRP test procedure for NR 2Tx configuration + + + +#### 7.4.3.1 UE configuration + +In general, the UE 2Tx configuration can be categorized into two test cases, i.e., TxD and UL-MIMO. + +For TxD test case, the TRP should be measured with all the Tx antenna ON. For SA, the NR System Simulator (SS) and DUT shall be configured per TS 38.521-1 [5], section 6.2G.1 (UE maximum output power for Tx Diversity) using the default settings specified in TS 38.521-1 [5] and TS 38.508-1 [7] as applicable. The measurement should be carried out based on the detailed test parameters for each band, as defined in Clause 4.3 of this TR. + +FFS phase issue between 2Tx antennas under TxD configuration, e.g., with additional UE-specific configuration based on UE declaration. + +For single-layer UL-MIMO, the baseline TRP measurement should be performed with all the Tx antenna ON. The detailed TPMI configuration for each UE type is as following: + +- For non-coherent UE support fullpowerMode1, fixed TPMI index =2 as baseline configuration +- For non-coherent UE does not support fullpowerMode1, single-layer UL-MIMO TRP testing is not required. +- For coherent UE, two or four TPMI index from TPMI index =2~5 based on UE declaration. + +#### 7.4.3.2 TxD TRP Test procedure + + + +For UE configured with 2Tx for TxD mode, the measurement procedure of TRP includes the following steps: + +- 1) Place the DUT inside the QZ following the positioning guideline defined in Clause 6. +- 2) Connect the SS with the DUT through the link antenna following steps 1 and 2 in section 6.2G.1.4.2 of TS 38.521-1 [5] and ensure the DUT transmits with its maximum power. +- 3) Measure the power at each measurement point, and calculate $EIRP(\theta, \phi)$ by adding the composite loss of the entire transmission path. + +The TRP value is calculated using the TRP integration approaches outlined in Clause 5.1.1. + +#### 7.4.3.3 Single-layer UL-MIMO TRP Test procedure + +For non-coherent UE support fullpowerMode1, the test procedure for single-layer UL-MIMO TRP Testing is as following: + +- 1) Place the DUT inside the QZ following the positioning guideline defined in Clause 6. +- 2) Connect the SS with the DUT through the link antenna following step 4 for ULFPTx in section 6.2D.1.4.2 of TS 38.521-1 [5] with the exception of UE configuration defined in clause 7.4.3.1 and ensure the DUT transmits with its maximum power. +- 3) Measure the power at each measurement point, and calculate $EIRP(\theta, \phi)$ by adding the composite loss of the entire transmission path. + +The TRP value is calculated using the TRP integration approaches outlined in Clause 5.1.1. + +For coherent UE UL-MIMO TRP testing, the common test procedure is as following: + +- 1) Place the DUT inside the QZ following the positioning guideline defined in Clause 6. +- 2) Connect the SS with the DUT through the link antenna following steps for ULFPTx in section 6.2D.1.4 of TS 38.521-1 [5] with the exception of UE configuration defined in clause 7.4.3.1 and ensure the DUT transmits with its maximum power. +- 3) Set the SS to transmit $TPMI_i$ with $[i=2]$ . +- 4) Measure the power and calculate $EIRP(TPMI_i, \theta, \phi)$ by adding the composite loss of the entire transmission path. +- 5) Repeat steps 3) and 4) for the remaining or subset of $TPMI_i$ with $[i=\{3,4,5\}]$ . +- 6) Repeat steps 3) to 5) for each measurement grid point. + +Note: Based on different test system implementation, step 5 and step 6 may be switched. + +How to data processing the measured EIRPs is FFS. + +### 7.4.4 TRP test procedure for NR DL CA configuration + +#### 7.4.4.1 UE configuration + +For UE radiated conformance testing P-MPRc shall be 0 dB. + +FR1 TRP and TRS radiated conformance testing shall be performed with the UE consistently operating at maximum power level, e.g., Time-Averaged Algorithm (TAA) and other power back-off functions should be disabled. The above functions OFF should be based on manufacturer declaration, if declared, then the manufacturer is required to provide a mechanism for the test lab to enable/disable the function. + +The NR SS should send continuous uplink power control “up” commands to the DUT to ensure the DUT’s transmitter is at maximum output power during the CA TRP and TRS test. + +For devices containing multiple Tx antennas, the Tx Antenna Switching (TAS), the guidelines specified in Clause 7.4.2 of TR 38.870 shall be used. However, devices supporting dual Tx in CA mode, without TAS, it can be tested as normal, namely no special handling of the Tx antennas is needed. + +For CA, the SS and DUT shall be configured per TS 38.521-1 [5], Section 6.2A.1 (UE Maximum Output Power for CA) using the default settings specified in TS 38.521-1 [5] and TS 38.508-1 [7] as applicable. The measurement should be carried out based on the detailed test parameters for each band, as defined in Table 4.3.3-1 in TR 38.870. + +#### 7.4.4.2 Test procedure + +For UE configured with inter-band DL CA (two bands) with only single uplink CC, the measurement procedure includes the following steps: + +- 1) Place the DUT inside the QZ following the positioning guideline defined in Clause 6. +- 2) Connect the SS with the DUT through the link antenna following steps 1 and 2 in section 6.2A.1.1.4.2 of TS 38.521-1 [5] and ensure the DUT transmits with its maximum power. +- 3) Measure the power for the UL CC at each measurement point, and calculate $EIRP(\theta, \phi)$ by adding the composite loss of the entire transmission path. + +The TRP value is calculated using the TRP integration approaches outlined in Clause 5.1.1. + +## 7.5 TRS Test procedure + + + +### 7.5.1 General + +For SA and EN-DC, the TRS of the DUT is measured by sampling effective isotropic sensitivity (EIS) of the DUT with three-dimensional scan at various locations surrounding the device. The measurement is performed with a constant sampling step of 30 degrees in both theta ( $\theta$ ) and phi ( $\phi$ ) axes for TRS measurement. + +EIS, or receiver sensitivity measurements, is defined as the minimum downlink signal power received at the UE antenna input required to provide a data throughput rate greater than or equal to 95% of the maximum throughput of the reference measurement channel (RMC) (the maximum throughput is per Appendix A of TS 38.521-1 [5]). + +For TRS measurement, the evaluations shall be performed at maximum transmit power. + +For TRS measurement, no specific setting is needed for Rx antennas. By default, the maximum number of Rx antennas supported at each band should be enabled during the TRS test. + +### 7.5.2 TRS test procedure for NR 1Tx configuration + +#### 7.5.2.1 UE configuration + + + +For Standalone, the NR System Simulator (SS) and DUT shall be configured per section 7.3.2 (Reference sensitivity power level) of TS 38.521-1 [5] using the defaults specified in TS 38.521-1 [5] and TS 38.508-1 [7] as applicable. The measurement should be carried out based on the detailed test parameters for each band, as defined in Clause 4. + +For EN-DC, the EN-DC SS and DUT shall be configured per section 7.3B.2 (Reference Sensitivity for EN-DC) of TS 38.521-3 [6], using the defaults specified in TS 38.521-3 [6] and TS 38.508-1 [7], as applicable. The measurement should be carried out based on the detailed test parameters for each band, as defined in Clause 4. The UL power configuration for LTE and NR is 50%-50% power splitting, i.e., + +- For PC3, p-MaxEUTRA-r15=20 dBm, and p-NR-FR1= 20dBm; +- or PC2, p-MaxEUTRA-r15=23 dBm, and p-NR-FR1= 23dBm. + +Different from handheld UE, a Redcap UE is required to be equipped with a minimum of single Rx antenna and maximum of two Rx antenna. + +#### 7.5.2.2 Test Procedure + + + +For UE configured with 1Tx for NR carrier, SA or EN-DC mode, the measurement procedure includes the following steps: + +- 1) Place the DUT inside the QZ following the positioning guideline defined in Clause 6. +- 2) Connect the SS with the DUT through the measurement antenna. +- 3) Follow steps 1 through 4 in section 7.3.2.4.2 of TS 38.521-1 [5], with the following exception: determine each EIS, i.e., by adjusting the downlink signal level until the minimum power level at which the throughput exceeds or equal to 95% of the maximum throughput of the specified RMC, at each sampling point. The downlink power step size shall be no more than 0.5 dB when the RF power level is near the NR sensitivity level. + +The TRS value is calculated using the equation outlined in Clause 5.2.2. + +### 7.5.3 TRS test procedure for NR 2Tx configuration + +#### 7.5.3.1 UE configuration + +For TRS testing of UE with TxD, the UE configuration is same as Clause 7.5.2.1, with an exception configuration that all Tx antenna shall be ON and consistently operating at maximum power level condition. + +For TRS testing of UE with single-layer UL-MIMO (coherent UE and non-coherent UE), the UE configuration is same as Clause 7.5.2.1, with exception that all Tx antenna shall be ON, the UE shall be configured by fixed TPMI index =2 and consistently operating at maximum power level condition. + +#### 7.5.3.2 Test procedure + +For UE TRS testing under TxD or single-layer UL-MIMO configuration, the general test procedure defined in Clause 7.5.2.2 applies. + +### 7.5.4 TRS test procedure for NR DL CA configuration + + + +#### 7.5.4.1 UE configuration + +The CA SS and DUT shall be configured per section 7.3A.1 (Reference sensitivity power level for 2DL CA without exception) of TS 38.521-1 [5], using the defaults specified in TS 38.521-1 [5] and TS 38.508-1 [7], as applicable. The measurement should be carried out based on the detailed test parameters for each band, as defined in Table 4.3.3-2, in Clause 4.3.3. + +#### 7.5.4.2 Test procedure + +For UE configured with inter-band DL CA (two bands) with only single uplink CC, the measurement procedure includes the following steps: + +- 1) Place the DUT inside the QZ following the positioning guideline defined in Clause 6. +- 2) Connect the SS with the DUT through the link antenna following steps 1 and 2 in section 7.3A.1.4.2 of TS 38.521-1 [5] and ensure the DUT transmits with its maximum power. +- 3) Follow steps 1 through 4 in section 7.3A.1.4.2 of TS 38.521-1 [5], with the following exception: determine each EIS per CC, i.e., by adjusting the downlink signal level until the minimum power level at which the throughput exceeds or equal to 95% of the maximum throughput of the specified RMC, at each sampling point. The downlink power step size shall be no more than 0.5 dB when the RF power level is near the NR sensitivity level. + +The TRS value per CC is calculated using the equation outlined in Clause 5.2.2. + +## 7.6 Ripple Test for Quiet Zone + +### 7.6.1 General + +The ripple test procedure is defined in this clause. Frequencies to be used for ripple test: + +**Table 7.6.1-1: Frequencies for FR1 ripple test** + +| NR FR1 Bands | Range | Test frequency (MHz) | +|-----------------------------|-------|----------------------| +| n71 | Low | 617MHz | +| n12, n17, n29, n14, n28 | | 722MHz | +| n5, n8, n18, n20 | | 836.5MHz | +| n50, n51, n74 | Mid | 1575.42MHz | +| n3, n2, n25, n39 | | 1880MHz | +| n1, n34, n65 | | 2132.5MHz | +| n7, n30, n41, n40, n38, n90 | | 2450MHz | +| n77, n78 | High | 3600MHz | +| n79 | | [4700MHz] | + +### 7.6.2 Ripple test procedure + +Unwanted reflections and support structure blockage cause a volumetric ripple to the field magnitude measured by or created by the measurement antenna as shown in Figure 7.6.2-1, affecting every possible test point within a desired test volume. By rotating an omnidirectional antenna through the test volume as illustrated by the red line, this volumetric ripple may be probed to obtain an estimate of the measurement uncertainty due to this volumetric error. Note, however, that the volumetric ripple caused by multipath reflections is related to the wavelength and the relative path lengths of the direct and reflected paths to the measurement antenna, and is not inherently a function of the test volume. As illustrated in Figure 7.6.2-1(left), when the wavelength is relatively large compared to the test volume, it may not be possible to probe the entire range of errors that may actually exist within the test volume. Doing so would require probing an area larger than the test volume in order to accurately estimate the error within the test volume. Even when the test volume is several wavelengths in size, a given evaluation of the ripple may not completely caliper the worst-case error conditions within the test volume (Figure 7.6.2-1 (right)). + +![Figure 7.6.2-1: Volumetric ripple and 20cm Phi axis cut. The figure contains two side-by-side heatmaps. The left heatmap is titled 'Volumetric Ripple - 750 MHz' and the right is titled 'Volumetric Ripple - 5500 MHz'. Both plots show 'Path Loss Error Due to Multipath (dB)' on a color scale from -0.7 (dark purple) to 0.7 (dark red). The x-axis and y-axis both range from -0.15 to 0.15 meters. A red circle with a radius of 0.1 meters (20 cm) is overlaid on each plot, centered at the origin (0,0). The 750 MHz plot shows a smoother, less detailed ripple pattern compared to the 5500 MHz plot, which shows more pronounced and complex ripple structures.](6bbc398f520a7bcc5491cab18d3e4cac_img.jpg) + +Figure 7.6.2-1: Volumetric ripple and 20cm Phi axis cut. The figure contains two side-by-side heatmaps. The left heatmap is titled 'Volumetric Ripple - 750 MHz' and the right is titled 'Volumetric Ripple - 5500 MHz'. Both plots show 'Path Loss Error Due to Multipath (dB)' on a color scale from -0.7 (dark purple) to 0.7 (dark red). The x-axis and y-axis both range from -0.15 to 0.15 meters. A red circle with a radius of 0.1 meters (20 cm) is overlaid on each plot, centered at the origin (0,0). The 750 MHz plot shows a smoother, less detailed ripple pattern compared to the 5500 MHz plot, which shows more pronounced and complex ripple structures. + +**Figure 7.6.2-1: Volumetric ripple and 20cm Phi axis cut** + +Conversely, field non-uniformities in the test volume caused by amplitude taper of the measurement antenna and shadowing of portions of the test volume by support structure are geometric in nature and relate directly to the size of the test volume and the related factors of the measurement antenna and support structure. This test procedure attempts to capture the impact of these effects to within the practical limits of the available test volume and test equipment expected in the lab. + +The quiet zone ripple test covers two cylindrical test volumes, one for handsets and smaller devices, with or without head and/or hand phantoms, and a larger volume for testing up to notebook PC sized devices. The smaller cylinder is 30 cm in diameter, concentric to the phi axis, and 30 cm tall along the phi axis, centered on the intersection of the theta and phi axes. The larger cylinder is 50 cm in diameter, concentric to the phi axis, with the base of the cylinder coincident with that of the smaller cylinder and a height of 36 cm along the phi axis. The test consists of a set of individual ripple tests about the phi- and theta-axes utilizing both electric dipoles and magnetic loop dipoles to generate uniform omnidirectional dipole-like patterns about the axis of rotation. Data is measured on the co-polarized measurement antenna element for each corresponding test. + +For the phi-axis ripple test, each reference antenna is oriented with its axis parallel to the phi axis at a total of three positions, offset 15 cm perpendicular to the phi axis with 0 cm and $\pm 15$ cm offsets parallel to the phi axis. At each position, the phi axis is rotated $360^\circ$ to record the ripple. Each position is labeled by its radial and axial offset from the center position, $(R, Z)$ . See Figure 7.6.2-2 for additional information. + +![Figure 7.6.2-2: Phi-axis test geometry. Two diagrams of a cylinder with a vertical 'Phi Axis'. The left diagram shows three yellow cylindrical test positions along the surface, with dimensions of 15 cm for the radius and 15 cm for each of two vertical segments. The right diagram shows three green circular test positions at the same vertical levels. Both diagrams include a red circular arrow at the base indicating rotation around the phi axis.](0e62b4ac2303ba5f3ff10123a7c0f273_img.jpg) + +Figure 7.6.2-2: Phi-axis test geometry. Two diagrams of a cylinder with a vertical 'Phi Axis'. The left diagram shows three yellow cylindrical test positions along the surface, with dimensions of 15 cm for the radius and 15 cm for each of two vertical segments. The right diagram shows three green circular test positions at the same vertical levels. Both diagrams include a red circular arrow at the base indicating rotation around the phi axis. + +**Figure 7.6.2-2: Phi-axis test geometry** + +For the notebook sized test volume, three additional test positions are added to the phi-axis test in order to cover the larger test cylinder. These positions are offset 25 cm perpendicular to the phi axis with -15, 0, and +21 cm offsets parallel to the phi axis, as shown in Figure 7.6.2-3. + +![Figure 7.6.2-3: Phi-axis test geometry for the notebook sized test volume. Two diagrams of a larger cylinder with an inner cylinder. The left diagram shows three yellow cylindrical test positions along the outer surface, with dimensions of 25 cm for the outer radius, 21 cm for the top vertical segment, and 15 cm for the bottom vertical segment. The right diagram shows three green circular test positions at the same vertical levels. Both diagrams include a red circular arrow at the base indicating rotation around the phi axis.](35afbfc3c4a5c0fe01e91ba536605e09_img.jpg) + +Figure 7.6.2-3: Phi-axis test geometry for the notebook sized test volume. Two diagrams of a larger cylinder with an inner cylinder. The left diagram shows three yellow cylindrical test positions along the outer surface, with dimensions of 25 cm for the outer radius, 21 cm for the top vertical segment, and 15 cm for the bottom vertical segment. The right diagram shows three green circular test positions at the same vertical levels. Both diagrams include a red circular arrow at the base indicating rotation around the phi axis. + +**Figure 7.6.2-3: Phi-axis test geometry for the notebook sized test volume** + +For the theta-axis ripple test, each reference antenna is oriented with its axis parallel to the theta axis at a total of eight positions on the surface of the cylinder defined above. Defining Cartesian coordinates (X, Y, Z) with the Z-axis along the phi-axis, the Y-axis along the theta-axis, and the measurement antenna moving in the XZ plane relative to the reference antenna used for the ripple test, the test positions are given as $(\pm 15 \text{ cm}, 0, \pm 15 \text{ cm})$ and $(0, \pm 15 \text{ cm}, \pm 15 \text{ cm})$ , relative to the center of the test volume as shown in Figure 7.6.2-4. At each position, the theta axis is rotated over as much of $360^\circ$ as supported by the system to record the ripple (e.g. $\pm 165^\circ$ ). For systems that can only move theta in the range of $0-180^\circ$ or less, the phi axis may be rotated $180^\circ$ and a second cut measured to meet or exceed the $\pm 165^\circ$ range. Each position is labeled by its (X, Y, Z) offset from the center position. + +![Figure 7.6.2-4: Theta-axis test geometry. The figure consists of two diagrams. The left diagram shows a cylinder with a vertical Phi Axis and a horizontal Theta Axis. A red curved arrow indicates rotation around the Theta Axis. The right diagram shows the same cylinder with eight additional test positions marked by green dots. These positions are at a radius of 25 cm and are vertically offset by 15 cm from the central plane. The vertical offsets are labeled as 15 cm, 15 cm, and 15 cm.](c1c7af7ea36be0323047962df57d75b0_img.jpg) + +Figure 7.6.2-4: Theta-axis test geometry. The figure consists of two diagrams. The left diagram shows a cylinder with a vertical Phi Axis and a horizontal Theta Axis. A red curved arrow indicates rotation around the Theta Axis. The right diagram shows the same cylinder with eight additional test positions marked by green dots. These positions are at a radius of 25 cm and are vertically offset by 15 cm from the central plane. The vertical offsets are labeled as 15 cm, 15 cm, and 15 cm. + +**Figure 7.6.2-4: Theta-axis test geometry** + +For the notebook sized test volume, eight additional test positions are added to the theta-axis test in order to cover the larger test cylinder. These positions are given as $(\pm 25 \text{ cm}, 0, -15 \text{ cm})$ , $(\pm 25 \text{ cm}, 0, +21 \text{ cm})$ , $(0, \pm 25 \text{ cm}, 0, -15 \text{ cm})$ , and $(0, \pm 25 \text{ cm}, +21 \text{ cm})$ , as shown in Figure 7.6.2-5. + +![Figure 7.6.2-5: Theta-axis test geometry for the notebook sized test volume. The figure consists of two diagrams. The left diagram shows a larger cylinder with a vertical Phi Axis and a horizontal Theta Axis. A red curved arrow indicates rotation around the Theta Axis. The right diagram shows the same cylinder with additional test positions marked by green dots. These positions are at a radius of 25 cm and are vertically offset by 15 cm and 21 cm from the central plane. The vertical offsets are labeled as 25 cm, 21 cm, and 15 cm.](1408b3d336e1d80c7a1abd0682f4f687_img.jpg) + +Figure 7.6.2-5: Theta-axis test geometry for the notebook sized test volume. The figure consists of two diagrams. The left diagram shows a larger cylinder with a vertical Phi Axis and a horizontal Theta Axis. A red curved arrow indicates rotation around the Theta Axis. The right diagram shows the same cylinder with additional test positions marked by green dots. These positions are at a radius of 25 cm and are vertically offset by 15 cm and 21 cm from the central plane. The vertical offsets are labeled as 25 cm, 21 cm, and 15 cm. + +**Figure 7.6.2-5: Theta-axis test geometry for the notebook sized test volume** + +For each polarization and band, repeat the following steps: + +For the phi-axis ripple test: + +1. Place the measurement antenna and any associated theta-axis positioner at $\theta = 90^\circ$ such that the measurement antenna is boresight with the center of the quiet zone. The measurement antenna should be at the same separation distance to be used for actual pattern measurements. This distance must be at least the minimum measurement distance away from the center of the quiet zone as defined in clause 7.7. Select the polarization of the measurement antenna to correspond to the polarization (theta or phi) to be tested. +2. Mount the reference antenna to the phi-axis positioner using a low permittivity dielectric support. Use the sleeve dipole for the theta polarization and the loop for the phi polarization. At each of the specified offset positions, ensure that the axis of the reference antenna is parallel to the phi axis of rotation. +3. Attach a signal source to a coaxial cable feeding the measurement antenna and set the frequency to the appropriate channel. Set the amplitude to a level appropriate for the measurement receiver. Connect a measurement receiver to the reference antenna. The received signal during the ripple test measurement should be at least 40 dB above the noise floor or noise errors greater than 0.1 dB will result. Ensure that all coaxial cables are dressed to minimize effects upon the measurement results. + +4. Rotate the reference antenna about the phi axis and record the signal received by the measurement antenna at resolution sufficient to ensure smoothly varying curves for a total of 360°. +5. Record the measurement results in a format suitable for calculating the ripple test metric. +6. Record test parameters including: (a) the distance between the measurement and reference antennas, (b) cable losses and other losses associated with the measurement setup, (c) the power of the signal source at the reference antenna connector, and (d) the noise level of the receiver with no signal applied. +7. Repeat steps 1 through 6 above for each reference antenna (polarization and band) for each of the required test positions. In order to accommodate reference positioning in the lower portion of the quiet zone, support materials with a dielectric constant less than 1.2 may be removed to a maximum distance of 25 cm outside the quiet zone for the tests that require additional clearance. + +For the theta-axis ripple test: + +1. Place the measurement antenna such that it is boresight with the center of the quiet zone. The measurement antenna should be at the same separation distance to be used for actual pattern measurements. This distance must be at least the minimum measurement distance away from the center of the quiet zone as defined in clause 7.7. Select the polarization of the measurement antenna to correspond to the polarization (theta or phi) to be tested. +2. Mount the reference antenna in the quiet zone using a low permittivity dielectric support and such that rotating the theta positioner will cause the measurement antenna to rotate relative to the reference antenna. Use the sleeve dipole for the phi polarization and the loop for the theta polarization. At each of the specified offset positions, ensure that the axis of the reference antenna is parallel to the theta axis of rotation. +3. Attach a signal source to a coaxial cable feeding the measurement antenna and set the frequency to the appropriate channel. Set the amplitude to a level appropriate for the measurement receiver. Connect a measurement receiver to the reference antenna. The received signal during the ripple test measurement should be at least 40 dB above the noise floor or noise errors greater than 0.1 dB will result. Ensure that all coaxial cables are dressed to minimize effects upon the measurement results. +4. Rotate the reference antenna about the theta axis and record the signal received by the measurement antenna at resolution sufficient to ensure smoothly varying curves for a total of at least $\pm 165^\circ$ or the equivalent (e.g. 0-360°). For systems that are unable to rotate a full $\pm 165^\circ$ , the reference antenna may be mounted to the phi axis and two separate theta cuts from 0 to 165° may be taken, after rotating the phi axis 180° between the first and second cut. +5. Record the measurement results in a format suitable for calculating the ripple test metric. +6. Record test parameters including: (a) the distance between the measurement and reference antennas, (b) cable losses and other losses associated with the measurement setup, (c) the power of the signal source at the reference antenna connector, and (d) the noise level of the receiver with no signal applied. + +7. Repeat steps 1 through 6 above for each reference antenna (polarization and band) for each of the required test positions. In order to accommodate reference positioning in the lower portion of the quiet zone, support materials with a dielectric constant less than 1.2 may be removed to a maximum distance of 25 cm outside the quiet zone for the tests that require additional clearance. + +## 7.7 Minimum Range Length + +This sub-section specifies the minimum range lengths for NR FR1 TRP-TRS OTA systems. The range length is defined as the distance from the centre of the quiet zone to the aperture of the measurement probes/antennas, as illustrated in Figure 7.7.1-1. + +![Figure 7.7.1-1: Illustration of range length definition. The diagram shows a central grey circle labeled 'Quiet Zone with 30cm diameter'. A larger dashed circle surrounds it. A radius line labeled 'Range Length' extends from the center of the quiet zone to the outer dashed circle. An arrow points from the text 'Quiet Zone with 30cm diameter' to the inner grey circle.](0538daaa5583c23e17db3a12f2281a55_img.jpg) + +Figure 7.7.1-1: Illustration of range length definition. The diagram shows a central grey circle labeled 'Quiet Zone with 30cm diameter'. A larger dashed circle surrounds it. A radius line labeled 'Range Length' extends from the center of the quiet zone to the outer dashed circle. An arrow points from the text 'Quiet Zone with 30cm diameter' to the inner grey circle. + +**Figure 7.7.1-1: Illustration of range length definition** + +The minimum range length shall be the maximum of the following three limits + +- The phase uncertainty limit: $R_{QZ} + 2D_{rad}^2/\lambda$ +- The amplitude uncertainty limit: $3D$ +- The reactive Near-Field limit: $R_{QZ} + 2\lambda$ + +where $R_{QZ}$ is defined as the radius of the quiet zone, i.e., $R_{QZ} = D/2$ , and $D_{rad}$ is the diameter of the effective radiating aperture. The minimum range length calculations for $D=30\text{cm}$ quiet zone size TRP-TRS OTA test systems shall assume that $D_{rad}$ is 30cm below 1GHz and decrease linearly from 30cm to 5cm from 1GHz to 7.125GHz, respectively. The last column of Table 7.7.1-1 shall be considered the minimum range length for NR FR1 TRP-TRS OTA systems with 30cm quiet zone size. + +**Table 7.7.1-1: Minimum Range Length for NR FR1 TRP-TRS OTA systems with 30cm quiet zone size.** + +| $F$ [GHz] | $D_{rad}$ [m] | $R_{oz}+2D_{rad}^2/\lambda$ | $3D = 6R_{oz}$ | $R_{oz}+2\lambda$ | $\max(R_{oz}+2\lambda, 3D, R_{oz}+2D^2/\lambda)$ | +|-----------|---------------|-----------------------------|----------------|-------------------|--------------------------------------------------| +| 0.41 | 0.30 | 0.40 | 0.9 | 1.61 | 1.61 | +| 0.6 | 0.30 | 0.51 | 0.9 | 1.15 | 1.15 | +| 0.7 | 0.30 | 0.57 | 0.9 | 1.01 | 1.01 | +| 0.8 | 0.30 | 0.63 | 0.9 | 0.90 | 0.90 | +| 1 | 0.30 | 0.75 | 0.9 | 0.75 | 0.90 | +| 1.2 | 0.29 | 0.83 | 0.9 | 0.65 | 0.90 | +| 1.4 | 0.28 | 0.90 | 0.9 | 0.58 | 0.90 | +| 1.6 | 0.28 | 0.96 | 0.9 | 0.52 | 0.96 | +| 1.8 | 0.27 | 1.01 | 0.9 | 0.48 | 1.01 | +| 2 | 0.26 | 1.05 | 0.9 | 0.45 | 1.05 | +| 2.2 | 0.25 | 1.07 | 0.9 | 0.42 | 1.07 | +| 2.4 | 0.24 | 1.09 | 0.9 | 0.40 | 1.09 | +| 2.6 | 0.23 | 1.11 | 0.9 | 0.38 | 1.11 | +| 2.8 | 0.23 | 1.11 | 0.9 | 0.36 | 1.11 | +| 3 | 0.22 | 1.10 | 0.9 | 0.35 | 1.10 | +| 4 | 0.18 | 0.99 | 0.9 | 0.30 | 0.99 | +| 5 | 0.14 | 0.77 | 0.9 | 0.27 | 0.90 | +| 6 | 0.10 | 0.52 | 0.9 | 0.25 | 0.90 | +| 7 | 0.06 | 0.29 | 0.9 | 0.24 | 0.90 | +| 7.125 | 0.05 | 0.27 | 0.9 | 0.23 | 0.90 | + +# 8 Reverberation Chamber test methodology + +## 8.1 General + +This clause defines the test method with a Reverberation Chamber (RC) system as an alternate method for FR1 TRP and TRS testing. + +## 8.2 Test setup + +A reverberation chamber (RC) is an electrically large shielded metal enclosure that employs one or several "stirring" methods to randomize the fields, such as moving paddles, turntables, etc. In this way, a large number of uncorrelated samples is obtained. The volume in the room where the field is well-stirred is the working volume. Here the E-field, averaged over an entire stirring cycle, is independent of the location in the room, i.e., the field is spatially uniform. + +![Figure 8.2-1: Example Test setup diagram for Reverberation Chamber test methodology. The diagram shows a rectangular 'Reverberation chamber' containing a 'Mode stirrer/tuner' (a large, irregular shape) and a 'Testunit' (a small rectangle). A 'Fixed measurement antenna' is mounted on the top right wall of the chamber. A cable connects the antenna to a 'Base station simulator' box outside the chamber. An arrow labeled 'Same path for up- and downlink' points to this cable.](69edc2887e907309499ac95b47ab6905_img.jpg) + +Figure 8.2-1: Example Test setup diagram for Reverberation Chamber test methodology. The diagram shows a rectangular 'Reverberation chamber' containing a 'Mode stirrer/tuner' (a large, irregular shape) and a 'Testunit' (a small rectangle). A 'Fixed measurement antenna' is mounted on the top right wall of the chamber. A cable connects the antenna to a 'Base station simulator' box outside the chamber. An arrow labeled 'Same path for up- and downlink' points to this cable. + +Figure 8.2-1: Example Test setup diagram for Reverberation Chamber test methodology + +![Figure 8.2-2: S-parameter test setup diagram. The diagram shows a dashed rectangular boundary labeled 'RC' (Reverberation Chamber). Inside, on the left, is a 'Stirrer' (a vertical bar with a curved arrow indicating rotation). In the center is a 'Working volume' (a dashed rectangle) containing an 'RF Absorber' (a green rectangle labeled 'size of max EUT'). Four points are marked: 1 (top left), 2 (top right), 3 (bottom left), and 4 (bottom right). A 'REF TX' (Reference Transmitter) is at point 3, and an 'RX' (Receiver) is at point 2. A blue arrow labeled 'Transfer function' points from REF TX to RX. Below the chamber, a box labeled 'NA' (Network Analyzer) is connected to both REF TX and RX.](d244183a8ff3d94b0dcf30140f51020d_img.jpg) + +Figure 8.2-2: S-parameter test setup diagram. The diagram shows a dashed rectangular boundary labeled 'RC' (Reverberation Chamber). Inside, on the left, is a 'Stirrer' (a vertical bar with a curved arrow indicating rotation). In the center is a 'Working volume' (a dashed rectangle) containing an 'RF Absorber' (a green rectangle labeled 'size of max EUT'). Four points are marked: 1 (top left), 2 (top right), 3 (bottom left), and 4 (bottom right). A 'REF TX' (Reference Transmitter) is at point 3, and an 'RX' (Receiver) is at point 2. A blue arrow labeled 'Transfer function' points from REF TX to RX. Below the chamber, a box labeled 'NA' (Network Analyzer) is connected to both REF TX and RX. + +Figure 8.2-2: S-parameter test setup diagram + +## 8.3 Chamber Characterization + +### 8.3.1 S-parameters and power transfer functions + +Measurements of S-parameters in the reverberation chamber and derivations of power transfer functions are explained in detail in the calibration procedure. + +### 8.3.2 Chamber loading for coherence bandwidth + +The reverberation chamber can be loaded to control the power delay profile or coherence bandwidth in the chamber. However, the reverberation chamber should not be loaded to such an extent that the mode statistics in the chamber are impaired. It is important to keep the same loss profile in the chamber during calibration, measurement and test, in order not to change the average power transfer function between these two cases. Examples of lossy objects are blocks of RF absorber, head and hand phantoms. The configuration should be calculated to achieve a minimum coherence bandwidth of [5] times the sub-carrier spacing. + +#### 8.3.2.1 Coherence bandwidth calculation + +The coherence bandwidth (CBW) is a metric to determine the correlation in frequency within a working volume of a reverberation chamber (RC). To measure CBW, one should calculate the complex autocorrelation of the transmission parameter ( $S_{21}$ ) for each mode-stirred sample over a minimum [100] MHz bandwidth, as follows [21]: + +$$R(i, n) = \frac{\sum_{j=1}^{P-i} S_{21}(f_j, n) S_{21}^*(f_{j+i}, n)}{\sum_{j=1}^P S_{21}(f_j, n) S_{21}^*(f_j, n)} \quad (8.1)$$ + +Where $R(i, n)$ represents the normalized correlation function at the $i^{th}$ frequency step and the $n^{th}$ mode stirring sample. $S_{21}(f_j, n)$ represents the measured complex $S_{21}$ at the frequency step $f_j$ with [P] frequency points measured within a given bandwidth (BW) such that $f_1 = f_c - (\frac{BW}{2})$ and $f_P = f_c + (\frac{BW}{2})$ . The symbol \* represents the complex conjugation acting on this parameter. $n$ is the mode stirring sample index with a total number equal to [N]. $i$ is the frequency offset index with a frequency resolution of $\frac{f_P - f_1}{P-1}$ , i.e., $\Delta f = i \frac{f_P - f_1}{P-1}$ , and $-(P - 1) \leq i \leq (P - 1)$ [21]. + +The test points could be the same as in step (a) given in Section 8.3.3 namely, T=12 for chambers with a turntable or T=24 for chambers without a turntable. + +To measure CBW, follow these steps: + +- (a) Select the center frequency $f_c$ and BW. A typical measurement frequency range of min [100] MHz channel bandwidth is used as the default. +- (b) Determine the number of measurement points P with respect to frequency. +- (c) Determine the total number of stirring sequence N. +- (d) Measure the S-parameters, specifically $S_{21}$ and calculate the correlation function using equation 8.1. +- (e) Average the autocorrelation functions $R(i, n)$ over all mode stirring sequence (i.e. index $n$ ) at each frequency point (i.e., index $i$ ). +- (f) Identify the coherence bandwidth corresponding to a value of [0.5] in autocorrelation function $R(i, n)$ , as shown in Figure 1. +- (g) Steps (a) through (f) may be repeated for different chamber loading configurations, e.g., using absorbers or similar materials, to meet specific coherence bandwidth requirements. + +![Figure 8.3.2.1-1: A line graph showing Correlation (Y-axis, 0.0 to 1.0) versus Center frequency + offset [MHz] (X-axis, 3600 to 3650). Two curves are plotted: a blue curve for '0 absorbers - CBW 2.36 [MHz]' and a red curve for '5 absorbers - CBW 7.72 [MHz]'. Both curves peak at 1.0 correlation at approximately 3625 MHz. A horizontal dotted line at 0.5 correlation intersects the red curve at approximately 3622 MHz and 3628 MHz, and the blue curve at approximately 3624 MHz and 3626 MHz. Vertical dashed lines mark the peak at 3625 MHz and the intersection points at 0.5 correlation for both curves.](6de7dcb072cef2388026fb0f504084b2_img.jpg) + +Figure 8.3.2.1-1: A line graph showing Correlation (Y-axis, 0.0 to 1.0) versus Center frequency + offset [MHz] (X-axis, 3600 to 3650). Two curves are plotted: a blue curve for '0 absorbers - CBW 2.36 [MHz]' and a red curve for '5 absorbers - CBW 7.72 [MHz]'. Both curves peak at 1.0 correlation at approximately 3625 MHz. A horizontal dotted line at 0.5 correlation intersects the red curve at approximately 3622 MHz and 3628 MHz, and the blue curve at approximately 3624 MHz and 3626 MHz. Vertical dashed lines mark the peak at 3625 MHz and the intersection points at 0.5 correlation for both curves. + +**Figure 8.3.2.1-1: The CBW plots based on the correlation function for loading with two different amounts of RF absorbers in the chamber. The threshold of 0.5 is chosen as shown by the dotted lines.** + +### 8.3.3 Chamber spatial uniformity + +The reverberation chamber shall have a working volume large enough to support the number of modes needed for the stated accuracy at the lowest operating frequency. The spatial uniformity test defines this working volume as the valid test zone of the chamber which must be large enough to contain the entire DUT plus any test scenario elements such as phantom fixtures. If DUT size is not known at the time of chamber validation, the minimum test zones described in the reference method [24] of $30\text{cm} \times 30\text{cm}$ or $50\text{cm} \times 36\text{cm}$ can be used in order to enable the same device size applicability. The test positions $T$ describing this working volume need to maintain the same distance requirements as the calibration antennas throughout the procedure, i.e. reference antenna or DUT shall maintain a distance of more than 0.7 wavelengths from chamber loading and more than 0.5 wavelengths from reflective surfaces. + +The value of the uncertainty contribution is determined by repeated calibration measurements for $T$ different positions and orientations of the calibration antenna to determine the statistical variation as a function of frequency, or at least at the frequencies at which the chamber is to be used. It can be assumed that this uncertainty contribution value is normally distributed. + +The $T$ calibration configurations refer to $T$ reference antenna positions. The operator should select these positions depending on whether or not a turntable is present in the chamber. The following instructions and explanation will assist the operator to perform the measurements. + +If there is a turntable in the RC: + +- Assume a cylindrical working volume by selecting two positions on the turntable (the outermost and innermost radial positions of the turntable are recommended). Then select two elevations (the highest and lowest possible are recommended, but far enough away from absorbent and metallic objects, if any). The cylindrical volume would become a toroid with rectangular cross-section if $R_{\min}$ is non-zero due to proximity effects, as described in [22]. The role of the turntable is to stir the source to obtain more independent samples. + +If there is no turntable in the RC: + +- Choose eight positions as corners of an imaginary cubic volume. This means the recommended heights are the highest and lowest possible, but far enough away from absorbing and metallic objects. + +The test steps are as follows. + +- (a) Choose either a cylindrical or a cubic working volume if there is or is not a turntable in the reverberation chamber. As shown by the red dots in Figure 2, use either the 4 corners of the imaginary rectangle that would form the cylindrical working volume or the 8 corners of the cubic working volume as locations for the measurement. For each location, point the antenna at three different angles, preferably at three orthogonal orientations (e.g., 45 degrees, -45 degrees, and horizontal plane). This results in a number of 12 or 24 measurements i.e., $T=12$ or $T=24$ . +- (b) Measure transmission coefficient $S_{21}$ for all 12 or 24 in a complete mode stirring sequence. +- (c) Calculate the power $P_{ref,t}$ for all 12 or 24 positions. In this way, $P_{ref,t}$ is the reference power transfer function for position $t$ of the calibration antenna. +- (d) Calculate the average of power transfer function $P_{ref}$ over the calibration positions, i.e. $T = 12$ or $T = 24$ using the following relation: + +$$P_{ref}^{mean} = \frac{1}{T-1} \sum_{t=1}^T P_{ref,t}$$ + +- (e) Calculate the standard deviation of the power transfer function over $T$ different calibration antenna positions by + +$$\sigma_{P_{ref}} = \sqrt{\frac{1}{T-1} \sum_{t=1}^T (P_{ref,t} - P_{ref}^{mean})^2}$$ + +- (f) Calculate $\sigma_{P_{ref}}$ in dB by + +$$\sigma_{P_{ref}}^{dB} = 10 \log_{10} \left( \frac{P_{ref}^{mean} + \sigma_{P_{ref}}}{P_{ref}^{mean}} \right)$$ + +- (g) Repeat steps (a) through (f) for at least [25] frequency points evenly distributed across the NR FR1 bands. +- (h) Steps (a) through (g) are repeated for various chamber loading configurations, e.g. using absorbers or similar materials, to meet specific coherence bandwidth requirements. + +![Figure 8.3.3-1: Illustration of a working volume with (left) for cylindrical and (right) for cubic volumes. The left diagram shows a cylindrical volume with four red dots at its corners labeled (R_min, Z_max), (R_max, Z_max), (R_min, Z_min), and (R_max, Z_min). The right diagram shows a cubic volume with eight red dots at its corners.](e384b831b3fb26071365a8ad1add04f1_img.jpg) + +Figure 8.3.3-1: Illustration of a working volume with (left) for cylindrical and (right) for cubic volumes. The left diagram shows a cylindrical volume with four red dots at its corners labeled (R\_min, Z\_max), (R\_max, Z\_max), (R\_min, Z\_min), and (R\_max, Z\_min). The right diagram shows a cubic volume with eight red dots at its corners. + +Figure 8.3.3-1: Illustration of a working volume with (left) for cylindrical and (right) for cubic volumes. + +## 8.4 Calibration procedure + +### 8.4.1 S-parameters measurement + +This procedure to measure S-parameters through the reverberation chamber must be performed for each measurement setup in which the loading of the chamber has been changed. Examples of objects that change the loading are phantoms, absorbers, antennas, etc. The calibration procedure must be repeated for each frequency range as defined above. Therefore, it is advantageous if the vector network analyzer can be configured to a frequency sweep covering the defined frequencies, so that all frequencies of interest can be measured with a minimal number of measurements runs. Place all objects into the RC which will be used during TRP or TRS measurements, including a head phantom, hand phantom and fixture for the UE. This ensures that the loss in the chamber, which determines the average power transfer level, is the same during both calibration and test measurements, e.g., TRP and TRS measurements. + +![Diagram of S-parameter measurement setup in a Reverberation Chamber (RC). The setup includes a Stirrer, a Device Under Test (DUT) labeled 'OFF', a Reference Transmitter (REF TX) connected to a Vector Network Analyzer (NA) at port A, and a Receiver (RX) connected to the NA at port B. A blue line represents the transfer function (S21) from the REF TX to the RX. A label 'DUT Control OFF' is shown below the DUT.](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +Diagram of S-parameter measurement setup in a Reverberation Chamber (RC). The setup includes a Stirrer, a Device Under Test (DUT) labeled 'OFF', a Reference Transmitter (REF TX) connected to a Vector Network Analyzer (NA) at port A, and a Receiver (RX) connected to the NA at port B. A blue line represents the transfer function (S21) from the REF TX to the RX. A label 'DUT Control OFF' is shown below the DUT. + +**Figure 8.4.1-1 S-parameter measurement setup in the RC, using a vector network analyzer** + +**Step-1:** Place the calibration antenna in the chamber. The calibration antenna should be mounted on a low-loss dielectric fixture (i.e., loss tangent less than 0.05), to avoid effects from the fixture itself which may affect the UE's radiation efficiency and mismatch factor. The calibration antenna must be placed in the chamber in such a way that it is far enough from any reflective and/or absorbing material such as walls, mode-stirrers, head phantom, or other object. This is to ensure that the environment for the calibration antenna (taken over the complete stirring sequence) resembles a free space environment. "Far enough away" depends on the type of calibration antenna used. For low gain nearly omni-directional antennas like dipoles, it is normally sufficient to ensure that this spacing is larger than 0.5 wavelengths from reflective objects and 0.7 wavelengths from absorbing objects at the lowest operating frequency. More directive calibration antennas should be oriented towards the center of the chamber. The calibration antenna should remain in the chamber during the TRP/TRS measurements. + +**Step-2:** Calibrate the vector network analyzer with a full 2-port calibration in such a way that the vector complex S-parameters between the ports of the fixed measurement antenna and the calibration antenna can be accurately measured. Preferably, the vector network analyzer is set to perform a frequency sweep at each stirrer position. This will enable calibration of several frequency points during the same stirring sequence, thereby reducing calibration time. This will also enable frequency stirring, i.e., averaging the measured power transfer function over a small frequency bandwidth around each measured frequency point (moving frequency window). This will increase accuracy at the expense of (lower) frequency resolution. + +**Step-3:** Place the calibration antenna in the chamber and connect it through the cables. The same procedure should be done for measurement antenna, if necessary. Measure the S-parameters for each fixed measurement antenna. The number of stirrer positions i.e. the number of S-parameter samples at each frequency point, should be chosen in such a way that it is large enough to yield an acceptable statistical contribution to the total measurement uncertainty. To this aim, at least 250 uncorrelated samples shall be used as defined in TR 37.941 clause 7.8.1 [18]. + +### 8.4.2 Calculation of the chamber reference transfer function + +From the S-parameters obtained in the calibration measurement, the chamber reference transfer function for fixed antenna $n$ can be calculated. The chamber reference transfer function for a fixed measurement antenna can be calculated as + +$$P_{ref} = \frac{1}{M} \sum_{m=1}^M \frac{|S_{21,m}|^2}{(1 - R)(1 - |\overline{S_{22,ref}}|^2)} \cdot \frac{1}{e_{ref}}$$ + +Where $M$ is total number of stirrer positions, $m$ is S-parameter sample number i.e., sampled at stirrer position $m$ , the operator $|\cdot|$ denotes the absolute value, the operator $\overline{\cdot}$ acting on parameter $S_{22,ref}$ denotes the average of complex parameters $S_{22,ref}$ over mode stirring sequence, $S_{22,ref}$ is the reflection coefficient for calibration antenna, $S_{21,m}$ is sample number $m$ of the transfer function for the measurement antenna, $e_{ref}$ is the radiation efficiency of the calibration antenna, and $R$ is the reflection coefficient for the fixed antenna and can be calculated as + +$$R = \left| \frac{1}{M} \sum_{m=1}^M S_{11,m} \right|^2 = |\overline{S_{11}}|^2$$ + +Where $S_{11,m}$ is sample number $m$ of the reflection coefficient for a fixed antenna and $\overline{S_{11}}$ is the average of reflection coefficient. + +Note that the radiation efficiency of the fixed antenna is not corrected for, because it will be the same both during calibration and measurements. Therefore, the fixed antenna's radiation efficiency will not affect the final results. + +## 8.5 TRP Test procedure + +### 8.5.1 TRP for SA and EN-DC + +#### 8.5.1.1 Test conditions + +The TRP of the DUT is measured by sampling the S-parameters through a mode-stirring sequence and using these parameters to estimate the average power measured by any fixed measurement antenna. This data is used to determine the TRP values measured in the reverberation chamber. The measurement is performed with a step-mode stirring sequence and a frequency stirrer can be used. + +#### 8.5.1.2 UE configurations + +For devices containing multiple Tx antennas, the Tx Antenna Switching (TAS) function should be OFF, and the TRP should be measured for each Tx antenna individually. The antenna with better TRP is identified as the primary antenna, and the corresponding TRP result will be used to determine the pass/fail compliance. Otherwise, the primary antenna should be selected based on manufacturer declaration. + +For Standalone, the NR System Simulator (SS) and DUT shall be configured per TS 38.521-1 [5], section 6.2.1 (UE maximum output power) using the default settings specified in TS 38.521-1 [5] and TS 38.508-1 [7] as applicable. The measurement should be carried out based on the detailed test parameters for each band, as defined in Clause 4.3. + +For EN-DC, the SS and DUT shall be configured per TS 38.521-3 [6], Section 6.2B.1 (UE Maximum Output Power for EN-DC) using the default settings specified in TS 38.521-3 [6] and TS 38.508-1 [7] as applicable. The measurement should be carried out based on the detailed test parameters for each band, as defined in Clause 4.3. The UL output power of LTE carrier should be set as a constant power of 10dBm, while measuring NR at maximum output power, i.e., with fixed p-MaxEUTRA-r15=10 dBm, and p-NR-FR1 not configured. + +#### 8.5.1.3 Test procedure + +For TRP measurement, the evaluations shall be performed at maximum transmit power. The measurement procedure includes the following steps: + +1. Place the DUT inside the test zone. +2. Connect the DUT through the cables/chamber to the instrument and ensure the DUT is transmitting at its maximum power. +3. Measure the power at each measurement point, and calculate the TRP by averaging over the sampling sequence. At least [150] uncorrelated measurement samples shall be used. The loss of the entire transmission path must be compensated. + +The TRP value is calculated using the TRP equation in the definition outlined in 5.1.2. + +## 8.6 TRS Test procedure + +### 8.6.1 TRS for SA and EN-DC + +#### 8.6.1.1 Test conditions + +The TRS of the DUT is based on searching for the lowest power received by UE for a discrete number of field combinations in the chamber. The power received by the UE at each discrete field combination that provides a BER (or BLER) which is better than the specified target BER/BLER level shall be averaged with other such measurements using different field combinations. The TRS of the DUT is estimated by measuring the transfer function for each fixed measurement antenna, which gives the BER threshold. + +#### 8.6.1.2 UE configurations + +For Standalone, the NR System Simulator (SS) and DUT shall be configured per section 7.3.2 (Reference sensitivity power level) of TS 38.521-1 [5] using the defaults specified in TS 38.521-1 [5] and TS 38.508-1 [7] as applicable. The measurement should be carried out based on the detailed test parameters for each band, as defined in Clause 4. + +For EN-DC, the EN-DC SS and DUT shall be configured per section 7.3B.2 (Reference Sensitivity for EN-DC) of TS 38.521-3 [6], using the defaults specified in TS 38.521-3 [6] and TS 38.508-1 [7], as applicable. The measurement should be carried out based on the detailed test parameters for each band, as defined in Clause 4. The UL power configuration for LTE and NR is 50%-50% power splitting, i.e., + +- For PC3, p-MaxEUTRA-r15=20 dBm, and p-NR-FR1= 20dBm; +- For PC2, p-MaxEUTRA-r15=23 dBm, and p-NR-FR1= 23dBm. + +#### 8.6.1.3 Test procedure + +For TRS measurement, the evaluations shall be performed at maximum transmit power. The measurement procedure includes the following steps: + +- 1) Place the DUT inside the test zone. +- 2) Connect the DUT through the cables/chamber to the instrument and ensure the DUT is transmitting at its maximum power. +- 3) Follow steps 1 through 4 in section 7.3.2.4.2 of TS 38.521-1 [5], with the following exception: determine each EIS, i.e., by adjusting the downlink signal level until the minimum power level at which the throughput exceeds or equal to 95% of the maximum throughput of the specified RMC, at each sampling point. The downlink power step size shall be no more than 0.5 dB when the RF power level is near the NR sensitivity level. At least [100] uncorrelated measurement sampling points shall be used. + +The TRS value is calculated using the equation outlined in 5.2.2. + +## 8.7 Test Volume + +The reverberation chamber shall have a volume large enough to support the number of modes needed for the stated accuracy at the lowest operating frequency. If the UE/MS is moved around in the chamber during the measurement, the volume of the reverberation chamber can be reduced. In addition to the physical chamber size considerations, the test volume of the chamber must be large enough to place a reference antenna/test object at a minimum distance of one-half wavelength, i.e., $\lambda/2$ from the chamber walls, mode stirrers, and other electromagnetic reflective objects within the chamber, and 0.7 wavelengths from absorbing objects at the lowest test frequency. + +# 9 Testing time reduction methodologies + +## 9.1 General + + + +## 9.2 Measurement grids for Anechoic Chamber method + +The measurement grid simulations relied on representative antenna patterns for smartphone UEs. + +For below 3 GHz, the device simulated is a flip-phone with dual-band GSM antenna and a separate Bluetooth antenna and is shown in Figure 9.2-1 in the BHR configuration. The simulation model for the phone includes many actual components, e.g., LCD, battery, buttons, speaker, vibration motor, shields, hinge, etc. It should be noted that the coordinate system in this simulation is not aligned with the coordinate systems for smartphone UEs in free-space and/or BH configurations, specifically Clause 6. However, given the nature of the simulation analyses, this misalignment is irrelevant. + +![Figure 9.2-1: Three 3D renderings of a human head model with a flip phone attached. The top-left image shows the phone with a red arrow pointing to the 'GSM Antenna'. The top-right image shows the phone with a red arrow pointing to the 'Bluetooth Antenna'. The bottom image shows the phone from a different angle, with a small coordinate system icon visible at the bottom left of the head model.](0a90113d6c8989e8b3c89c5cf9f926d7_img.jpg) + +The image consists of three separate 3D renderings of a human head model, which is a light beige color with a grid-like wireframe pattern. In the top-left rendering, a blue and yellow flip phone is attached to the side of the head, and a red arrow points to its internal antenna, labeled 'GSM Antenna'. In the top-right rendering, the same phone is shown from a slightly different angle, with a red arrow pointing to its internal antenna, labeled 'Bluetooth Antenna'. In the bottom rendering, the phone is shown from a rear-side perspective, and a small 3D coordinate system icon (with red, green, and blue axes) is visible at the bottom left of the head model. + +Figure 9.2-1: Three 3D renderings of a human head model with a flip phone attached. The top-left image shows the phone with a red arrow pointing to the 'GSM Antenna'. The top-right image shows the phone with a red arrow pointing to the 'Bluetooth Antenna'. The bottom image shows the phone from a different angle, with a small coordinate system icon visible at the bottom left of the head model. + +Figure 9.2-1: Illustration of the antennas integrated inside the DUT mounted (GSM antenna on the top left, Bluetooth antenna on the top right, coordinate system bottom). + +The simulations for the free-space configuration use the same coordinate system as shown in Figure 9.2-1 with the phantom completely removed from the simulation setup. + +The normalized BHR patterns are shown in Figure 9.2-2 through 9.2-4 for the GSM antenna at 824 MHz and 1800 MHz and for the Bluetooth antenna at 2450 MHz, respectively. Each pattern is normalized to its respective peak, i.e., the pattern is shown with a 15dB dynamic range with a peak value of 0dB. + +![Two 3D surface plots showing normalized BHR patterns for antennas. The left plot shows a pattern with a peak value of 0 dB, indicated by a color bar on the right ranging from -15 dB to 0 dB. The right plot shows a similar pattern with a peak value of 0 dB, also indicated by a color bar on the right ranging from -15 dB to 0 dB. Both plots include a 3D coordinate system with x, y, and z axes.](eb903413d070b64f45cd763804ba443f_img.jpg) + +The figure displays two 3D surface plots representing normalized BHR patterns. Each plot is accompanied by a vertical color bar on its right side, indicating a dynamic range from -15 dB (blue) to 0 dB (red). The left plot shows a pattern with a primary lobe oriented along the z-axis, while the right plot shows a more complex pattern with multiple lobes. Both plots include a 3D coordinate system with x, y, and z axes. + +Two 3D surface plots showing normalized BHR patterns for antennas. The left plot shows a pattern with a peak value of 0 dB, indicated by a color bar on the right ranging from -15 dB to 0 dB. The right plot shows a similar pattern with a peak value of 0 dB, also indicated by a color bar on the right ranging from -15 dB to 0 dB. Both plots include a 3D coordinate system with x, y, and z axes. + +**Figure 9.2-2: Normalized antenna patterns for GSM antenna at 824 MHz in BHR configuration. TRP of normalized pattern of -3.5 dB.** + +![Normalized antenna patterns for GSM antenna at 824 MHz in BHR configuration. The figure shows two 3D surface plots of the antenna radiation pattern. The left plot shows the pattern from a side view, and the right plot shows it from a top-down perspective. Both plots use a color scale from -15 dB (blue) to 0 dB (red). The pattern is roughly hemispherical, with a slight dip in the center of the flat face.](3ad4d1734817fe2ac05fe8d4da4f68e8_img.jpg) + +Normalized antenna patterns for GSM antenna at 824 MHz in BHR configuration. The figure shows two 3D surface plots of the antenna radiation pattern. The left plot shows the pattern from a side view, and the right plot shows it from a top-down perspective. Both plots use a color scale from -15 dB (blue) to 0 dB (red). The pattern is roughly hemispherical, with a slight dip in the center of the flat face. + +**Figure 9.2-3: Normalized antenna patterns for GSM antenna at 1800 MHz in BHR configuration. TRP of normalized pattern of -4.2 dB.** + +![Normalized antenna patterns for GSM antenna at 1800 MHz in BHR configuration. The figure shows two 3D surface plots of the antenna radiation pattern. The left plot shows the pattern from a side view, and the right plot shows it from a top-down perspective. Both plots use a color scale from -15 dB (blue) to 0 dB (red). The pattern is more directional than at 824 MHz, with a deeper central dip.](1559db1c389771b44f7dc11d48b06079_img.jpg) + +Normalized antenna patterns for GSM antenna at 1800 MHz in BHR configuration. The figure shows two 3D surface plots of the antenna radiation pattern. The left plot shows the pattern from a side view, and the right plot shows it from a top-down perspective. Both plots use a color scale from -15 dB (blue) to 0 dB (red). The pattern is more directional than at 824 MHz, with a deeper central dip. + +**Figure 9.2-4: Normalized antenna patterns for Bluetooth antenna at 2450 MHz in BHR configuration. TRP of normalized pattern of -6.5 dB.** + +The normalized FS patterns are shown in Figure 9.2-5 through 9.2-7 for the GSM antenna at 824 MHz and 1800 MHz and for the Bluetooth antenna at 2450 MHz, respectively. + +![Normalized antenna patterns for GSM antenna at 824 MHz in FS configuration. The figure shows two 3D surface plots of the antenna radiation pattern. The left plot shows a side view with the x, y, and z axes. The right plot shows a top-down view. Both plots have a color scale on the right ranging from 0 (red) to -15 (blue). The pattern is roughly hemispherical, with a slight dip in the center of the top view.](505116873ad67b610dfceb37016d04a3_img.jpg) + +Normalized antenna patterns for GSM antenna at 824 MHz in FS configuration. The figure shows two 3D surface plots of the antenna radiation pattern. The left plot shows a side view with the x, y, and z axes. The right plot shows a top-down view. Both plots have a color scale on the right ranging from 0 (red) to -15 (blue). The pattern is roughly hemispherical, with a slight dip in the center of the top view. + +**Figure 9.2-5: Normalized antenna patterns for GSM antenna at 824 MHz in FS configuration. TRP of normalized pattern of -3.1 dB.** + +![Normalized antenna patterns for GSM antenna at 1800 MHz in FS configuration. The figure shows two 3D surface plots of the antenna radiation pattern. The left plot shows a side view with the x, y, and z axes. The right plot shows a top-down view. Both plots have a color scale on the right ranging from 0 (red) to -15 (blue). The pattern is more complex than at 824 MHz, with multiple lobes and a central dip in the top view.](258c1507ae7e731f704a016f660cd469_img.jpg) + +Normalized antenna patterns for GSM antenna at 1800 MHz in FS configuration. The figure shows two 3D surface plots of the antenna radiation pattern. The left plot shows a side view with the x, y, and z axes. The right plot shows a top-down view. Both plots have a color scale on the right ranging from 0 (red) to -15 (blue). The pattern is more complex than at 824 MHz, with multiple lobes and a central dip in the top view. + +**Figure 9.2-6: Normalized antenna patterns for GSM antenna at 1800 MHz in FS configuration. TRP of normalized pattern of -4.7 dB.** + +![Normalized antenna patterns for Bluetooth antenna at 2450 MHz in FS configuration. The figure shows two 3D surface plots of the antenna radiation pattern. The left plot shows a side view with the x, y, and z axes. The right plot shows a top-down view. Both plots have a color scale on the right ranging from 0 (red) to -15 (blue). The pattern is roughly hemispherical, similar to the 824 MHz pattern but with a more pronounced central dip in the top view.](6d06e66b7a838f8c809884aeee597a5e_img.jpg) + +Normalized antenna patterns for Bluetooth antenna at 2450 MHz in FS configuration. The figure shows two 3D surface plots of the antenna radiation pattern. The left plot shows a side view with the x, y, and z axes. The right plot shows a top-down view. Both plots have a color scale on the right ranging from 0 (red) to -15 (blue). The pattern is roughly hemispherical, similar to the 824 MHz pattern but with a more pronounced central dip in the top view. + +**Figure 9.2-7: Normalized antenna patterns for Bluetooth antenna at 2450 MHz in FS configuration. TRP of normalized pattern of -4.3 dB.** + +For beyond 3 GHz, two sets of simulation results were utilized. The first set of results were for a smartphone UE in the FS and the BHR condition, illustrated in Figure 9.2-8. + +![3D simulation model of a human head with an antenna.](de5063b406eb787334c453b07b7dcc52_img.jpg) + +A 3D simulation model of a human head, rendered in yellow, with a black antenna array wrapped around its forehead. A coordinate system with x, y, and z axes is visible at the bottom right of the model. + +3D simulation model of a human head with an antenna. + +**Figure 9.2-8: Illustration of the simulation model for n78 patterns** + +The 3D antenna patterns in Figure 9.2-9 using a 30 dB dynamic range. + +![Simulated antenna patterns for n78 (3.5 GHz).](9455ca65b9fc488df790769b0122628e_img.jpg) + +Two 3D surface plots representing simulated antenna patterns for n78 at 3.5 GHz. The left plot, labeled 'free space (FS)', shows a relatively smooth, rounded pattern with a color scale from -25 (blue) to 0 (red). The right plot, labeled 'beside head right (BHR)', shows a more complex pattern with a prominent peak and a color scale from -20 (blue) to 5 (red). Both plots include x, y, and z axes. + +Simulated antenna patterns for n78 (3.5 GHz). + +**Figure 9.2-9: Simulated antenna patterns for n78 (3.5 GHz). Left: free space (FS), right: beside head right (BHR)** + +The second set of patterns are from a smartphone prototype with the antenna placed in the corner of a device with metallic ground plane. The model is simplified and contains an LCD (glass), ground plane (PEC), camera block (PEC), opposing solid block and battery (PEC) and a plastic housing. Dimensions of the device are 64 mm x 132 mm x 8 mm. The antenna element is approximately 3 mm from the ground and has reasonable matching between 4-6 GHz. The peak gain is between 4.6 and 5.6 dBi, but pattern shape varies between the various frequencies. + +![3D simulation model of a smartphone prototype.](9d71890acd754a1325e9415e44a7dacb_img.jpg) + +A 3D simulation model of a smartphone prototype, shown as a wireframe structure. The model includes a rectangular ground plane, a camera block, and other internal components. A coordinate system with x, y, and z axes is visible at the top left of the model. + +3D simulation model of a smartphone prototype. + +**Figure 9.2-10: Illustration of the simulation model for 4-6 GHz** + +The corresponding antenna patterns are illustrated in Figure 9.2-11. + +![Figure 9.2-11: Simulated antenna patterns for 4 GHz, 4.5 GHz, 5 GHz, 5.5 GHz, and 6 GHz. The figure consists of five 3D surface plots arranged in a 2x2 grid with one plot centered below. Each plot shows a 3D surface representing the antenna radiation pattern, with a color scale from -25 dB (blue) to 5 dB (red). The plots are labeled with x, y, and z axes. The patterns show a main lobe and side lobes, with the main lobe becoming more directional as the frequency increases from 4 GHz to 6 GHz.](b7251436a2a3c0d1c00c3e935df2a8f5_img.jpg) + +Figure 9.2-11 displays five simulated antenna patterns for different frequencies: 4 GHz (top left), 4.5 GHz (top right), 5 GHz (middle left), 5.5 GHz (middle right), and 6 GHz (bottom left). Each pattern is shown as a 3D surface plot with a color scale ranging from -25 dB (blue) to 5 dB (red). The plots are labeled with x, y, and z axes. The patterns show a main lobe and side lobes, with the main lobe becoming more directional as the frequency increases from 4 GHz to 6 GHz. + +Figure 9.2-11: Simulated antenna patterns for 4 GHz, 4.5 GHz, 5 GHz, 5.5 GHz, and 6 GHz. The figure consists of five 3D surface plots arranged in a 2x2 grid with one plot centered below. Each plot shows a 3D surface representing the antenna radiation pattern, with a color scale from -25 dB (blue) to 5 dB (red). The plots are labeled with x, y, and z axes. The patterns show a main lobe and side lobes, with the main lobe becoming more directional as the frequency increases from 4 GHz to 6 GHz. + +**Figure 9.2-11 Simulated antenna patterns for 4 GHz (top left), 4.5 GHz (top right), 5 GHz (middle left), 5.5 GHz (middle right), 6 GHz (bottom left).** + +The analyses in this contribution are closely aligned with those presented in [19]. The steps followed for the analyses are outlined and visualized in Table 9.2-1. + +For the TRP analyses, a total of 10,000 rotation angles were applied and analysed. In order to apply uniform rotation vectors to the antenna pattern, the rotation angle around the y axis needed to be scaled. The rotations around the z axis + +were therefore handled in a completely random fashion, e.g., $360 * \text{rand}(10000, 1)$ , while the distribution of rotations around the z axis needed to be scaled by $\sin(\theta)$ . The histograms of these two rotation angles are illustrated in Figure 9.2-12, while the uniform rotation vectors are illustrated in 3D in Figure 9.2-13. + +![Figure 9.2-12: Two histograms showing the distribution of random rotation angles. The top histogram shows 'Rotation around z [deg]' from 0 to 400, with a relatively flat distribution around 200. The bottom histogram shows 'Rotation around y [deg]' from -100 to 100, with a distribution peaking at 0 degrees.](b15e3860e0c96ed16ce77f032da6f107_img.jpg) + +The figure consists of two histograms. The top histogram is titled 'Histogram' on the y-axis and 'Rotation around z [deg]' on the x-axis. The x-axis ranges from 0 to 400 with major ticks every 50 units. The y-axis ranges from 0 to 200 with major ticks every 50 units. The histogram shows a distribution of rotation angles around the z-axis, with bars of varying heights, mostly between 150 and 200. The bottom histogram is also titled 'Histogram' on the y-axis and 'Rotation around y [deg]' on the x-axis. The x-axis ranges from -100 to 100 with major ticks every 20 units. The y-axis ranges from 0 to 300 with major ticks every 100 units. This histogram shows a distribution of rotation angles around the y-axis, with a clear peak at 0 degrees, reaching a frequency of about 300. + +Figure 9.2-12: Two histograms showing the distribution of random rotation angles. The top histogram shows 'Rotation around z [deg]' from 0 to 400, with a relatively flat distribution around 200. The bottom histogram shows 'Rotation around y [deg]' from -100 to 100, with a distribution peaking at 0 degrees. + +**Figure 9.2-12: Histogram of random distribution around the z and y axes.** + +![Figure 9.2-13: A 3D scatter plot illustrating 10,000 random rotation vectors. The vectors are represented by red dots distributed uniformly on a sphere. The axes are labeled x (red), y (green), and z (blue).](6f1efa91fb9b476380af7a35db4f14bf_img.jpg) + +The figure shows a 3D scatter plot of 10,000 random rotation vectors. The vectors are represented by red dots that are uniformly distributed on the surface of a sphere. A coordinate system is overlaid on the sphere, with the z-axis represented by a blue arrow pointing upwards, the y-axis by a green arrow pointing diagonally upwards and to the right, and the x-axis by a red arrow pointing diagonally downwards and to the right. The sphere itself is a light gray background. + +Figure 9.2-13: A 3D scatter plot illustrating 10,000 random rotation vectors. The vectors are represented by red dots distributed uniformly on a sphere. The axes are labeled x (red), y (green), and z (blue). + +**Figure 9.2-13: Illustration of 10k random rotation vectors.** + +**Table 9.2-1: Overview of the various steps for the TRP measurement grid analyses including overview for sample constant-step size measurement grids and pattern.** + +| Steps | $\Delta\theta=\Delta\phi=1^\circ$ (Reference) | $\Delta\theta=\Delta\phi=15^\circ$ | $\Delta\theta=\Delta\phi=45^\circ$ | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Step 1: Import the reference pattern with very fine discretization of $\Delta\theta=\Delta\phi=1^\circ$ . | 3D surface plot of the reference TRP pattern with a color scale from -15 to 0. The plot shows a complex, multi-lobed shape with axes labeled x, y, and z. | | | +| Step 2: Determine the reference TRP based on the fine grid pattern | | | | +| Step 3: Apply 10k random rotation angles to the y axis followed by the z axis to the fine pattern |

Plot of the discretized pattern (without rotation)

3D surface plot of the discretized pattern for the reference grid (1 degree step size). It appears smooth and detailed with a color bar from -15 to 0. |

Plot of the discretized pattern (without rotation)

3D surface plot of the discretized pattern for the 15 degree step size grid. The surface is visibly faceted into a grid of quadrilaterals. |

Plot of the discretized pattern (without rotation)

3D surface plot of the discretized pattern for the 45 degree step size grid. The surface is highly simplified into large triangular and quadrilateral facets. | +| Step 4: Discretize the rotated fine pattern to the coarse grid with $\Delta\theta, \Delta\phi$ for the constant-step size grids or N grid points for the constant-density grid | | | | + +Error! No text of specified style in document. + +Error! No text of specified style in document. + +| | | | | +|--------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Step 5: Calculate the TRP based on the selected quadrature |

Constant Step Size Grid with \Delta\theta=\Delta\phi=1\text{deg} and 64442 unique points
Pattern File: BHR_pattern1800_GSM

Histogram of TRP_CC for 1 degree grid

This histogram shows a very narrow distribution of TRPCC values, with a single prominent peak at approximately -4. The y-axis is labeled 'Histogram' and has a scale factor of \times 10^4. The x-axis is labeled 'TRPCC (normalized by TRP with fine grid)' and has a scale factor of \times 10^{-4}.

|

Constant Step Size Grid with \Delta\theta=\Delta\phi=15\text{deg} and 266 unique points
Pattern File: BHR_pattern1800_GSM

Histogram of TRP_CC for 15 degree grid

This histogram shows a bell-shaped distribution of TRPCC values centered around -4. The y-axis is labeled 'Histogram' and has a scale factor of \times 10^{-4}. The x-axis is labeled 'TRPCC (normalized by TRP with fine grid)' and has a scale factor of \times 10^{-4}.

|

Constant Step Size Grid with \Delta\theta=\Delta\phi=45\text{deg} and 26 unique points
Pattern File: BHR_pattern1800_GSM

Histogram of TRP_CC for 45 degree grid

This histogram shows a wide distribution of TRPCC values ranging from -0.15 to 0.2, with a peak around -0.05. The y-axis is labeled 'Histogram'. The x-axis is labeled 'TRPCC (normalized by TRP with fine grid)' and has a scale factor of \times 10^{-4}.

| +| Step 6: Calculate the standard deviation of the 10k different TRPs and the mean error from the reference TRP | | | | + +Various constant-step size grids were analysed for two TRP quadratures, i.e., $\sin(\theta)$ , the legacy quadrature, and the Clenshaw-Curtis approach. Both are currently permissible for TRP/TRS testing. The calculated standard deviations and mean errors for both quadratures are tabulated in Table 9.2-2 for below 3 GHz and in Table 9.2-3 for beyond 3 GHz. The last column includes a background colour with the following formatting + +- No coloured background means the std. deviation is less than 0.05dB, i.e., that this grid could be used without any additional MU impact +- yellow means the std. deviation is between 0.05dB and 0.25dB, i.e., this grid could be used with a small impact in MU +- red means the std. deviation is beyond 0.25dB, i.e., these grids should not be considered any further. + +The mean error column includes similar formatting where grids that yield an absolute value mean error between 0.05 and 0.25 dB are highlighted in yellow. These measurement grids might require a new MU element, or the mean error is included in the TIS calculation somehow. Grids with a red highlight have an absolute value of the mean error of greater than 0.25 dB and should be avoided. + +Clearly, the Clenshaw-Curtis quadrature has lower uncertainties compared to the $\sin(\theta)$ quadrature, especially for very coarse grids. + +**Table 9.2-2: Standard deviations and mean errors of TRPs after applying 10k rotations for various constant-step size measurement grids for below 3 GHz** + +| Constant Step-Size Grid | | | Standard Deviation [dB] | Mean Error [dB] | +|------------------------------------|--------------------|-----------------|----------------------------------|----------------------------------| +| $\Delta\theta=\Delta\phi [^\circ]$ | # of unique points | Quadrature | Aggregate (pooling all Patterns) | Aggregate (pooling all Patterns) | +| 1 | 64442 | Clenshaw-Curtis | 0.00 | 0.00 | +| 5 | 2522 | | 0.00 | 0.00 | +| 10 | 614 | | 0.00 | 0.00 | +| 15 | 266 | | 0.00 | 0.00 | +| 30 | 62 | | 0.01 | 0.00 | +| 45 | 26 | | 0.05 | -0.01 | +| 60 | 14 | | 0.11 | -0.01 | +| 1 | 64442 | $\sin(\theta)$ | 0.00 | 0.00 | +| 5 | 2522 | | 0.00 | 0.00 | +| 10 | 614 | | 0.00 | -0.01 | +| 15 | 266 | | 0.01 | -0.02 | +| 30 | 62 | | 0.04 | -0.09 | +| 45 | 26 | | 0.11 | -0.21 | +| 60 | 14 | | 0.26 | -0.38 | + +**Table 9.2-3: Standard deviations and mean errors of TRPs after applying 10k rotations for various constant-step size measurement grids for beyond 3 GHz** + +| Constant Step-Size Grid | | | Standard Deviation [dB] | Mean Error [dB] | +|----------------------------------------|--------------------|-----------------|----------------------------------|----------------------------------| +| $\Delta\theta=\Delta\phi$ [ $^\circ$ ] | # of unique points | Quadrature | Aggregate (pooling all Patterns) | Aggregate (pooling all Patterns) | +| 1 | 64442 | Clenshaw-Curtis | 0.00 | 0.00 | +| 5 | 2522 | | 0.00 | 0.00 | +| 15 | 266 | | 0.00 | 0.00 | +| 30 | 62 | | 0.11 | -0.01 | +| 45 | 26 | | 0.22 | -0.09 | +| 60 | 14 | | 0.34 | 0.05 | +| 1 | 64442 | sin(theta) | 0.00 | 0.00 | +| 5 | 2522 | | 0.00 | 0.00 | +| 15 | 266 | | 0.01 | -0.03 | +| 30 | 62 | | 0.11 | -0.11 | +| 45 | 26 | | 0.27 | -0.33 | +| 60 | 14 | | 0.43 | -0.37 | + +Another important set of analyses was performed for the constant-step size grids beyond 3 GHz where the EIRP at the pole of $\theta = 180^\circ$ was either set to a very small number/null (due to a potential blockage due to the positioner/pedestal), extrapolated from the second to last cut (mean of all EIRPs), or extrapolated from two neighbouring points $15^\circ$ off the pole, i.e., EIRP( $\theta=165^\circ, \phi=0^\circ$ ) and EIRP( $\theta=165^\circ, \phi=180^\circ$ ). Those results for the standard deviations and the mean errors summarized in Table 9.2-4 and 9.2-5, respectively. From the standard deviations in 9.2-4, it can be observed that the impact of how the EIRP at $\theta = 180^\circ$ is treated has little effect for measurement grids as coarse as 26 grid points while a small increase in standard uncertainty can be seen for the coarsest grid with 14 points regardless of whether the final grid point does not yield a reasonable measurement or whether it is extrapolated from the second to last cut. When the pole point is not measured and considered to be a deep null, unacceptable mean errors are observed for very coarse grids. The mean errors in Table 9.2-5 show that the averaging of the pole from the 2nd to last cut or the extrapolation of the two point $15^\circ$ off the pole yield very good agreement with the previous simulations that assume the grid point at the pole can be measured without any obstruction/blockage. Those two approaches are illustrated in Figure 9.2-14 for a measurement grid using the $\Delta\theta=\Delta\phi=45^\circ$ grid where the grid point at $\theta=180^\circ$ (shown in blue) is extrapolated either using 8 existing measurements at $\theta=135^\circ$ (shown in red) on the left or with two new grid points at $\theta=165^\circ$ (shown in red) on the right. The advantage of the more extrapolation approach using two new grid points at $\theta=165^\circ$ becomes more evident when considering the coarsest measurement grid presented here, i.e., $\Delta\theta=\Delta\phi=60^\circ$ , which could be considered for IoT or RedCap devices in the future. The extrapolation approach of the grid point at $\theta=180^\circ$ that relies on either on the existing 8 measurements at $\theta=135^\circ$ or the two close neighbours at $\theta=165^\circ$ is considered necessary for above 3 GHz TRP measurement grids for the most accurate extrapolation and lowest MUs. + +![Figure 9.2-14: Illustration of extrapolation approaches for the Δθ=Δφ=45° grid. The figure shows two spheres representing measurement grids. The left sphere shows a grid with black dots for measured points and red dots for extrapolated points. The right sphere shows a similar grid but with a different extrapolation approach, indicated by a blue dot at the bottom pole. Both spheres have coordinate axes x (red), y (green), and z (blue).](07f537f57749b75157f742525e6a8dbc_img.jpg) + +Figure 9.2-14: Illustration of extrapolation approaches for the Δθ=Δφ=45° grid. The figure shows two spheres representing measurement grids. The left sphere shows a grid with black dots for measured points and red dots for extrapolated points. The right sphere shows a similar grid but with a different extrapolation approach, indicated by a blue dot at the bottom pole. Both spheres have coordinate axes x (red), y (green), and z (blue). + +Figure 9.2-14: Illustration of extrapolation approaches for the $\Delta\theta=\Delta\phi=45^\circ$ grid + +Table 9.2-4: Standard deviations for various constant-step size measurement grids and different extrapolation approaches for beyond 3 GHz; results for Clenshaw-Curtis quadrature only + +| Constant Step-Size Grid | | Standard Deviation [dB] | | | | +|------------------------------------|--------------------|----------------------------------|------------------------------------|-------------------------------------------|---------------------------------------------------------------| +| $\Delta\theta=\Delta\phi [^\circ]$ | # of unique points | Aggregate (pooling all Patterns) | Aggregate (pooling all Patterns) | Aggregate (pooling all Patterns) | Aggregate (pooling all Patterns) | +| | | $180^\circ$ is measured | $180^\circ$ is not measured | $180^\circ$ is averaged from previous cut | $180^\circ$ is extrapolated from two $165^\circ$ measurements | +| 1 | 64442 | 0.00 | 0.00 | 0.00 | 0.00 | +| 5 | 2522 | 0.00 | 0.00 | 0.00 | 0.00 | +| 15 | 266 | 0.00 | 0.01 | 0.00 | 0.00 | +| 30 | 62 | 0.11 | 0.12 | 0.11 | 0.11 | +| 45 | 26 | 0.22 | 0.27 | 0.25 | 0.23 | +| 60 | 14 | 0.33 | 0.41 | 0.38 | 0.33 | + +Table 9.2-5: Mean errors for various constant-step size measurement grids and different extrapolation approaches for beyond 3 GHz; results for Clenshaw-Curtis quadrature only + +| Constant Step-Size Grid | | Mean Error (TRP-TRP ref ) [dB] | | | | +|------------------------------------|--------------------|-------------------------------------------|------------------------------------|-------------------------------------------|---------------------------------------------------------------| +| $\Delta\theta=\Delta\phi [^\circ]$ | # of unique points | Aggregate (pooling all Patterns) | Aggregate (pooling all Patterns) | Aggregate (pooling all Patterns) | Aggregate (pooling all Patterns) | +| | | $180^\circ$ is measured | $180^\circ$ is not measured | $180^\circ$ is averaged from previous cut | $180^\circ$ is extrapolated from two $165^\circ$ measurements | +| 1 | 64442 | 0.00 | 0.00 | 0.00 | 0.00 | +| 5 | 2522 | 0.00 | 0.00 | 0.00 | 0.00 | +| 15 | 266 | 0.00 | -0.01 | 0.00 | 0.00 | +| 30 | 62 | -0.01 | -0.06 | -0.01 | -0.01 | + +| | | | | | | +|----|----|-------|-------|-------|-------| +| 45 | 26 | -0.09 | -0.21 | -0.08 | -0.08 | +| 60 | 14 | 0.05 | -0.15 | 0.08 | 0.07 | + +The treatment of mean errors in the MU budget is FFS and will be finalized in RAN5, e.g., whether to consider these mean errors as a systematic uncertainty as it is currently done for FR2, i.e., the ‘Systematic error due to TRP calculation/quadrature’ MU element, specifically B.2.1.24 of [20]. + +## 9.3 Other solutions + + + +# Annex A: UE coordinate system + +## A.1 Reference coordinate system + +This annex defines the measurement coordinate system for NR FR1 TRP and TRS measurements. The reference coordinate system, as defined in [9] is provided in Figure A.1-1 below while A.1-2 shows the DUT in the default alignment for Free Space. + +![Figure A.1-1: Reference coordinate system. A 3D diagram showing a spherical coordinate system with axes +x, +y, and +Z. The +Z axis is vertical, the +y axis is horizontal to the right, and the +x axis points diagonally down and to the left. A sphere is centered at the origin. A vector is drawn from the origin to a point on the sphere's surface. The angle between the +Z axis and this vector is labeled theta (θ). The angle between the +y axis and the projection of the vector onto the xy-plane is labeled phi (φ). Two dashed ellipses represent the polarization planes: the phi-polarization plane (vertical) and the theta-polarization plane (horizontal). A label '(to Antenna)' is placed along the +Z axis.](475caf31ae90b878f12d651b689cc9d1_img.jpg) + +Figure A.1-1: Reference coordinate system. A 3D diagram showing a spherical coordinate system with axes +x, +y, and +Z. The +Z axis is vertical, the +y axis is horizontal to the right, and the +x axis points diagonally down and to the left. A sphere is centered at the origin. A vector is drawn from the origin to a point on the sphere's surface. The angle between the +Z axis and this vector is labeled theta (θ). The angle between the +y axis and the projection of the vector onto the xy-plane is labeled phi (φ). Two dashed ellipses represent the polarization planes: the phi-polarization plane (vertical) and the theta-polarization plane (horizontal). A label '(to Antenna)' is placed along the +Z axis. + +Figure A.1-1: Reference coordinate system + +![Diagram showing the default alignment of a Device Under Test (DUT) to a coordinate system. The phone is oriented vertically. The +Z axis points upwards from the top of the phone, labeled 'Top of phone'. The +Y axis points horizontally to the right from the side of the phone, labeled 'Side of phone'. The +X axis points diagonally downwards and to the left from the front of the phone, labeled 'Screen looks this way'.](10953d657a5f47fdc829a800419dd370_img.jpg) + +The diagram illustrates a mobile phone positioned vertically. A coordinate system is overlaid on it. The Z-axis is vertical, pointing upwards from the top of the phone, with an arrow labeled '+Z' and the text 'Top of phone'. The Y-axis is horizontal, pointing to the right from the right side of the phone, with an arrow labeled '+Y' and the text 'Side of phone'. The X-axis is diagonal, pointing towards the bottom-left from the front of the phone, with an arrow labeled '+X' and the text 'Screen looks this way'. + +Diagram showing the default alignment of a Device Under Test (DUT) to a coordinate system. The phone is oriented vertically. The +Z axis points upwards from the top of the phone, labeled 'Top of phone'. The +Y axis points horizontally to the right from the side of the phone, labeled 'Side of phone'. The +X axis points diagonally downwards and to the left from the front of the phone, labeled 'Screen looks this way'. + +**Figure A.1-2: DUT default alignment to coordinate system** + +The following aspects are necessary: + +- A basic understanding of the top and bottom of the device is needed in order to define unambiguous DUT positioning requirements for the test, e.g., in the drawings used in this annex, the earpiece is on the top center of the device (front), the three buttons are on the bottom of the device (front) and the camera is on the top of the device (back). +- An understanding of the origin and alignment of the coordinate system inside the test system, i.e. the directions in which the x, y, z axes point inside the test chamber, is needed in order to define unambiguous DUT orientation and measurement angles. + +# Annex B: Estimation of Measurement uncertainty + +## B.1 General + +Individual uncertainty contributions in the TRP and TRS measurements are discussed and evaluated in this Annex. A technique for calculating the total measurement uncertainty is also presented. + +An important part of a standard measurement procedure is the identification of uncertainty sources and the evaluation of the overall measurement uncertainty. There are various individual uncertainty sources in the measurement procedure that introduce a certain uncertainty contribution to the final measurement result. The approach in this standard test procedure is that the test laboratories are not limited to using some specific instruments and antenna positioners, for example. + +The TRP/TRS measurement procedure can be considered to include two stages. In Stage 1 the calibration of the absolute level of the DUT measurement results is performed by means of using a calibration antenna whose absolute gain/radiation efficiency is known at the frequencies of interest. In Stage 2 the actual measurement of the 3-D pattern of the Device Under Test (DUT) is performed. The uncertainty contributions are analysed in clause B.2 while the uncertainty budget and example tables related to TRP and TRS are listed in clauses B.4 and B.5 respectively. + +The calculation of the uncertainty contribution is based on the Guide to the expression of uncertainty in measurement [10]. Each individual uncertainty is expressed by its Standard Deviation (termed here as 'standard uncertainty') and represented by symbol $U$ . The uncertainty contributions can be classified to two categories: Type-A uncertainties, which are statistically determined e.g. by repeated measurements, and Type-B uncertainties, which are derived from existing data e.g. data sheets. Several individual uncertainties are common in Stage 1 and Stage 2 and therefore cancel. + +The procedure of forming the uncertainty budget is: + +- 1) Compile lists of individual uncertainty contributions for TRP or TRS measurement in both Stage 1 and Stage 2. +- 2) Determine the standard uncertainty of each contribution by + - a) Determining the distribution of the uncertainty (Actual, U-shaped, rectangular, normal, etc.) + - b) Determining the maximum value of each uncertainty (unless the distribution is Actual) + - c) Calculating the standard uncertainty by dividing the uncertainty by $\sqrt{2}$ if the distribution is U-shaped, by $\sqrt{3}$ if the distribution is rectangular, and by 2 if the distribution is normal. +- 3) Convert the units (if necessary) of each uncertainty element into the chosen unit, i.e. dB. +- 4) Combine all the standard uncertainties by the root-sum-squares (RSS) method to derive the 'combined standard uncertainty'. +- 5) Multiply the result by an expansion factor of 1.96 to derive expanded uncertainty at 95% confidence level: $1.96 \cdot U_c$ . +- 6) Systematic errors, commonly either DUT or test system dependent, captured in the MU budget are added to the expanded uncertainty to derive the 'total expanded uncertainty', i.e., + +$$u_{c,total\ expanded} = u_{c,expanded} + u_{c,systematic} = 1.96 \sqrt{\sum u_i^2} + \sum u_{i,systematic}$$ + +NOTE 1: The standard deviation from a data set of $N$ samples is defined as + +$$u_i = \sqrt{\frac{1}{N-1} \sum_{k=1}^N |s_k - \bar{s}|^2}$$ + +Where $s_k$ are the respective sample results and $\bar{s}$ the mean of all $N$ samples. For an uncertainty $u_i$ in dB, the dB values (instead of the linear powers) of $s_k$ and $\bar{s}$ are used. + +The combination of uncertainties is performed using dB values for simplicity. It has been shown that using dB uncertainty values gives a slightly worse combined uncertainty result than using linear values for the uncertainties. The analysis method therefore errs on the safe side. + +## B.2 MU contribution descriptions for Anechoic Chamber method + +### B.2.1 Mismatch uncertainty + +If the same chain configuration (e.g. including the measurement receiver; the measurement antenna and other elements) is used in both stages, the uncertainty is considered systematic and constant $\rightarrow$ 0.00dB value. + +If it is not the case, this uncertainty contribution has to be considered and determined by the following methods. + +#### B.2.1.1 Mismatch uncertainty between measurement receiver / communication tester and the measurement antenna + +In a measurement configuration, when two elements (devices, networks) are connected, if the matching is not ideal, there is an uncertainty in the RF level signal passing through the connection. The magnitude of the uncertainty depends on the VSWR at the junction of the two connectors. In practical measurement system there are probably several connections in a test set-up, they will all interact and contribute to the combined mismatch uncertainty. + +The total combined mismatch uncertainty is composed of 2 parts: + +- 1) The mismatch through the connector between two elements. +- 2) The mismatch due to the interaction between two elements. + +##### B.2.1.1.1 Mismatch uncertainty through the connector between two elements + +Hereunder, a measurement configuration: + +![Diagram showing a Measurement receiver (M.R) connected to Cable4 via a connector. The reflection coefficient of the Measurement Receiver is labeled as Γ_MR and the reflection coefficient of the cable is labeled as Γ_cable4. The connector is represented by two triangles pointing towards each other.](2bc39576969969ffe6d3f3d5264bba75_img.jpg) + +``` + +graph LR + MR[Measurement receiver (M.R)] -- Γ_MR --> C[Cable4] + C -- Γ_cable4 --> MR + style MR fill:#fff,stroke:#000 + style C fill:#fff,stroke:#000 + +``` + +Diagram showing a Measurement receiver (M.R) connected to Cable4 via a connector. The reflection coefficient of the Measurement Receiver is labeled as Γ\_MR and the reflection coefficient of the cable is labeled as Γ\_cable4. The connector is represented by two triangles pointing towards each other. + +**Figure B.2.1.1.1-1: Mismatch uncertainty through the connector** + +$\Gamma_{MR}$ is the complex reflection coefficient of the Measurement Receiver. This term is also applicable to the communication tester. + +$\Gamma_{cable4}$ is the complex reflection coefficient of the cable4. + +$S_{21}$ is the forward gain in the network between the two reflection coefficients of interest. + +$S_{12}$ is the backward gain in the network between the two reflection coefficients of interest. + +Note that $S_{21}$ and $S_{12}$ are set to 1 if the two parts are directly connected. + +The uncertainty limits of the mismatch are calculated by means of the following formula (equation 6.1 of [11]): + +$$\text{Mismatch limits(\% voltage)} = |\Gamma_{MR}| \cdot |\Gamma_{cable4}| \cdot |S_{21}| \cdot |S_{12}| \cdot 100$$ + +These mismatch limits are divided by $\sqrt{2}$ (equation 6.2 of [11]) because of the U-shaped distribution of the mismatch uncertainty and give the following standard uncertainty: + +$$U_{\text{mismatch}}(\% \text{ voltage}) = \frac{|\Gamma_{MR}| \cdot |\Gamma_{cable4}| \cdot |S_{21}| \cdot |S_{12}| \cdot 100}{\sqrt{2}}$$ + +To convert this standard uncertainty in dB, we divide it by the standard uncertainty conversion factor (table 1 of [11]): + +$$U_{mismatch}(\text{dB}) = \frac{|\Gamma_{MR}| \cdot |\Gamma_{cable4}| \cdot |S_{21}| \cdot |S_{12}| \cdot 100}{\sqrt{2} \cdot 11.5}$$ + +##### B.2.1.1.2 Mismatch uncertainty due to the interaction of several elements + +Previously, we presented how to determine the mismatch uncertainty between two elements through the junction (connector). Now, we introduce the other type of mismatch uncertainty, which is a result of the interaction between several elements. + +Hereunder, a measurement configuration: + +![Diagram showing a measurement configuration with a Measurement Receiver (M.R), Cable3, and Cable4. The M.R is connected to Cable3 via a junction with reflection coefficient Γ_MR. Cable3 has S-parameters S21 and S12. Cable3 is connected to Cable4 via a junction with reflection coefficient Γ_cable3. Cable4 has a reflection coefficient Γ_cable4.](c67d21fb3d9042e88cdc669f071b4e7c_img.jpg) + +The diagram illustrates a measurement setup. On the left, a box labeled 'Measurement Receiver (M.R)' is connected to a central box labeled 'Cable3'. The connection between them is marked with a double-headed arrow and the label $\Gamma_{MR}$ . The 'Cable3' box has two labels above and below it: $S_{21}$ and $S_{12}$ . To the right of 'Cable3', another box labeled 'Cable4' is connected. The connection between 'Cable3' and 'Cable4' is marked with a double-headed arrow and the label $\Gamma_{cable3}$ . The 'Cable4' box has a label $\Gamma_{cable4}$ above it. + +Diagram showing a measurement configuration with a Measurement Receiver (M.R), Cable3, and Cable4. The M.R is connected to Cable3 via a junction with reflection coefficient Γ\_MR. Cable3 has S-parameters S21 and S12. Cable3 is connected to Cable4 via a junction with reflection coefficient Γ\_cable3. Cable4 has a reflection coefficient Γ\_cable4. + +**Figure B.2.1.1.2-1: Mismatch uncertainty due to the interaction of several elements** + +Firstly, we determine the mismatch uncertainty between junctions of the elements: + +Between the MR and the cable3: + +$$U_{mismatch1}(\text{dB}) = \frac{|\Gamma_{MR}| \cdot |\Gamma_{cable3}| \cdot |S_{21}| \cdot |S_{12}| \cdot 100}{\sqrt{2} \cdot 11.5}$$ + +Between the cable3 and the cable4: + +$$U_{mismatch2}(\text{dB}) = \frac{|\Gamma_{cable3}| \cdot |\Gamma_{cable4}| \cdot |S_{21}| \cdot |S_{12}| \cdot 100}{\sqrt{2} \cdot 11.5}$$ + +$|S_{21}|$ and $|S_{12}|$ are set to 1 because there is no element between cable3 and cable 4. + +$$U_{mismatch1}(\text{dB}) = \frac{|\Gamma_{MR}| \cdot |\Gamma_{cable3}| \cdot 100}{\sqrt{2} \cdot 11.5}$$ + +$$U_{mismatch2}(\text{dB}) = \frac{|\Gamma_{cable3}| \cdot |\Gamma_{cable4}| \cdot 100}{\sqrt{2} \cdot 11.5}$$ + +Each mismatch uncertainty due to the interaction between the measurement receiver and the cable4 is determined by means of the following formula: + +$$U_{mismatch\_interaction1}(\text{dB}) = \frac{|\Gamma_{MR}| \cdot |\Gamma_{cable4}| \cdot |S_{21cable3}| \cdot |S_{12cable3}| \cdot 100}{\sqrt{2} \cdot 11.5}$$ + +$|S_{21}|$ and $|S_{12}|$ are equal and correspond to the cable3 attenuation. + +$$U_{mismatch\_interaction1}(\text{dB}) = \frac{|\Gamma_{MR}| \cdot |\Gamma_{cable4}| \cdot |S_{21cable3}|^2 \cdot 100}{\sqrt{2} \cdot 11.5}$$ + +We consider in the general case, the following measurement configuration: + +![Block diagram of mismatch uncertainty measurement configuration. A Measurement Receiver (MR) is connected to Cable1 via a reflection coefficient Γ_MR. Cable1 is connected to CableN via a dotted line representing a chain of cables. CableN is connected to an Antenna via a reflection coefficient Γ_antenna. Cable1 has S-parameters S21cable1 and S12cable1. CableN has S-parameters S21cableN and S12cableN.](acdccfc1d546eaad16a58be576456caf_img.jpg) + +Block diagram of mismatch uncertainty measurement configuration. A Measurement Receiver (MR) is connected to Cable1 via a reflection coefficient Γ\_MR. Cable1 is connected to CableN via a dotted line representing a chain of cables. CableN is connected to an Antenna via a reflection coefficient Γ\_antenna. Cable1 has S-parameters S21cable1 and S12cable1. CableN has S-parameters S21cableN and S12cableN. + +**Figure B.2.1.1.1.2-2: Mismatch uncertainty measurement configuration** + +In the general case, this uncertainty contribution can be calculated by: + +$$U_{mismatch\_interactionN}(\text{dB}) = \frac{|\Gamma_{MR}| \cdot |\Gamma_{antenna}| \cdot |S_{21cable1}| \cdot |S_{12cable1}| \cdot \dots \cdot |S_{21cableN}| \cdot |S_{12cableN}| \cdot 100}{\sqrt{2} \cdot 11.5}$$ + +$|S_{21}| = |S_{12}|$ for passive elements (cables...) + +$$U_{mismatch\_interactionN}(\text{dB}) = \frac{|\Gamma_{MR}| \cdot |\Gamma_{antenna}| \cdot |S_{21cable1}|^2 \cdot \dots \cdot |S_{21cableN}|^2 \cdot 100}{\sqrt{2} \cdot 11.5}$$ + +##### B.2.1.1.3 Total combined mismatch uncertainty + +The two kinds of mismatch uncertainty contributions are combined by the root-sum-squares (RSS) method to derive the total combined mismatch uncertainty. + +The total combined mismatch uncertainty is equal to: + +$$\sqrt{U_{mismatch1}^2 + \dots + U_{mismatchN}^2 + U_{mismatch\_interaction1}^2 + \dots + U_{mismatch\_interactionN}^2}$$ + +This formula shows that the uncertainty is frequency dependent by the way of the forward and the backward gains in the network between the two components. The uncertainty upon $|S_{21}|$ and $|S_{12}|$ increases with frequency. + +Note that for an anechoic chamber, horn antennas are frequently used as measurement antennas. There are two kinds of horn antennas: single-polarized and dual-polarized. With the second one, it is possible to measure the co-polarized and cross-polarized signals without any movement of the measurement antenna, which reduces the cable antenna uncertainty contribution and improves the measurement stability. + +To conduct the signals to the measurement receiver, the measurement system configuration using a dual-polarized horn antenna has to be completed with an RF Relay. This device will include new mismatch uncertainty contributions, which + +have to be determined with the previously presented calculation methods, completed by the RF relay parameters contributions, and described in the following. + +#### B.2.1.2 Mismatch uncertainty of the RF relay + +If the same receiver chain configuration (including the measurement receiver; the measurement antenna and other elements) is used in both stages, the uncertainty is considered systematic and constant $\rightarrow$ 0.00dB value. + +If it is not the case, this uncertainty contribution has to be considered and determined by the following method. + +The following figure describes the RF Relay with its S-parameters and the complex reflection coefficient of the inputs and output: + +![Diagram of an RF Relay showing its S-parameters and reflection coefficients. The central component is a box labeled 'RF Relay'. It has three external ports: Port 1 (left) connected to 'Input 1 device' with reflection coefficient Γ1; Port 2 (bottom) connected to 'Input 2 Device' with reflection coefficient Γ2; and Port 3 (right) connected to 'Output Device' with reflection coefficient Γ3. S-parameters are indicated by arrows: S11 (reflection at Port 1), S21 (transmission from Port 1 to Port 2), S31 (transmission from Port 1 to Port 3), S12 (transmission from Port 2 to Port 1), S22 (reflection at Port 2), S32 (transmission from Port 2 to Port 3), S13 (transmission from Port 3 to Port 1), S23 (transmission from Port 3 to Port 2), and S33 (reflection at Port 3).](0a12cc47f3c5ca76c39d5943ba8661bd_img.jpg) + +Diagram of an RF Relay showing its S-parameters and reflection coefficients. The central component is a box labeled 'RF Relay'. It has three external ports: Port 1 (left) connected to 'Input 1 device' with reflection coefficient Γ1; Port 2 (bottom) connected to 'Input 2 Device' with reflection coefficient Γ2; and Port 3 (right) connected to 'Output Device' with reflection coefficient Γ3. S-parameters are indicated by arrows: S11 (reflection at Port 1), S21 (transmission from Port 1 to Port 2), S31 (transmission from Port 1 to Port 3), S12 (transmission from Port 2 to Port 1), S22 (reflection at Port 2), S32 (transmission from Port 2 to Port 3), S13 (transmission from Port 3 to Port 1), S23 (transmission from Port 3 to Port 2), and S33 (reflection at Port 3). + +**Figure B.2.1.2-1: Mismatch uncertainty of the RF relay** + +The RF relay is used to switchover the cross and direct polarization signals from the measurement antenna. To determine RF Relay mismatch uncertainty contributions, reflection coefficients for each port and the cross-talk attenuation have to be known. + +The total combined mismatch uncertainty is composed of two parts: + +- 1) The mismatch uncertainty contributions when the RF Relay switches on the direct polarization signal +- 2) The mismatch uncertainty contributions when the RF Relay switches on the cross-polarization signal + +Each part is composed of two types of uncertainties introduced in the previous paragraph: the mismatch through the connector between two elements and the mismatch due to the interaction between several elements. + +##### B.2.1.2.1 First part: RF Relay switched on the co-polarized signal + +###### B.2.1.2.1.1 The mismatch through the connector between two elements + +Between the Input1 and the port1: + +$$U_{mismatch1}(\text{dB}) = \frac{|\Gamma_1| \cdot |S_{11}| \cdot 100}{\sqrt{2} \cdot 11.5}$$ + +Between the port3 and the Output: + +$$U_{mismatch2}(\text{dB}) = \frac{|Γ_3| \cdot |S_{33}| \cdot 100}{\sqrt{2} \cdot 11.5}$$ + +Between the Input2 and the port2: + +The RF Relay switchovers on the direct polarization signal. As a result, there is no mismatch uncertainty contribution. + +###### B.2.1.2.1.2 Mismatch due to the interaction between two elements or more + +Between the Input1 and the Output: + +$$U_{mismatch\_interaction1}(\text{dB}) = \frac{|Γ_1| \cdot |Γ_3| \cdot |S_{31}| \cdot |S_{13}| \cdot 100}{\sqrt{2} \cdot 11.5}$$ + +Between the Input1 and the Input2: + +$$U_{mismatch\_interaction2}(\text{dB}) = \frac{|Γ_1| \cdot |Γ_2| \cdot |S_{21}| \cdot |S_{12}| \cdot 100}{\sqrt{2} \cdot 11.5}$$ + +The RF Relay switchovers on the cross-polarization signal. As a result; this uncertainty contribution is usually disregarded because of the high crosstalk attenuation which is characterized by $|S_{21}|$ and $|S_{12}|$ S-parameters. If the crosstalk attenuation is low, this uncertainty contribution has to be considered. + +Between the Input2 and the Output: + +$$U_{mismatch\_interaction3}(\text{dB}) = \frac{|Γ_2| \cdot |Γ_3| \cdot |S_{23}| \cdot |S_{32}| \cdot 100}{\sqrt{2} \cdot 11.5}$$ + +The RF Relay switchovers on the cross polarization signal. As a result; this uncertainty contribution is usually disregarded because of the high cross-talk attenuation, which is characterized by $|S_{23}|$ and $|S_{32}|$ S-parameters. If the crosstalk attenuation is low, this uncertainty contribution has to be considered. + +##### B.2.1.2.2 Second part: RF relay switched on the cross-polarized signal + +###### B.2.1.2.2.1 The mismatch through the connector between two elements + +Between the Input1 and the port1: the RF Relay switchovers on the direct polarization signal. As a result, there is no mismatch uncertainty contribution. + +Between the port3 and the Output: + +$$U_{mismatch3}(\text{dB}) = \frac{|Γ_3| \cdot |S_{33}| \cdot 100}{\sqrt{2} \cdot 11.5}$$ + +Between the Input2 and the port2: + +$$U_{mismatch4}(\text{dB}) = \frac{|Γ_2| \cdot |S_{22}| \cdot 100}{\sqrt{2} \cdot 11.5}$$ + +###### B.2.1.2.2.2 Mismatch due to the interaction between two elements or more + +Between the Input1 and the Output: + +$$U_{mismatch\_interaction4}(\text{dB}) = \frac{|Γ_1| \cdot |Γ_3| \cdot |S_{31}| \cdot |S_{13}| \cdot 100}{\sqrt{2} \cdot 11.5}$$ + +The RF Relay switchovers on the cross-polarization signal. As a result; this uncertainty contribution is usually disregarded because of the high crosstalk attenuation which is characterized by $|S_{31}|$ and $|S_{13}|$ S-parameters. If the crosstalk attenuation is low, this uncertainty contribution has to be considered. + +Between the Input1 and the Input2: + +$$U_{mismatch\_interactions5}(\text{dB}) = \frac{|E_1| \cdot |E_2| \cdot |S_{21}| \cdot |S_{12}| \cdot 100}{\sqrt{2} \cdot 11.5}$$ + +The RF Relay switchovers on the cross-polarization signal. As a result; this uncertainty contribution is usually disregarded because of the high crosstalk attenuation which is characterized by $|S_{21}|$ and $|S_{12}|$ S-parameters. If the crosstalk attenuation is low, this uncertainty contribution has to be considered. + +Between the Input2 and the Output: + +$$U_{mismatch\_interaction6}(\text{dB}) = \frac{|E_2| \cdot |E_3| \cdot |S_{23}| \cdot |S_{32}| \cdot 100}{\sqrt{2} \cdot 11.5}$$ + +##### B.2.1.2.3 Total combined mismatch uncertainty + +Each non-zero mismatch uncertainty contribution from both parts (RF Relay switched on the cross and direct polarization signal) are combined by the root-sum-squares (RSS) method to derive the total combined mismatch uncertainty. + +The total combined mismatch uncertainty is equal to: + +$$\sqrt{U_{mismatch1}^2 + \dots + U_{mismatchN}^2 + U_{mismatch\_interaction1}^2 + \dots + U_{mismatch\_interactionN}^2}$$ + +If a RF Relay is used to drive the cross and direct polarization signals from the dual-polarized antenna, this total combined mismatch uncertainty has to be added with all the uncertainty measurement contributions for the total combined measurement uncertainty. + +### B.2.2 Insertion loss + +#### B.2.2.1 Insertion loss of the measurement antenna cable + +If the measurement antenna cable does not move between the calibration and the DUT measurement stage, the uncertainty due to the insertion loss of the cable is assumed to be systematic. Moreover, this uncertainty is common and constant in both stages and that is why this leads to 0.00dB value. + +If a different cable is used in the calibration measurement and in the DUT measurement, and the difference of the insertion loss is used in the calculations, then the overall combined standard uncertainty of the insertion loss measurement should be used in the uncertainty budget. The distribution of this uncertainty is assumed to be rectangular, in which case the standard uncertainty can be calculated as the maximum value divided by $\sqrt{3}$ . + +#### B.2.2.2 Insertion loss of the measurement antenna attenuator (if used) + +See Insertion loss of the measurement antenna cable + +If the measurement antenna attenuator is used in both stages, the uncertainty is considered systematic and constant → 0.00dB value. + +#### B.2.2.3 Insertion loss of the RF relays (if used) + +See Insertion loss of the measurement antenna cable. + +If the RF relay is used in both stages, the uncertainty is considered systematic and constant → 0.00dB value. + +#### B.2.2.4 Insertion loss: calibration antenna feed cable + +The feed cable of the calibration antenna only appears in Stage 1. As a result, this uncertainty has to be considered. + +This uncertainty will be measured or calculated from the manufacturer's data in logs with a rectangular distribution (see clause 5.1.2 in [11]). + +#### B.2.2.5 Insertion loss: calibration antenna attenuator (if used) + +If a calibration antenna attenuator is used, it only appears in Stage 1. As a result, this uncertainty has to be considered. + +This uncertainty will be calculated from the manufacturer's data in logs with a rectangular distribution (see clause 5.1.2 in [11]). + +### B.2.3 Influence of the antenna cable + +#### B.2.3.1 Measurement antenna cable + +If the measurement antenna is directional (i.e. peak gain >+5dBi e.g. horn, LPDA, etc.) and the same measurement antenna cable configuration is used for both stages, the uncertainty is considered systematic and constant → 0.00dB value. + +#### B.2.3.2 Calibration antenna cable + +If an efficiency calibration is performed, influence of the calibration antenna feed cable can be assumed to be negligible, due to data averaging. + +In the case of gain calibration, the influence of the calibration antenna feed cable must be assessed by measurements. A gain calibration measurement is repeated with a reasonably differing routing of the feed cable. Largest difference between the results is entered to the uncertainty budget with a rectangular distribution. + +### B.2.4 Measurement receiver: uncertainty of the absolute level + +The receiving device is used to measure the received signal level in TRP tests either as an absolute level or as a relative level. Receiving device used is typically a communication tester, spectrum analyser (SA), or power meter (PM). Generally, there occurs an uncertainty contribution from limited absolute level accuracy and non-linearity. + +This uncertainty will be determined from the manufacturer's datasheet and the distribution used (see clause 5.1.2 in [11]) shall match that provided in the datasheet which are commonly quoting MUs/accuracies with a "95% confidence level" and/or a "coverage factor of 2". In the absence of a declared distribution in the datasheet, the rectangular distribution should be used. Given the wide bandwidths of the modulated signal transmitted during the testing, the level flatness and not just the CW level accuracy shall be considered. + +### B.2.5 Communication tester: uncertainty of the absolute level + +The transmitter device (typically a communication tester or BS simulator) is used to drive a signal to the measurement antenna in sensitivity tests either as an absolute level or as a relative level. Receiving device used is the UE. Generally, there occurs uncertainty contribution from limited absolute level accuracy and non-linearity of the communication tester. + +For practical reasons, the calibration measurement (Stage 1) should be only performed with the measurement antenna as a receiver. Hence, the uncertainty on the absolute level of the transmitter device cannot be assumed as systematic. This uncertainty will be determined from the manufacturer's datasheet and the distribution used (see clause 5.1.2 in [11]) shall match that provided in the datasheet which are commonly quoting MUs/accuracies with a "95% confidence level" and/or a "coverage factor of 2". In the absence of a declared distribution in the datasheet, the rectangular distribution should be used. Furthermore, the uncertainty of the non-linearity of the device is included in the absolute level uncertainty. Given the wide bandwidths of the modulated signal transmitted during the testing, the level flatness and not just the CW level accuracy shall be considered. + +### B.2.6 Sensitivity measurement: output level step resolution + +When output power of the communication tester is swept to reach the throughput target that defines the sensitivity threshold, the final power step resolution represents an asymmetric uncertainty contribution that can be corrected since + +this uncertainty is device and test system independent. The lab shall correct the TRS results by $-0.5 \cdot \text{output level step resolution}$ of the final power step search and note the correction in the test report. + +### B.2.7 Measurement distance + +The uncertainty contribution from a finite measurement distance is estimated differently for Stage 1 and Stage 2. + +#### B.2.7.1 Offset of phase centre from axis(es) of rotation + +##### B.2.7.1.1 Offset of DUT phase centre from axis(es) of rotation + +In all the DUT measurements (Stage 2) defined in this test procedure the DUT and head phantom combination is rotated about the ear reference point of SAM phantom, which is also assumed to be the location of the phase centre in both angular directions of the measurements. + +For some positioning systems this may be practically impossible in which case a measurement uncertainty contribution can arise because the phase centre will rotate on a non-zero radius about the centre of rotation, thereby giving a variable measurement distance. Data averaging process may lead to a partial self-cancel of this uncertainty. + +The uncertainty limits of this effect are calculated by means of the following formula ( $u_{j22}$ of [12]): + +$$\text{Phase centre limits}(\%) = \frac{\pm \text{estimated offset from the axis of rotation}}{\text{range length}} \cdot 100$$ + +To convert this standard uncertainty in dB, we divide it by the standard uncertainty conversion factor (table 1 of [11]): + +$$U_{\text{phase centre offset}}(\text{dB}) = \frac{\pm \text{estimated offset from the axis of rotation}}{\text{range length} \cdot 11.5} \cdot 100$$ + +Because of the phase center can be anywhere between the offset limits, the distribution is assumed to have a rectangular distribution. + +For hand phantom measurements, the device is aligned with the centre of the quiet zone; thus, this MU element is not applicable to hand phantoms and the MU can be considered 0 dB. + +##### B.2.7.1.2 Offset of calibration antenna phase centre from axis(es) of rotation + +If a gain calibration is performed in Stage 1 with a directive antenna (e.g. horn antenna), the uncertainty contribution of calibration antenna's phase centre displacement is estimated by means of the following formula ( $u_{j21}$ of [12]): + +$$\text{Phase centre limits}(\%) = \frac{\pm \text{maximum dimension of the antenna}}{2 \cdot \text{range length}} \cdot 100$$ + +To convert this standard uncertainty in dB, we divide it by the standard uncertainty conversion factor (table 1 of [11]): + +$$U_{\text{phase centre offset}}(\text{dB}) = \frac{\pm \text{maximum dimension of the antenna}}{2 \cdot \text{range length} \cdot 11.5} \cdot 100$$ + +Because the phase centre can be anywhere between the offset limits, the distribution is assumed to have a rectangular distribution. + +If a gain calibration is performed in Stage 1 with omnidirectional calibration antenna (e.g. sleeve dipoles), uncertainty should be 0.00 dB provided that care is taken in their positioning since the phase centre are easily identifiable. + +For an efficiency calibration with an omnidirectional calibration antenna, the $U_{\text{phase centre offset}}$ is calculated similarly as for gain calibration but the uncertainty may be divided by factor 2. This is due to correcting impact of data averaging in this type of calibration. + +#### B.2.7.2 Mutual coupling + +In measurement of radio performances of UMTS mobile phones in speech mode, the mutual coupling uncertainty for this frequency band is a 0.00dB value (see annex A.2 in [13]). + +The 0.00dB value can be extended for NR FR1 band frequencies. + +#### B.2.7.3 Phase curvature + +This uncertainty originates from the finite far-field measurement distance, which causes phase curvature across the DUT. If the minimum measurement distance is respected, this error is assumed to be negligible. + +### B.2.8 Quality of quiet zone + +The uncertainty contribution due to unwanted reflections and obstructions within the anechoic chamber, including imperfect absorber treatments and the impact of positioning equipment support structure, is determined from data acquired using the ripple test methodology in clause 7.4. This data consists of single-axis pattern cuts that represent the sum of direct and reflected rays from a highly symmetrical omnidirectional radiation pattern measured at various points throughout the test volume. The data must be measured in sufficient spatial or angular resolution to accurately capture the peaks and nulls of the pattern to within a small fraction of the overall ripple contribution. In general, the worst-case peak-to-null ripple will reflect the potential error in a peak EIRP or EIS measurement for an omnidirectional DUT pattern located anywhere within the test volume. Note however that nulls in the pattern can exhibit considerably larger errors due to reflected signals being stronger than the line-of-sight signal from the null. + +When measuring the range path loss in Stage 1 using a dipole pattern, the associated measurement uncertainty may be determined from the peak-to-null ripple, after relative path loss compensation, of a single radial offset ripple test, where the range is configured as for range calibration (e.g. with any extraneous support structure removed) using a rectangular distribution. + +For spherically integrated quantities such as TRP and TRS, the peak-to-null ripple would overestimate the measurement uncertainty due to the inherent averaging of the various peaks and nulls as the spherical pattern is integrated. In this case, the surface standard deviation (SSD) [15] is used to obtain a statistical representation of the expected impact of ripple on the integrated power from an isotropic radiator placed anywhere within the test volume. Due to the impracticality of maintaining a constant path loss reference between individual ripple test cuts, each resultant pattern is treated individually and then the worst case SSD result is chosen as the standard uncertainty of the quiet zone. + +For the phi-axis ripple tests, the pattern can be considered an equatorial ( $\theta = 90^\circ$ ) cut of the isotropic pattern where every point has equal weighting on an evenly spaced spherical surface. Thus, the standard deviation of the single cut should be equivalent to the standard deviation of the entire spherical surface. Defining $p_k$ as the $k$ th ripple measurement point in linear power units ( $p_k = 10^{(P_k(\text{dB})/10)}$ ), and $\bar{p}$ as the average of all $p_k$ values in the associated ripple test, then the standard deviation of the corresponding cut is given by: + +$$s(p_k) = \sqrt{\frac{1}{(N-1)} \sum_{k=0}^{N-1} \left(\frac{p_k}{\bar{p}} - 1\right)^2}$$ + +On the theta-axis ripple test each ripple test cut can be considered as a great circle cut through an isotropic pattern with the symmetrical distortions that would be produced by revolving the pattern about the phi ( $0-180^\circ$ ) axis. Thus, it becomes apparent that ripple near the poles impacts a smaller total surface area on the sphere than that near $\theta = 90^\circ$ and $270^\circ$ . In this case, $\sin(\theta)$ weighting is used to generate the spherical surface weighted standard deviation as: + +$$s(p_k) = \sqrt{\frac{1}{N-1} \sum_{k=0}^{N-1} \left[\left(\frac{p_k}{\bar{p}} - 1\right) \sin(\theta_k)\right]^2}$$ + +Note that this equation simplifies to the previous equation when $\theta = 90^\circ$ , so the two formulations are in fact the same, regardless of which orientation of the ripple test is used. + +The standard uncertainty for the quiet zone ripple contribution to the TRP/TRS measurement is then given by the maximum SSD from all of the ripple test measurements. + +### B.2.9 DUT Tx-power drift + +A single point power reference measurement in the beginning and at the end of the measurement procedure is recommended to monitor the power drift of the DUT. Based on TX-power drift measurements for typical 3G UE, an uncertainty of 0.2 dB shall be entered to uncertainty budget with a rectangular distribution. If the drift measurement indicates larger drift, the actual drift shall be included to uncertainty. + +In order to minimize Tx-power drift error it is recommended to interleave sensitivity and power measurement of multiple channels. This spreads the measurements over a longer period, which helps to average the drift of the TX-power. + +Typical TX-power drifts of 3G UE, measured in a single angular point, DUT placed against phantom head are shown in Figure B.2.9-1. + +![Figure B.2.9-1: Output power variation of typical 3G UE during battery life. The graph shows Power [dB] on the y-axis (from -0.6 to 0.6) versus Time [min] on the x-axis (from 0 to 165). Multiple curves represent different battery levels or conditions. Most curves start near 0 dB and remain relatively flat, with some showing a slight downward trend after 45 minutes, particularly one curve that drops to approximately -0.3 dB at 90 minutes.](505116873ad67b610dfceb37016d04a3_img.jpg) + +Figure B.2.9-1: Output power variation of typical 3G UE during battery life. The graph shows Power [dB] on the y-axis (from -0.6 to 0.6) versus Time [min] on the x-axis (from 0 to 165). Multiple curves represent different battery levels or conditions. Most curves start near 0 dB and remain relatively flat, with some showing a slight downward trend after 45 minutes, particularly one curve that drops to approximately -0.3 dB at 90 minutes. + +Figure B.2.9-1: Output power variation of typical 3G UE during battery life + +### B.2.10 DUT sensitivity drift + +Due to statistical uncertainty of sensitivity measurement, drift in the TRS cannot be monitored similarly to TRP. An uncertainty value of 0.2dB can be used with a rectangular distribution, or the TRS drift should be measured, with a setup corresponding to the actual TRS measurement. + +### B.2.11 Uncertainty related to the use of phantoms + +The following elements of uncertainty contributions (when applicable) are combined by the root-sum-squares (RSS) method to derive the total combined uncertainty related to the use of phantoms. + +#### B.2.11.1 Uncertainty from using different types of SAM phantom + +This uncertainty contribution originates from the fact that different laboratories may use the two different versions of SAM head: the SAM head phantom or the SAM phantom including the head and the shoulders. The standard SAM head is the specified phantom. However, the use of the other type of SAM is also allowed with the requirement that the resulting uncertainty contribution is considered in the uncertainty budget. + +#### B.2.11.2 Simulated tissue liquid uncertainty + +This uncertainty will occur, if the laboratory uses a liquid which has dielectric parameters deviating more than $\pm 15\%$ of the target parameters. + +#### B.2.11.3 Uncertainty of dielectric properties and shape of the hand phantom + +The hand phantom contributes to OTA measurement uncertainty due to the manufacturing tolerances of its dielectric properties and shape. The dielectric properties on the surface of the hand may differ from those of its interior, so both are included in the evaluation. The moulded exterior surface of the hand shall be measured directly with an open-ended coaxial probe. The interior hand material is evaluated indirectly, by substituting a cube-shaped sample moulded from the same material and having some exterior surfaces removed. Following procedure will be used to evaluate the dielectric properties of the hand phantom; + +1. Each hand shall be manufactured together with a reference cube of the same material. The sides of the reference cube shall be not less than 40 mm in length. + +2. The moulded surface on three orthogonal sides of the cube shall be sliced away to a depth of at least 3 mm, in order to expose interior material for evaluation. The remaining three sides of the cube shall be left untreated. +3. Relative permittivity and conductivity shall be measured at ten different points on each of the three cut, exposed surfaces of the reference cube, and the combined interior averages ( $\epsilon_{int\_avg}$ , $\sigma_{int\_avg}$ , 30 points) and standard deviations ( $\epsilon_{int\_std}$ , $\sigma_{int\_std}$ , 30 points) shall be calculated. Individual interior averages for each of these three sides ( $\epsilon_{int\_i}$ , $\sigma_{int\_i}$ , 10 points) shall also be calculated. +4. Relative permittivity and conductivity shall be measured at ten points on the hand phantom exterior. A measurement point shall be located to each fingertip or as close to the tip as applicable. One measurement point shall be located to the back of the hand and one to the inner surface of wrist area. The exterior averages ( $\epsilon_{ext\_avg}$ , $\sigma_{ext\_avg}$ , 10 points) and standard deviations ( $\epsilon_{ext\_std}$ , $\sigma_{ext\_std}$ , 10 points) calculated accordingly. +5. The total averages ( $\epsilon_{avg}$ , $\sigma_{avg}$ ) shall be calculated as the average of exterior and interior values by either evaluating all data points or using equations : + +$$\epsilon_{avg} = \frac{\epsilon_{ext\_avg} + 3 \cdot \epsilon_{int\_avg}}{4}$$ + +$$\sigma_{avg} = \frac{\sigma_{ext\_avg} + 3 \cdot \sigma_{int\_avg}}{4}$$ + +6. The total standard deviations ( $\epsilon_{std}$ , $\sigma_{std}$ ) shall be calculated as the statistical combination of exterior and interior values by either evaluating all data points or using equations: + +$$\epsilon_{std} = \sqrt{\frac{1}{4} \left( \epsilon_{ext\_std}^2 + \epsilon_{ext\_avg}^2 + 3 \cdot (\epsilon_{int\_std}^2 + \epsilon_{int\_avg}^2) \right) - \epsilon_{avg}^2}$$ + +$$\sigma_{std} = \sqrt{\frac{1}{4} \left( \sigma_{ext\_std}^2 + \sigma_{ext\_avg}^2 + 3 \cdot (\sigma_{int\_std}^2 + \sigma_{int\_avg}^2) \right) - \sigma_{avg}^2}$$ + +7. The hands are acceptable for radiated performance testing, i.e., meet the minimal requirements, if + +- a. $\epsilon_{avg}$ deviates by less than 15% from the target values +- b. $\sigma_{avg}$ deviates by less than 25% from the target values +- c. the difference between the averaged permittivity of each 10-point interior surface $\epsilon_{int\_avg}$ deviates by less than 10% and $\epsilon_{ext\_avg}$ by less than 20% from the total average $\epsilon_{avg}$ +- d. the difference between the averaged conductivity of each 10-point interior surface $\sigma_{int\_avg}$ deviates by less than 20% and $\sigma_{ext\_avg}$ by less than 30% from the total average $\sigma_{avg}$ +- e. the standard deviation of the combined measurements (30 interior points and 10 exterior points) is less than 20% for permittivity $\epsilon_{std}$ and less than 40% for conductivity $\sigma_{std}$ + +8. For the hands meeting the minimal requirements of step 7, the following approximations shall be used to determine the hand uncertainty due to dielectric properties. + +$$U_\epsilon \text{ [dB]} = c_1 \cdot \left[ 10 \log_{10} \left( 1 + \left| \frac{\sqrt{\Delta \epsilon_{avg}^2 + \epsilon_{unc}^2 + (a_1 \epsilon_{std})^2}}{\epsilon} \right| \right) \right]$$ + +$$U_\sigma \text{ [dB]} = c_2 \cdot \left[ 10 \log_{10} \left( 1 + \left| \frac{\sqrt{\Delta \sigma_{avg}^2 + \sigma_{unc}^2 + (a_1 \sigma_{std})^2}}{\epsilon} \right| \right) \right]$$ + +$\Delta \epsilon_{avg}$ , $\Delta \sigma_{avg}$ , $\epsilon_{std}$ , $\sigma_{std}$ are the values determined as defined above and $\epsilon_{unc}$ and $\sigma_{unc}$ are expanded measurement uncertainties ( $k = 2$ ) of the dielectric parameter measurement method. The cube will be provided together with the hand such that the user can evaluate if the interior (cube) properties of the hand has degenerated over time by performing the test above. Coefficient $c_1 = 0.78$ , $c_2 = 0.39$ and $a_1 = 0.50$ were determined by numeric simulations. + +In case the hand phantoms are manufactured within CAD models, the tolerance is 2% and therefore the effects shape errors are negligible. If the tolerance is larger, a numerical study must be conducted. + +The assessment of uncertainties for the phantoms defined in CTIA Certification OTA Test Plan 01.72 Section 2 [25], is further detailed in CTIA Certification OTA Test Plan 01.70 Section 2 [26]. Values are from the CTIA Certification Test Plan for Wireless Device Over-the-Air Performance © CTIA Certification. Reproduced with permission. + +#### B.2.11.4 Uncertainty from using different types of Laptop Ground Plane phantom + +This uncertainty contribution originates from the fact that different laboratories may use different variations of Laptop Ground Plane phantom. The standard Laptop Ground Plane is the specified phantom. + +#### B.2.11.5 Positioning Uncertainty from using Phantoms + +Some uncertainty also occurs from the positioning of the DUT against the SAM phantom, as the DUT cannot be attached exactly in the same way every time. This uncertainty depends on how much the DUT's positioning against the SAM phantom and hand phantoms varies from the specified testing positions. It is noted that the uncertainty of the phone positioning depends on the phone holder and the measurement operator and is in fact difficult to distinguish from random uncertainty. Some uncertainty also occurs from the positioning of the DUT plugged into the Laptop Ground Plane phantom, as the DUT may not be plugged into the USB connector and positioned exactly in the same way every time. This uncertainty depends on how much the DUT's position plugged into the Laptop Ground Plane phantom varies from the specified plug-in position. Therefore, the positioning uncertainty is included in random uncertainty. + +To estimate this uncertainty for the SAM phantom, it is suggested to perform at least five evaluations of TRP/TRS whereby the device shall be dismounted and newly positioned with a fully charged battery before each test. This measurement set has to be carried out in mid channel of lowest and highest frequency bands utilized by the testing lab, for at least three phones with different type of mechanical design. The values have to be normalized by the mean for each measurement set. As a result, the uncertainty contribution entered to uncertainty budget is the difference between the maximum and minimum normalized values. + +With head and hand phantoms, random uncertainty evaluation may be done separately for each measurement configuration i.e. head only, browsing mode or speech mode. A speech mode random uncertainty evaluation, where both head and hand phantoms are used, can reasonably be considered to be the worst-case scenario and thus random uncertainties in other configurations to be less. + +To estimate this uncertainty for the Laptop Ground Plane phantom, it is suggested to perform at least five evaluations of TRP/TRS for the plug-in position whereby the device shall be dismounted and newly positioned before each test. This measurement set has to be carried out in mid channel of lowest and highest frequency bands utilized by the testing lab, for at least three USBs with different type of mechanical design. The values have to be normalized by the mean for each measurement set. As a result, the uncertainty contribution entered to uncertainty budget is the difference between the maximum and minimum normalized value. + +For the forearm phantom, the assessment of uncertainties for the phantoms defined in CTIA Certification OTA Test Plan 01.72 Section 2 [25], is further detailed in CTIA Certification OTA Test Plan 01.70 Section 2 [26]. Values are from the CTIA Certification Test Plan for Wireless Device Over-the-Air Performance © CTIA Certification. Reproduced with permission. + +#### B.2.11.6 Uncertainty of dielectric properties and shape of the forearm phantom + +The assessment of uncertainties for the phantoms defined in CTIA Certification OTA Test Plan 01.72 Section 2 [25], is further detailed in CTIA Certification OTA Test Plan 01.70 Section 2 [26]. Values are from the CTIA Certification Test Plan for Wireless Device Over-the-Air Performance © CTIA Certification. Reproduced with permission. + +### B.2.12 Coarse sampling grid + +This contributor describes the uncertainty of the measured TRP/TRS value due to the finite number of measurement grid points. Decreasing of sampling density to finite number of samples affects the measurement uncertainty by two + +different errors. First is due to inadequate number of samples and second is a systematic discrimination approximation error in TRP and TRS equations. Different TRP quadratures also have an effect on the MU. + +The grid options for TRP/TRS with associated MUs for constant-step size grids are summarized in Table B.2.12-1. + +**Table B.2.12-1: Grid Options for TRP/TRS with constant-step size grids** + +| Test Metric | Frequency Range | Quadrature | $\Delta\theta[^\circ]$ | $\Delta\phi[^\circ]$ | Min. Number of Grid Points (Note 1) | Std. Uncertainty [dB] | Mean Error (Note 3) [dB] | +|-----------------|-----------------|-----------------|------------------------|----------------------|-------------------------------------|-----------------------|---------------------------| +| TRP | < 3GHz | sin( $\theta$ ) | 15 | 15 | 266 | 0 | 0 | +| TRS | | | 30 | 30 | 62 | 0.13 | 0 | +| TRP | | Clenshaw-Curtis | 15 | 15 | 266 | 0 | 0 | +| TRS | | | 30 | 30 | 62 | 0.10 | 0 | +| TRP (Note 2) | | | 30 | 30 | 62 | 0.10 | 0 | +| TRS (Note 2) | | | 30 | 60 | 32 | 0.15 | 0 | +| TRS (Note 2) | | | 45 | 45 | 26 | 0.19 | 0 | +| TRP | > 3GHz | sin( $\theta$ ) | 15 | 15 | 266 | 0 | 0 | +| TRS | | | 30 | 30 | 62 | 0.21 | 0 | +| TRP | | Clenshaw-Curtis | 15 | 15 | 266 | 0 | 0 | +| TRS | | | 30 | 30 | 62 | 0.18 | 0 | +| TRP (Note 2) | | | 30 | 30 | 62 | 0.18 | 0 | +| TRS (Note 2) | | | 30 | 60 | 32 | 0.25 | 0 | +| TRS (Note 2, 4) | | | 45 | 45 | 27 | 0.23 | 0.08 | +| TRS (Note 2, 5) | | | 45 | 45 | 25 | 0.25 | 0.08 | + +Note 1: The exact number of grid points depends on how the back pole $EIRP(\theta=180^\circ)/EIS(\theta=180^\circ)$ is approximated due to obstruction and/or blocking. +Note 2: The overall MU shall not be larger than the maximum MU limits if the coarsest measurement grid is adopted. +Note 3: The inclusion of the mean error into the MU template/budget is FFS. +Note 4: The EIS value at $180^\circ$ is determined from two $165^\circ$ measurements. +Note 5: The EIS value at $180^\circ$ is averaged from previous cut. + +The mean error in Table B.2.12-1 shall be considered a systematic uncertainty that cannot be corrected and thus shall be included in the uncertainty budget table as a systematic uncertainty added to the combined expanded uncertainty. + +The legacy grid with $\Delta\theta=\Delta\phi=15^\circ$ for TRP and $\Delta\theta=\Delta\phi=30^\circ$ for TRS should be considered the default measurement grid and is recommended for certification testing. + +### B.2.13 Random uncertainty + +This contribution is used to account for all the unknown, unquantifiable, etc. uncertainties associated with the measurements. + +Random uncertainty MU contributions are normally distributed. + +The random uncertainty term, by definition, cannot be measured, or even isolated completely. However, past system definitions provide an empirical basis for a value. A fixed value of 0.25 dB (half that of FR2 SISO OTA measurements) is suggested for TRP measurements while a fixed value of 0.4 dB is suggested for TRS measurement to include a digital error rate uncertainty. + +### B.2.14 Frequency response + +Test systems might not be able to ensure flat frequency response across the entire channel bandwidth required for testing (e.g. up to 100MHz for NR FR1). When a frequency response correction based on the results from the system calibration measurements in Stage 1 is not possible or practical, this uncertainty has to be considered. + +This uncertainty term can be estimated as described in [14] using the following formula: + +$$\varepsilon_j = 10 \log \left( \frac{\sum_{k=j-N/2}^{j+N/2} PL_k}{(N+1)PL_j} \right)$$ + +where $\varepsilon_j$ is the expected relative error in the average power result for a given channel in dB, $PL_j$ is the linear path loss at the center frequency of the given channel, $PL_k$ is the linear path loss at each frequency point across the corresponding channel, and $N$ is the number of frequency steps across a given channel bandwidth. The maximum deviation $\varepsilon_j$ across all of the possible channels in a band shall be used to estimate the required frequency response uncertainty contribution with a rectangular distribution. + +This error may be removed directly at each frequency, $f_j$ , by using the average path loss across the channel as the range loss correction rather than the path loss at the center frequency as described in [14]. + +For sensitivity measurements, this effect is included in the output level step resolution. + +### B.2.15 Uncertainty of network analyser + +This uncertainty includes the all uncertainties involved in the S21 measurement with a network analyser, and will be determined from the manufacturer's datasheet which is now commonly quoting MUs/accuracies with a "95% confidence level" and/or a "coverage factor of 2" and the distribution used (see clause 5.1.2 in [11]) shall match that provided in the datasheet. In the absence of a declared distribution in the datasheet, the rectangular distribution should be used. + +### B.2.16 Uncertainty of the gain/efficiency of the calibration antenna + +The calibration antenna only appears in Stage 1. Therefore, the gain/efficiency uncertainty has to be considered. + +This uncertainty shall come from a calibration report (which is now commonly quoting MUs/accuracies with a "95% confidence level" and/or a "coverage factor of 2") with traceability to a National Metrology Institute with measurement uncertainty budgets generated following the guidelines outlined in internationally accepted standards. In the absence of a declared distribution in the report, the rectangular distribution should be used. + +## B.3 MU contribution descriptions for Alternative method + +Some of the terms for measurement uncertainty in the Reverberation Chamber method are identical to the reference method (i.e. Anechoic Chamber). Therefore, this section only lists the additional MU contribution description that are unique to the Reverberation Chamber method. + +### B.3.1 Additional Power Loss in EUT Chassis + +When the EUT is small and does not add noticeable loss to the chamber, the calibration procedure outlined in section 8.4, is performed without the EUT present in the chamber. The possible difference in average chamber transmission level between the EUT measurement and the reference measurement must in this case be considered in the uncertainty evaluation. The uncertainty value for this contribution can be tested empirically by choosing a unit within a set of samples which is considered to incur the highest amount of loss (normally the largest unit), and measure the average transmission loss in the chamber with and without the test unit present in the chamber including phantoms if applicable. The difference between the two cases shall be used in the uncertainty calculation and the distribution should be assumed to be rectangular. + +Alternatively, a fixed value of 0.2 dB with a rectangular distribution can be used in the uncertainty calculations. + +### B.3.3 Quality of Spatial Uniformity + +The standard deviation over calibration antenna positions and rotations of the transfer function, chamber reference or chamber loss ( $|S_{21}|^2$ ). This measures the lack of spatial uniformity over the test zone in the reverberation chamber which is also referred as lack of isotropy, statistical ripple, or uniformity of the transfer function. This procedure is detailed in section 8.3.3. + +According to the significance tests performed in [23], the uncertainty due to lack of spatial uniformity is not negligible. In this case, equation 12 in [23] holds and leads to the following uncertainty: + +$$U = \frac{\sigma_{P_{ref}}^{dB}}{\sqrt{T}}$$ + +The expanded uncertainty covers the 95th percentile and is given by + +$$U_{95} = K_{95} * U$$ + +Where $K_{95}$ is the coverage factor for the two-sided 95th percentile of Student's $t$ -distribution given $T-1$ degrees of freedom and corresponds to 2.201 at $T=12$ (11 degrees of freedom) or 2.069 at $T=24$ (23 degrees of freedom). + +### B.3.4 Sensitivity measurement: output level step resolution + +When output power of the communication tester is swept to reach the throughput target that defines the sensitivity threshold, used power step resolution creates this uncertainty. Output power step used in the sensitivity measurement is divided by factor 2 and then a rectangular distribution applied to obtain the uncertainty. + +## B.4 MU Assessment for TRP + +### B.4.1 MU Assessment for TRP in Anechoic Chamber + +The uncertainty contributions related to TRP are listed in Table B.4.1-1. A preliminary example uncertainty budgets are presented in Table B.4.1-2 and Table B.4.1-3. + +**Table B.4.1-1 Uncertainty contributions in TRP measurement for anechoic chamber method** + +| UID | Description of uncertainty contribution | Details in clause | +|---------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|-------------------| +| Stage 2: DUT measurement (Figure 7.2-1, Figure 7.2-2) | | | +| 1 | Mismatch of receiver chain | B.2.1 | +| 2 | Insertion loss of receiver chain | B.2.2 | +| 3 | Influence of the measurement antenna cable | B.2.3 | +| 4 | Measurement Receiver: uncertainty of the absolute level | B.2.4 | +| 5 | Measurement distance | B.2.7 | +| 6 | Quality of quiet zone | B.2.8 | +| 7 | DUT Tx-power drift | B.2.9 | +| 8 | Uncertainty related to the use of phantoms | B.2.11 | +| 9 | Coarse sampling grid | B.2.12 | +| 10 | Random uncertainty | B.2.13 | +| 11 | Frequency Response | B.2.14 | +| Stage 1: Calibration measurement, network analyzer method (Figure 7.3-1) | | | +| 12 | Uncertainty of network analyzer | B.2.15 | +| 13 | Mismatch of receiver chain | B.2.1 | +| 14 | Insertion loss of receiver chain | B.2.2 | +| 15 | Mismatch in the connection of calibration antenna | B.2.1 | +| 16 | Influence of the calibration antenna feed cable | B.2.3 | +| 17 | Influence of the measurement antenna cable | B.2.3 | +| 18 | Uncertainty of the absolute gain/ radiation efficiency of the calibration antenna | B.2.16 | +| 19 | Measurement distance | B.2.7 | +| 20 | Quality of the Quiet Zone | B.2.8 | +| Systematic Errors | | | +| 21 | Systematic Error related to TRP grids | B.2.12 | + +**Table B.4.1-2 Preliminary example of uncertainty budget for TRP hand only (browsing mode) +measurement for anechoic chamber method for NR FR1 bands** + +| UID | Uncertainty Source | Comment | Uncertainty Value [dB] | | Prob Distr | Div | ci | Standard Uncertainty [dB] | | +|------------------------------------------------------------------|-----------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|------------------------|------------|-------------|-----|----|---------------------------|-------------| +| | | | Below 3GHz | Above 3GHz | | | | Below 3GHz | Above 3GHz | +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Mismatch of receiver chain | $\Gamma_{\text{receiver}} < 0.33$
$\Gamma_{\text{measurement antenna}} < 0.5$
Cable attenuation > 3dB | 0.26 | 0.26 | U-shaped | 1.4 | 1 | 0.18 | 0.18 | +| 2 | Insertion loss of receiver chain | Systematic with Stage 1 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 3 | Influence of the measurement antenna cable | Systematic with Stage 1 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 4 | Measurement Receiver: uncertainty of the absolute level | Spectrum Analyzer | 0.42 | 0.54 | Normal | 2 | 1 | 0.21 | 0.27 | +| 5 | Measurement distance | DUT is not offset for hand-only phantom testing | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 6 | Quality of quiet zone | Surface standard deviation of power measurements in ripple test | 0.5 | 0.5 | Actual | 1 | 1 | 0.50 | 0.50 | +| 7 | DUT Tx-power drift | Drift | 0.2 | 0.2 | Rectangular | 1.7 | 1 | 0.12 | 0.12 | +| 8 | Uncertainty related to the use of phantoms | Material Dielectric Constant, Material Conductivity, Geometry/Shape (incl. spacer), Data Mode Fixture | 0.64 | 0.64 | Rectangular | 1.7 | 1 | 0.37 | 0.37 | +| 9 | Coarse sampling grid | Sampling grids per Table B.2.12-1 | 0 | 0 | Actual | 1 | 1 | 0.00 | 0.00 | +| 10 | Random Uncertainty | Fixed MU to account for all the unknown, unquantifiable, etc. uncertainties | 0.25 | 0.25 | Normal | 2 | 1 | 0.13 | 0.13 | +| 11 | Frequency Response | Average path loss corrected | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| Stage 1: Calibration measurement, network analyzer method | | | | | | | | | | +| 12 | Uncertainty of network analyzer | From datasheet of VNA with assessed transmission coefficients | 0.2 | 0.5 | Normal | 2 | 1 | 0.10 | 0.25 | +| 13 | Mismatch of receiver chain | Taken into account in VNA uncertainty term | 0 | 0 | U-shaped | 1.4 | 1 | 0.00 | 0.00 | +| 14 | Insertion loss of receiver chain | Systematic with Stage 2 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 15 | Mismatch in the connection of calibration antenna | Taken in to account in VNA setup uncertainty | 0 | 0 | U-shaped | 1.4 | 1 | 0.00 | 0.00 | +| 16 | Influence of the calibration antenna feed cable | Gain calibration with a dipole | 0.3 | 0.3 | Rectangular | 1.7 | 1 | 0.17 | 0.17 | +| 17 | Influence of the measurement antenna cable | Systematic with Stage 2 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 18 | Uncertainty of the absolute gain/ radiation efficiency of the calibration antenna | Calibration report with traceability to a National Metrology Institute | 0.58 | 0.58 | Normal | 2 | 1 | 0.29 | 0.29 | +| 19 | Measurement distance | Dipole: aligned with phase center | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 20 | Quality of the Quiet Zone | Peak-to-null ripple | 0.5 | 0.5 | Rectangular | 1.7 | 1 | 0.29 | 0.29 | +| Combined standard uncertainty [dB] | | | | | | | | 0.84 | 0.88 | +| Expanded uncertainty [dB] (Confidence interval of 95 %) | | | | | | | | 1.64 | 1.73 | + +| | | | | | | | | | | +|----------------------------------------------------------------------|---------------------------------------|------------|---|---|--------|---|---|-------------|-------------| +| 21 | Systematic Error related to TRP grids | mean error | 0 | 0 | Actual | 1 | 1 | 0.00 | 0.00 | +| Total Expanded uncertainty [dB] (Confidence interval of 95 %) | | | | | | | | 1.64 | 1.73 | + +**Table B.4.1-3 Preliminary example of uncertainty budget for TRP Beside Head and Hand (Talk mode) measurement for anechoic chamber method for NR FR1 bands** + +| UID | Uncertainty Source | Comment | Uncertainty Value [dB] | | Prob Distr | Div | ci | Standard Uncertainty [dB] | | +|------------------------------------------------------------------|-----------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|------------------------|------------|-------------|-----|----|---------------------------|------------| +| | | | Below 3GHz | Above 3GHz | | | | Below 3GHz | Above 3GHz | +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Mismatch of receiver chain | $\Gamma_{\text{receiver}} < 0.33$
$\Gamma_{\text{measurement antenna}} < 0.5$
Cable attenuation > 3dB | 0.26 | 0.26 | U-shaped | 1.4 | 1 | 0.18 | 0.18 | +| 2 | Insertion loss of receiver chain | Systematic with Stage 1 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 3 | Influence of the measurement antenna cable | Systematic with Stage 1 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 4 | Measurement Receiver: uncertainty of the absolute level | Spectrum Analyzer | 0.42 | 0.54 | Normal | 2 | 1 | 0.21 | 0.27 | +| 5 | Measurement distance | d=1.6m, $\Delta d=0.05\text{m}$ | 0.27 | 0.27 | Rectangular | 1.7 | 1 | 0.16 | 0.16 | +| 6 | Quality of quiet zone | Surface standard deviation of power measurements in ripple test | 0.5 | 0.5 | Actual | 1 | 1 | 0.50 | 0.50 | +| 7 | DUT Tx-power drift | Drift | 0.2 | 0.2 | Rectangular | 1.7 | 1 | 0.12 | 0.12 | +| 8 | Uncertainty related to the use of phantoms | Material Dielectric Constant, Material Conductivity, Geometry/Shape (incl. spacer), Beside Head and Hand | 0.99 | 0.99 | Rectangular | 1.7 | 1 | 0.57 | 0.57 | +| 9 | Coarse sampling grid | Sampling grids per Table B.2.12-1 | 0 | 0 | Actual | 1 | 1 | 0.00 | 0.00 | +| 10 | Random Uncertainty | Fixed MU to account for all the unknown, unquantifiable, etc. uncertainties | 0.25 | 0.25 | Normal | 2 | 1 | 0.13 | 0.13 | +| 11 | Frequency Response | Average path loss corrected | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| Stage 1: Calibration measurement, network analyzer method | | | | | | | | | | +| 12 | Uncertainty of network analyzer | From datasheet of VNA with assessed transmission coefficients | 0.2 | 0.5 | Normal | 2 | 1 | 0.10 | 0.25 | +| 13 | Mismatch of receiver chain | Taken into account in VNA uncertainty term | 0 | 0 | U-shaped | 1.4 | 1 | 0.00 | 0.00 | +| 14 | Insertion loss of receiver chain | Systematic with Stage 2 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 15 | Mismatch in the connection of calibration antenna | Taken in to account in VNA setup uncertainty | 0 | 0 | U-shaped | 1.4 | 1 | 0.00 | 0.00 | +| 16 | Influence of the calibration antenna feed cable | Gain calibration with a dipole | 0.3 | 0.3 | Rectangular | 1.7 | 1 | 0.17 | 0.17 | +| 17 | Influence of the measurement antenna cable | Systematic with Stage 2 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 18 | Uncertainty of the absolute gain/ radiation efficiency of the calibration antenna | Calibration report with traceability to a National Metrology Institute | 0.58 | 0.58 | Normal | 2 | 1 | 0.29 | 0.29 | +| 19 | Measurement distance | Dipole: aligned with phase center | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 20 | Quality of the Quiet Zone | Peak-to-null ripple | 0.5 | 0.5 | Rectangular | 1.7 | 1 | 0.29 | 0.29 | + +| | | | | | | | | | | +|----------------------------------------------------------------------|---------------------------------------|------------|---|---|--------|---|---|-------------|-------------| +| Combined standard uncertainty [dB] | | | | | | | | 0.96 | 1.00 | +| Expanded uncertainty [dB] (Confidence interval of 95 %) | | | | | | | | 1.88 | 1.96 | +| 21 | Systematic Error related to TRP grids | mean error | 0 | 0 | Actual | 1 | 1 | 0.00 | 0.00 | +| Total Expanded uncertainty [dB] (Confidence interval of 95 %) | | | | | | | | 1.88 | 1.96 | + +**Table B.4.1-4 Preliminary example of uncertainty budget for TRP Wrist-Worn device measurement for anechoic chamber method for NR FR1 bands** + +| UID | Uncertainty Source | Comment | Uncertainty Value [dB] | | Prob Distr | Div | ci | Standard Uncertainty [dB] | | +|------------------------------------------------------------------|-----------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|------------------------|------------|-------------|-----|----|---------------------------|------------| +| | | | Below 3GHz | Above 3GHz | | | | Below 3GHz | Above 3GHz | +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Mismatch of receiver chain | $\Gamma_{\text{receiver}} < 0.33$
$\Gamma_{\text{measurement antenna}} < 0.5$
Cable attenuation > 3dB | 0.26 | 0.26 | U-shaped | 1.4 | 1 | 0.18 | 0.18 | +| 2 | Insertion loss of receiver chain | Systematic with Stage 1 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 3 | Influence of the measurement antenna cable | Systematic with Stage 1 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 4 | Measurement Receiver: uncertainty of the absolute level | Spectrum Analyzer | 0.42 | 0.54 | Normal | 2 | 1 | 0.21 | 0.27 | +| 5 | Measurement distance | DUT is not offset for forearm phantom testing | 0 | 0 | Rectangular | 1.7 | 1 | 0 | 0 | +| 6 | Quality of quiet zone | Surface standard deviation of power measurements in ripple test | 0.5 | 0.5 | Actual | 1 | 1 | 0.50 | 0.50 | +| 7 | DUT Tx-power drift | Drift | 0.2 | 0.2 | Rectangular | 1.7 | 1 | 0.12 | 0.12 | +| 8 | Uncertainty related to the use of phantoms | Material Dielectric Constant, Material Conductivity, Geometry/Shape (incl. spacer), Forearm | 0.74 | 0.74 | Rectangular | 1.7 | 1 | 0.43 | 0.43 | +| 9 | Coarse sampling grid | Sampling grids per Table B.2.12-1 | 0 | 0 | Actual | 1 | 1 | 0.00 | 0.00 | +| 10 | Random Uncertainty | Fixed MU to account for all the unknown, unquantifiable, etc. uncertainties | 0.25 | 0.25 | Normal | 2 | 1 | 0.13 | 0.13 | +| 11 | Frequency Response | Average path loss corrected | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| Stage 1: Calibration measurement, network analyzer method | | | | | | | | | | +| 12 | Uncertainty of network analyzer | From datasheet of VNA with assessed transmission coefficients | 0.2 | 0.5 | Normal | 2 | 1 | 0.10 | 0.25 | +| 13 | Mismatch of receiver chain | Taken into account in VNA uncertainty term | 0 | 0 | U-shaped | 1.4 | 1 | 0.00 | 0.00 | +| 14 | Insertion loss of receiver chain | Systematic with Stage 2 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 15 | Mismatch in the connection of calibration antenna | Taken in to account in VNA setup uncertainty | 0 | 0 | U-shaped | 1.4 | 1 | 0.00 | 0.00 | +| 16 | Influence of the calibration antenna feed cable | Gain calibration with a dipole | 0.3 | 0.3 | Rectangular | 1.7 | 1 | 0.17 | 0.17 | +| 17 | Influence of the measurement antenna cable | Systematic with Stage 2 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 18 | Uncertainty of the absolute gain/ radiation efficiency of the calibration antenna | Calibration report with traceability to a National Metrology Institute | 0.58 | 0.58 | Normal | 2 | 1 | 0.29 | 0.29 | + +| | | | | | | | | | | +|----------------------------------------------------------------------|---------------------------------------|-----------------------------------|-----|-----|-------------|-----|---|-------------|-------------| +| 19 | Measurement distance | Dipole: aligned with phase center | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 20 | Quality of the Quiet Zone | Peak-to-null ripple | 0.5 | 0.5 | Rectangular | 1.7 | 1 | 0.29 | 0.29 | +| Combined standard uncertainty [dB] | | | | | | | | 0.86 | 0.91 | +| Expanded uncertainty [dB] (Confidence interval of 95 %) | | | | | | | | 1.69 | 1.78 | +| 21 | Systematic Error related to TRP grids | mean error | 0 | 0 | Actual | 1 | 1 | 0.00 | 0.00 | +| Total Expanded uncertainty [dB] (Confidence interval of 95 %) | | | | | | | | 1.69 | 1.78 | + +### B.4.2 MU Assessment for TRP in Reverberation Chamber + +**Table B.4.2-1 Uncertainty contributions in TRP measurement for reverberation chamber method** + +| UID | Description of uncertainty contribution | | Details in clause | +|-----------------------------------------|-----------------------------------------------------------------------------------|--|-------------------| +| Stage 2: DUT measurement | | | | +| 1 | Mismatch of receiver chain | | B.2.1 | +| 2 | Insertion loss of receiver chain | | B.2.2 | +| 3 | Influence of the measurement antenna cable | | B.2.3 | +| 4 | Measurement Receiver: uncertainty of the absolute level | | B.2.4 | +| 5 | Quality of Spatial Uniformity | | B.3.3 | +| 6 | Additional power loss in EUT chassis | | B.3.1 | +| 7 | DUT Tx-power drift | | B.2.9 | +| 8 | Uncertainty related to the use of phantoms | | B.2.11 | +| 9 | Random uncertainty | | B.2.13 | +| Stage 1: Calibration measurement | | | | +| 10 | Uncertainty of network analyzer | | B.2.15 | +| 11 | Mismatch of receiver chain | | B.2.1 | +| 12 | Insertion loss of receiver chain | | B.2.2 | +| 13 | Mismatch in the connection of calibration antenna | | B.2.1 | +| 14 | Influence of the calibration antenna feed cable | | B.2.3 | +| 15 | Influence of the measurement antenna cable | | B.2.3 | +| 16 | Uncertainty of the absolute gain/ radiation efficiency of the calibration antenna | | B.2.16 | +| 17 | Uniformity of transfer function | | B.3.3 | + +**Table B.4.2-2 Preliminary example of uncertainty budget for TRP measurement hand only (browsing mode) for reverberation chamber method for NR FR1 bands** + +| UID | Uncertainty Source | Comment | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] | +|---------------------------------|---------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|------------------------|-------------|------|----|---------------------------| +| Stage 2: DUT measurement | | | | | | | | +| 1 | Mismatch of receiver chain | $\Gamma_{\text{receiver}} < 0.33$
$\Gamma_{\text{measurement antenna connection}} < 0.5$
Cable loss > 3dB | 0.26 | U-shaped | 1.41 | 1 | 0.18 | +| 2 | Insertion loss of receiver chain | Systematic with Stage 1 (=> cancels) | 0.1 | Rectangular | 1.73 | 1 | 0.06 | +| 3 | Influence of the fixed measurement antenna cable | Systematic with Stage 1 (=> cancels) | 0 | Rectangular | 1.73 | 1 | 0.00 | +| 4 | Measurement Receiver: uncertainty of the absolute level | From datasheet of communication tester or Spectrum Analyzer | 0.54 | Normal | 2 | 1 | 0.27 | +| 5 | Quality of Spatial Uniformity | Statistics of chamber | 0.5 | Actual | 1 | 1 | 0.5 | + +| | | | | | | | | +|----------------------------------------------------|-----------------------------------------------------------------------------------|-------------------------------------------------------------------|------|-------------|------|---|--------| +| 6 | Additional power loss in EUT chassis | The EUT not present in the chamber during calibration measurement | 0.2 | Rectangular | 1.73 | 1 | 0.12 | +| 7 | DUT Tx-power drift | Drift | 0.2 | Rectangular | 1.73 | 1 | 0.12 | +| 8 | Uncertainty related to the use of phantoms | Material and Geometry | 0.64 | Rectangular | 1.73 | 1 | 0.37 | +| 9 | Random uncertainty | Using the same setup and stirring sequence | 0.25 | Rectangular | 1.73 | 1 | [0.14] | +| Stage 1: Calibration measurement | | | | | | | | +| 10 | Uncertainty of network analyzer | Manufacturer's uncertainty calculator, covers whole NA setup | 0.5 | Normal | 2 | 1 | 0.25 | +| 11 | Mismatch of receiver chain | Taken in to account in NA setup uncertainty | 0 | U-shaped | 1.41 | 1 | 0.00 | +| 12 | Insertion loss of receiver chain | Systematic with Stage 1 (=> cancels) | 0 | Rectangular | 1.73 | 1 | 0.00 | +| 13 | Mismatch in the connection of calibration antenna | Taken in to account in NA setup uncertainty | 0 | U-shaped | 1.41 | 1 | 0.00 | +| 14 | Influence of the feed cable of the calibration antenna | Efficiency calibration used | 0 | Rectangular | 1.73 | 1 | 0.00 | +| 15 | Influence of the measurement antenna cable | Systematic with Stage 1 (=> cancels) | 0 | Rectangular | 1.73 | 1 | 0.00 | +| 16 | Uncertainty of the absolute gain/ radiation efficiency of the calibration antenna | Calibration certificate | 0.58 | Normal | 2 | 1 | [0.29] | +| 17 | Uniformity of transfer function | Statistics of chamber | 0.5 | Actual | 1 | 1 | [0.5] | +| Combined standard uncertainty | | $u_c = \sqrt{\sum_{i=1}^m c_i^2 \cdot u_i^2}$ | | | | | [0.97] | +| Expanded uncertainty (Confidence interval of 95 %) | | $u_e = 1,96 u_c$ | | | | | [1.90] | + +**Table B.4.2-2 Preliminary example of uncertainty budget for TRP Beside Head and Hand (Talk mode) measurement for reverberation chamber method for NR FR1 bands** + +| UID | Uncertainty Source | Comment | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] | +|---------------------------------|---------------------------------------------------------|----------------------------------------------------------------------------------|------------------------|-------------|------|----|---------------------------| +| Stage 2: DUT measurement | | | | | | | | +| 1 | Mismatch of receiver chain | $\Gamma_{\text{receiver}} < 0.33$
$\Gamma_{\text{measurement antenna}} < 0.5$ | 0.26 | U-shaped | 1.41 | 1 | 0.18 | +| 2 | Insertion loss of receiver chain | Typically measured | 0.1 | Rectangular | 1.73 | 1 | 0.06 | +| 3 | Influence of the fixed measurement antenna cable | Systematic with Stage 1 (=> cancels) | 0 | Rectangular | 1.73 | 1 | 0.00 | +| 4 | Measurement Receiver: uncertainty of the absolute level | Spectrum Analyzer | 0.54 | Normal | 2 | 1 | 0.27 | +| 5 | Quality of Spatial Uniformity | Statistics of chamber | 0.5 | Actual | 1 | 1 | [0.5] | + +| | | | | | | | | +|----------------------------------------------------|-----------------------------------------------------------------------------------|-------------------------------------------------------------------|------|-------------|------|---|--------| +| 6 | Additional power loss in EUT chassis | The EUT not present in the chamber during calibration measurement | 0.2 | Rectangular | 1.73 | 1 | [0.12] | +| 7 | DUT Tx-power drift | Drift | 0.2 | Rectangular | 1.73 | 1 | 0.12 | +| 8 | Uncertainty related to the use of phantoms | Material and Geometry, Beside Head/Hand | 0.99 | Rectangular | 1.73 | 1 | 0.57 | +| 9 | Random Uncertainty | Using the same setup and stirring sequence | 0.25 | Rectangular | 1.73 | 1 | [0.14] | +| Stage 1: Calibration measurement | | | | | | | | +| 10 | Uncertainty of network analyzer | Manufacturer's uncertainty calculator, covers whole NA setup | 0.5 | Normal | 2 | 1 | 0.25 | +| 11 | Mismatch of receiver chain | Taken in to account in NA setup uncertainty | 0 | U-shaped | 1.41 | 1 | 0.00 | +| 12 | Insertion loss of receiver chain | Systematic with Stage 1 (=> cancels) | 0 | Rectangular | 1.73 | 1 | 0.00 | +| 13 | Mismatch in the connection of calibration antenna | Taken in to account in NA setup uncertainty | 0 | U-shaped | 1.41 | 1 | 0.00 | +| 14 | Influence of the feed cable of the calibration antenna | Efficiency calibration used | 0 | Rectangular | 1.73 | 1 | 0.00 | +| 15 | Influence of the measurement antenna cable | Systematic with Stage 1 (=> cancels) | 0 | Rectangular | 1.73 | 1 | 0.00 | +| 16 | Uncertainty of the absolute gain/ radiation efficiency of the calibration antenna | Calibration certificate | 0.58 | Normal | 2 | 1 | [0.29] | +| 17 | Uniformity of transfer function | Statistics of chamber | 0.5 | Actual | 1 | 1 | [0.5] | +| Combined standard uncertainty | | $u_c = \sqrt{\sum_{i=1}^m c_i^2 \cdot u_i^2}$ | | | | | [1.06] | +| Expanded uncertainty (Confidence interval of 95 %) | | $u_e = 1,96 u_c$ | | | | | [2.08] | + +## B.5 MU Assessment for TRS + +### B.5.1 MU Assessment for TRS in Anechoic Chamber + +The uncertainty contributions related to TRS are listed in Table B.5.1-1. A preliminary example uncertainty budgets are presented in Table B.5.1-2 and Table B.5.1-3. + +**Table B.5.1-1 Uncertainty contributions in TRS measurement for anechoic chamber method** + +| UID | Description of uncertainty contribution | Details in clause | +|--------------------------------------------------------------|----------------------------------------------------------------|-------------------| +| Stage 2: DUT measurement (Figure 7.2-1, Figure 7.2-2) | | | +| 1 | Mismatch of transmitter chain | B.2.1 | +| 2 | Insertion loss of transmitter chain | B.2.2 | +| 3 | Influence of the measurement antenna cable | B.2.3 | +| 4 | Communication Tester: uncertainty of the absolute output level | B.2.5 | +| 5 | Sensitivity measurement: output level step resolution | B.2.6 | + +| | | | +|---------------------------------------------------------------------------------|----------------------------------------------------------------------------------|--------| +| 6 | Measurement distance | B.2.7 | +| 7 | Quality of quiet zone | B.2.8 | +| 8 | DUT sensitivity drift | B.2.10 | +| 9 | Uncertainty related to the use of phantoms | B.2.11 | +| 10 | Coarse sampling grid | B.2.12 | +| 11 | Random uncertainty | B.2.13 | +| 12 | Frequency Response | B.2.14 | +| Stage 1: Calibration measurement, network analyzer method (Figure 7.3-1) | | | +| 13 | Uncertainty of network analyzer | B.2.15 | +| 14 | Mismatch of transmitter chain | B.2.1 | +| 15 | Insertion loss of transmitter chain | B.2.2 | +| 16 | Mismatch in the connection of calibration antenna | B.2.1 | +| 17 | Influence of the calibration antenna feed cable | B.2.3 | +| 18 | Influence of the measurement antenna cable | B.2.3 | +| 19 | Uncertainty of the absolute gain/radiation efficiency of the calibration antenna | B.2.16 | +| 20 | Measurement distance | B.2.7 | +| 21 | Quality of quiet zone | B.2.8 | +| Systematic Errors | | | +| 22 | Systematic Error related to TRS grids | B.2.12 | + +**Table B.5.1-2: Preliminary example of uncertainty budget for TRS hand only (browsing mode) measurement for anechoic chamber method for NR FR1 bands** + +| UID | Uncertainty Source | Comment | Uncertainty Value [dB] | | Prob Distr | Div | ci | Standard Uncertainty [dB] | | +|---------------------------------|----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|------------------------|------------|-------------|------|----|---------------------------|------------| +| | | | Below 3GHz | Above 3GHz | | | | Below 3GHz | Above 3GHz | +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Mismatch of receiver chain | $\Gamma_{\text{comm tester}} < 0.29$
$\Gamma_{\text{measurement antenna}} < 0.5$
Cable attenuation > 3dB | 0.22 | 0.22 | U-shaped | 1.4 | 1 | 0.16 | 0.16 | +| 2 | Insertion loss of receiver chain | Systematic with Stage 1 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 3 | Influence of the measurement antenna cable | Systematic with Stage 1 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 4 | Communication Tester: uncertainty of the absolute output level | Manufacturer's data sheet | 1.3 | 1.3 | Normal | 2 | 1 | 0.65 | 0.65 | +| 5 | Sensitivity measurement: output level step resolution | Systematic error that can be corrected | 0 | 0 | Rectangular | 1.73 | 1 | 0.00 | 0.00 | +| 6 | Measurement distance | DUT is not offset for hand-only phantom testing | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 7 | Quality of quiet zone | Surface standard deviation of power measurements in ripple test | 0.5 | 0.5 | Actual | 1 | 1 | 0.50 | 0.50 | +| 8 | DUT sensitivity drift | Drift | 0.2 | 0.2 | Rectangular | 1.7 | 1 | 0.12 | 0.12 | +| 9 | Uncertainty related to the use of phantoms | Material Dielectric Constant, Material Conductivity, Geometry/Shape (incl. spacer), Data Mode Fixture | 0.64 | 0.64 | Rectangular | 1.7 | 1 | 0.37 | 0.37 | +| 10 | Coarse sampling grid | Sampling grids per Table B.2.12-1 | 0.10 | 0.18 | Actual | 1 | 1 | 0.10 | 0.18 | +| 11 | Random Uncertainty | Fixed MU to account for all the unknown, unquantifiable, etc. uncertainties | 0.4 | 0.4 | Normal | 2 | 1 | 0.20 | 0.20 | + +| | | | | | | | | | | +|----------------------------------------------------------------------|-----------------------------------------------------------------------------------|------------------------------------------------------------------------|------|------|-------------|-----|---|-------------|-------------| +| | | including digital error rate | | | | | | | | +| 12 | Frequency Response | Included in the output level step resolution | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| Stage 1: Calibration measurement, network analyzer method | | | | | | | | | | +| 13 | Uncertainty of network analyzer | From datasheet of VNA with assessed transmission coefficients | 0.2 | 0.5 | Normal | 2 | 1 | 0.10 | 0.25 | +| 14 | Mismatch of receiver chain | Taken into account in VNA uncertainty term | 0 | 0 | U-shaped | 1.4 | 1 | 0.00 | 0.00 | +| 15 | Insertion loss of receiver chain | Systematic with Stage 2 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 16 | Mismatch in the connection of calibration antenna | Taken in to account in VNA setup uncertainty | 0 | 0 | U-shaped | 1.4 | 1 | 0.00 | 0.00 | +| 17 | Influence of the calibration antenna feed cable | Gain calibration with a dipole | 0.3 | 0.3 | Rectangular | 1.7 | 1 | 0.17 | 0.17 | +| 18 | Influence of the measurement antenna cable | Systematic with Stage 2 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 19 | Uncertainty of the absolute gain/ radiation efficiency of the calibration antenna | Calibration report with traceability to a National Metrology Institute | 0.58 | 0.58 | Normal | 2 | 1 | 0.29 | 0.29 | +| 20 | Measurement distance | Dipole: aligned with phase center | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 21 | Quality of the Quiet Zone | Peak-to-null ripple | 0.5 | 0.5 | Rectangular | 1.7 | 1 | 0.29 | 0.29 | +| Combined standard uncertainty [dB] | | | | | | | | 1.05 | 1.09 | +| Expanded uncertainty [dB] (Confidence interval of 95 %) | | | | | | | | 2.06 | 2.13 | +| 22 | Systematic Error related to TRS grids | mean error | 0 | 0 | Actual | 1 | 1 | 0.00 | 0.00 | +| Total Expanded uncertainty [dB] (Confidence interval of 95 %) | | | | | | | | 2.06 | 2.13 | + +**Table B.5.1-3: Preliminary example of uncertainty budget for TRS Beside Head and Hand (Talk mode) measurement for anechoic chamber method for NR FR1 bands** + +| UID | Uncertainty Source | Comment | Uncertainty Value [dB] | | Prob Distr | Div | ci | Standard Uncertainty [dB] | | +|------------------------------------------------------------------|-----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|------------------------|------------|-------------|------|----|---------------------------|------------| +| | | | Below 3GHz | Above 3GHz | | | | Below 3GHz | Above 3GHz | +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Mismatch of receiver chain | $\Gamma_{\text{comm tester}} < 0.29$
$\Gamma_{\text{measurement antenna}} < 0.5$
Cable attenuation > 3dB | 0.22 | 0.22 | U-shaped | 1.4 | 1 | 0.16 | 0.16 | +| 2 | Insertion loss of receiver chain | Systematic with Stage 1 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 3 | Influence of the measurement antenna cable | Systematic with Stage 1 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 4 | Communication Tester: uncertainty of the absolute output level | Manufacturer's data sheet | 1.3 | 1.3 | Normal | 2 | 1 | 0.65 | 0.65 | +| 5 | Sensitivity measurement: output level step resolution | Systematic error that can be corrected | 0 | 0 | Rectangular | 1.73 | 1 | 0.00 | 0.00 | +| 6 | Measurement distance | $d=1.6\text{m}$ , $\Delta d=0.05\text{m}$ | 0.27 | 0.27 | Rectangular | 1.7 | 1 | 0.16 | 0.16 | +| 7 | Quality of quiet zone | Surface standard deviation of power measurements in ripple test | 0.5 | 0.5 | Actual | 1 | 1 | 0.50 | 0.50 | +| 8 | DUT sensitivity drift | Drift | 0.2 | 0.2 | Rectangular | 1.7 | 1 | 0.12 | 0.12 | +| 9 | Uncertainty related to the use of phantoms | Material Dielectric Constant, Material Conductivity, Geometry/Shape (incl. spacer), Beside Head and Hand | 0.99 | 0.99 | Rectangular | 1.7 | 1 | 0.57 | 0.57 | +| 10 | Coarse sampling grid | Sampling grids per Table B.2.12-1 | 0.1 | 0.18 | Actual | 1 | 1 | 0.1 | 0.18 | +| 11 | Random Uncertainty | Fixed MU to account for all the unknown, unquantifiable, etc. uncertainties including digital error rate | 0.4 | 0.4 | Normal | 2 | 1 | 0.20 | 0.20 | +| 12 | Frequency Response | Included in the output level step resolution | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| Stage 1: Calibration measurement, network analyzer method | | | | | | | | | | +| 13 | Uncertainty of network analyzer | From datasheet of VNA with assessed transmission coefficients | 0.2 | 0.5 | Normal | 2 | 1 | 0.10 | 0.25 | +| 14 | Mismatch of receiver chain | Taken into account in VNA uncertainty term | 0 | 0 | U-shaped | 1.4 | 1 | 0.00 | 0.00 | +| 15 | Insertion loss of receiver chain | Systematic with Stage 2 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 16 | Mismatch in the connection of calibration antenna | Taken in to account in VNA setup uncertainty | 0 | 0 | U-shaped | 1.4 | 1 | 0.00 | 0.00 | +| 17 | Influence of the calibration antenna feed cable | Gain calibration with a dipole | 0.3 | 0.3 | Rectangular | 1.7 | 1 | 0.17 | 0.17 | +| 18 | Influence of the measurement antenna cable | Systematic with Stage 2 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 19 | Uncertainty of the absolute gain/ radiation efficiency of the calibration antenna | Calibration report with traceability to a National Metrology Institute | 0.58 | 0.58 | Normal | 2 | 1 | 0.29 | 0.29 | +| 20 | Measurement distance | Dipole: aligned with phase center | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 21 | Quality of the Quiet Zone | Peak-to-null ripple | 0.5 | 0.5 | Rectangular | 1.7 | 1 | 0.29 | 0.29 | + +| | | | | | | | | | | +|----------------------------------------------------------------------|---------------------------------------|------------|---|---|--------|---|---|-------------|-------------| +| Combined standard uncertainty [dB] | | | | | | | | 1.15 | 1.18 | +| Expanded uncertainty [dB] (Confidence interval of 95 %) | | | | | | | | 2.25 | 2.31 | +| 22 | Systematic Error related to TRS grids | mean error | 0 | 0 | Actual | 1 | 1 | 0.00 | 0.00 | +| Total Expanded uncertainty [dB] (Confidence interval of 95 %) | | | | | | | | 2.25 | 2.31 | + +**Table B.5.1-4: Preliminary example of uncertainty budget for TRS Wrist-Worn device measurement for anechoic chamber method for NR FR1 bands** + +| UID | Uncertainty Source | Comment | Uncertainty Value [dB] | | Prob Distr | Div | ci | Standard Uncertainty [dB] | | +|------------------------------------------------------------------|----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|------------------------|------------|-------------|------|----|---------------------------|------------| +| | | | Below 3GHz | Above 3GHz | | | | Below 3GHz | Above 3GHz | +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Mismatch of receiver chain | $\Gamma_{\text{comm tester}} < 0.29$
$\Gamma_{\text{measurement antenna}} < 0.5$
Cable attenuation > 3dB | 0.22 | 0.22 | U-shaped | 1.4 | 1 | 0.16 | 0.16 | +| 2 | Insertion loss of receiver chain | Systematic with Stage 1 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 3 | Influence of the measurement antenna cable | Systematic with Stage 1 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 4 | Communication Tester: uncertainty of the absolute output level | Manufacturer's data sheet | 1.3 | 1.3 | Normal | 2 | 1 | 0.65 | 0.65 | +| 5 | Sensitivity measurement: output level step resolution | Systematic error that can be corrected | 0 | 0 | Rectangular | 1.73 | 1 | 0.00 | 0.00 | +| 6 | Measurement distance | DUT is not offset for forearm phantom testing | 0 | 0 | Rectangular | 1.7 | 1 | 0 | 0 | +| 7 | Quality of quiet zone | Surface standard deviation of power measurements in ripple test | 0.5 | 0.5 | Actual | 1 | 1 | 0.50 | 0.50 | +| 8 | DUT sensitivity drift | Drift | 0.2 | 0.2 | Rectangular | 1.7 | 1 | 0.12 | 0.12 | +| 9 | Uncertainty related to the use of phantoms | Material Dielectric Constant, Material Conductivity, Geometry/Shape (incl. spacer), Forearm | 0.74 | 0.74 | Rectangular | 1.7 | 1 | 0.43 | 0.43 | +| 10 | Coarse sampling grid | Sampling grids per Table B.2.12-1 | 0.1 | 0.18 | Actual | 1 | 1 | 0.1 | 0.18 | +| 11 | Random Uncertainty | Fixed MU to account for all the unknown, unquantifiable, etc. uncertainties including digital error rate | 0.4 | 0.4 | Normal | 2 | 1 | 0.20 | 0.20 | +| 12 | Frequency Response | Included in the output level step resolution | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| Stage 1: Calibration measurement, network analyzer method | | | | | | | | | | +| 13 | Uncertainty of network analyzer | From datasheet of VNA with assessed transmission coefficients | 0.2 | 0.5 | Normal | 2 | 1 | 0.10 | 0.25 | +| 14 | Mismatch of receiver chain | Taken into account in VNA uncertainty term | 0 | 0 | U-shaped | 1.4 | 1 | 0.00 | 0.00 | +| 15 | Insertion loss of receiver chain | Systematic with Stage 2 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 16 | Mismatch in the connection of calibration antenna | Taken in to account in VNA setup uncertainty | 0 | 0 | U-shaped | 1.4 | 1 | 0.00 | 0.00 | +| 17 | Influence of the calibration antenna feed cable | Gain calibration with a dipole | 0.3 | 0.3 | Rectangular | 1.7 | 1 | 0.17 | 0.17 | +| 18 | Influence of the measurement antenna cable | Systematic with Stage 2 (=> cancels) | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | + +| | | | | | | | | | | +|----------------------------------------------------------------------|-----------------------------------------------------------------------------------|------------------------------------------------------------------------|------|------|-------------|-----|---|-------------|-------------| +| 19 | Uncertainty of the absolute gain/ radiation efficiency of the calibration antenna | Calibration report with traceability to a National Metrology Institute | 0.58 | 0.58 | Normal | 2 | 1 | 0.29 | 0.29 | +| 20 | Measurement distance | Dipole: aligned with phase center | 0 | 0 | Rectangular | 1.7 | 1 | 0.00 | 0.00 | +| 21 | Quality of the Quiet Zone | Peak-to-null ripple | 0.5 | 0.5 | Rectangular | 1.7 | 1 | 0.29 | 0.29 | +| Combined standard uncertainty [dB] | | | | | | | | 1.07 | 1.11 | +| Expanded uncertainty [dB] (Confidence interval of 95 %) | | | | | | | | 2.10 | 2.17 | +| 22 | Systematic Error related to TRS grids | mean error | 0 | 0 | Actual | 1 | 1 | 0.00 | 0.00 | +| Total Expanded uncertainty [dB] (Confidence interval of 95 %) | | | | | | | | 2.10 | 2.17 | + +### B.5.2 MU Assessment for TRS in Reverberation Chamber + +**Table B.5.2-1 Uncertainty contributions in TRS measurement for reverberation chamber method** + +| UID | Description of uncertainty contribution | Details in clause | +|-----------------------------------------|----------------------------------------------------------------------------------|-------------------| +| Stage 2: DUT measurement | | | +| 1 | Mismatch of transmitter chain | B.2.1 | +| 2 | Insertion loss of transmitter chain | B.2.2 | +| 3 | Influence of the measurement antenna cable | B.2.3 | +| 4 | Communication Tester: uncertainty of the absolute output level | B.2.5 | +| 5 | Sensitivity measurement: output level step resolution | B.3.4 | +| 6 | Quality of Spatial Uniformity | B.3.3 | +| 7 | Additional power loss in EUT chassis | B.3.1 | +| 8 | DUT sensitivity drift | B.2.10 | +| 9 | Uncertainty related to the use of phantoms | B.2.11 | +| 10 | Random uncertainty | B.2.13 | +| Stage 1: Calibration measurement | | | +| 11 | Uncertainty of network analyzer | B.2.15 | +| 12 | Mismatch of transmitter chain | B.2.1 | +| 13 | Insertion loss of transmitter chain | B.2.2 | +| 14 | Mismatch in the connection of calibration antenna | B.2.1 | +| 15 | Influence of the calibration antenna feed cable | B.2.3 | +| 16 | Influence of the measurement antenna cable | B.2.3 | +| 17 | Uncertainty of the absolute gain/radiation efficiency of the calibration antenna | B.2.16 | +| 18 | Uniformity of transfer function | B.3.3 | + +**Table B.5.2-2: Preliminary example of uncertainty budget for TRS hand only (browsing mode) measurement for reverberation chamber method for NR FR1 bands** + +| UID | Uncertainty Source | Comment | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] | +|---------------------------------|--------------------|---------|------------------------|------------|-----|----|---------------------------| +| Stage 2: DUT measurement | | | | | | | | + +| | | | | | | | | +|----------------------------------------------------|-------------------------------------------------------------|--------------------------------------------------------------------------------------------------|------|-------------|------|---|--------| +| 1 | Mismatch of transmitter chain | $\Gamma_{\text{comm tester}} < 0.29$
$\Gamma_{\text{meas antenna}} < 0.5$
Cable loss > 3dB | 0.22 | U-shaped | 1.41 | 1 | 0.16 | +| 2 | Insertion loss of transmitter chain | Systematic with Stage 1 (=> cancels) | 0 | Rectangular | 1.73 | 1 | 0 | +| 3 | Influence of the fixed measurement antenna cable | Systematic with Stage 1 (=> cancels) | 0 | Rectangular | 1.73 | 1 | 0 | +| 4 | Communication tester: uncertainty of the absolute level | From datasheet of communication tester | 1.3 | Normal | 2 | 1 | 0.65 | +| 5 | Sensitivity measurement: output level step resolution | Step 0.5dB | 0.25 | Rectangular | 1.73 | 1 | 0.14 | +| 6 | Quality of Spatial Uniformity | Statistics of chamber | 0.5 | Actual | 1 | 1 | 0.5 | +| 7 | Additional power loss in EUT chassis | The EUT not present in the chamber during calibration measurement | 0.2 | Rectangular | 1.73 | 1 | [0.12] | +| 8 | DUT sensitivity drift | Drift measurement | 0.2 | Rectangular | 1.73 | 1 | 0.12 | +| 9 | Uncertainty related to the use of phantoms | Material and Geometry for Data Mode Fixture | 0.64 | Rectangular | 1.73 | 1 | 0.37 | +| 10 | Random Uncertainty | Using the same setup and stirring sequence | 0.4 | Normal | 2 | 1 | 0.2 | +| Stage 1: Calibration measurement | | | | | | | | +| 11 | Uncertainty of network analyzer | Manufacturer's uncertainty calculator, covers NA setup | 0.5 | Normal | 2 | 1 | 0.25 | +| 12 | Mismatch of transmitter chain | Taken in to account in NA setup uncertainty | 0 | U-shaped | 1.41 | 1 | 0 | +| 13 | Insertion loss of transmitter chain | Systematic with Stage 2 (=> cancels) | 0 | Rectangular | 1.73 | 1 | 0 | +| 14 | Mismatch in the connection of calibration antenna | Taken in to account in NA setup uncertainty | 0 | U-shaped | 1.73 | 1 | 0 | +| 15 | Influence of the feed cable of the calibration antenna | Gain calibration with dipole | 0.3 | Rectangular | 1.73 | 1 | 0.17 | +| 16 | Influence of the fixed measurement antenna cable | Systematic with Stage 2 (=> cancels) | 0 | Rectangular | 1.73 | 1 | 0 | +| 17 | Uncertainty of the absolute gain of the calibration antenna | Calibration certificate | 0.58 | Normal | 2 | 1 | [0.29] | +| 18 | Uniformity of transfer function | Statistics of chamber | 0.5 | Actual | 1 | 1 | 0.5 | +| Combined standard uncertainty | | $u_c = \sqrt{\sum_{i=1}^m c_i^2 \cdot u_i^2}$ | | | | | [1.16] | +| Expanded uncertainty (Confidence interval of 95 %) | | $u_e = 1,96 u_c$ | | | | | [2.28] | + +**Table B.5.2-2: Preliminary example of uncertainty budget for TRS Beside Head and Hand (Talk mode) measurement for reverberation chamber method for NR FR1 bands** + +| UID | Uncertainty Source | Comment | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] | +|----------------------------------------------------|-------------------------------------------------------------|-------------------------------------------------------------------------------------------------|------------------------|-------------|------|----|---------------------------| +| Stage 2: DUT measurement | | | | | | | | +| 1 | Mismatch of transmitter chain | $\Gamma_{\text{comm tester}} < 0.29$
$\Gamma_{\text{meas antenna}} < 0.5$
Cable loss >3dB | 0.22 | U-shaped | 1.41 | 1 | 0.16 | +| 2 | Insertion loss of transmitter chain | Systematic with Stage 1 (=> cancels) | 0 | Rectangular | 1.73 | 1 | 0 | +| 3 | Influence of the fixed measurement antenna cable | Systematic with Stage 1 (=> cancels) | 0 | Rectangular | 1.73 | 1 | 0 | +| 5 | Communication tester: uncertainty of the absolute level | Manufacturer's data sheet | 1.3 | Normal | 2 | 1 | 0.65 | +| 6 | Sens. measurement: output level step resolution | Step 0.5dB | 0.25 | Rectangular | 1.73 | 1 | 0.14 | +| 6 | Quality of Spatial Uniformity | Statistics of chamber | 0.5 | Actual | 1 | 1 | 0.5 | +| 7 | Additional power loss in EUT chassis | The EUT not present in the chamber during calibration measurement | 0.2 | Rectangular | 1.73 | 1 | [0.12] | +| 8 | DUT sensitivity drift | Drift measurement | 0.2 | Rectangular | 1.73 | 1 | 0.12 | +| 9 | Uncertainty related to the use of phantoms | Material and Geometry for Data Mode Fixture | 0.99 | Rectangular | 1.73 | 1 | 0.57 | +| 10 | Random Uncertainty | Using the same setup and stirring sequence | 0.4 | Normal | 2 | 1 | 0.20 | +| Stage 1: Calibration measurement | | | | | | | | +| 11 | Uncertainty of network analyzer | Manufacturer's uncertainty calculator, covers NA setup | 0.5 | Normal | 2 | 1 | 0.25 | +| 12 | Mismatch of transmitter chain | Taken in to account in NA setup uncertainty | 0 | U-shaped | 1.41 | 1 | 0 | +| 13 | Insertion loss of transmitter chain | Systematic with Stage 1 (=> cancels) | 0 | Rectangular | 1.73 | 1 | 0 | +| 14 | Mismatch in the connection of calibration antenna | Taken in to account in NA setup uncertainty | 0 | Rectangular | 1.73 | 1 | 0 | +| 15 | Influence of the feed cable of the calibration antenna | Gain calibration with dipole | 0.3 | Rectangular | 1.73 | 1 | 0.17 | +| 16 | Influence of the fixed measurement antenna cable | Systematic with Stage 1 (=> cancels) | 0 | Rectangular | 1.73 | 1 | 0 | +| 17 | Uncertainty of the absolute gain of the calibration antenna | Calibration certificate | [0.58] | Normal | 2 | 1 | [0.29] | +| 18 | Quality of Spatial Uniformity | Statistics of chamber | 0.5 | Gaussian | 1 | 1 | 0.5 | +| Combined standard uncertainty | | $u_c = \sqrt{\sum_{i=1}^m c_i^2 \cdot u_i^2}$ | | | | | [1.24] | +| Expanded uncertainty (Confidence interval of 95 %) | | $u_e = 1.96 u_c$ | | | | | [2.43] | + + + +# --- Annex C: Environmental requirements + +## C.1 Scope + +The requirements in this clause apply to all types of UE(s) in FR1 for SA and EN-DC mode. + +## --- C.2 Ambient temperature + +All the test cases defined in this technical report should be measured in room temperature e.g. 18°C - 28°C. + +## --- C.3 Operating voltage + +For FR1 TRP TRS, test cases shall be performed with the DUT operated in stand-alone battery powered mode. It is preferable if the UE is fully charged in the beginning of the test. + +# --- Annex D: Phantom Definition + +## D.1 Head Phantom + +The basic head phantom is based on the “SAM” head phantom in IEEE Std 1528-2003, which is also described in TS 37.544 Annex A.2 [17]. For TRP TRS test, the IEEE SAM head model has been extended with the neck region, which is specified in CTIA Certification OTA Test Plan [14]. + +The Head phantom defined in CTIA Certification OTA Test Plan section C.2 [14], is used for FR1 TRP TRS testing in this technical report. + +![Figure D.1-1: Three views of the Head Phantom. The left view shows the front of the head with a vertical white stripe down the center. The middle view shows the head in profile, facing left. The right view shows the back of the head with a vertical white stripe down the center. The head is blue, and the neck is yellow.](f01b22e5bb303653828200595aece414_img.jpg) + +Figure D.1-1: Three views of the Head Phantom. The left view shows the front of the head with a vertical white stripe down the center. The middle view shows the head in profile, facing left. The right view shows the back of the head with a vertical white stripe down the center. The head is blue, and the neck is yellow. + +**Figure D.1-1 Head Phantom (© 2001 – 2022 CTIA Certification. Reproduced with permission.), defined in the CTIA Certification OTA Test Plan** + +## --- D.2 Hand Phantom + +### D.2.1 PDA Grip Hand + +The PDA Grip Hand described in TS 37.544 Annex A.2.2 [17], which is identical to that defined in CTIA Certification OTA Test Plan section C.4.8 [14], is adopted for TRP TRS testing for the UE with width $\geq 56\text{mm}$ and $\leq 72\text{mm}$ . + +### D.2.2 Wide Grip Hand + +The Wide Grip hand defined in CTIA Certification OTA Test Plan section C.4.9 [14], is used for FR1 TRP TRS testing for UE with Width $> 72\text{mm}$ and $\leq 92\text{mm}$ in this technical report. + +![Two grey 3D models of a wide grip hand, shown from the palm and back perspectives.](c37fe03d7cad74ad675a0eb16aa43821_img.jpg) + +Two grey 3D models of a wide grip hand, shown from the palm and back perspectives. + +Figure D.2.2-1 Wide Grip hand (© 2001 – 2022 CTIA Certification. Reproduced with permission.), defined in the CTIA Certification OTA Test Plan + +## D.3 Forearm Phantom + +The Forearm phantom defined in CTIA Certification OTA Test Plan 01.72 section 2.3 [25], is used for FR1 TRP TRS testing for wrist-worn RedCap UE in this technical report. + +![Diagram of a forearm phantom showing its cylindrical and conical sections, with labels for target test positions and perimeters.](e8ff6e66c77a8e96203c9f8db8f0986f_img.jpg) + +The diagram illustrates a forearm phantom with the following components and measurements: + +- Cylindrical Section (100 mm):** The top portion of the phantom. It has a **Cylindrical Perimeter: 144.0 mm**. +- Target Test Position:** A specific location on the cylindrical section, marked by a green circle. The **Test Position Perimeter: 162.7 mm**. +- Conical Section (215 mm):** The bottom portion of the phantom, which tapers down to the base. The **Base Perimeter: 224.5 mm**. + +Diagram of a forearm phantom showing its cylindrical and conical sections, with labels for target test positions and perimeters. + +Figure D.3-1: Forearm Phantom with Target Test Position (© 2001 – 2022 CTIA Certification. Reproduced with permission.), defined in the CTIA Certification OTA Test Plan + +# --- Annex E: + +## Harmonization outcome of Alternative method and Reference method + +< Editor's note: Detailed structure of the subclause is TBD. + +Framework, pass/fail limits, and final conclusions> + +# --- Annex F: Lab alignment outcome of Reference method + +< Editor's note: Detailed structure of the subclause is TBD. Framework, pass/fail limits, and final conclusions> + +## --- F.1 General + +This clause records the lab alignment activity of AC test method. The purpose of lab alignment campaign is to ensure there is no unexpected lab deviation and establish full trust and confidence on the measurement results, which is an essential action to define TRP TRS requirements based on measurement data. + +The test campaign is performed among volunteered test labs those are accredited under ISO 17025 (ISO 17025 accredited labs) and have any of 3GPP TS 37.544, CCSA YD/T 1484, and CTIA OTA Test Plan listed on its accreditation scope. + +## --- F.2 Rel-17 lab alignment campaign (Browsing mode) + +### F.2.1 Framework and workplan + +This clause defines the working procedure on how to proceed the lab alignment campaign in Rel-17. The purpose of Lab Alignment Campaign is to ensure there is no unexpected lab deviation and establish full trust and confidence on the results. + +Test labs are invited to participate to the lab alignment and test campaign, the following conditions should be fulfilled: + +- Participating lab should be accredited under ISO 17025 (ISO 17025 accredited labs) and have any of 3GPP TS 37.544, CCSA YD/T 1484.6, and CTIA OTA Test Plan listed on its accreditation scope. +- Participating lab should have anechoic chamber(s) ready to support testing based on 3GPP TR 38.834. Participating lab should have sufficient test resource to provide the on-time measurement results without delay. +- Other test methodology besides the methodology captured in existing TR 38.834 is not precluded and can be considered as long as it can meet the endorsed timeline based on the input from companies. + +Test methodology: + +- Test plan: 3GPP TR 38.834; + +Test cases for Lab Alignment Campaign: + +- Test bands: n41 and n78; +- Number of test cases: maximum 3 devices per-band +- Use scenario: Hand phantom only (Browsing mode), i.e., Hand Left and Hand Right +- Hand Phantom: Corresponding phantom depends on UE size +- Operation mode: NR Standalone (SA) + +Lab Alignment Device (LAD) selection criteria: + +- Smartphone DUT size: two sizes, both width >72mm and $\leq$ 92mm, and width $\geq$ 56mm and $\leq$ 72mm; +- DUT capability: support for all the Bands n41, n28, n78, and n79 those listed in the WID is preferred, but devices supporting only a subset of the above bands can equally be used in the lab alignment campaign. +- Intended for which market: no limitation + +- Tx Antenna switching: if the DUT support TAS, the LAD provider should also provide the software/method to lock the UE primary antenna, or the primary antenna has already been locked before submitting to test lab and kept unchanged during whole alignment campaign +- Power Class: PC2 (n41 and n78) +- TxD is not allowed +- For LAD selection: all application will be first come first served; +- For each device, all the supported bands information should be shared + +#### Test results submitting: + +- Using the same worksheet template in R4-2207327 to submit the measurement results +- The measurement results should be submitted to RAN4 by anonymous approach (the UE model should not be disclosed) +- Results shall not be shared between labs before submitting to RAN4 meetings or sharing in the RAN4 reflector. Comparison and lab alignment analysis should only be done in RAN4 meetings/discussions + +#### Lab alignment criteria: + +- The pass/fail criteria are defined as the maximum deviation between the measurement result and the reference value +- Confirm the reference value derived based on the per-band per-PC averaging approach (linear average with dBm) of lab alignment data pool from $\geq 3$ labs submitted before 16th May 2022 as baseline. +- If the unfinished volunteer labs submit LAD measurement results before RAN4#104 meeting and the results are not identified as apparent outliers, consider to update the reference values as the average of the LAD measurement results from all the labs. +- RAN4 allows the unfinished volunteer labs to submit LAD measurement results after RAN4#103-e meeting, before RAN4#104-e meeting. +- Labs who submitted data to RAN4#103-e are confirmed as the aligned labs according to the currently agreed reference values and pass/fail limits. +- Apparent outliers will not be considered in averaging process. The value deviates over $1.5 \cdot \text{MU}$ from all the other lab's results should be identified as apparent outlier. +- Pass/fail limit for lab alignment should be defined as $\pm 0.75 \cdot \text{MU}$ (i.e., 1.34dB for TRP, and 1.65dB for TRS) as baseline. MU value is the expanded MU in TR38.834, i.e., 1.78dB for TRP and 2.20dB for TRS. +- The pass/fail limit and reference value shall be considered together if further update identified based on more data input +- The summation form for TRP and TRS lab alignment should keep consistent during the calculation process of TRP TRS lab alignment from each company, i.e., $\sin\theta \cdot \Delta\theta$ weights approach or Clenshaw-Curtis quadrature integral approximation. Only traditional approach should be used during lab alignment activity to reduce unnecessary uncertainty. +- How to treat late submission results and confirm the alignment: + - The reference value and pass/fail limit should be defined in RAN4#103-e meeting. The late submission deadline for phase 2 is Tdoc submission deadline of RAN4#104-e meeting. + - An offline RAN4 conference call may be needed to review lab alignment data to tentatively confirm the pass or fail of late-submitted labs. Final endorsement will happen during RAN4#104e. + - Only measurement results from aligned labs in RAN4#104-e meeting are considered as TRP TRS Performance data pool to define final requirements. + +#### Test lab procedures: + +- LAD delivery scheme + - Decide LAD delivery scheme after all the test lab and LAD information being confirmed. + - The available LADs can be split among labs to multiplex the testing effort +- LAD measurement time in each test lab: finalize LAD measurement within 5 workdays, and deliver to next lab ASAP with LAD delivery In/Out information shared in reflector. +- Encourage test labs to share resulting combined MU based on their own systems + +### F.2.2 Measurement results + +Considering the test burden and urgent timeline, RAN4 decided to select two smartphones (named as LADs, Lab Alignment Devices) as reference DUTs to perform Rel-17 AC lab alignment activity. The devices' size belongs to width $>72\text{mm}$ and $\leq 92\text{mm}$ . + +In Rel-17, the lab alignment campaign is focused on Browsing mode (Hand phantoms only) at band n41 and n78. There are 8 test labs participate the lab alignment campaign, the reference value is derived based on linear average (with dBm) of all the 8 labs results. The summary of the lab alignment analysis outcome is shown in Figure F.2.2-1 for TRP, and Figure F.2.2-2 for TRS. + +![Figure F.2.2-1: NR FR1 TRP lab alignment analysis, deviation between each test lab and reference value. The chart shows TRP offset (dB) for four categories: LAD1, n41; LAD1, n78; LAD2, n41; and LAD2, n78. The y-axis ranges from -1.78 to 1.72 dB. The x-axis lists eight labs (Lab1 to Lab8). Data values are shown above each bar.](c222a9006d6d60a8d81e6ffbfc0e74ad_img.jpg) + +| Category | Lab1 | Lab2 | Lab3 | Lab4 | Lab5 | Lab6 | Lab7 | Lab8 | +|-----------|------|-------|-------|-------|-------|-------|-------|-------| +| LAD1, n41 | 0.10 | 0.25 | -0.07 | 0.14 | -0.46 | 0.44 | 0.14 | -0.55 | +| LAD1, n78 | 0.17 | -0.56 | 0.37 | 0.43 | -0.21 | -0.21 | -0.21 | 0.46 | +| LAD2, n41 | 0.40 | -0.16 | -0.16 | -0.16 | 0.30 | 0.26 | 0.67 | 1.08 | +| LAD2, n78 | 0.43 | -0.81 | -0.48 | 0.16 | 0.69 | 0.05 | -0.51 | 0.47 | + +Figure F.2.2-1: NR FR1 TRP lab alignment analysis, deviation between each test lab and reference value. The chart shows TRP offset (dB) for four categories: LAD1, n41; LAD1, n78; LAD2, n41; and LAD2, n78. The y-axis ranges from -1.78 to 1.72 dB. The x-axis lists eight labs (Lab1 to Lab8). Data values are shown above each bar. + +Figure F.2.2-1: NR FR1 TRP lab alignment analysis, deviation between each test lab and reference value + +![Figure F.2.2-2: NR FR1 TRS lab alignment analysis, deviation between each test lab and reference value. The chart shows TRS offset (dB) for four categories: LAD1, n41; LAD1, n78; LAD2, n41; and LAD2, n78. The y-axis ranges from -2.00 to 2.00 dB. The x-axis lists eight labs (Lab1 to Lab8). Data values are shown above each bar.](9d1abc573e35610946ece87a18cbe862_img.jpg) + +| Category | Lab1 | Lab2 | Lab3 | Lab4 | Lab5 | Lab6 | Lab7 | Lab8 | +|-----------|-------|-------|-------|------|------|-------|------|------| +| LAD1, n41 | -0.28 | -0.93 | -0.32 | 0.10 | 0.92 | -0.39 | 0.27 | 0.78 | +| LAD1, n78 | 0.04 | -0.36 | -0.89 | 0.03 | 0.27 | -0.07 | 0.36 | 0.53 | +| LAD2, n41 | -0.38 | -0.64 | -0.11 | 0.05 | 0.53 | 0.33 | 0.11 | 0.84 | +| LAD2, n78 | -0.17 | 0.40 | 0.14 | 0.44 | 0.14 | -0.22 | 0.40 | 0.55 | + +Figure F.2.2-2: NR FR1 TRS lab alignment analysis, deviation between each test lab and reference value. The chart shows TRS offset (dB) for four categories: LAD1, n41; LAD1, n78; LAD2, n41; and LAD2, n78. The y-axis ranges from -2.00 to 2.00 dB. The x-axis lists eight labs (Lab1 to Lab8). Data values are shown above each bar. + +Figure F.2.2-2: NR FR1 TRS lab alignment analysis, deviation between each test lab and reference value + +The maximum deviation between test labs and reference value is 1.08dB for TRP and 0.93dB for TRS. + +### F.2.3 Pass/fail limit + +Based on the preliminary MU assessment of AC test method with browsing mode in Annex B, and lab alignment measurement results in Annex F.2.2, RAN4 decided the final pass/fail limits for Rel-17 FR1 TRP TRS lab alignment activity (Browsing mode) as following: + +- TRP: 1.2 dB +- TRS: 1.5 dB + +### F.2.4 Conclusions + +RAN4 conclude the successful Rel-17 FR1 TRP TRS lab alignment activity, all the 8 test labs with anechoic chamber system are well aligned. Rel-17 TRP TRS requirements are specified based on the measurement results submitted by above aligned test labs. + +## --- F.3 Rel-18 lab alignment (Talk mode) + +< Editor's note: Detailed structure of the subclause is TBD. Framework, pass/fail limits, and final conclusions> + +### F.3.1 Framework and workplan + +### F.3.2 Measurement results + +### F.3.3 Pass/fail limit + +### F.3.4 Conclusions + +# Annex G (informative): Change history + +| Change history | | | | | | | | | +|----------------|---------------|------------|----|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2022-10 | RAN4#104bis-e | R4-2216104 | | | | Initial Skeleton | | 0.0.1 | +| 2022-11 | RAN4#105 | R4-2218845 | | | | R4-2218850 TP to TR 38.870 on supplement of basic AC test method | | 0.1.0 | +| 2023-03 | RAN4#106 | R4-2301555 | | | | R4-2301556 TP to TR 38.870 on RedCap OTA test parameters
R4-2302983 TP to TR 38.870 Reverberation Chamber Method (Alternate Method)
R4-2302498 TP to TR 38.870 on contents for Annex B | | 0.2.0 | +| 2023-04 | RAN4#106bis-e | R4-2305102 | | | | R4-2304034 Text proposal for Annex C on environment in TR 38.870
R4-2305908 TP to TR 38.870 on General parts
R4-2305785 TP on Test reductions with Measurement Grids | | 0.3.0 | +| 2023-05 | RAN4#107 | R4-2308250 | | | | R4-2308251 TP to TR 38.870 on supplement of coordinate system and phantom definition
R4-2309814 TP for CBW and spatial uniformity test procedures in TR38.870
R4-2308824 TP on Measurement Uncertainty Associated with Grid Size
R4-2309289 TP to TR 38.870 on contents for Annex B | | 0.4.0 | +| 2023-08 | RAN4#108 | R4-2312565 | | | | R4-2311673 TP to TR 38.870 on contents for Annex B
R4-2313988 TP to TR 38.870 on AC lab alignment campaign | | 0.5.0 | +| 2023-10 | RAN4#108bis | R4-2315838 | | | | R4-2315839 TP to TR 38.870 on phantoms
R4-2317003 TP to TR 38.870 on 2Tx test configuration | | 0.6.0 | +| 2023-11 | RAN4#109 | R4-2318965 | | | | R4-2321097 TP to TR 38.870 on TRP TRS test procedure for CA
R4-2321098 TP to TR 38.870 on TRP TRS test method
R4-2320707 TP to TR 38.870 on contents for Annex B | | 0.7.0 | +| 2023-12 | RAN#102 | RP-233136 | | | | For one-step approval | | 1.0.0 | +| 2023-12 | RAN#102 | RP-234063 | | | | Approved with additional editor note | | 1.1.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/38_series/38871/082ba09313df59d76a7bfbdde8ec877d_img.jpg b/marked/Rel-18/38_series/38871/082ba09313df59d76a7bfbdde8ec877d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57ba83ca398e151e9d7d3407e8425fc330cba6b3 --- /dev/null +++ b/marked/Rel-18/38_series/38871/082ba09313df59d76a7bfbdde8ec877d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45efe6e8097abefc218888c89d6bba787522753472763d9de0aa116cb4b15408 +size 67620 diff --git a/marked/Rel-18/38_series/38871/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-18/38_series/38871/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa2963a88987cc24e9d3a92f4dff55847289eb2b --- /dev/null +++ b/marked/Rel-18/38_series/38871/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:605a1c0afb1bb61d77c040e339f82eccfc1f7e57abd717d4e098ac71824732f3 +size 189086 diff --git a/marked/Rel-18/38_series/38871/093f97b6685d6756d2075a48d0a213e4_img.jpg b/marked/Rel-18/38_series/38871/093f97b6685d6756d2075a48d0a213e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..482fe614dbc7c77075c8c4ab0d0f8bff834702e9 --- /dev/null +++ b/marked/Rel-18/38_series/38871/093f97b6685d6756d2075a48d0a213e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4462682e7f7b6a53d1295177f7d8daa5fa7d22284dab58b672784c5714add112 +size 27449 diff --git a/marked/Rel-18/38_series/38871/09b5a76dd3d981abcc585df1314ef30a_img.jpg b/marked/Rel-18/38_series/38871/09b5a76dd3d981abcc585df1314ef30a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..abf357aaf5b8806583e910058a7a76e2ec7ba330 --- /dev/null +++ b/marked/Rel-18/38_series/38871/09b5a76dd3d981abcc585df1314ef30a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:352af43ce930396c314957a173ffc08b97007639da45f33ea7317e1a77d02b37 +size 37672 diff --git a/marked/Rel-18/38_series/38871/0c071a254cbc109c9ebce80487b4771b_img.jpg b/marked/Rel-18/38_series/38871/0c071a254cbc109c9ebce80487b4771b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6147b230793985a4fd1f0cda84ff5a9f223ffa58 --- /dev/null +++ b/marked/Rel-18/38_series/38871/0c071a254cbc109c9ebce80487b4771b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:030626508775b2186401e79bfea924169916904bb32fae8ed62cfcf89aa345df +size 25985 diff --git a/marked/Rel-18/38_series/38871/0cc86fe8fc37b0edc9581f2af9459a52_img.jpg b/marked/Rel-18/38_series/38871/0cc86fe8fc37b0edc9581f2af9459a52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74868990f5f58efed263f3ba733dded7775494a8 --- /dev/null +++ b/marked/Rel-18/38_series/38871/0cc86fe8fc37b0edc9581f2af9459a52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0ce9c5dfa97b20a6fed81b6b304dbe99d9f895cbacee2b2733b447354991551 +size 48043 diff --git a/marked/Rel-18/38_series/38871/0e240e8e4783e664047fbdb5fbd0989f_img.jpg b/marked/Rel-18/38_series/38871/0e240e8e4783e664047fbdb5fbd0989f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67771fdfa8c23b1a475dced664b8fe59895649fa --- /dev/null +++ b/marked/Rel-18/38_series/38871/0e240e8e4783e664047fbdb5fbd0989f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7849d2e59b0e955ae34b7fb06f5b1b1826462a84c4e3023ddae8bd17a2e94049 +size 27244 diff --git a/marked/Rel-18/38_series/38871/0efd769159aa06ce93313589cb93a3e0_img.jpg b/marked/Rel-18/38_series/38871/0efd769159aa06ce93313589cb93a3e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f65b30a8f55dc180bbdf7bb6d76c83f5d2877f02 --- /dev/null +++ b/marked/Rel-18/38_series/38871/0efd769159aa06ce93313589cb93a3e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82d000315246c9b816f78a12adfc56b936a107531b004be12fc4867330cb36b7 +size 38058 diff --git a/marked/Rel-18/38_series/38871/10953d657a5f47fdc829a800419dd370_img.jpg b/marked/Rel-18/38_series/38871/10953d657a5f47fdc829a800419dd370_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8843c1bb8422e599b2654acabdce04631db40228 --- /dev/null +++ b/marked/Rel-18/38_series/38871/10953d657a5f47fdc829a800419dd370_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9546c7f77a9e202bf0da417e5eefeb7ed76a988e44dd2483991e2679c3a2d271 +size 51100 diff --git a/marked/Rel-18/38_series/38871/1206a763f1e8da1c0441b3038cd8e88e_img.jpg b/marked/Rel-18/38_series/38871/1206a763f1e8da1c0441b3038cd8e88e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..381d7fd83ca63113779095e2ede50560a9b0303c --- /dev/null +++ b/marked/Rel-18/38_series/38871/1206a763f1e8da1c0441b3038cd8e88e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d319a71957993cbb0199ea189cce19c8b848a318fb4f1d99d3220d179ce37a2a +size 29636 diff --git a/marked/Rel-18/38_series/38871/125ef125614b4b91492f53d1858b74ce_img.jpg b/marked/Rel-18/38_series/38871/125ef125614b4b91492f53d1858b74ce_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1606e34ae3a5e7f90315edd716a875345d378398 --- /dev/null +++ b/marked/Rel-18/38_series/38871/125ef125614b4b91492f53d1858b74ce_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd393aae81cc7a83a1f32a00d05a6beb754a1f5aef4da4964b96b2d4b3d541e0 +size 37472 diff --git a/marked/Rel-18/38_series/38871/12c70b02d26d278557ab2e4864b837b2_img.jpg b/marked/Rel-18/38_series/38871/12c70b02d26d278557ab2e4864b837b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91ae7331c74cde15855e349391593816b27f7ed3 --- /dev/null +++ b/marked/Rel-18/38_series/38871/12c70b02d26d278557ab2e4864b837b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c92396baa45cf11dabebb0d30d691158782cf5a0bbb2c300bacae0c5939519a3 +size 25661 diff --git a/marked/Rel-18/38_series/38871/134b09b4aa4798c16559fe003bc1f63d_img.jpg b/marked/Rel-18/38_series/38871/134b09b4aa4798c16559fe003bc1f63d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0faee86e29bae8bcd67d79dc4cfaab16ef7cac33 --- /dev/null +++ b/marked/Rel-18/38_series/38871/134b09b4aa4798c16559fe003bc1f63d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d178b5ed9768d8a07bf715ec7eff4ce5620b6c4c11182fdb9a71a573bbdb4154 +size 33842 diff --git a/marked/Rel-18/38_series/38871/16cbfa79e7755f9abad5d7d1aa8019c1_img.jpg b/marked/Rel-18/38_series/38871/16cbfa79e7755f9abad5d7d1aa8019c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97cbd9d79868a3d153bd0d50c5c89f19215fa564 --- /dev/null +++ b/marked/Rel-18/38_series/38871/16cbfa79e7755f9abad5d7d1aa8019c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:925cb86c421bf335040084de85a205220c8b970d1d05f24905ab795128219d53 +size 50138 diff --git a/marked/Rel-18/38_series/38871/18bb06865e2dada3656ea3d57f290f7f_img.jpg b/marked/Rel-18/38_series/38871/18bb06865e2dada3656ea3d57f290f7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82cc4d373f897cb97c6480b88ebdb7c1dee36b42 --- /dev/null +++ b/marked/Rel-18/38_series/38871/18bb06865e2dada3656ea3d57f290f7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a06123887d818ac59d9195f40cd454c99a5b2f403b0f08fe969b7c2bc78f8c2 +size 17839 diff --git a/marked/Rel-18/38_series/38871/1a830f2a9a6d7451ab3ef9dc5f3dc001_img.jpg b/marked/Rel-18/38_series/38871/1a830f2a9a6d7451ab3ef9dc5f3dc001_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6127af9c70d746b0e41e5cab63406b13d8d73a6 --- /dev/null +++ b/marked/Rel-18/38_series/38871/1a830f2a9a6d7451ab3ef9dc5f3dc001_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a302b29810807669ff11582555e0347f19220dd3606f360aab73c22e25e5e882 +size 29645 diff --git a/marked/Rel-18/38_series/38871/1cb2f5dadf873c9a8a796588472710ef_img.jpg b/marked/Rel-18/38_series/38871/1cb2f5dadf873c9a8a796588472710ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f6457cde3575b90cdf0fec08b85c74312ab26f5 --- /dev/null +++ b/marked/Rel-18/38_series/38871/1cb2f5dadf873c9a8a796588472710ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6d0e764c97ca711f0bc95f1f18bbb0aeb568059d5b037f3526bb9919ac14641 +size 13573 diff --git a/marked/Rel-18/38_series/38871/201de44da5d99899a8cf58eac2fa7bc9_img.jpg b/marked/Rel-18/38_series/38871/201de44da5d99899a8cf58eac2fa7bc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32b70f6bb896887af59e01899f07f7974a0cb968 --- /dev/null +++ b/marked/Rel-18/38_series/38871/201de44da5d99899a8cf58eac2fa7bc9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7a8591ddbd7163936709adf0b38c02e273d55ee4b4f8e7c2643edf96bfd0a9b +size 238123 diff --git a/marked/Rel-18/38_series/38871/238c4829f8c2af6f920376617823b5b3_img.jpg b/marked/Rel-18/38_series/38871/238c4829f8c2af6f920376617823b5b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..caa2f8f552366a404ad4d3dad9f9cc5a45dcf8d9 --- /dev/null +++ b/marked/Rel-18/38_series/38871/238c4829f8c2af6f920376617823b5b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8cb20ca55fa97b764d80c63bf75a35f12558b7d7cf6dcceaf4e6ee10ac594c0d +size 59012 diff --git a/marked/Rel-18/38_series/38871/2452dbf3f1497ea958d60461703cc78a_img.jpg b/marked/Rel-18/38_series/38871/2452dbf3f1497ea958d60461703cc78a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4aa36a2f2a6ae299c168d3dbdd486c38025f03d3 --- /dev/null +++ b/marked/Rel-18/38_series/38871/2452dbf3f1497ea958d60461703cc78a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3bbc50469354529cb881b216b2dffe2b231501386c80a1ebc6cd5cf1d914343b +size 26983 diff --git a/marked/Rel-18/38_series/38871/24e93ddbd7313e03d70f4a426b213b9a_img.jpg b/marked/Rel-18/38_series/38871/24e93ddbd7313e03d70f4a426b213b9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39f1b103bf41a7e6051466d9ea5ec064ec10bd11 --- /dev/null +++ b/marked/Rel-18/38_series/38871/24e93ddbd7313e03d70f4a426b213b9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d95c982da648ed1d2016273f006ad340777a6ef42e2311fe30b914fa12e34379 +size 38295 diff --git a/marked/Rel-18/38_series/38871/24fd04245a3e87988420890cf311efc3_img.jpg b/marked/Rel-18/38_series/38871/24fd04245a3e87988420890cf311efc3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e18425bbbe5291b76a67dbf70f15a897abddb63 --- /dev/null +++ b/marked/Rel-18/38_series/38871/24fd04245a3e87988420890cf311efc3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a70eebd1eead87f69d50ec02e9635f90b783ac8d7b9f1d15e8936251d6eddcba +size 31736 diff --git a/marked/Rel-18/38_series/38871/275bb6a5a05beffc7108e295d4a221cd_img.jpg b/marked/Rel-18/38_series/38871/275bb6a5a05beffc7108e295d4a221cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08b0e6d4858fddb7da9442e3149c9ce402bf0f6c --- /dev/null +++ b/marked/Rel-18/38_series/38871/275bb6a5a05beffc7108e295d4a221cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d510168f9095d7457576f2f2fefc9ac4ab5ad6d5c53e158e351f8f4570de47c +size 27668 diff --git a/marked/Rel-18/38_series/38871/289089f4ae6873c72463afac5196de88_img.jpg b/marked/Rel-18/38_series/38871/289089f4ae6873c72463afac5196de88_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ddb104135c35eb741a6b9f0df25e42724d835ee --- /dev/null +++ b/marked/Rel-18/38_series/38871/289089f4ae6873c72463afac5196de88_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a579eba426e65fa43a3492b954af973295caa7b8625b63171ce38aa70043a2b5 +size 65322 diff --git a/marked/Rel-18/38_series/38871/2ae3ba8881a93c447741bdc95f18580a_img.jpg b/marked/Rel-18/38_series/38871/2ae3ba8881a93c447741bdc95f18580a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ef7ff57196a4eeb673a95e572859ed932e1409c --- /dev/null +++ b/marked/Rel-18/38_series/38871/2ae3ba8881a93c447741bdc95f18580a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9dfc2580e3ff642db57e71c380d741ef210a79aa7f81f06804a949430b525aa4 +size 51787 diff --git a/marked/Rel-18/38_series/38871/2aeb2e98986fac7c66e17a4e6afbe5c0_img.jpg b/marked/Rel-18/38_series/38871/2aeb2e98986fac7c66e17a4e6afbe5c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a68ceaf79a9c31075f1479ba38cf8e7631c1601c --- /dev/null +++ b/marked/Rel-18/38_series/38871/2aeb2e98986fac7c66e17a4e6afbe5c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d6b6a2c79b50dc570a24d5f29383d2ea21339c7bb4753776d41d751f27d998e +size 49468 diff --git a/marked/Rel-18/38_series/38871/2b7a5220e76abf6238c90ba6611a4c51_img.jpg b/marked/Rel-18/38_series/38871/2b7a5220e76abf6238c90ba6611a4c51_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4722e462adfcf6a1ef4e7251813f3ffcaf81ebe --- /dev/null +++ b/marked/Rel-18/38_series/38871/2b7a5220e76abf6238c90ba6611a4c51_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74f55a24341d8edb7776173b460de8a65c072cedb09ce486f0fb79ae5014b264 +size 25823 diff --git a/marked/Rel-18/38_series/38871/2de51a31da9b0ffd9d017f035d498997_img.jpg b/marked/Rel-18/38_series/38871/2de51a31da9b0ffd9d017f035d498997_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80526ffc1c3515d11e294838150401fa44dbbb39 --- /dev/null +++ b/marked/Rel-18/38_series/38871/2de51a31da9b0ffd9d017f035d498997_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6afac68c4f96ab6316ff23476fc87bb0c5769a4a3db3d694f52039318ae0c982 +size 49879 diff --git a/marked/Rel-18/38_series/38871/312b7c422177272f4e4e810eb4c4ad87_img.jpg b/marked/Rel-18/38_series/38871/312b7c422177272f4e4e810eb4c4ad87_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7816664ca84e998c19f1b3a2632e7399752b4632 --- /dev/null +++ b/marked/Rel-18/38_series/38871/312b7c422177272f4e4e810eb4c4ad87_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3e578b447eb9eb3945357bc0c9f67c184bfddaae28404e1383a31ceb491dd13 +size 45601 diff --git a/marked/Rel-18/38_series/38871/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Rel-18/38_series/38871/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..baeb0eb01e01c060f93800cf761fe834b594de09 --- /dev/null +++ b/marked/Rel-18/38_series/38871/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be05ad63e62ff66f3335ead36665543abbd26b0ad92738ec75c362e833133829 +size 17141 diff --git a/marked/Rel-18/38_series/38871/3293245c6893d9d49c2c878828423ecd_img.jpg b/marked/Rel-18/38_series/38871/3293245c6893d9d49c2c878828423ecd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0dd63ff51e225b8b8758f2aeed6503cd4b9793fb --- /dev/null +++ b/marked/Rel-18/38_series/38871/3293245c6893d9d49c2c878828423ecd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f0f4d062704d7cd978a6530ef8c547cf6eb25eb1bef55ee65b6c242d229b56e +size 29287 diff --git a/marked/Rel-18/38_series/38871/33fcd48ebd2456ea5e49fade0d4c7f75_img.jpg b/marked/Rel-18/38_series/38871/33fcd48ebd2456ea5e49fade0d4c7f75_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe8966a627b4bfd489147093c11bd2bd46c10d14 --- /dev/null +++ b/marked/Rel-18/38_series/38871/33fcd48ebd2456ea5e49fade0d4c7f75_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7fcd0f803b8d623e09a3c81e83363efded7cea961c4ad689ce672570aae84915 +size 43267 diff --git a/marked/Rel-18/38_series/38871/356fe144853f780de8f52534eeee6b10_img.jpg b/marked/Rel-18/38_series/38871/356fe144853f780de8f52534eeee6b10_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..077d2b6f4c0c16303d67650b9d29d2fbaad1b6d3 --- /dev/null +++ b/marked/Rel-18/38_series/38871/356fe144853f780de8f52534eeee6b10_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c273a51eed517b08a125bb79bb9014ab3aa9475c6f95cbd801a9f732288e6069 +size 34703 diff --git a/marked/Rel-18/38_series/38871/3668a836db39d25d24b56180a9c9a7fb_img.jpg b/marked/Rel-18/38_series/38871/3668a836db39d25d24b56180a9c9a7fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..108782f2efe3e63215d584b6b8654e17a6c93dc1 --- /dev/null +++ b/marked/Rel-18/38_series/38871/3668a836db39d25d24b56180a9c9a7fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4654140aeaa7e9677e33c545e37a5bf2086018de6e438b9a8cb13aae5f704275 +size 37704 diff --git a/marked/Rel-18/38_series/38871/38b1cf6150ea33422f219fc9646b8097_img.jpg b/marked/Rel-18/38_series/38871/38b1cf6150ea33422f219fc9646b8097_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cab169027ff4431ec983b9c1e147392d24b268aa --- /dev/null +++ b/marked/Rel-18/38_series/38871/38b1cf6150ea33422f219fc9646b8097_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40c5044d324e6a90059bc06d545deb8f3662f9f1f54f5ece07502da9e80e7765 +size 24026 diff --git a/marked/Rel-18/38_series/38871/3a53543f493df4ab709afab280973ddb_img.jpg b/marked/Rel-18/38_series/38871/3a53543f493df4ab709afab280973ddb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adb92f92f24ed0caf9fef250713dc1f268831989 --- /dev/null +++ b/marked/Rel-18/38_series/38871/3a53543f493df4ab709afab280973ddb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da91e1982801b05ea674e28c5367a2c44857e7db059f86872299c0a98d1d1ea0 +size 33641 diff --git a/marked/Rel-18/38_series/38871/3dbfeaa3a741161e292e4966c35c0cad_img.jpg b/marked/Rel-18/38_series/38871/3dbfeaa3a741161e292e4966c35c0cad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de2f38a63484be468f76efcb65f84c418fb8227d --- /dev/null +++ b/marked/Rel-18/38_series/38871/3dbfeaa3a741161e292e4966c35c0cad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33cfeb3ac786642f2512d0a5a9e18e9695c2e6194131568119b3a756d2accdd3 +size 30056 diff --git a/marked/Rel-18/38_series/38871/403affb63bbbac5175158681bb89f8a3_img.jpg b/marked/Rel-18/38_series/38871/403affb63bbbac5175158681bb89f8a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4a157ec5fd90f7c688219771dacd498113151b4 --- /dev/null +++ b/marked/Rel-18/38_series/38871/403affb63bbbac5175158681bb89f8a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db7c4496da4937dce729fefe1e9262ca64134fa34fe623e5d35468b96b5cc3af +size 29949 diff --git a/marked/Rel-18/38_series/38871/42f0611a8a2766c986ff45551918ca5d_img.jpg b/marked/Rel-18/38_series/38871/42f0611a8a2766c986ff45551918ca5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f22001c6dc1f1f9f53af08f8d0fc3a99b412f0f0 --- /dev/null +++ b/marked/Rel-18/38_series/38871/42f0611a8a2766c986ff45551918ca5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5bcc4b53b55e12c28d6ff049d37e33b4fe3d0ba974a47a3098fd0265a0d8005 +size 22135 diff --git a/marked/Rel-18/38_series/38871/43f250579f11228cb2f5931e460ea72b_img.jpg b/marked/Rel-18/38_series/38871/43f250579f11228cb2f5931e460ea72b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e255f514b5bcd6c35eea60a3b239b0f9aa12c967 --- /dev/null +++ b/marked/Rel-18/38_series/38871/43f250579f11228cb2f5931e460ea72b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d9fa18cf1ca00a25106d657a41e19a9eae2315f22944c3386eb8dec1740c8bb +size 46253 diff --git a/marked/Rel-18/38_series/38871/483c43eac5aa582dfcb6e0aa8cee163f_img.jpg b/marked/Rel-18/38_series/38871/483c43eac5aa582dfcb6e0aa8cee163f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ea201e7471255d3af216f167ca6731b0a7adebd --- /dev/null +++ b/marked/Rel-18/38_series/38871/483c43eac5aa582dfcb6e0aa8cee163f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8563c03b0d24c275166031bef4cc23f78edfef9d09aa1ce017ea58413a7feee +size 102709 diff --git a/marked/Rel-18/38_series/38871/4883297d1dd2e09e29fb2dec9f8c940b_img.jpg b/marked/Rel-18/38_series/38871/4883297d1dd2e09e29fb2dec9f8c940b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d558163c628ca226f23802306571689645908a2 --- /dev/null +++ b/marked/Rel-18/38_series/38871/4883297d1dd2e09e29fb2dec9f8c940b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b83419f138623c21ed74f81d4a8516d28e22fadc5e6dbf492ec41ef6e3c0004 +size 26601 diff --git a/marked/Rel-18/38_series/38871/4b09cf6f9d4da93fe55e6597e4bdb09b_img.jpg b/marked/Rel-18/38_series/38871/4b09cf6f9d4da93fe55e6597e4bdb09b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..254c5b843b972f56cdf1b11b427fce712e125ce2 --- /dev/null +++ b/marked/Rel-18/38_series/38871/4b09cf6f9d4da93fe55e6597e4bdb09b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03c7e351a309a69496735738b7bf08dbbb2b131ca065044f9dbdb8e52c206629 +size 63035 diff --git a/marked/Rel-18/38_series/38871/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg b/marked/Rel-18/38_series/38871/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d827fc4f947c832f35e894dc62fd93fd35a94670 --- /dev/null +++ b/marked/Rel-18/38_series/38871/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6c2c4d25e2cf9a326c78a4e87aa59db0b0a1daa33225216cfff6ee009b4eb21 +size 52684 diff --git a/marked/Rel-18/38_series/38871/509a054727400bc6d424bb2a559b8cfc_img.jpg b/marked/Rel-18/38_series/38871/509a054727400bc6d424bb2a559b8cfc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13c4a9999833432b7ea8c96cb0b1d353234b12ee --- /dev/null +++ b/marked/Rel-18/38_series/38871/509a054727400bc6d424bb2a559b8cfc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b837c5fd49dcfc7aeff4e81fc2f9e3885aa6844da093b2555a396b1093b93d6a +size 176964 diff --git a/marked/Rel-18/38_series/38871/53d8bef47c63e0897de4cd058bad2cbd_img.jpg b/marked/Rel-18/38_series/38871/53d8bef47c63e0897de4cd058bad2cbd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7029b02e1f13963ccbec51d6d8b65e8995dbe2ce --- /dev/null +++ b/marked/Rel-18/38_series/38871/53d8bef47c63e0897de4cd058bad2cbd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d6a1d74b7ebc31c63ba4d03543833aebb64abe3a10082ec55fbd4e58220da5b +size 174243 diff --git a/marked/Rel-18/38_series/38871/5829caa34c69304c08fb93a3c1ba5756_img.jpg b/marked/Rel-18/38_series/38871/5829caa34c69304c08fb93a3c1ba5756_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6fa53ed713c78901129d7162ae33e7c15b2780b --- /dev/null +++ b/marked/Rel-18/38_series/38871/5829caa34c69304c08fb93a3c1ba5756_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95f33ad26b7ecda0a7d2692087d38a93350efa4b6393e34ebe5579cc5ad790b5 +size 26583 diff --git a/marked/Rel-18/38_series/38871/589228d62aeb514220650b72e9490a44_img.jpg b/marked/Rel-18/38_series/38871/589228d62aeb514220650b72e9490a44_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..452279accbf465193afea68e9c6f09a4b3c2b921 --- /dev/null +++ b/marked/Rel-18/38_series/38871/589228d62aeb514220650b72e9490a44_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f86bf2be768004fa401168a65c59116fa58cddb23216d2da45c4a45dd4dcd88a +size 26829 diff --git a/marked/Rel-18/38_series/38871/5a8d83665fa993ed599f2eb41fd6c7f5_img.jpg b/marked/Rel-18/38_series/38871/5a8d83665fa993ed599f2eb41fd6c7f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d47dbd763a1c695deeccdd29c058e0ca5d9cc8f0 --- /dev/null +++ b/marked/Rel-18/38_series/38871/5a8d83665fa993ed599f2eb41fd6c7f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a54a311f3ffc9496fa00b24aa116704ae2926508c1cc2858b9e68801889f4fc3 +size 57841 diff --git a/marked/Rel-18/38_series/38871/5e16d3613b74558acc74ff6d7fd75fa9_img.jpg b/marked/Rel-18/38_series/38871/5e16d3613b74558acc74ff6d7fd75fa9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05a410f095fd89c549d9d3b1cf83dfd2e00fcd32 --- /dev/null +++ b/marked/Rel-18/38_series/38871/5e16d3613b74558acc74ff6d7fd75fa9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3b7ccbf0472da8d46333c15f423ac3b7c0f4743166402a2e90742666c55ce80 +size 29794 diff --git a/marked/Rel-18/38_series/38871/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38871/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..982477d79fb5166ed921d4dab8004095bdc7020a --- /dev/null +++ b/marked/Rel-18/38_series/38871/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ee9be984aa2b528305ec7b8c7f27bfcedbe367ed4fcb47fcc7938aaae2ef9ff +size 9400 diff --git a/marked/Rel-18/38_series/38871/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38871/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92cdf7c2514a0655a997a15e95f8ff9f1c1a76d4 --- /dev/null +++ b/marked/Rel-18/38_series/38871/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47bab1e264627c0c066bc27ebedcdde03c7c6fc4ab6c93252c745d69de365fb3 +size 5756 diff --git a/marked/Rel-18/38_series/38871/67af94a7c462e85f3a310c9a45c0980d_img.jpg b/marked/Rel-18/38_series/38871/67af94a7c462e85f3a310c9a45c0980d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55799719a8e73b1d87c23a49c6e773774f115b40 --- /dev/null +++ b/marked/Rel-18/38_series/38871/67af94a7c462e85f3a310c9a45c0980d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c6e6f14b5abe1a4165609aab16d94a78c44e01b01a32b1751a7fe89199b26e7 +size 81115 diff --git a/marked/Rel-18/38_series/38871/7073d971d62b28a8c0045003a08eeb36_img.jpg b/marked/Rel-18/38_series/38871/7073d971d62b28a8c0045003a08eeb36_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0166c523a5d420585bea8c00711bb2a3966ada01 --- /dev/null +++ b/marked/Rel-18/38_series/38871/7073d971d62b28a8c0045003a08eeb36_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a889a0aa34504fa24520500f790a90291689b65ad662a9749d3db555e3cbaeba +size 44645 diff --git a/marked/Rel-18/38_series/38871/711ec8db6b4a2d4e24b0c0b2ed8853b8_img.jpg b/marked/Rel-18/38_series/38871/711ec8db6b4a2d4e24b0c0b2ed8853b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..450a141a98287f1863861794e4b477ee5a26893f --- /dev/null +++ b/marked/Rel-18/38_series/38871/711ec8db6b4a2d4e24b0c0b2ed8853b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba923d201f5233298d52bf55a2d77836a9e822643dbdb2eb71bff1a3a2d152d2 +size 140540 diff --git a/marked/Rel-18/38_series/38871/71b3c09a6e19c24f87bf700ada69409c_img.jpg b/marked/Rel-18/38_series/38871/71b3c09a6e19c24f87bf700ada69409c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1868a557e7e1393ead4ee572175090f84246a245 --- /dev/null +++ b/marked/Rel-18/38_series/38871/71b3c09a6e19c24f87bf700ada69409c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:658bdb5008c16550ffe0534d39fac87a0e9178909c28c9cf69ae87669d2a5dbc +size 22393 diff --git a/marked/Rel-18/38_series/38871/730b6615db6d402580db1024a7f4e163_img.jpg b/marked/Rel-18/38_series/38871/730b6615db6d402580db1024a7f4e163_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7113a270e8be414c0b670e8abb8e1af2a55e218 --- /dev/null +++ b/marked/Rel-18/38_series/38871/730b6615db6d402580db1024a7f4e163_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b85523a9ee4e4f82fda4f1325b254e2beb8f48a6d82773a2a73b6e45fd2bc47 +size 160148 diff --git a/marked/Rel-18/38_series/38871/759c7d62402f0b4651ddce292be5bdef_img.jpg b/marked/Rel-18/38_series/38871/759c7d62402f0b4651ddce292be5bdef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..623240e1e17ad96040853d7171a1d147d6851905 --- /dev/null +++ b/marked/Rel-18/38_series/38871/759c7d62402f0b4651ddce292be5bdef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7169ad1f640d6aea68fbaa94ceb3ba7699c351dc528376d3a8014dd03cd66225 +size 124750 diff --git a/marked/Rel-18/38_series/38871/75b9cb95f5815d6f3bbe57020a049504_img.jpg b/marked/Rel-18/38_series/38871/75b9cb95f5815d6f3bbe57020a049504_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..525ec26f2e8786e8c42b9d5ee4fe94278321d9f3 --- /dev/null +++ b/marked/Rel-18/38_series/38871/75b9cb95f5815d6f3bbe57020a049504_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:509e3665402ea43e03af75f76ae5f14b996523aa40e86dc2f9453ddb74454815 +size 240269 diff --git a/marked/Rel-18/38_series/38871/77f518931f4f848dbd638ef1f012b5e8_img.jpg b/marked/Rel-18/38_series/38871/77f518931f4f848dbd638ef1f012b5e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e3fc9057e02eb9e74f75aad8090c7c85743f997 --- /dev/null +++ b/marked/Rel-18/38_series/38871/77f518931f4f848dbd638ef1f012b5e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63286e9a8157242c1d75d987c5bd05ccaae2d39acc6995bbafd12d6645df8f4f +size 31037 diff --git a/marked/Rel-18/38_series/38871/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-18/38_series/38871/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..146f768f7155a38222792bcb8b9a875775a64a38 --- /dev/null +++ b/marked/Rel-18/38_series/38871/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11d7778cf4214e7ce482806683e750882ffac6aaf4d62bd5e1073b0206cebb7a +size 67328 diff --git a/marked/Rel-18/38_series/38871/7b96fce298a23fd76a01ff6c176c1059_img.jpg b/marked/Rel-18/38_series/38871/7b96fce298a23fd76a01ff6c176c1059_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f269639b69ce97cac4e669f520d708406e2e51e --- /dev/null +++ b/marked/Rel-18/38_series/38871/7b96fce298a23fd76a01ff6c176c1059_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d53e6374ac099b9409c4c97016931e912eaf71fcd9a04eab4bf6672f8f82cc8 +size 178224 diff --git a/marked/Rel-18/38_series/38871/7c02e8a3056815b6f955527b101d1c9f_img.jpg b/marked/Rel-18/38_series/38871/7c02e8a3056815b6f955527b101d1c9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23dffc7e590e8cf98fc3f4051e9321d1e955664e --- /dev/null +++ b/marked/Rel-18/38_series/38871/7c02e8a3056815b6f955527b101d1c9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:627242d86ea50b6c824b05e551c887b614be7b01804ddfe805159d503d9db825 +size 45490 diff --git a/marked/Rel-18/38_series/38871/806477b46d89e2aa6e612a7d54df8f83_img.jpg b/marked/Rel-18/38_series/38871/806477b46d89e2aa6e612a7d54df8f83_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8269bb079990011640583b5243cfc1c4502ad890 --- /dev/null +++ b/marked/Rel-18/38_series/38871/806477b46d89e2aa6e612a7d54df8f83_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5ee37597f7d8c011125623eef6d3284ec611dc4774faeba544b0cb1df88d316 +size 24150 diff --git a/marked/Rel-18/38_series/38871/810c7bd381c13911f72d22587ad08606_img.jpg b/marked/Rel-18/38_series/38871/810c7bd381c13911f72d22587ad08606_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1439a01ad53a71935e4f218e8fd70c2ef746d76 --- /dev/null +++ b/marked/Rel-18/38_series/38871/810c7bd381c13911f72d22587ad08606_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d89ddc23d41bba80cde4070f7bb250866b669fa79388961d3ff1db010473b6b +size 19917 diff --git a/marked/Rel-18/38_series/38871/853ef5420f0432e626e83987e3f38a0b_img.jpg b/marked/Rel-18/38_series/38871/853ef5420f0432e626e83987e3f38a0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac5d19b6105226501c4e9f0c08988c0e94ea7b46 --- /dev/null +++ b/marked/Rel-18/38_series/38871/853ef5420f0432e626e83987e3f38a0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:babd33437bcef366a69033a8fa4f594261b911fe1f9450d1f6cf8f0415aa3003 +size 108128 diff --git a/marked/Rel-18/38_series/38871/89903b84ee51378cd21268377c9a3c2e_img.jpg b/marked/Rel-18/38_series/38871/89903b84ee51378cd21268377c9a3c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75f27b7667b3e6fab5d8f33098a982a59044ee3d --- /dev/null +++ b/marked/Rel-18/38_series/38871/89903b84ee51378cd21268377c9a3c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0c8b44b05fc2d1fbdfec6b93caebfaefab2dfdcb455f8298983e557d6be9418 +size 35064 diff --git a/marked/Rel-18/38_series/38871/89b3389b2c4fa1b452cf2b5daa5f82ad_img.jpg b/marked/Rel-18/38_series/38871/89b3389b2c4fa1b452cf2b5daa5f82ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1da74e726659298fae205ffbc5261fc28ce89de5 --- /dev/null +++ b/marked/Rel-18/38_series/38871/89b3389b2c4fa1b452cf2b5daa5f82ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a89e2be8a451fff18ed0f1eaec5dd98c14e4802dc49148523251ad418cd2b941 +size 279362 diff --git a/marked/Rel-18/38_series/38871/8b257b8403b56c8d3d3a1e5d63f28e9a_img.jpg b/marked/Rel-18/38_series/38871/8b257b8403b56c8d3d3a1e5d63f28e9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad0e506a0dddd8b4da05288f825250c4c9478b24 --- /dev/null +++ b/marked/Rel-18/38_series/38871/8b257b8403b56c8d3d3a1e5d63f28e9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28ea4c6440af9e05ae7f8bec805b69a1fbddaf8bd06c34ebd32298b192942e3b +size 25660 diff --git a/marked/Rel-18/38_series/38871/8dea092530401404edf31ad62d06a7b8_img.jpg b/marked/Rel-18/38_series/38871/8dea092530401404edf31ad62d06a7b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..688bf5d3c950aa02475fdff065f421c16f600e31 --- /dev/null +++ b/marked/Rel-18/38_series/38871/8dea092530401404edf31ad62d06a7b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b4ea7132aabf703f628ed0851ca34fa5ddedbb206d216a723e1dcf593a787b2 +size 14302 diff --git a/marked/Rel-18/38_series/38871/8e1795da0362b48209b7a5f6e7a590fd_img.jpg b/marked/Rel-18/38_series/38871/8e1795da0362b48209b7a5f6e7a590fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b062fb279f7355c9ffec2dda5aee17ae3f0a8ca6 --- /dev/null +++ b/marked/Rel-18/38_series/38871/8e1795da0362b48209b7a5f6e7a590fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65d29888cd8c4a82c24bdcf6e925f29db1125a4e50068f3932fcacce63a7c792 +size 37600 diff --git a/marked/Rel-18/38_series/38871/92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg b/marked/Rel-18/38_series/38871/92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e0a61eb369cf84d1fc08723bc6db31706cfedea --- /dev/null +++ b/marked/Rel-18/38_series/38871/92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7de996189e83b81336c3b66e7a6c14d237de5fac64188f56edbfa7c27b4e2a2f +size 32564 diff --git a/marked/Rel-18/38_series/38871/9312eb7f45ff2be193599c0ecefe46ba_img.jpg b/marked/Rel-18/38_series/38871/9312eb7f45ff2be193599c0ecefe46ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c891b8274274f1d34624bdc31c9efa622acf8ce --- /dev/null +++ b/marked/Rel-18/38_series/38871/9312eb7f45ff2be193599c0ecefe46ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a30a88a4bbb5eb95bff12a73193b5f65116518d849af2d0892b0dea55850b46e +size 60904 diff --git a/marked/Rel-18/38_series/38871/9642ee15d719705144037077981aaa99_img.jpg b/marked/Rel-18/38_series/38871/9642ee15d719705144037077981aaa99_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0ddc46ac58ad4fffd3811e67fe5dce34f9b649f --- /dev/null +++ b/marked/Rel-18/38_series/38871/9642ee15d719705144037077981aaa99_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f54aa9ea2637df04bb8882f31ef0e7fc8170dc5752c1f2f1a39eb26ef996558 +size 37610 diff --git a/marked/Rel-18/38_series/38871/97425d0928d13d2741b84e698ab2da55_img.jpg b/marked/Rel-18/38_series/38871/97425d0928d13d2741b84e698ab2da55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a5882ffce2e3a6216a1b344d66b64b0aa85f6e1 --- /dev/null +++ b/marked/Rel-18/38_series/38871/97425d0928d13d2741b84e698ab2da55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c76123184c379a1dcd3a4105295890798e55d9302b5cb0f5099e076baa473798 +size 27786 diff --git a/marked/Rel-18/38_series/38871/9c888dd6588358989047de6ced8b2bdb_img.jpg b/marked/Rel-18/38_series/38871/9c888dd6588358989047de6ced8b2bdb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..084f4a57e9c61247c8ad468fca401b2d5eb9b35b --- /dev/null +++ b/marked/Rel-18/38_series/38871/9c888dd6588358989047de6ced8b2bdb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac939988f7f552878081d3a47fca64d9b9cd11bce47725aadc706458a5055b71 +size 180881 diff --git a/marked/Rel-18/38_series/38871/a0c24b4aa687fe3fcc1b2d4f46461af5_img.jpg b/marked/Rel-18/38_series/38871/a0c24b4aa687fe3fcc1b2d4f46461af5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..870652c045a753079d6217a19ec1d4b110268dcd --- /dev/null +++ b/marked/Rel-18/38_series/38871/a0c24b4aa687fe3fcc1b2d4f46461af5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f77d7de4d1b7d4bb0e250ad1aa49ed78ce102f9050ed5b41ecc30b9b72e6933b +size 26414 diff --git a/marked/Rel-18/38_series/38871/a3bdecee519d876ad8ea9d5a8f042061_img.jpg b/marked/Rel-18/38_series/38871/a3bdecee519d876ad8ea9d5a8f042061_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eabb8e667ed68dcf517fe6cb22270adf5cd2d3c4 --- /dev/null +++ b/marked/Rel-18/38_series/38871/a3bdecee519d876ad8ea9d5a8f042061_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24777b002934996b5ac5e96f66c5a36c9e5df0ead7749e743ed908f1cc18df5c +size 25178 diff --git a/marked/Rel-18/38_series/38871/a478eb6698236d95b23c326698f5cc10_img.jpg b/marked/Rel-18/38_series/38871/a478eb6698236d95b23c326698f5cc10_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c821fb36984ab22008414e2364601f3929696f0 --- /dev/null +++ b/marked/Rel-18/38_series/38871/a478eb6698236d95b23c326698f5cc10_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88a1299472530453f25e8b69159a4b66d5ced82fed8aa6ac2b04685fe84544de +size 38360 diff --git a/marked/Rel-18/38_series/38871/a5ac2ed01d588d4d979f42717117c315_img.jpg b/marked/Rel-18/38_series/38871/a5ac2ed01d588d4d979f42717117c315_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f49f476e870a3d5a2300d7f3cac559ee7b4e9a4 --- /dev/null +++ b/marked/Rel-18/38_series/38871/a5ac2ed01d588d4d979f42717117c315_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a886e72fa129f2b37cf3373f85f99517c25b08cd3779c66eafcd42c3efde43b +size 56207 diff --git a/marked/Rel-18/38_series/38871/a8807f349e4e4d1d425fe4148f81741d_img.jpg b/marked/Rel-18/38_series/38871/a8807f349e4e4d1d425fe4148f81741d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00103dff1f1b9ce4c3c7b88e00f98bb6300c4b52 --- /dev/null +++ b/marked/Rel-18/38_series/38871/a8807f349e4e4d1d425fe4148f81741d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c28371a818dcde8c69a77208a3704f0ed00796dd111ad4f015fbc4df5166a8b7 +size 45818 diff --git a/marked/Rel-18/38_series/38871/a94f8b78e3e4b0c8fd20a9302a2e04e7_img.jpg b/marked/Rel-18/38_series/38871/a94f8b78e3e4b0c8fd20a9302a2e04e7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4380712947d9dc14bd0055eeb6b209e0d586bf07 --- /dev/null +++ b/marked/Rel-18/38_series/38871/a94f8b78e3e4b0c8fd20a9302a2e04e7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c57de0c06af2343b2276c6ea69335c1e934d3f5b6cbf54bbdd9158ada40127d +size 34736 diff --git a/marked/Rel-18/38_series/38871/ace13edeb79bdfa129ed84fbb4ac44e5_img.jpg b/marked/Rel-18/38_series/38871/ace13edeb79bdfa129ed84fbb4ac44e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfe02667f65cb7649550c88e06583923e555c177 --- /dev/null +++ b/marked/Rel-18/38_series/38871/ace13edeb79bdfa129ed84fbb4ac44e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89baaec6fff08d4d4f2baa5e745a24ae7922a9147c55e31c1816e2fffa5862f8 +size 20868 diff --git a/marked/Rel-18/38_series/38871/ae1052278bee12c05c49fe504203d217_img.jpg b/marked/Rel-18/38_series/38871/ae1052278bee12c05c49fe504203d217_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66283f571c5b4ffd825ac56d547d78c4b3e9ad69 --- /dev/null +++ b/marked/Rel-18/38_series/38871/ae1052278bee12c05c49fe504203d217_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:041f361e1ef3d1eb3dca719de63c51995cd0e16534df11c7d649e69eb0cebf1d +size 24730 diff --git a/marked/Rel-18/38_series/38871/ae3a4a187ed34e0ef828c5964e0ca891_img.jpg b/marked/Rel-18/38_series/38871/ae3a4a187ed34e0ef828c5964e0ca891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..505a9852d45f20de2da5df4abdd23a7ce260df3e --- /dev/null +++ b/marked/Rel-18/38_series/38871/ae3a4a187ed34e0ef828c5964e0ca891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0f17d6a5abca197d69541d2887acb6c06615a263cea33203fa50631ec1fb30e +size 25637 diff --git a/marked/Rel-18/38_series/38871/b25cc68846b070bbe56a949b011ba91c_img.jpg b/marked/Rel-18/38_series/38871/b25cc68846b070bbe56a949b011ba91c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3eec1a9f6c93d6883e3eb04fb0a8c550d8e29d4 --- /dev/null +++ b/marked/Rel-18/38_series/38871/b25cc68846b070bbe56a949b011ba91c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4745c16e7d3e8f506348192f47a8148319fb99a07c38d09c56edc77912729df9 +size 18730 diff --git a/marked/Rel-18/38_series/38871/b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg b/marked/Rel-18/38_series/38871/b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1cbe8845f93a7369eed56fb612e50610df2d4123 --- /dev/null +++ b/marked/Rel-18/38_series/38871/b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2220db3fdbf33ab99d7836ceeb1ed2190902f26229a9013fe7e0520a57ae2931 +size 226690 diff --git a/marked/Rel-18/38_series/38871/b6320eeb5fd6dac6be2381930f4d2016_img.jpg b/marked/Rel-18/38_series/38871/b6320eeb5fd6dac6be2381930f4d2016_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2240bb06f30fc0a296bd07e7eea20e5d8eef75d1 --- /dev/null +++ b/marked/Rel-18/38_series/38871/b6320eeb5fd6dac6be2381930f4d2016_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d014a06b42301641292e1b76b493fd54d496d371e2cb84bd90b3db64431d3189 +size 30061 diff --git a/marked/Rel-18/38_series/38871/b8205e5e617a8946ddc956c816156fec_img.jpg b/marked/Rel-18/38_series/38871/b8205e5e617a8946ddc956c816156fec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8899832e312abb6c3ee0e20dc0554bc527030502 --- /dev/null +++ b/marked/Rel-18/38_series/38871/b8205e5e617a8946ddc956c816156fec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ad5bec0fa6d7008b073cc6bddb6f3aaf833bdae9302c6c943d11409449ce14a +size 62755 diff --git a/marked/Rel-18/38_series/38871/b88b618bb8863766bd545c6bfb31f850_img.jpg b/marked/Rel-18/38_series/38871/b88b618bb8863766bd545c6bfb31f850_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78091494e423e587cfc1f4ce686c904921027be5 --- /dev/null +++ b/marked/Rel-18/38_series/38871/b88b618bb8863766bd545c6bfb31f850_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26055420ffe02ee6abc8a0d9058283087a0f4b63e62c627fce448cce58300e12 +size 82997 diff --git a/marked/Rel-18/38_series/38871/b90dcb4c35f1875e19ca312a6cf4adae_img.jpg b/marked/Rel-18/38_series/38871/b90dcb4c35f1875e19ca312a6cf4adae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da5bc5474bd2f9b5cdf88588a2807f4af1a9e710 --- /dev/null +++ b/marked/Rel-18/38_series/38871/b90dcb4c35f1875e19ca312a6cf4adae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21a5337c87a94c11cf730f0c76a6be67d3104ce9fe85c5e9044a4553f3a642c8 +size 283568 diff --git a/marked/Rel-18/38_series/38871/bd50d56ae2c12a92466ba2aea1a78040_img.jpg b/marked/Rel-18/38_series/38871/bd50d56ae2c12a92466ba2aea1a78040_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c41d7c5573e76a187298f783ca5dbdb348f9d4f --- /dev/null +++ b/marked/Rel-18/38_series/38871/bd50d56ae2c12a92466ba2aea1a78040_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61ff69e4af228f4b82301f793f88fe607a60309cb075f831a32bc6246a2d54f2 +size 26354 diff --git a/marked/Rel-18/38_series/38871/bda5b7ebfa41f921e378ab1532bdc706_img.jpg b/marked/Rel-18/38_series/38871/bda5b7ebfa41f921e378ab1532bdc706_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45dac0ebb44e9d435c36a02a81b8fe2fa158b2a9 --- /dev/null +++ b/marked/Rel-18/38_series/38871/bda5b7ebfa41f921e378ab1532bdc706_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:caf94ca017de5f4d3f40ad145edb8a1b304a6111aa309bcf7e49ffb5d884e3e2 +size 54848 diff --git a/marked/Rel-18/38_series/38871/be2d9105109f6a87907ab68cb88548d9_img.jpg b/marked/Rel-18/38_series/38871/be2d9105109f6a87907ab68cb88548d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6abde8e8e1655327e63e3b683094a942517bcc6d --- /dev/null +++ b/marked/Rel-18/38_series/38871/be2d9105109f6a87907ab68cb88548d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94482a9e1cc713040ab86b8319a6d8f5680643986bc7fcfdeb5c2a9d3ecc85e9 +size 41898 diff --git a/marked/Rel-18/38_series/38871/bf9297824aec2a021ecbad6f70536914_img.jpg b/marked/Rel-18/38_series/38871/bf9297824aec2a021ecbad6f70536914_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c7dc6dad3150c8f0c3a64fae5288f7dbf1299a2 --- /dev/null +++ b/marked/Rel-18/38_series/38871/bf9297824aec2a021ecbad6f70536914_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b4d65f41d50013aa0138d6d2acc1a96728a1b00b5fcc05df5f48ef64e138ae3 +size 30194 diff --git a/marked/Rel-18/38_series/38871/c0ad6ce178cb2d268bb7776c5afb507e_img.jpg b/marked/Rel-18/38_series/38871/c0ad6ce178cb2d268bb7776c5afb507e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c84eeed0bf65d22746f8a78e98b906592e84baf1 --- /dev/null +++ b/marked/Rel-18/38_series/38871/c0ad6ce178cb2d268bb7776c5afb507e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb1ccc718cec6cd44116837d20bbf2d5ce671a40070484f9637a82e6cb44d4b1 +size 33592 diff --git a/marked/Rel-18/38_series/38871/c0f6ba43542fddfee899e1af9cbd720d_img.jpg b/marked/Rel-18/38_series/38871/c0f6ba43542fddfee899e1af9cbd720d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bd3d9bf3e15b6d29487d2e2155d77d02c31988b --- /dev/null +++ b/marked/Rel-18/38_series/38871/c0f6ba43542fddfee899e1af9cbd720d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4a8a4407b61ec9edc8758007fea7d217cb956d206987f6c2f4a029d0938e6ab +size 49481 diff --git a/marked/Rel-18/38_series/38871/c13f6935817282291ff1db48a1488a68_img.jpg b/marked/Rel-18/38_series/38871/c13f6935817282291ff1db48a1488a68_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bac8eb4ac178856cc2e81e676a1dcec3e4bfa97a --- /dev/null +++ b/marked/Rel-18/38_series/38871/c13f6935817282291ff1db48a1488a68_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b71a6d503b5227f8540fbbe2b855af513c5b7bda02f0003591510933b66f38e0 +size 17135 diff --git a/marked/Rel-18/38_series/38871/c2f36c545b190860d04e1d84e58d22cc_img.jpg b/marked/Rel-18/38_series/38871/c2f36c545b190860d04e1d84e58d22cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f464b96ea495e41d3dc8667c73c5a9bb95f82f5 --- /dev/null +++ b/marked/Rel-18/38_series/38871/c2f36c545b190860d04e1d84e58d22cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5079e34a8f35a53b546e7e26f5795c033d543cf5c432085c740de8ce07d3f36 +size 20355 diff --git a/marked/Rel-18/38_series/38871/c4737359f71d2b1cb0a068aa478f5ff2_img.jpg b/marked/Rel-18/38_series/38871/c4737359f71d2b1cb0a068aa478f5ff2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06327b96b256c630201c7d9a704af0f2120f9b85 --- /dev/null +++ b/marked/Rel-18/38_series/38871/c4737359f71d2b1cb0a068aa478f5ff2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0db315b5f84e17564612b8f3eeff3de3a86bf3f47e6de8eab9ac2d41b09ed2cc +size 43755 diff --git a/marked/Rel-18/38_series/38871/c54c26de58f13334f236e73a4b8f66d8_img.jpg b/marked/Rel-18/38_series/38871/c54c26de58f13334f236e73a4b8f66d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..658b0caf7fe3ee89519c679c960f76d1680f78a3 --- /dev/null +++ b/marked/Rel-18/38_series/38871/c54c26de58f13334f236e73a4b8f66d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52cb9cf03cbd94127fcefa5053aea53c824708fa14b7cfe23ab3028d1f7f28d0 +size 33327 diff --git a/marked/Rel-18/38_series/38871/c75acc302d092d391c118af443fc2e43_img.jpg b/marked/Rel-18/38_series/38871/c75acc302d092d391c118af443fc2e43_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d151c43eaa46069db47d17f2db6b383319b35c0 --- /dev/null +++ b/marked/Rel-18/38_series/38871/c75acc302d092d391c118af443fc2e43_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:544affa3e97bb2c1a49980c95057dc0f7353305fa778658659f3bea6621ef670 +size 12901 diff --git a/marked/Rel-18/38_series/38871/c8f2f0357b99e801b1b0bb5faecf0787_img.jpg b/marked/Rel-18/38_series/38871/c8f2f0357b99e801b1b0bb5faecf0787_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a1377f9c14be2ddda88e9d9d2f542a2f2f24d73 --- /dev/null +++ b/marked/Rel-18/38_series/38871/c8f2f0357b99e801b1b0bb5faecf0787_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f98b59ecd841708ba1529f6f2c94978adb994262d940d55575cc23843279c2e9 +size 28215 diff --git a/marked/Rel-18/38_series/38871/c959fda5679ea6470e0810c8c29eb823_img.jpg b/marked/Rel-18/38_series/38871/c959fda5679ea6470e0810c8c29eb823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..618bed3e3731aa006d1fb41a9ce080ca56e8bc82 --- /dev/null +++ b/marked/Rel-18/38_series/38871/c959fda5679ea6470e0810c8c29eb823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6b646bff77ec84bef74fb4e6e811f5885c951e5efa5fab96cec83ceff8db733 +size 26043 diff --git a/marked/Rel-18/38_series/38871/ca6d37a6cfc63720d1a66fe263d60f2e_img.jpg b/marked/Rel-18/38_series/38871/ca6d37a6cfc63720d1a66fe263d60f2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f722873ce207e28e76ecd3595749b97a6a89eff --- /dev/null +++ b/marked/Rel-18/38_series/38871/ca6d37a6cfc63720d1a66fe263d60f2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66cf6e73d7d9a29283d216b39d4f26b5e243163fbac51ff2cd5afe20ff34c33d +size 35753 diff --git a/marked/Rel-18/38_series/38871/cea5c8233335c952c7f64d6a357f5d80_img.jpg b/marked/Rel-18/38_series/38871/cea5c8233335c952c7f64d6a357f5d80_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b80ab52f19792162d715ade0d437277ecd8b1a7 --- /dev/null +++ b/marked/Rel-18/38_series/38871/cea5c8233335c952c7f64d6a357f5d80_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5960f92eaa0dbb01a5ae382929d15d81f13ea68a0cc171433d5081b7248cc7e8 +size 25423 diff --git a/marked/Rel-18/38_series/38871/cf504c5f59d17aff988b7c672a829d5c_img.jpg b/marked/Rel-18/38_series/38871/cf504c5f59d17aff988b7c672a829d5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41d3b009f7d119de730994b80d2ada786a5613df --- /dev/null +++ b/marked/Rel-18/38_series/38871/cf504c5f59d17aff988b7c672a829d5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1f6af28ccdef0ed4e52b1bdf96e42985e78dcb0f47d3691b060296b44f6c3ff +size 24668 diff --git a/marked/Rel-18/38_series/38871/daa9e738320d13f92e63ceaef7ad93c4_img.jpg b/marked/Rel-18/38_series/38871/daa9e738320d13f92e63ceaef7ad93c4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38ac26a7da1959f7a717ed67f4721d2686390bf1 --- /dev/null +++ b/marked/Rel-18/38_series/38871/daa9e738320d13f92e63ceaef7ad93c4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8bab3e4487f499d1611ed8fed8b1a6fddb933de89dfdcfb0c9db2b3bb82038c +size 15704 diff --git a/marked/Rel-18/38_series/38871/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-18/38_series/38871/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e8b1cd7a2a0066b75920043787a39cea713c987 --- /dev/null +++ b/marked/Rel-18/38_series/38871/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb2e60a8e31623e7e97f6765ba104442e2adfe1be54c13fc94a78af508a8a624 +size 70690 diff --git a/marked/Rel-18/38_series/38871/dd7a15555767d4027adfa36fca520c50_img.jpg b/marked/Rel-18/38_series/38871/dd7a15555767d4027adfa36fca520c50_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e08bd590f64e16f9c62f82801ddbdaab3221531f --- /dev/null +++ b/marked/Rel-18/38_series/38871/dd7a15555767d4027adfa36fca520c50_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9113c216d0d414c7ba64366aca75483691c597ec10aef47726f9dc169d27c3e9 +size 91543 diff --git a/marked/Rel-18/38_series/38871/ddc357c6e690c78958d35aae4d3daeca_img.jpg b/marked/Rel-18/38_series/38871/ddc357c6e690c78958d35aae4d3daeca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d0c329ef1e05985422d21ce6736536776a57f30 --- /dev/null +++ b/marked/Rel-18/38_series/38871/ddc357c6e690c78958d35aae4d3daeca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7eb0acdb12b4881e87a04bd5f021e91223aa1f15b96d897ccfed257d99e3e7d7 +size 33371 diff --git a/marked/Rel-18/38_series/38871/df6babe297323feb1575ba89f5cf3b09_img.jpg b/marked/Rel-18/38_series/38871/df6babe297323feb1575ba89f5cf3b09_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de6ec8ee7d52779b3d9663a6682fa9f0b2b4b929 --- /dev/null +++ b/marked/Rel-18/38_series/38871/df6babe297323feb1575ba89f5cf3b09_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe3f51ae7a238e5151101413c356fc0a6a30365a9c7d57883abbf5577ec7fbec +size 26238 diff --git a/marked/Rel-18/38_series/38871/e0740204d7aa33697c8f2d59c4cca51b_img.jpg b/marked/Rel-18/38_series/38871/e0740204d7aa33697c8f2d59c4cca51b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bccdd3d8d5ee21e49e840448ae6b83a958834212 --- /dev/null +++ b/marked/Rel-18/38_series/38871/e0740204d7aa33697c8f2d59c4cca51b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df764d24bf3f1a617f1dd7e8de8d5a8cbe31a6ad006537b6bc71b13e15a461f1 +size 12047 diff --git a/marked/Rel-18/38_series/38871/e0f3606e9c9eee18bc68b713df4eda8a_img.jpg b/marked/Rel-18/38_series/38871/e0f3606e9c9eee18bc68b713df4eda8a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ab89723d794d2483ad0f454c14834a859300c3f --- /dev/null +++ b/marked/Rel-18/38_series/38871/e0f3606e9c9eee18bc68b713df4eda8a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:330b528d9229ecd854dcd39ea6877a68fb9288013458cf315731a9b61a53c4d1 +size 69337 diff --git a/marked/Rel-18/38_series/38871/e5c6de7d8ff5b0d75d5602d200b899f0_img.jpg b/marked/Rel-18/38_series/38871/e5c6de7d8ff5b0d75d5602d200b899f0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2292f30fd5cd2afabda649bf542e1d12b9117bf --- /dev/null +++ b/marked/Rel-18/38_series/38871/e5c6de7d8ff5b0d75d5602d200b899f0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c20fe21f4e582d975667a0e3d76e18b22353f6529c353d511c056d7f6524390 +size 72619 diff --git a/marked/Rel-18/38_series/38871/eaa5fbc353eb95b90302cfbe7c299576_img.jpg b/marked/Rel-18/38_series/38871/eaa5fbc353eb95b90302cfbe7c299576_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9892d85b79ca23da8cbd26c2845e48ec00b6f4e0 --- /dev/null +++ b/marked/Rel-18/38_series/38871/eaa5fbc353eb95b90302cfbe7c299576_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7d740b355ba6905f11a3e63f2ab26783725ac2b88f36db2b5e7777df4913547 +size 73669 diff --git a/marked/Rel-18/38_series/38871/ec07cb6b37a0878f3acbb201028080c1_img.jpg b/marked/Rel-18/38_series/38871/ec07cb6b37a0878f3acbb201028080c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd150e4d4a384cd1afa8b040db1405c31cbf42be --- /dev/null +++ b/marked/Rel-18/38_series/38871/ec07cb6b37a0878f3acbb201028080c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c40b107dd4739d1ac90e48e608d12f38cc41abb3eb4d07b6672710dd375547c +size 6036 diff --git a/marked/Rel-18/38_series/38871/edf708d74dbab9d4e2ed3b9e9a98295d_img.jpg b/marked/Rel-18/38_series/38871/edf708d74dbab9d4e2ed3b9e9a98295d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80fe77e04d7f8fdfc90ff319385dfa97b35b0e29 --- /dev/null +++ b/marked/Rel-18/38_series/38871/edf708d74dbab9d4e2ed3b9e9a98295d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f877111d238cd2b234e4b20eb811b790b5676f44d1deea931143cc106d28aa3 +size 25344 diff --git a/marked/Rel-18/38_series/38871/f2ea0f64a770b22b902820457d262265_img.jpg b/marked/Rel-18/38_series/38871/f2ea0f64a770b22b902820457d262265_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8dffc28b1c0daf8402f22d742dc99858b435e9a --- /dev/null +++ b/marked/Rel-18/38_series/38871/f2ea0f64a770b22b902820457d262265_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fed4588698791e8de7480902ae9d62b99c3af0b34892d4465c5878257672d9f0 +size 30120 diff --git a/marked/Rel-18/38_series/38871/f3a9d0606fc070983135f0a0c1496757_img.jpg b/marked/Rel-18/38_series/38871/f3a9d0606fc070983135f0a0c1496757_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e3501ee3814859458f87c7850653a5399d105b2 --- /dev/null +++ b/marked/Rel-18/38_series/38871/f3a9d0606fc070983135f0a0c1496757_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03e2541d061c57e22297b5f847e816000144b8099da5926034c70f8be48ff22e +size 21909 diff --git a/marked/Rel-18/38_series/38871/f5f8e0d3c976bbd6d547bcc01e91c7d5_img.jpg b/marked/Rel-18/38_series/38871/f5f8e0d3c976bbd6d547bcc01e91c7d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a469ed45702491315352b486af4d9df1faffc4c --- /dev/null +++ b/marked/Rel-18/38_series/38871/f5f8e0d3c976bbd6d547bcc01e91c7d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6116a1def4bad511a8435a24221691d7ffa1db2c90f9a6795e6e21d511c0baa7 +size 25243 diff --git a/marked/Rel-18/38_series/38871/f5fb1391d89d4586350057053c412158_img.jpg b/marked/Rel-18/38_series/38871/f5fb1391d89d4586350057053c412158_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3b6d619d9b6e83f09283e2bb80400451f82ecce --- /dev/null +++ b/marked/Rel-18/38_series/38871/f5fb1391d89d4586350057053c412158_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbea79648e0be0660671ffd07ebc5f512789533a2790115ac63c5bd6f38ef88a +size 26330 diff --git a/marked/Rel-18/38_series/38871/f88160096d5df53c1a91e2fc5a6a81a5_img.jpg b/marked/Rel-18/38_series/38871/f88160096d5df53c1a91e2fc5a6a81a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85701109a346d5b79a3c6b269f2b59ca9316e3a1 --- /dev/null +++ b/marked/Rel-18/38_series/38871/f88160096d5df53c1a91e2fc5a6a81a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08317ad373ce75143b6a922a6f23a8007ed822305b25d8bc4113915a245abc2b +size 13866 diff --git a/marked/Rel-18/38_series/38871/fd8369b549b3d1a5c848cbd83659cae9_img.jpg b/marked/Rel-18/38_series/38871/fd8369b549b3d1a5c848cbd83659cae9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f242900a5057547896a4af6b739157e9196378ed --- /dev/null +++ b/marked/Rel-18/38_series/38871/fd8369b549b3d1a5c848cbd83659cae9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa6da99e55f99f87d6e1a23977d0239c42b6dddc7a312a7c5165debf1c5b3a7b +size 233067 diff --git a/marked/Rel-18/38_series/38871/fe474eb6f1504964f54ee30c01708ecc_img.jpg b/marked/Rel-18/38_series/38871/fe474eb6f1504964f54ee30c01708ecc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cefbd740f6a946ca13e84a771e956c4f5522f12 --- /dev/null +++ b/marked/Rel-18/38_series/38871/fe474eb6f1504964f54ee30c01708ecc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c11fab79fc9cd215c752d46761cad5ecadc068b887eab8dbe5e9e1eb15c427b +size 38557 diff --git a/marked/Rel-18/38_series/38871/fed351d1b7c4568a439a8682c27f8cc3_img.jpg b/marked/Rel-18/38_series/38871/fed351d1b7c4568a439a8682c27f8cc3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62c459ca99dbf8f235d8df40a0b8d3ed51dc5806 --- /dev/null +++ b/marked/Rel-18/38_series/38871/fed351d1b7c4568a439a8682c27f8cc3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0dbb83455543d3196bb907e9c6a377df35a16e2a38769230cb26cdf8258d0dba +size 28166 diff --git a/marked/Rel-18/38_series/38871/raw.md b/marked/Rel-18/38_series/38871/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..da911125c8fe2bd5514c19c58b766c6aabcb2465 --- /dev/null +++ b/marked/Rel-18/38_series/38871/raw.md @@ -0,0 +1,1993 @@ + + +# **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Study on NR frequency range 2 (FR2) Over-the-Air (OTA) testing enhancements; (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5" and "G" 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. The "3" and "G" are connected at the top, and the "P" and "P" are connected at the top. Below the "P" is a red signal wave icon. 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. + +© 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 of terms, symbols and abbreviations..... | 8 | +| 3.1 Terms..... | 8 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations ..... | 8 | +| 4 General..... | 9 | +| 4.1 Objective ..... | 9 | +| 4.2 Devices Type..... | 9 | +| 5 UE RF testing methodology for multi-Rx chain DL reception..... | 10 | +| 5.1 General ..... | 10 | +| 5.2 Measurement setup..... | 10 | +| 5.2.1 Measurement Setup with Full Degree of Rotation Freedom for Each AoA ..... | 10 | +| 5.2.2 Measurement Setup with Full Degrees of Freedom for AoA1 with Fixed Angular Offset(s) Between AoA1 and AoA2..... | 19 | +| 5.2.3 Measurement Setup with Full Degrees of Freedom for AoA1 with Variable Angular Offset(s) between AoA1 and AoA2 ..... | 24 | +| 5.2.4 Measurement Setup with Full Degrees of Freedom for AoA1 with Partial Freedom of Variable Angular Offset(s) between AoA1 and AoA2 ..... | 26 | +| 5.2.5 Measurement Setup with Full Degrees of Freedom for AoA1 with Fixed AoA2/Anchor in NF ..... | 28 | +| 5.2.6 Measurement Setup with Test Modes ..... | 29 | +| 5.2.7 Measurement Setup to reduce sensitivity to UE orientation in holder with full degrees of freedom for AoA1 with fixed angular offset(s) between AoA1 and AoA2 ..... | 30 | +| 5.2.7.1 Background and Motivation ..... | 30 | +| 5.2.7.2 Implementation Direction..... | 32 | +| 5.2.7.3 Scan strategy to avoid source blocking..... | 35 | +| 5.2.7.4 Pros and Cons ..... | 38 | +| 5.3 Test System Aspects..... | 39 | +| 5.3.1 Absolute Probe Locations..... | 39 | +| 5.3.2 Minimum and Maximum Angular Separation between Probes ..... | 41 | +| 5.3.3 Impact of Probe Locations and 3D Scans on DL Directions..... | 44 | +| 5.3.4 DL Polarizations Perceived by the UE..... | 57 | +| 5.3.5 AoA1-AoA2 DL Orientation Vectors ..... | 68 | +| 5.3.6 Far-field criteria ..... | 74 | +| 5.4 Calibration Measurement Procedure..... | 74 | +| 5.4.1 Direct far field (DFF) ..... | 74 | +| 5.4.2 Indirect far field (IFF) ..... | 74 | +| 5.5 Test procedure..... | 75 | +| 6 UE RRM testing methodology for multi-Rx chain DL reception..... | 77 | +| 6.1 General ..... | 77 | +| 6.2 Measurement setup..... | 77 | +| 6.2.1 Baseline measurement setup..... | 77 | +| 6.2.1.1 Test scenarios..... | 77 | +| 6.2.1.2 Measurement setup for Category 1 scenario..... | 77 | +| 6.2.1.3 Measurement setup for Category 2 scenario..... | 78 | +| 6.2.1.4 Far-field criteria ..... | 81 | +| 6.2.1.5 Calibration measurement procedure ..... | 81 | +| 6.2.1.6 Reference point..... | 81 | +| 6.2.2 Test parameters..... | 82 | +| 6.2.2.1 Test parameters for Mode 1 ..... | 82 | +| 6.2.2.2 Test parameters for Mode 2 ..... | 82 | + +| | | | +|------------------------------------------------------|----------------------------------------------------------------------------------|------------| +| 7 | UE demodulation and CSI testing methodology for multi-Rx chain DL reception..... | 83 | +| 7.1 | General ..... | 83 | +| 7.2 | Measurement setup..... | 83 | +| 7.2.1 | Baseline measurement setup..... | 83 | +| 7.2.1.1 | Reference point..... | 83 | +| 7.2.1.2 | Far-field criteria ..... | 83 | +| 7.2.1.3 | Calibration measurement procedure ..... | 83 | +| 7.2.2 | Test parameters..... | 84 | +| 7.2.2.1 | Noc level configuration ..... | 84 | +| 7.2.2.2 | Criteria of UE test directions ..... | 84 | +| 8 | Summary ..... | 84 | +| Annex A: Measurement uncertainty ..... | | 86 | +| A.1 | Measurement uncertainty budget for UE RF testing methodology ..... | 86 | +| A.2 | Measurement uncertainty budget for UE RRM testing methodology ..... | 88 | +| A.3 | Measurement uncertainty budget for UE demodulation testing methodology ..... | 89 | +| Annex B: UE coordinate system ..... | | 91 | +| B.1 | Reference coordinate system ..... | 91 | +| B.2 | Alternate coordinate system for 2AoA testing..... | 92 | +| B.3 | Test conditions and angle definitions..... | 94 | +| B.4 | DUT positioning guidelines ..... | 99 | +| Annex G: Step size of measurement grids ..... | | 99 | +| G.1 | Simulation results for step size ..... | 100 | +| Annex H: Change history | | 102 | + +# 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 objectives for FR2-1 OTA testing for UEs with multi-panel reception and 4DL layer are as follows. + +- Define a test methodology for RF/RRM/Demodulation requirements testing for devices that can receive simultaneously from multiple Angle of Arrival (AoA) +- The multiple AoA test setup should enable testing of up to 2 DL Layers with dual polarization for each angle + - For RRM, the target should be to allow testing of 4 AoAs with 2 simultaneously active AoAs + - Define a test methodology for up to 4 DL MIMO layer demodulation testing +- Smartphone form factor should be the first priority, other UE types should also be discussed as 2nd priority +- Develop the related preliminary uncertainty assessments for the test methodologies +- The tests shall take the test system reuse, test system complexity and test time into account to keep the whole test costs within a reasonable level. + +# --- 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.101-2: "User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone". +- [3] 3GPP TR 38.810: "Study on test methods". +- [4] 3GPP TR 38.884: "Study on enhanced test methods for FR2 NR UEs". +- [5] 3GPP TS 38.509, "Special conformance testing functions for User Equipment (UE) ". +- [6] 3GPP TS 38.521-2, "User Equipment (UE) conformance specification; Radio transmission and reception; Part 2: Range 2 Standalone". +- [7] 3GPP TS 38.508-1, "User Equipment (UE) conformance specification; Part 1: Common test environment". +- [8] 3GPP TS 38.151, "Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) performance requirements". +- [9] 3GPP TR 38.884, "Study on enhanced test methods for FR2 NR UEs". +- [10] 3GPP TS 38.508-1, "User Equipment (UE) conformance specification; Part 1: Common test environment". +- [11] 3GPP TS 34.114: "User Equipment (UE) / Mobile Station (MS) Over The Air (OTA) antenna performance; Conformance testing". + +- [12] 3GPP TS 38.133: "Requirements for support of radio resource management". +- [13] 3GPP TR 38.903: "Derivation of test tolerances and measurement uncertainty for User Equipment (UE) conformance test cases". + +# 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]. + +**Measurement angle:** the angle of measurement of the desired metric from the view point of the UE, as described in Annex B. + +**RX beam peak direction:** direction where the maximum total component of RSRP and thus best total component of EIS is found. + +**TX beam peak direction:** direction where the maximum total component of EIRP is found. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +- $\theta$ Zenith angle in the spherical co-ordinate system, as well as measurement antenna polarization along the direction of motion of the zenith axis rotation. +- $\phi$ Azimuth angle in the spherical co-ordinate system, as well as measurement antenna polarization along the direction of motion of the azimuth axis rotation. + +## 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]. + +| | | +|------|----------------------------------------------------| +| AoA | Angle of Arrival | +| CATR | Compact Antenna Test Range | +| DFF | Direct Far Field | +| DUT | Device Under Test | +| EIS | Effective Isotropic Sensitivity | +| EIRP | Effective (or equivalent) isotropic radiated power | +| FR2 | Frequency Range 2 | +| IFF | Indirect Far Field | +| MU | Measurement Uncertainty | +| NR | New Radio | +| NSA | Non-standalone | +| OTA | Over The Air | +| RSRP | Reference signal receive power | +| SNR | Signal-to-Noise Ratio | +| SGH | Standard Gain Horn | +| TRP | Total Radiated Power | +| UBF | UE beam lock function | +| UE | User Equipment | + +# --- 4 General + +## 4.1 Objective + +In Rel-17 WI on further enhancements on MIMO for NR (Acronym: NR\_FeMIMO), the objective is to extend the specification to support several aspects on NR MIMO including simultaneous multi-Rx chain DL reception. With considering the objective to define new requirements for the UE with multi-Rx chain DL reception, the FR2 test methods for RF, RRM and demodulation need to be enhanced. This document is to define the enhanced test methods for the verifications of these new requirements for FR2 UE with multi-Rx chain DL receptions. + +## 4.2 Devices Type + +The following device types are considered in the scope of this study: + +- Smartphone +- Tablet +- Wearable devices +- Vehicular mounted device +- Fixed Wireless Access (FWA) terminal +- Other UE types are not precluded + +The development of test methods shall initially focus on the smartphone device type. Other UE types should also be studied as 2nd priority. + +# 5 UE RF testing methodology for multi-Rx chain DL reception + +## 5.1 General + +This clause describes the UE RF testing methodology for multi-Rx chain DL reception for FR2. The following candidate measurement setups are investigated: + +- Measurement Setup with Full Degree of Rotation Freedom for Each AoA +- Measurement Setup with Full Degrees of Freedom for AoA1 with Fixed Angular Offset(s) Between AoA1 and AoA2 +- Measurement Setup with Full Degrees of Freedom for AoA1 with Variable Angular Offset(s) between AoA1 and AoA2 +- Measurement Setup with Full Degrees of Freedom for AoA1 with Partial Freedom of Variable Angular Offset(s) between AoA1 and AoA2 +- Measurement Setup with Full Degrees of Freedom for AoA1 with Fixed AoA2/Anchor in NF +- Measurement Setup with Test Modes +- Measurement Setup to reduce sensitivity to UE orientation in holder with full degrees of freedom for AoA1 with fixed angular offset(s) between AoA1 and AoA2 + +Through the analysis of system complexity, chamber footprint, upgradeability of existing system, development lead time, measurement uncertainty, and test time aspects, the measurement setup with full degrees of freedom for AoA1 with fixed angular Offset(s) between AoA1 and AoA2 is selected as the baseline in Rel-18. + +## 5.2 Measurement setup + +### 5.2.1 Measurement Setup with Full Degree of Rotation Freedom for Each AoA + +FR2 OTA measurement setups with full degree of rotation freedom for each AoA support two simultaneous AoAs with any combination of DL directions, i.e., any permutation of possible AoAs shall be supported. This setup was initially considered as the preferred measurement setup for multi-AoA UE RF testing but later discarded for reasons outlined below. + +Such setup was also considered the default measurement setup for FR2 UE RF testing during the SI phase of FR2 OTA testing [3] given the requirement to perform off-centre of beam measurements as illustrated in Figure 5.2.1-1. However, the adoption of the UE Beamlock test Function (UBF), see Clause 5.4 of [5], to readily perform off-centre of beam measurements shifted the focus towards more practical single-AoA/single-probe UE RF setups, e.g., the Indirect Far Field (IFF) methodology [3] which subsequently became the de-facto setup for FR2 UE RF testing. + +![Figure 5.2.1-1: DFF measurement setup of UE RF characteristics for TRP scans. The diagram shows a smartphone (DUT) at the center of a spherical coordinate grid. A grey beam labeled 'Link Antenna for beam steering' is directed towards the top of the phone. Another grey beam labeled 'Measurement Antenna for centre and off centre of beam measurements' is directed towards the bottom-left of the phone.](3668a836db39d25d24b56180a9c9a7fb_img.jpg) + +Figure 5.2.1-1: DFF measurement setup of UE RF characteristics for TRP scans. The diagram shows a smartphone (DUT) at the center of a spherical coordinate grid. A grey beam labeled 'Link Antenna for beam steering' is directed towards the top of the phone. Another grey beam labeled 'Measurement Antenna for centre and off centre of beam measurements' is directed towards the bottom-left of the phone. + +**Figure 5.2.1-1: DFF measurement setup of UE RF characteristics for TRP scans (Figure 5.2.1.1-1 of [3]).** + +Measurement setups that allow arbitrary positioning for each probe, i.e., the UE does not necessarily require a positioning system are illustrated in Figure 5.2.1-2 and Figure 5.2.1-3. The Direct Far Field (DFF) methodology, i.e., millimeter-wave measurement probes placed in the far-field away from the DUT when adapted to two-simultaneous AoA testing, is illustrated in Figure 5.2.1-2. Here, the probes introducing AoA1 (beam shown in blue) and AoA2 (beam shown in red) can be positioned arbitrarily while the DUT is fixed. When the DFF probes are replaced with Indirect Far Field (IFF) probes, i.e., measurement probe and reflector, a sample test system with full degrees of freedom for each AoA is shown in Figure 5.2.1-3. The full degree of rotation freedom for each probe is highlighted with the yellow arrows behind each DFF probe/IFF probe&reflector combination. The positioning requirements to accurately position probe(s) along two principal axes in 3D yield a very high positioning complexity. + +![Figure 5.2.1-2: Example DFF measurement setup for two-simultaneous AoA testing with full degrees of freedom for each probe. The diagram shows a smartphone (DUT) at the center of a spherical coordinate grid. A blue beam labeled 'AoA1' is directed towards the top-left, and a red beam labeled 'AoA2' is directed towards the top-right. Yellow double-headed arrows behind each beam indicate full degrees of freedom for rotation and positioning.](2de51a31da9b0ffd9d017f035d498997_img.jpg) + +Figure 5.2.1-2: Example DFF measurement setup for two-simultaneous AoA testing with full degrees of freedom for each probe. The diagram shows a smartphone (DUT) at the center of a spherical coordinate grid. A blue beam labeled 'AoA1' is directed towards the top-left, and a red beam labeled 'AoA2' is directed towards the top-right. Yellow double-headed arrows behind each beam indicate full degrees of freedom for rotation and positioning. + +**Figure 5.2.1-2: Example DFF measurement setup for two-simultaneous AoA testing with full degrees of freedom for each probe.** + +![Figure 5.2.1-3: Example IFF measurement setup for two-simultaneous AoA testing with full degrees of freedom for each probe. The diagram shows a central Device Under Test (DUT) mounted on a spherical grid. Two probes are positioned around it: one on the left with a blue beam (AoA1) and one on the right with a red beam (AoA2). Yellow arrows indicate the rotational freedom of the probes and the DUT.](10953d657a5f47fdc829a800419dd370_img.jpg) + +Figure 5.2.1-3: Example IFF measurement setup for two-simultaneous AoA testing with full degrees of freedom for each probe. The diagram shows a central Device Under Test (DUT) mounted on a spherical grid. Two probes are positioned around it: one on the left with a blue beam (AoA1) and one on the right with a red beam (AoA2). Yellow arrows indicate the rotational freedom of the probes and the DUT. + +**Figure 5.2.1-3: Example IFF measurement setup for two-simultaneous AoA testing with full degrees of freedom for each probe.** + +Size (width/depth/height) estimations performed for such DFF/IFF systems supporting the FR2-1 frequency range and devices up to a 40 cm diameter (40 cm QZ) are tabulated in Table 5.2.1-1. The increase in chamber sizes (footprint and heights) when compared to existing FR2 UE RF chambers is significant and existing chambers are not upgradable to support full degrees of freedom. The lead times to develop such systems with full degrees of freedom could be quite significant and could thus delay the commercial adoption of these test cases. Additionally, the overall system complexities of such systems could further require an increase in measurement uncertainties (MUs) and thus test tolerances (TTs). + +**Table 5.2.1-1: Size estimates for UE RF systems with full degrees of freedom for each probe.** + +| Test Method \ Size | Width [m] | Depth [m] | Height [m] | +|--------------------|-----------|-----------|------------| +| DFF | 3.2 | 3.2 | 3.2 | +| IFF | 4.4 | 4.4 | 4.4 | + +Measurement setups that allow full degrees of positioning freedom for one probe and the DUT while the other probe is fixed are shown in Figure 5.2.1-4 for the DFF and Figure 5.2.1-5 for the IFF methodology. The probe introducing AoA1 (beam shown in blue) is fixed while the DUT and the probe introducing AoA2 (beam shown in red) can be positioned arbitrarily (as indicated with the yellow arrows). This approach therefore also supports full degrees of rotational freedom for each AoA. + +![Figure 5.2.1-4: Example DFF measurement setup for two-simultaneous AoA testing with arbitrary positioning capability for one probe and DUT supporting full degrees of freedom. The diagram shows a central Device Under Test (DUT) represented by a grey rectangle inside a wireframe sphere. Two probes, labeled AoA1 (blue) and AoA2 (red), are positioned at different angles. Yellow curved arrows indicate the rotational degrees of freedom for both the probes and the DUT.](0cc86fe8fc37b0edc9581f2af9459a52_img.jpg) + +Figure 5.2.1-4: Example DFF measurement setup for two-simultaneous AoA testing with arbitrary positioning capability for one probe and DUT supporting full degrees of freedom. The diagram shows a central Device Under Test (DUT) represented by a grey rectangle inside a wireframe sphere. Two probes, labeled AoA1 (blue) and AoA2 (red), are positioned at different angles. Yellow curved arrows indicate the rotational degrees of freedom for both the probes and the DUT. + +**Figure 5.2.1-4: Example DFF measurement setup for two-simultaneous AoA testing with arbitrary positioning capability for one probe and DUT supporting full degrees of freedom.** + +Size (width/depth/height) estimations were performed for such DFF/IFF systems as well which are tabulated in Table 5.2.1-2. Only a very small improvement in footprint, i.e., width, can be observed for this system architecture when compared to Table 5.2.1-1. The same conclusions/observations can be made as those above, i.e., the increase in chamber sizes (footprint and heights) when compared to existing FR2 UE RF chambers is significant and existing chambers are not upgradable to support full degrees of freedom. + +![Figure 5.2.1-5: Example IFF measurement setup for two-simultaneous AoA testing with full degrees of freedom for one probe & DUT. This diagram is similar to Figure 5.2.1-4 but shows a different probe mounting mechanism. The probes, AoA1 (blue) and AoA2 (red), are mounted on a mechanical arm structure that allows for their positioning. The DUT is again a grey rectangle within a wireframe sphere, with yellow arrows indicating its degrees of freedom.](b8205e5e617a8946ddc956c816156fec_img.jpg) + +Figure 5.2.1-5: Example IFF measurement setup for two-simultaneous AoA testing with full degrees of freedom for one probe & DUT. This diagram is similar to Figure 5.2.1-4 but shows a different probe mounting mechanism. The probes, AoA1 (blue) and AoA2 (red), are mounted on a mechanical arm structure that allows for their positioning. The DUT is again a grey rectangle within a wireframe sphere, with yellow arrows indicating its degrees of freedom. + +**Figure 5.2.1-5: Example IFF measurement setup for two-simultaneous AoA testing with full degrees of freedom for one probe & DUT** + +**Table 5.2.1-2: Size estimates for UE RF systems with full degrees of freedom for each probe.** + +| Test Method \ Size | Width [m] | Depth [m] | Height [m] | +|--------------------|-----------|-----------|------------| +| DFF | 3.2 | 3.2 | 3.2 | +| IFF | 4.4 | 4.4 | 4.4 | + +Alternate example measurement setups to support full degrees of freedom for AoA are shown in Figures 5.2.1-6 through 5.2.1-9. + +![Diagram of a 2AoA DFF test system with full degrees of freedom.](df6babe297323feb1575ba89f5cf3b09_img.jpg) + +This diagram shows a test system within a square boundary with jagged edges. A central device is mounted on a vertical pedestal. A blue curved arrow labeled $\theta_1$ indicates rotation around the vertical axis, and a blue curved arrow labeled $\phi_1$ indicates rotation around a horizontal axis. To the left, an orange curved arrow labeled $\theta_2$ indicates another rotation around the vertical axis, and an orange curved arrow labeled $\phi_2$ indicates rotation around a horizontal axis. Two range labels are present: $RL = 1m$ and $RL = 1.2m$ . + +Diagram of a 2AoA DFF test system with full degrees of freedom. + +Figure 5.2.1-6: Example of 2AoA DFF test system with full degrees of freedom + +![Diagram of a distributed-axes system with two moving IFF reflectors.](3293245c6893d9d49c2c878828423ecd_img.jpg) + +This diagram illustrates a distributed-axes system. A central sphere is marked with 'QZ' and 'N'. Two reflectors, 'Reflector #1' and 'Reflector #2', are positioned around it. Blue curved arrows indicate various degrees of freedom: $\theta_1$ and $\phi_1$ for the central sphere, and $\theta_2$ , $\phi_2$ , $\Phi_1$ , and $\Phi_2$ for the reflectors. + +Diagram of a distributed-axes system with two moving IFF reflectors. + +Figure 5.2.1-7: Distributed-axes system with two moving IFF reflectors + +![Diagram of a distributed-axes system with two moving IFF reflectors on a 4-axis positioner.](bf9297824aec2a021ecbad6f70536914_img.jpg) + +This diagram shows a distributed-axes system where the central sphere (marked 'QZ' and 'N') and two reflectors ('Reflector #1' and 'Reflector #2') are mounted on a 'Positioner (4-axes)'. Blue curved arrows indicate degrees of freedom: $\theta_1$ and $\phi_1$ for the positioner's base, and $\theta_2$ , $\phi_2$ , $\Phi_1$ , and $\Phi_2$ for the reflectors. + +Diagram of a distributed-axes system with two moving IFF reflectors on a 4-axis positioner. + +Figure 5.2.1-8: Distributed-axes system with two moving IFF reflectors + +![Figure 5.2.1-9: 2AoA RF test system with DFF antenna as the second NR anchor on a slider. The diagram shows a DFF antenna #1 mounted on a curved rail, a reflector #1, a QZ (Quarter Waveplate) at the center, and a 4-axis positioner. The positioner has degrees of freedom labeled theta_1, theta_2, and phi_2. The DFF antenna #1 is shown with a blue arc indicating its movement along the rail.](0e240e8e4783e664047fbdb5fbd0989f_img.jpg) + +Figure 5.2.1-9: 2AoA RF test system with DFF antenna as the second NR anchor on a slider. The diagram shows a DFF antenna #1 mounted on a curved rail, a reflector #1, a QZ (Quarter Waveplate) at the center, and a 4-axis positioner. The positioner has degrees of freedom labeled theta\_1, theta\_2, and phi\_2. The DFF antenna #1 is shown with a blue arc indicating its movement along the rail. + +**Figure 5.2.1-9: 2AoA RF test system with DFF antenna as the second NR anchor on a slider** + +The full degrees of freedom for each AoA supports a probe offset option with variable angular offset(s) between AoA1 and AoA2 in the chamber. The angular separation between AoA1 and AoA2 can change during the testing. This is further illustrated with a sample DUT with a beam peak in the DUT $y$ direction, as illustrated in Figure 5.2.1-10. As the AoA2 probe has full degrees of freedom, i.e., the angular difference between AoA1 and AoA2 is arbitrary, the AoA2 probe can track/follow the DUT's beam peak during testing as illustrated in Table 5.2.1-3 for two different DUT orientations/test points. + +![Figure 5.2.1-10: Sample DUT with assumed beam peak in the DUT's y direction. The diagram shows a rectangular DUT with a 3D beam pattern (colored lobes) originating from its top surface. The beam is oriented along the y_DUT axis, which is indicated by a green arrow. The x_DUT axis is indicated by a red arrow pointing along the bottom edge, and the z_DUT axis is indicated by a blue arrow pointing along the left edge.](ace13edeb79bdfa129ed84fbb4ac44e5_img.jpg) + +Figure 5.2.1-10: Sample DUT with assumed beam peak in the DUT's y direction. The diagram shows a rectangular DUT with a 3D beam pattern (colored lobes) originating from its top surface. The beam is oriented along the y\_DUT axis, which is indicated by a green arrow. The x\_DUT axis is indicated by a red arrow pointing along the bottom edge, and the z\_DUT axis is indicated by a blue arrow pointing along the left edge. + +**Figure 5.2.1-10: Sample DUT with assumed beam peak in the DUT's $y$ direction** + +Table 5.2.1-3: Ability of tracking a DUT reference direction + +| DUT Orientation
( $\theta, \phi$ ) | Offset Option: variable angular offset(s) between AoA1 and AoA2 | +|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $(0^\circ, 0^\circ)$ | Diagram showing a DUT at (0, 0) orientation. A blue beam labeled AoA1 points horizontally towards the DUT. A red beam labeled AoA2 points vertically towards the DUT. The DUT is mounted on a spherical grid with a local coordinate system. A yellow double-headed arrow indicates a variable angular offset between the two beams. | +| $(45^\circ, -45^\circ)$ | Diagram showing a DUT at (45, -45) orientation. The DUT is tilted on the spherical grid. A blue beam labeled AoA1 points horizontally towards the DUT. A red beam labeled AoA2 points vertically towards the DUT. A yellow double-headed arrow indicates a variable angular offset between the two beams. | + +Efforts for multi-AoA DL spherical coverage testing based on the assumptions that no prior knowledge of the performance of any panel/chain is available, e.g., beam peak directions of each panel, are significant and quantified next. The spherical coverage test for any multi-chain UE system configuration would require a spherical coverage test with $N*(N-1) \approx N^2$ AoA combinations. Here, $N$ is the minimum number of spherical coverage grid points. The effort in terms of minimum number of test points is quantified in Table 5.2.1-4 assuming that the same measurement grids/grid density are used as for legacy spherical coverage testing, defined in Clause M.3 of [6]. + +**Table 5.2.1-4: Test Effort Estimates for UE RF Systems with Full Degrees of Freedom for AoA.** + +| Power Class | Grid Type | Minimum Number of Spherical Coverage Test Points $N$ (single chain) as defined in M.3 of Error! Reference source not found. | Number of Spherical Coverage Test Points $N$ (multi chain) $N*(N-1)$ | +|-------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------| +| PC1 | constant density | 200 | 39,800 | +| PC3 | constant density | 180 | 32,220 | +| PC1/PC3 | constant-step size | 266 | 70,490 | + +The number of test points for this test approach is test time prohibitive given the very large number of test points. + +This measurement setup has its pros/cons summarized in Table 5.2.1-5. + +**Table 5.2.1-5: Overview of Measurement Setup** + +| Description | Full degrees of freedom for both AoAs | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Probe Offset Option | Variable Angular Offset(s) between AoA1 and AoA2 in the chamber. The angular separation between AoA1 and AoA2 can change during the testing | +| Pros |
  • - AoA2 can follow/track a specific reference direction
| +| Cons |
  • - Very high system complexity
  • - Existing systems cannot be re-used
  • - Large/very large chamber footprint/chamber heights
  • - Long development time/TTM
  • - Increase in MU/TT
| + +When the AoA2 probe/anchor probe is placed in the NF while supporting variable angular offsets, different system aspects must be taken into account. A sample measurement setup is shown in Figure 5.2.1-11 where both AoA1 (in FF) and AoA2 (in NF) have full degrees of freedom. + +![Diagram of an example measurement setup with AoA1 in the far field (FF) and AoA2/Anchor in the near field (NF).](e0f3606e9c9eee18bc68b713df4eda8a_img.jpg) + +The diagram illustrates a measurement setup within a spherical coordinate system. On the left, a blue probe labeled 'AoA1' is positioned in the far field, emitting a beam towards a central device. The device is mounted on a turntable with yellow arrows indicating its rotational degrees of freedom. Above the device, a green probe labeled 'Anchor' is mounted on a separate turntable, also with yellow arrows indicating its rotational degrees of freedom. A text box titled 'Notes:' lists the following points: + + +- AoA1 in FF; Anchor in NF +- Full degrees of freedom for Anchor probe +- Relative angular separation between Anchor and DUT is kept constant during the test + +Diagram of an example measurement setup with AoA1 in the far field (FF) and AoA2/Anchor in the near field (NF). + +**Figure 5.2.1-11: Example Measurement Setup with AoA2/Anchor in NF** + +An example implementation with the anchor probe mounted to the roll motor with independent positioning control (purple arrows) is shown in Figure 5.2.1-12. + +![Figure 5.2.1-12: Example Implementation of Measurement Setup with AoA2/Anchor in NF. The diagram shows a measurement setup with a probe antenna labeled 'AoA1' on the left, emitting a blue beam. On the right, a Device Under Test (DUT) is mounted on a 'Roll Stage/Motor' which is positioned on a rotating base. The DUT is shown with a coordinate system (X, Y, Z). The base has a yellow circular arrow indicating rotation. The DUT itself has a green circular arrow indicating rotation around its Z-axis. The setup is designed for Near Field (NF) measurements.](fed351d1b7c4568a439a8682c27f8cc3_img.jpg) + +Figure 5.2.1-12: Example Implementation of Measurement Setup with AoA2/Anchor in NF. The diagram shows a measurement setup with a probe antenna labeled 'AoA1' on the left, emitting a blue beam. On the right, a Device Under Test (DUT) is mounted on a 'Roll Stage/Motor' which is positioned on a rotating base. The DUT is shown with a coordinate system (X, Y, Z). The base has a yellow circular arrow indicating rotation. The DUT itself has a green circular arrow indicating rotation around its Z-axis. The setup is designed for Near Field (NF) measurements. + +**Figure 5.2.1-12: Example Implementation of Measurement Setup with AoA2/Anchor in NF** + +It should be noted that link antennas used in existing systems commonly do not have completely independent positioning control to support the full degrees of freedom. Link antennas are traditionally used to introduce an auxiliary communication link between the gNB and the DUT to avoid poor signal conditions in the non-tested DL or UL (for UL or DL measurements) and thus dropped calls. As no calibrated measurements are performed over this link, this signal path is generally never calibrated and the positioning and link probe requirements are very relaxed, e.g., large positioning uncertainty of the link antenna are acceptable, and the link antenna can be a low performance antenna coupler. Hence, such link antenna setups are not suitable for UE RF measurements. + +In [9], NF methodologies for single-UL and DL were investigated and eventually considered permitted methodologies for FR2 test cases that currently require large relaxations in RAN5 technical specifications. The EIS/EIRP measurements in the immediate NF require very accurate positioning of the NF probe, a high-end antenna probe, and the NF antenna pattern characterization. Given the need for accurate positioning and relatively large NF probe antennas supporting two principal polarizations, antenna(s) and fixturing will result in significant blocking in various AoA1 measurement directions. More importantly, to accurately determine EIS in the NF, it is required to calibrate out the offset of the active DUT antenna from the centre of QZ to account for the correct path loss between the NF measurement probe and the active antenna. This offset can either be determined using a set of measurements which need to be performed for each AoA1 measurement direction (black box approach of CFFNF in Clause 5.1.4 of [9]) or based on a rather extensive vendor declaration, e.g., location of all antenna panels and which antenna is active for any given measurement direction. Applying these NF findings to multi-Rx UE RF testing has the following implications: + +- The vendor declaration would require the exact location of all active antenna pairs for each AoA2 probe direction, i.e., an even more extensive vendor declaration than for single DL EIS measurements +- The NF probe needs to guarantee the same DL conditions to both active DUT receivers as a FF probe would since UE RF requirements are defined in the FF + +This measurement setup has its pros/cons summarized in Table 5.2.1-6. + +Table 5.2.1-6: Overview of Measurement Setup with AoA2 Probes in the NF + +| Description | Full Degrees of Freedom for AoA1 and AoA2 with AoA2 Probe in NF | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Probe Offset Option | Variable Angular Offset(s) between AoA1 and AoA2 in the chamber. The angular separation between AoA1 and AoA2 can change during the testing | +| Pros | - Existing systems could potentially be re-used after some modifications | +| Cons |
  • - Blocking of AoA1 in various directions by AoA2 probes
  • - Existing link antennas are not applicable; instead, very accurate positioning of the NF probe(s), high-end antenna probe(s), and the NF antenna pattern characterization are required
  • - Test-time intensive algorithms required to determine unknown offset of active antenna array(s) or
  • - Very extensive vendor declarations (location of all antenna panels and which sets of antenna panels are active for any given AoA2 measurement direction)
  • - The NF probe needs to guarantee the same DL conditions to both active DUT receivers as a FF probe would
| + +### 5.2.2 Measurement Setup with Full Degrees of Freedom for AoA1 with Fixed Angular Offset(s) Between AoA1 and AoA2 + +An alternate measurement setup considered for multi-AoA UE RF testing is based on full degrees of freedom for AoA1 with fixed angular offsets between AoA1 and AoA2 with the angular separations between AoA1 and AoA2(s) not changing during the testing. Example measurement setups are illustrated in Figure 5.2.2-1 where the (fixed) probe locations, the number of probes, and probe type (DFF, IFF) were selected arbitrarily. + +![Figure 5.2.2-1: Example measurement setups for two-simultaneous AoA testing supporting 3D AoAs for the 1st DL direction and discrete, fixed AoAs for the 2nd DL direction. The figure shows two spherical coordinate systems. The top diagram shows a central device with a blue probe labeled AoA1 on the left and four red probes labeled AoA2.1, AoA2.2, AoA2.3, and AoA2.4 positioned at various angles in the vertical plane. The bottom diagram shows the same device with the blue probe AoA1 on the left and four red probes labeled AoA2.1, AoA2.2, AoA2.3, and AoA2.4 positioned at various angles in the horizontal plane. Both diagrams include a grid representing the sphere and arrows indicating the direction of the probes.](67af94a7c462e85f3a310c9a45c0980d_img.jpg) + +Figure 5.2.2-1: Example measurement setups for two-simultaneous AoA testing supporting 3D AoAs for the 1st DL direction and discrete, fixed AoAs for the 2nd DL direction. The figure shows two spherical coordinate systems. The top diagram shows a central device with a blue probe labeled AoA1 on the left and four red probes labeled AoA2.1, AoA2.2, AoA2.3, and AoA2.4 positioned at various angles in the vertical plane. The bottom diagram shows the same device with the blue probe AoA1 on the left and four red probes labeled AoA2.1, AoA2.2, AoA2.3, and AoA2.4 positioned at various angles in the horizontal plane. Both diagrams include a grid representing the sphere and arrows indicating the direction of the probes. + +Figure 5.2.2-1: Example measurement setups for two-simultaneous AoA testing supporting 3D AoAs for the 1st DL direction and discrete, fixed AoAs for the 2nd DL direction. Top: probes in the vertical plane, Bottom: probes in the horizontal plane. + +This multi-AoA measurement setup is similar to baseline setups for 2 AoA RRM testing [7], see Clause B.2, as illustrated in Figure 5.2.2-2 or FR2 MIMO testing [8], see Clause B.2, as illustrated in Figure 5.2.2-3. + +![Three diagrams illustrating RRM baseline system setups: top (DFF), center (Enhanced IFF), and bottom (IFF+DFF). Each shows a DUT with coordinate axes x, y, z and various signal sources labeled P0, P30, P60, P90, P120, P150.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +The figure consists of three vertically stacked diagrams, each showing a Device Under Test (DUT) at the center. The DUT is represented by a grey circle containing a coordinate system with x (vertical), y (pointing into the page), and z (horizontal) axes. A curved arrow indicates rotation around the z-axis. Various signal sources, represented by black triangles, are positioned around the DUT and labeled with power levels: P0, P30, P60, P90, P120, and P150. + +- Top diagram (DFF setup):** All signal sources (P0, P30, P60, P90, P120, P150) are shown as individual triangles pointing towards the DUT. +- Center diagram (Enhanced IFF setup):** The signal sources are grouped into arcs. P150, P120, and P90 are on the left arc; P60, P30, and P0 are on the right arc. Small triangles point from these arcs towards the DUT. +- Bottom diagram (IFF+DFF setup):** Similar to the top setup, but the source P0 is represented by a curved arc instead of a triangle. + +Three diagrams illustrating RRM baseline system setups: top (DFF), center (Enhanced IFF), and bottom (IFF+DFF). Each shows a DUT with coordinate axes x, y, z and various signal sources labeled P0, P30, P60, P90, P120, P150. + +Figure 5.2.2-2: Example RRM baseline system with two simultaneously active AoA using top: DFF setup, centre: Enhanced IFF setup, bottom: IFF+DFF setup. + +![Diagram of an FR2 MIMO OTA 3D-MPAC system showing a Device Under Test (DUT) on a turntable with coordinate systems and a probe array.](b25cc68846b070bbe56a949b011ba91c_img.jpg) + +The diagram illustrates an FR2 MIMO OTA 3D-MPAC system. A Device Under Test (DUT), represented by a grey rectangular block, is mounted on a grey circular turntable. Two coordinate systems are shown: a fixed system with axes + + $x$ + +(red), + + $y$ + +(green), and + + $z$ + +(blue), and a DUT-centered system with axes + + $x_{CM}$ + +(red), + + $y_{CM}$ + +(green), and + + $z_{CM}$ + +(blue). The DUT is tilted at an angle. To the right of the DUT, a curved array of seven black circular probes is shown, representing the AoA2 probe array. + +Diagram of an FR2 MIMO OTA 3D-MPAC system showing a Device Under Test (DUT) on a turntable with coordinate systems and a probe array. + +**Figure 5.2.2-3: Example FR2 MIMO OTA 3D-MPAC system.** + +Due to the fixed offset between AoAs, the AoA2 probe cannot track/follow a DUT's reference direction, e.g., beam peak, during testing as illustrated in Table 5.2.2-1 for two different DUT orientations/test points. + +Table 5.2.2-1: Lack of ability of tracking a DUT reference direction + +| DUT Orientation
( $\theta, \phi$ ) | Offset Option: fixed angular offset(s) between AoA1 and AoA2 | +|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $(0^\circ, 0^\circ)$ | Diagram for DUT Orientation (0°, 0°) showing a device on a sphere with AoA1 and AoA2 antennas. A 3D diagram showing a rectangular device mounted on a wireframe sphere. A blue antenna labeled AoA1 is positioned to the left, emitting a beam towards the device. A red antenna labeled AoA2 is positioned above the device, also emitting a beam. The device has a local coordinate system with red, green, and blue arrows. A yellow circular arrow indicates rotation around the vertical axis. | +| $(45^\circ, -45^\circ)$ | Diagram for DUT Orientation (45°, -45°) showing the device tilted on a sphere with AoA1 and AoA2 antennas. A 3D diagram similar to the one above, but the rectangular device is tilted at an angle. The blue AoA1 antenna and red AoA2 antenna remain in the same positions. The local coordinate system on the device is also tilted, and the yellow rotation arrow is shown at an angle. | + +This measurement setup has its pros/cons summarized in Table 5.2.2-2. + +Table 5.2.2-2: Overview of Measurement Setup + +| Description | Full degrees of freedom for AoA1 with fixed angular offset(s) between AoA1 and AoA2 | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Probe Offset Option | Fixed Angular Offset(s) between AoA1 and AoA2 in the chamber. The angular separation between AoA1 and AoA2 is NOT changing during the testing | +| Pros |
  • - System complexity is manageable
  • - Existing systems, e.g., 2 AoA FR2 RRM, can be re-used (as long as common AoA2 probe locations are defined)
  • - Small chamber footprint/chamber heights
  • - Little to no development time/TTM
  • - Little to no impact in MU
  • - Multiple AoA1/AoA2 combinations can be tested
  • - A wide range of angular difference between AoA1 and AoA2 can readily be tested
  • - IFF methodology can be applied for each AoA probe for lowest MU and widest applicability.
| +| Cons |
  • - AoA2 cannot follow/track a specific reference direction
| + +This measurement setup was selected the baseline for multi-AoA UE RF testing. + +### 5.2.3 Measurement Setup with Full Degrees of Freedom for AoA1 with Variable Angular Offset(s) between AoA1 and AoA2 + +An alternate measurement setup considered for multi-AoA UE RF testing is based on full degrees of freedom for AoA1 with variable angular offsets between AoA1 and AoA2. At least one of the probes must utilize a 2-axis positioning system for full degrees of freedom as illustrated in Figure 5.2.3-1. The analyses for such system setup are very similar to the systems with full degrees of freedom for two AoAs in Clause 5.2.1. + +![Figure 5.2.3-1: Example DFF (left)/IFF (right) measurement setup to support full degrees of freedom with two-axis positioning system for one probe. The diagram shows two spherical coordinate systems. The left system (DFF) has a probe on a 2-axis positioning system (AoA1) and a second probe (AoA2) on a fixed stand. The right system (IFF) has a probe on a 2-axis positioning system (AoA1) and a second probe (AoA2) on a fixed stand, but with a different angular offset.](082ba09313df59d76a7bfbdde8ec877d_img.jpg) + +Figure 5.2.3-1: Example DFF (left)/IFF (right) measurement setup to support full degrees of freedom with two-axis positioning system for one probe. The diagram shows two spherical coordinate systems. The left system (DFF) has a probe on a 2-axis positioning system (AoA1) and a second probe (AoA2) on a fixed stand. The right system (IFF) has a probe on a 2-axis positioning system (AoA1) and a second probe (AoA2) on a fixed stand, but with a different angular offset. + +Figure 5.2.3-1: Example DFF (left)/IFF (right) measurement setup to support full degrees of freedom with two-axis positioning system for one probe. + +The positioning requirements to accurately position a probe along two principal axes in 3D yield a very high positioning complexity. A sample measurement setup is shown in Figure 5.2.3-2. The system implementation with AoA1 supporting the 2-axis positioner and with a single or multiple AoA2 probe(s) require very large systems since AoA2 probe(s) must be placed behind AoA1 probe as shown in Figure 5.2.3-3 to support free movement of AoA1 and no interference with AoA2. + +![Figure 5.2.3-2: Example DFF measurement setup with full degrees of freedom for AoA1 with variable angular offset(s) between AoA1 and AoA2. The diagram shows a central device under test (DUT) on a spherical grid. Four probes are positioned around it: AoA1 (blue) and AoA2.1 (red) are at the DFF range length, while AoA2.2 (red) and AoA2.3 (red) are placed beyond the DFF range length. A note box specifies: 'AoA1 placed at DFF range length', 'AoA2s placed beyond DFF range length to avoid collision of AoA1 with AoA2 probes', and 'AoA1 and AoA2 probes in FF'.](a8807f349e4e4d1d425fe4148f81741d_img.jpg) + +Figure 5.2.3-2: Example DFF measurement setup with full degrees of freedom for AoA1 with variable angular offset(s) between AoA1 and AoA2. The diagram shows a central device under test (DUT) on a spherical grid. Four probes are positioned around it: AoA1 (blue) and AoA2.1 (red) are at the DFF range length, while AoA2.2 (red) and AoA2.3 (red) are placed beyond the DFF range length. A note box specifies: 'AoA1 placed at DFF range length', 'AoA2s placed beyond DFF range length to avoid collision of AoA1 with AoA2 probes', and 'AoA1 and AoA2 probes in FF'. + +Figure 5.2.3-2: Example DFF measurement setup with full degrees of freedom for AoA1 with variable angular offset(s) between AoA1 and AoA2. + +![Figure 5.2.3-3: Illustration of IFF (left)/DFF (right) back-to-back probe placement. The left side shows IFF placement where AoA1 and AoA2 probes are placed back-to-back with a variable angular offset. The right side shows DFF placement where AoA1 and AoA2 probes are placed back-to-back with a variable angular offset.](810c7bd381c13911f72d22587ad08606_img.jpg) + +Figure 5.2.3-3: Illustration of IFF (left)/DFF (right) back-to-back probe placement. The left side shows IFF placement where AoA1 and AoA2 probes are placed back-to-back with a variable angular offset. The right side shows DFF placement where AoA1 and AoA2 probes are placed back-to-back with a variable angular offset. + +Figure 5.2.3-3: Illustration of IFF (left)/DFF (right) back-to-back probe placement. + +Size (width/depth/height) estimations for such DFF/IFF systems supporting the FR2-1 frequency range and devices up to a 40 cm diameter (40 cm QZ) are tabulated in Table 5.2.3-1. The increase in chamber sizes (footprint and heights) when compared to existing FR2 UE RF chambers is significant and existing chambers are not upgradeable to support full degrees of freedom. The lead times to develop such systems with full degrees of freedom could be quite significant and could thus delay the commercial adoption of these test cases. Additionally, the overall system complexities of such systems could further require an increase in measurement uncertainties (MUs) and thus test tolerances (TTs). + +Table 5.2.3-1: Size estimates for UE RF systems with Full Degrees of Freedom for AoA1 with Variable Angular Offset(s) between AoA1 and AoA2. + +| Test Method \ Size | Width [m] | Depth [m] | Height [m] | +|--------------------|-----------|-----------|------------| +| DFF | 3.6 | 3.6 | 3.6 | +| IFF | 6.6 | 6.6 | 6.6 | + +This measurement setup has its pros/cons summarized in Table 5.2.3-2. + +**Table 5.2.3-2: Overview of Measurement Setup with Probes in the FF** + +| Description | Full Degrees of Freedom for AoA1 with Variable Angular Offset(s) between AoA1 and AoA2 with Probes in FF | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Probe Offset Option | Variable Angular Offset(s) between AoA1 and AoA2 in the chamber. The angular separation between AoA1 and AoA2 is changing during the testing | +| Pros |
  • - The link/measurement conditions of AoA2 can be fixed during the testing
| +| Cons |
  • - AoA2 cannot follow/track a specific reference direction
  • - Very high system complexity
  • - Existing systems cannot be re-used
  • - Large/very large chamber footprint/chamber heights
  • - Long development time/TTM
  • - Increase in MU/TT
| + +### 5.2.4 Measurement Setup with Full Degrees of Freedom for AoA1 with Partial Freedom of Variable Angular Offset(s) between AoA1 and AoA2 + +An alternate measurement setup considered for multi-AoA UE RF testing is based on full degrees of freedom for AoA1 with partial freedom of variable angular offsets between AoA1 and AoA2. + +When all AoA1 and AoA2 probes are located in the Far Field (FF), the system complexity becomes manageable for the AoA2 positioner as AoA2 does not need to support full degrees of freedom; given the potentially large radial movements of AoA2 probe(s), the positioning complexities can still be pretty significant. A sample system is shown Figure 5.2.4-1 where the AoA1 and AoA2 probes need to be displaced from each other to avoid collisions, i.e., the chamber size estimates need to take the back-to-back probe placement illustrated in Figure 5.2.3-3 into account. As such, the size estimates with all probes in the FF are likely in the order of those listed in Table 5.2.3-1. This setup (with all probes in the FF) requires very large chambers, rather complex positioning needs for AoA2, lacks the ability to re-use existing test systems, and likes yields an increase of MUs and TTs. + +![Diagram of an example DFF measurement setup. A central Device Under Test (DUT) is shown within a spherical coordinate grid. AoA1 (blue probe) is positioned to the left, with a purple arrow indicating its rotation in the phi plane. AoA2 (red probe) is positioned above and to the right, with a yellow arrow indicating its rotation in the theta plane. A text box titled 'Notes:' lists several points: AoA1 & AoA2 in FF; Measurement distance of AoA2 must be greater than FF range length of AoA1 to avoid collision; AoA2/Anchor probe has independent positioning control to track one DUT rotation (yellow arrows); AoA2/Anchor probe does not rotate in phi, i.e., DUT rotates in phi (purple arrows) with anchor probe fixed in phi; Relative angular separation between AoA2/Anchor and DUT can be kept constant in theta but not phi during the test.](eaa5fbc353eb95b90302cfbe7c299576_img.jpg) + +Diagram of an example DFF measurement setup. A central Device Under Test (DUT) is shown within a spherical coordinate grid. AoA1 (blue probe) is positioned to the left, with a purple arrow indicating its rotation in the phi plane. AoA2 (red probe) is positioned above and to the right, with a yellow arrow indicating its rotation in the theta plane. A text box titled 'Notes:' lists several points: AoA1 & AoA2 in FF; Measurement distance of AoA2 must be greater than FF range length of AoA1 to avoid collision; AoA2/Anchor probe has independent positioning control to track one DUT rotation (yellow arrows); AoA2/Anchor probe does not rotate in phi, i.e., DUT rotates in phi (purple arrows) with anchor probe fixed in phi; Relative angular separation between AoA2/Anchor and DUT can be kept constant in theta but not phi during the test. + +**Figure 5.2.4-1: Example DFF measurement setup with full degrees of freedom for AoA1 with partial freedom of variable angular offset(s) between AoA1 and AoA2 with AoA2 in FF.** + +When AoA2 probes are placed in the NF of the DUT, e.g., using one or multiple link antennas as illustrated in the example illustration in Figure 5.2.4-2, similar aspects considered in the previous section apply here. The immediate seemingly advantage is that existing test systems could be used with some modifications to link antenna setups. However, as outlined in Clause 5.2.1, there are various disadvantages and testing considerations that need to be taken into account when the AoA2/anchor probe is in the NF + +#### Notes: + +- AoA1 in FF, while AoA2s/Anchors in NF +- AoA2/Anchor probes installed on $\theta$ positioner of DUT, i.e., anchor probes rotate in $\theta$ together with DUT (yellow arrows) +- AoA2/Anchor probes do not rotate in $\phi$ , i.e., DUT rotates in $\phi$ (purple arrows) with anchor probes fixed in $\phi$ +- Relative angular separation between NF AoAs/Anchors and DUT kept constant in $\theta$ but not $\phi$ during the test + +![Figure 5.2.4-2: Example DFF measurement setup with full degrees of freedom for AoA1 with partial freedom of variable angular offset(s) between AoA1 and AoA2 with AoA2 in NF. The diagram shows a spherical coordinate system with a Device Under Test (DUT) mounted on a turntable. An AoA1 probe is shown in the far field (FF) on the left, emitting a beam towards the DUT. The DUT is mounted on a turntable that can rotate in the phi (φ) direction, indicated by a purple curved arrow. The DUT is also mounted on a theta (θ) positioner, indicated by a yellow curved arrow. An anchor probe (AoA2) is shown in the near field (NF) on the right, mounted on the theta positioner. The diagram illustrates the relative angular separation between the DUT and the anchor probe, which is kept constant in theta but not in phi during the test.](e5c6de7d8ff5b0d75d5602d200b899f0_img.jpg) + +Figure 5.2.4-2: Example DFF measurement setup with full degrees of freedom for AoA1 with partial freedom of variable angular offset(s) between AoA1 and AoA2 with AoA2 in NF. The diagram shows a spherical coordinate system with a Device Under Test (DUT) mounted on a turntable. An AoA1 probe is shown in the far field (FF) on the left, emitting a beam towards the DUT. The DUT is mounted on a turntable that can rotate in the phi (φ) direction, indicated by a purple curved arrow. The DUT is also mounted on a theta (θ) positioner, indicated by a yellow curved arrow. An anchor probe (AoA2) is shown in the near field (NF) on the right, mounted on the theta positioner. The diagram illustrates the relative angular separation between the DUT and the anchor probe, which is kept constant in theta but not in phi during the test. + +Figure 5.2.4-2: Example DFF measurement setup with full degrees of freedom for AoA1 with partial freedom of variable angular offset(s) between AoA1 and AoA2 with AoA2 in NF. + +This measurement setup has its pros/cons summarized in Table 5.2.4-1. + +Table 5.2.4-1: Overview of Measurement Setup + +| Description | Measurement Setup with Full Degrees of Freedom for AoA1 with Partial Freedom of Variable Angular Offset(s) between AoA1 and AoA2 | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Probe Offset Option | Full degrees of freedom for AoA1 with partial freedom of variable angular offset(s) between AoA1 and AoA2, e.g., relative angular separation between anchor and DUT kept constant in $\theta$ but not $\phi$ ) | +| Pros | AoA1 & AoA2 probes in the FF
  • - N/A
AoA1 in FF with AoA2 probe(s)s in the NF
  • - Existing systems could potentially be re-used after some modifications
| +| Cons | AoA1 & AoA2 probes in the FF
  • - High system complexity
  • - Existing systems cannot be re-used
  • - Large/very large chamber footprint/chamber heights
  • - Long development time/TTM
  • - AoA2 cannot follow/track a specific reference direction
AoA1 in FF with AoA2 probe(s)s in the NF
  • - Blocking of AoA1 in various directions by AoA2 probes
  • - Existing link antennas are not applicable; instead, very accurate positioning of the NF probe(s), high-end antenna probe(s), and the NF antenna pattern characterization are required
  • - Test-time intensive algorithms required to determine unknown offset of active antenna array(s) or
  • - Very extensive vendor declarations (location of all antenna panels and which sets of antenna panels are active for any given AoA2 measurement direction)
  • - The NF probe needs to guarantee the same DL conditions to both active DUT receivers as a FF probe would
  • - AoA2 cannot follow/track a specific reference direction
| + +### 5.2.5 Measurement Setup with Full Degrees of Freedom for AoA1 with Fixed AoA2/Anchor in NF + +An alternate measurement setup considered for multi-AoA UE RF testing is based on full degrees of freedom for AoA1 with fixed AoA2/Anchor located in the NF, sample measurement setups are shown in Figure 5.2.5-1. + +![Figure 5.2.5-1: Example measurement setups with full degrees of freedom for AoA1 with fixed AoA2/Anchor in FF. The top diagram shows a DUT on a spherical grid with an AoA1 probe on the left and an anchor probe on the right. The bottom diagram shows a DUT on a 2-axis positioner with a reflector on the left and two anchor probes on the right.](759c7d62402f0b4651ddce292be5bdef_img.jpg) + +Notes: + +- AoA1 in FF, while Anchor in NF +- Anchor probe installed on $\theta$ positioner of DUT, i.e., anchor probe rotates in $\theta$ together with DUT (yellow arrows) +- Anchor probe does not rotate in $\phi$ , i.e., DUT rotates in $\phi$ (purple arrows) with anchor probe fixed in $\phi$ +- Relative angular separation between NF Anchor and DUT kept constant in $\theta$ but not $\phi$ during the test + +The top diagram illustrates a measurement setup where a Device Under Test (DUT) is mounted on a spherical grid. A blue probe labeled 'AoA1' is positioned on the left, pointing towards the DUT. A green probe labeled 'Anchor' is mounted on the DUT. Yellow curved arrows indicate rotation around the vertical axis ( $\theta$ ), and purple curved arrows indicate rotation around the horizontal axis ( $\phi$ ). + +The bottom diagram shows a different measurement setup. A DUT is mounted on a 'Positioner (2-axes)' which allows for rotation around the vertical axis ( $\theta_1$ ). A 'Reflector #1' is positioned on the left. On the right, there are two anchor probes: 'Anchor #1' (labeled '(Doesn't rotate with $\Phi_1$ )') and 'Anchor #1'' (labeled '(As the second anchor to maintain the link.)'). A coordinate system with 'QZ' and 'N' axes is shown. Blue curved arrows indicate rotation around the vertical axis ( $\theta_1$ ) and the horizontal axis ( $\Phi_1$ ). + +Figure 5.2.5-1: Example measurement setups with full degrees of freedom for AoA1 with fixed AoA2/Anchor in FF. The top diagram shows a DUT on a spherical grid with an AoA1 probe on the left and an anchor probe on the right. The bottom diagram shows a DUT on a 2-axis positioner with a reflector on the left and two anchor probes on the right. + +**Figure 5.2.5-1: Example measurement setups with full degrees of freedom for AoA1 with fixed AoA2/Anchor in FF.** + +Many of the aspects discussed in Clause 5.2.4 apply here. This measurement setup has its pros/cons summarized in Table 5.2.5-1. + +Table 5.2.5-1: Overview of Measurement Setup + +| Description | Full Degrees of Freedom for AoA1 with Fixed AoA2/Anchor in NF | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Probe Offset Option | Full degrees of freedom for AoA1 with partial freedom of variable angular offset(s) between AoA1 and AoA2 or fixed angular offset | +| Pros |
  • - Existing systems could potentially be re-used after some modifications
| +| Cons |
  • - Blocking of AoA1 in various directions by AoA2 probes
  • - Existing link antennas are not applicable; instead, very accurate positioning of the NF probe(s), high-end antenna probe(s), and the NF antenna pattern characterization are required
  • - Test-time intensive algorithms required to determine unknown offset of active antenna array(s) or
  • - Very extensive vendor declarations (location of all antenna panels and which sets of antenna panels are active for any given AoA2 measurement direction)
  • - The NF probe needs to guarantee the same DL conditions to both active DUT receivers as a FF probe would
  • - AoA2 cannot follow/track a specific reference direction
| + +### 5.2.6 Measurement Setup with Test Modes + +An alternate measurement setup considered for multi-AoA UE RF testing is based on full degrees of freedom for AoA1 with the use of test modes and performing tests sequentially. + +The first approach (Method 1) is illustrated in Figure 5.2.6-1. Though this methodology cannot test a behaviour of the DUT with two simultaneous DLs from different AoAs, the idea behind this approach is to introduce a test command to fix the active antenna panel in the DUT and evaluate the RF characteristics of the DUT without increasing the complexity of the 1-AoA IFF test system. This approach would require OEMs to declare the number of integrated antennas at a minimum and require a new test mode dedicated for just this one conformance test. + +![Figure 5.2.6-1: Example measurement setup (Method 1) with test mode to fix active antenna. The diagram shows two sequential test steps, Test #1 and Test #2, separated by a large green arrow. In Test #1, a Device Under Test (DUT) is shown with a yellow 'ON' label pointing to its top antenna panel. Green beams are shown emanating from this top panel towards a curved 'Reflector' above it. A dashed circle with a curved arrow indicates the DUT is rotating. In Test #2, the DUT is shown again with the yellow 'ON' label pointing to its right antenna panel. Green beams are shown emanating from this right panel towards the same 'Reflector'. The DUT is also shown rotating in this test step.](f2ea0f64a770b22b902820457d262265_img.jpg) + +Figure 5.2.6-1: Example measurement setup (Method 1) with test mode to fix active antenna. The diagram shows two sequential test steps, Test #1 and Test #2, separated by a large green arrow. In Test #1, a Device Under Test (DUT) is shown with a yellow 'ON' label pointing to its top antenna panel. Green beams are shown emanating from this top panel towards a curved 'Reflector' above it. A dashed circle with a curved arrow indicates the DUT is rotating. In Test #2, the DUT is shown again with the yellow 'ON' label pointing to its right antenna panel. Green beams are shown emanating from this right panel towards the same 'Reflector'. The DUT is also shown rotating in this test step. + +Figure 5.2.6-1: Example measurement setup (Method 1) with test mode to fix active antenna. + +The second approach (Method 2) is illustrated in Figure 5.2.6-1 and based on the following high-level procedure: + +- Perform Rx Beam peak search for $AoA_1$ . +- Connect the SS (System Simulator) with the DUT through the measurement antenna to form the RX beam towards the RX beam peak direction and respective polarization found for $AoA_1$ . +- SS activates the UE Beamlock Function (UBF) on $AoA_1$ . If necessary, switch the connection of the SS from the measurement antenna to the link antenna. +- Perform Rx Beam peak search for $AoA_2$ . + +The idea behind this approach is to augment/modify the existing UE Beamlock Function (UBF), i.e., lock a beam connected to one receiver while a second connection is still possible with freedom on the direction and/or panel used. + +![Figure 5.2.6-2: Example measurement setup (Method 2) with augmented UBF test mode. The diagram shows four sequential steps of a measurement setup. Step 1: A User Equipment (UE) is shown with a blue beam labeled 'AoA1' pointing towards a source. A small red antenna labeled 'Link' is also visible. Step 2: The UE is rotated, and the 'AoA1' beam is now orange. The 'Link' antenna is still visible. Step 3: The UE is rotated further, and a new blue beam labeled 'AoA2' is shown. The 'AoA1' beam is now orange and pointing away from the source. Step 4: The UE is rotated again, and the 'AoA2' beam is blue. The 'AoA1' beam is orange and pointing towards the source. The 'Link' antenna is visible in all steps.](dd5771673aececa53d42ece89218299d_img.jpg) + +1. AoA1 is first connected (without AoA2) towards the desired direction. E.g. beam peak found from single AoA testing. + +2. AoA1 is locked with UBF and the connection switched to a link antenna if necessary. + +3. AoA2 is tested over 3D, while AoA1 connection (with the beam locked with UBF) is maintained using a link antenna if necessary. + +Figure 5.2.6-2: Example measurement setup (Method 2) with augmented UBF test mode. The diagram shows four sequential steps of a measurement setup. Step 1: A User Equipment (UE) is shown with a blue beam labeled 'AoA1' pointing towards a source. A small red antenna labeled 'Link' is also visible. Step 2: The UE is rotated, and the 'AoA1' beam is now orange. The 'Link' antenna is still visible. Step 3: The UE is rotated further, and a new blue beam labeled 'AoA2' is shown. The 'AoA1' beam is now orange and pointing away from the source. Step 4: The UE is rotated again, and the 'AoA2' beam is blue. The 'AoA1' beam is orange and pointing towards the source. The 'Link' antenna is visible in all steps. + +**Figure 5.2.6-2: Example measurement setup (Method 2) with augmented UBF test mode.** + +Method 1 cannot verify the potential cross talk between two AoAs especially then the two AoAs are with a small angular separation. When performing sequential tests, the testing is not verifying the real performance of multi-Rx UEs. Method 2 does not suffer from these issues, but it was not concluded whether the measurements on the locked beam (i.e. AoA1 in Figure 5.2.6-2) may be impacted by the link antenna in the Near Field. + +### 5.2.7 Measurement Setup to reduce sensitivity to UE orientation in holder with full degrees of freedom for AoA1 with fixed angular offset(s) between AoA1 and AoA2 + +#### 5.2.7.1 Background and Motivation + +The system described in 5.2.2 has strong continuity with legacy systems, and therefore warrants further development. The system has reduced flexibility in placing source locations due to a fixed relative location of the sources. If this arrangement is used with a legacy 2 axis positioner, the UE can only be tested with some subset of all possible AoA pairs for a given AoA separation or offset. See Figure 5.2.7.1-1 for a graphical representation of the set of all possible testable AoA pairs by the system described in 5.2.2 in conjunction with a 2-axis positioner and a constant step-size scan. The restriction of the AoA pairings strictly towards one pole or the other can influence the measured 2AoA reception performance of the UE as a function of its orientation in the positioner during test. + +![Figure 5.2.7.1-1: A spherical coordinate system diagram showing grid points (red dots) and associated AoA pairs (blue segments) lying along meridians.](cea5c8233335c952c7f64d6a357f5d80_img.jpg) + +A diagram of a sphere with a grid of red dots representing grid point locations. Blue segments, representing AoA pairs, are shown as arrows pointing from these grid points along the meridians of the sphere. + +Figure 5.2.7.1-1: A spherical coordinate system diagram showing grid points (red dots) and associated AoA pairs (blue segments) lying along meridians. + +*Red dots are grid point locations* + +*For each grid point location, the companion AoA associated with the other TRP is along the direction indicated by the blue segments for the legacy 2-axis positioner.* + +**Figure 5.2.7.1-1: From the UE's perspective, AoA pairs lie along meridians of a spherical coordinate system for a test system with fixed offset between the sources and a 2-axis positioner.** + +Conceptually, robustness to orientation can be accomplished by adding test AoAs uniformly distributed on the sphere in more directions rather than just along the meridians. This necessitates using a 3-axis positioner in the agreed TE system rather than the legacy 2-axis positioner. Figure 5.2.7.1-2 graphically shows the intended goal of the added degree of freedom from the UE's perspective. + +*The orange circle represents the set of all AoAs that are separated from the any grid location by some fixed AoA separation.* + +*The intent is to sample the outcomes in spatially uniform directions to reduce bias.* + +![Figure 5.2.7.1-2: A diagram showing an orange circle representing the set of all AoAs separated from any grid location by a fixed AoA separation, with green arrows indicating additional directions.](ec07cb6b37a0878f3acbb201028080c1_img.jpg) + +A diagram of a sphere with an orange circle representing the set of all AoAs separated from any grid location by a fixed AoA separation. Green arrows indicate additional directions for AoA pairs, showing a more uniform distribution of test AoAs compared to the 2-axis positioner. + +Figure 5.2.7.1-2: A diagram showing an orange circle representing the set of all AoAs separated from any grid location by a fixed AoA separation, with green arrows indicating additional directions. + +**Figure 5.2.7.1-2: Scheme to combat bias introduced by AoA pairs limited to lie along meridians from the UE's perspective.** + +Recall that the legacy 2-axis positioner is only able to pair each grid point to AoAs along the blue arrows, respectively (see Figure 5.2.7.1-1). The 3-axis positioner is intended to allow each grid point to be additionally paired with AoAs along the green arrows. These additional directions essentially dismantle the restriction of having test AoA pairs exclusively along meridians of a spherical coordinate system from the UE's perspective. + +Simulated test runs with a UE with modules on adjacent confirms the intended enhancement removes sensitivity to UE orientation, see Figure 5.2.7.1-3. 'D' referenced in the figures is used in the sense of degree of freedom of the positioner, rather than spatial dimension. HH or VV refer to beam scanning directions for both modules, each assumed to be 4x1. + +![Four line graphs showing TE constrained overall 2TRP probability (%) vs AoA Sep (deg) for different positioner configurations. The top two graphs show results for a 2-axis positioner, while the bottom two show results for a 3-axis positioner. Each graph compares 'OR combining' and 'mean combining' methods across various antenna configurations (FrontTop HH, FrontTop VV, etc.). The 3-axis positioner graphs show significantly higher and more stable probabilities across the AoA range compared to the 2-axis positioner graphs. Blue arrows indicate the upgrade from 2-axis to 3-axis positioner.](853ef5420f0432e626e83987e3f38a0b_img.jpg) + +Orientation sensitivity from using a legacy 2-axis positioner. + +Positioner upgrade from 2-axis to 3-axis + +Four line graphs showing TE constrained overall 2TRP probability (%) vs AoA Sep (deg) for different positioner configurations. The top two graphs show results for a 2-axis positioner, while the bottom two show results for a 3-axis positioner. Each graph compares 'OR combining' and 'mean combining' methods across various antenna configurations (FrontTop HH, FrontTop VV, etc.). The 3-axis positioner graphs show significantly higher and more stable probabilities across the AoA range compared to the 2-axis positioner graphs. Blue arrows indicate the upgrade from 2-axis to 3-axis positioner. + +Figure 5.2.7.1-3: UE orientation sensitivity removal using a 3-axis positioner. + +#### 5.2.7.2 Implementation Direction + +The basic idea to implement this type of 3-axis positioner is an ‘inside’ 2-axis positioner that has similar functionality to the legacy positioner mounted to a fixed ‘outside’ roll-motor (‘outside’ to indicate it is not part of the positioner that would implement the basic scan). The ‘inside’ 2-axis positioner could be implemented as an azimuth-roll set-up (legacy geometry), an elevation-azimuth type positioner or other equivalent type. The ‘fixed’ aspect of the outside roll-motor refers to the fact that its stator would be statically positioned relative to the source locations, with its shaft axis pointed at one of the sources. This target source’s AoAs define the grid where the UE’s performance is evaluated. Figure 5.2.7.2-1 helps visualize the AoA pairings at each grid point. + +![A visualization of a spherical grid of red dots representing grid point locations. From each red dot, six blue line segments radiate outwards, representing the directions of test AoA pairs. The grid is denser at the top and bottom poles and more spread out at the equator.](5e16d3613b74558acc74ff6d7fd75fa9_img.jpg) + +A visualization of a spherical grid of red dots representing grid point locations. From each red dot, six blue line segments radiate outwards, representing the directions of test AoA pairs. The grid is denser at the top and bottom poles and more spread out at the equator. + +*Red dots are grid point locations where the regional probability is calculated.* + +*For each grid point location, a configurable number of AoA pairs is possible with a 3-axis positioner. Example shown with 6 pairs (blue segments indicate directions of test AoA pairs, second source locations suppressed for simplicity)* + +Figure 5.2.7.2-1: Visualization of AoA pairs associated with each point with the proposed 3-axis positioner + +One helpful aspect is that the 3-axis positioner no longer needs 180° swing of the azimuth motion from the ‘inside’ 2-axis positioner for each scanned hemisphere: It is possible for the inside positioner to use a 90° azimuth, 360° roll strategy if advantageous. + +Figure 5.2.7.2-2 helps with conceptual description of how the third degree of freedom in the positioner can be leveraged to achieve the grid and AoA pairings of 5.2.7.2-1. The blue and the green shafts represent the ‘inside’ 2-axis positioner, and they are together mounted on the outside roll motor shaft (red items). Two options are shown for the implementation of the ‘inside’ 2-axis positioner: azimuth-elevation and azimuth-roll. The latter option allows continuity with the legacy positioner grid and geometry. Detail design work is needed to adequately hide the motors to reduce the prospect of blockage, as well as other details like bringing the articulation axes closer; these are up to TE implementation. In either implementation the ‘outside’ roll motor is ground referenced like the sources and points to one of them, say S1 (grey body in the figures below). + +![Figure 5.2.7.2-2: Bias reducing 3-axis positioner concepts. The figure contains two diagrams. The top diagram shows a 3-axis positioner with a red 'outside' roll motor axis fixed towards one of the sources. It is actuated for multiple AoA pairs at the same grid point. The 'inside' 2-axis positioner is mounted to the roll motor and implemented as azimuth-elevation. The bottom diagram shows the same setup but the 'inside' 2-axis positioner is implemented as azimuth-roll. Both diagrams include labels for the 'outside' roll motor axis, the 'inside' 2-axis positioner, and the target source 'S1' at P0. A note indicates that objects are color-coded to indicate rigid interconnection.](dd7a15555767d4027adfa36fca520c50_img.jpg) + +‘Outside’ roll motor axis is fixed towards one of the sources. It is actuated for multiple AoA pairs at same grid point. + +‘inside’ 2-axis positioner mounted to roll motor, implemented as azimuth-elevation. + +Objects are color-coded to indicate rigid interconnection. + +Towards one of the sources ‘S1’ at P0 + +‘inside’ 2-axis positioner mounted to roll motor, implemented as azimuth-roll. + +Towards one of the sources ‘S1’ at P0 + +Figure 5.2.7.2-2: Bias reducing 3-axis positioner concepts. The figure contains two diagrams. The top diagram shows a 3-axis positioner with a red 'outside' roll motor axis fixed towards one of the sources. It is actuated for multiple AoA pairs at the same grid point. The 'inside' 2-axis positioner is mounted to the roll motor and implemented as azimuth-elevation. The bottom diagram shows the same setup but the 'inside' 2-axis positioner is implemented as azimuth-roll. Both diagrams include labels for the 'outside' roll motor axis, the 'inside' 2-axis positioner, and the target source 'S1' at P0. A note indicates that objects are color-coded to indicate rigid interconnection. + +**Figure 5.2.7.2-2: Bias reducing 3-axis positioner concepts.** + +The sequence of actuation can be considered equivalent to the following: + +- Step 1: The outside roll motor starts off at the zero-rotation location (as shown) and the ‘inside’ 2-axis positioner (blue and green axes) mounted to the roll motor is used to move S1 to the desired grid point from the UE’s perspective. +- Step 2: The outside roll-motor is then actuated over 360° with an arbitrary number of stops for measurement. Each stop represents an AoA pair with one source (S1) fixed in space +- Step 3: Once the outside roll-motor returns to the zero position, the ‘inside’ 2-axis positioner is used to move S1 to the next grid point +- Step 4: (Loop to step 2 until S1 is moved through all grid points). + +More realistic views of the positioner are shown in Figure 5.2.7.2-3. + +![Figure 5.2.7.2-3: More realistic depiction of an example implementation of the 3-axis positioner. The diagram shows three different views of a mechanical 3-axis positioner assembly. The top view shows the assembly aligned horizontally. The middle view shows it tilted. The bottom view shows it in a different orientation with circular source plates labeled S1 and S2. Labels indicate specific parts like the 'Outside' roll motor, 'Inside' 2-axis positioner roll motor, and Az hinge. Angles for Inside AZ, Inside Roll, and Outside Roll are provided as 30°, 45°, and 0° respectively.](483c43eac5aa582dfcb6e0aa8cee163f_img.jpg) + +Inside AZ: 30° + +Inside Roll: 45° + +Outside Roll: 0° + +'Outside' roll motor axis +is fixed towards S1. + +'Outside' roll motor + +Roll motor of 'Inside' 2- +axis positioner + +Az hinge of 'Inside' 2- +axis positioner + +S1 + +S2 + +SOURCE 1 +0 DEGREE + +SOURCE 2 +150 DEGREE + +Figure 5.2.7.2-3: More realistic depiction of an example implementation of the 3-axis positioner. The diagram shows three different views of a mechanical 3-axis positioner assembly. The top view shows the assembly aligned horizontally. The middle view shows it tilted. The bottom view shows it in a different orientation with circular source plates labeled S1 and S2. Labels indicate specific parts like the 'Outside' roll motor, 'Inside' 2-axis positioner roll motor, and Az hinge. Angles for Inside AZ, Inside Roll, and Outside Roll are provided as 30°, 45°, and 0° respectively. + +Figure 5.2.7.2-3: More realistic depiction of an example implementation of the 3-axis positioner. + +#### 5.2.7.3 Scan strategy to avoid source blocking + +The focus in this section is on an outside-roll-azimuth-roll positioner implementation, due to continuity of grid geometry with legacy positioners. Blocking is an important consideration for 2TRP connectivity. With the agreed TE with the legacy 2-axis positioner, both sources must be confined to a $180^\circ$ sector in the horizontal plane, to stay out of the $180^\circ$ swing of the azimuth motion of the positioner. With the proposed 3-axis positioner however, the roll axis of the outside motor is fixed to point to one of the sources, and the system loses its rotational symmetry. This means that the new positioner mechanism cannot be equally hidden from both sources for all AoA separations like the strategy used with the legacy positioner. There are two types of source blockages to navigate: + +1. Source blockage due to inside positioner mechanics. +2. Source blockage due to outside roll-motor arm to which the inside positioner is mounted. + +The blocking situation is more realistically depicted in Figure 5.2.7.3-1 in the form of a sequence of typical outside roll motor actuation. Note that azimuth and source separation sum up to $180^\circ$ , a relationship that is identified as the main condition for blocking to occur. This configuration depicts instances of both types of blockage. The red dotted highlight shows S2 blockage due to the inside positioner, while the blue dotted highlight shows S2 blockage due to the arm mounted to the outside motor. + +![Figure 5.2.7.3-1: Blockage issue with 3-axis positioner, viewed from azimuth axis. The diagram shows six states of a 3-axis positioner with 'SOURCE 2 150 DEGREE' at different 'Outside Roll' angles: 0°, 60°, 120°, 180°, 240°, and 300°. At 0° and 60°, there is no blockage. At 120° and 180°, the inside positioner (red dashed circle) blocks the line of sight to Source 2. At 240° and 300°, the outside motor arm (blue dashed circle) blocks the line of sight to Source 2. Arrows indicate the clockwise progression of the roll angle.](711ec8db6b4a2d4e24b0c0b2ed8853b8_img.jpg) + +Figure 5.2.7.3-1: Blockage issue with 3-axis positioner, viewed from azimuth axis. The diagram shows six states of a 3-axis positioner with 'SOURCE 2 150 DEGREE' at different 'Outside Roll' angles: 0°, 60°, 120°, 180°, 240°, and 300°. At 0° and 60°, there is no blockage. At 120° and 180°, the inside positioner (red dashed circle) blocks the line of sight to Source 2. At 240° and 300°, the outside motor arm (blue dashed circle) blocks the line of sight to Source 2. Arrows indicate the clockwise progression of the roll angle. + +**Figure 5.2.7.3-1: Blockage issue with 3-axis positioner, viewed from azimuth axis.** + +Blockage due to the insider positioner: + +Even if the reduced azimuth motion (per hemisphere) of the inside 2-axis positioner is reduced to $[0-90^\circ]$ , the outside roll motor would swing the 'inside' positioner into the LOS of the second source for source separations of $90^\circ$ or more. Conceptually, the blockage occurs when the second source (S2) approaches the pole of the grid where the inside positioner is located. This blockage condition is not due to the choice of positioner, but instead due to the choice to test each point with AoA pairs in more directions than just along meridians. + +This situation manifests for all grid points whose theta coordinate approaches the supplementary angle $(180-x)$ to the source separation angle. Furthermore, blocking may only occur for some subset of outside-motor roll angles. See Figure + +5.2.7.3-2. For perspective, it is useful to remember that this blockage condition is not due to the choice of positioner, but instead due to the choice to test each point with AoA pairs in more directions. + +![Diagram illustrating the blockage issue due to the inside positioner of a 3-axis positioner. The diagram shows a User Equipment (UE) mounted on an 'Inside positioner' which points it to a specific grid point. A vertical dashed red line represents the 'External roll motor axis'. A blue arrow labeled 'S1' points down towards the UE. A blue circle represents the 'Effective locus of S2 as external roll motor is actuated', with several 'Example S2 locations where UE 2TRP functionality is verified' marked by blue stars. A green oval at the bottom right indicates 'Outside-motor roll angles that cause S2 blockage', with a black dot representing the 'South pole'.](2aeb2e98986fac7c66e17a4e6afbe5c0_img.jpg) + +Diagram illustrating the blockage issue due to the inside positioner of a 3-axis positioner. The diagram shows a User Equipment (UE) mounted on an 'Inside positioner' which points it to a specific grid point. A vertical dashed red line represents the 'External roll motor axis'. A blue arrow labeled 'S1' points down towards the UE. A blue circle represents the 'Effective locus of S2 as external roll motor is actuated', with several 'Example S2 locations where UE 2TRP functionality is verified' marked by blue stars. A green oval at the bottom right indicates 'Outside-motor roll angles that cause S2 blockage', with a black dot representing the 'South pole'. + +**Figure 5.2.7.3-2: Blockage issue due to inside positioner of a 3-axis positioner, viewed from (the inside) azimuth axis of the example implementation.** + +The fraction of AoA pairs where one source is near the south pole is relatively small and can be identified a-priori for each hemisphere scan and re-assigned to the opposite hemisphere scan. For the opposite hemisphere scan, the second source would flip over to near the north pole and the first source would also flip but it will remain clear of the south pole, provided AoA separation is not $180^\circ$ . So, a blocked AoA in one hemisphere scan is not blocked during the opposite hemisphere scan. Another detail is that for the blocked AoA pairs, the second source location is now the one near the north pole (originally designated S1). It may not fall on the originally chosen grid, but that should not matter to the 'inside' positioner. The external roll motor can then position the flipped first source (originally designated S2) at the desired location in the southern hemisphere. Since the AoA pair reorganization can be done a-priori, there is no foreseen test time impact. + +To summarize, a 'no-block' strategy to dodge the inside positioner can be implemented by exchanging some pre-identified test AoAs across the two hemisphere scans. Since the blocked region is essentially due to the mechanical outline of the inside positioner, it is up to TE implementation to treat the considerations presented below: + +1. Various motion transfer schemes can be leveraged to reduce the shadow region, which reduces the number of AoA pairs that may be blocked. +2. It would be mathematically consistent to re-orient the sample points on the circle (locus of second source during the outside motor roll) to reduce blockage. i.e., move all stops for the external roll motor for that grid point by some convenient angle to avoid the shadow region. + +Blockage due to outside positioner arm: + +As the outside motor's is stopped at any grid point, some stops will cause the mechanics carrying the inside positioner to block the source. The strategy is to leverage multiple different mechanical configurations to achieve the same UE pointing direction relative to the two sources. An example is shown below for a given UE pointing direction. + +| TE coordinates | Option 1 | Option 2 | +|----------------------|----------|----------------------| +| Outside roll (deg) | $\alpha$ | $\alpha + 180^\circ$ | +| Inside azimuth (deg) | $\beta$ | $-\beta$ | +| Inside roll (deg) | $\gamma$ | $\gamma + 180^\circ$ | + +Since the same orientation is achieved with two different outside roll settings, the TE retains a way to dodge a blockage condition induced by the outside motor angular position. The following views of the system in a configuration that demonstrate the blocking issue endemic to testing each point with at least 3 equally spatially distributed AoA pairs. + +Sources are shown as flat discs. Source separation angle is $150^\circ$ . Chosen grid point for illustration is S1 at $\theta=30^\circ$ , $\phi = -45^\circ$ . Note that azimuth and source separation sum up to $180^\circ$ , a relationship that is identified as the main condition for blocking to occur. Geometries are not optimized for blockage reduction. + +The highlighted view is an example of how the outside motor arm can impede line of sight between the UE and source S2. In the illustration below, an alternative set of coordinates achieve the same UE orientation relative to the sources, but the arm is no longer in a blocking location. This strategy is an example of a no-block strategy for the outside motor. Figure 5.2.7.3-3 shows the strategy to allow the outside motor to dodge the line of sight to source S2 for the example 3-axis implementation. On the right is the blocking condition, note orange arm is in line of sight to source S2. On the left is an equivalent UE pointing direction but without blockage from the outside motor arm. + +![Figure 5.2.7.3-3: No-block strategy for outside motor arm the example implementation of a 3-axis positioner. The figure shows two 3D models of a user equipment (UE) with a motor arm. In the left model, the UE is pointing towards a source (S1) and the motor arm is positioned such that it does not block the line of sight to another source (S2). In the right model, the UE is pointing towards the same source (S1) but the motor arm is positioned such that it blocks the line of sight to source S2. The angular coordinates for each model are provided below the models.](33fcd48ebd2456ea5e49fade0d4c7f75_img.jpg) + +Internal AZ: $-30^\circ$ +Internal Roll: $225^\circ$ +External Roll: $300^\circ$ + +Internal AZ: $30^\circ$ +Internal Roll: $45^\circ$ +External Roll: $120^\circ$ + +Figure 5.2.7.3-3: No-block strategy for outside motor arm the example implementation of a 3-axis positioner. The figure shows two 3D models of a user equipment (UE) with a motor arm. In the left model, the UE is pointing towards a source (S1) and the motor arm is positioned such that it does not block the line of sight to another source (S2). In the right model, the UE is pointing towards the same source (S1) but the motor arm is positioned such that it blocks the line of sight to source S2. The angular coordinates for each model are provided below the models. + +**Figure 5.2.7.3-3: No-block strategy for outside motor arm the example implementation of a 3-axis positioner.** + +To summarize, a 'no-block' strategy to dodge the outside arm can be implemented by taking advantage of the fact that there are multiple unique positioner settings to achieve the same UE pointing direction. + +#### 5.2.7.4 Pros and Cons + +**Table 5.2.7.4-1: Overview of positioner enhancement** + +| Description | Full degrees of freedom for AoA1 with fixed angular offset(s) between AoA1 and AoA2 | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Probe Offset Option | Fixed Angular Offset(s) between AoA1 and AoA2 in the chamber. The angular separation between AoA1 and AoA2 is NOT changing during the testing | +| Positioner | 3-axis such that AoA pairs at each grid point are not strictly limited to poles of the spherical coordinate system in the UE's perspective | +| Pros |
  • - Removes sensitivity to UE orientation by enabling test AoA pairs for any separation that are not limited by some geometric constraint.
  • - Enhanced positioner enables full backward compatibility with legacy requirements and techniques
  • - Small chamber footprint/chamber heights
  • - Multiple AoA1/AoA2 combinations can be tested
  • - A wide range of angular difference between AoA1 and AoA2 can readily be tested
| +| Cons |
  • - System complexity high, due to 3-axis positioner
  • - Existing systems cannot be retrofit easily
  • - MU may have to revisited
  • - Blockage-dodging strategy is a stronger function of TE implementation than with the 2-axis positioner case
| + +## 5.3 Test System Aspects + +### 5.3.1 Absolute Probe Locations + +A sample system with three different probe locations as shown in Figure 5.3.1-1 is investigated to provide detailed justification to define absolute probe locations/directions for Multi-AoA UE RF testing. The sample implementation has a 2-axis positioning system for the DUT to implement a 3D scan and three probes in the $x$ , $y$ , and $z$ axes with the assumption that AoA1 is along $z$ and AoA2 along $x$ or $y$ . The DL directions perceived by the DUT from each probe are illustrated with red, green, and blue spheres on the DUT grid in the $x$ , $y$ , and $z$ directions, respectively, for this initial test point of $(\theta, \phi) = (0^\circ, 0^\circ)$ . + +![Figure 5.3.1-1: Sample measurement setup with three fixed probe locations for initial test point of (0°, 0°).](403affb63bbbac5175158681bb89f8a3_img.jpg) + +A 3D diagram illustrating a sample measurement setup. A Device Under Test (DUT) is mounted on a 2-axis positioning system, represented by a wireframe sphere. The DUT is shown in three orientations, each with a colored sphere indicating the perceived downlink (DL) direction: a green sphere for the + + $y$ + +-axis direction, a red sphere for the + + $x$ + +-axis direction, and a blue sphere for the + + $z$ + +-axis direction. The DUT is mounted on a grey base, and the positioning system includes a vertical column and a horizontal arm. A small blue cone is shown to the left of the DUT. + +Figure 5.3.1-1: Sample measurement setup with three fixed probe locations for initial test point of (0°, 0°). + +**Figure 5.3.1-1: Sample measurement setup with three fixed probe locations for initial test point of $(0^\circ, 0^\circ)$** + +For the sample multi-AoA system investigated, the angular difference between AoA1 ( $z$ direction) and AoA2 ( $x$ direction) and between AoA1 ( $z$ direction) and AoA2 ( $y$ direction) is $90^\circ$ in both cases. One could seemingly argue that the roll motor of the DUT (rotation around the DUT $z$ axis) makes it irrelevant whether AoA2 is along the $y$ or the $x$ axis. However, once the device is rotated in 3D, i.e., $\theta$ and $\phi$ , this argument is no longer applicable which is further analysed and illustrated below. For a second sample device orientation of $(\theta, \phi) = (45^\circ, -45^\circ)$ , the perceived DL directions are illustrated on the rotated DUT grid in Figure 5.3.1-2. Clearly, a $90^\circ$ rotation of the device around its $z$ axis would no longer map the green sphere onto the red sphere. + +![Figure 5.3.1-2: Sample measurement setup with three fixed probe locations for test point of (45°, -45°).](c8f2f0357b99e801b1b0bb5faecf0787_img.jpg) + +The diagram shows a 3D measurement setup. A spherical grid representing the test points is mounted on a turntable. A Device Under Test (DUT) is positioned at the center of the sphere. Three probes are shown: one aligned with the z-axis (blue), one aligned with the y-axis (green), and one aligned with the x-axis (red). The DUT is shown in three orientations, corresponding to the different probe locations. The turntable is mounted on a base, and the DUT is mounted on the turntable. + +Figure 5.3.1-2: Sample measurement setup with three fixed probe locations for test point of (45°, -45°). + +**Figure 5.3.1-2: Sample measurement setup with three fixed probe locations for test point of (45°, -45°)** + +It is now assumed that the test points in 3D are based on a constant-step size grid with 266 unique grid points ( $\Delta\theta=\Delta\phi=15^\circ$ ), i.e., as defined for PC1 & PC3 spherical coverage test cases for 1-DL in Clause 5.3 of [6], or on a constant density grid with 200 unique grid points, i.e., as defined for PC1 spherical coverage test cases for 1-DL in Clause 5.3 of [6]. These test/grid points are visualized in Table 5.3.1-1. + +**Table 5.3.1-1: Visualization of spherical coverage test/grid points** + +![Visualization of a constant-step size grid with 266 unique grid points. The grid points are distributed across a sphere with a regular pattern of latitude and longitude lines. Visualization of a constant density grid with 200 unique grid points. The grid points are distributed across a sphere with a more uniform density compared to the constant-step size grid.](b88b618bb8863766bd545c6bfb31f850_img.jpg) + +| Constant-step size grid with 266 unique grid points ( $\Delta\theta=\Delta\phi=15^\circ$ ) | Constant density grid with 200 unique grid points | +|--------------------------------------------------------------------------------------------|---------------------------------------------------| +| | | + +Visualization of a constant-step size grid with 266 unique grid points. The grid points are distributed across a sphere with a regular pattern of latitude and longitude lines. Visualization of a constant density grid with 200 unique grid points. The grid points are distributed across a sphere with a more uniform density compared to the constant-step size grid. + +When all spherical coverage grid points are sampled with $0^\circ \leq \theta \leq 180^\circ$ and $0^\circ \leq \phi \leq 360^\circ$ , the DL directions perceived by the UE from the various probes are plotted in Table 5.3.1-2. Clearly, these results show vastly different results. + +- For the probe aligned with the z axis, the perceived DL directions match the test points. +- For the probe aligned with the y axis, the DUT only perceives the DL in a single plane only, i.e., the DUT's xy plane. This is due to the turntable axis of the OTA positioner aligned with the y axis, i.e., the turntable rotation merely changes the polarization but not the DL direction with this probe. The roll motor, i.e., the rotation of the DUT around its z axis, only adjusts the DL direction within the xy plane. +- For the AoA2 probe aligned with the x axis, the DL directions are perceived from different directions in $(\theta, \phi)$ but limited to a single hemisphere only. + +The plots of the perceived DL directions from different, fixed probes demonstrate the need to define the absolute probe locations/directions for UE RF systems so that different test systems yield the same results. + +**Table 5.3.1-2: DL directions perceived by the DUT from probes in the $x$ , $y$ , and $z$ axes.** + +| Probe Along Direction | DL Directions perceived by DUT with constant-step size grid with 266 unique grid points ( $\Delta\theta=\Delta\phi=15^\circ$ ) | DL Directions perceived by DUT with constant density grid with 200 unique grid points | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $z$ | 3D plot of a sphere with a grid of 266 blue probe points. The points are concentrated along the z-axis and in the xy-plane. | 3D plot of a sphere with 200 blue probe points distributed more uniformly across the surface than in the constant-step grid. | +| $y$ | 3D plot of a sphere with green probe points concentrated along the y-axis. | 3D plot of a sphere with green probe points concentrated along the y-axis, showing a different distribution pattern than the constant-step grid. | +| $x$ | 3D plot of a sphere with red probe points concentrated along the x-axis. | 3D plot of a sphere with red probe points concentrated along the x-axis, showing a different distribution pattern than the constant-step grid. | + +### 5.3.2 Minimum and Maximum Angular Separation between Probes + +Due to the finite size of the probes, the minimum angular separation between probes will be limited to prevent collisions and thus prevent a “full” degree of rotation freedom of one AoA unless probes are placed back-to-back as illustrated in Figure 5.2.3-3 which on the other hand introduces blocking effects. + +The minimum angular separation between neighbouring reflectors is larger than the minimum separation between two regular millimetre-wave probes as illustrated in Figure 5.3.2-1. It is estimated that the minimum angular separation between two IFF probes is about $30^\circ$ while the minimum angular separation between two DFF probes is about $5^\circ$ . + +Although DFF is one of the permitted methodologies for FR2 OTA testing [10], IFF is the de-facto reference methodology for FR2 OTA measurements. To enable the applicability of IFF to multi-AoA UE RF testing [3, 12], the largest minimum angular separation of DFF and IFF must be selected, i.e., the minimum angular separation between probes must be $30^\circ$ . + +![Illustration of minimum angular separations between IFF and DFF probes.](cf504c5f59d17aff988b7c672a829d5c_img.jpg) + +The diagram illustrates the minimum angular separation for two types of probe configurations. The top part, labeled 'IFF', shows two vertically aligned, elongated, curved probes. A horizontal dashed line extends from the center of the lower probe, and a diagonal dashed line extends from the top probe to the right. The angle between these two lines is labeled 'Min. Angular Separation'. The bottom part, labeled 'DFF', shows two vertically aligned, horn-shaped probes. Similarly, a horizontal dashed line extends from the center of the lower probe, and a diagonal dashed line extends from the top probe to the right. The angle between these two lines is also labeled 'Min. Angular Separation'. + +Illustration of minimum angular separations between IFF and DFF probes. + +**Figure 5.3.2-1: Illustration of minimum angular separations between IFF (top) and DFF probes.** + +The maximum angular separation between probes could be as large as $180^\circ$ . However, this angular separation would result in significant blocking between one AoA probe and the DUT positioner, as illustrated in Figure 5.3.2-2, and the line-of-sight path between both probes also introduce a significant amount of coupling. It was therefore suggested to limit the maximum angular separation between probes/AoAs to $150^\circ$ (blue reflector/probe in Figure 5.3.2-2). + +![Figure 5.3.2-2: Illustration of maximum proposed angular separation including blocking for angular separation of 180°. The diagram shows a central probe on a sphere with a coordinate system (x, y, z). Two reflectors are positioned at 180° angular separation. The left reflector is black and has a label 'Angular separation of 180° results in blocking with positioner'. The right reflector is red and has a label 'Min. Angular Separation: 30°'. Above the sphere, a blue reflector is shown with a label 'Angular Separation: 150°'.](c0f6ba43542fddfee899e1af9cbd720d_img.jpg) + +Figure 5.3.2-2: Illustration of maximum proposed angular separation including blocking for angular separation of 180°. The diagram shows a central probe on a sphere with a coordinate system (x, y, z). Two reflectors are positioned at 180° angular separation. The left reflector is black and has a label 'Angular separation of 180° results in blocking with positioner'. The right reflector is red and has a label 'Min. Angular Separation: 30°'. Above the sphere, a blue reflector is shown with a label 'Angular Separation: 150°'. + +**Figure 5.3.2-2: Illustration of maximum proposed angular separation including blocking for angular separation of 180°.** + +Additionally, placing two reflectors opposite to each other will yield higher variations in field/power measurements within the QZ caused by reflections from one reflector facing another head on. As illustrated in Figure 5.3.2-3, the two dark grey reflectors with 180° separation illuminate each other with plane waves, i.e., without much attenuation; scattering from the metal surfaces including edges of the reflector will thus reflect energy back towards the source probe. On the other hand, the cross coupling between the reflector at 0° and the red or blue reflectors is minimized as they are not in each other's direct path. It was argued that the cross coupling between the two opposing reflectors should be insignificant given the large separation and thus large path losses. However, the reflectors are in each other's collimated beam's path, i.e., signal from the right reflector arriving at the left reflector should not have experienced much of an attenuation when compared to the signal at the QZ. + +It should furthermore be highlighted that 2 AoA RRM systems currently limit the maximum separation between probes to 150° [12], specifically Table A.3.15.3-1. + +Requiring a 180° separation for multi-AoA Rx testing would therefore not allow a re-use of existing 2 AoA RRM systems as they would not be able to support the larger separation. + +![Figure 5.3.2-3: Illustration of maximum proposed angular separation including blocking for angular separation of 180°. The diagram shows two reflectors at 180° angular separation (black) and a probe at 150° angular separation (blue). A red reflector is shown with a label 'Min. Angular Separation: 30°'. A central region is labeled 'QZ with Radius R'. The diagram illustrates the blocking and cross-coupling effects between the reflectors and the probe.](9642ee15d719705144037077981aaa99_img.jpg) + +Figure 5.3.2-3: Illustration of maximum proposed angular separation including blocking for angular separation of 180°. The diagram shows two reflectors at 180° angular separation (black) and a probe at 150° angular separation (blue). A red reflector is shown with a label 'Min. Angular Separation: 30°'. A central region is labeled 'QZ with Radius R'. The diagram illustrates the blocking and cross-coupling effects between the reflectors and the probe. + +**Figure 5.3.2-3: Illustration of maximum proposed angular separation including blocking for angular separation of 180°.** + +### 5.3.3 Impact of Probe Locations and 3D Scans on DL Directions + +A full 3D scan, typically required for beam peak searches, spherical coverage test cases and TRP measurements, can be performed in various ways as illustrated in Table 5.3.3-1. Here, a single-probe, combined-axes OTA system with the probe aligned in the $z$ direction is shown with two different methodologies to achieve a full 3D UE rotation/scan: + +- full rotation in $\phi$ (around $z$ axis) and half rotation in $\theta$ (around $y$ axis) as shown in left column +- full rotation in $\theta$ (around $y$ axis) and half rotation in $\phi$ (around $z$ axis) as shown in right column + +As shown in the table for the constant-step size grid with 312 grid points ( $\Delta\theta=\Delta\phi=15^\circ$ , 266 of which are unique due to the redundant points at the poles) on top or the constant-density grid with 200 grid points on the bottom, either approach will yield the same test point coverage. + +Table 5.3.3-1: 3D scan implementations and resulting coverage using single-probe system + +| | Single-probe system configuration with 3D scan using full rotation in $\phi$ and half rotation in $\theta$ | Single-probe system configuration with 3D scan using full rotation in $\theta$ and half rotation in $\phi$ | +|-------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| System Configuration | Diagram of a probe (P0) on a rotating stand. The stand has a vertical axis (z) and a horizontal axis (y). The probe is mounted on a sphere. Arrows indicate rotation: 'theta rotation' around the y-axis and 'phi rotation' around the z-axis. | Diagram of a probe (P0) on a rotating stand. The stand has a vertical axis (y) and a horizontal axis (z). The probe is mounted on a sphere. Arrows indicate rotation: 'theta rotation' around the y-axis and 'phi rotation' around the z-axis. | +| Constant-Step Size Grid with 312 grid points ( $\Delta\theta=\Delta\phi=15^\circ$ ); 266 unique grid points | A sphere with a grid of 312 points. The points are distributed in a regular pattern across the sphere's surface. A coordinate system (x, y, z) is shown with the y-axis pointing up, the z-axis pointing left, and the x-axis pointing right. | | +| Constant Density Grid with 200 grid points | A sphere with a grid of 200 points. The points are distributed in a regular pattern across the sphere's surface. A coordinate system (x, y, z) is shown with the y-axis pointing up, the z-axis pointing left, and the x-axis pointing right. | | + +It was agreed to define absolute probe locations as different 2D planes containing the various AoA probes were shown to have vastly different effects on the perceived DL directions by the UE, see Clause 5.3.1. For simplicity, sample test systems with just 4 total probes (1 AoA1 probe and 3 AoA2 probes) are considered next. Here, the AoA2 probes are displaced by $60^\circ$ (P60), $120^\circ$ (P120), and $150^\circ$ (P150) from the AoA1 probe placed along the z direction (P0). As illustrated in Table 5.3.3-2, one system configuration has the AoA2 probes aligned in the xz plane (left), and another system configuration has the AoA2 probes aligned in the yz plane (right). Aside from studying the effect of different probe locations on the perceived DL directions, the two different 3D approaches are investigated as well, i.e., by rotating the device a full turn in $\phi$ (rotation axis z) and a half turn in $\theta$ (rotation axis y) as shown the top of Table 5.3.3-2 and alternatively, a full turn in $\theta$ (rotation axis y) and a half turn in $\phi$ (rotation axis z) as shown the bottom of Table 5.3.3-2. + +The following analyses for constant step-size grids take into account that multiple measurements at the pole for P0 are performed; while these measurements yield unique DL directions for P0, they translate to non-unique DL directions for P60, P120, and P150. + +Table 5.3.3-2: System configurations with probes in the xz plane (left) and yz plane (right). 3D scan performed with full rotation in $\phi$ and half rotation in $\theta$ (top) and with full rotation in $\theta$ and half rotation in $\phi$ (bottom) + +| | Probes in the xz plane | Probes in the yz plane | +|----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3D Scan: full rotation in $\phi$ and half rotation in $\theta$ |

Image: Diagram of a probe on a rotating sphere for 3D scan with full rotation in phi and half rotation in theta. The sphere is mounted on a stand and has a coordinate system (x, y, z) with DUT and AUT. Probes P0, P60, P120, and P150 are shown in the xz plane. Yellow arrows indicate rotation around the y-axis (full rotation in phi) and the z-axis (half rotation in theta).

|

Image: Diagram of a probe on a rotating sphere for 3D scan with full rotation in phi and half rotation in theta. The sphere is mounted on a stand and has a coordinate system (x, y, z) with DUT and AUT. Probes P0, P60, P120, and P150 are shown in the yz plane. Yellow arrows indicate rotation around the y-axis (full rotation in phi) and the z-axis (half rotation in theta).

| +| 3D Scan: full rotation in $\theta$ and half rotation in $\phi$ |

Image: Diagram of a probe on a rotating sphere for 3D scan with full rotation in theta and half rotation in phi. The sphere is mounted on a stand and has a coordinate system (x, y, z) with DUT and AUT. Probes P0, P60, P120, and P150 are shown in the xz plane. Yellow arrows indicate rotation around the z-axis (full rotation in theta) and the y-axis (half rotation in phi).

|

Image: Diagram of a probe on a rotating sphere for 3D scan with full rotation in theta and half rotation in phi. The sphere is mounted on a stand and has a coordinate system (x, y, z) with DUT and AUT. Probes P0, P60, P120, and P150 are shown in the yz plane. Yellow arrows indicate rotation around the z-axis (full rotation in theta) and the y-axis (half rotation in phi).

| + +The system configurations with full rotation in $\phi$ and half rotation in $\theta$ and the perceived DL directions are further illustrated in Table 5.3.3-3 for a constant-step size grid with 312 grid points and in Table 5.3.3-4 for a constant density grid with 200 grid points. Similarly, the system configurations with full rotation in $\theta$ and half rotation in $\phi$ and the perceived DL directions are further illustrated in Table 5.3.3-5 for a constant-step size grid with 312 grid points and in Table 5.3.3-6 for a constant density grid with 200 grid points. The following observations can be made from these results: + +- Probes aligned in the $yz$ plane introduce large keep-out areas for the angular coverage/DL directions towards each pole. +- With full rotation in $\phi$ and half rotation in $\theta$ , probes aligned in the $xz$ plane introduce a conical sector towards the pole at $\theta=0^\circ$ with no angular coverage/DL directions for offset probes. +- Constant density grids do not maintain the constant density coverage/DL direction distribution for probes offset from P0, a higher density of DL directions is observed especially near the poles. +- When probes are aligned in the $xz$ plane, constant-step size grids maintain the constant-step size distribution of DL directions for probes offset from P0. +- Probes aligned in the $xz$ plane generally provide a wider angular coverage for AoA2 DL directions when compared to probes aligned in the $yz$ plane. +- With full rotation in $\theta$ and half rotation in $\phi$ and probes aligned in the $xz$ plane, the AoA2 DL directions are distributed in 3D without a conical region with lack of coverage. +- Only with full rotation in $\theta$ and half rotation in $\phi$ , probes aligned in the $xz$ plane, and constant-step size grids, uniform angular coverage/DL directions is achieved, i.e., the distribution of DL directions for all probes on the $xz$ plane match the distribution of grid points. + +Based on the observations made in this section, the following decisions were made: + +- For optimized AoA1 and AoA2 test point/perceived DL direction coverage, apply a full rotation in $\theta$ and a half rotation in $\phi$ . +- For optimized AoA1 and AoA2 test point/perceived DL direction coverage, utilize constant-step size grids only. +- For optimized AoA1 and AoA2 test point/perceived DL direction coverage, place the AoA2 probes in the $xz$ plane + +Table 5.3.3-3: DL directions perceived by the DUT from two different system configurations with AoA2 to AoA1 probe offsets of 60°, 120°, and 150° with a constant-step-size grid using 312 grid points ( $\Delta\theta=\Delta\phi=15^\circ$ ). Full rotation in $\phi$ and half rotation in $\theta$ . + +| | Probes in the xz plane | Probes in the yz plane | +|---------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| System Configuration with full rotation in $\phi$ and half rotation in $\theta$ | Diagram of system configuration with probes in the xz plane. A DUT is mounted on a turntable. Probes P0, P60, P120, and P150 are positioned in the xz plane. Arrows indicate full rotation in the phi direction and half rotation in the theta direction. | Diagram of system configuration with probes in the yz plane. A DUT is mounted on a turntable. Probes P0, P60, P120, and P150 are positioned in the yz plane. Arrows indicate full rotation in the phi direction and half rotation in the theta direction. | +| DL Directions perceived by DUT from Probe P60 | 3D sphere showing the DL directions perceived by the DUT from Probe P60 when probes are in the xz plane. The sphere is covered with a grid of blue dots representing the 312 grid points. | 3D sphere showing the DL directions perceived by the DUT from Probe P60 when probes are in the yz plane. The sphere is covered with a grid of blue dots representing the 312 grid points. | + +![3D sphere with red dots representing DL directions for Probe P120 (left view). 3D sphere with red dots representing DL directions for Probe P120 (right view). 3D sphere with green dots representing DL directions for Probe P150 (left view). 3D sphere with green dots representing DL directions for Probe P150 (right view).](75b9cb95f5815d6f3bbe57020a049504_img.jpg) + +| | | | +|------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DL Directions perceived by DUT from Probe P120 | A 3D sphere with a gray grid. Red dots are distributed across the sphere's surface, representing downlink directions. A coordinate system is overlaid with a green Y-axis pointing up, a blue Z-axis pointing left, and a red X-axis pointing diagonally down-right. | A 3D sphere with a gray grid. Red dots are distributed across the sphere's surface, representing downlink directions. A coordinate system is overlaid with a green Y-axis pointing up, a blue Z-axis pointing left, and a red X-axis pointing diagonally down-right. | +| DL Directions perceived by DUT from Probe P150 | A 3D sphere with a gray grid. Green dots are distributed across the sphere's surface, representing downlink directions. A coordinate system is overlaid with a green Y-axis pointing up, a blue Z-axis pointing left, and a red X-axis pointing diagonally down-right. | A 3D sphere with a gray grid. Green dots are distributed across the sphere's surface, representing downlink directions. A coordinate system is overlaid with a green Y-axis pointing up, a blue Z-axis pointing left, and a red X-axis pointing diagonally down-right. | + +3D sphere with red dots representing DL directions for Probe P120 (left view). 3D sphere with red dots representing DL directions for Probe P120 (right view). 3D sphere with green dots representing DL directions for Probe P150 (left view). 3D sphere with green dots representing DL directions for Probe P150 (right view). + +Table 5.3.3-4: DL directions perceived by the DUT from two different system configurations with AoA2 to AoA1 probe offsets of 60°, 120°, and 150° with a constant density grid using 200 grid points. Full rotation in $\phi$ and half rotation in $\theta$ . Full rotation in $\phi$ and half rotation in $\theta$ . + +| | Probes in the xz plane | Probes in the yz plane | +|---------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| System Configuration with full rotation in $\phi$ and half rotation in $\theta$ | Diagram of a DUT on a turntable with probes P0, P60, P120, and P150 in the xz plane. The DUT is a rectangular block on a sphere, which is on a turntable. Probes are positioned at 0, 60, 120, and 150 degrees in the xz plane. Arrows indicate rotation around the y-axis. | Diagram of a DUT on a turntable with probes P0, P60, P120, and P150 in the yz plane. The DUT is a rectangular block on a sphere, which is on a turntable. Probes are positioned at 0, 60, 120, and 150 degrees in the yz plane. Arrows indicate rotation around the y-axis. | +| DL Directions perceived by DUT from Probe P60 | 3D plot of a sphere with a grid of 200 blue dots representing DL directions perceived by the DUT from Probe P60 when probes are in the xz plane. The sphere is shown with x, y, and z axes. | 3D plot of a sphere with a grid of 200 blue dots representing DL directions perceived by the DUT from Probe P60 when probes are in the yz plane. The sphere is shown with x, y, and z axes. | + +![3D sphere with red dots representing DL directions for Probe P120, left view. 3D sphere with red dots representing DL directions for Probe P120, right view. 3D sphere with green dots representing DL directions for Probe P150, left view. 3D sphere with green dots representing DL directions for Probe P150, right view.](fd8369b549b3d1a5c848cbd83659cae9_img.jpg) + +| | | | +|------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DL Directions perceived by DUT from Probe P120 | A 3D sphere with a white grid. Red dots are concentrated on the right side of the sphere. A coordinate system is shown with a green Y-axis pointing up, a blue Z-axis pointing left, and a red X-axis pointing down-right. | A 3D sphere with a white grid. Red dots are concentrated on the right side of the sphere. A coordinate system is shown with a green Y-axis pointing up, a blue Z-axis pointing left, and a red X-axis pointing down-right. | +| DL Directions perceived by DUT from Probe P150 | A 3D sphere with a white grid. Green dots are distributed across the entire surface of the sphere. A coordinate system is shown with a green Y-axis pointing up, a blue Z-axis pointing left, and a red X-axis pointing down-right. | A 3D sphere with a white grid. Green dots are distributed across the entire surface of the sphere. A coordinate system is shown with a green Y-axis pointing up, a blue Z-axis pointing left, and a red X-axis pointing down-right. | + +3D sphere with red dots representing DL directions for Probe P120, left view. 3D sphere with red dots representing DL directions for Probe P120, right view. 3D sphere with green dots representing DL directions for Probe P150, left view. 3D sphere with green dots representing DL directions for Probe P150, right view. + +Table 5.3.3-5: DL directions perceived by the DUT from two different system configurations with AoA2 to AoA1 probe offsets of 60°, 120°, and 150° with a constant-step size grid using 312 grid points ( $\Delta\theta=\Delta\phi=15^\circ$ ). Full rotation in $\theta$ and half rotation in $\phi$ . + +| | Probes in the xz plane | Probes in the yz plane | +|---------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| System Configuration with full rotation in $\theta$ and half rotation in $\phi$ | Diagram of system configuration with probes in the xz plane. A Device Under Test (DUT) is mounted on a rotating platform. Probes P0, P60, P120, and P150 are shown in the xz plane. The DUT is shown with a coordinate system (x, y, z) and a rotation arrow around the y-axis. | Diagram of system configuration with probes in the yz plane. A Device Under Test (DUT) is mounted on a rotating platform. Probes P0, P60, P120, and P150 are shown in the yz plane. The DUT is shown with a coordinate system (x, y, z) and a rotation arrow around the y-axis. | +| DL Directions perceived by DUT from Probe P60 | 3D sphere showing the DL directions perceived by the DUT from Probe P60 when probes are in the xz plane. The sphere is covered with a grid of blue dots representing the 312 grid points. | 3D sphere showing the DL directions perceived by the DUT from Probe P60 when probes are in the yz plane. The sphere is covered with a grid of blue dots representing the 312 grid points. | + +![3D sphere visualization for Probe P120 showing red dots distributed across the surface, with a coordinate system (y-axis green, z-axis blue, x-axis red). 3D sphere visualization for Probe P120 showing red dots concentrated in specific regions, viewed from a different angle, with coordinate axes. 3D sphere visualization for Probe P150 showing green dots distributed across the surface, with a coordinate system (y-axis green, z-axis blue, x-axis red). 3D sphere visualization for Probe P150 showing green dots distributed across the surface, viewed from a different angle, with coordinate axes.](201de44da5d99899a8cf58eac2fa7bc9_img.jpg) + +| | | | +|-------------------------------------------------------|--|--| +|

DL Directions perceived by DUT from Probe P120

| | | +|

DL Directions perceived by DUT from Probe P150

| | | + +3D sphere visualization for Probe P120 showing red dots distributed across the surface, with a coordinate system (y-axis green, z-axis blue, x-axis red). 3D sphere visualization for Probe P120 showing red dots concentrated in specific regions, viewed from a different angle, with coordinate axes. 3D sphere visualization for Probe P150 showing green dots distributed across the surface, with a coordinate system (y-axis green, z-axis blue, x-axis red). 3D sphere visualization for Probe P150 showing green dots distributed across the surface, viewed from a different angle, with coordinate axes. + +Table 5.3.3-6: DL directions perceived by the DUT from two different system configurations with AoA2 to AoA1 probe offsets of 60°, 120°, and 150° with a constant density grid using 200 grid points. Full rotation in $\theta$ and half rotation in $\phi$ . + +| | Probes in the xz plane | Probes in the yz plane | +|---------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| System Configuration with full rotation in $\theta$ and half rotation in $\phi$ | Diagram of a DUT on a turntable with probes P0, P60, P120, and P150 in the xz plane. The DUT is a rectangular block on a sphere, mounted on a turntable. Probes are positioned at 0, 60, 120, and 150 degrees in the xz plane. Arrows indicate rotation around the y-axis. | Diagram of a DUT on a turntable with probes P0, P60, P120, and P150 in the yz plane. The DUT is a rectangular block on a sphere, mounted on a turntable. Probes are positioned at 0, 60, 120, and 150 degrees in the yz plane. Arrows indicate rotation around the y-axis. | +| DL Directions perceived by DUT from Probe P60 | 3D plot of a sphere with a grid of 200 blue dots representing DL directions perceived by the DUT from Probe P60 when probes are in the xz plane. The dots are concentrated on the left side of the sphere. | 3D plot of a sphere with a grid of 200 blue dots representing DL directions perceived by the DUT from Probe P60 when probes are in the yz plane. The dots are distributed across the sphere. | + +![3D sphere visualization for Probe P120 (View 1) 3D sphere visualization for Probe P120 (View 2) 3D sphere visualization for Probe P150 (View 1) 3D sphere visualization for Probe P150 (View 2)](b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg) + +| | | | +|-------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

DL Directions perceived by DUT from Probe P120

|

A 3D sphere with a gray latitude/longitude grid. Numerous red dots are scattered across the surface, primarily concentrated on the left and top-left regions from this perspective. A 3D coordinate system is centered in the sphere: a green arrow labeled 'y' points upward, a blue arrow labeled 'z' points to the left, and a red arrow labeled 'x' points towards the bottom right.

|

A second view of the 3D sphere for Probe P120. The red dots are densely clustered in the upper-left quadrant of the sphere's visible surface. The coordinate system remains consistent: green 'y' axis up, blue 'z' axis left, and red 'x' axis down-right.

| +|

DL Directions perceived by DUT from Probe P150

|

A 3D sphere with a gray grid, similar to the one above but with green dots. The green dots are distributed more uniformly across the visible surface compared to the red dots, though still slightly more concentrated in the upper hemisphere. The coordinate system (y-up, z-left, x-down-right) is present.

|

A second view of the 3D sphere for Probe P150. The green dots are spread across the surface, showing a wide distribution of directions. The coordinate system axes (y, z, x) are clearly marked.

| + +3D sphere visualization for Probe P120 (View 1) 3D sphere visualization for Probe P120 (View 2) 3D sphere visualization for Probe P150 (View 1) 3D sphere visualization for Probe P150 (View 2) + +### 5.3.4 DL Polarizations Perceived by the UE + +The DL polarizations perceived by the UE from various probes placed in different locations and 2D planes is investigated in this Annex. For better visualization purposes, a coarse measurement grid with 84 grid points for the constant-step size grid ( $\Delta\theta=\Delta\phi=30^\circ$ ) and 50 grid points for the constant density grid is considered. + +The DL directions and polarizations perceived by the DUT for a sample system with the AoA1 probe in the $z$ direction and AoA2 probes in the $x$ and $y$ directions are presented in Table 5.3.4-1 for just the constant-step size grid. The magenta arrows demonstrate the $\theta$ polarization while the orange arrows demonstrate the $\phi$ polarization with respect to the probe antenna/system coordinate system. Clearly, for the probes placed in the $z$ and $x$ directions, the DL polarizations w.r.t. the DUT coordinate system are preserved, i.e., the probe antenna DL $\theta/\phi$ polarization matches the DUT $\theta/\phi$ polarization. However, for the probe along the $y$ axis, the DL polarization perceived by the DUT changes depending on grid point. Similar observations can be made for a system configuration with multiple AoA2 probes placed on the $xz$ and the $yz$ planes. The system configurations with full rotation in $\phi$ and half rotation in $\theta$ and the perceived DL directions are further illustrated in Table 5.3.4-2 for the constant-step size grid and in Table 5.3.4-3 for the constant density grid. Similarly, the system configurations with full rotation in $\theta$ and half rotation in $\phi$ and the perceived DL directions are further illustrated in Table 5.3.4-4 for the constant-step size grid and in Table 5.3.4-5 for the constant density grid. + +These results again show that the probe antenna DL $\theta/\phi$ -polarizations from AoA2 probes (w.r.t. the system coordinate system) are preserved only when the AoA2 probes are placed in the $xz$ plane, i.e., antenna DL $\theta/\phi$ polarizations map to DUT $\theta/\phi$ polarizations, while this is no longer the case for AoA2 probes are placed in the $yz$ plane, i.e., probe antenna DL $\theta/\phi$ polarizations generally map to a combination of DUT $\theta/\phi$ polarizations. + +Table 5.3.4-1: DL direction and polarizations perceived by the DUT from probes in the x, y, and z axes. + +| | DL Directions perceived by DUT with constant-step size grid with 84 grid points ( $\Delta\theta=\Delta\phi=30^\circ$ ). Full rotation in $\phi$ and half rotation in $\theta$ . | DL Directions perceived by DUT with constant-step size grid with 84 grid points ( $\Delta\theta=\Delta\phi=30^\circ$ ). Full rotation in $\theta$ and half rotation in $\phi$ . | +|---------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| System Configuration | Diagram of a Device Under Test (DUT) on a turntable. A probe is positioned along the z-axis. The DUT is mounted on a sphere with a grid. Arrows indicate rotation: a green arrow for full rotation in phi and a yellow arrow for half rotation in theta. | Diagram of a Device Under Test (DUT) on a turntable. A probe is positioned along the z-axis. The DUT is mounted on a sphere with a grid. Arrows indicate rotation: a green arrow for full rotation in theta and a yellow arrow for half rotation in phi. | +| DL Directions and Polarizations perceived by DUT from Probe along z | 3D plot of the sphere showing the perceived DL directions and polarizations from a probe along the z-axis for the first configuration (full rotation in phi, half in theta). The grid points are marked with colored arrows representing different polarizations. | 3D plot of the sphere showing the perceived DL directions and polarizations from a probe along the z-axis for the second configuration (full rotation in theta, half in phi). The grid points are marked with colored arrows representing different polarizations. | + +![3D sphere plot showing DL directions and polarizations for a probe along the y-axis. The sphere has a grid and axes x (red), y (green), and z (blue). Several colored starburst markers are scattered across the sphere's surface. 3D sphere plot showing DL directions and polarizations for a probe along the y-axis. The sphere has a grid and axes x (red), y (green), and z (blue). Several colored starburst markers are scattered across the sphere's surface. 3D sphere plot showing DL directions and polarizations for a probe along the x-axis. The sphere has a grid and axes x (red), y (green), and z (blue). Colored starburst markers are arranged in a circular pattern around the equator. 3D sphere plot showing DL directions and polarizations for a probe along the x-axis. The sphere has a grid and axes x (red), y (green), and z (blue). Colored starburst markers are arranged in a circular pattern around the equator.](730b6615db6d402580db1024a7f4e163_img.jpg) + +| | | | +|----------------------------------------------------------------------------|--|--| +|

DL Directions and Polarizations perceived by DUT from Probe along y

| | | +|

DL Directions and Polarizations perceived by DUT from Probe along x

| | | + +3D sphere plot showing DL directions and polarizations for a probe along the y-axis. The sphere has a grid and axes x (red), y (green), and z (blue). Several colored starburst markers are scattered across the sphere's surface. 3D sphere plot showing DL directions and polarizations for a probe along the y-axis. The sphere has a grid and axes x (red), y (green), and z (blue). Several colored starburst markers are scattered across the sphere's surface. 3D sphere plot showing DL directions and polarizations for a probe along the x-axis. The sphere has a grid and axes x (red), y (green), and z (blue). Colored starburst markers are arranged in a circular pattern around the equator. 3D sphere plot showing DL directions and polarizations for a probe along the x-axis. The sphere has a grid and axes x (red), y (green), and z (blue). Colored starburst markers are arranged in a circular pattern around the equator. + +Table 5.3.4-2: DL direction perceived by the DUT from two different system configurations with AoA2 to AoA1 probe offsets of 60°, 120°, and 150° with a constant-step size spherical coverage grid using 84 grid points ( $\Delta\theta=\Delta\phi=30^\circ$ ). Full rotation in $\phi$ and half rotation in $\theta$ . + +| | Probes in the xz plane | Probes in the yz plane | +|---------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| System Configuration with full rotation in $\phi$ and half rotation in $\theta$ | Diagram of system configuration with probes in the xz plane. A DUT is mounted on a rotating platform. Probes P0, P60, P120, and P150 are shown in the xz plane. A yellow circular arrow indicates full rotation in phi, and a green circular arrow indicates half rotation in theta. | Diagram of system configuration with probes in the yz plane. A DUT is mounted on a rotating platform. Probes P0, P60, P120, and P150 are shown in the yz plane. A yellow circular arrow indicates full rotation in phi, and a green circular arrow indicates half rotation in theta. | +| DL Directions perceived by DUT from Probe P60 | 3D plot of DL directions perceived by DUT from Probe P60 for the xz plane configuration. The plot shows a sphere with a grid of 84 points. Arrows indicate the perceived directions from probe P60. | 3D plot of DL directions perceived by DUT from Probe P60 for the yz plane configuration. The plot shows a sphere with a grid of 84 points. Arrows indicate the perceived directions from probe P60. | + +![3D sphere plot for Probe P120 showing DL directions with red and yellow arrows on a coordinate grid. Alternative 3D sphere plot for Probe P120 showing a denser distribution of DL directions. 3D sphere plot for Probe P150 showing DL directions with green and yellow arrows on a coordinate grid. Alternative 3D sphere plot for Probe P150 showing a denser distribution of DL directions.](9c888dd6588358989047de6ced8b2bdb_img.jpg) + +| | | | +|-------------------------------------------------------|--|--| +|

DL Directions perceived by DUT from Probe P120

| | | +|

DL Directions perceived by DUT from Probe P150

| | | + +3D sphere plot for Probe P120 showing DL directions with red and yellow arrows on a coordinate grid. Alternative 3D sphere plot for Probe P120 showing a denser distribution of DL directions. 3D sphere plot for Probe P150 showing DL directions with green and yellow arrows on a coordinate grid. Alternative 3D sphere plot for Probe P150 showing a denser distribution of DL directions. + +Table 5.3.4-3: DL directions and polarizations perceived by the DUT from two different system configurations with AoA2 to AoA1 probe offsets of 60°, 120°, and 150° with a constant density spherical coverage grid using 50 grid points. Full rotation in $\phi$ and half rotation in $\theta$ . Full rotation in $\phi$ and half rotation in $\theta$ . + +| | Probes in the xz plane | Probes in the yz plane | +|---------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| System Configuration with full rotation in $\phi$ and half rotation in $\theta$ | Diagram of system configuration with probes in the xz plane. A Device Under Test (DUT) is mounted on a rotating platform. Three probes, P0, P60, and P150, are shown in the xz plane. P0 is on the left, P60 is at the bottom, and P150 is on the right. Arrows indicate rotation around the y-axis. | Diagram of system configuration with probes in the yz plane. A Device Under Test (DUT) is mounted on a rotating platform. Three probes, P0, P60, and P150, are shown in the yz plane. P0 is on the left, P60 is at the top, and P150 is at the top-right. Arrows indicate rotation around the y-axis. | +| DL Directions perceived by DUT from Probe P60 | 3D sphere showing DL directions and polarizations perceived by the DUT from Probe P60 when probes are in the xz plane. The sphere has a grid and colored arrows representing different directions and polarizations. | 3D sphere showing DL directions and polarizations perceived by the DUT from Probe P60 when probes are in the yz plane. The sphere has a grid and colored arrows representing different directions and polarizations. | + +![3D sphere plot for Probe P120 showing DL directions with a dense grid of arrows. 3D sphere plot for Probe P120 showing DL directions with a sparse grid of arrows. 3D sphere plot for Probe P150 showing DL directions with a dense grid of arrows. 3D sphere plot for Probe P150 showing DL directions with a sparse grid of arrows.](7b96fce298a23fd76a01ff6c176c1059_img.jpg) + +| | | | +|------------------------------------------------|--|--| +| DL Directions perceived by DUT from Probe P120 | | | +| DL Directions perceived by DUT from Probe P150 | | | + +3D sphere plot for Probe P120 showing DL directions with a dense grid of arrows. 3D sphere plot for Probe P120 showing DL directions with a sparse grid of arrows. 3D sphere plot for Probe P150 showing DL directions with a dense grid of arrows. 3D sphere plot for Probe P150 showing DL directions with a sparse grid of arrows. + +Table 5.3.4-4: DL directions and polarizations perceived by the DUT from two different system configurations with AoA2 to AoA1 probe offsets of 60°, 120°, and 150° with a constant-step size spherical coverage grid using 84 grid points ( $\Delta\theta=\Delta\phi=30^\circ$ ). Full rotation in $\theta$ and half rotation in $\phi$ . + +| | Probes in the xz plane | Probes in the yz plane | +|---------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| System Configuration with full rotation in $\theta$ and half rotation in $\phi$ | Diagram of system configuration with probes in the xz plane. A DUT is mounted on a rotating sphere. Probes P0, P60, P120, and P150 are shown in the xz plane. The sphere is rotating around the y-axis. | Diagram of system configuration with probes in the yz plane. A DUT is mounted on a rotating sphere. Probes P0, P60, P120, and P150 are shown in the yz plane. The sphere is rotating around the y-axis. | +| DL Directions perceived by DUT from Probe P60 | 3D plot showing DL directions and polarizations perceived by the DUT from Probe P60 when probes are in the xz plane. The plot shows a sphere with grid points and arrows indicating directions and polarizations. | 3D plot showing DL directions and polarizations perceived by the DUT from Probe P60 when probes are in the yz plane. The plot shows a sphere with grid points and arrows indicating directions and polarizations. | + +![3D sphere plot for Probe P120, left view. Shows a grid of points with arrows indicating directions. A green Y-axis, blue Z-axis, and red X-axis are shown. The sphere is shaded gray with a white grid. 3D sphere plot for Probe P120, right view. Similar to the left view but with a different perspective, showing the distribution of directions from Probe P120. 3D sphere plot for Probe P150, left view. Shows a grid of points with arrows indicating directions. A green Y-axis, blue Z-axis, and red X-axis are shown. The sphere is shaded gray with a white grid. 3D sphere plot for Probe P150, right view. Similar to the left view but with a different perspective, showing the distribution of directions from Probe P150.](509a054727400bc6d424bb2a559b8cfc_img.jpg) + +| | | | +|------------------------------------------------|--|--| +| DL Directions perceived by DUT from Probe P120 | | | +| DL Directions perceived by DUT from Probe P150 | | | + +3D sphere plot for Probe P120, left view. Shows a grid of points with arrows indicating directions. A green Y-axis, blue Z-axis, and red X-axis are shown. The sphere is shaded gray with a white grid. 3D sphere plot for Probe P120, right view. Similar to the left view but with a different perspective, showing the distribution of directions from Probe P120. 3D sphere plot for Probe P150, left view. Shows a grid of points with arrows indicating directions. A green Y-axis, blue Z-axis, and red X-axis are shown. The sphere is shaded gray with a white grid. 3D sphere plot for Probe P150, right view. Similar to the left view but with a different perspective, showing the distribution of directions from Probe P150. + +Table 5.3.4-5: DL directions and polarizations perceived by the DUT from two different system configurations with AoA2 to AoA1 probe offsets of 60°, 120°, and 150° with a constant density spherical coverage grid using 50 grid points. Full rotation in $\theta$ and half rotation in $\phi$ . + +| | Probes in the xz plane | Probes in the yz plane | +|---------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| System Configuration with full rotation in $\theta$ and half rotation in $\phi$ |

Image: Diagram of system configuration with probes in the xz plane. A Device Under Test (DUT) is mounted on a rotating platform. Probes P0, P60, P120, and P150 are positioned in the xz plane. The DUT is shown with a coordinate system (x, y, z) and a spherical grid. Arrows indicate the rotation of the DUT.

|

Image: Diagram of system configuration with probes in the yz plane. A Device Under Test (DUT) is mounted on a rotating platform. Probes P0, P60, P120, and P150 are positioned in the yz plane. The DUT is shown with a coordinate system (x, y, z) and a spherical grid. Arrows indicate the rotation of the DUT.

| +| DL Directions perceived by DUT from Probe P60 |

Image: Diagram showing the DL directions perceived by the DUT from Probe P60 when probes are in the xz plane. The DUT is shown with a coordinate system (x, y, z) and a spherical grid. Arrows indicate the perceived directions from Probe P60.

|

Image: Diagram showing the DL directions perceived by the DUT from Probe P60 when probes are in the yz plane. The DUT is shown with a coordinate system (x, y, z) and a spherical grid. Arrows indicate the perceived directions from Probe P60.

| + +![3D sphere plot for Probe P120 showing DL directions with yellow, green, and red arrows on a grid. 3D sphere plot for Probe P120 showing DL directions with yellow, green, and red arrows on a grid. 3D sphere plot for Probe P150 showing DL directions with yellow, green, and red arrows on a grid. 3D sphere plot for Probe P150 showing DL directions with yellow, green, and red arrows on a grid.](53d8bef47c63e0897de4cd058bad2cbd_img.jpg) + +| | | | +|------------------------------------------------|--|--| +| DL Directions perceived by DUT from Probe P120 | | | +| DL Directions perceived by DUT from Probe P150 | | | + +3D sphere plot for Probe P120 showing DL directions with yellow, green, and red arrows on a grid. 3D sphere plot for Probe P120 showing DL directions with yellow, green, and red arrows on a grid. 3D sphere plot for Probe P150 showing DL directions with yellow, green, and red arrows on a grid. 3D sphere plot for Probe P150 showing DL directions with yellow, green, and red arrows on a grid. + +### 5.3.5 AoA1-AoA2 DL Orientation Vectors + +The relative orientation between the P0 and the three offset probes, i.e., P60, P120, and P150, are investigated further here. For better visualization purposes, a coarse measurement grid with 84 grid points for the constant-step size grid ( $\Delta\theta=\Delta\phi=30^\circ$ ) and 50 grid points for the constant density grid is considered. Given the clear advantages of the 3D measurement scan using a full rotation in $\theta$ and half rotation in $\phi$ for multi-AoA testing, only this approach is further considered here. + +The AoA1-AoA2 DL orientation vectors, i.e., the vectors between the DL orientation perceived by the UE from AoA1 to AoA2, are visualized in Table 5.3.5-1 for the constant step-size grid and in Table 5.3.5-2 for the constant-density grid. The vectors are illustrated in two different ways. In the figures on the left, e.g., + +![A 3D visualization of a sphere with a grid. Black markers represent AoA1 DL directions on the sphere's surface. Colored markers (blue, green, red) represent AoA2 DL directions, which are slightly elevated above the sphere. Arrows of various colors connect the black markers to the colored markers, indicating the orientation vectors from AoA1 to AoA2.](09b5a76dd3d981abcc585df1314ef30a_img.jpg) + +A 3D visualization of a sphere with a grid. Black markers represent AoA1 DL directions on the sphere's surface. Colored markers (blue, green, red) represent AoA2 DL directions, which are slightly elevated above the sphere. Arrows of various colors connect the black markers to the colored markers, indicating the orientation vectors from AoA1 to AoA2. + +the AoA1 DL directions are plotted on top of the sphere with the black marker while the AoA2 DL directions are plotted slightly elevated from the sphere for clarity. The corresponding AoA1 & AoA2 pairs received by the UE are connected with arrows (pointing from AoA1 to AoA2) with the arrows plotted in random colours to support better differentiation. In the figures on the right, e.g., + +![A 3D visualization of a sphere with a grid. Black markers represent AoA1 DL directions on the sphere's surface. Single arrows of various colors (blue, green, red) originate from these black markers and point towards the surface, representing the direction towards the corresponding offset AoA2 DL direction. The length of the arrows corresponds to the value of the offset.](c959fda5679ea6470e0810c8c29eb823_img.jpg) + +A 3D visualization of a sphere with a grid. Black markers represent AoA1 DL directions on the sphere's surface. Single arrows of various colors (blue, green, red) originate from these black markers and point towards the surface, representing the direction towards the corresponding offset AoA2 DL direction. The length of the arrows corresponds to the value of the offset. + +only the AoA1 DL directions are plotted on top of the sphere with the black marker while the direction towards the corresponding offset AoA2 DL direction is visualized with the single arrow (the length of the arrow corresponds to the value of the offset). + +The following observations can be drawn from these figures: + +- With probes aligned in the $xz$ axis, the AoA1-AoA2 DL orientation vectors point towards the pole at $\theta=180^\circ$ for DL directions perceived from $y\geq 0$ while the AoA1-AoA2 DL orientation vectors point towards the pole at $\theta=0^\circ$ for DL directions perceived from $y\leq 0$ +- With probes aligned in the $yz$ axis, the AoA1-AoA2 DL orientation vectors point towards positive $\phi$ for DL directions perceived from $y\geq 0$ while the AoA1-AoA2 DL orientation vectors point towards negative $\phi$ for DL directions perceived from $y\leq 0$ . + +It was agreed that the directionality of the AoA1-AoA2 DL orientation vectors matters. For simulations, testing both $+AoA$ offset and $-AoA$ offset for each test point was considered the starting point. The intention is to accommodate the + +impact from directionality of the AoA1-AoA2 DL orientation vectors, i.e., to ensure no testing bias is introduced or whether it needs to be compensated somehow. + +Table 5.3.5-1: Vectors of DL orientations between AoA1 (P0) and AoA2 from two different system configurations with AoA2 to AoA1 probe offsets of 60°, 120°, and 150° with a constant-step size grid using 84 grid points ( $\Delta\theta=\Delta\phi=30^\circ$ ). Full rotation in $\theta$ and half rotation in $\phi$ . + +| | Probes in the xz plane | Probes in the yz plane | +|---------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| System Configuration with full rotation in $\theta$ and half rotation in $\phi$ | Diagram of a probe on a spherical grid in the xz plane. The grid is mounted on a stand with a vertical axis. Probes P0, P60, P120, and P150 are shown at various positions on the grid. Arrows indicate the rotation of the grid around the y-axis. | Diagram of a probe on a spherical grid in the yz plane. The grid is mounted on a stand with a vertical axis. Probes P0, P60, P120, and P150 are shown at various positions on the grid. Arrows indicate the rotation of the grid around the y-axis. | +| Orientation between Probes P0 and P60 | Two views of a spherical grid showing the orientation of probes. The left view shows the grid from the side, highlighting the circular paths of the probes. The right view shows the grid from the front, with arrows indicating the orientation of each probe at the 84 grid points. | Two views of a spherical grid showing the orientation of probes. The left view shows the grid from the side, highlighting the circular paths of the probes. The right view shows the grid from the front, with arrows indicating the orientation of each probe at the 84 grid points. | + +![Two 3D sphere plots for P0 and P120 orientation. The left plot shows a dense cloud of red and black points with many colored lines connecting them. The right plot shows the same points with fewer, more distinct colored lines. Two 3D sphere plots for P0 and P120 orientation. The left plot shows a dense cloud of red and black points with many colored lines connecting them. The right plot shows the same points with fewer, more distinct colored lines. Two 3D sphere plots for P0 and P150 orientation. The left plot shows a dense cloud of green and black points with many colored lines connecting them. The right plot shows the same points with fewer, more distinct colored lines. Two 3D sphere plots for P0 and P150 orientation. The left plot shows a dense cloud of green and black points with many colored lines connecting them. The right plot shows the same points with fewer, more distinct colored lines.](b90dcb4c35f1875e19ca312a6cf4adae_img.jpg) + +| | | | +|----------------------------------------|--|--| +| Orientation between Probes P0 and P120 | | | +| Orientation between Probes P0 and P150 | | | + +Two 3D sphere plots for P0 and P120 orientation. The left plot shows a dense cloud of red and black points with many colored lines connecting them. The right plot shows the same points with fewer, more distinct colored lines. Two 3D sphere plots for P0 and P120 orientation. The left plot shows a dense cloud of red and black points with many colored lines connecting them. The right plot shows the same points with fewer, more distinct colored lines. Two 3D sphere plots for P0 and P150 orientation. The left plot shows a dense cloud of green and black points with many colored lines connecting them. The right plot shows the same points with fewer, more distinct colored lines. Two 3D sphere plots for P0 and P150 orientation. The left plot shows a dense cloud of green and black points with many colored lines connecting them. The right plot shows the same points with fewer, more distinct colored lines. + +Table 5.3.5-2: Vectors of DL orientations between AoA1 (P0) and AoA2 from two different system configurations with AoA2 to AoA1 probe offsets of 60°, 120°, and 150° with a constant density grid using 50 grid points. Full rotation in $\theta$ and half rotation in $\phi$ . + +| | Probes in the xz plane | Probes in the yz plane | +|---------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| System Configuration with full rotation in $\theta$ and half rotation in $\phi$ | Diagram of a spherical coordinate system with a probe at P0. A sphere is mounted on a stand with a vertical axis. A yellow circular arrow indicates full rotation in theta. A green circular arrow indicates half rotation in phi. Probes P60, P120, and P150 are shown as small cones at various positions on the sphere's surface. | Diagram of a spherical coordinate system with a probe at P0. A sphere is mounted on a stand with a vertical axis. A yellow circular arrow indicates full rotation in theta. A green circular arrow indicates half rotation in phi. Probes P60, P120, and P150 are shown as small cones at various positions on the sphere's surface, with P120 and P150 positioned higher up than in the xz plane configuration. | +| Orientation between Probes P0 and P60 | Two 3D plots of a sphere with a grid. The left plot shows the orientation vectors for probes P0 and P60, with P0 at the origin and P60 at a 60-degree offset. The right plot shows the orientation vectors for P0 and P60 on a sphere with a different grid orientation. | Two 3D plots of a sphere with a grid. The left plot shows the orientation vectors for probes P0 and P60, with P0 at the origin and P60 at a 60-degree offset. The right plot shows the orientation vectors for P0 and P60 on a sphere with a different grid orientation. | + +![Two 3D sphere plots for P0 and P120. The left plot shows a dense cloud of multi-colored vectors originating from a central point. The right plot shows a sparse grid of red vectors on a sphere surface, with a green Y-axis and blue Z-axis. Two 3D sphere plots for P0 and P120. The left plot shows a dense cloud of multi-colored vectors. The right plot shows a sparse grid of red vectors on a sphere surface, with a green Y-axis and blue Z-axis. Two 3D sphere plots for P0 and P150. The left plot shows a dense cloud of multi-colored vectors. The right plot shows a sparse grid of green vectors on a sphere surface, with a green Y-axis and blue Z-axis. Two 3D sphere plots for P0 and P150. The left plot shows a dense cloud of multi-colored vectors. The right plot shows a sparse grid of green vectors on a sphere surface, with a green Y-axis and blue Z-axis.](89b3389b2c4fa1b452cf2b5daa5f82ad_img.jpg) + +| | | | +|----------------------------------------|--|--| +| Orientation between Probes P0 and P120 | | | +| Orientation between Probes P0 and P150 | | | + +Two 3D sphere plots for P0 and P120. The left plot shows a dense cloud of multi-colored vectors originating from a central point. The right plot shows a sparse grid of red vectors on a sphere surface, with a green Y-axis and blue Z-axis. Two 3D sphere plots for P0 and P120. The left plot shows a dense cloud of multi-colored vectors. The right plot shows a sparse grid of red vectors on a sphere surface, with a green Y-axis and blue Z-axis. Two 3D sphere plots for P0 and P150. The left plot shows a dense cloud of multi-colored vectors. The right plot shows a sparse grid of green vectors on a sphere surface, with a green Y-axis and blue Z-axis. Two 3D sphere plots for P0 and P150. The left plot shows a dense cloud of multi-colored vectors. The right plot shows a sparse grid of green vectors on a sphere surface, with a green Y-axis and blue Z-axis. + +### 5.3.6 Far-field criteria + +The Far-field criteria defined for the DFF UE RF test method described in clause 5.2.1.2 of [3] can be reused for the DFF-based measurement setup. + +The Far-field criteria defined for the IFF UE RF test method described in clause 5.2.3.2 of [3] can be reused for the IFF-based measurement setup. + +## 5.4 Calibration Measurement Procedure + +### 5.4.1 Direct far field (DFF) + +The calibration measurement per DFF probe is done by using a reference calibration antenna with known gain values. For the calibration measurement, the reference antenna is placed in the centre of the quiet zone. If an antenna with moving phase centre is used, a multi-segmented approach could be chosen where for multiple frequency segments the respective phase centre of the calibration antenna is placed in the centre of quiet zone. The calibration process determines the composite loss, $L_{\text{path,pol}}$ , of the entire transmission and receiver chain path gains (measurement antenna, amplification) and losses (switches, combiners, cables, path loss, etc.). The calibration measurement is repeated for each measurement path (two orthogonal polarizations and each signal path). Additional details of the calibration procedure are outlined in [11]. + +### 5.4.2 Indirect far field (IFF) + +The calibration measurement per IFF probe is done by using a reference antenna (SGH used in Figure 5.2.2.1-1) with known efficiency or gain values. In the calibration measurement the reference antenna is measured in the same place as the DUT, and the attenuation of the complete transmission path ( $C \leftrightarrow A$ , as in Figure 5.2.2.1-1) from the DUT to the measurement receiver (EIRP), and from the RF source to DUT (EIS) is calibrated out. Figure 5.2.2.1-1 presents a setup of a typical compact antenna test range for EIRP calibration per IFF probe: + +![Diagram of the IFF/CATR calibration system setup per AoA for EIRP. The setup is enclosed in a rectangular chamber with jagged edges representing reflectors. Inside, a 'Feed Antenna' is mounted on the bottom wall. Above it, a 'SGH' (Standard Gain Horn) antenna is mounted on a rotating turntable. A red arrow labeled 'A' points from the SGH to the Feed Antenna. Below the chamber, a 'Positioner controller' is connected to the turntable and to a 'PC'. The 'PC' is also connected to a 'Network analyzer'. The 'Network analyzer' has two ports, labeled 'B' and 'C', which are connected to the Feed Antenna and the SGH respectively.](4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg) + +Diagram of the IFF/CATR calibration system setup per AoA for EIRP. The setup is enclosed in a rectangular chamber with jagged edges representing reflectors. Inside, a 'Feed Antenna' is mounted on the bottom wall. Above it, a 'SGH' (Standard Gain Horn) antenna is mounted on a rotating turntable. A red arrow labeled 'A' points from the SGH to the Feed Antenna. Below the chamber, a 'Positioner controller' is connected to the turntable and to a 'PC'. The 'PC' is also connected to a 'Network analyzer'. The 'Network analyzer' has two ports, labeled 'B' and 'C', which are connected to the Feed Antenna and the SGH respectively. + +Figure 5.4.2-1. IFF/CATR calibration system setup per AoA for EIRP + +## 5.5 Test procedure + +The performance of simultaneous multi-Rx chain DL reception is measured by sampling the go/no-go result of the DUT with three-dimensional scan at various locations surrounding the device. The measurement is performed with a constant sampling step of 15 degree in both theta ( $\theta$ ) and phi ( $\phi$ ) axes. + +The measurement procedure of the performance of simultaneous multi-Rx chain DL reception is illustrated in Figure 5.5-1. + +![Flowchart illustrating the test procedure of simultaneous multi-Rx chain DL reception. The process starts with 'Start the test', followed by selecting the first grid point n=1. It then enters a loop: selecting a test point P(theta_n, phi_n), setting up the positioning system, introducing 2 DL signals from AoA1 and AoA2, setting fixed DL power levels, measuring throughput, and issuing PASS/FAIL for mDCI and sDCI. It records the result for the selected test AoA pair and polarization combination. Next, it introduces 2-DL MIMO signals, sets fixed DL power levels, measures throughput, and issues PASS/FAIL for mDCI and sDCI. It records the result for the selected test AoA pair and polarization combination. A decision diamond asks 'All grid points measured?'. If 'No', it selects the next grid point n and loops back to the test point selection. If 'Yes', it calculates and records multi Rx reception RF performance results for polarization combinations (theta, theta) and (phi, phi), then calculates the final multi Rx reception RF performance M as the arithmetic mean of M_theta_theta and M_phi_phi, and finally finishes the test.](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +``` + +graph TD + Start([Start the test]) --> n1[Select n=1 (first grid point)] + n1 --> P[Select test point P(θn, φn) and setup the positioning system with the required AoA offset accordingly] + P --> Signals1[Introduce the 2 DL signals from AoA1 and AoA2 simultaneously, on the selected polarization combination (θ, θ), and pause for tdwell for UE beam to form.] + Signals1 --> Power1[Set the fixed DL power level on AoA1 and AoA2 (at the center of the QZ) and measure Throughput.] + Power1 --> mDCI1[mDCI: Issue PASS if both TPAoA1 and TPAoA2 pass the minimum required TP, otherwise FAIL. +sDCI: Issue PASS if TP pass the minimum required TP, otherwise FAIL.] + mDCI1 --> Record1[Record a PASS/FAIL for the selected test AoA pair and polarization combination Pθθ(θn, φn)AoA+ and Pθθ(θn+Δθ, φn)AoA-.] + Record1 --> Signals2[Introduce the 2-DL MIMO signals with AoA1 and AoA2 simultaneously, on the selected polarization combination (φ, φ), and pause for tdwell for UE beam to form.] + Signals2 --> Power2[Set the fixed DL power level on AoA1 and AoA2 (at the center of the QZ) and measure Throughput.] + Power2 --> mDCI2[mDCI: Issue PASS if both TPAoA1 and TPAoA2 pass the minimum required TP, otherwise FAIL. +sDCI: Issue PASS if TP pass the minimum required TP, otherwise FAIL.] + mDCI2 --> Record2[Record a PASS/FAIL for the selected test AoA pair and polarization combination Pφφ(θn, φn)AoA+ and Pφφ(θn+Δθ, φn)AoA-.] + Record2 --> Decision{All grid points measured?} + Decision -- No --> NextN[Select the next grid point n] + NextN --> P + Decision -- Yes --> Calc1[Calculate and record multi Rx reception RF performance result for the polarization combination (θ, θ) and (φ, φ) with Pθθ and Pφφ separately, including area weights, naming as Mθθ and Mφφ.] + Calc1 --> Calc2[Calculate and record final multi Rx reception RF performance M with the arithmetic mean of Mθθ and Mφφ.] + Calc2 --> Finish([Finish the test]) + +``` + +Flowchart illustrating the test procedure of simultaneous multi-Rx chain DL reception. The process starts with 'Start the test', followed by selecting the first grid point n=1. It then enters a loop: selecting a test point P(theta\_n, phi\_n), setting up the positioning system, introducing 2 DL signals from AoA1 and AoA2, setting fixed DL power levels, measuring throughput, and issuing PASS/FAIL for mDCI and sDCI. It records the result for the selected test AoA pair and polarization combination. Next, it introduces 2-DL MIMO signals, sets fixed DL power levels, measures throughput, and issues PASS/FAIL for mDCI and sDCI. It records the result for the selected test AoA pair and polarization combination. A decision diamond asks 'All grid points measured?'. If 'No', it selects the next grid point n and loops back to the test point selection. If 'Yes', it calculates and records multi Rx reception RF performance results for polarization combinations (theta, theta) and (phi, phi), then calculates the final multi Rx reception RF performance M as the arithmetic mean of M\_theta\_theta and M\_phi\_phi, and finally finishes the test. + +Figure 5.5-1: Illustration of the test procedure of simultaneous multi-Rx chain DL reception + +# 6 UE RRM testing methodology for multi-Rx chain DL reception + +## 6.1 General + +This clause describes the UE RRM testing methodology for multi-Rx chain DL reception for FR2. The principle of selecting measurement setup for UE RRM testing is to reuse measurement setup for UE RF testing as much as possible to reduce the test system complexity and test cost. + +Considering system complexity and feasibility, chamber footprint, upgradeability of existing system, the measurement setup supporting Category 1 and Option 2 of Category 2 is selected as the baseline in Rel-18. + +The details of OTA test environments including side conditions are to be discussed in the corresponding work item that may have impact to the core requirements. + +## 6.2 Measurement setup + +### 6.2.1 Baseline measurement setup + +#### 6.2.1.1 Test scenarios + +The test scenarios of UE RRM testing for multi-Rx chain DL reception can be divided into two categories depending on whether dual DCI simultaneously switching needs to be supported by measurement setup or not: + +- Category 1: All the RRM test cases expect Dual TCI switching +- Category 2: Dual TCI switching test case + +#### 6.2.1.2 Measurement setup for Category 1 scenario + +The baseline measurement setup for Category 1 scenario is implemented based on the legacy 2AoA RRM setup specified in section 6 of [3]. An example measurement setup of multi-Rx chain DL reception RRM test case for Category 1 scenario is illustrated in Figure 6.2.1-1. + +![Figure 6.2.1-1: Example measurement setup for Category 1 scenario. The diagram shows two measurement phases, T1 and T2, separated by a vertical dashed line. In T1, a red beam labeled 'Probe #1' is directed towards a blue rectangular UE icon, with the label 'TCI state 0' above it. In T2, two beams are shown: a red beam labeled 'Probe #1' and a blue beam labeled 'Probe #2', both directed towards the UE icon. The red beam is labeled 'TCI state 0' and the blue beam is labeled 'TCI state 1'. The horizontal axis is labeled T1 and T2 with double-headed arrows indicating the duration of each phase.](daa9e738320d13f92e63ceaef7ad93c4_img.jpg) + +Figure 6.2.1-1: Example measurement setup for Category 1 scenario. The diagram shows two measurement phases, T1 and T2, separated by a vertical dashed line. In T1, a red beam labeled 'Probe #1' is directed towards a blue rectangular UE icon, with the label 'TCI state 0' above it. In T2, two beams are shown: a red beam labeled 'Probe #1' and a blue beam labeled 'Probe #2', both directed towards the UE icon. The red beam is labeled 'TCI state 0' and the blue beam is labeled 'TCI state 1'. The horizontal axis is labeled T1 and T2 with double-headed arrows indicating the duration of each phase. + +Figure 6.2.1-1: Example measurement setup for Category 1 scenario. + +![Figure 6.2.1-2: Example of Time and Frequency multiplexed downlink transmission for Category 1 scenario. The diagram shows two frequency bands, AoA1 transmission and AoA2 transmission, over time intervals T1 and T2. AoA1 transmission uses PDCCH/PDSCH (red) and PBCH (green). AoA2 transmission uses PDCCH/PDSCH (blue) and PBCH (green). CSI-RS (grey) is shown in both bands. A legend at the bottom identifies the colors: red for PDCCH/PDSCH, blue for PDCCH/PDSCH, green for PBCH, and grey for CSI-RS.](92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg) + +Figure 6.2.1-2: Example of Time and Frequency multiplexed downlink transmission for Category 1 scenario. The diagram shows two frequency bands, AoA1 transmission and AoA2 transmission, over time intervals T1 and T2. AoA1 transmission uses PDCCH/PDSCH (red) and PBCH (green). AoA2 transmission uses PDCCH/PDSCH (blue) and PBCH (green). CSI-RS (grey) is shown in both bands. A legend at the bottom identifies the colors: red for PDCCH/PDSCH, blue for PDCCH/PDSCH, green for PBCH, and grey for CSI-RS. + +**Figure 6.2.1-2: Example of Time and Frequency multiplexed downlink transmission for Category 1 scenario** + +As illustrated in Figure 6.2.1-2, PDCCH/PDSCH from two AoAs transmit in the FDM manner. PBCH measurement is based on TDM manner. For CSI-RS, the measurements could be based on TDM/FDM/CDM. + +#### 6.2.1.3 Measurement setup for Category 2 scenario + +Dual TCI switching is the key test case in multi-Rx chain DL reception RRM testing. To verify the performance of Dual TCI switching, the following 4 options were discussed: + +- Option 1: Dual TCI switches simultaneously, probe number for multiple AoA test system is at least 4 + +![Figure 6.2.1-3: Example measurement setup for Option 1 of Category 2 scenario with 4 probes. The diagram shows a DUT (Device Under Test) connected to four probes (Probe #1, Probe #2, Probe #3, Probe #4) via TCI states. In period T1, Probe #1 is connected to TCI state 0 and Probe #2 to TCI state 1. In period T2, Probe #1 switches to TCI state 3 and Probe #2 switches to TCI state 2. The diagram illustrates the simultaneous switching of TCI states between probes.](42f0611a8a2766c986ff45551918ca5d_img.jpg) + +Figure 6.2.1-3: Example measurement setup for Option 1 of Category 2 scenario with 4 probes. The diagram shows a DUT (Device Under Test) connected to four probes (Probe #1, Probe #2, Probe #3, Probe #4) via TCI states. In period T1, Probe #1 is connected to TCI state 0 and Probe #2 to TCI state 1. In period T2, Probe #1 switches to TCI state 3 and Probe #2 switches to TCI state 2. The diagram illustrates the simultaneous switching of TCI states between probes. + +**Figure 6.2.1-3: Example measurement setup for Option 1 of Category 2 scenario with 4 probes** + +For option 1, in the period of T1, DUT connects TCI state 0 and TCI state 1 via probe#1 and probe#2 respectively. Then in the period of T2, TCI state 0 switches to TCI state 3 via switching between probe#1 and probe#4, and in the meanwhile, TCI state 1 switches to TCI state 2 via switching between probe#2 and probe#3. + +- Option 2: Dual TCI switches from one probe to two probes simultaneously, probe number for multiple AoA test system is at least 3 + +![Figure 6.2.1-4: Example measurement setup for Option 2 of Category 2 scenario with 3 probes. The diagram shows two time periods, T1 and T2. In T1, a probe (Probe #1) is shown with TCI state 0. In T2, three probes are shown: Probe #1 with TCI state 0, Probe #2 with TCI state 1, and Probe #3 with TCI state 2. A small device icon is shown below the probes in each period.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +Figure 6.2.1-4: Example measurement setup for Option 2 of Category 2 scenario with 3 probes. The diagram shows two time periods, T1 and T2. In T1, a probe (Probe #1) is shown with TCI state 0. In T2, three probes are shown: Probe #1 with TCI state 0, Probe #2 with TCI state 1, and Probe #3 with TCI state 2. A small device icon is shown below the probes in each period. + +Figure 6.2.1-4: Example measurement setup for Option 2 of Category 2 scenario with 3 probes + +![Figure 6.2.1-5: Example of Time and Frequency multiplexed downlink transmission for Category 2 scenario with 3 probes. The figure shows three horizontal timelines for AoA1 (SSB index 0), AoA2 (SSB index 1), and AoA3 (SSB index 2) over two time periods, T1 and T2. The legend indicates: PDCCH/PDSCH (red, blue, green), SSB (purple), and CSI-RS (grey).](5a8d83665fa993ed599f2eb41fd6c7f5_img.jpg) + +The figure illustrates the downlink transmission for three different Angle of Arrival (AoA) test cases over two time periods, T1 and T2. The vertical axis represents the Channel Bandwidth (CBW). The legend identifies the following signal types: + + +- PDCCH/PDSCH:** Red, Blue, and Green blocks represent data channels for AoA1, AoA2, and AoA3 respectively. +- SSB:** Purple blocks represent Synchronization Signal Blocks. +- CSI-RS:** Grey blocks represent Channel State Information Reference Signals. + + In period T1, AoA1 transmits PDCCH/PDSCH and SSB. AoA2 transmits SSB and CSI-RS. AoA3 transmits SSB and CSI-RS. In period T2, AoA1 continues with PDCCH/PDSCH and SSB. AoA2 transmits PDCCH/PDSCH, SSB, and CSI-RS. AoA3 transmits PDCCH/PDSCH, SSB, and CSI-RS. + +Figure 6.2.1-5: Example of Time and Frequency multiplexed downlink transmission for Category 2 scenario with 3 probes. The figure shows three horizontal timelines for AoA1 (SSB index 0), AoA2 (SSB index 1), and AoA3 (SSB index 2) over two time periods, T1 and T2. The legend indicates: PDCCH/PDSCH (red, blue, green), SSB (purple), and CSI-RS (grey). + +Figure 6.2.1-5: Example of Time and Frequency multiplexed downlink transmission for Category 2 scenario with 3 probes + +For Option 2, in the period of T1, DUT connects TCI state 0 via Probe#1. In the period of T2, DUT measures the SSBs from Probe#2 and Probe#3 while keeping the connection from Probe 1. And then DUT simultaneously switches from Probe#1 to Probe#2 and #3. + +An example measurement setup of multi-Rx chain DL reception RRM test case for Category 2 scenario with 3 probes is illustrated in Figure 6.2.1-5. PDCCH/PDSCH from two AoAs transmit in the FDM manner. PBCH measurement is based on TDM manner. For CSI-RS, the measurements could be based on TDM/FDM/CDM. + +For the testing with Option 2, the side conditions for the period T1 and T1 are as follows. In the period of T1, the candidate test direction is selected from legacy EIS spherical coverage. In the period of T2, the candidate test directions (AoA pairs) are selected from multi-Rx spherical coverage requirements defined in UE RF core requirements. + +Note that Figure 6.2.1-4 and Figure 6.2.1-5 show an example test procedure for Dual TCI switching. Other test procedures with at least 3 probes measurement setup are not precluded. The details of RRM test cases are to be discussed in the corresponding work item. + +- Option 3: Dual TCI switches simultaneously, but the beam directions are not changed, probe number for multiple AoA test system is at least 2 + +![Figure 6.2.1-6: Example measurement setup for Option 3 of Category 2 scenario with 2 probes. The diagram shows two time periods, T1 and T2. In T1, Probe #1 (Pol. H) is in TCI state 0 and Probe #2 (Pol. H) is in TCI state 1. In T2, Probe #1 (Pol. V) is in TCI state 3 and Probe #2 (Pol. V) is in TCI state 2. The probes are shown as colored ellipses (red, blue, green, orange) pointing towards a central device.](18bb06865e2dada3656ea3d57f290f7f_img.jpg) + +Figure 6.2.1-6: Example measurement setup for Option 3 of Category 2 scenario with 2 probes. The diagram shows two time periods, T1 and T2. In T1, Probe #1 (Pol. H) is in TCI state 0 and Probe #2 (Pol. H) is in TCI state 1. In T2, Probe #1 (Pol. V) is in TCI state 3 and Probe #2 (Pol. V) is in TCI state 2. The probes are shown as colored ellipses (red, blue, green, orange) pointing towards a central device. + +**Figure 6.2.1-6: Example measurement setup for Option 3 of Category 2 scenario with 2 probes** + +For option 3, in the period of T1, DUT connects TCI state 0 and TCI state 1 via Pol.H of probe#1 and Pol.H of probe#2, respectively. Then in the period of T2, TCI state 0 switches to TCI state 3 via switching between Pol.H and Pol.V of probe 1, and in the meanwhile, TCI state 1 switches to TCI state 2 via switching between Pol.H and Pol.V of probe 2. Note that in option 3, different SSB IDs are transmitted from two polarizations in T1 and T2. + +- Option 4: Switching AoAs of the Rx beam from AoA1 to AoA2 or vice versa during the TCI switching test. Probe number for multiple AoA test system is at least 2. + +![Figure 6.2.1-7: Example measurement setup for Option 4 of Category 2 scenario with 2 probes. The diagram shows two time periods, T1 and T2, with the title 'TCI states switching from AoA1 viewpoint (TCI state 0 to state 1)'. In T1, Probe #1 is in TCI state 0 and Probe #2 is in TCI state 1. In T2, Probe #1 is in TCI state 3 and Probe #2 is in TCI state 2. Below the probes, SSB IDs are indicated: 'SSB 0 with Pol. V' and 'SSB 1 with Pol. V' in T1, and 'SSB 0 with Pol. V' and 'SSB 0 with Pol. V' in T2. A curved arrow indicates the switching of AoAs between the two probes.](bd50d56ae2c12a92466ba2aea1a78040_img.jpg) + +Figure 6.2.1-7: Example measurement setup for Option 4 of Category 2 scenario with 2 probes. The diagram shows two time periods, T1 and T2, with the title 'TCI states switching from AoA1 viewpoint (TCI state 0 to state 1)'. In T1, Probe #1 is in TCI state 0 and Probe #2 is in TCI state 1. In T2, Probe #1 is in TCI state 3 and Probe #2 is in TCI state 2. Below the probes, SSB IDs are indicated: 'SSB 0 with Pol. V' and 'SSB 1 with Pol. V' in T1, and 'SSB 0 with Pol. V' and 'SSB 0 with Pol. V' in T2. A curved arrow indicates the switching of AoAs between the two probes. + +**Figure 6.2.1-7 Example measurement setup for Option 4 of Category 2 scenario with 2 probes** + +For option 4, TCI state switching is based on SSB 0 to SSB 1. The test could be carried out simultaneously or in series with the switching. + +The pros and cons for 4 options are listed in Table 6.2.1-1. + +**Table 6.2.1-1: Pros and cons for 4 options** + +| | Pros | Cons | +|----------|-----------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Option 1 |
  • - The setup can fully verify the performance of dual TCI switching.
|
  • - Test system will at least support 4 physical probes.
  • - Two of the same AoA offsets from RF session is needed.
  • - Reusing of existing test system is not possible
| + +| | | | +|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Option 2 |
  • - The complexity of test system is lower, e.g., 3 physical probes is needed.
  • - The test condition could follow AoA offset from RF session.
  • - Reusing the existing is possible.
|
  • - The setup can partially verify the performance of dual TCI switching.
| +| Option 3/4 |
  • - The complexity of test system is lowest, e.g., 2 physical probes is needed.
|
  • - The setup cannot verify the real performance of dual TCI switching such as the beam directions are not changed from T1 to T2.
  • - This implies a perfect polarization alignment between DUT and TE in order to separate the beams, which is not feasible based on current test systems
| + +Considering system complexity and feasibility, chamber footprint, upgradeability of existing system, the measurement setup for Option 2 with at least 3 probes is selected as the baseline in Rel-18. + +#### 6.2.1.4 Far-field criteria + +For multi-Rx chain DL reception RRM baseline measurement setup based on DFF: + +- The Far-field criteria defined for the DFF UE RF testing methodology described in clause 5.3.6 can be applied. + +For multi-Rx chain DL reception RRM baseline measurement setup based on IFF: + +- The Far-field criteria defined for the IFF UE RF testing methodology described in clause 5.3.6 can be applied. + +#### 6.2.1.5 Calibration measurement procedure + +The calibration measurement procedure defined for the DFF UE RF testing methodology described in clause 5.4.1 can be applied for DFF based UE RRM testing. + +The calibration measurement procedure defined for the IFF UE RF testing methodology described in clause 5.4.2 can be applied for IFF based UE RRM testing. + +#### 6.2.1.6 Reference point + +For baseline measurement setup based on DFF and IFF, the reference point is located at the centre of the QZ. From the UE perspective the reference point is the input of UE antenna array. + +The following Modes for useful signals (S) and noise signals (N) configuration have been identified and can be supported by the RRM test method: + +- Mode 1 (SNR emulation): Test system transmits useful signals (S) and noise signals (N) to emulate target SNR condition. +- Mode 2 (noise-free transmission): Test system transmits only useful signals (S). + +The test cases in core specification TS 38.133 [x] will be specified at the reference point, according to the following principles: + +- Mode 1 + - Specify absolute Noc level at the Reference point per angle of arrival (AoA) + - Noc level may have different value according to operating band and UE power class +- Mode 2 + +- Specify SNR at the Reference point per angle of arrival (AoA) +- SNR is a test-specific value + +### 6.2.2 Test parameters + +#### 6.2.2.1 Test parameters for Mode 1 + +For Mode 1, the SINR at baseband for multi-DCI with overlapping scheme is given as follows: + +$$SINR1_{BB} = \frac{S1 * G1 * Loss}{(S2 + N) * G2 * Loss + N * G1 * Loss + Noise\_floor}, \quad (6.2.2.1-1)$$ + +where S1 and S2 are signal level from AoA1 and AoA2 respectively. G1 and G2 are the antenna gain from AoA1 and AoA2 respectively. Loss is the pathloss between probe and DUT. Noise\_floor is the total noise at DUT baseband receiver. N is the artificial noise at the reference point from AoA1 and AoA2. The artificial noise level is identical from AoA1 and AoA2. + +Since the wanted noise is set 6dB above UE thermal noise, therefore the total noise of baseband Noise\_floor can be ignored when calculating the SINR. And the SINR can be rewritten as: + +$$SINR1_{BB} \approx \frac{S1 * G1 * Loss}{(S2 + N) * G2 * Loss + N * G1 * Loss} = \frac{1}{\left(\frac{S2}{S1} + \frac{1}{SNR1}\right) * \frac{G2}{G1} + \frac{1}{SNR1}}, \quad (6.2.2.1-2)$$ + +where SINR1 is the SINR from probe 1, and the key parameter affecting the SINR at baseband is G1/G2. + +Similarly, the SINR at baseband for multi-DCI with partially overlapping scheme is given as: + +$$SINR1 \approx \frac{1}{\left(\frac{\alpha * S2}{S1} + \frac{1}{SNR1}\right) * \frac{G2}{G1} + \frac{1}{SNR1}}, \quad (6.2.2.1-3)$$ + +where $\alpha$ indicates the ratio of overlapping resources ( $0 < \alpha < 1$ ). + +For multi-Rx with non-overlapping scheme, the interference between two AoAs can be ignored. Then the test parameters for Mode 1 in the legacy RRM test methodology specified in [3] can be reused. + +#### 6.2.2.2 Test parameters for Mode 2 + +For Mode 2, the SINR at baseband for multi-DCI with overlapping scheme is given as follows: + +$$SINR1_{BB} = \frac{S1 * G1 * Loss}{S2 * G2 * Loss + Noise\_floor}, \quad (6.2.2.2-1)$$ + +where S1 and S2 are signal level from AoA1 and AoA2 respectively. G1 and G2 are the antenna gain from AoA1 and AoA2 respectively. Loss is the pathloss between probe and DUT. Noise\_floor is the total noise at DUT baseband receiver. + +If we set the signal level from interfering AoA direction at reference point is 6dB higher than UE thermal noise, then the approximate SINR can be rewritten as follows: + +$$SINR1_{BB} \approx \frac{S1}{S2 * G2 / G1}. \quad (6.2.2.2-2)$$ + +Same as for Mode 1, and the key parameter affecting the SINR at baseband is G1/G2. + +Similarly, the SINR at baseband for multi-DCI with partially overlapping scheme is given as follows: + +$$SINR1_{BB} \approx \frac{S1}{\alpha * S2 * \frac{G2}{G1}}, \quad (6.2.2.2-3)$$ + +where $\alpha$ indicates the ratio of overlapping resources ( $0 < \alpha < 1$ ). + +For multi-Rx with non-overlapping scheme, the interference between two AoAs can be ignored. Then the test parameters for Mode 2 in the legacy RRM test methodology specified in [3] can be reused. + +# 7 UE demodulation and CSI testing methodology for multi-Rx chain DL reception + +## 7.1 General + +This clause describes the UE Demodulation testing methodology for multi-Rx chain DL reception for FR2. The ‘virtual cable’ approach is adopted per each multi-Rx chain in which the setup is to be fixed with the beamlock function. The framework for UE demodulation and CSI testing for multi-Rx chain DL reception is shown in Figure 7.1-1. + +![Diagram of the framework for UE demodulation and CSI testing for multi-Rx chain DL reception. A central 'UE' (User Equipment) is shown inside a 'Test zone' (represented by a green oval). The UE is mounted on a 'Positioner' (represented by a grey rectangle). Two 'Dual-polarized antenna pair' sources, labeled 'AoA1' and 'AoA2', are positioned on the left and right respectively, with arrows pointing towards the UE. The UE is represented by a blue rectangle inside a grey rectangle, which is placed on a green oval labeled 'Test zone'. The entire setup is supported by a grey rectangle labeled 'Positioner'.](c2f36c545b190860d04e1d84e58d22cc_img.jpg) + +Diagram of the framework for UE demodulation and CSI testing for multi-Rx chain DL reception. A central 'UE' (User Equipment) is shown inside a 'Test zone' (represented by a green oval). The UE is mounted on a 'Positioner' (represented by a grey rectangle). Two 'Dual-polarized antenna pair' sources, labeled 'AoA1' and 'AoA2', are positioned on the left and right respectively, with arrows pointing towards the UE. The UE is represented by a blue rectangle inside a grey rectangle, which is placed on a green oval labeled 'Test zone'. The entire setup is supported by a grey rectangle labeled 'Positioner'. + +**Figure 7.1-1: The framework for UE demodulation and CSI testing for *multi-Rx chain DL reception*** + +## 7.2 Measurement setup + +### 7.2.1 Baseline measurement setup + +#### 7.2.1.1 Reference point + +Virtual cable setup is adopted for the baseline measurement setup. For baseline measurement setup based on DFF and IFF, the reference point is located at the centre of the QZ. From the UE perspective the reference point is the input of UE antenna array. + +#### 7.2.1.2 Far-field criteria + +For multi-Rx chain DL reception demodulation baseline measurement setup based on DFF: + +- The Far-field criteria defined for the DFF UE RF testing methodology described in clause 5.3.6 can be applied. + +For multi-Rx chain DL reception demodulation baseline measurement setup based on IFF: + +- The Far-field criteria defined for the IFF UE RF testing methodology described in clause 5.3.6 can be applied. + +#### 7.2.1.3 Calibration measurement procedure + +The calibration measurement procedure defined for the DFF UE RF testing methodology described in clause 5.4.1 can be applied for DFF based UE demodulation testing. + +The calibration measurement procedure defined for the IFF UE RF testing methodology described in clause 5.4.2 can be applied for IFF based UE demodulation testing. + +### 7.2.2 Test parameters + +#### 7.2.2.1 Noc level configuration + +Simulations for UE demodulation run at baseband with results expressed as $\text{SNR}_{\text{BB}}$ . The SNR at the reference point is the SNR configured by test equipment over-the-air expressed as $\text{SNR}_{\text{RP}}$ . The approach below is applied: + +- Set wanted noise to give 1dB difference between Reference point SNR and Baseband SNR, using agreed UE requirements, i.e., $\text{SNR}_{\text{RP}} = \text{SNR}_{\text{BB}} + 1\text{dB}$ + +Noc level is set by the below equation for demodulation test on band Y: + +$$\text{Noc} = \text{REFSENS}_{\text{PC3, band Y, 50MHz}} - 10\log_{10}(\text{SCS}_{\text{REFSENS}} \times \text{PRB}_{\text{REFSENS}} \times 12) - \text{SNR}_{\text{REFSENS}} + \Delta_{\text{thermal}} + X, \quad (7.2.2.1-1)$$ + +where + +- $\text{REFSENS}_{\text{PC3, band Y, 50MHz}}$ is the REFSENS value in dBm specified for Power Class 3 UE in band Y for 50MHz channel bandwidth in TS 38.101-2 Table 7.3.2.3-1, [dBm/Hz] +- $\text{SCS}_{\text{REFSENS}}$ is a subcarrier spacing associated with $N_{\text{RB}}$ for 50MHz in TS 38.101-2 Table 5.3.2-1, chosen as 120kHz. +- $\text{PRB}_{\text{REFSENS}}$ is $N_{\text{RB}}$ associated with subcarrier spacing 120kHz for 50MHz in TS 38.101-2 Table 5.3.2-1 and is 32. +- 12 is the number of subcarriers in a PRB +- $\text{SNR}_{\text{REFSENS}} = -1 \text{ dB}$ is the SNR used for simulation of REFSENS +- $\Delta_{\text{thermal}}$ is the amount of dB that the wanted noise is set above UE thermal noise, giving a rise in total noise of $\Delta_{\text{BB}}$ . $\Delta_{\text{thermal}} = 6\text{dB}$ , giving a rise in total noise of 1dB. +- $X = [3]$ is the allowable degradation in sensitivity from legacy REFSENS requirements in dB + +#### 7.2.2.2 Criteria of UE test directions + +The test directions and AoA separation for demodulation test can be declared by UE. The UE declared test directions shall satisfy the following 3 criteria: + +- Minimum isolation shall be at least [-12]dB +- Rank number shall be higher or same as intended rank for a given test case +- Each direction of AoA pair shall pass legacy REFSENS requirements with [3] dB degradation. + +Note: the minimum isolation of [-12]dB is reused from legacy FR2 up to 2 layer demodulation testing. For multi-Rx chain DL reception demodulation testing, RAN4 recommend the target of the required SNR difference between with and without additional interference introduced by chamber, i.e., MU due to non-ideal isolation, is 1dB. The final minimum isolation and corresponding MU defer the discussion to RAN5. + +# --- 8 Summary + +This technical report defines the UE RF/RRM/demodulation test methodology for the verifications of these new requirements for FR2 UE with multi-Rx chain DL receptions. Through the analysis of system complexity, chamber footprint, upgradeability of existing system, development lead time, measurement uncertainty, and test time aspects, the agreements on measurement setup of UE RF/RRM/demodulation testing are as follows. + +For UE RF testing, the measurement setup with full degrees of freedom for AoA1 with fixed angular Offset(s) between AoA1 and AoA2 is selected as the baseline. + +For UE RRM testing, the measurement setup supporting Dual TCI switches from one probe to two probes simultaneously is selected as the baseline. + +For UE demodulation testing, the measurement setup for UE RF testing can be reused to demodulation testing and the "virtual cable" approach is adopted per each multi-Rx chain. + +Additionally, the preliminary measurement uncertainty budget is specified in the document and the final MU will be further discussed and decided by RAN5. + +# --- Annex A: Measurement uncertainty --- + +## A.1 Measurement uncertainty budget for UE RF testing methodology + +Similar as legacy FR2 UE RF testing methodology, the uncertainty tables shall be presented with two stages: + +- Stage 1: the calibration of the absolute level of the DUT measurement results is performed by means of using a calibration antenna whose absolute gain is known at the frequencies of measurement +- Stage 2: the actual measurement with the DUT as either the transmitter or receiver is performed. + +The uncertainty assessments for UE RF testing mainly refer to [13] taking into the impact from 2AoAs receptions. For multi-Rx chain DL reception UE RF requirements, the percentage of 2AoA spherical coverage is specified. Therefore, the new requirements of 2AoA are quite similar as legacy EIS spherical coverage requirements. While the difference between multi-Rx chain DL reception requirement and legacy EIS spherical coverage requirement measurement is that DL power is not scanning with a DL power step size in multi-Rx chain DL reception UE RF testing. It says in multi-Rx chain DL reception UE RF testing, the throughput of UE is measured at a fixed DL power, i.e., legacy EIS spherical coverage power level. + +As specified in Table B.19.2-2 of [13], each MU element is described as dB value that could not totally apply for multi-Rx chain DL reception UE MU analysis. Additionally, the difference of probability between candidate measurement grids measurement step size could be evaluated and provided based on the simulations. Therefore, it is agreed to use the percentage value as the metric for the 2AoA UE RF MU analysis. + +The preliminary MU budget for UE RF testing methodology is defined in Table A.1-1 and Table A.1-2. + +**Table A.1-1: Uncertainty assessment for wanted DL signal absolute power in 2AoA coverage measurement with IFF** + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | [0.00] | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | [0.00] | +| 3 | Quality of Quiet Zone (NOTE 1) | 0.7 | Actual | 1.00 | [0.7] | +| 4 | Mismatch | 1.30 | Actual | 1.00 | [1.30] | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | [0.00] | +| 6 | gNB uncertainty on absolute level | 2.9 | Normal | 2.00 | [1.45] | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | [0.00] | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | [1.05] | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | [0.25] | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | [0.00] | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | [0.00] | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | [0.00] | +| 13 | Multiple measurement antenna uncertainty | 0.15 | Actual | 1.00 | [0.15] | +| 14 | DUT repositioning | 0.00 | Rectangular | 1.73 | [0.00] | +| 15 | Influence of spherical coverage grid | 0.12 | Actual | 1 | [0.12] | +| Stage 1: Calibration measurement | | | | | | +| 16 | Mismatch | 0.00 | U-shaped | 1.41 | [0.00] | +| 17 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | [0.00] | +| 18 | Misalignment of positioning System | 0.00 | Normal | 2.00 | [0.00] | +| 19 | Uncertainty of the Network Analyzer | 1.50 | Normal | 2.00 | [0.75] | +| 20 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | [0.30] | +| 21 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | [0.00] | +| 22 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | [0.00] | +| 23 | Quality of quiet zone for calibration process (NOTE 1) | 0.4 | Actual | 1.00 | [0.4] | +| 24 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | [0.00] | +| 25 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | [0.07] | +| 26 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | [0.00] | +| Measurement uncertainty | | | | | Value | +| Wanted DL signal absolute power (1.96 $\sigma$ - confidence interval of 95 %) [dB] | | | | | [4.92] | +| NOTE 1: The values from Enhanced IFF seem rather optimistic for MultiRX and should be further updated with the considerations of 2AoA impact | | | | | | + +### **A.1-2: Total uncertainty assessment for 2AoA coverage measurement with IFF** + +| Measurement uncertainty | Value | +|--------------------------------------------------------------------------------------------------|--------------| +| Wanted DL signal absolute power ( $1.96\sigma$ - confidence interval of 95 %) [%] (NOTE 1) | [4.0]% | +| Uncertainty related to measurement grid (NOTE 1) | [2.3]% | +| Total Measurement uncertainty | Value | +| [2AoA spherical coverage] expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [%] | [6.3]% | + +NOTE 1: It is derived based on the simulations with different DL power vs percentage of 2AoA metric. +NOTE 2: It is derived based on the simulations with measurement step size vs percentage of 2AoA metric. + +## --- A.2 Measurement uncertainty budget for UE RRM testing methodology + +The preliminary uncertainty budget for UE RRM testing is defined in Table A.2-1. + +Table A.2-1: Uncertainty assessment for RRM testing with IFF + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | +|----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------| +| Stage 2: DUT measurement | | | | | | +| 1 | Positioning misalignment | 0.00 | Normal | 2.00 | [0.00] | +| 2 | Measure distance uncertainty | 0.00 | Rectangular | 1.73 | [0.00] | +| 3 | Quality of Quiet Zone (NOTE 1) | 0.7 | Actual | 1.00 | [0.7] | +| 4 | Mismatch | 1.30 | Actual | 1.00 | [1.30] | +| 5 | Standing wave between the DUT and measurement antenna | 0.00 | U-shaped | 1.41 | [0.00] | +| 6 | gNB uncertainty on absolute level | 2.9 | Normal | 2.00 | [1.45] | +| 7 | Phase curvature | 0.00 | U-shaped | 1.41 | [0.00] | +| 8 | Amplifier uncertainties | 2.1 | Normal | 2.00 | [1.05] | +| 9 | Random uncertainty | 0.50 | Normal | 2.00 | [0.25] | +| 10 | Influence of the XPD | 0.01 | U-shaped | 1.41 | [0.00] | +| 11 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | [0.00] | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | 0.00 | Actual | 1.00 | [0.00] | +| 13 | Multiple measurement antenna uncertainty | 0.15 | Actual | 1.00 | [0.15] | +| 14 | DUT repositioning | 0.08 | Rectangular | 1.73 | [0.05] | +| Stage 1: Calibration measurement | | | | | | +| 15 | Mismatch | 0.00 | U-shaped | 1.41 | [0.00] | +| 16 | Amplifier Uncertainties | 0.00 | Normal | 2.00 | [0.00] | +| 17 | Misalignment of positioning System | 0.00 | Normal | 2.00 | [0.00] | +| 18 | Uncertainty of the Network Analyzer | 0.73 | Normal | 2.00 | [0.37] | +| 19 | Uncertainty of the absolute gain of the calibration antenna | 0.60 | Normal | 2.00 | [0.30] | +| 20 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | 0.01 | Rectangular | 1.73 | [0.00] | +| 21 | Phase centre offset of calibration antenna | 0.00 | Rectangular | 1.73 | [0.00] | +| 22 | Quality of quiet zone for calibration process (NOTE 1) | 0.4 | Actual | 1.00 | [0.4] | +| 23 | Standing wave between reference calibration antenna and measurement antenna | 0.00 | U-shaped | 1.41 | [0.00] | +| 24 | Influence of the calibration antenna feed cable | 0.14 | Normal | 2.00 | [0.07] | +| 25 | Insertion Loss Variation | 0.00 | Rectangular | 1.73 | [0.00] | +| Systematic uncertainties (NOTE 2) | | | | | Value | +| Total measurement uncertainty | | | | | Value | +| DL AWGN absolute power expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) [dB] | | | | | [4.75] | +| NOTE 1: The values from Enhanced IFF seem rather optimistic for MultiRX and should be further updated with the considerations of 2AoA impact | | | | | | + +## A.3 Measurement uncertainty budget for UE demodulation testing methodology + +The preliminary uncertainty budget for UE demodulation testing is defined in Table A.3-1. + +Table A.3-1: Uncertainty assessment for Multi-Rx demodulation testing with IFF + +| UID | Uncertainty source | Uncertainty value | Distribution of the probability | Divisor | Standard uncertainty ( $\sigma$ ) [dB] | | | | | +|-------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------------------|---------|----------------------------------------|--|--|--|--| +| Signal-to-noise ratio uncertainty | | | | | | | | | | +| Stage 2: DUT measurement | | | | | | | | | | +| 1 | Positioning misalignment | | [Normal] | [2.00] | | | | | | +| 2 | Measure distance uncertainty | | [Rectangular] | [1.73] | | | | | | +| 3 | Quality of Quiet Zone (NOTE 1) | | [Actual] | [1.00] | | | | | | +| 4 | Mismatch | | [Actual] | [1.00] | | | | | | +| 5 | Standing wave between the DUT and measurement antenna | | [U-shaped] | [1.41] | | | | | | +| 6 | gNB emulator SNR uncertainty | | [Normal] | [2.00] | | | | | | +| 7 | Phase curvature | | [U-shaped] | [1.41] | | | | | | +| 8 | Amplifier uncertainties | | [Normal] | [2.00] | | | | | | +| 9 | Random uncertainty | | [Normal] | [2.00] | | | | | | +| 10 | Influence of the XPD | | [U-shaped] | [1.41] | | | | | | +| 11 | Insertion Loss Variation | | [Rectangular] | [1.73] | | | | | | +| 12 | RF leakage (from measurement antenna to the receiver/transmitter) | | [Actual] | [1.00] | | | | | | +| 13 | Multiple measurement antenna uncertainty | | [Actual] | [1.00] | | | | | | +| 14 | DUT repositioning | | [Rectangular] | [1.73] | | | | | | +| Stage 1: Calibration measurement | | | | | | | | | | +| 15 | Mismatch | | [U-shaped] | [1.41] | | | | | | +| 16 | Amplifier Uncertainties | | [Normal] | [2.00] | | | | | | +| 17 | Misalignment of positioning System | | [Normal] | [2.00] | | | | | | +| 18 | Uncertainty of the Network Analyzer | | [Normal] | [2.00] | | | | | | +| 19 | Uncertainty of the absolute gain of the calibration antenna | | [Normal] | [2.00] | | | | | | +| 20 | Positioning and pointing misalignment between the reference antenna and the measurement antenna | | [Rectangular] | [1.73] | | | | | | +| 21 | Phase centre offset of calibration antenna | | [Rectangular] | [1.73] | | | | | | +| 22 | Quality of quiet zone for calibration process (NOTE 1) | | [Actual] | [1.00] | | | | | | +| 23 | Standing wave between reference calibration antenna and measurement antenna | | [U-shaped] | [1.41] | | | | | | +| 24 | Influence of the calibration antenna feed cable | | [Normal] | [2.00] | | | | | | +| 25 | Insertion Loss Variation | | [Rectangular] | [1.73] | | | | | | +| Systematic uncertainties | | | | | Value | | | | | +| 26 | Impact on non-ideal isolation between branches for the wireless cable mode | | | | TBD (NOTE 2) | | | | | +| Total Signal-to-Noise ratio uncertainty | | | | | | | | | | +| Other contributors affecting test result | | | | | | | | | | +| 27 | gNB emulator fading model impairments | | [Normal] | [2.00] | | | | | | +| 28 | AWGN flatness and signal flatness, max deviation for any Resource Block, relative to average over BW Config | | [Actual] | 1.00 | | | | | | +| 29 | Result variation due to finite test time | | [Actual] | [1.00] | | | | | | + +NOTE 1: The values from Enhanced IFF seem rather optimistic for MultiRX and should be further updated with the considerations of 2AoA impact + +NOTE 2: FFS which is relying on the min. isolation requirements. + +# Annex B: UE coordinate system + +## B.1 Reference coordinate system + +This annex defines the measurement coordinate system for the NR UE. The reference coordinate system is provided in Figure B.1-1 below while Figure B.1-2 shows the DUT in the default alignment, i.e., the DUT and the reference coordinate systems are aligned with $\alpha = 0^\circ$ and $\beta = 0^\circ$ and $\gamma = 0^\circ$ where $\alpha$ , $\beta$ , and $\gamma$ describe the relative angles between the two coordinate systems. + +![Figure B.1-1: Reference coordinate system diagram showing a 3D coordinate system with axes +x, +y, and +z. A sphere is centered at the origin. A vector labeled '(to Antenna)' points from the origin to a point on the sphere. The angle between the +z axis and this vector is labeled theta. The angle between the +y axis and the projection of the vector onto the xy-plane is labeled phi. Two dashed circles represent the phi-polarization and theta-polarization planes.](a5ac2ed01d588d4d979f42717117c315_img.jpg) + +The diagram illustrates the reference coordinate system for an NR UE. It features a 3D Cartesian coordinate system with axes labeled $+x$ , $+y$ , and $+z$ . A sphere is centered at the origin. A vector, labeled "(to Antenna)", originates from the origin and points to a location on the sphere's surface. The angle between the $+z$ axis and this vector is denoted by $\theta$ . The angle between the $+y$ axis and the projection of the vector onto the $xy$ -plane is denoted by $\phi$ . Two dashed circles are shown: one representing the $\phi$ -polarization plane and the other representing the $\theta$ -polarization plane. + +Figure B.1-1: Reference coordinate system diagram showing a 3D coordinate system with axes +x, +y, and +z. A sphere is centered at the origin. A vector labeled '(to Antenna)' points from the origin to a point on the sphere. The angle between the +z axis and this vector is labeled theta. The angle between the +y axis and the projection of the vector onto the xy-plane is labeled phi. Two dashed circles represent the phi-polarization and theta-polarization planes. + +Figure B.1-1: Reference coordinate system + +![Figure B.1-2: DUT default alignment to coordinate system. The diagram shows a smartphone oriented vertically. A vertical arrow labeled '+Z' points upwards from the top of the phone, with the label 'Top of phone' next to it. A horizontal arrow labeled '+Y' points to the right from the side of the phone, with the label 'Side of phone' next to it. A diagonal arrow labeled '+X' points towards the bottom-left from the front of the phone, with the label 'Screen looks this way' next to it. The phone has three buttons at the bottom and a camera at the top.](c13f6935817282291ff1db48a1488a68_img.jpg) + +Figure B.1-2: DUT default alignment to coordinate system. The diagram shows a smartphone oriented vertically. A vertical arrow labeled '+Z' points upwards from the top of the phone, with the label 'Top of phone' next to it. A horizontal arrow labeled '+Y' points to the right from the side of the phone, with the label 'Side of phone' next to it. A diagonal arrow labeled '+X' points towards the bottom-left from the front of the phone, with the label 'Screen looks this way' next to it. The phone has three buttons at the bottom and a camera at the top. + +**Figure B.1-2: DUT default alignment to coordinate system** + +The following aspects are necessary: + +- A basic understanding of the top and bottom of the device is needed in order to define unambiguous DUT positioning requirements for the test, e.g., in the drawings used in this annex, the three buttons are on the bottom of the device (front) and the camera is on the top of the device (back). +- An understanding of the origin and alignment the coordinate system inside the test system, i.e. the directions in which the x, y, z axes point inside the test chamber, is needed in order to define unambiguous DUT orientation, DUT beam, signal, interference, and measurement angles. + +## B.2 Alternate coordinate system for 2AoA testing + +Considering +AoA and -AoA are always on the meridian, the Reference coordinate system is used for Rel-18 multi-Rx testing. The Alternate coordinate system could be considered for the cases when the AoA pairs do not lie along the same meridian. + +The performance of UEs with multi-Rx chain reception DL with 2 active AoA is agreed to be measured with 3D scan on the spherical surface using constant step size grids. Therefore, the test point of AoA1 on the spherical surface can be expressed as $(\theta, \phi)$ in the same way it is defined for legacy RF testing with 1 AoA. In the case of the AoA2, the test points require certain angle separation with respect to AoA1. However, the direction of AoA2, which is also called as “AoA1-AoA2 DL Orientation Vector” in clause 5.3.5, may introduce ambiguity without additional instructions. The situation is illustrated in Figure B.2-1. + +![Figure B.2-1: Illustration of possible AoA pairs on the test point of AoA1. The diagram shows a smartphone at the center of a green circle. A black arrow labeled 'AoA1' points from the phone to a point on the circle. A yellow line extends from the phone to another point on the circle, representing the 'Possible directions of AoA2'. A dashed grey line connects the phone to this second point. A blue arc between the two lines is labeled 'Fixed offset between the two AoAs'.](8e1795da0362b48209b7a5f6e7a590fd_img.jpg) + +Figure B.2-1: Illustration of possible AoA pairs on the test point of AoA1. The diagram shows a smartphone at the center of a green circle. A black arrow labeled 'AoA1' points from the phone to a point on the circle. A yellow line extends from the phone to another point on the circle, representing the 'Possible directions of AoA2'. A dashed grey line connects the phone to this second point. A blue arc between the two lines is labeled 'Fixed offset between the two AoAs'. + +**Figure B.2-1 Illustration of possible AoA pairs on the test point of AoA1** + +In order to simplify the representation of the AoA pairs per test points of AoA1, the alternate coordinate system nomenclature described in this section can be used to express the AoA pairs with one coordinate, and it could be used also for the situation where AoA2 does not lie in the same meridian as of AoA1. + +In this alternate coordinate system nomenclature for 2AoA testing, the Reference coordinates of AoA1 ( $\theta, \phi$ ) could be extended to $(\theta, \phi, \omega)$ ( $\theta, \phi, \omega$ ), where $\omega$ corresponds to the AoA1-AoA2 DL Orientation Vector. In detail, $\omega$ is the angle between the AoA1-AoA2 DL Orientation Vector and the reference axis in the assistant plane. + +The assistant plane is orthogonal to the AoA1 direction, and the $Z'$ axis correspond to the projection of the meridian (points with same fixed $\phi$ angle) of AoA1 into the assistant plane. I.e. in case of $\theta < 90^\circ$ , $+Z'$ corresponds to the cross point of $+Z$ axis and the assistant plane (see Figure B.2-2a). In case of $\theta > 90^\circ$ , $-Z'$ corresponds to the cross point of $-Z$ axis and the assistant plane (see Figure B.2-2b). + +![Figure B.2-2: Illustration of Assistant Plane of the alternate coordinate system. It consists of two diagrams, (a) and (b), both showing a 3D coordinate system with X, Y, Z axes. In (a), the Assistant Plane is above the XY plane, containing point AoA1. The angle theta is between the Z-axis and the vector to AoA1, and phi is the azimuthal angle. In (b), the Assistant Plane is below the XY plane, also containing point AoA1, with similar angle definitions.](be2d9105109f6a87907ab68cb88548d9_img.jpg) + +a) case of $\theta < 90^\circ$ + +b) case of $\theta < 90^\circ$ + +Figure B.2-2: Illustration of Assistant Plane of the alternate coordinate system. It consists of two diagrams, (a) and (b), both showing a 3D coordinate system with X, Y, Z axes. In (a), the Assistant Plane is above the XY plane, containing point AoA1. The angle theta is between the Z-axis and the vector to AoA1, and phi is the azimuthal angle. In (b), the Assistant Plane is below the XY plane, also containing point AoA1, with similar angle definitions. + +**Figure B.2-2 Illustration of Assistant Plane of the alternate coordinate system** + +Finally, $\omega$ is the angle from the reference axis $Z'$ to the AoA1-AoA2 DL Orientation Vector in clockwise direction (see Figure B.2-3). + +![Figure B.2-3: Illustration of angle omega in the alternate coordinate system. It shows a 2D view of the Assistant Plane with a vertical Z' axis (positive up, negative down) and a vector pointing to AoA2 from AoA1. The angle omega is measured clockwise from the positive Z' axis to the vector.](e0740204d7aa33697c8f2d59c4cca51b_img.jpg) + +Figure B.2-3: Illustration of angle omega in the alternate coordinate system. It shows a 2D view of the Assistant Plane with a vertical Z' axis (positive up, negative down) and a vector pointing to AoA2 from AoA1. The angle omega is measured clockwise from the positive Z' axis to the vector. + +**Figure B.2-3 Illustration of angle $\omega$ in the alternate coordinate system** + +This alternate coordinate system can also cover the theoretical cases when the AoA pairs do not lie along the same meridian, and eliminate the possible ambiguity on test point expression. + +## B.3 Test conditions and angle definitions + + + +This sub-annex provides the test conditions and angle definitions for twelve permitted device orientations for the initial test condition. With the convenience of defining the permitted alignments/orientations, they are divided into three + +groups as shown from Table B.3-1 to Table B.3-3. The DUT orientation to be tested is chosen from Table B.3-1, Table B.3-2 and Table B.3-3 by UE vendor declaration. + +**Table B.3-1: Test conditions and angle definitions for Alignment Option 1** + +| Test condition | DUT orientation | Diagram | +|-----------------------------|-------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Orientation 1
(Option 1) | $\alpha = 0^\circ;$
$\beta = 0^\circ;$
$\gamma = 0^\circ$ |

Image: Diagram for Orientation 1 (Option 1) showing a Device Under Test (DUT) mounted on a stand. The DUT is oriented vertically with its front face towards the viewer. A 3D coordinate system is overlaid on the DUT, with the x-axis pointing up, the y-axis pointing left, and the z-axis pointing right. Four small icons in the corners represent different test positions: top-left, top-right, bottom-left, and bottom-right.

| +| Orientation 1
(Option 2) | $\alpha = 0^\circ;$
$\beta = 0^\circ;$
$\gamma = 180^\circ$ |

Image: Diagram for Orientation 1 (Option 2) showing the DUT rotated 180 degrees around the z-axis compared to the first diagram. The front face is now facing away from the viewer.

| +| Orientation 2
(Option 1) | $\alpha = 180^\circ;$
$\beta = 0^\circ;$
$\gamma = 0^\circ$ |

Image: Diagram for Orientation 2 (Option 1) showing the DUT rotated 180 degrees around the x-axis compared to the first diagram. The front face is now facing downwards.

| +| Orientation 2
(Option 2) | $\alpha = 0^\circ;$
$\beta = 180^\circ;$
$\gamma = 0^\circ$ |

Image: Diagram for Orientation 2 (Option 2) showing the DUT rotated 180 degrees around the y-axis compared to the first diagram. The front face is now facing to the right.

| + +NOTE 1: The combination of rotations is captured by matrix $M=R_z(\gamma) \cdot R_y(\beta) \cdot R_x(\alpha)$ + +Table B.3-2: Test conditions and angle definitions for Alignment Option 2 + +| Test condition | DUT orientation | Diagram | +|-----------------------------|---------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Orientation 1
(Option 1) | $\alpha = 0^\circ;$
$\beta = -90^\circ;$
$\gamma = 0^\circ$ |

Image: Diagram for Orientation 1 (Option 1) showing a device under test (DUT) on a stand with a coordinate system (x, y, z) and a color-coded radiation pattern. The DUT is oriented vertically with its main beam pointing upwards. Test antennas are positioned around it.

| +| Orientation 1
(Option 2) | $\alpha = 0^\circ;$
$\beta = -90^\circ;$
$\gamma = 180^\circ$ |

Image: Diagram for Orientation 1 (Option 2) showing the DUT rotated 180 degrees around the z-axis compared to the first row. The main beam still points upwards.

| +| Orientation 2
(Option 1) | $\alpha = 180^\circ;$
$\beta = 90^\circ;$
$\gamma = 0^\circ$ |

Image: Diagram for Orientation 2 (Option 1) showing the DUT rotated 180 degrees around the x-axis and 90 degrees around the y-axis. The main beam now points downwards.

| +| Orientation 2
(Option 2) | $\alpha = 0^\circ;$
$\beta = 90^\circ;$
$\gamma = 0^\circ$ |

Image: Diagram for Orientation 2 (Option 2) showing the DUT rotated 90 degrees around the y-axis. The main beam now points to the right.

| + +NOTE 1: The combination of rotations is captured by matrix $M=R_z(\gamma) \cdot R_y(\beta) \cdot R_x(\alpha)$ + +Table B.3-3: Test conditions and angle definitions for Alignment Option 3 + +| Test condition | DUT orientation | Diagram | +|-----------------------------|--------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Orientation 1
(Option 1) | $\alpha = 90^\circ;$
$\beta = 0^\circ;$
$\gamma = 0^\circ$ | Diagram for Orientation 1 (Option 1) showing a DUT on a rotating platform with signal and interferer directions. A 3D diagram showing a Device Under Test (DUT) mounted on a circular rotating platform. The DUT is a vertical rectangular panel. A coordinate system is defined with the Z-axis pointing horizontally to the right, the X-axis pointing vertically upwards, and the Y-axis pointing into the page. A green vertical line represents the signal direction. Four red circular icons with arrows indicate interferer directions: two from the top-left and two from the top-right. A blue circular icon with an arrow indicates a signal direction from the right. A color-coded heatmap is shown on the front face of the DUT. | +| Orientation 1
(Option 2) | $\alpha = 90^\circ;$
$\beta = 0^\circ;$
$\gamma = 180^\circ$ | Diagram for Orientation 1 (Option 2) showing a DUT on a rotating platform with signal and interferer directions. A 3D diagram similar to the first one, but the DUT panel is rotated 180 degrees around the Z-axis. The signal and interferer directions remain the same as in the first diagram. | +| Orientation 2
(Option 1) | $\alpha = -90^\circ;$
$\beta = 0^\circ;$
$\gamma = 0^\circ$ | Diagram for Orientation 2 (Option 1) showing a DUT on a rotating platform with signal and interferer directions. A 3D diagram showing the DUT rotated 90 degrees counter-clockwise around the Z-axis. The signal and interferer directions are consistent with the previous diagrams. | +| Orientation 2
(Option 2) | $\alpha = 90^\circ;$
$\beta = 180^\circ;$
$\gamma = 0^\circ$ | Diagram for Orientation 2 (Option 2) showing a DUT on a rotating platform with signal and interferer directions. A 3D diagram showing the DUT rotated 90 degrees clockwise around the Z-axis. The signal and interferer directions are consistent with the previous diagrams. | + +NOTE 1: The combination of rotations is captured by matrix $M = R_z(\gamma) \cdot R_y(\beta) \cdot R_x(\alpha)$ + +For each UE requirement and test case, each of the parameters in Table B.3-1 to Table B.3-3 need to be recorded, such that DUT positioning, DUT beam direction, and angles of the signal, link/interferer, and measurement are specified in terms of the fixed coordinate system. + +Due to the non-commutative nature of rotations, the order of rotations is important and needs to be defined when multiple DUT orientations are tested. + +The rotations around the x, y, and z axes can be defined with the following rotation matrices + +$$R_x(\alpha) = \begin{bmatrix} 1 & 0 & 0 & 0 \\ 0 & \cos \alpha & -\sin \alpha & 0 \\ 0 & \sin \alpha & \cos \alpha & 0 \\ 0 & 0 & 0 & 1 \end{bmatrix}$$ + +$$R_y(\beta) = \begin{bmatrix} \cos \beta & 0 & \sin \beta & 0 \\ 0 & 1 & 0 & 0 \\ -\sin \beta & 0 & \cos \beta & 0 \\ 0 & 0 & 0 & 1 \end{bmatrix}$$ + +and + +$$R_z(\gamma) = \begin{bmatrix} \cos \gamma & -\sin \gamma & 0 & 0 \\ \sin \gamma & \cos \gamma & 0 & 0 \\ 0 & 0 & 1 & 0 \\ 0 & 0 & 0 & 1 \end{bmatrix}.$$ + +with the respective angles of rotation, $\alpha$ , $\beta$ , $\gamma$ and + +$$\begin{bmatrix} x' \\ y' \\ z' \\ 1 \end{bmatrix} = R \begin{bmatrix} x \\ y \\ z \\ 1 \end{bmatrix}$$ + +Additionally, any translation of the DUT can be defined with the translation matrix + +$$T(t_x, t_y, t_z) = \begin{bmatrix} 1 & 0 & 0 & t_x \\ 0 & 1 & 0 & t_y \\ 0 & 0 & 1 & t_z \\ 0 & 0 & 0 & 1 \end{bmatrix}$$ + +with offsets $t_x$ , $t_y$ , $t_z$ in x, y, and z, respectively and with + +$$\begin{bmatrix} x' \\ y' \\ z' \\ 1 \end{bmatrix} = T \begin{bmatrix} x \\ y \\ z \\ 1 \end{bmatrix}$$ + +The combination of rotations and translation is captured by the multiplication of rotation and translation matrices. + +For instance, the matrix M + +$$M = T(t_x, t_y, t_z) \cdot R_z(\gamma) \cdot R_y(\beta) \cdot R_x(\alpha)$$ + +describes an initial rotation of the DUT around the x axis with angle $\alpha$ , a subsequent rotation around the y axis with angle $\beta$ , and a final rotation around the z axis with angle $\gamma$ . After those rotations, the DUT is translated by $t_x$ , $t_y$ , $t_z$ in x, y, and z, respectively. + +## B.4 DUT positioning guidelines + + + +The centre of the reference coordinate system shall be aligned with the geometric centre of the DUT in order to minimize the offset between antenna modules integrated at any position of the UE and the centre of the quiet zone. + +Near-field coupling effects between the antenna and the pedestals/positioners/fixtures generally cause increased signal ripples. Re-positioning approach is adopted for multi-Rx performance measurements to avoid AoA blockage. + +As the starting point, the initial positioner/UE orientation is selected to be ( $-90^\circ - \frac{1}{2}$ angular separation). The minimum angular separation between positioner and probe(s) are listed in Table B.4-1 as below. + +**Table B.4-1: Minimum angular separation between positioner and probe(s)** + +| Declared Angular Separation [ $^\circ$ ] | Min Angular Separation between Positioner and Probe(s) [ $^\circ$ ] | +|------------------------------------------|---------------------------------------------------------------------| +| 30 | 75 | +| 60 | 60 | +| 90 | 45 | +| 120 | 30 | +| 150 | 15 | + +# Annex G: Step size of measurement grids + +This appendix describes the assumptions and definition of the minimum number of measurement grid points for multi-Rx chain DL reception UE RF testing. + +The minimum number of measurement grid point for TRP/EIRP/EIS was investigated in [3] in which a completely random fashion is applied for both $\theta$ and $\phi$ dimensions. For multi-Rx chain DL reception UE RF testing, it has already known that measured performance of a UE is expected to systematically vary as a function of position. This systematic variation means that the strategy to completely randomize the orientation of the UE to determine MU does not apply. Moreover, for the measurement grid analysis for multi-Rx, the AoA pairs lie along longitudes of the UE reference coordination system, and the requirements apply only for the UE-declared orientation in the positioner. Therefore, it is agreed that uncertainty mechanism for multi-Rx chain DL reception UE RF testing is limited to the coarseness of the grid and doesn't depend on the UE random orientations as the legacy approach. + +Through the analysis from simulation results with antenna configuration of 6x2 and 4x2, 15deg is selected as the step size of constant-step grid. + +## G.1 Simulation results for step size + +In this clause, the simulation results with 1deg, 2deg, 5deg, 10deg, 15deg, and 30deg step sizes are shown in Table G.1-1 and Table G.1-2 considering different antenna modules placements. + +**Table G.1-1: Simulation results for step size with antenna configuration of 4x2** + +| Adjacent modules | | | | | | | | +|-----------------------------|-------|--------|--------|--------|--------|--------|--------| +| | | 30 | 60 | 90 | 120 | 150 | 180 | +| Samsung - OR | 10deg | 0.00% | -0.08% | -0.27% | 0.32% | 0.17% | 0.16% | +| Samsung - OR | 15deg | 0.21% | 0.28% | 0.23% | 0.56% | -0.08% | -0.56% | +| vivo - Arithmetic | 10deg | -0.30% | -0.50% | 0.10% | 0.20% | 0.10% | - | +| vivo - Arithmetic | 15deg | -0.20% | -1.00% | -0.70% | -1.10% | -0.10% | - | +| QC- OR | 10deg | - | 0.10% | 0.20% | 0.80% | 0.60% | 0.00% | +| QC - OR | 15deg | - | 1.60% | 0.30% | 2.60% | 2.60% | 1.50% | +| QC - Arithmetic | 10deg | - | -0.10% | 0.10% | 0.40% | 0.20% | 0.00% | +| QC - Arithmetic | 15deg | - | 1.20% | 0.10% | 1.30% | 1.90% | 1.50% | +| OPPO | 10deg | 0.21% | 0.54% | 0.27% | 0.82% | 0.84% | 0.39% | +| OPPO | 15deg | 0.97% | 0.26% | 1.47% | 0.38% | 0.20% | 0.53% | +| Huawei – OR | 10deg | -0.5% | -0.2% | -0.2% | 0.3% | -0.2% | -0.5% | +| Huawei - OR | 15deg | 0.1% | 0.6% | 0.6% | 0.9% | 0.3% | 0.1% | +| Back-to-back modules | | | | | | | | +| | | 30 | 60 | 90 | 120 | 150 | 180 | +| Samsung -OR | 10deg | 0.04% | -0.11% | 0.09% | 0.25% | 0.10% | 0.09% | +| Samsung - OR | 15deg | -0.15% | -0.43% | -0.72% | -0.35% | -0.43% | -0.41% | +| vivo - Arithmetic | 10deg | 0.20% | -0.50% | 0.10% | -0.20% | -1.50% | - | +| vivo - Arithmetic | 15deg | 0.60% | 1.30% | 0.50% | 0.20% | 1.20% | - | +| QC - OR | 10deg | - | 1.20% | 0.10% | -1.10% | -0.70% | -1.30% | +| QC - OR | 15deg | - | 1.50% | 0.40% | -3.20% | -2.80% | -2.20% | +| QC - Arithmetic | 10deg | - | 0.60% | 0.10% | -0.20% | -0.50% | -1.30% | +| QC - Arithmetic | 15deg | - | 0.70% | 0.30% | -0.90% | -1.90% | -2.20% | +| OPPO | 10deg | 2.93% | 3.48% | 0.16% | 2.74% | 0.81% | 1.29% | +| OPPO | 15deg | 3.65% | 4.56% | 0.41% | 0.77% | 1.22% | 1.03% | +| Huawei – OR | 10deg | 0.1% | 0.3% | 0.2% | -0.3% | 0.5% | - | +| Huawei - OR | 15deg | 0.4% | -0.6% | 0.8% | 0.4% | 0.9% | - | +| Same side modules | | | | | | | | +| | | 30 | 60 | 90 | 120 | 150 | 180 | +| Samsung - OR | 10deg | -0.02% | 0.10% | 0.28% | 0.25% | 0.31% | 0.04% | +| Samsung - OR | 15deg | -0.16% | -0.35% | -0.08% | -0.23% | 0.07% | -0.30% | +| vivo - Arithmetic | 10deg | -1.20% | 0.50% | 0.10% | 1.00% | 0.50% | - | +| vivo - Arithmetic | 15deg | -0.40% | -0.40% | -0.20% | 0.40% | -0.40% | - | +| OPPO | 10deg | 1.25% | 0.24% | 0.50% | 0.23% | 2.66% | 1.96% | +| OPPO | 15deg | 0.24% | 1.74% | 2.08% | 0.25% | 1.35% | 1.10% | +| Huawei – OR | 10deg | -0.4% | 0.2% | 0.3% | 0.6% | 0.4% | -0.4% | +| Huawei - OR | 15deg | -0.2% | -0.5% | -0.2% | 0.3% | 0.1% | -0.2% | + +Table G.1-2: Simulation results for step size with antenna configuration of 6x2 + +| Adjacent modules | | | | | | | | +|-----------------------------|-------|--------|--------|--------|--------|--------|--------| +| | | 30 | 60 | 90 | 120 | 150 | 180 | +| Samsung - OR | 10deg | 0.05% | -0.03% | 0.00% | 0.02% | -0.14% | -0.12% | +| Samsung - OR | 15deg | 0.12% | -0.13% | -0.20% | 0.04% | -0.44% | -0.39% | +| QC- OR | 10deg | - | 0.10% | -0.20% | 0.40% | 0.50% | 0.00% | +| QC - OR | 15deg | - | 1.40% | 0.50% | 2.70% | 2.70% | 1.80% | +| QC - Arithmetic | 10deg | - | -0.10% | -0.30% | 0.20% | 0.20% | 0.00% | +| QC - Arithmetic | 15deg | - | 1.10% | 0.60% | 1.30% | 2.00% | 1.80% | +| Back-to-back modules | | | | | | | | +| | | 30 | 60 | 90 | 120 | 150 | 180 | +| Samsung -OR | 10deg | - | - | - | - | - | - | +| Samsung - OR | 15deg | - | - | - | - | - | - | +| QC - OR | 10deg | - | 0.80% | -1.30% | -2.60% | -1.60% | -2.00% | +| QC - OR | 15deg | - | 1.90% | 2.50% | -1.30% | -2.10% | 1.00% | +| QC - Arithmetic | 10deg | - | 0.40% | -0.60% | -1.00% | -1.40% | -2.00% | +| QC - Arithmetic | 15deg | - | 0.90% | 1.30% | 0.30% | -0.90% | 1.00% | +| Same side modules | | | | | | | | +| | | 30 | 60 | 90 | 120 | 150 | 180 | +| Samsung - OR | 10deg | -0.07% | 0.15% | 0.06% | -0.17% | 0.07% | 0.01% | +| Samsung - OR | 15deg | 0.23% | 0.16% | 0.23% | -0.35% | -0.04% | -0.26% | + +# Annex H: Change history + +| Change history | | | | | | | | +|----------------|----------------|------------|----|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-08 | RAN4#10 4e | R4-2213182 | | | | Initial skeleton | 0.0.1 | +| 2023-03 | RAN4#10 6 | R4-2300085 | | | | The following TPs were agreed:
- R4-2300086, TP on TR 38.871 for editorial correction and general aspects, Qualcomm Incorporated
- R4-2302924, TP to introduce Multi-AoA UE RF Test Aspects, Keysight Technologies UK Ltd
- R4-2302150, TP on TR 38.871 calibration measurement procedure, Huawei, HiSilicon | 0.1.0 | +| 2023-04 | RAN4#10 6bis-e | R4-2305886 | | | | The following TP was agreed:
- R4-2305886, TP to introduce Multi-AoA UE RF Test Aspects, Keysight Technologies | 0.2.0 | +| 2023-05 | RAN4#10 7 | R4-2309247 | | | | The following TPs were agreed:
- R4-2309287, TP to TR 38.871 on 3-axis positioner considerations, Qualcomm Incorporated
- R4-2309246, TP to TR 38.871 on RRM test method, Qualcomm Incorporated | 0.3.0 | +| 2023-08 | RAN4#10 8 | R4-2312890 | | | | The following TPs were agreed:
- R4-2313887, TP for assistant coordination system, OPPO, ROHDE & SCHWARZ, Qualcomm Incorporated
- R4-2312889, TP to TR38.871 on UE RF testing methodology, Qualcomm Incorporated | 0.4.0 | +| 2023-10 | RAN4#10 8bis | R4-2316513 | | | | The following TPs were agreed:
- R4-2316948, TP on TR 38.871 for RRM test method, Qualcomm Incorporated
- R4-2316949, TP on TR 38.871 for Demodulation test method, Qualcomm Incorporated | 0.5.0 | +| 2023-11 | RAN4#10 9 | R4-2320391 | | | | The following TPs were agreed:
- R4-2321102, TP to TR38.871 for test procedure of UE RF multi-Rx, OPPO, Samsung
- R4-2321101, TP to TR 38.871 for UE coordinate system, OPPO, Keysight Technologies, Rohde & Schwarz, Qualcomm Incorporated
- R4-2320390, TP to TR 38.871 on draft summary and editorial changes, Qualcomm Incorporated
- R4-2321103, TP to TR 38.871 on step size of measurement grid, Qualcomm Incorporated
- R4-2321104, TP to TR 38.871 on RRM test method, Qualcomm Incorporated, Huawei, HiSilicon
- R4-2321105, TP to TR 38.871 on Demodulation test method, Qualcomm Incorporated
- R4-2321106, TP to TR 38.871 on MU assessment, Qualcomm Incorporated, Huawei, HiSilicon, vivo | 0.6.0 | +| 2023-12 | RAN#102 | RP-233172 | | | | 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/38_series/38876/02c999e5846341813b658e446e9a6fda_img.jpg b/marked/Rel-18/38_series/38876/02c999e5846341813b658e446e9a6fda_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a3da51d34f6ca3ddbe6b8300e6812362deeacc8 --- /dev/null +++ b/marked/Rel-18/38_series/38876/02c999e5846341813b658e446e9a6fda_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7edbb7538772360bba1cc6ff4924145d4b52cb1bcafe04f45bc764153a8a4049 +size 57774 diff --git a/marked/Rel-18/38_series/38876/068b3a3247570c4b78342a943f15de9e_img.jpg b/marked/Rel-18/38_series/38876/068b3a3247570c4b78342a943f15de9e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd5903588d8bb5dd72b9b04fad59d30c0e7d2237 --- /dev/null +++ b/marked/Rel-18/38_series/38876/068b3a3247570c4b78342a943f15de9e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cef57aea54960a1dd919911c89d89250e6cacc078bf0eaadce91469dbb6b37e8 +size 51161 diff --git a/marked/Rel-18/38_series/38876/07c5a1c0fddd7da92a8427f5af840ffa_img.jpg b/marked/Rel-18/38_series/38876/07c5a1c0fddd7da92a8427f5af840ffa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6918a34a7fc75a4444ec7f39b4103cbc3e89a052 --- /dev/null +++ b/marked/Rel-18/38_series/38876/07c5a1c0fddd7da92a8427f5af840ffa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98dc5d02b0b1abd4d25610780433b9ea0cf73c395c20c3d3c479626ad1a029c1 +size 50271 diff --git a/marked/Rel-18/38_series/38876/0892c0cb3b8502a44c4fe4e786be912a_img.jpg b/marked/Rel-18/38_series/38876/0892c0cb3b8502a44c4fe4e786be912a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5327654fb48bb8387a52dad7f2c5b0c62c5ba99 --- /dev/null +++ b/marked/Rel-18/38_series/38876/0892c0cb3b8502a44c4fe4e786be912a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e604001541e1b9908972d7b2a877a9825871e3f98e7dcfc4f5da7f3ed8c333ba +size 61420 diff --git a/marked/Rel-18/38_series/38876/09b5a76dd3d981abcc585df1314ef30a_img.jpg b/marked/Rel-18/38_series/38876/09b5a76dd3d981abcc585df1314ef30a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c89450ce6e89074c2f21afd653ea8b41b5544f30 --- /dev/null +++ b/marked/Rel-18/38_series/38876/09b5a76dd3d981abcc585df1314ef30a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6473b76a25a4f516d49b7cd105e31d8b3ec10823f2c0e48ed16010bbe5fb408 +size 52321 diff --git a/marked/Rel-18/38_series/38876/0aa15f5c9c3edae230985491199cfe8b_img.jpg b/marked/Rel-18/38_series/38876/0aa15f5c9c3edae230985491199cfe8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eeeef6f932f96fb259b4d9c5543ec18f72a1297a --- /dev/null +++ b/marked/Rel-18/38_series/38876/0aa15f5c9c3edae230985491199cfe8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35479c74425be2d26089e7b48a1d3694542f89784d4161bbb8510f2718360c97 +size 52374 diff --git a/marked/Rel-18/38_series/38876/0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg b/marked/Rel-18/38_series/38876/0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ace72d65a51e0697fe922337dc29c86f74bb4ad --- /dev/null +++ b/marked/Rel-18/38_series/38876/0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2baed4c63302acd626bd8a442ed477931ace42bb83d996f76b26c2e08cc52023 +size 49420 diff --git a/marked/Rel-18/38_series/38876/0e32ab25c356a3b09f57f8011afd5ac8_img.jpg b/marked/Rel-18/38_series/38876/0e32ab25c356a3b09f57f8011afd5ac8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b404db87a1f2d0a72558ff656d93941d40c7fb3 --- /dev/null +++ b/marked/Rel-18/38_series/38876/0e32ab25c356a3b09f57f8011afd5ac8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:996bb9c5c02cd07f95c6cdda806eeca7d389e5ae6f5bd94b71fdfeb21e01a0c1 +size 1722 diff --git a/marked/Rel-18/38_series/38876/0efd6f12e56065db5c69e0c6619267e7_img.jpg b/marked/Rel-18/38_series/38876/0efd6f12e56065db5c69e0c6619267e7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbedcb38bc3c8c14274c2e5345f09e987c67f6d5 --- /dev/null +++ b/marked/Rel-18/38_series/38876/0efd6f12e56065db5c69e0c6619267e7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06105e95343037ac081295528a9d6349fcf49e479ca28fe03e2ebe3c6de5c55c +size 1664 diff --git a/marked/Rel-18/38_series/38876/1071a283fcadf8d3e2ff23b77eefd4a8_img.jpg b/marked/Rel-18/38_series/38876/1071a283fcadf8d3e2ff23b77eefd4a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20ca9e60638c629f42e8cdbdad770def50952824 --- /dev/null +++ b/marked/Rel-18/38_series/38876/1071a283fcadf8d3e2ff23b77eefd4a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb28d0e2304e0153aeca1b1159502e19be3e4cf0b4004c52a7fc37c6a6bb9bad +size 54333 diff --git a/marked/Rel-18/38_series/38876/16a61693d0828a2d2a156dc0e03d06f7_img.jpg b/marked/Rel-18/38_series/38876/16a61693d0828a2d2a156dc0e03d06f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87eb640572cd36802a4e5a3af147fae7c7e2ed4e --- /dev/null +++ b/marked/Rel-18/38_series/38876/16a61693d0828a2d2a156dc0e03d06f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b465b9bb879c1449004461ae19e2236290376cafa5f0420aa5de5653612a964 +size 1380 diff --git a/marked/Rel-18/38_series/38876/198d076da025c516aec8122a6ab7db20_img.jpg b/marked/Rel-18/38_series/38876/198d076da025c516aec8122a6ab7db20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02807b1f8724f5b6936222287f3a2029efcc0be0 --- /dev/null +++ b/marked/Rel-18/38_series/38876/198d076da025c516aec8122a6ab7db20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed4051c7f64f446aac76c4b73751bd724a4e94d4f6a644cad8685a8f0dc95bbc +size 53396 diff --git a/marked/Rel-18/38_series/38876/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-18/38_series/38876/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ba42283a92a84cc502b5a36aeec2e96cb5d67e2 --- /dev/null +++ b/marked/Rel-18/38_series/38876/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9ee1371628ff297ff1d115364db1a08dbcb6850d8432e090cf2bcf4cb834092 +size 48370 diff --git a/marked/Rel-18/38_series/38876/1b1f1c6f7ba93ebe3c4f9b812d7476f9_img.jpg b/marked/Rel-18/38_series/38876/1b1f1c6f7ba93ebe3c4f9b812d7476f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c59412477996eeb97801160baee0feafd428a2d8 --- /dev/null +++ b/marked/Rel-18/38_series/38876/1b1f1c6f7ba93ebe3c4f9b812d7476f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0a564e1e67e0e71471be59791cdd0e02804e99c6df4a4483307ab7c726e664f +size 63525 diff --git a/marked/Rel-18/38_series/38876/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg b/marked/Rel-18/38_series/38876/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca51a0427d81b76630385eca9d7ff4bea0d0d0c1 --- /dev/null +++ b/marked/Rel-18/38_series/38876/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d80ace945f593080aaffac371ab2c5a8182a3e9ff69f9383ba80a81c40f6bfc0 +size 70934 diff --git a/marked/Rel-18/38_series/38876/1cd6a2d6e58e0e6d75c879a999be06ef_img.jpg b/marked/Rel-18/38_series/38876/1cd6a2d6e58e0e6d75c879a999be06ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2d40405916bffbaa9fec23874ad81b05a6159e9 --- /dev/null +++ b/marked/Rel-18/38_series/38876/1cd6a2d6e58e0e6d75c879a999be06ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9c1f29a8358aca3235a5e2e0dcb7f8ce48c553e16e57800518dbb17b9d1ff86 +size 51473 diff --git a/marked/Rel-18/38_series/38876/1f1e391c4625945115fe4f41a1c938e6_img.jpg b/marked/Rel-18/38_series/38876/1f1e391c4625945115fe4f41a1c938e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77af87eb11cb2daa5fc9fbb21019319f8b7201b4 --- /dev/null +++ b/marked/Rel-18/38_series/38876/1f1e391c4625945115fe4f41a1c938e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5473accfb08cf9503c92cdaaf22d0cee1ae40e4a7a4b049e5659ce3142fe441 +size 1426 diff --git a/marked/Rel-18/38_series/38876/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-18/38_series/38876/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c331651ae4f254c8ab1e5a4c8d0ddf56c32415a --- /dev/null +++ b/marked/Rel-18/38_series/38876/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdd7a8077a73c9e7ce50d6fe1810c0164663ea2823c40bb71edd06a846da479a +size 14578 diff --git a/marked/Rel-18/38_series/38876/28639a75145506e46966c11c1b995dd2_img.jpg b/marked/Rel-18/38_series/38876/28639a75145506e46966c11c1b995dd2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c07b81c5e92df2aae9051efe79e12ae6cdfd5c5 --- /dev/null +++ b/marked/Rel-18/38_series/38876/28639a75145506e46966c11c1b995dd2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc3235b53e28d0be572727a9723efe903bcc4e5d17b97f3c03ee1220c03f13b9 +size 48170 diff --git a/marked/Rel-18/38_series/38876/293fb0a508d182b518ea429927dfd343_img.jpg b/marked/Rel-18/38_series/38876/293fb0a508d182b518ea429927dfd343_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d62f7a1cdeed8eb8a741de8a3f12048d44704e8e --- /dev/null +++ b/marked/Rel-18/38_series/38876/293fb0a508d182b518ea429927dfd343_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43616a515ccf1439b4ec367aae48ad3a3bf6a0bd0ac4b8bdceb3d26a2a348b43 +size 65697 diff --git a/marked/Rel-18/38_series/38876/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg b/marked/Rel-18/38_series/38876/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa5009bf38a6b92df6632e307bb8ad2150844aa9 --- /dev/null +++ b/marked/Rel-18/38_series/38876/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02f4c0994cf9949b248bca3148b7f55216d657bbdacc55c5676e55980009eefd +size 50863 diff --git a/marked/Rel-18/38_series/38876/3179e999cb73ab07fad8e9407c88a3b6_img.jpg b/marked/Rel-18/38_series/38876/3179e999cb73ab07fad8e9407c88a3b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2acb737aa41d39ae373cd7df0c340b3011887e5 --- /dev/null +++ b/marked/Rel-18/38_series/38876/3179e999cb73ab07fad8e9407c88a3b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6509f30c8c89c8c0729940cba5da51e04b4b0a6d53c3ef06e1738ef9302260c0 +size 48147 diff --git a/marked/Rel-18/38_series/38876/343b095a7665e9a50574a33180bc51e4_img.jpg b/marked/Rel-18/38_series/38876/343b095a7665e9a50574a33180bc51e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b6b116d1ee12445ad7832c5bc5455d600ce8dbd --- /dev/null +++ b/marked/Rel-18/38_series/38876/343b095a7665e9a50574a33180bc51e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:145b006ead37f268f46cb15648383cade75d0acdd6bac1631631343cc388400f +size 58305 diff --git a/marked/Rel-18/38_series/38876/36f66d23ff319c73247feee55fd2dfb1_img.jpg b/marked/Rel-18/38_series/38876/36f66d23ff319c73247feee55fd2dfb1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..131ba16603c19afca5826d3bc79d012440c9fdf4 --- /dev/null +++ b/marked/Rel-18/38_series/38876/36f66d23ff319c73247feee55fd2dfb1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2000246d0e211c7956e5b02ec07cb0997bb0e33ecd90562b7262b73a04160033 +size 36333 diff --git a/marked/Rel-18/38_series/38876/38e1f09a72ec6ec6cdce4357bc9b4024_img.jpg b/marked/Rel-18/38_series/38876/38e1f09a72ec6ec6cdce4357bc9b4024_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36c5ca9fc00e3b029be53a0e525af34c108d7912 --- /dev/null +++ b/marked/Rel-18/38_series/38876/38e1f09a72ec6ec6cdce4357bc9b4024_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01fdfb7d803f77df90f594f989e03466170741a0100c314aa76a416a6d44d5b1 +size 64926 diff --git a/marked/Rel-18/38_series/38876/3a310163273edcf70c19269a06d0cdf2_img.jpg b/marked/Rel-18/38_series/38876/3a310163273edcf70c19269a06d0cdf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49a2f7bca31996f62e7786c29bdd921139f8d1b5 --- /dev/null +++ b/marked/Rel-18/38_series/38876/3a310163273edcf70c19269a06d0cdf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8a2259e4781fdbe8731ecbdb4f8924a61e9dd1e249a5178a0265b01f8b6103e +size 50134 diff --git a/marked/Rel-18/38_series/38876/4349d5e2b079af7d2e45e10a3b8235e9_img.jpg b/marked/Rel-18/38_series/38876/4349d5e2b079af7d2e45e10a3b8235e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82f16dcdfa7fe728bbb6ed7a0f178bd2b00a0407 --- /dev/null +++ b/marked/Rel-18/38_series/38876/4349d5e2b079af7d2e45e10a3b8235e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c6e02e1b3ecb0d6811b69e859b370611ad54fd64e3117b361ab6455ddaff3be +size 64106 diff --git a/marked/Rel-18/38_series/38876/43cd26e92a1c09efb81d26db4787dcb6_img.jpg b/marked/Rel-18/38_series/38876/43cd26e92a1c09efb81d26db4787dcb6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0fb293a065732b7fd085d357784694796e81eba6 --- /dev/null +++ b/marked/Rel-18/38_series/38876/43cd26e92a1c09efb81d26db4787dcb6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfd61b0ee9a89d82e8a232ca75a565ea56bce1fbe6f96c810e935ec6e3065f60 +size 34833 diff --git a/marked/Rel-18/38_series/38876/449dd9d482c5b47f1c013ce3e18b09e6_img.jpg b/marked/Rel-18/38_series/38876/449dd9d482c5b47f1c013ce3e18b09e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a76f7641e79886f2859f31f059e6f4ce3e447804 --- /dev/null +++ b/marked/Rel-18/38_series/38876/449dd9d482c5b47f1c013ce3e18b09e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:923122371c236e2eb7fff2a7d0e701c813d9b1d50e759a1ac6d4685b20864a8a +size 52269 diff --git a/marked/Rel-18/38_series/38876/49806c5ac206335a657bc126f17d37e8_img.jpg b/marked/Rel-18/38_series/38876/49806c5ac206335a657bc126f17d37e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a03249efc670e76c8bb1832db3cb387bd0484f5 --- /dev/null +++ b/marked/Rel-18/38_series/38876/49806c5ac206335a657bc126f17d37e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4404bac3c63aaf3f878c093391cc6b575581f4b594277b9728ac59ebb104374d +size 59432 diff --git a/marked/Rel-18/38_series/38876/4d2624b1b2871a23382b647cd71e1c1c_img.jpg b/marked/Rel-18/38_series/38876/4d2624b1b2871a23382b647cd71e1c1c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c574fd675b229afeafab2351168f8081fcb131de --- /dev/null +++ b/marked/Rel-18/38_series/38876/4d2624b1b2871a23382b647cd71e1c1c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8aac8dec32c0fa5cd11aaa81174d664fc7983f384f112b809cd574a5c2d9d14 +size 1225 diff --git a/marked/Rel-18/38_series/38876/4ee6ee5ce67694dbc95537938e09a917_img.jpg b/marked/Rel-18/38_series/38876/4ee6ee5ce67694dbc95537938e09a917_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05f320145ee614050831bfe3e282d23d80255e2f --- /dev/null +++ b/marked/Rel-18/38_series/38876/4ee6ee5ce67694dbc95537938e09a917_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89dea85f42e082e09473f884a22fc506013f4b8ae58aff05d6e07e9ca9e8babf +size 59017 diff --git a/marked/Rel-18/38_series/38876/53d8bef47c63e0897de4cd058bad2cbd_img.jpg b/marked/Rel-18/38_series/38876/53d8bef47c63e0897de4cd058bad2cbd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aacff6ae22a83e19c8d77cc2deb295de2765adb3 --- /dev/null +++ b/marked/Rel-18/38_series/38876/53d8bef47c63e0897de4cd058bad2cbd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c3811d8575d5200a1697ff2398e3da7927e7cb12d3efa3c0b77a7810c1d4b56 +size 60537 diff --git a/marked/Rel-18/38_series/38876/54bab05b404ce895e109a02e758a548a_img.jpg b/marked/Rel-18/38_series/38876/54bab05b404ce895e109a02e758a548a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9da5fde7eeecb59d8b216bebc820b7ce5e7242a6 --- /dev/null +++ b/marked/Rel-18/38_series/38876/54bab05b404ce895e109a02e758a548a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2071b9db2c7d43c75468c18caac0c5ac64ef349eb42a3cca7ee46273e8534c9c +size 52032 diff --git a/marked/Rel-18/38_series/38876/5a8d83665fa993ed599f2eb41fd6c7f5_img.jpg b/marked/Rel-18/38_series/38876/5a8d83665fa993ed599f2eb41fd6c7f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3be3666776293aab35d0eb367fbbd0c43be69992 --- /dev/null +++ b/marked/Rel-18/38_series/38876/5a8d83665fa993ed599f2eb41fd6c7f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fb241e9529494bba7951a669b8d96a58014ff774940031d730fcf3010bfabb8 +size 50031 diff --git a/marked/Rel-18/38_series/38876/5ae0af74768ab8a326191d61781d98e6_img.jpg b/marked/Rel-18/38_series/38876/5ae0af74768ab8a326191d61781d98e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d27c8d77d8d206d3597dee57c221709131d98209 --- /dev/null +++ b/marked/Rel-18/38_series/38876/5ae0af74768ab8a326191d61781d98e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c36fd5eb7ff39fe795509792c5c5085fa96dad776581b50b55e28efe29659db4 +size 62735 diff --git a/marked/Rel-18/38_series/38876/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38876/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0ded0d35a1e31630713c1688c3dd40c728680d4 --- /dev/null +++ b/marked/Rel-18/38_series/38876/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20d71d42c49dcb543615eaa67ab7ecf46230df54b469e2c33caa8088c50a2e6c +size 9459 diff --git a/marked/Rel-18/38_series/38876/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38876/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ec6fa4115bec6a326fdb07f45cebfe65c16531e --- /dev/null +++ b/marked/Rel-18/38_series/38876/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d9721b97491eef3631a39169063baa96585697b27ff3968e4b0a343dfe7ae56 +size 5710 diff --git a/marked/Rel-18/38_series/38876/671a9a08b8506e113012e056945fd8f3_img.jpg b/marked/Rel-18/38_series/38876/671a9a08b8506e113012e056945fd8f3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63a1007681288035006db5f79cf363a3c332986b --- /dev/null +++ b/marked/Rel-18/38_series/38876/671a9a08b8506e113012e056945fd8f3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68f3467743d19d1ab08a2c25f6b5b87d4436ea79cd8fc24caa54a97914bc2d3d +size 66931 diff --git a/marked/Rel-18/38_series/38876/67408c41c75d983c13a9bd3d66953f3c_img.jpg b/marked/Rel-18/38_series/38876/67408c41c75d983c13a9bd3d66953f3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc35b216d47384093a367b799c19db4632ef2078 --- /dev/null +++ b/marked/Rel-18/38_series/38876/67408c41c75d983c13a9bd3d66953f3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4027fed28a2189f630ad7499dd1908a29dcd853a9b30bc51bb7ebafc220983c5 +size 59045 diff --git a/marked/Rel-18/38_series/38876/6752cee124f693bc4cebc66180f4f91f_img.jpg b/marked/Rel-18/38_series/38876/6752cee124f693bc4cebc66180f4f91f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe37ed34845a8baafe796cf905b15da3438a77c5 --- /dev/null +++ b/marked/Rel-18/38_series/38876/6752cee124f693bc4cebc66180f4f91f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:209427415982c97542526ce9b013c893c93b739abbe387090570beb56edf174a +size 60908 diff --git a/marked/Rel-18/38_series/38876/68d47da43cdd5782cac97f784b52c270_img.jpg b/marked/Rel-18/38_series/38876/68d47da43cdd5782cac97f784b52c270_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43e0e0ab3496f36597934ade30db10aefe79bc98 --- /dev/null +++ b/marked/Rel-18/38_series/38876/68d47da43cdd5782cac97f784b52c270_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d05a8deb659880a1748fd99ba74f53fdf922bc8f856a85715e64c34dba3a93d +size 49000 diff --git a/marked/Rel-18/38_series/38876/6dcf3c6357538aad08b1cee84fb05985_img.jpg b/marked/Rel-18/38_series/38876/6dcf3c6357538aad08b1cee84fb05985_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6833dd70d323e5f0eb78a6b92a772195dd7334c9 --- /dev/null +++ b/marked/Rel-18/38_series/38876/6dcf3c6357538aad08b1cee84fb05985_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80dc24a22e814d7b24f9adf80ee811653d95a0b9c72df2616bac710b1032ce96 +size 65302 diff --git a/marked/Rel-18/38_series/38876/70546cb98239089866510133c7fbc169_img.jpg b/marked/Rel-18/38_series/38876/70546cb98239089866510133c7fbc169_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f66b259359a655b2a108e70668b71a5277e3ee22 --- /dev/null +++ b/marked/Rel-18/38_series/38876/70546cb98239089866510133c7fbc169_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48ccbf3dd41a8dc46310489ce83775761c3277cefd9d7c873c3ebf322f210f7d +size 63718 diff --git a/marked/Rel-18/38_series/38876/7085bb654c88de392054735bda2f6ad0_img.jpg b/marked/Rel-18/38_series/38876/7085bb654c88de392054735bda2f6ad0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ee2884fad2b5883ba379f2d1901d8b03eb2152e --- /dev/null +++ b/marked/Rel-18/38_series/38876/7085bb654c88de392054735bda2f6ad0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04910164f1c2d0a2058d80c9094b447f0b4792bd102fdf57168ff47dfa67e44e +size 1440 diff --git a/marked/Rel-18/38_series/38876/70ececdbb871824c3e57cace6262c4d6_img.jpg b/marked/Rel-18/38_series/38876/70ececdbb871824c3e57cace6262c4d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1060df0f1209b5aebe947260e255ad7e3ddef9b4 --- /dev/null +++ b/marked/Rel-18/38_series/38876/70ececdbb871824c3e57cace6262c4d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4213bb05d6251d553f9c015a34444d393d26f838ad96e090bc02e9e2081ff2e1 +size 69299 diff --git a/marked/Rel-18/38_series/38876/75b9cb95f5815d6f3bbe57020a049504_img.jpg b/marked/Rel-18/38_series/38876/75b9cb95f5815d6f3bbe57020a049504_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34e52b0154a66a737f75b7843d758a36b2541698 --- /dev/null +++ b/marked/Rel-18/38_series/38876/75b9cb95f5815d6f3bbe57020a049504_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fa97c395a04048a18ec289e29f6c74150f19f669aa32c02e8ff7c56bd82c35d +size 65608 diff --git a/marked/Rel-18/38_series/38876/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Rel-18/38_series/38876/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..359310c0546c7f9787aa1c9df028619998a52dc5 --- /dev/null +++ b/marked/Rel-18/38_series/38876/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7158db2d1ea30b07209694fb81b62016161ee317c4a9e35a043c60144b2ac444 +size 41835 diff --git a/marked/Rel-18/38_series/38876/770a0d19a708e61d3fe65ae95092faed_img.jpg b/marked/Rel-18/38_series/38876/770a0d19a708e61d3fe65ae95092faed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a3b93d538fdaebd6153d82c9093aaa71986447b --- /dev/null +++ b/marked/Rel-18/38_series/38876/770a0d19a708e61d3fe65ae95092faed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:360cd8f75f4ae7d5074e39b7e509b81b975606062ed395592a8d549c11dcfdd7 +size 1622 diff --git a/marked/Rel-18/38_series/38876/771c18f874d31c59c3b8c4e247be16ca_img.jpg b/marked/Rel-18/38_series/38876/771c18f874d31c59c3b8c4e247be16ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28f2300ab41fda9b6dd4d11ae4949dff5b3b6f46 --- /dev/null +++ b/marked/Rel-18/38_series/38876/771c18f874d31c59c3b8c4e247be16ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c9edad4c3b6cc69f8ee9bc4b6b3c21782f582d8b1a8abd451f6d0fda5fd3911 +size 59976 diff --git a/marked/Rel-18/38_series/38876/77a781dfb114c3e2b399f876f1808cfd_img.jpg b/marked/Rel-18/38_series/38876/77a781dfb114c3e2b399f876f1808cfd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b3779bae92b6753c645d1d908802f0567b252a2 --- /dev/null +++ b/marked/Rel-18/38_series/38876/77a781dfb114c3e2b399f876f1808cfd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c60413ab31146595601103a39d89968e973a2187b10c2f953cd1fef201e4fbb +size 52101 diff --git a/marked/Rel-18/38_series/38876/7b833b1c4b833d2d706d8cb3aeca003c_img.jpg b/marked/Rel-18/38_series/38876/7b833b1c4b833d2d706d8cb3aeca003c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c78dc63d6a17d583c42c0592d7c98aa29927b50 --- /dev/null +++ b/marked/Rel-18/38_series/38876/7b833b1c4b833d2d706d8cb3aeca003c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90564a2a07e783069413d6d7bcb250389349b8c6fc34fccf3e8cc4028e7c9bac +size 69890 diff --git a/marked/Rel-18/38_series/38876/7b96fce298a23fd76a01ff6c176c1059_img.jpg b/marked/Rel-18/38_series/38876/7b96fce298a23fd76a01ff6c176c1059_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4678eff089d7a7b2d31c1b2b6e6e4e1b1ad2c36a --- /dev/null +++ b/marked/Rel-18/38_series/38876/7b96fce298a23fd76a01ff6c176c1059_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3cdc685e5d23cbf19968eb55945671ff2593442fb267f2269bd0ba35345875c0 +size 49145 diff --git a/marked/Rel-18/38_series/38876/7c0a9511fa02b6c2c125ff5be465186e_img.jpg b/marked/Rel-18/38_series/38876/7c0a9511fa02b6c2c125ff5be465186e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74011190fdd457eba63ac817fe2fa18657811816 --- /dev/null +++ b/marked/Rel-18/38_series/38876/7c0a9511fa02b6c2c125ff5be465186e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57c6650a29d0ef5bbf1e96c27288a69f32dadf63f6b0f2be9b121a32339f9100 +size 63255 diff --git a/marked/Rel-18/38_series/38876/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-18/38_series/38876/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a27da84ac872b20d0598dbfe75861b6fe32803e6 --- /dev/null +++ b/marked/Rel-18/38_series/38876/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37658cdb8efb2a30e6a2e1ed68a71289e16263c2be767ecc8a1f8ba244700cf2 +size 8598 diff --git a/marked/Rel-18/38_series/38876/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-18/38_series/38876/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46f47700fbe2a357919769d22272134b0841e24a --- /dev/null +++ b/marked/Rel-18/38_series/38876/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa238f11edd4aed4373e95e8a359c3e50851af322da8b03e2a1824a8db5086d7 +size 52087 diff --git a/marked/Rel-18/38_series/38876/853f59c89931a666c07903b31d098277_img.jpg b/marked/Rel-18/38_series/38876/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff94459d69e617a704ad6efb049e279b764e2a6d --- /dev/null +++ b/marked/Rel-18/38_series/38876/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf2ca87a0489f3bc46255609bc78d9749839bf597a24ddd7a998db7d924c8c3d +size 34073 diff --git a/marked/Rel-18/38_series/38876/89b3389b2c4fa1b452cf2b5daa5f82ad_img.jpg b/marked/Rel-18/38_series/38876/89b3389b2c4fa1b452cf2b5daa5f82ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21e9245845dc9fe0f3c57186fcb863fd425260c6 --- /dev/null +++ b/marked/Rel-18/38_series/38876/89b3389b2c4fa1b452cf2b5daa5f82ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ab0bbbbf330b9c759262e640343a2df29820c30390bb13c971957777691e1e2 +size 50629 diff --git a/marked/Rel-18/38_series/38876/92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg b/marked/Rel-18/38_series/38876/92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..458e443bea7f69a44d833259139b8f6ea72fd1b9 --- /dev/null +++ b/marked/Rel-18/38_series/38876/92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56fb439b86ae13721a51c6a99494b97c3570b5fa86a77ad264282630f80242c5 +size 49048 diff --git a/marked/Rel-18/38_series/38876/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg b/marked/Rel-18/38_series/38876/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14cdb29e44f940fead4280a441d68d1bf53d5813 --- /dev/null +++ b/marked/Rel-18/38_series/38876/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7e52baf0510fb01cfb8cb20b49dfa292c8366bd247ac3e4046bbf279f0615aa +size 66769 diff --git a/marked/Rel-18/38_series/38876/9a53e14a8faff0f95017f132e73e6bea_img.jpg b/marked/Rel-18/38_series/38876/9a53e14a8faff0f95017f132e73e6bea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8c43dfdbe62a14ebecf7160dd883f94266fc630 --- /dev/null +++ b/marked/Rel-18/38_series/38876/9a53e14a8faff0f95017f132e73e6bea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9c5eb30d910ada7cd78e3b91e21e16d10940b5c281348e3c93a964d8e6a4ed4 +size 60922 diff --git a/marked/Rel-18/38_series/38876/9c888dd6588358989047de6ced8b2bdb_img.jpg b/marked/Rel-18/38_series/38876/9c888dd6588358989047de6ced8b2bdb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e962a3ceafb5b10bd139faab958aa6592c42705 --- /dev/null +++ b/marked/Rel-18/38_series/38876/9c888dd6588358989047de6ced8b2bdb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66adbfece605f4d6aa90d055c4eb52ddfa2744defaa52197b0507a82dfb62045 +size 64108 diff --git a/marked/Rel-18/38_series/38876/9d18af84f9d0bd3cb990f22f91fcf938_img.jpg b/marked/Rel-18/38_series/38876/9d18af84f9d0bd3cb990f22f91fcf938_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b322ec44fb4253c20c030b047476fbe9052dcc76 --- /dev/null +++ b/marked/Rel-18/38_series/38876/9d18af84f9d0bd3cb990f22f91fcf938_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d089abf067e12af782efeaa447051ec7af006f60dbff8bd08b5d3bf167f2d3de +size 33614 diff --git a/marked/Rel-18/38_series/38876/9ded0df3aa355d1a7fdb8598fdf54bff_img.jpg b/marked/Rel-18/38_series/38876/9ded0df3aa355d1a7fdb8598fdf54bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a3fc920692d205b020f5d0f4e0d3e57b94473c7 --- /dev/null +++ b/marked/Rel-18/38_series/38876/9ded0df3aa355d1a7fdb8598fdf54bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71d5673e5c58f4a3564a3e7991fb8216291079e02d439dd868ba5a28a1fe39f1 +size 48977 diff --git a/marked/Rel-18/38_series/38876/9e4179ffe4701bec67534299c4935049_img.jpg b/marked/Rel-18/38_series/38876/9e4179ffe4701bec67534299c4935049_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b867c50d5bd3c38230e61408ebabbf8622712a6 --- /dev/null +++ b/marked/Rel-18/38_series/38876/9e4179ffe4701bec67534299c4935049_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12147c6b227cddf6bd43b289a17a646e11f86887e0ef86ad8bedbeba46383fdd +size 57162 diff --git a/marked/Rel-18/38_series/38876/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Rel-18/38_series/38876/a0739aaf13fa5a632d4faa830f6b2708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6adc68187e085ddf85ac4b73503ebd1826964272 --- /dev/null +++ b/marked/Rel-18/38_series/38876/a0739aaf13fa5a632d4faa830f6b2708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e7052dd1326aa8b9deedf413466d548b564f0592bd46da9f848dbf5ed3af1b4 +size 17041 diff --git a/marked/Rel-18/38_series/38876/a0fdaf0b566e05f53f0085cf41e2dbad_img.jpg b/marked/Rel-18/38_series/38876/a0fdaf0b566e05f53f0085cf41e2dbad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1acb6057f2222f571786f5a7c3049e3337b26af7 --- /dev/null +++ b/marked/Rel-18/38_series/38876/a0fdaf0b566e05f53f0085cf41e2dbad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4c55c8c09e2a29a759290dcea9970f9364c7ab7639186034ae466df9112084b +size 52463 diff --git a/marked/Rel-18/38_series/38876/a14ef8a0fbd175ce9b6d24cca8328ecd_img.jpg b/marked/Rel-18/38_series/38876/a14ef8a0fbd175ce9b6d24cca8328ecd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e35e00aa1269f3e7303bd1c9fcda8774b62e7ae --- /dev/null +++ b/marked/Rel-18/38_series/38876/a14ef8a0fbd175ce9b6d24cca8328ecd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b3852fef9934c9288d27f922b5e5db874b264d3d3f43668bd29f59bb1e071c8 +size 54911 diff --git a/marked/Rel-18/38_series/38876/a1849005b1686d3991afbbb3970f623d_img.jpg b/marked/Rel-18/38_series/38876/a1849005b1686d3991afbbb3970f623d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79486a90b7f4be1ba876c7b37b154d00e89f3bf1 --- /dev/null +++ b/marked/Rel-18/38_series/38876/a1849005b1686d3991afbbb3970f623d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ded9d34ee83413f384acba9f898058eb32d1b832f5a43fb11022563a955fcd07 +size 44377 diff --git a/marked/Rel-18/38_series/38876/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-18/38_series/38876/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca646b28717c784a646726ee547388a978626676 --- /dev/null +++ b/marked/Rel-18/38_series/38876/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0966bf86a1e7d9ea3a6be61bcbc6f3016273981593cb35ea20d809fe675a41b +size 19995 diff --git a/marked/Rel-18/38_series/38876/a346e19f92f1699e3f96432c0464c957_img.jpg b/marked/Rel-18/38_series/38876/a346e19f92f1699e3f96432c0464c957_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45eb492b1f9e2df12f1ef2a83101878f6b11c817 --- /dev/null +++ b/marked/Rel-18/38_series/38876/a346e19f92f1699e3f96432c0464c957_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4d36dfba89d4df450878e2325ade293cb399da1eb4237ac91125f63f2311dc0 +size 55366 diff --git a/marked/Rel-18/38_series/38876/a50451e9d6b6c7f9b9673b9bb70bae3f_img.jpg b/marked/Rel-18/38_series/38876/a50451e9d6b6c7f9b9673b9bb70bae3f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1182cf9bef0444e90017638c7919b94787be4176 --- /dev/null +++ b/marked/Rel-18/38_series/38876/a50451e9d6b6c7f9b9673b9bb70bae3f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5a2c560a6583b2c24f487e4768db28ff9eece1af63ba2ff98d7907daa62a65f +size 68636 diff --git a/marked/Rel-18/38_series/38876/a85105fd544c64ef624aa45c72378647_img.jpg b/marked/Rel-18/38_series/38876/a85105fd544c64ef624aa45c72378647_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc3fd7d0232f799668ce5c84ef12a5e7eb989a3c --- /dev/null +++ b/marked/Rel-18/38_series/38876/a85105fd544c64ef624aa45c72378647_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c66ee0d969c46dfbbb13e235f622511b95cb03adccd08b0324c6892a5cb35c65 +size 55185 diff --git a/marked/Rel-18/38_series/38876/a8f5e96261c2ea20a0f83f121d8fcbcb_img.jpg b/marked/Rel-18/38_series/38876/a8f5e96261c2ea20a0f83f121d8fcbcb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea22d66cadadc07a42b3baed6001ea3aba92d629 --- /dev/null +++ b/marked/Rel-18/38_series/38876/a8f5e96261c2ea20a0f83f121d8fcbcb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63d922eded70fcf2bc1496eaa77865818541bcb292f2b73c7d12e5485ec547f6 +size 55742 diff --git a/marked/Rel-18/38_series/38876/a9bf8827f39b1b81b7e3ead912e1a69c_img.jpg b/marked/Rel-18/38_series/38876/a9bf8827f39b1b81b7e3ead912e1a69c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..617e888e934f80e6ce1a49bc8483ace7a4479401 --- /dev/null +++ b/marked/Rel-18/38_series/38876/a9bf8827f39b1b81b7e3ead912e1a69c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e578c8e13625dc77f7cc8c13e7a31a034b9930d1934efbf3c4f4c5956ea7de39 +size 54188 diff --git a/marked/Rel-18/38_series/38876/ac7113ab2270f2d29fbc296fe31432b5_img.jpg b/marked/Rel-18/38_series/38876/ac7113ab2270f2d29fbc296fe31432b5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3af4f8369fddf12743f26c7a467d5dd89b36910 --- /dev/null +++ b/marked/Rel-18/38_series/38876/ac7113ab2270f2d29fbc296fe31432b5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe9aa3c482d20e26ae432ac32f3a3ea81b9712eb4cf6d727e395edeb120435be +size 53386 diff --git a/marked/Rel-18/38_series/38876/ad406eca7668ea7128dba19ec32a22ac_img.jpg b/marked/Rel-18/38_series/38876/ad406eca7668ea7128dba19ec32a22ac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f1cccf5b59d198048ee8e3c3a7ed0d78254e148 --- /dev/null +++ b/marked/Rel-18/38_series/38876/ad406eca7668ea7128dba19ec32a22ac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01900705d1996f4e82bd3786f6462c63112bc4d7ea62c6284e6f3904e5207aee +size 53466 diff --git a/marked/Rel-18/38_series/38876/b11f4bc2bbfc46968de10a8ad2a8902f_img.jpg b/marked/Rel-18/38_series/38876/b11f4bc2bbfc46968de10a8ad2a8902f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a36d1c20008999c45e6fb96cfe128eaed4da9ab9 --- /dev/null +++ b/marked/Rel-18/38_series/38876/b11f4bc2bbfc46968de10a8ad2a8902f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b770db210b87dfe76b5b86fd62d30db5b6edeac53397fa8c615795870b24b58 +size 55722 diff --git a/marked/Rel-18/38_series/38876/b30a71a63c0093c8f54a2a57b1f601bb_img.jpg b/marked/Rel-18/38_series/38876/b30a71a63c0093c8f54a2a57b1f601bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f80bff65cc6a7956d9b05a680641453c8e4d8e33 --- /dev/null +++ b/marked/Rel-18/38_series/38876/b30a71a63c0093c8f54a2a57b1f601bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f461a7f99ba1226e1e976ef298f53698f1da4b2edc3cf860efd53b68396a06af +size 46778 diff --git a/marked/Rel-18/38_series/38876/b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg b/marked/Rel-18/38_series/38876/b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e736cc4560156fdc584aba58032bb5fdc5b3553 --- /dev/null +++ b/marked/Rel-18/38_series/38876/b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4d3696e352b48d2852f736bb9ef6705eed2f1817e84585a3e5e974d37408245 +size 53207 diff --git a/marked/Rel-18/38_series/38876/b90dcb4c35f1875e19ca312a6cf4adae_img.jpg b/marked/Rel-18/38_series/38876/b90dcb4c35f1875e19ca312a6cf4adae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bae0fc40f0540ac4d57732c6ab640b06f1c9b917 --- /dev/null +++ b/marked/Rel-18/38_series/38876/b90dcb4c35f1875e19ca312a6cf4adae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b86295337d2f5b02af60605e9c376f70bf414a8b102a0a96c1734f83b465fb0 +size 59941 diff --git a/marked/Rel-18/38_series/38876/bacc720ff6ea9195e4dddcee588abf83_img.jpg b/marked/Rel-18/38_series/38876/bacc720ff6ea9195e4dddcee588abf83_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..181bc96a31186c55a91bc0103389780fc97b53c5 --- /dev/null +++ b/marked/Rel-18/38_series/38876/bacc720ff6ea9195e4dddcee588abf83_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47f21dd5dcaeec51bfc0bd32ede2783ec0f8b59c13b5f73d49e02977a3199ee4 +size 1671 diff --git a/marked/Rel-18/38_series/38876/bb908297bfe73e2759a9dd88ae0506f9_img.jpg b/marked/Rel-18/38_series/38876/bb908297bfe73e2759a9dd88ae0506f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94f239582556fa53342c7731d3098504dfb54a09 --- /dev/null +++ b/marked/Rel-18/38_series/38876/bb908297bfe73e2759a9dd88ae0506f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50bdba649d015516d8c9e987b5c42ea8a48d5a52f8693842fcde0cda4c5b9854 +size 33527 diff --git a/marked/Rel-18/38_series/38876/c21fe89d8034ec5b80bd47c1cd710202_img.jpg b/marked/Rel-18/38_series/38876/c21fe89d8034ec5b80bd47c1cd710202_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2982478d22823e6dd375eb528d6183c3be9e15d0 --- /dev/null +++ b/marked/Rel-18/38_series/38876/c21fe89d8034ec5b80bd47c1cd710202_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1aa9b9d5d71e4280d47ef8ee6b047fb3ac79271b85eae3d2c3b2bf41f8faa967 +size 66957 diff --git a/marked/Rel-18/38_series/38876/c53adc66eab40abd5f8b9107d950ad04_img.jpg b/marked/Rel-18/38_series/38876/c53adc66eab40abd5f8b9107d950ad04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b957558c7d834a70d91a015d5976d146d0d4f55b --- /dev/null +++ b/marked/Rel-18/38_series/38876/c53adc66eab40abd5f8b9107d950ad04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bad5887dadf3fe885a7d1a331d527fc1d6520b2d2c919d8c57c99aa5f61ed2ad +size 65791 diff --git a/marked/Rel-18/38_series/38876/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg b/marked/Rel-18/38_series/38876/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b5bd5150270ee45aac4beeaa56015f615d44d08 --- /dev/null +++ b/marked/Rel-18/38_series/38876/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0504dcc339cafa9424140c82148fe6cc738ee1ebc50f96b3bce366c020dbcdb +size 51644 diff --git a/marked/Rel-18/38_series/38876/caeb46d58919c727aa9d338ae9492077_img.jpg b/marked/Rel-18/38_series/38876/caeb46d58919c727aa9d338ae9492077_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1810c03f2ab510bca381b35c54d825624a351c81 --- /dev/null +++ b/marked/Rel-18/38_series/38876/caeb46d58919c727aa9d338ae9492077_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bac2a3bb32c82495a410e24b7cd7acd8b9b1a6ab18ed0924cc687a4c115b066 +size 46369 diff --git a/marked/Rel-18/38_series/38876/cc7bd229cf6c181b389c7a43184af609_img.jpg b/marked/Rel-18/38_series/38876/cc7bd229cf6c181b389c7a43184af609_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed4054fe5cf991e84cf29771734f889e47dde0e9 --- /dev/null +++ b/marked/Rel-18/38_series/38876/cc7bd229cf6c181b389c7a43184af609_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f527cf7feb7cf68824fe935cc01347a9d0883fd16061bdad9b47923ede7ab629 +size 49812 diff --git a/marked/Rel-18/38_series/38876/ce4bc97f7f5e2c454b76ddbda454455c_img.jpg b/marked/Rel-18/38_series/38876/ce4bc97f7f5e2c454b76ddbda454455c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97648cd527d9f9d7f489883f339dbbfadf7e8817 --- /dev/null +++ b/marked/Rel-18/38_series/38876/ce4bc97f7f5e2c454b76ddbda454455c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdd6718b5796c5263a004968051ea09283c3c31c2cf6fc2c4cc7c2c831c09bcc +size 68798 diff --git a/marked/Rel-18/38_series/38876/d49bc18ad8867b97bbb9aa580449a641_img.jpg b/marked/Rel-18/38_series/38876/d49bc18ad8867b97bbb9aa580449a641_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbbda4993991952b12a4db9a96b1eae4881c065d --- /dev/null +++ b/marked/Rel-18/38_series/38876/d49bc18ad8867b97bbb9aa580449a641_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33b0f4b8590ff73ce69b3562aa8112ea2dadaa9de3c77fa3938c96892928bdae +size 63462 diff --git a/marked/Rel-18/38_series/38876/ddfefccc6c2fcfadf4e398109548faf8_img.jpg b/marked/Rel-18/38_series/38876/ddfefccc6c2fcfadf4e398109548faf8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d93fba5eec7fe71fc24432ec9baa00236a89081 --- /dev/null +++ b/marked/Rel-18/38_series/38876/ddfefccc6c2fcfadf4e398109548faf8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3d93652a9a7e6cc4b45b244ec6df291241932bbb0e52b9ce98080756912f6e5 +size 49956 diff --git a/marked/Rel-18/38_series/38876/e0113695dbf148bf5ec34354e544414b_img.jpg b/marked/Rel-18/38_series/38876/e0113695dbf148bf5ec34354e544414b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f7db7605ca2844a4d23d367c7fb3c420c0a6957 --- /dev/null +++ b/marked/Rel-18/38_series/38876/e0113695dbf148bf5ec34354e544414b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:402bbf6a062e8d987d65e328b45c3645cdd98028c42b1524df11c8d0c3f57f30 +size 52341 diff --git a/marked/Rel-18/38_series/38876/e01f9228a215e26c8b62ad471c9d7a7f_img.jpg b/marked/Rel-18/38_series/38876/e01f9228a215e26c8b62ad471c9d7a7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92b52262fb93f96a1469fa77a8b4f89df53a8f06 --- /dev/null +++ b/marked/Rel-18/38_series/38876/e01f9228a215e26c8b62ad471c9d7a7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:027d66e6868d7d7019dd7aee86c2ae3e928095dd8c335ef29c0f1725f0669a6a +size 54052 diff --git a/marked/Rel-18/38_series/38876/e466e4c4fb08567a109bb959a765225c_img.jpg b/marked/Rel-18/38_series/38876/e466e4c4fb08567a109bb959a765225c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26f78ed44db5f0ec347245998577293eb11c0719 --- /dev/null +++ b/marked/Rel-18/38_series/38876/e466e4c4fb08567a109bb959a765225c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3263d01dbc62ca92332d163447e76ab7971dd3fca9f8fddace1dab9f93cbefc0 +size 64851 diff --git a/marked/Rel-18/38_series/38876/ee5335ab27424e6c83acfb46679a7f9b_img.jpg b/marked/Rel-18/38_series/38876/ee5335ab27424e6c83acfb46679a7f9b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..751ead22d8281fe2fd23a626fe117b472f177253 --- /dev/null +++ b/marked/Rel-18/38_series/38876/ee5335ab27424e6c83acfb46679a7f9b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa50ad8a84818428c43b849f75e18c87e053a19a9c9ea9534301625a653200d0 +size 1704 diff --git a/marked/Rel-18/38_series/38876/f455955c4bc84005728b4138f19098dc_img.jpg b/marked/Rel-18/38_series/38876/f455955c4bc84005728b4138f19098dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3084c47b75edc0486499becc379b58c6c8b6c0f --- /dev/null +++ b/marked/Rel-18/38_series/38876/f455955c4bc84005728b4138f19098dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f3d0f501395dd5dfa5dd2bc4bd1a02ae32197007d96a087db1633b1143eb3e1 +size 54891 diff --git a/marked/Rel-18/38_series/38876/f68421f5d184c116a7061977a9057e63_img.jpg b/marked/Rel-18/38_series/38876/f68421f5d184c116a7061977a9057e63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bf458a109c2d6ce52bd8657a85809449d66e7ed --- /dev/null +++ b/marked/Rel-18/38_series/38876/f68421f5d184c116a7061977a9057e63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1133ef95c65b2002885e10b97768bb22027b82da1d992b39b7629e3c80f6bd13 +size 55301 diff --git a/marked/Rel-18/38_series/38876/f6e8acf9f931452d01688d311b5c0364_img.jpg b/marked/Rel-18/38_series/38876/f6e8acf9f931452d01688d311b5c0364_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f892697371ccaac25b2f6f04a26fd16c7f3fc851 --- /dev/null +++ b/marked/Rel-18/38_series/38876/f6e8acf9f931452d01688d311b5c0364_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8c4b959dc2a4373154bfe81565de0cac2f8d54c5b42fa6526dec7f01bbef0a7 +size 9129 diff --git a/marked/Rel-18/38_series/38876/fc3763c02020b3a260045bbadc1d36ba_img.jpg b/marked/Rel-18/38_series/38876/fc3763c02020b3a260045bbadc1d36ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd44668886e9238d9fa42e7dfaf7bdce3e574173 --- /dev/null +++ b/marked/Rel-18/38_series/38876/fc3763c02020b3a260045bbadc1d36ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41b6ada2f92452f95af9fe681deddc512b5e33d6c0f22768b6146301579610d6 +size 54814 diff --git a/marked/Rel-18/38_series/38876/fd8369b549b3d1a5c848cbd83659cae9_img.jpg b/marked/Rel-18/38_series/38876/fd8369b549b3d1a5c848cbd83659cae9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10543f53579bd9667d88ac800641f71921a54093 --- /dev/null +++ b/marked/Rel-18/38_series/38876/fd8369b549b3d1a5c848cbd83659cae9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3239d7cdb9a04badd9ce57acc1a84dce3463566432fdd25bfc53546f5ae4eff9 +size 53610 diff --git a/marked/Rel-18/38_series/38876/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-18/38_series/38876/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9700c0dc5071a3c0d73ef302929909c3cdaca4c9 --- /dev/null +++ b/marked/Rel-18/38_series/38876/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61f9caf9f5e0f64b547f6139fdcf4929087b07914c462b2e42b97ef34bdfc055 +size 13344 diff --git a/marked/Rel-18/38_series/38876/raw.md b/marked/Rel-18/38_series/38876/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5579edee2a6e9c4d8e8e50d4e8727cf8337df88a --- /dev/null +++ b/marked/Rel-18/38_series/38876/raw.md @@ -0,0 +1,4702 @@ + + +# 3GPP TR 38.876 V18.0.0 (2023-12) --- + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Air-to-ground network for NR (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a stylized '5G' with a green wave-like graphic 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. The 'G' has a red signal icon below it. 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. + +© 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..... | 8 | +| 2 References..... | 8 | +| 3 Definitions, symbols and abbreviations..... | 9 | +| 3.1 Definitions..... | 9 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 9 | +| 4 Background..... | 9 | +| 5 ATG bands ..... | 10 | +| 6 Co-existence study ..... | 10 | +| 6.1 Co-existence simulation scenario..... | 10 | +| 6.2 Co-existence simulation assumption..... | 11 | +| 6.2.1 Network layout model ..... | 11 | +| 6.2.1.1 Co-existence between ATG and NR terrestrial network ..... | 11 | +| 6.2.1.2 TN Network Layout..... | 13 | +| 6.2.1.3 ATG Network Layout..... | 13 | +| 6.2.1.4 Non-synchronized scenarios network layout..... | 14 | +| 6.2.2 System parameters..... | 17 | +| 6.2.2.1 ATG parameters..... | 17 | +| 6.2.2.2 ATG UE parameters ..... | 18 | +| 6.2.2.3 TN BS and UE parameters..... | 19 | +| 6.2.3 Antenna and beamforming pattern modelling..... | 19 | +| 6.2.3.1 ATG BS antenna model..... | 19 | +| 6.2.3.2 ATG UE antenna model ..... | 20 | +| 6.2.3.3 TN BS antenna model..... | 21 | +| 6.2.3.4 TN UE antenna model ..... | 22 | +| 6.2.4 ACLR and ACS modelling..... | 22 | +| 6.2.5 Propagation model..... | 23 | +| 6.2.5.1 Propagation model between TN UE and ATG UE..... | 23 | +| 6.2.5.2 Propagation model between TN BS and TN UE..... | 24 | +| 6.2.5.3 Propagation model between ATG BS and TN BS..... | 28 | +| 6.2.5.4 Propagation model between ATG BS and TN UE..... | 28 | +| 6.2.5.5 Propagation model between TN BS and ATG UE ..... | 28 | +| 6.2.5.6 Propagation model between ATG BS and ATG UE ..... | 28 | +| 6.2.6 Transmission power control model ..... | 28 | +| 6.2.6.1 TN UL TPC ..... | 28 | +| 6.2.6.2 TN DL TPC ..... | 29 | +| 6.2.6.3 ATG UL TPC..... | 29 | +| 6.2.6.4 ATG DL TPC..... | 29 | + +| | | | +|-----------|-------------------------------------------------------------|----| +| 6.2.7 | Received power model ..... | 29 | +| 6.2.8 | Performance metric ..... | 30 | +| 6.2.9 | Link level performance for NR ATG coexistence..... | 30 | +| 6.3 | Co-existence simulation methodology ..... | 31 | +| 6.4 | Co-existence simulation results..... | 32 | +| 6.4.1 | Synchronized Scenarios..... | 32 | +| 6.4.1.1 | Scenario 1: 4GHz ATG DL interfering TN DL ..... | 32 | +| 6.4.1.1.1 | Non-Subarray model ..... | 35 | +| 6.4.1.1.2 | Subarray model ..... | 37 | +| 6.4.1.2 | Scenario 2: 4GHz ATG UL interfering TN UL..... | 38 | +| 6.4.1.2.1 | Non-Subarray model ..... | 41 | +| 6.4.1.2.2 | Subarray model ..... | 44 | +| 6.4.1.3 | Scenario 3: 4GHz TN DL interfering ATG DL..... | 48 | +| 6.4.1.3.1 | Non-Subarray model ..... | 49 | +| 6.4.1.3.2 | Subarray model ..... | 51 | +| 6.4.1.4 | Scenario 4: 4GHz TN UL interfering ATG UL..... | 53 | +| 6.4.1.4.1 | Non-Subarray model ..... | 54 | +| 6.4.1.4.2 | Subarray model ..... | 55 | +| 6.4.1.5 | Scenario 9: 2GHz ATG DL interfering TN DL..... | 56 | +| 6.4.1.5.1 | Non-Subarray model ..... | 59 | +| 6.4.1.5.2 | Subarray model ..... | 61 | +| 6.4.1.6 | Scenario 10: 2GHz ATG UL interfering TN UL..... | 63 | +| 6.4.1.6.1 | Non-Subarray model ..... | 66 | +| 6.4.1.6.2 | Subarray model ..... | 70 | +| 6.4.1.7 | Scenario 11: 2GHz TN DL interfering ATG DL..... | 74 | +| 6.4.1.7.1 | Non-Subarray model ..... | 75 | +| 6.4.1.7.2 | Subarray model ..... | 77 | +| 6.4.1.8 | Scenario 12: 2GHz TN UL interfering ATG UL..... | 79 | +| 6.4.1.8.1 | Non-Subarray model ..... | 80 | +| 6.4.1.8.2 | Subarray model ..... | 81 | +| 6.4.2 | Non-synchronized Scenarios..... | 82 | +| 6.4.2.1 | Scenario 5: 4GHz ATG DL interfering TN UL..... | 82 | +| 6.4.2.1.1 | Using FSPL model ..... | 83 | +| 6.4.2.1.2 | Using RMa model in TR 38.901 with updating hUT as 30m ..... | 84 | +| 6.4.2.2 | Scenario 6: 4GHz TN UL interfering TN DL..... | 84 | +| 6.4.2.3 | Scenario 7: 4GHz TN DL interfering ATG UL..... | 84 | +| 6.4.2.3.1 | Using FSPL model ..... | 85 | +| 6.4.2.3.2 | Using RMa model in TR 38.901 with updating hUT as 30m ..... | 85 | +| 6.4.2.4 | Scenario 8: 4GHz TN UL interfering TN DL..... | 86 | +| 6.4.2.5 | Scenario 13: 4GHz TN UL interfering TN DL..... | 86 | +| 6.4.2.6 | Scenario 14: 2GHz TN DL interfering ATG UL..... | 86 | +| 6.4.2.6.1 | Using FSPL model ..... | 86 | +| 6.4.2.6.2 | Using RMa model in TR 38.901 with updating hUT as 30m ..... | 87 | +| 6.5 | Summary of co-existence study ..... | 87 | +| 6.5.1 | Synchronized Scenarios..... | 87 | + +| | | | +|----------|------------------------------------------------------------|-----| +| 6.5.2 | Non-Synchronized Scenarios ..... | 88 | +| 7 | RF requirements ..... | 89 | +| 7.1 | ATG UE specific ..... | 89 | +| 7.1.1 | ATG UE power class and requirement type ..... | 89 | +| 7.1.2 | Tx requirements ..... | 89 | +| 7.1.2.1 | Frequency error ..... | 89 | +| 7.1.2.2 | MOP requirements ..... | 90 | +| 7.1.2.3 | MPR/AMPR requirements ..... | 90 | +| 7.1.2.4 | Configured transmitted power ..... | 90 | +| 7.1.2.5 | Minimum output power ..... | 90 | +| 7.1.2.6 | Transmit OFF power ..... | 91 | +| 7.1.2.7 | Transmit ON/OFF time mask ..... | 91 | +| 7.1.2.8 | Power control ..... | 91 | +| 7.1.2.9 | Transmit signal quality ..... | 91 | +| 7.1.2.10 | Occupied bandwidth ..... | 92 | +| 7.1.2.11 | SEM requirements ..... | 92 | +| 7.1.2.12 | ACLR requirements ..... | 93 | +| 7.1.2.13 | Spurious emission ..... | 93 | +| 7.1.2.14 | Spurious emissions for UE co-existence ..... | 93 | +| 7.1.2.15 | Transmit intermodulation ..... | 93 | +| 7.1.3 | Rx requirements ..... | 93 | +| 7.1.3.1 | General ..... | 93 | +| 7.1.3.2 | Diversity characteristics ..... | 93 | +| 7.1.3.3 | REFSENS requirements ..... | 93 | +| 7.1.3.4 | Maximum input level ..... | 95 | +| 7.1.3.5 | Adjacent channel selectivity ..... | 95 | +| 7.1.3.6 | In-band blocking requirements ..... | 96 | +| 7.1.3.7 | Out-of-Band blocking requirements/ Spurious response ..... | 98 | +| 7.1.3.8 | Narrow band blocking requirements ..... | 98 | +| 7.1.3.9 | Intermodulation characteristics ..... | 98 | +| 7.1.3.10 | Receiver Spurious emissions ..... | 98 | +| 7.2 | ATG BS specific ..... | 98 | +| 7.2.1 | ATG BS class and BS type ..... | 98 | +| 7.2.2 | Tx requirements ..... | 99 | +| 7.2.2.1 | ATG Base station power ..... | 99 | +| 7.2.2.2 | Transmitted signal quality ..... | 99 | +| 7.2.2.3 | Unwanted emission requirements ..... | 100 | +| 7.2.2.4 | Transmitter spurious emissions ..... | 100 | +| 7.2.2.5 | Transmitter intermodulation ..... | 101 | +| 7.2.3 | Rx requirements ..... | 101 | +| 7.2.3.1 | Reference sensitivity level ..... | 101 | +| 7.2.3.2 | Dynamic range ..... | 101 | +| 7.2.3.3 | ACS ..... | 101 | +| 7.2.3.4 | In-band blocking ..... | 101 | +| 7.2.3.5 | Receiver intermodulation ..... | 101 | + +| | | | +|------------------------------------------------------------------------------------------------|------------------------------------------------------------------|------------| +| 7.2.3.6 | Out of band blocking ..... | 102 | +| 7.2.3.7 | In-channel selectivity ..... | 102 | +| 8 | RRM requirements ..... | 102 | +| 8.1 | General ..... | 102 | +| 9 | Conclusion ..... | 105 | +| 10 | Required changes to NR, E-UTRA, UTRA and MSR specifications..... | 106 | +| Annex A: Calibration results of synchronized operation ..... | | 106 | +| A.1 | Calibration assumptions ..... | 106 | +| A.2 | Calibration results at 2GHz and 4GHz..... | 106 | +| Annex B: Calibration results of non-synchronized operation ..... | | 107 | +| B.1 | Calibration assumptions ..... | 107 | +| B.2 | Calibration results at 2GHz and 4GHz..... | 107 | +| Annex C: Co-existence scenarios simulation data..... | | 107 | +| C.1 | Synchronized scenarios ..... | 107 | +| C.2 | Non-Synchronized scenarios ..... | 108 | +| Annex D: Supplementary simulation results for co-existence synchronized scenarios ..... | | 108 | +| D.1 | Synchronized scenarios ..... | 108 | +| D.1.1 | Impact of the number of TN BS columns ..... | 108 | +| D.1.2 | Impact of ATG UE antenna type ..... | 109 | +| D.1.3 | Impact of ATG-TN BS antennas collocation ..... | 109 | +| D.1.4 | Impact of ATG UE height distribution ..... | 110 | +| Annex E (informative): Change history ..... | | 112 | + +# --- 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 covers the RF, RRM and co-existence aspects of the work item “Air-to-ground network for NR” [2] + +The objectives for the study are the following: + +- Study and evaluate adjacent channel co-existence for ATG scenarios. +- Study and specify RF core requirements for ATG network and the ATG UE such that ATG deployment are well supported. +- Study and specify RRM requirement supporting ATG network deployment and ATG UE mobility + +# --- 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-230279, Air-to-ground network for NR, CMCC +- [3] ERC Recommendation 74-01: "Unwanted emissions in the spurious domain". +- [4] 3GPP TS 38.101-1: “NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone”. +- [5] 3GPP TS 38.104: “NR; Base Station (BS) radio transmission and reception”. +- [6] R4-2308745, Discussion on ATG UE RF Tx requirements, Ericsson +- [7] 3GPP TS 38.101-5: “NR; User Equipment (UE) radio transmission and reception; Part 5: Satellite access Radio Frequency (RF) and performance requirements”. +- [8] ITU-R M.2059-0: “Operational and technical characteristics and protection criteria of radio altimeters utilizing the band 4 200-4 400 MHz”. + +# 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]. + +**ATG UE:** a UE mounted on an aircraft + +**TAB connector:** *transceiver array boundary connector* + +**TRP (total radiated power):** the total power radiated by the antenna + +NOTE: The *total radiated power* is the power radiating in all direction for two orthogonal polarizations + +**RX beam peak direction:** direction where the maximum total component of RSRP and thus best total component of EIS is found + +**TX beam peak direction:** direction where the maximum total component of EIRP is found + +## 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]. + +| | | +|------|------------------------------------| +| AA | Antenna Array | +| ATG | Air To Ground | +| EIRP | Effective Isotropic Radiated Power | +| RDN | Radio Distribution Network | +| TAB | Transceiver Array Boundary | +| TN | Terrestrial Network | +| TRP | Total Radiated Power | + +# 4 Background + +Air-to-ground (ATG) network refers to in-flight connectivity technique, using ground-based cell towers that send signals up to an aircraft's antenna(s) of onboard ATG terminal. As a plane travels into different sections of airspace, the + +onboard ATG terminal automatically connects to the cell with strongest received signal power, just as a mobile phone does on the ground. In this network, a direct radio link will be established between BS on the ground and CPE type of UE mounted in the aircraft. + +From the trials and commercial operation [] of adapted LTE ATG solutions, some characteristics are considered for ATG network deployment scenarios. + +- **Extremely large inter-site distance (ISD) and large coverage range:** In order to control the network deployment cost and considering the limited number of flights, large ISD is preferred, e.g., about 100km to 200km. At the same time, when the plane is above the sea, the distance between the plane and the nearest base station could be more than 200km and even up to 300km. Therefore, ATG network should be able to provide up to 300km cell coverage range. +- **Utilizing non-disjoint frequency for deploying both ATG and terrestrial networks, i.e. same operating band but ATG network and TN use adjacent carriers:** Operators are interested to adopt the same frequency for deploying both ATG and terrestrial networks to save frequency resource cost, while interference between ATG and terrestrial networks becomes non-negligible and should be addressed. +- **Much powerful on-board ATG terminal capacity:** On-board ATG terminal can be much powerful than normal terrestrial UE, e.g., with higher EIRP via much larger transmission power and/or much larger on-board antenna gain. + +# 5 ATG bands + +ATG will operate within existing NR operating bands and does not need new bands. Depending on the operator's request so far, the following NR bands are intended for ATG deployment in Rel-18. Other new band request for ATG deployment is not precluded in future. + +**Table 5-1: ATG operating bands** + +| NR operating band | Uplink (UL) operating band
BS receive / UE transmit
$F_{UL\_low} - F_{UL\_high}$ | Downlink (DL) operating band
BS transmit / UE receive
$F_{DL\_low} - F_{DL\_high}$ | Duplex Mode | +|-------------------|----------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|-------------| +| n1 | 1920 MHz – 1980 MHz | 2110 MHz – 2170 MHz | FDD | +| n3 | 1710 MHz – 1785 MHz | 1805 MHz – 1880 MHz | FDD | +| n34 | 2010 MHz – 2025 MHz | 2010 MHz – 2025 MHz | TDD | +| n39 | 1880 MHz – 1920 MHz | 1880 MHz – 1920 MHz | TDD | +| n41 | 2496 MHz – 2690 MHz | 2496 MHz – 2690 MHz | TDD | +| n78 | 3300 MHz – 3800 MHz | 3300 MHz – 3800 MHz | TDD | +| n79 | 4400 MHz – 5000 MHz | 4400 MHz – 5000 MHz | TDD | + +# 6 Co-existence study + +## 6.1 Co-existence simulation scenario + +Table 6.1-1 summarizes the initial simulation scenarios for ATG coexistence study considering non co-location scenario as the baseline. Assume non-co-located for simulation cases 1, 4, 5, 6, 7, 8, 9, 12, 13, 14. For simulation cases 2, 3, 10, + +11, if evidence is brought forward that the ACLR/ACS requirements to cover co-location are substantially different to the requirements for the non-co-location, then discuss further how to cover both cases. + +**Table 6.1-1: Simulation scenarios for ATG coexistence study** + +| No. | Combination | Aggressor | | Victim | | Simulation frequency | Notes | Study Phase | +|-----|-------------|---------------------------|-----------------|---------------------------|-----------------|----------------------|--------|-------------| +| | | deployment scenario UL/DL | CBW duplex mode | deployment scenario UL/DL | CBW duplex mode | | | | +| 1 | TN with ATG | ATG DL | 100MHz TDD | TN rural DL | 100MHz /TDD | 4 GHz | | Phase 1 | +| 2 | TN with ATG | ATG UL | 100MHz TDD | TN rural UL | 100MHz TDD | 4 GHz | | Phase 1 | +| 3 | TN with ATG | TN rural DL | 100MHz TDD | ATG DL | 100MHz TDD | 4 GHz | | Phase 1 | +| 4 | TN with ATG | TN rural UL | 100MHz TDD | ATG UL | 100MHz TDD | 4 GHz | | Phase 1 | +| 5 | TN with ATG | ATG DL | 100MHz TDD | TN rural UL | 100MHz /TDD | 4 GHz | | Phase 2 | +| 6 | TN with ATG | ATG UL | 100MHz TDD | TN rural DL | 100MHz TDD | 4 GHz | | Phase 2 | +| 7 | TN with ATG | TN rural DL | 100MHz TDD | ATG UL | 100MHz TDD | 4 GHz | | Phase 2 | +| 8 | TN with ATG | TN rural UL | 100MHz TDD | ATG DL | 100MHz TDD | 4 GHz | | Phase 2 | +| 9 | TN with ATG | ATG DL | 20MHz FDD | TN rural DL | 20MHz FDD | 2 GHz | | Phase 1 | +| 10 | TN with ATG | ATG UL | 20MHz FDD | TN rural UL | 20MHz FDD | 2 GHz | | Phase 1 | +| 11 | TN with ATG | TN rural DL | 20MHz FDD | ATG DL | 20MHz FDD | 2 GHz | | Phase 1 | +| 12 | TN with ATG | TN rural UL | 20MHz FDD | ATG UL | 20MHz FDD | 2 GHz | | Phase 1 | +| 13 | TN with ATG | ATG UL | 20MHz FDD | TN rural DL | 20MHz TDD | 2 GHz | n1/n39 | Phase 2 | +| 14 | TN with ATG | TN rural DL | 20MHz FDD | ATG UL | 20MHz FDD | 2 GHz | n39/n1 | Phase 2 | + +NOTE 1: ACLR/ACS requirement for ATG BS and ATG UE are derived based on the synchronized scenario in Phase 1. + +NOTE 2: the non-synchronized coexistence scenarios listed in phase 2 are mainly used to identify the isolation distance between ATG BS and the the legacy TN BSs. And it's agreed to reuse 45dB ACLR and 46dB ACS for both TN and ATG BS for non-synchronized scenarios to derive isolated distance. + +NOTE 3: For scenario 11, if simulator doesn't support additional ring of TN network, i.e. additional 18 site and 54 cells, it's allowed to double the aggregate interference power from the 57 TN cells to simplify the platform modification, i.e. interference +3dB. + +NOTE 4: For scenario 6, 8 and 13 which is CLI between ATG UE and TN UE, it's not expected to have further coexistence simulation evaluation in Phase 2 due to low interference level. + +## 6.2 Co-existence simulation assumption + +### 6.2.1 Network layout model + +#### 6.2.1.1 Co-existence between ATG and NR terrestrial network + +Co-existence modelling is based on positioning a single ATG BS/sector and a TN cluster. Two options exist for the positioning of the TN cluster relative to the ATG BS. + +For simulation cases 1, 4, 5, 7, 8, 9, 12, 14 the worst-case network layout for simulation is one in which the TN cluster is placed at the same location as the ATG BS. The ATG BS are offset from the TN BS with $\frac{\sqrt{3}}{3} ISD_{TN}$ as depicted in figure 6.2.1.1-2. + +![Icon of an aircraft.](4d2624b1b2871a23382b647cd71e1c1c_img.jpg) + +Icon of an aircraft. + +![Diagram showing an ATG BS (aircraft) above a blue oval representing a TN network close to the ATG BS. The text inside the oval reads: 'TN network close to ATG BS (1/2 TN ISD offset)'.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +ATG BS + +TN network close to ATG BS (1/2 TN ISD offset) + +Diagram showing an ATG BS (aircraft) above a blue oval representing a TN network close to the ATG BS. The text inside the oval reads: 'TN network close to ATG BS (1/2 TN ISD offset)'. + +**Figure 6.2.1.1-1 Network layout with TN network located close to ATG BS** + +![Diagram of a hexagonal network grid. A central hexagon contains an ATG gNB (aircraft). Four other hexagons surrounding the central one each contain a base station icon. Dashed lines connect the central ATG gNB to these four surrounding base stations, illustrating the offset of the ATG BS compared to the TN BS grid.](853f59c89931a666c07903b31d098277_img.jpg) + +Diagram of a hexagonal network grid. A central hexagon contains an ATG gNB (aircraft). Four other hexagons surrounding the central one each contain a base station icon. Dashed lines connect the central ATG gNB to these four surrounding base stations, illustrating the offset of the ATG BS compared to the TN BS grid. + +**Figure 6.2.1.1-2 Offset of ATG BS compared to TN BS grid when the TN cluster is located close to the ATG BS** + +For the remaining simulation cases, if the ATG UE has an omni-directional radiation pattern then the worst-case network layout for simulation is one in which the TN is placed directly below the aircraft. If the UE has a directional radiation pattern, then in these cases companies should assess which of the network layout options (TN placed close to ATG BS or TN placed underneath the aircraft) is worst case and apply the worst-case option. + +![Diagram showing the network layout with a TN network located directly underneath the aircraft. On the left is an ATG BS (Air-to-Ground Base Station) icon. On the right is a blue oval representing the TN network directly underneath an aircraft icon.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +The diagram illustrates a network layout. On the left, there is an icon of a base station labeled 'ATG BS'. On the right, there is an icon of an aircraft with a blue oval underneath it containing the text 'TN network directly underneath aircraft'. + +Diagram showing the network layout with a TN network located directly underneath the aircraft. On the left is an ATG BS (Air-to-Ground Base Station) icon. On the right is a blue oval representing the TN network directly underneath an aircraft icon. + +**Figure 6.2.1.1-3 Network layout with TN network located directly underneath the aircraft** + +#### 6.2.1.2 TN Network Layout + +A rural hexagonal grid layout is assumed for TN network clusters with the parameters of table 6.2.1.2-1. + +**Table 6.2.1.2-1: Simulation scenarios for TN network layout** + +| Parameters | Values | +|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Network layout | For synchronized case:
For scenario 11: hexagonal grid, 37 macro sites, 3 sectors per site with wrap around
For other scenarios: hexagonal grid, 19 macro sites, 3 sectors per site with wrap around | +| | For non-synchronized case: no wrap around in TN | +| Inter-site distance | 3.5 km (4GHz)
7.5 km (2GHz) | +| BS antenna height | 30 m | +| UE location | Outdoor/indoor | +| | Indoor UE ratio | +| | LOS/NLOS | +| | UE antenna height | +| UE distribution (horizontal) | Uniform | +| Minimum BS - UE distance (2D) | 35 m | + +#### 6.2.1.3 ATG Network Layout + +A single ATG BS with a single cell is assumed for the ATG network. The aircraft are assumed to fly in a straight line from the minimum distance to the maximum horizontal distance from the ATG BS in the horizontal boresight of the ATG sector. The minimum and maximum horizontal distance of the ATG UE from the ATG BS are as depicted in table 6.2.1.3-1 and depend on the assumption of sub-arrays or not for the antenna model + +In the vertical domain, ATG UEs are distributed in height between 3000m and 10000m + +**Table 6.2.1.3-1: Simulation scenarios for ATG coexistence study** + +| Parameters | No sub-arrays | Sub-arrays | +|---------------------------------------|---------------|------------| +| Minimum ATG BS-UE horizontal distance | 20km | 50km | +| Maximum ATG BS-UE horizontal distance | 100km | 100km | + +![Figure 6.2.1.3-1: ATG BS layout (In horizontal boresight direction of ATG antenna).](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +The diagram shows a ground-based ATG BS (represented by a tower icon) on the left. A horizontal line represents the 'Horizon'. Two horizontal arrows indicate distance ranges from the BS: '20km or 50km minimum distance' and '100km maximum distance'. A vertical double-headed arrow on the right is labeled 'Height distribution'. + +Figure 6.2.1.3-1: ATG BS layout (In horizontal boresight direction of ATG antenna). + +**Figure 6.2.1.3-1 ATG BS layout (In horizontal boresight direction of ATG antenna)** + +For Scenarios 2, 3, 10, 11, in addition to simulations in the above assumptions some extra simulations were carried out in which the ATG UE is assumed to be around 300km from the ATG BS. The TN network is also located at 300km, and the ATG UE is assumed to be positioned within a straight line from the ATG BS and within the TN ground network area. + +For Scenario 2,3,10,11, it is agreed to conclude simulation results based on that ATG UEs flying over a TN cluster while ATG BS is 100km away as shown below. + +- Optional: ATG BS is 300km away. + +![Figure 6.2.1.3-2: ATG BS layout (Case 2,3, 10 and 11).](f6e8acf9f931452d01688d311b5c0364_img.jpg) + +The diagram shows a ground-based ATG BS on the left and a blue oval labeled 'TN network directly underneath aircraft' on the right. An aircraft icon is shown flying over the TN network. The ATG BS is labeled 'ATG BS'. + +Figure 6.2.1.3-2: ATG BS layout (Case 2,3, 10 and 11). + +**Figure 6.2.1.3-2: ATG BS layout (Case 2,3, 10 and 11)** + +#### 6.2.1.4 Non-synchronized scenarios network layout + +Case 1 - Angle between ATG BS boresight and nearest TN BS boresight in azimuth is 0 degree + +Figure 6.2.1.4-1 depicts the case when the angle between ATG BS boresight and nearest TN boresight in azimuth is 0 degree, also highlighted below – + +- The nearest TN BS sector points at the ATG BS in azimuth, with angle between the ATG BS boresight and nearest TN boresight as 0 degree (In Figure 6.2.1.4-1, highlighted through the orange dotted line) + +- ATG BS points at the ATG UE (In Figure 6.2.1.4-1, highlighted through the orange dotted line). +- ATG BS, ATG UE and TN cluster center are in a straight line. +- Isolation distance is the between the ATG BS and nearest TN BS. +- ATG UE is dropped between the maximum and minimum distance assumption depending on the ATG/ TN BS antenna configuration. + +![Diagram illustrating the angle between ATG BS boresight and nearest TN BS boresight in azimuth is 0 degree.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +The diagram shows a top-down view of a network. On the left, an airplane labeled 'ATG UE' is shown. In the center, a 'TN cluster' is represented by a hexagonal grid of small radio icons. On the right, a larger radio icon labeled 'ATG BS' is shown. A horizontal dashed line passes through the center of the ATG UE, the center of the TN cluster, and the ATG BS. An orange dotted line points from the ATG BS towards the ATG UE. A text label above the ATG BS states: 'Angle between ATG BS boresight and nearest TN boresight in azimuth is 0 degree'. A double-headed arrow between the ATG BS and the nearest TN BS is labeled 'Isolation distance between ATG BS and nearest TN BS'. A long double-headed arrow at the bottom, spanning from the ATG UE to the ATG BS, is labeled 'Between maximum and minimum distance assumption of ATG UE and ATG BS'. + +Diagram illustrating the angle between ATG BS boresight and nearest TN BS boresight in azimuth is 0 degree. + +**Figure 6.2.1.4-1: Angle between ATG BS boresight and nearest TN BS boresight in azimuth is 0 degree** + +Case 2 - Angle between ATG BS boresight and nearest TN BS boresight in azimuth is 30 degrees + +Figure 6.2.1.4-2 depicts the case when the angle between ATG BS boresight and nearest TN boresight in azimuth is 30 degrees, also highlighted below – + +- The nearest TN BS sector points at the ATG BS in azimuth, with angle between the ATG BS boresight and nearest TN boresight as 30 degrees (In Figure 6.2.1.4-2, highlighted through the orange dotted line) +- ATG BS points at the ATG UE ((In Figure 6.2.1.4-2, highlighted through the orange dotted line) +- Isolation distance is the between the ATG BS and nearest TN BS. +- ATG UE is dropped between the maximum and minimum distance assumption depending on the ATG/ TN BS antenna configuration. + +![Diagram illustrating the angle between ATG BS boresight and nearest TN BS boresight in azimuth is 30 degrees.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +The diagram shows a top view of a network cluster. On the left, an airplane labeled 'ATG UE' is shown. On the right, a base station labeled 'ATG BS' is shown. In the center, there is a 'Top view: TN cluster' represented by a grid of hexagons, each containing a small antenna icon. An orange dotted line connects the ATG BS to the ATG UE. Another orange dotted line connects the ATG BS to the nearest TN BS. The angle between these two lines at the ATG BS is labeled '30 degrees'. A horizontal double-headed arrow at the bottom indicates the 'Between maximum and minimum distance assumption of ATG UE and ATG BS'. A label 'Isolation distance between ATG BS and nearest TN BS' points to the distance between the ATG BS and the nearest TN BS. + +Diagram illustrating the angle between ATG BS boresight and nearest TN BS boresight in azimuth is 30 degrees. + +**Figure 6.2.1.4-2: Angle between ATG BS boresight and nearest TN BS boresight in azimuth is 30 degrees** + +Case 3 - Angle between ATG BS boresight and nearest TN BS boresight in azimuth is 60 degrees + +Figure 6.2.1.4-3 depicts the case when the angle between ATG BS boresight and nearest TN boresight in azimuth is 60 degrees, also highlighted below – + +- The nearest TN BS sector points at the ATG BS in azimuth, with angle between the ATG BS boresight and nearest TN boresight as 60 degrees ((In Figure 6.2.1.4-3, highlighted through the orange dotted line) +- ATG BS points at the ATG UE (In Figure 6.2.1.4-3, highlighted through the orange dotted line) +- Isolation distance is the between the ATG BS and nearest TN BS. +- ATG UE is dropped between the maximum and minimum distance assumption depending on the ATG/ TN BS antenna configuration. + +![Diagram showing the angle between ATG BS boresight and nearest TN BS boresight in azimuth is 60 degrees. It includes a top view of a TN cluster, an ATG UE (airplane), and an ATG BS with various distance and angle annotations.](8307f6b04df072c9332f9987e034272c_img.jpg) + +The diagram illustrates a network configuration for co-existence. On the left, a 'Top view: TN cluster' is shown as a hexagonal grid of six base stations (TN BS). On the right, an 'ATG BS' is depicted with an orange boresight arrow. The angle between this boresight and the boresight of the nearest TN BS is labeled as '60 degrees'. A dashed line connects an 'ATG UE' (represented by an airplane icon) to the ATG BS. A horizontal double-headed arrow at the bottom indicates the 'Between maximum and minimum distance assumption of ATG UE and ATG BS'. A vertical double-headed arrow between the ATG BS and the TN cluster is labeled 'Isolation distance between ATG BS and nearest TN BS'. + +Diagram showing the angle between ATG BS boresight and nearest TN BS boresight in azimuth is 60 degrees. It includes a top view of a TN cluster, an ATG UE (airplane), and an ATG BS with various distance and angle annotations. + +Figure 6.2.1.4-3: Angle between ATG BS boresight and nearest TN BS boresight in azimuth is 60 degrees + +### 6.2.2 System parameters + +#### 6.2.2.1 ATG parameters + +The system parameters for ATG BS for co-existence study are assumed as below. + +**Table 6.2.2.1-1: system parameters for ATG BS** + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ATG BS altitude | 30m | +| Carrier frequency | 2GHz, 4GHz | +| Frequency reuse factor | 1 | +| Duplex mode | FDD@2GHz, TDD@4GHz | +| Channel bandwidth | 20MHz@2GHz, 100MHz@4GHz | +| Subcarrier spacing (SCS) | 15k@2GHz, 30k@4GHz | +| Number of cells | one cell | +| UE distribution | Single ATG UE per ATG cell
Horizontal: Random between minimum and maximum distance in the straight line within range described in section 6.2.1.3
Vertical: Based on ATG UE uniform distribution among 3 to 10km | +| Indoor UE percentage | 0% | +| Number of DL active UEs per cell (NOTE 2) | one UE | +| Number of UL active UEs per cell (NOTE 2) | one UE | +| DL scheduled bandwidth per UE | Full bandwidth | +| UL scheduled bandwidth per UE | Full bandwidth | +| UL target SNR (NOTE 3) | 15dB | +| Traffic model | Full buffer | +| ATG BS maximum output power | 46dBm sum of two polarizations for 2GHz
53dBm sum of two polarizations for 4GHz | +| ATG BS noise figure | 5dB | +| Handover margin | Not needed | +| NOTE 1: ATG BS is assumed to serve UEs in the rural environment.
NOTE 2: Same as the number of BS beam(s).
NOTE 3: Target SNR for simulation is based on CL values and only compensates pathloss in the simulation assumptions. | | + +#### 6.2.2.2 ATG UE parameters + +The system parameters for ATG UE are assumed as below. + +**Table 6.2.2.2-1: system parameters for ATG UE** + +| | | +|----------------------------|--------------------------------------------| +| ATG UE altitude | Vertical: Distributed between 3km and 10km | +| Carrier frequency | 2GHz, 4GHz | +| ATG UE max TX power in dBm | 40dBm TRP for 2GHz
43dBm EIRP for 4GHz | +| ATG UE min TX power in dBm | -33dBm for 100MHz
-40dBm for 20MHz | +| ATG UE noise figure | 9dB | + +#### 6.2.2.3 TN BS and UE parameters + +The system parameters for TN BS and TN UE are assumed as below. + +**Table 6.2.2.3-1: system parameters for TN BS and UE** + +| Parameters | Rural | Rural | +|-----------------------------------------|-------------|-------------| +| Carrier frequency | 2GHz | 4GHz | +| Channel bandwidth | 20MHz | 100MHz | +| Scheduled channel bandwidth per UE (DL) | 1 | 1 | +| Scheduled channel bandwidth per UE (UL) | 1 | 1 | +| The number of active UE (DL) (NOTE 1) | 1 | 1 | +| The number of active UE (UL) (NOTE 1) | 1 | 1 | +| Traffic model | full buffer | full buffer | +| DL power control | No | No | +| UL power control | Yes | Yes | +| UL target SNR (NOTE 3) | 15dB | 15dB | +| TN BS-UE min distance in meters | 35m | 35m | +| TN BS max TX power in dBm (NOTE 2) | 46dBm | 53dBm | +| TN UE max TX power in dBm | 23dBm | 23dBm | +| TN UE min TX power in dBm | -40dBm | -40dBm | +| TN BS Noise figure in dB | 5dB | 5dB | +| TN UE Noise figure in dB | 9dB | 9dB | +| Handover margin | 3dB | 3dB | + +NOTE 1: Same as the number of BS beam(s). +NOTE 2: TN BS max TX power is defined as the sum over both polarizations. +NOTE 3: Target SNR for simulation is based on CL values and only compensates pathloss in the simulation assumptions. + +### 6.2.3 Antenna and beamforming pattern modelling + +#### 6.2.3.1 ATG BS antenna model + +For ATG BS antenna modelling, the following two options for antenna modelling could be used for ATG coexistence study. + +##### Option 1: non sub-array model + +**Table 6.2.3.1-1: AAS antenna parameters for non sub-array model** + +| | ATG | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------| +| Base Station Antenna Characteristics | | +| Antenna pattern | TR 38.921 | +| Element gain (dBi) | 7.1 | +| Horizontal/vertical 3 dB beam width of single element (degree) | 90° for H
54° for V | +| Horizontal/vertical front-to-back ratio (dB) | 30 for both H/V | +| Antenna polarization | Linear $\pm 45^\circ$ | +| Antenna array configuration (Row $\times$ Column) | 8 $\times$ 8 elements | +| Number of supported polarizations, $P$ | 2 | +| Horizontal/Vertical radiating element spacing | 0.5 of wavelength for H, 0.9 of wavelength for V | +| Array Ohmic loss (dB) | 2 | +| Conducted power (before Ohmic loss) per antenna element (dBm) (Note 1) | 25 for 2GHz
32 for 4GHz | +| Base station maximum coverage angle in the horizontal plane (degrees) | 120 | +| Base station vertical coverage range (degrees) (Note 2) | 25 | +| Mechanical uptilt (degrees) | 14 | +| Note 1: The conducted power per element assumes 8x8x2 elements (i.e. power per H/V polarized element).
Note 2: The vertical coverage range includes the mechanical downtilt. | | + +##### **Option 2: sub-array model** + +**Table 6.2.3.1-2: AAS antenna parameters for sub-array model** + +| Parameter | Macro urban | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------| +| Element gain (dBi) | 6.4 | +| Horizontal/vertical 3 dB beam width of single element (degree) | 90° for H
65° for V | +| Horizontal/vertical front-to-back ratio (dB) | 30 for both H/V | +| Antenna polarization | Linear $\pm 45^\circ$ | +| Antenna sub-array configuration (Row $\times$ Column) | 4 $\times$ 8 elements | +| Horizontal/Vertical radiating sub-array spacing | 0.5 of wavelength for H, 2.1 of wavelength for V | +| Number of element rows in sub-array | 3 | +| Vertical element separation in sub-array ( $d_{v,sub}$ ) | 0.7 of wavelength of V | +| Array Ohmic loss (dB) | 2 | +| Conducted power (before Ohmic loss) per sub-array (dBm) (Note 1) | 28 for 2GHz
35 for 4GHz | +| Base station horizontal coverage range (degrees) | +/-60 | +| Base station vertical coverage range (degrees) (Note 2) | 10 | +| Mechanical up-tilt (degrees) | 6.5 | +| Note 1: The conducted power per sub-array assumes 4x8x2 sub-arrays (i.e. power per H/V polarized sub-array).
Note 2: The vertical coverage range includes the mechanical downtilt. | | + +#### **6.2.3.2 ATG UE antenna model** + +For 2GHz, assume omni-directional antenna, assume 40dBm UE output power for calibration (as worst case for simulation purposes). + +For 4GHz, assume that UE is equipped with directional antenna, assume a UE EIRP of 43dBm for calibration (as worst case for simulation purposes) + +- Use following as the starting point for calibration. + +**Table 6.2.3.2-1: antenna parameters for antenna array** + +| | | +|-------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Horizontal/vertical 3 dB beam width of single element (degree) | 90° for H
90° for V | +| Element gain (dBi) | 5 dBi | +| Horizontal/vertical front-to-back ratio (dB) | 30dBc | +| Antenna polarization | Linear $\pm 90^\circ$ | +| Antenna array configuration (Row $\times$ Column $\times$ Polarization) | (8x2x2) or
(16x1x2) | +| Horizontal/Vertical radiating element spacing | 0.5 of wavelength for H, 0.5 of wavelength for V | +| UE antenna orientation | Single UE panel deployed on the abdomen of the airplane facing downwards and with the longest dimension of the array aligned with the direction of the flight route. The flight route is pointed at the BS. | + +#### 6.2.3.3 TN BS antenna model + +For TN BS antenna modelling, the following two options for antenna modelling could be used for ATG coexistence study. + +##### Option 1: non sub-array model + +**Table 6.2.3.3-1: Antenna parameters for non sub-array model** + +| | TN | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------| +| Base Station Antenna Characteristics | | +| Antenna pattern | TR 38.921 | +| Element gain (dBi) | 7.1 | +| Horizontal/vertical 3 dB beam width of single element (degree) | 90° for H
54° for V | +| Horizontal/vertical front-to-back ratio (dB) | 30 for both H/V | +| Antenna polarization | Linear $\pm 45^\circ$ | +| Antenna array configuration (Row $\times$ Column) | 8 $\times$ 8 elements AAS
Optional: 8 $\times$ 1 elements non AAS | +| Number of supported polarizations, $P$ | 2 | +| Horizontal/Vertical radiating element spacing | 0.5 of wavelength for H, 0.9 of wavelength for V | +| Array Ohmic loss (dB) | 2 | +| Conducted power (before Ohmic loss) per antenna element (dBm) (Note 1) | 25 for 2GHz
32 for 4GHz | +| Base station maximum coverage angle in the horizontal plane (degrees) | 120 | +| Base station vertical coverage range (degrees) (Note 2) | 25 | +| Mechanical down (degrees) | 3 | +| Note 1: The conducted power per element assumes 8x8x2 elements (i.e. power per H/V polarized element).
Note 2: The vertical coverage range includes the mechanical downtilt. | | + +##### Option 2: sub-array model + +**Table 6.2.3.3-2: Antenna parameters for sub-array model** + +| Parameter | Macro urban | +|-----------------------------------------------------------------------------|-------------------------------------------------------------| +| Element gain (dBi) | 6.4 | +| Horizontal/vertical 3 dB beam width of single element (degree) | 90° for H
65° for V | +| Horizontal/vertical front-to-back ratio (dB) | 30 for both H/V | +| Antenna polarization | Linear $\pm 45^\circ$ | +| Antenna sub-array configuration (Row $\times$ Column) | 4 $\times$ 8 elements AAS
Optional: 4x1 elements non-AAS | +| Horizontal/Vertical radiating sub-array spacing | 0.5 of wavelength for H, 2.1 of wavelength for V | +| Number of element rows in sub-array | 3 | +| Vertical element separation in sub-array ( $d_{v,sub}$ ) | 0.7 of wavelength of V | +| Array Ohmic loss (dB) | 2 | +| Conducted power (before Ohmic loss) per sub-array (dBm) (Note 1) | 28 for 2GHz
35 for 4GHz | +| Base station horizontal coverage range (degrees) | +/-60 | +| Base station vertical coverage range (degrees) (Note 2) | 10 | +| Mechanical downtilt (degrees) | 3 | + +Note 1: The conducted power per sub-array assumes 4x8x2 sub-arrays (i.e. power per H/V polarized sub-array). +Note 2: The vertical coverage range includes the mechanical downtilt. + +#### 6.2.3.4 TN UE antenna model + +The following assumption for TN UE antenna is shown as below. + +**Table 6.2.3.4-1: TN handheld UE antenna characteristic** + +| Characteristics | Handheld | +|--------------------------------|------------------------------------| +| Antenna type and configuration | 1 omni-directional antenna element | +| Polarisation | no | +| Tx/Rx Antenna gain | 0 dBi per element | +| the number of Tx and Rx | 1T2R | + +### 6.2.4 ACLR and ACS modelling + +For DL it seems reasonable from the perspective of simulating worst case scenarios that we assume BS ACLR is modelled as flat in space, and the UE ACS can be modelled flat in space. + +If this assumption is for DL, then the similar assumption could be made for the UL. + +Therefore, it is assumed that both ACLR ( or the adjacent channel interference) and ACS are flat in both space and frequency. The ACIR model can be express as: + +$$ACIR = \frac{1}{\frac{1}{ACLR} + \frac{1}{ACS}}$$ + +(Assuming ACLR, ACS and ACIR to be linear). + +The ACLR/ACS requirements for TN are defined as below. + +**Table 6.2.4-1: ACLR/ACS requirements for TN** + +| NR TN system | | | +|--------------|------|--------------| +| BS | ACLR | 45 dB | +| | ACS | 46 dB | +| UE | ACLR | 30dB (ACLR1) | +| | | 43dB (ACLR2) | +| | ACS | 33 | + +### 6.2.5 Propagation model + +#### 6.2.5.1 Propagation model between TN UE and ATG UE + +Referring to section 6.6 in TR 38.811, the propagation model between TN UE and ATG UE can be simplified and summarized as below. + +##### LOS probability + +Line-Of-Sight (LOS) probability depends on UE environment and elevation angle, and is obtained from Table 6.2.5.1-1. Reference elevation angles are considered from 10° to 90° with a 10° step. For an ATG UE-to-ATG BS, the LOS probability is taken from the nearest reference elevation angle. + +**Table 6.2.5.1-1 LOS probability** + +| Elevation | Suburban and Rural scenarios | +|-----------|------------------------------| +| 10° | 78.2% | +| 20° | 86.9% | +| 30° | 91.9% | +| 40° | 92.9% | +| 50° | 93.5% | +| 60° | 94.0% | +| 70° | 94.9% | +| 80° | 95.2% | +| 90° | 99.8% | + +##### Path loss and Shadow fading + +The signal path between ATG UE and ATG BS undergoes several stages of propagation and attenuation. The path loss (PL) is composed of components as follows: + +$$PL = PL_b = FSPL(d, f_c) + SF + CL(\alpha, f_c), \quad (6.2.5.1-1)$$ + +where $PL$ is the total path loss in dB, + +$PL_b$ is the basic path loss in dB, + +This section specifies the basic path loss model ( $PL_b$ ) which accounts for the signal's free space propagation, clutter loss, and shadow fading. + +The free space path loss (FSPL) in dB for a separation distance $d$ (between ATG UE and ATG BS) in meter and frequency $f_c$ in GHz is given by + +$$FSPL(d, f_c) = 32.45 + 20 \log_{10}(f_c) + 20 \log_{10}(d) \quad (6.6-2)$$ + +$CL(\alpha, f_c)$ is clutter loss, and $SF$ is shadow fading loss represented by a random number generated by the normal distribution, i.e., $SF \sim N(0, \sigma_{SF}^2)$ . When the UE is in LOS condition, clutter loss is negligible and should be set to 0 dB in the basic path loss model. + +**Table 6.2.5.1-2: Shadow fading and clutter loss for suburban and rural scenarios** + +| Elevation | 2GHz 3.5GHz | | | +|-----------|--------------------|--------------------|-----------| +| | LOS | NLOS | | +| | $\sigma_{SF}$ (dB) | $\sigma_{SF}$ (dB) | $CL$ (dB) | +| 10° | 1.79 | 8.93 | 19.52 | +| 20° | 1.14 | 9.08 | 18.17 | +| 30° | 1.14 | 8.78 | 18.42 | +| 40° | 0.92 | 10.25 | 18.28 | +| 50° | 1.42 | 10.56 | 18.63 | +| 60° | 1.56 | 10.74 | 17.68 | +| 70° | 0.85 | 10.17 | 16.50 | +| 80° | 0.72 | 11.52 | 16.30 | +| 90° | 0.72 | 11.52 | 16.30 | + +#### 6.2.5.2 Propagation model between TN BS and TN UE + +Referring to section 7.4 in TR 38.901, the propagation model between TN BS and TN UE can be summarized as below, which is same as RMa scenario. It's noted we assume all TN UE are outdoor, therefore there is no indoor distance and no O2I building penetration loss in simulation. + +##### Pathloss: + +The pathloss models are summarized in Table 6.2.5.2-1 and the distance definitions are indicated in Figure 6.2.5.2-1 and Figure 6.2.5.2-2. Note that the distribution of the shadow fading is log-normal, and its standard deviation for each scenario is given in Table 6.2.5.2-1. + +![Figure 6.2.5.2-1: Definition of d2D and d3D for outdoor UTs. A diagram showing a base station (BS) of height h_BS and an user terminal (UT) of height h_UT. The horizontal distance between them is d_2D, and the 3D distance is d_3D.](26d664119ad25250780f554633444e54_img.jpg) + +Figure 6.2.5.2-1: Definition of d2D and d3D for outdoor UTs. A diagram showing a base station (BS) of height h\_BS and an user terminal (UT) of height h\_UT. The horizontal distance between them is d\_2D, and the 3D distance is d\_3D. + +Figure 6.2.5.2-1: Definition of $d_{2D}$ and $d_{3D}$ for outdoor UTs + +![Figure 6.2.5.2-2: Definition of d2D-out, d2D-in and d3D-out, d3D-in for indoor UTs. A diagram showing a BS of height h_BS outside a building. The UT is inside the building at height h_UT. The distance from the BS to the building entrance is d_2D-out, and from the entrance to the UT is d_2D-in. The 3D distances are labeled d_3D-out and d_3D-in.](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +Figure 6.2.5.2-2: Definition of d2D-out, d2D-in and d3D-out, d3D-in for indoor UTs. A diagram showing a BS of height h\_BS outside a building. The UT is inside the building at height h\_UT. The distance from the BS to the building entrance is d\_2D-out, and from the entrance to the UT is d\_2D-in. The 3D distances are labeled d\_3D-out and d\_3D-in. + +Figure 6.2.5.2-2: Definition of $d_{2D-out}$ , $d_{2D-in}$ and $d_{3D-out}$ , $d_{3D-in}$ for indoor UTs. + +Note that + +$$d_{3D-out} + d_{3D-in} = \sqrt{(d_{2D-out} + d_{2D-in})^2 + (h_{BS} - h_{UT})^2} \quad (7.4-1)$$ + +Table 6.2.5.2-1: Pathloss models + +| Scenario | LOS/NLOS | Pathloss [dB], $f_c$ is in GHz and $d$ is in meters, see note 6 | Shadow fading std [dB] | Applicability range, antenna height default values | +|----------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | | +| RMa | LOS | $PL_{RMa-LOS} = \begin{cases} PL_1 & 10\text{m} \leq d_{2D} \leq d_{BP} \\ PL_2 & d_{BP} \leq d_{2D} \leq 10\text{km} \end{cases}, \text{ see note 5}$ $PL_1 = 20 \log_{10}(40\pi d_{3D} f_c / 3) + \min(0.03h^{1.72}, 10) \log_{10}(d_{3D}) - \min(0.044h^{1.72}, 14.77) + 0.002 \log_{10}(h) d_{3D}$ $PL_2 = PL_1(d_{BP}) + 40 \log_{10}(d_{3D} / d_{BP})$ | $\sigma_{SF} = 4$

$\sigma_{SF} = 6$ | $h_{BS} = 35\text{m}$
$h_{UT} = 1.5\text{m}$
$W = 20\text{m}$
$h = 5\text{m}$
$h = \text{avg. building height}$
$W = \text{avg. street width}$
The applicability ranges:
$5\text{m} \leq h \leq 50\text{m}$
$5\text{m} \leq W \leq 50\text{m}$
$10\text{m} \leq h_{BS} \leq 150\text{m}$
$1\text{m} \leq h_{UT} \leq 10\text{m}$ | +| | NLOS | $PL_{RMa-NLOS} = \max(PL_{RMa-LOS}, PL'_{RMa-NLOS})$ for $10\text{m} \leq d_{2D} \leq 5\text{km}$
$PL'_{RMa-NLOS} = 161.04 - 7.1 \log_{10}(W) + 7.5 \log_{10}(h) - (24.37 - 3.7(h/h_{BS})^2) \log_{10}(h_{BS}) + (43.42 - 3.1 \log_{10}(h_{BS}))(\log_{10}(d_{3D}) - 3) + 20 \log_{10}(f_c) - (3.2(\log_{10}(11.75h_{UT}))^2 - 4.97)$ | $\sigma_{SF} = 8$ | | + +| Scenario | LOS/NLOS | Pathloss [dB], $f_c$ is in GHz and $d$ is in meters, see note 6 | Shadow fading std [dB] | Applicability range, antenna height default values | +|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|------------------------|----------------------------------------------------| +| Note 1: |

Breakpoint distance d_{BP} = 4 h'_{BS} h'_{UT} f_c/c, where f_c is the centre frequency in Hz, c = 3.0 \times 10^8 m/s is the propagation velocity in free space, and h'_{BS} and h'_{UT} are the effective antenna heights at the BS and the UT, respectively. The effective antenna heights h'_{BS} and h'_{UT} are computed as follows: h'_{BS} = h_{BS} - h_E, h'_{UT} = h_{UT} - h_E, where h_{BS} and h_{UT} are the actual antenna heights, and h_E is the effective environment height. For UMi h_E = 1.0m. For UMa h_E=1m with a probability equal to 1/(1+C(d_{2D}, h_{UT})) and chosen from a discrete uniform distribution uniform(12,15,...,(h_{UT}-1.5)) otherwise. With C(d_{2D}, h_{UT}) given by

$C(d_{2D}, h_{UT}) = \begin{cases} 0 & , h_{UT} < 13\text{m} \\ \left(\frac{h_{UT} - 13}{10}\right)^{1.5} g(d_{2D}) & , 13\text{m} \leq h_{UT} \leq 23\text{m} \end{cases}$

where

$g(d_{2D}) = \begin{cases} 0 & , d_{2D} \leq 18\text{m} \\ \frac{5}{4} \left(\frac{d_{2D}}{100}\right)^3 \exp\left(\frac{-d_{2D}}{150}\right) & , 18\text{m} < d_{2D} \end{cases}$

Note that h_E depends on d_{2D} and h_{UT} and thus needs to be independently determined for every link between BS sites and UTs. A BS site may be a single BS or multiple co-located BSs.

Note 2: The applicable frequency range of the PL formula in this table is 0.5 < f_c < f_H GHz, where f_H = 30 GHz for RMa and f_H = 100 GHz for all the other scenarios. It is noted that RMa pathloss model for >7 GHz is validated based on a single measurement campaign conducted at 24 GHz.

Note 3: UMa NLOS pathloss is from TR36.873 with simplified format and PL_{UMa-LOS} = Pathloss of UMa LOS outdoor scenario.

Note 4: PL_{UMi-LOS} = Pathloss of UMi-Street Canyon LOS outdoor scenario.

Note 5: Break point distance d_{BP} = 2\pi h_{BS} h_{UT} f_c/c, where f_c is the centre frequency in Hz, c = 3.0 \times 10^8 m/s is the propagation velocity in free space, and h_{BS} and h_{UT} are the antenna heights at the BS and the UT, respectively.

Note 6: f_c denotes the center frequency normalized by 1GHz, all distance related values are normalized by 1m, unless it is stated otherwise.

| | | | + +##### **LOS probability** + +The Line-Of-Sight (LOS) probabilities are given in Table 6.2.5.2-2. + +**Table 6.2.5.2-2 LOS probability** + +| Scenario | LOS probability (distance is in meters) | +|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| RMa | $Pr_{LOS} = \begin{cases} 1 & , d_{2D-out} \leq 10\text{m} \\ \exp\left(-\frac{d_{2D-out} - 10}{1000}\right) & , 10\text{m} < d_{2D-out} \end{cases}$ | + +##### **O2I building penetration loss** + +The pathloss incorporating O2I building penetration loss is modelled as in the following: + +$$PL = PL_b + PL_{tw} + PL_{in} + N(0, \sigma_P^2) \quad (6.2.5.2-2)$$ + +where $PL_b$ is the basic outdoor path loss given in Clause 6.2.5.2, where $d_{3D}$ is replaced by $d_{3D-out} + d_{3D-in} \cdot PL_{tw}$ is the building penetration loss through the external wall, $PL_{in}$ is the inside loss dependent on the depth into the building, and $\sigma_p$ is the standard deviation for the penetration loss. + +$PL_{tw}$ is characterized as: + +$$PL_{tw} = PL_{npi} - 10 \log_{10} \sum_{i=1}^N \left( p_i \times 10^{\frac{L_{material\_i}}{-10}} \right) \quad (6.2.5.2-3)$$ + +$PL_{npi}$ is an additional loss is added to the external wall loss to account for non-perpendicular incidence; + +$L_{material\_i} = a_{material\_i} + b_{material\_i} \cdot f$ , is the penetration loss of material $i$ , example values of which can be found in + +Table 7.4.3-1; $p_i$ is proportion of $i$ -th materials, where $\sum_{i=1}^N p_i = 1$ ; and $N$ is the number of materials. + +**Table 6.2.5.2-3: Material penetration losses** + +| Material | Penetration loss [dB] | +|---------------------------|----------------------------| +| Standard multi-pane glass | $L_{glass} = 2 + 0.2f$ | +| IRR glass | $L_{IRRglass} = 23 + 0.3f$ | +| Concrete | $L_{concrete} = 5 + 4f$ | +| Wood | $L_{wood} = 4.85 + 0.12f$ | +| Note: | f is in GHz | + +Table 6.2.5.2-4 gives $PL_{tw}$ , $PL_{in}$ and $\sigma_p$ for two O2I penetration loss models. The O2I penetration is UT-specifically generated, and is added to the SF realization in the log domain. + +**Table 6.2.5.2-4: O2I building penetration loss model** + +| | Path loss through external wall:
$PL_{tw}$ in [dB] | Indoor loss:
$PL_{in}$ in [dB] | Standard deviation:
$\sigma_p$ in [dB] | +|------------------------|---------------------------------------------------------------------------------------------------------------------|-----------------------------------|-------------------------------------------| +| Low-loss model | $5 - 10 \log_{10} \left( 0.3 \cdot 10^{\frac{-L_{glass}}{10}} + 0.7 \cdot 10^{\frac{-L_{concrete}}{10}} \right)$ | $0.5 d_{2D-in}$ | 4.4 | +| High-loss model | $5 - 10 \log_{10} \left( 0.7 \cdot 10^{\frac{-L_{IRRglass}}{10}} + 0.3 \cdot 10^{\frac{-L_{concrete}}{10}} \right)$ | $0.5 d_{2D-in}$ | 6.5 | + +$d_{2D-in}$ is minimum of two independently generated uniformly distributed variables between 0 and 25 m for UMa and UMi-Street Canyon, and between 0 and 10 m for RMa. $d_{2D-in}$ shall be UT-specifically generated. + +Both low-loss and high-loss models are applicable to UMa and UMi-Street Canyon. + +Only the low-loss model is applicable to RMa. + +#### 6.2.5.3 Propagation model between ATG BS and TN BS + +The propagation model between ATG BS and TN BS is same as the LOS propagation model between TN UE and ATG UE in clause 6.2.5.1 (shadow fading and clutter loss are assumed to be zero, since the ATG BS and TN BS are at 30m above the clutter). + +#### 6.2.5.4 Propagation model between ATG BS and TN UE + +The propagation model between ATG BS and TN UE is same as the propagation model between TN BS and TN UE in clause 6.2.5.2 + +#### 6.2.5.5 Propagation model between TN BS and ATG UE + +The propagation model between TN BS and ATG UE is same as the LOS propagation model between TN UE and ATG UE in clause 6.2.5.1 (shadow fading and clutter loss are assumed to be zero, since the ATG BS and TN BS are at 30m and above the clutter). + +#### 6.2.5.6 Propagation model between ATG BS and ATG UE + +The propagation model between ATG BS and ATG UE is same as the LOS propagation model between TN UE and ATG UE in clause 6.2.5.1 (shadow fading and clutter loss are assumed to be zero, since the ATG BS and TN BS are at 30m and above the clutter). + +### 6.2.6 Transmission power control model + +#### 6.2.6.1 TN UL TPC + +For uplink scenario, TPC model specified in Section 9.1 TR 36.942 is applied for TN with following parameters. + +$$P_t = P_{\max} \times \min \left\{ 1, \max \left[ R_{\min}, \left( \frac{CL}{CL_{x-ile}} \right)^\gamma \right] \right\}$$ + +where: + +- $P_{\max} = 23\text{dBm}$ , +- $R_{\min} = -40\text{dBm}$ , +- $CL_{x-ile}$ and $\gamma$ are set as following: + - $CL_{x-ile} = 88 + 10 \cdot \log_{10}(200/X) + 11 - Y$ , where X is UL transmission BW (MHz) and Y is the BS noise figure + +- $\gamma = 1$ For uplink scenario. + +#### 6.2.6.2 TN DL TPC + +For downlink scenario, no power control scheme is applied. + +#### 6.2.6.3 ATG UL TPC + +For uplink scenario, TPC model specified in Section 9.1 TR 36.942 is applied for TN with following parameters. + +$$P_t = P_{\max} \times \min \left\{ 1, \max \left[ R_{\min}, \left( \frac{CL}{CL_{x-ile}} \right)^\gamma \right] \right\}$$ + +where: + +- $P_{\max}$ is ATG UE maximum output power (TRP) dBm, +- $R_{\min}$ is ATG UE minimum output power (TRP) dBm, +- $CL_{x-ile}$ and $\gamma$ are set as following: + - $CL_{x-ile} = 10 * \log_{10}(P_{\max}) - (\text{SNR}_{\text{target}} + (-174 + F + 10 * \log(B)))$ + - $\text{SNR}_{\text{target}}$ is the targeted UL SNR (dB). + - $F$ is BS noise figure (dB). + - $B$ is UL transmission BW (Hz) +- $\gamma = 1$ for uplink scenario. + +The specific parameters are assumed as below in table 6.2.6.3. + +**Table 6.2.6.3-1 LOS probability** + +| UE UL power control parameters | 2GHz | 4GHz | +|--------------------------------|--------|----------------------------| +| Target SNR | 15dB | 15dB | +| $P_{\max}$ (TRP) | 40dBm | 23dBm for per polarization | +| BW | 20MHz | 100MHz | +| $R_{\min}$ | -27dBm | -20dBm | +| NF for ATG BS | 5dB | 5dB | +| $CL_{x-ile}$ | 121dB | 97 | + +#### 6.2.6.4 ATG DL TPC + +For downlink scenario, no power control scheme is applied. + +### 6.2.7 Received power model + +The received power in downlink and uplink scenarios is defined as below: + +$$\text{RX\_PWR} = \text{TX\_PWR} - \text{Path loss} + \text{G\_TX} + \text{G\_RX}$$ + +where: + +- RX\_PWR is the received power +- TX\_PWR is the transmitted power +- G\_TX is the transmitter antenna gain (directional array gain) +- G\_RX is the receiver antenna gain (directional array gain). + +### 6.2.8 Performance metric + +For NR, the average throughput loss and 5%-ile throughput loss should be less than 5%. + +For ATG, the average throughput loss and 5%-ile throughput loss should be less than 5%. + +For synchronized scenario, when TN network as victim, the average throughput loss should be calculated in each of the TN cells. Results should be presented for the average throughput loss in the worst case TN cell, and an average of the average throughput losses in all of the TN cells in the cluster may also be presented. The details could be found as following: + +5% and average in the whole network (When TN UL as victim, 5% and average are 5% and average of the whole TN UL. When ATG as victim, 5% and average are the 5% and average among all drops.) + +5% and average of users within the cell with largest throughput loss for the case of TN DL victim + +For non-synchronized scenario, compared with ATG UE-to-TN UE CLI, ATG BS-to-TN BS CLI is the dominate interference. So we only consider ATG BS-to-TN BS CLI simulation and detailed performance metric is as below: + +When TN gNB as victim, only focus on the TN sector with worst throughput loss, 5% and mean among all drops + +When ATG gNB as victim, 5% and mean among all drops. + +### 6.2.9 Link level performance for NR ATG coexistence + +The throughput of a modem with link adaptation can be approximated by an attenuated and truncated form of the Shannon bound. (The Shannon bound represents the maximum theoretical throughput than can be achieved over an AWGN channel for a given SNIR). The following equations approximate the throughput over a channel with a given SNIR, when using link adaptation: + +$$\text{Throughput (SNIR), bps/Hz} = \begin{cases} 0 & \text{for } \text{SNIR} < \text{SNIR}_{\text{MIN}} \\ \alpha \cdot S(\text{SNIR}) & \text{for } \text{SNIR}_{\text{MIN}} \leq \text{SNIR} < \text{SNIR}_{\text{MAX}} \\ \alpha \cdot S(\text{SNIR}_{\text{MAX}}) & \text{for } \text{SNIR} \geq \text{SNIR}_{\text{MAX}} \end{cases}$$ + +Where: + +- $S(\text{SNIR})$ Shannon bound, $S(\text{SNIR}) = \log_2(1+\text{SNIR})$ bps/Hz +- $\alpha$ Attenuation factor, representing implementation losses +- $\text{SNIR}_{\text{MIN}}$ Minimum SNIR of the code set, dB + +- $\text{SNIR}_{\text{MAX}}$ Maximum SNIR of the code set, dB + +The parameters $\alpha$ , $\text{SNIR}_{\text{MIN}}$ and $\text{SNIR}_{\text{MAX}}$ can be chosen to represent different modem implementations and link conditions. The parameters proposed in Table 4.2.7-1 represent a baseline case, which assumes: + +- 1:1 antenna configuration +- AWGN channel model +- Link Adaptation (see Table 4.2.7-1 for details of the highest and lowest rate codes) +- No HARQ + +**Table 6.2.9-1: Parameters describing baseline Link Level performance for 5G NR** + +| Parameter | DL | UL | Notes | +|---------------------------------|-----|-----|----------------------------------------------| +| $\alpha$ , attenuation | 0.6 | 0.4 | Represents implementation losses | +| $\text{SNIR}_{\text{MIN}}$ , dB | -10 | -10 | Based on QPSK, 1/8 rate (DL) & 1/5 rate (UL) | +| $\text{SNIR}_{\text{MAX}}$ , dB | 30 | 22 | Based on 256QAM 0.93(DL) & 64QAM 0.93 (UL) | + +Note that the parameters proposed in Table 4.2.7-1 are targeted for eMBB coexistence scenario. + +## 6.3 Co-existence simulation methodology + +Adopt following simulation steps. + +- Step 1: Generate aggressor and victim networks. + - One ATG site with one sector is dropped referring to clause 6.2.1.3 + - Deployment of terrestrial network (19 cells with wraparound) refers to Table 6.2.1.2-1 + - The relationship between TN and ATG can refer to clause 6.2.1.1 +- Step2: UE associations + - TN UE are generated randomly inside the TN network, make sure enough TN UEs are associated to each TN sectors based on coupling loss. + - Deployment of ATG UE refers to clause 6.2.1.3. +- Step 3: Once association is done, round robin scheduling is used. BF weights are adjusted to point to the LOS direction between BS/ATG BS-UE. This is done for both victim and aggressor networks. +- Step 4: Throughput is computed in the victim systems without considering ACI as below: + +$$\text{Thput}_{\text{NO ACI}}[\text{bpshz}] = f(\text{SINR}_{\text{ICI}}) = f\left(\frac{s}{N+I_{\text{ICI}}}\right),$$ + +where: $I_{\text{ICI}}$ is the inter-cell interference. + +- Step 5: Throughput is computed considering ACI as below: + +$$\text{Thput}_{\text{ACI}}[\text{bpshz}] = f(\text{SINR}_{\text{ICI}+\text{ACI}}) = f\left(\frac{s}{N+I_{\text{ICI}}+I_{\text{ACI}}}\right),$$ + +where: $I_{ACI}$ is the adjacent channel interference. + +- Step 6: RF parameters are determined based on the degradation cause by ACI as below: + +$$Loss_{ACI} = 1 - \frac{Thput_{ACI}}{Thput_{SINGLE}}$$ + +## 6.4 Co-existence simulation results + +### 6.4.1 Synchronized Scenarios + +#### 6.4.1.1 Scenario 1: 4GHz ATG DL interfering TN DL + +This scenario captures the co-existence results after evaluation from all possible options. Here ATG DL with both AAS subarray and non-subarray model is interfering TN DL deployed in rural macro environment. + +**Table 6.4.1.1-1: Throughput Loss (%) at ATG BS ACLR 45 dB for Scenario 1 – 4 GHz ATG DL interfering TN DL** + +| Company | ATG/ TN BS antenna model | Performance Metric | Throughput Loss (%) at ATG BS ACLR 45 dB | +|----------|--------------------------|------------------------------------------------------------------------------------------------|------------------------------------------| +| Ericsson | Non-Subarray | 5% in the whole network | 0.102 | +| | | Average of all users in the whole network | 0.010 | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | 2.465 | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | 0.268 | +| | Subarray | 5% in the whole network | 0.038 | +| | | Average of all users in the whole network | 0.009 | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | 0.905 | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | 0.241 | +| ZTE | Non-Subarray | 5% in the whole network | 0.083 | +| | | Average of all users in the whole network | 0.013 | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | 2.388 | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | 0.175 | +| | Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | - | +| CMCC | Non-Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | 0.016 | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | 3.455 | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | 0.761 | +| | Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | - | +| Qualcomm | Non-Subarray | 5% in the whole network | 0.355 | +| | | Average of all users in the whole network | 0.080 | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | 0.524 | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | 0.149 | +| | Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | - | +| Huawei | Non-Subarray | 5% in the whole network | 0 | +| | | Average of all users in the whole network | 0 | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | - | +| | Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | - | +| CATT | Non-Subarray | 5% in the whole network | 0.096 | +| | | Average of all users in the whole network | 0.019 | + +| | | | +|----------|------------------------------------------------------------------------------------------------|---| +| Subarray | 5% of users within the cell with largest throughput loss for the case of TN DL victim | - | +| | Average of all users within the cell with largest throughput loss for the case of TN DL victim | - | +| | 5% in the whole network | - | +| | Average of all users in the whole network | - | +| | 5% of users within the cell with largest throughput loss for the case of TN DL victim | - | +| | Average of all users within the cell with largest throughput loss for the case of TN DL victim | - | + +##### 6.4.1.1.1 Non-Subarray model + +![Line graph titled 'Throughput Loss - 5% in the whole network' showing throughput loss (%) vs ATG BS ACLR (dB) for Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT. Qualcomm shows the highest loss, starting at ~2.5% at 35 dB and dropping to ~0.1% at 55 dB. Huawei starts at ~1.0% and drops to ~0.1%. Other vendors remain near 0%.](a8f5e96261c2ea20a0f83f121d8fcbcb_img.jpg) + +| ATG BS ACLR (dB) | Ericsson | ZTE | CMCC | Qualcomm | Huawei | CATT | +|------------------|----------|-----|------|----------|--------|------| +| 35 | 0.1 | 0.1 | 0.1 | 2.5 | 1.0 | 0.1 | +| 36 | 0.1 | 0.1 | 0.1 | 2.1 | 0.8 | 0.1 | +| 37 | 0.1 | 0.1 | 0.1 | 1.8 | 0.7 | 0.1 | +| 38 | 0.1 | 0.1 | 0.1 | 1.4 | 0.6 | 0.1 | +| 39 | 0.1 | 0.1 | 0.1 | 1.2 | 0.5 | 0.1 | +| 40 | 0.1 | 0.1 | 0.1 | 1.0 | 0.5 | 0.1 | +| 41 | 0.1 | 0.1 | 0.1 | 0.9 | 0.5 | 0.1 | +| 42 | 0.1 | 0.1 | 0.1 | 0.8 | 0.5 | 0.1 | +| 43 | 0.1 | 0.1 | 0.1 | 0.6 | 0.3 | 0.1 | +| 44 | 0.1 | 0.1 | 0.1 | 0.4 | 0.1 | 0.1 | +| 45 | 0.1 | 0.1 | 0.1 | 0.3 | 0.0 | 0.1 | +| 46 | 0.1 | 0.1 | 0.1 | 0.2 | 0.1 | 0.1 | +| 47 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | +| 48 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | +| 49 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | +| 50 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | +| 51 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | +| 52 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | +| 53 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | +| 54 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | +| 55 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | + +Line graph titled 'Throughput Loss - 5% in the whole network' showing throughput loss (%) vs ATG BS ACLR (dB) for Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT. Qualcomm shows the highest loss, starting at ~2.5% at 35 dB and dropping to ~0.1% at 55 dB. Huawei starts at ~1.0% and drops to ~0.1%. Other vendors remain near 0%. + +Figure 6.4.1.1-1: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph titled 'Throughput Loss - Average of all users in the whole network' showing throughput loss (%) vs ATG BS ACLR (dB) for Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT. Qualcomm shows the highest loss, starting at ~0.5% at 35 dB and dropping to ~0.05% at 55 dB. Huawei starts at ~0.1% and drops to ~0.05%. Other vendors remain near 0%.](343b095a7665e9a50574a33180bc51e4_img.jpg) + +| ATG BS ACLR (dB) | Ericsson | ZTE | CMCC | Qualcomm | Huawei | CATT | +|------------------|----------|------|------|----------|--------|------| +| 35 | 0.01 | 0.01 | 0.01 | 0.5 | 0.1 | 0.01 | +| 36 | 0.01 | 0.01 | 0.01 | 0.4 | 0.1 | 0.01 | +| 37 | 0.01 | 0.01 | 0.01 | 0.35 | 0.1 | 0.01 | +| 38 | 0.01 | 0.01 | 0.01 | 0.3 | 0.1 | 0.01 | +| 39 | 0.01 | 0.01 | 0.01 | 0.25 | 0.1 | 0.01 | +| 40 | 0.01 | 0.01 | 0.01 | 0.2 | 0.1 | 0.01 | +| 41 | 0.01 | 0.01 | 0.01 | 0.15 | 0.1 | 0.01 | +| 42 | 0.01 | 0.01 | 0.01 | 0.12 | 0.1 | 0.01 | +| 43 | 0.01 | 0.01 | 0.01 | 0.1 | 0.05 | 0.01 | +| 44 | 0.01 | 0.01 | 0.01 | 0.08 | 0.05 | 0.01 | +| 45 | 0.01 | 0.01 | 0.01 | 0.07 | 0.05 | 0.01 | +| 46 | 0.01 | 0.01 | 0.01 | 0.06 | 0.05 | 0.01 | +| 47 | 0.01 | 0.01 | 0.01 | 0.05 | 0.05 | 0.01 | +| 48 | 0.01 | 0.01 | 0.01 | 0.04 | 0.05 | 0.01 | +| 49 | 0.01 | 0.01 | 0.01 | 0.03 | 0.05 | 0.01 | +| 50 | 0.01 | 0.01 | 0.01 | 0.02 | 0.05 | 0.01 | +| 51 | 0.01 | 0.01 | 0.01 | 0.01 | 0.05 | 0.01 | +| 52 | 0.01 | 0.01 | 0.01 | 0.01 | 0.05 | 0.01 | +| 53 | 0.01 | 0.01 | 0.01 | 0.01 | 0.05 | 0.01 | +| 54 | 0.01 | 0.01 | 0.01 | 0.01 | 0.05 | 0.01 | +| 55 | 0.01 | 0.01 | 0.01 | 0.01 | 0.05 | 0.01 | + +Line graph titled 'Throughput Loss - Average of all users in the whole network' showing throughput loss (%) vs ATG BS ACLR (dB) for Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT. Qualcomm shows the highest loss, starting at ~0.5% at 35 dB and dropping to ~0.05% at 55 dB. Huawei starts at ~0.1% and drops to ~0.05%. Other vendors remain near 0%. + +Figure 6.4.1.1-2: Simulation results for Throughput Loss – Average of all users in the whole network + +![Line graph showing Throughput Loss (%) vs ATG BS ACLR (dB) for 5% of users within cell of largest throughput loss of victim network. The graph compares four vendors: Ericsson, ZTE, CMCC, and Qualcomm. Throughput loss generally decreases as ATG BS ACLR increases from 35 dB to 50 dB, then remains relatively flat. Qualcomm shows the lowest throughput loss, while CMCC shows the highest.](c53adc66eab40abd5f8b9107d950ad04_img.jpg) + +Throughput Loss - 5% of users within cell of largest throughput loss of victim network + +| ATG BS ACLR (dB) | Ericsson (%) | ZTE (%) | CMCC (%) | Qualcomm (%) | +|------------------|--------------|---------|----------|--------------| +| 35 | 4.8 | 2.9 | 5.1 | 4.8 | +| 36 | 4.8 | 2.9 | 4.8 | 3.8 | +| 37 | 4.8 | 2.9 | 4.5 | 2.9 | +| 38 | 4.8 | 2.9 | 4.2 | 2.2 | +| 39 | 4.8 | 2.9 | 4.0 | 1.8 | +| 40 | 4.8 | 2.9 | 3.8 | 1.4 | +| 41 | 4.8 | 2.6 | 3.7 | 1.4 | +| 42 | 4.7 | 2.6 | 3.6 | 1.4 | +| 43 | 3.8 | 2.5 | 3.5 | 1.0 | +| 44 | 3.1 | 2.4 | 3.5 | 0.6 | +| 45 | 2.5 | 2.4 | 3.4 | 0.6 | +| 46 | 2.0 | 2.4 | 3.4 | 0.6 | +| 47 | 1.8 | 2.4 | 3.4 | 0.5 | +| 48 | 1.8 | 2.4 | 3.4 | 0.3 | +| 49 | 1.8 | 2.4 | 3.4 | 0.2 | +| 50 | 1.8 | 2.4 | 3.4 | 0.1 | +| 51 | - | - | 3.4 | - | +| 52 | - | - | 3.4 | - | +| 53 | - | - | 3.4 | - | +| 54 | - | - | 3.4 | - | +| 55 | - | - | 3.4 | - | + +Line graph showing Throughput Loss (%) vs ATG BS ACLR (dB) for 5% of users within cell of largest throughput loss of victim network. The graph compares four vendors: Ericsson, ZTE, CMCC, and Qualcomm. Throughput loss generally decreases as ATG BS ACLR increases from 35 dB to 50 dB, then remains relatively flat. Qualcomm shows the lowest throughput loss, while CMCC shows the highest. + +Figure 6.4.1.1-3: Simulation results for Throughput Loss – 5% of users within cell of largest throughput loss of victim network + +![Line graph showing Throughput Loss (%) vs ATG BS ACLR (dB) for the average of all users within cell of largest throughput loss of victim network. The graph compares four vendors: Ericsson, ZTE, CMCC, and Qualcomm. Throughput loss generally decreases as ATG BS ACLR increases from 35 dB to 50 dB, then remains relatively flat. Qualcomm shows the lowest throughput loss, while CMCC shows the highest.](4349d5e2b079af7d2e45e10a3b8235e9_img.jpg) + +Throughput Loss - Average of all users within cell of largest throughput loss of victim network + +| ATG BS ACLR (dB) | Ericsson (%) | ZTE (%) | CMCC (%) | Qualcomm (%) | +|------------------|--------------|---------|----------|--------------| +| 35 | 0.38 | 0.22 | 1.05 | 0.98 | +| 36 | 0.35 | 0.22 | 0.98 | 0.82 | +| 37 | 0.33 | 0.22 | 0.92 | 0.72 | +| 38 | 0.31 | 0.22 | 0.88 | 0.62 | +| 39 | 0.30 | 0.22 | 0.85 | 0.52 | +| 40 | 0.30 | 0.22 | 0.82 | 0.45 | +| 41 | 0.30 | 0.22 | 0.80 | 0.45 | +| 42 | 0.30 | 0.22 | 0.78 | 0.45 | +| 43 | 0.30 | 0.22 | 0.78 | 0.30 | +| 44 | 0.30 | 0.22 | 0.78 | 0.20 | +| 45 | 0.30 | 0.22 | 0.78 | 0.20 | +| 46 | 0.30 | 0.22 | 0.78 | 0.20 | +| 47 | 0.30 | 0.22 | 0.78 | 0.15 | +| 48 | 0.30 | 0.22 | 0.78 | 0.10 | +| 49 | 0.30 | 0.22 | 0.78 | 0.10 | +| 50 | 0.30 | 0.22 | 0.78 | 0.08 | +| 51 | - | - | 0.78 | - | +| 52 | - | - | 0.78 | - | +| 53 | - | - | 0.78 | - | +| 54 | - | - | 0.78 | - | +| 55 | - | - | 0.78 | - | + +Line graph showing Throughput Loss (%) vs ATG BS ACLR (dB) for the average of all users within cell of largest throughput loss of victim network. The graph compares four vendors: Ericsson, ZTE, CMCC, and Qualcomm. Throughput loss generally decreases as ATG BS ACLR increases from 35 dB to 50 dB, then remains relatively flat. Qualcomm shows the lowest throughput loss, while CMCC shows the highest. + +Figure 6.4.1.1-4: Simulation results for Throughput Loss – Average of all users within cell of largest throughput loss of victim network + +##### 6.4.1.1.2 Subarray model + +![Line graph titled 'Throughput Loss - 5% in the whole network' showing throughput loss percentage vs ATG BS ACLR (dB) for Ericsson. The loss starts at ~0.046% at 35 dB, drops to ~0.038% at 37 dB, and remains constant at 0.038% through 50 dB.](a0fdaf0b566e05f53f0085cf41e2dbad_img.jpg) + +| ATG BS ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 35 | 0.046 | +| 36 | 0.044 | +| 37 | 0.038 | +| 38 | 0.038 | +| 39 | 0.038 | +| 40 | 0.038 | +| 41 | 0.038 | +| 42 | 0.038 | +| 43 | 0.038 | +| 44 | 0.038 | +| 45 | 0.038 | +| 46 | 0.038 | +| 47 | 0.038 | +| 48 | 0.038 | +| 49 | 0.038 | +| 50 | 0.038 | + +Line graph titled 'Throughput Loss - 5% in the whole network' showing throughput loss percentage vs ATG BS ACLR (dB) for Ericsson. The loss starts at ~0.046% at 35 dB, drops to ~0.038% at 37 dB, and remains constant at 0.038% through 50 dB. + +Figure 6.4.1.1-5: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph titled 'Throughput Loss - Average of all users in the whole network' showing throughput loss percentage vs ATG BS ACLR (dB) for Ericsson. The loss starts at ~0.013% at 35 dB and gradually decreases to ~0.009% at 50 dB.](1cd6a2d6e58e0e6d75c879a999be06ef_img.jpg) + +| ATG BS ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 35 | 0.013 | +| 36 | 0.012 | +| 37 | 0.0115 | +| 38 | 0.011 | +| 39 | 0.0105 | +| 40 | 0.0102 | +| 41 | 0.0098 | +| 42 | 0.0095 | +| 43 | 0.0092 | +| 44 | 0.009 | +| 45 | 0.0088 | +| 46 | 0.0086 | +| 47 | 0.0084 | +| 48 | 0.0082 | +| 49 | 0.008 | +| 50 | 0.0078 | + +Line graph titled 'Throughput Loss - Average of all users in the whole network' showing throughput loss percentage vs ATG BS ACLR (dB) for Ericsson. The loss starts at ~0.013% at 35 dB and gradually decreases to ~0.009% at 50 dB. + +Figure 6.4.1.1-6: Simulation results for Throughput Loss – Average of all users in the whole network + +![Line graph showing Throughput Loss (%) vs ATG BS ACLR (dB) for 5% of users within cell of largest loss of victim network. The y-axis values are all 0.9057939. The x-axis ranges from 35 to 55 dB. The data points show a slight downward trend from approximately 0.9057939 at 35 dB to 0.9057939 at 50 dB.](771c18f874d31c59c3b8c4e247be16ca_img.jpg) + +Throughput Loss - 5% of users within cell of largest loss of victim network + +ATG BS ACLR (dB) + +Ericsson + +| ATG BS ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 35 | 0.9057939 | +| 36 | 0.9057939 | +| 37 | 0.9057939 | +| 38 | 0.9057939 | +| 39 | 0.9057939 | +| 40 | 0.9057939 | +| 41 | 0.9057939 | +| 42 | 0.9057939 | +| 43 | 0.9057939 | +| 44 | 0.9057939 | +| 45 | 0.9057939 | +| 46 | 0.9057939 | +| 47 | 0.9057939 | +| 48 | 0.9057939 | +| 49 | 0.9057939 | +| 50 | 0.9057939 | + +Line graph showing Throughput Loss (%) vs ATG BS ACLR (dB) for 5% of users within cell of largest loss of victim network. The y-axis values are all 0.9057939. The x-axis ranges from 35 to 55 dB. The data points show a slight downward trend from approximately 0.9057939 at 35 dB to 0.9057939 at 50 dB. + +Figure 6.4.1.1-7: Simulation results for Throughput Loss – 5% of users within cell of largest throughput loss of victim network + +![Line graph showing Throughput Loss (%) vs ATG BS ACLR (dB) for average of all users within cell of largest throughput loss of victim network. The y-axis ranges from 0 to 0.35. The x-axis ranges from 35 to 55 dB. The data points show a slight downward trend from approximately 0.32 at 35 dB to 0.24 at 50 dB.](0aa15f5c9c3edae230985491199cfe8b_img.jpg) + +Throughput Loss - Average of all users within cell of largest throughput loss of victim network + +ATG BS ACLR (dB) + +Ericsson + +| ATG BS ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 35 | 0.32 | +| 36 | 0.31 | +| 37 | 0.30 | +| 38 | 0.29 | +| 39 | 0.28 | +| 40 | 0.27 | +| 41 | 0.26 | +| 42 | 0.25 | +| 43 | 0.24 | +| 44 | 0.24 | +| 45 | 0.24 | +| 46 | 0.24 | +| 47 | 0.24 | +| 48 | 0.24 | +| 49 | 0.24 | +| 50 | 0.24 | + +Line graph showing Throughput Loss (%) vs ATG BS ACLR (dB) for average of all users within cell of largest throughput loss of victim network. The y-axis ranges from 0 to 0.35. The x-axis ranges from 35 to 55 dB. The data points show a slight downward trend from approximately 0.32 at 35 dB to 0.24 at 50 dB. + +Figure 6.4.1.1-8: Simulation results for Throughput Loss – Average of all users within cell of largest throughput loss of victim network + +#### 6.4.1.2 Scenario 2: 4GHz ATG UL interfering TN UL + +This scenario captures the co-existence results after evaluation from all possible options. Here ATG UL with both AAS subarray and non-subarray model is interfering TN UL deployed in rural macro environment. + +**Table 6.4.1.2-1: Simulation results for Scenario 2 – 4 GHz ATG UL interfering TN UL** + +| Company | ATG/ TN BS antenna model | Performance Metric | Throughput Loss (%) at ATG UE ACLR 30 dB | | +|----------|--------------------------|------------------------------------------------------------------------------------------------|--------------------------------------------|--------| +| | | | Maximum distance between ATG BS and ATG UE | | +| | | | 100 km | 300 km | +| Ericsson | Non-Subarray | 5% in the whole network | 0 | 0 | +| | | Average of all users in the whole network | 0 | 0 | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | 0.05 | 0.05 | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | 0 | 0 | +| | Subarray | 5% in the whole network | 0 | 0 | +| | | Average of all users in the whole network | 0 | 0 | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | 0.03 | 0.03 | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | 0.01 | 0.01 | +| ZTE | Non-Subarray | 5% in the whole network | 0 | - | +| | | Average of all users in the whole network | 0 | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| | Subarray | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| CMCC | Non-Subarray | 5% in the whole network | 0 | - | +| | | Average of all users in the whole network | 0 | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | 0.03 | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | 0.01 | - | +| | Subarray | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| Qualcomm | Non-Subarray | 5% in the whole network | 0 | - | +| | | Average of all users in the whole network | 0 | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | 0 | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | 0 | - | +| | Subarray | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| Huawei | Non-Subarray | 5% in the whole network | 0 | - | +| | | Average of all users in the whole network | 0 | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | 0 | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | 0 | - | +| | Subarray | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | + +| | | | | | +|------|--------------|------------------------------------------------------------------------------------------------|---|---| +| CATT | Non-Subarray | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| | | 5% in the whole network | 0 | - | +| | | Average of all users in the whole network | 0 | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| | Subarray | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| | | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | + +##### 6.4.1.2.1 Non-Subarray model + +Maximum distance between ATG BS and ATG UE is 100 km + +![Line graph titled 'Throughput Loss - 5% in the whole network - (20 to) 100km'. The y-axis is 'Throughput Loss (%)' ranging from 0 to 0.006. The x-axis is 'ATG UE ACLR (dB)' ranging from 20 to 40. The graph shows data for six vendors: Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT. CMCC (green line with circles) starts at approximately 0.0055% at 20 dB and decreases to about 0.0002% at 40 dB. All other vendors (Ericsson, ZTE, Qualcomm, Huawei, CATT) show a throughput loss of 0% across the entire range of ACLR values.](54bab05b404ce895e109a02e758a548a_img.jpg) + +Line graph titled 'Throughput Loss - 5% in the whole network - (20 to) 100km'. The y-axis is 'Throughput Loss (%)' ranging from 0 to 0.006. The x-axis is 'ATG UE ACLR (dB)' ranging from 20 to 40. The graph shows data for six vendors: Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT. CMCC (green line with circles) starts at approximately 0.0055% at 20 dB and decreases to about 0.0002% at 40 dB. All other vendors (Ericsson, ZTE, Qualcomm, Huawei, CATT) show a throughput loss of 0% across the entire range of ACLR values. + +Figure 6.4.1.2-1: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph titled 'Throughput Loss - Average of all users in whole network - (20 to) 100km'. The y-axis is 'Throughput Loss (%)' ranging from 0 to 0.004. The x-axis is 'ATG UE ACLR (dB)' ranging from 20 to 40. The graph shows data for six vendors: Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT. Ericsson (blue line with circles) starts at approximately 0.0035% at 20 dB and decreases to about 0.0001% at 40 dB. CMCC (green line with circles) starts at approximately 0.002% at 20 dB and decreases to about 0.0001% at 40 dB. Qualcomm (purple line with circles) starts at approximately 0.0008% at 20 dB and decreases to about 0.0001% at 40 dB. ZTE (red line with circles), Huawei (cyan line with circles), and CATT (orange line with circles) all show a throughput loss of 0% across the entire range of ACLR values.](4ee6ee5ce67694dbc95537938e09a917_img.jpg) + +Line graph titled 'Throughput Loss - Average of all users in whole network - (20 to) 100km'. The y-axis is 'Throughput Loss (%)' ranging from 0 to 0.004. The x-axis is 'ATG UE ACLR (dB)' ranging from 20 to 40. The graph shows data for six vendors: Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT. Ericsson (blue line with circles) starts at approximately 0.0035% at 20 dB and decreases to about 0.0001% at 40 dB. CMCC (green line with circles) starts at approximately 0.002% at 20 dB and decreases to about 0.0001% at 40 dB. Qualcomm (purple line with circles) starts at approximately 0.0008% at 20 dB and decreases to about 0.0001% at 40 dB. ZTE (red line with circles), Huawei (cyan line with circles), and CATT (orange line with circles) all show a throughput loss of 0% across the entire range of ACLR values. + +Figure 6.4.1.2-2: Simulation results for Throughput Loss – Average of all users in the whole network + +![Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for 5% of users within cell of largest throughput loss of victim network. The y-axis ranges from 0 to 0.5. The x-axis ranges from 20 to 40 dB. Four data series are shown: Ericsson (blue), CMCC (green), Qualcomm (purple), and Huawei (cyan). Ericsson and CMCC show a decreasing trend from approximately 0.47% and 0.3% respectively at 20 dB down to near 0% at 40 dB. Qualcomm and Huawei remain near 0% throughout the range.](0892c0cb3b8502a44c4fe4e786be912a_img.jpg) + +Throughput Loss - 5% of users within cell of largest throughput loss of victim network - (20 to) 100km + +| ATG UE ACLR (dB) | Ericsson (%) | CMCC (%) | Qualcomm (%) | Huawei (%) | +|------------------|--------------|----------|--------------|------------| +| 20 | 0.47 | 0.30 | 0.00 | 0.00 | +| 21 | 0.38 | 0.24 | 0.00 | 0.00 | +| 22 | 0.30 | 0.19 | 0.00 | 0.00 | +| 23 | 0.24 | 0.15 | 0.00 | 0.00 | +| 24 | 0.19 | 0.12 | 0.00 | 0.00 | +| 25 | 0.15 | 0.09 | 0.00 | 0.00 | +| 26 | 0.12 | 0.07 | 0.00 | 0.00 | +| 27 | 0.10 | 0.06 | 0.00 | 0.00 | +| 28 | 0.08 | 0.05 | 0.00 | 0.00 | +| 29 | 0.07 | 0.04 | 0.00 | 0.00 | +| 30 | 0.06 | 0.04 | 0.00 | 0.00 | +| 31 | 0.05 | 0.03 | 0.00 | 0.00 | +| 32 | 0.04 | 0.03 | 0.00 | 0.00 | +| 33 | 0.03 | 0.02 | 0.00 | 0.00 | +| 34 | 0.02 | 0.02 | 0.00 | 0.00 | +| 35 | 0.02 | 0.01 | 0.00 | 0.00 | +| 36 | 0.01 | 0.01 | 0.00 | 0.00 | +| 37 | 0.01 | 0.01 | 0.00 | 0.00 | +| 38 | 0.01 | 0.01 | 0.00 | 0.00 | +| 39 | 0.01 | 0.01 | 0.00 | 0.00 | +| 40 | 0.01 | 0.01 | 0.00 | 0.00 | + +Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for 5% of users within cell of largest throughput loss of victim network. The y-axis ranges from 0 to 0.5. The x-axis ranges from 20 to 40 dB. Four data series are shown: Ericsson (blue), CMCC (green), Qualcomm (purple), and Huawei (cyan). Ericsson and CMCC show a decreasing trend from approximately 0.47% and 0.3% respectively at 20 dB down to near 0% at 40 dB. Qualcomm and Huawei remain near 0% throughout the range. + +Figure 6.4.1.2-3: Simulation results for Throughput Loss – 5% of users within cell of largest throughput loss of victim network + +![Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for the average of all users within cell of largest throughput loss of victim network. The y-axis ranges from 0 to 0.06. The x-axis ranges from 20 to 40 dB. Four data series are shown: Ericsson (blue), CMCC (green), Qualcomm (purple), and Huawei (cyan). Ericsson and CMCC show a decreasing trend from approximately 0.047% and 0.053% respectively at 20 dB down to near 0% at 40 dB. Qualcomm and Huawei remain near 0% throughout the range.](d49bc18ad8867b97bbb9aa580449a641_img.jpg) + +Throughput Loss - Average of all users within cell of largest throughput loss of victim network - (20 to) 100km + +| ATG UE ACLR (dB) | Ericsson (%) | CMCC (%) | Qualcomm (%) | Huawei (%) | +|------------------|--------------|----------|--------------|------------| +| 20 | 0.047 | 0.053 | 0.00 | 0.00 | +| 21 | 0.038 | 0.043 | 0.00 | 0.00 | +| 22 | 0.030 | 0.034 | 0.00 | 0.00 | +| 23 | 0.024 | 0.027 | 0.00 | 0.00 | +| 24 | 0.019 | 0.022 | 0.00 | 0.00 | +| 25 | 0.015 | 0.017 | 0.00 | 0.00 | +| 26 | 0.012 | 0.014 | 0.00 | 0.00 | +| 27 | 0.010 | 0.011 | 0.00 | 0.00 | +| 28 | 0.008 | 0.009 | 0.00 | 0.00 | +| 29 | 0.007 | 0.008 | 0.00 | 0.00 | +| 30 | 0.006 | 0.007 | 0.00 | 0.00 | +| 31 | 0.005 | 0.006 | 0.00 | 0.00 | +| 32 | 0.004 | 0.005 | 0.00 | 0.00 | +| 33 | 0.003 | 0.004 | 0.00 | 0.00 | +| 34 | 0.002 | 0.003 | 0.00 | 0.00 | +| 35 | 0.002 | 0.002 | 0.00 | 0.00 | +| 36 | 0.001 | 0.002 | 0.00 | 0.00 | +| 37 | 0.001 | 0.001 | 0.00 | 0.00 | +| 38 | 0.001 | 0.001 | 0.00 | 0.00 | +| 39 | 0.001 | 0.001 | 0.00 | 0.00 | +| 40 | 0.001 | 0.001 | 0.00 | 0.00 | + +Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for the average of all users within cell of largest throughput loss of victim network. The y-axis ranges from 0 to 0.06. The x-axis ranges from 20 to 40 dB. Four data series are shown: Ericsson (blue), CMCC (green), Qualcomm (purple), and Huawei (cyan). Ericsson and CMCC show a decreasing trend from approximately 0.047% and 0.053% respectively at 20 dB down to near 0% at 40 dB. Qualcomm and Huawei remain near 0% throughout the range. + +Figure 6.4.1.2-4: Simulation results for Throughput Loss – Average of all users within cell of largest throughput loss of victim network + +Maximum distance between ATG BS and ATG UE is 300 km + +![Line graph titled 'Throughput Loss - 5% in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' ranging from 0 to 0.0000016. The x-axis is 'ATG UE ACLR (dB)' ranging from 20 to 40. A blue line with circular markers represents 'Ericsson' data, showing a decreasing trend from approximately 0.0000015% at 20 dB to near 0% at 40 dB.](a85105fd544c64ef624aa45c72378647_img.jpg) + +Throughput Loss - 5% in the whole network - 300km + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 0.0000015 | +| 21 | 0.0000012 | +| 22 | 0.0000010 | +| 23 | 0.0000008 | +| 24 | 0.0000006 | +| 25 | 0.0000005 | +| 26 | 0.0000004 | +| 27 | 0.0000003 | +| 28 | 0.0000002 | +| 29 | 0.00000015 | +| 30 | 0.0000001 | +| 31 | 8e-05 | +| 32 | 6e-05 | +| 33 | 5e-05 | +| 34 | 4e-05 | +| 35 | 3e-05 | +| 36 | 2e-05 | +| 37 | 1e-05 | +| 38 | 1e-05 | +| 39 | 1e-05 | +| 40 | 1e-05 | + +Ericsson + +Line graph titled 'Throughput Loss - 5% in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' ranging from 0 to 0.0000016. The x-axis is 'ATG UE ACLR (dB)' ranging from 20 to 40. A blue line with circular markers represents 'Ericsson' data, showing a decreasing trend from approximately 0.0000015% at 20 dB to near 0% at 40 dB. + +Figure 6.4.1.2-5: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph titled 'Throughput Loss - Average of all users in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' ranging from 0 to 0.004. The x-axis is 'ATG UE ACLR (dB)' ranging from 20 to 40. A blue line with circular markers represents 'Ericsson' data, showing a decreasing trend from approximately 0.0035% at 20 dB to near 0% at 40 dB.](b30a71a63c0093c8f54a2a57b1f601bb_img.jpg) + +Throughput Loss - Average of all users in the whole network - 300km + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 0.0035 | +| 21 | 0.0028 | +| 22 | 0.0022 | +| 23 | 0.0018 | +| 24 | 0.0014 | +| 25 | 0.0011 | +| 26 | 0.0009 | +| 27 | 0.0007 | +| 28 | 0.0006 | +| 29 | 0.0005 | +| 30 | 0.0004 | +| 31 | 0.0003 | +| 32 | 0.0002 | +| 33 | 0.00015 | +| 34 | 0.0001 | +| 35 | 8e-05 | +| 36 | 6e-05 | +| 37 | 4e-05 | +| 38 | 2e-05 | +| 39 | 1e-05 | +| 40 | 1e-05 | + +Ericsson + +Line graph titled 'Throughput Loss - Average of all users in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' ranging from 0 to 0.004. The x-axis is 'ATG UE ACLR (dB)' ranging from 20 to 40. A blue line with circular markers represents 'Ericsson' data, showing a decreasing trend from approximately 0.0035% at 20 dB to near 0% at 40 dB. + +Figure 6.4.1.2-6: Simulation results for Throughput Loss – Average of all users in the whole network + +![Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for 5% of users within cell of largest throughput loss of victim network - 300km. The y-axis ranges from 0 to 0.5, and the x-axis ranges from 20 to 40. The data points show a decreasing trend from approximately 0.47% at 20 dB to 0% at 40 dB.](c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg) + +Throughput Loss - 5% of users within cell of largest throughput loss of victim network - 300km + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 0.47 | +| 21 | 0.38 | +| 22 | 0.30 | +| 23 | 0.24 | +| 24 | 0.19 | +| 25 | 0.15 | +| 26 | 0.12 | +| 27 | 0.10 | +| 28 | 0.08 | +| 29 | 0.06 | +| 30 | 0.05 | +| 31 | 0.04 | +| 32 | 0.03 | +| 33 | 0.02 | +| 34 | 0.02 | +| 35 | 0.01 | +| 36 | 0.01 | +| 37 | 0.01 | +| 38 | 0.01 | +| 39 | 0.01 | +| 40 | 0.01 | + +Ericsson + +Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for 5% of users within cell of largest throughput loss of victim network - 300km. The y-axis ranges from 0 to 0.5, and the x-axis ranges from 20 to 40. The data points show a decreasing trend from approximately 0.47% at 20 dB to 0% at 40 dB. + +Figure 6.4.1.2-7: Simulation results for Throughput Loss – 5% of users within cell of largest throughput loss of victim network + +![Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for Average of all users within cell of largest throughput loss of victim network - 300km. The y-axis ranges from 0 to 0.05, and the x-axis ranges from 20 to 40. The data points show a decreasing trend from approximately 0.047% at 20 dB to 0% at 40 dB.](198d076da025c516aec8122a6ab7db20_img.jpg) + +Throughput Loss - Average of all users within cell of largest throughput loss of victim network - 300km + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 0.047 | +| 21 | 0.038 | +| 22 | 0.030 | +| 23 | 0.024 | +| 24 | 0.019 | +| 25 | 0.015 | +| 26 | 0.012 | +| 27 | 0.010 | +| 28 | 0.008 | +| 29 | 0.006 | +| 30 | 0.005 | +| 31 | 0.004 | +| 32 | 0.003 | +| 33 | 0.002 | +| 34 | 0.002 | +| 35 | 0.001 | +| 36 | 0.001 | +| 37 | 0.001 | +| 38 | 0.001 | +| 39 | 0.001 | +| 40 | 0.001 | + +Ericsson + +Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for Average of all users within cell of largest throughput loss of victim network - 300km. The y-axis ranges from 0 to 0.05, and the x-axis ranges from 20 to 40. The data points show a decreasing trend from approximately 0.047% at 20 dB to 0% at 40 dB. + +Figure 6.4.1.2-8: Simulation results for Throughput Loss – Average of all users within cell of largest throughput loss of victim network + +##### 6.4.1.2.2 Subarray model + +Maximum distance between ATG BS and ATG UE is 100 km + +![Line graph titled 'Throughput Loss - 5% in the whole network - (50 to) 100km'. The y-axis is 'Throughput Loss (%)' ranging from 0.0019 to 0.0022. The x-axis is 'ATG UE ACLR (dB)' ranging from 20 to 40. A blue line with circular markers represents 'Ericsson' data. The throughput loss remains constant at approximately 0.00216% from 20 dB to 39 dB, then drops sharply to about 0.00202% at 40 dB.](0e2f908bcaa3136175994fcf0c9c1a9f_img.jpg) + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 0.00216 | +| 21 | 0.00216 | +| 22 | 0.00216 | +| 23 | 0.00216 | +| 24 | 0.00216 | +| 25 | 0.00216 | +| 26 | 0.00216 | +| 27 | 0.00216 | +| 28 | 0.00216 | +| 29 | 0.00216 | +| 30 | 0.00216 | +| 31 | 0.00216 | +| 32 | 0.00216 | +| 33 | 0.00216 | +| 34 | 0.00216 | +| 35 | 0.00216 | +| 36 | 0.00216 | +| 37 | 0.00216 | +| 38 | 0.00216 | +| 39 | 0.00216 | +| 40 | 0.00202 | + +Line graph titled 'Throughput Loss - 5% in the whole network - (50 to) 100km'. The y-axis is 'Throughput Loss (%)' ranging from 0.0019 to 0.0022. The x-axis is 'ATG UE ACLR (dB)' ranging from 20 to 40. A blue line with circular markers represents 'Ericsson' data. The throughput loss remains constant at approximately 0.00216% from 20 dB to 39 dB, then drops sharply to about 0.00202% at 40 dB. + +Figure 6.4.1.2-9: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph titled 'Throughput Loss - Average of all users in the whole network - (50 to) 100km'. The y-axis is 'Throughput Loss (%)' ranging from 0 to 0.006. The x-axis is 'ATG UE ACLR (dB)' ranging from 20 to 40. A blue line with circular markers represents 'Ericsson' data. The throughput loss starts at approximately 0.0055% at 20 dB and decreases steadily, reaching near 0% by 38 dB, and remaining near 0% at 39 dB and 40 dB.](3a310163273edcf70c19269a06d0cdf2_img.jpg) + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 0.0055 | +| 21 | 0.0045 | +| 22 | 0.0035 | +| 23 | 0.0028 | +| 24 | 0.0022 | +| 25 | 0.0018 | +| 26 | 0.0014 | +| 27 | 0.0011 | +| 28 | 0.0009 | +| 29 | 0.0007 | +| 30 | 0.0006 | +| 31 | 0.0005 | +| 32 | 0.0004 | +| 33 | 0.0003 | +| 34 | 0.0002 | +| 35 | 0.0001 | +| 36 | 0.0001 | +| 37 | 0.0001 | +| 38 | 0.0001 | +| 39 | 0.0001 | +| 40 | 0.0001 | + +Line graph titled 'Throughput Loss - Average of all users in the whole network - (50 to) 100km'. The y-axis is 'Throughput Loss (%)' ranging from 0 to 0.006. The x-axis is 'ATG UE ACLR (dB)' ranging from 20 to 40. A blue line with circular markers represents 'Ericsson' data. The throughput loss starts at approximately 0.0055% at 20 dB and decreases steadily, reaching near 0% by 38 dB, and remaining near 0% at 39 dB and 40 dB. + +Figure 6.4.1.2-10: Simulation results for Throughput Loss – Average of all users in the whole network + +![Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for 5% of users. The y-axis ranges from 0 to 0.5, and the x-axis ranges from 20 to 40 dB. The data points show a sharp decrease from 0.4% at 20 dB to about 0.01% at 30 dB, then leveling off near 0%.](068b3a3247570c4b78342a943f15de9e_img.jpg) + +Throughput Loss - 5% of users within cell of largest throughput loss of victim network - (50 to) 100km + +ATG UE ACLR (dB) + +Ericsson + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 0.4 | +| 21 | 0.25 | +| 22 | 0.2 | +| 23 | 0.15 | +| 24 | 0.12 | +| 25 | 0.1 | +| 26 | 0.08 | +| 27 | 0.07 | +| 28 | 0.06 | +| 29 | 0.05 | +| 30 | 0.04 | +| 31 | 0.03 | +| 32 | 0.02 | +| 33 | 0.02 | +| 34 | 0.01 | +| 35 | 0.01 | +| 36 | 0.01 | +| 37 | 0.01 | +| 38 | 0.01 | +| 39 | 0.01 | +| 40 | 0.01 | + +Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for 5% of users. The y-axis ranges from 0 to 0.5, and the x-axis ranges from 20 to 40 dB. The data points show a sharp decrease from 0.4% at 20 dB to about 0.01% at 30 dB, then leveling off near 0%. + +Figure 6.4.1.2-11: Simulation results for Throughput Loss – 5% of users within cell of largest throughput loss of victim network + +![Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for the average of all users. The y-axis ranges from 0 to 0.06, and the x-axis ranges from 20 to 40 dB. The data points show a sharp decrease from 0.055% at 20 dB to about 0.005% at 30 dB, then leveling off near 0%.](a14ef8a0fbd175ce9b6d24cca8328ecd_img.jpg) + +Throughput Loss - Average of all users within cell of largest throughput loss of victim network - (50 to) 100km + +ATG UE ACLR (dB) + +Ericsson + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 0.055 | +| 21 | 0.045 | +| 22 | 0.038 | +| 23 | 0.032 | +| 24 | 0.028 | +| 25 | 0.02 | +| 26 | 0.015 | +| 27 | 0.012 | +| 28 | 0.01 | +| 29 | 0.008 | +| 30 | 0.006 | +| 31 | 0.005 | +| 32 | 0.004 | +| 33 | 0.003 | +| 34 | 0.002 | +| 35 | 0.001 | +| 36 | 0.001 | +| 37 | 0.001 | +| 38 | 0.001 | +| 39 | 0.001 | +| 40 | 0.001 | + +Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for the average of all users. The y-axis ranges from 0 to 0.06, and the x-axis ranges from 20 to 40 dB. The data points show a sharp decrease from 0.055% at 20 dB to about 0.005% at 30 dB, then leveling off near 0%. + +Figure 6.4.1.2-12: Simulation results for Throughput Loss – Average of all users within cell of largest throughput loss of victim network + +Maximum distance between ATG BS and ATG UE is 300 km + +![Line graph titled 'Throughput Loss - 5% in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' ranging from 0.0019 to 0.0022. The x-axis is 'ATG UE ACLR (dB)' ranging from 20 to 40. A blue line with circular markers represents 'Ericsson' data. The line is flat at approximately 0.00216% until 39 dB, then drops sharply to about 0.00202% at 40 dB.](77a781dfb114c3e2b399f876f1808cfd_img.jpg) + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 0.00216 | +| 21 | 0.00216 | +| 22 | 0.00216 | +| 23 | 0.00216 | +| 24 | 0.00216 | +| 25 | 0.00216 | +| 26 | 0.00216 | +| 27 | 0.00216 | +| 28 | 0.00216 | +| 29 | 0.00216 | +| 30 | 0.00216 | +| 31 | 0.00216 | +| 32 | 0.00216 | +| 33 | 0.00216 | +| 34 | 0.00216 | +| 35 | 0.00216 | +| 36 | 0.00216 | +| 37 | 0.00216 | +| 38 | 0.00216 | +| 39 | 0.00216 | +| 40 | 0.00202 | + +Line graph titled 'Throughput Loss - 5% in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' ranging from 0.0019 to 0.0022. The x-axis is 'ATG UE ACLR (dB)' ranging from 20 to 40. A blue line with circular markers represents 'Ericsson' data. The line is flat at approximately 0.00216% until 39 dB, then drops sharply to about 0.00202% at 40 dB. + +Figure 6.4.1.2-13: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph titled 'Throughput Loss - Average of all users in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' ranging from 0 to 0.006. The x-axis is 'ATG UE ACLR (dB)' ranging from 20 to 40. A blue line with circular markers represents 'Ericsson' data. The line starts at approximately 0.0055% at 20 dB and decreases steadily, reaching near 0% by 36 dB and remaining flat until 40 dB.](07c5a1c0fddd7da92a8427f5af840ffa_img.jpg) + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 0.0055 | +| 21 | 0.0045 | +| 22 | 0.0036 | +| 23 | 0.0029 | +| 24 | 0.0023 | +| 25 | 0.0018 | +| 26 | 0.0014 | +| 27 | 0.0011 | +| 28 | 0.0009 | +| 29 | 0.0007 | +| 30 | 0.0006 | +| 31 | 0.0005 | +| 32 | 0.0004 | +| 33 | 0.0003 | +| 34 | 0.0002 | +| 35 | 0.0001 | +| 36 | 0.0001 | +| 37 | 0.0001 | +| 38 | 0.0001 | +| 39 | 0.0001 | +| 40 | 0.0001 | + +Line graph titled 'Throughput Loss - Average of all users in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' ranging from 0 to 0.006. The x-axis is 'ATG UE ACLR (dB)' ranging from 20 to 40. A blue line with circular markers represents 'Ericsson' data. The line starts at approximately 0.0055% at 20 dB and decreases steadily, reaching near 0% by 36 dB and remaining flat until 40 dB. + +Figure 6.4.1.2-14: Simulation results for Throughput Loss – Average of all users in the whole network + +![Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for 5% of users within cell of largest throughput loss of victim network - 300km. The y-axis ranges from 0 to 0.45% in 0.05% increments. The x-axis ranges from 20 to 40 dB in 1 dB increments. A single blue line with circular markers represents the Ericsson simulation results. The throughput loss starts at approximately 0.39% at 20 dB and decreases steadily to about 0.01% at 40 dB.](70ececdbb871824c3e57cace6262c4d6_img.jpg) + +Throughput Loss - 5% of users within cell of largest throughput loss of victim network - 300km + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 0.39 | +| 21 | 0.24 | +| 22 | 0.19 | +| 23 | 0.15 | +| 24 | 0.12 | +| 25 | 0.10 | +| 26 | 0.08 | +| 27 | 0.06 | +| 28 | 0.05 | +| 29 | 0.04 | +| 30 | 0.03 | +| 31 | 0.02 | +| 32 | 0.02 | +| 33 | 0.01 | +| 34 | 0.01 | +| 35 | 0.01 | +| 36 | 0.01 | +| 37 | 0.01 | +| 38 | 0.01 | +| 39 | 0.01 | +| 40 | 0.01 | + +Ericsson + +Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for 5% of users within cell of largest throughput loss of victim network - 300km. The y-axis ranges from 0 to 0.45% in 0.05% increments. The x-axis ranges from 20 to 40 dB in 1 dB increments. A single blue line with circular markers represents the Ericsson simulation results. The throughput loss starts at approximately 0.39% at 20 dB and decreases steadily to about 0.01% at 40 dB. + +Figure 6.4.1.2-15: Simulation results for Throughput Loss – 5% of users within cell of largest throughput loss of victim network + +![Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for Average of all users within cell of largest throughput loss of victim network - 300km. The y-axis ranges from 0 to 0.06% in 0.01% increments. The x-axis ranges from 20 to 40 dB in 1 dB increments. A single blue line with circular markers represents the Ericsson simulation results. The throughput loss starts at approximately 0.055% at 20 dB and decreases steadily to about 0.005% at 40 dB.](e01f9228a215e26c8b62ad471c9d7a7f_img.jpg) + +Throughput Loss - Average of all users within cell of largest throughput loss of victim network - 300km + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 0.055 | +| 21 | 0.045 | +| 22 | 0.038 | +| 23 | 0.032 | +| 24 | 0.027 | +| 25 | 0.018 | +| 26 | 0.014 | +| 27 | 0.011 | +| 28 | 0.009 | +| 29 | 0.007 | +| 30 | 0.006 | +| 31 | 0.005 | +| 32 | 0.004 | +| 33 | 0.003 | +| 34 | 0.002 | +| 35 | 0.002 | +| 36 | 0.001 | +| 37 | 0.001 | +| 38 | 0.001 | +| 39 | 0.001 | +| 40 | 0.001 | + +Ericsson + +Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for Average of all users within cell of largest throughput loss of victim network - 300km. The y-axis ranges from 0 to 0.06% in 0.01% increments. The x-axis ranges from 20 to 40 dB in 1 dB increments. A single blue line with circular markers represents the Ericsson simulation results. The throughput loss starts at approximately 0.055% at 20 dB and decreases steadily to about 0.005% at 40 dB. + +Figure 6.4.1.2-16: Simulation results for Throughput Loss – Average of all users within cell of largest throughput loss of victim network + +#### 6.4.1.3 Scenario 3: 4GHz TN DL interfering ATG DL + +This scenario captures the co-existence results after evaluation from all possible options. TN DL with both AAS subarray and non-subarray model is interfering ATG DL deployed in rural macro environment. + +Table 6.4.1.3-1: Simulation results for Scenario 3 – 4GHz TN DL interfering ATG DL + +| Company | ATG/ TN BS antenna model | Performance Metric | Throughput Loss (%) at ATG UE ACS 33 dB | | +|----------|--------------------------|-------------------------------------------|--------------------------------------------|--------| +| | | | Maximum distance between ATG BS and ATG UE | | +| | | | 100 km | 300 km | +| Ericsson | Non-Subarray | 5% in the whole network | 3.60 | 7.02 | +| | | Average of all users in the whole network | 1.35 | 2.22 | +| | Subarray | 5% in the whole network | 6.35 | 11.93 | +| | | Average of all users in the whole network | 1.97 | 3.21 | +| ZTE | Non-Subarray | 5% in the whole network | 0.90 | - | +| | | Average of all users in the whole network | 0.24 | - | +| | Subarray | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | +| CMCC | Non-Subarray | 5% in the whole network | 2.39 | - | +| | | Average of all users in the whole network | 0.47 | - | +| | Subarray | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | +| Qualcomm | Non-Subarray | 5% in the whole network | 1.75 | - | +| | | Average of all users in the whole network | 0.55 | - | +| | Subarray | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | +| Huawei | Non-Subarray | 5% in the whole network | 0.18 | - | +| | | Average of all users in the whole network | 0.23 | - | +| | Subarray | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | +| CATT | Non-Subarray | 5% in the whole network | 2.04 | - | +| | | Average of all users in the whole network | 0.62 | - | +| | Subarray | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | + +##### 6.4.1.3.1 Non-Subarray model + +Maximum distance between ATG BS and ATG UE is 100 km + +![Line graph showing Throughput Loss (%) vs ATG UE ACS (dB) for 5% of users in the whole network. The graph compares six companies: Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT. Throughput loss decreases as ACS increases from 23 dB to 43 dB. Ericsson shows the highest loss, while Huawei shows the lowest.](1b1f1c6f7ba93ebe3c4f9b812d7476f9_img.jpg) + +Throughput Loss - 5% in the whole network - (20 to) 100km + +| ATG UE ACS (dB) | Ericsson (%) | ZTE (%) | CMCC (%) | Qualcomm (%) | Huawei (%) | CATT (%) | +|-----------------|--------------|---------|----------|--------------|------------|----------| +| 23 | 23.5 | 9.0 | 14.5 | 14.0 | 5.0 | 12.0 | +| 24 | 20.5 | 7.5 | 12.5 | 11.5 | 4.0 | 10.5 | +| 25 | 17.5 | 6.0 | 10.5 | 9.5 | 3.0 | 9.0 | +| 26 | 15.0 | 5.0 | 9.0 | 8.0 | 2.0 | 8.0 | +| 27 | 12.5 | 4.0 | 7.5 | 6.5 | 1.5 | 7.0 | +| 28 | 10.5 | 3.0 | 6.0 | 5.5 | 1.0 | 6.0 | +| 29 | 8.5 | 2.5 | 5.0 | 4.5 | 0.8 | 5.0 | +| 30 | 7.0 | 2.0 | 4.0 | 3.5 | 0.5 | 4.0 | +| 31 | 5.5 | 1.5 | 3.0 | 2.5 | 0.3 | 3.0 | +| 32 | 4.5 | 1.0 | 2.5 | 2.0 | 0.2 | 2.5 | +| 33 | 3.5 | 0.8 | 2.0 | 1.5 | 0.1 | 2.0 | +| 34 | 2.5 | 0.5 | 1.5 | 1.0 | 0.1 | 1.5 | +| 35 | 2.0 | 0.4 | 1.0 | 0.8 | 0.1 | 1.0 | +| 36 | 1.5 | 0.3 | 0.8 | 0.6 | 0.1 | 0.8 | +| 37 | 1.2 | 0.2 | 0.6 | 0.5 | 0.1 | 0.6 | +| 38 | 1.0 | 0.1 | 0.5 | 0.4 | 0.1 | 0.5 | +| 39 | 0.8 | 0.1 | 0.4 | 0.3 | 0.1 | 0.4 | +| 40 | 0.6 | 0.1 | 0.3 | 0.2 | 0.1 | 0.3 | +| 41 | 0.5 | 0.1 | 0.2 | 0.1 | 0.1 | 0.2 | +| 42 | 0.4 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | +| 43 | 0.3 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | + +Line graph showing Throughput Loss (%) vs ATG UE ACS (dB) for 5% of users in the whole network. The graph compares six companies: Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT. Throughput loss decreases as ACS increases from 23 dB to 43 dB. Ericsson shows the highest loss, while Huawei shows the lowest. + +Figure 6.4.1.3.1-1: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph titled 'Throughput Loss - Average of all users in whole network - (20 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 9. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. Six lines represent different vendors: Ericsson (blue), ZTE (red), CMCC (green), Qualcomm (purple), Huawei (cyan), and CATT (orange). All lines show a downward trend as ACS increases, with Ericsson showing the highest loss and others converging near 0%.](75b9cb95f5815d6f3bbe57020a049504_img.jpg) + +| ATG UE ACS (dB) | Ericsson (%) | ZTE (%) | CMCC (%) | Qualcomm (%) | Huawei (%) | CATT (%) | +|-----------------|--------------|---------|----------|--------------|------------|----------| +| 23 | 8.2 | 3.0 | 3.5 | 4.0 | 2.5 | 3.8 | +| 24 | 7.0 | 2.5 | 2.8 | 3.2 | 2.0 | 3.5 | +| 25 | 6.0 | 2.0 | 2.2 | 2.5 | 1.5 | 3.0 | +| 26 | 5.0 | 1.5 | 1.8 | 2.0 | 1.0 | 2.5 | +| 27 | 4.2 | 1.2 | 1.5 | 1.8 | 0.8 | 2.2 | +| 28 | 3.5 | 1.0 | 1.2 | 1.5 | 0.6 | 1.8 | +| 29 | 2.8 | 0.8 | 1.0 | 1.2 | 0.5 | 1.5 | +| 30 | 2.2 | 0.6 | 0.8 | 1.0 | 0.4 | 1.2 | +| 31 | 1.8 | 0.5 | 0.6 | 0.8 | 0.3 | 1.0 | +| 32 | 1.5 | 0.4 | 0.5 | 0.6 | 0.2 | 0.8 | +| 33 | 1.2 | 0.3 | 0.4 | 0.5 | 0.1 | 0.6 | +| 34 | 1.0 | 0.2 | 0.3 | 0.4 | 0.1 | 0.5 | +| 35 | 0.8 | 0.1 | 0.2 | 0.3 | 0.0 | 0.4 | +| 36 | 0.7 | 0.1 | 0.1 | 0.2 | 0.0 | 0.3 | +| 37 | 0.6 | 0.0 | 0.1 | 0.1 | 0.0 | 0.2 | +| 38 | 0.5 | 0.0 | 0.0 | 0.1 | 0.0 | 0.1 | +| 39 | 0.4 | 0.0 | 0.0 | 0.0 | 0.0 | 0.1 | +| 40 | 0.3 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | +| 41 | 0.2 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | +| 42 | 0.1 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | +| 43 | 0.1 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | + +Line graph titled 'Throughput Loss - Average of all users in whole network - (20 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 9. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. Six lines represent different vendors: Ericsson (blue), ZTE (red), CMCC (green), Qualcomm (purple), Huawei (cyan), and CATT (orange). All lines show a downward trend as ACS increases, with Ericsson showing the highest loss and others converging near 0%. + +Figure 6.4.1.3.1-2: Simulation results for Throughput Loss – Average of all users in the whole network + +Maximum distance between ATG BS and ATG UE is 300 km + +![Line graph titled 'Throughput Loss - 5% in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' from 0 to 40. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. A single blue line with markers represents Ericsson. The line shows a steep downward trend from approximately 38% at 23 dB to about 1% at 43 dB.](ac7113ab2270f2d29fbc296fe31432b5_img.jpg) + +| ATG UE ACS (dB) | Ericsson (%) | +|-----------------|--------------| +| 23 | 38 | +| 24 | 34 | +| 25 | 30 | +| 26 | 26 | +| 27 | 22 | +| 28 | 19 | +| 29 | 16 | +| 30 | 13 | +| 31 | 11 | +| 32 | 9 | +| 33 | 7 | +| 34 | 6 | +| 35 | 5 | +| 36 | 4 | +| 37 | 3 | +| 38 | 2 | +| 39 | 2 | +| 40 | 1 | +| 41 | 1 | +| 42 | 1 | +| 43 | 1 | + +Line graph titled 'Throughput Loss - 5% in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' from 0 to 40. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. A single blue line with markers represents Ericsson. The line shows a steep downward trend from approximately 38% at 23 dB to about 1% at 43 dB. + +Figure 6.4.1.3.1-3: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph titled 'Throughput Loss - Average of all users in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' from 0 to 14. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. A blue line with circular markers represents 'Ericsson' data, showing a downward trend from approximately 13% at 23 dB to about 0.5% at 43 dB.](2d62ff2bded0c21414a0f40fdf8fd537_img.jpg) + +Throughput Loss - Average of all users in the whole network - 300km + +| ATG UE ACS (dB) | Throughput Loss (%) | +|-----------------|---------------------| +| 23 | 13.0 | +| 24 | 11.5 | +| 25 | 10.0 | +| 26 | 8.5 | +| 27 | 7.0 | +| 28 | 5.5 | +| 29 | 4.5 | +| 30 | 3.5 | +| 31 | 3.0 | +| 32 | 2.5 | +| 33 | 2.0 | +| 34 | 1.5 | +| 35 | 1.2 | +| 36 | 1.0 | +| 37 | 0.8 | +| 38 | 0.7 | +| 39 | 0.6 | +| 40 | 0.5 | +| 41 | 0.5 | +| 42 | 0.5 | +| 43 | 0.5 | + +Line graph titled 'Throughput Loss - Average of all users in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' from 0 to 14. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. A blue line with circular markers represents 'Ericsson' data, showing a downward trend from approximately 13% at 23 dB to about 0.5% at 43 dB. + +Figure 6.4.1.3.1-4: Simulation results for Throughput Loss – Average of all users in the whole network + +##### 6.4.1.3.2 Subarray model + +Maximum distance between ATG BS and ATG UE is 100 km + +![Line graph titled 'Throughput Loss - 5% in the whole network - (50 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 35. The x-axis is 'ATG UE ACS(dB)' from 23 to 43. A blue line with circular markers represents 'Ericsson' data, showing a downward trend from approximately 31% at 23 dB to about 1% at 43 dB.](cc7bd229cf6c181b389c7a43184af609_img.jpg) + +Throughput Loss - 5% in the whole network - (50 to) 100km + +| ATG UE ACS(dB) | Throughput Loss (%) | +|----------------|---------------------| +| 23 | 31.0 | +| 24 | 28.0 | +| 25 | 25.0 | +| 26 | 22.0 | +| 27 | 19.0 | +| 28 | 16.0 | +| 29 | 14.0 | +| 30 | 12.0 | +| 31 | 10.0 | +| 32 | 8.0 | +| 33 | 6.5 | +| 34 | 5.5 | +| 35 | 4.5 | +| 36 | 3.5 | +| 37 | 2.5 | +| 38 | 2.0 | +| 39 | 1.5 | +| 40 | 1.2 | +| 41 | 1.0 | +| 42 | 1.0 | +| 43 | 1.0 | + +Line graph titled 'Throughput Loss - 5% in the whole network - (50 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 35. The x-axis is 'ATG UE ACS(dB)' from 23 to 43. A blue line with circular markers represents 'Ericsson' data, showing a downward trend from approximately 31% at 23 dB to about 1% at 43 dB. + +Figure 6.4.1.3.2-1: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph titled 'Throughput Loss - Average of all users in the whole network - (50 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 12. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. A blue line with circular markers represents 'Ericsson' data, showing a downward trend from approximately 10.5% at 23 dB to about 0.5% at 43 dB.](fd8369b549b3d1a5c848cbd83659cae9_img.jpg) + +Throughput Loss - Average of all users in the whole network - (50 to) 100km + +| ATG UE ACS (dB) | Throughput Loss (%) | +|-----------------|---------------------| +| 23 | 10.5 | +| 24 | 9.2 | +| 25 | 7.8 | +| 26 | 6.5 | +| 27 | 5.5 | +| 28 | 4.8 | +| 29 | 4.0 | +| 30 | 3.5 | +| 31 | 3.0 | +| 32 | 2.5 | +| 33 | 2.0 | +| 34 | 1.8 | +| 35 | 1.5 | +| 36 | 1.2 | +| 37 | 1.0 | +| 38 | 0.8 | +| 39 | 0.7 | +| 40 | 0.6 | +| 41 | 0.5 | +| 42 | 0.5 | +| 43 | 0.5 | + +Line graph titled 'Throughput Loss - Average of all users in the whole network - (50 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 12. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. A blue line with circular markers represents 'Ericsson' data, showing a downward trend from approximately 10.5% at 23 dB to about 0.5% at 43 dB. + +Figure 6.4.1.3.2-2: Simulation results for Throughput Loss – Average of all users in the whole network + +Maximum distance between ATG BS and ATG UE is 300 km + +![Line graph titled 'Throughput Loss - 5% in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' from 0 to 60. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. A blue line with circular markers represents 'Ericsson' data, showing a downward trend from approximately 50% at 23 dB to about 2% at 43 dB.](caeb46d58919c727aa9d338ae9492077_img.jpg) + +Throughput Loss - 5% in the whole network - 300km + +| ATG UE ACS (dB) | Throughput Loss (%) | +|-----------------|---------------------| +| 23 | 50 | +| 24 | 45 | +| 25 | 40 | +| 26 | 35 | +| 27 | 31 | +| 28 | 27 | +| 29 | 24 | +| 30 | 21 | +| 31 | 18 | +| 32 | 15 | +| 33 | 12 | +| 34 | 10 | +| 35 | 8 | +| 36 | 7 | +| 37 | 6 | +| 38 | 5 | +| 39 | 4 | +| 40 | 3 | +| 41 | 2.5 | +| 42 | 2 | +| 43 | 2 | + +Line graph titled 'Throughput Loss - 5% in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' from 0 to 60. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. A blue line with circular markers represents 'Ericsson' data, showing a downward trend from approximately 50% at 23 dB to about 2% at 43 dB. + +Figure 6.4.1.3.2-3: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph showing Throughput Loss (%) vs ATG UE ACS (dB) for Ericsson. The throughput loss decreases from approximately 16.5% at 23 dB to about 1% at 43 dB.](6752cee124f693bc4cebc66180f4f91f_img.jpg) + +Throughput Loss - Average of all users in the whole network - 300km + +The graph shows a single data series for 'Ericsson' representing the average throughput loss for all users in a 300km network. The x-axis is 'ATG UE ACS (dB)' ranging from 23 to 43 in increments of 1. The y-axis is 'Throughput Loss (%)' ranging from 0 to 18 in increments of 2. The data points are connected by a blue line with circular markers. The throughput loss starts at approximately 16.5% at 23 dB and decreases steadily to about 1% at 43 dB. + +| ATG UE ACS (dB) | Throughput Loss (%) | +|-----------------|---------------------| +| 23 | 16.5 | +| 24 | 14.5 | +| 25 | 12.5 | +| 26 | 10.5 | +| 27 | 8.5 | +| 28 | 6.5 | +| 29 | 4.5 | +| 30 | 3.5 | +| 31 | 2.5 | +| 32 | 1.5 | +| 33 | 1.0 | +| 34 | 0.8 | +| 35 | 0.6 | +| 36 | 0.4 | +| 37 | 0.3 | +| 38 | 0.2 | +| 39 | 0.1 | +| 40 | 0.1 | +| 41 | 0.1 | +| 42 | 0.1 | +| 43 | 0.1 | + +Line graph showing Throughput Loss (%) vs ATG UE ACS (dB) for Ericsson. The throughput loss decreases from approximately 16.5% at 23 dB to about 1% at 43 dB. + +**Figure 6.4.1.3.2-4: Simulation results for Throughput Loss – Average of all users in the whole network** + +#### 6.4.1.4 Scenario 4: 4GHz TN UL interfering ATG UL + +This scenario captures the co-existence results after evaluation from all possible options. Here TN UL with both AAS subarray and non-subarray model is interfering ATG UL deployed in rural macro environment. + +Table 6.4.1.4-1: Simulation results for Scenario 4 – 4GHz TN UL interfering ATG UL + +| Company | ATG/ TN BS antenna model | Performance Metric | Throughput loss (%) at ATG BS ACS 46 dB | +|----------|--------------------------|-------------------------------------------|-----------------------------------------| +| Ericsson | Non-Subarray | 5% in the whole network | 1.08 | +| | | Average of all users in the whole network | 0.34 | +| | Subarray | 5% in the whole network | 0.91 | +| | | Average of all users in the whole network | 0.49 | +| ZTE | Non-Subarray | 5% in the whole network | 0.44 | +| | | Average of all users in the whole network | 0.13 | +| | Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | - | +| CMCC | Non-Subarray | 5% in the whole network | 0.93 | +| | | Average of all users in the whole network | 0.15 | +| | Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | - | +| Qualcomm | Non-Subarray | 5% in the whole network | 0 | +| | | Average of all users in the whole network | 0 | +| | Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | - | +| Huawei | Non-Subarray | 5% in the whole network | 0.22 | +| | | Average of all users in the whole network | 0 | +| | Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | - | +| CATT | Non-Subarray | 5% in the whole network | 0.27 | +| | | Average of all users in the whole network | 0.05 | +| | Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | - | + +##### 6.4.1.4.1 Non-Subarray model + +![Line graph titled 'Throughput Loss - 5% in the whole network' showing throughput loss (%) vs ATG BS ACS (dB) for six companies. Ericsson and CMCC show the highest loss, while Qualcomm shows zero loss.](6dcf3c6357538aad08b1cee84fb05985_img.jpg) + +The graph displays the throughput loss percentage for six companies (Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT) as a function of the ATG BS ACS (dB) value, ranging from 36 to 56 dB. The Y-axis represents the Throughput Loss (%) from 0 to 1.4. The X-axis represents the ATG BS ACS (dB) from 36 to 56. The data series are as follows: + +| ATG BS ACS (dB) | Ericsson (%) | ZTE (%) | CMCC (%) | Qualcomm (%) | Huawei (%) | CATT (%) | +|-----------------|--------------|---------|----------|--------------|------------|----------| +| 36 | 1.22 | 0.45 | 1.15 | 0.05 | 0.58 | 0.32 | +| 37 | 1.18 | 0.45 | 1.08 | 0.05 | 0.52 | 0.30 | +| 38 | 1.18 | 0.45 | 1.05 | 0.05 | 0.42 | 0.28 | +| 39 | 1.15 | 0.45 | 1.02 | 0.05 | 0.42 | 0.28 | +| 40 | 1.12 | 0.45 | 1.00 | 0.05 | 0.32 | 0.28 | +| 41 | 1.12 | 0.45 | 0.98 | 0.05 | 0.30 | 0.28 | +| 42 | 1.12 | 0.45 | 0.98 | 0.05 | 0.30 | 0.28 | +| 43 | 1.10 | 0.45 | 0.95 | 0.05 | 0.28 | 0.28 | +| 44 | 1.10 | 0.45 | 0.95 | 0.05 | 0.25 | 0.28 | +| 45 | 1.10 | 0.45 | 0.95 | 0.05 | 0.25 | 0.28 | +| 46 | 1.08 | 0.45 | 0.95 | 0.05 | 0.22 | 0.28 | +| 47 | 1.08 | 0.45 | 0.95 | 0.05 | - | 0.28 | +| 48 | 1.08 | 0.45 | 0.95 | 0.05 | - | 0.28 | +| 49 | 1.08 | 0.45 | 0.95 | 0.05 | - | 0.28 | +| 50 | 1.08 | 0.45 | 0.95 | 0.05 | - | 0.28 | +| 51 | - | - | 0.95 | - | - | - | +| 52 | - | - | 0.95 | - | - | - | +| 53 | - | - | 0.95 | - | - | - | +| 54 | - | - | 0.95 | - | - | - | +| 55 | - | - | 0.95 | - | - | - | +| 56 | - | - | 0.95 | - | - | - | + +Line graph titled 'Throughput Loss - 5% in the whole network' showing throughput loss (%) vs ATG BS ACS (dB) for six companies. Ericsson and CMCC show the highest loss, while Qualcomm shows zero loss. + +Figure 6.4.1.4.1-1: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph showing Throughput Loss (%) vs ATG BS ACS (dB) for average users across six vendors.](1bc1bf231ada31f57cd9f0d8791b784b_img.jpg) + +Throughput Loss - Average of all users in the whole network + +This line graph illustrates the throughput loss for the average user across a network for six different vendors. The x-axis represents the ATG BS ACS (dB) from 36 to 56, and the y-axis represents the Throughput Loss (%) from 0 to 0.45. The data series are: Ericsson (blue), ZTE (red), CMCC (green), Qualcomm (purple), Huawei (cyan), and CATT (orange). Ericsson shows the highest loss, starting at approximately 0.4% at 36 dB and slightly decreasing to about 0.34% at 50 dB. CMCC and ZTE show losses around 0.15% and 0.13% respectively, remaining relatively flat. Huawei and CATT show lower losses, starting around 0.08% and 0.06% and decreasing to near 0% by 46 dB. Qualcomm shows the lowest loss, starting around 0.03% and decreasing to 0% by 46 dB. + +| ATG BS ACS (dB) | Ericsson (%) | ZTE (%) | CMCC (%) | Qualcomm (%) | Huawei (%) | CATT (%) | +|-----------------|--------------|---------|----------|--------------|------------|----------| +| 36 | 0.40 | 0.15 | 0.18 | 0.03 | 0.08 | 0.06 | +| 37 | 0.39 | 0.14 | 0.17 | 0.02 | 0.07 | 0.05 | +| 38 | 0.38 | 0.14 | 0.16 | 0.02 | 0.07 | 0.05 | +| 39 | 0.37 | 0.13 | 0.16 | 0.02 | 0.06 | 0.05 | +| 40 | 0.36 | 0.13 | 0.16 | 0.02 | 0.06 | 0.05 | +| 41 | 0.35 | 0.13 | 0.16 | 0.01 | 0.05 | 0.05 | +| 42 | 0.35 | 0.13 | 0.16 | 0.01 | 0.05 | 0.05 | +| 43 | 0.34 | 0.13 | 0.16 | 0.01 | 0.04 | 0.05 | +| 44 | 0.34 | 0.13 | 0.16 | 0.01 | 0.04 | 0.05 | +| 45 | 0.34 | 0.13 | 0.16 | 0.01 | 0.04 | 0.05 | +| 46 | 0.34 | 0.13 | 0.16 | 0.00 | 0.00 | 0.05 | +| 47 | 0.34 | 0.13 | 0.16 | 0.00 | 0.00 | 0.05 | +| 48 | 0.34 | 0.13 | 0.16 | 0.00 | 0.00 | 0.05 | +| 49 | 0.34 | 0.13 | 0.16 | 0.00 | 0.00 | 0.05 | +| 50 | 0.34 | 0.13 | 0.16 | 0.00 | 0.00 | 0.05 | + +Line graph showing Throughput Loss (%) vs ATG BS ACS (dB) for average users across six vendors. + +Figure 6.4.1.4.1-2: Simulation results for Throughput Loss – Average of all users in the whole network + +##### 6.4.1.4.2 Subarray model + +![Line graph showing Throughput Loss (%) vs ATG BS ACS (dB) for 5% of users across six vendors, with only Ericsson data shown.](a1849005b1686d3991afbbb3970f623d_img.jpg) + +Throughput Loss - 5% in the whole network + +This line graph shows the throughput loss for 5% of the users in the network. The x-axis represents the ATG BS ACS (dB) from 36 to 56, and the y-axis represents the Throughput Loss (%) from 0.8 to 1.1. Only the Ericsson data series is plotted, showing a decrease in throughput loss from approximately 1.07% at 36 dB to about 0.91% at 50 dB. The loss decreases more sharply between 38 dB and 43 dB. + +| ATG BS ACS (dB) | Ericsson (%) | +|-----------------|--------------| +| 36 | 1.07 | +| 37 | 1.05 | +| 38 | 1.04 | +| 39 | 1.01 | +| 40 | 1.00 | +| 41 | 0.99 | +| 42 | 0.98 | +| 43 | 0.94 | +| 44 | 0.93 | +| 45 | 0.92 | +| 46 | 0.91 | +| 47 | 0.91 | +| 48 | 0.91 | +| 49 | 0.91 | +| 50 | 0.91 | + +Line graph showing Throughput Loss (%) vs ATG BS ACS (dB) for 5% of users across six vendors, with only Ericsson data shown. + +Figure 6.4.1.4.1-3: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph titled 'Throughput Loss - Average of all users in the whole network'. The y-axis is 'Throughput Loss (%)' ranging from 0.42 to 0.6. The x-axis is 'ATG BS ACS (dB)' ranging from 36 to 56. A single data series labeled 'Ericsson' shows a decreasing trend from approximately 0.58% at 36 dB to 0.48% at 50 dB.](b4b7023ccc81c5f4ebfd3ccb58361529_img.jpg) + +The graph shows the average throughput loss for all users in the network as a function of the ATG BS ACS (dB). The x-axis represents the ATG BS ACS in dB, ranging from 36 to 56. The y-axis represents the Throughput Loss in percentage, ranging from 0.42 to 0.6. The data points for the 'Ericsson' series are as follows: + +| ATG BS ACS (dB) | Throughput Loss (%) | +|-----------------|---------------------| +| 36 | 0.58 | +| 37 | 0.56 | +| 38 | 0.54 | +| 39 | 0.53 | +| 40 | 0.52 | +| 41 | 0.51 | +| 42 | 0.50 | +| 43 | 0.49 | +| 44 | 0.48 | +| 45 | 0.48 | +| 46 | 0.48 | +| 47 | 0.48 | +| 48 | 0.48 | +| 49 | 0.48 | +| 50 | 0.48 | + +Line graph titled 'Throughput Loss - Average of all users in the whole network'. The y-axis is 'Throughput Loss (%)' ranging from 0.42 to 0.6. The x-axis is 'ATG BS ACS (dB)' ranging from 36 to 56. A single data series labeled 'Ericsson' shows a decreasing trend from approximately 0.58% at 36 dB to 0.48% at 50 dB. + +**Figure 6.4.1.4.1-4: Simulation results for Throughput Loss – Average of all users in the whole network** + +#### 6.4.1.5 Scenario 9: 2GHz ATG DL interfering TN DL + +This scenario captures the co-existence results after evaluation from all possible options. Here ATG DL with both AAS subarray and non-subarray model is interfering TN DL deployed in rural macro environment. + +**Table 6.4.1.5-1: Simulation results for Scenario 9 – 2GHz ATG DL interfering TN DL** + +| Company | ATG/ TN BS antenna model | Performance Metric | Throughput loss (%) at ATG BS ACLR 45 dB | +|----------|--------------------------|------------------------------------------------------------------------------------------------|------------------------------------------| +| Ericsson | Non-Subarray | 5% in the whole network | 0.16 | +| | | Average of all users in the whole network | 0.03 | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | 5.38 | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | 0.76 | +| | Subarray | 5% in the whole network | 0.02 | +| | | Average of all users in the whole network | 0.03 | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | 1.51 | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | 0.74 | +| ZTE | Non-Subarray | 5% in the whole network | 0.06 | +| | | Average of all users in the whole network | 0.01 | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | 1.04 | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | 0.16 | +| | Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | - | +| CMCC | Non-Subarray | 5% in the whole network | 0 | +| | | Average of all users in the whole network | 0.01 | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | 1.67 | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | 0.63 | +| | Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | - | +| Qualcomm | Non-Subarray | 5% in the whole network | 0 | +| | | Average of all users in the whole network | 0 | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | 0 | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | 0 | +| | Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | - | +| Huawei | Non-Subarray | 5% in the whole network | 0.22 | +| | | Average of all users in the whole network | 0.01 | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | - | +| | Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | - | +| CATT | Non-Subarray | 5% in the whole network | 0.22 | +| | | Average of all users in the whole network | 0.02 | + +| | | | | +|--|----------|------------------------------------------------------------------------------------------------|---| +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | - | +| | Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN DL victim | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN DL victim | - | + +##### 6.4.1.5.1 Non-Subarray model + +![Line graph titled 'Throughput Loss - 5% in the whole network' showing throughput loss (%) vs ATG BS ACLR (dB) for Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT. Huawei shows the highest loss, while CMCC and Qualcomm show zero loss.](671a9a08b8506e113012e056945fd8f3_img.jpg) + +| ATG BS ACLR (dB) | Ericsson (%) | ZTE (%) | CMCC (%) | Qualcomm (%) | Huawei (%) | CATT (%) | +|------------------|--------------|---------|----------|--------------|------------|----------| +| 35 | 0.23 | 0.07 | 0.00 | 0.00 | 0.39 | 0.30 | +| 36 | 0.23 | 0.07 | 0.00 | 0.00 | 0.38 | 0.30 | +| 37 | 0.23 | 0.07 | 0.00 | 0.00 | 0.37 | 0.29 | +| 38 | 0.18 | 0.07 | 0.00 | 0.00 | 0.35 | 0.28 | +| 39 | 0.16 | 0.06 | 0.00 | 0.00 | 0.33 | 0.24 | +| 40 | 0.16 | 0.06 | 0.00 | 0.00 | 0.30 | 0.23 | +| 41 | 0.16 | 0.06 | 0.00 | 0.00 | 0.29 | 0.23 | +| 42 | 0.16 | 0.06 | 0.00 | 0.00 | 0.27 | 0.22 | +| 43 | 0.16 | 0.06 | 0.00 | 0.00 | 0.24 | 0.22 | +| 44 | 0.16 | 0.06 | 0.00 | 0.00 | 0.23 | 0.22 | +| 45 | 0.16 | 0.06 | 0.00 | 0.00 | 0.22 | 0.22 | +| 46 | 0.16 | 0.06 | 0.00 | 0.00 | 0.22 | 0.21 | +| 47 | 0.16 | 0.06 | 0.00 | 0.00 | 0.22 | 0.21 | +| 48 | 0.16 | 0.06 | 0.00 | 0.00 | 0.22 | 0.21 | +| 49 | 0.16 | 0.06 | 0.00 | 0.00 | 0.22 | 0.21 | +| 50 | 0.16 | 0.06 | 0.00 | 0.00 | 0.22 | 0.21 | +| 51 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 52 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 53 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 54 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 55 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | + +Line graph titled 'Throughput Loss - 5% in the whole network' showing throughput loss (%) vs ATG BS ACLR (dB) for Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT. Huawei shows the highest loss, while CMCC and Qualcomm show zero loss. + +Figure 6.4.1.5.1-1: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph titled 'Throughput Loss - Average of all users in the whole network'. The y-axis is 'Throughput Loss (%)' from 0 to 0.035. The x-axis is 'ATG BS ACLR (dB)' from 35 to 55. Six data series are shown: Ericsson (blue), ZTE (red), CMCC (green), Qualcomm (purple), Huawei (cyan), and CATT (orange). Ericsson starts at ~0.032% and decreases to ~0.026%. CATT starts at ~0.029% and decreases to ~0.021%. Huawei starts at ~0.028% and decreases to ~0.012%. CMCC starts at ~0.017% and decreases to ~0.012%. ZTE starts at ~0.014% and decreases to ~0.012%. Qualcomm remains at 0% throughout.](98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg) + +| ATG BS ACLR (dB) | Ericsson (%) | ZTE (%) | CMCC (%) | Qualcomm (%) | Huawei (%) | CATT (%) | +|------------------|--------------|---------|----------|--------------|------------|----------| +| 35 | 0.032 | 0.014 | 0.017 | 0.000 | 0.028 | 0.029 | +| 36 | 0.031 | 0.014 | 0.016 | 0.000 | 0.025 | 0.027 | +| 37 | 0.030 | 0.014 | 0.015 | 0.000 | 0.021 | 0.025 | +| 38 | 0.029 | 0.014 | 0.014 | 0.000 | 0.019 | 0.023 | +| 39 | 0.028 | 0.014 | 0.014 | 0.000 | 0.018 | 0.022 | +| 40 | 0.028 | 0.014 | 0.014 | 0.000 | 0.014 | 0.022 | +| 41 | 0.027 | 0.013 | 0.013 | 0.000 | 0.013 | 0.021 | +| 42 | 0.027 | 0.013 | 0.013 | 0.000 | 0.013 | 0.021 | +| 43 | 0.027 | 0.013 | 0.013 | 0.000 | 0.013 | 0.021 | +| 44 | 0.026 | 0.013 | 0.013 | 0.000 | 0.013 | 0.021 | +| 45 | 0.026 | 0.013 | 0.013 | 0.000 | 0.012 | 0.021 | +| 46 | 0.026 | 0.013 | 0.013 | 0.000 | 0.013 | 0.021 | +| 47 | 0.026 | 0.013 | 0.013 | 0.000 | 0.013 | 0.021 | +| 48 | 0.026 | 0.013 | 0.013 | 0.000 | 0.013 | 0.021 | +| 49 | 0.026 | 0.013 | 0.013 | 0.000 | 0.013 | 0.021 | +| 50 | 0.026 | 0.013 | 0.013 | 0.000 | 0.013 | 0.021 | + +Line graph titled 'Throughput Loss - Average of all users in the whole network'. The y-axis is 'Throughput Loss (%)' from 0 to 0.035. The x-axis is 'ATG BS ACLR (dB)' from 35 to 55. Six data series are shown: Ericsson (blue), ZTE (red), CMCC (green), Qualcomm (purple), Huawei (cyan), and CATT (orange). Ericsson starts at ~0.032% and decreases to ~0.026%. CATT starts at ~0.029% and decreases to ~0.021%. Huawei starts at ~0.028% and decreases to ~0.012%. CMCC starts at ~0.017% and decreases to ~0.012%. ZTE starts at ~0.014% and decreases to ~0.012%. Qualcomm remains at 0% throughout. + +Figure 6.4.1.5.1-2: Simulation results for Throughput Loss – Average of all users in the whole network + +![Line graph titled 'Throughput Loss - 5% of users within cell of largest throughput loss of victim network'. The y-axis is 'Throughput Loss (%)' from 0 to 6. The x-axis is 'ATG BS ACLR (dB)' from 35 to 55. Four data series are shown: Ericsson (blue), ZTE (red), CMCC (green), and Qualcomm (purple). Ericsson is constant at ~5.5%. CMCC starts at ~2.5% and decreases to ~1.6%. ZTE is constant at ~1.1%. Qualcomm is constant at 0%.](293fb0a508d182b518ea429927dfd343_img.jpg) + +| ATG BS ACLR (dB) | Ericsson (%) | ZTE (%) | CMCC (%) | Qualcomm (%) | +|------------------|--------------|---------|----------|--------------| +| 35 | 5.5 | 1.1 | 2.5 | 0.0 | +| 36 | 5.5 | 1.1 | 2.3 | 0.0 | +| 37 | 5.5 | 1.1 | 2.2 | 0.0 | +| 38 | 5.5 | 1.1 | 2.1 | 0.0 | +| 39 | 5.5 | 1.1 | 2.0 | 0.0 | +| 40 | 5.5 | 1.1 | 1.9 | 0.0 | +| 41 | 5.5 | 1.1 | 1.8 | 0.0 | +| 42 | 5.5 | 1.1 | 1.8 | 0.0 | +| 43 | 5.5 | 1.1 | 1.7 | 0.0 | +| 44 | 5.5 | 1.1 | 1.7 | 0.0 | +| 45 | 5.5 | 1.1 | 1.7 | 0.0 | +| 46 | 5.5 | 1.1 | 1.7 | 0.0 | +| 47 | 5.5 | 1.1 | 1.7 | 0.0 | +| 48 | 5.5 | 1.1 | 1.7 | 0.0 | +| 49 | 5.5 | 1.1 | 1.7 | 0.0 | +| 50 | 5.5 | 1.1 | 1.7 | 0.0 | + +Line graph titled 'Throughput Loss - 5% of users within cell of largest throughput loss of victim network'. The y-axis is 'Throughput Loss (%)' from 0 to 6. The x-axis is 'ATG BS ACLR (dB)' from 35 to 55. Four data series are shown: Ericsson (blue), ZTE (red), CMCC (green), and Qualcomm (purple). Ericsson is constant at ~5.5%. CMCC starts at ~2.5% and decreases to ~1.6%. ZTE is constant at ~1.1%. Qualcomm is constant at 0%. + +Figure 6.4.1.5.1-3: Simulation results for Throughput Loss – 5% of users within cell of largest throughput loss of victim network + +![Line graph titled 'Throughput Loss - Average of all the users within cell of largest throughput loss of victim network'. The y-axis is 'Throughput Loss (%)' from 0 to 1. The x-axis is 'ATG BS ACLR (dB)' from 35 to 55. Four lines represent Ericsson (blue), ZTE (red), CMCC (green), and Qualcomm (purple). Ericsson starts at ~0.9% and decreases to ~0.75%. ZTE starts at ~0.2% and decreases to ~0.1%. CMCC starts at ~0.85% and decreases to ~0.6%. Qualcomm stays at 0%.](9c888dd6588358989047de6ced8b2bdb_img.jpg) + +| ATG BS ACLR (dB) | Ericsson (%) | ZTE (%) | CMCC (%) | Qualcomm (%) | +|------------------|--------------|---------|----------|--------------| +| 35 | 0.9 | 0.2 | 0.85 | 0 | +| 36 | 0.88 | 0.19 | 0.8 | 0 | +| 37 | 0.86 | 0.18 | 0.75 | 0 | +| 38 | 0.84 | 0.17 | 0.72 | 0 | +| 39 | 0.82 | 0.16 | 0.7 | 0 | +| 40 | 0.81 | 0.16 | 0.68 | 0 | +| 41 | 0.8 | 0.16 | 0.67 | 0 | +| 42 | 0.79 | 0.16 | 0.66 | 0 | +| 43 | 0.78 | 0.16 | 0.65 | 0 | +| 44 | 0.77 | 0.16 | 0.64 | 0 | +| 45 | 0.76 | 0.16 | 0.63 | 0 | +| 46 | 0.75 | 0.16 | 0.62 | 0 | +| 47 | 0.75 | 0.16 | 0.62 | 0 | +| 48 | 0.75 | 0.16 | 0.62 | 0 | +| 49 | 0.75 | 0.16 | 0.62 | 0 | +| 50 | 0.75 | 0.16 | 0.62 | 0 | +| 51 | - | 0.13 | 0.61 | - | +| 52 | - | 0.13 | 0.61 | - | +| 53 | - | 0.13 | 0.61 | - | +| 54 | - | 0.13 | 0.61 | - | +| 55 | - | 0.13 | 0.61 | - | + +Line graph titled 'Throughput Loss - Average of all the users within cell of largest throughput loss of victim network'. The y-axis is 'Throughput Loss (%)' from 0 to 1. The x-axis is 'ATG BS ACLR (dB)' from 35 to 55. Four lines represent Ericsson (blue), ZTE (red), CMCC (green), and Qualcomm (purple). Ericsson starts at ~0.9% and decreases to ~0.75%. ZTE starts at ~0.2% and decreases to ~0.1%. CMCC starts at ~0.85% and decreases to ~0.6%. Qualcomm stays at 0%. + +Figure 6.4.1.5.1-4: Simulation results for Throughput Loss – Average of all users within cell of largest throughput loss of victim network + +##### 6.4.1.5.2 Subarray model + +![Line graph titled 'Throughput Loss - 5% in the whole network'. The y-axis is 'Throughput Loss (%)' from 0 to 0.08. The x-axis is 'ATG BS ACLR (dB)' from 35 to 55. A single blue line represents Ericsson. The throughput loss starts at ~0.075% at 35 dB, drops to ~0.05% at 36 dB, ~0.035% at 38 dB, and stabilizes at ~0.022% from 40 dB onwards.](ddfefccc6c2fcfadf4e398109548faf8_img.jpg) + +| ATG BS ACLR (dB) | Ericsson (%) | +|------------------|--------------| +| 35 | 0.075 | +| 36 | 0.05 | +| 37 | 0.05 | +| 38 | 0.035 | +| 39 | 0.035 | +| 40 | 0.022 | +| 41 | 0.022 | +| 42 | 0.022 | +| 43 | 0.022 | +| 44 | 0.022 | +| 45 | 0.022 | +| 46 | 0.022 | +| 47 | 0.022 | +| 48 | 0.022 | +| 49 | 0.022 | +| 50 | 0.022 | + +Line graph titled 'Throughput Loss - 5% in the whole network'. The y-axis is 'Throughput Loss (%)' from 0 to 0.08. The x-axis is 'ATG BS ACLR (dB)' from 35 to 55. A single blue line represents Ericsson. The throughput loss starts at ~0.075% at 35 dB, drops to ~0.05% at 36 dB, ~0.035% at 38 dB, and stabilizes at ~0.022% from 40 dB onwards. + +Figure 6.4.1.5.2-1: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph showing Throughput Loss (%) vs ATG BS ACLR (dB) for the average of all users in the whole network. The y-axis ranges from 0 to 0.04 with increments of 0.005. The x-axis ranges from 35 to 55 dB with increments of 1 dB. A single data series for Ericsson shows a gradual decrease in throughput loss from approximately 0.035% at 35 dB to about 0.027% at 50 dB.](e0113695dbf148bf5ec34354e544414b_img.jpg) + +Throughput Loss - Average of all users in the whole network + +| ATG BS ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 35 | 0.035 | +| 36 | 0.033 | +| 37 | 0.032 | +| 38 | 0.031 | +| 39 | 0.030 | +| 40 | 0.030 | +| 41 | 0.029 | +| 42 | 0.029 | +| 43 | 0.028 | +| 44 | 0.028 | +| 45 | 0.028 | +| 46 | 0.028 | +| 47 | 0.028 | +| 48 | 0.028 | +| 49 | 0.028 | +| 50 | 0.028 | + +ATG BS ACLR (dB) + +Ericsson + +Line graph showing Throughput Loss (%) vs ATG BS ACLR (dB) for the average of all users in the whole network. The y-axis ranges from 0 to 0.04 with increments of 0.005. The x-axis ranges from 35 to 55 dB with increments of 1 dB. A single data series for Ericsson shows a gradual decrease in throughput loss from approximately 0.035% at 35 dB to about 0.027% at 50 dB. + +Figure 6.4.1.5.2-2: Simulation results for Throughput Loss – Average of all users in the whole network + +![Line graph showing Throughput Loss (%) vs ATG BS ACLR (dB) for 5% of users within the cell of largest throughput loss of the victim network. The y-axis ranges from 0 to 3 with increments of 0.5. The x-axis ranges from 35 to 55 dB with increments of 1 dB. A single data series for Ericsson shows a sharp drop in throughput loss from approximately 2.8% at 35 dB to about 1.5% at 37 dB, remaining constant thereafter.](3179e999cb73ab07fad8e9407c88a3b6_img.jpg) + +Throughput Loss - 5% of users within cell of largest throughput loss of victim network + +| ATG BS ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 35 | 2.8 | +| 36 | 2.1 | +| 37 | 1.5 | +| 38 | 1.5 | +| 39 | 1.5 | +| 40 | 1.5 | +| 41 | 1.5 | +| 42 | 1.5 | +| 43 | 1.5 | +| 44 | 1.5 | +| 45 | 1.5 | +| 46 | 1.5 | +| 47 | 1.5 | +| 48 | 1.5 | +| 49 | 1.5 | +| 50 | 1.5 | + +ATG BS ACLR (dB) + +Ericsson + +Line graph showing Throughput Loss (%) vs ATG BS ACLR (dB) for 5% of users within the cell of largest throughput loss of the victim network. The y-axis ranges from 0 to 3 with increments of 0.5. The x-axis ranges from 35 to 55 dB with increments of 1 dB. A single data series for Ericsson shows a sharp drop in throughput loss from approximately 2.8% at 35 dB to about 1.5% at 37 dB, remaining constant thereafter. + +Figure 6.4.1.5.2-3: Simulation results for Throughput Loss – 5% of users within cell of largest throughput loss of victim network + +![Line graph showing Throughput Loss (%) vs ATG BS ACLR (dB) for Ericsson. The throughput loss starts at approximately 0.9% at 35 dB ACLR and decreases to about 0.75% at 50 dB ACLR.](7b96fce298a23fd76a01ff6c176c1059_img.jpg) + +Throughput Loss - Average of all users within cell of largest throughput loss of victim network + +| ATG BS ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 35 | 0.9 | +| 36 | 0.88 | +| 37 | 0.85 | +| 38 | 0.82 | +| 39 | 0.8 | +| 40 | 0.78 | +| 41 | 0.77 | +| 42 | 0.76 | +| 43 | 0.75 | +| 44 | 0.75 | +| 45 | 0.75 | +| 46 | 0.75 | +| 47 | 0.75 | +| 48 | 0.75 | +| 49 | 0.75 | +| 50 | 0.75 | + +Line graph showing Throughput Loss (%) vs ATG BS ACLR (dB) for Ericsson. The throughput loss starts at approximately 0.9% at 35 dB ACLR and decreases to about 0.75% at 50 dB ACLR. + +**Figure 6.4.1.5.2-4: Simulation results for Throughput Loss – Average of all users within cell of largest throughput loss of victim network** + +#### 6.4.1.6 Scenario 10: 2GHz ATG UL interfering TN UL + +This scenario captures the co-existence results after evaluation from all possible options. Here ATG UL with both AAS subarray and non-subarray model is interfering TN UL deployed in rural macro environment. + +**Table 6.4.1.6-1: Simulation results for Scenario 10 – 2GHz ATG UL interfering TN UL** + +| Company | ATG/ TN BS antenna model | Performance Metric | Throughput loss (%) at ATG UE ACLR 30 dB | | +|----------|--------------------------|------------------------------------------------------------------------------------------------|--------------------------------------------|--------| +| | | | Maximum distance between ATG BS and ATG UE | | +| | | | 100 km | 300 km | +| Ericsson | Non-Subarray | 5% in the whole network | 0.02 | 0.32 | +| | | Average of all users in the whole network | 0.04 | 0.20 | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | 1.00 | 4.38 | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | 0.07 | 0.37 | +| | Subarray | 5% in the whole network | 0.13 | 0.42 | +| | | Average of all users in the whole network | 0.02 | 0.14 | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | 0.79 | 3.84 | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | 0.04 | 0.28 | +| ZTE | Non-Subarray | 5% in the whole network | 0.01 | - | +| | | Average of all users in the whole network | 0.003 | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| | Subarray | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| CMCC | Non-Subarray | 5% in the whole network | 0.07 | - | +| | | Average of all users in the whole network | 0.07 | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | 10.95 | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | 1.60 | - | +| | Subarray | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| Qualcomm | Non-Subarray | 5% in the whole network | 0.004 | - | +| | | Average of all users in the whole network | 0.001 | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | 0.005 | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | 0.003 | - | +| | Subarray | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| Huawei | Non-Subarray | 5% in the whole network | 0 | - | +| | | Average of all users in the whole network | 0.02 | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | 0.03 | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | 0.003 | - | +| | Subarray | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | + +| | | | | | +|------|--------------|------------------------------------------------------------------------------------------------|---|---| +| CATT | Non-Subarray | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| | | 5% in the whole network | 0 | - | +| | | Average of all users in the whole network | 0 | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| | Subarray | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | +| | | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | + +##### 6.4.1.6.1 Non-Subarray model + +Maximum distance between ATG BS and ATG UE is 100 km + +![Line graph titled 'Throughput Loss - 5% in the whole network - (20 to) 100km'. The Y-axis is 'Throughput Loss (%)' from 0 to 0.8. The X-axis is 'ATG UE ACLR (dB)' from 20 to 40. Six lines represent different vendors: Ericsson (blue), ZTE (red), CMCC (green), Qualcomm (purple), Huawei (cyan), and CATT (orange). CMCC shows the highest throughput loss, starting at ~0.7% at 20 dB and decreasing to ~0.02% at 40 dB. Ericsson starts at ~0.7% and decreases to ~0.01%. ZTE, Qualcomm, Huawei, and CATT all show very low throughput loss, remaining near 0% across the entire range.](70546cb98239089866510133c7fbc169_img.jpg) + +| ATG UE ACLR (dB) | Ericsson (%) | ZTE (%) | CMCC (%) | Qualcomm (%) | Huawei (%) | CATT (%) | +|------------------|--------------|---------|----------|--------------|------------|----------| +| 20 | 0.70 | 0.08 | 0.70 | 0.05 | 0.05 | 0.01 | +| 21 | 0.55 | 0.05 | 0.55 | 0.04 | 0.04 | 0.01 | +| 22 | 0.35 | 0.03 | 0.45 | 0.03 | 0.03 | 0.01 | +| 23 | 0.25 | 0.02 | 0.35 | 0.02 | 0.02 | 0.01 | +| 24 | 0.18 | 0.01 | 0.28 | 0.01 | 0.01 | 0.01 | +| 25 | 0.15 | 0.01 | 0.22 | 0.01 | 0.01 | 0.01 | +| 26 | 0.10 | 0.01 | 0.18 | 0.01 | 0.01 | 0.01 | +| 27 | 0.08 | 0.01 | 0.14 | 0.01 | 0.01 | 0.01 | +| 28 | 0.06 | 0.01 | 0.11 | 0.01 | 0.01 | 0.01 | +| 29 | 0.04 | 0.01 | 0.09 | 0.01 | 0.01 | 0.01 | +| 30 | 0.03 | 0.01 | 0.07 | 0.01 | 0.01 | 0.01 | +| 31 | 0.02 | 0.01 | 0.06 | 0.01 | 0.01 | 0.01 | +| 32 | 0.02 | 0.01 | 0.05 | 0.01 | 0.01 | 0.01 | +| 33 | 0.01 | 0.01 | 0.04 | 0.01 | 0.01 | 0.01 | +| 34 | 0.01 | 0.01 | 0.03 | 0.01 | 0.01 | 0.01 | +| 35 | 0.01 | 0.01 | 0.02 | 0.01 | 0.01 | 0.01 | +| 36 | 0.01 | 0.01 | 0.02 | 0.01 | 0.01 | 0.01 | +| 37 | 0.01 | 0.01 | 0.01 | 0.01 | 0.01 | 0.01 | +| 38 | 0.01 | 0.01 | 0.01 | 0.01 | 0.01 | 0.01 | +| 39 | 0.01 | 0.01 | 0.01 | 0.01 | 0.01 | 0.01 | +| 40 | 0.01 | 0.01 | 0.01 | 0.01 | 0.01 | 0.01 | + +Line graph titled 'Throughput Loss - 5% in the whole network - (20 to) 100km'. The Y-axis is 'Throughput Loss (%)' from 0 to 0.8. The X-axis is 'ATG UE ACLR (dB)' from 20 to 40. Six lines represent different vendors: Ericsson (blue), ZTE (red), CMCC (green), Qualcomm (purple), Huawei (cyan), and CATT (orange). CMCC shows the highest throughput loss, starting at ~0.7% at 20 dB and decreasing to ~0.02% at 40 dB. Ericsson starts at ~0.7% and decreases to ~0.01%. ZTE, Qualcomm, Huawei, and CATT all show very low throughput loss, remaining near 0% across the entire range. + +Figure 6.4.1.6.1-1: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph titled 'Throughput Loss - Average of all users in the whole network - (20 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 0.5. The x-axis is 'ATG UE ACLR (dB)' from 20 to 40. Six data series are shown: Ericsson (blue), ZTE (red), CMCC (green), Qualcomm (purple), Huawei (cyan), and CATT (orange). CMCC shows a significant decrease in throughput loss as ACLR increases, while others remain near zero.](53d8bef47c63e0897de4cd058bad2cbd_img.jpg) + +Throughput Loss - Average of all users in the whole network - (20 to) 100km + +| ATG UE ACLR (dB) | Ericsson (%) | ZTE (%) | CMCC (%) | Qualcomm (%) | Huawei (%) | CATT (%) | +|------------------|--------------|---------|----------|--------------|------------|----------| +| 20 | 0.34 | 0.02 | 0.48 | 0.01 | 0.04 | 0.01 | +| 21 | 0.28 | 0.02 | 0.40 | 0.01 | 0.04 | 0.01 | +| 22 | 0.22 | 0.02 | 0.34 | 0.01 | 0.04 | 0.01 | +| 23 | 0.18 | 0.02 | 0.28 | 0.01 | 0.04 | 0.01 | +| 24 | 0.14 | 0.02 | 0.23 | 0.01 | 0.04 | 0.01 | +| 25 | 0.11 | 0.02 | 0.19 | 0.01 | 0.04 | 0.01 | +| 26 | 0.09 | 0.02 | 0.16 | 0.01 | 0.04 | 0.01 | +| 27 | 0.07 | 0.02 | 0.13 | 0.01 | 0.04 | 0.01 | +| 28 | 0.06 | 0.02 | 0.11 | 0.01 | 0.04 | 0.01 | +| 29 | 0.05 | 0.02 | 0.09 | 0.01 | 0.04 | 0.01 | +| 30 | 0.04 | 0.02 | 0.08 | 0.01 | 0.04 | 0.01 | +| 31 | 0.04 | 0.02 | 0.07 | 0.01 | 0.04 | 0.01 | +| 32 | 0.03 | 0.02 | 0.06 | 0.01 | 0.04 | 0.01 | +| 33 | 0.03 | 0.02 | 0.05 | 0.01 | 0.04 | 0.01 | +| 34 | 0.02 | 0.02 | 0.04 | 0.01 | 0.04 | 0.01 | +| 35 | 0.02 | 0.02 | 0.03 | 0.01 | 0.04 | 0.01 | +| 36 | 0.02 | 0.02 | 0.03 | 0.01 | 0.04 | 0.01 | +| 37 | 0.01 | 0.02 | 0.02 | 0.01 | 0.04 | 0.01 | +| 38 | 0.01 | 0.02 | 0.02 | 0.01 | 0.04 | 0.01 | +| 39 | 0.01 | 0.02 | 0.01 | 0.01 | 0.04 | 0.01 | +| 40 | 0.01 | 0.02 | 0.01 | 0.01 | 0.04 | 0.01 | + +Line graph titled 'Throughput Loss - Average of all users in the whole network - (20 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 0.5. The x-axis is 'ATG UE ACLR (dB)' from 20 to 40. Six data series are shown: Ericsson (blue), ZTE (red), CMCC (green), Qualcomm (purple), Huawei (cyan), and CATT (orange). CMCC shows a significant decrease in throughput loss as ACLR increases, while others remain near zero. + +Figure 6.4.1.6.1-2: Simulation results for Throughput Loss – Average of all users in the whole network + +![Line graph titled 'Throughput Loss - 5% of users within cell of largest throughput loss of victim network - (20 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 60. The x-axis is 'ATG UE ACLR (dB)' from 20 to 40. Four data series are shown: Ericsson (blue), CMCC (green), Qualcomm (purple), and Huawei (cyan). CMCC shows a significant decrease in throughput loss as ACLR increases, while others remain near zero.](5ae0af74768ab8a326191d61781d98e6_img.jpg) + +Throughput Loss - 5% of users within cell of largest throughput loss of victim network - (20 to) 100km + +| ATG UE ACLR (dB) | Ericsson (%) | CMCC (%) | Qualcomm (%) | Huawei (%) | +|------------------|--------------|----------|--------------|------------| +| 20 | 5 | 54 | 0 | 0 | +| 21 | 5 | 48 | 0 | 0 | +| 22 | 5 | 42 | 0 | 0 | +| 23 | 4 | 37 | 0 | 0 | +| 24 | 4 | 32 | 0 | 0 | +| 25 | 4 | 27 | 0 | 0 | +| 26 | 3 | 23 | 0 | 0 | +| 27 | 3 | 19 | 0 | 0 | +| 28 | 2 | 16 | 0 | 0 | +| 29 | 2 | 13 | 0 | 0 | +| 30 | 1 | 11 | 0 | 0 | +| 31 | 1 | 9 | 0 | 0 | +| 32 | 1 | 7 | 0 | 0 | +| 33 | 1 | 6 | 0 | 0 | +| 34 | 1 | 5 | 0 | 0 | +| 35 | 1 | 4 | 0 | 0 | +| 36 | 1 | 3 | 0 | 0 | +| 37 | 1 | 2 | 0 | 0 | +| 38 | 1 | 2 | 0 | 0 | +| 39 | 1 | 1 | 0 | 0 | +| 40 | 1 | 1 | 0 | 0 | + +Line graph titled 'Throughput Loss - 5% of users within cell of largest throughput loss of victim network - (20 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 60. The x-axis is 'ATG UE ACLR (dB)' from 20 to 40. Four data series are shown: Ericsson (blue), CMCC (green), Qualcomm (purple), and Huawei (cyan). CMCC shows a significant decrease in throughput loss as ACLR increases, while others remain near zero. + +Figure 6.4.1.6.1-3: Simulation results for Throughput Loss – 5% of users within cell of largest throughput loss of victim network + +![Line graph titled 'Throughput Loss - Average of all users within cell of largest throughput loss of victim network - (20 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 12. The x-axis is 'ATG UE ACLR (dB)' from 20 to 40. Four series are shown: Ericsson (blue), CMCC (green), Qualcomm (purple), and Huawei (cyan). CMCC shows a significant decrease from 10% at 20 dB to near 0% at 40 dB. The other three remain near 0%.](7c0a9511fa02b6c2c125ff5be465186e_img.jpg) + +| ATG UE ACLR (dB) | Ericsson (%) | CMCC (%) | Qualcomm (%) | Huawei (%) | +|------------------|--------------|----------|--------------|------------| +| 20 | 0.5 | 10.0 | 0.5 | 0.5 | +| 21 | 0.5 | 8.5 | 0.5 | 0.5 | +| 22 | 0.5 | 7.5 | 0.5 | 0.5 | +| 23 | 0.5 | 6.0 | 0.5 | 0.5 | +| 24 | 0.5 | 5.0 | 0.5 | 0.5 | +| 25 | 0.5 | 4.2 | 0.5 | 0.5 | +| 26 | 0.5 | 3.5 | 0.5 | 0.5 | +| 27 | 0.5 | 3.0 | 0.5 | 0.5 | +| 28 | 0.5 | 2.5 | 0.5 | 0.5 | +| 29 | 0.5 | 2.0 | 0.5 | 0.5 | +| 30 | 0.5 | 1.8 | 0.5 | 0.5 | +| 31 | 0.5 | 1.5 | 0.5 | 0.5 | +| 32 | 0.5 | 1.2 | 0.5 | 0.5 | +| 33 | 0.5 | 1.0 | 0.5 | 0.5 | +| 34 | 0.5 | 0.8 | 0.5 | 0.5 | +| 35 | 0.5 | 0.7 | 0.5 | 0.5 | +| 36 | 0.5 | 0.6 | 0.5 | 0.5 | +| 37 | 0.5 | 0.5 | 0.5 | 0.5 | +| 38 | 0.5 | 0.4 | 0.5 | 0.5 | +| 39 | 0.5 | 0.3 | 0.5 | 0.5 | +| 40 | 0.5 | 0.2 | 0.5 | 0.5 | + +Line graph titled 'Throughput Loss - Average of all users within cell of largest throughput loss of victim network - (20 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 12. The x-axis is 'ATG UE ACLR (dB)' from 20 to 40. Four series are shown: Ericsson (blue), CMCC (green), Qualcomm (purple), and Huawei (cyan). CMCC shows a significant decrease from 10% at 20 dB to near 0% at 40 dB. The other three remain near 0%. + +Figure 6.4.1.6.1-4: Simulation results for Throughput Loss – Average of all users within cell of largest throughput loss of victim network + +Maximum distance between ATG BS and ATG UE is 300 km + +![Line graph titled 'Throughput Loss - 5% in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' from 0 to 4. The x-axis is 'ATG UE ACLR (dB)' from 20 to 40. One series for Ericsson (blue) shows a decrease from approximately 3.6% at 20 dB to near 0% at 40 dB.](09b5a76dd3d981abcc585df1314ef30a_img.jpg) + +| ATG UE ACLR (dB) | Ericsson (%) | +|------------------|--------------| +| 20 | 3.6 | +| 21 | 3.0 | +| 22 | 2.4 | +| 23 | 1.9 | +| 24 | 1.6 | +| 25 | 1.3 | +| 26 | 1.1 | +| 27 | 0.7 | +| 28 | 0.5 | +| 29 | 0.4 | +| 30 | 0.3 | +| 31 | 0.2 | +| 32 | 0.2 | +| 33 | 0.2 | +| 34 | 0.1 | +| 35 | 0.1 | +| 36 | 0.1 | +| 37 | 0.1 | +| 38 | 0.1 | +| 39 | 0.1 | +| 40 | 0.1 | + +Line graph titled 'Throughput Loss - 5% in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' from 0 to 4. The x-axis is 'ATG UE ACLR (dB)' from 20 to 40. One series for Ericsson (blue) shows a decrease from approximately 3.6% at 20 dB to near 0% at 40 dB. + +Figure 6.4.1.6.1-5: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph titled 'Throughput Loss - Average of all users in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' from 0 to 1.8. The x-axis is 'ATG UE ACLR (dB)' from 20 to 40. A blue line with circular markers represents 'Ericsson' data, showing a decrease in throughput loss as ACLR increases.](f455955c4bc84005728b4138f19098dc_img.jpg) + +Throughput Loss - Average of all users in the whole network - 300km + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 1.6 | +| 21 | 1.3 | +| 22 | 1.1 | +| 23 | 0.9 | +| 24 | 0.7 | +| 25 | 0.6 | +| 26 | 0.5 | +| 27 | 0.4 | +| 28 | 0.3 | +| 29 | 0.25 | +| 30 | 0.2 | +| 31 | 0.18 | +| 32 | 0.15 | +| 33 | 0.12 | +| 34 | 0.1 | +| 35 | 0.08 | +| 36 | 0.07 | +| 37 | 0.06 | +| 38 | 0.05 | +| 39 | 0.04 | +| 40 | 0.03 | + +Line graph titled 'Throughput Loss - Average of all users in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' from 0 to 1.8. The x-axis is 'ATG UE ACLR (dB)' from 20 to 40. A blue line with circular markers represents 'Ericsson' data, showing a decrease in throughput loss as ACLR increases. + +Figure 6.4.1.6.1-6: Simulation results for Throughput Loss – Average of all users in the whole network + +![Line graph titled 'Throughput Loss - 5% of users within cell of largest throughput loss of victim network- 300km'. The y-axis is 'Throughput Loss (%)' from 0 to 10. The x-axis is 'ATG UE ACLR (dB)' from 20 to 40. A blue line with circular markers represents 'Ericsson' data, showing a decrease in throughput loss as ACLR increases.](67408c41c75d983c13a9bd3d66953f3c_img.jpg) + +Throughput Loss - 5% of users within cell of largest throughput loss of victim network- 300km + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 8.8 | +| 21 | 8.0 | +| 22 | 5.8 | +| 23 | 5.5 | +| 24 | 5.0 | +| 25 | 5.0 | +| 26 | 5.0 | +| 27 | 4.9 | +| 28 | 4.8 | +| 29 | 4.7 | +| 30 | 4.5 | +| 31 | 3.8 | +| 32 | 3.0 | +| 33 | 2.5 | +| 34 | 2.0 | +| 35 | 1.5 | +| 36 | 1.2 | +| 37 | 1.1 | +| 38 | 1.0 | +| 39 | 0.8 | +| 40 | 0.6 | + +Line graph titled 'Throughput Loss - 5% of users within cell of largest throughput loss of victim network- 300km'. The y-axis is 'Throughput Loss (%)' from 0 to 10. The x-axis is 'ATG UE ACLR (dB)' from 20 to 40. A blue line with circular markers represents 'Ericsson' data, showing a decrease in throughput loss as ACLR increases. + +Figure 6.4.1.6.1-7: Simulation results for Throughput Loss – 5% of users within cell of largest throughput loss of victim network + +![Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for the Ericsson model. The y-axis ranges from 0 to 3.0 in increments of 0.5. The x-axis ranges from 20 to 40 in increments of 1. The data points show a steady decrease in throughput loss as ACLR increases, starting at approximately 2.8% at 20 dB and leveling off near 0% after 38 dB.](a346e19f92f1699e3f96432c0464c957_img.jpg) + +Throughput Loss - Average of all users within cell of largest throughput loss of victim network- 300km + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 2.8 | +| 21 | 2.3 | +| 22 | 1.9 | +| 23 | 1.6 | +| 24 | 1.3 | +| 25 | 1.1 | +| 26 | 0.9 | +| 27 | 0.7 | +| 28 | 0.6 | +| 29 | 0.5 | +| 30 | 0.4 | +| 31 | 0.3 | +| 32 | 0.25 | +| 33 | 0.2 | +| 34 | 0.15 | +| 35 | 0.1 | +| 36 | 0.1 | +| 37 | 0.08 | +| 38 | 0.05 | +| 39 | 0.05 | +| 40 | 0.05 | + +Ericsson + +Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for the Ericsson model. The y-axis ranges from 0 to 3.0 in increments of 0.5. The x-axis ranges from 20 to 40 in increments of 1. The data points show a steady decrease in throughput loss as ACLR increases, starting at approximately 2.8% at 20 dB and leveling off near 0% after 38 dB. + +Figure 6.4.1.6.1-8: Simulation results for Throughput Loss – Average of all users within cell of largest throughput loss of victim network + +##### 6.4.1.6.2 Subarray model + +Maximum distance between ATG BS and ATG UE is 100 km + +![Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for the Ericsson model. The y-axis ranges from 0 to 0.6 in increments of 0.1. The x-axis ranges from 20 to 40 in increments of 1. The data points show a sharp initial drop in throughput loss from 0.48% at 20 dB to 0.25% at 23 dB, followed by a more gradual decline to near 0% by 34 dB.](1071a283fcadf8d3e2ff23b77eefd4a8_img.jpg) + +Throughput Loss - 5% in the whole network - (50 to) 100km + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 0.48 | +| 21 | 0.45 | +| 22 | 0.38 | +| 23 | 0.25 | +| 24 | 0.22 | +| 25 | 0.19 | +| 26 | 0.19 | +| 27 | 0.17 | +| 28 | 0.16 | +| 29 | 0.14 | +| 30 | 0.13 | +| 31 | 0.06 | +| 32 | 0.04 | +| 33 | 0.03 | +| 34 | 0.01 | +| 35 | 0.01 | +| 36 | 0.01 | +| 37 | 0.01 | +| 38 | 0.01 | +| 39 | 0.01 | +| 40 | 0.01 | + +Ericsson + +Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for the Ericsson model. The y-axis ranges from 0 to 0.6 in increments of 0.1. The x-axis ranges from 20 to 40 in increments of 1. The data points show a sharp initial drop in throughput loss from 0.48% at 20 dB to 0.25% at 23 dB, followed by a more gradual decline to near 0% by 34 dB. + +Figure 6.4.1.6.2-1: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for the average of all users in the whole network. The y-axis ranges from 0 to 0.2, and the x-axis ranges from 20 to 40 dB. The data points show a decreasing trend from approximately 0.17% at 20 dB to 0.01% at 40 dB.](b90dcb4c35f1875e19ca312a6cf4adae_img.jpg) + +Throughput Loss - Average of all users in the whole network - (50 to) 100km + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 0.17 | +| 21 | 0.14 | +| 22 | 0.11 | +| 23 | 0.09 | +| 24 | 0.07 | +| 25 | 0.06 | +| 26 | 0.05 | +| 27 | 0.04 | +| 28 | 0.03 | +| 29 | 0.025 | +| 30 | 0.02 | +| 31 | 0.018 | +| 32 | 0.016 | +| 33 | 0.014 | +| 34 | 0.012 | +| 35 | 0.011 | +| 36 | 0.01 | +| 37 | 0.009 | +| 38 | 0.008 | +| 39 | 0.007 | +| 40 | 0.006 | + +Legend: Ericsson + +Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for the average of all users in the whole network. The y-axis ranges from 0 to 0.2, and the x-axis ranges from 20 to 40 dB. The data points show a decreasing trend from approximately 0.17% at 20 dB to 0.01% at 40 dB. + +Figure 6.4.1.6.2-2: Simulation results for Throughput Loss – Average of all users in the whole network + +![Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for 5% of users within cell of largest throughput loss of victim network. The y-axis ranges from 0 to 4.5, and the x-axis ranges from 20 to 40 dB. The data points show a decreasing trend from approximately 3.8% at 20 dB to 0.1% at 40 dB.](02c999e5846341813b658e446e9a6fda_img.jpg) + +Throughput Loss - 5% of users within cell of largest throughput loss of victim network - (50 to) 100km + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 3.8 | +| 21 | 3.8 | +| 22 | 3.3 | +| 23 | 2.2 | +| 24 | 2.2 | +| 25 | 2.2 | +| 26 | 2.0 | +| 27 | 1.6 | +| 28 | 1.3 | +| 29 | 1.0 | +| 30 | 0.8 | +| 31 | 0.6 | +| 32 | 0.5 | +| 33 | 0.4 | +| 34 | 0.35 | +| 35 | 0.3 | +| 36 | 0.25 | +| 37 | 0.2 | +| 38 | 0.15 | +| 39 | 0.1 | +| 40 | 0.05 | + +Legend: Ericsson + +Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for 5% of users within cell of largest throughput loss of victim network. The y-axis ranges from 0 to 4.5, and the x-axis ranges from 20 to 40 dB. The data points show a decreasing trend from approximately 3.8% at 20 dB to 0.1% at 40 dB. + +Figure 6.4.1.6.2-3: Simulation results for Throughput Loss – 5% of users within cell of largest throughput loss of victim network + +![Line graph titled 'Throughput Loss - Average of all users within cell of largest throughput loss of victim network - (50 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 0.35. The x-axis is 'ATG UE ACLR (dB)' from 20 to 40. A blue line with circular markers represents 'Ericsson' data, showing a decrease in throughput loss as ACLR increases.](9e4179ffe4701bec67534299c4935049_img.jpg) + +Throughput Loss - Average of all users within cell of largest throughput loss of victim network - (50 to) 100km + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 0.33 | +| 21 | 0.27 | +| 22 | 0.22 | +| 23 | 0.18 | +| 24 | 0.15 | +| 25 | 0.12 | +| 26 | 0.10 | +| 27 | 0.08 | +| 28 | 0.06 | +| 29 | 0.05 | +| 30 | 0.04 | +| 31 | 0.03 | +| 32 | 0.02 | +| 33 | 0.02 | +| 34 | 0.01 | +| 35 | 0.01 | +| 36 | 0.01 | +| 37 | 0.01 | +| 38 | 0.01 | +| 39 | 0.01 | +| 40 | 0.01 | + +Line graph titled 'Throughput Loss - Average of all users within cell of largest throughput loss of victim network - (50 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 0.35. The x-axis is 'ATG UE ACLR (dB)' from 20 to 40. A blue line with circular markers represents 'Ericsson' data, showing a decrease in throughput loss as ACLR increases. + +Figure 6.4.1.6.2-4: Simulation results for Throughput Loss – Average of all users within cell of largest throughput loss of victim network + +Maximum distance between ATG BS and ATG UE is 300 km + +![Line graph titled 'Throughput Loss - 5% in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' from 0 to 3.5. The x-axis is 'ATG UE ACLR (dB)' from 20 to 40. A blue line with circular markers represents 'Ericsson' data, showing a decrease in throughput loss as ACLR increases.](68d47da43cdd5782cac97f784b52c270_img.jpg) + +Throughput Loss - 5% in the whole network - 300km + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 2.9 | +| 21 | 2.4 | +| 22 | 1.8 | +| 23 | 1.4 | +| 24 | 1.2 | +| 25 | 1.0 | +| 26 | 0.8 | +| 27 | 0.7 | +| 28 | 0.6 | +| 29 | 0.5 | +| 30 | 0.4 | +| 31 | 0.3 | +| 32 | 0.2 | +| 33 | 0.2 | +| 34 | 0.2 | +| 35 | 0.2 | +| 36 | 0.2 | +| 37 | 0.2 | +| 38 | 0.2 | +| 39 | 0.2 | +| 40 | 0.1 | + +Line graph titled 'Throughput Loss - 5% in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' from 0 to 3.5. The x-axis is 'ATG UE ACLR (dB)' from 20 to 40. A blue line with circular markers represents 'Ericsson' data, showing a decrease in throughput loss as ACLR increases. + +Figure 6.4.1.6.2-5: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for the average of all users in the whole network at 300km. The y-axis ranges from 0 to 1.2, and the x-axis ranges from 20 to 40. The data points show a decreasing trend from approximately 1.05% at 20 dB to 0.05% at 40 dB.](89b3389b2c4fa1b452cf2b5daa5f82ad_img.jpg) + +Throughput Loss - Average of all users in the whole network - 300km + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 1.05 | +| 21 | 0.90 | +| 22 | 0.75 | +| 23 | 0.60 | +| 24 | 0.50 | +| 25 | 0.40 | +| 26 | 0.35 | +| 27 | 0.30 | +| 28 | 0.25 | +| 29 | 0.20 | +| 30 | 0.18 | +| 31 | 0.15 | +| 32 | 0.12 | +| 33 | 0.10 | +| 34 | 0.08 | +| 35 | 0.07 | +| 36 | 0.06 | +| 37 | 0.05 | +| 38 | 0.04 | +| 39 | 0.03 | +| 40 | 0.02 | + +Ericsson + +Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for the average of all users in the whole network at 300km. The y-axis ranges from 0 to 1.2, and the x-axis ranges from 20 to 40. The data points show a decreasing trend from approximately 1.05% at 20 dB to 0.05% at 40 dB. + +Figure 6.4.1.6.2-6: Simulation results for Throughput Loss – Average of all users in the whole network + +![Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for 5% of users within the cell of largest throughput loss of victim network at 300km. The y-axis ranges from 0 to 12, and the x-axis ranges from 20 to 40. The data points show a decreasing trend from approximately 10.5% at 20 dB to 0.5% at 40 dB.](ad406eca7668ea7128dba19ec32a22ac_img.jpg) + +Throughput Loss - 5% of users within cell of largest throughput loss of victim network - 300km + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 10.5 | +| 21 | 9.5 | +| 22 | 9.5 | +| 23 | 8.0 | +| 24 | 8.0 | +| 25 | 7.0 | +| 26 | 5.5 | +| 27 | 4.5 | +| 28 | 4.2 | +| 29 | 3.8 | +| 30 | 3.8 | +| 31 | 3.8 | +| 32 | 3.8 | +| 33 | 2.5 | +| 34 | 2.0 | +| 35 | 1.5 | +| 36 | 1.5 | +| 37 | 1.0 | +| 38 | 0.8 | +| 39 | 0.6 | +| 40 | 0.5 | + +Ericsson + +Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for 5% of users within the cell of largest throughput loss of victim network at 300km. The y-axis ranges from 0 to 12, and the x-axis ranges from 20 to 40. The data points show a decreasing trend from approximately 10.5% at 20 dB to 0.5% at 40 dB. + +Figure 6.4.1.6.2-7: Simulation results for Throughput Loss – 5% of users within cell of largest throughput loss of victim network + +![Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for Ericsson simulation. The throughput loss decreases from approximately 1.9% at 20 dB to 0% at 40 dB.](449dd9d482c5b47f1c013ce3e18b09e6_img.jpg) + +The graph is titled "Throughput Loss - Average of all users within cell of largest throughput loss of victim network - 300km". The y-axis is labeled "Throughput Loss (%)" and ranges from 0 to 2.5 with major ticks every 0.5 units. The x-axis is labeled "ATG UE ACLR (dB)" and ranges from 20 to 40 with major ticks every 1 unit. A single data series named "Ericsson" is plotted as a blue line with circular markers. The data points show a steady decrease in throughput loss as the ATG UE ACLR increases, starting at approximately 1.9% at 20 dB and reaching 0% at 40 dB. + +| ATG UE ACLR (dB) | Throughput Loss (%) | +|------------------|---------------------| +| 20 | 1.9 | +| 21 | 1.6 | +| 22 | 1.3 | +| 23 | 1.1 | +| 24 | 0.9 | +| 25 | 0.7 | +| 26 | 0.6 | +| 27 | 0.5 | +| 28 | 0.4 | +| 29 | 0.3 | +| 30 | 0.3 | +| 31 | 0.2 | +| 32 | 0.2 | +| 33 | 0.2 | +| 34 | 0.1 | +| 35 | 0.1 | +| 36 | 0.1 | +| 37 | 0.1 | +| 38 | 0.1 | +| 39 | 0.1 | +| 40 | 0.1 | + +Line graph showing Throughput Loss (%) vs ATG UE ACLR (dB) for Ericsson simulation. The throughput loss decreases from approximately 1.9% at 20 dB to 0% at 40 dB. + +**Figure 6.4.1.6.2-8: Simulation results for Throughput Loss – Average of all users within cell of largest throughput loss of victim network** + +#### 6.4.1.7 Scenario 11: 2GHz TN DL interfering ATG DL + +This scenario captures the co-existence results after evaluation from all possible options. Here TN DL with both AAS subarray and non-subarray model is interfering ATG DL deployed in rural macro environment. + +Table 6.4.1.7-1: Simulation results for Scenario 11 – 2GHz TN DL interfering ATG DL + +| Company | ATG/ TN BS antenna model | Performance Metric | Throughput Loss (%) at ATG UE ACS 33 dB | | +|----------|--------------------------|-------------------------------------------|--------------------------------------------|--------| +| | | | Maximum distance between ATG BS and ATG UE | | +| | | | 100 km | 300 km | +| Ericsson | Non-Subarray | 5% in the whole network | 3.62 | 7.85 | +| | | Average of all users in the whole network | 2.45 | 3.92 | +| | Subarray | 5% in the whole network | 3.45 | 8.21 | +| | | Average of all users in the whole network | 2.59 | 4.08 | +| ZTE | Non-Subarray | 5% in the whole network | 1.45 | - | +| | | Average of all users in the whole network | 0.75 | - | +| | Subarray | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | +| CMCC | Non-Subarray | 5% in the whole network | 13.52 | - | +| | | Average of all users in the whole network | 3.23 | - | +| | Subarray | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | +| Qualcomm | Non-Subarray | 5% in the whole network | 2.07 | - | +| | | Average of all users in the whole network | 0.90 | - | +| | Subarray | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | +| Huawei | Non-Subarray | 5% in the whole network | 1.36 | - | +| | | Average of all users in the whole network | 1.03 | - | +| | Subarray | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | +| CATT | Non-Subarray | 5% in the whole network | 5.32 | - | +| | | Average of all users in the whole network | 0.86 | - | +| | Subarray | 5% in the whole network | - | - | +| | | Average of all users in the whole network | - | - | + +##### 6.4.1.7.1 Non-Subarray model + +Maximum distance between ATG BS and ATG UE is 100 km + +![Line graph titled 'Throughput Loss - 5% in the whole network - (20 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 50. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. Six lines represent Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT. CMCC shows the highest loss, starting at ~43% and ending at ~3%. Ericsson starts at ~26% and ends at ~1%. ZTE, Qualcomm, Huawei, and CATT all start between 13% and 20% and converge to ~1% at 43 dB.](c21fe89d8034ec5b80bd47c1cd710202_img.jpg) + +| ATG UE ACS (dB) | Ericsson (%) | ZTE (%) | CMCC (%) | Qualcomm (%) | Huawei (%) | CATT (%) | +|-----------------|--------------|---------|----------|--------------|------------|----------| +| 23 | 26 | 13 | 43 | 18 | 11 | 20 | +| 24 | 23 | 11 | 40 | 15 | 10 | 18 | +| 25 | 20 | 9 | 36 | 13 | 9 | 16 | +| 26 | 17 | 7 | 33 | 10 | 8 | 14 | +| 27 | 14 | 6 | 29 | 9 | 7 | 12 | +| 28 | 12 | 5 | 26 | 8 | 6 | 11 | +| 29 | 10 | 4 | 23 | 7 | 5 | 10 | +| 30 | 8 | 3 | 20 | 6 | 4 | 9 | +| 31 | 7 | 3 | 18 | 5 | 3 | 8 | +| 32 | 6 | 2 | 16 | 4 | 3 | 7 | +| 33 | 5 | 2 | 14 | 3 | 2 | 6 | +| 34 | 4 | 1 | 12 | 2 | 2 | 5 | +| 35 | 3 | 1 | 10 | 1 | 1 | 4 | +| 36 | 2 | 1 | 9 | 1 | 1 | 3 | +| 37 | 1 | 1 | 8 | 1 | 1 | 2 | +| 38 | 1 | 1 | 7 | 1 | 1 | 2 | +| 39 | 1 | 1 | 6 | 1 | 1 | 1 | +| 40 | 1 | 1 | 5 | 1 | 1 | 1 | +| 41 | 1 | 1 | 4 | 1 | 1 | 1 | +| 42 | 1 | 1 | 3 | 1 | 1 | 1 | +| 43 | 1 | 1 | 3 | 1 | 1 | 1 | + +Line graph titled 'Throughput Loss - 5% in the whole network - (20 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 50. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. Six lines represent Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT. CMCC shows the highest loss, starting at ~43% and ending at ~3%. Ericsson starts at ~26% and ends at ~1%. ZTE, Qualcomm, Huawei, and CATT all start between 13% and 20% and converge to ~1% at 43 dB. + +Figure 6.4.1.7.1-1: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph titled 'Throughput Loss - Average of all users in the whole network - (20 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 16. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. Six lines represent Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT. CMCC shows the highest loss, starting at ~14% and ending at ~1%. Ericsson starts at ~14% and ends at ~1%. ZTE, Qualcomm, Huawei, and CATT all start between 4% and 7% and converge to ~1% at 43 dB.](38e1f09a72ec6ec6cdce4357bc9b4024_img.jpg) + +| ATG UE ACS (dB) | Ericsson (%) | ZTE (%) | CMCC (%) | Qualcomm (%) | Huawei (%) | CATT (%) | +|-----------------|--------------|---------|----------|--------------|------------|----------| +| 23 | 14 | 6 | 14 | 6 | 7 | 4 | +| 24 | 12 | 5 | 12 | 5 | 6 | 3.5 | +| 25 | 10 | 4 | 10 | 4 | 5 | 3 | +| 26 | 8 | 3 | 8 | 3 | 4 | 2.5 | +| 27 | 6 | 2 | 6 | 2 | 3 | 2 | +| 28 | 5 | 2 | 5 | 2 | 2.5 | 1.8 | +| 29 | 4 | 1 | 4 | 1 | 2 | 1.5 | +| 30 | 3 | 1 | 3 | 1 | 1.8 | 1.2 | +| 31 | 2 | 1 | 2 | 1 | 1.5 | 1 | +| 32 | 1.5 | 1 | 1.5 | 1 | 1.2 | 0.8 | +| 33 | 1 | 1 | 1 | 1 | 1 | 0.6 | +| 34 | 1 | 1 | 1 | 1 | 0.8 | 0.5 | +| 35 | 1 | 1 | 1 | 1 | 0.6 | 0.4 | +| 36 | 1 | 1 | 1 | 1 | 0.5 | 0.3 | +| 37 | 1 | 1 | 1 | 1 | 0.4 | 0.2 | +| 38 | 1 | 1 | 1 | 1 | 0.3 | 0.1 | +| 39 | 1 | 1 | 1 | 1 | 0.2 | 0.1 | +| 40 | 1 | 1 | 1 | 1 | 0.1 | 0.1 | +| 41 | 1 | 1 | 1 | 1 | 0.1 | 0.1 | +| 42 | 1 | 1 | 1 | 1 | 0.1 | 0.1 | +| 43 | 1 | 1 | 1 | 1 | 0.1 | 0.1 | + +Line graph titled 'Throughput Loss - Average of all users in the whole network - (20 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 16. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. Six lines represent Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT. CMCC shows the highest loss, starting at ~14% and ending at ~1%. Ericsson starts at ~14% and ends at ~1%. ZTE, Qualcomm, Huawei, and CATT all start between 4% and 7% and converge to ~1% at 43 dB. + +Figure 6.4.1.7.1-2: Simulation results for Throughput Loss – Average of all users in the whole network + +Maximum distance between ATG BS and ATG UE is 300 km + +![Line graph titled 'Throughput Loss - 5% in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' from 0 to 45. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. A blue line with circular markers represents 'Ericsson' data, showing a downward trend from approximately 43% at 23 dB to 1% at 43 dB.](a9bf8827f39b1b81b7e3ead912e1a69c_img.jpg) + +Throughput Loss - 5% in the whole network - 300km + +| ATG UE ACS (dB) | Throughput Loss (%) | +|-----------------|---------------------| +| 23 | 43 | +| 24 | 38 | +| 25 | 34 | +| 26 | 30 | +| 27 | 26 | +| 28 | 22 | +| 29 | 19 | +| 30 | 16 | +| 31 | 13 | +| 32 | 11 | +| 33 | 9 | +| 34 | 7 | +| 35 | 5 | +| 36 | 4 | +| 37 | 3 | +| 38 | 2 | +| 39 | 2 | +| 40 | 1 | +| 41 | 1 | +| 42 | 1 | +| 43 | 1 | + +Line graph titled 'Throughput Loss - 5% in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' from 0 to 45. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. A blue line with circular markers represents 'Ericsson' data, showing a downward trend from approximately 43% at 23 dB to 1% at 43 dB. + +Figure 6.4.1.7.1-3: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph titled 'Throughput Loss - Average of all users in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' from 0 to 25. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. A blue line with circular markers represents 'Ericsson' data, showing a downward trend from approximately 22% at 23 dB to 1% at 43 dB.](9ded0df3aa355d1a7fdb8598fdf54bff_img.jpg) + +Throughput Loss - Average of all users in the whole network - 300km + +| ATG UE ACS (dB) | Throughput Loss (%) | +|-----------------|---------------------| +| 23 | 22 | +| 24 | 19 | +| 25 | 17 | +| 26 | 14 | +| 27 | 12 | +| 28 | 10 | +| 29 | 8 | +| 30 | 7 | +| 31 | 6 | +| 32 | 5 | +| 33 | 4 | +| 34 | 3 | +| 35 | 3 | +| 36 | 2 | +| 37 | 2 | +| 38 | 1 | +| 39 | 1 | +| 40 | 1 | +| 41 | 1 | +| 42 | 1 | +| 43 | 1 | + +Line graph titled 'Throughput Loss - Average of all users in the whole network - 300km'. The y-axis is 'Throughput Loss (%)' from 0 to 25. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. A blue line with circular markers represents 'Ericsson' data, showing a downward trend from approximately 22% at 23 dB to 1% at 43 dB. + +Figure 6.4.1.7.1-4: Simulation results for Throughput Loss – Average of all users in the whole network + +##### 6.4.1.7.2 Subarray model + +Maximum distance between ATG BS and ATG UE is 100 km + +![Line graph titled 'Throughput Loss - 5% in the whole network - (50 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 30. The x-axis is 'ATG UE ACS(dB)' from 23 to 43. A blue line with circular markers represents 'Ericsson' data, showing a decrease in throughput loss as ACS increases.](92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg) + +Throughput Loss - 5% in the whole network - (50 to) 100km + +| ATG UE ACS(dB) | Throughput Loss (%) | +|----------------|---------------------| +| 23 | 25.5 | +| 24 | 22.5 | +| 25 | 19.5 | +| 26 | 16.5 | +| 27 | 14.0 | +| 28 | 11.5 | +| 29 | 9.5 | +| 30 | 7.5 | +| 31 | 6.0 | +| 32 | 4.5 | +| 33 | 3.5 | +| 34 | 2.8 | +| 35 | 2.2 | +| 36 | 1.8 | +| 37 | 1.5 | +| 38 | 1.2 | +| 39 | 1.0 | +| 40 | 0.8 | +| 41 | 0.6 | +| 42 | 0.5 | +| 43 | 0.4 | + +Line graph titled 'Throughput Loss - 5% in the whole network - (50 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 30. The x-axis is 'ATG UE ACS(dB)' from 23 to 43. A blue line with circular markers represents 'Ericsson' data, showing a decrease in throughput loss as ACS increases. + +Figure 6.4.1.7.1-5: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph titled 'Throughput Loss - Average of all users in the whole network - (50 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 16. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. A blue line with circular markers represents 'Ericsson' data, showing a decrease in throughput loss as ACS increases.](fc3763c02020b3a260045bbadc1d36ba_img.jpg) + +Throughput Loss - Average of all users in the whole network - (50 to) 100km + +| ATG UE ACS (dB) | Throughput Loss (%) | +|-----------------|---------------------| +| 23 | 14.5 | +| 24 | 12.5 | +| 25 | 10.8 | +| 26 | 9.2 | +| 27 | 7.8 | +| 28 | 6.5 | +| 29 | 5.5 | +| 30 | 4.5 | +| 31 | 3.8 | +| 32 | 3.2 | +| 33 | 2.6 | +| 34 | 2.1 | +| 35 | 1.7 | +| 36 | 1.4 | +| 37 | 1.1 | +| 38 | 0.9 | +| 39 | 0.7 | +| 40 | 0.6 | +| 41 | 0.5 | +| 42 | 0.4 | +| 43 | 0.3 | + +Line graph titled 'Throughput Loss - Average of all users in the whole network - (50 to) 100km'. The y-axis is 'Throughput Loss (%)' from 0 to 16. The x-axis is 'ATG UE ACS (dB)' from 23 to 43. A blue line with circular markers represents 'Ericsson' data, showing a decrease in throughput loss as ACS increases. + +Figure 6.4.1.7.1-6: Simulation results for Throughput Loss – Average of all users in the whole network + +Maximum distance between ATG BS and ATG UE is 300 km + +![Line graph showing Throughput Loss (%) vs ATG UE ACS (dB) for 5% of users in the whole network. The y-axis ranges from 0 to 45, and the x-axis ranges from 23 to 43. The data points show a decreasing trend from approximately 42% at 23 dB to about 1% at 43 dB. The legend indicates the data is from Ericsson.](b11f4bc2bbfc46968de10a8ad2a8902f_img.jpg) + +Throughput Loss - 5% in the whole network - 300km + +| ATG UE ACS (dB) | Throughput Loss (%) | +|-----------------|---------------------| +| 23 | 42 | +| 24 | 38 | +| 25 | 34 | +| 26 | 30 | +| 27 | 26 | +| 28 | 22 | +| 29 | 18 | +| 30 | 15 | +| 31 | 12 | +| 32 | 10 | +| 33 | 8 | +| 34 | 6 | +| 35 | 5 | +| 36 | 4 | +| 37 | 3 | +| 38 | 2 | +| 39 | 2 | +| 40 | 1 | +| 41 | 1 | +| 42 | 1 | +| 43 | 1 | + +Ericsson + +Line graph showing Throughput Loss (%) vs ATG UE ACS (dB) for 5% of users in the whole network. The y-axis ranges from 0 to 45, and the x-axis ranges from 23 to 43. The data points show a decreasing trend from approximately 42% at 23 dB to about 1% at 43 dB. The legend indicates the data is from Ericsson. + +Figure 6.4.1.7.1-7: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph showing Throughput Loss (%) vs ATG UE ACS (dB) for the average of all users in the whole network. The y-axis ranges from 0 to 25, and the x-axis ranges from 23 to 43. The data points show a decreasing trend from approximately 22% at 23 dB to about 1% at 43 dB. The legend indicates the data is from Ericsson.](5a8d83665fa993ed599f2eb41fd6c7f5_img.jpg) + +Throughput Loss - Average of all users the whole network - 300km + +| ATG UE ACS (dB) | Throughput Loss (%) | +|-----------------|---------------------| +| 23 | 22 | +| 24 | 19 | +| 25 | 16 | +| 26 | 14 | +| 27 | 12 | +| 28 | 10 | +| 29 | 8 | +| 30 | 7 | +| 31 | 6 | +| 32 | 5 | +| 33 | 4 | +| 34 | 3 | +| 35 | 3 | +| 36 | 2 | +| 37 | 2 | +| 38 | 1 | +| 39 | 1 | +| 40 | 1 | +| 41 | 1 | +| 42 | 1 | +| 43 | 1 | + +Ericsson + +Line graph showing Throughput Loss (%) vs ATG UE ACS (dB) for the average of all users in the whole network. The y-axis ranges from 0 to 25, and the x-axis ranges from 23 to 43. The data points show a decreasing trend from approximately 22% at 23 dB to about 1% at 43 dB. The legend indicates the data is from Ericsson. + +Figure 6.4.1.7.1-8: Simulation results for Throughput Loss – Average of all users in the whole network + +#### 6.4.1.8 Scenario 12: 2GHz TN UL interfering ATG UL + +This scenario captures the co-existence results after evaluation from all possible options. Here TN UL with both AAS subarray and non-subarray model is interfering ATG UL deployed in rural macro environment. + +Table 6.4.1.8-1: Simulation results for Scenario 12 – 2GHz TN UL interfering ATG UL + +| Company | ATG/ TN BS antenna model | Performance Metric | Throughput Loss (%) at ATG BS ACS 46 dB | +|----------|--------------------------|-------------------------------------------|-----------------------------------------| +| Ericsson | Non-Subarray | 5% in the whole network | 2.01 | +| | | Average of all users in the whole network | 0.55 | +| | Subarray | 5% in the whole network | 3.23 | +| | | Average of all users in the whole network | 0.68 | +| ZTE | Non-Subarray | 5% in the whole network | 2.20 | +| | | Average of all users in the whole network | 0.63 | +| | Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | - | +| CMCC | Non-Subarray | 5% in the whole network | 3.18 | +| | | Average of all users in the whole network | 0.88 | +| | Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | - | +| Qualcomm | Non-Subarray | 5% in the whole network | 0.02 | +| | | Average of all users in the whole network | 0.01 | +| | Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | - | +| Huawei | Non-Subarray | 5% in the whole network | 1.70 | +| | | Average of all users in the whole network | 0.001 | +| | Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | - | +| CATT | Non-Subarray | 5% in the whole network | 1.32 | +| | | Average of all users in the whole network | 0.05 | +| | Subarray | 5% in the whole network | - | +| | | Average of all users in the whole network | - | + +##### 6.4.1.8.1 Non-Subarray model + +![Line graph titled 'Throughput Loss - 5% in the whole network' showing throughput loss (%) vs ATG BS ACS (dB) for six companies. CMCC shows the highest loss, while Qualcomm shows the lowest.](a50451e9d6b6c7f9b9673b9bb70bae3f_img.jpg) + +The graph displays the throughput loss percentage for six companies (Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT) as a function of the ATG BS ACS (dB) value, ranging from 36 to 56 dB. The Y-axis represents the Throughput Loss (%) from 0 to 4.5. The X-axis represents the ATG BS ACS (dB) from 36 to 56. The data series are as follows: + +| ATG BS ACS (dB) | Ericsson (%) | ZTE (%) | CMCC (%) | Qualcomm (%) | Huawei (%) | CATT (%) | +|-----------------|--------------|---------|----------|--------------|------------|----------| +| 36 | 2.8 | 2.7 | 3.8 | 0.2 | 2.8 | 2.4 | +| 37 | 2.4 | 2.5 | 3.7 | 0.2 | 2.4 | 2.2 | +| 38 | 2.2 | 2.4 | 3.6 | 0.2 | 2.2 | 2.0 | +| 39 | 2.1 | 2.3 | 3.5 | 0.2 | 2.1 | 1.9 | +| 40 | 2.0 | 2.2 | 3.4 | 0.2 | 2.0 | 1.8 | +| 41 | 2.0 | 2.1 | 3.3 | 0.2 | 2.0 | 1.7 | +| 42 | 2.0 | 2.1 | 3.2 | 0.2 | 2.0 | 1.6 | +| 43 | 2.0 | 2.1 | 3.1 | 0.2 | 2.0 | 1.5 | +| 44 | 2.0 | 2.1 | 3.0 | 0.2 | 2.0 | 1.4 | +| 45 | 2.0 | 2.1 | 3.0 | 0.2 | 2.0 | 1.3 | +| 46 | 2.0 | 2.1 | 3.0 | 0.2 | 2.0 | 1.2 | +| 47 | 2.0 | 2.1 | 3.0 | 0.2 | 2.0 | 1.1 | +| 48 | 2.0 | 2.1 | 3.0 | 0.2 | 2.0 | 1.1 | +| 49 | 2.0 | 2.1 | 3.0 | 0.2 | 2.0 | 1.1 | +| 50 | 2.0 | 2.1 | 3.0 | 0.2 | 2.0 | 1.1 | + +Line graph titled 'Throughput Loss - 5% in the whole network' showing throughput loss (%) vs ATG BS ACS (dB) for six companies. CMCC shows the highest loss, while Qualcomm shows the lowest. + +Figure 6.4.1.8.1-1: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph titled 'Throughput Loss - Average of all users in the whole network' showing throughput loss (%) vs ATG BS ACS (dB) for Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT.](e466e4c4fb08567a109bb959a765225c_img.jpg) + +This line graph shows the average throughput loss for all users in the network across different ATG BS ACS (dB) values. The y-axis represents 'Throughput Loss (%)' from 0 to 1.2, and the x-axis represents 'ATG BS ACS (dB)' from 36 to 56. Six data series are plotted: Ericsson (blue), ZTE (red), CMCC (green), Qualcomm (purple), Huawei (cyan), and CATT (orange). CMCC shows the highest throughput loss, starting at approximately 1.0% at 36 dB and slightly decreasing to about 0.85% at 50 dB. ZTE and Ericsson show moderate losses, starting around 0.7% and 0.65% respectively, and decreasing slightly to around 0.6% and 0.55% at 50 dB. Qualcomm, Huawei, and CATT show the lowest losses, starting near 0% and slightly increasing to around 0.05% at 50 dB. + +| ATG BS ACS (dB) | Ericsson (%) | ZTE (%) | CMCC (%) | Qualcomm (%) | Huawei (%) | CATT (%) | +|-----------------|--------------|---------|----------|--------------|------------|----------| +| 36 | 0.65 | 0.75 | 1.00 | 0.10 | 0.00 | 0.25 | +| 37 | 0.62 | 0.72 | 0.98 | 0.08 | 0.00 | 0.22 | +| 38 | 0.60 | 0.70 | 0.96 | 0.06 | 0.00 | 0.20 | +| 39 | 0.58 | 0.68 | 0.94 | 0.04 | 0.00 | 0.18 | +| 40 | 0.57 | 0.66 | 0.92 | 0.03 | 0.00 | 0.16 | +| 41 | 0.56 | 0.65 | 0.91 | 0.02 | 0.00 | 0.14 | +| 42 | 0.55 | 0.64 | 0.90 | 0.01 | 0.00 | 0.12 | +| 43 | 0.54 | 0.63 | 0.89 | 0.01 | 0.00 | 0.10 | +| 44 | 0.53 | 0.62 | 0.88 | 0.01 | 0.00 | 0.08 | +| 45 | 0.52 | 0.61 | 0.87 | 0.01 | 0.00 | 0.07 | +| 46 | 0.51 | 0.60 | 0.86 | 0.01 | 0.00 | 0.06 | +| 47 | 0.50 | 0.59 | 0.85 | 0.01 | 0.00 | 0.05 | +| 48 | 0.49 | 0.58 | 0.84 | 0.01 | 0.00 | 0.04 | +| 49 | 0.48 | 0.57 | 0.83 | 0.01 | 0.00 | 0.03 | +| 50 | 0.47 | 0.56 | 0.82 | 0.01 | 0.00 | 0.02 | + +Line graph titled 'Throughput Loss - Average of all users in the whole network' showing throughput loss (%) vs ATG BS ACS (dB) for Ericsson, ZTE, CMCC, Qualcomm, Huawei, and CATT. + +Figure 6.4.1.8.1-2: Simulation results for Throughput Loss – Average of all users in the whole network + +##### 6.4.1.8.2 Subarray model + +![Line graph titled 'Throughput Loss - 5% in the whole network' showing throughput loss (%) vs ATG BS ACS (dB) for Ericsson.](28639a75145506e46966c11c1b995dd2_img.jpg) + +This line graph shows the throughput loss for 5% of users in the network across different ATG BS ACS (dB) values. The y-axis represents 'Throughput Loss (%)' from 0 to 4.5, and the x-axis represents 'ATG BS ACS (dB)' from 36 to 56. A single data series for Ericsson (blue) is plotted, showing a decrease in throughput loss from approximately 3.9% at 36 dB to about 3.2% at 50 dB. + +| ATG BS ACS (dB) | Ericsson (%) | +|-----------------|--------------| +| 36 | 3.9 | +| 37 | 3.7 | +| 38 | 3.5 | +| 39 | 3.4 | +| 40 | 3.3 | +| 41 | 3.2 | +| 42 | 3.1 | +| 43 | 3.0 | +| 44 | 2.9 | +| 45 | 2.8 | +| 46 | 2.7 | +| 47 | 2.6 | +| 48 | 2.5 | +| 49 | 2.4 | +| 50 | 2.3 | + +Line graph titled 'Throughput Loss - 5% in the whole network' showing throughput loss (%) vs ATG BS ACS (dB) for Ericsson. + +Figure 6.4.1.8.2-1: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph titled 'Throughput Loss - Average of all users in the whole network'. The y-axis is 'Throughput Loss (%)' from 0.6 to 0.8. The x-axis is 'ATG BS ACS (dB)' from 36 to 56. A blue line with circular markers represents the 'Ericsson' data, showing a decrease in throughput loss as ACS increases.](f68421f5d184c116a7061977a9057e63_img.jpg) + +The graph shows the average throughput loss for all users in the network as a function of the ATG BS ACS (dB). The x-axis ranges from 36 to 56 dB, and the y-axis ranges from 0.6 to 0.8. The data points for Ericsson show a steady decrease in throughput loss as the ACS increases, starting at approximately 0.785% at 36 dB and ending at approximately 0.67% at 50 dB. + +| ATG BS ACS (dB) | Throughput Loss (%) | +|-----------------|---------------------| +| 36 | 0.785 | +| 37 | 0.765 | +| 38 | 0.745 | +| 39 | 0.725 | +| 40 | 0.71 | +| 41 | 0.70 | +| 42 | 0.69 | +| 43 | 0.685 | +| 44 | 0.68 | +| 45 | 0.678 | +| 46 | 0.675 | +| 47 | 0.672 | +| 48 | 0.67 | +| 49 | 0.668 | +| 50 | 0.665 | + +Line graph titled 'Throughput Loss - Average of all users in the whole network'. The y-axis is 'Throughput Loss (%)' from 0.6 to 0.8. The x-axis is 'ATG BS ACS (dB)' from 36 to 56. A blue line with circular markers represents the 'Ericsson' data, showing a decrease in throughput loss as ACS increases. + +**Figure 6.4.1.8.2-2: Simulation results for Throughput Loss – Average of all users in the whole network** + +### 6.4.2 Non-synchronized Scenarios + +#### 6.4.2.1 Scenario 5: 4GHz ATG DL interfering TN UL + +This scenario captures the co-existence results after evaluation from all possible options. Here ATG DL with both AAS subarray and non-subarray model is interfering TN UL deployed in rural macro environment. + +##### 6.4.2.1.1 Using FSPL model + +Table 6.4.2.1.1: Simulation results for Scenario 5 – 4GHz ATG DL interfering TN UL using FSPL model + +| Company | ATG/ TN BS antenna model | Performance Metric | Isolation distance (km) for 5% throughput loss | | | +|----------|--------------------------|------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|-----|-----| +| | | | Angle between ATG BS boresight and nearest TN BS boresight in azimuth | | | +| | | | 0° | 30° | 60° | +| CMCC | Non-subarray | 5% of users within the cell with largest throughput loss for the case of TN UL victim | >400 | 50 | 35 | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | 200 | 30 | 15 | +| | Subarray | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | - | +| ZTE | Non-Subarray | 5% of users within the cell with largest throughput loss for the case of TN UL victim | 100 | 10 | 80 | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | - | +| | Subarray | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | - | +| Qualcomm | Non-Subarray | 5% of users within the cell with largest throughput loss for the case of TN UL victim | 50 | - | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | - | +| | Subarray | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | - | +| Ericsson | Non-Subarray | 5% of users within the cell with largest throughput loss for the case of TN UL victim | 290 | 39 | 15 | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | 60 | 14 | 8 | +| | Subarray | 5% of users within the cell with largest throughput loss for the case of TN UL victim | 350 | 42 | 25 | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | 70 | 14 | 9 | + +##### 6.4.2.1.2 Using RMa model in TR 38.901 with updating hUT as 30m + +**Table 6.4.2.1.2: Simulation results for Scenario 5 – 4GHz ATG DL interfering TN UL using RMa model with hUT as 30m** + +| Company | ATG/ TN BS antenna model | Performance Metric | Isolation distance (km) for 5% throughput loss | | | +|---------|--------------------------|------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|-----|-----| +| | | | Angle between ATG BS boresight and nearest TN BS boresight in azimuth | | | +| | | | 0° | 30° | 60° | +| CMCC | Non-subarray | 5% of users within the cell with largest throughput loss for the case of TN UL victim | 17 | 11 | 9 | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | 12 | 7 | 6 | +| | Subarray | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | - | +| CATT | Non-Subarray | 5% of users within the cell with largest throughput loss for the case of TN UL victim | 19 | 13 | 8 | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | <5 | <5 | <5 | +| | Subarray | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | - | +| ZTE | Non-Subarray | 5% of users within the cell with largest throughput loss for the case of TN UL victim | 20 | 3 | 17 | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | - | +| | Subarray | 5% of users within the cell with largest throughput loss for the case of TN UL victim | - | - | - | +| | | Average of all users within the cell with largest throughput loss for the case of TN UL victim | - | - | - | + +#### 6.4.2.2 Scenario 6: 4GHz TN UL interfering TN DL + +The ATG BS – TN BS cross link interference will dominate the interference between ATG UE and TN UE, so the co-existence evaluation for this scenario has been excluded considering low interference levels. + +#### 6.4.2.3 Scenario 7: 4GHz TN DL interfering ATG UL + +This scenario captures the co-existence results after evaluation from all possible options. Here TN DL with both AAS subarray and non-subarray model is interfering ATG UL deployed in rural macro environment. + +##### 6.4.2.3.1 Using FSPL model + +Table 6.4.2.3.1: Simulation results for Scenario 7 – 4GHz TN DL interfering ATG UL using FSPL model + +| Company | ATG/ TN BS antenna model | Performance Metric | Isolation distance (km) for 5% throughput loss | | | +|----------|--------------------------|-------------------------------------------|-----------------------------------------------------------------------|-----|-----| +| | | | Angle between ATG BS boresight and nearest TN BS boresight in azimuth | | | +| | | | 0° | 30° | 60° | +| CMCC | Non-Subarray | 5% in the whole network | >500 | 75 | 55 | +| | | Average of all users in the whole network | >300 | 45 | 25 | +| | Subarray | 5% in the whole network | - | - | - | +| | | Average of all users in the whole network | - | - | - | +| ZTE | Non-Subarray | 5% in the whole network | 550 | 50 | 40 | +| | | Average of all users in the whole network | - | - | - | +| | Subarray | 5% in the whole network | - | - | - | +| | | Average of all users in the whole network | - | - | - | +| Qualcomm | Non-Subarray | 5% in the whole network | 203 | - | - | +| | | Average of all users in the whole network | - | - | - | +| | Subarray | 5% in the whole network | - | - | - | +| | | Average of all users in the whole network | - | - | - | +| Ericsson | Non-Subarray | 5% in the whole network | >500 | 70 | 35 | +| | | Average of all users in the whole network | 290 | 41 | 25 | +| | Subarray | 5% in the whole network | >500 | 70 | 70 | +| | | Average of all users in the whole network | 400 | 47 | 43 | +| Huawei | Non-Subarray | 5% in the whole network | >1000 | - | - | +| | | Average of all users in the whole network | - | - | - | +| | Subarray | 5% in the whole network | - | - | - | +| | | Average of all users in the whole network | - | - | - | + +##### 6.4.2.3.2 Using RMa model in TR 38.901 with updating hUT as 30m + +Table 6.4.2.3.2: Simulation results for Scenario 7 – 4GHz TN DL interfering ATG UL using RMa model with hUT as 30m + +| Company | ATG/ TN BS antenna model | Performance Metric | Isolation distance (km) for 5% throughput loss | | | +|----------|--------------------------|-------------------------------------------|-----------------------------------------------------------------------|-----|-----| +| | | | Angle between ATG BS boresight and nearest TN BS boresight in azimuth | | | +| | | | 0° | 30° | 60° | +| CMCC | Non-Subarray | 5% in the whole network | 16 | 9 | 8 | +| | | Average of all users in the whole network | 11 | 7 | 5 | +| | Subarray | 5% in the whole network | - | - | - | +| | | Average of all users in the whole network | - | - | - | +| ZTE | Non-Subarray | 5% in the whole network | 20 | 9 | 6 | +| | | Average of all users in the whole network | - | - | - | +| | Subarray | 5% in the whole network | - | - | - | +| | | Average of all users in the whole network | - | - | - | +| Qualcomm | Non-Subarray | 5% in the whole network | 9 | - | - | +| | | Average of all users in the whole network | - | - | - | +| | Subarray | 5% in the whole network | - | - | - | +| | | Average of all users in the whole network | - | - | - | +| CATT | Non-Subarray | 5% in the whole network | 18 | 13 | 11 | +| | | Average of all users in the whole network | 15 | 10 | 7 | +| | Subarray | 5% in the whole network | - | - | - | +| | | Average of all users in the whole network | - | - | - | + +#### 6.4.2.4 Scenario 8: 4GHz TN UL interfering TN DL + +The ATG BS – TN BS cross link interference will dominate the interference between ATG UE and TN UE, so the co-existence evaluation for this scenario has been excluded considering low interference levels. + +#### 6.4.2.5 Scenario 13: 4GHz TN UL interfering TN DL + +The ATG BS – TN BS cross link interference will dominate the interference between ATG UE and TN UE, so the co-existence evaluation for this scenario has been excluded considering low interference levels. + +#### 6.4.2.6 Scenario 14: 2GHz TN DL interfering ATG UL + +This scenario captures the co-existence results after evaluation from all possible options. Here TN DL with both AAS subarray and non-subarray model is interfering ATG UL deployed in rural macro environment. + +##### 6.4.2.6.1 Using FSPL model + +**Table 6.4.2.6-1: Simulation results for Scenario 14 – 2GHz TN DL interfering ATG UL using FSPL model** + +| Company | ATG/ TN BS antenna model | Performance Metric | Isolation distance (km) for 5% throughput loss | | | +|----------|--------------------------|-------------------------------------------|-----------------------------------------------------------------------|------|-----| +| | | | Angle between ATG BS boresight and nearest TN BS boresight in azimuth | | | +| | | | 0° | 30° | 60° | +| CMCC | Non-Subarray | 5% in the whole network | >500 | >100 | 80 | +| | | Average of all users in the whole network | 500 | 75 | 35 | +| | Subarray | 5% in the whole network | - | - | - | +| | | Average of all users in the whole network | - | - | - | +| Huawei | Non-Subarray | 5% in the whole network | >1000 | - | - | +| | | Average of all users in the whole network | - | - | - | +| | Subarray | 5% in the whole network | - | - | - | +| | | Average of all users in the whole network | - | - | - | +| ZTE | Non-Subarray | 5% in the whole network | 700 | 90 | 70 | +| | | Average of all users in the whole network | - | - | - | +| | Subarray | 5% in the whole network | - | - | - | +| | | Average of all users in the whole network | - | - | - | +| Qualcomm | Non-Subarray | 5% in the whole network | 220 | - | - | +| | | Average of all users in the whole network | - | - | - | +| | Subarray | 5% in the whole network | - | - | - | +| | | Average of all users in the whole network | - | - | - | +| Ericsson | Non-Subarray | 5% in the whole network | >500 | 130 | 90 | +| | | Average of all users in the whole network | >500 | 80 | 41 | +| | Subarray | 5% in the whole network | >500 | 140 | 120 | +| | | Average of all users in the whole network | >500 | 90 | 70 | + +##### 6.4.2.6.2 Using RMa model in TR 38.901 with updating hUT as 30m + +**Table 6.4.2.6-2: Simulation results for Scenario 14 – 2GHz TN DL interfering ATG UL using RMa model with hUT as 30m** + +| Company | ATG/ TN BS antenna model | Performance Metric | Isolation distance (km) for 5% throughput loss | | | +|----------|--------------------------|-------------------------------------------|-----------------------------------------------------------------------|-----|-----| +| | | | Angle between ATG BS boresight and nearest TN BS boresight in azimuth | | | +| | | | 0° | 30° | 60° | +| CMCC | Non-Subarray | 5% in the whole network | 18 | 12 | 10 | +| | | Average of all users in the whole network | 13 | 0 | 6 | +| | Subarray | 5% in the whole network | - | - | - | +| | | Average of all users in the whole network | - | - | - | +| CATT | Non-Subarray | 5% in the whole network | 26 | 19 | 19 | +| | | Average of all users in the whole network | 22 | 18 | 16 | +| | Subarray | 5% in the whole network | - | - | - | +| | | Average of all users in the whole network | - | - | - | +| ZTE | Non-Subarray | 5% in the whole network | 17 | 10 | 6 | +| | | Average of all users in the whole network | - | - | - | +| | Subarray | 5% in the whole network | - | - | - | +| | | Average of all users in the whole network | - | - | - | +| Qualcomm | Non-Subarray | 5% in the whole network | 5 | - | - | +| | | Average of all users in the whole network | - | - | - | +| | Subarray | 5% in the whole network | - | - | - | +| | | Average of all users in the whole network | - | - | - | + +## 6.5 Summary of co-existence study + +### 6.5.1 Synchronized Scenarios + +This sub-clause captures the summary of the co-existence studies for the synchronized scenarios. + +Considering the following ACLR and ACS of TN BS and UE in Table 6.5.1-1, the suggested ACLR and ACS of ATG BS and UE for all scenarios are given in Table 6.5.1-2. It should be noted that the derived values are limited by the nature of assumptions and methodologies adopted in the co-existence studies. + +**Table 6.5.1-1: ACLR and ACS of TN** + +| TN | | Values | +|----|------|--------| +| BS | ACLR | 45 dB | +| | ACS | 46 dB | +| UE | ACLR | 30 dB | +| | ACS | 33 dB | + +**Table 6.5.1-2: Co-existence results suggested ACLR and ACS of ATG system** + +| ATG | | Values | +|--------------------------------------------------------------------------------------------------|------|---------------| +| BS | ACLR | 45 dB | +| | ACS | 46 dB | +| UE | ACLR | 30 dB | +| | ACS | 33 dB | +| NOTE 1: Higher interference maybe caused by aircraft at lower altitudes in the applicable range. | | | + +### 6.5.2 Non-Synchronized Scenarios + +This sub-clause captures the summary of the co-existence studies for the non-synchronized scenarios. + +Two propagation models between ATG BS and TN BS has been considered. The simulation results based on both models – Free Space Path loss and RMa model in TR 38.901 with hUT as 30m has been captured in the TR, serving only as information for the readers. The models have the following limitations as highlighted below and it's upto the readers discretion to analyze based on their implementation – + +- Free Space Path Loss model + - Interference may arise through a range of propagation mechanisms whose individual dominance depends on climate, radio frequency, time percentage of interest, distance, and path topography. Free space modeling is one of such mechanism. +- RMa model in TR 38.901 with updating hUT as 30m + - The applicable range of User Terminal antenna height- hUT in the proposed RMa Pathloss model is - + +$$1\text{m} \leq h_{\text{UT}} \leq 10\text{m}$$ + +- whereas in the simulations, hUT has been considered as 30m which is above the limit. +- The applicable maximum distance - d2D in the RMa Pathloss model is 10 km for LoS and 5km for NLoS, whereas in the simulations (also stated in Table 6.2.1.2-1 in ATG Network Layout) is minimum distance of 20 km for Non-subarray and 50 km for Sub-array and maximum distance of 100km for both antenna models. This is again way above the limit questioning the validity and accuracy of the model. + +Considering the simulation results in Sub-clause 6.4.2 and the highlighted above limitations, following observations are made based on the propagation models + +- Optimistic isolation distances in the multiples of tens of kilometres, based on RMa pathloss model in TR 38.901 with hUT as 30m, when the angle between ATG BS boresight and nearest TN boresight in azimuth are 0°, 30° and 60°. +- Pessimistic isolation distances in the multiples of tens to multiples of hundreds of kilometres, based on Free space Pathloss model, when the angle between ATG BS boresight and nearest TN boresight in azimuth are 0°, 30° and 60°. + +# 7 RF requirements + +## 7.1 ATG UE specific + +### 7.1.1 ATG UE power class and requirement type + +Since the required power level for ATG might be varying in different aircraft types and also in different frequency ranges, it's quite difficult to focus on one specific power class for ATG UE from 3GPP perspective, therefore 3GPP agreed to introduce the new capability for ATG UE to indicate the rated maximum output power at maximum modulation order and full PRB configurations and its capability report granularity as 1dB. The range of its power limit are defined as following: + +- The lower limit of conductive MOP or TRP of ATG UE is 23 dBm +- The upper limit of conductive MOP or TRP of ATG UE is 40 dBm + +In addition, considering the implementation freedom for ATG UE(e.g. for 2 GHz, to use omni-directional antenna for ATG UE and for 4 GHz, to use antenna array for ATG UE), therefore 3GPP RAN4 agreed to introduce two ATG UE types to distinguish the antenna types for ATG UE. + +### 7.1.2 Tx requirements + +#### 7.1.2.1 Frequency error + +The doppler frequency for ATG UE can be determined by, + +$$f_D = \cos\theta * \frac{v}{c} * f_c$$ + +Where, + +- $f_D$ is Doppler frequency, $f_c$ is the carrier frequency, which is set as 5GHz for n79. +- $v$ is the speed of the aircraft which is 1200km/h. +- $\theta$ is the elevation angle between UE and gNB. + +Since the potential maximum cell range is up to 200-300km [2] and the normal commercial airplane altitude is 10km, the elevation angle is only about 2~3 degrees when UE doing initial access at cell edge. Then the maximum DL doppler frequency is approaching 5.5kHz and the UL doppler frequency compared to the configured UL central frequency is approaching 5.5kHz if without any compensation which may cause not negligible impact for link performance and access successful rate. ATG UE needs to perform frequency compensation. The frequency accuracy requirement will be written assuming Doppler frequency pre-compensation. + +The ATG BS coarse location information captured in new SIB specified in TS 38.331 for ATG could be broadcasted for ATG UE to do frequency compensation if necessary. [UE shall rely on the ATG BS location broadcasted by the IE *EphemerisInfo* in NTN SIB 19 in 38.331 if pre-compensation is based on SIB19. Where, Ephemeris may be expressed in format of position and velocity state vector]. + +#### 7.1.2.2 MOP requirements + +For ATG UE, the maximum output power is declared at maximum modulation order and full PRB configurations within the channel bandwidth of NR carrier unless otherwise stated. The period of measurement shall be at least one sub frame (1ms). + +ATG UE implementations/antenna patterns might be varying for different operating bands. The output power from the UE may depend on the aircraft type and exact deployment scenario. Currently, there is a lack of knowledge in 3GPP of the appropriate output power for an ATG UE considering all design, regulatory constraints and potential avionics device protection. For this reason, it is agreed that ATG UE is allowed to declare the output power and signal it to the network. The lower limit of conductive MOP or TRP declared by ATG UE is 23dBm. The upper limit of conductive MOP or TRP declared by ATG UE is 40dBm. The capability report granularity is 1dB. + +#### 7.1.2.3 MPR/AMPR requirements + +ATG UE is allowed to declare the output power at supported maximum modulation order and full PRB configurations. Thus, MPR/AMPR requirements are not needed as ATG UE can declare a lower power whenever power back-off is needed. Additionally, when ATG UE indicate the maximum output power under the specific conditions (the supported maximum modulation order, full PRB configurations, SEM/spurious emission requirements, regulation requirements and so on), the necessary power back-off should be considered. In total, the power back-off has been included in the declared maximum output power, so there is no need to specify MPR/AMPR requirements for ATG UE. + +#### 7.1.2.4 Configured transmitted power + +The UE is allowed to set its configured maximum output power $P_{\text{CMAX},f,c}$ for carrier f of serving cell c in each slot. The configured maximum output power $P_{\text{CMAX},f,c}$ is set within the following bounds: + +$$P_{\text{CMAX\_L},f,c} \leq P_{\text{CMAX},f,c} \leq P_{\text{CMAX\_H},f,c} \text{ with}$$ + +$$P_{\text{CMAX\_L},f,c} = \text{MIN} \{P_{\text{EMAX},c}, P_{\text{MaxOutputPower}}\}$$ + +$$P_{\text{CMAX\_H},f,c} = P_{\text{EMAX},c}$$ + +where + +$P_{\text{EMAX},c}$ is the value given by either the *p-Max* IE or the field *additionalPmax* of the *NR-NS-PmaxList* IE, whichever is applicable according to TS 38.331[7]; + +$P_{\text{MaxOutputPower}}$ is the maximum UE output power at maximum modulation order and full PRB configurations which is indicated by ATG UE; + +#### 7.1.2.5 Minimum output power + +The calculation and results for minimum output power are listed below. + +**Table 7.1.2.5-1 the calculation for minimum output power requirements** + +| Parameters | Omni-directional antenna | phased array antenna | +|-------------------------------------|--------------------------|----------------------| +| center frequency GHz | 2 | 4 | +| Distance meter | 3000 | 3000 | +| Pathloss dB | 108.063 | 114.0836 | +| ATG BS antenna gain | 21 | 21 | +| ATG UE antenna gain | 0 | 11 | +| Thermal noise power density dBm/MHz | -114 | -114 | +| ATG BS Noise figure dB | 5 | 5 | +| Minimum output power dBm/MHz | -21.937 | -26.9164 | +| Minimum output power dBm/5MHz | -14.9473 | -19.92669996 | + +The minimum output power requirements are specified below. + +**Table 7.1.2.5-2 the calculation for minimum output power requirements** + +| Channel bandwidth | (MHz) | 5,10,15,20 | 25,30,35,40,45,50 | 60,70,80,90,100 | +|-----------------------|-------|-----------------------------------------------------|------------------------------------------------|------------------------------------------------| +| REF_SCS | (kHz) | 15 | | | +| Minimum output power | (dBm) | X | $X+10\log_{10}(\text{BW}_{\text{Channel}}/20)$ | $X+10\log_{10}(\text{BW}_{\text{Channel}}/20)$ | +| Measurement bandwidth | (MHz) | $\text{MBW}=\text{REF\_SCS}*(12*\text{NRB}+1)/1000$ | | | + +NOTE 1: The minimum output power value is rounded to the nearest number down to one decimal point. +NOTE 2: X = -15 for the ATG UE with omni-directional antenna. X = -19 for the ATG UE with phased array antenna. + +#### 7.1.2.6 Transmit OFF power + +The current requirements for Transmit OFF power specified in clause 6.3.2 of TS 38.101-1 are applicable to ATG UE, i.e. -50dBm. + +#### 7.1.2.7 Transmit ON/OFF time mask + +The current requirements for Transmit ON/OFF time mask specified in clause 6.3.3 of TS 38.101-1 are applicable to ATG UE. + +#### 7.1.2.8 Power control + +The current requirements for power control specified in clause 6.3.4 of TS 38.101-1 are applicable to ATG UE. + +#### 7.1.2.9 Transmit signal quality + +Transmit signal quality include frequency error and transmit modulation quality. + +For frequency error, frequency pre-compensation is assumed for ATG UE. The existing requirement defined for NTN UE in TS 38.101-5 [7] will be reused as baseline. + +Regarding modulation scheme, QPSK/16QAM/64QAM will be supported as mandatory. For 256QAM, there are some challenges for ATG due to large propagation distance. While according to the evaluation for 2GHz and 4GHz in [6], the + +SNR above 25dB can still be seen in the considered scenarios for both UL and DL. UL 256QAM is supported for ATG UE as optional feature. + +![Figure 7.1.2.9-1: Received SNR for FDD 20MHz @ 2GHz. A line graph showing SNR [dB] on the y-axis (0.0 to 50.0) versus Distance [km] on the x-axis (10 to 290). Two curves are plotted: DL (blue) and UL (orange). Both curves start at approximately 45 dB at 10 km and decrease to about 15 dB at 290 km, with the UL curve being slightly higher than the DL curve throughout.](9d18af84f9d0bd3cb990f22f91fcf938_img.jpg) + +| Distance [km] | DL SNR [dB] | UL SNR [dB] | +|---------------|-------------|-------------| +| 10 | 45 | 45 | +| 30 | 38 | 39 | +| 50 | 32 | 33 | +| 70 | 28 | 29 | +| 90 | 25 | 26 | +| 110 | 22 | 23 | +| 130 | 20 | 21 | +| 150 | 18 | 19 | +| 170 | 16 | 17 | +| 190 | 15 | 16 | +| 210 | 14 | 15 | +| 230 | 13 | 14 | +| 250 | 12 | 13 | +| 270 | 11 | 12 | +| 290 | 10 | 11 | + +Figure 7.1.2.9-1: Received SNR for FDD 20MHz @ 2GHz. A line graph showing SNR [dB] on the y-axis (0.0 to 50.0) versus Distance [km] on the x-axis (10 to 290). Two curves are plotted: DL (blue) and UL (orange). Both curves start at approximately 45 dB at 10 km and decrease to about 15 dB at 290 km, with the UL curve being slightly higher than the DL curve throughout. + +Figure 7.1.2.9-1: received SNR for FDD 20MHz at 2GHz + +![Figure 7.1.2.9-2: Received SNR for TDD 100MHz @ 4GHz. A line graph showing SNR [dB] on the y-axis (0.0 to 50.0) versus Distance [km] on the x-axis (10 to 290). Two curves are plotted: DL (blue) and UL (orange). Both curves start at approximately 40 dB at 10 km and decrease to about 10 dB at 290 km, with the DL curve being slightly higher than the UL curve throughout.](36f66d23ff319c73247feee55fd2dfb1_img.jpg) + +| Distance [km] | DL SNR [dB] | UL SNR [dB] | +|---------------|-------------|-------------| +| 10 | 40 | 38 | +| 30 | 35 | 32 | +| 50 | 30 | 26 | +| 70 | 26 | 22 | +| 90 | 23 | 19 | +| 110 | 20 | 16 | +| 130 | 18 | 14 | +| 150 | 16 | 12 | +| 170 | 14 | 10 | +| 190 | 13 | 9 | +| 210 | 12 | 8 | +| 230 | 11 | 7 | +| 250 | 10 | 6 | +| 270 | 9 | 5 | +| 290 | 8 | 4 | + +Figure 7.1.2.9-2: Received SNR for TDD 100MHz @ 4GHz. A line graph showing SNR [dB] on the y-axis (0.0 to 50.0) versus Distance [km] on the x-axis (10 to 290). Two curves are plotted: DL (blue) and UL (orange). Both curves start at approximately 40 dB at 10 km and decrease to about 10 dB at 290 km, with the DL curve being slightly higher than the UL curve throughout. + +Figure 7.1.2.9-2: received SNR for TDD 100MHz at 4GHz + +For transmit modulation quality, the following requirement for FR1 UE in 38.101-1 [4] will be reused for ATG UE. + +| Parameter | Unit | Average EVM Level | +|-----------|------|-------------------| +| QPSK | % | 17.5 | +| 16 QAM | % | 12.5 | +| 64 QAM | % | 8 | +| 256 QAM | % | 3.5 | + +#### 7.1.2.10 Occupied bandwidth + +The Occupied bandwidth requirement in subclause 6.5.1 of 38.101-1 [4] is applicable for ATG UE operating in FR1. + +#### 7.1.2.11 SEM requirements + +#### 7.1.2.12 ACLR requirements + +FR1 PC3 ACLR requirement in 38.101-1 is reused for ATG CPE. + +#### 7.1.2.13 Spurious emission + +The general spurious emission requirement in subclause 6.5.3.1 of 38.101-1 [4] is applicable for ATG UE operating in FR1. + +#### 7.1.2.14 Spurious emissions for UE co-existence + +Given the separation distance between ATG UE and TN UE is quite large, it is expected that the achievable MCL can be large enough to overcome the UE-UE interference. This requirement will not be specified for ATG UE. + +#### 7.1.2.15 Transmit intermodulation + +### 7.1.3 Rx requirements + +#### 7.1.3.1 General + +Unless otherwise stated the receiver characteristics are specified at the antenna connector(s) of the ATG UE. For CPE(s) with an integral antenna only, a reference antenna(s) with a gain of 0 dBi is assumed for each antenna port(s). CPE with an integral antenna(s) may be taken into account by converting these power levels into field strength requirements, assuming a 0 dBi gain antenna. For CPEs with more than one receiver antenna connector, identical interfering signals shall be applied to each receiver antenna port if more than one of these is used (diversity). + +#### 7.1.3.2 Diversity characteristics + +The CPE for ATG is required to be equipped with a minimum of two Rx antenna ports in all the ATG operating bands in FR1. + +#### 7.1.3.3 REFSENS requirements + +The reference sensitivity power level REFSENS is the minimum mean power applied to each one of the CPE antenna ports, at which the throughput shall meet or exceed the requirements for the specified reference measurement channel. + +The same assumptions of NR FR1 handheld UE are used for NR ATG CEP in ATG operating bands in FR1. Therefore, the reference sensitivity of NR FR1 handheld UE could be reused for ATG UE. + +The throughput shall be $\geq 95$ % of the maximum throughput of the reference measurement channels as specified in Annexes A.2.2.2 and A.3.2 from TS 38.101-1 [4] (with one sided dynamic OCNG Pattern OP.1 FDD for the DL-signal as described in Annex A.5.1.1 from TS 38.101-1 [4]) with parameters specified in Table 7.1.3.3-1a, Table 7.1.3.3-1b and Table 7.1.3.2.2-3 + +Table 7.1.3.3-1a: Two antenna port reference sensitivity QPSK REFSENS for FDD bands + +| Operating band / SCS / Channel bandwidth | | | | | | +|------------------------------------------|---------|-------------|--------------|--------------|--------------| +| Operating Band | SCS kHz | 5 MHz (dBm) | 10 MHz (dBm) | 15 MHz (dBm) | 20 MHz (dBm) | +| n1 | 15 | -100.0 | -96.8 | -95.0 | -93.8 | +| | 30 | | -97.1 | -95.1 | -94.0 | +| | 60 | | -97.5 | -95.4 | -94.2 | + +Table 7.1.3.3-1b: Two antenna port reference sensitivity QPSK REFSENS for TDD bands + +| Operating band / SCS / Channel bandwidth / REFSENS | | | | | +|----------------------------------------------------|---------|-------------------------------------------------|----------------------------------|-------------| +| Operating band | SCS kHz | Channel bandwidth (MHz) | REFSENS (dBm) | Duplex Mode | +| n39 | 15 | 5, 10, 15, 20, 25, 30, 40 | $-100 + 10\log_{10}(N_{RB}/25)$ | TDD | +| | 30 | 10, 15, 20, 25, 30, 40 | $-97.1 + 10\log_{10}(N_{RB}/24)$ | | +| | 60 | 10, 15, 20, 25, 30, 40 | $-97.5 + 10\log_{10}(N_{RB}/11)$ | | +| n78 | 15 | 10, 15, 20, 25, 30, 40, 50 | $-95.8 + 10\log_{10}(N_{RB}/52)$ | TDD | +| | 30 | 10, 15, 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | $-96.1 + 10\log_{10}(N_{RB}/24)$ | | +| | 60 | 10, 15, 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | $-96.5 + 10\log_{10}(N_{RB}/11)$ | | +| n79 | 15 | 10, 20, 30, 40, 50 | $-95.8 + 10\log_{10}(N_{RB}/52)$ | TDD | +| | 30 | 10, 20, 30, 40, 50, 60, 70, 80, 90, 100 | $-96.1 + 10\log_{10}(N_{RB}/24)$ | | +| | 60 | 10, 20, 30, 40, 50, 60, 70, 80, 90, 100 | $-96.5 + 10\log_{10}(N_{RB}/11)$ | | + +For UE(s) equipped with 4 Rx antenna ports, reference sensitivity for 2Rx antenna ports in Table 7.1.3.3-1a and in Table 7.1.3.3-1b shall be modified by the amount given in $\Delta R_{IB,4R}$ in Table 7.1.3.3-2 for the applicable operating bands. + +Table 7.1.3.3-2: Four antenna port reference sensitivity allowance $\Delta R_{IB,4R}$ + +| Operating band | $\Delta R_{IB,4R}$ (dB) | +|----------------|-------------------------| +| n1, n39 | -2.7 | +| n78, n79 | -2.2 | + +Table 7.1.3.3-3: Uplink configuration for reference sensitivity + +| Operating band / SCS (kHz) / Channel bandwidth (MHz) / Duplex mode | | | | | | | | | | | | | | | | | | +|--------------------------------------------------------------------|-----|----|-----------------|-----------------|------------------|------------------|------------------|----|------------------|------------------|------------------|-----|-----|-----|-----|-----|-------------| +| Operating Band | SCS | 5 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | 50 | 60 | 70 | 80 | 90 | 100 | Duplex Mode | +| n1 | 15 | 25 | 50 1 | 75 1 | 100 1 | 128 1 | 128 1 | | 128 1 | 128 1 | 128 1 | | | | | | FDD | +| | 30 | | 24 | 36 1 | 50 1 | 64 1 | 64 1 | | 64 1 | 64 1 | 64 1 | | | | | | | +| | 60 | | 10 1 | 18 | 24 | 30 1 | 30 1 | | 30 1 | 30 1 | 30 1 | | | | | | | +| n39 | 15 | 25 | 50 | 75 | 100 | 128 | 160 | | 216 | | | | | | | | TDD | +| | 30 | | 24 | 36 | 50 | 64 | 75 | | 100 | | | | | | | | | +| | 60 | | 10 | 18 | 24 | 30 | 36 | | 50 | | | | | | | | | +| n78 | 15 | | 50 | 75 | 100 | 128 | 160 | | 216 | | 270 | | | | | | TDD | +| | 30 | | 24 | 36 | 50 | 64 | 75 | | 100 | | 128 | 162 | 180 | 216 | 243 | 270 | | +| | 60 | | 10 | 18 | 24 | 30 | 36 | | 50 | | 64 | 75 | 90 | 100 | 120 | 135 | | +| n79 | 15 | | 50 | | 100 | | 160 | | 216 | | 270 | | | | | | TDD | +| | 30 | | 24 | | 50 | | 75 | | 100 | | 128 | 162 | 180 | 216 | 243 | 270 | | +| | 60 | | 10 | | 24 | | 36 | | 50 | | 64 | 75 | 90 | 100 | 120 | 135 | | + +#### 7.1.3.4 Maximum input level + +The calculation and results for maximum input level are listed in Table 7.1.3.4-1. The maximum input level is a compromise of the theoretical worst-case which assumes the 5 dBi UE element gain under the condition that the ATG UE antenna and BS antenna are not directly pointing to each other. + +**Table 7.1.3.4-1 the calculation for maximum input level requirements** + +| Parameters | Omni-directional antenna | phased array antenna | +|-------------------------|--------------------------|----------------------| +| Center frequency GHz | 2 | 4 | +| Distance meter | 3000 | 3000 | +| Pathloss dB | 108.063 | 114.0836 | +| ATG BS output power dBm | 46 | 53 | +| ATG BS antenna gain | 21 | 21 | +| ATG UE element gain | 0 | 5 | +| | | | +| maximum input level dBm | -42.063 | -35.0836 | + +Maximum input level is defined as the maximum mean power received at the UE antenna port, at which the specified relative throughput shall meet or exceed the minimum requirements for the specified reference measurement channel. For ATG, the maximum input level requirements are defined in Table 7.1.3.4-2 based on two types of UE antenna, i.e., omni-directional antenna and phased array antenna. + +**Table 7.1.3.4-2: Maximum input level for ATG** + +| Rx Parameter | Units | ATG UE Types | | Reference measurement channel | +|-----------------------------------------------|-------|------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|--------------------------------| +| | | Omni-directional antenna: receiver characteristics specified at the antenna connector(s) | Phased array antenna: receiver characteristics specified at transceiver array boundary (TAB) connectors | | +| Power in Transmission Bandwidth Configuration | dBm | -42 | -30 | A.3.2.3 or A.3.3.3 for 64 QAM | +| | | -44 | -32 | A.3.2.4 or A.3.3.4 for 256 QAM | +| The applicable channel bandwidths | MHz | 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 60, 70, 80, 90, 100 | | | + +NOTE 1: The transmitter shall be set to 4 dB below $P_{\text{CMAX\_L,f,c}}$ at the minimum uplink configuration specified in Table [7.3.2-3] with $P_{\text{CMAX\_L,f,c}}$ as defined in clause [6.2.4]. + +#### 7.1.3.5 Adjacent channel selectivity + +For ACS, the coexistence studies outcome shows that the legacy ACS values as for NR FR1 UE are appropriate, and therefore reused. + +The legacy ACS test parameters in case 1 is applied for ATG UE. ACS requirements in case 2 shall be specified based on the maximum input level of xdBm. + +#### 7.1.3.6 In-band blocking requirements + +##### Blocking due to TN interference + +Compared to terrestrial UE, ATG UEs are distant from base stations, experiencing LoS path loss from the TN BS that is not directly pointed at them. ATG UE at 2 GHz with omni-directional antennas, may receive power from multiple TN BSs. Even at 4 GHz, an ATG UE pointing downwards may still receive Rx power from the ground TN BS. + +To evaluate the TN's blocking power, simulations are conducted based on Scenario 3 and 11 (TN aggressor DL to ATG DL) and analyze the CDF of the absolute Rx power received by the ATG UE from the TN. The simulation is based on the following deployment scenarios: the ATG BS is located 300 km away from the center of the TN cluster and the ATG UEs x-coordinate is uniformly distributed over the horizontal extent of the TN cluster. The TN BSs utilize non-co-located 8-column non-subarray antennas. A single 5 dBi gain element has been used at the ATG UE at 4 GHz while an isotropic radiator is used at 2 GHz. + +At a CDF of 99.999%, the simulation shows that the Rx power for a uniform distribution of ATG UEs' altitude between 3 km and 10 km is -52 dBm and -56 dBm for 2 GHz and 4 GHz, respectively. For a fixed 10 km case, the Rx power is quite similar. A 6 dB difference can be observed in the fixed 3 km case, which is an unlikely scenario. Strictly following the simulation suggests -52 dBm in-band blocking, but it is essential to note that this relies on a 99.999% CDF. Lowering CDF to 99.99% is expected to yield lower interference at least several dB lower. + +Therefore, it is suggested to reuse the in-band blocking requirements in TS 38.101-1 for ATG UE. + +![Figure 7.1.3.6-1: Simulation results of ACI blocking for scenario 3. The graph shows the Cumulative Distribution Function (CDF) of ACI (dBm) for three scenarios: Uniform, Fixed 3 km, and Fixed 10 km. The x-axis represents ACI (dBm) from -85 to -45, and the y-axis represents CDF [%] from 0 to 100. The legend indicates the 99.999th percentile values for each scenario.](43cd26e92a1c09efb81d26db4787dcb6_img.jpg) + +| Scenario | 99.999 th perc. (dBm) | +|-------------|----------------------------------| +| Uniform | -52.1628 | +| Fixed 3 km | -48.1411 | +| Fixed 10 km | -59.3608 | + +Figure 7.1.3.6-1: Simulation results of ACI blocking for scenario 3. The graph shows the Cumulative Distribution Function (CDF) of ACI (dBm) for three scenarios: Uniform, Fixed 3 km, and Fixed 10 km. The x-axis represents ACI (dBm) from -85 to -45, and the y-axis represents CDF [%] from 0 to 100. The legend indicates the 99.999th percentile values for each scenario. + +Figure 7.1.3.6-1 Simulation results of ACI blocking for scenario 3. + +![Figure 7.1.3.6-2: Simulation results of ACI blocking for scenario 11. The graph shows the Cumulative Distribution Function (CDF) [%] of ACI (dBm) for three cases: Uniform, Fixed 3 km, and Fixed 10 km. The x-axis ranges from -85 to -50 dBm, and the y-axis ranges from 0 to 100%. The curves show that the Fixed 10 km case has the lowest ACI values, followed by Uniform, and then Fixed 3 km. The legend indicates the 99.999th percentile values for each case.](bb908297bfe73e2759a9dd88ae0506f9_img.jpg) + +| Case | 99.999 th perc. (dBm) | +|-------------|----------------------------------| +| Uniform | -55.8731 | +| Fixed 3 km | -54.8526 | +| Fixed 10 km | -59.7098 | + +Figure 7.1.3.6-2: Simulation results of ACI blocking for scenario 11. The graph shows the Cumulative Distribution Function (CDF) [%] of ACI (dBm) for three cases: Uniform, Fixed 3 km, and Fixed 10 km. The x-axis ranges from -85 to -50 dBm, and the y-axis ranges from 0 to 100%. The curves show that the Fixed 10 km case has the lowest ACI values, followed by Uniform, and then Fixed 3 km. The legend indicates the 99.999th percentile values for each case. + +Figure 7.1.3.6-2 Simulation results of ACI blocking for scenario 11. + +##### Blocking due to interference from another ATG network + +The co-existence simulations do not consider ATG-ATG co-existence. In the case of in-band blocking, the involvement of neighboring operators operating ATG could be significant. The most severe situation arises when co-located ATG BS direct their beams toward aircraft that are relatively close to each other and the BS. In such a case, the victim ATG UE could still be in the vicinity of the beam of the aggressor BS. Two scenarios are illustrated in 7.1.3.6-3, scenario 1 with two adjacent aircraft separated vertically by 300 m and scenario 2 with a 9.26 km horizontal separation. + +![Figure 7.1.3.6-3: Two scenarios when co-located BS pointing towards different aircraft that are relatively close. Scenario 1 shows two aircraft (Operator 1 UE and Operator 2 UE) separated vertically by 300 m, with Operator 1 BS and Operator 2 BS pointing towards them. Scenario 2 shows two aircraft (Operator 1 UE and Operator 2 UE) separated horizontally by 9.26 km, with Operator 1 BS and Operator 2 BS pointing towards them. Both scenarios show the vertical separation of the aircraft as 10 km.](49806c5ac206335a657bc126f17d37e8_img.jpg) + +Figure 7.1.3.6-3: Two scenarios when co-located BS pointing towards different aircraft that are relatively close. Scenario 1 shows two aircraft (Operator 1 UE and Operator 2 UE) separated vertically by 300 m, with Operator 1 BS and Operator 2 BS pointing towards them. Scenario 2 shows two aircraft (Operator 1 UE and Operator 2 UE) separated horizontally by 9.26 km, with Operator 1 BS and Operator 2 BS pointing towards them. Both scenarios show the vertical separation of the aircraft as 10 km. + +Figure 7.1.3.6-3 Two scenarios when co-located BS pointing towards different aircraft that are relatively close. + +Considering the FAA regulations mandating minimum aircraft separations of 300 m (1000 ft) vertically or 9.26 km (5 NM) horizontally in en-route airspace, one can estimate the angular separation. The victim aircraft could fall within the + +main lobe or the edge of the beam lobe towards the aggressor aircraft. Assuming 20 km distance from the ATG BS to the victim aircraft at a 10 km flight level, the angle separation is less than 1 deg in Scenario 1 and 15.4 deg in Scenario 2. + +In Scenario 1, the victim UE falls into the main lobe of the aggressor beam. Determining the EIRP of the victim involves utilizing the ATG BS output power from simulation parameters and accounting for free space path loss. For an ATG UE operating at 2 GHz, the EIRP is calculated to be - 72 dBm, significantly lower than the blocking caused by TN interference. Furthermore, the 300 m vertical separation is an absolute minimum distance and is very unlikely to occur during normal cruising in the same direction. + +Thus, it is not necessary to consider blocking from other ATG networks when assessing the in-band blocking requirement. + +#### 7.1.3.7 Out-of-Band blocking requirements/ Spurious response + +Referring to the ITU-R M.2059-0 [8], Tables 1 and 2 of ITU-R M.2059-0 provide technical characteristics for representative analogue and digital FMCW radio altimeters. In 3GPP, the ATG UE OOB specification is defined to ensure the telecommunication link and there may be other sources of interference and regulatory issues that need to be considered when designing ATG UE, i.e. avionic equipment. + +Thus, the existing out-of-band blocking requirements and spurious response requirement (-44dBm) in TS 38.101-1 are used for ATG UE. + +#### 7.1.3.8 Narrow band blocking requirements + +It was agreed not to specify narrow band blocking requirements for ATG UE. + +#### 7.1.3.9 Intermodulation characteristics + +Intermodulation response rejection is a measure of the receiver's capability to receive a wanted signal on its assigned channel frequency in the presence of two or more interfering signals with a specific frequency relationship to the wanted signal. + +It was agreed to reuse the intermodulation characteristics requirements specified in TS 38.101-1 for ATG UE. + +#### 7.1.3.10 Receiver Spurious emissions + +As this is regulatory requirements and referring to the ERC Recommendation 74-01 Annex 3 [3], the spurious emissions limits specified in sub-clause of TS 38.101-1[4] would also be applicable to ATG UE. + +## 7.2 ATG BS specific + +For most of the requirements, it was generally agreed to aim to reuse the existing TN BS requirements for ATG BS wherever possible since the TN BS requirements would provide the same or better BS performance for an ATG BS deployment. The following section will capture the considerations of ATG BS RF requirements. + +### 7.2.1 ATG BS class and BS type + +This WI study focus on FR1 bands only. After some discussion, the three BS FR1 types are specified for ATG BS, i.e. ATG BS type type1-C, 1-H and 1-O are defined. + +For the ATG BS class, the deployment scenarios were discussed. ATG BSs are supposed to be deployed on the ground to serve ATG UEs (CPE type of UE mounted in the aircraft) in the air. The flight altitude of ATG UE is supposed to turn on is assumed from 3~10km based on the regulatory input and coexistence study. The distance between aircraft and the nearest ATG BS in azimuth angle could be more than 200km and even up to 300km. So the scenario for ATG is different from existing scenarios for TN BS and scenario for HAPS. Separate BS classes for ATG need to be defined. + +For ATG BS type type1-C, 1-H and 1-O, ATG BS class is defined as below: + +ATG Base Stations are characterized by requirements derived from ATG scenarios with a ground BS to air UE with typical vertical altitude of around 10,000m and take-off/landing altitudes down to 3000m. + +Generally most of the WA BS class requirements can be reused by ATG BS. Some exceptions were found in the WI study, for example TAE requirement. The detail requirements study and conclusion are captured in the corresponding sections. + +### 7.2.2 Tx requirements + +#### 7.2.2.1 ATG Base station power + +##### Base station output power + +Considering the large coverage requirements of ATG system, only wide area BS is proper for ATG BS type 1-C, type 1-H and type 1-O. Similar to NR Wide area BS, there is no upper limit for the rated carrier output power, maximum output power should be left up to the declaration. The existing requirement defined in TS 38.104 [5] can be reused. + +##### RE power control dynamic range + +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 for a specified reference condition. + +The RE power control dynamic range was derived by considering the relation between RE power boosting/de-boosting and other RF requirements like UEM, ACLR and EVM. For ATG BS, since the same waveform as NR is used, the existing requirement defined in TS 38.104 [5] can be applicable. + +##### Total power dynamic range + +The BS total power dynamic range is the difference between the maximum and the minimum transmit power of an OFDM symbol for a specified reference condition. It can be calculated by $10\log_{10}(N_{RB})$ . The Total power dynamic range for ATG BS can reuse the requirement from TN BS in 3GPP TS 38.104 [5] for the same channel bandwidth. + +#### 7.2.2.2 Transmitted signal quality + +##### Frequency error + +Frequency error mainly depends on the timing and synchronization performance and PLL performance within transceiver chain. ATG system is expected to use the existing timing and synchronization network directly. Meanwhile, similar PLL performance of ATG BS as NR BS is also expected as they are operating at the same frequency range. With the above considerations, frequency error requirement of NR can be reused for ATG BS. + +Considering the 0.05ppm BS frequency error, for 2100 MHz, it is 105 Hz. For ATG system, UE velocity can be reach up 900-1200km/h at cruising speed, it can be seen that the more serious frequency offset is caused by the Doppler effect. The 0.05 ppm frequency offset has little impact on the system performance. + +##### **Time alignment error** + +For a specific set of NR signals/transmitter configurations/transmission modes, the conducted Time Alignment Error (TAE) is defined as the largest allowed timing difference (i.e. error) between two different reference signals belonging to different antenna connectors (for 1-C type NR BS), or *TAB connectors* (for 1-H type NR BS). + +TAE is only applicable for NR BS transmitting from multiple antennas via MIMO, CA, or combination of them. + +However, in ATG system, BS transmits signals from the ground to the air. Generally, these are only the main path signals, and few multipath signals. Thus, it's unnecessary to specify the MIMO TAE requirements for ATG BS. In addition, CA is not supported for ATG in Rel-18. As a result, no TAE requirements need to be developed for ATG BS. + +##### **Modulation quality** + +It is agreed to specify QPSK, 16QAM, 64QAM and 256QAM for ATG, for the supported modulation order is up to the vendor's declaration. + +For ATG BS, the EVM value of each carrier for different modulation schemes on PDSCH in TS 38.104 [5] shall be met. + +#### **7.2.2.3 Unwanted emission requirements** + +##### **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$ ( $=0.5\%$ ) of the total mean transmitted power. For ATG BS, it is agreed to reuse the same requirement defined in TS38.104 [5] which is following Recommendation ITU-R SM.328. + +##### **Adjacent Channel Leakage Power Ratio (ACLR)** + +Based on the coexistence simulation results, it is sufficient to reuse the legacy FR1 ACLR 45dBc requirement for ATG BS.. + +##### **Operating band unwanted emissions** + +ATG BS can follow Wide Area BS, that the UEM level in the spurious domain is aligned with ITU-R recommendation SM.329. + +#### **7.2.2.4 Transmitter spurious emissions** + +Since transmitter spurious emissions for TN BS should meet the requirements of ITU-R SM329, CEPT, and FCC etc., the spurious emission requirement defined in TS 38.104 [5] for TN BS is sufficient for ATG. + +The same spurious emission requirement defined in TS 38.104 [5] for TN BS can be reused. + +#### 7.2.2.5 Transmitter intermodulation + +In the standard discussion, it's supposed that there's no surrounding interfering BS with same bands existing for ATG BS. But some other scenarios were identified, for example, interfering signals from other bands or other asynchronous BS, also temporary interferers could occur close to the ATG BS. Therefore, it was agreed that it is important to verify that the ATG BS will still meet all emissions requirements, including regulatory requirements robustly. + +It was agreed that the Tx IM requirement in TS 38.104 [5] can be reused to guarantee the performance of the ATG BS. + +### 7.2.3 Rx requirements + +#### 7.2.3.1 Reference sensitivity level + +For reference sensitivity level because it is expected that the BS technology will be the same and hence the noise factor the same. The existing requirements specified in clause 7.2 of TS 38.104[5] can be reused for ATG BS type1-C, 1-H, and clause 10.3 of TS 38.104[5] can be reused for ATG BS type1-O. + +#### 7.2.3.2 Dynamic range + +For dynamic range because it is based on assumptions on the maximum interference level around the BS. Detailed investigation has not been made, but since the main difference between an ATG BS and TN BS is the tilt, it is not expected to be greater and may be expected sometimes to be similar to a TN BS. The existing requirements specified in clause 7.3 of TS 38.104[5] can be reused for ATG BS type1-C, 1-H, and clause 10.4 of TS 38.104[5] can be reused for ATG BS type1-O. + +#### 7.2.3.3 ACS + +The co-existence simulations demonstrate that if 46dBc ACS is applied for BS in ATG scenarios then the cross operator interference is acceptable (<5% degradation) in all scenarios. It is desirable to apply the same ACS as TN BS to maximize compatibility with BS hardware platforms. Thus, based on the simulation results, the ATG adjacent channel selectivity (ACS) reuse the existing FR1 ACS (i.e. 46dBc) requirement applied for TN BS. The existing requirements specified in clause 7.4 of TS 38.104[5] can be reused for ATG BS type1-C, 1-H, and clause 10.5 of TS 38.104[5] can be reused for ATG BS type1-O. + +#### 7.2.3.4 In-band blocking + +Since ATG BS is supposed to steer its beam up towards to provide the service for ATG UE in the air, the received power level of in-band blocking would be also lower than that for the legacy TN BS with beam steering down towards to provide the service on the ground. In addition, considering that it's agreed to reuse the FR1 BS ACS requirement [46dBc] for ATG BS, therefore it is also reasonable to reuse the in-band blocking requirement for FR1 WA BS for ATG BS. + +#### 7.2.3.5 Receiver intermodulation + +Regarding the Rx intermodulation, although it is not likely to have the coexistence scenario in which ATG BS is subject to intermodulation interferers with the power levels defined in FR1 WA Rx intermodulation requirement, Rx intermodulation still dimension some aspects of receiver design (e.g. receiver linearity to minimize the interfering signal intermodulation fall into the wanted signal). Therefore, it's still useful to keep the receiver intermodulation requirements and it is agreed to reuse the Rx IM requirement for FR1 WA BS for ATG BS. + +#### 7.2.3.6 Out of band blocking + +Since ATG BS is supposed to steer its beam up towards to provide the service for ATG UE in the air, the received OOB power level would be also lower than that for the legacy TN BS with beam steering down towards to provide the service on the ground, then it's sufficient to reuse the existing OOB requirement defined for Wide Area BS in TS38.104. + +#### 7.2.3.7 In-channel selectivity + +Since the IoT level of ATG BS is supposed to quite low compared with IoT level of the legacy TN BS. In addition, considering that noise figure for WA BS and FRC could be reused for ATG BS, then it's sufficient to reuse the existing requirement for Wide Area BS defined in TS 38.104. + +# --- 8 RRM requirements + +## 8.1 General + +In R18, the WI on ATG doesn't consider FR2, CA/DC and inter-RAT measurement scenario, the corresponding requirements are not applicable for R18 ATG. In light of ATG characteristics (e.g. ISD assumption of [14]-200km, maximum UE speed of 1200km/h, maximum distance between UE and BS is greater than [200]km), some RRM requirements are different from legacy ground-based network requirements, as listed in table 8-1. + +Editor's Note: In table 8-1, the RRM requirements with square brackets are still under discussion, which may be updated according to the latest agreements. + +**Table 8-1: RRM requirements for R18 ATG which are different from legacy ground-based network requirements** + +| Requirement | Item | Comments | +|-----------------------------------------|----------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Cell re-selection | Cell re-selection measurement requirements for intra-frequency measurement | Introduce scaling factor N for L3 measurements for ATG UEs with [antenna arrays]
N = 3 for the case when network assistance on ATG cells reference locations is provided:
N = 4 otherwise | +| | Cell re-selection measurement requirements for inter-frequency measurement | Define two set of cell detection requirements for ATG
Set 1: legacy R15 cell-reselection requirement
Set 2: R17 HST cell-reselection requirement
Introduce scaling factor N for L3 measurements for ATG UEs with [antenna arrays]
N = 3 for the case when network assistance on ATG cells reference locations is provided
N = 4 otherwise | +| Handover | Interruption time | For ATG UE with [antenna arrays], when network assistance on ATG unknown target cell's reference BS locations is provided, the $T_{search}$ should be scaled with scaling factor N= 2
when network assistance on ATG unknown target cell's reference BS locations is not provided, the $T_{search}$ should be scaled with scaling factor N=4 | +| Conditional handover | Conditional handover mechanism | Introduce location-based CHO for ATG, reusing the procedure in R17 NTN for R18 ATG | +| RRC Re-establishment delay requirement | UE Re-establishment delay requirement | For ATG UE with [antenna array]
Introduce scaling factor for unknown cell case
When network assistance on ATG cells reference location of the target cell is provided to UE, N = 3
Otherwise, N = 4 | +| RRC connection release with redirection | RRC connection release with redirection to NR | For ATG UE with [antenna array]
Introduce scaling factor
When network assistance on ATG cells reference location of the target cell is provided to UE, N = 3
Otherwise, N = 4 | +| UE transmit timing | Initial transmit timing requirements $T_e$ | Involve UE pre-compensation timing error, GNSS error=40m is assumed | +| | Gradual timing adjustment requirement | Involve the timing drift caused by UE mobility, 1200km/h is assumed. | +| | Timing advance adjustment delay requirement | Introduce the mechanism of $K_{offset}$ | +| Signalling characteristics | Radio link monitoring | Introduce the sharing factor for ATG UEs with [antenna arrays] | +| | Link recovery procedures | Introduce the sharing factor for ATG UEs with [antenna arrays] | + +| | | | +|----------------------------------------|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement procedure and requirements | NR intra-frequency measurements | For ATG TDD deployment, 'deriveSSB-IndexFromCell' is not always applicable for NR intra-frequency measurement.
For intra-frequency measurements without gap, Introduce scaling factor N for L3 measurements for ATG UEs with [antenna arrays]
N = 3 for the case when network assistance on ATG cells reference locations is provided
N = 4 otherwise
Introduce the sharing factor for ATG UEs with [antenna arrays] | +| | Inter-frequency measurements without measurement gap | Introduce scaling factor N for L3 measurements for ATG UEs with [antenna arrays]
N = 3 for the case when network assistance on ATG cells reference locations is provided
N = 4 otherwise
Introduce the sharing factor for ATG UEs with [antenna arrays] | +| | CSI-RS based intra-frequency measurements | For ATG TDD deployment, 'deriveSSB-IndexFromCell' is not always applicable for CSI-RS based intra-frequency measurement.
For intra-frequency measurements without gap, Introduce scaling factor N for L3 measurements for ATG UEs with [antenna arrays]
N = 3 for the case when network assistance on ATG cells reference locations is provided
N = 4 otherwise
Introduce the sharing factor for ATG UEs with [antenna arrays] | +| | L1-RSRP/SINR measurements for Reporting | Introduce the sharing factor for ATG UEs with [antenna arrays] | +| | Scheduling restrictions of UE performing measurements | Introduce additional scheduling restriction for ATG UEs with [antenna arrays] | + +For other RRM requirements, no new ATG specific requirements will be defined in R18. + +# 9 Conclusion + +RAN4 has performed the adjacent channel co-existence simulation between ATG network and TN network under the synchronized operation and non-synchronized operation assumptions. 4GHz and 2GHz are chosen as example bands using antenna array and omni-directional antenna at ATG UE side respectively. + +- The synchronized operation assumption is used to derive adjacent channel co-existence RF requirements, i.e., ACLR and ACS. Two kinds of layout have been conducted to simulate different location relationship between ATG UE and TN network, one for ATG UE on top of TN network and the other for ATG UE away from TN UE in azimuth. For adjacent channel co-existence, RAN4 has concluded to reuse legacy FR1 TN BS and UE RF requirements (i.e., ACLR and ACS) for ATG BS and UE, respectively. +- The non-synchronized operation assumption is used to analyze isolation distance between ATG BS and TN network based on derived ACLR and ACS from synchronization operation. Moreover, a total of 3 cases have + +been performed to describe different boresight relationship between ATG BS and nearest TN BS. ATG BS point directly at nearest TN BS in azimuth is the worst case. RAN4 conclusions for different propagation conditions and modeling have been summarized in Section 6.5. + +Besides, ATG specific operation bands are listed in clause 5 based on request from operators. It's noted this TR only encompass FR1 operation bands with larger than 1GHz frequency. + +RAN4 also studied the UE RF, BS RF, UE RRM requirement in Chapter 7.1, 7.2 and 8 respectively. Two kinds of UE RF and RRM requirements have been considered considering the implementation freedom for ATG UE with omni-directional antenna and/or antenna array. + +# 10 Required changes to NR, E-UTRA, UTRA and MSR specifications + +The required changes to the 3GPP specifications for the ATG are summarised in a Table 10-1. + +**Table 10-1: Overview of 3GPP specifications with required changes** + +| Affected existing specifications | | | | +|----------------------------------|-------------------|----------|--------------| +| Spec No. | Subject of the CR | Comments | CR/TP (Tdoc) | +| | | | | + +# Annex A: Calibration results of synchronized operation + +## A.1 Calibration assumptions + +The calibration assumptions is the same as listed in clause 6.2 and 6.3. + +## A.2 Calibration results at 2GHz and 4GHz + +Four kinds of performance metrics are used for synchronized operation calibration purpose which encompass Coupling Loss (CL), SINR without adjacent channel interference, SINR with adjacent channel interference from synchronized intra-system and SINR CDF with adjacent channel interference from synchronized inter-system. Following show detailed explanation for each performance metric in calibration excel file. + +- CL: coupling loss between transmitter and receiver +- SINR CDF without adjacent channel interference: Here the $SINR = S / (N + I_{ICI})$ where $I_{ICI}$ is the co-channel interference +- SINR CDF with adjacent channel interference from synchronization intra-system: Here the $SINR = S / (N + I_{ICI} + I_{ACI})$ . + - For TN, $I_{ACI}$ is from synchronized TN network using adjacent channel + - For ATG, due to we only consider one ATG BS and UE, $I_{ACI}$ and $I_{ICI}$ are both 0 + +- SINR CDF with adjacent channel interference from synchronization inter-system: Here the $\text{SINR} = \frac{S}{(N + I_{\text{ICI}} + I_{\text{ACI}})}$ . +- For TN, $I_{\text{ACI}}$ is from synchronized ATG network using adjacent channel +- For ATG, $I_{\text{ACI}}$ is from synchronized TN network using adjacent channel and $I_{\text{ICI}}$ is 0 + +The below linked sheet captures the data of calibration co-existence simulation study for all synchronized scenarios. More details on the assumptions can be found in the Cover page of the sheet. + +![Icon representing a spreadsheet file, with a green 'S' on a white background.](1f1e391c4625945115fe4f41a1c938e6_img.jpg) + +Icon representing a spreadsheet file, with a green 'S' on a white background. + +calibration for +synchronized sce + +# --- Annex B: Calibration results of non-synchronized operation + +## B.1 Calibration assumptions + +The calibration assumptions is the same as listed in clause 6.2 and 6.3. + +## B.2 Calibration results at 2GHz and 4GHz + +For non-synchronized operation, the performance metric to be calibrated would be the Cross coupling loss between ATG BS and TN BS with 0 azimuth angle (TN and ATG BS on the same horizontal line). besides, 5 km isolation distance is assumed between ATG BS and nearest TN BS. + +The below linked sheet captures the data of calibration co-existence simulation study for all non-synchronized scenarios. + +![Icon representing a spreadsheet file, with a green 'S' on a white background.](7085bb654c88de392054735bda2f6ad0_img.jpg) + +Icon representing a spreadsheet file, with a green 'S' on a white background. + +calibration for +non-synchronize + +# --- Annex C: Co-existence scenarios simulation data + +## C.1 Synchronized scenarios + +The below linked sheet captures the data of co-existence simulation study for all synchronized scenarios. More details on the assumptions can be found in the Cover page of the sheet. + +![Icon representing a synchronized scenario Co-existence sheet](bacc720ff6ea9195e4dddcee588abf83_img.jpg) + +Icon representing a synchronized scenario Co-existence sheet + +Synchronized +scenarios Co-existence + +## C.2 Non-Synchronized scenarios + +The below linked sheet captures the data of co-existence simulation results for non-synchronized scenarios. More details can be found in the Cover page of the sheet. + +Note: Some companies opted to only capture the results in the form of tables (Sub-clause 6.4.2) + +![Icon representing a non-synchronized scenarios co-existence sheet](16a61693d0828a2d2a156dc0e03d06f7_img.jpg) + +Icon representing a non-synchronized scenarios co-existence sheet + +Non-synchronized +scenarios co-existence + +# --- Annex D: Supplementary simulation results for co-existence synchronized scenarios + +This section comprises the additional simulation results captured during the early discussions for extra robustness of the ATG system. The simulation parameters are changed to check the influence on the simulation results. + +## D.1 Synchronized scenarios + +### D.1.1 Impact of the number of TN BS columns + +To protect the legacy deployments, it is important to highlight that 8-column AAS may not be satisfactory for all deployments in 2 GHz. With this consideration, this subsection points out the impact of the number of antenna columns in the TN BSs for 2 GHz carrier frequency. The results captured are for scenarios 9-12, where one and eight antenna columns at the TN are assumed using both sub-array and non-subarray configurations. + +The linked excel sheet provides detailed plots for the Scenarios 9-12. + +![Icon representing the Annex - Impact of the number of TN BS columns sheet](770a0d19a708e61d3fe65ae95092faed_img.jpg) + +Icon representing the Annex - Impact of the number of TN BS columns sheet + +Annex - Impact of +the number of TN BS + +It's noted that the number of TN BS columns study adopts the acceptable ACLR/ ACS values for all the scenarios. The 8-column cases seem to be the worst ones. The simulations results show varied degradation in some cases, but the variations don't make a large difference from the agreed requirements. Overall, the one and eight column antennas still follow the acceptable ACLR/ ACS requirements. + +### D.1.2 Impact of ATG UE antenna type + +This subsection points out the impact of the number of antenna array at the ATG UEs for 4 GHz frequency. The results captured are for scenarios 1-4, where 16x1 and 8x2 antenna array are compared. + +The linked excel sheet provides detailed plots for the Scenarios 1-4. + +![Icon representing an Excel file.](ee5335ab27424e6c83acfb46679a7f9b_img.jpg) + +Icon representing an Excel file. + +Annex - Impact of ATG UE antenna type + +It's noted the ATG UE antenna type study adopts the acceptable ACLR/ ACS values for all the scenarios. The 16x1 and 8x2 antenna array options have minimal differences in Scenarios 1, 2 and 4 for 4 GHz frequency. However, in Scenario 3, 16x1 antenna array seems to be the worst case for 5% throughput loss level. Though the differences are not that significant that would impact any of the acceptable ACLR/ ACS requirements as per the agreements. + +![Line graph titled 'SCENARIO 3 (Non-subarray model): Throughput Loss - 5% in the whole network - (20 to) 100km'. The Y-axis is 'Throughput Loss (%)' ranging from 0 to 25. The X-axis is 'ATG UE ACS (dB)' ranging from 23 to 43. Two lines are plotted: a blue line with circles for 'ATG UE 16x1 array' and a red line with circles for 'ATG UE 8x2 array'. Both lines show a decreasing trend as ACS increases, with the 16x1 array consistently showing higher throughput loss than the 8x2 array.](9a53e14a8faff0f95017f132e73e6bea_img.jpg) + +| ATG UE ACS (dB) | ATG UE 16x1 array (%) | ATG UE 8x2 array (%) | +|-----------------|-----------------------|----------------------| +| 23 | 23.5 | 18.5 | +| 24 | 20.5 | 16.0 | +| 25 | 17.5 | 13.5 | +| 26 | 15.0 | 11.5 | +| 27 | 12.5 | 9.5 | +| 28 | 10.5 | 8.0 | +| 29 | 8.5 | 6.5 | +| 30 | 7.0 | 5.0 | +| 31 | 5.5 | 4.0 | +| 32 | 4.5 | 3.0 | +| 33 | 3.5 | 2.5 | +| 34 | 2.5 | 2.0 | +| 35 | 2.0 | 1.5 | +| 36 | 1.5 | 1.0 | +| 37 | 1.0 | 0.8 | +| 38 | 0.8 | 0.6 | +| 39 | 0.6 | 0.5 | +| 40 | 0.5 | 0.4 | +| 41 | 0.4 | 0.3 | +| 42 | 0.3 | 0.2 | +| 43 | 0.2 | 0.1 | + +Line graph titled 'SCENARIO 3 (Non-subarray model): Throughput Loss - 5% in the whole network - (20 to) 100km'. The Y-axis is 'Throughput Loss (%)' ranging from 0 to 25. The X-axis is 'ATG UE ACS (dB)' ranging from 23 to 43. Two lines are plotted: a blue line with circles for 'ATG UE 16x1 array' and a red line with circles for 'ATG UE 8x2 array'. Both lines show a decreasing trend as ACS increases, with the 16x1 array consistently showing higher throughput loss than the 8x2 array. + +Figure D.1.2-1: Simulation results for Throughput Loss - 5% of users in the whole network + +### D.1.3 Impact of ATG-TN BS antennas collocation + +This subsection points out the impact of the TN and ATG BS collocation to identify the worst cases. The collocated deployments are the ones in which the ATG BS is located inside the TN cluster and the horizontal distance between ATG BS and ATG UE is in the range of [20, 100] km. Similarly, the non-collocated deployments are the ones in which the ATG BS is located 300 km away from the center of the TN cluster and ATG UEs x-coordinate is uniformly distributed over the horizontal extent of the TN cluster. + +The linked excel sheet provides detailed plots for the Scenarios 2, 3, 10 and 11. + +![Excel icon](0e32ab25c356a3b09f57f8011afd5ac8_img.jpg) + +Excel icon + +Annex - Impact of +ATG-TN BS antennas + +It's noted that the ATG-TN BS collocation study adopts the acceptable ACLR/ ACS values with the non-collocated deployment option as the worst case for most of the scenarios. In scenarios where it is observed the other way round, the differences are not that significant that would impact any of the acceptable ACLR/ ACS requirements as per the agreements. + +### D.1.4 Impact of ATG UE height distribution + +This subsection points out the impact of the ATG UE height distribution. The results shown are for cases when ATG UEs are uniformly distributed between 3 and 10 km heights, all ATG UEs have a fixed height of 3 km and all ATG UEs have a fixed height of 10 km. + +The linked excel sheet provides detailed plots for the Scenarios 1-4 and 9-12. + +![Excel icon](0efd6f12e56065db5c69e0c6619267e7_img.jpg) + +Excel icon + +Annex - Impact of +ATG UE height distribution + +It's noted that the ATG height distribution studied adopts the acceptable ATG ACLR/ ACS requirements in most of the scenarios. However, in scenarios 3 and 11 (as shown below), 3 km is the worst case, and the ATG UE ACS level is way above the accepted level of 33 dB. + +![Line graph titled 'SCENARIO 3 (Non-subarray model): Throughput Loss - 5% in the whole network - (20 to) 100km'. The Y-axis is 'Throughput Loss (%)' from 0 to 45. The X-axis is 'ATG UE ACS (dB)' from 23 to 43. Three lines are plotted: Uniform (blue), Fixed 3 km (red), and Fixed 10 km (green). The Fixed 3 km line shows the highest throughput loss, starting at ~39% at 23 dB and decreasing to ~1% at 43 dB. The Uniform line starts at ~23% and decreases to ~1%. The Fixed 10 km line shows the lowest loss, starting at ~9% and decreasing to ~1%.](7b833b1c4b833d2d706d8cb3aeca003c_img.jpg) + +| ATG UE ACS (dB) | Uniform (%) | Fixed 3 km (%) | Fixed 10 km (%) | +|-----------------|-------------|----------------|-----------------| +| 23 | 23 | 39 | 9 | +| 24 | 20 | 35 | 8 | +| 25 | 17 | 31 | 7 | +| 26 | 15 | 28 | 6 | +| 27 | 12 | 24 | 5 | +| 28 | 10 | 21 | 4 | +| 29 | 9 | 18 | 3 | +| 30 | 7 | 15 | 2 | +| 31 | 6 | 12 | 2 | +| 32 | 5 | 10 | 1 | +| 33 | 4 | 8 | 1 | +| 34 | 3 | 6 | 1 | +| 35 | 3 | 5 | 1 | +| 36 | 2 | 4 | 1 | +| 37 | 2 | 3 | 1 | +| 38 | 1 | 2 | 1 | +| 39 | 1 | 1 | 1 | +| 40 | 1 | 1 | 1 | +| 41 | 1 | 1 | 1 | +| 42 | 1 | 1 | 1 | +| 43 | 1 | 1 | 1 | + +Line graph titled 'SCENARIO 3 (Non-subarray model): Throughput Loss - 5% in the whole network - (20 to) 100km'. The Y-axis is 'Throughput Loss (%)' from 0 to 45. The X-axis is 'ATG UE ACS (dB)' from 23 to 43. Three lines are plotted: Uniform (blue), Fixed 3 km (red), and Fixed 10 km (green). The Fixed 3 km line shows the highest throughput loss, starting at ~39% at 23 dB and decreasing to ~1% at 43 dB. The Uniform line starts at ~23% and decreases to ~1%. The Fixed 10 km line shows the lowest loss, starting at ~9% and decreasing to ~1%. + +Figure D.1.4-1: Simulation results for Throughput Loss - 5% of users in the whole network + +![Line graph showing Throughput Loss (%) vs ATG UE ACS (dB) for three scenarios: Uniform, Fixed 3 km, and Fixed 10 km. The graph shows that throughput loss decreases as ATG UE ACS increases. The 'Fixed 3 km' scenario shows the highest throughput loss, while 'Fixed 10 km' shows the lowest.](ce4bc97f7f5e2c454b76ddbda454455c_img.jpg) + +**SCENARIO 11 (Non-subarray model): Throughput Loss - 5% in the whole network - (20 to) 100km** + +| ATG UE ACS (dB) | Uniform (%) | Fixed 3 km (%) | Fixed 10 km (%) | +|-----------------|-------------|----------------|-----------------| +| 23 | 26 | 39 | 8 | +| 24 | 23 | 35 | 6 | +| 25 | 20 | 32 | 5 | +| 26 | 17 | 29 | 4 | +| 27 | 14 | 25 | 3 | +| 28 | 11 | 22 | 2 | +| 29 | 9 | 19 | 2 | +| 30 | 7 | 16 | 1 | +| 31 | 6 | 14 | 1 | +| 32 | 5 | 12 | 1 | +| 33 | 4 | 10 | 1 | +| 34 | 3 | 8 | 1 | +| 35 | 2 | 7 | 1 | +| 36 | 2 | 6 | 1 | +| 37 | 1 | 5 | 1 | +| 38 | 1 | 4 | 1 | +| 39 | 1 | 3 | 1 | +| 40 | 1 | 3 | 1 | +| 41 | 1 | 2 | 1 | +| 42 | 1 | 2 | 1 | +| 43 | 1 | 2 | 1 | + +Line graph showing Throughput Loss (%) vs ATG UE ACS (dB) for three scenarios: Uniform, Fixed 3 km, and Fixed 10 km. The graph shows that throughput loss decreases as ATG UE ACS increases. The 'Fixed 3 km' scenario shows the highest throughput loss, while 'Fixed 10 km' shows the lowest. + +**Figure D.1.4-2: Simulation results for Throughput Loss - 5% of users in the whole network** + +It is possible that ATG UE suffers degradation during take-off and landing i.e., at 3 km. A certain throughput loss higher than 5% maybe be acceptable, as far as the ATG network doesn't break off when ATG UEs are at a height of 3 km. + +# --- Annex E (informative): + +# Change history + +| Change history | | | | | | | | +|----------------|-------------|------------|----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 08/2022 | RAN4#104-e | R4-2214912 | | | TR skeleton | N/A | 0.0.1 | +| 11/2022 | RAN4#105 | R4-2218030 | | | R4-2215335 TP for ATG TR 38.876 skeleton
R4-2217504 TP for TR 38.876 | 0.0.1 | 0.1.0 | +| 02/2023 | RAN4#106 | R4-2301861 | | | R4-2220826 TP for TR 38.876: frequency error
R4-2220539 TP for TR 38.876 to capture general assumptions
R4-2220540 TP for TR 38.876 to capture scenarios and network layout
R4-2220541 TP for TR 38.876 to capture system parameter assumption and antenna modelling | 0.1.0 | 0.2.0 | +| 04/2023 | RAN4#106bis | R4-2303640 | | | R4-2302096 TP for TR 38.876 to add some coexistence assumption and methodology
R4-2303641 TP for TR 38.876 to capture system parameter assumption
R4-2303642 TP to TR 38.876: Update of simulation assumptions
R4-2303643 TP for TR 38.876 to introduce ATG UE Tx requirements
R4-2303644 TP for TR 38.876 to introduce technical analysis for ATG UE Rx requirements.
R4-2303227 TP to TR 38.876: RRM requirements for ATG network
R4-2302905 TP for TR 38.876 on BS RF requirements | 0.2.0 | 0.3.0 | +| 05/2023 | RAN4#107 | R4-2309106 | | | R4-2310402 TP for TR 38.876 to add Annex, CMCC
R4-2310494 TP to TR 38.876: Skeleton for Co-existence simulation results, Ericsson
R4-2310404 TP for TS 38.876: Clause 6.1~6.3, ZTE Corporation
R4-2310405 TP for TR38.876:clause 7.1 and 7.1.1, ZTE Corporation
R4-2310406 TP for TR 38.876 to introduce ATG UE Tx requirements part 1, Huawei, HiSilicon
R4-2309169 TP for TR38.876 :clause 7.2.3.4~7.2.3.7, ZTE Corporation
R4-2309761 TP for TR 38.876 to introduce ATG BS Rx requirements, CMCC
R4-2310056 TP to TR 38.876 RRM requirements for ATG network, CMCC | 0.3.0 | 0.4.0 | +| 08/2023 | RAN4#108 | R4-2312291 | | | R4-2311266, TP to TR 38.876: Addition of Co-existence simulation results for Synchronized Scenarios, Ericsson
R4-2311458, TP for TR 38.876 on BS RF requirements, Huawei, HiSilicon
R4-2313501, TP for TR 38.876: General aspects, Apple
R4-2313502, TP for TR 38.876: ATG UE Tx requirement, Apple
R4-2314451, TP to TR 38.876: RRM requirements for ATG network, CMCC
R4-2314758, TP to TR 38.876: Extra results of co-existence synchronized scenarios in Annexure, Ericsson
R4-2314760, TP for TR 38.876 to introduce ATG UE Tx requirements part 1, Huawei, HiSilicon | 0.4.0 | 0.5.0 | +| 10/2023 | RAN4#108bis | R4-2315904 | | | R4-2317745, TP for TR 38.876 to introduce minimum output power requirements for ATG UE, Huawei, HiSilicon
R4-2317746 TP for TR 38.876 to introduce some consideration for OOB requirements, Huawei, HiSilicon
R4-2315197, TP for ATG TR annex calibration part, CMCC
R4-2315443 TP for TR 38.876 Addition of Summary for synchronized scenarios simulation results, Ericsson
R4-2316518 TP to TR 38.876 In-band blocking, Ericsson
R4-2316719, TP on TR 38.876 for ATG UE Rx requirements - Part 1, Qualcomm Incorporated
R4-2317741, TP for TR 38876 - section 1 to section 6, CMCC | 0.5.0 | 0.6.0 | + +| | | | | | | | | +|---------|----------|------------|--|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------| +| 11/2023 | RAN4#109 | R4-2319706 | | | R4-2318921, TP for TR 38.876 to add non-synchronized calibration part for ATG TR, CMCC
R4-2319726 TP to TR 38.876 Updated non-synchronized scenarios network layout model, Ericsson
R4-2319727 TP to TR 38.876 Addition of co-existence simulation results for ATG non-synchronized scenarios, Ericsson
R4-2321911 TP for TR 38.876 to add conclusion part and update omni-directional terminology and other description, CMCC
R4-2321912 TP for TR 38.876 to maintain the Tx RF requirements for ATG UE, Huawei, HiSilicon
R4-2319798 TP to TR 38.876 on intermodulation characteristics, Ericsson
R4-2321916 TP to TR 38.876 on ATG UE Maximum input level, Qualcomm Incorporated
R4-2318902 TP to TR 38.876: RRM requirements for ATG network, CMCC | 0.6.0 | 0.7.0 | +| 12/2023 | RAN#102 | RP-233520 | | | Provide endorsed Draft TR to RAN plenary meeting for one step approval. | 0.7.0 | 1.0.0 | +| 12/2023 | RAN#102 | RP-234022 | | | Update TR title compared to version 1.0.0 | 1.0.0 | 1.0.1 | + +| 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/38_series/38877/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/Rel-18/38_series/38877/09955ff8214ffb6947951fc0f60eb6ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cccb6f7bd468c1115c3a450449df26686a883246 --- /dev/null +++ b/marked/Rel-18/38_series/38877/09955ff8214ffb6947951fc0f60eb6ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cdbc8d29afee13e6e7bbcb4da39b53bd30e208fb0b05b79988c3e261ae5a6b8f +size 23739 diff --git a/marked/Rel-18/38_series/38877/19a59d6b53059ebd27b13c98793f88e0_img.jpg b/marked/Rel-18/38_series/38877/19a59d6b53059ebd27b13c98793f88e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45add78db7462fee8109aee5bc61b8639c70458a --- /dev/null +++ b/marked/Rel-18/38_series/38877/19a59d6b53059ebd27b13c98793f88e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0833d92c3e66c95c418c1b876e4f61316c3c5a5e32d69aed95d61d69ad40ecda +size 39778 diff --git a/marked/Rel-18/38_series/38877/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg b/marked/Rel-18/38_series/38877/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2436e20b3c20c15ffafeb4cbc5a056e70b8fd933 --- /dev/null +++ b/marked/Rel-18/38_series/38877/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bcc6fcfad4dac149726df6d07aa514dba4fb407bd6a8a7550dbe2d025916b1c +size 114222 diff --git a/marked/Rel-18/38_series/38877/20e597e389dfd8d131e05ad6e1617dcd_img.jpg b/marked/Rel-18/38_series/38877/20e597e389dfd8d131e05ad6e1617dcd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..682072eae599546ba06421118bae87a6aef62407 --- /dev/null +++ b/marked/Rel-18/38_series/38877/20e597e389dfd8d131e05ad6e1617dcd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2ab0eed2e03ebd32445dfd75bf5e9457f17d268c8318f1aa60117b9475f8610 +size 36442 diff --git a/marked/Rel-18/38_series/38877/45329c7d9aa2bd1290af5b2027f08d7e_img.jpg b/marked/Rel-18/38_series/38877/45329c7d9aa2bd1290af5b2027f08d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..761319d26388f747c0ec58831bd8f346f71a2ae3 --- /dev/null +++ b/marked/Rel-18/38_series/38877/45329c7d9aa2bd1290af5b2027f08d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:663b8667ee26140a2fc4dcde30892007916fdea0cc66fa72b95288a16e8dea42 +size 129584 diff --git a/marked/Rel-18/38_series/38877/47e75dc9e83054b2dac3df8bf3e57019_img.jpg b/marked/Rel-18/38_series/38877/47e75dc9e83054b2dac3df8bf3e57019_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5e668c9947d3c3e1a179e08bf6add8438f40ad7 --- /dev/null +++ b/marked/Rel-18/38_series/38877/47e75dc9e83054b2dac3df8bf3e57019_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c818c7980c55cc3e103d15b7a2caa9b6ec4cd9f665195f07011c08faf81e70c +size 83282 diff --git a/marked/Rel-18/38_series/38877/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38877/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85cdaf256639cc597b38bba48f0da8f112972456 --- /dev/null +++ b/marked/Rel-18/38_series/38877/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08c35d3572176229430d0f4573390dd4211222595f5fa113313a9fa20d7e4b08 +size 9407 diff --git a/marked/Rel-18/38_series/38877/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38877/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03f8aec44dc15458de1e122ee5b4632554aa6b91 --- /dev/null +++ b/marked/Rel-18/38_series/38877/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e6ca3eeff51b5ee7954a05df3d6a2fe959564e16cb9623f616003061a8ca9c3 +size 5810 diff --git a/marked/Rel-18/38_series/38877/6b09b11992389190c93c33a3e80d6fa9_img.jpg b/marked/Rel-18/38_series/38877/6b09b11992389190c93c33a3e80d6fa9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0c447f2af31f7f4d756c3676095ed2beb6cc365 --- /dev/null +++ b/marked/Rel-18/38_series/38877/6b09b11992389190c93c33a3e80d6fa9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e333e6f246b69ed1be8839210eb50b1ce95b736f58436f4f56703dd28937560e +size 20662 diff --git a/marked/Rel-18/38_series/38877/6e5a85131eedf6b98db62877ee64506e_img.jpg b/marked/Rel-18/38_series/38877/6e5a85131eedf6b98db62877ee64506e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc3a52c25d986d54c3648831a58fd7c9ca88d7cd --- /dev/null +++ b/marked/Rel-18/38_series/38877/6e5a85131eedf6b98db62877ee64506e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f9ee02748900e304ddf8015b9b7dad1f5881b088508170c6def06661cc63b42 +size 83670 diff --git a/marked/Rel-18/38_series/38877/853f59c89931a666c07903b31d098277_img.jpg b/marked/Rel-18/38_series/38877/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e160d4ed1ee916d5b5f4569584e906ab5b7ca745 --- /dev/null +++ b/marked/Rel-18/38_series/38877/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd273f5dd94bafb252ad4fbdab34ae65a7d4421695008912e35321035ce3dfed +size 97560 diff --git a/marked/Rel-18/38_series/38877/85b10db535b22e64c7d37f362705ddbf_img.jpg b/marked/Rel-18/38_series/38877/85b10db535b22e64c7d37f362705ddbf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c527db6ad137d60b215ef7c435c9fc0acc01900 --- /dev/null +++ b/marked/Rel-18/38_series/38877/85b10db535b22e64c7d37f362705ddbf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbeba1832eb7a63ca40c6f3d1487500a4d5d003de4a101e4d60d12aaf308d9c5 +size 99678 diff --git a/marked/Rel-18/38_series/38877/8a597e344d10e36bbb2f243f6c4e74c6_img.jpg b/marked/Rel-18/38_series/38877/8a597e344d10e36bbb2f243f6c4e74c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03cb38298909dd84c867577cbafe9a3845ad6fef --- /dev/null +++ b/marked/Rel-18/38_series/38877/8a597e344d10e36bbb2f243f6c4e74c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3037393954ec1f556710a118adfe8e1ff7967fc9d6c139b9a12c53eac334bc0d +size 20023 diff --git a/marked/Rel-18/38_series/38877/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-18/38_series/38877/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35f4b4bf5dd259debe82e09d6cdeaf7985ff15ce --- /dev/null +++ b/marked/Rel-18/38_series/38877/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b61889f5344209b9c65608c4b8d4ad43706fdfb40c3ef73056299ed9855e8baa +size 38144 diff --git a/marked/Rel-18/38_series/38877/98ff4ec9e120afa420dbe08b0d8d77b6_img.jpg b/marked/Rel-18/38_series/38877/98ff4ec9e120afa420dbe08b0d8d77b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16de8c2748308414521380e344829fb8f0bce6cf --- /dev/null +++ b/marked/Rel-18/38_series/38877/98ff4ec9e120afa420dbe08b0d8d77b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afba276772f4576493637c80bddf964f4859e3b63aa50add6ad51b1e3964e7df +size 73149 diff --git a/marked/Rel-18/38_series/38877/9cd90f495b95ad2116ff780248c26d95_img.jpg b/marked/Rel-18/38_series/38877/9cd90f495b95ad2116ff780248c26d95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c6cc22477ba195433906391131c4a7a0909df30 --- /dev/null +++ b/marked/Rel-18/38_series/38877/9cd90f495b95ad2116ff780248c26d95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22e594eb5e3be3480a903c0fbf9dd03dd8536d5cc6f3ccf93cb734ebfd976fd1 +size 51943 diff --git a/marked/Rel-18/38_series/38877/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/marked/Rel-18/38_series/38877/b2ea162a0f53d5e0504b7d28346e0754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8b2b37ba156b32d9cc4ed7256785cc9402e1202 --- /dev/null +++ b/marked/Rel-18/38_series/38877/b2ea162a0f53d5e0504b7d28346e0754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d542a4e2e068a32cec2b6f2702aeaabfd26ae461ddc54af7036f9953417dbc80 +size 26008 diff --git a/marked/Rel-18/38_series/38877/bb3354f497635d15bef873577125c48d_img.jpg b/marked/Rel-18/38_series/38877/bb3354f497635d15bef873577125c48d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0780c424a7e08a0b086ef4b2480713977ab0193 --- /dev/null +++ b/marked/Rel-18/38_series/38877/bb3354f497635d15bef873577125c48d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51ac7e90c2eab171d937ab3f83fdd71612cbdb73ccf3a55755a58ae2a34c568b +size 35727 diff --git a/marked/Rel-18/38_series/38877/bd4617f25d15430eb78c2d6d75a99dde_img.jpg b/marked/Rel-18/38_series/38877/bd4617f25d15430eb78c2d6d75a99dde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ba74b0e52aa21244598b75f36f7b07fafcfc638 --- /dev/null +++ b/marked/Rel-18/38_series/38877/bd4617f25d15430eb78c2d6d75a99dde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed7ace5946db482706a10975517d84169aa92d507528eee73d99739cc9b3bde0 +size 86007 diff --git a/marked/Rel-18/38_series/38877/d8d893dd559845f86c5dd46147ef98b6_img.jpg b/marked/Rel-18/38_series/38877/d8d893dd559845f86c5dd46147ef98b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..461178702429d1a964dad590a25af46d3631f6e5 --- /dev/null +++ b/marked/Rel-18/38_series/38877/d8d893dd559845f86c5dd46147ef98b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c13cedf493c71daf6a6c6ccaaf68d843f0481a8b462e51c5e1e9bd87b1a79315 +size 43286 diff --git a/marked/Rel-18/38_series/38877/e9b43ac020435f8121e8592f31afdc52_img.jpg b/marked/Rel-18/38_series/38877/e9b43ac020435f8121e8592f31afdc52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff2847deed4a1b0adbd3049197a0cf46cd46e453 --- /dev/null +++ b/marked/Rel-18/38_series/38877/e9b43ac020435f8121e8592f31afdc52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c23a978dba975546e4f585772a773af9d09a65e634e00c12f33786425adc1772 +size 23025 diff --git a/marked/Rel-18/38_series/38877/eb5834a9eafc9eba7a2b597b13afbbed_img.jpg b/marked/Rel-18/38_series/38877/eb5834a9eafc9eba7a2b597b13afbbed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9a54ea84fcd6048895ec05a58ef6758922ce8ac --- /dev/null +++ b/marked/Rel-18/38_series/38877/eb5834a9eafc9eba7a2b597b13afbbed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29ad54092562e184dadd7517b3a181c77c9b656cb87a8fa41182e35c8347a2a7 +size 30139 diff --git a/marked/Rel-18/38_series/38877/f1c3ae01c82d4410b559fad6174a2f1a_img.jpg b/marked/Rel-18/38_series/38877/f1c3ae01c82d4410b559fad6174a2f1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1181ee376c2ddf84725d6753107b78898c926caf --- /dev/null +++ b/marked/Rel-18/38_series/38877/f1c3ae01c82d4410b559fad6174a2f1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7b8d777d489e1bf90353b34f8949353c75d054cb09bf9be3cb1a446e5d4b4a5 +size 91188 diff --git a/marked/Rel-18/38_series/38877/raw.md b/marked/Rel-18/38_series/38877/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5b28fc7cd319c147158959d31dfb7dadead01ebc --- /dev/null +++ b/marked/Rel-18/38_series/38877/raw.md @@ -0,0 +1,1024 @@ + + +# 3GPP TR 38.877 V18.1.0 (2023-09) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on NR mmWave MB-BS (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. There is a small red signal wave icon under the 'G'. + +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..... | 8 | +| 3.1 Terms..... | 8 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 10 | +| 4 General..... | 11 | +| 4.1 Study item objective..... | 11 | +| 4.2 Deployment scenarios ..... | 11 | +| 4.2.1 Architecture options ..... | 12 | +| 5 Feasibility study ..... | 13 | +| 5.1 General ..... | 13 | +| 5.2 Wideband RF architectures ..... | 14 | +| 5.2.1 RF Front end..... | 14 | +| 5.2.1.1 General..... | 14 | +| 5.2.1.2 Beam former and PA ..... | 14 | +| 5.2.1.3 Receiver front end..... | 16 | +| 5.2.1.4 Summary ..... | 17 | +| 5.2.2 Digital Pre-distortion ..... | 17 | +| 5.2.2.1 DPD for FR2 single-band BS ..... | 17 | +| 5.2.2.2 DPD for FR2 multiband BS..... | 19 | +| 5.2.3 Phase shifter..... | 20 | +| 5.3 Wideband antenna architectures..... | 22 | +| 5.3.1 General ..... | 22 | +| 5.3.2 Single array bandwidth..... | 23 | +| 5.3.3 Interleaved array structures ..... | 25 | +| 5.3.4 MIMO EM simulation results ..... | 27 | +| 5.3.5 Diplexer technology ..... | 29 | +| 5.4 Other..... | 30 | +| 6 Study on RF requirements..... | 31 | +| 6.1 Definition of FR2 multi-band BS..... | 31 | +| 6.2 Re-using FR1 multi-band methods ..... | 32 | +| 6.3 Re-using FR1 exceptions ..... | 32 | +| 6.4 FR2-1 specific multi-band requirements..... | 33 | +| 7 Summary and further work ..... | 33 | +| Annex A (informative): Change history..... | 34 | + +# 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 the Technical Report for the Study Item on BS RF requirement evolution dealing with FR2 multi-band BS 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 38.104: "NR; Base Station (BS) radio transmission and reception". +- [3] 3GPP TR 37.840: "Study of Radio Frequency (RF) and Electromagnetic Compatibility (EMC) requirements for Active Antenna Array System (AAS) base station" +- [4] Rusek, Fredrik, et al. "Scaling up MIMO: Opportunities and challenges with very large arrays." IEEE signal processing magazine 30.1 (2012): 40-60. +- [5] Fager, Christian, et al. "Linearity and efficiency in 5G transmitters: New techniques for analyzing efficiency, linearity, and linearization in a 5G active antenna transmitter context." IEEE Microwave Magazine 20.5 (2019): 35-49. +- [6] Tervo, Nuutti, et al. "Analyzing the effects of PA variations on the performance of phased array digital predistortion." 2018 IEEE 29th Annual International Symposium on Personal, Indoor and Mobile Radio Communications (PIMRC). IEEE, 2018. +- [7] Jalili, Feridoon, et al. "Linearization trade-offs in a 5G mmWave active phased array OTA setup." Ieee Access 8 (2020): 110669-110677. +- [8] Khan, Bilal, et al. "Statistical Digital Predistortion of 5G Millimeter-Wave RF Beamforming Transmitter Under Random Amplitude Variations." IEEE Transactions on Microwave Theory and Techniques 70.9 (2022): 4284-4296. +- [9] Ng, Eric, et al. "Digital predistortion of millimeter-wave RF beamforming arrays using low number of steering angle-dependent coefficient sets." IEEE Transactions on Microwave Theory and Techniques 67.11 (2019): 4479-4492. +- [10] Larsson, Erik G., and Liesbet Van der Perre. "Out-of-band radiation from antenna arrays clarified." IEEE Wireless Communications Letters 7.4 (2018): 610-613. +- [11] Haider, Muhammad Furqan, et al. "Predistortion-Based Linearization for 5G and Beyond Millimeter-Wave Transceiver Systems: A Comprehensive Survey." IEEE Communications Surveys & Tutorials (2022). +- [12] ADI, Technical article, "Why Millimeter Wave Requires a Different Approach to DPD and How to Quantify Its Value" +- [13] Abdelaziz, Mahmoud, et al. "Digital predistortion for hybrid MIMO transmitters." IEEE Journal of Selected Topics in Signal Processing 12.3 (2018): 445-454. + +- [14] Design and linearization of concurrent dual-band Doherty PA with frequency-dependent power ranges, Chen W H, Bassam S A, Li X, et al. IEEE Trans Microw Theory Tech, 2011, 59:2537–2546 +- [15] Wu, Qian, et al. "Digital Predistortion for Concurrent Dual-Band Millimeter Wave Analog Multibeam Transmitters." IEEE Transactions on Circuits and Systems II: Express Briefs 69.3 (2021): 1747-1751. +- [16] Li, Yue, Xiaoyu Wang, and Anding Zhu. "Sampling rate reduction for digital predistortion of broadband RF power amplifiers." IEEE Transactions on Microwave Theory and Techniques 68.3 (2019): 1054-1064. +- [17] Yu, Chao, et al. "Linear-decomposition digital predistortion of power amplifiers for 5G ultrabroadband applications." IEEE Transactions on Microwave Theory and Techniques 68.7 (2020): 2833-2844. +- [18] 3GPP R4-2219154: “Further discussion on phase shifters”, Huawei, HiSilicon. +- [19] 28/38 GHz Dual-band Dual-polarized Highly Isolated Antenna for 5G Phased Array Applications, Chenhao Chu et.al, University College Dublin, IEEE IWS 2019: Sixth IEEE MTT-S International Wireless Symposium, Guangzhou, China, 19-22 May 2019 +[https://researchrepository.ucd.ie/bitstream/10197/11051/2/Antenna%20for%205G%20Phased%20Array\\_IWS2019\\_CChu.pdf](https://researchrepository.ucd.ie/bitstream/10197/11051/2/Antenna%20for%205G%20Phased%20Array_IWS2019_CChu.pdf) +- [20] A Compact Dual-Band and Dual-Polarized Millimeter-Wave Beam Scanning Antenna Array for 5G Mobile Terminals, Yuqi He et.al, Xidian University, + +- [21] Dual-Band Dual-Polarized Microstrip Antenna Array Using Double-Layer Gridded Patches for 5G Millimeter-Wave Applications, Wangyu Sun et.al, IEEE Transactions On Antennas And Propagation, Vol. 69, No. 10, October 2021 +- [22] A 32-Element 28/39 GHz Dual-Band Dual-Beam 5G Phased-Array with 40 dBm EIRP and Simultaneous 64 QAM Operation, Shufan Wang et al., University of California San Diego, USA, 2022 IEEE/MTT-S International Microwave Symposium, + +- [23] Antenna diversity in mobile communications, R. G. Vaughan et al., IEEE Transactions on Vehicular Technology, Vol. 36, No. 4, November 1987, + +- [24] R4-2215413: "General consideration on mmWave multi-band BS". +- [25] An Instantaneously Broadband Ultra-Compact Highly Linear PA with Compensated Distributed-Balun Output Network Achieving >17.8dBm P1dB and >36.6% PAE1dB over 24 to 40GHz and Continuously Supporting 64-/256-QAM 5G NR Signals over 24 to 42GHz, Fei Wang, Hua Wang, ISSCC 2020 / session 24 / RF & mm-Wave power amplifiers / 24.6, + +- [26] A 26-to-39GHz Broadband Ultra-Compact High-Linearity Switchless Hybrid N/PMOS Bi-Directional PA/LNA Front-End for Multi-Band 5G Large-Scaled MIMO System, ISSCC 2022 / Session 19 / power amplifiers and building blocks / 19.4, Jeongsoo Park1, +- [27] A Mm-Wave Wideband MIMO RX With Instinctual Array-Based Blocker/Signal Management for Ultralow-Latency Communication, Min-Yu Huang, et al., IEEE Journal Of Solid-State Circuits, Vol. 54, No. 12, December 2019 +- [28] A Power-Efficient 24-to-71GHz CMOS Phased-Array Receiver Utilizing Harmonic-Selection Technique Supporting 36dB Inter-Band Blocker Rejection for 5G NR, Jian Pang et al., ISSCC 2022 / Session 27 / mm-Wave & Sub-6GHz receivers and transceivers for 5g radios / 27.2, + +- [29] A 22–44-GHz Phased-Array Receive Beamformer in 45-nm CMOS SOI for 5G Applications With 3–3.6-dB NF, Li Gao et al., IEEE Transactions on Microwave Theory and Techniques, Vol. 68, No. 11, November 2020 + +- [30] 3GPP TS 38.141-2: "NR; Base Station (BS) conformance testing, Part 2: Radiated conformance testing". +- [31] 3GPP TR 38.901: "Study on channel model for frequencies from 0.5 to 100 GHz" + +# 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]. + +**array element:** subdivision of a passive *antenna array*, consisting of a single radiating element or a group of radiating elements, with a fixed radiation pattern + +**antenna array:** group of radiating elements characterized by the geometry and the properties of the *array elements* + +**Base Station RF Bandwidth:** RF bandwidth in which a base station transmits and/or receives single or multiple carrier(s) within a supported *operating band* + +NOTE: In single carrier operation, the *Base Station RF Bandwidth* is equal to the *BS channel bandwidth*. + +**beam:** beam (of the antenna) is the main lobe of the radiation pattern of an *antenna array* + +NOTE: For certain AAS BS *antenna array*, there may be more than one beam. + +**BS channel bandwidth:** RF bandwidth supporting a single NR RF carrier with the *transmission bandwidth* configured in the uplink or downlink + +NOTE 1: The *BS channel bandwidth* is measured in MHz and is used as a reference for transmitter and receiver RF requirements. + +NOTE 2: It is possible for the BS to transmit to and/or receive from one or more UE bandwidth parts that are smaller than or equal to the *BS transmission bandwidth configuration*, in any part of the *BS transmission bandwidth configuration*. + +**BS transmission bandwidth configuration:** set of resource blocks located within the *BS channel bandwidth* which may be used for transmitting or receiving by the BS + +**BS type 1-O:** NR base station operating at FR1 with a requirement set consisting only of OTA requirements defined at the RIB + +**BS type 2-O:** NR base station operating at FR2 with a requirement set consisting only of OTA requirements defined at the RIB + +**directivity:** ratio of the radiation intensity in a given direction from the antenna to the radiation intensity averaged over all directions + +NOTE: If the direction is not specified, the direction of maximum radiation intensity is implied. + +**equivalent isotropic radiated power:** in a given direction, the relative *antenna gain* of a transmitting antenna with respect to the *antenna gain* of an isotropic radiating element multiplied by the net power accepted by the antenna from the connected transmitter + +NOTE: For an AAS BS the EIRP can be seen as the equivalent power radiated from an isotropic radiating element, producing the same field intensity as the field intensity radiated in the declared beam pointing direction of the active antenna system being considered. + +**equivalent isotropic sensitivity:** power level relative to an isotropic antenna that is required to be incident on the AAS BS array from a specified azimuth/elevation direction in order to meet a specified receiver sensitivity requirement + +NOTE: EIS is directly related to field-strength via free-space impedance and effective aperture antenna area. EIS is expressed as the receiver power that would be collected by an isotropic antenna if it were subject to a uniform field around the whole sphere as the AAS BS array experiences in the specified azimuth/elevation direction. + +**Inter RF Bandwidth gap:** frequency gap between two consecutive *Base Station RF Bandwidths* that are placed within two supported *operating bands* + +**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* + +**operating band:** frequency range in which NR operates (paired or unpaired), that is defined with a specific set of technical requirements. + +**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 + +**radiating element:** basic building block of an *array element* characterized by its radiation properties + +**radiation pattern:** angular distribution of the radiated electromagnetic field or power level in the far field region + +**radio distribution network:** passive network which distributes radio signals generated by the active *transceiver unit array* to the *antenna array*, and/or distributes the radio signals collected by the *antenna array* to the active *transceiver unit array*. + +NOTE: The number of transmission outputs from the RDN should be greater than or equal to the number of transmission inputs for a single frequency. + +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-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 RIB*. + +**sub-band:** A *sub-band* of an operating band contains a part of the uplink and downlink frequency range of the operating band. + +**superseding-band:** A *superseding-band* of an operating band includes the whole of the uplink and downlink frequency range of the operating band. + +**total radiated power:** is the total power radiated by the antenna + +NOTE: The *total radiated power* is the power radiating in all direction for two orthogonal polarizations. *Total radiated power* is defined in both the near-field region and the far-field region + +**transmission bandwidth:** RF Bandwidth of an instantaneous transmission from a UE or BS, measured in resource block units + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------| +| $F_{\text{FBWhigh}}$ | Highest supported frequency within supported operating band , for which fractional bandwidth support was declared | +| $F_{\text{FBWlow}}$ | Lowest supported frequency within supported operating band , for which fractional bandwidth support was declared | +| $F_{\text{PBWhigh}}$ | Highest supported frequency, for which percentage bandwidth support was declared | +| $F_{\text{PBWlow}}$ | Lowest supported frequency, for which percentage bandwidth support was declared | + +## 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]. + +| | | +|--------|-----------------------------------------| +| AA | Antenna Array | +| AAS | Antenna Array System | +| ACLR | Adjacent Channel Leakage Ratio | +| ACS | Adjacent Channel Selectivity | +| ADC | Analog-to-Digital Converter | +| BB | Base Band | +| BS | Base Station | +| BW | Bandwidth | +| CFR | Crest Factor Reduction | +| CMOS | Complementary Metal-Oxide-Semiconductor | +| DAC | Digital-to-Analog Converter | +| DPD | Digital Pre-Distortion | +| EIRP | Effective Isotropic Radiated Power | +| EIS | Equivalent Isotropic Sensitivity | +| EVM | Error Vector Magnitude | +| FBW | Fractional Bandwidth | +| FR | Frequency Range | +| IC | Integrated Circuit | +| IM | Inter-Modulation | +| IMD | Inter-Modulation Distortion | +| LNA | Low Noise Amplifier | +| LTCC | Low Temperature Co-fired Ceramic | +| MCS | Modulation and Coding Scheme | +| MIMO | Multiple-Input Multiple-Output | +| NF | Noise Figure | +| N/PMOS | N/P-channel Metal-Oxide Semiconductor | +| NR | New Radio | +| OBUE | Operating Band Unwanted Emissions | +| OOB | Out-of-band | +| OTA | Over-The-Air | +| PA | Power Amplifier | +| PAE | Power Added Efficiency | +| PBW | Percentage Bandwidth | +| PSD | Power Spectral Density | +| RB | Resource Block | +| RDN | Radio Distribution Network | +| RF | Radio Frequency | +| RIB | Radiated Interface Boundary | +| RMS | Root Mean Square (value) | +| RX | Receiver | +| SCS | Sub-Carrier Spacing | +| SOI | Silicon On Insulator | +| TX | Transmitter | +| TRP | Total Radiated Power | +| TRX | Transceiver | +| UE | User Equipment | +| VGA | Variable Gain Amplifier | +| VSWR | Voltage Standing Wave Ratio | +| ZF | Zero Forcing | + +# 4 General + +## 4.1 Study item objective + +Study the following aspects for FR2 multi-band BS: + +Example bands: + +- 26+28 GHz: n258 + n261 + - 28+39 GHz: n257/n261 + n260 + - 26+40 GHz: n258 + n259/n262 + - 28+40 GHz: n257/n261 + n259/n262 +- +- Investigate the feasibility and performance of wideband RF and antenna architectures covering multiple FR2 bands + - Investigate if FR1 multi-band methods are re-usable for FR2, and (if so) agree on the appropriate inter-RF BW gaps + - Investigate if FR1 exceptions are acceptable for FR2 + - Investigate whether a generic solution for all combinations within FR2-1 is possible and/or a solution for all or a part of the frequency range should be targeted + - Frequency range 24-29 GHz which includes n257/n258/n261 + - Frequency range 37-48 GHz which includes n260/n259/n262 + - Study the definition of FR2 multi-band BS + +## 4.2 Deployment scenarios + +The scope of this study encompasses FR2 multi-band BS can support multiple FR2-1 mmWave bands transmission and/or reception through common active RF components. BS that supports multiple bands by means of separate antenna arrays and active components within the same enclosure are not in the scope of this study as they can already be supported by Rel-15 single band requirements and do not need further study. + +FR2 BS capable of multi-band operation (whether those in the scope of this study, or BS supporting multiple bands by means of separate antenna arrays and active components within the same enclosure) should support evolution from single FR2-1 band to two FR2-1 bands application. Operators can configure for single band operation at one band initially and upgrade it to two bands sharing a common radio without further hardware investment. + +Since common active RF components are used for FR2 multi-band BS, the receiver and transmitter operate simultaneously would require very large isolation, which make it less possible for unsynchronized operation between bands. Hence inter-band synchronized operation is required for multi-band operation. + +Possible FR2 multi-band BS structures and configurations based on combining different receiver/transmitter implementations (multi-band or single band), as well as mapping receive and transmit signals on a shared antenna or separate antennas should be considered in the study. + +Scenarios 1), 4), 5) and 6) below should be considered as the target scenarios to be studied in this study while no study needed on the scenario 2) and 3) below: + +- 1) Multi-band transmitter and/or receiver with common active RF components +- 2) Single-band transmitter and receiver + +- 3) Configurable BS for different bands with the same hardware, i.e. only one band can be configured to operate at any time. +- 4) BS covers full-band or sub-band of band A and band B +- 5) BS covers consecutive spectrums with different band number, for example, n258+n261 +- 6) BS covers two bands which have overlapping spectrums, for example, n258+n257, and BS support no overlapping frequency range in the two bands. + +The upcoming section illustrates high-level architecture options for multi-band support and further identifies which of those options are within the scope of this study. + +### 4.2.1 Architecture options + +Figure 4.2.1-1 depicts potential architectures based on the implementation options available for multi-band support in FR2-1 BS. The main components included are the PA, antenna array, and diplexers (wherever needed). Note that there are no active RF components before the RF input in any of the options in the figure. + +![Figure 4.2.1-1: High-level architecture options to support multi-band operation in FR2-1. The figure shows five options (Option #1 to Option #5) for RF architecture. Option #1: RFIN_MB enters a diplexer, splitting into F_low and F_high paths, each with a PA (PA_low, PA_high) and antenna (ANT_low, ANT_high). Option #2: RFIN_MB enters a multi-band PA (PA_MB), then a diplexer for F_low and F_high paths with antennas. Option #3: RFIN_MB enters a diplexer, then PAs, then another diplexer, and finally a multi-band antenna (ANT_MB). Option #4: RFIN_MB enters a multi-band PA (PA_MB) directly to a multi-band antenna (ANT_MB). Option #5: Two separate RFIN_SB inputs (F_low, F_high) enter individual PAs (PA_low, PA_high) connected to antennas (ANT_low, ANT_high). A notes box defines Low, High, and MB components.](853f59c89931a666c07903b31d098277_img.jpg) + +**Option #1** + +**Option #2** + +**Option #3** + +**Option #4** + +**Option #5** + +Notes: + +- Low = lower frequency range supported + - Low range may be single-band or multi-band +- High = higher frequency range supported + - High range may be single-band or multi-band +- MB = component supports multi-band + +Figure 4.2.1-1: High-level architecture options to support multi-band operation in FR2-1. The figure shows five options (Option #1 to Option #5) for RF architecture. Option #1: RFIN\_MB enters a diplexer, splitting into F\_low and F\_high paths, each with a PA (PA\_low, PA\_high) and antenna (ANT\_low, ANT\_high). Option #2: RFIN\_MB enters a multi-band PA (PA\_MB), then a diplexer for F\_low and F\_high paths with antennas. Option #3: RFIN\_MB enters a diplexer, then PAs, then another diplexer, and finally a multi-band antenna (ANT\_MB). Option #4: RFIN\_MB enters a multi-band PA (PA\_MB) directly to a multi-band antenna (ANT\_MB). Option #5: Two separate RFIN\_SB inputs (F\_low, F\_high) enter individual PAs (PA\_low, PA\_high) connected to antennas (ANT\_low, ANT\_high). A notes box defines Low, High, and MB components. + +**Figure 4.2.1-1: High-level architecture options to support multi-band operation in FR2-1** + +From the options captured in the figure, Option #2 and Option #4 are the target scenarios of this study item, while no study is needed for Option #5. For Option #1 and Option #3, if the PA is capable of being operated in multiple bands at the same time, then it supports multi-band operation. However, if the PA can only be configured and operated in a single-band, then it is considered a single-band RIB. + +Option #1 and Option #3 are feasible with current technology if the ranges covered by each path have a percentage bandwidth up to 19.5%. Per agreements in sub-Clause 5.2.1.4, Option #2 and Option #4 should also be feasible for a percentage bandwidth up to 19.5%. Note that even within the same frequency group, the performance attained would yield a lower Tx power compared to a single-band design. However, given that this requirement is a manufacturer declaration, it would not impact the requirement applicability. + +# 5 Feasibility study + +## 5.1 General + +According to the definition in section 6.1, a multi-band FR2-1 RIB is a RIB that transmits in two or more FR2-1 bands using common active components. In this section, the feasibility of an FR2-1 multi-band solution is considered. The feasibility is examined taking into account technology challenges and emerging solutions. It is possible that not all parts of the BS are multi-band but that some advantage can be gained by implementing some parts as multi-band. For example one potential advantage of a multiband PA might be that power can be distributed between the supported bands offering more flexibility to optimize the power available for each, this requires only a multi-band PA. + +The evaluation considers whether the proposed set of FR2-1 requirements is likely to be achievable with present or future implementation possibilities. The study does not aim to conclude on whether a multi-band FR2 solution is more optimal or effective (considering complexity, power, weight etc.) than other possibilities, for example mounting individual radio panels for each band within a BS enclosure. + +When discussing the feasibility of wideband components/systems the multi-band bandwidth as a percentage of the carrier frequency should be considered. + +Note that this is generally called fractional BW but in [2] the term fractional BW is already defined to mean something specific so is best avoided to prevent confusion. + +Fractional bandwidth (FBW) is defined for a single operating band as shown below: + +- Fractional bandwidth (FBW) is defined in [2] as $FBW = 200 \cdot \frac{F_{FBWhigh} - F_{FBWlow}}{F_{FBWhigh} + F_{FBWlow}} \%$ , +- where $F_{FBWhigh}$ is highest supported frequency within supported operating band, for which fractional bandwidth support was declared, and $F_{FBWlow}$ is lowest supported frequency within supported operating band, for which fractional bandwidth support was declared. + +Multiple operating bands are discussed in this study so the existing definition of fractional bandwidth is not suitable, the term percentage bandwidth is therefore used and defined as follows: + +- Percentage bandwidth (PBW) is defined in this study as $PBW = 200 \cdot \frac{F_{PBWhigh} - F_{PBWlow}}{F_{PBWhigh} + F_{PBWlow}} \%$ , +- where $F_{PBWhigh}$ is highest supported frequency, for which percentage bandwidth support was declared, and $F_{PBWlow}$ is lowest supported frequency, for which percentage bandwidth support was declared. + +Table 5.1-1 shows the percentage bandwidth for the FR2-1 bands and various potential multi-band groups. + +**Table 5.1-1:Percentage band width of FR2-1 operating band (s)** + +| Frequency group, NR operating band pairing (lowest, highest) | Frequency range | Percentage bandwidth | +|--------------------------------------------------------------|-----------------------|----------------------| +| 26 GHz (n258) | 24250 MHz – 27500 MHz | 12.6% | +| 28 GHz (n257) | 26500 MHz – 29500 MHz | 10.7% | +| 28 GHz (n261) | 27500 MHz – 28350 MHz | 3% | +| 39 GHz (n260) | 37000 MHz – 40000 MHz | 7.8% | +| 40 GHz (n259) | 39500 MHz – 43500 MHz | 9.6% | +| 48 GHz (n262) | 47200 MHz – 48200 MHz | 2.1% | +| 24-29 GHz (n257/n258/n261) | 24250 MHz – 29500 MHz | 19.5% | +| 37-48 GHz (n260/n259/n262) | 37000 MHz – 48200 MHz | 26.3% | +| 26+28 GHz (n258, n261) | 24250 MHz – 28350 MHz | 15.6% | +| 28+39 GHz (n257/n261, n260) | 26500 MHz – 40000 MHz | 40.6% | +| 26+40 GHz (n258, n259/n262) | 24250 MHz – 48200 MHz | 66.1% | +| 28+40 GHz (n257/n261, n259/n262) | 26500 MHz – 48200 MHz | 58.1% | + +## 5.2 Wideband RF architectures + +### 5.2.1 RF Front end + +#### 5.2.1.1 General + +Feasibility for RF front ends can be considered by looking at existing component capabilities which could be used for multi-band FR2 products now but also by studying literature for the direction of future capabilities. + +#### 5.2.1.2 Beam former and PA + +There are a number of components available today which offer sufficient band widths to cover at least some of the FR2 multi-band options. In [24] a wide band beamformer and PA was presented which covered 24 to 29.5 GHz (bands n257/n258/n261). The performance of which can be seen in table 5.2.1.2-1 and figure 5.2.1.2-1. + +**Table 5.2.1.2-1: beamformer IC in 24-29.5GHz** + +| Parameter | Beamformer | +|--------------------------|-------------| +| Frequency Range | 24-29.5 GHz | +| Tx OP1dB/OIP3 | 21 / 25 dBm | +| Tx Pdiss/Ch @ 12dBm Pout | 300 mW | +| Pout @3% EVM w/ 64QAM | 12 dBm | +| Rx Single Channel NF | 4 dB | +| Rx Pdiss | 130 mW | +| Instantaneous Bandwidth | 1600 MHz | + +![Figure 5.2.1.2-1: PA bias optimized for P1dB for 24GHz (left), and 28GHz (right). The figure contains two line graphs. The left graph shows Output P1dB (dBm) vs Frequency (GHz) for 24 GHz, with curves for bias voltages -10, 25, 85, 95, and 105. The right graph shows Gain (dB) vs Frequency (GHz) for 28 GHz, with the same bias voltage curves. Both graphs show that as the bias voltage increases, the output power and gain generally decrease across the frequency range.](eb5834a9eafc9eba7a2b597b13afbbed_img.jpg) + +Figure 5.2.1.2-1: PA bias optimized for P1dB for 24GHz (left), and 28GHz (right). The figure contains two line graphs. The left graph shows Output P1dB (dBm) vs Frequency (GHz) for 24 GHz, with curves for bias voltages -10, 25, 85, 95, and 105. The right graph shows Gain (dB) vs Frequency (GHz) for 28 GHz, with the same bias voltage curves. Both graphs show that as the bias voltage increases, the output power and gain generally decrease across the frequency range. + +**Figure 5.2.1.2-1: PA bias optimized for P1dB for 24GHz (left), and 28GHz (right)** + +It is considered feasible that multi-band beamformer IC covering 24-29.5GHz and associated bands can be achieved. + +Looking further ahead the results of academic studies in [25] a 24-42 GHZ wideband PA was presented which exhibited flat P1dB of 17.8 to 19.6dBm, within 1.6dB from $P_{\text{sat}}$ , and flat PAEP1dB of 36.6 to 44.3% over 24 to 40GHz, verifying the truly wideband large-signal matching. + +In [26] the hybrid N/PMOS allowed the 26-39GHz PA deep Class-AB biasing and device cascade, substantially increasing PA Pout and efficiency. + +These PAs across different frequency groups are summarized in the following Table 5.2.1.2-2. It can be seen that some recent study shows PA covering 26-39GHz, 24-42GHz with average output power around 10dBm, PAEP1dB larger than 30%. + +**Table 5.2.1.2-2: PAs performance from literatures** + +| Frequency | [25] 24 -42GHz PA | [26] 26 -39GHz PA | +|----------------------------------------------|-------------------|-------------------| +| Authors and year of publication | Fei Wang,2020 | J Park,2022 | +| Technology | 45nm SOI CMOS | 45nm SOI CMOS | +| Gain (dB) | 20.5 | 18.9 | +| S 21 BW -3dB (GHz ) | 25.8-43.4 | 25.3-42.0 | +| P 1dB BW -1dB (GHz ) | 22.0-37.0 | 25.0-37.0 | +| PAE P1dB BW -1dB (GHz) | 24.0-41.2 | 29.9-33.6 | +| P1dB (dBm) | 17.8-19.6 | 16.3-18.4 | +| Pavg (dBm) | 8.4-11.3 | 10.8-12.3 | +| PAE P1dB (%) | 36.6-44.3 | 29.9-34.9 | + +These papers indicate that PAs covering frequency ranges from 26 to 40GHz or more are at least technically feasible in the research environment and may become available in the longer term. + +It should be noted PAs with wide percentage bandwidths may not be capable of operating with signals that broad. For instance, while the PA may cover 50% bandwidth, its instantaneous bandwidth, i.e. maximum signal bandwidth, is usually restricted to a few hundred MHz due to limitations with bias networks and memory effects. + +#### 5.2.1.3 Receiver front end + +In [27] a 27-41GHz RX was designed and a proof-of-concept mm-Wave four-input-four-output MIMO RX array was implemented in a 45-nm CMOS SOI process with a total chip size of 3.6 mm×6.5 mm. + +In [28] a 24.25-to-71GHz phased-array receiver is was introduced, which covering the whole FR2 frequency band 3GPP have defined by now. A harmonic-selection technique is was proposed to extend the operating bandwidth with low power consumption. The LNA can be configured into either operating Mode 1 covering 24 to 44GHz or operating Mode 2 covering 44 to 71GHz. + +Paper [29] presented a 22–44 GHz 2×2 phased-array receive beamformer. The RX channel includes a LNA, a 5-bit vector modulator (VM) phase shifter, an attenuator, and a variable gain amplifier (VGA). The phased-array channel results in a peak gain of 26.3 dB and a 3-dB bandwidth of 20.5–44 GHz. The measured NF is 3–3.6 dB at 22–44 GHz with an IP1dB of –27.5 to –24.5 dBm. + +For phase-array receive beamformer, these good performance receivers across different frequency groups are summarized in the following Table 5.2.1.3-3. They achieved low NF in a wide bandwidth. + +**Table 5.2.1.3-3: Phased-array receiver chips performance** + +| Frequency | [29]22–44 GHz | [27]27–41GHz | [28]24–71GHz | +|---------------------------------------|---------------|-------------------|--------------------------------------------------| +| Authors and year of publication | Li Gao,2020 | Min-Yu Huang,2019 | Jian Pang,2022 | +| Tech. | 45nm CMOS SOI | 45nm CMOS SOI | 65nm CMOS Bulk | +| BW(GHz) | 22-44 | 27-41 | 24.25-71 | +| Gain(dB) | 26.2 | 36/element | / | +| NF(dB) | 3-3.6 | 4.3-6.3 | 3.6-8.0 (at 24.25-35GHz)
4.0-7.6(at 35-44GHz) | +| Gain Tuning(dB) | 16 | 15 | / | +| Phase Shift Res( $^{\circ}$ ) | 11.25 | / | / | +| Phase/Gain RMS Error( $^{\circ}$ /dB) | 6/1.9 | / | / | +| IP1dB(dBm) | -25.4 | -34/-27.3 | -17.6 (at 28GHz)
-20.9(at 39GHz) | +| IIP3(dBm) | -18 | / | / | +| P dc (mW) | 112 | / | / | + +#### 5.2.1.4 Summary + +It has been shown that: + +- Multi-band beamformer IC with common active RF components with 19.5% percentage bandwidth in frequency range 24-29 GHz which includes n257/n258/n261 is technically feasible. +- For RF front-end, TRX chips covering 24-29.5GHz. 27-41GHz RX are shown. A harmonic-selection technique is proposed to extend the receiver's operating bandwidth up to 24.25-71GHz. + +Key components of a multi-band FR2 RF front end are hence available today for certain frequency ranges and band numbers (n257/n258/n261) and it can be envisioned that wider frequency range products could be feasible in the future. + +### 5.2.2 Digital Pre-distortion + +#### 5.2.2.1 DPD for FR2 single-band BS + +For single-band FR2 radios, the application of DPD may not be critical compared to that of the FR1 counterpart. On one hand, the contribution of PAs to the total DC power consumption in a FR2 BS is much reduced. This is due to the fact that more antenna elements are added to increase the directivity of the antenna array to combat against the high path loss occurred at FR2, which in turn requires smaller power to feed each antenna element, and thus small-power PA per Tx is sufficient. On the other hand, the requirement on ACLR for FR2 BSs is not as large, i.e. 24 - 28dBc (by means of OTA measurement), compared to that applied to FR1 BSs, i.e. 45dBc [2] due to the beamforming and propagation environment. This somewhat alleviates the essential need of high-linearity PAs on meeting required ACLR. Therefore, the DPD in single-band FR2 BSs is expected to provide a little gain in terms of improving power efficiency and meeting the ACLR requirement. Furthermore, the analog and hybrid beamforming, which are predominantly used in FR2 radios, also pose challenges for DPD implementation. With hundreds to thousands of PAs and higher operating bandwidths for FR2 radio, simply utilizing a similar DPD architecture as in FR1 would cost extra for RF hardware design and power consumption, while it may be infeasible to deploy single DPD for every PA in the analog/hybrid beamforming phased array since several or all analog chains essentially share one digital path. The DPD algorithms would also have more demands on the bandwidth of feedback receiver/ADC and BB signal processing resources, which + +are scaled with the size of bandwidth to be linearized. These limited-gain and implementation-challenge factors make the similar DPD implementations as in FR1 less attractive to the FR2 single-band BS. + +Nevertheless, DPD may still bring benefit for FR2 BSs in terms boosting the overall system performance (e.g. throughput due to improved EVM, or very possibly energy efficiency). It is worth highlighting that common FR2 transmitter architecture requires to have tight integration between RF components to reduce hardware costs, sizes, and power loss in which isolator between an antenna element and a PA is preferably avoided [5], e.g. as illustrated in Figure 5.2.2.1-1. In such architecture, PAs directly interact with the antenna array due to low path isolation between them. As a result, mutual coupling and antenna mismatch between antenna paths have strong impact to the PAs' output matching impedance which changes the PA's efficiency and nonlinearity behaviours [5]. The array steering angle, which also alters the antenna matching impedance, shows strong dependence on the nonlinearity to the PAs too. In addition, input of PAs in different branches may be driven with different power as a result of the beamforming techniques applied (i.e. tapering, ZF, etc.), or gain error of the phase shifters and gain imbalance of power division network [6]. These mentioned factors have the detrimental effect to efficiency and linearity behaviours of PAs which may degrade the ACLR while increasing the OOB emission and beam distortions [5]. For example, several studies have demonstrated the impact of steering angle to ACLR and OOB emission and how DPD can help to improve the beamforming performance [5, 6, 7, 8, 9]. + +![Figure 5.2.2.1-1: A typical single-band FR2 antenna array architecture. The diagram shows a vertical stack of antenna elements. Each element is connected to a common input bus via a switch. Each element consists of a phase shifter (represented by a circle with a diagonal arrow), a power amplifier (represented by a triangle), and an antenna (represented by a triangle with a vertical line). The switches are shown in the 'on' position for each element, connecting them to the bus. Vertical ellipses indicate additional elements in the array.](9cd90f495b95ad2116ff780248c26d95_img.jpg) + +Figure 5.2.2.1-1: A typical single-band FR2 antenna array architecture. The diagram shows a vertical stack of antenna elements. Each element is connected to a common input bus via a switch. Each element consists of a phase shifter (represented by a circle with a diagonal arrow), a power amplifier (represented by a triangle), and an antenna (represented by a triangle with a vertical line). The switches are shown in the 'on' position for each element, connecting them to the bus. Vertical ellipses indicate additional elements in the array. + +**Figure 5.2.2.1-1: A typical single-band FR2 antenna array architecture** + +Obviously, any individual variation in PA would affect the performance of the linearization so the peak linearization performance is likely to be lower than that of a one-DPD-per-PA system. Whilst the design of PA's is likely to be identical there are a number of factors which could change their performance: + +- Temperature – the location of each PA in the array (and the silicon) may mean different transistors are at different temperature (depending on the number of neighbouring devices for example) so the temperature of each junction may be different. +- Unit to unit variation – whilst some transistors may all be on a single piece of silicon and variation on a single bit of silicon may be small if multiple devices are used (8 or 16 per device may be more usual) so there will be unit to unit variation across the potential 128 paths +- Output match variation – PA performance is very dependent on the load it is working into, again all output match circuits are likely to be designed identically but will vary based on a number of factors: + - Unit to unit of components + - Antenna unit to unit + +- Antenna isolation and load pulling from nearby antenna (and signals) + +Despite these issues useful linearization of an FR2 systems can be achieved and may become more common as technology improves. + +#### 5.2.2.2 DPD for FR2 multiband BS + +Antenna array and TRXs in FR2 radios are desired to be tightly integrated in which RF filter is preferably omitted after the PA. Since a *multi-band RIB* essentially needs to transmit multiple-band signals concurrently, the nonlinearity of PAs will likely cause intermodulation (IM) distortion. It would be highly challenging to manage the PAs in multiband RIB not to operate in the nonlinearity power region. Particularly, the varying nonlinearity behaviours of the PAs, which causes by the nonlinear interaction between antenna array and the PAs as discussed above, also inherit to the FR2 *multi-band RIB*. Such issues would be expected to be more complicated in the multiband use cases than in single-band ones due to higher requirements on matching load impedance of PAs covering multiband/wideband. Therefore, unwanted emissions due to IM distortions likely exist and may possibly fall into the operating bands or inter- RF bandwidth. Note that the latter case occurs if there is multicarrier transmission in one band. Figures 5.2.2.2-1 and 5.2.2.2-2 illustrate some examples. Assume that frequency ranges that the BS can operate in Band A and B are 24.25-26.5GHz (n258) and 27-29.5 GHz (n257), and there is transmission taking place at 26GHz in Band A and 27.5GHz in band B. Then IM3 components occur at 24.5GHz and 29GHz, which obviously fall into operating bandwidth of both bands as seen in Figure 5.2.2.2-1. Now assume that band A transmits two carrier frequencies at 24.75 and 25.75GHz. Then one IM3 component occurs at 26.75GHz which falls into the inter- RF bandwidth of the multiband BS as seen in Figure 5.2.2.2-3. + +![Figure 5.2.2.2-1: Frequency spectrum diagram showing Band A (24.25-26.5 GHz) and Band B (27-29.5 GHz) with an inter- RF bandwidth gap between them. Carrier f1 is at 26 GHz in Band A, and carrier f2 is at 27.5 GHz in Band B. IM3 components are shown at 24.5 GHz and 29 GHz, both falling within the operating bands.](8a597e344d10e36bbb2f243f6c4e74c6_img.jpg) + +The diagram shows two frequency bands, Band A and Band B, separated by an 'Inter- RF bandwidth gap'. Band A spans from 24.25 GHz to 26.5 GHz, and Band B spans from 27 GHz to 29.5 GHz. A carrier signal $f_1$ is transmitted at 26 GHz within Band A, and a carrier signal $f_2$ is transmitted at 27.5 GHz within Band B. Third-order intermodulation (IM3) products are indicated by red arrows at 24.5 GHz and 29 GHz, both of which fall within the operating frequency ranges of Bands A and B respectively. + +Figure 5.2.2.2-1: Frequency spectrum diagram showing Band A (24.25-26.5 GHz) and Band B (27-29.5 GHz) with an inter- RF bandwidth gap between them. Carrier f1 is at 26 GHz in Band A, and carrier f2 is at 27.5 GHz in Band B. IM3 components are shown at 24.5 GHz and 29 GHz, both falling within the operating bands. + +Figure 5.2.2.2-1: Example for possible unwanted emission due to concurrent multiband transmission + +![Figure 5.2.2.2-2: Frequency spectrum diagram showing Band A (24.25-26.5 GHz) and Band B (27-29.5 GHz) with an inter- RF bandwidth gap between them. Two carriers, f1 and f2, are transmitted within Band A at 24.75 GHz and 25.75 GHz respectively. IM3 components are shown at 24.5 GHz and 26.75 GHz, with the latter falling into the inter- RF bandwidth gap.](6b09b11992389190c93c33a3e80d6fa9_img.jpg) + +This diagram illustrates a scenario where two carrier signals, $f_1$ and $f_2$ , are transmitted within Band A at 24.75 GHz and 25.75 GHz. Band A covers 24.25 GHz to 26.5 GHz, and Band B covers 27 GHz to 29.5 GHz, with an inter- RF bandwidth gap between 26.5 GHz and 27 GHz. IM3 components are shown at 24.5 GHz and 26.75 GHz. The 26.75 GHz component falls into the inter- RF bandwidth gap between the two bands. + +Figure 5.2.2.2-2: Frequency spectrum diagram showing Band A (24.25-26.5 GHz) and Band B (27-29.5 GHz) with an inter- RF bandwidth gap between them. Two carriers, f1 and f2, are transmitted within Band A at 24.75 GHz and 25.75 GHz respectively. IM3 components are shown at 24.5 GHz and 26.75 GHz, with the latter falling into the inter- RF bandwidth gap. + +Figure 5.2.2.2-2: Example for possible unwanted emission due to multi-carrier transmission in one band + +Note that Figure 5.2.2.2-1 and Figure 5.2.2.2-2 demonstrate the location of IMD products with CW signals, in reality the transmitted signals are wide band and the IMD products even more so, as such they may not be separable from the noise floor. As such IMD products are a potential issue but possibly not a serious one in some case, for example: + +- 128 PA's at 20mW each is only 2.56W (34dBm) +- With 28dBc ACLR this gives an adjacent channel power of 6dBm + +For a 100MHz channel this gives a PSD of -14dBm/MHz which is below the spurious emissions requirements for FR2. It is unlikely that any in-band non-linearities will be greater than the ACLR level (as these are 3rd order products) so the out of band emissions requirements are unlikely to be a problem. + +The IM distortion is also beamformed [10], however if the beams in the different bands are steered in different directions the IM product is in a different direction again [3]. If the beams are close to each other however, e.g. when UEs are nearby each other, the IM distortion beam may still be close enough to point at the intended UE. Thus, it needs to be managed to ensure that RF requirements are still be met for the FR2 multiband RIB. + +Apart from other UEs within the network, IM products in the *inter RF bandwidth gap* need to be suppressed sufficiently to ensure that spurious emissions requirements towards other systems are met. This would in particular need attention if band combinations between frequency groups would be considered. + +RF filter/diplexer after every PAs could be used to handle IM distortions. However, such solution would be very expensive since beamforming phased array in FR2 could have thousands of antenna paths. Filter per path may also generate significantly phase error between antenna paths and increase power loss. Thus, this may not be feasible in terms of cost, size, and performance of FR2 radios. Alternatively, DPD may be a cheaper solution for RF hardware architectures to this issue. For FR2 multi-band DPD, it essentially inherits the abovementioned advantages as well as challenges for single-band FR2 BS with a few additional issues. For instance, the very large percentage BW may cause potential issues when applying DPD for multi-band FR2, these are: + +- The large percentage BW of the PA and the wider the BW the more difficult it will be to maintain a consistent impedance match of PAs over the entire band and hence memory effects may be greater making the DPD algorithm tougher to achieve good linearization. +- Larger BW means variation of the potential sources (as listed for single band) are greater, once gain reducing the potential linearity saving. + +Potentially split or stacked element arrays mean each band signal may be fed to a different antenna, meaning the output load for the PA is more complex and more open to variation. + +Investigating practically feasible DPD solutions for beamforming phased array in FR2 has been an active research topic [11]. To address the concerns on the DPD implementation in FR2, DPD architectures and efficient DPD training model/algorithms have been intensively studied. Note that since one digital path will be shared between some or all analog chains in the analog/hybrid beamforming phased array, an architecture in which DPD linearization is applied for a set of PAs has been proposed and then demonstrated to be able to improve ACLR and EVM, e.g. [12, 13]. + +For multi-band DPD, as the beam steering for a multi-band FR2 system is likely to be applied to each band separately before the signals are combined and fed to a single PA, one example architecture could be that the signals will be generated separately in different converters. Such architectures have been investigated in FR1 bands [14] where separate signals were used to linearize a dual-band signals in a dual-band PA. + +In general, one can either deploy a common DPD for all bands or a dedicated DPD for each band [15]. The former may have less demand on DPD architecture but requires much higher bandwidth for DPD hardware as the captured, training and correcting samples are wideband; since the correction is wide-band, band-specific linearization may not be achievable as such. The latter has lower demand on DPD hardware bandwidth and can achieve per-band linearization but may require more complex DPD architectures and algorithms, i.e. to decompose the captured multiband signals to single-band one and vice versa for the corrections, as well as jointly optimize linearized coefficients for all bands. In both architectures, a wider bandwidth feedback path is required to deal with large signal bandwidth of FR2 band; traditionally the feedback channel needs 3 to 5 times the signal bandwidth to collect nonlinear information of PA. This can be a big burden for high-speed and high-precision ADCs. Nevertheless, DPD training algorithms which minimize the demand on DPD hardware bandwidth and BB resources have also been proposed, e.g. in [16, 17]. It should be highlighted that the implementation of phase shifters will not significantly impact the DPD solutions as linearization are applied to signals seen at the output of the PA, as mentioned in [18]. + +### 5.2.3 Phase shifter + +Analog phase shifters in mmWave BS are used to control the phase of signals in order to steer the beam. In some architectures, attenuators or variable-gain amplifiers are also placed along with the phase shifter to control the gain of beamformed signals to achieve desirable beamforming performance. + +Considering phase shifter designs which are wideband it would prove difficult to apply different phase shifts to different bands. Hence it is not possible to independently steer beams to different directions in the different bands, and it may even not be feasible to steer the beams in the same directions for 2 separate bands if the bands are sufficiently far apart in frequency that the beamforming weights would need to be different for each band. + +If variable true time delay based phase shifters, which add delay to time-domain signals to create phase shift such as tapped delay line phase shifter, are used, then it may be possible to steer the beams toward the same direction for two different bands. This is because the frequency-dependent linear phase response of the true time delay phase shifter can create different phase shifts at different frequencies. However, true time delay phase shifts are challenging to implement + +due to the required size to delivered acceptable phase shift performance (e.g, phase shift resolution), while incurring high insertion loss. + +Phase shifters with a frequency-flat phase response, such as vector modulated phase shifters may have cheaper implementational cost and be more feasible to integrated into commercial BFICs. However, since only one phase shift value can be controlled at a time instant, it may not be feasible to steer the beams in the same direction for two different bands if the bands are sufficiently far apart in frequency that the beamforming weights need to be different for each band. + +Examples of beam steering results when wide-band frequency-flat phase response phase shifters and wideband phased array are used in a multiband transmitter are shown below. The phase shifters only control the beam weights of the lower frequency band. Two steering angles are considered, i.e. 0 and 20 degrees. Figure 5.2.3-1 illustrates the beam patterns when the element separation for lower band and upper band is $0.5\lambda$ and $0.6\lambda$ , respectively, which corresponds to the case of, for example, the combination n258+n261. Figure 5.2.3-2 presents the case when the operating bands are further apart, i.e. the element separation for lower band and upper band is $0.35\lambda$ and $0.65\lambda$ , respectively, which can be the case of combinations across different frequency groups. As can be seen, except when UEs of different bands are at the boresight of the array, otherwise the transmitter cannot steer the beam to multiple UEs independently. Even if different-band UEs are located at same direction (but not boresight), the beam for upper-band UEs is not pointed to its desired direction and a larger frequency separation of the bands results in bigger error of the steering angle. + +![Figure 5.2.3-1: Beam pattern of different band signals when using wideband phase shifter and antenna array. The figure contains two plots: 'Azimuth cut of beams, steering angle 0deg' (left) and 'Azimuth cut of beams, steering angle 20deg' (right). Both plots show 'Normalized directivity [dB]' on the y-axis (from -80 to 10) versus 'Angle [deg]' on the x-axis (from -90 to 90). Two curves are shown: 'lower band' (blue) and 'upper band' (orange). In the 0-degree steering plot, both bands have a main lobe at 0 degrees. In the 20-degree steering plot, the lower band's main lobe is at 20 degrees, while the upper band's main lobe is shifted to approximately 15 degrees.](bd4617f25d15430eb78c2d6d75a99dde_img.jpg) + +Figure 5.2.3-1: Beam pattern of different band signals when using wideband phase shifter and antenna array. The figure contains two plots: 'Azimuth cut of beams, steering angle 0deg' (left) and 'Azimuth cut of beams, steering angle 20deg' (right). Both plots show 'Normalized directivity [dB]' on the y-axis (from -80 to 10) versus 'Angle [deg]' on the x-axis (from -90 to 90). Two curves are shown: 'lower band' (blue) and 'upper band' (orange). In the 0-degree steering plot, both bands have a main lobe at 0 degrees. In the 20-degree steering plot, the lower band's main lobe is at 20 degrees, while the upper band's main lobe is shifted to approximately 15 degrees. + +**Figure 5.2.3-1. Beam pattern of different band signals when using wideband phase shifter and antenna array. Phase shifters apply beam weights for the lower band. Array separation for lower band $0.5\lambda$ , and upper band $0.6\lambda$ : (Left) 0-degree steering angle; (Right) 20-degree steering angle** + +![Figure 5.2.3-2: Beam pattern of different band signals when using wideband phase shifter and antenna array. The figure contains two plots: 'Azimuth cut of beams, steering angle 0deg' (left) and 'Azimuth cut of beams, steering angle 20deg' (right). Both plots show 'Normalized directivity [dB]' on the y-axis (from -80 to 10) versus 'Angle [deg]' on the x-axis (from -90 to 90). Two curves are shown: 'lower band' (blue) and 'upper band' (orange). In the 0-degree steering plot, both bands have a main lobe at 0 degrees. In the 20-degree steering plot, the lower band's main lobe is at 20 degrees, while the upper band's main lobe is shifted to approximately 10 degrees, showing a larger steering error compared to Figure 5.2.3-1.](47e75dc9e83054b2dac3df8bf3e57019_img.jpg) + +Figure 5.2.3-2: Beam pattern of different band signals when using wideband phase shifter and antenna array. The figure contains two plots: 'Azimuth cut of beams, steering angle 0deg' (left) and 'Azimuth cut of beams, steering angle 20deg' (right). Both plots show 'Normalized directivity [dB]' on the y-axis (from -80 to 10) versus 'Angle [deg]' on the x-axis (from -90 to 90). Two curves are shown: 'lower band' (blue) and 'upper band' (orange). In the 0-degree steering plot, both bands have a main lobe at 0 degrees. In the 20-degree steering plot, the lower band's main lobe is at 20 degrees, while the upper band's main lobe is shifted to approximately 10 degrees, showing a larger steering error compared to Figure 5.2.3-1. + +**Figure 5.2.3-2. Beam pattern of different band signals when using wideband phase shifter and antenna array. Phase shifters apply beam weights for the lower band. Array separation for lower band $0.35\lambda$ , and upper band $0.65\lambda$ : (Left) 0-degree steering angle; (Right) 20-degree steering angle.** + +Thus, it is not clear such a wide band phase shifter as shown in Figure 5.2.3-3 would be of use. Within the time frame of this SI it seems commercially available multi-band frequency selective phase shifters that can apply a different phase shift per band are unlikely to be available. However, any specification should not preclude a potential future architecture based on frequency dependent phase shifters. If and when frequency dependent phase shifters become viable, it is possible that RAN4 requirements created in Rel-18 would need re-visiting. + +![Figure 5.2.3-3: Example of multi-band phase shifter prior to a multi-band PA](09955ff8214ffb6947951fc0f60eb6ab_img.jpg) + +The diagram shows a signal flow from left to right. It starts with a 'Band A+B signal' input. This signal passes through a 'multi-band phase shifter' (represented by a dashed box containing a circle with a diagonal arrow). The output of the phase shifter goes into a 'common PA' (represented by a triangle). The output of the PA then passes through a 'Filter' (represented by a dashed box containing two wavy lines). Finally, the signal is sent to an 'Antenna array' (represented by a solid rectangle). + +Figure 5.2.3-3: Example of multi-band phase shifter prior to a multi-band PA + +**Figure 5.2.3-3. Example of multi-band phase shifter prior to a multi-band PA** + +In order to apply independent phase shift and hence independent steering to each band, phase shifters need to be applied differently to each band. Using technology available today it may be possible to use multiple single band phase shifters to provide the beam steering to each band independently whilst feeding into a multi-band PA shown in Figure 5.2.3-4, although this may have some performance penalty. + +Note that Figures 5.2.3-3 and 5.2.3-4 show example architectures for a multi-band BS. Depending on the implementation, filter may or may not be placed after the multi-band PAs. + +![Figure 5.2.3-4: Example of single band phase shifter prior to a multi-band PA to steer each band separately](b2ea162a0f53d5e0504b7d28346e0754_img.jpg) + +The diagram shows two input signals, 'Band A signal' and 'Band B signal', entering a 'single band phase shifter' (represented by a dashed box containing two circles with diagonal arrows). The outputs of these phase shifters are combined and then fed into a 'common PA' (represented by a triangle). The output of the PA passes through a 'Filter' (represented by a dashed box containing two wavy lines). Finally, the signal is sent to an 'Antenna array' (represented by a solid rectangle). + +Figure 5.2.3-4: Example of single band phase shifter prior to a multi-band PA to steer each band separately + +**Figure 5.2.3-4. Example of single band phase shifter prior to a multi-band PA to steer each band separately** + +## 5.3 Wideband antenna architectures + +### 5.3.1 General + +Antenna arrays are resonant structures. The optimum radiating element size (a dipole is nominally $\lambda/2$ ) and the array element separation are both dependent on frequency. If an antenna is required to operate over a broad range of frequencies it is difficult to maintain optimum element size and element spacing over the whole range. The required + +percentage bandwidth of the multi-band signal in Table 5.1-1 is therefore important when looking at the feasibility of a broadband antenna. + +From antenna design perspective, solutions covering multiple bands can be achieved in three main ways: a single broadband design covering the entire range of the bands (trades certain performance parameters), designing an antenna with multiple resonances in the desired bands, or having separate antenna designs each covering a band (lower percentage bandwidth) + +### 5.3.2 Single array bandwidth + +It can be noted for comparison that there are FR1 multi-band fixed antenna arrays covering 1710MHz to 2690MHz, with a percentage bandwidth of 44.5% (VSWR of $< 1.5:1$ ). Fixed antenna arrays (with no or limited beam steering) however have more flexibility on element separation with values of up to $0.9\lambda$ being acceptable as the grating lobe is also fixed and can be attenuated with the element pattern. Whilst FR1 antennas build practices are different, the limitations on element size and spacing between elements are similar to those for FR2. + +The radiating element can trade bandwidth against radiation performance. Short dipoles still radiate but the performance degrades the farther from the ideal frequency they are operated at. Defining an exact “acceptable” level of radiation efficiency for a broadband product is not straightforward as other aspects have to be considered (some radiation efficiency may be traded to achieve a broadband system). Also, as the element becomes smaller, its radiation pattern becomes broader these negating its ability to act as a spatial filter for array grating lobes. + +The size of the radiating element and the element separation are also dependent, e.g. the elements cannot touch each other. The separation of the elements in terms of wavelength occurs at the highest frequency, as the maximum separation is limited by the grating lobe performance there is an upper limit to how large this separation may be. Therefore, this sets the maximum size of the element (which will be electrically shortest at the lowest frequency). + +![Diagram showing element length L and separation S between two adjacent elements. The diagram consists of two vertical lines representing elements. A double-headed vertical arrow between the top of the first element and the top of the second element is labeled 'L', representing the element length. Another double-headed vertical arrow between the bottom of the first element and the bottom of the second element is labeled 'S', representing the element separation. To the right of the diagram, text provides an example: 'E.g. Lmin=0.5λ, Smax=0.7λ At 40GHz Smax=0.7λ, so S=5.25mm Hence Max L = 5.25mm Min frequency for Lmax=0.5 λ element is 28.6GHz'.](19a59d6b53059ebd27b13c98793f88e0_img.jpg) + +E.g. + $L_{min}=0.5\lambda$ , $S_{max}=0.7\lambda$ + At 40GHz + $S_{max}=0.7\lambda$ , so $S=5.25\text{mm}$ + Hence Max $L = 5.25\text{mm}$ + Min frequency for $L_{max}=0.5 \lambda$ element is 28.6GHz + +Diagram showing element length L and separation S between two adjacent elements. The diagram consists of two vertical lines representing elements. A double-headed vertical arrow between the top of the first element and the top of the second element is labeled 'L', representing the element length. Another double-headed vertical arrow between the bottom of the first element and the bottom of the second element is labeled 'S', representing the element separation. To the right of the diagram, text provides an example: 'E.g. Lmin=0.5λ, Smax=0.7λ At 40GHz Smax=0.7λ, so S=5.25mm Hence Max L = 5.25mm Min frequency for Lmax=0.5 λ element is 28.6GHz'. + +**Figure 5.3.2-1: Example of physical limitations of element size and separation** + +The maximum separation is also a parameter which is difficult to agree as it depends on a number of things, a fixed antenna array may have a separation of up to $0.9\lambda$ (at its maximum operational frequency). In previous studies [xx] it has been assumed for BS antenna simulations that a fully steerable antenna array has a separation of $0.5-0.7\lambda$ to avoid grating lobes. + +For example, taking $0.5\lambda$ as a lower limit (this could be smaller if short dipoles were used), it then needs to be decided what an acceptable level of side lobe / grating lobe suppression is and also what range of steering is required. + +Three examples with similar grating lobe levels and different element spacing and steering can be seen: + +- $0.7\lambda$ element separation with $30^\circ$ steering +- $0.8\lambda$ element separation with $20^\circ$ steering +- $0.9\lambda$ element separation with $10^\circ$ steering + +![Figure 5.3.2-1: Three elevation plots showing directivity (dB) vs theta (deg) for different element separations and steering angles. Each plot compares Composite (red), element pattern (blue), and Array factor (purple) curves. The plots are for 0.7λ element separation with 30° steering, 0.8λ element separation with 20° steering, and 0.9λ element separation with 10° steering.](45329c7d9aa2bd1290af5b2027f08d7e_img.jpg) + +Figure 5.3.2-1: Three elevation plots showing directivity (dB) vs theta (deg) for different element separations and steering angles. Each plot compares Composite (red), element pattern (blue), and Array factor (purple) curves. The plots are for 0.7λ element separation with 30° steering, 0.8λ element separation with 20° steering, and 0.9λ element separation with 10° steering. + +**Figure 5.3.2-1 Array pattern: $0.7\lambda$ element separation with $30^\circ$ steering, $0.8\lambda$ element separation with $20^\circ$ steering, $0.9\lambda$ element separation with $10^\circ$ steering** + +Each of these maximum separations equates to a percentage BW of 33%, 46% and 57%, respectively, and it is clear that grating lobe level and steering range can be traded against percentage bandwidth. Once again, selecting an exact set of conditions to estimate a maximum percentage bandwidth is difficult as it depends on the product definition. + +Using another approach and taking antenna element separation $0.5\lambda$ at a higher limit, the scanning angle reaches $\pm 60^\circ$ at 26 GHz and $\pm 45^\circ$ at 38 GHz with acceptable side lobe/grating lobe levels, as shown in Figure 5.3.2-2. The corresponding spacing will be $0.34\lambda$ at a lower limit. The isolation among the antenna elements at a lower limit can be ensured with the use of decoupling structures. + +![Figure 5.3.2-2: Two beam scanning performance plots in the azimuth plane. (a) shows Directivity (dBi) vs Theta (degree) for 26 GHz with scanning angles from -60° to 60°. (b) shows Directivity (dBi) vs Theta (degree) for 38 GHz with scanning angles from -45° to 45°. Both plots show multiple curves representing different beam positions.](f1c3ae01c82d4410b559fad6174a2f1a_img.jpg) + +Figure 5.3.2-2: Two beam scanning performance plots in the azimuth plane. (a) shows Directivity (dBi) vs Theta (degree) for 26 GHz with scanning angles from -60° to 60°. (b) shows Directivity (dBi) vs Theta (degree) for 38 GHz with scanning angles from -45° to 45°. Both plots show multiple curves representing different beam positions. + +**Figure 5.3.2-2. Beam scanning performance in azimuth plane when antenna element separation is $0.5\lambda$ at higher limit (a) 26 GHz, and (b) 38 GHz.** + +In addition to the physical limitations and grating lobe performance discussed, it should also be noted that the array is electrically shorter at lower frequencies than higher frequencies and this also affects the antenna directivity and gain. For example, there is approximately 3dB gain difference between low band (26GHz) and high band (38GHz) that can be seen in Figure 5.3.2-2. This factor may also be a consideration when planning an antenna design. + +Taking another example, Figure 5.3.2-3 shows the directivity of an 8x8 uniform rectangular phased array with respect to different element separations. The antenna elements described in [31] are used in the simulation. It is seen that lower element separation will result in low array directivity. This means if the separations seen by lower frequency band is low, it likely consumes more energy to deliver acceptable array performance and cause power imbalance with higher bands, while the EIS receiver sensitive is low. The directivity difference between operating frequency bands may also be a consideration when planning an antenna design. + +![Figure 5.3.2-3: Directivity of 8x8 URA w.r.t. array element separation. The graph shows Directivity [dB] on the y-axis (ranging from 16 to 30) versus element separation [λ] on the x-axis (ranging from 0.2 to 0.9). The curve shows a positive correlation, starting at approximately 16.5 dB at 0.2 λ and increasing to about 28 dB at 0.9 λ.](d8d893dd559845f86c5dd46147ef98b6_img.jpg) + +| element separation [ $\lambda$ ] | Directivity [dB] | +|----------------------------------|------------------| +| 0.2 | 16.5 | +| 0.3 | 19.5 | +| 0.4 | 21.5 | +| 0.5 | 23.5 | +| 0.6 | 25.0 | +| 0.7 | 26.5 | +| 0.8 | 27.5 | +| 0.9 | 28.0 | + +Figure 5.3.2-3: Directivity of 8x8 URA w.r.t. array element separation. The graph shows Directivity [dB] on the y-axis (ranging from 16 to 30) versus element separation [λ] on the x-axis (ranging from 0.2 to 0.9). The curve shows a positive correlation, starting at approximately 16.5 dB at 0.2 λ and increasing to about 28 dB at 0.9 λ. + +**Figure 5.3.2-3. Directivity of uniform rectangular array (URA) with respect to array element separations.** + +The coupling effect may also pose challenges in wideband antenna array designs. It should be further noticed that the lower and higher band will see different impact of the mutual coupling effect among radiators due to different element spacing, i.e. the narrower element spacing suffers stronger mutual coupling. This effect could change the array pattern and input impedance matching of the antenna elements while being difficult to analytically predict. + +However, based on existing technology it has been agreed that multi-band AA with common radiated element with 19.5% percentage bandwidth in frequency range 24-29 GHz which includes n257/n258/n261, or with 26.3% percentage bandwidth in frequency range 37-48 GHz which includes n260/n259/n262 is feasible, at least from antenna array perspective. + +### 5.3.3 Interleaved array structures + +If the required multi-band antenna bandwidth is too great to be handled by a single antenna array (for the required steering range) it is also possible to use interleaved array structures such as stacked patches. Using stacked patches allows the different bands to feed different elements which are tuned for the specific band. This resolves some of the physical restrictions on the element size. However, if the arrays are stacked then restrictions still exist on the element separation in the array. + +Stacked patches can be designed with either a single dual band input or with separate input ports. As the bands are separated (for example 26GHz and 40GHz), it is possible to implement a diplexer to separate the bands for each of the antenna arrays, if necessary. + +![Figure 5.3.3-1: Two block diagrams showing Multi-band PA configurations. The left diagram shows a 'Multi-band PA' connected to a 'Single input Stacked patch multi-band antenna' which has two output ports labeled 'Band A' and 'Band B'. The right diagram shows a 'Multi-band PA' connected to a 'Diplexer', which is then connected to a 'Dual input Stacked patch multi-band antenna' with two input ports labeled 'Band A' and 'Band B'.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +Figure 5.3.3-1: Two block diagrams showing Multi-band PA configurations. The left diagram shows a 'Multi-band PA' connected to a 'Single input Stacked patch multi-band antenna' which has two output ports labeled 'Band A' and 'Band B'. The right diagram shows a 'Multi-band PA' connected to a 'Diplexer', which is then connected to a 'Dual input Stacked patch multi-band antenna' with two input ports labeled 'Band A' and 'Band B'. + +**Figure 5.3.3-1: Multi-band PA with stacked single band arrays (single and dual input ports)** + +A number of papers have been identified [19], [20], [21], and [22] which have demonstrated the feasibility of operational stacked patch antennas in the range 26 to 40 GHz + +Dual band performance can be achieved by using multiple patches stacked on top of each other. For example, in [20] a simple stack with a high band patch and a low band patch with a single input port was shown. Using these patches, a 2x2 array was demonstrated with acceptable levels of input match, boresight gain isolation and scanning angle. Although of course such small arrays are more suitable for a handset than a BS. + +In [22] a larger 8x4 array was demonstrated along with separate single band beamformers. While this is still small for BS purposes, it demonstrates the scalability of such structures and that larger BS-size arrays may be technically feasible to implement. + +In the above configuration, there are two types of feed line such as single input and dual input. The following analysis shows the difference between their performance. The 28+39 GHz (n257/n261, n260) combination was analysed, and figure 5.3.3-2 shows their structures. Both type support dual polarization. Upper patch is for Hi-band (n260) and lower patch is for Lo-band (n257/n261). + +![Figure 5.3.3-2: Two diagrams of dual polarized stacked patch antenna elements. The left diagram, labeled 'Single input type', shows a single feed line connected to a stacked patch with two output ports labeled '28+39GHz(H-pol.)' and '28+39GHz(V-pol.)'. The right diagram, labeled 'Dual input type', shows two separate feed lines connected to the stacked patch, with four output ports labeled '28GHz(V-pol.)', '28GHz(H-pol.)', '39GHz(H-pol.)', and '39GHz(V-pol.)'.](bb3354f497635d15bef873577125c48d_img.jpg) + +Figure 5.3.3-2: Two diagrams of dual polarized stacked patch antenna elements. The left diagram, labeled 'Single input type', shows a single feed line connected to a stacked patch with two output ports labeled '28+39GHz(H-pol.)' and '28+39GHz(V-pol.)'. The right diagram, labeled 'Dual input type', shows two separate feed lines connected to the stacked patch, with four output ports labeled '28GHz(V-pol.)', '28GHz(H-pol.)', '39GHz(H-pol.)', and '39GHz(V-pol.)'. + +**Figure 5.3.3-2: Dual polarized stacked patch antenna element for 28+39GHz combination.** + +The following simulation result shows antenna gain of both stacked patch antenna elements. + +![Figure 5.3.3-3: Performance of multi-band stacked patch antenna element for 28+39GHz combination. The figure consists of three subplots: (a) Single input type, (b) Dual input type(28GHz), and (c) Dual input type(39GHz). Each subplot shows Gain (dBi) vs Frequency (GHz) from 20 to 45 GHz. The plots show two main resonance peaks around 28 GHz and 39 GHz. The single input type (a) shows a gain of approximately 4.99 dBi at 26.5 GHz, 5.65 dBi at 29.5 GHz, 5.07 dBi at 37.0 GHz, and 4.67 dBi at 40.0 GHz. The dual input type (b) and (c) show similar performance with slight variations in the resonance peaks.](6e5a85131eedf6b98db62877ee64506e_img.jpg) + +Figure 5.3.3-3: Performance of multi-band stacked patch antenna element for 28+39GHz combination. The figure consists of three subplots: (a) Single input type, (b) Dual input type(28GHz), and (c) Dual input type(39GHz). Each subplot shows Gain (dBi) vs Frequency (GHz) from 20 to 45 GHz. The plots show two main resonance peaks around 28 GHz and 39 GHz. The single input type (a) shows a gain of approximately 4.99 dBi at 26.5 GHz, 5.65 dBi at 29.5 GHz, 5.07 dBi at 37.0 GHz, and 4.67 dBi at 40.0 GHz. The dual input type (b) and (c) show similar performance with slight variations in the resonance peaks. + +Figure 5.3.3-3: Performance of multi-band stacked patch antenna element for 28+39GHz combination. + +Table 5.3.3-1: Performance of multi-band stacked patch antenna element for 28+39GHz combination. + +| | Antenna element gain [dBi] | | | | +|-------------------|----------------------------|---------|---------|---------| +| | 26.5GHz | 29.5GHz | 37.0GHz | 40.0GHz | +| Single input type | 4.99 | 5.65 | 5.07 | 4.67 | +| Dual input type | 4.47 | 5.37 | 4.42 | 4.26 | + +From antenna performance perspective, the difference between single input and dual input of stacked patch multi-band antenna is small, and both types could achieve 4 to 5dBi element gain including frequency roll-off. Considering that 4 to 5dBi is generally set as the antenna element gain in a link budget for mmWave communication equipment, performance impact of both stacked patch multi-band antennas is small. In addition, it is possible to expand the support frequency range by increasing thickness of the antenna as needed. + +From the above discussions for different antenna array structures, either a multi-band antenna array (broadband or with multi-resonances) or separate antenna arrays with lower percentage bandwidth can be used in FR2 multiband RIB/BS. In comparison to separate antenna arrays, a consolidated multi-band design is more compact and reduces costs, but trades performance aspects that can be optimized for in separate designs. On the other hand, having separate designs enables dedicated optimizations, yielding better performance. However, this comes at the cost of a significantly larger circuit area being used for two designs and additional integration losses from lines and transitions. + +### 5.3.4 MIMO EM simulation results + +To enhance the capacity and reliability of data transmission the BSs utilize MIMO of antenna arrays. Therefore, the antenna array designs need to ensure key metrics (such as isolation between antenna elements and diversity performance parameters) achievable in order to deliver expected MIMO performances. The following simulation results demonstrate the capability of a dual-band antenna array design to achieve acceptable performance metrics required for the MIMO. + +Uniform phased antenna arrays in multiple panels spanning beams in two dimensions (2D) are employed at BSs, to serve multiple users within the same time-frequency resource via spatial beamforming across the azimuth and elevation domains. Figure 5.3.4-1 shows the example of 2D multibeam scanning of an 8-panel massive MIMO antenna array system of in 3D view at 26 GHz and 38 GHz, which has been designed by considering antenna element separation of $0.5\lambda$ at higher limit. When various phased antenna arrays are employed in multiple panels in a small physical size, the mutual coupling between them can greatly affect the performance. The isolation between panels' adjacent antenna elements and correlation between the radiated beams needs to be ensured. The performance metrics are isolation (between antenna elements) and diversity performance parameters e.g. envelope correlation coefficient (ECC). The ECC is commonly used to measure amount of radiated beams correlation. The ECC values are calculated using radiated far-field equation in [23]. For good diversity action the ECC should be low. + +![Figure 5.3.4-1: 3D visualization of 2D multibeam scanning for an 8-panel MIMO antenna array system at 26 GHz (left) and 38 GHz (right). The figure shows two panels, each with 8 antenna elements (AA1-AA8) arranged in a grid. Each element is shown with a 3D beam pattern, color-coded from blue (low gain) to red (high gain). The beams are steered to different directions across the panels, demonstrating the multibeam scanning capability. The 38 GHz panel shows more complex beam patterns with multiple lobes compared to the 26 GHz panel.](85b10db535b22e64c7d37f362705ddbf_img.jpg) + +Figure 5.3.4-1: 3D visualization of 2D multibeam scanning for an 8-panel MIMO antenna array system at 26 GHz (left) and 38 GHz (right). The figure shows two panels, each with 8 antenna elements (AA1-AA8) arranged in a grid. Each element is shown with a 3D beam pattern, color-coded from blue (low gain) to red (high gain). The beams are steered to different directions across the panels, demonstrating the multibeam scanning capability. The 38 GHz panel shows more complex beam patterns with multiple lobes compared to the 26 GHz panel. + +**Figure 5.3.4-1. Example of 2D multibeam scanning of an 8-panel MIMO antenna array system in 3D view: 26 GHz (left), 38 GHz (right)** + +MIMO diversity performance of massive MIMO antenna system has been evaluated for three different cases by considering one panel steering the beam at different angles with respect to the other panels' main beam in a fixed direction. + +**Case 1:** When Panel 1 (AA1) radiates the field in the azimuth plane at $(40^\circ, 0^\circ)$ and Panel 2 (AA2) steers the beam at different angles i.e. $-40^\circ$ , $-20^\circ$ , $0^\circ$ , $20^\circ$ , and $40^\circ$ in the azimuth plane. + +**Case 2:** When Panel 1 (AA1) radiates the field in the elevation plane at $(0^\circ, 20^\circ)$ and Panel 3 (AA3) steers the beam at different angles i.e. $-40^\circ$ , $-20^\circ$ , $0^\circ$ , $20^\circ$ , and $40^\circ$ in the elevation plane. + +**Case 3:** When Panel 1 (AA1) radiates field at $(20^\circ, 20^\circ)$ and Panel 4 (AA4) steers beam at different angles i.e. $(-40^\circ, -40^\circ)$ , $(-20^\circ, -20^\circ)$ , $(0^\circ, 0^\circ)$ , $(20^\circ, 20^\circ)$ , and $(40^\circ, 40^\circ)$ . + +![Figure 5.3.4-2: Diversity performance plots showing ECC vs Frequency (GHz) for different beam steering scenarios in azimuth, elevation, and diagonal planes.](1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg) + +Figure 5.3.4-2 consists of three line graphs showing the Envelope Correlation Coefficient (ECC) versus Frequency (GHz) from 26 GHz to 40 GHz. Each graph represents a different beam steering scenario: + +- Top Left: When beam steered in azimuth plane.** The legend includes: + - ECC\_Panell at (40°,0°) & Panel2 at (-40°,0°) + - ECC\_Panell at (40°,0°) & Panel2 at (-20°,0°) + - ECC\_Panell at (40°,0°) & Panel2 at (0°,0°) + - ECC\_Panell at (40°,0°) & Panel2 at (20°,0°) + - ECC\_Panell at (40°,0°) & Panel2 at (40°,0°) +- Top Right: When beam steered in elevation plane.** The legend includes: + - ECC\_Panell at (0°,20°) & Panel2 at (0°,-40°) + - ECC\_Panell at (0°,20°) & Panel2 at (0°,-20°) + - ECC\_Panell at (0°,20°) & Panel2 at (0°,0°) + - ECC\_Panell at (0°,20°) & Panel2 at (0°,20°) + - ECC\_Panell at (0°,20°) & Panel2 at (0°,40°) +- Bottom: When beam steered diagonally.** The legend includes: + - ECC\_Panell at (20°,20°) & Panel2 at (-40°,-40°) + - ECC\_Panell at (20°,20°) & Panel2 at (-20°,-20°) + - ECC\_Panell at (20°,20°) & Panel2 at (0°,0°) + - ECC\_Panell at (20°,20°) & Panel2 at (20°,20°) + - ECC\_Panell at (20°,20°) & Panel2 at (40°,40°) + +Figure 5.3.4-2: Diversity performance plots showing ECC vs Frequency (GHz) for different beam steering scenarios in azimuth, elevation, and diagonal planes. + +**Figure 5.3.4-2. Diversity performance: when beam steered in azimuth plane, when beam steered in elevation plane, when beam steered diagonally** + +BSs implemented with MIMO antenna systems can serve multiple users via spatial beamforming across the azimuth and elevation domains with good diversity performance over multiple frequency bands. + +### 5.3.5 Diplexer technology + +The following discusses a use case of diplexer in FR2 multiband RIB architecture. + +To support across the different frequency group with dual input stacked patch multi-band antenna and multi-band PA, a diplexer is useful to divide each frequency group's signals as figure 5.3.5-1. To implement a diplexer between multi-band antenna and PA, diplexer should be smaller than antenna elements interval of phased array. + +![Figure 5.3.5-1: Block diagram showing a Multi-band PA connected to a Diplexer, which is then connected to a Dual input stacked patch multi-band array antenna with separate outputs for Band A ANT and Band B ANT.](e9b43ac020435f8121e8592f31afdc52_img.jpg) + +The diagram illustrates the signal flow from a combined 'Band A + Band B' input through a 'Multi-band PA'. The output of the PA enters a 'Diplexer' (represented by a dashed box containing two coupled lines). The diplexer separates the signals into two distinct outputs: 'Band A ANT' and 'Band B ANT'. These outputs are then fed into a 'Dual input stacked patch multi-band array antenna'. + +Figure 5.3.5-1: Block diagram showing a Multi-band PA connected to a Diplexer, which is then connected to a Dual input stacked patch multi-band array antenna with separate outputs for Band A ANT and Band B ANT. + +**Figure 5.3.5-1 Diplexer between multi-band PA and stacked patch multi-band array antenna.** + +The following simulation result shows the feasibility of a diplexer and its performance impact based on the above condition. Figure 5.3.5-2 is for a diplexer for 28+39GHz (n257/n261, n260) band combination. 1dB insertion loss and >50dB attenuation are achieved. + +![Graph showing S(dB) vs Freq [GHz] for 28+39GHz (n257/n261, n260) diplexer performance. The graph shows two curves: S(2,1) in red and S(3,1) in blue. The red curve has a peak around 28 GHz and a dip around 39 GHz. The blue curve has a peak around 39 GHz and a dip around 28 GHz. Markers M01, M02, M03, and M04 are indicated on the graph.](20e597e389dfd8d131e05ad6e1617dcd_img.jpg) + +| Marker | Parameter | Freq [GHz] | S(dB) | +|--------|-----------|------------|--------| +| M01 | S(2,1) | 26.500 | -0.637 | +| M02 | S(2,1) | 29.500 | -1.082 | +| M03 | S(3,1) | 37.000 | -1.026 | +| M04 | S(3,1) | 40.000 | -1.034 | + +Graph showing S(dB) vs Freq [GHz] for 28+39GHz (n257/n261, n260) diplexer performance. The graph shows two curves: S(2,1) in red and S(3,1) in blue. The red curve has a peak around 28 GHz and a dip around 39 GHz. The blue curve has a peak around 39 GHz and a dip around 28 GHz. Markers M01, M02, M03, and M04 are indicated on the graph. + +Figure 5.3.5-2. Diplexer performance for 28+39GHz combination + +The dimension of this diplexer is 4.0 mm x 1.8 mm or less in LTCC substrate, and dielectric constant of this substrate is 6.4, Q value is 200. Most of the current base station supports dual polarization, so the required area to implement a diplexer should be doubled and it becomes 4.0mm x 3.6mm. In case of 28+39GHz combination, $0.5\lambda$ at the centre frequency is 4.51mm. So if antenna element interval is $0.5\lambda$ or larger, it is possible to implement diplexer below each antenna elements. + +For other multi-band combinations such as 26+40GHz (n258, n259/n260) and 28+40GHz (n257/n261, n259/n262), the following examples are provided. Over 50dB attenuation is achieved for the all band combinations and their performance impact is around 1dB. + +![Two graphs showing diplexer performance for 26+40GHz and 28+40GHz combinations. The left graph is for 26+40GHz (n258, n259/n262) and the right graph is for 28+40GHz (n257/n261, n259/n262). Both graphs show S(dB) vs Freq [GHz] with red and blue curves representing S(2,1) and S(3,1) respectively. Markers M05 through M12 are indicated on the graphs.](98ff4ec9e120afa420dbe08b0d8d77b6_img.jpg) + +| Marker | Parameter | Freq [GHz] | S(dB) | +|--------|-----------|------------|--------| +| M05 | S(2,1) | 24.250 | -0.657 | +| M06 | S(2,1) | 27.500 | -0.706 | +| M07 | S(3,1) | 39.500 | -0.841 | +| M08 | S(3,1) | 48.200 | -0.585 | +| M09 | S(2,1) | 26.500 | -0.913 | +| M10 | S(2,1) | 29.500 | -1.130 | +| M11 | S(3,1) | 39.500 | -0.836 | +| M12 | S(3,1) | 48.200 | -0.555 | + +Two graphs showing diplexer performance for 26+40GHz and 28+40GHz combinations. The left graph is for 26+40GHz (n258, n259/n262) and the right graph is for 28+40GHz (n257/n261, n259/n262). Both graphs show S(dB) vs Freq [GHz] with red and blue curves representing S(2,1) and S(3,1) respectively. Markers M05 through M12 are indicated on the graphs. + +Figure 5.3.5-3. Diplexer performance for 26+40GHz, 28+40GHz combinations + +## 5.4 Other + +In this section, a number of other considerations for FR2-1 wideband BS from the feasibility point of view that are not considered in the preceding sections are mentioned. + +### Digital considerations + +To support a large bandwidth, it is necessary to provide a high sampling rate for ADC and DAC. For individual Frequency Band Groups (e.g. 24.5-29.5GHz, n257+n258), the bandwidth to be supported may be more than 5GHz, and to cover the full FR2-1 the bandwidth might be up to 24GHz. If linearization would be seen later to be feasible for multiband BS, then DAC/ADC would need to support for the feedback and correction, which poses another challenge to DAC/ADC. + +Potentially only the in band spectrum could be generated by separate converters which would reduce the requirements on individual converters. + +In an implementation, the architecture, RF performance and power consumption of the analogue/digital interface would be key considerations. The ADC and DAC complexity and power consumption could be reduced by reducing the sampling resolution, but this would impact TX factors such as EVM and emissions and RX factors such as dynamic range and RX EVM. For this reason, care would need to be taken that requirements on e.g. EVM, receiver dynamic range and demodulation performance would be achievable. + +In addition to the DAC and ADC, the large bandwidth and sampling rates would lead to very high volumes of data to be moved within the radio architecture. Data transport and interface architectures would need to support the very high data volume. Reducing the data volume (e.g. by reducing the sampling resolution) would lead to similar considerations as for ADC and DAC on meeting requirements such as EVM, emissions, RX dynamic range and demodulation. + +In addition to the interface bandwidth, the digital transport latency may also impact radio near algorithms (such as DPD, CFR) and could impact the performance of the transmitter and receiver. It is not clear whether the need to support a much larger interface bandwidth could impact the interface latency. + +Digital filtering may be needed for meeting selectivity and blocking requirements depending on the sensitivity and architecture. The large sampling rates and bandwidth would increase the amount of computational power needed for digital filtering, and potentially the achievable steepness of the filters. This could impact the feasibility of meeting TX EVM and RX selectivity, blocking and demodulation requirements. + +### Analogue considerations + +The possibilities for analogue filtering within an FR2-1 AAS array are extremely limited. The filter in a typical single-band FR2 BS may not be placed before the antenna. However, it could be the case of multi-band, due to the multi-frequency signal going through the PA if the PA is highly nonlinearity, or due to the architecture splitting multi-band signals. And thus filter before the antenna may be needed. + +Choosing where to place filter components is an important part of a multi-band solution as it impacts the overall performance. For instance, if a filter would need to be placed before the antenna, then there are other issues in practice with insertion loss and power unbalancing due to non-identical filter for each branch. + +The regulatory requirements in the *inter RF gap* and the linearity of the transmitter will set the boundary for the analogue filtering. The feasibility of analogue filtering may impact the ability to meet some regulatory emissions requirements and out of band blocking, and if the filter has ripple also the EVM may be impacted. + +Depending on the array architecture, it may be necessary to split different frequency components of the multi-band signal and route them to different antenna elements, e.g. in architectures using diplexer. The splitting and additional routing can have implications for TX power loss and RX sensitivity, and the placement of components needs to be carefully considered. For instance, placing the diplexer before the PA is preferred from a design loss and power dissipation perspective. This is because the insertion loss of the diplexer occurs at a lower power level and can be accommodated by a simple increase in driver gain. Conversely, if the diplexer is placed after the PA, the insertion loss of the diplexer directly reduces the power available to the antenna array and leads to more thermal dissipation. + +On the other hand, it is worth noting that if the power loss is significantly different/uneven between antenna branches, then beamforming may be degraded, and calibration may be required which may bring complexity to the architecture. This may impact the feasibility of the multi-band solution, although since TX power and RX sensitivity are subject to declarations it may not impact the requirements definition. As shown in Clause 4.2.1 Option #4, splitting and additional routing can be avoided by using a multi-band antenna, such as a single input stacked patch design. + +Dedicated PAs for the desired frequency ranges may be adopted from a design loss and power dissipation perspective, as the narrower band designs will have better efficiency and the thermal dissipation will be spread out over a larger area. + +# --- 6 Study on RF requirements + +## 6.1 Definition of FR2 multi-band BS + +The existing definitions of single-band RIB and *multi-band RIB* for FR1 defined in TS 38.104 are shown as below: + +**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*. + +**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 RIB*. + +From definition of *multi-band RIB* for FR1, the transmitter or receiver of *multi-band RIB* dependent BS have the capability to process two or more carriers from the different bands in common active RF components simultaneously. For FR2-1, the existing *multi-band RIB* definition for FR1 can be reused. + +As the same with FR1, the existing explanations on BS capable of supporting operation in multiple operating bands in 38.104 [2] for FR1 are sufficient. The same descriptions can be applied to FR2-1, i.e. + +- *BS type 2-O* 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 multi-band RIBs. + - A combination of single-band RIBs and multi-band RIBs provides support of the BS type 2-O capability of operation in multiple operating bands. + +## 6.2 Re-using FR1 multi-band methods + +On requirements of FR2-1 multi-band BS, the followings are agreed: + +- Existing definitions of *Inter RF Bandwidth gap* and Base Station RF Bandwidth for FR1 multi-band operation can be reused for FR2-1 multi-band operation. +- The existing method for requirement for FR1 multi-band operation can be reused for that for FR2-1 multi-band operation. + +The impacts on requirements of FR2-1 multi-band BS in TS 38.104 [2] are summarized in Table 6.2-1. + +**Table 6.2-1: Impacts on requirements of FR2-1 multi-band BS in TS 38.104** + +| OTA Clause | Requirement | Impacts | +|------------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| 9.5.2 | Transmitter OFF power | Existing BS type 2-O requirements can be applied. | +| 9.7.3.3 | ACLR | Specify ACLR and CACLR requirements inside the Inter RF Bandwidth gap for a BS type 2-O multi-band RIB . | +| 9.7.4.3 | OBUE | Specify cumulative OBUE limits the Inter RF Bandwidth gap for a BS type 2-O multi-band RIB . | +| 9.7.5.3 | Transmitter spurious emissions | Apply BS type 2-O requirements with the same BS type 1-O multi-band RIB exceptions to BS type 2-O multi-band RIB . | +| 9.8.2 | Transmitter intermodulation | No transmitter intermodulation requirement for BS type 2-O . | +| 10.5.1.3 | ACS | Specify ACS requirements the Inter RF Bandwidth gap for a BS type 2-O multi-band RIB . | +| 10.5.2.3 | In-band blocking | Specify in-band blocking requirements the Inter RF Bandwidth gap for a BS type 2-O multi-band RIB . | +| 10.6.3 | Out-of-band blocking | Apply BS type 2-O requirements with the same BS type 1-O multi-band RIB exceptions to BS type 2-O multi-band RIB . | +| 10.7.3 | Receiver spurious emissions | Apply BS type 2-O requirements with the same BS type 1-O multi-band RIB exceptions to BS type 2-O multi-band RIB . | +| 10.8.3 | Receiver Intermodulation | Specify receiver intermodulation requirements the Inter RF Bandwidth gap for a BS type 2-O multi-band RIB . | + +## 6.3 Re-using FR1 exceptions + +On requirement exceptions of FR2-1 multi-band BS, the followings are agreed: + +- The FR1 exceptions for spurious emissions, RX spurious emissions and out of band blocking could be applied in FR2-1, as well as all other multi-band considerations made for FR1 for transmit ON/OFF power, operating band unwanted emissions, transmitter/receiver intermodulation, in-band selectivity and blocking. + +**Table 6.3-1: Impacts on requirement exceptions of FR2-1 multi-band BS in TS 38.104** + +| OTA Clause | Requirement | Impacts | +|------------|--------------------------------|----------------------------------------------------------------------------------------------------| +| 9.7.5.3 | Transmitter spurious emissions | Apply the same BS type 1-O multi-band RIB exceptions to BS type 2-O multi-band RIB . | +| 10.6.3 | Out-of-band blocking | Apply the same BS type 1-O multi-band RIB exceptions to BS type 2-O multi-band RIB . | +| 10.7.3 | Receiver spurious emissions | Apply the same BS type 1-O multi-band RIB exceptions to BS type 2-O multi-band RIB . | + +## 6.4 FR2-1 specific multi-band requirements + +FR2-1 specific multi-band requirements refer to requirements specific to FR2-1 compared to those currently applied to FR1. It was agreed that this study focuses on the *multi-band RIB* within the same frequency group meanwhile the study on *multi-band RIB* across different frequency groups not precluded. With this agreement, together with the agreements on re-using FR1 multi-band methods and exceptions, there is currently no need for new FR2-1 specific multi-band requirements as the current FR1 multi-band methods and exceptions can be applied to FR2-1 and are sufficient for FR2-1 *multi-band RIB* for all band combinations within the same frequency group. For *multi-band RIB* for band combinations across different frequency groups, the current FR1 multi-band methods and exceptions can also be applied, while FR2-1 specific multi-band requirements may be considered in the future taking into account the implementation challenges. + +# 7 Summary and further work + +The feasibility study for the essential RF components and sub-systems for an FR2-1 multi-band system were carried out and found that: + +- Multi-band implementations with percentage BW of up to 19.5% are feasible. +- Multi-band implementations with greater percentage BW's may be feasible in the future. + +Within these percentage BWs some design blocks such as the PA, and RF front end components are capable of true multi-band performance, other blocks and specifically the phase shifters used for beam forming the different bands need to be applied to separate band specific solutions. There are currently no proposed solutions to enable a wide band beam former to steer beams for different bands in different directions. + +Antennas and antenna arrays are limited to certain maximum percentage BW's however MB solutions using multiple antenna arrays have been investigated and solutions within the agreed percentage BW's above have been identified. + +Other considerations, i.e. on a need of DPD and complications of digital and analogue designs for a wideband / multiband BS are also analysed. + +Considering the wide range of FR2-1 operating bands and potential combinations FR2-1 operating bands have been considered within frequency groups with limited percentage BW's as shown in table 5.1-1 and feasibility analysed within these groups. However, whilst practical limits exist which may limit multi-band solutions to be within these groups no restrictions need to be used in the technical specification and as such frequency groups do not need to be defined with the updates of the technical specifications. On the other hand, as highlighted in clause 6.2 study of solutions across frequency groups may be further studied and the use of additional multi-band requirements may be considered in the future for percentage BW's greater than 19.5%. + +For updating the technical specifications, FR2-1 multi-band requirements are to be added to the existing NR 3GPP TS 38.104 [2] and 3GPP TS 38.141-2 [30] technical specifications, using the same approach as FR1 multi-band as described in clause 6. The existing MB RIB definition as well as the explanations on BS capable of supporting operation in multiple operating bands with different implementations at the RIB in 38.104 [2] for FR1 can also apply to FR2-1. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|----------------|------------|------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-08 | RAN4#104-e | R4-2214779 | | | | TR skeleton | 0.0.1 | +| 2022-11 | RAN4#105 | R4-2219148 | | | | The following TP approved at RAN4#104-bis-e was implemented:
R4-2217502 TP for deployment scenarios | 0.1.0 | +| 2023-03 | RAN4#106 | R4-2301419 | | | | The following TPs approved at RAN4#105 were implemented:
R4-2220295 TP for TR 38.877: On definition of FR2-1 multi-band BS in clause 6.1
R4-2220294 TP to TR 38.877: Requirements of FR2-1 multi-band BS | 0.2.0 | +| 2023-04 | RAN4#106-bis-e | R4-2305882 | | | | The following TPs approved at RAN4#106 were implemented:
R4-2302894 TP to TR 38.877: FR2-1 specific multi-band requirements
R4-2302895 TP to TR 38.877: General paragraph for feasibility aspects
R4-2302896 TP to TR 38.877: DPD in FR2 multiband BS
R4-2302897 TP on Antenna array capability
R4-2302898 TP on RF front end capability
R4-2302899 TP to TR 38.877: phase shifter in FR2 multiband BS
R4-2302900 TP to TR 38.877: Other feasibility aspects | 0.3.0 | +| 2023-05 | RAN4#107 | R4-2307753 | | | | The following TPs approved at RAN4#106-bis-e were implemented:
R4-2304118 TP to TR 38.877: Phase shifter and antenna
R4-2304712 TP to TR 38.877: Corrections in DPD sections
R4-2305880 TP to TR 38.877: Antenna array
R4-2305881 TP to TR 38.877: Fractional bandwidth and percentage bandwidth
R4-2305883 TP for Clause 3: abbreviations
R4-2305884 TP on SI summary
R4-2305885 TP for TR 38.877: Additional feasibility aspects | 0.4.0 | +| 2023-05 | RAN4#107 | R4-2309759 | | | | The following TPs approved at RAN4#107 were implemented:
R4-2307230 TP to TR 38.877: Clause 4.2 and Clause 5
R4-2309756 TP to TR 38.877: Terms and Symbols
R4-2309757 Clean up and correction to TR 38.877
R4-2309758 TP to TR 38.877: Antenna array | 0.5.0 | +| 2023-06 | RAN#100 | RP-231057 | | | | Presented to RAN for approval. | 1.0.0 | +| 2023-06 | RAN#100 | | | | | First version of Release 18 | 18.0.0 | +| 2023-09 | RAN#101 | RP-232506 | 0001 | 1 | F | [FS_NR_BS_RF_evo] CR to TR 38.877 on correction and additional clarification on phase shifters for MB BS | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38878/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38878/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0b77914482a58699e8029d2284acdb425b9a7ed --- /dev/null +++ b/marked/Rel-18/38_series/38878/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa4ff55f5d3ec34b2353651072d315c626d6d073fee7a93717350f044df722bd +size 9376 diff --git a/marked/Rel-18/38_series/38878/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38878/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..472e300aeaa951ad8ce484805762a94a78fd342b --- /dev/null +++ b/marked/Rel-18/38_series/38878/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:156b5817873a3326e48275c32ce4a62b52edbbc6d31cbf89c92b578878ca0edf +size 5667 diff --git a/marked/Rel-18/38_series/38878/925f55ce69802b9d3b00546382663ee2_img.jpg b/marked/Rel-18/38_series/38878/925f55ce69802b9d3b00546382663ee2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55404b974d7534f4acfe1fbf5879256789fa8802 --- /dev/null +++ b/marked/Rel-18/38_series/38878/925f55ce69802b9d3b00546382663ee2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e97f3bd306dceac4b9104dc925118960fabac8fb417316e241a1cdfb2c31845b +size 55394 diff --git a/marked/Rel-18/38_series/38878/aa14b9ec884bf40ce06c161be468cd84_img.jpg b/marked/Rel-18/38_series/38878/aa14b9ec884bf40ce06c161be468cd84_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6f01e416d7aef1aaf319d4fd6472fc7893660e3 --- /dev/null +++ b/marked/Rel-18/38_series/38878/aa14b9ec884bf40ce06c161be468cd84_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d9d3e0204c172e4810ef70f2a4a42da79824b03aa45ea04f52b04439f81e455 +size 56329 diff --git a/marked/Rel-18/38_series/38878/bedcca5cdf168e3508ef511d94ec514c_img.jpg b/marked/Rel-18/38_series/38878/bedcca5cdf168e3508ef511d94ec514c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31e2b7e89cca90530fa2f473cf9d01c6d7c1675f --- /dev/null +++ b/marked/Rel-18/38_series/38878/bedcca5cdf168e3508ef511d94ec514c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25125360c8eba6ac86a099f754b007811d8c7ab3ad1db9fcc8ef1b08df2c065b +size 107688 diff --git a/marked/Rel-18/38_series/38878/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-18/38_series/38878/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a89f8afa2e003bb817ffcf078dc8fad269c7738a --- /dev/null +++ b/marked/Rel-18/38_series/38878/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3dfd38e0175045d2257dc9fdbab192c2a492e34556ea85b5ab2d3674fc9ce98a +size 16859 diff --git a/marked/Rel-18/38_series/38878/raw.md b/marked/Rel-18/38_series/38878/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4856cc34709131591e7aa0ee74ef64a32164aa80 --- /dev/null +++ b/marked/Rel-18/38_series/38878/raw.md @@ -0,0 +1,603 @@ + + +# 3GPP TR 38.878 V18.1.0 (2023-12) --- + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Networks; NR demodulation performance evolution (Release 18)** --- + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green wave-like graphic 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 icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath. + +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 ..... | 4 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 6 | +| 3.1 Terms..... | 6 | +| 3.2 Symbols..... | 6 | +| 3.3 Abbreviations ..... | 6 | +| 4 Advanced receiver to cancel inter-user interference for MU-MIMO ..... | 7 | +| 4.1 Scenario and interference modelling..... | 7 | +| 4.1.1 Scenario ..... | 7 | +| 4.1.2 Interference model..... | 9 | +| 4.2 Receiver structure..... | 10 | +| 4.2.1 General ..... | 10 | +| 4.2.2 E-MMSE IRC receiver ..... | 10 | +| 4.2.3 R-ML receiver ..... | 11 | +| 4.3 Analysis on the required information..... | 11 | +| 4.4 Link performance characterization..... | 12 | +| 4.4.1 Parameters for link level evaluation ..... | 12 | +| 4.4.2 Link level simulation results ..... | 14 | +| 4.4.3 Summary of link level evaluation..... | 18 | +| 5 Conclusions..... | 21 | +| Annex A: Change history | 22 | + +# 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 technical report documents the Phase I study outcome on the advanced receiver to cancel inter-user interference for MU-MIMO, with the detailed objectives as follows: + +- Evaluate and specify advanced receiver to cancel inter-user interference for MU-MIMO +- Phase I: Study the performance gain, reference receiver assumption, interference modeling, testability, required signalling overhead, as well as impact on other WGs + - Further discuss reference receiver assumption with below candidates + - E-MMSE-IRC + - R-ML + - Target scenario: Focus on slot based transmission + +# --- 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". + +# --- 3 Definitions, 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 + +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]. + +| | | +|-----|-------------------| +| AL | Aggregation level | +| AP | Antenna port | +| BWP | Bandwidth part | +| CBW | Channel bandwidth | + +| | | +|------------|-----------------------------------------------------------------------| +| CDM | Code division multiple | +| CORESET | Control resource set | +| CSI-RS | Channel state information reference signal | +| DCI | Downlink Control Information | +| DMRS | Demodulation reference signal | +| E-MMSE-IRC | Enhanced Minimum mean square error - interference rejection combining | +| FD-CDM | Frequency division - code division multiple | +| FDD | Frequency Division Duplex | +| FDRA | Frequency domain resource allocation | +| HARQ | Hybrid Automatic Repeat Request | +| MCS | Modulation and Coding Scheme | +| MMSE-IRC | Minimum mean square error - interference rejection combining | +| MU-MIMO | Multi-user-Multiple Input Multiple Output | +| NZP | Non-zero-power | +| OFDM | Orthogonal Frequency Division Multiplexing | +| PDSCH | Physical Downlink Shared Channel | +| PRG | Precoding resource block group | +| PSS | Primary synchronization signal | +| PT-RS | Phase-tracking reference signal | +| QAM | Quadrature Amplitude Modulation | +| QCL | Quasi co-location | +| RB | Resource block | +| RE | Resource element | +| R-ML | Reduced complexity Maximum likelihood | +| RRC | Radio Resource Control | +| SCS | Subcarrier spacing | +| SNR | Signal-to-noise ratio | +| SSB | Synchronization signal block | +| SSS | Secondary synchronization signal | +| TBS | Transport block size | +| TCI | Transmission configuration indicator | +| TDL | Tapped delay line | +| TDRA | Time domain resource allocation | +| TM | Transmission mode | +| ULA | Uniform Linear Array | + +# --- 4 Advanced receiver to cancel inter-user interference for MU-MIMO + +## 4.1 Scenario and interference modelling + +### 4.1.1 Scenario + +MU-MIMO allows gNB to transmit data to multiple UEs in the same time-frequency resources through spatial multiplexing. The process of selecting paired UEs is called ‘pairing’. As illustrated in Figure 4.1.1-1, UE1 and UE2 are paired and gNB transmits data to both UEs with suitable precoders through the same time-frequency resources. However, the gNB cannot guarantee the perfect pairing of multiple users in the real network. The paired UEs may not perfectly spatially orthogonal to each other and this will induce the intra-cell interference between paired UEs. + +![Diagram of a gNB transmitting data to paired UE1 and UE2 using the same time-frequency resources.](d0abac95583b52a3b35f74a215567334_img.jpg) + +The diagram shows a gNB (base station) at the top center. Below it, two user equipments, labeled 'paired UE1' and 'paired UE2', are shown. Arrows from the gNB point to both UE1 and UE2, indicating simultaneous data transmission. The entire setup is enclosed within a large oval shape. + +Diagram of a gNB transmitting data to paired UE1 and UE2 using the same time-frequency resources. + +**Figure 4.1.1-1. gNB transmit data to paired UE1 and UE2 with the same time-frequency resources** + +To evaluate the performance of UE with intra-cell interference induced by spatial multiplexing, the following scenarios illustrated from Figure 4.1.1-2 to Figure 4.1.1-3 are considered for the case of number of paired UEs is 2. Moreover, scenario illustrated in Figure 4.1.1-4 is considered for the case of number of paired UEs is 3. + +- Target UE with single DMRS antenna port: + - Scenario 1: Number of CDM group without data is 1 + - AP1000 for target UE, AP1001 for interference UE +- Target UE with two DMRS antenna ports: + - Scenario 2: Number of CDM group without data is 2 + - AP1000 and 1001 for target UE, AP1002 and 1003 for interference UE +- Target UE with single DMRS antenna port: + - Scenario 3: Number of CDM group without data is 1 + - AP1000 for target UE, AP1001 for 2 interference UEs with different frequency domain allocation. + +![Resource grid diagrams for Target UE and Interference UE in Scenario 1.](aa14b9ec884bf40ce06c161be468cd84_img.jpg) + +The figure displays two resource grids side-by-side. The left grid is labeled 'Target UE' and the right grid is labeled 'Interference UE'. Both grids have 12 columns and 10 rows. The first column in each grid is shaded grey, representing PDCCH. The remaining columns are blue, representing PDSCH. In the 'Target UE' grid, green squares (AP1000) are placed in the 2nd, 4th, 6th, 8th, and 10th rows of the first PDSCH column (column 2). In the 'Interference UE' grid, yellow squares (AP1001) are placed in the 1st, 3rd, 5th, 7th, and 9th rows of the first PDSCH column (column 2). A legend at the bottom indicates: + + +- Grey square: PDCCH +- Blue square: PDSCH +- Green square: AP1000 +- Yellow square: AP1001 + +Resource grid diagrams for Target UE and Interference UE in Scenario 1. + +**Figure 4.1.1-2: Scenario 1, number of CDM group without data is 1 and AP1000 for target UE, AP1001 for interference UE** + +![Figure 4.1.1-3: Scenario 2, number of CDM group without data is 2 and AP1000 and 1001 for target UE, AP1002 and 1003 for interference UE. The figure shows four resource grids. The top-left grid is for the Target UE, showing PDCCH (grey) and PDSCH (blue) resources, with AP1000 (green) and AP1001 (yellow) pilot symbols. The top-right grid is for the Interference UE, showing PDCCH (grey) and PDSCH (blue) resources, with AP1002 (orange) and AP1003 (purple) pilot symbols. The bottom-left grid is for the Target UE, showing PDCCH (grey) and PDSCH (blue) resources, with AP1001 (yellow) pilot symbols. The bottom-right grid is for the Interference UE, showing PDCCH (grey) and PDSCH (blue) resources, with AP1003 (purple) pilot symbols. A legend at the bottom identifies the colors: PDCCH (grey), PDSCH (blue), AP1000 (green), AP1001 (yellow), AP1002 (orange), and AP1003 (purple).](bedcca5cdf168e3508ef511d94ec514c_img.jpg) + +Figure 4.1.1-3: Scenario 2, number of CDM group without data is 2 and AP1000 and 1001 for target UE, AP1002 and 1003 for interference UE. The figure shows four resource grids. The top-left grid is for the Target UE, showing PDCCH (grey) and PDSCH (blue) resources, with AP1000 (green) and AP1001 (yellow) pilot symbols. The top-right grid is for the Interference UE, showing PDCCH (grey) and PDSCH (blue) resources, with AP1002 (orange) and AP1003 (purple) pilot symbols. The bottom-left grid is for the Target UE, showing PDCCH (grey) and PDSCH (blue) resources, with AP1001 (yellow) pilot symbols. The bottom-right grid is for the Interference UE, showing PDCCH (grey) and PDSCH (blue) resources, with AP1003 (purple) pilot symbols. A legend at the bottom identifies the colors: PDCCH (grey), PDSCH (blue), AP1000 (green), AP1001 (yellow), AP1002 (orange), and AP1003 (purple). + +Figure 4.1.1-3: Scenario 2, number of CDM group without data is 2 and AP1000 and 1001 for target UE, AP1002 and 1003 for interference UE + +![Figure 4.1.1-4: Scenario 3, number of CDM group without data is 1 and AP1000 for target UE, AP1001 for 2 interference UEs with different frequency domain allocation. The figure shows two resource grids. The left grid is for the Target UE, showing PDCCH (grey) and PDSCH (blue) resources, with AP1000 (green) pilot symbols. The right grid is for the Interference UE, showing PDCCH (grey) and PDSCH (blue) resources, with AP1001 (yellow) pilot symbols. A legend at the bottom identifies the colors: PDCCH (grey), PDSCH (blue), AP1000 (green), and AP1001 (yellow).](925f55ce69802b9d3b00546382663ee2_img.jpg) + +Figure 4.1.1-4: Scenario 3, number of CDM group without data is 1 and AP1000 for target UE, AP1001 for 2 interference UEs with different frequency domain allocation. The figure shows two resource grids. The left grid is for the Target UE, showing PDCCH (grey) and PDSCH (blue) resources, with AP1000 (green) pilot symbols. The right grid is for the Interference UE, showing PDCCH (grey) and PDSCH (blue) resources, with AP1001 (yellow) pilot symbols. A legend at the bottom identifies the colors: PDCCH (grey), PDSCH (blue), AP1000 (green), and AP1001 (yellow). + +Figure 4.1.1-4: Scenario 3, number of CDM group without data is 1 and AP1000 for target UE, AP1001 for 2 interference UEs with different frequency domain allocation + +### 4.1.2 Interference model + +The PDSCH of the co-scheduled UE consists of QAM modulated uncoded random bits. The modulation order of PDSCH of paired UEs can be selected independently. The DMRS sequences of paired UEs are assumed to be known for channel estimation purposes for all paired UEs. Note that the DMRS scrambling sequences of paired UEs are assumed to be the same to guarantee orthogonality. + +The PDSCH and DMRS of the paired UEs are precoded prior to transmission. The precoder for each user is denoted by $W'_1$ and $W'_2$ respectively. + +In the scope of this technical report $\mathbf{W}_i$ is the precoder matrix of $i^{\text{th}}$ UE, of size $N_{\text{TX}} \times N_{\text{Li}}$ from Type I single panel codebook as described in [3GPP TS 38.214]. Where, $N_{\text{TX}}$ is the number of TX antenna, $N_{\text{Li}}$ is the number of layers from $i^{\text{th}}$ UE. The combined precoder $\mathbf{W} = [\mathbf{W}_1 \mathbf{W}_2]$ , of size $N_{\text{TX}} \times N_{\text{L}}$ where, $N_{\text{L}}$ is the total number layers across all users. In general, other codebooks are also valid for MU-MIMO scenarios with advanced receiver. + +The precoder of the target UE $\mathbf{W}_1$ is randomly selected. For the co-scheduled UE, the precoder $\mathbf{W}_2$ is selected in one of the two ways below. + +- Orthogonal precoder: $\mathbf{W}_2$ is randomly selected from the codebook with a constraint that the combined precoder $\mathbf{W}$ has orthogonal columns, i.e., the off-diagonal entries of $\mathbf{W}^H \mathbf{W}$ are zero. +- Random precoder: $\mathbf{W}_2$ is randomly selected from the codebook ensuring any column of $\mathbf{W}_2$ is not identical to any column of $\mathbf{W}_1$ + +To maintain the average per UE signal power as $N_{\text{Li}}/N_{\text{L}}$ , an additional scaling is applied to the each precoder as: + +$$\mathbf{W}'_i = \sqrt{\frac{N_{\text{Li}}}{N_{\text{L}}}} * \mathbf{W}_i$$ + +## 4.2 Receiver structure + +### 4.2.1 General + +In this clause, we provide the receiver structure to mitigate the intra-cell inter-user interference. + +The $N_{\text{Rx}}$ -dimensional received signal vector $\mathbf{r}$ of the $k$ -th subcarrier and the $l$ -th OFDM symbol is assumed to be expressed as a sum of target's UE own signal $\mathbf{H}_1(k, l)\mathbf{d}_1(k, l)$ , and co-scheduled UEs' interference signals $\mathbf{H}_j(k, l)\mathbf{d}_j(k, l)$ ( $j > 1$ ) and the white noise $\mathbf{n}(k, l)$ : + +$$\mathbf{r}(k, l) = \mathbf{H}_1(k, l)\mathbf{d}_1(k, l) + \sum_{j=2}^{N_{\text{UE}}} \mathbf{H}_j(k, l)\mathbf{d}_j(k, l) + \mathbf{n}(k, l)$$ + +Where, + +$\mathbf{d}_j(k, l)$ and $\mathbf{H}_j(k, l)$ , $j = \{2, \dots, N_{\text{UE}}\}$ represent the $N_{\text{layer},j} \times 1$ transmitted signal vector and the $(N_{\text{Rx}} \times N_{\text{layer},j})$ channel matrix between the $j$ -th co-scheduled UE's interference and the UE containing the contribution from receiver branches, + +$$\text{with } \mathbf{H}_j = \begin{bmatrix} (\mathbf{H}_{j,1})^H \\ (\mathbf{H}_{j,2})^H \end{bmatrix} \text{ for two receiver antennas and } \mathbf{H}_j = \begin{bmatrix} (\mathbf{H}_{j,1})^H \\ (\mathbf{H}_{j,2})^H \\ (\mathbf{H}_{j,3})^H \\ (\mathbf{H}_{j,4})^H \end{bmatrix} \text{ for four receiver antennas, where, } \mathbf{H}_{j,i} \text{ channel-}$$ + +matrix of size $N_{\text{layer},j} \times 1$ for the $i$ -th receiver antenna, respectively. + +$N_{\text{UE}}$ is the number of paired UEs. + +### 4.2.2 E-MMSE IRC receiver + +To suppress the co-scheduled UE's interference, the candidate E-MMSE IRC receiver type is captured in this subclause. The E-MMSE IRC receiver weight matrix is expressed as follow: + +$$\mathbf{W}_{\text{RX},1}(k, l) = \hat{\mathbf{H}}_1^H(k, l) \mathbf{R}^{-1}$$ + +$$\mathbf{R} = P_1 \hat{\mathbf{H}}_1(k, l) \hat{\mathbf{H}}_1^H(k, l) + P_j \sum_{j=2}^{N_{\text{UE}}} \hat{\mathbf{H}}_j(k, l) \hat{\mathbf{H}}_j^H(k, l) + \frac{1}{N_{\text{re}}} \sum_{k, l \in \text{DMRS of } N_{\text{UE}}} \tilde{\mathbf{r}}(k, l) \tilde{\mathbf{r}}(k, l)^H,$$ + +$$\tilde{\mathbf{r}}(k, l) = \mathbf{r}(k, l) - \sum_{j=1}^{N_{\text{UE}}} \hat{\mathbf{H}}_j(k, l) \mathbf{d}_j(k, l).$$ + +Where, + +$\hat{\mathbf{H}}_j^H(k, l)$ and $\mathbf{d}_j(k, l)$ denote the estimated channel matrix and the transmit signal of all UE's DMRS symbols, respectively, where the estimated channel matrix is also based on DMRS. + +$N_{re}$ is the number of sampling REs of intra-user's DMRS. + +$P_j$ is the power of $j$ -th UE. + +### 4.2.3 R-ML receiver + +ML receiver performs joint maximum likelihood detection of the useful and co-scheduled UE signals considering the constellations of both signals: + +$$\begin{aligned} \mathbf{r}(k, l) &= \mathbf{H}_1(k, l)\mathbf{d}_1(k, l) + \sum_{j=2}^{N_{UE}} \mathbf{H}_j(k, l)\mathbf{d}_j(k, l) + \mathbf{n}(k, l) = \\ &= [\mathbf{H}_1(k, l) \mathbf{H}_2(k, l) \dots \mathbf{H}_{N_{UE}}(k, l)] \begin{bmatrix} \mathbf{d}_1(k, l) \\ \mathbf{d}_2(k, l) \\ \vdots \\ \mathbf{d}_{N_{UE}}(k, l) \end{bmatrix} + \mathbf{n}(k, l) \end{aligned}$$ + +So the ML receiver can be rewritten as + +$$\hat{\mathbf{d}}_{\text{ML}} = \underset{\mathbf{d}_j \in S}{\text{argmin}} \left\| \mathbf{r}(k, l) - \sum_{j=1}^{N_{UE}} \mathbf{H}_j(k, l)\mathbf{d}_j(k, l) \right\|^2$$ + +Where, + +$\|\cdot\|$ denotes the $l_2$ -norm of a vector. + +$\mathbf{r}(k, l)$ is the received signal vector. + +$\mathbf{H}_j(k, l)$ is the channel matrix over target and interference layers for a RE at frequency location $k$ and symbol $l$ . + +$S$ is the set of all possible transmitted signal vectors across target and interference spatial layers. + +Reduced complexity ML (R-ML): + +Reduced complexity joint detection of useful and interference modulation symbols in accordance to the ML criterion (e.g. sphere decoding, QR-MLD, MLM, etc.). + +## 4.3 Analysis on the required information + +The agreed list of required information for advanced receiver is captured below: + +| Information | RAN4 Default assumption
(If N/A, how could be obtained by the UE) | Signalling if RAN4 default assumption not valid | +|----------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------| +| The DMRS port information for the co-scheduled UE | N/A (Obtained by UE blind detection) | N/A | +| PRB bundling size for the co-scheduled UE
Frequency domain resource allocation for the co-UE within each PRG of the target UE | For the target and any co-scheduled UEs in different CDM groups and with the same DMRS sequence, the target UE assumes the precoding and resource allocation of the co-scheduled UE are the same in the PRG-level grid configured to the target UE when PRG=2 or 4. | Introduce dedicated RRC signalling to indicate whether the default assumptions valid or not | +| DMRS power boosting for the co-scheduled UE | Same as target UE | Introduce dedicated RRC signalling to indicate whether the default assumptions valid or not | +| Time domain resource allocation information of the co-scheduled UE | Same as target UE | Introduce dedicated RRC signalling to indicate whether the default assumptions valid or not | +| Frequency domain resource allocation for the co-UE across different PRGs of the target UE: | N/A (Obtained by UE blind detection) | N/A | +| CSI-RS location of co-scheduled UE (Only required for R-ML) | UE assumes the target PDSCH is not overlapped with the CSI-RS of the co-scheduled UE | No RRC signalling is needed | +| Modulation order of co-scheduled UE | N/A
Obtained by DCI based network assistance information or UE blind detection | | + +DCI based network assistance information for the co-scheduled UE existence and modulation order related information signalling is captured in the table below: + +| Bit field mapped to index | Content | +|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | No co-scheduled UE(s) which has same DMRS sequence as target UE exists | +| 1 | In all the PRBs allocated to the target UE, all the co-scheduled UE(s), which has the same DMRS sequence as the target UE, have QPSK scheduled | +| 2 | In all the PRBs allocated to the target UE, all the co-scheduled UE(s), which has the same DMRS sequence as the target UE, have 16QAM scheduled | +| 3 | In all the PRBs allocated to the target UE, all the co-scheduled UE(s), which has the same DMRS sequence as the target UE, have 64QAM scheduled | +| 4 | In all the PRBs allocated to the target UE, all the co-scheduled UE(s), which has the same DMRS sequence as the target UE, have 256QAM scheduled | +| 5 | In all the PRBs allocated to the target UE, all the co-scheduled UE(s), which has the same DMRS sequence as the target UE, have 1024QAM scheduled | +| 6 | Not covered by cases corresponding to index 0~5.
In each individual PRB allocated to the target UE, the following condition is satisfied:
Only single modulation order is allocated for the co-scheduled UE(s) which has the same DMRS sequence as the target UE, if the co-scheduled UE(s) exist | +| 7 | Others | + +## 4.4 Link performance characterization + +### 4.4.1 Parameters for link level evaluation + +General link level simulation parameters are captured in Table 4.4-1: + +Table 4.4-1: General parameters + +| Parameter | | Unit | Value | | +|----------------------------------------------|---------------------------------------------------------|---------|----------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | Target UE | Co-scheduled UE | +| Channel Bandwidth/SCS | | MHz/KHz | 10/15 | | +| Duplex mode | | | FDD | | +| Allocation for interference UE and target UE | Rank allocation | | 1 | 1 | +| | Scrambling ID | | Same scrambling ID for both UEs | | +| MIMO configuration | | | Rank 1+1: 2T2R Medium
Rank 2+2: 4T4R Low | | +| Port allocation | | | Rank 1+1: 1000
Rank 2+2: 1000,1001 | Rank 1+1: 1001
Rank 2+2: 1002,1003 | +| Number of CDM groups without data | | | 1 for paired UE allocated in same CDM groups and 2 for paired UE allocated in different CDM groups | | +| HARQ process number | | | 4 | | +| Maximum number of HARQ transmission | | | 4 | | +| Precoding model | Target UE | | Random precoding with Single panel Type 1 per PRB bundling size per slot | Rank 2+2: Select the precoding matrix to ensure orthogonality with target UE
Rank 1+1: Select the precoding matrix randomly ensuring the selected precoding matrix shall not be identical to the precoding matrix of target UE | +| PDSCH configuration | Mapping type | | Type A | | +| | Starting symbol (S) | | 2 | | +| | Length (L) | | 12 | | +| | PRB bundling size | | 2 | | +| | PRB bundling type | | Static | | +| | Frequency domain allocation | | Full bandwidth allocation | Partial bandwidth allocation
Full bandwidth allocation | +| PDSCH DMRS configuration | DMRS Type | | DMRS Type 1 | | +| | Number of additional DMRS | | 1 | | +| | Maximum number of OFDM symbols for DL front loaded DMRS | | 1 | | +| Propagation conditions | | | Rank 1+1: TDLC300-100
Rank 2+2: TDLA30-10 | | +| Test metric | | | SNR @ %70 of maximum Throughput | N/A | + +Detailed link level simulation parameters are captured in Table 4.4-2: + +Table 4.4-2: Simulation parameters + +| Case | Target UE | | Co-scheduled UE(s) | | | Receiver assumption | | +|------|-----------|-----|--------------------|---------------------------------------------------|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | Rank | MCS | Rank | Modulation order | RB allocation | | | +| 1 | 1 | 4 | 1 | QPSK | Full allocation(52PRBs) | MMSE-IRC, E-MMSE-IRC,R-ML receiver with genie aided knowledge of all the required information of scheduled UE | | +| 2 | | 13 | | QPSK | | | | +| 3 | 2 | 13 | 2 | QPSK | | | | +| 4 | | | | 16QAM | | | | +| 5 | | | | 64QAM | | | | +| 6 | | 17 | | QPSK | | | | +| 7 | | | | 16QAM | | | | +| 8 | | | | 64QAM | | | | +| 9 | 1 | 13 | 1 | QPSK | Full allocation(52PRBs) | E-MMSE-IRC,R-ML receiver with genie aided knowledge of all the required information of scheduled UE except for DMRS port and frequency domain allocation which are blindly detected by target UE | | +| 10 | | | | | Partial allocation(0~25PRBs) | | | +| 11 | 2 | 13 | 2 | 64QAM | Full allocation(52PRBs) | | | +| 12 | | | | | Partial allocation(0~25PRBs) | | | +| 13 | 1 | 13 | 1 | QPSK | Full allocation(52PRBs) | E-MMSE-IRC,R-ML receiver with genie aided knowledge of all the required information of scheduled UE except for DMRS port, frequency domain allocation and modulation order which are blindly detected by target UE | | +| 14 | 2 | 17 | 2 | 16QAM | Full allocation(52PRBs) | | | +| 15 | 1 | 13 | 1 | 16QAM | Full allocation(52PRBs) | E-MMSE-IRC,R-ML receiver with genie aided knowledge of all the required information of scheduled UE except for DMRS port, frequency domain allocation and modulation order which are blindly detected by target UE | | +| 16 | 1 | 13 | 1 | Co-scheduled UE1: QPSK
Co-scheduled UE2: 16QAM | Co-scheduled UE1: PRB index 0~25
Co-scheduled UE2: PRB index 26~51 | E-MMSE-IRC,R-ML receiver with genie aided knowledge of all the required information of scheduled UE except for DMRS port, frequency domain allocation and modulation order which are blindly detected by target UE | | + +Note 1: Case 1 to 15 are corresponding to 1 co-scheduled UE. Case 16 is corresponding to 2 co-scheduled UEs + +### 4.4.2 Link level simulation results + +In this sub-clause, link level simulation results from different companies are collected for analysis of PDSCH performance in scenario with inter-user interference for MU-MIMO. The link level analysis of PDSCH performance is performed under assumptions from sub-clause 4.4.1. + +The detailed simulation results from different companies are provided in the attached file 'Attachment 1 - R4-2301098 Simulation result collection for advanced receiver for MU-MIMO' Table 4.4.2-1 provides the summary of simulation results from different companies. + +Table 4.4.2-1: Summary of simulation + +| Case Number (Note 1) | Co-scheduled UE number | Rank for the target UE | Rank for the Co-scheduled UE | MCS for the target UE (MCS Table 1) | Modulation order for the co-scheduled UE | MIMO | Channel model | Precoder selection for the Co-scheduled UE | FDRA of the Co-UE | SPAN | | | Average | | | +|----------------------|------------------------|------------------------|------------------------------|-------------------------------------|------------------------------------------|--------------------|---------------|--------------------------------------------|-------------------------------------|------|-------|----------------|--------------|---------------|--| +| | | | | | | | | | | R-ML | E-IRC | IRC (baseline) | Gain of R-ML | Gain of E-IRC | | +| 1 | 1 | 1 | 1 | 4 | QPSK | 2Tx 2Rx ULA medium | TDLC300-100 | random | Full CHBW allocation (52PRBs) | 3.9 | 4.2 | 7.5 | 1.6 | 0.7 | | +| 2 | | | | 13 | | | | | | 6.2 | 4.6 | 7.3 | 7.8 | 1.8 | | +| 3 | | 2 | 2 | | 64QAM | 4Tx 4Rx ULA Low | TDLA30-10 | orthogonal | | 3.7 | 1.9 | 3.8 | 0.7 | 0.3 | | +| 4 | | | | | 16QAM | | | | | 3.4 | 2.4 | 4.1 | 1.2 | 0.4 | | +| 5 | | | | | QPSK | | | | | 2.5 | 2.3 | 3.8 | 2.4 | 0.5 | | +| 6 | | | | | 64QAM | | | | | 3.1 | 2.1 | 4.1 | 0.4 | 0.4 | | +| 7 | | | | | 16QAM | | | | | 3.5 | 2.1 | 4.0 | 1.1 | 0.4 | | +| 8 | | | | | QPSK | | | | | 3.2 | 2.1 | 4.0 | 2.8 | 0.4 | | +| 9 | | 1 | 1 | 13 | QPSK | 2Tx 2Rx ULA medium | TDLC300-100 | random | Full CHBW allocation (52PRBs) | 5.4 | 1.9 | 0.1 | 9.3 | 4.1 | | +| 10 | | | | | | | | | Partial CHBW allocation (0~25 PRBs) | 1.2 | 3.1 | 4.0 | 3.8 | 2.5 | | + +| | | | | | | | | | | | | | | | +|-----------------------------------------------------------|---|---|------------------|----|----------------------------|--------------------|-------------|------------|-----------------------------------------|-----|-----|-----|-----|-----| +| 11 | | 2 | 2 | | 64QAM | 4Tx 4Rx ULA Low | TDLA30-10 | orthogonal | Full CHBW allocation (52PRBs) | 1.1 | 0.4 | 0.7 | 1.4 | 0.9 | +| 12 | | | | | | | | | Partial CHBW allocation (0~25 PRBs) | 2.3 | 1.9 | 1.9 | 1.0 | 0.7 | +| 13 | | 1 | 1 | 13 | QPSK | 2Tx 2Rx ULA medium | TDLC300-100 | random | Full CHBW allocation (52PRBs) | 6.9 | 2.7 | 3.7 | 7.8 | 3.0 | +| 14 | | 2 | 2 | 17 | 16QAM | 4Tx 4Rx ULA Low | TDLA30-10 | orthogonal | | 1.2 | 0.9 | 1.6 | 1.0 | 0.4 | +| 15 (Optional) | | 1 | 1 | 13 | 16QAM | 2Tx 2Rx ULA medium | TDLC300-100 | random | | 3.7 | 0.0 | 0.0 | 4.4 | 3.3 | +| 16 (Companies are encouraged to bring simulation results) | 2 | 1 | 1 for each Co-UE | 13 | Co-UE1: QPSK Co-UE2: 16QAM | 2Tx 2Rx ULA medium | TDLC300-100 | random | Co-UE1: 0~25 PRBs
Co-UE2: 26~51 PRBs | 8.0 | 4.7 | 2.8 | 7.5 | 4.7 | + +### 4.4.3 Summary of link level evaluation + +The link level evaluation target was to compare differing receiver structures in combination with differing sources of interference parameters. + +This section will summarize the observations for the decided phase I test configurations, for the combinations contributed. + +All PDSCH link level evaluations in clause 4.4.2, have been carried out using a FDD 10MHz/15kHz scenario. + +Summary for advanced receiver with genie aided knowledge of all the required information (simulation test cases 1-8): + +- 1 co-scheduled scheduled UE, + - Environment with low ranks, medium correlation, multipath dominated channel, random precoding, and low to mid MCS, i.e., coverage challenged environment + - target UE rank 1, co-scheduled UE rank 1 + - 2Tx 2Rx ULA medium, TDL300-100, precoder selection for the Co-scheduled UE is random, FDRA of co-UE is full chBW. + - Observations (cases 1-2) + - 8 companies provided input with target UE MCS 13 and co-UE QPSK. + - The gain of R-ML over IRC baseline was observed to be between 5.2 dB and -0.1 dB, with average of 1.6 dB. + - The gain of E-IRC over IRC baseline was observed to be between 3.1 dB and -0.6 dB, with average of 0.7 dB. + - 10 companies provided input with target UE MCS 4 and co-UE QPSK. + - (9 companies) The gain of R-ML over IRC baseline was observed to be between 11.5 dB and 1.2 dB, with average of 7.8 dB. + - (8 companies) The gain of E-IRC over IRC baseline was observed to be between 4.8 dB and 0 dB, with average of 1.8 dB. + - Hence, for coverage challenged conditions with low or mid MCS for both target and co-UE served, using random precoding and with genie aided knowledge, R-ML outperforms E-IRC by up to 6.0 dB. + - Environment with higher ranks, low correlation, low delay spread channel, orthogonal precoding, and mid to high MCS, i.e., higher throughput environment + - target UE rank 2, co-scheduled UE rank 2 + - 4Tx 4Rx ULA low, TDL30-10, precoder selection for the Co-scheduled UE is orthogonal, FDRA of co-UE is full chBW. + - Observations (cases 3-8) + - 10 companies provided input with target UE MCS13 and co-UE 64QAM. + - (9 companies) The gain of R-ML over IRC baseline was observed to be between 1.8 dB and 0.1 dB, with average of 0.7 dB. + - (8 companies) The gain of E-IRC over IRC baseline was observed to be between 1.0 dB and 0.0 dB, with average of 0.3 dB. + - 8 companies provided input with target UE MCS 13 and co-UE 16QAM. + - The gain of R-ML over IRC baseline was observed to be between 2.9 dB and 0.3 dB, with average of 1.2 dB. + +- The gain of E-IRC over IRC baseline was observed to be between 1.1 dB and 0 dB, with average of 0.4 dB. +- 10 companies provided input with target UE MCS 13 and co-UE QPSK. + - (9 companies) The gain of R-ML over IRC baseline was observed to be between 4.2 dB and 0.3 dB, with average of 2.4 dB. + - (8 companies) The gain of E-IRC over IRC baseline was observed to be between 1.2 dB and -0.1 dB, with average of 0.5 dB. +- 8 companies provided input with target UE MCS 17 and co-UE 64QAM. + - (7 companies) The gain of R-ML over IRC baseline was observed to be between 1.0 dB and -0.4 dB, with average of 0.4 dB. + - (7 companies) The gain of E-IRC over IRC baseline was observed to be between 0.8 dB and 0.0 dB, with average of 0.4 dB. +- 9 companies provided input with target UE MCS 17 and co-UE 16QAM. + - (8 companies) The gain of R-ML over IRC baseline was observed to be between 2.7 dB and 0.1 dB, with average of 1.1 dB. + - (7 companies) The gain of E-IRC over IRC baseline was observed to be between 0.9 dB and 0.0 dB, with average of 0.4 dB. +- 9 companies provided input with target UE MCS 17 and co-UE QPSK. + - (8 companies) The gain of R-ML over IRC baseline was observed to be between 5.4 dB and 0.5 dB, with average of 2.8 dB. + - (7 companies) The gain of E-IRC over IRC baseline was observed to be between 0.8 dB and 0.0 dB, with average of 0.4 dB. +- Hence, high throughput challenged conditions with mid or high MCS for target UE and low, mid or high MCS for co-UE served, using orthogonal precoding and with genie aided knowledge, R-ML outperforms E-IRC by up to 2.4 dB. + +Summary for advanced receiver with blind detection of FDRA and DMRS ports (simulation test cases 9-12): + +- 1 co-scheduled scheduled UE, target UE needs to blind detect the FDRA and DMRS port allocation information of the co-scheduled UE +- Environment with low ranks, medium correlation, multipath dominated channel, random precoding, and low to mid MCS, i.e., coverage challenged environment + - target UE rank 1, co-scheduled UE rank 1 + - 2Tx 2Rx ULA medium, TDLC300-100, precoder selection for the Co-scheduled UE is random, FDRA of co-UE is either full or partial chBW. + - Observations cases 9-10 + - 3 companies provided input with target UE MCS 13 and co-UE QPSK with full CHBW allocation. + - (2 companies) The gain of R-ML over IRC baseline was observed to be between 11.5 dB and 7.0 dB, with average of 9.3 dB. + - (2 companies) The gain of E-IRC over IRC baseline was observed to be between 5.0 dB and 3.2 dB, with average of 4.1 dB. + - 2 companies provided input with target UE MCS 13 and co-UE QPSK with partial CHBW allocation. + - The gain of R-ML over IRC baseline was observed to be between 5.2 dB and 2.4 dB, with average of 3.8 dB. + +- The gain of E-IRC over IRC baseline was observed to be between 2.9 dB and 2.0 dB, with average of 2.5 dB. +- Hence, for coverage challenged conditions with mid MCS for target UE and low or mid MCS for co-UE served, full/partial CHBW allocation for co-UE, using random precoding and with blind detection of FDRA and DMRS ports, R-ML outperforms E-IRC by up to 5.2 dB. +- Environment with higher ranks, low correlation, low delay spread channel, orthogonal precoding, and mid to high MCS, i.e., higher throughput environment + - target UE rank 2, co-scheduled UE rank 2 + - 4Tx 4Rx ULA low, TDLA30-10, precoder selection for the Co-scheduled UE is orthogonal, FDRA of co-UE is either full or partial chBW. + - Observations cases 11-12 + - 3 companies provided input with target UE MCS 13 and co-UE 64QAM with full CHBW allocation. + - (2 companies) The gain of R-ML over IRC baseline was observed to be between 1.7 dB and 1.1 dB, with average of 1.4 dB. + - (2 companies) The gain of E-IRC over IRC baseline was observed to be between 1.0 dB and 0.7 dB, with average of 0.9 dB. + - 2 companies provided input with target UE MCS 13 and co-UE 64QAM with partial CHBW allocation. + - The gain of R-ML over IRC baseline was observed to be between 1.2 dB and 0.8 dB, with average of 1.0 dB. + - The gain of E-IRC over IRC baseline was observed to be between 0.7 dB and 0.7 dB, with average of 0.7 dB. + - Hence, high throughput challenged conditions with MCS13 for target UE and mid MCS for co-UE served, full/partial CHBW allocation for co-UE, using orthogonal precoding and with blind detection of FDRA and DMRS ports, R-ML outperforms E-IRC by up to 0.6 dB. + +Summary for advanced receiver with blind detection of FDRA and DMRS ports and blind detection of co-UE modulation order (simulation test cases 13-16): + +- 1 co-scheduled scheduled UE, target UE needs to blind detect the FDRA, DMRS port allocation information and modulation order of the co-scheduled UE +- Environment with low ranks, medium correlation, multipath dominated channel, random precoding, and low to mid MCS, i.e., coverage challenged environment + - target UE rank 1, co-scheduled UE rank 1 + - 2Tx 2Rx ULA medium, TDLC300-100, precoder selection for the Co-scheduled UE is random, FDRA of co-UE is full chBW. + - Observations cases 13 and 15 + - 5 companies provided input with target UE MCS 13 and co-UE QPSK + - (4 companies) The gain of R-ML over IRC baseline was observed to be between 9.7 dB and 6.0 dB, with average of 7.8 dB. + - (4 companies) The gain of E-IRC over IRC baseline was observed to be between 5.0 dB and 1.1 dB, with average of 3.0 dB. + - 2 companies provided input with target UE MCS 13 and co-UE 16QAM + - (1 company) The gain of R-ML over IRC baseline was observed to be 4.4 dB. + - The gain of E-IRC over IRC baseline was observed to be 3.3 dB. + +- Hence, for coverage challenged conditions with mid MCS for target UE and low or mid MCS for co-UE served, full CHBW allocation for co-UE, using random precoding and with blind detection of FDRA, DMRS ports and modulation order, R-ML outperforms E-IRC by up to 4.9 dB. +- Environment with higher ranks, low correlation, low delay spread channel, orthogonal precoding, and mid to high MCS, i.e., higher throughput environment + - target UE rank 2, co-scheduled UE rank 2 + - 4Tx 4Rx ULA low, TDLA30-10, precoder selection for the Co-scheduled UE is orthogonal, FDRA of co-UE is full chBW. + - Observations cases 14 + - 4 companies provided input with target UE MCS 17 and co-UE 16QAM + - (3 companies) The gain of R-ML over IRC baseline was observed to be between 1.8 dB and 0.5 dB, with average of 1.0 dB. + - (3 companies) The gain of E-IRC over IRC baseline was observed to be between 0.8 dB and 0.1 dB, with average of 0.4 dB. + - Hence, high throughput challenged conditions with MCS17 for target UE and mid MCS for co-UE served, full CHBW allocation for co-UE, using orthogonal precoding and with blind detection of FDRA, DMRS ports and modulation order, R-ML outperforms E-IRC by up to 0.6 dB. +- 2 co-scheduled UEs, target UE needs to blind detect the FDRA, DMRS port allocation information and modulation order of the co-scheduled UEs, each co-UE occupies half of the available PRBs +- Environment with low ranks, medium correlation, multipath dominated channel, random precoding, and low to mid MCS, i.e., coverage challenged environment + - target UE rank 1, co-scheduled UE rank 1 + - 2Tx 2Rx ULA medium, TDLC300-100, precoder selection for the Co-scheduled UEs is random, FDRA of each co-UE is partial chBW. + - Observations case 16 + - 3 companies provided input with target UE MCS 13, 1st co-UE QPSK and 2nd co-UE 16QAM + - The gain of R-ML over IRC baseline was observed to be between 11.2 dB and 5.1 dB, with average of 7.5 dB. + - The gain of E-IRC over IRC baseline was observed to be between 5.8 dB and 2.7 dB, with average of 4.7 dB. + - Hence, for coverage challenged conditions with MCS13 for target UE and low and mid MCS respectively for the two co-UEs served, partial CHBW allocation for each co-UE equally distributed, using random precoding and with blind detection of FDRA, DMRS ports and modulation order, R-ML outperforms E-IRC by up to 2.8 dB. + +# --- 5 Conclusions + +This technical report has documented the RAN4 evaluation on techniques to cancel downlink intra cell inter-user interference. The major work includes the determination of network scenario, interference modelling, interference suppressing receiver structure, required information analysis for each candidate receiver, link-level simulation parameters and performance evaluations. + +MU-MIMO scenario with gNB transmits PDSCH to the paired UEs through the same time-frequency resources is evaluated. + +gNBs equipped with 2Tx and 4Tx antennas are considered in the RAN4 performance evaluation. However, for the UEs capable of inter-user interference suppression ability discussed in this TR, they can also be used in the deployments + +with larger number of Tx ports configuration. For the interference suppressing receiver, both E-MMSE-IRC and R-ML are evaluated as candidate advanced receivers. + +RAN4 reaches consensus on the required information for both E-IRC and R-ML receiver. In addition, RAN4 has agreed the network default configuration assumptions. Therefore, the advanced receiving algorithm can be performed under these default assumptions. For some of the default assumptions, it is required for the network to indicate the UE whether the default assumption is valid or not by RRC signalling. For UE with R-ML receiver, DCI based network assistant signalling is required. + +PDSCH link-level simulations are performed to evaluate the performance gain of the candidate E-IRC and R-ML receiver over the baseline MMSE-IRC receiver under intra-cell inter-user interference scenario. 16 simulation cases that covers the advanced receiver with genie-aided required information, with co-scheduled UE DMRS port and FDRA information blind detection, and with co-scheduled UE modulation order blind detection (for R-ML receiver only), are selected for the evaluation. Different antenna and rank configurations for target and interference UEs, different propagation condition, and CBW configurations are included. + +Based on the simulation results, the performance gain of R-ML receiver over the baseline MMSE-IRC receiver is verified. + +Based on the above evaluations, it is recommended to select R-ML as the new advanced receiver for inter-user interference suppression receiver for MU-MIMO scenario in Rel-18, and to introduce necessary new UE capability and network assistant signalling for the selected receiver. + +It is also recommended to define NR PDSCH demodulation requirements for the selected inter-user interference suppression receiver for MU-MIMO scenario in Rel-18. + +# Annex A: Change history + +| Change history | | | | | | | | +|----------------|-----------|------------|----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2023-03 | RAN4 #106 | R4-2300127 | | | TR skeleton | | 0.0.1 | +| 2023-08 | RAN4#108 | R4-2311100 | | | Implemented the following TPs endorsed at RAN4#108:
R4-2313969, TP to TR38.878: on the phase I conclusion for advanced receiver for MU-MIMO, China Telecom
R4-2313970, TP to TR38.878: Symbols and abbreviations, China Telecom
R4-2313994, TP for TR 38.878 Receiver structure of MU-MIMO, ZTE Corporation
R4-2313972, TP for TR38.878: Summary of link level evaluation, Nokia, Nokia Shanghai Bell
R4-2313973, MU-MIMO TR TP, Qualcomm
R4-2313974, TP to TR38.878 on Scenario and interference modelling, MediaTek inc
R4-2313975, TP to TR38.878: Link level simulation results, Ericsson
R4-2313976, Draft TP on TR 38.878 Introduction on parameters for link level evaluation, Huawei, HiSilicon | 0.0.1 | 0.1.0 | +| 2023-09 | RAN #101 | RP-232282 | | | Presented at RAN#95e for approval. | 0.1.0 | 1.0.0 | + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|-----------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2023-09 | RAN #101 | | | | | Put under change control | 18.0.0 | +| 2023-12 | RAN#102 | RP-233364 | 0001 | | F | CR for TR38.878 on Summary of link level evaluation | 18.1.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38879/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/Rel-18/38_series/38879/053f1077d592e6622cd21dc4bb4cb366_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50d353cbbd957afc9ffc9d4c9f2ca0b30baa90e1 --- /dev/null +++ b/marked/Rel-18/38_series/38879/053f1077d592e6622cd21dc4bb4cb366_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e697d1de97a5c92abbfbc41bfbf81ff5e6c837a2b521e8803218a6009826307 +size 42451 diff --git a/marked/Rel-18/38_series/38879/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/Rel-18/38_series/38879/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..042781654bb0228ac880a10936218bc190929046 --- /dev/null +++ b/marked/Rel-18/38_series/38879/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b724e62384275d88d8e95c49c60ab0cd39839a218d77ab61cf28992678185b0 +size 29580 diff --git a/marked/Rel-18/38_series/38879/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg b/marked/Rel-18/38_series/38879/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..912d5157618f7abaa46e5cd20937ee551c02b03f --- /dev/null +++ b/marked/Rel-18/38_series/38879/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97762593f7b2fb27a1ce5cd9490fca13b12910521ec20bd62455f113e6c40e5c +size 41760 diff --git a/marked/Rel-18/38_series/38879/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38879/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14d89b502abf6326a06b6408d90300b88521c106 --- /dev/null +++ b/marked/Rel-18/38_series/38879/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:555e6a5fb72e22eb97df1047a8515820f360c03801b44b5d4b394a4faa2ed036 +size 9351 diff --git a/marked/Rel-18/38_series/38879/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38879/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8e9f6f07870f1b8e769b9cd76350ccd4f0de03e --- /dev/null +++ b/marked/Rel-18/38_series/38879/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d6b94f22bbb239b0eb4fba0375e8e8f14aaf1abd8de2467c22fb4df926f7772 +size 5715 diff --git a/marked/Rel-18/38_series/38879/88b0f3f4393228e9ea4d6542aef7c399_img.jpg b/marked/Rel-18/38_series/38879/88b0f3f4393228e9ea4d6542aef7c399_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..632535de6253d33eece3a5fc2dcb629514b742d5 --- /dev/null +++ b/marked/Rel-18/38_series/38879/88b0f3f4393228e9ea4d6542aef7c399_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e23ff30478bd0d14b486be4f01f28784926e9e35032eb2c3627316ce4e6fcb4 +size 30064 diff --git a/marked/Rel-18/38_series/38879/a92b1fdf37a74b707e9f03087c8f1377_img.jpg b/marked/Rel-18/38_series/38879/a92b1fdf37a74b707e9f03087c8f1377_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57f6bd3cbbca9766082b333bf36c7ca43773dce5 --- /dev/null +++ b/marked/Rel-18/38_series/38879/a92b1fdf37a74b707e9f03087c8f1377_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52e01769bd813ee563721b4dd39dffddaae50179c0341fde15ba14d8fdbcaf73 +size 43221 diff --git a/marked/Rel-18/38_series/38879/b10763be31553f31cbb795653b731a43_img.jpg b/marked/Rel-18/38_series/38879/b10763be31553f31cbb795653b731a43_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1282fba94a644006d560917e07f0f5653b01acf7 --- /dev/null +++ b/marked/Rel-18/38_series/38879/b10763be31553f31cbb795653b731a43_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:085c1c82bb2a6892ed5559bd1cf90a69cedd8537fa35455ed2a0df5b9f2add0b +size 42169 diff --git a/marked/Rel-18/38_series/38879/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/Rel-18/38_series/38879/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22907a7ebb4fd3c9e9301799b6530f69bf9aa3cd --- /dev/null +++ b/marked/Rel-18/38_series/38879/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4873cba5c942b221fbcd5260d2e9eb3330a69cd38bffa4f4ea70402065f5da19 +size 24827 diff --git a/marked/Rel-18/38_series/38879/raw.md b/marked/Rel-18/38_series/38879/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..589ddf5560126b88bcf1e76d1498eb4279bb801a --- /dev/null +++ b/marked/Rel-18/38_series/38879/raw.md @@ -0,0 +1,452 @@ + + +# 3GPP TR 38.879 V18.0.0 (2022-09) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Study on enhancement for Resiliency of gNB-CU-CP (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. + +© 2022, 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 of terms, symbols and abbreviations..... | 5 | +| 3.1 Terms..... | 5 | +| 3.2 Symbols..... | 5 | +| 3.3 Abbreviations ..... | 5 | +| 4 General..... | 5 | +| 5 Study failure scenarios associated with the gNB-CU-CP..... | 7 | +| 6 Conclusion ..... | 7 | +| Annex (informative): Failure Scenario from each contribution's view ..... | 8 | +| A.1 Scenario and issue description (R3-224787)..... | 8 | +| A.1.1 CU SW failure ..... | 8 | +| A.1.2 gNB-CU-CP HW failure ..... | 8 | +| A.1.3 Power outages..... | 8 | +| A.1.4 Transport network failure (out of 3GPP scope)..... | 8 | +| A.1.5 Summary of failure scenarios ..... | 9 | +| A.2 Scenario (R3-224281) ..... | 9 | +| A.2.1 Scenarios A, B, C ..... | 9 | +| A.2.2 Scenario D ..... | 10 | +| A.2.3 Scenario E..... | 10 | +| A.3 Scenario and issue description (R3-224303)..... | 11 | +| A.4 Scenario and issue description (R3-224324)..... | 11 | +| A.5 Failure Case (R3-224576) ..... | 12 | +| A.6 Scenario and issue description (R3-224627)..... | 12 | +| A.6.1 Scenario #1: Geographical Redundancy..... | 12 | +| A.6.1.1 General description ..... | 12 | +| A.7 Scenario and issue description (R3-224754)..... | 13 | +| A.7.1 Local Redundancy ..... | 13 | +| A.7.2 Failure Scenarios ..... | 13 | +| A.7.2.1 Server Failure..... | 13 | +| A.7.2.2 VNFC (Virtual Network Function Component) Failure..... | 13 | +| A.7.2.3 Transport Link Failure (out of 3GPP scope) ..... | 13 | +| A.7.3 Failure Impact..... | 13 | +| A.8 Scenario and issue description (R3-224898)..... | 14 | +| A.8.1 Possible failure scenarios ..... | 14 | +| Annex (informative): Change history ..... | 14 | + +# --- 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 provides descriptions of failure scenarios associated with the gNB-CU-CP based on current architecture for the 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 23.501: "System architecture for the 5G System (5GS)". +- [4] RP-221438: "Revised SID: Study on enhancement for resiliency on gNB-CU-CP" + +# --- 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: + + + +## 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]. + + + +# --- 4 General + +The 3GPP split architecture for NG-RAN is described in TS 38.401 [2]. The NR gNB disaggregated architecture is characterized by the presence of a single gNB-CU-CP, which is in control of one or more gNB-DU(s) and one or more gNB-CU-UP(s) (Figure 4-1). Similarly, a gNB-DU may interact with multiple gNB-CU-UPs simultaneously for the same user context as long as they are controlled by the same gNB-CU-CP. + +![Figure 4-1: Overall architecture for separation of gNB-CU-CP and gNB-CU-UP. The diagram shows a gNB-CU-CP connected to multiple gNB-CU-UP units via E1 interfaces. Each gNB-CU-UP is connected to two gNB-DUs via F1-C and F1-U interfaces. The gNB-CU-CP is also connected to the gNB-DUs via F1-C interfaces. The entire gNB unit is enclosed in a dashed box labeled 'gNB'.](88b0f3f4393228e9ea4d6542aef7c399_img.jpg) + +Figure 4-1: Overall architecture for separation of gNB-CU-CP and gNB-CU-UP. The diagram shows a gNB-CU-CP connected to multiple gNB-CU-UP units via E1 interfaces. Each gNB-CU-UP is connected to two gNB-DUs via F1-C and F1-U interfaces. The gNB-CU-CP is also connected to the gNB-DUs via F1-C interfaces. The entire gNB unit is enclosed in a dashed box labeled 'gNB'. + +**Figure 4-1: Overall architecture for separation of gNB-CU-CP and gNB-CU-UP TS 38.401 [2]** + +The gNB-CU-CP may have specific configured data for each supported cell in the gNB, and a common gNB ID per PLMN. This identity is known in the gNB-DU and in neighbor gNBs, and it is also broadcasted in the served NR cells as part of the cell identity. + +![Figure 4-2: CP connections involving the AMF, gNB-CU-CP, gNB-CU-UP, and gNB-DUs. The diagram shows an AMF connected to gNB1 CU-CP via NG-C interfaces, labeled 'Multiple SCTP connections (UE-associated)' and 'Primary SCTP connection (non-UE associated)'. gNB1 CU-CP is connected to gNB2 CU-CP via Xn-C and SCTP. gNB1 CU-CP is connected to gNB1 CU-UP via E1 and SCTP. gNB1 CU-CP is connected to three gNB1 DUs via F1-C and SCTP.](1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg) + +Figure 4-2: CP connections involving the AMF, gNB-CU-CP, gNB-CU-UP, and gNB-DUs. The diagram shows an AMF connected to gNB1 CU-CP via NG-C interfaces, labeled 'Multiple SCTP connections (UE-associated)' and 'Primary SCTP connection (non-UE associated)'. gNB1 CU-CP is connected to gNB2 CU-CP via Xn-C and SCTP. gNB1 CU-CP is connected to gNB1 CU-UP via E1 and SCTP. gNB1 CU-CP is connected to three gNB1 DUs via F1-C and SCTP. + +**Figure 4-2: CP connections involving the AMF, gNB-CU-CP, gNB-CU-UP, and gNB-DUs.** + +There is one (active) CP anchor node per UE in the 5GC (AMF) and one (active) CP anchor per gNB in the NG-RAN (gNB-CU-CP). Figure 4-2 highlights the various CP connections going through the same gNB-CU-CP towards the AMF, to neighbor gNB-CU-CPs, to gNB-CU-UPs, and to gNB-DUs. All CP connections terminate in the gNB-CU-CP; if we only look at the logical architecture, the gNB-CU-CP may indeed be considered as a single point of failure. + +For Operator, resiliency of public network is under national regulations or other operational constraints. + +With regard to resiliency TS 38.401[2] includes only the following note: + +NOTE: For resiliency, a gNB-DU may be connected to multiple gNB-CUs by appropriate implementation. + +Furthermore, multiple TNL associations toward the gNB-CU-CP are currently supported by the standard. + +In the event of a failure at gNB-CU-CP, the likely outcome is that all user contexts could be affected and experience user service interruption. + +This study handles failure scenarios for gNB-CU-CP, based on the current NG-RAN architecture. + +Solutions for failure scenarios will not be addressed in this study. + +The nodes shown in Figure 4-1 are logical nodes, i.e., they can be implemented as physical network functions (PNFs) using dedicated hardware (HW) infrastructures or as virtual network functions (VNFs) running as software (SW) functions (e.g., virtual machines (VMs) or cloud-native containers (CNFs)) on general purpose processors (GPPs; with or without HW acceleration support), e.g., in a cloud environment of a data center. + +# --- 5 Study failure scenarios associated with the gNB-CU-CP + +Various perspectives were considered by each company (see the informative Annex A for details). + +A failure scenario for a deployment case with gNB-CU-CP at the antenna site (Distributed RAN/D-RAN) should not be of relevance for this study as an outage would impact the network performance only in a limited local area (similar to an outage of the co-located gNB-DU). Local resiliency measures may therefore be realized in the same way for both logical nodes (dependent on PNF/VNF implementation). + +A more important scenario is the case when a gNB-CU-CP is deployed in a central office location of an operator's network. Those central locations may have transport network (TN) connections (e.g., via tree- or ring-based fibers) to several gNB-DUs located at different antenna sites. In such deployment case the gNB-CU-CP has the responsibility for proper operation of a large number of cells covering a wider regional area, i.e., an outage has a strong impact on overall user experience in a larger part of the mobile network. Each gNB-CU-CP may be connected via multiple TNL associations. As implicitly stated by the note in TS 38.401[2] gNB-DUs at antenna sites may be connected via the same or different TN links to one or several central locations (geo-redundancy) hosting gNB-CU-CP instances. + +The following failure scenarios have been discussed: + +- Hardware failure +- Software failure +- Transport network failure +- Power failure +- Entire gNB-CU-CP failure, e.g., due to natural disaster + +It was confirmed that some failures in the gNB-CU-CP may be addressed by using virtualization technology. + +On the other hand, there is a scenario with possibly an entire gNB-CU-CP failure (e.g. due to natural disasters). Resiliency mechanisms to recover from such failure may be achieved via gNB-DU's connection to multiple gNB-CUs by appropriate implementation, as captured in TS 38.401[2]. + +# --- 6 Conclusion + +In this TR, failure scenario in the existing gNB-CU-CP architecture from various perspectives were studied. + +A failure affecting the entire (logical) gNB-CU-CP would impact all UEs served by the cells of the gNB-DUs connected to the gNB-CU-CP, resulting in those UEs being out of service for potentially long periods of time (dependent on type of failure and available resiliency measures). Current specification allows for some resiliency mechanisms via appropriate implementation (as described in TS 38.401[2]) which can address a number of the failure scenarios. + +# --- Annex (informative): Failure Scenario from each contribution's view + +## A.1 Scenario and issue description (R3-224787) + +### A.1.1 CU SW failure + +#### **Failure reason** + +gNB-CU-CP SW failure caused by software in gNB-CU-CP's equipment. This is mainly caused by information inconsistencies in the software, which in most cases can be resolved by restarting the system (or, in case of a virtualized implementation, by respawning the relevant software parts). + +#### **Failure impact** + +The impact of the failure and the extent of the restart depends on the configuration of the equipment and where the problem occurs. In some cases, the effect may be limited to only some functions in the gNB-CU-CP, while in other cases, all functions in the gNB-CU-CP may be affected. + +### A.1.2 gNB-CU-CP HW failure + +#### **Failure reason** + +gNB-CU-CP HW Failure is a problem caused by the hardware of the gNB-CU-CP, mainly due to aging and deterioration of the HW of the gNB-CU-CP, and in most cases can be resolved by replacing some of the HW in the equipment. + +#### **Failure impact** + +The impact of the failure and the extent of the replacement depends on the configuration of the equipment and the part of the problem. In some cases, only some functions of the gNB-CU-CP will be affected, but it is expected that the whole gNB-CU-CP will be affected, especially in the case of vRAN scenarios. + +### A.1.3 Power outages + +#### **Failure reason** + +Power outages are caused by power grid failures due to various disasters (earthquakes, lightning, tsunamis, fires, windstorms, snowstorms, etc.), as well as by malfunctions of substation equipment or cable breaks in the station building. + +#### **Failure impact** + +The impact of a failure depends on the part of the system where the failure occurs, but often affects multiple gNB-CU-CPs. The higher degree of centralization, the more gNB-CU-CPs will be affected. + +### A.1.4 Transport network failure (out of 3GPP scope) + +#### **Failure reason** + +Transport network failures result from cable breaks in transmission lines, network equipment failures, and misconfigurations. These can also occur as software or hardware malfunctions, disasters, or human error. + +#### **Failure impact** + +The impact of a failure depends on the part of the system where the failure occurs. When the failure occurs outside line, it often affects multiple gNB-CU-CPs. The higher degree of centralization, the more gNB-CU-CPs will be affected. + +### A.1.5 Summary of failure scenarios + +Failures affecting only one gNB-CU-CP can be addressed by existing countermeasures. + +For failures affecting multiple gNB-CU-CPs simultaneously, in particular when the cause of the failure is closely related to the region, such as a disaster, a solution that takes advantage of the different locations for deploying redundant infrastructure should be considered. + +## A.2 Scenario (R3-224281) + +The most relevant scenarios in regard to gNB-CU-CP are those that will incur a failure of the entire gNB-CU-CP. Such cases would affect all the existing UE contexts under the gNB-CU-CP where the failure occurred. Likewise, the disaggregated gNB architecture allows for very large configurations. A given gNB-CU-CP can host 512 gNB-DUs, and a total of 16,384 cells with existing specifications. Furthermore, each cell may be serving hundreds of UEs. Therefore, a gNB-CU-CP failure can incur a very high impact in service availability and user experience for a very large number of UEs. Further, these failure scenarios can incur further problems by generating very high signalling loads from e.g., re-establishment of connections and signalling interfaces. + +In contrast issues affecting only limited portions of the gNB-CU-CP, for example, trouble incurred from individual hardware blades in a virtualized environment, are not the focus of this study. + +### A.2.1 Scenarios A, B, C + +#### (A) Node breakdown leading to a gNB-CU-CP failure + +This failure scenario includes cases where the gNB-CU-CP becomes completely unresponsive. This could be e.g., due to hardware failure, or power source becoming lost and unrecoverable. + +#### (B) Natural disaster leading to loss of the gNB-CU-CP + +This failure scenario includes cases where the gNB-CU-CP becomes unrecoverable due to the node itself becoming destroyed or its required connectivity, hence becoming unrecoverable. This could be result of e.g., an earthquake, tsunami, or major fire. + +#### (C) Human-made disaster leading to loss of the gNB-CU-CP + +This failure scenario is similar to that caused by natural means but with the source of the failure being due to human involvement. This failure could be result e.g., of war, civil war, terrorism or social unrest. + +![Diagram illustrating gNB-CU-CP failure scenarios. A central gNB-CU-CP node at Location B is shown as failed (indicated by a red 'No' symbol and a 'Node is Lost!' label). It is connected via E1 interfaces to two gNB-CU-UP nodes: gNB-CU-UP1 at Location A and gNB-CU-UP2 at Location C. The gNB-CU-UP nodes are connected via F1-U interfaces to multiple gNB-DU nodes (gNB-DU1, gNB-DU2, gNB-DU3, ..., gNB-DU512). The gNB-DU nodes are connected via F1-C interfaces to the gNB-CU-CP node. The diagram shows that the failure of the gNB-CU-CP node at Location B affects all connected gNB-DU nodes and their associated cells.](a92b1fdf37a74b707e9f03087c8f1377_img.jpg) + +The diagram illustrates a network architecture with three main locations: Location A, Location B, and Location C. + - **Location A** contains a blue box labeled 'gNB-CU-UP1'. + - **Location B** contains a blue box labeled 'gNB-CU-CP' which is marked with a red 'No' symbol and a label 'Node is Lost!'. Above it, a yellow starburst indicates an explosion or failure. + - **Location C** contains a blue box labeled 'gNB-CU-UP2'. + - At the bottom, there are several grey boxes representing gNB-DUs: 'gNB-DU1 (cells 1-32)', 'gNB-DU2 (cells 33-64)', 'gNB-DU3 (cells 65-96)', an ellipsis, and 'gNB-DU512 (cells 16,352-16,384)'. + - Dashed lines labeled 'E1' connect gNB-CU-UP1 and gNB-CU-UP2 to the gNB-CU-CP. + - Solid lines labeled 'F1-U' connect gNB-CU-UP1 and gNB-CU-UP2 to the gNB-DUs. + - Dashed lines labeled 'F1-C' connect the gNB-DUs to the gNB-CU-CP. + +Diagram illustrating gNB-CU-CP failure scenarios. A central gNB-CU-CP node at Location B is shown as failed (indicated by a red 'No' symbol and a 'Node is Lost!' label). It is connected via E1 interfaces to two gNB-CU-UP nodes: gNB-CU-UP1 at Location A and gNB-CU-UP2 at Location C. The gNB-CU-UP nodes are connected via F1-U interfaces to multiple gNB-DU nodes (gNB-DU1, gNB-DU2, gNB-DU3, ..., gNB-DU512). The gNB-DU nodes are connected via F1-C interfaces to the gNB-CU-CP node. The diagram shows that the failure of the gNB-CU-CP node at Location B affects all connected gNB-DU nodes and their associated cells. + +Figure A.2.1-1: Example of gNB-CU-CP Failure Scenarios (A)(B)(C) + +### A.2.2 Scenario D + +#### **(D) Signalling Interface Link Failure** + +This failure includes cases where the control plane signalling link becomes unavailable. The issue may be temporary (e.g., intermittent issues at a switch/router at a given communication path), or (semi-)permanent. + +![Diagram of gNB-CU-CP Failure Scenario (D)](053f1077d592e6622cd21dc4bb4cb366_img.jpg) + +The diagram illustrates a network architecture for Scenario D. At the top, 'Location B' contains a dark blue box labeled 'gNB-CU-CP'. To its right, 'Location C' contains a light blue box labeled 'gNB-CU-UP2'. A dashed line labeled 'E1' connects them. Below 'Location B', 'Location A' contains a light blue box labeled 'gNB-CU-UP1', connected to the gNB-CU-CP by a dashed line labeled 'E1'. At the bottom, several grey boxes represent gNB-DUs: 'gNB-DU1 (cells 1-32)', 'gNB-DU2 (cells 33-64)', 'gNB-DU3 (cells 65-96)', an ellipsis, and 'gNB-DU512 (cells 16,352-16,384)'. Each DU is connected to the gNB-CU-CP by a dashed line labeled 'F1-C' and to the gNB-CU-UP1 by a solid line labeled 'F1-U'. A red 'Link Failure!' box with a yellow starburst and a red 'no' symbol is placed over the F1-C link between the gNB-CU-CP and the gNB-DU512. + +Diagram of gNB-CU-CP Failure Scenario (D) + +Figure A.2.2-1: Example of gNB-CU-CP Failure Scenario (D) + +### A.2.3 Scenario E + +#### **(E) Planned Maintenance Causing Downtime** + +This use case corresponds to maintenance events (e.g., Software upgrade, new feature activations, public protests or temporary unrest). Software upgrade may result in a full reboot of the gNB-CU-CP as well. + +![Diagram of gNB-CU-CP Failure Scenario (E)](b10763be31553f31cbb795653b731a43_img.jpg) + +The diagram illustrates a network architecture for Scenario E. It is identical to the diagram in Scenario D, but instead of a link failure, the 'gNB-CU-CP' box in 'Location B' is marked with a red 'Reboot!' label and a red 'no' symbol, indicating a complete failure of the control plane unit. + +Diagram of gNB-CU-CP Failure Scenario (E) + +Figure A.2.3-1: Example of gNB-CU-CP Failure Scenario (E) + +## A.3 Scenario and issue description (R3-224303) + +In the legacy network architecture, a gNB-CU-DU is only connected to one gNB-CU-CP. With the increasing number of connected gNB-CU-UP and gNB-DU, gNB-CU-CP will be in the risk of failure caused by the large amount of signalling processing. So this SI will introduce a mechanism to allow the gNB-CU-UP and gNB-DU to recovery service. Higher-layer split between gNB-CU and gNB-DU would enable highly-centralized gNB-CU deployment with large coverage area per gNB-CU, especially from C-Plane perspective. Likewise, Higher-layer split between gNB-CU-CP and gNB-CU-UP would enable highly-centralized gNB-CU-CP deployment with large coverage area per gNB-CU-CP. + +As described in the draft SID, such a centralized gNB-CU(-CP) would be a single point of failure. Hence the resiliency of the gNB-CU(-CP) is highly important. Given the limited time allocated for gNB-CU resiliency, only gNB-CU-CP resiliency should be considered in this release, other network nod, e.g. AMF, gNB CU(non-split CU architecture) should not be considered in this release if time not allowed. + +Failure condition: + +Failure condition is the trigger of gNB-CU-CP resiliency. If a network node is considered a failure when it is crashed completely, then it would be too late to recovery. The network should have scheme to switch part or all of the services/connections to another resilient network node to offload before it completely crashes down. The decision of offloading the service/connection can be either of the below: + +- 1) Up to the implantation of gNB-CU-CP +- 2) The configured threshold from OAM + +Both options work and has no impact to RAN3. So the failure condition can be left to network implementation. + +In addition, if any of the adjacent nodes of gNB-CU-CP, e.g. AMF, gNB-CU-CP and gNB-DU lost the connection to gNB-CU-CP, due to an unexpected gNB-CU-CP failure, adjacent node should be able to activate the resilient gNB-CU-CP automatically. + +## A.4 Scenario and issue description (R3-224324) + +The most critical cases are failures that may happen if a gNB-CU-CP is deployed in a central office location with responsibility for a high number of gNB-DUs and therefore of cells. There are different failure scenarios that may happen in such a deployment scenario: + +- (1) SW or HW failure in a PNF-based implementation; +- (2) VNF (SW) or GPP (HW) failure in a virtualized environment (e.g. cloud-based implementation); +- (3) Failures of NW connections, e.g., TN or server NW card failures; +- (4) Total failure of central location, e.g., caused by a power shutdown or a disaster case. + +For failure scenarios (1) and (2) the gNB-CU(-CP) functionality can be recovered by taking local redundancy in the same central location into account (e.g., based on usage of spare HW (PNF/GPP) for redundancy purposes). A slow recovery can be initiated via OAM orchestrating a new gNB-CU(-CP) instance on the spare HW (e.g., in combination with cloud-based mechanisms in a virtualized environment). A fast recovery approach to bring the outage time down would require active/stand-by operation of a mirror gNB-CU-CP instance in parallel which may be realized in a local environment by appropriate implementation (incl. also cloud-based mechanism in case of virtualization). + +Slow recovery may also work in case of failure scenarios (3) and (4) using a second central location for orchestrating a new gNB-CU-CP instance via OAM, but the critical and more important issue from an operator's perspective is fast recovery in the geo-redundant case as 3GPP specifications do not provide suitable support for it. + +Therefore, the failure case where a benefit of a resiliency enhancement in 3GPP specifications is seen would be: + +- Outage of gNB-CU(-CP) when deployed in a central location without sufficient local redundancy, but availability of geo-redundancy (SW/HW) is given and fast recovery of gNB-CU(-CP) functionality is required by the operator. + +Note: Fast recovery would also incorporate the gNB-CU-UP functionality in a redundant central location if it was running in the primary central location experiencing the failure. + +## A.5 Failure Case (R3-224576) + +*If a gNB-CU-CP fails, the network support for the NR cells is lost and UEs cannot communicate.* More specifically, the following can be observed: + +- CP signaling redundancy is possible in RAN, but still only one RRC-anchor (gNB-CU-CP) is defined: + - SRB duplication is possible in DC (PDCP duplicates RRC messages, which are sent via different carriers to/from UE), but losing the main connection to the UE still means CP failure + - RLF handling: + - Rel-15: if SCG connection fails, inform the network; if MCG fails, the connection is lost + - Rel-16: if SCG/MCG connection fails, inform the network via MCG/SCG. There will be MCG/SCG UP downtime due to DRBs suspension. +- CP failure leading to UP failure (UP failure, leading to service interruption time, is probably the most important KPI associated with a CU-CP failure): + - Generally, an absence of RRC messages is not noted by the UE, so the UE does not know that the CP has failed + - RRC timer expiry procedures in RRC work as long as RRC connectivity is up. In some cases DRBs suspension is caused by the expiration of timers + - If the gNB-CU-CP goes down, CP connectivity is not re-established automatically until the failure is detected + - UP connection could be lost if RRC reconfiguration (critical to maintain UP) is not possible + - e.g. Handover required; bearer reconfiguration required; meet QoS or other RAN reconfiguration required + +There is always a single RRC anchor even for the case of DC; furthermore, there is currently no way for the UE to detect a gNB(-CU(-CP)) failure. + +A CU-CP failure is essentially a node internal failure (i.e. it may not be the whole logical node that fails). + +## A.6 Scenario and issue description (R3-224627) + +### A.6.1 Scenario #1: Geographical Redundancy + +#### A.6.1.1 General description + +Geographical redundancy is the distribution of mission-critical components or infrastructures, such as the servers across multiple data centers that reside in different geographic locations, which is able to ensures high availability and disaster recovery. Geographical redundancy will replicate the data and store it in other databases located in the separate physical locations. Even one of the locations fails or simply needs to be taken offline, the other location with the replicated data will not be affected. + +Considering the geographical redundancy for gNB-CU-CP, the backup gNB-CU-CP could be allocated in the separate physical locations. In this case, even the original gNB-CU-CP detects the failures and cannot work, the appearance of the backup gNB-CU-CP is able to avoid the interruption of multiple UP traffic or the disconnection of multiple UEs. + +## A.7 Scenario and issue description (R3-224754) + +### A.7.1 Local Redundancy + +The split NG-RAN architecture consists of single logical gNB-CU-CP connected to multiple logical gNB-CU-UPs and multiple logical gNB-DUs, and the gNB-CU-CP is connected to multiple AMFs in 5GC. The logical gNB-CU-CP function can be implemented and deployed with the Network Function Virtualization as shown in Figure A.7.1-1. And the logical gNB-CU-CP function can be split further with sub-functions, e.g. network interface sub-function, and each sub-function can be implemented as a virtual network function component (VNFC). + +![Diagram illustrating gNB-CU-CP failure scenarios. It shows three stacked layers: the top layer contains two boxes labeled 'CU-CP (VNF)' and 'CU-UP (VNF)'; the middle layer is a box labeled 'Virtualization'; and the bottom layer is a box labeled 'Physical Infrastructure (Server)'.](ddc7460821484f1ae2835c67955c554c_img.jpg) + +``` +graph TD; subgraph TopLayer [ ]; CU_CP[CU-CP (VNF)]; CU_UP[CU-UP (VNF)]; end; CU_CP --- Virtualization[Virtualization]; CU_UP --- Virtualization; Virtualization --- Physical[Physical Infrastructure (Server)]; +``` + +Diagram illustrating gNB-CU-CP failure scenarios. It shows three stacked layers: the top layer contains two boxes labeled 'CU-CP (VNF)' and 'CU-UP (VNF)'; the middle layer is a box labeled 'Virtualization'; and the bottom layer is a box labeled 'Physical Infrastructure (Server)'. + +Figure A.7.1-1: gNB-CU-CP failure scenarios + +### A.7.2 Failure Scenarios + +#### A.7.2.1 Server Failure + +The server may not work properly because of hardware failure or virtualization platform failure. The hardware failure is caused owing to some deterioration or the instant failure of the hardware. Depending on the failure cause, the hardware needs to be replaced or be recovered by rebooting the system. The virtualization platform failure is caused by software error, so it could be also recovered by rebooting the system or by the software upgrade. + +#### A.7.2.2 VNFC (Virtual Network Function Component) Failure + +The logical gNB-CU-CP function can be implemented with sub-functions, e.g. network interface sub-function, and they can be separately implemented as VNFC (Virtual Network Function Component) and interact each other. One or more VNFCs consisting a gNB-CU-CP may not work properly owing to software error or other reason. Mostly the VNFC failure could be recovered by rebooting the system or by the software upgrade. + +#### A.7.2.3 Transport Link Failure (out of 3GPP scope) + +Transport link failure is caused by the malfunction of transport link hardware or software. The failure also comes from the transmission line problem or the transport network equipment failure. If the transport link failure caused in the gNB-CU-CP system, the failure could be recovered by rebooting the system or by the software upgrade. If the failure caused outside the gNB-CU-CP system, the transmission line needs to be substituted or the network equipment needs to be rebooted, upgraded or substituted. + +### A.7.3 Failure Impact + +In any failure scenarios, there exist solutions to recover the logical gNB-CU-CP operation, e.g. system reboot, software upgrade, hardware replacement. Depending on the recovery solution, it may take a few minutes or some days and it may break the service continuity of the gNB-CU-CP. + +So to minimize the interruption of UP traffic and disconnection of UEs, the virtualized gNB-CU-CP function could be duplicated, and the data used is shared and synchronized between duplicated gNB-CU-CP function. And if a failure is detected, the role of duplicated gNB-CU-CP functions are exchanged to support fast switch-over by implementation. + +## A.8 Scenario and issue description (R3-224898) + +### A.8.1 Possible failure scenarios + +The purpose of this SI is to Study and identify failure scenarios associated with the gNB-CU-CP, based on the current architecture for the NG-RAN, which could be referred in 38.401 [2], see below: + +![Figure A.8.1-1 Overall architecture for separation of gNB-CU-CP and gNB-CU-UP. The diagram shows a gNB-CU-CP connected to multiple gNB-CU-UP units via E1 interfaces. Each gNB-CU-UP is connected to two gNB-DU units via F1-U interfaces. The gNB-CU-CP is also connected to the gNB-DU units via F1-C interfaces. The entire gNB architecture is enclosed in a dashed box labeled 'gNB'.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +Figure A.8.1-1 Overall architecture for separation of gNB-CU-CP and gNB-CU-UP. The diagram shows a gNB-CU-CP connected to multiple gNB-CU-UP units via E1 interfaces. Each gNB-CU-UP is connected to two gNB-DU units via F1-U interfaces. The gNB-CU-CP is also connected to the gNB-DU units via F1-C interfaces. The entire gNB architecture is enclosed in a dashed box labeled 'gNB'. + +Figure A.8.1-1 Overall architecture for separation of gNB-CU-CP and gNB-CU-UP + +gNB-CU-CP as a logical node, could be deployed in different way which is up to operator and vendor's strategy, e.g. could be software plus dedicated hardware within a physical box or, could be software instance run over virtualized environment (generic hardware). Thus, the failure could happen at any single point distributed at any place in Figure A.8.1-1, i.e. either to software or to hardware which would finally lead to the unavailability of gNB-CU-CP; in addition, power is also a main factor causing failure. + +# Annex (informative): Change history + +| Change history | | | | | | | | +|----------------|------------|-----------|----|-----|-----|-------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-08 | RAN3#117-e | R3-225156 | | | | TR skeleton | 0.0.1 | +| 2022-08 | RAN3#117-e | R3-225212 | | | | Updated draft TR | 0.1.0 | +| 2022-08 | RAN3#117-e | R3-225251 | | | | Editorial changes in Change history | 0.1.1 | +| 2022-09 | RAN#97-e | RP-222271 | | | | For approval in plenary | 1.0.0 | +| 2022-09 | RAN#97-e | | | | | TR approved by TSG RAN plenary | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38882/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38882/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbc0c6cde6387d4c591b14daca3973262ce897f6 --- /dev/null +++ b/marked/Rel-18/38_series/38882/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:350f8556533eb65701bad2ca92ac4a648d3ddbf83e7ba189774638b6f439e93b +size 9589 diff --git a/marked/Rel-18/38_series/38882/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38882/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e033d91fe700a19e8f4e4e1300c76e088b62bb47 --- /dev/null +++ b/marked/Rel-18/38_series/38882/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7980621fe7fe21d42131a8e51b600aa650a8b3864f3ecedbc1a90100d594b3a3 +size 5670 diff --git a/marked/Rel-18/38_series/38882/raw.md b/marked/Rel-18/38_series/38882/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3e1ebf54c5cebff1730974ae459a07230d744d71 --- /dev/null +++ b/marked/Rel-18/38_series/38882/raw.md @@ -0,0 +1,416 @@ + + +# 3GPP TR 38.882 V18.0.0 (2022-06) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on requirements and use cases for network verified UE location for Non-Terrestrial-Networks (NTN) in 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 'P' is a small 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. + +© 2022, 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..... | 7 | +| 3.1 Terms..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 Use cases..... | 7 | +| 4.1 Background from Rel-17 Discussions..... | 7 | +| 4.2 NTN vs. Terrestrial Regulatory Requirements ..... | 8 | +| 4.3 Regulatory support of services in NTN..... | 8 | +| 4.4 LCS and NTN..... | 9 | +| 5 Recommendations..... | 10 | +| Annex A (informative): Requirements for UE location verification ..... | 11 | +| A.1 Emergency calls ..... | 11 | +| A.2 Lawful intercept (LI)..... | 11 | +| A.3 Public warning Service (PWS)..... | 12 | +| A.4 Charging and Tariff notifications..... | 12 | +| A.5 All regulated services..... | 13 | +| Annex B (informative): Change history ..... | 13 | + +# 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 analyses the regulatory requirements (e.g. accuracy, privacy, reliability, latency) in terms of UE location service for a set of use cases/services (i.e. emergency call, lawful intercept, public warning, charging/billing). It identifies the possible need for network-verified UE location specification support in Rel-18. + +# --- 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 23.737: "Study on architecture aspects for using satellite access in 5G (Release 17)". +- [3] 3GPP TR 22.926: "Guidelines for Extraterritorial 5G Systems; Stage 1". +- [4] 3GPP S3i200056: "Response LS on the "LS OUT on Location of UEs and associated key issues""(Contact: Rogers). +- [5] 3GPP TR 22.872: Study on positioning use cases; Stage 1 (Release 16). +- [6] Standardisation Request for E112 (as regards hand-held mobile phones in support of Directive 2014/53/EU). +- [7] "Indoor Location Accuracy Benchmarks", retrieved from on 20.10.2020. +- [8] 3GPP S3i210282 "Reply LS on UE location aspects in NTN" (contact = Tencastle) +- [9] R2-2101150 Summary of [Post112-e][115][NTN] the Email Discussion on LCS for NTN, Fraunhofer IIS, Fraunhofer HHI. +- [10] ETSI TS 103 625: "Transporting Handset Location to PSAPs for Emergency Calls - Advanced Mobile Location". +- [11] Directive (EU) 2018/1972 of the European Parliament and of the Council of 11 December 2018 establishing the European Electronic Communications Code (Recast) (See Official Journal of the European Union, Volume 61, 17th December 2018), . +- [12] Official Journal C 329, 04/11/1996 p. 0001 - 0006 Council Resolution of 17 January 1995 on the lawful interception of telecommunications. +- [13] REGULATION (EU) 2016/679 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation) . +- [14] 3GPP "SID on Study on expanded and improved NR positioning", RP-213588 +- [15] 3GPP TS 38.300 "NR; NR and NG-RAN Overall description; Stage-2". + +[16] 3GPP TS 22.261 "Service requirements for the 5G system". + +# --- 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]. + +| | | +|------|-------------------------------------| +| EMS | Emergency Services | +| GNSS | Global Navigation Satellite Systems | +| GSO | Geo Synchronous Orbit | +| HAPS | High Altitude Platform System | +| LI | Lawful Intercept | +| NAS | Non Access Stratum | +| NGSO | Non Geo Synchronous Orbit | +| NNSF | NAS Node Selection Function | +| NTN | Non-Terrestrial Network | +| PLMN | Public Land Mobile Network | +| PWS | Public Warning System | +| RAT | Radio Access Technology | +| SMS | Short Message Service | +| TN | Terrestrial network | +| UE | User Equipment | + +# --- 4 Use cases + +## 4.1 Background from Rel-17 Discussions + +When a UE attaches to the mobile network, the RAN selects the appropriate core network for the UE taking into account, among other things (TS 38.300 [15]): + +- UE identifiers; +- UE's selected PLMN; +- UE location information (including the serving cell as known to the serving RAN node). + +With NTN it is possible to deploy very large cells over large portions of a continent (possibly covering different countries), with the different core networks for the various countries connected to the same NTN RAN (MOCN network sharing scenario). In such a scenario, it may not always be possible to correctly determine the appropriate core + +network for a connecting UE, especially close to country borders, because the serving cell information may not be granular enough. + +Furthermore, a malicious UE might "fake" its selected PLMN in order to attempt connecting to a different core network. Upon such an attempt the AMF will disconnect the UE and inform the RAN node via an appropriate NGAP cause value, so the RAN can take appropriate action on subsequent attempts by the same UE. + +The UE may send GNSS measurements to the RAN over RRC, but this has at least the following drawbacks: + +- In principle, just as a malicious UE could fake its selected PLMN, it could also fake its GNSS measurements; +- Sending GNSS measurements over RRC before AS security is set up raises security and privacy issues. + +Because of the above, relying only on signalling GNSS measurements over RRC is not considered a viable solution to this issue. + +As recommended in SA3 LS to RAN2 (R2-2204458) the location information is sent after NAS security is established. Even after NAS security establishment, user consent for obtaining UE location information may also be required depending on regional regulation and policy. + +The RAN can also request radio measurements (intra-RAT neighbours, inter-RAT neighbours, WLAN, etc.) from the UE; these may be used to drive NNSF and to learn from the environment. + +Some further observations: + +- a) At least some of the information the UE supplies to the network will have to be considered as trusted, to avoid extreme conclusions (at least RRC measurements cannot be faked); +- b) Core networks connecting to the same shared RAN will always require some degree of common coordination / configuration: this is typically the case for network sharing (especially MOCN). For NTN, this may include e.g. specific timer settings/behaviour for UE connection attempts; +- c) Due to mere traffic load considerations, it may not be desirable to cover whole portions of a continent, including multiple countries, with a single cell. Therefore, in real deployments the served cell information may typically be more granular than in the extreme case envisaged so far. + +The above has been deemed sufficient to mitigate the issue in Rel-17. + +## 4.2 NTN vs. Terrestrial Regulatory Requirements + +A 5G system with satellite access shall be able to determine a UE's location in order to provide service (e.g. route traffic, support emergency calls) in accordance with the governing national or regional regulatory requirements applicable to that UE. (Sec. 6.3.2.3 of TS 22.261 [16]). + +Because of this, even when providing services over entire continents with NTN, there is no "globally harmonized" set of requirements that overrules local ones. This is also valid for UE location information. In this respect, there is no difference between NTN and terrestrial networks. + +Because of the above, for NTN the same required granularity for UE location information estimated via GNSS should be considered as for terrestrial networks. + +## 4.3 Regulatory support of services in NTN + +Network operators of 3GPP defined non-terrestrial network, have to know reliably the location information of a UE attached to the network in order to select the appropriate core network. Once the appropriate core network has been selected for a UE, it is possible to support some services subject to national regulations or other operational constraints. + +In TR 23.737 [2], the list of such services has been identified in key issue #10: + +- Public Warning System (PWS) +- Lawful interception (LI) +- Emergency services (EMS) + +- Charging and Tariff notifications + +In TR 22. 926 [3], it has been identified that *"To support regulated services and features (e.g. Public Warning System, Charging and Billing, Emergency calls, Lawful Intercept, Data Retention Policy in cross-border scenarios and international regions, Network access), 3GPP networks should have the capability to locate each UE in a reliable manner and determine the policy that applies to their operation depending on their location and/or context."* + +Furthermore, in [4], it is pointed out that *"any solution addressing extraterritorial (e.g. international maritime zone and aeronautical) use cases should provide means to notify the HPLMN on roaming in and out of those areas, including the cases when the serving PLMN has not changed."* + +Relying only on the GNSS based location information reported by the UE is not considered reliable by SA3-LI [4]. + +The UE reported location information (for example determined with its GNSS receiver), could be erroneous due to intentional (e.g. maliciously tampering by user or by 3rd party) or unintentional (e.g. interference) causes, hence it cannot be considered trusted by network operators. + +Already 3GPP has defined a network based functionality to verify the reported UE location with the identifier of the serving cell. However, radio cells in non-terrestrial networks, may be larger than the ones of terrestrial networks and may cover borders between two or more countries. Therefore, such Cell Id information may not be sufficient to discriminate the country in which the UE is located. + +It is expected that solutions combining both UE reported GNSS information and network based information for verification of UE location can improve the reliability of core network selection in non-terrestrial networks. This is important for + +- Services subject to national regulations or other operational constraints. (e.g. Public Warning System (PWS), Lawful interception (LI), Emergency services (EMS), Charging and Tariff notifications). +- Cases where the UE reported location information (for example determined with its GNSS receiver), could be erroneous due to intentional (e.g. maliciously tampering by user or by 3rd party) or unintentional (e.g. interference) causes. +- NTN radio cells larger than terrestrial network radio cells and possibly covering borders between two or more countries. + +In order to define an appropriate network based solution to verify UE location, it is necessary to determine requirements for the verification accuracy. Note that these requirements should not be assumed to be the same as the regulatory requirements applicable to the UE location in terms of Accuracy, Reliability (related to law enforcement and liability), Latency and Privacy as identified in Annex A. + +As identified in annex A.2, SA3-LI recommends in S3i200056 [4] that *"The logical location shall unambiguously map to the geographical area of the UE physical location. Granularity of such geographical areas needs to be able to provide network location accuracy comparable with terrestrial networks."* + +In terrestrial networks, verification is based on Cell Id and hence, the targeted granularity is related to cell size. Similar granularity should be considered for NTN. Terrestrial macro cell size is assumed to be up to 5-10 km diameter. + +## 4.4 LCS and NTN + +Most UE positioning functionality is typically UE-associated, i.e., it assumes that a UE context is present for the UE being positioned. This means that the UE itself has already completed the initial access procedures. Because of this, all observations and mitigations already discussed in Rel-17 are still relevant and applicable. + +# --- 5 Recommendations + +In this study, we have identified the need to define a network based solution which aims at verifying the reported UE location information. + +The verification should be performed independently from the location information reported by UE. + +The UE location information for the study is considered verified if the reported UE location is consistent with the network based assessment to within 5-10 km (similar to terrestrial network macro cell size), enabling country discrimination and selection of an appropriate core network in order to support all the regulatory services (i.e. emergency call, lawful intercept, public warning, charging/billing). + +The solution should not impact significantly the latency of the targeted services nor infringe privacy requirements that apply to the UE location. + +The study in [RAN2,RAN1,RAN3], which will study and evaluate solutions for the network to verify UE reported location information, shall consider the following aspects: + +- The scenario of single satellite (or HAPS) in view by the UE at a time is considered with higher priority. + - Multiple satellite (or HAPS) in view by the UE may be considered if time allows +- Assume that the UE is attached to a network (so that its context has been set up in the network) for the purpose of positioning +- Different solutions or positioning methods for NGSO, GSO or HAPS are not precluded +- When considering solutions based on positioning methods, existing 3GPP defined RAT dependent positioning methods shall be considered as baseline. Other methods are not precluded. +- Solutions using existing NG-RAN architecture and procedures shall be considered + +# Annex A (informative): Requirements for UE location verification + +## A.1 Emergency calls + +It refers to a telephone request or text message request for emergency services (e.g. police, fire departments, or other first responders) which requires immediate action to prevent loss of life, reduce bodily injury, prevent or reduce loss of property and respond to other emergency situations determined by local policy. + +#### Accuracy + +Accuracy requirements for emergency calls have been identified in TR 22.872 [5], where the position accuracy is required to be [50m Horizontal, 3m Vertical] which are the most demanding of the regulated services in terms of accuracy requirements. This is in line with the requirements of two major regulatory bodies and summarized as follows: + +**Table A.1-1: Accuracy requirements for emergency calls** + +| Regulatory body | Accuracy requirements | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EC [6] | "capability to achieve a horizontal position error of maximum 5 metres in open sky conditions and maximum 25 metres in urban canyon conditions with a confidence level of 95 % (2s coverage factor), where open sky conditions and urban canyon conditions are as defined, respectively, in points 2.1.8 (Figure 1) and 2.2.4.2 (Figure 3) of Annex VI to Delegated Regulation (EU) 2017/793" The European directive is based on an assumption of use of GNSS as positioning technology as specified in ETSI TS 103 625 [10]. | +| FCC [7] | In 2020, the FCC specifies a 50-meter horizontal accuracy or provide a dispatchable location for 70 percent of all wireless 911 calls, which increases to 80 percent of all calls in 2021. From 2021 onwards, an additional requirement to achieve an accuracy with $\pm 3\text{m}$ is applies in addition. | + +#### Reliability + +In this case, the mobile network operator may be liable for the provision of a "reliable" UE location (either network verified or network provided) that will be the basis to the organisation of personal assistance or rescue. + +#### Latency + +The delay to determine the UE location should be minimised to ensure timely assistance or rescue, + +While a typical call set-up is less than a second, the delay for UE location determination should not impact significantly this communication set-up time. + +## A.2 Lawful intercept (LI) + +As a legally sanctioned official access to private communications, Lawful Interception (LI) is a security process in which a service provider or network operator collects and provides law enforcement officials with intercepted communications of private individuals or organizations. + +LI implementation is required for example by the European Council Resolution from 1995 [12] which allows for LI to prevent crime, including fraud and terrorism. + +#### Accuracy + +For lawful intercept, SA3-LI recommends in [4] that "*The logical location shall unambiguously map to the geographical area of the UE physical location. Granularity of such geographical areas needs to be able to provide network location accuracy comparable with terrestrial networks.*" + +Given that for such use cases, the location accuracy in terrestrial networks is mostly based on cell ID, it directly relates to the typical cell size. Hence a macro cell size granularity (accepted granularity by SA3-LI) should be sufficient to detect country border crossings. + +#### Reliability + +In this case, Law enforcement applies, and therefore the mobile network operator shall be able to provide a "reliable" UE location (either network verified or network provided). + +In S3i210282 [8], it is noted that *"any method which relies solely on UE-generated location information is unlikely to be considered reliable for network selection purposes. Therefore, a method such as GNSS/A-GNSS cannot be considered as reliable or trusted unless the information provided by the UE can be verified by the network."* + +#### Latency + +No regulatory requirement have been identified for this. Despite this, NTN location determination should not significantly impact the LI service as provided by an TN network. + +## A.3 Public warning Service (PWS) + +PWS is usually realised (based on country regulator rules) by CellBroadcast, which provides a direct selectivity by cellID (sends the message to all devices registered in a base station) but can reach sector accuracy (each of the antenna emitters in the same cellID) to provide geographical accuracy. E.g. to alert half of the city that is getting an imminent flood but not the other half which is on a higher positions. + +Alternatively Location-Based SMS may be used, and same selectivity shall be employed. That will rely on reliable location, and at least cellID is expected to be necessary. + +In its Directive (EU) 2018/1972 [11], the European Union states in (293) that + +*"Diverging national law has developed in relation to the transmission by electronic communications services of public warnings regarding imminent or developing major emergencies and disasters. In order to approximate law in that area, this Directive should therefore provide that, when public warning systems are in place, public warnings should be transmitted by providers of mobile number-based interpersonal communication services to all end-users concerned. The end-users concerned should be considered to be those who are located in the geographic areas potentially being affected by imminent or developing major emergencies and disasters during the warning period, as determined by the competent authorities."* + +#### Accuracy + +One can assume that the service should be provided over the targeted area with an equivalent granularity as obtained in terrestrial networks that is cell size related. Hence a macro cell size granularity should be sufficient. + +#### Reliability + +There are no explicit regulatory requirement for this. Despite this, NTN location determination should follow same reliability requirements as the PWS systems. + +#### Latency + +No regulatory requirement have been identified for this. Despite this, NTN location determination should not impact significantly the PWS service as provided by an TN network. + +## A.4 Charging and Tariff notifications + +Tariff refer to the set of parameters defining the applied charge for the use of a particular bearer /session / service. + +#### Accuracy + +As per Public warning service, knowing the context of the UE (country or aeronautical/maritime) is sufficient for charging and tariff notifications. + +One can assume that the accuracy of the UE location service should be similar to the one in typical terrestrial mobile networks that is cell size related. Hence a macro cell size granularity should be sufficient. + +#### Reliability + +It is the responsibility of the Mobile network operator to ensure via reliable methods that the UE is effectively in a given context for appropriate charging/billing. + +#### Latency + +No regulatory requirement have been identified for this. Despite this, NTN location determination should not significantly impact the charging/tariff service as provided by an TN network. + +## A.5 All regulated services + +#### Privacy + +In [13], it is stated in article (71) that *"The data subject should have the right not to be subject to a decision, which may include a measure, evaluating personal aspects relating to him or her which is based solely on automated processing and which produces legal effects concerning him or her or similarly significantly affects him or her, such as automatic refusal of an online credit application or e-recruiting practices without any human intervention. Such processing includes 'profiling' that consists of any form of automated processing of personal data evaluating the personal aspects relating to a natural person, in particular to analyse or predict aspects concerning the data subject's performance at work, economic situation, health, personal preferences or interests, reliability or behaviour, location or movements, where it produces legal effects concerning him or her or similarly significantly affects him or her. "* + +Therefore the UE location shall be protected to preserve the privacy of the users. + +In [13], it is further stated in article (71) that *"However, decision-making based on such processing, including profiling, should be allowed where expressly authorised by Union or Member State law to which the controller is subject, including for fraud and tax-evasion monitoring and prevention purposes conducted in accordance with the regulations, standards and recommendations of Union institutions or national oversight bodies and to ensure the security and reliability of a service provided by the controller, or necessary for the entering or performance of a contract between the data subject and a controller, or when the data subject has given his or her explicit consent. "* + +Therefore, the user location can be processed if it is to comply with regulations for example in order to provide safety to the citizen (emergency calls, public warning services), to prevent crimes (Lawful intercept) or frauds (Charging and Tariff notifications). + +# --- Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 06-2022 | RP-96 | RP-221847 | | | | first version of the TR, created at RAN #96 | 0.1.0 | +| 06-2022 | RP-96 | RP-221859 | | | | | 0.2.0 | +| 06-2022 | RP-96 | RP-221860 | | | | | 0.3.0 | +| 06-2022 | RP-96 | RP-221875 | | | | provided for approval to RAN #96 | 1.0.0 | +| 06-2022 | RP-96 | - | - | - | - | approved by RAN #96 and put under change control | 18.0.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38884/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg b/marked/Rel-18/38_series/38884/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3ac336e4c0adcda7046660894c68b262656278b --- /dev/null +++ b/marked/Rel-18/38_series/38884/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a362130a12ccd3072ae36519e4050522829a792c490e81303544bf5ba4f748b +size 15444 diff --git a/marked/Rel-18/38_series/38884/06eef9cc3970450903c158ec25346d21_img.jpg b/marked/Rel-18/38_series/38884/06eef9cc3970450903c158ec25346d21_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72923851d07df51f24be3039ce1571524203e302 --- /dev/null +++ b/marked/Rel-18/38_series/38884/06eef9cc3970450903c158ec25346d21_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5702c2f0c3e188e2755510a9ce1911a3d8144795eec7ae50475fb30bd1ff886f +size 42345 diff --git a/marked/Rel-18/38_series/38884/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-18/38_series/38884/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5231d768f283feb6599893d32e9e088b72cc8e3 --- /dev/null +++ b/marked/Rel-18/38_series/38884/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb4ae34c8916cd369876fc1ad4f4dd5b2d668b97e31c8f282c4b1cb9a80f6816 +size 54437 diff --git a/marked/Rel-18/38_series/38884/0cefc51a6600c6c8e2c2b60fcff0fb63_img.jpg b/marked/Rel-18/38_series/38884/0cefc51a6600c6c8e2c2b60fcff0fb63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d56763e65e5a754857f109a3d1f813c90bba7af --- /dev/null +++ b/marked/Rel-18/38_series/38884/0cefc51a6600c6c8e2c2b60fcff0fb63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ed9047a70b5c54ea62566a5276acedb5612f29c70ffdf4327e8a7de88734238 +size 57767 diff --git a/marked/Rel-18/38_series/38884/0e240e8e4783e664047fbdb5fbd0989f_img.jpg b/marked/Rel-18/38_series/38884/0e240e8e4783e664047fbdb5fbd0989f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b776fe6b568d3a8913d1aad97fd07c93b2dc489 --- /dev/null +++ b/marked/Rel-18/38_series/38884/0e240e8e4783e664047fbdb5fbd0989f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:105607292382d434a28ece3cfa80a89050304fd83bad7c0273775384149a2c39 +size 17062 diff --git a/marked/Rel-18/38_series/38884/17431d8b59408f09df7552d8bdbaa015_img.jpg b/marked/Rel-18/38_series/38884/17431d8b59408f09df7552d8bdbaa015_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44a02f80b3e851b492c756549d01b24436156ea8 --- /dev/null +++ b/marked/Rel-18/38_series/38884/17431d8b59408f09df7552d8bdbaa015_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8242a95cf2ad69aab46640d44974d25bf294b3a962fb95097051f338fb8dba6c +size 29746 diff --git a/marked/Rel-18/38_series/38884/19a878abbd7068d98e7d54341c8d897c_img.jpg b/marked/Rel-18/38_series/38884/19a878abbd7068d98e7d54341c8d897c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d28129a244929eab4623e9bf6e0585ead9f2f60a --- /dev/null +++ b/marked/Rel-18/38_series/38884/19a878abbd7068d98e7d54341c8d897c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff455e454ec6358c0b92a14415fec4b06df5bf974d4c0ab5f2ef497717d92885 +size 47899 diff --git a/marked/Rel-18/38_series/38884/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg b/marked/Rel-18/38_series/38884/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd647fa228e8c187f74991b2514bdfde17c28bdd --- /dev/null +++ b/marked/Rel-18/38_series/38884/1bc1bf231ada31f57cd9f0d8791b784b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a072fb957eb56eae9239805fcb52280e7a42abc84925424a0e387f8229adec34 +size 68881 diff --git a/marked/Rel-18/38_series/38884/223c6f5bda05ffdd254a828a148b53f1_img.jpg b/marked/Rel-18/38_series/38884/223c6f5bda05ffdd254a828a148b53f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f728f956083f4f0d9c0992f0715af8a72aebf55 --- /dev/null +++ b/marked/Rel-18/38_series/38884/223c6f5bda05ffdd254a828a148b53f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6af7095a225a92e23c1fac7ea371dfc4c956ecb2622d38fa8af75e22df5e3f49 +size 71937 diff --git a/marked/Rel-18/38_series/38884/26070f41b834cefd33d293fecdba9868_img.jpg b/marked/Rel-18/38_series/38884/26070f41b834cefd33d293fecdba9868_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7da17aa3856d84680a5e399181f4626f1de320d --- /dev/null +++ b/marked/Rel-18/38_series/38884/26070f41b834cefd33d293fecdba9868_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23d1fa73d4c97927988840abc3103ef77b38cffff19808c1db6360b908260e73 +size 21599 diff --git a/marked/Rel-18/38_series/38884/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-18/38_series/38884/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cae84ae2dba70d566c0b544fe98b2402c5fa4c9c --- /dev/null +++ b/marked/Rel-18/38_series/38884/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6b467222d79fdc3d510dd2266fe433cdb35f1ab9e9aa94410d948cd5ca52a03 +size 62799 diff --git a/marked/Rel-18/38_series/38884/2957154f4dc666a6cafb7b4d2d882910_img.jpg b/marked/Rel-18/38_series/38884/2957154f4dc666a6cafb7b4d2d882910_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2da87cbfb0d6d8cc673b4fdec88dd299e2442b6c --- /dev/null +++ b/marked/Rel-18/38_series/38884/2957154f4dc666a6cafb7b4d2d882910_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:235a994cf5ab113948ff25e0e889b6394d2f22295aa5b2a357719c34c83691e7 +size 40813 diff --git a/marked/Rel-18/38_series/38884/31d28c91958950ee8785840552992758_img.jpg b/marked/Rel-18/38_series/38884/31d28c91958950ee8785840552992758_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..163318bd0ce2ec9f960835f67fb6c6c9989d9a75 --- /dev/null +++ b/marked/Rel-18/38_series/38884/31d28c91958950ee8785840552992758_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:534b662d6645724172d836683dccbb9630450d57b57c3faaaad1d68f0be15ca8 +size 58702 diff --git a/marked/Rel-18/38_series/38884/3750b0149a6380885998ab3ca6a8787c_img.jpg b/marked/Rel-18/38_series/38884/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53c415923e8167b01a6acc39c3d78824371570ab --- /dev/null +++ b/marked/Rel-18/38_series/38884/3750b0149a6380885998ab3ca6a8787c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21edc8816f9119402cd82c2558467e50fe3269fd8b1141e5c3b5c324583adb8d +size 80409 diff --git a/marked/Rel-18/38_series/38884/48fc91e19c1a9b6674b120fbdd89b203_img.jpg b/marked/Rel-18/38_series/38884/48fc91e19c1a9b6674b120fbdd89b203_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae3a874bf727f8e2a392067eaf3178ff5954d29a --- /dev/null +++ b/marked/Rel-18/38_series/38884/48fc91e19c1a9b6674b120fbdd89b203_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d68eda8267bfa0a639fa32768ae94797789efe4f4c6f356b0a94e1a580a9d57a +size 54938 diff --git a/marked/Rel-18/38_series/38884/53a3d214d0850fac26a99299ef3cb43e_img.jpg b/marked/Rel-18/38_series/38884/53a3d214d0850fac26a99299ef3cb43e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4ab69536f5eda4207aa0328959e38ae0a276656 --- /dev/null +++ b/marked/Rel-18/38_series/38884/53a3d214d0850fac26a99299ef3cb43e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90a3ffcab4052c43d02beb62b85bbb10f6e886077f2dc494bdfffe2e401e1992 +size 42372 diff --git a/marked/Rel-18/38_series/38884/53d8bef47c63e0897de4cd058bad2cbd_img.jpg b/marked/Rel-18/38_series/38884/53d8bef47c63e0897de4cd058bad2cbd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17396a6c06fb0a8bb0aeffd7826475d31fdc7d28 --- /dev/null +++ b/marked/Rel-18/38_series/38884/53d8bef47c63e0897de4cd058bad2cbd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5585bb2752a708786d497f52ca4e38229d964e538d444f0464945bdf9275c1f9 +size 52172 diff --git a/marked/Rel-18/38_series/38884/54bab05b404ce895e109a02e758a548a_img.jpg b/marked/Rel-18/38_series/38884/54bab05b404ce895e109a02e758a548a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c62701bf3a77bfd1da7b0454b1a246c89a1c823b --- /dev/null +++ b/marked/Rel-18/38_series/38884/54bab05b404ce895e109a02e758a548a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4df4967ad8f39085368224c16c1819c8626d853df5a3429fde998529be46aff +size 18384 diff --git a/marked/Rel-18/38_series/38884/552328a9daaf3bc0069424b500025880_img.jpg b/marked/Rel-18/38_series/38884/552328a9daaf3bc0069424b500025880_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bad45d1352eeea0d5a22d74f3afc9386700847eb --- /dev/null +++ b/marked/Rel-18/38_series/38884/552328a9daaf3bc0069424b500025880_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cdce5f7a59b24a29591c50073152df336381e4c709c4098b97db176d6c65ce8 +size 78102 diff --git a/marked/Rel-18/38_series/38884/572cf014db14c8234f91c07d5a5a28c6_img.jpg b/marked/Rel-18/38_series/38884/572cf014db14c8234f91c07d5a5a28c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..326eec97a5d5d8d0a8fcdd2d443364adb00279fb --- /dev/null +++ b/marked/Rel-18/38_series/38884/572cf014db14c8234f91c07d5a5a28c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:628dfbfea355382634a53b79e3b451f6b48034e296705912dfc77591b388c1ed +size 34345 diff --git a/marked/Rel-18/38_series/38884/5ad593a688ae2c96712847c300171b5d_img.jpg b/marked/Rel-18/38_series/38884/5ad593a688ae2c96712847c300171b5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27cbb3a445a70ec85f0c5c1e96a40fd8f550b3a6 --- /dev/null +++ b/marked/Rel-18/38_series/38884/5ad593a688ae2c96712847c300171b5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eeb727c1aa7eb09ea3239209bf00e89a7416a67cd3d52128308589ef57525728 +size 37866 diff --git a/marked/Rel-18/38_series/38884/5c1059b19e142ca5a6d58f18f3767b97_img.jpg b/marked/Rel-18/38_series/38884/5c1059b19e142ca5a6d58f18f3767b97_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec46a6100ac95dc0f3444076582815319ad864a7 --- /dev/null +++ b/marked/Rel-18/38_series/38884/5c1059b19e142ca5a6d58f18f3767b97_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a09850ab07be9a8826db1827702e270b41c3d2a19762e2596257302fef1a067c +size 54378 diff --git a/marked/Rel-18/38_series/38884/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38884/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..782a57c5a1b6b3621eb176ec0bb337efbf5003b5 --- /dev/null +++ b/marked/Rel-18/38_series/38884/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:364ea0cc3b44fe271b5ad3a2256b5c876d8c60fc09fd14c164189b454d5c7c19 +size 9374 diff --git a/marked/Rel-18/38_series/38884/609dff0a56be2ded8c960a3672afa937_img.jpg b/marked/Rel-18/38_series/38884/609dff0a56be2ded8c960a3672afa937_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eafc91a67768d0168e63e1807d8ea77e7dc14788 --- /dev/null +++ b/marked/Rel-18/38_series/38884/609dff0a56be2ded8c960a3672afa937_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d15f63d36a3a647515f3f185a1a87046db884b7cb0b5f9c504e640912f19ef91 +size 32969 diff --git a/marked/Rel-18/38_series/38884/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38884/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2d371852a5b48cc48722659b1a366b441793c7d --- /dev/null +++ b/marked/Rel-18/38_series/38884/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d51b3ad4ba455d18095dae6c162895d4c5131179ce6d440b8c0b39add5d65050 +size 5726 diff --git a/marked/Rel-18/38_series/38884/68f0e97e094e315c0ed95a24eb0585c3_img.jpg b/marked/Rel-18/38_series/38884/68f0e97e094e315c0ed95a24eb0585c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1b5b7180b85d0eeb4dbe9e2f8a97fd1d6334d78 --- /dev/null +++ b/marked/Rel-18/38_series/38884/68f0e97e094e315c0ed95a24eb0585c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa7de46c6e2fcb805dfd640335ac33e19686bc6c5a9cf6d3ea1d893604a79f25 +size 39726 diff --git a/marked/Rel-18/38_series/38884/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/marked/Rel-18/38_series/38884/6ca05954842b17f14dfd52f26b9d43d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3daf2af882311127afcb8494eaad3318ee2f0b8c --- /dev/null +++ b/marked/Rel-18/38_series/38884/6ca05954842b17f14dfd52f26b9d43d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:821c7ee3764c251ab003cadece45e3048e4e4635d1d43374d4e2432c418a4fca +size 37466 diff --git a/marked/Rel-18/38_series/38884/72dc35c6c075018909676f36a0a98af1_img.jpg b/marked/Rel-18/38_series/38884/72dc35c6c075018909676f36a0a98af1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25f72a799195138aa922c17031f907d5859cd18f --- /dev/null +++ b/marked/Rel-18/38_series/38884/72dc35c6c075018909676f36a0a98af1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b56a5a379bc5460ff3bb27f04973f08ce473e1e8e84014cf0ab246148ce7e2ee +size 26926 diff --git a/marked/Rel-18/38_series/38884/771c18f874d31c59c3b8c4e247be16ca_img.jpg b/marked/Rel-18/38_series/38884/771c18f874d31c59c3b8c4e247be16ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e54cbc93f32037cf061180d054c58868b050fe6a --- /dev/null +++ b/marked/Rel-18/38_series/38884/771c18f874d31c59c3b8c4e247be16ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c051cbda95f629a62c7405d552555b4481361ad510351c5f2cf4fc2fee63755b +size 40220 diff --git a/marked/Rel-18/38_series/38884/79607caa47ed192b11a2c7b17f0b88dd_img.jpg b/marked/Rel-18/38_series/38884/79607caa47ed192b11a2c7b17f0b88dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c12ad34878e55c6ed4183c676dd7433767778c6 --- /dev/null +++ b/marked/Rel-18/38_series/38884/79607caa47ed192b11a2c7b17f0b88dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aec0cf0b5c01e2c433f737ad659b45979a0f229e14e1e4279d02387958fe2151 +size 16876 diff --git a/marked/Rel-18/38_series/38884/7a4a00f53376de68707bb8a27b211f02_img.jpg b/marked/Rel-18/38_series/38884/7a4a00f53376de68707bb8a27b211f02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34b78c6df9b713a2f55cf7566f62e2809e5a9f16 --- /dev/null +++ b/marked/Rel-18/38_series/38884/7a4a00f53376de68707bb8a27b211f02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:456445142bbb10dac73508be2a6ab612fa5b65955fe01554f0fc96d2e925e7cd +size 55339 diff --git a/marked/Rel-18/38_series/38884/7c0a9511fa02b6c2c125ff5be465186e_img.jpg b/marked/Rel-18/38_series/38884/7c0a9511fa02b6c2c125ff5be465186e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0cc63965d61435168a6abdad4fbc8e402234c3a --- /dev/null +++ b/marked/Rel-18/38_series/38884/7c0a9511fa02b6c2c125ff5be465186e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bbff98fc195d2c90391791953f8a5523f90d085a52fbe6cf8a5dd80f70086ed +size 96559 diff --git a/marked/Rel-18/38_series/38884/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/marked/Rel-18/38_series/38884/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0114aafda42d925a473f98d5efd2e473e2c611cf --- /dev/null +++ b/marked/Rel-18/38_series/38884/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5aa71739a7c9ef8ffbcf179b6e41580a13c3b90adf477ad1e5804a1612ce9aac +size 16434 diff --git a/marked/Rel-18/38_series/38884/810c7bd381c13911f72d22587ad08606_img.jpg b/marked/Rel-18/38_series/38884/810c7bd381c13911f72d22587ad08606_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b192548064faadaa16c42d035ffe9f6ad4843a87 --- /dev/null +++ b/marked/Rel-18/38_series/38884/810c7bd381c13911f72d22587ad08606_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb4bb9c6405f2933b34eaa9781ebea323b1e74121b9e35977260cbdc917f03d0 +size 52160 diff --git a/marked/Rel-18/38_series/38884/81f54eb0ad0c7dfc557a7e3b22bb025b_img.jpg b/marked/Rel-18/38_series/38884/81f54eb0ad0c7dfc557a7e3b22bb025b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5928e1f69478e5b4e8c071f94c9d5b3370241154 --- /dev/null +++ b/marked/Rel-18/38_series/38884/81f54eb0ad0c7dfc557a7e3b22bb025b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2584bf77dd2b7b3123db41df56b059c9e840c863c63f36cd63c518ae46553929 +size 35566 diff --git a/marked/Rel-18/38_series/38884/8f8caebe58364416a2eda21039d8c7bf_img.jpg b/marked/Rel-18/38_series/38884/8f8caebe58364416a2eda21039d8c7bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a25ff5e4104ff0fbddb9dc7a6da264479e281d1 --- /dev/null +++ b/marked/Rel-18/38_series/38884/8f8caebe58364416a2eda21039d8c7bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:354f91b46871f309567d90c3bd3850780efc42e84ac229448896a0cb28d9b097 +size 50161 diff --git a/marked/Rel-18/38_series/38884/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-18/38_series/38884/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6fcd04c9fccad60b341950b0fb935a7ff46a8fa --- /dev/null +++ b/marked/Rel-18/38_series/38884/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c15d2c509f61b95fe70abda3f0b9c77d892aa28932be0377a8764076ef510b43 +size 29375 diff --git a/marked/Rel-18/38_series/38884/9058545957858eea01975496aa340d5b_img.jpg b/marked/Rel-18/38_series/38884/9058545957858eea01975496aa340d5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55b5776e02017df2d42e13bbc81610a6d58dd78a --- /dev/null +++ b/marked/Rel-18/38_series/38884/9058545957858eea01975496aa340d5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:450f2148eeaa99b8f720be3255f091909c2720df60049ffab5d714552eb3e160 +size 31238 diff --git a/marked/Rel-18/38_series/38884/930335a43c8196e391f87e6860db4d45_img.jpg b/marked/Rel-18/38_series/38884/930335a43c8196e391f87e6860db4d45_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f15677a1b6eed009af1b7260bb4db0224b9a494 --- /dev/null +++ b/marked/Rel-18/38_series/38884/930335a43c8196e391f87e6860db4d45_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8a117936951aa48e151786a594ecb71683a16468d933ca54c785504fd0ec4a5 +size 25586 diff --git a/marked/Rel-18/38_series/38884/939b79420df0cf962959ccef56f3371f_img.jpg b/marked/Rel-18/38_series/38884/939b79420df0cf962959ccef56f3371f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e383ad866bbf8872eb04d0141b6c01535342534c --- /dev/null +++ b/marked/Rel-18/38_series/38884/939b79420df0cf962959ccef56f3371f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79de2cf09f75503f28bb116a6d97dd1a821fb6c1751532804dbf90d24837c7d2 +size 136581 diff --git a/marked/Rel-18/38_series/38884/9600eb9b09749d5b8a30898a75407ac8_img.jpg b/marked/Rel-18/38_series/38884/9600eb9b09749d5b8a30898a75407ac8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61841b2f9c911e82b1707893ea1c3786455b0dfe --- /dev/null +++ b/marked/Rel-18/38_series/38884/9600eb9b09749d5b8a30898a75407ac8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1bec4c95b6867dbc3ad3dce7840bea1b30a64d8e83cc1774a2a99d34394502c +size 38999 diff --git a/marked/Rel-18/38_series/38884/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-18/38_series/38884/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30593826c3dbfeac7027dfbae1ab5a9af8d58de7 --- /dev/null +++ b/marked/Rel-18/38_series/38884/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc2a143401357011a18ab8fc8606942075603d1449be4f7bfb6501f31a26a8c7 +size 75958 diff --git a/marked/Rel-18/38_series/38884/a1849005b1686d3991afbbb3970f623d_img.jpg b/marked/Rel-18/38_series/38884/a1849005b1686d3991afbbb3970f623d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23e1264ce56368b8e3c730de2393e8c4d905046b --- /dev/null +++ b/marked/Rel-18/38_series/38884/a1849005b1686d3991afbbb3970f623d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56a9cc20558b14ef9707e0dea679fdd68ef22675e91616fbfc63fd5e52bedfc5 +size 67088 diff --git a/marked/Rel-18/38_series/38884/a2c9fe78d22304889baddc26f4329ddf_img.jpg b/marked/Rel-18/38_series/38884/a2c9fe78d22304889baddc26f4329ddf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bceee2733ebebf36d7363ae50487c8be86b085a --- /dev/null +++ b/marked/Rel-18/38_series/38884/a2c9fe78d22304889baddc26f4329ddf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba64d34c81eec0d7dd687ac490897ba030c7b3058d9c0d433f52fbe58ee7b5b9 +size 22881 diff --git a/marked/Rel-18/38_series/38884/a4cee18a14f569dd8b88c5e5f9d43b48_img.jpg b/marked/Rel-18/38_series/38884/a4cee18a14f569dd8b88c5e5f9d43b48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eafe3d2ba7427061dafd2af64a08ae9018308c69 --- /dev/null +++ b/marked/Rel-18/38_series/38884/a4cee18a14f569dd8b88c5e5f9d43b48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:218bec76832568f95b6192f5d4467dc9aa1a31152d5b7e18ba03f42448099647 +size 5386 diff --git a/marked/Rel-18/38_series/38884/a734898ce18e972938949637c32a34f4_img.jpg b/marked/Rel-18/38_series/38884/a734898ce18e972938949637c32a34f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9027e7b936618163c55eb7393ca856f08f01d932 --- /dev/null +++ b/marked/Rel-18/38_series/38884/a734898ce18e972938949637c32a34f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:159b5c89dd9b694111c94da1260993869caa5dec39a8d49ba121d5f63bca516b +size 16220 diff --git a/marked/Rel-18/38_series/38884/b104cf622ef88c0bb857ecb3f0816d87_img.jpg b/marked/Rel-18/38_series/38884/b104cf622ef88c0bb857ecb3f0816d87_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c31f8c15baeed2cfdd764ea27b71de9b2d1ecd24 --- /dev/null +++ b/marked/Rel-18/38_series/38884/b104cf622ef88c0bb857ecb3f0816d87_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ee73464414bcac3f6471d7061ff7b766fbc1532aae8c0dbf98658366bf933bf +size 33962 diff --git a/marked/Rel-18/38_series/38884/b47f393ea2c781f313367435c7166abb_img.jpg b/marked/Rel-18/38_series/38884/b47f393ea2c781f313367435c7166abb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36b7bb924a4cc49948263b21080e58e0db7afeb9 --- /dev/null +++ b/marked/Rel-18/38_series/38884/b47f393ea2c781f313367435c7166abb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8477b7176bf821f71790dfc949a1b781ee0101840bfeb837c4f4ed96ed274c68 +size 70555 diff --git a/marked/Rel-18/38_series/38884/b800051c57e75b44155683ea69ed4227_img.jpg b/marked/Rel-18/38_series/38884/b800051c57e75b44155683ea69ed4227_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b2935975a6a12e338cb97f411a8dfae9dbf670c --- /dev/null +++ b/marked/Rel-18/38_series/38884/b800051c57e75b44155683ea69ed4227_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c87ddb54d8827d44272f765d97a3d09f04512688345768d6a52a042ead8b5d75 +size 44849 diff --git a/marked/Rel-18/38_series/38884/bb908297bfe73e2759a9dd88ae0506f9_img.jpg b/marked/Rel-18/38_series/38884/bb908297bfe73e2759a9dd88ae0506f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d9c19813167867caaccb02da718bbb34aef5cc2 --- /dev/null +++ b/marked/Rel-18/38_series/38884/bb908297bfe73e2759a9dd88ae0506f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e39f45968f63e9f8b5a44e1930404b6590cc035bc90c46e3fd4853b4db9383b2 +size 41918 diff --git a/marked/Rel-18/38_series/38884/bc9fe6d1f3411f724ddf3b8c11a37f7e_img.jpg b/marked/Rel-18/38_series/38884/bc9fe6d1f3411f724ddf3b8c11a37f7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0c00618af7509fccc5d03259c57e2a07d5105bc --- /dev/null +++ b/marked/Rel-18/38_series/38884/bc9fe6d1f3411f724ddf3b8c11a37f7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab1690f2591b91f9a016278358d7547e8694a1b22b17308618b83ce4d348fb5e +size 37090 diff --git a/marked/Rel-18/38_series/38884/bd361bbf5003c5df0416591de03a4522_img.jpg b/marked/Rel-18/38_series/38884/bd361bbf5003c5df0416591de03a4522_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ffa5da6f745e70e910b9be8e51a3a3b8d936d7b --- /dev/null +++ b/marked/Rel-18/38_series/38884/bd361bbf5003c5df0416591de03a4522_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ed5a36b9016d5b3be1e1e87759899bda3894ee23f32e11bd7c78ff5ac49a142 +size 71408 diff --git a/marked/Rel-18/38_series/38884/bf30e154f82662d212f21fccdfa2980f_img.jpg b/marked/Rel-18/38_series/38884/bf30e154f82662d212f21fccdfa2980f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa875cee9cdc4a1db8912e91a9cce622ef60bea8 --- /dev/null +++ b/marked/Rel-18/38_series/38884/bf30e154f82662d212f21fccdfa2980f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acd46fd94793bed7a4b674f46b2f7adafe61f87502f9f0518160c5284807d8d1 +size 94511 diff --git a/marked/Rel-18/38_series/38884/c2e6ba8cdf072f7f5934f8e90664be1b_img.jpg b/marked/Rel-18/38_series/38884/c2e6ba8cdf072f7f5934f8e90664be1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42aed22b52e3dcf4e441005a931ee9c149512f55 --- /dev/null +++ b/marked/Rel-18/38_series/38884/c2e6ba8cdf072f7f5934f8e90664be1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b96bd35a71fbb4a2861c32b691267c683624940bff55ca858eda1a9edfdad24 +size 46802 diff --git a/marked/Rel-18/38_series/38884/c53adc66eab40abd5f8b9107d950ad04_img.jpg b/marked/Rel-18/38_series/38884/c53adc66eab40abd5f8b9107d950ad04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..352d6bf7df23c5013cae6a41921497d41abd512c --- /dev/null +++ b/marked/Rel-18/38_series/38884/c53adc66eab40abd5f8b9107d950ad04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e931b2d47ac09c78ff0289de30196782fa0408aa39ed4f4837378ebe35dfa2ba +size 37669 diff --git a/marked/Rel-18/38_series/38884/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg b/marked/Rel-18/38_series/38884/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0fb330c831b533bf99de39e84498bf557ba4f3e1 --- /dev/null +++ b/marked/Rel-18/38_series/38884/c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34e742c31d10d4a02fa8ed3434eeb4aa4458bead4a22b231761e79932da60306 +size 106162 diff --git a/marked/Rel-18/38_series/38884/c8d2bc5b813f5d46408a32185a56a7b1_img.jpg b/marked/Rel-18/38_series/38884/c8d2bc5b813f5d46408a32185a56a7b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70ccd139ee2055c053b673e4b97cbb44dc1dd717 --- /dev/null +++ b/marked/Rel-18/38_series/38884/c8d2bc5b813f5d46408a32185a56a7b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02a7cca900ff980279001412dc5bb8a3743d9f6a2cbe1198617b64c667758654 +size 73346 diff --git a/marked/Rel-18/38_series/38884/cb6c5456549559ce70a9a8cb0680a880_img.jpg b/marked/Rel-18/38_series/38884/cb6c5456549559ce70a9a8cb0680a880_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3de58eefe87872481938b8b005d6ebb98ea36f68 --- /dev/null +++ b/marked/Rel-18/38_series/38884/cb6c5456549559ce70a9a8cb0680a880_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5df1636b36da76ec19c90ccf3f7faee5dabfa1be708ec7ec4810b760851f3da6 +size 29792 diff --git a/marked/Rel-18/38_series/38884/cc777601b892d144a2c0b69f56ef03bf_img.jpg b/marked/Rel-18/38_series/38884/cc777601b892d144a2c0b69f56ef03bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db7c62451fe3c05c9afbca8a241f5b3c5a4ca701 --- /dev/null +++ b/marked/Rel-18/38_series/38884/cc777601b892d144a2c0b69f56ef03bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c14947ffa3284d89b78932fd72e128efbc4a97fe3e30e87d1bf22d8e342c9e36 +size 14103 diff --git a/marked/Rel-18/38_series/38884/cfc852835f2d91bea8dc074568937e22_img.jpg b/marked/Rel-18/38_series/38884/cfc852835f2d91bea8dc074568937e22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a07011e01aaf74718788328caca2097d6db81be9 --- /dev/null +++ b/marked/Rel-18/38_series/38884/cfc852835f2d91bea8dc074568937e22_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82dd207a913f51f74f28283bd33ab03f71ab716245bd45e60b4b04dd3fa65418 +size 84446 diff --git a/marked/Rel-18/38_series/38884/d2417b04116c354deccb25d98a84a0fb_img.jpg b/marked/Rel-18/38_series/38884/d2417b04116c354deccb25d98a84a0fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d29c3884d18cf5eabccaefc722acc3cc58d44f1 --- /dev/null +++ b/marked/Rel-18/38_series/38884/d2417b04116c354deccb25d98a84a0fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3d59ad53683ace94f88ea483fc47dbe8d49116bb9dc0b92e136b2887516ebe5 +size 20311 diff --git a/marked/Rel-18/38_series/38884/da82c28f91abb7e03beec3535b711ab7_img.jpg b/marked/Rel-18/38_series/38884/da82c28f91abb7e03beec3535b711ab7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2241a89995b0948a598219a990e1ac6db57af1f --- /dev/null +++ b/marked/Rel-18/38_series/38884/da82c28f91abb7e03beec3535b711ab7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bb156b12f09d4306e086a0fba91e85b2ed5adf303ccc86ad7ffa4faafd668a8 +size 70424 diff --git a/marked/Rel-18/38_series/38884/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-18/38_series/38884/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ef4815b6bd8284136607bee0690779141ad06e2 --- /dev/null +++ b/marked/Rel-18/38_series/38884/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e2527cc1da5a151dcce26ff81111c2139d41918a279294b2b5a48d702617887 +size 90346 diff --git a/marked/Rel-18/38_series/38884/ddc89e164666201115a1c006e4c3b6da_img.jpg b/marked/Rel-18/38_series/38884/ddc89e164666201115a1c006e4c3b6da_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..341b2d9a1e633050c1c4b3bd2b37b49517c46f45 --- /dev/null +++ b/marked/Rel-18/38_series/38884/ddc89e164666201115a1c006e4c3b6da_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3c02464be37d296565e1eefe43ceb02996947567c5bc2291694e5e24da3afd8 +size 87656 diff --git a/marked/Rel-18/38_series/38884/de6b883a4ffcab8046e199c0bfd72d84_img.jpg b/marked/Rel-18/38_series/38884/de6b883a4ffcab8046e199c0bfd72d84_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..074e7317d6e6534da1cdb1c347e716b98e7c2cfa --- /dev/null +++ b/marked/Rel-18/38_series/38884/de6b883a4ffcab8046e199c0bfd72d84_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56ac618d371ce37978c1e75c52214a79a3812021edb3af4fda4c5b03eba02f8f +size 38533 diff --git a/marked/Rel-18/38_series/38884/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-18/38_series/38884/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e6db6ff31579b2e2c9e0456ad7854835a72107e --- /dev/null +++ b/marked/Rel-18/38_series/38884/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d18fe64c9553e8300751e4e743c646c07521aa8178945799e20fb84bdbece324 +size 42863 diff --git a/marked/Rel-18/38_series/38884/e2a6d00ef953ffef831511e534394a27_img.jpg b/marked/Rel-18/38_series/38884/e2a6d00ef953ffef831511e534394a27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d38fcc29852377427ce1bcf3d87da8646660eff1 --- /dev/null +++ b/marked/Rel-18/38_series/38884/e2a6d00ef953ffef831511e534394a27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:941634abeaa177198f484b163b99cf4605ee59671c9f87a709390b7949e59496 +size 40242 diff --git a/marked/Rel-18/38_series/38884/e342f16f418dd3a8bf8fcec8a55b752c_img.jpg b/marked/Rel-18/38_series/38884/e342f16f418dd3a8bf8fcec8a55b752c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35aa92c39c1f64f7f55caa32eb785a6f05ba09be --- /dev/null +++ b/marked/Rel-18/38_series/38884/e342f16f418dd3a8bf8fcec8a55b752c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7dd98683050ce75dda7db5d5d80713e82ec4bfd237b0d39798c7af23c7c4202 +size 29165 diff --git a/marked/Rel-18/38_series/38884/e487aa3d0a4f904f2d04785ee0c6c474_img.jpg b/marked/Rel-18/38_series/38884/e487aa3d0a4f904f2d04785ee0c6c474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6976a8f869af3cbded1059a5c2add7f75b294237 --- /dev/null +++ b/marked/Rel-18/38_series/38884/e487aa3d0a4f904f2d04785ee0c6c474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b187b2623c489b01331b890e718cbb9cee8a64e261ff73bc22bef164fc8e470 +size 45465 diff --git a/marked/Rel-18/38_series/38884/e51925aa86bb1cd1ea891dbb493caa4f_img.jpg b/marked/Rel-18/38_series/38884/e51925aa86bb1cd1ea891dbb493caa4f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..affe344375614c1af5dc80d1818650c792365b83 --- /dev/null +++ b/marked/Rel-18/38_series/38884/e51925aa86bb1cd1ea891dbb493caa4f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a88a153d69a732d01d7c75e6c26dad09ce8b3926aac137c0d76f56f063e25d8 +size 76112 diff --git a/marked/Rel-18/38_series/38884/e7d6aacb9818a209033d6d8d7b99c8d9_img.jpg b/marked/Rel-18/38_series/38884/e7d6aacb9818a209033d6d8d7b99c8d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..372cdda107c6a91f71d3af2b4bc4de85187ba10f --- /dev/null +++ b/marked/Rel-18/38_series/38884/e7d6aacb9818a209033d6d8d7b99c8d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d179fddce1ad35a2dc95a7ba53c9c9c4ab54da6d02349a3399073d89965774b +size 32910 diff --git a/marked/Rel-18/38_series/38884/e84de38c2eac283d770e2c8acdf64308_img.jpg b/marked/Rel-18/38_series/38884/e84de38c2eac283d770e2c8acdf64308_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec4ce9501d3014b16c01ece070abb9901d870a3b --- /dev/null +++ b/marked/Rel-18/38_series/38884/e84de38c2eac283d770e2c8acdf64308_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5b340d31c387ff4994e7aad7fe6281675d46d0fd820d3ecf86e6b608085f333 +size 38153 diff --git a/marked/Rel-18/38_series/38884/eecfb45aacdf80575bc7c1c6228ef6c4_img.jpg b/marked/Rel-18/38_series/38884/eecfb45aacdf80575bc7c1c6228ef6c4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90c90eb5cb5e933b9ceb127e300c05d9b77377c1 --- /dev/null +++ b/marked/Rel-18/38_series/38884/eecfb45aacdf80575bc7c1c6228ef6c4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8b1aad3db54af1e1206c6bee05b5258d1a537cebd5cd854f835eadbab0d0837 +size 38345 diff --git a/marked/Rel-18/38_series/38884/f29504cb9770aad6c8c696acad49adff_img.jpg b/marked/Rel-18/38_series/38884/f29504cb9770aad6c8c696acad49adff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0f34953d04d29a52da13e6ff20b6f4ba71653b5 --- /dev/null +++ b/marked/Rel-18/38_series/38884/f29504cb9770aad6c8c696acad49adff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4e92e3880fb28163fe7a8cfd146d85e396e2b46132d4bb899a5e26db04d533f +size 51534 diff --git a/marked/Rel-18/38_series/38884/f455955c4bc84005728b4138f19098dc_img.jpg b/marked/Rel-18/38_series/38884/f455955c4bc84005728b4138f19098dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e60c63dd6c0964f0fb7e5014f734a0e80194b78 --- /dev/null +++ b/marked/Rel-18/38_series/38884/f455955c4bc84005728b4138f19098dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:334d71e0b5383d91e8bbbb91b5ac205548ee159df83cb3fe15572eeeb4a695e2 +size 108894 diff --git a/marked/Rel-18/38_series/38884/f9625fa3465b009051f85d91cfa1da7e_img.jpg b/marked/Rel-18/38_series/38884/f9625fa3465b009051f85d91cfa1da7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a85b02098faf894ffc0da81afe5aa3660a6e660 --- /dev/null +++ b/marked/Rel-18/38_series/38884/f9625fa3465b009051f85d91cfa1da7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b8384889f7aa48b134aba5db9041082bac0c0baeff99621c5ae8c3ce66cd67b +size 103178 diff --git a/marked/Rel-18/38_series/38884/f9d11004ac6966f27936c8d01e579313_img.jpg b/marked/Rel-18/38_series/38884/f9d11004ac6966f27936c8d01e579313_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13dab7c86e782c38858c8141cb05425aed3ebe0d --- /dev/null +++ b/marked/Rel-18/38_series/38884/f9d11004ac6966f27936c8d01e579313_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b0d1afd626b258b7f7d107e50f748f44f7f6de9ed4ea082bef1c4716e4cb52a +size 46121 diff --git a/marked/Rel-18/38_series/38884/fe236a7cb4bf9aaf4a61a04f700b0e7e_img.jpg b/marked/Rel-18/38_series/38884/fe236a7cb4bf9aaf4a61a04f700b0e7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4cd363cd21b34efeafc4606b7be8c4d3fd663df9 --- /dev/null +++ b/marked/Rel-18/38_series/38884/fe236a7cb4bf9aaf4a61a04f700b0e7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed8817aed855895ddf00d93117ee70b31b846def58db1fd5361ac84900ddb410 +size 33140 diff --git a/marked/Rel-18/38_series/38884/fed351d1b7c4568a439a8682c27f8cc3_img.jpg b/marked/Rel-18/38_series/38884/fed351d1b7c4568a439a8682c27f8cc3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81d27855f21a323f7d07381d8f7a726ed632bed1 --- /dev/null +++ b/marked/Rel-18/38_series/38884/fed351d1b7c4568a439a8682c27f8cc3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e21111571b9cdc4cbb91f70586b4253dc586a050e2e978b113b10d8cf72e73a +size 42439 diff --git a/marked/Rel-18/38_series/38884/raw.md b/marked/Rel-18/38_series/38884/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..03a9f1e58ac4d238bcadc0bcc587a0203e4e13f6 --- /dev/null +++ b/marked/Rel-18/38_series/38884/raw.md @@ -0,0 +1,4361 @@ + + +# **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Study on enhanced test methods for FR2 NR UEs; (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' in smaller 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. + +© 2022, 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..... | 9 | +| 3 Definitions of terms, symbols and abbreviations..... | 10 | +| 3.1 Terms..... | 10 | +| 3.2 Symbols..... | 10 | +| 3.3 Abbreviations..... | 10 | +| 4 General..... | 12 | +| 5 UE RF testing methodology enhancements..... | 13 | +| 5.1 High DL power and low UL power..... | 13 | +| 5.1.1 General..... | 13 | +| 5.1.2 Beam management sensitivity study of NF based solutions..... | 14 | +| 5.1.2.1 Simulation assumptions..... | 14 | +| 5.1.2.2 Simulation results..... | 15 | +| 5.1.3 Manufacturer declarations..... | 17 | +| 5.1.4 Permitted Methodologies: CFFNF, CFFDNF and CFFdeltaNF..... | 24 | +| 5.1.4.1 Asymptotic Expansion Approach for CFFNF..... | 26 | +| 5.1.4.2 Test Procedures for CFFDNF, CFFNF and CFFdeltaNF..... | 28 | +| 5.1.4.3 Simulation Assumptions..... | 34 | +| 5.1.4.4 Simulation results for CFFDNF..... | 35 | +| 5.1.4.5 Simulation results for CFFNF (using Black & White-Box Approach)..... | 52 | +| 5.1.4.6 Simulation results for CFFNF (using Black-Box Approach)..... | 54 | +| 5.1.4.7 Simulation results for sensitivity of CFFNF to relative measurement uncertainties..... | 58 | +| 5.1.4.8 Simulation results for CFFdeltaNF..... | 59 | +| 5.1.4.9 Simulation results for Influence of Noise..... | 75 | +| 5.1.4.10 Simulation Results for offset error MU..... | 78 | +| 5.1.5 Applicability of NF methodologies..... | 80 | +| 5.1.6 Improvement of permitted methods..... | 83 | +| 5.2 Polarization basis mismatch between the TE and DUT..... | 84 | +| 5.2.1 General..... | 84 | +| 5.2.2 Enhanced test method for EIRP measurement..... | 85 | +| 5.2.2.1 TPMI method..... | 85 | +| 5.2.2.2 Applicability of TPMI side condition method..... | 85 | +| 5.2.2.3 Alternative test method..... | 86 | +| 5.2.3 Enhanced test method for UL demodulation measurement..... | 86 | +| 5.2.3.1 Test equipment Zero-forcing MIMO receiver..... | 86 | +| 5.2.3.1.1 Method 1..... | 86 | +| 5.2.3.1.1.1 Method 1 description..... | 86 | +| 5.2.3.1.1.2 Method 1 MIMO Equalization..... | 88 | +| 5.2.3.1.1.3 Method 1 Maximum Ratio Combining..... | 88 | +| 5.2.3.1.1.4 Method 1 Layer processing..... | 89 | +| 5.2.3.1.2 Method 2..... | 89 | +| 5.2.3.1.2.1 Method 2 description..... | 89 | +| 5.2.3.1.2.2 Method 2 MIMO Equalization..... | 90 | +| 5.2.3.1.2.3 Method 2 Maximal Ratio Combining..... | 91 | +| 5.2.3.1.2.4 Method 2 EVM equalizer flatness..... | 92 | +| 5.2.3.1.2.5 Method 2 channel invertibility considerations..... | 92 | +| 5.2.3.1.2.6 Method 2 DC (LO) cancellation..... | 93 | +| 5.2.3.1.3 Analysis of Method 1 & 2..... | 94 | +| 5.2.3.1.3.1 Comparison of both Methods..... | 94 | +| 5.2.3.1.3.2 Conclusion 96 | 96 | +| 5.3 Inter-band (FR2+FR2) CA..... | 96 | +| 5.3.1 General..... | 96 | +| 5.3.2 Impact of multiple test antennae..... | 97 | + +| | | | +|-----------|-------------------------------------------------------------------------------------|-----| +| 5.3.2.1 | PSD imbalance with DL signals from test equipment..... | 97 | +| 5.3.2.1.1 | DL PSD towards UE supporting independent beam management (IBM)..... | 97 | +| 5.3.2.1.2 | DL PSD towards UE supporting common beam management (CBM)..... | 98 | +| 5.3.2.2 | Impact of off-focus test system antennae..... | 100 | +| 5.3.2.2.1 | Quality of quiet zone (QoQZ)..... | 100 | +| 5.3.2.2.2 | Rx beam profiles with an independent beam management (IBM) UE..... | 106 | +| 5.3.2.2.3 | Propensity to trigger incorrect beam in CBM UE..... | 107 | +| 5.3.2.2.4 | Spherical coverage measurement simulation with common beam management (CBM) UE..... | 108 | +| 5.3.2.3 | Summary on applicability of offset antenna test system..... | 110 | +| 5.3.2.4 | Points to design the FR2 OTA test system with offset test antennae..... | 110 | +| 5.3.3 | Inter-band testing ramifications..... | 111 | +| 5.3.3.1 | Single antenna..... | 112 | +| 5.3.3.2 | Multiple antennae..... | 112 | +| 5.4 | Extreme temperature conditions..... | 112 | +| 5.4.1 | ETC test system..... | 112 | +| 5.4.2 | Calibration procedure..... | 113 | +| 5.4.3 | Test procedure..... | 113 | +| 5.4.4 | Temperature tolerance limit of ETC test system..... | 113 | +| 5.5 | Extension of frequency applicability for band n262..... | 114 | +| 5.6 | Extension of frequency applicability for FR2-2..... | 114 | +| 5.6.1 | Permitted test methods..... | 114 | +| 5.6.2 | Enhanced test methods..... | 114 | +| 5.6.2.1 | High DL power and low UL power..... | 114 | +| 5.6.2.2 | Polarization basis mismatch between the TE and DUT..... | 115 | +| 5.6.2.3 | Inter-band (FR2+FR2) CA..... | 115 | +| 5.6.2.4 | Extreme temperature conditions..... | 115 | +| 5.6.2.5 | Test time reduction..... | 115 | +| 6 | UE RRM testing methodology enhancements..... | 116 | +| 6.1 | Extension of frequency applicability for band n262..... | 116 | +| 6.2 | Extension of frequency applicability for FR2-2..... | 116 | +| 6.2.1 | General..... | 116 | +| 6.2.2 | Noc methodology..... | 116 | +| 6.2.3 | Maximum SNR derivation..... | 116 | +| 7 | UE demodulation testing methodology enhancements..... | 118 | +| 7.1 | Extension of frequency applicability for band n262..... | 118 | +| 7.2 | Extension of frequency applicability for FR2-2..... | 119 | +| 7.2.1 | General..... | 119 | +| 7.2.2 | Noc methodology..... | 119 | +| 7.2.3 | Maximum SNR derivation..... | 120 | +| 8 | Test time reduction..... | 123 | +| 8.1 | General..... | 123 | +| 8.2 | New measurement grid..... | 123 | +| 8.2.1 | New measurement grids based on 4x2 antenna pattern assumption..... | 123 | +| 8.2.1.1 | Beam Peak Search Measurement Grid..... | 124 | +| 8.2.1.2 | Spherical Coverage Measurement Grid..... | 126 | +| 8.2.1.3 | TRP Measurement Grid..... | 127 | +| 8.2.2 | Applicability of the 4x2 measurement grids..... | 130 | +| 8.3 | RSRP(B) based RX beam peak search..... | 131 | +| 8.3.1 | Test procedure..... | 131 | +| 8.3.2 | RSRP(B) accuracy..... | 131 | +| 8.4 | Single link polarization measurement..... | 131 | +| 8.4.1 | Test procedure..... | 131 | +| 8.4.2 | Applicability of Single link polarization measurement..... | 132 | +| 8.5 | Other methods..... | 133 | +| 8.5.1 | Fast Spherical Coverage Method..... | 133 | +| 8.5.1.1 | General..... | 133 | +| 8.5.1.2 | Tx Fast Spherical Coverage Method..... | 133 | +| 8.5.1.3 | Rx Fast Spherical Coverage Method..... | 134 | +| 8.5.2 | Non-Uniform TRP Measurement Grids..... | 135 | + +| | | | +|---------------------------------------------------|-------------------------------------------------------------------|------------| +| 9 | Propagation conditions..... | 137 | +| 9.1 | Extension of frequency applicability for FR2-2..... | 137 | +| Annex A: Environment conditions..... | | 139 | +| A.1 | Operating voltage..... | 139 | +| A.2 | Temperature..... | 139 | +| Annex B: Measurement uncertainty..... | | 140 | +| B.1 | Measurement uncertainty budget for UE RF testing methodology..... | 140 | +| B.1.1 | High DL power and low UL power..... | 140 | +| B.1.1.1 | Uncertainty Contributions..... | 140 | +| B.1.1.2 | Uncertainty Contributions descriptions..... | 143 | +| B.1.1.2.1 | DUT antenna location estimation..... | 143 | +| B.1.1.2.2 | Probe antenna pattern..... | 143 | +| B.1.1.2.3 | EIRP measurement error in NF ..... | 144 | +| B.1.1.2.4 | TRP measurement error in NF ..... | 144 | +| B.1.1.2.5 | Near-field interaction between probe antenna and DUT antenna..... | 144 | +| B.1.1.2.6 | Influence of power measurement uncertainty..... | 144 | +| B.1.1.2.7 | Influence of noise..... | 144 | +| B.1.1.3 | Uncertainty assessment..... | 144 | +| B.1.2 | Polarization basis mismatch between the TE and DUT..... | 145 | +| B.1.3 | Inter-band (FR2+FR2) CA..... | 145 | +| B.1.4 | Test system for ETC..... | 145 | +| B.1.5 | Measurement uncertainty budget for FR2-2 test methods..... | 146 | +| Annex C (informative): Change history..... | | 147 | + +# 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 objectives of this study are to enhance the FR2 RF testing methodology and to quantify the impact of the enhancements on the UE performance, as related to the polarization basis mismatch between the test equipment and UE and to add support for testing under extreme temperature conditions. + +The development of testing methodology enhancements proceeds within the following scope: + +- In general + - Target the testing and calibration aspects of the permitted methods for FR2 UE RF testing and the preliminary assessment of measurement uncertainty (Clause 5.2 and Annex B of TR38.810) + - The test methodologies and procedures shall be applicable for different device types and power classes with DUT size defined in the TR 38.810. Prioritize the study to PC3 for aspects related to DUT size, and limit the study to free space conditions + - The study item outcomes shall capture the efficacy of the enhancements + - Objectives related to regulatory test cases shall be prioritized + +The detailed objectives are: + +1. Define test methodology for high DL power and low UL power test cases + - Considering path loss reduction, measurement antenna gain improvement, DUT positioning improvement, and MU improvement + - Considering NFTF (defined in Clause 5.2 of TR38.810) and direct near field test methodologies as possible alternative methods + - Other approaches are not precluded + - Study preliminary assessment of measurement uncertainty of new alternative methods +2. Define solutions to minimize the impact of polarization basis mismatch between the TE and DUT on the RF testing + - Considering polarization basis mismatch between the test equipment and UE and UE implementations which may be impacted by this mismatch + - Study EIS test metric which can apply to different UE RF implementations considering downlink polarization sweep enhancement + - Limit the study of this objective to the permitted UE RF methods defined in Clause 5.2 of TR38.810 + - Possible enhancements may be described as + - Downlink polarization sweeping by the test equipment (i.e. introducing an additional degree of freedom for polarization alignment of the measurement antenna) + - The use of circular polarization to perform measurements + - Coherent combining and demodulation of orthogonally polarized received signals in the test equipment + - Uplink polarization sweeping by the test equipment to search for the optimal polarization angle to receive and demodulate the signal transmitted by the UE + - Considering NFTF (defined in Clause 5.2 of TR38.810) test methodology for EIS measurement + - TPMI side condition method, where TPMI side conditions are applicable to Rel-16 (and higher) UEs + - Test mode to trigger TX diversity + - Other approaches are not precluded + +3. Study testability enhancements to support the verification of RF requirements for inter-band (FR2+FR2) CA + - Work on inter-band DL CA is prioritized + - Whether the test setup shall be restricted to emulating the signal from the same direction for the aggregated bands shall be aligned with the UE RF architecture assumption taken in the work item on NR RF Requirement Enhancements for FR2 [UID 830189] +4. Support extreme temperature conditions for all applicable FR2 UE RF test cases + - Considering beam peak search, spherical coverage, and total radiated power procedures + - Limit the study of this objective to the permitted UE RF methods defined in Clause 5.2 of TR38.810 + - Study preliminary impacts on system measurement uncertainty under extreme temperature conditions +5. Study testability enhancements to reduce test time + - Including RF test method enhancement with reduced test time, and possible test time saving approach for UE Demodulation test and RRM test +6. Study testability aspects for the introduction of the new band n262 + - Considering the extension of frequency applicability of the permitted methods in TR38.810 from 43.5 GHz up to at least 48.2 GHz + - Considering the extension of frequency applicability of the test methodology enhancements in Objectives 1 through 5 above + +# --- 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.101-2: "User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone". + - [3] 3GPP TR 38.810: "NR; Study on test methods". + - [4] 3GPP TS 38.211: "NR; Physical channels and modulation". + - [5] 3GPP TS 38.212: "NR; Multiplexing and channel coding". + - [6] 3GPP TS 38.521-2: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 2: Range 2 Standalone". + - [7] 3GPP TR 38.903: " Derivation of test tolerances and measurement uncertainty for User Equipment (UE) conformance test cases". + - [8] L. Anttila, A. Brihuega, M. Valkama. On Antenna Array Out-of-Band Emissions, IEEE Wireless Communications Letters, Dec 2019 + +- [9] H. Li, X. Li, C. Wei, The analysis of the performance of multi-beamforming in memory nonlinear power amplifier, EURASIP Journal on Advances in Signal Processing, 2014 +- [10] 3GPP TS 38.508-1: "5GS; User Equipment (UE) conformance specification; Part 1: Common test environment". +- ... +- [x] <#>[ ([up to and including]{yyyy[-mm]}|V)[onwards]]: "". + +# 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]. + +| | | +|--------|----------------------------------------------------| +| AoA | Angle of Arrival | +| BP | Beam Peak | +| CA | Carrier Aggregation | +| CBW | Channel Bandwidth | +| CFFNF | Combined Far-Field/Near-Field | +| CFFDNF | Combined Far-Field/Direct-Near-Field | +| DFF | Direct Far Field | +| DNF | Direct Near Field | +| DUT | Device Under Test | +| EIS | Effective Isotropic Sensitivity | +| EIRP | Effective (or equivalent) isotropic radiated power | +| EPRE | Energy per resource element | +| ETC | Extreme Temperature Condition | +| EVM | Error Vector Magnitude | +| FF | Far-Field | +| FR1 | Frequency Range 1 | +| FR2 | Frequency Range 2 | +| FS | Free Space | +| IBM | Independent Beam Management | +| IFF | Indirect Far Field | +| MU | Measurement Uncertainty | +| NF | Near-Field | +| NFTF | Near Field to Far-field | +| NSA | Non-standalone | +| OTA | Over The Air | +| QZ | Quiet Zone | +| RSRP | Reference signal receive power | +| SNR | Signal-to-Noise Ratio | +| SS | System Simulator | + +| | | +|----------|-----------------------------------------------| +| SS-RSRPB | SS reference signal received power per branch | +| TRP | Total Radiated Power | +| UBF | UE beam lock function | +| UE | User Equipment | + +# --- 4 General + +The enhanced test methods defined in the following clauses are not only applicable to current release, the general applicability can be categorized as following: + +1. If a test case or requirement was not-testable in an older Release (e.g. Rel-15), and a new test method or procedure unblocks it in Rel-17, then the method can be said to be release-independent and would apply to the older release. +2. If we call one of the enhanced test methodologies as a Rel-17 test equipment feature, then a test equipment setup implementing the earlier release conformance test specification should be allowed to bring in a Rel-17 feature, provided that it meets all of the applicable Rel-17 requirements for that feature. +3. When there is a core requirement change (or modification/relaxation) in, e.g. Rel-17, to enable testing/unblock testability issues, then the requirement change should be applicable only from Rel-17 onwards. +4. When the enhanced test methodology applies to a UE feature supported only from a specific release, the test method becomes applicable only from that release onwards. + +# 5 UE RF testing methodology enhancements + +## 5.1 High DL power and low UL power + +### 5.1.1 General + +The investigation of high DL power and low UL power enhancements to the FR2 test methodology includes the following aspects: scope of test cases with high DL power and low UL power issues, enhanced test systems, including the investigation of non-permitted systems, enhancements to permitted methods, manufacturer declarations, beam management sensitivity of the DUT in near-field test system environments, and path loss comparison across system types. + +Table 5.1.1-1 below provides a summary of the test cases and testability issues. + +**Table 5.1.1-1: Summary of test cases and testability issues** + +| Clause | Requirement | Testability issue | Test Metric | +|---------|---------------------------------------|-------------------|------------------------------------------------------| +| 6.3.1 | Minimum output power | Low UL power | EIRP (Link=TX beam peak direction, Meas=Link angle). | +| 6.3.2 | Transmit OFF power | Low UL power | TRP (Link=TX beam peak direction, Meas=TRP grid) | +| 6.5.1 | Occupied bandwidth | Low UL power | OBW (Link=TX beam peak direction, Meas=Link angle) | +| 6.5.2.3 | Adjacent channel leakage ratio | Low UL power | TRP (Link=TX beam peak direction, Meas=TRP grid). | +| 6.5.3.2 | Additional spurious emissions | Low UL power | TRP (Link=TX beam peak direction, Meas=TRP grid). | +| 7.4 | Maximum input power | High DL power | EIS (Link=RX beam peak direction, Meas=Link angle). | +| 7.5 | Adjacent channel selectivity (case 1) | High DL power | EIS (Link=RX beam peak direction, Meas=Link angle) | +| 7.5 | Adjacent channel selectivity (case 2) | High DL power | EIS (Link=RX beam peak direction, Meas=Link angle) | +| 7.6.2 | In-band blocking | High DL power | EIS (Link=RX beam peak direction, Meas=Link angle) | +| 7.9 | Receiver spurious emissions | Low UL power | TRP (Link=TX beam peak direction, Meas=TRP grid). | + +The investigation of test methodology enhancements to strive to reduce the testability issues which were identified includes study of the feasibility of enhancing test systems which are permitted in TR38.810 [3] as well as test systems which are not permitted. Non-permitted test systems according to TR38.810 [3] are not required to verify all requirements in TS38.101-2 [2]. The candidate test systems are limited to near-field (NF) based solutions and include the following solutions: + +- The Direct near-field (DNF) system assumes that all measurements and call setups are performed with a measurement probe in the NF of the DUT. +- The Combined far-field/near-field (CFFNF) system utilizing a transform-based approach assumes that the UE beamlock function (UBF) activation is performed towards the FF beam peak direction based on the far-field method and then test case procedures are performed with measurement probe(s) in the NF of the DUT. +- Combined far-field/direct-near-field (CFFDNF) system assumes that the UE beamlock function (UBF) activation is performed towards the FF beam peak direction based on the far-field method and then test case procedures are performed based on the direct near-field method. +- Combined far-field/delta-near-field (CFFdeltaNF) system utilizing a relative measurement approach assumes that the UE beamlock function (UBF) activation is performed towards the FF beam peak direction based on the far-field method, a reference test case without testability issues is performed both in FF and NF to obtain the relative correction factor, and the final test case procedure are performed in the NF and compensated with the relative correction factor. + +The applicability of these NF methodologies is further outlined in Clause 5.1.4. + +### 5.1.2 Beam management sensitivity study of NF based solutions + +#### 5.1.2.1 Simulation assumptions + +For NF based solutions, where beam peak search is necessary to perform all applicable test case procedures, an evaluation of UE beam management sensitivity to magnitude/phase variation of the DL signal is needed. Two assumptions are made about the NF based system: + +- Beam peak search is performed in the NF (i.e. DNF system); OR +- Beam peak search is first performed in the FF/IFF and test case is executed in the NF (i.e. CFFNF system). + +Using the spherical coverage measurement grid assumptions shown in Table 5.1.2.1-1, evaluations were performed of the UE beam management sensitivity in terms of simulated radiated performance metrics for each of the assumptions. + +**Table 5.1.2.1-1: Beam management sensitivity simulation assumptions** + +| Parameter | Value | Notes | +|----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------| +| Spherical coverage Measurement Grids baseline assumption | Annex G.1.1 in TR38.810 | | +| Antenna array | - 8x2 and 4x1<br>- Antenna element HPBW: {260/130, 90/90} deg | Element near-field assumption is implementation specific | +| Simulated DUT | Two antenna arrays are integrated in the UE for the spherical coverage analyses<br>- Antenna panels are studied with $N_z \times N_y$ with $N_z > N_y$ , e.g., 8x2 corresponds to $N_z = 8$ and $N_y = 2$<br>- The implementation loss for the antenna near the front is 0dB less than that for the antenna near the back<br>- The antenna in the back is on the opposite side of the UE (mirrored around (0,0,0)). | See Figure 5.1.2.1-1 for example positions of two antenna arrays | +| Beam steering | - In the xy plane, assume 45° beam steering granularity (AZ from -45° to +45°)<br>- In the xz plane, assume 22.5° beam steering granularity (EL from -90° to 90°) | | +| Offsets | - Various antenna offsets (yoffset, zoffset) beyond 7.5cm in radius (12.5cm max)<br>- For TRP analysis, model random antenna offsets anywhere within the 30cm spherical QZ | Offset is defined with respect to the center of antenna array | +| Range Lengths | - 30cm, 20m (more range lengths are not precluded)<br>- Goal is to eventually determine min. range length and MU for performing spherical coverage tests in DNF | Defined as distance between centre of QZ/positioning axes and measurement probe | +| Test methodology | - CFFDNF/DNF (while taking path loss offsets into account)<br>- CFFNF | | +| Sampling grid | Study finer than 7.5deg step size for constant-step size grids | Parametric studies to show convergence for the selected assumption | + +Figure 5.1.2.1-1 below illustrates example positions of two antenna arrays in the simulated DUT. + +![Diagram illustrating the simulated DUT antenna assumptions for beam management sensitivity study. The diagram shows two views of a User Equipment (UE) model. The left view is a front/side perspective showing a 'Front' antenna array (green rectangle) and a 'Back' antenna array (green rectangle). A coordinate system (x, y, z) is shown, with the z-axis pointing up. The 'z_offset' is the vertical distance from the top of the UE to the center of the front antenna array. The 'y_offset' is the horizontal distance from the top edge of the UE to the center of the front antenna array. The right view is a top-down perspective showing the 'Back' antenna array (green rectangle) and a small black rectangle representing the UE's top edge.](0e240e8e4783e664047fbdb5fbd0989f_img.jpg) + +Diagram illustrating the simulated DUT antenna assumptions for beam management sensitivity study. The diagram shows two views of a User Equipment (UE) model. The left view is a front/side perspective showing a 'Front' antenna array (green rectangle) and a 'Back' antenna array (green rectangle). A coordinate system (x, y, z) is shown, with the z-axis pointing up. The 'z\_offset' is the vertical distance from the top of the UE to the center of the front antenna array. The 'y\_offset' is the horizontal distance from the top edge of the UE to the center of the front antenna array. The right view is a top-down perspective showing the 'Back' antenna array (green rectangle) and a small black rectangle representing the UE's top edge. + +Illustration of the two antenna arrays integrated in the UE, for Rel-17 simulation + +**Figure 5.1.2.1-1: Simulated DUT antenna assumptions for beam management sensitivity study** + +#### 5.1.2.2 Simulation results + +Table 5.1.2.2-1 below summarizes the results from simulations of beam management sensitivity of a DNF system (i.e. beam peak search is performed in the NF). + +**Table 5.1.2.2-1: Beam management sensitivity results of a DNF system** + +| Company label | Swept parameters | Beam management performance maximum $\Delta$ relative to reference (dB) | | | Notes | +|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|--------------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Beam peak | 50% CDF | TRP | | +| Company A | Array: 8x2<br>Range: {0.2, 0.4, 0.8} m<br>Offset: {0, 0.05, 0.10} m<br>HPBW: {90/90} | 2.5 | Not analysed | Not analysed | There is approximately 2.5 dB of BP error when range length is reduced to 0.2m in presence of the module offset mentioned above. There is also significant perturbation of the CDF curve. CDF statistics start to converge when the range length is at least 4 times the offset. | +| Company B | Array: 8x2, 4x1<br>Range: {0.25, 0.3, 0.45, 20} m<br>Offset: {0.125 in y, 0.125 in z, 0.09 in y & z} m<br>HPBW: {260/130} | 7.0 | 1.0 | TRP analysed separately | The EIRP beam peak (100%-ile EIRP) and direction cannot be measured accurately with the direct NF methodology | +| Company B | Array: 8x2<br>Range: 0.2 m<br>Offset: 0.15 m in x, y, z<br>HPBW: {260/130} | | | 0.66 dB systematic<br>0.46 dB RSS'ed | Large uncertainties can be observed for TRP for measurements performed in the NF utilizing the black back box approach | +| Company C | Array: 4x1<br>Range: {100, 4.2, 0.9, 0.45, 0.3} m<br>Offsets: not specified<br>Full phone model (including the PCB and phone house) has been considered | 0.3 | 0 | Not clear whether 0.1 or 0.4 | Figure of merits such as EIRP, TRP, and Spherical Coverage are not influenced dramatically from range length | +| Company B | Array: {4x1, 8x2}<br>Range: 0.25 m<br>Offset: {0, 0.125, 0.9} m in y, z<br>HPBW: {90/90} | 4.2 | | | UE selected different beam between NF beam peak direction and FF beam peak direction | +| Company B | Array: {4x1, 8x2}<br>Range: 0.25 m<br>Offset: {0, 0.53, 0.75} m in x, y, z<br>HPBW: {90/90} | 10.4 | | | UE select the same beam in the NF as in the FF more often, we still see concerning trends with the peak EIRP deltas | +| Company B | Reuse assumptions used by Company A:<br>Array: 8x2<br>Range: {0.2, 0.4, 0.8} m<br>Offset: {0, 0.05, 0.10} m<br>HPBW: {90/90} | 2.5 | 1.2 | | Simulations were performed to establish alignment with another company | + +Table 5.1.2.2-2 below summarizes the results from simulations of beam management sensitivity of a CFFNF system (i.e. beam peak search is first performed in the FF/IFF and test case is executed in the NF). + +**Table 5.1.2.2-2: Beam management sensitivity results of a CFFNF system** + +| Company and reference | Swept parameters | Beam management performance maximum $\Delta$ relative to reference (dB) | | | Notes | +|---------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|--------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Beam peak | 50% CDF | TRP | | +| Company B (“Black box with transform approach”) | Array: 8x2, 4x1<br>Range: {0.22 – 0.30} m<br>Offset: {0, 0.50, 0.10, 0.125} m | Max $\mu$ = 0.2<br>Max $\sigma$ = 0.3 | Not analysed | Not analysed | These results were obtained using a transform-based approach to correct the incurred path loss. Feedback from industry is requested whether to continue efforts in terms of simulations and empirical investigations on this enhanced NF methodology with transform utilizing black-box approach | +| Company B (“Black & White box with transform approach”) | Array: 8x2, 4x1<br>Range: {0.22 – 0.30} m<br>Offset: {0, 0.50, 0.10, 0.125} m | Max $\mu$ = 0.1<br>Max $\sigma$ = 0.3 | Not analysed | TRP analysed separately | These results were obtained using a transform-based approach to correct the incurred path loss. Feedback from industry is requested whether to continue efforts in terms of simulations and empirical investigations on this enhanced NF methodology with transform utilizing the white&black-box approach | +| Company B (“TRP with compensation for antenna offset”) | Array: 8x2<br>Range: 0.2 m<br>Offset: 0.15 m in x, y, z<br><br>HPBW: {260/130} | | | 0.02 dB systematic<br>0.21 dB RSS'ed | These results were obtained using the DNF methodology with declared offset; alternatively, these results could be obtained using a transform based approach to estimate the phase centre offset. With the offset of the antenna array known, e.g., estimated with the enhanced NF methodology introduced in this contribution, very accurate TRP measurements in the NF can be made with a TRP offset compensation approach | +| Company C | Array: 4x1<br>Range: {100, 4.2, 0.9, 0.45, 0.3} m<br>Offsets: not specified<br><br>Full phone model (including the PCB and phone house) has been considered | 0.3 | 1.0 | 0.8 | These results were obtained using the DNF methodology. Figure of merits such as EIRP, TRP, and Spherical Coverage are not influenced dramatically from range length<br><br>Full phone model (including the PCB and phone house) has been considered | + +### 5.1.3 Manufacturer declarations + +If a manufacturer declaration is used to inform or optimize a test system parameter, and the DUT is positioned in the test system according to parameters which are informed by this declaration, then the DUT is measured assuming a “white box” configuration. If no manufacturer declaration is used, and the DUT is positioned in the test system according to common procedures, then the DUT is measured assuming a “black box” configuration. + +Black box testing requires no knowledge which antenna panel is active at any given time and the detailed location of the active panel within the DUT. In this test configuration, the geometric centre of the DUT is aligned with the centre of the quiet zone as illustrated in Figure 5.1.3-1. + +![Figure 5.1.3-1: Illustration of black box approach. Two diagrams show a Device Under Test (DUT) centered at the center of a quiet zone (QZ). In the left diagram, a red antenna panel on the left side of the DUT is active, with a red beam pointing left. In the right diagram, a green antenna panel on the right side of the DUT is active, with a green beam pointing right. Both diagrams include a dashed circle representing the QZ and yellow curved arrows indicating rotation.](fed351d1b7c4568a439a8682c27f8cc3_img.jpg) + +Figure 5.1.3-1: Illustration of black box approach. Two diagrams show a Device Under Test (DUT) centered at the center of a quiet zone (QZ). In the left diagram, a red antenna panel on the left side of the DUT is active, with a red beam pointing left. In the right diagram, a green antenna panel on the right side of the DUT is active, with a green beam pointing right. Both diagrams include a dashed circle representing the QZ and yellow curved arrows indicating rotation. + +**Figure 5.1.3-1: Illustration of black box approach** + +White box testing on the other hand requires the manufacturer declaration of detailed locations of all antenna panels and which antenna panel is active in any UL/DL test direction. In this test configuration, the centre of the radiating aperture (of the active panel) is aligned with the centre of the quiet zone as illustrated in Figure 5.1.3-2. + +![Figure 5.1.3-2: Illustration of white box approach. Two diagrams show a DUT centered at the center of a quiet zone (QZ). In the left diagram, a red antenna panel on the left side of the DUT is active, with a red beam pointing left. The center of the radiating aperture of this panel is labeled 'A2 centred at centre of quiet zone'. In the right diagram, a green antenna panel on the right side of the DUT is active, with a green beam pointing right. The center of the radiating aperture of this panel is labeled 'A1 centred at centre of quiet zone'. Both diagrams include a dashed circle representing the QZ and yellow curved arrows indicating rotation.](06eef9cc3970450903c158ec25346d21_img.jpg) + +Figure 5.1.3-2: Illustration of white box approach. Two diagrams show a DUT centered at the center of a quiet zone (QZ). In the left diagram, a red antenna panel on the left side of the DUT is active, with a red beam pointing left. The center of the radiating aperture of this panel is labeled 'A2 centred at centre of quiet zone'. In the right diagram, a green antenna panel on the right side of the DUT is active, with a green beam pointing right. The center of the radiating aperture of this panel is labeled 'A1 centred at centre of quiet zone'. Both diagrams include a dashed circle representing the QZ and yellow curved arrows indicating rotation. + +**Figure 5.1.3-2: Illustration of white box approach** + +The black&white-box approach combines the advantages of both the black and white-box approaches where the antenna phase centre offset(s) are declared, i.e., white-box approach, but the geometric centre of the DUT is aligned with the centre of the QZ, i.e., black-box approach. + +The following paragraphs provide further information on the need for the various vendor declarations with the help of sample illustrations. Here, a DUT with three antenna panels is considered shown schematically in Figure 5.1.3-3 on the left. The right side shows coverage sectors and the corresponding antenna panels the DUT would select if the DL was presented from within those sectors. In this example, the red antenna panel would yield the TX beam peak in the horizontal direction; this direction would be identified following the TX beam peak search. For simplicity, most of the arguments in the next few paragraphs are applied to testing in the FF but they can be applied to testing in the NF as well. + +![Figure 5.1.3-3: Illustration of Sample DUT with three antenna panels. The diagram shows a square DUT with three antenna panels on its right side, each emitting a beam (red, blue, and purple). A red oval labeled 'TX BP' is positioned to the right of the top panel. A large black arrow labeled 'Coverage Map' points to the right, where the beams are shown overlapping and forming a coverage map.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +The diagram illustrates a square Device Under Test (DUT) with three antenna panels on its right side. Each panel is represented by a small grid of yellow squares. The top panel emits a red beam, the middle panel emits a blue beam, and the bottom panel emits a purple beam. A red oval labeled 'TX BP' is positioned to the right of the top panel. A large black arrow labeled 'Coverage Map' points to the right, where the beams are shown overlapping and forming a coverage map. + +Figure 5.1.3-3: Illustration of Sample DUT with three antenna panels. The diagram shows a square DUT with three antenna panels on its right side, each emitting a beam (red, blue, and purple). A red oval labeled 'TX BP' is positioned to the right of the top panel. A large black arrow labeled 'Coverage Map' points to the right, where the beams are shown overlapping and forming a coverage map. + +**Figure 5.1.3-3: Illustration of Sample DUT with three antenna panels** + +The beam peak search or spherical coverage test case of the DUT utilizing the black-box approach, i.e., none of the antenna offsets are known/declared, is illustrated in Figure 5.1.3-4. Here, the geometric centre of the DUT is aligned with the centre of the QZ (yellow circle). The (green) beam peak search grid points sample the EIRP around the DUT. + +![Figure 5.1.3-4: Illustration of beam peak search of sample DUT utilizing black-box approach. The diagram shows the DUT from Figure 5.1.3-3 centered within a large grey circle. A yellow circle at the center of the DUT represents the QZ. Twelve green dots are arranged in a circular grid around the DUT, representing beam peak search grid points.](a734898ce18e972938949637c32a34f4_img.jpg) + +The diagram shows the DUT from Figure 5.1.3-3 centered within a large grey circle. A yellow circle at the center of the DUT represents the QZ. Twelve green dots are arranged in a circular grid around the DUT, representing beam peak search grid points. + +Figure 5.1.3-4: Illustration of beam peak search of sample DUT utilizing black-box approach. The diagram shows the DUT from Figure 5.1.3-3 centered within a large grey circle. A yellow circle at the center of the DUT represents the QZ. Twelve green dots are arranged in a circular grid around the DUT, representing beam peak search grid points. + +**Figure 5.1.3-4: Illustration of beam peak search of sample DUT utilizing black-box approach.** + +Test cases without a 3D scan, e.g., EIRP/EIS test case towards the known TX/RX beam peak direction, utilizing the black-box approach are illustrated in Figure 5.1.3-5. Here, the geometric centre of the DUT is aligned with the centre of the QZ (yellow circle) and the TX beam peak direction is known from a previous beam peak search measurement, e.g., from an IFF system. Hence, the single (green) FF grid point is aligned with the FF TX beam peak direction. + +![Figure 5.1.3-5: Illustration of beam peak search of sample DUT utilizing black-box approach. The diagram shows the DUT from Figure 5.1.3-3 centered within a large grey circle. A yellow circle at the center of the DUT represents the QZ. A single green dot is positioned on the right side of the DUT, aligned with the TX BP direction. A red oval labeled 'TX BP' is positioned to the right of the top panel.](04f51626e2e10a16e3eb2c4b33cb2742_img.jpg) + +The diagram shows the DUT from Figure 5.1.3-3 centered within a large grey circle. A yellow circle at the center of the DUT represents the QZ. A single green dot is positioned on the right side of the DUT, aligned with the TX BP direction. A red oval labeled 'TX BP' is positioned to the right of the top panel. + +Figure 5.1.3-5: Illustration of beam peak search of sample DUT utilizing black-box approach. The diagram shows the DUT from Figure 5.1.3-3 centered within a large grey circle. A yellow circle at the center of the DUT represents the QZ. A single green dot is positioned on the right side of the DUT, aligned with the TX BP direction. A red oval labeled 'TX BP' is positioned to the right of the top panel. + +**Figure 5.1.3-5: Illustration low UL power test case along TX BP direction of sample DUT utilizing black-box approach.** + +For the white-box measurement approach, the level of information provided in vendor declarations largely depends on the purpose of test case coverage. If the white-box approach is leveraged for all conformance test cases including the beam peak searches, the total number of panels and the phase centre offsets of each panel need to be declared. Additionally, vendors would have to declare which antenna panel is active for each grid point or test sectors so that the respective antenna panel is aligned with the centre of the QZ during testing. This approach is further illustrated in Figure 5.1.3-6. To sample EIRPs on all beam peak search grid points, three different device positions have to be applied, i.e., for the angular range covering the + +- red grid points (declared by OEM), the red antenna panel (location declared by OEM) has to be aligned with the centre of QZ (yellow circle) +- purple grid points (declared by OEM), the purple antenna panel (location declared by OEM) has to be aligned with the centre of QZ (yellow circle) +- blue grid points (declared by OEM), the blue antenna panel (location declared by OEM) has to be aligned with the centre of QZ (yellow circle) + +![Figure 5.1.3-6: Illustration of beam peak search of sample DUT utilizing white-box approach. The figure shows three circular diagrams representing different device positions. Each diagram contains a central yellow circle (QZ) and several colored grid points (red, green, purple, blue) around it. A rectangular box represents the DUT, with a colored wedge (red, purple, or blue) indicating the active antenna panel. The wedges are aligned with the grid points to ensure the antenna panel is centered on the QZ during testing.](72dc35c6c075018909676f36a0a98af1_img.jpg) + +Figure 5.1.3-6: Illustration of beam peak search of sample DUT utilizing white-box approach. The figure shows three circular diagrams representing different device positions. Each diagram contains a central yellow circle (QZ) and several colored grid points (red, green, purple, blue) around it. A rectangular box represents the DUT, with a colored wedge (red, purple, or blue) indicating the active antenna panel. The wedges are aligned with the grid points to ensure the antenna panel is centered on the QZ during testing. + +**Figure 5.1.3-6: Illustration of beam peak search of sample DUT utilizing white-box approach.** + +In summary, the information that would have to be declared by the OEMs if the white-box approach is utilized for all conformance test cases is tabulated in Table 5.1.3-1. + +**Table 5.1.3-1: Sample Vendor Declaration for white box approach supporting all conformance test cases** + +| Number of Antenna Panels in DUT | # | | +|---------------------------------|--------------------------------------------------|--------------------------------------------------------------------------------------| +| Antenna Panel # | Phase-centre offset from geometric centre of DUT | Range of Angles covered by Antenna Panel | +| 1 | $(X_{off1}, Y_{off1}, Z_{off1})$ | $(\theta_{start1} \text{ to } \theta_{end1}, \phi_{start1} \text{ to } \phi_{end1})$ | +| 2 | $(X_{off2}, Y_{off2}, Z_{off2})$ | $(\theta_{start2} \text{ to } \theta_{end2}, \phi_{start2} \text{ to } \phi_{end2})$ | +| ... | ... | ... | +| N | $(X_{offN}, Y_{offN}, Z_{offN})$ | $(\theta_{startN} \text{ to } \theta_{endN}, \phi_{startN} \text{ to } \phi_{endN})$ | + +Assuming the enhanced test methodology needs to perform beam peak searches and a white box approach was selected, the DUT should be measured in several positions inside the test volume, where two options could be considered: + +- DUT is placed manually in the corresponding off-center positions. This will likely result in significant test time increase and additional MU due to inaccuracies in the alignment of the DUT. +- x-y-z positioning systems are needed to fully automate testing based on the knowledge of which antenna panel is active in any given UL/DL test direction, as outlined in Figure 5.1.3-6. This will in effect likely result in significant signal ripple and near field coupling effects which is expected to degrade the quality of QZ MU which could offset the offset MU a white box approach eliminates. Such positioning system will furthermore increase test system complexity from a SW and HW perspective as well as test time. + +Test cases without a 3D scan, e.g., EIRP/EIS test case towards the known TX/RX beam peak direction, utilizing the white-box approach is illustrated in Figure 5.1.3-7. Here, the phase centre of the red panel (yielding beam peak radiation) of the DUT is aligned with the centre of the QZ (yellow circle) and the TX beam peak direction is known from a previous beam peak search measurement; thus the single (green) grid point is aligned with the FF TX beam peak direction. In this case, only the location of the one antenna panel that yields the beam peak radiation would have to be declared. A sample declaration is shown in Table 5.1.3-2. + +![Figure 5.1.3-7: Illustration of low UL power test case along TX BP direction of sample DUT utilizing white-box approach. The diagram shows a circular test area with a central DUT model. A red arrow labeled 'TX BP' points from the DUT to a green circle on the right, indicating the beam peak direction. A yellow circle is also visible, representing the phase centre of the antenna panel.](cc777601b892d144a2c0b69f56ef03bf_img.jpg) + +Figure 5.1.3-7: Illustration of low UL power test case along TX BP direction of sample DUT utilizing white-box approach. The diagram shows a circular test area with a central DUT model. A red arrow labeled 'TX BP' points from the DUT to a green circle on the right, indicating the beam peak direction. A yellow circle is also visible, representing the phase centre of the antenna panel. + +**Figure 5.1.3-7: Illustration of low UL power test case along TX BP direction of sample DUT utilizing white-box approach.** + +**Table 5.1.3-2: Sample Vendor Declaration for white-box approach supporting low UL power test cases** + +| Antenna Panel (yielding TX beam peak radiation) | Phase-centre offset from geometric centre of DUT | +|-------------------------------------------------|----------------------------------------------------| +| | $(X_{\text{off}}, Y_{\text{off}}, Z_{\text{off}})$ | + +Two different black&white-box approaches could be further considered, i.e., + +- Extensive Black&white-box approach: When the NF methodology is used for spherical coverage test cases and for beam peak searches, all active antenna locations are declared together with the angular ranges (theta, phi) each active antenna performs best (when compared to the remaining antenna panels, i.e., the vendor declaration is as outlined in Table 5.1.3-1. Very much similar to the white-box approach with the only difference that the geometric centre of DUT is aligned with the centre of QZ. +- Black&white box: When the NF methodology is used only for EIS based high DL power or EIRP/TRP based low UL power test cases, only the antenna location of the antenna that yields the beam peak needs to be declared, i.e., the vendor declaration is as outlined in Table 5.1.3-2. The geometric centre of DUT is aligned with the centre of QZ. + +For test cases focused only on the for EIS based high DL power or EIRP/TRP based low UL power test cases, the key differences are illustrated in Figure 5.1.3-8 for the black-box approach (left), black&white-box approach (centre), and the white-box approach (right). While the black-box approach requires local searches to determine the NF test direction, the need for local searches for the black&white-box approach is FFS. No local search is necessary for the white-box approach. + +For the spherical coverage test cases or the beam peak searches, the extensive black&white-box approach is further outlined in Figure 5.1.3-9. On the other hand, the black-box approach is outlined in Figure 5.1.3-4 while the white-box approach is outlined in Figure 5.1.3-6. + +![Figure 5.1.3-8: Illustration of three antenna testing approaches: Black Box, Black&White Box, and White Box. Each approach shows a device with a beam pattern (blue, red, purple) and a transmit beam peak (TX BP) indicated by a red oval. The Black Box approach shows the TX BP as a known value from previous measurements. The Black&White Box approach shows the TX BP as a declared offset of the antenna panel. The White Box approach shows the TX BP as a result of the measurement. A green dot indicates the center of the quiet zone (QZ).](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +Black Box                      Black&White Box                      White Box + +TX BP                      TX BP                      TX BP + +Declared Offset of Antenna Panel yielding TX BP + +TX BP KNOWN FROM PREVIOUS MEASUREMENTS + +• Center of QZ + +Figure 5.1.3-8: Illustration of three antenna testing approaches: Black Box, Black&White Box, and White Box. Each approach shows a device with a beam pattern (blue, red, purple) and a transmit beam peak (TX BP) indicated by a red oval. The Black Box approach shows the TX BP as a known value from previous measurements. The Black&White Box approach shows the TX BP as a declared offset of the antenna panel. The White Box approach shows the TX BP as a result of the measurement. A green dot indicates the center of the quiet zone (QZ). + +**Figure 5.1.3-8: Illustration of black-box approach (left), black&white-box approach (centre), and the white-box approach (right) for the low-UL power test case.** + +![Figure 5.1.3-9: Illustration of beam peak search or beam peak search of sample DUT utilizing extensive black&white-box approach. The diagram shows a device with a beam pattern (blue, red, purple) and a transmit beam peak (TX BP) indicated by a red oval. The device is surrounded by a circular array of 8 probes (4 red, 4 blue) for beam peak search. A green dot indicates the center of the quiet zone (QZ).](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +Figure 5.1.3-9: Illustration of beam peak search or beam peak search of sample DUT utilizing extensive black&white-box approach. The diagram shows a device with a beam pattern (blue, red, purple) and a transmit beam peak (TX BP) indicated by a red oval. The device is surrounded by a circular array of 8 probes (4 red, 4 blue) for beam peak search. A green dot indicates the center of the quiet zone (QZ). + +**Figure 5.1.3-9: Illustration of beam peak search or beam peak search of sample DUT utilizing extensive black&white-box approach** + +For white box testing, the minimum radius of the NF probe antenna from the centre of the quiet zone generally must exceed the maximum diameter of the device, as illustrated in Figure 5.1.3-10, to prevent interference of the near field scanning probe with the DUT. While this requirement of the NF range length having to exceed the maximum diameter of the DUT is generally applicable to TRP where the NF Probe antenna needs to perform a full 3D scan around the DUT, this could very well be applicable to single-directional measurements as well, as illustrated in Figure 5.1.3-10 using a PC1 CPE as an example. Similar restrictions apply when testing using ETC enclosures surrounding the DUT. + +![Figure 5.1.3-10: Illustration of min. Range length of NF Systems when applying white box testing.](a2c9fe78d22304889baddc26f4329ddf_img.jpg) + +This diagram illustrates the minimum range length for Near Field (NF) systems using white box testing. It features a large circle representing the test area. Inside, a rectangular device is shown with a red oval representing its beam. Two green shapes represent the NF probe. One probe, labeled 'NF Probe (Beam Peak)', is positioned at the top of the circle, with a yellow double-headed arrow indicating its movement. The other probe, labeled 'NF Probe (TRP Scan)', is positioned at the bottom left of the circle, also with a yellow double-headed arrow indicating its movement. The device has a small green rectangle on its top right corner. + +Figure 5.1.3-10: Illustration of min. Range length of NF Systems when applying white box testing. + +Figure 5.1.3-10: Illustration of min. Range length of NF Systems when applying white box testing + +![Figure 5.1.3-11: Illustration of min. Range length for NF Systems using PC1 CPE as example.](26070f41b834cefd33d293fecdba9868_img.jpg) + +This diagram illustrates the minimum range length for NF systems using PC1 CPE as an example. It features a large circle representing the test area. Inside, a rectangular device is shown with a red oval representing its beam. A green shape representing the NF probe is positioned at the top right of the circle, with a yellow double-headed arrow indicating its movement. The device has a small green rectangle on its top right corner. The diagram also includes a smaller inset showing a 3D view of the device and its beam. + +Figure 5.1.3-11: Illustration of min. Range length for NF Systems using PC1 CPE as example. + +Figure 5.1.3-11: Illustration of min. Range length for NF Systems using PC1 CPE as example. + +The corresponding FF and NF min. range lengths are tabulated for selected FR2 frequencies in Table 5.1.3-3 for PC3 devices with fixed $D=5\text{cm}$ . + +**Table 5.1.3-3: Minimum FF and NF Range Lengths for black box and white box conditions for PC3 devices** + +| f [GHz] | Antenna Config. 1 and 2<br>- BLACK BOX -<br>(PC3 Devices: D=5cm) | | Antenna Config. 1 and 2<br>- WHITE BOX -<br>(PC3 Devices: D=5cm) | | +|---------|------------------------------------------------------------------|--------------------------|------------------------------------------------------------------|--------------------------| +| | Min. FF Range Length [m] | Min. NF Range Length [m] | Min. FF Range Length [m] | Min. NF Range Length [m] | +| 24.25 | 0.53 | 0.19 | 0.40 | 0.28 | +| 30 | 0.63 | 0.19 | 0.50 | 0.28 | +| 40 | 0.79 | 0.21 | 0.67 | 0.28 | +| 43.5 | 0.85 | 0.21 | 0.73 | 0.28 | +| 52.6 | 1.00 | 0.22 | 0.88 | 0.28 | + +Table 5.1.3-4 summarizes the path loss comparison between “white box” and “black box” configuration across IFF/DFF and NF system types. + +**Table 5.1.3-4: Path loss comparison between “white box” and “black box” configuration** + +| f (GHz) | Antenna Config. 1, 2, and 3<br>- BLACK BOX -<br>(PC3 Devices: D=5cm) | | Antenna Config. 1 and 2<br>- WHITE BOX -<br>(PC3 Devices: D=5cm) | | +|---------|----------------------------------------------------------------------|-----------------------------------|------------------------------------------------------------------|-----------------------------------| +| | IFF/DFF | NF | DFF | NF | +| | Path Loss with 1m range length | Path Loss with 0.22m range length | Path Loss with 0.88m range length | Path Loss with 0.28m range length | +| 24.25 | 60.16 | 46.86 | 59.01 | 48.93 | +| 30 | 62.01 | 48.71 | 60.85 | 50.78 | +| 40 | 64.51 | 51.21 | 63.35 | 53.28 | +| 43.5 | 65.24 | 51.94 | 64.08 | 54.00 | +| 52.6 | 66.89 | 53.59 | 65.73 | 55.65 | + +Based on the analysis shown in Table 5.1.3-4, it can be concluded that a “white box” is not deemed a feasible enhancement of the methodology. + +Additionally, since the beam peak searches and the spherical coverage test cases are not part of the low UL/high DL power test cases and given the complexity of the vendor declaration of the extensive black&white-box approach, it can be concluded that the extensive black&white-box approach is not deemed a feasible enhancement of the methodology. + +### 5.1.4 Permitted Methodologies: CFFNF, CFFDNF and CFFdeltaNF + +Both methodologies have in common that a FF probe, e.g., reflector & feed probe from the IFF methodology, is used for the test cases that are not considered low UL power/high DL power. This FF probe is used for the low UL/high DL power test cases to steer and lock the beam in the known FF direction before the NF measurements are performed with a NF probe that exhibits much lower free-space path losses. An example test setup of such a hybrid system is shown in Figure 5.1.4-1. + +The main differences between the three measurement approaches are outlined in Table 5.1.4-1. + +**Table 5.1.4-1: Main differences between CFFDNF and CFFNF measurement approaches** + +| ► Methodology ►<br>▼ Test Approach ▼ | CFFDNF | CFFNF | CFFdeltaNF | +|------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| Black Box | N/A (Note 1) | Wide local search at initial radius $r_1$ , narrow local searches at radii $r_2, r_3$ , i.e., multiple NF measurements at $r_1, r_2$ , and $r_3$ | Local search at fixed radius, reference measurement at FF and NF to obtain the relative correction factor, single NF measurement | +| Black&white-box | Single NF measurement or local search at $r_1$ | Single NF measurements at $r_1$ , and $r_2$ | N/A | +| Note 1: This can be revised whenever empirical methods to determine the offset location or other methods are shown feasible. | | | | + +![Figure 5.1.4-1: Hybrid NF/(I)FF test setup suitable for NF measurements. The diagram shows a 3D perspective view of a Device Under Test (DUT) mounted on a turntable. A probe antenna is positioned to measure the DUT. Coordinate axes X (red), Y (green), and Z (blue) are shown. The DUT is emitting a beam, represented by a red shaded area. The probe antenna is shown in two positions: one for Near Field (NF) measurement and one for Far Field (FF) measurement. The NF measurement is performed at a closer distance, while the FF measurement is performed at a larger distance. The diagram illustrates the hybrid setup for NF measurements.](810c7bd381c13911f72d22587ad08606_img.jpg) + +Figure 5.1.4-1: Hybrid NF/(I)FF test setup suitable for NF measurements. The diagram shows a 3D perspective view of a Device Under Test (DUT) mounted on a turntable. A probe antenna is positioned to measure the DUT. Coordinate axes X (red), Y (green), and Z (blue) are shown. The DUT is emitting a beam, represented by a red shaded area. The probe antenna is shown in two positions: one for Near Field (NF) measurement and one for Far Field (FF) measurement. The NF measurement is performed at a closer distance, while the FF measurement is performed at a larger distance. The diagram illustrates the hybrid setup for NF measurements. + +**Figure 5.1.4-1: Hybrid NF/(I)FF test setup suitable for NF measurements** + +In a NF system, the NF beam peak direction for an offset antenna is not necessarily the same as the FF beam peak direction; however, the knowledge of the antenna phase centre offset, i.e., black&white-box approach, can be leveraged to measure at the NF beam peak direction as illustrated in 5.1.4-2. The knowledge of the offset together with the probe antenna pattern will allow the calculation of the optimized DUT orientation to optimize the NF measurement. The beam peak direction in the NF can either be calculated or determined via a local search. + +![Figure 5.1.4-2: Illustration of NF testing utilizing the black&white-box approach. The diagram shows two scenarios for NF testing. In the left scenario, the DUT is oriented such that its Far Field (FF) beam peak direction (blue arrow) is aligned with the probe antenna. The Near Field (NF) beam peak direction (purple arrow) is shown to be different from the FF direction due to the offset of the antenna phase center. In the right scenario, the DUT is reoriented so that its NF beam peak direction is aligned with the probe antenna. The FF beam peak direction is now at an angle. The offset of the antenna phase center is indicated by the coordinates (x_off, y_off, z_off). The distance from the phase center to the probe antenna in the NF is labeled r_1, and the distance in the FF is labeled d_1.](e342f16f418dd3a8bf8fcec8a55b752c_img.jpg) + +Figure 5.1.4-2: Illustration of NF testing utilizing the black&white-box approach. The diagram shows two scenarios for NF testing. In the left scenario, the DUT is oriented such that its Far Field (FF) beam peak direction (blue arrow) is aligned with the probe antenna. The Near Field (NF) beam peak direction (purple arrow) is shown to be different from the FF direction due to the offset of the antenna phase center. In the right scenario, the DUT is reoriented so that its NF beam peak direction is aligned with the probe antenna. The FF beam peak direction is now at an angle. The offset of the antenna phase center is indicated by the coordinates (x\_off, y\_off, z\_off). The distance from the phase center to the probe antenna in the NF is labeled r\_1, and the distance in the FF is labeled d\_1. + +**Figure 5.1.4-2: Illustration of NF testing utilizing the black&white-box approach.** + +To guarantee that the correct beam is measured for when the black&white-box measurement approach is applied, the CFF(D)NF approach utilizes a FF probe that allows the UE to select the proper beam in the known beam peak direction. A beam lock activation via the UBF makes sure that the UE no longer changes its antenna pattern when the NF measurement probe is used to perform the measurements with significantly reduced free-space path losses compared to existing IFF systems. + +The CFFDNF approach and test steps for EIRP/EIS/TRP follow those for IFF/DFF outlined in Annex K [6] with the exception that the minimum range length is reduced. The minimum number of TRP grid points, required grid point spacing, and the effect of compensation of the declared/known offset is further outlined in this clause. + +#### 5.1.4.1 Asymptotic Expansion Approach for CFFNF + +The asymptotic expansion approach for CFFNF that is using measurements + +- at three different radii including local searches around the FF beam peak direction (black-box approach) or +- at two different radii without local searches as the NF beam peak direction can be calculated (black&white-box approach) + +is primarily meant to estimate the FF EIRP/EIS at the beam peak with NF EIRP/EIS measurements performed in the radiative NF instead of the reactive NF. This expansion approach is not suitable to determine the FF pattern given the required overhead with the measurements at multiple radii. + +The asymptotic expansion approach is based on the superposition approach + +with + +- $\text{Signal}(\theta, \phi)$ : signal at measurement grid point $(\theta, \phi, r)$ +- $c_k$ : complex coefficient for $k^{\text{th}}$ antenna array element +- $F_k$ : field pattern for $k^{\text{th}}$ antenna element +- $F_p$ : field pattern for probe antenna +- $(\theta_k, \phi_k)$ : EL and AZ angles of $k^{\text{th}}$ antenna element with respect to measurement grid point $(\theta, \phi, r)$ +- $(\alpha_k, \beta_k)$ : EL and AZ angles of probe antenna with respect to the $k^{\text{th}}$ antenna element +- $\lambda$ : wavelength +- $d_k$ : distance between $k^{\text{th}}$ antenna element to measurement grid point $(\theta, \phi, r)$ +- $r$ : range length/measurement distance between centre of QZ and probe antenna +- $\rho$ : amplitude loss caused by propagation on length of +- $\psi$ : the phase variation caused by propagation on length of + +The estimate of the FF EIRP based on NF measurements, $p(d)$ , can be expressed as follows + +with + +where $\text{EIRP}(d_f)$ is the estimated EIRP in the far-field and $d_f$ is the distance between the phase centre of the antenna array and the far-field beam peak at range length $r$ (in the FF: $r \sim d_f$ ) while $p(d_1)$ is the measured power with the probe antenna at a near-field distance $d_1$ (measured from the phase centre of the antenna array to probe antenna), $\partial p / \partial d$ is the derivative of power $p$ to distance $d$ . Because the near-field distance $d_1$ is unknown for the black box approach, measurements of the EIRP at multiple measurement distances are needed to determine the parameters of the $\partial p / \partial d$ derivative and the first near-field distance $d_1$ . + +Following the implementation of the CFFNF simulations and an in-depth analysis of the derivative of the superposition expression above, the approximation of normalized power to distance $\partial p / \partial d$ was determined to be + +which yields dependency of normalized power to $d$ of + +This approximation in turn corresponds to a power (field) dependence in the NF of $1/r^4$ ( $1/r^2$ ) which is commonly observed in the radiative NF. CST simulations were used to further support this formulation. Here, an 8x2 antenna array, placed at (0,0,0), was evaluated. Two measurements at $r_1$ and $r_2$ were used to estimate the asymptotic expansion coefficients $b_i$ ; this allowed to estimate the power/EIRP at various distances which was can be compared with actual CST simulations at those distances. The behaviour and the normalized power (compensating the path loss) estimated from two sets of two measurements at $(r_1, r_2)$ of (7.5cm, 9.5cm) and (20cm, 22cm) simulated at various distances ( $>r_2$ ) are shown in Figure 5.1.4.1-1. + +![Four subplots showing CST Sim. v.s. Asymp. Expan. Estimation using NF Power. Top-left: Power (dBm) vs Distance (m) for NF Power @ (7.50 9.50)cm. Top-right: Derivation of Power to Distance (dB/m) vs Distance (m) for NF Power @ (7.50 9.50)cm. Bottom-left: Power (dBm) vs Distance (m) for NF Power @ (20.00 22.00)cm. Bottom-right: Derivation of Power to Distance (dB/m) vs Distance (m) for NF Power @ (20.00 22.00)cm. Each plot compares CST Simulation (red line with circles) and Asymp. Expan. Est. (blue line with stars).](939b79420df0cf962959ccef56f3371f_img.jpg) + +The figure consists of four subplots arranged in a 2x2 grid, comparing CST Simulation (red line with circles) and Asymptotic Expansion Estimation (blue line with stars) for an 8x2 antenna array. The x-axis for all plots is 'Distance (m)' ranging from 0.2 to 2.0. + +- Top-left plot:** 'CST Sim. v.s. Asymp. Expan. Estimation using NF Power @ (7.50 9.50)cm'. The y-axis is 'Power (dBm)' ranging from 82.5 to 83.3. Both curves show a rapid increase in power from approximately 82.6 dBm at 0.2m to about 83.2 dBm at 0.4m, then level off. The CST simulation levels off slightly higher than the asymptotic expansion estimation. +- Top-right plot:** 'CST Sim. v.s. Asymp. Expan. Estimation using NF Power @ (7.50 9.50)cm'. The y-axis is 'Derivation of Power to Distance (dB/m)' ranging from 0 to 14. Both curves show a sharp decrease from approximately 14 dB/m at 0.2m to near 0 dB/m by 0.4m, remaining flat thereafter. +- Bottom-left plot:** 'CST Sim. v.s. Asymp. Expan. Estimation using NF Power @ (20.00 22.00)cm'. The y-axis is 'Power (dBm)' ranging from 83.05 to 83.35. Both curves show a gradual increase in power from approximately 83.15 dBm at 0.2m to about 83.28 dBm at 0.4m, then level off. The CST simulation levels off slightly higher than the asymptotic expansion estimation. +- Bottom-right plot:** 'CST Sim. v.s. Asymp. Expan. Estimation using NF Power @ (20.00 22.00)cm'. The y-axis is 'Derivation of Power to Distance (dB/m)' ranging from -0.4 to 1.2. Both curves show a decrease from approximately 0.8 dB/m at 0.2m to near 0 dB/m by 0.4m, remaining flat thereafter. + +Four subplots showing CST Sim. v.s. Asymp. Expan. Estimation using NF Power. Top-left: Power (dBm) vs Distance (m) for NF Power @ (7.50 9.50)cm. Top-right: Derivation of Power to Distance (dB/m) vs Distance (m) for NF Power @ (7.50 9.50)cm. Bottom-left: Power (dBm) vs Distance (m) for NF Power @ (20.00 22.00)cm. Bottom-right: Derivation of Power to Distance (dB/m) vs Distance (m) for NF Power @ (20.00 22.00)cm. Each plot compares CST Simulation (red line with circles) and Asymp. Expan. Est. (blue line with stars). + +**Figure 5.1.4.1-1: Normalized power (left) and power derivative (right) and as a function of transformed distance. The NF evaluations were performed at $r_1=7.5\text{cm}$ , $r_2=8.5\text{cm}$ , $r_3=9.5\text{cm}$ (top) and at $r_1=20\text{cm}$ , $r_2=21\text{cm}$ , $r_3=22\text{cm}$ (bottom)** + +These curves show that the asymptotic expansion formulation yields good estimates of EIRP/EIS based on measurements in the radiative NF. + +#### 5.1.4.2 Test Procedures for CFFDNF, CFFNF and CFFdeltaNF + +The appropriate test steps required for NF testing based on the CFFDNF approach of DUTs with known phase-centre offsets (black&white-box) are illustrated in Figure 5.1.4.2-1. + +![Figure 5.1.4.2-1: Test Steps for CFFDNF testing of DUTs with known antenna phase centre offset (black&white-box approach).](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +The figure illustrates four sequential steps for CFFDNF testing, each shown in a rectangular frame with a coordinate system (x, y, z) and a 'Quiet Zone' label. + +- Step 1:** Position the UE so that the geometric center of UE is aligned with the center of QZ. A red triangle labeled 'FF Probe' is on the right. +- Step 2:** Orient the UE so that the known UL/DL beam peak is formed towards the FF probe. A red triangle labeled 'FF Probe' is on the right. +- Step 3:** Activate the UE Beamlock Function (UBF). A large black arrow labeled 'Activate UBF' points from right to left. A red triangle labeled 'FF Probe' is on the right. +- Step 4:** Perform measurements with the NF probe along the NF BP direction. A green triangle is on the left, and a red triangle labeled 'FF Probe' and a green triangle labeled 'NF Probe(s)' are on the right. + +Figure 5.1.4.2-1: Test Steps for CFFDNF testing of DUTs with known antenna phase centre offset (black&white-box approach). + +**Figure 5.1.4.2-1: Test Steps for CFFDNF testing of DUTs with known antenna phase centre offset (black&white-box approach).** + +For the CFFNF methodology that supports both the black-box and the black&white-box approach, the initial test steps are the same as steps 1-3 in Figure 5.1.4.2-1. The test steps for the NF measurement portion of the black-box approach are further outlined in Figure 5.1.4.2-2 while the NF test steps for the black&white-box approach are outlined in Figure 5.1.4.2-3. The diagrams on the right of Figure 5.1.4.2-2 illustrate the different local searches required for the measurements at each of the three radii. The measurements at the very first radius $r_1$ require a wide sector of grid points around the known FF beam peak direction big enough so that the local/NF beam peak is captured properly. For the initial local search at $r_1=20\text{cm}$ , the width of the sector is about $\pm 40^\circ$ which can be covered using coarse and fine scans to further reduce the number of points. On the other hand, the sector of grid points for measurements at radius $r_2$ and $r_3$ can be significantly smaller as only a small region around the local NF beam peak found at $r_1$ is needed. + +![Figure 5.1.4.2-2: Illustration of the additional CFFNF test steps with asymptotic expansion transform utilizing the black-box approach. The figure shows three steps: Step 4 (local search around known beam peak direction at radius r1), Step 5 (local search around NF beam peak direction at radius r2), and Step 6 (local search around NF beam peak direction at radius r3). Each step includes a 3D sphere diagram with a probe and a corresponding 2D polar plot showing the beam peak direction and local search test points.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +Step 4: Perform a local search around the known beam peak direction at radius $r_1$ + +NF Probe(s) + +Step 5: Perform a local search around the NF beam peak direction at radius $r_2$ + +NF Probe(s) + +Step 6: Perform a local search around the NF beam peak direction at radius $r_3$ + +NF Probe(s) + +● Known FF BP Direction +● Local Search Test Points for $r_1$ + +● BP Direction in NF at $r_1$ +● Local Search Test Points for $r_2$ & $r_3$ + +● BP Direction in NF at $r_1$ +● Local Search Test Points for $r_2$ & $r_3$ + +Figure 5.1.4.2-2: Illustration of the additional CFFNF test steps with asymptotic expansion transform utilizing the black-box approach. The figure shows three steps: Step 4 (local search around known beam peak direction at radius r1), Step 5 (local search around NF beam peak direction at radius r2), and Step 6 (local search around NF beam peak direction at radius r3). Each step includes a 3D sphere diagram with a probe and a corresponding 2D polar plot showing the beam peak direction and local search test points. + +Figure 5.1.4.2-2: Illustration of the additional CFFNF test steps with asymptotic expansion transform utilizing the black-box approach. + +![Figure 5.1.4.2-3: Illustration of the additional CFFNF test steps with asymptotic expansion transform utilizing the black&white-box approach. The figure shows two steps: Step 4 (measurement with NF probe along the NF beam peak direction at radius r1) and Step 5 (measurement with NF probe along the NF beam peak direction at radius r2). Each step includes a 3D sphere diagram with a probe and a corresponding 2D polar plot showing the beam peak direction and local search test points.](6ca05954842b17f14dfd52f26b9d43d2_img.jpg) + +Step 4: Perform measurement with NF probe along the NF beam peak direction at radius $r_1$ + +NF Probe(s) + +Step 5: Perform measurement with NF probe along the NF beam peak direction at radius $r_2$ + +NF Probe(s) + +Figure 5.1.4.2-3: Illustration of the additional CFFNF test steps with asymptotic expansion transform utilizing the black&white-box approach. The figure shows two steps: Step 4 (measurement with NF probe along the NF beam peak direction at radius r1) and Step 5 (measurement with NF probe along the NF beam peak direction at radius r2). Each step includes a 3D sphere diagram with a probe and a corresponding 2D polar plot showing the beam peak direction and local search test points. + +Figure 5.1.4.2-3: Illustration of the additional CFFNF test steps with asymptotic expansion transform utilizing the black&white-box approach. + +For the CFFdeltaNF methodology that supports the black-box approach, the initial test steps are the same as steps 1-3 in Figure 5.1.4.2-1. The additional test steps for the NF relative and final measurement portion of the black-box approach are further outlined in Figure 5.1.4.2-4. The diagrams on the right of Figure 5.1.4.2-4 illustrate the local search required for the measurements in NF. At $r=35\text{cm}$ , the width of the sector is about $\pm 20^\circ$ which can be covered using coarse and fine scans to further reduce the number of points. + +![Diagram for Step 4: A 3D coordinate system (x, y, z) shows a sphere representing the far-field (FF) region. A black dot on the sphere indicates the FF beam peak direction. A red arrow points to the right, representing the FF probe. A green arrow points to the right, representing the NF probe. Diagram for Step 5: Similar to Step 4, but the NF probe (green arrow) is now positioned at a radius r1 from the center. A circular diagram on the right shows the 'Known FF BP Direction' as a black dot and 'Local Search Test Points for r1' as red dots on a circle of radius r1. Diagram for Step 6: The NF probe (green arrow) is now aligned with the NF beam peak direction, which is different from the FF beam peak direction. Diagram for Step 7: Similar to Step 6, but the power operation test case has been switched.](dd5771673aececa53d42ece89218299d_img.jpg) + +Step 4: Perform a measurement for the reference test case with high-UL or low DL-power operation with the FF probe in the FF beam peak direction + +Step 5: Perform a local search for the reference test case with high-UL or low DL-power operation around the FF beam peak direction at radius $r_1$ in the NF with the NF probe + +Step 6: Perform a measurement for reference test case with high-UL or low DL-power operation with the NF probe in the NF beam peak direction + +Step 7: Switch to the low-UL or high-DL power operation test case and perform a measurement with the NF probe in the NF beam peak direction + +Diagram for Step 4: A 3D coordinate system (x, y, z) shows a sphere representing the far-field (FF) region. A black dot on the sphere indicates the FF beam peak direction. A red arrow points to the right, representing the FF probe. A green arrow points to the right, representing the NF probe. Diagram for Step 5: Similar to Step 4, but the NF probe (green arrow) is now positioned at a radius r1 from the center. A circular diagram on the right shows the 'Known FF BP Direction' as a black dot and 'Local Search Test Points for r1' as red dots on a circle of radius r1. Diagram for Step 6: The NF probe (green arrow) is now aligned with the NF beam peak direction, which is different from the FF beam peak direction. Diagram for Step 7: Similar to Step 6, but the power operation test case has been switched. + +**Figure 5.1.4.2-4: Illustration of the additional CFFdeltaNF test steps utilizing the black-box approach.** + +The sample sequence of test steps for the CFFDNF test methodology with the black&white-box approach is as follows (aligned in principle with Clause K.1.3 of [6]): + +1. Connect the SS (System Simulator) with the DUT through the FF measurement antenna with polarization reference $Pol_{Link}$ to form the TX beam towards the FF TX beam peak direction. Allow at least $BEAM\_SELECT\_WAIT\_TIME$ for the UE TX beam selection to complete. +2. SS activates the UE Beamlock Function (UBF) by performing the procedure as specified in TS 38.508-1 clause 4.9.2 using condition Tx only. +3. If necessary, switch the connection of the SS from the FF probe to the NF probe at range length $r_1$ with polarization reference $Pol_{Link}$ . Position the device so that the NF probe antenna is pointed towards the NF TX beam peak direction (determined from the antenna offset, range length, and FF beam peak direction). The range length is left up to system implementation. +4. Measure the mean power $P_{meas}(Pol_{Meas}=\theta, Pol_{Link})$ of the modulated signal arriving at the power measurement equipment (such as a spectrum analyser, power meter, or gNB emulator). +5. Calculate the EIRP( $Pol_{Meas}=\theta, Pol_{Link}$ ) from the measured power $P_{meas}(Pol_{Meas}=\theta, Pol_{Link})$ + - a. adding the calibrated composite loss of the entire transmission path between the TE and the centre of QZ (displaced from measurement probe by $r$ ), $L_{EIRP,0}$ + - b. compensating the actual measurement distance $d$ (between the centre of the array to the measurement probe) using term $20 \log_{10}(d/r)$ + - c. applying the probe antenna gain NF correction + +6. Measure the mean power $P_{\text{meas}}(\text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}})$ of the modulated signal arriving at the power measurement equipment (such as a spectrum analyser, power meter, or gNB emulator). +7. Calculate the EIRP( $\text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}}$ ) from the measured power $P_{\text{meas}}(\text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}})$ + - a. adding the calibrated composite loss of the entire transmission path between the TE and the centre of QZ (displaced from measurement probe by $r$ ), $L_{\text{EIRP},\phi}$ + - b. compensating the actual measurement distance $d$ (between the centre of the array to the measurement probe) using term $20 \log_{10}(d/r)$ + - c. applying the probe antenna gain NF correction +8. Calculate the resulting “total EIRP( $\text{Pol}_{\text{Link}}$ )”, for the chosen $\text{Pol}_{\text{Link}}$ of $\theta$ or $\phi$ as follows: + +$$\text{total EIRP}(\text{Pol}_{\text{Link}}) = \text{EIRP}(\text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}}) + \text{EIRP}(\text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}})$$ +9. SS deactivates the UE Beamlock Function (UBF) by performing the procedure as specified in TS 38.508-1 clause 4.9.3. + +The sample sequence of test steps for the CFFNF test methodology with the black&white-box approach is as follows (aligned in principle with Clause K.1.3 of [6]): + +1. Connect the SS (System Simulator) with the DUT through the FF measurement antenna with polarization reference $\text{Pol}_{\text{Link}}$ to form the TX beam towards the FF TX beam peak direction. Allow at least BEAM\_SELECT\_WAIT\_TIME for the UE TX beam selection to complete. +2. SS activates the UE Beamlock Function (UBF) by performing the procedure as specified in TS 38.508-1 clause 4.9.2 using condition Tx only. +3. If necessary, switch the connection of the SS from the FF probe to the NF probe at range length $r=r_1$ /at measurement distance $d=d_1$ (between the centre of the array to the measurement probe) with polarization reference $\text{Pol}_{\text{Link}}$ . +4. Position the device so that the NF probe antenna is pointed towards the NF TX beam peak direction (determined from the antenna offset, range length $r$ , and FF beam peak direction). The range length $r$ is left up to system implementation. +5. Measure $N$ averages of the mean power $P_{\text{meas}}(d, \text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}})$ of the modulated signal arriving at the power measurement equipment (such as a spectrum analyser, power meter, or gNB emulator). The number of averages is left up to system implementation. +6. Calculate the normalized NF power $p(d, \text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}})$ from the measured power $P_{\text{meas}}(d, \text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}})$ + - a. adding the calibrated composite loss of the entire transmission path between the TE and the centre of QZ (displaced from measurement probe by $r=r_1$ ), $L_{\text{EIRP},\theta}$ + - b. compensating the actual measurement distance $d$ using term $20 \log_{10}(d/r)$ + - c. applying the probe antenna gain NF correction +7. Measure $N$ averages of the mean power $P_{\text{meas}}(d, \text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}})$ of the modulated signal arriving at the power measurement equipment (such as a spectrum analyser, power meter, or gNB emulator). The number of averages is left up to system implementation. +8. Calculate the normalized NF power $p(d, \text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}})$ from the measured power $P_{\text{meas}}(d, \text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}})$ + - a. adding the calibrated composite loss of the entire transmission path between the TE and the centre of QZ (displaced from measurement probe by $r$ ), $L_{\text{EIRP},\phi}$ + - b. compensating the actual measurement distance $d$ (between the centre of the array to the measurement probe) using term $20 \log_{10}(d/r)$ + - c. applying the probe antenna gain NF correction +9. Repeat Steps 4-8 for $r=r_2$ and $d=d_2$ + +- Calculate the total normalized NF power for the chosen $\text{Pol}_{\text{Link}}$ of $\theta$ or $\phi$ as follows: + +$$p(d_i) = p(d_i, \text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}}) + p(d_i, \text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}}) \text{ with } i=\{1,2\}$$ + +- Based on the selected asymptotic expansion formulation, determine the “total FF EIRP( $\text{Pol}_{\text{Link}}$ )” from the two total normalized NF power measurement measurements, $p(d_1)$ and $p(d_2)$ . For an asymptotic expansion formulation of + +The resulting “total FF EIRP( $\text{Pol}_{\text{Link}}$ )”, for the chosen $\text{Pol}_{\text{Link}}$ of $\theta$ or $\phi$ is calculated as follows + +- SS deactivates the UE Beamlock Function (UBF) by performing the procedure as specified in TS 38.508-1 clause 4.9.3. + +The sample sequence of test steps for the CFFNF test methodology with the black-box approach is as follows (aligned in principle with Clause K.1.3 of [6]): + +- Connect the SS (System Simulator) with the DUT through the FF measurement antenna with polarization reference $\text{Pol}_{\text{Link}}$ to form the TX beam towards the FF TX beam peak direction. Allow at least $\text{BEAM\_SELECT\_WAIT\_TIME}$ for the UE TX beam selection to complete. +- SS activates the UE Beamlock Function (UBF) by performing the procedure as specified in TS 38.508-1 clause 4.9.2 using condition Tx only. +- If necessary, switch the connection of the SS from the FF probe to the NF probe at range length $r_1$ with polarization reference $\text{Pol}_{\text{Link}}$ . Position the device so that that NF probe antenna is pointed towards the FF TX beam peak direction. The range length $r_1$ is left up to system implementation. +- Perform a NF BP search on a sector around the FF BP direction at radius $r=r_1$ , which could determine $K (\geq 1)$ possible NF BP directions and corresponding antenna array phase centre positions and thus distances between the antenna array and the measurement probe, $d_{i,k}$ . Based on the NF BP directions and antenna array phase centre positions, the corresponding NF BP directions at radius $r=r_2$ and $r=r_3$ can be determined. Details including the range lengths $r_2$ and $r_3$ are left up to system implementation. +- Measure $N$ averages of the mean power $P_{\text{meas},k}(d_{i,k}, \text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}})$ , $k=\{1,2,\dots,K\}$ of the modulated signal arriving at the power measurement equipment (such as a spectrum analyser, power meter, or gNB emulator) at each of the $K$ possible NF BP direction at radius $r=r_i$ with $i=\{1,2,3\}$ determined in Step 4. The number of averages is left up to system implementation. +- Calculate the normalized NF power $p_{\text{meas},k}(d_{i,k}, \text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}})$ , $k=\{1,2,\dots,K\}$ , from the measured power $P_{\text{meas},k}(d_{i,k}, \text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}})$ , $k=\{1,2,\dots,K\}$ , at radius $r=r_i$ with $i=\{1,2,3\}$ + - adding the calibrated composite loss of the entire transmission path between the TE and the centre of QZ (displaced from measurement probe by $r=r_i$ ), $L_{\text{EIRP},\theta}$ + - compensating the actual measurement distance $d=d_i$ (between the centre of the array to the measurement probe) using term $20 \log_{10}(d_i/r_i)$ + - applying the probe antenna gain NF correction +- Measure $N$ averages of the mean power $P_{\text{meas},k}(d_{i,k}, \text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}})$ , $k=\{1,2,\dots,K\}$ , of the modulated signal arriving at the power measurement equipment (such as a spectrum analyser, power meter, or gNB emulator) at each of the possible NF BP direction at radius $r=r_i$ with $i=\{1,2,3\}$ determined in Step 4. The number of averages is left up to system implementation. +- Calculate the normalized NF power $p_{\text{meas},k}(d_{i,k}, \text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}})$ , $k=\{1,2,\dots,K\}$ , from the measured power $P_{\text{meas},k}(d_{i,k}, \text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}})$ , $k=\{1,2,\dots,K\}$ , at radius $r=r_i$ with $i=\{1,2,3\}$ + - adding the calibrated composite loss of the entire transmission path between the TE and the centre of QZ (displaced from measurement probe by $r=r_i$ ), $L_{\text{EIRP},\phi}$ + - compensating the actual measurement distance $d=d_i$ (between the centre of the array to the measurement probe) using term $20 \log_{10}(d_i/r_i)$ + +- c. applying the probe antenna gain NF correction +9. Calculate the total normalized NF power for each of possible NF BP directions with the chosen Pol<sub>Link</sub> of $\theta$ or $\phi$ as follows: + +$$p_{\text{meas},k}(d_i) = p_{\text{meas}}(d_{i,k}, \text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}}) + p_{\text{meas}}(d_{i,k}, \text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}}) \text{ with } k=\{1,2,\dots,K\} \text{ and } i=\{1,2,3\}$$ + 10. For each of $K$ possible NF BP directions, based on the $p_{\text{meas},k}$ , $k=\{1,2,\dots,K\}$ , results at $r=r_1$ , $r=r_2$ , and $r=r_3$ perform a linear fitting to determine far-field normalized power “total FF EIRP<sub>k</sub>(Pol<sub>Link</sub>)” and fitting error $err_k$ , based on the selected expansion formulation, e.g., + 11. Determine the final NF BP direction by choosing the NF BP direction with minimum fitting error Details of this step are left up to system implementation. + 12. Based on the selected NF BP direction in Step 11, the resulting “total FF EIRP(Pol<sub>Link</sub>)”, for the chosen Pol<sub>Link</sub> of $\theta$ or $\phi$ is determined as + 13. SS deactivates the UE Beamlock Function (UBF) by performing the procedure as specified in TS 38.508-1 clause 4.9.3. + +The sample sequence of test steps for the CFFdeltaNF test methodology with the black-box approach is as follows (aligned in principle with Clause K.1.3 of [6]): + +1. Connect the SS (System Simulator) with the DUT through the FF measurement antenna with polarization reference Pol<sub>Link</sub> to form the TX beam towards the FF TX beam peak direction. Allow at least BEAM\_SELECT\_WAIT\_TIME for the UE TX beam selection to complete. +2. SS activates the UE Beamlock Function (UBF) by performing the procedure as specified in TS 38.508-1 clause 4.9.2 using condition Tx only. +3. Measure the mean power $P_{\text{meas}}(\text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}})$ and $P_{\text{meas}}(\text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}})$ of the modulated signal arriving at the power measurement equipment (such as a spectrum analyser, power meter, or gNB emulator) through the FF measurement antenna for the reference test case without testability issue (e.g. Peak EIRP). +4. If necessary, switch the connection of the SS from the FF probe to the NF probe at range length $r_1$ with polarization reference Pol<sub>Link</sub>. The range length is left up to system implementation. +5. Position the device so that the NF probe antenna is pointed towards the FF TX beam peak direction and perform a NF BP search on a sector around the FF BP direction at range length $r_1$ to determine the NF Tx beam peak direction. +6. Measure the mean power $P_{\text{meas}}(\text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}})$ and $P_{\text{meas}}(\text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}})$ of the modulated signal arriving at the power measurement equipment (such as a spectrum analyser, power meter, or gNB emulator) through the NF measurement antenna for the reference test case without testability issue (e.g. Peak EIRP) at the NF beam peak direction. +7. Calculate the NF correction factor for each polarization as the difference between the measured mean power and the composite loss of the entire transmission path through the FF and NF measurement antennas: + +Note: this correction factor include all effects due to the usage of a NF probe (i.e. DUT antenna location displacement from center, probe antenna pattern and near-field interaction between probe antenna and DUT antenna) + +8. If necessary, calculate the NF correction factor for each polarization at the correct test frequency for the low UL power test case to include the additional effect of the system frequency response: + +9. Measure the mean power $P_{\text{meas}}(\text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}})$ of the modulated signal arriving at the power measurement equipment (such as a spectrum analyser, power meter, or gNB emulator) through the NF measurement antenna for the low UL power test case at the NF beam peak direction. +10. Calculate the EIRP( $\text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}}$ ) from the measured power $P_{\text{meas}}(\text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}})$ by adding the composite correction factor between FF and DNF and the frequency to the measured power $P_{\text{meas}}(\text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}})$ . +11. Measure the mean power $P_{\text{meas}}(\text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}})$ of the modulated signal arriving at the power measurement equipment (such as a spectrum analyser, power meter, or gNB emulator) through the NF measurement antenna for the low UL power test case at the NF beam peak direction. +12. Calculate the EIRP( $\text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}}$ ) from the measured power $P_{\text{meas}}(\text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}})$ by adding the composite correction factor between FF and DNF and the frequency to the measured power $P_{\text{meas}}(\text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}})$ . +13. Calculate the resulting “total EIRP( $\text{Pol}_{\text{Link}}$ )”, for the chosen $\text{Pol}_{\text{Link}}$ of $\theta$ or $\phi$ as follows: + +$$\text{total EIRP}(\text{Pol}_{\text{Link}}) = \text{EIRP}(\text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}}) + \text{EIRP}(\text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}})$$ + +14. SS deactivates the UE Beamlock Function (UBF) by performing the procedure as specified in TS 38.508-1 clause 4.9.3. + +#### 5.1.4.3 Simulation Assumptions + +The simulation assumptions for the CFFDNF, CFFNF and CFFdeltaNF methodologies are summarized in Table 5.1.4.3-1. + +**Table 5.1.4.3-1: Simulation assumptions for CFFDNF, CFFNF and CFFdeltaNF simulations** + +| Parameter | Value(s)/Assumptions | Comment | +|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| Methodology | CFFDNF: with black&white-box approach<br>CFFNF: with black-box and black&white-box approach<br>CFFdeltaNF: with black-box approach | | +| Simulation Frequency [GHz] | 28 (others are not precluded) | | +| UE Antenna Array Configuration | PC3: 8x2 and 4x1<br>PC1: 12x12 | | +| Beam Steering Assumptions | N/A | Not needed for combined FF and NF methods as beam peak searches and spherical coverage measurements are based on FF probe | +| HPBW of Individual Array Element | 90°/90° | | +| Offsets of Active Array Panel | PC3 8x2&4x1:<br>$0 \leq x_{\text{offset}} \leq 12.5\text{cm}$<br>$-12.5\text{cm} \leq y_{\text{offset}} \leq 12.5\text{cm}$<br>$-12.5\text{cm} \leq z_{\text{offset}} \leq 12.5\text{cm}$<br>(The maximum radial offset cannot exceed 12.5cm)<br><br>PC1 12x12:<br>$0 \leq x_{\text{offset}} \leq 10\text{cm}$<br>$-10\text{cm} \leq y_{\text{offset}} \leq 10\text{cm}$<br>$-10\text{cm} \leq z_{\text{offset}} \leq 10\text{cm}$<br>(The maximum radial offset cannot exceed 10cm) | Offsets should be picked randomly (for uniform distribution)<br><br>Min of 500 offsets selected randomly with uniform distribution | +| Path Loss Correction | Compensation of antenna array offset for black&white-box approaches and the CFFNF black-box approach.<br>N/A for CFFdeltaNF black-box approach | Path loss applied to the EIRP measurements is not referenced to the centre of QZ but to the phase centre of the active antenna array | +| NF Measurement Direction | Determined theoretically from range length, FF BP direction, and array offsets for black&white-box approach.<br>Determined with local search for black-box approach. | | +| Probe antenna pattern/gain compensation | With compensation (uniform pattern assumed in simulations)<br>Without compensation (typical horn pattern with ~50° HPBW pattern applied) | N/A for CFFdeltaNF | +| Tool Used for Simulations | Matlab or EM simulator | | +| Range Lengths | 20cm, 25cm, 30cm, 35cm, 40cm, 45cm, 20m | | + +#### 5.1.4.4 Simulation results for CFFDNF + +The main intention of this clause is to estimate the measurement uncertainties of EIRP measurements performed in the NF at various range lengths. Since the beam peak search and spherical coverage analyses are performed with the FF probe, beam steering assumptions are not required here. The definitions of offsets ( $x_{\text{offset}}/y_{\text{offset}}/z_{\text{offset}}$ ), maximum offsets ( $\leq 12.5\text{cm}$ for PC3 and $\leq 10\text{cm}$ for PC1), array configurations (PC3: 8x2 and 4x1, PC1: 12x12), and range lengths are summarized in Table 5.1.4.3-1. + +The FF 8x2 and 4x1 array patterns with the 90°/90° HPBW assumption are shown in Figure 5.1.4.4-1. + +![Figure 5.1.4.4-1: Far-field antenna patterns for 2x8 and 1x4 array configurations. The left plot shows a 2x8 array with a color scale from -15 to 15 dB. The right plot shows a 1x4 array with a color scale from -20 to 10 dB. Both plots include a 3D surface plot of the antenna pattern and a 2D polar plot below it. The 2x8 array pattern is more directional than the 1x4 array pattern.](c53adc66eab40abd5f8b9107d950ad04_img.jpg) + +Figure 5.1.4.4-1: Far-field antenna patterns for 2x8 and 1x4 array configurations. The left plot shows a 2x8 array with a color scale from -15 to 15 dB. The right plot shows a 1x4 array with a color scale from -20 to 10 dB. Both plots include a 3D surface plot of the antenna pattern and a 2D polar plot below it. The 2x8 array pattern is more directional than the 1x4 array pattern. + +**Figure 5.1.4.4-1: FF antenna pattern with $90^\circ/90^\circ$ HPBW for 8x2 antenna array configuration (left) and 4x1 antenna array configuration (right).** + +The pattern simulations assume superpositions of individual, single-element far-field antenna patterns; this approach requires that the NF of $N_y \times N_z$ antenna array is well in the FF of the single-element antenna. The EIRP simulations were performed using Matlab and CST. + +The simulations assume that the FF beam peak direction of the DUT is known for the sample DUT considered. + +For the statistical analyses using Matlab, a total of 100,000 simulations with random and uniformly spaced offsets were performed. These offsets were varied between 0 to 12.5cm (10cm) in $x$ and from -12.5cm (-10cm) to 12.5cm (10cm) in $y$ and $z$ for PC3 (PC1) while making sure that the maximum radial offset cannot exceed 12.5cm (10cm). The offsets in $x$ were limited to positive values since it is assumed that the front antenna of the DUT is always in the upper hemisphere since the geometric centre of the device is aligned with the centre of the QZ. A sample set of 100,000 random offsets is visualized in Figure 5.1.4.4-2. Histograms of the respective offset radii, and offsets in $x$ , $y$ , and $z$ are shown in Figure 5.1.4.4-3. + +**100000 Random Array Offsets +(Max Array Offset: 125mm with $R_{QZ}=150\text{mm}$ )** + +![Figure 5.1.4.4-2: Illustration of 100,000 random offsets uniformly spaced within 12.5cm in a single hemisphere. The plot shows a 3D coordinate system with x, y, and z axes. A red shaded region represents the distribution of offsets, which are concentrated in the upper hemisphere (positive z) and spread out radially from the origin.](a4cee18a14f569dd8b88c5e5f9d43b48_img.jpg) + +Figure 5.1.4.4-2: Illustration of 100,000 random offsets uniformly spaced within 12.5cm in a single hemisphere. The plot shows a 3D coordinate system with x, y, and z axes. A red shaded region represents the distribution of offsets, which are concentrated in the upper hemisphere (positive z) and spread out radially from the origin. + +**Figure 5.1.4.4-2: Illustration of 100,000 random offsets uniformly spaced within 12.5cm in a single hemisphere.** + +![Figure 5.1.4.4-3: Four histograms showing the distribution of 100,000 random offsets uniformly spaced within 12.5cm in a single hemisphere. The histograms are: Radius of offset [mm] (0 to 125 mm, peak frequency ~4500), x_offset [mm] (0 to 125 mm, peak frequency ~2500), y_offset [mm] (-125 to 125 mm, peak frequency ~3000), and z_offset [mm] (-125 to 125 mm, peak frequency ~3000).](bf30e154f82662d212f21fccdfa2980f_img.jpg) + +Figure 5.1.4.4-3: Four histograms showing the distribution of 100,000 random offsets uniformly spaced within 12.5cm in a single hemisphere. The histograms are: Radius of offset [mm] (0 to 125 mm, peak frequency ~4500), x\_offset [mm] (0 to 125 mm, peak frequency ~2500), y\_offset [mm] (-125 to 125 mm, peak frequency ~3000), and z\_offset [mm] (-125 to 125 mm, peak frequency ~3000). + +**Figure 5.1.4.4-3: Histograms of 100,000 random offsets uniformly spaced within 12.5cm in a single hemisphere.** + +Since each of the offsets are known/declared, the offset can be properly compensated, i.e., the pathloss applied to the EIRP measurements is not referenced to the centre of QZ but to the phase centre of the active antenna array. The results in this clause focus only on the EIRP results after the path loss with respect to the offset antenna array was compensated. + +Additionally, for the best/optimized measurement uncertainties, the probe antenna pattern/gain must be compensated since the array offsets can result in the NF beam peak to be observed from directions with large deviations from the peak gain direction of the measurement probe/horn as illustrated in Figure 5.1.4-2. In the simulations, probe pattern/gain compensation can be modelled in the simplest approximation by assuming an omnidirectional pattern of the probe. To quantify the effect of not compensating the probe antenna pattern, this section will present measurement uncertainties for a typical horn antenna. For these simulations, a symmetric pattern of a horn antenna with $\sim 50^\circ$ HPBW pattern is assumed as plotted in Figure 5.1.4.4-4, which was obtained using the following Matlab commands: + +``` +ProbeTheta=-180:1:180; +HPBW=50; +ProbePattern_norm=-12*(ProbeTheta/HPBW); +``` + +![Two plots showing Normalized Probe Gain [dBi] vs theta [°]. The top plot shows a wide beam pattern from -150 to 150 degrees, and the bottom plot shows a narrower beam pattern from -40 to 40 degrees. An inset diagram shows the angle theta definition.](771c18f874d31c59c3b8c4e247be16ca_img.jpg) + +The figure consists of two plots. The top plot shows 'Normalized Probe Gain [dBi]' on the y-axis (ranging from -30 to 0) against $\theta [^\circ]$ on the x-axis (ranging from -150 to 150). The curve is a broad bell shape centered at 0 degrees. An inset box shows a diagram of an antenna with a green arrow pointing to the right, and an angle $\theta$ indicated by a curved arrow. The bottom plot shows 'Normalized Probe Gain [dBi]' on the y-axis (ranging from -20 to 0) against $\theta [^\circ]$ on the x-axis (ranging from -40 to 40). This curve is a narrower bell shape, also centered at 0 degrees. + +Two plots showing Normalized Probe Gain [dBi] vs theta [°]. The top plot shows a wide beam pattern from -150 to 150 degrees, and the bottom plot shows a narrower beam pattern from -40 to 40 degrees. An inset diagram shows the angle theta definition. + +**Figure 5.1.4.4-4: Assumed measurement probe antenna pattern.** + +The NF beam peak direction, illustrated in Figure 5.1.4-2, was calculated using the known FF beam peak direction, the offset of the antenna array, and the range length. + +A histogram of the 100k EIRP simulations for 4 different NF range lengths (20cm, 25cm, 30cm, 45cm) and the 20m FF range lengths is shown in Figure 5.1.4.4-5 and the statistical results of these simulations are tabulated in Table 5.1.4.4-1. These results assume that the antenna array offsets and the probe pattern/gain were compensated. + +![Histogram titled 'CFFDNF Results with Black&White Box Assumption at 28GHz'. It shows PDF vs Normalized EIRP [dBm] for various range lengths (0.2m to 20m). The distributions become narrower and shift towards zero as range length increases.](ddc89e164666201115a1c006e4c3b6da_img.jpg) + +The figure is a histogram titled 'CFFDNF Results with Black&White Box Assumption at 28GHz'. It includes a subtitle 'Antenna array offset correction applied to EIRP results' and another subtitle 'Probe pattern offset applied'. The y-axis is labeled 'PDF' and ranges from 0 to 1. The x-axis is labeled 'Normalized EIRP [dBm]' and ranges from -1.4 to 0. The legend lists seven data series for different range lengths, each with its mean error and standard deviation in dB: + +| Range Length [m] | Mean Error [dB] | Std. Dev [dB] | +|------------------|-----------------|---------------| +| 0.2 | 0.48 | 0.22 | +| 0.25 | 0.23 | 0.08 | +| 0.3 | 0.14 | 0.04 | +| 0.35 | 0.09 | 0.02 | +| 0.4 | 0.07 | 0.01 | +| 0.45 | 0.05 | 0.01 | +| 20 | 0.00 | 0.00 | + +The histogram shows that as the range length increases, the distribution of Normalized EIRP becomes narrower and its mean shifts towards zero. + +Histogram titled 'CFFDNF Results with Black&White Box Assumption at 28GHz'. It shows PDF vs Normalized EIRP [dBm] for various range lengths (0.2m to 20m). The distributions become narrower and shift towards zero as range length increases. + +**Figure 5.1.4.4-5: Histogram of 100,000 EIRP CFFDNF simulations based on black&white-box approach with random 8x2 antenna array offsets uniformly spaced within 12.5cm in a single hemisphere. The antenna array offsets and the probe pattern/gain were compensated** + +**Table 5.1.4.4-1: Statistical results of 100,000 EIRP CFFDNF simulations based on black&white-box approach with random 8x2 antenna array offsets uniformly spaced within 12.5cm in a single hemisphere. The antenna array offsets and the probe pattern/gain were compensated** + +| Range Length [m] | Max-Min EIRP [dB] | Max EIRP Error w.r.t. FF [dB] | Mean EIRP Error w.r.t. FF [dB] | Std. Dev of EIRP [dB] | +|------------------|-------------------|-------------------------------|---------------------------------|-----------------------| +| 0.2 | 1.17 | 1.36 | 0.48 | 0.22 | +| 0.25 | 0.37 | 0.50 | 0.23 | 0.08 | +| 0.3 | 0.17 | 0.26 | 0.14 | 0.04 | +| 0.35 | 0.09 | 0.16 | 0.09 | 0.02 | +| 0.4 | 0.06 | 0.10 | 0.07 | 0.01 | +| 0.45 | 0.04 | 0.07 | 0.05 | 0.01 | +| 20 | 0.00 | 0.00 | 0.00 | 0.00 | + +Figure 5.1.4.4-6 illustrates which simulations for the 20cm range length result in the minimum and maximum EIRPs after antenna offset and probe pattern compensation. + +![Figure 5.1.4.4-6: Two 3D plots showing the radiation pattern of an 8x2 antenna array. The left plot shows the configuration resulting in the smallest EIRP, and the right plot shows the configuration resulting in the largest EIRP. Each plot includes a 3D view of the probe and array, a 'DUT View' of the pattern, and a color scale from -15 to 15.](e51925aa86bb1cd1ea891dbb493caa4f_img.jpg) + +- (Ny x Nz): 2x8 Pattern with Range Length [(m/ $\lambda$ )]: (0.20, 18.68) with f [GHz]: 28 +- Offset in x/y/z [cm]: 12.5/-0.6/-0.4 +- $\theta_{DUT}$ [deg]: 91.2, $\phi_{DUT}$ [deg]: -1.6 with Alignment Option 1 - DUT Orientation 1 +- EIRP [dBm] @Probe after Path Loss Compensation (Centre of QZ): 20.67 +- EIRP [dBm] @Probe after Path Loss Compensation (Centre of Array): 12.18 +- Angle between Probe and Array [deg]: 2.0 + +- (Ny x Nz): 2x8 Pattern with Range Length [(m/ $\lambda$ )]: (0.20, 18.68) with f [GHz]: 28 +- Offset in x/y/z [cm]: 0.0/-0.2/0.8 +- $\theta_{DUT}$ [deg]: 87.8, $\phi_{DUT}$ [deg]: -0.5 with Alignment Option 1 - DUT Orientation 1 +- EIRP [dBm] @Probe after Path Loss Compensation (Centre of QZ): 13.36 +- EIRP [dBm] @Probe after Path Loss Compensation (Centre of Array): 13.34 +- Angle between Probe and Array [deg]: 2.2 + +Figure 5.1.4.4-6: Two 3D plots showing the radiation pattern of an 8x2 antenna array. The left plot shows the configuration resulting in the smallest EIRP, and the right plot shows the configuration resulting in the largest EIRP. Each plot includes a 3D view of the probe and array, a 'DUT View' of the pattern, and a color scale from -15 to 15. + +**Figure 5.1.4.4-6: Illustration of simulations for the 20cm range length with 8x2 antenna configuration resulting in smallest (left) and largest (right) EIRPs after antenna offset and probe pattern compensation.** + +When the antenna array offset is towards the probe antenna, shown in the left plot of Figure 5.1.4.4-6, the EIRP without the offset compensation is very high (20.7dBm in this example); however, the offset compensation, i.e., applying the pathloss between the probe antenna and the active antenna array, helps to significantly improve the EIRP measurement uncertainty with respect to the EIRP measured in the FF. + +Once the array offsets and the probe antenna pattern are compensated in the NF with CFFDNF methodology assuming the black&white-box approach, almost insignificant measurement uncertainties for PC3 devices can be observed at 45cm. At distances less than 45cm, measurement uncertainties must be taken into account. + +When the probe pattern/gain is not compensated, a much larger variation of the measured EIRP results is expected due to the large off broadside directions of the antenna panels from the probe antenna, as illustrated schematically in Figure 5.1.4-2. This is further quantified in Figure 5.1.4.4-6 and in Table 5.1.4.4-2 for the same simulations. These results assume that the antenna array offsets are compensated while the probe pattern/gain were not compensated, i.e., the pattern in Figure 5.1.4.4-4 was applied to the simulations. + +![Histogram of 100,000 EIRP CFFDNF simulations. The x-axis is 'Normalized EIRP [dBm]' from -8 to 0. The y-axis is 'PDF' from 0 to 1. Seven curves are shown for different range lengths: 0.2m, 0.25m, 0.3m, 0.35m, 0.4m, 0.45m, and 20m. The 20m curve is a vertical line at 0 dBm. The other curves show a distribution of errors centered around 0 dBm, with the spread decreasing as range length increases. A legend box in the top-left corner provides the mean and standard deviation for each range length.](cfc852835f2d91bea8dc074568937e22_img.jpg) + +**CFFDNF Results with Black&White Box Assumption at 28GHz** +**Antenna array offset correction applied to EIRP results** +**Probe pattern offset not applied** + +| Range Length [m] | Mean Error [dB] | Std. Dev [dB] | +|------------------|-----------------|---------------| +| 0.2 | 3.15 | 1.82 | +| 0.25 | 1.89 | 1.11 | +| 0.3 | 1.27 | 0.75 | +| 0.35 | 0.92 | 0.54 | +| 0.4 | 0.69 | 0.41 | +| 0.45 | 0.54 | 0.32 | +| 20 | 0.00 | 0.00 | + +Histogram of 100,000 EIRP CFFDNF simulations. The x-axis is 'Normalized EIRP [dBm]' from -8 to 0. The y-axis is 'PDF' from 0 to 1. Seven curves are shown for different range lengths: 0.2m, 0.25m, 0.3m, 0.35m, 0.4m, 0.45m, and 20m. The 20m curve is a vertical line at 0 dBm. The other curves show a distribution of errors centered around 0 dBm, with the spread decreasing as range length increases. A legend box in the top-left corner provides the mean and standard deviation for each range length. + +**Figure 5.1.4.4-7: Histogram of 100,000 EIRP CFFDNF simulations based on black&white-box approach with random 8x2 antenna array offsets uniformly spaced within 12.5cm in a single hemisphere. The antenna array offsets were compensated while the probe pattern/gain was not compensated** + +**Table 5.1.4.4-2: Statistical results of 100,000 EIRP CFFDNF simulations based on black&white-box approach with random 8x2 antenna array offsets uniformly spaced within 12.5cm in a single hemisphere. The antenna array offsets were compensated while the probe pattern/gain was not compensated.** + +| Range Length [m] | Max-Min EIRP at (90,0) [dB] | Max EIRP Error w.r.t. FF [dB] | Mean EIRP Error w.r.t. FF [dB] | Std. Dev of EIRP at (90,0) [dB] | +|------------------|-----------------------------|-------------------------------|---------------------------------|---------------------------------| +| 0.2 | 7.31 | 7.51 | 3.15 | 1.82 | +| 0.25 | 4.36 | 4.49 | 1.89 | 1.11 | +| 0.3 | 2.93 | 3.02 | 1.27 | 0.75 | +| 0.35 | 2.11 | 2.18 | 0.92 | 0.54 | +| 0.4 | 1.60 | 1.65 | 0.69 | 0.41 | +| 0.45 | 1.25 | 1.29 | 0.54 | 0.32 | +| 20 | 0.00 | 0.00 | 0.00 | 0.00 | + +The latter results clearly demonstrate that when performing measurements in the NF with CFFDNF methodology assuming the black&white-box approach, the probe antenna pattern must be compensated. + +A study to determine whether 1k or even 250 offset simulations are sufficient for the MU results, a comparison of 100k vs 1k vs 250 offset simulations was made. The visualization of 100k vs 1k random offsets is illustrated in Figure 5.1.4.4-8. Clearly, the 100k offsets are uniformly distributed in the hemisphere while the random 250 and 1k offsets are distributed rather sparsely. + +100000 Random Array Offsets +(Max Array Offset: 125mm with $R_{QZ}=150\text{mm}$ ) + +1000 Random Array Offsets +(Max Array Offset: 125mm with $R_{QZ}=150\text{mm}$ ) + +250 Random Array Offsets +(Max Array Offset: 125mm with $R_{QZ}=150\text{mm}$ ) + +![Figure 5.1.4.4-8: Illustration of 100k (left) vs 1k (middle) vs 250 (right) offsets. The figure shows three circular plots representing the distribution of random array offsets in a 2D plane (x, y) with a vertical z-axis. The left plot for 100,000 offsets shows a dense, solid red circular area. The middle plot for 1,000 offsets shows a sparse distribution of red dots. The right plot for 250 offsets shows an even sparser distribution of red dots. All plots have a gray background and axes labeled x (red), y (green), and z (blue).](54bab05b404ce895e109a02e758a548a_img.jpg) + +Figure 5.1.4.4-8: Illustration of 100k (left) vs 1k (middle) vs 250 (right) offsets. The figure shows three circular plots representing the distribution of random array offsets in a 2D plane (x, y) with a vertical z-axis. The left plot for 100,000 offsets shows a dense, solid red circular area. The middle plot for 1,000 offsets shows a sparse distribution of red dots. The right plot for 250 offsets shows an even sparser distribution of red dots. All plots have a gray background and axes labeled x (red), y (green), and z (blue). + +**Figure 5.1.4.4-8: Illustration of 100k (left) vs 1k (middle) vs 250 (right) offsets.** + +The results summarizing the different simulations are tabulated in Table 5.1.4.4-3. The results show that regardless of range length and antenna configuration, the difference in mean error and standard deviation is almost insignificant. + +**Table 5.1.4.4-3: Statistical results of 100k vs 1k vs 250 EIRP CFFDNF offset simulations based on black&white-box approach with random antenna array offsets uniformly spaced within 12.5cm (PC3)/10cm (PC1) in a single hemisphere. The antenna array offsets were compensated.** + +| Antenna Configuration | Number of Offsets | Range Length [m] | Mean EIRP Error w.r.t. FF [dB] | Std. Dev of EIRP at NF BP [dB] | +|-----------------------|-------------------|------------------|--------------------------------|--------------------------------| +| 8x2 | 100k | 0.2 | 0.48 | 0.22 | +| | | 0.25 | 0.23 | 0.08 | +| | | 0.3 | 0.14 | 0.04 | +| | | 0.35 | 0.09 | 0.02 | +| | | 0.4 | 0.07 | 0.01 | +| | | 0.45 | 0.05 | 0.01 | +| | | 20 | 0.00 | 0.00 | +| 8x2 | 1k | 0.2 | 0.48 | 0.21 | +| | | 0.25 | 0.23 | 0.07 | +| | | 0.3 | 0.14 | 0.03 | +| | | 0.35 | 0.09 | 0.02 | +| | | 0.4 | 0.07 | 0.01 | +| | | 0.45 | 0.05 | 0.01 | +| | | 20 | 0.00 | 0.00 | +| 8x2 | 250 | 0.2 | 0.49 | 0.23 | +| | | 0.25 | 0.23 | 0.08 | +| | | 0.3 | 0.14 | 0.04 | +| | | 0.35 | 0.09 | 0.02 | +| | | 0.4 | 0.07 | 0.01 | +| | | 0.45 | 0.05 | 0.01 | +| | | 20 | 0.00 | 0.00 | +| 12x12 | 100k | 0.2 | 3.41 | 1.09 | +| | | 0.25 | 1.84 | 0.44 | +| | | 0.3 | 1.16 | 0.22 | +| | | 0.35 | 0.80 | 0.13 | +| | | 0.4 | 0.59 | 0.08 | +| | | 0.45 | 0.45 | 0.05 | +| | | 20 | 0.00 | 0.00 | +| 12x12 | 1k | 0.2 | 3.43 | 1.10 | +| | | 0.25 | 1.85 | 0.44 | +| | | 0.3 | 1.17 | 0.22 | +| | | 0.35 | 0.81 | 0.13 | +| | | 0.4 | 0.59 | 0.08 | +| | | 0.45 | 0.45 | 0.05 | +| | | 20 | 0.00 | 0.00 | +| 12x12 | 250 | 0.2 | 3.47 | 1.13 | +| | | 0.25 | 1.87 | 0.45 | +| | | 0.3 | 1.18 | 0.23 | +| | | 0.35 | 0.81 | 0.13 | +| | | 0.4 | 0.60 | 0.08 | +| | | 0.45 | 0.46 | 0.06 | +| | | 20 | 0.00 | 0.00 | + +Another investigation focused on the MUs at two different frequencies at opposite ends of FR2, i.e., 28GHz and 49GHz using the same fixed range lengths. The simulation results are tabulated in Table 5.1.4.4-5 which show that the MUs at 28GHz are larger than at 49GHz. + +As outlined in Table 5.1.4.4-4 below, the range lengths as a function of wavelength are different between those two frequencies. The MUs are smaller for 49GHz when compared to 28GHz since the distances in wavelength are larger for the 40GHz case. + +**Table 5.1.4.4-4: Range length vs frequency** + +| Range Length [m] | Frequency [GHz] | | +|------------------|------------------------|------------------------| +| | 28 | 49 | +| | Distance [ $\lambda$ ] | Distance [ $\lambda$ ] | +| 0.2 | 19 | 33 | +| 0.3 | 28 | 49 | +| 0.45 | 42 | 74 | +| 20 | 1868 | 3269 | + +**Table 5.1.4.4-5: Statistical results of 28GHz vs 49GHz EIRP CFFDNF offset simulations based on black&white-box approach with random antenna array offsets uniformly spaced within 12.5cm (PC3)/10cm (PC1) in a single** + +| Antenna Configuration | Simulation Frequency [GHz] | Range Length [m] | Mean EIRP Error w.r.t. FF [dB] | Std. Dev of EIRP at NF BP [dB] | +|-----------------------|----------------------------|------------------|---------------------------------|--------------------------------| +| 8x2 | 28 | 0.2 | 0.48 | 0.22 | +| | | 0.25 | 0.23 | 0.08 | +| | | 0.3 | 0.14 | 0.04 | +| | | 0.35 | 0.09 | 0.02 | +| | | 0.4 | 0.07 | 0.01 | +| | | 0.45 | 0.05 | 0.01 | +| | | 20 | 0.00 | 0.00 | +| 8x2 | 49 | 0.2 | 0.16 | 0.07 | +| | | 0.25 | 0.08 | 0.02 | +| | | 0.3 | 0.05 | 0.01 | +| | | 0.35 | 0.03 | 0.01 | +| | | 0.4 | 0.02 | 0.00 | +| | | 0.45 | 0.02 | 0.00 | +| | | 20 | 0.00 | 0.00 | + +Another investigation focused on whether Matlab which is using an analytical approximation of the radiation pattern of the antenna arrays in the NF and FF based on the superposition approach yields similar uncertainties as a full EM simulation tool, i.e., CST, which is calculating the NF and FF patterns based on a numerical approach. Figure 5.1.4.4-9 illustrates the differences of the simulated 8x2 antenna patterns between Matlab (solid lines) and CST (dashed lines) both for the FF interface distance of $2D^2/\lambda$ , i.e., 47cm at 28GHz with $D=5\text{cm}$ , (red lines) and the NF interface distance of , i.e., 7cm at 28GHz with $D=5\text{cm}$ , (blue lines) in two principal cuts. Clearly, the agreement between Matlab and CST simulations of a dipole-based antenna element array placed over a ground plane is very good in both NF and FF. The CST analyses which used a grid size of $1^\circ$ in $\Delta\theta$ and $\Delta\phi$ . Those results are summarized in Table 5.1.4.4-6 and assume that array offsets and the feed probe have been compensated. The simulations with the limited number of offsets assumed the same offsets were used in Matlab and CST. Overall, these results show that were good agreement between 100k and the limited number of offsets can be achieved and that the Matlab and CST simulations yield excellent agreement. + +![Two line graphs comparing antenna patterns. The top graph, 'Pattern in xz Plane', shows Normalized Pattern w.r.t. FF [dBm] vs theta [deg] from 0 to 180. The bottom graph, 'Pattern in xy Plane', shows Normalized Pattern w.r.t. FF [dBm] vs phi [deg] from -150 to 150. Both graphs compare Matlab (FF, NF) and CST (FF, NF) results.](c69f84a5cf3ebb8f0fc511e642d4c02a_img.jpg) + +Two line graphs comparing antenna patterns. The top graph, 'Pattern in xz Plane', shows Normalized Pattern w.r.t. FF [dBm] vs theta [deg] from 0 to 180. The bottom graph, 'Pattern in xy Plane', shows Normalized Pattern w.r.t. FF [dBm] vs phi [deg] from -150 to 150. Both graphs compare Matlab (FF, NF) and CST (FF, NF) results. + +Figure 5.1.4.4-9: Comparison of CST and Matlab 8x2 antenna pattern. + +Table 5.1.4.4-6: Statistical results of EIRP CFFDNF simulations performed with Matlab and CST. + +| Antenna Configuration | Simulation Tool | Number of Offsets | Range Length [m] | Max-Min EIRP at NF BP [dB] | Max EIRP Error w.r.t. FF [dB] | Mean EIRP Error w.r.t. FF [dB] | Std. Dev of EIRP at NF BP [dB] | +|-----------------------|-----------------|-------------------|------------------|----------------------------|-------------------------------|---------------------------------|--------------------------------| +| 8x2 | Matlab | 100k | 0.2 | 1.17 | 1.36 | 0.48 | 0.22 | +| | | | 0.25 | 0.37 | 0.50 | 0.23 | 0.08 | +| | | | 0.3 | 0.17 | 0.26 | 0.14 | 0.04 | +| 8x2 | Matlab | 500 | 0.2 | 1.05 | 1.25 | 0.48 | 0.22 | +| | | | 0.25 | 0.34 | 0.47 | 0.23 | 0.07 | +| | | | 0.3 | 0.16 | 0.25 | 0.14 | 0.03 | +| 8x2 | CST | 500 | 0.2 | 0.93 | 1.10 | 0.42 | 0.19 | +| | | | 0.25 | 0.34 | 0.45 | 0.22 | 0.07 | +| | | | 0.3 | 0.18 | 0.26 | 0.14 | 0.04 | +| 12x12 | Matlab | 100k | 0.25 | 2.07 | 3.26 | 1.84 | 0.44 | +| | | | 0.3 | 1.02 | 1.85 | 1.16 | 0.22 | +| | | | 0.35 | 0.58 | 1.19 | 0.80 | 0.13 | +| 12x12 | CST | 500 | 0.25 | 2.15 | 3.45 | 1.98 | 0.47 | +| | | | 0.3 | 1.09 | 2.00 | 1.26 | 0.24 | +| | | | 0.35 | 0.63 | 1.31 | 0.89 | 0.14 | + +The results for the other antenna configurations are tabulated in Table 5.1.4.4-7. + +**Table 5.1.4.4-7: Statistical results of 100,000 EIRP CFFDNF simulations based on black&white-box approach with random antenna array offsets uniformly spaced within 12.5cm (PC3)/10cm (PC1) in a single hemisphere. The antenna array offsets were compensated.** + +| Antenna Configuration | Probe Pattern Compensation | Range Length [m] | Max-Min EIRP at NF BP [dB] | Max EIRP Error w.r.t. FF [dB] | Mean EIRP Error w.r.t. FF [dB] | Std. Dev of EIRP at NF BP [dB] | +|-----------------------|----------------------------|------------------|----------------------------|-------------------------------|---------------------------------|--------------------------------| +| 4x1 | yes | 0.2 | 0.10 | 0.11 | 0.04 | 0.02 | +| | | 0.25 | 0.03 | 0.04 | 0.02 | 0.01 | +| | | 0.3 | 0.01 | 0.02 | 0.01 | 0.00 | +| | | 0.35 | 0.01 | 0.01 | 0.01 | 0.00 | +| | | 0.4 | 0.01 | 0.01 | 0.01 | 0.00 | +| | | 0.45 | 0.00 | 0.01 | 0.00 | 0.00 | +| | | 20 | 0.00 | 0.00 | 0.00 | 0.00 | +| | no | 0.2 | 7.19 | 7.21 | 2.73 | 1.84 | +| | | 0.25 | 4.32 | 4.33 | 1.68 | 1.12 | +| | | 0.3 | 2.91 | 2.92 | 1.15 | 0.76 | +| | | 0.35 | 2.10 | 2.11 | 0.84 | 0.55 | +| | | 0.4 | 1.59 | 1.60 | 0.64 | 0.42 | +| | | 0.45 | 1.25 | 1.25 | 0.50 | 0.33 | +| | | 20 | 0.00 | 0.00 | 0.00 | 0.00 | +| 12x12 | yes | 0.2 | 5.38 | 7.24 | 3.41 | 1.09 | +| | | 0.25 | 2.07 | 3.26 | 1.84 | 0.44 | +| | | 0.3 | 1.02 | 1.85 | 1.16 | 0.22 | +| | | 0.35 | 0.58 | 1.19 | 0.80 | 0.13 | +| | | 0.4 | 0.36 | 0.82 | 0.59 | 0.08 | +| | | 0.45 | 0.24 | 0.61 | 0.45 | 0.05 | +| | | 20 | 0.00 | 0.00 | 0.00 | 0.00 | +| | no | 0.2 | 5.63 | 7.49 | 5.07 | 1.41 | +| | | 0.25 | 3.05 | 4.25 | 2.89 | 0.73 | +| | | 0.3 | 1.98 | 2.81 | 1.88 | 0.47 | +| | | 0.35 | 1.40 | 2.02 | 1.33 | 0.33 | +| | | 0.4 | 1.05 | 1.52 | 0.99 | 0.25 | +| | | 0.45 | 0.82 | 1.19 | 0.77 | 0.20 | +| | | 20 | 0.00 | 0.00 | 0.00 | 0.00 | + +The simulation results from two different companies using the same simulation assumptions are tabulated in Table 5.1.4.4-8. + +**Table 5.1.4.4-8: CFFDNF simulation results utilizing black&white-box with antenna array offset and feed antenna pattern compensated.** + +| Antenna Config. | Range Length [m] | Company A (using Matlab and 100k Offsets) | | Company A (using CST and 500 Offsets) | | Company B (using Matlab and 500 Offsets) | | +|-----------------|------------------|-------------------------------------------|--------------------------------|---------------------------------------|--------------------------------|------------------------------------------|--------------------------------| +| | | Mean EIRP Error w.r.t. FF [dB] | Std. Dev of EIRP at NF BP [dB] | Mean EIRP Error w.r.t. FF [dB] | Std. Dev of EIRP at NF BP [dB] | Mean EIRP Error w.r.t. FF [dB] | Std. Dev of EIRP at NF BP [dB] | +| 4x1 | 0.2 | 0.04 | 0.02 | | | 0.034 | 0.015 | +| | 0.25 | 0.02 | 0.01 | | | 0.016 | 0.005 | +| | 0.3 | 0.01 | 0.00 | | | 0.010 | 0.002 | +| | 0.35 | 0.01 | 0.00 | | | 0.006 | 0.003 | +| | 0.4 | 0.01 | 0.00 | | | 0.003 | 0.001 | +| | 0.45 | 0.00 | 0.00 | | | 0.002 | 0.000 | +| | 20 | 0.00 | 0.00 | | | 0.000 | 0.000 | +| 8x2 | 0.2 | 0.48 | 0.22 | 0.42 | 0.19 | 0.391 | 0.174 | +| | 0.25 | 0.23 | 0.08 | 0.22 | 0.07 | 0.188 | 0.058 | +| | 0.3 | 0.14 | 0.04 | 0.14 | 0.04 | 0.113 | 0.026 | +| | 0.35 | 0.09 | 0.02 | | | 0.075 | 0.016 | +| | 0.4 | 0.07 | 0.01 | | | 0.054 | 0.008 | +| | 0.45 | 0.05 | 0.01 | | | 0.041 | 0.006 | +| | 20 | 0.00 | 0.00 | | | 0.000 | 0.000 | +| 12x12 | 0.2 | 3.41 | 1.09 | | | 2.697 | 0.832 | +| | 0.25 | 1.84 | 0.44 | 1.98 | 0.47 | 1.450 | 0.333 | +| | 0.3 | 1.16 | 0.22 | 1.26 | 0.24 | 0.913 | 0.166 | +| | 0.35 | 0.80 | 0.13 | 0.89 | 0.14 | 0.627 | 0.097 | +| | 0.4 | 0.59 | 0.08 | | | 0.460 | 0.061 | +| | 0.45 | 0.45 | 0.05 | | | 0.351 | 0.040 | +| | 20 | 0.00 | 0.00 | | | 0.000 | 0.000 | + +While it has always been argued that TRP can be tested in the near-field due to conservation of power, no clear measurement uncertainty analyses have been presented to quantify the errors. The findings for measurement uncertainties when testing TRP in the near field using CFFDNF are presented next. + +An analysis of the impact on measurement uncertainty by testing TRP in the NF was performed according to the assumption for TRP offsets in Table 5.1.2.1-1. In this analysis, near-field effects of the antenna pattern were taken into account. Figure 5.1.4.4-10 below illustrates the differences in the 8x2 antenna pattern at the $2D^2/\lambda$ distance (a) and at $1/8^{\text{th}}$ of that distance (b). + +![Figure 5.1.4.4-10: Radiation pattern of the 8x2 antenna array. The figure shows two 3D surface plots of the radiation pattern. The left plot represents the pattern at the far-field distance of 2D²/λ, showing a broad main lobe and several side lobes. The right plot represents the pattern in the near-field at 1/8th of the far-field distance, showing a more concentrated main lobe and different side lobe structures. Both plots include a color scale on the right ranging from -15 dB (blue) to 10 dB (red). Each plot also includes a small 2D polar plot at the bottom left showing the horizontal plane radiation pattern.](930335a43c8196e391f87e6860db4d45_img.jpg) + +Figure 5.1.4.4-10: Radiation pattern of the 8x2 antenna array. The figure shows two 3D surface plots of the radiation pattern. The left plot represents the pattern at the far-field distance of 2D²/λ, showing a broad main lobe and several side lobes. The right plot represents the pattern in the near-field at 1/8th of the far-field distance, showing a more concentrated main lobe and different side lobe structures. Both plots include a color scale on the right ranging from -15 dB (blue) to 10 dB (red). Each plot also includes a small 2D polar plot at the bottom left showing the horizontal plane radiation pattern. + +**Figure 5.1.4.4-10: Radiation pattern of the 8x2 antenna array at $2D^2/\lambda$ FF distance (left) and in NF at $1/8^{\text{th}}$ of FF distance (right)** + +Table 5.1.4.4-9 below summarizes the impact of the approaches with and without offset correction on TRP MU. + +**Table 5.1.4.4-9: Impact of TRP measurement with and without offset correction on MU** + +| Antenna Configuration | Range Length (cm) | Constant Step-Size Grid Step Size $\Delta\theta=\Delta\phi$ [°] | With Offset Correction | | Without Offset Correction | | +|-----------------------|-------------------|-----------------------------------------------------------------|------------------------|--------------------|---------------------------|--------------------| +| | | | Mean TRP Error [dB] | TRP Std. Dev. [dB] | Mean TRP Error [dB] | TRP Std. Dev. [dB] | +| 8x2 | 20 | 5 | 0.01 | 0.04 | 0.39 | 0.24 | +| | | 10 | 0.03 | 0.17 | 0.39 | 0.29 | +| | 25 | 5 | 0.02 | 0.02 | 0.24 | 0.14 | +| | | 10 | 0.03 | 0.08 | 0.24 | 0.16 | +| | 30 | 5 | 0.02 | 0.01 | 0.16 | 0.09 | +| | | 10 | 0.03 | 0.04 | 0.16 | 0.10 | +| | 35 | 5 | 0.02 | 0.01 | 0.12 | 0.07 | +| | | 10 | 0.04 | 0.03 | 0.12 | 0.07 | +| | 40 | 5 | 0.02 | 0.01 | 0.09 | 0.05 | +| | | 10 | 0.04 | 0.03 | 0.09 | 0.05 | + +Additionally, CDF curves for the various simulation results are presented in Figure 5.1.4.4-11 below. + +![Figure 5.1.4.4-11: Empirical CDF plot showing the distribution of simulated TRP measurements. The x-axis is 'Simulated TRP(dB)' ranging from -4 to -0.5. The y-axis is 'cdf' ranging from 0 to 1. The plot compares 'no correction' (dashed lines) and 'correction' (solid lines) for various range lengths: 20cm, 25cm, 28cm, 32cm, 43cm, and 100cm. A 'Reference' line is shown as a vertical black line at approximately -2.2 dB. The 'correction' curves are tightly clustered around the reference line, while the 'no correction' curves are shifted to the right, indicating higher TRP values.](48fc91e19c1a9b6674b120fbdd89b203_img.jpg) + +Figure 5.1.4.4-11: Empirical CDF plot showing the distribution of simulated TRP measurements. The x-axis is 'Simulated TRP(dB)' ranging from -4 to -0.5. The y-axis is 'cdf' ranging from 0 to 1. The plot compares 'no correction' (dashed lines) and 'correction' (solid lines) for various range lengths: 20cm, 25cm, 28cm, 32cm, 43cm, and 100cm. A 'Reference' line is shown as a vertical black line at approximately -2.2 dB. The 'correction' curves are tightly clustered around the reference line, while the 'no correction' curves are shifted to the right, indicating higher TRP values. + +**Figure 5.1.4.4-11: Distribution of simulated TRP measurements with and without offset correction** + +Next, TRP simulation results are presented for the CFFDNF methodology for PC1 based on the 12x12 antenna configuration following the assumptions outlined in Section 5.1.4.3. The Matlab simulation results are summarized in Table 5.1.4.4-10 with and without path loss correction. For these simulations, a uniform angular grid spacing was applied in $\theta$ and $\phi$ to the TRP grid. It should be noted that the antenna array offset must be known/declared when the path loss correction is applied. + +**Table 5.1.4.4-10: CFFDNF TRP simulation results with and without path loss correction for PC1 devices (12x12 antenna configuration) with a uniform angular spacing in $\theta$ and $\phi$ .** + +| Antenna Configuration | Range Length [cm] | Constant Step-Size Grid Step Size $\Delta\theta=\Delta\phi$ [°] | With Path Loss Correction | | Without Path Loss Correction | | +|-----------------------|-------------------|-----------------------------------------------------------------|---------------------------|--------------------|------------------------------|--------------------| +| | | | Mean TRP Error [dB] | TRP Std. Dev. [dB] | Mean TRP Error [dB] | TRP Std. Dev. [dB] | +| 12x12 | 20 | 5 | 0.02 | 0.02 | 0.27 | 0.16 | +| | | 7.5 | 0.01 | 0.19 | 0.27 | 0.23 | +| | 25 | 5 | 0 | 0.02 | 0.17 | 0.1 | +| | 30 | 5 | 0.02 | 0.02 | 0.11 | 0.06 | +| | 35 | 5 | 0.02 | 0.02 | 0.08 | 0.05 | +| | 40 | 5 | 0.03 | 0.02 | 0.06 | 0.04 | +| | 45 | 5 | 0.03 | 0.02 | 0.05 | 0.03 | + +For PC1, TRP test cases with a uniform angular spacing in $\theta$ and $\phi$ do not require additional measurement uncertainty due to reduced range length for + +- range lengths exceeding 20cm if the path loss correction is applied for measurement grids with step size of at most $5^\circ$ (unique number of grid points: 2522) +- for range lengths exceeding 35cm if the path loss correction is not applied for measurement grids with step size of at most $5^\circ$ (unique number of grid points: 2522) + +Given the large number of grid points, additional test time reduction techniques based on non-uniform grids were investigated. The focus of this investigation is for the antenna array offset applied, i.e., the offset must be known/declared which can be used to determine the NF beam peak direction. The idea here is to apply a fine grid around the NF beam peak direction to capture the main portion of the very directive beam while a coarse grid around the remaining portion of the sphere is applied. This is further illustrated in Figure 5.1.4.4-12 with the following non-uniform TRP grid assumptions: + +- The known NF beam is shown with the large grey dot. On top, the NF beam peak is assumed at $(0^\circ, 0^\circ)$ while the NF beam peak on the bottom is assumed at $(45^\circ, 45^\circ)$ . +- The red grid points are within a $\pm 20^\circ$ cone centred around the NF beam peak with $\Delta\theta = \Delta\phi = 2.5^\circ$ . +- The cyan grid points are outside a $\pm 20^\circ$ cone centred around the NF beam peak with $\Delta\theta = \Delta\phi = 10^\circ$ . + +![Figure 5.1.4.4-12: Visualization of non-uniform TRP grids for NF beam at (0°, 0°) on top and at (45°, 45°) on bottom. The figure consists of four sub-views of a sphere representing the measurement grid. Top-left: View from the Z-axis showing the NF beam peak at (0°, 0°) with a dense red grid around it and a sparse cyan grid elsewhere. Top-right: View from the Y-axis showing the NF beam peak at (0°, 0°) as a small red dot. Bottom-left: View from the Z-axis showing the NF beam peak at (45°, 45°) with a dense red grid around it and a sparse cyan grid elsewhere. Bottom-right: View from the X-axis showing the NF beam peak at (45°, 45°) as a small red dot. In all views, the red grid points are concentrated in a cone around the peak direction, while the cyan grid points are distributed more sparsely over the rest of the sphere.](f9625fa3465b009051f85d91cfa1da7e_img.jpg) + +Figure 5.1.4.4-12: Visualization of non-uniform TRP grids for NF beam at (0°, 0°) on top and at (45°, 45°) on bottom. The figure consists of four sub-views of a sphere representing the measurement grid. Top-left: View from the Z-axis showing the NF beam peak at (0°, 0°) with a dense red grid around it and a sparse cyan grid elsewhere. Top-right: View from the Y-axis showing the NF beam peak at (0°, 0°) as a small red dot. Bottom-left: View from the Z-axis showing the NF beam peak at (45°, 45°) with a dense red grid around it and a sparse cyan grid elsewhere. Bottom-right: View from the X-axis showing the NF beam peak at (45°, 45°) as a small red dot. In all views, the red grid points are concentrated in a cone around the peak direction, while the cyan grid points are distributed more sparsely over the rest of the sphere. + +**Figure 5.1.4.4-12: Visualization of non-uniform TRP grids for NF beam at $(0^\circ, 0^\circ)$ on top and at $(45^\circ, 45^\circ)$ on bottom. Grid points in cyan (red) are outside (inside) the conical NF beam peak region.** + +Simulation with 2000 random offsets up to 10cm were performed together with random permutations of the beam peak direction (rotation in $\theta$ , $\phi$ , and twist $\alpha$ as outlined in Clause G.1 of [3]). Table 5.1.4.4-11 shows the simulation results + +for the non-uniform measurement grids considered the most suitable for PC1 devices. The average number of unique grid points based on all simulations investigated is ~900 which shows a significant test time reduction with the same TRP MUs as the 5° measurement grid with uniform spacing in $\theta$ and $\phi$ , Table 5.1.4.4-10. For PC1, TRP test cases with a non-uniform angular spacing in $\theta$ and $\phi$ do not require additional measurement uncertainty due to reduced range length for range lengths exceeding 20cm if the path loss correction is applied for measurement grids with step size of 2.5° within $\pm 20^\circ$ of the NF beam peak and step size of 10° outside $\pm 20^\circ$ of the NF beam peak. + +**Table 5.1.4.4-11: CFFDNF TRP simulation results with path loss correction for PC1 devices (12x12 antenna configuration) using non-uniform measurement grids.** + +| Antenna Configuration | Range Length [cm] | Cone width ( $\pm$ ) [°] | Constant Step-Size Grid Step Size outside cone $\Delta\theta=\Delta\phi$ [°] | Constant Step-Size Grid Step Size within cone $\Delta\theta=\Delta\phi$ [°] | Average number of unique grid points | With Path Loss Correction | | +|-----------------------|-------------------|--------------------------|------------------------------------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------------|---------------------------|--------------------| +| | | | | | | Mean TRP Error [dB] | TRP Std. Dev. [dB] | +| 12x12 | 20 | 20 | 10 | 2.5 | 917 | 0.02 | 0.04 | +| | 25 | | | | 916 | 0.01 | 0.04 | +| | 30 | | | | 914 | 0.02 | 0.04 | +| | 35 | | | | 914 | 0.03 | 0.04 | +| | 40 | | | | 914 | 0.04 | 0.04 | +| | 45 | | | | 914 | 0.04 | 0.04 | + +Similar simulations were performed for PC3 devices with the 8x2 antenna configuration with random offsets up to 12.5cm. The results for the non-uniform grids are tabulated in Table 5.1.4.4-12. + +**Table 5.1.4.4-12: CFFDNF TRP simulation results with path loss correction for PC3 devices (8x2 antenna configuration) using non-uniform measurement grids.** + +| Antenna Configuration | Range Length [cm] | Cone width ( $\pm$ ) [°] | Constant Step-Size Grid Step Size outside cone $\Delta\theta=\Delta\phi$ [°] | Constant Step-Size Grid Step Size within cone $\Delta\theta=\Delta\phi$ [°] | Average number of unique grid points | With Path Loss Correction | | +|-----------------------|-------------------|--------------------------|------------------------------------------------------------------------------|-----------------------------------------------------------------------------|--------------------------------------|---------------------------|--------------------| +| | | | | | | Mean TRP Error [dB] | TRP Std. Dev. [dB] | +| 8x2 | 20 | 30 | 15 | 5 | 428 | 0.05 | 0.05 | +| | 25 | | | | 427 | 0.06 | 0.04 | +| | 30 | | | | 427 | 0.06 | 0.04 | +| | 35 | | | | 427 | 0.06 | 0.04 | +| | 40 | | | | 427 | 0.06 | 0.04 | +| | 45 | | | | 426 | 0.06 | 0.04 | + +For PC3, TRP test cases with a non-uniform angular spacing in $\theta$ and $\phi$ do not require additional measurement uncertainty due to reduced range length for range lengths exceeding 20cm if the path loss correction is applied for measurement grids with step size of 5° within $\pm 30^\circ$ of the NF beam peak and step size of 15° outside $\pm 30^\circ$ of the NF beam peak. + +The comparison of the TRP measurement grid parameters and the min. number of grid points are tabulated in Table 5.1.4.4-13 when the antenna array offset is known and compensated with angular grid spacings placed uniformly and non-uniformly in $\theta$ and $\phi$ . Clearly, the non-uniform TRP measurement grid approach is especially beneficial in terms of test time reduction. The TRP calculation is left to the system vendor as there are different approaches to determine TRP, e.g., interpolation of all results to the fine grid vs partial TRPs calculated within the cone and outside the cone. + +**Table 5.1.4.4-13: Comparison of the TRP measurement grid parameters for PC3 and PC1 including potential test time improvement. The simulations assume the offset is known/declared and the path loss correction was applied.** + +| Antenna Config. | Range Length [cm] | Non-uniform angular spacing | | | | Uniform angular spacing | | Potential Test Time Improvement with non-uniform angular spacing in $\theta$ and $\phi$ (factor) | +|-----------------|-------------------|-----------------------------------|---------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|--------------------------------------|--------------------------------------------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------| +| | | Cone width ( $\pm$ ) [ $^\circ$ ] | Constant Step-Size Grid Step Size outside cone $\Delta\theta=\Delta\phi$ [ $^\circ$ ] | Constant Step-Size Grid Step Size within cone $\Delta\theta=\Delta\phi$ [ $^\circ$ ] | Average Number of unique grid points | Constant Step-Size Grid Step Size $\Delta\theta=\Delta\phi$ [ $^\circ$ ] | Number of unique grid points | | +| 8x2 | 20 | 30 | 15 | 5 | 427 | 5 | 2522 | 5.9 | +| | 25 | | | | | 10 | 614 | 1.4 | +| 12x12 | 20 | 20 | 10 | 2.5 | 915 | 5 | 2522 | 2.8 | + +Additional simulations were performed based on the assumption that the DUT changes the antenna configuration between high-UL power operation, e.g., 8x2 configuration, and low-UL power operation, e.g., 4x1, 1x2, 1x1. Sample configurations of the active antenna elements placed near the edge and the centre are visualized in Figure 5.1.4.4-13 for the 8x2 antenna configuration. + +![Figure 5.1.4.4-13: 8x2 configuration for high UL power operation (left) and sample configurations for low UL power operation. The diagram shows seven antenna element grids. The first grid is an 8x2 configuration with all 16 elements active (orange). The next two are 4x1 configurations: 'Edge' (4 elements on the left column active) and 'Centre' (4 elements in the middle two columns active). The next two are 1x2 configurations: 'Edge' (1 element in the first column active) and 'Centre' (1 element in the second column active). The last two are 1x1 configurations: 'Edge' (1 element in the first column active) and 'Centre' (1 element in the second column active). A legend at the bottom indicates orange squares are 'Active Antenna Element' and grey squares are 'Inactive Antenna Element'.](552328a9daaf3bc0069424b500025880_img.jpg) + +High-UL Power 8x2 Configuration      Sample Low-UL Power 4x1 Configurations      Sample Low-UL Power 1x2 Configurations      Sample Low-UL Power 1x1 Configurations + +■ Active Antenna Element    ■ Inactive Antenna Element + +Figure 5.1.4.4-13: 8x2 configuration for high UL power operation (left) and sample configurations for low UL power operation. The diagram shows seven antenna element grids. The first grid is an 8x2 configuration with all 16 elements active (orange). The next two are 4x1 configurations: 'Edge' (4 elements on the left column active) and 'Centre' (4 elements in the middle two columns active). The next two are 1x2 configurations: 'Edge' (1 element in the first column active) and 'Centre' (1 element in the second column active). The last two are 1x1 configurations: 'Edge' (1 element in the first column active) and 'Centre' (1 element in the second column active). A legend at the bottom indicates orange squares are 'Active Antenna Element' and grey squares are 'Inactive Antenna Element'. + +**Figure 5.1.4.4-13: 8x2 configuration for high UL power operation (left) and sample configurations for low UL power operation** + +The following high-level procedure for the CFFDNF test methodology as presented in clause 5.1.4.2 for the black&white-box approach was used: + +- Step 1: form the beam towards FF antenna in the Tx beam peak direction for the higher array order, i.e. 8x2, then activate UBF. +- Step 2: set the NF probe antenna towards the NF TX beam peak direction, determined from the antenna offset, range length, and FF beam peak direction for the higher array order, i.e., 8x2. +- Step 3: set UE array to transmit with the lower power mode, i.e., by reducing the number of active elements. +- Step 4: Measure NF power of the UE for the lower power mode in the NF beam peak direction determined in Step 2. +- Step 5: Calculate the EIRP from the NF power in Step 4 by: + - Adding the composite loss to the centre of the QZ + +- Compensate the actual measurement distance to the centre of the UE array, using the 8x2 order +- Applying the probe antenna NF correction. + +The simulation results from two companies are for the steps outlined above and the PC3 worst-case array assumption of 8x2 and the 0.2m NF range length are shown in Table 5.1.4.4-14. It can be observed that + +- The MUs for the case when the antenna array does not change its antenna configuration, i.e., the low-UL and high-UL configuration is 8x2, matches the MU presented in Table 5.1.4.4-1 +- The MUs for the sub-array configurations, i.e., {4x1, 1x1, 1x2}, are the same or generally smaller than the MU for the 8x2 case + +**Table 5.1.4.4-14: CFFDNF simulation results utilizing black&white-box with antenna array offset and feed antenna pattern compensated based on the assumption that the antenna configuration could change from 8x2 (high-UL power configuration).** + +| Company | Number of Offsets | Range Length [m] | NF BP Direction determined from | Antenna Centre used for Path Loss Compensation | MUs | Low Power Antenna Config | | | | | | | +|---------|-------------------|------------------|------------------------------------------|------------------------------------------------|-----------------|--------------------------|------------|--------------|------------|--------------|------------|--------------| +| | | | | | | 8x2 | 4x1 "edge" | 4x1 "centre" | 1x1 "edge" | 1x1 "centre" | 1x2 "edge" | 1x2 "centre" | +| A | 5000 | 0.2 | Reference Antenna (High-UL Power) | Reference (High UL-Power) | Mean Error [dB] | 0.48 | 0.48 | 0.04 | 0.20 | 0.01 | 0.20 | 0.01 | +| | | | | | Std. Dev. [dB] | 0.22 | 0.22 | 0.02 | 0.09 | 0.00 | 0.09 | 0.00 | +| B | 500 | 0.2 | Reference Antenna (High-UL Power) offset | Reference (High UL-Power) | Mean Error [dB] | | 0.43 | 0.06 | 0.21 | 0.03 | 0.21 | 0.03 | +| | | | | | Std. Dev. [dB] | | 0.20 | 0.03 | 0.10 | 0.02 | 0.10 | 0.01 | +| A | 5000 | 0.2 | Sub-Array (Low-UL Power) offset | Sub-Array (Low-UL Power) offset | Mean Error [dB] | | 0.04 | 0.04 | 0.00 | 0.00 | 0.00 | 0.00 | +| | | | | | Std. Dev. [dB] | | 0.02 | 0.02 | 0.00 | 0.00 | 0.00 | 0.00 | + +Separate analyses were performed that take the same antenna array offsets into account but instead of determining the NF beam peak direction and the applying the path loss compensation with respect to the phase centre of the 8x2 antenna array, the NF beam peak direction and offset compensation was based on the centre of the sub-antenna array configuration {4x1, 1x1, 1x2}. These results are presented in the third row of the table above. Clearly, the MUs for the 4x1 configuration match the MUs presented in Table 5.1.4.4-7. + +Similar simulations were performed for the 12x12 (PC1) baseline/high-UL power configuration and various {8x2, 4x1, 1x1, 1x2} sub-array configurations for the low-UL power operation; those simulations are shown in Table 5.1.4.4-15. + +**Table 5.1.4.4-15: CFFDNF simulation results utilizing black&white-box with antenna array offset and feed antenna pattern compensated based on the assumption that the antenna configuration could change from 12x12 (high-UL power configuration).** + +| NF BP Direction determined from | Antenna Centre used for Path Loss Compensation | MUs | Low Power Antenna Config | | | | | | | | | +|------------------------------------------|------------------------------------------------|-----------------|--------------------------|------------|--------------|------------|--------------|------------|--------------|------------|--------------| +| | | | 12x12 | 8x2 "edge" | 8x2 "centre" | 4x1 "edge" | 4x1 "centre" | 1x1 "edge" | 1x1 "centre" | 1x2 "edge" | 1x2 "centre" | +| Reference Antenna (High-UL Power) offset | Reference (High UL-Power) | Mean Error [dB] | 0.45 | 0.30 | 0.05 | 0.23 | 0.00 | 0.01 | 0.00 | 0.13 | 0.00 | +| | | Std. Dev. [dB] | 0.05 | 0.04 | 0.01 | 0.03 | 0.00 | 0.00 | 0.00 | 0.02 | 0.00 | +| Sub-Array (Low-UL Power) offset | Sub-Array (Low-UL Power) offset | Mean Error [dB] | | 0.05 | 0.05 | 0.00 | 0.00 | | | | | +| | | Std. Dev. [dB] | | 0.01 | 0.01 | 0.00 | 0.00 | | | | | + +Similar observations as for the PC3 analyses can be drawn: + +- The MUs for the case when the antenna array does not change its antenna configuration, i.e., the low-UL and high-UL configuration is 12x12, matches the MU presented earlier which is captured in Table 5.1.4.4-3 +- The MUs for the sub-array configurations, i.e., {8x2, 4x1, 1x1, 1x2}, are smaller than the MU for the 12x12 case (which is serving as the reference for PC1 MU purposes) +- The MUs for the case when the actual offset position of the sub-array is declared match the MUs determined in previous simulations, e.g., the MUs for the 8x2 antenna and for 0.45cm range length match the MUs for the 8x2 antenna array shown in Table 5.1.4.4-3. +- It can therefore be concluded that for CFFDNF (with black&white-box approach): If the phase centre of the reference antenna array (high UL-power operation: 8x2 for PC3, 12x12 for PC1) is declared, the previously determined MUs hold if the antenna changes its configuration for the low-UL power operation +- If the phase centre of the sub-antenna array used for low-UL power operation is declared, the previously determined MUs can be further reduced + +#### 5.1.4.5 Simulation results for CFFNF (using Black & White-Box Approach) + +In this clause, results for near-field and far-field simulations of $N_y \times N_z$ antenna arrays for the CFFNF methodology based on the black&white-box approach, i.e., the location of active antenna panel for the FF beam peak direction is known/declared, are presented. The simulation assumptions are, for the most part, the same as those in Table 5.1.4.3-1. + +Initial simulations were performed with an EM simulator, CST. The grid size used for the CST simulations had step sizes of $1^\circ$ in $\Delta\theta$ and $\Delta\phi$ . Given the previous observation regarding the need to offset the probe pattern, the simulations for CFFNF using black&white approach only focused on the feed probe pattern compensated. + +The CFFNF results are tabulated in Table 5.1.4.5-1 for 8x2 (PC3) and in Table 5.1.4.5-2 for 12x12 (PC1) and compared with the CFFDNF results (same as those in Table 5.1.4.4-8). Clearly, the measurement at the additional radius $r_2$ significantly reduces the measurement uncertainties and allows EIRP/EIS measurements of PC3 (PC1) devices at 21cm (31cm) range length without additional (with very small) MU. These simulations assume that $r_2$ is either $r_2=r_1+1\text{cm}$ or $r_2=r_1+2\text{cm}$ . + +Subsequent simulations were performed with Matlab based on the same assumptions. The PC3 results are tabulated in Table 5.1.4.5-3 with results from two different companies while the PC1 results are tabulated in Table 5.1.4.5-4. + +**Table 5.1.4.5-1: Statistical results of 500 EIRP CFFNF & CFFDNF CST simulations based on black&white-box approach with random 8x2 antenna array offsets uniformly spaced within 12.5cm in a single hemisphere. The antenna array offsets and probe pattern were compensated.** + +| Method | Range Length(m) | Max-Min EIRP (dB) | Max Error w.r.t. FF (dB) | Mean Error (dB) | Std. Dev (dB) | +|----------------------------------------------|-----------------|-------------------|--------------------------|------------------|---------------| +| CFFNF<br>B&W Box<br>( $r_2=r_1+1\text{cm}$ ) | 0.21 | 0.24 | 0.16 | 0.04 | 0.04 | +| | 0.26 | 0.22 | 0.13 | 0.03 | 0.03 | +| | 0.31 | 0.25 | 0.15 | 0.03 | 0.03 | +| CFFNF<br>B&W Box<br>( $r_2=r_1+2\text{cm}$ ) | 0.22 | 0.30 | 0.23 | 0.04 | 0.04 | +| | 0.27 | 0.25 | 0.16 | 0.03 | 0.04 | +| | 0.32 | 0.25 | 0.17 | 0.03 | 0.04 | +| CFFDNF<br>B&W Box | 0.20 | 0.93 | 1.10 | 0.42 | 0.19 | +| | 0.25 | 0.34 | 0.45 | 0.22 | 0.07 | +| | 0.30 | 0.18 | 0.26 | 0.14 | 0.04 | + +Note: The range length for CFFNF with black&white-box approach is reported for radius $r_2 > r_1$ . + +**Table 5.1.4.5-2: Statistical results of 500 EIRP CFFNF & CFFDNF CST simulations based on black&white-box approach with random 12x12 antenna array offsets uniformly spaced within 10cm in a single hemisphere. The antenna array offsets and probe pattern were compensated.** + +| Method | Range Length(m) | Max-Min EIRP (dB) | Max Error w.r.t. FF (dB) | Mean Error (dB) | Std. Dev (dB) | +|----------------------------------------------|-----------------|-------------------|--------------------------|------------------|---------------| +| CFFNF<br>B&W Box<br>( $r_2=r_1+1\text{cm}$ ) | 0.26 | 0.74 | 0.89 | 0.36 | 0.15 | +| | 0.31 | 0.40 | 0.42 | 0.18 | 0.07 | +| | 0.36 | 0.32 | 0.29 | 0.10 | 0.05 | +| CFFNF<br>B&W Box<br>( $r_2=r_1+2\text{cm}$ ) | 0.27 | 0.73 | 0.87 | 0.36 | 0.15 | +| | 0.32 | 0.37 | 0.39 | 0.18 | 0.07 | +| | 0.37 | 0.28 | 0.25 | 0.10 | 0.05 | +| CFFDNF<br>B&W Box | 0.25 | 2.15 | 3.45 | 1.98 | 0.47 | +| | 0.30 | 1.09 | 2.00 | 1.26 | 0.24 | +| | 0.35 | 0.63 | 1.31 | 0.89 | 0.14 | + +Note: The range length for CFFNF with black&white-box approach is reported for radius $r_2 > r_1$ . + +**Table 5.1.4.5-3: Statistical results of EIRP CFFNF offset simulations based on black&white-box approach with random antenna array offsets uniformly spaced within 12.5cm (PC3) in a single hemisphere. The antenna array offsets were compensated.** + +| Company ► ► ► ► ► | | | Company A | | Company B | | Company B | | +|------------------------------------------|------------------------|------------------------|------------------|---------------|------------------|---------------|------------------|---------------| +| Tool ► ► ► ► ► | | | CST | | Matlab | | Matlab | | +| Number of Offsets ► ► ► ► ► | | | 500 | | 500 | | 1000 | | +| Method | Range Length $r_1$ (m) | Range Length $r_2$ (m) | Mean Error (dB) | Std. Dev (dB) | Mean Error (dB) | Std. Dev (dB) | Mean Error (dB) | Std. Dev (dB) | +| CFFNF<br>B&W Box<br>$r_2=r_1+1\text{cm}$ | 0.2 | 0.21 | 0.04 | 0.04 | 0.06 | 0.03 | 0.03 | 0.02 | +| | 0.25 | 0.26 | 0.03 | 0.03 | 0.03 | 0.01 | 0.01 | 0 | +| | 0.3 | 0.31 | 0.03 | 0.03 | | | 0 | 0 | +| | 0.35 | 0.36 | | | | | 0 | 0 | +| | 0.4 | 0.41 | | | | | 0 | 0 | +| | 0.45 | 0.46 | | | | | 0 | 0 | +| CFFNF<br>B&W Box<br>$r_2=r_1+2\text{cm}$ | 20 | 20.01 | | | | | 0 | 0 | +| | 0.2 | 0.22 | 0.04 | 0.04 | | | 0.02 | 0.02 | +| | 0.25 | 0.27 | 0.03 | 0.04 | | | 0.01 | 0 | +| | 0.3 | 0.32 | 0.03 | 0.04 | | | 0 | 0 | +| | 0.35 | 0.37 | | | | | 0 | 0 | +| | 0.4 | 0.42 | | | | | 0 | 0 | +| | 0.45 | 0.47 | | | | | 0 | 0 | +| | 20 | 20.02 | | | | | 0 | 0 | + +**Table 5.1.4.5-4: Statistical results of EIRP CFFNF offset simulations based on black&white-box approach with random antenna array offsets uniformly spaced within 10cm (PC1) in a single hemisphere. The antenna array offsets were compensated.** + +| Tool ► ► ► ► ► | | CST | | Matlab | | +|---------------------------------------------------------------------------------------------------|------------------|------------------|---------------|------------------|---------------| +| Number of Offsets ► ► | | 500 | | 1000 | | +| Method | Range Length (m) | Mean Error (dB) | Std. Dev (dB) | Mean Error (dB) | Std. Dev (dB) | +| CFFNF | 0.26 | 0.36 | 0.15 | 0.30 | 0.12 | +| B&W Box | 0.31 | 0.18 | 0.07 | 0.13 | 0.04 | +| $r_2=r_1+1\text{cm}$ | 0.36 | 0.10 | 0.05 | 0.07 | 0.02 | +| CFFNF | 0.27 | 0.33 | 0.14 | 0.27 | 0.11 | +| B&W Box | 0.32 | 0.17 | 0.06 | 0.12 | 0.04 | +| $r_2=r_1+2\text{cm}$ | 0.37 | 0.10 | 0.04 | 0.06 | 0.02 | +| Note: The range length for CFFNF with black&white-box approach is reported for radius $r_2>r_1$ . | | | | | | + +#### 5.1.4.6 Simulation results for CFFNF (using Black-Box Approach) + +In this clause, results for near-field and far-field simulations of $N_y \times N_z$ antenna arrays for the CFFNF methodology are presented based on the black-box approach, i.e., the location active antenna panel for the FF beam peak direction is unknown while only the FF BP direction is known. The simulation assumptions are, for the most part, the same as those in Table 5.1.4.3-1. + +All simulations are performed with an EM simulator, CST. The grid size used for the CST simulations had step sizes of $1^\circ$ in $\Delta\theta$ and $\Delta\phi$ . Given the previous observation regarding the need to offset the probe pattern, the simulations for CFFNF using black&white approach only focused on the feed probe pattern compensated. + +The angular widths of the cone needed for the local searches as a function of the range length is tabulated in Table 5.1.4.6-1. + +**Table 5.1.4.6-1: Local search cone angles for PC3 device with maximum offset of 12.5cm** + +| Range Length [cm] | Single-Sided Cone Angle [deg] | +|-------------------|-------------------------------| +| 20 | 38.7 | +| 25 | 30.0 | +| 30 | 24.6 | +| 35 | 20.9 | + +Since the black-box approach utilizes/requires relatively wide area local searches at $r = r_1$ , e.g., the width of the sector is about $\pm 40^\circ$ for $r_1=20\text{cm}$ , with limited local searches at $r_2$ and $r_3$ as illustrated in Figure 5.1.4.2-2, the test time for the black-box approach is inherently longer than the black&white-box approach due to the 3 vs 2 radii and the need for local searches vs no local search requirements. On the other hand, this approach does not require the declaration of the active antenna array location. + +Suitable approaches to reduce the test time of these local searches include coarse and fine search approaches, e.g., Figures M.2.2-3 and M.2.2-4 of [6]. Alternatively, continuous non-demodulated EIRP measurements on sectors with fixed angular distance could be utilized to speed up the local searches, as illustrated in Figure 5.1.4.6-1 for BP directions near the poles. For this accelerated search approach, the positioner is moved continuously while the measurements are performed in close succession. + +![Figure 5.1.4.6-1: Stepped (left) vs continuous (right) search approach for EIRP for a FF BP near the pole. The figure shows two spherical coordinate systems. The left diagram shows a 'stepped' search approach where test points (red dots) are concentrated in a small sector around the known FF BP direction (black dot) near the Z-axis. The right diagram shows a 'continuous' search approach where test points are distributed across a larger sector around the known FF BP direction. A legend indicates: black dot for Known FF BP Direction, red dots for Local Search Test Points for r1 within sector around FF BP Direction, and blue dots for Grid points outside search local search sector.](1bc1bf231ada31f57cd9f0d8791b784b_img.jpg) + +Figure 5.1.4.6-1: Stepped (left) vs continuous (right) search approach for EIRP for a FF BP near the pole. The figure shows two spherical coordinate systems. The left diagram shows a 'stepped' search approach where test points (red dots) are concentrated in a small sector around the known FF BP direction (black dot) near the Z-axis. The right diagram shows a 'continuous' search approach where test points are distributed across a larger sector around the known FF BP direction. A legend indicates: black dot for Known FF BP Direction, red dots for Local Search Test Points for r1 within sector around FF BP Direction, and blue dots for Grid points outside search local search sector. + +**Figure 5.1.4.6-1: Stepped (left) vs continuous (right) search approach for EIRP for a FF BP near the pole.** + +Even for arbitrary FF BP directions not near the pole, a continuous scan over the sector, can be performed since the beam is locked with the UBF towards the FF beam peak direction. An illustration of this approach is in Figure 5.1.4.6-2. + +![Figure 5.1.4.6-2: Stepped (left) vs continuous (right) search approach for EIRP for an arbitrary FF BP direction. The figure shows two spherical coordinate systems. The left diagram shows a 'stepped' search approach where test points (red dots) are concentrated in a small sector around the known FF BP direction (black dot) at an arbitrary angle. The right diagram shows a 'continuous' search approach where test points are distributed across a larger sector around the known FF BP direction. A legend indicates: black dot for Known FF BP Direction, red dots for Local Search Test Points for r1 within sector around FF BP Direction, and blue dots for Grid points outside search local search sector.](a1849005b1686d3991afbbb3970f623d_img.jpg) + +Figure 5.1.4.6-2: Stepped (left) vs continuous (right) search approach for EIRP for an arbitrary FF BP direction. The figure shows two spherical coordinate systems. The left diagram shows a 'stepped' search approach where test points (red dots) are concentrated in a small sector around the known FF BP direction (black dot) at an arbitrary angle. The right diagram shows a 'continuous' search approach where test points are distributed across a larger sector around the known FF BP direction. A legend indicates: black dot for Known FF BP Direction, red dots for Local Search Test Points for r1 within sector around FF BP Direction, and blue dots for Grid points outside search local search sector. + +**Figure 5.1.4.6-2: Stepped (left) vs continuous (right) search approach for EIRP for an arbitrary FF BP direction.** + +As outlined in earlier, the CFFNF methodology based on the black-box approach leverages the declared FF beam peak direction and since the antenna array offset is not known/declared, a localized search for the NF beam peak in the NF must be performed over a small sector around the FF beam peak direction. For an approximately $\pm 40^\circ$ cone needed for PC3 devices (based on the $8 \times 2$ antenna array configuration) with a 20cm range length and a constant-step size measurement grid with $\Delta\phi = \Delta\theta = 1^\circ$ , around 14k grid points for the initial NF local search at $r = r_1$ would be required. Obviously, this is completely impractical due to the enormous test time requirements. The measurement uncertainties serving as the reference for investigations to follow, are shown in Table 5.1.4.6-2. + +**Table 5.1.4.6-2: Statistical results of 500 EIRP CFFNF & CFFDNF CST simulations based on black-box approach with random 8x2 (12x12) antenna array offsets uniformly spaced within 12.5cm (10cm) in a single hemisphere. The antenna array offsets and probe pattern were compensated and the search grids were based on $\Delta\phi=\Delta\theta=1^\circ$ .** + +| Antenna Configuration | Method | Range Length $r_3$ (m) | Mean Error (dB) | Std. Dev (dB) | Approximate max. number of local search grid points @ $r_1$ | +|-----------------------|-------------------|------------------------|------------------|---------------|-------------------------------------------------------------| +| 8x2 | CFFNF (Black Box) | 0.22 | 0.09 | 0.24 | 14k | +| | | 0.27 | 0.04 | 0.09 | 11k | +| | | 0.32 | 0.00 | 0.07 | 9k | +| 12x12 | CFFNF (Black Box) | 0.27 | 0.29 | 0.61 | 8k | +| | | 0.32 | 0.16 | 0.53 | 7k | +| | | 0.37 | 0.17 | 0.45 | 6k | + +These CFFNF results are tabulated in Table 5.1.4.6-3 for 8x2 (PC3) and for 12x12 (PC1) and compared with the CFFDNF results (same as those in Table 5.1.4.4-8). These simulations assume that $r_2$ is either $r_2=r_1+1\text{cm}$ or $r_2=r_1+2\text{cm}$ . + +**Table 5.1.4.6-3: Statistical results of 500 EIRP CFFNF & CFFDNF CST simulations based on black-box, black&white-box approach with random 8x2 and 12x12 antenna array offsets uniformly spaced within 12.5cm for 8x2 and within 10cm for 12x12 in a single hemisphere. The antenna array offsets and probe pattern were compensated.** + +| Antenna Configuration | Method | Range Length(m) | Mean Error (dB) | Std. Dev (dB) | +|-----------------------|----------------------------------------|-----------------|------------------|---------------| +| 8x2 | CFFNF Black Box | 0.22 | 0.09 | 0.24 | +| | | 0.27 | 0.04 | 0.09 | +| | | 0.32 | 0.00 | 0.07 | +| | CFFNF B&W Box ( $r_2=r_1+1\text{cm}$ ) | 0.21 | 0.04 | 0.04 | +| | | 0.26 | 0.03 | 0.03 | +| | | 0.31 | 0.03 | 0.03 | +| | CFFNF B&W Box ( $r_2=r_1+2\text{cm}$ ) | 0.22 | 0.04 | 0.04 | +| | | 0.27 | 0.03 | 0.04 | +| | | 0.32 | 0.03 | 0.04 | +| | CFFDNF B&W Box | 0.20 | 0.42 | 0.19 | +| 12x12 | CFFNF Black Box | 0.27 | 0.29 | 0.61 | +| | | 0.32 | 0.16 | 0.53 | +| | | 0.37 | 0.17 | 0.45 | +| | CFFNF B&W Box ( $r_2=r_1+1\text{cm}$ ) | 0.26 | 0.36 | 0.15 | +| | | 0.31 | 0.18 | 0.07 | +| | | 0.36 | 0.10 | 0.05 | +| | CFFNF B&W Box ( $r_2=r_1+2\text{cm}$ ) | 0.27 | 0.36 | 0.15 | +| | | 0.32 | 0.18 | 0.07 | +| | | 0.37 | 0.10 | 0.05 | +| | CFFDNF B&W Box | 0.25 | 1.98 | 0.47 | +| | | 0.30 | 1.26 | 0.24 | +| | | 0.35 | 0.89 | 0.14 | + +Note 1: The range length for CFFNF with black&white-box approach is reported for radius $r_2>r_1$ . +Note 2: The range length for CFFNF with black-box approach is reported for radius $r_3>r_2>r_1$ and $r_3=r_2+1=r_1+2\text{cm}$ . + +For the CFFNF (black box) simulations shown in Table 5.1.4.6-3, the local searches were performed using a $1^\circ$ step size in $\theta$ and $\phi$ to establish the reference MUs for the CFFNF methodology. + +On top of the initial local search at $r=r_1$ , small local searches at $r=r_2$ and $r=r_3$ are required as outlined in Section 5.1.4.2, i.e., the total number of grid points could exceed the numbers listed in Table 5.1.4.6-2. To significantly reduce the number of total number of grid points, coarse and fine searches were investigated more closely, i.e., an initial coarse search at $r=r_1$ with $\Delta\theta_{r1,coarse}$ and $\Delta\phi_{r1,coarse}$ and fine searches around potential NF beam peak candidates with + +$\Delta\theta_{r123, \text{fine}} = \Delta\phi_{r123, \text{fine}}$ are then performed at $r=r_1$ , $r=r_2$ , and $r=r_3$ . The MUs for the optimized search procedures are shown in Table 5.1.4.6-4; clearly, the presented optimized search grids significantly reduce the total number of search grid points while maintaining MUs similar to the reference MUs, Table 5.1.4.6-2. + +**Table 5.1.4.6-4: Statistical results of 500 EIRP CFFNF & CFFDNF CST simulations based on black-box approach with random 8x2 (12x12) antenna array offsets uniformly spaced within 12.5cm (10cm) in a single hemisphere. The antenna array offsets and probe pattern were compensated and the search grids were optimized with coarse & fine local searches.** + +| Antenna Configuration n | Method | Range Length r3 (m) | $\Delta\theta_{r1, \text{coarse}} @ r_1 [^\circ]$ | $\Delta\phi_{r1, \text{coarse}} @ r_1 [^\circ]$ | $\Delta\theta_{r123, \text{fine}} = \Delta\phi_{r123, \text{fine}} @ r_1, r_2, r_3 [^\circ]$ | Mean Error (dB) | Std. Dev (dB) | Approximate max. total number of local search grid points | +|-------------------------|-------------------|---------------------|---------------------------------------------------|-------------------------------------------------|----------------------------------------------------------------------------------------------|------------------|---------------|-----------------------------------------------------------| +| 8x2 | CFFNF (Black Box) | 0.22 | 8 | 15 | 2 | 0.10 | 0.27 | 400 | +| | | 0.27 | | | | 0.05 | 0.12 | | +| | | 0.32 | | | | 0.02 | 0.10 | | +| | CFFNF (Black Box) | 0.22 | 10 | 15 | 2 | 0.12 | 0.32 | 370 | +| | | 0.27 | | | | 0.06 | 0.15 | | +| | | 0.32 | | | | 0.01 | 0.13 | | +| 12x12 | CFFNF (Black Box) | 0.27 | 8 | 15 | 2 | 0.28 | 0.64 | 160 | +| | | 0.32 | | | | 0.17 | 0.52 | | +| | | 0.37 | | | | 0.20 | 0.41 | | +| | CFFNF (Black Box) | 0.27 | 10 | 15 | 2 | 0.28 | 0.64 | 160 | +| | | 0.32 | | | | 0.17 | 0.52 | | +| | | 0.37 | | | | 0.20 | 0.43 | | + +Constant step size measurement grids can leverage continuous scans to speed up the searches while $5^\circ$ searches yield between 200-500 grid points for a $\sim \pm 40^\circ$ cone at $r_1=20\text{cm}$ . Leveraging coarse and fine search approaches, e.g., a coarse search grid of $10^\circ$ (between 40-110 grid points for a $\sim \pm 40^\circ$ cone) over the entire cone with localized fine $5^\circ$ searches could likely significantly drop the number of grid points for the NF BP search. The total number could be further reduced when utilizing constant density search grids instead of constant-step size grids. + +A hybrid CFFNF approach could be used which combines the advantages in terms of test time of the black&white-box approach without the need of a vendor declaration, i.e., black box. Instead of having to declare the phase centre offset, this offset is determined first using the CFFNF methodology based on black-box approach. Here, the following sample approach could be leveraged: + +- For low UL power test case #1 + - Apply the black-box CFFNF test methodology using FF probe + - Use the FF probe to steer the antenna beam towards the known BP direction + - Lock the beam using UBF + - Switch operation to NF probe + - Perform local searches around sectors centred around the FF peak at three different radii in the NF + - Determine FF EIRP + - Determine phase centre offset of the active antenna +- For low UL power test cases $\geq \#2$ + - Apply the black&white-box NF test approach using NF probe + - Use the FF probe to steer the antenna beam towards the known BP direction + - Lock the beam using UBF + - Switch operation to NF probe + - Perform EIRP measurements at two different radii in the NF BP direction + +- Determine EIRP + +#### 5.1.4.7 Simulation results for sensitivity of CFFNF to relative measurement uncertainties + +This clause provides simulation assumptions for how uncertainties of power measurements in the NF, $p(d_i)$ , affect the estimates for EIRP/EIS measurements based on the asymptotic expansion approach. As outlined in Figure 5.1.4-2, $d$ is the distance between the NF measurement probe and the centre of the antenna array, while $r$ is the range length defined as the distance between the centre of QZ and the NF measurement probe. + +The asymptotic expansion approach expression for the normalized power as a function of $d$ is assumed as follows + +and is illustrated for two cases, i.e., $d_1$ & $d_2$ maximized and minimized, in Figure 5.1.4.7-1. For the simulations in this clause, it is assumed that $r_2 = r_1 + 2\text{cm}$ . + +![Figure 5.1.4.7-1: Illustration of the asymptotic expansion approach using two radii approach with the antenna array located closer to the NF probe on the left than on the right. The figure contains two graphs and two corresponding diagrams. The left graph shows Normalized Power vs. Distance with points p(d1) at d1 and p(d2) at d2, and a red dot at d_FF. The right graph shows Normalized Power vs. Distance with points p(d1) at d1 and p(d2) at d2, and a red dot at d_FF. The diagrams show an antenna array (green grid) and a probe (blue triangle) at distances d1 and d2.](f9d11004ac6966f27936c8d01e579313_img.jpg) + +Figure 5.1.4.7-1: Illustration of the asymptotic expansion approach using two radii approach with the antenna array located closer to the NF probe on the left than on the right. The figure contains two graphs and two corresponding diagrams. The left graph shows Normalized Power vs. Distance with points p(d1) at d1 and p(d2) at d2, and a red dot at d\_FF. The right graph shows Normalized Power vs. Distance with points p(d1) at d1 and p(d2) at d2, and a red dot at d\_FF. The diagrams show an antenna array (green grid) and a probe (blue triangle) at distances d1 and d2. + +**Figure 5.1.4.7-1: Illustration of the asymptotic expansion approach using two radii approach with the antenna array located closer to the NF probe on the left than on the right.** + +Power measurement uncertainties, $u_i$ , on the NF measurements $p(d_i)$ can have an effect on the resulting estimate of the estimated FF EIRP/EIS due to the asymptotic expansion transformation. This effect is illustrated schematically in Figure 5.1.4.7-2. + +![Figure 5.1.4.7-2: Illustration of the effect of power measurement uncertainties ui applied to NF measurements p(di) on the estimated FF EIRP/EIS. The graph shows Normalized Power vs. Distance with points p(d1) at d1 and p(d2) at d2, and a red dot at d_FF. Green vertical bars with error bars represent the uncertainties ui at d1 and d2.](79607caa47ed192b11a2c7b17f0b88dd_img.jpg) + +Figure 5.1.4.7-2: Illustration of the effect of power measurement uncertainties ui applied to NF measurements p(di) on the estimated FF EIRP/EIS. The graph shows Normalized Power vs. Distance with points p(d1) at d1 and p(d2) at d2, and a red dot at d\_FF. Green vertical bars with error bars represent the uncertainties ui at d1 and d2. + +**Figure 5.1.4.7-2: Illustration of the effect of power measurement uncertainties $u_i$ applied to NF measurements $p(d_i)$ on the estimated FF EIRP/EIS.** + +For these simulations, $u_i$ is assumed to be a Gaussian distribution with std. deviation of $\sigma$ varying from 0 to 0.4dB. It should be noted that the test equipment uncertainties, e.g., Uncertainty of the RF power measurement equipment (B.2.1.6 of [7]) or gNB emulator uncertainty (B.2.1.17 of [7]), are not applicable in full here since the measurements at + +$r_1$ and $r_2$ are performed with the same equipment in close succession. Instead, the relative power measurement MU apply here. + +In these simulations, it is furthermore assumed that $N=30$ averages are taken for each power measurement $p(d_i)$ . + +For fixed offsets, the effect of $u_i$ with fixed standard deviations are shown in Table 5.1.4.7-1 for the two extreme cases with $d_{\text{CFFNF,min}}=7.5\text{cm}$ and $d_{\text{CFFNF,max}}=20\text{cm}$ , visualized schematically in Figure 5.1.4.7-1. For each offset, 100K random Gaussian distributions for $u_i$ with fixed standard deviations (ranging from 0 to 0.4dB) were simulated to get obtain the mean errors with respect to the FF EIRP and the standard deviation. + +**Table 5.1.4.7-1: Impact of power measurement uncertainty $u_i$ applied to $p(d)$ measurements on FF EIRP for fixed offsets.** + +| Std. Deviation of $u_i$ (dB) | $d_{\text{CFFNF,min}}=7.5\text{cm}$ & $d_{\text{CFFNF,min}}+2\text{cm}=9.5\text{cm}$ | | $d_{\text{CFFNF,max}}=20\text{cm}$ & $d_{\text{CFFNF,max}}+2\text{cm}=22\text{cm}$ | | +|------------------------------|--------------------------------------------------------------------------------------|--------------------------------------|------------------------------------------------------------------------------------|--------------------------------------| +| | Mean Error of FF EIRP Error (dB) | Std. Deviation of FF EIRP Error (dB) | Mean Error of FF EIRP Error (dB) | Std. Deviation of FF EIRP Error (dB) | +| 0 | 0.09 | 0 | 0.01 | 0 | +| 0.1 | 0.09 | 0.05 | 0.01 | 0.14 | +| 0.2 | 0.09 | 0.11 | 0.02 | 0.31 | +| 0.3 | 0.10 | 0.19 | 0.04 | 0.52 | +| 0.4 | 0.12 | 0.27 | 0.07 | 0.77 | + +In order to obtain an overall estimate of the MUs, 1000 random offsets from Company A (500 random offsets from Company B) were evaluated. For each of the 1000 (500) random offsets, 100K random Gaussian distributions (100) for $u_i$ with fixed standard deviations were simulated to get obtain the mean errors and standard deviation for the FF EIRP; these results are tabulated in Table 5.1.4.7-2. + +**Table 5.1.4.7-2: Impact of measurement uncertainty $u_i$ applied to $p(d)$ measurements on FF EIRP with random offsets** + +| Std. Deviation of $u_i$ (dB) | Company A (N=30) | | Company B (N=1) | | Company B (N=30) | | Company A (N=1) | | Company A (N=30) | | +|------------------------------|-----------------------------------|---------------------------------|-----------------------------------|---------------------------------|-----------------------------------|---------------------------------|-----------------------------------|---------------------------------|-----------------------------------|---------------------------------| +| | Mean Error of FF EIRP Error (dB) | Std. Dev. of FF EIRP Error (dB) | Mean Error of FF EIRP Error (dB) | Std. Dev. of FF EIRP Error (dB) | Mean Error of FF EIRP Error (dB) | Std. Dev. of FF EIRP Error (dB) | Mean Error of FF EIRP Error (dB) | Std. Dev. of FF EIRP Error (dB) | Mean Error of FF EIRP Error (dB) | Std. Dev. of FF EIRP Error (dB) | +| 0 | 0.04 | 0.0 | | | | | | | | | +| 0.1 | 0.04 | 0.07 | 0.035 | 0.249 | 0.041 | 0.093 | 0.12 | 0.95 | 0.03 | 0.16 | +| 0.2 | 0.04 | 0.16 | | | | | 0.4 | 2.23 | 0.01 | 0.29 | +| 0.3 | 0.05 | 0.27 | 0.017 | 0.730 | 0.039 | 0.152 | 0.53 | 3.13 | 0.06 | 0.37 | +| 0.4 | 0.06 | 0.40 | | | | | 0.43 | 3.65 | 0.16 | 0.44 | +| 0.5 | | | 0.136 | 1.347 | 0.035 | 0.229 | | | | | + +#### 5.1.4.8 Simulation results for CFFdeltaNF + +In this clause, results for near-field and far-field simulations of $N_y \times N_z$ antenna arrays for the CFFdeltaNF methodology are presented based on the black-box approach, i.e., the location active antenna panel for the FF beam peak direction is unknown while only the FF BP direction is known. The simulation assumptions are, for the most part, the same as those in Table 5.1.4.3-1. All simulations are performed with various NF search step sizes in $\Delta\theta$ and $\Delta\phi$ . + +It has to be noted that the local search cone angles per range length shown in Table 5.1.4.6-1 are valid for CFFdeltaNF, same as the coarse and fine search approaches to reduce the test time. + +The following analyses focus on NF and FF Matlab simulations based the following high-level test procedure + +- Step 1: Measure FF EIRP of the DUT in the FF beam peak direction for max UL power with the FF probe + +- Step 2: Perform a local search around the FF beam peak direction for max UL power with the NF probe without compensating the probe antenna pattern. +- Step 3: Measure NF EIRP of the DUT in the NF beam peak direction (determine in Step 2) for max UL power with the NF probe +- Step 4: Determine the correlation factor (difference between FF and NF EIRP measurements in Steps 1 and 3) +- Step 5: Measure NF EIRP of the DUT in the NF beam peak direction for low UL power with the NF probe +- Step 6: Estimate the FF EIRP for the low UL power case with the correlation factor determined in Step 4 and the NF EIRP measured in Step 5 + +These simulations assume that for the reference high-UL power operation measurements, a 4x1 and 8x2 PC3 antenna configuration of $M \times N$ is used in Steps 1 and 3. When the operation is switched to the low-UL power operation in Step 5, it is assumed that the DUT can switch to an $O \times P$ configuration with $O \leq M$ and $P \leq N$ . Additionally, it is assumed that any arbitrary sub-array can be activated, i.e., towards the edges, the centre, or anywhere in between the full array configuration. Examples for the 8x2 configuration and various $O \times P$ configurations for the low-UL power operation are illustrated in Figure 5.1.4.4-13. For the low-UL power operation, antenna arrays of $O=\{1, 2, 4, 8\} \times P=\{1,2\}$ for the 8x2 and $O=\{1, 2, 4\} \times P=\{1\}$ for the 4x2 configuration were simulated with all possible locations within the $M \times N$ array. + +These simulations assumed 2000 random offsets and that the NF beam peak direction was determined without the NF probe antenna pattern compensation with $1^\circ$ , $2.5^\circ$ and $5^\circ$ local search step sizes for the local search (see step 2 above). The simulation results for the PC3 DUT with 8x2 configuration for the high-UL power operation are tabulated in Table 5.1.4.8-1 and with 4x1 configuration for the high-UL power operation in Table 5.1.4.8-2. The simulation results for PC1 DUT with 12x12 configuration for the high-UL power operation are tabulated in Table 5.1.4.8-3. + +**Table 5.1.4.8-1: CFFdeltaNF using black-box approach for 8x2 PC3 configuration. The low UL power configuration of the antenna array can be $O=\{1, 2, 4, 8\} \times P=\{1,2\}$ and be configured anywhere within the 8x2 array.** + +| Search Step Size ► ► ► | | $\Delta\theta=\Delta\phi=1^\circ$ | | $\Delta\theta=\Delta\phi=2.5^\circ$ | | $\Delta\theta=\Delta\phi=5^\circ$ | | +|------------------------|--------------------|-------------------------------------|------------------------------------|-------------------------------------|------------------------------------|-------------------------------------|------------------------------------| +| Range Length [m] | OxP Antenna Config | FF Low Pwr EIRP-Max Mean Error [dB] | FF Low Pwr EIRP-Max Std. Dev. [dB] | FF Low Pwr EIRP-Max Mean Error [dB] | FF Low Pwr EIRP-Max Std. Dev. [dB] | FF Low Pwr EIRP-Max Mean Error [dB] | FF Low Pwr EIRP-Max Std. Dev. [dB] | +| 0.2 | 1x1 | -0.72 | 0.36 | -0.79 | 0.42 | -1.04 | 0.60 | +| 0.2 | 2x1 | -0.72 | 0.36 | -0.79 | 0.41 | -1.02 | 0.59 | +| 0.2 | 4x1 | -0.67 | 0.34 | -0.73 | 0.38 | -0.44 | 0.61 | +| 0.2 | 1x2 | -0.55 | 0.25 | -0.62 | 0.31 | -0.86 | 0.53 | +| 0.2 | 2x2 | -0.55 | 0.25 | -0.61 | 0.30 | -0.84 | 0.51 | +| 0.2 | 4x2 | -0.50 | 0.23 | -0.08 | 0.29 | -0.27 | 0.57 | +| 0.2 | 8x2 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 0.25 | 1x1 | -0.36 | 0.15 | -0.42 | 0.19 | -0.62 | 0.36 | +| 0.25 | 2x1 | -0.35 | 0.15 | -0.41 | 0.19 | -0.61 | 0.34 | +| 0.25 | 4x1 | -0.33 | 0.15 | -0.16 | 0.21 | -0.31 | 0.38 | +| 0.25 | 1x2 | -0.26 | 0.09 | -0.32 | 0.13 | -0.51 | 0.31 | +| 0.25 | 2x2 | -0.26 | 0.09 | -0.31 | 0.13 | -0.34 | 0.30 | +| 0.25 | 4x2 | -0.02 | 0.08 | -0.06 | 0.16 | -0.20 | 0.35 | +| 0.25 | 8x2 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 0.3 | 1x1 | -0.21 | 0.08 | -0.26 | 0.11 | -0.43 | 0.26 | +| 0.3 | 2x1 | -0.21 | 0.08 | -0.25 | 0.11 | -0.33 | 0.26 | +| 0.3 | 4x1 | -0.07 | 0.08 | -0.10 | 0.13 | -0.23 | 0.27 | +| 0.3 | 1x2 | -0.16 | 0.04 | -0.20 | 0.08 | -0.37 | 0.25 | +| 0.3 | 2x2 | -0.16 | 0.04 | -0.11 | 0.08 | -0.27 | 0.25 | +| 0.3 | 4x2 | -0.01 | 0.05 | -0.05 | 0.11 | -0.17 | 0.26 | +| 0.3 | 8x2 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 0.35 | 1x1 | -0.14 | 0.05 | -0.19 | 0.08 | -0.31 | 0.22 | +| 0.35 | 2x1 | -0.14 | 0.05 | -0.12 | 0.08 | -0.28 | 0.22 | +| 0.35 | 4x1 | -0.05 | 0.06 | -0.08 | 0.10 | -0.21 | 0.22 | +| 0.35 | 1x2 | -0.11 | 0.03 | -0.15 | 0.06 | -0.26 | 0.21 | +| 0.35 | 2x2 | -0.11 | 0.03 | -0.08 | 0.07 | -0.23 | 0.21 | +| 0.35 | 4x2 | -0.01 | 0.04 | -0.04 | 0.09 | -0.16 | 0.22 | +| 0.35 | 8x2 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 0.4 | 1x1 | -0.11 | 0.04 | -0.12 | 0.07 | -0.27 | 0.20 | +| 0.4 | 2x1 | -0.11 | 0.04 | -0.10 | 0.07 | -0.24 | 0.19 | +| 0.4 | 4x1 | -0.04 | 0.04 | -0.07 | 0.08 | -0.18 | 0.19 | +| 0.4 | 1x2 | -0.08 | 0.02 | -0.09 | 0.06 | -0.23 | 0.19 | +| 0.4 | 2x2 | -0.03 | 0.02 | -0.07 | 0.06 | -0.20 | 0.19 | +| 0.4 | 4x2 | -0.01 | 0.03 | -0.04 | 0.07 | -0.14 | 0.19 | +| 0.4 | 8x2 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 0.45 | 1x1 | -0.08 | 0.03 | -0.10 | 0.06 | -0.25 | 0.18 | +| 0.45 | 2x1 | -0.05 | 0.03 | -0.09 | 0.06 | -0.23 | 0.18 | +| 0.45 | 4x1 | -0.03 | 0.03 | -0.06 | 0.07 | -0.17 | 0.18 | +| 0.45 | 1x2 | -0.06 | 0.01 | -0.08 | 0.05 | -0.22 | 0.18 | +| 0.45 | 2x2 | -0.03 | 0.02 | -0.06 | 0.05 | -0.20 | 0.18 | +| 0.45 | 4x2 | -0.01 | 0.02 | -0.04 | 0.06 | -0.14 | 0.17 | +| 0.45 | 8x2 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 20 | 1x1 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 20 | 2x1 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 20 | 4x1 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | + +| | | | | | | | | +|----|-----|------|------|------|------|------|------| +| 20 | 1x2 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 20 | 2x2 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 20 | 4x2 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 20 | 8x2 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | + +**Table 5.1.4.8-2: CFFdeltaNF using black-box approach for 4x1 PC3 configuration. The low UL power configuration of the antenna array can be $O=\{1, 2, 4\} \times P=\{1\}$ and be configured anywhere within the 4x1 array.** + +| Search Step Size ► ► ► | | $\Delta\theta=\Delta\phi=1^\circ$ | | $\Delta\theta=\Delta\phi=2.5^\circ$ | | $\Delta\theta=\Delta\phi=5^\circ$ | | +|------------------------|--------------------|-------------------------------------|------------------------------------|-------------------------------------|------------------------------------|-------------------------------------|------------------------------------| +| Range Length [m] | OxP Antenna Config | FF Low Pwr EIRP-Max Mean Error [dB] | FF Low Pwr EIRP-Max Std. Dev. [dB] | FF Low Pwr EIRP-Max Mean Error [dB] | FF Low Pwr EIRP-Max Std. Dev. [dB] | FF Low Pwr EIRP-Max Mean Error [dB] | FF Low Pwr EIRP-Max Std. Dev. [dB] | +| 0.2 | 1x1 | -0.11 | 0.14 | -0.13 | 0.17 | -0.19 | 0.26 | +| 0.2 | 2x1 | -0.08 | 0.13 | -0.10 | 0.16 | -0.15 | 0.23 | +| 0.2 | 4x1 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 0.25 | 1x1 | -0.05 | 0.06 | -0.06 | 0.08 | -0.12 | 0.15 | +| 0.25 | 2x1 | -0.04 | 0.06 | -0.05 | 0.08 | -0.10 | 0.13 | +| 0.25 | 4x1 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 0.3 | 1x1 | -0.03 | 0.04 | -0.04 | 0.06 | -0.09 | 0.11 | +| 0.3 | 2x1 | -0.02 | 0.03 | -0.03 | 0.05 | -0.07 | 0.09 | +| 0.3 | 4x1 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 0.35 | 1x1 | -0.02 | 0.02 | -0.03 | 0.04 | -0.07 | 0.08 | +| 0.35 | 2x1 | -0.02 | 0.02 | -0.02 | 0.04 | -0.05 | 0.07 | +| 0.35 | 4x1 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 0.4 | 1x1 | -0.01 | 0.02 | -0.02 | 0.03 | -0.06 | 0.07 | +| 0.4 | 2x1 | -0.01 | 0.02 | -0.02 | 0.03 | -0.05 | 0.06 | +| 0.4 | 4x1 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 0.45 | 1x1 | -0.01 | 0.01 | -0.02 | 0.02 | -0.05 | 0.06 | +| 0.45 | 2x1 | -0.01 | 0.01 | -0.02 | 0.02 | -0.04 | 0.05 | +| 0.45 | 4x1 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 1.05 | 1x1 | 0.00 | 0.00 | -0.01 | 0.01 | -0.04 | 0.03 | +| 1.05 | 2x1 | 0.00 | 0.00 | -0.01 | 0.01 | -0.03 | 0.03 | +| 1.05 | 4x1 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 20 | 1x1 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 20 | 2x1 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | +| 20 | 4x1 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | + +**Table 5.1.4.8-3: CFFdeltaNF using black-box approach for 12x12 PC1 configuration. The low UL power configuration of the antenna array can be $O=\{1, 2, 4, 8\} \times P=\{1, 2\}$ and be configured anywhere within the 12x12 array.** + +| Search Step Size ►►► | | $\Delta\theta=\Delta\phi=1^\circ$ | | $\Delta\theta=\Delta\phi=2.5^\circ$ | | +|----------------------|--------------------|-------------------------------------|------------------------------------|-------------------------------------|------------------------------------| +| Range Length [m] | OxP Antenna Config | FF Low Pwr EIRP-Max Mean Error [dB] | FF Low Pwr EIRP-Max Std. Dev. [dB] | FF Low Pwr EIRP-Max Mean Error [dB] | FF Low Pwr EIRP-Max Std. Dev. [dB] | +| 0.2 | 12x12 | 0.00 | 0.00 | 0.00 | 0.00 | +| 0.2 | 1x1 | -3.44 | 1.12 | -3.62 | 1.17 | +| 0.2 | 2x1 | -3.44 | 1.12 | -3.62 | 1.17 | +| 0.2 | 4x1 | -3.42 | 1.11 | -3.58 | 1.16 | +| 0.2 | 1x2 | -3.44 | 1.12 | -3.62 | 1.17 | +| 0.2 | 2x2 | -3.44 | 1.12 | -3.62 | 1.17 | +| 0.2 | 4x2 | -3.41 | 1.11 | -3.58 | 1.16 | +| 0.2 | 8x2 | -3.08 | 1.00 | -3.21 | 1.03 | +| 0.25 | 12x12 | 0.00 | 0.00 | 0.00 | 0.00 | +| 0.25 | 1x1 | -1.88 | 0.45 | -2.06 | 0.52 | +| 0.25 | 2x1 | -1.88 | 0.45 | -2.06 | 0.51 | +| 0.25 | 4x1 | -1.86 | 0.45 | -2.03 | 0.51 | +| 0.25 | 1x2 | -1.88 | 0.45 | -2.06 | 0.51 | +| 0.25 | 2x2 | -1.88 | 0.45 | -2.05 | 0.51 | +| 0.25 | 4x2 | -1.86 | 0.45 | -2.03 | 0.50 | +| 0.25 | 8x2 | -1.67 | 0.40 | -1.17 | 0.51 | +| 0.3 | 12x12 | 0.00 | 0.00 | 0.00 | 0.00 | +| 0.3 | 1x1 | -1.20 | 0.23 | -1.37 | 0.29 | +| 0.3 | 2x1 | -1.20 | 0.23 | -1.36 | 0.29 | +| 0.3 | 4x1 | -1.18 | 0.23 | -1.35 | 0.29 | +| 0.3 | 1x2 | -1.20 | 0.23 | -1.36 | 0.29 | +| 0.3 | 2x2 | -1.19 | 0.23 | -1.36 | 0.29 | +| 0.3 | 4x2 | -1.18 | 0.23 | -1.34 | 0.29 | +| 0.3 | 8x2 | -1.07 | 0.21 | -0.78 | 0.35 | +| 0.35 | 12x12 | 0.00 | 0.00 | 0.00 | 0.00 | +| 0.35 | 1x1 | -0.84 | 0.14 | -1.00 | 0.20 | +| 0.35 | 2x1 | -0.84 | 0.14 | -1.00 | 0.20 | +| 0.35 | 4x1 | -0.83 | 0.13 | -0.67 | 0.21 | +| 0.35 | 1x2 | -0.84 | 0.14 | -1.00 | 0.20 | +| 0.35 | 2x2 | -0.84 | 0.14 | -1.00 | 0.20 | +| 0.35 | 4x2 | -0.83 | 0.13 | -0.67 | 0.20 | +| 0.35 | 8x2 | -0.46 | 0.13 | -0.58 | 0.28 | +| 0.4 | 12x12 | 0.00 | 0.00 | 0.00 | 0.00 | +| 0.4 | 1x1 | -0.62 | 0.09 | -0.79 | 0.17 | +| 0.4 | 2x1 | -0.62 | 0.09 | -0.79 | 0.17 | +| 0.4 | 4x1 | -0.61 | 0.09 | -0.54 | 0.18 | +| 0.4 | 1x2 | -0.62 | 0.09 | -0.78 | 0.17 | +| 0.4 | 2x2 | -0.62 | 0.09 | -0.78 | 0.17 | +| 0.4 | 4x2 | -0.61 | 0.09 | -0.52 | 0.18 | +| 0.4 | 8x2 | -0.34 | 0.10 | -0.46 | 0.24 | +| 0.45 | 12x12 | 0.00 | 0.00 | 0.00 | 0.00 | +| 0.45 | 1x1 | -0.48 | 0.06 | -0.64 | 0.15 | +| 0.45 | 2x1 | -0.48 | 0.06 | -0.56 | 0.15 | +| 0.45 | 4x1 | -0.48 | 0.06 | -0.46 | 0.16 | +| 0.45 | 1x2 | -0.48 | 0.06 | -0.64 | 0.15 | +| 0.45 | 2x2 | -0.48 | 0.06 | -0.47 | 0.15 | + +| | | | | | | +|------|-------|-------|------|-------|------| +| 0.45 | 4x2 | -0.48 | 0.06 | -0.37 | 0.16 | +| 0.45 | 8x2 | -0.27 | 0.08 | -0.30 | 0.21 | +| 20 | 12x12 | 0.00 | 0.00 | 0.00 | 0.00 | +| 20 | 1x1 | -0.01 | 0.00 | -0.01 | 0.00 | +| 20 | 2x1 | -0.01 | 0.00 | -0.01 | 0.00 | +| 20 | 4x1 | 0.00 | 0.00 | 0.00 | 0.00 | +| 20 | 1x2 | -0.01 | 0.00 | -0.01 | 0.00 | +| 20 | 2x2 | 0.00 | 0.00 | 0.00 | 0.00 | +| 20 | 4x2 | 0.00 | 0.00 | 0.00 | 0.00 | +| 20 | 8x2 | 0.00 | 0.00 | 0.00 | 0.00 | + +Modelling PA behaviour in polynomial mode is a common method for RF link simulation and well accepted by the industry [8][9]. Here, a simplified PA model is added into Matlab simulations to investigate how the PA behaviour will impact the beamforming pattern shape for high power vs low power. + +The received signal expansion after beamforming based on the superposition approach outlined in detail in 5.1.4.1 + +A PA model in polynomial can be expressed as follows [8][9]: + +- : equivalent complex baseband input signal sample for PA +- : equivalent complex baseband output signal sample from PA +- PA gain in linear +- Parameter characterizing PA non-linearity property determined by output P1dB and output IP2, IP3, etc. contribute to the non-linearity components, without loss of generality: + +A simplified PA model , which only contains one non-linearity item is introduced into the received signal expression, the complex input signal for $k^{\text{th}}$ antenna array element is turned to , then + +In this simulation, we set the PA parameters, keep the low-UL power input signal power unchanged, but change the high-UL power input signal power to two different levels: the 2<sup>nd</sup> one is 2 dB higher than the 1<sup>st</sup> one. The simulations assume 200 random antenna array centre offsets and beam tilt for PC3 with 8x2 antenna configuration. The NF simulation test distance is 35cm, the low-UL power EIRP simulation error is plotted in Figure 5.1.4.8-1. + +When the operation is switched from high-UL power to low-UL power, the input signal power experiences a significant change, which means the PA is operated in two different regions. If both the high-UL power and low-UL power tests operate the PA in its perfect linearity region, the beam pattern shape change between high and low power is small and negligible under same antenna configuration as illustrated in Figure 5.1.4.8-1 (left plot), but if the high-UL power case working point is approaching the beginning of the nonlinearity region, for some beamforming tilt direction the beam pattern shape in the high-UL power case will have a large difference compared to the low-UL power case as illustrated in Figure 5.1.4.8-1 (right plot). This will then yield a relatively large error introduced by using the correlation factor deduced from the high-UL power case. + +![Figure 5.1.4.8-1: CDF of Correlation Factor with different PA model assumptions. The figure contains two side-by-side plots. The left plot shows the Empirical CDF of Deduced Low Power EIRP Error using Correlation Factor (dB) for a case with Mean Error = -0.0066dB and Std Deviation = 0.0745dB. The x-axis ranges from -0.6 to 0.3 dB, and the y-axis (CDF) ranges from 0 to 1. The curve is a smooth S-shape centered at 0. The right plot shows the Empirical CDF for a case with Mean Error = -0.2369dB and Std Deviation = 2.1473dB. The x-axis ranges from -25 to 5 dB, and the y-axis (CDF) ranges from 0 to 1. This curve is very steep, jumping from 0 to 1 near 0 dB.](53d8bef47c63e0897de4cd058bad2cbd_img.jpg) + +Figure 5.1.4.8-1: CDF of Correlation Factor with different PA model assumptions. The figure contains two side-by-side plots. The left plot shows the Empirical CDF of Deduced Low Power EIRP Error using Correlation Factor (dB) for a case with Mean Error = -0.0066dB and Std Deviation = 0.0745dB. The x-axis ranges from -0.6 to 0.3 dB, and the y-axis (CDF) ranges from 0 to 1. The curve is a smooth S-shape centered at 0. The right plot shows the Empirical CDF for a case with Mean Error = -0.2369dB and Std Deviation = 2.1473dB. The x-axis ranges from -25 to 5 dB, and the y-axis (CDF) ranges from 0 to 1. This curve is very steep, jumping from 0 to 1 near 0 dB. + +**Figure 5.1.4.8-1: CDF of Correlation Factor with different PA model assumptions** + +Some more work is needed to quantify the effect of non-linear PA behaviour on the CFFdeltaNF MUs. + +The high-level six-step measurement procedure was applied with a phased antenna array operated at 26 GHz. This phased antenna array has an 8x8 configuration and supports beam steering using external control of the code books. The FF measurements were performed at 84 cm while the NF measurements were performed at 20 cm. Three beam steering directions, i.e., $-60^\circ$ , $0^\circ$ , and $60^\circ$ were considered. Some parameters of the measurement procedures are summarized in Table 5.1.4.8-4. + +**Table 5.1.4.8-4: Measurement Parameters of CFFdeltaNF methodology using black-box approach** + +| Parameter | Value | +|------------------------------------|--------------------------------------| +| Phased Antenna Array Configuration | 8x8 | +| Beam Steering Configuration | $-60^\circ$ , $0^\circ$ , $60^\circ$ | +| Frequency | 26 GHz | +| FF Distance | 84 cm | +| NF Distance | 20 cm | +| Offset | 0 cm | + +Since each individual antenna array element has independent amplitude and phase control, the high-UL power operation of the antenna array was implemented by maximizing the amplitude weights while those weights were reduced by 30 dB for the low-UL power operation. + +With beam steering applied in just a single direction, single principal cut measurements were performed to determine the NF direction (step 2 of the 6-step procedure introduced in the previous section); the NF probe antenna pattern was not compensated. The NF and FF EIRP patterns at 26 GHz are plotted in Figure 5.1.4.8-2 for the high-UL and low-UL power operations. It should be noted that the path loss (to the centre of QZ) was compensated in these plots already. Some pattern changes between the FF and NF patterns but also pattern changes between the high-UL and low-UL operation can be noticed. + +The measurement results for the three different beam steering directions are tabulated in Table 5.1.4.8-5. The estimated FF EIRP for the low-UL case is compared with the measured EIRP to determine the error in the CFFdeltaNF EIRP MU. Clearly, the results show that the FF EIRP can be estimated well but the pattern changes due to low-UL vs high-UL power operation can introduce some MUs. More detailed analyses are required to study the pattern changes due to amplifiers and phase shifters operated at different power levels to determine the corresponding example MU. + +![Line graph showing Radiated power(dBm) vs Angle(degree) for four antenna configurations: High power, 84cm; High power, 20cm; Low power, 84cm; and Low power, 20cm. The graph shows multiple peaks and dips across the -80 to 80 degree range. High power configurations show significantly higher radiated power (peaking around 40-45 dBm) compared to low power configurations (peaking around 10-15 dBm).](7c0a9511fa02b6c2c125ff5be465186e_img.jpg) + +Line graph showing Radiated power(dBm) vs Angle(degree) for four antenna configurations: High power, 84cm; High power, 20cm; Low power, 84cm; and Low power, 20cm. The graph shows multiple peaks and dips across the -80 to 80 degree range. High power configurations show significantly higher radiated power (peaking around 40-45 dBm) compared to low power configurations (peaking around 10-15 dBm). + +**Figure 5.1.4.8-2: Measured NF and FF EIRP patterns of the 8x8 antenna array with high-UL and low-UL power operation.** + +**Table 5.1.4.8-5: Measurement results for CFFdeltaNF methodology using black-box approach with no change in antenna array configuration of 8x8.** + +| Beam Steering Angle [deg] ▶▶▶ | -60 | 0 | 60 | +|-------------------------------------------------------|--------|--------|--------| +| FF EIRP for High UL at FF BP Direction [dBm] | 38.07 | 41.45 | 38.46 | +| NF EIRP for High UL at NF BP Direction [dBm] | 51.00 | 53.67 | 52.62 | +| Correlation Factor [dB] | -12.93 | -12.22 | -14.17 | +| FF EIRP for Low UL at FF BP Direction [dBm] | 7.71 | 12.46 | 8.74 | +| NF EIRP for Low UL at NF BP Direction [dBm] | 20.56 | 24.84 | 23.21 | +| Estimated FF EIRP for Low UL at FF BP Direction [dBm] | 7.63 | 12.62 | 9.04 | +| FF Error in estimated EIRP [dB] | 0.08 | -0.16 | -0.30 | + +While the errors in Table 5.1.4.8-5 are relatively small and could be interpreted as overall measurement MUs instead of being caused by the change in antenna pattern, the overall trend of the pattern plots and EIRP errors seem to support the earlier findings. + +Another set of measurements was performed where the antenna configuration was modified between high-UL ( $M \times N = 8 \times 8$ ) and low-UL ( $O \times P$ ) operation similar as described in the previous section. Here, the $O \times P$ configuration was a subset of the $8 \times 8$ configuration with $O \times P = \{8 \times 4, 8 \times 2, \text{ and } 8 \times 1\}$ configurations. For each of the $O \times P$ array configurations, different positions within the $8 \times 8$ array were activated. Sample $8 \times 4$ low-UL configurations and starting coordinates are visualized in Figure 5.1.4.8-3. + +![Diagram showing three antenna array configurations: High-UL Power 8x8 Configuration, Sample Low-UL Power Configuration: 8x4 @ (1,1), and Sample Low-UL Power Configuration: 8x4 @ (1,3). A legend indicates orange squares are Active Antenna Elements and grey squares are Inactive Antenna Elements.](f455955c4bc84005728b4138f19098dc_img.jpg) + +The figure displays three antenna array configurations. Each configuration is represented by a grid of 64 elements (8 rows by 8 columns). The first configuration, 'High-UL Power 8x8 Configuration', shows all 64 elements as active (orange). The second configuration, 'Sample Low-UL Power Configuration: 8x4 @ (1,1)', shows the first 4 columns of 8 elements each as active (orange) and the last 4 columns as inactive (grey). The third configuration, 'Sample Low-UL Power Configuration: 8x4 @ (1,3)', shows the first 2 columns and the 5th through 8th columns as active (orange), with the 3rd and 4th columns being inactive (grey). A legend at the bottom indicates that an orange square represents an 'Active Antenna Element' and a grey square represents an 'Inactive Antenna Element'. + +Diagram showing three antenna array configurations: High-UL Power 8x8 Configuration, Sample Low-UL Power Configuration: 8x4 @ (1,1), and Sample Low-UL Power Configuration: 8x4 @ (1,3). A legend indicates orange squares are Active Antenna Elements and grey squares are Inactive Antenna Elements. + +**Figure 5.1.4.8-3: 8x8 Configuration for high-UL power operation (left) and sample 8x4 configurations for low UL-power operation.** + +The measurement results for the set of measurements at two different NF range lengths of 20cm and 35cm with changes in the antenna array configuration are tabulated in Table 5.1.4.8-6. These results yield similar findings as presented earlier: + +- When the antenna configuration for the low UL power operation is a subset of the antenna configuration for the high UL power operation, the CFFdeltaNF methodology needs to take EIRP MU uncertainties into account +- These uncertainties increase with decreasing range lengths + +**Table 5.1.4.8-6: Measurement results for CFFdeltaNF methodology using black-box approach with changes in antenna array configuration from 8x8 (high-UL power) to 8xP (low-UL power).** + +| Range Length | Description of Meas./Calc. | High-UL Power | Low-UL Power | | | | | | | | | | | +|--------------|----------------------------------------|---------------|--------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------| +| | | 8x8 | 8x4 @ (1,1) | 8x4 @ (1,2) | 8x4 @ (1,3) | 8x2 @ (1,1) | 8x2 @ (1,2) | 8x2 @ (1,3) | 8x2 @ (1,4) | 8x1 @ (1,1) | 8x1 @ (1,2) | 8x1 @ (1,3) | 8x1 @ (1,4) | +| FF @ 84cm | EIRP in FF BP Dir. [dB] | 45.61 | 40.64 | 40.84 | 40.99 | 37.18 | 35.61 | 34.96 | 36.46 | 33.87 | 31.9 | 31.43 | 30.18 | +| NF @ 35cm | EIRP in NF BP Dir. [dB] | 52.93 | 48.04 | 48.32 | 48.29 | 44.62 | 43.31 | 42.7 | 44.1 | 41.02 | 39.62 | 39.24 | 38.71 | +| | Correlation Factor [dB] | -7.32 | | | | | | | | | | | | +| | Estimated FF EIRP in FF BP. Dir. [dBm] | | 40.72 | 41.00 | 40.97 | 37.30 | 35.99 | 35.38 | 36.78 | 33.70 | 32.30 | 31.91 | 31.39 | +| | FF Error in estimated EIRP [dB] | | 0.08 | 0.16 | -0.02 | 0.12 | 0.38 | 0.42 | 0.32 | -0.17 | 0.40 | 0.49 | 1.21 | +| FF @ 84cm | EIRP in FF BP Dir. [dB] | 45.61 | 40.64 | 40.84 | 40.99 | 37.18 | 35.61 | 34.96 | 36.46 | 33.87 | 31.9 | 31.43 | 30.18 | +| NF @ 20cm | EIRP in NF BP Dir. [dB] | 56.33 | 52.13 | 51.97 | 52.53 | 48.41 | 46.83 | 46.61 | 48.04 | 44.56 | 43.32 | 42.33 | 42.95 | +| | Correlation Factor [dB] | -10.72 | | | | | | | | | | | | +| | Estimated FF EIRP in FF BP. Dir. [dBm] | | 41.41 | 41.24 | 41.81 | 37.68 | 36.11 | 35.89 | 37.31 | 33.84 | 32.60 | 31.61 | 32.23 | +| | FF Error in estimated EIRP [dB] | | 0.77 | 0.40 | 0.82 | 0.50 | 0.50 | 0.92 | 0.85 | -0.03 | 0.70 | 0.18 | 2.05 | + +The next part focuses on simulations based on the CFFdeltaNF methodology using black-box approach, specifically the correlation factor approach where the low-UL power operation is no longer triggered. Instead, the low-UL power measurement is the result of performing measurements at frequencies that yield low EIRPs when compared to the EIRPs at the reference frequency, e.g., ACLR. Therefore, the test procedure for this approach is as follows with the first 4 steps identical and slightly adjusted steps 5 and 6 to the approach introduced earlier: + +- Step 1: Measure FF EIRP of the DUT in the FF beam peak direction for high-UL power with the FF probe at the reference frequency +- Step 2: Perform a local search around the FF beam peak direction for high-UL power with the NF probe without compensating the probe antenna pattern at the reference frequency. +- Step 3: Measure NF EIRP of the DUT in the NF beam peak direction (determined in Step 2) for high-UL power with the NF probe at the reference frequency +- Step 4: Determine the correlation factor (difference between FF and NF EIRP measurements in Steps 1 and 3) and add the pathloss differences at the desired frequency +- Step 5: Measure NF EIRP of the DUT in the NF beam peak direction with the NF probe at the desired frequency other than the reference frequency +- Step 6: Estimate the FF EIRP for the desired frequency with the correlation factor determined in Step 4 and the NF EIRP measured in Step 5 + +The simplified PA model described in the previous section is used in this simulation. The 1<sup>st</sup> item is the major component for in-band (wanted) signal, while some of the 2<sup>nd</sup> item will also contribute to the in-band pattern; the OOB signal's pattern shape will be impacted by the non-linearity component [8][9]. + +When $\alpha$ is defined in amplitude and phase expression as $\alpha$ , we assume the amplitude is constant and only adjust the phase for each channel, then the 2<sup>nd</sup> item can be expressed as + +If $\alpha$ is not always zeros for all indices $n$ , $\alpha$ will not generate the same pattern shape as $\alpha$ because of the different phase offset among multiple channels. + +Below Figures 5.1.4.8-4 and 5.1.4.8-5 use the 8x2 antenna array with random position offset and beam tilt as an example to show the PA's non-linearity impact on the OOB signal pattern shape. + +For Figure 5.1.4.8-4, when the PA has poor linearity, the OOB signal pattern shape (plot on right) is different from the in-band signal pattern (plot on left). In this case, when using the relative correlation factor approach and the local NF peak direction deduced from the in-band signal to estimate OOB EIRP, the error can be as large as -3.67 dB. + +For Figures 5.1.4.8-5, when the PA has very good linearity, the OOB signal pattern shape (plot on right) is almost same as the in-band signal pattern (plot on left). In this case, the error is insignificant. + +These analyses show the out-of-band signal's pattern shape will be impacted by the PA behaviour; the relative correlation factor deduced from the in-band signal to estimate out of band signal's FF power will introduce extra errors. Clearly, the corresponding EIRP MUs are dependent on the PA and needs further study. + +![Figure 5.1.4.8-4: PA with poor linearity. In-band pattern on the left, OOB pattern on the right.](fe236a7cb4bf9aaf4a61a04f700b0e7e_img.jpg) + +The figure consists of two side-by-side 3D surface plots. The left plot is titled '8x2 In Band Signal Antenna Pattern FF' and shows a radiation pattern with a main lobe and several side lobes. The color scale on the right of the plot ranges from 30 (blue) to 55 (red). The right plot is titled '8x2 Out of Band Signal Antenna Pattern FF' and shows a similar radiation pattern but with a different shape, particularly in the side lobes. The color scale on the right of this plot ranges from 15 (blue) to 40 (red). Both plots include a 3D coordinate system with X, Y, and Z axes. + +Figure 5.1.4.8-4: PA with poor linearity. In-band pattern on the left, OOB pattern on the right. + +Figure 5.1.4.8-4: PA with poor linearity. In-band pattern on the left, OOB pattern on the right. + +![Figure 5.1.4.8-5: PA with very good linearity. In-band pattern on the left, OOB pattern on the right.](b104cf622ef88c0bb857ecb3f0816d87_img.jpg) + +The figure consists of two side-by-side 3D surface plots. The left plot is titled '8x2 In Band Signal Antenna Pattern FF' and shows a radiation pattern with a main lobe and several side lobes. The color scale on the right of the plot ranges from 30 (blue) to 55 (red). The right plot is titled '8x2 Out of Band Signal Antenna Pattern FF' and shows a radiation pattern that is very similar to the in-band pattern. The color scale on the right of this plot ranges from 10 (blue) to 35 (red). Both plots include a 3D coordinate system with X, Y, and Z axes. + +Figure 5.1.4.8-5: PA with very good linearity. In-band pattern on the left, OOB pattern on the right. + +**Figure 5.1.4.8-5: PA with good linearity. In-band pattern on the left, OOB pattern on the right.** + +The next investigation focuses on measurements and the 6-step procedure discussed earlier. The measurements presented in Table 5.1.4.8-7 use the same 8x8 antenna array introduced earlier. Here, a 200 MHz wide signal is applied to the RF ports of the phased antenna array and the power in the reference channel around 26 GHz as well as the adjacent channels (Low, High) were measured in both the NF at {20cm, 35cm} range lengths and FF at 84cm range length in the respective in-band beam peak directions. + +**Table 5.1.4.8-7: Measurement results for CFFdeltaNF methodology using black-box approach.** + +| Range Length [cm] | Beam Steering Angle [deg]<br>▶▶▶ | 0 | 10 | 20 | 30 | 40 | 50 | 60 | +|-------------------|------------------------------------------------------------------------|-------|-------|-------|-------|-------|-------|-------| +| | | | | | | | | | +| 35 | FF EIRP in reference channel at FF BP Direction [dBm] | 46.16 | 46.35 | 44.43 | 44.69 | 43.95 | 43.35 | 42.02 | +| | NF EIRP in reference channel at NF BP Direction [dBm] | 52.05 | 51.89 | 50.92 | 51.83 | 51.32 | 50.82 | 49.42 | +| | Correlation Factor [dB] | -5.89 | -5.54 | -6.49 | -7.14 | -7.37 | -7.47 | -7.40 | +| | FF EIRP in reference channel (low) at FF BP Direction [dBm] | 24.49 | 25.12 | 22.03 | 24.22 | 22.48 | 21.39 | 20.24 | +| | FF EIRP in reference channel (high) at FF BP Direction [dBm] | 27.68 | 28.86 | 26.23 | 26.50 | 26.83 | 25.76 | 25.31 | +| | NF EIRP in reference channel (low) at NF BP Direction [dBm] | 30.71 | 30.22 | 28.25 | 30.79 | 28.94 | 28.07 | 26.69 | +| | NF EIRP in reference channel (high) at NF BP Direction [dBm] | 32.82 | 33.54 | 32.25 | 32.53 | 32.86 | 31.87 | 31.09 | +| | Estimated FF EIRP in reference channel (low) at FF BP Direction [dBm] | 24.82 | 24.68 | 21.76 | 23.64 | 21.57 | 20.61 | 19.29 | +| | Error in estimated EIRP in reference channel (low) [dB] | -0.33 | 0.44 | 0.27 | 0.58 | 0.92 | 0.78 | 0.95 | +| | Estimated FF EIRP in reference channel (high) at FF BP Direction [dBm] | 26.93 | 28.00 | 25.76 | 25.39 | 25.48 | 24.40 | 23.69 | +| | Error in estimated EIRP in reference channel (high) [dB] | 0.75 | 0.86 | 0.48 | 1.11 | 1.34 | 1.35 | 1.62 | +| 20 | FF EIRP in reference channel at FF BP Direction [dBm] | 46.16 | 46.35 | 44.43 | 44.69 | 43.95 | 43.35 | 42.02 | + +| | | | | | | | | | +|--|------------------------------------------------------------------------|-------|--------|--------|--------|--------|--------|--------| +| | NF EIRP in reference channel at NF BP Direction [dBm] | 55.79 | 56.48 | 55.79 | 56.05 | 55.90 | 55.27 | 55.31 | +| | Correlation Factor [dB] | -9.64 | -10.13 | -11.36 | -11.36 | -11.95 | -11.92 | -13.29 | +| | FF EIRP in reference channel (low) at FF BP Direction [dBm] | 24.49 | 25.12 | 22.03 | 24.22 | 22.48 | 21.39 | 20.24 | +| | FF EIRP in reference channel (high) at FF BP Direction [dBm] | 27.68 | 28.86 | 26.23 | 26.50 | 26.83 | 25.76 | 25.31 | +| | NF EIRP in reference channel (low) at NF BP Direction [dBm] | 33.15 | 35.01 | 32.97 | 35.01 | 34.04 | 32.84 | 31.80 | +| | NF EIRP in reference channel (high) at NF BP Direction [dBm] | 42.18 | 43.44 | 42.04 | 42.15 | 42.48 | 41.16 | 37.29 | +| | Estimated FF EIRP in reference channel (low) at FF BP Direction [dBm] | 23.52 | 24.88 | 21.61 | 23.64 | 22.09 | 20.92 | 18.51 | +| | Error in estimated EIRP in reference channel (low) [dB] | 0.97 | 0.24 | 0.42 | 0.58 | 0.39 | 0.46 | 1.73 | +| | Estimated FF EIRP in reference channel (high) at FF BP Direction [dBm] | 32.54 | 33.31 | 30.68 | 30.79 | 30.53 | 29.24 | 24.00 | +| | Error in estimated EIRP in reference channel (high) [dB] | -4.86 | -4.45 | -4.45 | -4.29 | -3.71 | -3.49 | 1.31 | + +These results show that the relative correlation factor approach of CFFdeltaNF is generally applicable for measurements at frequencies other than the reference frequency. However, as outlined earlier, MUs should be considered for this approach to take into account pattern changes due to non-ideal PA behaviour which was verified using measurements. More detailed analyses are required to study the non-linearity effects of PAs on the corresponding EIRP MU of CFFdeltaNF. + +Another investigation focused on the effect of the UE pattern change over frequency in the resulting EIRP using the CFFdeltaNF methodology with black-box approach as described in clause 5.1.4.2. A simulation campaign using Matlab was defined following the assumptions presented in Table 5.1.4.3-1 with additional frequencies at 50, 100, 200, 400, 800 and 1200MHz from the centre frequency (i.e. 28GHz). + +In this case, the EIRP error is calculated between the theoretical EIRP value in FF at the test frequency (e.g. 400MHz from channel's centre frequency) and the resulting EIRP value calculated in the FF at the same test frequency but applying the calculated for the reference test case at the reference frequency. + +Mean and standard deviation errors, for all offsets and test frequencies, are presented in table 5.1.4.8-8, including results for different grid steps for the local search: + +**Table 5.1.4.8-8: Statistical results of EIRP simulations for CFFdeltaNF with black-box approach** + +| Antenna configuration | Range length (m) | Grid step | Mean Error (dB) | Std. Deviation (dB) | +|-----------------------|------------------|-----------|------------------|---------------------| +| 8x2 | 0.20 | 1° | 0.016 | 0.017 | +| | | 5° | 0.024 | 0.028 | +| | | 10° | 0.050 | 0.075 | +| | 0.25 | 1° | 0.009 | 0.008 | +| | | 5° | 0.015 | 0.018 | +| | | 10° | 0.037 | 0.056 | +| | 0.30 | 1° | 0.006 | 0.005 | + +| | | | | | +|--|------|-----|-------|-------| +| | | 5° | 0.012 | 0.014 | +| | | 10° | 0.032 | 0.051 | +| | 0.35 | 1° | 0.004 | 0.004 | +| | | 5° | 0.010 | 0.012 | +| | | 10° | 0.031 | 0.048 | +| | 0.40 | 1° | 0.003 | 0.003 | +| | | 5° | 0.008 | 0.011 | +| | | 10° | 0.028 | 0.043 | +| | 0.45 | 1° | 0.003 | 0.002 | +| | | 5° | 0.007 | 0.009 | +| | | 10° | 0.026 | 0.041 | + +These results, assuming no change in antenna patterns due to non-linearities of the PAs, etc., confirm that CFFdeltaNF method is not impacted the potential changes in the pattern of the UE array due to frequency response. + +#### 5.1.4.9 Simulation results for Influence of Noise + +This clause provides influence of noise simulation assumptions and results for IFF/DFF, CFFDNF, and CFFNF methodologies. + +The influence of noise quantifies the effect of a SNR at the TE input on EIRP measurements as outlined in [7]. + +### B.2.1.27 Influence of noise + +This contributor describes an offset uncertainty factor caused by a noise floor especially in a case of low SNR. This contributor works as a bias to measured results only to a direction to increase values and thus this shall be included in the uncertainty budget table as a systematic uncertainty. The uncertainty value can be derived by the following equation. + +For low UL power test cases, the ~1m path losses due to range length (DFF) or focal distance (IFF) yield very poor SNR conditions at the TE input. Assuming a fixed noise level at the TE input, a reduction in measurement distance/range loss will significantly improve the SNR conditions for CFFDNF and CFFNF when compared to DFF/IFF as illustrated in Figure 5.1.4.9-1. + +![Figure 5.1.4.9-1: SNR Conditions for different test methodologies. The diagram shows three test setups (CFNFN, CFDFN, and DFF/IFF) connected to a central 'Switch Box*'. The outputs of the switch box are labeled S_CFFNF, S_CFFDNF, and S_DFF/IFF. These signals are then fed into a 'TE' (Test Equipment) block. A callout box indicates that with N_CFFNF = N_CFFDNF = N_DFF/IFF and S_CFFNF > S_CFFDNF > S_DFF/IFF, the resulting SNR is SNR_CFFNF > SNR_CFFDNF > SNR_DFF/IFF. A note below the switch box states: '* Switching, Amplification, Signal Conditioning (assumed same for all methodologies)'.](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +Figure 5.1.4.9-1: SNR Conditions for different test methodologies. The diagram shows three test setups (CFNFN, CFDFN, and DFF/IFF) connected to a central 'Switch Box\*'. The outputs of the switch box are labeled S\_CFFNF, S\_CFFDNF, and S\_DFF/IFF. These signals are then fed into a 'TE' (Test Equipment) block. A callout box indicates that with N\_CFFNF = N\_CFFDNF = N\_DFF/IFF and S\_CFFNF > S\_CFFDNF > S\_DFF/IFF, the resulting SNR is SNR\_CFFNF > SNR\_CFFDNF > SNR\_DFF/IFF. A note below the switch box states: '\* Switching, Amplification, Signal Conditioning (assumed same for all methodologies)'. + +**Figure 5.1.4.9-1: SNR Conditions for different test methodologies** + +The analyses in this clause are focused on the following PC3 assumption: + +- For an $r_1=20\text{cm}$ CFFNF range length (distance between probe and centre of QZ), the min distance between the probe and the antenna array is $d_{\text{CFFNF,min}} = r_1 - 12.5\text{cm}$ (max offset) $= 7.5\text{cm}$ +- For an $r_1=20\text{cm}$ CFFNF range length, the max distance between the probe and the antenna array is $d_{\text{CFFNF,max}} = r_1 = 20\text{cm}$ +- Similarly, for the CFDFN methodology with a range length of $r_{\text{CFDFN}}=35\text{cm}$ , the min (max) distance between the probe and the antenna array is $d_{\text{CFDFN,min}} = r_{\text{CFDFN}} - 12.5\text{cm} = 22.5\text{cm}$ ( $d_{\text{CFDFN,max}} = r_{\text{CFDFN}} = 35\text{cm}$ ). +- For the DFF/IFF calculations, we considered a $r_{\text{DFF/IFF}}=1\text{m}$ range length for simplicity. + +The improvements in SNR for CFFNF and CFDFN compared to DFF/IFF are tabulated in Table 5.1.4.9-1. + +**Table 5.1.4.9-1: SNR Improvement due to reduced measurement distance w.r.t. 1m DFF/IFF FSPL with fixed noise at TE Input** + +| Methodology ►►<br>▼ $f$ [GHz] ▼ | DFF/IFF | CFDFN | | CFFNF | | +|---------------------------------|---------|-------|---------|-------|--------| +| | @100cm | @35cm | @22.5cm | @20cm | @7.5cm | +| 24 | 0.0 | 9.1 | 13.0 | 14.0 | 22.5 | +| 30 | 0.0 | 9.1 | 13.0 | 14.0 | 22.5 | +| 35 | 0.0 | 9.1 | 13.0 | 14.0 | 22.5 | +| 40 | 0.0 | 9.1 | 13.0 | 14.0 | 22.5 | +| 45 | 0.0 | 9.1 | 13.0 | 14.0 | 22.5 | +| 50 | 0.0 | 9.1 | 13.0 | 14.0 | 22.5 | + +In our influence of noise calculations, we assumed a range of SNR values for the DFF/IFF methodology at the TE input and scaled the effective SNR at the TE input for the CFDFN/CFFNF analyses as shown in Table 5.1.4.9-2 based on the FSPL/SNR improvements in Table 5.1.4.9-1. + +**Table 5.1.4.9-2: Effective SNRs at the TE Input based on assumed SNR at the TE input for DFF/IFF** + +| Methodology ►►<br>▼ DFF/IFF SNR [dB]<br>▼ | DFF/IFF | CFFDFN | | CFFNF | | +|-------------------------------------------|---------|--------|---------|-------|--------| +| | @100cm | @35cm | @22.5cm | @20cm | @7.5cm | +| -15 | -15.0 | -5.9 | -2.0 | -1.0 | 7.5 | +| -10 | -10.0 | -0.9 | 3.0 | 4.0 | 12.5 | +| -5 | -5.0 | 4.1 | 8.0 | 9.0 | 17.5 | +| 0 | 0.0 | 9.1 | 13.0 | 14.0 | 22.5 | +| 5 | 5.0 | 14.1 | 18.0 | 19.0 | 27.5 | +| 10 | 10.0 | 19.1 | 23.0 | 24.0 | 32.5 | +| 15 | 15.0 | 24.1 | 28.0 | 29.0 | 37.5 | + +The analyses of the difference in EIRP when compared to the FF EIRP due to noise were based on 10k different AWGN simulations and $N=30$ averages were taken for each EIRP analysed. In each of the 10k AWGN simulations, a signal is generated first with 1000 samples, subsequently AWGN with specified SNR on the signal is applied, and in the end power of signal + AWGN was measured. These simulated results, labelled '[Mean Err to FF Reference]' in the following tables are then compared with the calculations using the analytical equation and labelled 'Influence of Noise' in the following tables: for $r_{\text{DFF/IFF}}$ , $d_{\text{CFFDFN,min}}$ , and $d_{\text{CFFNF,min}}$ in Table 5.1.4.9-3 and for $r_{\text{DFF/IFF}}$ , $d_{\text{CFFDFN,max}}$ , and $d_{\text{CFFNF,max}}$ in Table 5.1.4.9-4. In these simulations, it was assumed that $r_2 = r_1 + 2\text{cm}$ . + +**Table 5.1.4.9-3: Influence of Noise Simulations and Calculations for DFF/IFF, CFFDFN, CFFNF based on shortest measurement distance $d_{\text{min}}$** + +| DFF/IFF | | | CFFDFN | | | CFFNF | | | | +|-----------------------------------|--------------------------------|-------------------------|---------------------------------------|--------------------------------|-------------------------|---------------------------------------------------------------------------------|----------------------------------------|--------------------------------|---------------------------------------------------------------| +| $r_{\text{DFF/IFF}}=100\text{cm}$ | | | $d_{\text{CFFDFN,min}}=22.5\text{cm}$ | | | $(d_{\text{CFFNF,min}}, d_{\text{CFFNF,min}}+2\text{cm}) = (7.5, 9.5)\text{cm}$ | | | | +| SNR @ $r_{\text{DFF/IFF}}$ (dB) | Mean Err to FF Reference (dB) | Influence of Noise (dB) | SNR @ $d_{\text{min}}$ (dB) | Mean Err to FF Reference (dB) | Influence of Noise (dB) | SNR @ $d_{\text{min}}$ (dB) | SNR @ $d_{\text{min}}+2\text{cm}$ (dB) | Mean Err to FF Reference (dB) | Influence of Noise with SNR@ $d_{\text{min}}+2\text{cm}$ (dB) | +| -15.00 | 15.1 | 15.1 | -2.0 | 4.0 | 4.2 | 7.5 | 5.4 | 1.44 | 1.1 | +| -10.00 | 10.4 | 10.4 | 3.0 | 1.6 | 1.8 | 12.5 | 10.4 | 0.45 | 0.4 | +| -5.00 | 6.2 | 6.2 | 8.0 | 0.5 | 0.6 | 17.5 | 15.4 | 0.09 | 0.1 | +| 0.00 | 3.0 | 3.0 | 11 | 0.1 | 0.2 | 22.5 | 20.4 | 0.04 | 0.0 | +| 5.00 | 1.2 | 1.2 | 17 | 0.1 | 0.1 | 27.5 | 25.4 | 0.07 | 0.0 | +| 10.00 | 0.4 | 0.4 | 23 | 0.1 | 0.0 | 32.5 | 30.4 | 0.09 | 0.0 | +| 15.00 | 0.1 | 0.1 | 28 | 0.1 | 0.0 | 37.5 | 35.4 | 0.09 | 0.0 | + +**Table 5.1.4.9-4: Influence of Noise Simulations and Calculations for DFF/IFF, CFFDNF, CFFNF based on largest measurement distance $d_{max}$** + +| DFF/IFF | | | CFFDNF | | | CFFNF | | | | +|----------------------------|--------------------------------|-------------------------|------------------------------|--------------------------------|-------------------------|-----------------------------------------------------------------|---------------------------------|--------------------------------|--------------------------------------------------------| +| $r_{DFF/IFF}=100\text{cm}$ | | | $d_{CFFDNF,max}=35\text{cm}$ | | | $(d_{CFFNF,max}, d_{CFFNF,max}+2\text{cm}) = (20, 22)\text{cm}$ | | | | +| SNR @ $r_{DFF/IFF}$ (dB) | Mean Err to FF Reference (dB) | Influence of Noise (dB) | SNR @ $d_{max}$ (dB) | Mean Err to FF Reference (dB) | Influence of Noise (dB) | SNR @ $d_{max}$ (dB) | SNR @ $d_{max}+2\text{cm}$ (dB) | Mean Err to FF Reference (dB) | Influence of Noise with SNR@ $d_{max}+2\text{cm}$ (dB) | +| -15.00 | 15.1 | 15.1 | -5.9 | 6.8 | 6.9 | -1.0 | -1.8 | 5.7 | 4.0 | +| -10.00 | 10.4 | 10.4 | -0.9 | 3.4 | 3.5 | 4.0 | 3.2 | 2.7 | 1.7 | +| -5.00 | 6.2 | 6.2 | 4.1 | 1.4 | 1.4 | 9.0 | 8.2 | 1.0 | 0.6 | +| 0.00 | 3.0 | 3.0 | 9.1 | 0.4 | 0.5 | 14.0 | 13.2 | 0.4 | 0.2 | +| 5.00 | 1.2 | 1.2 | 14.1 | 0.1 | 0.2 | 19.0 | 18.2 | 0.1 | 0.1 | +| 10.00 | 0.4 | 0.4 | 19.1 | 0.0 | 0.1 | 24.0 | 23.2 | 0.0 | 0.0 | +| 15.00 | 0.1 | 0.1 | 24.1 | 0.1 | 0.0 | 29.0 | 28.2 | 0.0 | 0.0 | + +The simulated influence of noise, i.e., |Mean Err to FF Reference|, was determined for non-fixed distances $d$ . Here, 1000 random offsets uniformly spaced from 0 to 12.5cm were simulated and the individual results were averaged to obtain the results tabulated in Table 5.1.4.9-5 for PC3 devices. The simulated influences of noise are within the results at the respective extremes presented in Table 5.1.4.9-3 (min offset) and Table 5.1.4.9-4 (max offset). Similar simulations were performed for PC1 devices with the 12x12 antenna configuration with maximum offset of 10cm and are tabulated in Table 5.1.4.9-6. + +**Table 5.1.4.9-5: Influence of Noise Simulations and Calculations for DFF/IFF, CFFDNF, CFFNF based on 1000 random offsets uniformly spaced within 12.5cm (PC3) in a single hemisphere and $N=1$ .** + +| DFF/IFF | | | CFFDNF | | CFFNF | | | +|----------------------------|--------------------------------|-------------------------|--------------------------------------------------|--------------------------------|----------------------------------------------------------------------|-------------------------|--------------------------------| +| $r_{DFF/IFF}=100\text{cm}$ | | | $22.5\text{cm} \leq d_{CFFDNF} \leq 35\text{cm}$ | | $7.5\text{cm} \leq d_{CFFNF} \leq 20\text{cm}$<br>$r2=r1+2\text{cm}$ | | | +| SNR @ $r_{DFF/IFF}$ (dB) | Mean Err to FF Reference (dB) | Influence of Noise (dB) | Average SNR @ $r1$ (dB) | Mean Err to FF Reference (dB) | Average SNR @ $r1$ (dB) | Average SNR @ $r2$ (dB) | Mean Err to FF Reference (dB) | +| -15 | 15.1 | 15.1 | -4.3 | 5.6 | 2.5 | 1.2 | 3.6 | +| -10 | 10.4 | 10.4 | 0.7 | 2.6 | 7.5 | 6.2 | 1.5 | +| -5 | 6.2 | 6.2 | 5.7 | 1 | 12.5 | 11.2 | 0.5 | +| 0 | 3 | 3 | 10.7 | 0.3 | 17.5 | 16.2 | 0.2 | +| 5 | 1.2 | 1.2 | 15.7 | 0 | 22.5 | 21.2 | 0 | +| 10 | 0.4 | 0.4 | 20.7 | 0.1 | 27.5 | 26.2 | 0 | +| 15 | 0.1 | 0.1 | 25.7 | 0.1 | 32.5 | 31.2 | 0 | + +**Table 5.1.4.9-6: Influence of Noise Simulations and Calculations for DFF/IFF, CFFDNF, CFFNF based on 1000 random offsets uniformly spaced within 10cm (PC1) in a single hemisphere and $N=1$ .** + +| DFF/IFF | CFFDNF | CFFNF | +|---------|--------|-------| +| | | | + +| SNR @ r <sub>DFF/IFF</sub> (dB) | Mean Err to FF Reference (dB) | Influence of Noise (dB) | Average SNR @ r <sub>1</sub> (dB) | Mean Err to FF Reference (dB) | Average SNR @ r <sub>1</sub> (dB) | Average SNR @ r <sub>2</sub> (dB) | Mean Err to FF Reference (dB) | +|---------------------------------|--------------------------------|-------------------------|-----------------------------------|--------------------------------|-----------------------------------|-----------------------------------|--------------------------------| +| -15 | 15.1 | 15.1 | -7.2 | 10.5 | -3.1 | -3.8 | 6.8 | +| -10 | 10.4 | 10.4 | -2.2 | 6.2 | 1.9 | 1.2 | 3.4 | +| -5 | 6.2 | 6.2 | 2.8 | 3.0 | 6.9 | 6.2 | 1.3 | +| 0 | 3 | 3 | 7.8 | 1.1 | 11.9 | 11.2 | 0.4 | +| 5 | 1.2 | 1.2 | 12.8 | 0.4 | 16.9 | 16.2 | 0.1 | +| 10 | 0.4 | 0.4 | 17.8 | 0.1 | 21.9 | 21.2 | 0.1 | +| 15 | 0.1 | 0.1 | 22.8 | 0.0 | 26.9 | 26.2 | 0.1 | + +While these results compare the simulated Influence of Noise, i.e., Mean Err to FF Reference, for the different methodologies at fixed DFF/IFF SNRs based on a 1m free-space path loss, it should be pointed out that for the same SNR at $r_{\text{CFDFNF}}$ , the CFDFNF Influence of Noise is lower than the CFFNF Influence of Noise for the same SNR at $r_{2,\text{CFNF}} < r_{\text{CFDFNF}}$ . + +#### 5.1.4.10 Simulation Results for offset error MU + +The analyses in this clause are to determine the uncertainties on EIRP/EIS when the antenna offset is declared incorrectly, i.e., when the actual antenna offset deviates from the declared antenna offset. These analyses are based on differences in path losses between the declared and the actual offsets and the difference in compensated probe gains. Here, the following assumptions were made: + +- 1000 random offsets ( $x_{\text{offset}}, y_{\text{offset}}, z_{\text{offset}}$ ), illustrated with red dots in Figure 5.1.4.10-1, were simulated and each offset was considered the actual offset of the antenna array. +- For each random offset, 1000 random declaration errors ( $x_{\text{error}}, y_{\text{error}}, z_{\text{error}}$ ), illustrated with blue dots in Figure 5.1.4.10-1, were generated with a fixed radius from the actual offset +- For each actual offset and for each of the declared offsets, the device orientation was calculated so that the NF probe is placed in the actual/declared NF beam peak direction + - For each actual offset and for each of the declared offsets, the corresponding path losses between the (actual/declared) antenna offsets and the probe were determined + - For each actual offset and for each of the declared offsets, the corresponding probe antenna gains were determined in the respective NF beam peak directions. + +**1000 Random Array Offsets** +(Max Array Offset: 125mm with $R_{\text{QZ}}=150\text{mm}$ ) + +![Figure 5.1.4.10-1: Two 3D plots illustrating antenna offsets and errors. The left plot shows 1000 random array offsets (red dots) distributed within a circular area in the xy-plane, with axes labeled x_offset, y_offset, and z_offset. The right plot shows 1000 random declaration errors (blue dots) distributed within a circular area in the xy-plane, with axes labeled x_error, y_error, and z_error. Both plots show a dense cloud of points centered around the origin.](c2e6ba8cdf072f7f5934f8e90664be1b_img.jpg) + +Figure 5.1.4.10-1: Two 3D plots illustrating antenna offsets and errors. The left plot shows 1000 random array offsets (red dots) distributed within a circular area in the xy-plane, with axes labeled x\_offset, y\_offset, and z\_offset. The right plot shows 1000 random declaration errors (blue dots) distributed within a circular area in the xy-plane, with axes labeled x\_error, y\_error, and z\_error. Both plots show a dense cloud of points centered around the origin. + +**Figure 5.1.4.10-1: Illustration of simulation assumptions. The 1000 random offsets considered the actual antenna offsets shown on the left; 1000 random errors around each offset shown on the right.** + +The results for this analysis are tabulated in Table 5.1.4.10-1. Similar analyses from another company are included in Table 5.1.4.10-1 focusing only on the uncertainties based on the effect of the antenna offset error on the pathloss, i.e., without the probe antenna gain impact. + +**Table 5.1.4.10-1: Statistical results of 1M EIRP CFFDNF simulations to determine the effect of offset declaration error on EIRP/EIS** + +| Error in declared offset [cm] | Range Length [m] | Company A | Company B | | +|-------------------------------|------------------|-----------------------|----------------------|-----------------------| +| | | Std. Dev of EIRP [dB] | Mean EIRP error [dB] | Std. Dev of EIRP [dB] | +| 0.1 | 0.4 | | 0.056 | 0.019 | +| 0.5 | 0.2 | 0.17 | | | +| | 0.25 | 0.12 | | | +| | 0.3 | 0.10 | | | +| | 0.35 | 0.08 | | | +| | 0.4 | 0.07 | 0.074 | 0.087 | +| | 0.45 | 0.06 | | | +| | 1 | 0.03 | | | +| | 20 | 0.00 | | | +| 1 | 0.2 | 0.35 | | | +| | 0.25 | 0.24 | | | +| | 0.3 | 0.19 | | | +| | 0.35 | 0.16 | | | +| | 0.4 | 0.14 | 0.129 | 0.221 | +| | 0.45 | 0.12 | | | +| | 1 | 0.05 | | | +| | 20 | 0.00 | | | +| 2 | 0.2 | 0.71 | | | +| | 0.25 | 0.49 | | | +| | 0.3 | 0.38 | | | +| | 0.35 | 0.32 | | | +| | 0.4 | 0.28 | | | +| | 0.45 | 0.24 | | | +| | 1 | 0.10 | | | +| | 20 | 0.01 | | | + +### 5.1.5 Applicability of NF methodologies + +Here, the applicability of the NF methodologies considered, i.e., direct Near Field (DNF), Combined Far-Field/Direct Near Field (CFFDNF), Combined Far-Field/Near Field (CFFNF), and Combined far-field/delta-near-field (CFFdeltaNF), are further analysed. + +The CFFNF with transform (e.g. asymptotic expansion transform) has the following applicability: + +- Beam peak searches and spherical coverage test cases are performed with black box approach using the FF probe. Performing these tests with the NF measurement probe would require the extensive black&white-box approach which is not deemed a feasible enhancement of the methodology. +- The low UL power/high DL power EIRP/EIS test cases in known FF BP direction are applicable to the black-box approach using transform techniques: + - Three radii approach (i.e. local search on radius r1 and very localized searches at r2 and r3) can be used. + - EIRP/EIS can be approximated very accurately with the NF probe at very close distances with optimized improvements in relaxations + - 22cm for PC3 with ~0.3dB standard deviation and ~0.1dB mean error (systematic uncertainty), + - 32cm for PC1 with ~0.6dB standard deviation and ~0.3dB mean error (systematic uncertainty). + +- The unknown antenna location can be estimated accurately which allows very accurate TRP measurements at very close distances with large improvement in relaxations and no additional MU (mean error and standard deviation). +- an MU element related to estimated DUT antenna offset error is required +- an MU element related to the sensitivity of the asymptotic expansion approach to relative measurement uncertainty is required +- the Influence of Noise MU element needs to be revised for the asymptotic expansion approach +- EIRP/EIS based test cases require the compensation of the path loss (with respect to the active antenna array) and the compensation of the probe antenna pattern +- The low UL power/high DL power EIRP/EIS test cases in known FF BP direction are applicable to the black&white-box approach. +- Two radii approach without local searches can be used. +- EIRP/EIS can be approximated very accurately with the NF probe at very close distances with optimized improvements in relaxations. + - 22cm for PC3 with no additional MU (mean error and standard deviation). + - 32cm for PC1 with~0.1dB mean error (systematic uncertainty). +- an MU element related to declared DUT antenna offset error is required +- an MU element related to the relative measurement uncertainty on the asymptotic expansion approach is required +- the Influence of Noise MU element needs to be revised for the asymptotic expansion approach +- EIRP/EIS based test cases require the compensation of the path loss (with respect to the active antenna array) and the compensation of the probe antenna pattern +- The low UL power TRP test cases are not applicable to transform approach (CFFNF) since that approach would be test time prohibitive. However, the known offset (empirical evaluation with black box approach or declared with black&white-box approach) can be compensated using CFFDNF approach to obtain very accurate TRP results at very close distances. + +The CFFDNF has the following applicability: + +- Beam peak searches and spherical coverage test cases are performed with black box approach using the FF probe. Performing these tests with the NF measurement probe would require the extensive black&white-box approach which is not deemed a feasible enhancement of the methodology. +- The low UL power/high DL power EIRP/EIS test cases in the known FF BP direction are applicable to the black&white-box approach. + - A local search to determine the NF test direction and/or optimize EIRP/EIS is not required. + - EIRP/EIS can be approximated very accurately in the NF, i.e., at + - 35cm for PC3 with an additional 0.1dB mean error (systematic error) due to reduced range length + - 45 cm for PC1 with an additional 0.5dB mean error (systematic error) due to reduced range length. +- For PC3, TRP test cases do not require additional measurement uncertainty due to reduced range length for + - range lengths exceeding 20cm if the path loss correction is applied for measurement grids with step size of at most 5° + - range lengths exceeding 25cm if the path loss correction is applied for measurement grids with step size of at most 10° + +- non-uniform measurement grid can be utilized if the path loss correction is applied for measurement grids to further reduce the number of grid points without any additional measurement uncertainty, i.e., using a constant step size grid of $\Delta\theta=\Delta\phi=5^\circ$ within a $\pm 30^\circ$ cone centred around the NF beam peak and a constant step size grid of $\Delta\theta=\Delta\phi=15^\circ$ outside that cone. +- for range lengths exceeding 40cm if the path loss correction is not applied for measurement grids with step size of at most $10^\circ$ +- For PC1, TRP test cases do not require additional measurement uncertainty due to reduced range length for + - range lengths exceeding 20cm if the path loss correction is applied for measurement grids with step size of at most $5^\circ$ + - non-uniform measurement grid can be utilized if the path loss correction is applied for measurement grids to further reduce the number of grid points without any additional measurement uncertainty, i.e., using a constant step size grid of $\Delta\theta=\Delta\phi=2.5^\circ$ within a $\pm 20^\circ$ cone centred around the NF beam peak and a constant step size grid of $\Delta\theta=\Delta\phi=10^\circ$ outside that cone. + - for range lengths exceeding 35cm if the path loss correction is not applied for measurement grids with step size of at most $5^\circ$ +- EIRP/EIS based test cases require the compensation of the path loss (with respect to the active antenna array) and the compensation of the probe antenna pattern +- an MU element related to declared DUT antenna offset error is required + +The CFFdeltaNF has the following applicability: + +- Beam peak searches and spherical coverage test cases are performed with black box approach using the FF probe. Performing these tests with the NF measurement probe would require the extensive black&white-box approach which is not deemed a feasible enhancement of the methodology. +- The low UL power/high DL power EIRP/EIS test cases in the known FF BP direction are applicable to the black-box approach. + - A local search to determine the NF test direction is required. + - EIRP/EIS can be approximated very accurately in the NF, i.e., at + - 35cm for PC3 with an additional 0.14dB mean error (systematic error) due to reduced range length for a 1deg step size of the NF local search grid size (based on antenna pattern/configuration changes); the effect of pattern changes due to non-linear PA behaviour is FFS. + - 45cm for PC1 with an additional 0.5dB mean error (systematic error) due to reduced range length for a 1deg step size of the NF local search grid size (based on antenna pattern/configuration changes); the effect of pattern changes due to non-linear PA behaviour is FFS. +- The low UL power TRP test cases are not applicable. + +DNF has the following applicability: + +- Beam peak searches and spherical coverage test cases are not applicable for the black-box approach. An extensive black&white-box approach would be required to perform these tests with the NF measurement probe. Given the complexities of the extensive black&white-box approach, DNF is not deemed a feasible enhancement of the methodology for conformance testing but it might be suitable during UE development phase. +- The low UL power/high DL power EIRP/EIS test cases in the known FF BP direction are not applicable to the black box approach. +- The applicability of the low UL power/high DL power EIRP/TRP/EIS test cases in the known BP direction and with the black&white-box approach is FFS. + +The assumption for this “black & white box” testing approach is that the antenna phase centre offset for the antenna panel that corresponds to the FF beam peak is known and declared, i.e., following the “white box” approach discussed earlier. On the other hand, however, it is assumed that the geometric centre of the DUT is aligned with the centre of the + +QZ, i.e., following the “black box” approach. This approach would have the same advantages as the “black box” approach over the “white box” approach in terms of complexity, test time, MU, and improvements of the relaxations and is summarized in Table 5.1.5-1 below. + +**Table 5.1.5-1: Comparison between the “black box” and “black & white box” approaches** + +| Approach | Knowledge of FF BP Direction (from Meas.) | Declaration of Antenna Phase Centre Offset of Antenna yielding BP | Need for FF probes and UBF | Need for local searches around NF BP | Meas. at different Radii | Test Time Impact | Estimated maximum Improvement of Relaxation (NOTE 1) | +|---------------------------------------------|-------------------------------------------|-------------------------------------------------------------------|----------------------------|--------------------------------------|--------------------------|--------------------------------------------------|----------------------------------------------------------| +| CFFNF for EIRP/EIS using Black Box | Yes | No | Yes | Yes | Yes (x3 in NF) | Medium (local searches & 3 different radii) | ~14dB (for 20cm range length). | +| CFFNF for EIRP/EIS using Black & White Box | Yes | Yes | Yes | No | Yes (x2 in NF) | Low (2 different radii in fixed NF BP Direction) | ~14dB (for 20cm range length) | +| CFFDNF for TRP using Black Box | Yes | No | Yes | No | No | None | Without offset correction: ~10dB (for 32cm range length) | +| CFFDNF for TRP using Black & White Box | Yes | Yes | Yes | No | No | None | With offset correction: ~14dB (for 20cm range length) | +| CFFDNF for EIRP/EIS using Black & White Box | Yes | Yes | Yes | FFS | No | Depends on local search | With pathloss correction: ~9dB (for 35cm range length) | +| CFFdeltaNF for EIRP/EIS using Black Box | Yes | No | Yes | Yes | Yes (x1 FF, x2 NF) | Low (local search) | ~9dB (for 35cm range length) | + +NOTE 1: Improvement of relaxation is only considering Free Space Path Loss + +### 5.1.6 Improvement of permitted methods + +Tables 5.1.6-1 and 5.1.6-2 below provide a preliminary list of potential improvement of permitted methods based on the analysis provided by one company and are applicable to the frequency range of 24.25 – 43.5 GHz. + +**Table 5.1.6-1: Summary of potential improvement of permitted methods by Tx test case (24.25 – 43.5 GHz)** + +| Clause | Requirement | Testability issue | Test Metric | Regulatory related | TS 38.521-2 Test Requirements | Potential improvement | +|---------|--------------------------------|-------------------|------------------------------------------------------|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------| +| 6.3.1 | Minimum output power | Low UL power | EIRP (Link=TX beam peak direction, Meas=Link angle). | No | No relaxation for PC1. For other power classes, relaxation varies from 0dB to 13.5dB depending on the operating band and channel bandwidth. | Improvements remove required relaxations from TC | +| 6.3.2 | Transmit OFF power | Low UL power | TRP (Link=TX beam peak direction, Meas=TRP grid) | Yes | Relaxations for n257: 21.4dB @ 50MHz, 24.4dB @ 100MHz, 27.4dB @ 200MHz and 30.4dB @ 400MHz.<br><br>Relaxations for n258 and n261: [21.4]dB @ 50MHz, [24.4]dB @ 100MHz, [27.4]dB @ 200MHz and [30.4]dB @ 400MHz.<br><br>Relaxations for n260: [24.1]dB @ 50MHz, [27.1]dB @ 100MHz, [30.1]dB @ 200MHz and [33.1]dB @ 400MHz. | ~ 10dB for FR2a and FR2b | +| 6.5.1 | Occupied bandwidth | Low UL power | OBW (Link=TX beam peak direction, Meas=Link angle) | Yes | No relaxations for FR2a and FR2b | N/A for FR2a and FR2b | +| 6.5.2.3 | Adjacent channel leakage ratio | Low UL power | TRP (Link=TX beam peak direction, Meas=TRP grid). | Yes | Relaxation for n257, n258 and n261: 0dB, except for 200MHz (1.5dB in two test IDs) and 400MHz (between 0 and 5.5dB) | Improvements remove required relaxations from TC<br><br>TC coverage is extended for FR2b | +| 6.5.3.2 | Additional spurious emissions | Low UL power | TRP (Link=TX beam peak direction, Meas=TRP grid). | Yes | Between 0.3dB and 13dB relaxation depending on the combination of NR Band and Protected band. | TBD | + +**Table 5.1.6-2: Summary of potential improvement of permitted methods by Rx test case (24.25 – 43.5 GHz)** + +| Clause | Requirement | Testability issue | Test Metric | Regulatory related | TS 38.521-2 Test Requirements | Potential improvement | +|--------|---------------------------------------|-------------------|-----------------------------------------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------| +| 7.4 | Maximum input power | High DL power | EIS (Link=RX beam peak direction, Meas=Link angle). | No | 26dB relaxation for 24.25 ~ 29.5 GHz and 34 dB relaxation for 37 ~ 40 GHz with respect to minimum requirements. | ~ 12dB for FR2a<br>~16dB for FR2b | +| 7.5 | Adjacent channel selectivity (case 1) | High DL power | EIS (Link=RX beam peak direction, Meas=Link angle) | Yes | 50MHz: 1.8dB relaxation for power in transmission BW and interferer for band n260.<br><br>100MHz: 4.8dB relaxation for power in transmission BW and interferer for band n260.<br><br>200MHz and 400MHz are deemed not testable. | Similar improvements as for TC 7.4<br><br>Improvements remove required relaxations from TC | +| 7.5 | Adjacent channel selectivity (case 2) | High DL power | EIS (Link=RX beam peak direction, Meas=Link angle) | No | Decision not test ACS case 2. | Interferer need ~ 15-22dB relaxation | +| 7.6.2 | In-band blocking | High DL power | EIS (Link=RX beam peak direction, Meas=Link angle) | Yes | 50MHz: 1.8dB relaxation for power in transmission BW and interferer for band n260.<br><br>100MHz: 4.8dB relaxation for power in transmission BW and interferer for band n260.<br><br>200MHz and 400MHz are deemed not testable. | Similar improvements as for TC 7.4<br><br>Improvements remove required relaxations from TC | +| 7.9 | Receiver spurious emissions | Low UL power | TRP (Link=TX beam peak direction, Meas=TRP grid). | Yes | Relaxations for n257, n258, n260, and n261: 10.2dB between 6-20GHz, 17.2dB between 20-40GHz and 33.1dB between 40GHz and the 2 <sup>nd</sup> harmonic.<br><br>Relaxations for other bands are still TBD. | TBD | + +For a given test case, NF based solutions should only be considered if the improvement for current methods is not enough to remove the relaxations determined by RAN5. + +## 5.2 Polarization basis mismatch between the TE and DUT + +### 5.2.1 General + +The investigation of polarization basis mismatch enhancements to the FR2 test methodology includes the following aspects: scope of test cases with polarization basis mismatch between the TE and DUT issues, enhanced test methods, applicability of the enhanced test methods. + +The initial testing methodology for FR2 UE RF requirement verification is defined in [3] and features a measurement antenna capable of + +- transmitting and receiving on two orthogonal polarizations +- introducing linearly polarized downlink signals at the centre of the quiet zone one polarization at a time +- measuring the total uplink signal power by combining the power measured by two orthogonally polarized antennas sequentially or +- demodulating the signal received by a single polarization at a time. + +Regarding polarization basis mismatch between the UE TE and DUT, there are two main issues: + +- DL polarization basis mismatch for EIRP measurement. The mismatch between the TE and UE may lead such UEs to disable a Tx chain associated with one DL polarization and may result in an EIRP measurement which fails to include the polarization gain at some test points; +- UL polarization basis mismatch for demodulation. Some UE implementations may support uplink transmission diversity schemes which, although transparent to the specification, impact the demodulation performance when the UL signal is demodulated on just a single polarization. + +Therefore, these two issues are addressed separated with different approach. The potential solutions to minimize the impact of polarization basis mismatch address two distinct goals: to enhance the EIRP measurement of UEs with various capabilities, and to enhance the test equipment demodulation performance in the uplink, such that a test mode to disable Tx diversity at the UE is no longer necessary for the UE to perform conformance testing. + +### 5.2.2 Enhanced test method for EIRP measurement + +#### 5.2.2.1 TPMI method + +Transmitted Matrix Precoding Indicator (TPMI) is the basis of codebook based transmission enabling multi-port antenna transmission. TPMI method is identified as applicable method to enhance EIRP measurement, which is able to activate dual polarization transmission in EIRP measurement. The applicability of this method is defined in Clause 5.2.2.2. + +For FR2 UEs support the TPMI method, the precoding matrix is given by Table 5.2.2.1-1 (same as Table 6.3.1.5-1 in TS 38.211 [4]). 2Tx TPMI index 2-5 can force UE single-layer transmission using two antenna ports. Among them, only TPMI index 2 is selected for EIRP measurement. + +**Table 5.2.2.1-1: Precoding matrix for single-layer transmission using two antenna ports.** + +| TPMI index | (ordered from left to right in increasing order of TPMI index) | | | | | | | | +|------------|----------------------------------------------------------------|--|--|--|--|--|---|---| +| 0 – 5 | | | | | | | - | - | + +The permitted test methods (i.e. DFF, IFF and NFTF) in [3] are all applicable for TPMI method with the additional procedure that the UE should be configured with TPMI index and working at single-layer transmission using two antenna ports, before performing EIRP-based test procedures in Clause 5.2.1.3 in TR38.810 [3].: + +- Peak EIRP Measurement Procedure +- TRP Measurement Procedure +- TX Beam Peak direction search and EIRP Spherical Coverage + +#### 5.2.2.2 Applicability of TPMI side condition method + +TPMI is applicable for one layer transmission with multi-port antenna. In FR2, dual polarization can be regarded as dual antenna ports, so it is natural to activate dual polarization transmission with TPMI side condition in EIRP measurement procedure. However, for TPMI supporting dual antenna ports, the number of SRS ports (*nrofSRS-Ports*) is configured as 2 for both one layer transmission with ‘full power transmission’ and two layers transmission with regular UL MIMO, as specified in clause 6.1 of TS 38.101-2 [2]: + +For a UE that supports 'UL full power transmission' and is configured to transmit a single layer with $nrofSRS-Ports = 2$ , the requirements for UL MIMO operation apply only when it is configured for any of its declared full power modes in IE *FullPowerTransmission-r16* (as defined in TS 38.331[13]). + +For a UE configured to transmit 2 layers, transmitter requirements for UL MIMO operation apply when the UE transmits on 2 ports on the same CDM group. The UE may use higher MPR values outside this limitation. + +Thus, TPMI method is applicable for the following FR2 UEs: + +- Rel-15 Coherent UE +- Rel-16 Coherent UE +- Rel-16 UE supporting UL full power transmission model ( $ul-FullPowerTransmission = fullpowerModel1$ ) + +Other UEs are not applicable for TPMI based test method. + +#### 5.2.2.3 Alternative test method + +A number of open issues have been identified with the configuration of 2-port CSI-RS method, and a conclusion whether this method is a feasible enhancement is TBD. + +### 5.2.3 Enhanced test method for UL demodulation measurement + +#### 5.2.3.1 Test equipment Zero-forcing MIMO receiver + +As an enhancement to the FR2 test equipment topology, it has been proposed to adopt a zero-forcing MIMO receiver architecture so that dual-polarization transmissions by the UE can be demodulated by the test equipment receiver. + +Two methods of demodulation and EVM calculation were discussed, one utilized DMRS-based channel inversion (Method 1), and the other based on inversion of the LSE-estimate of the channel (Method 2). + +##### 5.2.3.1.1 Method 1 + +###### 5.2.3.1.1.1 Method 1 description + +The EVM calculation method for 2-layer measurements is shown in Figure 5.2.3.1.1.1-1 and for 1-layer measurements in Figure 5.2.3.1.1.1-2. + +![Block diagram of Method 1 for UL demodulation measurement. The diagram shows two input paths (TE port 1 and TE port 2) entering RF correction blocks. The outputs of RF correction are split: one path goes through FFT @ CP/2 to a 'DMRS based MIMO Channel Estimation + MIMO Equalization (2x2 per SC)' block. This block outputs MS(f,t) Layer 1 and MS(f,t) Layer 2. These signals go to 'Decision + LS estimation per slot (1x1 per SC)' blocks, which output NS(f,t) Layer 1 and NS(f,t) Layer 2. The other path from RF correction goes through FFT @ CP/2 +/- W/2 to a 'MIMO Equalization, Layer separation (matrix multiply)' block. This block outputs Layer 1 and Layer 2. These signals go to 'Layer 1 "Equalization" (vector multiply)' and 'Layer 2 "Equalization" (vector multiply)' blocks, which output EVM Layer 1 and EVM Layer 2. Green arrows indicate feedback from the EVM calculation blocks back to the channel estimation and equalization blocks.](b47f393ea2c781f313367435c7166abb_img.jpg) + +Block diagram of Method 1 for UL demodulation measurement. The diagram shows two input paths (TE port 1 and TE port 2) entering RF correction blocks. The outputs of RF correction are split: one path goes through FFT @ CP/2 to a 'DMRS based MIMO Channel Estimation + MIMO Equalization (2x2 per SC)' block. This block outputs MS(f,t) Layer 1 and MS(f,t) Layer 2. These signals go to 'Decision + LS estimation per slot (1x1 per SC)' blocks, which output NS(f,t) Layer 1 and NS(f,t) Layer 2. The other path from RF correction goes through FFT @ CP/2 +/- W/2 to a 'MIMO Equalization, Layer separation (matrix multiply)' block. This block outputs Layer 1 and Layer 2. These signals go to 'Layer 1 "Equalization" (vector multiply)' and 'Layer 2 "Equalization" (vector multiply)' blocks, which output EVM Layer 1 and EVM Layer 2. Green arrows indicate feedback from the EVM calculation blocks back to the channel estimation and equalization blocks. + +**Figure 5.2.3.1.1.1-1: EVM calculation block diagram for 2-Layer UL MIMO** + +![Block diagram for 2-Layer UL MIMO EVM calculation. Two TE ports (TE port 1 and TE port 2) feed into RF correction blocks. The outputs of RF correction are split: one path goes to FFT @ CP/2, and the other goes to FFT @ CP/2 +/- W/2. The FFT @ CP/2 outputs feed into a 'DMRS based Channel Estimation + Equalization' block. The output of this block is MS(f,t), which feeds into a 'Decision + LS estimation per slot (1x1 per SC)' block. The output of this block is NS(f,t), which feeds into an 'EVM' block. The FFT @ CP/2 +/- W/2 outputs feed into a 'Maximum Ratio Combining' block. The output of this block feeds into an 'LS Equalization (vector multiply)' block. The output of this block also feeds into the 'EVM' block. A green arrow points from the 'DMRS based Channel Estimation + Equalization' block to the 'Maximum Ratio Combining' block. A green arrow also points from the 'Decision + LS estimation per slot' block to the 'LS Equalization (vector multiply)' block.](8f8caebe58364416a2eda21039d8c7bf_img.jpg) + +Block diagram for 2-Layer UL MIMO EVM calculation. Two TE ports (TE port 1 and TE port 2) feed into RF correction blocks. The outputs of RF correction are split: one path goes to FFT @ CP/2, and the other goes to FFT @ CP/2 +/- W/2. The FFT @ CP/2 outputs feed into a 'DMRS based Channel Estimation + Equalization' block. The output of this block is MS(f,t), which feeds into a 'Decision + LS estimation per slot (1x1 per SC)' block. The output of this block is NS(f,t), which feeds into an 'EVM' block. The FFT @ CP/2 +/- W/2 outputs feed into a 'Maximum Ratio Combining' block. The output of this block feeds into an 'LS Equalization (vector multiply)' block. The output of this block also feeds into the 'EVM' block. A green arrow points from the 'DMRS based Channel Estimation + Equalization' block to the 'Maximum Ratio Combining' block. A green arrow also points from the 'Decision + LS estimation per slot' block to the 'LS Equalization (vector multiply)' block. + +**Figure 5.2.3.1.1.1-2: EVM calculation block diagram for 1-Layer** + +The TE receives signals from 2 different ports which are connected to the dual polarized measurement antenna in the FR2 test system. + +For the 2-layer transmission case shown in Figure 5.2.3.1.1.1-1 a MIMO equalization step as described in section 5.2.3.1.1.2 is performed to separate the layers. + +For the 1-layer transmission case shown in Figure 5.2.3.1.1.1-2 the signals from both measurement antenna polarizations are combined using maximum ratio combining as described in section 5.2.3.1.1.3. + +Each layer is then processed as described in section 5.2.3.1.1.4 to receive the measurement results for each individual layer. + +###### 5.2.3.1.1.2 Method 1 MIMO Equalization + +The MIMO equalization is based only on reference signals (DMRS) without using any data symbols. In order to obtain comparable EVM results independent of the number of DMRS symbols per slot, only the first DMRS symbol in each slot is used. + +Estimation of effective 2x2 channel matrix is a well known procedure if reference signals use different subcarriers, e.g. in case of DMRS antenna ports 0 and 2. In case that same subcarriers are used, e.g. DMRS antenna ports 0 and 1, a channel decomposition is necessary taking advantage of the orthogonal codes $w_r$ and $w_i$ and assuming identical channel coefficients for adjacent subcarriers of same CDM group. + +Effective channel including the precoding matrix $P$ is: + +with + +where $y$ denotes the received symbol on port index $n$ and $r$ the reference signal for layer index $v$ . + +Since reference signals of a specific layer are transmitted only on subcarriers of one CDM group channel, interpolation is needed in order to obtain channel coefficients for all subcarriers. Channel interpolation is done using the channel coefficients of active CDM group in all other CDM groups. + +The channel coefficients used to calculate the equalizer coefficients are obtained after channel smoothing in frequency domain by computing the moving average of interpolated channel coefficients. The moving average window size is 7. For subcarriers at or near the edge of allocation the window size is reduced accordingly. + +The ZF equalizer coefficients are calculated as the inverse of the effective channel matrix, in general: + +###### 5.2.3.1.1.3 Method 1 Maximum Ratio Combining + +The channel estimation for maximum ratio combining is based only on reference signals (DMRS) w/o including any data symbols. One or all DMRS symbols of one slot can be considered, but in order to obtain comparable EVM results independent of number of DMRS symbols per slot, only first DMRS symbol is used. + +Estimation of effective $2 \times 1$ channel is a well known procedure. In case of transmit diversity, the effective channel includes the precoding matrix $P$ : + +with + +where $y$ denotes the received symbol on port index $n$ and $r$ the reference signal. + +Since reference signals are transmitted only on subcarriers of one CDM group, channel interpolation is needed in order to obtain channel coefficients for all subcarriers. Channel interpolation is done using the channel coefficients of active CDM group in all other CDM groups. + +The channel coefficients used to calculate the equalizer coefficients are obtained after channel smoothing in frequency domain by computing the moving average of interpolated channel coefficients. The moving average window size is 7. For subcarriers at or near the edge of allocation the window size is reduced accordingly. + +The ZF equalizer coefficients for maximum ratio combining are calculated as pseudo inverse of effective channel, in general: + +###### 5.2.3.1.1.4 Method 1 Layer processing + +After performing either the MIMO equalization as described in section 5.2.3.1.1.2 or the maximum ratio combining as described in section 5.2.3.1.1.3, each layer is processed using the existing procedure as defined in Annex E of TS 38.521-1 [6]. + +Since the channel estimation is calculated only on first DMRS symbol an averaging including all 14 symbols of one slot, i.e. data and reference signals, is needed in order to minimize EVM. The averaging is achieved by the LS equalization method described for single layer in Annex E.3. of TS 38.521-2 [6]. + +$MS(f,t)$ and $NS(f,t)$ are processed with a least square (LS) estimator, to derive one equalizer coefficient per time slot and per allocated subcarrier. $EC(f)$ is defined for each layer as: + +With $*$ denoting complex conjugation. $EC(f)$ are used to equalize layer data symbols. + +EVM equalizer spectral flatness is derived from equalizer coefficients for each layer as follows: + +##### 5.2.3.1.2 Method 2 + +###### 5.2.3.1.2.1 Method 2 description + +The block diagram of this demodulation scheme for FR2 2L UL is shown in figure 5.2.3.1.2.1-1. Everything to the right of the FFT blocks is per SC, and therefore must be replicated for the entire UL allocation. Figure 5.2.3.1.2.1-2 shows the 2L demodulation calculator while suppressing sections that would be unused for single layer operation. + +For the 2-layer transmission case shown in Figure 5.2.3.1.2.1-1 a MIMO equalization step as described in section 5.2.3.1.2.2 is performed to separate the layers. + +For the 1-layer transmission case shown in Figure 5.2.3.1.2.1-2 the signals from both measurement antenna polarizations are combined using maximum ratio combining as described in section 5.2.3.1.2.3. + +![Block diagram of the demodulation scheme for FR2 2L UL. The diagram shows two input paths, TE port 1 and TE port 2, each passing through an RF CORRECTION block and an FFT @ Δf block. The outputs of these FFT blocks are fed into a 'Chan Est. from DMRS (2x2 per SC) + Equalization' block. This block also receives 'Measured TE port 2 symbols' and 'Measured TE port 1 symbols'. The output of the channel estimation block is fed into 'Layer 1 IBE' and 'Layer 2 IBE' blocks, which then feed into 'HARD DECISION DECODING' blocks. The 'HARD DECISION DECODING' blocks output 'Reconstructed layer 1 symbols' and 'Reconstructed layer 2 symbols'. The 'Chan Est. from DMRS' block also feeds into an 'LS Channel Estimator. Calculate 'F' (2x2 per SC)' block, which then feeds into a 'Calculate ZF equalizer 'A' (invert channel estimate 'F') 2x2 per SC' block. The output of this block is fed into two 'Equalizer + timing adjustment (matrix multiply)' blocks. The first 'Equalizer + timing adjustment' block receives inputs from 'FFT @ Δf - W/2' and 'FFT @ Δf + W/2' blocks. The second 'Equalizer + timing adjustment' block receives inputs from 'FFT @ Δf + W/2' and 'FFT @ Δf - W/2' blocks. The outputs of these equalizers are fed into 'Demodulated Layer 1 symbols' and 'Demodulated Layer 2 symbols' blocks, which then feed into 'EVM (sy1)' and 'EVM (sy2)' blocks. The 'EVM (sy1)' and 'EVM (sy2)' blocks output 'EVM_sy1' and 'EVM_sy2' respectively. The 'EVM (sy1)' and 'EVM (sy2)' blocks also receive inputs from the 'Reconstructed layer 1 symbols' and 'Reconstructed layer 2 symbols' blocks.](223c6f5bda05ffdd254a828a148b53f1_img.jpg) + +Block diagram of the demodulation scheme for FR2 2L UL. The diagram shows two input paths, TE port 1 and TE port 2, each passing through an RF CORRECTION block and an FFT @ Δf block. The outputs of these FFT blocks are fed into a 'Chan Est. from DMRS (2x2 per SC) + Equalization' block. This block also receives 'Measured TE port 2 symbols' and 'Measured TE port 1 symbols'. The output of the channel estimation block is fed into 'Layer 1 IBE' and 'Layer 2 IBE' blocks, which then feed into 'HARD DECISION DECODING' blocks. The 'HARD DECISION DECODING' blocks output 'Reconstructed layer 1 symbols' and 'Reconstructed layer 2 symbols'. The 'Chan Est. from DMRS' block also feeds into an 'LS Channel Estimator. Calculate 'F' (2x2 per SC)' block, which then feeds into a 'Calculate ZF equalizer 'A' (invert channel estimate 'F') 2x2 per SC' block. The output of this block is fed into two 'Equalizer + timing adjustment (matrix multiply)' blocks. The first 'Equalizer + timing adjustment' block receives inputs from 'FFT @ Δf - W/2' and 'FFT @ Δf + W/2' blocks. The second 'Equalizer + timing adjustment' block receives inputs from 'FFT @ Δf + W/2' and 'FFT @ Δf - W/2' blocks. The outputs of these equalizers are fed into 'Demodulated Layer 1 symbols' and 'Demodulated Layer 2 symbols' blocks, which then feed into 'EVM (sy1)' and 'EVM (sy2)' blocks. The 'EVM (sy1)' and 'EVM (sy2)' blocks output 'EVM\_sy1' and 'EVM\_sy2' respectively. The 'EVM (sy1)' and 'EVM (sy2)' blocks also receive inputs from the 'Reconstructed layer 1 symbols' and 'Reconstructed layer 2 symbols' blocks. + +Figure 5.2.3.1.2.1-1: Demodulation scheme for FR2 2L UL + +![Figure 5.2.3.1.2.1-2: Demodulation scheme for 2L UL, used for single layer UL. This block diagram shows the signal processing flow from two transmit (TE) ports through RF correction, FFT, channel estimation, equalization, and demodulation to produce Layer 1 and Layer 2 symbols and their respective EVM values.](3750b0149a6380885998ab3ca6a8787c_img.jpg) + +The diagram illustrates the demodulation scheme for 2L UL. It starts with two input signals, 'TE port 1' and 'TE port 2', each passing through an 'RF CORRECTION' block. The output of 'TE port 1' is split: one path goes to an 'FFT @ Δf' block, and the other to a 'Chan Est. from DMRS (2x2-per-SC) (2x1-per-SC) + Equalization' block. The output of 'TE port 2' is also split: one path goes to an 'FFT @ Δf' block, and the other to an 'LS Channel Estimator. Calculate 'F' (2x2-per-SC) (2x1-per-SC)' block. The 'Chan Est. from DMRS' block outputs 'Measured TE port 2 symbols' to the 'LS Channel Estimator' and 'Measured TE port 1 symbols' to the 'Calculate ZF equalizer 'A' (invert channel estimate 'F') 2x2 1x2 per SC' block. The 'LS Channel Estimator' outputs 'Reconstructed layer 2 symbols' to a 'HARD DECISION DECODING' block and 'Reconstructed layer 1 symbols' to another 'HARD DECISION DECODING' block. The 'Calculate ZF equalizer 'A'' block outputs to two 'Equalizer + timing adjustment (matrix multiply)' blocks. The first 'Equalizer' block receives inputs from the 'FFT @ Δf' blocks and outputs 'Demodulated Layer 1 symbols' and 'Demodulated Layer 2 symbols' to 'EVM (Lyr1) Δt = Δf - W/2' and 'EVM (Lyr2) Δt = Δf - W/2' blocks, respectively. The second 'Equalizer' block receives inputs from the 'FFT @ Δf' blocks and outputs 'Demodulated Layer 1 symbols' and 'Demodulated Layer 2 symbols' to 'EVM (Lyr1) Δt = Δf + W/2' and 'EVM (Lyr2) Δt = Δf + W/2' blocks, respectively. The 'EVM (Lyr1) Δt = Δf - W/2' block outputs 'EVM\_low' and the 'EVM (Lyr1) Δt = Δf + W/2' block outputs 'EVM\_high'. + +Figure 5.2.3.1.2.1-2: Demodulation scheme for 2L UL, used for single layer UL. This block diagram shows the signal processing flow from two transmit (TE) ports through RF correction, FFT, channel estimation, equalization, and demodulation to produce Layer 1 and Layer 2 symbols and their respective EVM values. + +Figure 5.2.3.1.2.1-2: Demodulation scheme for 2L UL, used for single layer UL + +###### 5.2.3.1.2.2 Method 2 MIMO Equalization + +For the 2L UL MIMO EVM test case, the system is framed as: + +Here, H is the 2x2 OTA channel, G is the 2x2 diversity scheme that the UE uses, and W is the 2x2 precoder matrix. G and W are UE-resident as shown in Figure 5.2.3.1.2.2-1. + +![Figure 5.2.3.1.2.2-1: UE implementation model. This diagram shows the internal structure of the UE, including Layer 1 and Layer 2 processing, Tone Mapping, Layer mapping (with precoder matrix W and diversity matrix G), IFFT, and TX Front-end blocks.](572cf014db14c8234f91c07d5a5a28c6_img.jpg) + +The diagram shows the UE implementation model. It consists of two layers, 'Layer 1' and 'Layer 2', each with a 'CP-OFDM, PUSCH, PUCCH, DM-RS' input. These inputs pass through 'Tone Map' blocks. The outputs of the 'Tone Map' blocks are then processed by a 'Layer mapping' block, which is enclosed in a dashed box. Inside this box, the signals are multiplied by precoder coefficients $W_{1,1}, W_{1,2}, W_{2,1}, W_{2,2}$ and summed. The 'Layer mapping' block also contains a diversity matrix $G = \begin{bmatrix} g_{1,1} & g_{1,2} \\ g_{2,1} & g_{2,2} \end{bmatrix}$ . The outputs of the 'Layer mapping' block are then processed by 'IFFT' blocks and 'TX Front-end' blocks. The entire 'Layer mapping' block is labeled 'DUT' (Device Under Test). + +Figure 5.2.3.1.2.2-1: UE implementation model. This diagram shows the internal structure of the UE, including Layer 1 and Layer 2 processing, Tone Mapping, Layer mapping (with precoder matrix W and diversity matrix G), IFFT, and TX Front-end blocks. + +Figure 5.2.3.1.2.2-1: UE implementation model + +Here, the effective channel (HGW) as seen by the TE can be represented by a 2x2 matrix for each subcarrier ('SC'). The process of equalization is implemented by multiplying data collected simultaneously at the TE receiver ports 'y' by an equalization matrix 'A'. A unique 'A' matrix is computed for each SC. Using the ZF equalization method, 'A' is generated as the inverse of the estimate 'F' of the effective channel HGW for that SC. + +; where + +For each SC, the train of reconstructed symbols and received symbols are jointly used to estimate $F$ (effective channel, also per SC), by minimizing the LSE between the received symbols and those that are calculated from the estimated channel and the reconstructed symbols, over all the symbols in the measurement interval. This technique is a 2L generalization of the legacy method to estimate the legacy rank 1 channel. This LSE minimization procedure results in the following channel estimate: + +Where $\mathbf{x}_k$ and $\mathbf{y}_k$ are respectively the $k^{\text{th}}$ transmitted and received OFDM symbol in the measurement interval: + +Note the strong resemblance to the expression for channel estimate for the single layer legacy demodulation case. + +While $A$ can be taken as the inverse of ' $F$ ' for the ZF equalizer, we show later that there is a more general form of $A$ that helps streamline single layer and 2L treatments. Two aspects bear further consideration: the existence of $F$ and the invertibility of ' $F$ ', see section 5.2.3.1.2.5. The detailed treatment logically derives that if either $F$ or $F^{-1}$ do not exist, it is because the UE cannot support an OTA channel (coded into matrix ' $H$ ') of rank 2, and is unable to maintain valid 2L UL. Failure to calculate either of the quantities therefore is tied to poor UE implementation rather than TE limitation. + +Noting that $A$ is the inverse of the estimate of the product $HGW$ , the equalization step can be written as: + +The matrix equation can be resolved into 2 separate scalar equations corresponding to the two layers: + +Where, $\hat{x}_m$ represents equalized layer data ' $m$ ', $x_m$ represents reconstructed (ideal) layer ' $m$ ' data, and $v_m$ represents noise accompanying ideal layer data ' $m$ ' after equalization. Note that the transmitted symbols are recovered without phase or gain modification, albeit in the presence of accompanying noise (responsible for EVM degradation). This is the case for every allocated SC – when the symbol on each sub carrier on each layer is reproduced without gain modification as this method does, no flatness artefacts are introduced into the measurements. + +###### 5.2.3.1.2.3 Method 2 Maximal Ratio Combining + +The channel estimate remains of the same form as in the 2L case, but the dimensions are now $2 \times 1$ because $x$ is now a scalar for the single layer case: + +Because $x$ is a scalar, $(\sum x x^H)^{-1}$ is merely the reciprocal of a scalar quantity. Consequently, there are no numerical corner cases pertaining to existence of the quantity to ponder. + +Due to $F$ not being square, the equalization matrix ' $A$ ' must be derived as the pseudo inverse of $F$ , rather than a true inverse as in the 2L case: + +This type of ZF equalizer implements MRC for the single layer case. Note that this expression simplifies to $A=F^{-1}$ for the 2L case, and so, ' $A_{SL}$ ' is a more general construction for ' $A$ ' that is applicable to both cases (single layer as well as 2L). + +###### 5.2.3.1.2.4 Method 2 EVM equalizer flatness + +In the legacy single layer UL case, the channel estimate for each SC was a (complex) scalar, so it was straightforward to evaluate equalizer flatness. In the 2L test case however, the channel equalizer ' $A$ ' consists of 4 elements, 2 for each layer. Framing $A$ as a row vector: + +For layer ‘ $m$ ’, recall that the ZF equalization coefficients for each layer $A_m^T$ are scaled to diagonalize the channel. There is no realistic bound on the relative ratios of the coefficients, but the coefficients together preserve any frequency domain shape of the channel. Therefore, a composite parameter $c_m$ for each layer ‘ $m$ ’ can be used to evaluate the equalizer spectrum flatness, given by: + +Or + +The FR2 single layer case is merely a subset of the 2L case, where ‘ $m$ ’ can take on just one value: 1. + +###### 5.2.3.1.2.5 Method 2 channel invertibility considerations + +Recall that $F$ , the estimate of the effective channel for each sub carrier is derived as an averaging operation over multiple OFDM symbols: + +The existence of $F$ depends on the sum matrix $\Sigma_{xx^H}$ being rank 2. Recall now that ‘ $x_k$ ’ is the train of constellation symbols per SC, for both layers, as embedded in the train of OFDM symbols. For pseudo-random data, the sum matrix $\Sigma_{xx^H}$ accumulates positive values along the diagonal, and random zero-mean values in off diagonal locations (cross correlation across independent data). As the number of OFDM symbols increases in the averaging interval, this matrix tends towards a multiple of an identity matrix. Could this matrix be rank 1 in some corner case? Mathematically, this can happen only if ‘ $x$ ’ is the same (both layers) in a SC for all OFDM symbols in the averaging interval. This outcome is extremely improbable if not impossible due to reliance on scramblers and standardized pseudo-random data generators in the UE. One can therefore conclude that $F$ exists if the TE can merely work out ‘ $x_k$ ’. Since the TE estimates ‘ $x_k$ ’ by decoding measured data (see figure 2.2.1-1), the TE still depends on the UE’s ability to transmit data with enough inter-layer isolation to allow reconstruction. If $F$ does not exist or is ill conditioned, it must mean that the UE is unable to maintain valid 2L UL. + +The invertibility of ‘ $F$ ’ depends on the invertibility of the cross-correlation term $\Sigma_{yx^H}$ in the expression for ‘ $F$ ’: + +The first term inside the parenthesis ( $GW\Sigma_{xx^H}$ ) involves 2 unitary matrices multiplied by a strongly diagonal matrix (as discussed in the section about the existence of $F$ ), and so remains rank 2. The second term inside the parenthesis ( $\Sigma_{nx^H}$ ) is a measure of correlation between noise and data symbols. + +‘Noise’ can be truly thermal (low output power cases) in which case the second term would tend towards an all-zero matrix and can be ignored. We can therefore conclude that in low output power cases, $\Sigma_{yx^H}$ is rank 2 (i.e it is invertible) if $H$ is also rank 2. Now, $H$ contains information about the UE antenna’s cross-pol isolation: $H$ is strongly rank 2 for UE implementations with good cross-pol isolation. $H$ loses rank or becomes ill-conditioned if the UE’s transmit chains suffer from high antenna correlation. If $F$ is not invertible or is ill conditioned, the reason can be traced back to the UE’s inability to maintain valid 2L UL. + +Alternatively, the ‘noise’ can be composed of third order non-linearity from a PA. This is the case for high output power cases. A PA can be approximated by the time domain normalized characteristic shown here ( $k_3 > 0$ ): + +The cubic term retains strong correlation with the linear term, so the PA model’s cubic term output can be approximated as sum of a correlated component (‘ $a \cdot x$ ’, where ‘ $a$ ’ is related to the correlation coefficient of the cubic term to the linear term) and an un-correlated component (‘ $n_{un}$ ’). In the post-FFT frequency domain, $\Sigma_{yx^H}$ can be rewritten as: + +We focus on the matrix inside the parenthesis: + +The third term inside the parenthesis is a measure of correlation between data and the un-correlated component, which (by definition) would tend towards an all-zero matrix and can be ignored, like the low output power case. There is still risk of $\Sigma_{yx^H}$ losing rank and becoming non-invertible, however, for example if the matrix $(GW - a \cdot k_3 \cdot I)$ loses rank. + +Note that this mechanism (3<sup>rd</sup> order nonlinearity) also exists in the case of demodulation by TE with single chain receivers, and experience tells us that PA non-linearity products do not contribute to a situation where the channel cannot be inverted. Legacy demodulation procedures therefore serve as empirical proof of the argument that the matrix $(G \cdot W - a \cdot k_3 \cdot I)$ never loses rank. + +Physically, for compliant UEs, $|k_3|$ is in the range of 0.10-0.20 in normalized form, and $a$ , while PAPR dependent, can be verified to be $\leq 2$ for NR UL waveforms. We also note that matrices $G$ and $W$ are unitary, which allows direct comparison of the terms in $(GW - a \cdot k_3 \cdot I)$ ; the relative magnitude of $|a \cdot k_3|$ is small enough that matrix $B$ would still be dominated by the first term $(GW - \Sigma x x^H)$ for the range of EVMs expected to be measured. We therefore expect $B$ is rank 2 for pseudo random data. Consequently, here too, rank of $\Sigma y x^H$ depends solely on rank of $H$ . i.e $\Sigma y x^H$ is rank 2 (i.e it is invertible) if $H$ is also rank 2. If $F$ is still not invertible (i.e $\Sigma y x^H$ is rank 1), it is because the UE cannot support an OTA channel ( $H$ ) of rank 2, and is unable to maintain valid 2L UL. + +This treatment can conclude with the observation that both $F$ and $F^{-1}$ exist provided the UE can support a rank 2 OTA channel, i.e $\text{rank}(H)=2$ . + +###### 5.2.3.1.2.6 Method 2 DC (LO) cancellation + +EVM calculation is gated by the TE's procedure to cancel LO. Per existing signaling, only one LO location can be declared per BWP for the carrier being tested, be it single layer or two. More significantly, the only locations allowed to be declared are SC locations. For NR, LO cancellation based on signaling declaration of LO location can therefore be performed either pre- or post-FFT. Per layer quantities are only available in the post-FFT, post-equalization domain where the channel has already been diagonalized, so the focus in the treatment below is the post-FFT method. + +A UE can expect LO cancellation only if the LO location is signalled in terms of a valid subcarrier location. If the UE reports 3300 or 3301 via IE *txDirectCurrentLocation* the TE or network can get no information on LO location other than 'it does not coincide with the FFT grid'. This aspect is consistent with the exception in the core-requirement pertaining to this IE. + +The following passage describes a method based on post-FFT LO removal based on LO location declaration via IE *txDirectCurrentLocation*. Post-FFT LO removal involves removing dependency on the LO-bearing SC or being able to ignore the impact of LO leakage. + +Recall that each allocated SC has an instantiation of the post-FFT procedure outlined in figure 2.2.1-2. The equalization matrix 'A' is calculated for each sub carrier and is derived from reconstructed symbols recovered from processing DMRS. In NR, DMRS symbols do not occupy each SC of the OFDM symbol, necessitating some form of interpolation for DMRS-less sub carriers. To minimize impact of LO leakage on the accuracy of the process of reconstructing the transmitted symbols, a logical choice is to select a DMRS comb that skips over the SC declared to have the LO leakage. + +While it is relatively easy to ensure that the reconstruction process remains free of impact from LO leakage by using the comb, the measured symbols 'y' for the LO-bearing SC still contain a systematic and constant leakage term for all OFDM symbols in the measurement interval. + +; where + +where $c_1$ and $c_2$ are complex constants pertaining to the LO leakage. The channel estimate for the LO-bearing SC starts with the LSE estimate: + +There are multiple options to deal with this extra term from LO leakage $(C(\Sigma x^H(\Sigma x x^H)^{-1}))$ . The first option is to use a very long-term averaging to determine 'F' for the LO-bearing SC. Since 'C' is a constant and $(\Sigma x^H)$ can reasonably be assumed to be zero for a long enough average, the contribution of the first term reduces to zero. So, the first option is to do nothing other than ensure a very long-term average is used for calculating 'F' for the LO bearing SC. The second option is to interpolate from neighbour SCs to determine F for the LO-bearing SC. Other, more sophisticated treatments may also exist. 'F' calculated from either of these methods can be compared to 'F' calculated using the LSE-estimate expression over the standard measurement interval to derive the value of 'C' for the measured interval. + +The equalization equation for an LO-bearing SC is: + +![Diagram of the equalization equation for an LO-bearing SC. The equation is \hat{x} = A \cdot y = x + A H n + A C. Three green boxes with leader lines point to parts of the equation: 'Reconstructed symbol' points to \hat{x}, 'EVM contributor' points to A H n, and 'LO leakage component' points to A C.](d2417b04116c354deccb25d98a84a0fb_img.jpg) + +$$\hat{x} = A \cdot y = x + A H n + A C$$ + +Diagram of the equalization equation for an LO-bearing SC. The equation is \hat{x} = A \cdot y = x + A H n + A C. Three green boxes with leader lines point to parts of the equation: 'Reconstructed symbol' points to \hat{x}, 'EVM contributor' points to A H n, and 'LO leakage component' points to A C. + +**Figure 5.2.3.1.2.6-1: Equalization equation for an LO-bearing SC** + +The calculated quantity ‘AC’ can be used both to estimate carrier leakage per layer, as well as to correct the estimated symbol on the LO-bearing SC prior to EVM calculation. + +##### 5.2.3.1.3 Analysis of Method 1 & 2 + +###### 5.2.3.1.3.1 Comparison of both Methods + +To downselect one of the Methods described above, the EVM measurement performance for both methods has been analysed with the following assumptions: + +- Test waveforms constructed with: + - Flat signal PSD + - Injected AWGN +- Signal configuration: + - [50/66] contiguous RBs + - CP-OFDM (QPSK – 64QAM – 256QAM) PUSCH, rank 2 + - UL RMC as defined in appendix of 38.101-2 + +In the following, the results of the analysis of Method 1 and 2 are presented and compared. + +As a first step the EVM accuracy for both methods has been analysed. As can be seen from Figure 5.2.3.1.3.1-1, both Methods show good EVM measurement accuracy, while Method 1 has equivalent or superior accuracy to Method 2. + +![Line graph titled 'EVM calculation error, 3 DMRS symbols/slot'. The y-axis is 'Over-estimation (dB)' ranging from -2.0 to 8.0. The x-axis is 'SNR (dB)' ranging from 10 to 40. Five lines are plotted: Method 1, no smooth (red); Method 1, 3 sample (orange); Method 1, 5 sample (yellow); Method 1, 7 sample (blue); and Method 2, no smooth (green). All lines are near 0 dB over-estimation across the SNR range.](9058545957858eea01975496aa340d5b_img.jpg) + +| SNR (dB) | Method 1, no smooth (dB) | Method 1, 3 sample (dB) | Method 1, 5 sample (dB) | Method 1, 7 sample (dB) | Method 2, no smooth (dB) | +|----------|--------------------------|-------------------------|-------------------------|-------------------------|--------------------------| +| 10 | 0.2 | 0.1 | 0.0 | -0.1 | -0.2 | +| 15 | 0.3 | 0.2 | 0.1 | 0.0 | -0.1 | +| 20 | 0.3 | 0.2 | 0.1 | 0.0 | -0.1 | +| 25 | 0.3 | 0.2 | 0.1 | 0.0 | -0.1 | +| 30 | 0.3 | 0.2 | 0.1 | 0.0 | -0.1 | +| 35 | 0.2 | 0.1 | 0.0 | -0.1 | -0.2 | + +Line graph titled 'EVM calculation error, 3 DMRS symbols/slot'. The y-axis is 'Over-estimation (dB)' ranging from -2.0 to 8.0. The x-axis is 'SNR (dB)' ranging from 10 to 40. Five lines are plotted: Method 1, no smooth (red); Method 1, 3 sample (orange); Method 1, 5 sample (yellow); Method 1, 7 sample (blue); and Method 2, no smooth (green). All lines are near 0 dB over-estimation across the SNR range. + +**Figure 5.2.3.1.3.1-1: EVM accuracy evaluation for slot length signals with Method 1 & 2** + +Figure 5.2.3.1.3.1-2 shows further analysis of Method 1, here the results of 2-layer signal analysed with Method 1 are compared to an analysis of a SISO signal, which has been measured according to the EVM measurement definition in TS 38.521-2 Annex E. For signals with 3 DMRS as defined for the UL RMCs the difference is around 0.2 dB, This applies for all different modulations as can be seen from the graphs for QPSK and 64QAM. + +![Two line graphs showing EVM absolute [%] vs SNR [dB] for QPSK and 64-QAM. The left graph is for QPSK and the right is for 64-QAM. Both graphs compare four cases: 1 DMRS, no smooth; 1 DMRS, 7 sample; 3 DMRS, 7 sample; and SISO (1 layer). In both cases, EVM decreases as SNR increases. The 1 DMRS, no smooth case shows significantly higher EVM than the others, which are clustered together. The 3 DMRS, 7 sample case shows slightly lower EVM than the 1 DMRS, 7 sample case.](5c1059b19e142ca5a6d58f18f3767b97_img.jpg) + +The figure contains two line graphs. The left graph is titled 'EVM absolute - QPSK' and the right graph is titled 'EVM absolute - 64-QAM'. Both graphs plot EVM [%] on the y-axis against SNR [dB] on the x-axis. The x-axis ranges from 15 to 40 dB for QPSK and 20 to 40 dB for 64-QAM. The y-axis ranges from 0 to 20% for QPSK and 0 to 11% for 64-QAM. Four data series are shown in each graph: '1 DMRS, no smooth' (green line with circles), '1 DMRS, 7 sample' (black line with squares), '3 DMRS, 7 sample' (blue line with triangles), and 'SISO (1 layer)' (red line with diamonds). In both graphs, the '1 DMRS, no smooth' series starts at a higher EVM (around 18% for QPSK and 10% for 64-QAM at 15/20 dB SNR) and decreases rapidly. The other three series start lower (around 16% for QPSK and 9% for 64-QAM) and decrease more gradually, converging towards each other at higher SNR values. The '3 DMRS, 7 sample' series consistently shows the lowest EVM across the SNR range. + +Two line graphs showing EVM absolute [%] vs SNR [dB] for QPSK and 64-QAM. The left graph is for QPSK and the right is for 64-QAM. Both graphs compare four cases: 1 DMRS, no smooth; 1 DMRS, 7 sample; 3 DMRS, 7 sample; and SISO (1 layer). In both cases, EVM decreases as SNR increases. The 1 DMRS, no smooth case shows significantly higher EVM than the others, which are clustered together. The 3 DMRS, 7 sample case shows slightly lower EVM than the 1 DMRS, 7 sample case. + +Figure 5.2.3.1.3.1-2: Absolute EVM accuracy evaluation for slot length signals with Method 1 + +Further analysis of Method 1 shows a good performance also under the condition of varying antenna misalignments or antenna port configurations. While in Figure 5.2.3.1.3.1-3 it can be observed that for reasonable SNR levels, the EVM is only overestimated by less than 0.5 dB, this may still mean that the EVM evaluation is impacted by the different antenna ports or antenna misalignment. Figure 5.2.3.1.3.1-4 shows that the EVM evaluation is independent of those factors and the same results are obtained for different combinations of antenna ports and misalignments. + +![Two line graphs showing Over estimation (dB) vs SNR (dB) for the identity matrix (left) and rotation matrix (right). Both graphs compare four cases: 1DMRS_QPSK, 1DMRS_256QAM, 3DMRS_QPSK, and 3DMRS_256QAM. The over estimation is generally low, mostly below 1.0 dB, with some higher values at low SNR for the 1DMRS cases.](f29504cb9770aad6c8c696acad49adff_img.jpg) + +The figure contains two line graphs. The left graph is for the 'identity matrix' and the right graph is for the 'rotation matrix'. Both graphs plot 'Over estimation (dB)' on the y-axis against 'SNR (dB)' on the x-axis. The x-axis ranges from 10 to 40 dB. The y-axis ranges from -2.0 to 8.0 dB. Four data series are shown in each graph: '1DMRS\_QPSK' (blue line with circles), '1DMRS\_256QAM' (orange line with squares), '3DMRS\_QPSK' (grey line with triangles), and '3DMRS\_256QAM' (yellow line with diamonds). At 10 dB SNR, the '1DMRS' cases show higher over estimation (around 4.5 dB for QPSK and 5.0 dB for 256QAM) compared to the '3DMRS' cases (around 0.5 dB). As SNR increases to 20, 30, and 40 dB, the over estimation for all cases drops significantly, staying below 1.0 dB. The '3DMRS' cases maintain a lower over estimation than the '1DMRS' cases across the entire SNR range. Error bars are shown for each data point. + +Two line graphs showing Over estimation (dB) vs SNR (dB) for the identity matrix (left) and rotation matrix (right). Both graphs compare four cases: 1DMRS\_QPSK, 1DMRS\_256QAM, 3DMRS\_QPSK, and 3DMRS\_256QAM. The over estimation is generally low, mostly below 1.0 dB, with some higher values at low SNR for the 1DMRS cases. + +Figure 5.2.3.1.3.1-3: Method 1 EVM evaluation for the identity matrix (left) and rotation matrix (right) + +![Figure 5.2.3.1.3.1-4: Method 1 EVM results for different antenna misalignments and ports. The graph shows EVM [%] on the y-axis (0 to 10) versus SNR [dB] on the x-axis (20 to 40). Two data series are plotted: 'ports (0,1), 0 deg' (blue line with circles) and 'ports (0,2), 45 deg' (red line with crosses). Both series show a decreasing trend of EVM as SNR increases, with the red line generally showing slightly lower EVM values than the blue line.](bb908297bfe73e2759a9dd88ae0506f9_img.jpg) + +| SNR [dB] | EVM [%] (ports (0,1), 0 deg) | EVM [%] (ports (0,2), 45 deg) | +|----------|------------------------------|-------------------------------| +| 20 | 9.2 | 9.2 | +| 21 | 8.2 | 8.2 | +| 22 | 7.2 | 7.2 | +| 23 | 6.2 | 6.2 | +| 24 | 5.2 | 5.2 | +| 25 | 4.2 | 4.2 | +| 26 | 3.2 | 3.2 | +| 27 | 2.2 | 2.2 | +| 28 | 1.2 | 1.2 | +| 29 | 0.8 | 0.8 | +| 30 | 0.6 | 0.6 | +| 31 | 0.4 | 0.4 | +| 32 | 0.3 | 0.3 | +| 33 | 0.2 | 0.2 | +| 34 | 0.1 | 0.1 | +| 35 | 0.1 | 0.1 | +| 36 | 0.1 | 0.1 | +| 37 | 0.1 | 0.1 | +| 38 | 0.1 | 0.1 | +| 39 | 0.1 | 0.1 | +| 40 | 0.1 | 0.1 | + +Figure 5.2.3.1.3.1-4: Method 1 EVM results for different antenna misalignments and ports. The graph shows EVM [%] on the y-axis (0 to 10) versus SNR [dB] on the x-axis (20 to 40). Two data series are plotted: 'ports (0,1), 0 deg' (blue line with circles) and 'ports (0,2), 45 deg' (red line with crosses). Both series show a decreasing trend of EVM as SNR increases, with the red line generally showing slightly lower EVM values than the blue line. + +**Figure 5.2.3.1.3.1-4: Method 1 EVM results for different antenna misalignments and ports** + +###### 5.2.3.1.3.2 Conclusion + +Based on the analysis shown in section 5.2.3.1.3.1 it is recommended to adapt Method 1 as the enhanced test method for UL MIMO demodulation measurement. Further implementation details to ensure that the results among different TE vendors are comparable, are up to RAN5 definition. + +## 5.3 Inter-band (FR2+FR2) CA + +### 5.3.1 General + +In this sub-clause, following analyses with an in-direct far field (IFF) OTA test systems are introduced in achieving RF measurements of an inter-band CA UE in FR2. + +- a) Impact of multiple test antennae + - 1) PSD imbalance with DL signals from test equipment + - DL PSD towards UE supporting independent beam management (IBM) + - DL PSD towards UE supporting common beam management (CBM) + - 2) Impact of off-focus test system antennae + - Quality of quiet zone (QoQZ) + - Rx beam profiles with an independent beam management (IBM) UE + - Propensity to trigger incorrect beam in CBM UE + - Spherical coverage measurement simulation with common beam management (CBM) UE + - 3) Summary on applicability of offset antenna test system +- b) Inter-band testing ramifications + +### 5.3.2 Impact of multiple test antennae + +#### 5.3.2.1 PSD imbalance with DL signals from test equipment + +##### 5.3.2.1.1 DL PSD towards UE supporting independent beam management (IBM) + +An impact of an AoA offset ranging from 0 to 7 degrees was analyzed for UE supporting independent beam management. The gain difference between the CCs is a test case parameter informed by the recent agreement on the PSD difference in the REFSENS and EIS spherical coverage requirement for DL inter-band CA within FR2 [2]. The simulation assumptions are shown in Table 5.3.2.1.1-1 below. + +**Table 5.3.2.1.1-1: Simulation assumptions for PSD imbalance** + +| Simulation Parameters | | +|------------------------------------------|----------------------------------------| +| Antenna array size | 4x1 | +| Element spacing | 5mm | +| Element pattern | See TR38.803 | +| Antenna impairments | Not considered | +| Phase shifter impairments | See TR38.817-01 | +| Transmission line impairments | Modeled TL length and loss per element | +| AoA offset | {0, 2, 5, 7} deg | +| Beam management assumptions | Independent beam management on each CC | +| Center frequencies of component carriers | f1 = 27.9 GHz, f2 = 38.5 GHz | +| Gain difference between CC1 and CC2 | 15.2 dB | + +For each AoA offset the PSD difference between CC1 and CC2 was calculated after spatially filtering the signal with the array response pattern corresponding to each CC. Figure 5.3.2.1.1-1 below illustrates the simulation results. + +![Figure 5.3.2.1.1-1: A line graph titled 'AoA offset analysis, CC1 Fc=27.93 GHz, CC2 Fc=38.50 GHz'. The y-axis is 'PSD difference after spatial filtering between CC1 and CC2 (dB)' ranging from 14 to 22. The x-axis is 'Angular separation between CCs (deg)' ranging from 0 to 7. Two lines are plotted: a blue line for '90 pct conf interval difference' and a red line for 'Max difference'. Both lines start at approximately 16 dB at 0 degrees and increase linearly as angular separation increases. A dashed horizontal line is drawn at 15.2 dB.](609dff0a56be2ded8c960a3672afa937_img.jpg) + +| Angular separation (deg) | 90 pct conf interval difference (dB) | Max difference (dB) | +|--------------------------|--------------------------------------|---------------------| +| 0 | ~15.8 | ~16.0 | +| 2 | ~15.9 | ~16.4 | +| 5 | ~16.2 | ~17.1 | +| 7 | ~16.5 | ~17.7 | + +Figure 5.3.2.1.1-1: A line graph titled 'AoA offset analysis, CC1 Fc=27.93 GHz, CC2 Fc=38.50 GHz'. The y-axis is 'PSD difference after spatial filtering between CC1 and CC2 (dB)' ranging from 14 to 22. The x-axis is 'Angular separation between CCs (deg)' ranging from 0 to 7. Two lines are plotted: a blue line for '90 pct conf interval difference' and a red line for 'Max difference'. Both lines start at approximately 16 dB at 0 degrees and increase linearly as angular separation increases. A dashed horizontal line is drawn at 15.2 dB. + +**Figure 5.3.2.1.1-1: Spatially filtered PSD difference vs. angular separation between CCs** + +Table 5.3.2.1.1-2 below summarizes the simulation results. + +**Table 5.3.2.1.1-2: Simulation results for spatially filtered PSD difference vs. angular separation between CCs** + +| Max excess PSD difference due to AoA offset (dB) | | +|--------------------------------------------------|---------------| +| AoA offset (°) | PSD diff (dB) | +| 2 | 0.4 | +| 5 | 1.1 | +| 7 | 1.7 | + +The requirement for inter-band CA between bands n261 and n260 is defined assuming a non-zero PSD difference between the component carriers. This assumption holds for the class of inter-band CA configurations to which the independent beam management (IBM) type is applicable. It is observed that at least for IBM inter-band CA requirements, AoA offsets of up to 7 degrees between two FR2 CA component carriers do not significantly impact the PSD difference assumption taken for the core requirement. This observation should be double-checked after the band n262 requirements are finalized and the scope of CA configurations with n262 are understood. + +Further note that as part of the Rel-17 FR2 RF enhancement work item, RAN4 is discussing the potential definition of requirements assuming common beam management (CBM) for combination of certain band groups, such as 28+28 GHz. An analysis of the impact of AoA offsets in the test setup for inter-band CA with CBM is needed after the scope of CBM requirements and associated agreements are better understood. + +##### 5.3.2.1.2 DL PSD towards UE supporting common beam management (CBM) + +Following a similar simulation methodology as described in 5.3.2.1.1, an analysis of the impact of an AoA offset ranging from 0 to 7 degrees was analyzed for UE supporting common beam management. The gain difference between the CCs is a test case parameter informed by the recent agreement on the PSD difference in the REFSENS and EIS spherical coverage requirement for DL inter-band CA within FR2 [2]. The simulation assumptions are shown in Table 5.3.2.1.2-1 below. + +Table 5.3.2.1.2-1: Simulation assumptions for PSD imbalance with CBM + +| Simulation Parameters | | +|------------------------------------------|-----------------------------------------------------------------------------------------------| +| Antenna array size | 4x1 | +| Element spacing | 5mm | +| Element pattern | See TR38.803 | +| Antenna impairments | Not considered | +| Phase shifter impairments | See TR38.817-01 | +| Transmission line impairments | Modeled TL length and loss per element | +| AoA offset | {0, 2, 5, 7} deg | +| Beam management assumptions | Common beam management between CC1 and CC2 (codebook optimized for f1) | +| Center frequencies of component carriers | Case 1: f1 = 24.25 GHz, f2 = 29.5 GHz<br>Case 2: f1 = 37.0 GHz, f2 = 43.5 GHz | +| Gain difference between CC1 and CC2 | Case 1: 0.0 dB<br>Case 2: 1.2 dB (difference in EIS spherical coverage between n260 and n259) | + +For each AoA offset the PSD difference between CC1 and CC2 was calculated after spatially filtering the signal with the array response pattern corresponding to each CC. Figure 5.3.2.1.2-1 below illustrates the simulation results. + +![Figure 5.3.2.1.2-1: Two line graphs showing spatially filtered PSD difference (dB) vs. angular separation between CCs (deg). Graph (a) is for Case 1 (24.25 + 29.5 GHz) and graph (b) is for Case 2 (37.0 + 43.5 GHz). Both graphs show a 90 pct conf interval difference (blue line) and a Max difference (red line). In (a), the Max difference increases from ~8.5 dB to ~10.5 dB as angular separation increases from 0 to 7 degrees. In (b), the Max difference increases from ~7.5 dB to ~8.5 dB. The 90 pct conf interval difference remains relatively flat around 2-3 dB in both cases.](b800051c57e75b44155683ea69ed4227_img.jpg) + +Figure 5.3.2.1.2-1: Two line graphs showing spatially filtered PSD difference (dB) vs. angular separation between CCs (deg). Graph (a) is for Case 1 (24.25 + 29.5 GHz) and graph (b) is for Case 2 (37.0 + 43.5 GHz). Both graphs show a 90 pct conf interval difference (blue line) and a Max difference (red line). In (a), the Max difference increases from ~8.5 dB to ~10.5 dB as angular separation increases from 0 to 7 degrees. In (b), the Max difference increases from ~7.5 dB to ~8.5 dB. The 90 pct conf interval difference remains relatively flat around 2-3 dB in both cases. + +Figure 5.3.2.1.2-1: Spatially filtered PSD difference vs. angular separation between CCs; a) Case 1 (24.25 + 29.5 GHz); b) Case 2 (37.0 + 43.5 GHz) + +Table 5.3.2.1.2-2 below summarizes the simulation results. + +**Table 5.3.2.1.2-2: Simulation results for spatially filtered PSD difference vs. angular separation between CCs** + +| AoA offset (°) | Max excess PSD difference due to AoA offset (dB) | | +|----------------|--------------------------------------------------|--------| +| | PSD diff (dB) | | +| | Case 1 | Case 2 | +| 2 | 0.3 | -0.2 | +| 5 | 0.8 | 0.3 | +| 7 | 1.7 | 1.2 | + +Because RAN4 is still discussing the potential introduction of requirements for CBM CA between bands within the same band group (as of #98-e meeting 2021 Jan.), the PSD difference analysis in this subclause assumes a convergence toward 0 dB PSD difference or, in the case of bands with different spherical coverage requirements, for the difference to be bounded by the difference in spherical coverage EIS values. + +We note that because the CBM CA architecture is, in essence, an optimization, the UE receiver is more sensitive to PSD differences beyond those assumed for the core requirement. Although Table 5.3.2.1.2-2 indicates that the maximum excess PSD difference due to AoA offset $\leq 1.7$ dB which is applicable only to PC3 UE, this effect compounds with the beam squint impairment. + +Again noting that the core requirement work on CBM CA is still ongoing, it is not possible to use the results to disqualify the proposed AoA offset method from applicability to CBM CA test cases. However, the impact of AoA offset on PSD difference assumptions made in the core requirement definition should be taken into account. + +#### 5.3.2.2 Impact of off-focus test system antennae + +##### 5.3.2.2.1 Quality of quiet zone (QoQZ) + +The IFF system for FR2 UE OTA testing is constructed around an offset parabolic mirror to collimate beams from a test antenna towards the UE. The architecture allows for a quiet zone (QZ) roughly the size of the spot on the mirror illuminated by the source. The key to this architecture is locating the source at the focus of the parabola that describes the mirror. + +The burgeoning number of FR2 bands place increasing demands on both, the antenna, as well as the RFFE in test equipment. + +The effect of off-focus test system antenna in IFF systems was studied before listing ramifications to inter-band test requirements. The components of the IFF are much larger than the wavelength of signals under test. The primary effect of the EM solution to the IFF problem can hence be determined by an equivalent optics problem. + +From the geometry of a parabola, there is a unique location (the focus) that allows a test antenna to appear as a far-field antenna after reflection off the mirror. The far-field characteristic comes from the wavefront geometry that is transformed by the mirror from spherical to planar. The planar wavefront is normal to the optical axis of the mirror. Unfortunately, the favorable characteristics of the parabolic mirror are limited to proper placement of the source, and optical aberration is expected outside the geometry demands specific to the mirror in use. For example, in astronomy, the ‘coma’ aberration has long been associated with telescopes when wavefronts of incoming light are not normal to the optical axis. + +To simplify the problem, the following assumptions were made about the IFF system, which was modelled with a 2D ray tracer: + +1. The TE antenna was modelled as a point light source with uniform illumination in the hemisphere facing the mirror, and no illumination facing the source. +2. Light not incident on the mirror was modelled as being perfectly absorbed by the background +3. Edge effects of the mirror were not considered +4. The primary focal length was chosen to be 0.65m, for an effective focal length with the offset mirror of $\sim 0.7$ m. The mirror offset was such that the mirror extended from $y = 0.2$ m to $y = 0.5$ m off the optical axis. +5. QZ plane was placed orthogonal to the optical axis 1.5 m away from the point where the axis intersects the parabola. + +6. Source-to-source interaction, in case of multiple sources, are neglected +7. EM field perturbation due to presence of positioner or DUT fixturing is neglected by virtue of choosing an optic method +8. Light source locations considered (d,h defined in figure 5.3.2.2.1-1): + +Note that assumption #1 is not valid for typical horn antennae, but the uniform illumination assumption serves as a good reference point for studying power variation across the QZ when the source is moved off-focus. + +**Table 5.3.2.2.1-1: Source locations** + +| Location id | d (m) | h (m) | +|-------------|-------|-------| +| 1 (focus) | 0 | 0 | +| 2 | 0 | 0.05 | +| 3 | 0 | 0.10 | +| 4 | -0.05 | 0.10 | +| 5 | +0.05 | 0.10 | + +Figures 5.3.2.2.1-1 shows the position of the mirror relative to the sources, as well as the illumination levels at the QZ (sub figure 1b). The blue curve in the sub-figure 1b indicates 2 things about a source at the focus (location1). The first observation is that the nominal QZ is located between $y = 0.2$ and $y=0.5$ , which coincides with the mirror extents in the y-dimension. This detail is expected. The second observation is that an isotropic source gets transformed to a non-uniform illumination at the QZ. + +![Figure 5.3.2.2.1-1: a: Mirror and source locations; b : Source to QZ power density distortion. Sub-figure (a) is a plot titled 'Mirror and source locations' showing the mirror's profile as a blue curve from (0, 0.2) to (0.1, 0.5). Source locations 1-5 are marked with colored stars at (d, h) coordinates: (0,0), (0, 0.05), (0, 0.1), (-0.05, 0.1), and (0.05, 0.1). Sub-figure (b) is a plot titled '% Deviation from uniform illumination @ QZ' showing the percentage deviation across the QZ coordinate (0.2 to 0.5) for each source location. The curves show that as the source moves away from the focus, the illumination becomes more non-uniform across the QZ.](e487aa3d0a4f904f2d04785ee0c6c474_img.jpg) + +Figure 5.3.2.2.1-1: a: Mirror and source locations; b : Source to QZ power density distortion. Sub-figure (a) is a plot titled 'Mirror and source locations' showing the mirror's profile as a blue curve from (0, 0.2) to (0.1, 0.5). Source locations 1-5 are marked with colored stars at (d, h) coordinates: (0,0), (0, 0.05), (0, 0.1), (-0.05, 0.1), and (0.05, 0.1). Sub-figure (b) is a plot titled '% Deviation from uniform illumination @ QZ' showing the percentage deviation across the QZ coordinate (0.2 to 0.5) for each source location. The curves show that as the source moves away from the focus, the illumination becomes more non-uniform across the QZ. + +**Figure 5.3.2.2.1-1: a: Mirror and source locations; b : Source to QZ power density distortion** + +Furthermore, the illumination intensity curves corresponding to other source locations inform that the collimated beam moves progressively off the QZ as the source is moved away from focus. In the example locations studied, the beam develops a down tilt, but an up tilt is also possible if the source is moved to a location, say, below and to the left of the focus in figure 1a. + +In figure 5.3.2.2.1-2, it is observed that the wavefront also starts to deviate from being purely orthogonal to the optical axis. The wavefront shape is consistent with the ‘beam tilt’ observation made earlier. + +![Figure 5.3.2.2.1-2: Wavefront orientation at QZ due to off-focus source. The figure contains two plots. The left plot, titled 'Mirror and source locations', shows a coordinate system with 'h' on the x-axis (0 to 0.7) and 'd' on the y-axis (0 to 0.6). A blue curve represents the mirror surface, starting at (0, 0.2) and ending at (0.1, 0.5). A vertical line at h ≈ 0.6 represents the focus. Five source locations are marked: location 1 (blue circle) at (0.6, 0), location 2 (orange star) at (0.6, 0.05), location 3 (yellow star) at (0.6, 0.1), location 4 (purple star) at (0.6, 0.15), and location 5 (green star) at (0.6, 0.2). The right plot, titled 'Wavefront orientation', shows the same five locations on a coordinate system with x-axis values from 1.4 to 1.6 and y-axis values from 0 to 0.6. Lines representing the wavefront orientation for each location are shown, all originating from a point on the x-axis around 1.48.](bc9fe6d1f3411f724ddf3b8c11a37f7e_img.jpg) + +Figure 5.3.2.2.1-2: Wavefront orientation at QZ due to off-focus source. The figure contains two plots. The left plot, titled 'Mirror and source locations', shows a coordinate system with 'h' on the x-axis (0 to 0.7) and 'd' on the y-axis (0 to 0.6). A blue curve represents the mirror surface, starting at (0, 0.2) and ending at (0.1, 0.5). A vertical line at h ≈ 0.6 represents the focus. Five source locations are marked: location 1 (blue circle) at (0.6, 0), location 2 (orange star) at (0.6, 0.05), location 3 (yellow star) at (0.6, 0.1), location 4 (purple star) at (0.6, 0.15), and location 5 (green star) at (0.6, 0.2). The right plot, titled 'Wavefront orientation', shows the same five locations on a coordinate system with x-axis values from 1.4 to 1.6 and y-axis values from 0 to 0.6. Lines representing the wavefront orientation for each location are shown, all originating from a point on the x-axis around 1.48. + +**Figure 5.3.2.2.1-2: Wavefront orientation at QZ due to off-focus source** + +For a UE's perspective on off-focus sources, candidate source locations were characterized by their angular locations relative to mirror normal. Note that the focus is off the mirror normal due to 'offset mirror' geometry, so it has a non-zero value. In the example studied, the focus is 15.4 degrees below mirror normal, and the other off-focus source locations studied all have lower angular offsets than the focus. In figure 5.3.2.2.1-3 we show that the rate of increase beam tilt and the rate of increase in angular offset of the source are very similar, i.e. close to 1:1 for the geometry studied. + +![Figure 5.3.2.2.1-3: Beam tilt due to off-focus source. The plot shows 'Beam tilt (deg) at QZ' on the y-axis (from -10 to 2) versus 'Source location relative to mirror normal (deg)' on the x-axis (from -16 to -6). A dashed grey line represents the trend, starting at the 'focus' point (approx. -15.4, 0) and passing through points for locations 1 to 5. The data points are: location 1 (blue cross) at (-15.4, 0), location 2 (orange cross) at (-12, -4), location 3 (yellow cross) at (-10, -6), location 4 (purple cross) at (-8, -8), and location 5 (green cross) at (-6, -10).](e7d6aacb9818a209033d6d8d7b99c8d9_img.jpg) + +Figure 5.3.2.2.1-3: Beam tilt due to off-focus source. The plot shows 'Beam tilt (deg) at QZ' on the y-axis (from -10 to 2) versus 'Source location relative to mirror normal (deg)' on the x-axis (from -16 to -6). A dashed grey line represents the trend, starting at the 'focus' point (approx. -15.4, 0) and passing through points for locations 1 to 5. The data points are: location 1 (blue cross) at (-15.4, 0), location 2 (orange cross) at (-12, -4), location 3 (yellow cross) at (-10, -6), location 4 (purple cross) at (-8, -8), and location 5 (green cross) at (-6, -10). + +**Figure 5.3.2.2.1-3: Beam tilt due to off-focus source** + +Recall that the nominal QZ location is the illuminated spot in the plane of the QZ when the source is located at the focus of the mirror. In case of our example, the nominal QZ extends from $(x=1.5, y=0.2)$ to $(x=1.5, y=0.5)$ . Beam tilt causes the illuminated spot in the plane of the QZ to move off the nominal QZ location. When multiple sources illuminate the mirror, the effective QZ size reduces to the common area across the beams from all sources. Beam tilt consequently has the effect of reducing the effective QZ size. See figure 5.3.2.2.1-4. The reduction in size is a function of both, the angular offset between source and focus, and the distance of the QZ from the mirror. + +![Figure 5.3.2.2.1-4: Beam tilt causes QZ size reduction. A 2D plot showing beam shapes for various source locations. The x-axis is labeled 'focus' from 0 to 1. The y-axis ranges from 0 to 0.8. A blue line indicates the 'Nominal QZ location'. Multiple orange and yellow shaded regions represent 'QZ locations for various source locations'. A pink double-headed arrow on the right indicates the 'Common QZ' area.](bd361bbf5003c5df0416591de03a4522_img.jpg) + +The figure is a plot titled 'Beam tilt'. The horizontal axis is labeled 'focus' and ranges from 0 to 1. The vertical axis ranges from 0 to 0.8. A blue line labeled 'Nominal QZ location' points to a specific region. Multiple orange and yellow shaded regions represent 'QZ locations for various source locations'. A pink double-headed arrow on the right side of the plot indicates the 'Common QZ' area, which is the intersection of all the individual QZ locations. + +Figure 5.3.2.2.1-4: Beam tilt causes QZ size reduction. A 2D plot showing beam shapes for various source locations. The x-axis is labeled 'focus' from 0 to 1. The y-axis ranges from 0 to 0.8. A blue line indicates the 'Nominal QZ location'. Multiple orange and yellow shaded regions represent 'QZ locations for various source locations'. A pink double-headed arrow on the right indicates the 'Common QZ' area. + +**Figure 5.3.2.2.1-4: Beam tilt causes QZ size reduction** + +Now, different UE power classes have different beam shapes, and different beam packing densities. For power class 1, 3dB beam widths are expected to be between 5 and 10 degrees as an extreme example. A beam tilt in the range of a few degrees could cause a PC1 UE to select a different beam for an off-focus source, relative to a source at the focus. + +UE size also limits how close to the mirror the QZ plane can be moved. The radiating face of PC1 device can measure in the 10s of cm in each dimension, which would force the QZ far away from the mirror. This restriction would, in turn, cause much greater reduction in QZ size for a given beam tilt angle, when using multiple sources. These problems would be less serious for PC3 devices. + +In a case a test antenna is located simply off the position from a focal point (normally at a position of a main test antenna) in the IFF test system, a centre of a beam from the offset feed antenna would shift depending on a distance of focal length ( $f$ ), a distance between the reflector and a centre of a quiet zone ( $r$ ), and a distance of the antenna offset ( $\delta$ ). Figure 5.3.2.2.1-5 depicts the relationship of this shift ( $\delta'$ ). + +![Figure 5.3.2.2.1-5: Offset of antenna beam peak from centre of QZ (Top view of IFF test system). A schematic diagram showing a reflector, focal point, offset antenna, and the resulting beam shift.](2957154f4dc666a6cafb7b4d2d882910_img.jpg) + +The diagram shows a top view of an IFF test system. A curved 'Reflector' is on the left. A 'Focal point (= Main antenna position)' is marked with a black dot. An 'Offset antenna' is marked with a green square, positioned at a distance $\delta$ below the focal point. A red line represents the beam path from the offset antenna, reflecting off the reflector and converging towards the focal point. The distance from the reflector to the focal point is labeled $f$ . The distance from the reflector to the 'Centre of QZ' is labeled $r$ . The 'Centre of beam from the offset antenna' is marked with a blue dot, shifted vertically from the focal point by a distance $\delta'$ . The angle between the beam path and the horizontal axis is labeled $\theta$ . A coordinate system is shown in the top right corner with the z-axis pointing left and the x-axis pointing down. + +Figure 5.3.2.2.1-5: Offset of antenna beam peak from centre of QZ (Top view of IFF test system). A schematic diagram showing a reflector, focal point, offset antenna, and the resulting beam shift. + +**Figure 5.3.2.2.1-5: Offset of antenna beam peak from centre of QZ (Top view of IFF test system)** + +Here the shift ( $\delta'$ ) can be calculated geometrically by the following equation, and it may cause an increase of QoQZ measurement uncertainty in a 30 cm quiet zone. + +From our experience to date, an electric field intensity in a quiet zone when a feed antenna is located near a focal point is decided by two factors, an antenna pattern of the feed antenna for a test equipment and a shape of the reflector. Especially the antenna pattern can be assumed as the main factor to decide this characteristic, which is directly connected also to the QoQZ. + +Based on this observation an estimation was made with an impact of the offset antenna to QoQZ from an experimental data which was obtained by measuring the electric field intensity of a feed antenna via a reflector. Figure 5.3.2.2.1-6 shows one of the experimental data obtained by scanning the field intensity in a range of +/- 200 mm from a centre of the quiet zone. Here a 40.8 GHz vertical polarization beam was scanned along with theta (x) direction. + +![Figure 5.3.2.2.1-6: Electric field intensity of feed antenna scanned along with theta direction (40.8 GHz, V-pol). The graph shows Amplitude [dB] on the y-axis (from -2 to 0) versus X [mm] @ Y=0 mm on the x-axis (from -200 to 200). A noisy blue line represents the experimental data, and a smooth black curve represents a quadratic fit. The equation for the fit is y = 3E-05x^2 + 0.0003x - 0.3871.](c8d2bc5b813f5d46408a32185a56a7b1_img.jpg) + +Figure 5.3.2.2.1-6: Electric field intensity of feed antenna scanned along with theta direction (40.8 GHz, V-pol). The graph shows Amplitude [dB] on the y-axis (from -2 to 0) versus X [mm] @ Y=0 mm on the x-axis (from -200 to 200). A noisy blue line represents the experimental data, and a smooth black curve represents a quadratic fit. The equation for the fit is y = 3E-05x^2 + 0.0003x - 0.3871. + +**Figure 5.3.2.2.1-6: Electric field intensity of feed antenna scanned along with theta direction (40.8 GHz, V-pol)** + +Table 5.3.2.2.1-2 and Figure 5.3.2.2.1-7 show the estimation of difference between the QoQZ of main antenna and of the offset antenna. Note that these values are specific to the feed antenna (amplitude taper) in this experiment and thus they may vary depending on an antenna pattern used by each test equipment vendor. + +**Table 5.3.2.2.1-2: Estimation of QoQZ difference between main and offset antenna** + +| $\delta$ [mm] | Estimation of QoQZ difference (EIRP) [dB] | | | +|---------------|-------------------------------------------|------------|----------| +| | 23.45 GHz | 32.125 GHz | 40.8 GHz | +| 0 | 0.00 | 0.00 | 0.00 | +| 15 | 0.02 | 0.02 | 0.01 | +| 30 | 0.04 | 0.05 | 0.03 | +| 45 | 0.08 | 0.08 | 0.06 | +| 60 | 0.11 | 0.11 | 0.09 | +| 75 | 0.14 | 0.15 | 0.11 | + +![Figure 5.3.2.2.1-7: Estimation of QoQZ difference between main and offset antenna. The graph shows QoQZ difference [dB] on the y-axis (from 0.00 to 0.20) versus delta [mm] on the x-axis (from 0 to 80). Three data series are plotted: 23.45GHz (blue line with circles), 32.125GHz (orange line with circles), and 40.8GHz (grey line with circles). All series show a linear increase in QoQZ difference as delta increases, with the 32.125GHz series having the steepest slope.](5ad593a688ae2c96712847c300171b5d_img.jpg) + +Figure 5.3.2.2.1-7: Estimation of QoQZ difference between main and offset antenna. The graph shows QoQZ difference [dB] on the y-axis (from 0.00 to 0.20) versus delta [mm] on the x-axis (from 0 to 80). Three data series are plotted: 23.45GHz (blue line with circles), 32.125GHz (orange line with circles), and 40.8GHz (grey line with circles). All series show a linear increase in QoQZ difference as delta increases, with the 32.125GHz series having the steepest slope. + +**Figure 5.3.2.2.1-7: Plot of QoQZ difference** + +Though these differences may vary depending on an antenna pattern (amplitude taper) of a feed antenna, as can be seen from above, there is a chance that the difference of QoQZ due to the offset antenna can be limited within an acceptable level by optimizing an arrangement of antennas. + +As described above, these QoQZ differences are estimated based on the antenna configuration with which the offset antenna is simply off the position from a focal point. And there is a way to mitigate the impact of the offset antenna to the actual QoQZ. + +One of major factors to decide QoQZ is the electric field intensity in the quiet zone. Figure 5.3.2.2.1-8 depicts a 2D image of the electric field intensity (amplitude taper) in the quiet zone when the offset antenna is used. As shown in the figure, due to the shift of beam centre from the main antenna, distribution of the field intensity becomes asymmetric in the quiet zone and thus it causes the increase of the QoQZ MU value. However it is possible to shift the beam peak position by tilting the offset antenna and make the distribution of the field intensity close to symmetric in the quiet zone like the one from the main antenna, allowing us to mitigate the impact of beam centre shift to the QoQZ value. Figure 5.3.2.2.1-9 depicts the image of the improvement with the offset antenna placement. At the same time, there might be diffraction and/or scattering effects created by the reflector's paraboloid edges and the size of the paraboloid that impact the QoQZ characteristics. Thus, there should be some limitations with antenna offset ranges and angles to tilt the offset antenna that depend on a relationship between reflector size, measurement antenna offset and range length. All these factors should be considered during the design of the test system. + +![Figure 5.3.2.2.1-8: Top view diagram of an antenna system with an offset antenna. A parabolic reflector is on the left. A focal point is marked on the central axis. An offset antenna is positioned below the focal point by a distance δ. A beam is shown originating from the offset antenna, with its peak (Beam peak) shifted upwards in the quiet zone (QZ). The amplitude taper is indicated by a red curve. A coordinate system (z, x) is shown in the top right corner.](e2a6d00ef953ffef831511e534394a27_img.jpg) + +Figure 5.3.2.2.1-8: Top view diagram of an antenna system with an offset antenna. A parabolic reflector is on the left. A focal point is marked on the central axis. An offset antenna is positioned below the focal point by a distance δ. A beam is shown originating from the offset antenna, with its peak (Beam peak) shifted upwards in the quiet zone (QZ). The amplitude taper is indicated by a red curve. A coordinate system (z, x) is shown in the top right corner. + +**Figure 5.3.2.2.1-8: 2D image of the electric field intensity (amplitude taper) in the quiet zone from an offset antenna**![Figure 5.3.2.2.1-9: Top view diagram similar to Figure 5.3.2.2.1-8, but the offset antenna is tilted. The beam peak (Beam peak) is now more centrally located within the quiet zone (QZ), showing improved symmetry. The amplitude taper curve is also shown. The coordinate system (z, x) remains the same.](53a3d214d0850fac26a99299ef3cb43e_img.jpg) + +Figure 5.3.2.2.1-9: Top view diagram similar to Figure 5.3.2.2.1-8, but the offset antenna is tilted. The beam peak (Beam peak) is now more centrally located within the quiet zone (QZ), showing improved symmetry. The amplitude taper curve is also shown. The coordinate system (z, x) remains the same. + +**Figure 5.3.2.2.1-9: 2D image of the electric field intensity in the quiet zone from a tilted offset antenna** + +There is another way of recovering desired QZ illumination. In Figure 5.3.2.2.1-4, it is shown that beam tilt causes reduction in size of QZ that is common to all source locations. This mechanism is intuitive and can be pre-compensated during design of the test system. + +The matter of QZ quality however involves more complexity. As a first approximation, QZ quality can be quantified by the illumination distribution from a hypothetical constant density source illuminating the mirror. Here it becomes evident that angular offset of the antenna alone is not enough to determine illumination distribution. See figure 5.3.2.2.1-10. Locations 2, 3 and 4 all have approximately the same angular offset ( $< 0.5$ degree difference), but their QZ illumination can be made better or worse than that of the on-focus source by adjusting mirror to source distance. In the graphic example, the source location closest to the mirror has the least variation QZ illumination. + +It is therefore possible to recover desired QZ illumination by adjusting the source location distance from mirror in concert with angular offset. A discussion regarding whether the different QoQZ MU needs to be applied compared to the single carrier case can be left to RAN5. + +As shown later in the discussion of wavefront shapes however (see sub-clause 5.3.2.2.3), there are other constraints governing offset source to mirror distance. + +![Figure 5.3.2.2.1-10: Two plots showing mirror and source locations and their illumination distribution at the QZ. Plot (a) shows the mirror and source locations for four different source locations. Plot (b) shows the percentage deviation from uniform illumination at the QZ for the same four source locations.](da82c28f91abb7e03beec3535b711ab7_img.jpg) + +Figure 5.3.2.2.1-10 consists of two plots. Plot (a), titled 'Mirror and source locations', shows the QZ coordinate (y-axis, 0 to 0.6) versus the percentage (x-axis, 0 to 0.7). It displays four sets of lines representing different source locations: location 1 (blue), location 2 (orange), location 3 (yellow), and location 4 (purple). The lines show a dense, fan-like distribution of points. Plot (b), titled '% Deviation from uniform illumination @ QZ', shows the QZ coordinate (y-axis, 0 to 0.6) versus the percentage (x-axis, -30 to 30). It displays four sets of lines representing the same source locations. The lines show a more sparse, linear-like distribution of points, indicating the percentage deviation from uniform illumination. + +Figure 5.3.2.2.1-10: Two plots showing mirror and source locations and their illumination distribution at the QZ. Plot (a) shows the mirror and source locations for four different source locations. Plot (b) shows the percentage deviation from uniform illumination at the QZ for the same four source locations. + +**Figure 5.3.2.2.1-10: a: Mirror and source locations. Locations 2, 3 and 4 have similar offset; b: Locations 2, 3 and 4 cause different illumination distribution at QZ** + +##### 5.3.2.2.2 Rx beam profiles with an independent beam management (IBM) UE + +In this sub-clause, an explanation is shown that it is possible to measure the appropriate EIS spherical coverage beam profiles by the test system which equips the non co-located (offset) antenna even with the inter-band 2 DL CA cases as long as the UE is supporting the independent beam management (IBM). + +First we consider a single carrier Rx spherical coverage beam profile which we can obtain by two kinds of antennae. If we compare Rx beam profiles of two different cases, one which has been measured by main antenna of the OTA test system, or the other with which the DL beam frequency is same but has been measured from the offset antenna, both beam profiles can be assumed identical as far as following conditions are satisfied. + +- Two measurement antennae (main and offset) are arranged along with the $\theta$ rotation of the positioner +- DL power of the offset antenna is calibrated and capable of transmitting same power level with the main measurement antenna. + +For the rotation angles of positioner, refer to Annex D.2.6 in TS 38.810 [3]. + +Figure 5.3.2.2.2-1 depicts the image of two beam profiles obtained by different antennae. Note that the profiles are obtained one by one since the link has to be maintained with either of antennae during the measurement. + +![Figure 5.3.2.2.2-1: 2D image of beam profile obtained by two antennae. The diagram shows a smartphone in the center. Two beam profiles are overlaid: a blue curve labeled 'Beam profile obtained by main antenna' and a red curve labeled 'Beam profile obtained by offset antenna. Rotated 2.5 to 7 degrees from the one obtained by the main antenna.' The main antenna is indicated by a label and a small antenna icon, and the offset antenna is indicated by a label and a small antenna icon. Arrows point from the text labels to the corresponding beam profiles.](e84de38c2eac283d770e2c8acdf64308_img.jpg) + +Figure 5.3.2.2.2-1: 2D image of beam profile obtained by two antennae. The diagram shows a smartphone in the center. Two beam profiles are overlaid: a blue curve labeled 'Beam profile obtained by main antenna' and a red curve labeled 'Beam profile obtained by offset antenna. Rotated 2.5 to 7 degrees from the one obtained by the main antenna.' The main antenna is indicated by a label and a small antenna icon, and the offset antenna is indicated by a label and a small antenna icon. Arrows point from the text labels to the corresponding beam profiles. + +**Figure 5.3.2.2.2-1: 2D image of beam profile obtained by two antennae** + +If we compare the two measurements, a difference between them are just a point of sight from the UE, in other words a boresight of UE is slightly rotated depending on the arrangement of measured antennae. + +There is an angular offset between the two measurement antennae such as 2.5 to 7 degrees. Therefore to compare the two obtained beam profiles, rotation of either one of profiles in accordance with the actual antenna alignment is necessary. Also the adjustment of the start/ stop coordinates to measure is necessary with a case of the offset antenna. + +Now we consider beam profiles which are obtained by the test system that transmits two DL signals from single antenna (system A), and the system which has one additional offset antenna to transmit two DL signals - one DL from the main antenna and the other from the offset antenna (system B). For inter-band 2 DL CA case for example with band n260 and n261, suppose only system B transmits n261 from the offset antenna, properties of each beam profile are summarized in Table 5.3.2.2.2-1. Note that 2 measurement antennae of system B are assumed to be arranged along with the $\theta$ rotation of the positioner again just as mentioned above. + +**Table 5.3.2.2.2-1: Beam profiles obtained by system A and system B in a case with IBM antennae in a UE** + +| | System A (2 DL from main antenna, 1 AoA) | System B (2 DL from slightly offset 2 AoA antennae) | +|----------------------|------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| Beam profile of n260 | Obtained by main antenna | Obtained by main antenna. Thus completely identical with system A. | +| Beam profile of n261 | Obtained by main antenna | Obtained by the offset antenna. The shape of profile should be same but rotated in accordance with the angular offset between two test antennae. | + +Taking all explanations above into consideration, system B requires a post processing of the obtained data in accordance with the slightly rotated coordinate system. But the obtained beam profiles can be assumed as identical with ones obtained by system A as far as the UE is supporting the IBM. i.e. There is a way to make IBM UEs to choose same relative beam direction and conduct spherical coverage tests properly like a single test antenna system. + +Choice of the beam by UEs with common beam management (CBM) is studied at the next sub-clause. + +##### 5.3.2.2.3 Propensity to trigger incorrect beam in CBM UE + +The primary mechanism that can mislead CBM UEs is band-specific beam tilt in the test setup. As shown in sub-clause 5.3.2.2.1, beam tilt at the QZ is roughly 1:1 with source angular offset. In the spherical coverage space of a UE, beam tilt becomes a significant problem for beam management at beam boundaries. The impact to measured performance is directly related to probability of finding a beam boundary during 3D search. Beam tilt therefore penalizes UEs with dense beam packing (i.e more beam boundaries). + +Dense beam packing is often associated with UEs with good spherical coverage. It can be reasonably argued that the impact of beam tilt in this context is worse for UEs with better spherical coverage. This problem does not have a systematic effect across all UE designs and therefore difficult to overcome. + +Another important characteristic of a far field scenario is a nearly planar wavefront. Figures 5.3.2.2.3-1 shows the deviation from planar wavefront at the QZ when the source is moved off-focus. As before, in the figures below, locations 2,3 and 4 have similar angular offset, but differ in mirror to source distance. The figures show that there is an optimal distance from the mirror for any angular offset of the source, for the wavefront to appear planar at the QZ. + +![Figure 5.3.2.2.3-1: Wavefront orientation at QZ due to off-focus source. The figure contains two line graphs. The left graph is titled 'Wavefront Plane-ness, 24GHz' and the right graph is titled 'Wavefront Plane-ness, 48GHz'. Both graphs plot 'radians' on the x-axis (from -6 to 3) against a y-axis (from 0.1 to 0.5). Four curves are shown in each graph, labeled 'location 1' (blue), 'location 2' (orange), 'location 3' (yellow), and 'location 4' (purple). In both graphs, the curves for location 1 and 3 are nearly vertical and close to each other, indicating a planar wavefront. The curves for location 2 and 4 are more curved and spread out, indicating a non-planar wavefront. The 48GHz graph shows more pronounced curvature for the non-planar locations compared to the 24GHz graph.](19a878abbd7068d98e7d54341c8d897c_img.jpg) + +Figure 5.3.2.2.3-1: Wavefront orientation at QZ due to off-focus source. The figure contains two line graphs. The left graph is titled 'Wavefront Plane-ness, 24GHz' and the right graph is titled 'Wavefront Plane-ness, 48GHz'. Both graphs plot 'radians' on the x-axis (from -6 to 3) against a y-axis (from 0.1 to 0.5). Four curves are shown in each graph, labeled 'location 1' (blue), 'location 2' (orange), 'location 3' (yellow), and 'location 4' (purple). In both graphs, the curves for location 1 and 3 are nearly vertical and close to each other, indicating a planar wavefront. The curves for location 2 and 4 are more curved and spread out, indicating a non-planar wavefront. The 48GHz graph shows more pronounced curvature for the non-planar locations compared to the 24GHz graph. + +**Figure 5.3.2.2.3-1: Wavefront orientation at QZ due to off-focus source** + +Also note that positioning an offset source at the optimal distance may not result in optimal illumination density of the QZ. From a beam management standpoint however, it is more important to ensure quality of the wavefront given that the deviation in illumination density seems minor. (Explanation: Position 3 is close to the optimal point, as witnessed by its nearly flat wavefront in figures 5.3.2.2.3-1. In figure 5.3.2.2.3-1, illumination density curves of location 3 and location 1, the focus or 'ideal location', track closely) + +The figures 5.3.2.2.3-1 also reasonably predict that the non-linear phase variation varies with frequency. Ergo, it is advantageous to reserve the ideal location (focus) for the antenna serving the highest frequencies and use offset locations for antennae serving lower frequencies. + +##### 5.3.2.2.4 Spherical coverage measurement simulation with common beam management (CBM) UE + +For inter-band CA requirements within 28 GHz range (L + L) or 39 GHz range (H + H) which has a possibility of transmissions by CBM, a simulation was made on the influence of the offset antenna measurement for inter-band CA case with CBM UE. From this simulation we tried to clarify a difference with the measurement of 2 DL by 1 AoA at a frequency range from 37 GHz and 43.5 GHz. + +###### Assumption of the UE antenna inter-element distance + +It is difficult for us to expect an actual inter-element distance (D) of an antenna in the current UE since it is implementation dependent. But as a starting point, during this simulation we put an assumption that an optimization of the inter-element distance is made at the centre frequency between the lower edge of band n258 (24.25 GHz) and higher edge of n259 (43.5 GHz), i.e. 33.875 GHz where $D/\lambda$ becomes 0.5. + +**Table 5.3.2.2.4-1: Optimized frequency and corresponding ratio (D/l) for simulation frequencies** + +| Optimized frequency ( $D/\lambda = 0.5$ ) | Frequency 1 (f1) for simulation | Frequency 2 (f2) for simulation | +|-------------------------------------------|---------------------------------|---------------------------------| +| 33.875 GHz (0.5) | 37.0 GHz (0.55) | 43.5 GHz (0.64) | + +###### Assumption of phase shifter in a UE + +For a beam forming method of the UE, following two methods were applied in the simulation. + +- i) A fixed phase shift to the antenna regardless with the carrier frequencies, which we assume this method is causing the beam squint. +- ii) A different phase shift which is proportional to the carrier frequencies so called true time delay (TTD). + +###### Simulation procedures for spherical coverage + +The simulation of the spherical coverage measurement was carried out by the following steps. + +Step 1) Decide a code book to obtain the maximum sensitivity at frequency 1 (37.0 GHz) with a measurement grid placed randomly against a DUT. + +Step 2) Keep the identified code book at step 1) and calculate gain profiles at frequency 2 (43.5 GHz). Then compare the following two cases. + +Case 1) Gain profile at frequency 2 measured by the main antenna + +- Only the difference of the ratio ( $D/\lambda$ ) can be monitored as the difference from the frequency 1. This result can be assumed as a baseline when comparing the influence of the offset antenna measurement. + +Case 2) Gain profile at frequency 2 measured by the offset antenna + +- In addition to the difference of the ratio ( $D/\lambda$ ), influence of the offset antenna is included in this result. (e.g. influence to the measurement grid due to the offset of the antenna.) + +###### Simulation parameter + +Simulation parameters are summarized in Table 5.3.2.2.4-2. + +**Table 5.3.2.2.4-2: Simulation parameter for spherical coverage gain profile** + +| Item | Parameter | +|-------------------|------------------------------------------------------------------| +| Grid | Constant Density 200 pt, 1000 random orientations against a DUT. | +| Antenna offset | $\theta = 4.0$ degrees | +| Array antenna | 1 x 4. Inter-element distance is optimized at 33.875 GHz. | +| Phase shifter | Non TTD (Constant Phase), TTD (True Time Delay) | +| Carrier frequency | 37.0 GHz, 43.5 GHz | + +###### Spherical coverage simulation result + +Simulation results of the spherical coverage are summarized in Table 5.3.2.2.4-3 and 5.3.2.2.4-4. + +**Table 5.3.2.2.4-3: Simulation result of spherical coverage – Mean 50%-ile error (against 1deg uniform grid as a reference)** + +| D/ $\lambda$<br>(Test frequency) | Non-TTD | | TTD | | +|----------------------------------|--------------|----------------|-----------------|----------------| +| | Main antenna | Offset antenna | Main antenna | Offset antenna | +| 0.55 (37.0 GHz) | 0.024 | - | Same as Non-TTD | - | +| 0.64 (43.5 GHz) | 0.016 | 0.101 | 0.019 | 0.135 | + +**Table 5.3.2.2.4-4: Simulation result of spherical coverage – Standard deviation of 50%-ile value** + +| D/ $\lambda$<br>(Test frequency) | Non-TTD | | TTD | | +|----------------------------------|--------------|----------------|-----------------|----------------| +| | Main antenna | Offset antenna | Main antenna | Offset antenna | +| 0.55 (37.0 GHz) | 0.059 | - | Same as Non-TTD | - | +| 0.64 (43.5 GHz) | 0.096 | 0.102 | 0.111 | 0.168 | + +Comparing the results between the main antenna and offset antenna, we observed that the mean error by measuring from the offset antenna increases slightly with both non-TTD and TTD type phase shifter (0.085 dB with non-TTD and 0.116 dB with TTD at 43.5 GHz.). This means that the total measurement uncertainty by measuring from offset antenna will increase approximately 0.1 dB as the systematic uncertainty. + +For the standard deviation, only the result with TTD phase shifter showed the slight increase of measurement uncertainty (0.057 at 43.5 GHz.). However this increase of random uncertainty should be a negligible level compared to the other uncertainty contribution. + +Therefore for both mean error (systematic error) and standard deviation (random error) with offset antenna, these values are within the acceptable level because the simulation assumptions in this paper are chosen as one of the severest conditions from the viewpoint of the frequency point to optimize inter-element distance, test frequencies, basic frequency point of phase shift, etc. And since the optimization of the inter-element distance was assumed at 33.875 GHz, if this optimization is made at a higher frequency such as at the middle of 37 GHz and 43.5 GHz, the observed uncertainty should be decreased. + +Considering all the observations above, we assume that the FR2 OTA test system with the offset test antenna has a feasibility of measuring inter-band DL CA test cases for both CBM and IBM UEs under some limitations. + +For cases with UEs which supports wider frequencies (such as n262 in addition) or higher power such as PC1 need a further study. + +#### 5.3.2.3 Summary on applicability of offset antenna test system + +Taking into consideration of study results in sub-clause 5.3.2.1 and 5.3.2.2, an applicability of the offset antenna test system to the spherical coverage test with an inter-band CA UE is summarized as follows. + +IBM UE: + +On a test for UEs supporting inter-band CA with IBM, there is a way to make IBM UEs to choose same relative beam direction and conduct spherical coverage tests properly like a single test antenna system. It is recommended that a design of the test system is optimized to mitigate an impact of the offset antenna to the QoQZ measurement uncertainty, including the diffraction and/or scattering effects created by the reflector's paraboloid edges and the size of the paraboloid. + +CBM UE: + +On a test for UEs supporting inter-band CA with CBM, there might be a limitation with the feasibility by the offset antenna test system. But this relates also to the on-going WI discussion on the necessity of spherical coverage requirements with CBM UEs supporting a same band group e.g. 28 GHz + 28 GHz. + +#### 5.3.2.4 Points to design the FR2 OTA test system with offset test antennae + +To design FR2 OTA IFF test system for inter-band CA UE, following points were analyzed in the previous sub-clauses with regards to an impact of off-focus test antennae. + +- Distance (and angular offset) between the main antenna and the offset antenna +- Arrangement of the offset antenna +- Angle to fix (tilt) the offset antenna +- Distance between the offset antenna and a reflector +- Arrangement of antennae associated with their frequency coverage + +We pick out and iterate examples from the previous analyses which need to be considered during a design of the test system to minimize impacts from the offset antenna. We also consider further with their feasibility from some other aspects e.g. another affecting factor, actual system assembly procedures and test operations. + +##### Distance (and angular offset) between main antenna and offset antenna + +Based on the assumption that a range length in an IFF chamber is from 800 mm to 1200 mm, antenna offset from 50 mm to 100 mm were studied. These offsets are equivalent to approximately 2.5 to 7 degrees as an angular offset. And due to a shift of focal point from a centre of the quiet zone, approximately 0.15 dB degradation of the quality of quiet zone MU is estimated at the frequency range from 23.45 to 40.8 GHz. Note the estimation may vary depending on components and system designs in each vendor. + +From the previous studies, it is obvious that the impact is proportional to the distance between antennae. From this point it is preferable that each antenna is arranged as close as possible. However another effect of mutual coupling arises if the gap becomes too close like that of one wavelength (i.e. approximately 10 mm around 30 GHz.). Though we can assume that the effect can be included while evaluating the quality of quiet zone, at the same time when we think of an assembly of cables to each antenna, some clearances must be ensured and thus a gap around 40 to 50 mm between antennae is considered possible closest distance. + +##### **Arrangement of the offset antenna** + +On condition that a DUT is supporting IBM, we have a chance to carry out the inter-band CA test case with the offset antenna test system equivalent to the system only with the main antenna. To obtain identical beam profiles from both of main and offset antenna, following conditions need to be satisfied: + +- Two measurement antennae (main and offset) are arranged along with the $\theta$ rotation of the positioner +- DL power of the offset antenna is calibrated and capable of transmitting same power level with the main measurement antenna. + +Since there is an angular offset between the two measurement antennae such as 2.5 to 7 degrees, to compare the two obtained beam profiles, a post processing of obtained data is necessary with either one of profiles in accordance with the actual antenna alignment. Also the adjustment of the start/ stop coordinates to measure is necessary with the offset antenna. + +##### **Angle to fix (tilt) the offset antenna** + +It is recommended that also an angle to fix (tilt) the offset antenna is considered while designing the test system. It is possible to shift the electric field intensity by tilting the offset antenna (e.g. 0.5 to 0.7 degree) and make the distribution of the field intensity, in other words an amplitude taper, close to symmetric in the quiet zone like the one from the main antenna. However since the applicable tilt angles are closely related with a size of reflector and the range length, there should be some limitations and care must be taken to avoid diffraction and/or scattering effects created by the reflector's paraboloid edges. + +##### **Distance between the offset antenna and a reflector** + +It is possible to optimize the shape of wavefront and illumination at the centre of the quiet zone by adjusting a distance between the offset antenna and a reflector. However since the QZ illumination also depends on the frequency of beam, and considering the current frequency range of mmWave region, which is wide spread from 24 GHz to 52 GHz, it is not practical to change the distance for each antenna one by one. Also when we consider a design that the placement of the offset antenna is above the main antenna, there might be another factor to increase the measurement uncertainty since coordinates of the measurement grid changes. Thus as mentioned above, it is recommended that antennas are arranged along with the $\theta$ rotation of the positioner + +##### **Arrangement of antennae associated with their frequency coverage** + +It is predicted that the non-linear phase variation varies with frequency. Ergo, it is advantageous to reserve the ideal location (focus) for the antenna serving the highest frequencies and use offset locations for antennae serving lower frequencies. + +### **5.3.3 Inter-band testing ramifications** + +The primary dependency of inter-band test set ramifications is the frequency coverage of each antenna in an IFF system with multiple antennae. + +#### 5.3.3.1 Single antenna + +For bands that can be supported by a single antenna, the condition to evaluate is if the antenna is not at the focus of the mirror. On-focus single antenna IFF systems have already been studied and their MU quantified, and do not need to be considered again in this context. Non-ideal (off-focus) location causes the following problems: + +- A shifted QZ due to beam tilt. Note however that all bands have the same AoA at the UE. +- Beam tilt causes the AoA to no longer be parallel to the optical axis. This aspect must be properly considered during system calibration; for example, a directional calibration antenna placed at the QZ must be pointed accurately along the arrival direction for an accurate path loss estimate. + +Provided the problems above are accounted for, UEs with either CBM or IBM can tolerate an IFF system with an off-focus source. + +#### 5.3.3.2 Multiple antennae + +The assumption for inter-band testing in this context is that the bands are supported through multiple non-co-located test system antennae. For this set up, the considerations listed in the single antenna case get further complicated. + +- A reduction in QZ size due to different beam tilt experienced by different bands. +- Beam tilt causes different AoA for different bands. There are two problems associated with this aspect: + - Calibration for each band will require adjustment of a directional calibration antenna so it is pointed along arrival direction of band being calibrated. + - This set up can be perceived as 'non-co-located' gNBs by some UEs. + +The calibration step complication, and the QZ size reduction may be surmountable, but the non-co-located gNB implication can cause significant problems for UEs with CBM limitation. + +A special note is warranted for ACS and IBB requirements – the standard requires that the interferer share the same AoA as the DL band being tested. Fortunately, ACS and IBB interferers are expected to be in the same band as the DL being tested, so it would be natural for the test equipment to use the same antenna for both. If such is not the case, additional MU would be introduced into the system, which is not preferred. + +## 5.4 Extreme temperature conditions + +### 5.4.1 ETC test system + +Permitted test methods (i.e. DFF, IFF, NFTF) defined in Clause 5, TR 38.810 [3] can support extreme temperature condition tests with the update of additional temperature control system. An example of IFF-based ETC test system is shown in Figure 5.4.1-1 below. + +![Diagram of an IFF-based ETC test system. The setup includes an ETC enclosure with a device under test (DUT) inside, a reflector, and a feed antenna. The ETC enclosure is connected to a positioner controller, which is connected to a PC. The PC is also connected to an SS (Signal Source).](17431d8b59408f09df7552d8bdbaa015_img.jpg) + +The diagram illustrates an IFF-based ETC test system. Inside a large, rectangular ETC enclosure, there is a DUT (Device Under Test) mounted on a rotating platform. A reflector is positioned to the right of the DUT, and a feed antenna is located below it. The ETC enclosure is connected to a positioner controller, which is in turn connected to a PC. The PC is also connected to an SS (Signal Source). The DUT is shown with coordinate axes (X, Y, Z) and rotation arrows indicating its orientation. + +Diagram of an IFF-based ETC test system. The setup includes an ETC enclosure with a device under test (DUT) inside, a reflector, and a feed antenna. The ETC enclosure is connected to a positioner controller, which is connected to a PC. The PC is also connected to an SS (Signal Source). + +**Figure 5.4.1-1: An example of an IFF-based ETC test system** + +The key aspects of the ETC setup are: + +- The test system should support the temperature range for extreme conditions, i.e. $-10^{\circ}\text{C}$ to $+55^{\circ}\text{C}$ , defined in Annex E.2.1 in TS 38.101-2 [2]. +- The criterion temperature tolerance is defined in 5.4.5 +- A positioning system can support 3D scan. + +### 5.4.2 Calibration procedure + +The path loss calibration should be performed with the ETC enclosure surrounding the calibration reference antenna. All measurements performed with the ETC enclosure in place shall use the path loss calibration performed under this condition. + +### 5.4.3 Test procedure + +For EIRP/EIS beam peak searching procedure under ETC, two test procedures are available: + +- Option 1: perform 3D scan +- Option 2: beam peak search within a certain cone of directions around peak position under NTC (by declaration or NTC peak searching results) + +By default, 3D scan is used for ETC tests. If a certain cone of directions around peak position under NTC can be declared by UE vendor or be got from NTC peak searching results, then option 2 can be used. + +Note: 3D scan (option 1) is needed for UE with best antenna panel switched by temperature variation and/or UE without declaration present. + +### 5.4.4 Temperature tolerance limit of ETC test system + +The temperature tolerance for FR2 ETC system should be defined, and the test can only be executed under target temperature within the tolerance. At least two aspects need to consider: + +- An accuracy of temperature control by an air conditioner +- Accuracy of a thermocouple to measure a temperature in the ETC enclosure + +The recommended temperature tolerance limit of FR2 ETC system is $\pm[4]^{\circ}\text{C}$ . + +## 5.5 Extension of frequency applicability for band n262 + +## 5.6 Extension of frequency applicability for FR2-2 + +### 5.6.1 Permitted test methods + +Unless otherwise stated, FR2-2 will follow the baseline UE RF methodology detailed in TR 38.810. This includes the extension of frequency applicability of permitted test methods in Clause 5.2 of TR 38.810 and the general testing and calibration aspects captured in Clause 5.2.1.3. + +The assumption on radiating aperture $D = 5\text{cm}$ can be reused for FR2-2, resulting in the extension of the definition of the minimum range length of the DFF system, as shown in Table 5.6.1-1 below. + +**Table 5.6.1-1: Minimum Range Length of DFF System for $D = 5\text{cm}$** + +| <b>f [GHz]<br/>QZ [cm]</b> | <b>24.25</b> | <b>30</b> | <b>40</b> | <b>50</b> | <b>52.6</b> | <b>71</b> | +|----------------------------|--------------|-----------|-----------|-----------|-------------|-----------| +| <b>15</b> | 0.45 | 0.55 | 0.72 | 0.88 | 0.93 | 1.23 | +| <b>30</b> | 0.53 | 0.63 | 0.79 | 0.96 | 1.00 | 1.31 | + +As related to the measurement grid assumptions, single UE antenna element pattern parameters can be reused as Table G.1.1-1 in TR38.810, with below exceptions: + +- half-power beamwidth: $[80^\circ/60^\circ]$ as starting point +- Gain: $[5\text{dBi}]$ + +Additionally, the beam steering assumptions in TR38.810 can be reused for PC3, and the worst-case antenna assumption for testability and MU assessment of handheld UEs in FR2-2 is [8 x2]. + +The worst-case antenna array configuration ( $M \times N$ ) for PC1 and PC2 on MU assessment is as follows: + +- PC1: $[144(12 \times 12)]$ +- PC2: $[40(10 \times 4)]$ + +As related to vehicular UEs, the study's outcomes are as follows: + +- Avoid developing a standardized ground plane for FR2 vehicular UEs as part of this SI. +- Consider the optional ground plane designed and manufactured by the OEM an integral part of the FR2 vehicular UE DUT submitted for conformance testing. +- Consider battery and AC/DC powered operation acceptable for FR2 vehicular UEs and request manufacturers to provide proper guidance on cable routings +- Adopt embedded UE only testing for FR2 vehicular UEs. The term embedded UE implies the OBU/TCU + antenna + optional ground plane + +### 5.6.2 Enhanced test methods + +#### 5.6.2.1 High DL power and low UL power + +#### 5.6.2.2 Polarization basis mismatch between the TE and DUT + +Unless otherwise stated, applicability of the polarization basis mismatch solutions found in Clause 5.2 of this TR, shall be extended to FR2-2. + +#### 5.6.2.3 Inter-band (FR2+FR2) CA + +#### 5.6.2.4 Extreme temperature conditions + +#### 5.6.2.5 Test time reduction + +Unless otherwise stated, applicability of the enhanced test methods defined in Clause 8.2 (RSRP(B) based RX beam peak search), Clause 8.4 (Single link polarization measurement) and Clause 8.5 (Other methods) of this TR, shall be extended to FR2-2. + +# 6 UE RRM testing methodology enhancements + +## 6.1 Extension of frequency applicability for band n262 + +Following the derivation of band-dependent parameters provided in Clause 7.1 and reusing the assumptions from Clause 6.2.1.4 of TR38.810 related to AoA scenarios and requirement types, the maximum achievable SNR for the RRM test setups with a PC3 DUT can be summarized as shown in Table 6.1-1 below. + +**Table 6.1-1: Comparison of maximum SNR between TR38.810 and preliminary extension to band n262** + +| RRM test setup | UE | CBW (MHz) | Max SNR (dB)<br>[TR38.810] | Max SNR (dB)<br>[n262] | +|-------------------------------------------------------------------------------------------------------------|--------------------------------------|-----------|----------------------------|------------------------| +| Scenario 1 (1AoA RX beam peak) for Type 1 Requirements ("Fine" RX beams) and Mode 1 Configuration (S+N) | Single band UE | 100 | [19.7] | [15.2] | +| | | 200 | [16.7] | [12.2] | +| | Multi-band UE <sup>(NOTEs 1,2)</sup> | 100 | [17.7] | [14.2] | +| | | 200 | [14.6] | [11.2] | +| | Single band UE | 100 | [12.5] | [7.6] | +| | | 200 | [9.5] | [4.6] | +| | Multi-band UE <sup>(NOTEs 1,2)</sup> | 100 | [10.5] | [6.6] | +| | | 200 | [7.5] | [3.6] | +| Scenario 2 (1AoA RX non-beam peak) for Type 1 Requirements ("Fine" RX beams) and Mode 1 Configuration (S+N) | Single band UE | 100 | [6.7] | [-2.7] | +| | | 200 | [3.7] | [-5.7] | +| | Multi-band UE <sup>(NOTEs 1,2)</sup> | 100 | [4.7] | [-3.7] | +| | | 200 | [1.7] | [-6.7] | +| | Single band UE | 100 | Not usable | Not usable | +| | | 200 | Not usable | Not usable | +| | Multi-band UE <sup>(NOTEs 1,2)</sup> | 100 | Not usable | Not usable | +| | | 200 | Not usable | Not usable | + +NOTE 1: For $\sum$ MBp from TS 38.101-2 [2] Table 6.2.1.3-4 allows up to 2 dB in Rel-15 +NOTE 2: From Rel-16 and later $\sum$ MBp can be rounded up to 1.0 dB for all bands +NOTE 3: The parameters and values in this table are preliminary and subject to further refinement by RAN5 as part of their conformance test development work. + +## 6.2 Extension of frequency applicability for FR2-2 + +### 6.2.1 General + +Unless otherwise stated, all test methods and measurement setup for FR2 RRM methodology defined in TR 38.810 [3] Clause 6 and in TS 38.508-1 [10] Clause 7 are applicable for FR2-2. + +### 6.2.2 Noc methodology + +The Noc level for Scenario 1 (1AoA RX beam peak) for Type 1 Requirements ("Fine" RX beams) and Mode 1 Configuration (S+N) described in TR 38.810 Clause 6.2.1.4.3 need to be adjusted and can be derived similar to the Noc level for UE demodulation test methods described in Clause 7.2.2. + +### 6.2.3 Maximum SNR derivation + +Following the derivation of band-dependent parameters provided in Clause 7.2 and reusing the assumptions from Clause 6.2.1.4 of TR 38.810 related to AoA scenarios and requirement types, the maximum achievable SNR for the RRM test setups can be summarized as shown in Table 6.2.3-1. + +**Table 6.2.3-1: Maximum SNR preliminary extension to band n263** + +| RRM test setup | UE | CBW (MHz) | Max SNR (dB) [n263] | +|--------------------------------------------------------------------------------------------------------------|----------------|-----------|---------------------| +| Scenario 1 (1AoA RX beam peak) for Type 1 Requirements (“Fine” RX beams) and Mode 1 Configuration (S+N) | Single band UE | 100 | [7.7] | +| | | 400 | [-0.6] | +| | Multi-band UE | 100 | TBD | +| | | 400 | TBD | +| Scenario 1 (1AoA RX beam peak) for Type 2 Requirements (“Rough” RX beams) and Mode 1 Configuration (S+N) | Single band UE | 100 | < -20 (NOTE 1) | +| | | 400 | < -20 (NOTE 1) | +| | Multi-band UE | 100 | TBD | +| | | 400 | TBD | +| Scenario 2 (1AoA RX non-beam peak) for Type 1 Requirements (“Fine” RX beams) and Mode 1 Configuration (S+N) | Single band UE | 100 | < -20 (NOTE 1) | +| | | 400 | < -20 (NOTE 1) | +| | Multi-band UE | 100 | TBD | +| | | 400 | TBD | +| Scenario 2 (1AoA RX non-beam peak) for Type 2 Requirements (“Rough” RX beams) and Mode 1 Configuration (S+N) | Single band UE | 100 | < -20 (NOTE 1) | +| | | 400 | < -20 (NOTE 1) | +| | Multi-band UE | 100 | TBD | +| | | 400 | TBD | + +NOTE 1: Result does not converge + +# 7 UE demodulation testing methodology enhancements + +## 7.1 Extension of frequency applicability for band n262 + +Annex B.3 in TR38.810 describes the detailed calculations of the maximum achievable SNR by the demodulation test setup. Although range length for the DFF setup is not a requirement for permitted methods, a reference value of 0.725m is used in the TR38.810 calculations. Furthermore, the maximum achievable SNR values are calculated assuming the highest band n259 frequency ( $f=43.5$ GHz). The highest frequency to be considered for the SNR calculation is the highest frequency of band n262: 48.2 GHz. Using the reference range length of 0.725m we determine free space path loss at $f=48.2$ GHz, as shown in Figure 7.1-1 below. + +![Figure 7.1-1: Free space path loss vs. frequency for d=0.725m. The graph shows a single blue curve representing free space path loss (dB) increasing with frequency (GHz) from 25 GHz to 48.2 GHz. Two vertical red dashed lines are drawn at 43.5 GHz and 48.2 GHz, with corresponding path loss values of 62.42 dB and 63.32 dB labeled on the graph.](cb6c5456549559ce70a9a8cb0680a880_img.jpg) + +| Frequency (GHz) | Free space path loss (dB) | +|-----------------|---------------------------| +| 43.5 | 62.42 | +| 48.2 | 63.32 | + +Figure 7.1-1: Free space path loss vs. frequency for d=0.725m. The graph shows a single blue curve representing free space path loss (dB) increasing with frequency (GHz) from 25 GHz to 48.2 GHz. Two vertical red dashed lines are drawn at 43.5 GHz and 48.2 GHz, with corresponding path loss values of 62.42 dB and 63.32 dB labeled on the graph. + +**Figure 7.1-1: Free space path loss vs. frequency for d=0.725m** + +Based on this analysis, the relative increase in free space path loss from 43.5 GHz to 48.2 GHz is 0.9 dB. + +Another parameter in the SNR calculation which scales with frequency is cable loss per meter. Using the datasheets from five different commercially available RF cables, which are rated up to 50 GHz, the average cable loss per meter is calculated (averaging performed in linear gain units), as shown in Figure 7.1-2 below. + +![Figure 7.1-2: Cable loss per meter vs frequency. The graph shows six lines representing cable loss per meter (dB) for five different vendors (A-E) and an average, plotted against frequency (GHz) from 25 GHz to 48.2 GHz. Two vertical red dashed lines are drawn at 43.5 GHz and 48.2 GHz, with corresponding average cable loss values of 5.15 dB and 5.48 dB labeled on the graph.](eecfb45aacdf80575bc7c1c6228ef6c4_img.jpg) + +| Frequency (GHz) | Average Cable loss per meter (dB) | +|-----------------|-----------------------------------| +| 43.5 | 5.15 | +| 48.2 | 5.48 | + +Figure 7.1-2: Cable loss per meter vs frequency. The graph shows six lines representing cable loss per meter (dB) for five different vendors (A-E) and an average, plotted against frequency (GHz) from 25 GHz to 48.2 GHz. Two vertical red dashed lines are drawn at 43.5 GHz and 48.2 GHz, with corresponding average cable loss values of 5.15 dB and 5.48 dB labeled on the graph. + +**Figure 7.1-2: Cable loss per meter vs. frequency** + +Based on this analysis, the relative increase in cable loss per meter from 43.5 GHz to 48.2 GHz is 0.33 dB. + +The SNR calculation related to cable loss also includes connector losses and additional margin, and it is feasible to reuse these parameters for the calculations related to band n262. + +The SNR calculation also includes two parameters which are taken from UE RF requirements: REFSENS and multi-band relaxation. For REFSENS the recently agreed value of -82.8 dBm/50 MHz is used, and for MBR 1.0 dB (rounded up from 0.7 dB) is used [2]. Table 7.1-1 below summarizes the parameters. + +**Table 7.1-1: Preliminary demodulation test setup SNR calculation parameters for band n262** + +| Parameter | Value | Comment | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|------------------------------------------------------| +| REFSENS | -82.8 dBm/50 MHz | Using REFSENS agreed for band n262 | +| Multi-band relaxation | 1.0 dB | Defined as $\text{ceil}(\cdot)$ ; change from 2.0 dB | +| FS path loss | -63.2 dB | Change from -62.3 dB (scaling from 43.5 to 48.2 GHz) | +| Cable loss | -8.7 dB | Additional 0.33 dB/m in cable loss at 48.2 GHz | +| Probe antenna gain | [12.0] dB | | +| Backoff from P1dB | [13.0] dB | | +| NOTE: The parameters and values in this table are preliminary and subject to further refinement by RAN5 as part of their conformance test development work. | | | + +The maximum achievable SNR for the demodulation test setup can be summarized as shown in Table 7.1-2. + +**Table 7.1-2: Comparison of maximum SNR between TR38.810 and preliminary extension to band n262** + +| | CBW (MHz) | Max SNR (TR38.810) | Max SNR (n262) | +|------------------------------------------------------------------------------------------------|-----------|--------------------|----------------| +| Single band UE | 100 | [19.7 dB] | [15.2] | +| | 200 | [16.7 dB] | [12.2] | +| Multi-band UE (NOTES 1,2) | 100 | [17.7 dB] | [14.2] | +| | 200 | [14.6 dB] | [11.2] | +| NOTE 1: For $\sum \text{MBp}$ from TS 38.101-2 [2] Table 6.2.1.3-4 allows up to 2 dB in Rel-15 | | | | +| NOTE 2: From Rel-16 and later $\sum \text{MBp}$ can be rounded up to 1.0 dB for all bands | | | | + +In general, there is a 3.5 dB degradation in maximum achievable SNR for band n262 relative to the budgeted values in TR38.810. + +## 7.2 Extension of frequency applicability for FR2-2 + +### 7.2.1 General + +Unless otherwise stated, all test methods and measurement setup for FR2 UE demodulation and CSI testing methodology defined in TR 38.810 Clause 7 [3] are applicable for FR2-2. + +### 7.2.2 Noc methodology + +The following methodology to define the minimum Noc level for power class X (PC\_X) and operating band Y (Band\_Y) is used for the single carrier case and a single band device: + +- $\text{Noc}(\text{PC\_X}, \text{Band\_Y}) = \text{REFSENS}_{\text{PCX}, \text{BandY}} - 10\log_{10}(\text{SCS}_{\text{REFSENS}} \times \text{PRB}_{\text{REFSENS}} \times 12) - \text{SNR}_{\text{REFSENS}} + \Delta_{\text{thermal}}$ +- $\text{REFSENS}_{\text{PCX}, \text{BandY}}$ is the REFSENS value in dBm specified for Power Class X UE in band Y for [100MHz] channel bandwidth +- $\text{SCS}_{\text{REFSENS}}$ is [120 kHz]. +- $\text{PRB}_{\text{REFSENS}}$ is NRB associated with subcarrier spacing $\text{SCS}_{\text{REFSENS}}$ for [100MHz] channel bandwidth + +- 12 is the number of subcarriers in a PRB +- $\text{SNR}_{\text{REFSENS}} = -1$ dB is the SNR used for simulation of REFSENS +- $\Delta_{\text{thermal}}$ is the amount of dB that the wanted noise is set above UE thermal noise, giving a rise in total noise of $\Delta_{\text{BB}}$ . $\Delta_{\text{thermal}} = 6$ dB, giving a rise in total noise of 1dB. + +*Note: Further confirmation of used parameters is needed based on core requirements definition.* + +### 7.2.3 Maximum SNR derivation + +This clause includes an informational assessment of testable DL SNR range for FR2-2 for maximum frequency ( $\sim 71$ GHz) using TR38.810 methodology. Annex B.3 in TR38.810 describes the detailed calculations of the maximum achievable SNR by the demodulation test setup. As an informative assessment, calculation of the maximum testable DL SNR for band n263 is performed below. IFF test method is considered. + +Although range length for the DFF setup is not a requirement for permitted methods, a reference value of 0.725m is used in the TR38.810 calculations. The highest frequency to be considered for the SNR calculation is the highest frequency of band n263: $f=71$ GHz. Using the reference range length of 0.725m we determine free space path loss, together with modeling of atmospheric absorption, at $f=71$ GHz, as shown in Figure 7.2.3-1 below. + +![Figure 7.2.3-1: Free space path loss vs. frequency for d=0.725m. The graph shows two curves: 'Free space path loss' (solid blue line) and 'PL with atmospheric absorption' (dashed red line). The x-axis is frequency (GHz) from 25 to 75, and the y-axis is free space path loss (dB) from 50 to 70. At 55 GHz, the path loss is 64.77 dB. At 71 GHz, the path loss is 66.68 dB. The two lines are nearly perfectly overlaid, showing no significant difference between free space path loss and path loss with atmospheric absorption at this range length.](81f54eb0ad0c7dfc557a7e3b22bb025b_img.jpg) + +| Frequency (GHz) | Free space path loss (dB) | PL with atmospheric absorption (dB) | +|-----------------|---------------------------|-------------------------------------| +| 55 | 64.77 | 64.77 | +| 71 | 66.68 | 66.68 | + +Figure 7.2.3-1: Free space path loss vs. frequency for d=0.725m. The graph shows two curves: 'Free space path loss' (solid blue line) and 'PL with atmospheric absorption' (dashed red line). The x-axis is frequency (GHz) from 25 to 75, and the y-axis is free space path loss (dB) from 50 to 70. At 55 GHz, the path loss is 64.77 dB. At 71 GHz, the path loss is 66.68 dB. The two lines are nearly perfectly overlaid, showing no significant difference between free space path loss and path loss with atmospheric absorption at this range length. + +**Figure 7.2.3-1: Free space path loss vs. frequency for d=0.725m** + +We note that atmospheric attenuation has no impact on path loss at the range scales of an FR2 testing chamber. + +Another parameter in the SNR calculation which scales with frequency is cable loss per meter. Using the datasheets from four different commercially available RF cables, which are rated up to at least 90 GHz, we calculate the average cable loss per meter (averaging performed in linear gain units), as shown in Figure 7.2.3-2 below. + +![Figure 7.2.3-2: Cable loss per meter vs. frequency. A line graph showing attenuation (dB/m) versus frequency (GHz) for four vendors (A, B, C, D) and an average. The x-axis ranges from 25 to 75 GHz, and the y-axis ranges from 2 to 14 dB/m. Vendor D (cyan) has the highest loss, starting at ~8.5 dB/m at 25 GHz and reaching ~13.5 dB/m at 75 GHz. Vendor B (green) and the Average (dotted black) are close, starting at ~5.5 dB/m and reaching ~10.5 dB/m. Vendor A (blue) starts at ~5 dB/m and reaches ~8.5 dB/m. Vendor C (red) has the lowest loss, starting at ~3 dB/m and reaching ~5.5 dB/m. Two vertical red lines indicate cable loss (CL) values at 58 GHz (CL=8.94 dB) and 72 GHz (CL=10.29 dB).](9600eb9b09749d5b8a30898a75407ac8_img.jpg) + +Figure 7.2.3-2: Cable loss per meter vs. frequency. A line graph showing attenuation (dB/m) versus frequency (GHz) for four vendors (A, B, C, D) and an average. The x-axis ranges from 25 to 75 GHz, and the y-axis ranges from 2 to 14 dB/m. Vendor D (cyan) has the highest loss, starting at ~8.5 dB/m at 25 GHz and reaching ~13.5 dB/m at 75 GHz. Vendor B (green) and the Average (dotted black) are close, starting at ~5.5 dB/m and reaching ~10.5 dB/m. Vendor A (blue) starts at ~5 dB/m and reaches ~8.5 dB/m. Vendor C (red) has the lowest loss, starting at ~3 dB/m and reaching ~5.5 dB/m. Two vertical red lines indicate cable loss (CL) values at 58 GHz (CL=8.94 dB) and 72 GHz (CL=10.29 dB). + +**Figure 7.2.3-2: Cable loss per meter vs. frequency** + +We further note that the SNR calculation related to cable loss also includes connector losses and additional margin. Demodulation test system setup parameters required for SNR calculation are summarized in Table 7.2.3-1. + +**Table 7.2.3-1: Demodulation test setup SNR calculation parameters for band n263** + +| Parameter | Comment | +|------------------------------------------|----------------------------------------------------------| +| REFSENS | Using REFSSENS agreed for band n263<br>-72.0 dBm/400 MHz | +| Multi-band relaxation | TBD | +| TE amplifier 1dB compression | 23 dBm | +| Backoff from P1dB | --11.08 (RAN5 assumption endorsed in R5-221628) | +| Cable loss | 10.3 dB, assuming 1m length | +| Connector insertion loss | 0 | +| FS path loss | 66.7 dB, assuming 0.725m range length | +| TE DL absolute power setting uncertainty | +/-6 dB | +| Probe antenna gain | 12 dBi | +| Beam peak search procedure error | 0.5 dB | + +The maximum achievable DL SNR is summarized in Table 7.2.3-2. + +**Table 7.2.3-2: Maximum DL testable SNR preliminary extension for band n263** + +| | CBW (MHz) | Test method | +|-----------------------|-----------|----------------| +| | | IFF | +| <b>Single band UE</b> | 100 | [9.8] | +| | 400 | [2.6] | +| | 800 | [-2.3] | +| | 1600 | < -20 (NOTE 1) | +| | 2000 | < -20 (NOTE 1) | +| <b>Multi band UE</b> | 100 | TBD | + +| | | | +|----------------------------------|------|-----| +| | 400 | TBD | +| | 800 | TBD | +| | 1600 | TBD | +| | 2000 | TBD | +| NOTE 1: Result does not converge | | | + +A method to adjust $\Delta$ thermal value in Noc setting methodology can increase max achievable DL SNR. $\Delta$ thermal is the actual difference between UE thermal noise level and wanted noise level. The difference between these levels leads to the difference between baseband SNR and SNR at the reference point. According to the FR2-1 SNR calculation methodology, 6 dB $\Delta$ thermal is used that corresponds to 1 dB SNR difference. + +Table 7.2.3-2 below provides evaluations how $\Delta$ thermal impacts DL SNR. For simplicity the $\Delta$ thermal value is recalculated to allowed SNR difference (allowed noise increase). 400 MHz CBW and -13 dB backoff from P1dB were selected for the analysis. Note that at 3 dB allowed noise increase, Noc level becomes the same as UE thermal noise level. + +**Table 7.2.3-3: Allowed noise increase vs max achievable DL SNR** + +| Allowed noise increase, dB | 1 | 2 | 3 | +|----------------------------|-----|-----|-----| +| $\Delta$ thermal, dBm/Hz | 6.1 | 2.6 | 0.1 | +| Max DL SNR BB, dB | 1.1 | 5 | 6.8 | + +Minimum FR2-1 DL radiated performance requirements are specified for up to Rank 2. The required SNR point is 14.4 and 18.6 dB for 16QAM and 64QAM respectively for 100 MHz and 120 kHz CBW/SCS combination. It can be approximately expected that SNR will not dramatically change for higher CBWs as 400MHz. Same time, some margin on phase noise impact at higher carrier frequency should be considered. For instance, 16 and 20 dB SNRs can be assumed. Such SNR targets require adjustments of TE parameters. Table 7.2.3-4 summarizes required wanted signal + headroom budget to reach 16 and 20 dB DL SNR. The parameters from Table 7.2.3-1 are assumed with RAN4 assumption on backoff from P1dB. + +**Table 7.2.3-4: Wanted signal + headroom budget vs max achievable DL SNR** + +| Target DL SNR, dB | 16 | 20 | +|--------------------------------------|------|------| +| wanted signal + headroom, dBm/ Ch BW | 35.8 | 39.8 | + +Wanted signal + headroom budget can be increased by adjustment of power amplifier 1dB compression point and/or probe antenna gain. Another option how to allow testing of high CBW is to restrict max PRB allocation size within the CBW. As seen from Table 7.2.3-2, 66 PRB allocation size (100 MHz) leads to 7.7 dB max SNR increase compared to 264PRBs in 400 MHz. + +# 8 Test time reduction + +## 8.1 General + +The verification methodologies for FR2 UE RF, UE RRM, and UE demodulation requirements are all OTA measurements. Given the complexity of OTA test system, the test time of RF, RRM and demodulation test have been dramatically increased compare with FR1 conducted test cases. + +An example of test time of some FR2 RF test cases is listed in Table 8.1-1. + +**Table 8.1-1: Feedback of actual FR2 testing time from one TE vendor (example)** + +| FR2 test cases based on TS38.521-3/2: | | | Time/h or min | +|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|----------------------| +| 38.521-2 | | Tx beam peak direction search | 4h (with 7.5° step) | +| 38.521-2 | | Rx beam peak direction search | 11h (with 7.5° step) | +| 38.521-3 | 6.2B.1.4.1 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (2 CCs) - EIRP and TRP | 30min | +| 38.521-3 | 6.2B.1.4.2 | UE Maximum Output Power for Inter-Band EN-DC including FR2 (2 CCs) - Spherical Coverage | 1h | +| 38.521-3 | 6.3B.2.4 | Transmit OFF Power for inter-band EN-DC including FR2 | 15min | +| 38.521-3 | 6.5B.2.4.1 | Spectrum emissions mask for Inter-band EN-DC including FR2 (2 CCs) | 35min | +| 38.521-3 | 6.5B.2.4.3 | Adjacent channel leakage ratio for Inter-band EN-DC including FR2 (2 CCs) | 35min | +| 38.521-3 | 6.5B.3.4.1 | General Spurious Emissions for Inter-band including FR2 (2 CCs) | 1h | +| Note: | The above testing time is varied due to different UE performance, Test software version, and detailed parameters setting. | | | + +In addition, given all the FR2 UE should be tested with the DUT operated in stand-alone battery powered mode [3], which means much power charging time should also be considered, then the total testing time would be further increased. Therefore, proper approaches to reduce the FR2 test time significantly is a key issue to be resolved. + +## 8.2 New measurement grid + +### 8.2.1 New measurement grids based on 4x2 antenna pattern assumption + +For PC3 UEs, an 4x2 antenna array has been agreed for measurement grid analyses. The Table 8.2.1-1 and Table 8.2.1-2 outline the antenna patterns for simulation. + +**Table 8.2.1-1: Single Antenna Element Radiation Pattern** + +| | | +|-------------------------------------------------------|-----------------------| +| Antenna element horizontal radiation pattern | , $A_m = 30$ dB | +| Horizontal half-power beamwidth of single element | $260^\circ$ | +| Antenna element vertical radiation pattern | , $SLA_v = 30$ dB | +| Vertical half-power beamwidth of single array element | $130^\circ$ | +| Array element radiation pattern | $G_{E,max} = 1.5$ dBi | +| Element gain without antenna losses | $G_{E,max} = 1.5$ dBi | + +**Table 8.2.1-2: Composite Antenna Array Radiation Pattern** + +| | | +|----------------------------------------------------|--------------------------------------------------------------------------------| +| Composite array radiation pattern in dB | the super position vector is given by:<br>;<br>;<br>the weighting is given by: | +| Antenna array configuration (Row×Column) | 4 × 2 | +| Horizontal radiating element spacing $d_h/\lambda$ | 0.5 | +| Vertical radiating element spacing $d_v/\lambda$ | 0.5 | + +Based on 4x2 antenna array, the following three types of measurement grids need to be derived: + +- Beam Peak Search Grid: using this grid, the TX and RX beam peak direction will be determined. 3D EIRP scans are used to determine the TX beam peak direction and 3D Throughput/RSRP/EIS scans for RX beam peak directions. +- Spherical Coverage Grid: using this grid, the CDF of the EIRP/EIS distribution in 3D is calculated to determine the spherical coverage performance. +- TRP Measurement Grid: using this grid, the total power radiated by the DUT in the TX beam peak direction is determined by integrating the EIRP measurements taken on the sampling grid. + +#### 8.2.1.1 Beam Peak Search Measurement Grid + +Following the analysis approach in TR38.810 Annex G, similar analyses based on 50k simulations have been performed for the 4x2 antenna array assumption. The global beam peak of the 4x2 antenna array was determined first. Subsequently, the relative orientation of the simulated antenna array and the measurement grid was altered randomly. + +Sample histograms and CDF distributions for the beam peak error for constant step-size measurement grids are shown in Figure 8.2.1.1-1 and for the constant density measurement grid (based on the charged particle implementation) in Figure 8.2.1.1-2. The histograms show a half-normal distribution. + +Given the half-normal distribution, the MU term should be based on the determination of the offset from the beam peak that contains 95% of the distribution (alternatively, the value at which the CDF is 5%). This offset shall be considered a systematic error in the MU budget. The various statistical metrics are illustrated in Figure 8.2.1.1-3. + +![Figure 8.2.1.1-1: Histogram of maximum beam peak errors for sample constant-step size measurement grids. The figure contains two side-by-side plots. The left plot is for a 12° step size and the right plot is for a 15° step size, both for 260°/130° HPBW. Each plot shows a blue histogram representing the PDF and a red line representing the CDF. The x-axis is 'Beam Peak Error (Max EIRP - Beam Peak EIRP) [dB]' ranging from -0.6 to 0 for the left plot and -1 to 0 for the right plot. The left y-axis is 'Histogram' (0 to 1400) and the right y-axis is 'CDF' (0 to 1). The distributions are skewed towards negative errors, indicating overestimation of beam peak power.](7a4a00f53376de68707bb8a27b211f02_img.jpg) + +Figure 8.2.1.1-1: Histogram of maximum beam peak errors for sample constant-step size measurement grids. The figure contains two side-by-side plots. The left plot is for a 12° step size and the right plot is for a 15° step size, both for 260°/130° HPBW. Each plot shows a blue histogram representing the PDF and a red line representing the CDF. The x-axis is 'Beam Peak Error (Max EIRP - Beam Peak EIRP) [dB]' ranging from -0.6 to 0 for the left plot and -1 to 0 for the right plot. The left y-axis is 'Histogram' (0 to 1400) and the right y-axis is 'CDF' (0 to 1). The distributions are skewed towards negative errors, indicating overestimation of beam peak power. + +**Figure 8.2.1.1-1: Histogram of maximum beam peak errors for sample constant-step size measurement grids (left: 12°, right: 15° step size) for 260°/130° HPBW** + +![Figure 8.2.1.1-2: Two side-by-side plots showing the histogram of maximum beam peak errors for sample constant density measurement grids. The left plot is for 320 grid points and the right plot is for 200 grid points, both for 260°/130° HPBW. Each plot shows a blue histogram of Beam Peak Error (Max EIRP - Beam Peak EIRP) [dB] on the x-axis (ranging from -0.6 to 0 for the left plot and -1 to 0 for the right plot) and a red CDF curve. The y-axis on the left shows the Histogram count (0 to 1200) and the y-axis on the right shows the CDF (0 to 1).](0cefc51a6600c6c8e2c2b60fcff0fb63_img.jpg) + +Figure 8.2.1.1-2: Two side-by-side plots showing the histogram of maximum beam peak errors for sample constant density measurement grids. The left plot is for 320 grid points and the right plot is for 200 grid points, both for 260°/130° HPBW. Each plot shows a blue histogram of Beam Peak Error (Max EIRP - Beam Peak EIRP) [dB] on the x-axis (ranging from -0.6 to 0 for the left plot and -1 to 0 for the right plot) and a red CDF curve. The y-axis on the left shows the Histogram count (0 to 1200) and the y-axis on the right shows the CDF (0 to 1). + +**Figure 8.2.1.1-2: Histogram of maximum beam peak errors for sample constant density measurement grids (left: 320, right: 200 grid points) for 260°/130° HPBW** + +![Figure 8.2.1.1-3: A plot showing statistical metrics for a sample half-normal distribution. The x-axis is Beam Peak Error (Max EIRP - Beam Peak EIRP) [dB] from -1 to 0. The left y-axis is Histogram count from 0 to 3000. The right y-axis is CDF from 0 to 1. The plot shows a blue histogram and a red CDF curve. A green vertical line indicates the Mean Error. A yellow horizontal double-headed arrow indicates the STD (Standard Deviation). A purple horizontal double-headed arrow indicates the Offset_{5\%CDF}.](68f0e97e094e315c0ed95a24eb0585c3_img.jpg) + +Figure 8.2.1.1-3: A plot showing statistical metrics for a sample half-normal distribution. The x-axis is Beam Peak Error (Max EIRP - Beam Peak EIRP) [dB] from -1 to 0. The left y-axis is Histogram count from 0 to 3000. The right y-axis is CDF from 0 to 1. The plot shows a blue histogram and a red CDF curve. A green vertical line indicates the Mean Error. A yellow horizontal double-headed arrow indicates the STD (Standard Deviation). A purple horizontal double-headed arrow indicates the Offset\_{5\%CDF}. + +**Figure 8.2.1.1-3: Statistical metrics for a sample half-normal distribution** + +The statistical results from simulations using 50k random orientations are then used for further analyses, summarized in Table 8.2.1.1-1 for constant-step-size grids and in Table 8.2.1.1-2 for constant-density grids. The simulation assumptions of the rotations were the same as those outlined in Annex G.1.1 of [3]. It should be noted that these measurement grids are derived without consideration of UE beam steering effect (i.e. beam correspondence). + +**Table 8.2.1.1-1: Statistical Analyses of the 50k simulations for the constant-step size grids** + +| Angular Step Size [°] | Number of unique grid points | Mean Error [dB] | STD [dB] | Offset <sub>5%CDF</sub> [dB] | +|-----------------------|------------------------------|-----------------|----------|------------------------------| +| 7.5 | 1106 | 0.07 | 0.05 | 0.17 | +| 9.0 | 762 | 0.10 | 0.07 | 0.25 | +| 10.0 | 614 | 0.12 | 0.09 | 0.31 | +| 11.25 | 482 | 0.15 | 0.11 | 0.38 | +| 12.0 | 422 | 0.17 | 0.13 | 0.44 | +| 12.86 | 366 | 0.20 | 0.15 | 0.50 | +| 13.8 | 314 | 0.23 | 0.17 | 0.58 | +| 15.0 | 266 | 0.27 | 0.21 | 0.69 | + +**Table 8.2.1.1-2: Statistical Analyses of the 50k simulations for the constant-density grids** + +| Number of unique grid points | Mean Error [dB] | STD [dB] | Offset <sub>5%CDF</sub> [dB] | +|------------------------------|-----------------|----------|------------------------------| +| 800 | 0.07 | 0.05 | 0.17 | +| 700 | 0.09 | 0.06 | 0.20 | +| 650 | 0.09 | 0.06 | 0.21 | +| 600 | 0.10 | 0.07 | 0.23 | +| 550 | 0.11 | 0.07 | 0.25 | +| 500 | 0.12 | 0.08 | 0.28 | +| 450 | 0.13 | 0.09 | 0.31 | +| 400 | 0.15 | 0.10 | 0.35 | +| 350 | 0.17 | 0.12 | 0.39 | +| 300 | 0.20 | 0.14 | 0.46 | +| 275 | 0.22 | 0.15 | 0.50 | +| 250 | 0.24 | 0.16 | 0.55 | + +Based on the previously agreed limit of Offset<sub>5%CDF</sub> of 0.5dB (systematic error), the following minimum number of grid points would be required for Beam Peak Search Grid. + +- Constant density grid with at least 275 grid points +- Constant step size grid with at least 366 grid points + +**Table 8.2.1.1-3: Min Number of Grid Points for TX/RX Beam Peak Search** + +| Antenna Assumption | 8x2 | 4x2 | Factor of Improvement | +|--------------------|------|-----|-----------------------| +| Grid Type | | | | +| Constant-Step Size | 1106 | 366 | 3.0 | +| Constant-Density | 800 | 275 | 2.9 | + +The approximate test times for the 4x2 beam peak searches are as follows: + +- Constant-Step Size: TX ~0.7hrs; RX ~4hrs +- Constant Density: TX ~0.5hrs; RX ~3hrs + +#### 8.2.1.2 Spherical Coverage Measurement Grid + +The simulation assumptions including the antenna patterns for the spherical coverage measurement grids are the same as Clause G.3 [3] except the 4x2 antenna array assumptions instead of 8x2. + +At the 50%-tile CDF, i.e., the target CDF for Power Class 3, statistical analyses of all 10000 EIRPs, EIRP50%CDF, are performed. + +The simulations in this contribution were only for the case where the beam peak is oriented in completely random orientations, i.e., the beam peak is not always aligned to a grid point. It is understood that the CDF curve cannot be used to accurately determine the TX beam peak (100%-tile CDF) + +Unlike in [3], the simulations here were performed for EIRP only it was shown previously that the EIS simulations with infinitesimal DL power step sizes match the standard deviations of the EIRP results and that a finite DL power step size introduces a mean error that matches the DL power step size. + +The results for various constant-step size measurement grids are tabulated in Table 8.2.1.2-1 and the grid with similar MUs as previously agreed for the 8x2 based PC3 configuration is highlighted. + +**Table 8.2.1.2-1: Statistical results of EIRP50%CDF for the 4x2 antenna array for constant step size measurement grids and the beam peak oriented in completely random orientations.** + +| Step Size [ $\alpha$ ] | Number of unique grid points | Std. Dev [dB] | Mean Error [dB] | +|------------------------|------------------------------|---------------|------------------| +| 10.0 | 614 | 0.03 | 0.00 | +| 12.0 | 422 | 0.08 | 0.01 | +| 15.0 | 266 | 0.06 | 0.02 | +| 20.0 | 146 | 0.10 | 0.03 | +| 22.5 | 114 | 0.22 | 0.02 | +| 30.0 | 62 | 0.21 | 0.04 | +| 45.0 | 26 | 0.30 | 0.14 | + +Similar results for the constant-density measurement grids are tabulated in Table 8.2.1.2-2 and the grid with similar MUs as previously agreed for the 8x2 based PC3 configuration is highlighted. + +**Table 8.2.1.2-2: Statistical results of EIRP50%CDF for the 4x2 antenna array for constant density measurement grids and the beam peak oriented in completely random orientations.** + +| Number of unique grid points | Std. Dev [dB] | Mean Error [dB] | +|------------------------------|---------------|------------------| +| 50 | 0.19 | 0.05 | +| 60 | 0.25 | 0.03 | +| 70 | 0.21 | 0.04 | +| 80 | 0.22 | 0.03 | +| 90 | 0.14 | 0.03 | +| 100 | 0.12 | 0.03 | +| 110 | 0.10 | 0.03 | +| 120 | 0.09 | 0.03 | +| 130 | 0.07 | 0.02 | +| 140 | 0.07 | 0.02 | +| 150 | 0.07 | 0.02 | + +At least 100 (constant density grid with charged particle implementation) or 146 (constant step size grid with 20deg step size) measurement grid points shall be used for EIRP spherical coverage procedure. Compared with 8x2 antenna array, the factor of improvement based on new measurement grid with 4x2 antenna is about 2, as summarized in the table 8.2.1.2-3. + +**Table 8.2.1.2-3: Min Number of Grid Points for Spherical Coverage** + +| Antenna Assumption | 8x2 | 4x2 | Factor of Improvement | +|--------------------|----------------|----------------|-----------------------| +| Grid Type | | | | +| Constant-Step Size | 266 (15.0 deg) | 146 (20.0 deg) | 1.8 | +| Constant-Density | 200 | 100 | 2 | + +#### 8.2.1.3 TRP Measurement Grid + +The simulation assumptions including the antenna patterns for the TRP measurement grids are the same as Clause G.2 [3] except a 4x2 antenna array assumption instead of 8x2 for both single-element antenna patterns. + +The results tabulated in this section outline the results of a statistical analyses with the positioning concept taken into account, i.e., the analyses were performed with and without the assumption that the beam peak direction is oriented away from the hemisphere towards the pole at $\theta = 180^\circ$ . Additionally, the standard deviations are presented when + +ranges of pattern values are disregarded (zeroed out). For the constant-step size measurement grids, three cases were investigated, i.e., no pattern values are disregarded, values only at one latitude at $\theta=180^\circ$ , and the values at the bottom two latitudes are disregarded. The results with the re-positioning concept applied are summarized in Table 8.2.1.3-1 for the $\sin(\theta)$ and the Clenshaw-Curtis quadratures while the results without the re-positioning concept applied are summarized in Table 8.2.1.3-2. + +For the constant density measurement grids, a similar investigation was performed using the Charged Particle implementation. Two cases investigated were: no pattern values are disregarded and values between $X \leq \theta \leq 180^\circ$ are disregarded. The results with the re-positioning concept applied are summarized in Table 8.2.1.3-2 for the Charged Particle implementation while the results without the re-positioning concept applied are summarized in Table 8.2.1.3-4. + +The previously agreed limit for the PC3 TRP grids is 0.25dB. Those measurement grids meeting that limit have been highlighted in green while the grids exceeding that limit are highlighted in red. It should be noted that some mean errors are relatively high for grids that meet the 0.25dB std. deviation limit and therefore should not be considered candidate measurement grids. + +**Table 8.2.1.3-1: Statistics of quadrature approaches for constant step size measurement grids for the 4x2 antenna array with the re-positioning concept applied.** + +| Number of | | Step Size<br>$\Delta\theta=\Delta\phi$ | Number of<br>unique<br>grid<br>points | Number of<br>Latitudes<br>disregarded | Mean<br>Error<br>[dB] | Std.<br>Dev<br>[dB] | Quadrature | Re-<br>Positioning<br>Concept<br>Applied | +|-----------|------------|----------------------------------------|---------------------------------------|---------------------------------------|-----------------------|---------------------|-----------------|------------------------------------------| +| Latitudes | Longitudes | | | | | | | | +| 13 | 24 | 15 | 266 | 1 | -0.02 | 0.05 | Sin(theta) | yes | +| 13 | 24 | 15 | 266 | 1 | -0.01 | 0.01 | Clenshaw-Curtis | yes | +| 13 | 24 | 15 | 266 | 2 | -0.10 | 0.16 | Sin(theta) | yes | +| 13 | 24 | 15 | 266 | 2 | -0.08 | 0.12 | Clenshaw-Curtis | yes | +| 13 | 24 | 15 | 266 | 3 | -0.18 | 0.17 | Sin(theta) | yes | +| 13 | 24 | 15 | 266 | 3 | -0.16 | 0.14 | Clenshaw-Curtis | yes | +| 10 | 18 | 20 | 146 | 1 | -0.05 | 0.10 | Sin(theta) | yes | +| 10 | 18 | 20 | 146 | 1 | -0.01 | 0.03 | Clenshaw-Curtis | yes | +| 10 | 18 | 20 | 146 | 2 | -0.19 | 0.27 | Sin(theta) | yes | +| 10 | 18 | 20 | 146 | 2 | -0.15 | 0.18 | Clenshaw-Curtis | yes | +| 10 | 18 | 20 | 146 | 3 | -0.31 | 0.21 | Sin(theta) | yes | +| 10 | 18 | 20 | 146 | 3 | -0.28 | 0.17 | Clenshaw-Curtis | yes | +| 8 | 14 | 25.71 | 86 | 1 | -0.08 | 0.19 | Sin(theta) | yes | +| 8 | 14 | 25.71 | 86 | 1 | -0.02 | 0.05 | Clenshaw-Curtis | yes | +| 8 | 14 | 25.71 | 86 | 2 | -0.32 | 0.40 | Sin(theta) | yes | +| 8 | 14 | 25.71 | 86 | 2 | -0.25 | 0.26 | Clenshaw-Curtis | yes | +| 8 | 14 | 25.71 | 86 | 3 | -0.52 | 0.24 | Sin(theta) | yes | +| 8 | 14 | 25.71 | 86 | 3 | -0.46 | 0.17 | Clenshaw-Curtis | yes | +| 7 | 12 | 30 | 62 | 1 | -0.11 | 0.33 | Sin(theta) | yes | +| 7 | 12 | 30 | 62 | 1 | -0.03 | 0.13 | Clenshaw-Curtis | yes | +| 7 | 12 | 30 | 62 | 2 | -0.44 | 0.53 | Sin(theta) | yes | +| 7 | 12 | 30 | 62 | 2 | -0.34 | 0.32 | Clenshaw-Curtis | yes | +| 7 | 12 | 30 | 62 | 3 | -0.73 | 0.36 | Sin(theta) | yes | +| 7 | 12 | 30 | 62 | 3 | -0.66 | 0.26 | Clenshaw-Curtis | yes | + +**Table 8.2.1.3-2: Statistics of quadrature approaches for constant step size measurement grids for the 4x2 antenna array without the re-positioning concept applied.** + +| Number of | | Step Size<br>$\Delta\theta=\Delta\phi$ | Number of<br>unique<br>grid<br>points | Number of<br>Latitudes<br>disregarded | Mean<br>Error<br>[dB] | Std.<br>Dev<br>[dB] | Quadrature | Re-<br>Positioning<br>Concept<br>Applied | +|-----------|------------|----------------------------------------|---------------------------------------|---------------------------------------|-----------------------|---------------------|------------|------------------------------------------| +| Latitudes | Longitudes | | | | | | | | + +| | | | | | | | | | +|----|----|-------|-----|---|-------|------|-----------------|----| +| 13 | 24 | 15 | 266 | 1 | -0.03 | 0.06 | Sin(theta) | no | +| 13 | 24 | 15 | 266 | 1 | -0.02 | 0.04 | Clenshaw-Curtis | no | +| 13 | 24 | 15 | 266 | 2 | -0.19 | 0.37 | Sin(theta) | no | +| 13 | 24 | 15 | 266 | 2 | -0.18 | 0.35 | Clenshaw-Curtis | no | +| 10 | 18 | 20 | 146 | 1 | -0.05 | 0.10 | Sin(theta) | no | +| 10 | 18 | 20 | 146 | 1 | -0.03 | 0.07 | Clenshaw-Curtis | no | +| 10 | 18 | 20 | 146 | 2 | -0.35 | 0.63 | Sin(theta) | no | +| 10 | 18 | 20 | 146 | 2 | -0.33 | 0.59 | Clenshaw-Curtis | no | +| 8 | 14 | 25.71 | 86 | 1 | -0.08 | 0.20 | Sin(theta) | no | +| 8 | 14 | 25.71 | 86 | 1 | -0.05 | 0.12 | Clenshaw-Curtis | no | +| 8 | 14 | 25.71 | 86 | 2 | -0.62 | 0.96 | Sin(theta) | no | +| 8 | 14 | 25.71 | 86 | 2 | -0.56 | 0.90 | Clenshaw-Curtis | no | +| 7 | 12 | 30 | 62 | 1 | -0.11 | 0.33 | Sin(theta) | no | +| 7 | 12 | 30 | 62 | 1 | -0.07 | 0.22 | Clenshaw-Curtis | no | +| 7 | 12 | 30 | 62 | 2 | -0.87 | 1.24 | Sin(theta) | no | +| 7 | 12 | 30 | 62 | 2 | -0.79 | 1.15 | Clenshaw-Curtis | no | + +**Table 8.2.1.3-3: Statistics for constant density measurement grid types for the 4x2 reference antenna array with the re-positioning concept applied (charged particle implementation only)** + +| Number of Grid Points | Range of Angles disregarded | Mean Error [dB] | Std. Dev [dB] | Re-Positioning Concept Applied | +|-----------------------|-----------------------------|-----------------|---------------|--------------------------------| +| 90 | none | 0.05 | 0.02 | yes | +| 80 | none | 0.05 | 0.03 | yes | +| 70 | none | 0.05 | 0.03 | yes | +| 60 | none | 0.05 | 0.05 | yes | +| 50 | none | 0.05 | 0.07 | yes | +| 40 | none | 0.04 | 0.17 | yes | +| 90 | 165°-180° | 0.00 | 0.08 | yes | +| 80 | 165°-180° | -0.01 | 0.09 | yes | +| 70 | 165°-180° | 0.02 | 0.07 | yes | +| 60 | 165°-180° | 0.01 | 0.09 | yes | +| 50 | 165°-180° | 0.00 | 0.11 | yes | +| 40 | 165°-180° | 0.04 | 0.17 | yes | +| 90 | 150°-180° | -0.10 | 0.18 | yes | +| 80 | 150°-180° | -0.09 | 0.18 | yes | +| 70 | 150°-180° | -0.11 | 0.20 | yes | +| 60 | 150°-180° | -0.10 | 0.20 | yes | +| 50 | 150°-180° | -0.14 | 0.21 | yes | +| 40 | 150°-180° | -0.13 | 0.28 | yes | + +**Table 8.2.1.3-4: Statistics for constant density measurement grid types for the 4x2 reference antenna array without the re-positioning concept applied (charged particle implementation only)** + +| Number of Grid Points | Range of Angles disregarded | Mean Error [dB] | Std. Dev [dB] | Re-Positioning Concept Applied | +|-----------------------|-----------------------------|-----------------|---------------|--------------------------------| +| 90 | none | 0.05 | 0.02 | no | +| 80 | none | 0.05 | 0.03 | no | +| 70 | none | 0.05 | 0.03 | no | +| 60 | none | 0.05 | 0.05 | no | +| 50 | none | 0.05 | 0.07 | no | +| 40 | none | 0.05 | 0.17 | no | +| 90 | 165°-180° | 0.00 | 0.13 | no | +| 80 | 165°-180° | -0.01 | 0.14 | no | +| 70 | 165°-180° | -0.02 | 0.17 | no | +| 60 | 165°-180° | -0.03 | 0.21 | no | +| 50 | 165°-180° | -0.04 | 0.26 | no | +| 40 | 165°-180° | -0.08 | 0.39 | no | +| 90 | 150°-180° | -0.28 | 0.58 | no | +| 80 | 150°-180° | -0.26 | 0.56 | no | +| 70 | 150°-180° | -0.32 | 0.64 | no | +| 60 | 150°-180° | -0.29 | 0.61 | no | +| 50 | 150°-180° | -0.36 | 0.70 | no | +| 40 | 150°-180° | -0.34 | 0.73 | no | + +According to the above analysis, the following conclusions can be made: + +- If the re-positioning concept is not applied to TRP test cases: + - 40 measurement grid points for constant density grid – Charged Particle implementation, with standard deviation of 0.17dB. + - 8 latitudes and 14 longitudes (84 grid points) for constant step size grid – sin (theta) weights integration approach, with standard deviation of 0.20dB with the allowance to skip and interpolate measurements at the pole at $\theta=180^\circ$ . + - 7 latitudes and 12 longitudes (62 grid points) for constant step size grid – Clenshaw Curtis weights integration approach, with standard deviation of 0.22 dB with the allowance to skip and interpolate measurements at the pole at $\theta=180^\circ$ +- If the re-positioning concept is applied to TRP test cases: + - 50 measurement grid points for constant density grid – Charged Particle implementation, with standard deviation of 0.21 dB with the allowance to skip and interpolate measurements beyond $150^\circ$ in $\theta$ + - 8 latitudes and 14 longitudes (86 grid points) for constant step size grid – sin (theta) weights integration approach, with standard deviation of 0.19dB with the allowance to skip and interpolate measurements the at pole at $\theta=180^\circ$ + - 7 latitudes and 12 longitudes (62 grid points) for constant step size grid – Clenshaw Curtis weights integration approach, with standard deviation of 0.13 dB with the allowance to skip and interpolate measurements the at pole at $\theta=180^\circ$ + +### 8.2.2 Applicability of the 4x2 measurement grids + +Since RAN5 has decided on maximum test system uncertainties and test tolerances already, it is not suggested to change the assumptions at this point as this will have significant impact in RAN5 and industry since changes in MU/MTSU could have impact on certifications and test platform validations. Keep the system-related assumptions unchanged in RAN5, i.e., based on the previously agreed worst case 8x2 assumptions. + +It is therefore the 4x2-antenna-based measurement grids are agreed as an additional option for FR2 test cases, but not replace previous 8x2 based measurement grids. The selection of measurement grid based on 4x2 or 8x2 is based on optional vendor declaration. + +The above new measurement grids based on 4x2 antenna array are applicable to both NTC and ETC test cases. + +## 8.3 RSRP(B) based RX beam peak search + +RSRP(B)-based RX beam peak search approach is applicable to find the beam peak, the beam peak searching time can be reduced significantly. + +### 8.3.1 Test procedure + +The RX beam peak direction is found with a 3D RSRP(B) scan (separately for each orthogonal downlink polarization). The RX beam peak direction is where the maximum total component of RSRP is found. The RX beam peak direction search grid points for this single grid approach are defined in Clause 8.2. + +The measurement procedure includes the following steps: + +- 1) Select any of the three Alignment Options (1, 2, or 3) from Tables N.2-1 through N.2-3 [6] to mount the DUT inside the QZ. +- 2) Position the DUT in DUT Orientation 1 or 2 from Tables N.2-1 through N.2-3 [6]. +- 3) Connect the SS (System Simulator) with the DUT through the measurement antenna with $Pol_{Link}=\theta$ polarization to form the RX beam towards the measurement antenna. +- 4) Set a proper high DL power supported by the test system, this value will be defined in RAN5 conformance test spec. Determine RSRP or RSRPBs (one per receiver branch) at $Pol_{Meas}=Pol_{Link}=\theta$ condition reported by UE. +- 5) Connect the SS (System Simulator) with the DUT through the measurement antenna with $Pol_{Link}=\phi$ polarization to form the RX beam towards the measurement antenna. +- 6) Set the same DL power as the one in step 4. Determine RSRP or RSRPBs (one per receiver branch) at $Pol_{Meas}=Pol_{Link}=\phi$ condition reported by UE. +- 7) Advance to the next grid point and repeat steps 3 through 6 until measurements within the full 3D scan have been completed. +- 8) Data processing the linear sum of four reported RSRPBs. How to calculate the reported RSRPs is FFS. + +Note: RSRPB-based test procedure is adopted for RX beam peak. Feasibility of RSRP-based approach is FFS. + +### 8.3.2 RSRP(B) accuracy + +To guarantee RSRP(B) accuracy, SNR side condition configuration can refer to the minimum SSB\_RP specified for beam correspondence in TS 38.101-2. + +## 8.4 Single link polarization measurement + +As an enhancement to the FR2 2Tx test cases, it has been proposed to adopt a Single link polarization measurement to reduce the test time. Single $Pol_{link}$ can be randomly selected from either theta $Pol_{link}$ or phi $Pol_{link}$ . + +For EIRP test, whether single $Pol_{link}$ is adopted or test under 2 link directions, depends on UE declaration. + +### 8.4.1 Test procedure + +For single link polarization measurement, the link antenna can be randomly selected, in this clause the detailed Single $Pol_{link}$ measurement procedure for TX Beam Peak direction search and EIRP Spherical Coverage based on $Pol_{Link}=\theta$ is presented as an example: + +- 1) Select any of the three Alignment Options (1, 2, or 3) from Tables N.2-1 through N.2-3 [6] to mount the DUT inside the QZ. +- 2) Position the DUT in DUT Orientation 1 from Tables N.2-1 through N.2-3 [6]. +- 3) Connect the SS (System Simulator) with the DUT through the measurement antenna with $\text{Pol}_{\text{Link}}=\theta$ to form the TX beam towards the measurement antenna. +- 4) DUT refines its TX beam toward that direction depending on DUT's beam correspondence capability which shall match OEM declaration: + - a) if DUT's beam correspondence capability is [bit-1], then DUT autonomously chooses the corresponding TX beam for PUSCH transmission using downlink reference signals to transmit in the direction of the incoming DL signal, which is based on beam correspondence without relying on UL beam sweeping + - b) if DUT's beam correspondence capability is [bit-0], then DUT chooses the TX beam for PUSCH transmission which is based on beam correspondence that relies on both DL measurements on downlink reference signals and network-assisted uplink beam sweeping. +- 5) Lock the beam and send continuously power control "up" commands in every uplink scheduling information to the UE +- 6) Measure the mean power $P_{\text{meas}}(\text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}}=\theta)$ of the modulated signal arriving at the power measurement equipment (such as a spectrum analyser, power meter, or gNB emulator). +- 7) Calculate EIRP ( $\text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}}=\theta$ ) by adding the composite loss of the entire transmission path for utilized signal path, $L_{\text{EIRP},\theta}$ , and frequency to the measured power $P_{\text{meas}}(\text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}}=\theta)$ +- 8) Measure the mean power $P_{\text{meas}}(\text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}}=\theta)$ of the modulated signal arriving at the power measurement equipment. +- 9) Calculate EIRP ( $\text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}}=\theta$ ) by adding the composite losses of the entire transmission path for utilized signal path, $L_{\text{EIRP},\phi}$ , and frequency to the measured power $P_{\text{meas}}(\text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}}=\theta)$ +- 10) Calculate total EIRP( $\text{Pol}_{\text{Link}}=\theta$ ) = EIRP( $\text{Pol}_{\text{Meas}}=\theta, \text{Pol}_{\text{Link}}=\theta$ ) + EIRP( $\text{Pol}_{\text{Meas}}=\phi, \text{Pol}_{\text{Link}}=\theta$ ) +- 11) Advance to the next grid point and repeat steps 3 through 13 until measurements within zenith range $0^\circ \leq \theta \leq 90^\circ$ have been completed +- 12) After the measurements within zenith range $0^\circ \leq \theta \leq 90^\circ$ have been completed and + - a) if the re-positioning concept is applied to the TX test cases, position the device in DUT Orientation 2 (either Options 1 or 2) from Tables N.2-1 through N.2-3 [6] for the Alignment Option selected in Step 1. For the TX beam peak search in the second hemisphere, perform steps 3 through 14 for the range of zenith angles $90^\circ < \theta \leq 180^\circ$ . + - b) if the re-positioning concept is not applied to the TX test cases, continue steps 3 through 13 for the range of zenith angles $90^\circ < \theta \leq 180^\circ$ + +The TX beam peak direction is where the maximum total component of EIRP( $\text{Pol}_{\text{Link}}=\theta$ ) is found. + +The EIRP<sub>target-CDF</sub> is then obtained from the Cumulative Distribution Function (CDF) computed using maximum EIRP( $\text{Pol}_{\text{Link}}=\theta$ ) for all grid points. + +### 8.4.2 Applicability of Single link polarization measurement + +Whether single $\text{Pol}_{\text{link}}$ is adopted or test under 2 link directions, depends on UE declaration. Link antenna for Single $\text{Pol}_{\text{link}}$ measurement can be randomly selected, i.e., using either theta $\text{Pol}_{\text{link}}$ or phi $\text{Pol}_{\text{link}}$ . + +## 8.5 Other methods + +### 8.5.1 Fast Spherical Coverage Method + +#### 8.5.1.1 General + +The Fast Spherical Coverage Method is a test method providing an optimized test time for Tx and Rx spherical coverage measurements. + +Instead of measuring all grid points as defined in Annex M of TS 38.521-2 [6] as required by the current test procedure as defined in Annex K.1.5 and Annex K.1.6 of TS 38.521-2 [6], the Fast Spherical Coverage Method requires only a reduced number of grid points to be measured. + +For test systems where the device repositioning approach outlined in Annex N of TS 38.521-2 [6] is applied, the grid points of up to a zenith of $[90]^\circ$ are allowed to be measured in the first hemisphere before the device needs to be placed in the second orientation. + +This method is applicable to Constant Density grid type. Fast spherical coverage measurement method is also applicable for constant step size grid type. + +#### 8.5.1.2 Tx Fast Spherical Coverage Method + +The measurement procedure for an EIRP Fast Spherical Coverage Method includes the following steps: + +- 1) Select any of the three Alignment Options (1, 2, or 3) from Tables N.2-1 through N.2-3 [6] to mount the DUT inside the QZ. +- 2) Position the DUT in DUT Orientation 1 or 2 from Tables N.2-1 through N.2-3 [6]. +- 3) Connect the SS (System Simulator) with the DUT through the measurement antenna with $\text{Pol}_{\text{Link}}=0$ polarization to form the TX beam towards the measurement antenna. +- 4) Send continuously uplink power control "up" commands in every uplink scheduling information to the UE. +- 5) For beam correspondence, DUT refines its TX beam toward that direction depending on DUT's beam correspondence capability which shall match OEM declaration. +- 6) Lock the beam using the UE beamlock function. +- 7) Measure the mean power $P_{\text{meas}}$ ( $\text{Pol}_{\text{Meas}}=0$ , $\text{Pol}_{\text{Link}}=0$ ) of the modulated signal arriving at the power measurement equipment (such as a spectrum analyser, power meter, or gNB emulator). +- 8) Calculate EIRP ( $\text{Pol}_{\text{Meas}}=0$ , $\text{Pol}_{\text{Link}}=0$ ) by adding the composite loss of the entire transmission path for utilized signal path, $L_{\text{EIRP},0}$ , and frequency to the measured power $P_{\text{meas}}$ ( $\text{Pol}_{\text{Meas}}=0$ , $\text{Pol}_{\text{Link}}=0$ ). +- 9) Measure the mean power $P_{\text{meas}}$ ( $\text{Pol}_{\text{Meas}}=\phi$ , $\text{Pol}_{\text{Link}}=0$ ) of the modulated signal arriving at the power measurement equipment. +- 10) Calculate EIRP ( $\text{Pol}_{\text{Meas}}=\phi$ , $\text{Pol}_{\text{Link}}=0$ ) by adding the composite losses of the entire transmission path for utilized signal path, $L_{\text{EIRP},\phi}$ , and frequency to the measured power $P_{\text{meas}}$ ( $\text{Pol}_{\text{Meas}}=\phi$ , $\text{Pol}_{\text{Link}}=0$ ). +- 11) Calculate total EIRP( $\text{Pol}_{\text{Link}}=0$ ) = ( $\text{Pol}_{\text{Meas}}=0$ , $\text{Pol}_{\text{Link}}=0$ ) + EIRP( $\text{Pol}_{\text{Meas}}=\phi$ , $\text{Pol}_{\text{Link}}=0$ ). +- 12) Unlock the beam using the UE beamlock function. +- 13) Connect the SS (System Simulator) with the DUT through the measurement antenna with $\text{Pol}_{\text{Link}}=\phi$ polarization to form the TX beam towards the measurement antenna and repeat steps 4 through 12. +- 14) Calculate the EIRP result for the grid point as $\text{EIRP}_{\text{spherical}} = \text{Max}(\text{EIRP}(\text{Pol}_{\text{Link}}=0), \text{EIRP}(\text{Pol}_{\text{Link}}=\phi))$ . If the $\text{EIRP}_{\text{spherical}}$ value is above the Min EIRP spherical coverage limit increase $N_{\text{grid, meas, PASS}}$ by 1. +- 15) Calculate the percentage of total grid points measured so far above the EIRP spherical coverage requirement limit $N_{\text{grid, meas, PASS}}$ compared to the total number of grid points on the measurement grid $N_{\text{grid,total}}$ . + +- 16) If the percentage calculated in step 15 is equal to or higher than (100 - $n^{\text{th}}$ percentile for EIRP spherical coverage)%, pass the device, otherwise continue to step 17. If all grid points have been measured, calculate the CDF for all grid points and pass the UE if the derived %-tile EIRP in measurement distribution exceeds the requirement. Otherwise fail the UE. +- 17) Advance to the next grid point and repeat steps 3 through 16 until measurements within zenith range $0^\circ \leq \theta \leq 90^\circ$ have been completed +- 18) After the measurements within zenith range $0^\circ \leq \theta \leq 90^\circ$ have been completed and + - a) if the re-positioning concept is applied to the TX test cases, position the device in the corresponding second DUT Orientation from Tables N.2-1 through N.2-3 [6] for the Alignment Option selected in Step 1 and DUT Orientation selected in Step 2. For the TX spherical coverage measurement in the second hemisphere, perform steps 3 through 16 for the range of zenith angles $90^\circ < \theta \leq 180^\circ$ . + - b) if the re-positioning concept is not applied to the TX test cases, continue steps 3 through 16 for the range of zenith angles $90^\circ < \theta \leq 180^\circ$ . + +#### 8.5.1.3 Rx Fast Spherical Coverage Method + +The measurement procedure for an EIS Fast Spherical Coverage Method includes the following steps: + +- 1) Select any of the three Alignment Options (1, 2, or 3) from Tables N.2-1 through N.2-3 [6] to mount the DUT inside the QZ. +- 2) Position the DUT in DUT Orientation 1 or 2 from Tables N.2-1 through N.2-3 [6]. +- 3) Connect the SS (System Simulator) with the DUT through the measurement antenna with $\text{Pol}_{\text{Link}} = \theta$ polarization to form the RX beam towards the measurement antenna. +- 4) Determine $\text{EIS}(\text{Pol}_{\text{Meas}} = \theta, \text{Pol}_{\text{Link}} = \theta)$ for $\theta$ -polarization, i.e., the power level for the $\theta$ -polarization at which the throughput exceeds the requirements for the specified reference measurement channel. The downlink power step size shall be no more than 0.2 dB when the RF power level is near the sensitivity level. +- 5) Connect the SS (System Simulator) with the DUT through the measurement antenna with $\text{Pol}_{\text{Link}} = \phi$ polarization to form the RX beam towards the RX beam peak direction. +- 6) Determine $\text{EIS}(\text{Pol}_{\text{Meas}} = \phi, \text{Pol}_{\text{Link}} = \phi)$ for $\phi$ -polarization, i.e., the power level for the $\phi$ -polarization at which the throughput exceeds the requirements for the specified reference measurement channel. The downlink power step size shall be no more than 0.2 dB when the RF power level is near the sensitivity level. +- 7) Calculate the resulting averaged EIS as: $\text{EIS} = 2 * [1/\text{EIS}(\text{Pol}_{\text{Meas}} = \theta, \text{Pol}_{\text{Link}} = \theta) + 1/\text{EIS}(\text{Pol}_{\text{Meas}} = \phi, \text{Pol}_{\text{Link}} = \phi)]^{-1}$ . If the EIS value is below the EIS spherical coverage limit increase $N_{\text{grid, meas, PASS}}$ by 1. +- 8) Calculate the percentage of total grid points measured so far below the EIS spherical coverage requirement limit $N_{\text{grid, meas, PASS}}$ compared to the total number of grid points on the measurement grid $N_{\text{grid, total}}$ . +- 9) If the percentage calculated in step 8 is equal to or higher than (100 - $n^{\text{th}}$ percentile for EIS spherical coverage)%, pass the device, otherwise continue to step 10. If all grid points have been measured, calculate the CCDF for all grid points and pass the UE if the derived %-tile EIS in measurement distribution is lower than the requirement. Otherwise fail the UE. +- 10) Advance to the next grid point and repeat steps 3 through 16 until measurements within zenith range $0^\circ \leq \theta \leq 90^\circ$ have been completed +- 11) After the measurements within zenith range $0^\circ \leq \theta \leq 90^\circ$ have been completed and + - a) if the re-positioning concept is applied to the TX test cases, position the device in the corresponding second DUT Orientation from Tables N.2-1 through N.2-3 [6] for the Alignment Option selected in Step 1 and DUT Orientation selected in Step 2. For the RX spherical coverage measurement in the second hemisphere, perform steps 3 through 9 for the range of zenith angles $90^\circ < \theta \leq 180^\circ$ . + - b) if the re-positioning concept is not applied to the RX test cases, continue steps 3 through 9 for the range of zenith angles $90^\circ < \theta \leq 180^\circ$ . + +### 8.5.2 Non-Uniform TRP Measurement Grids + +Given the large number of PC1 TRP grid points, as specified in Clause M.4.1.1 of [6], additional test time reduction can be achieved based on non-uniform grids. The idea here is to apply a fine grid around the FF beam peak direction to capture the main portion of the very directive beam while a coarse grid around the remaining portion of the sphere is applied. This is further illustrated in Figure 8.5.2-1 for a constant step-size grid with the following non-uniform TRP grid assumptions: + +- The known FF beam is shown with the large grey dot. On top, the FF beam peak is assumed at $(0^\circ, 0^\circ)$ while the FF beam peak on the bottom is assumed at $(45^\circ, 45^\circ)$ . +- The red grid points are within a $\pm 20^\circ$ cone centred around the NF beam peak with $\Delta\theta=\Delta\phi=7.5^\circ$ . +- The cyan grid points are outside a $\pm 20^\circ$ cone centred around the NF beam peak with $\Delta\theta=\Delta\phi=15^\circ$ . + +![Figure 8.5.2-1: Visualization of non-uniform TRP grids for NF beam at (0,0) on top and at (45,45) on bottom. The figure consists of three sub-visualizations. The top visualization shows a sphere with a coordinate system (x, y, z) where the y-axis is vertical. A large grey dot represents the FF beam peak at (0,0,0). A red dashed circle indicates the NF beam peak region. The bottom-left visualization shows the sphere with the FF beam peak at (45, 45, 0) and the NF beam peak region at (0, 0, 0). The bottom-right visualization shows the sphere with the FF beam peak at (0, 0, 0) and the NF beam peak region at (45, 45, 0). In all cases, red grid points are concentrated within a cone around the NF beam peak, while cyan grid points are distributed outside this cone.](31d28c91958950ee8785840552992758_img.jpg) + +Figure 8.5.2-1: Visualization of non-uniform TRP grids for NF beam at (0,0) on top and at (45,45) on bottom. The figure consists of three sub-visualizations. The top visualization shows a sphere with a coordinate system (x, y, z) where the y-axis is vertical. A large grey dot represents the FF beam peak at (0,0,0). A red dashed circle indicates the NF beam peak region. The bottom-left visualization shows the sphere with the FF beam peak at (45, 45, 0) and the NF beam peak region at (0, 0, 0). The bottom-right visualization shows the sphere with the FF beam peak at (0, 0, 0) and the NF beam peak region at (45, 45, 0). In all cases, red grid points are concentrated within a cone around the NF beam peak, while cyan grid points are distributed outside this cone. + +**Figure 8.5.2-1: Visualization of non-uniform TRP grids for NF beam at $(0^\circ, 0^\circ)$ on top and at $(45^\circ, 45^\circ)$ on bottom. Grid points in cyan (red) are outside (inside) the conical NF beam peak region.** + +Simulations with 2000 random permutations of the beam peak direction (rotation in $\theta$ , $\phi$ , and twist $\alpha$ as outlined in Clause G.1 of [3]) were performed for a FF range length of 20m; only the Clenshaw-Curtis quadrature was considered here. Table 8.5.2-1 shows the simulation results for the non-uniform measurement grids considered suitable for PC1 devices; the grid with step size of $7.5^\circ$ within $\pm 20^\circ$ of the FF beam peak and step size of $15^\circ$ outside $\pm 20^\circ$ of the FF beam peak are meeting the same MUs as the current measurement grid. The average number of unique grid points based on all simulations investigated is $\sim 300$ which shows a significant test time reduction compared to the current standard TRP grid with 1106 grid points while maintaining the same MU as the grid with uniform step sizes in $\theta$ and $\phi$ . + +**Table 8.5.2-1: CFFDNF TRP simulation results (using Clenshaw-Curtis quadrature) for PC1 devices (12x12 antenna configuration) using non-uniform measurement grids.** + +| Antenna Configuration | Cone width ( $\pm$ ) [ $^\circ$ ] | Constant Step-Size Grid Step Size outside cone $\Delta\theta=\Delta\phi$ [ $^\circ$ ] | Constant Step-Size Grid Step Size within cone $\Delta\theta=\Delta\phi$ [ $^\circ$ ] | Average number of unique grid points | Mean TRP Error [dB] | TRP Std. Dev. [dB] | +|-----------------------|-----------------------------------|---------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|--------------------------------------|----------------------|--------------------| +| 12x12 | 15 | 10 | 5 | 648 | 0.1 | 0.1 | +| | 20 | 15 | 5 | 338 | 0.1 | 0.1 | +| | | 15 | 7.5 | 293 | 0.1 | 0.1 | + +The TRP calculation is left to the system vendor as there are different approaches to determine TRP, e.g., interpolation of all results to the fine grid vs partial TRPs calculated within the cone and outside the cone. + +The comparison of the TRP measurement grid parameters and the min. number of grid points are tabulated in Table 8.5.2-2 with angular grid spacings placed uniformly and non-uniformly in $\theta$ and $\phi$ . Clearly, the non-uniform TRP measurement grid approach is beneficial in terms of test time reduction. + +**Table 8.5.2-2: Comparison of the TRP measurement grid parameters for PC1 including potential test time improvement.** + +| Antenna Config. | Non-uniform angular spacing | | | | Uniform angular spacing | | Potential Test Time Improvement with non-uniform angular spacing in $\theta$ and $\phi$ (factor) | +|-----------------|-----------------------------------|---------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|--------------------------------------|--------------------------------------------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------| +| | Cone width ( $\pm$ ) [ $^\circ$ ] | Constant Step-Size Grid Step Size outside cone $\Delta\theta=\Delta\phi$ [ $^\circ$ ] | Constant Step-Size Grid Step Size within cone $\Delta\theta=\Delta\phi$ [ $^\circ$ ] | Average Number of unique grid points | Constant Step-Size Grid Step Size $\Delta\theta=\Delta\phi$ [ $^\circ$ ] | Number of unique grid points | | +| 12x12 | 20 | 15 | 7.5 | 293 | 7.5 | 1106 | 3.8 | + +This non-uniform TRP grid approach is also applicable to the constant-density measurement grid type. + +# 9 Propagation conditions + +## 9.1 Extension of frequency applicability for FR2-2 + +Unless otherwise stated, the propagation condition methodology defined in TR 38.810 Clause 8 [3] is applicable for FR2-2: + +- Static propagation conditions + - Model is described in TR 38.810 clause 8.3. + - Applicable to the UE RRM testing methodology and UE Demodulation and CSI testing methodology. +- Multi-path fading propagation conditions + - Fading propagation conditions between the DUT and the emulated gNB sources are modelled as Single probe channel models as described in TR 38.810 clause 8.2. + - Applicable to the UE RRM testing methodology and UE Demodulation and CSI testing methodology. + - For FR2-2 measurement system is expected to support modelling of multi-path fading for single carrier scenarios with channel bandwidth of at least [400] MHz. + - For FR2-2 single carrier scenarios with channel bandwidth up to [400] MHz, the $F_{\text{sample}}$ is defined as [400] MHz and $\Delta T \leq [2.5]$ ns. + - An example for mapping the delays for a scaled power delay profile to the equidistant delay grid is given in clause 9.1.1 + +### 9.1.1 Example for determining the resulting delay profile + +A power delay profile after delay spread scaling is given as follows in Table 9.1.1-1. + +**Table 9.1.1-1: Original power delay profile** + +| Tap $k$ | Power (linear) | Delay $\tau_k$ [ns] | +|---------|----------------|---------------------| +| 1 | | 0 | +| 2 | | 1.91 | +| 3 | | 2.01 | +| 4 | | 2.93 | +| 5 | | 2.31 | +| 6 | | 2.69 | +| 7 | | 3.35 | +| 8 | | 2.88 | +| 9 | | 3.81 | +| 10 | | 7.69 | + +With the assumption of $\Delta T = 1/(400 \text{ MHz}) = 2.5 \text{ ns}$ , the taps from Table 9.1.1-1 can be mapped onto an equidistant delay grid as shown in Table 9.1.1-2. + +**Table 9.1.1-2: Power delay profile after mapping to delay grid** + +| Tap <i>k</i> | Power (linear) | Delay [ns] | +|--------------|----------------|------------| +| 1 | | 0 | +| 2 | | 2.50 | +| 3 | | 2.50 | +| 4 | | 2.50 | +| 5 | | 2.50 | +| 6 | | 2.50 | +| 7 | | 3.75 | +| 8 | | 2.50 | +| 9 | | 3.75 | +| 10 | | 7.5 | + +Since multiple taps share the same delay, those taps need to be combined into a single tap as shown in Table 9.1.1-3. + +**Table 9.1.1-3: Resulting delay profile** + +| Tap <i>k</i> | Power (linear) | Delay [ns] | +|--------------|----------------|------------| +| 1 | | 0 | +| 2 | | 2.50 | +| 3 | | 3.75 | +| 4 | | 7.50 | + +# --- Annex A: Environment conditions --- + +## A.1 Operating voltage --- + +## A.2 Temperature + +**Table A.2-1: Temperature conditions** + +| | | +|-----------------|---------------------------------------------------------------------------------| +| + 25 °C ± 10 °C | For normal (room temperature) conditions with relative humidity of 25 % to 75 % | +| -10°C to +55°C | For extreme conditions | + +For ETC test system defined in Clause 5.4, the extreme temperature conditions in Table A.2-1 applies. + +# Annex B: Measurement uncertainty + +## B.1 Measurement uncertainty budget for UE RF testing methodology + +### B.1.1 High DL power and low UL power + +#### B.1.1.1 Uncertainty Contributions + +This section covers the additional MU elements for different enhanced test systems in the following tables. + +**Table B.1.1.3-1: Uncertainty contributions for CFFNF system for PC3 UEs utilizing the black-box approach** + +| UID | Description of uncertainty contribution | Uncertainty Value | Details in Clause | +|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------| +| <b>Measurement stage</b> | | | | +| 1 | DUT antenna location estimation | 0 (Note 1) | N/A | +| 2 | Probe antenna pattern | 0 | B.1.1.2.2 | +| 3 | EIRP measurement error in NF | 0.27 (Note 2) | 5.1.4.6<br>(Table 5.1.4.6-4) | +| 4 | Near-field interaction between probe antenna and DUT antenna | 0 | B.1.1.2.6 | +| 5 | Influence of power measurement uncertainty | FFS (Note 3) | 5.1.4.7 | +| <b>Systematic Uncertainties</b> | | | | +| 6 | EIRP measurement error in NF | 0.10 | 5.1.4.6<br>(Table 5.1.4.6-4) | +| Note: | The range length for CFFNF with black-box approach is reported for radius $r_3 > r_2 > r_1$ and $r_3 = r_2 + 1 \text{ cm} = r_1 + 2 \text{ cm} = 22 \text{ cm}$ . | | | +| Note 1: | Black-box does not require the declaration of the antenna offset | | | +| Note 2: | Probe antenna pattern must be compensated. | | | +| Note 3: | MU can be finalized in RAN5 based on the analysis framework in Clause 5.1.4.7. | | | + +**Table B.1.1.3-2: Uncertainty contributions for CFFNF system for PC1 UEs utilizing the black-box approach** + +| UID | Description of uncertainty contribution | Uncertainty Value | Details in Clause | +|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------| +| <b>Measurement stage</b> | | | | +| 1 | DUT antenna location estimation | 0 (Note 1) | N/A | +| 2 | Probe antenna pattern | 0 | B.1.1.2.2 | +| 3 | EIRP measurement error in NF | 0.52 (Note 2) | 5.1.4.6<br>(Table 5.1.4.6-4) | +| 4 | Near-field interaction between probe antenna and DUT antenna | 0 | B.1.1.2.6 | +| 5 | Influence of power measurement uncertainty | FFS (Note 3) | 5.1.4.7 | +| <b>Systematic Uncertainties</b> | | | | +| 6 | EIRP measurement error in NF | 0.17 (Note 2) | 5.1.4.6<br>(Table 5.1.4.6-4) | +| Note: | The range length for CFFNF with black-box approach is reported for radius $r_3 > r_2 > r_1$ and $r_3 = r_2 + 1 \text{ cm} = r_1 + 2 \text{ cm} = 32 \text{ cm}$ . | | | +| Note 1: | Black-box does not require the declaration of the antenna offset | | | +| Note 2: | Probe antenna pattern must be compensated. | | | +| Note 3: | MU can be finalized in RAN5 based on the analysis framework in Clause 5.1.4.7. | | | + +**Table B.1.1.3-3: Uncertainty contributions for CFFNF system for PC3 UEs utilizing the black&white-box approach** + +| UID | Description of uncertainty contribution | Uncertainty Value | Details in Clause | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------| +| <b>Measurement stage</b> | | | | +| 1 | DUT antenna location estimation | FFS (Note 1) | 5.1.4.10 | +| 2 | Probe antenna pattern | 0 | B.1.1.2.2 | +| 3 | EIRP measurement error in NF | 0.02 (Note 2) | 5.1.4.5<br>(Table 5.1.4.5-3) | +| 4 | Near-field interaction between probe antenna and DUT antenna | 0 | B.1.1.2.6 | +| 5 | Influence of power measurement uncertainty | 0.37 | 5.1.4.7 | +| Note: | The range length for CFFNF with black&white-box approach is reported for radius $r_2 > r_1$ and $r_2 = r_1 + 2 \text{ cm} = 22 \text{ cm}$ . | | | +| Note 1: | Pending OEM feedback on typical offset estimation error. Analyses in Clause 5.1.4.9 | | | +| Note 2: | Probe antenna pattern and array offset must be compensated. | | | + +**Table B.1.1.3-4: Uncertainty contributions for CFFNF system for PC1 UEs utilizing the black&white-box approach** + +| UID | Description of uncertainty contribution | Uncertainty Value | Details in Clause | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------| +| <b>Measurement stage</b> | | | | +| 1 | DUT antenna location estimation | FFS (Note 1) | 5.1.4.10 | +| 2 | Probe antenna pattern | 0 | B.1.1.2.2 | +| 3 | EIRP measurement error in NF | 0.04 (Note 2) | 5.1.4.5<br>(Table 5.1.4.5-4) | +| 4 | Near-field interaction between probe antenna and DUT antenna | 0 | B.1.1.2.6 | +| 5 | Influence of power measurement uncertainty | FFS (Note 3) | 5.1.4.7 | +| <b>Systematic Uncertainties</b> | | | | +| 6 | EIRP measurement error in NF | 0.12 (Note 2) | 5.1.4.5<br>(Table 5.1.4.5-4) | +| Note: | The range length for CFFNF with black&white-box approach is reported for radius $r_2 > r_1$ and $r_2 = r_1 + 2 \text{ cm} = 32 \text{ cm}$ . | | | +| Note 1: | Pending OEM feedback on typical offset estimation error. Analyses in Clause 5.1.4.9 | | | +| Note 2: | Probe antenna pattern and array offset must be compensated. | | | +| Note 3: | MU can be finalized in RAN5 based on the analysis framework in Clause 5.1.4.7. | | | + +**Table B.1.1.3-5: Uncertainty contributions for CFFDNF system for PC3 UEs utilizing the black&white-box approach** + +| UID | Description of uncertainty contribution | Uncertainty Value | Details in Clause | +|--------------------------|--------------------------------------------------------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------| +| <b>Measurement stage</b> | | | | +| 1 | DUT antenna location estimation | FFS (Note 1) | 5.1.4.10 | +| 2 | Probe antenna pattern | 0 | B.1.1.2.2 | +| 3 | EIRP measurement error in NF | 0.02 (Note 2) | 5.1.4.4<br>(Table 5.1.4.4-8) | +| 4 | TRP measurement error in NF | 0.05 (Note 3) | 5.1.4.4<br>(Table 5.1.4.4-9 for uniform constant-step size grids;<br>Table 5.1.4.4-12 for non-uniform constant-step size grids) | +| 5 | Near-field interaction between probe antenna and DUT antenna | 0 | B.1.1.2.6 | + +Note: The range length for CFFNF with black&white-box approach is reported for radius $r=35$ cm (EIRP) and $r=20$ cm (TRP). + +Note 1: Pending OEM feedback on typical offset estimation error. Analyses in Clause 5.1.4.9 + +Note 2: Probe antenna pattern and array offset must be compensated + +Note 3: Alternate minimum range lengths, need for offset compensation, and measurement grids defined in Clause 5.1.4.4 + +**Table B.1.1.3-6: Uncertainty contributions for CFFDNF system for PC1 UEs utilizing the black&white-box approach** + +| UID | Description of uncertainty contribution | Uncertainty Value | Details in Clause | +|---------------------------------|--------------------------------------------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------| +| <b>Measurement stage</b> | | | | +| 1 | DUT antenna location estimation | FFS (Note 1) | 5.1.4.10 | +| 2 | Probe antenna pattern | 0 | B.1.1.2.2 | +| 3 | EIRP measurement error in NF | 0.05 (Note 2) | 5.1.4.4<br>(Table 5.1.4.4-8) | +| 4 | TRP measurement error in NF | 0.04 (Note 3) | 5.1.4.4<br>(Table 5.1.4.4-10 for uniform constant-step size grids;<br>Table 5.1.4.4-11 for non-uniform constant-step size grids) | +| 5 | Near-field interaction between probe antenna and DUT antenna | 0 | B.1.1.2.6 | +| <b>Systematic Uncertainties</b> | | | | +| 6 | EIRP measurement error | 0.45 (Note 2) | 5.1.4.4<br>(Table 5.1.4.4-8) | + +Note: The range length for CFFNF with black&white-box approach is reported for radius $r=45$ cm (EIRP) and $r=20$ cm (TRP). + +Note 1: Pending OEM feedback on typical offset estimation error. Analyses in Clause 5.1.4.9 + +Note 2: Probe antenna pattern and array offset must be compensated + +Note 3: Alternative minimum range lengths, need for offset compensation, and measurement grids defined in Clause 5.1.4.4 + +**Table B.1.1.3-7 Uncertainty contributions for CFFdeltaNF system for PC3 UEs utilizing the black-box approach** + +| UID | Description of uncertainty contribution | Uncertainty Value | Details in Clause | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------| +| <b>Measurement stage</b> | | | | +| 1 | DUT antenna location estimation | 0 | N/A | +| 2 | Probe antenna pattern | 0 | N/A | +| 3 | EIRP measurement error in NF | 0 (Note 1) | 5.1.4.8<br>(Table 5.1.4.8-1) | +| 4 | Near-field interaction between probe antenna and DUT antenna | 0 | N/A | +| <b>Systematic Uncertainties</b> | | | | +| 5 | EIRP measurement error in NF | 0.14 (Note 1) | 5.1.4.8<br>(Table 5.1.4.8-1) | +| Note: | The range length for CFFdeltaNF with black&white-box approach is reported for radius $r=35$ cm (EIRP).<br>Alternate minimum range lengths in Clause 5.1.4.8 | | | +| Note 1: | MUs include effect due to pattern change based on antenna array configuration adjustment between high-UL and low-UL operation; the effect due to pattern change based on PA nonlinearities are FFS | | | + +**Table B.1.1.3-8: Uncertainty contributions for CFFdeltaNF system for PC1 UEs utilizing the black-box approach** + +| UID | Description of uncertainty contribution | Uncertainty Value | Details in Clause | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------| +| <b>Measurement stage</b> | | | | +| 1 | DUT antenna location estimation | 0 | N/A | +| 2 | Probe antenna pattern | 0 | N/A | +| 3 | EIRP measurement error in NF | 0 (Note 1) | 5.1.4.8<br>(Table 5.1.4.8-3) | +| 4 | EIRP measurement error in NF due to pattern changes caused by PA non-linearities | FFS | 5.1.4.8 | +| 5 | Near-field interaction between probe antenna and DUT antenna | 0 | N/A | +| <b>Systematic Uncertainties</b> | | | | +| 6 | EIRP measurement error in NF | 0.5 (Note 1) | 5.1.4.8<br>(Table 5.1.4.8-3) | +| Note: | The range length for CFFdeltaNF with black&white-box approach is reported for radius $r=45$ cm (EIRP).<br>Alternate minimum range lengths in Clause 5.1.4.8 | | | +| Note 1: | MUs include effect due to pattern change based on antenna array configuration adjustment between high-UL and low-UL operation; the effect due to pattern change based on PA nonlinearities are FFS | | | + +#### B.1.1.2 Uncertainty Contributions descriptions + +##### B.1.1.2.1 DUT antenna location estimation + +This contribution originates from estimating the phase centre of the active antenna array and thus declaring the phase centre offset incorrectly in the vendor declaration for the black&white-box approach. The factors included in this uncertainty are the differences in path losses between the declare and the actual offsets and the difference in compensated probe pattern. This uncertainty is assumed to have a Gaussian distribution. This MU element is applicable to CFFDNF&CFFNF methodologies with the black&white-box approach. + +Additional background: This MU element was analysed in Clause 5.1.4.9. + +##### B.1.1.2.2 Probe antenna pattern + +The probe pattern is assumed to be known so that the measurement in the near field can be corrected when the probe pattern needs to be compensated. There is no direct dependence between the UE pattern and the probe pattern in near field measurements. This uncertainty is assumed to have a Gaussian distribution. This MU element is applicable to the CFFDNF&CFFNF methodologies. + +Additional background: This MU element is similar to the 'A3-14 Probe pattern knowledge' of the Near Field Test Range in TR 37.941 and should be considered 0 since the probe pattern can readily be measured. + +##### B.1.1.2.3 EIRP measurement error in NF + +The cause of this uncertainty contributor is due to the reduction of distance between the measurement antenna and the DUT from Far-Field to Near-Field. This uncertainty is assumed to have a Gaussian distribution. This MU element is applicable to the CFFDNF, CFFNF, and CFFdeltaNF methodologies. This MU element, if a non-insignificant mean error was identified, shall also be listed under System Uncertainties. + +Additional background: This MU element was analysed in Clauses 5.1.4.4, 5.1.4.5, 5.1.4.6, 5.1.4.8. + +For the CFFdeltaNF methodology, there is an additional impact due to changes in antenna pattern caused by PA non-linearities, etc. which is FFS. + +Additional background: This effect was analysed in Clause 5.1.4.8. + +##### B.1.1.2.4 TRP measurement error in NF + +This contribution originates from calculating the Total Radiated Power based on EIRP measurements in the NF. This uncertainty is assumed to have a Gaussian distribution. This MU element is applicable to the CFFDNF methodology. + +**Additional background:** This MU element was analysed in Clause 5.1.4.4. + +##### B.1.1.2.5 Near-field interaction between probe antenna and DUT antenna + +This uncertainty term is related to the coupling between the UE antenna and the measurement antenna in the near field at different distances. This uncertainty can be determined by multiple measurements of the DUT when at different distance from the probe. This uncertainty is assumed to have a Gaussian distribution. This MU element is applicable to the CFFDNF&CFFNF methodologies. + +Additional background: This MU element is similar to the ‘A3-15 Multiple Reflections’ MU element of the Near Field Test Range in TR 37.941 and can be assumed to be 0 but needs to be evaluated for each system separately. + +##### B.1.1.2.6 Influence of power measurement uncertainty + +This contribution originates from relative power measurement uncertainties at different radii when applied to the asymptotic expansion transformation. This uncertainty is assumed to have a Gaussian distribution. This MU element is applicable to the CFFNF methodology. + +**Additional background:** This MU element was analysed in Clause 5.1.4.7. + +##### B.1.1.2.7 Influence of noise + +This contributor describes an offset uncertainty factor caused by a noise floor especially in a case of low SNR. This contributor works as a bias to measured results only to a direction to increase values and thus this shall be included in the uncertainty budget table as a systematic uncertainty. The uncertainty value can be derived by the following equation for CFFDNF and CFFdeltaNF. + +For the CFFNF methodology, the asymptotic expansion approach requires EIRP measurements of two (black&white-box) or three different radii (black-box approach) and thus different SNR conditions for each EIRP measurement. The influence of noise MU therefore requires an AWGN analyses with those varying SNR conditions applied to the signals. + +The available SNR for the CFFDNF and CFFNF methodologies must take the reduction in free-space path losses due to measurements in the near field and the reduction of relaxations into account while making sure that the available SNR is above 6dB. + +Additional background: This MU element was analysed in Clause 5.1.4.8 + +#### B.1.1.3 Uncertainty assessment + +FFS + +### B.1.2 Polarization basis mismatch between the TE and DUT + +For TPMI-based test method for EIRP measurement, the fixed TPMI index is used to configure the UE to ensure 1 layer 2 port transmission. The test setup and test procedure keep unchanged, thus no additional MU is identified for this enhanced test method. + +### B.1.3 Inter-band (FR2+FR2) CA + +For IFF-based off-focus test system defined in Clause 5.3, the Quality of quiet zone (QoQZ) will be impacted by both the main antenna and of the offset antenna. The preliminary QoQZ difference is analysed to present the measurement uncertainty induced by the off-focus test system. + +The difference between the QoQZ of main antenna and of the offset antenna is summarized in Table B.1.3-1 and plotted in Figure B.1.3-1. Note that these values are specific to the feed antenna (amplitude taper) in this experiment and thus they may vary depending on an antenna pattern used by each test equipment vendor. + +**Table B.1.3-1: Estimation of QoQZ difference between main and offset antenna** + +| $\delta$ [mm] | Estimation of QoQZ difference (EIRP) [dB] | | | +|---------------|-------------------------------------------|------------|----------| +| | 23.45 GHz | 32.125 GHz | 40.8 GHz | +| 0 | 0.00 | 0.00 | 0.00 | +| 15 | 0.02 | 0.02 | 0.01 | +| 30 | 0.04 | 0.05 | 0.03 | +| 45 | 0.08 | 0.08 | 0.06 | +| 60 | 0.11 | 0.11 | 0.09 | +| 75 | 0.14 | 0.15 | 0.11 | + +![Figure B.1.3-1: Plot of QoQZ difference. The graph shows the QoQZ difference in dB on the y-axis (ranging from 0.00 to 0.20) against the offset distance delta in mm on the x-axis (ranging from 0 to 80). Three data series are plotted: 23.45GHz (blue line with circles), 32.125GHz (orange line with circles), and 40.8GHz (grey line with circles). All series show an increasing trend as delta increases, with 32.125GHz consistently showing the highest difference, followed by 23.45GHz, and 40.8GHz showing the lowest difference.](de6b883a4ffcab8046e199c0bfd72d84_img.jpg) + +| $\delta$ [mm] | 23.45GHz [dB] | 32.125GHz [dB] | 40.8GHz [dB] | +|---------------|---------------|----------------|--------------| +| 0 | 0.00 | 0.00 | 0.00 | +| 15 | 0.02 | 0.02 | 0.01 | +| 30 | 0.04 | 0.05 | 0.03 | +| 45 | 0.08 | 0.08 | 0.06 | +| 60 | 0.11 | 0.11 | 0.09 | +| 75 | 0.14 | 0.15 | 0.11 | + +Figure B.1.3-1: Plot of QoQZ difference. The graph shows the QoQZ difference in dB on the y-axis (ranging from 0.00 to 0.20) against the offset distance delta in mm on the x-axis (ranging from 0 to 80). Three data series are plotted: 23.45GHz (blue line with circles), 32.125GHz (orange line with circles), and 40.8GHz (grey line with circles). All series show an increasing trend as delta increases, with 32.125GHz consistently showing the highest difference, followed by 23.45GHz, and 40.8GHz showing the lowest difference. + +**Figure B.1.3-1: Plot of QoQZ difference** + +### B.1.4 Test system for ETC + +The ETC test method has been defined in Clause 5.4. The ETC test system will increase measurement uncertainty compared with NTC test system. For MOP-EIRP and REFSSENS-EIS, the comparison of the MU under NTC and ETC is summarized in the table B.1.4-1. + +**Table B.1.4-1: Comparison of MOP-EIRP and REFSSENS-EIS MTSUs.** + +| Test Case | MTSU [dB] | | | | +|--------------------|-----------------------------------|----------------------------------|-----------------------------------|----------------------------------| +| | NTC | | ETC | | +| | FR2A<br>(23.45GHz -<br>32.125GHz) | FR2B<br>(32.125GHz -<br>40.8GHz) | FR2A<br>(23.45GHz -<br>32.125GHz) | FR2B<br>(32.125GHz -<br>40.8GHz) | +| <b>MOP-EIRP</b> | 4.89 | 5.09 | 5.17 | 5.37 | +| <b>REFSENS-EIS</b> | 5.19 | 5.19 | 5.45 | 5.45 | + +Whether the recommended $\pm 4^\circ\text{C}$ temperature tolerance limit of FR2 ETC system defined in clause 5.4.4 would introduce additional MU or not, is FFS. + +### B.1.5 Measurement uncertainty budget for FR2-2 test methods + +*Editor's note: based on the approved SID, the preliminary MU assessment for 52.6GHz should be added.* + +# Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|-----------|------------|----|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2019-10 | R4#92bis | R4-1913071 | | | | Initial skeleton | 0.0.1 | +| 2020-11 | R4#97e | R4-2017663 | | | | Implemented the following text proposal:<br>R4-2017598 TP to TR38.884 on High DL and Low UL power test cases | 0.1.0 | +| 2021-02 | R4#98e | R4-2103985 | | | | Implemented the following text proposals:<br>R4-2100530 TP to TR38.884 on structure updates related to band n262<br>R4-2103966 TP to TR 38.884 on Low UL Power/High DL Power Test Cases<br>R4-2103967 TP to TR38.884 v0.1.0 on polarization basis mismatch<br>R4-2103968 TP to TR 38.884 on Inter-band DL CA in FR2 | 0.2.0 | +| 2021-04 | R4#98bis | R4-2106165 | | | | Implemented the following text proposals:<br>R4-2104523 TP to TR38.884 v0.2.0 on MU Annex<br>R4-2104897 Rapporteur input to TR38.884<br>R4-2104958 TP to TR 38.884 on Inter-band DL CA in FR2<br>R4-2106129 TP to TR38.884 v0.2.0 on ETC system<br>R4-2104519 Discussion and TP to TR38.884 on FR2 test time reduction<br>R4-2106164 Text proposal to TR38.884: Fast Spherical Coverage Method | 0.3.0 | +| 2021-05 | R4#99e | R4-2108098 | | | | Implemented the following text proposals:<br>R4-2108652 TP to TR38.884 v0.3.0 on UL signal demodulation<br>R4-2108658 TP to TR38.884 v0.3.0 on Environment conditions<br>R4-2108659 TP to TR38.884 v0.3.0 on measurement uncertainty<br>R4-2108653 TP on high DL power and low UL power test cases<br>R4-2108655 TP to TR38.884 v0.3.0 on testing time reduction<br>R4-2108657 TP to TR38.884 on permitted test methods for demodulation and RRM in band n262 | 0.4.0 | +| 2021-06 | RP#92e | RP-211465 | | | | Presented to RAN for information | 1.0.0 | +| 2021-08 | R4#100e | R4-2115820 | | | | Implemented the following text proposals:<br>R4-2112986 TP to TR38.884 on TPMI index for EIRP measurement<br>R4-2115762 TP on high DL power and low UL power test cases<br>R4-2115764 TP to TR38.884 on the EVM calculation method<br>R4-2115766 TP to TR38.884 on enhanced test methods for FR2 testing time reduction<br>R4-2115822 TR structure to accommodate OTA test methods for 52.6-71GHz | 1.1.0 | +| 2021-11 | R4#101e | R4-2120768 | | | | Implemented the following text proposals:<br>R4-2120697 TP on CFFdeltaNF Rohde & Schwarz, Keysight Technologies<br>R4-2120696 Preliminary MU assessment of CFFDNF and CFFNF methodologies Keysight Technologies, Rohde & Schwarz<br>R4-2120695 TP to TR 38.884 on general aspects vivo | 1.2.0 | +| 2022-01 | R4#101bis | R4-2203128 | | | | Implemented the following text proposals:<br>R4-2200452 TP to TR 38.884 on release independence applicability of test method enhancements<br>R4-2203078 TP to TR 38. 884 on extension of NR test methods to FR2-2 | 1.3.0 | +| 2022-03 | R4#102 | R4-2207512 | | | | Implemented the following text proposals:<br>R4-2207202 TP for TR 38.884 on NR test methods extension to FR2-2<br>R4-2207203 TP to TR38.884 on minimum SNR for RRM test cases for band n263<br>R4-2207204 TP to TR38.884 on minimum SNR for demodulation test cases for band n263 | 1.4.0 | +| 2022-03 | RP#95e | RP-220452 | | | | Presented to RAN for approval | 2.0.0 | +| 2022-03 | RP#95e | RP-220856 | | | | Editorial corrections | 2.0.1 | + +| <b>Change history</b> | | | | | | | | +|-----------------------|----------------|-------------|-----------|------------|------------|--------------------------------------------------------|--------------------| +| <b>Date</b> | <b>Meeting</b> | <b>TDoc</b> | <b>CR</b> | <b>Rev</b> | <b>Cat</b> | <b>Subject/Comment</b> | <b>New version</b> | +| 2022-03 | RAN#95 | | | | | Approved by plenary – Rel-17 spec under change control | 18.0.0 | +| 2022-06 | RAN#96 | RP-221688 | 0001 | | F | CR to 38.884 on finalizing the study outcomes (Rel-18) | 18.1.0 | +| 2022-09 | RAN#97 | RP-222030 | 0002 | 1 | F | CR on TR 38.884 for FR2-2 maximum DL testable SNR | 18.2.0 | \ No newline at end of file diff --git a/marked/Rel-18/38_series/38895/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-18/38_series/38895/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09a1653876418987c5b7a3c865bbae3588b692e7 --- /dev/null +++ b/marked/Rel-18/38_series/38895/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23eb85a48289422ec9963312f54ab6f7248a982ae19203520b2a26ebd7af6eb5 +size 9400 diff --git a/marked/Rel-18/38_series/38895/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-18/38_series/38895/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..894fcb5eb3e24d47233e565981d4b7081b9b10f8 --- /dev/null +++ b/marked/Rel-18/38_series/38895/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f6cb670b40ce835bba12b6b0555c3239aed5b09de8119b4a63486ff2c2c218d +size 5707 diff --git a/marked/Rel-18/38_series/38895/raw.md b/marked/Rel-18/38_series/38895/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..cf54fa7eb5efa65923c9296565bd653c816afd2f --- /dev/null +++ b/marked/Rel-18/38_series/38895/raw.md @@ -0,0 +1,255 @@ + + +# **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; High power UE (power class 1.5) for NR FR1 TDD single band (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a stylized '5G' with a green wave-like graphic 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 icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath. + +3GPP logo + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + +<http://www.3gpp.org> + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|--------------------------------------------------------------------|---| +| Foreword ..... | 4 | +| 1 Scope..... | 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 | +| 5 High power for FR1 TDD single bands with power class 1.5 UE..... | 7 | +| 5.1 NR band n34..... | 7 | +| 5.1.1 UE maximum output power ..... | 7 | +| 5.1.2 UE additional maximum output power reduction ..... | 7 | +| 5.2 NR band n40..... | 8 | +| 5.2.1 UE maximum output power ..... | 8 | +| 5.2.2 UE additional maximum output power reduction ..... | 8 | +| 5.3 NR band n39..... | 8 | +| 5.3.1 UE maximum output power ..... | 8 | +| 5.3.2 UE additional maximum output power reduction ..... | 8 | +| Annex A (informative): Change history..... | 9 | + +# 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 release 18 basket WI High power UE (power class 1.5) for NR FR1 TDD single band. The purpose is to gather the relevant background information and studies in order to complete the band specific requirements for the newly requested bands for power class 1.5 UE under TDD 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 TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP RP-222351: "New WID on High power for FR1 TDD single bands with power class 1.5 UE". +- [3] 3GPP RP-223499: "Revised WID on High power UE (power class 1.5) for NR FR1 TDD single band". + +# --- 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]. + +| | | +|-----|----------------------| +| UE | User Equipment | +| TDD | Time Division Duplex | + +# 4 Background + +At 3GPP RAN#97 meeting, a basket Work Item on “High power for FR1 TDD single bands with power class 1.5 UE” [2] was approved for Rel-18. At 3GPP RAN#98 meeting, the WID is revised [3]. The objectives of the core part are as follows: + +Develop RF requirements that are applicable to PC1.5 UE mobile device and FWA for NR TDD bands. + +- Introduction of high power UE (power class 1.5) operation for NR TDD bands. + - Including bands n34, n39, n40 as in table 1. Other bands based on operators request. +- Specify RF characteristics with dual-PA assumption, including following requirements if needed. + - UE maximum output power + - Tx power tolerance + - A-MPR, if needed +- Reuse existing SAR mechanism. + +**Table 1: Power class 1.5 NR TDD bands within FR1** + +| NR FDD band | Contact name, company | Contact email | Other supporting companies (min. 3) | Status (new, ongoing, completed, stopped) | +|-------------|-----------------------|----------------------------|-------------------------------------|-------------------------------------------| +| n34 | Chunxia GUO, CMCC | guochunxia@chinamobile.com | CATT, ZTE, Huawei | completed for PC2, new for PC1.5 | +| n39 | Chunxia GUO, CMCC | guochunxia@chinamobile.com | CATT, ZTE, Huawei | completed for PC2, new for PC1.5 | +| n40 | Chunxia GUO, CMCC | guochunxia@chinamobile.com | CATT, ZTE, Huawei | completed for PC2, new for PC1.5 | + +The present document is a technical report for this basket Work Item. + +# 5 High power for FR1 TDD single bands with power class 1.5 UE + +## 5.1 NR band n34 + +### 5.1.1 UE maximum output power + +**Table 5.1.1-1: UE Power Class** + +| NR band | Class 1 (dBm) | Tolerance (dB) | Class 1.5 (dBm) | Tolerance (dB) | Class 2 (dBm) | Tolerance (dB) | Class 3 (dBm) | Tolerance (dB) | +|----------------------------|---------------|----------------|-----------------|----------------|---------------|----------------|---------------|----------------| +| n34 | | | 29 <sup>5</sup> | +2/-3 | 26 | +2/-3 | 23 | ±2 | +| NOTE: Achieved via dual Tx | | | | | | | | | + +### 5.1.2 UE additional maximum output power reduction + +Void. + +## 5.2 NR band n40 + +### 5.2.1 UE maximum output power + +Table 5.2.1-1: UE Power Class + +| NR band | Class 1 (dBm) | Tolerance (dB) | Class 1.5 (dBm) | Tolerance (dB) | Class 2 (dBm) | Tolerance (dB) | Class 3 (dBm) | Tolerance (dB) | +|----------------------------|---------------|----------------|-----------------|----------------|---------------|----------------|---------------|----------------| +| n40 | | | 29 <sup>5</sup> | +2/-3 | 26 | +2/-3 | 23 | ±2 | +| NOTE: Achieved via dual Tx | | | | | | | | | + +### 5.2.2 UE additional maximum output power reduction + +Void + +## 5.3 NR band n39 + +### 5.3.1 UE maximum output power + +Table 5.3.1-1: UE Power Class + +| NR band | Class 1 (dBm) | Tolerance (dB) | Class 1.5 (dBm) | Tolerance (dB) | Class 2 (dBm) | Tolerance (dB) | Class 3 (dBm) | Tolerance (dB) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|----------------|-------------------|----------------|---------------|----------------|---------------|----------------| +| n39 | | | 29 <sup>5.7</sup> | +2/-3 | 26 | +2/-3 | 23 | ±2 | +| Note: PC1.5 considerations for bands n39 35 MHz CBW will be handled in WID “Adding new channel BWs support to existing NR bands [RAN4 WI: NR bands R18 BWs-Core]”. | | | | | | | | | + +### 5.3.2 UE additional maximum output power reduction + +In 3GPP RAN4 #104bis meeting, following agreements is approved to evaluate A-MPR for NS\_50. + +- A-MPR including 5MHz and region need to be re-evaluated. +- Evaluate the PC1.5 A-MPR requirements for NS\_50 for band n39, using the Rel-17 RF assumptions for mobile devices. +- The new PC1.5 A-MPR requirements to be defined for NS\_50 are also applicable for FWA devices. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-----------------|------------|----|-----|-----|----------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-10 | RAN4 #104-bis-e | R4-2215853 | | | | TR skeleton | 0.0.1 | +| 2023-02 | RAN4 #106 | R4-2301577 | | | | Adding band n34, n40 | 0.1.0 | +| 2023-04 | RAN4 #106-bis-e | R4-2304281 | | | | Add note 7 for PC1. N39 | 0.2.0 | +| 2023-12 | RAN#102 | RP-233521 | | | | Provide endorsed TR to RAN plenary for one step approval | 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